Hi everyone!
I found yesterday a project really cool that brings Linux to your tablet in an easy way using the chroot method. They made an app for each distro and are available on Play Store for free.
I've installed Ubuntu Small on my tablet and I'm surprised because it runs without any lag. You can use Ubuntu, BackTrack and Debian distros for now and each distro are available as:
Core (the basic Ubuntu, no GUI and only 750MB when extracted)
Small * (includes LXDE Desktop, a few programs like Chromium Browser and is about 2GB when extracted)
Full (A lot of programs including LibreOffice and has Unity, 3.5GB when extracted)
* Recommended, runs better on this tablet.
To use it you have to access the linux using VNC, it's nice because you can also access from another computer on your network.
More details and where you can download the image here: [APPS] Linux-on-Android project (incorporating Ubuntu installer)
Here's Ubuntu 12.04 Small running on my tablet and on my Mac.
Hope you all enjoy it
can it run Chromium OS?
I don't know if Chromium OS has ARM support, if it does might be possible, but idk for sure.
Sent from my Galaxy Tab 7.0 Plus using XDA Premium HD app
Does stock kernel has loop? I did everything according to instruction, but when i launch it says that loop device missing...
Forgot about busybox, problem solved.
maelfilk said:
Does stock kernel has loop? I did everything according to instruction, but when i launch it says that loop device missing...
Forgot about busybox, problem solved.
Click to expand...
Click to collapse
I was going to say that, yes the stock kernel has loop, you only need to install or update busybox.
Tried Backtrack v5, smooth as butter!
Does wifi work?
bdds13 said:
Does wifi work?
Click to expand...
Click to collapse
Yes, it does. And let me point out that you can easily switch to Android back again with no lag or whatsoever[Home button].
Wanted to ask, what for do you use ubuntu on tablet? It's great to be able to have it, but what's the point?
maelfilk said:
Wanted to ask, what for do you use ubuntu on tablet? It's great to be able to have it, but what's the point?
Click to expand...
Click to collapse
I don't know you but I like to explore what any of my devices can do, so run Linux on this tablet is a nice thing, I mean, if you want to try something new.
FMAranda said:
I don't know you but I like to explore what any of my devices can do, so run Linux on this tablet is a nice thing, I mean, if you want to try something new.
Click to expand...
Click to collapse
Yeah, it is interesting to try it out. http://www.ubuntu.com/devices/android looks promising as well.
maelfilk said:
Wanted to ask, what for do you use ubuntu on tablet? It's great to be able to have it, but what's the point?
Click to expand...
Click to collapse
Well, for one you could use it if you're a dev on devices. You can also try cracking a few wifi hotspots with it(aircrack and etc.).
Full ubutu on P1000
Hi Guys, I've been trying the full ububtu version on the P1000.
I'm using CM9 RC1, and Ubuntu runs, but very slow.
I'll give a try to the small image.
Does anyone have any tips to make it run faster?
The full build runs slow even on Tab7+. Small is the best choice.
FMAranda said:
I don't know you but I like to explore what any of my devices can do, so run Linux on this tablet is a nice thing, I mean, if you want to try something new.
Click to expand...
Click to collapse
you do realise that android is the linux kernel with a set of runtimes on top. it has a shell and a fair smattering on linux commands already.
Yes, I know that, but it isn't the Linux itself, right? It has a lot of modifications just like you said.
Android is based on Linux, linux is the base of android .
Enviado de meu GT-P6210 usando o Tapatalk 2
Hi.
First of all I want to thank to FMAranda for this effort.
Second, I need a little help. I have a Galaxy Tab 2.0 7" with cyanogenmod [email protected] (Android 4.2.1)
I think that the loop devices will come included with cyanogenmod, but the script says me that the loop device is missing. Do you know any other ROM I can use that include loop devices? Or how to enable it (noob guide)? Ideally with Android 4.2.1 because my kids use the tablet too
thanks
clemare
Linux is soooooooooo 1960s
originally developed in 1969 by a group of AT&T employees at Bell Labs,
Don;t they teach you kids nothin in school??
http://en.wikipedia.org/wiki/Unix
Running a 40 yo OS. .....LMAO>>>>>>
Android is a great OS, and flashing new roms is one of the best experiences when it comes to your device
I know how to root, flash roms, kernels, and radios, but I want to know more. I'd like to get into rom development, mainly from source code.
I do have experience with computer languages. I can build a nice website in Notepad using HTML. JavaScript is no problem either. I also dabbled in CSS.
What exactly should I know to eventually know the ins and outs of rom development? What languages, PC environments, etc?
KayxGee1 said:
Android is a great OS, and flashing new roms is one of the best experiences when it comes to your device
I know how to root, flash roms, kernels, and radios, but I want to know more. I'd like to get into rom development, mainly from source code.
I do have experience with computer languages. I can build a nice website in Notepad using HTML. JavaScript is no problem either. I also dabbled in CSS.
What exactly should I know to eventually know the ins and outs of rom development? What languages, PC environments, etc?
Click to expand...
Click to collapse
You will need a Linux distro to build rom source and most of it is in Java C+ and C++
Or u can just use dsixda's online kitchen. It the UOT kitchen
QuantumFoam said:
Or u can just use dsixda's online kitchen. It the UOT kitchen
Click to expand...
Click to collapse
He asked about learning Tom development and those are not even close
Sent for a corner cell in Arkham
zelendel said:
He asked about learning Tom development and those are not even close
Sent for a corner cell in Arkham
Click to expand...
Click to collapse
Yes. But he didn't ask about making a rom from source. He could take an existing rom, modify the ui and release it as his own version :
Oh well. Who am I to contradict a senior mod
QuantumFoam said:
Yes. But he didn't ask about making a rom from source. He could take an existing rom, modify the ui and release it as his own version :
Oh well. Who am I to contradict a senior mod
Click to expand...
Click to collapse
No he didn't but what you described is coming to an end very soon.
Sent for a corner cell in Arkham
zelendel said:
No he didn't but what you described is coming to an end very soon.
Sent for a corner cell in Arkham
Click to expand...
Click to collapse
Really? The ROM kitchens are closing?
QuantumFoam said:
Really? The ROM kitchens are closing?
Click to expand...
Click to collapse
No but posting roms done this way will be. Remember this is a development site. Focusing on real development
Sent for a corner cell in Arkham
zelendel said:
No but posting roms done this way will be. Remember this is a development site. Focusing on real development
Sent for a corner cell in Arkham
Click to expand...
Click to collapse
Well you're right.
I hope op got his answer
Hey, so the best way is to jump right into development. Go and download the official AOSP tree. This side will guide you:
http:
//source.android.com/source/downloading.html
So you need to be able to handle a linux machine, should know about java and c/c++, git and repo. Do not get frustrated it is really a lot of stuff that you will need on your way. But it is worth it.
I recommend that you start with stock AOSP as this is staight forward and should build stable. A google development device is a must have to verify your roms as those are official supported and as newbie you really do not want to start hacking/porting/steeling/manipulating device drivers to get things working .
If you passed this hurdles you can start to modify small parts of the system an so on...
Good luck and have fun
Much appreciation. Thanks have been given.
Sent from my iPad using Tapatalk HD
Hi all,
i own a SbkV2 TF101 (with Dock) and always found really really difficult to install Ubuntu on my little (and oldie !) tablet.
So i was thinking about a different flavour of linux. What about ArchLinux ? Debian ? LinuxMint ?
Why no threads, no one-click tool , no support for other flavor.
Ok, i understand that the kernel underlying linux is alway the same so, the drivers, once complete, should fit any distribution, but maybe there are distributions better than others for our tf101.
And, to be honest, i became so jealous about ubuntu 12.10 on Nexus7 (ok, it's tegra3 vs tegra2, but....)
Having a full, complete linux distribution working on our tablets could allow us to many real program (not android wannabe apps), like gimp, libreoffice, mail clients, and many, many others , improving productivity dramatically.
What do you think ? i'm a visionary and the real fact is that tf101 is dying ? boh any help would be appreciated !!!
TheMac
I would love to see Mint, puppy,or a few others on here as well. I tried looking into it but could never get any image to build correctly for flashing. I'd gladly test it out if its possible to flash directly from tablet, no laptop ATM.
Sent from my Transformer TF101 using xda premium
Kubuntu has a tablet ui version for omap 4
Sent from my EPAD using Tapatalk 2
cpu999 said:
Kubuntu has a tablet ui version for omap 4
Sent from my EPAD using Tapatalk 2
Click to expand...
Click to collapse
I just visited their site. None for tegra2
TheMac
i don't think this is a good place for asking that. this is not a DEV thread. Anyway, i already wrote something about this.
I have running debian in my transformer. But if you want another distro you should be able to do it. This is a good place to start:
http://forum.xda-developers.com/showthread.php?t=1476835
The thread shaola mentioned is a good place to start.
Another good place to get started working with this without nuking your daily driver and messing with dualboot is to loopmount a img file on your internal storage as your root, but flash a kernel zip modified to do this and boot it up. I've been messing with it and it works pretty well.
Heres the link to the thread (again by shaola): http://forum.xda-developers.com/showthread.php?t=1537566
You can pretty easily build an image for this kind of system. I'm working on getting an Arch image booting. I used the Arch for Arm project with a tegra2 image, and just stuck that in with the loopmount kernel. I imagine LinuxMint would be pretty easy since its ubuntu based and they share packages. So again shaola's thread is a great place to start. If I get the Arch image booting ill put it up.
@SHAOLA : Thanks ! Still hoping, anyway, for a one-click-like solution (i'm the laziest man with a degree in computer science :laugh: )
@JHOLTOM : Ok, i'll stay tuned . Thanks !
TheMac
Hey I know this isnt device specific but was just curious out of the devs using linux wat distro/version would you suggest for developement of roms. ive heard a lot use ubuntu but i know some of their newest versions are the greatest to use in this area.
stoneduser8907 said:
Hey I know this isnt device specific but was just curious out of the devs using linux wat distro/version would you suggest for developement of roms. ive heard a lot use ubuntu but i know some of their newest versions are the greatest to use in this area.
Click to expand...
Click to collapse
I'm using Ubuntu 12.10 ...there is some crashes right of the bat but nothing big enough to cause any problems building.
Latest updates seem to fix most of the misc crashes...so I'm sticking to this.
stoneduser8907 said:
Hey I know this isnt device specific but was just curious out of the devs using linux wat distro/version would you suggest for developement of roms. ive heard a lot use ubuntu but i know some of their newest versions are the greatest to use in this area.
Click to expand...
Click to collapse
Beastmode said:
I'm using Ubuntu 12.10 ...there is some crashes right of the bat but nothing big enough to cause any problems building.
Latest updates seem to fix most of the misc crashes...so I'm sticking to this.
Click to expand...
Click to collapse
It's really a preference kind of thing. I have done builds on my Mac, yes kernel too.
A build server I use has ubuntu server installed. On my own build server I use debian unstable, but again, this is my preference. I like messing with experimental stuff
I know some people prefer fedora for their builds, others use OpenSUSE, archlinux, or centos. It's really what you are comfortable with.
Supposedly there is a variant of archlinux called bbqlinux, which is supposed to have install time helpers to install the android sdk parts automatically.
Ya I ended up following a tutorial and using Ubuntu 10.04. Just got aosp source all downloaded last nite haven't got a chance to fool with it quite yet spent a lot of time with Google since found out java6 no longer supported so after about 2 - 3 hours of trying find and install all the dependencies that were not existent now I get to learn what the hell I'm doing and hope not to screw up my phone too much lol.
Sent from the deep depths of hell....
You should've followed the aosp tutorial more closely and installed ubuntu 12.04 instead... it's the most recent LTS version available.
Here is a guide you can trust (as with any other articles on xda-u), making sure you have ubuntu 12.04 64 BIT installed for most compatibility.
http://xda-university.com/as-a-developer/getting-started-building-android-from-source
FBis251 said:
You should've followed the aosp tutorial more closely and installed ubuntu 12.04 instead... it's the most recent LTS version available.
Here is a guide you can trust (as with any other articles on xda-u), making sure you have ubuntu 12.04 64 BIT installed for most compatibility.
http://xda-university.com/as-a-developer/getting-started-building-android-from-source
Click to expand...
Click to collapse
Ya I ended up going by this.
http://source.android.com/source/index.html
Last time I had installed Ubuntu I remember not being too thrilled about the new looks so thats more or less why I had chosen to go with 10.04. I'll take your advice though its been buggin me to make the upgrade and hey if I don't like it could always go back.
Sent from the deep depths of hell....
I checked out that bbqlinux that Brian mentioned. Didn't do much yet but got it installed in a virtualbox last night and everything seems to be there like adb and the android SDK and java and all that stuff installed already. Pretty light weight, runs fine inside a VM with a few dedicated cores and a few GB of ram. Didn't play around much more though yet.
If you want something better than Ubuntu use Linux Mint w/Cinnamon. Its Ubuntu based but different. It does not use Unity so that's a plus.
Sent from my SGH-T959V using xda premium
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.