|i'm dead| |please close| |discontinued|

Status
Not open for further replies.
Search This thread
By:
Advanced…
lovejoy777

lovejoy777

Inactive Recognized Developer
Dec 30, 2011
3,725
4,541
Nottingham
djkeller3 said:
Yes. No problems whatsoever; other than the charge indicator isn't working, but that has nothing to do with the battery getting charged.

Sent from my Kindle Fire using XDA Premium
ROM: CM9 ReloadedROM v1.2H
Kernel: Hashcode 3.0.21+
Overclock: 1.0 GHz Max, 1.0 GHz Min. Performance
Launcher: Apex
Click to expand...
Click to collapse

try this:)

sorry.lol link
http://db.tt/dQ537ewz
Sent from my Amazon Kindle Fire using xda premium
 
Last edited:
walts

walts

Senior Member
Apr 11, 2006
399
74
TahrirSquare said:
Mine is charging via AC wall charger fine, try it.
Click to expand...
Click to collapse

Actually I tried several chargers and cables - none worked. But the USB charge gave me a full battery overnight. Actually it went from 77% to 100% in about 3 hours, with the Kindle sleeping.

I'm really liking this ROM. I haven't tried to see what the WIFI bug is all about, since I seldom take the Kindle out of the house, but turning WIFI off and on again doesn't cause the connection to be lost. Battery drain at first look is much better than with 1.2, and it's nice to have things like Flash and YouTube working.

Walt

---------- Post added at 07:41 AM ---------- Previous post was at 07:29 AM ----------
paszczi said:
I was just wondering, what's your avarage battery life? I'm experiencing around 10% drop every hour (charged via AC adapter).

Sent from my Amazon Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse

Mine went from 100% to 94% in one hour, reading books and web pages, syncing blogs, tweets and e-mail over WIFI. That compares to a 12% - 15% drop with the same activities under 1.2. I'm very pleased :)

Walt
 
BiteBlaze

BiteBlaze

Senior Member
Mar 18, 2012
1,176
956
Wisconsin
coldbloodedroms.com
walts said:
Actually I tried several chargers and cables - none worked. But the USB charge gave me a full battery overnight. Actually it went from 77% to 100% in about 3 hours, with the Kindle sleeping.

I'm really liking this ROM. I haven't tried to see what the WIFI bug is all about, since I seldom take the Kindle out of the house, but turning WIFI off and on again doesn't cause the connection to be lost. Battery drain at first look is much better than with 1.2, and it's nice to have things like Flash and YouTube working.

Walt

---------- Post added at 07:41 AM ---------- Previous post was at 07:29 AM ----------



Mine went from 100% to 94% in one hour, reading books and web pages, syncing blogs, tweets and e-mail over WIFI. That compares to a 12% - 15% drop with the same activities under 1.2. I'm very pleased :)

Walt
Click to expand...
Click to collapse
I did a few tweaks to increase battery, as usual! So I'm glad people notice that.
 
  • Like
Reactions: djkeller3 and walts
P

pmdisawesome

Senior Member
Jan 23, 2012
273
70
walts said:
Actually I tried several chargers and cables - none worked. But the USB charge gave me a full battery overnight. Actually it went from 77% to 100% in about 3 hours, with the Kindle sleeping.

I'm really liking this ROM. I haven't tried to see what the WIFI bug is all about, since I seldom take the Kindle out of the house, but turning WIFI off and on again doesn't cause the connection to be lost. Battery drain at first look is much better than with 1.2, and it's nice to have things like Flash and YouTube working.

Walt

---------- Post added at 07:41 AM ---------- Previous post was at 07:29 AM ----------



Mine went from 100% to 94% in one hour, reading books and web pages, syncing blogs, tweets and e-mail over WIFI. That compares to a 12% - 15% drop with the same activities under 1.2. I'm very pleased :)

Walt
Click to expand...
Click to collapse

That's weird, my Kindle Fire can be charge via the wall AC outlet, I left it there, take a bath for 15 minutes and it went from 63% to 69%! It's not showing that it's charging in the Quick Settings upon the Notification, however if you go to Settings and then Battery it says your Kindle is charging! Nice!
 
BluesHawk

BluesHawk

