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"....

[HOW-TO]--Stock Bootscreen w/ Sound

Well here we go, this will revert your bootscreen to the Stock Verizon Android Bootscreen with Sound.
(Verizon animation then waving droids, followed by the HTC animation)
!!!! THIS IS FOR ROOT USERS ONLY !!!!
This has not been tested with any Non-Root ROM!
This HOW-TO was put together on a Windows Machine, Please adjust your syntax if you are using linux.
This has been tested on the Plain Jane ROM (Thanks Jcase!!) And confirmed working on Ivan's ROM (Thanks pkopalek)
EDIT [6/9/10 @ 3:39pm EST]: THIS WORKS ON Eris-based ROMs ONLY at this time. I will be experimenting with other ROM's and will post my findings.
This Bootscreen was pulled from the Downgrade.zip included in this post:
Android Fourms
Please give credit where credit is due. All i did was get all together and write this HOW-TO.
1. Download this zip ... bootscreen_Stock_Sound
And Extract to any location on you computer. You should have a folder named bootscreen with some xml,mp3,and gif files.
2. if you have pushed a bootscreen to /data/local, delete it.
Code:
adb remount
adb shell rm /data/local/bootanimation.zip
3 Enter the adb shell and cd to /system/media and list contents.
Code:
adb remount
adb shell
cd /system/media
ls
Back up the bootanimation.zip located here.
Code:
cp bootanimation.zip bootanimation.bak
or delete it.
Code:
rm bootanimation.zip
Exit shell
Code:
exit
4. Now to push the animation to /system/media
<your-save-path-here> is where you extracted the RAR. When extracted you will have folder named bootscreen_Stock_Sound with a nested folder named bootscreen.
I downloaded the rar to the desktop on Win 7 so my path would be:
C:\Users\Lostbytes\Desktop\bootscreen_Stock_Sound\bootscreen
NOT: C:\Users\Lostbytes\Desktop\bootscreen_Stock_Sound\bootscreen\
as this will nest the folders.
Code:
adb push <your-save-path-here>\bootscreen /system/media/bootscreen
Wait for it to finish.
EDIT:For those having problems with a black boot screen, please enter the following to set the permissions on the bootscreen folder.
Code:
adb remount
adb shell chmod 775 /system/media/bootscreen
5. To Test.
Code:
adb remount
adb shell
bootanimation
PRESS Ctrl-C to return to the shell.
Now a creative person with the inclination, should be able to modify the contents of the bootscreen xml file to use custom sounds and animations. Have Fun All
TO THE DEVS:
Thank you for all your hard work day in and day out. Without people like you, this scene would not exist.

Have Fun
Have Fun Everyone!!!!!!

I've been thinking about this bootscreen for a long time.
Thank you for this.

And for what it's worth, with all the files in place,
my Evil Eris boot animation is just a blank, black screen.
Hmm..... I'm missing something.

I thought this had to be in a ZIP format...
After downloading ..it is a RAR file...

bukada said:
I thought this had to be in a ZIP format...
After downloading ..it is a RAR file...
Click to expand...
Click to collapse
This is not the common Bootanimation.zip!!!
Please read the directions, this is the old Style bootanimation format. (using a XML instruction sheet, NOT the desc.txt file w/ png in zip format) This allows much more control. You mush first back up or remove any and all Bootanimations on your phone.

pkopalek said:
And for what it's worth, with all the files in place,
my Evil Eris boot animation is just a blank, black screen.
Hmm..... I'm missing something.
Click to expand...
Click to collapse
Did you back up or remove the bootanimation in
/data/local
/system/media
also if /system/media already has a bootscreen folder delete it and replace it with the one from the RAR.
Bootanimation formats as far as i know are:
/data/local/bootanimation.zip
/system/media/booanimation.zip
/system/media/bootscreen/<XML,Gif,MP3 files>/
This bootscreen is the last format. It works on a ERIS running Plain Jane, Will post vid soon.

