yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] dcmedic:
Yes!!.. I'm familiar with command line adjuncts. I'm saying that it will not dump the whole dmesg log to the file, it will only dump around 25-50 lines of it.......

edit: I figured it out......
[Touch Pro2, Tilt 2 Android Development] Raul^:
I'm not sure if we should only report SODs (i'm using test kernel from this moring and haven't got one). If not, then I have problem with data/phone icons - they look like there were no phone service/no data service, but when I connect to internet it changes into proper Edge/3G icon. On the lock screen it shows no service / Orange . Really strange, never had such behavior with prior to this kernels ('this' means 2/2/2011).
[Touch Pro2, Tilt 2 Android Development] workingmanbh:
Hey @arrrghhh, i'm trying to this at my phone. Last night i hadn't time, and only later i'll return home.

And how do i know my panel version ?
[Touch Pro2, Tilt 2 Android Development] Christiaan91:
SoD logs

A got a SoD today so here are my logs.

I got 1 before rebooting android (mounting data.img in windows) and 1 after booting android.

With the kernel for SoD debug( 1/2 i thought)
[Touch Pro2, Tilt 2 Android Development] CrEOF:
I had a SoD this morning. My phone (Tilt2) didn't want to go to sleep - LED never went green. Thinking this may have been related to the tweaked Email app and Exchange accounts I added yesterday I removed the accounts and rebooted. After booting Android back up I was not able to get the device to respond - had to pop the battery cover and press the reset button. Attached is the log file. If you need any more info let me know. Thanks!
[Touch Pro2, Tilt 2 Android Development] Christiaan91:
SoD is when the phone doesn't wake up. When it doesn't want to sleep it isn't a SoD. SoD = sleep of death
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Very odd indeed, I don't see this behavior, and I don't think anyone else has either.

However, you are using a primarily CDMA device as a GSM device - might be part of the problem. You might have more problems when we split boardfiles, but hopefully not. I for one am looking forward to it, I see all sorts of weird GSM commands in my logs.

First, don't run that Huawei ROM to test these kernels, it'll probably skew results.

Second, you have to use haretconsole and dump some info from it to get the panel type. If you have a RHOD100, I'd just leave this kernel be until the AUO panel is up to speed.

Mounting data.img in windows...? That sounds dangerous.

I'll send these to WisTilt2.

So were you ever actually booted into Android? This doesn't really sound like the SoD condition we've all been talking about.

Usually the phone is sleeping - green LED. Then you try to wake the device, and it refuses. Now there's a ton of other conditions related to this, I've sometimes had the LED go orange and it acted like it was going to wake, but never does. Sometimes the LED never changes. Sometimes the kbd backlight still works, sometimes it doesn't. The only thing that is consisitent is the device is impossible to wake. Panel will never come up, even if you wait 10 minutes, hit every button, etc.

Also good to note, adb never worked and I could never call the device - hence the name Sleep of Death.

Back to the system_server discussion - WisTilt2 seems to think we have enough logs for him to attack the root cause, thanks to all those who submitted logs. Hopefully in the short term he'll throw out a kernel to resolve the system_server bug, and long term he plans on attacking the root cause, which will definitely take longer.
[Touch Pro2, Tilt 2 Android Development] CrEOF:
The phone did boot up to the lock/slider screen. I usually let it sit there for a minute or two to let it finish doing its thing. I'll pay more attention to it next time.
[Touch Pro2, Tilt 2 Android Development] Christiaan91:
Never had a problem with mounting in windows. I can mount the ext2 as well.

BTW what exactly is the system_server bug. I read that you've to call your voicemail or something to stop it. I never called my voicemail to stop anything, maybe i don't have any system_server errors. Ok, the first 2 minutes my phone is a bit slow, but after that it's running smooth. Maybe you can use my logs to see what's different?
[Touch Pro2, Tilt 2 Android Development] Raul^:
That slowness is because of system server being busy, for some of us it doesn't stop after a looong time. I have to make a call to stop it.
[Touch Pro2, Tilt 2 Android Development] surge919:
I haven't experiences the issues mentioned in this thread yet, but since using the kernal with debugging turned on, my phone did restart on it's own.

Would the logs be useful for the devs?

