• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

[Verizon] [ROM] AOKP JB-MR1 Milestone 2 [4.2.2] (07.21.13) TORO

Running the latest (B3 I believe).
Really love it. :)
Mods aren't quite on par with Sourcery but plenty for me. Really speedy but haven't gotten a better sense for battery life. Anyone running a different kernel other than the stock one it comes with?

I played with B3 for bit. It was fine but I left AOKP for Jelly Belly when AOKP was on hiatus and I have just come to enjoy the stock Android experience. I used to be all about the tweaks but I have moved past it I guess. Crazy, huh?

Try Lean Kernel 6. It's great on battery.:D
 
Upvote 0
have you checked out the timed hidden nav bar feature with the latest aokp roms? works really well and you can set the time out to 0 so it stays there until you tap somewhere and make it go away.


yeah i hid the nav bar when i was using the pie feature. had probs selecting apps near the edge of the screen, and typing letters that were near the edge. unless i'm missing something, that new pie feature sucks lol
 
Upvote 0
Was running build 3 and was having issues receiving and sending pic text. Anyone else having these issues?

One reason I switched back to JDX. One thing to keep in mind though. I had to download all of my apps from the play store instead of restoring from titanium backup to get a truly bug free experience for the first time since going from ice cream sandwich to jelly bean. Just a word of caution.
 
Upvote 0
One reason I switched back to JDX. One thing to keep in mind though. I had to download all of my apps from the play store instead of restoring from titanium backup to get a truly bug free experience for the first time since going from ice cream sandwich to jelly bean. Just a word of caution.

Yeah, I make a habit of having Google dowload my apps and using Titanium Backup to just restore data for selected apps.

However, for 4.2.1 it seems that 3rd party texting apps (or at the very least, Handcent) will not send or receive pic text. If I use the native messaging app, I'm ok - but not if I use Handcent. I read similar issues over on the XenonHD thread so I don't think is just AOKP or XenonHD - must be something with the texting apps. I'm just surprised that this isn't a more widely talked about issue - or if I'm in the vast minority.
 
Upvote 0
I have galaxy nexus 4.2.1, unlocked and rooted, I want to flash Minco v6 ROM to phone, but everytime I flash it says, "failed"? I have the zip in phone un-opened, I wiped dalvik cache and did factory reset, but the zip just won't flash? Should I extract the zip in phone? How do you install a ROM like this? I read up on it and follwed the directions I found, but have no luck.
 
Upvote 0
Damn! And I am just diggin on Sourcery! Maybe will give this a whirl before going to JBS5.0.

If I restore my nandroid form AOKP mr1 build3, does that simplify the flashing process for build4? Or do I have to do all the dalvik/cache/data wiping still? Maybe it makes restoring user apps and data ok even if a wipe is required? However, there will probably be problems with restoring system apps/data still?

Probably not a good idea to restore any data from a 4.2.2 rom, eh?

Edit: ok, I see that this build is 4.2.2-based. So maybe problems restoring data from a 4.2.1 build...
 
Upvote 0
Damn! And I am just diggin on Sourcery! Maybe will give this a whirl before going to JBS5.0.

If I restore my nandroid form AOKP mr1 build3, does that simplify the flashing process for build4? Or do I have to do all the dalvik/cache/data wiping still? Maybe it makes restoring user apps and data ok even if a wipe is required? However, there will probably be problems with restoring system apps/data still?

Probably not a good idea to restore any data from a 4.2.2 rom, eh?

Edit: ok, I see that this build is 4.2.2-based. So maybe problems restoring data from a 4.2.1 build...

I will be honest with you: this is my experience that I am sharing here, so take it for what you find of worth.

Team Kang recommends a complete wipe. Wipe system, cache, dalvik and full reset (all in recovery, of course).

I recommend the same and here's why:

I tried using Titanium Backup to restore my apps and data going from a 4.2.1 to 4.2.2 ROM recently. While mostly bug free, I started to experience a bug where my default chosen apps wouldn't keep. Meaning, if I chose Chrome as my default browser when clicking a link, it wouldn't stay as the default and I would have to chose it again, over and over.

I have had very few problems using Titanium Backup over the years but this one was real. So I did a complete wipe, flashed the ROM, downloaded all my apps individually and started fresh. No problems since. I don't like having to do that and hadn't had to do it that way in a long time but it gave me a fresh, bug free experience. I have since backed up all my apps using Titanium Backup, now that I am on a fresh install of 4.2.2.

Sometimes, even a tiny .x bump in version brings enough change to require a fresh start.

As far as a dirty install from a 4.2.1 to a 4.2.2 (wiping dalvik, cache and system only), I again recommend against this.

If you want to restore apps I would do so without data.

Hope this is helpful :)

jmar
 
  • Like
Reactions: dhworph
Upvote 0
hm... I'm on 4.2.2-based JBSourcery 4.5.6 right now... I wonder if restoring user and/or system data from it would cause problems... I do tend to think its best to just start over with each rom flash, and only restore apps, no data... there could be tiny little things that cause the weirdest bugs...

nothing better than a factory reset though... so fresh and so clean clean.
 
Upvote 0
hm... I'm on 4.2.2-based JBSourcery 4.5.6 right now... I wonder if restoring user and/or system data from it would cause problems... I do tend to think its best to just start over with each rom flash, and only restore apps, no data... there could be tiny little things that cause the weirdest bugs...

nothing better than a factory reset though... so fresh and so clean clean.

I wouldn't restore app data from one ROM to the next, ever. My rule. And I never ever restore system data, especially not from one ROM to the next. Clean flashing almost always means a great experience. Good luck my friend.

On a separate note I have decided that Jelly Belly is my phone ROM and AOKP is my tablet (N7) ROM. At least for now. I'm digging my phone experience being stock and predictable while having my tweaking fun on a device that I never need in an emergency. Enjoy the ROM folks!

Edit: I will continue to maintain this thread. Just speaking my thoughts out loud. If you have an N7, check out this thread for support: http://androidforums.com/showthread.php?p=5578343

jmar
 
  • Like
Reactions: dhworph
Upvote 0
I am on aokp build-5. It's running great with better power efficiency and speed compared to build-2. I am having one strange problem w/ dictation. If I click on the microphone icon I get a pop-up that says "Unfortunately Google Search has stopped". The pop-up quickly disappears, and after that I have issues bringing up the keyboard. Does anyone have a tip on how to resolve this issue? Before I flashed I did a clean reset including a wipe of the cashe and dalvic cashe. Thanks.
 
Upvote 0
I am on aokp build-5. It's running great with better power efficiency and speed compared to build-2. I am having one strange problem w/ dictation. If I click on the microphone icon I get a pop-up that says "Unfortunately Google Search has stopped". The pop-up quickly disappears, and after that I have issues bringing up the keyboard. Does anyone have a tip on how to resolve this issue? Before I flashed I did a clean reset including a wipe of the cashe and dalvic cashe. Thanks.
May I ask if you restored any data, up to and including that for Google Search? This could be the source of your issue...

Let us know.

jmar
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones