yashsingh1/xdaforums huggingface dataset:
[Essential Phone ROMs, Kernels, Recoveries, & Other] ali.sbi:
Wanna flash this rom and now i'm running RR 7.1.2. can i flash directly or i need to flash stock ph-1 pie rom and after that i'm good to go for this rom?tnx
[Essential Phone ROMs, Kernels, Recoveries, & Other] RawSlugs:
Does aosip have built in kernel support for wireguard?
[Essential Phone ROMs, Kernels, Recoveries, & Other] aamadorj:
AFAIK, one way to proceed is to clean flash AOSiP 9.0 on your PH-1, following the "FAQ and Install instructions" at the OP, and also install the latest Essential firmware (no vendor version) from this other thread.
[Essential Phone ROMs, Kernels, Recoveries, & Other] tqwzUX6fn39GZMEzSnDF:
I'm on 25/03, no Gapps, rooted with magisk. What is the recommended update procedure?

Somewhere I've read to do it via TWRP. Could someone please write / add s.th. to a step-by-step guide?

- Download OTA update

- Reboot to TWRP

- Flash AOSiP

(reboot or not?)

- Flash Magisk

- reboot to system

???

Did I miss any switch of A/B partition? Or do I have to flash TWRP again aimilar as mentioned in OP for installation?
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
Flash rom in twrp. Flash twrp installer zip in the same session before rebooting.

Reboot to recovery, not system.