Should a new thread for reboot tracking be opened and the logs sent there?
[Touch Pro2, Tilt 2 Android Development] Raul^:
Looking at issues which are very rhodXXX dependent I think it's almost like making this kernel+modules for 10 phones at once. They surely have some parts alike, but many more things doesn't work the same (for example rhod100 'other' panels).

I understand that splited boardfiles would mean better comptibility for specific rhod, but that would mean no gsm for me. And I know about 10 ppl who have Verizon/Sprint version of TP2 in Poland. I for example wanted to have jack more than front camera.

End of offtopic.

I've read on the PPCGeeks that WisTilt: "..he'll just force it to start again basically if it is detected that the condition exists. "

I hope it does work, when I used crash system server it always meant no service. And a restart.
[Touch Pro2, Tilt 2 Android Development] rpierce99:
Yeah he's not crashing system server, he is just restarting some failed transactions from his description. Should all happen before bootani, so with any luck, you won't even notice it happen.
[Touch Pro2, Tilt 2 Android Development] aichemist:
I got the latest kernel, but I'm not sure how to do the start the debug thing. I need some help =). I am using FRx04
[Touch Pro2, Tilt 2 Android Development] portreeve:
would love to help but i get seem to get the drivers to load on my windows 7 box via http://xdaforums.com/showthread.php?t=849718&page=1
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Don't worry about system_server logs guys, WisTilt2 said he had enough to attack the root cause. I should adjust the first post, sorry...

Don't sweat, it'll still work as GSM or as CDMA - the point being is they're different phones, therefore they need different boardfiles. I don't think it'll change the way the radios function, we're not going to lose any functionality here - the point is to gain functionality, and the ability to change phone-specific things more easily (ie without breaking 15 other phone types...)
[Touch Pro2, Tilt 2 Android Development] toadlife:
I've experienced this too ("No Service" on the lockscreen), and my device is GSM only but after rebooting a few times I've not had the issue. I have no idea how to reproduce it. It's not really a big deal IMO.
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
If you guys still need logs for the SoD's? My Rhod had one last night while charging, I had to leave in a hurry this morning so I dumped the entire dropbox after rebooting WinMo->Android. Attached is a rar with all kmsg's, unfortunately there is no date attached to it :S (none that makes sense anyway). Is there a way to find out which one is most recent by the large numer at the end?

I wish I can help with the system_server bug, but unfortunately (?) I haven't had one since using this kernel....
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
BTW I have quite some problems calling people or when I get called with the sound; I often cannot hear the other side, and vice versa. Haven't had those probs with the 'standard' FRX04 build. Not sure if this is the place to put these problems?
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
So ehm, I was wondering: everybody says some stuff won't work when using a AUO panel. Most of the stuff works fine with me (except some calls but who needs a phone for that haha!), but out of curiosity I was wondering what panel I had. So I used Haretconsole and it returned 0x13 which should mean AUO right? So has WisTilt2 fixed it or am I just really special :D?
[Touch Pro2, Tilt 2 Android Development] Christiaan91:
So Yes 0x13 is AUO panel.
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
I know that it's an AUO panel, I was just wondering why (almost) everything works fine with this kernel when the generel 'Rhod100/AUO caveat/warning' applies to this kernel (see first post). I must admit that I don't know what this caveat implies, but it says that it will not work for AUO panels. Since it does I was wondering if this is a weird case or that the caveat doesn't apply anymore because it's fixed or whatever.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Based on what I've been told, the panel won't properly collapse, and therefore you won't get any benefits from running this kernel.

Soooo... I wouldn't advise running this kernel. It seems it is unknown how to wake that panel after it collapses - so it's my understanding that the panel is never collapsed, so you won't get any benefits from running this kernel. If anything, it might just hurt - which it sounds like it has.

I didn't just put that up there because I hate people with AUO panels ;).
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
:) I just found out my panel type after using it for 4 days :D perhaps a bit naive hehe. Anyway, I'll go back to the standard build I gues, cheers!
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Ha, panel type isn't exactly common knowledge, so no worries there. Seems the majority (if not all, except for that one 210) of RHOD100's have the AUO panel, which is why I say for the RHOD100 folk to hold off for the time being.

Sucks, and I do apologize - hopefully WisTilt2 can look at this other panel type, he keeps getting pulled in 5 different directions because there is just so much to be done...
[Touch Pro2, Tilt 2 Android Development] husam666:
Hey..

