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.
nerdkiller14 said:
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.
Click to expand...
Click to collapse
Check your pm nerd!
Sent from my Desire HD using XDA Premium App
Screenshots?
How does this differ from GingerBeast?
Read in Gingerbeasts thread somewhere (running it for three awesome days) and Dilli stated something along the lines that since gtx had put out Inspired AOSP (or working on it?) He did actually do a couple of things differently ala H icons, etc... and hinted that having two identical AOSP ROMS would have been dull and competitive or pointless or something. Since gtx isn't keeping up with his rom anymore (so it read?) This could be ok right? Would like to try the stable version, or is it?
I started flashing a sense rom again last night and almost immediately during setup scrapped it forb my NAN backup. I can get different results from seemingly identical roms.
MyPocketWizard
gtalum said:
FWIW, I'm not trying to be negative. I honestly want to know what differences there will be between GingerBeast (which I currently run and love) and PUREGANDROID. if there are some substantive differences I'd like to give it a try.
Click to expand...
Click to collapse
This is a CM7 base with various bits removed. Gingerbeast is a proper AOSP base with bits of CM7 added in. That's the major difference at least.
dyliho said:
Read in Gingerbeasts thread somewhere (running it for three awesome days) and Dilli stated something along the lines that since gtx had put out Inspired AOSP (or working on it?) He did actually do a couple of things differently ala H icons, etc... and hinted that having two identical AOSP ROMS would have been dull and competitive or pointless or something. Since gtx isn't keeping up with his rom anymore (so it read?) This could be ok right? Would like to try the stable version, or is it?
I started flashing a sense rom again last night and almost immediately during setup scrapped it forb my NAN backup. I can get different results from seemingly identical roms.
MyPocketWizard
Click to expand...
Click to collapse
Wish we had a pure aosp rom T_T
Gtx had the best one and its gone
Sent from my Inspire 4G using XDA App
If you look I came before Gingerbeast
nerdkiller14 said:
If you look I came before Gingerbeast
Click to expand...
Click to collapse
You talking about that post that was a chop and hack of Cm7?
I had a second post. With one built from CM source. This one is built from AOSP source with make files and framework files from CM.
I am working toward a more AOSP base. Building my own kernel, using image files from
AOSP, using AOSP programs. He Is just using a modified CM7.
This is an AOSP base actually.
sure just use the search funtion at the top of page and type PureGandroid 1.1
By beta I mean not all of the stuff I want in this version is there. The ROM is completely stable and ready for use. I just didn't remove and add all the things I wanted in this version
I am trying to get there but its very slow for me to do this. My co compiler John Weyrauch hasn't been online lately and we have had little progress the past 2 weeks
nerdkiller14 said:
I am working toward a more AOSP base. Building my own kernel, using image files from
AOSP, using AOSP programs. He Is just using a modified CM7.
Click to expand...
Click to collapse
what exactly do you think i did?
took a pre-compiled cm7 rom and modified it?. if im just using a modified cm7, what are you doing?
gingerbeast is built and compiled from aosp and cm7. both were cloned, some cm stuff was removed, aosp added. look in your /system/etc-
CHANGELOG-CM.txt
init.d- all cm init scripts
/system/bin-
backuptool.sh- cyanogen script
modelid_cfg.sh- cyanogen script
verify_cache_partition_size.sh- cyanogen script
-your default wallpaper is attached
what im saying is- dont act like your rom is pure aosp and then say mine is just a modified cm7.
like i said in my thread- as i go more and more cm is removed, and a lot already has- IE theme engine, i have the froyo lockscreen back(will make it in next update), etc- plus i added some of my own stuff to framework/ base. my kernel has some important tweaks(to me anyway- not sure why cm hasnt updated jhash to lookup3 in their kernel yet) that help with efficiency/speed that cm, nor any other kernel for the dhd inspire have
im not saying what your doing is a bad thing, its EXACTLY what i did. most users dont give 2 sh!ts what the base is- if they like how aosp looks, its fast and good on battery and bug free thats all that matters. (cyanogen base for the inspire is very good and pretty much bug free, which is exactly why i chose to use it- and i dont have the time for a 100% aosp rom made from scratch especially when that is readily available)
btw- its usually nice to put a credit in the OP for what you used of other peoples that helped you out. just to show appreciation for work done that benefited you.
By modified I meant using a hybrid that has modified files for Wallpapers, icons, etc. I am trying to create a non tweaked kernel with Google Apps included, and only opensource software in it (except for GAPPS).
I meant nothing against you or your rom also would it be ok if I extracted the lockscreen from your rom to use on mine?
My apps are aosp, icons aosp, wallpapers and sounds are from nexus s- which is technically aosp.
Everything is opensource
Yes you can use the lockscreen, but like I said it wont be included until next update, so you'll have to wait. It should be soon though
thank you. Would you be interested in making a 100% pure rom? I can compile most of it on my Mac Pro. I just need some help debugging some of the errors while compiling?
I've been here for a week or two... Just long enough to know how funny this is...
Sent from my rooted (GingerBeast) overclocked (1.9) HTC Inspire 4G.
Perfect Android is a redistribution of the Android Open Source Project and Google software code that I have lightly modified to make as a daily driver for myself that I'm sharing with the community. This project doesn't have and won't focus on adding a ton of features and mods but instead focus on stability, and reliability so yes basically this is a stock like rom but not just stock my only efforts will be to make it run better, and be more polished, and complete.
GOOGLE APPS ARE INCLUDED
DOWNLOAD:
https://hotfile.com/dl/181925379/d84644d/perfect_grouper_ota_2012-12-01.zip.html
Mirrors:
If you have an error or something pops up I ask that before you post about it please make sure that you are running the ROM as provided. I cannot troubleshoot anything that is related to using other kernels, mods, or themes.
This ROM is basically like a stock rom of jelly bean so there is not a need for screen shots ........
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 my ROM is un-branded just give me some mention .......
WANT TO CUSTOMIZE THIS ROM READ THIS:
Like the ROM and want to add or remove anything or customize for yourself use this http://forum.xda-developers.com/showthread.php?t=633246 DSIXDA's Kitchen. Its a great kitchen for customizing prebuilt ROMs
CREDITS:
CyanogenMod Team
Google - I used their apps
AOSP - of course
Probably gonna add a changelog here
AOSP 4.2 ROM so quickly? That will be interesting
Can you have some screenshots?
yep its uploaded
it looks just like stock I built it to be at least as good as what you get from google if everything is working correctly that is when I will begin modifying but for now it looks like the stock ROM so I didn't think screenshots would be needed
first of all you have to give us changelog, then i'll flash it, because now i don't know exactly what are the differences between Your rom and stock, so is it worth flash it?
Patroy said:
first of all you have to give us changelog, then i'll flash it, because now i don't know exactly what are the differences between Your rom and stock, so is it worth flash it?
Click to expand...
Click to collapse
Its solely up to you guys if you want to flash it as this is an expensive hobby for me I'm just sharing what I do with the community so is it worth it, for me yeah, for you I really don't care, I hope I'm not coming off as an ass but I have to draw a line somewhere. I not making any claims with this ROM I just sharing it if you use it fine if not fine, I don't get into the whole screenshots large claims huge changelog thing I just post and share I also maintain this ROM for the Sprint Galaxy Nexus which it has done just fine so if you want you can do a search here and see what and where I come from .......
I'm very happy when see any new rom in N7 development, because nexus need fresh look from developers, so i was thinking that You could push some new tweaks into ours devices. Almost all roms here are just "cleaned" or "minimalistic" or "performanced" in real these rom are almost stock with the same user experience. So do not get angry when I want to know if there will be something more here...
Does it work with twrp?
After flash with twrp, I see the information is Android 4.2 JOP40C. I dont know whether it is flashed or not?
I will happily try your rom to see how it compares to CleanRom, give my feedback tomorrow
Patroy said:
I'm very happy when see any new rom in N7 development, because nexus need fresh look from developers, so i was thinking that You could push some new tweaks into ours devices. Almost all roms here are just "cleaned" or "minimalistic" or "performanced" in real these rom are almost stock with the same user experience. So do not get angry when I want to know if there will be something more here...
Click to expand...
Click to collapse
I'm not getting angry with you in fact I agree however, regardless of how you feel about those roms someone still put that effort into them. Honestly for me the N7 is a new device and before I go making claims that my ROM can start your car and end world hunger I want to make sure that it at least meets stock standards. AOSP has done a lot of work to somewhat remove google entries in their code so it has taken me a few days to re-build AOSP code to work correctly with G-APPS and other Google code I do NOT claim to be an over the top developer I just do this as a pastime I have certain things that I do not like and thats why I have started making my own ROMs so that I always get what I want. Now I can tell you this and I know this as a fact THIS IS NOT A WINZIP KITCHEN ROM IT IS BUILT FROM SOURCE it took hella work to get it up to a win zip ROM and thats where we're at so far lol. When I learn all the changes to the 4.2 coding I will start to add small feature to my ROM.
SuperBoUDS said:
Does it work with twrp?
After flash with twrp, I see the information is Android 4.2 JOP40C. I dont know whether it is flashed or not?
Click to expand...
Click to collapse
yes it works with TWRP and the information in the About screen is correct
There isn't developer section in setting menu. Is this normal?
SuperBoUDS said:
There isn't developer section in setting menu. Is this normal?
Click to expand...
Click to collapse
Tap on the build in settings>about phone 7 times and it appears.
Paul
Sent from my Nexus 7 using xda app-developers app
PAULO76 said:
Tap on the build in settings>about phone 7 times and it appears.
Paul
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thank you! I dont know this.
This ROM doesn't include busybox. I think jakdillard should install busybox by default .
Testing this ROM with LeanKernel.
SuperBoUDS said:
Thank you! I dont know this.
This ROM doesn't include busybox. I think jakdillard should install busybox by default .
Testing this ROM with LeanKernel.
Click to expand...
Click to collapse
lol who knows I might depends on how things go with this
Installed thid yesterday and so far no problems, nice deep sleep of 96%. Nice work
With leanKernel, I just have 86% batterry overnight :crying:. I charged it fully the night before.
SuperBoUDS said:
With leanKernel, I just have 86% batterry overnight :crying:. I charged it fully the night before.
Click to expand...
Click to collapse
haven't checked for myself but is leankernel updated for 4.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.
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.
I would just like to mention an amazing rom that i just recently discovered that wasn't in our section It is PurifieD 3.5 rom over in the GT-I9505 section it said that it would only work with twrp/cwm and i was able to get it to boot with safestrap 3.75 after 1 slight change it has the option to look like samsung touch wiz or pure aosp theme and aosp lockscrren and apps stock messaging light or dark theme aosp dialer and contacts, clock, browser and more so i encourage everyone to check it out because it is smooth!
http://forum.xda-developers.com/showthread.php?t=2454205
Screenshot of about device?
Sgh-i337
Att I337 Nj4 baseband
Murasakiii said:
Screenshot of about device?
Click to expand...
Click to collapse
If its only booted with twrp or cwm, what change did you make to make this boot and still have WiFi and I assume data? Maybe you should share in the all things general thread?
Disregard. This ROM is already posted there. I wonder how this one is compatible and we can't figure out why the others aren't.
Murasakiii said:
If its only booted with twrp or cwm, what change did you make to make this boot and still have WiFi and I assume data? Maybe you should share in the all things general thread?
Disregard. This ROM is already posted there. I wonder how this one is compatible and we can't figure out why the others aren't.
Click to expand...
Click to collapse
Yup. This ROM was ported by Gogollie. This was built with a TouchWiz kernel, that's why it boots, it isn't real GPE without the GPE kernel. Just themed with some AOSP apps.
npjohnson said:
Yup. This ROM was ported by Gogollie. This was built with a TouchWiz kernel, that's why it boots, it isn't real GPE without the GPE kernel. Just themed with some AOSP apps.
Click to expand...
Click to collapse
actually no 3.5 I have never ported. If its davy's ROM still its probably Stock International Wanam ROM Build with KNOX and other crap cleaned up with options to install AOSP apps by DSA creator of BlackBox another great Hybrid or its 100% TouchWiz with his Domination theme flashed over the top. If you dont know what Domination is in terms of a theme its one of the greatest themes ever made. I miss the option to go white with it sometimes tho. Its themed to look nearly identical to AOSP. Theres other Aroma options to MOD the ROM to act more like AOSP or install AOSP Apps like Calculators, Camera, and stuff. The Aroma installer is pretty nifty and lets you somewhat De-Bloat while installing it.
My newest ROM looks completely different and installs at half the size. Its also a minimal install / beast with speed and battery. I dont know its been posted here but you should be able to use it no problem. with safestrap just flash your modules to get wifi working. and if your at&T you might have to flash an apn patch to replace the apns from /etc directory with your own. or maybe manually entering them would work too. Its nearly all AOSP but yes in order to maintain good data signal, wifi, tethering, usb, etc I had to make a ROM over the TW so the Stock Kernel that most of AT&T/VZW has to run with a locked bootloader would be able to use these features of the phone with no problems. Theres also a "Smoke Weed Everyday"Nate Dogg Audio Clip during shutdown that I accidentally forgot to remove before releasing so if at work or school you might want to delete the file PowerOff.ogg from the /system/media/audio/ui folder you can also replace the file or PowerOn.ogg for startup sound with any mp3 or ogg file just rename it to that file name...
dOPE-PSOA
@gigilie This is so nice of you to post! And great to know that there are two additional Roms we can try to further get away from touchwiz. @guut13 have you tested these out/posted them?
Murasakiii said:
@gigilie This is so nice of you to post! And great to know that there are two additional Roms we can try to further get away from touchwiz. @guut13 have you tested these out/posted them?
Click to expand...
Click to collapse
I've ran Purified for a long time on the 4.4.2, it's a TouchWiz-based ROM so it works with Safestrap just fine. It's using the Domination AOSP them package, it's a solid rom and I'm happy to see it's update I'll have to switch back.
@guut13 - I'm testing it now ~ I'll let you know how it goes so you can update the index.
NighthawkXL said:
I've ran Purified for a long time on the 4.4.2, it's a TouchWiz-based ROM so it works with Safestrap just fine. It's using the Domination AOSP them package, it's a solid rom and I'm happy to see it's update I'll have to switch back.
Click to expand...
Click to collapse
Thanks for this, I'm gonna try it out.
I would like to know what was changed as well. Ive tried multiple kernels (stock) and multiple modules, and I cant get wifi to enable on this rom.