yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Android Development] Sblood86:
I'm not finding any power issues with the rom or recovery.

Could have sworn I resolved the issue with the blank on bootup but I just confirmed that lol, will also blank it if you set it to default and reboot, will have to double check see what I broke lol. As for the pngs I redid those to, they are in the testing branch, forgot to merge them apparently lol.
[Kindle Fire Android Development] smirkis:
no worries, just wanted to put it out there. ive been super busy with work lately so I don't get to test stuff as much as id like to but I love the work you've put in!
[Kindle Fire Android Development] Sblood86:
Yeah you know it's funny; I have real mixed feelings opinions regarding this color bit. On the one hand it's a recovery partition; who really cares what color it is? On the other hand; if it's possible why not allow it?

This really started off as me just trying to see if I could figure out how to do it, now that it works there's very little reason not to have it.

PS.

Fixed ;)

Edit: We do need more than 4 colors...
[Kindle Fire Android Development] smirkis:
works great, and red works fine again as usual. i took some screen shots if you wanna snag them n host em in your thread? its up to you, but i posted em too so others can see what you've done.

bravo my friend.
[Kindle Fire Android Development] vbdss:
Its the power menu, on the rom itself. You can configure it under Cyanogenmod settings >> Tablet Settings >> and then the option to extend the power button menu, like adding back, home and menu.

And i tried to use lockscreen and cant enable too.

btw, which video file types support H/W accel ? i am trying to play a mkv and it changes to S/W, i am using MX Player
[Kindle Fire Android Development] Sblood86:
Either you didn't wipe something or you restored bad backups cause there is absolutely nothing wrong with the extended power menu or the lockscreen.

Pretty sure the codecs are kernel and app related.
[Kindle Fire Android Development] vbdss:
H/W is no problem now, i was using an file that was not using the H/W, but with another it worked

Ive wiped everything included formatted the system partition, i did a full wipe, didnt restore anything.
[Kindle Fire Android Development] Sblood86:
Glad to hear you figured the codec issue. I've flashed the 4/11 build several times trying to see if I can duplicate any issues with the extended power menu or lockscreen both of which as I said are working fine. The only reason you would still be having issues is if a file is either corrupt or being overwritten by a titanium restore or similar.

Best I can recommend would be to download the rom again and confirm the md5sum (if you didn't the first time) and reinstall (make sure you wipe everything again).
[Kindle Fire Android Development] chairshot215:
Flashed the. latest and no problems, also digging the new recovery. Still in my opinion the most stable can count on everything just working like it should Rom available for the Fire. Do you plan on a CM9 BUILD once we have a 100% working Kernel. Otherwise still my opinion that if you just need every thing to work and don't care about having the latest and greatest new thing then this is definitely the Rom to use.
[Kindle Fire Android Development] Sblood86:
I appreciate the kind words. As for CM9 as you are likely aware it's actually what I'm running because I don't really care if everything works lol. That's how I feel about my device though not a recommendation or whatever.

Currently we have several cm9 builds, some close to stock, some aokp and some extra themed builds. If I support cm9 it won't be until more of the bugs are worked out (I don't have the knowledge to help with the current bugs or I gladly would) after that it will really depend on how support plays out by other devs, if solid maintenance is done on a stockish cm9 than I probably won't see much need for my own tree, if not than yes I will likely merge together a tree like the one we have here for an easy build from which people can do whatever they want.

Edit: In the meantime IF I see anything I can assist with regarding the cm9 development I will open the appropriate pull requests but as I said currently I don't see me fixing the present issues lol

Edit 2: I'm glad people are liking the recovery but I would love it if people would open requests for added colors, preferably with rgb codes (I'm not entirely happy with the current shades of orange and green so any recommendations would be great).
[Kindle Fire Android Development] chairshot215:
Unfortunately I use my Kindle as Media Machine so has kind of purposely stayed away from CM9. Just because with the anticipation I think I will enjoy it more if everything is working when I first give it a test run. I just don't get those who seem to think the Kindle is worthless without ICS. Completely understand if one has no need for the things that are not working but more referring to friends or acquaintances that only use ICS so they can go around telling people they have installed ICS on their devices. On another note I do have a question or two actually,

First I was thinking to save precious SD-card space I could instead of doing a full backup just backup Data and in the case I want to restore just flash the Rom & Gapps and then Advanced Restore the data backup after flashing the Rom. Is this a good idea or could it end up just being problematic? I have little experience in doing any type of advanced restores.

Second was that over the past few months I have learned how to build from source and have gotten fairly good at modifying my device? Sometimes when board I just like to play around with things and am pretty happy with the performance of my device in comparison to others that Friends and family members are throwing me their Kindles and asking to make theirs look and run like mine does. Because of this I have been thinking of trying to take things up a notch and learn how to build my own version or variant if you will for others to try. The actual question is does anyone know of or could recommend any guides or really anything a beginner like myself could use to learn how to produce a working Rom? I’m thinking that maybe just learning how to put a theme together may be a good place to start. I have thought about just going the share a backup rt. as with the Kindle it pretty much gives the same result but feel like I would much rather learn how to produce a Rom as I find learning to do these things is actually more enjoyable then using the device itself, if that makes any sense.
[Kindle Fire Android Development] Sblood86:
You know I've honestly never tried it, make sure if you do still wipe the cache and dalvik cache just to have it rebuilt on boot rather than worrying about any loops that may happen later.

Well part of why I bought my kindle was for second device to try to learn more about the android platform from/with so far I think I've done exactly that so I'm satisfied with the purchase. Otherwise as for actual guides to custom roms or similar I'm not sure I ever found any. Best thing I did to learn anything was start following other peoples repos on github; read their changes and for every other random commit I read I learned (still do) a little bit more.
[Kindle Fire Android Development] raiderep:
Can you point me in the right direction to getting started with making my own changes to recovery images? I have some ideas and want to play too.

Doh! Just read your reply before my post....got in a hurry :eek:
[Kindle Fire Android Development] Sblood86:
I never liked extracting and manipulating boot and recovery images, same reason I don't like working on binary ports. Anything that requires me to decompress and/or throw into a hex editor just to try to change it is really not something I enjoy doing. If you want to make changes to recovery you should look at the source itself.

bootable_recovery is also the file path in the source tree. Sync the repo per directions in the OP than navigate to <repo root dir/where you synced everything>/bootable/recovery/ and you can make any changes you want in there. Than using the same instructions in the OP try compiling the recovery.
[Kindle Fire Android Development] raiderep:
Thanks, I have a laptop setup as a build machine and compiled one ics build for my nexus that actually worked but I am hoping it gets easier every time lol. This was what I was hoping you would say, the easy way isn't always the best ala extract and such. I prefer to learn the proper way but juggling school and life along with Android play is interesting to say the least!
[Kindle Fire Android Development] Sblood86:
If either of y'all come across something that you think the main tree here would benefit from with your playing around feel free to fork the corresponding repo and open a pull request (this goes for anyone else as well).

Now for the reason I felt the need to post... Moar recovery colors!!!
[Kindle Fire Android Development] spooky75:
No more updates? :-\
[Kindle Fire Android Development] Sblood86:
Been a little distracted with other things as of late and currently I don't have a working build environment up, I'll see if I can get something pulled together. In the meantime this is a source tree, you could follow the directions in the OP if you really wanted an updated build.

Build status:

Well looks like my installing the new LTS wasn't such a good idea, cm7 fails to compile on Ubuntu 12.04; per the google developer page 12.04 is still in experimental state and 'may' only work on the master branch... I'm going to look into the matter later on today if I can't hack it around the build environment I have a spare partition I can install 11.10 on.
[Kindle Fire Android Development] Sblood86:
New recovery release: this should resolve 3.0 boot image issues as well as enable script verification on boot (if people could test both and report back please).

