Related
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.
What would happen if I build android from source and flash it to my One X?
With the current release, it is possible to build for Nexus 7, for some variants of Galaxy Nexus, for a variant of the Motorola Xoom, and for all variants of Nexus S and Nexus S 4G. The exact level of functionality for each device depends on the availability of the relevant proprietary hardware-specific binaries.
Click to expand...
Click to collapse
- (source)
Will I brick my device? Did HTC basically just take the code and modify it to work on the One X? Any suggestions on how to proceed if I were to build my own ROM?
If you have no experience in this you are likely to f*** things up.
Just stick to aosp roms - same result.
Sent from my HTC One X
TToivanen said:
If you have no experience in this you are likely to f*** things up.
Just stick to aosp roms - same result.
Click to expand...
Click to collapse
Well that is no fun answer. I want to learn. I make apps for a living and want to advance and build my own ROM, because I want an all custom made one. I know I can go with CM and mod their code (or, can I?), but it would be more fun to actually do it from scratch. If it is possible, not build from AOSP at all. I know it sounds retarded but I believe the best way to learn is do as much as possible completely from scratch.
With that said, do you have any suggestion on where to start? Like mod the AOSP source code and get it running on the emulator?
You can branch cm10 and build that, it's a good place to start, you'll learn a lot.
After that, you may want to say, diff the AOSP kernel against a similar HTC kernel to see how many changes you'd be required to make to pure AOSP to get it to work with all the hardware specific bits.
Due to GPL, HTC are required to release the source modifications to the kernel and android (I assume), for any released binaries, but they can be a little slow. The JB stuff should be out soon, in theory. Hopefully that's enough to get everything working, but you will also need any binary drivers from nVidia etc.
It's a long road, and you'd do well to start with something working and work backwards towards AOSP.
I'm not sure what you mean by not even with AOSP, do you intend to create your own OS?
BenPope said:
You can branch cm10 and build that, it's a good place to start, you'll learn a lot.
After that, you may want to say, diff the AOSP kernel against a similar HTC kernel to see how many changes you'd be required to make to pure AOSP to get it to work with all the hardware specific bits.
Due to GPL, HTC are required to release the source modifications to the kernel and android (I assume), for any released binaries, but they can be a little slow. The JB stuff should be out soon, in theory. Hopefully that's enough to get everything working, but you will also need any binary drivers from nVidia etc.
It's a long road, and you'd do well to start with something working and work backwards towards AOSP.
I'm not sure what you mean by not even with AOSP, do you intend to create your own OS?
Click to expand...
Click to collapse
Thanks for the thorough information! If it is possible to create your own OS, then yes, it would be awesome. Actually my idea is to make a ROM similar to the Linux distribution Tiny Core Linux; only the most essential stuff are present and bloatware and other features are removed. It could maybe serve as a good starting point for other ROMs to build on that want a minimalistic base. However, that is very, very far into the future. Now I would just like to compile a ROM that I have developed. But as I said before, if possible, skip AOSP and build my own OS definitely! Is that even possible?
Of course its possible, Android wasn't invented by some higher being or alien lifeform.
Nobody would use it though, because there would be no apps.
BenPope said:
Of course its possible, Android wasn't invented by some higher being or alien lifeform.
Nobody would use it though, because there would be no apps.
Click to expand...
Click to collapse
I see, so I am locked to AOSP then? i better start with the CM branch, thanks a bunch.
I just wanted to start this thread for anyone who has information regarding the development of cyanogenmod 12 for the HTC One M9 and for a general discussion on Cyanogenmod 12 and 12.1
This is something I'd be incredibly interested in. I've got a gold S6 Edge preordered; in part because the M9 is uninspiring, partly because I'm not at at all a fan of Sense 7. Having cyanogenmod on this device might be a game changer for me.
Don't you think that when a dev has that information, they will post it themselves in the development forum, instead of searching Q&A for your thread?
Why you gotta go round throwing logic into the mix?
To be fair, I think there are a decent amount of people interested in this. Why not have a little playful banter in advance.
For I will most certainly jump on the vzw variant when we get the s-off treatment and reasonably stable cm12 builds
I'm working on CM builds for the M9 (developer version for now) so I'll keep you updated when I get it to boot.
Rashed97 said:
I'm working on CM builds for the M9 (developer version for now) so I'll keep you updated when I get it to boot.
Click to expand...
Click to collapse
Heroic. Best of luck. I am hurting for vzw s-off treatment for cm12 with a better camera than m8.
Thank you for your efforts.
Someone from AICP is also building... It builds fine just can't get it to boot yet
Rashed97 said:
I'm working on CM builds for the M9 (developer version for now) so I'll keep you updated when I get it to boot.
Click to expand...
Click to collapse
Hey dude, I want to buy this device, but I'm wondering how much "friendly" is HTC with the open source about the driver binary blobs? I saw the kernel sources from HTC, but I do not found the firmware/module blob. How are you doing this job? Are fully open source or are you using the same kernel version to re-use the current binaries?
Many thanks
WalterCool said:
Hey dude, I want to buy this device, but I'm wondering how much "friendly" is HTC with the open source about the driver binary blobs? I saw the kernel sources from HTC, but I do not found the firmware/module blob. How are you doing this job? Are fully open source or are you using the same kernel version to re-use the current binaries?
Many thanks
Click to expand...
Click to collapse
You can get these from the device itself.
Just thought I'd share, we have a booting system. Broken stuff: camera, NFC, WiFi, Audio, media. Working stuff: Bluetooth, RIL, sensors, touch, display
Rashed97 said:
Just thought I'd share, we have a booting system. Broken stuff: camera, NFC, WiFi, Audio, media. Working stuff: Bluetooth, RIL, sensors, touch, display
Click to expand...
Click to collapse
Rashed,
Thanks for your continuing work on this. Any updates to this thread are extremely nice. Obviously I can't really do much to help, but it's fun to see what you guys are working on.
Hope everything is going smoothly. I'm super excited to boot cm on yet another device.
Rashed97 said:
Just thought I'd share, we have a booting system. Broken stuff: camera, NFC, WiFi, Audio, media. Working stuff: Bluetooth, RIL, sensors, touch, display
Click to expand...
Click to collapse
this makes me happy in the pants. <3
Rashed97 said:
Just thought I'd share, we have a booting system. Broken stuff: camera, NFC, WiFi, Audio, media. Working stuff: Bluetooth, RIL, sensors, touch, display
Click to expand...
Click to collapse
I have to agree this makes me very happy:victory:
I've no doubt that this will happen, and there's probably a distinct possibility of dual boot too, I haven't heard anything as of yet but HTC usually does get good stuff, the M9 is a stellar device, not without it's faults but I wouldn't swap it, coming from an iPhone 6 and a Note 4 I wouldn't swap it back, I've also had the S6 and the S6 edge to use and they simply don't compare, nothing wrong with them that's just my opinion.
Watch the original development section for development of CM12 / 12.1, it will get done, hopefully pac and dirt unicorns will follow, they're the ones to watch for.
Got to say, running viper and Leedroid at the moment, absolutely superb roms, both of them.
Rashed97 said:
Just thought I'd share, we have a booting system. Broken stuff: camera, NFC, WiFi, Audio, media. Working stuff: Bluetooth, RIL, sensors, touch, display
Click to expand...
Click to collapse
hey rashed97 how's it going, very much looking forward to having something none sense to try out on my m9.
Like @Rashed97 I'm working on a build as well. Right now I'm just trying to figure out how to get all of the proprietary stuff I need out of the sense kernel source and shoehorn it into AOSP kernel source. That's the biggest step to getting it to boot.
In past devices that didn't get a Google Play Edition, and therefore only had sense kernel source released, there had to be a way to do this... So I'm taking a trip through history of popular handsets where someone managed to port the vanilla kernel source to the phone with sense.
Barring that, I'll just strip all of sense out of a stock rom, replace the status bar icons and other assets with stock LP, and slap nova launcher on it and make a lightweight senseless rom. I'd really prefer getting a CM build on this thing though so I'm going to keep plugging away at that until either I get it to work, or someone else does and I can add my work into their release.
agentfusion said:
Like @Rashed97 I'm working on a build as well. Right now I'm just trying to figure out how to get all of the proprietary stuff I need out of the sense kernel source and shoehorn it into AOSP kernel source. That's the biggest step to getting it to boot.
In past devices that didn't get a Google Play Edition, and therefore only had sense kernel source released, there had to be a way to do this... So I'm taking a trip through history of popular handsets where someone managed to port the vanilla kernel source to the phone with sense.
Barring that, I'll just strip all of sense out of a stock rom, replace the status bar icons and other assets with stock LP, and slap nova launcher on it and make a lightweight senseless rom. I'd really prefer getting a CM build on this thing though so I'm going to keep plugging away at that until either I get it to work, or someone else does and I can add my work into their release.
Click to expand...
Click to collapse
Sounds great. Had GPE running like a dream on my M8, so it almost seemed to me like a step backwards, moving to M9 with Sense. AOSP on M8 didn't have the sound drivers, so audio quality was an issue and a deal-breaker.
Thanks for the update. I've been chomping at the bit waiting for an aosp.
agentfusion said:
Like @Rashed97 I'm working on a build as well. Right now I'm just trying to figure out how to get all of the proprietary stuff I need out of the sense kernel source and shoehorn it into AOSP kernel source. That's the biggest step to getting it to boot.
In past devices that didn't get a Google Play Edition, and therefore only had sense kernel source released, there had to be a way to do this... So I'm taking a trip through history of popular handsets where someone managed to port the vanilla kernel source to the phone with sense.
Barring that, I'll just strip all of sense out of a stock rom, replace the status bar icons and other assets with stock LP, and slap nova launcher on it and make a lightweight senseless rom. I'd really prefer getting a CM build on this thing though so I'm going to keep plugging away at that until either I get it to work, or someone else does and I can add my work into their release.
Click to expand...
Click to collapse
There's eragon rom which is de-sensed running everything you just mentioned with the htc sense camera included and few other apks. Its dead quick and dev has been around since hox days making roms like that
I have since moved on to the Nexus 6, but came across this on my Google Plus feed. I haven't tested personally, but another user said it works on Maguro. Might work on Toro since it states "Tuna" in the name. Definitely recommend backing up before trying.
https://www.androidfilehost.com/?fid=24459283995314894
For those not familiar with Dirty Unicorns, they make a great custom firmware. Their team has some great Android veterans like Big Rushdog from the Omni and EOS days of the Xoom and Alex Cruz(Mazda).
Homepage: http://dirtyunicorns.com/
Google Plus: https://plus.google.com/communities/109738128866939227235
Interesting. How did you find this?
I'll give this a shot on toro to see if it flashes.
EDIT: Working on a toro that calls itself a "tuna". I have yet to test with a true toro recovery.
I came across this yesterday too whist looking for alternatives.
There is a Custom ROM section of the Galaxy Nexus owners feed on Google Plus and it was posted there.
https://plus.google.com/communities...3/stream/90071095-ed9d-4388-942b-41d09398482e
opticyclic said:
I came across this yesterday too whist looking for alternatives.
There is a Custom ROM section of the Galaxy Nexus owners feed on Google Plus and it was posted there.
https://plus.google.com/communities...3/stream/90071095-ed9d-4388-942b-41d09398482e
Click to expand...
Click to collapse
Yep, honestly speaking, it is looking like Google+ is the place to be for firmware info, questions, and releases. At least for newer phones. I have been on the Nexus 6 for a few months now and I visit the ROMS and Devs Google+ pages just as much as their XDA threads.
Hell, just yesterday I saw a build of Pure Nexus for Tuna posted.
And an FYI for others visiting this thread, If you click the link in the OP, that Dev has released newer versions of it which are listed out on the side. He seems to be updating it pretty well.
I think the dev is @voidz777
DU is just want I want in a ROM, it has SuperSU bundled, dev options already on, loads of tweak options and several features from other roms like the choice of Slim recents or OmniSwitch.
Unfortunately, I just noticed I'm not getting any mobile data, which is a bit of a bummer!
Someone did call me? lol
I have three of unofficial projects for lovable maguro .
Operation verification has been in maguro.
probably, I think work with other tuna variants
Look here.
https://www.androidfilehost.com/?w=files&flid=34398
https://www.androidfilehost.com/?w=files&flid=50101
https://www.androidfilehost.com/?w=files&flid=47838
christianpeso said:
Yep, honestly speaking, it is looking like Google+ is the place to be for firmware info, questions, and releases. At least for newer phones. I have been on the Nexus 6 for a few months now and I visit the ROMS and Devs Google+ pages just as much as their XDA threads.
Hell, just yesterday I saw a build of Pure Nexus for Tuna posted.
And an FYI for others visiting this thread, If you click the link in the OP, that Dev has released newer versions of it which are listed out on the side. He seems to be updating it pretty well.
Click to expand...
Click to collapse
1st thanks a ton to @christianpeso for coming by to post and let us know about this . :good:
opticyclic said:
I think the dev is @voidz777
Unfortunately, I just noticed I'm not getting any mobile data, which is a bit of a bummer!
Click to expand...
Click to collapse
2nd Thanks a ton to @opticyclic for tagging the creator @voidz777 which brought him here to post :good:
voidz777 said:
Someone did call me? lol
I have three of unofficial projects for lovable maguro .
Operation verification has been in maguro.
probably, I think work with other tuna variants
Look here.
Click to expand...
Click to collapse
and abc 1st+ 1st+ 1st+ to @voidz777 for building and posting these links .
I've just installed the purenexus with open gapps nano package and have everything restored and I just have to say
this is the fastest and smoothest my device has ever ran . It's up and going flawlessly on my Toroplus , data and telephony work like a champ . I absolutely love the layout and the hamburger menu in settings . I would like to follow you on google+ @voidz777 . I'm a good logger and can get you on a logcat if you ever need me to . I will check everything like gps , etc but so far it's perfect . Do you have a g+ page where I can find you and whatever projects and builds you have going ? I can't thank you enough for this awesome rom !!!!!:good::good: .
For anyone reading if you have a toroplus I can confirm it runs great , fast , smooth and data works . I think this rom runs so well because this is a nexus as we all know and finally we have a rom thats practically native for it .
voidz777 do you have unnoficial xda thread hidden somewhere here ? just wondering if I'm missing it somehow .
DU ROM
Tks for the AWESOME ROM...it's fast and buttery smooth...dl speeds are excellent...can't wait to try Pure Nexus ROM...BIG tks to voidz777...
voidz777 said:
Someone did call me? lol
I have three of unofficial projects for lovable maguro .
Operation verification has been in maguro.
probably, I think work with other tuna variants
Look here.
https://www.androidfilehost.com/?w=files&flid=34398
https://www.androidfilehost.com/?w=files&flid=50101
https://www.androidfilehost.com/?w=files&flid=47838
Click to expand...
Click to collapse
Thank you for your ROMs. I have a quetion, do your ROM support F2FS?
quantan said:
Thank you for your ROMs. I have a quetion, do your ROM support F2FS?
Click to expand...
Click to collapse
I'm not sure because it is not like the f2fs.
But, I think that it probably works.
voidz777 said:
I'm not sure because it is not like the f2fs.
But, I think that it probably works.
Click to expand...
Click to collapse
I just try format f2fs for /cache and /data. After installing your ROM, /cache returns back to ext4. But I think it doesn't matter. The ROM is smooth regardless f2fs.
Can't get my f2fs /data and /cache toro to install any of these. They are, of course, not built for toro, so I have no complaint at all. I was just curious to see if I could install them.
I'm a bit confused. What exactly is dirty unicorn(could not find a FHQ only blog posts from current status and that they moved to asop)..
And how much ram does it have? The rom i'm using now has 0,93GB ram.
Always got 'pea pea' sound
Sent from my Galaxy Nexus using XDA Premium HD app
SAOSP 7.0 and Pure Nexus 7.0 is also there uploaded by @voidz777 ....!!
Why he is not posting or informing anyone on XDA....!!
I'm sorry, I do not post on xda because English is poor. lol
If English is the poor, it also because it is difficult to manage the thread.
When I was upload, I have announced in my G +.
https://plus.google.com/+HatayamaYuuji
Sent from my Nexus 5
@voidz777 i just noticed DU 7.0....!! Greatest work by you..... Thank You.....
And if possible please share them here.... Everyone deserve that great work.... ?
DU for Tuna (7.1.1) Under the 'Scope
rm571 said:
Tks for the AWESOME ROM...it's fast and buttery smooth...dl speeds are excellent...can't wait to try Pure Nexus ROM...BIG tks to voidz777...
Click to expand...
Click to collapse
I grabbed DU for Tuna to put under the gun (replace/upgrade from Unlegacy 7.1.0 - the only other N-based firmware I am aware of for either maguro OR toro, let alone any variant of tuna).
First boot - YOW! The boot animation is B-R-I-G-H-T - brighter (and longer) than that for OmniROM. (Contrast that with Unlegacy - which has NO first-boot animation whatever.) Unless it develops a case of stiction, I won't count that against it (that was, in fact, my sole ding against Omni 6 - the animation DID develop "stiction").
Now I'm through the animation, and in the second part of startup ("Android is starting") - the icons are crisp; in fact, so is the background (courtesy of Tapet, which I had installed prior). The very reason WHY I installed Tapet is because I love the Material Design backgrounds (which are not unique to Android, though they started there; I've seen them in Linux distributions - notably Ubuntu-based Linux distros, in addition to Android). From what I am seeing, Tapet+DU = win (just for the clarity of the icons and display). Another surprise is that it actually IS using more mobile data than Unlegacy - a bit of a surprise there, especially with my router literally at my right elbow. (Does DU prefer mobile data over wi-fi for some reason? I'm merely asking as that can be a problem where mobile data is NOT AYCE - and it isn't for me; I'd prefer to use wi-fi compared to mobile data - for cost reasons.)
Okay - I got it running; however, I could not install it clean, as it kept taking out the AOSP Keyboard part of GApps. Amusingly, a pour-over AOSP 7.1 worked wonders; I only needed to re-root it. Everything works, and I've had a ball with the tweaks (little stuff, like the carrier-notification area - mine actually now says Tracfone - my MVNO; MVNOs don't advertise), smaller fonts, etc. Pixel Launcher works from the get-go (with the GN Launcher as its backup), and I've added Substratum for themery (and the ONLY reason I added it is because it also supports Pixel Launcher along with most third-party launchers). Yes - I do believe PL's gonna grow on me. (Actually, the PL/PN tag-team reminds me a LOT of the early days of (don't laugh!) Stardock's Object Desktop for Windows - and the two play off each other quite a bit.)
I wonder what the difference is between the Dirty Unicorn mentioned here and PureNexus which I came across on another thread and have installed OK with Pico Gapps (purenexus_tuna-7.1.1-20170107-HOMEMADE.zip) and where that ROM can lead or is it a semi-dead end?
Regardless, the Galaxy Nexus performance improved considerably over CM 13, no doubt owing to approximately 80MB more free system, so it's fun to use again
Cintra2 said:
I wonder what the difference is between the Dirty Unicorn mentioned here and PureNexus which I came across on another thread and have installed OK with Pico Gapps (purenexus_tuna-7.1.1-20170107-HOMEMADE.zip) and where that ROM can lead or is it a semi-dead end?
Regardless, the Galaxy Nexus performance improved considerably over CM 13, no doubt owing to approximately 80MB more free system, so it's fun to use again
Click to expand...
Click to collapse
The two ROMs don't differ much (understandably, since they have developers in common); in fact, this PN variant is DU-based - in terms of their N sorts, it's primarily that PureNexus includes PixelLauncher and some extra customization features that DU lacks. Both are lighter than CM13 - which shocked the heck outta me, since CM13 is based on MM, while both DU and PN are not only N-based, but 7.1.1-based in their latest iterations - isn't MM supposed to be lighter than N? (Because PN is based on DU, eventually (though not simultaneously) PN for tuna gets the updates DU does - the latest DU for Tuna includes the March updates, which the current PN for Tuna hasn't gotten yet. Unfortunately, it looks like PL is getting the boot from PN (despite my not having an issue using it) - is there an alternative way of putting it back?