yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] rcgators:
One more SOD with 1258 testing kernel. Did not have screen wakeup issues today. SOD occured after moving to a location with marginal 3G coverage. Hope this helps the devs.
[Touch Pro2, Tilt 2 Android Development] shatred:
woops sorry made an mistake there (forgot i was using 1253 again xD).

im gonna test it right now with correct kernel from this thread

Edit* here is the correct dmesg from this kernel:View attachment dmesg1258-FIXED.txt

Edit2*

after the phone being 15 mins on standby i cant seem to wake it up, if i press the wake button the screen gets started up but stays black, i can unlock the screen (i know where the unlock slider is) but after unlocking the screen still stays black...

im going back to 1253 that worked fine for me xD
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
Not sure, I started using xdandroid somwhere arond 1242. I'll try to check this weekend with a new SD to exclude those issues. Oh dear, back to the sys_serv issues :D
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
I switched on my voicemail today, and noticed the same behaviour!
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
new kmesg

Another freeze, had the phone in my pocket.

Log: http://pastebin.com/HUjLtgm3
[Touch Pro2, Tilt 2 Android Development] shatred:
so far the 1258 version released 14/02 works better then the one from this thread, because with this one its impossible to get the screen out of sleep, with the 1258 from 14-02 just press the power button, then hold volume down or up for about 5-6 secs, release the button and the lock screen should just pop-up.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Do you have an AUO or EID panel?

I'm hoping WisTilt2 has these squashed, he was testing some code with F22 last night and it seemed to work well from what I gleaned.

Don't have the kernel yet for public release, hopefully soon tho.
[Touch Pro2, Tilt 2 Android Development] shatred:
Where to find if i hace auo or eid? i provided an dmesg can it be found in there?

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

Sent via the XDA Tapatalk App
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yup, Panel type detected: 13. AUO.

WisTilt2 just said he made another kernel pack - hopefully it will fix the issues with RHOD100/AUO. Please test it!

I have been running it, and when the phone does wake it's less than a second to wake. I've had a couple of failed wakes, and WisTilt2 is convinced those are related to the new .35 fb... need acl to look at it, but he's swamped with other things.

Hopefully this will be more stable for everyone. Try it out, let me know how it goes!

Kernel posted, let's see how this works out for everyone!
[Touch Pro2, Tilt 2 Android Development] Rhodium500:
What sleep mode should we be using with this kernel and no OC. pm.sleep_mode=0 or 1 or 2
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
You bring up a great point that I forgot to mention!

WisTilt2 recommends we go with sleep_mode of 0 for this kernel. He wants to see how much power savings we can get vs. 1. You should never, ever be using 2 any longer unless you're OC'd and on an old kernel. Thanks!
[Touch Pro2, Tilt 2 Android Development] Jandyman:
Okay iv first short-term test for you :)

So far iv noticed a reasonable improvement on last kernal.

Out of about 10 wakes I had 1complete failed wake and 2touch-to-wakes.

*EDIT: yeah the extremly quick to deep sleep has stopped and its bak t normal around 30secs. Same as last kernal.

Keep up the good work :)
[Touch Pro2, Tilt 2 Android Development] Rhodium500:
It would be helpful to mention the sleep mode in the first post.
[Touch Pro2, Tilt 2 Android Development] aberry:
which sleep_mode?

I'm curious, would this apply to regular 1258 kernel also or just these test kernels?

Rhod400 with no OC

Thanks!
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
You can run whatever sleep mode you want, WisTilt2 was just curious if people saw better drain (less drain) with 0 as opposed to 1.

I already did, thanks!
[Touch Pro2, Tilt 2 Android Development] Jandyman:
Well I'm using an ext.2 partition as opposed to ext.2 file (much the same only I personally get better speed with partition) so I didn't have any pm.sleep_mode line in my haret startup.txt . . . . I had 'pmem.extra=1' but I'm not sure what that's for?*removed* . . . . I added pm.sleep_mode=0 anyway :)

EDIT: done and rebooted, having added pm.sleep_mode=0 and it doesn't seem to have any negative effects on the waking/sleeping thus far :)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
pmem.extra is a deprecated command, you were right to remove it. Thanks.
[Touch Pro2, Tilt 2 Android Development] snalbansed:
Going well so far - no issues after a couple of hours. But then again they always seem to be good at first. Will see if it lasts the night! Here's hoping!

