Hi all,
I'm a LeeDroid HD user, and I've spent some time over the last few weeks tweaking the auto-brightness settings to maximise battery life. I've reached a point where I haven't found any problems with my settings for 4 or 5 days now, which I think is a pretty good test. It's on the low side under most light conditions, but I've tried to find a point where I can comfortably read the screen without holding it up to my face, and when outside, this includes wearing sunglasses.
Obviously screen brightness is a very personal thing, so you might not like where I've ended up. When you want to impress your friends with your awesome DHD, you can always override the auto setting and just crank up the brightness control manually
Sharing my settings is also not simple either, since it requires a mod to res-framework.apk, which is used for themes. So ... what I will do is show you a graph of my changes to so you can see what I'm doing:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(Left side of graph is a dark room, right side is the harsh West Australian sun)
And make a flashable zip available for Lee's default ROM, with no themes installed (Base_LeeDroid_Lower_Auto_Brightness_Patch).
And another flashable zip to use if you've installed the "LeeDrOiD Notification power widget" from the LeeDroid HD OP (LeeDroid-PNW-Lower_Auto_Brightness_Patch).
And I've already had a request to make one for the "Stock 1.84" theme from here, so that's also attached (Stock_1.84-Lower_Auto_Brightness_Patch).
If you have another theme/mod installed, I think that flashing the above will wreck it ... be warned!
If you have a specific theme/mod you're using and want to try my settings, just send me a link to it and I'll cook up a flashable zip for it ... it doesn't take long. Alternatively if you know what you're doing, I can provide my arrays.xml file and you can do it yourself.
ALL files in this post are to be flashed with cwm 2.5.1.3 ... I haven't tested with any other version.
Even though I've tested all these patches myself, I'm not an expert at this, so PLEASE PLEASE PLEASE take a nandroid backup first in case I've done something fundamentally wrong.
If you don't like my settings, you can either restore your nandroid backup, or if it was a theme specific patch, you could just apply the theme again.
If it all goes pear-shaped ... I TAKE NO RESPONSIBILITY!
Hope somebody (other than myself) can benefit from my experimenting
If any themers want to incorporate my settings, it's just a change to arrays.xml inside framework-res.apk, nothing else. I'll also attach my arrays.xml (zipped), feel free to use it. As a courtesy, please credit me for the auto-brightness settings If you use them.
As mentioned above, if anyone would like to patch this on top of a specific theme/ROM you have already flashed, just ask and I can cook it up. If you feel like making it easier for me, all I need is framework-res.apk, so if you have a link to just download that, you'll get your patch quicker than if I have to download the entire theme
If anyone has arrived here from the LeeDroid thread, be aware that these are NEW versions of the files, as the ones in that thread were based on the wrong version (they were too low in the 40-90-160 range).
Cheers all, any feedback is appreciated
I have since put together a DIY guide on how to mod the auto-brightness settings inside framework-res.apk yourself. Thanks to those who contributed. Here's the guide!
This was all done on myWindows XP SP3 machine.
1. Download and install a recent Java Runtime Environment (JRE), if you don't already have one. I won't go through those steps, google it. If you're unsure, you can always come back to this step later if it's not working.
2. Download APK Manager from here: http://forum.xda-developers.com/showthread.php?t=695701 ... there's probably lots of good info in this thread if you have questions later about this tool.
3. Unzip the file wherever you want, mine is just on my desktop.
4. I was advised to replace the version of apktool.exe in the 'other' folder with an earlier version. I don't know if this is necessary, and I don't know what version I now have ... possibly 1.3. ** Multiple people have needed to downgrade to the older apktool.exe that I use, so I have attached it to this post. Just extract apktool.exe from the zip and place it in the 'other' folder, replacing the existing apktool.exe.
5. OK, now you should be ready to go! Grab your framework-res.apk either from your phone, or straight from the ROM you've flashed if you haven't applied any themes. framework-res.apk can be found in /system/framework.
6. Copy your framework-res.apk into the "place-apk-here-for-modding" folder.
7. Run script.bat. If you see a text menu pop up then all is good. If you get an error then you've done something wrong! Probably related to your JRE.
8. Choose Option 9 - Decompile apk. Wait until it finishes. Minimise this window now, we'll come back to it later.
9. Go into your projects folder, and you will have a new folder there called framework-res.apk, double click it.
10. Navigate to res/values
11. Open up arrays.xml in a text editor such as Notepad++. Using Windows built in notepad app could cause issues due to Windows -> Linux compatibility issues.
12. Scroll down to the section where it says "<integer-array name="config_autoBrightnessLevels">". This is the section that defines the steps of the ambient light sensor. You probably won't need to adjust these values for now.
13. The next section down should be "<integer-array name="config_autoBrightnessLcdBacklightValues">", this is where the tweaks really begin. The values here relate directly to how bright the screen is at the steps defined in the section above. Minimum value is 1, maximum value seems to be 249, but that could be incorrect. Would make more sense for it to be 255.
14. Change these values as you wish, but change them to the same thing in all these 3 sections - config_autoBrightnessLcdBacklightValues, config_autoBrightnessLcdBacklightValuesUp, config_autoBrightnessLcdBacklightValuesDown.
15. The next 2 sections - config_autoBrightnessButtonBacklightValues, and config_autoBrightnessKeyboardBacklightValues do the same thing, except for the hardware buttons, and keyboard buttons (if present) respectively. Adjust these if you wish.
16. Save the file.
17. Navigate back to the root of the APK Manager directory.
18. Return to your APK Manager window.
19. Choose option 11 - compile APK.
20. When prompted if this is a system APK, type y. Hit Enter.
21. When prompted if you want to copy additional files, type n. Hit Enter.
22. Choose option 22 - Set Current Project
23. Choose option 2 - unsignedframework-res.apk
24. Choose Option 5 - Zipalign apk
25. Choose Option 24 - Quit. On my script version you have to choose option 24 twice. I assume it's a bug on my version, hopefully you won't have to do the same thing.
26. Congrats! You now have a modded framework-res.apk!! You'll find it in the folder "place-apk-here-for-modding", with the new name "unsignedframework-res.apk". Copy it somewhere else (eg. desktop) and rename it to framework-res.apk.
*** If you know how to copy the modded file into a pre-existing flasheable zip, then by all means go for it. If not, continue following the steps below to create a flashable zip in the UOT Kitchen ***
27. Go to the UOT Kitchen - http://uot.dakra.lt/kitchen/ Hopefully it's not busy and it lets you in! If not, you'll have to wait.
28. Go to the file upload tab and upload your new framework-res.apk file.
29. If this is a FROYO ROM that you're modding, then that's it! If it's a GINGERBREAD ROM, then you also have to grab SystemUI.apk and com.htc.resources.apk from your ROM or phone and upload these also. SystemUI.apk can be found in /system/app and com.htc.resources.apk can be found in /system/framework
30. Go back to the Summary tab, then click "Submit Work to Kitchen".
31. When it's done, download the file, boot into cwm, ***DO A NANDROID BACKUP***, then flash your file!
If you've done it right, you're auto-brightness settings should be applied!
If you get stuck in a boot loop, or it just doesn't boot at all ... lucky you have a nandroid backup!
Please note that as this thread progresses, newer versions of the files get posted which makes these ones in the OP redundant. I'll leave them up for now just in case someone needs them, but in general, you'll want to dig deeper into the thread to get flashable files for newer versions of ROMS.
Excellent post.
I will take a look at your final arrays.xml, but I'm happy (so far) with the one I've cooked up with modified at the dimmer end of the scale.
Over the next day or so, I'm going to try and add extra steps (double) into the array, making a more linear or at least a smoother curve. As you said in Lee's thread, not sure if it's up to the build of the kernel.
Even if I can successfully add the extra values and flash, maybe I won't notice if its really working and the values are applied or they are just ignored by the ROM or kernel? What's the worst that can happen? Backup...........
Using the GPS Status & Lux Meter I was able to double check the phone light sensor invrements in:
10-40-90-160-225-320-640-1280-2600-10240 (pls correct me if I've missed any out)
Would the 'driver' for the light sensor need to be modified for extra steps (ie. 10-25-40-70-90-125-160-...........) and then the array?
Any idea how this correlates to the array.xml?
<integer-array name="config_autoBrightnessLevels">
<item>21</item>
<item>42</item>
<item>84</item>
<item>159</item>
<item>336</item>
<item>672</item>
<item>872</item>
<item>1281</item>
<item>2601</item>
UpInTheAir said:
10-40-90-160-225-320-640-1280-2600-10240 (pls correct me if I've missed any out)
Click to expand...
Click to collapse
That looks right to me, I've not noticed any others in my testing
UpInTheAir said:
Would the 'driver' for the light sensor need to be modified for extra steps (ie. 10-25-40-70-90-125-160-...........) and then the array?
Click to expand...
Click to collapse
Yep, I believe that's right. New drivers would need to be compiled into the kernel, and then the array modified accordingly. This is still something I'm not 100% sure on though, since their could also be a hardware limitation here.
UpInTheAir said:
Any idea how this correlates to the array.xml?
<integer-array name="config_autoBrightnessLevels">
<item>21</item>
<item>42</item>
<item>84</item>
<item>159</item>
<item>336</item>
<item>672</item>
<item>872</item>
<item>1281</item>
<item>2601</item>
Click to expand...
Click to collapse
The way it works is, if the light sensor returns a value of 10 (which is < 21), then it returns the first value of the array. If it's 40 ( 40 > 21 and 40 < 42) then it'll use the 2nd value ... and so on. that's why there's one extra value in the backlight values arrays than there is in the brightness level arrays, because it's the in betweens, plus less than the first value, plus greater than the last value.
Does that answer your question? Or did I mis-understand?
Thanks for the reply. Confirmed what I had thought.
Been looking up on how to de-compile the kernel, but most tools seem to point to lynux system. I run W7, so that's no an option right now. It still is a little beyond my scope of knowledge, but I'm learning bit by bit and also a lot of reading what others have said and researching Mr. Google.
Another useful app is Sensor List, which can graph the changes in lx, but the values are the same as above.
Looks like I'll be keeping this PC when I eventually upgrade so I can run Linux on it to play around...........
UpInTheAir said:
Been looking up on how to de-compile the kernel, but most tools seem to point to lynux system.
Click to expand...
Click to collapse
No need to de-compile it dude ... Lee publishes his kernel source code on github!
https://github.com/LeeDroid-/htc-kernel-ace
As for making changes and then re-compiling it ... I have no idea either
Thanks, will check it out and see if I can find out anything useful.
I don't really want to bother Lee as he's either quite busy or having some well deserved time 'off' before the official GB release.
It's not that big a deal to me (as you said, could be hardware limitation, so no chance anyway), but more of having a play, seeing where things are and what happens and why.
Hi mate,
Sorry, I'm late...
Great thread.
Just few questions:
The value I got (have ever seen) in my GPS status are: 10-40-90-160-220(5)?-640-10240
I have not seen these readings: 320, 1280 and 2600.
So, do I need to download and flash arrays.xml.zip first?
What is Base_LeeDroid-Lower_Auto_Brightness_Patch.zip, your initial modified version?
What is LeeDroid-PNW-Lower_Auto_Brightness_Patch.zip then?
Stock_1.84-Lower_Auto_Brightness_Patch.zip means I can use it with my battery mod, right?
I had a thorough test on the one slopppy posted for me in LeeDrOid's thread. I works great except when the reading is at 40. At 40, the brightness is lowered to minimum. I know this as the button light has lit up. (My phone got 40-90-160 under fluorescent light, so if brightness is lowered to minimum at 40, it means it goes too low [for me].) Apart from this, everything works fine.
Sitting in the car under the sun, the brightness works well. Screen is readable even with sunglasses on. Walking out from the car, under direct sunlight, brightness still works fine.
Like what I said before, may be we should not be too particular about how it works under the sun as it maybe too bright an environment for our eyes to notice the difference.
So bro slopppy, what should I do now if I want to try them out now?
Regards!
So, do I need to download and flash arrays.xml.zip first?
Click to expand...
Click to collapse
Woooaaaaaaah, slow down .... no, no that's not for patching! That's just if anyone wants to use these values in their own themes.
What is Base_LeeDroid-Lower_Auto_Brightness_Patch.zip, your initial modified version?
Click to expand...
Click to collapse
That's the patch you use if you installed LeeDroid but no themes/battery mods etc on top of it
What is LeeDroid-PNW-Lower_Auto_Brightness_Patch.zip then?
Click to expand...
Click to collapse
That's the patch you use if you installed LeeDroid and then installed the "Notification Power Widget" from the OP of the LeeDroid HD thread.
Stock_1.84-Lower_Auto_Brightness_Patch.zip means I can use it with my battery mod, right?
Click to expand...
Click to collapse
Yep, this is the one you should flash mate
works great except when the reading is at 40. At 40, the brightness is lowered to minimum.
Click to expand...
Click to collapse
I think that 40 isn't a value I come across in my daily life! haha ... I've only ever seen it when I mess around with the sensor to try and make it hit different readings. Couldn't hurt to up it a little I guess.
So bro slopppy, what should I do now if I want to try them out now?
Click to expand...
Click to collapse
You should download and flash "Stock_1.84-Lower_Auto_Brightness_Patch.zip". You don't need to do anything else, it will just replace my previous one that you patched. Try it first, since it's different from the one you already have, but I think you might find the same issue. If so, I'll boost the backlight a little at 40 for you.
Let me know how you go
slopppy said:
Woooaaaaaaah, slow down .... no, no that's not for patching! That's just if anyone wants to use these values in their own themes.
...
You should download and flash "Stock_1.84-Lower_Auto_Brightness_Patch.zip". You don't need to do anything else, it will just replace my previous one that you patched. Try it first, since it's different from the one you already have, but I think you might find the same issue. If so, I'll boost the backlight a little at 40 for you.
Let me know how you go
Click to expand...
Click to collapse
Thanks mate. Will do a thorough test again for this.
Value 40 is when I'm sitting at the corner and the phone facing away (opposite) the light. My eyes did not notice any much difference in brightness but my phone's sensor did.
Thanks more for the last sentence of your previous post... (maybe push it up a little to 8%-10%? frankly, me too not sure whether it will suit me more... my suggestion, 40 - 8-10%, 90 - 10-12% and 160 - 12-15%)
Edit: Oh, luckily I'm patient enough to wait for your reply this time...lol
Quick feedback for indoor test:
My personal opinion:
at 40, the brightness is a lowered to minimum and button light turn on, hence, a little too low.
at 90, didn't notice any difference in brightness. However, the button light turned off. So there must be an increment but not noticeable to my eyes. Still too low. (the one posted for me in LeeDrOid thread doesn't have this issue)
at 160, a little (really little only) too bright. Few percent reduction is better.
Will again update my feedback for outdoor test.
Regards!
HoneyHD Theme.
is it possible to make one for Honey Hd Theme,
http://forum.xda-developers.com/showthread.php?t=1028813
What about Kalagas theme...i would be very appriciate
Is this for Froyo only because i can't find arrays.xml inside GB framework-res.apk
Yes, sloppy should be a bit more specific, but in his defence, he does mention in the first post cwm recovery 2.5.1.3,...... relative only to LeeDrOiD Froyo.
Sent from my Desire HD using XDA App
Yep, good point, sorry about that. It's for Froyo SENSE ROMs only.
Anyone know how I can modify the title of the thread??
I'll get on to the requests now.
Cheers,
hamurabi1 said:
What about Kalagas theme...i would be very appriciate
Click to expand...
Click to collapse
Which version of Kalagas theme are you running? There seems to be a zillion of them
kennykenneth said:
is it possible to make one for Honey Hd Theme,
http://forum.xda-developers.com/showthread.php?t=1028813
Click to expand...
Click to collapse
Hi,
The framework-res.apk from Honey HD doesn't want to play ball. It gets a couple of errors when I decompile it, then totally flips out when I try to recompile it. It's an intense theme ... maybe he's doing some things which are incompatible with the way I'm going about my changes.
You could always see if the developer is nice enough to cook you up a version using my arrays.xml from the OP. He has other changes in his arrays.xml as well, so he would have to make sure he just uses the auto-brightness section.
Sorry mate!
slopppy said:
Which version of Kalagas theme are you running? There seems to be a zillion of them
Click to expand...
Click to collapse
I am running this version:
Full Kalagas_Mixed_Theme_LeeDroid_HD [v2.0 09/03/2011 - compatible with LeeDroid HD 1.5.0/1.5.1/2.0.0/2.2.2/2.2.3].
Thank you!
hamurabi1 said:
I am running this version:
Full Kalagas_Mixed_Theme_LeeDroid_HD [v2.0 09/03/2011 - compatible with LeeDroid HD 1.5.0/1.5.1/2.0.0/2.2.2/2.2.3].!
Click to expand...
Click to collapse
Here you mate
As stated in the OP, please do a nandroid backup first ... better safe than sorry ...
Related
Since the same questions seem to be getting asked a lot, here are some methods for getting past stock NookColor ROM limitations in a single thread:
1. How do I keep wifi from turning off when the screen goes to sleep?
- download Spare Parts from the market and set wifi sleep policy to never.
. . . mixed results have been reported with this method, but this appears to be the best known fix at the moment.
2. I restored and re-rooted, now I can't log in to my B&N account!
- get NookColorTools app (if not installed during root, it's on xda). Under All Settings, open the 2nd (of 3) setting called Wireless near the bottom. This will begin their registration process again.
3. How do I install a different keyboard?
- if it's in the market, first purchase/install it-- if it's a stand-alone apk, skip that and move on to the next paragraph. If you just downloaded it from the market, find the apk somewhere in data/app/ and copy from there.
Now place the app's apk (Root Explorer works great) in system/app (mount system as r-w first). Look at the file's permissions (long hold on it and choose Permissions from the menu), and match it to the permissions of the other files in that folder. Reboot. Then open your trusty NookColorTools, select keyboard, and you should be able to switch to it. Not all keyboards are currently working, but this is a great way to find out if it does that doesn't require renaming or deleting your current keyboard.
4. How do I get Swype on here?
- right now, you can't. Swype requires a copy that matches your device's resolution, and the only version of Swype that matches ours (1024x600) is the copy that ships with the Galaxy Tab, but, to my knowledge, nobody has gotten it completely working on here without causing major system crashes (not to mention the apk couldn't be posted on xda even if it was eventually hacked to work).
SlideIT keyboard is another trace keyboard that DOES work on the NookColor, and I've been very happy with it (it's come a long way since I tried it last summer and quickly uninstalled it). The method in #3 above should work to install it.
5. Wait, I can't copy and paste on the NookColor??
- not through the OS, no. There is a solution though. It involves getting an app called Copy Paste It from the market (paid, but there's a trial version). You'll probably need to set it to rotate clockwise (in settings), or it'll get screwy.
When you want to copy, activate the function from the notification, and it'll let you frame the text to copy:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The second part, pasting, requires having a keyboard with a Paste setting in it. Again, SlideIT has this on the special characters keyboard (I'm not a troll for SlideIT, just a happy customer). I'm not sure which other keyboards have this feature, if any (if you know, post, and I'll update this). Assuming you have a keyboard with paste, it'll paste what the Copy Paste It app copied.
6. Why is everything on my screen so small?
- this is because the NookColor's stock LCD density is 169.333, which is pretty low (Galaxy Tab is 240). Unlike resolution, which is hardware-based, density is software-based and can be changed. If you search the market for LCD density, there are a couple apps that will do this--a free one that won't survive a hard reboot, and a paid one that (supposedly) will.
If you want to make it permanent for free, you can edit your build.prop file. Again, use Root Explorer to open system/build.prop (BACKUP FIRST!), find the following two lines:
ro.sf.lcd_density.xdpi=169.33333
ro.sf.lcd_density.ydpi=169.33333
If you wanted your density to be 250, you'd replace them with the following single line:
ro.sf.lcd_density=250
Save the edited file, and reboot.
Here are two of my Galaxy Tab-esque homescreens set to 250:
. . . Now, jacking up your LCD density much above 200 will make your status bar look wonky and cut-off. One solution for this is to set it to 250, like above (by changing build.prop - I think the apps I mentioned only allow multiples of 20), which will make it look clean (as long as wifi is on). The only problem there is that you'll lose your status bar clock and Notifications in portrait mode . . .
. . . the solution for THIS is to get two apps: hellostatusbar, and quick launch. Set quick launch to open hellostatusbar on a home- button double press, and it will display your Notifications.
Also note that raising the density can cut-off parts of the stock Barnes & Noble software (they're designed for the lower density), so this mod is probably better for people like me who use the Kindle app and ezPDF for reading.
7. If I don't want to use softkeys, can I remap the hardware buttons to do something different?
Yes. In Root Explorer, navigate to system/usr/keylayout, make a backup of TWL4030_Keypad.kl, then open the original with text editor and change the entry for key 115 ( volume up) and/or key 114 (volume down) with something like BACK, MENU, or SEARCH. Save the file. Reboot, and they'll be whatever you changed the entry to.
If you want easy volume controls after remapping these buttons, a market app called Volumer++ can be set to live in your notifications for easy access. Otherwise, you can change them from settings.
8. How do I set my wallpaper so that the resolution looks good?
- I used a market app called Wallpaper Set & Save. It's easy, and resolution looks great. I think it cuts off the image a little bit, but not much. I think this method will suffice for many people, but if you want it to be sized perfectly, do the following (credit to swapdotavi for the instructions):
[Get an image that is at least 1200x1024, crop it (without scaling) to 1200x1024. If you're using Photoshop, copy the entire image, then create a new file sized 1200x1024. Then paste the image and use the arrow to drag it around to whatever looks best to you. Save the file as a .png, transfer to your nook, and use Wallpaper Set & Save to choose the new file.]
. . . Since we share the same resolution with the Galaxy Tab, the wallpapers that came with it look phenomenal (in my opinion) on the NookColor. Follow this link to pick them up:
http://galaxytabwallpapers.net/original-galaxy-tab/
9. Can I change the lockscreen slider to look like stock Android or Sense?
- yes - get an app called WidgetLocker. Set it to look how you want. Then, under Behavior, set Homehelper as your system home. Still under Behavior, go to Home to Launch, and pick your real launcher (Launcherpro, ADW, etc.). Also, under Advanced, be sure to check both the Root Bypass of 5 Second Rule, and Retain Keyguard.
10. My NookColor seems sluggish - is there a way to speed it up?
Most of you will already know this, but Setcpu is a market app that can speed things up and improve battery life. CPU Tuner is a free alternative that's similar, but I've had more experience with setcpu, and can vouch much more for it.
My recommended settings:
Min 600
Max 800
Governor: OnDemand*
check 'set on boot'
... And one profile enabled:
Screen Off
Min 300
Max 600
Governor: Ondemand
... And another optional setting (for even a little more extra zip):
under Advanced:
change "Up Threshold" to 35
* for the fastest setting, set the governor in the main CPU setting to Performance (with 800 max). It may drain your battery quicker, but mine still holds up surprisingly well on performance--and the nook is very fast.
These are just settings that work for me. Feel free to experiment. Also, some people were having their Nook randomly reboot, and changing the governor from conservative to ondemand helped.
11. Any other battery-saving tips?
In case you missed the rival xda threads arguing over who thought of it first, there was a potentially useful battery-saving trick in there:
Go back in Root Explorer, and in system/app, mount as r-w and rename Phone.apk and TelephonyProvider.apk to anything else (adding .bak onto the end would be fine).
Basically, you're removing android system files that may be wasting juice looking for a non-existent cell service. It's unsure if or how much this actually improves battery life, but it very well could, and it certainly won't hurt anything changing their names.
12. Why aren't my favorite live wallpapers working?
I'm not sure, but here's how to get the rest of them going:
Download this file: http://db.tt/ur0c98s
It will fail installing, but if you use Root Explorer, copy it from your download directory, go to system/app, set as r-w... Then long-press on any file in that directory, and look at its permissions. Now paste your LiveWallpapers.apk there and change its permissions to match the others. Your live wallpapers should work now!
The Nexus wallpaper won't work, but just install Nexus Revamped from the market - it's identical, it's free, and it has customization.
If you're using one of the more system-intensive Live Wallpapers (like "Water"), I'd recommend using all of the Setcpu changes from #10 above to keep things snappy (also know that LWP's can drain battery quicker).
13. How can I get my Google contacts in here?
If you aren't concerned with them showing up in the B&N Contacts app, and are more interested in having them come up as auto-suggestions when typing an email address or Google Voice text number, there's a way (credit to jadambpharm):
- Go to gmail on the web, click on contacts (left side), then More Actions, then Export. Choose .vcard format. Transfer that file to your SD card.
- get a Market app on your Nook called Import Contacts. Point it to the contacts.vcard file you just got, and they'll now come up for auto-fill suggestions!
14. How can I prevent the Nook from automatically updating the firmware?
- Change the name of etc/security/otacerts.zip to anything else (doing this in Root Explorer works fine). So far, this had looked pretty solid in successfully disabling OTA updates.
15. Why won't YouTube play videos in HD?
For some reason, the YouTube that's installed from rooting won't do it. To get a version that plays HD:
- uninstall your current YouTube via Titanium Backup
- download this version from the Evo (credit aludal): http://db.tt/y5vVvI2
- rather than installing this one, rename it youtube.apk and copy it into system/app (w/permissions matching the other apk's in that folder)
It should be there now, ready to play HQ clips. If not, reboot first.
I'll update as I think of more. Enjoy your modestly-priced, unintentional Android tablets!
Reserved 10 chars
How about "What size should wallpaper images be?"
I suggest this because I dont know
swapdotavi said:
How about "What size should wallpaper images be?"
I suggest this because I dont know
Click to expand...
Click to collapse
I didn't resize them manually, I just used an app - will update OP in a minute with that, and again later when I get the chance to research manually setting them . . .
I don't know either, but I've had good luck with searching for 'wallpaper' on Google images with size set to 1024*1024 and then using 'set as wallpaper' from dolphin browser HD.
Sent from my NOOKcolor using XDA App
pest789 said:
I don't know either, but I've had good luck with searching for 'wallpaper' on Google images with size set to 1024*1024 and then using 'set as wallpaper' from dolphin browser HD.
Sent from my NOOKcolor using XDA App
Click to expand...
Click to collapse
The Galaxy Tab wallpapers I've used all look phenomenal too. Same resolution, so its tailor-made. Easy to find them with a google search.
For some reason changing the lcd density didn't do a damn thing through build.prob after reboot. What did I do wrong?
Edit:
And I did save it before rebooting so I'm not sure what I did wrong...
wvcachi said:
3. How do I install a different keyboard?
- if it's in the market, first purchase/install it-- if it's a stand-alone apk, skip that and move on to the next paragraph. If you just downloaded it from the market, find the apk somewhere in data/app/ and copy from there.
Now place the app's apk (Root Explorer works great) in system/app (set system as r-w first). Reboot. Then open your trusty NookColorTools, select keyboard, and you should be able to switch to it. Not all keyboards are currently working, but this is a great way to find out if it does that doesn't require renaming or deleting your current keyboard.
Can you please explain the 'set system as r-w'?
Thanks
Click to expand...
Click to collapse
Click to expand...
Click to collapse
@beejis - make sure you're losing the xdpi and ydpi parts and merging it into a single entry. Look closely at the example in the OP. Also, make sure you're editing the entry that isn't commented out (don't bother editing the lcddensity entry with a # in front of it) a few lines earlier. If for some reason that didn't work, then use the free app from the market to change it.
@k8108 - if you're using Root Explorer, it's a little button up top when you're navigating system/, which lets you toggle mounting system as 'read-write' and 'read-only.'
Beejis said:
For some reason changing the lcd density didn't do a damn thing through build.prob after reboot. What did I do wrong?
Edit:
And I did save it before rebooting so I'm not sure what I did wrong...
Click to expand...
Click to collapse
Comment out these lines (add # to beginning):
# ro.sf.lcd_density.xdpi=169.3333
# ro.sf.lcd_density.ydpi=169.3333
Add this line:
ro.sf.lcd_density=254
I already had a line similar that I uncommented, and I run mine at 254.
169.3333 / 2 = 84.6666
169.3333 + 84.6666 = 254
I am probably overthinking it, but it looks good. You can make that number 250 if you want.
The Program LCD Density lets you select specific densities as well, but is only soft. Nice for testing.
k8108 said:
Can you please explain the 'set system as r-w'?
Thanks
Click to expand...
Click to collapse
http://nookdevs.com/NookColor_Making_system_partition_Read-Write
From adb shell, run this code:
Code:
mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
ThrowingKs said:
http://nookdevs.com/NookColor_Making_system_partition_Read-Write
From adb shell, run this code:
Code:
mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
Click to expand...
Click to collapse
...I got the impression he was using Root Explorer, in which case it's a little button that says r-w.
I have used the free market app to change the lcd density and it makes most of the interface fantastic except for a couple things. As noted the status bar doe mess up but that I am not worried about but the screen density change to, 250 in my case, really screws up the formating of my nook library and shop. I use them quite a lot to read newspapers and such so if anyone else has this experience let me know how/if you deal with it.
Sent from my LogicPD Zoom2 using XDA App
foethalove said:
I have used the free market app to change the lcd density and it makes most of the interface fantastic except for a couple things. As noted the status bar doe mess up but that I am not worried about but the screen density change to, 250 in my case, really screws up the formating of my nook library and shop. I use them quite a lot to read newspapers and such so if anyone else has this experience let me know how/if you deal with it.
Sent from my LogicPD Zoom2 using XDA App
Click to expand...
Click to collapse
Good point - I'll note that in the OP. I don't use the B&N stuff, so it's easy for me to forget that not everyone on xda is in the same boat.
Where does the SlideIT.apk go after you install it from the market? I can't put it in the system/app folder because i can't find it. Any ideas?
NookColor+ XDA 4 ever
cgtombstone said:
Where does the SlideIT.apk go after you install it from the market? I can't put it in the system/app folder because i can't find it. Any ideas?
NookColor+ XDA 4 ever
Click to expand...
Click to collapse
Look in data/app, and find the file named com.dasur.slideit.apk. Copy/paste that into system/app (hit r-w first of course), then reboot and switch keyboards via NookColorTools.
My bad I was searching for it in root explorer and I gues the search function was skipping the data folder for some reason ( or I'm missing something). Thanks anyway.
NookColor+ XDA 4 ever
Thanks bookmarking this thread
wvcachi said:
I didn't resize them manually, I just used an app - will update OP in a minute with that, and again later when I get the chance to research manually setting them . . .
Click to expand...
Click to collapse
Ah perfect did not see your update. I see you found Set and Save, but you mentioned you might update with exact size instructions later. I actually went and did a bit of research, so maybe I can save you some time
To get an perfect wallpaper using 5 screens, like in ADW:
- Get an image that is at least 1200x1024
- Crop (dont scale) it to 1200x1024. A really easily way to do this is open the file in Photoshop, copy the entire image, then create a new file that's exactly 1200x1024. Then just paste the image and use the arrow to drag it around to whatever looks best to you.
- Save the file as a .png
- Get it on to your nook. (SD card transfer, email and download, whatever)
- Open Wallpaper Set & Save
- Point it towards the folder you have your wallpapers in
- Select the wallpaper you want
- Hit apply
Bam. Perfect wallpaper, no stretching, no compression. Looks great! I'll post screens later today if I remember
I used a 1920x1200 wallpaper I had on my PC, cropped it, emailed it to myself, then used Set & Save to place my wallpaper. It's really crisp.
edit: And thanks for the lock screen information! Going to do that tonight; sick of the stock screen
MOD, can we get this stickied? Lots of good info!
The 1% battery mod for GingerBlur 3.1/4 is complete. I have attached the file below the post. Download the 3.1 package for GB 3.1, and the 4 package for GB 4.0. As of now, I have not figured out how to script it (I tried putting the shell commands in a .sh script, but always got "permission denied" when I tried to run it, even if I did chmod). So you will need to push both included files manually. I advise you to execute the commands quickly, as changing the framework-res.apk / services.jar may cause your phone to reboot by itself after a short while (happened to me before). Do not push services.jar for GB 3.1 - it is not necessary.
Alternatively, if you have not flashed GingerBlur yet, you can push framework-res.apk (GB 3.1 and 4) and services.jar (GB 3.1 ONLY) into the zip file. Small hint: if you're using Swype beta, remove the swype.apk from the system apps folder before flashing - otherwise you break your Swype beta
Battery icons from UOT Kitchen, connectivity icons from myself (see here). If you want "stock" GingerBlur connectivity icons, you need to replace them in the framework-res.apk. (Never unpack framework-res.apk, just open in a zip editor and push the files in.)
The battery icons show percentage both when charging (4.0 only) and when discharging. The charging animation stops at 95% charge for unknown reasons, and will only show the percentage from 95% - 100%. Nothing I can do about this for now.
Prerequisites:
1.83 rooted
GingerBlur 3.1/4.0
A copy of adb (with the two dlls)
The attached files in the same folder as adb.exe
If you want to make this work for stock or for other mods / themes, check here for instructions.
The commands are below (you should be in the su shell after the "su" command - you may need to approve super user permissions on your phone for this! Wait for the "#" to appear). If anyone previously flashed both files (from my previous version), there should be no need to re-flash framework-res.apk, only services.jar .
Code:
adb.exe push framework-res.apk /data/tmp/
adb.exe push services.jar /data/tmp/
adb.exe shell
su
mount -o rw,remount /dev/block/mmcblk0p12 /system
cp /system/framework/framework-res.apk /system/framework/framework-res.apk.BAK
cp /system/framework/services.jar /system/framework/services.jar.BAK
cp /data/tmp/framework-res.apk /system/framework/
cp /data/tmp/services.jar /system/framework/
mount -o ro,remount /dev/block/mmcblk0p12 /system
reboot
If you want to donate, do it to shoux instead. Or donate to a charity.
It seems the 1% battery mod has been done, but the original is buried quite deeply within other threads. For your reference (I shall update this as I go along, and take NO CREDIT for this):
A flashable CWM .zip that looks a bit like GingerBlur (thanks to shoux): http://forum.xda-developers.com/showpost.php?p=13726101&postcount=575
There is a theme around now with the 1% battery for deodexed 1.83 Atrix (presumably otherwise stock): http://forum.xda-developers.com/showthread.php?t=1076524
Thanks for everyone highlighting this below!
Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Previous post for reference:
bl0wf1sh said:
I would like to do a 1% battery mod for the atrix. I am a bit stuck at the moment though, and it would be great if sb can point me into the right direction.
I tried replacing /res/drawable/stat_sys_battery.xml (see attached), and it took me a bit to modify it so that the xml translation is correct. My new file has 1% steps. There was already a set of icons, so I did not create new ones - maybe that was my mistake, I do not know. This file uses the resource identifiers from the gingerblur ROM (beta 7.7, but I would think those would be identical in RC1, but if not, it is not a big deal to modify it now for me).
The set of icons for 1% steps in the gingerblur ROM have a different size (38x38) than the ones that are actually shown (22x38). I am wondering whether this makes a difference, but I am not sure. I am planning to verify this, but may end up without a battery icon again (happened to me today).
I tried looking at /sys/class/power_supply/battery/uevent - the system seems to report 1% steps there.
Is there any part of the system I need to modify so that alerts (for lack of a better word) get broadcasted for 1% increments? I would think that the battery status is more of a push event, not a pull event.
Click to expand...
Click to collapse
the app circle battery can display with 1%.but unfortunately,it's always installed into media area of my atrix.The widget will be disappeared after it restart and cannot find it anymore.....
I recall DG attempting this, after a week or so he posted that the found confirmation hardware dosn't support it. Don't mean to negate your effort I hope you get this to work,
http://forum.xda-developers.com/showpost.php?p=11586163&postcount=60
within this thread
http://forum.xda-developers.com/showthread.php?t=965682
Anyone try UOT Kitchen for this ?? Could solve a few problems.
Djazin said:
I recall DG attempting this, after a week or so he posted that the found confirmation hardware dosn't support it. Don't mean to negate your effort I hope you get this to work,
http://forum.xda-developers.com/showpost.php?p=11586163&postcount=60
within this thread
http://forum.xda-developers.com/showthread.php?t=965682
Click to expand...
Click to collapse
I remember this being brought up in the IRC channel, and the consensus was it could be done, but the Battery Driver would have to be rewritten. That's what DG was talking about most likely. Rewriting the driver isn't easy, and most people can't do that.
If interested to get more input go to irc.freenode and join #moto-atrix
Really hope you (or anyone) is successful in making this happen!
naturefreak85 said:
I remember this being brought up in the IRC channel, and the consensus was it could be done, but the Battery Driver would have to be rewritten. That's what DG was talking about most likely. Rewriting the driver isn't easy, and most people can't do that.
If interested to get more input go to irc.freenode and join #moto-atrix
Click to expand...
Click to collapse
But how can app called Circle Bettery can display with 1% based on current driver?
godwin1981 said:
But how can app called Circle Bettery can display with 1% based on current driver?
Click to expand...
Click to collapse
It takes the 1% battery increments from the system events.
can we get a screen shot of this mod? i am currently using circle battery as well and would like that space back
spyz88 said:
It takes the 1% battery increments from the system events.
Click to expand...
Click to collapse
not quite 100% accurate.
The circle battery widget like alot of other moto specific battery apps check a file in they system folder(dont remember which one exactly) which has the correct battery %. The system fires battery change events correctly at every 1% change but even tho it is firing correctly it only reports the 10% levels. so instead of using the system reported values it checks the file for the value.
idk where in the control structure it goes from 1%->10%. I would guess that the driver itself is working correctly, but the system reading the driver is restricting it to 10%.
jug6ernaut said:
not quite 100% accurate.
The circle battery widget like alot of other moto specific battery apps check a file in they system folder(dont remember which one exactly) which has the correct battery %. The system fires battery change events correctly at every 1% change but even tho it is firing correctly it only reports the 10% levels. so instead of using the system reported values it checks the file for the value.
idk where in the control structure it goes from 1%->10%. I would guess that the driver itself is working correctly, but the system reading the driver is restricting it to 10%.
Click to expand...
Click to collapse
That kind of info would be availible in /sys.
Djazin said:
I recall DG attempting this, after a week or so he posted that the found confirmation hardware dosn't support it. Don't mean to negate your effort I hope you get this to work,
http://forum.xda-developers.com/showpost.php?p=11586163&postcount=60
within this thread
http://forum.xda-developers.com/showthread.php?t=965682
Click to expand...
Click to collapse
indeed.
Well, the situation is this (I believe this is what DG was talking about):
- /sys/class/power_supply/battery/uevent reports 1% events via power_supply_charge_counter (this I can confirm, so can everyone in a shell on the phone)
- the battery icon on the top right takes the percentage though from a different broadcast event (probably), which only broadcasts 10% increments.
Any battery icons on the LEFT side (media area) of the status bar can do whatever mechanism they want to show the percentage. They can take uevent, they can estimate based on voltage, they can look at the weather, ... This is not the case for the right side. There is a specific event it needs to listen to.
I will try to dig a bit deeper to backtrace what needs to be changed. It could well be that the battery driver needs to be modified - I highly doubt that, though. Even if that were the case, there should at least be some way to bring the uevent to the right side of the status bar.
Has anyone else looked in /data/battd and found a file named "powerup"?
If you open as text with RE it looks pretty interesting...
anyone know or care to explain?
Sent from my MB860 using XDA App
BravoMotorola said:
Has anyone else looked in /data/battd and found a file named "powerup"?
If you open as text with RE it looks pretty interesting...
anyone know or care to explain?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
It is an interesting file. It even has my battery health down to the 1%.
Also, check out /sys/devices/platform/cpcap_battery/power_supply/battery/uevent
Code:
POWER_SUPPLY_NAME=battery
POWER_SUPPLY_TYPE=Battery
POWER_SUPPLY_STATUS=Full
POWER_SUPPLY_HEALTH=Good
POWER_SUPPLY_PRESENT=1
POWER_SUPPLY_TECHNOLOGY=Li-ion
POWER_SUPPLY_CAPACITY=100
POWER_SUPPLY_VOLTAGE_NOW=4203000
POWER_SUPPLY_TEMP=340
POWER_SUPPLY_CHARGE_FULL_DESIGN=1880
[b]POWER_SUPPLY_CHARGE_COUNTER=99[/b]
That one is accurate down to 1% as well.
shawnbuck said:
It is an interesting file. It even has my battery health down to the 1%.
Also, check out /sys/devices/platform/cpcap_battery/power_supply/battery/uevent
Code:
POWER_SUPPLY_NAME=battery
POWER_SUPPLY_TYPE=Battery
POWER_SUPPLY_STATUS=Full
POWER_SUPPLY_HEALTH=Good
POWER_SUPPLY_PRESENT=1
POWER_SUPPLY_TECHNOLOGY=Li-ion
POWER_SUPPLY_CAPACITY=100
POWER_SUPPLY_VOLTAGE_NOW=4203000
POWER_SUPPLY_TEMP=340
POWER_SUPPLY_CHARGE_FULL_DESIGN=1880
[b]POWER_SUPPLY_CHARGE_COUNTER=99[/b]
That one is accurate down to 1% as well.
Click to expand...
Click to collapse
That is the same file as /sys/class/power_supply/battery/uevent (this is an alias, yours I think the "real" directory path)
We know it is there - so how do we get it up in the status bar?
It is possible that the status bar in-built battery icon would somehow read out the POWER_SUPPLY_CAPACITY event and react to it, while we WANT it to read the POWER_SUPPLY_CHARGE_COUNTER event instead. If so, that should be relatively easy to manipulate. Once we find out where the reading takes place, that is
*edit* I am tempted to just redirect POWER_SUPPLY_CAPACITY to POWER_SUPPLY_CHARGE_COUNTER, but I am afraid that could break some things. An easier way should be to manipulate the routine behind the battery icon update, wherever it is.
another app that does 1% increments on the atrix:
https://market.android.com/details?id=battery.monitor&feature=search_result
difference from circle batt mod is that it puts the percent batt remaining in the notification bar.
it is VERY accurate, and to prove it look at how the motorola battery monitor works
when simmo or circle hits 94%, it shows 90% in motorola
when simmo/circle hits 84%, it shows 80% in moto
etc
etc
when it hits 15%, thats when the motorola battery monitor starts doing 5% increments, and simmo/circle is dead on.
I have Motocharge, is verry good
https://market.android.com/details?id=com.zorgblaubaer.motocharge&feature=search_result
There's another app I'm trying now:
Battery Monitor Widget. It has some themes, nice graphics, and do not use much battery. Best shot so far for me.
All this is interesting, but it does NOT solve the problem. This is about mods to the right-side battery icon, not apps.
spline1 said:
I have Motocharge, is verry good
https://market.android.com/details?id=com.zorgblaubaer.motocharge&feature=search_result
Click to expand...
Click to collapse
alex_herrero said:
There's another app I'm trying now:
Battery Monitor Widget. It has some themes, nice graphics, and do not use much battery. Best shot so far for me.
Click to expand...
Click to collapse
andy2na said:
another app that does 1% increments on the atrix:
https://market.android.com/details?id=battery.monitor&feature=search_result
difference from circle batt mod is that it puts the percent batt remaining in the notification bar.
it is VERY accurate, and to prove it look at how the motorola battery monitor works
when simmo or circle hits 94%, it shows 90% in motorola
when simmo/circle hits 84%, it shows 80% in moto
etc
etc
when it hits 15%, thats when the motorola battery monitor starts doing 5% increments, and simmo/circle is dead on.
Click to expand...
Click to collapse
I know, i test the UOT Kitchen with the framework from Atrix.
Noope it's not working FC's overall :-(
Original Thread : http://goo.gl/Y4nyq
Teams Website:http://betadan.com/paranoid/
Thanks to D4rKn3sSyS, molesarecoming and xylograph,Madflapjack.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
A message from the Paranoid Android Team: This is an ongoing developer project to make way for a modification that will entirely transform your device, but retain the aesthetics and the experience of your phone. I know you've seen tablet mode roms before, they change two lines in your build.prop file which you could easily edit yourself in seconds and maybe throw a keyboard in there to make it work better. It's a start, but this ain't enough. This thing has potential, but it is wasted the moment you try to stuff a full blown tablet into your poor phone. Yet we all know our high res phones can very well handle more than silly 1-column layouts. So the magic must be in between somewhere, a place that Google must have overlooked and left blank. Yes, this rom strives to drop your device into tablet mode, but it won't stop there, it will reshape and redefine ICS to make it all a usefull addition and not just a cute novelty. we're calling it: Hybrid Mode, best of both worlds.*
A message from Battlekry: I have been running this rom on my device for a good day and a half and have ironed out some minor things... I have communicated with the members of the PA team and will link this thread to them, I have been permitted to do this. I hope you guys enjoy this.. This version of the PA rom is VERSION 1.0 as seen in the CL in post 2 and VERSION 1.1 was released today by PA so it should be coming your way if I find it a mandatory update.. I will keep an eye out.. Use this rom and fun with it do not go blind though... but also let me warn you....
I am not responsible for bricked devices, dead SD cards, or the Derrick Rose's season ending injury this NBA post season...
* YOU are choosing to make these modifications, and if you point your finger at anyone for messing up your device, remember it's in your hands, no one made you flash anyone or anything ;p/
*
Download: http://tiny.cc/oui5ew
Factory Reset
Advanced Cache Wipe
Dalvik Wipe
Mounts and Storage System Reset
CWM -> Advanced -> Fix Permissions
Hybrid Gapps already inclueded in zip... may eventually separate for reducing the size of the Rom and make Gapps an optional flash..
Go to Settings, System, Font size, set it to NORMAL
Check "Auto Hide" in Settings, System, Statusbar, to finally get Fullscreen (or Hold power button, and press "Toggle StatusBar")
Launcher Settings: margins: SMALL (If youre using Apex / Nova), show permanent searchbar: YES, Grid: 5x4, resize all widgets: YES, Wallpaper scrolling: OFF
Wifi Tethering is not working. (It will gives you bootloop.)
All possible visual bugs can be fixed changing PAL & PAD parameters
Have to clean up some additional Nexus S files but this rom is an awesome beta...
Any issues currently with CM9/ICS 4.0.4 for the Vibrant
You tell me, please?
Cyanogenmod Team, specially Codeworkx and XplodWild, for CM9
AOKP team, they've got some great pieces of code.
shayne77, for Battery Images
evilisto, for Honeycomb lockscreen, Sense Recent Apps mod, and Tablet mode source
dubidu, for hiding statusbar mod
Mr_Psycho for Sdcard Swap fix
Gltich Team for Glitch Kernel
Antonio Camerino for some kool walls... included below.
Reserved
v1.0b1
Kanged from source, 1:04pm COT. All features included (even the ones that are on CM9 changelog but not on latest nightly)
Improvements on OTA app- Does not apply to Vibrant
First time in Android history that Per-App-Layout has been realized
Comes with a better panel
Fixed pin screen hot reboot
v0.6
Kanged from source, 2:52pm COT.
Updated kernel to latest siyahKernel- Does not apply to Vibrant
Fixed tablet mode swapping not overriding sense recent apps option
Automatically disable all the DPI options if PAD is not enabled
General fixes. We're now stable. This version is not a beta but a RC - Does not apply to Vibrant
Fixed reset button on PAD panel
Fixed tablet mode keyboard popup (Is little but there it is, not cutted anymore)
Force to hide statusbar (Global menu option)... finally fullscreen gaming!
New PAD code. No lags at all, rotation is smoooth.
v0.5
Kanged from source, 11:10am COT. All features included
Updated kernel to latest siyahKernel- Does not apply to Vibrant
CherryPicked a few CM things that I'm sure they will merge soon (and what if they dont )
Home button long press on tablet mode now handles recent apps (just like on phone mode)
New PAD panel. Moles didn't sleep today
Fixed most of the crashes (99%, maybe I missed something)
Fixed lockscreen music transport overlay
Fixed Can't install apps to external sd, installing them causes acore fc
Tablet mode onScreen buttons toggle
Instant changes, SoftKeys (Not even on AOKP )
Reserved again...
Just in case... I don't make it home tonight...
Gotta give this a try later this week!
Thanks for the port!
Holy ****!! You did it
Thank you
Sent from my SGH-T959 using Tapatalk 2
Awesome! Just flashed this to my friends cappy ^^
Time to do it all over again for myself
Thank you for your hard work
Flashing... Hope ota updates of vibrant comes soon
Sent from my SGH-T959 using Tapatalk 2
Is there a way to remove the "Home", "Back" buttons along the bottom?
chadhoard said:
Is there a way to remove the "Home", "Back" buttons along the bottom?
Click to expand...
Click to collapse
System Setting-->Paranoid Android-->Toggle Soft keys..
this looks like amazing work! Well done!
Can anyone comment if 911 works (in the USA), as CM9 ROM's don't seem to be all that consistent with this and it's still considered a bug.
Globespy said:
this looks like amazing work! Well done!
Can anyone comment if 911 works (in the USA), as CM9 ROM's don't seem to be all that consistent with this and it's still considered a bug.
Click to expand...
Click to collapse
Globe, your results may vary with 911 as we all understand.. Maybe someone can check as I have not...I may when I get to the crib.. Sorry for now brother..
GPS is also not made to work in this rom as it is missing the files although a GPS fix could be flashed along with any preferred Kernel combo...
One reason I did not include Subzero out the box for this is because it does not play nice with the Galaxy S settings for color... Although if dig a little deeper I could find a solution for that, if not someone may just chime in..
For the most part I am getting decent battery life, I did not mess with any build prop edits to enhance data or wifi scanning for the flashable rom zip but you you all can with your own setup.. The rom is running sturdy on the Vibrant...
Sent from my SGH-T959 using XDA
nice rom...just installed one hour ago and the only bug seems to be external sd not showing
battlekry said:
One reason I did not include Subzero out the box for this is because it does not play nice with the Galaxy S settings for color... Although if dig a little deeper I could find a solution for that, if not someone may just chime in..
Sent from my SGH-T959 using XDA
Click to expand...
Click to collapse
Mr Psycho has a moded version of the app that works with his kernels, it may or may not work on this rom.
Vibrant MiuiV4 360° Productions
So far after a few hours on this rom, I like it quite a bit. The only thing I am not liking is the fact the stock keyboard is the only one working when in tablet mode. I tried two tablet specific keyboards and they both did the same thing which was that they are so blown up in size I can only see the upper left part of the keyboard. One of the ones I tried was thumbkeyboard and that has options for changing the size but that didn't change it at all. Anyone know if this can be fixed?
mikka06 said:
...the only bug seems to be external sd not showing
Click to expand...
Click to collapse
Anyone else confirm this? Definitely want to flash this ROM.
How do you adjust the DPI?
MStrawder said:
Anyone else confirm this? Definitely want to flash this ROM.
Click to expand...
Click to collapse
It shows on the phone under emmc, haven't tried mounting yet.
chadhoard said:
How do you adjust the DPI?
Click to expand...
Click to collapse
Hey there, settings--->Paranoid settings ---> hybrid --->enable it ---> list apps.. go to all apps towards the most right... here you can adjust the dpi for tablet or phone mode and set a custom dpi..
Sent from my SGH-T959 using XDA
mikka06 said:
nice rom...just installed one hour ago and the only bug seems to be external sd not showing
Click to expand...
Click to collapse
It is listed as emmc in any file manager.. so it is in fact mounting for me...
I can add a flashable zip that MP made to invert that to the new CM standard where the internal SD card for phones is seen as the emmc and the external would be the main.. this seems to resonate with the way the CM9 nightlies are doing it... let me know if you guys want that...
Sent from my SGH-T959 using XDA
Blars1206 said:
One of the ones I tried was thumbkeyboard and that has options for changing the size but that didn't change it at all. Anyone know if this can be fixed?
Click to expand...
Click to collapse
What I did is the following
settings--->Paranoid settings ---> hybrid enabled ---> list apps.. find thumb keyboard, set it to phone mode and dpi to 120... small running hybrid but works...
Sent from my SGH-T959 using XDA
Hi guys and girls Ok well i've been lurking around on these forums for some time now. Recently I rooted my Nexus 5 and I must say I love it! I'm aiming to make this thread somewhat of a one stop for people who have just rooted or are considering rooting to see what is possible once you root your phone!
Alright so first things first, before you go any further you are going to need:
A rooted Nexus 5!
A fair amount of time.
if you are unsure of how to go about doing this please read through this thread made by the wonderful Chromium_:
http://forum.xda-developers.com/showthread.php?t=2507905
OK, so from this point on i'm going to assume you have all the requisites you need so lets get into it shall we
Block adverts while browsing the web.
So i'm pretty sure that most of us have been blocking those frustrating pop ups and banner adverts while browsing the web on our PCs or Macs for years now right? (Yes, I am looking at you Mr. 888 Poker! ) But for some reason this is not possible to do on our phones. Not anymore! With your rooted phone you can install the superb adaway and wave those adverts goodbye!
Adaway is not however available from the playstore. Don't fear though you can get it here!
http://forum.xda-developers.com/showthread.php?t=2190753
NB: If for some reason you are not currently blocking ads on your PC or Mac. I recommend the add on - adblockplus.
https://adblockplus.org
Install custom Lockrings, softkeys and more.
Bored of the standard android lockscreen? Don't want to have to mess around with apps such as widgetlocker which often prove to be quite unstable at times? Now you don't have to!
Check out this thread created by matthew0776
http://forum.xda-developers.com/showthread.php?t=2514238
With the files included in that thread you can have whatever look you could possibly want! As the thread states however, in order to flash them on your device you will need the application ZipThemer.
ZipThemer is a simple enough application to use and is available from the playstore.
https://play.google.com/store/apps/details?id=kellinwood.zipthemer
In order to use ZipThemer the steps are as follows:
1) Open the ZipThemer application and press Update Edify, you will find this in the drop down menu which appears when you press the 3 dots in the top corner of the right hand side of the screen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2) Once you press Update Edify you should be greeted with this screen:
3) Press 'Browse'
4) Select the firmware file you are currently using. It could be called, for example, pa_hammerhead-4.0-BETA6-20140217.zip
5) Press 'Configure' A message at the bottom of the screen should pop up at this point which says 'success'.
6) Press the back key once. You should end up at this screen:
7) Once at the screen above press '+Theme' You should then be presented with this screen:
8) Press the green back arrow on the screen above and browse to the location of your lockring/sofkey .zip file you downloaded and placed on your device earlier.
9) Press 'Build It!' and make sure you select the option to make a backup/undo so you can always switch back to stock easily or if there is any issues.
10) Boot device into recovery (CWM or TWRP) Select install Zip from SD card and install it! You will find your file in the root of your SD card for easy access.
ZipThemer not working? Don't worry all hope is not lost! The method above works for the vast majority but if you are one of the unfortunate few there is a solution!
Follow the steps above as usual but when you get to step #4 (Browse for firmware file) Select this file:
http://d-h.st/CgG
Instead of whatever firmware file you are currently running on your device.
Again all credit goes to matthew0776 here. I have simply tried to rephrase the instructions he provided in the thread here:
http://forum.xda-developers.com/showpost.php?p=39572221&postcount=18&nocache=1&z=5376182028558105
To make them easier to understand
Change your boot animation.
Alright so did you know now that you've rooted your phone you can change the boot animation to whatever you like? Well you can! And below i'm going to try my best to explain how.
Ok, now there are a few ways to do this. Personally I like to do things manually however so that's the way i'm going to demonstrate here. If however you don't fancy doing the legwork yourself though (and don't mind paying a small sum) I am aware of a option in the awesome ROM Toolbox pro which does pretty much the same thing. You can get ROM Toolbox pro from the playstore here:
https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolboxpro
So, you've decided to stick with me then?! Alright cool, well here is how to do it the good old fashioned way then
You will need:
Root Explorer: https://play.google.com/store/apps/details?id=com.speedsoftware.rootexplorer
A custom boot animation: http://forum.xda-developers.com/showthread.php?t=2577081 (Thanks to thor6577)
1) Open Root Explorer and navigate your way to: system/media.
2) Here you will find a file called bootanimation.zip Select this file (press the tick to the right of it) and rename it. To do this press the 3 dots in the top corner of the right hand side of the screen once you have selected it and press 'Rename' You may be greeted with a warning at this stage asking if you wish to change the file system from read-only to read-write the answer is YES.
3) Rename the file to bottanimation.zip1 . This is essentially making a backup
4) Browse to wherever you have saved your new custom boot animation and copy it over to this directory (system/media)
NOTE: Your custom boot animation MUST BE called bootanimation.zip or it will not work.
5) Reboot and enjoy
Change your LCD screen density.
The Nexus 5 has absolutely gorgeous 5" display but in my opinion it does not make the most of it out the box! With a rooted phone however you can change the LCD density of the screen to whatever you like!
In simple terms changing the density effects how large icons and widgets will appear on your screen. This means the lower the density the more you can fit on one screen
Changing the screen density on a rooted phone is an incredibly simple Build.prop tweak. Certain custom ROMs come with this feature already nicely packaged into the ROM for example the ROM I am using AOSB 1.3.1 does.
http://forum.xda-developers.com/showthread.php?t=2615590
But, if your ROM doesn't or you have decided to stay on stock don't worry To change you LCD Density follow the steps below:
1) Open Root Explorer and navigate your way to system.
2) Select build.prop (Press the blue tick)
3) Click on the three dots on the top right of the screen and select 'Open in Text Editor' You may be greeted with a prompt here which 'WARNING' file system read-only, switch to read-write? (I'm paraphrasing) The answer is of course YES.
4) Find the entry ro.sf.LCD_density.
5) Change the number directly after the '=' to what you want the screen density to be. You can go anywhere from 300 - 480 before apps such as the Playstore start to break. Personally I use 340 dpi and I think its perfect, its all personal preference though
6) Press the three bars in the top right corner and select save changes.
7) Reboot your phone and enjoy
For more information on LCD density and discussion please check out this thread:
http://forum.xda-developers.com/showthread.php?t=2517311
mmmm PIE!
PIE is a nice little feature you may have stumbled across browsing these forums. If you haven't already it looks like this:
Pretty cool right?! Well I thought so anyway. Well with your rooted phone now you can have it to Now there are two ways (which I know of) how you can get this. The first way is the simplest by far. Many ROMS come with this nice feature already installed. To find out if yours does just check out the features page. Often you don't even have to do that its actually written in the title of whatever ROM you are using. To check out all the custom ROMs available for the Nexus 5 on XDA check out these two forums:
http://forum.xda-developers.com/google-nexus-5/development
http://forum.xda-developers.com/google-nexus-5/orig-development
Now if your ROM does come with PIE baked into it. Your already all set, just go to your settings page and you will find the options for it in there. However if you are still running stock don't worry you can have PIE too thanks to noname81. To get it visit here:
http://forum.xda-developers.com/showthread.php?t=1330150
noname81's app couldn't be simpler to use either, simply download the latest build and place it somewhere easily accessible on your device, for example, Download. Then browse for it using whatever file manager you like (there's loads on the Playstore) however personally I like ES File manager the most if you just cant make your mind up. Its free and you can get it here:
https://play.google.com/store/apps/details?id=com.estrongs.android.pop
Once you've found it click on the apk and hit install.
NOTE: YOU MUST ALLOW INSTALLATION OF APPS FROM UNKNOWN SOURCES.
To do this:
1) Go to settings.
2) Scroll down to 'Personal' and press on 'Security'.
3) Scroll down to 'Device Administration'
4) Press the check box located to the right of the entry 'unknown sources'.
AppBar (Xposed Framework)
Ok, well the options really are somewhat limitless with this so i'm not going to go through all of them. Instead i'm just going to focus on one of my personal favorites, The AppBar. If you are wondering what AppBar is, it's a little feature which looks like this:
AppBar is not permanently on show like the picture above however. It simply slides into frame when you touch a certain area of the screen which you can personally set up to your liking (much like PIE above).
Ok, so i'm going to put in a slight warning here, in terms of actually installing the app, this one is slightly more work than the others I have mentioned. It's still nothing to challenging though, I promise!
To get AppBar. The first thing you are going to need to do is install the Xposed Framework. You can get it here:
http://repo.xposed.info/module/de.robv.android.xposed.installer
1) Once, you've installed the apk above you should be greeted with this screen (if you are not, navigate your way to it):
2) Once at the screen above, press Install/Update and let it do its thing.
3) Reboot phone.
4) Once you've rebooted, go back into the Xposed installer and press the tab on the top left of the screen.
5) Select 'Download' from the drop down menu which appears. You should be landed at this screen:
6) Scroll down until you find XBlast Tools and install the correct version for whatever version of android you are running.
7) Press on the entry and hit download.
8) Once it's finished you will get a notification which says something along the lines of 'Xposed module is not active yet'
9) Open your notification bar and press on the notification.
10) You will end up at this screen:
11) Press the check box to the right of XBlast Tools [1.8.0]
12) Reboot.
Once you've rebooted you should see a new icon in your app draw called XBlast Tools, open it.
1) Scroll down to the entry AppBar .
2) Enable it using the slider.
3) To set up what you want in you appbar content go to 'Setup Appbar content'
4) You will be taken to this screen:
5) Drag and drop apps into the bar on the left
6) You can adjust the trigger position, height, width and transparency using the sliders on the first screen.
Note: Thanks to femblack (Riyajudeen Mohamed yousuf) for XBlast tools if you which to support him you can buy XBlast tools from the Playstore here:
https://play.google.com/store/apps/details?id=ind.fem.black.xposed.mods
Flash a custom kernel.
NOTE: You must have a custom recovery installed (Dont have one? Check the top of this thread )
Ok, well there are quite a few reasons why to install a custom kernel. In short (very short) You can install a custom Kernel for one of these 3 reasons.
1) To improve battery life. (Undervolting)
2) To improve performance. (Overclocking)
3) Fancy features such as double tab screen to wake device (My personal favorite). Swipe across screen to sleep device etc etc.
Installing a custom kernel is actually remarkably easy especially thanks to the developers who have included AROMA installers. All you have to do is put the zip file on your SDcard boot into recovery and follow the on screen instructions.
For the purpose of this post i'm going to point you towards the ElementalX as it is the Kernel I am currently running and I have had no issues with it personally. it is also incredibly easy to set up and seems like it would serve as a good starting point for newcomers. You can find it here:
http://forum.xda-developers.com/showthread.php?t=2519607 (Thanks to flar2)
Please note that this is far from the only option when it comes to kernels its just the easiest in my opinion. if you want to see more kernels for the Nexus 5 and decide for yourself have a browse around this forum:
http://forum.xda-developers.com/google-nexus-5/orig-development
IMPORTANT: When flashing any custom kernel you must be sure you have the right build for whatever base you are running. Some ROMs are CM based others are AOSP based and so on. ALWAYS CHECK FIRST.
Thats it for now everyone! Hope this thread is of some use. Plan to add information on HALO and MultiWindow when possible as well as a few other things.
More to come!
[RESERVED
Quite nice thread for newcomers, and it might, as it grows, be a go-to for those of us who have been rooted for ages in case we forgot about some of the stuff we can do/achieve with root
One question though, why not use the features included in Rom Toolsbox Pro, since you're already using it. I has a root explorer, if you swipe once to the left in the main menu, you'll get to a Build.prop editor and one more swipe will bring you to the Boot Animations "switcher". Think about it
Nice thread, changing dpi is the first thing i do when i root, but I don't think its appropriate to call that "changing the screen resolution" , we are simply changing dpi, not resolution.
I like where this thread is going, thanks for your time just adding my support. I'm rooted. Flashed Faux Kernel but still stock. I'm still waiting for AOKP or Paranoid put out their hand even more.
Used to run carbon on my n4. But I'm just neat picky about by clock position, battery icon, toggles *torch, extended boot menu and Navbar. My main reasons I used custom ROMs.
Sent from my Nexus 5 using xda app-developers app
Gormsen said:
Quite nice thread for newcomers, and it might, as it grows, be a go-to for those of us who have been rooted for ages in case we forgot about some of the stuff we can do/achieve with root
One question though, why not use the features included in Rom Toolsbox Pro, since you're already using it. I has a root explorer, if you swipe once to the left in the main menu, you'll get to a Build.prop editor and one more swipe will bring you to the Boot Animations "switcher". Think about it
Click to expand...
Click to collapse
Honestly there is no real reason not to this, I just learnt how to do it the old fashioned way first and old habits and all that. Also the above method can be done for free using any root explorer whereas for ROM toolbox you have to pay. Also i've found that using ROM toolboxes boot animations are quite often not scaled to fit the screen properly!
Dakura said:
Nice thread, changing dpi is the first thing i do when i root, but I don't think its appropriate to call that "changing the screen resolution" , we are simply changing dpi, not resolution.
Click to expand...
Click to collapse
Thankyou, and yes you are correct, fixed it
Michael-1993 said:
Honestly there is no real reason not to this, I just learnt how to do it the old fashioned way first and old habits and all that. Also the above method can be done for free using any root explorer whereas for ROM toolbox you have to pay. Also i've found that using ROM toolboxes boot animations are quite often not scaled to fit the screen properly!
Thankyou, and yes you are correct, fixed it
Click to expand...
Click to collapse
I'm also a fan of doing things manually, so no arguing there
My though was that, when being a noob at all of this, there's a lot to handle, a lot of words and a lot of tools to use. Rom Toolbox gathers a lot of options in a single app, and might simplify things for the slow learning newcomer.
You could also teach him to set his kernel using scripts, but using an app like Trickster og System Tuner simplifies things, a lot!
Sent from my Nexus 5 using Tapatalk
Gormsen said:
I'm also a fan of doing things manually, so no arguing there
My though was that, when being a noob at all of this, there's a lot to handle, a lot of words and a lot of tools to use. Rom Toolbox gathers a lot of options in a single app, and might simplify things for the slow learning newcomer.
You could also teach him to set his kernel using scripts, but using an app like Trickster og System Tuner simplifies things, a lot!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
That's a great idea! Ill add it as soon as I get time
And yeah, you're right it is a lot to take in at first I suppose, I am trying my best to make the thread as simple as possible though I promise! i'm also planning on adding how to backup applications and accounts as well as how to dual boot multiple ROMS at some point. But yeah ROM Toolbox really is a a great tool. I may add a section dedicated just to the main features on that as well
Michael-1993 said:
That's a great idea! Ill add it as soon as I get time
And yeah, you're right it is a lot to take in at first I suppose, I am trying my best to make the thread as simple as possible though I promise! i'm also planning on adding how to backup applications and accounts as well as how to dual boot multiple ROMS at some point. But yeah ROM Toolbox really is a a great tool. I may add a section dedicated just to the main features on that as well
Click to expand...
Click to collapse
And you're doing a great job so, the OP has really grown a lot in just a couple of days.
A couple of suggestions:
1. You might wanna consider making an index, since this thread is going to grow a lot and it might end up being hard to get an overview.
2. How about a dedicated Xposed section since the possibilities with this are almost endless?
I know all of this takes time, so just get to it as you see fit. Keep up the good work
Sent from my Nexus 5 using Tapatalk
Hey Thanks for such informative thread, I subscribed to your thread and look forward to learn more.
I am interested in changing the DPI of my phone especially to the level that is on Samsung Note 2. This is purely because of the game 8 ball pool from Miniclip as the game looks different on Note 2 and different on N5. Do you have any idea what is the DPI of Note 2 v/s our phone.
Thanks.
kailashnj said:
Hey Thanks for such informative thread, I subscribed to your thread and look forward to learn more.
I am interested in changing the DPI of my phone especially to the level that is on Samsung Note 2. This is purely because of the game 8 ball pool from Miniclip as the game looks different on Note 2 and different on N5. Do you have any idea what is the DPI of Note 2 v/s our phone.
Thanks.
Click to expand...
Click to collapse
Yeah well the Note 2's DPI is set at 320 by default, but the general consensus seems to be 240 DPI looks sharpest on that phone. Bare in mind the Note 2 has a 5.5" screen though which is somewhat larger than the Nexus 5 so it may not work quite so well for you, give it ago though! Would be cool to see what you think, like I said i struggle to tolerate anything lower than 340 myself but its all personal prefrence
Thanks to joyo22 for the information. Thread is here:
http://forum.xda-developers.com/showthread.php?t=2243799
okay guys, here i'll explain how to reduce adaptive brightness (minimum) to match manual brightness (minimal) when using a kernel that supports lower minimum brightness than stock. (in this case, Zombie Kernel for Xperia Z, which is, as far as i know at the moment of writing, the only kernel for xperia z which supports this)
Disclaimer:
Im not responsible for anything that might happen to you or your phone or anything else when following these instructions.
Reguirements:
-PC with Java installed
-Notepad++ installed (recommended)
-Advanced ApkTool
-a phone (obviously) running a kernel that supports lower brightness than stock
-some basic knowlegde
1. first of all, make a nandroid backup in case something goes wrong!
2. copy your framework-res.apk and SemcGenericUxpRes.apk from /system/framework/ and from /system/framework/SemcGenericUxpRes/ and copy it to the root of your internal sd.
3. now plug in your phone to pc and move the files into the 2-in folder inside the advancedapktool folder on your pc.
4a. run advanced apktool and install frameworks (option 1).
4b. run option 2 (decompile files) and select the framework-res.apk.
5. you should now have a framework-res.apk folder in the 3-out folder in the root of the advancedapktool folder, open it and navigate to advancedapktool/3-out/framework-res.apk/res/values/
you should see something like this
now open integers.xml in notepad++ and search for the following lines:
<integer name="config_screenBrightnessDim">20</integer>
<integer name="config_screenBrightnessDark">20</integer>
change the ''20'' in to ''6'' (6 is a little bit brighter than kernel minimum, but 5 is too dark and makes the screen flickering)
so it looks like this
6. then you can recompile using option 3 in advancedapktool and option 2 in the next menu where it asks you to sign the apk. hit y and wait till its done.
7. copy the newly created framework-res.apk file found in the 4-done folder to the root of your internal sdcard.
8. using file manager, move the file to tmp/ folder and set correct permissions (rw-r-r aka 644)
9. then move the file to /system/framework/ and hit overwrite. (some apps like rootbrowser will create framework-res -copy.apk so i like to use ''file manager'' instead)
10. reboot and enjoy!
NOTE: you can also add brightness steps to the framework, they are in the arrays.xml file.
that will only add more diffferent steps to the brightness and will not reduce any brightness at all.
so, its an optional step if you like go a bit further!
the lines to look for look like this
also note, that values may differ from rom to rom and kernel to kernel and device to device. fine-tuning may be needed but this write-up defines what applied to my specific case.
Credits:
@BDFreak for the advanced apktool which prevents bootloop after decompiling/compiling.
@Tommy-Geenexus for this awesome, fast and lean kernel which supports low backlight brightness
@chiragkrishna for his guide which i used as a start guide dates from 2012 so pretty old but thanks to him i knew where to look for.
i am not a developer nor i have experience in theming or building apps or roms etc, and this decompiling was new for me too so i learned a bit and was fun. (was pretty simple though)
regards
Good stuff. I don't mind that 6 is brighter, the minimum brightness on zombie is too dark for me except on pitch blackness
Sent from my C6603 using Tapatalk
CosmicDan said:
Good stuff. I don't mind that 6 is brighter, the minimum brightness on zombie is too dark for me except on pitch blackness
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
So, do you use this also now?
langeveld024 said:
So, do you use this also now?
Click to expand...
Click to collapse
Not yet, today I will do my heatsink mod with before/after heat tests and photos and such, then ill mod the framework
Sent from my C6603 using Tapatalk
Hey mate, I decided not to use this as I tried out "Velis Auto Brightness" on Play Store (free) and it works really well, very customisable and easy to tune replacement for adaptive brightness. Downside is that it is obviously an extra service running in background, and if you want to manually adjust brightness then you have to use its own notification slider (firmware brightness slider is literally hijacked and has no effect).
I'm also running Dirty Unicorns 9.5 firmware at the moment rather than stock, which means I'm not even on Zombie anymore. Battery life and performance is impressive.
Sent from my Xperia Z using Tapatalk
CosmicDan said:
Hey mate, I decided not to use this as I tried out "Velis Auto Brightness" on Play Store (free) and it works really well, very customisable and easy to tune replacement for adaptive brightness. Downside is that it is obviously an extra service running in background, and if you want to manually adjust brightness then you have to use its own notification slider (firmware brightness slider is literally hijacked and has no effect).
I'm also running Dirty Unicorns 9.5 firmware at the moment rather than stock, which means I'm not even on Zombie anymore. Battery life and performance is impressive.
Sent from my Xperia Z using Tapatalk
Click to expand...
Click to collapse
Okay cool bro, I've already read that in zombie threat lol
Anyway if u need the framework-res.apk, I made if for existenz rom so if anyone is interested I can put it online :thumbup: