Related
Does any one else think that Google should be spending a lot more time here on xda and learning from the devs?
Just little features like being able to hide and unhide the nav bar, and edit the buttons of the nav bar...
Getting the smoothness of the stock launcher sorted once and for all that some custom rooms have managed...
The few extra targets on the lock screen.
You get the idea. Just little tweaks that are missing from stock that I feel should have been added from the start.
A company that large with that much resource should surely b thinking of these things before Joe bloggs comes along and adds it for them.
Sent from my Galaxy Nexus using XDA
zolah said:
Does any one else think that Google should be spending a lot more time here on xda and learning from the devs?
Just little features like being able to hide and unhide the nav bar, and edit the buttons of the nav bar...
Getting the smoothness of the stock launcher sorted once and for all that some custom rooms have managed...
The few extra targets on the lock screen.
You get the idea. Just little tweaks that are missing from stock that I feel should have been added from the start.
A company that large with that much resource should surely b thinking of these things before Joe bloggs comes along and adds it for them.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
If I recall correctly some of the new features in ICS from the Cynogenmod team (the only one that I can recall is the swipe away notification menu list).
But yea I agree, those little tweaks that you mentioned would be sweet to have in future releases of android...and who knows maybe they are paying attention and in the next (major) update of theirs we might get new features.
Yes/No.
I'm sure some Google employees might check sites like this from time to time, but more often than not they're aware of bugs before most of the XDA population notices them. Legitimate issues will be reported to their bug tracker quickly I'm sure.
People may get impatient waiting for a fix, thinking, the Big G is oblivious, but the majority of the time they're a few steps ahead of most users here and a fix has been in the pipe for a while. I'm sure it's someone's, or someTHING's job, to harvest pertinent info; Google is in the information biz after all. I doubt any Google (or AOSP) presence would ever be officially declared here; I can't picture that going well.
There is a gerrit for code submissions. If they are not submitted, good luck in seeing them considered for implementation.
However, devs like us tend to introduce problems as well. Unless it can fit into the master branch for all supported AOSP devices and appears to not cause issues with other items, it will be immediately thrown out.
Ever read rom threads? At least half the posts stem from problems that were created from tampering with code/adding features.
..and I don't want to hear "insert rom" is bugless, because it is not true for any rom.
adrynalyne said:
There is a gerrit for code submissions. If they are not submitted, good luck in seeing them considered for implementation.
However, devs like us tend to introduce problems as well. Unless it can fit into the master branch for all supported AOSP devices and appears to not cause issues with other items, it will not be immediately thrown out.
Ever read rom threads? At least half the posts stem from problems that were created from tampering with code/adding features.
..and I don't want to hear "insert rom" is bugless, because it is not true for any rom.
Click to expand...
Click to collapse
Good point for sure. I definitely do not want my phone to ship with the instability custom ROM lol.
And people won't be satisfied either way. They're gonna ROM their phone anyways, not all of these things need to be included in the shipping software.
Um...Google knows man. Come on, they are the largest search engine in the world. They know what CM team has added, they know what people dislike about their products, they know EVERYTHING.
I'm sure they are learning from the devs, also have to realize a lot of the things CM adds and the fact Google doesn't include a lot of the stuff is good for the mass, a lot of my friends have a Android phones.
I always root their phones and add toggles and the extra features and they don't even realize or use them because they don't care, but I'm sure they know what people do want and what people don't based on their search histories.
I thought about this the other day...
If any of these ROMs and Kernels were actually significantly better without compromising stability then the Google devs would be out of a job pretty quickly.
I think the main advantages of custom ROMs and kernels are:
- customization above and beyond standard - but Google wants too keep a uniform ICS theme.. and adding too much detracts from this... not to mention over complicating menus and settings
- performance from overclocking - again something Google doesn't want to do for stability and hardware reasons
- getting new releases and sources before OTA updates - for the phones that are Samsung controlled which have to wait ages for them.. and you can flash a stock image for this anyway.
So custom ROMs don't really add that much that Google would want in its stock builds
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.
I sincerely apologize if this is not posted in the correct location or if such a request is out of line. The only reason I am posting about this is because I believe that there would be a fair amount of people who would be interested.
I've installed many ROMs since I got my Galaxy Nexus on release day last year, but I have always come back to AOKP because every other ROM I've installed was missing at least one feature of AOKP that I use. Recently however I started playing with DPI settings and I'm in love with 240. I like the tablet layout of most apps, but certain ones, like the phone app look a little strange. Also, some apps, like the Navigon navigation app are next to impossible to use at this DPI. Naturally, I immediately flashed Paranoid Android so that I could get the per-app control of DPI. That lasted all of about 10 minutes, because I immediately noticed it was missing far too many features.
So basically I'm looking to see if there's a dev out there who can kang the Paranoid Settings to AOKP. Maybe if there's enough interest from other people who would like this I could set up a pool for donations. I know there's a couple ROMs floating around that are AOKP based Paranoid rather than CM based, but they are for other devices.
Eventually I'm going to try to do this myself if no one else is willing/able, however between being in school full time and my two jobs I probably wouldn't be able to start teaching myself until about May. Plus, my laptop is about 6 years old and I'm afraid it will be an extremely slow process.
+100000000000^infinity
Sent from my Galaxy Nexus using Tapatalk 2
This!
Sent from my Galaxy Nexus using xda app-developers app
So far it seems like I've found three ROMs for other devices that combine PA and AOKP. King Kang for the Galaxy Note (which I think is still on ICS), PACman mostly on Sony devices as far as I could tell (PA/AOKP/CM), and Disarmed Toaster on some HTC phones. It's definitely possible and I imagine it would be quite popular...we just need to get a dev with a GNex to see the benefits!
Why don't you go to the AOKP thread and request the dev do so? Better to post there than here anyway. Don't get your hopes up though
Sent from my Galaxy Nexus using xda premium
jimmyhook said:
Why don't you go to the AOKP thread and request the dev do so? Better to post there than here anyway. Don't get your hopes up though
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
As far as I know they're still not interested in hearing feature requests unfortunately.
Sent from my ThinkPad Tablet using Tapatalk 2
I'm sure CM will become more of a beast with each update, and PA uses it as its base. Already highly customizable. I'm not even sure what the benefit of using AOKP as a base would be.
Sent from my Galaxy Nexus using xda premium
Love this idea I thought about something similar 2 weeks ago when I flashed CNA on my Gnex. I know there to different development teams but I would love to see a Code Name Paranoid ROM that ROM would kick azz but that just opinion but +1 to this idea
Sent from my Galaxy Nexus using XDA Premium App
jimmyhook said:
I'm sure CM will become more of a beast with each update, and PA uses it as its base. Already highly customizable. I'm not even sure what the benefit of using AOKP as a base would be.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
The benefit of using AOKP as a base would be that there are a lot of very useful features in AOKP that aren't in CM.
Sent from my ThinkPad Tablet using Tapatalk 2
I thought AOKP already had a tablet mode? But I haven't wanted to leave PA yet.
slow88lx said:
I thought AOKP already had a tablet mode? But I haven't wanted to leave PA yet.
Click to expand...
Click to collapse
It does. PA isn't about tablet mode, its about being able to control each app individually.
Sent from my ThinkPad Tablet using Tapatalk 2
slow88lx said:
I thought AOKP already had a tablet mode? But I haven't wanted to leave PA yet.
Click to expand...
Click to collapse
no, its has build.prop dpi and a sysUI hack.
JamMasterClay said:
The benefit of using AOKP as a base would be that there are a lot of very useful features in AOKP that aren't in CM. 2
Click to expand...
Click to collapse
honestly, i think people are not fair with cyanogenmod. cm is a great rom and has tons of features. yes you cant color your buttons pink other than using theming engine, but my goodness is that really such a strongpoint? toys will sure come aswell.
i have seen these mixups btw, paranoid + cm + aokp. it pains me. i wont interfere but man, this is crazy. one rom i have seen has four toggle implementations, two from cm, one from us, one from aokp, it mixes paprefs with aokps dpi changer and a non-standard build.prop dpi, etc. its a complete mess and sometimes i wish i wish they'd just kang hybrid engine without bringing our name into it lol. :silly:
the reason its not easily ported to other roms is that its complicated. its literally spanning all over android, framework, core, policy, res, graphics, parts of sysUI rewritten from scratch, androids layout definitions were changed, apps had to be adjusted - and then the hybrid engine itself of course. its not a simple "git fetch" and you got it, it grew over half a year, hundreds of commits, reverts and pushes.
what really matters is what's more important to you. a pink button or a completely renewed phone with functions it never had before. you know, we're developers, too. you might aswell request someone should bring over missing features to cm/pa, its getting a little bit discouraging to see the focus in all devcommunities is often on kanging instead of developing.
molesarecoming said:
honestly, i think people are not fair with cyanogenmod. cm is a great rom and has tons of features. yes you cant color your buttons pink other than using theming engine, but my goodness is that really such a strongpoint? toys will sure come aswell.
i have seen these mixups btw, paranoid + cm + aokp. it pains me. i wont interfere but man, this is crazy. one rom i have seen has four toggle implementations, two from cm, one from us, one from aokp, it mixes paprefs with aokps dpi changer and a non-standard build.prop dpi, etc. its a complete mess and sometimes i wish i wish they'd just kang hybrid engine without bringing our name into it lol. :silly:
the reason its not easily ported to other roms is that its complicated. its literally spanning all over android, framework, core, policy, res, graphics, parts of sysUI rewritten from scratch, androids layout definitions were changed, apps had to be adjusted - and then the hybrid engine itself of course. its not a simple "git fetch" and you got it, it grew over half a year, hundreds of commits, reverts and pushes.
what really matters is what's more important to you. a pink button or a completely renewed phone with functions it never had before. you know, we're developers, too. you might aswell request someone should bring over missing features to cm/pa, its getting a little bit discouraging to see the focus in all devcommunities is often on kanging instead of developing.
Click to expand...
Click to collapse
VERY well said.
molesarecoming said:
honestly, i think people are not fair with cyanogenmod. cm is a great rom and has tons of features. yes you cant color your buttons pink other than using theming engine, but my goodness is that really such a strongpoint? toys will sure come aswell.
i have seen these mixups btw, paranoid + cm + aokp. it pains me. i wont interfere but man, this is crazy. one rom i have seen has four toggle implementations, two from cm, one from us, one from aokp, it mixes paprefs with aokps dpi changer and a non-standard build.prop dpi, etc. its a complete mess and sometimes i wish i wish they'd just kang hybrid engine without bringing our name into it lol. :silly:
the reason its not easily ported to other roms is that its complicated. its literally spanning all over android, framework, core, policy, res, graphics, parts of sysUI rewritten from scratch, androids layout definitions were changed, apps had to be adjusted - and then the hybrid engine itself of course. its not a simple "git fetch" and you got it, it grew over half a year, hundreds of commits, reverts and pushes.
what really matters is what's more important to you. a pink button or a completely renewed phone with functions it never had before. you know, we're developers, too. you might aswell request someone should bring over missing features to cm/pa, its getting a little bit discouraging to see the focus in all devcommunities is often on kanging instead of developing.
Click to expand...
Click to collapse
Thank you for chiming in!
I would be glad to put the little extra effort into using ZipThemer to change the NavBar buttons/colors in exchange for having ParanoidPreferences. CM however is missing a lot of things that I haven't been able to find any other way of accomplishing other than using a ROM with the features built in. Let me provide thorough specifics. I don't know how familiar you are with AOKP Rom Control, and obviously this is all personal to me, so feel free to take this with a grain of salt. There's nothing in General UI, Lockscreen, Power Menu, Clock, Signal, Sound, Weather, Vibrations, or Performance that I use. The Navigation Bar section however is a lot better. Not because of color/icon selection but because of the longpress settings and because of the NavBar Ring Targets. Neither of those are things I could find a way to replicate in CM/PA, and both have proven to be extremely useful. Also, I like the ability to set NavBar height separate from status bar DPI...this may have been in PA but I missed it. In terms of Battery; I use the battery bar, and hide the icon in the status bar. I know there's an app with similar functionality, however it doesn't work the same. As far as I could tell Toggles were pretty much the same. For LED, I don't use any of the settings other than being able to have the LED flash with the screen on. This, to me, is a necessity.
I agree 100% that the PA/AOKP/CM combinations are a bit ridiculous. (If you notice in the OP, I was looking for someone to add ParanoidPreferences into AOKP, not combine the ROMs). If I had the time/ability to do it myself, I would remove the DPI, tablet mode, and dual panel options from ROM control and just add ParanoidPreferences.
As I said, I would gladly give up some "convenience" features of AOKP, but some of the actual functionality I can't do without at this point. I did post a couple feature requests in the PA forum, but I'm very hesitant to do so. You have done amazing work, and I always feel that by requesting more features I would be minimizing all the hard work the devs have done.
Sent from my ThinkPad Tablet using Tapatalk HD
I don't know if this will ever happen, but I agree.. I LOVE aokp and the fact that it has basic tablet mode, but I had to stop using it because a holistic "tablet button" isn't quite usable for me.
Sent from my Galaxy Nexus using Tapatalk 2
You said cm is missing a lot of things, but in the midst of your lengthy paragraph was only two or three small tweaks. No ROM can make everyone one hundred percent happy, but it sounds like PA has 99 percent of what you need.... am I missing something?
Sent from my Galaxy Nexus using xda premium
jimmyhook said:
You said cm is missing a lot of things, but in the midst of your lengthy paragraph was only two or three small tweaks. No ROM can make everyone one hundred percent happy, but it sounds like PA has 99 percent of what you need.... am I missing something?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I don't recall saying CM is missing a lot of things, but if I did than I apologize. In the OP at least I said this:
JamMasterClay said:
I have always come back to AOKP because every other ROM I've installed was missing at least one feature of AOKP that I use.
Click to expand...
Click to collapse
It's not about the amount of features, it's about weighing the importance of features. I guess in my mind I thought it would be easier to add ParanoidPreferences to AOKP rather than the other way around. Mostly, as I said, because the PA developers are busy with their own thing and don't need a bunch of people asking for new features. If those couple features could be added to PA that would be much preferred.
The problem with a lot of these popular high maintenance ROM's is that if the Dev's ever get taken away from their work on the ROM at any time, the project can collapse. This seemed to be to me, kind of what happened with AOKP.
What I've suggested in the past and still wondering if it's possible... is to create an app with access to "mount /system..." root privileges etc that is able to add mod's as installable updates/patches? If we had a system like this then all the developers could create mod's instead of an entire ROM and base it off a AOSP, which is technically what all ROM's are based off of anyway.
Then you could install each mod as you wish, just making sure it's compatible with your current firmware/software version.
This would be somewhat of a Cydia approach, the way jailbroken iPhones apply patches to the ROM.
I personally think this is a better idea than having a dedicated Developer OR Set of Developers for each ROM that continually have to be relied upon in order to maintain updates.
Does anybody think I'm speaking any sense here??
AOKP, first off, is very much alive.
Secondly, projects LIKE this exist.
FNV, for example, where everyone is encouraged to push their commits over for review.
There is no "lead developer" and it is the closest you'll get to what you're describing.
As far as just...installing patches and such to get a "flash what you want" type experience...
It isn't that simple.
Even if an open commit is left alone for a few days; it may need rebasing to merge into the branch.
Each little piece of each commit has to build on the previous merges and not interfere with them.
It's a cool thought, bit I can't see it being even slightly plausible.
Jubakuba said:
AOKP, first off, is very much alive.
Secondly, projects LIKE this exist.
FNV, for example, where everyone is encouraged to push their commits over for review.
There is no "lead developer" and it is the closest you'll get to what you're describing.
As far as just...installing patches and such to get a "flash what you want" type experience...
It isn't that simple.
Even if an open commit is left alone for a few days; it may need rebasing to merge into the branch.
Each little piece of each commit has to build on the previous merges and not interfere with them.
It's a cool thought, bit I can't see it being even slightly plausible.
Click to expand...
Click to collapse
Yea I see what you mean, im just wondering how Cydia for iOS interacts with the ROM to apply patches then..?? how have they managed to implement this kind of system?
FNV looks interesting but a little dead. On the other hand, I like how actively updated CM10 is, and it doesn't look like support is going to stop there anytime soon which is a big plus.
UKROB86 said:
The problem with a lot of these popular high maintenance ROM's is that if the Dev's ever get taken away from their work on the ROM at any time, the project can collapse. This seemed to be to me, kind of what happened with AOKP.
What I've suggested in the past and still wondering if it's possible... is to create an app with access to "mount /system..." root privileges etc that is able to add mod's as installable updates/patches? If we had a system like this then all the developers could create mod's instead of an entire ROM and base it off a AOSP, which is technically what all ROM's are based off of anyway.
Then you could install each mod as you wish, just making sure it's compatible with your current firmware/software version.
This would be somewhat of a Cydia approach, the way jailbroken iPhones apply patches to the ROM.
I personally think this is a better idea than having a dedicated Developer OR Set of Developers for each ROM that continually have to be relied upon in order to maintain updates.
Does anybody think I'm speaking any sense here??
Click to expand...
Click to collapse
Remember, the performance of a jail broken iPhone once you install those tweaks, let's just say, all hell breaks loose. My friends who jailbreak and use the simplest of jailbreak scripts and stuff all complain of lag on their iPad 2/3. I personally think its a hack job.
We have the source code unlike iOS, in the spirit of open source, developers download the source, make modifications, compile and make ROMs. They also give out the source to the public again so if anyone wants to base off any existing work, its okay. A great example is cm and perhaps Paranoid Android. And this method is flawed as other devices don't have AOSP support. I'm talking about S2/S3/HTC One X, etc. How are we supposed to make a single stable rom for them that's a clean aosp rom? Usually lots of hacking and tinkering and waiting for kernel sources is required to get AOSP on those devices. Its unlike the nexus where we have everything (source, proprietary drivers, etc) straight from Google. Anyway, that's my view. From the practical standpoint, you have to talk with other developers as ROMs come with their own framework and things.
Sent from my Galaxy Nexus using Tapatalk 2
---------- Post added at 01:31 PM ---------- Previous post was at 01:27 PM ----------
And another note, have a problem with a dead rom? Its probably stable enough for the developer. Or the developer has other important things in life. You can't blame them. What you can do is switch your ROM easily. If your looking for AOKP like ROMs, there's slimbean, CNA and Sourcery and even more that cram in all the tweaks. If you want a clean and minimal ROM, fast and stable, there are roms like Minco and rasbean jelly. Its seriously a different ecosystem than the apple cydia stuff, but it isn't a bad thing.
Sent from my Galaxy Nexus using Tapatalk 2
akash3656 said:
Remember, the performance of a jail broken iPhone once you install those tweaks, let's just say, all hell breaks loose. My friends who jailbreak and use the simplest of jailbreak scripts and stuff all complain of lag on their iPad 2/3. I personally think its a hack job.
We have the source code unlike iOS, in the spirit of open source, developers download the source, make modifications, compile and make ROMs. They also give out the source to the public again so if anyone wants to base off any existing work, its okay. A great example is cm and perhaps Paranoid Android. And this method is flawed as other devices don't have AOSP support. I'm talking about S2/S3/HTC One X, etc. How are we supposed to make a single stable rom for them that's a clean aosp rom? Usually lots of hacking and tinkering and waiting for kernel sources is required to get AOSP on those devices. Its unlike the nexus where we have everything (source, proprietary drivers, etc) straight from Google. Anyway, that's my view. From the practical standpoint, you have to talk with other developers as ROMs come with their own framework and things.
Sent from my Galaxy Nexus using Tapatalk 2
---------- Post added at 01:31 PM ---------- Previous post was at 01:27 PM ----------
And another note, have a problem with a dead rom? Its probably stable enough for the developer. Or the developer has other important things in life. You can't blame them. What you can do is switch your ROM easily. If your looking for AOKP like ROMs, there's slimbean, CNA and Sourcery and even more that cram in all the tweaks. If you want a clean and minimal ROM, fast and stable, there are roms like Minco and rasbean jelly. Its seriously a different ecosystem than the apple cydia stuff, but it isn't a bad thing.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yea I get what your saying.
Im not complaining about dead ROMs just was trying to think if there was a workaround. But yes I see your point about how a ROM developed from source would be less likely to lag.
I've been on CNA for awhile now, since AOKP slowed right now, and CNA is amazing. I guess CM10 is always a good backup if any of these ROM's stop updates.
thanks anyways.
Dont worry, you'll get your precious roms - this is an aosp device, after all.
Sent from my i9250
I just went from BAMF to Paranoid Android 4.2 and for the life of me I can't figure out why so many people are talking up this ROM, could someone please explain it to me because I need to be missing something.
The only thing that looked interesting was the UI features which do not work correctly. The Opaque Statusbar and Taskbar do not work. Randomly they will go back to solid black then never goes back to Opaque. The Tablet UI seems awesome but the Taskbar buttons are way to small. So I figured I would change the DPI but it makes the Statusbar clock huge and the notifications area pop-up moves half-way off the screen rendering it unusable.
So after those features are taking away there really is no custom / developer settings on the ROM so it's pretty much pointless.
A lot of people like a tablet UI but don't like the smaller DPI or visa/versa et cetera.
Jubakuba said:
A lot of people like a tablet UI but don't like the smaller DPI or visa/versa et cetera.
Click to expand...
Click to collapse
The Tablet UI is awesome but very poorly implemented it seems.
Shuino said:
So after those features are taking away there really is no custom / developer settings on the ROM so it's pretty much pointless.
Click to expand...
Click to collapse
I came from AOKP milestone 1 to PA 2.99.5 and while I like the 4.2 I'm thinking it might be time to go back to AOKP. I thought the Phablet UI was interesting but when I tried it... it didn't work correctly. I do like the per-app customization but I'd rather customize other areas of the phone with my time. Add I miss my integrated weather on the lockscreen.
illegalsmile said:
I came from AOKP milestone 1 to PA 2.99.5 and while I like the 4.2 I'm thinking it might be time to go back to AOKP. I thought the Phablet UI was interesting but when I tried it... it didn't work correctly. I do like the per-app customization but I'd rather customize other areas of the phone with my time. Add I miss my integrated weather on the lockscreen.
Click to expand...
Click to collapse
You are pretty much in the same boat am I. I was just hoping something happened during my install of Paranoid and that's why it wasn't working or features were missing or something. I'm glad I'm not the only one who thinks this ROM is defiantly lacking.
I am staying hopeful though. Once they get this ROM out of beta maybe Tablet UI will be working, and they will include some basic customization.
I do not see any problems with PA 2.99.5 whatsoever.. It works perfectly fine..smooth, good battery life, no lags, everything works as it should.. Once again, it is a matter of preference.. You putting up this thread was a matter of preference.. But once again, it is advisable that you do not complain by making a new thread.. Just post in the PA thread.. Molesarecoming is always open to constructive criticism..Once again, the word is "constructive criticism" the diversity of ROMs in the Galaxy Nexus community is what makes many stick with the nexus. so before bashing other ROMs, please just remember you not liking it, doesnt mean it's the same for others. If you hate it so much twitter it or fb it or something. >.<
Leemur89 said:
I do not see any problems with PA 2.99.5 whatsoever.. It works perfectly fine..smooth, good battery life, no lags, everything works as it should.. Once again, it is a matter of preference.. You putting up this thread was a matter of preference.. But once again, it is advisable that you do not complain by making a new thread.. Just post in the PA thread.. Molesarecoming is always open to constructive criticism..Once again, the word is "constructive criticism" the diversity of ROMs in the Galaxy Nexus community is what makes many stick with the nexus. so before bashing other ROMs, please just remember you not liking it, doesnt mean it's the same for others. If you hate it so much twitter it or fb it or something. >.<
Click to expand...
Click to collapse
I'm not bashing anyone work at all, honestly I just wanted to know if I was missing something from the ROM since so many seem to use it. I have used it for 2 days now and none of the UI tweaks are functional, or do not work properly or are just way to small with no functional way to increase size. But the ROM is smooth and quick with insane boot speed.
Here is info on PA 2.99+ in a nutshell. First and foremost, you all downtalking tabletui need to realize that it does not actually exist in android 4.2, the paranoidandroid team found it deactivated by google in the code for 4.2 and they spent their time making it available again, it is in no way a finished product, if you want to see it work good then download a version of PA with an android 4.1x base ( i.e. PA 2.54 or before). Now onto people that cannot see the big deal, well anyone that tried the pre 4.2 PA knows that there is more customization available in PA than any other rom put together. Now PA 2.99+ are all AOSP based instead of CM based so they basically are building this rom from scratch to improve speed, performance and battery life for everyone, this means that a lot is not even integrated back into the rom yet. Simply trying out the newest PA will not give you a feel for why it is hands down the best rom out there. As for transparency, that only works on the homescreen and in order to properly utilize it you must A. be using a compatible launcher which has the homescreen backgrounds drawn correctly ( i.e. Apex, Stock or Holo etc, NOVA does not work) B. Choose a correct transparent hexcode or slide the transparency bar to where you would like it for that said Launcher in the "apps" section of paranoid preferences. I am on 2.99 Beta 5 and have full transparency with no issues that you speak of (Photo included as proof), in fact, Beta 5 has added almost everything I want back into the rom and fully functional, I can hardly wait for v3.0, seriously, I cannot see ever using another rom after using paranoidandroid, it just has the edge on everything else out there. AOKP and CM have nothing on it especially when it's at 100% again, which will be in the next couple weeks at the rate it's awesome devs work at!
tabUI is not existant in 4.2, what you see right now is raw honeycomb. if you want to see how good it was install 2.54, thats still based on 4.1. but right now i got to make my hands dirty with this. i know that on xda most people do not understand the difference between developing and kanging, and they wonder "why's this rom slower than others" but someones gotta do the dirty work and im okay if crackflashers avoid ours. they avoid cm for the same reason.
as for hybrid engine, i dont think you have understood it yet. it works flawless and it gives you more customization than all roms on xda combined, IF you can handle it. yes, you are able to make a button pink in this and that rom, but hybrid can transform thousands of apps and components to the better, with practical implications that are unheard of. the apps that are running on your huge 720p screen were not optimized for it, they're in the same layout that applies to pocketwatches or stone age miniature phones like the htc wildfire.
as for opacity, no app, obviously, draws underneath the bars - why would it. the launcher can do it, but again - not all do. nova has even a bug that offsets the wallpapers which leaves a black gap. our launcher works, apex works, holo works and perhaps a bunch of others. no rom does it differently, simply because its impossible.
the real difference is that we are producing features that push androids boundaries, we are sick of a homogen rom culture that hasnt really moved one inch for a couple of years now. all these roms are the same, do you realize that? kanging has produced one grey mass and nothing stands out. when we are done with our beta we will of course bring in all the essential features aswell, but new features have greater priority. and these blow everthing related to it clean out of the water.
compare build.prop hacks with hybrid engine, its like night and day. this is quite possibly the biggest rom scene improvement android has ever had.
compare rom scene color tweaks with per-app-color, its like night and day. normal roms are static, they give you one color and thats that. our colors shift from app to app.
compare extended desktop (which also came from us) with per-app-fullscreen
compare our recents with clearall implementations,
we had the most versatile toggles on android in 4.1 (right now we're implementing a new panel which will come in beta6)
etc.
but you got to understand that this stuff takes alot of time. i know i could just rename an open source rom, call myself "founder," post in 30 device forums and make craploads of money here on xda, but i chose not to and im happy i found a few guys that think in the same way. im content with the few people that use PA and the support i get from those, i dont see myself competing with any other rom for that matter. i dont feel like i have to stop all my work now just because this and that rom has a minor option that we dont have at the moment.
molesarecoming said:
tabUI is not existant in 4.2, what you see right now is raw honeycomb. if you want to see how good it was install 2.54, thats still based on 4.1. but right now i got to make my hands dirty with this. i know that on xda most people do not understand the difference between developing and kanging, and they wonder "why's this rom slower than others" but someones gotta do the dirty work and im okay if crackflashers avoid ours. they avoid cm for the same reason.
as for hybrid engine, i dont think you have understood it yet. it works flawless and it gives you more customization than all roms on xda combined, IF you can handle it. yes, you are able to make a button pink in this and that rom, but hybrid can transform thousands of apps and components to the better, with practical implications that are unheard of. the apps that are running on your huge 720p screen were not optimized for it, they're in the same layout that applies to pocketwatches or stone age miniature phones like the htc wildfire.
as for opacity, no app, obviously, draws underneath the bars - why would it. the launcher can do it, but again - not all do. nova has even a bug that offsets the wallpapers which leaves a black gap. our launcher works, apex works, holo works and perhaps a bunch of others. no rom does it differently, simply because its impossible.
the real difference is that we are producing features that push androids boundaries, we are sick of a homogen rom culture that hasnt really moved one inch for a couple of years now. all these roms are the same, do you realize that? kanging has produced one grey mass and nothing stands out. when we are done with our beta we will of course bring in all the essential features aswell, but new features have greater priority. and these blow everthing related to it clean out of the water.
compare build.prop hacks with hybrid engine, its like night and day. this is quite possibly the biggest rom scene improvement android has ever had.
compare rom scene color tweaks with per-app-color, its like night and day. normal roms are static, they give you one color and thats that. our colors shift from app to app.
compare extended desktop (which also came from us) with per-app-fullscreen
compare our recents with clearall implementations,
we had the most versatile toggles on android in 4.1 (right now we're implementing a new panel which will come in beta6)
etc.
but you got to understand that this stuff takes alot of time. i know i could just rename an open source rom, call myself "founder," post in 30 device forums and make craploads of money here on xda, but i chose not to and im happy i found a few guys that think in the same way. im content with the few people that use PA and the support i get from those, i dont see myself competing with any other rom for that matter. i dont feel like i have to stop all my work now just because this and that rom has a minor option that we dont have at the moment.
Click to expand...
Click to collapse
Wonderfully said.
Sent from my Galaxy Nexus
PA 2.54 on epic 4g touch
I just flashed to this rom yesterday and really like it so far. I am interested in flashing to the newest 2.99 version. Where I can get the correct download for my phone, and do I need to update my recovery and if so, where do I get the link for that?
Thanks
btvolta said:
I just flashed to this rom yesterday and really like it so far. I am interested in flashing to the newest 2.99 version. Where I can get the correct download for my phone, and do I need to update my recovery and if so, where do I get the link for that?
Thanks
Click to expand...
Click to collapse
I think the new 4.2 based PA roms might only be available for the Nexus series phones and tablets currently since the developers have started over building it from the ground up using AOSP source instead of CyanogenMod. I am not certain if the code is out there for other devs to build on their particular devices yet though.