yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Android Development] piotr.pot:
Hello,

Thanks again for your great work Hash. Kernel get better and better every build.

I've got question about charger driver fixing progress. I'm not asking about ETA, just to say few words. Should we look optimistic in future? Or it's looking worse that you think at beginning? Thanks in advance.
[Kindle Fire Android Development] sthomas38:
Looks like the new GPU driver makes 3D gaming a lot smoother. Got constant 55 FPS in the FPS part on my latest Quadrant, it was ~40 before, that's really nice.
[Kindle Fire Android Development] corlygunnz:
Running may 10 rom with new kernal and never had a problem of shutdown or anything. Great work......
[Kindle Fire Android Development] obsanity:
Can anyone confirm USB mass storage while in OS working on #11?
[Kindle Fire Android Development] harry_fine:
Still not working for me.
[Kindle Fire Android Development] mughalgxt:
USb file transfer leads to tab freeze and screen blacked out, requiring a force restart. This issue has been prevalent for quite a while accross all the updates i believe HAshcode hasn't noticed. It usually occurs while transferring big files > 1 GB with screen suspended. Even the transfer rates are quite slow 1.3MBps compared to 2.6MBps on Factory firmware

Not Sure if its kernel related or Hashcode's CM9 Rom issue.
[Kindle Fire Android Development] ratchetandclankf:
Google actually got rid of mass storage in ICS. Now it's jut recognized as a portable device.

(Edit) looked at first post- didn't realize new kernel ready... flashing now.
[Kindle Fire Android Development] powerpoint45:
usb

usb mass storage works perfect for me as well as usb debugging in hellfire ICS.I dont know what yall are talkin bout.:cool:
[Kindle Fire Android Development] smirkis:
ums is rom specific. it works fine in the kernel.
[Kindle Fire Android Development] Hashcode:
For those having USB mounting issues in the OS, I'm going to assume Windows 7.