Rhod100 AUO
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Keep me posted!
[Touch Pro2, Tilt 2 Android Development] Jandyman:
Okay done the first long-sleep test. Its been asleep for 35 minutes and woke within a second or two. (No touch to wake even) Havnt had that with previous kernals. Although after the first 20 the led briefly flashed orange so I'm not sure if that voids the test.

So far iv havnt had a panel wake kernal which would wake properly after the school to break period (sleep from 8am to 1pm =5hours) Maybe this will be the first :) I'll keep ye updated.

(Also all along my battery life never seemed to be improved the the same extent of others here, hoping the sleep_mode=0 will solve that mystery too)
[Touch Pro2, Tilt 2 Android Development] snalbansed:
11 hours later, still good! Could this be the one? ;)
[Touch Pro2, Tilt 2 Android Development] djcrosstunez:
Much better now, 1 or 2 seconds.

Rhod100_nl
[Touch Pro2, Tilt 2 Android Development] Zombie069:
Testing this with tiad8's froyo. Slept on the charger all night, and woke within 1-2 seconds first thing.

Had wifi on using market, when I turned off wifi, and closed Ti Backup the phone rebooted. Haven't tried to replicate yet but will play with it today.

No flashing green light, and the battery life still doesn't work out too good. I can't make it through a day with minimal phone usage.
[Touch Pro2, Tilt 2 Android Development] codedesignr:
Good at first

Using this kernel with Gingerbread. Very fast and responsive. Wakes mixed. Some instant, some take 5-10 secs. Phone was sleeping well at first. The battery was almost fully charged, went to bed and phone was dead 6 hours later. The light was green when I went to bed, but was steady orange 3-4 hours into the night. I'm using a Rhod400
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hrm... seems like some app woke your phone up, that's really weird. I haven't personally experienced it, but I usually don't leave GB running overnight - not to say that you shouldn't, just that it's very alpha :p.

If the phone isn't sleeping, you won't get good battery life. This kernel went back to a solid green light in sleep. Many causes for reboots, and if you're on FroyoX I'm just going to blame that build - browsing thru that thread, lots of people are having reboot problems with his builds...
[Touch Pro2, Tilt 2 Android Development] codedesignr:
Maybe Clocksync woke it. Have it set to sync every 3 hours and I synced just before I went to bed so that I could check in the morning to see if it was working. I installed it for the first time yesterday.
[Touch Pro2, Tilt 2 Android Development] snalbansed:
23 hours now without a SOD. A couple of reboots, but first one due to signal loss, second due to XDA app giving FC errors (can't have that can we!).

WisTilt2 - you are a wonderful person!

Arrrghhh - you are quite useful too ;)
[Touch Pro2, Tilt 2 Android Development] Jandyman:
Okay I got my 1st SOD . . .BUT I got it on my 1st sleep after installing and enabling 'juiceDefender' the device slept but it den jumped to orange LED (presuming JD is at fault for that) then it wouldn't wake. But juicedefender gave me problems before so its not the kernal that's at fault :)

Also ppl who are having problems with apps waking their device try the 'autostarts' app, use it to disable the problematic apps from auto opening (how I found which apps cause problems was by closing all apps before sleep, then watching untill my device is woken from deepsleep, den unlocking and seeing which apps started, its usually one of these) Also iv found the apps which are under the 'widget' section of autostarts are usually where disabling the accused apps will solve your problem.

Worked for me, hopes this helps some1 else too.

