yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Android Development] Sblood86:
That's not entirely true, after the project was terminated they open sourced it all. Problem is if you ask me it looks like crap and I personally trust cwm more, it has been around longer and the source is much much cleaner. In short, given the choice I would rather maintain cwm than twrp (if for no other reason than I'm more familiar with its source).

Originally I had no intention of supporting twrp in the first place but at the time cwm still had issues with rebooting out of the advanced menu (twrp has incorrect reboot wrappers also, hence having to remove the reboot option to it in the first place) this is resolved in the included version of cwm.

If you choose to remain on twrp that is your choice, but I will not be supporting something that was deprecated by it's own devs.

Edit: I've been considering adding a reboot fastboot option to the rom reboot menu, thoughts?

Also, here is the TWRP source (complete after the project was deprecated agrabren re-released it) RecoverWin. If you guys really want support for TWRP what I would recommend is that someone fork that and fix the reboot wrappers so it doesn't require we treat it differently than CWM in the first place.

Convenience? I shouldn't have to remember to hold down my power button on reboot just to get into recovery; that's why we have those options for the power menu in the first place.

Updated post 2 with a link to Smirkis' gscripts isntallation method for recovery for those who would like to update but don't want to use fastboot.
[Kindle Fire Android Development] twa_priv:
Ok, point taken. I guess it's time to switch to CWM - even though TWRP worked just fine for me so far.

EDIT: Installed CWM on my two kf's and I must say it feels a lot more like home using it on two other devices. Sorry for the noise.
[Kindle Fire Android Development] Sblood86:
No worries at all (I know what you mean though about the 'feeling more like home' lol)
[Kindle Fire Android Development] DesDr0id:
Thanks for this build. One of the most stable cm7 builds to date. Nice to see that status bar FC has been fixed as well.
[Kindle Fire Android Development] johnwayne007:
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
4 errors
make: *** [out/target/common/obj/APPS/Phone_intermediates/classes-full-debug.jar] Error 41
make: *** Waiting for unfinished jobs....
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.

I tried to compile from your source, but i keep getting the above error. I have used the same virtual machine to compile ICS for my Inspire and gingerbread.

OS

Ubuntu 11.10

Working build environment for ICS/Gingerbread -> tested for HTC Inspire 4G

I'll repo sync my ICS build and compile to make sure that something didn't break. Love the builds though running them as my DD until ICS is complete, and has HWA.
[Kindle Fire Android Development] Sblood86:
Interesting... I haven't synced and compiled since (well the 2nd according to this lol), just synced, starting a compile right now. Will see what happens.

Edit: Yep, I see it. It's an issue with CM but let me research it a bit, might be able to resolve...

Edit 2: Looks like the Dutch Translations that were added (to the phone apk) 4 days ago are at fault. I don't read Dutch and rather than trying to fix this error I am currently forking and reverting the last commit from CM in a local repo, will add it to the manifest (I realise we don't use the phone but removing it can create some FC issues which I will not be doing at the build level, anyone wanting to remove the phone from their installed rom is more than welcome ;) )
[Kindle Fire Android Development] twa_priv:
Hey Sblood86,

I needed to sync android_frameworks_base to get the compile finish successful. That's was all I needed to do. Can't remember the exact errors but there were 4 phone related compile errors - which were caused by android_frameworks_base not beeing up-to-date.

I didn't need to backout anything on pks_apps_phone - and I compiled yesterday (after syncing everything).
[Kindle Fire Android Development] Sblood86:
Haha, that would make sense: they probably changed more than the translations I didn't read the entire commit to phone anyway; I was updating frameworks anyway while at it so I'll give it a test and we'll find out.

Edit: Yeah I just reread that other commit to the phone, I'm either blind or stupid (probably both; my fault for assuming... however on more than one occasion these translation updates have broken things lol).

Edit 2: Looks good, made it past that point at least, the manifest is updated; if this breaks I'll look into it some more but assuming it finishes I'll have a new build up in a little while.
[Kindle Fire Android Development] smirkis:
Just finished syncing without a hitch. Building as we speak, ill let u know how it goes.

I too love this rom, rock solid, hwa, everything just works!
[Kindle Fire Android Development] acax456:
one version for twrp pleaseeeeeeeeeeeeeee
[Kindle Fire Android Development] airmaxx23:
So will there be a new build released soon?
[Kindle Fire Android Development] twa_priv:
Sblood86 updated the OP with a link to his build from yesterday. So if smirkis just compiles using Sblood86 repos then the builds will be pretty much the same - unless he makes some customizations.
[Kindle Fire Android Development] smirkis:
Swap recoveries lol

Building takes hours, so Modding the source to remove the option and rebuilding for twrp is time consuming.

I like to modify my roms a pinch, ill post it soon I've just been playing around with the source a bit n keep rebuilding for tests. When I feel its solid with my small changes ill put it up
[Kindle Fire Android Development] worldwidepmp:
Cool. I would love give it a spin.
[Kindle Fire Android Development] twa_priv:
Just out of curiosity - what are you changing? Thx.
[Kindle Fire Android Development] smirkis:
not too much, it's already awesome as is lol. a few presets in the overlays to things I always set when I flash anyway, adding beatsmod, intersects oc kernel, ics theme and gapps preinstalled.

I'm trying to figure out how to enable cyanogenmodsettings/lockscreen/styleoptions/minimal ring style and change it to halo.

also, preconfig desktop arrangement, disable dock n extended dock.

those are the things I wanted to figure out before I share it. *shrug*
[Kindle Fire Android Development] dieandromeda:
i came from cm7 barebones. i feel the touch screen is less sensitive especially when selecting buttons at statusbar (back, menu, etc)... might be my imagination?. anyone experienced the same
[Kindle Fire Android Development] Sblood86:
Touch slop is kernel related (at least to my knowledge); as explained in post 2 I did not replace jackpots old kernel.

If you haven't already flashed a different kernel give it a try and see what happens.

Edit: barebones uses an older version of intersect ravens kernel.
[Kindle Fire Android Development] dieandromeda:
ic. at least i know it cause by kernel not the rom itself. btw i encounter statusbar force close once in a while while using golauncher.. other than that, all seem perfect..
[Kindle Fire Android Development] acax456:
Great rom.... keep updating dude
[Kindle Fire Android Development] miro101:
does this rom include some tweaks as v6supercharge or markete fixes? I do wonder since the google music app does not show up.
[Kindle Fire Android Development] airmaxx23:
I just installed this yesterday and it shows up for me, it's listed as Google Play Music.
[Kindle Fire Android Development] Sblood86:
There are some minor tweaks for the market: basically just pulled in some extra permissions to get some stuff to install that otherwise wouldn't list. No it does not include the v6supercharger (there are custom roms that do include it but the goal here is to try to provide a relatively pure/stable source tree from which other people can base their custom roms on).

You guys may have noticed my delay in binary builds; part of my goal in posting this source tree was in hopes that other people would find it useful for their customization purposes (Takenover and Smirkis are both good examples of people doing just that) because of that I haven't been maintaining binaries on an extremely consistent basis (the ones that I have posted are my test builds that I make when I update the source to confirm I didn't break anything)

I don't actually use CM7; mostly all I use my kindle for is browsing the internet, email and gtalk all of which work on CM9 ;) that also means that I have to flash it just to test the different issues reported (this is fine and I'm not complaining or anything; I'm simply explaining this so that everyone understands why stuff takes forever for me to test... like the test branch that I pushed 2 days ago and haven't done anything with since, very minor build prop changes, should not break anything but I need to test it before merging it and posting it... Hint hint, someone with more time feel like cloning my repo and checking out the new branch (only those who already know how of course)).
[Kindle Fire Android Development] DesDr0id:
Hi all

