yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] snalbansed:
Update after a night and half a day running the 20th Feb test kernel. Had a SOD (on charge, green light). Reset. Had a SOD (in pocket, orange light) a short while later. Reset. Decided that the kernel was killing rhod100/AUO panels.

Booted windows, renamed andboot and returned to the andboot folder I was using for the previous test kernel, which was working fine (2011-02-18?)

Booted, had a SOD within minutes (in pocket). Mmmm... one off? Reset, booted. Had SOD half an hour later (panel on, orange light, on my desk in use).

So what gives? My phone has a bad spell and kills all kernels?

I'm now rebooting the previous test kernel, see how we go.
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
Been testing the newest since this morning; one SoD while it was in my pocket, log at http://pastebin.com/gAScUAVU

Als, I noticed that the buttons like end-call also wake up the device, and when woken, if you press menu, the device unlocks. I never noticed this, is this regular behaviour?
[Touch Pro2, Tilt 2 Android Development] hashtowent:
runs great so far on rhod100_de!

led is flashing red/green always^^ (new in this version!)

wake and sleep very fast

now up to one day usage(9°°-16°°) and still battery left (=

camera is not working.

wifi is

gps untested

data no eplus but tmo

i have frx04 latest rootfs and kernel(yours)!

did create delte data.img before first boot followed frx04 tutorial step by step.

your kernels are best for me (=
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
LOL RHOD only dude. Surprised it runs at all... You probably just won't get any benefits. I thought TOPA panels already had panel collapse code...?

I believe this is normal behavior... Not positive tho, you can confirm by going back to an autobuild kernel ;).

Delete your data.img, just to be sure.

Might want to try a fresh data.img as well. Reboots to WinMo you'll have to pull the logs from /data/system/dropbox. I guess that if you have a true SoD you'll have to pull logs from here as well ;). adb is probably the easiest way once it's setup. If not, you can move them around with the terminal emulator.
[Touch Pro2, Tilt 2 Android Development] sjabbie88:
I noticed this unlocking with the menu-button too. And I ask myself the same question about "is this regular behaviour?"
[Touch Pro2, Tilt 2 Android Development] jae18708:
Oh is that why my slide to answer screen lags so much when I receive a call? I've always had my pm.sleep_mode set to 0.. I'll have to try =1. I didn't have many SODs though, once in a while when the Froyo had been running for week or so straight, I would take it off the charger in the AM and it wouldn't wake. But that was rare.
[Touch Pro2, Tilt 2 Android Development] trusa1:
I use this combination of buttons at least one months. I like it.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yes, please read the first post carefully.
[Touch Pro2, Tilt 2 Android Development] hceuterpe:
How could you like the 'end call' wakes up the screen funcationality? Granted, I don't carry my phone in my pocket (and instead a purse), but I would imagine it would accidentally wake up all the time if the end call button woke it up!
[Touch Pro2, Tilt 2 Android Development] bahairus:
I am LOVING this kernel with FRX4 on my AT&T Tilt2: Best battery life I have ever seen; I ran the device all day and still had life left over when I went to bed. No SODs or dialer hang-ups. I can finally allow Google Voice to ring this phone again on Android. Huzzah! Way to go, devs!

(Needless to say, I am set on pm.sleep_mode=1)

I did try it with Gingerbread.. a little spotty. Some SODs. I assume that will improve as Gingerbread improves.
[Touch Pro2, Tilt 2 Android Development] djcrosstunez:
Works great here:D Instant sleep and instant wake! Good work! Rhod100 nl gingerbread. Battery life 20 hours with normal usage!
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
GPS and sleep mode...

Arghhh, are you sure that this kernel doesn't help with sleep mode and battery life at all with GPS enabled? I realize that you mentioned that the Green Led with GPS enabled doesn't mean it is sleeping, but usually if I keep GPS enabled and it doesn't sleep at all I only get maybe 6-8 hours at most on a battery. While this is the first day running this kernel at all, it seems like I have better battery life than if it wasn't sleeping at all with GPS enabled. I have 70% of my battery left with GPS enabled and the phone has been unplugged for 8 hours now and I have been running this kernel for about 6 hours.

