The button lights are OFF..?!? - HD Mini General

Hi everyone.
Today i installed an app called startup cleaner pro from android market...with this app u can choose which apps will be started up on android booting....so i selected a few and it stopped 22 other system + user apps from starting when i booted up my droid..the first thing i noticed is that the lights which are ALWAYS on in our touch buttons were OFF...and they remain off even when u touch them...but the buttons are WORKING properly...
Hope this helps

that's not something out of common...when i run android sometimes button lights stays always on,sometimes always off lol,so it's not software related,it's just wrong code which must be fixed

This had never happened with me...not once...but since i stopped some of the system services...button lights are always off..!!...and i have restarted my phone like 10-12 times...and lights have not started in droid everytime..

Same behaviour here. Now the lights are always off.
Moreover, when I press the power button and the screen is black, the phone doesn't wait some seconds anymore and it turns on immediatly.

asorcinelli said:
Same behaviour here. Now the lights are always off.
Moreover, when I press the power button and the screen is black, the phone doesn't wait some seconds anymore and it turns on immediatly.
Click to expand...
Click to collapse
What you may want to consider (but what will be a time consuming job I guess) is to test which process/app does make the difference.

I think that tzacapaca was right.
I'm trying to identify the service or services that force the lights on, but I can't because now I have always the lights on.
I have reboot multiple times, without any changes. It's strange because the first time that I have disable the startup services, I have reboot many times and all the times the lights are off.

guys think logical..it cannot be because of software or services..lights on/off are commanded by OS,in my opinion..
developers correct me if i'm wrong

tzacapaca said:
:
guys think logical..it cannot be because of software or services..lights on/off are commanded by OS,in my opinion..
developers correct me if i'm wrong
Click to expand...
Click to collapse
Software and services do give command to the OS. It may be that some of the services are giving commands to the OS (for example: turn on 3G) which are misunderstand by the OS (for example: turn off lights).

pietje63 said:
Software and services do give command to the OS. It may be that some of the services are giving commands to the OS (for example: turn on 3G) which are misunderstand by the OS (for example: turn off lights).
Click to expand...
Click to collapse
about software.. when you install naked android there is just astro and superuser and i dont think these programs will give commands to buttons to turn off the light
about services...they are part of OS..so OS and kernel is written using some codes..anyway i'm pretty sure this is kernel's fault which needs to be patched.
p.s. btw are u a developer?
p.s2. robin can tell us for sure,he is the one

Nope, I'm not a developer, but I have some programming knowledge. That why I said 'it may be'.
And I agree, it will most likely be the kernel which is wrong here (that what I tried to say with 'which are misunderstand by the OS'). But if we find out which command is misunderstand by the kernel, we may find out where the error in the kernel is. Or not?

Related

Issues with JFv1.41

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.

Power control of the Vogue

Maybe this shows that I am a noob, but here it goes.
I want to save my battary power when running the GPS, but all the power saveing settings turn the phone onto standby, thus loosing GPS lock (and when I am using my better bluetooth GPS, it locks out the bluetooth and I have to re-boot). Is there some why to just turn of the screen? Is that "an app for that"? I am currently trying out SVM Power Manager, but you can not set it to turn the screen off in 2 minites or whatever. To use it how I need, I would have to turn off the OS's power saver, and always manualy turn off the screen using SVM Power Manager. All the power manager apps I have seen work like that.
Help!
you will probably have to buy an extended battery man. i think even real android phones batteries drain pretty quick from what i hear.
Did some testing. It seems that the battery will last for about 5h with the screen of (using SVM Power Manager to turn it off), and the GPS running (GPSed running it).
Understood that the battery is just under powered, but I was wondering if there was a way to make the screen automaticaly turn off after X amount of time, but not have the phone go into standby.
I also bought one of those battery powered battery chargers (battery extender). But the one I got turned out to have only 500mAh (compared with 1100mAh in the phone battery), so it turned out to only help a bit. Maybe I will try to make one with a voltage regulator and a rechargable 9V battery
I think one of the pmsleepmodes may support this (in default.txt) Try 2 or 3. It seems like one of these didnt do a full power collapse, but did turn the screen off.
katmandu421: I am not familiar with this stuff. Can you give me a bit of a more detailed explination?
Is this a built in windows mobile funciton. Can I access this in the registry?
I love it how most of us would assume he's talking Android. Yes in android, editing your default.txt to sleep mode 0 would turn off the screen, but not sleep the system. 1,2, or 3 would allow the different system board types used in various Vogues to go to sleep.
WinMo however is a different story. The GPS in the Vogue is a low power chip, but from everything I can gather is requires the system to stay fully awake. If you find an app that allows you to turn off your screen, post back but I don't believe there is much hope to that. Windows seems to think that when the lights go out, it's sleepy time.
Also, the radio on the Vogue doesn't sleep, and it's use to wake up the phone i.e. incoming calls. The GPS is part of the radio so if there is a way to keep the system board awake, in theory it should work.
SVM Power Manager will turn off the screen while keeping everything awake, but it is not automatic. I have maped the camera button to this program, so it is not a huge hassle, but I realy would like to have it automatic.
Will consider installing Android.
Titus_Andronicus said:
SVM Power Manager will turn off the screen while keeping everything awake, but it is not automatic. I have maped the camera button to this program, so it is not a huge hassle, but I realy would like to have it automatic.
Will consider installing Android.
Click to expand...
Click to collapse
Did anyone ever figure out how to do this? I'm trying to figure this out as well. After finally getting GPS to work, now I'd like to be able to use some apps that need to run when in standby.
mnations said:
Did anyone ever figure out how to do this? I'm trying to figure this out as well. After finally getting GPS to work, now I'd like to be able to use some apps that need to run when in standby.
Click to expand...
Click to collapse
Check on Dev&Hacking. An app just came out today that does exactly what you are asking for here.
http://forum.xda-developers.com/showthread.php?goto=newpost&t=707458
Enjoy
egzthunder1 said:
Check on Dev&Hacking. An app just came out today that does exactly what you are asking for here.
Enjoy
Click to expand...
Click to collapse
Thanks! That looks like a handy app.
An update (in case anyone hits this thread later)...I made this one change which seemed to clear up all of the problems (found elsewhere but can't post outside link yet.)
[HKEY_LOCAL_MACHINE\Comm\ConnMgr\Providers\{7C4B7A3 8-5FF7-4bc1-80F6-5DA7870BB1AA}\Connections\Phone as Modem]
"Enabled"=dword:00000000"
Now this is in conjunction with QuickGPS and all the other fiddling I've done, so I don't if this alone is responsible.
However, when running Google Maps or other GPS applications I get a lock within 5-15 secs. Also, when coming back from standby it's able to re-lock in the same amount of time. This normally required a soft restart before.
For apps that track your routes, such as SportyPal which I've been using for mapping my bike rides, they can keep a lock even in standby mode. I'm not sure if the app itself is able to hold a lock or if QuickGPS may be helping it. Either way it works.

Disable Hardware Buttons

Hi All,
in the company I work for we use a range of XDA's for our drivers, the current and most popular one is the HD2, however i have noticed that drivers are able to put the XDA to standby, normally this is a requirement, however for the system we are using it causes major issues and provides the driver a way to cheat the system.
What im looking for it a way to disable the hardware buttons when the device is switched on, i imagine there may be a registry edit, but im not sure and need help as this is becoming a pressing issue.
Thanks
M
Your request is very peculiar, and I seriously doubt that you can achieve something like that, after all completely disabling the hardware buttons can impair seriously the functionality of the device and I don't think there is a pre-set method to do that.
Anyway, I've seen a thread that talked about reassigning the shortpress on power button to something else (and I'm talking about shortpress, not longpress), yet this didn't work on the HD2 when I tested it this morning.
Anyway, if your system is debunked by putting the device in standby, it will also troubled by simply removing the battery. In other words, you can put a strong password to forbid a user from turnning off a pc from the start menu, but you cannot forbid this user from pulling the plug off the mains
Anyway, a very feeble solution could be making so that whatever is that's thrown off by the standby, keeps working even in standby; there's a tweak for wifi that allows wifi radio to stay on during standby, and probably forcing the wifi always on, and tweaking it from bsb to be on even during standby, it will also force the CPU of the device to be on even if you lock the phone by press endkey
Dont really want to give too much away, but our application uses gprs/3g and gps constantly, and by going into standby it loses connection with our servers and gps, thus allowing users to go standby in one area and then turn back on somewhere else but system thinks they are in area 1 until they move to antoher area again. this causes a major issue and headache for me, so what i really need is for the app to remain live when in standby and to keep the data and gps connection live
hope that makes sense
Hi,
These threads may help:
http://forum.xda-developers.com/showthread.php?p=6417238
http://forum.xda-developers.com/showthread.php?t=661472
had a look at those links and the second won looked like a winner, but when hit the HW power button the device still goes off, however i noticed that it kept its gprs connection, but it still lost gps which is one of the main factors. Just need some way to stop the device from turning off, apart from removing the case and then removing the buttons
railto said:
had a look at those links and the second won looked like a winner, but when hit the HW power button the device still goes off, however i noticed that it kept its gprs connection, but it still lost gps which is one of the main factors. Just need some way to stop the device from turning off, apart from removing the case and then removing the buttons
Click to expand...
Click to collapse
try this:
Change this with your registery
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Contro l\Power\State\Resuming]
"gps0:"=dword:00000001
"gpd0:"=dword:00000001
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Contro l\Power\State\Unattended]
"gps0:"=dword:00000001
"gpd0:"=dword:00000001
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Contro l\Power\State\Suspend]
"gps0:"=dword:00000001
"gpd0:"=dword:00000001
Normaly the numbers are on "4" - put this on "1" and gps should stay awake even when you put the phone in standby.
It will stay on until a program stops using the gps.
found it here
http://forum.xda-developers.com/showthread.php?t=676267
railto said:
had a look at those links and the second won looked like a winner
Click to expand...
Click to collapse
It's the first one you should try. Works fine for me.
http://forum.xda-developers.com/showpost.php?p=6416870&postcount=6
But frankly if they do it on purpose they will no doubt find other ways to do it - so you should rather build in some protection in your software to detect it, like if 2 consecutive positions are at the same place but with more than a certain amount of time apart, it's that they turned the thing off / cut connection on purpose/...
EDIT: wilcovh beat me to it.
those reg edits have been confirmed not to work... at the time being there is no way to have the GPS stay on while in standby, and that's a pity. I am personally interested in this and have researched in the forums, yet no working method was devised (yet). And I would love to be corrected by someone, but all the solutions I found were app specific (as in, app turns off screen without turning off GPS).
So, unless the drivers should have a personal reason to "cheat" the system by turning off the GPS, just instruct them not to press that button
If they just want to turn off the display, you can make it so that they do just that without actually locking the device, by associating, as I did, longpress on send key, with xdashutdown /lightsout command. That will turn off the screen but the phne won't be locked nor put to standby.
the theory of having gps active while on standby is moot and now useless, i need to stop the device going into standby mode period
to my best knowledge you can't really do that; I mean, you can programmatically disable automatica standby in an app by calling a function to reset the idle timer, yet the power button will put the device into standby.
I'm almost positive neither AEbutton plus can remap the power button short press on the HD2, but giving it a try won't hurt that much
railto said:
the theory of having gps active while on standby is moot and now useless, i need to stop the device going into standby mode period
Click to expand...
Click to collapse
other approach:
app that wakes up the device after a minute or so? the gps only disconnects for short time.
railto said:
the theory of having gps active while on standby is moot and now useless, i need to stop the device going into standby mode period
Click to expand...
Click to collapse
But that's solved already!
The keepAwake app posted earlier, music players keeping playing when pressing the off button, IM clients continue to run and receive messages after pressing the power button (implies both processor running and internet connection active)... in these cases, like any app that does the required system calls to disable standby while it's running, the device won't go to standby.
The only real problem you're facing is that GPS goes off when the power button is pressed, regardless of whether the rest of the device actually goes to standby or not (try running a GPS app while playing music, press power button, music still plays but GPS turns off).
Now we pointed some hints for you - you can try them (the reg edits for GPS apparently work in some cases but not all), but if they don't work then you're alone on that one, no solution is known. And tbh I've never seen any device on which you can disable the power off key, and it's obvious why...

