yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] großa:
This morning I noticed that the display woke up very fast when my alarm was ringing. I charged the phone the whole night. So the charger was connected.

Somebody else had something like that?

Seems that the panel wakes up faster if the charger is connected.

Sent from my MSM using the XDA mobile application powered by Tapatalk
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yes, microp isn't collapsing when AC or USB is plugged in. Same issue with GPS. So the phone isn't in a "deep sleep" state when you're charging basically... ARM11 is sleeping, but nothing else is. Hence the screen wake is extremely fast. If you hit power and try to wake the phone again in less than 5s, wake will be just as fast - again for the same reason, microp isn't sleeping completely.
[Touch Pro2, Tilt 2 Android Development] Ltilt2:
INSTA-WAKE, INSTA-SLEEP AND INSTA-DEATH...LOL :D

But thanks for all your work. much ass gracias
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
New kernel folks... this one is a doozie.
[Touch Pro2, Tilt 2 Android Development] AkumaX:
I'd be lying if I said I wasn't intrigued by the title of this thread ;)
[Touch Pro2, Tilt 2 Android Development] electricalve:
the insta wake insta sleep (aaarrggh tm) works smooth on my phone ive tried because the 1258 and 1260 kernels gives me an error with my rhod500, im testing this new version.

the wifi seems to be ok

it is weird not to see the whole kernel loading
[Touch Pro2, Tilt 2 Android Development] electriczbif:
Rhod100_uk, FRX04, rootfs 02/24, Wistilt2 02/24 Test Kernel:

Goes to sleep (solid green) in 1 second, wakes up very fast.

About 10% failed wakes on power button press (led orange, backlight on but screen black). Touching the unlock area lights up the screen, but not always (~80%).

30% failed wakes on incoming call. Phone keeps ringing after the calling party hangs up, after 2x pwr button press phone wakes up ok but after unlock I have a message about phone process stopped to respond kill/wait.
[Touch Pro2, Tilt 2 Android Development] snalbansed:
rhod100_uk AUO panel FRX04 24th February test kernel

I put the new kernel in this morning about 9am. I've had three SOD so far :-(

1st on charge, flashing green light

2nd sleeping, solid light

3rd can't remember the light - not long after boot, panel off.

I would put the logs up, but the SYSTEM_LAST_KMSG is now a short text file, 5 lines long. What has happened to the dmesg capture that is GZipped on this kernel? Has it been dispatched in the changes WisTilt2 made tot he boot sequence?
[Touch Pro2, Tilt 2 Android Development] Jandyman:
okay new update while i slept :) awesome! downloading as i type.

Just to be clear we DONT rename the modules to 'modules.tar.gz' do we? (i read in another forum that we had to. . . . . then found conflicting info elsewhere)
[Touch Pro2, Tilt 2 Android Development] rpierce99:
each zImage is coded specifically for the modules file that it comes with, zImage should always be just "zImage" but modules should be whatever format it was in when downloaded, "modules-lotsanumbersandletters.tar.gz
[Touch Pro2, Tilt 2 Android Development] Jandyman:
Thanks that makes sense. I never use wifi anyway so it didn't cause me problems but still its best to have the modules installed just in case :) Also update on the new kernal, No failed wakes yet. No SODs (as in last kernal), new blinking led is a bit distracting but it'll help with debugging so I'll live ;P. It usually blinks green/orange for about 3-4 seconds before turning full green :) Also when you said A lot less white text you wernt joking :o much faster :D

EDIT: okay its all changed new kernal is not working well for me at all now. Now instead of orange/green-full green, it seems to be an blinking green non-stop. On one occasion it went from blinking green to full green but then it wouldnt wake!! i had to slide out the keyboard to force it to orange led then from there i eventually managed to wake it. Also when it does decide to wake it lags the lockscreen. Also turning of the screen is diabolical. .. *press screen off*. . . nothing. . . 5second later-screen dims . ..2seconds later screen turns off blinking LED. Also when i wake my device is unresponsive to touch for up to 2 seconds and is mysteriously laggy and many partial freezes, doesnt even highlight buttons when pressed anymore due to the lag. And last but not least. .. right hang up button doesnt work anymore (have it set to *home then sleep* in spare parts. . it now does so only occasionally.

Hope its a quick fix and youve found what is causing this but for now im most definatly reverting to last kernal which worked awesomely ;)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hrm, not that I know of... I'll have to look myself. What sleep_mod are you on?

