Development [ROM][OFFICIAL] [OOS CAM] Pixel Extended ROM V5.9 Android 13.0 [Lemonade][21.07.2023]

[mattie_49]

Someone said this had bad battery is why they switched off Pe. Latest that is Not my experience in the least. Wowie super impressed and no settling just flashed earlier tonight. An hour on screen for every 10% battery. Yes please. Great work

 

[applyscience]

Someone said this had bad battery is why they switched off Pe. Latest that is Not my experience in the least. Wowie super impressed and no settling just flashed earlier tonight. An hour on screen for every 10% battery. Yes please. Great work

A13 is just packed full of new services and appss because google went to a compartmentalized management system for android. (and of courser, because of our human desire to always have MORE AND ALL AT THE SAME TIME)

Instead of just "baking in" new features, they make them services/apps that now has their revision management done with Google play.

That being said, I STILL bloat as much as possible with debater, autostart management or just disable/freezing.

i disable things i know have no impact being removed, like one-handed mode. but if its stable after, i sitll figure it cant hurt.

idk, honestly, when i hear someone complain about "bad battery" as a critique of a ROM and not the phone they own itself, i judge them for them n silence.

 

[jmadiaga]

It's truly a remarkable rom . First run off charger and everything set up. Every mode on oos cam works. 8k doesn't crash anything. Very very nice @ralf979 . I've found a new home and it's def not stock OnePlus software anymore.

which camera app are you using? TIA. cheers

 

[mattie_49]

which camera app are you using? TIA. cheers

Stock oos that it comes with. And literally every lens and camera mode work perfectly. 4 & 8k video!! Slo motion. I've used other aosp builds recently and these video modes put device in crashdump. Not on PE.

 

[applyscience]

Yes magisk 25.1 if I got to 26.1 it breaks vipers drivers. And use this after magisk is installed. And you have to force close dialer after side loading build a couple times for everything to kick up. This passes all cts and google lockouts because of root. https://github.com/Displax/safetynet-fix/releases

magisk 26 does come with a new way it treats boot, especially with magic mount and a reworked zygistt., so hopefully the moduals for safety net update and potentially resolve it

i am going to try and mess with disabling certain phone services and activities from the starting process to pinpoint it. I used thanox to block the app from booting with the OS (which means you are forced to run it to get calls after a boot, but i want screening so im doing that anyhow to then close it and open it for it to function) and it worked on first launch.

not the best solution but its a start, in the end, launching the phone app real quick at launch is nothing.

 

[AlmaGHWOR]

Works great but I got a few issues
Ear pice senor not working(screen not going off on calls)
From latest update notification volume seam's it's always on max
And the finger print unlock pop up window for apps it's a bit offset like lowered
Anyone else having this?

Totally agree with you. The sensor of proximity seems not to work never (tested on phone calls and Whatsapp audios). It's a bit annoying cause accidentaly calls with your face to someone your are listening to.
In addition, I noticed that the maximum volume of the notifications are a bit lower than in previous versions.
Is there any fixes for this yet?
P.S. the ROM is absolutely incredible and so customizable.

 

[mattie_49]

Totally agree with you. The sensor of proximity seems not to work never (tested on phone calls and Whatsapp audios). It's a bit annoying cause accidentaly calls with your face to someone your are listening to.
In addition, I noticed that the maximum volume of the notifications are a bit lower than in previous versions.
Is there any fixes for this yet?
P.S. the ROM is absolutely incredible and so customizable.

Mine works fine on Google dialer . Pull from ear it lights up. Back to ear goes dark. I flashed from F21 . Wonder if this makes a difference? All pixel dialer options working properly as well. And I just tested call when I read posts.

 

[pifubaro]

Hello! when formatting data, I get this message: error recovery open failed metadata no such file or directory
PE crashes after the first restart!

 

[mattie_49]

Hello! when formatting data, I get this message: error recovery open failed metadata no such file or directory
PE crashes after the first restart!

