While the development is still in its infancy here,
lets post here a bunch of do it yourself tweaks.
Feel free to post any rom tweaks you know of.
In the file /system/etc/init.qcom.post_boot.sh , find the section
case "$target" in
"msm8960" | jaguar* | M2* | m2* )
Click to expand...
Click to collapse
then modify the following value:
echo 80 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold
Click to expand...
Click to collapse
This will improve the touchscreen responsiveness.
Add the following line at the end of the msm8960 section:
echo 1024 > /sys/devices/virtual/bdi/179:0/read_ahead_kb
Click to expand...
Click to collapse
This will speed up loading of apps somewhat.
Reboot for changes to take effect.
In the same file you can have it run every init.d file if you don't have init.d support.
Sent from my SPH-D700 using Tapatalk 2
governor tweaks
if on the on-demand governer i recommend you change the sampling rate to 70,000, it improves the devices scaling performance i.e if your device is sitting for a sec. and you touch the screen it should jump to a higher frequency to perform the action faster at the cost of a little bit higher battery consumption but a minuscule amount. And of course please all use the noop i/o scheduler it really does improve responsivness of the phone by alot.
I will aslo be uploading a sys ctl.conf tweak to greatly improve our battery life my og epic increased by 3 hours because of this it is a cwm flashable but for those who dont feel like using it you can always use a root explorer and copy and paste or adb push it. i will post when i know it works
file is migrating to new host this is the link you have to take it apart and either copy and paste or adb push, the install script is giving me trouble will post back when i get around to fixing it unless some brave soul would like to fix it for me idc its all about you guys so if you wanna beat me to it be my guest
and remember always make a nandroid
I would also like to say i did not create this and i have absolutly no idea who did this mod has been circulating around xda's htc forums,android central, and droid forums as far as im concerned the maker of this mod is untraceable.
V6supercharger makes a world of a difference in the memory management section and no ram is waisted it is devoted to the cache for our devices its a pain to set up because we are on odex stock devices ice is a bitc* that way haha.
I found this thread here with several build.prop tweaks... He claims they work on all devices. I am an Android newbie so I can not verify that information.
http://forum.xda-developers.com/showthread.php?t=1639104
matrixzone5 said:
if on the on-demand governer i recommend you change the sampling rate to 70,000, it improves the devices scaling performance i.e if your device is sitting for a sec. and you touch the screen it should jump to a higher frequency to perform the action faster at the cost of a little bit higher battery consumption but a minuscule amount. And of course please all use the noop i/o scheduler it really does improve responsivness of the phone by alot.
I will aslo be uploading a sys ctl.conf tweak to greatly improve our battery life my og epic increased by 3 hours because of this it is a cwm flashable but for those who dont feel like using it you can always use a root explorer and copy and paste or adb push it. i will post when i know it works
Remove this is the link you have to take it apart and either copy and paste or adb push, the install script is giving me trouble will post back when i get around to fixing it unless some brave soul would like to fix it for me idc its all about you guys so if you wanna beat me to it be my guest
and remember always make a nandroid
I would also like to say i did not create this and i have absolutly no idea who did this mod has been circulating around xda's htc forums,android central, and droid forums as far as im concerned the maker of this mod is untraceable.
Click to expand...
Click to collapse
Gotta ask you to remove your link. Third-party downloads that require signing in/up are prohibited.
I'm sorry about that bro I understand its totally annoying I forgot u gotta sign up now for 4shared ill upload it to media fire the second I get a chance
Note to mod* remove if you can please
Sent from my SPH-L710 using XDA
Doesn't build.prop cover most do-it-yourself tweaks?
Yes but there's still ur susctl .conf file u can play with if u go to sustem/etc I believe there is a file u can edit to boost the Max speaker volune
I personally love ofinding new little tweaks to apply and edit in android I love poking and prodding around just to find out what does what whether removing this and replacing it with *,that will benefit perform
Sent from my SPH-L710 using XDA
Terminal emulator cmd
getprop til.MSL Works for getting your msl # to change the settings for faster 3g in ##DATA# menu under the multimedia tab.
If you know what I mean.
Sent from my PB GS3 using XDA
Tewlman252 said:
Terminal emulator cmd
getprop til.MSL Works for getting your msl # to change the settings for faster 3g in ##DATA# menu under the multimedia tab.
If you know what I mean.
Sent from my PB GS3 using XDA
Click to expand...
Click to collapse
I've tried this both with
Code:
getprop til.MSL
&
Code:
getprop ril.MSL
and can't get it to display the MSL, any ideas?
And yes I entered "su" prior to typing the cmd, I actually have terminal setup to do that automatically.
Sent from my SPH-L710 using Tapatalk 2
Strange, it worked for me the first time but now no luck.
Sent from my SPH-L710 using XDA
Tewlman252 said:
Strange, it worked for me the first time but now no luck.
Sent from my SPH-L710 using XDA
Click to expand...
Click to collapse
That's weird, hmmph.
Sent from my Transformer TF101 using Tapatalk 2
carhauler1969 said:
I've tried this both with
Code:
getprop til.MSL
&
Code:
getprop ril.MSL
and can't get it to display the MSL, any ideas?
And yes I entered "su" prior to typing the cmd, I actually have terminal setup to do that automatically.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
What app are you using to control ur su binary? Super user?
And did you try typing just get prop and scrolling through
Sent from my GT-I9100 using xda app-developers app I recommend using supersu by chain fire for super user on ics
Tewlman252 said:
Terminal emulator cmd
getprop til.MSL Works for getting your msl # to change the settings for faster 3g in ##DATA# menu under the multimedia tab.
If you know what I mean.
Sent from my PB GS3 using XDA
Click to expand...
Click to collapse
Can you clarify this? Thanks
Courtesy of our own Qbking77
http://www.youtube.com/watch?v=RQRZ2Z_IQkY&feature=youtube_gdata_player
This is how I got it to work the first time on my GS3 from Sprint but subsequent tries have failed. Not sure if it's just a one time thing or not.
Needless to say, now that I have my MSL, I don't need to get it again unless I switch devices.
Sent from my SPH-L710 using XDA
Another tip to save battery is enable power saving mode. It automatically scales back the cpu governor to a max speed of 1.026 ghz. Unless you're gaming, this should be fine for day to day usage.
I have tested this with cpu spy and no frills cpu control.
Sent from my SPH-L710 using XDA
nabbed said:
While the development is still in its infancy here,
lets post here a bunch of do it yourself tweaks.
Feel free to post any rom tweaks you know of.
In the file /system/etc/init.qcom.post_boot.sh , find the section
then modify the following value:
This will improve the touchscreen responsiveness.
Add the following line at the end of the msm8960 section:
This will speed up loading of apps somewhat.
Reboot for changes to take effect.
Click to expand...
Click to collapse
echo 80 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold
this part showed a 90 in my script. i just want to verify that the instruction is to change the 90 to an 80. or is the instruction to alter it how i wish, and the 80 is just what you picked?
stretchwookie said:
echo 80 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold
this part showed a 90 in my script. i just want to verify that the instruction is to change the 90 to an 80. or is the instruction to alter it how i wish, and the 80 is just what you picked?
Click to expand...
Click to collapse
Its alot easier if you used an app like setcpu and go to governed setting ans change the up thresh hold to 80 remember the lower the number the higher the performance at the cost of Max battery life but never set it to 100 it freezes really badly. 99 is even a stretch u shudnt need to go over 95
Sent from my SPH-L710 using xda app-developers app
Related
Does any one have any files or links? Cant find any info on this for the incredible 2.
fbmustang69 said:
Does any one have any files or links? Cant find any info on this for the incredible 2.
Click to expand...
Click to collapse
what exactly are you trying to edit in the build.prop??
Anything really from how the phone responses to what it does when you make a call. When i had my x people had buils.prop files where they changed certain things to make the operate better.
NVM moto and htc build.prop files do not controll the same type of thing. I will just search want each line means so i know what i can change to what.
fbmustang69 said:
NVM moto and htc build.prop files do not controll the same type of thing. I will just search want each line means so i know what i can change to what.
Click to expand...
Click to collapse
You can edit things like VM heap.. name of ROM, .. although VM heap can also be changed easily with an app. use something like root explorere and build.prop is in system. u should be able to open it up and just read it and see what you're able to change..
andybones said:
You can edit things like VM heap.. name of ROM, .. although VM heap can also be changed easily with an app. use something like root explorere and build.prop is in system. u should be able to open it up and just read it and see what you're able to change..
Click to expand...
Click to collapse
What are recommended build.prop modifications for use with the Incredible 2 as far as optimization goes?
bracketslash said:
What are recommended build.prop modifications for use with the Incredible 2 as far as optimization goes?
Click to expand...
Click to collapse
I'd keep VM heap at 32, since there's not much point in increasing it unless you happen to run apps that require more of the dalvik vm.
artvandelay440 said:
I'd keep VM heap at 32, since there's not much point in increasing it unless you happen to run apps that require more of the dalvik vm.
Click to expand...
Click to collapse
I agree. It's annoying to see apps use more then that and more then likely things will slow down if you have a buggy written app.
Sent from my Incredible 2 HD using xda premium
I used some from these links and they worked fine.
http://fourm.xda-developers.com/showthread.php?t=1151608
http://fourm.xda-developers.com/showthread.php?t=1249628
I think we need sub forums inside of the sub forums inside the subforums! All im trying to find is how to increase the fps to 240....i found it once and did it and everything really did look much smoother.....now i cant find it....mean while im looking for it....next thing you know im d/l GTA hd and google body and then i forget where i was.....and ahhhhhhhhhhhhhhhh!!!!!!!!!!!!! Too much stuff!!!!!!! we need a sub forum for boot ani's one for issues....one for how too's...one for fixes...toooooooooooo much stufff!!!!!!!!!!!!!
Sounds like too much coffee, too... Decaf ftw
Terminators run on Android
Someone needs a hug
Sent from my Google phone
LOL!!
There's an app for that.
Sent from my MB860 using xda premium
Your holding it wrong.
You mean this:
http://forum.xda-developers.com/showpost.php?p=20905882&postcount=1865
Code:
Disable error checking. Gives a nice speed boost.
ro.kernel.android.checkjni=0
This one sets the max framerate of the system to 240 fps. (Well beyond the screen's ability to render. I did notice a nice difference in smoothness.)
windowsmgr.max_events_per_sec=240
link: http://rootzwiki.com/topic/13426-mod-buildprop-tweaks-to-improve-performance/
In closing. if this setup doesn't fit your criteria nothing will.
Have a great day.
player911 said:
Your holding it wrong.
You mean this:
http://forum.xda-developers.com/showpost.php?p=20905882&postcount=1865
Code:
Disable error checking. Gives a nice speed boost.
ro.kernel.android.checkjni=0
This one sets the max framerate of the system to 240 fps. (Well beyond the screen's ability to render. I did notice a nice difference in smoothness.)
windowsmgr.max_events_per_sec=240
link: http://rootzwiki.com/topic/13426-mod-buildprop-tweaks-to-improve-performance/
In closing. if this setup doesn't fit your criteria nothing will.
Have a great day.
Click to expand...
Click to collapse
Thank you! I searched and looked everywhere lol
Sent from my Galaxy Nexus using Tapatalk
This is a dirty fix. I have an idea for a better fix but I am unable to implement it.
These are scripts to be run with Script Manager.
Code:
led_on script:
#!/system/bin/sh
print 80 > /sys/class/leds/button-backlight-portrait/brightness
print 80 > /sys/class/leds/button-backlight-landscape/brightness
led_off script:
#!/system/bin/sh
print 0 > /sys/class/leds/button-backlight-portrait/brightness
print 0 > /sys/class/leds/button-backlight-landscape/brightness
The value can be set from 0 to 255. I chose 80 as it is good enough and also due to a known issue, as explained below.
Obviously enable root browsing in SManager and run this as root. You can also run led_on at boot if needed. This is a fix when not using auto-brightness.
This will cause the capacitive buttons to ALWAYS be on, even when the screen is off. A simple idea is to check the status of the screen and then appropriately modify that file. But this means a service running in the background and is probably wasteful on resources. But if someone can help me out or have ideas, go ahead and do so. But once done, please lemme know as I am trying to learn.
Lemme know of other issues!
Cheers!
litetaker said:
This is a dirty fix. I have an idea for a better fix but I am unable to implement it.
These are scripts to be run with Script Manager.
Code:
led_on script:
#!/system/bin/sh
print 50 > /sys/class/leds/button-backlight-portrait/brightness
led_off script:
#!/system/bin/sh
print 0 > /sys/class/leds/button-backlight-portrait/brightness
The value can be set from 0 to 255. I chose 50 as it is good enough and also due to a known issue, as explained below.
Obviously enable root browsing in SManager and run this as root. You can also run led_on at boot if needed. This is a fix when not using auto-brightness.
This will cause the capacitive buttons to ALWAYS be on, even when the screen is off. A simple idea is to check the status of the screen and then appropriately modify that file. But this means a service running in the background and is probably wasteful on resources. But if someone can help me out or have ideas, go ahead and do so. But once done, please lemme know as I am trying to learn.
Lemme know of other issues!
Cheers!
Click to expand...
Click to collapse
Awesome work. I'm not feeling so well tonight or I would look into it bro.
Sent from my Incredible 2 using xda premium
litetaker said:
This is a dirty fix. I have an idea for a better fix but I am unable to implement it.
These are scripts to be run with Script Manager.
Code:
led_on script:
#!/system/bin/sh
print 50 > /sys/class/leds/button-backlight-portrait/brightness
led_off script:
#!/system/bin/sh
print 0 > /sys/class/leds/button-backlight-portrait/brightness
The value can be set from 0 to 255. I chose 50 as it is good enough and also due to a known issue, as explained below.
Obviously enable root browsing in SManager and run this as root. You can also run led_on at boot if needed. This is a fix when not using auto-brightness.
This will cause the capacitive buttons to ALWAYS be on, even when the screen is off. A simple idea is to check the status of the screen and then appropriately modify that file. But this means a service running in the background and is probably wasteful on resources. But if someone can help me out or have ideas, go ahead and do so. But once done, please lemme know as I am trying to learn.
Lemme know of other issues!
Cheers!
Click to expand...
Click to collapse
I see you have something for lights in portrait. Maybe also write it for landscape as the lights always go out in landscape.
Sent from my Incredible 2 using xda premium
knipp21 said:
I see you have something for lights in portrait. Maybe also write it for landscape as the lights always go out in landscape.
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
Did that. This fix is a very hackey one! I wish I could make a more clean one later...
I see a few people asking about this and I found this app that works on my HTC One X.
Screen Filter:
https://play.google.com/store/apps/details?id=com.haxor&hl=en
If you just want to switch the lights off, set the filter to 100% then un-tick the enable softkey back light. It works great when watching videos or using it as a nightstand clock.
Hope their wasn't a thread about his. I did a few searches and couldn't find anything, hope this helps a few people.
Does it save the preference after reboot? I use Adjbrightness and after rebooting I have to load the app up again.
Sent from my HTC One X using xda app-developers app
I will have a look but I think you have to reopen it.
Sent from my HTC One X using xda app-developers app
I had a test now and it doesn't start on boot. But when you start the app after a boot it then knows what your last settings were. Hope that helps.
Sent from my HTC One X using xda app-developers app
K, when I have the time I was thinking of writing my own app that does this.
Sent from my HTC One X using xda app-developers app
If u put the app (screenfilter) in some autostart program it will work fine, if u dont wanna enable it manually.
This text was generated by a HoX device, in symbiosis with thoughts from someone else
ououououo said:
If u put the app (screenfilter) in some autostart program it will work fine, if u dont wanna enable it manually.
This text was generated by a HoX device, in symbiosis with thoughts from someone else
Click to expand...
Click to collapse
That is a great idea, I was wondering if there was an app like that I will have a look and see how well that works. But it's really nice to disable those lights, gives the phone a really neat appearance.
Roars21 said:
That is a great idea, I was wondering if there was an app like that I will have a look and see how well that works. But it's really nice to disable those lights, gives the phone a really neat appearance.
Click to expand...
Click to collapse
I did this on my previous device (xperia u, to get rid of the annoying LED-bar )
NOTE:
*** If you accidentally make your screen go BLACK ***
1. Pull your battery
2. Uninstall the app to reset your bad brightness setting
3. Reinstall the app and use it normally again"
Click to expand...
Click to collapse
I am kinda worried about this happening on my HOX...the fist step is already too much trouble to go through.
jimmy2027 said:
I am kinda worried about this happening on my HOX...the fist step is already too much trouble to go through.
Click to expand...
Click to collapse
Don't worry if you hold down the power button for a couple seconds it simulates a battery pull. Then when you start up, provided you don't have it on a autostart app you can then go in and change the settings. Also if you do set the brightness too low it gives you 10 seconds to approve it or it will just revert your settings. If that makes sense.
Make a new file, call it 99KeyOff.sh and put this in it:
#!/system/bin/sh
# ========================================
# init.d script for key light off. ONE X.
#BACKFROMTHE[/QUOTE]STORM
# ========================================
#disable Key Backlight
echo begin set Key Backlight - KB
echo KB - set permissions rw
chmod 0666 /sys/class/leds/button-backlight/brightness
echo KB - set Key Backlight 0
echo "0" > /sys/class/leds/button-backlight/brightness
echo KB - set permissions ro
chmod 0444 /sys/class/leds/button-backlight/brightness
echo KB - done!
Put it in the init.d folder or run it manually in a terminal emulator or script manager.
Unfortunately that doesn't work on the Maximus ROM. I think it's because the rootfs mounts read only. I tried adding a remount line to the top but nothing happened.
Sent from my HTC One X using xda app-developers app
Screen Dimmer
The minimum screen brightness is too damn bright to use in the dark.
Run the app, click "Load" next to "n5dim", change your brightness to the minimum (and then up a bit and back down) and notice how much dimmer it is.
The brightness at all other levels stay the same.
Source: https://github.com/mzhou/n5dim
Fast Charge
This works by setting the registers on the bq24192 charger chip to allow as much input current (from USB/AC) as possible, as well as allowing as high a charge current as possible (to the battery).
From limited tests I've performed in the past, this actually isn't enough to get faster charging, so further investigation will be needed, though your testing will be much appreciated.
It will take effect on the first time you plug in after clicking "Load". If you're already plugged in, you need to unplug and replug for it to take effect.
Source: https://github.com/mzhou/n5charge
General
To use either of these, you need any kernel which supports modules (CONFIG_MODULES=y).
I've attached (modules_boot.img) a stock kernel with the config changed to support modules.
modules_441_boot.img is for 4.4.1, while modules_boot.img is for 4.4.0.
Does this dim further than setting '1' in /sys/devices/mdp.0/qcom,mdss_fb_primary.160/leds/lcd-backlight?
(Also I noticed your CSE email, a fellow UNSW student?)
Cyb3rGlitch said:
Does this dim further than setting '1' in /sys/devices/mdp.0/qcom,mdss_fb_primary.160/leds/lcd-backlight?
(Also I noticed your CSE email, a fellow UNSW student?)
Click to expand...
Click to collapse
Yes. Dragging the brightness slider to the minimum already sets 1 there.
There's values hard coded in the platform data to internally restrict the value to a minimum of 5 (but that's of little consequence).
The main gain is is from the "full scale current" (you can find an explanation in the datasheet for lm3630) which has been hard coded to 18 in the platform data. Bringing it down to 0 makes a huge difference.
(sup)
Nice work! I wonder why they limited it. Possibly to stop people putting their phone into an unusable state during the day?
Cyb3rGlitch said:
Nice work! I wonder why they limited it. Possibly to stop people putting their phone into an unusable state during the day?
Click to expand...
Click to collapse
I've done it to myself many times when I did this to my old phone.
Also updated the attachment in the OP to be compatible with more kernels.
Tested working on Franco.
Very cool! :good:
AWESOME! Is there maybe a mod like this for the NN7 (new nexus 7 )
Is there any advantage to this method over using an app like lux?
Sent from my Nexus 5 using XDA Premium 4 mobile app
adzjwarner said:
Is there any advantage to this method over using an app like lux?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No app will be able to get the backlight this dark.
I'm not sure what Lux does, but if it modifies the colours to produce a darkening effect, then the contrast will be very bad.
adzjwarner said:
Is there any advantage to this method over using an app like lux?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey there, I'm actually the developer of Lux. The main purpose of Lux is to replace your auto brightness system without the need for root access. That being said, there's no reason why this neat kernel module couldn't be added to a root plugin for Lux.
Cyb3rGlitch said:
Hey there, I'm actually the developer of Lux. The main purpose of Lux is to replace your auto brightness system without the need for root access. That being said, there's no reason why this neat kernel module couldn't be added to a root plugin for Lux.
Click to expand...
Click to collapse
Ah cool.
I tried out Lux and I'm not sure if it's a limitation in the free version, but it only sets the backlight brightness (/sys/class/leds/lcd-backlight/brightness) to a minimum of 10 before it starts doing colour adjustment instead.
My module treats the value 1 as special for making the backlight super dark. Dragging Android's built in brightness slider uses the full range of values 1-225 inclusive.
There's no reason it couldn't just map the full 1-255 to a wider range, but I initially wanted to lean towards keeping things as stock as possible.
arararagi said:
Ah cool.
I tried out Lux and I'm not sure if it's a limitation in the free version, but it only sets the backlight brightness (/sys/class/leds/lcd-backlight/brightness) to a minimum of 10 before it starts doing colour adjustment instead.
My module treats the value 1 as special for making the backlight super dark. Dragging Android's built in brightness slider uses the full range of values 1-225 inclusive.
There's no reason it couldn't just map the full 1-255 to a wider range, but I initially wanted to lean towards keeping things as stock as possible.
Click to expand...
Click to collapse
It does that because some devices do silly things near 0 like putting the device to sleep. You can change the minimum brightness in settings to 1 which should fix this (although I suspect it might round 0.01*255 to 2. I'll have to check my codebase).
Cyb3rGlitch said:
It does that because some devices do silly things near 0 like putting the device to sleep. You can change the minimum brightness in settings to 1 which should fix this (although I suspect it might round 0.01*255 to 2. I'll have to check my codebase).
Click to expand...
Click to collapse
Somehow overlooked that when I was skimming the settings. (And it does round to 2 ).
I could make 2 or anything less than 5 special so that Lux users can benefit. Or maybe just make it configurable with a parameter at insmod time...
arararagi said:
Somehow overlooked that when I was skimming the settings. (And it does round to 2 ).
I could make 2 or anything less than 5 special so that Lux users can benefit. Or maybe just make it configurable with a parameter at insmod time...
Click to expand...
Click to collapse
Whatever you feel works best. A parameter sounds like the most flexible solution though.
This is exactly what I was looking for!
Could I get a bit more explanation of how to install this though? Do I flash the kernel in recovery and then run the command from a shell on my phone, or on my computer?
Thanks for making this.
Sent from my Nexus 5 using xda app-developers app
I'll be watching this thread intently. I currently use lux as well.
rockingondrums said:
I'll be watching this thread intently. I currently use lux as well.
Click to expand...
Click to collapse
Ditto!
Sent from my Nexus 5 using XDA Premium 4 mobile app
Nelsocracy said:
This is exactly what I was looking for!
Could I get a bit more explanation of how to install this though? Do I flash the kernel in recovery and then run the command from a shell on my phone, or on my computer?
Thanks for making this.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Flash the kernel in whatever normal way you choose.
Extract and copy n5din.ko to your phone.
Use root and put it in /data so that apps with SD card access can't mess with it.
Run "insmod /data/n5dim.ko" on your phone. This can be with a terminal emulator or adb or script manager.
I'm probably gonna be making more modules so I might make an app to simplify the process.
Cyb3rGlitch said:
Hey there, I'm actually the developer of Lux. The main purpose of Lux is to replace your auto brightness system without the need for root access. That being said, there's no reason why this neat kernel module couldn't be added to a root plugin for Lux.
Click to expand...
Click to collapse
OhHai! Big fan of the app, it's saved my eyes when internetting in bed for many many months now! (Though I probably should just not internet at night)
I'll leave the plugin stuff to somebody who knows how to do that and rejoice when(if) it happens. :good:
arararagi said:
Flash the kernel in whatever normal way you choose.
Extract and copy n5din.ko to your phone.
Use root and put it in /data so that apps with SD card access can't mess with it.
Run "insmod /data/n5dim.ko" on your phone. This can be with a terminal emulator or adb or script manager.
I'm probably gonna be making more modules so I might make an app to simplify the process.
Click to expand...
Click to collapse
That worked perfectly, thanks.
This is really dim! I'm impressed. If you ever decide to modify it like you mentioned earlier so that the full brightness adjustment was available I'd be interested. It would be useful to have access to all the brightness levels between yours and the ordinary minimum brightness.
Sent from my Nexus 5 using xda app-developers app