What is the best Rom out currently?

Yeah. Just make sure that if you use it, make a backup/nandroid before using it, just in case you don't like the results. There's no "undo" or "do over" option unless I missed it...

Also, when changing softkeys it appears to change wallpaper and stuff like that. Just FYI.
 
After last night's episode with the theme, I don't answer the phone anymore without making a backup. :)

Tonight I might try flashing Crossbreed V7 with Franco's R89 kernel, and trying out the same theme for V7. I couldn't care less about the fancy boot animation as long as it completes the boot process. I saw enough of it last night.
 
So the new AXI0M CROSSBREED SHO PATIENT ZERO is the one to get?

I have a question about the REVERT. Is that to revert the UI back to the previous, or to the stock UI?
 
So the new AXI0M CROSSBREED SHO PATIENT ZERO is the one to get?

I have a question about the REVERT. Is that to revert the UI back to the previous, or to the stock UI?

Yes, it's his best build--apparently.

UI revert takes it back to stock.

Be cautious with the newer franco nightlies. The popping after a call hangup is annoying as all hell. I installed M1 because I actually have to use my phone (as a phone) today, and I'd cringe every time the soundhack produces the pop.
 
  • Like
Reactions: stacman.nexus
Yes, it's his best build--apparently.

UI revert takes it back to stock.

Be cautious with the newer franco nightlies. The popping after a call hangup is annoying as all hell. I installed M1 because I actually have to use my phone (as a phone) today, and I'd cringe every time the soundhack produces the pop.

That's right the UI takes you back to stock aesthetics.

the Nightly patient zero build is experimental. If you want a more stable or daily driver type, you probably want the monolith builds.
 
  • Like
Reactions: stacman.nexus
That's right the UI takes you back to stock aesthetics.

the Nightly patient zero build is experimental. If you want a more stable or daily driver type, you probably want the monolith builds.

Oh the build itself is fantastic. My only issue is the kernel and the popping on phone calls.

He says so himself--the build is stable, but with bugs. I don't necessarily consider the kernel thing to be a bug of his though, since it's franco's thing, 'nah mean.
 
Oh the build itself is fantastic. My only issue is the kernel and the popping on phone calls.

He says so himself--the build is stable, but with bugs. I don't necessarily consider the kernel thing to be a bug of his though, since it's franco's thing, 'nah mean.

Word i flashed patient zero nightly but had to restore a backup this morning to get some info out of some texts.

Probably flash back later.

Havent noticed the call end popping but i hardly talk on the phone. :)
 
Word i flashed patient zero nightly but had to restore a backup this morning to get some info out of some texts.

Probably flash back later.

Havent noticed the call end popping but i hardly talk on the phone. :)

Yeah it's the newer kernels. Do a test drive, just dial a random number and hang up. I got it to happen on 96/97 and whatever came with ZERO, but not on M1, therefore M1 it is lol
 
Thanks both...

The changes are minimal in this build, but my backup from last night is working perfectly after all I did, so I may flash this one to see what it looks like, and hopefully I can get that theme to work on this build. I still have some soft keys in the taskbar to change yet. I am liking this monolith B1 (I should go to M1), but it wouldn't be fun if I stuck with the same one. As long as I can get to backup recovery, I'm golden.

I have noticed in Franco's app that it only has the option to flash the latest kernel. Is there not a way to go back to a previous build, and avoid the quirks like the popping? I like this R89 kernel and the configurations included.
 
Thanks both...

The changes are minimal in this build, but my backup from last night is working perfectly after all I did, so I may flash this one to see what it looks like, and hopefully I can get that theme to work on this build. I still have some soft keys in the taskbar to change yet. I am liking this monolith B1 (I should go to M1), but it wouldn't be fun if I stuck with the same one. As long as I can get to backup recovery, I'm golden.

I have noticed in Franco's app that it only has the option to flash the latest kernel. Is there not a way to go back to a previous build, and avoid the quirks like the popping? I like this R89 kernel and the configurations included.

Unfortunately, your options are only twofold: finding a zip of that kernel, or downloading as zip. I believe the app updated a few days ago to bring back that feature for the nightlies. Before, like a few days ago, you could only download either the nightly or the stable build, with the other being auto-flash only. I much prefer to download then flash myself.
 
Damn, my app took the update, and now I notice that it has the option to "download" the lastest or the latest stable kernel as a zip. Hopefully someone out there got to the 89 kernel. If I find it I'll let you know, if you're interested.

Another newbie question, but I'm finding that my aging brain isn't absorbing like a sponge anymore. When you format the system prepping for a new ROM flash in recovery, does it wipe the SD section, or do you have to actually tell it to wipe the SD?
 
Damn, my app took the update, and now I notice that it has the option to "download" the lastest or the latest stable kernel as a zip. Hopefully someone out there got to the 89 kernel. If I find it I'll let you know, if you're interested.

Another newbie question, but I'm finding that my aging brain isn't absorbing like a sponge anymore. When you format the system prepping for a new ROM flash in recovery, does it wipe the SD section, or do you have to actually tell it to wipe the SD?

Absolutely. IIRC, that didn't have the popping due to the older version of the soundhack.

It does not wipe the SD. Unless you format the SDcard (which would), lock/bring back to stock, unlock the bootloader, or wipe it yourself, the internal/"fake" SDcard will remain through thick and thin.

Of course, it's good practice to backup your SDcard. I do it weekly. Just a simple drag and drop on my Mac.
 
Thanks! I'm the king of backup, but I wouldn't want to backup everything each time I flash something if I'm going to format. I just backed up last night because I made another nandroid before trying that theme one more time.

One of these days I'm going to experiment more with restoration. I noticed in recovery mode that when you select "backup" it backs up everything in the nandroid folder. Otherwise, you also have selections to restore individual portions of the nandroid (i.e. data, apps, etc.), so I'm assuming that theoretically you could restore a ROM, and then choose another section of another ROM and restore that to the current build. Make sense? Just wondering. It's a slow day at the office. :D

I'm sure there are limitations involving mixing data from two separate builds, but it's just a thought. I haven't looked inside a ROM to see what's there.....yet.
 
Thanks! I'm the king of backup, but I wouldn't want to backup everything each time I flash something if I'm going to format. I just backed up last night because I made another nandroid before trying that theme one more time.

One of these days I'm going to experiment more with restoration. I noticed in recovery mode that when you select "backup" it backs up everything in the nandroid folder. Otherwise, you also have selections to restore individual portions of the nandroid (i.e. data, apps, etc.), so I'm assuming that theoretically you could restore a ROM, and then choose another section of another ROM and restore that to the current build. Make sense? Just wondering. It's a slow day at the office. :D

I'm sure there are limitations involving mixing data from two separate builds, but it's just a thought. I haven't looked inside a ROM to see what's there.....yet.

Presumably. But you hit the nail on the head--the data could conflict and you could have a Force Close party--a party no one wants to attend.

I've looked in roms before, but I believe they need to be "zipped" up in a special fashion in order for them to take. In an earlier build of Black Exodus I tried taking out his special font and failed epically.

If anyone has any thoughts on re-zipping, please, let them loose!
 
Presumably. But you hit the nail on the head--the data could conflict and you could have a Force Close party--a party no one wants to attend.

I've looked in roms before, but I believe they need to be "zipped" up in a special fashion in order for them to take. In an earlier build of Black Exodus I tried taking out his special font and failed epically.

If anyone has any thoughts on re-zipping, please, let them loose!

Zip with no compression and it will flash in CWM.

Sent from my Galaxy Nexus
 
I'm a little reluctant to move away from this Monolith B1 build. It's been up under average use all day (10 hours) and I still have 71% battery remaining. I guess I can always come back to it, but I always wonder if it'll ever be the same. :eek:
 
Hmmm! I downloaded the ROM from the OP and have flashed it twice now. Waiting for it to boot on the second round for 20 minutes now, but it's just hanging on the lock screen (Google/padlock).

I noticed in fastboot when the ROM was loaded that it said "opening update package". I never noticed that when flashing the previous ROMs. I wiped everything and formatted both times. Is this the correct zip? Should it say "opening update package"? It doesn't even start to boot, like there is no OS on it. Kind of what flashing an update would do if the base ROM wasn't there.

Oh yeah, and I'm sure I selected "install zip from SD Card" and not the update.

One more thing, when I flashed the ROM it only took maybe 30 seconds to complete.
 
Last edited: