Using JellyBean DS 1.7 -- on the slide, dont know when this exactly stared occurring (as it seemed to be ok after i just installed the rom), i see that there is some sort of cyanogen-mod "phone update" thing, which runs on occasion and think it might have broken something. as i really cant get a gps fix, and at this point dont know how to proceed - is it a hw issue or something in the rom or some sort of update issue?
In maps i see the blue triangle but its always surrounded by a big blue circle, and don't know if its some update but I cant use navigation anymore...
Is there some way to reset the GPS in the device?
Anyone seen this issue or know of a fix?
steve_77 said:
Using JellyBean DS 1.7 -- on the slide, dont know when this exactly stared occurring (as it seemed to be ok after i just installed the rom), i see that there is some sort of cyanogen-mod "phone update" thing, which runs on occasion and think it might have broken something. as i really cant get a gps fix, and at this point dont know how to proceed - is it a hw issue or something in the rom or some sort of update issue?
In maps i see the blue triangle but its always surrounded by a big blue circle, and don't know if its some update but I cant use navigation anymore...
Is there some way to reset the GPS in the device?
Anyone seen this issue or know of a fix?
Click to expand...
Click to collapse
Try GPS Status.
You should see sattelites as green marks on the radar and the bar underneath.
Somehow my gps got broken, and the device can't see any of them. I guess my case is a HW issue as the same thing happens when I tried to roll back to an earlier ROM.
Related
Hi to all!
I have a strange problem with my HTC s710.
I bought it a month ago and it worked fine for a while, then it started to shutdown the display. Then it appears again, and the it turns off... it continues to work, but you can see nothing because the display turns off.
It's impossibile to use it. The HTC customer care sended back my phone after having upgraded the software but the problem is still here.
They wrote: "upgraded software and no problems found" but it's not really true.
I can't use the phone because the display turns off while i'm using it...
i tried to hard reset it several time without results.
Please, help me...
I would take it apart, clean the contacts and make sure it is seated properly. Does it happen when you're not using the device? Say if it's sitting on the table will the display flicker?
Unfortunately this is a very common problem with the S710... Since so many people are experiencing this issue with their phones even after hard resetting & changing roms I strongly believe it's a hardware issue.
It's not s710 only, even the microsoft emulator also have the problem
Look in the registry HKEY_CURRENT_USER\ControlPanel\Power The Dword-key "Display". It sets the seconds for display timout. It overrides every other setting!
It happens while i'm using the phone...
for example, if i'm writing an sms, it suddenly turns off the display... then i have to wait for a while and the it appears again... and this go on for all the time...
same problem to me.... dunno what the source of the problem is
guess gonna have to take it back and ask for refund
i've already send it back to the HTC customer care and they said there is nothing to do because it works fine... (oh my god!)
I think it's an hardware problem...
Display blackout
I got the same problem too, did rom upgrades but no success, it s**ks
Its an intermittent fault.
Should someone identify the problem pls let me know !!
This is almost sure a connection problem of the Flex-cable between upper and lower part of the device. Search related threads here or on MoDaCo.
s710 display issues
Hi Guys,
This is not a LCD or flex issue, neither is it a connection issue.
The actual fault is the display driver on the main board, it seems to be an intermittant fault.
please post your findings on this topic....
bro am also havin the same problem but they say it seems to replace the board which costs 9k... hw can i fix this problem pls help me i bought this stuff for 17 k...
tjsa said:
Hi Guys,
This is not a LCD or flex issue, neither is it a connection issue.
The actual fault is the display driver on the main board, it seems to be an intermittent fault.
please post your findings on this topic....
Click to expand...
Click to collapse
What makes you so sure it is not HW related? The only thing that really changes over time is the HW (as you slide in/out the keyboard, move the device etc.pp) - SW stays as it is and if even ROM reload does not fix it, well I feel rather sure it is HW.
Anyway, hunting intermittent faults is hard to do and you may construct a causality from just coincident events - no fun nailing this down.
any solution for my problem..?
I have had so many power related issues so far. Sometimes it is the battery, sometimes it is the charging connector, sometimes LCD and sometimes even the whole circuit board.
When i had the same problem relating to intermittent off displays, I got it repaired in the warranty and they had to change the main board. I dont think there is any other solution to your problem!
Display failure
The failure of the screen is not the problem on my Vox. My screen always jumps back to the Home screen. Even while writing an SMS or scrolling in the application menu. Is there a possibility that there ever comes a Dutch version for my Vox?
It happens to me also. I tried to open the device, take everything apart then mount everything back. The problem stays. I tried hard rest, ROM flashing, soft reset, changing settings etc etc etc... The problem is still here.
Then, I left the mobile without using it for 6 month or so. I am using it again and the problem doesn't happen so often but still happens. Any news on this matter?
I solved this problem because my device was still under warranty: I had to get back it to HTC four times before to fix it.
They changed me three motherboard and finally it seems to work fine...
hi,behind the sim reader there is a small switch,either open it or close it,remove the sim reader to and push it back to open the switch or open the housing and do it manuelly.
cheyn said:
hi,behind the sim reader there is a small switch,either open it or close it,remove the sim reader to and push it back to open the switch or open the housing and do it manuelly.
Click to expand...
Click to collapse
And what is supposed to happen after that? Also, I guess we have to open again the phone to find this switch because I can't see any switch otherwise. Can you please post a picture of it?
Is your camera locking up (No pre-view picture)?
When I select the camera icon, I see the camera menu in the lower part of the screen and I can even take pictures, however I see a black image instead of the pre-view photo on the screen. This issue goes away by soft resetting the phone; however it usually comes back after few days and the only way to see the pre-view image is by resetting the phone. The strange part is that the camera can actually take pictures but I cannot see the photo before taking it. Have you heard of this issue? The phone works just fine otherwise and I like it a lot.
Thanks,
z_zk_z said:
Is your camera locking up (No pre-view picture)?
When I select the camera icon, I see the camera menu in the lower part of the screen and I can even take pictures, however I see a black image instead of the pre-view photo on the screen. This issue goes away by soft resetting the phone; however it usually comes back after few days and the only way to see the pre-view image is by resetting the phone. The strange part is that the camera can actually take pictures but I cannot see the photo before taking it. Have you heard of this issue? The phone works just fine otherwise and I like it a lot.
Thanks,
Click to expand...
Click to collapse
Are you running stock?
I can't speak for whatever potential issues might be caused by any of the custom roms in circulation, but on a stock phone, obviously it shouldn't be doing that.
I can't imagine what hardware issue would produce intermittent preview-ability that's temporarily remedied by a soft reset, yet still manages to capture the photo itself, but there's a first time for everything.
Sent from my Inspire using XDA Premium
My stock camera application (and Camera360) and camcorder applications both exhibit this behavior. A soft-reset of the device usually temporarily resolves the issue (i.e. allows me to use the camera for a short period of time). However, after my phone has been on for a while any app that uses the camera just locks up (eventually have to force close or soft-reset).
It is rather annoying. The only information I found seems to indicate that there may be an issue with the API within FroYo itself. Hopefully when we get the update to GingerBread the problem will resolve itself.
I also read something else about something to do with an LED widget that caused someone problems but I'm not using any LED widgets, so I'm not sure what that's referring to.
Hopefully there's a fix out there somewhere or we get the 2.3 update soonish.
ryguy25 said:
My stock camera application (and Camera360) and camcorder applications both exhibit this behavior. A soft-reset of the device usually temporarily resolves the issue (i.e. allows me to use the camera for a short period of time). However, after my phone has been on for a while any app that uses the camera just locks up (eventually have to force close or soft-reset).
It is rather annoying. The only information I found seems to indicate that there may be an issue with the API within FroYo itself. Hopefully when we get the update to GingerBread the problem will resolve itself.
I also read something else about something to do with an LED widget that caused someone problems but I'm not using any LED widgets, so I'm not sure what that's referring to.
Hopefully there's a fix out there somewhere or we get the 2.3 update soonish.
Click to expand...
Click to collapse
Hmmm...
This is the first thread I've come across that brings up this problem.
My stock (rooted) phone, my mom's stock phone, and my dad's stock phone have never encountered an issue like this, but then again, maybe we were the three lucky ones...
EDIT:
That's not to say you guys are crazy... maybe we just haven't had the right combo of circumstances to expose the problem/bug on our phones.
Now that I think more about it, I did have an issue when I ran barcode scanner once, about a month ago. That of course uses the camera. As soon as it identified the barcode, and I pressed the 'search web' button, it just froze (image still visible), but the back key/screen input was unresponsive. The only thing that worked was the home button, which, instead of going to the home screen, displayed the screen you see when you are about to end a call with someone on your phone. Thing is, I hadn't made a single call that day. That screen was also unresponsive, but when I pushed the home button again, it finally got to the home screen.
I then went into manage apps in settings and FC'd barcode scanner and the dialer/phone, just in case. I even uninstalled barcode scanner because I thought it might have a phone-specific bug that I didn't want to deal with.
I don't know if there's any correlation between the yours/OP's issue, but it sounds like it's ****ed up in a similar way. FWIW.
Sent from my Inspire using XDA Premium
I think I managed to fix mine by wiping my dalvik cache. On the downside, my current drain used to be around 5 when my phone was in standby and now it is around 45. On the upside, I haven't had a problem with the camera or camcorder since then.
Sent from my Desire HD using XDA App
Mine ended up being a hardware issue. Phone was exchanged with at&t. Haven't had an issue with the camera since.
Just wanted to update for the OP.
Sent from my Inspire using XDA App
Hello everyone,
I've been having quite an interesting issue on my NS4G. I'm currently running the latest available CM7 nightlies/gapps, as well with Pete Alfonso's kernel. The underlying system in the phone (radio/etc) is all running the current latest available from Sprint as well.
Now the issue in question, I've been having an issue that seems to be occurring more and more frequently on my phone. Now because I am already running a custom ROM and not just stock, this makes me unsure if the issue is coming from the software, or if there is an actual hardware issue with my phone.
Occasionally (I would say as infrequently as once every 2 days or so) when I unlock my phone with the power button, for a split second after the CRT animation I see my phones screen as all green (with a hint of purple), almost the color you associate artifacting with. Now I am not overclocked, but I am running this custom kernel. But the thing is, I'm not 100% on this, but If I remember correctly I do remember seeing this issue on other kernels as well before (I've been running Pete's for some time now).
I also occasionally experience issues with lets say finishing up a phone call, and my phone may lock up with that green screen w/ purple, and then CM7 will automatically reboot the phone for me. I've also experienced my phone rebooting into "Safe Mode".
Essentially what I am wondering is if anyone can shed some light, are these just software bugs that I am running into that other users are experiencing as well, or is this an issue with my phone?
Thanks everyone!
boktai1000 said:
Hello everyone,
I've been having quite an interesting issue on my NS4G. I'm currently running the latest available CM7 nightlies/gapps, as well with Pete Alfonso's kernel. The underlying system in the phone (radio/etc) is all running the current latest available from Sprint as well.
Now the issue in question, I've been having an issue that seems to be occurring more and more frequently on my phone. Now because I am already running a custom ROM and not just stock, this makes me unsure if the issue is coming from the software, or if there is an actual hardware issue with my phone.
Occasionally (I would say as infrequently as once every 2 days or so) when I unlock my phone with the power button, for a split second after the CRT animation I see my phones screen as all green (with a hint of purple), almost the color you associate artifacting with. Now I am not overclocked, but I am running this custom kernel. But the thing is, I'm not 100% on this, but If I remember correctly I do remember seeing this issue on other kernels as well before (I've been running Pete's for some time now).
I also occasionally experience issues with lets say finishing up a phone call, and my phone may lock up with that green screen w/ purple, and then CM7 will automatically reboot the phone for me. I've also experienced my phone rebooting into "Safe Mode".
Essentially what I am wondering is if anyone can shed some light, are these just software bugs that I am running into that other users are experiencing as well, or is this an issue with my phone?
Thanks everyone!
Click to expand...
Click to collapse
go to the main settings, cyanogenmod settings, display.. turn on the screen off animation. then go back to cyanogenmod settings, lockscreen, delay and timeout, turn both screen timeout delay and screen turned off delay to immediately. that should fix the green screen.
Hi, it appears that recently the gravity sensor in my Nexus 5 stopped working.
At least it is what it seems by using sensor testing apps. And this makes it impossible for the phone to get its orientation (compass is not working).
Screen rotation is still working fine though.
Here is what happened exactly: not long ago I was using Google Maps, but the phone was a bit sluggish so I decided to reboot it.
After rebooting I opened Google Maps again and immediately noticed that the orientation indicator was missing (the blue "beam"), while it was present before the reboot. But I didn't care about it, and just thought that the compass needed re-calibration.
After a few days the orientation indicator was still missing, and the phone never asked me to re-calibrate, as it used to do before instead.
Then one day I launched Google Sky Map, and noticed that the view does not rotate automatically.
So I fired up a sensor test app I had installed (asd.vector.sensor), and no data is displayed for the Gravity sensor. Also orientation is not displayed and the info says that the gravity sensor is used to compute orientation, too.
Other sensors are ok, and as I already wrote screen rotation still works great.
Any clues about this issue? Did anyone ever experience this?
I'm afraid a system restore would not help...
I'm using Resurrection Remix ROM, Android 6.0.1.
Thanks.
If the problem exists on a stock ROM, it could be a hardware fault.
audit13 said:
If the problem exists on a stock ROM, it could be a hardware fault.
Click to expand...
Click to collapse
Ok yes, but I still do not know if it exists on a stock ROM.
Taking it the other way around... Do you think there is real possibility that it is a software fault?
I mean: did it ever occur to anyone? Is there really any hope that resetting my phone to stock will fix this?
I HATE having to reset my phone...
Thank you.
I stopped using custom roms a while ago because of minor problems that would suddenly appear.
I don't think there is a way to really tell if it is software or hardware unless you reset or use a stock ROM.
audit13 said:
I stopped using custom roms a while ago because of minor problems that would suddenly appear..
Click to expand...
Click to collapse
Well, that's a little hope at least.
I will need to find some time to re-stock my Nexus and try.
Thanks .
Ok, I restored the phone to stock and all sensors work again now!
Thanks audit13 for pushing me in that direction .
That's great that it was a software bug in the custom ROM.
Now you get to hunt for a custom ROM that works with a minimal or zero number of issues
When I wake up the cell phone it gives a bug
I have this problem I don't know why
I thought it was the September update, but I installed the October patch and the same thing happens
I think it's root. Has anyone had this problem? Do you know how to solve?
I've already tried changing the unlock type
Video of what's happening
This problem only does not happen when I leave the option always display active
Edit: I just installed the clean flash from the rom stock and it still has the same problem
resoved:
well i think i figured out what causes this bug on the lock screen. I tested several things, uninstalled LSxposed, root, applications etc. But nothing solved. So I put in gesture navigation as I only use buttons. And that was it, after I put the gesture navigation there was no more problems