I am using Myns Android ROM withthe wifi update + 110 pixel density update, booting via SD card and every now and then I get a graphical glitch/system crash that shows as thin, black and white stripes on my screen.
Anyone know what might be the cause/how I can fix this?
If i chose to install to NAND, would it be more stable/faster? And can I simply flash it with a WM ROM to go back to "normal"?
Thanks!!
I cant say about the glitch, try changing the kernel maybe. But your second and third questions have been asked and answered so many times, its ridiculous. But since its your first post, I'll answer:
would it be more stable/faster?
Click to expand...
Click to collapse
Yes to both
can I simply flash it with a WM ROM to go back to "normal"?
Click to expand...
Click to collapse
Yes again. Also, Try using the search button in the forums, and read the stickys, go through some threads etc.
My apologies for not going through the threads properly.
I half knew the answers to my 2nd and 3rd question, but wanted clarification
I am trying Super Eclair Lite, and whilst wifi works well, I cannot hook up to 3G(gprs/wap/hdspa/EDGE etc)
I can call and make/receive texts though :S Hit this glitch a couple of times too, but i noticed it seemed to happen when putting the device to sleep, so I changed the screen setting to 30 minutes and turned of animations etc.
p.s. How do you remove widgets?
graphical glitches are usually caused by using the wrong panel type in default.txt when using haret, or the wrong NBH panel type when using Nand, to fix the first, edit default.txt, to fix the second flash another NBH with another panel type, (panel type is usually in the filename).
To remove a widget, press and hold on it, then move it to the bottom of the screen.
Apologies for being a totaly newbie, but what are the "panel types"? MY default.txt shows the correct resolution, but I cannot see anything about panels (I might just not be looking hard enough lol!)
I now have a problem when booting from the SD card that my resolution is "bigger" (icons are larger and overlap, menu items are larger too) But it was fine before i rebooted....
Any help for the GPRS issue?
mr_pablo said:
My apologies for not going through the threads properly.
I half knew the answers to my 2nd and 3rd question, but wanted clarification
I am trying Super Eclair Lite, and whilst wifi works well, I cannot hook up to 3G(gprs/wap/hdspa/EDGE etc)
I can call and make/receive texts though :S Hit this glitch a couple of times too, but i noticed it seemed to happen when putting the device to sleep, so I changed the screen setting to 30 minutes and turned of animations etc.
p.s. How do you remove widgets?
Click to expand...
Click to collapse
You can remove widgets by long pressing on them until the bottom tray becomes a bin/x or something similar, then drag them to it.
About the 3g problem, I had that a while back after installing a new build, what solved it for me was changing the kernel. I had flashed to nand so I simply got another nbh. For you it might be zimage. If you say you got that graphical glitch when the device went to sleep, then you should try changing your panel time. For a good smooth android experience, you will have to take some time, and flash many different nbhs/updates and change settings etc to get what works best for you.
I am trying out Myns Warm Donut again with the wifi update.
How can i change panel time?
Dunno if this helps but I managed to get GPRS/3G working on SuperEclair. I had to manually put in the APN and made sure the mcc mcn codes were right.
When i changed the codes the APN disapeared from the list but data connection established itself after a couple of minutes.
This is the link I used to get the right APN codes:
http://george.insideiphone.com/wp-content/uploads/2007/12/mcc-and-mnc-codes.pdf
For NBH files the panel type and resolution is in the filename: KAISIMG-PANEL1-320-ECLAIR.NBH : the filename shown is for Panel1 resolution 240x320.
To change panel type simply flash another NBH with panel2 or panel3, it will not affect your install, since the android nbh's don't format Nand, this is done by the installer
For Haret installs the panel type is changed in default.txt look for the line: board-htckaiser.panel_type and change the value to 1, 2 or 3.
Wow, that is great! I've searched for a solution for this problem a long time, but this is the first thing that works for my Kaizer 130.
Many thanks!
I had android running off the sd card most of the day yesterday, using the panel type of 1 worked well (did notice the odd glitch when coming out of sleep mode, but it didnt crash)
still not sure what the panel type does, can anyone explain? (curiosity really)
However, I tried to use the camera, and after switching to vide and back again to photo mode, android crashed.
I can suffer not using the camera, as its nothing amazing.
p.s. anyone know if you can remap the buttons? as the hang up button puts the phone into sleep mode, the wheel doesnt do much, and other buttons dont do much either.
Panel type refers to the LCD panel, there are 3 different types of panel fitted to the kaiser series, one manufactured by Sony, the other two by Topoly, functionally they are identical, however there are some differences in the electronic controllers fitted to each, which in winmo is detected automatically, however Android is unable to detect the differences and the correct type must be passed to the kernel at boot time, either by boot parameters in default.txt or hardcoded into the NBH. Due to the way electronics factories work, the panel type depends on which one was available at the lowest price, and shortest lead time, when it was required, hence the reason for the confusion, since some people still think that panel type is set for certain models of kaiser, which is inaccurate, since both my KAIS130's have different panels fitted.
Camera does not work in any Eclair build yet, it does in Donut builds, however it's still a little low quality even on the 3Mp Kais130, Video does not work on any android builds very well, if at all.
Remapping buttons can only be done by recompiling the kernel I think, however after a while the button layout becomes second nature, I actually get lost using winmo now, lol.
Related
My Screen has totally stop touching and Ive searched and searched for a solution.... and yet havent found any. I deleted the ts-calibration file and yet still screen no work
BUMP Help!
You mean that the screen is not working within android of with windows mobile?
If you mean windows mobile then your screen is broken or if you think it is because of the cab, you can try a hard reset.
If it is only in android then uninstall this version of android and download the .rar and extract it to your SDcard.
I have sort of the same issue. My screen doesn't work (most of the time). For some reason it is responsive sometime (not clear how to recreate that). I can see the screen is responding, although if I go to the menu and try to select a icon with my finger it holds the icon and drags it (and I cannot let it go)
But also my keyboard layout is messed up. It totally doesn't have any logic anymore. Only when entering a pincode the numbers are correct, but if you are trying to enter a number to call, it is totally messed up (numbers are symbols, letters are numbers)
Deleting the calibration file doesn't work for me. Also I have tried hard resets and rom upgrades several times, with no succes. It looks like installing android changed something, but doesn't set it to his old state after removal.
Anybody?
This is in WinMo you're having the problem...? I'm not sure what to tell you, Android doesn't touch the NAND whatsoever - so it shouldn't effect (affect?) WinMo whatsoever.
yea i was having the same problem and couldnt figure out a solution, i deleted the ts-calibration, i've tried deleting all android files and starting over but the problem still exists. I think it might have something to do with the little bit of moisture i see under the screen because before i started seeing that, it used to work. But the screen works just fine when WinMobile is running so i dont know
If the screen is fine in WinMo, try a clean build. Not sure what could cause the screen to just stop working in only Android tho... unless of course you have a bad ts-calibration file...
When you do the screen calibration process in Android, does it work OK...?
arrrghhh said:
This is in WinMo you're having the problem...? I'm not sure what to tell you, Android doesn't touch the NAND whatsoever - so it shouldn't effect (affect?) WinMo whatsoever.
Click to expand...
Click to collapse
No, in both. This problem originated from the fact I was never able to start up a blazin android. It started booting, but for some reason never finished it. With the previous editions I never had any problems.
arrrghhh said:
If the screen is fine in WinMo, try a clean build. Not sure what could cause the screen to just stop working in only Android tho... unless of course you have a bad ts-calibration file...
When you do the screen calibration process in Android, does it work OK...?
Click to expand...
Click to collapse
I know you are replying on another user, but I still want to respond
Yesterday my screen was responding for a short moment. I have replaced the WinMo rom after that several times, no success. Also deleted android and reinstalled it again. (I've been trying trial and error for a while now, without any success.)
My WinMo rom btw was an energy build. Any similarities with other users experiencing this issue?
Is there some internal memory where these type of settings (keyboard layout and such) are stored and what not always change if you upgrade roms?
Perhaps I should go back to the original T-mobile rom.
Just upgraded to the original tmobile rom, but I'm stuck at the WinMo startscreen (tap the screen to start using it for the first time) I noticed that if you slide the phone open (keyboard visible) the display of the screen is correct. If I flip it back I'm missing parts of the screen.
dwaaz said:
But also my keyboard layout is messed up. It totally doesn't have any logic anymore. Only when entering a pincode the numbers are correct, but if you are trying to enter a number to call, it is totally messed up (numbers are symbols, letters are numbers)
Click to expand...
Click to collapse
I'm sorry for spamming this topic, but isn't it really weird that only for entering your pincode the numbers are correct, but afterwards the layout is all messed up?
6_7_8 = 123
Y_U_I = 456
H_J_K = 789
N=0
I have the feeling my phone is using system files (after login) of a completely different phone (and no.. I did use the right rom's ) This goes for the keyboard as well as the screen issue.
any bright ideas?
Just to bring it under the attention again, because I'm on the edge of sending it back to t-mobile. (I hope they are not going to charge me because I have a diamond 2 that also needs repairing, touchscreen doesn't work as well, and I'm seeing some costs coming up there. For some reason I always manage to wreck my phones in the first 2 years. )
Any bright ideas?
I had a possibly similar problem.... I thought my screen was going bad after the install, but the install wasn't the issue. It was just a coincidence.
Take a small pin and run it along the side of your touch screen. Sometimes dirt gets stuck in there and that stops it from working properly. If that does not do it, slighty and gently lift the touch screen a little bit and put it back down. That worked for me!
Sent from my MSM using XDA App
It worked!
trotmanc said:
I had a possibly similar problem.... I thought my screen was going bad after the install, but the install wasn't the issue. It was just a coincidence.
Take a small pin and run it along the side of your touch screen. Sometimes dirt gets stuck in there and that stops it from working properly. If that does not do it, slightly and gently lift the touch screen a little bit and put it back down. That worked for me!
Sent from my MSM using XDA App
Click to expand...
Click to collapse
I was kind of skeptic here of this solution, because my phone looked quit clean. But there I was, on visit with my parents, fiddling with my phone, thought; let's put my nails between the lines next to the touchscreen..... and wtf.. it worked My screen is back up. Very surprising but good.
No I only have my keyboard to worry about. Any thoughts on that?
I just flashed my Kaiser with Fat Free Froyo RLS5. I really like the Android OS, but the lack of functionality is bothersome. I can't type into the Google search bar that is on the desktop, the camera doesn't work and, worst of all, the USB to PC data connection is inoperable. These things along with some other minor things like the fact that I can't change the volume of the alarm clock make me want to try a different flavor. I've only been using it for about an hour and already found all these problems so I can image that there are more.
All I am looking for it a version of Android that will allow me to use the camera, browse my SD card from my PC, and has a working WiFi. Speed is also a concern.
If I could get some suggestions I would be appreciative.
Thank you.
lemminman said:
I just flashed my Kaiser with Fat Free Froyo RLS5. I really like the Android OS, but the lack of functionality is bothersome. I can't type into the Google search bar that is on the desktop, the camera doesn't work and, worst of all, the USB to PC data connection is inoperable. These things along with some other minor things like the fact that I can't change the volume of the alarm clock make me want to try a different flavor. I've only been using it for about an hour and already found all these problems so I can image that there are more.
All I am looking for it a version of Android that will allow me to use the camera, browse my SD card from my PC, and has a working WiFi. Speed is also a concern.
If I could get some suggestions I would be appreciative.
Thank you.
Click to expand...
Click to collapse
Camera not working is related to your kernel/radio rom. Also you could use not so super froyo if you want the same with more features. If you want more speed I suggest a Cyanogen based rom as these are the fastest currently. I suggest changing your kernel to l1qu1ds latest .32 kernel via the thread that is stickied at the top.
USB to pc is not working through my computer right now but adb is at least. What I do for data transfer is just use System on NAND and Data on SD and use a card reader for the data.
Lastly, remember that android on the Kaiser is by no means perfect and is still more or less of a thing to be like "Look what my old phone can do!" thing. If you want everything perfect then Windows mobile has that already. Otherwise if you want a cooler newer OS on your phone then its going to take a little time for us. We have come a long ways but not all the way there yet.
lemminman said:
I just flashed my Kaiser with Fat Free Froyo RLS5. I really like the Android OS, but the lack of functionality is bothersome. I can't type into the Google search bar that is on the desktop, the camera doesn't work and, worst of all, the USB to PC data connection is inoperable. These things along with some other minor things like the fact that I can't change the volume of the alarm clock make me want to try a different flavor. I've only been using it for about an hour and already found all these problems so I can image that there are more.
All I am looking for it a version of Android that will allow me to use the camera, browse my SD card from my PC, and has a working WiFi. Speed is also a concern.
If I could get some suggestions I would be appreciative.
Thank you.
Click to expand...
Click to collapse
the search bar will work if you download google search from the market, it was removed since it can be installed from the market, fat free is fully functional you just have to work to get it going out of the gate, now in contrast not so super froyo is ready to go from the get go
lemminman said:
the camera doesn't work and, worst of all, the USB to PC data connection is inoperable. These things along with some other minor things like the fact that I can't change the volume of the alarm clock make me want to try a different flavor.
Click to expand...
Click to collapse
I am using Fat Free Froyo RLS5 and all that stuff works for me.
USB to PC works perfectly in linux It works for me on windows 7 too, but you just have to wait a long time (maybe 2-5 mins) for the computer to recognise it.
To change the alarm volume just roll the jog wheel while in that menu (or press whatever buttons you have assigned to volume up/down)
Thanks for the help, guys.
I suggest changing your kernel to l1qu1ds latest .32 kernel via the thread that is stickied at the top
Click to expand...
Click to collapse
That is the kernel I have. My radio is version 1.65 something.
What I do for data transfer is just use System on NAND and Data on SD and use a card reader for the data.
Click to expand...
Click to collapse
I don't have a card reader; that is why this is important to me. Are there any Android versions that this works, or an app that I can install even?
Lastly, remember that android on the Kaiser is by no means perfect [...]
Click to expand...
Click to collapse
The only reason I don't want WMP is because it is ridiculously slow to respond. I had heard that Android was much faster so I am giving it a try.
the search bar will work if you download google search from the market
Click to expand...
Click to collapse
That part really isn't a big deal; I probably would never even use it. It was just one of the many small glitches I was noticing during normal use. Things like there being no way to bring the phone back from sleeping except the power button (not even opening it!). At one point, when it is just sitting on my desk, the screen turned white and the phone was completely unresponsive. I had to hard reset it. They keyboard works except when dialing a number where it seems completely random.
If there is a workaround to these things, I'm fine with doing some personalizing, but if not, I would like to know if there are flavors that don't have these kinds of issues.
I think I will try Cyanogen like you suggested and see if I like it any better.
Thanks again for the help.
lemminman said:
Thanks for the help, guys.
That is the kernel I have. My radio is version 1.65 something.
I don't have a card reader; that is why this is important to me. Are there any Android versions that this works, or an app that I can install even?
The only reason I don't want WMP is because it is ridiculously slow to respond. I had heard that Android was much faster so I am giving it a try.
That part really isn't a big deal; I probably would never even use it. It was just one of the many small glitches I was noticing during normal use. Things like there being no way to bring the phone back from sleeping except the power button (not even opening it!). At one point, when it is just sitting on my desk, the screen turned white and the phone was completely unresponsive. I had to hard reset it. They keyboard works except when dialing a number where it seems completely random.
If there is a workaround to these things, I'm fine with doing some personalizing, but if not, I would like to know if there are flavors that don't have these kinds of issues.
I think I will try Cyanogen like you suggested and see if I like it any better.
Thanks again for the help.
Click to expand...
Click to collapse
the white screen is a known issue apparently overclocking improves this
White screen is present when the system didn't draw the screen before it power up.
When you overclock the system is faster so it spend less time to draw the interface.
Sometimes you have with screen when the system sleep but it can't resume because the main app crashes.
To change the alarm volume just roll the jog wheel while in that menu
Click to expand...
Click to collapse
This changes "Ring volume" regardless of what I have opened.
Thanks for all the input, everyone.
I have tried four different Android builds now and I haven't gotten a USB data connection with any of them. I noticed that one of them had a Network option, as though I might be able to browse files of computers on the network which would solve my problem. Unfortunately, that particular build just says "Error" when I try to turn WiFi on.
Is there an android app I can install that will allow me to transfer files between my phone and a PC? That is really the number one priority right now. To test these Android builds I have been reverting back to WMP every time I want to try a different one because I need to put the androidinstall.tar onto my card. I tried loading a bunch of different ones on the card to avoid this, but I get "Permission denied" when I try to rename a file in the andboot folder.
Thanks again.
The forum search tool will answer all those questions I know I have answered it atleast 500000 times
Sent from my HERO200 using XDA App
I have a kaiser with froyo kernel 2.6.32 date 9.9.2010 I have overclocked with atools to 500 mhz and also overclocked the GPU, battery is standard setting. My radio is Neon 1.65.24.36 Together with thoughtlesskyle`s (thank you!!) fat free release 5, i have a very stable situation here. I have to admit i am not a heavy user. Merely phonecalls and sms (or whatsup) and sygic navigation software . I only have to reboot once a week. I am not sure why, maybe because i use cachemate once a while.
For connection between pc and kaiser i use SD Share Dual Mount. It works perfectly. I had flashed the latest kernel(s) of l1q1d because of the alleged stable reboots. I am sad that i did not have stable reboots, it got stuck and i had to reinstall my apk`s again. And most important for me, the SD Share did not work with the latest kernel(s), thats why i reverted back to the 9.9.2010 one.
As for the white screen, it only happens to me if my kaiser goes asleep and i awake it immediately. If i take some seconds between asleep and awakening, it`s okay.
I have to thank many people here to be able to use my kaiser like i bought it yesterday or so. Maybe someone can try my settings and profit from it, like i do.
Shayer said:
I have a kaiser with froyo kernel 2.6.32 date 9.9.2010 I have overclocked with atools to 500 mhz and also overclocked the GPU, battery is standard setting. My radio is Neon 1.65.24.36 Together with thoughtlesskyle`s (thank you!!) fat free release 5, i have a very stable situation here. I have to admit i am not a heavy user. Merely phonecalls and sms (or whatsup) and sygic navigation software . I only have to reboot once a week. I am not sure why, maybe because i use cachemate once a while.
For connection between pc and kaiser i use SD Share Dual Mount. It works perfectly. I had flashed the latest kernel(s) of l1q1d because of the alleged stable reboots. I am sad that i did not have stable reboots, it got stuck and i had to reinstall my apk`s again. And most important for me, the SD Share did not work with the latest kernel(s), thats why i reverted back to the 9.9.2010 one.
As for the white screen, it only happens to me if my kaiser goes asleep and i awake it immediately. If i take some seconds between asleep and awakening, it`s okay.
I have to thank many people here to be able to use my kaiser like i bought it yesterday or so. Maybe someone can try my settings and profit from it, like i do.
Click to expand...
Click to collapse
Well at least the white screen is being worked on, see the thread I made.
Hello all, First, I searched the forums for my answer with no such luck, that being said if Im repeating a question thats been asked I apologize. I have a problem with keeping android stable. I have flashed with different versions of windows several times all with success. I do however, prefer the android system, I find that it runs much better, faster and has better perks. Everytime I flash following the original how to, I run in to a couple similar problems.
The first is when I hit the power (not hold the power) the back light cuts off and the keyguard enables, the screen goes dark all as it should. Depending on the time ( the longer it is the worse it is) when I hit the power key to revive my phone, I often get a white screen, then it waits , then it goes dim, Sometimes If I hit the power button several times it eventually comes back to the key guard option, but others I have to remove the battery and reboot. This is the major problem, as I cant use my phone when I need it. This problem seems to get worse the farther it gets away from the flash date, e.g..,, after a brand new flash it works pretty good and then it goes downhill from there.
Second, it seems to lock up when I let it charge overnight, not always (but most of the time) I get up, click the power button to revive the phone and I have a white screen before me that is frozen solid. This like the previous problem seems to be linked to the distance from the last flash.
I hope that its something Im doing wrong, as Im currently using wmobile 6.5 and since Ive had a taste of the droid os, my wm phone is just disappointing. And as I was unsuccessful in finding a post that adequately describes my problem ,Im hoping that there is a way around this .
I have tried, Incubus Superfroyo, Wrym warm donut, and Cyanogens build. Im sure Ive tried others, they just escape me, I was re-flashing daily until I went back to windows. I truly hope someone out there has encountered what I have and has a solution. thank you all for what you do, these forums have been extremely valuable and helpful.
Sounds like you have the wrong panel type selected. Is it set to auto? if it is, try setting it to 2 instead. That cleared up the problem for me.
Tried all panels all have the same problem.
Well thanks for all the many replies. I give Ive tried everything on this site and m android is still really glitchy. Guess it will be windows until I get perhaps a phone capable of running android smoothly.
What kind of phone do you have?
Sent from my HTC Vision using XDA App
do you have an SD card you can try to boot from and share your settings?
What we need to know is which kernel you're using, or an image of the kernel you currently have. Also, we need to know which radio version you're using, as this can have detremental effects on stability as well.
Personally, I have been using radio version 1.70.19.09, which seems to be the most stable with kernel .25 IMHO.
I have also "personalized" ThoughtlessKyle's "Fat-Free Froyo", adding/removing apps that I need or don't use respectively (navigation, QQPlayer, Pandora, etc.).
Currently, I think I might be one of the only people not experiencing any issues with this phone running Android 2.2.1. I do get the occasional "hang" (I wait for it to finish what it's doing instead of force close), but that usually has something to do with network coverage or an app requesting something from an unopened port.
Old phone, new OS and runs smooth as could be expected.
Next for me will be the HTC HD2 (if I get one at the right price, the tilt was free)...
I know, I know that MANY PEOPLE THINK OF THE WAKE UP WHITE JIBBERISH SCREEN as NEVER WORKING.
PoXFreak said:
What we need to know is which kernel you're using, or an image of the kernel you currently have. Also, we need to know which radio version you're using, as this can have detremental effects on stability as well.
Personally, I have been using radio version 1.70.19.09, which seems to be the most stable with kernel .25 IMHO.
I have also "personalized" ThoughtlessKyle's "Fat-Free Froyo", adding/removing apps that I need or don't use respectively (navigation, QQPlayer, Pandora, etc.).
Currently, I think I might be one of the only people not experiencing any issues with this phone running Android 2.2.1. I do get the occasional "hang" (I wait for it to finish what it's doing instead of force close), but that usually has something to do with network coverage or an app requesting something from an unopened port.
Old phone, new OS and runs smooth as could be expected.
Next for me will be the HTC HD2 (if I get one at the right price, the tilt was free)...
Click to expand...
Click to collapse
Ill try that combination and post my results. The latest I tried was
Scoot CyanogenMod 6.1.2 RLS6 with 2.6.32 still no joy, white screen crashes and hang ups. and it seems progressively worse the longer the rom is on the phone. To whomever asked what phone I have, its the at&t tilt II
srlebonv said:
Ill try that combination and post my results. The latest I tried was
Scoot CyanogenMod 6.1.2 RLS6 with 2.6.32 still no joy, white screen crashes and hang ups. and it seems progressively worse the longer the rom is on the phone. To whomever asked what phone I have, its the at&t tilt II
Click to expand...
Click to collapse
I can't help you regarding panel selection but, please have Radio ROM version 1.65 or higher. And do give my fresh foryo a go with 2.6.25 kernel (everything is there in the thread on how to use it with 2.6.25 kernel).
the WHITE GLITCHY SCREEN IS THE PROBLEM WITH ANDROID DRIVERS. Install with Data on SD Card often causes lockups / force closes.
I am using panel type 1 and white glitchy screen stays for like half of a second and next moment I get a nice clean keylock screen. I don't know but its like 20th time I am explaining the problem related to LCD
Change Panel Type, Get a compatible Radio version (1.65.x or HIGHER)
You say that often install with data on the sd card causes lock ups and freezes. Can you explain further what you mean ?
dark_prince said:
I can't help you regarding panel selection but, please have Radio ROM version 1.65 or higher. And do give my fresh foryo a go with 2.6.25 kernel (everything is there in the thread on how to use it with 2.6.25 kernel).
the WHITE GLITCHY SCREEN IS THE PROBLEM WITH ANDROID DRIVERS. Install with Data on SD Card often causes lockups / force closes.
I am using panel type 1 and white glitchy screen stays for like half of a second and next moment I get a nice clean keylock screen. I don't know but its like 20th time I am explaining the problem related to LCD
Change Panel Type, Get a compatible Radio version (1.65.x or HIGHER)
Click to expand...
Click to collapse
Ok, so I installed your version of froyo, the accompanying 2.6.25, the radio that you use. For the most part the hanging up is fixed. Now the second problem is still in place. Sometimes when Its been in hibernation(or whatever you would call when you hit the power button once ) when I attempt to refresh my phone (hitting the power button once) nothing happens, the green light is still blinking at the top but the screen stays blank, normally have to remove the battery and restart to get back to using the phone. Is this a sleep setting? or is this something Ive done wrong during the installation.
Hi everyone.
First time on a forum for years. This one is pretty daunting though. Not even sure if Im in the correct thread
Just recently got myself an HTC Touch Pro. Yeah! it's old but I guess its better that the Ericsson w350 I had.
I was not happy with the 6.1 Win Mobile OS on the HTC and I heard that Android can be loaded up instead. So I started doing some research.
To cut a long story short, I managed to load XDAndroid onto the microSD card. all is working fine except I messed up on the touch screen calibration. or at least it was not made clear to me that what I was indeed doing was a screen calibration.
After some reading on the wiki files, I removed the ts_calibration as instructed and rebooted the system. The graphic for the calibration test does not seem to display correctly. Hence the readon for the initial stuff-up so I simply had to guess where the pointer were using the win6.1 OS calibration(Don't ask - it involved a non-permanent marker). Even that does not seem to work.
It would seem that the co-ords where transposed after some fiddling around. Left was right, up was down etc. So I got to thinking to open that ts_calibration file and started playing around with the numbers. Even the screen functionality was reversed when the I slid the screen open. Navigation via the Keyboard is no hassle though. The touch button navigation seems to work fine except the selection key does not actually select anything, I have to use the enter key on the keyboard. Not sure if this is normal. So if anything, navigation involves the keyboard to be open thus the screen orientation is always landscape as opposed to portrait view which sucks! esp if I'm texting or making a call. What the work around for this is general?
So I thought of opening the ts file in a txt editor and I transposed the numbers. I seem to be getting somewhere as the up and down seem to be working correctly now but the left and right are not, center screen is still out though. I'm not sure what sets of number represent which co-ord. I know that the calibration requires 5 co-ords, but I dont know in which order they should be. Is middle, top-right, top-left, bottom left, bottom right?
It would be easier to just have the correct co-ords for this phone. instead of playing around with some random numbers. IOW would the ts file co-ords be the same for all HTC Touch Pros? if so where can I get the correct co-ord numbers for that file? then I wont have to use the calibration function. easier still, is there a free app that will do this from within the XDAndroid os?
The start up txt I chose was Raph100 for the root folder. This is correct for my phone according to the wiki help files. I've not updated the files and used them as is. Would the incremental updates fix this?
I'm having the same issue for my TP. After some discussion, I downloaded the ts file from the FRX07 fixed discussion and it's pretty darned close to accurate. MAYBE just a little off center to the lower left of icons.
Here's a utube vid that shows clearly the touch pattern for calibration.
http://www.youtube.com/watch?v=FB6MVFH4Jv4
Hope it helps.
Hello,
I got an problem on like 4 of the 5 kaisers here.
The problem is that sometimes the kaisers goes into an sleep where it doenst come out without reset.
You will get an black screen and the light of your keyboard is on and doesnt turn off. When this happens the battery goes from 100% to 0% in like 40 mins. without the problem i can use the phone for 2 days.
My question is how to solve this? I tried the following things.
- Radio 1.65, 1.70. 1.71
- 2 different hspl
- old and new kernel.
- and loads of different roms. from gingerbread to eclair.
Any solution or fix for this? because i can't use it for daily base now since when i dont notice the battery is empty of that bug.
Best Regards,
Veldmuus
That's the black screen of death. I never get that, but it's one of three problems that I have heard of. I think it might be related to going to sleep. I use the latest kernel, from git, which is pretty much identical to scooter1556's kernel with separate cache. What kernel are you using?
The second problem is the white screen of death, which I get a lot when I leave the phone on the charger. The screen is white bright, the kernel is not crashed. Sometimes Fn-Right-soft-key twice will cure this, but usually not. Some have guessed that this has something to do with the phone going to sleep not quite properly while charging. There is an option to not go to sleep while connected to a charger, and I haven't tried that option for a long time.
The third problem is a kernel crash (screen freezes, keyboard doesn't turn on LED, etc) caused by compcache (zram). Can be avoided by not using compcache.
The most annoying issue I have is that I've never figured out how to tweak the build so that apps can be installed to SD. I've been trying to change initrd so that, when installed completely on NAND, the sdcard is completely managed by vold. So far no success, and I've pretty much moved on to my newer phone (Rhodium, aka AT&T Tilt2).
I have spent the last week or so "tweaking" my build.prop file, adding lines for disabling sleep mode, 3G speed tweaks (doesn't do much yet) and fixing small compatibility issues such as AGPS/GPS not working. So far so good, no more sleep of death/black screen/white screen.
If successful, I would ask that the modified build.prop file be added to the Froyo builds on SourceForge, intergrated directly as to eliminate "end user interaction", meaning you won't have to touch it.
I am also looking into some sysinit.rc mods as well, but I haven't had much time lately.
Veldmuus, do you have a way to edit your own build.prop file such as Root Explorer, or would you have to push it to the phone via ADB?