[Q] No sensors - Stock 5.1 - Nexus 6 Q&A, Help & Troubleshooting

Hi all
So I flashed LMY47I onto my Google play Nexus 6, and now all the sensors (brightness, prox, gyro) are disabled. These were working fine before the flash and flash went well.
A few apps from Google play agree that my phone do not have any sensors. This makes me think its not some hardware issues since these are independent sensors.
I have tried clean flash, full wipe, but no changes.
Any ideas? Search in the forum only returns some Samsung stuff.
Thanks in advance
2015/04/25 Update:
Reflashed a few different unofficial roms, as well as official 5.1.0 one last time with full wipe and factory reset. Nothing worked.
Since I feel like I've already spent enough time on this, I just gave up and called google. Quick 5 minutes phone call and a replacement is on its way! At least the service is good :good:

shinysword said:
Hi all
Thought I posted, but don't think it went through, will delete this thread if the original eventually shows up!
So I flashed LMY47I onto my Google play Nexus 6, and now all the sensors (brightness, prox, gyro) are disabled. These were working fine before the flash and flash went well.
A few apps from Google play agree that my phone do not have any sensors. This makes me think its not some hardware issues since these are independent sensors.
I have tried clean flash, full wipe, but no changes.
Any ideas? Search in the forum only returns some Samsung stuff.
Thanks in advance
Click to expand...
Click to collapse
I had the same issue originally with my pre-order unit, I ended up having to RMA it. No matter what I did, I could never get the sensors to start working again. I ended up taking a friends phone, grabbing his entire partition layout and stock dump and it still did not work.

I posted on here with what I think is the same issue. I noticed it with the accelerometer first because screen rotation stopped working, then I realized the compass wasn't working either. I hadn't noticed the light and proximity sensors, but after reading your post I checked and it seems those are broken too. I see the same thing that you are; apps seem to think my phone has no sensors at all. I checked the system logs and it seems that it throws some kind of access denied error when trying to use the sensor API. I haven't been able to fix it in 5.1, however, when I first noticed the issue I flashed the 5.0.1 image and they seemed to be working again (screen rotation worked at least) so I'm pretty sure the hardware is okay. I have just been using my phone with broken sensors, but it's really annoying.

Nopcodex90 said:
I had the same issue originally with my pre-order unit, I ended up having to RMA it. No matter what I did, I could never get the sensors to start working again. I ended up taking a friends phone, grabbing his entire partition layout and stock dump and it still did not work.
Click to expand...
Click to collapse
Hm, can you share your RMA process with Google? Did you get in touch with them through call or email?

Herohtar said:
I haven't been able to fix it in 5.1, however, when I first noticed the issue I flashed the 5.0.1 image and they seemed to be working again
Click to expand...
Click to collapse
Wow, let me try flashing back 5.0.1 and see what happens. Thanks for the info!

shinysword said:
Wow, let me try flashing back 5.0.1 and see what happens. Thanks for the info!
Click to expand...
Click to collapse
Any luck? If yes, perhaps you could try a custom 5.1 or 5.1.1 rom and see if the sensors work.
You could play it safe by flashing one of the stock-based custom roms in the development forum.
Sent from my Nexus 6 using Tapatalk

micmars said:
Any luck? If yes, perhaps you could try a custom 5.1 or 5.1.1 rom and see if the sensors work.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Have to wait until weekend. Only a business trip and don't have access to my personal computer.
That being said. Definitely a problem if stock image doesn't work... Hm... still considering RMA.
Will report back either way though!

shinysword said:
Wow, let me try flashing back 5.0.1 and see what happens. Thanks for the info!
Click to expand...
Click to collapse
shinysword said:
Will report back either way though!
Click to expand...
Click to collapse
You're welcome. It'll be interesting to see if 5.0.1 works for someone else. Up until now it looked like I was the only one who had this issue.

shinysword said:
Hm, can you share your RMA process with Google? Did you get in touch with them through call or email?
Click to expand...
Click to collapse
My RMA process was handled through ATT since it was a pre-order item from them originally. I ended up trying CM12, stock and reflashing the PIT, nothing seemed to correct it so I just wanted to get a new unit as fast as possible.

micmars said:
Any luck? If yes, perhaps you could try a custom 5.1 or 5.1.1 rom and see if the sensors work.
Click to expand...
Click to collapse
Didn't work unfortunately.
I've updated the op. Basically I just called up Google and asked for replacement.

Sorry to bump and resurrect a dead thread -- my accelerometer stopped working after I accidentally dropped it on my hard wood floor.
I was able to get it working again by dropping it from 2.5 feet onto my carpet. I know it sounds crazy and dumb -- but that was my last resort before calling Google for a replacement.
All is working perfectly now.
It happened when I dropped my phone in my Carved case. I have dropped it accidentally with a spigen case (2 layers) never had a problem. Not blaming the case but pointing out the correlation.

Related

Odd Touchscreen issues

Hey,
I have Verizon droid 3 running up in Canada, and its been working fine...however it recently started having issues with the touchscreen.
Basically the screen works normally 3% now, otherwise it only works when the keyboard is open to just above the first row of keys.
If I touch the screen while the keyboard is fully open it wont respond, but when I go back to the working position it will respond to a touch made while fully open (ie; I pressed ok after typing, it didn't submit until I closed the keyboard to the working position, like a delayed response).
It seems like a software issue, but I already hard reset.....
Any ideas? I don't want to change this phone after only 5 months (no Verizon warranty here!)..
Thanks,
--CP
Sent from my XT883 using xda app-developers app
CrazyPhil said:
Hey,
I have Verizon droid 3 running up in Canada, and its been working fine...however it recently started having issues with the touchscreen.
Basically the screen works normally 3% now, otherwise it only works when the keyboard is open to just above the first row of keys.
If I touch the screen while the keyboard is fully open it wont respond, but when I go back to the working position it will respond to a touch made while fully open (ie; I pressed ok after typing, it didn't submit until I closed the keyboard to the working position, like a delayed response).
It seems like a software issue, but I already hard reset.....
Any ideas? I don't want to change this phone after only 5 months (no Verizon warranty here!)..
Thanks,
--CP
Sent from my XT883 using xda app-developers app
Click to expand...
Click to collapse
Which ROM are you on, stock or a custom one?
Its a long shot, but I have odd touchscreen issues when plugged into cheap power sources (inverters, etc). You may want to check the battery - pop it out for a bit, put it back in, maybe try someone else's, etc...
Sent from my DROID3 using xda app-developers app
Phibernaut said:
Its a long shot, but I have odd touchscreen issues when plugged into cheap power sources (inverters, etc). You may want to check the battery - pop it out for a bit, put it back in, maybe try someone else's, etc...
Sent from my DROID3 using xda app-developers app
Click to expand...
Click to collapse
Haha ya I have odd touchscreen issues when I get to 100% battery and am still plugged in :cyclops:
adamskub said:
Which ROM are you on, stock or a custom one?
Click to expand...
Click to collapse
I believe it's stock-ish, I don't remember what I flashed 5 months ago, think I just changed the radio.img:
57.1.60.XT883.ChinaTelecom.en.CN
XT883
2.3.4
n_16.18.16s
2.6.35.7-g790a33c / [email protected] #1
SLNCT-57.1.60
Thanks,
--CP
CrazyPhil said:
I believe it's stock-ish, I don't remember what I flashed 5 months ago, think I just changed the radio.img:
57.1.60.XT883.ChinaTelecom.en.CN
XT883
2.3.4
n_16.18.16s
2.6.35.7-g790a33c / [email protected] #1
SLNCT-57.1.60
Thanks,
--CP
Click to expand...
Click to collapse
Oh ok, then I'm not really sure. I would, if you want, try and flash right back to complete stock and see if your having the same troubles. If you are then it's almost guaranteed to be a hardware problem. However, if the problem doesn't persist then it could have just been some weird bug or glitch that happened. I've had some weird things happen a week or so after a flash and it was software related.
But all this would be having you do a reflash either through CWM/Safestrap or sbf and then you lose everything you have (Though you can backup & restore apps via Titanium Backup). So if you don't end up reflashing I understand
Also does this happen only at certain times/intervals say when your charging? Hope this helps!
Edit: I looked at the orig post at work and forgot to look at it again. A hard reset should be able to fix it, but you never know. I would recommend a reflash and see what happens. Sorry I can't be more help
I hate you. I read your post yesterday and thought "huh, that's really weird and unfortunate." I woke up today and the same thing is happening to me. I haven't flashed anything since April. It was totally out of the blue.
Mine only works when the screen is slid open bout half a centimeter, not even enough to force the screen to rotate.
Sent from my DROID3 using xda premium
That's exactly what's happening....It's been like this for a week. However, it sometimes works when I left it for the night to charge...or randomly, but full functionality lasts only a few minutes.
has there been any update on this status? im trying to fix a friends with the same problem.
Chaunton said:
has there been any update on this status? im trying to fix a friends with the same problem.
Click to expand...
Click to collapse
I think that is bad luck and your digitizer is stopped working.
ugynok said:
I think that is bad luck and your digitizer is stopped working.
Click to expand...
Click to collapse
I'm in the same train
It's strange.
Yesterday my touchscreen it was completely unresponsive the whole day.
stock rom, everything untouched
i rebooted it a million times. closed or open make no difference.
today, it is working amazingly
what was the difference? nothing at all! it layed on my desk all night
i don't understand how the digitizer can go between perfect condition and not working as it wish.

Flashlight always on problem

Ok, so, I've had this for a while now... I've searched for solutions, found people with the same problem, but no definite answers, so I thought one of you guys can help me.
My flash (camera) light is always on. By always, I mean ...when the phone itself is on, i.e. the light doesn't go off until i turn the phone off... ALWAYS. The light is not at it's full strenght, it's somewhat hard to notice during the day for ex., but I just don't know how to turn it off.
I thought maybe that some app might be using it, but after checking into it, I don't think that's the case here...
So, any solutions or at least ideas on how to aproach this? Thanx...
Dzombache said:
Ok, so, I've had this for a while now... I've searched for solutions, found people with the same problem, but no definite answers, so I thought one of you guys can help me.
My flash (camera) light is always on. By always, I mean when the phone itself is on, i.e. the light doesn't go off until i turn the phone off. The light is not at it's full strenght, it's somewhat hard to notice during the day for ex., but I just don't know how to turn it off.
I thought maybe that some app might be using it, but after checking into it, I don't think that's the case here...
So, any solutions or at least ideas on how to aproach this? Thanx...
Click to expand...
Click to collapse
there is a system widget, called asissitive light. put it in the on position, then turn it off. i had the same issue, that solved it.
Kobro said:
there is a system widget, called asissitive light. put it in the on position, then turn it off. i had the same issue, that solved it.
Click to expand...
Click to collapse
Forgot to mention that I am on CM10. I don't have that widget.
Dzombache said:
Forgot to mention that I am on CM10. I don't have that widget.
Click to expand...
Click to collapse
then maybe try downloading other flashlight apps from play and doing the same thing?
I have torch app that comes with CM 10, and I've tried the thing, nothing...
I doubt that it will be different with other apps, but I'll try them too. Thanx.
Ok, just noticed one majpr thing - the flash is on even when the phone is turned off!!! Not sure what that means...
Btw, tried with 5 different app store apps, no change.
Same problem with stock ROM?
Haven't tried that yet... It's a major pain in the ass. And even if it resolves it, I'm not going back to stock, for sure.
But, if it is gone on stock, and then doesn't come back on new CM flash, then it could be worth it. (even if it's double pain in the ass)
But, I doubt that will be the case. I am thinking more and more that the problem is hardware orientated.
As for the time before I migrated to CM, I don't remember.
Anyway, thanx, I'll think about doing it if I have the time.
Dzombache said:
Haven't tried that yet... It's a major pain in the ass. And even if it resolves it, I'm not going back to stock, for sure.
But, if it is gone on stock, and then doesn't come back on new CM flash, then it could be worth it. (even if it's double pain in the ass)
But, I doubt that will be the case. I am thinking more and more that the problem is hardware orientated.
As for the time before I migrated to CM, I don't remember.
Anyway, thanx, I'll think about doing it if I have the time.
Click to expand...
Click to collapse
It's not that hard to try it, just to know if it's software or hardware related.
Make a full backup in recovery, then flash stock with Odin.
See if problem is solved.
If not, it's probably HW related.
Now you can just flash recovery and restore your backup if you don't have plans to bring it in for service.
If it's fixed, then it's probably best to make a clean cm install anyway.
Hope you'll find a solution.
tys0n said:
It's not that hard to try it, just to know if it's software or hardware related.
Make a full backup in recovery, then flash stock with Odin.
See if problem is solved.
If not, it's probably HW related.
Now you can just flash recovery and restore your backup if you don't have plans to bring it in for service.
If it's fixed, then it's probably best to make a clean cm install anyway.
Hope you'll find a solution.
Click to expand...
Click to collapse
Finaly found the time to do it. Flashed stock, tried the widget, nothing.
I'm super sad right now.
But, hey, tnx anyway guys, once again.
Dzombache said:
Finaly found the time to do it. Flashed stock, tried the widget, nothing.
I'm super sad right now.
But, hey, tnx anyway guys, once again.
Click to expand...
Click to collapse
Hi... I have the same problem with a new Samnsung galaxy mini III. Brand new. Any solution?
Thanks!
aaguillon said:
Hi... I have the same problem with a new Samnsung galaxy mini III. Brand new. Any solution?
Thanks!
Click to expand...
Click to collapse
I suppose my problem was hardware related (phone went through A LOT), but for you... Sorry, don't know.
You should definitly object to the seller, if you are in position. It's not a small problem.
Послато са HM NOTE 1LTE уз помоћ Тапатока

