So I am trying to port ICS to our kaisers, but the problem is I have very limited developer knowledge (actually none). As a result I am trying to port the HTC Wildfire's ics builds. But the only things I can do, is:
extract the system file out of the Wildfire build
delete a couple of files to get in down in size (the wildfire has more RAM than the Kaiser)
add the sysinit.rc file to the system file
recompress the system file to androidinstall.tar
And the furthest I have come with this method is seeing the boot logo flikkering while I still saw some of the white code on the screen.
The matter of the fact just is, I REALLY WANT TO LEARN HOW TO BUILD MY ANDRIOD BUILDS, but I don't have the knowledge or time to exactly learn the java code. So as a result I really just want to know what the keypoints are? CAn somebody please point me in the right direction?
** As an example: when you open the system file of an android build you get all kinds of folders, and from most of them I don't know what they mean, like from bin, etc, framework, lib, usr and xbin I haven't got the slightest clue of what they are there for.**
**Also I don't know what there should be changed in the build.prop and the sysinit.rc when you are trying to a build of another device on the kaiser. Are the build.prop and sysinit.rc dependent from the version of Android you are giong to run or are the dependant of the kind of device you're gonna run it or are they dependant of both??**
hom.hom said:
So I am trying to port ICS to our kaisers, but the problem is I have very limited developer knowledge (actually none). As a result I am trying to port the HTC Wildfire's ics builds. But the only things I can do, is:
extract the system file out of the Wildfire build
delete a couple of files to get in down in size (the wildfire has more RAM than the Kaiser)
add the sysinit.rc file to the system file
recompress the system file to androidinstall.tar
And the furthest I have come with this method is seeing the boot logo flikkering while I still saw some of the white code on the screen.
The matter of the fact just is, I REALLY WANT TO LEARN HOW TO BUILD MY ANDRIOD BUILDS, but I don't have the knowledge or time to exactly learn the java code. So as a result I really just want to know what the keypoints are? CAn somebody please point me in the right direction?
** As an example: when you open the system file of an android build you get all kinds of folders, and from most of them I don't know what they mean, like from bin, etc, framework, lib, usr and xbin I haven't got the slightest clue of what they are there for.**
**Also I don't know what there should be changed in the build.prop and the sysinit.rc when you are trying to a build of another device on the kaiser. Are the build.prop and sysinit.rc dependent from the version of Android you are giong to run or are the dependant of the kind of device you're gonna run it or are they dependant of both??**
Click to expand...
Click to collapse
ICS on Kaiser? Big mistake...
I know see that you have gotten it right about ics on the kaiser, but I still want to develop my own builds for the kaiser, gingerbread builds, then. So can anyone shed their light on helping me into the right direction of creating my own build from the source or porting a build from another (htc) phone??
if you want to port android start from this - take system from similar device (example click or wildfire) and follow directions from this thread http://forum.xda-developers.com/showthread.php?t=996431. Method from post #3 definitely works for Froyo and Gingerbread. If you find problem really helpful is using logcat and DDMS.
In my opinion porting AOSP ICS for Kaiser at the moment is a waste of time. Will be more problematic and you never will achieve a fast, fully operational system. BUT with Cyanogenmod9 situations can be change...
Almost there....
I have used the Official Cyanogenmod Stable release from the HTC Wildfire to port (as a test) and I have used Scoot CyanogenMod 7.1.0 RLS3 (Gingerbread 2.3.5) [07/08/11] to paste the files from into the CM for the buzz.
Michga said:
i have this one...
I'll look into the specs of wildwire and let you know if my steps would work. Just kinda busy this holiday season. But my steps were pretty simple. We have to know if this is an odex'd or deodexed version. If it is odexed version, it would be nice to deodex it first. I use Android kitchen from dsixda. The only part we need is the system folder. It has apps, etc, lib, bin and the rest...basically under the system we need to put Fresh Froyo (FF) files build.prop and sysinit.rc and move it to wildfire's system folder (these two files are required for booting)then under /system/etc you need to grab vold.conf(1) from (FF) and move it to wildfire's /system/etc. Ooops..I'll have to get back to you. Dinner time BTW, vold.conf is what loads SD card. I looked at the specs of wildfire and not sure if it works since it has a 7225 processor and 5 megapixel but it's worth a try. Then /system/etc, copy ppp and passwd from liquid's kernel and put it in that folder (like permissions)(2). Compare the folders with Fresh Froyo and if something is missing from Fresh Froyo to wildfire. Copy wifi folder (don't copy ppp folder, delete it if wildfire ROM has it). Now lets go to system/lib. Copy the following files from Fresh Froyo to wildfire libaudio.so, libaudiopolicy.so (audio drivers) libcamera.so libcamera_client.so libcameraservice.so (camera drivers) libgps.so (gps driver) libhtcgeneric-ril.so (phone driver) libicudata.so. Then copy egl folder to hw folder and bluez-plugin folder. Now go to system/modules and delete all files and get modules from l1q1d's latest kernel(3) and put it in the system/lib/modules folder. Then go to system folder and copy bin folder, media folder, xbin and usr folder to wilfire system. That's it. Save the system folder as androidinstall.tar and see how it goes. Goodluck.
Click to expand...
Click to collapse
So I have tried the method of post 3 of the link, but all I get is the kaiser to boot in Android, but it never stops booting, the infinite bootloop. I believe the cause for this bootloop to be the sheer size of the androidinstall.tar(as jholtom already explaines in his post in this thread). It at its least becomes 150 mb. I can't get it any smaller, because I need to add the xbin file of Scoot's Cyanogenmod 7.1 for Kaiser, which is 67 mb of size. While the official Cyanogen Wildfire rom also is about 67 mb of size.
Also some other problems
(1)vold.conf: I can only find vold.fstab does this matter?
(2)how do i extract passwd from liquid's kernel? And do I need to put this in the permissions folder?
(3)Instead of the latest files as posted by Michga, I have used the files from the update.zip provided by Scoot in his kernel with separate cache thread: http://forum.xda-developers.com/showthread.php?t=1152219
You need strip the system as much as possible. cut out the unnecessary applications that take space and are not required to work (example: radiofm, rom manager, thememanager), tts voices, rings even some libraries - try to compare catalogs from Scoot_CyanogenMod_7.1.0_RLS3 and wildfiresystem. Strip unnecesary files, copy all the missing files. If your androidinstall.tar reach size below 100mb should be ok with standard partitions. But you can always enlarge the partitions in atools.
What do you mean that xbin have 67mb? It have about 7mb
As you can see Michga wrote this for Froyo so some files will vary. (1) copy only volf.fstab (2) may be unneeded for scoot's kernel- i'm not copy this and system works (3) you can use files from scoot 7.1 RLS3 - these are the same modules as in the update.
Install the android sdk on computer, run DDMS and plug the Kaiser. You will then be able to see what at the time the phone is doing and what is causing the problem.
Sorry for my english
Well, also the strangest thing is that I redownloaded Scoot_CyanogenMod_7.1.0_RLS3 build from this thread, http://forum.xda-developers.com/showthread.php?t=948134, and extracted the file to my desktop and the file is 148 mb in size of which the xbin folder is 69.6 mb in size. How is that possible? I am using Windows 7 x64 and I am extracting the file with Winrar. And when I use 7-zip to get the system file back to androidinstall.tar, this file is also 148 mb, BUT THIS FILE I AM ABLE TO INSTALL....
I am using 7zip only (also Win 7 x64) and extracted RLS3 have 84.3MB. Strange...
hom.hom said:
Well, also the strangest thing is that I redownloaded Scoot_CyanogenMod_7.1.0_RLS3 build from this thread, http://forum.xda-developers.com/showthread.php?t=948134, and extracted the file to my desktop and the file is 148 mb in size of which the xbin folder is 69.6 mb in size. How is that possible? I am using Windows 7 x64 and I am extracting the file with Winrar. And when I use 7-zip to get the system file back to androidinstall.tar, this file is also 148 mb, BUT THIS FILE I AM ABLE TO INSTALL....
Click to expand...
Click to collapse
Impossible, you can't install 148 MB file because System partition on Kaiser is just 120 MB!
So my first problem with the immens build sizes have been solved by using 7zip for every step in my android adventure instead of Winrar.
But know the real problem the booting problem. I ran ddms and the conclusion I get is:
system_process Audiosystem AudioPolicyService not published, waiting....
....
....
HTC Acoustic can't open /dev/htc-acoustic -1
AudioHardware Could not set acoustic parameters to share memory -1
I already googled this problem and the solution is supposed to be to create an android dummy audio driver, but as I said already my knowledge is really limited. So i don't know how to create an android dummy audio driver.
**I also uploaded the warn screen of the ddms...**
did you copy libaudio.so, libaudiopolicy.so (and i'm not sure now - libaudioflinger.so?) from scoots build?
First of all, THANK YOU!!!!
**I just needed to copy all the libaudioxxxx.so files from Scoot's build to the Wildfire's build.**
I am able to boot Zerorom 1.0 from the HTC kaiser now. But there are still a couple of quirks in the build, like the missing statusbar, the not working wifi and the screen looks like it has the wrong panel type in this build. While with Scoot's build it's A-ok.
Do you have logs from ddms?
Maybe you cut too much. Of course you adjust build.prop to our phone. To resolve graphic problems make sure that you still have SystemUI.apk and replaced folders hw and egl from scoot's build. To wifi make sure that you replaced in etc: firmware and wifi folder. If this not help swap libhardware-legacy.so
These are the files of the ddms log and the files which I used to port the official Cyanogenmod release of the HTC Wildfire to the HTC Kaiser. The problems are a flikkering screen it goes on and off all the time, improper (or actually none proper) detection of touch and no wifi.
**I needed to separate the files I copied into two separate folder, system1 and system2, because otherwise I couldn't upload it to the site. I hope that this gives a proper insight in what I have exactly done. Before I copied this files, I deleted the original ones from the Wildfire's build.**
well... What am I to do with it? Download zerorom, merge with this and see what's wrong? I dont know what you do to get tar smaller and what contains folders from porting system. Im think that You better create a new thread called example Zerorom alpha port 0.1 and upload androidinstall.tar to mediafire or somewhere. Then I or someone else see or flash this to phone and tell you what is missing and why libskia.so and launcher still crashing
I've been watching the progress here and I have a few things to point out.
What if the panel size in the kernel is correct, but the screen is "over-drawn"? Maybe ICS doesn't have an option to draw to a screen with a 320x240 resolution? This would explain the status bar and launcher issues. Try rewriting the kernel with the highest resolution (480x328 I think?).
And about the WIFI issue, did you remember to copy the .ko file over to the new build and add the update?
I Know I'm pissing in the wind; I had less luck getting Honeycomb ported from the Wildfire to the Kaiser, so this is looking interesting. You could strip to the basics and just replace things one at a time like I did and see what happens.
PoXFreak, if I good understand this
hom.hom said:
I am able to boot Zerorom 1.0 from the HTC kaiser now. But there are still a couple of quirks
Click to expand...
Click to collapse
he wants to port zerorom from wildfire. And this is just 2.3.7(cyanogenmod) with few applications changed to only looks like ICS. So it shouldn't be these problems with porting gingerbread...
Same rules apply: If the original rom's apps require a resolution higher than what's provided, there could be overscan or "over-shoot" of the original screen into unseen parts of the screen.
As far as the WiFi issue, the wifi.ko file from Scoot's 2.3.5 CM "should" work, but I have not tested it myself.
I do have an unused Kaiser witha good screen and only 2 bad blocks if he wants help with it. I would need all the files he's working with in a tarball posted to mediafire or some other file hosting site.
Im not sure whats in the guide you are looking at and quite frankly I dont feel like looking, but a few of us many moons ago were working on Sense Roms. One trick we used was stripping the system folder of its apps and placing them in a new folder "app_s" in data then symlinking /data/app_s to system/app at boot time. This was one way of shrinking you system files. I also managed onced instead of using data/app_s I used sdcard/app_s however this slows things down a tad but it worked. We eventually gave up on sense roms cause the sense widgets would not work properly and the entire rom was extremely laggy. Good luck with ICS If you happen to get it running I will install it for ****s and giggles however I no longer use this phone, and havent for several years but I still have it and it still boots up
hom.hom:
What is the total size of this build?
Could you not move apps from /system/apps to /data/apps?
What about swapping libskia.so and install a different Launcher from another build?
Related
Figured we might need a help thread for metamorph and since I need help here goes the first question
So I took part of my theme and made it Metamorph compatible with the guide here:
http://forum.xda-developers.com/showthread.php?t=591329
Now MM opens the zip fine, starts to install it, asks permission to edit framework-res.apk then after about 1 minute it asks for a reboot and then before I can answer it just reboots. At this point it gets stuck in a boot loop and I have to nandroid.
Never really messed with MM so it could be something I am doing wrong or I did read this:
Depending on the device you have you may need a different SPL to be able to apply themes.
Click to expand...
Click to collapse
Anyways I attached my test theme (no where complete, just wanted to test it). Is the issue with me, the phones spl or metamorph not ready for the incredible yet?
ps: If your going to test my theme uploaded here, be smart, do a backup, this is just a test and not a full theme and I just told you it is causing boot loops
test file download
I wonder if the SPL will be the roadblock until Froyo is officially released. Of course I know nothing of these things...
*Sent via Tapatalk on my Incredible
running latest leak 8/1/10 new radio 2.15 busybox all set up. tried to installed metamorph and ninjamorph, gives /system error about space and then my root is broken ?!? any ideas folks, so lost on this one. thank god for nandroid restore
icedmayhem said:
running latest leak 8/1/10 new radio 2.15 busybox all set up. tried to installed metamorph and ninjamorph, gives /system error about space and then my root is broken ?!? any ideas folks, so lost on this one. thank god for nandroid restore
Click to expand...
Click to collapse
Did you run the unrevoked forever to unlock the nand
I'm having mixed results with metamorph. I was able to do everything I wanted on CM6. I actually ported this over for us and it works great on metamorph not problems, check it out: http://androidforums.com/roms-incredible/149055-theme-vatsense-cm6port.html
now I tried porting one of my themes over to skyraider2.2 and I can get framework-res and com.htc.resources to work fine, but when i tried to add in my themed apps, I get a f/c and have to pull battery. http://androidforums.com/roms-incredible/148221-theme-do-bluev1.html
Ran the unrevoked tool so give me s off as well...
I had somebody in the nexus forum metamorph the weather channel widget but I cant get it to install, anyone game to take a look? I would love this to be transparent.
I have ran unrevoked forever and installe the latest metamorph.
Thanks
Im running (latest) stock 2.2 leak, and i cant get metamorph or NinjaMorph to make ANYthing stick. (YES I HAVE S-OFF) Both run as if they are making the changes, No diff than they did with the Moto Droid. MM reboots after ANY package, not just framework, with out asking to reboot. Ninja will usually break the app (app is no longer installed)
ANY IDEAS?
EDIT: just for kicks i installed a Deodexed Stock ROM, and still the same results... It says its doing it, but i the end it makes NO changes to the APK files.
see if you can manually (adb) replace the files and see if it sticks..... if not then the issue is not metemporph.... it's a rooting/nand issue.
R1lover said:
see if you can manually (adb) replace the files and see if it sticks..... if not then the issue is not metemporph.... it's a rooting/nand issue.
Click to expand...
Click to collapse
Manually replacing the entire APK... work just like it did when we needed recovery. Just now you type ADB remount, then push it.
If you mean manually replacing the edited files within the apk, thats not directly possible via adb. you have to PULL, EDIT,PUSH.
The problem here is metaMorph is supposed to open the apk replace just the edited files then close it up right on the phone, and its just not doing that!
what i did that fixed all my issues was install busybox from market. its odd but it all works perfect now even though i though it had been prebuilt into the rom. strange but ill take it
icedmayhem said:
what i did that fixed all my issues was install busybox from market. its odd but it all works perfect now even though i though it had been prebuilt into the rom. strange but ill take it
Click to expand...
Click to collapse
Yea, I just did what you said, before Metamorph would say not enough free space in /system/
I was using the 8/1/10 Froyo leak and I guess that one didn't have busybox, weird I was able to use Titanium Backup and I though that required busybox as well...
everytime you switch a rom, you should download busybox and let it update, it changes per rom.
Welp , Im still at a loss... I updated busybox, using the market app... and it still gives me the same results...
It takes 2-3 min to "apply theme" then reboots... and NO changes !
My theme contains ONLY the folders and files that need to be replaced, and my xml is copied from an existing theme, then edited. So i dont know wtf is goin on with this ****.
try making it into a file that can be flashed from recovery, then ull know for sure u made it correct....
Not sure this will help but I just installed Metamorph today and was getting the "system memory" error. To fix the problem I just used Root Explorer to mount /system as rw. Could the problems be related to write permissions?
I'm new to this...
I'm running SkyRaider's 2.5.2. Sense ROM. Just downloaded MM & BusyBox via market. When I start MM I select "Start Checks" or whatever. It then either forces my phone into reboot or gives me the "not enough memory in /system" error.
I did not install unrevoked forever. Is that my problem?
ksidirt said:
I'm new to this...
I'm running SkyRaider's 2.5.2. Sense ROM. Just downloaded MM & BusyBox via market. When I start MM I select "Start Checks" or whatever. It then either forces my phone into reboot or gives me the "not enough memory in /system" error.
I did not install unrevoked forever. Is that my problem?
Click to expand...
Click to collapse
Uh yea, it needs to write to system, you need S-off to use it.
I'm reviving this thread so as to not clutter up the Metamorph Themes Master List thread
This quote is from the other thread, I just thought it would be more appropriate to answer here instead.
mikesincredible said:
Wow. What you just told me is like trying to learn chinese...lol I see there's more involved...any good articles to point out so I can learn. I just know rom manager and adb push code... ::
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I'm sure there are some guides floating around XDA, but I mostly learned MM just by messing with it and learning from trial and error.
Basically, metamorph just opens up an .apk file, replaces any of the files it finds in the folders specified by a theme's .xml file, then closes/re-signs the apk.
This is much better than flashing themes from the recovery menu or rom manager because doing so replaces the entire framework-res.apk, overwriting any themes you had previously installed. Since metamorph only replaces the files you want, any theme you already had will be preserved.
Here's an example to get a quick overview of how it works. Say you've already applied my black rotary lockscreen mod (found here) and you want to use some of the elements from SoCalMiles' Incredible rEVOlution theme.
First you should download his file, and inside the .zip find "\Incredible_Revolution_Original_Theme.zip\system\framework\framework-res.apk" and extract it somewhere.
Then rename "framework-res.apk" to "framework-res.apk.zip" or something similar. Now you can browse/unzip the files just like you would any other folder.
In your new .zip navigate to \framework-res.apk.zip\res\drawable-hdpi-v4, most of a rom's theme will be in that folder.
Now, if you've applied my theme through metamorph (or any theme, for that matter) you should have the directory "\sdcard\AndroidThemes\BlackRotary-hdpi-v4\framework-res\res\drawable-hdpi-v4\" on your sdcard.
Choose any of the files you want to apply to your phone from the extracted Incredible rEVOlution drawable-hdpi-v4 folder and copy them from to the \sdcard\AndroidThemes\BlackRotary-hdpi-v4\framework-res\res\drawable-hdpi-v4\ folder. Now when you run the metamorph it should copy the files you added as well as the ones that were previously there.
If you want to copy files that are not in the drawable-hdpi-v4 folder, simply make a new folder for the containing folder. Basically just make sure the \sdcard\AndroidThemes\whatevs\framework-res\ directories match the directories in the framework-res.apk file you're pulling from.
That's the easiest way to combine two themes, if you're looking to make you're own metamorph theme to post on xda you'll need to learn to edit the .xml file which directs metamorph to which files to modify, but that isn't too hard either, and there's no need to do this if you're just making metamorphs for your own personal use.
mixedlemon said:
I'm reviving this thread so as to not clutter up the Metamorph Themes Master List thread
This quote is from the other thread, I just thought it would be more appropriate to answer here instead.
I'm sure there are some guides floating around XDA, but I mostly learned MM just by messing with it and learning from trial and error.
Basically, metamorph just opens up an .apk file, replaces any of the files it finds in the folders specified by a theme's .xml file, then closes/re-signs the apk.
This is much better than flashing themes from the recovery menu or rom manager because doing so replaces the entire framework-res.apk, overwriting any themes you had previously installed. Since metamorph only replaces the files you want, any theme you already had will be preserved.
Here's an example to get a quick overview of how it works. Say you've already applied my black rotary lockscreen mod (found here) and you want to use some of the elements from SoCalMiles' Incredible rEVOlution theme.
First you should download his file, and inside the .zip find "\Incredible_Revolution_Original_Theme.zip\system\framework\framework-res.apk" and extract it somewhere.
Then rename "framework-res.apk" to "framework-res.apk.zip" or something similar. Now you can browse/unzip the files just like you would any other folder.
In your new .zip navigate to \framework-res.apk.zip\res\drawable-hdpi-v4, most of a rom's theme will be in that folder.
Now, if you've applied my theme through metamorph (or any theme, for that matter) you should have the directory "\sdcard\AndroidThemes\BlackRotary-hdpi-v4\framework-res\res\drawable-hdpi-v4\" on your sdcard.
Choose any of the files you want to apply to your phone from the extracted Incredible rEVOlution drawable-hdpi-v4 folder and copy them from to the \sdcard\AndroidThemes\BlackRotary-hdpi-v4\framework-res\res\drawable-hdpi-v4\ folder. Now when you run the metamorph it should copy the files you added as well as the ones that were previously there.
If you want to copy files that are not in the drawable-hdpi-v4 folder, simply make a new folder for the containing folder. Basically just make sure the \sdcard\AndroidThemes\whatevs\framework-res\ directories match the directories in the framework-res.apk file you're pulling from.
That's the easiest way to combine two themes, if you're looking to make you're own metamorph theme to post on xda you'll need to learn to edit the .xml file which directs metamorph to which files to modify, but that isn't too hard either, and there's no need to do this if you're just making metamorphs for your own personal use.
Click to expand...
Click to collapse
What other folders contain the status icons? I'm looking to restore the circle battery and alarm from the incredible revolution theme, I found the battery.pngs..but no alarm..so if I copy and paste them to the blackrotary folder in androidthemes and metamorph, I should have the battery back
Hi all,
I'm trying to install adobe flash to the system partition to save space. I've done it by adding the flash apk and libs to the gapps addon (required for CM6 anyway).
I can see in root explorer that in /system/apps I've got com.adobe.flashplayer.apk, and in /system/lib i've got libflashplayer.so and libysshared.so.
Under settings->applications I can see that Adobe Flash Player 10.1 is present.
In browser settings, Enable plugins is set to "on demand".
But when I try a flash site that used to work, it no longer does. What am I missing?
Thanks for any help,
Phil
It seems if you leave the .so files where they were in /data/data/com.adobe.flashplayer/lib, eveything works. So it looks like the app doesn't bother to check /system/lib, but goes straight to its own data folder.
Any way to remedy this? I've saved 4-5 MB on /data by moving the apk to /system, but the .so files are 8MB between them, i'd like to get them on /system as well.
Before flashing a ROM, move the APK file into the /system/app folder in the ZIP file and then re-zip it
EddyOS said:
Before flashing a ROM, move the APK file into the /system/app folder in the ZIP file and then re-zip it
Click to expand...
Click to collapse
Hi Eddy, that's exactly what I did as I said in my first post. It didn't work initially, but I now have it working by restoring the /data/data/com.adobe.flashplayer/lib folder with the two libs in it.
So the apk is in /system/app, but there are still these two big libs on /data taking up about 8MB. I was wondering if there is any way to get the system to pick them up from /system/lib like with all the other libs.
Cheers for any help,
Phil
I just have the APK in /system/app and it's fine - got over 100MB of storage (but I only use 5 apps and have them all moved to /system/app)
really? can you do me a favour and check in /data/data/com.adobe.flashplayer/lib and see what you have in there? Should be one huge (~7mb) .so file and a smaller one.
you definitely have the latest flash 10.1 final? version 10.1.92.8? (check in settings->applications).
I'm thinking of creating symlinks in /data/data/com.adobe.flashplayer/lib to the two files in /system/lib and see if that works.
Yes I do have the latest it's there by default in Paul's MCR r8 ROM (first thing I did once it was out) - he normally has it set to go to /data/app but I move it (and the other 5 apps) to the /system/app folder and it's fine...I'll have to install Root Explorer again to check the folder, though...
EDIT: Checked that folder, there's nothing in there at all...
Oh. Huh. Can you check and see if they're in /system/lib? I wonder how paul's got this set up. Should probably just ask him
What file(s) am I looking for?
libflashplayer.so and libysshared.so. Cheers
libflashplayer.so is, libysshared.so isn't
ok thanks for your help i tried the symlinks and it works for now although i guess its a bit hacky. Don't know why yours picks it up from /system/lib and mine won't. I'll see if I can get one of the elder gods to give up their wisdom
wingphil said:
ok thanks for your help i tried the symlinks and it works for now although i guess its a bit hacky. Don't know why yours picks it up from /system/lib and mine won't. I'll see if I can get one of the elder gods to give up their wisdom
Click to expand...
Click to collapse
any progress on this? I also would like to push those shared objects into the /system/lib/ folder to save on space
You need to have the matching apk and libraries in /system for it to work.
teppic74 said:
You need to have the matching apk and libraries in /system for it to work.
Click to expand...
Click to collapse
Had the libs in /system whith fresh MCR r8 ROM .. once i upgraded via Market to latest version they were also in /data/data.
So is there a way to get them to /system again (so that they will really be taken from there by the apk) ?
I am S-Off so the moving itself is easy ;-)
Marcus
soory if i dug an ol thread but i cant make it work...
copy the apk file to /system/app via root explorer and reboot...
in settings/application/manage application/all/
Adobe flash player is in it but it is only 56kb..
set browser for enable plugin to be 'on-demand' and 'always on' but no go (tried surfing on adobe flash mobile showcase site).....
to think i am thinking to move adobe air using this method too..
what else is needed?
Running Nexus One, CM6.0
Hi everyone!
I see this thread is a a bit old, but I've been trying to do the exact same thing with installing Flash Player in /system. My device also won't find the libs in /system/lib, so I'm thinking about doing the symlink stuff as well, but I'm not quite sure how to do this, since I don't have a lot of linux experience. Could you please help out a little?
Will this work?
Code:
ln -s /data/data/com.adobe.flashplayer /system/lib/com.adobe.flashplayer
Also, just to check: is there anything else I should do besides copying the libs Adobe Flash installs in its /data/data folder to /system/lib and creating the link?
Thanks a lot!
Not needed to make symlinks.
Just create folder /system/lib/plugins/com.adobe.flashplayer and move libs to it.
..
i'm tring to make a boot animation and i have the pics as png in a folder,i have a desc, and i have signed and zipped it but when i try to install i get can't find update script. i have looked into other bootanimes and not all have that. so thats where im stuck if anyone could help me learn what i'm doing wrong that would be great. thx
Help Anyone?
dased14 said:
i'm tring to make a boot animation and i have the pics as png in a folder,i have a desc, and i have signed and zipped it but when i try to install i get can't find update script. i have looked into other bootanimes and not all have that. so thats where im stuck if anyone could help me learn what i'm doing wrong that would be great. thx
Click to expand...
Click to collapse
How are you trying to install? Did you make sure you bootanimation.zip is a storage zip?
Trying to make it flashable through recovery, and I think on 7zip I used normal, but i'll check into that after I get home.
dased14 said:
Trying to make it flashable through recovery, and I think on 7zip I used normal, but i'll check into that after I get home.
Click to expand...
Click to collapse
After creating your bootanimation -- You need to make sure that a couple things have been done correctly for the bootanimation to 1) Work and 2) Be able to be flashed via recovery.
1) To make the bootanimation work
a. Make sure that after creating the animation itself that the .zip you create has NO compression -- (e.g You use "store" mode, instead of "normal" -- both 7zip/Winrar have this feature)
b. Make sure the desc.txt file is properly formatted and has the correct folder names inside the file. Also make sure you have a carriage return (press enter) at the VERY last line of your desc.txt file
c) Make sure the .png filenames are somewhat sequential and organized. (e.g. BootUp001, BootUp002, BootUp003, etc)
2a) To make a flashable package
a. First create a folder to house the bootanimation and you'll also need to explicitly define the folder names that you want the animation to be pushed to. (e.g -- Inside lets say the "MyBootanimation" folder -- you should have three folders; they're names respectively are:: system/customize/resource
Inside the resource folder is where your newly created bootanimation.zip will go.
2b) To make the package flashable and work in recovery; you'll need a update-script file which should be in a folder called:: META-INF (ALL CAPS); inside that folder should reside, three more folders:: com/google/android/. The update-script file will go INSIDE the android folder.
I've attached a simple update-script file that will make your package flashable. Unzip the "Extract-ME" file and you'll find the file.
So, to get this to work, you'll open the "MyBootanimation folder and inside it should reside to folders (system (and it's subfolders); which houses the bootanimation and META-INF (and it's subfolders); which houses the update-script). You need to select both files and zip them up in NORMAL mode, not "store" mode. This will create your new package, which you then need to sign via whatever method you use. I use command line and I'd like not to explain that if I don't have to.
here's the file i'm working on if someone wants to take a look at it and tell me what i'm doing wrong that would help me out a lot.if you can i would like to know what is wrong so for future use and the knowledge.
http://dl.dropbox.com/u/9628638/bootanimation1.zip
Lemme know if this helps...
dased14 said:
here's the file i'm working on if someone wants to take a look at it and tell me what i'm doing wrong that would help me out a lot.if you can i would like to know what is wrong so for future use and the knowledge.
Click to expand...
Click to collapse
Two noticeable things:
1. Your images are 850 x 400 (resize all to 800 x 450)
2. Your .zip file is not arranged right.(look at my attached file, should give you an idea)
Your file is way too big to upload here so attaching the base file here for you to work with.
- First, zip the android folder,part2 folder and the desc.txt file as a storage, and name the file bootanimation.zip.
- Second, 7zip my file and navigate to customize>resource and replace the file there with the one you created in the previous step.
- Close and flash the file (This is in amend so you might want to use clockwork 2x (or equivalent RA) to flash it. Feel free to change the update script if you wish)
I tried this on my myn RLS5, works like a charm. Might want to change the desc.txt to match the image dimensions. (800 x 450)
I hope this helps.
PS: I Like the minion animation.
now it came up E:\wrong digest:customize/resource/bootanimation.zip huh?
i put the file here http://dl.dropbox.com/u/9628638/minionsdisco.zip
i know i'm a pain in the [email protected]@, thanks for all the help
edit: i figured out what i was doing wrong it was the way i was zipped files together. now to speed it up and maybe a loop
here's a working one http://dl.dropbox.com/u/9628638/minionsdisco1.zip. how do i speed it up to play more like the movie.
ps thanks to pseudoremora,theidlemonk for helping me figure out what i was doing wrong.
pm me your email...I'll send the file over...i am having trouble uploading it
dased14 said:
now it came up E:\wrong digest:customize/resource/bootanimation.zip huh?
i put the file here http://dl.dropbox.com/u/9628638/minionsdisco.zip
i know i'm a pain in the [email protected]@, thanks for all the help
Click to expand...
Click to collapse
First and foremost -- I don't know whose method recommended that you leave the "system" folder out of the flashing process, but that's a very incorrect way of doing this.
I've stated earlier that you need THREE folders -- SYSTEM, customize, and resource. You only have customize and resource. Your customize folder (and it's subfolders) needs to be placed inside a folder labeled "system".
Secondly, the command you're using in the update-script, while it will work now; will not work if someone decides to change the structure of your package in the future. The update-script I uploaded earlier allows for future flashing because anything placed inside the "system" folder (which Android 100% relies on) will always be flashed, as long as the structure is correct within the system folder.
You should remove the update-script you have now and place this one inside it (if you decide to use the method I've stated above). I've attached the file below (extract first).
Lastly, quite frankly; I've never seen a 60MB bootanimation before and to be honest, that's just unbelievably huge. You need to figure out either how to shorten your animation or to compress it in a manner which will lower its size.
Also, the native resolution for the EVO is 480 x 800 and not 450 x 800 for future reference.
pseudoremora said:
First and foremost -- I don't know whose method recommended that you leave the "system" folder out of the flashing process, but that's a very incorrect way of doing this.
I've stated earlier that you need THREE folders -- SYSTEM, customize, and resource. You only have customize and resource. Your customize folder (and it's subfolders) needs to be placed inside a folder labeled "system".
Secondly, the command you're using in the update-script, while it will work now; will not work if someone decides to change the structure of your package in the future. The update-script I uploaded earlier allows for future flashing because anything placed inside the "system" folder (which Android 100% relies on) will always be flashed, as long as the structure is correct within the system folder.
You should remove the update-script you have now and place this one inside it (if you decide to use the method I've stated above). I've attached the file below (extract first).
Lastly, quite frankly; I've never seen a 60MB bootanimation before and to be honest, that's just unbelievably huge. You need to figure out either how to shorten your animation or to compress it in a manner which will lower its size.
Also, the native resolution for the EVO is 480 x 800 and not 450 x 800 for future reference.
Click to expand...
Click to collapse
ok thanks,how would i compress it to make it smaller? and i want to speed it up to run more like the movie. i have it working it just runs kinda slow?
Not sure if you are on windows, but if you are then pngoptimizer does the trick (should be able to do multiple pngs at a time) and its free online. Also on windows I had an issue with the bootanimation.zip because windows kept adding the thumbs.* file in the two folders other than the desc.txt...that made my animation choppy. Just 7zip into you file and delete if you see it.
pseudoremora said:
First and foremost -- I don't know whose method recommended that you leave the "system" folder out of the flashing process, but that's a very incorrect way of doing this.
I've stated earlier that you need THREE folders -- SYSTEM, customize, and resource. You only have customize and resource. Your customize folder (and it's subfolders) needs to be placed inside a folder labeled "system".
Secondly, the command you're using in the update-script, while it will work now; will not work if someone decides to change the structure of your package in the future. The update-script I uploaded earlier allows for future flashing because anything placed inside the "system" folder (which Android 100% relies on) will always be flashed, as long as the structure is correct within the system folder.
You should remove the update-script you have now and place this one inside it (if you decide to use the method I've stated above). I've attached the file below (extract first).
Lastly, quite frankly; I've never seen a 60MB bootanimation before and to be honest, that's just unbelievably huge. You need to figure out either how to shorten your animation or to compress it in a manner which will lower its size.
Also, the native resolution for the EVO is 480 x 800 and not 450 x 800 for future reference.
Click to expand...
Click to collapse
thanks for your help on this, i'm looking for any ideas on how to compress this to make it smaller in size(without losing any animations) i have been usiing 7zip to compress it
dased14 said:
thanks for your help on this, i'm looking for any ideas on how to compress this to make it smaller in size(without losing any animations) i have been usiing 7zip to compress it
Click to expand...
Click to collapse
pngoptimizer as theidlemonk recommended should be used for each PNG file and hopefully should bring down the size a bit. Otherwise; it really comes down to cutting the animation.
I'm not saying you can't push a 60MB file onto your phone as a bootanimation; but I think it's huge waste of space for such a thing. You have to remember; we're only talking about the bootanimation here and quite frankly, the EVO tends to boot up rather quickly, so trying to show a clip from a movie really shouldn't be your goal -- if anything, you can take bits and pieces from the clip and use that instead.
Personally, I try to make my bootanimations minimal and light. The important part of the animation is actually the looping; so concentrate on that.
pseudoremora said:
pngoptimizer as theidlemonk recommended should be used for each PNG file and hopefully should bring down the size a bit. Otherwise; it really comes down to cutting the animation.
I'm not saying you can't push a 60MB file onto your phone as a bootanimation; but I think it's huge waste of space for such a thing. You have to remember; we're only talking about the bootanimation here and quite frankly, the EVO tends to boot up rather quickly, so trying to show a clip from a movie really shouldn't be your goal -- if anything, you can take bits and pieces from the clip and use that instead.
Personally, I try to make my bootanimations minimal and light. The important part of the animation is actually the looping; so concentrate on that.
Click to expand...
Click to collapse
i'll look into pngoptimizer, now would i set eveything up the same for loop(with fewer animations)like i said this is the first one i have ever tried to make(i hope i get better as i do more) how would i add sound to one. and thx again guys for putting up with me and for all the help
dased14 said:
i'll look into pngoptimizer, now would i set eveything up the same for loop(with fewer animations)like i said this is the first one i have ever tried to make(i hope i get better as i do more) how would i add sound to one. and thx again guys for putting up with me and for all the help
Click to expand...
Click to collapse
I'd advise you take a look at this post and this one also. I wrote that quite some time ago, however it's still very much applicable today.
Edit:: It's actually probably good to read the posts from pages 15, 16, and probably 17 as well in the links I've posted above.
what would you guys say is the best png optimizer to (less loss, better compression)
dased14 said:
what would you guys say is the best png optimizer to (less loss, better compression)
Click to expand...
Click to collapse
Both of us just told you.
Use pngoptimizer. The program itself optimizes each png, taking away any erroneous data and leaves everything else intact; thus giving you a smaller .png file. Doing this for EACH .png file will result in a smaller bootanimation file.
PNGs can be optimized just so much, I would rather think more on the lines of what pseudoremora said: Cutting down animation to keep it minimal and light. Looping will also be a big part as you have over 300 images. Looping would reuse images and allow cutting of parts. (I hope I made sense).
pseudoremora said:
Both of us just told you.
Use pngoptimizer. The program itself optimizes each png, taking away any erroneous data and leaves everything else intact; thus giving you a smaller .png file. Doing this for EACH .png file will result in a smaller bootanimation file.
Click to expand...
Click to collapse
Ok I wasn't sure if that was the name of it or a program type, Googled it and got a bunch of different ones just wanted to make sure. And yes I know its a large file and I will take both of your advice and cut it down. Again thanks for the time and help
Hi. please, write your own method to port.. i have one.. its from someone so its not by me.. i think when everyone write his own method. we can find the best way..to cooperate
Well I generally start by looking for the rom I want to port on a device with similar specs to ours or has some compatibility. I have used the Wildfire, Hero, MyTouch 3g.
Then I find the most compatible kernel, usually 2.6.32.
Having downloaded the rom unpack the zip.
Remove any folders or files you normally don't see in the root folder (boot.img, META-INF)
Add a sysinit.rc from fresh froyo/gingerbread/Myn's donut/Incubus eclair (depending on which os version your port is)
If you are porting Sense change the bootclasspath in sysinit.rc (what to change it to: /system/framework/core.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/com.htc.framework.jar:/system/framework/com.htc.android.pimlib.jar:/system/framework/com.htc.android.easopen.jar:/system/framework/com.scalado.util.ScaladoUtil.jar)
Then tar the thing.
Put it in andboot
boot the kernel (I do everything android on NAND)
install it to system.img
clear dalvik cache (I find this almost always necessary with ported roms)
and see what happens!
If it boots with no bootloop, strip all unnecessary apps (I usually start and just remove the "data" folder)
Continue stripping anything you don't want and then release.
If it doesn't boot right, I usually fiddle with the sysinit.rc first and a little in the build.prop.
Sysinit.rc I work with by extracting the one from the boot.img (don't ever completely remove it) and merging them
build.prop = hopefully self explanatory (if not I can write the rest later)
Try, Try again!!
i have this one...
I'll look into the specs of wildwire and let you know if my steps would work. Just kinda busy this holiday season. But my steps were pretty simple. We have to know if this is an odex'd or deodexed version. If it is odexed version, it would be nice to deodex it first. I use Android kitchen from dsixda. The only part we need is the system folder. It has apps, etc, lib, bin and the rest...basically under the system we need to put Fresh Froyo (FF) files build.prop and sysinit.rc and move it to wildfire's system folder (these two files are required for booting)then under /system/etc you need to grab vold.conf from (FF) and move it to wildfire's /system/etc. Ooops..I'll have to get back to you. Dinner time BTW, vold.conf is what loads SD card. I looked at the specs of wildfire and not sure if it works since it has a 7225 processor and 5 megapixel but it's worth a try. Then /system/etc, copy ppp and passwd from liquid's kernel and put it in that folder (like permissions). Compare the folders with Fresh Froyo and if something is missing from Fresh Froyo to wildfire. Copy wifi folder (don't copy ppp folder, delete it if wildfire ROM has it). Now lets go to system/lib. Copy the following files from Fresh Froyo to wildfire libaudio.so, libaudiopolicy.so (audio drivers) libcamera.so libcamera_client.so libcameraservice.so (camera drivers) libgps.so (gps driver) libhtcgeneric-ril.so (phone driver) libicudata.so. Then copy egl folder to hw folder and bluez-plugin folder. Now go to system/modules and delete all files and get modules from l1q1d's latest kernel and put it in the system/lib/modules folder. Then go to system folder and copy bin folder, media folder, xbin and usr folder to wilfire system. That's it. Save the system folder as androidinstall.tar and see how it goes. Goodluck.
can u update nbh which u used? i have many of them but no works
I use an Atools edited 2.6.32 kernel with built in o'c to 520mhz and a bigger system NAND partition.
Almost or All Wildfire build work without importing system files just mess around with the sysinit.rc and build.prop.
The screen res is the same as our lovely phone
Since we are talking about porting here is my question:
I also have a huawei u8300 with stock eclair (2.1 update 1) and stock kernel (2.6.29)
I don't have the source files of the kernel (T_T)
Phone is based on msm7225 BUT has a physical qwerty keyboard, so I NEED to use the stock kernel to have it working (tried other kernels from 7225 platform but they crashes after the press of any key on the keyboard).
It is possible in your opinion to make the stock kernel working with a froyo build?
And if so, how?
I've tried to use the stock kernel with varius system images from various 7225 phones but with no luck :/, I need to learn! Be my teacher xD!
TuoNonno said:
Since we are talking about porting here is my question:
I also have a huawei u8300 with stock eclair (2.1 update 1) and stock kernel (2.6.29)
I don't have the source files of the kernel (T_T)
Phone is based on msm7225 BUT has a physical qwerty keyboard, so I NEED to use the stock kernel to have it working (tried other kernels from 7225 platform but they crashes after the press of any key on the keyboard).
It is possible in your opinion to make the stock kernel working with a froyo build?
And if so, how?
I've tried to use the stock kernel with varius system images from various 7225 phones but with no luck :/, I need to learn! Be my teacher xD!
Click to expand...
Click to collapse
I dont know your answer, sry.. (Offtopic: My opinion - you are on bad device thread..) So my answer is i dont know..
Hey guys,
For a few days, I was wondering what could happen if we could compile the Standard C library (not trimmed one like Bionic) and compile some linux applications for ARM processor (say, Desire). I successfully compiled the GlibC, and now do have the .a and .so files.
The problem is, I don't know where to put them, so the dynamically linked applications can reach them! I could put them to /system/lib, but I don't want to overwrite the files already there (I don't want to crash the working parts of the system). I was thinking to put them to (say) /data and create symbolic links to /system/lib, but - as I said - what about the libraries which have the same name?
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to General
Sorry for the wrong section post. I found the solution though..
The thing is to be done is editing the Ramdisk/init.rc; changing LD_LIBRARY_PATH variable, accordingly (say, /data/lib). Once you do that, the system loads libraries from the folders, in specified order.
However, you must be cautious because since at the boot time, Data might not be mounted yet, the libraries that are installed there could not be read. Ergo, don't delete (or move) the system libraries (like I did ) - the phone won't boot without them.
Another issue is libc. Since bash shell is compiled with bionic, it requires bionic version of libc; not glibc. I'm going to try to overcome this by recompling shell; yet still there might be other problems (there might be other native executables need Bionic Libc)
I'll update this thread as I try new things.
theGanymedes said:
Sorry for the wrong section post. I found the solution though..
The thing is to be done is editing the Ramdisk/init.rc; changing LD_LIBRARY_PATH variable, accordingly (say, /data/lib). Once you do that, the system loads libraries from the folders, in specified order.
However, you must be cautious because since at the boot time, Data might not be mounted yet, the libraries that are installed there could not be read. Ergo, don't delete (or move) the system libraries (like I did ) - the phone won't boot without them.
Another issue is libc. Since bash shell is compiled with bionic, it requires bionic version of libc; not glibc. I'm going to try to overcome this by recompling shell; yet still there might be other problems (there might be other native executables need Bionic Libc)
I'll update this thread as I try new things.
Click to expand...
Click to collapse
I just put glibc in /lib, at boot /lib is empty, but then I mount the contents of /lib aftwards. Ideally it would mount from a custom init.rc script. I suppose if you put the libc in /data/lib you could sym link that to /lib during boot. I am pretty sure that /lib needs to be in the root dir and its contents must be executable. I found I had to edit some header file somewhere, I'll get back to ya once I start poking my head round Android again, syncing back up atm.