Basically the kernel is between the operating system and the hardware. The better the kernel works, the better the operating system works.
Sent from my Butta'd Kindle Fire using Tapatalk.
Letting this die. New dev and user threads created.
- Thread starter Hashcode
- Start date
- Status
Basically the kernel is between the operating system and the hardware. The better the kernel works, the better the operating system works.
Sent from my Butta'd Kindle Fire using Tapatalk.
It's an effort to a fully stable and working ICS with hw acceleration. And by the looks of things he's doing a amazing job. Thanks hash!
Sent from my Hellfire Kindle using Tapatalk
It runs the rom... It's like the engine of a car and the rom is the body and everything else.
Sent from my HellfireKindle using Tapatalk 2
Last edited:
Sad....God just killed another puppy....
---------- Post added at 09:08 AM ---------- Previous post was at 09:00 AM ----------
I would say the kernel is the operating system, what you see and recgonize as ICS is just the user interface. This coming from my old Linux days, like Slackware version 3...around 1996, when if you wanted to add a piece of hardware like a NIC card you had to recompile the kernel to add support for it. Before the lodeable modules. What you see as ICS is running around the shell which is running around the kernel.
That's hows I sees it...
What is this back light bug people are talking about? I'm using cm9 and nothing seems wrong. Is the bug just in the new kernel?
Sent from my Kindle Fire using Tapatalk
Sent from my Kindle Fire using Tapatalk
This is the development thread for the new 3.0 kernel in development..
So in short, yes, its something wrong with the new kernel (hence it being posted in this thread).
Sigh...if people would just read through this thread, they would realize that what Hashcode has done to create this new kernel is nothing short of miraculous, and once he figures out the hardware acceleration issue, this will easily be the most epic breakthrough for the KF. Glib questions about whether this will be fixed or that - is almost offensive. Come on people, just do a little reading. You'll learn a lot from it.
Sent from my Kindle Fire using XDA Premium
ROM: Energy CM9 Kang Build 3/19/2012
Kernel: 0xD34D
Overclock: 1.3 GHz Max, 800 MHz min. On Demand
Launcher: ADW EX
would just read through this thread, they would realize that what Hashcode has done to create this new kernel is nothing short of miraculous, and once he figures out the hardware acceleration issue, this will easily be the most epic breakthrough for the KF. Glib questions about whether this will be fixed or that - is almost offensive. Come on people, just do a little reading. You'll learn a lot from it.Sent from my Kindle Fire using XDA Premium
ROM: Energy CM9 Kang Build 3/19/2012
Kernel: 0xD34D
Overclock: 1.3 GHz Max, 800 MHz min. On Demand
Launcher: ADW EX
Hey hashcode thanks for the updates! I have a question though. With more devices getting official manufacturer ics updates does that help you in anyway? Specifically the rumor that the droid razr getting ics on the 4th. I know that the are in no way the same product but the do share the TI omap 4430 chip set..does that help or is it a non factor? Thanks again for all you do for the modding community!
Sent from my Droid Razr using XDA
Sent from my Droid Razr using XDA
Just a heads up, there are a lot of Kindle Fire stuff that has made its way into the current 3.4-RC1 kernel source... I'm configuring it right now, just to see if it'll even boot.
a lot like what?
Maybe you can colab with hashcode as per see, you have the knowledge to do this things
Usually device-specific updates are pretty propriety, I think.
The source is not left open for many of the drivers (depending on the manufacturer) so, even if the hardware is similar on every level, you may still have trouble getting the drivers to work.
Are those even words? I realize these comments are just as annoying as annoying comments, but this thread is just buzzing with questions about bugs and features on a pre-pre-pre-Alpha kernel that hasn't even been unleashed yet.
There is a Q&A ICS discussion thread, this is not that thread.
Just go easy, guys. Please. every time you post, I get a notification in my email.
Could someone lock this thread for everyone but Hashcode? Reading questions and answers which already are answered in the OP has lost it's novelty.
Thanks...
Thanks...
- Status
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
229LAST UPDATED: 4/2/2012
WHERE ARE WE NOW? IS IT BOOTING? CAN I GET A NEW ROM W/ AN ICS KERNEL?
Is it booting? Yes.
Is there a new ROM for the kernel? Yes. It's still a work in progress and likely to continue changing as the kernel gets more developed.
Can I test the new ROM? Right now, there's no reason to run this ROM unless you're working on the kernel and/or bug testing. It is booting into the OS now and as soon as I fix up the Wifi and SD MMC mount, I'll probably put up a test link for testers -- lots to bugfix, this isn't "usable" yet. Especially since we don't have the Ducati loading for hw codecs.
How long will it take to fix? There is no way to know. I work on the kernel about 4-5 nights a week, and when I fix something, there's always something behind it which needs fixing as well. I am making good progress (in my opinion), but that may still mean weeks of development.
I'm going to keep a page updated on my blog so that at any point in time if you're curious what the output of the boot up looks like you can go take a look (this will be mostly technical output and don't worry if it much of it doesn't make sense):
http://blog.hash-of-codes.com/kindle-fire-ics/
[NOTE: I've now highlighted items in green which are good and some red items still to be fixed.]
2nd post has the current status in more detail134UPDATED 4/7
WORKING -- WILL NEED TESTING:
EXT4 MMC Filesystem Access
USB Android Gadget with modes like ADB and MTP (Do we want mass storage also?)
Battery / Charger Driver
Display driver / SGX / ION now plays nice w/ 512M memory (originally the 3.0 kernel was hard coded for 1G of memory)
Touchscreen is working
Sensors are working to detect tilt / movement
Power button working (no colored leds yet)
New Audio driver from TI is working (thanks nook_lover!)
Headset output / recording
Internal media partition mount
Ducati binary is being loading by the system now and the OMX server is starting -- NEEDS TESTING -- probably still won't work -- but its progress towards hardware codecs
PARTIALLY WORKING:
New Backlight Driver is now partially working. Won't adjust brightness yet, but it's coming.
:| Wireless device and driver is being recognized. Still troubleshooting.
STILL BROKEN:
:/ Color Changing Power Button Leds - Old Driver needs to be updated
FUTURE CHANGES IF NECESSARY:
- Touchscreen Driver has a newer straight Linux driver available which would need minor Android customization (current driver seems ok for now)
- Charger Driver has a newer straight Linux driver available which could be customized for Android (will probably do this one eventually. The current charger driver is very messy)
- Battery Gauge has a generic 3.0 android driver available. It would need minor customization (may or may not rewrite this one eventually)72Updated #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!
Sent from my DROID4 using XDA57I 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.
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.54Quick 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.