Try this (and I'm doing this from memory so bear with me)

- unplug the phone from the computer

- go to Device Manager

- right-click the first item (your computer name) and select something like "show hidden devices"

- that should now show "android phone" (or something like that)

- once expanded that category has a device: android composite something

- right-click on that item, and uninstall (but keep the driver)

Now plug back in the phone and you should see device installing

You should then have an extra drive listed, but it wont open until you enter the USB sharing screen and click on the button at the bottom to enable USB sharing.

Let me know if this helps.
[Kindle Fire Android Development] Hashcode:
This could be related to charger issues / bad timing for sleep attempts which is all kernel related. I know for sure that the USB speed is something that needs to get worked out. The kernel doesnt handle EHCI atm.
[Kindle Fire Android Development] Hashcode:
I have no doubt that I can eventually get the charger working. Its just how long it will take. Lately, I haven't had as much time on it due to Motorola ICS leaks for both the RAZR and the Droid 4, which are some of the phones that I support.
[Kindle Fire Android Development] tedr108:
Strange, but USB mass storage is working fine for me. Not sure what you mean by "OS," I just tested on a Win7 machine. Haven't tested it on my Ubuntu machine, yet.

I plugged my KF into the Win7 usb port and only got "USB debugging enabled" at first. So, I did Settings | Storage | (options -- 3 square dots upper right) | USB computer connection | Mass Storage (checked it). My KF then showed up in Explorer as a fully functioning drive letter after I clicked the "Turn on USB storage" button. Write speed for a copy of a 130MB file to KF was only 1.3 MB/second.

Never installed any drivers on my Win7 machine, by the way... And, I just installed the Full ROM from this thread yesterday.

Thanks for the nice ROM and kernel, Hashcode (and all the CM9 devs, of course).
[Kindle Fire Android Development] Thief777:
This is not the maximum possible speed, which is missing in the firmware!

In TWRP the write speed of 4.5mb\s
[Kindle Fire Android Development] harry_fine:
That's the problem for me and a lot of others who can't get USB mass storage working. There are no dots in the upper right corner. Everyone seems to ignore that in our posts. They used to be, about a month ago, earlier version of the ROM, and earlier version of the Kernel. I'm using AOKP from this thread: "[ROM][5/20/12] AOKP KF Edition Build 36".
[Kindle Fire Android Development] jmcoffey:
Most help published here will be for the rom the hash provides. As will most errors.
[Kindle Fire Android Development] Hashcode:
The current 3.0 kernel does not support EHCI (hi-speed USB) at the moment. It's part of the driver code shared between the charger / battery / USB interface which isn't working correctly.
[Kindle Fire Android Development] tedr108:
Shot in the dark here... Any possibility that the 3 square dots are there, but are the same color as the top bar, making them invisible? You can try going to Settings | Storage and then tapping about 1/4" from the right side of the screen at the very top (vertically, you should be lined up with the "Settings" header, which is on the far left).

Something like this happened to me on a custom rom once, so it's not as ridiculous as it may sound.
[Kindle Fire Android Development] corlygunnz:
In hash rom I have no problem with ums not working , it is slow tho...
[Kindle Fire Android Development] marty331:
Go to xdaTV and watch Adam Outlers pro tip number 2, QuickSSHhd will solve your issue no matter the ROM.
[Kindle Fire Android Development] afu1979:
VPN L2TP/IPSec PSK

I do not have an OpenVPN account. I tried a L2TP/IPSec PSK connection (which I tested successfully on my Euphoria 4.03 Vibrant) and it got further than the other.

D/mtpd (23106): Received SCCRP (remote_tunnel = 58586) -> Sending SCCCN
D/mtpd (23106): Received ACK -> Sending ICRQ (local_session = 4358)
I/mtpd (23106): Tunnel established
D/mtpd (23106): Received ICRP (remote_session = 3929) -> Sending ICCN
D/mtpd (23106): Received ACK
I/mtpd (23106): Session established
I/mtpd (23106): Creating PPPoX socket
F/mtpd (23106): Socket() Protocol not supported
I/LegacyVpnRunner( 171): Aborting
I/LegacyVpnRunner( 171): java.lang.IllegalStateException: mtpd is dead
I/LegacyVpnRunner( 171): at com.android.server.connectivity.Vpn$LegacyVpn
Runner.execute(Vpn.java:569)
I/LegacyVpnRunner( 171): at com.android.server.connectivity.Vpn$LegacyVpn
Runner.run(Vpn.java:447)[/PHP]

As always, thanks for all the great work on kernel. It is awesome.
[Kindle Fire Android Development] shahabk818:
I have this problem, please tell me if you have the same problem or you have solution, so almost every time i restart the device when it boots touch screen doesn't work! So I have to reset the kindle by holding power button 2 or 3 times to make it work

what should I do?
[Kindle Fire Android Development] GoSooners345:
I'm able to use ftp

My Slimmed Infuse Sent This
[Kindle Fire Android Development] incognico:
Just run AndroSensor and saw the ambient light sensor does not show up. Is it possible to make it work? Also I came across this: http://xdaforums.com/showthread.php?t=1398014 worth a look too.
[Kindle Fire Android Development] AlexDeGruven:
The current driver code for the sensor is (quite literally) crap. So much so that even Amazon pulled it quite early on.

If we're lucky, there's a 3.x source driver for the sensor that doesn't totally suck, and we'll be able to use it at a later date.
[Kindle Fire Android Development] smirkis:
I can't run snes emulator for some reason now. it just black screens then closes
[Kindle Fire Android Development] shahabk818:
can somebody please give me reply?
[Kindle Fire Android Development] jmcoffey:
Re-flash the full ROM. Not just the kernel.
[Kindle Fire Android Development] x0xhellx0x:
I'll get it added so it works I'll sand brother hash the code
[Kindle Fire Android Development] Dasanko:
Have you tried reinstalling it?

I have a similar issue with Opera whenever I flash a new ROM: restoring the backup from TB just makes it blackscreen and close, the only way to make it work is to uninstall and install again from Play Store.
[Kindle Fire Android Development] shahabk818:
I'm having this problem with all CM9 Roms
[Kindle Fire Android Development] isaiahhhhh:
Forgive me if this is an obvious question but is Hashcode including the new kernel builds in each new stock CM9 build he pushes or do we need to flash the kernel seperately?
[Kindle Fire Android Development] bitemeoftn:
The new kernel is in every build he puts up. No need to flash separately.
[Kindle Fire Android Development] Entropy512:
Same here.
[Kindle Fire Android Development] skrewie:
Hey

Have questions about the new GPU driver. I know that benchmarks program dosent say all, but i got lower score in both Antutu and Quadrant. So where are the new gpu driver faster ? or better ? :confused:

And once again give us 1.3-1.4 ghz ! :D
[Kindle Fire Android Development] AlexDeGruven:
Until everything is complete, benchmarks are less than useless. Even when things are complete, they're still not that useful aside from comparing like devices or like software builds.
[Kindle Fire Android Development] Entropy512:
I think UMS misbehaving may just be something specific to how it's done in ICS...

Strangely enough, his complaints are the same ones that people who use UMS on Samsung devices also have. (Transfers often failing when the screen turns off, utterly awful speeds when other interfaces like ADB and MTP work fine.)

I use ADB, no problems with the device interrupting transfers. Speed is slow, but as you mention, this is expected.
[Kindle Fire Android Development] Jaimemex:
Hows progress on mic input Hashcode?
[Kindle Fire Android Development] Solid-Dado:
Hi, I have a question Hash.

With the old kernel(2.36), my wi-fi worked fine, since I've updated at 3.0 version I'm having a trouble connecting my tablet to wireless. I know that I can solve this problem changing my router, but my doubt is:

My wi-fi worked with the old kernel, could this a problem with the newest wi-fi drivers? Is it possible toput the old version of the wi fi driver?

Thank you:)
[Kindle Fire Android Development] southbird:
That's a dangerous and probably impossible idea.

