yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Android Development] Stevethegreat:
Honestly though, this project will breathe a new life to KF and make it really competitive to the other small tablets despite it's equally small pricetag...

It's obvious that Amazon crippled the device through bad software/kernel so that it can only do one thing, pitch the Amazon store and it's products. But if Hash is successful only then the device will be truly freed and become able to use its hardware.

So for that -Hash- you have my thanks (regardless of your eventual level of success). It will be quite a shift to be able to have a *fully* functional tablet for less than $200, maybe the first of its kind
[Kindle Fire Android Development] Krunk_Kracker:
To be fair, the Fire is not crippled to Amazons standards. It does exactly what they made it for.

It's us who cripple it, by asking it to do things it was not intended for. That said, this kernel will be a great start to making it a full fledged tablet.
[Kindle Fire Android Development] Shermanballz:
Uh, you are SO backward about this. STOCK fire runs android, but features were removed/tweaked so they could lock you into their ecosystem. They took a decent operating system and made it worse to benefit them. It does exactly what they made it for BECAUSE they TOTALLY crippled it to their standards.

We don't cripple it. We give it MORE features. Yes, ICS is missing things stock has (hwa), but that's because its not done. Go use cm7. Is that crippled?
[Kindle Fire Android Development] Krunk_Kracker:
Totally missed my point.

This thread is not for this discussion anyways.
[Kindle Fire Android Development] AlexDeGruven:
This... It's been gone over 1000 times. The Fire is a purpose-built device for delivering Amazon's curated experience. Android, in this case, is merely a platform for this delivery.

There is no crippling going on. This device does exactly what it was intended to do out of the box 100%.

It's great that devs are working so hard on unlocking the extremely high potential of the device, but it's by no means a reason to slight Amazon for shipping it the way they did.

If, however, Amazon had touted the Fire as a do-it-all 7" full-featured Android tablet-on-the-cheap and then only delivered the curated experience, then people might have a complaint.

To make a car analogy: 99% of vehicles produced today have the potential to output MUCH higher horsepower than what they ship with from the factory. The LS1 in my Camaro outputs 340hp as shipped to me. If I choose to unlock more of the potential (which is extremely high for these engines), that is my decision, and it's by no means a slight to GM for "crippling" my car's engine with only it's stock HP.

Saying the Kindle Fire is a "crippled" device is like saying that any car not shipped producing the absolute max horsepower possible from the engine is selling a "crippled" car. Then going out and still buying that car, all the while *****ing about its lack of horsepower.

Back on topic: I'm extremely excited about these new developments. It's great that we've gotten some source/bins for Ducati that is already ready to work within our 512MB RAM envelope. I'm getting closer and closer to loading out CM9 on my Fire.
[Kindle Fire Android Development] Hashcode:
I've tried to load the ducati bin from the Archos ROMs out there but it seems they are for the 1gb systems. Im going to extract the .aos file and see if there is an alternate "lib" folder for the 512mb device.

We don't have the same gptimer issue as NookTab so you might have more success with one of the 1GB binaries that uses timer 10. Tho offhand I don't know of any devices that fit the bill.
[Kindle Fire Android Development] Krunk_Kracker:
Last I heard, Hash still doesn't have the Ducati source for the fire. Unless you're talking about the other potential ones that work with 512?
[Kindle Fire Android Development] isaiahhhhh:
Hey hash if you get a chance please jump into IRC, I have something to run by you.
[Kindle Fire Android Development] backspacepc:
Hash, which .bin did you wind up with? Can we merge the 2 together?
[Kindle Fire Android Development] AlexDeGruven:
Yeah, that's why I said "source/bin", and not just source.
[Kindle Fire Android Development] datacron:
Um... we bought a book reader at a decent price and we're able to unlock more features. I don't see how or why you're complaining. I saved money and gained functionality I wouldn't have otherwise.
[Kindle Fire Android Development] Stevethegreat:
Exactly which is why we bought it for $199 and not $499 like the rest of the android tablets. That's why I do not actually complain... but to tell the truth here hash does us an actual service here. He takes a fiat and tries to turn it into a Ferrari... for that I'm thankful.

Anyway back on topic, which is the kernel; please -people- ignore my prior post (which started all this), especially if you are to read it the wrong way...so like I said "back on topic".
[Kindle Fire Android Development] Pyrotek:
Any way you look at it, we are all going to come out ahead thanks to the hard work of hashcode and his peers on the Nook side of the fence. It's exciting to follow his progress as a fellow programmer. I've been an iOS dev since the inception of the "app store". (dare I say iOS on an Android forum? :lol:)

