Would someone be willing to build android l from source for the sprint gnex? I am willing to test it but I don't have the resources or the space to build it myself. Also, I would like it to be stock without root as I don't need that for the time being and don't want to risk a brick of any kind.
From what I understand, even though some sources are up for the L preview, not everything is there which limits the usefulness of source builds at the moment.
There is an ongoing discussion of L porting in the general section and even though its for the Verizon gnex, just remove the very top line in the updater script of the zip over there to make it flash on toroplus.
http://forum.xda-developers.com/showthread.php?t=2796203
Everything almost works but our open gl drivers aren't up to snuff and that pretty much can't be worked around at this point. Also it won't boot into android even though its about 90% of the way there, but full source is needed to hack around it.
Sent from my Galaxy Nexus using XDA Free mobile app
Related
Ok so instead of five billion different ports of the CyanogenMod 5 for the GSM Hero, I have simply forked Darchstar's CDMA Hero port of CyanogenMod 5 on github.
It will be WAY more productive & efficient if all the developers work together instead of fragment the process of this port.
If anyone wants to be added as a collaborator, just PM your Github name.
Github: link
Re: [ROM-DEV] CyanogenMod 5 for the GSM Hero (Community Edition)
I think it is very good idea
-------------------------------------
Sent via the XDA Tapatalk App
bump..
tenchar
Free bump.
There needs to be some order around here. The amount of seeming "best" "fastest" Builds are a pain in the arse. Can people just not get their **** together? This forum is a proper mess.
Detol Loki said:
Free bump.
There needs to be some order around here. The amount of seeming "best" "fastest" Builds are a pain in the arse. Can people just not get their **** together? This forum is a proper mess.
Click to expand...
Click to collapse
I entirely agree.
you need to modify the AndroidBoard.mk to actually point to the hero libs and proprietary files to not get errors during compilation. and also, you may also want to use actual hero proprietary stuff in the vendor tree too.
also, rename the thread to "[Vendor Tree] Cyanogenmod for GSM Hero (Community Edition)"
darchstar said:
you need to modify the AndroidBoard.mk to actually point to the hero libs and proprietary files to not get errors during compilation. and also, you may also want to use actual hero proprietary stuff in the vendor tree too.
Click to expand...
Click to collapse
I don't know how to do any of this this. I have simply set this up to push the community into a direction of hopefully working together & get this working on the GSM Hero faster.
jaymac407 said:
I entirely agree.
Click to expand...
Click to collapse
As do I.. But then, I am still on an 1.5 rom, as I found them to be the fastest, least power-hungry.
The only thing I am missing is some Google Maps updates and some software I can not install as it requires 1.6+, but whenever I tried a 2.x rom, I found I only used it for a little while and then restored the nandroid backup of my trusty 1.5 setup, it's just fast and stable.
Sorry for this stupid quesiton, but how can i compile/sign/whatever it to run this on my hero?
I'm sure when the time comes there will be a release version. For now this is for the devs to work on.
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
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.
MIUIv5 will Jelly Bean, based on GeekyDroid's CyanogenMod 10.
Kitkat will be Source Compiling, and may not be fully functional.
let me Know, So I am working on a more beneficial project.
quakze said:
MIUIv5 will Jelly Bean, based on GeekyDroid's CyanogenMod 10.
Kitkat will be Source Compiling, and may not be fully functional.
let me Know, So I am working on a more beneficial project.
Click to expand...
Click to collapse
Can you see anything related to lollipop on github If you have synchronized resources ???
Sent from my XT1033 using XDA Free mobile app
sachoosaini said:
Can you see anything related to lollipop on github If you have synchronized resources ???
Sent from my XT1033 using XDA Free mobile app
Click to expand...
Click to collapse
Due to lack of responses for my present project, I have decided not do.
I also ask the moderator to close this thread
upon you
quakze said:
Due to lack of responses for my present project, I have decided not do.
I also ask the moderator to close this thread
Click to expand...
Click to collapse
well ohk
sachoosaini said:
well ohk
Click to expand...
Click to collapse
I Thought of doing Kitkat, tried with prebuild Kernel but compiler says its deprecated and discontinued.
So trying to compile Kernel with the Kitkat ROM.
To make it happen, Need some support from you guys !
Well i am not developer
quakze said:
I Thought of doing Kitkat, tried with prebuild Kernel but compiler says its deprecated and discontinued.
So trying to compile Kernel with the Kitkat ROM.
To make it happen, Need some support from you guys !
Click to expand...
Click to collapse
you see i don't own a linux ever. i use windows and my laotop is mostly always filled my own stuff. i need a decent RAM for building a machine for ROM And kernel development. so in that case i never able to succeed. IT require a certain amount of knowldge about programming which i don't know. so here everything stops. Well i tried to ask as much as developers in the past to make us a 3.0 kernel. but the issue is that our processor is way too slow and moreover it is single clock. The biggest thing that hampers the development is the non availability of GPU. After 2.3.7 google has introduced hardware acceleration. That was the last that was enough to kill our willy. Now as the code changes and and API changed with the more powerful phones. So at the end of the tunnel i also came to know that arm 6 processor does not support ART. So whati thought that someone will try to port the kitkat for our willy. But most of the devices that are getting the updates of kitkat are having GPU. I closed down my threats because of this. No one want to work on a device in which the power is way too less. so the main issue is not with kernel i saw HTC Explorer got KITKAT on 2.6 version of kernel though it is buggy but still they got it. Now hell it again has GPU. SO GPU is must for anything to happen after 2.3.7.. SASA's last attempt to built 4.2.2 is the last ray of hope for us. Because there the main developer of the arm 6 supported us for a while but then he vanishes. Well now just imagine for a wonder that somebody will post a KITKAT built. :good:
I just checked out the aospa Twitter page and they are devices that are running the new version of paranoid Android. I am wondering if there are no maintainers for this device as we do not get it built for our devices I believe that it can be built off of source but I know that there compilation methods are abid difficult. Anybody want to take a stab at it and build this wonderful run for our devices. @slothdabski @calsurferpunk @kingbri
I would sport that puppy...
i42o said:
I just checked out the aospa Twitter page and they are devices that are running the new version of paranoid Android. I am wondering if there are no maintainers for this device as we do not get it built for our devices I believe that it can be built off of source but I know that there compilation methods are abid difficult. Anybody want to take a stab at it and build this wonderful run for our devices. @[email protected]@kingbri
Click to expand...
Click to collapse
I read this on their gsi xda post
(NOT using A/B partitioning scheme (ie. A-Only)
Bummer
It's a device specific flag that can be set up to run on a/b devices... It's just a matter of someone picking up the project for our phones.. I do recall that back in the day the way to build it was different from other operating systems so maybe the setup was different and nobody here has that set up possibly? I'm trying to stay patient but I am currently running DU and is running phenomenally.. I do understand that paranoid Android is very barebone right now but the caf source makes it really good on battery low and stability. I recall way back and my Galaxy S2 days ... And this is just a great project. If anyone out there can build this for us you would be incredible
i42o said:
I just checked out the aospa Twitter page and they are devices that are running the new version of paranoid Android. I am wondering if there are no maintainers for this device as we do not get it built for our devices I believe that it can be built off of source but I know that there compilation methods are abid difficult. Anybody want to take a stab at it and build this wonderful run for our devices. @slothdabski @calsurferpunk @kingbri
Click to expand...
Click to collapse
Paranoid Android was very cool in 2013, I used it on my SGS4 back then on Android 4.3. They had this engine where you could set the phone to tablet, phablet or phone mode and change DPI. You could even do this on a per-App basis! Very nice :good:
On top they had a plethora of setting - oh and they had this psychedelic design! E.g. for OTA updates (IIRC) they showed this one: https://www.androidpolice.com/wp-content/uploads/2013/06/nexusae0_lennon.jpg
But now, in 2019, what is special about PA?
BabelHuber said:
Paranoid Android was very cool in 2013, I used it on my SGS4 back then on Android 4.3. They had this engine where you could set the phone to tablet, phablet or phone mode and change DPI. You could even do this on a per-App basis! Very nice :good:
On top they had a plethora of setting - oh and they had this psychedelic design! E.g. for OTA updates (IIRC) they showed this one: https://www.androidpolice.com/wp-content/uploads/2013/06/nexusae0_lennon.jpg
But now, in 2019, what is special about PA?
Click to expand...
Click to collapse
Nothing really, a lot of the stuff that they Incorporated back in the day or something that comes native on Android nowadays.. PA Theme engine is somewhat redundant especially how it lets you theme per app basis somewhat like substratum can do... I don't see Halo coming back, and it wasn't back in the Android 7 or 8 builds of paranoid Android... I will say one of the things that they have going for them would be the caf base.. as I mentioned before it is extremely fluid and great on battery life.. ever since @molesarecoming left the dev scene for this operating system, it honestly seemed to have died as far as what features where available on this... I guess now it's good for nostalgia and stability as far as features go I don't see what they can offer that we don't already get with other options... I can't say this though, the battery life has always been good on these ROMs