pkopalek said:
And for what it's worth, with all the files in place,
my Evil Eris boot animation is just a blank, black screen.
Hmm..... I'm missing something.
Click to expand...
Click to collapse
Same here. Followed the instrucations and only have a blank screen now during boot up. Is a step missing?

lostbytes said:
Did you back up or remove the bootanimation in
/data/local
/system/media
also if /system/media already has a bootscreen folder delete it and replace it with the one from the RAR.
Bootanimation formats as far as i know are:
/data/local/bootanimation.zip
/system/media/booanimation.zip
/system/media/bootscreen/<XML,Gif,MP3 files>/
This bootscreen is the last format. It works on a ERIS running Plain Jane, Will post vid soon.
Click to expand...
Click to collapse
All checkpoints check.
This is also pretty standard for all of Android, so I am baffled as to why we're getting black bootscreens!

pkopalek said:
All checkpoints check.
This is also pretty standard for all of Android, so I am baffled as to why we're getting black bootscreens!
Click to expand...
Click to collapse
I will recreate the procedure from the beginning . All i did was pull the original boot screen from Android 1.5 and push to my phone, Maybe i missed documenting something.....But it is a simple operation. Will post again soon.

Yeah, I see.
I even pulled apart downgrade.zip (which I have on my computer) and looked at it myself, just in case a file got corrupted or something.
I can't figure it out!
Maybe this needs to be turned into a bootanimation.zip for some ROMs?

pkopalek said:
Yeah, I see.
I even pulled apart downgrade.zip (which I have on my computer) and looked at it myself, just in case a file got corrupted or something.
I can't figure it out!
Maybe this needs to be turned into a bootanimation.zip for some ROMs?
Click to expand...
Click to collapse
Its possible, I will look into it some more, What baffles me is that works for me!!! It may be ROM dependent but i am just recreating the file structure with no modifications from the original. So, in theory the ROM should not matter.

I tried grabbing the /system/bin/bootanimation file from another ROM (so that the 'bootanimation' command would maybe work?) to see if that makes the difference, but it doesn't seem to.
It seems like something silly is missing! I even did a Root Explorer search for anything with the word 'boot' in it to see what could be causing the trouble, but I don't see anything at all! The only things with 'bootscreen' or words like it is in the /system/media/bootscreen/ folder that is there (because I put it there).
Baffling!

Here are screens of what i did, I recreated the whole process and it worked fine for me. Again i am running the Plain Jane ROM (Thanks to Jcase) if that matters.
link To Screen
Hope this helps!!!

