yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Android Development] animefun135:
Nice rom, but where I can find "hide navbar" option? and why navbar is so small? how to do bigger??
[Kindle Fire Android Development] three-p-o:
Issues charging. Kinda, but not really. When plugged in, it charges. But the icon on the home screen does not indicate charging. Going into battery under settings, shows it is actually charging.

HWA is working, but still has some quirks. I watched netflix the other day and there was a slight audio sync issue. Think it still needs to be tweaked some.

OTG access is not working. Hashcode needs to build the kernel for it and he is working the bugs out first.

Chaining, not sure how to do it if it is even possible.

Edit: forgot to mention. Unless you flash to Kernel 3.0 #7, expect for the battery to drain really fast. #7 has, amongst other things, a fix for an issue with wifi that seemed to have been blowing all the power by overheating.
[Kindle Fire Android Development] :
i tried to install the rom on my kindle. Everything went oke. But after booting it aint working anymore, but worst of all: I cant connect my Kindle anymore with ADB.

I installed the usb driver from KFU without succes... Under Device Manager the Kindle shows up as: "Amazon" with a yellow triangle, and i see a hard drive names "AM".'

Installed ADB and everything, but what i do.. i can't connect with ADB anymore, so i can't unbrick my device.

Is there someone who has an idea?

PS. I did not install TWRP Recovery. Only rooted, installed Clockwork recovery and installed the rom after wiping.
[Kindle Fire Android Development] iesvs:
Use TWRP.

Uninstall CWM and use TWRP. CWM has issues from what I've read.

Edit: Sorry. I feel stupid now. That could prove difficult without adb. But the updated KFU utility works wonders for problems like this: getting adb functions back and whatnot. It's worked every problem I've had.
[Kindle Fire Android Development] three-p-o:
And you apparently did not read the OP. Clockwork has issues with roms based on kernel 3.0. It is being looked into.

I assume you can boot into Clockwork. If it is anything like TWRP you can use ADB in there.

Worst case, you should be able to install TWRP using fastboot.
[Kindle Fire Android Development] rthibeault:
I ran into the same problem (my fault of course, for trying to flash in CWM!) Here's what I had to do...

http://www.jayceooi.com/2011/12/13/how-to-install-setup-android-sdk-development-environment/

http://xdaforums.com/showthread.php?t=1413293

http://rootzwiki.com/topic/12363-how-to-windows-install-twrp-20-on-your-kindle-fire/

Good luck!
[Kindle Fire Android Development] :
Hey just curious the op doesn't say what version of hashcodes kernel this using can someone please confirm if it is 6 or 7? Also if it isn't 7 can I just download the rom then download hashcodes version 7 and after flashing the rom flash the kernel in trwp? Thank you for help!
[Kindle Fire Android Development] rthibeault:
Touch sensitivity

Just FYI regarding the touch screen sensitivity issues. I noticed the same issue. I installed this app from Google Play and it seems to have helped...

https://play.google.com/store/apps/details?id=br.shop4apps.touchscreenbooster.com&hl=en
[Kindle Fire Android Development] TexasRules777:
Thats what i did..just flash rom,g apps then the kernel.
[Kindle Fire Android Development] :
Thank you very very much!!
[Kindle Fire Android Development] Aesrys:
I have the same problem. Thanks for pointing out the fix, it worked fine for me. I did notice that right before the reboot, ROM Control popped a message on the status bar, but it went by too quick to read.

Otherwise, this is a really nice ROM. I do notice a little lag with screen touches, but it's an minor inconvenience for me more than a major issue.

Great job overall.
[Kindle Fire Android Development] three-p-o:
That is an interesting question. Post 3 in the thread provides the info.

There have been atleast 2, possibly 3, versions of the zip package. These are the 2 I know.

aokp_otter_build-33_0xD34D.zip

aokp_otter_build-33r2_0xD34D.zip

33 has kernel #6

33v2 has kernel #7

As much as I respect Hashcode for getting 3.0 working, his packaging of the boot.img leaves a bit to be desired. The img for 6 and 7 both say they were built on Feb 28th 2008 lol. The only way to tell the difference is via file size. Heaven forbid he makes a change where there is no change in size.
[Kindle Fire Android Development] Thepooch:
Works pretty good touch sensitivity needs a little amping battery consumption is high Google earth stops unexpectedly some small buggy things but nothing major. Its really sweet to have HWA on ICS finally netfilx and in browser flash seem to work well for the most part. All in all no doubt this is some fine work thanks:-) :D
[Kindle Fire Android Development] mwcashmoney:
Battery