I'm sorry i couldn't test the last 2 kernels

and I can't do it now (I don't have time sorry). I'm still with the 30/1 kernel and it's pretty stable to me. I my phone never experienced any SODs and battery life is good.

Thank you :)
[Touch Pro2, Tilt 2 Android Development] ersinkavakli:
wireless lan not working with the latest file.

What should be the solution?

Phone Topa100.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Kernel is RHOD only, and we're not really looking at WLAN with this kernel. Panel collapse mainly, with the latest trying to trap a particular condition, system_server.
[Touch Pro2, Tilt 2 Android Development] Ltilt2:
I'm using FRX04 and pressed the update botton, it said I needed to update the 01/23 to 1977....... dont remember what the number was but it started like 1977

Does anyone know about this?

Also after uninstalling all apps I have had any SOD but I'm tempted to download like the XDA app and Opera Mini and others.

Do you guys think apps are the cause of SODs??:confused:
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Not sure what the cause of the SoD is exactly, seems like there may be many different scenearios where SoD can occur...

However, are you sure you posted this in the right thread? I assume when you say you press "Update" you mean Sov's startup utility - nothing within Android. This update utility would not apply to these kernels whatsoever, so I'm not quite sure why you're mentioning it.

If you'd like to run this test kernel, you'll have to download it and put in on your SD manually.
[Touch Pro2, Tilt 2 Android Development] aichemist:
Any kernel to test this weekend =) ? Itching at home.
[Touch Pro2, Tilt 2 Android Development] XavierGr:
Well, my Rhodium is rhod100 with an AUO panel (pd 0x00081034 4 returns 0x13) but with this kernel I get no SODs and a surprisingly good battery life. I am running latest FROYO X with "pm.sleep_mode=1 and acpuclock.oc_freq_khz=786432" without any problems. My phone is greek localized, GSM and has a keyboard layout of rhod100_uk. The only misbehaviour I've seen is that when sleeping (green led) I have to touch the panel for it to properly wake. If I won't touch it, it will either sleep again or have a delay of 1-2 seconds to wake up.

If what you are saying is true I wonder how much of an improvement we can get.

P.S: About overclocking. Most guides I've read say that stock speed is 528 MHz with a value of 540672 in kHz. But we are talking in kHz not kilobytes. If I am not mistaken 540672 kHz are 540.672 MHz. Why divide by 1024 when measuring SI units?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Explained in the FAQ.
[Touch Pro2, Tilt 2 Android Development] Raul^:
It's not explained in FAQ. I asked for this before and I got response, that the values in FAQ are wrong.
[Touch Pro2, Tilt 2 Android Development] XavierGr:
Exactly! 528 MHz is 528000 KHz not 540672 KHz. The FAQ assumes that 1024 KHz = 1 MHz which is completely wrong.
[Touch Pro2, Tilt 2 Android Development] Eodun:
Take the acpuclock.oc_freq_khz= and put the values you wish. Start at 528000 and rise it until it freezes, then go back and leave it.

But I don't feel it to be faster...
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hrm, seems everyone is wrong - I assumed the FAQ was correct (I apologize, never really verified).

I get this when I put in 540672:

ACPU running at 537600 KHz

If I have nothing in there:

ACPU running at 528000 KHz

Now if I put in 528000? Guess what...

ACPU running at 518400 KHz

So they're in steps of 19.2khz basically, and you have to go in those steps - or else it'll go to the next closest one. I'll have him update the FAQ, thanks for pointing it out.

Edit - If you want exactly 528mhz, just don't overclock - simple.

This also isn't the place to discuss this issue, not even sure why it came up in here...
[Touch Pro2, Tilt 2 Android Development] F22:
Overclocking Steps

The FAQ is indeed off. Those who have pointed out that MHz are not calculated like MB are correct. 1MHz is 1,000kHz or 1,000,000 Hz. As Arrrghhh has mentioned, the clock speed of the CPU when overclocking is a whole number multiple of 19.2MHz or 19,200kHz. If you try to assign a different value it will be rounded down to the nearest multiple of 19.2MHz that is a lower value.