I know it may not give me 20 hours like a lot of people have with GPS off, but if this kernel helps somewhat and gives me at least 12-13 hours I would be happy and leave GPS on, because it would last me till I get home from work everyday.

I am glad WisTilt is improving things with this kernel because 1258 was probably the worst thing that happened to my phone since the earliest kernels. I was getting multiple SOD's daily and just random reboots. This kernel is a lot more stable and I didn't have to go back to 1253 to get stability!
[Touch Pro2, Tilt 2 Android Development] rpierce99:
To be clear, you turned on GPS, then USED GPS, then closed the app that was using GPS, and the let the phone sleep for 6 hours and only drained off 30%? While 5% per hour still isn't where it should be, when I tested last night I started at about 90%, used GPS, then closed the app, let the phone sleep for maybe 3 hours, and my battery was half gone, so I lost ~40% in 3 hours. With GPS disabled I get more like 14-18 hours of sleep.

Arrrghhh confirmed in his testing of the private kernel version that GPS being enabled and previously used, the ARM sleeps, but GPS either doesn't sleep, or stays on for ~60 seconds every time the phone wakes up to do something like sync.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Correct, ARM11 would collapse immediately, but microp never collapsed - never got a solid green LED with GPS enabled (after using it). So the phone isn't sleeping completely, just partially (it seems).
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
Here is exactly what I have done so far today:

1)Took phone off charger using Kernel 1258 at 8:00am

2)Once I was at work found out that my phone had rebooted into WM when I received a phone call at about 9:30am. This was happening a lot to me, so I downloaded this kernel and put it to the phone. It was booted into it by 10:00am or earlier.

3)I went lunch around Noon and turned on my GPS to use Foursquare. I didn't turn back off GPS as I normally would. I did however us Advance Task Killer to kill Apps I started like Foursquare which I always do before putting it into sleep mode.

4)Currently it is around 4:30pm and Android says battery says it has 36% using Spare Parts.

I am using it very lightly today, just checking my email when it comes in, and that GPS foursquare usage around lunch time.

So basically I have been running the kernel since 10:00am at that time the battery had probably about 80-90% remaining at that point. I didn't check then, so I am estimating here and now at 4:30pm I am down to 36%, so 6.5 hours and battery decrease of around 44-54% keeping GPS on and asleep for the most part. I will continue this experiment tomorrow and see how many hours I get fully with it enabled on a full battery, but it looks like I would get probably get 11-13 hours or so if it is enabled which means that the phone is going into some type of partial sleep even if it isn't fully asleep because as I said before I was getting at most 6-8 hours if I had GPS on previously.

Anything else you all want to me to try on this?

I bought 2 extra batteries recently with a A/C battery charger so I always have 2 fresh batteries in my pocket (I was tired of running out of battery all the time in high usage and high user areas (football stadiums etc...) so I now can triple my battery life in those situations and also can run Android fully all the time now without worry of not having a charged phoned to make an important phone call.

Update: 02/23/11: Leaving GPS on after activating an app using it, does not give much better battery life than I was getting before when I was doing this. Before I was getting 6-8 hours at most, now I am maybe getting 9 hours. So it looks as if there is any partial sleep with GPS activated it is very minimum....oh well back to turning it off and on when I need to use it! :)
[Touch Pro2, Tilt 2 Android Development] snalbansed:
I'm confused :-(

I tried a new data.img with 20th Feb test kernel, lasted seconds. Tried gingerbread - didn't even get to the flying androids!

Put 24th November kernel back in with the old data.img, and all seems fine again. I DON'T UNDERSTAND!

I'll run with this for a day and then try the newer kernels again. I saw mention of a new official kernel - do you know what is in it? (Haven't got pc to hand)
[Touch Pro2, Tilt 2 Android Development] trusa1:
More important to me is that I need to unlock the screen (tap and slide or "menu" button).
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I don't know either man, something seems messed up for sure. Other RHOD100/AUO panel folk don't have an issue...
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Well, after a full charge and leaving it sleeping overnight, I woke up to find it with orange LED and frozen again.