Does r2 have any better charging support?
[Kindle Fire Android Development] TexasRules777:
I tried wiping dalvik and cache ..even uninstalling and re installing amazon mp3 and each time i press the icon..boom,reboot. (sorry hit the wrong quote..it's for the guy who fixed his amazon mp3 problem)
[Kindle Fire Android Development] BibleBelt:
I've got no adb connection as well.

Compairing this with an the build 32 rom, I noticed that in build 33 I see both the "USB debugging" and the "USB Storage" icons in the notification bar. I'm not able to kill the "USB Storage" from the UI. It always comes back as long as the usb-cable is connected.

When I look at the uevents with udevadm monitor, I get the following

Build 32, working adb:

Build 33, non working adb:

Any chance to kill that "USB Storage" connection in this build?
[Kindle Fire Android Development] renegade027:
Ufff, I've had issues before on a Win 7 64 bit machine - haven't tried ADB with this particular ROM yet - and for a time now I've been using wireless ADB only . Never fails to work. Otherwise, you might want to reinstall USB drivers, etc., and it might work.*
[Kindle Fire Android Development] nathris:
Check to see if the drivers are installed. I've since switched to a different rom, but IIRC the device id has changed with this rom. Not sure why or how that's even possible, but check your device ID in Device Manager to make sure its not different.

I had to add

%SingleAdbInterface%	= USB_Install, USB\VID_1949&PID_0001&REV_021&MI_01
%CompositeAdbInterface%	= USB_Install, USB\VID_1949&PID_0001&MI_01

to [Google.NTamd64] and [Google.NTx86] in android_winusb.inf before it would recognize the drivers, but after that it worked.
[Kindle Fire Android Development] smirkis:
I really like the polished feel in this rom, but the touch slop makes it hard to use regularly. and rom control crashed randomly pretty often now.
[Kindle Fire Android Development] vbdss:
The problem is with USB somehow, ive used ADB before with kindle and use with Samsung Galaxy 5.

I can access adb using Wifi adb
[Kindle Fire Android Development] 0xD34D:
So what are you doing when ROM Control crashes? A little more info can help to track down possible problems. Just saying it crashes is not a big help without knowing what is going on at the time and the steps required to reproduce it.

I'm actively working on this ROM so the more info that you guys can provide me when you have issues, the better chance I have at tracking down the cause and fixing it.
[Kindle Fire Android Development] nathris:
It doesn't matter if you can access it using another device or if you've accessed it before. If the device isn't showing up in ADB then you either have debugging disabled, or the driver isn't installed. Since you have wireless ADB setup I'm guessing its the latter.

Even if you've installed the driver, if the device ID has changed Windows won't recognize it as a Kindle Fire. On mine it showed up as "Amazon" instead of "kindle" with a device ID of VID_1949&PID_000

1

when it should have been VID_1949&PID_000

6

.

When you plug the device in Windows will scan android_winusb.inf for that ID and if it doesn't match then it won't use the driver. No driver, no ADB.
[Kindle Fire Android Development] vbdss:
My device is recognized as Storage and shown as "am"
[Kindle Fire Android Development] nathris:
Android uses separate drivers for ADB and Mass Storage. You can have mass storage without ADB. If ADB is installed it will show up like this:

Check to see if there are any unrecognised devices.
[Kindle Fire Android Development] vbdss:
No devices unrecognized

ADB on TWRP works fine
[Kindle Fire Android Development] AlexDeGruven:
What app are people using to take screenshots on this rom?

I haven't gotten any to work yet, and we don't have the hardware to do it native.
[Kindle Fire Android Development] nathris:
TWRP is different. When I was having trouble I could still access adb from recovery. But if the device isn't even showing up looks like you have the opposite of the trouble I'm having. I have ADB but no mass storage on CM9, but mass storage works in TWRP :p

Try plugging it in and using DDMS (android-sdk\tools\ddms.bat). Just select your device and press ctrl-s.
[Kindle Fire Android Development] AlexDeGruven:
I would, but adb isn't working for me right now.
[Kindle Fire Android Development] vbdss:
maybe ADB is broken on this rom
[Kindle Fire Android Development] MarkGbe:
so i just rooted and install this, build 33. Everything went fine except my wifi wont connect. Just says "obtaining ip address". I rebooted, powered off and back on and no good. Any ideas?
[Kindle Fire Android Development] Piercing Heavens:
Minus the touch screen needing multiple touches at times it works perfectly. Nav bar isn't fully working but its functional.
[Kindle Fire Android Development] vbdss:
AOKP Build 34 is out

http://forum.aokp.co/page/news
[Kindle Fire Android Development] machos1:
as opposed to what said in kernel post, am able to charge fine with wall charger, it doesnt show up as charging in notification though, only shows up in settings/battery...
[Kindle Fire Android Development] rg1973:
Edit
[Kindle Fire Android Development] vbdss:
Where did you got the Build 34?
[Kindle Fire Android Development] rg1973:
From your,link
[Kindle Fire Android Development] rg1973:
I guess that wasn't the update it says otter 34 build just reflashed 33 all back now wheew
[Kindle Fire Android Development] vbdss:
That build is from the Kang Team, makers of AOKP. They dont seen to pay much attention to kindle, so i advise to not use their rom.
[Kindle Fire Android Development] rg1973:
R u sure that's not the same from my goo inside app says that is the update for this rom
[Kindle Fire Android Development] dw9906:
Try selecting "screenshot" from the power menu.
[Kindle Fire Android Development] pbailey212:
You have to turn on screenshots in the rom tools menu (sorry I can't be more spacific, I'm away from my kf right now)
[Kindle Fire Android Development] vbdss:
Damn sure. They are made by different people
[Kindle Fire Android Development] Creampuffyness:
For anyone interested I was able to flash 33 from this thread over 32 from johnwaynes thread with only wiping cache and davlik.
[Kindle Fire Android Development] Hashcode:
Any ROM from AOKP directly would be built using the older kernel and no have the newer features working.

As soon as we kill off the last of the major kernel bugs expect to see Kindle fully merged w/ AOKP and then links like this one will work. :)

Adding to that, devs are also taking the time to make the ROM better than straight AOKP and that's something to consider as well.
[Kindle Fire Android Development] evo_like:
looks awesome, I am trying to give this a shot now. But my fire won't flash this....doesn't find a verifiable MD5 sum and doesn't flash. I have tried multiple downloads of the file (this is my 4th try now) but with same result.

Am following the usual flashing instructions but with same result. Any suggestions or thoughts?

Keep on getting E:cannot load volume /misc! error
[Kindle Fire Android Development] vbdss:
E:cannot load volume /misc! error its normal. Our device dont have this partition

Are you using TWRP?
[Kindle Fire Android Development] 0xD34D:
I'm away from my computer so I can't update this thread at the moment but I did update to build 34 and you can get it at http://rootzwiki.com/topic/23717-rom4232012-aokp-build-34-for-kindle-fire/ for now.
[Kindle Fire Android Development] 0xD34D:
Exactly. I'm even submitting my changes to AOKP code review so if all goes well some of these features will become part of AOKP out of the box.
[Kindle Fire Android Development] evo_like:
yes i am.

So even though it's showing that error, it's actually flashing? So I should go ahead and flash gapps, then reboot device?
[Kindle Fire Android Development] Thepooch:
Screenshot can be added to your nav bar under rom control nav bar I believe I just added a button to a total of 5 and long pressed the empty button 5 and added screenshot:-)
[Kindle Fire Android Development] webdroidmt:
You got a free thanks, I was trying to thank lithium's post above and yours popped up. :p

Mike T
[Kindle Fire Android Development] evo_like:
Thanks! and thanks! :p you got a thanks as well :-) lol
[Kindle Fire Android Development] webdroidmt:
Well, thank you! :D How did your flash go with the rom and gapps?

Mike T
[Kindle Fire Android Development] evo_like:
it went very well actually, now that I figured that i can ignore that message about E drive. The problem I am having now is that I need to go to bed about an hour ago, but I am stuck playingon my fire with this frakking awesome of a ROM. holy crap. I am loving it!! I have not experienced ICS on any tablet before...I am still getting used to it right now, and my god i am frakking loving this right now. i am gonna need a couple days to get used to finding things and such. But i am loving this right now. :):):):):):D:D:D:D:cool::cool::cool:
[Kindle Fire Android Development] webdroidmt:
I take it from your post that you like this rom. LOL Don't know if you've read any of the stuff from Hashcode's kernel thread but be sure to power down properly by holding the power button down a second time for approx 20s until you see the backlight go dark. Enjoy!

Mike T
[Kindle Fire Android Development] evo_like:
I don't usually power this down all the way either ways I have just pushed the power button and let it go on usual standby . Is powering down all the way recommended or something then?

Btw thanks for looking out.
[Kindle Fire Android Development] Thepooch:
Dont forget to charge it nothing worse than a dead battery lol :D just flashed 34 over 33 only wiped dalvik and cache all good so far:-)
[Kindle Fire Android Development] evo_like:
Gotten a couple fc's...the systemui one a couple times, and the trebuchet launcher one once. Reading earlier.... this is pretty common?
[Kindle Fire Android Development] evo_like:
Sorry for another post but I felt I needed a separate post to thank the dev. Thank you for working on this ROM, lithium. I am loving it so far, and look forward to all the wonderful work you are going to put in this ROM (which you already are!) :-)
[Kindle Fire Android Development] Alessioromatm:
I don't understand if is possible to use bluetooth and wi-fi at same time,is it possible?
[Kindle Fire Android Development] MarkGbe:
figures this out... the mac address changed? Not sure how that works but alright. :)
[Kindle Fire Android Development] three-p-o:
It is possible, just not with the Kindle Fire as it does not have a bluetooth chip.
[Kindle Fire Android Development] Alessioromatm:
LOL :D so why bluetooth appears below features list in OP ?
[Kindle Fire Android Development] jmartin72:
I was wondering that myself, because the KF does NOT have bluetooth!
[Kindle Fire Android Development] cellgeek:
Noticed that my KF doesn't want to power off when I shutdown. This is a nice ROM for the KF. Hoping that eventually all the "phone" stuff gets pulled out and it fit's the KF like a glove.

Nice work!!
[Kindle Fire Android Development] pbailey212:
Lithium copied and pasted the change log from the aokp website. Its a general change log, not device specific.
[Kindle Fire Android Development] Thepooch:
Bluetooth is a feature of the rom its not necessary to write it out even if kindle doesn't have Bluetooth but its available if this was ported for another device some items are left because of the length of time to remove them and potential of creating instability of doing such. It affects nothing to just leave it :D
[Kindle Fire Android Development] dnd61:
Please remove Camera option on the lock screen, when I choose the Camera option my Kindle Fire auto reboot.
[Kindle Fire Android Development] Aesrys:
Just curious, did anyone else have to flash GAPPS again after going from 33 to 34 (or is that normal)? I flashed to 34 and everything seemed OK, but when I tried to go to Play Store, it said the App was not installed. When I flashed 34, all I did was wipe both caches.

Anyone try Amazon MP3 with 34? Just curious if it still does the weird quasi-reboot thing.

Thanks.
[Kindle Fire Android Development] acax456:
Me too
[Kindle Fire Android Development] Aesrys:
This was actually part of the #7 kernel. Hashcode added a script that basically spoofs a unique MAC address. He did this to deal with that fact that previous kernels were all installing with the same MAC (not really an issue unless you're running multiple rooted kindles on the same network). I believe he stated that once the new MAC is set, it shouldn't change again. Hope this helps.
[Kindle Fire Android Development] dnathan13:
don't choose it... or disable it in rom control...

---------- Post added at 08:31 AM ---------- Previous post was at 08:30 AM ----------

Thats standard procedure with AOKP. I run AOKP on my phone and have to flash gapps everytime.
[Kindle Fire Android Development] Aesrys:
Thanks, I wasn't aware of that since this is the first AOKP build I've used. Wanted to make sure I didn't miss something.
[Kindle Fire Android Development] sthomas38:
Is the AOKP status bar like the screenshots in the OP? I mean the buttons. They are really "close". Can it be changed? Thanks :).
[Kindle Fire Android Development] acax456:
Setting / rom control / nagative bar / menu location / left
[Kindle Fire Android Development] Aesrys:
A previous poster mentioned that they're not quite as close if you add a 5th button to the bar (Settings->Rom Control->Navigation Bar->Navigation Button Quantity). I added a 5th button (only 4 actually show unless an app needs the Menu) and added the Play Store to it. Others have added the ability to do screenshots. Hope that helps.

---------- Post added at 08:48 AM ---------- Previous post was at 08:46 AM ----------

Or you could do it the simple way. :D
[Kindle Fire Android Development] sthomas38:
Thanks :).
[Kindle Fire Android Development] evo_like:
Would somebody be kind enough to please fill me in on the recommended charging method? I charged it (wall charger) for at least 5 hours but the battery didn't juice up all the way to 100 ( went from 38 to 83)...I know its an issue right now with the hash kernel but I am not clear on how to counter this ans charge it all the way up. Any thoughts would be appreciated. I am on build 33. TIA.
[Kindle Fire Android Development] dnathan13:
Charge it longer. It is just a slow process so you have to charge it longer to get a full charge. Plus it isn't optimized fully yet so it is still getting a pretty good amount of battery drain it has to contend with.
[Kindle Fire Android Development] pbailey212:
Were you using the Charger that came with your kf?
[Kindle Fire Android Development] operanal:
Stuck in boot loop

First of all, I want to thank the devs for the incredible effort. I honestly have no idea where you all have time to get all this going.

So...

Using TWRP 2.0.0 and coming from a stock rooted 6.3 ROM, I wiped my Fire (system, cache, factory reset, etc), then installed the rom and gapps as specified. Upon reboot, the Team Kang boot animation came up, but then the device rebooted itself and is now stuck in a boot loop when plugged in to USB. It shows the fire-in-a-triangle image for a few seconds, then reboots. Pressing the power button doesn't get me into recovery, and all ADB utilities (Fire Utility 0.9.5, Unbrick Utility 1.1, etc) to set the device to normal boot are not working. It seems the device reboots before the USB driver has a chance to load.

Oddly, I cannot get the device to boot up when it's unplugged at all.

Has anyone else seen this?

---------- Post added at 11:19 AM ---------- Previous post was at 10:46 AM ----------

Slight update: with some plugging-cycles, I can get the ADB utility to see something, but it spits out "FAILED (status read failed (Too many links))"
[Kindle Fire Android Development] webdroidmt:
Hashcode recommended powering down with the initial release of the new kernel, due to excessive battery drain. Now, with the latest kernel, battery is no longer an issue. I'm just in the habit of leaving it on standby but powering down when I go to bed.

Mike T
[Kindle Fire Android Development] Aesrys:
This might be a dumb question, but could your battery just be really low, especially since you mention it won't boot at all without being plugged in? Just trying to throw out ideas.
[Kindle Fire Android Development] operanal:
Not a dumb question- I am wondering about that myself. I'm a bit wary of leaving the device in a boot loop for an hour to build some charge (if it even will). The power light comes on green, then goes out when it reboots.

I need to find a charge-only connection and see if an orange light will come on and stay on.

<update> using a micro-usb cable plugged into a generic usb wall charger, the boot loop is much faster. Plugged into a PC, the initial fire-in-a-triangle screen would last about 3-5 seconds before rebooting. Now, plugged into the wall, the screen lasts only a second before rebooting.
[Kindle Fire Android Development] evo_like:
Yes I was.

Is the latest kernel baked into build 33?
[Kindle Fire Android Development] rubytuesday007:
To the OP...there is an issue with downloading this ROM. Tried in multiple browsers and it says interrupted at about the 99% point. Not sure if its me or the link.
[Kindle Fire Android Development] acax456:
I had no problem :|
[Kindle Fire Android Development] Aesrys:
How do you actually confirm that the device now registers as what you changed in the build.prop? I can see the GT-P6210 in About Tablet. However, when I go to Google Play (website) and look at my devices (My Orders and Devices (bottom of page)->Devices) I still see the system listen as Amazon Kindle Fire. Or should that not update? I force stopped both Google Play and Services Framework and cleared cache/data on both, then shutdown the tablet. Thanks for any help.
[Kindle Fire Android Development] Creampuffyness:
I had the same issue, and it was indeed the battery. When the device was off, plugging in the charger or to a PC would boot the device, attempt to boot, power off and cycle. I ended up going into recovery and letting it charge off the AC power. When I rebooted around 50%, I was able to get ADB working again for whatever reason.

Edit: Re-read your first post, are you able to get into recovery now?
[Xperia Arc Q&A, Help & Troubleshooting] echo1991:
Hey guys,

something I noticed about FXP117 (CM7) is that it seems to miss the auto-backlight function/button/options in the settings. Something else I noticed, when I recover from lockscreen the screen seems darker than before, I'd say darker than the minimum selected in the options.

Is there any fix for it?

I've got no auto-backlight functions/settings/buttons what so ever.

thanks in advice
[Xperia Arc Q&A, Help & Troubleshooting] echo1991:
I also noticed that setting the brightness via swiping over statusbar does not work =/
[Xperia Arc Q&A, Help & Troubleshooting] am2222:
I cant find auto brighness setting in ICS ...what I must do?
[Xperia Arc Q&A, Help & Troubleshooting] soad0:
well I think it is a known problem in CM7 for ARC.

That the reason I remove CM7, waiting for this correction