AOSiP 9.0 [Official]

[Randal84]

Tried out the latest update yesterday...


I first want to say that I always run a fresh install ( because I flash back and forth ROMs so much) Wipe everything but internal storage (dalvik cache, system, data)install ROM, install TWRP, reboot recovery, install aroma gapps (I like to pick and choose what I want installed) install Magisk, reboot to ROM.

I also as another person posted, had out the gate, Bluetooth crashes. It was intermittent for me, sometimes would happen and sometimes would be fine. After a couple reboots and app updates, it went away. So idk what the cause was but I noticed another person had Bluetooth crashes and I just wanted to say they're not alone.

I've noticed when the phone drops from LTE, to 3G, or 1X (my house and workplace are dead zones) it shows 31000 for the carrier name instead of Verizon. It's never done this before on ANY ROM I've used on ANY device I've had in the past. In fact it normally says Verizon Wireless for 1X and 3G and only Verizon for LTE. I've ran past versions of this ROM and never had this issue, nor have I had it do this on other devices in the past either, and I've been on Verizon for nearly 10 years. Reboots don't fix this issue. I also tried uninstalling and reinstalling the SIM card, with the device on, and it still does it.

The next issue and this is for me, a bigger issue, is now when I get an MMS, or more particular, a screenshot sent to me it comes in blurry. My job involves getting texts from my boss with job assignments, and on a regular basis, screenshots of info related to what I need to do, so when numbers are blurry it makes things a bit harder, so this is for me a big issue. Again this hasn't happened on past versions of this ROM, and definitely not the stock ROM. I have tried other ROMs aside AOSiP on this device and havent ran into this issue there either. The only time I ran into this issue was on my HTC 10 but every single custom ROM that wasn't Sense ROM based (stock ROM) would do it, meaning any ROM that was AOSP/Lineage based (Lineage crDroid, and yes even the HTC10 variant of AOSiP would do it) so I knew it was something specific with that device. This seems to be ROM based, and in my opinion, these issues have something to do with the update and maybe even related to the switch from Quickstep, to Lawnchair as the base Launcher.

I tend to go between this ROM and the stock ROM. As I mentioned I've tried a few others for this device but this seems to be my favorite for a custom ROM. I don't mind Lawnchair over Quickstep, because frankly I don't use Quickstep....or Lawnchair for that matter. Even on the stock ROM I dont use it Quickstep. I use CPL, but the nice thing with Lawnchair is it doesn't interfere with the additional download required to use Google discover on it. Quickstep likes to block it from being installed, so I was happy seeing that the developer used a different base Launcher other than Quickstep, but these issues seem to have came along with the change. Hoping that this can be fixed for the next update. Just wanted to outline some issues I noticed in using the latest update, great job otherwise guys, keep up the great work!

 

[Randal84]

UPDATE!

So I flashed back to stock rom, and after a couple days I decided to give this update a try again. The blurred MMS issue is gone. Must have been a bad flash, or a better guess would be related to gapps. I had originally flashed nano gapps and then decided to flash aroma gapps over it. I've never used nano gapps before, and learned when you install that and install the Google dialer from the play store vs through aroma and have installed as a system app, you don't get to use visual voicemail. The stock dialer would allow it but I don't use that. The re flash fixed that issue.

Still have the Bluetooth issue. Again it's intermittent. I can boot the phone and start getting Bluetooth crashes, reboot the phone and then it's working again. Seems to be something happening whente phone boots up because it either works or doesn't from boot.

The carrier name bug is still persistent, again it drops to 3G or 1X and says 31000, instead of Verizon. It's not affecting calls or a signal issue of it working or not. I can make and take calls like always, just seems to be a weird bug, but I've just never seen this happen before in years of numerous Android devices and being with Verizon for many years.

Just thought I'd give an update on relation to my previous post.

Curious to know if an update to 10 is in the works for this ROM?

 

[rignfool]

UPDATE!

So I flashed back to stock rom, and after a couple days I decided to give this update a try again. The blurred MMS issue is gone. Must have been a bad flash, or a better guess would be related to gapps. I had originally flashed nano gapps and then decided to flash aroma gapps over it. I've never used nano gapps before, and learned when you install that and install the Google dialer from the play store vs through aroma and have installed as a system app, you don't get to use visual voicemail. The stock dialer would allow it but I don't use that. The re flash fixed that issue.

Still have the Bluetooth issue. Again it's intermittent. I can boot the phone and start getting Bluetooth crashes, reboot the phone and then it's working again. Seems to be something happening whente phone boots up because it either works or doesn't from boot.

The carrier name bug is still persistent, again it drops to 3G or 1X and says 31000, instead of Verizon. It's not affecting calls or a signal issue of it working or not. I can make and take calls like always, just seems to be a weird bug, but I've just never seen this happen before in years of numerous Android devices and being with Verizon for many years.

Just thought I'd give an update on relation to my previous post.

Curious to know if an update to 10 is in the works for this ROM?

Everytime you ask for an ETA...

A Dev somewhere gives up

 

[Randal84]

Everytime you ask for an ETA...

