Related
Q&A isn't the ideal place, but I'm not yet able to post in the dev forum, so...
I've been using the cm10.1 experimental build (p1c) posted by cdesai for the last week or so.
It's very smooth but about once a day the Sleep of Death (I think) strikes.
It never happens when I'm using the tab. A full reset brings it back, but if I don't catch it quickly it will very rapidly drain my battery and turn the tab into a small space heater. Aggravating.
Anyone else have the issue? Any ideas?
Sent from my SCH-I800 using Tapatalk 2
set your brightness to 20% and always turn-off wifi when its not in use ....its works for me....played my tab for 30 minutes and my tablet consumed only 15% of the battery
SORRY FOR MY BAD ENGLISH
*i also turn off mobile data......when i dont need to use the internet....
frrambo said:
Q&A isn't the ideal place, but I'm not yet able to post in the dev forum, so...
I've been using the cm10.1 experimental build (p1c) posted by cdesai for the last week or so.
It's very smooth but about once a day the Sleep of Death (I think) strikes.
It never happens when I'm using the tab. A full reset brings it back, but if I don't catch it quickly it will very rapidly drain my battery and turn the tab into a small space heater. Aggravating.
Anyone else have the issue? Any ideas?
Sent from my SCH-I800 using Tapatalk 2
Click to expand...
Click to collapse
Yeah. SOD probably happens randomly as for me.
Try alroger latest build. running it as my daily driver. no SOD and FC happens in a day.
imadork said:
Yeah. SOD probably happens randomly as for me.
Try alroger latest build. running it as my daily driver. no SOD and FC happens in a day.
Click to expand...
Click to collapse
Thanks, I'll give it a shot.
imadork said:
Yeah. SOD probably happens randomly as for me.
Try alroger latest build. running it as my daily driver. no SOD and FC happens in a day.
Click to expand...
Click to collapse
I always get encryption failed when installing alroger builds - I guess you are not running CDMA (p1c) ?
If you are using a p1c then you are lucky to have alroger working.
cdesai builds work great on p1c but usb tether doesn't seem to work on any CM10.x build yet which is annoying
Re: CyanogenMod 10.1 Experimental Builds
Yup.
I tried alroger's p1c and had the encryption problem. Back to cdesai's build for now.
Sent from my SCH-I800 using Tapatalk 2
frrambo said:
Yup.
I tried alroger's p1c and had the encryption problem. Back to cdesai's build for now.
Click to expand...
Click to collapse
Yeah alroger's newest builds are broken on p1c but if you go back to his first p1c release it actually works okay http://goo.gl/QBsmn
Actually I came back to the tab tonight and it was constantly rebooting in a loop so I may go back to cdesai too.
The one I am really waiting for is AOKP 4.2.2 for p1c, apparently his build machine is broken but hopefully he will post it soon.
But I cannot do usb tether or otg in any 4.1.x or 4.2.x build yet which is frustrating.
CM9.1 is very stable but missing all the 10.1 niceties.
You should put "p1c cmda" in the thread title here so we can have a 10.1 "club" for p1c folks.
I am running alrogers latest builds without any problem on my p1. Fast reliable and without any problems
I noticed fewer problems of unattended sleep or reboot after I flushed Dalvik and partition caches.
But the device still drains battery faster than the lastest CM10 nightlies (screenshots included) did, mostly because of the radio (30% - veille GSM) and while inactive (21% - tablette inactive).
Do you experience the same? Do you know where it could come from? (since I'm not able to post to dev section yet, too).
Re: CyanogenMod 10.1 Experimental Builds
If you have unknown baseband also, then the cause has been widely known. Broken modem.
Download JPZ modem zip from the development forum, unzip it and paste modem.bin to /radio to replace the one there.
Sent from my GT-I9300 using xda app-developers app
alroger's newest build from 20130328 now has working usb tether and works on my cdma (p1c)
but it's missing an adb toggle, cannot find it for the life of me
aha! found it - in CM10 you have to go to settings -> about tabet -> build number -> tap 7 times (to enable dev mode)
So several days after reflashing cdesai's experimental build I'm happy to report only one SoD compared to one or two previously.
With a bootlooping recovery, I used Heimdall to re-stock (mostly, I used a CWM kernal). I then reflashed with the same proceedure as before, wiping cache/dalvic, flashed gapps and I'm good to go.
Aside from the USB tether and BT issues (maybe someday...), my only problem now is that the screen orientation is sometimes unresponsive. Even the battery life is good, better than I had on CM 9.
I've not had any radio problems, at least none that Better Battery Stats could show me. The modem is the likely culprit.
Good suggestion on the title change p1c needs more love! :highfive:
Of course now with _ck_'s news that alroger has USB tether working, I'm tempted to try it again. Just can't leave well enough alone.
Just came back to my tablet to wake it up and the screen shows "encryption unsuccessful" wtf
Maybe alrodger build is not quite ready.
Spent an hour getting everything right again but not messing around this time, did both Titanium backup and clockwork backup.
Any help would be greatly appreciated.Hello all thank you for you time. I'm running cm10.1 unofficial nightly build 05.22.13 on my touchpad with the latest adobe flash apk and Firefox app from Googleplay.
The issue that I'm having is my display would go to sleep as configure per my display setting while I'm streaming flash content at full screen. Not sure why this is happening and not sure if this is just my device. I didn't have this issue with cm9. Only notice this with cm10 and now 10.1. Theodd thing is that this issue is also happening with my nook color and nexus 7 with cm10.1
My current work around is setting display to time out 30 mins and touch the display every now and then.
Any help would be greatly appreciated
Thanks again
I did a quick search and found this app for you. I haven't tried it, but its worth a try.
https://play.google.com/store/apps/details?id=it.android.keepscreenon
nickster1 said:
I did a quick search and found this app for you. I haven't tried it, but its worth a try.
Thank you. I went back to cm9 for stability but will keep this app in the back pocket . I was just curious to know if I was the only one experiencing this flash problem or its the same for everyone else. If its just me I wonder wat I did wrong with the install
Click to expand...
Click to collapse
imanobe said:
nickster1 said:
I did a quick search and found this app for you. I haven't tried it, but its worth a try.
Thank you. I went back to cm9 for stability but will keep this app in the back pocket . I was just curious to know if I was the only one experiencing this flash problem or its the same for everyone else. If its just me I wonder wat I did wrong with the install
Click to expand...
Click to collapse
Flash is being phased out and anything past 4.1 either doesnt work or partially works.
Sent from my TouchPad using xda app-developers app
Click to expand...
Click to collapse
gradular said:
imanobe said:
Flash is being phased out and anything past 4.1 either doesnt work or partially works.
Sent from my TouchPad using xda app-developers app
Click to expand...
Click to collapse
Flash is phased out but that doesn't mean you can't get it to work well. Its working great for me on my phone and tablet. Both running 4.2.2
Click to expand...
Click to collapse
nickster1 said:
gradular said:
Flash is phased out but that doesn't mean you can't get it to work well. Its working great for me on my phone and tablet. Both running 4.2.2
Click to expand...
Click to collapse
I,ve been flasing custom roms since the touchpad and nook color was out so i'm curious to know what I did wrong with these installs. I've had this issue happened to me with multiple devices. Nexus 7 nook color and my touchpad . All install were done with complete wipe of device.
Click to expand...
Click to collapse
imanobe said:
nickster1 said:
I did a quick search and found this app for you. I haven't tried it, but its worth a try.
Thank you. I went back to cm9 for stability but will keep this app in the back pocket . I was just curious to know if I was the only one experiencing this flash problem or its the same for everyone else. If its just me I wonder wat I did wrong with the install
Click to expand...
Click to collapse
Flash has never worked well on 4.1+ ROMs on the Touchpad in my experience. Flash isn't supported on 4.1+ but on other devices its still smooth so its a Touchpad Android issue not a Flash issue.
If you want Flash stay with CM9. I went back to CM9 after being on CM10 a while because I wanted stable Flash and couldn't really think of any new CM10 features that I needed.
Click to expand...
Click to collapse
spunker88 said:
imanobe said:
Flash has never worked well on 4.1+ ROMs on the Touchpad in my experience. Flash isn't supported on 4.1+ but on other devices its still smooth so its a Touchpad Android issue not a Flash issue.
If you want Flash stay with CM9. I went back to CM9 after being on CM10 a while because I wanted stable Flash and couldn't really think of any new CM10 features that I needed.
Click to expand...
Click to collapse
First and foremost thank you for your input. It is true that flash is no longer supported on 4.1 + but it can and should be stable once installed. One example I can provide is with my nexus seven. With stock rom and latest flash APk installed it runs Smoth no problem but when it is rooted and custom rom installed display issue occurs. There must be some config in the rom where display would remain awake when certain apps are running at full screen. Also its hard to see that its a touch pad issue because this is happening to other devices that I've installed custom 4.1+ rom. I'm currently back with cm9. For stability until cm 10.1 is more stable will switch.
Click to expand...
Click to collapse
imanobe said:
spunker88 said:
First and foremost thank you for your input. It is true that flash is no longer supported on 4.1 + but it can and should be stable once installed. One example I can provide is with my nexus seven. With stock rom and latest flash APk installed it runs Smoth no problem but when it is rooted and custom rom installed display issue occurs. There must be some config in the rom where display would remain awake when certain apps are running at full screen. Also its hard to see that its a touch pad issue because this is happening to other devices that I've installed custom 4.1+ rom. I'm currently back with cm9. For stability until cm 10.1 is more stable will switch.
Click to expand...
Click to collapse
Samsung probably built in some code to be more flash-compitable.
Sent from my TouchPad using xda app-developers app
Click to expand...
Click to collapse
Flash runs smooth on my Droid3 with CM10.1 even though the rom is far from stable. Also runs well on the Razr with stock 4.1.2 update. Its just on the Touchpad that 4.1+ have issues with flash in my experience.
Sent from my cm_tenderloin using Tapatalk HD
Can anyone port SmoothRom for the Kindle Fire HD 7? Now I already figured it may not be possible as someone would've provably already done it, but I decided to try it myself using the instructions in the following thread:
http://forum.xda-developers.com/showthread.php?t=1908008
STATUS: FAIL. And I used Hashcode's CM10.1 and SmoothRom 5.2 for Nexus 7 by jamesst20. Don't know if its a sin, if it is I apologize, I wanted it for my personal use, I'm not a developer, more of a "trial and error fixer" and I gave it a shot before asking. I loved that ROM when I had my Nexus 7 as it was so lag free and ran...well...smooth. If anyone has any info at all whether its possible, whether there's any takers to the project or even if its impossible, I'm all ears, and it would be much appreciated. Thanks in advance.
Sent from my Amazon Kindle Fire HD using xda app-developers app
Hmm I don't know much about making a full ROM, but it might have something to do with the fact smoothrom is aokp based, and cm is aosp based. Then again we do have some aokp ROMs for kfhd, they built theirs from the source code though rather than the method in your link, if I remember right that is.. Hmmm...
Edit:After re-reading that tut it seems it also works on ROMs that are AOKP so idk. Maybe try basing it from a aokp ROM. This is really a bit more beyond me than I thought at first.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Hmm I don't know much about making a full ROM, but it might have something to do with the fact smoothrom is aokp based, and cm is aosp based. Then again we do have some aokp ROMs for kfhd, they built theirs from the source code though rather than the method in your link, if I remember right that is.. Hmmm...
Edit:After re-reading that tut it seems it also works on ROMs that are AOKP so idk. Maybe try basing it from a aokp ROM. This is really a bit more beyond me than I thought at first.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thanks for the info. Do you know of any links to AOKP based ROMs for the KFHD7? I always used AOKP on my previous tablets etc and was looking for any AOKP based ROM for this device when I first planned on tossing in a custom ROM but I only got as far as CM10.1, CM10.2, MIUI port, and PAC ROM. So if you know any AOKP based ROMs links I would really appreciate it.
EDIT: Looked around, found nothing but this thread that never went anywhere.
http://forum.xda-developers.com/showthread.php?t=2285306&page=2
So I'm assuming 100% there are no AOKP based ROMs. If I knew how to compile a ROM, I'd do it. SmoothRom 5.2 was made for the Nexus 7 (well at least the one I was using) and the Nexus 7 and KFHD7 are nearly identical in a sense for example screen size, etc. So I know there must be even the slightest possibility.
This is aokp based...: http://forum.xda-developers.com/showthread.php?t=2355103, or at least it says it is, because its a mix of paranoid android and aokp and cm10.1 if I remember right, has some of the setting that aokp has if I remember right. I haven't ever used aokp or pac-man ROM, I prefer closer to stock, so maybe I misunderstand if that ROM is aokp based.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
This is aokp based...: http://forum.xda-developers.com/showthread.php?t=2355103, or at least it says it is, because its a mix of paranoid android and aokp and cm10.1 if I remember right, has some of the setting that aokp has if I remember right. I haven't ever used aokp or pac-man ROM, I prefer closer to stock, so maybe I misunderstand if that ROM is aokp based.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Well it does have AOKP but Im more than sure it started with CM10 when it was being compiled. I just know that nobody has made an AOKP based rom for no reason, there must be some story behind why its been left out of the mix. I've switched to using ROM-PORTER-v3.6, and its more successful than that guide I mentioned as I actually made the ROM flashable ONLY when using stock Amazon OS as the base and then SmoothRom as the port. Flashes fine, boot image works, but its a total boot loop, so I must be getting closer. I also tried adding certain extra files mentioned in the guide I mentioned, but them it causes the ROM to fail the flash. Then I realized that the build.prop is still as it was on the Nexus 7 and if im not mistaking the thread i got the tool from did mention editing that. So I must give it a try. Maybe thatll solve the case?
Why do I find it funny your are converting the stock ROM to a custom aokp ROM... On the bright side it would maybe work in a similar manner to kinology where you still have amazon video access and such. Fix the build.prop and it might work idk, I'm sure if anything it would help, just make sure if you are replacing it without flashing it that u chmod it to 644.
If I had to take a wild guess at why there isn't a stock aokp ROM or any others, it would be because the lack of devs, not to say we have a lack in the sense we are producing ROMs, but I think hashcode laid out the groundwork for most of the other devs, but because it was a aosp base I guess it was more likely to attract aosp devs, because it seems like less work to me if you are staying at aosp. Not to mention technically the cm builds are still beta last I checked, maybe we might get some other aokp and aosp devs once it goes official. For instance I don't believe I have seen a stock aosp android os for kindle fire HD yet. Most of the above is speculation, just thought I'd mention that before someone says I have no idea what I'm talking about. xD
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Why do I find it funny your are converting the stock ROM to a custom aokp ROM... On the bright side it would maybe work in a similar manner to kinology where you still have amazon video access and such. Fix the build.prop and it might work idk, I'm sure if anything it would help, just make sure if you are replacing it without flashing it that u chmod it to 644.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Believe me I know that I'm just juggling ROMs here with the possibility of being far off track and getting nowhere. Really dont kmow what I'm doimg at all. Just experimemting with trial and error to see if I make it somewhere. Even though I read that the base must be the same type as the port (AOKP to AOKP, CM to CM, etc) and that these certain things must be completely changed if not, etc etc, it doesnt hurt to try. No one else wants to do it, no one else has some info, then I must do as the saying goes: "if you want something done right, do it yourself." I have no clue how to create a AOKP rom out of thin air since theres really no AOKP based KFHD7 roms out there, so why not experiment with any other? My latest bigquestion is if AOKP is CM based in a way or two, how is it that the two combined isn't working out?
Hi,
Problem i have is the device isnt showing up in "My Computer".
It Makes a shound when connected, and it's in the Device Manager. Also.
Any help would be gr8!!!!!!!
_________________________________________________________________________________________________________________________
I've a rooted, with 2nd bootloader, TWRP v2.6.1.0, Paranoid Android C.ROM (pa_tate-3.99-20130824) and GAPPS (gapps-jb-20130813-signed) KFHD 7".
bump
please, any help -
Try reinstalling the drivers for the MTP device in then device manager. I think this usually happens when coming from stock and going to another ROM.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Try reinstalling the drivers for the MTP device in then device manager. I think this usually happens when coming from stock and going to another ROM.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Great - i'll try that.
Also though, im finding that there are a lot of crashes. and its actually preventing me from opening apps like, GAPPS, facebook etc etc.
Do you know of a stable ROM for KFHD7???
thank again
I run cm 10.1 with a tablet patch I made for the latest cm 10.1, I'm avoiding cm 10.2 for a few more months before I switch to it, I heard there's small performance issues because of some files not being optimized, as well as people in the market having to update their apps to work with the new is, as well as some fstrim things that need a little more investigating before I use it. I mean I am pretty sure most people are using it instead of cm 10.1 now, but I personally want to wait a bit.
Idk about your crashes but it could just be a bad flash or you used the wrong gapps package. I am not too familiar with the ROM you are using, since I haven't ever used it. The way I look at it is usually the closer you are to stock the less bulky the os would be, least that's how a PC operating system would work sorta. Don't know if the same holds true for android.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
I run cm 10.1 with a tablet patch I made for the latest cm 10.1, I'm avoiding cm 10.2 for a few more months before I switch to it, I heard there's small performance issues because of some files not being optimized, as well as people in the market having to update their apps to work with the new is, as well as some fstrim things that need a little more investigating before I use it. I mean I am pretty sure most people are using it instead of cm 10.1 now, but I personally want to wait a bit.
Idk about your crashes but it could just be a bad flash or you used the wrong gapps package. I am not too familiar with the ROM you are using, since I haven't ever used it. The way I look at it is usually the closer you are to stock the less bulky the os would be, least that's how a PC operating system would work sorta. Don't know if the same holds true for android.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thanks for your help!!
What build of CM10.1 are you using and what build of GAPPS?
I'll try in staling those and see if that makes a difference.
Thanks again!
I'm using the 8/12 build of cm 10.1 and if u click the link in my SIG for the tablet patch I directly linked the correct gapps zip in that post.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
I'm using the 8/12 build of cm 10.1 and if u click the link in my SIG for the tablet patch I directly linked the correct gapps zip in that post.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
thanks v.much for your help. really appreciate it. cheers!!!!
Please help. I have done a through search of the forums and found nothing on the subject. (Any search including "otg" returns results for "ota" updates.) The ability to use a flash drive as a kind of external hard drive was a MAJOR reason I rooted and installed a non-stock os. I have a Kindle Fire HD running twrp, cm10.2 and hashcode's 3.0.50+ kernel. I have tried both the "stickdrive" and "USB OTG Helper" apps with no luck. I was told in another thread that some ROMs will support USB OTG mounting but when I asked which ones I didn't get a response.
Thank you in advance.
Last I heard hashcode hasn't enabled otg in his kernel yet, and I think all ROMs use his kernel except stock amazon and kinology. You should wait for some other people to verify what I said first though because I am not 100% sure on this.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Last I heard hashcode hasn't enabled otg in his kernel yet, and I think all ROMs use his kernel except stock amazon and kinology. You should wait for some other people to verify what I said first though because I am not 100% sure on this.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
What is "kinology"? I'd be willing to try it out and update as to the results if I knew where to download it.
Its in the android development section, but it uses the same kernel as stock amazon os, its basically Amazon's os, but modded.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Its in the android development section, but it uses the same kernel as stock amazon os, its basically Amazon's os, but modded.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I tried both of the apps I mentioned before I rooted/modded my KFHD with no luck. So, do I just need to wait till KitKat and CM11 come out?
Or just wait until hashcode gets otg working. I think he was going to work on otg after all the other bugs and such are worked out. Seems like waiting for cm 11 to have otg would take longer than waiting for the current version, because I'm guessing the new version will have a new kernel so some things will have to be redone, and bugs introduced. Personally I'm just hoping by the time the next android release is out we can still use a buggy flashplayer... Don't even get me started on that....
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Or just wait until hashcode gets otg working. I think he was going to work on otg after all the other bugs and such are worked out. ..."some things will have to be redone, and bugs introduced." ...we can still use a "buggy" flashplayer.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Forgive me, why would one want to introduce bugs into a system?, and what is a "buggy" flash player? I thought bugs were glitches. Do you mean exploits?
Also, why do you use CM10.1? Is it more stable than CM10.2?
Eh well you don't want to introduce bugs into a system it just tends to happen when making something new while ironing the new problems out. That's why official releases of an os have these things fixed first usually before final release, though we tend to use alpha and beta ROMs a lot because some of us would rather have a buggy os than a amazon os. Not that hashcode's cm is that buggy anymore, he's worked out almost all the bugs I think. As for the buggy flash player, adobe stopped development a while back for flash player in ice cream sandwich, because they said html5 would be the future, even though so much of the net uses flash... Anyways the last flash player for ICS is kinda buggy on jellybean OS's, mainly because it wasn't designed for it, and some web browsers won't let u use the last version of flash because its buggy, like dolphin unless you download the modded version of the browser I found on the forums. One of the bugs I noticed is if I tap around in a video player too much it crashes the web browser. So no not exploits, just code that needs rewriting but will never happen since flash players is closed source. Ah as for me using cm 10.1, I just want to wait a few months until I'm sure that the apps in the market have stabilized, among other things, because some apps were having problems after the changes made in the new release caused certain apps to not work correctly. There's also a few other reasons like I heard about some of the libraries for the new version aren't optimized yet for our processor, and that there was a nasty bug with fstrim that could potentially hard brick our kindle by corrupting the emmc beyond repair. The bug that could do that isn't confirmed in the kindle fire HD, but it is said to affect the specific emmc that the kindle fire HD has. So yea there are a few things I'm waiting on before making the switch. Not to mention I'm happy with my os as-is right now.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Ah as for me using cm 10.1, I just want to wait a few months until I'm sure that the apps in the market have stabilized, among other things, because some apps were having problems after the changes made in the new release caused certain apps to not work correctly. There's also a few other reasons like I heard about some of the libraries for the new version aren't optimized yet for our processor, and that there was a nasty bug with fstrim that could potentially hard brick our kindle by corrupting the emmc beyond repair. The bug that could do that isn't confirmed in the kindle fire HD, but it is said to affect the specific emmc that the kindle fire HD has. So yea there are a few things I'm waiting on before making the switch. Not to mention I'm happy with my os as-is right now.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I hate to ask, but I'm still new to XDA and I'm still having a bit of trouble navigating. Would you post a link to where I can find CM10.1? Specifically the one meant for our KFTT? Thanks.
Here ya go: http://forum.xda-developers.com/showthread.php?t=2245335
If you want, try the tablet ui patch in my signature for the latest cm 10.1, I haven't had much feedback on it. It also contains the same link I just posted.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Here ya go: http://forum.xda-developers.com/showthread.php?t=2245335
If you want, try the tablet ui patch in my signature for the latest cm 10.1, I haven't had much feedback on it. It also contains the same link I just posted.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
So... I would use the "Latest"? And how would I go about implementing your tablet ui?
Sorry to keep bugging you. I feel like I'm being a bother.
The instructions are on the link in my SIG, u basically flash the file I attached after u flash cm and gapps, and yea use the latest.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
The instructions are on the link in my SIG, u basically flash the file I attached after u flash cm and gapps, and yea use the latest.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thank you. I appreciate the help.
Still no OTG
JeremySwagS said:
I tried both of the apps I mentioned before I rooted/modded my KFHD with no luck. So, do I just need to wait till KitKat and CM11 come out?
Click to expand...
Click to collapse
Well CM11 is out and still no OTG support for Kindle Fire HD. I sure wish that I could get this to work. I just don't know where to start.
New member here. I have the same problem -- KFHD7, CM11, no OTG. Did you ever figure this out?
Thanks.
-L
---------- Post added at 04:16 PM ---------- Previous post was at 04:11 PM ----------
Beaker319 said:
Well CM11 is out and still no OTG support for Kindle Fire HD. I sure wish that I could get this to work. I just don't know where to start.
Click to expand...
Click to collapse
To JeremySwags and Breaker319,
Did you guys ever figure this out? I'm ready to pitch this thing...
-L