yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Android Development] Hashcode:
Hello,

The flashing LED effect that you're seeing is a side-effect of the poorly written charger driver.

Basically the LED shows green when told by the charger that the device has a full battery. Then it partially suspends and the LED light goes out. And the next time the charger sends the update to the LED it turns on again and shows green. Rinse repeat.

Normally you would only see this while plugged into AC, because while connected to a computer deep sleep is disabled.

Question: you're seeing the charging inidicator in the OS? As far as I knew that was still broken.
[Kindle Fire Android Development] fox_dye:
After allowing the tablet to charge for a bit it s working just fine and I am not seeing the heat issues others are.
[Kindle Fire Android Development] southbird:
Screen banding is gone for me as well!

With #7, this is the first time I've ever tried running Netflix (I know, I probably have before etc.) I downloaded the APK from here, and all it does is terminate immediately and quietly on launch. Not sure if I need to use a device-agnostic version or something like that; is the immedate termination the problem that everyone else is talking about?
[Kindle Fire Android Development] TexasRules777:
Weird..I'm using aokp 33 and the latest kernel and Netflix is working fine on my end.
[Kindle Fire Android Development] BrooksBlood:
Just download Netflix from the play store. Works fine for me
[Kindle Fire Android Development] fox_dye:
Why don't you just download it directly from the play store? I'm having no issues with Netflix
[Kindle Fire Android Development] mjybarr:
What rom are you using?
[Kindle Fire Android Development] mjybarr:
Yes I have immediate termination upon playing a video on Netflix. I'm on Biteblaze latest rom and Hashcodes latest kernel and Netflix from the market.

EDIT: Finally I found out why Netflix isn't working. I believe its because of BiteBlazes latest rom mixed with the latest kernel.

I went to page 16 of this thread, downloaded that rom, booted it up, flashed Hash's latest kernel and bada bing! Netflix works! I'm not for sure exactly why BiteBlaze's rom won't play Netflix with the latest kernel. Anywho...for those that are having troubles, maybe my trail and error will help you out. I apologize for contributing to the whole "Netflix" issue and flooding this thread with that issue.
[Kindle Fire Android Development] shahabk818:
I think my Fire doesn't charge, it was pluged in to usb for half hour and didn't charge a bit, stuck in %90:confused:

Anyone has this problem?

--------------------------------------------------

oh never mind restarted and now its charged
[Kindle Fire Android Development] biglama:
I lied, charging shows in one of my Widgets not in the actual notification area. I guess I haven't paid that much attention to it for the past week. At least I know its charging. :-)

Thanks for the info on the led, again not a complaint just something I noticed.
[Kindle Fire Android Development] southbird:
You're right, this ultimately made the difference for me! Installing GApps and using Play Store to install Netflix worked peachy!

So no banding AND Netflix, Hash!

Tip for everyone: I wipe EVERYTHING before EVERY install... in the case of #7, installed the ROM from #6 and then the #7 kernel... I think this is the best way to eliminate variables.
[Kindle Fire Android Development] motioneso:
What should we be seeing in the way of USB OTG? I tried a keyboard, mouse, and flash drive all to no avail. Is there an app to monitor USB activity?
[Kindle Fire Android Development] shahabk818:
New issue: the battery bar doesn't show the right %... like i was playing around with fire and it was stuck in 100 and then i restarted and it was 85
[Kindle Fire Android Development] SalsaForte:
Just a short message: Go go go! You can do it! :D

Nice work... But it's not clear in the first posts, does the Kernel have hardware acceleration?
[Kindle Fire Android Development] Damedus:
I'm interested in a build prop that would fix the gameloft games issue I'm not sure if its Cm9 related or kernel but these used to work on 7. It might be sure to the bar not hiding, even if the option is listed in the settings it's not hiding in games, has anyone gotten around this?
[Kindle Fire Android Development] acax456:
Sure
[Kindle Fire Android Development] SalsaForte:
So, once the charger issues are fixed, I'll give the Kernel a try.
[Kindle Fire Android Development] animefun135:
LCD now fixed, thanks Hash! but HD video still laggy even in HW decoder.

In my experience, I realized that the HW decoder ICS does not work as well as on the Gingerbrad, because the tablet strongly heated ICS as well as video lag.

It seems that the new hashcode's kernel does not use all the power of HW decoder, but only part of it.
[Kindle Fire Android Development] lovejoy777:
can you anyone advise on otg (is it enabled)?
[Kindle Fire Android Development] alan110112:
Flashed #7: no more lcd ghosting lines!! :D

