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

[Verizon] [ROM]JDX (formerly Jelly Belly) AOSP+ - v15 (7/28)

I feel like battery life is another one of those really, really, REALLY subjective topics that will never give you an accurate reading no matter who you ask. It's all personal. No one is running the same stuff and no one can really compare because everyone's location is different as well.

I can speak on just my experience and say that the GNex, no matter what ROM you are on, has pretty weak battery life. I even have the extended battery and while there is a difference, it is slight. The reality is the fact that this phone has an enormous screen and it's just so taxing on the battery, it can't hold up to constantly being on all the time. If you watch Netflix, chances are your phone will be drained in an hour. If you are listening to music, it'll last a good bit longer if you don't turn your screen on.

I guess the moral of this story is the fact that you just cannot take anyone's word without a HUGE salt-lick because it is not going to be that accurate for your specific device. It just isn't.


I completely agree with this 99% - Only because I would add that apps also play a huge factor, as well as the differences in "hardware". Kernals are a good example of how the difference in hardware will be affected. I am glad that I have rooted, so that I can find the best setup for ME!! I KNOW that the 112 apps that I use on a regular basis are not the same as anyone elses, even my better half's phone does not have the same apps..... That said, I have used my own battery consumption comparisons with a huge salt intake, simply because I remember having terrible drain the first week I got my phone, completely stock, unrooted, etc, and not being able to get through a whole day, let alone overnight....it would drain at 5-8% per hour, with NO use.

However, I do like to see how other peoples phones are handling the combination of what ROM and Kernal, as I can get a slight picture of what a combination might provide given similar circumstances....Plus, it helps me remember what I was getting on a particular ROM too, LOL (crack-flasher here...)

It should help us all feel a little better, knowing that we are getting fantastic life on a particular ROM version, and a warning to some that you may get terrible loss on different version!!

Thank you very much for posting that....it is a good reminder for me, as well as to any lurkers checking in!!

(Welcome to the party - to those lurkers out there...we all know you are there!!!)
 
Haha. I noticed this as well and I actually kind of liked it. When it is actually happening, it resembles a baseball a bit. And I like baseball when the Braves aren't losing in extra innings to a guy named "Melky".

Grumble, grumble...


Ha ha, I thought the same thing. If only the Google was written in red letters, then it would really look like seams. I like the subtlety of the original animation though.

It works fine when waking the phone. It only happens on a call.
 
Haha. I noticed this as well and I actually kind of liked it. When it is actually happening, it resembles a baseball a bit. And I like baseball when the Braves aren't losing in extra innings to a guy named "Melky".

Grumble, grumble...

Unbelievable..... sigh.

GO BRAVES!
 
Other than the Play movies issue for some, most answers there will help too. Still working on that Play issue Patriot...trading some PMs this morning with the dev, but so far we keep coming back to the app...not sure still.

Again, really appreciate it. Its definitely a ROM issue. This morning I flashed winner00's CM10 port, and they work perfectly. Sorry to say, but I'll be leaving this ROM and using winner00's till AOKP drops
 
I don't know about you folks, but I'm very impressed with battery life on this 3.7 non-linaro kernel! The 3.6 stock linaro was sucking my battery down bad... this isn't that harsh.

Granted, I've burned 12% battery in 1-1/2 hours, but that's with my BT music streaming.

I am viciously abusive to my battery :D
 
I don't know about you folks, but I'm very impressed with battery life on this 3.7 non-linaro kernel! The 3.6 stock linaro was sucking my battery down bad... this isn't that harsh.

Granted, I've burned 12% battery in 1-1/2 hours, but that's with my BT music streaming.

I am viciously abusive to my battery :D

It's not conclusive for me yet, but so far, it seems better than the 3.x versions before. This time yesterday it I was having to recharge. I'm still around 50% and I have been using it alot...including a fresh flash of 3.7 using superwipe instead of manually cleaning. I also turned my wifi since I don't get a good signal and 4G is right overhead.
 
Quick update on some of the MMS issues over Wifi:

The reason that your MMS is not working is most likely because you are using Google Voice as default.
Only those of us that use Google voice are having the issue.
Jake is looking into it.


Edit: HOWEVER, let us know if you do not have Google voice as default, because the Dev will need to look at different items, but so far all we are finding is its related to GVoice.... Good Luck!

But just an update, mine was fixed in 3.6 with the WIFI fix we posted earlier with the advanced settings and the DNS address changes....and definitely fixed in 3.7. But I do NOT use Google voice as default for texting....
 
I didn't notice a change log. Is long press to kill an app, volume music controls, power widget notification included? I'm holding off for those
 
MMS over WiFi was working fine for me on 3.6 but it is no longer working for me on 3.7.



Edit: I just rebooted because I lost my signal and now I'm stuck at the Google logo, I've booted into recovery and tried wiping cache and dalvik but it did not help.

Edit: Trying to restore a backup and/or doing a factory reset still gets stuck at the Google logo....suggestions?
 
MMS over WiFi was working fine for me on 3.6 but it is no longer working for me on 3.7.



Edit: I just rebooted because I lost my signal and now I'm stuck at the Google logo, I've booted into recovery and tried wiping cache and dalvik but it did not help.


Reboot to recovery, wipe Dalvik and fix permissions. And then let it catch up on the X GLogo....

Interesting that each of us is having issues on the other build with MMS....

Let us know..
 
Quick update on some of the MMS issues over Wifi:

The reason that your MMS is not working is most likely because you are using Google Voice as default.
Only those of us that use Google voice are having the issue.
Jake is looking into it.