Did you try the fix-mac.sh script? Also, if moving from 2.6 to 3.0, did you clear just about every memory type (cache, stats, etc.)? Any leftovers could cause problems.
[Kindle Fire Android Development] mwcashmoney:
Battery Life

Battery life seems to be limited. It seems to be using a large amount after the screen timeout. Anyone else experiencing this?

I'm on the following aokp latest KF build.

http://xdaforums.com/showthread.php?t=1614004
[Kindle Fire Android Development] barrmulio:
we'll need to see your battery stats to help, but you should post in the aokp thread rather than here

as a quick tip, not sure if it's there in aokp, but on cm9 builds under wifi advanced settings make sure that Keep Wifi on during sleep is set to 'only when plugged in' - that stopped quite a bit of my battery drain
[Kindle Fire Android Development] Solid-Dado:
I'm sure that I cleared everything corretly, I've never heard the fix-Mac.sh script, can you explain ho do that?
[Kindle Fire Android Development] engenuine:
I just wanted to drop in and say Thank You! Hashcode for all of your hard work. People like me who bought Kindle Fire just because they knew it supported custom roms are truly grateful for your contribution. Thank you again!
[Kindle Fire Android Development] veeman:
^ There you go.

And if that doesn't work, try setting your Kindle to Static IP instead of DHCP.
[Kindle Fire Android Development] mwcashmoney:
Reply

Already tried that. 14% used on sys idle since last login. Went from 68% to 56% batt while it sat unused since earlier today. I can't go two days wifi off and only using the reader app with lowest brightness setting. Minimal apps installed. Even have Gmail checking; inbox at longest interval.
[Kindle Fire Android Development] All~G1:
Have you tried fixing permission and then doing a battery calibration cycle via recovery?
[Kindle Fire Android Development] koroshbhasabrain:
Hashcode, I just want to say a big thank you for all this work!

I've noticed that in your build.prop you named the device "Amazon Amazon Kindle Fire"

This might be way too early, but maybe if you're not busy for a while you could change the text in there. I've already done it for myself. Once again, thank you!

I have noticed, over normal use, that sometimes it takes a few presses of the power button to get it to wake up.
[Kindle Fire Android Development] pbailey212:
The screen wake up is a known bug, I'm sure its somewhere on his list of fixes. He is more worried about functionality fixes first
[Kindle Fire Android Development] artur0588:
That will be great update since we got skype working and calling (means call not ended unexpectedly when on other side accept the call) except of mic.
[Kindle Fire Android Development] lovejoy777:
if you change the name in build.prop and remove one of the amazons you will have issues with the play store, hash changed it a couple of builds back and people had issues so he changed it back again.
[Kindle Fire Android Development] southbird:
Correct. Amazon named their device "model" as "Amazon Kindle Fire", and the manufacturer is, again, Amazon. This wasn't noticeable in their stock firmware, and it looks goofy in this one. But if you "fix" the name, a lot of popular apps e.g. Netflix will not be available in the Play Store and even worse may refuse to start if you try to work around that when they do their own name comparison checks. So ... deal with it. :)
[Kindle Fire Android Development] mwcashmoney:
reply

Testing it out now, will report back.
[Kindle Fire Android Development] bennettg:
Hi!

with hash's rom/kernel, i can connect to what i think is an ad-hoc hotspot from my android phone (optimus v running inferior human organs rom: gingerbread) when it uses wpa-psk as the encryption. no app, just the stock wifi hotspot from the rom.

