yashsingh1/xdaforums huggingface dataset:
[Essential Phone Guides, News, & Discussion] luyen:
how to flash with twrp ? I have tried but not working.
[Essential Phone Guides, News, & Discussion] jgracz01:
wifi callling is working for me sprint variant
[Essential Phone Guides, News, & Discussion] anandlal:
I was on lineage. Flashed the factory image for NMJ32F then side loaded Oreo. Everything is running smoothly. No issues as yet.
[Essential Phone Guides, News, & Discussion] okgnew:
WiFi calling doesn't work for me anymore (even after re-enabling it in settings).

It was working fine on 7.1.1.

Otherwise it feels faster (with occasional stuttering while scrolling)
[Essential Phone Guides, News, & Discussion] treIII:
Motion photos is enabled on the Oreo beta if you have the Google camera installed
[Essential Phone Guides, News, & Discussion] luyen:
have anyway to flash from lineage?
[Essential Phone Guides, News, & Discussion] Charkatak:
For some reason the phone wouldn't register fast charging or a normal rate charge, but instead was possibly charging at the speed of PC's usb port :) At that moment, I disconnect then re-connect the power cable and that solves it. I have noticed this in Oreo mostly. Since I am not using original charger(I use 3rd party 5 port charger), I don't know if this issue would show itself using OEM charger.
[Essential Phone Guides, News, & Discussion] Lostdogs:
Im having the same issue since I loaded Oreo on to my device. Super frustrating.
[Essential Phone Guides, News, & Discussion] anandlal:
I contacted support. They think it's hardware related. They are going to send me a replacement device. Maybe if everyone who is having the issue let them know, it might be fixed.

After all the troubleshooting steps I did with them, they said it's hardware related... Even though it only started happening for me after KRACK.
[Essential Phone Guides, News, & Discussion] glasscitysd:
anybody getting a issue where a certain spot on the screen acts as if its constantly being touched? specifically on my phone the area where j would be on the google keyboard happens for awhile then eventually goes away if my screen is locked when it happens its almost impossible to unlock the phone
[Essential Phone Guides, News, & Discussion] Flapjack:
I got this phone yesterday and have not tried to root it or change recovery. I did unlock the bootloader and sideload Oreo, however. Overall, I am very impressed. Enough that I think I'll keep it. At this point, I'd like to root it and get my apps copied over from my Axon 7, but I haven't seen anything about rooting the Oreo beta.

Is it even possible?
[Essential Phone Guides, News, & Discussion] johnny8910:
Root is possible on Oreo, but not the easiest of methods to do it.

Look for rooting your PH-1, and use the 'Old Method' described.
[Essential Phone Guides, News, & Discussion] SquireSCA:
For everyone that is using the Beta... Is it worth it, or should I just wait for an official release?

While part of the allure of Android is being able to have the latest and greatest versions, I don't want to have BT hiccups or break Android Auto or something that I use on a daily basis...

How buggy is it, now that you guys have had time to play with it for a bit?
[Essential Phone Guides, News, & Discussion] TheDethEgineer:
Zero BT issues for me
[Essential Phone Guides, News, & Discussion] SquireSCA:
What about Android auto? 2016 Colorado Z71 with MyTouch.

Any other things to consider before pulling the trigger?
[Essential Phone Guides, News, & Discussion] okgnew:
I don't use Android Auto.

BT works with my car, headphones and smart watch, but I see a much higher battery drain when BT is on (comparing to 7.1.1 ROM).

I also get a random reboot about once a day.

And few random app crashes about 3 times a day.

