Develop Bugs

Touch screen doesn't work on any Android builds

I am among a few people who have (for many months) been unable to get any Android builds to work on our Kaisers.. It installs fine and boots properly but the touch screen never ever works. We've tried all the options/screen types/builds/radios/nand & sdcard installs etc... We always get stuck at the "Touch the android to begin" screen and cant get any further.
There was a thread about this in the old forum (which is for Windows Mobile only now) and is still there:
http://forum.xda-developers.com/showthread.php?t=587340&page=4
A few people in this thread offered to try to help but nothing came of it.
I've posted this new thread in the forum in hope that someone can move that thread here and/or attract the attention of any devs/android experts who can help solve this problem. Is anyone out there able to help?
Thanks!

To be useful some more info is needed like:
what build ROM are you using?
Is this NAND or haret?
what version/build have you used?
What version of Kaiser do you have?
I am by no means an expert but I have 2 kaisers(Tilt) and have both working with touchscreens. One is Nand and one is haret.

kendav911 said:
To be useful some more info is needed like:
what build ROM are you using?
Is this NAND or haret?
what version/build have you used?
What version of Kaiser do you have?
Click to expand...
Click to collapse
Thanks for your interest..
I've tried most builds posted in this forum, with both nand and haret.
The most recent one tried (this morning) was a nand install of the latest Polymod 2.1g. I haven't flashed it back to Windows Mobile yet.
I tried it with all three screen versions of KAISIMG-PANEL-320.NBH 2010-02-20 from sourceforge and all got the same result, although Panel1 looks the best.
I used Radio 1.71.09.01, as it was recommended in the polymod thread.
I have a UK model HTC TYTN II. It's the standard HTC one and not from any mobile carrier. The model number behind the battery says KAIS130.
Do you have any ideas?

First, trying shutting down the phone and removing the battery, then hold the power button down to drain any left over power. Replace battery and power it back on and see if that fixed anything.
Second, get kallt_kaffe's kernel. It works the best so far.

Dukenukemx said:
First, trying shutting down the phone and removing the battery, then hold the power button down to drain any left over power. Replace battery and power it back on and see if that fixed anything.
Click to expand...
Click to collapse
I generally do this whenever I change builds/kernels etc.. I'm assuming holding the button down for a minute is enough?
Dukenukemx said:
Second, get kallt_kaffe's kernel. It works the best so far.
Click to expand...
Click to collapse
OK. I've just tried this one with polymod and Incubus26Jc's Super Eclair Lite 2.1 for kaiser [RLS5]. Same result. No touch screen response.
I'm really don't know what could be causing this. I know my touch screen works fine in Windows Mobile.

Hi,
My Kaiser screen works fine.
Panel1 = dodgy graphics
Panel2 = Rotating wrong way
Panel3 = Working fine
My Kaiser was a XDA Stellar and has myns warm donut on it using NAND to internal memory (with wifi update).
Have you tried using the above setup?

XCougar said:
Hi,
My Kaiser screen works fine.
Panel1 = dodgy graphics
Panel2 = Rotating wrong way
Panel3 = Working fine
My Kaiser was a XDA Stellar and has myns warm donut on it using NAND to internal memory (with wifi update).
Have you tried using the above setup?
Click to expand...
Click to collapse
I've tried myns warm donut with kallt_kaffe's kernel and with the latest dzo ones with NAND installs... using all 3 panel types and all the same result.
I did get a single touch to register once with myns/kallt_kaffe combo, but after the first click worked, the screen stop responding to touch again. Maybe it was a weird glitch or something. Anyway, no luck so far...

Ok been following this, and although I have never had this problem, I do have a Kais130 panel2 variant.
I assume from the previous posts that since the touchscreen works in Winmo then it cannot be a hardware problem, as this would affect both android and winmo.
Can you try an NBH from here, http://ponack.net/poly/BT_Update/index.php?folder=S2Fpc2VyX05CSHMvRWNsYWly
And install polymod 2.1G (or D ).
This should give you a known-good install to check with.
Note that once you install polymod you should do the 'skip registration and wait 15 minutes' ritual followed by a shutdown/restart.
Once the phone restarts and goes into the initial boot console, ( scrolling text ), try opening the keyboard and see if the screen flips in response, this lets you know that the screen flex is working, ( or at least mostly working ).
Also note that the initial boot of android on most builds is pretty sluggish at first until everything in the firstboot script has been completed, and sometimes the touchscreen is unresponsive for a while, ( 5 minutes max ).
Also after a reboot there can be a delay before the touchscreen starts to respond, maybe a minute or so, therefore let everything settle down before using it.
However you may have to replace the screen if it simply refuses to work, I know there have been a few cases of non-working touchscreens, but as yet have seen no resolution to this.

zenity said:
Ok been following this, and although I have never had this problem, I do have a Kais130 panel2 variant.
Click to expand...
Click to collapse
Thanks for your interest and help!
I'm pretty sure mine is a panel1, as the other 2 don't look good at all.
I assume from the previous posts that since the touchscreen works in Winmo then it cannot be a hardware problem, as this would affect both android and winmo.
Click to expand...
Click to collapse
I just reflashed to WinMo just to check, and to make sure that I'm not going insane! The touch screen works fine.
Can you try an NBH from here, http://ponack.net/poly/BT_Update/index.php?folder=S2Fpc2VyX05CSHMvRWNsYWly
And install polymod 2.1G (or D ).
This should give you a known-good install to check with.
Note that once you install polymod you should do the 'skip registration and wait 15 minutes' ritual followed by a shutdown/restart.
Once the phone restarts and goes into the initial boot console, ( scrolling text ), try opening the keyboard and see if the screen flips in response, this lets you know that the screen flex is working, ( or at least mostly working ).
Click to expand...
Click to collapse
OK. I've installed polymod 2.1g with KAISIMG-PANEL1-320-ECLAIR.NBH from your link. In the boot console, if I open the keyboard the screen flips upside down and then flips back when I close it.
Also note that the initial boot of android on most builds is pretty sluggish at first until everything in the firstboot script has been completed, and sometimes the touchscreen is unresponsive for a while, ( 5 minutes max ).
Click to expand...
Click to collapse
OK, I did this and waited 5 minutes after it reached the "Touch the android" screen. It didn't respond to touch at this point and I couldn't get any further.
Also after a reboot there can be a delay before the touchscreen starts to respond, maybe a minute or so, therefore let everything settle down before using it.
Click to expand...
Click to collapse
I shut down after the first boot, pulled the battery and held the power button for a couple of minutes. I then rebooted into Android. The power drain seemed to have an effect, as the battery calibration went out of whack and it gave me an empty battery warning, even though it's nearly fully charged. I then let it sit again at the "Touch the android" screen for a couple of minutes. Still no response to touch.
However you may have to replace the screen if it simply refuses to work, I know there have been a few cases of non-working touchscreens, but as yet have seen no resolution to this.
Click to expand...
Click to collapse
I hope I don't have to replace the screen.. Sounds like a lot of hassle and cost!
If you think there is anything else I can do, please let me know!

Ok check your PM's and get back to me

just a thought...
did you try to calibrate the screen.
I know on my phone the calibrate screen app never works.
so I use the pointer location setting in dev tools.
you can set it by going to dev tools>pointer location,
and press and hold the camera button...
then while holding the camera button use the stylus to press
all four corners starting at top left, top right, bottom right, then bottom left,
then top left again.
let go of the camera button and scribble on the screen with your stylus.
if it worked you will see trace lines on the screen.
and if it really worked it will also be directly under your stylus.
if it isn't then start over and try again until it lock correctly.

Hello I had the same problem. I installed several versions of android and nbh files. How I saved the previous versions that had tested. Re-installed previous versions of files and nbh touch scree back to work. Try using this file: kaisimg-panel2-320-24-05-10.nbh
Hope that helps.

@ pokeybloke
Just a question. Did you only flash the new NBH or do you setup a new system too (wipe system & data)?
I had the same yesterday. Flashed a new NBA but leave the system as it was. Bad idea... the touchscreen and no calibration works anymore. i had to setup a new system too.
Or there are some Kaisers which need some different touchpanel drivers. We have 3 different display types so why not there may be some different touchpanel types?
best regards...

I have a POLA100 but I (and apparently a few others) have a similar problem. Around 16 June DZO implemented a unified touch screen driver - after which none of his newer kernels have worked for me personally. I am able to run newer builds on an older kernel, including Froyo, but I miss out on some of the improvements like battery life and memory savings. Perhaps you can try an older kernel dated before 16 June?

[TESTING]LCD panel improvements

Hey ho fellas ,
I was working on adding power management + initialisation/de-initialisation sequence for rhodium´s lcd panel. Till now rhodium´s panel was always on ( initialised ) in deep-sleep aswell those meaning that the display was never de-initialised and was consuming more battery then normal.
I would like that all of you users that are willing to help to test the kernel ( zImage+modules + latest commits included ) and give some feedback.
Test the power on/off sequence, leave it sleeping for ~30mins and unlock it,...then give me here some feedback on your lcd panel behaviour.
zImage + modules ( mediafire or attachment ):
http://www.mediafire.com/?ny18wpc3z8utxrf
Prerequisites:
- Backup your data.img if you have some valuable data on it ( anyway it should not affect it )
- Delete pm_sleep cmd from your startup.txt

