Related
So talking to my buddy about all the "junk" loaded on the Samsung, he kept raving about how his old Nexus One was just the way I would like it. I would like to have a "plain" version of Android 2.1 on my phone. I have a coworker friend that's a Linux guru that's willing to help. Here's my questions.
Can I take take the Samsung released source for the hardware drivers and compile it with a stock Android 2.1 platform? I'm not asking for step by step. More of a 10,000 foot how to. Is that possible?
Can you leave the CSC and Modem info the same and just install a PDA ROM with Odin? Or would you be overwriting all of that info on the phone?
Thanks and if this has been answered before, please fill free to say "search is your friend" and give me the links...
hallfleming said:
So talking to my buddy about all the "junk" loaded on the Samsung, he kept raving about how his old Nexus One was just the way I would like it. I would like to have a "plain" version of Android 2.1 on my phone. I have a coworker friend that's a Linux guru that's willing to help. Here's my questions.
Can I take take the Samsung released source for the hardware drivers and compile it with a stock Android 2.1 platform? I'm not asking for step by step. More of a 10,000 foot how to. Is that possible?
Can you leave the CSC and Modem info the same and just install a PDA ROM with Odin? Or would you be overwriting all of that info on the phone?
Thanks and if this has been answered before, please fill free to say "search is your friend" and give me the links...
Click to expand...
Click to collapse
I unfortunately haven't the answer but I'd like to add that I am curious about this too.
dalingrin said:
I unfortunately haven't the answer but I'd like to add that I am curious about this too.
Click to expand...
Click to collapse
I'll second this and ask that if you do figure it out, please share with the community.
I think that vanilla Roms are a little further away in the future. First step in the process right now would be for someone to be able to compile a kernel from the Samsung released source code that works. Unfortunately the current Captivate kernel source code, when compiled, causes issues (voices garbled, lag when waking up the phone) that are not present in the stock precompiled kernel. These bugs are apparently not present in the other versions of the source code. Once these initial bugs are ironed out, we can truly start down the path of having custom fixes, and the devs can start to focus on bigger challenges, like making the vanilla Eclair or Froyo Roms to start working with our kernel. Good thing about this phone is that there are going to be so many versions of it, that parallel development is happening on multiple platforms. This will likely produce independent breakthroughs that could be theoretically ported between the platforms, but unfortunately it also slows down the development of each platform due to the quirks that have to be overcome. I hope that, in the future, we get to a place where all the source codes are merged into master repository that has all the necessary improvements and the ability to overcome individual platform quirks, so that the development can proceed more rapidly.
hallfleming said:
So talking to my buddy about all the "junk" loaded on the Samsung, he kept raving about how his old Nexus One was just the way I would like it. I would like to have a "plain" version of Android 2.1 on my phone. I have a coworker friend that's a Linux guru that's willing to help. Here's my questions.
Can I take take the Samsung released source for the hardware drivers and compile it with a stock Android 2.1 platform? I'm not asking for step by step. More of a 10,000 foot how to. Is that possible?
Can you leave the CSC and Modem info the same and just install a PDA ROM with Odin? Or would you be overwriting all of that info on the phone?
Thanks and if this has been answered before, please fill free to say "search is your friend" and give me the links...
Click to expand...
Click to collapse
Check out this wiki from cyanogen:
http://wiki.cyanogenmod.com/index.php?title=Main_Page
On the bottom right you will see an advanced section that explains how to build from source code. (aosp)
Good luck!!! It's definitely not for me, not with kids and a full time job!
Good info. I haven't seen a post on people testing out the source code testing and their experience. Can you IM or point me to that?
Thanks!
rajendra82 said:
I think that vanilla Roms are a little further away in the future. First step in the process right now would be for someone to be able to compile a kernel from the Samsung released source code that works. Unfortunately the current Captivate kernel source code, when compiled, causes issues (voices garbled, lag when waking up the phone) that are not present in the stock precompiled kernel. These bugs are apparently not present in the other versions of the source code. Once these initial bugs are ironed out, we can truly start down the path of having custom fixes, and the devs can start to focus on bigger challenges, like making the vanilla Eclair or Froyo Roms to start working with our kernel. Good thing about this phone is that there are going to be so many versions of it, that parallel development is happening on multiple platforms. This will likely produce independent breakthroughs that could be theoretically ported between the platforms, but unfortunately it also slows down the development of each platform due to the quirks that have to be overcome. I hope that, in the future, we get to a place where all the source codes are merged into master repository that has all the necessary improvements and the ability to overcome individual platform quirks, so that the development can proceed more rapidly.
Click to expand...
Click to collapse
Also for clarification, when you bought a Nexus One straight from Google for AT&T, was it considered "Vanilla"? Is the build on that phone just like someone downloaded the source for 2.1 and compiled it with the hardware drivers and that's it? I'm wondering what all comes on a "basic" Andriod ROM straight from the source.
hallfleming said:
Also for clarification, when you bought a Nexus One straight from Google for AT&T, was it considered "Vanilla"? Is the build on that phone just like someone downloaded the source for 2.1 and compiled it with the hardware drivers and that's it? I'm wondering what all comes on a "basic" Andriod ROM straight from the source.
Click to expand...
Click to collapse
Nexus One is as Vanilla as it comes. Just straight up Android! I don't think there is anything added to stock 2.1 or 2.2 on the Nexus.
hallfleming said:
Good info. I haven't seen a post on people testing out the source code testing and their experience. Can you IM or point me to that?
Thanks!
Click to expand...
Click to collapse
Most of the kernel compiling struggles are documented here:
http://forum.xda-developers.com/showthread.php?t=740747
Mimocan himself has started some work on it here:
http://forum.xda-developers.com/showthread.php?t=747040
There are also people having success mixing Vibrant ROM on the Captivate with some GPS crash issues:
http://forum.xda-developers.com/showthread.php?t=746466
I am trying to follow those threads, and since I am not a developer, I can't personally contribute to the process. But it is interesting to me anyway.
I've seen these before. I thought they were just edited versions of ROM's sucked off a existing phone. Are these compiled from scratch?
rajendra82 said:
Most of the kernel compiling struggles are documented here:
http://forum.xda-developers.com/showthread.php?t=740747
Mimocan himself has started some work on it here:
http://forum.xda-developers.com/showthread.php?t=747040
There are also people having success mixing Vibrant ROM on the Captivate with some GPS crash issues:
http://forum.xda-developers.com/showthread.php?t=746466
I am trying to follow those threads, and since I am not a deveoper, I can't personally contribute to the process. But it is interesting to me anyway.
Click to expand...
Click to collapse
hallfleming said:
I've seen these before. I thought they were just edited versions of ROM's sucked off a existing phone. Are these compiled from scratch?
Click to expand...
Click to collapse
The first two are attempts to recompile the kernel to put in the ext3/ext4 mimocan fix. The third one I believe is a script for boot logo animation hack to achieve the same thing.
I forgot to mention one more thread:
http://forum.xda-developers.com/showthread.php?t=739823
So we've got the source code with drivers and know which ones to use from the T959 for fixing the voice issue. We've got the stock kernel. What's left to creat a plain jane captivate?
hallfleming said:
So we've got the source code with drivers and know which ones to use from the T959 for fixing the voice issue. We've got the stock kernel. What's left to creat a plain jane captivate?
Click to expand...
Click to collapse
I'm guessing not too much. There are somethings that would need to be edited such as handling the capacitive buttons. The i9000 roms handle buttons differently regardless of the kernel so, its apparently an OS level config.
I've been wanting to work on this but I've been neck deep in source code from work.
Here is a good how to: http://forum.xda-developers.com/showthread.php?t=704561
Thanks for the link. The US codes out there so we don't need i9000 port
Sent from my SAMSUNG-SGH-I897 using XDA App
hallfleming said:
Thanks for the link. The US codes out there so we don't need i9000 port
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
My point was that given the I9000 rom needs source level changes in order to work as expected(haptic feedback on certain buttons, etc) then running an AOSP build may require some source level changes as well. It may not be as simple as building and flashing.
I stumbled upon an article linking to a download to the Gingerbread "beta" for Evo and I'm wondering:
What would happen to my current roms if I actually flashed the update? (using CM 6 and Fresh 3.4.0.1)
Is there potential to completely brick the phone to the point I won't even be able to get into the recovery to get back to a functional rom?
Its not beta. More like a "dev only" or alpha. Its in the dev forum. It wont brick your phone but It could give you some headaches if your new at flashing roms.
Sent from my PC36100 using XDA App
it is very choppy on my phone, like 5fps choppy.
but text and web browsing worked, along with the market.
however couldn't check gmail, id click on the email and it'd open than go back to the menu right away
Is the flashing process any different than simply selecting the .zip file from clockwork, or do I need to name it update or PC36IMG?
or would it be similar to the headaches received from not wiping the data and cache to load CM 6.1 "stable"?
What exactly are you hoping to accomplish any way? The rom is purely in developmental stages right now and should in no way be used as your primary rom. It's literally going to suck. Performance is NOT there right now. Given the questions you're asking in this thread it's highly unlikely you're going to be loading this rom and helping to improve it by developing it further...
a 2.3 based rom for the Evo intended for the "end user" is likely not going to be ready for you until the source is released for 2.3.
I just saw this posted, not sure if it could be of any help to those that "were" working on the sdk port. I say were because the thread was just closed.
http://androidcommunity.com/unoffic...-droid-x-available-now-20101212/#entrycontent
jobryan26 said:
I just saw this posted, not sure if it could be of any help to those that "were" working on the sdk port. I say were because the thread was just closed.
http://androidcommunity.com/unoffic...-droid-x-available-now-20101212/#entrycontent
Click to expand...
Click to collapse
You are mistaken at what that rom is. It is a froyo rom for the Droid X with the gingerbread keyboard and theme.
The numbering convention for the Droid X firmwares just happen to be at 2.3.x right now which is probably confusing you. If you actually go the thread dedicated to that rom you will see: http://www.droidxforums.com/forum/d...x-1-3-0-droid-x-running-running-fast-can.html
deathsled said:
You are mistaken at what that rom is. It is a froyo rom for the Droid X with the gingerbread keyboard and theme.
The numbering convention for the Droid X firmwares just happen to be at 2.3.x right now which is probably confusing you. If you actually go the thread dedicated to that rom you will see: http://www.droidxforums.com/forum/d...x-1-3-0-droid-x-running-running-fast-can.html
Click to expand...
Click to collapse
What was/is mis-leading is they are calling it "unofficial Gingerbread port" when they should have called it a rom with a ported theme & keyboard. They never mentioned the version # so I wasn't looking at that. Thanks for the clarification. ... Android Central>
That is a very mis-leading title.
jobryan26 said:
What was/is mis-leading is they are calling it "unofficial Gingerbread port" when they should have called it a rom with a ported theme & keyboard. They never mentioned the version # so I wasn't looking at that. Thanks for the clarification. ... Android Central>
Click to expand...
Click to collapse
Well the ROM creator didn't do that, it was the genius who blogged about it lol
Hello,
I am coming from an iOS world (no bashing please) and I first tried yesterday to update my Nexus One (GingerBread) to Jelly Bean. Although many forums post and blogs are available. It is nothing like easy for someone new in this world. Many acronyms, shortcuts etc ..
I summarized my experience in this blog post: www dot stormacq dot com/?p=494 (sorry for the link but stupid forum policies forbid forum newbie to post links. Not easy to share experience and information !!)
This is NOT a step-by-step tutorial, but just some highlight, warning and soem ways to avoid common pitfalls.
I hope it will be useful to others.
Seb
Give me more details:
Are you trying to install a aosp from your personal kang?
Are you trying to update?
Are you trying to port?
Why dont using some beautiful ports from developers section?
sebsto127 said:
Hello,
I am coming from an iOS world (no bashing please) and I first tried yesterday to update my Nexus One (GingerBread) to Jelly Bean. Although many forums post and blogs are available. It is nothing like easy for someone new in this world. Many acronyms, shortcuts etc ..
I summarized my experience in this blog post: www dot stormacq dot com/?p=494 (sorry for the link but stupid forum policies forbid forum newbie to post links. Not easy to share experience and information !!)
This is NOT a step-by-step tutorial, but just some highlight, warning and soem ways to avoid common pitfalls.
I hope it will be useful to others.
Seb
Click to expand...
Click to collapse
Not bad for an Apple fan tried to flash a Jelly Bean ROM I read your blog. It's not stupid forum policies but it's a way to prevent spammers post links to other sites.
taodan said:
Not bad for an Apple fan tried to flash a Jelly Bean ROM I read your blog. It's not stupid forum policies but it's a way to prevent spammers post links to other sites.
Click to expand...
Click to collapse
Don't know if I understand :S
Just finished... Took me 6 hours!
I just did this, thinking that is wouldn't be so hard since I had unlocked and flashed CM 7.2 a while back. I feel like I definitely jumped into the deep end. I had never used fastboot usb or Blackrose and they were actually quite fun to learn to use, albeit frustrating. I think I had to reread like 5 different threads at least 10 times but I got there. 6 hours of solid learning!
I would love to see such a tutorial (I couldn't visit the link above, even after some 'dot'substitution/etc).
I am using CM7.2. I put CM on my N1 some months before, and just keep updating by installing new releases from CM. The nice thing is that I do not have to reinstall app/move data after each upgrade.
I would love to get step-by-step help on getting Jelly Bean (Evervolv rom), and wonder whether it'll be as "upgrade friendly" as CM afterwards.
Thanks!
i dint understand flashing the patch for hboot.. i did repartition using balckrose..
Nice blog post sebsto127. I did it slightly different in that I used OSX to manually install BlackRose.
Running the installer in OSX doesn't work as you've found (cant execute binary or something) so then I followed the instructions found in the BlackRose "manual" download..
All that did was screw my recovery partition and BlackRose couldn't install due to 'signature verify fail'.
After some searching through the BlackRose thread I found this (why it isn't in the OP I don't know): http://forum.xda-developers.com/showpost.php?p=29156664&postcount=1292
After reflashing 4EXT recovery all was good again.
---------- Post added at 12:25 PM ---------- Previous post was at 12:19 PM ----------
Drapsthomas said:
i dint understand flashing the patch for hboot.. i did repartition using balckrose..
Click to expand...
Click to collapse
Installing Blackrose allows you to repartition - Step #2 in the blog is to install the actual partition system for Jellybean
thanks!!
This might be somewhat off topic but I just want to mention that having tried both Evervolv's JB and Spazedog's, the Spazedog JB ROM has been much more stable for me and since it is based on CM, many of the CM customization options are there (Evervolv is closer to stock AOSP). You'll also want to overclock your processor to achieve optimum performance.
As for learning all this stuff, it seems to be a never ending process for me. I had unlocked rooted five devices since December but when I got my N1 a couple weeks ago...I was going crazy trying to learn about the particularities of this device (especially in regards to hboot & a2sd...neither of which are present/necessary on any other device I've tinkered with).
Sent from my Nexus One using Tapatalk 2
mtmjr90 said:
This might be somewhat off topic but I just want to mention that having tried both Evervolv's JB and Spazedog's, the Spazedog JB ROM has been much more stable for me and since it is based on CM, many of the CM customization options are there (Evervolv is closer to stock AOSP). You'll also want to overclock your processor to achieve optimum performance.
As for learning all this stuff, it seems to be a never ending process for me. I had unlocked rooted five devices since December but when I got my N1 a couple weeks ago...I was going crazy trying to learn about the particularities of this device (especially in regards to hboot & a2sd...neither of which are present/necessary on any other device I've tinkered with).
Sent from my Nexus One using Tapatalk 2
Click to expand...
Click to collapse
I ended up trying both Evervolv ICS and SpazeDog ICS. And find the latter smoother on my N1 (but I don't like the boot animation on SpazeDog )
I find the following helpful for ICS, and probably also what one need for JB.
http://forum.xda-developers.com/showthread.php?t=1804571
As mentioned in many places by the devs, the JB is not as mature and there are known issues like camera. That's probably why there is not a complete instruction, by purpose.
Last but not the least, thanks for all the great things this community brings!
Guys,
Naturally, as the title states, its a general discussion thread for huashan LBL users. I want to discuss some things with like-minded people and hopefully once the momentum builds, we can try to achieve something.
Android L official release is just around the corner and our official fate is sealed by Sony @ 4.3.
But i plan on trying to port L using existing 4.3 kernel and make it at least boot so we know later on its a possibility for Locked Bootloader to have Android L.
Unlocked Bootloader guys are advised to stay away, as sooner or later, they will get proper AOSP 5.0.
Some points i want to make important.
1. This is NOT a cheer thread. Dont just post to show your excitement. It blocks the purpose of healthy discussion.
2. This is not for people who want new android. Have some sense, it isnt going to come anytime soon.
3. This is strictly for Locked Bootloader guys. So any other person coming and commenting might just be wasting his time.
Although, if you really have some positive thing to contribute, than whatever you have, LBL or UBL, please do share with all.
This is a good starting place to study.
https://github.com/Android-L-Porting-Team/Android-L-Mako/commits/master?page=3
Lets begin !
Im not sure how much id be able to contribute but ill be willing to help any way I can do. Do we even have a vague idea of what kernel modules would be needed for L? Im assuming thats what we'd need as I remember Bagyusz saying thats what he had to do for KK.
Has any of the freexperia team looked at L yet to your knowledge? Perhaps they may be able to give some small insight into drivers etc for LBL/UBL.
Will PA still be updated while this is being looked at? I'm assuming PAC wont need anything now unless problems occur as its all automated. Until L is working PA is a good thing for those wanting L due to them implementing features from L in KK such as recents and tinted bars (if they ever release them to legacy!!).
Oblox said:
Im not sure how much id be able to contribute but ill be willing to help any way I can do. Do we even have a vague idea of what kernel modules would be needed for L? Im assuming thats what we'd need as I remember Bagyusz saying thats what he had to do for KK.
Has any of the freexperia team looked at L yet to your knowledge? Perhaps they may be able to give some small insight into drivers etc for LBL/UBL.
Will PA still be updated while this is being looked at? I'm assuming PAC wont need anything now unless problems occur as its all automated. Until L is working PA is a good thing for those wanting L due to them implementing features from L in KK such as recents and tinted bars (if they ever release them to legacy!!).
Click to expand...
Click to collapse
Dont worry so much. PA is at a stage that if u have linux, u can just compile it right away and all is on Auto.
I will release milestone builds... No point pushing weekly updates if there arent any major changes.
For PAC, i have even taken that burden off and compiling and uploading is not my headache now.
And apart from above, i dont use PA personally. PAC suits me best.
As you stated the main concern is how well "the sealed by Sony @ 4.3. bootloader" will be able to cope with android L?
I really appreciate your enthusiasm. And yes there is only one way to find out. And that is to actually try porting it.
mmfh said:
As you stated the main concern is how well "the sealed by Sony @ 4.3. bootloader" will be able to cope with android L?
I really appreciate your enthusiasm. And yes there is only one way to find out. And that is to actually try porting it.
Click to expand...
Click to collapse
Porting is not an issue. We need a team. Not a band, but maybe 3 people. One compiler, One to tinker with trees and files, One tester. Just my suggestion.
One person cannot do it alone, unless he is an expert dev.
And about coping with L, all current devices having L port are using 4.4 kernel. And our 4.3 copes with 4.4. Technically there are not much issues compatibility wise. Just ramdisk and correct blobs.
I may be wrong, but thats why this discussion is goign on, if someone wants to correct me, please do.
I think this is an interesting project, XDA needs ppl like U
you think is easy port L with 4.3 kernel? I mean I'm just talking w/o reference, but Sony is just (until now) ignoring ART which is the biggest change for L (since 4.4 but well, now is not optional), and I think that could be a barrier to port new android for older phones (like SP)... what do you think about?
I hope this thread came with great news in the near future, :good:
This can be either hard or easy, hell or heaven, depending on the changes in L official release. Up until now, the changes are lying in ramdisk, but some features aren't available in the beta release.
But here are a few things that I noticed right now, before the official release:
1. UBL and LBL are stuck with 4.3 blobs. We are already using patched libraries, I guess it will get worse later, even on UBL.
2. I think we should wait until the CM12(?) will be working on UBL, while helping with bringing it up. If it works on UBL, then we should tinker with the LBL version. Actually, we have the hijack part, and we have the patches needed. I think it will be easy to get it to boot.
3. I think when @delewer finishes his kexec modules, some people that are experienced with kernel development could port it to SP, and then we could use it on forever locked phones. It will take some time, but will be the best for our phones.
So overall, if we have some luck, we would only have to kang CM trees, add the patches for hwcomposer, etc., add hijack and maybe some kernel modules. But we can be extremely unlucky and... I don't even want to imagine the worst case scenario.
Dont worry, the ground work is there. bagyusz gave us a great gift. I am sure Final release wont have boot-related changes. Maybe framework and libs, but not more.
The best thing is, 4.3 SONY rom DID NOT support ART. Bagyusz made it work even on LBL. and as Android L only supports ART, so thats the most important point i think.
Hmm, is ART even kernel-dependent?
I think that's not the case, and it's just great for us. So, bagyusz did a great work(it's just amazing), but I don't think he made any change to support ART.
And yeah, maybe there are just changes in frameworks and libs, but I'm still paranoid about this.
Anyway, I think that we are going to make it. That's what I feel, and I hope it comes true
neXus PRIME said:
Porting is not an issue. We need a team. Not a band, but maybe 3 people. One compiler, One to tinker with trees and files, One tester. Just my suggestion.
One person cannot do it alone, unless he is an expert dev.
And about coping with L, all current devices having L port are using 4.4 kernel. And our 4.3 copes with 4.4. Technically there are not much issues compatibility wise. Just ramdisk and correct blobs.
I may be wrong, but thats why this discussion is goign on, if someone wants to correct me, please do.
Click to expand...
Click to collapse
As I'm far from developer, I'm afraid cannot be of big help to you.
But I'm willing to contribute by testing builds and discovering bugs.
MrSteve555 said:
Hmm, is ART even kernel-dependent?
I think that's not the case, and it's just great for us. So, bagyusz did a great work(it's just amazing), but I don't think he made any change to support ART.
And yeah, maybe there are just changes in frameworks and libs, but I'm still paranoid about this.
Anyway, I think that we are going to make it. That's what I feel, and I hope it comes true
Click to expand...
Click to collapse
Not kernel dependant, i know, but you know what, booting a new android version using old kernel with just hijack n scripts is one HELL of a job.
And ART even didnt work for a long time on AOSP CM for huashan on UBL.
My point was, what we have here is a 4.3 kernel and blobs which might or might not be enough for android L. But before official release, we can try to port L from mako, by replacing blobs and ramdisk and boot, so that we have at least a proof of concept that LBL CAN boot L. Just boot. Nothing else.
neXus PRIME said:
Not kernel dependant, i know, but you know what, booting a new android version using old kernel with just hijack n scripts is one HELL of a job.
And ART even didnt work for a long time on AOSP CM for huashan on UBL.
My point was, what we have here is a 4.3 kernel and blobs which might or might not be enough for android L. But before official release, we can try to port L from mako, by replacing blobs and ramdisk and boot, so that we have at least a proof of concept that LBL CAN boot L. Just boot. Nothing else.
Click to expand...
Click to collapse
"Just" hijack? Bagyusz gave us an excellent base(hijack), and I bet we can boot FFOS or Ubuntu on that.
I didn't even know that ART didn't work on huashan before. Wasn't it a Gapps problem?
And yeah, these maybe aren't enough, as we are already patching some libs.
Ans one thing - I don't think we could port that from mako. It uses a little different base, and it isn't a CAF base. I think we should just wait
MrSteve555 said:
"Just" hijack? Bagyusz gave us an excellent base(hijack), and I bet we can boot FFOS or Ubuntu on that.
I didn't even know that ART didn't work on huashan before. Wasn't it a Gapps problem?
And yeah, these maybe aren't enough, as we are already patching some libs.
Ans one thing - I don't think we could port that from mako. It uses a little different base, and it isn't a CAF base. I think we should just wait
Click to expand...
Click to collapse
Just hijack meant different in a positive sense. But maybe it came out wrong.
And I'm talking about porting. Framework. Not building from source. They are actually doing same thing. I'll have to give it some time though.
neXus PRIME said:
Just hijack meant different in a positive sense. But maybe it came out wrong.
And I'm talking about porting. Framework. Not building from source. They are actually doing same thing. I'll have to give it some time though.
Click to expand...
Click to collapse
Yes, I know what you are trying to say with porting L. Actually, there would be a few things that would break:
1. The YUV color palette support (fixable with our hwcomposer, gralloc etc)
2. GPU drivers - this is the "best" part. L is precompiled, and I think it uses the libRS override, which doesn't work on our huashan because of a kernel difference (if we could build from source, we could just not enable it). There are a few other things that aren't compatible. So even if we got it to boot, it would just show black screen, and I assume by "just booting" you mean actually seeing the effort
3. The whole "thing" is built off AOSP repos, not CAF ones. Idk if SP's stock kernel would play nicely with the whole different stuff.
These are just my assumptions, in the end everything could work just fine. If you have the sufficient time, it's nice to try. Just deleting the mako proprietary stuff, and adding the needed huashan blobs + adding correct ramdisk would get it to the bootable/half working state (or there is a chance that the "build" wouldn't even boot.). I guess it's not done yet for a reason.
Anyway, I have to squash one last bug in my CM builds. If it will work, I could also try porting the magical "L".
My friend owns an samsung galaxy tab 4 t-230 and would love to upgrade it into a more pure android. Since i kind of got into android ROMs and there are no AOSP or CM roms for the tab 4 t-230 this would be a great chance for me to build a AOSP or CM rom. I have ubuntu 14.10 and a decent enough pc with 16 gb of ram and an i7. If anyone could help me abit of how to build a AOSP or CM rom for the device i would be verry thankfull.
----------------------Edit-----------------------
I wanted to say thank to you guys! I did quite some progress by now. If you own a t230 / nu then feel free to check out my custom kernel
CTXz said:
My friend owns an samsung galaxy tab 4 t-230 and would love to upgrade it into a more pure android. Since i kind of got into android ROMs and there are no AOSP or CM roms for the tab 4 t-230 this would be a great chance for me to build a AOSP or CM rom. I have ubuntu 14.10 and a decent enough pc with 16 gb of ram and an i7. If anyone could help me abit of how to build a AOSP or CM rom for the device i would be verry thankfull.
Click to expand...
Click to collapse
Relevant post - some starting info, and check out the CM wiki he links to. Also, and this is a very basic step, but if you've never done this before it can be informative: download a rom zip file (preferably but not necessarily a stock-based kitkat rom for this device) and open it up in either 7zip or WinRar, check out the layout and structure, and familiarize yourself with the updater-script. (Actually you can do that with a firmware tar file too). Sorry I can't give you any more useful info, not a dev, definitely not a rom designer, just a guy who knows a fair amount of android stuff.
Also don't let the tone of that post discourage you; the poster was answering a guy who was basically asking about the feasibility of building a brand new rom for the sole purpose of being able to use one particular proprietary Samsung app. Yes it is difficult, but still doable, and you say you're motivated...
Yes i did forgot to say that any links for learning are appriciated
Well.. I would ask moonbutt74 for more info regarding commands and such, probably more info than I can give but.. keep in mind your going to have to download about 20+GB of source code and all that. Also a bunch more knowledge of more things I don't remember. But it is alot
-DUHA
Well I decided to revisit this thread. Never thought I would come so far. I really want to say thanks to all of you who supported me and still support me. Everyone has a beginning and here was mine. Now I am actually there where I really wanted to be. Releasing a custom kernel and finally work on a custom ROM! Thank you XDA!
CTXz said:
Well I decided to revisit this thread. Never thought I would come so far. I really want to say thanks to all of you who supported me and still support me. I mean everyone has a beginning and here was mine. Now I am actually there where I really wanted to be. Releasing a custom kernel and finally work on a custom ROM! Thank you XDA!
Click to expand...
Click to collapse
I'm amazed on how much people learn and achieve as well as myself. I've seen people who were total newbies then later built custom recoveries, CM12, Mods, Roms etc. Anyway good luck on working your rom!
Sent from my SM-T800 using Tapatalk
DUHAsianSKILLZ said:
I'm amazed on how much people learn and achieve as well as myself. I've seen people who were total newbies then later built custom recoveries, CM12, Mods, Roms etc. Anyway good luck on working your rom!
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
Also I thank you my life for introducing me to moonbutt74. He learned me everything from how to work with custom kernels to Roms. Sadly he decided to stop developing a few Werks ago but he's doing it for his own good. I still will mention @moonbutt74 on my future projects because he really is the one who changed me from confused to knowing what is actually going on. So thanks allot !
CTXz said:
Also I thank you my life for introducing me to moonbutt74. He leatned me everything from how to work with custom kernels to Roms. Sadly he decided to stop developing a few Werks ago but he's doing it for his own good. I still will mention @moonbutt74 on my future projects because je really is the one who changed me from confused to knowing what is actually going on. So thanks allot !
Click to expand...
Click to collapse
the erlkönig cant stop!