And you were on current stock firmware.? Fastboot flashed boot,dtbo,vendor_boot. Rebooted recovery,factory reset then side loaded PE 5.7? I've been on 3 days after installing this way, with zero issues anywhere. Even in apps. Booted right up restored google backup restored migrate apps and data. No hesitation in launcher . Just perfect. We all need to throw some donations ralf's way. It's a work of art.

 

[pifubaro]

And you were on current stock firmware.? Fastboot flashed boot,dtbo,vendor_boot. Rebooted recovery,factory reset then side loaded PE 5.7? I've been on 3 days after installing this way, with zero issues anywhere. Even in apps. Booted right up restored google backup restored migrate apps and data. No hesitation in launcher . Just perfect. We all need to throw some donations ralf's way. It's a work of art.

I can flash nameless and crdroid, PE can't, I have no idea why?

 

[mattie_49]

I can flash nameless and crdroid, PE can't, I have no idea why?View attachment 5896341

Try fastboot -w . You might get a successful wipe like this after sideload. Or fastboot erase cache,fastboot erase data.

 

[pifubaro]

Try fastboot -w . You might get a successful wipe like this after sideload. Or fastboot erase cache,fastboot erase data.

Thanks, it didn't work

 

[pawelmiernik]

Hello! when formatting data, I get this message: error recovery open failed metadata no such file or directory
PE crashes after the first restart!

It's tedious but download the firmware flasher utility. In bootloader make note of which slot is active, run the flasher utility (choose no to flashing modem) and when it's done go back to bootloader, switch slots and run the flasher utility again, when that's done go back to bootloader and flash PEX boot.img, vemdor_boot.img, dtbo.img go into recovery and flash PEX zip. Also name your images with a prefix for which rom you're using, I've had it happen where I had dtbo mixed up with another rom and kept scratching my head why things weren't working. Just prefix your images something like pex-dtbo.img and nameless-dtbo.img and so on if you're constantly switching between roms like me.

 

[shadabkiani]

I can flash nameless and crdroid, PE can't, I have no idea why?View attachment 5896341

Looks to me that data wipe was successful anyway. I'm on crDroid and I think I had some error too when factory resetting from recovery, data wipe was complete nevertheless. I proceeded with flashing and everything was good.

 

[pifubaro]

It's tedious but download the firmware flasher utility. In bootloader make note of which slot is active, run the flasher utility (choose no to flashing modem) and when it's done go back to bootloader, switch slots and run the flasher utility again, when that's done go back to bootloader and flash PEX boot.img, vemdor_boot.img, dtbo.img go into recovery and flash PEX zip. Also name your images with a prefix for which rom you're using, I've had it happen where I had dtbo mixed up with another rom and kept scratching my head why things weren't working. Just prefix your images something like pex-dtbo.img and nameless-dtbo.img and so on if you're constantly switching between roms like me.

How can I check the active slot in fastboot mode?
What command do I use to change slots?

 

[pawelmiernik]

How can I check the active slot in fastboot mode?
What command do I use to change slots?

Google is your friend, this is stuff you should familiarize yourself with before you attempt flashing custom software on your phone, I suggest you Google basic adb and fastboot commands or use --help command for both and go over the information they provide. Good luck!

 

[mattie_49]

Looks to me that data wipe was successful anyway. I'm on crDroid and I think I had some error too when factory resetting from recovery, data wipe was complete nevertheless. I proceeded with flashing and everything was good.

 

[mattie_49]

Stock kernel op9 na lemonade 5.7 PE. Battery profile in K-profiles. This is over 2 year old device and I charge to 100 every time and get down low before recharge. Still killing it.

 

[jmadiaga]

Stock oos that it comes with. And literally every lens and camera mode work perfectly. 4 & 8k video!! Slo motion. I've used other aosp builds recently and these video modes put device in crashdump. Not on PE.

i think bec PEX does not CPU throttle. i tested it with CPU Throttling Test

 

[mattie_49]

How can I check the active slot in fastboot mode?
What command do I use to change slots.?

How can I check the active slot in fastboot mode?
What command do I use to change slots?

fastboot --set-active=other
This no longer works on 9 series because of the jacked up super partition. 8 series is last that you could jump around with. Have stock on slot _a and custom on slot _b and wipe data and boot into whatever you wanted. Very handy