Related
Just flashed to the Ricky's latest Opera ROM, and starting to explore the new system, but I am having an odd problem. The home screen keeps popping up while I am in the middle browsing through menus. For example, I was trying to change my connection settings, and in the middle it just put me back at the home screen. This has happened at all menus, so I can't pinpoint the issue. I browse back with no issue, but it is annoying to be half way through something, and get booted back to the home screen, and have to start all over. Anyone have any insight into what my issue would be? Could it be a process, or program?
Edit:
Ok, my issue was a user error. I didn't know what the Time Out setting did under the Home Screen settings, and had set it to 10s. Should have played around more before post.
jyxavier said:
Just flashed to the Ricky's latest Opera ROM, and starting to explore the new system, but I am having an odd problem. The home screen keeps popping up while I am in the middle browsing through menus. For example, I was trying to change my connection settings, and in the middle it just put me back at the home screen. This has happened at all menus, so I can't pinpoint the issue. I browse back with no issue, but it is annoying to be half way through something, and get booted back to the home screen, and have to start all over. Anyone have any insight into what my issue would be? Could it be a process, or program?
Edit:
Ok, my issue was a user error. I didn't know what the Time Out setting did under the Home Screen settings, and had set it to 10s. Should have played around more before post.
Click to expand...
Click to collapse
Oh ok glad you found the error lol. So is everything okay no with your phone? if you have any other problems or concerns please feel free to ask. We are all willing to help out
I have a weird issue with my TP2.
When i reset it... it boots up and i can see the HTC logo but tf3d won't start.. i went into settings unchecked tf3d and reticked it.. no difference!
How is the executable called? anyone elese experiencing this issue?
Known problem.
The best workaround I found till now:
1. Switch on Flightmode. (use the red phone button press for more than 3 seconds)
2 Reset/Restart
3. Switch off flightmode. The PIN screen comes up automatically.
Works in 100% of the cases.
Huib
You can run the manila.exe found in the Windows folder but I've found that when doing this, the clock on the home tab doesn't refresh/change and the notification balloons don't come up (the little round icon on the sms tab when you have unread sms's for example)
the workaround worked like a blast. Thanks..
I could not find that thread describing it.. i wonder why HTC did not release any hotfix for this.
How is the manila.exe started???
Hi!
I have the same issue, Touchflo3d not starting after boot on my swedish Touch Pro2.
If i try to manually start manila.exe i also get the clock freeze on the start screen and no mail/message notifications.
I've tried two hard resets, and adding programs and settings one at a time just to try to find the reason for this, but no luck. It feels like it's all random, it all works with apps installed, and suddenly it stops working, no changes made.
I notice that when i manually execute \windows\manila.exe the screen goes from the black screen with the HTC logo directly to the start screen of touchflo3d. When everything works the way it should do, there is a difference, a text appears on the black screen under the HTC logo, something like "starting Touchflo3D".
I'm not that good at windows mobile myself, but i hope someone on this forum, that has a phone with touchflo3d, can find the difference between starting the manila.exe manually, not seeing the "starting Touchflo"-test, compared to the automatic start with that text.
I hope that would lead to a solution or fix, i would not mind very much having to start touchflo myself with a click, but i'd like to start it the same way it does when working so the clock and notifications work as it should.
Let's all hope some of the many extremly skilled members here picks up the glove and takes a good look at this!!
Best regards
Cerebral Cortex
Phone screen will disapper?
herpi said:
Known problem.
The best workaround I found till now:
1. Switch on Flightmode. (use the red phone button press for more than 3 seconds)
2 Reset/Restart
3. Switch off flightmode. The PIN screen comes up automatically.
Works in 100% of the cases.
Huib
Click to expand...
Click to collapse
Thanx it worked for me!
But now TF3D will come in front when I make a call. So after 5 seconds calling the first screen of TF3D (the clock) will appear. Then I have to press the first button (phone) to get the phone screen again. Verry sad.
I also can not use the program Notes anymore when calling, the program will go to the back. And TF3D will come to the front!
Someone know the answer?
Thanx in advance,
Richard
Hi,
i had the same problem and tried many solutions until i found what was the cause for that problem: S2U2. Once i disabled the S2U2-autostart on boot up, tf3d is always starting the way its supposed to. I simply removed the ilock2-shortcut from windows/autostart and start it manually after tf3d has launched. Not really perfect, but better than everything else for me.
Do you use S2U2?
Regards
MiDiAN
MiDiANx360 said:
Hi,
i had the same problem and tried many solutions until i found what was the cause for that problem: S2U2. Once i disabled the S2U2-autostart on boot up, tf3d is always starting the way its supposed to. I simply removed the ilock2-shortcut from windows/autostart and start it manually after tf3d has launched. Not really perfect, but better than everything else for me.
Do you use S2U2?
Regards
MiDiAN
Click to expand...
Click to collapse
I did the same, disabled s2u2, and no more problems. After a while however the hanging came back randomly.
S2u2 is back now. Mothers little helper! I can live with the flightmode on and off solution.
Huib
Quote:
Originally Posted by daveke0201
have a problem with s2u2 v2.04 wvga and 3dtf. after installation it wont boot anymore.
this is what i tried.
start stop 3dtf => not starting
stop ilock2, stop start 3dtf => not starting.
does work with the 1.62.
can anyone help me?
************* reply from ac ************
Try to set a longer "Boot-up Delay" (S2U2 Settings->Advanced).
__________________
Cheers,
A_C
http://ac-s2.com
*******************************************
I've set my bootup delay in the advanced menu to 20seconds and my problem is gone.
pieterbotes said:
I've set my bootup delay in the advanced menu to 20seconds and my problem is gone.
Click to expand...
Click to collapse
Nope, 20 secs does not do the job in my case.
Tried several combinations and different ways of startup, but no deal.
I already had the problem without S2U2 so I cannot possibly blame them.
I still am stuck at the flightmode trick which gives a 100% success.
Huib
Moisture damage perhaps???
herpi said:
Known problem.
The best workaround I found till now:
1. Switch on Flightmode. (use the red phone button press for more than 3 seconds)
2 Reset/Restart
3. Switch off flightmode. The PIN screen comes up automatically.
Works in 100% of the cases.
Huib
Click to expand...
Click to collapse
I have the same issue. The first time this behavior surfaced for me was right after i´d applied Zagg´s inivisible shield.
I must admit that i lacked the patience to be leaving the phone for 12 hours drying up.
I´d put it in a dry, warm & well ventilated place for approximately 4 hours and thought that should suffice.
When the phone started acting up i used up all the non-printable 4 letter words i knew and did a hard reset.
Anyway - the problem has showed up about every third time i do a soft reset.
To me the solution has so far been another soft-reset.
Regards
Have the same problem, it's driving me nuts. Hate reseting the phone - it takes ages to boot up.
Won't spend time trying to fix this, will just not reboot/reset often. Hopefully the WM6.5/TF3D official package sometime in October will cure this.
vasra said:
Have the same problem, it's driving me nuts. Hate reseting the phone - it takes ages to boot up.
Won't spend time trying to fix this, will just not reboot/reset often. Hopefully the WM6.5/TF3D official package sometime in October will cure this.
Click to expand...
Click to collapse
I combine the flightmode trick together with the SlidetoShutdown, where I use the restart slider.
Doing it this way makes it more acceptable.
Huib
Hmm... I've had success with the 20 second thing but now that is also not working for me anymore... not sure what changed.
pieterbotes said:
Hmm... I've had success with the 20 second thing but now that is also not working for me anymore... not sure what changed.
Click to expand...
Click to collapse
It is quite random.
The flight-on/restart/flight-off always works, at least in my tp2.
Huib
so i've tried checking on/off Today/Item/TF3D, tried Flight Mode, and it still won't work. i'm talking like only 30-50% of the time it does work. and I never had PIN1 enabled!
i'm no programmer but it is conflicting with apps we install because TF3D works perfectly when the phone was fresh or hard-resetted. btw i'm using 6.1 Stock T-mobile
I had one before, dropped it a few times.. I wrote it off as that being why, well I just got a replacement one sent.. haven't dropped it once, it's been here only about 2 weeks
Randomly sometimes it won't respond to almost anything.. I'll be trying to slide the screen, it either won't at all or will go halfway like I barely touched it. I'll try clicking on things, programs, start, whatever... it'll not respond at all, I end up having to press with way more pressure than I should have to, way more.
Then sometimes without even a reset it'll start working just about normally again.. but that's rarely, usually I'll soft reset or pull the battery for a second and then it'll be fine.. for days even.. then I'll run into it again..
I noticed 2-3 times it was because I had **** updating at the time (motweets) or was receiving email.. but I've since made everything manual regarding email, and motweets updates once every 15 minutes and the amount of tweets is limited so it's not a lot..
Still, I run into this problem, and I've made sure it wasn't a program updating but I can't think of what else would make this happen, am I the only one??
Is it because there's a way to clear cache on internets and other programs and I have no idea how? (I fully close them, that's not the problem, I know my Vogue I just can't figure this out an it seems nobody else has this problem).. Not to mention I have my internet cache's directed to my storage card so as to keep my phone memory as free'd up as possible
If anyone can help..
mine is unresponsive sometimes and i have to tap on the back of the phone to get to work again. i thinks its going out soon
That's what I thought about my old one, I figured I had dropped it to much.. because I did lol but now I got a new one 2 weeks old and I'm running into the SAME problems.. I'm assuming I must be doing something wrong with how I've got **** set-up
j18yo said:
I had one before, dropped it a few times.. I wrote it off as that being why, well I just got a replacement one sent.. haven't dropped it once, it's been here only about 2 weeks
Randomly sometimes it won't respond to almost anything.. I'll be trying to slide the screen, it either won't at all or will go halfway like I barely touched it. I'll try clicking on things, programs, start, whatever... it'll not respond at all, I end up having to press with way more pressure than I should have to, way more.
Then sometimes without even a reset it'll start working just about normally again.. but that's rarely, usually I'll soft reset or pull the battery for a second and then it'll be fine.. for days even.. then I'll run into it again..
I noticed 2-3 times it was because I had **** updating at the time (motweets) or was receiving email.. but I've since made everything manual regarding email, and motweets updates once every 15 minutes and the amount of tweets is limited so it's not a lot..
Still, I run into this problem, and I've made sure it wasn't a program updating but I can't think of what else would make this happen, am I the only one??
Is it because there's a way to clear cache on internets and other programs and I have no idea how? (I fully close them, that's not the problem, I know my Vogue I just can't figure this out an it seems nobody else has this problem).. Not to mention I have my internet cache's directed to my storage card so as to keep my phone memory as free'd up as possible
If anyone can help..
Click to expand...
Click to collapse
j18yo i think that your problem might be that to many programs run when you start your vogue that happened to me before and i hated it but then i heard of a program named "Space Reclaimer" FREE and it made my vogue much more responsive because the program stops any programs that start when you turn on your vogue or any windows mobile phone
I have the same problem usually under the same conditions. Mostly happens in the morning after the device has been off. Works fine for a few seconds then stops responding correctly i.e., the D-Pad stops scrolling correctly with a lag on touch response. I use CleanRAM and it still doesn't fix the prob once it occurs. Sometimes when I run CleanRAM it will occur. I've tried putting biotouch.exe and everyting BUT the kernel processes in the exceptions list and a Level 1 clean. Hard reset yesterday and haven't had the problem yet. If it continues to work, I'll post my settings.
BTW, I'm on a stock 6.1 ROM with a few apps.
j18yo said:
I had one before, dropped it a few times.. I wrote it off as that being why, well I just got a replacement one sent.. haven't dropped it once, it's been here only about 2 weeks
Randomly sometimes it won't respond to almost anything.. I'll be trying to slide the screen, it either won't at all or will go halfway like I barely touched it. I'll try clicking on things, programs, start, whatever... it'll not respond at all, I end up having to press with way more pressure than I should have to, way more.
Then sometimes without even a reset it'll start working just about normally again.. but that's rarely, usually I'll soft reset or pull the battery for a second and then it'll be fine.. for days even.. then I'll run into it again..
I noticed 2-3 times it was because I had **** updating at the time (motweets) or was receiving email.. but I've since made everything manual regarding email, and motweets updates once every 15 minutes and the amount of tweets is limited so it's not a lot..
Still, I run into this problem, and I've made sure it wasn't a program updating but I can't think of what else would make this happen, am I the only one??
Is it because there's a way to clear cache on internets and other programs and I have no idea how? (I fully close them, that's not the problem, I know my Vogue I just can't figure this out an it seems nobody else has this problem).. Not to mention I have my internet cache's directed to my storage card so as to keep my phone memory as free'd up as possible
If anyone can help..
Click to expand...
Click to collapse
What ROM are you running? I asume that wehn your new device came you loaded it the same as the old one. It has to be something with the ROM you are runnning or a problem with a program causing your issue.
My phone would do this periodically too, with Vin's latest ROMs. I turned off Manila and am running Titanium now. Interestingly - no lags when unlocking since. I'll keep Titanium on for some time to see if that makes it go away. I had an issue with both his current v2 and v4 (which I am running now).
Ive had to replace my screen twice and the whole phone once because of touch screen problems. Thank God for the insurance.
Ah yes... to what OP mentioned:
I do not beleive it is a more pressure thing. I do not think it is more pressure that is required but rather that the phone is non responsive. If you are unlocking and typing a PIN, it takes the PIN and all but it takes perhaps one digit every 5 seconds. That's my experience anyway. So it is just slower, as if something was consuming the CPU and UI is not responsive.
crazylegs91 said:
I have the same problem usually under the same conditions. Mostly happens in the morning after the device has been off. Works fine for a few seconds then stops responding correctly i.e., the D-Pad stops scrolling correctly with a lag on touch response. I use CleanRAM and it still doesn't fix the prob once it occurs. Sometimes when I run CleanRAM it will occur. I've tried putting biotouch.exe and everyting BUT the kernel processes in the exceptions list and a Level 1 clean. Hard reset yesterday and haven't had the problem yet. If it continues to work, I'll post my settings.
BTW, I'm on a stock 6.1 ROM with a few apps.
Click to expand...
Click to collapse
THIS..
It has to be the problem.. I have CleanRAM run every 12 hours or 6 hours because I figured it would help.. lol but now your saying sometimes it happens WHEN you run cleanRAM.. Im assuming it does something, or erases something it shouldnt?
This is like the 1 sole thing I have run on a schedule, I've turned off my email and everything to manual, I went into my startup folder and there was about 4-5 things I didn't need which made the battery 100% better than it was in terms of how long it lasts.. and I set-up this CleanRAM schedule on my last phone I THINK I forgot but I do know as soon as I got this 1 going I did it and I'm bout to delete the program completely and see if it'll help, I have speedbooster too which does a cleanup too I'm curious if it would have the same result..
I'll let everyone know if this ended up being my problem incase anyones in the exact same boat with the same apps
PS: I was doing level 3 cleans
j18yo said:
THIS..
It has to be the problem.. I have CleanRAM run every 12 hours or 6 hours because I figured it would help.. lol but now your saying sometimes it happens WHEN you run cleanRAM.. Im assuming it does something, or erases something it shouldnt?
This is like the 1 sole thing I have run on a schedule, I've turned off my email and everything to manual, I went into my startup folder and there was about 4-5 things I didn't need which made the battery 100% better than it was in terms of how long it lasts.. and I set-up this CleanRAM schedule on my last phone I THINK I forgot but I do know as soon as I got this 1 going I did it and I'm bout to delete the program completely and see if it'll help, I have speedbooster too which does a cleanup too I'm curious if it would have the same result..
I'll let everyone know if this ended up being my problem incase anyones in the exact same boat with the same apps
PS: I was doing level 3 cleans
Click to expand...
Click to collapse
Update: I don't think CR erases things as much as it kills processes that won't restart. Thru trial and error, I've adjusted my CleanRAM settings to where I haven't had the problem for a couple of days. I'm able to do a Level 3 cleans on a once a night schedule and during the day if need be. In settings, I have it to close all apps, launch startup progs, and display today screen. I have no exceptions listed for either running progs or startup progs. I have the most up to date version from the OTA update in the program.
The program links in my StartUp folder are: poutlook (original on ROM), sddaemon (original on ROM), WLMUpdate (original on ROM), Glossybars.exe (I added this), biotouch.exe (I added as I thought CR killing this was the source of the problem), pocketwit.exe (I added), and SIPChange (I added).
One thing I did do was delete the link for TouchPal from the Startup folder. I did this for other reasons (I use FingerKeyBoard). Not sure if this was part of the problem.
I can scroll with d-pad and no touch lag.
On a side note, can I delete any of poutlook, sddaemon, or WLMUpdate from the startup folder to save battery power?
I'm probably just a bit above a newb so sorry if I don't make sense.
Update: Just for kicks, I deleted the links for glossybars.exe and pocketwit.exe from my StartUp and it started locking again after running CleanRAM. I put them back in and it works again even after running CleanRAM. Maybe someone with more knowledge can explain this. I'm just keeping it the way it is now...
Hmm weird that you removed something not very important like pocketwit an cleanram caused problems again.. someone has to have some info on this??
I deleted everything from my StartUp folder but my SPB Mobile Shell.. I didn't have sddaemon, but I did have poutlook and WLMUpdate both of which I deleted.. then I had some other programs that aren't necessary for the phone.. I have no problems on restart or anything, and the % showed being used is stays around the 30's now instead of 40s/50s.. and when I run programs it usually reachs 50% tops now instead of 60/70% I used to get.
PS: Pocketwit isnt bad I used to praise the program but now I've tried MoTweets and.. I can't think of the other one now.. ****.. it's really good though but it seems to use a lot more phone power than MoTweets so I went back to that.
Pocketwit kept giving me problems, started saying I need to install that NET 3.5 or whatever but when I try to it says I have a later version already so it won't install, then other times it'll work completely fine.. but MoTweets I like better anyways
Ok, I give up. I restored everything to the way I had it when it was working and now I'm having problems again. After the screen turns off and I turn it back on, it locks up and won't scroll and has the touch lag issue.
Hope someone figures this out. Shouldn't have messed with success. Good luck.
crazylegs91 said:
Ok, I give up. I restored everything to the way I had it when it was working and now I'm having problems again. After the screen turns off and I turn it back on, it locks up and won't scroll and has the touch lag issue.
Hope someone figures this out. Shouldn't have messed with success. Good luck.
Click to expand...
Click to collapse
Are you running TouchFLO?
As mentioned before -for me, turning off TouchFLO (and running Titanium) fixed this 100%...
bigboy292000 said:
Are you running TouchFLO?
As mentioned before -for me, turning off TouchFLO (and running Titanium) fixed this 100%...
Click to expand...
Click to collapse
I'm running a stock Sprint 6.1 ROM. Thanks though.
bigboy292000 said:
Are you running TouchFLO?
As mentioned before -for me, turning off TouchFLO (and running Titanium) fixed this 100%...
Click to expand...
Click to collapse
I'm not using the TouchFLO interface, does that mean its still on though?
I'm not completely up on understanding all this
This was happening with Vin's Rom for me as well. I was tripping out pressing ON so many times with no screen showing up but phone light on! I believe it could be the power settings. I disabled the "Turn off device" which I believe was mentioned in his notes about the rom.
I gave up on this problem for a while but found something when researching how to disable to cube. I used the registry edit in this thread to disable to cube post #69. I didn't do any of the other steps because I'm not having memory probs (42% with pocketwit in the bckgrd).
http://forum.xda-developers.com/showthread.php?t=368269&page=7
I noticed that biotouch.exe never shows up in the running processes menu in CleanRAM and I don't have the "lock/freeze" scrolling problem any longer and I can run CleanRam without the problem occurring. I can press any item on the screen as well with no delayed response.
However, this stops you from being able to finger scroll and do the "side to side" scroll in Messaging. I never really finger scrolled and prefer using the d-pad for scrolling so losing that functionality isn't a big deal to me.
If anyone can figure out how to keep this working so smooth and have the option to finger scroll, I'd be much obliged. It just seems that biotouch.exe craps out sometimes and locks up the d-pad. If they could both work equally well....
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.
Hey guys,
I've been having issues with the Widgetlocker lockscreen recently, and was wondering if any of this will ring a bell with someone.
I recently flashed the KJ2 2.3.5 ROM (the XEU non-wipe Frankenstein one), and i've also flashed CF-Root and then the Speedmod kernel. I'm in the UK, on O2 (debranded to XEU) and i have no issues with the phone whatsoever. I even get great battery life. It's just this damn widgetlocker issue that's grating on me!
For some reason when i wake the phone up and try to unlock it by using the slider (i just use the default 'Android' one for unlocking - the only other things i have are a couple of widgets for missed calls & texts and a battery % one) a lot of the time the slider does not repond to touch. It doesn't always happen, but maybe a good one out of every three times it happens. And the weird part is, if i then just wait about 5 seconds, then it suddenly responds and i can unlock the phone. Obviously having another 5 seconds on top of the already present lag when pressing the home button is not good, and because of this i'm thinking of not using WL anymore.
I've been through all of the settings, i'm almost 100% sure it's not something in there. Can anyone help with this?
Cheers guys.
Happens with me too sometimes. Another issue is if you keep pressing Menu button 4-5 times the phone gets unlocked and takes you to the home screen.
Hey, just wanted to post that i finally figured out what the problem was.
I'm using an .apk to help with the touchscreen sensitivity. See vitalij's thread here:
http://forum.xda-developers.com/showthread.php?p=18999801#post18999801
Well it turns out on 2.3.5 vitalij's .apk has some issues with the most up-to-date superuser. The solution, so far, isn't great but gets the job done, is to uninstall the .apk, and then re-install. The important part is not to click on 'enable service' in the app! So basically each time you want to use the app you have to open it and hit 'apply' on whatever setting you need. The setting will work until you next turn the screen off. For me this workaround is actually ok, as the only time i ever really used it was for the odd game, so i'm happy to just do it manually on these occassions.
disable root helper
madrano, can you expand on what you mean by this? i have tried enabling & disabling root helper but if i remember correctly the problem was still there.