Once rebooted, flash Magisk. (This is also when you would need to flash gapps, but you said you aren't using those.)

Reboot to system.
[Essential Phone ROMs, Kernels, Recoveries, & Other] RawSlugs:
Dont need to "switch slots" in twrp before rebooting?
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
That's what rebooting back to recovery in the middle does. If you're on slot A, the installer installs the ROM to boot_b and system_b. Rebooting to recovery just tells TWRP to work with the B slots for the next flashes

---------- Post added at 12:00 PM ---------- Previous post was at 11:58 AM ----------

I don't know if using the Switch Slot option will accomplish the same thing, as I can't remember if twrp allows you to WRITE to the other slot without the reboot.
[Essential Phone ROMs, Kernels, Recoveries, & Other] RawSlugs:
I have been always manually switching slots before the reboot, didn't know it does it automatically
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
No need to.
[Essential Phone ROMs, Kernels, Recoveries, & Other] varxx:
This has been one of my two favorite custom ROMs for my PH-1. With the latest build (20190401), though, I've been getting some wifi weirdness -- disconnects and poor reception. Is anyone else seeing this?
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
The only weirdness I've seen with WiFi is that I have a Tasker profile to enable/disable based on location. I also have a task that disables that profile entirely and shuts WiFi off (for when my router is being updated or Time Warner/Spectrum has their head up their ass with my service).

Tried that earlier today and it showed as locked in the OFF setting, but it kept reconnecting. I have it set to NOT automatically re-enable WiFi in the Android settings. So, I couldn't shut mine off for a little bit earlier. Sounds like the opposite of your issue :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] xarekusu:
I flashed the latest firmware AOSiP then flash TWRP. When I reboot in TWRP touch was not working. I used an USBc to USB mouse to install Gapps and Magisk. When I rebooted to android the touch was still not working.

I read through the thread and I see that people are flashing NOVENDORS firmware. But if I flash NOVENDORS firmware it will be back to stock no? Unless its something I can flash in TWRP to fix the touch problem

can anyone tell what I need to install or flash to get touch working?

Thanks in advance
[Essential Phone ROMs, Kernels, Recoveries, & Other] tqwzUX6fn39GZMEzSnDF:
I had same problem, explanation from starcms solved it:

https://xdaforums.com/showpost.php?p=77597383&postcount=86

As you have a mouse, you could use it instead of ADB commands.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Ricx94:
I've been having an issue with this ROM where it won't let me pair to my gear S3 watch at the same time as any bluetooth speaker or headphones or my car. Anyone having a similar issue? Any suggestions to fix? I'm running April 1st build with gapps and magisk
[Essential Phone ROMs, Kernels, Recoveries, & Other] foueddyf:
Yes it does.
[Essential Phone ROMs, Kernels, Recoveries, & Other] internationalistic:
I have a problem that others may have experienced. I installed this ROM in January along with EdXposed. I dirty flash updated to a newer release (both 03/18 and 04/01) and afterwards my Xposed modules no longer showed up in Xposed Installer App (also the newer EdXposed Installer App). The module list is just blank, yet everything seems to be working still (XprivacyLua). Now the only problem is that I cannot deactivate a module, and when I try to download it again, the module stops working. I'm not sure if this is a ROM issue or an Xposed issue. It only happens when I try to dirty flash the update. Any suggestions or feedback is appreciated.
[Essential Phone ROMs, Kernels, Recoveries, & Other] ali.sbi:
i have problem here :

i'm running stock january frimware with no root or any thing and wanna flash aosip 9.0,when i flash twrp 323 i have working touch . and when i flash jan_twrp_root.img based on daze one toturial i lose my touch in twrp so i decided to start instructions for installing custom roms with twrp 3.2.3.0 because i have touch on it. after flashing rom i flashed twrp-installer.zip and after rebooting to recovery i did not have touch to flash gapps and when i change to the another slot after flashing twrp installer i have twrp working so did it and change the active slot with fastboot after that in twrp < reboot< change slot to the other i mean were the rom installed and doing gapps and magisk.zip rebooting to the system but i do not have touch in system and can not do nothing in lets go screen. testing the process with RR and Aosip rom and having the same results.

any suggestion?tnx in advanced
[Essential Phone ROMs, Kernels, Recoveries, & Other] internationalistic:
If you have working touch in TWRP, Install the AOSiP 9.0 zip and then touch "add more Zips" and put the twrp-installer-mata-3.2.3-0.zip in the flash que. Swipe to confirm flash.

(FYI: After that is finished you could go to the reboot menu in TWRP and it will show you what slot you were on. You don't need to worry about switching slots because that slot will automatically change when you Reboot back into TWRP.)

Reboot to System and let everything load. Then boot back into TWRP recovery, and install the Magisk-v18.1.zip (or current one). Reboot to System and open Magisk Manager. If Magisk is not installed, download updates and reboot your phone.

You should have root now. If you want gapps, boot back into TWRP and install the zip.
[Essential Phone ROMs, Kernels, Recoveries, & Other] ali.sbi:
following the instructions and no touch on rom to load anything. i even test it without twrp-installer. instaling rom and reboot to the system no touch.

another thing before all of this i was on RR 7.1.1 and flashing back to stock march frimware caused no touch so i decided to flash back to stock january one and i hve no problem with that. :(:(:(:(:(
[Essential Phone ROMs, Kernels, Recoveries, & Other] ali.sbi:
any body say anything please,without custom roms my ph-1 is useless:(
[Essential Phone ROMs, Kernels, Recoveries, & Other] xarekusu:
Anyone got google pay to work? I have April 1st build with magisk 18.1.

I hide in magisk google pay and google play services but still doesn’t work.
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
Have you tried repackaging the manager in its settings menu?
[Essential Phone ROMs, Kernels, Recoveries, & Other] xarekusu:
It says hide magisk manager failed when I try to repackage.
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
Well, THAT'S not good. Maybe hit the Magisk general discussion forum and search for a solution there. You need that to work for Pay
[Essential Phone ROMs, Kernels, Recoveries, & Other] killer86th:
Try other boot image, one of them actually help me to regain touch in TWRP

https://drive.google.com/drive/folders/161SEe74nYxXIBfg3OPlYEUz_D2IAguCf
[Essential Phone ROMs, Kernels, Recoveries, & Other] mymagicmyhero:
I would say this rom is a very nice try, but:

- No option to force apps to use cutout area;

- UI lags, especially in Settings app;

- Ambient display doesn't show live wallpapers and its too dimmed;

- Camera is worse than stock (except if you use Gcam port);

- Some missing UI sounds (screenshot for example);

-Lockscreen weather isn't working( at least for me);

-No preview in notification pane when screenshot has been taken( only blank space instead);

-Blank space for the oldest notification for an app of Wich you got multiple (for example Twitter);

First two are keeping me off for now.

Edit: I'm using latest official build.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mymagicmyhero:
Maybe you should try to install Pix3lify in magisk. It contains some pixel frameworks and might help if other things aren't...
[Essential Phone ROMs, Kernels, Recoveries, & Other] xarekusu:
I install magisk beta 19 and everything is working.

Thanks
[Essential Phone ROMs, Kernels, Recoveries, & Other] TomTheGeek3:
lockscreen weather works. usually you gotta get it to work in tandem with lawnchair or something. settings UI isn't laggy for me at all, neither with these notification problems.

the only thing that we share in common is the screenshot sound, yes it's missing.

other than that this is the best rom out there for the PH-1 right now. i'll be rocking this until Q comes out.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mymagicmyhero:
Hmm. I was stock before flashing this rom.

About that locksreen weather- Im using Nova Launcher, and its not working.

Jittering in settings I notice only when slowly scrolling slowly hrough the list (its more of a flickering).

How can I get the notch area to be used by games for example?
[Essential Phone ROMs, Kernels, Recoveries, & Other] TomTheGeek3:
oh, that flickering doesn't sound right. i came from stock as well (april update) but i wiped system / data / cache as usual and went to install the rom. no huge problems whatsoever.

the notch settings i believe there's a way to do it with a app. i'm sure someone will know what i'm talking about.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mymagicmyhero:
And this is what Im talking about the notifications. No preview for the screenshot and look twitter notifications-only the bottom one has twitter icon.

Also, Ambient display is too dim, I cant see it when I receive a notification when in daylight. Is it the same with you?

EDIT: Uploaded a second photo and you can see that the bottom tweet is like cutted... :eek:
[Essential Phone ROMs, Kernels, Recoveries, & Other] TomTheGeek3:
i only have the blank screenshot. no artifacting like that...
[Essential Phone ROMs, Kernels, Recoveries, & Other] purple.epod:
I'm having what seems to be an odd bug. When I plug in the USB audio dongle, my phone starts trying to charge the plugged in device. I am unable to disable this in USB behaviour. Is there any way to correct this? I've confirmed that this behaviour does *not* occur on stock, it's just AOSiP.
[Essential Phone ROMs, Kernels, Recoveries, & Other] pgoelz:
No touch in ROM

Guys, hope this isn't a tired old question.... I searched the thread and found references to this issue but no specific fix.

I have installed the latest AOSIP ROM as well as the TWRP installer. All was fine in TWRP and touch worked. I was originally on slot B, switched to slot A for the wipe and install, switched back to slot B and booted. AOSIP booted right up but at the lock screen, I have no touch. The buttons work and I can force a reboot or power off. I can also switch back to slot A and boot to TWRP (with working touch). But I have no touch in AOSIP.

Any suggestions how to get touch working? Is there a prerequisite stock ROM required? I tried it over PH1-Images-PPR1.180610.091 per a post in this thread..... should it be installed over the current April update? Does it matter?

TIA,

Paul

EDIT: I just realized my initial install (ie., before I tried it over PH1-Images-PPR1.180610.091) was on top of a stock ROM that was several revs old. I mistakenly thought it was current (this is not my everyday phone). I'll try again over the current April update and see what happens.

EDIT 2: That was the problem. Installed over the current April update resulted in a functional touchscreen. That said, I had issues with no touch in TWRP and the "workaround" steps in the TWRP installation guide were a bit vague. I hacked around and got TWRP touch working and the rest is history.
[Essential Phone ROMs, Kernels, Recoveries, & Other] RawSlugs:
So ive been on this rom a few weeks now, the general experience is good but i keep getting "system ui" reboots where the whole screen turns black and goes to lock screen (also pauses any audio that might be playing)

Last week this happened and i couldn't get it back so i forced a hard reboot and the phone was in a bootloop and had to reset - thanks for backups ;)

Android auto seems to be broken as well (dont really care about that)

Has anyone else had this experience?

________________________

AOSIP 20190409

Opengapps nano

Magisk 19

Busybox

Vanced

Wireguard

---------- Post added at 06:40 PM ---------- Previous post was at 06:36 PM ----------

I have the same thing with screenshots
[Essential Phone ROMs, Kernels, Recoveries, & Other] pgoelz:
What GAPPS?

I have AOSIP successfully installed on one of my two PH1s. The initial intent was to use AOSIP Google-free. That has been successful, and an interesting experiment. Much better battery life, for starters. However, I find that A) I kinda like AOSIP and B) there are a couple Google functions I cannot live without (like speech to text and location services). So.....

1. Can GAPPS be flashed after running AOSIP or must they be flashed at the same time as the OS?

2. What GAPPS are compatible with AOSIP on the PH1? I tried the "ARM64 / Android 9 / Micro" variant from the OpenGapps web site and got an "incompatible ROM" error in TWRP when I flashed them. I tried flashing the GAPPS immediately after flashing the OS as well as after first booting and running AOSIP. Why would that GAPPS variant be incompatible with AOSIP? AOSIP is Android 9 isn't it? And the PH1 uses ARM64?

Thanks,

Paul
[Essential Phone ROMs, Kernels, Recoveries, & Other] aamadorj:
To install GApps, the procedure to follow is described at the OP and other posts at this thread: 1) install ROM and TWRP from recovery (on the same session), 2) reboot to recovery and 3) install GApps (Android 9 and ARM64 variant, micro, mini or the flavor you like).

Booting ROM after 1), setting up and later installing GApps will cause different issues. I recommend you to stick with the official procedure.

The "incompatible ROM" issue you mentioned is caused by skipping step 2).
[Essential Phone ROMs, Kernels, Recoveries, & Other] pgoelz:
Ah, OK. That is (I think) the one thing I didn't do. I'm used to flashing the ROM and GAPPS together. I'll try it by booting back to recovery prior to flashing GAPPS.

Paul

---------- Post added at 03:39 PM ---------- Previous post was at 03:03 PM ----------

Sorry, I now have a more serious issue.

1. When I boot to bootloader, I get the standard Android bootloader. From there if I select start recovery, I get the regular Android recovery, not TWRP.

2. When I boot to the bootloader and send fastboot devices, I get the correct response.

3. When I send fastboot getvar current-slot, the reply is getvar:current-slot FAILED (command write failed (No error))

4. At least once, that current slot command returned the current slot (b in this case). However, if I then send fastboot --set-active=a, I get Error: device does not support slots.

5. When I attempt to return to stock by sending flashall.bat in the current stock fastboot file, I get target didn't report max-download-size

sending 'nvdef_a' (310 KB)...

What's wrong? Have I bricked the phone? Note that AOSIP continues to boot and run. I just can't get into TWRP, I can't change slots and I can't flash a stock ROM. I tried a factory reset from recovery, which worked. But all the above still applies.

Paul

EDIT: Never mind... for now. I rebooted the PC and tried again and this time the flashall.bat back to stock is working. Once I'm back to stock I'll try again. This may or may not be related but I notice that plugged into a PC USB port, AOSIP apparently wants to charge at more than the USB port can supply. This results in the phone going online and offline and back online as the USB port current limits. I'm wondering if this might be part of the issue. Between the time when it was failing and when it succeeded, I also charged the phone from 80% to 85%.... maybe that reduced the charge current to the point that the USB port could handle it. in any event, it is back to stock and I can try again.

---------- Post added at 04:25 PM ---------- Previous post was at 03:39 PM ----------

One final clarification.... following the steps:

boot twrp

wipe system/data/cache

flash rom

flash twrp installer

reboot recovery

flash gapps package and/or

flash latest magisk zip

reboot to system << Can I assume that involves switching to the other slot prior to booting? And after AOSIP boots, is booting to "recovery" supposed to boot straight into TWRP or will I still need to switch slots before booting?

In the mean time, I have successfully flashed back to stock. Color me relieved ;)

