yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] trusa1:
Updated kernel 1/26/11, UK RHOD 100:

- lights are reversed

- Ctrl button trigger light instead of FN button (?????)

- caps lock doesn't always show the correct state

- buttons (Caps/FN) themselves are functioning correctly

- wake up working OK. (don't need to touch the panel)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Cool... So does the FN button trigger... nothing? Just curious, I don't have a CTRL button my kbd. Too many damned layouts!

The others are status quo. Thanks for your feedback!
[Touch Pro2, Tilt 2 Android Development] snalbansed:
Have you got a rhod100 with the same panel as all the other models then? If you have been ok with the recent kernels, you must have! Most rhod100s have the alternative panel.
[Touch Pro2, Tilt 2 Android Development] vinceweis:
For me, the following:

I do have to touch the panel to wake up.

Caps and FN do correspond to the correct lights.

Double pressing the Caps or FN, the light turns off after one character but it is still properly locked to Caps or FN; the light does not reflect the current state.

Battery so far seems greatly improved, but too early to tell for sure.

So far, a great improvement.

Phone in my sig.

Edit: after a couple hours, SOD. Could be something else I did.
[Touch Pro2, Tilt 2 Android Development] snalbansed:
But thread title not updated...
[Touch Pro2, Tilt 2 Android Development] trusa1:
FN button working properly, just don't trigger light.

CTRL button working properly (CTRL+X, CTRL+C, CTRL+V).

CAPS button working properly.

Light should be trigger only by CAPS/FN buttons.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yet somehow you still knew... :p

Thanks, I'll fix it!
[Touch Pro2, Tilt 2 Android Development] trusa1:
I don't know what type of panel i have. Can you tell me how do I do that?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I think you have to use haretconsole... Not sure if there's a better/easier way tho.
[Touch Pro2, Tilt 2 Android Development] trusa1:
OK. I found a haretconsole and i have EID panel.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Lucky you! ;) That means these panel improvements should work for ya, no prob.
[Touch Pro2, Tilt 2 Android Development] portreeve:
will this fix sod issues with the tilt2?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Nope. Just improves battery life.

At least there's nothing specific that is in this kernel to address this issue, as far as I know.
[Touch Pro2, Tilt 2 Android Development] benouch:
Kernel Testing

Hi everyone,

First thanks very much for the hard work.

I've been testing this new kernel.

The function and caps keys are working perfecty.

There one little glitch tho.

If I try to lock the caps or the function by hitting it twice. it goes on at the first hit and turns off when hitting the key the second time. As whereas it should stay on until I hit it a third time.

Ben.
[Touch Pro2, Tilt 2 Android Development] benouch:
Hi there,

I'm testing this kernel with pm.sleep=1 and OC @ 716Mhz

And so far my phone is been running for 19 hours and I'm still having 55% of battery left.

It sounds too good to be true.

By saying "improved Battery" are you looking at reaching that kind figure?

Thanks for the great job.

Ben.
[Touch Pro2, Tilt 2 Android Development] dcmedic:
While testing I have found the following:

Tilt 2 with FRX04

1.. The Cap / Func LED's operate as noted above, I have never had a problem with my CAP's or Numbers anyway.

2.. Prior to testing the new kernel (1253-dirty), I was using the current " stable ", you like my visualization of "loosely", kernel. Now with the current kernel I have been up and running for 2 days without a problem, I have installed and removed programs, browsed the internet & market, received and sent email from 2 different accounts, all without a crash or sod. Once I started running 1253-dirty in about 1 hour I had my first "Sleep of Death", restarted then again another SOD. I replaced the kernel and module back to what was working for 2 days without a glitch, and I can't boot it back up. even though I didn't build the data file with 1253-dirty, I built it with the Good 1253. I have deleted the 1253-dirty kernel and module from the sd card and I'm still getting a reference during the boot echo, not loading /sdcard/andboot/2.x.x.x.x.1253.xx.x (x's are fills), then before the boot hangs I see something about the 1253-dirty kernel...