Some people who do the math will point out that 528MHz isn't a whole number multiple of 19.2MHz. They are correct, it isn't. This is because clock speed is calculated a little differently when you aren't overclocking. Your handset's PLL2 value gets divided by 2 instead of 1, which effectively allows for 9.6MHz steps in the cpu speed for every 19.2MHz you increase PLL2. Why don't we do it this way while overclocking? Because we can't. There is a maximum value that PLL2 can attain. In order to overclock beyond half that value we need to change the divisor on it to a 1 instead of a 2, and that doubles the size of each clock step increment.
[Touch Pro2, Tilt 2 Android Development] XavierGr:
Thanks for clearing that out. Now I can be sure of the exact frequency that my Rhodium is over-clocked (confirmed by dmesg).

Currently I can get at 806,4 MHz in Android (19.2 * 42), while in Windows Mobile I could only get at around 747 MHz.
[Touch Pro2, Tilt 2 Android Development] BigOnes69:
I mostly experience the SOD after a phone call I have found that I can avoid this by opening and closing the keyboard at the time the screen times out and goes into the sleep mode. This has been true for me for most all of the latest kernels I tested in which we have the server issue. The earlier kernels which I mostly tested on my diamond 500 rather than my rhodium 400 did not have this issue. This kernel has not defeated the sod completely and I do not think you are going to do it until you answer the bigger picture.

To explain what I think.With the various chipsets being co dependent for various functions when you did not utilize those functions you had no problem (earlier kernels). When you you started activating more features (later kernels) you created more co dependent problems.

Once you get everything working ie. Bluetooth, Audio jack, Camera etc. you will resolve the issue.

The weirdest example of this I have come across is a specific motherboard I had in one of my computers if the wireless keyboard battery went low the Bluetooth, usb, and computer would randomly crash. I spent days troubleshooting this with a post probe, software, and removal of devices etc.. until the battery failed completely. Whenever this occurred I just replaced the battery. The connection is the keyboard controller, Bluetooth, and USB were co dependent.

What tells me this is the case, with our phones, is all the different random occurrences of the SOD throughout the various machines. The co dependent chips in the various phones do things differently thus the different SOD occurrences.

I could be wrong but I would fix everything first and ignore this problem it might just go away on its own.
[Touch Pro2, Tilt 2 Android Development] outerdepth:
That Sounds Like A Winner To Me

That is a very interesting thought. I have shared this viewpoint with you for a while. I have also had similar pc issues like you referenced earlier. I noticed once I resolved the issue with one device, it fixed crashing issues or other issues that arose from devices that are "co-dependent" as you stated. I think this approach of not messing with the SOD's is perhaps the best approach for the time being. We might find that if we can get the different bluetooth, wifi, data, camera issues resolved, then in turn the system errors might just disappear since they are interrelated. Good mention!!:cool:
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
LOL I wish what you said was true, but the SoD seems to be happening from simple bad code.

There's a lot of places that the kernel code needs to be cleaned up and rethinked. Problem is we have only so many devs, and they just tackle things as they see fit - not really an order to any of it, y'know.

Not that we're not trying to get everything fixed guys. I just doubt that if we fix everything else that the SoD will magically disappear...
[Touch Pro2, Tilt 2 Android Development] BigOnes69:
You are probably right but I think this approach would be easier and many of the problems would be resolved that might have you looking in the wrong place or the wrong approach. Mine is just an opinion but I have been working these type of problems for over 30 years. I was always a troubleshooter wherever I worked because I could take a step back look at the big picture and move towards the goal from that perspective. It saves time and effort. And believe me frustration..
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Oh trust me I know. We've come a long way, and we're in the home stretch now it seems...
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
First post updated guys...

AUO panel folk - unite! And let me know how it goes!! :D

Oh and for the rest of you... there is a new kernel, but the only change is in sleep you get a blinking green LED instead of a solid one... Hoping to help diagnose these SoD issues ;)
[Touch Pro2, Tilt 2 Android Development] randomblame:
The new kernel will not boot it reboots windows mobile immediately

before you ask yes I downloaded the correct one not the AUO kernel.

