yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Android Development] sionicion:
Hey guys, just curious what is holding hardware video decoding back. I KNOW it isn't here and is coming but what is so hard about getting it working when there is all these kernel improvements and such throughout the thread? Is it just being ignored? Left to some long day off from work? Is it continually being worked on?

Also, I know it is hardware video decoding that is absent, but like someone else asked earlier, does this affect hardware acceleration in general? The touchscreen is just so off...I can't tap on a link or do anything, it thinks I'm scrolling ever so slightly when I'm trying to tap on a link like a billion times, hard press, soft presses, eventually I get lucky... Get it a lot in the browser.

Also, regarding the SD card issues, and the tablet app issues...Real Racing 2 doesn't work for me, it can't download the additional 500-600 megabytes, stays at 0%. I have to up the DPI to 240, then it will download the game. But I believe it is downloading phone quality graphics...

I can bounce back to 160 DPI and it will continue working. It's just odd that it can't download the game with 160 DPI and I don't know if that is regarding the size of the files and the SD card having issues versus phone graphics being less in size or what...I'm not quite sure. I haven't even played Real Racing 2 with a CM7 or stock ROM, so I don't have anything to compare to. From what I heard, it download the game without issue, it is the ICS rom that it has trouble with and needs the DPI fix. For more info check this thread http://xdaforums.com/showthread.php?t=1410604&page=2 and my own thread about this http://xdaforums.com/showthread.php?t=1481107 . If anybody has a possible solution, I'd be happy to try it and see. Or if you got it working without issue on ICS, tell me what ROM you have.

Other than that, great work guys! Keep it up. :)
[Kindle Fire Android Development] CodenameDeadpool:
I am downloading the best/most stable build of this ROM?

I wasn't sure which build to flash but I'm currently downloading:

2012-02-02 cm9_02_02.zip

based on VideoTouch1-29.zip

+ USB mounting

406fbefeb573e5e92e041c6da4e72345 by nind

(Sounded like the best version to me....)
[Kindle Fire Android Development] awadewitz:
Yea I have question....Who is doing what rom????

Could you please state the DEV and pluses
[Kindle Fire Android Development] CodenameDeadpool:
Here goes nothing... Flashing it, now.

Been wanting to check ICS out.
[Kindle Fire Android Development] csholmq:
Hashcode and JackpotClavin are the two main devs who are doing all the grunt work. However, there are other good people who are taking their time and making builds and posting it to the thread. Those builds are directly from this threads github.

Then there are about three different kernels being included. It's the "stock" (which is kinda messed up), it's the one by IntersectRaven (which is more performance targeted, built upon the stock) and then there's Hashcodes, which is cleaned up from scratch to resemble the stock as much as possible (without the messed up part).

I would go with the latest build that has Hashcodes kernel included.
[Kindle Fire Android Development] trvor:
I've had the "black screen bug" on the cm9_02_02.zip rom, so I was forced to stop trying. With the USBWOOT.zip rom, the only unbearable aspect of this particular rom are the minor touch glitches on the browser's text box and on the status bar/general touch sensor issues.

The usb mount bug is easy to fix (if not already working), the battery life not a significant pain (methods of limiting unneeded battery usage), and the Ice Cream Sandwich fluency that any and all Android Tablet users admire. This is an excellent project. These things excite me! :cool:

I'll be fully behind the rom that has full HD functionality and Netflix playback. HDFIXWOOT.zip!
[Kindle Fire Android Development] CodenameDeadpool:
PC adhoc WiFi

CM9 ROM is looking smooth except for the fact that I can't connect to my PC's adhoc WiFi network. I'm using Connectify. Anyone found anything that works? I've been looking for something to no avail. Am I just screwed? I ended up going back to CM7. Don't like not being able to access the internet at home.
[Kindle Fire Android Development] Tiffany84:
I'm on 2/5 and I don't get the option to mount the sd card when I plug the fire into my pc and I thought that had been fixed?
[Kindle Fire Android Development] GustavTheLion:
I'm on 2-5 and the Wi-Fi is extremely spotty. It becomes gray often and then I have to soft-reset for it to reconnect. Anything I can do?
[Kindle Fire Android Development] CodenameDeadpool:
Anybody? Anything?
[Kindle Fire Android Development] foxdog66:
Have you tried anything like this? I don't have a adhoc connection to try it on.