I just thought I would put that out there.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Awesome. Yea, with full panel collapse we should be at WinMo battery levels if not better! Basically the panel was never fully being powered down, and in this kernel it is (unless you have an AUO panel... we're getting there).

bzo got I think 65 hrs on this kernel. This was nearly 100% sleep with the radio on, sync off. So we're getting real close to being able to ditch WinMo on this aspect... now we just need a little more stability, squash a couple of bugs... maybe with some luck full NAND. We'll be there!

I'm not sure what your question is... are you not able to boot any longer? Try to keep zImage/modules files separate - it can be confusing, I usually just append a .camera or .WisTilt2 or whatever and move the kernel/modules to another folder. That way I can go back to them if I want, and I know which kernel belongs to which modules file.
[Touch Pro2, Tilt 2 Android Development] MrPib:
Tried 01253-dirty with FRX04 on my RHOD500, and gave up after my 3rd SOD today. Back to 01247-dirty / FRX03 (previous Wistilt test build).

I've yet to find a build (01253, Froyo X, camera) that was as stable as the one that I switched back to.

As reported above, the LEDs were switched. Was nice seeing them work, though!
[Touch Pro2, Tilt 2 Android Development] dcmedic:
I'm not asking a question. I was just posting some of my test results.

In retrospect I never tried a full format after switching back.....
[Touch Pro2, Tilt 2 Android Development] slapshot30:
Using FRX04 with no OC and latest kernal. Not getting same results as others. Within 30 minutes of boot I am at 28%. What am I doing wrong?
[Touch Pro2, Tilt 2 Android Development] manekineko:
Are you saying that your TP2 is using up 72% battery life in 30 minutes?

Sounds like a hardware problem to me. I don't even use up battery life that fast when everything is on and I'm playing a graphic intensive game.
[Touch Pro2, Tilt 2 Android Development] slapshot30:
Eh nevermind. Android reported a weird battery reading even though I started with 100%. When I booted back into winmo it said 70%, so not quite as bad but still not as good as others are reporting.
[Touch Pro2, Tilt 2 Android Development] Naadi900:
For me the shift/caps button turn on the FN light. But the FN button does not turn on any light.

Everything else seems great in this kernel, including wifi which is broken for me in the main kernel. Autobl doesn't seem to work in any recent kernel for me tho.
[Touch Pro2, Tilt 2 Android Development] trusa1:
Kernel 1/26/11 battery life report:

In sleep mode battery drain about 2% per hour (pm.sleep=1, sync off, EID panel)

I'm using SetCPU OC. 710 MHz and underclocked CPU to 122 MHz in sleep mode.
[Touch Pro2, Tilt 2 Android Development] jmstumme:
RHOD500 hard reboot randomly on FRX04. Does anyone have the last test kernel?
[Touch Pro2, Tilt 2 Android Development] slapshot30:
How can you set an underclock for sleep mode? Is it something you put in the startup txt?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Evidently using SetCPU you can... The phone should put the clock speed way down in sleep anyways, but I'm not real solid on how that works in reality.

Got a new kernel guys, going to post it shortly - fixes the FN/Caps messup, and I think WisTilt2 also included some additional fixes for power management, and further adjusting timings to improve the touch-to-wake problem. Let me know how it goes!
[Touch Pro2, Tilt 2 Android Development] mike92585:
Using the 1/26/11, Froyo X rebooted every 20 mins or so. After charging over night, it never woke up with orange light (constant).

Changed to 1253 kernel. With 1253, no reboot yet. Will report back.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
New kernel works great for me. Only hiccup I've found is if you hit Caps or FN 3x, the LED doesn't reflect the status correctly.

Already been passed on to WisTilt2 - so what other issues are we seein folks?
[Touch Pro2, Tilt 2 Android Development] Jandyman:
i used the pre-update one earlier and now iv just switched to the updated one. The wrong led status for CAPS and ALT is fixed for rhod210 anyway :) although since updating the end call button which should send me tp 'home then sleep' is beng very tempermental. Lags up to 5 seconds before going to home and often rufesus to turn of the screen, the odd time it those turn of the screen as it should there is a lag of about 4seconds before it does so. I didnt have the problem before so it may be an issue with the kernal? same problem when using the end button.

ps. also switched rom from the ancient cyanogenmod6 to vanijeclair which should be faster but isnt with this kernal anyway.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I'd recommend doing testing on FRX04. Why are you on eclair? That's more ancient than CM6...
[Touch Pro2, Tilt 2 Android Development] Jandyman:
because im using neopeeks builds, with ext2 formatted sd. And because the build iv been using 'VaniljEclair V1.6 - CyanogenMod 5.0.8' which is said to be "really fast compared to Froyo" iv also heard it has better battery life. It is also been updated more recently than the cyanogen6 build i was using previously. So today i both changed my build and updated to this newest kernal.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
My point being, if you're doing testing it's best to be on a vanilla XDAndroid build.

Basically we won't be able to help you much if you do have odd issues - like that end key to home. Mine works flawlessly, and instantly.
[Touch Pro2, Tilt 2 Android Development] mike92585:
Testing 1/28/11 Kernel.

With TP2 Sprint, it went into deep sleep with (orange led). Couldn't wake it up, so had to hard-reset. The battery was burning hot..
[Touch Pro2, Tilt 2 Android Development] pdawg17:
R

I have had 1 instance of "dim backlight" after waking the phone so far...I am using "auto brightness" setting...once I put the phone to sleep and woke it again it was fine...
[Touch Pro2, Tilt 2 Android Development] Rhodium500:
This kernel seems to crash android on Rhod500 randomly. I have not updated or installed anything new. Just went from 1253 to 1/28 test
[Touch Pro2, Tilt 2 Android Development] farukb:
try making new data.img with new kernel,maybe some collision with 1253 is causing crashes
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
What was running on the phone? I've had this happen when wifi tethering...

Usually means an app is running like crazy, causing the battery to light itself aflame.

Any specific apps...? I've been running this test kernel for hours and haven't had a single crash or SoD... but I don't have 10,000 apps installed. I just used GV a little bit.

New data.img as suggested above is always a good thing to try.

Plus, I encourage everyone to test this on FRX04 - if you're not, a lot of the weird issues you're experiencing could be related to the build you're using.
[Touch Pro2, Tilt 2 Android Development] Jandyman:
yeah thats fair enough, and if noone else is experiencing the same difficulties than my problems may be cased by my build.

Anyway panel init/deinit is a great breakthrough:) one step closer to android being practicall for full time use. I will change my android build to a fresh one and hopfully that should solve some of my problems.

:cool:
[Touch Pro2, Tilt 2 Android Development] Rhodium500:
I am using standard frx04 android. I have maybe 15 apps installed. None have caused issues and they have been present for a few kernals and builds
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Did you at least try a new data.img?

I literally have not had a single crash. Besides, most 'crashes' are userland. If you get a kernel crashing, then you're rebooting to WinMo (usually) - kernel panic!

You still haven't clarified what exactly you mean by crashing either - FC's? Apps hanging? Reboot to WinMo? Reboot of Android...? Crash could mean anything misbehaving really.
[Touch Pro2, Tilt 2 Android Development] slapshot30:
Can someone post the 1/26 version so see if I get the same issues with that? The 1/28 is giving me pretty bad battery and I just want to make sure it isn't a hardware issue.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
This kernel really doesn't change much between 1/26 honestly... The only change is the mostly fixed Caps/FN lights.

There must be something you're doing differently. Try starting with a clean build, see if it persists.

Also, if you're on AT&T you have a RHOD300 - which is the same device WisTilt2 has... So if anything you've probably got the best device to test his kernels with.
[Touch Pro2, Tilt 2 Android Development] trusa1:
It seems that it works. Check in the attached log these rows:

request_suspend_state: sleep

Sending arm9_low_speed 2

tssc_manager_resume(): ts->use_irq=1

Sending arm9_low_speed 7
[Touch Pro2, Tilt 2 Android Development] Rhodium500:
It reboots to Winmo and it seems to happen when i put it in standby by pushing the top button
[Touch Pro2, Tilt 2 Android Development] dcmedic:
To add to arrrghhh's statement about a new data.img, a full format of the sd card or partition is recommended.

Side note to arrrghhh, the issue with moving back to the older kernel was due to me not formatting, if you remember.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Ah... yes I've had that happen once so far with this kernel. I need to talk to WisTilt2 about it, because I don't think he has the code in there to produce a dmesg after a crash, as viruscrazy's cam testing kernel does...

I've only had one so far, and it was when the phone was supposed to be 'sleeping'.
[Touch Pro2, Tilt 2 Android Development] trusa1:
Using the 1/28/11, to wake up i need to touch the panel. With the 1/26/11 wake up working OK. (EID panel)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Is it every time? I actually found the touch-to-wake issue is better in this kernel...

Better as in the screen comes on sooner than previously - it's not perfect tho.

So if you let it sit, does the screen come on eventually? We're talking about the phone in a sleep state... Thanks.
[Touch Pro2, Tilt 2 Android Development] slapshot30:
Okay thanks. I'll try again with a fresh build.
[Touch Pro2, Tilt 2 Android Development] trusa1:
Yes, we're talking about the phone in a sleep mode and touch-to-wake issue.

It does not happen most of the time, but when it happens it happens repeatedly.

As I said with a 1/26 that does not happen.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hrm. Interesting.

I've had a few more reboots to WinMo too. I'll let WisTilt2 know, thanks.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
TO ALL!!!

Grab the kernel I _just_ posted in #1. WisTilt2 said he missed a few things in the last kernel, and that's probably causing the issue with resets to WinMo.

Basically a timing value on the screen timeout. So please, grab the new kernel and send it thru the ringer!
[Touch Pro2, Tilt 2 Android Development] Rhodium500:
Improvement. No reset on standby so far
[Touch Pro2, Tilt 2 Android Development] m2maynard:
not sure if is because of my startup.txt or something in the new kernel (01/28) but the four lights on the bottom of the phone remain on all the time even when the phone is asleep (with green LED). any ideas what the cause is? Running Rhod300 (ATT Tilt2) in case that helps. My understanding is that the LEDs arent supposed to be constant on with this kernel? correct me if I am wrong?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I guess you're new to Android (on the RHOD) :p

Currently, if these 4-button lights are on when you boot Android, they will stay stuck on. If you boot with them off, stuck off... it's on the list of things to fix, trust me!
[Touch Pro2, Tilt 2 Android Development] randomblame:
yep it's just a silly backlight for buttons we should all have memorized at this point.
[Touch Pro2, Tilt 2 Android Development] m2maynard:
Ok. Simple enough. It is better than stuck up I guess. :)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yet another kernel guys. FN/Caps should be completely fixed, except for ironically the RHOD300/Tilt2. It now has reversed LEDs, until WisTilt2 can incorporate a detection method (which is fairly simple, just needs to be done ;)).

Additional fixes to try and improve touch-to-wake issue. Enjoy!
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Working well here. Hitting End, the screen goes off and the notification LED immediately goes from orange to green. Will see how long it can last in sleep mode... The caps and alt LEDs work pretty much as expected. Nice...
[Touch Pro2, Tilt 2 Android Development] Erikson89:
Does the kernel works with Topaz device, too?
[Touch Pro2, Tilt 2 Android Development] Jandyman:
arrgh you were right, iv solved all my previous problems and hav got the kernal working but there is a problem with the latest updaye.

yesterday:update1 (CAPS/FN backwards!) - this one now works fine besides the touch to wake issue

yesterday:update2 (CAPS/FN corrected :])- this one seemed to solve touch to wake issue and worked like a charm

Latest update: (as of editing) SOD occuring, and screen refuses to come on very often (haptic feedback/vibration still occurs if for example power buton is held but blank screen :(

taught id let ye kno.

Any fix on the way for this issue? :)

currently iv reverted back to update one as unfortunatly id deleted update2.
[Touch Pro2, Tilt 2 Android Development] trusa1:
No, Rhodium only or use at your own risk.

Read the 1st post.
[Touch Pro2, Tilt 2 Android Development] jasonrr987:
So far the kernel is working great on my rhod400 except for a few things.

1. Im getting the wifi error

2. when i enable bluetooth it forces my phone into airplane mode and i cant get out of it.

Is there a non-stripped version of the newest update?

Thanks
[Touch Pro2, Tilt 2 Android Development] JBS2:
I'm using a rhod_100 on the FRX04 release and just tried the newest kernel (01/29). The screen init en re-init isn't working as needed. When I got an incoming call the screen wakes up, but with the home and power button I can't get my screen wake up. You can see it gets on but stays black. I'll try the next one for sure :)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Ok, let's be clear on what we mean when we say SoD - this is a condition where it is absolutely impossible to wake the device. Backlight never comes on, panel never wakes. Sometimes it happens with the LED orange, sometimes green - I've had both situations. But each and every time no matter what button combo I hit the phone was impossible to wake up. This is SoD...

What you're talking about with the haptic feedback I experienced as well, and I already told WisTilt2 about it. Basically you can unlock the phone before the panel comes up, and it gives you 2 blips of haptic feedback - one when you actually unlock it, and then a 2nd one when the panel wakes (usually a second or two later). It's kinda funny, I've also 'caught' the screen showing my swipe 2 secs later. Again, I've already passed this onto WisTilt2 ;).

Even tho this question was answered, I just want to confirm. Use at your own risk - it very well may boot, but there's no code that would help the Topaz - the panel collapse code is RHOD-only, and Topaz doesn't have a keyboard so that shouldn't matter either. Basically you'll get no benefit from running this kernel, if it runs at all ;).

Reboot. RHOD400 here and wifi works perfectly. Dude with a 210 had the same issue - obviously make sure you are removing (moving) your old zImage/modules file and replacing with these - no need to rename either file.

BT doesn't work... in any kernel. Let's focus on what's been changed in this kernel, and not what other things are broken that have nothing to do with the things that have been changed - panel code, caps/FN keys... - we can sort out other issues when it's committed, if you do really think it breaks other features...

This device doesn't work on this kernel, as WisTilt2 still hasn't sorted out the AUO panel issues. I'm pretty sure I point that out in the first post...

Yup...
[Touch Pro2, Tilt 2 Android Development] JBS2:
Not sure why, but after editing my post it was posted as a new one.

I'm using a rhod_100 on the FRX04 release and just tried the newest kernel (01/29). The screen init en re-init isn't working as needed to the phone is quite unusefull. When I got an incoming call the screen wakes up, but with the home and power button I can't get my screen wake up. You can see it gets on but stays black.

Touching the screen does sometimes works to get the screen on.

@arrrghhh: As I can read on the first post, the rhod_100 is a problem child with (re)init the panel/screen... I'll try the next one for sure :)
[Touch Pro2, Tilt 2 Android Development] trusa1:
About screen wake-up speed.

I tried again kernel 1/26 and this kernel is faster than 1/28-29, screen comes on sooner.

Kernel 1/26 need 3 sec. to wake-up.

Kernel 1/29 need 5 sec. to wake-up.

Kernel 1/26 begins with a black screen and after 3 sec. lock screen appears with fast backlight fade-out effect.

Kernel 1/28-29 begins with a black screen and then after 2 sec. gray screen appears (backlight was on), then after 3 more sec. lock screen appears with fast backlight fade-out effect.

Kernel 1/26 is faster and more visual pleasant at least for RHOD100 EID panel.
[Touch Pro2, Tilt 2 Android Development] vnes1984:
Rhod400, FRX04 with 1/29 kernal. Powering on- When led is solid green (sleeping) lights up a little but I have to touch the screen for it to wake. When NOT sleeping, it takes about 2-3 seconds for slide to unlock to appear.
[Touch Pro2, Tilt 2 Android Development] randomblame:
That is because the 1/26 kernel wasn't properly managing the panel - it was still on - hence it "woke up" faster.

edit - that might be incorrect- there were incorrect values in place for the screen timeout and another change was autobl was disabled in 1/26 and is now enabled. All I know is I prefer battery life to wakeup speed.
[Touch Pro2, Tilt 2 Android Development] trusa1:
Thanks for the explanation. I prefer battery life to wakeup speed too. :)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
+1 ;)

So what kind of battery life are you guys seeing? I'm at 70% after 17 hrs... in full sleep at night (sync ON) I got around 1%/hr... very good!
[Touch Pro2, Tilt 2 Android Development] trusa1:
1/29 kernel, sync off: 5 hours in sleep mode drains 4% of the battery life. :cool:
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
That's freakin awesome.

Well, WisTilt2 just needs to get that AUO panel workin and I think his panel collapse work is done! Then proper panel wake, which he has been tweaking - probably just needs a little more adjustment.
[Touch Pro2, Tilt 2 Android Development] pdawg17:
I've been getting a lot of WM reboots with the last few versions...it may be a program I have installed but the 1/26 version did not reboot me at all...last occurrence I had just woken up the screen and within 3 seconds it reset...
[Touch Pro2, Tilt 2 Android Development] slapshot30:
Tilt2, FRX04, 1/29 kernal. VERY impressed with everything on this build, battery seems to be a lot better. Of course, there is the delay with the lock screen showing up but oh well, a battery fix like this is a huge step up!
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
New kernel guys.

Somehow, WisTilt2 says even better battery life... I know, unbelievable.

Better panel wake as well!

RHOD300 FN/Caps still reversed... Sorry.