yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Android Development] altitude909:
I've noticed that too, its crazy sensitive. It seems sometimes you dont even have to touch it.

Oh and btw:

HASHCODE FOR PRESIDENT. u rock

:p
[Kindle Fire Android Development] powerpoint45:
Does the touch screen driver mods help with battery life?
[Kindle Fire Android Development] southbird:
I don't know why it would ... a touch screen driver just alters the OS-to-touch hardware connection. At best there might be some tiny power savings from the OS not having to process a stream of messages, but I'm sure it's negliable. :P
[Kindle Fire Android Development] jcatt:
Hey Hash,

So after running the new kernel on the Simple CM9 Rom I can feel that the touchscreen is much smoother. I noticed that on the older kernel selecting text and moving the handles was very erratic. Since the new kernel it definitely seems smoother and less jumpy.

Thanks Again,

Jcatt
[Kindle Fire Android Development] Entropy512:
I've noticed that where I used to often have issues bringing up the notifications from the notification area, it seems MUCH more reliable now. Same for swiping away notifications to dismiss them.
[Kindle Fire Android Development] speedingcheetah:
Where is this new kernel mentioned in the posts above?...is this the May 26 kernel posted in the OP?
[Kindle Fire Android Development] AlexDeGruven:
When it's done, Hashcode will post it, update the OP, and reply to the thread. It will be dated either 6/7 or 6/8, depending on when the build finished.
[Kindle Fire Android Development] speedingcheetah:
O...well..I was confused by a lot of the roms having newer kernals than what was officially posted here...I understand now....thanks...
[Kindle Fire Android Development] Sblood86:
Source is on github. As Hashcode updates stuff the other ROM maintainers are building dynamically off the same source (at least in most cases) because of that they will have the updates (for that reason there is an inherent chance that new ROMs may have kernel related bugs yet to be listed).
[Kindle Fire Android Development] Hashcode:
06-08: KERNEL.ZIP #12 IS NOW READY HERE (FLASH IN RECOVERY): http://bit.ly/KPbDVm

md5sum: e7476ff785b2dfbdb062e1cc036c14ac

- Touchscreen driver changes (event optimization, ICS friendly)

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

- Cleaned up the charger code some more (part of on-going charger work)

- Added more support for PPTP and L2TP connections

- [NEW 06/08] Added CCMP support used in 802.11i for EAPOL/WPA2/IPSEC connections using 4-way handshakes (Will fix some users who can't connect to wifi at certain locations)

NOTE: I didn't do a full ROM this time as most of these changes are already in many of the ROMs out there. If there is a huge demand, I'll do one and add it to the OP and here.
[Kindle Fire Android Development] southbird:
So "BOARD_HAS_LEGACY_TOUCHSCREEN" was a flag in the kernel, not CM9?
[Kindle Fire Android Development] Hashcode:
No it's in CM9. But I tested and the touchscreen seems to work just fine with that still enabled.
[Kindle Fire Android Development] King_Stannis:
For the benefit of those of relatively new to the customized ROM scene does this simply mean to install the kernal zip from TWRP? No backups need to be made or anything like that? Just flash and go, correct?

And thanks again for helping make my Fire a device I had already sort of consigned to the forgotten pile of technological junk into an item I simply can't be without!
[Kindle Fire Android Development] webdroidmt:
It is generally wise to make a nandroid backup prior to flashing. Something can always go wrong and after all, the 3.0 kernel is still in a testing stage.

Mike T
[Kindle Fire Android Development] airmaxx23:
The new kernel installed without any issues and is running great so far. Thanks Hash.
[Kindle Fire Android Development] skmpowdjy:
I personally would like a full ROM, as I want my experience to be as stock-CM9 as possible and most of the other ROMs on here theme or modify CM9 somehow.
[Kindle Fire Android Development] tedr108:
You will probably like this ROM:

http://xdaforums.com/showthread.php?t=1662798
[Kindle Fire Android Development] speedingcheetah:
I have noticed that things don't look as sharp on the screen as they did in earlier builds...

I flashed AOKP build 38..text and everything was nice and sharp..flashed the updated kernal...things musshy and blurry a bit...

I also noticed this on CM9 roms like gedeROm etc.
[Kindle Fire Android Development] davall:
Can confirm this. Video is stuttering.
[Kindle Fire Android Development] southbird:
Try on stock CM9 -- use Hash's last 5/26 build if you have it, apply this kernel over it. Do this first to net out any possibility that it's just the ROM you're using, which is frequently an issue with separate kernels.
[Kindle Fire Android Development] sthomas38:
Running my latest internal CM9 build from today (repo synced two hours ago) and it's fine, nothing blurry.

EDIT: Video playing is fine too.
[Kindle Fire Android Development] twa_priv:
Same here ... no issues at all.
[Kindle Fire Android Development] Hashcode:
I would need quite a bit more detailed information to help on issues like this (screenshots in the case of graphical issues may help).

1. [davall] What ROM are you currently running and what build date?

2. What kernel does the affected ROM normally include? (Some of the ROMs out are already updated w/ this kernel)

3. Can you try wiping Dalvik Cache after flashing the kernel and seeing if that helps (though I can't think of any updated .jar/.apk files in this kernel .zip).

3. [speedingcheetah] gedeROM hasn't been updated for a few days and still has this issue? Other CM9 ROMs have this issue? Please be specific as you can.

4. Also feel free to PM me dmesg/logcat for items which you can trigger in the OS (edit them down to just that time frame please)
[Kindle Fire Android Development] speedingcheetah:
I have tried several of the most current roms....AOKP, gedeROM, CM9 based on SGT7.......

Its weird, I guess its just me.....been flashing back and forth, new kernel and org with roms...cant seem to notice a difference now....maybe i am just used to the super sharp OLED screen in my Samsung fassy...

I have deiced to stick with the newest built rom I can find here....CM9 based on SGT7 framework/settings [20120608] - Edge swipe navigation...built today....

Running that...videos play fine...using mx Player....thats the only player i use...

I still think the overall screen quality it a tad blurry....text and edges seemed sharper on stock rom....is there anyway to implement a sharpen filter or something along those lines to how the screen is drawn...? I know on there is an app for Galaxy s phones (Galaxy S Settings)that enables mDNIe Mode- Post processing...which makes the screen look amazing...but that may just be a Samsung thing...
[Kindle Fire Android Development] Daniel120201:
Thanks for the wifi fix in the latest kernel.
[Kindle Fire Android Development] str3tchb0y:
I am running NRGZ28 Energy rom (a slightly themed CM9 rom) and flashed this kernel. I did wipe Dalvik cache.

Booting: it took 3 boots to finally get to boot animation and then boot. Not sure what pushed it over. each time you could tell the screen was on (black with a slight backlight) but there was nothing happening. At first I thought something had happened to the boot ani but even leaving for a few minutes nothing. On the third hard reboot I got a normal boot.

Video: works flawless. No stutters or blur.

Touchscreen: Big big improvement. I have a couple of sketch apps (Drawsomething, Autocad's sketchbook) that before this kernel, if you drew slowly you would get a really wavy line even if you were using a ruler to draw a straight line but now the precision is much better. slow or fast draws a straight line.

So major props for this fix. Keep it up.
[Kindle Fire Android Development] ProfEngr:
Took me 1 hard reset with NRG's ROM to get into the OS. Wiped cache/dalvic right after flash. Rebooted from twrp. He's supposed to be releasing a fix 'soon' for the keyboard crash so maybe he'll have this kernel build included.

Sent from my TBolt with the XDA App using 1 opposable thumb
[Kindle Fire Android Development] airmaxx23:
Edit: Drawing slowly in a straight line at an angel (with a straight edge and a couple different styluses at the same speed) gives me very wavy lines. A straight horizontal or vertical line is fine but the closer to 45 degrees the worse it gets. Notice the straight areas that show up at almost the same interval. This is with 2 different apps. It could be ROM related, it happens with the last kernel as well but I'm using GedeROM.
[Kindle Fire Android Development] Hashcode:
Can you do this same test on the kernel previous to this one?
[Kindle Fire Android Development] airmaxx23:
I get the same results, if I can help in any way please let me know.
[Kindle Fire Android Development] veeman:
I'm using the previous kernel (#11) with gedeROM and drawing in Sketchbook Pro works fine.
[Kindle Fire Android Development] powerpoint45:
Hey how come you removed the rom link from the 26th? Is something wrong with it?
[Kindle Fire Android Development] ProfEngr:
Got the power off bug on the last shutdown. Forced it off, rebooted, and it worked properly the next time. Will let you know if it becomes more than a once-in-a-while thing. Thanks for all the hard work.

Sent from my TBolt with the XDA App using 1 opposable thumb
[Kindle Fire Android Development] YaKillaCJ:
Am able toWell hmm. I havent tested today kernel but can speak on the 1 right before. I upgraded it on GedeRom and it did make video stutter on the basics like flash and netflix. Before hand, it wouldnt at all. I believe Gede reverted the kernels video drivideo drivers because of it. Using the 5/26 kernel am able to play full 1080p mpeg/avi and 720p mkv with not so much as a stutter via my NAS streaming using Diceplayer. 720p wmv is possible but using MxPlayer.
[Kindle Fire Android Development] Hashcode:
Link didn't work. Rombot is down atm. The other 2 ROMs (vanilla and simple) are updated much more than mine ever was anyway.

I can re-upload it to goo.im or something later if people feel the need for it.
[Kindle Fire Android Development] powerpoint45:
Ok I was making sure that it didn't have any serious bugs or something because I was using that rom.
[Kindle Fire Android Development] andTab:
This definitely does NOT boot.

10-15 tries.

Installed the kernel 10+ times

No boot. Just hangs with a black screen for 15+ minutes

5/26 rom + 6/8 kernel
[Kindle Fire Android Development] powerpoint45:
Did you wipe cache or dalvic cache. If a factory reset does not work then you will probably need to reflash the rom
[Kindle Fire Android Development] kenikh:
Maybe it's just overzealous enthusiasm, but everything seems smoother now. I have the latest NRG ROM with this kernel flashed onto it and I am very please compared to the previous kernel.
[Kindle Fire Android Development] freefaling:
Could it be a bad download? Check the MD5.

I am on 5/26 rom as well. No issues for me. Installed just fine. Working just as fine.

Text selection used to be a jittery affair, it's much bettet now :thumbup:
[Kindle Fire Android Development] shahabk818:
works great can't wait for charger detector to work
[Kindle Fire Android Development] powerpoint45:
Works fine for me on simple cm9 rom using hashes latest kernel(amazing rom)

Edit-nevermind it still has a slight problem,but the orange light stays on as long as the screen is on
[Kindle Fire Android Development] Solid-Dado:
Hash you are a GOD, now my wi-fi works correctly, I don't know how to thank you, I'll m,ake a donation and drink a beer
[Kindle Fire Android Development] davall:
I'm on AOKP. 38 from Goo with intersects kernel from 06-02.

The video stuttering was during watching football with streaming on Zattoo via MX Player.

I will investigate more and report back.

By the way. Thanks for your hard work, Hashcode.
[Kindle Fire Android Development] airmaxx23:
Hashcode, If you need anything from me to help solve the "wavy line" issue please let me know.
[Kindle Fire Android Development] veeman:
Actually I just tested it again and I had just never noticed it before. I also have that issue.
[Kindle Fire Android Development] southbird:
Oh! Should probably make a note of that in the OP (link to the other thread where those are maintained.) I thought there was always a risk of issues of using ROMs not officially built by you due to possible driver function disparities or something along those lines.
[Kindle Fire Android Development] gtrider:
allowed my ics fire on an april kernel power all the way down.. now it's boot cycling on charge are the firefirefire screen... will it eventually pull enough charge from there? should i figureout where my amazon charger went ?
[Kindle Fire Android Development] Sblood86:
Find the amazon charger... And you realise fff1.4a is designed to specifically around resolving those errors?
[Kindle Fire Android Development] skmpowdjy:
Ah, don't know why I didn't see this before. Thanks!!

Haha-- nevermind about building a ROM every time, then d:
[Kindle Fire Android Development] Hashcode:
FYI: ROMBot links should be working again. Re-added the full ROM.zip for 05/26 to the OP.
[Kindle Fire Android Development] andTab:
I am pretty convinced at this point that there is a bug in the 5/26 rom:

Yes. I wipe cache and dalvik every time I flash and I always check the md5.

I resolved the issue by flashing the vanilla rom plus the new kernel. Booted up just fine on the first try and is running fine.
[Kindle Fire Android Development] King_Stannis:
Running the latest kernel on hellfire's ICS. So far no issues. I flashed it without incident, video runs fine. I notice a little change in the Touchscreen, it seems to work a little better than before.

If you can get the mic working my Kindle will be just about perfect. :-)
[Kindle Fire Android Development] incognico:
Latest kernel working good with AOKP 38.

But I have another issue and I don't know if it is related to the kernel, rom or my device: When for example exiting google chrome I can see the url bar (actually bright parts of the last app) very slightly on my homescreen and in other screens, for example settings. It seems that bright pixels get somehow stuck and still persist in some other menus. Another example is the Google Play icon appearing very slightly in other apps. Happens not on a 100% black background like trebuchet launcher. After some minutes it will go away. It is not related to the new kernel version, it was there before too. Have not used another kernel but this one since the last 3 releases so I can't really tell.
[Kindle Fire Android Development] jmcoffey:
Perhaps you have the brightness up too high??
[Kindle Fire Android Development] southbird:
Is it possible you were just downloading the 5/26 kernel and applying th 6/8 kernel over top of it? I made that stupid mistake last night on one of my KFs when I didn't realize the ROM link was gone. :P
[Kindle Fire Android Development] AlexDeGruven:
Trip report:

Removed SGS screen tuner and flashed the new kernel. So far, things are working really well.

Only minor thing I see at the moment is that there is a little bit of LCD sync issue right as everything comes online. I get a flash as the boot animation gets started up.

Otherwise, I haven't run into anything significant at all.

Looking forward to see how battery is.
[Kindle Fire Android Development] firered365:
I don't know if it is an issue from the kernel or the ROM. I am run SGT7 latest build and every time I uninstall an app, it sometimes restart. Any idea why it is doing this?
[Kindle Fire Android Development] twa_priv:
You really shouldn't be posting such issue in the kernel dev thread. Post it in the SGT7 thread - with exact details how you installed the rom (from which rom you came from, which wipes etc), how you uninstall the app(s) and what apps these are. It's not going to be an issue with either one because other people would have reported such problems.
[Kindle Fire Android Development] str3tchb0y:
After my previously overzealous comment that the jagged lines was fixed I tried with a little more diligence and I am still experiencing this effect. And yes this was happening with previous kernels.
[Kindle Fire Android Development] mdaa83:
Maybe it's related to your launcher. I have the same ROM (latest) and the latest kernel and this does not happen to me.
[Kindle Fire Android Development] pinios:
Great!!! with the new kernel now my wifi conection works!!!

Thank you Hash!!
[Kindle Fire Android Development] twa_priv:
Hey Hash,

This is a followup on the linaro compile issue I had (previously posted in the Vanialla thread):

I finally managed to compile the kernel successfully using the linaro toolchain (tested 4.7 and 4.7.1) using gcc 4.6.3 on Ubuntu 12.4:

You can have a look at the changes I needed to make here: https://github.com/loosethisskin/kernel_omap/commits/ics-linaro/

Please let me know what you think - given that I'm not a kernel dev and I haven't coded in C/C++ in a long time...

Next I'm going to try a full CM9 build (including kernel) and see how it goes...
[Kindle Fire Android Development] Hashcode:
What optimization level are you currently running?
[Kindle Fire Android Development] twa_priv:
None, I basically followed your build instructions from post#1

export TOOLCHAIN_DIR=/u01/dev/build_tools/linaro-4.7.1
export PATH=$TOOLCHAIN_DIR/bin:$PATH
export CCOMPILER="$TOOLCHAIN_DIR/bin/arm-eabi-"
make O=$OUTPUT_DIR ARCH=arm distclean
make O=$OUTPUT_DIR ARCH=arm CROSS_COMPILE=$CCOMPILER otter_android_defconfig
make -j 4 O=$OUTPUT_DIR ARCH=arm CROSS_COMPILE=$CCOMPILER
[Kindle Fire Android Development] Hashcode:
Ah. You wont see performance gains tho till you kick optimization level up to 2 or more.
[Kindle Fire Android Development] twa_priv:
First things first :) - a complete linaro build without errors.

You mean optimizations like this pending commit: http://review.cyanogenmod.com/#/c/17358/ ?

Any hints or things I should try out are very welcome.

Thanks
[Kindle Fire Android Development] Hashcode:
twa_priv: Yep, and I would expect to see more of those "Linaro optimization" commits coming in the future.

NOTE: I'm setting up automated builds for those that are interested on Rombot. But, it doesn't have the volume mod yet, so it's not quite as cool as it sounds. :/ Soon as I get my replacement device, I'll setup a patch for CM9 and hopefully merge in some kind of usable volume toggle/slider (unless someone else wants to).

http://rombot.droidhive.com/ROMs/otter/cm9/
[Kindle Fire Android Development] shahabk818:
Hashcode please reply!

I asked this question a few times nobody gave me a convincing answer, When I reboot my Kindle or even when sometimes it's on touchscreen stops working, I know Kindle's not freezing because the clock works.

I have to reboot my Kindle by holding the power button up to 3-4 times to get touch sensation working again.

Can you just tell me is this the kernel or my device? What should I do about it?

I tried all the cm9 roms doing factory reset ...:confused:
[Kindle Fire Android Development] kenikh:
Remove all doubt by flashing another ROM.
[Kindle Fire Android Development] southbird:
I hope you're not doing ONLY factory reset. You should always at least clear Cache and Dalvik Cache.

Also, just saying "it stops working!" doesn't help ... since you've lost touch screen, you can either try a USB keyboard/mouse, if so equipped, or connect a USB cable to the KF and run ADB to get data from "dmesg" and "logcat." If it's a kernel issue, it'll probably show up in dmesg. If it's a ROM issue, it'll probably show up in logcat. In any case, more data to assist, since Hash can't personally visit you and your issue appears to be a minority case.
[Kindle Fire Android Development] shahabk818:
I cleared everything! I didn't have this problem with CM7! Is there a chance that I should update/re-install TWRP to fix the issue?

I don't know how to get logcat I'm such a noob in this:D

So non of you guys have this problem? Is it just me?
[Kindle Fire Android Development] MayfairDROID:
It has happened to me a few times as well, but I just chalk it up to a dirty wake from sleep. I am having all kinds of bugs with this kernel, but nothing so major I felt the need to report it....again, I figure it has to do with my fear of wiping after moving to cwmd. I have lost adb, and fast boot, so notwrp for me
[Kindle Fire Android Development] wmc90:
In regards to the wavy lines people are experiencing; it's likely just a function of the cheap digitizer the Fire has. I would test to see if it still happens in CM7 and the original customized Gingerbread before we start trying to 'fix' it.

For reference I'm drawing my conclusions based upon what you can see from this test on other devices - http://www.electronista.com/articles/10/03/24/robot.test.shows.apple.htc.best.at.touch.accuracy/

EDIT: also in response to the post above, TWRP is totally safe with the latest FFF since it can just reset the bootmode through it's menu thingy
[Kindle Fire Android Development] tedr108:
You do realize the TWRP has a flashable .zip now, right? It is available on the TeamWin site. You do not need adb or fastboot to install it.

Nevermind: Wrong forum ... there does not seem to be a flashable .zip for the KF.
[Kindle Fire Android Development] yoosee:
WPA Enterprise couldn't be connected

I'm trying my KF with gedeROM v1.6 (kernel) to WPA Enterprise but not succeeded. It loops at "Obtaining IP address..." when I try to connect to network and finally stacked.

It looks like all Authentication succeeded. here's some log.

I/wpa_supplicant( 229): wlan0: CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully
I/wpa_supplicant( 229): wlan0: WPA: Key negotiation completed with 00:1b:53:a8:74:c0 [PTK=TKIP GTK=WEP-104]
I/wpa_supplicant( 229): wlan0: CTRL-EVENT-CONNECTED - Connection to 00:1b:53:a8:74:c0 completed (reauth) [id=0 id_str=]

I look at log and found following situation. after "DRIVER GETPOWER" called, it went to deauthentification and CTL-EVENT-DISCONNECT happened.

D/wpa_supplicant( 229): Writing configuration file '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 229): Configuration file '/data/misc/wifi/wpa_supplicant.conf' written successfully
D/wpa_supplicant( 229): CTRL_IFACE: SAVE_CONFIG - Configuration updated
D/wpa_supplicant( 229): ctrl_iface: DRIVER BTCOEXMODE 1
D/wpa_supplicant( 229): ctrl_iface: DRIVER GETPOWER
D/wpa_supplicant( 229): nl80211: Event message available
D/wpa_supplicant( 229): nl80211: Delete station 00:1b:53:a8:74:c0
D/wpa_supplicant( 229): nl80211: Event message available
D/wpa_supplicant( 229): nl80211: MLME event 39
D/wpa_supplicant( 229): Event 12 received on interface wlan0
D/wpa_supplicant( 229): Deauthentication notification
D/wpa_supplicant( 229): * reason 23
D/wpa_supplicant( 229): * address 00:1b:53:a8:74:c0
D/wpa_supplicant( 229): WPA: Auto connect enabled: try to reconnect (wps=0)
D/wpa_supplicant( 229): Setting scan request: 0 sec 500000 usec
D/wpa_supplicant( 229): Added BSSID 00:1b:53:a8:74:c0 into blacklist
D/wpa_supplicant( 229): Setting scan request: 0 sec 100000 usec
I/wpa_supplicant( 229): wlan0: CTRL-EVENT-DISCONNECTED bssid=00:1b:53:a8:74:c0 reason=23

Is that something wrong with nl80211 driver, or wpa_supplicant or something else? I appreciate if someone can help to investigate that.
[Kindle Fire Android Development] southbird:
It appears it might be a wpasupplicant bug or possibly an openssl bug, and the whole reason 23 business is not unique whatsoever to our domain.

E.g.: https://bugs.launchpad.net/ubuntu/+source/wpasupplicant/+bug/969343 (see #26 and #49)

In any case, a recent and current issue in most Linux-related places.
[Kindle Fire Android Development] Entropy512:
As far as wiping after moving to CWM:

1) Try updating CWM to the test build Hashcode posted maybe 2/3 through the thread

2) Try this:

cat /sys/class/block/mmcblk0/device/name

If it's M8G2FA, absolutely make sure you're on a "fixed" CWM before wiping (actually, that reminds me, I need to pull-request another safety measure to Hashcode)

If it's MMC08G there's a good chance even the original CWM will be safe for you.