Same to you, what sleep_mode are you using?

I'd recommend you try a fresh data.img as well, that's a really odd report. Also, if the green LED never goes solid something is enabled that is breaking sleep... perhaps GPS?

I've been running this kernel all night, been fantastic for me. I haven't had an SoD in a long time tho to be honest. Without logs, I'm not going to be able to do anything tho folks...
[Touch Pro2, Tilt 2 Android Development] Jandyman:
i use ext.2 version for speed, it gives alot less problems then i had with data.img also upon switching back to last kernal everything ran brilliantly again! :) and nope, gps is disabled (as always, never use it) and sleep_mode=1, i changed nothing except the kernal when i switched to new kernal.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
ext2 version of what...? FRX04? You'd have to manually muck with the inits to get that to work. If you're using a neopeek build, that's really unsupported :p.

I certainly haven't had any of those problems you had with this kernel, and considering your setup I can't really say it's a good environment to test these kernels on, as it's so very different from everyone else's environment, including mine and WisTilt2's.

Not that you can't run these kernels, but unfortunately your feedback is going to be useless (no offense, it just is if that's how you're setup).
[Touch Pro2, Tilt 2 Android Development] Jandyman:
FROYO-Bv4, its a very fast/stable rom. Also neopeek builds are made to run on the exact same kernals as ex.2 file builds(XDA) so 'technically' it shouldnt make a huge difference in result. And up untill now iv had

identical

experiences with these kernals when compared to people with FRX04 so i cant understand why that would suddenly change now (il wait and see what results more people are getting)

So i presume my kmsg would be useless? :)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Well I can look at it, but that is a drastically different build. Nothing similar to XDAndroid, AFAIK.

I'd ask that you at least try it on FRX04 to see if there is any problems with it there... I don't have any issues with this newest kernel, and the majority of feedback has been fantastic.
[Touch Pro2, Tilt 2 Android Development] Jandyman:
Okay thats fair enuf, i will install frx04 try the kernal and get back to you. :)
[Touch Pro2, Tilt 2 Android Development] ryannathans:
android was getting slow and bad so i decided to reformat my sd card.

dropped in FRX04, replaced the zImage and modules with these. Replaced rootfs with the one that fixes the FN keys.

After booting it will sit there for a few minutes (very laggy) and then freeze up, as is screen freezes and the top command totally stops on my pc. The connection is down.

Should I post logs and stuff or wait?

(in the mean time i shall have a play with gingerbread)

I had these issues a long time ago and didn't know what i was doing wrong but they fixed them selves.

EDIT: No such issues present in gingerbread :)
[Touch Pro2, Tilt 2 Android Development] Ltilt2:
I have had no SODs since yesteday when I switch to newest kernel.

Droid on my tilt2 is so almost close to being perfect, for me not to use windows. Love it!
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
How did you format the card? I would've tried a new data.img first. On first boot the phone is going to be kinda slow and laggy (lots of background processes running to get everything updated).

Just saw that it doesn't happen on gb. Definitely try a new data.img.
[Touch Pro2, Tilt 2 Android Development] Jandyman:
okay i used a spare 2gb card i had and installed the latest FRX04 on it w/ latest kernal and now it seems to wake and sleep okay . . . blinking green for about 5seconds usually and then solid green.

problems seem to be solved.

That leaves two variables: the fact i was using a different build or the fact i used a different sd. The former being the most likly suspect. This is rather unfortunate :(

But there is a new version of my ext.2 build being released at 22:00 tonit, sp my plan is il install that fresh, and try the latest kernal again before i restore all my setting and hope for the best. If it still isnt working il try my 2nd choice build. Hopefully il get it working.

But if i cant please remember everyone on neopeeks build uses the same repositry of kernals (AFAIK) so if this breaks there sleep/wake and there is no solution it probly should be said before loads of people flood the other forums with problems. :)

sry for the bother :D
[Touch Pro2, Tilt 2 Android Development] snalbansed:
sleep_mode=1

I'd love to, but as I said they aren't right. Have you had a chance to reboot and check your logs yet?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Good on the sleep_mode. I have looked at my logs they look just fine, but I haven't had any SoD's. Another fella on PPCG posted his log, and it only had the first 5 lines in it... bleh. Seems SoD isn't solved, and I'm betting that it is RIL related. Stupid fawkin RIL.

Well I can't really help with builds I don't run. If they have a problem with our kernels (yes they do use our kernels, I know that...) and XDAndroid is fine, then the problem is with their build, plain and simple. Thanks for confirming my suspicions ;).
[Touch Pro2, Tilt 2 Android Development] snalbansed:
Is the system_last_kmsg not created on boot by harvesting the previous dmsg? In which case a SOD shouldn't make any difference to how the file is created? Plus the fact that it isn't gzipped suggested to me there must be a change in the way they are created?

On a related note, apart from dmsg, where are the logs stored in XDAndroid?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
There aren't any stored logs, just logs you can pull from a running system. The only "archive" of logs is /data/system/dropbox...

My last_kmsg logs are still gzipped, I don't get why that would be different at all. Haven't run into WisTilt2 yet.
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
Ok I promised not to jump the gun anymore, but been trying the 24/2 kernel for 15 hours, and no sods, I have a feeling its also better on my battery. One thing I noticed in this kernel and the previous one also is that the lights on the hard keys (end call, menu etc) are on all the time, whether the device is sleeping, or not. Rebooting usually cures it.

Lets see if this one also has a timebomb built in :p
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
The 4-buttons at the bottom of the phone will stay lit if they're on in WinMo. Happens on all kernels until that piece is fixed... so just make sure these lights are off when you boot Android.
[Touch Pro2, Tilt 2 Android Development] Ltilt2:
3rd SOD

after doing so good, I have started getting SODs....I was getting my hopes up
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Failed wakes or SoD? SoD means the phone will not, cannot wakeup. Even if you wait 30 minutes and hit the power button 15,000 times. Does not respond to adb (USB plug in from PC) doesn't do anything at all basically...

The failed wake issue is still present, it's not completely squashed. He had another theory, and I've been testing a new kernel for about 20 mins and so far so good.

I was able to recreate the issue usually pretty quickly my calling the phone. All calls have went thru no prob.
[Touch Pro2, Tilt 2 Android Development] ryannathans:
rhod 110 gingerbread

just got a SOD (light was still flashing though?), perhaps it was GPS related, turned it off and not turning it on again.

During bootup there is some strange activity, there is no where near as much output as there used to be. (so i found out after reading OP)

also at one part it says it cant read lzo_compress.ko lzo_decompress.ko ramzaswap.ko and xcmalloc.ko

then shortly after ends with the blinking cursor where i can enter commands, if i wait about 10 seconds after this is then moves to the XDANDROID logo and then boots normally.

Just another SOD. No gps, I was just putting it to sleep and awaking it on the pattern screen every 30 seconds. (I am overclocking 650000) It won't wake up and i cant ADB

I am watching sleep in top and about 10-15 seconds in it dies.
[Touch Pro2, Tilt 2 Android Development] muziling:
charge with AC/DC cause system die.

logs:
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Phone can't sleep while adb is connected, so you won't be able to 'watch sleep in top' unfortunately.

I guess we need to get logging enabled again, that's unfortunate that you've had so many SoD's. I can't really help much without logs, and logs are disabled basically... d'oh.
[Touch Pro2, Tilt 2 Android Development] Ltilt2:
After rebooting, no SOD
[Touch Pro2, Tilt 2 Android Development] Raul^:
I have kind of strange SOD's with this new kernel. Half of the time android boot up ok but the next restart and when it should show startup animation there is 'nothing', black screen like it was waiting for something. I haven't such issues with previous 22/02 kernel.

And btw it's just me or the input to the screen is a lot slower and seems that there is some lines missing when compared to 'normal' kernels?
[Touch Pro2, Tilt 2 Android Development] eik:
phone seems to wake up fine (although slightly slower than 1 or 2 test kernels ago and sometimes touching help needed).

Have had one freeze so far (orange led, not able to get it activated, phone calls just end up in vm). Tip someone gave to activate it before hooking up the charger and activate before taking it off the charger, not leaving it charging for too long really seems to help there.

GPS fix is good after getting fix in winmo.

Battery life making it a real usable phone now in Android. Well done guys! Things are definitely going the right way real fast.

rhod100uk, AUO
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
First post updated, enjoy the fast sleep ;).
[Touch Pro2, Tilt 2 Android Development] Naadi900:
Sweet! Missed the previous kernel as all of a sudden the one before kept on working for long time. Had a battery time of 18-19 hours before i had to recharge, this is with normal use :) uptime so far 26 hours, no SOD. But had with that same kernel sometimes 3/4 SOD's short after eachother, mainly when travelling i think.

I'll keep you up to date how this kernel is on my eid panel.

Cheers!
[Touch Pro2, Tilt 2 Android Development] Ltilt2:
In sticking with the 2/24 kernel as its been pretty good on me. Will wait for others to feed back on this new one. Thx for all ur work
[Touch Pro2, Tilt 2 Android Development] Jandyman:
Okay tried latest kernal with a neopeek build just in case it mightve fixed the sudden problems with all the 2/25+ kernals . . . . No luck.

But I do have an update for you on that matter if your interested: I posted about how the latest kernals where incompatible with partition builds over in the neopeek forums and a couple more people found that very strange also.

You know how you mentioned wistilt2 is porting his kernals from .27 to .35? Well we're any early commits for this porting added in 2/25?

(Id just like to have as much info as possible before asking someone over at neopeek if they have an idea on how to fix it before the commits are added to git ^-^)
[Touch Pro2, Tilt 2 Android Development] electricalve:
dammit this guy is fast relasing kernels, o dont even have time to report the last one, this kernels areworking better on my phone thant the autobuild site. im thinking to try the nand again with this one to see if i have the same gsm/sd error
[Touch Pro2, Tilt 2 Android Development] scooper:
tilt2 - led always blinking (sleeping) and never solid. can never wake up.

funny the only one that wakes up consistently majority of the times is the insta wake kernel. All the other kernels I've tried, was never able to wake up even once. all SODs.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
WisTilt2 actually hasn't done any work towards .35, that's the rest of the dev team that is pushing us to .35...

What sleep_mode are you using?

Also, without logs, we can't fix anything... thanks.
[Touch Pro2, Tilt 2 Android Development] wmg316:
I tried WisTilt2's kernel on 2/24. Very nice. I ran until right now with zero failed wake-ups! There was one time during the day yesterday where the green-on-sleep was not immediate; it would blink green for 24 seconds and then change to solid green...I reboot and it did not happen again?? Just thought it might be worth mentioning.

I just downloaded and loaded the kernel on page 1 and noticed the module is named the same...is it different than the 24th build? Is there no changes in the WisTilt2 naming convention?
[Touch Pro2, Tilt 2 Android Development] neilson:
What's the latest on Bluetooth work? I know that's probably the most complex thing left on the phone that isn't working at all across any of the Touch Pro 2's(everything else is just tweaking what already works, and only the CDMA TP2's have the 3.5 mm headphone jack that isn't working at all).
[Touch Pro2, Tilt 2 Android Development] Jandyman:
Well this isn't really the thread for this because AFAIK wistilt2 is concentrating on perfecting panel collapse and such. . . . Not bluetooth.

But I heard tiad is doing some tests on it, but I wouldn't hold your breath for it ;) it'll happen eventually :)
[Touch Pro2, Tilt 2 Android Development] Thelightning87:
I am having troubles with waking the phone up, i usually have to try 2 or 3 times.

When it does wake up, the screen backlight is always dimmed, i cant seem to get it fully lit.

Otherwise no major issues.
[Touch Pro2, Tilt 2 Android Development] BigOnes69:
Tether

I have installed the jan 1 kernel on sprint rhodium and made the following observations from the earlier Kernel.

1. Most important to me. Wireless tether for root does not work. It does connect to wifi network. It did not work on earlier kernel either.

2. Video seems to play better, specifically some flash content I was not getting before with earlier kernel posted here. Seems I get a higher frame rate. Is this my imagination?

3. Keyboard back lighting works good. Power consumption is better. But when it goes into sleepmode sometimes reboots into xdaandroid boot screen (not winmo) when you wake it up.

4. AAAarghs making a phone call while on booting on the 3.5 jack does not work, but the usb headset does work. ( I have my own trick. I have a mini usb hub from my touch diamond that i use. I then connect a bluetooth dongle to the 3.5 jack on the hub and I can use my bluetooth stereo headset.)

Final just a few stability issues and fixing the usb tethering I could use this all the time. Thank you.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Glad to hear that the RHOD100's work! I'll adjust the first post accordingly!

The light does dim while typing sometimes, I noticed that if you force a refresh of the kbd backlight, it'll readjust the light. It seems to always start with the dimmest, and then adjust up... WisTilt2 will make it much smoother, this is just the very first implementation.

Just to be sure, can you boot with your kbd backlight off...? I want to see if it inits the kbd properly for the 100's :D

Awesome news, since it's working I don't think I need anything from ya ;)

No clue what that would do. Did you put this in your startup.txt...? Are you running FRX03 of XDAndroid?

Keep in mind the "touch the screen" bug. I've noticed you have to specifically touch the screen where the unlock bar is. Using this method, I've never had an issue with waking the phone. We're aware of this problem as well, thanks :D

Not sure how to answer this post. Wifi tether has nothing to do with this kernel, and it should work. The built-in utility may not, you may have to use the so-called XDAndroid wifi tether, or some have reported barnacle wifi tether from the market works fine. Out of the scope of this thread/kernel test tho.

Video adsp tables have been worked on, so there might be some additional commits in this kernel that the main git tree doesn't have. Entirely possible video playback is better in this kernel ;)

Haven't had a reboot yet, been running this kernel for 12+ hrs now. I've even overclocking... might be an app you have running in your background, I don't have many apps installed TBH. Makes for a cleaner testing palette :D

3.5mm jack/usb headset are definitely out of the scope of this test kernel. Let's try to stick to a few things to focus on with these test kernels, makes things easier on the devs, and me too :D
[Touch Pro2, Tilt 2 Android Development] Bieka:
The init seems to work. I rebooted and the Keyboard Backlight lights up when slided and goes out when closed! Great Work. Only some finetuning and it would be another great step to a perfect port!!! Only Camera and BT left ;) (Ok lights on HW Keys (Endcall, back...) and some little things but these two things are the most important i think).

My thanks are going out to you devs!!! You are doing a great job!!!
[Touch Pro2, Tilt 2 Android Development] JBS2:
Very good job :)

What bout rebooting (android, not back to WinMo) during a call, does this happen with this new kernel?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
That wasn't a kernel issue (AFAIK) that was a system image issue. If you're running a clean FRX03 image without a build.prop mounted from the graphics testing thread, you should never get that issue again.

Not to say that every bug is squashed, but that one has been and an old build.prop resurfaced in the graphics testing thread and this bug reared its ugly head again.
[Touch Pro2, Tilt 2 Android Development] JBS2:
Thanks for your reply. According to this issue I remember it happened before when I was using a clean CAB installation (release before FRX03) which was updated with de update tool.

However, I will try this new kernel :)

I'm on a RHOD100 btw :)
[Touch Pro2, Tilt 2 Android Development] jookdakang23:
Im About to test the New Kernel On my RHod 210 and see if my issue with calling is settled. Whenever i go to make a call in android the screen flashes red and says end call. Does anyone Know WHy this would be?? and good work guys on this amazing port ;)
[Touch Pro2, Tilt 2 Android Development] kurtir:
Great job!! Rhodium 100_UK

Device Rhodium 100_UK, FRX03, pm sleep=1

the keyboard backlight and the wifi are both working perfectly (thank you for that) also the device seems a bit faster.

but the call process is a bit sluggish, and if you enable the speakerphone while making a call you'll get a static noise.

will report tomorrow for battery performance.

yeah one more thing, when booting from winmo the screen flickers during the android animation

Cheers