What do you mean by this?
Till now rhodium´s panel was always on ( initialised ) in deep-sleep aswell those meaning that the display was never de-initialised and was consuming more battery then normal.
Click to expand...
Click to collapse
Do you mean that although the display is off, the panel is still on? Or am I getting this the wrong way? If you could explain this to me then I am willing to test

Lennyz1988 said:
What do you mean by this?
Do you mean that although the display is off, the panel is still on? Or am I getting this the wrong way? If you could explain this to me then I am willing to test
Click to expand...
Click to collapse
yeah im curious as well because the only time the lcd is on even when the screen should be sleeping is when its in autobacklight in wm.

lilchicano said:
yeah im curious as well because the only time the lcd is on even when the screen should be sleeping is when its in autobacklight in wm.
Click to expand...
Click to collapse
I think that even though it looks like the screen is turned off it still draws power, so this should eliminate that issue allowing better battery life

Yea the way it was explained to me (by the OP on IRC) is that you can't really tell necessairly that the panel isn't being properly de-initialized... I questioned that at first as well.
I played with the new zImage, seems pretty smooth. Had a few hiccups on wakeup, but nothing crazy. Test it out guys, let the OP know how it worked!!

uub11 said:
I think that even though it looks like the screen is turned off it still draws power, so this should eliminate that issue allowing better battery life
Click to expand...
Click to collapse
Yeah, its a little bit hard to explain, but its like you said.
arrrghhh said:
Yea the way it was explained to me (by the OP on IRC) is that you can't really tell necessairly that the panel isn't being properly de-initialized... I questioned that at first as well.
I played with the new zImage, seems pretty smooth. Had a few hiccups on wakeup, but nothing crazy. Test it out guys, let the OP know how it worked!!
Click to expand...
Click to collapse
Yeah, test it out and post your feedback

ReWind402 said:
Yeah, its a little bit hard to explain, but its like you said.
Yeah, test it out and post your feedback
Click to expand...
Click to collapse
I'm at work and can't download off mediafire can anyone either upload here or on rapidshare.

uub11 said:
I'm at work and can't download off mediafire can anyone either upload here or on rapidshare.
Click to expand...
Click to collapse
I uploaded it here on xda, check the 1st post.

uub11 said:
I'm at work and can't download off mediafire can anyone either upload here or on rapidshare.
Click to expand...
Click to collapse
Ha, responded a little late. I removed it...

Does it matter for the testing if you use pm sleep 2 or 1? Just curious. Testing now

Lennyz1988 said:
Does it matter for the testing if you use pm sleep 2 or 1? Just curious. Testing now
Click to expand...
Click to collapse
It would better that pm_sleep has the default value.

Will give this a try as I go about my day today. I don't OC and use pm_sleep=1 yet still get terrible battery life (b/c I'm a power-user, on e-mail constantly). Any positive change will be wonderful We'll see how it goes.

My findings:
- Device does not go into standby, but I used sleep 2, maybe that is the cause.
- The Led keeps blinkin red. (never seen that before on android)
- The device reboots itself.
and a really negative effect is that I lost all my settings... My launcher pro settings, setcpu, whatsapp...

Hi,
As far as i understood there is no way to know exactly is display in standby mode or not?
I did some tests for now with light sensor ON and OFF (in WM) so here we go (PM is set to 2).
With sensor turned ON in WM:
After going standby screen gone completely off, no glow from backlight in dark environment like it was in previeous kernels and here is an answer to my guess above, screen IS truly going into standby. Also I've noticed some strange behaviour, the debugging led which was intended to go green in standby, randomly (i guess) flashes in around 2 Hz frequency with amber and then stays for 3-4 secs and cycleing like this, no green at all. Returning from standby is not OK, after pressing end button screen is not turning on as expected BUT, after touching at the place where unlock or mute sliders should be screen wakes, so i can assume that after pressing end button screen is just not turning on but touch panel does. Wake on call works as before, as like as wake from HWkeyboard slide (both with 2-3 sec delay). Shutdown actually turn the phone OFF.
It seems With sensor turned OFF in WM, phone acts same way.
I was testing with Matthew's RAR - Android v2.2 Froyo: BLAZN from Aug 30, 2010

