yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] Erikson89:
I also had a SOD after charging. Doesn't have this kernel but I think it could help. (Cam DEV Kernel)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
FN LED isn't working...? Works for me. As does capslock, that should all be functional.

Although, not many RHOD100's have tried this kernel, because most seem to be unlucky and have that AUO panel that doesn't work with this panel collapse code.

So, you're on the latest 1/30 (2) kernel and FN doesn't work at all, and when you enable the capslock the LED doesn't work either...? I thought everyone said these were working, and they *mostly* work for me. Eventually WisTilt2 is going to incorporate a userland hook, so he can grab the userland state of caps/FN which is always "correct".
[Touch Pro2, Tilt 2 Android Development] trusa1:
FN LED working when you press CTRL button. It is a common problem for all devices that have a CTRL button.

Please read 202 post.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Bah, sorry... I forgot. I need to pass this onto WisTilt2, thanks for reminding me again!
[Touch Pro2, Tilt 2 Android Development] Christiaan91:
When i press FN and then caps, i get the same result as when pressing only the caps key. So i can't type like this "HELLO HOW ARE YOU" at ones.

What trusa1 already said, FN led is going on when pressing the ctrl key.
[Touch Pro2, Tilt 2 Android Development] codedesignr:
So far the new kernel with FRX04 is very quick and responsive. I've had waking issues twice using the latest kernel. The first was when the phone went to sleep while downloading and installing an app from the market. The second was just after a phone call. It took about 30 secs and multiple power button presses to get the screen back on. When it did come on, I had no backlight. Had to reset.
[Touch Pro2, Tilt 2 Android Development] trusa1:
Christiaan91, you can type all uppercase letters at once.

1st press the Caps key = Caps is temporarily on

2nd press the Caps key = Caps is always on

3rd press the Caps key = Caps is off

The same rule applies for the FN key.

Just press the Caps key twice.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
New kernel posted guys.

This one is ONLY for debugging that nasty SoD issue where the phone is completely down - you cannot wake it no matter what, waiting 10 minutes, calling it, pressing every button - nothing.

I've seen this with the green LED stuck on, and sometimes with the orange LED stuck on. Sometimes I've been able to slide the kbd and see the kbd backlight turn on/off, but nothing else would work. Any of these situations I would call SoD.

Please read the first post carefully. I changed it quite a bit, as we need a few things to change to debug this SoD issue. Please feel free to ask questions, but read that first post thoroughly - I think I included everything you will need in that post, if not I will modify it. Thanks!
[Touch Pro2, Tilt 2 Android Development] Christiaan91:
Never had a SoD with this kernel, but i downloaded it, just to be sure.

You never know when you're getting a SoD
[Touch Pro2, Tilt 2 Android Development] aichemist:
The FRX04 is located in the "andboot" folder,

Would I need to change the code for debugging since its not in the root storage folder?

I wouldn't be able to get to it until after work today =(....

I had one SOD today when I was on the elevator to work! I thought I was doing something wrong, and I couldn't wake up(red LED light).
[Touch Pro2, Tilt 2 Android Development] slapshot30:
SOD has been an issue for me so I'll go ahead and test this new kernal. With me it only happened when asleep for long periods of time so I'll leave it alone for a few hours during the day to see what happens and then charge it at night and see if it wakes in the morning.
[Touch Pro2, Tilt 2 Android Development] Christiaan91:
you'll have to change /sdcard/libc.so to /sdcard/andboot/libc.so

BTW:

Do you need to save the files directly after reboot or can it be done later.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Correct, just change the left side of that mount statement as shown above.

I would assume you would want to pull the last_kmsg quickly - I'm not exactly sure when that is pulled, but it may get overwritten by your current boot. I guess you'll have to experiment, but if you do get SoD I would pull that last_kmsg as soon as you boot back into Android - just to be on the safe side...
[Touch Pro2, Tilt 2 Android Development] Christiaan91:
I already noticed, that the wake-up time is much longer then the 1/30 kernel. Is that normal?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Shouldn't be any different... Perhaps the debugs he put in there are making it take longer, but I haven't noticed any difference in panel init times. All wake within 2s.
[Touch Pro2, Tilt 2 Android Development] aichemist:
On FRX04 with 1/30 Kernel.

I just tested google navigation twice, one this morning in the car and one time at work.