Senior Member
Jan 26, 2012
147
33
nkd said:
I tthought I just bricked my kindle after flashing this rom. I flashed as instructed and now it is boot looping like crazy. I had the 1.2 on before, wiped cache, delvik, factory reset twice and flashed this and it bricked it.
I am able to get back in to recovery, I am gonna try to reflash this, but I am using clockwork to flash, because TWRP was not playing well with my kindle.

Update: Still boot looping, I guess I will just stick with 1.2 right now, I really dont have time to flash twrp, kindle seems to not play nice on my main computer when it comes to drivers, so I have to use fastboot method on my laptop which I currently don't have.
Click to expand...
Click to collapse
TWRP is needed to correctly flash the 3.0 kernel at this point. Smirkis' gscript thread is the easiest way to switch between TWRP and CWM. All you need to do is unzip the scripts folder to your sdcard and then run the "install twrp2.0" script and reboot :)

Great work on this ROM BiteBlaze. Very fast, very smooth, and very good battery life.
 
uoY_redruM

uoY_redruM

Senior Member
May 1, 2010
3,469
1,941
Longwood, FL
freefaling said:
I think it could be that your bootmode is set to recovery (TWRP has a bug) or your download is corrupted (did you confirm the MD5 of the downloaded file?).

Or you can try TWRP 2.1.0.
Click to expand...
Click to collapse

I was thinking the same about boot mode. My issue is, how can I change it if I don't have access to a computer? (Mine is down).

I checked and MD5 matches fine.

Sent from my Nexus One using xda premium
 
BiteBlaze

BiteBlaze

Senior Member
Mar 18, 2012
1,176
956
Wisconsin
coldbloodedroms.com
acax456 said:
Hey, what gorvenor is the best for battery life??

Sent from my LG-P500 using Tapatalk 2
Click to expand...
Click to collapse
Powersave = lowest MHz (best battery, horrible performance), ondemand = Highest MHz when touching screen, when not touching screen, lowest (best mix of battery + performance), performance = Highest MHz (best performance, crappy battery)
 
  • Like
Reactions: djkeller3 and acax456
BiteBlaze

BiteBlaze

Senior Member
Mar 18, 2012
1,176
956
Wisconsin
coldbloodedroms.com
I will post this somewhere in OP
Performance Governor:
This locks the phone's CPU at maximum frequency. While this may sound like an ugly idea, there is growing evidence to suggest that running a phone at its maximum frequency at all times will allow a faster race-to-idle. Race-to-idle is the process by which a phone completes a given task, such as syncing email, and returns the CPU to the extremely efficient low-power state. This still requires extensive testing, and a kernel that properly implements a given CPU's C-states (low power states). For more on this, the Samsung Galaxy Nexus GLaDOS kernel from developer Ezekeel has been a pioneer in this space.

Conservative Governor:
This biases the phone to prefer the lowest possible clockspeed as often as possible. In other words, a larger and more persistent load must be placed on the CPU before the conservative governor will be prompted to raise the CPU clockspeed. Depending on how the developer has implemented this governor, and the minimum clockspeed chosen by the user, the conservative governor can introduce choppy performance. On the other hand, it can be good for battery life.

The Conservative Governor is also frequently described as a "slow OnDemand," if that helps to give you a more complete picture of its functionality.

OnDemand Governor:
This governor has a hair trigger for boosting clockspeed to the maximum speed set by the user. If the CPU load placed by the user abates, the OnDemand governor will slowly step back down through the kernel's frequency steppings until it settles at the lowest possible frequency, or the user executes another task to demand a ramp.

OnDemand has excellent interface fluidity because of its high-frequency bias, but it can also have a relatively negative effect on battery life versus other governors. OnDemand is commonly chosen by smartphone manufacturers because it is well-tested, reliable, and virtually guarantees the smoothest possible performance for the phone. This is so because users are vastly more likely to ***** about performance than they are the few hours of extra battery life another governor could have granted them.

This final fact is important to know before you read about the Interactive governor: OnDemand scales its clockspeed in a work queue context. In other words, once the task that triggered the clockspeed ramp is finished, OnDemand will attempt to move the clockspeed back to minimum. If the user executes another task that triggers OnDemand's ramp, the clockspeed will bounce from minimum to maximum. This can happen especially frequently if the user is multi-tasking. This, too, has negative implications for battery life.