[Q]long wakeup time from standby

I use Froyo 2.1 build, after I press power key to turn off screen, if I press the power key again in short time, the device wakeup will take a long time (about 5 seconds), sometimes even not wakeup (due to timeout in the lockscreen and screen turns off again I guess), then I have to press the power key again and wait, normally it will take about 4 seconds to turn on the screen.
I tried to turn off setCPU and ATK completely, but not works, still long time to wake up.
is there a solution to this? everything works fine except this
thanks in advance!
I also have this issue. I tried many builds but there is always lag. No build will wake up so fast as WinMo but I think its the limitation of running OS from SD Card. Maybe I`m wrong but I think internal memory has lower latency so windows wakes up immediately and android always takes some time..
I want to know is there anyone do not have this long delay before wakeup? if there is, please tell me, thanks!
these are known issues and there is no fix , most of time things like this come
from human error
Yeah these are known issues with the Froyo builds. Will probablyget fix somewhere down the line.
The best thing to do now is to be patient with it. I find the more frustrated I get with it, the worse it gets. What I mean is if I keep hitting the hangup/unlock button to try to get it to wake, it takes longer to awake.
Also someone has posted that a possible problem is with Advanced Task Killer settings. If you have that program set to kill apps during sleep, it could cause a hang on wake. Also I believe auto screen rotate could have an effect.
I am sure that in time the situation will be resolved, as will every other minor bug and glitch.
The only solution I have foudn to this problem is to use shub 1.4c or d. It usualy turns on the first press, if it doesn't I press the button again(b/c usually the backlight goes on on the first press just nothing shows up on the lcd) then wiat a couple seconds and it goes on. I also have minimal TS freezes w. that build while with other builds they are common
disable autorotate. i had this even in shubcrafts builds, sometimes it woiult be within have a second, sometimes id see the screen power up but and go greyish, then a few seconds later id get the lock screen. from time to time, though i wouldnt get the lock screen and it just power down again.
since disabled auto rotate, its been pretty consistant at showing the lockscreen quickly.
The devs know about these problems, they are bveing worked on.
this is the major problem for me, but I still can not find it in any build's known bug/issue list, does the developer guys really know this? or it's only the problems shown in our devices?
If any of you have installed Battery Indicator, try to uninstall it and see if it help.
I used to have Battery Indicator to disable screen lock, after I uninstalled it, the problem is gone.
I have had the same issue with all the roms i tried ... but recently on shubcraft 1.5, i ve found out that when pressing the end key and that nothing shows on the LCD but the keyboard backlight is on, you can unlock as usual by doing the slide pattern on the black screen (you can feel it vibrate when you hit the spot before sliding).
Sent from my HTC HD2 using XDA App
I'm using FroyoStone 2.1 with kernel r9 and have the same issue.
I can confirm your finding that it's indeed the backlight that doesn't light up and unlock can be done anyway...
Dev's please fix this backlight issue...
BIG THANKS!
I had this annoying issue and tried almost all the builds and finally the build in the following link worked well. Note : This is a nexus ROM without sense and FM radio. Very snappy and no wakeup delay for me.
forum.xda-developers.com/showthread.php?t=773790
Yes, same here. Using mattc 1.1 clean
hate it.
I have this problem either , Shubcraft 1.5 , also during calls , sometimes it take more than 5 seconds to wake the screen after you take it off from your ear .
cecaa1030 said:
I use Froyo 2.1 build, after I press power key to turn off screen, if I press the power key again in short time, the device wakeup will take a long time (about 5 seconds), sometimes even not wakeup (due to timeout in the lockscreen and screen turns off again I guess), then I have to press the power key again and wait, normally it will take about 4 seconds to turn on the screen.
I tried to turn off setCPU and ATK completely, but not works, still long time to wake up.
is there a solution to this? everything works fine except this
thanks in advance!
Click to expand...
Click to collapse
Can you try waking up your phone with the YES/SEND key? (instead of power key)
Please provide feedback if this makes a difference.
memin1857 said:
Can you try waking up your phone with the YES/SEND key? (instead of power key)
Please provide feedback if this makes a difference.
Click to expand...
Click to collapse
Thx a lot.. The Call button wakes up the phone much faster than the default Power button.
Is is possible that a low memory situation can cause this? My HD2 was running perfectly then out of nowhere the long wake and wake screen freeze started to appear. I have been troubleshooting it for 2 days now. I just noticed that my available memory show in Taskiller was 109mb. I had seen that low memory situation before during a freeze period and not paid any attention to it. But I do know that after I reboot the phone its perfect again w/ 200+mb.
Anyone else notice this?
Has any progress been made on this matter in recent builds? Running shubcraft 1.5, and still having major troubles with it about 2 out 3 unlocks..
Try disabling any & all task killers, what I think is happening is that something gets killed when it shouldn't. I had the same issue to the point of going back to Winmo and as a last resort just disabled all those and then went with a static wallpaper (no live). The problem disappeared and now the battery last much longer.

[Q] Screen won't turn off

For some reason my screen won't shut off when I press the power button or by itself after any amount of time. I made sure all of the settings were set right that might keep it on. I know it's not hardware damage because I've pretty much never dropped it or handled it hard. The power button still works because it will get the turn off, restart, etc screen to go. Any idea how to fix it? I already did a factory reset.
JollyGreen527 said:
For some reason my screen won't shut off when I press the power button or by itself after any amount of time. I made sure all of the settings were set right that might keep it on. I know it's not hardware damage because I've pretty much never dropped it or handled it hard. The power button still works because it will get the turn off, restart, etc screen to go. Any idea how to fix it? I already did a factory reset.
Click to expand...
Click to collapse
Dial *#0*# check some test for dimming, sleep etc.
JollyGreen527 said:
For some reason my screen won't shut off when I press the power button or by itself after any amount of time. I made sure all of the settings were set right that might keep it on. I know it's not hardware damage because I've pretty much never dropped it or handled it hard. The power button still works because it will get the turn off, restart, etc screen to go. Any idea how to fix it? I already did a factory reset.
Click to expand...
Click to collapse
Download wakelock detector and see which app is keeping your screen on.
Dialed that number, the dimming worked, but the sleep button didn't do anything. I'll try that app out and see what it says.
In my understanding *#0*# dialing is for hardware check, if sleep is not working from there means it has nothing to do with any app & better to take to service centre.
Sent from my SM-N9005 using XDA Free mobile app
It didn't do it until after I tried to change my boot screen. Know if that would do anything? No boot animations go off besides the galaxy note 3 one (no Tmobile or samsung animation, and no shut off animation). I also rooted it so would they still help me even though the knox counter is 0x1?
Any help? Using the wakelock app it says that system manager application is used a lot more than anything else. Not sure what it does.
JollyGreen527 said:
It didn't do it until after I tried to change my boot screen. Know if that would do anything? No boot animations go off besides the galaxy note 3 one (no Tmobile or samsung animation, and no shut off animation). I also rooted it so would they still help me even though the knox counter is 0x1?
Click to expand...
Click to collapse
Try to flash complete stock ROM & clear Data & Catch before & after flashing from recovery may HELP.
That fixed it. I'm not sure why I didn't already try that since it seems kinda obvious. Don't know what made it do that though. Do you happen to know if modifying the boot animations can mess other things up?
Mine its not rooted still stock and all of the sudden started acting up with the screen ....i did the *# test and when i went to sleep it went straight to the lock screen ...any idea what could cause it
help
JollyGreen527 said:
That fixed it. I'm not sure why I didn't already try that since it seems kinda obvious. Don't know what made it do that though. Do you happen to know if modifying the boot animations can mess other things up?
Click to expand...
Click to collapse
how do you do that cause I'm having same problem s
scooby 777 said:
how do you do that cause I'm having same problem s
Click to expand...
Click to collapse
Mine does this every time I reboot my phone. I have to press and hold the home key, pick the pie chart, pick RAM and pick "Clear Memory". Then it's fine til the next time I reboot.
I had my note 3 with the same problem and solved it recovering the original system/media/bootsamsung*.qmg files.
to solve the problem plug the charger and unplug it immediately and plug it back in again. This is also the reason why the problem is caused. So doing it again will solve the problem.

Categories

Resources