Tyrog07 said:

Is this ROM dead?

Slow charging and battery issues · Issue #2576 · PixelExperience/android-issues

Build date PixelExperience_phoenix-12.0-20220222-0107-OFFICIAL.zip Expected Behavior The Device should charge fast because it supports 27W. Current Behavior Battery taking huge time to get charge u...

github.com

@SreekanthPalakurthi said:

Slow charging and battery issues · Issue #2576 · PixelExperience/android-issues

Build date PixelExperience_phoenix-12.0-20220222-0107-OFFICIAL.zip Expected Behavior The Device should charge fast because it supports 27W. Current Behavior Battery taking huge time to get charge u...

github.com

Thanks man. Efforts are appreciated.

Tyrog07 said:

Status bar icons are messed up. Dosent show even two sim card icons and sometimes two icons colliding. Also on lock screen only battery icon is visible properly. For plus version.

There's nothing I can do about it, Google's sv2 status bar api isn't dual cut out notch friendly. Try using higher dpi from developer options.

@SreekanthPalakurthi said:

There's nothing I can do about it, Google's sv2 status bar api isn't dual cut out notch friendly. Try using higher dpi from developer options.

Tried but it still doesn't work on lock screen. This issue is with 12L codebase?
It was fine in previous non plus build I was using.

Tyrog07 said:

Tried but it still doesn't work on lock screen. This issue is with 12L codebase?
It was fine in previous non plus build I was using.

Yes, s2v or 12L introduced a newer api for statusbar padding

Sivakanthsharma said:

okay, a few questions

background: TWRP doesnt work for a12 roms. i've installed pixel experience recovery.

1. Do i need a clean flash to go from PE to PE plus
2. Can i download the rom, place it manually into the ota location and expect the recovery to install it? if yes, where does the OTA download to?
3. If no to above, what are my other options? right now, im unable to sideload any ROMs. i get "cannot read *filename*" error. i tried reinstalling adb drivers, to no avail.

Any help would be greatly appreciated

Click to expand...

That "cannot read filename" error is caused by the fact that path of file becomes too large in characters. So just trim down the name of file and try to place platform tools/adb tools at much higher (parent directory) as possible.
For ex: I placed my adb folder in c/adb and renamed the zip to short name ie. Update.zip. I hope this helps.

Tyrog07 said:

That "cannot read filename" error is caused by the fact that path of file becomes too large in characters. So just trim down the name of file and try to place platform tools/adb tools at much higher (parent directory) as possible.
For ex: I placed my adb folder in c/adb and renamed the zip to short name ie. Update.zip. I hope this helps.

Thanks dude! I did cut the file name. didnt know even the path name could affect this. it finally works.

The problems you have when you're only used to TWRP.

Sivakanthsharma said:

Thanks dude! I did cut the file name. didnt know even the path name could affect this. it finally works.

The problems you have when you're only used to TWRP.

Glad it worked.
Actually it's not related to only TWRP, it a global issue. Depends on each entity how much long characters they can process in filepath. It can be different in different cases.
Ex. (Hypothetical) let's say TWRP can process filename having characters length 50 but OrangeFox can process characters length upto 100.

langeyouxiang said:

I am very disappointed and very angry. Use the system update in the mobile phone to download this upgrade package, each time the download fails halfway, and then you have to start the download again. I finally downloaded it successfully once, and I have to download it again when I log out to delete the mobile phone password and come back. Can't you just stop and resume? ? ?

"We are really sorry for your inconvenience, we are always working on making our user experience better. Your feedback is welcomed." Or so would I say if this was some "paid customer service" but unfortunately it's not, it's just an open-source project which is free to use to build yourself. If this was a genuine "issue" I'd look into it but, You could have just downloaded the ota from your browser with a download manager. Generally, it should be fine but maybe at that time, our server had some issues. Learn to use work arounds if things aren't working as expected, that's how life is.

@SreekanthPalakurthi said:

"We are really sorry for your inconvenience, we are always working on making our user experience better. Your feedback is welcomed." Or so would I say if this was some "paid customer service" but unfortunately it's not, it's just an open-source project which is free to use to build yourself. If this was a genuine "issue" I'd look into it but, You could have just downloaded the ota from your browser with a download manager. Generally, it should be fine but maybe at that time, our server had some issues. Learn to use work arounds if things aren't working as expected, that's how life is.

I have downloaded the upgrade package in the computer browser and the update is complete. Thank you, still supporting you as always.

langeyouxiang said:

I have downloaded the upgrade package in the computer browser and the update is complete. Thank you, still supporting you as always.

Glad to know it worked out well in the end : )