yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Android Development] Hashcode:
I have source for a linux mainline v3.3 Ilitek Touchscreen driver and as soon as things slow down I'm probably going to implement it for 2 reasons:

- The code is more generic and easier to upgrade for the future

- It's an ICS compatible touchscreen driver (where the current is more Gingerbread compatible and we use additional settings to make it work)

Once that's in-place I can work with a group of testers to craft the "perfect" settings for our device. Going to be a bit tho. :/
[Kindle Fire Android Development] vbdss:
Hash if you are going to work on the driver, you will implement the multitouch too?
[Kindle Fire Android Development] ma.da.ladla:
i second that

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] dnathan13:
Last I heard it had been decided the kindle couldn't do more than two touches due to hardware issues so I don't think the drive will help. Feel free to correct me if I am wrong
[Kindle Fire Android Development] southbird:
The difference is between a "driver" and "firmware" -- the touchscreen hardware has firmware which only supplies a two-point touch. The "driver" is merely what interfaces the hardware with the operating system. The driver might interact with the hardware better, but it will not alter its core capability as a new firmware would. AFAIK we don't have access to the touchscreen firmware so at this point it's a solid "no" going forward.
[Kindle Fire Android Development] Hashcode:
^^^ this. Thank you for the great explanation.
[Kindle Fire Android Development] SalsaForte:
Good point! I didn't thought about that.
[Kindle Fire Android Development] EVOlvedAndroid:
My kindle is dead and whenever I try to charge it, It boots to bootloader for a second shuts off and repeats over and over and over. If you can help PLEASE REPLY.

Using this kernel with AOKP
[Kindle Fire Android Development] mlpmail:
Are you using he AC adapter? Once the battery gets discharged too far the only way to get the device recharged is to use AC adapter. USB won't put out enough current to boot far enough to start charging. This is a Kindle issue not caused by this kernel.
[Kindle Fire Android Development] backspacepc:
The AC adapter puts out 1000 mV where as USB only puts out 100. If the AC adapter doesn't work then you might have a hardware issue. I would suggest leaving it plugged into AC for at least 10 mins before attempting to power it back up. If that doesn't work then you may have damaged the battery which is very unlikely.
[Kindle Fire Android Development] HaiKaiDo:
Yeah Ive had this happen to me before. It actually happened to me the day i got the device cause iw as messing with it so much. Just plug it into the wall and make sure it is indeed not trying to turn on and walk away for an hour. That should fix it.
[Kindle Fire Android Development] EVOlvedAndroid:
Ok, now I have to find the AC Adapter.
[Kindle Fire Android Development] Techlyfe:
Agreed, although USB 2.0 can put out up to 500 mA it's just that the kindle itself can use well over that 500 mA just with the screen on lowest setting and sitting on a home screen. And usb 3.0 can put out up to 900 mA. But yes, just plug it to the OEM wall plug. Some aftermarket plugs cant produce the necessary power.
[Kindle Fire Android Development] mlpmail:
The trouble is when it is dead just plugging in the power causes it to boot before it will charge, it runs out of power and the whole thing starts over. Thats is why you need the added current available with the stock charger just to get it working again. I don't know if USB 3.0 provides enough.
[Kindle Fire Android Development] Jaimemex:
Is overheating still a known issue? The lower back of my kindle fire still overheats when wifi is on and when charging....
[Kindle Fire Android Development] erikiksaz:
You need to differentiate overheating from warm to the touch.

Find yourself a G2x, plug in a mini HDMI plug, and that my friend, is what real "overheating" is, granted you had one of the faulty g2x. It would get so hot you wouldn't be able to hold it against your face, let alone the fear that the damn battery would explode.
[Kindle Fire Android Development] RebelebeR:
My KF stays plugged in to the charger and wifi connected all of the time when I am home. It's never even gotten warm to the touch. I have a battery app that also gives the temperature of the battery. Assuming it is correct the battery has never gotten any warmer than 98 degrees. This being said, I don't imagine anything on my KF has gotten more than a few degrees higher than that.
[Kindle Fire Android Development] Jaimemex:
Are u running the latest version of the kernel? #7? Because my kindle has gotten very hot to the point I feared it mite cause screen damage...maybe I'll try a clean install again or going back 2 stock then flashing back to CM9 to see if that will help...:confused:
[Kindle Fire Android Development] animefun135:
About HD video in HW decoder...