Paul
[Essential Phone ROMs, Kernels, Recoveries, & Other] RawSlugs:
When you reboot recovery, that automatically switches slots. So when you flash gapps and magisk you are already in the correct slot, so just reboot to system / boot up normally
[Essential Phone ROMs, Kernels, Recoveries, & Other] pgoelz:
I forgot you can boot straight to recovery from AOSIP. My bad. That might have worked.

Paul
[Essential Phone ROMs, Kernels, Recoveries, & Other] RawSlugs:
I meant reboot recovery while in twrp, booting to recovery while in aosip will not change slots
[Essential Phone ROMs, Kernels, Recoveries, & Other] internationalistic:
Almost Google Free AOSiP

I have been using AOSiP almost Google free. It has taken me some time setting it up, but everything is running smoothly. You don't need to install Gapps for the functionality that you need.

After flashing the rom, instead of flashing Gapps, install microG GmsCore.apk, GsfProxy.apk, and FakeStore.apk. In the microG settings you can configure UnifiedNlp Settings for location services. Here's a link to that:

https://github.com/microg/android_packages_apps_GmsCore/wiki/Installation

Now for speech to text, I have tried to to find a non-Google app that offers this but, there really isn't' one that integrates with all the other apps on the market. So I downloaded the Google App version 5.8.58.19 from ApkMiror. I chose that older version because the newer versions would force close immediately, and the version I chose was less than half the size. Here's a link: https://www.apkmirror.com/apk/googl...gle-app-5-8-58-19-arm64-android-apk-download/

The only functionality I get from the Google App is speech to text which I use with the open source anysoftkeyboard. I hid the icon in the app drawer for the Google App and I took the search bar off of my home screen , so I don't ever use it. I did this with Lawnchair. Here's the link: https://www.apkmirror.com/?post_type=app_release&searchtype=apk&s=lawnchair

I use F-Droid and Yalpstore to download apps and update etc.

As far as privacy goes, I use XprivacyLua, but that requires Xposed Framework.

This is a very brief description of my setup. If anyone is interested, and I have some time, I'll go into more detail. Hope this helps. :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] pgoelz:
Whoa, thanks for all that! Much of that mirrors what I did but your solution to speech to text is intriguing.... I'll have to give that a try. If I could get speech to text working, I had solutions for just about everything else. I missed the Google calendar app, though. Not having Google calendar would be a deal breaker. However, I found the web version was (mostly) acceptable. Dittto for the web versions of Google drive and photos, although the camera did not of course upload to Photos.

Paul
[Essential Phone ROMs, Kernels, Recoveries, & Other] RawSlugs:
And it happened again!

Was using my phone like normal, it got really slow and apps just started crashing, I rebooted and got into endless boot animation!

Is this happening to anyone else? Am I setting something up wrong? Why would this (apparently) randomly happen?
[Essential Phone ROMs, Kernels, Recoveries, & Other] knift:
This rom is the most stable one for me. Others sometimes got random system or ui reboot for me. If you reflash and it happened again, maybe something wrong with you phone. And maybe you should tye another rom or ask for warranty.
[Essential Phone ROMs, Kernels, Recoveries, & Other] darkknight200:
official 4/22 build install failing with twrp 3.2.3

So like any other official aosip update, I use the twrp method to install and not the updater.

The 4/22 build takes me to bootloader and won't boot up.

Here are the steps that i normally take to update each aosip weekly updates:

-download rom zip

-reboot to twrp

-flash 4/22 rom

-flash twrp 3.2.3 installer

-reboot to recovery, so switches slot

Then it reboots to bootloader only and when i select recovery its goes back to bootloader. Same if i select system.

Is anyone else having the same problem with the twrp method?
[Essential Phone ROMs, Kernels, Recoveries, & Other] RawSlugs:
What happens when you power down from the bootloader and power up again?

Can flash twrp img and install rom and twrp zip again (if you don't have touch just use adb
[Essential Phone ROMs, Kernels, Recoveries, & Other] darkknight200:
when i power down and power back up, it goes to bootloader/fastboot mode. yea i could do twrp img and twrp zip but that would be extra steps just to update aosip by twrp..

anyways i fastboot set active back to my previous slot and got twrp back and flashed older aosip 4/16 and back to working order again.

So the new aosip 4/22 beyond can't be installed by twrp flashing.

I have done this twrp updating method for all other aosip updates with no problems each time.

Todays 4/22 build is the first time i encounter problem like this
[Essential Phone ROMs, Kernels, Recoveries, & Other] pawelmiernik:
I'd like to add that 4/22 build can't be clean-flashed. After a clean flash from stock by getting twrp running, flash rom, flash twrp installer zip, reboot to recovery takes you back to bootloader. I've flashed a patched boot image with twrp and magisk, but that causes a boot loop with the AOSiP owl logo. A clean install of previous version works great with twrp and magisk installed, but when you update through the ota tool in settings you lose twrp recovery and magisk root. Switching slots gets you back into twrp, but flashing twrp installer zip breaks the 4/22 build and it boot loops into twrp. So if you want to keep twrp and root avoid the 4/22 update, it only successfully updates to a stock boot image and no root. Trying to get root back will break it. I really hope this gets fixed. Maybe for the time being remove the build until someone figures out what is going on with it.
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
There's a 04/23 build in the updater. Flash the prior version (04/09) without setting up the phone after, download the update, and look for it in /data/aosip-updater. You can then clean flash the 04/23 build.
[Essential Phone ROMs, Kernels, Recoveries, & Other] pawelmiernik:
Read this after setting everything up. The updater still only shows 4/22 and downloads the 4/22 official zip that's the same as on aosip.dev. At this point I'll wait until another update if any? And dirty flash that. This rom is awesome on the essential, the only things it lacks imo are quick unlock and an option to turn pin ripple off.