The kindle is my first Android device, and the only reason I picked it up a couple weeks ago was the awesome deal I found on CL for 100$. I've been wanting a tablet for awhile, and with the custom roms available paired with the cost this was a no-brainer.

We should all be thanking hash for his dedication and waiting patiently for updates rather then asking silly questions in his development thread. Some of them made me cringe.
[Kindle Fire Android Development] bennettg:
what is CL?
[Kindle Fire Android Development] JoshuaLintag:
Craig List
[Kindle Fire Android Development] shantam:
I think now progress should be fast
[Kindle Fire Android Development] shantam:
Where are u hash bro
[Kindle Fire Android Development] airmaxx23:
He's probably working...
[Kindle Fire Android Development] Hashcode:
I was out of town a bit this week, but I'm back and catching up on work (and some hot issues with the phones I support).

Most of that is taken care of and I'll be hammering on the kernel tonight.
[Kindle Fire Android Development] airmaxx23:
Great news, I'm looking forward to it and your work is greatly appreciated.
[Kindle Fire Android Development] lovejoy777:
how dare you have a life outside of xda. :-)

thanks again.

steve
[Kindle Fire Android Development] vbdss:
kkkkkkkkkkkkkkkkkk

Little bastard this hash guy, having a life outside xda and we here, on F5 just refreshing our browsers.
[Kindle Fire Android Development] Krunk_Kracker:
You guys are totally smashing this thread...
[Kindle Fire Android Development] BrooksBlood:
Great news Hash, we really appreciate the amount of time and effort that you put into this kernel. I know that if anyone can get it compiled its you! Can't wait to see hwa working, along with the other great features you are working so hard on.
[Kindle Fire Android Development] shantam:
Hit like if u like it

Like=
[Kindle Fire Android Development] Hashcode:
Updated #2 post with some fixed items:

- Audio is now working, including headset jack for output and recording. (Thanks nook_lover for getting source from TI!)

- Internal "media" mounting is fixed

- Wireless drivers and modules are built but hitting an error in the OS. Troubleshooting this.

- New memory routines for handling our lower (512M) system in ICS are now working. I show 130MB free when I first boot up, and the system should dynamically allocate needed resources for the ION driver vs. The pre-allocated 200MB method that is used on 1GB systems.

I managed to get the Archos ducati binary to load and the OMX server to start. Now I want to be very clear: this is very experimental and probably wont work right off the bat. BUT it's progress on the hardware codecs front.

Once the wireless issues are ironed out, I'll crank up a new dev/testing thread with a CM9 v0.1 ICS ROM (running the new kernel).

Some quick notes about the upcoming testing:

- We'll actually have 2 threads: 1 here in the dev section for testers and devs to talk about current issues. And a 2nd "users" thread (not that the ROM should be used as a daily yet -- its not ready) in the general section. This should be where discussion about non-dev questions and/or tech support can happen.

- No ETAs. This is still a work in progress and fixes happen as they happen.

- Expect things to work, and then not to work, and then get fixed again.

Hope you're all enjoying your Saturday!
[Kindle Fire Android Development] phamxp426:
That's great news Hash! Thank you for all your hard work. No need to rush and take time for yourself too!
[Kindle Fire Android Development] backspacepc:
What problems are you running into as far as ducati? Is it actually running, or loading then failing?

Edit: never mind, I just read the second post.
[Kindle Fire Android Development] shantam:
Great progress

God created u as a special and helping personality
[Kindle Fire Android Development] shantam:
Hash brother

If u can make a more than two touch points work

It will be a great deal and we will be very thankful to u
[Kindle Fire Android Development] Krunk_Kracker:
He's said multiple times we do not have the correct firmware for more than two touches. Currently, afaik multi point is not a priority.
[Kindle Fire Android Development] backspacepc:
Some people refuse to read, which is why I'm glad he's separating the threads when it gets to alpha.
[Kindle Fire Android Development] Jaimemex:
hashcode is a beast! Can't wait for the alpha release!
[Kindle Fire Android Development] uoY_redruM:
Who knows, Alpha could be here in days from now for all we know! Hash has progressed way further and faster then I had expected, that's for sure.