it seems that when playing videos on HW sometimes frames per second reduced to 17 frames ... If you watch a third-party player like BS Player and use setup "System video decoder" that are visible decrease in fps. If you put in the same setting for "BS Player Engine" fps is always at 23-24.
[Kindle Fire Android Development] astmario:
Same for MP4 and MKV containers? Other video player programs?

That is played from device, I assume that LAN playback is still software mode only?

EDIT Mod's should move this post to general thread so we do not clog here.
[Kindle Fire Android Development] animefun135:
yes container does't metter. Videos played from device using HW decoder.
[Kindle Fire Android Development] walts:
{Deleted - wrong thread. Sorry}
[Kindle Fire Android Development] alan110112:
(Not completely) OT: Hashcode, I think will be useful to put a volume control in clock menu of your rom, like the one in first ics rom for kindle fire... if it is possible.
[Kindle Fire Android Development] sthomas38:
Yeah that's true. Or a button to pop-up the volume panel in the status bar would be awesome! :D

Keep up the great work :).
[Kindle Fire Android Development] Sblood86:
Both the volume and brightness controls are part of the custom UI framework we were using, that same framework repo is the one that was causing peoples recent build issues; subsequently Hashcode said he would be removing said framework (to avoid CM sync/build issues) until the kernel was more stable (one possible reason for this would be that someone has to update the framework repo with CM changes anytime they change something in another repo which requires framework changes)... In other words I expect we will have the volume and brightness controls back in the not

too

distant future.
[Kindle Fire Android Development] Hashcode:
As a matter of fact they will be in the next build that I do.

I was originally trying to find an elegant way of adding the volume slider without customizing the frameworks code, but I was pointed to a gerrit review where the volume will be added to the notification area in the not too distant future (hopefully).

So I have my local framework patched for now.
[Kindle Fire Android Development] sthomas38:
You're the man ;).

Envoyé depuis mon Amazon Kindle Fire avec Tapatalk
[Kindle Fire Android Development] twa_priv:
Are you going to push these changes to your github (maybe just by creating a test branch)?

Edit: Nevermind. To remove bluetooth/wifi and add the volume slider to the status bar I cloned your android_frameworks_base repo, merged in the latest CM changes and compiled. Works like a charm.
[Kindle Fire Android Development] smirkis:
gedemis addded it to his build, not sure if he did it your way but it works. he also over clocked your kernel which feels great at 1.2ghz!
[Kindle Fire Android Development] leviwhite9:
Will this not work in CWM? :confused:
[Kindle Fire Android Development] bi2o:
Great news! I was waiting for that.

While you are at it, I have a suggestion.

If you get rid of the airplane mode switch (how many times do u take the airplane per year? )

And remove the Bluetooth switch (it is not usable anyway)

This way u create enough vertical space to add the volume slider without having to scroll down to reach the settings. Everything will be reachable on the same screen without flickering up and down.

What do u think?

All the best Hash. Ur the man.
[Kindle Fire Android Development] kjwalker:
CWM has issues with flashing 3.0 kernels. Use TWRP.
[Kindle Fire Android Development] smirkis:
copied fr4nklin and put gedemis kernel and systemui and I'm at home for now lol. ums works on your build hash
[Kindle Fire Android Development] dnd61:
How about the touch screen? I think it has bit issue with register
[Kindle Fire Android Development] Hashcode:
Next build will also include a 1.2ghz kernel where the 1008 and below settings all have stock undervolt settings. The default max will be 1008. So it will be a personal preference which speed each user chooses (settable via the performance menu).

Other news includes:

- I have a new clockwork recovery (5.5.0.4 on the 3.0 kernel) modded with soft keys (based on gweedo747's git) that I've fixed for flashing both 2.6 and 3.0 kernels/ROMs.

Right now, I'm troubleshooting issues like "reboot recovery" and making sure it's completely RomManager compatible.

- Also, I'm making the necessary changes to the CM ROM build so that the kernel and all of the modules are built dynamically and packaged correctly. (This will be required for official nightlies).
[Kindle Fire Android Development] smirkis:
I think the reboot recovery issue is rommanager related. it calls for reboot-bootloader which isn't proper for our device unless u hot fix that in the ramdisk of the rom some how
[Kindle Fire Android Development] vbdss:
Hashcode any updates on the kernel?
[Kindle Fire Android Development] acax456:
Dont ask for eta please
[Kindle Fire Android Development] pbailey212:
Just skip using rom manager all together. That garbage has created more bricks then the great wall of china. Stick with the device spacific instructions posted by our trusted devs
[Kindle Fire Android Development] vbdss:
Sorry, didnt saw that i was asking for ETAs, i thought that i was asking for updates on the kernel features and bugs.
[Kindle Fire Android Development] 50CalPotato:
Well, technically, bricks were used for the Great Wall's construction; the wall was not in any manner a monstrously large brick synthesizing apparatus.
[Kindle Fire Android Development] kernelsandirs:
haha I really LOL, that is funny.
[Kindle Fire Android Development] sigporsson:
me too!

I play the same 480P MP4 video with MX Player 1.6C HW decoder on both stock rom 6.3 and Hash's rom.

Stock rom goes well, but hash's rom gets a small lag sometimes...
[Kindle Fire Android Development] Tiffany84:
Just wanted to take a minute to give u thanks and praise. U have taken a good tablet and made it GREAT!! I'm still amazed every time I use my Kindle how much of a difference hwa has had on it. I knew it would help but had no idea how much. I've owned several tablets and all have cost a lot more than the Kindle but with your kernel the Kindle is just as fast and smooth IMO as any other tablet I've used in the past. So thanks again for all you've done and continue to do for all of us. I'm really broke right now lol but as soon as I have some extra cash its definitely coming your way;)

Sent from my SPH-D710 using Xparent ICS Blue Tapatalk 2
[Kindle Fire Android Development] icemank121:
The next version of the kernel has some framebuffer changes that could help HD playback. Make sure to retest your videos once it is released.
[Kindle Fire Android Development] dnathan13:
If you want updates on the kernel read the thread... hash updates consistently and you asking just buries those even more. I realize I just added to the problem, but hopefully in the future you will remember this. Or you could always post in the thread in the general section that is specifically for questions like the one you asked.
[Kindle Fire Android Development] portezbie:
Sorry to go off topic, but I had no idea bsplayer had an android version, sweet! This is what I use on my home pc.
[Kindle Fire Android Development] icemank121:
I thought I'd post some info about the HW acceleration to help people out.

I tested a ton of files with 2 different players, BSPlayer and MX Player.

The main difference between the 2 players is that MX Player uses the Android video playback engine, and BSPlayer has it's own engine. This matters because the Android video engine doesn't by default have support for several popular video containers (MOV and AVI) and BSPlayer using their engine does support those formats. The other great thing about BSPlayer is that even when using their engine, you can still use HW acceleration, while adding support for a lot of file formats.

The result, means BSPlayer can play alot more videos than MX Player while still using HW acceleration. I played 720p and 1080p trailers downloaded directly from Apple Trailers (MOV) and they worked great with HW acceleration. Also since BSPlayer supports AVI containers, DivX/XviD actually works with HWA as well.

To make sure BSPlayer is working correctly, make sure that "Decoding mode" in BSPlayer is set to "Hardware decoding mode (BSPlayer engine)" which lets you play all formats such as MOV and AVI, while retaining hardware acceleration. I believe this is the default setting, but I wanted to post this in case anyone has changed it.

Conclusion: BSPlayer lets you use HWA and and supports a ton of file formats at the same time, versus using the built-in Android video player or players that use it and just add a few more features (MX Player). BSPlayer is definitely the player that has the most HWA capability on the Kindle Fire.
[Kindle Fire Android Development] x0xhellx0x:
Harsh this is butter hellfirekindle sandwich 1.2 beta with your kernel made my rom perfect ty bud
[Kindle Fire Android Development] Thepooch:
Your kernel is making all these roms rock hashcode your the man getting HWA going is a massive obstacle well done:-) :-) :-) :-)
[Kindle Fire Android Development] foxdog66:
did i read somewhere that hashcode has a clockwork port that works with the 3.0 kernel/his rom? Id love to try this so if anyone knows where its at, please let me know. im getting really tired of having to edit/create my own updater scripts within installable zips.
[Kindle Fire Android Development] dnathan13:
Not released. You would know if it was out there will be an announcement and everyone will be talking about it.
[Kindle Fire Android Development] bennettg:
OTG errors

