Flashing this will enable navigation bar, and disable capacitive touch buttons on Nexus S.
Make sure to set the Backlight Dimmer delay to 0 using the NSTools, so the capacitive touch buttons don't light up.
If you are using the navigation bar, I recommend setting the LCD density to 200 or 190. Edit it with Rom toolbox, or
navigate to /system/build.prop/ro.sf.lcd_density=200 edit it with text editor and reboot.
Always do a backup before flashing. It should work for any JB rom.
To disable navigation bar, reflash the rom, restore the backup or flash disable nav bars.
You are doing this at your own risk.
Its based on Brainmaster's tweaks for android, all thanks goes to him.
Added files, they set dpi to 190 or 200 or disable Nav bars.
Screenshots please.
Gesendet von meinem Nexus S mit Tapatalk 2
AzN MusiQ said:
Screenshots please.
Gesendet von meinem Nexus S mit Tapatalk 2
Click to expand...
Click to collapse
You get these three buttons on bottom of your screen.
http://cdn3.digitaltrends.com/wp-co.../samsung-galaxy-nexus-review-home-buttons.jpg
Or you can just add
qemu.hw.mainkeys=0
To your build.prop and reboot. It works with every ROM I think. To disable, just set it back to =1.
Sent from my Nexus S using xda premium
But that won't disable the capacitive buttons
Sent from my Nexus S using xda app-developers app
Does DPI of 200 break the play store? I'm at 210 and its breaking some installs
tehkraft said:
Does DPI of 200 break the play store? I'm at 210 and its breaking some installs
Click to expand...
Click to collapse
First time I went from 240 to 200, I wiped googleplay, everything else worked okay, as far as I remember.
If you get FC's wipe that app.
If BLD is set to zero, this will just turn off the backlight right, but they will still work when pressed. Is there a way to disable them for real otherwise what's the point of the nav bars, right?
Sent using the xda mobile app
apatal said:
If BLD is set to zero, this will just turn off the backlight right, but they will still work when pressed. Is there a way to disable them for real otherwise what's the point of the nav bars, right?
Sent using the xda mobile app
Click to expand...
Click to collapse
They are disabled...
Serris said:
They are disabled...
Click to expand...
Click to collapse
Oh OK. So the zip turns then off already. Question though, in the BLD settings, setting it to zero turns off BLD meaning the buttons are always lighted up. I set it to 1 to turn it off almost immediately.
Sent using the xda mobile app
apatal said:
Oh OK. So the zip turns then off already. Question though, in the BLD settings, setting it to zero turns off BLD meaning the buttons are always lighted up. I set it to 1 to turn it off almost immediately.
Sent using the xda mobile app
Click to expand...
Click to collapse
Yes you are correct, I used NSTools, and set it to 0, I assumed its the same with CM settings, I will try to fix it. Thanks
EDIT: OK no go, CMsettings work like that, if its set to BLD 0 its always on, NSTools looks like overrides it.
great! this is working just great. really thanks! but i don't see any problem by leaving screen density to 240 though. been opened all apps installed on my ns
quick edit: i am using CM 10 nightly
What's about the menu button? Is it build in the apps? Can I configured them?
Gesendet von meinem Nexus S mit Tapatalk 2
AzN MusiQ said:
What's about the menu button? Is it build in the apps? Can I configured them?
Gesendet von meinem Nexus S mit Tapatalk 2
Click to expand...
Click to collapse
Yes you can see the three dots in the navigation bar, and in aplications
Serris said:
Yes you are correct, I used NSTools, and set it to 0, I assumed its the same with CM settings, I will try to fix it. Thanks
EDIT: OK no go, CMsettings work like that, if its set to BLD 0 its always on, NSTools looks like overrides it.
Click to expand...
Click to collapse
I'm using a script it works like a charm with 0 if you don't use bln.
Sent from my Nexus S using xda premium
BenHeng said:
I'm using a script it works like a charm with 0 if you don't use bln.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
So all you have to do, is disable BLN, and put below code(script) in init.d?
Code:
echo 1 > /sys/devices/virtual/misc/backlightdimmer/enabled
echo 0 > /sys/devices/virtual/misc/backlightdimmer/delay
Works for me at least
Sent from my Nexus S using xda premium
Tried the mod last night and it works! Unfortunately, my fingers are already too big for the default PDI, and reducing it to 200 won't really help me very much. Thanks for sharing this anyway. I'm sure some users have been looking for this.
Sent using the xda mobile app
apatal said:
Oh OK. So the zip turns then off already. Question though, in the BLD settings, setting it to zero turns off BLD meaning the buttons are always lighted up. I set it to 1 to turn it off almost immediately.
Sent using the xda mobile app
Click to expand...
Click to collapse
in order to turn off capacitive buttons follow these:
1. using root browser lit go to system.
2.then "usr" then " keylayout"
3. open sec_touchscree.kl > open as > text file > rb text editor
4. insert "#" in front of lines u want to make them stop working.
like
#key 158 BACK virtual
will make back button stop working.
Hello, is there a way to change UC settings that offer power save mode ?
I mean by default UC Power save mode underclock our CPU to 1000MHZ single core..
is there a way to change it to 1200mhz dual core or something like that ?
I am interesting to same topic. I want to more gpu performance in power saver mode
Sent from my MZ601 using xda app-developers app
Is any one else seeing the gesture typing and keyboard popping up laging. I have to reboot my phone every morning as the lag starts, the night before it's fine.
Symptoms, select a text entry box and the back key turns into the down arrow, but the keyboard does not appear, click the down arrow and click in the text box again keyboard will appear but delayed, then gesture type and everything lags, words are not formed by your finger fluid, the path is not shown in real time and when I have finished the word it takes a second to show up in the box.
I thought it may be the fact I use tasker to manage bedside clock starting only when i plug in at night, but I have done testing during the day and it does not happen.
Are you on the stock ROM and stock kernel?
Sent from my Nexus 4 using xda premium
most likely a CPU scaling problem.
if you're not on stock rom, try to switch to the performance governor and try if it works better
Change governors and kernels. On ondemand I had laggy swype, of course I'm UC to 1.35 GHz.
Sent from my Nexus 4 using xda app-developers app
steviewevie said:
Are you on the stock ROM and stock kernel?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Completley stock not even rooted
rpudner said:
Completley stock not even rooted
Click to expand...
Click to collapse
A little more info, I found that if I wait for the keyboard to pop up( can be 15 - 20 seconds) then press the microphone for voice typing, exit this it all works fine ????
In setcpu I set a profile to switch the governor to conservative. So when I open the browser I can tell it sets conservative by using cool tools, and when I close the browser, it switches my governor back to interactive but the tweaks (hispeed_freq, timer_rate) reset back to their default values, instead of the ones I set. And yes I checked "set with profiles".
Has anyone experienced this? I wanted to double check before I sent them an email.
Try Trickster Mod. That is what I use, and have had no problems. I haven't used SetCPU since my DD was a Captivate
peneoark said:
Try Trickster Mod. That is what I use, and have had no problems. I haven't used SetCPU since my DD was a Captivate
Click to expand...
Click to collapse
Thanks for the suggestion I'll give it a try. But I've experienced this before on my gs3 with another kernel app (ktoonsez ktweaker) which led me to believe its present on all apps.
I have an S3 and also use KT747, and have not had the issues with Ktweaker. Do you have them set to enable at boot? If so, try changing them to a delay of 15 seconds. That's what I had to do with Ktweaker, and do the same on all other kernel apps.
peneoark said:
I have an S3 and also use KT747, and have not had the issues with Ktweaker. Do you have them set to enable at boot? If so, try changing them to a delay of 15 seconds. That's what I had to do with Ktweaker, and do the same on all other kernel apps.
Click to expand...
Click to collapse
Yes, I did set it on boot, actually everything sets fine on boot. Its when switching governors, like when I set a different screen off governor, some governor adjustments stick, others like sampling rate get set back to default.
That sounds normal. Does SetCPU have a setting backup? If so, try backing up, then loading if you want.
Why are you changing govs that much?
peneoark said:
That sounds normal. Does SetCPU have a setting backup? If so, try backing up, then loading if you want.
Why are you changing govs that much?
Click to expand...
Click to collapse
Well I use interactive as my governor, but I tweak it for better battery life. Then I like the conservative governor when in the browser or when battery drops below a certain level. But when I close the browser and my gov switches back to interactive, some tweaks are set back to default instead of what I set.
I haven't read anything about this being intended or normal behavior but I guess that's an explanation..
Sent the developer an email this morning, still waiting to hear back
Does anyone know what the CPU power saving mode scales down? I know that the CPU is underclocked to 1000MHz, but I would like to know whether some other CPU scaling/core usage internal settings are altered.
I'm asking this because when I turn power saving on, I notice some lag when swiping through homescreens and the app drawer, whereas I do not when I manually set the maximum frequency to 1000MHz with SetCPU (with the phone's power saving option turned off).
You should try cpu tweaker.
You can't really find out unless you manually open all the respective files in sys partition.
Sent from my GT-N7100 using xda premium
Does CPU tweaker give all CPU information so that I can check what settings are being changed with power saving mode? I already use SetCPU and STweaks (for kernel settings)
It will show offline cpus and ghz.
To see other stuff like governor or scalling factor and all you will need to open each file manually which are located in sys folder.
Sent from my GT-N7100 using xda premium