Userspace Governor:
This governor, exceptionally rare for the world of mobile devices, allows any program executed by the user to set the CPU's operating frequency. This governor is more common amongst servers or desktop PCs where an application (like a power profile app) needs privileges to set the CPU clockspeed.

Powersave Governor:
The opposite of the Performance governor, the Powersave governor locks the CPU frequency at the lowest frequency set by the user.

Interactive Governor:
Much like the OnDemand governor, the Interactive governor dynamically scales CPU clockspeed in response to the workload placed on the CPU by the user. This is where the similarities end. Interactive is significantly more responsive than OnDemand, because it's faster at scaling to maximum frequency.

Unlike OnDemand, which you'll recall scales clockspeed in the context of a work queue, Interactive scales the clockspeed over the course of a timer set arbitrarily by the kernel developer. In other words, if an application demands a ramp to maximum clockspeed (by placing 100% load on the CPU), a user can execute another task before the governor starts reducing CPU frequency. This can eliminate the frequency bouncing discussed in the OnDemand section. Because of this timer, Interactive is also better prepared to utilize intermediate clockspeeds that fall between the minimum and maximum CPU frequencies. This is another pro-battery life benefit of Interactive.

However, because Interactive is permitted to spend more time at maximum frequency than OnDemand (for device performance reasons), the battery-saving benefits discussed above are effectively negated. Long story short, Interactive offers better performance than OnDemand (some say the best performance of any governor) and negligibly different battery life.

Interactive also makes the assumption that a user turning the screen on will shortly be followed by the user interacting with some application on their device. Because of this, screen on triggers a ramp to maximum clockspeed, followed by the timer behavior described above.

By far, Interactive is the default governor of choice for today's smartphone and tablet manufacturers.

InteractiveX Governor:
Created by kernel developer "Imoseyon," the InteractiveX governor is based heavily on the Interactive governor, enhanced with tuned timer parameters to better balance battery vs. performance. The InteractiveX governor's defining feature, however, is that it locks the CPU frequency to the user's lowest defined speed when the screen is off.

Hotplug Governor:
The Hotplug governor performs very similarly to the OnDemand governor, with the added benefit of being more precise about how it steps down through the kernel's frequency table as the governor measures the user's CPU load. However, the Hotplug governor's defining feature is its ability to turn unused CPU cores off during periods of low CPU utilization. This is known as "hotplugging."

Obviously, this governor is only available on multi-core devices.
Click to expand...
Click to collapse
 
  • Like
Reactions: djkeller3, freefaling and acax456
walts

walts

Senior Member
Apr 11, 2006
399
74
pmdisawesome said:
That's weird, my Kindle Fire can be charge via the wall AC outlet, I left it there, take a bath for 15 minutes and it went from 63% to 69%! It's not showing that it's charging in the Quick Settings upon the Notification, however if you go to Settings and then Battery it says your Kindle is charging! Nice!
Click to expand...
Click to collapse

Yes, I just noticed that, too. Since the charge light never came on, and there was no "lightning bolt" on the battery icon, I assumed is wasn't charging - but it really is! The problem seems to be with the INDICATOR, not the actual charge mechanism, when using the AC adapter. On USB, it works normally.

Walt
 
BiteBlaze

BiteBlaze

Senior Member
Mar 18, 2012
1,176
956
Wisconsin
coldbloodedroms.com
walts said:
Yes, I just noticed that, too. Since the charge light never came on, and there was no "lightning bolt" on the battery icon, I assumed is wasn't charging - but it really is! The problem seems to be with the INDICATOR, not the actual charge mechanism, when using the AC adapter. On USB, it works normally.

Walt
Click to expand...
Click to collapse
The indicator is a kernel issue, or my mistake... either one I'll try to fix it
 
walts

walts

Senior Member
Apr 11, 2006
399
74
BiteBlaze said:
Like we have said, this is the kernel. It happens on my nightly AOKP Reloaded build too, and even on the Pure AOKP rom, Hashcode's test, and any other rom with kernel 3.0.
Click to expand...
Click to collapse

