hey you guys,
i'm using a rom i created which is based off dwang 1.17.1, and i'm trying to get the eclair browser like in cyan's build. to run on dwang.
i tried adb pushing... Browser.apk to /system/app/ and libwebcore.so /system/lib
but i reboot and it hangs on the initial start up screen. is there something i'm missing? or is there a bigger issue like perhaps an incompatible framework?
thanx in advanced
echo
the libwebcore.so is also dependant on a certain framework (though I can't remember which) jar and you'd also need libskia and libskiagl from cyanogen's build to get the browser to run.
Thanks for the reply
When I get home imma push thoses libs to the build and I'll post back with the results
Related
I use the pdfviewer from htc quite often, as it is really the only pdf viewer that works well with mathematical typesetting. This was the only thing that disappointed me with the official 1.6 release, and would love to install it. I know I need to push FilePicker.apk to /system/app and PDFViewer to /system/app, in addition I know that I need to push a new libpdfreader.so file, this is where I do not know how to procede. Since Akirah has the pdf viewer on his rom, I am tempted to just push files from his rom. Is there a reason this would not work? Any help would be greatly appreciated. Thank you.
I have the same problem on official firmware ADP1... any ideas ?
when I try run it, I get "force close"
im going to try and push this. i will report back my results
ok the .so file goes into system/lib i just pushed the files and im rebooting now. when its done i will report back
ok it fc, but i think we might need the framework i just need to know witch ones to push
yeah I am definitely missing the pdfviewer any help would be appreciated, heck tell me what I can do to contribute
yes i miss the pdfviewer from htc too. i've install other pdf viewer but it doesn't work with gmail too.
anyone have the solution either enable any pdfviewer to associate with gmail or put back htc.pdfviewer into donut?
i am using this 1.6 rom at the moment. since it's the most stable one so far. others 1.6 rom just keep crashing or with minor problems
http://forum.xda-developers.com/showthread.php?t=567023
Our devices don't have very much flash memory and it's easy to fill up /data with apps but here is a quick solution that can give you a bit more space.
In /data is a directory called dalvik-cache, this is a cache of the classes.dex from every app on the device, including those in /system.
On most android devices this doesn't happen, the system applications and the framework are stored as optimised dex files with a .odex extension.
People have spent a lot of time figuring out how to recreate the apks from the odex files and this is good if you have enough space to put all your apps on the device twice because it allows them to be easily swapped for theming.
The attached script goes through each app and jar in /system, creates an odex file and deletes classes.dex. It will give you about 30M extra space on /data while making /system about 10% bigger.
To run it do the following:
Backup you device
Make sure you have at least 15% free on /system, this is important because if you run out of space things will go badly wrong.
unzip odex.zip and then do:
adb push odex /data/odex
adb shell /data/odex/odex.sh
Wait till it finishes and then reboot the phone.
Another reason for odexing is that it boots very quickly and when testing kernels its nice not to have to wait too long.
If you want to see a simple odexed system try this:
http://www.mediafire.com/download.php?qjyniynyqzz
Rename it to androidinstall.tar and it will give you the donut system in the attached screenshots.
The main disadvantage of odexing is that it means you can't change the theme without reinstalling /system so find a theme you like before doing this to your device.
Thanks to Paul O'Brien for writing the original script.
Have fun.
dzo, once again, Thank you.
This should provide ALOT more breathing room in Eclair and Sense builds. Not to mention more flexibility for ROM devs too.
Thanks!
so would this only be useful for people who are making roms and stuff like that I'm kinda a noob still sorry
Unfortunately with my eclair build, /system is almost full
App2SD or /data on sd card look better
but that's device dependant
thank you for the tip anyway
I was about to ask if this will mess up the zipaligning but then I looked a the script and it also does zipaligning.
jadenj5 said:
so would this only be useful for people who are making roms and stuff like that I'm kinda a noob still sorry
Click to expand...
Click to collapse
The end user could run it, too...
Any thoughts on adding this to the install menu? That way you could install system, apply themes, then odex.
I updated the system tar in the first post to fix the broken calendar. I've been running this on my primary phone for a few days now and it seems much faster than it was. Perhaps there's are fewer file accesses with an odexed system and it needs to keep less data in the fs cache. Whatever the reason, give it a try.
is there anyway to do this from the phone without adb?
Include in vogue tools?
Thanks DZO, great that more performance can be squeezed out of our aging devices!
Just a thought: Could this be included in Vogue tools?
Two strange things with this build (on a Kaiser and I've added Wifi so maybe that has to do with it?)
- It never sleeps, I haven't run any Donut build for very long but I think I had this issue when trying the Warm Donut once.
If I turn off the screen (or if it times out by itself) this shows up in /dev/kmsg:
stop_drawing_early_suspend: timeout waiting for userspace to stop drawing
- When I run GPS Test and use the time screen the updates are irregular and sometimes skips a couple of seconds and sometimes several updates comes quickle after each other (with less than a second between them). I actually spent some time debugging my GPS code before I tried on eclair and realized it was not the GPS code that was causing it.
Perhaps both issues are related. I've a panel 1 Kaiser.
Other than that it feels very quick and snappy but no sleeping is terrible for the battery life.
Oh, and I tried turning off both wifi and background transfer but that doesn't help.
Tried this on Incubus's Tattoo and it got to HTCCamera.apk and failed:
Code:
--- BEGIN 'HTCCamera.apk' (bootstrap=0) ---
--- would reduce privs here
--- waiting for verify+opt, pid=3751
--- END 'HTCCamera.apk' --- status=0xff00, process failed
Unable to create '/tmp.odex': File exists
rm: cannot remove '/data/dalvik-cache/*': No such file or directory
It repeated Unable to create '/tmp.odex': File exists but i removed them from the code above because it's not necessary to have them in there 9473975394 times.
I rebooted and reinstalled the system to be safe.
preardon said:
Tried this on Incubus's Tattoo and it got to HTCCamera.apk and failed:
Code:
--- BEGIN 'HTCCamera.apk' (bootstrap=0) ---
--- would reduce privs here
--- waiting for verify+opt, pid=3751
--- END 'HTCCamera.apk' --- status=0xff00, process failed
Unable to create '/tmp.odex': File exists
rm: cannot remove '/data/dalvik-cache/*': No such file or directory
It repeated Unable to create '/tmp.odex': File exists but i removed them from the code above because it's not necessary to have them in there 9473975394 times.
I rebooted and reinstalled the system to be safe.
Click to expand...
Click to collapse
it might have something to do with most of the apk's already being odexed
I've posted an odex:ed and zipaligned CM5.0.7 port here: http://forum.xda-developers.com/showthread.php?t=700669
It also odexes every app in /data/app on boot (and clears the dalvik cache).
great donut build!
Thanks Dzo, you managed to pull together a great, snappy no frills donut build! it is fantastic on my Kaiser - and it is only a by-product of yet another great contributions of your! Thanks!
how is this donut build for use?
thoughtlesskyle said:
how is this donut build for use?
Click to expand...
Click to collapse
Great, I am using it daily on my kaiser at the moment. I understand that Kalt_Kaffe had problems with sleeping and battery life, but it works fine for me.
yea i shouldnt have the sleep and battery life problems because i run a vogue and they do things a little differently.
i wish i wasnt changing builds like every other day anymore
this is an excellent vanilla donut build dzo. it's very responsive and stable running from my sd card on the vogue so far. i really like myn's warm donut rom but it would frequently lock up requiring a restart; not the case with this build. thanks.
edit: is it possible to run the odex script again considering that i've been funning this build on my sd card? i wanted to odex the additional apps i added since the first install. also, would i have to manually remove the odexed files after updating an apk?
Had this running for a day on my old Kaiser and it's nearly as fast as my Hero! Fantastic work! Thanks!
This is the "snapiest" android build I have run on my vogue.
loving it thus far.
This patch is to provide fully deodexed app and framework for users of the new 1.36.605.0 OTA (stock 2.1 Sense).
Nothing has been stripped out or changed, this is completely stock. To be clear, it is NOT a full ROM and will replace your /system/app and /system/framework folders completely. If you have added anything to these directories it will be removed.
As always, you should perform a nandroid backup before applying the patch.
http://www.multiupload.com/HAI18ED91X
<Insert usual disclaimer about not taking responsibility here>.
Worked fine for me. Initial boot took several minutes, so it appears your droid eye is frozen and it also got stuck at the HTC Incredible white screen for a few seconds longer too.
So far only problem The keyboard doesnt work. Get a FC on com.htc.android.htcime
Thanks for providing this.
Can't optipng keyboard folks...it will break it every time.
adrynalyne said:
Can't optipng keyboard folks...it will break it every time.
Click to expand...
Click to collapse
I ran HTC_IME.APK through xUltimate and deodexed it there and it works fine now.
I'll attach it here for everyone, seems to work just fine on my phone now.
just reboot into recovery. I suggest the free app on market called Quick Boot. It has option to boot right to recovery or bootloader.
Put HTC_IME.apk in your tools folder where ADB is located
adb shell
rm /system/app/HTC_IME.apk
exit
adb push HTC_IME.apk /system/app/
Deodexing is fine, the problem is when folks try to use optipng on it.
adrynalyne said:
Deodexing is fine, the problem is when folks try to use optipng on it.
Click to expand...
Click to collapse
Whats optipng?
It compresses the png images inside the apks. A lot of the deodex tools out there optimize (zipalign) and optipng as well.
This allows you to get the performance increase from zipalign, but lowers the size as well.
Zipalign actually increases the size of an apk.
I'm using the vanilla sms program. can I remove the stock hero dialer and use the vanilla one? when I go into my epst settings and have to enter my msl, I get a blak dialer of sorts.
edit: can we use somethign from an eris or similar device?
edit2: i downloaded the 'nexus-like' dialer from this post. havent pushed it yet, pretty sure its for gsm
what rom are you running. CM6 is all AOSP so the stock android dialer is in there. I attached both phone and contacts. Just adb push xxxxx.apk /system/app or adb install xxxxx.apk
unCoRrUpTeD said:
what rom are you running. CM6 is all AOSP so the stock android dialer is in there. I attached both phone and contacts. Just adb push xxxxx.apk /system/app or adb install xxxxx.apk
Click to expand...
Click to collapse
im using nfinites .6odex version with a darch oc kernel. i pushed the vanilla messages app and it worked alright. will this work the same way and do i need to delete the originals in the phone via adb prior to pushing? long sentence. thank you thank you
well I tried pushing those over after I deleted phone.apk. couldn't find anything called contacts.apk to delete. I pushed them both and neither seemed to work. in fact phone.apk did not work. seemed like it couldn't find service...
I attached both phone and contacts.
Are these apk's the ones that come with CM6 RC1 already ?
In all of the AOSP-apps-on-Sense discussions I've read through, people have always have trouble getting contacts/phone working.
c00ller said:
In all of the AOSP-apps-on-Sense discussions I've read through, people have always have trouble getting contacts/phone working.
Click to expand...
Click to collapse
yeah, they didnt work for me...
I was wondering if it would be possible to take the Messaging .apk from a 2.1 ROM, and push it onto a 2.2 ROM, replacing the 2.2 Messaging app. I don't really like the 2.2 one, as it lags for me, and I can't really change the font sizes or anything.
Also, is it possible to take a 2.1 LatinIME.apk and do the same thing? These are the only two things that I don't really like about Froyo ROMs, because they are both slow on my phone.
Thanks!
I'm no dev or anything so I'm not 100% sure but I think it can be done. I just don't know if it would run I read somewhere where people tried to push apps from a different build and it FC's when the app starts. Also, I was looking into getting the froyo messager on a donut rom to see how it would run and i found this http://forum.xda-developers.com/showthread.php?t=752604. I opened it up to see what files we're flashed to get this and it's just the mms.apk. So I'm guessing what you said can be done by getting the mms.apk from a Eclair rom and push it into your system/app/ folder, The question is will it run though?
Ianlikescake said:
I'm no dev or anything so I'm not 100% sure but I think it can be done. I just don't know if it would run I read somewhere where people tried to push apps from a different build and it FC's when the app starts. Also, I was looking into getting the froyo messager on a donut rom to see how it would run and i found this http://forum.xda-developers.com/showthread.php?t=752604. I opened it up to see what files we're flashed to get this and it's just the mms.apk. So I'm guessing what you said can be done by getting the mms.apk from a Eclair rom and push it into your system/app/ folder, The question is will it run though?
Click to expand...
Click to collapse
I think I'm just gonna try it. I'll adb pull the original MMS.apk first, and if the pushed one doesn't work, I'll just push the original back in.
EDIT: Nope, doesn't work.
skate4lyph said:
I think I'm just gonna try it. I'll adb pull the original MMS.apk first, and if the pushed one doesn't work, I'll just push the original back in.
EDIT: Nope, doesn't work.
Click to expand...
Click to collapse
It was worth a shot.