Although the status bar FC appears to be fixed (or rarely occurs) I still do see the issue regarding the full screen soft-button appearing when it should not and appearing inconsistently. See screenshot below (the soft button I'm referring to looks like two down arrows).

Another minor annoyance is the head phone icon remaining on at times when there are no head phones connected.

Thank you Dev(s) for all the work put into this rom!

View attachment 942616
[Kindle Fire Android Development] smirkis:
Are you playing music when you see it? If so that's how its setup.
[Kindle Fire Android Development] DesDr0id:
Hi,

No it varies sporadically. When it appears out of context, pressing the button has no effect.

I had reported these issues in Whistlestop's original thread a while back I believe, and others have confirmed experiencing both these issues (though they are at this point probably more of annoyances)

Thanks!
[Kindle Fire Android Development] Sblood86:
The soft button in question is the full screen hide button, that really sounds like a cm bug, I was fiddling with it previously and noticed there was some inconsistency (not really sure where to even start on that one, I'll look into it though)

The headphone icon is odd though, not something I've seen when I have ran it. Can anyone else confirm this?
[Kindle Fire Android Development] smirkis:
I don't get it randomly for what its worth. But it does show the headphone icon when I'm playing music with or without headphones. But I thought it was more of a music app icon.
[Kindle Fire Android Development] worldwidepmp:
Yeah it happened to me last night for the first time.
[Kindle Fire Android Development] DesDr0id:
For the head-phone icon issue:

If I had to take a guess as to what is happening, I would say the software isn't properly handling or receiving the "event" that the headphones have been removed. I'm pretty much able to replicate it in this way:

-Connect your headphones and notice the headphones icon.

-Let your device's screen go off for a bit. While your screen is off, remove the headphones.

-Hit the power button to turn on the screen and the headphone icon is still there

It also happens you plug them in and out pretty quickly.

(at least for me)

It was a bit irritating so all I did was go into settings and turned-off the headphone icon altogether.

---------- Post added at 10:29 PM ---------- Previous post was at 10:26 PM ----------

I remember the last time I had brought this up, someone responded that they had the same issue on another device as well -- so it may very well be a CM bug.
[Kindle Fire Android Development] Sblood86:
Seems others have been talking about this recently on Whistlestop's thread, does this explain/resolve the issue?
[Kindle Fire Android Development] DesDr0id:
Yep, I noticed those posts the other day and it certainly appears to be the same issue. What's described in that particular post though isn't a solution per say, but rather a work-around (ie just turn off the full-screen soft button and be forced to use the physical power button instead).

Similarly the work-around for the headphone issue is just to turn off the icon completely from settings.

Definitely bugs, but by no means show-stoppers :)
[Kindle Fire Android Development] acax456:
Can u add some tweaks n scripts to make it more comfortable???
[Kindle Fire Android Development] chairshot215:
question,

I have been using the below build.prop with these builds because just about every app shows up. Market or whatever they call it these days thinks my Kindle is a Galaxy Tab. The question is, with the new build.prop edits is the one I have been using now unnecessary and is there anything in the one I have been using that could potentially cause any issues? Not that I have had issues I would contribute to the file but still I would appreciate if anyone with a bit more knowledge then I has any useful feedback.

http://xdaforums.com/showthread.php?t=1424068
[Kindle Fire Android Development] Sblood86:
Small system prop tweaks like my recent changes I have no problem with as they are non-invasive and already present functionality. Scripts on the other hand I have no intention of adding at this time. The goal here is to keep a source tree not a custom rom, so the answer is likely no; on that note though, what sense does it make in asking for tweaks and scripts without making suggestions as to what tweaks or scripts you are asking for?

I've actually started pulling in some of those build.prop changes into the system.prop in device_amazon_blaze (my changes are a bit more conservative but should be an improvement over the old one).

The galaxy tab setting is (at least according to others) the cause of the netflix audio sync quality issues and therefor not something I will be setting. I have however included some extra device permissions which

should

improve the market capabilities but I haven't fully tested this. If you want to help out, run the included build.prop for awhile and see if you have any issues with specific apps (as stated in the changelog).
[Kindle Fire Android Development] chairshot215:
Can do, I think the reason I had continued using the build.prop was that a game would show up that I was playing at the time. One thing I noticed off the batt was that the Tablet version of Swiftkey shows with the included build.prop that had not using the modified one I had been using.

Edit,

I did a few tests with and without the Modified build.prop. I make it a point to purchase an app a week even if it is just a donation as adds get on my nerves but like supporting developers so will generally purchase paid versions of an app if it stays installed on one of my devices for any prolonged period of time or if it’s on sale and I think I may one day want the app. For example knowing I was receiving a Kindle for X-mas I purchased all the Gameloft games that had been on sale in December with my phone. So anyway I now have allot of apps in the not installed section from My Apps list from the Market so decided to just do an app count with and without the Galaxy Tab build.prop. What I found was a difference of 14 of 53 Apps had been missing from the list without the Galaxy Tab build.prop. Most had been games like all the Modern Combat games from what I could tell. I also double checked Netflix for Audio problems and was able to watch an episode of DS9 and Serenity without issues. With that said the below lines are also added to the build.prop and had kept the VM heap size at 64 and not 48 as had also been changed in the Galaxy Tab build.prop I posted above. I was wondering if this could be the reason I have not experienced sync issues with Netflix like other users have reported. Am very curious because Netflix is the only reason I have not used an ICS Rom and have been using the Galaxy Tab build.prop Since I first flashed over to CM7 on New Year’s Day. That and although I have a general idea of what these things do but not sure on the specifics. Another thing I checked on was that I was able to install Modern Combat 2 & 3 using the Galaxy Tab build.prop and they still play just fine now that I am no longer using it and am now using the one from my build. Sorry I tend to rant which would not be so bad if I wasn’t also too lazy to edit after noticing that I am doing so.

Sorry forgot,

net.tcp.buffersize.default=4096,87380,256960,4096,16384,256960

net.tcp.buffersize.wifi=4096,87380,256960,4096,16384,256960

net.tcp.buffersize.umts=4096,87380,256960,4096,16384,256960

net.tcp.buffersize.gprs=4096,87380,256960,4096,16384,256960

net.tcp.buffersize.edge=4096,87380,256960,4096,16384,256960

media.stagefright.enable-player=true

media.stagefright.enable-meta=true

media.stagefright.enable-scan=true

media.stagefright.enable-http=true
[Kindle Fire Android Development] smirkis:
RC1 is upon us?! U gonna merge these changes? can't wait lol
[Kindle Fire Android Development] Sblood86:
Yes that probably does have something to do with the reported video sync issues, I haven't played with the build props much honestly. Thank you for the information on the games, I'll look into this when I get a chance.

Edit: Just to make sure I'm following your saying switfkey does work properly with this my build prop and not the modified one?

Well check the CM blog and gerrit (both open and merged) commit histories and compare this to the most recent changes to the our frameworks_base repo you will see we are already up to date with the most recent release candidate and actually were since a few days before the announcement (guess that means you've been running rc1 since the 13th :p), thank you for pointing this out.
[Kindle Fire Android Development] dieandromeda:
i'm using the latest build. no problem at all but fc on statusbar once in a while, but statusbar came back after the crash..
[Kindle Fire Android Development] vbdss:
Can I use the CWM version file on TWRP? Or vice versa?

And do you know why Tiny Tower and Modern Combat 3 cant be played on your rom?

Do the option Reboot Recovery ends on bootloop? using CWM

EDIT: Modern Combat 3 was only a build.prop edit, but Tiny Tower gives me Missed Shared Library
[Kindle Fire Android Development] chairshot215:
Swiftkey tablet version shows using the build.prop included with your build and does not or say's the app is not compatible with your device using the modified build.prop.
[Kindle Fire Android Development] guyute74:
Prior to this rom (which I like best) I had no issues downloading kindle magazines and reading them on my fire. Now the nytimes newspaper tells me it is not supported on kindle reader apps? Any thoughts? I'm assuming its a build.prop issue?
[Kindle Fire Android Development] Sblood86:
TWRP has broken reboot wrappers hence the recovery loop if you select reboot recovery, this has been fixed on CWM which is why CWM is the preferred recovery.

What exactly did you change in the build.prop to allow Modern Combat 3 to load? Not sure why TinyTower would cause that off the top of my head but I'll try to have a look.

Probably is yes, as for the exact fix I'm not particularly certain. I've been a little distracted as of late but I want to try fiddling with some stuff later today and this week. Can you both do me a favor and open issues regarding the kindle app and tiny tower on github in the issue tracker, make it a little easier for me to keep track of (actually you as well if you don't mind Chairshot), main reason is not having to scroll through a forum to find each issue as more people post stuff.
[Kindle Fire Android Development] acax456:
thanks for the updates...
[Kindle Fire Android Development] mikengcm:
Thanks a lot!

I am a new CM7 user of Kindle Fire. I flash firefirefire 1.2 with twrp already.

How can I remove the twrp & install CWM for your new cm7 build?

Thanks!:D
[Kindle Fire Android Development] Sblood86:
There is a link in post 2 to Smirkis' installation scripts, he has included the DooMLoRD's updated recovery which has a few features that have not been merged into my tree yet, you can use Smirkis' scripts to install it. Otherwise you can actually flash the zips labeled CWM in TWRP just make sure if you do that you do NOT select reboot recovery from the reboot menu while running TWRP (the reboot wrappers are broke and it won't reboot out of recovery).
[Kindle Fire Android Development] smirkis:
just for the record, my scripts actually have your recovery as well. for those who don't want all the add ons. i kinda like my recovery to be bare so i run the one that gets compiled thru your tree. but i do change the power button to be back like i previously mentioned somewhere. but i need to sync up here soon just to be up to date.
[Kindle Fire Android Development] mikengcm:
Thanks a lot!

I will NOT select reboot recovery in TWRP. Thanks!

Oh...But I can't find the Reboot recovery button in reboot menu if TWRP 2.0.

It just contain System & Power Off buttons to select........

Remark: I am using your Feb 21 TWRP build right now!

Anyway... Thanks once more.
[Kindle Fire Android Development] dieandromeda:
sir, rom updated on 28th march?. i don't see any updated link but i only see the new changelog:)
[Kindle Fire Android Development] chairshot215:
Using the Gscript was God awful easy, probably the easiest recovery installation I have ever performed. TWRP has more issues then just the reboot into recovery option.
[Kindle Fire Android Development] smirkis:
The changes were towards the recovery files. I believe. Read the change log for that day. I saw it update again lastnight but not sure what else changed.
[Kindle Fire Android Development] Sblood86:
That is correct (exact reason I didn't update the date in the OP/subject), the changes were to recovery only

There is a link to a binary of the recovery in post 2 (if you are using the DooMLoRDs recovery flashing mine will remove the secondary function such as time and battery {I would like to merge some of these changes, at least in part; as it stands I don't exactly know how to apply those changes and that source has yet to be released} in the meantime Smirkis and I have been fiddling with some other parts to try to make the recovery more user friendly.

Edit: The changelog as you can tell also references changes to the compiling/build instructions/method.
[Kindle Fire Android Development] dnathan13:
Bump
[Kindle Fire Android Development] Sblood86:
I've been fiddling around with something the last couple of weeks and I finally got it working today (took me forever cause I'm really bad at C).

No more asking for specific colors when compiling recovery ;)

I had screenshots I was trying to post here and let people see what I was talking about but it seems they're not posting properly. I'll update the changelog in a minute and the bacon is cooking.

Edit: New recovery is up checkout the ui color switch (we need more colors).
[Kindle Fire Android Development] vbdss:
Extended power off button mod doesnt work
[Kindle Fire Android Development] Sblood86:
Hmm, interesting; I never clicked it lol... I'll have a look tonight thanks for the info.

Edit: for some reaosn I thought you meant power off in the extended commands menu of recovery (just doubled checked; thought I was losing my mind for a sec) there is no power off in the advanced recovery menu... Are you talking about the power off button in rom itself? (again I never even thought to click it but if that's teh case I would want to know if it worked previously as I haven't touched the rom side of the code in awhile lol)

Please report bugs to the appropriate issue tracker on github for easier tracking:

Rom Bugs

Recovery Bugs
[Kindle Fire Android Development] smirkis:
awesome update sblood. floor changes work great and revolt is cleaned up nicely.

one weird thing on first bootup, it was all blank instead of red. I had to navigate my way to ui change and picked cyan. I'm loving it.

only issue. after color change the buttons are still red. not sure if it bothers you or you meant to leave it like that, but I edit the blank images to replace the red ones.