If you need a tester when you're at testing point, feel free to PM me. I know how to use fastboot and what not and I'm experienced (I won't freak out on you if something weird happens :p)

Great job thus far Hash!
[Kindle Fire Android Development] soupmagnet:
ditto
[Kindle Fire Android Development] iroctheworld:
I <3 New Kernels.

I'm ready to test, and Great Job! :D
[Kindle Fire Android Development] cruel91:
I dont want to spam, but this is the greatest news for me. Thank you again for amazing work and effort
[Kindle Fire Android Development] teng247:
Once hw acceleration is working ill be sure to send over a donation. Keep up the good work!
[Kindle Fire Android Development] nickf1227:
$10 bucks hash, sorry I couldnt do more.

THANKS AGAIN FOR WORKING SO HARD ON THIS
[Kindle Fire Android Development] Lance Uppercut:
Great job Hash. Thank you for using your talents to help useless bums like me out. I'll be sending a donation your way and another one the minute I'm able to use Netflix on my new ICS Kindle :)
[Kindle Fire Android Development] pbailey212:
For a while I was getting irritated with all of the non kernel chatter going on here. But hash isn't complaining and its his thread. Plus I'm sure he has made a couple bucks in the process, so rock on I guess.
[Kindle Fire Android Development] lovejoy777:
A beer's on it's way:-)

Thanks
[Kindle Fire Android Development] AgentCherryColla:
Wow :D Nice job. I didn't see Bluetooth. Sorry if it's been asked before, but dosn't need a special driver?

I'm buying a KF in 3 weeks. This ICS Kernel sold me on it, once I get my paycheck you'll see a 12 pack coming.
[Kindle Fire Android Development] Felnarion:
Bluetooth will not be possible on the KF. The various fear Downs have shown relatively definitively that there is no chip for it
[Kindle Fire Android Development] AgentCherryColla:
Great sadness has over came me. But I swore the TI chip had BT.
[Kindle Fire Android Development] Joshlovesandroid:
I can't find a download think. Sorry for the dumb statement and question but I'm new to this thread. Where is the link?
[Kindle Fire Android Development] marty331:
Once you find it, it will be there.

CM7 Infuse - XDA Premium
[Kindle Fire Android Development] collindv:
For Pete's sake, do people not read the op anymore? This is a work in progress, there has been nothing released yet. We are all waiting patiently :-)
[Kindle Fire Android Development] shantam:
Mera lun hai
[Kindle Fire Android Development] UrticantOwl:
In response to the second post:

I think USB Mass Storage would be fantastic. :D

What, besides kernel and generic USB drivers, is required for it to work on the KF?

The lack of expandable storage on the device makes this particularly useful, since it will allow you to easily move media off of the internal SDcard.

That said, it's not necessarily something that needs to be in the initial release of the kernel...
[Kindle Fire Android Development] chairshot215:
overall I'm not sure what I find more irritating, people who either don't read or more likely just missed something or posters who fill up space commenting about those who either did not read or missed something. At least the first group is somewhat looking for information. The second group more often than not just come across as needing someone to belittle so they can appear more intelligent. Annoyed at myself for taking the space for this post but just saying commenting on dumb questions not only just waists more space but discourages good questions when there is a group of people just hanging out waiting to make themselves appear to be the smartest person in the room by trying to make others look stupid.
[Kindle Fire Android Development] YaKillaCJ:
Yea not needed but would be really nice to have. Also CIFS would be another plus.

Just a random question. Being that ICS is designed to run under a 1GB ram system. Would adding a 256MB swap partition help big time? I mean not to the sdcard partition but makin 1 for itself.
[Kindle Fire Android Development] Stevethegreat:
CIFS and OTG support is a must for devices with as low storage as our KF.

Even if they do not have to be to the initial kernel release they would be very welcome to come with subsequent releases.
[Kindle Fire Android Development] vbdss:
There is a guy testing an build of AOKP using the Hash's Kernel that he said he got from his git.

http://xdaforums.com/showpost.php?p=24627907&postcount=149
[Kindle Fire Android Development] Pyrotek:
I built Hash's kernel from source and integrated with AOKP build 30. It boots nicely and even fixed the static wallpaper. Obviously, no wifi yet as mentioned in his progress. Haven't tried much else, as I did this late last night and have to work now. :)

