Related
Sorry if this has been asked, but I checked a lit of the q&a but is there any hope or any developers working on ICS for us? And because I don't know much why is it hard to port to the sgs 4g?
Sent from my SGH-T959V using XDA App
An entire kernel needs to be built from practically scratch... Its a tonnnn of work. And our GB source JUST came out...
Sent from my SGH-T959V
OK sorry, like I said I don't know much and just was curious. Thank you for the info tho
Sent from my SGH-T959V using XDA App
tehgyb said:
An entire kernel needs to be built from practically scratch... Its a tonnnn of work. And our GB source JUST came out...
Sent from my SGH-T959V
Click to expand...
Click to collapse
Really? I know some (almost all except the very newest ones) of the Motorola phones have completely locked boot loaders which prohibit any unauthorized kernel from being loaded. Take for example, the Milestone and the Milestone xt720- they were forced (figuratively speaking) to build roms for Froyo and Gingerbread off of the same, crappy kernel that was released with Eclair. They have done a lot, it's far from stable. Which surprises me considering how bad the phone was, how few people got it, and the general negative attitude that tends to flow through Xda.
I don't know much about it- for example, once the kernel is built for gingerbread, does a new one need to be built, or can that kernel be repurposed?
How about building a Gingerbread Kernel ( CM7 based )
Now that they have finally released a Gingerbread source for the 4GS, It would be nice to have a CM7 build. I know the Devs are busy with ICS, or other products, but if one would be willing to work with me, I'd be willing to make a jab at it. I can currrently build the released kernel, but something is missing that I can not get the zimage to successfully load. It is also smaller in size. The only referenced web discussion I could find was for the I9003 series and there are files mentioned that are not part of the 4G. Any help would be appreciated.
mccabet said:
Now that they have finally released a Gingerbread source for the 4GS, It would be nice to have a CM7 build. I know the Devs are busy with ICS, or other products, but if one would be willing to work with me, I'd be willing to make a jab at it. I can currrently build the released kernel, but something is missing that I can not get the zimage to successfully load. It is also smaller in size. The only referenced web discussion I could find was for the I9003 series and there are files mentioned that are not part of the 4G. Any help would be appreciated.
Click to expand...
Click to collapse
Oh trust me, devs are looking at cm7. I know I am, like its a big New York steak!
But its going to be a while, unless you can employee me to work on it. Otherwise... Gotta pay the bills before I have fun.
Sent from my SGH-T959V using xda premium
I know that and realize other priorities make everyones time valuable. I am trying to get up to speed and just need a little bit of help getting the base kernel to build. I have successfully built the CM7 in the past for the captivate, but this is the first time for an raw, untouch source release from samsung.
Thanks for your input.
Also, just to note. There are multiple kernel devs here.
Still waiting for drhonk to release some Bali goodness.
My kernel has a different goal and approach from drhonk's. Search the op of my kernel thread for 'plan'.
As usual, all code is GPL and is available on github (see my signature), so if you want to learn or help out, start with the source.
Sent from my SGH-T959V using xda premium
finch8423 said:
Really? I know some (almost all except the very newest ones) of the Motorola phones have completely locked boot loaders which prohibit any unauthorized kernel from being loaded. Take for example, the Milestone and the Milestone xt720- they were forced (figuratively speaking) to build roms for Froyo and Gingerbread off of the same, crappy kernel that was released with Eclair. They have done a lot, it's far from stable. Which surprises me considering how bad the phone was, how few people got it, and the general negative attitude that tends to flow through Xda.
I don't know much about it- for example, once the kernel is built for gingerbread, does a new one need to be built, or can that kernel be repurposed?
Click to expand...
Click to collapse
you seem to be forgetting that every device except for the SGS1 series takes a boot.img this makes it a lot easier to do things because of the partition layout. sgs1 series uses zImage with initramfs, and has a BML/RFS file system. Not ext4, mtd, yaffs2, ext3...but a **** file system.
krylon360 said:
you seem to be forgetting that every device except for the SGS1 series takes a boot.img this makes it a lot easier to do things because of the partition layout. sgs1 series uses zImage with initramfs, and has a BML/RFS file system. Not ext4, mtd, yaffs2, ext3...but a **** file system.
Click to expand...
Click to collapse
Yea, don't sweat this quite yet, Krylon360
I say we work on the cwm that converts to ext4 like epic4g, like you'd suggested in irc. I already have some code and tests in place to convert to mtd. It's just not in any kind of stable/usable/releasable form yet. It's still early code.
When (hopefully soon) I get time, and hopefully an email back from chipworks about some info I need, I'm going to get u-boot rolling. It's hard for me to explain all the benefits of this now, but some snippets:
fastboot mode (say, flash an mtd partition like: fastboot flash <partition name> <file>)
android usb gadget support (adbd) in u-boot (say to have early console access at the bootloader), and plenty of other goodies.
many other things I just don't have time to list, on top of the fact that we can now control the bootloader...
doing the auto conversion is cake. it's just a bit inside init.rc that tells it to run a script in /sbin, that script is just a quick conversion to ext4. as long as /system, /data, and /cache have the ext4 mounting bit in init.rc, and the ext4.ko is in /lib/modules, it should would just fine.
I'll get the script while Im at work tomorrow.
Krylon360,
you mentioned the initramfs being combined with the zimage. Can you shed some light on how this is done?
bhundven,
Thank you for your help. I will be checking out your source to look over and looking at your forum. Thanks Again!
I know everyone has prob said this. But I'm willing to test betas and such for the sgs4g. Let me know if I can. Thanks
Sent from my SGH-T959V using XDA App
I have picked up an old project I was working on, getting Eclair on our phones.
Now you might think, why Eclair, it is much older than Froyo and we already have Gingerbread!?
The answer is simple, just because we do not have Eclair roms for our phones
Some people here think newer is always better, but that is not always the case
Eclair is already booting, but I have some FC's and launcher does not work correctly. Neither any other things work.
I was trying to get a logcat, but could not connect using adb.
Perhaps someone else can give me a solution for enabling adb?
What did I use to get eclair booting up?
Froyo bootimage
Compiled Eclair using Froyo-libs and kernel.
If you want to take a look at it, here is a pre-pre-alpha where nothing works
It is not the latest, because I'm already solving some problems.
Reserved for future use
Why are you doing this?????
Raffy 97 said:
Why are you doing this?????
Click to expand...
Click to collapse
Damn ---^^^open your eyes wide n read d first post!
Sent from my LG-P500 using Tapatalk
First: Congrats
Second: Provide some logcat,maybe you have same problem as mine in OMFGB (missing resources in apks)
Third: Upload to your gitHub,I'll have a look
BTW: Could you check if you have any /build/core/kernel.mk? Really getting mad with that error on CM6.
Could not get any logcat
But it's solved
Launcher is working now!
Updated build.prop, checked if some files existed, but some were missing.
Guess I forgot something in device-files
Now working on sd-card mounting, gsm and wifi, if these are fixed I will provide an updated zip (this zip contains generic build.prop )
_Arjen_ said:
Could not get any logcat
But it's solved
Launcher is working now!
Updated build.prop, checked if some files existed, but some were missing.
Guess I forgot something in device-files
Now working on sd-card mounting, gsm and wifi, if these are fixed I will provide an updated zip (this zip contains generic build.prop )
Click to expand...
Click to collapse
Non-working RIL could be caused from three things:
You missed LG services into makefiles/.rc files (if you want I can PM you some strings to add to .rc files)
Wrong libs (easy to check)
Non-prelinked libraries (define TARGET_PRELINKER_MAP (or some like that) into device_thunderg.mk and modify prelink-linux-arm-msm7xx7 or some like that with names of unlinked libs. You can see what stuff isn't prelinked with a debugging-enabled linker you can find into Swift-sense Mur4iK GT540 post. For prelink address,use google because I don't know
Would this have any actual speed benefit?
Sent from my LG-P500 using Tapatalk
You will absolutely encounter speed differences with Gingerbread.
You will even have more space available, romsize is rather small
_Arjen_ said:
You will absolutely encounter speed differences with Gingerbread.
Click to expand...
Click to collapse
yes performance will be 2x(low) xD
If you can't contribute anything usefull, do not react here, I was glad SWEATTAIMI has stopped with it after many warnings and now you start
Anyway, Eclair is more smooth than Gingerbread on our phone (at least this version)
ccdreadcc said:
yes performance will be 2x(low) xD
Click to expand...
Click to collapse
Reply to my private message
Sorry for offtopic
Sent from my LG-P500 using XDA Premium App
CAF Code right?
BTW,Did you build kernel together with the system? If so check your kernel.mk into /build/core. I'm getting mad at it.
Sent from my LG-P500 using XDA Premium App
No, this one is just AOSP with some LG crap
And booting using original LG Froyo kernel for now
Seems most compatible
Perhaps later a custom kernel will be used
Sorry for this off topic, but, good job and good luck ^_^ i hope you can successfully do this i loved the older builds of android an would love to go back to it, i wish i could help in some way and this is the best i can do :3 but good luck
What's up with RIL Arj?
_Arjen_ said:
If you can't contribute anything usefull, do not react here, I was glad SWEATTAIMI has stopped with it after many warnings and now you start
Anyway, Eclair is more smooth than Gingerbread on our phone (at least this version)
Click to expand...
Click to collapse
whaa xD what now lmao,
good to see we can use eclair hope the look is as i remember D:
It is still as simple as Eclair is, it still uses the KISS principle
_Arjen_ said:
It is still as simple as Eclair is, it still uses the KISS principle
Click to expand...
Click to collapse
It didn't boot for me so i were not able to test
Sent from Mexico
The one posted here just boots to UI but launcher etc FC. (that is why it is called pre alpha)
Got one with working launcher now, but spent some time on OMFGB with Bytecode and CM9.
As soon as all is working I will release a beta.
Hi,
Nvidia has just release binary and tools to build ICS ROM for Tegar2 plateforme...
http://developer.nvidia.com/tegra-resources
Bye
looks like (a lot of) the stuff needed to get our own built AOSP image running properly on the TF101.
Who knows, we might see a proper ICS rom before Asus releases their own .
I cant wait to see a ics-rom on my TF101!
Sent from my Galaxy Nexus using xda premium
Ohhhh... Nice.... I'm new around here does the transformer have a dev that build aosp roms from source (not kanged)
That page has been around forever and doesn't have what is necessary to get AOSP on pretty much anything.
There's been a few accounts posting that all around the same time frame the last few days all over the Tegra based device forums.....hmmmmmm.
thanks for this!reading ics 3ad it seems that it isn't so usefull...(http://forum.xda-developers.com/showpost.php?p=21768082&postcount=361)what are you think about that?
They posted an ICS device image for ventana. We can pull the required binaries from there as a starting point rather than trying to get ICS to work with the binaries pulled from honeycomb.
I'm downloading it now.
Thanks for the post!
daoist said:
They posted an ICS device image for ventana. We can pull the required binaries from there as a starting point rather than trying to get ICS to work with the binaries pulled from honeycomb.
I'm downloading it now.
Thanks for the post!
Click to expand...
Click to collapse
...we already have binaries that work with ICS, I've had builds in the public with working (and very smooth) graphics for weeks. If these ones are comparable then it'll be a nice source to pull them from, build a ROM without having to pull from a device etc. but they don't make anything any easier as you suggest.
paulburton said:
...we already have binaries that work with ICS, I've had builds in the public with working (and very smooth) graphics for weeks. If these ones are comparable then it'll be a nice source to pull them from, build a ROM without having to pull from a device etc. but they don't make anything any easier as you suggest.
Click to expand...
Click to collapse
But isn't there a new kernel in there or something to help with the (deep) sleep problems? Or is the reference board too diferent from our TF101 board?
It's all quite helpful. Cribbing stuff from a working compile is going to be easier than doing it from scratch.
dipje said:
But isn't there a new kernel in there or something to help with the (deep) sleep problems? Or is the reference board too diferent from our TF101 board?
Click to expand...
Click to collapse
There's a kernel binary, sure. It won't run on the TF101 though because as you mention it's not the same board. Ok, maybe it would run, but if it does then it'll have all the wrong peripheral setup etc. The source for the kernel is (presumably) the same nvidia source that's been available for a while and is the basis of the TF101 kernel I've been working on, so it shouldn't be significantly different.
daoist said:
It's all quite helpful. Cribbing stuff from a working compile is going to be easier than doing it from scratch.
Click to expand...
Click to collapse
'Cribbing' what exactly? I'm not sure what you think you can usefully take from this.
paulburton said:
There's a kernel binary, sure. It won't run on the TF101 though because as you mention it's not the same board. Ok, maybe it would run, but if it does then it'll have all the wrong peripheral setup etc. The source for the kernel is (presumably) the same nvidia source that's been available for a while and is the basis of the TF101 kernel I've been working on, so it shouldn't be significantly different.
'Cribbing' what exactly? I'm not sure what you think you can usefully take from this.
Click to expand...
Click to collapse
All the proprietary binaries/configs/etc. The sort of stuff we'd pull via extract-files.sh. Right now you've done an excellent job building it up from what we had in honeycomb. Now we have known-good files from ICS.
daoist said:
All the proprietary binaries/configs/etc. The sort of stuff we'd pull via extract-files.sh. Right now you've done an excellent job building it up from what we had in honeycomb. Now we have known-good files from ICS.
Click to expand...
Click to collapse
Well, no. The _only_ things that I intend to use binaries for are the graphics drivers and bluetooth firmware. Bluetooth firmware doesn't care at all which version of android you're running, so we can ignore that. Which just leaves graphics drivers, which are already taken from an ICS ROM (fortunately the TF101 isn't the only tegra 2 tablet!).
This thread is no longer active. Jomeister plans to continue work on Evervolv. He will open a new thread for that purpose.
Introduction
The purpose of this thread is to coordinate work on the AOSP-based Evervolv 2.2 ROM for Skyrocket (and its sister, T989).
Skyrocket is not an officially supported ROM by Evervolv, but we have fully integrated device and vendor directories in their tree. Therefore we get fixes from the main tree and also have the ability to push fixes to Evervolv's tree. This is something we could never do when we worked directly off the Code Aurora source.
Our desire is to give the dev community a single codebase to coalesce around. Hopefully, with more devs working on the same project, we can progress faster towards AOSP.
To build, follow the instructions here (choose ev_skyrocket-eng at the lunch menu):
https://github.com/Evervolv/android
Or, the short, short version:
Run "repo status" and make sure you have no local mods.
Run "repo sync" and make sure it completes without error.
Run "rm -rf out" to remove any old compiled stuff
Run ". build/envsetup.sh" to set up your environment
Run "lunch ev_skyrocket-eng" to select the target
Run "make -j4 otapackage" (adjust -j option to match your # of processors)
What works:
2D/3D graphics, hw accel of gui, bluetooth, gps, nfc, wifi, sdcard (int+ext), MTP/PTP over USB
What doesn't work:
audio, calls, camera, cell data, sms, anything else you can think of
Issues are being managed on Github:
https://github.com/Evervolv/android_device_samsung_skyrocket/issues
Want a ROM link?
Then follow the instructions to build a ROM! The point, at this time, is to get devs involved in the process. The ROM is not ready for anyone to try out or use at this point. There are many problems left to solve.
Want to help?
Are you a dev with a Skyrocket and a burning desire to get AOSP for your phone? Please, check out Evervolv and start debugging! The Github Issues link above is a great starting point.
Jomeister and RaverX3X graciously agreed to join forces here. We hope other devs join too!
Current Dev Contributors:
jomeister15
RaverX3X
topprospect
Credit and Thanks:
Xboarder56 for the original Evervolv Skyrocket device tree
romracer for the unsecure mods to the ICS kernel
Changes Log:
04/11/12: Posted succint build instructions
04/11/12: Fixed unstable-ness of GUI (link)
04/06/12: Build now boots on its own boot.img (link)
this is on 4.0.4 now?
Sent from my GT-P7510 using XDA Premium HD app
BaconStep said:
this is on 4.0.4 now?
Sent from my GT-P7510 using XDA Premium HD app
Click to expand...
Click to collapse
yes because google has released 4.0.4 sources and ota updates to nexus.
wali01x said:
yes because google has released 4.0.4 sources and ota updates to nexus.
Click to expand...
Click to collapse
Sweet!
Sent from my GT-P7510 using XDA Premium HD app
Looks great, will try building/debugging when I get my Ubuntu box up again!
Sent from my SAMSUNG-SGH-I727 using XDA
I'll be helping out as well, just got me a T989. I was working on cm9, but I'll switch to this. Hope I can help.
This is obviously a stupid question, and probably not the place to be asking it, but it is going to be asked anyway so.. I understand what the device tree is, but why is it not possible to pull one from the existing ICS leak?
giant420 said:
This is obviously a stupid question, and probably not the place to be asking it, but it is going to be asked anyway so.. I understand what the device tree is, but why is it not possible to pull one from the existing ICS leak?
Click to expand...
Click to collapse
No stupid questions here. A fully compiled ROM like the ICS leak obscures a lot of the details about how to build the ROM from scratch. You have to reverse engineer a lot of what Samsung did to compile AOSP, plus how to avoid pulling in too much Samsung bloat code. Hope that helps.
more or less were going to keep as much samsung out of it as we possibly can . Yes u can kang in stuff from the leak but then that actually causes more issues in the long run then doing it right the first time ;P.
bsbachert said:
I'll be helping out as well, just got me a T989. I was working on cm9, but I'll switch to this. Hope I can help.
Click to expand...
Click to collapse
I think we as a community should still continue working on things such as CM9 and AOKP in addition to Evervolv, just to give people as many options as possible. The good thing that Evervolv device trees are very similar to those required by CM9 and AOKP, so with a few hacks here and there I'm sure we can get those building as well. I don't know about the other devs, but I definitely have enough time to collaborate on multiple projects, as long as I'm not the sole carrier.
ur killing me. I finally managed to get media server to stay up for msm8660 audio pulled from the leak with jos isotope a4 with some other libs and bins. acdb pulling audio policy was still a problem though.
This is definitely for the better though. I was uncomfortable with all those Samsung libs bins and blobs, especially after staring at them under IDA. like raver said it woulda been a nightmare later on.
This is great though, everyone on the same pile should make this go a lot faster.
im very excited for this.
What's IDA?
Sent from my SGH-T989 using XDA
Wow. This build is going to b epic! Can't wait guys. Nice work so far
LawStud3nt said:
What's IDA?
Click to expand...
Click to collapse
http://en.m.wikipedia.org/wiki/Interactive_Disassembler
crazy what u can find in those blobs. helps a lot for debugging though
all I know is I love evervolv on my nexus one its super baller... Thanks to all 3 of you guys
Sent from my SAMSUNG-SGH-I727 using xda premium
Any updates? Got ants in my pants waiting for this one!
softballjunkee13 said:
Any updates? Got ants in my pants waiting for this one!
Click to expand...
Click to collapse
Thanks for the interest.
We will post updates as they happen. Right now we are just trying to organize and get everyone on the same page.
Sent from my SAMSUNG-SGH-I727 using Tapatalk
topprospect said:
Thanks for the interest.
We will post updates as they happen. Right now we are just trying to organize and get everyone on the same page.
Sent from my SAMSUNG-SGH-I727 using Tapatalk
Click to expand...
Click to collapse
OK...enjoy the holiday as well!
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.