[ROM][flo|deb][UNOFFICIAL][LineageOS 18.1] -> 2020-12-11

followmsi

Senior Member
Oct 10, 2013
4,028
11,783
263
Pixel Experience .. let's test the CAF sources

One more build .. for flo only !
Switched completely to CAF (Code Aurora) sources .. basically Lineage-16.0 sources.

PixelExperience_flo-9.0-20190120-0939-UNOFFICIAL.zip

- Based on CAF sources now !
- Requires 1200MB system partition ! - Pls use "sysrepart_1280_120.zip" script.
- Including gapps and launchers and all the pixel stuff.
- No regular builds .. but happy to share the sources.

Still need to test the ROM myself ..

Enjoy :p

EDIT:
Bootloop .. need to check it.
Have removed the ROM from gdrive folder again.
 
Last edited:

dutchjeroen

New member
Jan 20, 2019
1
0
0
Just to prevent accidents:
I did the Clamor repartitioning on my Nexus Flo 16. It went well. (have installed Oreo with the mini Gapps package, before that was too big).
Can I flash the sysrepart_1280_120.zip after finishing the Clamor repartition? Or do I have to get back to the stock partition first?

thanks for all the work keeping flo alive!
 

prsa01

Senior Member
Jan 11, 2012
143
45
48
Minneapolis
Flo 16

Tried both without & with system wipe. Got bootloop with both.

Back to 01/18.

---------- Post added at 02:04 PM ---------- Previous post was at 01:58 PM ----------

The clamor repart gives you ~ 1.5 sys. The one in this thread is just a simpler repart that gets 1.2. So you are fine from a partitioning standpoint. As long as you have at least 1.2 sys partition size or greater. Make sure in twrp, adv wipe sys you see the larger size you expect (> 1.2).


Just to prevent accidents:
I did the Clamor repartitioning on my Nexus Flo 16. It went well. (have installed Oreo with the mini Gapps package, before that was too big).
Can I flash the sysrepart_1280_120.zip after finishing the Clamor repartition? Or do I have to get back to the stock partition first?

thanks for all the work keeping flo alive!
 
  • Like
Reactions: followmsi

jhford

Senior Member
Oct 28, 2005
444
60
48
Spontaneous reboots

I'm glad I pointed this out. The Oreo build of this ROM never did this. However, I have an Oreo nandroid backup. Will a nandroid restore overwrite the current partition layout back to default, or is there anything else I need to do to return to Oreo while waiting for a pie fix?
 
Last edited:

jhford

Senior Member
Oct 28, 2005
444
60
48
Does one just install this in twrp like a rom? Anything else you need to know to install?

Thanks
I tried to install the GPU with TWRP, but it failed.
@followmsi
I suggest dark mode splash screen or something else; this white one is too bright and hard on the eyes.
Also, my deb stopped rotating. Is that from the failed GPU install?
 
Last edited:

jhford

Senior Member
Oct 28, 2005
444
60
48
Of course. I forgot to say you have to flash the nexus 7 zip... Inside the downloaded zip...
I flashed the Nexus 7 zip. No difference. My deb continues to spontaneously reboot. Can I restore my Oreo nandroid backup while I patiently wait for @followmsi to figure this out? Or am I stuck because of the changed partition layout?
 
Last edited:

ReBat

Member
Jun 24, 2018
9
4
0
Guarda
I flashed the Nexus 7 zip. No difference. My deb continues to spontaneously reboot. Can I restore my Oreo nandroid backup while I patiently wait for @followmsi to figure this out? Or am I stuck because of the changed partition layout?
I restored my Oreo 8.1.0 nandroid backup and it works perfectly fine with the new partition layout.
 

jhford

Senior Member
Oct 28, 2005
444
60
48
I restored my Oreo 8.1.0 nandroid backup and it works perfectly fine with the new partition layout.
Thank you. Good to know.
EDIT #1. I restored my nandroid backup which went fine. One line, however, read, "flashing 3 partitions." What does that mean vis-a-vis the new partition layout? Now I have 2 debs running 8.1 and 9.0, respectively. I'll monitor the 9.0.
EDIT #2. I hate to bring this up now, because I noticed it a few days ago but quickly forgot. The Chrome and Chrome Beta apps also spontaneous close, like a FC, on both debs, 8.1.0 and 9.0. I uninstalled and reinstalled them. Should I do anything else?
 
Last edited:

drewski_1

Senior Member
Jul 20, 2012
3,828
1,602
113
SF Bay Area, CA
Thank you. Good to know.
EDIT #1. I restored my nandroid backup which went fine. One line, however, read, "flashing 3 partitions." What does that mean vis-a-vis the new partition layout? Now I have 2 debs running 8.1 and 9.0, respectively. I'll monitor the 9.0.
EDIT #2. I hate to bring this up now, because I noticed it a few days ago but quickly forgot. The Chrome and Chrome Beta apps also spontaneous close, like a FC, on both debs, 8.1.0 and 9.0. I uninstalled and reinstalled them. Should I do anything else?
you should just "ignore" the new partition layout once it's in place. they should just modify the sizes, but the use of them remains the same as prior.

i'm guessing what you're seeing is just referring to the restoration of 1) Boot 2) System & 3) Data partitions? that's what i typically back-up. haven't done it in a bit so can't recall the exact wording that comes up.



Sent from my dragon using XDA Labs
 
  • Like
Reactions: followmsi

followmsi

Senior Member
Oct 10, 2013
4,028
11,783
263
I flashed the Nexus 7 zip. No difference. My deb continues to spontaneously reboot. Can I restore my Oreo nandroid backup while I patiently wait for @followmsi to figure this out? Or am I stuck because of the changed partition layout?
Like mentioned above .. partition is one time task and should work on all ROMs !

Just continue flashing / backup / restore like normal .. and enjoy the bigger system partition.:)