Edit: HOWEVER, let us know if you do not have Google voice as default, because the Dev will need to look at different items, but so far all we are finding is its related to GVoice.... Good Luck!

But just an update, mine was fixed in 3.6 with the WIFI fix we posted earlier with the advanced settings and the DNS address changes....and definitely fixed in 3.7. But I do NOT use Google voice as default for texting....

Not true, I have never used google voice. I have the problem. And now I have found out that I'm getting a reboot after connecting to a wifi network. Ugh. I want this to work so bad.
 
Reboot to recovery, wipe Dalvik and fix permissions. And then let it catch up on the X GLogo....

Interesting that each of us is having issues on the other build with MMS....

Let us know..

Yeah it seems like when some of you aren't having issues, I am. And when you are, I'm not. The first time it happened was when I was on 2.4 and 2.5 was out. 2.4 was way better for me than 2.5, 2.6, 2.7.
 
MMS over WiFi was working fine for me on 3.6 but it is no longer working for me on 3.7.



Edit: I just rebooted because I lost my signal and now I'm stuck at the Google logo, I've booted into recovery and tried wiping cache and dalvik but it did not help.

Edit: Trying to restore a backup and/or doing a factory reset still gets stuck at the Google logo....suggestions?

if this was me...and it was a couple of days ago....Here is what I did:

Boot into recovery, Factory Reset, wipe Dalvik
Install ROM
Install GAPPS
Fix permissions
reboot
Enter info, BUT UNCHECK restore from Google Play
Enter gmail address
go to Play Store, install Titanium Back Up (I have the proversion so the Key too)
Restore all Mising apps...select all apps that I want, as long as they are not system apps, like Gmail or anything
reboot to recovery
Wipe Dalvik
Install all mods
wipe dalvik
fix permissions
reboot

then set up the phone again the way I like it.

Caveat: Some people have borked their phone with these reboots, but I just had to remember to be patient at the google X....it can take up to 10 minutes to initialize the original boot after ROM and Gapps....If you battery pull during that time, its best to start all over at the beginning.

If however, you are still not able to get in....during the above process...BEFORE you install ROM and GAPPS, flash a superwipelite script....however, i understand that might not be possible if you are unable to get into your phone anyways to download it, although it you want to adb the file over in recovery, the script is in my dropbox link in the OP

Good luck, and PM if you need any other troubleshooting!!
 
I got things back up and running again but I'm not sure what caused the crash in the first place and that's what concerns me most. All I did was reboot the phone because I lost my cell signal and it was stuck at the google logo not the "x" logo.

I booted into recovery, factory reset, formatted system and dalvik, then installed my ROM and GAPPS, then fixed permissions, rebooted, logged in, booted back into recovery, installed a mod, wiped cache and dalvik, then rebooted and restored my apps with TiBu. I never let google restore my apps.


Edit: Rebooting takes a very long time now for some reason.
 
I got things back up and running again but I'm not sure what caused the crash in the first place and that's what concerns me most. All I did was reboot the phone because I lost my cell signal and it was stuck at the google logo not the "x" logo.

I booted into recovery, factory reset, formatted system and dalvik, then installed my ROM and GAPPS, then fixed permissions, rebooted, logged in, booted back into recovery, installed a mod, wiped cache and dalvik, then rebooted and restored my apps with TiBu. I never let google restore my apps.

How long did you wait it out on the Google logo? A ton of issues have cropped up on JB because of people pulling the battery while stuck on the Google logo. Not waiting long enough because it can take a long time.
 
Is wireless tether working for anyone on 3.7? I flashed it last night and can't get it to work on the native tether or other apps...
 
I got things back up and running again but I'm not sure what caused the crash in the first place and that's what concerns me most. All I did was reboot the phone because I lost my cell signal and it was stuck at the google logo not the "x" logo.

I booted into recovery, factory reset, formatted system and dalvik, then installed my ROM and GAPPS, then fixed permissions, rebooted, logged in, booted back into recovery, installed a mod, wiped cache and dalvik, then rebooted and restored my apps with TiBu. I never let google restore my apps.


Edit: Rebooting takes a very long time now for some reason.

"Note to self...Do not try to send MMS over Wifi!"

:D

Sorry you are having problems...that is strange. I'm just not even trying MMS again until it's confirmed to be working (I usually don't send many MMS anyway). I too use Google Voice but it is not my "default" messaging app.
 
Give it some time don't pull battery

Damn, you quoted me before I had a chance to edit...lol. It took about 3 minutes to boot up after just rebooting the phone. I wonder why it's suddenly taking so long. Earlier I waited about 15 minutes and it was just stuck.

Edit: Just to let people know I do not use google voice so my MMS issues are not related to it at all.
 
Damn, you quoted me before I had a chance to edit...lol. It took about 3 minutes to boot up after just rebooting the phone. I wonder why it's suddenly taking so long. Earlier I waited about 15 minutes and it was just stuck.

Don't know, but this has certainly been the MO for JB roms for a lot of us. It's random as heck, I experienced it on Jelly belly & VanirBean (in the beginning) several times and just waited 4-5 minutes at times.

I've run Jelly Belly since the beginning, but have dipped my toes into other JBwaters. It ups the ante on "buttery"! and wifi and MMS are :thumbup:
 
Nav lady's voice is not working on 3.7 for me (clean flashed and fixed permissions). She's been working fine on all previous builds (3.5, 3.2, 2.5, 2.4). The only thing she can say is "Head Northeast." she said that for every upcoming direction haha. I'm starting to get a little worried that new bugs are popping up when they weren't an issue before...
 
Back
Top Bottom