Unlike AOKP, the Back/Home/Stack icons at the bottom of teh screen work properly with this build. On AOKP, they shrink to minute size for any app that displays its menu icon on the bottom.

Just one more example of BitBlaze doing the job right! Thanks, BB :D

Walt

---------- Post added at 10:36 AM ---------- Previous post was at 10:35 AM ----------
BiteBlaze said:
The indicator is a kernel issue, or my mistake... either one I'll try to fix it
Click to expand...
Click to collapse

AOKP also has the charge indicator problem --- looks like a kernel issue!

Walt
 
A

Android16

Senior Member
Nov 30, 2011
88
12
My battery went from 100% to 50% overnight in idle state. I have it set to interactive so it should not use the CPU when idle so IDK why the battery is a lot worse on this.

If you can fix this and also somehow get the appstores to let us play games that are playable on the stock ROM(like modaco) along with the new things that do show up with this, this would be perfect.
 
Last edited:
Ramer

Ramer

Senior Member
Jun 20, 2010
4,292
6,246
Sunset
BiteBlaze said:
The indicator is a kernel issue, or my mistake... either one I'll try to fix it
Click to expand...
Click to collapse
I've got my wi-fi set to sleep except when charging. On mine, when plugged into a wall charger, the orange charge light will flash on and off every few seconds. No set interval, it's been anywhere from 3 seconds to 9 seconds when it flashes.
 
Status
Not open for further replies.

Similar threads

V
  • Locked
[Root][TWRP][FFF][CWM]Kindle Fire Utility v0.9.6 (5/09/12) [First Gen Only]
Replies
2K
Views
2M
Moscow Desire
Moscow Desire
Hashcode
[ROM/KERNEL] OFFICIAL CM11.0 + 3.0.72 Kernel for Kindle Fire [NIGHTLIES]
Replies
3K
Views
1M
M
mikeataol
twa_priv
[ROM] CM10/SGT7 for the Kindle Fire [20130117]
Replies
4K
Views
1M
sd_shadow
sd_shadow
twa_priv
[ROM] [JB 4.2.2] CM10.1/SGT7 for the Kindle Fire [20130724]
Replies
2K
Views
632K
t3chwizard
t3chwizard
whistlestop
CM7 for Kindle Fire (aka standing on the shoulders Giants)
Replies
1K
Views
507K
S
Stevethegreat

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 128
    BiteBlaze
    BiteBlaze
    20572262.jpg

    Thanks to poler166 for design

    I AM NOT RESPONSIBLE FOR ANY DAMAGE OR DATA LOSS! FLASH AT YOUR OWN RISK! NO KANGS OR MIRRORS PLEASE!


    Can't post in the development section yet? Give feedback here: http://xdaforums.com/showthread.php?t=1586146

    Features:
    Code: 
    [SIZE="4"]- ICS latest 4.0.4
- CM9
- OC to 1.2GHz (kernel 3.0 is very snappy even at that)
- APEX launcher and Trebuchet Launcher
- Lots of pre-installed apps (uninstallable)
- G-Apps included
- Themed with the standard ICS blue color in ALL apps and extras (smooth UI, will get smoother in the next milestone)
- File Manager
- Useless stuff removed (Camera, Voice recorder, voice actions, phone, facelock)
- ICS Direct port sounds
- Increased battery life (wifi supplicant scan = 150)
- Much more![/SIZE]

    Bugs:
    Code: 
    - All issues involving kernel 3.0 (v1.2H to latest versions)
- All issues involving kernel 2.6 (v1.2 to older versions)