however, when i run the same phone with a different rom (quattrimus ics) and the wifi tether app (definately ad-hoc) , which uses wep, it doesn't work the same. the kf sees the ad-hoc hotspot, it will connect and state "optaining ip address" for a while, never connecting, and then disconnect and the process starts over.

i'm a noob, so i would appreciate any insight that you might have. is the KF unable to connect too wep wifi for some reason? is the first scenario (wpa-psk) not ad-hoc?

thanks in advance
[Kindle Fire Android Development] All~G1:
Cycle your battery by wiping the battery stats, let the KF drain till it shuts off, charge it to 100% while it's off..... Enjoy.
[Kindle Fire Android Development] uoY_redruM:
It powers up as soon as you plug it in...
[Kindle Fire Android Development] Tbbo514:
System UI fc when I apply cm9 themes :-\
[Kindle Fire Android Development] pinios:
Seems the same problem I had. Tryed everything but didn't connect. Had to go back to CM7
[Kindle Fire Android Development] King_Stannis:
I know Skype isn't working yet in this kernel but can someone tell me if the mic will work at all with it? I am running hellfire's Ics rom and I can't get even Google voice search to work with a mic that I just got. It is supposedly the right type, too, with three black bands. Any help would be most appreciated.
[Kindle Fire Android Development] southbird:
Known issue, doesn't work currently in this kernel.

http://xdaforums.com/showpost.php?p=25228425&postcount=577

In the future, you should use the "Search This Thread" feature to look up issues first before posting about them. I found the above in about 30 seconds searching just for "mic".
[Kindle Fire Android Development] webstas:
Bluetooth

I tried to get my kindle to recognize my Asus BT211 via OTG, i can see it via lsusb it shows up it shows up but it wont initialize in settings. is there a list of drivers that were compiled in this kernel? if so does anyone know if the atheros generic driver was included?

(Side note)

has anyone had any luck with a BT Dongle? if so what model/brand
[Kindle Fire Android Development] mwcashmoney:
Update

I did a full recalibration. Up time battery life is a lot better. Still using way too much juice when it's idle. Went down 10% while off and at work today. Stock the KF could be left for days without any juice trickle. Anyone else notice this?

Again I'm on aokp kang latest build, wifi off when screen off, no Widgets, no weather, email refresh at latest intervals and lowest possible brightness setting,
[Kindle Fire Android Development] southbird:
As of yet, there hasn't been a Bluetooth adapter that works. I don't know for sure what BT drivers Hash has included, but I downloaded his kernel source from git after the previous release and it seemed like various components of BT were not enabled. But having said that, I'm no kernel expert, and I don't really know what parts are needed, and I suspect that the problem is more to do with Android than the kernel.

Also, it's more important that you look at dmesg after connecting a USB device to see if it recognizes it properly and gives it a device entry; if it does not add a device entry then the driver support is missing. lsusb will show all connected devices regardless if the kernel has loaded a driver for them.
[Kindle Fire Android Development] nursereese:
I had terrible battery life until I reinstalled with an sdcard memory wipe. Since doing that my battery life has been better. It used about 10% sitting unused for 16hrs+
[Kindle Fire Android Development] linktohack:
That's a good rate at the moment. Mine is about one to two percent per hour (idle though).

Gửi từ Kindle Lửa của tôi qua Tapatalk 2
[Kindle Fire Android Development] powerpoint45:
just tested out your rom. its great. love the boot animation :)
[Kindle Fire Android Development] webstas:
it doesn't look its recognized, it stating "<3>[23866.111083] usb 1-1.4.3: device v0cf3 p3000 is not supported" v0cf3 p3000 being the hardware id if thats correct.

i attached the full dump
[Kindle Fire Android Development] southbird:
The weird thing about the "not supported" message is that it seems to show up for every device; note your earlier dmesg entries for keyboard and mouse. It says "not supported" but device ("/dev/...") paths are assigned anyway (which is the most important part.) (Can anyone explain that behavior? It's confusing... guessing it's not referring to the kernel lacking a driver?) In any case, definitely looks like a driver is not available for your adapter.
[Kindle Fire Android Development] AluminumHaste:
I can report 2 more kindles on this ROM that USB Mass Storage fails trying to copy anything over 1 GB. For now, mounting in recovery works fine.
[Kindle Fire Android Development] powerpoint45:
I just got his rom yesterday and I re-setup adb. I can't even mount USB storage to my computer. The USB debugging icon comes up on my fire but no USB storage icon. Anyone else have this problem?Anyone know how to fix it?
[Kindle Fire Android Development] twa_priv:
Setting -> Storage -> Click on the 3 dots in the upper right corner -> Usb compute connection -> Check mass storage