So lots of minor issue, but nothing too bad (it's a beta ROM anyway).
[Essential Phone Guides, News, & Discussion] Shadow Samurai:
For those of you who want root on Oreo, just flash the Oreo compatible boot image file in fastboot and then install magisk app and let it update. That's it. I went in circles for 2 hours when I first got it Monday night. I'll post my battery life and SOT later today. So far it is AMAZING. 70% battery remains and I've been using the phone heavily gaming, lots of YouTube, etc. 2.5 hours SOT. Will see when it finally dies. I got 4 hours of SOT with my normal daily usage and the battery was only at 50% when I went to bed and plugged it in. I'm expecting between 6-8 hours SOT end of today.

It did used to get hot because of me having restored from backup on titanium backup app data (excluding system apps, only app data because of Google restore services when setup and XML) and something weird was going on with Google play services. I wiped the data of all Google related services and since then fixed the issue with battery drain.

I do have greenify active as well in root mode.

Link to Oreo modified boot:

https://drive.google.com/file/d/1r-x8TuNNZuZVDE7Fhu7tAHnBw92gMO-E/view?usp=drivesdk
[Essential Phone Guides, News, & Discussion] Flapjack:
Thanks for the info on root. Sounds very simple.

As for battery, I really don't have much to compare with, as I didn't run 7.1.1 for more than a few hours. It was very laggy to me. Oreo is much smoother. I've been up about 4 hours, with maybe an hour of screen time and probably two hours of Pandora over Bluetooth. I'm at 50%. Not very impressive, but zero BT issues, crashes, etc. Thinking of giving LOS a try, but does that mean I'll have to flash back the stock modified boot?
[Essential Phone Guides, News, & Discussion] Shadow Samurai:
Yes. You would have to flash back the 7.1.1 image. Also. BT is a huge drain on battery ATM on Oreo and lineage. I haven't been using it as much until the issue is fixed.
[Essential Phone Guides, News, & Discussion] Flapjack:
Are you just backing up the 7.1.1 image before you flash it, or are you using the one from inside the PH1-Images-NMJ32F.zip file?

As for BT, I guess I'll just keep it off when I'm not actively using it. Is that the primary source of battery drain then?
[Essential Phone Guides, News, & Discussion] Shadow Samurai:
BT is the primary source of battery drain. Essential themselves say that before you download the Oreo beta.

All info you looking for is in this guide thread:

https://xdaforums.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976/page21

Basically if you want to downgrade back, download the fastboot file off essential website and fastboot flash it. That should be it. If you want root, refer to the thread above and get the modified j32 image file.
[Essential Phone Guides, News, & Discussion] 12paq:
Essential Oreo Beta release notes say that Bluetooth might drain the battery faster. They implied it would be fixed in the next Oreo release.
[Essential Phone Guides, News, & Discussion] Flapjack:
Yeah, I read all the notes, so I wasn't surprised about the battery drain. I don't remember it saying t was specifically in regards to Bluetooth, though. I may have missed that.

What I have been surprised by is people saying they are getting great battery life out of the beta Oreo build. If it is primarily due to BT, however, that would explain it.

One thing I noticed is that the phone simply does not want to charge on my Axon 7 battery charger. It'll say "charging slow", "charging rapidly", "charging slow", then disappear for a few seconds before starting the cycle again. Almost like it's a bad connection or something (works perfectly fine on my Axon, and I never pull on or bend my connectors). I plugged it into the included charger and it charges just fine. Weird.
[Essential Phone Guides, News, & Discussion] 12paq:
Beta builds can be odd like that. I get great battery on Oreo, some do not. Maybe because I don't use bluetooth much?

On chargers, my Pixel C charger will charge the PH-1 rapidly, however my Qualcomm 3 charger will not, again go figure? Possibly OEM chargers use different versions of Qualcomm chargers and software for their own devices? I don't really know enough to say for sure. But you've got curious now! Cool, something new to research. :good:
[Essential Phone Guides, News, & Discussion] Shadow Samurai:
5 hours 20 min SOT and still got 30% left.

My old OnePlus one barely got 3 hrs before almost dead.
[Essential Phone Guides, News, & Discussion] TheDethEgineer:
Essential and Pixels uses Power Delivery USB Standars to charge, while Quick Charge is a Qualcomm stantard
[Essential Phone Guides, News, & Discussion] 12paq:
Thanks! :good:
[Essential Phone Guides, News, & Discussion] prgopala:
Does the stock camera take a while to load on this Oreo beta? Have a black screen at the launch of the app and then the viewfinder loads up.
[Essential Phone Guides, News, & Discussion] Flapjack:
Thanks for both posts. So many sites listed the PH-1 as a QC 3.0 phone, which is obviously BS. Glad I read your posts.

I'm getting ready to flash the modified Oreo boot and root this damn thing.

---------- Post added at 01:40 AM ---------- Previous post was at 01:03 AM ----------

I was able to get Magisk working using the method Shadow Samurai. Very, VERY easy.

My only question now is in regards to TWRP. I found a TWRP for Oreo, but the typical "fastboot flash recovery _____.img" failed with the error "no such partition". I think looked at the OP of the root thread, and it said to use "fastboot flash boot oreotwrp.img". Why would I want to flash boot for TWRP? I didn't even attempt it, because I didn't want to mess anything up.
[Essential Phone Guides, News, & Discussion] lkhafra:
I think that's just to not into TWRP but don't quote me on that. It's 5am and I haven't gone to sleep yet.
[Essential Phone Guides, News, & Discussion] vergilbt:
LOL...

Then turn your phone off
[Essential Phone Guides, News, & Discussion] lkhafra:
I can't I've been doing Christmas shopping. I have to go renew my license in a little bit and take my teenager cloths shopping. Then after that 18 other things. Then after that get this BOGO iPhone deal from T-Mobile for the two older kids. Whoooo busy busy busy. At least she can drive so I don't have to.
[Essential Phone Guides, News, & Discussion] arya9901:
I have a 2017 Chevy Bolt EV and have no issues at all with Android auto so far on the beta. No Bluetooth issues either. Battery life is not as good as expected as I have a Pebble watch so Bluetooth is on all the time.
[Essential Phone Guides, News, & Discussion] 12paq:
TWRP is now with the boot partition. It has to do with the new A/B partitions. Read the first several pages of the root guide thread, then it will make more sense. :good:

Also, for the TWRP for Oreo is bare bones. At first it had no touch, and now I think it has no encryption. But they are working on it. For now I just use Fastboot and ADB for flashing and backups.
[Essential Phone Guides, News, & Discussion] SquireSCA:
Hmmm... Well, if there is no real advantage to updating, and if updating will reduce battery life, then it probably makes sense to wait for the next update... It seems that you give up more than you gain with the beta at this time...
[Essential Phone Guides, News, & Discussion] kbonnel:
Anybody able to perform adb reboot recovery command (and actually work) after applying oreo beta? My phone just reboots normally. I can get into there by manually going into fastboot and then recovery. Unfortunately, when I attempt to reload the beta (just to test) and select Apply update from ADB, I get strange errors basically saying:

(it indicates this twice)

unable to open sysfs usb mode failed to set driver control

Then it asks to send the file. When I type adb devices, I get the following response:

? sideload

The phone boots fine, and seems to work fine with Oreo.

Thanks
[Essential Phone Guides, News, & Discussion] Flapjack:
Sounds like a major change in the way things have been done for years, but I'll have to check it out. So you're saying the TWRP has the same functionality as a normal boot partition , but the phone some how knows to look there when you trigger a boot into recovery? Is this linked to the post below ("adb reboot recovery" just reboots phone normally)?

I haven't tried reloading the beta, but I've definitely noticed "adb reboot recovery" not working as expected. I wonder if it has something to do with the A/B partitioning scheme 12paq mentioned above.
[Essential Phone Guides, News, & Discussion] 12paq:
No.

Read the op from this:

https://xdaforums.com/essential-phone/development/rom-lineageos-14-1-essential-ph-1-mata-t3703759

Hope it helps.

Edit: More infos, the A/B partition setup help keep OTAs from bricking devices. This has long been an OEM's nightmare. However it changes the custom ROM communities in how they flash recovery and GAPPs etc. Fortunately we have devs and users who have experience with A/B partitions from the Pixel devices. I would go into more detail here but Google search is your friend and I am just getting up to speed myself.
[Essential Phone Guides, News, & Discussion] Flapjack:
Yeah, I read it.... but other than it being "different", I still didn't quite understand it. After doing some more reading, it sounds like a typical A/B setup for an operational mission system, where one is an active side, and the other one can be updated, and you can flip back and forth. I just don't know if it's as robust as some of the systems I've worked on, where you can flip back and forth as needed for testing, or reversion. It sounds like the Android system just boots to the other "side" if it encounters a problem. It would be kinda cool to dual boot different ROMs as you needed.

Here's the best info I got on it:

https://source.android.com/devices/tech/ota/ab_updates
[Essential Phone Guides, News, & Discussion] 12paq:
Cool! Thanks. Reading now.

Before I read this I updated my post as well.
[Essential Phone Guides, News, & Discussion] Flapjack:
Yeah, it's got a huge amount of detail in it. I definitely feel better about the idea, vs how I was resistant to change just a few minutes ago, lol.
[Essential Phone Guides, News, & Discussion] Charkatak:
Any sign of "double tap to wake" feature on Oreo?
[Essential Phone Guides, News, & Discussion] Shadow Samurai:
No. Custom kernel maybe, but as the unofficial lineageOS builder for this phone said:

Tap to wake implementation in a phone that touch hardware drivers didn't support it just cause excessive battery drain.

Finger print reader is really damn fast so no need really. Just change of habits. I had asked about this in the lineageOS forum.
[Essential Phone Guides, News, & Discussion] Charkatak:
I see. I wouldn't need Tap to wake if fingerprint reader would be in the front.
[Essential Phone Guides, News, & Discussion] Shadow Samurai:
Screenshot from what invisiblek stated.

Makes sense. I do agree with you that it is nice, I used it for 4 years with my trusty OnePlus one until I finally upgraded to this phone and lost that feature.

Battery life is the most important thing to me, I don't want anything draining it. That damn OnePlus barely was lasting 3 hours SOT when I finally laid it to rest.
[Essential Phone Guides, News, & Discussion] Charkatak:
So in order to have Tap to wake feature, touchscreen needs to support it? Is Essential able to add that to the firmware or the touchscreen hardware isn't supporting it?
[Essential Phone Guides, News, & Discussion] elkay:
Basically, the touchpanel firmware needs to support tap to wake. If the firmware supports it, then the whole device doesn't need to be awake checking for the touches.
[Essential Phone Guides, News, & Discussion] dago:
Sometimes i can't awake my phone, screen keep black.

My essential is rooted and i use a theme with substratum.

Someone else with same issue ?
[Essential Phone Guides, News, & Discussion] Flapjack:
QUOTE=Charkatak;74627206]I see. I wouldn't need Tap to wake if fingerprint reader would be in the front.[/QUOTE]