I get two vibrations and then I see windows mobile rebooting. There is no kernel message output at all - which completely discounts anything panel related.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Heh, noticed the same thing myself. I pulled that one for the time being, it'll be back shortly I hope... Sorry 'bout that, thanks for the post ;). Fixed!
[Touch Pro2, Tilt 2 Android Development] randomblame:
got it - it's working properly so far blinking light etc.
[Touch Pro2, Tilt 2 Android Development] muziling:
rhod400 with 2/2 kernel, for tested two days, occured:

1. answer & talk phone from HongKong for some minutes, first time phone auto back to boot animation screen, phone normal, but sound auto changed to speaker mode. Second time, after talk several minutes, sound auto changed to speaker mode.

2. Seems SOD, but when I keep pressing power button, alternative press menu button, screen wake up. Today, when I plug in usb cable(for adb shell), press power button not wake up , keep pressing power button, alternative press menu button, phone auto reboot

I attach the logs below
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
Will try this afternoon! Allthough I had no problems booting with my AUO panel with the 2/2 kernel.
[Touch Pro2, Tilt 2 Android Development] Naadi900:
Hope to get my phone back within a few hours.

Then I will first try to establish wether I have a AUO panel or EID, as I had no problems booting before, neither with waking up the panel.. but not sure if my battery life was better.

I'm working on OSX so have to see how to get haretconsole working, have ubuntu and xp in virtual machines, but you never know if it works.

If I can't find out I'll just try both kernels haha.
[Touch Pro2, Tilt 2 Android Development] großa:
New Kernel up and running (Rhod100_de).

I suppose that i have a EID panel. If i'm using the AUO panel kernel, my phone is

booting fine. But i can't wake it up, when it's sleeping.

The automatic brightness adjustment isn't working. Brightness has changed. Seems to be darker as before.

XDAndroid is faster now (just my feeling).
[Touch Pro2, Tilt 2 Android Development] snalbansed:
Nearly all the kernels to date will boot with an AUO panel, but things start to go wrong with frequent SOD. So that would suggest that you do have an AUO panel.

If you have an EID panel, then the AUO kernel will not boot.
[Touch Pro2, Tilt 2 Android Development] snalbansed:
Fingers crossed

New AUO kernel installed. So far looks good, appreciate the keyboard back lights and Caps light. Fn light comes on with Ctrl instead of Fn, but I think that has been mentioned before.

Only time will tell if this is a good'n :)

Thanks Wistilt2!
[Touch Pro2, Tilt 2 Android Development] snalbansed:
Does the slow blinking green light indicate any particular depth of sleep? On my newly updated AUO kernel rhod100, the light goes to green blinking within a few seconds of the screen going off.

Ed
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Not to my knowledge, just blinking LED indicates sleep, solid orange indicates wake.

WisTilt2 shot me an email while I was sleeping, said he got the panel detect worked out... so I'll post another kernel here shortly!
[Touch Pro2, Tilt 2 Android Development] snalbansed:
Sleeping? Are you not on here 24/7? ;)

First crash since new kernel - rebooted to enable sleep without disabling GPS after using it, and the screen has frozen (on). Reset required. Old kernel data.img.
[Touch Pro2, Tilt 2 Android Development] Naadi900:
Yeah, since when do you sleep Arrrghhh?! shame on you haha.

Anyway, just got my phone back :) had a boardswap, so new imei code. But now my F and U buttons don't work!! the idiots. So far I got a new screen, fixed the keyboard, did a boardswap and they broke the keyboard haha. I'm gonna claim a desire Z haha!

Anyway, before i'll send it off i'm gonna do a test!

Is there anyway to read from the logs with the upcoming kernel what screen you have? As it has panel detection working?

Thanks!!
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
What does "Old kernel data.img" mean? I don't think the data.img matters, but if your particular data.img is messed up, then yea...

Also, I've had that happen to me a few times, but very rarely. Now when you say 'screen has frozen on' <---- was it just the backlight, or was the panel itself up? As in, could you "see" anything on the screen, or was it a blank screen just the backlight on?

Thanks. Might want to try a new data.img...
[Touch Pro2, Tilt 2 Android Development] crazyC:
I assume I have an AUO panel on my UK Rhod100 as the AUO kernal works fine. Seems to take longer to wake up than the original with Froyo X after its been asleep for a while. I keep thinking I am having a SOD but then it wakes up.

Having said that I have never really had this SOD issue with mine anyway.

Battery life does indeed seem better.

Excellent.