05-04-2012, 09:36 AM | #1 |
Member
Posts: 16
Karma: 10
Join Date: Jan 2012
Device: kindle touch
|
strange issue of KT
I update my KT to 5.1.0 and it was fine at the begining, (with jailbreak,luncher 1.1.0 and simple screen saver hack)
After several hours ,it's touching control suddenly became mad—— I press the menu and it goes to search, I select books and has no feedback. Clean the screen is no helping. Since the diag mode works fine, I figure it's software issue,so I use dd to clean /var/local and downgrade to 5.0.0, then upgrade to 5.1.0 again. After these procedures everything works fine for 3 or 4 days then the touch screen became mad again, this time dd is not helping anymore, I try fastboot flash kernel kernel-kt-5.0.0.img and with no luck. The diag mode still works fine so the hardware should be ok, is there any other thing I can do to save my KT? (It can reboot normally,every thing is working other than touching control) Last edited by dir194; 05-04-2012 at 09:40 AM. |
05-04-2012, 09:48 AM | #2 |
Member
Posts: 16
Karma: 10
Join Date: Jan 2012
Device: kindle touch
|
everything I have try is here:
================================================== ===== D:\kindletools\debricking\fastboot_win_public>fast boot flash kernel kernel-5.0.0.img downloading 'kernel'... OKAY [ 0.345s] writing 'kernel'... OKAY [ 0.635s] finished. total time: 0.979s D:\kindletools\debricking\fastboot_win_public>fast boot setvar bootmode bootloader setting 'bootmode' to 'bootloader'... bootmode bootloader: finished. total time: 0.012s D:\kindletools\debricking\fastboot_win_public> ================================================== ============================================ [root@[192_168_15_244] root]# dd if=/dev/zero of=/dev/mmcblk0p3 bs=4K dd: writing '/dev/mmcblk0p3': No space left on device 8193+0 records in 8192+0 records out 33554432 bytes (32.0MB) copied, 0.276325 seconds, 115.8MB/s [root@[192_168_15_244] root]# dd if=/mnt/us/mmcblk0p1-kt-5.0.0.img of=/dev/mmcblk0p1 bs=4K 89600+0 records in 89600+0 records out 367001600 bytes (350.0MB) copied, 145.847002 seconds, 2.4MB/s [root@[192_168_15_244] root]# fsck -text3 / fsck 1.41.10 (10-Feb-2009) e2fsck 1.41.10 (10-Feb-2009) Superblock last mount time (Mon Dec 19 00:55:36 2011, now = Thu Jan 1 01:08:28 1970) is in the future. Fix<y>? cancelled! Superblock last write time (Mon Dec 19 00:55:36 2011, now = Thu Jan 1 01:08:28 1970) is in the future. Fix<y>? cancelled! [root@[192_168_15_244] root]# [root@[192_168_15_244] root]# [root@[192_168_15_244] root]# [root@[192_168_15_244] root]# date -s 2012.05.04-21:33 Fri May 4 21:33:00 UTC 2012 [root@[192_168_15_244] root]# fsck -text3 / fsck 1.41.10 (10-Feb-2009) e2fsck 1.41.10 (10-Feb-2009) /dev/mmcblk0p1: clean, 5092/11352 files, 219264/350000 blocks [root@[192_168_15_244] root]# exit |
Advert | |
|
05-04-2012, 11:15 AM | #3 |
Carpe diem, c'est la vie.
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
|
You need matching partitions and kernels. To go back to 5.0.0 mmcblk0p1 you also need to flash main 5.0.0 kernel (using fastboot).
In the new 5.1.0 main kernel, in the gpl source code there were a lot of changes to the touchscreen driver code. Perhaps there is a bug? |
05-04-2012, 11:40 AM | #4 |
Member
Posts: 16
Karma: 10
Join Date: Jan 2012
Device: kindle touch
|
I'm using imgs from here
http://gitbrew.org/~dasmoover/kindle/touch/forensic/ kernel-kt-5.0.0.img.gz mmcblk0p1-kt-5.0.0.img mmcblk0p2-kt-5.0.0.img and reset mmcblk0p3 using dd if=/dev/zero of=/dev/mmcblk0p3 bs=4K still the same.... |
05-04-2012, 11:50 AM | #5 |
Member
Posts: 16
Karma: 10
Join Date: Jan 2012
Device: kindle touch
|
Wonder if 5.0.4 will be helpful.There's kernel-kt-5.0.4.img.gz in http://gitbrew.org/~dasmoover/kindle/touch/forensic/
but without 5.0.4 p01 & p02,is anyone got dumps of 5.0.4? |
Advert | |
|
05-04-2012, 11:59 AM | #6 |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
|
05-04-2012, 12:07 PM | #7 |
Member
Posts: 16
Karma: 10
Join Date: Jan 2012
Device: kindle touch
|
I've set the time,just few lines below.
[root@[192_168_15_244] root]# date -s 2012.05.04-21:33 |
05-04-2012, 12:55 PM | #8 | |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Quote:
then set the hardware clock from the system time: hwclock --systohc There are (or should be) system initialization scripts that take care of these settings, but you may have to poke them in yourself, at least once. Note: The (very few) Wifi models I have seen get the system time from an Amazon time server - but of course, that takes a Wifi connection. |
|
05-04-2012, 02:06 PM | #9 |
Member
Posts: 16
Karma: 10
Join Date: Jan 2012
Device: kindle touch
|
thx for the tip
just have a go: Code:
[root@[192_168_15_244] root]# hwclock -systohc hwclock: invalid option -- 'y' BusyBox v1.17.1 (2011-11-03 11:08:48 PDT) multi-call binary. Usage: hwclock [-r] [-s] [-w] [-l] [-u] [-f FILE] Query and set hardware clock (RTC) Options: -r Show hardware clock time -s Set system time from hardware clock -w Set hardware clock to system time -u Hardware clock is in UTC -l Hardware clock is in local time -f FILE Use specified device (e.g. /dev/rtc2) [root@[192_168_15_244] root]# date -s 2012.05.05-2:01 Sat May 5 02:01:00 UTC 2012 [root@[192_168_15_244] root]# hwclock -w [root@[192_168_15_244] root]# date Sat May 5 02:01:11 UTC 2012 [root@[192_168_15_244] root]# |
05-04-2012, 02:19 PM | #10 | |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Quote:
but I see you figured out my mistake. Now the hardware clock (whatever that is in a Kindle SoC) should keep the time between restarts. May not fix the event recognition but at least fsck should no longer complain about the file system being out of date. I was working off the observation that the problem only developed after hours or even days of use. (Clock drift or other clock problems came first to mind.) Hmm... What else can change over "normal" operation of hours or days? Some part of the filesystem "filling up"? Check the filesystem usage with: df You may want to cut&paste the result, some areas will probably report 100% as their "normal" use, making the problem area hard to spot. |
|
05-04-2012, 02:43 PM | #11 |
Member
Posts: 16
Karma: 10
Join Date: Jan 2012
Device: kindle touch
|
I actually believe the clock issue is the key before I try since the issue not happen immediately after the flash... sadly it's not working.
driver space seems ok for me.. Code:
[root@[192_168_15_244] root]# df -m Filesystem 1M-blocks Used Available Use% Mounted on /dev/root 62 54 6 91% / tmpfs 125 0 125 0% /dev tmpfs 125 0 125 0% /dev/shm /dev/mmcblk0p3 31 9 21 30% /var/local fsp 3295 607 2688 18% /mnt/us /dev/loop/0 3295 607 2688 18% /mnt/base-us [root@[192_168_15_244] root]# |
05-04-2012, 03:11 PM | #12 |
Member
Posts: 16
Karma: 10
Join Date: Jan 2012
Device: kindle touch
|
the first time I got this issue is after I accidently copy someth big to KT and fill it up.It looks fine after I del some files reflash & reupgrade,so I though it's some kind of conf file problem when the /var/local is full.
After that I keep about 1G space empty, but it happen again after days. Not sure if dd will fix filesystem's problem(if there's any), maybe filesystem had broke when I fill it up? I use fsck and diskscan under windows(for /mnt/us) , but it seems ok. Last edited by dir194; 05-04-2012 at 03:28 PM. |
05-04-2012, 04:28 PM | #13 | |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Quote:
I am out of guesses. Need to wait for GM to review this thread again. |
|
05-04-2012, 04:35 PM | #14 |
Carpe diem, c'est la vie.
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
|
|
05-05-2012, 08:40 AM | #15 |
Wizard
Posts: 1,379
Karma: 2155307
Join Date: Nov 2010
Location: Goettingen, Germany
Device: Kindle Paperwhite, Kobo Mini
|
My guess is on the hardware, sadly. I don't have a touch, but I think I would try and debug input events in diag mode. Is there evtest or a similar tool in the diag mode?
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Strange interface issue | paulfiera | Calibre | 2 | 06-27-2011 01:31 AM |
PRS-950 strange battery issue | sovre | Sony Reader | 23 | 06-22-2011 12:26 AM |
strange cover issue | affa | Sigil | 6 | 05-03-2011 06:59 PM |
Strange MetaData Issue | Sirkit | Calibre | 6 | 01-02-2010 06:30 PM |
Strange new Font issue. | shighfield | Fictionwise eBookwise | 2 | 08-22-2009 11:25 AM |