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

Status
Not open for further replies.
Search This thread

soupmagnet

Retired Forum Moderator
Jan 7, 2012
3,990
2,587
Austin, TX
Google Pixel 6
Yeah, I've been using Android devices since the Motorola CLIQ, and I can tell you from experience that benchmarks, while fun to run and compare, aren't very accurate. There are way too many variables, including different runs of the hardware manufacturing process. I has been discussed ad nauseum just about everywhere in the Android community. I've personally found that messing with CPU settings just to get higher scores can easily bork an install of a ROM, so I stopped a while back. Again, I go by usability and real-world speed over any benchmark score. And no one was trying to inflate egos or act superior. It's just kinda taken at fact these days


I appreciate your input but I think you are overlooking one important piece of information that I assumed was made clear from the beginning.

I realize that, because each device is different, benchmark scores cannot be compared between devices. But, when you take an average of a series of tests (say, 20 or so), replicating the same testing environment, with the same device, you can get a pretty decent baseline comparison to use against other roms tested on the same device with the same testing environment as it eliminates as many variables as possible.

Scores that are off by a couple hundred are no big deal and can be attributed to hardware issues....I get that. But when scores are off by a couple thousand, one could likely assume that it is no longer a hardware issue and should be looking elsewhere for the source of the problem.

That being said, had I known that my interest in such an anomaly would cause people to get so offended, I probably would have kept my original comments to myself. But I have very little patience for people who, knowing nothing about me, feel it necessary to address me as if I were some random 14 y/o who has very little working knowledge of a system.



There...I've said my peace and you'll hear nothing more from me.




Sent from my Kindle Fire using xda premium
 

chrisliphart

Senior Member
Apr 7, 2010
592
138
41
Atlanta, GA
I appreciate your input but I think you are overlooking one important piece of information that I assumed was made clear from the beginning.

I realize that, because each device is different, benchmark scores cannot be compared between devices. But, when you take an average of a series of tests (say, 20 or so), replicating the same testing environment, with the same device, you can get a pretty decent baseline comparison to use against other roms tested on the same device with the same testing environment as it eliminates as many variables as possible.

Scores that are off by a couple hundred are no big deal and can be attributed to hardware issues....I get that. But when scores are off by a couple thousand, one could likely assume that it is no longer a hardware issue and should be looking elsewhere for the source of the problem.

That being said, had I known that my interest in such an anomaly would cause people to get so offended, I probably would have kept my original comments to myself. But I have very little patience for people who, knowing nothing about me, feel it necessary to address me as if I were some random 14 y/o who has very little working knowledge of a system.



There...I've said my peace and you'll hear nothing more from me.




Sent from my Kindle Fire using xda premium

Oh, I hope you didn't think I was talking down to you, and yes, you can draw some comparisons on the same hardware unit from benchmarks. I was just saying that trying to push your device to the limit for the sake of a score can cause many more problems than it's worth. I've been through a lot of different Android devices, and thus a lot of different Android device forums, and I've found people are way to obsessed with comparing scores with other people. I've seen people pick apart scores and really screw up installs in pursuit of some other guy's score.

On a single device for your own comparisons, though, you're good. I get that. I'm sorry if I misunderstood you. :)
 
  • Like
Reactions: freefaling

bbc0

Senior Member
Nov 30, 2011
203
27
I've skimmed the posts, and I think that I may be the only one experiencing this..

I cannot leave apps on my sd card, or else I reboot to find them inaccessible. App manager gives me "couldn't find app," and I end up having to reinstall it. Am I the only one, or is this a "usual ics kindle fire" problem? Any suggestions? By the way, I followed your directions in the first post. Mostly everything else seems fine.

Also, the apps sizes change to 0.00bytes. Their names change to the long com.etc ones.

I can't say that I have ever heard of this problem before. Is it possible that the memory partition may have become corrupted? It is definitely not the usual ICS complaint.
bbc0
 
  • Like
Reactions: Twilla

BiteBlaze

Senior Member
Mar 18, 2012
1,176
956
Wisconsin
coldbloodedroms.com
OK. No more benchmark talk. If you have an issue, AS I HAVE STATED MANY TIMES BEFORE PLEASE EMAIL ME WITH YOUR PROBLEM! I'm not yelling at any of you. Please do not take this personally or post off topic again. It gets annoying after a long day when you come home and see a bunch of off topic posts. Please try to keep the off topic posts to a minimum. Thank you for those who emailed me instead of reporting in this thread. If you do report in this thread then please also send me an email so I can answer it faster and not have to look through 100+ posts to help you. Thank you for listening to my rant and that is all :D

~ BiteBlaze via SGH-T989
 

djkeller3

Senior Member
Jan 15, 2011
628
195
Lexington, KY
No battery issues here, unless you're comparing it to the stock ROM. Because it doesn't have hardware acceleration and optimizations, it will drain faster than stock. However, I'm getting far better battery life with this than I was getting with Energy ROM.

Were you on the 3/19 build? My battery improved a lot when I went from 3/6 to 3/19.

I'm trying to decide whether to flash this one or not. Not sure there's a compelling reason for me.

Sent from my Kindle Fire using XDA Premium

ROM: Energy CM9 Kang Build 3/19/2012
Kernel: 0xD34D
Overclock: 1.3 GHz Max, 800 MHz min. On Demand
Launcher: ADW EX
 

googlelover

Senior Member
Oct 19, 2010
100
23
Were you on the 3/19 build? My battery improved a lot when I went from 3/6 to 3/19.

I'm trying to decide whether to flash this one or not. Not sure there's a compelling reason for me.

Sent from my Kindle Fire using XDA Premium

ROM: Energy CM9 Kang Build 3/19/2012
Kernel: 0xD34D
Overclock: 1.3 GHz Max, 800 MHz min. On Demand
Launcher: ADW EX

My battery did the opposite when I went from 3/6 to 3/19. It was horrible... This rom has done much much better in the battery life department.
 

chrisliphart

Senior Member
Apr 7, 2010
592
138
41
Atlanta, GA
Were you on the 3/19 build? My battery improved a lot when I went from 3/6 to 3/19.

I'm trying to decide whether to flash this one or not. Not sure there's a compelling reason for me.

Sent from my Kindle Fire using XDA Premium

ROM: Energy CM9 Kang Build 3/19/2012
Kernel: 0xD34D
Overclock: 1.3 GHz Max, 800 MHz min. On Demand
Launcher: ADW EX

I was on 3/19. Never looked back from this ROM. :)
 

hanji1

Member
Apr 5, 2008
15
0
Hey guys how do I get this Rom up and running? It keeps freezing on startup.

Here's what I did..

I had CM7 flashed on it before and just followed the instructions exactly except the " backup the rom" part because I had already made a backup of it when I flashed the Cm7 on it.

Now after the installation on the this rom I rebooted my KF and it froze after I saw the ICS animation. Had to hard reboot it again and this time it said Android is updating 78 files and it just froze at the language screen. After another reboot it froze at the animation again. Rebooted again and it froze after "Android updating 4 files".What can I do? Is the installation corrupted or something? Should I restore my stock rom with TWRP?


[SOLVED] Nevermind I had to restart it like 5-6 times and it finally finished updating everything. Don't mind the noob in me. Thanks.
 
Last edited:

wildsoyabean

Member
Mar 9, 2012
27
5
Hey guys how do I get this Rom up and running? It keeps freezing on startup.

Here's what I did..

I had CM7 flashed on it before and just followed the instructions exactly except the " backup the rom" part because I had already made a backup of it when I flashed the Cm7 on it.

Now after the installation on the this rom I rebooted my KF and it froze after I saw the ICS animation. Had to hard reboot it again and this time it said Android is updating 78 files and it just froze at the language screen. After another reboot it froze at the animation again. Rebooted again and it froze after "Android updating 4 files".What can I do? Is the installation corrupted or something? Should I restore my stock rom with TWRP?

1) Did you wipe everything before flashing
2) Did you flash Gapps after flashing the rom?
3) Did you check the md5sums are correct for your downloaded files.?

Best solution: redownload all the files, wipe everything, flash the rom, flash the gapps. It should work

---------- Post added at 04:05 AM ---------- Previous post was at 04:04 AM ----------

So far so good on this rom. On first install it hangs while I was playing angry bird.

Tweak the settings a bit, set rom cpu to 300 min, 1000 max, conservative. Been running 2 full days now with no freeze and no SOD. Im pretty happy. I really think the CPU speed could be one of the root cause of the freeze
 
  • Like
Reactions: hanji1

CodenameDeadpool

Senior Member
Dec 8, 2011
441
39
1) Did you wipe everything before flashing
2) Did you flash Gapps after flashing the rom?
3) Did you check the md5sums are correct for your downloaded files.?

Best solution: redownload all the files, wipe everything, flash the rom, flash the gapps. It should work

---------- Post added at 04:05 AM ---------- Previous post was at 04:04 AM ----------

So far so good on this rom. On first install it hangs while I was playing angry bird.

Tweak the settings a bit, set rom cpu to 300 min, 1000 max, conservative. Been running 2 full days now with no freeze and no SOD. Im pretty happy. I really think the CPU speed could be one of the root cause of the freeze

I could never get my CPU to stay what I set it at and it kept freezing up. Had to go back to Jp/Hc/Nind/JDom's ROM.

Sent from my Amazon Kindle Fire using xda premium
 

hanji1

Member
Apr 5, 2008
15
0
I was really looking forward to your rom but after re downloading and re-flashing your rom last night again I am still having the same problem. This time I restored back to my Stock rom first and then I flashed ur rom. Unlike before when I flashed ur rom after Cm7. I am going to upload a video of part of the installation so you can see what's going on. It takes 5-6 hard reboots to get it properly installed. Even then it freezes. Oh and the KF won't mount as a SD card on a pc after installing ur rom. So the only solution I have is to revert back to stock since I can't transfer any files from the pc.

Rom Flashing Problems

No USB mounting
 
Last edited:
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 128
    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!
    22
    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.
    21
    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
    21
    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/
    12
    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
    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.