more information [URL="http://xdaforums.com/showthread.php?p=24006456#post24006456"][U][B][COLOR="Red"][SIZE="3"]HERE[/SIZE][/COLOR][/B][/U][/URL]

    Instructions:
    1. Download newest CM9 Reloaded version
    2. Put on sdcard
    3. Boot into recovery (MUST BE TWRP)
    4. Backup current rom (optional)
    5. Wipe data (factory reset), wipe cache, wipe dalvik cache
    6. Flash CM9 Reloaded
    7. Wipe Cache and Dalvik
    8. Reboot
    9. On first boot, choose "Setup Wizard"
    (Follow these letter for letter, or it will probably not work!)

    DOWNLOAD:

    You can always find the latest EXPERIMENTAL and BETA builds in the following link: www.reloadedrom-selection.weebly.com

    v1.3:

    CM9 Reloaded for Kindle Fire - v1.3


    Out with the old!
    v1.2H
    v1.2
    v1.1
    v1.0.1

    Thanks to:
    NRGZ28 for letting me use a few broken .apk files
    CM team for the source (made this possible)
    intersectRaven for his wonderful kernel! (in v1.2 and under)
    Hashcode for the amazing kernel 3.0! (in v1.2H and above)
    poler166 for graphic designs in this thread (Graphic designer on Team Reloaded)

    Thank you so much guys :D!

    Screenshots in post #2
    Changelog and CPU Governor overview in #3
    Bugs explained & Coming soon #4

    Thanks for Reloading your KF!
    View
    22
    BiteBlaze
    BiteBlaze
    Changelog and CPU Governor Overview

    Changelog:



    Code: 
    v1.3 - Graphical updates, performance tweaks, new kernel version

    Code: 
    v1.2H - Kernel 3.0 (fixed hardware acceleration and many other issues like SOD)


v1.2
1. New Soft Keys (stock soft keys are now blue and reflective)
2. New Lockscreen color (has a blue glow)
3. Flashable Mods (for soft keys and other things)
4. Updated Apps
5. Integrated Google Apps (single flash rom!)
6. Better CPU app
7. Graphic Improvements
8. Bug Fixes
9. Modified build.prop
10. Few other minor things


v1.1
Bug Fixes
cpu change issue fixed
cpu app 
less launchers 
and many improvements(graphic wise and performance wise)