Can't answer incoming calls!

When someone calls me I can't answer an incoming call. If I'm lookin at stuff on my phone it just rings and freezes what ever its on. If I try to touch the screen it doesn't respond to any touch. Really frustrated as this is my first motorola smartphone. Isn't the call screen supposed to pop up? I have rooted my phone and I'm using xposed, but I've tried to disable every module on it and still same problem! And there is others with the same problem as mine (probably without root) out there :/
Please any help would be very appreciated! Thanks
There is a gravity box setting called 'non-intrusive calls' or something like that, might be part of the problem.
My guess is its exposed. Uninstall all modules, uninstall the framework, flash the disabler zip in recovery and try it again.
laurorual said:
When someone calls me I can't answer an incoming call. If I'm lookin at stuff on my phone it just rings and freezes what ever its on. If I try to touch the screen it doesn't respond to any touch. Really frustrated as this is my first motorola smartphone. Isn't the call screen supposed to pop up? I have rooted my phone and I'm using xposed, but I've tried to disable every module on it and still same problem! And there is others with the same problem as mine (probably without root) out there :/
Please any help would be very appreciated! Thanks
Click to expand...
Click to collapse
I helped another user with an issue that matches what you have described exactly. After much troubleshooting, the only thing that fixed it was to flash the entire stock SBF as per the "Return to Stock" thread.
Keep in mind this erases EVERYTHING, including anything you have downloaded to the internal memory. So save anything important to your PC first, and put it back afterwards.
You can try other methods, but I fear they won't work - based on [much] experience.
Good Luck!
samwathegreat said:
I helped another user with an issue that matches what you have described exactly. After much troubleshooting, the only thing that fixed it was to flash the entire stock SBF as per the "Return to Stock" thread.
Keep in mind this erases EVERYTHING, including anything you have downloaded to the internal memory. So save anything important to your PC first, and put it back afterwards.
You can try other methods, but I fear they won't work - based on [much] experience.
Good Luck!
Click to expand...
Click to collapse
I feared this. I just can't imagine why this happened out of nothing. But thanks for the advice, I'll try to do this
Aha! At least you got some responses! I posted here http://forum.xda-developers.com/showthread.php?t=2826011 with the same issue and got none but yes I'm experiencing the same issue. Very dumb the phone just doesn't let you answer and takes the nav bar away
Sent from my XT1060
rocketsaucev2 said:
Aha! At least you got some responses! I posted here http://forum.xda-developers.com/showthread.php?t=2826011 with the same issue and got none but yes I'm experiencing the same issue. Very dumb the phone just doesn't let you answer and takes the nav bar away
Sent from my XT1060
Click to expand...
Click to collapse
Sorry @rocketsaucev2 . I must have missed your thread, otherwise I would have suggested this. I try to help, whenever possible. At least now you have some suggestions to go on.... Good Luck.
samwathegreat said:
Sorry @rocketsaucev2 . I must have missed your thread, otherwise I would have suggested this. I try to help, whenever possible. At least now you have some suggestions to go on.... Good Luck.
Click to expand...
Click to collapse
No sweat I didn't mean anything by it. Fwiw I did an fdr and re-fastbooted 4.4.4 (vzw) and everything is working now [emoji4]
Sent from my XT1060