Usually means you have came disconnected from Google's servers. Logging back into gtalk should fix it. With the screen off, this thing tends to ignore any 'keep wifi on' settings unless there is network activity (for me anyway)
[Kindle Fire Android Development] CodenameDeadpool:
I've tried a similar app but I couldn'teven get it to open in ICS, acted like it wanted to but wouldn't. Worked in CM7, though. I'm about to try the one you suggested. We'll Se.. All this switching back and forth between recoveries is tedious...
[Kindle Fire Android Development] tillum:
@shapur

Oh come off it. People are asking all kinds of questions in this thread, and it's no longer strictly for development. The less *****ing we have and more simple answers to people who need them, the quicker this thread will move along. Or are you keen to keep posting on this topic to 'speed' up development?

Sent from Fire
[Kindle Fire Android Development] CodenameDeadpool:
STILL no luck connecting to my PC's adhoc WiFi. Can we put "no adhoc wifi access" on the bugs sheet? CM7 has no problem with it.
[Kindle Fire Android Development] Hashcode:
For those of you running nind's 2/5 build of CM9:

I cleaned up the kernel some:

- Fixed power off issue

- Removed extra code for usb mtp which was probably causing issues

- Removed extra code for mmc host sd controller (for boards w/ a card slots)

Anyway, if you want to update the kernel here's a link to the boot.img:

http://bit.ly/AB5E0J

Let me know of any issues that you experience.
[Kindle Fire Android Development] KAdot:
thanks! but still cannot install apps on sdcard.
[Kindle Fire Android Development] ammubarak:
You need to update the PC window driver to connect to KF.
[Kindle Fire Android Development] KAdot:
I mean when i trying to move app on sdcard (Settings -> Apps) it says "Couldn't move app."
[Kindle Fire Android Development] phatboypat:
I have been able to connect to my phone running Wi-Fi Tether. I know it's not the same as what you're trying, but I thought you'd like to know that you can connect to ad-hoc.
[Kindle Fire Android Development] jwilliamf:
I tried this kernel and apps installed on sdcard does not show on drawer after reboot. After mount/unmount sdcard, app started to show up.

Mount/Unmount work perfect.

Power off issues resolved.

Using cm9_02_02

Thank you hashcode!!
[Kindle Fire Android Development] KAdot:
I can access kindle via ADB, but cannot mount usb to PC.

I tried to remove persist.sys.usb.config and reboot, but it has no effect. What i doing wrong?

I also tried to reinstall driver.

P.S. i'm using cm9-02-05.zip and fresh Hashcode kernel.
[Kindle Fire Android Development] jwilliamf:
Ha! same problem here with cm9-02-05 build. Guess cm9_02_02 is the better build.
[Kindle Fire Android Development] jfb9301:
Based on my experience with 02_05 and 02_02. This seems to be apparent in both Hashcodes' 02/02 and 02/05 kernel, nind's 02/05 kernel (based on hashcodes most recent work, and IntersectRaven's most recent kernel.

the USB issue with 02_05 typically appears after a successful mount and unmount of USB. On unmounting, SDCARD becomes unmounted. Resulting in no access to sdcard and no ability to mount sdcard on USB.

Workarounds:

Reboot should work

02_02 does not suffer from this problem and successfully unmounts without unmounting sdcard. This in my eyes makes 02/02 with updated USB drivers the most functional of the available ROMs.
[Kindle Fire Android Development] bl1nkk:
Chrome Beta for Android does not work on the Kindle Fire with ICS. It also does not use the tablet interface. FYI
[Kindle Fire Android Development] N23:
yes, i can confirm that - it's a pity :(
[Kindle Fire Android Development] ssmaster:
Same here, the page loads, but it is a blank white slate. Links seem to work if I press on random parts of the page.
[Kindle Fire Android Development] That Baker Guy:
Makes me sad.
[Kindle Fire Android Development] rmagruder:
Do you think it's because HW Acceleration is off? The reports I read say that it requires it for accelerated scrolling.
[Kindle Fire Android Development] N23:
yes, it looks like it's relaying on Open ES/GL and hardware acceleration - hopefully we will see it working in future builds...

devs we count on you, keep up your fabulous work!
[Kindle Fire Android Development] raphytaffy:
Is anyone able to run Dolphin Browser HD on any of the builds? I believe I'm on the 1/29 build and it is not working for me.
[Kindle Fire Android Development] Felnarion:
Dolphin works for me. Opera does not.
[Kindle Fire Android Development] raphytaffy:
What build are you on?
[Kindle Fire Android Development] KAdot:
Usb mounting works with cm9_02_02 and latest Hashcode kernel, so something was broken in cm9-02-05 and it's not an kernel problem.
[Kindle Fire Android Development] jwilliamf:
You are right! It is not a Kernel problem, but in the build.prop on cm9-02-05.

update: ok fix my problem.

On cm9_02_05 build.prop I changed this line:

persist.sys.usb.config=mtp,adb

to

persist.sys.usb.config=mass_storage,adb
[Kindle Fire Android Development] mewshi:
I took Hashcode's boot.img, merged it into the 2/02 build. It works pretty well on my end. However, as always, I am not responsible if it kills you with a machete.

Get it here

Edit: may not need this; going to TRY the fix in the above post
[Kindle Fire Android Development] foxdog66:
What is the difference between mass_storage and mtp? This is also configured in the kernel (I'm pretty sure)
[Kindle Fire Android Development] nind:
Hmm, i don't have the sdcard does not get remounted as USB gets unmounted issue in 02-05. The part that fixed it is also unchanged in 02-05 :confused:

To all of those who have problem mounting the sdcard on your PC:

I have changed from UMS to MTP in 02-05 completly as that fixed part of the "app could not install to sdcard" problem. If you are running Windows make sure that the drivers are installed correctly. You can check that using the device manager on windows when the kindle fire is plugged in. Use the driver which are shipped with KFU if it shows some errors/warnings. If you are running Windows XP you may need Windows Media Player 10 or above.

---------- Post added at 09:26 PM ---------- Previous post was at 09:22 PM ----------

I don't know wich part of MTP Hashcode has removed from his new kernel, it is working here as before anyway. I'm trying to fix the "app could not install to sd card" thing first and then go partially back to mass_storage so you don't need to reinstall the drivers on windows. The problem is that i don't have much time to figure out what's wrong with the init.rc files these days. (Won't be better in the next 2 weeks)
[Kindle Fire Android Development] Felnarion:
Problem happens on 2/2 and 2/5 for me.
[Kindle Fire Android Development] tillum:
Gotta say, LOVING usbwoot.zip image. Awesome work. Is my daily driver now, and highly usable! Using Nova launcher pushed to /system/apps

How do I donate? Keep up the awesome work.

Sent from Fire
[Kindle Fire Android Development] Shahpur.Azizpour:
Not a big loss imho. It doesn't even support text reflow. At this point the ics stock browser is much better. I played around with chrome on my Nexus S and uninstalled it.

Chrome needs some more time to become really good...
[Kindle Fire Android Development] FroyoShark:
Chrome Beta doesn't work :O

It installs and everything, but settings crashes it and web pages are completely white.
[Kindle Fire Android Development] CodenameDeadpool:
Hhmmmmm. Maybe I'll try another adhoc wifi program on my PC...see if that works. I've tried a couple different adhoc switcher apps on my kindle, but no dice.
[Kindle Fire Android Development] lovejoy777:
does this work?

if so can you post a link to the new build.prop

thanks

Edit. sorry ment to quote tupdate: ok fix my problem.

On cm9_02_05 build.prop I changed this line:

Code:

persist.sys.usb.config=mtp,adb

to

Code:

persist.sys.usb.config=mass_storage,adb

his..
[Kindle Fire Android Development] un4givn85:
so whats the difference between the ics browser and chrome beta

i think the ics browser is just like chrome as is, and it syncs bookmarks with the desktop chrome so whats the big deal?
[Kindle Fire Android Development] eclass82:
Did you even get the chrome browser to work? I downloaded and can't even get any pages to load on it.. hmmm strange...
[Kindle Fire Android Development] sduvick:
The chrome beta doesn't work yet because we do not have hw acceleration working.
[Kindle Fire Android Development] FroyoShark:
The Motorola Triumph CM9 ROM has hw accel working, and Chrome Beta doesn't work on it either.
[Kindle Fire Android Development] eclass82:
Awwww thats right.. Dam HW
[Kindle Fire Android Development] rukin5197:
I think speed is pretty good as it is... will hw acceleration improve this?
[Kindle Fire Android Development] tim1987:
(Regarding the new Chrome Beta on KF)

Looking at logcat, the browser seems to connect to pages and downloads all resources. I see a warning that appears that says "A TextureView or a subclass can only be used with hardware acceleration enabled" There are some other warnings and errors too.

[I'm happy to see that when I installed it and signed into my Google account that it prompted me for my passphrase, so I will soon be able to dump ChromeMarks (As soon as Chrome doesn't rely on hw acceleration/Fire gets hw acceleration)]
[Kindle Fire Android Development] Silent8Strike:
Chrome also doesn't work for me on the Fire, but it works very well on the Galaxy Nexus. I find it a lot more polished than the default ICS browser, and it is VERY fast. I was scrolling through a page with over 50+ high res images images and it didn't stutter once.
[Kindle Fire Android Development] sionicion:
I've asked this already and everybody simply ignored my post altogether... Disregarding my post for now, I will bring up this point once again...why the hell are all of you drawing conclusions to believe that hardware video decoding is the same thing as hardware acceleration?

Hardware video decoding doesn't work, you can't decode video on the Kindle Fire with your hardware, you use software rendering which kills the battery and is hard on the system...when I start Real Racing 2, the game's splash video stutters like ****, but when the real game starts, the graphics are stunning with a great FPS.

I can watch videos using MX Player also fine... Switching to hardware video decoding crashes the playlist and it will start over with software rendering on. It does fine without hardware video decoding but in certain instances, this feature is required.

Now, getting back to what I'm trying to understand... What the hell does hardware video decoding have to do with Chrome not working? As said FroyoShark said, another device WITH hardware acceleration working can't even get Chrome to work either.

So number 1, Kindle Fire most likely has hardware acceleration because I've been able to play all the games I usually play with decent FPS and graphics. Number 2, hardware video decoding is not hardware acceleration. Number 3, hardware video decoding nor hardware acceleration is at fault here regarding Chrome.

Chances are it's yet another compatibility issue where the app thinks the device is a high-resolution phone like the Galaxy Nexus and not a tablet and uses the wrong code for rendering the UI.

My own hypothesis is ICS introduced a new way to identify tablets from phones and apps are just fed a line...its a tablet...no its a phone... They don't really know, they just get told by Android what kind of device they are on. Because Gingerbread certainly doesn't have near as much issues with app compatibility.

An example would be Real Racing 2... Game downloads fine on Gingerbread... Does NOT download fine on ICS, for some reason it gets stuck at 0%.. I believe somewhere along the way, the servers don't know what to send to the tablet because it thinks of it as some unidentified device. BUT if you change the DPI to 240 (practically a phone), then the tables have turned and it downloads and runs the game, you are able to easily switch back to the 160 DPI and the game still runs smooth as butter.

It all comes down to app compatibility for why Chrome isn't functioning correctly on custom ROMs for unsupported tablets. Something Gingerbread handled much easier but ICS made it rocket science I guess for the future of high-end high-resolution Android phones and tablets. Of course, this is my own hypothesis that I have concocted evidence for. I do not know the exact specifics, but it's way better than jumping to conclusions like this "Awwww thats right.. Dam HW", and I'm not even implying that was the only person to assume it, everyone assumed it, but if you read the spreadsheet it clearly states hardware VIDEO DECODING, not acceleration. ;)
[Kindle Fire Android Development] Sidriel:
If you look at the logcat it says a TextureView cannot be loaded without hardware acceleration enabled. That's why people are saying hw acceleration.
[Kindle Fire Android Development] isaiahhhhh:
Not that I don't love chrome as well but how's about we all put our heads together and work on that pesky USB mounting problem before we get to chrome?
[Kindle Fire Android Development] papugoz:
AFAIK USB is mounting correctly now :)
[Kindle Fire Android Development] MayfairDROID:
The latest jackpot release still has issues.... and the other developers release does not use the latest has code kernal. I am waiting for jackpot to update his....
[Kindle Fire Android Development] adbirdie:
Fyi, changing dpi to ldpi fixes the settings crash issue in chrome , so that's one issue done. And to what the poster said at the top of the page, it doesn't work on HTC desire either.
[Kindle Fire Android Development] N23:
how did you change that?

