Database Users

How to solve phone unresponsiveness after using GPS??

Hello everyone, i've my SG3 flashed with Gsam101 ultraclean SPF rom + modified JPB kernel + lagfix v2!
I've solved the GPS slowness using the post http://forum.xda-developers.com/showpost.php?p=10385614&postcount=43
The main issue is that opening googlemaps already slows down the phone (cause it's kind of heavy application!) then with this software glitch it becomes even more slow... it's a sort of 3310 with froyo on it! :-(
I've kind of few applications installed btw and NO services started at boot, so i would exclude the cause of 3rd party applications causing this...

Did you actually fix the unresponsiveness? Or just the GPS fix time? I've managed to get the GPS fix to work, but the phone becomes very slow, even after the GPS is turned off.

exactly my problem, the gps fix with the method posted before is really fast!!
The phone becomes slow though, as you said :S

Ok I think I've found the problem. The stock GPS I5800XXJPF actually works really well. With a fresh install, my GPS would lock on for the first time within 20 seconds or so, and the phone would work fine. However, after reinstalling all my stuff with Titanium, the GPS went back to being very slow, and the phone would remain slow (laggy) until reboot.
So... I checked my GPS settings and I had 'Use sensor aiding' checked. Unchecked it, reboot and voila! No GPS problems. I still use GPS toolkit to make the first fix, but that is the only thing different from stock. GPS works great now and phone runs at full speed.
Does this make a difference for you guys?

You're my new hero...this "fix" works and gpsfix it's still fast and stable!
Sent from my GT-I5800 using XDA App

disabled "sensor aiding" on Galaxy-3 i5800
Hi,
I was planning to make a new thread on the lagging behaviour of the galaxy-3 i-5800 when i found this thread.
problem I had for long time :
My phone went to 100% cpu after "closing/ending" an application which uses gps, like g-maps,copilot,lattitide etc. It took me many weeks to pinpoint the problem, when it happened. Reason it took so long is that i found by accident, the 'remedy' , which is switching off the display and switch it on again. This interfered with the root-cause analysis , because when the screen went out automatically, the problem dissappeared :-S
"Finally" yesterday i found the root-cause of the lag.
It was "sensor aiding" in location and security setting. After disabling this setting, the lag problem is gone.
In dutch the setting is called "sensorondersteuning", which is located under "locatie en beveiliging".
So I want to spread the word to many galaxy-3 owners (i-5800/5801) to NOT use this feature (even not in the lates JPM firmware).
From yesterday, I'm a happy galaxy-3 owner again
enjoy it.

its JPF not SPF and its kinda stock like, many stock apps are removed, social hub etc. I dont think any are added, besides superuser since i suspect its prerooted

[Q] andriod on htc hd2 struck on black screen after a call

Hi
I have a HTC HD2
and i installed andriod nand rom on it with the following things
HSPL 2.08
Radio 2.15.50.14
MAGLDR 1.12
i installed almost 10 andriod roms and find the same problem
after making or receiving a call screen goes into black screen and hangs up. i have to reboot the device by removing the battery. i would appreciate if any one can provide me the solution to fix this problem as i love andriod roms.
thank you

mohammedmazher said:
Hi
I have a HTC HD2
and i installed andriod nand rom on it with the following things
HSPL 2.08
Radio 2.15.50.14
MAGLDR 1.12
i installed almost 10 andriod roms and find the same problem
after making or receiving a call screen goes into black screen and hangs up. i have to reboot the device by removing the battery. i would appreciate if any one can provide me the solution to fix this problem as i love andriod roms.
thank you
Click to expand...
Click to collapse
I am facing this only when battery is bellow 15%. If this is the case then just charge it before it goes to 15%.
If that's not the case then you can try installl MAGLDR v1.3
Do you have this issue in Froyo or Gingerbread ROMs? or in both? What version of CWM are you using?

I have the same problem on MIUI since after approximately 1.3.18 (cutover from Froyo to Gingerbread). Also have this problem on CME DHD2 Compact.
It is also an issue if someone tries to call me.
Sometimes, if I try waking the phone from sleep (power button) and it hits the black screen, and I wait long enough, it will wake. But again, the only real fix I know is pulling the battery.
I am running MAGLDR 1.13
Also, another fix that works sometimes is plugging in the phone into a power source e.g. laptop USB port

It's something about light sensor, when you put your screen into a strong light it would be turn "unblack" again. I don't know how to fix it, is this a problem with this hardware because it's broken or my version of LEO doesn't support NAND full functionaly.
Begging for answer!
i know about my poor english

I have this problem too.. running latest Hyperdroid rom by pongster (magdlr version) and it's driving me crazy. Sometimes phone wakes up normally after a call like it shoud, sometimes is stuck with black screen for few minutes, hours even (although i can't wait that long so i pull out battery)..
Back on WinMo everything worked normally, so it's not an hardware issue with proximity/light/whatever sensors
Is there any fix out yet? I googled and searched this forum a lot and haven't found nothing much helpful, ony a couple of threads with bunch of people with same problem like me. An option for disableing those sensors would be just as good, i've tried few apps for keeping the screen awake and none of them actually worked..
Any help is appreciated.. thanks in advance.

Bump!
Anyone? :/

I have the same issue - running Gingerbread, MAGLDR 1.13
Very annoying cause everything else works super.
Temporary solution i use is to use headset / handsfree. Then there is no problem.
So experts on XDA, we are begging for a fix for this!

I have the same issue since first Android roms and never found a real solution for the problem.
Instead i found a bypass that works for me reasonably well (99% of the cases the screen turns on after a call).
I installed the following 2 applications that wakes up my screen after the call (install then enable each one):
1. Screebl - https://market.android.com/details?id=com.keyes.screebl.lite
2. Modified version of SpeakerShake - http://forum.xda-developers.com/attachment.php?attachmentid=449922&d=1290758421
I suspect this issue is somehow related to hardware failure in light sensor. Installing these programs solve this problem for me.
Also take a look on the following thread:
http://forum.xda-developers.com/showthread.php?t=835127

I have had the same thing happen to me but only around 2 or 3 times in a about 3 months of usage. Had it on both CM7 and MIUI Gingerbread ROMs regardless of battery percentage.
MAGLDR 1.13

Some users experience this using SetCPU
if you have a profile for screenoff and it's set to the lowest frequency, try to set the frequency to something above 500 MHz.
If you have smartass set as governor, then even setting the frequency to it's highest (without OC) during screenoff wouldn't change anything in battery performance, but the device will wake up faster.

Your setup works for me as well - until we`ll see a fix for it this will do

Quiethinker said:
I have the same issue since first Android roms and never found a real solution for the problem.
Instead i found a bypass that works for me reasonably well (99% of the cases the screen turns on after a call).
I installed the following 2 applications that wakes up my screen after the call (install then enable each one):
1. Screebl - https://market.android.com/details?id=com.keyes.screebl.lite
2. Modified version of SpeakerShake - http://forum.xda-developers.com/attachment.php?attachmentid=449922&d=1290758421
I suspect this issue is somehow related to hardware failure in light sensor. Installing these programs solve this problem for me.
Also take a look on the following thread:
http://forum.xda-developers.com/showthread.php?t=835127
Click to expand...
Click to collapse
Yup, this worked for my setup to - thanks!

hi guys ! i can`t realy figured out how to set it . shall i use only one app or both ? and wich settings should be ?

xanthrax said:
hi guys ! i can`t realy figured out how to set it . shall i use only one app or both ? and wich settings should be ?
Click to expand...
Click to collapse
(install then enable each one):
Click to expand...
Click to collapse
Incearca Sanity app, cauta pe Market, mie aceste doua nu mo ajutat

with me is so but only if I navigation (Navigon) and to have someone call me and then left the screen black and I can not make

try to change the kernel. that works for me

hey guys! i found the solution goin through the market!
download an app called "Sanity" theres a free version in the regular android market.
go to the settings > general > check "Reverse Proximity" (This will give you some warning about not using it if you DONT have a buggy proximity sensor). Check it anyways. Then go back to preferences then click "Proximity" scroll down and uncheck Turn off screen and leave leave the Turn on screen checked. this will force your phone to stay on during calls so that it never has to go through the proximity phase of calls this no more black screens. Hope this was helpful ^_^

Thanks!
I had this problem aswell. MIUI & Cyanogen mod were the ROMs I was using, and this problem started occuring after a few months use (my screen is also damaged from a fall, so maybe the sensors are a little damaged as well).
When I installed the WinMo 6.5 stock ROM again, everything was normal, except that my screen still turns black during calls BUT I can activate it again by pressing the power button.
Now I installed android again and the Screebl app (enabled it) and I have the same functionality! The only problem that remains is that my screen still turns black during calls, so I have to answer with the phone button and putt down phone with the power button. Still beats having to remove the battery though .
If someone has a fix for the black screen, it would be more than welcome!
But, thanks a million for the Screebl app tip! I can use my phone again .

papaganz said:
Thanks!
I had this problem aswell. MIUI & Cyanogen mod were the ROMs I was using, and this problem started occuring after a few months use (my screen is also damaged from a fall, so maybe the sensors are a little damaged as well).
When I installed the WinMo 6.5 stock ROM again, everything was normal, except that my screen still turns black during calls BUT I can activate it again by pressing the power button.
Now I installed android again and the Screebl app (enabled it) and I have the same functionality! The only problem that remains is that my screen still turns black during calls, so I have to answer with the phone button and putt down phone with the power button. Still beats having to remove the battery though .
If someone has a fix for the black screen, it would be more than welcome!
But, thanks a million for the Screebl app tip! I can use my phone again .
Click to expand...
Click to collapse
I also try with WinMobile and the problem was still there ...
I think the sensor is broken ....
I will bring my phone to service ... and when i take it back I will tell you whether it is repaired

Solution
I had the same problem with Android roms on my HD2. I saw in an other thread a member (z-o-r-r-o-, thanks btw) wrote "just clean dust on the screen, where sensor is situated". This looked like a joke to me, but it's not. On a review of the phone I found the place of the proximity sensor. This is on the top of your screen next to the speaker, on the left if you look at the screen. I just took off the protection layer of the screen and cleand the sensor and the problem was solved. So I cut of a bit from the protection layer so that the sensors arn't touched by anything.
I think the problem is that this sensor is much more sensitive with android roms.
Hope this works for you to.

[Q] Proximity/light sensor turns of my screen

Hi!
Ive had a problem with the screen turning of, during calls only, for a couple of months. I think it happend somewhere in July/August.
Now, this question have been asked but there has been no answer that solves this.
There is a solution for Desire HD http://forum.xda-developers.com/showthread.php?t=951858.
I have tried the Proximity screen off http://forum.xda-developers.com/showthread.php?t=624206 for the HD2 but that does not deal with my problem, it did not work for me.
The problem only occurs during calls, the screen shuts of no matter if Iam close to it or not.
The screen does not shut off if I plug in the headset before/in the call and also if there is very very much light before I answer/make a call to the time where I hang up/the other person hangs up.
The screen does not wake up for along time after the call has been ended, unless I put it very very close to a light source ( LED does not work so good, light bulb would do the trick),or the usb charger. If I plug in the headset after the call has ended, the screen is till turned off.
I only have this problem when Iam in android. I have been using AmeriCanAndroid ever since I got the phone in May.
Regarding the Proximity sensor off, I made about 90 different setting combination, Screenoff triggered/not triggered with lockscreen delay immediately/several minutes (CM7 settings) with different values when the screen is covered/uncovered with Advanced task killer on/off.
No matter what I tried the result was either the same or worse.
The interesting thing I found out was the screen (at least for the first seconds) turned off each other time, i.e did not shut off for the first ~10 sec, the next call it shut off immediately.
Is there someone who could create an app/setting for the HD2 so that whatever reaction the phone gives when plugged to charger/headset, regarding the sensor(s), but without actually connecting it, would be a life saver.
This problem is very annoying when Iam in a call and want e.g use the dial/check messages/check the time.
Thank you

Go to your settings, and look for something dealing with your proximity sensor

GSM4ever said:
Go to your settings, and look for something dealing with your proximity sensor
Click to expand...
Click to collapse
Thanks for trying to help me, but I have checked everything on the phone.
Anyways, I think this problem is with the proximity sensor because the light sensor seems to work just fine (automatic brightness/backlight settings is responding to the amount of light)
Thanks!

Default settings on CM7 WITH TYPHOONS roms does not have this problem. Perhaps re-create system since it is same since may. Fresh install and all should be well.
Otherwise check for dirt or finger grease smudging over the proximity sensor.
Used to have this problem too on typhoon. Task29 and starting from scratch solved the problems.

Thanks for your reply!
But I dont know anything about TYPHOON roms, and I dont have a reason to change from americanandroid except for the proximity sensor problem.
Iam writing this in hope somebody can include an app or a setting for the HD2 so one can shut off the proximity sensor, I think that would be the best an easiest solution.

Still suggesting you might wipe everything. When I had issues appearing, I started fresh and it fixed it 99% of the time.
Backup your stuff first if needed, then install the newest American Droid and start from scratch.
You might do a nandroid backup before, then if a fresh install doesn't work, you can restore back right before you backed up.

I have the same problem & I couldn't fix it!
using all the sensor monitors in the Market I can't ge any readings from the light & proximity sensors!
in "Phone tester" the sensors read:
Proximity = Near
Light = 10.0 lx
This for covered & uncovered phone - near or far - dark or light!
I'm using: AmeriCanAndroid 110711(sd)
Radio: 2.15.50.14
I think the file /system/lib/hw/sensors.htcleo.so is the problem.

wh_hsn said:
I think the file /system/lib/hw/sensors.htcleo.so is the problem.
Click to expand...
Click to collapse
The reason why removing that file, fix the problem, is because you basically tell the system that there are no sensors at all.
Now that would be a good enough solution for me, only downside is that the sensor wich tells the phone to go in landscape mode also stop working.
I think if somebody could edit the script to tell the phone to stop using the proximity/lightsensor then the problem would be solved.
I saw a post where archagel got scripts from HyperDroid
Here
I checked the files, but the names did not match with my files, perhaps someone knows more about this?
archagel said:
I had the same problem, so I got libsensors source from HyperDroid, commented out lines that do proximity sensor initialization and got sensors.leo.so that shows to phone that there are no proximity sensor.
There are 3 identical files in the attachment - simply copy them over into /system/lib/hw on the device.
But, actually, repairing sensor would be better solution...
Click to expand...
Click to collapse

Camera crash..

Hey, i use this ROM at the moment (http://forum.xda-developers.com/showthread.php?t=769026) but i also had this problem with an other one (Nexus-HD2..or something like that).
So, the problem is following. When i record something it works pretty fine, but sometimes when i hit the stop button to finish the record the whole app freeze and after few seconds i get the message if i want to close the app because it didnt react anymore or if i want to wait. if i choose to wait nothing happens, if i say "close app" i cant start the cam app anymore. then i need to reboot the phone. and the biggest **** is, that the recorded file is damaged so evertyhing i filmed is lost and this crash happens pretty often.. and i also had this problem with the other android build.. does anybody know the problem or what to do?
regards, Helgon

I've had the same issue several times with the stock camera. Search the last week or so of the Hyperdroid thread - somebody posted the MIUI camera apk, which seems to work better. I haven't used it a lot after installation, though, so no guarantees.

I use the miui cam to get around this. It still happens occasionally, but not as often. ( about 1 time in 10 for default app, 1 in 20/25 for miui,, tho I haven't really been counting)
Its not your rom or phone, op, its common to most roms.

Re: [ROM][NIGHTLY] CyanogenMod 9 for Motorola Milestone 2 (Android 4.0.4)

Re: [ROM][NIGHTLY] CyanogenMod 9 for Motorola Milestone 2 (Android 4.0.4)
This is kinda sad, that I can't reply directly to the ROM thread, but here it is, I just hope someone will tell them, or see it to adress these problems correctly:
There's a couple of problems with this ROM. First of all it loses the data connection after sometime of inactivity. Browser won't load anything, asking to check the connection. Going to settings -> data usage -> mobile data switch -> turning it off and then on solves the problem, but it's kind of annoying to do that five to six times a day.
Secondly - just after flashing this ROM keyboard backlight was working fine. But after installing the gapps it stopped. Just won't work. ((
Third(ly))) - Apollo app crashes at random when trying to listen to podcast/music from sdcard. Also annoying. Disabling data connection seem to solve the issue tho as it stopped crashing yesterday.
Fourth - some sensor shanannigans when you're trying to use chrome (games are fine with it) while charging. Random zoom-ins and stuff.
Fifth - and most terrifying. Sometimes it loops, as if I was repeatedly taping the screen at the center or somewhere near it. Can't even reboot when it happens. Power button to lockscreen seem to solve the issue.
Otherwise this ROM is smooth and good and I like it a lot. Using it for a few months now.
Big thanks.
Sent from my MotoA953 using xda app-developers app

sintu_cf said:
This is kinda sad, that I can't reply directly to the ROM thread, but here it is, I just hope someone will tell them, or see it to adress these problems correctly:
There's a couple of problems with this ROM. First of all it loses the data connection after sometime of inactivity. Browser won't load anything, asking to check the connection. Going to settings -> data usage -> mobile data switch -> turning it off and then on solves the problem, but it's kind of annoying to do that five to six times a day.
Secondly - just after flashing this ROM keyboard backlight was working fine. But after installing the gapps it stopped. Just won't work. ((
Third(ly))) - Apollo app crashes at random when trying to listen to podcast/music from sdcard. Also annoying. Disabling data connection seem to solve the issue tho as it stopped crashing yesterday.
Fourth - some sensor shanannigans when you're trying to use chrome (games are fine with it) while charging. Random zoom-ins and stuff.
Fifth - and most terrifying. Sometimes it loops, as if I was repeatedly taping the screen at the center or somewhere near it. Can't even reboot when it happens. Power button to lockscreen seem to solve the issue.
Otherwise this ROM is smooth and good and I like it a lot. Using it for a few months now.
Big thanks.
Sent from my MotoA953 using xda app-developers app
Click to expand...
Click to collapse
The Data connexion loss is a recuring bug for some, mostly people who have a Carrier that use roaming (ie : use another's carrier's network). No known fix for know, but some people seems to have it working "better" by disabling data roaming/national data roaming in options, but it's not for everyone, since some carriers require that to be toggled for data to work.
For the Backlight on the keyboard, be sure to check if the automatic gestion of automatic backlight is activated, it's required for it to work. There is too a "fix" for the problem in the last 5/6 pages of the main topic from memory, but don't recall it exactly, so you'll have to dig to try it.
No idea about Apollo, but it seems to have quite some quirks, and most people use other players so not sure about it, maybe start by checking the Apollo dev's page and market comments to be sure it's not related to Apollo but to the ROM.
The "random sensor shennanigans" while charging is something that happens to a lot of people, i think it's a multi touch bug from the kernel, but not sure (ie : not really solvable by the dev, unless he finds a way to remake tezet's fix (i think it was tezet) or we all use CH kernel since it seems the bug isn't there in this kernel [ wtb a way to use custom kernels :/]).
Your last problem is a weird bug, probably linked to the ROM, but i must admit it'll be hard to pinpoint, since i don't have it but my brother do, while both phones are the exact same model, and flashed the same, in the same order, with the same sbf/rom versions and so on.
I guess you can try to make a full wipe/factory reset (only backuping data you REALLY need to keep like contacts/sms/call log and so on) and redo your phone config, because as far as i know, the only difference between my phone and my brother's is that i had to did that again after i screwed up a couple times, installing an app that was bricking the phone (took me a few wipes to identify it), it might be the reason why i don't have it and he does, or not.