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
So is everybody just waiting for Google to release the revised version of software for the Nexus Q??
or has anybody yet created a flashable CM9 ROM?
I'm getting so impatient I've started trying to build a CM9 from source myself, but it's my first attempt at building a ROM.. I'm using mostly maguro base files and removing what's unnecessary.
Moved to Nexus Q Q&A.
Trebuchet + sideloaded apk's + usb mouse and keyboard works great for me.
I want a more polished solution but I am watching Hulu and Netflix daily (nightly) just like this. I even played Angry Birds and Ski Safari this way. What are you specifically looking to do?
UKROB86 said:
So is everybody just waiting for Google to release the revised version of software for the Nexus Q??
or has anybody yet created a flashable CM9 ROM?
I'm getting so impatient I've started trying to build a CM9 from source myself, but it's my first attempt at building a ROM.. I'm using mostly maguro base files and removing what's unnecessary.
Click to expand...
Click to collapse
Interestingly, Netflix now works kind of like the Q when on the same WiFi network as a ps3. Like a remote, and controlled. I'd guess that the wheels are turning, we just haven't seen anything yet. Give it till Christmas.
I doubt amazon video will work though, they seem to be going the selfish route: Buy our hardware or get nothing from us...Sigh...
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!
If I was to start developing a custom ROM based on the latest ICS update for the Verizon model of this tab.... would there be any interest ?
I ask because last time I took the time to do one for the Verizon SGT (the original 7 incher) there wasn't that many interested "customers"
NRGZ28 said:
If I was to start developing a custom ROM based on the latest ICS update for the Verizon model of this tab.... would there be any interest ?
I ask because last time I took the time to do one for the Verizon SGT (the original 7 incher) there wasn't that many interested "customers"
Click to expand...
Click to collapse
I would be interested.
NRGZ28 said:
If I was to start developing a custom ROM based on the latest ICS update for the Verizon model of this tab.... would there be any interest ?
I ask because last time I took the time to do one for the Verizon SGT (the original 7 incher) there wasn't that many interested "customers"
Click to expand...
Click to collapse
Even if there isn't many "customers", there's always the personal challenge, satisfaction and self education Good luck
Sent from my GT-I9500 using XDA Premium 4 mobile app
UpInTheAir said:
Even if there isn't many "customers", there's always the personal challenge, satisfaction and self education Good luck
Sent from my GT-I9500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
True.. I'm past all that at this level and it would just be the time invested. Sounds like it's not worth it. Heh
If you did an ICS rom and left the samsung video player in it and added ntfssd (from google play) or compiled your own kernel that would use exfat or ntfs (TWRP supports exfat) for large file support I would test it.
Keep in mind ICS has been done, but If you could figure out how to port kitkat to the device that would be awesome. Kitkat is supposed to have great memory management. The galaxy 7.7 only has 1GB of system memory HC ran fast on it but ICS is a bit of a dog even with bloat removed and tweaks applied. The port of PAC rom to the i815 gave me issues due to incorrectly signed files in the rom.
I haven't checked the general section on this forum for a long time but yea I still use my i815 quite often and the lack of stock development has been extremely disappointing. But there is a lot of driver work afaik particularly with the IR and LTE. I don't have a data plan on my i815 anymore but from time to time I may throw my phone SIM in there. Biggest thing for me over the other ROMs is having the function of the full hardware. I personally dislike touchwiz thoroughly with the exception of multiwindow features
So yea
I would definitely be interested there are likely a few others who would be interested but don't frequent this section. The i815 info thread I think still have a decent number of subscribers.
NRGZ28 said:
True.. I'm past all that at this level and it would just be the time invested. Sounds like it's not worth it. Heh
Click to expand...
Click to collapse
Any further thought on this?
Currently I use in my car as a glorified GPS I might do a rom for it in the future
Hey all, new Tab 4 7.0 owner here. I've only ever owned HTC EVO devices, which have a wide selection of custom everything to choose from, so empty Android/Original Development sections are a new concept for me.
From what I read, development hasn't started because we don't have a stable recovery environment yet, but assuming we get that down, what would be the main hinderances (device-specifc issues) of getting AOSP on this tablet? What can we non-developers do to help?
Thanks for all your answers!
Lacedaemon said:
Hey all, new Tab 4 7.0 owner here. I've only ever owned HTC EVO devices, which have a wide selection of custom everything to choose from, so empty Android/Original Development sections are a new concept for me.
From what I read, development hasn't started because we don't have a stable recovery environment yet, but assuming we get that down, what would be the main hinderances (device-specifc issues) of getting AOSP on this tablet? What can we non-developers do to help?
Thanks for all your answers!
Click to expand...
Click to collapse
As far as I know, we have a bit of lack of support fro Devs. We do have great Devs however some (if not most) of them don't actually own the device so they are trying to work from other devices including the Tab 3 series. Another thing is lack of tools and information from Samsung. Even though they do provide Devs with tools and info, they are a bit secretive when it comes to development of the actual OS. So that's that. What you can do is to offer to test new methods but you must accept the risks which involves Hard Bricking of the the tab. Other than that just be patient and privide any information you can give
Sent from my SM-T230NU using XDA Free mobile app
As a contributor that works with the Tab 3 7in version, I can tell you that the Marvel cpu/board set that Samsung used on our (and your) 7in wifi versions is the main problem.
We have managed to get a version of CM 11 working, but some essentials such as wifi, bluetooth, and hardware composer are not easy with Marvel. We still have a lot of work to do and very little time to spend trying.
And the previous answer is also correct, you need more devs for the Tab 4.
Sent from my SCH-I605