Related
I'm having a couple off issues with the latest release.
First of all I can't turn Wifi off and keep it off. Everytime I go into the menu to check on it, it's checked, so I uncheck it, and it'll turn off for a minute or two and then all of a sudden turns right back on. This is extremely annoying.
And the other is that it seems like in some apps my touchscreen presses don't keep the phone awake. So I can be interacting with the screen and then all of a sudden it'll go dim. I'll keep pressing on screen buttons and a few seconds later the display will shut off completely. The only way I can jog it back awake in its dimmed state is to move the trackball or press some other hardware button.
Anyone else seen these problems?
LPChris said:
I'm having a couple off issues with the latest release.
First of all I can't turn Wifi off and keep it off. Everytime I go into the menu to check on it, it's checked, so I uncheck it, and it'll turn off for a minute or two and then all of a sudden turns right back on. This is extremely annoying.
And the other is that it seems like in some apps my touchscreen presses don't keep the phone awake. So I can be interacting with the screen and then all of a sudden it'll go dim. I'll keep pressing on screen buttons and a few seconds later the display will shut off completely. The only way I can jog it back awake in its dimmed state is to move the trackball or press some other hardware button.
Anyone else seen these problems?
Click to expand...
Click to collapse
I've seen similar issue with the screen staying awake, thought it's just the phone. Also not sure if it's related sometimes I'll click on a button for example, but it will almost not recognize the spot i'm clicking on and click something else on the screen.
These are the same problems I've been seeing on my phone. I imagine it is due to the multitouch hack, but I haven't gotten the motivation to downgrade my phone back to 1.31.
Do you have anything installed like power manager or locale? One of those progams may be turning on wifi.
Dharkaron said:
Do you have anything installed like power manager or locale? One of those progams may be turning on wifi.
Click to expand...
Click to collapse
Nope, I had installed Power Manager once a while back and didn't like how it worked so I uninstalled it. Don't have Locale installed either. I ran the task manager to see what was running and there was nothing that I could tell that would turn the wifi on.
The touch issues are rather widespread amongst 1.41 users. However, don't know what's up with ur wifi. I have a strange issue with my wifi as well though. Whenever I boot up my phone and wifi was enabled when it turned it off. I get 2 not responding errors. Everytime. Its like clockwork. With 3g? Never. It took me about 20 wipes and 10 or so hours to finally figure it out. Hopefully all these problems will be fixed with rc33
I have also noticed that Applications don't check for new updates anymore. even when I go to "My Downloads", It used to show "free" next to any application that has an update or has been uninstalled. Now it shows "Installed" next to all the applications but when I go to the application by category, It shows up as "Free" meaning that there is a new version.
the case in simple points:
1. when I open the Application..... It doesn't detect the update.
2. when I go to "My Downloads" in the market, It doesn't show "Free" next to any application that has an update.
But if I go to the application by category, It shows "Free".
LPChris said:
I'm having a couple off issues with the latest release.
First of all I can't turn Wifi off and keep it off. Everytime I go into the menu to check on it, it's checked, so I uncheck it, and it'll turn off for a minute or two and then all of a sudden turns right back on. This is extremely annoying.
And the other is that it seems like in some apps my touchscreen presses don't keep the phone awake. So I can be interacting with the screen and then all of a sudden it'll go dim. I'll keep pressing on screen buttons and a few seconds later the display will shut off completely. The only way I can jog it back awake in its dimmed state is to move the trackball or press some other hardware button.
Anyone else seen these problems?
Click to expand...
Click to collapse
i havnt had a problem with it staying on, i noticed that my phone was dimming to quickly. I know theres probably an adjustment somwhere (i think at least) but i havnt had any problems what so ever with it.
Very strange. I haven't had either problem (wifi or touchscreen). I have noticed that my battery drains more quickly than it used to, but I have been blaming this on the DroidSans autorotate feature always flipping the screen everytime I move the phone (I mess with the phone an awful lot).
Droidsan
I can not get auto rotate on JF RC-33. Does anyone have this problem???
another issue with with this version was that all my ringtones were changed for my contacts and stuff
pretty wierd.
i don't have any problems mentioned ATM.
JF RC30 to RC33
stonefurry said:
I can not get auto rotate on JF RC-33. Does anyone have this problem???
Click to expand...
Click to collapse
DroidSans Tweaks checks the version. At the moment it's not going to recognize RC33 as a valid version. Wait for it to be updated.
danguyf said:
DroidSans Tweaks checks the version. At the moment it's not going to recognize RC33 as a valid version. Wait for it to be updated.
Click to expand...
Click to collapse
What he said... But don't forget to enable auto rotate in your browser though. You don't need droidsans for that.
Hello,
After rooting my G1... I've noticed I cannot lock the phone by pressing the red button. I can unlock the phone fine using MENU (or now the Lock 2.0) application, but I have been unable to lock by pressing the red button since I rooted/changed the firmware.
Also, I've had problems with text messages sending (sparadically) and issues with the Market downloading applications without having to reboot the phone.
I do have the most up to date Radio firmware from HTC.
Any ideas?
Thanks,
Jeff
What does it do when you press the red button?
And whats the deal with that poll? Doesn't seem related. You also missed some choices that might be more popular... i.e. 2 days, 3 days, 5 days.
My phone has been crashing sparadically, force closes. For the past two days pressing end called asked me to set a default action, for which there was only two options "Home" and "Lock 2.0 (WARNING DO NOT CHOOSE THIS) or something to that effect. When I chose home, the button did absolutely nothing, but I never chose Lock. I have not disabled lock, intentionally... But running "Backup for Root Users" wiped my contacts, e-mails, sms, all application settings, my google account, everything.
So go figure.. that somehow fixed the locking issue, but my phone is still far from stable.
I can't imagine anyone getting 24 hours of battery life without plugging it in. I have the original HTC battery and a generic battery too, no luck.
I have GPS and Wifi disabled, brightness down low. I have 3G disabled as well.
Any ideas?
Thanks,
Jeff
First of all do a wipe on the phone. If that does not fix it I would re-flash the rom that you are using and wipe. Hope that helps.
if your running jf 1.51 there should be a app called spare parts if you go into that app there is a section that allows you to pick wut the end call button should do whether it be go to the home screen turn the screen of or both
NYSteeler you star! I completely forgot about that option in Spare Parts!
Just installed cyanogen's latest ROM and I was having similar problems. For some reason when it was set to 'Home then Sleep' the red button does nothing. But when set to just 'sleep' it locks the phone as it should!
There's probably a conflict somewhere... but I can do without the hassle of add/removing apps one at a time to see which one it is! And I can live with having to push 'Home' then 'End'.. It's easier than waiting for the screen to timeout!
And who on earth is getting more than 24hrs out of their G1 battery!? Maybe if you leave it at home for the day...! I get about 12-13 at the most out of mine.
I'm having issues where after going to sleep, it wakes up with the lcd very dark. It doesn't matter which level of brightness I put it on, the lcd is still hard to see. Rebooting solve the problem. Just wondering if anyone experienced this too. I hope it isn't my lcd dying...
This happen on both froyostone and bangster. I'm on the latest radio using tmousa.
I had this on bangsters 1.2, but haven't seen it on 1.3b, but only been running that build for a few days.
azzzz said:
I'm having issues where after going to sleep, it wakes up with the lcd very dark. It doesn't matter which level of brightness I put it on, the lcd is still hard to see. Rebooting solve the problem. Just wondering if anyone experienced this too. I hope it isn't my lcd dying...
This happen on both froyostone and bangster. I'm on the latest radio using tmousa.
Click to expand...
Click to collapse
i had this a few times before on a shubi build. I came to the conslusion that it is the screen not fully coming out of sleep. Seeing as it only happened when I put the phone to sleep and then tried to wake it immeadiately or got frustrated and impatient with it and tried tapping buttons repeatedly until the screen came on.
palosjr said:
i had this a few times before on a shubi build. I came to the conslusion that it is the screen not fully coming out of sleep. Seeing as it only happened when I put the phone to sleep and then tried to wake it immeadiately or got frustrated and impatient with it and tried tapping buttons repeatedly until the screen came on.
Click to expand...
Click to collapse
I had this same experience. Patience is a virtue with these phones. As long as I wait if its taking a bit to come out of sleep, I get zero problems.
Sent from my HTC HD2 using XDA App
thanks for the advice. I hope its just a software glitch. I will just have to be more patient when coming out of sleep.
My solution
azzzz said:
I'm having issues where after going to sleep, it wakes up with the lcd very dark. It doesn't matter which level of brightness I put it on, the lcd is still hard to see. Rebooting solve the problem. Just wondering if anyone experienced this too. I hope it isn't my lcd dying...
This happen on both froyostone and bangster. I'm on the latest radio using tmousa.
Click to expand...
Click to collapse
Here is my solution, i posted it in a similar thread, I think the key element here is the bsb tweaks part, hope it helps, thanks:
I solved this problem in my phone.
even turn on/off/on/off/on/off etc the screen, the devices wakes up correctly every time.
I don't really what exactly fixed but.
i installed Miris romm 20.0, then i turned off the auto screen off *start/system/power, so the screen nevers dims or turn off. I turned off the charge the device when it is connected to the computer, turned off quiet pickup, turned off 3g.
and now i think this is the key, installed bsb tweaks and turned off everything(even power savings), disable data connections and screen rotation, I only left use high glymp cache. reboot and run android, in winmo i dont have anything installed besides bsb1.6
in android i have the task killer on and set cpu at 768mhz ondemand. no profiles. battery last well over 24 hrs moderate use. by the way im using shubcraft, and the gsensor disabled kernel. thanks,
edit: also my auto sync is off in android and my wifi is always on.
I dealt with the problem by putting a widget to control screen brightness on my home page, if it goes dim I can find it ' blind'
Sent from my HD2 on mattc froyo sense.
Yeah it does happen to me if I'm being impatient and banging on the screen before it fully wakes up. Haven't found a real solution yet, but so far I would just try my luck by turning on/off/on/off several times, hoping that it get stucks momentarily again to let if "fully" wake up. Worst case scenario, reboot.
SOD and random screen freezes has been bothering me almost always. I was reading all over the xda, different complains and strange solutions for them. I almost tried all of them and NONE is REALLY working (at least for me).
Recently I notice that when I wake up my phone (with yes button) after turning on, LCD immediately turns off. I mean after waking up the lcd, even if it is awake and responses to screen touch (even I can unlock it) but the LCD is off!!!! in this situation if I continue touching the screen it comes to life after couple of seconds and if not it goes back to sleep mode.
I wanted to see if anybody else has experienced same thing and If there is any solutions for it or not.
my android is HyperDroid http://forum.xda-developers.com/showthread.php?t=769026
and my kernel is hastarin http://forum.xda-developers.com/showthread.php?t=787588
I assume you are using the auto backlight...
If so search the problem is discussed in the hyperdroid thread.
Hold up to a bright light when that happens.
hold up to a lightbulb and then turn of autobrightness.
joseph230 said:
SOD and random screen freezes has been bothering me almost always. I was reading all over the xda, different complains and strange solutions for them. I almost tried all of them and NONE is REALLY working (at least for me).
Recently I notice that when I wake up my phone (with yes button) after turning on, LCD immediately turns off. I mean after waking up the lcd, even if it is awake and responses to screen touch (even I can unlock it) but the LCD is off!!!! in this situation if I continue touching the screen it comes to life after couple of seconds and if not it goes back to sleep mode.
I wanted to see if anybody else has experienced same thing and If there is any solutions for it or not.
my android is HyperDroid http://forum.xda-developers.com/showthread.php?t=769026
and my kernel is hastarin http://forum.xda-developers.com/showthread.php?t=787588
Click to expand...
Click to collapse
Not only hold it up to a bright light, but once the screen comes back on go insto display settings and turn off the auto brightness. If our using hyperdroid you should try phiremod CM6
I had this problem. I also search xda to find solutions. The only thing that worked for me was to update to the latest radio. 2.15.50 if you havent tried that already
good luck
cs378 said:
I had this problem. I also search xda to find solutions. The only thing that worked for me was to update to the latest radio. 2.15.50 if you havent tried that already
good luck
Click to expand...
Click to collapse
My Radio is 2.15 already.
I will try the bright bulb and turning off the auto balcklight to see wat happens. I hope it fix the problem. I will report back with the result.
Thank you everybody for the replies. I really appreciate it.
For EVO kernels, screen backlight turns off when brightness value is set lower than 30. Meanwhile the default lowest autobacklight level is 20. If you use a Cyanogenmod build, the levels can be adjusted, but the "screen dim level" cannot be set to values greater than 26.
The best solution would be lowering turn-off threshold in backlight driver to 20 or less.
RobertsDF said:
hold up to a lightbulb and then turn of autobrightness.
Click to expand...
Click to collapse
Thank you.
I used the trick and when I turned the auto balcklight off, it seems that my problems are gone.
AMCJUNGLE said:
Not only hold it up to a bright light, but once the screen comes back on go insto display settings and turn off the auto brightness. If our using hyperdroid you should try phiremod CM6
Click to expand...
Click to collapse
Thank you , the tricked worked
About PhireMod, I switched to it and till now LATE WAKE UP time is gone. It is waking up very fast and normal. Of course it had the same auto backlight problem which got fixed by disabling it.
Also for me HyperDroid was not giving me bluetooth and it was causing the phone process to FC. But PhireMod successfully passed the bluetooth test and I am using it now.
Thank you again for hints and suggesting the PhireMod.
I tried searching if this happens to anybody else, but couldn't find it. Since I updated to lollipop (I put original polish rom first via odin) whenever my auto brightness is turned on, when I wake the phone using home key or power button, my screen turns on with full brightness for a half second or something like that, and than goes back to normal.... I thought it was a bug on polish ROM, so I flashed austrian rom, but no improvement. Now I have custom TW rom, and it is still the same. When I turn auto brightness off, it doesn't happen. So I suspect it to be that screen turns before the light sensor on unlock, and it is set to full brightness always. is there some file I can edit, so screen starts at lowest brightness or delay screen start for half a second so the sensor can start first.
It is killing me when I get a message while sleeping in a dark room, and I want to check it, it blinds me so I wake up, and can't go back to sleep later!!!
LOL I have the same problem, which is extremely irritating to say the least, but I had no idea that it had to do with auto brightness! I am on latest AryaMod, which is stock TW based ROM, so I guess its a problem of all the TW releases?
Don't know! I will ask this in AryaMod topic and see whether dev will be more than kind to provide us a solution. Thanks for creating the topic, I had thought about it a lot of times, but was never intrigued enough.
neky92 said:
I tried searching if this happens to anybody else, but couldn't find it. Since I updated to lollipop (I put original polish rom first via odin) whenever my auto brightness is turned on, when I wake the phone using home key or power button, my screen turns on with full brightness for a half second or something like that, and than goes back to normal.... I thought it was a bug on polish ROM, so I flashed austrian rom, but no improvement. Now I have custom TW rom, and it is still the same. When I turn auto brightness off, it doesn't happen. So I suspect it to be that screen turns before the light sensor on unlock, and it is set to full brightness always. is there some file I can edit, so screen starts at lowest brightness or delay screen start for half a second so the sensor can start first.
It is killing me when I get a message while sleeping in a dark room, and I want to check it, it blinds me so I wake up, and can't go back to sleep later!!!
Click to expand...
Click to collapse
Same thing here mate. I noticed that this happens to all 5.0 rom and currently I am using ported 5.0.1 rom and it went well.
shchiam1978 said:
Same thing here mate. I noticed that this happens to all 5.0 rom and currently I am using ported 5.0.1 rom and it went well.
Click to expand...
Click to collapse
I tried flashing 5.0.1, but it didn't fix it, I also have a problem with screen not turning off during calls now, which rom are you using?
neky92 said:
I tried flashing 5.0.1, but it didn't fix it, I also have a problem with screen not turning off during calls now, which rom are you using?
Click to expand...
Click to collapse
I am using death note.
Now I am back to Arya to test the battery life.