A Dev somewhere gives up

Wasn't asking for an ETA, but merely if we can expect Android 10 variant of this rom or not. Take as long as needed. So no I wasn't asking for an ETA, thank you.

 

[FaTaLCrAsH]

Wasn't asking for an ETA, but merely if we can expect Android 10 variant of this rom or not. Take as long as needed. So no I wasn't asking for an ETA, thank you.

There is an unofficial version of Android 10 available, it's fairly stable and I use it as a daily driver. It's on another thread and not build by the team. Also if you want to fix your Bluetooth, completely flash stock img. After you install the ROM flash the last Bluetooth and radio images.

 

[Randal84]

There is an unofficial version of Android 10 available, it's fairly stable and I use it as a daily driver. It's on another thread and not build by the team. Also if you want to fix your Bluetooth, completely flash stock img. After you install the ROM flash the last Bluetooth and radio images.

Thanks for the info

I tried out the unofficial AOSiP Android 10 for a couple days but ultimately ended up flashing back to 9, for reasons stated on that forum. In a nutshell, my opinion is that Google needs to quit trying so hard to copy Apple / iOS. They did with pie and the blinding white everywhere and now the removal of ambient display in means to have face ID...the damn pixel 4 looks identical to the iPhone 11. IDK what was so wrong with Material Design, that they felt the need to change it so much. First the Dialer, back when it had the transparent blue background and now even more so with the newer style, then the white and blue color scheme, now face ID, and rectangle camera box after they mocked Apple for needing more than one camera to get an amazing picture on a phone ( yet the pixels have always been highly regarded as the best telephoto lens on a phone)

Anywho enough ranting..

I can live with the whole reboot if the crash dialog kicks in. If I understand right, wouldn't flashing the stock img get rid of magisk? Magisk modifys the stock boot img correct? I use quite a few apps and modules through magisk, so of that's the case then that's a no go. Like I said I can live with the whole reboot once the crash dialog kicks in and that's always right after I e restarted the device for any reason, so I'll know right away and just rest it again. Good to go until I reboot the phone again for whatever reason.

 

[VVegetto]

There is an unofficial version of Android 10 available, it's fairly stable and I use it as a daily driver. It's on another thread and not build by the team. Also if you want to fix your Bluetooth, completely flash stock img. After you install the ROM flash the last Bluetooth and radio images.

How to download unofficial 10 for Essential Phone? I want to try it. Thanks.

 

[the_Pan]

How to download unofficial 10 for Essential Phone? I want to try it. Thanks.

Try this thread: https://forum.xda-developers.com/es...nt/unofficial-lineage-17-0-android-q-t3966864

 

[brepeti]

Hi. What is the default system font type name in this rom? This is awesome.

 

[n0ve]

According to "Web" fonts only. Your chances are one in 15,698 Families. Get focused... Scroll... May the luck of not knowing simpler ways be with you.

https://cutt.ly/QeaDQoq

 

[FaTaLCrAsH]

How to download unofficial 10 for Essential Phone? I want to try it. Thanks.

The link needs to be updated. Stay tuned

 

[nijohnson]

Hiya. Probably an easy question. Each time I flash the rom, my sim card seems to get lost. Right now, I'm on the last Pie stock. I'm flashing OpenGapps 9 arm 64 micro, and magisk 20. Am I missing some update of some such?

 

[CamoGeko]

Hiya. Probably an easy question. Each time I flash the rom, my sim card seems to get lost. Right now, I'm on the last Pie stock. I'm flashing OpenGapps 9 arm 64 micro, and magisk 20. Am I missing some update of some such?

Are you using a Sprint device?

I'm pretty sure they're sim locked, and you can't really do anything with them unless you get it unlocked by Sprint.

 

[ceelos218]

Are you using a Sprint device?

I'm pretty sure they're sim locked, and you can't really do anything with them unless you get it unlocked by Sprint.

all you have to do is flash old modem files located somewhere in this thread https://forum.xda-developers.com/essential-phone/how-to/discussion-brainstorm-sim-unlock-t3724135.. that's how I got my Sprint unlocked.

 

[foueddyf]

@xlxfoxxlx

Been using your rom for a year, its been great, and just updated to the lastest AOSiP-9.0-Official-mata-20200211.zip.
The changelog indicates the February 2020 Security Patch is included but the build.prop still indicates ro.build.version.security_patch=2019-08-05
Anyway you can update the string on your future updates? Thanks

 

[Erven2017]

The mobile data tiles seems to not work

Even thought I close mobile data switch in settings, the mobile data always is working, apps could connect to network still

ROM: AOSiP-9.0-Official-mata-20200310.zip

 

[foueddyf]

AOSiP 10 (Android 10) released yesterday.
Haven't tried it but just letting u guys out there know there's another Android 10 rom to try.

 

[howardsean]

AOSiP 10 installation guide?

 

[CamoGeko]

AOSiP 10 installation guide?

Its in the 1st post.

 

[The Doctor04]

So there is an official build and a gapps link. Is that a no gapps vs gapps install? Both are the same size so I was wondering what the difference was between the two.