I confirmed this DOES seem to work on normal Eris-based ROMs like yours (Ivan's 1.0, in my case)
but NOT on EvilEris.

pkopalek said:
I confirmed this DOES seem to work on normal Eris-based ROMs like yours (Ivan's 1.0, in my case)
but NOT on EvilEris.
Click to expand...
Click to collapse
Would you like me to post the bootanimation file from /system/bin?
maybe replacing this file with mine might solve the issue...
File located here........... Bootanimation
Please let me know if this resolves the issue. If not i will install EvilEris and try to recreate.

Same exact success rate.
I also had to chmod your 'bootanimation' to make it work, but that may or may not be related to me downloading/pushing it from a Windows machine.
Neither here nor there, just a black screen.
Blah.

pkopalek said:
Same exact success rate.
I also had to chmod your 'bootanimation' to make it work, but that may or may not be related to me downloading/pushing it from a Windows machine.
Neither here nor there, just a black screen.
Blah.
Click to expand...
Click to collapse
pkopalek, Would you please, in root explorer, goto /system/media/bootscreen and list its contents? there should be a bunch of files and NO folders. I thinks my code was nesting the files in a second bootscreen folder.

lostbytes said:
pkopalek, Would you please, in root explorer, goto /system/media/bootscreen and list its contents? there should be a bunch of files and NO folders. I thinks my code was nesting the files in a second bootscreen folder.
Click to expand...
Click to collapse
Nope. Exactly the contents it should have.
android_audio.mp3, android_audio.mp3_, boot.gif, boot.mp3, boot_animation.xml, etc etc etc.
Certainly no folders in here. Exactly the contents it should have.
/system/media/bootscreen
same contents as C:\Documents and Settings\Administrator.PAULSTERM1\Desktop\android\downloads\bootscreen
which is where I extracted the bootscreen contents (twice, once from your download, once from my own downgrade.zip. same results.)

pkopalek, Would you please, in root explorer, goto /system/media/bootscreen and list its contents? there should be a bunch of files and NO folders. I
Click to expand...
Click to collapse
Nope. Exactly the contents it should have.
android_audio.mp3, android_audio.mp3_, boot.gif, boot.mp3, boot_animation.xml, etc etc etc.
Certainly no folders in here. Exactly the contents it should have.
/system/media/bootscreen
same contents as C:\Documents and Settings\Administrator.PAULSTERM1\Desktop\android\downloads\bootscreen
which is where I extracted the bootscreen contents (twice, once from your download, once from my own downgrade.zip. same results.)
Click to expand...
Click to collapse
This may be obvious, but make sure to check the permissions on the folder itself.
Try this, then reboot.
adb remount
adb shell chmod 775 /system/media/bootscreen
-------------------------------------
Sent via the XDA Tapatalk App

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!

ATT 2.3.5 SystemUI Quickpanel

ATT 2.3.5 SystemUI
quickpanel_title_background.9 I Can not define

This is nice!
A few suggestions:
- Less icon spacing. Should fit at least 5 on the screen at once.
- No vibrate icon. It's unnecessary. Holding the power button works fine.
- Brightness control.

Thank you. Well done
Sent from my MB860 using Tapatalk

Hi can I install this on rooted locked atrix on 2.3.4!? I'm on UK retail. The thanks
Sent from my MB860 using XDA App

Wow. This is what I wanted.
Thank you

I'm on a rooted US ATT 2.3.4. How can I get this to install? I tried abd install, that didn't work...
--Q
EDIT: I think I figured it out. You have to go into /system/app and rename SystemUI.apk and SystemUI.odex to have .bak then copy the modified SystemUI.apk and then chmod 644 it. Rebooting now...will keep you posted!
EDIT2: Yep! Totally worked! GENIUS!! THANKS!

Do I really need to use adb or can do chmod by using some tool on phone?
Sent from my MB860 using XDA App

You can do all this with Root Explorer if you have it. Same idea.

I think the OP is trying to edit the SystemUI.apk to include more functions. If so, may take a look here. Not sure if that will help too much or not...?
for the other posting people, here's what I have been running for a while..
basically Darkside's stock SystemUI with a theme hacked together from thread mentioned above as well. MIUI Icon set I think is what he says...
To install:
Download file to C: or where ever(if downloaded to someplace else, fix path in the commands below).
Start Menu --> Run --> cmd
On Windows 7 (or XP): hold the Windows Key on keyboard and press R together. Input CMD and hit OK
On Linux: well, you know whats up
On MAC: unplug the computer and toss it out the window.. j/k. This wont work for you though. Follow normal procedure to use ADB in your teminal
Inside CMD Prompt, in this order:
adb push C:\SystemUI.apk /sdcard/SystemUI.apk
adb shell
su
/bin/mount -o remount,rw /system
cp /sdcard/SystemUI.apk /system/app/SystemUI.apk
chmod 644 /system/app/SystemUI.apk
exit
exit
adb reboot

Lack of ability to use a lot of smali. Or else can do more...

ein1002 said:
Lack of ability to use a lot of smali. Or else can do more...
Click to expand...
Click to collapse
I love the last one you've posted.
But could you please replace the vibration by the luminisity control?
And the order would be:
Wifi; Mobile DATA; Bluetooth; GPS, Brightness, Screen Orientation

Shaydar said:
I love the last one you've posted.
But could you please replace the vibration by the luminisity control?
And the order would be:
Wifi; Mobile DATA; Bluetooth; GPS, Brightness, Screen Orientation
Click to expand...
Click to collapse
I have no way to make the right moves Brightness：（
So I removed the BrightnessSettingButton
Leaving only the image resources
Hope someone can fix. And add this part.
sorry. My English is not good

Thanks, It does not matter anyway.
The Screen is so bright that I always set the brightness to its lowest.

malfuncion said:
I think the OP is trying to edit the SystemUI.apk to include more functions. If so, may take a look here. Not sure if that will help too much or not...?
for the other posting people, here's what I have been running for a while..
basically Darkside's stock SystemUI with a theme hacked together from thread mentioned above as well. MIUI Icon set I think is what he says...
To install:
Download file to C: or where ever(if downloaded to someplace else, fix path in the commands below).
Start Menu --> Run --> cmd
On Windows 7 (or XP): hold the Windows Key on keyboard and press R together. Input CMD and hit OK
On Linux: well, you know whats up
On MAC: unplug the computer and toss it out the window.. j/k. This wont work for you though. Follow normal procedure to use ADB in your teminal
Inside CMD Prompt, in this order:
adb push C:\SystemUI.apk /sdcard/SystemUI.apk
adb shell
su
/bin/mount -o remount,rw /system
cp /sdcard/SystemUI.apk /system/app/SystemUI.apk
chmod 644 /system/app/SystemUI.apk
exit
exit
adb reboot
Click to expand...
Click to collapse
Many many thanks! This needs to be in new thread. please post it or I will.
I really liked the darkside ROM, But I soft bricked my phone at least 15 times trying Arabic letters connecting solutions under 2.3.5. So I flashed the Aura ROM missing the quick panel from the Darkside ROM the most.
Not only I have the quick panel now with Aura 2.3.4, the icons also look cleaner/better.
Great job. Thanks to you and Nottach also!

CyberPunk7t9 said:
Many many thanks! This needs to be in new thread. please post it or I will.
I really liked the darkside ROM, But I soft bricked my phone at least 15 times trying Arabic letters connecting solutions under 2.3.5. So I flashed the Aura ROM missing the quick panel from the Darkside ROM the most.
Not only I have the quick panel now with Aura 2.3.4, the icons also look cleaner/better.
Great job. Thanks to you and Nottach also!
Click to expand...
Click to collapse
Any chance you upload your version and share it? I'm looking for exactly the same thing and sadly 2.3.5 Darkside ain't providing that.
Sent from my Atrix 4g using Tapatalk

Abu-7abash said:
Any chance you upload your version and share it? I'm looking for exactly the same thing and sadly 2.3.5 Darkside ain't providing that.
Sent from my Atrix 4g using Tapatalk
Click to expand...
Click to collapse
It's just the latest Aura ROM (found in the development section) + this awesome quick panel MOD.
Aura is based on 2.3.4. I noticed that arabic fonts were connecting properly in the system+browser with Aura ROM as-is. No framework.jar or lebwebcore.is hacks are needed with that ROM.
Root+Battery % icons MOD+No carrier logo MOD+proper Arabic font connecting+this quick panel MOD is pretty much what I want now in my Atrix. Currently happy to have all that.
Not to mention a lot of other plus features Aura ROM adds.

Hi,
I was using this mod on 2.3.4 and it was great! Just upgraded to Android OS 2.3.6 (att build 4.5.141) and it just boot loops until I replace it back with the original. Is there any way to modify this to work on 2.3.6? Or, is there a version around that I'm not finding that will work on 2.3.6?
Thanks!
--Q

Apktool problem MIUI v5

Hello to all devs
If someone can help me I would be very gratefull.
What I`m trying to do is to edit the values for screen brightness in framework-res.apk .
The problem is that after decompiling ,edit the values (values/array.xml) ,compiling and push to system/framework, after reboot the phone won`t boot anymore.It just stucks at the finish of the bootanimation.
So...please...can someone help me?

Do you get any warnings/errors while compiling? You could also try vrtheme instead of modding the apk.
Sent from my Nexus⁴ using Tapatalk 4 Beta

TToivanen said:
Do you get any warnings/errors while compiling? You could also try vrtheme instead of modding the apk.
Sent from my Nexus⁴ using Tapatalk 4 Beta
Click to expand...
Click to collapse
I installed the miui framework and other dependecies and succsessfully compile a new framework-res.apk.
The problem is that after I push the modded framework to system/framework and reboot the system won`t boot anymore.I don`t like how MIUI Team set the values for brightness.It`s too dark for me.And I wanted to "light" the display without any 3rd app from market.

aresbv2000 said:
I installed the miui framework and other dependecies and succsessfully compile a new framework-res.apk.
The problem is that after I push the modded framework to system/framework and reboot the system won`t boot anymore.I don`t like how MIUI Team set the values for brightness.It`s too dark for me.And I wanted to "light" the display without any 3rd app from market.
Click to expand...
Click to collapse
Did you set permissions after pushing? Making a flashable zip may be a good idea.
Sent from my Nexus⁴ using Tapatalk 4 Beta

TToivanen said:
Did you set permissions after pushing? Making a flashable zip may be a good idea.
Sent from my Nexus⁴ using Tapatalk 4 Beta
Click to expand...
Click to collapse
The permissions were set like this:
adb shell
cd system/framework/framework-res.apk
chmod 644 framework-res.apk
Before restart i`ve checked if the permissions were right and they do.
I don`t know where the problem is

aresbv2000 said:
The permissions were set like this:
adb shell
cd system/framework/framework-res.apk
chmod 644 framework-res.apk
Before restart i`ve checked if the permissions were right and they do.
I don`t know where the problem is
Click to expand...
Click to collapse
Hm, seems fine to me.
Can you please upload the modded apk and tell me which file you edited? Imma make a vrtheme zip for you to try.
Sent from my Nexus⁴ using Tapatalk 4 Beta

Here is the two files (framework-res.apk and framework-miui-res.apk). If you have free time and want to give a try,maybe you will manage to do it right.Edit anything in the values/array.xml and I will test to see if it works.
framework-res.apk
framework-miui-res.apk
I run on my laptop Windows 7 x64.Maybe this is the problem.But if the compiling is fine...i think this is not the problem.Maybe the signature of the apk or something like that would be the problem.
Thank you for your interest.

@aresbv2000
Here you go
The zip does not replace the entire apk. It sorta injects the arrays.xml into frameworks-res.apk. I've set every auto brightness step to 250 in order to easily find out if it works. If your screen lights up 100% after enabling autobrightness, the zip worked.
Then you must open the zip using and replace my proof-of-concept arrays.xml with your own.
Cheers!

TToivanen said:
@aresbv2000
Here you go
The zip does not replace the entire apk. It sorta injects the arrays.xml into frameworks-res.apk. I've set every auto brightness step to 250 in order to easily find out if it works. If your screen lights up 100% after enabling autobrightness, the zip worked.
Then you must open the zip using and replace my proof-of-concept arrays.xml with your own.
Cheers!
Click to expand...
Click to collapse
ok....thank you so much.i will install the zip as you made it.i will report to you if it worked.
please if you have time check this thread later to see if i posted any question for you.
thank you again

it is not working my friend
the screen stays the same as usual....too dimm.
i don`t know why but if i use velis autobrightness it seems that the color tones are changing also.and i spent a week just to calibrate my display the way I like it .thank you so much for your effort.i appreciate your efforts.

After a few hours and a lot of nervs i`ve succsessfully edited the values in array.xml, compile....and VOILA>>>it worked.
It took me some time to figure out what values should I set, but now is way better than was before.
All the credis goes to this and to you for your tips.
Thank you.
Forum moderator can delete this thread as the problem is solved

aresbv2000 said:
After a few hours and a lot of nervs i`ve succsessfully edited the values in array.xml, compile....and VOILA>>>it worked.
It took me some time to figure out what values should I set, but now is way better than was before.
All the credis goes to this and to you for your tips.
Thank you.
Forum moderator can delete this thread as the problem is solved
Click to expand...
Click to collapse
Sweet. I'm glad you figured it out
Sent from my Nexus⁴ using Tapatalk 4 Beta