So you would give up the ability to security lock your phone for the ability to wake it up from the front side? There's no security for DT2W. If you did have a PIN/pattern after the double tap, then it would be slower than just using the fingerprint reader.

Not having that issue. Having very few issues, actually. Here are my big ones:

- Camera sucks bad. Slow, doesn't focus well, crashes often. At least it will start back up (vs some camera crashes that require you to restart the phone). Need to figure out how to install the google camera, and if that's even worth it.

- Weak vibrate strength. Can't tell when I get a notification when it's on anything but a hard surface. Definitely don't notice it vibrate when it's in my pocket. Couldn't find a setting to adjust.

- Obviously the BT battery drain. Hopefully the official Oreo release comes out soon (or at least another beta with that bug fixed).

Other than those things, I simply can't believe this is a beta. I'm amazed at the battery life (with BT off).
[Essential Phone Guides, News, & Discussion] rignfool:
Maybe I've just had devices with bad battery...

But WHAT Bluetooth battery drain?

I leave all radios on all the time... On Oreo... And leave my charger at home? And this is still the best in terms of battery I've ever gotten
[Essential Phone Guides, News, & Discussion] bergsim:
just updated 2hr everything looks ok for now but i am missing wifi calling option its not there under call setting i am on att and it was there on 7.1.1
[Essential Phone Guides, News, & Discussion] glasscitysd:
WiFi calling is in the wifi settings in Oreo can also be added to your drop down notification panel
[Essential Phone Guides, News, & Discussion] bergsim:
It's not there I can't find it anywhere
[Essential Phone Guides, News, & Discussion] SquireSCA:
Yeah, when I upgraded to Oreo yesterday, Wifi Calling went away in the settings.
[Essential Phone Guides, News, & Discussion] bergsim:
WiFi calling and video calling gone
[Essential Phone Guides, News, & Discussion] spotmark:
I've been running the Oreo beta, rooted, since the day after they released it. I've tried to find things wrong with it, and I can't. The biggest gripe I've seen is the stuttering scrolling. I haven't noticed it at all, and I've tried all kinds of scrolling. Slow or fast the phone scrolls fine. I guess the BT drain is a problem for some people, but I only use mine when I'm in the car, so I turn it on and off as needed. With Substratum, I can't believe that I'm actually happy running stock. Go figure.
[Essential Phone Guides, News, & Discussion] 12paq:
Same here. Would love to have it back.
[Essential Phone Guides, News, & Discussion] mpetruzz:
So did you root your phone and then sideload the beta?? I'm thinking about rooting and the beta but wanna make sure I do the right order
[Essential Phone Guides, News, & Discussion] spotmark:
Install build first, then root.
[Essential Phone Guides, News, & Discussion] Flapjack:
Are you sure you're looking in the right place? Maybe it moved with Oreo... it's kind of buried and non-intuitive. For me, it is under Settings > Network & Internet > Wi-Fi > Wi-Fi preferences > Advanced > Wi-Fi calling.
[Essential Phone Guides, News, & Discussion] 12paq:
Yes.
[Essential Phone Guides, News, & Discussion] Flapjack:
I'm having a whole host of issues, and I think it's since I tried the latest Google Camera APK. The camera was barely useable. If I took a picture, it would not show up in the gallery preview, and the camera app would lock up. If I closed the camera and opened the gallery, the picture would be there, but there would be successive pictures of nearly the same scene... as if I had been holding the camera button down instead of taking a single pic. I tried to uninstall it, but that wasn't an option (I forgot to backup the stock camera app). However, when I run camera it's definitely the stock camera again. In that regard, all is well.