Lennyz1988 said:
My findings:
- Device does not go into standby, but I used sleep 2, maybe that is the cause.
- The Led keeps blinkin red. (never seen that before on android)
- The device reboots itself.
and a really negative effect is that I lost all my settings... My launcher pro settings, setcpu, whatsapp...
Click to expand...
Click to collapse
1. Try deleting pm_sleep from your startup.txt ( then the default value will be used - i recommend that ) or put 1
2. never seen that on android
Anyway i am really sry for the inconvenience regarding launcer pro, kernel change should not affect those kind of settings :s
solevi said:
Hi,
As far as i understood there is no way to know exactly is display in standby mode or not?
I did some tests for now with light sensor ON and OFF (in WM) so here we go (PM is set to 2).
With sensor turned ON in WM:
After going standby screen gone completely off, no glow from backlight in dark environment like it was in previeous kernels and here is an answer to my guess above, screen IS truly going into standby. Also I've noticed some strange behaviour, the debugging led which was intended to go green in standby, randomly (i guess) flashes in around 2 Hz frequency with amber and then stays for 3-4 secs and cycleing like this, no green at all. Returning from standby is not OK, after pressing end button screen is not turning on as expected BUT, after touching at the place where unlock or mute sliders should be screen wakes, so i can assume that after pressing end button screen is just not turning on but touch panel does. Wake on call works as before, as like as wake from HWkeyboard slide (both with 2-3 sec delay). Shutdown actually turn the phone OFF.
It seems With sensor turned OFF in WM, phone acts same way.
I was testing with Matthew's RAR - Android v2.2 Froyo: BLAZN from Aug 30, 2010
Click to expand...
Click to collapse
Yeah its a common problem for now we are investigating this.
So i have a confirmation that the screen is really powered off?
Anyway guys try putting 1 into pm_sleep or deleting it from startup.txt (i recommend the 2nd choice ).

I ran into an interesting problem however I did not see the previous post...
Several time it went into standby (I assume) and the screen was pitch black meaning the backlight was not on. To get it out of standby, I woul click the end button like normal. after a couple of hours I pulled the phone out of my holdster, and it was abnormally hot. I do not have an overclock and my pm sleep is set to 1. I did not press the screen to see if it would respond so maybe that is what was being mentioned in the last post. None of the buttons would bring it back to life and the LED was amber and solid, where typically it would flash with this new zimage and modules. I will try to get it back to that state and see if I can click the screen even though it is dark. One thing that worries me is the battery though. Could this be damaging to it? Even when I did have it overclocked it never reached that temperature.
Anything else I can do to help troubleshoot?
EDIT: Sorry, forgot to mention I am on a Sprint RHOD400

I'm on the RHOD400 model, no OC, pm_sleep=1
Couldn't really get it to be stable, had to switch back to WinMo for the day (and trust me, that's desperation ). Once restarted in my pocket without any interaction on my part. I would press the end key to turn on screen, and had it auto reboot at that point as well. Also got a "sleep of death" twice and had to restart. While in your kernel I didn't have notification LEDs as well (not even for power events), vs the guy above that had blinking red.
I'm sure you'll get it eventually, keep up the hard work!

Hi!
Any news? Are we gonna wait for new kernel with committed code or it development is stalled?

HELP! Phone doesn't wake up

My phone goes to sleep
and does NOT wake up, the bottom row of buttons and keyboard both light up if I open them or press them.
Help please!

rossle12 said:
My phone goes to sleep
and does NOT wake up, the bottom row of buttons and keyboard both light up if I open them or press them.
Help please!
Click to expand...
Click to collapse
Stock ROM or custom? Any overclocking?
The phone powers up if you soft reset, correct?

Well, I found out it was a small problem with the rom.
It was a custom rom, and I just installed a different one and it works flawlessly.
With the other one, the light sensor did not work either.
Also, I dropped my phone the other day, and a really small spring fell out.
And the back plain on my screen is loose and opens up easily..

Which ROM?

I hate to hijack this thread but i am having the exact same problem. Basically when i put my phone to sleep its hit or mess as to if it will wake. It seems to have started when i flashed Energy ROM. It was terrible after that, so I switched back to the stock ROM available from the HTC website and all seemed well at first. Now its back to hit or miss.
I cant really rule out a hardware issue such as a broken sensor or something because I'm not sure how the mechanics of it work. When i push the power button on top the phone wakes but not the screen I know this because the 4 lights on the bottom light up and the keyboard as well. I can hit the button repeatedly but it doesnt help. At other times it works flawlessly, but usually does not.
Can anyone give me a suggestion as to what it could be, or a way to rule out a hardware issue?

Exactly my problem!
It was perfectly fine for the first day or so before it started crapping out again..
Can someone please help us with this problem?
It's mind consuming and it's making me worry.
Until TP3 is out, I won't get a new phone ):

Well, the problem is discussed in great detail on the internet, but no one can give a definitive answer. ..
I've been a touch pro 2 user for exactly 3 days... My new HD2 from T-Mobile is in the mail... This is a un acceptable flaw with no real solutiion... Good Luck TP2 users....

Good luck to you.
I've had mine for over two years and it was flawless
Just one recent drop determined everything
Although I Must say, it was one hell of a durable phone

Yea, dont get me wrong. I really like the phone. Thats why I'm getting the HD2. Great OS and big beautiful screen. I'm gonna miss the slide out keyboard but I think thats what breaks these phones.
I'm excited that there's the possibility of running Windows Mobile 7 on it.

rossle12 said:
Can someone please help us with this problem?
Click to expand...
Click to collapse
I'd like to try to help. But you never answered my question of what ROM you are on (and which one you tried previously).

I've determined my problem is 100% hardware related. If I open my keyboard and then grab the screen and tweak it while pressing the power button it comes onn 100% of the time. Sux, but at least I know the cause now

djowen6565 said:
I've determined my problem is 100% hardware related. If I open my keyboard and then grab the screen and tweak it while pressing the power button it comes onn 100% of the time. Sux, but at least I know the cause now
Click to expand...
Click to collapse
Every once in a while my phone would turn on and I wouldn't know why
But yeah, I think it is hardware related.
I previously used Energy then went to Jacko's.
Both were perfectly fine, just the upsetting sleep function and light sensor would keep the phone off.

HELP: Same problem Phone not waking up
Hi saw this thread and was wondering if anyone can help me.
I have an HTC Touch Pro 2 for some month now...
Using the following details:
OS Version: 5.2.21887 (21887.5.0.86)
ROM Version: 2.07..401.1 (80303) WWE
ROM date: 02/04/10
Radio ver: 4.49.25.91
stock ROM basically...
THe issue is that the phone doesn't wake or when using it just freezes/hangs.
Not much software/apps installed... and memory is good as well.
I just don't know what's going on...
Help please.
Thanks

rossle12 said:
Every once in a while my phone would turn on and I wouldn't know why
But yeah, I think it is hardware related.
I previously used Energy then went to Jacko's.
Both were perfectly fine, just the upsetting sleep function and light sensor would keep the phone off.
Click to expand...
Click to collapse
I'd agree with the notion that its likely hardware related. I've flashed maybe 10 different builds of Energy over the last 7 months or so, and never once had and issue with the SOD (sleep of death) that I can recall. A bad flash can sometimes happen. But since you flashed another reputable ROM (Jackos), that somewhat eliminates the possibility that a bad flash is the culprit.
You can start from scratch, by running Task29 to format the ROM area of the phone's memory, and reflash the ROM. But this would be just to eliminate the possibility of a bad ROM flash. My gut says that you won't see any different results.
Running the phone "clean" for a while (to see if you still have the SOD) without any software installed or any other modifications will eliminate the possibility that any software or mods are responsible for the issue.

are you sure its hardware related? because my phone started doing this yesterday too...I had an energy rom from october, and it was really buggy. I am only able to keep my phone from sleeping when it is plugged in to some power, so i flashed the newest energy rom and still having the same problem...wont wake up from sleep
EDIT:
I dont see how this can be hardware related because everytime i soft-reset, the screen works again. this problem only happens when the device goes to sleep...

Any overclocking?
As I already mentioned, I never had any SODs on Energy that I can recall, except when using OCT (OverClocking Tool).

I have done no overclocking...I just flashed the newest energy rom like 15min ago...is there anything else I can do or check? it looks like the phone works still, just no backlight...

After flashing the ROM, maybe try running it "clean" for a day or two, don't install any software or do any mods, reg edits, etc. If you still have problems with the phone waking up with a new ROM, and no other software or other mods, than it may indicate a hardware problem.
And be sure to run Task29 before you flash the new ROM, if you don't already do that.

