Hi,
I noticed that my LED notifications just don't work on my G2. While I was using 4.2.2 it was perfect, but after that some days later it just didn't work. I did a hard reset and it works some hours but after that it stopped again to work. I did a newer HR today and it just isn't working too.
So please, if anyone knows how to solve this problem, tell me.
Thank you, and sorry for my english.
TheBalage said:
Hi,
I noticed that my LED notifications just don't work on my G2. While I was using 4.2.2 it was perfect, but after that some days later it just didn't work. I did a hard reset and it works some hours but after that it stopped again to work. I did a newer HR today and it just isn't working too.
So please, if anyone knows how to solve this problem, tell me.
Thank you, and sorry for my english.
Click to expand...
Click to collapse
Try this?
http://forum.xda-developers.com/showthread.php?t=2716012
Related
hi, ive used android on my hd2 pretty much since day one,
ive never been able to get the g-sensor to work in android. i dont get freezes or anything at all it just simply doesnt work, ive tried all sorts i was hoping nand would fix it for me but it doesnt can anyone be kind enough to offer me any solutions?
it works fine in windows mobile so its definatly related to android
ive tried loads of builds and most kernals still nothing, ive tried scripts to disable and re enable and nothing im totally mythed :/
Sorry for bump
Sent from my HTC HD2 using Tapatalk
Are you still using SD?, if so try calibrating with it upside down, screen facing down.
I'm running NAND, when I go to caliberate the bubbles don't move at all, until I press caliberate then the just move left and right and it says complete.
....
Sent from my HTC HD2 using Tapatalk
Hi, I allready posted this problem a while ago. I hoped this was a problem with windows mobile occupying the G-sensor, while running android from SD. I was happy to see that we finally could boot to android and skip WM, but still no G-sensor in android. Is there someone who knows the commands (in Gscript) for starting the G-sensor? I allready tried renaming the akmd file but this is only a solution for someone who has a working G-sensor and wants it disabled temporarily.
Please help a handfull of us G-sensorless android users.
Thanks.
oddly I got it to calibrate with the phone on its side, facing sideways. IT rotated ok afterwards but then got stuck. Best thing to do here is not to calibrate at all as it seems to work fine without any calibration - too late once you have done it though?
pvdw50 said:
Hi, I allready posted this problem a while ago. I hoped this was a problem with windows mobile occupying the G-sensor, while running android from SD. I was happy to see that we finally could boot to android and skip WM, but still no G-sensor in android. Is there someone who knows the commands (in Gscript) for starting the G-sensor? I allready tried renaming the akmd file but this is only a solution for someone who has a working G-sensor and wants it disabled temporarily.
Please help a handfull of us G-sensorless android users.
Thanks.
Click to expand...
Click to collapse
I can't find the script but all it does is renames the akmd file to stop and start. Your the only person I've found with the same problem we need to figure this out man
Sent from my HTC HD2 using Tapatalk
There's 2 more topics on this for a while now, but there's no luck on a solution. The biggest problem we all have is likely the fact that anyone reading a G-sensor thread is having the same problems. The one with the solution isnt looking for our threads.
solution - working for me
it works properly without any calibration, but if you already did it, here is the solution:
calibrate it with upside down - screen facing down, it will resolve your problem
Spartn said:
it works properly without any calibration, but if you already did it, here is the solution:
calibrate it with upside down - screen facing down, it will resolve your problem
Click to expand...
Click to collapse
Did it already, it seems there maintains a hardware differences in every HD2, some of can work properly, some of like us can not. Hope that the dev. who also has this problems can work this out.
i got this problem too!!!
and i already try many different way try to fix it out
but it still does not working!!!!
i guess the problem is the device of our gsensor hareware different form the others!
sorry for my poor english
if someone can read it,i want to say!!!!!
help me~~~~~~~~~~~~~~
有中国人是同样的问题吗?我是Tmo版的~~~有的加我QQ385334026讨论
朋友,你也是重力出了问题吗?
Just keep subscribed to this post and we'll find something eventually
i hope so~~~~~~~~~
hen_43 said:
i got this problem too!!!
and i already try many different way try to fix it out
but it still does not working!!!!
i guess the problem is the device of our gsensor hareware different form the others!
sorry for my poor english
if someone can read it,i want to say!!!!!
help me~~~~~~~~~~~~~~
Click to expand...
Click to collapse
It looks like so, but it works in WM, so it may be HARDWARE DIFFERENCE let the drivers cause issues? I must talk about, I have never calibrated g-sensor after flashing NAND ROM.
hen_43 said:
有中国人是同样的问题吗?我是Tmo版的~~~有的加我QQ385334026讨论
Click to expand...
Click to collapse
hen_43 said:
朋友,你也是重力出了问题吗?
Click to expand...
Click to collapse
Please use English on this forum, thank you.
whynot66 said:
Just keep subscribed to this post and we'll find something eventually
Click to expand...
Click to collapse
Hope that we can eventually find something useful.
ye~~i try but my english is poor
BTW,,i hope we'll find something eventuallye,too
seem like no one can solve this problemT_T
honestly this solution didn't help me - first time, i calibrate my HD2 facing down about 3 times, and finally 3rd shot was done successfully
So your g works?
Me and others in this thread have no g at all baby caliberate as the g sensor doesn't work at all :-/ please can some one help
Hey,
I have a major problem for a couple of weeks now. My phone just keeps waking up randomly and turns the screen on by itself. I have root and s-off and tried out a few roms. Sense Roms as well as MIUI roms... It does not make a difference at all, so I guess it can't be rom related. I have read a few more posts on the web of users having a similar problem but there was no solution given anywhere.
Also, my speaker automatically turns on when I receive or make a call. These two problems seem interconnected since there is at least one person on xda having exactly the same two issues...
Does anybody have an idea or a solution for this? I would be thankful for any kind of help! Thank you in advance!!!
I've a similar problem a bunch of months ago, my phone turn on automatically, without no logic. I've resolved the problem pulling out the battery for a night, after that the problem disappeared.
I hope that will help you to resolve your problem,
Rodomar705
Thanks, I will try that out tonight and report!
Ok, I tried it out last night, but it did not work
Does anybody have a different idea?
Dabarr said:
Ok, I tried it out last night, but it did not work
Does anybody have a different idea?
Click to expand...
Click to collapse
Did you check the date and time once you'd insert battery inside DHD? I think to solve the problem that way, you should leave DHD without battery until the internal battery will be totally discharged. It takes approx. 12-14 hours, and you can be sure only if turning on DHD you'll find time and date set to 12:00am, 1st jan 1980 (or something like that).
Yeah, it definately worked though, time was resetted as well. I turned it in today, hope to be able to pick it up next week. Before, I ran the Ruu to set it back to shipping condition... It still had the same error, so it is definately not rom related...
It is a huge drag without it... Already feeling uncomfortable ^^
Dabarr said:
Hey,
I have a major problem for a couple of weeks now. My phone just keeps waking up randomly and turns the screen on by itself. I have root and s-off and tried out a few roms. Sense Roms as well as MIUI roms... It does not make a difference at all, so I guess it can't be rom related. I have read a few more posts on the web of users having a similar problem but there was no solution given anywhere.
Also, my speaker automatically turns on when I receive or make a call. These two problems seem interconnected since there is at least one person on xda having exactly the same two issues...
Does anybody have an idea or a solution for this? I would be thankful for any kind of help! Thank you in advance!!!
Click to expand...
Click to collapse
same here, i have the MIUI ROM, will try with another version.
Dabarr said:
Yeah, it definately worked though, time was resetted as well. I turned it in today, hope to be able to pick it up next week. Before, I ran the Ruu to set it back to shipping condition... It still had the same error, so it is definately not rom related...
It is a huge drag without it... Already feeling uncomfortable ^^
Click to expand...
Click to collapse
Sorry mate!! Just wait for a week, ist not so long time, and you'll get back your phone as new as when you bought first time!! Hope this makes you feel a little bit of joy!!
Ok, I have gotten my phone back on thursday (after one week)...
SO far so good, everything worked again, they even set the proximity sensor right again... Then I rerooted it and put another MIUI on it...
On friday then, I put Vipermod back in and undervolted it by 50 mA... BOOM, the issue came back, I couldn't remove it, so I took the battery out and waited for 12 hours, as you suggested... and it worked... Issue was gone... Then I ran vipermod again and BOOM the issue was there again... It didn't even help to set the mA values back to normal, I had to reset it again by taking out the battery for 12 hours.
So my conclusion is that this issue is directly related to the actual USE (not just the installation) of vipermod... Can anyone confirm? Don't want to put out false information in the vipermod thread without having others to confirm...
need help also
Stinger696 said:
need help also
Click to expand...
Click to collapse
have you tried pulling out the battery already?
xlxl said:
same here, i have the MIUI ROM, will try with another version.
Click to expand...
Click to collapse
As I have stated before: Rom change haven't helped me.. Did it work for you ???
Dabarr said:
As I have stated before: Rom change haven't helped me.. Did it work for you ???
Click to expand...
Click to collapse
If changing the ROM didn't help then it is an app issue. One of your apps is causing it. Time to look deeper
I have exactly the same issue! Also with the speaker sometimes. Really annoying. If an app is causing it, how can we find out which one? I'm using ARHD 6.1.0, but I've had the issue with older versions of the ROM too (with the same apps installed).
freakshock said:
I have exactly the same issue! Also with the speaker sometimes. Really annoying. If an app is causing it, how can we find out which one? I'm using ARHD 6.1.0, but I've had the issue with older versions of the ROM too (with the same apps installed).
Click to expand...
Click to collapse
Only way to find out is to test them one by one by reinstalling them one at a time
Hi all,
After using version r167 for a while without any problem, yesterday the time started changing when the screen is in standby.
I've done a clean installation of r167 and r 169 but the problem still excists.
Does anyone have a solution for this problem?
Thanks and keep up the good work!
Mherry said:
Hi all,
After using version r167 for a while without any problem, yesterday the time started changing when the screen is in standby.
I've done a clean installation of r167 and r 169 but the problem still excists.
Does anyone have a solution for this problem?
Thanks and keep up the good work!
Click to expand...
Click to collapse
I think you are doing something wrong...I use the same version as u and i don't have this problem
try:
format card and reinstall r169
I did a clean installation of r169 and the problem still existed, however in another thread I found read something about the problem of the device freezing.
Calibrating the G sensor should solve that problem, so I calibrated the G sensor and believe it or not but the time problem is history. No more problems anymore!!
Mherry said:
Calibrating the G sensor should solve that problem, so I calibrated the G sensor and believe it or not but the time problem is history. No more problems anymore!!
Click to expand...
Click to collapse
How could it be possible? Is there any real explanation?
rigo007 said:
How could it be possible? Is there any real explanation?
Click to expand...
Click to collapse
Calibrating the G Sensor solved the freeze problem, and somehow it also solved the time problem. Maybe I'm just lucky because I can't explain it either
Hi
I have a Galaxy Tab 2 which I had originally put omni-4.4.2-20140509 on.
After the installation (as soon as the device is turned on) it kept telling me the Bluetooth Share had stopped.
This error keeps coming up for a 1 minute or so no matter how much I click OK.
If after the error has gone I try to turn bluetooth on, the error comes back up again.
The error was getting so annoying that I disabled bluetooth share in the app manager.
I installed omni 4.4.4-20140708 hoping this would fix the issue but it hasn't and now I'm at a loss as to how to fix this after spending hours searching the web.
Please can someone help with this.
Many Thanks
Still an issue
This issue is still causing a problem even with the latest nightly release.
Please can some one help with this
Thanks
ashsense said:
This issue is still causing a problem even with the latest nightly release.
Please can some one help with this
Thanks
Click to expand...
Click to collapse
As of this date I haven't seen a solution.
ranges said:
As of this date I haven't seen a solution.
Click to expand...
Click to collapse
I had another issue crop up which meant I had to factory reset and reinstall the rom .
Bizarrely after doing this the issue didn't return even though I did this when the issue first appeared.
Glad I now have my Bluetooth back
Hi everybody, I have a Moto X Pure (XT1575) with Stock ROM 6.0, and I'm having this weird issue. Every time I play some video on fullscreen, no matter what app, display turns off after a few seconds... And what's weirder, audio never stops playing and if I move the phone a little bit, screen turns on again... It's like the compass or gyro sensor has something to do with it... I was thinking about Moto app being responsible for this, so I turned on and off every option related to the Screen over there, in every possible combination...
Any other person with this rare issue??
Greetings!
did you solve your problem? I have the same issue as you. would you like to share your experience please?
I get this issue every once in a while. I just solve it by restarting the device. I am not sure what triggers it. I watch a lot of video on my phone every day and this only happens maybe once or twice a month. A google search will show that its been a known issue for a long time now.
tantrum829 said:
I get this issue every once in a while. I just solve it by restarting the device. I am not sure what triggers it. I watch a lot of video on my phone every day and this only happens maybe once or twice a month. A google search will show that its been a known issue for a long time now.
Click to expand...
Click to collapse
thank you. my phone turn off the screen many times some time, but also sometime it not happen at all. don't understand it.
arsene28 said:
thank you. my phone turn off the screen many times some time, but also sometime it not happen at all. don't understand it.
Click to expand...
Click to collapse
No problem. In other forums people have suggested turning off Moto display and/or adaptive brightness but that has not worked for me. It still keeps happening occasionally. I Hope it's something that will be fixed in Android 7.
hope so, but it still need waiting for several months , and since my phone is Asian version, I guess I have to wait for much longer times... if your problem is solved after updating to 7.0, would you please to let me know? thank you!
arsene28 said:
hope so, but it still need waiting for several months , and since my phone is Asian version, I guess I have to wait for much longer times... if your problem is solved after updating to 7.0, would you please to let me know? thank you!
Click to expand...
Click to collapse
Will do.