yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Android Development] woolbeo:
Awesome work. Keep it up! :)

It looks like you could have a similar problem with ducati

<6>omap-rproc omap-rproc.1: Loaded BIOS image ducati-m3.bin, size 1388356
<6>omap-rproc omap-rproc.1: BIOS image version is 1
<6>init: command ‘write’ r=0
<3>omap-rproc omap-rproc.1: Expected BIOS version: 2!
[Kindle Fire Android Development] UrticantOwl:
I was looking through the output and saw something that I wasn't expecting:

<6>usbcore: registered new interface driver usbhid
<6>usbhid: USB HID core driver

Since the USB Human Interface Device drivers seem to be registering, can we expect that simple USB keyboards (as well as mice and game controllers) might not be too difficult to set up on this kernel?
[Kindle Fire Android Development] shantam:
plz make usb drive support

it will be best part of the kernel
[Kindle Fire Android Development] tmhung:
OMG , i love it :)
[Kindle Fire Android Development] AlexDeGruven:
I'm going to go ahead and say you're dead wrong on that one :).

I agree it will be a very cool thing to have, but USB host support is already working in .35 kernels.

The biggest, coolest thing about this will be having full access to the hardware for acceleration.
[Kindle Fire Android Development] seishuku:
Where and what kernel? I've tried nearly all available, and also have tried with my own custom kernels... All to no avail.
[Kindle Fire Android Development] luniz7:
I really appreciate the work your putting into this hashcode. Thanks!
[Kindle Fire Android Development] lovejoy777:
ooo its so exiting :-)

thanks

steve
[Kindle Fire Android Development] Veritass:
God damn people who spell the word "please "plz" just really Irk me

On the higher note. I can't wait for hwa support ill finally be able to switch to ics.

Any news on the light sensor?
[Kindle Fire Android Development] shantam:
in which kernel usb host mode is supported
[Kindle Fire Android Development] gadgetman13:
None that I'm aware of. You might want to follow the following thread: http://xdaforums.com/showthread.php?t=1531509

Especially post 2. nind is trying to get it to work.
[Kindle Fire Android Development] AlexDeGruven:
My mistake. For some reason, I thought CM7 and some of the .35-based CM9 builds had USB-host working.
[Kindle Fire Android Development] malawito:
Not sure if it works for us, but qualcomm just released their gpu drivers for ics (kernel 3.0). Probably that could help.
[Kindle Fire Android Development] mitzumr:
i dont think so, the Kindle has TI OMAP 4430 with PowerVR on it, but i hope TI does the same:)
[Kindle Fire Android Development] astmario:
Maybe is time to start spaming TI for drivers or making pettition like guys have for Quallcom drivers:D
[Kindle Fire Android Development] shantam:
i am selling my kindle fire bcoz no support for usb drives and

no hw acceleration
[Kindle Fire Android Development] jardivben:
That will come all in good time so hold on to it.:D
[Kindle Fire Android Development] Shahpur.Azizpour:
Thanks for the information.
[Kindle Fire Android Development] Krunk_Kracker:
It is truly a mortal blow to the Kindle Fire community that you are leaving us. We, in our desperate but feeble attempt to keep you, humbly request, nay, beg you to stay with us. Please sir, do not go!

TL: DNR,

Bye.
[Kindle Fire Android Development] chairshot215:
I get free concert tickets all the time by spamming record label PR departments convincing them I am a writer for a fabricated local publication. Could we not spam TI in the same way but as a startup electronics developer who is looking at the chip to be used as part of a new device but would need to look at the drivers before making any decisions or something along those lines?
[Kindle Fire Android Development] southbird:
Wow. Posting it in the thread that most recently gets us hope that there WILL be support for these things.

Problem is that most hardware manufacturers don't release driver source because they're worried about some kind of intellectual property or something they think will be leaked if you get it. So usually you will have to sign an NDA to even see the source and that won't really help anybody. If they're just not releasing it for support reasons, and they'll release it with a disclaimer of no support, then you'd be lucky. So you can always try.
[Kindle Fire Android Development] icebuck:
To add some worth to your conspicuous post, Why don't you come up with a list of tablets that support HWA

Also, in the future please post non development stuff in the General Section. :D
[Kindle Fire Android Development] gett:
So? What you expect from this community? To buy your device? To spread the word? To leave their jobs and start urgent developing of usb drivers? To cry?
[Kindle Fire Android Development] HaiKaiDo:
You had me at bcoz........ffs >_>
[Kindle Fire Android Development] ontwowheels:
To properly voice your displeasure with the development community, you should just GIVE your kindle away.
[Kindle Fire Android Development] BiteBlaze:
I can't wait for this kernel! I hate on CM9 how the sound stops working and then it just freezes and reboot after 2 minutes.

Sent from my Kindle Fire with CM9
[Kindle Fire Android Development] isaiahhhhh:
NO! I had a dream that this day would come but I hoped with all my heart it never would. Sir, you were the glue that held this community together, under your valiant guidance we flourished, now we hang by but a thread in your absence, please, don't sell your Kindle Fire you would start a selling frenzy you would be the first to do so...wait...no you wouldn't...never mind my bad, bye...
[Kindle Fire Android Development] symbiiote:
Delete your account to.
[Kindle Fire Android Development] leoinj:
I was having problems with my kindle and I flashed it back to stock. HW and USB work fine now. You could try that.
[Kindle Fire Android Development] isaiahhhhh:
No no, let him go, it's called thinning the herd, just think of it as one less person to complain about something they did wrong.
[Kindle Fire Android Development] theTwiz:
From:

theTwiz

Finance Manager

Kindle Fire Development

To:

shantam

18th May 2012

Dear shantam

This is in reference to your letter of resignation submitted on 17 May 2012. I wish to inform you that your resignation has been approved by the organization and you will be relieved of your responsibilities at the end of your last working day on 18 May 2012.

Your resignation letter has been forwarded to the Finance Department for processing any dues and you can clear other exit procedures before the last day of work with us.

It has been a pleasure having you as one of our employees and we wish you success in your future undertakings. The company will miss your good behaviour, hard work and the heights you gave to the company with your strong determination and support.

With best regards,

theTwiz
[Kindle Fire Android Development] intersectRaven:
Not sure if serious or flame-bait... ;)
[Kindle Fire Android Development] NRGZ28:
Alright guys.. enough with the trolling. Let the guy be. It was obviously bait and you guys took it well. Let's talk kernels from now on.
[Kindle Fire Android Development] borborpa:
Pssssssst. Hey Twiz...it's March. :D
[Kindle Fire Android Development] astmario:
http://kernelnewbies.org/Linux_3.3?el

Summary: This release features as the most important change the merge of kernel code from the Android project. But there is more, it also includes support for a new architecture (TI C6X), much improved balancing and the ability to restripe between different RAID profiles in Btrfs, and several network improvements: a virtual switch implementation (Open vSwitch) designed for virtualization scenarios, a faster and more scalable alternative to the "bonding" driver, a configurable limit to the transmission queue of the network devices to fight bufferbloat, a network priority control group and per-cgroup TCP buffer limits. There are also many small features and new drivers and fixes are also available.

You didn't go far for now, maybe switch to new 3.3 kernel instead of 3.0?
[Kindle Fire Android Development] ontwowheels:
Agreed.....but it was good stress relief...
[Kindle Fire Android Development] isaiahhhhh:
Agreed, it was good, but there's a good point, no need for anarchy.
[Kindle Fire Android Development] southbird:
Wouldn't recommend switching to a new kernel willy-nilly when we don't even have a working 3.0.8 kernel yet. The 3.0.8 release that's being worked on is officially sanctioned for the motherboard. It really should be "new enough" for the time being.

But that is interesting news that Android and mainline Linux are finally going to start getting along. :)
[Kindle Fire Android Development] furtom:
Yes, troll-bait, but the above response was really funny!

Made the whole thing worthwhile. Thanks!
[Kindle Fire Android Development] UrticantOwl:
Agreed, for now I think we should stick with the Kernel that the board was built for...

Those features are nice, but many of them have no practical application in a Kindle Fire. (as of now) RAID striping just isn't something that can practically be done on our devices and most ROMs don't make any use of BTRFS anyways. (ext4/ext3 is fast enough and stable). The list goes on, but none of the new kernel additions seem to be all that relevant to the Kindle Fire environment.

That said, once we have the 3.0.8 running, I will whole-hardheartedly support forward movement.
[Kindle Fire Android Development] Hashcode:
Technically after merging in TI updates from the p-android-omap-3.0 branch, the Kindle Fire kernel is now at 3.0.21.

I was hitting some roadblocks with the mmc controller and some of the bugfixes / changes were very interesting looking. But anytime you merge code or make large changes, there are a few days of cleaning up merge issues, etc. Which is what I'm doing now.