Chrome is working nice on the Desire HD (Virtuous Quattro RC3) with only some pink-ish flicker on tab-swipes...
[Kindle Fire Android Development] DeerSteak:
Search the market for an app called LCD Density or similar, there are several, that can change the DPI settings on the tablet. The default is 160DPI.
[Kindle Fire Android Development] woolbeo:
You guys know that there are multiple types of hardware acceleration right? There is hw accelerated video decoding, hw accelerated open gl, hw accelerated composition, hw accelerated animations, hw accelerated ui toolkit drawing, etc. Honeycomb added hw accelerated ui toolkit drawing, but the app developer had to specifically enable it, even if the app developer targeted honeycomb's sdk version. ICS enabled hw accelerated ui toolkit drawing by default when the app developer targeted ICS's SDK version, if the device had greater than 512MB ram, or was a a tablet.

Since our kernel doesn't have updated PVR Open GL drivers, and screen buffers to accommodate hw accelerated ui drawing, it is disabled on our build of ICS. Yes I know you need the updated binary drivers too, its just that the kernel has to match the binary driver version.

From what I understand, but easily could be wrong, until we have a kernel with updated screen buffers and open gl drivers, we will not be able to have hw accelerated video decoding, even if we have updated IVA codecs and drivers.

FWIW, teamhacksung was able to patch the 2.6.35 kernel for the Galaxy S line to work with the updated PVR Open GL drivers and make the changes necessary to the screen buffers. I know that they were working on a different SOC, but it might give some direction on getting it working on our 2.6.35 kernel until we can get a 3.0 kernel working. Their work is available on their github page.
[Kindle Fire Android Development] jfb9301:
I'm beginning to think that my USB issues stem from a driver conflict. With 02_02, and the latest drivers from KFU 0.93 installed, everything is just fine. With 02_05 and the same drivers I looked in Device Manager and found that Kindle, MTP and MTP USB Device were all flagged with errors (There is no driver for selected device or element), and I get no ADB or USB connectivity.

This is with Windows 7 (32bit) and Win7 64bit

device manager for 02_02 lists Android Composite ADB interface and assigns a drive letter to the Portable Device.
[Kindle Fire Android Development] jdommer:
The correct settings for the our touch screen appear to be:

touch.deviceType = touchScreen
touch.orientationAware = 1

# Size
# Based on empirical measurements, we estimate the size of the contact
# using size = sqrt(area) * 28 + 0.
touch.size.calibration = default
touch.size.scale = 1
touch.size.bias = 0
touch.size.isSummed = 0

# Pressure
# Driver reports signal strength as pressure.
#
# A normal index finger touch typically registers about 80 signal strength
# units although we don't expect these values to be accurate.
touch.pressure.calibration = none
touch.pressure.scale = 1.0

# Orientation
touch.orientation.calibration = default

Unfortunately, that doesn't do anything for the tap/drag problem. The KF can't distinguish pressure or size of touch.

Looks like Android decides any touch where x1-x2 or y1-y2 > 8 as a drag. I can't find any place that that value is configurable after scouring the internets all morning, but if it could simply be turned up to maybe 12 that would probably alleviate 90% of our taps as drags problems.

Anyone have any idea, is there a config file or is that compiled in and has to be changed at source? I feel competent enough to dink with config files, but can't compile crap.
[Kindle Fire Android Development] Hashcode:
I build from the KFire-Android git as a testing model and i've been experimenting with a setting of "16" for touch slop, and in my opinion it's working much better.. could probably be 12, but who knows. I'm having a much easier time selecting things like Beautiful Widgets 1x1 Toggles, where before it was a trial of patience and about 10 touches.

This is a setting in the overlay config.xml file. I went ahead and committed it this morning to the KFire-Android org at Github:

https://github.com/KFire-Android/device-amazon-otter/commit/56b3d52fe6c645a18e60ab765e5b9831cb6a0663
[Kindle Fire Android Development] AdrienC:
Guys, on CM7, we can use the build.prop info from Galaxy Tab to allow us to see, install and run more apps.

But there's no CM9 for Galaxy Tab, so I wonder, what could we use for that? Maybe Transformer's Prime or original Transformer's with ICS? I guess that with Chainfire there would be no issues regarding Tegra.