Hello all, I recently acquired an Essential PH1 from a friend after he said that the last person he let borrow it to see if they wanted to buy it, they said they updated to Android PIE from OREO and afterwards sound was lost, when you call the speaker button is already pressed and you can't toggle it to the earpiece, YouTube videos won't play (keeps loading) but ads will play with no sound. This is the weirdest thing I've ever seen.
I tried flashing LineageOS onto the device to see if a different OS would solve the issue, but no dice. Anyone have any ideas? I'll take them all. PLEASE HELP!
EDIT: Downgraded to 7.1.1 and I'm greeted with a "Can't play this video" screen and my screen does not work. Sound still doesn't work. What should I do?
Try this, sideload the first PIE Essential OTA (August 2018 Release | Android 9 Pie, Release 1), which you can get from Essential' s developer site. This should make sure that the bootloader and vendor partitions are correctly updated. Make sure to factory reset after the install so everything is wiped.
Related
Hi,
First of all I'm a complete noob,
I was on Marshmellow 6.0.1 (NO ROOT) and signed up for Android N beta and tried to update my phone to the beta version and started downloading it, in the meanwhile i had no idea how, but all of a sudden i got the Android N update when i thought that i was updated to android N beta.
So, i went ahead and updated my phone and then the problem started,
the system UI frequently stops working and puts my phone to the lock screen and i observed, this happens everytime i press the overview softkey
Any ideas, what might be the problem and how to resolve it?
Nexus 6p, unlocked bootloader and running 8.1DP.
Whenever I make a call and put the phone to my ear the screen turns off and never comes back on. I tested the sensor with the device info app and I the sensor stays in the "close" position when engaged untill the app is restarted.
I did some research and I found that some users had this issue with the Nougat update but no relevant solutions were found and the 7.1.1 update fixed the problem.
I would like to avoid factory reset or locking the bootloader if possible.
Can anyone think of a possible solution?
I tried the Proximity sensor reset app from the play store and that does absolutely nothing.
EDIT: Stable 8.1 doesn't fix the issue, even after clean install and manual flash and wipe.
I'm on SuperXe 8.0 Oreo built and it works flawlessly. I remember having that issue on nougat ROMs use to drive me nuts. Every time I needed the keypad I had to fight to get the screen back on. ?
Not a factory reset. Manually wipe the phone and apply the latest 8.0 image.
So after manually flashing the 8.0 image everything worked. I thought id give 8.1 DP2 a shot and I wiped and flashed this manually. It worked during the restore but stopped working after all my apps were back, so I thought it may be an app that's causing the problem. Strated in safe mode, issue is still there. I guess Ill just have to wait for the stable 8.1 release. If anyone else is facing the issue please post here.
I recently acquired a Nexus 6P.
TWRP is properly installed as the Recovery - twrp-3.2.3-0-angler
First thing I did with the device was flash the latest Android 8.1 Oreo version to it - angler-ota-opm7.181205.001-abb36a2f
I then installed Lineage OS 15.1, Open G Apps 8.1 (nano), and SU
From there I've done nothing but struggle with bugs and quirks. The device has been re-imaged several different times, with different variations of the above setup, and one of the main things I need to get working (Android Auto) keeps failing. Does anyone have any idea why Android Auto keeps pulling up the error "Google Play Services doesn't seem to be working right now"
All of the suggestions I've found online have failed. Screenshots have been provided for the version info and error. I've already cleared the data caches and tried to re-install and re-flash the device.
I got pissed and went back to JUST the stock OTA for testing/verification. With the stock rom there are no issues. Seems like Lineage OS 15.1 on the Nexus 6P has some bugs to work out. A fully functional stock phone is better then being frustrated.
If anyone can confirm I'm not crazy or explain what I missed while troubleshooting that would be awesome.
GTF696 said:
I got pissed and went back to JUST the stock OTA for testing/verification. With the stock rom there are no issues. Seems like Lineage OS 15.1 on the Nexus 6P has some bugs to work out. A fully functional stock phone is better then being frustrated.
If anyone can confirm I'm not crazy or explain what I missed while troubleshooting that would be awesome.
Click to expand...
Click to collapse
Try magisk as root method insted of su...
Other than that, cant think any other solution
GTF696 said:
I recently acquired a Nexus 6P.
TWRP is properly installed as the Recovery - twrp-3.2.3-0-angler
First thing I did with the device was flash the latest Android 8.1 Oreo version to it - angler-ota-opm7.181205.001-abb36a2f
I then installed Lineage OS 15.1, Open G Apps 8.1 (nano), and SU
From there I've done nothing but struggle with bugs and quirks. The device has been re-imaged several different times, with different variations of the above setup, and one of the main things I need to get working (Android Auto) keeps failing. Does anyone have any idea why Android Auto keeps pulling up the error "Google Play Services doesn't seem to be working right now"
All of the suggestions I've found online have failed. Screenshots have been provided for the version info and error. I've already cleared the data caches and tried to re-install and re-flash the device.
Click to expand...
Click to collapse
I got error when installed lineageos15.0 on twrp 3.2.3 , suddenly automatic restart. Can you help me dude ?
will be that you can support me on something about this device, a while ago I wanted to install a rom lineage 15.1 and had many bugs, one of them was that Dolby stopped audio did not want to open, so I decided to change it to stock again using minimal adb, and all good, I start the cel, but the problem continued, and restart it I get a message like 10 times in a row that says "daxUser stopped" after that, I skip another window where it says the "internal system is damaged and may be unstable to restore the cell phone factory "and I do not know what to do because I have already installed the rom allegedly stock several times and it does not take off in fact does not sound at all, the speaker is dead, I can not make calls, if the resiven but nothing is heard, it no longer connects to wifi, it leaves the few applications without any reason. ect etc, I hope you can support me with that, and if there is any solution it would be great.
Unroot, lock and take it back for repairs? Sorry, not very XDA-style answer.
Edit: are you completely sure that you flashed the right stock ROM for your device?
Try again
Alvaro Luna said:
will be that you can support me on something about this device, a while ago I wanted to install a rom lineage 15.1 and had many bugs, one of them was that Dolby stopped audio did not want to open, so I decided to change it to stock again using minimal adb, and all good, I start the cel, but the problem continued, and restart it I get a message like 10 times in a row that says "daxUser stopped" after that, I skip another window where it says the "internal system is damaged and may be unstable to restore the cell phone factory "and I do not know what to do because I have already installed the rom allegedly stock several times and it does not take off in fact does not sound at all, the speaker is dead, I can not make calls, if the resiven but nothing is heard, it no longer connects to wifi, it leaves the few applications without any reason. ect etc, I hope you can support me with that, and if there is any solution it would be great.
Click to expand...
Click to collapse
I have a Retla and received official 9.0. download the 89-2 stock firmware. You can find it here. Use the .bat
File, place inside extracted firmware click & when it restarts you should get a notification to download 89-5.. once it completes the next notification will appear.. that's 116-11 9.0..
mod edit - telegram chat spam removed
I have what appears to be a demo device; this one will not do OTA.
So I installed the newer roms but then speech to text, the microphone would not work except only for calling. I downgraded to the stock rom and it was fine.
But I decided to keep trying I was hoping it might be something I did wrong and could upgrade. Still no microphone so I downgraded back to stock again. This time; Wifi completely stopped working. It will not detect any wifi networks. Some goggle searching said that it is possible the modem got messed up. Not sure what to do. I tried flashing again it didn't make any difference.
One thing I noticed though is the first time when downgrading I forgot to turn on USB debugging, but it still allowed me to do it and it went smoothly.
Having no wifi on a smartphone with no apps on it is a bad thing
Well some google search told me if this happens you can flash to the July Oreo update and your stuff will work. I did that and it worked. My ,ic still won't record sound so then I went back to the 7.1.1 and it works fine. Too bad I am stuck with nouget or my mic will not record stound and I cannot do OTA.
Here is the thread I found which was quite helpful.:
https://forum.xda-developers.com/essential-phone/help/wifi-android-p-t3790678
I just used the July Oreo update, the fastboot version.