After I quit from google navigation back to home screen (gps icon off), and try to sleep, it wouldn't go back to green. I recreated the situation again. Is this reported yet or it is something to do with the gps and panel sleeping ?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Oy.

You can't have GPS enabled and sleep. WELL-known bug - disable GPS in Loc&Sec, the phone'll be able to sleep just fine.
[Touch Pro2, Tilt 2 Android Development] MrPib:
Got bit by the SOD twice today (Rhod500, 1/31 wistilt test kernel).

Just loaded the new test kernel.

Please let wistilt know that him working on this bug is VERY much appreciated!

I can wait for the camera, etc, but having a phone in a coma won't do ;-)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
lol no one likes a comatose phone.

I'm assuming you weren't on this new debug kernel...? Please get the libc.so and the new kernel loaded, the more logs we can get from SoD conditions the better!!
[Touch Pro2, Tilt 2 Android Development] MrPib:
Yeah, I wasn't on the debug kernel, but I am now (with libc.so loaded).
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Cool. I'm almost hoping for an SoD, so we can see what's going on!! The anticipation is killing me, c'mon phone! Fail! lol.
[Touch Pro2, Tilt 2 Android Development] rpierce99:
Yeah I almost feel like waiting for the SoD has made me wake my phone too often to check it, thus the SoD not happening. Since some have speculated it only happens after a long sleep.
[Touch Pro2, Tilt 2 Android Development] Bld-:
I'm gonna test this kernel also! I really want to help by sharing my logs to fix these SoDs!
[Touch Pro2, Tilt 2 Android Development] toadlife:
I'm in. I've been getting the SOD issue and really want the issue resolved. It's been pissing off my wife, who's not been able to get a hold of me a few times.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Crap guys. F22 just pointed out that I'm dumb, and you don't need to do that libc crap.... there's a MUCH better method, as these are already logged and compressed in this folder:

/data/system/dropbox/

Has nothing to do with the service 'Dropbox' FYI ;).

So, going forward you guys don't need to do that libc.so mounting mess... Sorry for the confusion, I really had no idea it was already being logged and compressed.

Thanks again F22 for pointing this out!
[Touch Pro2, Tilt 2 Android Development] Christiaan91:
i tried to find that folder (data/system/dropbox/), but i couldn't find the folder.

my data folder is empty.

I also did a search to dropbox, but the search get suck on /lib/modules....... it goes on and on.

Can someone help me to find that folder?
[Touch Pro2, Tilt 2 Android Development] rpierce99:
Your data.img file gets mounted to /data, so if you are running android, your /data folder will not be empty. How are you navigating to that folder? ADB, terminal emulator? Make sure you always precede the "data" with a "/" like "cd /data/system/dropbox", otherwise you will end up trying to find a data folder as a subdirectory of where you are currently looking.
[Touch Pro2, Tilt 2 Android Development] Christiaan91:
I tried so find it when running android, with the astro file manager app. I went all the way up. Starting in /sdcard. One up in / then opened data and this folder was empty
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
You must be root to see this folder - probably be easiest if you use adb, especially since you can pull the files straight to your PC.
[Touch Pro2, Tilt 2 Android Development] Christiaan91:
Yes i've bin there. I'll try adb tomorrow.

EDIT:

Tried it with droid explorer and there i can find the folder. I was in the exact same folder on ASTRO file manager, but it didn't show any subfolders. A bit strange, but i got it finally:P
[Touch Pro2, Tilt 2 Android Development] dcmedic:
I'm experiencing NO SLEEP with this debug kernel.

It may be the debug commands.
[Touch Pro2, Tilt 2 Android Development] gnnash:
Hello, I'm a lurker here poking my head out.

Have a RHOD400, Kernel seems very stable. First boot had problems with panel init, but still on my second boot since approximately 24 hours ago. No problems waking this boot.

However, since unplugging from charging, my status LED has been stuck orange, regardless of power state.

Backlight seems a bit wonky. On wakeup, panel goes to full brightness briefly, then settles down to a slightly-too-low brightness. Panel also flares up in brightness when going to sleep on a timeout (not as bad when locking the phone).

Battery seems much improved. Mine has been unplugged for 8 hours, and is reporting 41-48 percent. (the battery level is still extremely variable, especially as my activity varies on it.) This is with a few calls and texts, some internet use, and checking email a few times. Very much improved from what I have seen in previous kernels.

