Database Users

[Q] Is your compass working properly?

I started a thread before, but found out it could be a software problem as a lot of demo units' compasses don't work all the time.
S4 has this problem too.
I have the N900W8 device, if that makes a difference.
Fill the poll out above to answer ^, or just comment down below.

Same problem here
nicholaschum said:
I started a thread before, but found out it could be a software problem as a lot of demo units' compasses don't work all the time.
S4 has this problem too.
I have the N900W8 device, if that makes a difference.
Fill the poll out above to answer ^, or just comment down below.
Click to expand...
Click to collapse
Hi, nicholaschum.
I've the same problem. Mi phone is a N9005 (europe free note 3).
I agree that is a software problem, as if you calibrate the compass sensor (*#0*#) it runs without problem until I restart the phone.
I've also tested several demo units at a samsung store and all of them (galaxy s4, note 3, s4 mini) presented the same problem.
The technical service guy told me that they can change the motherboard of the phone, but I doubt that itgonna fix the problem.
There is a lot of threads, here on XDA, but also in other forums reportinf the same problem on several samsung devices...but unfortunately without solutions.
I'm very pessimistic about this problem, due to that we're more concerned about getting new versions of android instead of get this kind of issues fixed.
Sorry for my english!

Mine's accurate in Smart Tools. DBT N9005 4.4.2 NB7

The calibration does seem to get lost upon a reboot, but you do not have to go into the service menu to recalibrate it.
When you are in google maps, simply rotate your wrist (not your arm). Rotate your wrist around and around about 3-4 times (no need for anything more than this so only takes 5 seconds). And then I find everything works just fine.
You shouldn't have to do that after every reboot, but its not too bad if you realise you don't need to go into the service menu and the right movement to recalibrate it quickly.

HTC working to fix voice calling fault on HTC One M7 and mabye M8

Read more in this link.
HTC plans to issue a fix for an issue preventing some owners of the HTC One M7 handset from placing and receiving calls.
A HTC spokesperson confirmed the problem to TechRadar, with a recent HTC Service Pack downloaded from the Google Play Store the presumed (but unconfirmed) culprit.
The firm says resolving the problem, which could also be affecting One M8 users, is its number one priority and has told customers to expect the roll out in the coming days.
The statement says: “We are aware that some HTC One M7 (and possibly some M8) users have recently been experiencing audio issues making network calls on their devices.
“WiFi calling does not seem to be impacted at this time. We're working around the clock with our technical teams and partners to resolve the issue as a number one priority.
“We will provide further updates as soon as we can. For anyone experiencing this issue with your HTC One (M7 or M8), you may want to try WiFi calling, and we ask that you please contact your local Customer Care: www.htc.com/support."
Speculation suggests the Service Pack may have caused the instability, but HTC isn’t offering up that information at this stage. As the original report points out, if you haven’t downloaded the update yet, it may be wise not to do so.

jkolner said:
Read more in this link.
HTC plans to issue a fix for an issue preventing some owners of the HTC One M7 handset from placing and receiving calls..
Click to expand...
Click to collapse
This might explain the issues I have been experiencing since the 5.01 OTA. Call recording has failed with every SW I have tried. Sound quality during calls has crackling and is very poor.

This makes a lot of sense, in the last couple of days mine has had the same problem as was told by HTC that it was a hardware issue, but if this is the case may just hold back and wait for an update.

I've had mine recently producing no audio at either end when answering a call, a reboot seems to sort it out for a while. Hopefully this is all it is and they can sort it out fairly soon, I'm in the middle of buying my first home and trying to talk to lawyers and stuff gets a bit embarrassing when this happens.

Oh my a God.

Thought was mine only!
Sent from my HTC One using XDA Free mobile app

I noticed that also, when my wife called me, and said about sound distorsions during the call. The solution in my case was returning to branded T-Mo firmware, and not updating HTC Service Pack from Play Store.

Pavlova said:
I noticed that also, when my wife called me, and said about sound distorsions during the call. The solution in my case was returning to branded T-Mo firmware, and not updating HTC Service Pack from Play Store.
Click to expand...
Click to collapse
On M8 Original GPE, HTC service pack was installed with 5.01 OTA update. No choice on whether to install or not - it appeared on the list of updated apps.
Apart from sound issues (which I suspect come from HTC/Google disabling features at the Kernel level), I am now experiencing delayed touch response.

Yes, but as I remeber, it was updated also after initial startup. Last update of the Service Pack (on Sense) in Play Store was from 11th December. Anyway, on T-Mo firmware 3.29.118.9 call quality is much better. Also ringtones and notifications are more clear.

Just got a service pack update.

for me I am running the latest gpe 5.0.1 and my problem is that the upper speaker is not ringing but it plays music just fine
uninstalled all google and htc services and the problem is gone F%[email protected] this
I thought that my phone was damaged spent 2 hours searching

Andrew149 said:
Just got a service pack update.
Click to expand...
Click to collapse
Yeah, Christmas graphics for DotView. Nothing fixed otherwise.
RedBlackPellet said:
for me I am running the latest gpe 5.0.1 and my problem is that the upper speaker is not ringing but it plays music just fine
uninstalled all google and htc services and the problem is gone F%[email protected] this
I thought that my phone was damaged spent 2 hours searching
Click to expand...
Click to collapse
Can you pls give a little more details as to what specifically you uninstalled. Thanks.

Roadrunner100 said:
Yeah, Christmas graphics for DotView. Nothing fixed otherwise.
Can you pls give a little more details as to what specifically you uninstalled. Thanks.
Click to expand...
Click to collapse
well till now I am not sure that it is software or hardware problem but when I uninstalled google play services to factory settings the problm is gone and when I restart the Device the Problem is back again Will try to downgrade to 4.4.4 gpe to insure that the problem is not software related

RedBlackPellet said:
well till now I am not sure that it is software or hardware problem but when I uninstalled google play services to factory settings the problm is gone and when I restart the Device the Problem is back again Will try to downgrade to 4.4.4 gpe to insure that the problem is not software related
Click to expand...
Click to collapse
A quick summary of issues:
Google have confirmed memory leak issues with 5.01. An update is supposedly on the way: http://www.xda-developers.com/android/lollipop-memory-leak-fixed/
I've fixed Touch Delay by going into recovery and clearing cache.
Sound and playback issues are probably to do with Google disabling certain features in Lollipop, one of which results in an inability to record calls - access for third party apps to intercept caller voice has been disabled. I'd speculate that this hatchet-job has led to most of the sound issues some have encountered on Original M8 GPE's.
A partial explanation can be found here: http://forum.xda-developers.com/showpost.php?p=56397342&postcount=1

Roadrunner100 said:
A quick summary of issues:
Google have confirmed memory leak issues with 5.01. An update is supposedly on the way: http://www.xda-developers.com/android/lollipop-memory-leak-fixed/
I've fixed Touch Delay by going into recovery and clearing cache.
Sound and playback issues are probably to do with Google disabling certain features in Lollipop, one of which results in an inability to record calls - access for third party apps to intercept caller voice has been disabled. I'd speculate that this hatchet-job has led to most of the sound issues some have encountered on Original M8 GPE's.
A partial explanation can be found here: http://forum.xda-developers.com/showpost.php?p=56397342&postcount=1
Click to expand...
Click to collapse
does this means that my problem [upper speaker doesn't ring but it plays music just fine also the ear piece is working as it should] is due to software issue but I reverted to 4.4.4 and the problem exists the upper speaker doesn't ring but on sense it rings whenever the proximity sensor is not covered [facedown or in pocket it doesn't ring ]
well try to revert now to 4.4.2 1.54.401 firmware and rom and see if the problem persists
on my friend's one m8 and brother''s one mini 2 that proximity sensor covering issue exits but I am not sure what to do and can't decide whether it is software or hardware or even a problem after all I found sony xperia users complain about upper speaker not ringing due to safety precaution

RedBlackPellet said:
does this means that my problem [upper speaker doesn't ring but it plays music just fine also the ear piece is working as it should] is due to software issue but I reverted to 4.4.4 and the problem exists the upper speaker doesn't ring but on sense it rings whenever the proximity sensor is not covered [facedown or in pocket it doesn't ring ]
well try to revert now to 4.4.2 1.54.401 firmware and rom and see if the problem persists
on my friend's one m8 and brother''s one mini 2 that proximity sensor covering issue exits but I am not sure what to do and can't decide whether it is software or hardware or even a problem after all I found sony xperia users complain about upper speaker not ringing due to safety precaution
Click to expand...
Click to collapse
Like you I'm trying to find out what's going on. I can confirm issues with the proximity sensor. I have further issues like skype not gaining access to camera, voice call issues like loud speaker switching on by itself during a call.. etc. What's clear at the moment is that this GPE release is screwed up big time. Like you I've reset the device a few times, but noting changes. Same problems reappear.
I think that finding out more is difficult since there are no specific Forums or threads dedicated to non converted stock GPE's. So finding out more about issues specific to this version is very hard... I have two other colleagues with Original GPE's (mine is a very early device, their's purchased recently) that have the exact same issues, so I can only assume that this is not HW related, but due to Google disabling certain features and getting it badly wrong or HTC's service Pack at fault. In the office there are three other Sense M8's, which don't have any of these issues, but none of them are on Lollipop yet, so I cannot compare until they get HTC's update.

I have a OEM gpe m8, running mrjaydee82's lollipop gpe ROM. I've seen no weirdness besides memory leak.

Dead sensors? [not any more!]

All of a sudden yesterday, my trusty old Nexus 10 stopped auto-rotating. Apps that have a fixed orientation will work and rotate the screen, but then the screen stays in that orientation until an app with a different fixed orientation is launched. I downloaded a couple sensor checking apps, and it seems the gyroscope/compass/acceleremeter are just dead. It doesn't register anything at all on the apps. I'm guessing it's just the result of age (no "trauma" to the device such as a drop or anything). Any similar experiences, or thoughts on repairing? I doubt I'll replace the tablet anytime soon, it's really just a media consumption device at this point, though a couple of the games I played used the gryo/accel. My initial thought is it's just time to let it go, use it for what I can, then provide a proper burial when it totally dies.

Hurricane Andrew said:
All of a sudden yesterday, my trusty old Nexus 10 stopped auto-rotating. Apps that have a fixed orientation will work and rotate the screen, but then the screen stays in that orientation until an app with a different fixed orientation is launched. I downloaded a couple sensor checking apps, and it seems the gyroscope/compass/acceleremeter are just dead. It doesn't register anything at all on the apps. I'm guessing it's just the result of age (no "trauma" to the device such as a drop or anything). Any similar experiences, or thoughts on repairing? I doubt I'll replace the tablet anytime soon, it's really just a media consumption device at this point, though a couple of the games I played used the gryo/accel. My initial thought is it's just time to let it go, use it for what I can, then provide a proper burial when it totally dies.
Click to expand...
Click to collapse
probably your sensor is dead(could you try to install some app that display all sensors informations? you should find that easily on the play store).
could you also tell us what is your ROM ?

I'm running the current official LMY49F, but rooted.

Hurricane Andrew said:
I'm running the current official LMY49F, but rooted.
Click to expand...
Click to collapse
Hm indeed your issue should not happen( I think) with lollipop.
MM had some issues with sensors but since you are on lollipop ...
Hehe, well then you should flash a rom with a QS tile to rotate hehe.

LOL, probably not going to mess with flashing a new ROM. Like I said, I only use it for media consumption and some light gaming...nothing that "needs" the gyro, so I'll just live with it until it totally dies

Huh, son a gun. Just flashed the Feb Nexus update via fastboot, and low and behold, it lives again! Looks like it was software related after all.

Lost

Hello all. I was a member of this site between the times of the tmobile dash-note 2 eras and i havent done much modding since. I may have to start back after getting this phone. I recently upgraded from the LG g2 and besides the better hardware it seems that the software is a downgrade in terms of over customization and getting the most out of this hardware. I just want to know if there's a way to fix any of these problems or if I should root and if so what should I go with..
1. Get front flash to work while video chatting or to use phone as lighted mirror;without having to record video. ( I always visualized an ad of a chick using the moto x as a mirror or a soldier video chatting his family in a poorly lit space)
2. Pair multiple Bluetooth devices. My LG g2 could pair my pebble time steel and two other devices. One could be paired to play media and the other would be set for calls only and they were remembered.
3. Custom alarm tones. I thought the pure meant that there wouldn't be any restrictions and everything would be customizable like the good windows phones.
I'm sure these problems have been solved but I couldn't find it by searching the forums so maybe someone could point me to the best mod for this phone please?

[Help Needed] Android 9.0 Head Continuously Crashes

[SOLVED]
Hi All,
i have read the other posts about similar problems and although they are probably one and the same problems,
i'm slightly new to terminologies and was hoping for a slightly tailored discussion.
That being said i'm going to jump straight in with the story from the beginning,
Around 2 Months ago i bought this Head unit for my car.
Seicane - 9 Inch OEM Android 9.0 Radio 2004-2011 Ford FOCUS EXI MT 2 3 Mk2/Mk3 Manual air condition GPS Navigation system Bluetooth Touch Screen TPMS DVR OBD II Rear camera AUX 3G WiFi HD 1080P Video
I have recently received this and installed it just yesterday.
Now the problems i'm having is that when ever i use anything internet based via a WiFi dongle or hot spot on my phone then the whole system crashes out on me and i have to turn off the ignition.
Also Google is unable to grab my information, It recognizes me and goes through the 2 step verification but gets stuck after accepting agreement, the Gathering Information shows up on screen and then it just loads indefinitely until either the system or the app crashes.
now i'm not sure if these are one and the same issue but do seem very similar, Like once it has an internet connection it is trying to do a background connection to google to pull data but its getting stuck and crashing out again.
So the only way i'm able to use the system is to put it in airplane mode otherwise it crashes and makes the stereo unusable altogether.
So i have contacted Seicane in regards to this issue and awaiting a reply but figure i may have more luck talking with a community of people that know what they are on about.
So i'm going to say i probably need some kind of system update from google and firmware for the system, but cant log into google without the firmware update.
The problem i'm having is i don't know what stereo it is as such..... if someone could help me with this then i may have more luck
I assume its a MTCD board, but is it a PX6 -5 -4 or 104? i have no idea. i don't know if its even a PX...?
any help on that would be GREAT as i may then be able to download the right updates for it and maybe solve this issue that i'm having.
That being said if anyone can take some time to try and help me i would greatly appreciate it.
I look forward to hearing from you.
MANY many thanks,
Frederus

My initial thought on this is that it is probably caused by a hardware fault in the unit, rather than being a software fault. My reason for saying this is that Seicane are a reasonably popular (ie used by many people) brand, and connecting to the internet is a fundamental function of these head units. If it were a software fault, I would expect to see many more users reporting this issue since the software is in fairly widespread use. Since this seems to be (on the surface at least) only happening to your unit, I suspect it is a hardware fault. It would be interesting to see what the manufacturer has to say when they get back to you. Good Luck!

Update
So i have an update for everyone with some Progress.
So after talking with Seicane they sent me a firmware update it was about six months out of date.
After installing this it seems to have helped with the continues crashing issue i was having.
that being said i then lost a few apps like
Netflix, Spotify and my DAB+ app
They also sent me some APK's for Google services and login services, [This didn't make any difference to my login hanging issue]
So i got back to Seicane and informed them of what had transpired along with a short video of what was happening so that they could see this first hand
They got back to me by the morning and sent me the link for the DAB+ apk so i could reinstall and also forward me another set of apk's
Google Services
Login Services
Google Play Store.
i have given these a go this morning,
DAB+ is back and working
Google Services - No difference
Login Services - No difference
Google Play Store. - No difference
I have just sent them another email saying that this hasn't made any difference and await there reply.
After doing some searching i noticed a lot of people have this issue of google getting stuck on "gathering Info" on there smart phones
which is usually a Cache issue, so i will try this once i'm in my car again.
I would attach the link to the firmware update that they sent me for others who may have the same issue, but i am unable to at this moment in time due to forum limitations for new users.
Ill keep everyone informed as and when i have more information.

Update [Solved]
So its been a week or so,
Quick update after going backwards and forwards with tech support at Seicane it turns out it was a combination of the outdated APK and the fact that google was stuck due to an error with the cache, from what i can tell at least,
So in the end i removed all of the google services from the head unit and deleted the caches as well. then forced it to restart and reinstalled Google login services.
This seems to have worked and i'm not having this issue any longer.
That being said i do have an issue where it doesn't want to turn on very occasionally, but this is on a very rare basis and isn't really a problem usually just have to power down the car and reset ignition. except once where i had to hit the reset button, but 99% of the time it is now working fine.
I hope this helps someone who has the same or similar issue.
Fred.