6.0.1 Changes for LG G Watch R

So my watch updated last night, and now I am trying to figure out all the changes.
I see that we have new gestures. I don't really use them, so Meh.
I also see that my battery projection jumped from 50 hours to 3 days, so that I freaking awesome if it pans out.
Anyone see anything else?
-Chris
cdaly1970 said:
So my watch updated last night, and now I am trying to figure out all the changes.
I see that we have new gestures. I don't really use them, so Meh.
I also see that my battery projection jumped from 50 hours to 3 days, so that I freaking awesome if it pans out.
Anyone see anything else?
-Chris
Click to expand...
Click to collapse
No more reboot watch.. Have to turn it off and on again.
matejilic said:
No more reboot watch.. Have to turn it off and on again.
Click to expand...
Click to collapse
Yeah I noticed that. Find this odd as to why they removed that
Hawke84 said:
Yeah I noticed that. Find this odd as to why they removed that
Click to expand...
Click to collapse
I think Google's reason was: "Why? Because F**k you, thats why!" It also baffles me that they still haven't incorporated custom canned responses to declined phone calls; you are stuck with the default ones even though you set up custom ones on the phone - the reason was probaby the same as the reboot omisson.
matejilic said:
I think Google's reason was: "Why? Because F**k you, thats why!" It also baffles me that they still haven't incorporated custom canned responses to declined phone calls; you are stuck with the default ones even though you set up custom ones on the phone - the reason was probaby the same as the reboot omisson.
Click to expand...
Click to collapse
but how to make a factory reset now? there is no item in menu.
Hawke84 said:
Yeah I noticed that. Find this odd as to why they removed that
Click to expand...
Click to collapse
Just hold down the button until it buzzes and reboots. Hardware reboot.
shobull.eu said:
but how to make a factory reset now? there is no item in menu.
Click to expand...
Click to collapse
Have you tried 'Unpair with phone'? To me that sounds like it would do a factory reset since an unpaired watch is basically useless.
Big change
Hi all,
Also got marshmallow, and biggest change for me is that it won't pair with phone. It comes up alright, and after accepting the Bluetooth code the phone wear app says "couldn't connect with ...". I tried factory resets (via unpair phone setting item), fresh install of wear phone app, and what not - still no luck.
Will try to downgrade and see if that helps.
Yours,
Christian
Hawkeye3 said:
Have you tried 'Unpair with phone'? To me that sounds like it would do a factory reset since an unpaired watch is basically useless.
Click to expand...
Click to collapse
From what I understand factory reset is "Unpair with phone" now, as when you select it asks: "are you sure you want to unpair and factory reset watch.
Interesting thing, is the new Reminders app, doesn't seem to work it asks to update android wear on phone when I open it, but nothing happens.
cholm said:
Hi all,
Also got marshmallow, and biggest change for me is that it won't pair with phone. It comes up alright, and after accepting the Bluetooth code the phone wear app says "couldn't connect with ...". I tried factory resets (via unpair phone setting item), fresh install of wear phone app, and what not - still no luck.
Will try to downgrade and see if that helps.
Yours,
Christian
Click to expand...
Click to collapse
I replied to you in the other thread but will post here as it may be useful to others..
I have the same issue. After OTA , i factory resetted and now it will not pair. I get "failed to pair...." I have tried multiple resets and cleared the data on the android wear app but no joy. I have gone back to 5.1.1 using the first post of the factory image thread. I was able to flash boot.img and system.img but recovery.img failed due to a partition error. Now everything is working again. Paired and synced on first attempt.

			
				