EDIT: Oh, and GPS is enabled as well! Only used once or twice during the day, but still enabled. Wifi is broken, but I am using the trimmed modules file. Just rebooted to change to the "fat" modules file, and WinMo is reporting 22% battery. Rebooted into android again, and battery is reported at 76%.
[Touch Pro2, Tilt 2 Android Development] anotherhawkeye:
Experienced SOD after 5 or 6 sleep/wake-up cycles on a non-overclocked rhod400 with pm.sleep_mode=1.
[Touch Pro2, Tilt 2 Android Development] gnnash:
Got my first SOD today. Stuck with a green light, no changes with button pushes or screen taps.

This is with the fat modules file. Didn't experience this with the stripped one.
[Touch Pro2, Tilt 2 Android Development] anotherhawkeye:
I'm using the fat modules file as well (and getting SOD). Next time I get SOD, will switch to stripped version and report back.
[Touch Pro2, Tilt 2 Android Development] anotherhawkeye:
Ok, for the first time, I'm embarrassed due to a kernel :).

Was talking on the phone quietly on a sensitive subject, inside the office. Tried to reduce the volume (using the volume down button), instead the speaker phone turned on (at the loudest). Every one in half a mile could hear the private conversation. I Couldn't disconnect the call (end button didn't work), the other end the person kept talking, I finally took off the battery to quiet it.
[Touch Pro2, Tilt 2 Android Development] vnes1984:
sorry that happened, pretty funny tho :) Made me laugh
[Touch Pro2, Tilt 2 Android Development] gnnash:
Ha! I had this happen to me the first time I installed android. My battery was dying, and for whatever reason, as the phone was shutting down, my call in progress went straight to speakerphone, extremely loud. Everyone around me in target was hearing my conversation, and the microphone didn't work, so I couldn't tell the other person to stop!
[Touch Pro2, Tilt 2 Android Development] pdawg17:
Just an FYI:

Had a SOD this AM using latest stripped kernel...had a solid green light if that makes any difference...

However the SOD problem is not just with this kernel but I reported here since this is the kernel I was using at the time...I have had SOD problems since 1239 (which I think this is based off of)...
[Touch Pro2, Tilt 2 Android Development] gnnash:
Haven't had any more SOD problems.

However, every restart the phone is incredibly sluggish until I make a call. Making the call is sluggish and is still sluggish through the call, but once I can get it to end, everything speeds up.

This started after installing the fat modules file.

No server process using all of the CPU when it is slow (not that I can see anyway).
[Touch Pro2, Tilt 2 Android Development] pdawg17:
I don't even have the modules file installed and it is slow starting up and I have to make a call to fix it as well...
[Touch Pro2, Tilt 2 Android Development] gnnash:
Another update - battery yesterday was remarkable! Unplugged for over 17 hours, android was showing 61 - 66% battery remaining. This was with light use, a few calls, checking email, and some web use.

Amazing, keep up the good work!
[Touch Pro2, Tilt 2 Android Development] F22:
SOD

Yes, I just got a SOD with 1245 yesterday.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
First post updated folks!
[Touch Pro2, Tilt 2 Android Development] pdawg17:
Is wifi supposed to work with today's build? I know it's not the focus but I get an error on wifi with my rhod400...just curious if it's a problem on my end or not...
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Usually wouldn't bump this again, but it's worth it...

Keyboard backlight! Just need to make sure it's turned on when you boot haret, then it should take over in Android. Timeout it set to 3s.

Seems it works for RHOD300/400. 210 failed, and 100,500 are untested. Let me know how it works out guys! First post updated :D
[Touch Pro2, Tilt 2 Android Development] jeffgarret:
Keyboard light works great on my 500. Once in android it comes on immediately when i open the keyboard and goes off when the keyboard is about 90% closed.

WIFI now broken on first boot, trying again.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Thanks for the feedback. WisTilt2 is adjusting brightness and setting timeout to 5s in a few, so I'll update the first post then.

I'll look into the wifi issue.

Update - first post updated with new kernel, 5s timeout and brighter kbd backlight.

Wifi is fixed. Sorry 'bout that ;) (AKA first post updated)
[Touch Pro2, Tilt 2 Android Development] Yusuke14:
I was just comparing the contents of this update to the 1245 update and I noticed 4 modules missing from modules .tar.gz. They are:

rfkill_backport.ko

wl1251.ko

wl1251_sdio.ko

wlan.ko

