Develop Bugs

[Q] Some WIFI Problems with FROYO X on Rhod210 - HTC Touch Pro 2

Hi, I noob on this of an Android Phone, I have a HTC TOUCH PRO 2, RHOD210.
I install the FROYO X 2011.01.12 and i put the kernel that have the packet than run the camera and this is OK.
My problem is that the wifi interface is not workink, i am try a lot of solutions that found in this forum, but nothing is ok for me, i change the rootfs like suggest in a forum, modify the wifi-nvram.txt and put the mac address of the wifi, i update the kernel to Latest Kernel Commit# 1253, and i have the same problem.
could someone tell me how to solve the wifi of my rhod210?
Please, I do not want to use windows mobile

How about you just run with vanilla FRX03 and then try to get fancy with it?
Let us know how that works, then we can work on updating your kernel. If you're a noob at swimming, you don't start in the deep end...

arrrghhh said:
How about you just run with vanilla FRX03 and then try to get fancy with it?
Let us know how that works, then we can work on updating your kernel. If you're a noob at swimming, you don't start in the deep end...
Click to expand...
Click to collapse
Sorry, i'm only was trying to solve the problems for my self.
I understand that some of these RHOD210 if they have managed to run the wifi.
I tell you that I use from the beginning FRX03 and it worked well, at least part of the telephone, sound and GPS, but other things did not work, so I started to search the forums and trying different solutions. but I have not found a way to walk the wifi which is what most interests me, so probe, with the latest versions of the kernel etc.
Thanks, I know I'm a rookie, but I like trying to find solutions to the problems I have ....

kleper said:
Sorry, i'm only was trying to solve the problems for my self.
I understand that some of these RHOD210 if they have managed to run the wifi.
I tell you that I use from the beginning FRX03 and it worked well, at least part of the telephone, sound and GPS, but other things did not work, so I started to search the forums and trying different solutions. but I have not found a way to walk the wifi which is what most interests me, so probe, with the latest versions of the kernel etc.
Thanks, I know I'm a rookie, but I like trying to find solutions to the problems I have ....
Click to expand...
Click to collapse
Yes, and I'm trying to help you triage. You said a lot in this post, but didn't answer my question.
Does wifi work with a vanilla FRX03 bundle?

arrrghhh said:
Yes, and I'm trying to help you triage. You said a lot in this post, but didn't answer my question.
Does wifi work with a vanilla FRX03 bundle?
Click to expand...
Click to collapse
Does't work wifi in vanilla FRX03, in fact, the phone worki slow with this kernel, with FROYO is more faster.
Thanks.

kleper said:
Does't work wifi in vanilla FRX03, in fact, the phone worki slow with this kernel, with FROYO is more faster.
Thanks.
Click to expand...
Click to collapse
Erm, I guess I should be more specific.
Where did you download vanilla FRX03? Also, FRX03 is Froyo, so I assume you mean that Froyo 'X' build tiad8 put together.
Also, I'm not sure what you mean "slow with this kernel" - by vanilla FRX03 build, I mean the complete bundle - not just the kernel. Plus, kernels are not tied to system images... So I'm not sure what you mean.

arrrghhh said:
Erm, I guess I should be more specific.
Where did you download vanilla FRX03? Also, FRX03 is Froyo, so I assume you mean that Froyo 'X' build tiad8 put together.
Click to expand...
Click to collapse
Yes, is this build, i look de dmesg logs of the phone, and i see an error that say: can't found the mac address of the wifi. and, i look the file, wifi-nvram.txt and this file have the mac address that i look on windows mobile.

kleper said:
Yes, is this build, i look de dmesg logs of the phone, and i see an error that say: can't found the mac address of the wifi. and, i look the file, wifi-nvram.txt and this file have the mac address that i look on windows mobile.
Click to expand...
Click to collapse
I thought I already directed you to this thread, but it seems to be your issue... so follow these directions. See F22's post.

arrrghhh said:
I thought I already directed you to this thread, but it seems to be your issue... so follow these directions. See F22's post.
Click to expand...
Click to collapse
I do that, and don't work for me.
Thanks

kleper said:
I do that, and don't work for me.
Click to expand...
Click to collapse
Well then, I guess you just can't have wifi...
Honestly, every single person either wifi "just works", or they have to do the wifi-nvram trick. I've never heard of anyone not being able to use wifi, that didn't try the wifi-nvram trick - and those people were definitely in the minority. Vast majority of people, wifi works perfectly fine for.
Please, be a little more diligent. I can't do this troubleshooting for you, I can only point you in the right direction. I need you to do some legwork, as I can't see what you're doing.

arrrghhh said:
Well then, I guess you just can't have wifi...
Honestly, every single person either wifi "just works", or they have to do the wifi-nvram trick. I've never heard of anyone not being able to use wifi, that didn't try the wifi-nvram trick - and those people were definitely in the minority. Vast majority of people, wifi works perfectly fine for.
Please, be a little more diligent. I can't do this troubleshooting for you, I can only point you in the right direction. I need you to do some legwork, as I can't see what you're doing.
Click to expand...
Click to collapse
Fine, i go to format again my SD-CARD and start from zero, any installer recomeded? or pick the installer that i want?

how do I find out my exact model, I'm assuming is that it's RHOD210 for photos and that according to information I have read I understand that T-Mobile only has this HTC TOUCH PRO2, can that be part of my error, there is a way to identify exactly which model is?

kleper said:
how do I find out my exact model, I'm assuming is that it's RHOD210 for photos and that according to information I have read I understand that T-Mobile only has this HTC TOUCH PRO2, can that be part of my error, there is a way to identify exactly which model is?
Click to expand...
Click to collapse
Sticker underneath the battery - not on the battery itself. It's usually in tiny gray font.
kleper said:
Fine, i go to format again my SD-CARD and start from zero, any installer recomeded? or pick the installer that i want?
Click to expand...
Click to collapse
Well, I'd format with the HP tool. (Full format, FAT32) Download this bundle as well.

[SOLVED]
Thank you very much to everyone who answered me and all the developers of this project so interesting, yesterday succeeded in solving the problems I had, my SD formatting, reinstalling Froyo x version 2011.01.12 and puts a kernel of the chamber, after That did the trick again wifi-nvram.txt file, according to the link that let me arrrghhh one of the threads of this forum, after that the WIFI has started to work wonders.
Then my HTC Touch Pro 2, RHOD210 remain with:
WIFI
CAMERA
GPS
PHONE, DATA AND YOU
AUDIO
Thank you very much.

Remember to use zImage and Modules package from the same place and that only WPA is working , NO WEP !

eu0741924381 said:
Remember to use zImage and Modules package from the same place and that only WPA is working , NO WEP !
Click to expand...
Click to collapse
WEP actually seems to work on mine. Strange as that is.

Other problems
These days I've been testing my phone RHOD210 Android, after having settled about the WIFI, but I noticed a problem is that the phone is locked, I can receive a call and make a call, and thereafter ceases to operate the module telephony, change the 1214-Dirty kernel that runs the camera for the 1253 and I have the same problem, another thing I noticed is that the speakerphone does not work completely, it is telling me the microphone works but not the headphones, someone happened?

kleper said:
These days I've been testing my phone RHOD210 Android, after having settled about the WIFI, but I noticed a problem is that the phone is locked, I can receive a call and make a call, and thereafter ceases to operate the module telephony, change the 1214-Dirty kernel that runs the camera for the 1253 and I have the same problem, another thing I noticed is that the speakerphone does not work completely, it is telling me the microphone works but not the headphones, someone happened?
Click to expand...
Click to collapse
Uhm... the older kernel doesn't have the commits for speakerphone mic I would say. Once it all gets committed to GIT it will be a lot less confusing - just a lot of code that's in testing right now basically.
jchutch2 said:
WEP actually seems to work on mine. Strange as that is.
Click to expand...
Click to collapse
WEP should never, ever be used in any circumstances if it can be avoided. That protocol is extremely insecure...

arrrghhh said:
Uhm... the older kernel doesn't have the commits for speakerphone mic I would say. Once it all gets committed to GIT it will be a lot less confusing - just a lot of code that's in testing right now basically.
Click to expand...
Click to collapse
What kernel do you recommend for my RHOD210, the 1253 is doing that the phone will be frozen and I have to Quiaro the battery and put it again to restart the system.
Wonder that in the future will be able to remove the windows and flash the device with adro to make it natively? : D
Thank you very much

kleper said:
What kernel do you recommend for my RHOD210, the 1253 is doing that the phone will be frozen and I have to Quiaro the battery and put it again to restart the system.
Wonder that in the future will be able to remove the windows and flash the device with adro to make it natively? : D
Thank you very much
Click to expand...
Click to collapse
Well, I'd recommend 1250 then I guess... Usually I recommend the newest GIT kernel, which is currently 1253.
FYI, you already can remove Windows and flash the device to run Android natively. It's just not as stable as haret, but it's getting there. Plus, it's only a partial NAND boot - only init and the zImage are actually loaded on the MTD if I'm not mistaken, everything else is on the SD card (which is still 99% of the data...)
But, if you're feeling brave and really do want to completely get rid of WinMo, NAND boot away... can't say I didn't warn ya

Honeycomb 3.0

Hi,
Attached is a build of Honeycomb for DesireHD, I managed to find this by browsing the net and take no credit for creating it whatsoever.
I'm hoping one of our more clever members can do what needs doing with this to make it work on our beloved HD2.
Thanks.
http://www.multiupload.com/DLJ46IG55Q

Nobody is interested? Or is it a fake? Can anybody (with the right skills and tools) check this please.

???
Are you serious ?! someone can verify that build or can you make some screenshots ?

Could be, but dont know if his link is trusted.
http://tweakers.net/nieuws/72741/ontwikkelaar-installeert-android-honeycomb-op-htc-desire-hd.html
Also wrong section.

honeycomb is not really made for phones as I understand?

FrAsErTaG said:
honeycomb is not really made for phones as I understand?
Click to expand...
Click to collapse
Yes that's what i read
but hey
DFT can make it a reality as usual XD

If you check the link in my post, ist already ported and working.
There is a video there to, its a Dutch site though.

Yes its ported to EVO & is working..!!!
PS: - I haven't tried yet though
The LINK
[ROM-DEV] ||Honeycomb on EVO||Alpha||SpyderComb||Honeycomb Android 3.0||2/17/2011||
http://forum.xda-developers.com/showthread.php?t=957842

It is a genuine link, I haven't tested because I don't have a desire, I have seen video footage of it running from the same source and I have inspected the file which looks about right to me, just needs correct drivers and repackaging I believe. If only I knew how to do the repackaging and which driver files were needed I would do it myself.
Yup this is built for tablets and not phones but there are a few tablets with screens not much bigger than our hd2's. It may not even be practical for daily use but I'd love to have a play. : )
Sent from my HTC HD2 using XDA App

May be we can have a working one on our HD2's, can't say, DFT & the cheifs here ROCK..!!!
I like the lock screen & the home screen, it a really an evolution from the older Android Versions..!!!
So hope we get a working port pretty soon..!!!

here's a video for DesireHD release..
http://www.youtube.com/watch?v=t5-yO4FOAvI&feature=player_embedded#at=75

I know that mdeejay or one of the other devs on here could get it working in no time, I just don't have the knowledge, fingers crossed.
Sent from my HTC HD2 using XDA App

the expert cooks should be working to port it to the archos tablets

Booted it on my HD2, but... it lags, nearly nothing works by now etc, and it's hard to hit interface buttons... not sure this will be really useful, but I'll try to work on it
Don't ask for upload please...

Can someone point me in the direction for a tutorial for creating clockwork mod roms please?

this would be probably better suited for viewsonic g tablet

Probably, would still be fun to play with on my phone though.
Sent from my HTC HD2 using XDA App

I haven't had any fun
Nothing really works, sdcard mount, wifi, radio, bluetooth, etc etc, even some buttons are not properly mapped, so i couldn't turn the screen off, i haven't took a closer look though.
Default launcher, and some interface parts lag SO much
But this will really take time, cause everything should be fixed, and cause it's still preview SDK - not really worth it.

imilka said:
I haven't had any fun
Nothing really works, sdcard mount, wifi, radio, bluetooth, etc etc, even some buttons are not properly mapped, so i couldn't turn the screen off, i haven't took a closer look though.
Default launcher, and some interface parts lag SO much
But this will really take time, cause everything should be fixed, and cause it's still preview SDK - not really worth it.
Click to expand...
Click to collapse
i appreciate you taking the time and look forward to IF anything can be done.

Would someone mind posting the half working version so I can have a look please?
Sent from my HTC HD2 using XDA App

Letting this die. New dev and user threads created.

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

