Database Info

[ROM][27 APR] Puregandroid v 1.1

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!

[PORT][ROM]LeWa Rom (extremely early alpha, further development done by EminSG)

This is just a quick 30 minutes port, i saw a tutorial on how to port LeWa to CM7, but it failed actually so i screwed a bit around with the files and got it booting, I'm not gonna continue any development on this rom, so don't ask me for anything, I have broodROM to take care of already XD
couldn't decide to take the ROM tag or the JOKE tag, since it actually runs i chose for the ROM tag
If you're really bored atm this might be fun to test, else don't even waste your time on it , I actually did no effort at all to make it bugfree, just wanted to get it running
What is not working, almost everything that is needed for daily use
To get past the lockscreen you need to press the home key and then tap menu and back a few times, only this way you will unfreeze the screen. So this is just a fun test, since it sucks so hard to actually use as rom (because of all the bugs, not the rom itself)
Installation:
1. install arco's recovery
2. install the zip in recovery
3. wipe /data and /cache and boot
if you want some laughter you could hold logcat next to it, the errors list is humongous.
Download:
http://www.mediafire.com/?a3c9qlzor9c2n60
The screenshot are unfortunately all red..

:-D amazing
Sent from my GT-I9001 using XDA Premium App

I think this LeWa ROM could be a good port, it's has a nice MIUI like design and is extremely lite,
I got it booting pretty easily, so I think a actual port could be made, just like MIUI but of course with the known bugs of CM7!
I'm starting to hate the fact that the i9001 doesn't even have proper AOSP support more and more, If broodROM would be built on AOSP it would be ****ing great , samsung really screwed up their baseroms (if you only look at rom size and ram usage)

Well, Happy and Lucky developing!

Broodplank?

KoekwousNL said:
Broodplank?
Click to expand...
Click to collapse
Speak you may
xewier said:
Well, Happy and Lucky developing!
Click to expand...
Click to collapse
Hehe yes but not by me for this rom I've got plenty of work for broodROM only,
Anyone who wants to take over this port is welcome

Still better than samsung stock roms

BzArEx said:
Still better than samsung stock roms
Click to expand...
Click to collapse
hehe true story sadly

Still a lot girly than samsung stock roms

nail16 said:
Still a lot girly than samsung stock roms
Click to expand...
Click to collapse
Yes XD thats true, one of the reasons i wouldn't use it

Ok so I found an other person that likes to continue the development of this rom, his nickname is EminSG. he still has 0 posts so you will see him around very soon.
to mod: this topic may be closed

Why an official CM 10 is not possible for Atrix 2?

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.

[DEV]- Pantech Vega N6 A860 - CM10 Porting

This thread is going to be WIP thread for the porting of CM10 to the Pantech Vega N6 A860 codename e51.
Currently kernels are extracted and device tree wip while I collect the files to be input
https://github.com/VincentEmmanuel/android_kernel_pantech_e51k.git
I welcome anyone who is interested to help out in any way because I am really new in this porting stuff.
WIll update as and when more work is done.
Things working on now
1. Trying to find a suitable msm8960 common files repo (Not sure whether needed this at all but conducting R&D now)
2. Compiling a list of proprietary files needed for the build
God bless.
Vincent

ClockworkMod
ClockworkMod for A860 K/L/S
Flash using fastboot. Instructions are all over XDA so please search.
Thanks

thanks so much for your work...
another than CM10.1 , I also want to see customized kernel which can further enhance A860 , like power tweaks, disable logging, init.d or even add FauxAudio mod

Finally something about te Vega No6
I have the A860K. I installed a customized ROM from here http://mizal.net:82/pantech/NO.6/
Works fine, but it is not very customized. Still would like to get rid of Korean characters.Another kernel. deodexed. Less bloatware, etc.
Any other customizations?
Cheers!
---------- Post added at 11:58 AM ---------- Previous post was at 11:20 AM ----------
Leechoonhwee said:
This thread is going to be WIP thread for the porting of CM10 to the Pantech Vega N6 A860 codename e51.
Currently kernels are extracted and device tree wip while I collect the files to be input
https://github.com/VincentEmmanuel/android_kernel_pantech_e51k.git
I welcome anyone who is interested to help out in any way because I am really new in this porting stuff.
WIll update as and when more work is done.
Things working on now
1. Trying to find a suitable msm8960 common files repo (Not sure whether needed this at all but conducting R&D now)
2. Compiling a list of proprietary files needed for the build
God bless.
Vincent
Click to expand...
Click to collapse
I would not mind helping, but I am even newer than yourself
I am not a programmer, but I know very good shell scripting, PHP, and not so good C and some other useless languages.
I have pro skills in Linux as well (I work with it)
Let me know if I could be of any help.
Cheers and good luck!

magare said:
I have the A860K. I installed a customized ROM from here http://mizal.net:82/pantech/NO.6/
Works fine, but it is not very customized. Still would like to get rid of Korean characters.Another kernel. deodexed. Less bloatware, etc.
Any other customizations?
Cheers!
---------- Post added at 11:58 AM ---------- Previous post was at 11:20 AM ----------
I would not mind helping, but I am even newer than yourself
I am not a programmer, but I know very good shell scripting, PHP, and not so good C and some other useless languages.
I have pro skills in Linux as well (I work with it)
Let me know if I could be of any help.
Cheers and good luck!
Click to expand...
Click to collapse
Anyone can help in anyway they can! Please take a look at the following page about CM porting.
http://wiki.cyanogenmod.org/w/Doc:_porting_intro
Currently, I am trying to find a similiar device in terms of hardware and use their kernel github and try to build a test build
Device Tree
https://github.com/CyanogenMod/android_device_sony_yuga
Kernel
https://github.com/CyanogenMod/android_kernel_sony_apq8064
Let me know. Thanks!!!!

Sorry. Got busy at work and don't have time now.

Interesting
Sent from my IM-A860S using xda app-developers app

I found a gitub source for this device github.com/mifl/android_kernel_pantech_im-860s, but i have no time to verify yet
i would like to help since i just got mine today, but i only do android programming and driver compiling, and i never successfully make a kernel that can boot my galaxy s2 and some chinese tabs

Hi Vincent,
I just bought a A860S and want to back up boot/system/recovery partitions, probably all partitions, except the data one.
Do you know anyway to open those official update .binx file?
Thanks.

aget1 said:
I found a gitub source for this device github.com/mifl/android_kernel_pantech_im-860s, but i have no time to verify yet
i would like to help since i just got mine today, but i only do android programming and driver compiling, and i never successfully make a kernel that can boot my galaxy s2 and some chinese tabs
Click to expand...
Click to collapse
I think this is the stock kernel. I think we need to grab a working kernel from Xperia Z or Oppo Find 5 since we are on the same architecture.

totalz said:
Hi Vincent,
I just bought a A860S and want to back up boot/system/recovery partitions, probably all partitions, except the data one.
Do you know anyway to open those official update .binx file?
Thanks.
Click to expand...
Click to collapse
I remembered coming across a CWM mod that can allow you to choose which to backup. You can try ROM Toolbox.

Leechoonhwee said:
I think this is the stock kernel. I think we need to grab a working kernel from Xperia Z or Oppo Find 5 since we are on the same architecture.
Click to expand...
Click to collapse
As long as it boots, and it is a 3.4.0 kernel, i think it will work with cm10
anyway i am checking out cyanogenmod, but i dont find the a860 cwm recovery_ui.cpp source, only binary... i guess i need time to find the button mapping?

You could get answers from SDA.
Sent from my KM-S220 using xda app-developers app

There is a working CWM around in the 91dongji forum - works fine on my A860S with 1.30 software; now updating to 1.36 and see if the recovery sticks.
I'll post detailed instructions here once it is confirmed to work

i hope we can get some update on your efforts. though the crowd for this specific device is fewer than a handful for now, a lot of users are just waiting anxiously for any development....

Is there hope for this device to receive custom ROM?

there's a very active community in vegaviet coming up with mods and roms based on stock.you may want to check them out.

tommyrumbler said:
there's a very active community in vegaviet coming up with mods and roms based on stock.you may want to check them out.
Click to expand...
Click to collapse
I tried flashing the roms from the Vegaviet but i had a problem getting my network to connect. after the restore was complete there was no apn settings for the network. I tried reading but the translations from the website but it dont make sense and no one noticed issue because they are not located in korea.

clockedtouch said:
I tried flashing the roms from the Vegaviet but i had a problem getting my network to connect. after the restore was complete there was no apn settings for the network. I tried reading but the translations from the website but it dont make sense and no one noticed issue because they are not located in korea.
Click to expand...
Click to collapse
so why not set up your APN? that should be easy.
Also, using the ROM from vegaviet, i noticed the following observation :
-there was a considerable build-up of lag after three to four days of use, especially when doing a lot of web browsing
-the browser is unable to open some websites/webpages due to Ad-Block restriction
-the forced DNS settings most times slow-down my internet connection
-the keyboard still retains Korean functionality, with Korean characters sometimes getting in the way when typing
-kernel logging was enabled
much of the above were solved using the uninstall zip of crossbreeder - i just noticed our Vietnamese friends are fond of using cross-breeder on all their ROM mods.
the keyboard i uninstalled and deleted the IME file in system and just replaced it using Optimus G Pro's keyboard IME installer.
everything should be all good. don't ask me where i got those zips - a simple search should do wonders for you.

The rom doesn't allow for setting up your own APN. Those features are not available in JB. Thanks for the tips but I just went back to stock since I wasn't able to get the network going.
Sent from the brightest star in the sky using xda app-developers app

| ROM | FLO | AOSP | KitKat | 4.4 | S3 | 11-30-2013

Android 4.4
S3 builds are focused on being a simple, stable, and "stock-like" experience for your Android device.
View the source code at: http://github.com/jakdillard
----------
Developed by:
Jakdillard
----------
Devices currently supported:
Asus Nexus 7 (2013)
LG Nexus 5
S3 includes modifications to extend the basic functions of Android. With each update to Android, S3 features may change to work with the current version.
Feature list:
- Full Google Experience
- Clear Recents with VM Cache drop
- Reboot In Power menu
- Screenshot In Power menu (enable in developers settings)
- Advanced Reboot options (enable in developers settings)
- Swapped "on click" and "longpress" behavior for WIFI, Mobile network, and BlueTooth tiles
- Init.d support
- SuperSU root
Instructions:
First time flashing device, or coming from another ROM?
Download the zip(s).
Optional: adb backup
Fastboot oem unlock > fastboot flash recovery recovery.img.
Perform a NANDroid backup of your current ROM.
Wipe data & cache partitions of your device (required when coming from stock!).
Flash ROM.
Known Issues:
This rom contains AOSP versions of Gallery2 and Camera2 which does not contain Google features such as HDR+ and Picasa album viewing. Also I DO NOT USE FACE LOCK SO I DIDN'T INCLUDE IT SINCE I BELIEVE ITS A WASTE OF SPACE.
ROM: Link
G-Apps (INCLUDED)
Follow the above link for the complete source to make your own changes or to completely debug down to the core of the rom also follow my github for detailed changes.
Always remember that XDA started out as a great place and will remain a great place as long as we are great to each other anything used in this ROM is available upon request and feel free to use this as a base rom for any other project.
WANT TO CUSTOMIZE THIS ROM READ THIS:
Want to add or remove anything or customize for yourself use DSIXDA's Kitchen. Its a great kitchen for customizing prebuilt ROMs.

Hi. Just installed this and I like it. A few others have been having issues with chrome and location services causing soft reboots and really bad stability. This ROM does not have that problem. I tried first with the full PA gapps and had issues with Google search and the Google calendar FC. Wiped and clean installed and used the Banks gapps. All is good now.
Gonna go install the Elemental X kennel now.
Thanks for the ROM.
Sent from my Nexus 7 using XDA Premium 4 mobile app

going to try this and add some tweaks to it get more power of using aosp

HI @jakdillard . First off thanks for the great AOSP ROM. Glad to see more entries. I have a question not about the ROM because its excellent for me but ever since the AOSP ROMs started coming out, some of us have noted a recurring problem with many of them. @scrosler maintains a AOSP ROM which is afflicted. @ctfrommn does too for some of us. The main problem we have is that when we load these ROMs on our Nexus 7 wifi editions and visit pages which request access to locations like www.google.com, www.yahoo.com or others, the chrome browser crashes and for me it causes a soft reboot. If we just stick to the aosp ROM after some bit of time the AOSP browser also gets very unstable and will start crashing no matter how much cleaning, clearing, etc we do. @scrosler had documented some of this and we've collaborated a bit trying to figure out why this happens. On rasbean, carbon, your ROM, and a few others it does not happen.
I am hoping perhaps you could share some knowledge and let us know any commits, if you saw this behavior before you put the ROM up and did something to fix it. Any info at all would be very helpful. I'd love to be able to see this fixed and get the other ROMs working.
Thanks for the contribution again.

mpmilestogo said:
HI @jakdillard . First off thanks for the great AOSP ROM. Glad to see more entries. I have a question not about the ROM because its excellent for me but ever since the AOSP ROMs started coming out, some of us have noted a recurring problem with many of them. @scrosler maintains a AOSP ROM which is afflicted. @ctfrommn does too for some of us. The main problem we have is that when we load these ROMs on our Nexus 7 wifi editions and visit pages which request access to locations like www.google.com, www.yahoo.com or others, the chrome browser crashes and for me it causes a soft reboot. If we just stick to the aosp ROM after some bit of time the AOSP browser also gets very unstable and will start crashing no matter how much cleaning, clearing, etc we do. @scrosler had documented some of this and we've collaborated a bit trying to figure out why this happens. On rasbean, carbon, your ROM, and a few others it does not happen.
I am hoping perhaps you could share some knowledge and let us know any commits, if you saw this behavior before you put the ROM up and did something to fix it. Any info at all would be very helpful. I'd love to be able to see this fixed and get the other ROMs working.
Thanks for the contribution again.
Click to expand...
Click to collapse
Very well put. I build rom's from aosp for myself. I am, of course, running into the same issues. Clearly there is something being added by Google that doesn't exist in aosp to make Google location services work. Obviously this rom has it. With the support of the aosp apps being slowly phased out in favor of Google apps, we are going to need a patch in order to be able to make a fully functional rom. Any help with this would be greatly appreciated.
Sent from my Flo using Tapatalk 4

ridobe said:
Very well put. I build rom's from aosp for myself. I am, of course, running into the same issues. Clearly there is something being added by Google that doesn't exist in aosp to make Google location services work. Obviously this rom has it. With the support of the aosp apps being slowly phased out in favor of Google apps, we are going to need a patch in order to be able to make a fully functional rom. Any help with this would be greatly appreciated.
Sent from my Flo using Tapatalk 4
Click to expand...
Click to collapse
mpmilestogo said:
HI @jakdillard . First off thanks for the great AOSP ROM. Glad to see more entries. I have a question not about the ROM because its excellent for me but ever since the AOSP ROMs started coming out, some of us have noted a recurring problem with many of them. @scrosler maintains a AOSP ROM which is afflicted. @ctfrommn does too for some of us. The main problem we have is that when we load these ROMs on our Nexus 7 wifi editions and visit pages which request access to locations like www.google.com, www.yahoo.com or others, the chrome browser crashes and for me it causes a soft reboot. If we just stick to the aosp ROM after some bit of time the AOSP browser also gets very unstable and will start crashing no matter how much cleaning, clearing, etc we do. @scrosler had documented some of this and we've collaborated a bit trying to figure out why this happens. On rasbean, carbon, your ROM, and a few others it does not happen.
I am hoping perhaps you could share some knowledge and let us know any commits, if you saw this behavior before you put the ROM up and did something to fix it. Any info at all would be very helpful. I'd love to be able to see this fixed and get the other ROMs working.
Thanks for the contribution again.
Click to expand...
Click to collapse
I have to look over those other roms sources to see what they are missing more the likely they don't have the location services pointing to the right adapter or still using the old way of making device trees causing make to not put the overlays together correctly.

Nice ROM Jak!
Syncing your Repo now!

Update 10-29-2013
http://d-h.st/RlW
10-29-2013
Added Google Play Edition Bootanimation
Added missing Flo props ( sound should be a little better )
Added missing proprietary DRM
De-Odexed ROM

Update 11-3-2013
Well there a beta quality build of KitKat in the op this will not be a daily driver until I have a complete source to work with and proper proprietary binaries but good luch and enjoy. Also consider this a nightly project as features will slowly be added.

Always under the radar for some reason, but your builds are always fantastic. Great job as always on 4.4. Loving the additional features.

Update 11-6-2013
http://d-h.st/bjj
New update but still no camera

jakdillard said:
http://d-h.st/bjj
New update but still no camera
Click to expand...
Click to collapse
Changes?

dictionary said:
Changes?
Click to expand...
Click to collapse
+1
Gesendet von meinem Nexus 7 mit Tapatalk 4

dictionary said:
Changes?
Click to expand...
Click to collapse
I know he added a file manager and volume rocker wake. Those two weren't in the OP for the first build.
Sent from my Nexus 7 using Tapatalk 4

Unfortunately flash fails inTwrp 2.6.3.1.

Awesome. Best KitKat ROM of all I have tried so far. Smooth and no fc or other issues at all so far. Stable in tests that other ROMs have failed. Thank you!
Sent from my Nexus 7 using XDA Premium 4 mobile app

Mindrocket said:
Unfortunately flash fails inTwrp 2.6.3.1.
Click to expand...
Click to collapse
I believe twrp has updated to 2.6.3.2

Great build!
Just wondering if anyone else is getting the keyboard every time you hit the home button coming form another app? Not a big deal, just curious.
Thanks!

jconner05 said:
Great build!
Just wondering if anyone else is getting the keyboard every time you hit the home button coming form another app? Not a big deal, just curious.
Thanks!
Click to expand...
Click to collapse
Every last person using any 4.4 with the new Google Experience Launcher.

jconner05 said:
Great build!
Just wondering if anyone else is getting the keyboard every time you hit the home button coming form another app? Not a big deal, just curious.
Thanks!
Click to expand...
Click to collapse
I just double tap the home button. It's less annoying.
Love Jack's creations. Keep up the great work and thanks for sharing.