*minimalistic text was one of the apps causing problems in case anyone is wondering (even though I wasn't even using it as a widget . . .)
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
Man..... been running this for 14 hours, and every single time it wakes within two seconds without having to press or slide. Low usage today, but nevertheless. No SoDs, only one time that an outgoing call froze. Wicked!
[Touch Pro2, Tilt 2 Android Development] snalbansed:
Had the first SOD now - in pocket, panel off, orange light on. However - the key thing is whether it starts happening more frequently now - previous kernels that have looked good for as much as 16 hours have gone on to get SOD within hours, then minutes, of being rebooted :(

Time will tell...
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Seems better tho. I'm hoping some of the reboots can be fixed with the battery fixes.

I'm hoping that the SoD's related to charging and the flaming hot device from charging will also be remedied with new code...

I know some reboots seem to be related to low/poor signal zones... hopefully we can get that resolved, it seems like we are going to have to figure out how to use the rilwrapper, because our current RIL has issues...

Glad to hear this kernel is workin better for people tho! I'm betting we'll see this code hit GIT soon. Last thing is the last few failed wakes, we're going to look at pulling the .35 framebuffer commit... might be easier until we go to full .35.
[Touch Pro2, Tilt 2 Android Development] Zombie069:
The phone was sleeping properly, I just remembered reading some post recently about the green light being set to flash now, but that's changed so no matter.

However with this kernal, and sleep=0, I have been unable to receive calls. 6 this morning I'm sitting at my PC dicking with the phone and I could here the tell-tale crackling garbage through my PC speakers when a call comes in. Phone sitting idle at open home screen did nothing. No ring, no vibrate, no indication of a call until the voicemail came through. I tested this 4 times after reboots with my buddies phone on the way to work. Calling my phone would get 4 rings on the dialing phone, but my tilt2 would never even wake, and if it was already awake it would not show any sign of a call coming in.

I switched back to an older froyo and kernal on the fly at work to keep phone usable. Trying now on that version with sleep=0 to see if that is the issue of if it's this kernal's problem. I'll format my spare MC and fresh install with this kernal and check again.

As you don't like froyo much, what do you recommend running? I tried the XD and didn't care much for it, too laggy moving around. Give me a bone.
[Touch Pro2, Tilt 2 Android Development] manekineko:
Give XD FRX04 a try again, and try it with Zeam launcher from the market.

Then you should get good speed and be able to provide useful testing feedback at the same time.
[Touch Pro2, Tilt 2 Android Development] Zombie069:
I'll give it another shot. I have launcher pro that I prefer mostly, but zeam does have some much nicer dock icons. If I could find a messaging widget similar to the LP version, I would be set on Zeam.
[Touch Pro2, Tilt 2 Android Development] Zombie069:
Wrong forum for this I know, but as an aside, I just downloaded FRX04 complete from the site, and it just hangs at the text-line booting screen. Used the contained startup.txt, only changing sleep to 0 vs 1.

Just don't seem to have any luck with this version.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Build issues, please post in the appropriate build thread. Thanks!

On the topic of the phone not waking with sleep_mode=0 - does it work OK with =1?

You have the exact same phone as WisTilt2 and he's been running XDAndroid builds for a long time...
[Touch Pro2, Tilt 2 Android Development] Zombie069:
Yes I know those are build issues, pointed that out and not trying to clutter the test thread with usless garbage.

With my previous froyo, yes it worked with sleep 0, woke everytime, but wouldn't receive a call, didn't try sleep 1 as I needed my phone and reverted to old android folder on MC.

With this XD, don't know yet. Just installed. Sleep 0 now and after 10 minutes use it already woke to black lit screen, swiped and then it appeared. I'll be drinkin beer tomorrow watching the race and will have ample time to play with the phone. Maybe a drunken report, but I'll type slowly. :D

on edit: figured out the hang on boot was lack of calibration. copied and fixed.
[Touch Pro2, Tilt 2 Android Development] shatred:
Running 18-02 for almost 24 hours now and its working perfect! The screen comes up every time, no freezes or reboot and wifi also works for me.

I am using rhod-100 with frx04 and 18-02 wistilt2 kernel.

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

Sent via the XDA Tapatalk App
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
New kernel guys... Ridiculous new developments, all I really need to say is read the first post ;).

RHOD100/AUO folk - really need to be sure this doesn't blow up your phones, so let me know how it goes!

Oops! I've been running the kernel fine, but WisTilt2 said he missed a change of code. I pulled it for the time being, if you did manage to download it in the short time it was up sorry! Grab the new one in a few...
[Touch Pro2, Tilt 2 Android Development] snalbansed:
few...

...
[Touch Pro2, Tilt 2 Android Development] husam666:
any news on battery meter, it should be the next priority :p
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
One thing at a time my friend... one thing at a time. WisTilt2 is working on it, but there's A LOT of things that need to fall into place for it to work correctly. IIRC there will be userland changes as well as kernel changes for the new battery code... please, be patient. I will post public tests as soon as I get them, trust me.

With that said, I do NOT post anything that I wouldn't consider at least semi-ready for public consumption.

WisTilt2 said he'd have the new kernel for me when the race (Daytona 500) is done :p.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Thanks for waiting guys, kernel posted.

Really curious to see if this kills RHOD100/AUO panels - please, let me know!
[Touch Pro2, Tilt 2 Android Development] Jandyman:
Wow . . .holy android-man! :) you really wernt joking with insta-sleep/insta-wake XD gotta say the improvement did way surpass my expectations.

