Hello, I am trying to compile CyanogenMod 5.0.8 (eclair) to the mini pro.
I chose this version because it will probably have almost everything working since the latest kernel on the x10 mini pro supports eclair.
however when I try to compile the eclair branch from the cyanogenmod source I get the following error.
Code:
error: revision eclair in CyanogenMod/android_external_webkit not found
I've looked on the internet for a solution and found something about removing a line from manifest.xml, but I haven't been able to locate it. Is there no hope for porting CM5 over then?
Greetings, Mike
what manifest.xml do you mean coz every app has an manifest.xml
please give us some information about this
edit:
i think you need the manifest.xml from browser.apk
coz its a problem with the external webkit this is the browser
and if you decompile browser.apk there is an manifest.xml (like every app has xD)
edit 2:
i've attached the original 2.1 SE Manifest.xml
Thanks, but this goes beyond my knowledge.
I think I'm going to start up trying to port a nice gingerbread theme including animations and will take a look at porting CM6 over. I have owned an android tablet before so I have some basic knowledge.
Related
Hi there!
I was wondeing how to create my custom ROM using xRecovery for Xperia?
One thing I don't know how to do is to delete my google account so others have to use their own.
I could'n find any tuto arround.
Any sugestion?
Thx
You could start with modifying existing ROMs. For example:
framework-res.apk
All the apps, you can unpack the .apk's, located in /system/app/ and replace the icons.
services.jar
Much, much more.
After that, you can try making a Nexus One or Nexus S kernel from the AOSP, and if you succeed, try looking up some tutorials.
Please note that for building the AOSP source, you need a 64-bit Ubuntu (or another Linux distro) or Mac. Building on Windows is currently not supported. If you don't have a 64-bit machine, you can still build Eclair ROMs, Froyo and above is 64-bit only.
As for a custom rom, even the experienced devs have only just cracked it, sort of. You can however use the Kitchen to modify and theme an S.E rom with Zdzihu's xRecovery which is what I and others are currently doing.
Hello all,
So I remember not too long ago a lot of people were asking for touchwiz 4.
Now it's out and I haven't really seen any steps in porting it to other devices (like ours).
BUT, some people over at the Galaxy S I9000 already ported it to their devices.
So, since we can also run android 2.3.4 now, I was wondering if there was a porter around here interested in porting this.
Here's a Link To the original post at the Galaxy S forum.
I don't have much experience porting other apps (unless I can get the whole source I.E. All the Java files and XML files in original format), otherwise I would have tried it.
Dympy
I think Gaby02 try port this.
Hello
I did not try this one yet, but maybe it works:
http://forum.xda-developers.com/showthread.php?t=1061883
I linked to that post in the OP.
Already tried and didn't work :/
Dympy.
Whoops, sorry did not saw that
Try running it through Chainfire? Or am I talking **** now?
Well graphics aren't the problem.
First of all, it just won't install (Maybe because I'm on Froyo (The manifest file requires a minimum SDK version of 8, so if I'm right Froyo is capable of using it)).
If that problem can be overcome, I think the rest of the porting Would be quite easy.
Dympy.
Try pushing it to /system/app and reboot? Maybe it works then?
the current port of Touchwiz 4 on froyo is for arm v7 devices only....... so i suggest wait till marcellusbe port's cm7 and releases gingerbread AOSP.... cause then only the pngs will have to be converted... i guess......
Installed on cm7 but when I select tw it just gives a black screen with the notification bar :/
Touchwiz 4 is for ARMv7 so for the moment I think it's impossible to use it :S
i have tried all on froyo and on cm7 but no one would start i cant install it and only blackscreen
Probably, this would take an another marcellusbe to port the lib files
I'm NOT EXPERT, I'm ONLY TRING TO HELP and SORRY IF I MADE SOME MISTAKES!
I have some ideas for porting android 3.2 to Folio 100 but I can't do all myself - I need some help.
My first idea is:
To add changes made in android 3.2 system(framework, apps etc.) to our Honeycomb from SDK or Xoom and decompile zlmage inside HC kernel(if that tool existe or find it's kernel source, add changes from android 3.2 kernel and recompile it).
---------------------------------------------------------------------------------------------------------
1. This idea is really hard to realise because kernel(I don't think that tool existe) but it's convinient(we'll finish it in short period with little work).
2. For this idea first we need to add changes from android 3.1 and after that from android 3.2.
3. I NEED YOUR HELP to find WHAT ARE CHANGES and TO DOWNLOAD
THEM for adding them to OUR build(First android 3.1 changes and after android 3.2).
For system that isn't problem but for kernel it is. The most detiled list of changes can
be find at Android SDK site but I think that we can't download them.
4. I think that mblaster know a lot of kernels and compiling it won't be problem for him.
----------------------------------------------------------------------------------------------------------
My second idea is similar to first one:
To add changes made in android 3.2 system(framework, apps etc.) to our Honeycomb from SDK or Xoom and compile android 3.2 tegra kernel from
Android Git or from other sources.
----------------------------------------------------------------------------------------------------------
1. I think that this idea is the best if mblaster help us or some one else that know a lot
of kernels.
2. Google won't relise full source of android 3.2 before pushing up android 4.0 aka
Ice Cream Sandwich to shops.
----------------------------------------------------------------------------------------------------------
I can port system itself(it will be faster if someone make a list of changes) but kernel is
a problem. I don't know much about kernels and because it I post first idea.
If you have new ideas or you don't agree with me or want to help me, please, post here!
EDIT: Android 3.2 might work with our HC kernel.
Sent from my Folio3x using Tapatalk
good idea +1
Thanks.
Sent from my Folio3x using Tapatalk
Not interested?
Sent from my Folio3x using Tapatalk
nice idea..
if u write drivers and kernel change, some other developer can use your work alot.
anyone writing all the drivers for folio will make toshiba happy, as they did not do it..
so if you make all this happen and write the drivers , i am sure folio will once again be a good tablet.
the development is something that takes companies 3-6 months to do, so you will be back in december 2011 or maybe early 2012 with your release?
Can someone compile Tegra 3.2 kernel from here? I tried but without success. I'm porting system now.
I tried to unyaffs FolioComb 3xx v2.0 image bu I got 'Segmentation fault'???
I succefully unyaffsed Android 3.1 and 3.1 SDK images.
I'll try to backup it from my tablet(I have FolioComb on it)
Nice to see someone trying to update folio 100, thanks to you and people in CM7 thead.
I don´t know about compiling so I cant help. But i keep an eye in this post.
Do you know anything about system?
EDIT:Nothing
Hi all,
I am trying to compile AOSP GB for the MP but I am wondering where I get the mimmi and msm7x27 files to add. When compiling CM for a supported device you just clone the files from the CM github and run ./extract-files.sh but this doesn't apply to our Mini Pro. I have seen in paul-xxx's compiling ICS ROM topic about adding it but I am wondering if these files will work for GB or are ICS specific.
Thanks for your help,
x10man
x10man said:
Hi all,
I am trying to compile AOSP GB for the MP but I am wondering where I get the mimmi and msm7x27 files to add. When compiling CM for a supported device you just clone the files from the CM github and run ./extract-files.sh but this doesn't apply to our Mini Pro. I have seen in paul-xxx's compiling ICS ROM topic about adding it but I am wondering if these files will work for GB or are ICS specific.
Thanks for your help,
x10man
Click to expand...
Click to collapse
You need make a lot patches for using some libs from eclair rom.
For example libaudio and libcamera.
CM source have some. AOSP no.
And you need make new configuration data for AOSP.
/device/semc/mimmi
thanks paul,
I will have a go at that now. created the folder but I need to create the config now.
X10man
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.