1. Download the #1 Android News App:   EarlyBird - News for Android
    Dismiss Notice

[Verizon] [KERNEL][4.0.4] Franco M4 & Nightlies (6/5)

Last Updated:

  1. jbdan

    jbdan Well-Known Member

    So you were running with hotplug and dynamic hotplug enabled I see over @ xda. You should run one or the other next time you try this kernel if you do.

  2. zerocool79346

    zerocool79346 Well-Known Member

    Do not use the hot plug option in his app on francoTurtle.
    jbdan likes this.
  3. jbdan

    jbdan Well-Known Member

    16.2 hit the boards
  4. elmerjr128

    elmerjr128 Well-Known Member

    This is wrong. You can use the hotplug option in the app, but if so, dynamic hotplug should not be enabled. It's one or the other, basically.
    jbdan likes this.
  5. jackburnt

    jackburnt Well-Known Member

    Installed 16.2. I'll see how it goes over the weekend.

    EDIT: Also installed the touch recovery. Wow, what a difference. No more jumpy volume buttons.
  6. jbdan

    jbdan Well-Known Member

    16.2 is interesting for me. Love the new touch recov indeed!
  7. hurricane630

    hurricane630 Well-Known Member

    I'm on 16.1 how long should I wait to see accurate battery readings? Been on it only 2 days so I don't want to jump to any conclusions. But I have 5 min screen time. And off charger for hour and a half and down to 87%...

    Give it a few more days to get accurate battery scores?
  8. jbdan

    jbdan Well-Known Member

    On 4G? Did it start at 100% on your graph? I find often that the initial 10% drop over an hour is frequent on any kernel then it will level off and drain slowly if idle afterwards. ymwv though

    I think 2 full charge cycles is enough to see and judge what the battery life is going to be like on a new kernel flash. Your results and usage vary from other users so user-to-user experience will rarely if ever be the same.

    Try 16.2 if you wish that is what flashing is for :) Or my favorite 13.1
  9. zerocool79346

    zerocool79346 Well-Known Member

    Right. So unless you disable Dhotplug, (which is safe to assume he did not considering his issue) my post was valid.
  10. elmerjr128

    elmerjr128 Well-Known Member

    Flash Faux's reset kernel and then reflash Franco. I saw an improvement in battery life immediately after doing so.

    This is on 16.0, though, not 16.1. I've heard 16.1 isn't so good for battery life.
    jbdan likes this.
  11. jbdan

    jbdan Well-Known Member


    I've been meaning to repeat this as the reset kernel is almost a pre-requisite for kernel flashing for me. Thanks for pointing it out
  12. Trooper

    Trooper Well-Known Member

    Where is his reset kernel again? We need a sticky for this kinda stuff. Unless of course I missed it. Thanks.
  13. jbdan

    jbdan Well-Known Member

    I actually keep it on my sdcard always have it. You can get it in his OP at the rootz near the end of his OP. here
    Trooper likes this.
  14. hurricane630

    hurricane630 Well-Known Member

    Hey so I just flashed 13.1 What settings should I put on to get the best possible battery life? 700mhz-1200 mhz? what CPU governor? and what voltage? anything else I should adjust??
  15. jbdan

    jbdan Well-Known Member

    You're going to have to play with it and see whats best for you and your usage. I use conservative gov and 350-1200MHz with no hotplugging on 13.1. I leave voltage alone. You'll have to move the MHz slider to 350MHz as it comes at default 700-1200MHz. Then once at 350MHz check "set on boot". You can always go to the INFO tab in setCPU then tap "Time in State" after using it for a while to see where your CPU likes to hang out.
    hurricane630 likes this.
  16. gapi

    gapi VIP Member VIP Member

    I am doing this today with my screen timeout @ 10 minutes for testing.
  17. jackburnt

    jackburnt Well-Known Member

    Not digging 16.2 as much as Lean 1.8.0. Though, I'm not giving it a real fair chance since I'm keeping it charged fairly often.

    I'm heading out today and I'll see how it goes. Using Turtle at default.
  18. elmerjr128

    elmerjr128 Well-Known Member

    Set that sucker to 700/1000mhz and flip on the hotplug.
  19. jester6x

    jester6x Well-Known Member

    Has anyone tried these kernels with codeman 1.3.3? Also, anyone have a link to details on the hotplug so I can read up on what it actually does? Thanks
  20. elmerjr128

    elmerjr128 Well-Known Member

    Read through Franco's thread. It will answer any questions you may have.
  21. bsems1000

    bsems1000 Well-Known Member

    My opinion. I went from 13.1 to 16.1. Yes i havent been on in a while, 13 was very very good to me. ANyways..after forcingmyself to try and let the initiation period run its course..after 4-5 days on 16.1 I have to go back to 13. I noticed some serious lag (only when using tweetcaster) and also some lag when nav'n through the menus on the phone.

    I dont agree with having the min at 700 and max at 1000. In his response he said its like heating a house..its better to keep it at a good medium so that the processor doesnt have to jack itself up to meet the phones speed requirements when coming from 350 instead of 700. But imo, its NOT like heating a house. Its a processor. It doesnt have to be "warm" to function well. The phone being powered on is enough for it to keep "warm". I had no lagg problems and had great batty life with 13.1 ..so thats where im staying for the time being :)
    jbdan likes this.
  22. jbdan

    jbdan Well-Known Member

    17 up!
  23. sneakking

    sneakking Well-Known Member

    tried 16.2 on team black hat's stock 4.0.4 and wasn't getting great results

    reverted to 16 and have seen better times

    will be interesting to see what 17 offers
    jbdan likes this.
  24. elmerjr128

    elmerjr128 Well-Known Member

    Sticking with 16 for now. Let the guinea pigs do their thing :D
    jbdan likes this.
  25. jbdan

    jbdan Well-Known Member

    Initial reports on 17...proceed with caution....might want to hold off on 17 for now

Share This Page