So far every wake has been perfect! And every sleep has been instant . . .not even one second. Its fairly amazing. But time will tell wether the instant transition to deep sleep will continue :) (with previous build the transition was always faster for the first hour or so)

But I'm hopefull :) seems like today was the last day that ill spend watching my fone for a minute after every sleep to make sure it goes to sleep mode ;)

Edit:(reverted back to sleep_mode=1 btw, as stated in first post)
[Touch Pro2, Tilt 2 Android Development] snalbansed:
Posting this from tapatalk on the new kernel, rhod100/AUO panel. When you say kill, what were you expecting, and when?

Has it passed already? Or should I be looking out for SOD later tonight?

I have sent it to sleep and woken it once so far. Pressed power button - instant green light! INSTA-sleep you could say, to coin a phrase!

Turning back on was a bit longer, but the phone had only been on few 30 seconds!
[Touch Pro2, Tilt 2 Android Development] snalbansed:
I have now played a bit more, and I can press the button and get INSTA-sleep and INSTA-wake now. Feels a bit weird!

Now if only I could hear callers on every call, not just 8/10 calls...
[Touch Pro2, Tilt 2 Android Development] Jandyman:
Okay time for my second update on this latest INSTA-kernal! :D

Iv made a interesting observation. You know how in previous kernals the phone wouldn't go into deep sleep while charging? (Causing hot phone and such)

Well I plugged my deep sleeping fone into the charger there and it woke it . . . . .den when the backlight went off and into deep sleep again it continued charging :o

So I tested some more, putting the phone to sleep and waking while charging and everytime it continued charging while in deep sleep mode. (my charger adapter makes a high pitched noise when not charging phone, so i m certain it was charging)

So suppose its also the last time I reboot to winmo everytime I'm doing a long charge :D this is a real milestone kernal, in the final hurdles id say :)

EDIT: also tested if the phone wakes correctly when there is an incoming call and it does, perfectly and right away! :D (I know it did in previous builds but I just taught since this kernal is so awesome I better do an all round test to make sure the developments in the sleep/wake hasn't cause any adverse effects)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Glad to hear you guys got the same as me!!

Jandyman, I noticed this as well. It seems to sleep correctly with GPS... with USB/adb... It's almost too good to be true.

He said he was going to muck around with power management stuff, really amazed at how much progress he made on this new one... Lots of other little bits he wants to torque, then hopefully he can commit this madness!!!

Thanks for the tests guys, let me know if you have any other feedback :D.
[Touch Pro2, Tilt 2 Android Development] Galaen:
Excellent!

This kernel is great news! It has been a while since I have put Android on my device, and I think now is the time to try it again. It has been a while, so I do have a couple of questions.

1) I am guessing that with this new update, we still need to turn off gps to acheive a deep sleep. Is this true?

2) What about overclocking? Is it ok to do so, or is it even necessary these days?

Thanks for all of the hard work!
[Touch Pro2, Tilt 2 Android Development] rpierce99:
I'm doing some testing of battery life while GPS is enabled, but initial testing shows GPS being powered off successfully when sleeping, so battery life should be fine with GPS on, but to be sure I'm going to run it all night with GPS enabled and see how my drain is.

Overclocking is fine, it will drain battery faster obviously, and the necessity of it depends on what you use your phone for, I personally don't find it adds much of anything.
[Touch Pro2, Tilt 2 Android Development] rcgators:
Test results with 2/20 kernel:

Twice the phone woke-up but panel did not light up on an incoming call. :( I was able to swipe to answer the call then I went off/on to wake up the panel.

Almost all incoming calls - no sound until I turn speaker phone on-off. This happens whether the phone is sleeping or awake. This previoulsy was annoying but not frequent.
[Touch Pro2, Tilt 2 Android Development] surge919:
This works great. I've made a few test calls and texts to the phone and so far I haven't seen any issues in that area.

The USB connection continues to work while the phone is sleeping.

Within the last few minutes, when I woke the phone, I lost the Sound icon, but if I slide it left, the sound turns off and I get the sound icon to turn it back on.

I'm almost certain it was there before and I recent lost it, but I'll restart the phone and try again. I'll post any updates.

edit:

I restarted my phone and played around with Google Maps and putting the phone in and out of sleep and the icon is still there.. I'll keep messing with it, but it looks like it just may have been a fluke.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I just tested 10 calls, every time the phone was sleeping. No problems with either of these things...

What pm.sleep_mode are you set to?

Edit - had a couple of calls that the panel did fail to wake on, after probably 30 calls. I was able to swipe and answer the call, of course I was testing on my GV number and I have the call screening on for unknown numbers... Frantically tried to get the panel to wake with the power button, but no joy.

Next time this happened, I thought ah... open the kbd and hit 1. As soon as I opened the kbd, the panel woke. Odd indeed.

However, I never had the audio issue with calls. Also, slide-to-answer always worked...

Well for the GPS to "disable" the phone does need to be sleeping for a little bit. The green LED now shows when the ARM11 collapses, I think things connected to the ARM9 can still be awake for a little bit, but they won't be able to do anything and should collapse shortly. I'm not exactly sure if the green LED displayed both collapsing before or not, I'm a little fuzzy on how that works TBH.
[Touch Pro2, Tilt 2 Android Development] pdawg17:
Yup...on my Rhod400 I have had a few times where the panel did not "wake up" fully...when swiping the blank screen I could "feel" it unlock but it did not "wake up" until I hit the power button to turn it off/on...

In general though I am LOVING the progress and improvements...
[Touch Pro2, Tilt 2 Android Development] rcgators:
pm.sleep_mode=1 Accidently ran with 0 and dialer locked up receiving a call. Glad to see Dev recommends 1 since that's what fixed my dialer lockups with past kernels.

On the sound issue, I usually run in silent (vibrate) mode. After switching to ring mode, volume problem was gone but eventually came back a few calls after returning to vibrate mode. I'll test more tomorrow...
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
So GPS sleep bug is still present... read first post if you want the complete explanation. Sorry to jump the gun on that one guys!
[Touch Pro2, Tilt 2 Android Development] picabiv:
On Topaz works prefect! Thx!!)
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
Will be testing it today; BTW, the previous one I tested over the weekend performed awesomely! One time I just couldn't get it to sleep, but after a reboot it worked flawlessly again. Not 1 failed wake, and NO SoD or other freezes! Batt life was 14h, but with relatively low usage (mode=0). Will try this one with sleep=1 as requested.
[Touch Pro2, Tilt 2 Android Development] electriczbif:
Rhod100_uk, WisTilt2 02/20 Test kernel on FRX04 with 02/10 rootfs, pm_sleep=1:

Goes to sleep instantly, but a have a lot of missed wake-ups (about 50%). Touching the screen in lock button area doesn't make the screen to come back up anymore. I also had missed wake-ups on incoming call, swiping the answer area answers the call without waking up the screen, but after the call I get "Launcher failed to respond. Close/Wait" and missed call icon :confused:

I know it's not the target of this test, but since it was mentioned above, the problem with no mic/speaker on 30% of incoming calls (need to switch speakerphone on/off) still remains.
[Touch Pro2, Tilt 2 Android Development] husam666:
IDK what happened but after 30minutes of sleeping in my pocket, the LED was red and there was no service in a full service area.
[Touch Pro2, Tilt 2 Android Development] Naadi900:
So tried it since last night, all nighht n the charger with no sod, alarm was working. but now i experienced random reboots to windows, sometimes no wake with green light on, keyboard, buttons, nothhing wakes it... what kind of logs can i make wistilt happy? Have a brand new rhod100 with EID panel.

Anyway the instant sleep/wake is awesome!
[Touch Pro2, Tilt 2 Android Development] Jandyman:
I'm noticing that occasionaly the led reverts back to orange for no particular reason and doesn't seem to instantly go back to sleep eithar.

I taught an app might be causing it but the only app activated is voice control (which I never use but have my suspicions about)