The problem is with a whole host of apps force closing. Gmail, Nine Exchange email, and a bunch of others. Some close when I try to open them (eg: Gmail), others try when I try to open something after the app opens (eg: opening any email in Nine). If I reboot the phone, the phone buzzes several times... presumably due to startup apps force closing.

I cleared the cache/data for each app having the problem, but it doesn't help. I'd like to wipe the phone's cache via recovery, but that's not an option with this recovery (vol up + power just shows the open android with a "No command" message).

Any ideas?

---------- Post added at 09:50 AM ---------- Previous post was at 09:49 AM ----------

Very weird. I'm guessing we upgraded the same way... I upgraded each OTA (I think there were three) prior to downloading the Oreo and unlocking the bootloader to install it.
[Essential Phone Guides, News, & Discussion] 12paq:
My install was the same. But I did try the first LOS version in between. But went back to the latest 7.1 then followed Essential's guide to flash the beta 8.0. I'm not blaming LOS, it's all on me.

For Open Camera the latest version did not work for me. I had to roll back to an earlier version.

As far as battery goes mine has been great since I turned off "Mobile Data Always Active" in Developer options. For some strange reason Google has this switched on by default in some of their Oreo betas. It's the same with the Pixel phones. I live at a fringe area that constantly switches between H and LTE. So this helped me with wifi on.

