Related
I want to start the ball rolling!
Hey,
So now we have a cracked bootloader, so why we aren't port cyanogen to our tabs?
The Nook have Cyanogen, and its architecture is pretty the same as gen8
the only difference i know is that our toucscreens are connected by an USB Controller..
but the cyanogen source is open! so a dev can change it and get it to us
I'm not a developer, but why developers aren't port cyanogen mod
i just don't understand it.
We'll see Gingerbread (2.3.3) on our Tablets
Maybe Sauron could think about Gingerbread/Cyanogen in a Future release of Urukdroid?..
I hope we get, finally , a working port at our tabs ( Luisivan`s HC Port just doesn't worked because the problem with the touchscreen )
Lennb said:
Hey,
I'm not a developer, but why developers aren't port cyanogen mod
i just don't understand it.
Click to expand...
Click to collapse
Well, firstly the bootloader hack was only posted 3 days ago. I am no developer either, but I would imagine it takes longer than that to port anything.
Secondly, the developers here on XDA are all people with real lives, doing this stuff in their spare time for their (and our) benefit. They don't get paid for it, and we have no right to expect/demand anything from them.
Thirdly, changing 1 byte in the stock recovery is a far cry from creating a custom recovery, which again takes time, energy and knowledge.
Don't misunderstand, I'm not flaming you here, just saying that a degree of patience might be come in handy right now. These things will come when the devs have the time to look into it.
Until then, just enjoy the huge benefits their hard work has already given us compared to stock.
sorry...
I don't want to insult any devs.., you did a great job
when i did this ↑↑↑↑↑ i am very sorry.
Yeah fisha i know what you mean, but i get angry when i think of the fact, that every damn android device gets an rom/hack/update. Even the oldest android device in the world has an honeycomb rom!
and we - owners of ones of the best android devices - stay at dark!
(okey we have a little bit of light and i thank sauron/artadat/silentrazor so much for that )
This upset me extremly! This is the only problem i had with Archos Products!
I was so happy, when i was heard that Archos Gen8 has an own Xda Forum in January
(Archosfans Forum is horror)
I just want to know that you guys :
Xda developers are the best android developers in the world
But we have to do something about the archos problem...
I do understand, the problem is just that the Archos isn't a very popular device. More people have the Nook etc, so more devs involved. There is some useful stuff on Archosfans, but much less in the way of development, that's true.
To be honest, when I bought my 101 in December, I thought I'd be waiting much longer to get to this stage....it will happen, just give it time. Or, do what I'm doing and start reading up on Android development, get your feet wet with some basic stuff, and who knows, you might be the one that brings us the next big thing!
Yeah i'm lucky about this too
I want it but i'm german i think you've already noticed that^^
And there're dont good german android development stuff
you're american?
I think that a future hypothetic Cyanogen port to archos will leave us without the GREAT archos video player and all the codec stuff they have on CLOSED development... so, we gotta wait and see the performance of our tablet with a "generic" set of codecs, for example...
Anyway... I'm very excited for the latest news of the recovery crack and happy to know that finally we are in position to have a CM port for archos ... with CW Recovery and all the stuff most android devices already have...
Yes,I am also deep wish and appreciated that Devepoler in ARCHOS Gen8 XDA forum could update more custom ROMs in the near future which will make the ARCHOS GEN8 more popular than before.
For example:There are many Dev. updated the custom ROMs of Huawei IDEOS u8150 in XDA forum(refer to : http://forum.xda-developers.com/showthread.php?t=970832 ) and users are very happy to upgrade and enjoy the updated custom ROMs everyday!!
I don't know many things about rom cooking, but if someone can teach me how to do i would be happy to do a custom rom for our Archos
lechuckthepirate said:
I think that a future hypothetic Cyanogen port to archos will leave us without the GREAT archos video player and all the codec stuff they have on CLOSED development... so, we gotta wait and see the performance of our tablet with a "generic" set of codecs, for example...
Anyway... I'm very excited for the latest news of the recovery crack and happy to know that finally we are in position to have a CM port for archos ... with CW Recovery and all the stuff most android devices already have...
Click to expand...
Click to collapse
Honestly, I have started using VitalPlayer. It plays AC3 and has a better sync between audio and video when using an OC kernel. So if we have to move to another Mod which loses us the stock player, its not that great a loss.
cdelta01 said:
Honestly, I have started using VitalPlayer. It plays AC3 and has a better sync between audio and video when using an OC kernel. So if we have to move to another Mod which loses us the stock player, its not that great a loss.
Click to expand...
Click to collapse
YEEES! There are better players for music and videos out in Market ( VitalPlayer,Rockplayer and Player Plus )
I Will "do" an rom on my 101 even if the codecs got lost
Then you haven't tried to play 720p videos.
fzelle said:
Then you haven't tried to play 720p videos.
Click to expand...
Click to collapse
Oh i have works perfectly with other players too
720p works on VitalPlayer for sure. I have no issues with that.
I'm looking for CM on our Archos too!!
Did somebody here tried this?
http://wiki.cyanogenmod.com/index.p...nMod_for_Sholes#Prepare_the_Build_Environment
It's a tutorial for how to build a CyanogenMod for a device, maybe with some adaptation we could use it to try to port Cyanogen, no?
eagleofdeath13 said:
Did somebody here tried this?
http://wiki.cyanogenmod.com/index.p...nMod_for_Sholes#Prepare_the_Build_Environment
It's a tutorial for how to build a CyanogenMod for a device, maybe with some adaptation we could use it to try to port Cyanogen, no?
Click to expand...
Click to collapse
I dont know, but probably no
Im not a dev and i dont want to brick my archos^^
but thank you to find this
Maybe one day i'll try this (i really love Cyanogen, so i want it on my Archos ^^)
eagleofdeath13 said:
Maybe one day i'll try this (i really love Cyanogen, so i want it on my Archos ^^)
Click to expand...
Click to collapse
Thats good i hope there would be more of you
I'm working on my own os, going to combine CM with the stock os... I'll keep you updated
Thanks you very much, and if you need som beta-tester
Ahoy mateys. I've been a longtime Android user (October 2009) and have never been much for running the stock OS on my devices.
Currently I've been running CM7 and loving it on the KF. Been keeping tabs on the ICS port over, just waiting for the sound issues to be hammered out as I use the device mostly for watching videos via RockPlayer.
Lately I've been thinking about trying to port over Honeycomb to the KF, as it might be simpler given that it's been around longer. I know that it's somewhat futile given the state of the 3.0 kernel being needed for HW acceleration. But it seems like it could be worthwhile just to test it and see what might happen. Give it more tablety goodness if anything!
I'm a programmer by trade and am majoring in CS. Not much dev experience on Android aside from writing games. But I've built Gentoo for my machines, so I've got some kernel knowledge. What do you guys think?
Regards,
-Free
P.S. I don't have 10 posts so this is in General.
freeqaz said:
Ahoy mateys. I've been a longtime Android user (October 2009) and have never been much for running the stock OS on my devices.
Currently I've been running CM7 and loving it on the KF. Been keeping tabs on the ICS port over, just waiting for the sound issues to be hammered out as I use the device mostly for watching videos via RockPlayer.
Lately I've been thinking about trying to port over Honeycomb to the KF, as it might be simpler given that it's been around longer. I know that it's somewhat futile given the state of the 3.0 kernel being needed for HW acceleration. But it seems like it could be worthwhile just to test it and see what might happen. Give it more tablety goodness if anything!
I'm a programmer by trade and am majoring in CS. Not much dev experience on Android aside from writing games. But I've built Gentoo for my machines, so I've got some kernel knowledge. What do you guys think?
Regards,
-Free
P.S. I don't have 10 posts so this is in General.
Click to expand...
Click to collapse
Personally, I think it's a good idea, and that you should do it. You'll probably get a lot of people saying there's no point cause ICS is what honeycomb should've been. I've never used honeycomb before, so I don't know how different it is from ICS but I'm sure there are some.
I think you should do it to give this device and its users another ROM choice, with a different android version. Or even just for the fact that you might want to use it, do it for yourself and post it here just to see if people want it. I'd try it out, even if ICS is out and stable haha
Sent from my HTC Glacier using Tapatalk
Personally, I think it's a good idea, .... I've never used honeycomb before...
Click to expand...
Click to collapse
Huh?
Why would you encourage someone to work on something when you yourself don't know what the differences are between them??
ICS is Honeycomb just taking to what was its planned completion. With many Honeycomb devices moving to ICS I don't see the point.
That would be doing a lot of work, just to end up with an in between OS with all the new support going to ICS which is what everyone that can get it wants.
Also, for someone with no Android programming experience, you most likely would be a lot better of working with apps before tackling a whole OS.
krelvinaz said:
Huh?
Why would you encourage someone to work on something when you yourself don't know what the differences are between them??
ICS is Honeycomb just taking to what was its planned completion. With many Honeycomb devices moving to ICS I don't see the point.
That would be doing a lot of work, just to end up with an in between OS with all the new support going to ICS which is what everyone that can get it wants.
Also, for someone with no Android programming experience, you most likely would be a lot better of working with apps before tackling a whole OS.
Click to expand...
Click to collapse
I'd like to check it out. It's not like I'm telling him that he needs to do this, he asked what people thought of the idea because he was interested in doing it, and I voiced my opinion.
Though I do agree that it might be easier to work with apps and then maybe work on a ROM, but hey, if he's willing to attempt it and learn how everything works, why stop him? The more devs, the merrier lol
Isn't the problem with porting honeycomb is that it was never truly open source?
My understanding is there was never a source release for honeycomb
Sent from my SPH-D700 using xda premium
[email protected] said:
Isn't the problem with porting honeycomb is that it was never truly open source?
Click to expand...
Click to collapse
Yea, that is, AFAIK, why there was never a CM8. I don't think it would be worth OP's time to try to reverse-engineer a Honeycomb tablet and shoehorning it into the KF.
However, the OP might want to donate some of their time to the ICS port
It is open source after all...
[email protected] said:
Isn't the problem with porting honeycomb is that it was never truly open source?
Click to expand...
Click to collapse
I believe Google released the source for Honeycomb when they released the source for ICS
Sent from my Kindle Fire using Tapatalk
Hit up this Google announcement, they did indeed release the source.
This release includes the full history of the Android source code
tree, which naturally includes all the source code for the Honeycomb
releases. However, since Honeycomb was a little incomplete, we want
everyone to focus on Ice Cream Sandwich. So, we haven't created any
tags that correspond to the Honeycomb releases (even though the
changes are present in the history.)
Click to expand...
Click to collapse
groups.google dot com/forum/#!topic/android-building/T4XZJCZnqF8
The only thing that I really want to know is if there is a significant driver difference between ICS and Honeycomb. If there is, then there is a reason to try to port 3.0 over because it would have more driver support. There are 3.0 devices out in the wild. If there isn't a driver difference between 3.0 and 4.0, then it's futile and all efforts should be spent on 4.0.
theholyfork said:
I believe Google released the source for Honeycomb when they released the source for ICS
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
Indeed.
And when they released the source for ICS, they elaborated on why they included Honeycomb in the Source tree: To essentially display the hacks they were forced to use to push Honeycomb to market. Honeycomb was never AOSP'd because it wasn't reliable for wider use.
Based upon the fact that Google was basically too ashamed to release Honeycomb to AOSP, I don't think it would make much sense to target a broken platform (Honeycomb).
IMO, if you're going to spend time trying to work on getting a more tablet-oriented version of Android running, it's probably going to be *easier* to work with ICS than Honeycomb. Moreover your contributions could assist the greater KF community in getting a stable base of ICS for all.
If you go to my website (in signature) you can now access beta testing! I have opened it as my weebly pro account expired and it was expensive :/. So you can head over there and get v1.2 BETA for your kindle! Under members, no testers exist as everyone can be a tester and report bugs and/or issues they have. Also, I have a question: Should I include kernel 3.0 in the next release of my rom? I'm thinking of making 2 builds, 1 with 3.0 Kernel, and 1 with the current kernel. I say this because the current kernel, yes has no hardware acceleration; but kernel 3.0 has A LOT more bugs. Please post your opinion here and I will be sure to consider! Thank you for all of my donors who got me where I am. Donations are appreciated as I can pump builds for devices faster, especially as now I support FOUR devices.
Thanks again,
~ BiteBlaze via XDA Developers
I would suggest going with your two build idea since you have a great opportunity to be on the ground floor of this new kernel as it is a turning point in Kindle Fire roms. Also, hi, lol, sorry I went dark for awhile there, got crazy busy in classes and I wasn't able to do much more than post on the forums, my apologies.
The two versions idea sounds good, it'll be fun to try out
I second the 2 kernels idea.
Btw what is the change log for 1.2? I tried looking but couldn't find it. Is it significantly better than 1.1 or just marginally? I am on 1.1 and having this urge to beta test 1.2 but 1.1 has been so good so far and don't wish to leave this one
To flash or not to flash?
Sent from my Kindle Fire using XDA
Changelog (beta does not have all of this yet): New features on v1.2
1. New Soft Keys (stock soft keys are now blue and reflective)
2. New Lockscreen color (has a blue glow)
3. Flashable Mods (for soft keys and other things)
4. Updated Apps
5. Integrated Google Apps (single flash rom!)
6. Better CPU app
7. Graphic Improvements
8. Bug Fixes
9. Modified build.prop
10. Few other minor things
ETA: now - 4/17
v1.2 is going to be groundbreaking in the progress of ReloadedROM™
Cheers.
yes try kernel 3.0.
if nothing else it will be fun testing.
thanks
steve
I would be happy to test your builds I ran the first two you put out They seemed fine to me although I am a little leary on kernel 3.0 as it is still pretty buggy closer but buggy nontheless. Im not knocking hashcode hes doing an awsome job with his kernel development and will probably change the kindle as we know it exspecially related to hwa issues of cm9. Anyway wouldnt mind doing a flash or two what you have done has been stable so far
lovejoy777 said:
yes try kernel 3.0.
if nothing else it will be fun testing.
thanks
steve
Click to expand...
Click to collapse
+1 flashaholic here!
just posted in dev thread but thought i'd put it out here as well
nice job blaze working very smooth
Sent from my Kindle Fire using xda premium
Nice job! Thank you for opening up the testing. Two hours since flash and so far and so good.
Sent from my Kindle Fire using Tapatalk 2
Running smooth on 1.2, looks like kernel might have some progress soon, then maybe another beta with the new 3.0?
kernel
Hey guys.
I've been using ics on my kindle for a few months now. And the only thing missing to improve on it is hardware acceleration.
Would the new kernel fix it? Is it the same one that hashcode is working on?
Thanks!
yes & yes
Sent from my Galaxy Nexus using xda premium
I'm far from being an authority on this matter, as I am NEW to the Kindle Fire and flashing ROM's, but I like the idea of offering two builds with the different Kernels.
The best way to get a stable Kernel is to have as many people as possible using it IMHO, so this would be a good way since you have one of the more popular CM9 ROM's out there.
Keep up the good work!
Thank you for ur efforts Biteblaze. When do u expect the ROM based on the new kernel?
Totally appreciate the effort on this rom - definitely my fav.
Has anyone tired 1.2 with hashcode's 3.0 kernel yet?
Sent from my ADR6400L using XDA
Is there a way to go back to the grey soft keys in v1.2?
And great work! First time for me that Google Play downloaded my v1.1 apps automatically upon first boot.
Sent from my Kindle Fire using XDA
BiteBlaze! Awesome work on the KF! just started mucking around with my second KF and your rom is by far the best one I have loaded to date! 2 builds also sounds like a great idea. hopefully it won't turn into a real mess for you to support though.
Keep up the great work and I sent you a donation as well!
Seriously great work here!
THANKS!
/hades
Hello,
I just would like to share my experience of moving from the stock 4.1.2 Jelly Bean to the CM10 release, mostly for people who are still using stock 4.1.2 because I couldn't find such a thread before jumping to CM10.
I installed the 5th November nightly release of CM10 as the more recent ones (including the "stable" release) have an annoying problem : the Play Store reports some incompatibilities with apps which were working fine with the stock 4.1.2. It seems that this problem is due to the lack of free memory with the newest CM10 releases ...
The 11/05 CM10 was the last one with no Play Store problems, you can download it here for the Wingray :
http://dl.dropbox.com/u/2383656/cm-10-20121105-NIGHTLY-wingray.zip
EDIT : on the 6th December, I updated my Xoom from the 11/05 nightly to the 12/05 nightly, and so far I still didn't have the Play Store compatibility issue, which means the problem has been solved in between these two releases ...
Performances :
I must admit that I didn't think it was possible that a custom ROM was better optimized than the one made by Google itself ...
I was very happy with the fluidity of the stock 4.1.2, but when I used CM10 for the first time, I tried some websites known to be a bit laggy with the stock browser, and they were just close to perfect about fluidity with CM10 ! I couldn't find a laggy website with stock browser yet ... These tests were not involving overclocking.
So I then ran Quadrant and had a score of 2800, where I had 1900 with stock 4.1.2 ... !
I then overclocked the Xoom to 1,5 GHZ, and Quadrant reported a score of 4100, about equal to the Transformer Prime !
I don't really play with my Xoom but I tried to play to GTA III, and when overclocked, compared to the stock 4.1.2, I could put a lot more graphical details with a better fluidity. I really felt like using a whole new device. But most of the time I don't use overclocking as I want to save my battery life, and the overall fluidity of the Xoom running CM10 at 1GHz is very good.
A few people reported they found a performances increase with the very last nightly release. However, as it still have some compatibility problems with the Play Store, I will not jump on it.
I don't know if Cyanogen will try to solve this incompatibility issue as it maybe related to the Gapps taking too much storage space, and Cyanogen does not support Gapps ...
Updates :
I choosed a Cyanogen rom (instead of EOS) because with this one you can easily update to newer ROM release very easily, without the need to connect your Xoom to the PC, and without loosing datas : CM10 includes an update manager which proceeds just like an official Google OTA ! That's just perfect to me, I'm not sure if this does also exist on EOS, I couldn't find any informations about this.
So I have the feeling that my Xoom is still supported and updated, which is very good. Thanks a million to Cyanogen team !
Bugs :
I couldn't find bugs yet on the 11/05 release, I just had an unexpected reboot the very first time I used it, only after 5 minutes of use. Since then, I never had this problem again (3 days with no reboots for now).
Features :
I didn't try all of them yet, but there are plenty of cool features :
- overclocking ability with multiple policies possible to save battery life for exemple, or for the best performances all the time.
- other performances tweaks about RAM like "KSM" use, and some other parameters which allow better performances but lowering the battery life.
- root of course !
- the ability to light the charging LED, even when your Xoom is powered on.
- many many others, some I didn't tried/discovered yet.
So I am very happy now with CM10, and I would like to thanks Cyanogen again about this excellent work !
I would recommand to any stock 4.1.2 users to jump on to CM10, the Xoom will just be running better then !
Here is the link which explains how to jump to a Cyanogen ROM :
http://wiki.cyanogenmod.org/wiki/Mo...de#Installing_the_ClockworkMod_Recovery_Image
Have fun !
TeamEOS has all the features you mentioned and you can update it easily as well. Don't need a computer, they use GooManager. In short they are both good ROMs, there is nothing to dislike about both of those ROMs, both teams have putted a lot of effort into optimising the XOOM and adding functions/features. It's all up to user preference, with CM ROMs I get random reboots, while TeamEOS I don't get any of that.
Chaosgod27 said:
TeamEOS has all the features you mentioned and you can update it easily as well. Don't need a computer, they use GooManager. In short they are both good ROMs, there is nothing to dislike about both of those ROMs, both teams have putted a lot of effort into optimising the XOOM and adding functions/features. It's all up to user preference, with CM ROMs I get random reboots, while TeamEOS I don't get any of that.
Click to expand...
Click to collapse
How polished is the root/rom procedure for the Xoom? I came from the Transformer world and it was pretty well dialed in..not a lot of monkeying around or knowledge required.
What's the easiest way to get root and a custom rom?
rpavich said:
How polished is the root/rom procedure for the Xoom? I came from the Transformer world and it was pretty well dialed in..not a lot of monkeying around or knowledge required.
What's the easiest way to get root and a custom rom?
Click to expand...
Click to collapse
Idk, never rooted or used a Asus tablet. Once the Xoom is unlocked and rooted you really have no need for a PC unless you use fastboot & adb to flash, push, pull, etc.....
Sent from my Xoom using Tapatalk 2
Chaosgod27 said:
TeamEOS has all the features you mentioned and you can update it easily as well. Don't need a computer, they use GooManager. In short they are both good ROMs, there is nothing to dislike about both of those ROMs, both teams have putted a lot of effort into optimising the XOOM and adding functions/features. It's all up to user preference, with CM ROMs I get random reboots, while TeamEOS I don't get any of that.
Click to expand...
Click to collapse
Definitely. I've used both ROMs, but struggled with SOD's on EOS Stable and lag on the nightlies! CM10 solved both of these issues for me. Both ROMs are full of features and and a no brainer compared with stock.
Regards.
lynxboy said:
Definitely. I've used both ROMs, but struggled with SOD's on EOS Stable and lag on the nightlies! CM10 solved both of these issues for me. Both ROMs are full of features and and a no brainer compared with stock.
Regards.
Click to expand...
Click to collapse
Thanks a lot, that's interesting. I was more and more thinking about trying the EOS ROM, but I was too lazy about reinstalling all my softwares and data ...
What do you mean by "SOD" ?
It's very interesting to have the feedbacks of people having tried both custom ROMs, it would be cool if some other people could give their opinion.
dizzy33 said:
It's very interesting to have the feedbacks of people having tried both custom ROMs, it would be cool if some other people could give their opinion.
Click to expand...
Click to collapse
i have not tried EOS yet. CM10 runs absolutely flawless. I got a good 14hrs -/+ on the battery playing Deadzone, watching movings, browsing the net, skyping with my kids and I still have 28% left today. No OC. Having full R/W access to the External Sdcard is great. I now can Dropsync my folders from my Dropbox to the card for a quick handy on the go backup
EOS from what i have heard has some great features.....i will need to backup and give it a go here soon.
Sent by Samsung Galaxy Nexus (SCH-I515 Verizon LTE) using Tapa2
rpavich said:
How polished is the root/rom procedure for the Xoom? I came from the Transformer world and it was pretty well dialed in..not a lot of monkeying around or knowledge required.
What's the easiest way to get root and a custom rom?
Click to expand...
Click to collapse
Yes it's very easy, considering this is a google experience device all you really have to do is unlock it, flash in recovery and then using recovery flash in another ROM. You should have zero problems at all, considering the bootloader is unlocked.
Can anyone please tell me if one of the december CM10 nightly did solve the Play Store incompatibility problem ?
Thanks !
dizzy33 said:
Can anyone please tell me if one of the december CM10 nightly did solve the Play Store incompatibility problem ?
Thanks !
Click to expand...
Click to collapse
No need to ask this question almost everywhere.......I have not experienced any market issues.....
Sent by Samsung Galaxy Nexus (SCH-I515 Verizon LTE) using Tapa2
cdexsw said:
No need to ask this question almost everywhere.......I have not experienced any market issues.....
Sent by Samsung Galaxy Nexus (SCH-I515 Verizon LTE) using Tapa2
Click to expand...
Click to collapse
as long as you will not entirely answer my questions, I will still ask it, and I'm free to do it !
Yes you don't have this problem now, thanks for this information, but did you have this problem before ?
If you never had this problem, this means you may not be using the CM10 Gapps but the EOS one, or you just didn't realize that you actually have a compatibility issue with the Play Store ... It's easy, check the application named "eye in sky weather", if the store says that it's not compatible with your device, it means that you're facing the compatibility issue as this application is in fact compatible with the Xoom. Of course this problem is not only for this application, there are many others which are reported as not compatible ...
dizzy33 said:
as long as you will not entirely answer my questions, I will still ask it, and I'm free to do it !
Yes you don't have this problem now, thanks for this information, but did you have this problem before ?
If you never had this problem, this means you may not be using the CM10 Gapps but the EOS one, or you just didn't realize that you actually have a compatibility issue with the Play Store ... It's easy, check the application named "eye in sky weather", if the store says that it's not compatible with your device, it means that you're facing the compatibility issue as this application is in fact compatible with the Xoom. Of course this problem is not only for this application, there are many others which are reported as not compatible ...
Click to expand...
Click to collapse
I am using the latest nightly. In fact i have used all the December nightlies with no issues.
As far as gapps, i have used that lastest gapps 4.1.2 and i have tried gapps 4.2+. I used the gapps posted in the link on first page of this thread both packages i have experienced no issues, market is working fine, no incompatibilities.
As far as my comment about aking your questions.....ask in one place....no need to ask your question in every forum are start a new thread.....i was not being rude, it is in the forums rules.......
Good luck.....
Also, check your dpi settings....that will cause market issues. Search the forums & google the fix is simple...
Also try manual installing an older marker version or try or KDH 4.2 gapps.
These are all solutions to your issue(s). No one else may try and answer you question because they are not having or no longer have these issues.......what i posted above are the steps to fix the issue.
Sent by Samsung Galaxy Nexus (SCH-I515 Verizon LTE) using Tapa2
Thanks for these informations, I'll check this. But for now I have no problems with the market as I am using the 11/05 release. The problem came after this release and was known to be due to a free memory issue (check my first post of this thread). That's why I was asking if a recent release of CM10 did solve this problem.
EDIT : I just jumped from 11/05 nightly to 12/05, and I still have no problems with the Play Store, which means the Play Store compatibility problem has been solved in between these two releases ... Great news !
Thanks
Thanks man, that's what I needed to migrate, a good experience report.
I heard about incompatibilities, also that some apps won't work, but I can manage that. I'm now going to make a backup of my things and this weekend I want to install CM10. The main problem now is the backup, since I have a lot of things on it, both the internal memory and SD are quite full. XD
The most surprising thing is that I could not find any report about this bug correction, which was a very annoying bug, but I could find plenty of threads talking about this problem and trying to find workaround solutions ... None of them reported this bug does not exist anymore ...
Similar ROM experiences...
Chaosgod27 said:
TeamEOS has all the features you mentioned and you can update it easily as well. Don't need a computer, they use GooManager. In short they are both good ROMs, there is nothing to dislike about both of those ROMs, both teams have putted a lot of effort into optimising the XOOM and adding functions/features. It's all up to user preference, with CM ROMs I get random reboots, while TeamEOS I don't get any of that.
Click to expand...
Click to collapse
I had similar random rebooting issues using the CM9 ROMs on my tablet which is why I use Team EOS. Both ROMs do have similar features and it comes down to user preference and which UI you prefer.. but BOTH are quality software and greatly appreciated!
Hi guys,
I come to request your help to get CyanogenMod 10.1 to work on the HDX 8.9.
Reading the cyanogen wiki, I get a booting ROM with logcat but no more (I get the pretty cyanogen logo sometimes ...)
I hope some of you can help with their knowledges in order to get a working CM on our beautiful tablet
I attached the current logcat, and you can find a git repo with device files here : https://github.com/ptiwee/android_device_amazon_apollo
There is for sure huge mistakes/leaks, so don't hesitate to help.
Thanks
I wasn't aware that with the locked bootloader that you could flash cm due to not being able to flash a kernel to run with cm.
Sent from my LG-D800 using XDA Premium 4 mobile app
donharden2002 said:
I wasn't aware that with the locked bootloader that you could flash cm due to not being able to flash a kernel to run with cm.
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Stock kernel + CM ROM = Hybrid OS. It is doable.
Sent from my KFSOWI using Tapatalk
count me in
Mineturtle33 said:
Stock kernel + CM ROM = Hybrid OS. It is doable.
Sent from my KFSOWI using Tapatalk
Click to expand...
Click to collapse
So let's do it! One happy community working in concert to get cm working on our beloved device! I'm in and will help in any way possible.
I can try to build it. I don't have a HDX 8.9, I have an HD 2, so I can't test it. And I'm awful at building ROMS :silly: but I can try, and I know how.
AOSP user
Just an observation regarding my experience with my (7") HDX, to date. And I'm all for a CM or AOSP custom ROM. Like some other folks, I got the Kindle Hdx to have a good hardware platform at a good price - I can live without an Amazon OS!
I'm not a developer, just a tinkerer -- 'tho I've had a fair amount of experience playing with various ROMs -- on Motorola devices and now on my new Kindle HDX -- with a BIG THANKS to HashCode for his ongoing work with SafeStrap!
My current "ROM of choice" -- and the one that works best (and most stable) for me is Cpasjuste's aosp-4.2.2-thor-0 (ver. 0) first published in the HDX Android Development forum on January 12th. (Note: ]NOT his 4.2.2-1 published Jan. 24)
BTW: Another BIG THANKS to Cpasjuste for all his work, too! and thanks to all contributors!
I have tried all the thor-gapps roms available to date -- but the AOSP 4.2.2-0 works best for me. PS: I only use Kindle reader and that works on all roms if you use the older version that LinearEquation links to in different forums. If you use a lot of Amazon services -- well that's what the Amazon OS is for!
PS: for the few users who have commented on Google Maps not rendering properly on any of the Amazon based or thor-gapps roms -- it works perfectly on the aosp 4.2.2-0 rom that I mention above.
[instructor sa;50018690]Just an observation regarding my experience with my (7") HDX, to date. And I'm all for a CM or AOSP custom ROM. Like some other folks, I got the Kindle Hdx to have a good hardware platform at a good price - I can live without an Amazon OS!
I'm not a developer, just a tinkerer -- 'tho I've had a fair amount of experience playing with various ROMs -- on Motorola devices and now on my new Kindle HDX -- with a BIG THANKS to HashCode for his ongoing work with SafeStrap!
My current "ROM of choice" -- and the one that works best (and most stable) for me is Cpasjuste's aosp-4.2.2-thor-0 (ver. 0) first published in the HDX Android Development forum on January 12th. (Note: ]NOT his 4.2.2-1 published Jan. 24)
BTW: Another BIG THANKS to Cpasjuste for all his work, too! and thanks to all contributors!
I have tried all the thor-gapps roms available to date -- but the AOSP 4.2.2-0 works best for me. PS: I only use Kindle reader and that works on all roms if you use the older version that LinearEquation links to in different forums. If you use a lot of Amazon services -- well that's what the Amazon OS is for!
PS: for the few users who have commented on Google Maps not rendering properly on any of the Amazon based or thor-gapps roms -- it works perfectly on the aosp 4.2.2-0 rom that I mention above.[/QUOTE]
So is there any downside? Random crashes? Reboots? Anything?
@Mineturtle I'd be happy to test ish for you. What do u need?
Cpasjuste's AOSP ROM for thor has differing issues by release. Release 0 has rendering issues in which almost all games, youtube, and music were unbearable to use/broken. Release 1 has some rendering issues still, but youtube and music work. However, release 1 also has the quirk that no system dialog boxes actually render on screen. You can touch them, but you can't see them. It's weird and kind of frustrating, but do-able.
Ptiwee said:
Hi guys,
I come to request your help to get CyanogenMod 10.1 to work on the HDX 8.9.
Reading the cyanogen wiki, I get a booting ROM with logcat but no more (I get the pretty cyanogen logo sometimes ...)
I hope some of you can help with their knowledges in order to get a working CM on our beautiful tablet
I attached the current logcat, and you can find a git repo with device files here : https://github.com/ptiwee/android_device_amazon_apollo
There is for sure huge mistakes/leaks, so don't hesitate to help.
Thanks
Click to expand...
Click to collapse
Looking at the logs it seems your primary problem is with the opengles drivers/libraries as it can't init opengles.
Cpasjuste said:
Looking at the logs it seems your primary problem is with the opengles drivers/libraries as it can't init opengles.
Click to expand...
Click to collapse
So what do we do now? how can i help?
Lets push it harder
Guys i read through everything and i believe since this tablet blows the nexus out of the water.i think we should push kitkat i understand we need ot start somewhere and 10.1 is a great starter platform to get devlopers on it and ive been trying to get a starter rom to get this show on the road fo rmyself i think we should keep up this thread and submit it cm personally.:highfive::laugh:
wazedubstep said:
Guys i read through everything and i believe since this tablet blows the nexus out of the water.i think we should push kitkat i understand we need ot start somewhere and 10.1 is a great starter platform to get devlopers on it and ive been trying to get a starter rom to get this show on the road fo rmyself i think we should keep up this thread and submit it cm personally.:highfive::laugh:
Click to expand...
Click to collapse
There is a thread about a bounty to unlock the boot loader. I think that's our best course of action. An unlocked boot loader gives us so many options. The bounty is for the 7 inch HDX but the hardware is almost identical I would be surprised if it didn't work for both. If we get the bounty high enough we could recruit some low level programmers to our cause.
This is my 69th post... hehe... I'm such a little kid at heart
gutts10 said:
There is a thread about a bounty to unlock the boot loader. I think that's our best course of action. An unlocked boot loader gives us so many options. The bounty is for the 7 inch HDX but the hardware is almost identical I would be surprised if it didn't work for both. If we get the bounty high enough we could recruit some low level programmers to our cause.
This is my 69th post... hehe... I'm such a little kid at heart
Click to expand...
Click to collapse
In. That case its settled let's start a bounty page and get this show on the road :laugh::laugh:
wazerdub said:
In. That case its settled let's start a bounty page and get this show on the road :laugh::laugh:
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2580428
here ya go... do a little pledge and lets see if we can get a potential programmer a free hdx on our behalf
Could someone make this CM possible
So I need to make some posts
Sent from my KFAPWI using Tapatalk
The bootloader is locked down pretty tightly. I do not think it'll ever be unlocked.
Root is possible on previous updates and may be possible soon on 14.3.2.2
But that's probably all we'll get
Sent from my Nexus 4
Would work on safe strap if we ever get root. My 16 gig is full as it is though... safe strap made the available memory show too small