USB OTG worked only with an usb keyboard and a diy OTG cable. (On micro-usb: every contact as usual, sence -short circuit- on pins 4-5 to allow kindle detecting the USB device)

Tested OTG with a usb powered hub: never recognised... usb mouse: never recognised... usb flash drive powered/direct: never recognised.

EDIT: to test usb otg detection you can use the market app USB Host diagnostics
[Kindle Fire Android Development] donsam:
battery life is excellent in this kernel. the heating is gone. cant wait till the next release:)!!!

keep em coming !!

audio does have a little issue tho. it comes and goes according to the program you are running. the screen still flicker when waking.
[Kindle Fire Android Development] GoSooners345:
Snappy

This kernel is stable now :-)
[Kindle Fire Android Development] Felnarion:
Guess this thread being dev only went out the window.
[Kindle Fire Android Development] southbird:
I didn't know about the pin 4/5 short for sense thing, but it does appear to be typical. (And described here.) That's a good point; when I get my cable I will have to check this.

As far as a hub is concerned, it SEEMS like you are required to use an On-the-Go compatible hub. Something to do with how which device knows it should be host or not. But I'm not sure about this (but I have failed to use a typical hub in OTG on a different device.)
[Kindle Fire Android Development] alan110112:
Since I have read that many users do not know how to build an usb otg cable compatible with this build, I have written a little guide+video you can find here: http://goo.gl/x28h7

Hope this can help.
[Kindle Fire Android Development] Jaimemex:
Any way to get headphones with mic working on the ROM? For Google voice search...
[Kindle Fire Android Development] remmie80:
I've so far tried an harddisk with external power supply, a bluetooth adapter and a usb flash drive and a usb memory card reader with a DIY otg cable. None of them worked.

USB host diagnostics only detected the bluetooth adapter, but I didn't get it to work, but there are probably no bluetooth drivers?

So did the other's not work because of the cable, the drivers or because not enough power? And does it matter how my hard drive is formatted?
[Kindle Fire Android Development] southbird:
I'd imagine running dmesg in the terminal would be more useful in terms of seeing what the kernel is doing (i.e. if there's any connection at all, if it fails to bind it, etc.) And hard drive format matters as far as what file system drivers are in this kernel.
[Kindle Fire Android Development] rukin5197:
Hash, probably stupid question here, but if I sync with your device and vendor files do I automatically get the new kernel? Or will I have to add it in manually?
[Kindle Fire Android Development] twa_priv:
You only need device-amazon-otter. The vendor repo is not needed right now.

And yes, Hash updates his device repo usualy once a new kernel build is ready.
[Kindle Fire Android Development] Hashcode:
Mic input is currently broken and on the issue list.
[Kindle Fire Android Development] tabormeister:
Banding obliterated, a little touch panel weirdness in multitouch use, the usual issues and notification popups freak out and checkerboard (possibly rom issue but seemed like it appeared with kernel 7) otherwise, butter.

