Related
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.
..
Hello,
I began the Rooting / flashing custom Rom journey just 4 nights ago. I would not have thought it just a week ago…. nine months of all that damn bloatware…. five months of envying all those Sense 3.0 users…. but, a rooted, suited, un-bloated ROCKET DHD I now have
I have one last thing to accomplish, then, after monitoring all is okay for a little while I will revisit all the members here who's guides I followed and programmes I downloaded in order to help me get to this point and I'll show my thanks to each of them; a small donation to LeeDrOID must also be in order.
But first, my final step:
I'm trying to update my RIL but my old one simply refuses to budge, regardless of how many times I reflash it, can you help me please ?
I have installed Radio: 12.62.60.27U_26.13.04.19_M
The recommended RIL to go with this is: RIL_12.62.60.27_26.13.04.19_M
I downloaded both from here: http://forum.xda-developers.com/showthread.php?t=996630
I flash the RIL by booting into Recovery - scoll down to Mounts and Storage and enter - scroll down to Mount System and enter - scroll down to Go Back and enter - scroll down to Install Zip from SDcard and enter - enter Choose Zip from SDcard - scroll down to RIL_12.62.60.27_26.13.04.19_M.zip and enter - scroll down to Yes and enter.........
"Install from SDcard complete"
scroll down to Go Back and enter - enter Reboot System Now and enter.
Phone reboots normally.
I check RIL by using this app that I installed: Simple RIL Infos Displayer v1.1 by ZikHD
RIL always shows: HTC-RIL 2.2.0179HM (Aug 17 2011)
What am I doing wrong ?
Appreciate any help.
Many thanks.
This will work for you: Unzip your rom.zip and ril.zip, copy the 3 lib files (from your ril.zip in lib folder) in your rom (system/lib) if the files already excist delete them first, then zip your rom and flash it. You can also use another method by pushing the 3 libs in your system/lib folder by using root explorer for example.
MichDHD said:
This will work for you: Unzip your rom.zip and ril.zip, copy the 3 lib files (from your ril.zip in lib folder) in your rom (system/lib) if the files already excist delete them first, then zip your rom and flash it. You can also use another method by pushing the 3 libs in your system/lib folder by using root explorer for example.
Click to expand...
Click to collapse
Mich, thanks for your kind reply.
Interesting, regarding putting the 3 RIL files into the relevant Rom folder, zipping back up then reflashing, however, depite having Titanium BackUp, I would still rather not reflash my Rom; I have my phone all set-up nice and lovely and would rather not go down this route if I can avoid it, but thank you for offering me it, and explaining the process in simple terms, which I need
Now, what I am excited about is the Root Explorer way, which I also have installed on the phone.
Fancy taking 5 minutes to reply and writing (in dumbo terms - I'm the dumbo, not you) exactly how I go about doing it ?
Thank you, friend.
Put the 3 lib files from your ril.zip on your sd-card, open root explorer and go to your sd card, select multiselect and copy the 3 lib files, go back one folder and push Mount R/W buttom (you need Mount R/O) then open system and do the same (Need R/O), open lib folder and paste the 3 lib files you copied, after that reboot your phone and now you have your matching rils.
MichDHD said:
Put the 3 lib files from your ril.zip on your sd-card, open root explorer and go to your sd card, select multiselect and copy the 3 lib files, go back one folder and push Mount R/W buttom (you need Mount R/O) then open system and do the same (Need R/O), open lib folder and paste the 3 lib files you copied, after that reboot your phone and now you have your matching rils.
Click to expand...
Click to collapse
Perfect, simple instructions, thank you.
I have hit your "Thanks" button.
The 3 Lib files from the RIL Zip are now living in their new home.... my phone's System Lib folder. But my RIL is still showing as the HTC-RIL 2.2.0179HM.
Could it be that a Cache somewhere (I've no idea which one) needs clearing before the new RIL will show itself ?
Could it be that the HTC RIL keeps showing as my current RIL because it actually IS the one from the 3 Lib files; it's the new RIL after all ?
Signal strength seems unchanged (I only know how to gauge it by looking at the strength bars)
Internet speed seems unchanged (I only know how to gauge/test it by opening a few websites)
Sorry my phone, and me, and my RIL's have become a pain in the arse
Sir_Danny_Boy said:
The 3 Lib files from the RIL Zip are now living in their new home.... my phone's System Lib folder. But my RIL is still showing as the HTC-RIL 2.2.0179HM.
Click to expand...
Click to collapse
You did everything right, this IS the correct RIL for this radio
You can try reinstall that app but to be honest, forget about that app. Really, i don't care what it says because i know if you flashed your radio properly, and you replaced the libs properly, you are using latest radio+ril with certainty.
How did you flashed your radio?? And mayb its good for you to take a look at the updater-script (open with text editor) in the meta-inf folder in your ril.zip. This script shows you whats happening with your phone when you flash that ril.zip. As you can see, you did the things in the script manualy by using rool explorer.
@MichDHD: I flashed my Radio using the wonderful Radio Tool created by "leith51" - I downloaded it from here: http://forum.xda-developers.com/showthread.php?t=896597
I have just installed Text Editor app. I'm trying to follow your instructions on how to read the updater-script in the meta-inf folder of my RIL.Zip.... struggling ! I open the Text Editor on my phone, scroll to my RIL.Zip that is on my SDcard ? I tried this, and when Text Editor opens the RIL.Zip just a ton of crazy Chinese type symbols came up
And what do you make of "sigurd_LU's" comment ? So the HTC-RIL 2.2.0179HM (Aug 17 2011) is the correct RIL for Radio 12.62.60.27U_26.13.04.19_M after all it seems
@sigurd_LU: Thank you.
To be honest, i never heard of that app, but it seems to be that you did it properly.
I meant open the updater-script on your pc, If you'r running windows, download notepad++ for free, are you on linux then just open with texeditor. You can always find the updater-script in this folder:
(RIL_12.62.60.27_26.13.04.19_M) / META-INF / com / google / android (in unzipped ril.zip)
@MichDHD: Wow, friend, how the hell do you know all this stuff ?
So, I downloaded Notepad Plus Plus and using it I opened the RIL Zip that's still on my PC (I assume I don't need to keep RIL Zip, Radio Zip, Rom Zip once they've been flashed on my phone?) Navigating to META-INF / com / google / android this is what I saw.....
ui_print("Applying RIL files - by amresh");
run_program("/sbin/mount", "/dev/block/mmcblk0p25", "/system");
package_extract_dir("lib", "/system/lib");
unmount("/system");
Nothing more, nothing less.
Of course it goes without saying, that I have absolutely no idea what any of it means
Well done mate. that's what i wanted you to see.
ui_print("Applying RIL files - by amresh"); ---> ui_print tells the phone to show "Applying RIL files - by amresh"
run_program("/sbin/mount", "/dev/block/mmcblk0p25", "/system");---> This line mounts your system (mmcblk0p25=system) (Remember, you made R/O from R/W , so R/O is mounted)
package_extract_dir("lib", "/system/lib"); ---> This line extracts the libs from your ril.zip in system/lib folder (like you did by yourself by pushing the 3 libs in system/lib folder)
unmount("/system");--> I think you know what this line does
Anyway, my point with this is if you're flashing something and it won't work, check the updater-script and try it by yourself. I know flashing is the easiest way but when you do it by yourself, you really understand whats happening at all and make it easier to find where it goes wrong.
edit: That's right, yo don't need that files on your phone after flashing/installing/pushing.
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.
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?
Hello guys.
Since it's my first post so i hope this's can usefull and can help my problem.
Did you all see thread this http://forum.xda-developers.com/showthread.php?t=1461712 It's aroma installer that can build custom rom with UI in recovery mode (if no mistake) and success in htc device. From this forum i know that sgy have dev and mod that success to build rom, recovery, and now MAROK kernel. It's sound good if we can build in with the installer to make our device more better.
So, is there any dev or mod try or start to this stuff to build our device?
You know that i'm newbie in android device, but i've start to learn the installer and make some modification (just a little part) and you know it's not easy to develop something if we are a newbie.
After i read about android i know that i must have tools to help us, so i've start to download any stuf to help me. Some of my tool that i have in my PC are cygwin, dsixda kitchen, apk manager, xUltimate, notepad++, 7zip, winrar, jre 6.22, jdk 6.20, microsoft.netframework 2 and 4 client user, and window xp sp2.
Is there any tools that i should have to help me playing with my device?
From all stuff that i have so far only xUltimate can give me best result for deodex. But to applied to my device in recovery mode i use tool that develop from other member like pratyuse, shuvit_kaskuser, skin, and the newest is marok. Thanks to you all guys and other that i've forget
Sory if this post is annoying you all and thanks to make me more better with this forum.
wow...you're so serious dude. I'm only using CWM, root explorer, titanium backup and a base custom ROM to make my own custom ROM (lol). btw, a deodex ROM will use a lot of internal memory. It isn't a mighty feature that every ROM must have. I thought we should use it wisely.
kurotsugi said:
wow...you're so serious dude. I'm only using CWM, root explorer, titanium backup and a base custom ROM to make my own custom ROM (lol). btw, a deodex ROM will use a lot of internal memory. It isn't a mighty feature that every ROM must have. I thought we should use it wisely.
Click to expand...
Click to collapse
I just read all bout android and don't know what should i do so i've try all of method for customize my device.
deodex In original stock of course it's will be more use internal memory but i've delete some app that i don't need. only some app can't deodex with xultimate.
I wanna make my device simple n fast. and of course wanna try aroma installer too.
well...this is what I do for compiling a new ROM. I'm definetely not a dev so I can't start with a raw project. I started from a custom ROM (in my case, its myss v.3.4. you may use other one. Repencis doesn't work in my test thought). we need these custom rom only to install our ROM in our device so basicly we can use any custom ROM. after that I customize my stock ROM with root explorer and titanium backup. I use root explorer to put some apps in /system/app and editing script. I like a light ROM which consume minimum internal memory so I use titanium backup to integrate dalvik cache into /system/app. after all customization on my stock ROM, I create a nandroid backup with CWM. extract it. then replace anything in my base custom ROM except /system/bin and /system/xbin. these two folder is related to kernel and the installer script so basicly I didn't do anything on them except removing any a2sd script. the last step, repack all the files into *zip file and flash it via cwm.
for customizing the theme, we can use UOT kitchen or recompile framework-res.apk and systemUI.apk manually via eclipse or just replacing the files inside with 7zip. we may also put another bootanimation.zip in /system/media to change the bootscreen and put bootsound.ogg in /system/etc for the bootsound.
for everything we do, we should make sure the size is fit with our system partition. thats the reason why I customize my stock ROM manually via rootexplorer. I just want to make sure that the my customization is fit with my system partition and work properly. I thought our system partition is 220 mb but make sure you give some space for later modification.
well...thats all. I'm not saying that I really make a new custom ROM. It's more like recompile another ROM with my personal taste. a fresh installation of mine is only use about 3.4 mb internal ROM.
kurotsugi said:
well...this is what I do for compiling a new ROM. I'm definetely not a dev so I can't start with a raw project. I started from a custom ROM (in my case, its myss v.3.4. you may use other one. Repencis doesn't work in my test thought). we need these custom rom only to install our ROM in our device so basicly we can use any custom ROM. after that I customize my stock ROM with root explorer and titanium backup. I use root explorer to put some apps in /system/app and editing script. I like a light ROM which consume minimum internal memory so I use titanium backup to integrate dalvik cache into /system/app. after all customization on my stock ROM, I create a nandroid backup with CWM. extract it. then replace anything in my base custom ROM except /system/bin and /system/xbin. these two folder is related to kernel and the installer script so basicly I didn't do anything on them except removing any a2sd script. the last step, repack all the files into *zip file and flash it via cwm.
for customizing the theme, we can use UOT kitchen or recompile framework-res.apk and systemUI.apk manually via eclipse or just replacing the files inside with 7zip. we may also put another bootanimation.zip in /system/media to change the bootscreen and put bootsound.ogg in /system/etc for the bootsound.
for everything we do, we should make sure the size is fit with our system partition. thats the reason why I customize my stock ROM manually via rootexplorer. I just want to make sure that the my customization is fit with my system partition and work properly. I thought our system partition is 220 mb but make sure you give some space for later modification.
well...thats all. I'm not saying that I really make a new custom ROM. It's more like recompile another ROM with my personal taste. a fresh installation of mine is only use about 3.4 mb internal ROM.
Click to expand...
Click to collapse
Same case with me, i'm not dev so i just compile any trick from other. But i always start from stock rom (i use dxlb1) then i modified as i like to make my device at least not brick. Anyway your method sound nice just 3.4MB fresh installation in internal and maybe sometime i will try.
I now there's many method to customize device but we (as newbie) still confuse with the step and tools are needed. Some method doesn't work even we doing step by step right because of different case or maybe some forget guide from the source.
In my opinon, can moderator give us guide or compilation how to customize device because i didn't see that thread in sgy forum (hope i'm not wrong) or maybe just link reference. Of course must put in faq or ultimate tutorial because this is just for newbie.
there's also a negatif effect of using full odexed ROM. it takes a lot of space in /system. in my case, I remove all bloatware and useless app and got only 20-15 mb free space in /system. btw, if you want to see which app is safe to removed, you may see hybrid ROM app list. he remove almost everything in this ROM (lol). I thought we can't put a tutorial for compiling a ROM. it would be huge and difficult to understand for a noob (just like me). you should PM'ed the dev to teach you how to make a custom ROM.
Aroma Installer can use on SGY..
--deleted--