Seems like I've still had the best luck with the 01/30 test kernel. Oh well.
[Touch Pro2, Tilt 2 Android Development] rcgators:
Kernel 1260 is out. Is there any way to tell if any of the test kernel changes to date were committed to the new kernel?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
1260 doesn't have much new stuff in it. Prep-work for cam commits.

None of the changes in the test kernel are 1260.
[Touch Pro2, Tilt 2 Android Development] ryannathans:
should I be using this or 1260?
[Touch Pro2, Tilt 2 Android Development] afrizal_chen:
like arrrghhh said, no much update. Let's wait for the next build ;)
[Touch Pro2, Tilt 2 Android Development] Naadi900:
This is my last_kmsg from a freeze on boot I believe. Logs look really odd compared to others.

Anyway my phone has now done fine through the night while charging, will try and check for battery usage throughout the day now.
[Touch Pro2, Tilt 2 Android Development] Holograph:
I didn't have any crash so far. I am using my phone for 2 days without having to reboot (RHOD500).
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
Mucho SODs all day! Worked fine for a couple of days and then poooof, one sod after the other :s also a freeze during boot, before the animation... Also different apps not responding on start up. This is on new SD.

Will try a new data.img, and also post my logs tonight.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
You can use whatever kernel you want dude... This kernel is for testing, so if you want to help test have at it. If you don't care, run 1260.

So you found the timebomb? Heh, just kidding. I think another RHOD100/AUO panel user had the same experience, snalsbad (sorry if I spelled that wrong :p).

Very odd indeed. Let me know how the new data.img works out.
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
Ok, so here are the logs, remebered just in time to get those before deleting the data.img :D
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
One of your logs in particular point to a bad SD - 1298364656270.

I'll get these over to WisTilt2, see what he thinks...
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
Hmmm that wouldn't be good, since it's a new brand SD, (normal) formatted with the HP tool in FAT32..... Is it definitely an error on the SD side?

The only error that was in relatively normal English I could find was the

END CALL : 0x0--

[ 313.607116] END CALL triggered without being in a call!

[ 313.607147] This really shouldn't happen

[ 330.953887] Power down.

:) I hope Wistilt can find anything in there...
[Touch Pro2, Tilt 2 Android Development] großa:
Trying this kernel since ~30 minutes now :D

It is really fast. The phone found my hidden WIFI without problems.

Sleep and wake is really, really fast ;);)

I'm really surprised. The last kernel wasn't nearly working so good.

Will try it for a few days now :)

Thanks for the hard and good work!!!
[Touch Pro2, Tilt 2 Android Development] Raul^:
I'm using this kernel since yesterday. Wake-up / going to sleep is usually faster than in 1258, but not every time. Good thin is that I have no sod's for now.
[Touch Pro2, Tilt 2 Android Development] snalbansed:
snalbans = local speak for St Albans, ed = my name. Easy!

I was going to try a different SD card assuming it was just me. I think I will anyway, then if it all happens again I'll add my logs to the ones you already have, see if there are any connections.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
I always get SoD after leaving the phone on overnight. The dmesg log is pretty much the same each time. Usability has really gone downhill for me since 01/30. I'm giving up on this for now.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
What do you mean leaving the phone on overnight? As in leaving it charging overnight?

Every night I run Android, I do battery drain testing, so I never charge overnight in Android... there's lots of issues with it, and generally avoid it. Are you saying this is better in the 1/30 kernel?
[Touch Pro2, Tilt 2 Android Development] snalbansed:
Where as I always leave it on charge over night, and have very very rarely had any issues. During the day is a different matter!
[Touch Pro2, Tilt 2 Android Development] highlandsun:
I've done both - on charger overnight, and unplugged overnight. Hangs either way. On the 01/30 test kernel I could leave it unplugged overnight and get 30-40 hours between charges.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
pm.sleep_mode=?
[Touch Pro2, Tilt 2 Android Development] muziling:
today,plug into USB cable, phone reboot, kernel 20/2, yesterday it does not.

well ,this is greate kernel, wake up sometimes also need to press serveral power button or menu button.