Downngrade wakes up watch
Hi there,
mhacin said:
I replied to you in the other thread but will post here as it may be useful to others..
...
I have gone back to 5.1.1 using the first post of the factory image thread. I was able to flash boot.img and system.img but recovery.img failed due to a partition error. Now everything is working again. Paired and synced on first attempt.
Click to expand...
Click to collapse
I also went back to 5.1.1 and things now work again - recovery flash also worked.
Seems the problem is really on the phone end. I have a Nexus 4 with "Fake stock" ROM (marshmellow). I could get the watch to pair with my Nexus 7 running stock 6.0..1 and that paired just fine. I also see other problems with the same Nexus 4 ROM with other bluetooth devices - e.g., my Jabra Tag II bluetooth audio RX/TX. I've posted on the ROM bug report forum.
My watch gives an error about a muted microfone although the mike is enabled everywhere in the settings where possible.
" Microfone disabled, waiting for injected audio."
Any suggestions?
Edit: Also the screen goes off after some time although I haven't enabled it anywhere?
Maybe I'll just reset it...
The biggest change for me - now we have native vibration when the watch disconnects (on connects) ... it was about f'in time ...
cholm said:
I have a Nexus 4 with "Fake stock" ROM (marshmellow).
Click to expand...
Click to collapse
I also have nexus 4 running Chroma MM. I will wait for OTA again and this time I wont factory reset to see how it goes
Manually updated mine to 6.0.1 using adb and now my iPhone (9.3 beta3 and latest android wear app) constantly looses connection. Have to pair as new device, restarting phone and/ or watch won't help.
Does anybody experience the same?
Might have to go back to 5.1.1 ...
Gesendet von iPhone mit Tapatalk
Hmm, well thats a disappointing. The removal of the reboot and reset is moronic and the new gestures are useless.
For the most part I cant get them to work, and even if I could why would I want to look like I was a nutter because I was randomly flapping my arm around trying (usually unsuccessfully) to control my damn watch?
delete me
mhacin said:
I replied to you in the other thread but will post here as it may be useful to others..
I have the same issue. After OTA , i factory resetted and now it will not pair. I get "failed to pair...." I have tried multiple resets and cleared the data on the android wear app but no joy. I have gone back to 5.1.1 using the first post of the factory image thread. I was able to flash boot.img and system.img but recovery.img failed due to a partition error. Now everything is working again. Paired and synced on first attempt.
Click to expand...
Click to collapse
Which 5.1.1 is better?
SharpSA said:
Which 5.1.1 is better?
Click to expand...
Click to collapse
I used the one at the top of the list. I don't know what the differences are between 5.1.1 versions

Bluetooth failed

Hi guys, just got my mix around a week ago. Flawless at first, no real complain, then this morning i noticed my smartband hasnt given me any notification and it turns out the phone bluetooth connection is dead.
Dead as in you can click it to tell it to turn itself on, but nothing happens. It doesnt recognise any bluetooth nearby either. Tried the test in the about section of the phone and it doesnt give me anything on the bluetooth status, just blank.
Tried restarting the phone, same thing. Factory reset, same thing. Im on 8.0 global rom straight from when i bought it. Any idea if this is hardware or software?
Thanks
I flashed EpicROM from last week and now I can't connect to my Bluetooth speaker. I can still see Bluetooth devices but it's not pairing. Worked on EpicROM from february
mr_sheen said:
Hi guys, just got my mix around a week ago. Flawless at first, no real complain, then this morning i noticed my smartband hasnt given me any notification and it turns out the phone bluetooth connection is dead.
Dead as in you can click it to tell it to turn itself on, but nothing happens. It doesnt recognise any bluetooth nearby either. Tried the test in the about section of the phone and it doesnt give me anything on the bluetooth status, just blank.
Tried restarting the phone, same thing. Factory reset, same thing. Im on 8.0 global rom straight from when i bought it. Any idea if this is hardware or software?
Thanks
Click to expand...
Click to collapse
That is vendor ROM.
Well at the very least you still able to toggle the bluetooth on and off, while mine just doesnt even budge. Really disappointing though...
mr_sheen said:
Well at the very least you still able to toggle the bluetooth on and off, while mine just doesnt even budge. Really disappointing though...
Click to expand...
Click to collapse
Think you are going to have to flash proper ROM
jazz452 said:
Think you are going to have to flash proper ROM
Click to expand...
Click to collapse
Yup. Im very rusty about all this rom flashing things nowadays. I'll read some and hopefully can flash some tonight, need my device up and running for monday morning :crying:
*edit:
Updated to 8.2 global and the Bluetooth still fudged. Guess im probably selling the phone then as it looks like hardware failure
mr_sheen said:
Yup. Im very rusty about all this rom flashing things nowadays. I'll read some and hopefully can flash some tonight, need my device up and running for monday morning :crying:
*edit:
Updated to 8.2 global and the Bluetooth still fudged. Guess im probably selling the phone then as it looks like hardware failure
Click to expand...
Click to collapse
Did that include full wipe?
jazz452 said:
Did that include full wipe?
Click to expand...
Click to collapse
Good point Jazz....when I dirty flashed to the 8.2 global rom I was having all kinds of forced closes literally almost every few seconds it seemed. It clearly stated in the guide if you go from developer rom to global you should do a complete wipe but I seemed to miss that part. I then re formatted and started from scratch and it worked like a charm after that...zero FCS. Give it another try if you didn't wipe it last time, could make the difference.
I'm from official rom 8.2.3.0 stable and without bluetooth since 3 days ... I wait for an official update or it's hardware problem ? What can i do ? I'm so sad and disappointed with this !
Nobody can help me ? It's software or hardware problem ?
[email protected] said:
Nobody can help me ? It's software or hardware problem ?
Click to expand...
Click to collapse
Try to do a clean flash with another rom, like global or last beta. Probaly, is a software problem.
I'm already on global rom ... A clean flash is full erase of the phone but Mi Mix without SD card is a big problem for backup all my phone ...
I gotts say i bought this phone with high hopes but it is a total c**p. Moving from opo5 I regret it all the way. My Bluetooth doesnt work also. I tried resetting phone and settings only since it doesn't back up app data (except for sone google spps) i dont want to factory reset. Anyone had a chance fixing it?
wolus666 said:
I gotts say i bought this phone with high hopes but it is a total c**p. Moving from opo5 I regret it all the way. My Bluetooth doesnt work also. I tried resetting phone and settings only since it doesn't back up app data (except for sone google spps) i dont want to factory reset. Anyone had a chance fixing it?
Click to expand...
Click to collapse
update firmware and install custom rom
wolus666 said:
I gotts say i bought this phone with high hopes but it is a total c**p. Moving from opo5 I regret it all the way. My Bluetooth doesnt work also. I tried resetting phone and settings only since it doesn't back up app data (except for sone google spps) i dont want to factory reset. Anyone had a chance fixing it?
Click to expand...
Click to collapse
Did you buy it new, which ROM, could it be vendor rom, do as suggested, back up you're data, install custom rom it's the only way to find out if it's hardware, no one else is reporting these sorts of problems even after 2 years of abuse.
Sorry posted in wrong section. I bought new global mix 2S and has latest ota.
wolus666 said:
Sorry posted in wrong section. I bought new global mix 2S and has latest ota.
Click to expand...
Click to collapse
Near enough mate.

Categories

Resources