Maybe you or someone could help me. I purchased the following USB OTG cable from Amazon.com

http://www.amazon.com/gp/product/B00...ls_o02_s00_i00

per the instructions in this thread, i 1st plugged in the host cable and then the usb mouse and restarted. when my kf restarted, it seemed to see the usb mouse as a usb mass storage device. it did not work. i tried the same directions with a usb keyboard and it also failed.

Is there any setting I need to change for OTG to work?

-android debugging is checked

-root access is for apps only

-usb computer connection: mass storage (enable usb mass storage) i selected.

is there some part of the kernel that i need to load? I'm on hashcode's ROM/kernel 4/22 #7

Or maybe the cable is not wokring?

I'm desperate. please help this silly nOOb.

thanks in advance.
[Kindle Fire Android Development] d33dvb:
I hate to even say this, but guys, in GENERAL section there is a 3.0 kernel USER thread, people are waiting patiently to help you there. In here, you better have some code to contribute, or YOU are the reason for the slow releases. The fixes the dev's come up here are posted here, and when they have to poll through mass amounts of BS it slows them down. SO PLEASE READ, AND DONT POST HERE.
[Kindle Fire Android Development] Hashcode:
KERNEL.ZIP #8 IS NOW READY HERE (FLASH IN RECOVERY): http://bit.ly/Iz9J4s

CHANGES:

- Kernel now has the 1.2ghz setting added again, but is default to 1.0ghz. To enable the higher clock speed, go into Settings -> Performance -> Processor and change "Maximum CPU frequency" to 1200. Then select "Set on boot".

- Added bluetooth USB support modules to the kernel for OTG testing

- Fixed early backlight bug. All of the bootanimation should now be visible.

[DEVS] The kernel is now compiled as a part of the "brunch otter" process. Modules and kernel will be added to the build automatically. Update your local_manifest.xml here: https://raw.github.com/KFire-Android/android_local_manifest/ics/local_manifest.xml

NOTES: I know this update might seem a bit disappointing. But, work has been VERY busy for me atm. I am still working on the charger code and I have a CWRecovery 5.5.0.4 modified with touch controls in testing. But, I'm still working out "reboot recovery" handling from ROM and the recovery doesn't power off entirely (similar to the ROM). So.. more bugs to fix before it's release ready.

Tomorrow when I get more time, I'll do an updated full CM9 ROM with this kernel + the volume slider in the notification area.
[Kindle Fire Android Development] walts:
+1

There's a reason for having two threads. By all means read them both, but post in the appropriate section, and don't cross-post unless what you have to say is vital to both threads. It makes life better for everyone if we all follow the same rules :)

Walt
[Kindle Fire Android Development] sigporsson:
Great Work!!!

OTG USB flash disk work!

Buybox + USB Storage Manager or Stick Mount can do this, but Stick Mount can't display chinese charactor.

PS: Hash, do you change the script for fixxing mac address? My KF' mac has been changed again......
[Kindle Fire Android Development] isfisherman:
Hashcode released a new ROM...:)
[Kindle Fire Android Development] seishuku:
He's probably using a powered hub, for some reason usb2 devices are requesting too much power.
[Kindle Fire Android Development] paxChristos:
This thread is intended for development related posts, not for support. Support related posts MUST be placed in the support thread in the general forum. Any future posts asking for help in this thread will be deleted.

Pax

FSM Amazon Kindle Fire
[Kindle Fire Android Development] umash4:
Sorry, not working me. Simply says Application not installed. Tried even rebuilding from (reverse engineered) source to address the signing issue. adb install gives a variety of parse errors.
[Kindle Fire Android Development] jmcoffey:
You don't install it. You have to manually replace it and reboot.
[Kindle Fire Android Development] Stevethegreat:
Also more advanced overclocks for those of us lucky enough to handle them (I.e. my KF handles 1.4ghz on the cpu and 384mhz on the gpu). Practically turning my omap 4430 to omap 4460 :D

And yes I know this is the development thread but since I'm inquiring about an extra function (instead of mere user experience) I think here is the place to post...
[Kindle Fire Android Development] southbird:
Not an excuse. For future reference, at the top of the thread is a "Search this thread" button. I use it all the time, it's good for referencing information.
[Kindle Fire Android Development] seishuku:
Hey Hash, what's your exact procedure for building the sgx and wlan modules? I'm making some custom changes to my kernel and it's enough for the sgx mod to fail loading.

I seem to be missing something, the INSTALL says to set KERNELDIR and do "make DEBUG all", or something like that, but there isn't a Makefile... So I'm kinda confused as to how that's supposed to work.

I don't need the whole Android build tree, do I?
[Kindle Fire Android Development] Hashcode:
The easiest way now is to build android, but if you'd like I'll review my pvr/sgx instructions to make sure they are still accurate.

(I know you probably already know this, but be sure the kernel compiles fully before using the SGX make instructions.)
[Kindle Fire Android Development] seishuku:
Ok.

Yeah, the kernel builds and boots fine, just no display and a kernel message of sgx version not matching (or something along those lines).

Maybe some time tonight I'll break down and set up an android build env, but I don't really want to unless I have to... Especially if I only need to change the kernel and nothing else. lol
[Kindle Fire Android Development] Hashcode:
I hear ya. I'll walk back through my notes.
[Kindle Fire Android Development] seishuku:
Ok, i got it built, had to edit a few mk files though... must be something about my slackware build.

Thanks!
[Kindle Fire Android Development] Hashcode:
Awesome. If you'd like, send me the edits you needed to make, and as other devs jump into the fray, I can keep track of various compile "issues" using different build systems.
[Kindle Fire Android Development] seishuku:
One was an edit to the top level make file, to set the right cross compiler... though maybe that was just an env var set wrong.

The other is in commands.mk, for the dos to Unix text file converter, for whatever reason it didn't pick up on dos2unix on my system.

Oh, also the reason its rejecting usb2 devices that take too much power, is because the port can only supply 100mA and the device wants 100mA, but the USB core doubles the current requirement for devices with bad descriptors that have incorrect mA descriptions.

I still haven't got to the bottom of the descriptor read fail though. It only seems to happen with my bluetooth usb adapter, which maybe because it's a cheap-o $1 HK adapter. lol

Edit-

If you edit devices/usb/core/generic.c

Remove the '*2' on the 'if (c->desc.bMaxPower...' line, USB flash drives will work with out a powered hub.

Edit-

It also seems that one of my flash drives work, the 2gb. Both the 4GB sticks fail.
[Kindle Fire Android Development] csholmq:
Works like a charm! Away with the bluetooth setting and welcome audio slider!

Though the battery stats look like crap imo. I'll see if I can live with that :)
[Kindle Fire Android Development] Hashcode:
I have a new full ROM build which includes the #8 kernel and the volume mod up on rombot here:

http://rombot.droidhive.com/ROMs/otter/cm9/

Note that this was more of a test than anything, to see how an automated build would look.

I'm still working on the kernel, etc.
[Kindle Fire Android Development] FlyRyan:
Does this take a long time to boot for the first time?

I've tried flashing it over my JackpotCalvin ICS build and installing Hashcode's ROM with it built in and I have been on the opening animation for like 10 minutes.
[Kindle Fire Android Development] Hashcode:
Couple items to check:

- Flash in TWRP

- You will need to wipe when moving from any non CyanogenMode/3.0 kernel based ROM, can restore apps via Titanium Backup

1st boot is about a minute at the max. (Probably less)
[Kindle Fire Android Development] FlyRyan:
I seem to have it working. I just redownloaded the kernel and flashed it again and all seems well as far as booting. However, I can only get WiFi to work in your CM9 version. Wifi will not toggle on in the other ROM (which is also CM9 based). Any ideas?
[Kindle Fire Android Development] Hashcode:
Hard to tell. I make sure every build has recompiled modules.. or possibly some difference in wpa_supplicant? For this build, I made 2 edits in systemui tabletstatusbar and added the volume pngs. Everything else is straight from github.
[Kindle Fire Android Development] BrooksBlood:
Could just be from hardware damage, but I seem to be getting really bad "ghost images" on my screen on your new rom with the kernel integrated in. Trying to turn the brightness down to see if that effected it.
[Kindle Fire Android Development] Hashcode:
Is there a way you could put up an image? I wouldn't immediately jump to hardware damage when using a brand new kernel.

Have you seen the ghosting on other ROMs? Or you could try flashing back to stock even.