As usual recovery is in post 2 instructions listed are for linux, checkout smirkit if you need further flashing assistance.
[Kindle Fire Android Development] smirkis:
damnit. so my windows7 partition took a dump so I've been trying to use my mac to run adb and fastboot commands and its been an annoying night lol.

so my mac automatically unzips every .zip file i download and as i rezip them they all fail during a flash attempt. so i had to copy the zips from my main kindle, to my mac, back to my new kindle to test flashing.

after all my fail, great news. the new recovery flashes cm9 3.0 kernels perfectly fine.

the only weird thing i was noticing is ui color changes don't work for some reason. it just flashes the screen and stays red every time. nice work sblood, I'm not sure whats up with uicolors but i wanna squeeze it into smirkit as soon as you find it ready! I'm sure users will be thrilled to have that "choice" again!
[Kindle Fire Android Development] Sblood86:
Yeah let me look at the colors tonight I forgot to test the switch cause mine booted in orange (still had the conf file on sdcard/).

Thanks for confirming the 3.0 kernel flashed, so I'm not crazy :D

I haven't checked the signature verification yet.

Edit: I just booted back into recovery and confirmed I flashed the version build 1.8 and color switch is working fine for me... Make sure you aren't using that pre-build I sent you eh Smirkis, if anyone else can confirm the color switch is either working/or not :D
[Kindle Fire Android Development] smirkis:
it did fail verification check, seems to be enabled by default? but it flashed fine after I disabled it.

try deleting ur conf file on ur sdcard, maybe the issue is creating it? I noticed it not working before actually. someone on the boards mentioned it wouldn't change colors after a fresh flash. so this was my chance to test a fresh fresh install. and color changes failed as he mentioned before. but, on my old kindle which already had it, seemed to change colors fine as u describe.
[Kindle Fire Android Development] webdroidmt:
Sblood, will it take advantage of the new FFF 1.4 and safely reboot to recovery from the OS? Thanks for releasing this.

Mike T
[Kindle Fire Android Development] smirkis:
yes, I already tried it. its bootloader and rom related. the recovery is just the partition that gets loaded.
[Kindle Fire Android Development] Sblood86:
To be entirely honest I did consider removing the bootmode tools from the recovery ramdisk but since I can't guarantee people update fff I kept them for now. This works the same as the old cwm for bootmodes.
[Kindle Fire Android Development] webdroidmt:
Thanks smirkis, just installed this over TWRP 2.1.1 and I had no prob changing colors. Rebooting works great, haven't flashed a 3.0 kernel rom yet but I'll take your word for it. :D

Mike T
[Kindle Fire Android Development] smirkis:
nice. lemme boot into recovery again and see if it works. not sure if it was the first boot or not.
[Kindle Fire Android Development] Sblood86:
I'll investigate the color switch after work.
[Kindle Fire Android Development] webdroidmt:
Just wanna' report everything I tried working well. Flashed a 3.0 kernel rom, did a backup/restore and tried all the colors but still stuck with Cyan. :cool:

Thanks again, Sblood

Mike T
[Kindle Fire Android Development] Sblood86:
That's how the signature verification is supposed to be yes, just for some reason it wasn't enabled by default before which really creeped me out lol. Sure a lot of the stuff that gets released isn't signed but you should still be the one allowing the recovery to flash it :D

Glad to hear. I also can't duplicate any issues with the color switch not working. Only thing I can think (and I might try this in a sec) is that if the clockworkmod folder doesn't exist the file creation might fail (I can fix that if that's the case), an obvious work around would also be to make a backup before changing the color (possibly why only some people are seeing the issue).

Edit:

-Just deleted the whole folder and yes that did seem to cause the aforementioned issue (I'll have a look at a fix here in a bit), thanks Smirkis.
[Kindle Fire Android Development] webdroidmt:
That makes sense, I still had my folder from your previous version, so CWM probably felt right at home. :D

Mike T
[Kindle Fire Android Development] Sblood86:
At any rate that's fixed now....
[Kindle Fire Android Development] Sblood86:
New rom build up with proper postmode changes, I didn't get a chance to actually flash it but I can't imagine why it would have any issues. Let me know if something doesn't work.

On a separate note I was playing with the recovery. If using fff1.4 or above it does work properly with rom manager. If you are using an older version of fff (such as fffe for dualboot) the bootmode tools are still included to reset the bootmode so you shouldn't have any issues with getting out of recovery (as always let me know if something fails).
[Kindle Fire Android Development] Sblood86:
There seems to be some issues with the format commands in the recovery, apparently I broke them somewhere with the retouch code and didn't notice. For the time being please do NOT use the new retouched recovery (if you are already using it I urge you to replace it for now)(I'm off work tomorrow so I should be able to fix this tonight assuming it's not too difficult)

Ok, so it seems that I didn't directly break the recovery so much as when I tried to make it rely on a native version of ext4_utils instead of the cm7 version it broke. At this point I have it working fine for flashing ics and the 3.0 kernels but the retouch changes actually make it so we can't directly install cm7 now. Being that the recovery in this thread is originally intended for use w/ cm7 I don't see a point in releasing the partially working version.

For now continue to use the older versions for flashing cm7 and alternate recovery for cm9. If there is a demand for the partially working recovery (the aforementioned one that only flashes cm9) I will release it but as I said at this moment I have no direct intention to.

As for actually fixing the recovery to allow for flashing cm7 and cm9 I am working on it but I seem to have hit a bit of a wall. If anyone familiar with C feels like lending a hand the recovery repo is linked in the OP (check the master branch for most recent development).
[Kindle Fire Android Development] mughalgxt:
Got this error when flashing from twrp 2.0, error in /tmp/sideload/package zip. hopefully you shall spare some time to correct this error. Thanks for cm7 ROM support.
[Kindle Fire Android Development] Sblood86:
Yeh I'm not sure the specific cause at this moment as I haven't had a chance to test it. Currently I'm working on cleaning up the build tree significantly (the way I have it currently isn't really all that nice) I was hoping to have a new release today but it seems somewhere along the way I broke something (I think I know what lol), should be an easy fix.

After that it's back to working on cwm for me lol.

Edit: I should note the new version (while several things are broken) does flash (in TWRP) so that shouldn't be an issue anymore.
[Kindle Fire Android Development] Sblood86:
New tree and build posted in the OP:

Device tree is much cleaner now and updated everything to Otter instead of Blaze. There does seem to be an issue with the zip itself not being signed (I haven't gone back and checked but I think this may have been the case for awhile, signature verification in twrp is disabled by default Oo and for awhile it was in our version of CWM as well).

In the process of cleaning things up there is a chance I may have broken more than what I realised last night so please do not hesitate to flash any errors you may encounter (it goes without saying that you should make a backup of your current rom before flashing the new build).
[Kindle Fire Android Development] mughalgxt:
ISSUES (apart from the flashing error fixed)

1. No scroll bars in browse (my university portal site) hence cant scroll up down left right

2. Tilt sensor(accelerometer) is broken!

3. Status bar time resets to GMT +0 after reboot

4. NO SOUND!!

5. Selecing recovery in reboot menu doesn't work.

............initial impressions!:( others to add...:p
[Kindle Fire Android Development] Sblood86:
Hahah wow, sorry man I didn't really get to test it much could have sworn the accelerometer was working when I flashed it last night... seems I broke more in the system prop than I initially thought... Instead of fiddling driving myself insane I'll revert it back to jackpots when I get off work (sadly that won't be til late tonight).

Selecting recovery in reboot menu does most certainly work; if you are using fff1.4, this has been the case with several builds back (and I know for a fact that that did work for me yesterday)

[LIST]
[*]May 14:
[LIST]
[*]Updates postmode for proper recovery selection and compatibility with FFF1.4a
[/LIST][/LIST]

If you are having issues reaching recovery than you are using an old version of FFF that does not use the correct postmode settings...

Edit: Thanks for the test as I said in the above post there could be some stuff broken (just apparently more than I thought lol)
[Kindle Fire Android Development] mughalgxt:
You haven't responded about NO sound issue! Am eagerly waiting for a stable release like the MAy 1. CM7 is in better state than CM9, which still is more Alpha (Charging issue, USb Transfer issue - mostly related to a singular driver). Please take some more time and release a evolved version up to the may 1 mark. The only good thing i found in this release was the volume and back button apps (referred to second post) survived reboot.
[Kindle Fire Android Development] Sblood86:
Sorry I thought I was clear in the fact that all the issues were related to the build prop changes (that included the audio), give this one a shot (I reverted my changes to the build prop so it should work the same as it did) (I've been busy this evening so all I could do was flash it, it boots; that is all I know with certainty).
[Kindle Fire Android Development] mughalgxt:
Except for the file name all else remains unadulterated. Same issues and shortcomings. Either the issues are beyond build.prop or you have a messy kitchen with build.prop from last release repacked.
[Kindle Fire Android Development] Sblood86:
Interesting, should have been a clean build so if build prop isn't it than something else is borking in relation to the blaze to otter changes (there weren't that many changes really lol) anyway, I'll have another look after work (this is turning out to be a little more obnoxious than I hoped; I knew there was a reason I didn't want to convert blaze to otter lol || ignore the rantings I'll figure it out later if I can I'm off work tomorrow so I should be able to put some time in tonight and tomorrow)
[Kindle Fire Android Development] Sblood86:
New build for a new month ;)

Tested and approved by mughalgxt
[Kindle Fire Android Development] portezbie:
No problems so far. Installed an ics theme as well without any problems.
[Kindle Fire Android Development] twa_priv:
Compiled my own build yesterday based on the new KFire-Android gb branches and installed it on my kids "gaming" KF. All works well as before.

Thanks Sblood86
[Kindle Fire Android Development] TahrirSquare:
Can anyone post some screen shots? also How is the battery life on this ROM guys?
[Kindle Fire Android Development] twa_priv:
This is what I got with a previous build from the same sources. Minimal use.
[Kindle Fire Android Development] TahrirSquare:
That's a looong battery life compared to CM9. hard to go back though.
[Kindle Fire Android Development] Sblood86:
Sorry didn't see this for some reason... I see little need to post screenshots for non-modified CM7 (there are no themes or UI changes; I'm considering adding back in my changes to enable 360 degree rotation by default and change the toggles around as the defaults don't even all work on the KF in the first place. I didn't merge them to the most recent manifest because I was trying to keep it as close to cm stock as possible but if there is a demand I will do it), in short; this looks exactly like CM7 :p
[Kindle Fire Android Development] portezbie:
I was using hellfire's cm7 rom previously but so far I have found this rom to be even more stable.

I have been getting very good battery life, I am now at 29% with over 24 hours on and heavy usage. If I am only web browsing, email etc it lasts forever, but I've been playing some pretty draining games and still I only have to charge it every 2-3 days.
[Kindle Fire Android Development] chairshot215:
I have been on CM9 for a bit but am about to go back as this is still the most stable and consistent thing going. Am however back with a few questions. Sorry but don't have my source in front of me so I hope I get everything correct. Posting now anyway because the answer could give me something to look foreword to after work. Basically if I remember correctly if I would like to include a few extra APK's in the build I could place them in a device tree directory like prebuilt and then enter them into the .mk? sorry think its Kindle or Otter.mk but not sure at the moment. Also I remember being able to add new lines to the build.prop here also but not sure how to edit an existing line. Basically what I am doing is trying to build using my own theme and want to build with the APK included and the theme set in the build.prop as the default.
[Kindle Fire Android Development] twa_priv:
You could do add something like this

PRODUCT_COPY_FILES += \

device/amazon/otter/prebuilt/app/xyz.apk:system/app/xyz.apk

to otter.mk for example.

And put your extra apks in prebuilt/app.