Modifying CyanogenMod 7 for Nook Color to work on the N2E

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!

[Q] Thanks Hashcode for the new CM11!! OTG?

Hashcode thank you so much for all the work that you have done for the Kindle Fire HD! The new CM11 is working great on my device! I have read several of your post stating that you are trying to find the time to work on the OTG problem with the Kindle Fire HD. Have you or anyone else made any progress? I have seriously spent hours upon hours researching this topic on the internet. Watched every youtube video I could fine and have searched the XDA forums. I have tried every powered USB hub configuration I could possibly think of and I just can't find the solution. Is there something that I am missing? If you have any suggestions, could you or anyone else please point me in the right direction? I use my Fire HD for meetings and such at the office and a mouse, keyboard and flash memory would be so convenient!
Thank you again for all of your hard work!!
Regards,
Beaker319

It's disabled in the kernel, if you want it enabled you will have to compile your own kernel and flash it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

Thanks
stunts513 said:
It's disabled in the kernel, if you want it enabled you will have to compile your own kernel and flash it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thank you for your reply! Is there a place I can start for a tutorial on how to do this? I really enjoy a puzzle!!

OK I have some experience with this but it's a bit different for mobile devices. Lookup a basic tutorial on Google for compiling a Linux kernel. And what I would do is install a Linux distro, like Ubuntu 13.10, and download the cm sources for cm 11 following hashcode's instruction on his post cm 10.1 post, but use the cm 11 and such repos instead. You will need I would recommend around a 50 GB partition for Ubuntu if you plan on doing this, because the source code of cm + the device tree is at least 15gb, probably bigger for cm, I am compiling a different ROM so it is probably less in my case, anyways the compilation of the ROM takes up a huge amount of space, but I'm a but unaware of the kernel compiling process for android devices in one sense, I am not sure if the kernel is recompiled by the ROM compilation or if you have to do it manually. If you have to do it manually you will want to load up a custom defconfig that hashcode made for our device then check off the otg support before compiling. If you never have compiled a Linux kernel before, I recommend trying to compile one for your PC first to get the hang of it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

Beaker319 said:
Hashcode thank you so much for all the work that you have done for the Kindle Fire HD! The new CM11 is working great on my device! I have read several of your post stating that you are trying to find the time to work on the OTG problem with the Kindle Fire HD. Have you or anyone else made any progress? I have seriously spent hours upon hours researching this topic on the internet. Watched every youtube video I could fine and have searched the XDA forums. I have tried every powered USB hub configuration I could possibly think of and I just can't find the solution. Is there something that I am missing? If you have any suggestions, could you or anyone else please point me in the right direction? I use my Fire HD for meetings and such at the office and a mouse, keyboard and flash memory would be so convenient!
Thank you again for all of your hard work!!
Regards,
Beaker319
Click to expand...
Click to collapse
Did you end up compiling for USB OTG compatibility to be enabled?

No
blickblocks said:
Did you end up compiling for USB OTG compatibility to be enabled?
Click to expand...
Click to collapse
This looks way to complicated for me. I will leave it to the professionals.

stunts513 said:
It's disabled in the kernel, if you want it enabled you will have to compile your own kernel and flash it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
After doing all the reading I can, I'm of the opinion that it just won't work. If it was as simple as enabling it in the kernel, I would bet that it would be done by now.
However, I don't know anything, so I'm at the mercy of all the smart people here!
-L

stunts513 said:
It's disabled in the kernel, if you want it enabled you will have to compile your own kernel and flash it
Click to expand...
Click to collapse
The question is whether OTG detection is implemented for this device, there are two power controllers on this device that may handle ID pin of a USB port, and can handle power output for connected device. First twl6030, I believe it is used just as multi-channel power controller for SoC an other periferial devices, it also has OTG module and may supply power to connected device.
Second smb347, is actually a battery charget and I believe VBUS is connected to it, it supports USB power output of up to 750mA, but I am not sure if there is a driver in linux kernel that may use this IC to output this power.
So I believe it's possible to have OTG wokring, but it may need some R&D and not just enabling it in config.

stunts513 said:
It's disabled in the kernel, if you want it enabled you will have to compile your own kernel and flash it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Why would this be "disabled"? It looks like everyone wants this.. Did someone really "turn it off"? Doesn't make any sense.
-L