Database Users

Trying to get Camera from 5.0.2Hr5

Hi there,
I tried running the Camera from Haykuro's build on my image.
After copying libcamera.so libqcamer.so and libcameraservice.so to /system/lib and changing the Camera.apk in /system/app my Camera and Camcorder disapperead, somebody can tell me the trick?

I don't know what image you are running, but it isn't that simple. The HTC camera.apk requires lots of htc frame work libraries to work. You will have to edit and repack your own boot image to include the com.htc*.jar libraries into class path, and the add and replace some of those libraries to your image. It will require lots of time to test and debug what is missing. It definitely isn't as simple as replacing few .so files and the apk. By the way I couldn't get it to work either but I gave up when I realized I had to rebuild boot.img. Haykuro will probably be able to get it to the adp 1.5 image soon.

I have read somewhere where Haykuro posted this to use H build cam. He did state that it's not quite 100% working and that he'll add this to the new 1.5H build.
adb shell reboot recovery
adb shell mount /system
adb shell rm /system/app/Camera.apk
adb shell rm /system/lib/*cam*.so
adb push libcamera.so /system/lib
adb push libcameraservice.so /system/lib
adb push libqcamera.so /system/lib
adb push Camera.apk /system/app
adb push HTC_Gallery.apk /system/app
adb shell reboot
t4c said:
Hi there,
I tried running the Camera from Haykuro's build on my image.
After copying libcamera.so libqcamer.so and libcameraservice.so to /system/lib and changing the Camera.apk in /system/app my Camera and Camcorder disapperead, somebody can tell me the trick?
Click to expand...
Click to collapse

Hi there,
Thanks for your replay.
I got cam working but got bad problems with force close everytime I try to make some settings. After some tries the camera won't come back up again, what I did:
copy system/lib/*cam* to my build
Camera.apk
HTC_gallery.apk
modified /system/etc/permission/platform.xml for finding the pimlib.

t4c said:
Hi there,
Thanks for your replay.
I got cam working but got bad problems with force close everytime I try to make some settings. After some tries the camera won't come back up again, what I did:
copy system/lib/*cam* to my build
Camera.apk
HTC_gallery.apk
modified /system/etc/permission/platform.xml for finding the pimlib.
Click to expand...
Click to collapse
If you wouldn't mind, send me your platform.xml ([email protected]) I'm 90% sure I know how to fix it to work. Db files are usually the root of all force closes. Settings, acore, messaging... if you have a db with variables that don't exist or missing ones that were added to the apk a crash occurs. I am pretty sure I know what files to fix and we can pack an apk for this...

Hey Twistedumbrella,
thank for your answer and your help, I just sent the xml file.
I am very excited...
Regards

I'd love to get the HTC camera working on the JF 1.5 build. All the camera image adjustments were great. Lemme know if you need someone to test things.

Please Post The steps & Platform.xml Whatever U Did
I am Gona Make A Seperate Thread Of All The apps Ported From Haykuro's Sapphire Builds To JF 1.5
I have Currently Ported The H-Virtual Keyboard To JF 1.5

Yeah i have been waiting for someone to do this...
if you need tester i will gladly do it... =D

ATM I wait for twistedumbrella, he got the cam working but I am completly stuck with this thing.
H cam will make photos but if I try to configure something the cam close forces all the time.

t4c said:
ATM I wait for twistedumbrella, he got the cam working but I am completly stuck with this thing.
H cam will make photos but if I try to configure something the cam close forces all the time.
Click to expand...
Click to collapse
Packing it into an update and testing as we speak

I got the force close problem.
Does anyone find out how to fix it ?
I am running JF 1.5, I push all the .so files also add files into /system/framework
and replace the platform.xml with the one online said for the JF 1.5 HTC app.
The camera will run into a Gray mode, and if I clicked on any icons it will show "force closed"....

[Q] Themes on HD2

Since we are not able to boot into recovery mode and run update.zip is there a way to manually apply themes to the Desire builds we are using?
Such as [MOD] Smooth Sense Icons v.1.0 (now with screenshots)
Thanks in advance.

+1
i have been asking this question since day 1..and no honest reply

I'd love to know how to skin android full stop I cant even get my hd2 to connect in usb mode

well...the only way to apply some themes is to replace framework-res.apk into system/framework/framework-res.apk...doing this with root explorer has no succes even if you ADB it..this will brick your build and u have to install again the whole system.ext2...!!everywhere is explaining that first phone must go into recovery mode to apply it..!!so,till now cant have any solution but only wait to make a function to have the possibility to run the phone into recovery mode..!!Be patient..soon we'll have it!

[★] said:
I'd love to know how to skin android full stop I cant even get my hd2 to connect in usb mode
Click to expand...
Click to collapse
What build/zImage are you using? The latest zImage allows for USB internet sharing tethering and USB file transfer.

jjones1983 said:
What build/zImage are you using? The latest zImage allows for USB internet sharing tethering and USB file transfer.
Click to expand...
Click to collapse
I dont know what a zimage is (I know nothing about android ) but Im pretty sure my current build is a shubcraft one

yes..
i have even tried with droid exployer and it bricks the rom..it boots the at the android screen it just flashes black..dont understand..im using darkstone sense rom..he has the espresso bar..and i cant add anything too it

[★] said:
I dont know what a zimage is (I know nothing about android ) but Im pretty sure my current build is a shubcraft one
Click to expand...
Click to collapse
from what I've gathered a zimage is based around the kernal & drivers, with shubCRAFT you can connect via USB as long as its on debug.

11calcal said:
from what I've gathered a zimage is based around the kernal & drivers, with shubCRAFT you can connect via USB as long as its on debug.
Click to expand...
Click to collapse
ahh thanks and how do I put it into debug?

edangel said:
well...the only way to apply some themes is to replace framework-res.apk into system/framework/framework-res.apk...doing this with root explorer has no succes even if you ADB it..this will brick your build and u have to install again the whole system.ext2...!!everywhere is explaining that first phone must go into recovery mode to apply it..!!so,till now cant have any solution but only wait to make a function to have the possibility to run the phone into recovery mode..!!Be patient..soon we'll have it!
Click to expand...
Click to collapse
It's possible to change framework-res.apk through the terminal, can't say this will work for everyone and it may completely screw your android build, so a titanium backup couldn't hurt. This was done on shubcraft 1.4d to theme back to stock android (if your looking for the framework, it's somewhere in the shubcraft thread).
1. Place your new framework-res.apk in the root of /sdcard.
2. Run terminal.
3. su
4. mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
5. cd /sdcard
6. cp framework-res.apk /system/framework
Reboot and hopefully success.

gardndj said:
It's possible to change framework-res.apk through the terminal, can't say this will work for everyone and it may completely screw your android build, so a titanium backup couldn't hurt. This was done on shubcraft 1.4d to theme back to stock android (if your looking for the framework, it's somewhere in the shubcraft thread).
1. Place your new framework-res.apk in the root of /sdcard.
2. Run terminal.
3. su
4. mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
5. cd /sdcard
6. cp framework-res.apk /system/framework
Reboot and hopefully success.
Click to expand...
Click to collapse
DO you know of any guide anywhere which tells us where to get the android sdk and how to exactly set it up with adb on windows 7 so we can skin our android hd2's? I cant find much

all those guides
[★] said:
DO you know of any guide anywhere which tells us where to get the android sdk and how to exactly set it up with adb on windows 7 so we can skin our android hd2's? I cant find much
Click to expand...
Click to collapse
are for phones that can be rooted and flashed with recovery..for us on the hd2 we HAVE to adb every file 1 by 1...sucks..and even the terminal method..you will see errors on your phone..i wish darkstone would just say how he put the espresso on his rom.

Go to market and Download ROM Manager from Clockworkmod it's free.
Put the theme on the root of the SD
open ROM Manager
click install from SD
pick out the theme you just put it.
Reboot

themes are ROM/framework specific which is why certain themes are only available for certain ROMs. shu8i builds are based off of cyanogen and are therefore the easiest to theme IMO. I have done a theme thread for that particular set of builds and have had great feedback from users.
So FWIW, a theme cannot be applied to just any ROM. If you want to get into it, you will need to find and extract the .PNG files from the framework-res.apk , pull the framework-res.apk from the build you are currently running, replace the images, and replace the framework-res.apk in your build with the patched one with the new .PNG's
there are plenty of TUTs on XDA explaining how to theme, only difference is us HD2 users have to manually push the files instead of using the convenience of an update.zip that is flashable in recovery.

Moved you guys over to general.. Best of luck!

makomek said:
Go to market and Download ROM Manager from Clockworkmod it's free.
Put the theme on the root of the SD
open ROM Manager
click install from SD
pick out the theme you just put it.
Reboot
Click to expand...
Click to collapse
I understand that this thread is old, but I just found it. Trying to install a new framework-res.apk to my device using this method. I have it in a zip file (which is the format that would be used on a normal device to flash it from recovery mode).
Well I tried this; it lets me choose the theme (zip file) that I want, and it then prompts me to choose OK to reboot in recovery mode and continue the installation. Nothing happens when I choose OK.
Any further info on how to do this? What am I doing wrong?

Flashlight Preinstalled in Vodafone Froyo release

Hi,
Can anybody extract the APK for the LED Torch app preinstalled in Froyo?
I saw that the one include with Froyo on the Desire works with a Desire with Eclair. (But doesn't work with my Legend) So I would like to check if the one included in Froyo for the Legend will also work with the Legend on Eclair.
The package name is com.htc.flashlight
Thanks!

U don't have to wait....
Try this APP: Lamppu
But first u have to (Soft)root your Legend with (Universal Androot)
After that, install superuser APP. Now start Lamppu and allow superuser rights...
Now u can use your LED as torch.
Tried it self on my legend v.2.1

Sure about the name?
The only thing I found in the Modaco ROM was Flashlight.apk
Then again...I have no clue what I am doing

above file is not working

Yeah it doesn't install

Ok gentlemen, one more try.
Extracted, re-zipped and signed the apk using apk-manager.
Removed the system app from my phone using TitaniumBackup and installed the signed apk through Root Explorer.
Works for me. No guarantee that it does for any other ROM or Android version though.
Sorry for the video but I just found out how to do screencasts and love it
Its German but you should be able to understand it.
Notice that it is now uninstallable and listed as downloaded app.

denisman said:
Ok gentlemen, one more try.
Extracted, re-zipped and signed the apk using apk-manager.
Removed the system app from my phone using TitaniumBackup and installed the signed apk through Root Explorer.
Works for me. No guarantee that it does for any other ROM or Android version though.
Click to expand...
Click to collapse
Installed and ran for me in stock 2.1 but it didn't do anything with the flash when playing with it

Thanks for trying!
This one is installing correctly, and also loading correctly, but it doesn't light up the LED.
So it isn't working

Are you phones rooted?

First of all, you have to have deodexed apk and second, you need to set right permissions in sysfs.
Sent from my HTC Legend

BlaY0 said:
First of all, you have to have deodexed apk and second, you need to set right permissions in sysfs.
Sent from my HTC Legend
Click to expand...
Click to collapse
The apk is deodexed. As for the permissions. No clue how to set them right
Had to read up an hour last night just to learn enough to extract it. Big newbie here hehe. Guess I'll check some threads about sysfs permissions and try it again later.

Sysfs is everything under /sys directory. File /sys/class/leds/flashlight/brightnes should have read-write permission set for everyone.
Sent from my HTC Legend

BlaY0 said:
Sysfs is everything under /sys directory. File /sys/class/leds/flashlight/brightnes should have read-write permission set for everyone.
Sent from my HTC Legend
Click to expand...
Click to collapse
Ahhh thanks! I guess I understand now.
Ok I just flashed whitetigerdk's rev03 ROM which is a rooted 2.03 ROM.
Than I did the following in adb shell:
Code:
chmod 777 /sys/class/leds/flashlight/brightness
checked permissions with:
Code:
cd /sys/class/leds/flashlight
ls -l
and it has rw permission for everyone now.
Code:
-rwxrwxrwx root root 4096 2010-12-01 16:29 brightness
Problem is, that booting the phone resets the permissions.
EDIT:
I just repeated the procedure while the phone was booted in normal mode.
Permissions successfully changed AND flashlight is working correctly, including all three different light settings!
Still, a reboot resets the permissions.
Guess I have to find a way to make this change permanent now and all is done
Hah so cool. Never used chmod or any other linux command until today. Had to google everything while I was testing. Nice how much one can learn here.
Another EDIT:
Found something else that is interesting.
http://developer.android.com/reference/android/Manifest.permission.html#FLASHLIGHT
Would adding this to the AndroidManifest.xml help aswell? I'd do it myself but I have to work soon. Just tried it decoding the xml with AXMLPrinter and adding it. Unfortunatly I don't know how to save the xml in the right format again and just saving it corrupts the apk. If noone else wants to give it a try I'll check back after work.

denisman said:
Still, a reboot resets the permissions.
Click to expand...
Click to collapse
Yeah... this is done via init.rc which is inside initrd image. So you have two options... tweak init.rc (you would need to unpack boot.img image and extract initrd image, edit init.rc, make new initrd image and construct back boot.img... this can all be done in one swoop with dsixda's kitchen) or make a script that is run every boot (we are doing it via run-parts which also requires editing of init.rc... once again dsixda's kitchen can add this functionality in a single swoop)...
As for "android.permission.FLASHLIGHT" I'm not sure about it as I can see that HTC is doing it avoiding it (setting permissions to 666 by default in FroYo)...
If you want decoding/encoding xmls use ApkManager. It's a nice CLI tool that can decompile and compile apks back...
You are quite a fast learner, congrats.

Back home Got pretty late.
I don't actually need this since I am running a rooted Froyo ROM anyways but thought it would be an interesting task to get this working for others to easily use it and for me to learn more about Android. The first option sounds like it would require a bit too much end-user activity and would be limited to a certain set of ROMs if I understand it correctly.
Leaving the second and third option as the most user-friendly ones I guess.
I will read up more on init.rc and ways to script for it tomorrow. Sounds like a very powerful "tool" to know.
For now I will concentrate on the XML. Might be the most comfortable and ROM-independent way if I get it to work.
BlaY0 said:
As for "android.permission.FLASHLIGHT" I'm not sure about it as I can see that HTC is doing it avoiding it (setting permissions to 666 by default in FroYo)...
If you want decoding/encoding xmls use ApkManager. It's a nice CLI tool that can decompile and compile apks back...
Click to expand...
Click to collapse
Used Apk Manager to extract, zip and sign the apk in the first place. Really nice tool. Just didn't find an option to convert the xml from binary to readable, that's why I used AXMLPrinter2.jar which can do the conversion one-way but not back to binary.
I'll find a way
Thanks again for the input! Helped me a lot!

[Q] DSP Manager conversion request

Hi all,
Attached is the DSP manager for Villain Rom, when i try to install it on my sense desire 2.2 (Starburst) its giving parse error
is there anyone who can modify this for android 2.2, this version of DSP has enhanced functionality which we dont get with prior versions
any help is appreciated
regards
H

The DSPManager must be installed as systemapp afaik.
Either you put it into a flashable zip or push it with adb or copy it to system/app with root explorer and S-OFF

mate i have already got a DSP manager installed. I just want to replace it with this one.
Being it made for android 2.3 its not compatible with android 2.2
as i have no clue about development of android i hoped someone here could recompile this APK to be compatible for android 2.2

Don't know if it will work for you, but I edited the minSDKversion from 9 to 8 in AndroidManifest.xml.

thanks mate, i will check and let u know if this works
cheers for the effort
regards
H

it works mate, thanks a billion...
is there a possibility for you to show me how this can be done. perhaps a link to tutorial.
thanks again for your help.
Sent from my HTC Desire

oops, too quick to respond, it is force closing since I have rebooted my desire.
any suggestions?
Sent from my HTC Desire

can anyone help.... ?

anyone?
Sent from my HTC Desire using Tapatalk

come on guys
Sent from my HTC Desire

There may be other software dependencies that it relies on to function properly. If that isn't the reason, then you could try clearing the apps data/cache in settings-applications-manager applications and seeing what that does.
If you would still like to know what I did to make it work, I could write a quick guide later today of what I did.

I would like to know how you made it work, since I want to use it on my LG Optimus 2X but when I install the apk I got from the cyanogen CM7 .zip for another phone it doesn't work...

I think theres one more file for the cyanogen DSPmanager.
system\lib\soundfx\libcyanogen-dsp.so
Read from an Oxygen thread post that you need to put that file in too.
I have both .apk and .so files on my Desire with Oxygen and it works.

im using oxygen 2.0.3 and i would love the dsp manager, what files are required.....??

To make it work with froyo, I used apktool on the apk, then I opened up the AndroidManifest.xml with PSPad, I edited the android:targetSdkVersion to be 8 instead of 9 (8 is the SDK version for froyo), then I recompiled the apk with apktool, signed, and pushed/installed on the phone.
In the DSPManager.apk from CM7.0.0, you need to edit the line android:minSdkVersion to be 8.
I have no way of testing this (as I am using CM7 RC4 and do not feel like installing a froyo ROM or a ROM without DSPManager), but it has the .so file mentioned above and the DSPManager.apk from CM7.0.0. Flash the file in recovery, if for some reason it will not flash, then push the files with adb or use root explorer and set the permissions.
Code:
adb remount
adb push libcyanogen-dsp.so /system/lib/soundfx/libcyanogen-dsp.so
adb push DSPManager.apk /system/app/DSPManager.apk
adb shell reboot
http://bit.ly/gLGIxj
Let me know whether or not this works.

flashing the zip, the phone would freeze at the bootloader, but pushing the files it works a treat thank you so much, i can finally make use of my headphones.......

Well it seems we might be getting closer:
http://forum.xda-developers.com/showthread.php?p=12884327#post12884327
Has someone tested this yet? Someone uploaded the latest one with an edited .so file. Maybe someone can test if this works on 2.2.2. LG Optimus X2 without patched libaudioflinger.so?
Kind regards,
Xav...

i tried it but all i get is FC...
LG Revo. Android V 2.2.2

tracker01 said:
i tried it but all i get is FC...
LG Revo. Android V 2.2.2
Click to expand...
Click to collapse
I got the same problem Samsung Omnia 2 Android 2.2.2
Older versions work fine (I got that .so file already in it's place) I just want the one with more bass just like my friend has on his LG GT540 android 2.3.5

Transplant stock radio layer

I'm not sure if this is the right place to post this, but here goes.
I was running Mokee 4.3, and loved it; but the battery life was terrible.
So I went back to White Rabbit 2.11.
Now I'm getting lots of reboots due to Errors in Telephony Layer.
My question is: Is it possible to take the RIL from the stock ROM and replace it in White Rabbit?
If so, which files should I copy?
Thanks

Rijidij said:
I'm not sure if this is the right place to post this, but here goes.
I was running Mokee 4.3, and loved it; but the battery life was terrible.
So I went back to White Rabbit 2.11.
Now I'm getting lots of reboots due to Errors in Telephony Layer.
My question is: Is it possible to take the RIL from the stock ROM and replace it in White Rabbit?
If so, which files should I copy?
Thanks
Click to expand...
Click to collapse
Copy the bp_nvm_default folder from system/etc into the ROM.
Sent from my Nexus 7 using Tapatalk

hotdog125 said:
Copy the bp_nvm_default folder from system/etc into the ROM.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Thanks. I'll give this a try.

Update - progress so far:
As per advice from hotdog125, I copied the bp_nvm_default folder from a nandroid of the (rooted) stock ROM.
I found it in the /system/etc/motorola folder in this ROM
It appears to be working so far - I will keep a close eye on it for telephony errors...
If others want to try the same, here are the steps I took. (YMMV)
Extract the bp_nvm_default folder from the stock ROM (in /system/etc/motorola)
Rename to bp_nvm_default.stock
Copy to phone SD card
On the phone, copy from SD card to /system/etc/motorola
I had to chmod the folder to 755, and all the contents to 644 (again, YMMV)
Rename the existing bp_nvm_default folder to bp_nvm_default.bak
Rename bp_nvm_default.stock to bp_nvm_default
Reboot...
My phone booted up OK, and everything looked fine. So I decided to push a bit further. :fingers-crossed:
Reboot into recovery
Clear cache and dalvik cache
Reboot...
Again, I had success!
A few points:
Steps 4-7 were possible thanks to JRummy's ROM Toolbox Pro (great tool - worth every penny! :good
A message appeared saying changing permissions failed, but after refreshing the list, permissions were correct.
I had to chmod each file in the folder individually - a bit of a pain, but it only took a few minutes. (I tried it in the terminal, but that definitely didn't work).
Baseband has defaulted to Central Europe 3.4.2-145. I'll leave it on that one for now and see how it goes.
On the subject of Baseband, I'm in the UK and have these available under the GB heading:
3.4.2-117
3.4.2-11
2.51
T-Mobile 2.51
T-Mobile 2.21
3.4.3-3
4.5.1-85
Any recommendations from this list?
Thanks

Update:
No telephony reboots so far...
But the phone has got quite hot (while dark) on a couple of occasions.
Also, I couldn't get a connection to the Play Store this morning. Toggling Aeroplane Mode fixed it.
I might try one of the other basebands next.

Arrrgh! I spoke too soon!
RIL bug has struck 3 times since last night...
Damn... I thought I had this fixed.

RIL Bug is due to hardware issues. Changing the baseband will not help unfortunately
The best way to fix it is to use one of the later builds which have incorporated SlugZero's RIL patches
Sent from my MB526 using Tapatalk 4