Not found /data/data/dropbox directory that last version store logs
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
The correct directory is /data/system/dropbox...
[Touch Pro2, Tilt 2 Android Development] highlandsun:
I was using pm.sleep_mode=0 with earlier kernels, just switched to =1 with this latest kernel.
[Touch Pro2, Tilt 2 Android Development] muziling:
upload the logs,thks
[Touch Pro2, Tilt 2 Android Development] PlacidFury:
I used to have failed wakes (having to reset phone to unlock) on my TP2 with various versions of Android.

After a couple hours with this kernel and tiad8's newest froyo x red, I've had two failed wakes, but both were easily solved by pushing power button twice (off, on again) and it woke properly the second time. I'll take that over a full reboot anytime :-)
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
New Data.img works like a charm; very responsive again, insta-wake/sleep and in the last 12 hours no SODs. Would it be interesting to have a copy of the data.img now and when The Timebomb kicks in again? To see if is anything different that might upset it? I could not do any installations etc (except for the backups from titanium) and wait for a couple of days?
[Touch Pro2, Tilt 2 Android Development] snalbansed:
I tried using a different SD card, a fresh download of stinebd's FRX04 (usually I use reefermatness'), F22's latest rootfs and the 20th Feb kernel from this thread. It booted, went to sleep from the home screen (I think, wasn't looking), then never woke up. Green light. Rebooted, got to home screen, went to sleep, never woke up :-(

I'll try and see if I can extract the logs one way or another later. For now, back to November :-(
[Touch Pro2, Tilt 2 Android Development] muziling:
About an hour ago, SoD first time in recent 3 days, logs below
[Touch Pro2, Tilt 2 Android Development] großa:
Here's what i noticed:

The phone is waking up by itself sometimes (LED switching from green to orange for 3-4 seconds), saw it last night. Phone wasn't charging.

If I get a call, or if the alarm rings, the panel needs a very long time to wake up (panel, not the phone!). Took me ~3-4 minutes to get rid of my alarm this morning.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Sometimes waking the panel is a chore, we're trying to sort that out.

The phone of course wakes up by itself - if you have any applications that sync or anything like that, the phone needs to wake up to do that...
[Touch Pro2, Tilt 2 Android Development] großa:
Yes of course. Can't remember that I've apps installed, which do have to sync. I also turned everything off in the settings.

Oh by the way. Battery went down from 76% to 30% in 19h. Did some calls, used the alarm, sent some messages and used wifi :)

Sent from my MSM using the XDA mobile application powered by Tapatalk
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
That's slightly less than 3%/hr... great considering the usage! I'm currently testing some other PM fixes, hopefully I'll be able to release another test soon. Then assuming all goes well commit!
[Touch Pro2, Tilt 2 Android Development] großa:
Sounds great!!

Sent from my MSM using the XDA mobile application powered by Tapatalk
[Touch Pro2, Tilt 2 Android Development] Naadi900:
Left it last night off the charger, battery drained +-19% in about 9.5 hours, while asleep. Have clocksync and 1 gmail account set to sync.

Today the phone had 1 or two SOD's.. and twice or so back to windows. Don't have all the logs, but got four, also two from yesterday I believe.

The last two are kernel panics I believe, happening after the end call without a call message.

Apart from these random reboots, and occasional SOD's, this kernel runs fine on my rhod100_uk with and EID panel. (no autobacklight, but gotta trace back to a kernel where it does work, guess it's not related to Wistilt's work).
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Might not be 'common knowledge' but manual backlight is broken. Please use autobacklight until manual is fixed.
[Touch Pro2, Tilt 2 Android Development] Naadi900:
Manual backlight broken?

For me autobacklight doesn't do a thing.. or should it be turned on at boot? Cause then I need to try that..

Or do you mean it the other way around? auto broken, manual should be used xD

Thanks anyway!
[Touch Pro2, Tilt 2 Android Development] Jandyman:
Really? Works for me. Only thing is lowest brightness seeting ISN'T the lowest backlight, the first notch for the backlight is the lowest.But this is fine, had this problem always.

Or are you referring to manual backlight in a difference sense?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
No, I mean manual backlight doesn't work properly. You haven't noticed if you set manual bl to 100% and the lock the phone, it gets knocked out? I think there's other issues as well with manual backlight, and auto should always be used until they are fixed. They might be one of the many sources of the SoD's, we're not sure.