You guys should read the following thread:
http://forum.xda-developers.com/showthread.php?t=648134
You're not the only ones (by any means) with the SOD issue. But it isn't at all clear what causes the issue. Lots of different theories in that thread about various software or ROMs, with no clear solution.
Lots of conflicting info, but some comments on the thread suggest (as I mentioned) that Task29 may help (certainly can't hurt).
moto2000 said:
are you sure its hardware related?
Click to expand...
Click to collapse
Nope, definitely not sure, especially after reading the thread linked above. But as I suggested before, Task 29, try a different ROM, and run it clean with no software or mods, and start eliminating the variables.

[TESTING] .39 Kernel **NEW**

Hey all,
This is a shiny new test kernel from none other than WisTilt2 and jonpry.
***NOTE***
The new acoustic code is in this kernel. If you're not running a system image that supports the new acoustic code, you will lose all sounds! This includes in call audio, speakerphone, everything!!
***********
They have been working hard on getting a new codebase out, and this is a result of their work.
Note - things are going to be broken in this kernel. Most things from .27 will work, the second post will serve as a list of confirmed broken things & workarounds if they exist. Initially I'd like to see what people report, so let me know! If you report a issue that is listed in the next post, put your flamesuit on, you're asking for it.
This kernel is RHOD only. It may boot other devices, but they are untested. Run at your own risk!
This kernel also requires some changes to haret & the startup.txt, which I will outline below.
Steps:
1. Download the alternate haret version (attached). I have found that this alternate version will boot other 'normal' kernels, but you must use this haret to boot this kernel.
2. Add this line to your startup.txt (I added it after the set initrd line):
Code:
set initrd_offset 0x00a00000
3. Download the kernel from the .39 (autobuild service), replace as you normally would, and boot!

Broken Things​
The additional modules are now provided, however wifi is still broken...
adb now works, but the usual indicator in the notification bar is missing...
BT obviously won't work, as the new audio routing code is not in this kernel. It has the standard audio routing from the autobuild.
user.conf files don't seem to be getting processed... Help on this would be appreciated, I'm honestly baffled that the kernel would affect this, but it seems to be.
Overclocking hasn't worked for anyone as of yet. WisTilt2 was thinking the statement is ignored currently.
End call seems to be failing. It's related to the new zoombar enhancements unfortunately... **These are going to be temporarily pulled until the issue is resolved**
Booting on the new HaRET may fail completely. See this post!
Wifi does not work. There's a fix! Thanks to detule & jonpry for it!

DEVELOPERS ONLY​
Now that's out of the way...
There is a public git repo for .39, assuming you want to see the action live!

no wifi no camera...how is this better than other versions? just curious

prexzone said:
no wifi no camera...how is this better than other versions? just curious
Click to expand...
Click to collapse
Newer code base, so presumably old bugs are fixed, new bugs are present.

prexzone said:
no wifi no camera...how is this better than other versions? just curious
Click to expand...
Click to collapse
The .39 kernel is the future, off which all future updates will presumably be based. However, work has just started on it, which is why it's got a lot broken still.
The .27 kernel which we've been using to date is a hacked together mess that is woefully outdated. Froyo and Gingerbread were never designed to work with this old kernel, and as a result, hacks had to be hacked together, and the whole thing is creaky and hard to improve upon.
I personally was looking at developing a driver for the zoom bar to emulate multitouch pinch-to-zoom for Rhodium/Topaz. However, multitouch wasn't added to the Linux kernel until I think .31, so I gave that up for now.
I was also looking at switching our file systems to the much faster ext4 filesystem, but support was not added for that until .28.
So it may not be better now, but it's pretty much our only hope for progress. There are also crashing and other stability bugs that were fixed in newer kernels, that we simply don't have. I also understand that the .39 kernel is faster.

Thank you all! First impressions with my RHOD100/AUO with FRX06:
Instant sleep and wakeup! It seems that the intermediate sleep state led (blinking green) is not available in this kernel, so amber=awake and green=sleeping. Trying to wake up the phone while freezing applications (screen off, amber -- former blinking green) brings up the backlight but not the panel, touching the screen brings up the panel. This is 100% reproducable.
Data works great with hyc's ril2.
In-call audio did not work correctly, but this was also the same with the .27 kernels, a problem which seems to be specific to my phone. Only JB's audio routing code solved this problem completely, I can only hope that this will be integrated sometime in the future.
However, FB and overall android interface did not get faster (which was discussed in IRC). I can say that it is just about the same as in .27. Don't know exactly if the android interface is hardware accelerated, I am going to try the updated GLES library.

prexzone said:
no wifi no camera...how is this better than other versions? just curious
Click to expand...
Click to collapse
Cam does work (sorry about that!), and wifi is being worked on. With modules I've heard it scans, but doesn't connect.
xanathar said:
Thank you all! First impressions with my RHOD100/AUO with FRX06:
Instant sleep and wakeup! It seems that the intermediate sleep state led (blinking green) is not available in this kernel, so amber=awake and green=sleeping. Trying to wake up the phone while freezing applications (screen off, amber -- former blinking green) brings up the backlight but not the panel, touching the screen brings up the panel. This is 100% reproducable.
Data works great with hyc's ril2.
In-call audio did not work correctly, but this was also the same with the .27 kernels, a problem which seems to be specific to my phone. Only JB's audio routing code solved this problem completely, I can only hope that this will be integrated sometime in the future.
However, FB and overall android interface did not get faster (which was discussed in IRC). I can say that it is just about the same as in .27. Don't know exactly if the android interface is hardware accelerated, I am going to try the updated GLES library.
Click to expand...
Click to collapse
Thanks for the feedback! Interesting that you didn't feel any speed boost. I've been having some oddities with severe slowdowns, but when those aren't happening it seems very fast .
You're right about the rest too, I can confirm that I've had some issues where it won't wake properly when the LED is orange - and you're also right that there's not intermediate blinking state, just solid orange or solid green. I need to flesh out the first post .

when boot up, windows found an unknown device "ethernet gadget", where can I found this driver
When SMS in , phone auto reboot

muziling said:
when boot up, windows found an unknown device "ethernet gadget", where can I found this driver
When SMS in , phone auto reboot
Click to expand...
Click to collapse
I said adb doesn't work... I guess I should refine that and say "nothing USB works".
No clue on your SMS issue, sounds wacky. Post logs.

arrrghhh said:
I said adb doesn't work... I guess I should refine that and say "nothing USB works".
No clue on your SMS issue, sounds wacky. Post logs.
Click to expand...
Click to collapse
not USB works ,how to use dmesg to get logs?
May be wifi is the only way
Command in file /sdcard/conf/froyo.user.conf seems not be executed, I add "rm -f /sdcard/fsck*.rec", file not deleted, switch back to .27 kernel , work normal.

muziling said:
not USB works ,how to use dmesg to get logs?
May be wifi is the only way
Click to expand...
Click to collapse
But don't forget wifi doesn't work

I noticed a decent speed up and no stability problems with my short testing. Will do some more testing tomorrow.

Took it out for a little spin on my semi-retired RHOD400. Keyboard repeat bug is still there it seems. I'll post a dmesg dump if it's useful.
http://db.tt/YP4kMo5
-- Starfox

Test in my RHOD100 with my daily working CWM1.8 plus froyo blue :
Sleep and Wakeup works well just like WisTilt2's 4/15 test kernel.
EDGE works.
Still have no incall but outcall works well.
Also i didn't feel faster since i still get some lag when go into drawer of adw, but it is good to see a .39 working in our phone!
Looking forward to wifi!

muziling said:
not USB works ,how to use dmesg to get logs?
May be wifi is the only way
Command in file /sdcard/conf/froyo.user.conf seems not be executed, I add "rm -f /sdcard/fsck*.rec", file not deleted, switch back to .27 kernel , work normal.
Click to expand...
Click to collapse
Hrm, that's interesting the kernel would affect whether or not that file is processed...
Anyways, you can always just pull up a command line and pull logs there, dump 'em to the SD card. C'mon, this thread kinda assumes you know what you're doing. If you don't, you probably shouldn't be mucking with such an advanced things... Thanks!

hmmm phone does not reboot when receiving a sms but it just goes to sleep
else booting is way faster then the previous kernels.
data connection works . wifi idd not.
nothing else noticed yet

Do I need the modules for bluetooth? My BT does not start.

the new...
...kernel .39 killed my wifi, i now get an error

latinohot said:
...kernel .39 killed my wifi, i now get an error
Click to expand...
Click to collapse
Um, did you bother to read the second post (known issues) at all?

screen wont come back on during call

my wife has the att nitro hd, when the screen goes off during a call sometimes nothing including power button will turn it back on. Anyone know of a fix? did the ATT small update fix this?
Actually it comes back on after a long minute or two. Not very helpful if you need the dialpad or keys, etc.
I have just rooted it for her and installed CWM.
I have added a few proximity tweaks to build.prop
gsm.proximity.enable=false (rebooted twice but screen still goes off)
also used the ro.lg.proximity and the mot.lge.proximity (dont recall exact wording) both were set to a value of 5.
I'll have to take alook into the lg hidden dialer menu to see if I can disable this.
I dont like this sensor on my device either, but I have an option in settings to disable it, which makes it bearable.
thanks for the help guys.
I have noticied LG throws together some junky builds, typos, bad english/grammar. Wonky sensors etc. Incorrect kernel build ReadMe's
I thought I recall someone with another device just placing a peice of tape over the sensor. hmmm..worth a try.
cheers.

chrisrotolo said:
gsm.proximity.enable=false (rebooted twice but screen still goes off)
also used the ro.lg.proximity and the mot.lge.proximity (dont recall exact wording) both were set to a value of 5.
Click to expand...
Click to collapse
Congrats. Today, you learned that most of the "tweaks" found at XDA are utter bull****

aremcee said:
Congrats. Today, you learned that most of the "tweaks" found at XDA are utter bull****
Click to expand...
Click to collapse
What about the tweaks that aren't BS? Are they already included in your CM9 builds?

From what I can tell, pretty much the main thing that build.prop is good for is providing information about the system and software (i.e. info about the build). It's not really used much for useful configurations as far as I know.

networks tweaks actually have doubled me download speed.
I still have faith.
but can anyone answer my questions I posted in ICS SLim thread and PM'ed Andasa , no responses yet.
does ICS slim or CM9 have option to keep lcd no during call? and does it work??
what's working not working? I found changelogs but not a working/not working list for CM9.
and has anyone successfully restored a nandroid from ICS to GB without real issues?
thanks guys.

i doubt the ota fixed your issue as the issue is not one that occurs for every nitro.
I can tell you that when I make a phone call they screen stays no.
what's working not working, well, many of us are running it daily with no probs.
as you prolly know, it is a nightly build so a public list of what's working or not isn't rly part of the deal.
i've succesfully restore a nandroid from both slim and cm9 back to the stock att rom and others many many times. dozens.

thanks good enough.
I will have to give it a go.
would you recommend one or the other?
CM9 or slim?
thank you.

well, I like them both a lot. slim is just a trimmed down version of cm9 and i _think_ it does run just a bit snappier........maybe..but it's not wildly different from cm9. I usually switch back&forth throughout the day.

There's no setting in CM9 to disable the proximity sensor, although there may be a way to do it.

We just got a Nitro HD for my wife and her phone also has this issue. I have not gotten to know the phone well enough to try rooting or anything else of that nature, it's pure stock.
When she makes a call the screen turns off immediately after hitting the call button and will not wake up. When she receives a call we get a glimpse of the in-call screen with the various buttons etc but then the screen turns off. If the other party hangs up her screen turns back on, but if she calls something automated, like voicemail, she can't do anything except pull the battery to disconnect.
I've tried putting my thumb over the proximity sensor, hitting all buttons including power, and nothing makes the screen wake up or turns the phone off other than a battery pull.
The phone was running a build from last November when we first got it (V10i?) and today prompted us to update, so I did that hoping it would solve the problem. The phone is currently on V10j, but the problem persists.
Any help?

no driver said:
We just got a Nitro HD for my wife and her phone also has this issue. I have not gotten to know the phone well enough to try rooting or anything else of that nature, it's pure stock.
When she makes a call the screen turns off immediately after hitting the call button and will not wake up. When she receives a call we get a glimpse of the in-call screen with the various buttons etc but then the screen turns off. If the other party hangs up her screen turns back on, but if she calls something automated, like voicemail, she can't do anything except pull the battery to disconnect.
I've tried putting my thumb over the proximity sensor, hitting all buttons including power, and nothing makes the screen wake up or turns the phone off other than a battery pull.
The phone was running a build from last November when we first got it (V10i?) and today prompted us to update, so I did that hoping it would solve the problem. The phone is currently on V10j, but the problem persists.
Any help?
Click to expand...
Click to collapse
If you bought it from a store, get it exchanged for a new one.

actually works much faster on cm9, but therr still should be an optin to keep lcd on during call. i found some free apps that will disable hardware drivers but cant find the name of the proximity sensor driver, only that is named LGE.

Unfortunately it was given to us by a friend after my wife lost her Captivate, so taking it to a store to exchange is probably not going to work too well. As far as I can tell it was never used before we got it--the battery was still in it's own sealed pouch, the texting and driving warning was on the phone, and the phone went through the whole initial setup routine--but they didn't send us the box, I guess to cut down on mailing costs. I was hoping there was a known solution.

Ok, I downloaded two proximity sensor test apps today, but neither showed any activity. On my Captivate I get different readings with Proximity Sensor Finder (market link), but on the Nitro it is stuck at 3cm and it doesn't register anything no matter where I put my hand over the phone.
Can someone whose phone works right try installing this app and make sure that it picks up different readings on this device? OP, if you are still having issues, can you also try this app and see if it is static for you?
Thanks.

Took off the screen protector that they installed at the AT&T store and now the proximity sensor works just fine. OP, do you have a screen protector on your device?

we had an awfully thick one from att. we have since changed it to a super thin one. screen off is not a real problem on cm9, however i feel all devices should have the option to disable proximity sensor/keep lcd on during calls.

It's worth trying to use the warranty on the phone. Even though you dont have the original sales reciept, the phone has been released for less than a year, so no matter when you bought it, it is still within it's year long guaranteed warranty window.
Finished reading the thread, I suppose this post is now irrelevent