Awesome Hash, i'm learning from your hard work. Please don't bother him about this or keep asking for a test rom. If you really want one, it's not hard to build yourself.
[Kindle Fire Android Development] backspacepc:
Pyro, did you test HA? When I compiled I was getting spotty results. I didn't see source for wifi so I could play with it. Ported 3.2 from the a500 for testing purposes.
[Kindle Fire Android Development] Pyrotek:
Not yet, will prob poke around a bit more this evening. I used his prebuilt kernel driver modules. Was late last night when the initial build finished so I didn't get to spend any time once it built / booted.
[Kindle Fire Android Development] Hashcode:
Pyrotek, this is awesome :) And EXACTLY the reason I'm trying to keep the new build for Kindle Fire ICS as clean as possible. We should be able to bring up the more developed AOSP-based ROMs in a day w/o little to no customisation (AOSP, CM9, AOKP, etc).

Wifi is coming. I'm down to about 1-2 issues of debugging.

Side note: My work has been VERY busy over the last few days so I'm trying to get time in when I can, to get this out for testing.

Thanks for the patience.
[Kindle Fire Android Development] backspacepc:
Its running really well with HC 3.2. Today when I get home I'm going to start compiling a new AOSP.
[Kindle Fire Android Development] Joshlovesandroid:
Sorry I read it i just didn't know if there was a download link anywhere so I thought I'd ask
[Kindle Fire Android Development] matchstick13:
The previous posters all built it from Hash's git source. If you want to try it out, compile it from his git hub and flash it to your phone. There will not be a download link until Hash thinks it is ready for the general public to test/use. When that time comes he will compile a kernel from his source for distribution, and will post the link in the new thread he starts. Until then STOP ASKING.
[Kindle Fire Android Development] Hashcode:
Lets try and keep it civil please.

People are probably getting excited to see something new and asking for a download link isn't quite the same as "does netflix work with this ROM?" Right now this thread is mostly discussion anyway. Once the new threads kick off, we'll try and steer folks into the right one.
[Kindle Fire Android Development] AgentCherryColla:
What's the Current max OC on the KF? 1.3? Just noobing it out for right now.
[Kindle Fire Android Development] Krunk_Kracker:
Only for some. Not all Fires are able to handle it.
[Kindle Fire Android Development] Hashcode:
This does bring up a good question of whether I should enable 1.2 overclocking via the "high silicon" setting (some chips are better than others..).

Or perhaps setup the default kernel with 1.0ghz as max, but have a flashable upgrade for 1.2ghz.

So if your chip can handle it, then use the extra kernel. If not, just leave it alone.
[Kindle Fire Android Development] drk.hd:
I'm thinking that a flashable upgrade would probably be best. That way, the users take on the risk, and can't blame you.
[Kindle Fire Android Development] milanche:
I agree on this one.
[Kindle Fire Android Development] pbailey212:
It would clear up the threads of people complaining about random reboots. You should also have the minimum set to atleast 600 by default. It will help with "SODs." I might blow the dust off my build box and tinker around with this tomorrow
[Kindle Fire Android Development] AgentCherryColla:
A lot of Devs do that these days. That would be a great Idea.

Is there a UV, or does that needa be done. I'm learning a lot about about making kernels via soucre. Once this is public, I'll want to make a UV kernel. It's all about that 2% 5% and 8%.
[Kindle Fire Android Development] Damedus:
Can't wait, since the kindle is my Android option until I can grab the cash to buy an Asus prime or is there a better one than the prime?
[Kindle Fire Android Development] leoinj:
Hashcode, Thanks for all the hard work and secondly for keeping us in the loop.

I use CIFS on a regular basis. I would love to see it integrated into the kernel. It would be great if this feature could be tacked on to the community wishlist.

Also, will the kernel be MIUI ready or will it need more work?
[Kindle Fire Android Development] Hashcode:
CIFS / TUN are already in the config / build.

And it should be MIUI ready once it's done.
[Kindle Fire Android Development] astmario:
When, or better say, if you manage to find working DucatiMM bin or it source, would hardware decoding of video material have same capatibilities as now?

As I understand, hardware decoding is working in stock kernel+stock ROM, but you can only decode up to 720p and MP4 only, acceleration of MKV files is not available.

Is something changed in new binary capatibility-wise?

I know that there isn't much space on Kindle for 1080p mkv video, but it is real PIA to encode movie to be able to watch it knowing that other devices with same hardware actually CAN playback it with HVA.

Again, I do know that this is something that is not important right now, but if you ever find source for HVA and if you have time and willpower to do it, can you check this out?
[Kindle Fire Android Development] Techlyfe:
If the almighty Hashcode doesn't know the answer to this, the rest of us haven't got a clue... ;)

BTW Great F'n Job Hashcode. Your my hero!
[Kindle Fire Android Development] boomn:
MKV is not a video codec itself, it is a container file that wraps around the video data and other related pieces (audio file, sync info, subtitles, etc). An MKV could contain video data in a format that Ducati can handle or in one that it can't. Lots of MKV files are encoded in h264 which Ducati is definitely designed to accelerate. However even a format like h264 that Ducati can accelerate could be encoded in a profile that is too much for it to handle, such as over 30 fps, but I don't think that should really be an issue you'll have to worry about.

Also the video player you're using also has to know that hardware acceleration is available for a given format and correctly send the video data to be decoded. So when you can start testing these things with a released kernel make sure to check deeper into what codec your MKV files are using and also try different players to make sure it isn't a limitation or bug in the one you're using.

I don't know about the exact capabilities of this hardware in regards to 1080p though
[Kindle Fire Android Development] Krunk_Kracker:
You are a super user, amongst users.

Thanks for all your efforts.
[Kindle Fire Android Development] ontwowheels:
Indeed
[Kindle Fire Android Development] johnwayne007:
Such great work being done, i'll gladly test this when you need testers. If i was a good coder, i would help debug as well. lol
[Kindle Fire Android Development] NRGZ28:
I'd be willing to chip in a few bucks to keep you caffeinated during the nights you work on this kernel. Anybody else with me ?
[Kindle Fire Android Development] theholyfork:
Definitely, with what this could do for the Fire, it'd be more than worth it.
[Kindle Fire Android Development] WolfV2:
Looks great, thanks for your hard work!
[Kindle Fire Android Development] intersectRaven:
The PVR initialization is the same problem I'm currently encountering in my backport attempts...seems I was close to it... :p Anyways, keep it up! I think it's better in the long run to have a 3.0 kernel anyways. :)
[Kindle Fire Android Development] rua_boy:
Bravo you guy :D
[Kindle Fire Android Development] symbiiote:
this is GREAT news!! im getting tiered of CM7 lol
[Kindle Fire Android Development] JoshuaLintag:
So Bluetooth works now because you have full OMAP4 support?!
[Kindle Fire Android Development] csholmq:
No. We don't have a bluetooth chip so support.
[Kindle Fire Android Development] Veritass:
U sure about that I remember people saying we do it's just not working or something
[Kindle Fire Android Development] dnd61:
waiting for testing
[Kindle Fire Android Development] isaiahhhhh:
After further probing it was discovered that the specific chip inside the kindle fire does not support bluetooth, also, just so you know hashcode, i'm writing a letter to the pope proposing you be made a saint for this...
[Kindle Fire Android Development] Talnaj:
That's great, waiting for your working ICS ROM.
[Kindle Fire Android Development] ygvuhb:
very happy to see the news of kernal 3.0:)
[Kindle Fire Android Development] CptanPanic:
Beer money sent. Good work.
[Kindle Fire Android Development] csholmq:
It's pretty clear actually.
[Kindle Fire Android Development] Stevethegreat:
What about bluetooth via USB-OTG?
[Kindle Fire Android Development] btonetbone:
First, we'd need USB-OTG!
[Kindle Fire Android Development] Hashcode:
Got past the PVR init today. But I think loading the ducati firmware is causing problems right after. Updated the boot log.
[Kindle Fire Android Development] jardivben:
Keep on truckin' man! We all appreciate what you do!
[Kindle Fire Android Development] intersectRaven:
What did you modify? I could use that for my backport. Keep it up! We're all anxiously waiting for a 3.0 kernel! :)
[Kindle Fire Android Development] Krunk_Kracker:
I love Ducati's.

Baddatish!
[Kindle Fire Android Development] Hashcode:
Its a combination of matching the kernel PVR version with the binaries you use in userspace, and getting the display setup correctly as well as dmm/tiler/ion.
[Kindle Fire Android Development] intersectRaven:
I thought so...oh well, I'll revisit it once I have the time again. Hopefully you'll be finished with 3.0 before then. :p
[Kindle Fire Android Development] Veritass:
Ah damn thanks for the insite