This beta is rock solid for me except for me loosing wifi calling on ATT.
[Essential Phone Guides, News, & Discussion] Acronet:
For me on T-Mobile Wi-Fi Calling now is on the Phone app setting. So go to Phone - Settings - Calls - Wi-Fi Calling.
[Essential Phone Guides, News, & Discussion] 12paq:
First place I looked. No go.
[Essential Phone Guides, News, & Discussion] Flapjack:
I'm still getting FCs all over the place. Not sure what to do, at this point. Wish I had done a backup of the stock camera app. Sucks not having TWRP to do backups before you mess with things.

It has to be the camera APK. I haven't done much else to the phone, and the Fact started the day after I tried the google camera. The only major issue I had before installing the google camera APK was the horrendous battery drain with BT on. I haven't touched the mobile data settings, but it's clearly draining out with BT on. I can sit at 100% for an hour before it drops to 99%, so long as I don't turn on BT.

At least the XDA app is not one of the problem apps!
[Essential Phone Guides, News, & Discussion] mpetruzz:
I actually returned my first PH1 due to FCs etc. Turns out it very well may have been due to flashing the modified Google camera apk

I just bought another one and it's running like a champ and I haven't installed the Google camera apk
[Essential Phone Guides, News, & Discussion] bergsim:
Same here it's just disappeared wifi calling and video calling I am using it on at&t maybe that's why
[Essential Phone Guides, News, & Discussion] Flapjack:
Well, I'm sure it's something I did, so I'd feel bad returning it. Did you try reinstalling from scratch before you returned it?

Did you have your SIM in when you ran through the initial setup wizard?
[Essential Phone Guides, News, & Discussion] Mania626:
Is anybody experiencing crackling noise when talking on the phone or listening to a voice note on the speaker phone?
[Essential Phone Guides, News, & Discussion] SquireSCA:
It's not under my settings on that screen. What APN are you using?
[Essential Phone Guides, News, & Discussion] Flapjack:
The "T-Mobile US 260" one. I haven't touched the APN settings. It auto-provisions for me... but I do make sure I have the sim card in when I boot the ROM for the first time.
[Essential Phone Guides, News, & Discussion] SquireSCA:
Ahhh... I am on ATT. It was there on Nougat, but upgrading to Oreo on ATT seems to remove it.
[Essential Phone Guides, News, & Discussion] Shadow Samurai:
Hey. Guys. Actually use the search engine in your settings app.
[Essential Phone Guides, News, & Discussion] SquireSCA:
We did. It lists it in the search, and when you click on it, it takes me to this screen. By all means, please highlight the setting here for me. LOL
[Essential Phone Guides, News, & Discussion] Shadow Samurai:
Hmm. Ok

Go to wifi preferences under WiFi access points. Then advanced and that where it is for me. I'm on t mobile. And let's not share our Mac and ip address anymore. Lol :silly: