yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Android Development] portezbie:
I can't imagine what else there is to fix since the rom works so well, but I always look forward to your updates.

Thanks again!(How many times is that now....)
[Kindle Fire Android Development] XdxH62:
I don't think goomanager is FOSS. At least I can't find the source code and there is no free license mentioned.
[Kindle Fire Android Development] Sblood86:
New build on Goo.im

Synced w/ CM source and updated for incremental updates.

Future builds should show up and update automatically via the GooManager app.
[Kindle Fire Android Development] shrimpm:
Like like good

:oLike like
[Kindle Fire Android Development] portezbie:
Yay! Thanks for the update! Awesome!

How can we find out what changes/improvements have been made?
[Kindle Fire Android Development] Sblood86:
Only changes made have been on CyanogenMod's side so I'd say their gerritt instance or forums, I haven't really been following the gingerbread branch (at all), I just realized it had been over a month since I updated this and was reminded I wanted to get you gets better update support since noone seams to want to support gingerbread anymore.
[Kindle Fire Android Development] portezbie:
Yeah everyone's all jellybean this and jellybean that now.

Thanks for thinking of us still!
[Kindle Fire Android Development] portezbie:
I think the newest update breaks the accelerometer.

I noticed games like doodle jump no longer seem to work, I just bounce in one place but when I switch back to the june update it works again.
[Kindle Fire Android Development] Sblood86:
Odd... I can't imagine how, I didn't do anything that should effect that; literally the only difference between the last two builds are the CM changes and the goo.im update settings... I'll have a look when I get a chance though (probably be a day or two unfortunately).
[Kindle Fire Android Development] portezbie:
Thanks for looking into it, you're the best.
[Kindle Fire Android Development] Sblood86:
Fixed in the source. Updated something I shouldn't have. Next build will be in a bit, will also be the first incremental update (you will need to be running the broken build for auto updates).

Edit: New build is up. The auto notify is there but goo manager doesn't do push notifications so you may have to reboot or check for updates (this will only work if you are running the July 22 build). Seems the incremental updates themselves are a little different and not working yet but I'm going to look into it further, just download the new rom as usual and flash it :D

Edit 2: Incrementals do work; those packages are repacked by goo bot and subsequently take a bit longer to show up.
[Kindle Fire Android Development] zenzi:
Can other launcher run on this rom ?
[Kindle Fire Android Development] portezbie:
All roms can run any launcher designed for that version of android. This is a CM7 rom so it can run any launcher that isn't designed for ics or jelly bean(nova, apex)

I recommend holo launcher. It has an ics feel to it while being very lightweight and responsive.
[Kindle Fire Android Development] Sblood86:
For those following the progress of Cannibal Open Touch, we have just release version 2.0
[Kindle Fire Android Development] webdroidmt:
Quote:

Originally Posted by webdroidmt

Yes, this will occur randomly and it appears to only do this with JB roms. I posted this issue in the TWRP thread a couple of days ago but I don't think Dees_Troy visits the KF forum too often, so I suspect I will not get a reply.

If TWRP is "unable to open zipfile" and gives you a Failed message, tap reboot to recovery and when TWRP reloads, flash the zipfile again. This has worked for me every time I've gotten the Failed message. From doing a little research, it seems that TWRP has issues with the mount points in JB. I have a feeling we'll be seeing TWRP 2.2.1 in the not too distant future, hopefully this will be addressed.

Mike T

Sblood86 said:

I would venture a guess it's the same issue we dealt w/ for COTR just a few days ago.

Rather than it being random, is it happening when you attempt to flash things from Goo Manager but not when you flash them from the recovery itself?

Assuming this is the case you're exactly right about it being mount points: Goo Manager is writing the ORS script with the value for the download location as seen from the ROM; for example if you are running this ROM and you are using the default Goo Manager download location the path is /storage/sdcard0/goomanager/<name of zip>.

TWRP is going to likely be using the mount point of simply /sdcard/ (I haven't looked at their source recently that is an assumption); obviously that point will fail so the ORS flash will fail. You can than simply view the file from the recovery menu cause it knows where to mount to see the 'sdcard'. It's something that will definitely be showing up on pretty much all JB devices so you are likely correct about an up and coming release as well.

Sblood, thanks for chiming in, figured I'd post here so I don't derail twa's rom thread. This issue also occurs if I transfer the rom zips from my PC to KF, I noticed it mostly happens when I do the transfer from within TWRP using USB mount. It only happens with JB roms and doesn't affect gapps or other zipfiles. Do you think this is a different issue, or could it still be somehow related to the mount point issue ie; storage/sdcard0?

Btw, have you solved this issue with COTR? Thanks.

Mike T
[Kindle Fire Android Development] Sblood86:
No that sounds like something else unfortunately; weird though... As for the issue that I was talking about yes it's resolved (Drew and I just symlinked storage/sdcard0 to sdcard and changed when to mount/unmount that partition(this is really a temporary workaround I'd like to change that code up a bit but as it is it works))
[Kindle Fire Android Development] webdroidmt:
Thanks for the reply, and good to know about COTR. I've done some searching and I haven't found a valid reason why Google needs a third sdcard with sdcard0???

EDIT: My understanding is that symlinks are basically like shortcuts to your files in sdcard, if this helps improve performance, then I guess I can deal with that.

Mike T
[Kindle Fire Android Development] webdroidmt:
sblood, just to let you know that I installed COTR 2.0 last night with smirkit. Haven't done a whole lot with it but flashed twa's JB rom, backed up and restored a nandroid, all went well.

As you know, I (others as well) have been having issues flashing JB roms with TWRP. Lately, it's been kinda' hit or miss, so I figured I'd try COTR and it flashed twa's rom first time, no problem. Also did some reboots in and out of system, no probs as well. Thanks again for giving us a solid working alternative.

Mike T
[Kindle Fire Android Development] Sblood86:
No problem, glad to hear it...

On a less happy note:

You may notice that my goo hosting has been blanked; this is a server issue on Goo's side, you can read about it more @ http://snipanet.com/lustre-pain-and-goo/

I will be uploading a new build later this evening, sorry for the inconvenience.
[Kindle Fire Android Development] webdroidmt:
Yeah, I saw this. Looks like what was supposed to be a maintenance upgrade resulted in catastrophic loss of the metadata. I guess the biggest PITA is that all the devs have to reupload their files.....Bummer!

Well sblood, I hope more people give COTR a shot. Rock on! :)

Mike T
[Kindle Fire Android Development] Sblood86:
Cleaned up the OP and got you GB users a new build posted.
[Kindle Fire Android Development] Thepooch:
Very nice Sblood its good to see someone working on CM7:highfive:updated in index as well:D
[Kindle Fire Android Development] Sblood86:
Just uploaded your relatively monthly update for those of you kickin' gingerbread.

Don't ask me about changes cause I have absolutely no idea. If you are already running the previous build incremental updates should be rolling out shortly otherwise you're linked in the OP.
[Kindle Fire Android Development] portezbie:
Thanks a bunch for maintaining this rom. I'm using cm10 mostly now, but it's nice to know that this rom which is still more stable and still has better battery life, is still being updated.

I also like having it because when I hack other peoples kindle fires this is usually what I give them.
[Kindle Fire Android Development] :
Thank you so much...glad this exists
[Kindle Fire Android Development] :
Can't even believe it...thing has been unplugged 12hrs and still at 95% with about 20 minutes active use...didn't even think that was possible...cm9 would already be at 60% or so
[Kindle Fire Android Development] twa_priv:
This was back in the days when I had CM7 installed :)
[Kindle Fire Android Development] powerpoint45:
I have never tried cm7 for kindle fire. I have always used cm9-10. Did the charging indicator work in cm7?
[Kindle Fire Android Development] Sblood86:
I haven't ran this build in a long time but I believe everything works; I do recommend replacing the kernel with intersect ravens though if you do install it.
[Kindle Fire Android Development] portezbie:
I no longer use this rom but I used it for a while, it is very good. I don't remember anything not working. In fact, although I use jb now, this rom had better battery life.
[Kindle Fire Android Development] Sblood86:
Alright for y'all using it there's the update.
[Kindle Fire Android Development] :
You are the best
[Kindle Fire Android Development] :
Would you be willing to repackage for installation as alt ROM for dual boot (w/ gapps)
[Kindle Fire Android Development] Sblood86:
Maybe but honestly if I do it's a bit on the low side of the priority list. My primary focus as of late has been fixing up Cannibal Open Touch Recovery (mainly trying to bring the portrait and landscape versions more in line and resolving some other device specific issues. One the my current goals for the beta though is actually proper dualboot backup support (may be awhile before it's actually ready); if I haven't repackaged this before then (which I've been considering) I may do it after that's released.

Come to think of it; I'll go one step further even. The source is all open, find me an easy way to rewrite the updater script during the build process so that it compiles already packaged for dualboot and I'll recompile the build on queue :D

Edit: I may have answered my above question, if this works than you may have your wish sooner than you think.

Edit 2: Yeah that didn't work, I'm reminded of why I dislike python; I'll check it out later (away to sleep, I must go :D).
[Kindle Fire Android Development] :
Totally appreciate your response and understand... just wanted to ask....

I used to program in python 10+ years ago... pain... that's why I quit tech and went to law school :eek:

Thanks again for everything!
[Kindle Fire Android Development] Sblood86:
I wanted to apologize for not putting an update out this month (yet):

Normally I would have posted one on the first weekend of the month; this happened to be the same time that we released the current iteration of Cannibal Open Touch Recovery so y'all can see how this may have been neglected.

I would have posted one this last sunday but I've been maintaining this build via the Goo.Im build bot and it has been down for an extended period of time (I haven't looked into if/when they will be restoring it); in the meantime I will be syncing a new build tree to my machine sometime this week.
[Kindle Fire Android Development] :
Thanks SBlood...

Someone made an alt ROM of your November build...runs awesome...maybe he'll update it for the December build...

http://xdaforums.com/showthread.php?t=2037560
[Kindle Fire Android Development] :
Honestly, the rom is so solid as is, the last monthly could be considered about as good as CM7 can get. Been running it for few months as daily and it is just solid.
[Kindle Fire Android Development] Sblood86:
So holidays not withstanding I managed to hose my OS and have to redo it (don't ask why), lost all my goo.im login info (since found; about 2 minutes ago) and generally just haven't done jack code related in the past month lol...

I had a build compiled last week but without the goo.im info I didn't/couldn't upload it. New one from today has just finished uploading as I type this. Had to update the local manifest to reflect Hashcode's new naming conventions being that our device repo is stored in the KFire-Android repos.

Hopefully I'll get around to updating some release tools to compile this as an alt rom (cause I'm too lazy to repack it) but in the meantime here's to keeping legacy stuff alive as long as people use it.
[Kindle Fire Android Development] Guitarman:
I still use your updates of CM7 as alt-ROMs :) This update is greatly appreciated!
[Kindle Fire Android Development] Fedot01:
2 Sblood86: Thank you very much! Your ROM - is the best for Kindle Fire. Fast, stable, without bloatware, but last and all previous versions have small issue - Wi-Fi not resume after sleep :( Can you fix this issue?
[Kindle Fire Android Development] Vlasp:
That's a stock CM7 thing. My friend has a Nook and it also does this on N2A;)
[Kindle Fire Android Development] :
I was able to get around it by changing some settings...can't remember exactly what...
[Kindle Fire Android Development] Fedot01:
This is not common CM7 issue - two my co-workers have Nook Color reflashed into CyanogenMod. Wi-Fi works fine. Other my GB based devices also reconnect to AP after sleep.

I think you mean "Wi-Fi sleep policy" -> "Never". Unfortunately this not fix Wi-Fi sleep bug :(
[Kindle Fire Android Development] furtom:
Thank you for the update. IMO, this ROM is best for functionality on the Kindle. Super fast, great battery life.

As long as you keep releasing them, I'll keep installing them.

Thanks again!
[Kindle Fire Android Development] Fedot01:
I foung a great workaround to fix Wi-Fi sleep bug - Advanced Wi-Fi Lock by Opotech.
[Kindle Fire Android Development] VTCruzer:
Does anyone have a flashable CM7 kernel that OC's? I'd like the option of 1.2 ghz on this rom but I'm terrible with ADB.
[Kindle Fire Android Development] smirkis:
disable screen-lock-disable. for some reason, no screen lock sxreen brings force closes. re-enabling lockscreen fixes it.
[Kindle Fire Android Development] Sblood86:
That should have been resolved; I'm confused
[Kindle Fire Android Development] worldwidepmp:
Could it be because I flashed over my existing ROM from Whistlestop? It was having that issue when I installed yours without wiping.
[Kindle Fire Android Development] chairshot215:
I upgraded from Whistlestop to your builds a few weeks ago with IntersectRavens Kernel and have felt no need to look at anything else. The only issue I came across using this build was that if I turn off wifi and then let it sit in my work desk for a few hours I get SOD. If I leave wifi on or under Juice Defender control no SOD. Used to have this issue in the past but have not seen it since using the last thermocontroled Kernel. Am on like my 6th upgrade and have yet to need to wipe data. Been using TWRP and with each flash I have wiped both caches and system and then flashing Rom, Gapps, Kernel, double wipe caches again because I'm paranoid like that and then rebooting system.

Sorry about typos been stuck in start stop tragic for like forever, will edit when I get home.
[Kindle Fire Android Development] Sblood86:
Ahh, yes probably, if you don't mind and or want to test that you could re-enable the disable lockscreen and wipe it lol (but yes I think that is going to be the cause: I tested this on a clean wipe and did not see any force closes... this was when my kindle powered on lol; sadly my roommate forgot his soldering iron to try to make my factory cable, tomorrow perhaps)
[Kindle Fire Android Development] worldwidepmp:
I just went ahead reflashed fresh. Everything is working fantastic! Thanks again!
[Kindle Fire Android Development] Sblood86:
Sorry I meant to respond to this earlier but I've been distracted. Honestly I haven't seen any such issues and I'm not really sure off the top of my head what could/would cause that. I do want to just confirm one part:

I'm not sure if I am following; are you saying that this issue has been ever present or that one of the versions of IntersectRavens kernels did resolve it?

If it's the latter than that confirms my suspicions mentioned in the second post which I will refer you to for a reason as to why I haven't replaced the kernel as well.
[Kindle Fire Android Development] chairshot215:
Sorry about that,

I used to get the SOD on the stock Kernel & IntersectRaven's when I would turn off wifi and let sit for 4 or 5 hours, Would happen more often when put into Airplane mode. After flashing IntersectRaven's first Kernel that was not thermo controlled I did not see the issue again until after the latest build. I have also since my last post noticed that when using an App that reports mV or temperature the readings are way off as I’m now showing 40830000000mV and 0.0c for temperature. Also I had used a setCPU profile that did not overclock when charging but with the latest build it looks like it will always stay in the charging profile regardless if it is actually charging. I am going to try and rebuild and then report back.

Edit: Just reflashed following the process I described above and things seem to b ok now. The only difference was that instead of using IntersectRavens 2/16 build I decided to re-download the Kernel and saw he has a 2/22 Kernel so I downloaded and used that Kernel instead. Will see later about the SOD issue but everything is reporting correct values and setCPU does not think the Kindle is charging.
[Kindle Fire Android Development] Sblood86:
Awesome, thanks for the input; hopefully it will help others who are experiencing such issues (being that that is all kernel related I really don't have a lot of thoughts as to actually resolving it properly) I would recommend sending something to the kernel devs in regards to the temperature monitoring as that could be the cause of other issues as well.
[Kindle Fire Android Development] worldwidepmp:
Unfortunately I am starting to get the status bar force closes off of a clean flash. Not a big deal but nevertheless annoying.
[Kindle Fire Android Development] Sblood86:
aye that doesn't make sense, unfortunately I have no way to try to test anything but if you can possibly snag a logcat of the FC that may help in finding a resolution.
[Kindle Fire Android Development] dieandromeda:
any info on the kernel you used in the pack?is it stock kernel?.
[Kindle Fire Android Development] Sblood86:
To be perfectly honest about everything I know about the kernel included is in post 2 (and as mentioned I would love to replace it); I highly recommend flashing an alternate kernel after installation.
[Kindle Fire Android Development] dieandromeda:
^i'm downloading your pack, i will try installing this rom along with new intersectRaven's kernel.. hope all went well. thanks
[Kindle Fire Android Development] acax456:
great rom... keep updatinggg
[Kindle Fire Android Development] neugroove:
I'm having browser crashes on certain websites, and while playing flash vids. Anyone else having this problem? Also I've had this same problem on whistlestops rom. Yes I did a fresh install after fully wiping.
[Kindle Fire Android Development] Sblood86:
That's not something that I've seen but I would need to test it more. A few quick questions to try to better understand:

What browser are you using?

Does it happen in all browsers?

Can you name an example of a website this is happening with?

Lastly, and I'm going to update the OP with this request later tonight (about to go to work now) can I get a logcat of the error?
[Kindle Fire Android Development] neugroove:
Hey sorry, I should have told you how much I like your rom. This is the only problem I'm having with it. So to answer your questions...

1,2 & 3. I've used stock, dolphin hd, and opera mobile. Opera mobile works the best, but I have streaming issues with longer videos, and does crash from time to time. The stock browser, and dolphin both crash frequently on www.theblaze.com that's where I find most of my news.

4. I need to find out how to do the logcat thing.
[Kindle Fire Android Development] twa_priv:
If you have adb installed on your computer:

Connect your fire to the PC and type

adb logcat > logcat.txt

Or install Catlog from the market.
[Kindle Fire Android Development] neugroove:
thanks, I appreciate that!

and here's my log...
[Kindle Fire Android Development] Sblood86:
Alrighty, so I flashed the feb26 build earlier today while I was working and played around with it. It's weird the browser isn't actually force closing so much as the process actually dies and it just shuts (ie; no force close message) having said that that doesn't make it any less annoying. I played around on theblaze.com for about 2 minutes earlier and soon as I was about to click an article it crashed. Was taking a look at your logcat and while I can see where the process is dying I'm not sure what is causing it as of yet. I am still researching the issue but I am wondering if it's not related more to how the gingerbread browser handles the site than the rom itself (I'm aware this is effecting all browsers though which is what makes me think the previous shouldn't be the case). In short I have no idea what's causing it but I'm looking into it.
[Kindle Fire Android Development] neugroove:
I appreciate that man... If nobody else complains about it, I wouldn't worry about it. I love this rom, and using Opera works good enough for the moment. Thanks for your hard work.
[Kindle Fire Android Development] sergeroyal:
Fullscreen

Is there anyway to go into FullScreen (hide status bar) inside apps and games ?

pS: auto hide combines bar doesn't work !
[Kindle Fire Android Development] dieandromeda:
new release only work with cwm?.
[Kindle Fire Android Development] Elbob10s:
Works for both, it just doesn't remove reboot to recovery option which will bootloop you if you're not on cwm
[Kindle Fire Android Development] acax456:
Make a version for twrp please
[Kindle Fire Android Development] twa_priv:
Hey Sblood86,

Is there really a need for two different builds (and hence branches) - one for CWM and one for TWRP? Why not just leave the reboot into recovery option out at all?

Even without it rebooting into recovery is as simple as rebooting and pressing the power button during boot up (I'm using TWRP and never tried CWM but assume that booting into recovery works the same for both).

Just my 0.02. Cheers
[Kindle Fire Android Development] smirkis:
Unfortunately, twrp is dead. It works, but noone can update it.

Removing the reboot to recovery option just shouldn't happen. Sadly, I haven't used twrp for months. 1 initial release and the whole project died. Were all trying to move forward, cwm is properly open sourced and now has been updated again by sblood!

Cwm is a bit more basic looking, but has all necessary features, its updated, it can be updated, and works how it should.

So flatout, everyone SHOULd update from twrp, to our new cwmtouch! If not your choice. But the rest of us have moved passed a dead project. IF we had the source, that would be another thing. But we don't.