One of those should be responsible for wifi, i'd say the wlan
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hehe, sorry dude... I edited both posts. Wifi's fixed. Thanks ;)
[Touch Pro2, Tilt 2 Android Development] MassStash:
it's dirty anyway, possible he just doesn't care bout wifi right now. this is a testing thread, ya kno what i mean?
[Touch Pro2, Tilt 2 Android Development] randomblame:
Pppretty. Sure he just added some printk's shoulddnt cause a no sleep condition. My wifes. Rhoood 300 is configured identicaly to mine but has different apps installed and won't sleeeeep either. I think the problem comes from an app. Mine sleeps quickly everyy time. Wistilt2 is working on thhhhe kernel he fixed Some problems with system server. Mayybe that will help. Hopefullyy arghh will post thatt tonight. -obviously sent from my rhod
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
It was the root thing... as mentioned earlier. If you try to 'ls' /data from the terminal without being root, it fails with permissions issues.

Works perfectly for me - try the usual. Make sure GPS is disabled. Make sure there aren't any apps running out of control. Reboot, try again.

Looks like no new kernel tonight. He doesn't quite have the issue licked, he said it's significantly better. He said that he's now able to recognize at the kernel level when it's happening, and force it to realloc memory - which is what making a phone call does basically. He wants to test it overnight, and if all goes well, you guys will have a present in the morning...

