Related
PUREGANDROID
About
PUREGANDROID ( Pure Google Android) is a pure android os as google intended.
It uses a CM7 base but most if not all CM7 is removed. This is my first rom and I could not remove all CM7 but I will remove more in the Future (cyanogenmod in setting ( Please I need some help on this) and the RenderFX widget( can't locate it)
UPDATE:
I have posted a beta to see if you guys like it it was built from CM and AOSP sources. I just have to compile kernel and change lockscreen.
NEW WEBSITE
macaddict.tk
DOWNLOAD
http://dl.dropbox.com/u/27168952/DOWNLOADS/PURG3.oBETA.zip
HOW TO FLASH
*USE CWR
1. wipe all user data
2. wipe cache
3. install from SDCARD
4. Select rom
5 reboot
About:
Uses Google stock launcher
Includes all google apps
Has North America GPS FIX
Uses a CM7 Kernel (for it to be stable)
Wants in Future
Ablsolutly no CM7
pure google
overclock to 1.5 or 1.8
Changes in 2.2
New aosp settings menu and more cygen removed
Lockscreen still needs editing
NOTICE
I TAKE NO RESPONSIBILITY FOR LOSS OF DATA OR AND DAMAGES.
I'm confused.
How can it be based on CM7 yet have all the CM7 removed ?
Sent using XDA Premium running MIUI version in OP
symonc said:
I'm confused.
How can it be based on CM7 yet have all the CM7 removed ?
Sent using XDA Premium running MIUI version in OP
Click to expand...
Click to collapse
I was thinking the same thing.
OP You should start with aosp source and fix that if you want as pure as google android as you can get.
By the way you your picture you have up there is not stock launcher it's adw launcher. And the rotary lock screen is not stock either. Sorry.
Sent from my Incredible using Tapatalk
I have the stock launcher installed in this version that screenshot is old. The Google lockscreen is included but not set as default ( trying to learn how to do this). I have remove Most of the CM stuff except for somethings i need to learn ( edit settings.apk to remove The CM settings ( which will not open when clicked on). All the apps on this rom come from a aosp rom for the DroidX( except for Terminal, Rom Manager, and File Explorer (which is very useful). All traces that i can remove so far have been removed.
haha dicks, just rippin him apart and the rom hasnt even been out for a day LOL
I applaud the effort. Congrats on your first rom and look forward to see the improvement. As far as removing apps, one thing I do is find it in Titanium then see what the file is named, then you can remove it out of the app folder.
Like stated above, you should work with a pure aosp base and you won't have to worry about any of that CM7 stuff. In my opinion, I think aosp is about as smooth as it gets when it comes to UI. I'm sure people would love to have a pure aosp ROM around here since there aren't any yet that I'm aware of.
Good luck with everything and if you need any help just ask.
I'll give a shot. I love loading new roms. Thanks and good luck.
The problem is that I remove CMparts.apk and cyanogenMod settings is still in my settings menu (like a ghost menu ( it won't open). I need someway to edit setting.apk to remove this from the settings menu but im not skilled enough to do this any help would be apreciated.
Also The RenderFX widget is unable to be found (If someone has a location or what file it is in please tell me)
tell me how it is please!!!!!
OP There is a lot more to removing cm then you are thinking. Cm is not just the addition off apps but also modification of all what is android. If you want aosp start with aosp
Sent from my Incredible using Tapatalk
Ok I tried it and honestly it looks just like cm7. I don't know about creating roms but it seems that this is cm7 renamed and the boot screen changed. I would seek advice on properly creating roms and start over. Good luck.
cpbeats said:
Ok I tried it and honestly it looks just like cm7. I don't know about creating roms but it seems that this is cm7 renamed and the boot screen changed. I would seek advice on properly creating roms and start over. Good luck.
Click to expand...
Click to collapse
It's because it is. I will gladly offer my help to the OP. Hit me up if you like OP @linuxmotion or pm.
Sent from my Incredible using Tapatalk
If I were to create this from a aosp rom I first need to get my hand on one. I need to get drivers (I have no Idea on how to do drivers). And what kernel would I use. also what drivers would i need and don't need (screen, mix, speaker, touchscreen, bluetooth,wifi?)
Also would you want to make this rom with me?
nerdkiller14 said:
If I were to create this from a aosp rom I first need to get my hand on one. I need to get drivers (I have no Idea on how to do drivers). And what kernel would I use. also what drivers would i need and don't need (screen, mix, speaker, touchscreen, bluetooth,wifi?)
Also would you want to make this rom with me?
Click to expand...
Click to collapse
You might want to check with @DOAlaboratories. He was working on an AOSP ROM, but hasn't updated his thread in a while.
http://forum.xda-developers.com/showthread.php?t=999988
nerdkiller14 said:
If I were to create this from a aosp rom I first need to get my hand on one. I need to get drivers (I have no Idea on how to do drivers). And what kernel would I use. also what drivers would i need and don't need (screen, mix, speaker, touchscreen, bluetooth,wifi?)
Also would you want to make this rom with me?
Click to expand...
Click to collapse
Building from source ie. google. You can google ginger bread aosp and it will bring up this or from Git. You are going to have to build a kernel from source as well. You take the drivers that inspire already has. Its alot of trial and error to see what works and what doesn't.
Is there anywhere that has all the information necessary to build a rom compiled into one handy area?
Sent from my HTC Desire HD using XDA App
Google is your friend if you want to learn how to compile asop. You can check out the android source site http://source.android.com/ or the developer sitehttp://developer.android.com/
Sent from my Incredible using Tapatalk
I have found a outdated 2.3.1 Asop rom for Desire HD (camera not working and USB mass storage not working ). Also If any one has any idea of how to copy CM7's drivers for USB and CAMERA I would love to hear from you!!!
Also How can I update this rom to 2.3.3 without having to recompile from ANDROID-SDK
I'm gonna take a crack at building from AOSP tonight. Gonna use the kernel and proprietary files from CM7. If it doesn't boot though, I don't have the patience to start looking into the kernel and framework to fix it. Wish me luck!
Alot of people have been asking me how i ported Slim ICS, soooo...i made a tutorial on how i port AOSP ICS roms...this is a general tutorial that should be just enough to get the port to boot. your port will not be flawless and it will probably have some major bugs that need fixing which are usually fixed by libs.
This should work with all AOSP ICS roms except those formated in a MTD file system (MTD is not supported by the infuse)...but for best compatibilty use a similar phone like the galaxy s...also before porting if you plan on uploading it you must get permission first!!! Dont make the same mistake i made with slim...
http://www.youtube.com/watch?v=loFHhYf0ca4
Guide:
***DISCLAIMER***
i am not responsible to any damdge caused to your phone by following this tutorial, you are doing this at your own risk. Before beginning you can not be afraid to mess with system file, to experiment, to get boot loops or even completely destroy your phone-for the infuse this is highly unlikely
if you fear bootloops or bricking a phone than you should not follow this tutorial
this guide should work for all phones and all AOSP roms, however every rom is different so some may require extra steps which you will be on your own for...this should be enough to get you to boot up though.
***END OF DISCLAIMER***
if you have any questions please feel free to comment bellow, dont message me on youtube i probably wont answer...if you do comment i may or may not help you, but maybe somebody else will. i have a busy life, and am constantly busy with the infuse and can not spend the time to address everyones issues...but by commenting maybe some one will help.
TOOLS/PROGRAMS NEEDED:
1) 7zip or other archive program
2) text editor, for windows i would use notepad++
STEPS:
1) download CM9 for your device or other AOSP based ics rom ***This is your base rom, you will use this to replace files in the rom you want to port***
What ever firmware your base is is the firmware you will be able to port...EX: 4.0.4 base=4.0.4 port
***for this tut i will be using CM9 4.0.4 for the infuse found here: http://forum.xda-developers.com/showthread.php?t=1601844 ***
2) download rom you want ported ***it can be from any phone, but for best compatibilty/least amount of bugs use a rom from a similar device, since i have an infuse i will use a Galaxy S ICS rom"
3) open up the CM9 or whatever base rom you are using with 7zip (dont extract it just view the archive...for 7zip right click rom, go to 7zip option and choose view archive)
4) delete the following folders in the system folder: app, framework, media, and fonts
5) open up the rom you want to port and use the app, framework, media, and fonts folder to replace the ones you just deleted in the cm9 base
6) copy libandroid_runtime.so *located in /system/lib/* from the rom you want to port into the cm9 base (you are replacing the one already in there) keep a copy of the one in CM9...if it doesnt boot up put the CM9 one back in
OPTIONAL/NOT NEEDED to make the rom run
a) go to build.prop and change the name of the rom
b) change the name of the CM9 base zip to whatever you are porting
7) place the rom on your sd card and flash...if you get bootloops do a logcat
If your rom is unresponsive/not working right you may need to replace some stuff in the /system/lib/ with stuff from the rom you are porting (just compare the rom you are porting with cm9 and whenever you see something missing in the CM9 base or dif size switch it over BUT keep a backup of the unresponsive one that booted...this part is all trial and error) i can not help you with this part...you are on your own, but feel free to comment and i may try and help or someone else may try and help
Also logcats will help in diagnosing problems...
please dont pm me for help, comment on this thread and if i have time i will try and help...or someone else will. im really busy, im a junior in highschool, so i have homework monday-friday, not to mention that my 92 year old great aunt is moving in with us as she can no longer take care of her self alone so i will be busy taken her to appointments and what not.
If i could i would help each and every one of you guys...but i just dont have the time to help everyone so if we can restrict the questions and answers to here hopefully we can limit the amount of questions asked.
Saved for Q&As...
just in case...
Thank you very much MG for your hardwork and dedication. This guide will actually help and inspire many of us to bring ICS flavours on Infuse. :thumbup:
Only a HS junior? My god what was I doing when I was your age? Definitely not porting Android roms.
Sent from my Samsung Infuse running AOKP.
i was bumping school to join computer class
ndhanta said:
i was bumping school to join computer class
Click to expand...
Click to collapse
Hmm I believe we were smoking cigs and talking about girls. But then in those days we didn't have computers or cell phones
Rom Aeon v 1.3.1
oldbbman said:
Hmm I believe we were smoking cigs and talking about girls. But then in those days we didn't have computers or cell phones
Rom Aeon v 1.3.1
Click to expand...
Click to collapse
Although oldbbman is more seasoned than me...I do remember those days...now I jjust dip Copenhagen and still talk about the girls...MILFs....
bigjoe2675 said:
Although oldbbman is more seasoned than me...I do remember those days...now I jjust dip Copenhagen and still talk about the girls...MILFs....
Click to expand...
Click to collapse
Lol
Luckily I didn't know then what I know now or I would probably have more kids then I have now.
Now back on topic. Porting ics Tom's is getting bigger on this forum
:thumbup::thumbup::thumbup:
Rom Aeon v 1.3.1
Believe me...for a while I wasn't making the smartest choices...wasn't hanging around the right crowd and was leading my life down the wrong path...doing these ports and developing has helped me turn my life around and make better choices, I love the challange and I lobe figuring things out...always have
Sent from my SGH-I997 using XDA
Btw...you guys should see a new port by me tomorrow...maybe even tonight, and I have received permission this time...
Sent from my SGH-I997 using XDA
ndhanta said:
Thank you very much MG for your hardwork and dedication. This guide will actually help and inspire many of us to bring ICS flavours on Infuse. :thumbup:
Here are steps for port which are with the Youtube video of MG2195. (It also deserves to be here).
TOOLS/PROGRAMS NEEDED:
1) 7zip or other archive program
2) text editor, for windows i would use notepad++
STEPS:
1) download CM9 for your device or other AOSP based ics rom ***This is your base rom, you will use this to replace files in the rom you want to port***
What ever firmware your base is is the firmware you will be able to port...EX: 4.0.4 base=4.0.4 port
***for this tut i will be using CM9 4.0.4 for the infuse found here: http://forum.xda-developers.com/showthread.php?t=1601844 ***
2) download rom you want ported ***it can be from any phone, but for best compatibilty/least amount of bugs use a rom from a similar device, since i have an infuse i will use a Galaxy S ICS rom"
3) open up the CM9 or whatever base rom you are using with 7zip (dont extract it just view the archive...for 7zip right click rom, go to 7zip option and choose view archive)
4) delete the following folders in the system folder: app, framework, media, and fonts
5) open up the rom you want to port and use the app, framework, media, and fonts folder to replace the ones you just deleted in the cm9 base
6) copy libandroid_runtime.so *located in /system/lib/* from the rom you want to port into the cm9 base (you are replacing the one already in there) keep a copy of the one in CM9...if it doesnt boot up put the CM9 one back in
OPTIONAL/NOT NEEDED to make the rom run
a) go to build.prop and change the name of the rom
b) change the name of the CM9 base zip to whatever you are porting
7) place the rom on your sd card and flash...if you get bootloops do a logcat.
If your rom is unresponsive/not working right you may need to replace some stuff in the /system/lib/ with stuff from the rom you are porting (just compare the rom you are porting with cm9 and whenever you see something missing in the CM9 base or dif size switch it over BUT keep a backup of the unresponsive one that booted...this part is all trial and error) i can not help you with this part...you are on your own, but feel free to comment and i may try and help or someone else may try and help
Also logcats will help in diagnosing problems.
Click to expand...
Click to collapse
Your right should be here...I'll add to the op
Sent from my SGH-I997 using XDA
mg2195 said:
Btw...you guys should see a new port by me tomorrow...maybe even tonight, and I have received permission this time...
Sent from my SGH-I997 using XDA
Click to expand...
Click to collapse
Now we can see more and more Android 4.x.x. in the Development section.
Nice work. Thanks for sharing with the community.
Sent from my SGH-I997 using xda premium
mg2195 said:
Alot of people have been asking me how i ported Slim ICS, soooo...i made a tutorial on how i port AOSP ICS roms...this is a general tutorial that should be just enough to get the port to boot. your port will not be flawless and it will probably have some major bugs that need fixing which are usually fixed by libs.
im a junior in highschool, so i have homework monday-friday.
Click to expand...
Click to collapse
Good job..thanks for sharing.
Now I can't say I never learned anything about tech from a high schooler..
Um that is a wise statement
Hey mg. I have your v1.0 slim ics and the ns tools fix. How would i combine them? Thanks in advance
I was going through the files and if I just put the apk in the system/app it would be alright?
isaiahe97 said:
Hey mg. I have your v1.0 slim ics and the ns tools fix. How would i combine them? Thanks in advance
I was going through the files and if I just put the apk in the system/app it would be alright?
Click to expand...
Click to collapse
yep, that would fix it
you may want to warn those about the mtd partition system while porting since i ve ran into several of them
GoSooners345 said:
you may want to warn those about the mtd partition system while porting since i ve ran into several of them
Click to expand...
Click to collapse
Yeah...ive been looking for another rom to port as the one i last did was just discontinued by the original dev, out of the three ive tried so far all have been mtd file system...will add to OP/title that it doesnt work with mtd file systems...
I am wanting to try my hands at porting Sense ROMs for my Shift and was wondering what I should use as the base. I found a thread, http://forum.xda-developers.com/showthread.php?t=934313, that has the stock ROM from the Shift that has just been rooted and nothing else. Is this what I should use as the base for it and then find another Sense ROM, ideally 3.0 or above, and use it as the porting ROM? Thanks for any answers, I am hoping to become a help to those who are wanting to get into this field by not being afraid to ask these questions, because I myself would love to become a dev and figured porting would be the best jumping off point and then working my way into building whole custom ROMs.
This would be an updated base for Gingerbread Sense ROMS http://forum.xda-developers.com/showthread.php?t=1873472
To port Sense 3.6+ ICS is going to be some work. Porting Sense is more involved than just moving a few files and getting it to boot. It's honestly easier to use the dsixda kitchen to turn a system.img and boot.img into a ROM than it is to port. I've been messing with Android for a good year now and I've just learned to port aosp, and Def can't port Sense.
Sent from my miTouch-4G-Slide using Tapatalk 2
strapped365 said:
This would be an updated base for Gingerbread Sense ROMS http://forum.xda-developers.com/showthread.php?t=1873472
To port Sense 3.6+ ICS is going to be some work. Porting Sense is more involved than just moving a few files and getting it to boot. It's honestly easier to use the dsixda kitchen to turn a system.img and boot.img into a ROM than it is to port. I've been messing with Android for a good year now and I've just learned to port aosp, and Def can't port Sense.
Sent from my miTouch-4G-Slide using Tapatalk 2
Click to expand...
Click to collapse
So most of the "porting tutorials" I have seen out there are full of bs and not as easy as they make it out to be then lol. I have read through ones using dsixda kitchen, I will go that route, thanks for the advice and answer.
nateandjess07 said:
So most of the "porting tutorials" I have seen out there are full of bs and not as easy as they make it out to be then lol. I have read through ones using dsixda kitchen, I will go that route, thanks for the advice and answer.
Click to expand...
Click to collapse
In all honesty they were that easy, but with every new version of android comes new files, or renamed files ect.
Porting aosp is as easy as the guides, megaghost is who started teaching me how to port aosp, then a couple guides later I noticed that there were libs I never moved over from port to base.
Dsixda kitchen is just a tool for me, I use it to sign apks when I don't decompile them in android-utility also if I'm leaving the house and need something deodexed, or to simply cook an ota into a flashable.
Sent from my miTouch-4G-Slide using Tapatalk 2
But there is always something with AOSP ports that you have to go back and fix and that is not always easy... In fact it is sometimes mind numbingly difficult to get some stuff to work. Trial and error, and don't be afraid to ask questions if you get stuck.
Yes just post up. People in the Shift forum are more than willing to help each other out
This might be a noob question, but I want to know that since our bootloader is locked, how we are able to port Cynaogenmod and other ROMs like Paranoid Android to Atrix 2? Recently official AOSP ROM was released for Moto RAZR which also has a locked bootloader. So why we can't have an official CM for Atrix 2?
What difference is there between a CM port and an official CM for unlocked bootloader device ?
Just some noob questions which came in my mind. Please clarify. Sorry for a silly question.
androiddecoded said:
This might be a noob question, but I want to know that since our bootloader is locked, how we are able to port Cynaogenmod and other ROMs like Paranoid Android to Atrix 2? Recently official AOSP ROM was released for Moto RAZR which also has a locked bootloader. So why we can't have an official CM for Atrix 2?
What difference is there between a CM port and an official CM for unlocked bootloader device ?
Just some noob questions which came in my mind. Please clarify. Sorry for a silly question.
Click to expand...
Click to collapse
It all surrounds around the kernel. Unlocked bootloader devices can run "custom" compiled kernels, and CM and the other "custom" non-stock based roms all have their own kernels too.
The reason that we can run "unofficial" versions is because your devs (me included), have to compile the ROM around the "stock" kernel, so that it can be installed right along side the stock kernel, and run without issue. All of the AOSPA, and PA, and such are the same exact way.
Anything that can be done on the Razr can pretty much be done on this phone. The thing is that your dev team is much smaller on the A2 as it was not a very popular device, so it takes longer if ever to get something since the devs make the choice to work on a specific ROM or not.
Also the "official" CM compiles are done by the cyanogen mod team themselves and they do all the coding and have an auto compile server to get the versions out to the public, so again it is up to the developers there to decide which phones they want to support. Again though if you look all the "official" build devices ALL have unlocked bootloaders in some form or fashion, so that the "custom" compiled kernel will install with out issue.
Actually, it looks like Hashcode and dhacker recently got the RAZR included in the "official" CM nightlies... http://wiki.cyanogenmod.org/w/Spyder_Info
So, if something stable enough is worked out for the A2 (i.e. kexec), then we could possibly see an "official" edison of some sort at some point... in theory.
For now, I'll be happy with stable "unofficial" builds..
alteredlikeness said:
Actually, it looks like Hashcode and dhacker recently got the RAZR included in the "official" CM nightlies... http://wiki.cyanogenmod.org/w/Spyder_Info
So, if something stable enough is worked out for the A2 (i.e. kexec), then we could possibly see an "official" edison of some sort at some point... in theory.
For now, I'll be happy with stable "unofficial" builds..
Click to expand...
Click to collapse
That is still not considered "official" cyanogen builds.....
If it is not listed here, then it is not 100% official:
http://get.cm
It is lets say.... an unofficial, "official" build, though. LOL
jimbridgman said:
That is still not considered "official" cyanogen builds.....
If it is not listed here, then it is not 100% official:
http://get.cm
It is lets say.... an unofficial, "official" build, though. LOL
Click to expand...
Click to collapse
Um, Jim.. spyder and umts_spyder are both listed there
Still, I think Hashcode and dhacker have the status/connections to get it dubbed "official"..
alteredlikeness said:
Um, Jim.. spyder and umts_spyder are both listed there
Still, I think Hashcode and dhacker have the status/connections to get it dubbed "official"..
Click to expand...
Click to collapse
so do I.... Don't forget who is on the cm coding team....
I did some looking internally at CM and found that these are semi-official, right now, with a big but, the kexec I am told is what is keeping it with the semi status...
They are looking into changing that for kexec based compiles, so.... Hopefully, that happens.
jimbridgman said:
It all surrounds around the kernel. Unlocked bootloader devices can run "custom" compiled kernels, and CM and the other "custom" non-stock based roms all have their own kernels too.
The reason that we can run "unofficial" versions is because your devs (me included), have to compile the ROM around the "stock" kernel, so that it can be installed right along side the stock kernel, and run without issue. All of the AOSPA, and PA, and such are the same exact way.
Anything that can be done on the Razr can pretty much be done on this phone. The thing is that your dev team is much smaller on the A2 as it was not a very popular device, so it takes longer if ever to get something since the devs make the choice to work on a specific ROM or not.
Also the "official" CM compiles are done by the cyanogen mod team themselves and they do all the coding and have an auto compile server to get the versions out to the public, so again it is up to the developers there to decide which phones they want to support. Again though if you look all the "official" build devices ALL have unlocked bootloaders in some form or fashion, so that the "custom" compiled kernel will install with out issue.
Click to expand...
Click to collapse
Thanks for the reply. I wish I could also develop something for Atrix 2. But I am not familiar with the development. How is it done? and where do you test it and all other things? Is there some starting tutorial there for it? Or maybe some place from where you all guys started learning the developement?
androiddecoded said:
Thanks for the reply. I wish I could also develop something for Atrix 2. But I am not familiar with the development. How is it done? and where do you test it and all other things? Is there some starting tutorial there for it? Or maybe some place from where you all guys started learning the developement?
Click to expand...
Click to collapse
I would start with my thread for all the tools you need.
http://forum.xda-developers.com/showthread.php?t=1404442
Then you can start with taking a shot at a stock based ROM, since they really are the easiest place to start. You will need some form of linux ubuntu is really the most supported distro for android dev work, so that is a good start. This can be a VM to start out with, you can use a free VM tool like virtual box, if you want to just to give it a try, but I will tell you a dual boot works much better, and I will be honest I have a machine that just uses ubuntu and does not run windows at all. I have a wine install for things like netflix and such, but other than that.... no windows. That is just me though.
The key is the android kitchen... and that ONLY runs on linux, that where you build your ROM at. There are guys like rdavisct, who do it on windows, but even he would tell you how much of a PIA it was for him, and he did eventually go to ubuntu with my help.
After that you can start to look at compiling roms like CM, aospa, and the like.
jimbridgman said:
I would start with my thread for all the tools you need.
http://forum.xda-developers.com/showthread.php?t=1404442
Then you can start with taking a shot at a stock based ROM, since they really are the easiest place to start. You will need some form of linux ubuntu is really the most supported distro for android dev work, so that is a good start. This can be a VM to start out with, you can use a free VM tool like virtual box, if you want to just to give it a try, but I will tell you a dual boot works much better, and I will be honest I have a machine that just uses ubuntu and does not run windows at all. I have a wine install for things like netflix and such, but other than that.... no windows. That is just me though.
The key is the android kitchen... and that ONLY runs on linux, that where you build your ROM at. There are guys like rdavisct, who do it on windows, but even he would tell you how much of a PIA it was for him, and he did eventually go to ubuntu with my help.
After that you can start to look at compiling roms like CM, aospa, and the like.
Click to expand...
Click to collapse
I don't want to be the antagonist here , but I did everything in Windows until I started my attempts at building from source.
Dsixda's kitchen works fine in Windows with Cygwin. I started off building pseudo-ROMs (or rebuilding the stock ROMs) with the kitchen, and then I eventually just used 7-zip and other tools and did it manually.
I currently use Ubuntu 12.04 64-bit in Virtual Box in Windows on my laptop to compile from source. But I did just install 12.10 fully on my old PC... 32-bit unfortunately.. I need to upgrade that comp, or find a work-around to build in 32-bit.. Anyhow, it runs much nicer than windows xp did.
Sent from my paranoid phone's mind
jimbridgman said:
I would start with my thread for all the tools you need.
http://forum.xda-developers.com/showthread.php?t=1404442
Then you can start with taking a shot at a stock based ROM, since they really are the easiest place to start. You will need some form of linux ubuntu is really the most supported distro for android dev work, so that is a good start. This can be a VM to start out with, you can use a free VM tool like virtual box, if you want to just to give it a try, but I will tell you a dual boot works much better, and I will be honest I have a machine that just uses ubuntu and does not run windows at all. I have a wine install for things like netflix and such, but other than that.... no windows. That is just me though.
The key is the android kitchen... and that ONLY runs on linux, that where you build your ROM at. There are guys like rdavisct, who do it on windows, but even he would tell you how much of a PIA it was for him, and he did eventually go to ubuntu with my help.
After that you can start to look at compiling roms like CM, aospa, and the like.
Click to expand...
Click to collapse
Thats awesome. I have both Red Hat and Ubuntu installed. What about the testing? After compiling do you test it directly on your Atrix 2? I have only one mobile and am afraid to test it directly on it. :crying:
androiddecoded said:
Thats awesome. I have both Red Hat and Ubuntu installed. What about the testing? After compiling do you test it directly on your Atrix 2? I have only one mobile and am afraid to test it directly on it. :crying:
Click to expand...
Click to collapse
Yes, that is the only way. That is why you have the fxz and rsd lite handy and ready, just in case. 20 min. and you are back up and running. If you are concerned go buy a 10-40 buck "burner" at Walmart and put your sim in it, for while you test. I am lucky that I still have my HTC hero lying around for just that purpose... Every time I bricked my a2 (doing bootloader work), that was my go to backup.
I never needed it while doing ROM work, because the worst that will happen is boot loops/soft brick, it is nearly impossible to hard brick the a2 testing a ROM that does not have a kernel in it.
jimbridgman said:
Yes, that is the only way. That is why you have the fxz and rsd lite handy and ready, just in case. 20 min. and you are back up and running. If you are concerned go buy a 10-40 buck "burner" at Walmart and put your sim in it, for while you test. I am lucky that I still have my HTC hero lying around for just that purpose... Every time I bricked my a2 (doing bootloader work), that was my go to backup.
I never needed it while doing ROM work, because the worst that will happen is boot loops/soft brick, it is nearly impossible to hard brick the a2 testing a ROM that does not have a kernel in it.
Click to expand...
Click to collapse
Thanks sir. Got that
Will try to contribute something if I can. Kudos to our dev team. You guys are doing a great job. Happy to be a part of a great community
jimbridgman said:
Yes, that is the only way. That is why you have the fxz and rsd lite handy and ready, just in case. 20 min. and you are back up and running. If you are concerned go buy a 10-40 buck "burner" at Walmart and put your sim in it, for while you test. I am lucky that I still have my HTC hero lying around for just that purpose... Every time I bricked my a2 (doing bootloader work), that was my go to backup.
I never needed it while doing ROM work, because the worst that will happen is boot loops/soft brick, it is nearly impossible to hard brick the a2 testing a ROM that does not have a kernel in it.
Click to expand...
Click to collapse
I took the Paranoid Android ROM from this page for practice. http://forum.xda-developers.com/showthread.php?t=2050705
I extracted it using Android Kitchen, but it says boot.img not found. Do we need to add boot.img from our phone or its not needed since we have a locked bootlader. Or should I take stock Atrix 2 ROM?
androiddecoded said:
I took the Paranoid Android ROM from this page for practice. http://forum.xda-developers.com/showthread.php?t=2050705
I extracted it using Android Kitchen, but it says boot.img not found. Do we need to add boot.img from our phone or its not needed since we have a locked bootlader. Or should I take stock Atrix 2 ROM?
Click to expand...
Click to collapse
Ok, so you need to let the kitchen create or import a "fake" one, as the kitchen was originally made for like samsung and htc phones and they require one, so the kitchen needs one, it will remove it when it builds the ROM and creates the zip file.
Also make sure you have the edison file, that was listed and where to put it was also listed in my thread on ROM building for the A2. That will help you create a proper updater-script when it builds the ROM, as well as give the proper mapping for our partitions on the A2.
jimbridgman said:
Ok, so you need to let the kitchen create or import a "fake" one, as the kitchen was originally made for like samsung and htc phones and they require one, so the kitchen needs one, it will remove it when it builds the ROM and creates the zip file.
Also make sure you have the edison file, that was listed and where to put it was also listed in my thread on ROM building for the A2. That will help you create a proper updater-script when it builds the ROM, as well as give the proper mapping for our partitions on the A2.
Click to expand...
Click to collapse
I will do it tomorrow. Really thank you for assisting me.
jimbridgman said:
Ok, so you need to let the kitchen create or import a "fake" one, as the kitchen was originally made for like samsung and htc phones and they require one, so the kitchen needs one, it will remove it when it builds the ROM and creates the zip file.
Also make sure you have the edison file, that was listed and where to put it was also listed in my thread on ROM building for the A2. That will help you create a proper updater-script when it builds the ROM, as well as give the proper mapping for our partitions on the A2.
Click to expand...
Click to collapse
One more doubt. I am building ROM from already built ROM i.e. the zip is already compiled, so how can I fix bugs like camera bugs and other things because they are already compiled i.e. in the form of apk.So should I use APK tool which is used to decompile the apk? Is there any difference while creating a ROM from source and creating it from already compiled zips.?? Silly question but I want to clear all these doubts
I downloaded the leaked 4.1 for Atrix 2. But I can't see the same folder format in that like system, META-INF? Why is that difference
androiddecoded said:
One more doubt. I am building ROM from already built ROM i.e. the zip is already compiled, so how can I fix bugs like camera bugs and other things because they are already compiled i.e. in the form of apk.So should I use APK tool which is used to decompile the apk? Is there any difference while creating a ROM from source and creating it from already compiled zips.?? Silly question but I want to clear all these doubts
I downloaded the leaked 4.1 for Atrix 2. But I can't see the same folder format in that like system, META-INF? Why is that difference
Click to expand...
Click to collapse
The issues for the camera are NOT in the apk itself, they are in the vendor libraries, the issue is that when vendor libraries are introduced for certai n things the ROM does not boot.
The best bet until you get better at C code and compiling ROMS, I would not mess with that. You can however build a working CM10.1 with a working camera by using a camera apk from the market, like 360 camera, and there are a few others, you can just drop that into /system/app and build the ROM and it should work for you.
Once you complie CM there is not much you can fix like that, rdavisct and I were doing just that until Wang released his source for the required A2 files (we did find a lot of issues and fix them, but they were actual missing libs and similar back then., It really is a lost cause to use the zip to "fix" "real compiled in bugs, because anything you do like that will not have the needed pieces compiled around it, some libraries will not work right since others that are from CM were not compiled around the ones from the phone, and think that they are part of the CM code, and are not "includes" in the compile.
You can however do a lot of customizing to the ROM to fit YOUR needs, but do not expect to fix any issues this way. Like I mentioned the camera is an easy one, you then just go to settings tell it your "default" camera app is the 360 camera, not the stock CM one.
jimbridgman said:
The issues for the camera are NOT in the apk itself, they are in the vendor libraries, the issue is that when vendor libraries are introduced for certai n things the ROM does not boot.
The best bet until you get better at C code and compiling ROMS, I would not mess with that. You can however build a working CM10.1 with a working camera by using a camera apk from the market, like 360 camera, and there are a few others, you can just drop that into /system/app and build the ROM and it should work for you.
Once you complie CM there is not much you can fix like that, rdavisct and I were doing just that until Wang released his source for the required A2 files (we did find a lot of issues and fix them, but they were actual missing libs and similar back then., It really is a lost cause to use the zip to "fix" "real compiled in bugs, because anything you do like that will not have the needed pieces compiled around it, some libraries will not work right since others that are from CM were not compiled around the ones from the phone, and think that they are part of the CM code, and are not "includes" in the compile.
You can however do a lot of customizing to the ROM to fit YOUR needs, but do not expect to fix any issues this way. Like I mentioned the camera is an easy one, you then just go to settings tell it your "default" camera app is the 360 camera, not the stock CM one.
Click to expand...
Click to collapse
Oh, ok. So can I try removing Moto Homescreen app and setting Nova Launcher as default?
And why is the difference between files between Moto 4.1 leak and Paranoid Android ROM. The regular mapping of folder is not there like META-inf , /system etc..
EDIT: I think I got it. Leaked Moto 4.1 is fastboot file and PA is flashable zip. I think I am right. Can I get the zip for Moto 4.1 leak?
4.1 leak is not a flashable zip.
The meta-inf folder items are for zips that are flashed in recovery.
And, not to dissuade you from jumping in to modding/dev'ing, but you may want to take things a bit slower... Start small.. And read/research a lot.
Sent from my paranoid phone's mind
androiddecoded said:
Oh, ok. So can I try removing Moto Homescreen app and setting Nova Launcher as default?
And why is the difference between files between Moto 4.1 leak and Paranoid Android ROM. The regular mapping of folder is not there like META-inf , /system etc..
EDIT: I think I got it. Leaked Moto 4.1 is fastboot file and PA is flashable zip. I think I am right. Can I get the zip for Moto 4.1 leak?
Click to expand...
Click to collapse
No, there is not a flashable "zip" for the Moto 4.1 leak, you will have to build that on your own with the Rom kitchen, since it is an FXZ, it will not have those flashable parts. The kitchen is very easy to use, it is menu driven and only takes about 30 min to an hour to do what it seems you want to do.
You can replace the launcher from within a flashable zip, but you might have issues, because the MOTO blur junk that is in their ROMS DEPENDS on it, if you do NOT leave it (moto blur launcher) in /system, then a number of things will not work that depend on the moto launcher (they are embedded in the xml files in the apks, and need to be edited to NOT look for the moto laucher), I think it is more trouble than it is worth, personally.
I would throw Apex in there if that is what you want, and then on first boot select it as your default launcher and be done with it, less issues and mess, other than the old moto launcher taking space in /system. BY the way ANYTHING that you put in /system is not really 100% upgrade-able by the market app, so like lets say you put apex in /system, then the market can not update the version in /system, since it is read only, and it will either fail the update, or try to put the newer updated files /data, so you will have things in two places for your 3rd party launcher. It is MUCH better to put any APKS that would come from the market into /data so they can get updates with out any odd issues, just a heads up...
--EDIT--
As alteredlikeness said about the same time I was posting, start a little smaller, and do a bunch of learning, because from what I see you asking about and posting in here, you have a good bit of learning to do, about how the directory structure and things are and work in android, as well as some ROM building basics.
Hey Everybody,
Has anybody tried using Android Kitchen by dsixda to port roms to our device, the one sv?
According to the Kitchen's thread it was built for Htc devices....
I am new to porting and porting to htc devices seems much harder than porting to Samsung devices?!
I have tried using ViperSv.. It's horrible.. I mean it's really laggy .. I am currently using the stock rom with many Xposed mods.
What exactly do you expect it should do for you?
Porting other roms will need either very much resizing to resolution of SV or finding drivers/files that work with its hardware (in simple words).
In both cases the kitchen will not do the work for you.
I thought you left! Welcome Back
I thought porting is just copying kernel files/drivers and using a rom from a device with the same res. #noobinglikeaboss
imankareem said:
I thought you left! Welcome Back
Click to expand...
Click to collapse
From time to time i come and take a look, if there is something new up here
I thought porting is just copying kernel files/drivers and using a rom from a device with the same res. #noobinglikeaboss
Click to expand...
Click to collapse
Well, if it would be that easy....
I don't want to discourage you, but at least some basic knowledge is needed.
I tried to port Desire 500 dump, but it didn't even boot, so i think you need a good guide, to do that.
Awww.. Well I thought it would be easy since Cm gets ported instantly to every new device