[Verizon] anyone having weird charging issues with these new JRO03L-4.1.1-r4 roms??

Thread Status:
Not open for further replies.

Last Updated:

  1. i've tried jbsourcery, aokp build 4, baked rom, and CNA 3.6.5, and my phone acts like it's charging even when it's not plugged in.

    the battery icon in status bar keeps flashing the little lightening bolt, and the screen wakes up randomly. also, since i activate the battery status on the lockscreen with each rom, it actually says "charging" on the lockscreen and keeps blinking

    :eek: :eek:

  2. trophynuts

    trophynuts Well-Known Member

    didn't see that on BB or Bamf
  3. mrichick

    mrichick Well-Known Member

    Yep, I'm having this same problem too. I thought switching roms would help and have full wiped my way to latest sorcery and cna but still the same issue.

    In addition to that, I'm experiencing weirdness when I plug in my phone to charge and it won't give me the charging indicator at all. Phone keeps draining, so I reboot and it's fine till next time. I'm gonna try a few more roms later tonight but idk if that's gonna help
  4. are those the same release? it seems to only happen on roms based on the new aokp 4, or "r4"

    i just tried, and it didn't happen on factory rom. i'm flashing the new liquid one right now (i'm a crack flasher lol). ill let you know.

  5. cool i was thinking my phone was messed up lol

    i noticed most kernels won't work with these releases either. trinity wouldn't stick at all (stays on default), and air kernel causes freezing.
  6. Caveman419

    Caveman419 Well-Known Member

    I did not have this issue on BAMF 2.3.5 (was having issue where phone would not charge, but that is a different issue).

    I flashed to the latest nightly of CM10 last night, no problem. Just flashed today's nightly (flash cracker too) and the phone keeps saying that it is charging when it is not. I plug it in and it still says charging (as it should) and when I unplug it, it shows dischraging for about 3-4 seconds and goes back to reading charging.
    I have put a different battery in the phone and now I am not having this issue. I have the "problem" battery in a time-out in the charger (was only at 67%). I will let it get fully charged and replace it to see if the issue is with that battery or not. THe "problem" battery was one that got from Sprint, the good one is one from Verizon (where my phone is through), but I know that is not the issue....just thought I would give to many details.
  7. mrichick

    mrichick Well-Known Member

    Are you going to focus on different kernels instead of a different rom? I'm kind of at a loss in troubleshooting this bc on top of this i have another wacky issue with the nighttime clock thing turning itself on constantly and interrupting phone calls, etc. It's sucking my battery fast, and then one of these charging issue rears its ugly head

  8. the new jb sourcery, aokp, CNA, and xenon are full of bugs. the topic of this thread is only one of them i've experienced. you can read more on them on xda developers and rootzwiki. pretty disappointing that these developers are for some reason releasing problem roms now...
  9. tdevaughn

    tdevaughn Well-Known Member Developer

    Would love to know what bugs you are referring to

  10. refer to the OP, as well as post #5.

    in addition, freezing and rebooting occured with jb beta 2.3.5 with the stock kernel. jb sourcery beta, like the other new ones, won't let you use any trinity kernels (the default sticks), and air kernel causes freezing.

    i always clean flash, btw.
  11. tdevaughn

    tdevaughn Well-Known Member Developer

    Never had any issues charging or not charging my phone. Sounds like a few are and would be hard to troubleshoot without being able to replicate

    The default kernel in 2.3.5 is trinity kernel.

    Having a kernel freeze maybe related to the kernel itself and not the Rom
  12. bjtcars

    bjtcars Well-Known Member

    I haven't seen that problem yet (hope I don't) and am running JB Sourcery 2.3.5 on my Gnex and Codename 3.6.5 on the Gnex 7 and have flashed different kernels on both.
  13. Steven58

    Steven58 Reformed PH VIP Member

    I've deleted some posts and edited some in order tone stuff down a bit. Please report beta issues correctly and also refrain from incivility. I don't mind keeping this thread open, but will close it if heats up again.

    We want a free exchange of ideas here, but site policy prohibits flaming. OP: Understand beta is just that. If folks are going to flash you take the risks. Not all phones are the same. I've never heard of your issue, so perhaps it could be the phone.

    Note to all: Please refrain from making sweeping generalities about developers, who work hard in a job that doesn't pay. (I can relate.. take this job at Android Forums.)

    Let's show each other respect going forward. :)


  14. yeah i've tried 5 different kernels lol (all clean flashed).

    i know the default is trinity, but any other trinity kernels i flash won't stick. it stays on default. maybe it's an intentional feature?
  15. tdevaughn

    tdevaughn Well-Known Member Developer

    Nope, I've flashed them all. Loaded just fine for me. I don't wipe anything on a kernel flash
  16. \

    did you flash another trinity, and check under settings "about phone" made sure it took?
  17. trophynuts

    trophynuts Well-Known Member

    have you tried LeanKernel? i've always had good luck with it. I'm running it on BAMF 2.3.5 now and no charging issues.

  18. yeah that one worked, but i found tiny kernel wokred better. have you tried that one? it's new on rootzwiki
  19. tdevaughn

    tdevaughn Well-Known Member Developer

    Just tried 2 of them, and they do change. also checked the trinity app and made sure the cpu/gpu changed and they did.
  20. tdevaughn

    tdevaughn Well-Known Member Developer

    You asked, I answered.
    Check your cpu/gpu settings after install. Betting the kernels are installing, if your only looking at the kernel info in the about phone, they are very similar and could easily be missed
  21. Right....
  22. tdevaughn

    tdevaughn Well-Known Member Developer

    oh well, tried. Good luck....
  23. Steven58

    Steven58 Reformed PH VIP Member

    I don't see the usefulness of this.. going forward. Additionally, rhyming cuss words is just as bad as using them against someone. I will be locking this thread and taking action privately.
    trophynuts and Rxpert83 like this.
Thread Status:
Not open for further replies.

Share This Page