Thanks guys!
[Touch Pro2, Tilt 2 Android Development] aichemist:
will our rhodium kernel guy every post here? He's like Batman hiding in his cave and coming out to save the world when no one is watching.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
lmao, no he never goes to the forums. He does hang out in #htc-linux, but if you do go there please just lurk. A lot of devs go there, and it really is supposed to be a dev-only room - so if it becomes an issue we might have to make a locked room for the devs. No one minds if you lurk tho ;).
[Touch Pro2, Tilt 2 Android Development] rcgators:
No SOD since running the 2/1 debug kernel. Never gone this long without SOD. Was hoping to contriubte by catching a failure.:( The no-sleep with this kernel has happened twice in 14 hours, but only after running several apps over a couple hours.

Could the debug statements have changed the timing enough to affect the SOD?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
WisTilt2 found a piece of bad code and said he fixed it before he released the debug kernel... so he may have fixed it before we got the chance to even debug it.

Which, is not only mildly funny... is freakin awesome at the same time. I haven't had an SoD either!
[Touch Pro2, Tilt 2 Android Development] MrPib:
No SOD for me (yet?), but I did just get a complete freeze while composing a text. Keyboard light stayed on and everything. Should I post the KMSG file?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Can't hurt, post it up!
[Touch Pro2, Tilt 2 Android Development] randomblame:
well my phone was awake this morning (orange led) then I pushed the power button to turn it off, selected power down, and android just restarted - no winmo- it booted right back to android. so here is my dmesg http://pastebin.com/ayx0xEN5 this is the 1/30 kernel I haven't had a chance to plug in the 1/31 kernel
[Touch Pro2, Tilt 2 Android Development] Jandyman:
Did the screen stay on? If it did this has happend to me also keyboard freeze, usually it stops if you press the input box again. I also get random freezes where the keyboard posts around 30 of one character . . . .which is quiet annoyn but only a small problem ^-^

---------------------------------------------------------------------

Also a warning to everybody so that they don't waste as much time as I did: The app 'juice defender' and possibly other apps like it will have a great negative effect on waking after a period of sleep.

I was wondering why my light always seemd to be orange I taught it was a glich, and also I began gettn very slow wake-ups and freezes. I used to notice it when I changed a kernal and I taught it was a problem with my build and so everytime I got a new kernal I reinstalled my build and it suddenly seemd to solve my problem (because the new build hadn't juice defender installed yet) then later the probly would occur again after restoring all my setting and apps. I know it was a n00b moment for me @_@

But iv woken up and figured that juice-defender is the only common denominator :) and now the probly is solved (should also explain why I was gettn 4%/hour battery compared to others 1%/hour)
[Touch Pro2, Tilt 2 Android Development] dcmedic:
SoD Debug last_kmsg

Attached is the system_last_kmsg from my SoD experience.

Conditions:

-Tilt 2 - Rhod300

-FROYO X 1-28-2011 update.

-In Belt Case

-Sleep Status was unknown (as stated in an earlier post, I wasn't getting any sleep)

-Used the device for texting and email this morning.

-Could not wake by any means. Performed a battery pull (lol sounds like the old Blackberry days)
[Touch Pro2, Tilt 2 Android Development] MrPib:
The screen was on. I waited for a while, then tried all of the buttons. Completely frozen. I've had the short-term freeze you mentioned happen, but this was different.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Unfortunately that log is extremely short - only a few seconds worth of log basically. Can you grab a few others...? This doesn't do us much good, sorry :(.
[Touch Pro2, Tilt 2 Android Development] rpierce99:
dcmedic - you could also try /proc/last_kmsg and just dumping a dmesg as normal, I'm told those will also work in some cases, unless it's been a long time since your SoD.
[Touch Pro2, Tilt 2 Android Development] dcmedic:
The last_kmsg from ../proc/ appeared to be identical to the other. I'm installing SDK right now. I'll see what I get.
[Touch Pro2, Tilt 2 Android Development] slapshot30:
I just found the pro advanced task killer apk online and it seems to be working well. It has a feature to auto kill certain apps after a certain period of time (I set mine to every 30 minutes). You can also set it so certain apps won't be auto killed. My phone sleeps as normal though, no issues.
[Touch Pro2, Tilt 2 Android Development] toadlife:
I too have not had the SOD since installing the test kernel yesterday. I was getting them fairly frequently with the 1253 kernel.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Another new kernel folks.

This time, system_server is on the chopping block. WisTilt2 has a workaround for system_server, but it is NOT in this kernel. This kernel will probably cause the system_server issue as usual, but there's additional logging traps placed in this kernel to hopefully expose the root cause of the system_server issue, instead of just fixing it in a hack.

Basically grab the newest kernel, boot your phone. Assuming you have a system_server condition (verify thru top) pull your dmesg and post it.

Not sure if you have to wait until you resolve the system_server bug, but it seems like a good idea so WisTilt2 has a dmesg log of a "complete" run thru the bug. Thanks!

Update - seriously guys, on the logs... every single person downloading this new kernel should give me a dmesg log. I see 5 views, and I have 0 logs. It's really important, let's get this bug squashed!
[Touch Pro2, Tilt 2 Android Development] rpierce99:
dmesg from system_server boot:

http://pastebin.com/ym3XwXnd
[Touch Pro2, Tilt 2 Android Development] toadlife:
Do you still want SOD logs, or has that ship sailed? My phone finally got a SOD...
[Touch Pro2, Tilt 2 Android Development] toadlife:
SOD Log

Well...if you need it, here is a log from the SOD I just got. This is from the kernel prior to the latest.
[Touch Pro2, Tilt 2 Android Development] workingmanbh:
Hey, i'm using the kernel with Froyo X, and having SODs problems.

With which app, method, can i use to extract the logs to anorher dir, and use Androzip to send?

I have a rhodium100 unbranded.
[Touch Pro2, Tilt 2 Android Development] slapshot30:
Most of us are running FRX04 with these kernals, from what I understand it is more helpful.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I would prefer you run FRX04, but if you feel you're on the right kernel and have a valid log from an SoD, we'll still look at it.

Easiest way to pull logs is adb. If you're using Windows, Droid Explorer makes it pretty easy.

Also wait... RHOD100? Did you read the first post? If you have an AUO panel, it'll never wake.
[Touch Pro2, Tilt 2 Android Development] dcmedic:
When I'm dumping dmesg to a file, I only get a partial log. But when printing it to the screen, I think it prints the whole log. I'm not sure my cmd window will only show so much.

Any insight would be appreciated.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
cmd is... crap. You'll have to change the settings on it if you want to increase the buffer.

But, there's a MUCH easier method.

adb shell dmesg > dmesg.txt

Will dump the dmesg in the current directory you are at in cmd.
[Touch Pro2, Tilt 2 Android Development] dcmedic:
Well what do you recommend? I have ubuntu on VB.

I was using the same shell cmd as you listed and I would get about 50 lines or so. I just increased the buffer as high as it goes and I still can't get the whole log.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Did you try the command above...? It'll basically redirect the output (that's what the '>' character does) to a file, in this case dmesg.txt.
[Touch Pro2, Tilt 2 Android Development] rcgators:
Here is dmesg.:cool: Cleared error condition prior to dumping dmesg.

Top showed SystemState > 80%

FRX04 w Kernel 2/2