LAST 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 detail
UPDATED 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)
Glad to hear it's coming along well. Keep up the good work!
Great news. Waiting for the kernel
Sent from my Kindle Fire using xda premium
STOKED!
Thanks Mr. Hash!
I have absolutely know idea what your talking about.
Thank You for being so smart.
kdkinc said:
I have absolutely know idea what your talking about.
Thank You for being so smart.
Click to expand...
Click to collapse
It'll make Netflix work on the Kindle. And stuff... like that. And some games too.
Hashcode said:
It'll make Netflix work on the Kindle. And stuff... like that. And some games too.
Click to expand...
Click to collapse
Love the layman's speak.
kdkinc said:
I have absolutely know idea what your talking about.
Thank You for being so smart.
Click to expand...
Click to collapse
In other words, all your porn will work....
kidding...
THANKS for the update Hash.....GOOD LUCK!!
You are doing the Lord's work here, man. I may not post very much, but I'm monitoring and your hard work is appreciated and my guess is you will get many accolades and hopefully a good shot of donations for this
Oh my god i love u !
Posrting just to show my support, if there is anything that a noob can make to help, i am more than glad to help
I volunteer as a crash test dummy...errr, Tester. Just say the word.
CM7 Infuse - XDA Premium
CM7 Infuse - XDA Premium
This is really good news. I have been waiting for it. Thank you for massive contribution for the community
Sent from my Amazon Kindle Fire using xda premium
Hardware acceleration! Yay Thanks Hashcode
HW Acceleration is a good news Thank you
I also volunteer to test this
Count me in too for testing! Would sure love to give this a flash when the time comes!
Sent from my Amazon Kindle Fire using xda premium
Im also Available for testing.
you are awesome, thanks for your work
Related
Meizu M9 Q'n'D port for Vision
!!!!!!!!!!!!!!!!!!!
03/20/2011 update: no progress made, throwing in the towel
I can't figure the framework out, every edit I make breaks something else. Long story short, this is a little too in depth for me! Between work and family life, I don't have the time to sink into this to figure it out. For anyone interested in picking the project up, I'd recommend trying to merge an updated Meizu /system dump. Once you do, you'll need to baksmali services.jar and make some major edits. Here's 3 more up-to-date /system dumps I've found around various fora:
system_v1.0.0-13940.zip - Mediafire
system_v1.0.2-14504.zip - Mediafire
system_v1.0.2-15033.zip - Mediafire
Good luck to anyone who decides to pick this up, it's no joke!
END UPDATE
!!!!!!!!!!!!!!!!!!!
Here's a working port of the Meizu M9 ROM for Vision! I need your help debugging and testing the ROM. This is to be considered totally experimental, and is still in need of further development. I wouldn't recommend using it as your daily driver (although I suppose you could ). I'm looking for input from other hackers on fixing what's broken. Thanks!
Flash it with CWM. It will work with the latest version available in ROM manager.
Thanks to:
siulmagic - he started the port and got it booting. This wouldn't be possible without him.
eViL D - Pieces of this were taken from his MT4G port.
meltus - Pieces of this were taken from his N1 port.
XxDaLoWeSt1xX/MagnusRagnarok - Their work porting it to the EVO
Click to expand...
Click to collapse
Now, on to the details!
What works:
- Phonecalls/SMS
- Audio
- Microphone
- Data (APNs should work automatically)
- SD Card (recognized by phone)
- Sensors
- Keyboard
- Backlights
- Softkeys
- Accelerometer
- Haptic Feedback (needs to be enabled in Accessibility Settings)
- USB (debugging needs to be enabled in USB settings)
- Rooted
Click to expand...
Click to collapse
What's broken:
Major
- Wifi - enabling causes the phone to reboot
- Bluetooth
- Camera
- Mounting SD card via USB
Minor
- Resolution issues (framework edits are needed)
- Graphics issues (white on white text, etc)
- Time isn't automatically set properly. Manually set your time if it's off.. YMMV.
- Random Chinese text here and there
Click to expand...
Click to collapse
What I haven't tested yet:
- GPS
- MMS
Click to expand...
Click to collapse
Other things you should be aware of:
- The M9 ROM doesn't seem to sync well with Google. Your contacts will not be synced. I believe this is the intended behavior of the ROM itself, but I need to do more testing/investigating.
Click to expand...
Click to collapse
Included apps:
- Some Google Apps (Gmail/Maps/Chrome to Phone/Voice/Youtube/Search/etc)
- Wifi Calling (useless for now, wifi doesn't work)
- ROM manager
- Titanium Backup
Click to expand...
Click to collapse
Screenshots:
Disclaimer:
I'm not responsible if you break your phone with this. Please be careful.
Click to expand...
Click to collapse
Last but not least...
DOWNLOAD
V0.1 - Multiupload
Wow, this looks like an awesome ROM. Hope you get everything working soon
Nice
Sent from my Liquid Metal using XDA App
Awesome you got sound working, and sensors. Hopefully you get this port further than what I did.
Sent from my Incredible using XDA App
I've always wanted to try Meizu out.
Best of luck.
p.s. - bug reports if I find any time to tinker with it.
Great job. I hope all the remaining features works soon.
oh .. my .. god
i have first seen this phone during my stay in china and am really interested in the whole meizu thing!
I kinda need my phone to be stable for at least the next week cuz ill be without internet or anything (going snowboarding, woohoo), but after that i will definitely flash this and help finding bugs and whatnot
I tried it looks great loved the lock screen icons everything but ill just wait until its finally ported
Thanks
Sent from my G2 using XDA App
I can't thank you enough for porting this rom across, although it is still in early stages I have been waiting for someone to port it across. Again thanks so much!
Hi, will other languages than german be included in this rom ?
Great work! I love you man.
Sent from my HTC Vision using Tapatalk
WOAH. Looks really interesting. With the google sync problem:
you try skipping then logging in via market?
Wanna test but i kinda need wifi. Definately flash when fixed though
I never thought we'd get a port of this awesome looking rom, I'm SUPER EXCITE for this!
b1oh4zard said:
Hi, will other languages than german be included in this rom ?
Click to expand...
Click to collapse
I haven't done any translation work at all yet. Whatever is there is what came packaged by Meizu
Sent from my HTC Vision using XDA App
tun4f1sh said:
I haven't done any translation work at all yet. Whatever is there is what came packaged by Meizu
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
i very much doubt there a german translation, this rom comes in Chinese only, so they only translation there is, its for English.
OOOHHHH YYEaaahhh
tun4!! your are the man drop everything your doing and give this rom hell bro.. i think this rom is overlooked and thanks to you it shall finally be recognized!! hands down a much need refreshment to the community!
wow.., i just want those call recorder
Excited!!!!!!!!!!!!!!!!
Dude, I'm so excited for this port!
Get Wi-Fi Working and I'm all over it!
Good job by the way! I would flash it immediately but I don't have a data plan cause I don't really need it... I have Wi-Fi all the time.
btw mountig sdcard via usb works, you just have to do it a couple of times, eventually it will work. thats how it was when i last worked on my build.
hey guys,
i just tried it out on my gsm htc vision and i had a lot of problems even if the rom boot.
no sim detection. no keyboard/trackpad/buttons working.
i just can't try it more since i can't lock/unlock the screen and can't use the home button.
hope you'l lfix it, this rom sounds really interesting.
Found this via Google tonight, anyone have any insights?
Did someone get bluetooth working?
pastebin.com/YgRKdpej
intel352 said:
Found this via Google tonight, anyone have any insights?
Did someone get bluetooth working?
pastebin.com/YgRKdpej
Click to expand...
Click to collapse
Loading the drivers doesn't mean anything, show me working hciattach and I'll believe it.
If someone wants to donate a broken KF I can find if it's connected in a useable way and if so make it work. Really broken is ok, as in mauled by wild dogs and drowned in the ocean broken. All I need is the mainboard to be physically intact even if it doesn't work.
pokey9000 said:
Loading the drivers doesn't mean anything, show me working hciattach and I'll believe it.
If someone wants to donate a broken KF I can find if it's connected in a useable way and if so make it work. Really broken is ok, as in mauled by wild dogs and drowned in the ocean broken. All I need is the mainboard to be physically intact even if it doesn't work.
Click to expand...
Click to collapse
I hate that my device is not broken but at the same time I'm glad it's working
Glad to see that some people gladly help with the development for the Kindle Fire though.
A pastebin by the same user shows dmesg output showing bluetooth loaded (just fyi):
http://pastebin.com/a4m6jc7T
intel352 said:
A pastebin by the same user shows dmesg output showing bluetooth loaded (just fyi):
http://pastebin.com/a4m6jc7T
Click to expand...
Click to collapse
That looks like output from the diagnostic boot mode (bootmode 8000, DON'T DO THIS WITHOUT FFF INSTALLED). Not sure if BT is in the kernel out of laziness or if there's something else to be found...
pokey9000 said:
That looks like output from the diagnostic boot mode (bootmode 8000, DON'T DO THIS WITHOUT FFF INSTALLED). Not sure if BT is in the kernel out of laziness or if there's something else to be found...
Click to expand...
Click to collapse
Considering bt hardware is on board and in kernel, would be nice if it could be easily enabled/used
Would running a Linux distro on the device pick up Bluetooth hardware and allow you to do something with it? I have Debian running via debootstrap loop file (installed with app called Linux installer on market) but i don't use any ui and don't know how to check for it in a terminal
I'm trying to get up to speed to look at bluetooth too - from what I understand of what I've found so far, it seems like it kinda has to be there and be usable unless they went out of the way to disable it. I suspect making hardware changes to disable something they could just not build into the OS to disable would have been unnecessarily expensive.
I am thinking this because:
1) Wikipedia shows the Kindle Fire is based on the OMAP4430 PandaBoard
2) Pages 36 of the PandaBoard System Reference Manual:
The PandaBoard provides a module (LS Research Inc. P/N LS240-WI-01-A20) that provides a Bluetooth interface, a 2.4 GHz 802.11b/g/n interface, and an FM interface. This module may be found on sheet 14 of the schematics (reference designator U4). It uses Texas Instruments’ WiLink TM 6.0 solution.
Click to expand...
Click to collapse
3) According to the Mouser page for part #LS240-WI-01-A20, they share the same antenna:
Both WLAN and Bluetooth share the same antenna port.
Click to expand...
Click to collapse
So the functionality is there - it's all on the same chip and uses the same antenna as the wifi...
What I'd like to do is get to where I can build CM7 and poke around the code - I've got an OS dev (Windows) background but I've never done anything on Linux so it's taking some time to get the build setup. I've got ICS (not for the Fire) setup to build, just because the directions I was following were for that. Now working on CM7 for the Fire.
If I can get where I can build and flash my own CM7, I'm willing to spend some time doing some trial and brick/fix and trial again...
sweet @LanceDiamond looks like you did some homework
so you have a linux distro up and running with stock asop synced?
cyanogenmod has a wiki on how to compile from their source http://wiki.cyanogenmod.com/wiki/Building_from_source its pretty massive and as far as i know, you need the whole frigging thing. as far as I can tell, the info for each device is pretty much the same until it comes to specifying which device your building for. you will probably need to git clone extra stuff into the source and probably edit... something in order to build specifically for the kindle fire... its been a while sense I messed with the source and I never manage to make it to these forums until im tired, so sorry if im kinda all over the place
if someone can develop an app that actually turns bluetooth on in kindle fire, I will be the first one to commit buying the app. since we are in this topic, does kindle fire has microphone that can be enabled as well?
jendol said:
if someone can develop an app that actually turns bluetooth on in kindle fire, I will be the first one to commit buying the app. since we are in this topic, does kindle fire has microphone that can be enabled as well?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1363215
jendol said:
if someone can develop an app that actually turns bluetooth on in kindle fire, I will be the first one to commit buying the app. since we are in this topic, does kindle fire has microphone that can be enabled as well?
Click to expand...
Click to collapse
No built in microphone but http://forum.xda-developers.com/showthread.php?t=1363215
Doesn't seem to work with Skype etc. though.
Well....yes and no lol.
I have an Ubuntu VM using VirtualBox with somewhere around 30GB of stuff. I think I actually built some form of stock (non KF non cm7) Android. Then I started reading up on CM7 and Jackpot/Whistlestop work. Git cloned CM7KF tree from Whistlestops Git page. Followed directions to link in directories in spite of being a Linux idiot.
I now have a build that builds a bunch of stuff but eventually stops with a multi paragraph message about how my code is including something not normally included or something like that. Not home again till Monday so can't get the exact error... I may rebuild the VM from scratch when I do get back to it just to eliminate any weirdness from my not knowing what I was doing first time.
Also got a little sidetracked playing with cm7 once I flashed it
One slightly strange thing - in whistlestops cm7 directions for linking in the CM7KF tree, if I follow those steps to the letter I wind up with a dir like this:
/vendor/amazon/amazon/blaze
I assumed that was wrong and I want the tree to look like the others there, ie:
/vendor/amazon/blaze
So I didn't mkdir amazon first and that seems to give me the desired structure....
Sent from my GT-P1000 using Tapatalk (and apparently Taps thinks my kindle is a GT-1000 now with cm7/new build.prop)
Really ?? I dont know KF has bluetooth. Why Amazon put Bluetooth there without software to use ???
I've got my build working and I've spent a lot of time digging...
It looks like, as someone said up above in this thread, the kernel needs to be built with bluetooth enabled. And you need the driver and the firmware files put in the right place in your android build tree. Then you'd need to do something to cause the driver and firmware to actually wind up in an image when you build.
I have the files and I have a working CM7 build. I *think* the CM7 kernel has bluetooth enabled so I am thinking it might be possible to hack this around to work without having to actually build the linux ARM7 kernel.
I'm at least encouraged...
FYI, I found the driver here - not sure if it'll work, but easy enough to try - the hard part is going to be figuring out the editing to get it in an image...
awesome work, thank you
Bluetooth would be awesome!
Hopefully the driver is compatible with wiimote and similar programs.
Lance you are teasing me! i like what i am hearing... if theres anything i can do please let me know got a research junction you want to pass off let me know im good with rooting people on...
well you should definitely toouch base with Whistlestop the dev running the cm7 build if you didnt know. im going to google my eyeballs out on your details. This thing has bluetooth i can just smell it.
Sent from my HTC Vision using xda premium
So let me get this straight? Bluetooth is possible, but not supported by the kernel?? This is simular to the iPhone 2G/iPod Touch 2G having bluetooth radios. But no supported by the kernel.
Sent from my HTC myTouch_4G_Slide using Tapatalk
Kindle Fire Bluetooth
someone asked why Amazon would put bluetooth in the Fire but not have it active? i think the answer is simple. "introducing the KF2. one of the new features is bluetooth". i'm sure Amazon has other features built in but not turned on. would make bringing in the next version cheaper for them, imo.
Update: We finally have usb host mode working on leo.
The interrupt problem i was having was fixed by liiochen, right here (his blog). He has also tested a few devices like keyboard, mouse, storage etc..
Attached is the kernel and modules in a cwm zip. usb mass storage, usb charging, usb tether and usb adb will NOT work. adb over wifi should be fine. If you were going to ask, it's based on the latest tytung kernel.
Requirements:
ICS rom
Self powered hub OR a Y USB cable
How to:
1) Reboot to recovery
2) flash file
3) reboot to android
It supports both clk/magldr.
Credits:
liiochen, cotulla, markinus, sven killig, tytung
good luck .
http://forum.xda-developers.com/showthread.php?t=1459304
Good luck
awesome
pirlano said:
awesome
Click to expand...
Click to collapse
Cant wait for this to be functional on our HD2's
great effort out there man !!
good luck with your work !
Hello! Any news about this great project?
Salvestro said:
Hello! Any news about this great project?
Click to expand...
Click to collapse
+1
Sent from my HTC HD2 using xda premium
any news
great that some1 is working on this as its something that i want for my hd2 especially if u can.get tv out working wish ud post news on how ur getting on and more.developers would help u out i think u should do.a poll on how many people want this as id say a large percentage of hd2 owners on here would say they do. when i finally retire my hd2 would be great to turn it into a media centre by connecting it to tv and a hard drive for files. i hope u keep.at it until u get it working and if u want a beta tester count me in!!
Maybe Rick gave up on this thread, considering none of the posts in it (including this one) apart from his have been development related (we are in the development forum...)
Also, don't you think if he had news he'd post it?
mikeysteele said:
Maybe Rick gave up on this thread, considering none of the posts in it (including this one) apart from his have been development related (we are in the development forum...)
Also, don't you think if he had news he'd post it?
Click to expand...
Click to collapse
I haven't given up on this but yeah, such people really do nothing but spam the thread for no reason. I will require 2.6.33 kernel at a minimum to continue because usb stack interface was changed between .32 and .33 linux. So instead of starting from scratch, i have asked tweakos who already has a .33 kernel running perfectly for the source code for me to continue, He mentioned he had some data loss but has a backup and it would take him around 4~5 days to recover and upload that somewhere.
As for the news, whatever news i would have about the host controller wouldn't be understood properly as most of it would be regarding low level stuff or unless the news is about release..
As for the possible uses of usb host would be:
1) USB joysticks, (any controller that works with linux) so you can play psx emulator with real controls, and other supporting games
2) USB TV in, Watch TV on your HD2 using a USB powered TV tuner card.
3) USB TV out, Use larger displays for your HD2 using usb monitors or some kind of usb video adapters certified for use with linux
4) USB sound cards for those who want real quality audio with an external usb sound card, but i think android does not support this. will require GNU/Linux distro.
Infact anything that works properly with USB 2.0 in linux will work in kernel space and can be used by apps which have ability for such hardware.
Wow, that's great. I love USB TV out function.
I want it, good luck
Good luck with this one. It would be great to have on our beloved hd2's
Rick_1995 said:
I haven't given up on this but yeah, such people really do nothing but spam the thread for no reason. I will require 2.6.33 kernel at a minimum to continue because usb stack interface was changed between .32 and .33 linux. So instead of starting from scratch, i have asked tweakos who already has a .33 kernel running perfectly for the source code for me to continue, He mentioned he had some data loss but has a backup and it would take him around 4~5 days to recover and upload that somewhere.
Click to expand...
Click to collapse
How about using my kernel 2.6.35.14 forked from ACA which is forked from Marc? I have done a lot of work making it very stable and fast...
Rick_1995 said:
. There are posts which confirm that OTG worked in froyo sense, so i will be testing the support in froyo roms and gnu/linux builds like ubuntu for further research.
Click to expand...
Click to collapse
Which froyo roms have OTG support?
It would be useful to use one for Ubuntu http://forum.xda-developers.com/showthread.php?t=1025499 (and possibly Debian http://forum.xda-developers.com/showthread.php?t=1029390) via VNC
Thanks
Robbie P said:
Which froyo roms have OTG support?
It would be useful to use one for Ubuntu http://forum.xda-developers.com/showthread.php?t=1025499 (and possibly Debian http://forum.xda-developers.com/showthread.php?t=1029390) via VNC
Thanks
Click to expand...
Click to collapse
Dunno if they would work, btw with my kernel i have usb root showing up but cannot yet test anything because my usb hub seems to be broken and i don't have any usb female port lying around.
OP updated.
Hi sry slightly of topic....is there a new version of magldr in the works? What is the expected time of release?
Many thanks
Sent from my HD2 using Tapatalk
I have, for the most part, returned from my leave of absence and hopefully this time around I will be able to provide you folks with something a bit more useful.
Admittedly, this was a fairly halfhearted attempt but, hey, it's something to start with. I branched the CM7 for Nook Color source. Part of the compilation process involves running a script (system/device/bn/encore/extract-files.sh) that extracts proprietary libraries (or something?) from stock Nook Color, so I plugged in a rooted N2E instead for this step and ripped the files off of it. Some files were missing from the N2E, so I copied those over from a Nook Color. Here's a list of those files:
Code:
/system/lib/libOMX.TI.720P.Decoder.so
/system/lib/libomap_mm_library_jni.so
/system/etc/powervr.ini
/system/lib/libpvrPVR2D_FLIPWSEGL.so
/system/lib/libusc.so
/system/lib/libpvrPVR2D_FRONTWSEGL.so
/system/lib/libOpenVG.so
/system/lib/libOpenVGU.so
/system/lib/liba2dp.so
/system/lib/hw/alsa.omap3.so
/system/usr/share/alsa/init/hda
/system/usr/share/alsa/init/00main
/system/usr/share/alsa/init/help
/system/usr/share/alsa/init/default
/system/usr/share/alsa/init/info
/system/usr/share/alsa/init/test
Compilation of the franken-nook-color source went without problems.
Unfortunately although unsurprisingly, the produced userland doesn't boot. I'll keep y'all updated with my progress; this is only the very tip of the iceberk.
I have two NST so I can use one for testing your rom if you promise no to brick it very often ;-)
I have a NST that, while the 3/4's of the screen is broken, it still functions fine and I can see anything in the top right quadrant of the screen. It doesn't do anything else for me, so you're welcome to brick it in the name of experimentation.
Thanks for the offering! I am not really in need of anything just yet but should anything come up I will PM y'all.
Anyhow, I tried again but this time excluded all the missing prop files from the build by editing them out of device-vendor-blobs.mk. It still didn't work so that means we're probably going to have to find a way to actually debug it instead of using trial and error like we have been.
Maybe there is like, a serial port or something on this thing.
klausef said:
Maybe there is like, a serial port or something on this thing.
Click to expand...
Click to collapse
Yes there is a UART on the OMAP3621.
Still, it's hard to get any info out of TI since it's an OEM part.
Does anybody have a real pinout?
Actually, unless somebody has a dead Nook that you can pull the processor off it would be hard to trace.
I guess the best bet would be to look for suspicious unused pc lands.
Can you toggle the charge light gpio as a progress indicator?
You don't need anything special.
As long as you can boot a kernel, which you can, you can do all your debugging over adb. Just enable adbd in the ramdisk.
The use for a serial console is for debugging KERNEL failures.
The firsts thing you really need to work on instead of just trying to boot CM7, is a compatible NST Kernel. Without a CM7 compatible kernel as far as I know it just won't boot. Once you know the kernel works you should start work on getting /system and such to work, as far as I know the major differences between the Nook Color and the Nook Touch are the input types and display types, which means you'll have to replace the drivers with ones that actually work.
GabrialDestruir said:
The firsts thing you really need to work on instead of just trying to boot CM7, is a compatible NST Kernel. Without a CM7 compatible kernel as far as I know it just won't boot. Once you know the kernel works you should start work on getting /system and such to work, as far as I know the major differences between the Nook Color and the Nook Touch are the input types and display types, which means you'll have to replace the drivers with ones that actually work.
Click to expand...
Click to collapse
Thanks for the direction, I kind of have been seeing that getting this working isn't as trivial as swapping a few files. I've been asking on some Freenode channels about what exactly makes a kernel 'CyanogenMod compatible.' There are clearly people out there who know exactly what facilities and stuff need to be backported, but such people are hard to find. Do you have any idea where this kind of stuff is documented? The CyanogenMod wiki seems a bit sparse, although maybe I haven't been looking in the right places...
If it is of any interest to anyone:
http://tldp.org/HOWTO/Remote-Serial-Console-HOWTO/configure-kernel.html
I've recompiled U-Boot to call our current N2E kernel with a new `console=[...]` parameter, and recompiled the kernel with USB serial support. I figure I should be able to plug this thing into a linux box and just use `minicom` to look at the kernel's output in this manner. I know this probably won't give too much information about userspace issues but at least hopefully it will give some info on why/if/when/where init fails.
It would be nice if a spare UART could be found directly on the board.
http://tldp.org/HOWTO/Remote-Serial-Console-HOWTO/configure-kernel.html said:
The USB subsystem is started rather late in the boot process, console messages printed during boot before the USB subsystem is loaded will be lost.
Click to expand...
Click to collapse
I should be more specific, it's not so much you need to make the current kernel CM7 compatible, as it is you need to make it Android Froyo Compatible, which usually involves porting features from the eclair, if you want to get specifics, try talking with people in #nookcolor or #nook-tablet on Freenode. They may be able to help point you in the right directions for porting the kernel.
Waiting for my NST to come from new continent.
Personally, I would start building original kernel source from b&n. When it works and device boots, then I would clone google repository for kernel 2.6.x and would compare its files with the files from original kernel. And then adding needed source files for booting, and needed device drivers.
I doubt I'll have free time and enough knowledge for that.
Sent from my GT-I9000 using XDA
seeing as we now have the uart http://forum.xda-developers.com/showthread.php?t=1702734 i feel its time to make a cm7 port. it would unlimit the device, and bring it into more compatible apps.
How goes it? Will fundraising speed things up by letting you concentrate more of your time on this project?
imachine said:
How goes it? Will fundraising speed things up by letting you concentrate more of your time on this project?
Click to expand...
Click to collapse
Sorry if you weren't asking me.
I don't write a single line of C code since almost twelve years. I'm a programmer in a very different environment, fact which makes me know that such a port needs a lot of dedication.
In the next weeks I'm gonna be father for the first time and this makes me set completely different goals in my life.
As far as I've understood of cyanogenmod, is that this world is made of brilliant volunteers, some accepting donations, some not. Maybe in the whole cm community, there is somebody with time and experience.
Sent from my GT-I9000 using XDA
I've been considering picking this up as a project, because I'm tired of 2.1, i would like some GB at least I doubt we will see cm9, but cm7 seems doable. I'll have to learn some to do it, but I don't see why it's not outside of reach; now that we have a serial port, and such.
tdcfpp said:
Sorry if you weren't asking me.
Click to expand...
Click to collapse
No problemas, I wasn't. I directed my message at klausef who started this thread, though anyone willing to help out would probably be beneficient from fundraising, were it to start funding a project, instead of a single developer.
If money's a problem, perhaphs starting a kickstarter (or similar) project might help out?
Donating via paypal works as well, but I don't think it's possible to allow public access to account levels in order to motivate the experience of funding, by letting people see how much the project has risen.
i can't wait to get CyanogenMod on my nook! Have you guys discovered anything new?
Cheers!
Soooo, any news? Come on, klausef, we can help! Let us know how the progress is coming along
imachine said:
Soooo, any news? Come on, klausef, we can help! Let us know how the progress is coming along
Click to expand...
Click to collapse
Bump. I've got a great use for a NST / N2E application, and the app is currently compiled for Android 2.2 only. I may not be able to get to the source (and may not be able to make it work in 2.1 even if I did!), so a NST with 2.2 would be ideal!
*omg, thread updating needed*
Hey guys, as some of you might know, I was donated a Galaxy Note 4 (N910C) and am now working on AOSP for it.
The sources required to build a ROM are hosted at GitHub currently:
device: https://github.com/teameos/device_samsung_treltexx/
kernel: https://github.com/raymanfx/kernel_samsung_trelte/
vendor: https://github.com/raymanfx/vendor_samsung_treltexx/
If you want to give this a shot, you should be familiar with git and repo and be able to sync the TeamEos source yourself.
If anybody feels brave enough, give it a try yourself, all the required bits are posted above
TODO/BROKEN:
Bluetooth headset calls (RX works, TX is broken)
Open source AVC (H.264) Encoder is broken (Videos recorded in portrait are rotated by 90° counter clockwise, and there's artifacts all over the place)
Everything else should be pretty much working.
hopefully watching all your work. congratulations.
hey! any progress on this? I'm really excited!
Sent from my SM-N910C using XDA Free mobile app
+1
Congratulations
First success:
The phone is booting and the adb server is starting.
I'm still missing some sensor blobs from stock which causes the sensor layer not to start and thus prevent various other init tasks (such as display, EGL) to crash.
I'm going to work on getting at least display up this weekend.
No promises though.
This is great news. Thanks for this hard work. Thank you for making our donation future experience CM12.
someone was trying to port CM11 to galaxy alpha.. i guess its a similar kernel..
http://forum.xda-developers.com/note-4/development/exynos-543x-android-development-t2949478
dats d link.. jus posting, if it helps u in anyways..
Good luck!
Superb!!!
Awesome work looking forward to seeing it on my N910U... hopefully
Great :good:
Awesome!
More progress today:
The device partially boots now, boot animation shows but that's where it loops.
Sensors are fully working and storage handling (internal storage, external sdcard and usbdisk) have been fixed.
I'm still missing some camera blobs which I believe keep the device from booting up (because it crashes other init services).
I'll look into that tomorrow probably.
All the latest fixes have been pushed to my github repos, so if anyone in here feels like experimenting a bit, let me know how it goes
RaymanFX said:
More progress today:
The device partially boots now, boot animation shows but that's where it loops.
Sensors are fully working and storage handling (internal storage, external sdcard and usbdisk) have been fixed.
I'm still missing some camera blobs which I believe keep the device from booting up (because it crashes other init services).
I'll look into that tomorrow probably.
All the latest fixes have been pushed to my github repos, so if anyone in here feels like experimenting a bit, let me know how it goes
Click to expand...
Click to collapse
These words cause many joys.
@RaymanFX , great work, update the first post with every progres, and for the other guys this a dev thread, dont spam with greets otherwise im sure a mod is gonna close the thread, keep it dev related or someone can open a thread in the general options for this project
Go go go
Progress?
+1
Well, as stated on the first post, it'd probably make more sense to watch my github for progress instead of asking in this thread.. Just saying.
Big progress has been made in terms of audio, as I finally got around to configuring proper mixer paths for audio devices here: https://github.com/RaymanFX/device_samsung_trelte/commit/c5954750b5c13ce9bf27992f145a18a837099e12.
I had to do lots of research because there is little to no documentation on these mixer_paths.xml configs, so I ended up creating it from scratch based on Samsung's UCM config.
The device still doesn't boot further than the bootanimation, but I still have some interesting lines in the logs to solve, for example it still reports invalid input/output devices in audioflinger, which clearly is an issue.
At least the issues preventing us from booting are no actual display issues, but init services crashing.
Also, it looks like the RIL is starting up after adding Samsung's cbd daemon to early init execution (ramdisk), but I don't expect telephony/mobile data to work just yet.