I guess I should put that in big bold letters on the first post, please test this kernel with autobl enabled - no manual bl.
[Touch Pro2, Tilt 2 Android Development] Jandyman:
Yeah I have noticed that actually but it never botherd my too much. I usually use lowest backlight level anyway to save battery. I never had any SODs with this kernal yet, but if you think it might cause problems I'll enable autobl
[Touch Pro2, Tilt 2 Android Development] Naadi900:
So to conclude autobacklight should work fine? Wonder how other rhod100 users are experiencing autobacklight. I remember that it used to work, but lately not anymore.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hrm. I keep getting conflicting reports on manual backlight. I always run auto, and WisTilt2 said there's issues with manual backlight.

The issues might simply be that bug at the unlock screen, not sure.

If you guys don't have a problem with manual backlight, use it! Just know that there might still be some outstanding bugs with it (ever since autobl was enabled).
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
Hmmm I new that manual was not prefered, but always assumed that it was automatically set on auto. Maybe I even changed it within realizing. Hmmm it is from now on auto anyway :s yeah might not be a bad idea to put in 1st post.
[Touch Pro2, Tilt 2 Android Development] nasapunk88:
backlight

My manual worked fine for me except i couldnt get below 9% brightness.

I downloaded a brightness control widget from markerplace and using that i was able to bring my backlight down all the way!!

its great for saving battery! it basically lets me completely turn it off nearly which is fine when inside and not in sun.

im no dev but if there was a way to change settings back light controller to the way widget works and it would be perfect then =)
[Touch Pro2, Tilt 2 Android Development] highlandsun:
rilwrapper? Tell me more. I tried using the libhtc-ril from my G1 on my TP2. It worked for dialing but not for data. Also the mic didn't work, but I could hear DTMF tones from the keypad. It would be great to get the real HTC ril working.

Also, on a real Android phone, the data connection seems to be managed as part of the framework and the kernel. On XDAndroid, it seems that the data connection is created using pppd. Would be nice not to need to use pppd if there's in fact an in-kernel driver already available.
[Touch Pro2, Tilt 2 Android Development] Jandyman:
Wow thanks for that. I have troubles with battery time and this should help a lot. Widget is ugly but nothing desktop visualizer can't solve :D
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I know very little on the subject, other than it takes a RIL blob from WinMo and wraps it into Android. HD2 guys do this, they didn't write their own RIL at all... they just wrap the RIL from HTC, which is proprietary (of course).
[Touch Pro2, Tilt 2 Android Development] muziling:
Seems when system is sleeping, plug usb cable, then SoD.
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
another SoD

36 hours after the new data.img 2 more sods, have only one log, which is garbled at the end :S http://pastebin.com/Am8PpFV1
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
SoD means it's impossible to wake the device. Not just the screen takes a while to come up, I mean you've tried everything you can think of for 30 minutes and the panel never wakes again... Right?

Reason I say that is I don't have this problem. I just plugged in USB when it was sleeping, and it acted kinda funny but I was able to wake it eventually. Might want to wake it before you plug in USB.

[32995.179687] END CALL triggered without being in a call!
[32995.179687] This really shouldn't happen

I see those at the end of a lot of your SoD's... odd. WisTilt2 is tracing all sorts of weird crap, plus we're trying to move to .35... seems like we might just want to wait until we are on .35 before pursuing this any more...
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
Ok, will wait for that and hold off on putting up any more logs then. What exactly is the .35 and what should it improve?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Kernel version. We're currently on .27, and if I'm perfectly honest the code seems to be quite messy. Devs are trying to get everything up to .35, with the hopes that we can abandon a lot of old unused code, plus get the benefits of a newer kernel base.

Cotulla is working on .32, but from what I understand a lot of things .32+ are very portable. Not sure when it's going to be "done", but they are making good progress on it. I just don't want to spend a lot of developer time when they're in the middle of a big migration like this. Still lots of things to sort out on .35, so don't expect it like next week... but again, no sense in devs spending time on something that might just be related to bad code on the .27 base.
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
Clear. I'll keep collecting them at home, if anybody suddenly wants to pursue the issue and needs logs just let me know.