Look, if like to start by saying I couldn't find the question section in tapatalk, and this seemed the most appropriate section to post in (move to correct one if necessary)
Anyway, my question:
I was wondering if it's possible to build either android honeycomb or tablet UI ICS (stock of course) for this kindle fire. I know that it seems weird to go back word in android versions, but honeycomb is my favorite and I wouldn't be able to build it as I don't have a Linux PC, and I'm having a surprising amount of trouble getting virtual box to work on my PC. (Yes, I'm using the correct cup architecture and have all required files) any feedback is welcome!
Edit: any way to edit the title? I didn't catch the typo... (Yet another reason to proof read)
Sent from my iPhone using Tapatalk
MeowDude said:
Look, if like to start by saying I couldn't find the question section in tapatalk, and this seemed the most appropriate section to post in (move to correct one if necessary)
Anyway, my question:
I was wondering if it's possible to build either android honeycomb or tablet UI ICS (stock of course) for this kindle fire. I know that it seems weird to go back word in android versions, but honeycomb is my favorite and I wouldn't be able to build it as I don't have a Linux PC, and I'm having a surprising amount of trouble getting virtual box to work on my PC. (Yes, I'm using the correct cup architecture and have all required files) any feedback is welcome!
Edit: any way to edit the title? I didn't catch the typo... (Yet another reason to proof read)
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
This would likely be better suited in the KFHD 8.9" Q&A forum. That being said, there will be significant work involved with porting. Honeycomb on these kindles would be like porting Windows 95 to run on a modern-day laptop. It might work, but it's unlikely. You'd have to spend a lot of time backporting Amazon's proprietary drivers (or even open source libraries, if such are still supported for older Android versions), and those are likely built with 4.0 in mind. Additionally, the underlying Android Honeycomb source code may not have critical components needed for proper operation on more recent devices like these. (It's worth noting that Amazon's stock firmware is based on ICS, so a large part of that work would likely be done already if you're porting that Android base.) Finally, I'd advise against porting older Android versions because they're not maintained or supported anymore by Google, so any compromising bugs or security holes (like the recent Stagefright issues) will not have been backported to those unsupported releases.
If you're still set on porting ICS, I haven't found any stock 4.0 build makefiles for the HD 8.9 on GitHub. You could use an unofficial prebuilt CM10.1 or CM10.2 ROM (look in the 8.9 development forum and use Xposed modules to modify the UI to tablet mode. I know of one Xposed module that backports tablet UI to JB ROMs, and it still works on KitKat/CM11. Those mods would save you a lot of time, as you wouldn't need to compile or backport older releases. If you want an up-to-date CM11 ROM to use the mods on, you'd need to compile with those sources (they're on GH here). If you're still having trouble, I'd be willing to compile CM11 for you.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
This would likely be better suited in the KFHD 8.9" Q&A forum. That being said, there will be significant work involved with porting. Honeycomb on these kindles would be like porting Windows 95 to run on a modern-day laptop. It might work, but it's unlikely. You'd have to spend a lot of time backporting Amazon's proprietary drivers (or even open source libraries, if such are still supported for older Android versions), and those are likely built with 4.0 in mind. Additionally, the underlying Android Honeycomb source code may not have critical components needed for proper operation on more recent devices like these. (It's worth noting that Amazon's stock firmware is based on ICS, so a large part of that work would likely be done already if you're porting that Android base.) Finally, I'd advise against porting older Android versions because they're not maintained or supported anymore by Google, so any compromising bugs or security holes (like the recent Stagefright issues) will not have been backported to those unsupported releases.
If you're still set on porting ICS, I haven't found any stock 4.0 build makefiles for the HD 8.9 on GitHub. You could use an unofficial prebuilt CM10.1 or CM10.2 ROM (look in the 8.9 development forum and use Xposed modules to modify the UI to tablet mode. I know of one Xposed module that backports tablet UI to JB ROMs, and it still works on KitKat/CM11. Those mods would save you a lot of time, as you wouldn't need to compile or backport older releases. If you want an up-to-date CM11 ROM to use the mods on, you'd need to compile with those sources (they're on GH here). If you're still having trouble, I'd be willing to compile CM11 for you.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Thanks for the feedback, my heart is indeed set on back porting honeycomb, I'll try later and see how it works out. I'm gonna have to research the recent stage fright bug (haven't heard of it). I figured I could just build android 3.2 from AOSP, set up the necessary drivers, and flash it. Even if that's not an option, I'll just try to build Stock ICS. I just like the older holo UI, and ICS and especially Honeycomb have it.
Sent from my iPhone using Tapatalk
MeowDude said:
Thanks for the feedback, my heart is indeed set on back porting honeycomb, I'll try later and see how it works out. I'm gonna have to research the recent stage fright bug (haven't heard of it). I figured I could just build android 3.2 from AOSP, set up the necessary drivers, and flash it. Even if that's not an option, I'll just try to build Stock ICS. I just like the older holo UI, and ICS and especially Honeycomb have it.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
If the holo UI is all you're interested in, you can use any recent ROM and this Xposed mod called Holo Themer that forces all apps that it can to fall back to the holo UI interface. Also, if you're running KitKat or below (CM11), you can use TabletKat, another Xposed mod to bring back the legacy tablet UI from Honeycomb/ICS.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
If the holo UI is all you're interested in, you can use any recent ROM and this Xposed mod called Holo Themer that forces all apps that it can to fall back to the holo UI interface. Also, if you're running KitKat or below (CM11), you can use TabletKat, another Xposed mod to bring back the legacy tablet UI from Honeycomb/ICS.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Sounds good, I'll check it out. On a side note, do you think it would be possible, after modifying the system UI, and all the system apps (framework.res,etc.,etc.) one could turn the stock Amazon OS into stock AOSP-like ICS? Just wondering, because it seems like every custom rom I find has some big I just can't stand (aside from the other ones) either it's too slow, no he youtube, the lock screen doesn't rotate, etc. while I've never had any problem with stock Amazon OS. (Other then that the may bar placement/UI/keyboard suck, but that's easily fixable).
Sent from my iPhone using Tapatalk
MeowDude said:
Sounds good, I'll check it out. On a side note, do you think it would be possible, after modifying the system UI, and all the system apps (framework.res,etc.,etc.) one could turn the stock Amazon OS into stock AOSP-like ICS? Just wondering, because it seems like every custom rom I find has some big I just can't stand (aside from the other ones) either it's too slow, no he youtube, the lock screen doesn't rotate, etc. while I've never had any problem with stock Amazon OS. (Other then that the may bar placement/UI/keyboard suck, but that's easily fixable).
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
It could be possible, but considering all the significant modifications Amazon made to the OS, it would most likely be a long, complex process. There may be xposed mods available to try to tweak the stock UI, and you could try to replace all the stock apps in the stock ROM with their AOSP counterparts, but there's always the risk of bootlooping the OS if you make modifications it doesn't agree with. I think you'd be better off using CM11 or a prebuilt custom ROM instead of trying to reverse engineer Amazon's source to reconcile it with AOSP.
Sent from my Amazon Jem using XDA Labs
I'm gonna try to work on that, there's no way I'm the only one who's thought to want the stock UI---interesting thing I found in the systemUI.apk, I found all the stock AOSP icons in SystemUI.zip/res/drawablehdpi even the tablet UI icons, which really through me off. Also, almost all the Amazon OS icons were in SystemUI.zip/res/drawable-- my idea, do some crazy xml/png editing, and get the stock UI I'm looking for. Your thoughts?
Sent from my iPhone using Tapatalk
monster1612 said:
...There may be xposed mods available to try to tweak the stock UI...
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Do have a list of these modules? I've set up xposed framework on mine, but I'm having trouble finding modules meant for kindles, and I don't want to be constantly playing the "trial and wait 10min to restore my compressed TWRP backup" game.
Sent from my iPhone using Tapatalk
monster1612 said:
...There may be xposed mods available to try to tweak the stock UI...
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Do have a list of these modules? I've set up xposed framework on mine, but I'm having trouble finding modules meant for kindles, and I don't want to be constantly playing the "trial and wait 10min to restore my compressed TWRP backup" game.
Sent from my iPhone using Tapatalk
I just figured out why it wasn't letting me send that last post...
Sent from my iPhone using Tapatalk
MeowDude said:
...almost all the Amazon OS icons were in SystemUI.zip/res/drawable-- my idea, do some crazy xml/png editing, and get the stock UI I'm looking for. Your thoughts?
Click to expand...
Click to collapse
You could do that, but I think it'd be easier to copy/paste icons from an AOSP/CM9 ROM. (CM9 is the corresponding version for AOSP 4.0.3, which is still ICS.)
MeowDude said:
Do have a list of these modules? I've set up xposed framework on mine, but I'm having trouble finding modules meant for kindles, and I don't want to be constantly playing the "trial and wait 10min to restore my compressed TWRP backup" game.
Click to expand...
Click to collapse
I haven't tried out the xposed framework on Amazon's stock OS, so I think you'll have to play with trial and error. However, you won't need to mess around with restoring TWRP backups - all you need to do to disable the framework is simply run touch disabled from the TWRP terminal in the /data/data/de.robv.android.xposed.installer/conf/ folder. Then reboot, uncheck the problematic mod in the Xposed Installer, delete that disabled file, and reboot to re-enable the framework.
Related
I would be greatful for someone to help me with getting honeycomb on the Kindle Fire. I Have access to all types of machines, so just any how-to's would be awesome.
Why do you want honeycomb? any reason?
We have an almost fully working copy of ICS. Is there a reason you want honeycomb instead of ICS?
I second this request I personally like honey comb better and also it nice to have options I have a little know how and would love to help
Sent from my RubiX ICS Infused using Tapatalk
im no developer, but as far as i know, i understand that honeycomb and ics are similar as far as kernels go and how the os works so this is just a shot in the dark, if what i hear is correct. you could, hypothetically back port everything from ics to honeycomb, except for hardware acceleration, because we have to have a custom kernel to get that to work, and our devs are hard at work with no luck as of yet. it shouldn't be too hard.
just my .02cents, i could be completely wrong, some one correct me if i am.
thrasherht said:
Why do you want honeycomb? any reason?
We have an almost fully working copy of ICS. Is there a reason you want honeycomb instead of ICS?
Click to expand...
Click to collapse
I just have never had a honeycomb device to be honest. I think it would be neat to port the rom.
Sent from my myTouch_4G_Slide using XDA App
Yes, I think it would be great if devs bring honeycomb to kindle fire. In fact I like the looking more than ICS and because there are a lot of tablets with honeycom out there it should be easy to port
One major problem; honeycomb was never opensourced by the AOSP team (they are still catching flack for it but moving on...) because of that there is no source tree to build from (you never wondered why cm8 was skipped?) the only way to get honeycomb on the fire is to port it in binary form from a similar device (this is not something I know how to do or intent on researching, sorry) I'm not providing this information to discourage but merely for the information (honeycomb would be cool lol) if someone with more binary porting experience wants to do this I'd say go for it and good luck.
If I'm not mistaken, wasn't the Honeycomb source released with the ICS source? Ill do some searching, but I'm fairly positive it was. And honestly, if they were released at the same time, I understand why the CM team would go with CM9 instead since ICS is the newer OS and is in higher demand. More options would be nice though.
Yeah, this was the first result I got from a search. The source is out there...
forum.xda-developers.com/showthread.php?t=1346829
Sent from my SGH-I727 using xda premium
Sully6789 said:
If I'm not mistaken, wasn't the Honeycomb source released with the ICS source? Ill do some searching, but I'm fairly positive it was. And honestly, if they were released at the same time, I understand why the CM team would go with CM9 instead since ICS is the newer OS and is in higher demand. More options would be nice though.
Yeah, this was the first result I got from a search. The source is out there...
forum.xda-developers.com/showthread.php?t=1346829
Sent from my SGH-I727 using xda premium
Click to expand...
Click to collapse
Well that's news to me lol; if I get bored I might actually have a look at that (I have nothing to test it on atm lol)
In all practicality it would make more sense to try to update the system ui for cm9 with the options wanted from honeycomb that were not in ics, reason being we still have no cm8 to port so anything built from honeycomb would be vanilla and not cm (not necessarily a bad thing). If you have a read it looks like they did not provide any revision tags for honeycomb however; which means if I'm not mistaken I will have to clone the entire history without choosing a branch to look lol.
Edit: I was mistaken, not choosing a branch (as I should have obviously realized) gits from master, durr lol. However I did definitely get bored so here I sit trying to figure out the best way to sync honeycomb.
So I cloned a single repo and ran git branch -a : as you can clearly see by the following branch list there is no honeycomb branch tag:
remotes/origin/HEAD -> origin/master
remotes/origin/donut-release
remotes/origin/donut-release2
remotes/origin/eclair-passion-release
remotes/origin/eclair-release
remotes/origin/eclair-sholes-release
remotes/origin/eclair-sholes-release2
remotes/origin/froyo
remotes/origin/froyo-release
remotes/origin/gingerbread
remotes/origin/gingerbread-mr4-release
remotes/origin/gingerbread-release
remotes/origin/ics-factoryrom-2-release
remotes/origin/ics-mr0
remotes/origin/ics-mr0-release
remotes/origin/ics-mr1
remotes/origin/ics-mr1-release
remotes/origin/master
The source is in there in the commit history but the only way you can get to it that I can think of is to clone each repo and revert the commits back one at a time (I'm far too lazy for this).
Brings me back to one of my earlier points; porting the elements wanted into the existing roms or porting a binary from a similar device (for which you would want to start by finding something with a similar omap cpu, I'm sure a google sure would yield some results for those wanting to look into porting a binary)
From what I have read Google has publicly admitted to not releasing Honeycomb because it was rushed and is below Google's normal standards and that they would be rather embarrassed to have put out sloppy work. With that said I would still like to see Honeycomb as an option on the Kindle. The more the merrier is pretty much the way I look at it.
I don't understand why you would want Honeycomb if you have ICS. ICS is basically the same as Honeycomb with more features.
Honeycomb was integrated into ICS. There is no real Honeycomb branch. Yes, google was embarrassed with how bad honeycomb came out since it was so rushed. Thats the main reason they didn't want to release it. After all, it was sloppy code. ICS has the tablet interface built into it.
Honeycomb might happen on the kindle fire eventually, but ICS should be the priority.
As everyone has said, honeycomb is harder to build, less feature filled, and older than Ice cream.
Until ICS it's flawless, I wouldn't keep your hopes up.
Without the source or a similar device to port from, there isn't a good place to start.
My recommendation: Get ICS and put a HC theme on it. It'll run better, sooner and go longer before it's depreciated. Plus Google Chrome only works in ICS.
I'm not a dev, but would it be easier to get hwa with honeycomb than ics? just asking!
No...
Only way to get Honeycomb would be a similar device that already has it.
therefore you cant edit the source code of the files. So you wont get HWA
death2all110 said:
No...
Only way to get Honeycomb would be a similar device that already has it.
therefore you cant edit the source code of the files. So you wont get HWA
Click to expand...
Click to collapse
Nope, that's not true. The source is there, it's just not clear where honeycomb ends and ics starts. I've looked a bit into the source code, i saw some default.xml files with should checkout the right commits for 3.0, 3.1 or 3.2. When i saw that i was happy as i thought it was easy, but i tried them out and it failed at building inside frameworks/base. It looks that the commit-sha1's inside these default.xml's are only relevant for the GPL components. The next thing i did was to revert every .git to 2011-08-30 (the release date of 3.2.2, i've looked into the version history of framworks/base and it looks like the first reference of ics starts after that):
Code:
SOURCE=/path/to/source
while read line
do cd $SOURCE/$line
echo $line
git checkout `git rev-list -n 1 --before="2011-08-30 23:59" HEAD`
done <.repo/project.list.revert
where .repo/project.list.revert is the list of projects to revert. I've still got a lot of compile errors, fixed some but now i hang with some problems with clang. But maybe it could work when you only take the projects of these base-for-3.?-gpl.xml files from ics and revert them. The lists of projects change a lot between 3.0<->4.0.
The good thing about honeycomb would be that it's based on the 2.6.36 kernel so it think it still uses the old renderer for video acceleration. (Did not saw any reference of rpmsg in regard to honeycomb)
my 2 cents on honeycomb
As an Acer a500 iconia owner, I simply love honeycomb. I've been an avid android user since the T-Mobile g1 and android had become second nature to me by the time I got my hands on honeycomb. Ics is very similar but I do have my gripes. 1st being I don't like the way they swapped the confirmation screens "OK" and "cancel" buttons...not such a big deal but it was never an issue before, so y fix what ain't broke? 2nd, i cant ever recall a time where i installed an app on hc and had it act all funky the way i have it happen on ics builds for the several devices that i own that do run ics. With that said, I'd love hc on my fire, as I've grown very accustomed to it on my iconia tab. Maybe once all these HWA issues are ironed out we may start seeing some hc builds. Thanks to all the devs and all their hard work for making everyone of our kindles better than amazon ever could
---------- Post added at 08:22 AM ---------- Previous post was at 08:19 AM ----------
Even with my a500 running ics, I get all kinds of fc's and a lot of apps just fail to run what so ever, so I can see where the OP is coming from, so much so, that I'm back running 3.2 on my iconia
ICS is to Honeycomb what Win 7 was to Vista. Both are what their forerunners should have been in the first place, and are really only a more finished version.
Having run Honeycomb on a couple of Tegra 2 devices for a while, and then playing around with ICS, I can't honestly imagine why any dev would waste his time with Honeycomb, unless you're doing it for the "just because" factor. But if that's the case, why not port Froyo or AOSP Gingerbread or Tap n' Tap too?
Screw Win98 and XP. Give me WinME.
jmcoffey said:
I would be greatful for someone to help me with getting honeycomb on the Kindle Fire. I Have access to all types of machines, so just any how-to's would be awesome.
Click to expand...
Click to collapse
I would try starting with any ROM you can find from the Toshiba AT200, it apparently has the same processor and therefore a similar if not the same Kernel. Then try and get the drivers for the Kindle Fire to make sure that the screen and everything else is compatible. Stop back and let us know how it goes!
As most users on XDA, I've got a rooted device that I want to use a custom ROM on, and there are so many choices it makes choosing a ROM very difficult.
And it is all a matter of preference, depending what included features (included Gapps, default launcher, notification options, etc) or what base it is built from (CM10, AOSP, AOKP, etc) everyone has their own preference.
I created this public spreadsheet, but I thought it may be useful for others, and allow others to possibly to keep track of what features are included out-of-the-box on different custom ROMs. It has really taken off since I originally created it.
http://goo.gl/U8a0E
Hopefully this can help others like me who want to quickly know what features they will or won't have with different custom ROMs.
I considered trying to do a forum post on this, but obviously I would have to keep up with updates myself on Post #1 like most stickied reference posts, that's why I thought a public Google Spreadsheet would be more helpful as anyone can update it.
Overall, a lot of this will probably be moot once a stable CM10 is released, but we never really know how long that can take. And we all know there will still be customizations made to it, one I can think of specifically is Paranoid Android.
Thanks everyone who makes updates to the sheet. I would also like to throw out a HUGE thank you to the custom ROM makers giving us stable ROMs that meet our individual needs.
And, as the Google Doc can be viewed by ANYONE, must get permission on google account to edit.
My personal "Must Haves":
- T9 Dialer (avoid having to install separate dialer app)
- Customizable Notification drop down for Additional Toggles (this has replaced the need for Widgetsoid2 since I can have the Flashlight and Wifi AP here.)
- Reboot and Reboot to Recovery in Power Menu (Mostly Reboot as a minimum as I sometimes forget to turn it back on if I Poweroff)
- Battery Percentage in Status Bar (The logo itself is no where near specific enough for my needs, and I now prefer the circle style)
NOVEMBER 24, 2012 UPDATE: Personally I've switched over to Paranoid Android 2.99.3 (beta 3), it doesn't have my personal must haves yet, but I'm sure it will, currently I'd rather have 4.2 and lose a few features, than be running 4.1.2, it is one of the first roms with customizations to be released on AOSP 4.2, so until it is 3.x it could have some bugs.
HwyXingFrog said:
I've tried a few ROMs on my Unlocked GSM Galaxy Nexus and am still trying to find the ROM that has all the features I want. And is the most stable with those features.
I just created this public spreadsheet, mostly for my own use so it is very basic at the moment. But I thought it may be useful for others, and allow others to possibly to keep track of what features are included out-of-the-box on different custom ROMs.
https://docs.google.com/spreadsheet/ccc?key=0AggpxyzXBu--dEZMWnZTUWtMVXBpdHNteW5zTXpRVmc
Hopefully this can help others like me who want to quickly know what features they will or won't have with different custom ROMs.
I considered trying to do a forum post on this, but obviously I would have to keep up with updates myself on Post #1 like most stickied reference posts, that's why I thought a public Google Spreadsheet would be more helpful as anyone can update it.
Like I said, it is very empty right now and is completely open to others who want to make changes to it.
Overall, a lot of this will probably be moot once a stable CM10 is released, but we never really know how long that can take. And we all know there will still be customizations made to it, one I can think of specifically is Paranoid Android, and I haven't even included it on the Google Spreadsheet yet as I still haven't tried it.
I would like to throw out a HUGE thank you to the custom ROM makers giving us stable and fast versions of what CM10 can't do yet, isn't stable enough to use yet, or may never do in some cases.
Click to expand...
Click to collapse
This is nice. I have bought gnex seven days ago and tried every JB ROM so far.
Also I noticed that paranoid, like you said ( the only ROM that I am using as a daily driver ) is not on this list.
You really should try his alpha 1.9.1 with included kernel. Well now all kernels work on this ROM. But I think that gnex is the beast already and doesnt need any Custom kernels.
Hey I like Franco kernel and I purchased his app and I am playing a lot with it, but as long as I need decent battery life I will use stock kernel. On that ROM I had only 2% of battery dropped in amazing 6 night hours. I just couldnt believe my eyes.
Sent from my Galaxy Nexus using xda app-developers app
dejson said:
This is nice. I have bought gnex seven days ago and tried every JB ROM so far.
Also I noticed that paranoid, like you said ( the only ROM that I am using as a daily driver ) is not on this list.
You really should try his alpha 1.9.1 with included kernel. Well now all kernels work on this ROM. But I think that gnex is the beast already and doesnt need any Custom kernels.
Hey I like Franco kernel and I purchased his app and I am playing a lot with it, but as long as I need decent battery life I will use stock kernel. On that ROM I had only 2% of battery dropped in amazing 6 night hours. I just couldnt believe my eyes.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Yeah, I was trying to find a good ROM to get me by until CM10 was officially released as "Stable", and I was going to wait until that to try Paranoid Android, especially with all the customization I can do in it.
I may have to give it a try, maybe once I see my spreadsheet fill up with more user input. I'm already seeing a lot of activity on the sheet.
HwyXingFrog said:
Yeah, I was trying to find a good ROM to get me by until CM10 was officially released as "Stable", and I was going to wait until that to try Paranoid Android, especially with all the customization I can do in it.
I may have to give it a try, maybe once I see my spreadsheet fill up with more user input. I'm already seeing a lot of activity on the sheet.
Click to expand...
Click to collapse
Great thing, i've just checked the document and cant believe. Excellent and I'm glad to see that there is no problems with paranoid rom so far. I respect the work of all developers, but for me paranoid is the best so far, phablet mode is excellent and original approach.
Message
Sent from my Galaxy Nexus using xda app-developers app
dejson said:
Great thing, i've just checked the document and cant believe. Excellent and I'm glad to see that there is no problems with paranoid rom so far. I respect the work of all developers, but for me paranoid is the best so far, phablet mode is excellent and original approach.
Message
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
+1
Great idea, love the list. Love the idea of being able to let anyone edit it.
Excellent
ThunderStick said:
Great idea, love the list. Love the idea of being able to let anyone edit it.
Excellent
Click to expand...
Click to collapse
Thanks, I assume you added Soft and Chewy.
I'm downloading the newest CM10 and JellyBro to load onto my Nexus quick, hopefully I will get those two filled in completely, then at least I will know where my baseline is for my own personal comparison.
A few people have messed it up a bit and I'm sure some changes got lost, but if I don't leave it wide open, I know a lot of people won't make changes.
So, after all of that, and the spreadsheet getting updated by users pretty nicely, it looks like there is a functional enough CM10 (from the +Google page) v1.8 that is stable enough for me to start using as a daily driver for at least a few days.
I'll be using Gapps-b as I need Picasa sync to be working.
Damn! That's great work, well done! Keeping this up to date will be the hardest part but if you manage it you will help the Galaxy Nexus community a lot! I'll try to help. Keep up the good work.
HwyXingFrog said:
Thanks, I assume you added Soft and Chewy.
I'm downloading the newest CM10 and JellyBro to load onto my Nexus quick, hopefully I will get those two filled in completely, then at least I will know where my baseline is for my own personal comparison.
A few people have messed it up a bit and I'm sure some changes got lost, but if I don't leave it wide open, I know a lot of people won't make changes.
Click to expand...
Click to collapse
I would probably leave the battery life comparison off. This is very subjective on any Rom or device.
Sent by tapping my screen as it lays on some hookers back, while I tap that ...
ThunderStick said:
I would probably leave the battery life comparison off. This is very subjective on any Rom or device.
Sent by tapping my screen as it lays on some hookers back, while I tap that ...
Click to expand...
Click to collapse
I agree, I didn't put the battery life on there, all roms except the Nightlies like to advertise "Good" battery life anyway.
That's one of the issues with leaving it editable by anyone.
HwyXingFrog said:
That's one of the issues with leaving it editable by anyone.
Click to expand...
Click to collapse
You could leave the public version as is, but add a "revised" version (editable only by you) that weeds out any egregious and obvious inaccuracies.
Oops misread.
I started one of these back in the day for the droid Eris. You should be able to leave it public, you can always see and revert changes.
Can we get a column for cdma vs GSM?
Sent from my Galaxy Nexus using xda premium
Thanks for sharing man! Im using xenonhd ad my first custom ROM band its fine
Sent from my Galaxy Nexus using xda app-developers app
So, overall, I definitely accomplished what I wanted to do with the Google Doc, everyone has been awesome with their updates to it.
But, for myself, the Doc is basically useless as soon as I found CM10 v1.8 on the +Google page, which is basically a very stable nightly (although it isn't), it is exactly what I wanted....
It's very stable, gives me all the features I have as my "Bare Minimum"
- Toggles in notification screen
- Battery Percentage in Status bar
- Reboot options in shutdown menu
I ended up in the exact same state after trying numerous custom roms on my HTC Desire and Motorola Atrix previously, always just ending up with CyanogenMod7.
And I happened to just fall onto the +Google post with v1.8 while compiling the Google Doc. Was about to download 1.3 then 1.8 was posted and I'm LOVING it.
And as long as I stick to CM10, I shouldn't have to wipe my data, I'm tired of doing all my Titanium Restores (as I don't have the paid version).
Again, thanks everyone for updating the Google Doc, and as I've made it public, anyone should be able to update it and keep it updated for other people out there that want to use custom roms. And if anyone ever needs to revert anything that really breaks it, all you have to do is log in with your google account.
I really hope it helps some people find the ROM they want to use for their specific needs. And it would be nice to see more of these for different devices, especially for devices not officially supported by CyanogenMod. I may have to get one started for my Motorola Atrix 4G.
Anyone notice this on both CM official and jelly bro.
There's no Document Viewer app??? it's in stock! I can view pdf, microsoft word, without needing to download 3rd party app.
Show widget before lockscreen seems not working in both CM official and jelly bro.
Great work. Should always be maintained and help users what they really want.
Sent from my Galaxy Nexus using xda app-developers app
Bayint Naung said:
Anyone notice this on both CM official and jelly bro.
There's no Document Viewer app??? it's in stock! I can view pdf, microsoft word, without needing to download 3rd party app.
Show widget before lockscreen seems not working in both CM official and jelly bro.
Click to expand...
Click to collapse
It may be in stock, but is not in AOSP.
Plenty of apps on the market for it, which is how we justify not adding one.
adrynalyne said:
It may be in stock, but is not in AOSP.
Plenty of apps on the market for it, which is how we justify not adding one.
Click to expand...
Click to collapse
Speaking of that, does anyone know what document viewer the stock Nexus uses, and if there is an Play App, or APK I can install on CM10 that is the same.
I have Documents to Go, but I'm wondering what the Stock nexus one is.
I've added this to the spreadsheet as CM10 not having one, so if we know which app the Stock has I can put that on the spreadsheet.
Thanks.
Hey guys,
So this is my second question post after asking for proper guidelines on how to root. It was hard at first but after trying it it was pretty easy. I've looked at other threads like this but ROMS constantly changes and update and many new one's are released (what I am observing).
I'm really lost on terminology, what does AOKP or AOSP mean?
Is there one which is the "fastest" or most "fluid?"
What's the difference between some of the popular ones?
Am I alone for thinking that TouchWiz is more beautiful than CM10?
Any recommendations? (I'd prefer one with GWallet enabled, Rooting, etc...)
Which one has best extended features or customizability?
Thanks again! The android community is great!
EDIT: Where can I buy the cheapest/modern looking NFC tags? I found these are there any other smaller ones or anything else I should take a look at before buying?
http://tagsfordroid.com/tags/Home.html
I can help with terminology - look at the top of the "General" section for a sticky called "XDA and Android Terms and Acronyms". That should help you get started.
As for what's best, it's pretty much a matter of just trying out different ones to see what works best for you.
Bronos said:
Am I alone for thinking that TouchWiz is more beautiful than CM10?
Click to expand...
Click to collapse
Yes.
Sent from my Motorola DynaTAC 8000X
no you are not alone...it really is a matter of preference and style
Quick synopsis:
In simple terms, there are stock Samsung based roms, which will have Touchwiz as launcher or one available from the market in addition, and there are ROMs developed striaght from Google sources without the Samsung layer or interface (e.g. Touchwiz) -- those are CM10, AOSP and AOKP -- all multi-platform, open source muti-developer community interactive projects, with many avid adherents.
Some of it is look and style, other times people prefer the google based systems as they are "pure" -- more significantly, they tend to have continuous and ongoing development.-- so there are official JB roms with a CM10 or AOSP, AOKP base -- except the source is official , the development is all the open source community.(confused yet?).
In the Samsung ROM department there are basically those that are based on stock releases (latest being the ICS 4,04 firmware) and those based on initial or leaked firmware yet to be officially released (latest being JB 4.1.1). IN general terms, if you are comfortable flashing and being an early adopter (think some errors and problem solving) then leaked firmware ROMs are fun. If you are new and/or unsure about messing with settings, stick with an officially released firmware ROM.
And, if you don't like Touchwiz and/or just appreciate the putiy and spirit of the community, go CM10 AOSP or AOKP.
Good news, is there are many good developers and many helpful people throughout.
One good hint: always ask questions first and then flash -- rather than making a mistake and then asking someone to help you recover. ALso, read the thread for the ROM you choose -- most questions have been raised and solved by the regulars on any thread.
Hey man that was very helpful! Do you know how I can better transition into CM10? I tried backing up all my data and apps using TBP but my widgets, folders, and settings didn't transfer over. Os there a way to get EVERYTHING to transfer over?
Sent from my SPH-L710 using xda premium
Bronos said:
Hey man that was very helpful! Do you know how I can better transition into CM10? I tried backing up all my data and apps using TBP but my widgets, folders, and settings didn't transfer over. Os there a way to get EVERYTHING to transfer over?
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
To recover your widgets, if you were using a 3rd party launcher (such as Nova, Apex, etc), you could restore the data only for that launcher with TB. If not, you will have to start from scratch, as the Touchwiz launcher does not exist in CM10. You can also restore data for settings, but this is usually not desirable as it could conflict and cause instability. I use SMS+ Backup to backup my SMS messages when I switch ROMs, TB to back up app data for installed apps (not system stuff) and Nova launcher. In Nova launcher, if you remember to use it, you can back up the launcher data and screens (widgets, folders, etc). You can then restore from the Nova Launcher when you install a new ROM. This is probably more stable then restoring via TB, but I have not had any issues restoring that from TB in the past.
My rule of thumb with TB is to never restore apps, only data. So I'll re-install my apps from the Play store and then restore the data for those apps from TB.
Hope this helps.
Andromadus - Test Builds
To start with here you will find test versions of ROMs built by me from the Andromadus github repo http://github.com/Andromadus, think of them along the same concept as nightly builds just not every night These are development ROM's, if you want to run bleeding edge development ROM's and at least know how to use adb and logcat then you might find something of interest here. If you require something that works 100% of the time all of the time then this might not be for you. That said you can always give it a try and if it doesn't work restore your previous nandroid backup!
What IS Andromadus?
Initially it was a group of people who got together to make ICS work on the HTC Desire Z because nobody else seemed to want to support devices with physical hardware keyboards/trackpads. Whilst the idea stays the same It has grown slightly to support some other hardware and some of the work we have done is now used in many other devices. Andromadus builds of CM10 or CM10.1 are basically CM sources with a few additional tweaks or additions to support our phones.
1. New versions will be added as and when I feel there are enough changes to warrant one, don’t ask when the next version is coming.
2. If we decide to release a "Stable" version of these roms they will be published in another Andromadus thread.
Direct all your queries with release versions to that thread and in the same vain do not discuss these releases anywhere but here.
3. I will do as best I can to answer questions but if you don't get an answer from me I'm sure somebody else will be along to help. Help each other and I have more time to spend fixing things!
4. Don't ask for what's changed since the previous version, have a look at the recent submits on the Andromadus github if you want to know or wait for the mini changelogs when I post a new release.
5. If there is something in particular to test it'll be mentioned!
6. As always if you didn't wipe between installations then at least verify that the problem exists on a clean install before posting here. Nandroid/superwipe/install/check at the end of the day you can always restore your nandroid if the problem is reproducible on a clean installation. If you can't be bothered to try this then I really can't be bothered to try to help you :>
7. All that said ensure you make a nandroid/backup before hand. I take no responsibility for what you do to your phone with these ROM.
8. Whilst I can't stop you I would rather these builds were not used as a base for any ROM/MOD/ETC. The source is all available if you want to do your own builds with which you can do whatever you like.
9. Tell us what works/what's worse/what's better but don't ***** when something breaks or isn't fixed yet, report it and move on.
10. Sometimes people forget that we do this for fun, for ourselves, and sometimes your super important issue is way down on our personal list of things to be fixed.
If you ignore any of the above you will in turn be ignored.
Now that's all out of the way as always have fun
As usual you need to flash the ROM then GAPPS.
Checkout http://andromadus.flinny.org for links/files/changelog's
This a team/community effort, I'll not list everyone who has helped along the way here that list is in the beta thread but I will say thanks to all of them again and obviously anyone that has been missed.
Current Build Changelog
Build 16
Rom
Should have fixed the zoom problem with browser some were having with large fingers/thumb presses.
Notification LED should be green again.
Disabled sliding picture animation when taking a picture for now.
Saga, rotation issue should be resolved again.
Everything else synced with CM.
Kernel
Patched to 3.0.66
Saga - S2W should be disabled by default on a clean install
Increased PMEM allocation on both SAGA and VISION as we were having out of PMEM issues sometimes when coming out of standby.
MDDI - sorry still need an updated kernel for you.
Checkout http://andromadus.flinny.org for previous changelogs
Looking forward to this
Flinny said:
Files still uploading...
Click to expand...
Click to collapse
Could you please reply back when you've made the files available? Thanks!
rubin110 said:
Could you please reply back when you've made the files available? Thanks!
Click to expand...
Click to collapse
Uploaded
Sent from my Nexus 7 using Tapatalk 2
rubin110 said:
Could you please reply back when you've made the files available? Thanks!
Click to expand...
Click to collapse
http://andromadus.codefi.re/ and sort by 'Date'
Wooo! Trying this
Can I flash directly over 4.1.2 build 129?
or would you recommend a clean wipe : ]
or check the link to the new website on the OP
I would suggest doing a wipe as Gapps etc are all different... if you do try an upgrade then I would suggest backing up... flashing rom/new gapps/wipe cache/dalvik at least.. then most likely finding it didn't work and having to wipe anyway
Nick.
Thx so much. I will try it.
Just tried installing directly over 129, rotation broke so I'm going to try from a full wipe. ( everything else is hunky dory really, although took a quite some time for the phone to calm down and get back to it's usual pace)
By the by, I notice the kill all icon from 129 is gone, is there anyway I can add that myself rather than wait for an update? ( as it's super handy!)
Thanks again flinny and Andromadus folks! My phone is even more woosh woosh and fancy than ever before.
Great job Flinny! You have done quite a lot.
just a question... what is the difference between the cm10.1 and the aosp 4.2? Is cm10.1 the beta release? or are they new test builds based off of cm and not just aosp?
jspina said:
Great job Flinny! You have done quite a lot.
just a question... what is the difference between the cm10.1 and the aosp 4.2? Is cm10.1 the beta release? or are they new test builds based off of cm and not just aosp?
Click to expand...
Click to collapse
ASOP is stock Android, CM10.1 is with Cyanogenmod and Andromadus tweaks. ( I.E more things to mess about with! yay)
Okay got all my apps reinstalled after a fresh wipe and this Rom is daaamn smooth.
All the default apps run without a hitch, and none of my extra apps have caused any issues either ( got 50 installed)
Just needs lock screen short cut tweaks, statusbar/notifcation tray colour/alpha picker and a kill all apps button and this would be puurrfect.
More than happy to use it as is though, runs great.
Pantherx12 said:
ASOP is stock Android, CM10.1 is with Cyanogenmod and Andromadus tweaks. ( I.E more things to mess about with! yay)
Okay got all my apps reinstalled after a fresh wipe and this Rom is daaamn smooth.
All the default apps run without a hitch, and none of my extra apps have caused any issues either ( got 50 installed)
Just needs lock screen short cut tweaks, statusbar/notifcation tray colour/alpha picker and a kill all apps button and this would be puurrfect.
More than happy to use it as is though, runs great.
Click to expand...
Click to collapse
Thanks. I know what the differences between the two are. I was just wondering if thats all that differentiated the two. And after looking at the titles its obvious that they are.
haha took me a few mins to realise this is the new cm 10.1 anyways good work as usual flinny downloading now
Sent from my HTC Vision using xda app-developers app
Am I being stupid or is there no developer menu item under settings? Additionally missing is the glorious Performance menu item too.
Also having some troubles connecting to wifi access points after the initial setup.
Flinny please make name theme more easy. It difficult to distinguish
Sent from my HTC Desire Z using xda app-developers app
rubin110 said:
Am I being stupid or is there no developer menu item under settings? Additionally missing is the glorious Performance menu item too.
Also having some troubles connecting to wifi access points after the initial setup.
Click to expand...
Click to collapse
Its missing in the settings menu for me also. And wifi works but sometimes it doesn't connect, everything else seems to work
Sent from my HTC Vision using xda app-developers app
Go to about phone and tap build number until it tells you that your now a developer....
Sent from my Nexus 7 using Tapatalk 2
Thanks flinny~~
It's so wonderful~
But I can't find the CM's function, like "Performance",
If the CM 10.1 have some function not implement??
Some features have not yet been ported to 10.1 by the CM team yet. But performance and developer are hidden in all 4.2 builds until you do the tap build number thing
Alright, this mod is dedicated to mariog, who helped me to not give up on this idea.
Now, on to the MOD...
This mod is a ROM that gives the NST an experience that is as-close-as-possible to legitimate Android. This mod will be flashed using the CWM for NST. There's one problem, I had a release ready, but when I tested it, well that's another story. The point is, I deleted alpha-1 in a fit of rage over it not working, so, I need more devs to help me build this, because A.) I can't dedicate my every waking hour to this. (I'm in school most of the time) B.) Because my first attempt failed even though I looked it over like a Trillion times. ( Just to clarify: it booted, but everything crashed. Literally everything) Obviously I'm doing something wrong. I've built unofficial ROMs before.
In the future, I hope to branch this mod out to other black and white Readers, But at this point, I'm just worried about the NST.
THE MOD WILL INCLUDE:
-The best homescreen possible for the NST (Was using stock 2.1 Eclair launcher, not sure what is best. Launcher 7 looks good)
-Barnes & Noble stock reading apps
-B&N OOBE. (Modified?)
-Android Market/Gapps
-Dropbox included in install
-No bloatware (ie: phone.apk etc)
-Best NST internet browser (opera mini) installed as default browser)
-"Chef's freezer" app (look it up)
-Probably more.
-I will also include a minimalistic version. (No: dropbox, browser, freezer, Gapps other than Gmail)
All I need is devs willing to devote just a little bit of their time to this project.
Note: ROM based on android 2.1, I will try to do 2.3 once CM7 support is made for the NST.
Note2: All you readers will be lucky if I get any sort of release anytime soon. Don't rush me. If you want to get this fast, then you can help me! I need beta-testers and devs anyways. No unofficial releases will be made to non beta-testers. If you want them, become a beta-tester!
Reserved for downloads
Sent from my NookColor using xda app-developers app
Reserved for changelog
Sent from my NookColor using xda app-developers app
Reserved for current devs/beta-testers
Sent from my NookColor using xda app-developers app
Thread closed, we do not allow place holders here, if your looking for devs etc then post in general section.
If at some point you have something to share then feel free to contact me and I shall unlock the thread.