v1.0.1 - initial release of CM9 Reloaded KF build[/SIZE]

    CPU GOVERNOR OVERVIEW:
    Performance Governor:
    This locks the phone's CPU at maximum frequency. While this may sound like an ugly idea, there is growing evidence to suggest that running a phone at its maximum frequency at all times will allow a faster race-to-idle. Race-to-idle is the process by which a phone completes a given task, such as syncing email, and returns the CPU to the extremely efficient low-power state. This still requires extensive testing, and a kernel that properly implements a given CPU's C-states (low power states). For more on this, the Samsung Galaxy Nexus GLaDOS kernel from developer Ezekeel has been a pioneer in this space.

    Conservative Governor:
    This biases the phone to prefer the lowest possible clockspeed as often as possible. In other words, a larger and more persistent load must be placed on the CPU before the conservative governor will be prompted to raise the CPU clockspeed. Depending on how the developer has implemented this governor, and the minimum clockspeed chosen by the user, the conservative governor can introduce choppy performance. On the other hand, it can be good for battery life.

    The Conservative Governor is also frequently described as a "slow OnDemand," if that helps to give you a more complete picture of its functionality.

    OnDemand Governor:
    This governor has a hair trigger for boosting clockspeed to the maximum speed set by the user. If the CPU load placed by the user abates, the OnDemand governor will slowly step back down through the kernel's frequency steppings until it settles at the lowest possible frequency, or the user executes another task to demand a ramp.

    OnDemand has excellent interface fluidity because of its high-frequency bias, but it can also have a relatively negative effect on battery life versus other governors. OnDemand is commonly chosen by smartphone manufacturers because it is well-tested, reliable, and virtually guarantees the smoothest possible performance for the phone. This is so because users are vastly more likely to ***** about performance than they are the few hours of extra battery life another governor could have granted them.

    This final fact is important to know before you read about the Interactive governor: OnDemand scales its clockspeed in a work queue context. In other words, once the task that triggered the clockspeed ramp is finished, OnDemand will attempt to move the clockspeed back to minimum. If the user executes another task that triggers OnDemand's ramp, the clockspeed will bounce from minimum to maximum. This can happen especially frequently if the user is multi-tasking. This, too, has negative implications for battery life.

    Userspace Governor:
    This governor, exceptionally rare for the world of mobile devices, allows any program executed by the user to set the CPU's operating frequency. This governor is more common amongst servers or desktop PCs where an application (like a power profile app) needs privileges to set the CPU clockspeed.

    Powersave Governor:
    The opposite of the Performance governor, the Powersave governor locks the CPU frequency at the lowest frequency set by the user.

    Interactive Governor:
    Much like the OnDemand governor, the Interactive governor dynamically scales CPU clockspeed in response to the workload placed on the CPU by the user. This is where the similarities end. Interactive is significantly more responsive than OnDemand, because it's faster at scaling to maximum frequency.

    Unlike OnDemand, which you'll recall scales clockspeed in the context of a work queue, Interactive scales the clockspeed over the course of a timer set arbitrarily by the kernel developer. In other words, if an application demands a ramp to maximum clockspeed (by placing 100% load on the CPU), a user can execute another task before the governor starts reducing CPU frequency. This can eliminate the frequency bouncing discussed in the OnDemand section. Because of this timer, Interactive is also better prepared to utilize intermediate clockspeeds that fall between the minimum and maximum CPU frequencies. This is another pro-battery life benefit of Interactive.

    However, because Interactive is permitted to spend more time at maximum frequency than OnDemand (for device performance reasons), the battery-saving benefits discussed above are effectively negated. Long story short, Interactive offers better performance than OnDemand (some say the best performance of any governor) and negligibly different battery life.

    Interactive also makes the assumption that a user turning the screen on will shortly be followed by the user interacting with some application on their device. Because of this, screen on triggers a ramp to maximum clockspeed, followed by the timer behavior described above.

    By far, Interactive is the default governor of choice for today's smartphone and tablet manufacturers.

    InteractiveX Governor:
    Created by kernel developer "Imoseyon," the InteractiveX governor is based heavily on the Interactive governor, enhanced with tuned timer parameters to better balance battery vs. performance. The InteractiveX governor's defining feature, however, is that it locks the CPU frequency to the user's lowest defined speed when the screen is off.

    Hotplug Governor:
    The Hotplug governor performs very similarly to the OnDemand governor, with the added benefit of being more precise about how it steps down through the kernel's frequency table as the governor measures the user's CPU load. However, the Hotplug governor's defining feature is its ability to turn unused CPU cores off during periods of low CPU utilization. This is known as "hotplugging."

    Obviously, this governor is only available on multi-core devices.
    Click to expand...
    Click to collapse
    View
    21
    BiteBlaze
    BiteBlaze
    Screenshots

    Screenshots:

    (be warned... these are massive:eek:!)

    haha I'll need these provided.... I'll post in the thread when I need them. :) Real developers do it blind lol
    View
    21
    BiteBlaze
    BiteBlaze
    Bugs Explained and Coming Soon

    Bugs explained:

    Code: 
    [SIZE="3"]Kernel 3.0 (v1.2H) - Bugs:

- Only flash in TWRP
- Black screen for awhile on boot, wait it out
- Notification graphic glitch (my error, being fixed in v1.3 and v1.3H)
- Wifi - Works once; when you disconnect, you have to reboot to reconnect
- Sometimes weird bars appear on the screen (not too noticeable)
- Can't mount storage when not in TWRP

Kernel 2.6 (v1.2) - Bugs:

- Hardware Acceleration doesn't work (HD video, netflix, some games, quadrant standerd 3d benchmark, etc.) THIS IS A BIGGER DEAL THAN YOU WOULD THINK!! MANY FREEZES, SOD, AND NON-FUNCTIONALITY!![/SIZE]

    Coming Soon:

    Code: 
    v1.3 - Graphical fixes, bug fixes, and most likely an updated kernel. Since I no longer have the device, future builds may take 1 or 2 days longer to release as I have nothing to test the build on. Check the beta testing section on my website for beta builds/
    View
    12
    BiteBlaze
    BiteBlaze
    CodenameDeadpool said:
    What happened to these flashable soft key mods? I was really looking forward to these. Also, not a big fan of the blue reflective. Anyway you could post a build with the stock white home, back, and recent soft keys? Everything else is great on 1.2
    Click to expand...
    Click to collapse
    I am working on them, once they are done I will put them in the THEMES/APPS Section as well as the mods post in this thread. And, I have integrated kernel 3.0 in this rom and it works! I will soon distribute.
    View

New posts