Also, word from the NookTab guys was that if you could work out some driver / support issues, its actually easier to bring new devices up on a 3.2/3.3 kernel due to code cleanup and streamlined support for the architecture.

Someday maybe.
[Kindle Fire Android Development] shantam:
Dear Hashcode

you didnt update your op from when the thread has started

what's your new accomplishments

glad to know about?
[Kindle Fire Android Development] astmario:
Had you read that post, you would notice that he is posting updated boot log on his blog:

http://blog.hash-of-codes.com/kindle-fire-ics/

As you can see, it is updated today, so he is working on it. Since no one else contribute to what he is doing, and he didn't came to some breakthrough since last post here, there is no point for him to post here.
[Kindle Fire Android Development] That Baker Guy:
i second that notion
[Kindle Fire Android Development] bwinger79:
Stop posting garbage.....

<rant>

Plz people....out of 90 some odd posts, there are about 5-8 worth reading. Can we all grow up and stop posting garbage??? We dont need every XDA member dropping in to post "I agree with .......whatever". All you do is waste space, and make these forums impossible to find the actual content people are looking for. 60 posts for troll bait...really??? Cant we just let Hash and the other devs to their thing and follow along without wasting server space with worthless posts? Flame away.....I really dont care.....but PLZ, PLZ, PLEASE stop wasting time and space.

</rant>
[Kindle Fire Android Development] tokyostomp:
i agree with bwinger79!
[Kindle Fire Android Development] alarien:
So, now there shouldn't be any questions, just see post #2.
[Kindle Fire Android Development] papugoz:
Yes, and complaining about those posts are another 40 posts to read :(

So... maybe just ignore posts with stupid questions and resp only to something constructive?
[Kindle Fire Android Development] x0xhellx0x:
I'll get on it
[Kindle Fire Android Development] ontwowheels:
I must have missed the original poster complaining about the thread....:rolleyes:
[Kindle Fire Android Development] Hashcode:
Quick Status update:

I completed the latest source code merge with TI's omapzoom and the kernel is now technically version 3.0.21 (as opposed to 3.0.8). During this merge I removed quite a bit of Amazon customization from the kernel sources and will continue to do so as needed, because it makes updates about a quadrillion times easier.

The bootup status really hasn't changed much: Kernel boots, init kicks off, the services startup and about the time we hit "surfaceflinger / bootanimation" the whole process stalls out.

A new change, is that ADB is now up and running and that's helping troubleshoot quite a bit. It means access to logcat, shell, etc. So far it looks like the halt is due to a 2.6 backlight driver and some framebuffer configuration issues. Hoping to make some progress on those soon.

Also, I've started the updated Android build under "ics-test" branches in the KFire-Android git for both device/amazon/otter and vendor/amazon/otter (https://github.com/KFire-Android). Here you can see what a "regular" ICS build for the Kindle Fire looks like. Almost all of the vendor files are removed (which came off the original device), and it has 3.0 kernel modules and board config. This includes removal of most of the legacy hacks that are used for OpenGL, old style Wifi config, etc.

I'll get you more info as it happens. But, you can trust that if nothing is being updated here or on the blog (http://blog.hash-of-codes.com/kindle-fire-ics/); it's not because I'm ignoring the KFire. I'm just not making much progress.
[Kindle Fire Android Development] fiddlefaddle:
Awesome hashcode!! Keep up the good work man!:cool:
[Kindle Fire Android Development] ygvuhb:
nice news update
[Kindle Fire Android Development] Stevethegreat:
About hardware accelerarion: What exactly do you mean by it? I think games (for example) are already accelerated on ICS, so maybe you mean "hardware decoding"?

Also if you do so, do you mean the same that can be found in stock (.MP4, Netflix), which is limited at best or do you mean the whole pack (most popular filetypes), like -say- some Chinese tablets already have (for that we'd need codecs of course)?
[Kindle Fire Android Development] southbird:
Hardware acceleration in the context we're using it is the way that video information can be quickly moved around for high performance situations such as video playback. Google Chrome for Android also uses this for its general rendering. Lack of this hardware assistance breaks video players such as Netflix and Flash which depend on it to get performance.

It really has nothing to do with codecs, otherwise they would be calling it hardware decoding. You'd like to think a forum full of kernel geeks would know the right terms to use. :)
[Kindle Fire Android Development] tduermeier:
I've hit the thanks button, but I just want to express my thanks further. I'm infinitely impressed at your diligence, Hashcode. With the progress as slow as it is a lesser man would have quit long ago. Mad props to you, brother.

Sent from my SGH-T959
[Kindle Fire Android Development] isaiahhhhh:
Hashcode, when you get to the point where you need testing (if you decide you need testing on multiple kindles aside from what you have already) i'm perfectly willing to lend mine to the cause.
[Kindle Fire Android Development] AlexDeGruven:
Ha, except a solid half of the posters in this particular dev forum barely have enough brain cells to maintain respiration.

There should be a test for posting privileges in dev forums (general and Q/A, whatever). Only the geeks should be allowed here, and everything else goes to the other areas.

Related: This is awesome. I'll have to laugh if it takes something ridiculous like 30 sec of tweaking to get HWA working once the screen gets going properly.

Also: I wonder how much control we'll have over the LED color once that driver is up and running properly. It does green and orange already, so that means there's at least green and red LEDs. If there's a (unused) blue one in there too, and we can access it, that would be entirely awesome.
[Kindle Fire Android Development] lovejoy777:
Dear

Alex Newton Fleming Einstein DeGruven

If you are so smart where's your 3.0 kernel?.
[Kindle Fire Android Development] NRGZ28:
Cut it out and stop flaming.
[Kindle Fire Android Development] verkerria:
I was noticing as I browsed the kernel init on the blog, and where hash said the boonanim went to hell, it mentions the emif0. Im wondering if it has something to do with it. The only place this item successfully does anything prior to bootanim is irq assignment, it failed the mpu load. I dont know if this is relevant, just trying to help :)
[Kindle Fire Android Development] shantam:
Very good progress hashcode bhai
[Kindle Fire Android Development] Stevethegreat:
OK then, sorry if I have offended some souls, so let me rephrase:

"Are we going to get proper hardware decoding too?"

Because as it stands the only filetype that is accelerated on KF (in general) is .MP4, which is a rather frustrating situation; for a tablet -at least- it is, if it was a phone I wouldn't mind.
[Kindle Fire Android Development] kjwalker:
THIS. Cannot say it any better. You are a saint among us all, Hashcode.
[Kindle Fire Android Development] tex321:
Do any of you know of any functional implementation of the 3.3 kernel on a 4430 device running android?

Thanks for working on making Kindle fire better.
[Kindle Fire Android Development] AlexDeGruven:
Highly unlikely this early in the game. I don't even know of any desktop spins (outside of individuals compiling their own kernels) using 3.3.x yet.
[Kindle Fire Android Development] CUViper:
Fedora 16 is already pushing out kernel 3.3: http://koji.fedoraproject.org/koji/packageinfo?packageID=8

However, updating for x86 desktops is a whole different ballgame, pretty straightforward. That's a big reason why developers try to get their code into the kernel, so they're not continuously porting forward manually.
[Kindle Fire Android Development] generaldizzle:
Dude just saying thanks. You are awesome
[Kindle Fire Android Development] akarpov:
Is kernel 3.x working with VMware 8.0?
[Kindle Fire Android Development] Hashcode:
Minor update:

I booted up into the OS with the screen driver off.

In adb, I ran some event/input tests and was able to see touchscreen events registering as well as the accel/gyro/proximity sensors. Audio is disabled

For the screen, I'm posting on the TI forums with all of the debug info to see if they can give me more info about the EMIF0 SYS error I'm seeing whenever the dmm is running in the graphics driver.

Hopefully, I'll get a response Monday.

If I get bored, I'll go ahead and try out the latest 3.2 TI kernel to see if the screen is magically working (it probably won't be).
[Kindle Fire Android Development] un4givn85:
Great work hashcode

Can't wait for the finished product.
[Kindle Fire Android Development] Kuzma30:
Where did you found 3.2 TI kernel? I want test it also :).
[Kindle Fire Android Development] Hashcode:
I totally misspoke :/

Latest from p-android-3.1 head is: Linux/arm 3.1.0
[Kindle Fire Android Development] Hashcode:
I have a merge in-progress to the TI 5AI1.8 kernel (3.1.0). I'll get a status update later.
[Kindle Fire Android Development] Leraeniesh:
Good to Hear :D

Sent from my CM9 Kindle Fire
[Kindle Fire Android Development] ontwowheels:
I am getting all warm and tingley inside.....
[Kindle Fire Android Development] Jaimemex:
What does that mean exactly? :p
[Kindle Fire Android Development] vbdss:
I think it means that all the work that he had done on the other kernel, will be merged to this new one.
[Kindle Fire Android Development] Stevethegreat:
I'm aware that I'm becoming a bit redundant and I'm sorry about it but I've got to ask once again (since last time around I didn't get an answer)...

What do you mean by HW acceleration? It seems that every android device has different definition(s) of the term. To some it means 3d acceleration (like the one you get in games), to others it means 2d acceleration (like the ones you get in menus), to others yet it means hardware decoding in videofiles (certain filetypes). So in our case what of the above HW acceleration means?

Again I'm sorry if I'm becoming redundant... :(
[Kindle Fire Android Development] vbdss:
Means everything, from 2d homescreen drawing using H/W to 3d games using H/W

I guess that we now have only Software running everything
[Kindle Fire Android Development] Krunk_Kracker:
H/W decoding. We have 3D, but with just software decoding. H/W decoding will use the cpu/gpu rather than emulating through software. At least that is how I understand it.
[Kindle Fire Android Development] YaKillaCJ:
Ok its simple really.

Think of it like a computer. Our devices has a few major parts that all work together. CPU, Video Card, Ram, Hard-Drive, ect. The 2 that we discussing are the CPU and VideoCard.

Now the CPU (Processor) is designed to control, decipher, decode, calculate and transmit all the information from every other part. Its basicly the brain.

The Video Card (GPU) is designed to only process the visuals and display. It anticipates and draws/displays everything on the screen.

Now whats happening in the current ICS roms for the kindle is we have a lack of drivers so the video card isnt running all the task its suppose to do. In this case our CPU has to step up to the plate and take on the work load of processing and then sending the info to be displayed on the gpu. However it isnt designed to handle high quality visuals and it means our CPU is running much more then its meant to.

With the right video drivers. Our Video Card will do the original work its designed to do and take on nearly all visuals that isnt basic blocky colors. 2D, 3D, anticipation of whats coming next as we scroll a text page all count.

Hardware decoding is more about Video/Audio file formats. Again think in a similar manner. If we have the right Drivers and Codecs. The load is taken off the program to process a video. When a program does software decoding, its pulling its power from the CPU (which is VERY ineffencient)

Real life example is think of your TV as a CPU and your Cable/Satellite box as a GPU. TVs have a basic standard and arent designed to said Cable/Sat provider needs. Plugging your feed line straight into the TV doesnt provide all its Chanels, quality, or functions.
[Kindle Fire Android Development] Hashcode:
EMIF errors are fixed now.

Had a full boot into Android.

Next up fixing backlight driver so I can see the damn screen, and then audio issues.

Kernel page updated to logcat:

http://blog.hash-of-codes.com/kindle-fire-ics/
[Kindle Fire Android Development] adamantypants:
I blacked out for a second after reading "full boot"
[Kindle Fire Android Development] Hashcode:
I tried "BOOTING INTO OS" but it didn't fit :/
[Kindle Fire Android Development] shantam:
We all are eagerly waiting for your kernel and your progress shows your hard work and your love to xda
[Kindle Fire Android Development] TexasRules777:
Ha I lol'd hard reading that! I thought the same thing! Hash you're a beast..the work here and on my razr..don't know how you find the time but THANK YOU!!!
[Kindle Fire Android Development] googlelover:
I **** brix, and thought I was dreaming when I read it, of course I didn't dare hope the kernel was magically done, but crazier things have happened haha.
[Kindle Fire Android Development] Jaimemex:
I'm going to name my son after u Hashcode...
[Kindle Fire Android Development] ObihoernchenDE:
Such a great progess!

Hope you'll be able to fix the backlight driver soon.
[Kindle Fire Android Development] Bohnsta:
Tell me why the Devs at XDA work harder than Amazon? Thanks Hash!
[Kindle Fire Android Development] Pyrotek:
You sir are a giant among men. lol

Seriously, thanks for all of your hard work and dedication.
[Kindle Fire Android Development] cluendo:
Hashcode you make history here:) Hashcode > Amazon devs
[Kindle Fire Android Development] AlexDeGruven:
I'll take 'Missing the Point' for $2,000, Alex.
[Kindle Fire Android Development] isaiahhhhh:
When I saw Hashcodes post I almost went and told people on my floor, then I remembered my floor is full of idiots and they can't program an alarm clock let alone flash a rom. Hashcode, thank you ever so much, it is people like you that are keeping the open source spirit alive.