Next time please post questions like this in the user discussion thread in the general forum.
[Kindle Fire Android Development] powerpoint45:
Sorry,I thought it was a rom issue. I will keep that in mind next time I post.
[Kindle Fire Android Development] Hashcode:
I made some changes to the Kindle Fire code today, and will put together a new FULL ROM tomorrow sometime (it's getting late):

1. Cleaned up the Touch Screen driver

- It sends touchscreen data back to the OS per the 3.0.x touchscreen protocol spec (added a dummy pressure and touch width value and cleaned up the EV_SYN events). This means where we had been using a BOARD_HAS_LEGACY_TOUCHSCREEN setting it is now removed.

- Slowed the pace of the touchscreen events overall.

- Duplicate touchscreen events are now eliminated as per the 3.0.x kernel spec for touchscreen protocol. (e.g. holding your finger in the same spot on the screen doesn't send endless events back to the OS like it did before.)

- This requires a make clobber and full recompile

THIS NEEDS A LOT OF TESTING. LET ME KNOW WHAT YOU THINK. AND NO, I CAN'T ADD MORE TOUCHPOINTS W/O NEW FIRMWARE FOR THE TOUCH CONTROLLER.

2. Updated the WLAN driver to R5.00.18 (up from R5.00.5)

3. Cleaned up the charger code some more. This is part of my larger project to get the charger operating in a friendly way with the OS.

4. Added more configuration to the kernel to support PPTP and L2TP connections. I was only able to do some minor testing, but it was getting past the previous socket creation errors. This will need more testing once I can get a new build out.

5. I've removed the prebuilt files from the device/amazon/otter project and merged them back into the vendor/amazon/otter project which hasn't been used for a while now.

DEVS: update your local_manifest.xml files here:

https://github.com/KFire-Android/android_local_manifest/blob/ics/local_manifest.xml
[Kindle Fire Android Development] chykal:
Kernel Also?

Will this be made available as a stand alone kernel in a flashable zip? Very much looking forward to using this with AOKP B38. Thanks for the great work you do.
[Kindle Fire Android Development] southbird:
He probably will release a standalone kernel, but it's been stated many times before that using other ROMS (e.g. like AOKP) can lead to aberrant behavior that wouldn't happen under CM9. It's better to get the AOKP team to build a new AOKP with the new kernel source so everything is in sync. Basically if you load the new kernel and your touchscreen is shot, you'd be better off trying to get AOKP to fix it than complaining about it here. Only after AOKP has integrated the kernel with their build would it be best to report a kernel issue.
[Kindle Fire Android Development] drk.hd:
I just made a CM9 build with the latest changes, and it seems to be working rather well.

The only thing I've notices in these last few minutes is that the Electron Beam screen off animation is sideways compared to before; as if the tablet was landscape instead of portrait, no matter the orientation. Not a big deal, but still.
[Kindle Fire Android Development] shahabk818:
Can not wait:)

can you add full screen mod to AOPK?
[Kindle Fire Android Development] Hashcode:
Yeah, I noticed that screen-off animation was added in the last few days, and that it's sideways on our device. Whaddya do. Could submit a patch to change the orientation of it based on the width vs. height of the screen (e.g. use the edges of the bigger dimension to act as the flat lines which collapse towards the center).

Do you notice any difference in the touchscreen behavior?

FYI slight delay on the release: I'm testing a stand-alone kernel .zip package for side affects when used on a ROM that still may have the LEGACY_TOUCHSCREEN setting enabled. So stay tuned.
[Kindle Fire Android Development] twa_priv:
I'm always playing a few Temple Run games to see if something's off, but I haven't noticed any differences in regards to touchscreen behavior - all as good as before.

Thanks
[Kindle Fire Android Development] Hashcode:
Specifically, I used to get "double" clicks sometimes on a certain key when typing in an email or something where the touch spot was decent small and you're trying to type faster than normal.

For me at least, the double key phantom presses are gone. But in general the touch controller is almost too sensitive for the device. The screen is only 7" and the longer side of the touch controller senses almost 4000 different points. Compared to my phone which has a 4" screen and only detects 1024.

It's so detailed that it's nearly impossible to hold your finger still enough on the screen to get the touch controller to stop sending events to the OS. Where on my phone the detection is perfectly balanced with just enough to detect smooth movement but not overly detailed to cause "jerkyness".

IMHO, there's still room for improvement, but it'll take time to iron out the details.