Hash rules.
[Kindle Fire Android Development] Damedus:
Hash is autohide of the notif bar on the todo list for fullscreen aps and games(its only working on videos) the bar seems to be limiting some older games from gameloft(preICS) making them crash due to the resolution being limited of that area (u can notice the logos and stuff before the crash don't occupy the whole area but rather re sized and not even centered (black bar at one side) then some go into gameplay for a few secs/mins before closing, these used to work on 7 and hid the notif bar, on the other hand the newer games (six guns, DH3) work flawlessly and adapt to the visible area screen and the notif bar does not seen to affect them. perhaps older games were set for not having the bar consume space while you played. Or perhaps they dont work on ICS period( dont have a phone to test them in) any thoughts?
[Kindle Fire Android Development] Royalaid:
I had this problem on ReloadedRom. I wiped flashed over to build 33 of AOKP then reflashed Kernel #7 and the notifications work fine, I also noticed that it seems to be much snappier.
[Kindle Fire Android Development] backspacepc:
Did you resync the device tree as well? I've done a couple builds so far with no issues.

DEVELOPMENT THREAD!!!!!
[Kindle Fire Android Development] soupmagnet:
Yes, and as far as I can tell my device tree is an exact replica of the one on github.

Could it be that cm9 was updated recently and that's causing problems?

I synced the ICS repo last night for the first time for this build while I was in bed last night and twice this morning.

I'm just going to scrap the whole thing and try again.
[Kindle Fire Android Development] Hashcode:
NIXED THIS PATCH. Nothing to see.
[Kindle Fire Android Development] Hashcode:
So I worked till about 3am on the backlight running various tests and comparing the flow of the driver to the 2.6.35 kernerl backlight driver.

All without any success in making the backlight work better.

I'll be on it again tonight.

And when I get some time I'll outline the issue here.
[Kindle Fire Android Development] rukin5197:
Have you been able to recreate the issue yourself? It would probably be better then.
[Kindle Fire Android Development] soupmagnet:
I feel completely f**king retarded now. I cannot, for the life of me, get this damn thing to build. I've scrapped everything and started over three times, followed directions to the letter, yet I keep getting the same errors.

/vendor/cm/config/common_tablet_wifionly.mk calls for both...

/frameworks/base/data/sounds/NewAudio.mk

...and...

/frameworks/base/data/sounds/AudioPackageNew.mk

...which, obviously don't exist. I've synced everything several times, checked that the manifest is in the right folder (I'm sure it's a manifest issue) and I'm completely dumbfounded. I'm obviously doing something wrong or else no one would have had success building, I just can't figure out what.
[Kindle Fire Android Development] Hashcode:
I dropped our custom frameworks/base earlier today so that build issues can be avoided.

Can you refresh your local_manifest.xml from here:

https://github.com/KFire-Android/android_local_manifest/blob/ics-test/local_manifest.xml
[Kindle Fire Android Development] astmario:
Delete this if it's irrelevant, but it is confirmed that Samsung Galaxy Tab 2 7.0 is having the same TI 4430 platform, and it is running ICS. Does it help if someone get it's hand on it, you know, getting ducatiMM from it or something?

http://www.engadget.com/2012/04/11/samsung-galaxy-tab-2-7-0-review/
[Kindle Fire Android Development] southbird:
Check this review instead: http://www.wired.com/gadgetlab/2012/04/first-look-samsung-galaxy-tab-2-7-0/

The kicker is that the Galaxy Tab has 1GB of RAM, which is just wonderful for ICS and Ducati, but on Kindle Fire, we don't -- only 512MB. That's what makes this port so difficult.

Short version: Sorry, no, Galaxy's Ducati doesn't help :)
[Kindle Fire Android Development] backspacepc:
Reported. On a more serious note, hash, did you ever see what was causing the non shutdown issue? Looking through logcat , mine ends right at where the kernel is doing its last calls and then hangs at CPU0 and doesn't report anything else. Do you have the original source from TI? It looks like something is missing.
[Kindle Fire Android Development] astmario:
That review it wrong, it says that 7.0 Plus and Tab 2 7.0 both have AMOLED screen's and both have same 1,2GHz CPU, both wrong info, both have PLS LCD, and plus have exynos 1,2 CPU while tab 2 7.0 have TI 4430.

I could not find any info on RAM on Samsung, but you probably are right about 1Gb.
[Kindle Fire Android Development] southbird:
How about from the mouth of the beast itself?

http://www.samsung.com/global/microsite/galaxytab/7.0/spec.html?type=find
[Kindle Fire Android Development] Whiskey103:
Okay guys.

I am aware and will deal with it ;)

Thread cleaned

Cheers!

Whiskey

Forum Moderator
[Kindle Fire Android Development] shantam:
mod edit: STOP!
[Kindle Fire Android Development] backspacepc:
Thank you!!
[Kindle Fire Android Development] astmario:
Those are 7.0 Plus spec, I talk about Galaxy Tab 2 7.0:

http://www.samsung.com/global/microsite/galaxytab2/7.0/spec.html?type=find

No spec. about RAM, I don't say you are wrong, just I cant find any info on it.

EDIT: You are right.

8 / 16 / 32GB User memory + 1GB (RAM)
[Kindle Fire Android Development] Krunk_Kracker:
Hash has already gotten Ducati to work with 512.

I'm sure it wouldn't be a problem for him to get it to work again...that's assuming those tablets would be helpful.
[Kindle Fire Android Development] backspacepc:
Ducati is starting and running, we just need to get the codecs worked out.
[Kindle Fire Android Development] southbird:
Well if you feel that way then you probably shouldn't be concerned with the Fire... because pending some kind of tedious hardware hack, 512MB is all it's ever going to have. Who knows about future models, but I'm not expecting too much. (And we'd probably need a whole new kernel again...)
[Kindle Fire Android Development] backspacepc:
Bird, that's just a troll. Don't bother with him.
[Kindle Fire Android Development] SalsaForte:
Effectively, I have 2 kindle fire with kernel 6 and both can't use the Internet at the same time.

I'll patch one with v7 right away.
[Kindle Fire Android Development] vbdss:
Use the new v7 Kernel that hashcode uploaded today, it fixes wifi
[Kindle Fire Android Development] Techlyfe:
Isn't the ROM on that is linked to on page 16 test version 2?

Shouldnt you be using the ROM that is linked in the first post?

Or maybe i'm wrong. <shrugs>
[Kindle Fire Android Development] vbdss:
Hashcode post on his site everything related to the ROM and Kernel

Just use this URL http://rombot.droidhive.com/ROMs/otter/

There you will have access to Kernel and ROM, always the latest!
[Kindle Fire Android Development] HeWhoWas:
Thank you both for helping me out. I still stand by my original point though: This should be for development only, as stated in the original post. I will be making it my daily mission to remind every single person of this when they post in the wrong place.
[Kindle Fire Android Development] dnathan13:
Wait... Like you just did twice? What are you developing? ;) Sorry I couldn't resist. :D
[Kindle Fire Android Development] HeWhoWas:
I'm not saying I've contributed much, but I have a day job that has to take precedance :-) I did help a little during the infancy of the KF CM9 build with JC, but kernel work is above and beyond my level of experience. And yes, I know I'm just as guilty but at this point I feel like it's pissing in the ocean :-P
[Kindle Fire Android Development] Arjen:
Topic cleaned, please try to keep it friendly ;)
[Kindle Fire Android Development] intersectRaven:
O...k...my post also got cleaned in the process, anyways, to sum it up:

Please post HOW TO FIX PROBLEMS ENCOUNTERED on this thread. For REPORTING ENCOUNTERED PROBLEMS, please post on the sister thread of this thread located in the GENERAL SECTION.

Hashcode, me and other contributors regularly read BOTH threads so be assured that we are on top of things. Please be PATIENT as hashcode and most of the contributors don't do this as their job and just work on it at their leisure or at their free time. :)
[Kindle Fire Android Development] Arjen:
Topic cleaned again,

please post in appropriate thread!

You can find the link to User Discussion thread in first post!
[Kindle Fire Android Development] twa_priv:
Hey Hash,

Seems like Netflix doesn't like your recent device naming changes (Amazon Kindle Fire -> Kindle Fire). The window which is supposed to play the video just pops up for a second and then closes.

I verified this by changing ro.product.model back to Amazon Kindle Fire in build.prop and voila, netflix works again :)

https://github.com/KFire-Android/device-amazon-otter/commit/b130d49e25461a642aad9b122a6b5f0853802501

https://github.com/KFire-Android/device-amazon-otter/commit/e1202a33fbbceb087f6ff7c5fecc54fd51f87bb1

The new boot animation looks good btw. Thanks
[Kindle Fire Android Development] southbird:
[EDIT: Sorry, this was ROM #6 with Kernel #7, didn't realize the change was so recent.] Is there maybe a legal/support reason that Hash changed the name? It seems like it was deliberate and I'm guessing he had good cause.
[Kindle Fire Android Development] twa_priv:
I also uninstalled/reinstalled netflix from the play store and it didn't work. Which rom are you on? I tried hash's latest cm9-kfire-3.0-hashcode-04-22.zip and also my own build - same issue. Only changing the device name in build.prop fixed it.
[Kindle Fire Android Development] southbird:
Never mind, I didn't realize how recent this was. I was running ROM #6 with Kernel #7 when I tried Netflix. Hash did mention a Netflix issue he was looking at, maybe this was it. Still, wondering why he "fixed" it as such, and still wondering if it had to do with some kind of lash back from Amazon or something.
[Kindle Fire Android Development] Jaimemex:
Where do u change it in? Root explorer?
[Kindle Fire Android Development] nathris:
That's one way. I prefer to use adb, although it does require you to have the Android SDK.

From the command line:

Remount /system in read/write mode

adb remount

Copy build.prop to your PC, it will show up in the same directory as adb.exe

adb pull /system/build.prop

Edit build.prop using notepad or your preferred text editor

Push build.prop back to the device

adb push build.prop /system/build.prop
[Kindle Fire Android Development] tedr108:
Any simple text editor should be fine. You can get to it thru Root Explorer or ES Explorer, etc.

Edit: You would probably end up having to change permissions to do it this way, so use the adb method mentioned by nathris above. That's actually the way I normally do things like this, though I am typically booted into recovery while this is being done.
[Kindle Fire Android Development] pbailey212:
I heard that if you ask in the proper thread (for instance the general thread) you might get better answers
[Kindle Fire Android Development] djkeller3:
I use the build.prop editor tool in Root Tools. You can get Root Tools from Google Play. I think its free. :)

ROM: CM9 ReloadedROM v1.2H

Kernel: Hashcode 3.0.21(#7)

Overclock: 1.0 GHz Max, 1.0 GHz Min. Performance

Launcher: ADW EX
[Kindle Fire Android Development] AlexDeGruven:
A note on charging.

While on a standard USB2 plug (or other <1A USB plug), it doesn't appear to charge while powered on (charges fine while powered off).

I was able to get it to show charging when I plugged in to a USB3 port on my UD3 motherboard, but I am having some driver wonkiness with ADB which really freaked my system out.

So, it would appear, if you want to charge via USB, do it via USB3 (with the extra power availability.
[Kindle Fire Android Development] icemank121:
On AOKP it was showing Amazon twice which is why he changed it, but I think he changed it on CM9 by accident. No Amazon complaints or anything
[Kindle Fire Android Development] Airbag888:
if you got a keyboard like swiftkey you can use vi itself.

open a console on the kindle with Connectbot (for example)

#su

#vi /system/build.prop

--use the arrow keys to get to the proper char

--hit A

--type in Amazon space making sure it reads Amazon Kindle Fire

--touch the screen then touch on screen Esc button

type :w

then :q

and you're done
[Kindle Fire Android Development] nathris:
I think its charging, just not at full power. I had mine plugged in to USB and was watching Netflix. After 1 hour the battery only dropped 2%. I unplugged it and continued watching and it dropped another 15% after about 40 minutes.
[Kindle Fire Android Development] moriz1:
Keep in mind that the stock kindle fire can barely be charged by a computer's USB port. This is because the computer's USB port can only manage .5A. This is why the fire ships with a charger that does 1.7A.
[Kindle Fire Android Development] TechIsCool:
The reason the name was is changed was my fault I guess it was showing up in the amazon play store as amazon amazon kindle fire vs just amazon kindle fire and we both thought that it was because Hash had typed to name wrong so he changed to what you guys see now. It will get updated.
[Kindle Fire Android Development] southbird:
You're right; happens in Google's store too (see attachment.) Guess we'll have to take a silly looking name for the sake of compatibility.
[Kindle Fire Android Development] Hashcode:
I reverted the name change on github and fixed the 04-22 ROM build which was broken here:

http://rombot.droidhive.com/ROMs/otter/cm9
[Kindle Fire Android Development] SalsaForte:
You should have made a version change, even for this small fix: 4-22a or something like that.

It would be clearer. BTW, thanks for your kernel, I do really enjoy my KF.
[Kindle Fire Android Development] ma.da.ladla:
heat issue didn't subside

Sent From my Kindle Fire

Setup:Details are Below

Cm7 Barebones+Raven's Kernel

Minimum:300 Higher 1200mhz

Go launcher Ex With MIUI Theme

Games:MC3,Fifa 2012,Real Racing 2,Stick Cricket,Gangster Rio....

Apps:Mx Video Player,JetVid,Titanium Backup,Opera Mobile,Dolphin HD,Adobe Reader
[Kindle Fire Android Development] Jaimemex:
Same here the lower back of my kindle over heats pretty bad on wifi...
[Kindle Fire Android Development] Hashcode:
I completely agree in theory.

The reality is that that some of the links are posted around the internet and people will continue to download the wrong ROM (not knowing there's an update).

So in this case, I tend to over-write the offending file.
[Kindle Fire Android Development] AlexDeGruven:
Been thinking about touch sensitivity quite a bit today as I've been demoing AOKP 33r2 and 34 to coworkers (who are still too chicken to do this to their Fires).

I've noticed that touching works perfectly if you just barely make contact with the screen, rather than the normal 'push' action that we're used to with touch screens. A quick tap also seems to have the same effect.

I get the most errant scrolling when I try and push like there's an actual button there.

This leads me to believe that one of two things might be going on:

1. The polling interval for the digitizer might be set too fast, and is reading a push multiple times (initial contact, then the wider contact patch of a full-on press).

2. The software that determines whether a touch action is a touch or slide is tuned too sensitive and is reading the wider contact patch as a movement.

These could also be the same thing, just two sides of the same symptom.