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?
Related
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.
Hey kiddos.
WisTilt2 wanted to get some more testers for this kernel, so please download and put it thru the ringer!
This is RHOD ONLY! Please, don't ask if any other devices will work as currently it probably will not! Use at your own risk!
UPDATE 5/14/11 Temp test, SOD prevention!
So the newest autobuild has been plagued with an odd SOD condition. WisTilt2 thinks he traced the issue, and he wants people to run this kernel to see if it's SOD-free (compared to the newest autobuild).
WisTilt2 said:
Current git tree, my pm/fb patch with the proc_comm test. Need to see if anyone gets SOD's. Should have very fast sleep and wakes still, leds are like autobuild also.
Click to expand...
Click to collapse
Let me know guys, thanks!
(In this case, I will leave the old kernel - but do please test this new kernel against the autobuild, see if the SOD's disappear...)
Archive:
UPDATE 4/15/11 SCBS integration
This is the new battery meter code that jonpry has been working hard on. To get the full benefits, you'll need an APK and a new rootfs.img. Please see jonpry's thread on PPCG for more information.
So download this kernel, grab the apk and rootfs from jonpry's thread (don't grab the kernel in his thread!) and follow his instructions if you want to give SCBS a spin. I've already noticed a difference, and I haven't generated a model yet. Rule of thumb with generating the model/algo is the more data the better - so go thru a few charge cycles, some heavy use, some sleep - the more usage the better the algo! Enjoy!
Just to be clear - this new kernel only has the updated SCBS code. Nothing else has been changed since the previous 4/4 test kernel.
UPDATE 4/4/11 Minor fixes...
Just an update to the previous kernel, stylus should be fixed (meaning it will boot into landscape again, fix needs to happen in userland) along with the button lights (when keyboard is open, button lights do not light now). Nothing major!
UPDATE 4/2/11 *Hopefully* failed panel wakes are gone!
WisTilt2 said he found and irq that was set wrong... and it was related to the touchscreen - hence the reason touching the screen wakes it! So this kernel seems to wake very nicely for me - how does it for you?
UPDATE 3/31/11
WisTilt2 said:
This fixes the button lights so they go out when you open kbd and they turn on when you close kbd just like winmo. Also fixed the portrait/landscape unlock screen so at boot it should be in portrait so you don't have to do the back arrow trick to switch it.
Click to expand...
Click to collapse
Update: On the button lights, when the keyboard is open - the button lights will act odd... seems the kernel is torn, it flips them on and then quickly back off .
UPDATE 3/30/11 Button lights, PM Rework, kbd flicker/repeat key, and failed wake fixes!!
WisTilt2 has been trying to clean up his code so he can commit - this is working towards that goal. This new kernel has fixes for the kbd flicker/repeat ("stuck") key bug, the failed panel wakes have also disappeared for me - the panel doesn't always wake instantly, but I've never had to touch the screen to get it to wake - it's ALWAYS come up! Let me know, YMMV as always! Oh and yes, the 4-button light LEDs should now work perfectly as well .
Update - ok, might've jumped the gun on the repeat letter thing - but it does seem better... Just not perfect yet .
RHOD100/AUO users - really need to know if this new kernel breaks your phones! I also would like to know if the SoD issue is actually squashed. I haven't had an SoD in forever, so to those who have recently, let me know!
Perhaps also good to note, is the sleep LED is changed in this one. Initially it will blink green to show that processes are going down and it's trying to sleep (a wakelock of some sort is present in other words). Solid green is full, deep sleep. So you should see blinking green when charging, with GPS enabled etc. You won't get a solid green LED until it's completely sleeping, as usual.
In addition, WisTilt2 has changed the boot screen. Hopefully it'll boot faster, but you'll see a lot less flying text - don't panic! It's normal .
Enjoy! Please feel free to report how this kernel works, so we can get the changes committed!
**Notice**
These kernels are meant for testing purposes - there is no public GIT repo that this kernel code resides on, however the majority of the changes get pushed to the master GIT repo for XDAndroid. The ones that don't didn't work or were simply in place for testing - again the changes that are being tested here are eventually destined for autobuild. Please contact me if you have any technical questions related to this kernel, I will do my best to explain the changes - if you want specifics, I can put you in contact with WisTilt2, the man in charge of pumping out these test kernels. Feedback is not only welcomed but encouraged, please reply to this thread with it!
Downloading and testing now...
UPDATE: Sorry this is taking so long but strangely I've had 5 boots in a row that have resulted in that slow, 100% cpu issue...I've never had that many in a row but can't say that it's the test kernel...I'll keep trying...btw is this built off of the 1245 kernel or an older one?
Yep, testing now.
Incidentally, with both this and 1245 I cannot seem to boot my neopeek system. They fail to see the root partition at /dev/mmcblk0p2 and either hang or reset.
The 1242 kernel still works fine . Weird
Anyway, I will test this out with my XDAndroid setup.
Cheers!
Sorry to be an echo of the others... before I test it, is it built from the 1245 kernel?
1245 seems to be working sweet for me so far....
This should have all the newest commits + WisTilt2's modifications. He said all but bzo's latest commits... I guess git died on him. I'll upload a new one if he builds another.
First impressions on Rhod400:
Speakerphone volume is still fairly low for my taste...when the volume setting is at 1/3 it is barely audible...at full I have to hold it fairly close to hear all words clearly...
Also there is a lot of background "noise" when the external speaker is on...sounds like white noise or static...
Otherwise everything is running smooth...
New Test Kernel (WisTilt2) - 2nd edition - Rhodiums Only
Info: WisTilt2 has another test kernel he'd like some helpful volunteers with rhodiums to test. This test kernel is based on the previous test kernel posted by Arrrghhh earlier in this thread. In addition, it adds bzo's overclock with pm.sleep_mode=1 patch for even better battery life when you're overclocking. So set pm.sleep_mode=1 in your startup.txt when trying this, regardless of whether or not you're overclocking. It also adjusts the volume level of the speakerphone mic to make it easier to hear. Please report any problems you encounter with these kernels, including but not limited, to battery life and speakerphone. Please also mention your rhodium model. They may not all behave the same. Thanks.
WARNING: This kernel is for RHODIUMS only. This kernel could potentially -BRICK- a non-rhodium. So only try this out if you have a rhodium.
Wifi:There is a possibility that rhodium wifi is broken in the stripped version. (WisTilt2 and I use different toolchains. He built it, I stripped it to reduce its size. Our toolchains should theoretically be interoperable, but the resulting modules file is half the usual size. So I'm not entirely sure about that.) If rhodium wifi doesn't work with the stripped version of the modules file, please give the fatter non-stripped version a try. Either way wifi isn't what we're testing here.
Rhodium Only - Kernel & Stripped Modules File(1.94MB version):
wistilt2-kernel-pack-stripped.zip
Rhodium Only - Kernel & Non-Stripped Modules File ("fatter" 8.69MB version, grab this only if you use wifi and the stripped version doesn't work):
wistilt2-kernel-pack.zip
@pdawg17 the static is expected atm, but how loud is it compared to the actual call. same volume or pretty quiet?
People that post here, make sure to specify which model you have, eg. 100, 300. If you don't know you likely shouldn't be testing experimental kernels.
F22 said:
Info: WisTilt2 has another test kernel he'd like some helpful volunteers with rhodium owners to test. This test kernel is based on the previous test kernel posted by Arrrghhh earlier in this thread. In addition, it adds bzo's overclock with pm.mode_sleep=1 patch for even better battery life when you're overclocking. So set pm.mode_sleep=1 in your startup.txt when trying this, regardless of whether or not you're overclocking. It also adjusts the volume level of the speakerphone mic to make it easier to hear. Please report any problems you encounter with these kernels, including but not limited, to battery life and speakerphone. Thanks.
WARNING: This kernel is for RHODIUMS ONLY. This kernel could potentially -BRICK- a non-rhodium. So only try this out if you have a rhodium.
Wifi:There is a possibility that rhodium wifi is broken in the stripped version. (WisTilt2 and I use different toolchains. He built it, I stripped it to reduce its size. Our toolchains should theoretically be interoperable, but the resulting modules file is half the usual size. So I'm not entirely sure about that.) If rhodium wifi doesn't work with the stripped version of the modules file, please give the fatter non-stripped version a try. Either way wifi isn't what we're testing here.
Rhodium Only - Kernel & Stripped Modules File(1.94MB version):
wistilt2-kernel-pack-stripped.zip
Rhodium Only - Kernel & Non-Stripped Modules File ("fatter" 8.69MB version, grab this only if you use wifi and the stripped version doesn't work):
wistilt2-kernel-pack.zip
Click to expand...
Click to collapse
Hey just to report back both kernels do not load it keeps saying that the sd card didn't mount then when I go back to an old kernel it works perfectly so i didn't even get a chance to test the new kernel. Hope it can get fixed so I can start testing for you guys. Thanks and sorry about the bad news
I have RHOD100_de with pm.sleep=1
Well i can say that:
1) The screen is not coming back from stand-by, it remains black while i will nor swipe the unlock pattern (from left to right). It was so on the first stages of kernel with screen turn off feature. UPD: actually screen backlight turns on, but screen doesn’t come back from black...
2) WiFI shows error
3) The in-call/speakerphone volume seems OK
4) Auto backlight function seems to be OK, since it was OK in other kernels.
5) unfortunately currently I don't have enough time to check how battery usage is, i will try to post later.
If You say me on what exactly to focus i'll give more info
So far testing the Rhod kernel:
1) Wifi shows "error" with stripped or "fat" module...I have never had a problem with this on past kernels...
2) In-call volume is great...speakerphone volume is still low to me...the "noise" is lower/better than before but it was be nice for the voice to be a bit higher as in WM it is definitely louder...
3) A couple of times when I woke the phone from sleep the screen was very dim and did not adjust...it was like the auto backlight did not kick in...
4) Sleep mode=1 with my overclock is fine so far...it has woken up all 20 times or so...
5) Occasionally when waking the phone everything is slow/stuttery for a few minutes afterwards...this has occurred the last 3 kernels or so...
I'll keep it running today to see how battery life is...
Otherwise it is great! I'll keep testing!
UPDATE: Just realized my data at some point stopped working too...turning airplane mode on and then off fixed it...
UPDATE 2: Weird...once I did the airplane mode trick my wifi now works AND immediately the stuttering/slowness disappeared and my smooth phone is back!
Rhod400 (Sprint TP2)
Rhod 400. LED is not solid green but occasionally will turn on/off. SOD occured after sleeping for 30 minutes. Speakerphone is much louder but still has static
pdawg17 said:
Downloading and testing now...
UPDATE: Sorry this is taking so long but strangely I've had 5 boots in a row that have resulted in that slow, 100% cpu issue...I've never had that many in a row but can't say that it's the test kernel...I'll keep trying...btw is this built off of the 1245 kernel or an older one?
Click to expand...
Click to collapse
This isn't built off of 1245. I believe it's built off of 1238 with WisTilt2's modifications on top as well as some of the newer patches like 1239 and 1241 added into the mix. I don't believe commits 1243-1245 made it into this test kernel.
Rhodium 100 Panel Issue
solevi said:
I have RHOD100_de with pm.sleep=1
Well i can say that:
1) The screen is not coming back from stand-by, it remains black while i will nor swipe the unlock pattern (from left to right). It was so on the first stages of kernel with screen turn off feature. UPD: actually screen backlight turns on, but screen doesn’t come back from black...
Click to expand...
Click to collapse
Most rhodiums have an EID panel. Some rhodium 100's however have an AUO panel instead. The kernel doesn't properly initialize the AUO panel yet, it only worked before because Win Mo set it up and the kernel never fully turned it off. So now that the kernel is turning it off some rhod 100's aren't waking up. This issue isn't limited to just this test kernel, but exists in all recent kernels. ACL is working on getting the init info for your panel into the kernel. Hopefully it's just the two panels. Should there be a 3rd panel out there it will still be screwed until we can get a volunteer to grab the panel init info from it via haretconsole for us.
2) WiFI shows error
Click to expand...
Click to collapse
Both the stripped and non-stripped versions of the modules file? And are you getting the same stuttery slowness that pdawg17 is experiencing?
3) The in-call/speakerphone volume seems OK
Click to expand...
Click to collapse
Good. That was one of the new things in this test kernel.
4) Auto backlight function seems to be OK, since it was OK in other kernels.
Click to expand...
Click to collapse
Good.
5) unfortunately currently I don't have enough time to check how battery usage is, i will try to post later.
Click to expand...
Click to collapse
Get back to us on that one when you can. That's one of the new modifications that WisTilt2 is specifically testing in this kernel.
If You say me on what exactly to focus i'll give more info
Click to expand...
Click to collapse
Battery.
SD Card Issue
thomas d said:
Hey just to report back both kernels do not load it keeps saying that the sd card didn't mount then when I go back to an old kernel it works perfectly so i didn't even get a chance to test the new kernel. Hope it can get fixed so I can start testing for you guys. Thanks and sorry about the bad news
Click to expand...
Click to collapse
Back up your data via Titanium Backup (downloadable from the market) and try renaming your data.img file to something else. Android will recreate it the next time you boot and hopefully your sd card issue will be gone.
Stuttery Slowness
pdawg17 said:
So far testing the Rhod kernel:
1) Wifi shows "error" with stripped or "fat" module...I have never had a problem with this on past kernels...
2) In-call volume is great...speakerphone volume is still low to me...the "noise" is lower/better than before but it was be nice for the voice to be a bit higher as in WM it is definitely louder...
3) A couple of times when I woke the phone from sleep the screen was very dim and did not adjust...it was like the auto backlight did not kick in...
4) Sleep mode=1 with my overclock is fine so far...it has woken up all 20 times or so...
5) Occasionally when waking the phone everything is slow/stuttery for a few minutes afterwards...this has occurred the last 3 kernels or so...
I'll keep it running today to see how battery life is...
Otherwise it is great! I'll keep testing!
UPDATE: Just realized my data at some point stopped working too...turning airplane mode on and then off fixed it...
UPDATE 2: Weird...once I did the airplane mode trick my wifi now works AND immediately the stuttering/slowness disappeared and my smooth phone is back!
Rhod400 (Sprint TP2)
Click to expand...
Click to collapse
The stuttering slowness means system_server was running amok on your handset. When it goes berserk, it puts a stranglehold on the cpu, preventing wifi and other things from getting their fair share of resources. This issue has existed for months, but it used to be much less common. It appears to be occurring far more frequently in newer kernels with the latest system.ext2.
Thanks for the feedback!
Sleep of Death
vnes1984 said:
Rhod 400. LED is not solid green but occasionally will turn on/off. SOD occured after sleeping for 30 minutes. Speakerphone is much louder but still has static
Click to expand...
Click to collapse
Has the SOD occurred again since? Have you experienced this problem with any other recent kernels? Has anyone else experienced Sleep of Death with this kernel? (Not counting rhod100 users whose panels won't reinitialize after going to sleep. That's a separate issue.)
LOL, thanks for takin care of mah thread F22
Not much for me to do there tho
F22 said:
until we can get a volunteer to grab the panel init info from it via haretconsole for us.
Click to expand...
Click to collapse
Already uploaded to ppcgeeks.
And I did some more testing:
1) I've renamed data.img file and commented lines in froyo.user.conf (from tiad8's 3D Package post) to have a clean system.
2) Tried with stripped modules: Wifi shows error.
3) Deleted this newly created data.img file and tried to boot with not stripped kernel modules: Wifi seems OK.
As told pdawg17 screen lights up, then dim out. Sometimes it is working OK. This behavior exist either with autobacklight enabled or disabled.
Still not enough time to check battery :-(
F22 said:
Has the SOD occurred again since? Have you experienced this problem with any other recent kernels? Has anyone else experienced Sleep of Death with this kernel? (Not counting rhod100 users whose panels won't reinitialize after going to sleep. That's a separate issue.)
Click to expand...
Click to collapse
I haven't experienced this with other kernals. well for awhile. I've since updated to the most recent kernal after the SOD. (working very well btw) It seemed the test kernal had very inaccurate battery readings compared to other kernals. I would hit the power on button to wake and the screen would flicker slightly, it wasn't until I swiped my thumb across the bottom of the screen that the phone would wake up. Once I left it sleeping for about an hour and tried everything to wake it up but no such luck. (rhod400)
I flashed about 2 days ago from stock to RHD 4 Beta 1, hoping that the problem will solve.
Problem is, that very often I would say, when touching the screen and even the 4 buttons it doesn't take the command.
Sometimes if I am quick enough, I press 2 times and still not receiving feedback, so I would say it lasts from 2-3 seconds and if I continuously use the screen, about 4 times per minute.
That is very annoying. It happened also in ROM stock and also now.
Anybody had that? Any ideas ?
That doesn't sound like a common issue, and it's possible you might have a hardware defect with your phone.
I'd flash it back to stock, or as close as you can find, and take it back to wherever it was purchased for a replacement or repair.
raulttro said:
I flashed about 2 days ago from stock to RHD 4 Beta 1, hoping that the problem will solve.
Problem is, that very often I would say, when touching the screen and even the 4 buttons it doesn't take the command.
Sometimes if I am quick enough, I press 2 times and still not receiving feedback, so I would say it lasts from 2-3 seconds and if I continuously use the screen, about 4 times per minute.
That is very annoying. It happened also in ROM stock and also now.
Anybody had that? Any ideas ?
Click to expand...
Click to collapse
mine does the same with stock, but its not that common it happens like once a week for like 2-3 secs, and you dont need to have apps running, i just took it as it is
I m having no such issues in my DHD and i have used ARHD since very early versions.
Are you using any programs like setcpu or cpuspeed? Which kernel are you using?
If you have your htcsense account on, it would be a better idea to turn it off as well. And finally you can recalibrate your G-sensor (settings ---display)
I did some test with more ROMs. I can confirm that it happens frequently with Stock, Revolution HD 4.0 and LeeDroid 2.3.4.
I also flashed the CM7 Rom and I didn't had that problem, but it was only for test purpose as I still wan't to use HTC Sense.
So it's clearly soft related issue. Something must do this delay. As i am handling very fast everything I use, for me it is not acceptable.
I don't use cpuspeed or setcpu
Kernel is: 2.6.35.10-g4a4b278 ( Wed 16 Feb 2011 )
I don't use HTC Account. Reclibration doesn't help.
I don't think it's a performance problem, because all runs smoothly and it happens regularely exactly after restart ( when processes are starting loading etc ) and when no application runs in background and CPU / RAM is not being heavily used.
I see you use ADHD 2.0.15 and you also tested ADHD 4 beta 2, what I am actually using.
How would you compare those? I assume you don't have the problem.
Ah! ok...it is really a strange problem though, i would say. I never had this issue being touch unresponsive.
Yes of all the ARHD builds 2.0.15 is the best one, IMO. Well, the GB build is still in beta and it lags. The battery life is claimed to be slightly better though. But i could not live without search function (which FC all the time), the tweaks we have for Froyo builds and the overall user experience with froyo is just awesome...and Mike has done great job. At the moment the version i m using is priceless...
Hi,
I have this problem where the screen doesn't respond to my touch for a few seconds.
It's not all the time, but when it happens, it is like it for a while.
My phone is on Orange UK and has not been rooted. It is just as from the factory with apps added.
I will be interested to find out if this is a serious problem or just a minor glitch as it seems to be for me.
Matthew
MattOsprey said:
Hi,
I have this problem where the screen doesn't respond to my touch for a few seconds.
It's not all the time, but when it happens, it is like it for a while.
My phone is on Orange UK and has not been rooted. It is just as from the factory with apps added.
I will be interested to find out if this is a serious problem or just a minor glitch as it seems to be for me.
Matthew
Click to expand...
Click to collapse
You have a similar problem as mine, but not so often.
What do you mean by a serious problem? It depends if it is disturbing you or if you can live with it. It won't get worse as I've seen it is not a hardware problem.
You can do the test by installing CM7 ROM and check if it does again. For me that solved the problem, but as I like to use HTC Sense, it is not an option to stay on the CM7 ROM.
raulttro said:
I did some test with more ROMs. I can confirm that it happens frequently with Stock, Revolution HD 4.0 and LeeDroid 2.3.4.
I also flashed the CM7 Rom and I didn't had that problem, but it was only for test purpose as I still wan't to use HTC Sense.
So it's clearly soft related issue. Something must do this delay. As i am handling very fast everything I use, for me it is not acceptable.
I don't use cpuspeed or setcpu
Kernel is: 2.6.35.10-g4a4b278 ( Wed 16 Feb 2011 )
I don't use HTC Account. Reclibration doesn't help.
I don't think it's a performance problem, because all runs smoothly and it happens regularely exactly after restart ( when processes are starting loading etc ) and when no application runs in background and CPU / RAM is not being heavily used.
I see you use ADHD 2.0.15 and you also tested ADHD 4 beta 2, what I am actually using.
How would you compare those? I assume you don't have the problem.
Click to expand...
Click to collapse
Just a really wild guess, which launcher are you using? As I'm using launcher pro plus and it has a tendency to freeze after restart and the screen has no response for a while, usually it force closes automatically and restarts instantly after and works perfect. I'm on CM7 latest nightly and haven't tried other roms for a while so it might not be comparable. So if you are using launcher pro then try to manually restart it if it doesn't force close itself and start again. And if you're not, well just ignore this
Hey everyone,
I'm currently running the latest Jackos and I believe everyone was fine with the speaker you hold to your ear in conversation until about 2 weeks ago. Maybe a week or so after I installed the newest Jackos. Now I can't hear anything on it, but the microphone works fine. Speakerphone works fine, and my bluetooth earpiece works fine. I've searched for help on this and can't find anything to fix this problem.
The other problem is right when I boot the phone, instead of getting the black screen with the red diagnostic text, I get a white screen with colored speckles all over the screen. The speckles don't move at all and if I let it sit for 20 seconds or so, it will then show the HTC logo on black and continue booting. I can't get into the bootloader, I can't hard reset the phone, etc. Any ideas how to fix this? I haven't tried flashing the same/another ROM yet, but I don't know if that's even possible with this snow screen problem.
I've run Task29 and all the usual stuff every time I've flashed and I have never seen this happen until a couple of weeks ago. It does it NEARLY every time I soft reset or shutdown and boot or pull the battery and boot. The battery charges fine and it runs fine otherwise.
The screen will get random glitches in it, even when the battery is full and it makes me suspect maybe the battery's going bad but it'll run all day without problems and it doesn't get warmer than usual or anything like that.
Also, sometimes it says there's no SIM inserted and I've pulled it out, the contacts are nice and gold and nothing seems wrong.
Any ideas?
My sig is out of date but I have to head out right now and can't switch it yet, but it's the latest Jackos with 6.5.
Thanks,
Eric
I would flash a different/stock ROM and see if anything changes.
If no, hardware problem. If yes, software problem .
You seem to think you cannot, but AFAIK if you can task29, you can flash a ROM. Either way, putting an nbh on the SD card and doing power+vol up+reset should work regardless, unless the device is really bricked - in which case it wouldn't be booting.
Okay thanks, I'll see what I can do with it.. It does boot fine, though for a week I thought it was bricked because of the snow, but I decided to just let it sit for a week and gave it a shot, and poof! no snow on the first boot. It had the regular red text on black. Then I reset it from the slide to reset menu item and it went to snow again. I let it sit there and about the duration that it would be on the diagnostic screen, it was snow, then magically showed me the HTC logo and booted normally.
So it seems to me that it somehow doesn't want to show diagnostic info but does everything else.. So maybe the bootloader mode IS working, I just can't view that. I'll see what I can do.
Does the screen corruption/no sound in earpiece seem like a ROM issue, or battery related, or phone going bad problem to you?
And I've been looking for a while trying to find a suitable replacement, but haven't seen anything that I really find appealing (either in Android or WP7).. Any thoughts on that?
Thanks again,
Eric
shep2112 said:
So it seems to me that it somehow doesn't want to show diagnostic info but does everything else.. So maybe the bootloader mode IS working, I just can't view that. I'll see what I can do.
Click to expand...
Click to collapse
Flash stock, it re-flashes everything... Make sure it works, then flash back to Jacko's.
shep2112 said:
Does the screen corruption/no sound in earpiece seem like a ROM issue, or battery related, or phone going bad problem to you?
Click to expand...
Click to collapse
This is what we're trying to troubleshoot .
shep2112 said:
And I've been looking for a while trying to find a suitable replacement, but haven't seen anything that I really find appealing (either in Android or WP7).. Any thoughts on that?
Click to expand...
Click to collapse
Talk about loaded questions! I haven't found anything that's appealing with a hardware keyboard yet... The supposed TP3 (on Sprint it's the "Arrive"...) was a real disappointment.
MT4GS looks decent, if you can live with tmo...
Thanks for your replies, I'm going to try to flash to stock in a little while and see how that goes.
The new Glide phone that AT&T has sounded promising until I read a review of it. Slow camera, 480x800 on a larger screen, etc. It didn't seem as cool as I had hoped it would be after that.
I'll write back with my progress or lack thereof with this TP2.
Eric
I installed HTC's official AT&T ROM and the screen corruption seems to be less extensive but looks different too. The snow at startup is still present though.
There was a radio that came with Jackos ROM, is there any chance that's to blame? Though it worked fine for a couple weeks before these weird screen things started happening.
I haven't tried making a voice call yet to test the earpiece/earphone/loudspeaker or whatever the proper name is for it but since nothing else is really 'fixed' I'm not sure it will work either.
Thanks,
Eric
shep2112 said:
I installed HTC's official AT&T ROM and the screen corruption seems to be less extensive but looks different too. The snow at startup is still present though.
There was a radio that came with Jackos ROM, is there any chance that's to blame? Though it worked fine for a couple weeks before these weird screen things started happening.
I haven't tried making a voice call yet to test the earpiece/earphone/loudspeaker or whatever the proper name is for it but since nothing else is really 'fixed' I'm not sure it will work either.
Thanks,
Eric
Click to expand...
Click to collapse
The stock ROM should've come with a radio as well...
task29 & flash stock? Otherwise perhaps you have a hardware problem... I don't know what to make of this snow .
The earpiece/loudspeaker thing isn't fixed either. I'll try a Task29 tomorrow or tonight if I can't sleep (thinking about this stupid phone! ) and then flash this ROM again and see what happens and let you know.
Thanks again
Problem: Cannot turn on the screen by pressing the power button sometimes. The screen is black or very dim, I cannot tell. One can see nothing on the screen, and it doesn’t accept any touch input, either. The phone still rings if there’s an incoming call. If this happens, the following several presses (about 10 - 20) on the power button will probably lead to a reboot. The “screen auto-rotate” and the proximity sensor may fail after the reboot, but will recover after a manual reboot.
Frequency: Fewer with higher Rom version. About once per day for 4.3.
Other description:
The problem frequently happens when I just take the phone outside my house/office, and seldom happens when the phone just stays somewhere.
The problem seems to be irrelevant to the remaining battery capacity or the uptime, but it never happens when charging.
The problem seems to be irrelevant to the Apps installed.
The problem seldom happens in the first 3-4 days after flashing a Rom, but happens more and more frequently as time goes by. My guess is some cache is stuffed by some trash, which causes the problem. The phone may be fine as long as the trash can be cleaned up on a regular basis.
I manually reboot my phone at most every two days.
Solutions tried, but don’t work
Flashing official ROMs 4.0.4, 4.1.1, 4.1.2, 4.2.2 and 4.3 following the procedure “adb reboot bootloader; fastboot oem unlock; flash-all; fastboot oem lock”, without google wallet, not rooted.
Turning off the auto-brightness control, as suggested by some post on the Internet.
Does it look like it goes to standby normally or does the screen show gibberish and then turns off?
Sent from my Galaxy Nexus using XDA Free mobile app
Thymo said:
Does it look like it goes to standby normally or does the screen show gibberish and then turns off?
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
Thank you very much.
I think it's standing-by normally even through the screen is black (or very dim, I cannot tell), since it rings if there's an incoming call. I can see nothing from the screen, and I don't think the screen accepts any touch input, either.
Does this answer your question? Thank you.
Bobby_yan said:
Thank you very much.
I think it's standing-by normally even through the screen is black (or very dim, I cannot tell), since it rings if there's an incoming call. I can see nothing from the screen, and I don't think the screen accepts any touch input, either.
Does this answer your question? Thank you.
Click to expand...
Click to collapse
Thanks.
Was just asking if you had gibberish yes or no. In that case i've got a different issue than you (Suspecting f*cked GPU).
Have you tried a different ROM/Kernel combination maybe it's related to that.
Thymo said:
Thanks.
Was just asking if you had gibberish yes or no. In that case i've got a different issue than you (Suspecting f*cked GPU).
Have you tried a different ROM/Kernel combination maybe it's related to that.
Click to expand...
Click to collapse
No.
No, I just tried the official ROMs. Any suggestion?
Perhaps it's just busy in the background and running low on RAM. Give LagFix a try. Sorry can't link atm as I am on mobile...
eKeith said:
Perhaps it's just busy in the background and running low on RAM. Give LagFix a try. Sorry can't link atm as I am on mobile...
Click to expand...
Click to collapse
Thanks a lot. I'm trying it.
Bobby_yan said:
Thanks a lot. I'm trying it.
Click to expand...
Click to collapse
LagFix does NOT help in my case. Any other suggestions? Thanks.
I've also had this blank screen with calls still ring issue for as long as I can remember, nearly 2.5 yrs.
I've always suspected it's my ROM and so I'd try out another ROM'S, BUT no other ROM works like how I'd like, so I always come back to my ROM.
It doesn't happen every single day, but it does happen very often.
I've tried using apps that auto reboot daily, but eventually this blank screen issue will return.
Unfortunately I can't seem to find any solution, so I just put up with it, it's like the 1 only flaw with my ROM.
&
Not to be at all rude, but I'm really glad op has had this issue from testing other versions of Android, cause then at least I know I don't need to give up my great tablet mode ROM.
LOL
I think I've finally found a work around for this screen of death.
Using Exposed, download/install this module/extension:
Disable Proximity
http://repo.xposed.info/module/com.mrchandler.disableprox
It does exactly what it's name is and ever since then I've not once had to remove my GN battery to work again because the screen went completely dead.
NVM
Screen still goes dead.
Anyone find an actual fix to this?
isajoo,
I had pretty much the same problems with my Galaxy Nexus running CyanogenMod 11 M12.
It got better by doing the following :
Blowing dry air in the earpiece… though the proximity sensor is clearly beside it. Can't do any harm though, I guess.
Settings/Applications/All/menu/Reset applications preferences (or whatever that's called in english) : that seemed to do a lot of good to my phone ! However, it's a very unsatisfactory answer on a technical point of view, as I still don't know WHAT was precisely needed. It's a "magic wand" solution for which I can't give an explanation.
Not specifically related, but greatly helped my phone in the responsiveness area : Trimmer (fstrim) (https://play.google.com/store/apps/details?id=com.fifthelement.trimmer), an updated version of LagFix that you may already know
Hope that helped !
(I wanted to try http://www.androidlegend.com/how-to-perform-proximity-sensor-calibration-on-any-samsung-phone/ as well, but apparently, /sys/class/sensors/proximity_sensor/prox_cal does not exist on my phone…)