Hi to all!
I am new in the Android world and I have a mutimidia car system with Android 2.3.4.
The problem i have is to install new applications available on the playstore like Viago.
This application requires at least Android. I have the Android 2.3.4 ROM soucecode and my doubt is if can i make a compilation of the ROM, to upgrada to Android 4 just modifying the sourcecode of the ROM i have.
Or if can i use any other V4 stock ROM, and add the kernel i have and cook it together.
Thanks in advance.
c_verri said:
Hi to all!
I am new in the Android world and I have a mutimidia car system with Android 2.3.4.
The problem i have is to install new applications available on the playstore like Viago.
This application requires at least Android. I have the Android 2.3.4 ROM soucecode and my doubt is if can i make a compilation of the ROM, to upgrada to Android 4 just modifying the sourcecode of the ROM i have.
Or if can i use any other V4 stock ROM, and add the kernel i have and cook it together.
Thanks in advance.
Click to expand...
Click to collapse
Well, what you could do is modify the AndroidManifest.xml in the apk file so that the minSdkVersion is set to API 10. so it would look like this:
minSdkVersion="resource_id:0x10"
Make sure that the app does not require any features that are not in Gingerbread. I hope this helps.
rcunningham said:
Well, what you could do is modify the AndroidManifest.xml in the apk file so that the minSdkVersion is set to API 10. so it would look like this:
minSdkVersion="resource_id:0x10"
Make sure that the app does not require any features that are not in Gingerbread. I hope this helps.
Click to expand...
Click to collapse
Thanks for your quick response. I have some trouble. When I decompile the apk, i am having some errors and dont know what to do. The apk is fully functional in my s4 mini With Android 4.2. this apk (garmin viago) and apktool are not good friends. Initially there are some errors with .9.png images, i've made the Changes in the AndroidManifest.xml and then a recompiled the apk. The result: More and more errors. The only i want to do is modify the min sdk to 10. I Dont know where to follow.
c_verri said:
Thanks for your quick response. I have some trouble. When I decompile the apk, i am having some errors and dont know what to do. The apk is fully functional in my s4 mini With Android 4.2. this apk (garmin viago) and apktool are not good friends. Initially there are some errors with .9.png images, i've made the Changes in the AndroidManifest.xml and then a recompiled the apk. The result: More and more errors. The only i want to do is modify the min sdk to 10. I Dont know where to follow.
Click to expand...
Click to collapse
Trying to get a apk file from Android 4.2 to work on Gingerbread is hard. Getting a apk from ICS to work on Gingerbread is much more simple. But if you only make changes to the AndroidManifest.xml everything should work. If you have more issues, message me on XDA and I could help you a bit more. I might get marked as spam if I post on this page to much.
Related
Hi guys,
I need help. Really I have search on google again again and again but I couldn't find anything about this topic..
My government gave us galaxy (10.1) tablets instead of books. But unfortunately this tablets's OS is not a normal android 3.2; It has been customized and we can't access many applications or other thinks. So I've decided to make a new custom rom for this tablets to offer in a competition of project. I have 2,5 months for this competition and I should make this rom so I need help. I've downloaded the android source (I want to work on 4.1jb) It is 4.2gb on my ubuntu 12.04 and I don't understand anything till see your answer on stackoverflow. I read and have some knowledge about system but It is not enough.. I know c# lang and I know general coding for 4 years.
I should edit the launcher (I said desktop but I don't know how calls It..). It has programs and widgets tabs and I want to put a new tab here. And anyone cannot see programs and widgets tab without any permission. This permission will give students's tablets by teacher ('s tablet). So, students can't play anything in the lesson but when it is over, stundents can play anything what they want.. Teacher will give the permission before leaving class..
This is what I want to do.. Briefly, I want to make a custom rom but directly using android source codes.Because I think I can't make this rom with using kitchen or just editing .apk files..
Thank you for your help..
Go to chef central in XDA forums it's very interesting (read all stickies), build a good kitchen and start building. Take some CM things to build a great ROM.
Sent from my RK29 tab...
I have thought It cannot work, haven't it?
Because I want to make a custom rom with using details. Not just editing .apk packages etc.. I looked for kitchen when I begin to make costum rom but kitchens don't satiate me.
Do you think again I should look kitchens ?
dmrc1143 said:
I have thought It cannot work, haven't it?
Because I want to make a custom rom with using details. Not just editing .apk packages etc.. I looked for kitchen when I begin to make costum rom but kitchens don't satiate me.
Do you think again I should look kitchens ?
Click to expand...
Click to collapse
If you are editing the source code you are doing more than modding apks. What I recommend to you is start building a Android with main features for example low requirements. Then you start deleting all those stuff you don't need building a very small Android. Then you modify system ui like appearance and themes and you start adding those great developer community apps. Those steps are easy for start then you'll modify those great things. And if you have time you should create a project web page in Google developers and start getting support and testers. Also if you post here your Roms you'll gain experienced developer support.
Remember you are building a Android Room not a new OS. Start modding and removing not useful stuff.
If it helps give thanks ! :thumbup:
Edit: I also recommend you if it's possible to don't work with Honeycomb... If you wanna get good results use Jelly Bean or Ice Cream Sandwich.
Sent from my RK29 tab...
SferaDev said:
...Remember you are building a Android Room not a new OS. Start modding and removing not useful stuff.
If it helps give thanks ! :thumbup:
Edit: I also recommend you if it's possible to don't work with Honeycomb... If you wanna get good results use Jelly Bean or Ice Cream Sandwich.
Sent from my RK29 tab...
Click to expand...
Click to collapse
Yes, I'm just editing an android rom not making a new OS. And I'm not working on Honeycomb. I got the source of JB.
Okey, I'll start doing your thinks. But I've an idea and if you know, please help..
Yes, I don't have to edit source code and it seems very hard to do. But I thought making a new tab panel like this panels top of JB. Check it.
http://androidplus.in/wp-content/uploads/2012/08/Jelly-Bean-Apex-theme.jpg
There are apps, downloaded, widgets tab panels on top. If I can add a new panel just with coding a new app. (not editing the source), It would be a solution for me. The panel that I'll add (let's call it education panel) have to open and close with my command (the command that comes from teacher in realty). If the command doesn't let the user of tablet to switch other panels, user can't switch. The education panel is like apps panel and contains some essential tools (like e-book, notepad, some videos about education etc.). Do you have an idea how can I do? or can I do this with just an application?
Please give me knowledge.. (Again I don't have to edit source code (like you've said) if I find this quests answer.)
Ok let's remember how Android it's divided...
I think you must modify for this launcher and systemui, if I'm not wrong. You must deodex the files inside the app package to build the eclipse project.
Good to know you aren't working with Honeycomb
Sent from my RK29 tab...
I was reading out in Android Dev forums and those links are useful to you:
http://forum.xda-developers.com/showthread.php?t=1732635
http://forum.xda-developers.com/showthread.php?t=1814441
Click to expand...
Click to collapse
Sent from my RK29 tab...
Got it. Thank you.
I was (am) busy for this job so I can answer now
dmrc1143 said:
Got it. Thank you.
I was (am) busy for this job so I can answer now
Click to expand...
Click to collapse
For anything you need !
Sent from my RK29 tab...
The first thing I want to say is that my English is not really good. I hope you understand my questions.
I have an idea for a new Android rom, but I'm faced with a dilemma. I want to have as much as possible supported devices, so I also can just build a launcher apk which can be installed through Google Play. In this way all mobile devices with the minimal platform version can use it. The biggest problem is that I don't only want a replacement for the application launcher but also the notification drawer and everything else. Is it possible to replace them also? I don't think so, so I think I'll work on a custom rom.
The next problem is which base rom I would use if I really build a custom rom. It's most likely to use AOSP as base because it's clean. The question is which version of AOSP: Gingerbread, Ice Cream Sandwich, or the newest version Jelly Bean. You would probably say Jelly Bean because this is the newest version. The problem is the phone support. Gingerbread is supported on most phones. If I build ICS or JB the phones which are supported by Cyanogenmod are easy to support, because I can use their device files. The only problem is that my phone, the Samsung Galaxy Gio is not officially supported and the unofficial port is not really stable. I don't think it's a big problem to use this device files and just wait till the developer makes it more stable, but I don't know for sure.
The last thing I want to know is if it's really that simple to support multiple devices. If I read tutorials about porting existing roms to your device they all say you just have to add your device files to the source and compile it. But they never say something about the kernel. Most devices need another kernel because their hardware is different isn't it? Please explain me how this works.
I'm sorry about this hazy story, but please help me before I make wrong choices. Thanks on purpose.
Wietse
WietsedeVries said:
The biggest problem is that I don't only want a replacement for the application launcher but also the notification drawer and everything else. Is it possible to replace them also? I don't think so, so I think I'll work on a custom rom.
Click to expand...
Click to collapse
These changes you are talking about can be done. They are system changes so not supported by the android app installer.
Eg: Your notification drawer, status bar are part of SystemUI.apk. The source for this is can be found in the AOSP source code under android/frameworks/base/...
You can make your modifications, compile it into an apk and then make a flashable zip to replace the current one (or push it via a rooted adb console).
or you can compile the entire source code into a flashable zip (eg CM7,9 etc..) and use it a replacement ROM with your modifications.
This is the line between an application under the android runtime and the android runtime itself.
these files, under framework are part of the OS. so to provide a customized version of the operating itself is what people like to call ROMs.
Now ROMs (like any OS) are device dependant. Windows has the code to run in a lot of different hardware configs, but android aims to be small. It should have only the minimum required code to efficiently run itself on a device.
Thats the kernel. The kernel communicates with the hardware and so the rest of the hardware can happily talk to a working kernel and expect the hardware to function as advertised. Kernel is a simple program which goes into the RAM on system start and sits there directing the operation of the phone.
Kernel devs work on making sure the hardware and the android runtime work perfectly together. Now, in this imperfect world, not all sources are open, even though they should be. and therein the issue lies.
If you want to compile android from source and make sure it works on your phone, first you need to make sure you have the kernel with all the changes(patches) to it made by the vendor (chap who made the phone and bullied you into buying it) to get it working on your hardware.
If you dont have that, you have to do it yourself. Or wait for someone else to do it.
once you can compile android and get it working on your phone with all the itty bitty hardware working A-OK.. then you can browse through the source, make changes as per your individual requirements and compile it into a ROM.
see the changes to the OS are separate from the changes to the kernel. The kernel changes are for hardware-software interaction so they are phone SPECIFIC.
but changes to your custom android OS (ROM) can be "cherry-picked" from other ROM/gerrit/AOSP/CM/AOKP sources and put inside your own source tree to get included in your build.
so if you have all the device / kernel stuff from a working android distribution, you can take the source of another android distribution and swap the device stuff into it and see if it works.
hope this helps.
wingie6200 said:
These changes you are talking about can be done. They are system changes so not supported by the android app installer.
Eg: Your notification drawer, status bar are part of SystemUI.apk. The source for this is can be found in the AOSP source code under android/frameworks/base/...
You can make your modifications, compile it into an apk and then make a flashable zip to replace the current one (or push it via a rooted adb console).
or you can compile the entire source code into a flashable zip (eg CM7,9 etc..) and use it a replacement ROM with your modifications.
This is the line between an application under the android runtime and the android runtime itself.
these files, under framework are part of the OS. so to provide a customized version of the operating itself is what people like to call ROMs.
Now ROMs (like any OS) are device dependant. Windows has the code to run in a lot of different hardware configs, but android aims to be small. It should have only the minimum required code to efficiently run itself on a device.
Thats the kernel. The kernel communicates with the hardware and so the rest of the hardware can happily talk to a working kernel and expect the hardware to function as advertised. Kernel is a simple program which goes into the RAM on system start and sits there directing the operation of the phone.
Kernel devs work on making sure the hardware and the android runtime work perfectly together. Now, in this imperfect world, not all sources are open, even though they should be. and therein the issue lies.
If you want to compile android from source and make sure it works on your phone, first you need to make sure you have the kernel with all the changes(patches) to it made by the vendor (chap who made the phone and bullied you into buying it) to get it working on your hardware.
If you dont have that, you have to do it yourself. Or wait for someone else to do it.
once you can compile android and get it working on your phone with all the itty bitty hardware working A-OK.. then you can browse through the source, make changes as per your individual requirements and compile it into a ROM.
see the changes to the OS are separate from the changes to the kernel. The kernel changes are for hardware-software interaction so they are phone SPECIFIC.
but changes to your custom android OS (ROM) can be "cherry-picked" from other ROM/gerrit/AOSP/CM/AOKP sources and put inside your own source tree to get included in your build.
so if you have all the device / kernel stuff from a working android distribution, you can take the source of another android distribution and swap the device stuff into it and see if it works.
hope this helps.
Click to expand...
Click to collapse
Thank you very very much for your explanation! It's a pity it's impossible to hit multiple times "Thanks".
I think I'm going to make a modified SystemUI.apk but you didn't tell the application launcher is also in this file. Did you just forget this or is this stored in another file/folder? And the lock screen? And I want also to replace the boot animation if it's possible.
If I take the source files of the SystemUI.apk of AOSP ICS, does this work on every phone running ICS? Included CM, AOKP and other (smaller) custom roms? And my last question: Since SystemUI.apk a apk file is, is it possible to edit these files through Eclipse and build it in Eclipse? Or do I get errors?
//Edit:
Still another question: How much work is it to, as example, port a modified Gingerbread SystemUI.apk to ICS? (Or vice versa)
WietsedeVries said:
Thank you very very much for your explanation! It's a pity it's impossible to hit multiple times "Thanks".
I think I'm going to make a modified SystemUI.apk but you didn't tell the application launcher is also in this file. Did you just forget this or is this stored in another file/folder? And the lock screen? And I want also to replace the boot animation if it's possible.
If I take the source files of the SystemUI.apk of AOSP ICS, does this work on every phone running ICS? Included CM, AOKP and other (smaller) custom roms? And my last question: Since SystemUI.apk a apk file is, is it possible to edit these files through Eclipse and build it in Eclipse? Or do I get errors?
//Edit:
Still another question: How much work is it to, as example, port a modified Gingerbread SystemUI.apk to ICS? (Or vice versa)
Click to expand...
Click to collapse
Only way is through exchanging the png files since porting the whole .apk is impossible.
Sent from my Jelly Beaned Ace
Thanks for the answer. And do you also know the answers of the other questions?
Sent from my GT-S5660 using xda app-developers app
WietsedeVries said:
If I take the source files of the SystemUI.apk of AOSP ICS, does this work on every phone running ICS? Included CM, AOKP and other (smaller) custom roms? And my last question: Since SystemUI.apk a apk file is, is it possible to edit these files through Eclipse and build it in Eclipse? Or do I get errors?
//Edit:
Still another question: How much work is it to, as example, port a modified Gingerbread SystemUI.apk to ICS? (Or vice versa)
Click to expand...
Click to collapse
There are two roads you can go now - one is use apktool to *decompile* apk the apk file that you've taken from your phone, it doesnt convert the app to java source code but java bytecode in .smali files (like an assembly version of the source) but you will have access to the resource files (xml, images etc..) so you can replace them and create some new themes.
http://forum.xda-developers.com/showthread.php?t=1814441
http://forum.xda-developers.com/showthread.php?t=1760133
And no - a GB systemUI.apk will *NOT* work on ICS. It is very probable that any changes you make through any of these methods can brick you phone. So make sure you have CWM and a nandroid backup.
If you want to add/edit functionality within the source code of systemUI.apk, you need to learn how to compile Android from Source. i would suggest getting hold of the CyanogenMod source tree for your device and playing around with it.
Ginger bread is CM7 and ICS is CM9.
http://forum.xda-developers.com/showthread.php?t=1552090
once you have the full source tree, you'll find a folder called android/frameworks/base/core/...something../systemui/..
this will contain the javasource code for your application. Here you can edit stuff to your hearts content!
Note that this cannot be compiled standalone by eclipse. The Android build system must be used to compile this (cuz its a system app).
a nice resource i used when i was doing the same thing :laugh:
http://iserveandroid.blogspot.in/2011/01/how-to-implement-your-own-status-bar.html
cheers and have fun.
There is currently a patch for true Tablet UI on the Nexus7 Development that has worked successfully. Link is here. The following is a quote from the original thread:
Intro
Goal of thread is to share details around how the trigger for Phone UI/Phablet UI/Tablet UI works, and provide a dpi independent patch for tablet ui. Hopefully this also eliminates the misinformation that changing lcd density is the only way to get Tablet UI.
What's "true" tablet UI vs what is called tablet UI in many roms? The Tablet UI actually defines how some apps work (e.g. dual-paned settings like in the screenshots below) vs the other solutions that simply draw the standard Nexus UI with tablet navigation/system bars.
The 'Triggers'
In 4.1.x, there are two files that need to be modified:
PhoneWindowManager.java, located in frameworks/base/policy/src/com/android/internal/policy/impl contains the code that determines which UI to present. During compile this is a part of android.policy.jar
WindowManagerService.java, located in frameworks/base/services/java/com/android/server/wm contains code that specifies the lowest DP settings and has the system select from either sw600 or sw720 presentations. It is a part of services.jar
Click to expand...
Click to collapse
Basically, I'd like to modify this to work on a 4.2.1 AOSP ROM on the Nexus10 (flashing the Nexus7 patch on the Nexus 10 leads to a bootloop). The OP shows what modifications can be made in his thread so I'm wondering how I can port this to a Nexus10 ROM. I've used APKTool to break down the "android.policy.jar" file and looked through the smali files hoping to simply edit the corresponding lines but I was unable to locate it. Apparently there's more to it than that. Any thoughts on how to create a flashable zip to patch these files?
brGabriel said:
There is currently a patch for true Tablet UI on the Nexus7 Development that has worked successfully. Link is here. The following is a quote from the original thread:
Basically, I'd like to modify this to work on a 4.2.1 AOSP ROM on the Nexus10 (flashing the Nexus7 patch on the Nexus 10 leads to a bootloop). The OP shows what modifications can be made in his thread so I'm wondering how I can port this to a Nexus10 ROM. I've used APKTool to break down the "android.policy.jar" file and looked through the smali files hoping to simply edit the corresponding lines but I was unable to locate it. Apparently there's more to it than that. Any thoughts on how to create a flashable zip to patch these files?
Click to expand...
Click to collapse
haha i saw your post to my rom thread and this is exactly what i tried to do!
the thing is when you decompile precompiled java code you get the assembly and actually have to edit the opcodes. i tried doing that and failed (bootloop). I was so frustrated because i spent like 6 hours for nothing and decided to learn how to build AOSP from scratch. When i succeeded i posted my rom
schnip said:
haha i saw your post to my rom thread and this is exactly what i tried to do!
the thing is when you decompile precompiled java code you get the assembly and actually have to edit the opcodes. i tried doing that and failed (bootloop). I was so frustrated because i spent like 6 hours for nothing and decided to learn how to build AOSP from scratch. When i succeeded i posted my rom
Click to expand...
Click to collapse
Haha, well it was a noob "shot in the dark" attempt on my part. Going to start looking into building from scratch so I can take care of business on my own instead of having to rely on others. I don't mean that in a negative sense, I'd like to be able to contribute to the community one day.
Anyway, thanks for your work, schnip!
Hi All,
I need to get APK from AOSP (a 4.2.2 Browser in particular), I have an Android SDK with synced 4.2 branch. Is there a way to extract just one APK or do I need to make a ROM?
Thanks in advance!
yes u can do so...
Summer Son said:
Hi All,
I need to get APK from AOSP (a 4.2.2 Browser in particular), I have an Android SDK with synced 4.2 branch. Is there a way to extract just one APK or do I need to make a ROM?
Thanks in advance!
Click to expand...
Click to collapse
u can extract apk code but if u try to build through ecllipse then it wont compile because of missing libraries that are only available in full source...
just look in Android.mk
and try to satisfy the needed libraries...
So I really like google dialer and have a Samsung s5. Now the new lollipop dialer or the google dialer 2.0/2.1 won't install on a tw ROM as it would appear. So I was thinking if I could make my own build from the source I could have the dialer I want without losing the tw features. So I have successfully clone the source to my PC and imported it into android studio as a project. Every time I try to build or try to produce an apk I have 31 errors stating ”no resource...” in the style.XML. I have tried to find a guide that would help me to build an apk from source with no avail. So I am curious to what I'm missing? Some direction would be greatly appreciated.
Do you have the Android sdk installed? Even then it wont install. You have to have it as a system APP and then you will lose the TW features of the dialer.
zelendel said:
Do you have the Android sdk installed? Even then it wont install. You have to have it as a system APP and then you will lose the TW features of the dialer.
Click to expand...
Click to collapse
Well I do have SDK installed.
Ok and it is updated? I would track down the errors and just fix what is missing by comparing it to a pre-built apk