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

Status
Not open for further replies.
Search This thread

pmdisawesome

Senior Member
Jan 23, 2012
273
70
I'm not BiteBlaze, but I can help you. I too am on the rom and I did flash the lastest kernel. All works great, except for full HW (Netflix doesn't work). Just make sure after you flash the kernel. Go rename this file using Root Explorer.

/system/etc/firmware/ti-connectivity/wl1271-nvs.bin.orig. and rename it to: wl1271-nvs.bin

If you don't rename that file. Wifi won't work. So please edit it. The screen issue is fixed in this kernel.

Sent from my HTC Vision using Tapatalk 2

That's weird, my Wifi works normally after flashing the new Kernel without having to rename that file, and I'm pretty the flash is successful since the "line" bug on the screen is gone!
 

walts

Senior Member
Apr 11, 2006
399
74
For some reason my Kindle Fire won't connect to the Wifi. It says saved but when I select the AP and select connect it doesn't work. Just stays on Saved. Trying to do the setup wizard but very difficult without an internet connection. Any suggestions?

I was experimenting along the lines of an earlier post that said when you drop one WIFI connection, you have to reboot before another one will pick up. I found the re-connect sluggish - it wouldn't "see" my AP, until I pressed the SCAN button on the top of the screen, then it found my AP and connected.

From my Sharp Zaurus days, I was familiar with wpa_supplicant.conf which we had to create by hand to get WIFI working on that device. These days it is generated automatically, but I had to look around anyway, and I noticed that the copy in /data/misc/wifi is missing two options:
Code:
ap_scan=1
fast_reauth=1
I didn't change mine since it seems to be working OK, but maybe a WIFI expert would comment on the situation. Why are those options not included, and should they be added?

After a few re-boots, my Kindle seems to be acting normally ????

Walt
 

bigguyone

Member
Mar 28, 2012
46
1
Baton Rouge
Had prob with WiFi at frist but works fine after off and on. Only prob is some app wont load, I-Tune, Flash but others did fine. Played with it just about all night and thats the only prob i had.
Will this ROM be able to let you watch tv. I think its an app from cable for like the
I Pad with 4.0?
 

shazbot

Senior Member
May 31, 2010
128
10
Washington
Is anyone else getting horrible download speeds from dev-host? I'm getting ~20KB/sec on my 30Mbit line. Anyone have a mirror? :/
 

djkeller3

Senior Member
Jan 15, 2011
628
195
Lexington, KY
Just flashed Hashcode's kernel #7, and screen is definitely back to normal so far as half-second flicker at screen-on is concerned. Never saw the banding since I never power off. :D

Wifi and hotspot working great so far.
 

smaghe

Senior Member
Sep 26, 2008
54
11
Paris
IMO work is far from finished. Look how CM9 is just running flawlessly on GS2.
Experience is just way better than stock, although CM9 is not even beta.
CM9 on KF still has several major issues : video decoding, random freezes, lags, wifi problems, power button, no USB host ...
IMO these things prevent oneself to run it as a true daily driver.
I'll donate as soon as a pretty "stable" version comes out.
It's also a way to prevent CM9 reloaded development from stopping or slowing, as AOKP is now a priority.

Didn't mean to be harsh at all. As I said before, I appreciate all the time and effort which has been put in this rom; I am also aware that developing a rom is a long hastle. I was just beeing critic about ppl saying "Oh my god everything is perfect" every 2,3 posts.
It's also hard to distinguish rom issues from kernel ones.

I just flashed 1.2h, as you said Biteblaze, things are getting definitely better.
Got rid of several annoying issues. Video decoding works flawlessly, and my smile is getting wider and wider.
As soon as usb mount and AC-charging will be fixed, I'll call it a daily :D
Thank you again for your work.

Cheers KFolks !
 

djkeller3

Senior Member
Jan 15, 2011
628
195
Lexington, KY
Didn't mean to be harsh at all. As I said before, I appreciate all the time and effort which has been put in this rom; I am also aware that developing a rom is a long hastle. I was just beeing critic about ppl saying "Oh my god everything is perfect" every 2,3 posts.
It's also hard to distinguish rom issues from kernel ones.

I just flashed 1.2h, as you said Biteblaze, things are getting definitely better.
Got rid of several annoying issues. Video decoding works flawlessly, and my smile is getting wider and wider.
As soon as usb mount and AC-charging will be fixed, I'll call it a daily :D
Thank you again for your work.

Cheers KFolks !

AC charging is fixed.

Sent from my Kindle Fire using XDA Premium
ROM: CM9 ReloadedROM v1.2H
Kernel: Hashcode 3.0.21(#7)
Overclock: 1.0 GHz Max, 1.0 GHz Min. Performance
Launcher: ADW EX
 

SalsaForte

Senior Member
Dec 11, 2010
288
24
Montreal
comobi.ca
When I plug my kindle for recharge with version 1.2h I don't see the recharge icon in the tray, but I see the kindle power light turn orange. It this only a cosmetic bug? Does the Kindle recharge anyway?

Very smooth rom.
 

xxxredeye

Member
Aug 6, 2009
5
0
Grand Rapids, MI
Google Chrome

+ Chrome beta app now works.

I have flashed this ROM multiple time as well as updated Chrome via the Play store but still cannot get it it work correctly.

It does update. I open it up go through the little setup process and wait for the page to load. Then nothing. The app is open, the address bar and tabs are at the top and the chrome bar is at the bottom, but no web pages will load. I hit refresh thinking it lost connection, and still nothing. I try to open an additional page, and its the same as before. I close Chrome, reboot, and try again, and still nothing.

Anyone else having this issue? I didn't see any posts like this, so please forgive me if I'm asking a question that's been answered previously.
 

jamminjon82

Senior Member
Mar 9, 2012
845
269
Gloucester
I have flashed this ROM multiple time as well as updated Chrome via the Play store but still cannot get it it work correctly.

It does update. I open it up go through the little setup process and wait for the page to load. Then nothing. The app is open, the address bar and tabs are at the top and the chrome bar is at the bottom, but no web pages will load. I hit refresh thinking it lost connection, and still nothing. I try to open an additional page, and its the same as before. I close Chrome, reboot, and try again, and still nothing.

Anyone else having this issue? I didn't see any posts like this, so please forgive me if I'm asking a question that's been answered previously.
Are you on 1.2 or 1.2H? Did you follow instructions in the op to the t?
 

nathris

Senior Member
Aug 18, 2010
63
28
Victoria
AOKP #33 + Hashcode #7, Netflix works
1.2H + Hashcode #7, Netflix opens but won't play video


Anyone know why? I'd just switch to AOKP but the touch driver is messed up on it.
 

WattB006

Senior Member
Sep 24, 2011
280
51
Nebraska
Every time I go to open Chrome it FC on me. I am running 1.2h with #7 of the 3.0 kernel. I just updated it through the play store. Any ideas?

Sent from my LG-P925 using xda premium
 
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.