Related
This is quite a simple howto and I don't even know if it's appropriate to post it here instead on legend general. I post here as it requires root privileges, if someone think this is the wrong section for it just ask a mod to move it somewhere else
This (quite simple) howto is intended if you are experiencing lags or slowdowns with live wallpapers, and it's working very well for me. I think most of you can do this without an howto but I hope someone less experienced in messing with terminal will find it useful I just try to help.
Will work better if you disable the wallpaper scrolling in the launcher's properties. The thread is titled 'renice live wallpapers' but I found it works better to renice the launcher. However you can try both
I would like to thank BlaY0 for the help.
you'll need:
- root privileges
- a terminal emulator
- live wallpapers
- GScript
what you have to do is:
- download GScript from market (lite or paid version, works with both)
- launch it, then press Menu/Add script
- give it a name, be sure to check 'Needs SU', then type this in the text field below
renice -15 `pgrep android.process.acore'
where android.process.acore is the LauncherPro process name. If you're using another launcher you have to do a google search and find its
process name
- now save, and try executing it and see if it works
- add a shortcut to GScript on your home which launches the script. With this approach you have to launch it after every reboot
Maybe you want to try to renice the live wallpaper too (this may slow it down, I would not suggest to do it). To do this
- launch the terminal
- write 'ps' then press enter
- will appear a list of processes. here you should find one that has a name similar to the LWP you're using (for example, I'm using Pixel Zombies Infection and the process name is haydenTheAndroid.liveWallpaper.pixelZombies)
now you can renice it either from terminal or from GScript.
To renice from terminal:
- check the number *** which the process has in the PID row. You have to remember this number
- write 'su' then press enter. now you have root privileges
- write 'renice N ***' where N is the nice number you want (20=minimum priority ; -20=maximum priority, which you obviously don't want). You can set it to 20 to give the LWP the minimum priority
To renice from GScript go in the script you already created and add a similar line, by substituting "-15" with "20" and the process name with your LWP's process name.
You should now see an increased smoothness when scrolling homescreens and app drawer
wow will try...............
FOLLOW ME http://smartsreenath.blogspot.com/
Thanks, let me know
Sent from my Legend using Tapatalk
Corra said:
...
what you have to do is:
- launch the terminal
- write 'ps' then press enter
- will appear a list of processes. here you should find one that has a name similar to the LWP you're using (for example, I'm using Pixel Zombies Infection and the process name is haydenTheAndroid.liveWallpaper.pixelZombies)
- now check the number *** which it has in the PID row. You have to remember this number
- write 'su' then press enter. now you have root privileges
- write 'renice N ***' where N is the nice number you want (20=minimum priority ; -20=maximum priority, which you obviously don't want). You can set it to 20 to give the LWP the minimum priority
...
Click to expand...
Click to collapse
Just tried it out with the Light Grid LWP (com.joko.lightgrid) and ADW Launcher. All I can say is that this feeling is so smooth, it is like an angel pissed on my Legend just now
PS: I used adb instead of terminal emulator.
LOL this is pure poetry
Sent from my Legend using Tapatalk
Hi , i tried this and it really works!
But it is at the cost of the smoothness of the LWP i guess our puny 600mhz processor aint up to speed to handle LWP properly T^T
I oupdated with a script that does the procedure automatically but I'm encountering some issues with its permissions... no time to think about it now, will try again later
D-Lo said:
Just tried it out with the Light Grid LWP (com.joko.lightgrid) and ADW Launcher. All I can say is that this feeling is so smooth, it is like an angel pissed on my Legend just now
Click to expand...
Click to collapse
Hey, I'm the dev for Light Grid. Just wondering about performance issues - did you try the Battery Life slider in the Performance settings? That should lower the amount of time Light Grid spends taking up the CPU, which should help 'lag' issues.
Will this setting keep after a reboot?
Of course not...
You would need a script that would do that on every reboot.
JokoInteractive said:
...
Just wondering about performance issues - did you try the Battery Life slider in the Performance settings? That should lower the amount of time Light Grid spends taking up the CPU, which should help 'lag' issues.
Click to expand...
Click to collapse
I just tried your suggestion (overlooked it somehow ^^").
The LWP is indeed faster/smoother when maxed on 100fps, result? Terrible, terrible lag in the drawer. Also tried 15fps and no joy, the launcher is still suffering by it when opening the drawer (unless renice'd ofc ).
offtopic: My guess is that the lwp's are getting a little too high priority by default that actually make the launchers lag on a phone like this. Maybe even a rom setting?
I made a script but I don't know how to autorun it at boot. Unfortunately I'm very very noob
Sent from my Legend using Tapatalk
There are several possibilities:
find some app on market that does that
use GScript to run the script manually on every reboot
use run-parts approach through init.rc
run the script directly from init.rc
...there are some more.
until I figure out how to autostart the script at boot I updated the howto including GScript. thanks
I have written something about run-parts a while ago into dsixda's Kitchen thread in Chef Central subforum...
can anyone post the script?
Had not time to think about it but you can use it with GScript which is quite simple
Sent from my Legend using Tapatalk
I'd like to try this in form of SL4A script in order to use my already-running Tasker rather than gScript.
Do you guys have some hint for me to do this ?
Please read this post through thoroughly before downloading.
This app allows you to control your CPU voltages with an easy to use interface. You can increase or decrease voltages (undervolt or overvolt) for all frequencies or fine tune voltages for each individual frequency.
! HTC DEVICES, currently only single core devices are supported !
! ROOT is Required !
! Kernel that supports HAVS or SVS voltage adjustment REQUIRED !
In addition, if you are an Incredikernel user, the app may also be used to toggle Incredikernel specific features on and off, namely USB fast charging and audio boost.
Get it over at http://www.incredikernel.com
IncrediControl is now also available in the market:
IncrediControl
IncrediControl - Ad Free
Additionally, all donators are eligible to receive the Ad Free version. It doesn't matter how much or how little you donate or have donated. If you don't want to purchase the app from the market, you may donate using the button on this page. Please register on the site first and include your username in the comments box.
All previous donators, please register on the site if you have not done so and contact me with your username!
NOTE: The settings in the general tab are only functional in kernels that have implemented the simple sysfs interfaces for usb fast charging and audio boost. If you toggle them, its not going to break anything, but they won't work and the app may crash. If you would like your kernel dev to implement the interfaces, please direct them to these two commits:
https://github.com/Chad0989/android_kernel_common/commit/a7c21fa0391c225900f93960362535179c0cecc9
https://github.com/Chad0989/android_kernel_common/commit/41dc138bae23dc7582de72a4d9895aaa8e1f8b2d
NOTE2: It is a requirement of the HAVS adjustment that the kernel you are using has the HAVS sysfs interface implemented. If it does not, it will not work. Most non-stock gingerbread kernels have the HAVS adjustment. Very few sense kernels have the adjustment. I believe ziggy's latest is the only one that does.
NOTE3: Before using, please delete any boot scripts you may have in /etc/init.d that toggle any of the settings this app controls.
Get it at http://www.incredikernel.com
Restore script - use this if you went too low and find yourself in a boot loop. Flash through recovery:
http://www.incredikernel.com/?p=229
This excites me.
Neat
Sent from my Synergy Rom using Tapatalk
Great chad! Finally an app that does all the work.
Sent from my ADR6300 using XDA App
Hey Preview 2 has the HAVS, I think you should put the minus on the left of each number field. So that way it's like
- [voltage] +
mikeymop said:
Hey Preview 2 has the HAVS, I think you should put the minus on the left of each number field. So that way it's like
- [voltage] +
Click to expand...
Click to collapse
I concur. And will this work on the incredikernel?
J/k on the the question part (because I know someone will take that seriously ). Great work, chad.
Chad, here's something to ponder or consider. Please think about putting in some way to back-up your settings. That way when flashing new roms you could just restore from back rather than settings all again. Just a thought.
Great thanks!
I know viperboy was working on something similar.
I have to say though your aggressive undervolt package is the tits. It is rock solid for me, and I can't lower anything -25v from there without crashing.
RebelShadow said:
Chad, here's something to ponder or consider. Please think about putting in some way to back-up your settings. That way when flashing new roms you could just restore from back rather than settings all again. Just a thought.
Click to expand...
Click to collapse
That may come in the future.
@everyone: Anyone try it on other devices that have havs + sysfs interface? Evo, desire?
effing sweet..... no more term emulator for me
Chad, I've noticed that after I reboot the phone and go back into the app, the boxes for "set on boot" are unticked.
Also I know you already know this but it's sort of a pain in the ass to set the SD card speed (your other app) after every boot, so if you could do a "set on boot" for that one too that'd be awesome.
Keep up the good work, I like how every time I check back here you have a bunch of updates
I've noticed after installing a new nightly with no wipes, the values revert to stock, even with set on boot.
POQbum said:
Chad, I've noticed that after I reboot the phone and go back into the app, the boxes for "set on boot" are unticked.
Also I know you already know this but it's sort of a pain in the ass to set the SD card speed (your other app) after every boot, so if you could do a "set on boot" for that one too that'd be awesome.
Keep up the good work, I like how every time I check back here you have a bunch of updates
Click to expand...
Click to collapse
The boxes are unticked on purpose, so that the file is only written when you specify that you want to set the current settings on boot. The other option is to have it ticked when the boot script is found, but then you would have to untick it when you want to just play with voltages (but not change your boot script) and then tick it again to set on boot. Would everyone prefer it that way?
I should also specify that when you tick set on boot, you also must click set in order to truly set it on boot. There is also the option to have it write the file when set on boot is ticked. I just need to know what everyone's preference is.
SDspeed might be added to a future release and would have the set on boot option.
PonsAsinorem said:
I've noticed after installing a new nightly with no wipes, the values revert to stock, even with set on boot.
Click to expand...
Click to collapse
That's because new nightlies overwrite the /system folder where the boot script is stored. I'll probably add a backup option too so you can load the defaults, either that or change over to storing the values in a database and loading them via the app on boot as opposed to the boot script.
Looks cool.
Backup database - yes!
Default set on boot once it's been ticked - yes!
Thanks for this, Chad!
Zeam & Incredikernel
CM7 latest Nightly
7/19/2011 - Preview 3:
Changes include:
Added +/- All Min and All Max buttons
Reordered the + and – buttons to flank the voltages to clean up the layout a bit.
Removed the title bar for more vertical screen space
Next up is feature checking / disabling of functions your kernel doesn’t support as well as voltage checking.
Get it at http://www.incredikernel.com
Here's an icon I made in photoshop for the time being, so there won't have to be that plain android icon.
Download it here: http://dl.dropbox.com/u/12361010/volts.png
nagasgura said:
Here's an icon I made in photoshop for the time being, so there won't have to be that plain android icon.
Download it here: http://dl.dropbox.com/u/12361010/volts.png
Click to expand...
Click to collapse
Thanks, I'll add it for the next release.
The + on the Max voltage doesn't display for me.
Love it, fast and simple volt changing.. Makes viperMOD ancient news.
Hi,
I am trying to put a code together to control the refresh behavior of the e-ink screen. The final goal is to have a drop-in library for app developers to help making their app more e-ink friendly.
The code works already for the PRS-T1, but needs a different driver for the Nook Touch (N2EpdController included).
My one and only beta tester gets the famous "There is a problem parsing the package" error. Pls find enclosed the sources.
I would be grateful if someone could fix possible Eclipse setting or other errors.
Hi,
I have some interest in adapting apps to the eink screen, so I will try to help with this. Unfortunately, I cannot post in the dev forums yet.
When you get error installing apps via android UI, it is useful to do via "adb install" to be able to know the error cause. The message was "INSTALL_FAILED_OLDER_SDK", which I solved by lowering the android:minSdkVersion parameter in Manifest. Then, the app installed and ran fine, but didn't do the desired effect yet. I will check the code now...
---------- Post added at 02:41 AM ---------- Previous post was at 01:53 AM ----------
I see that you're trying to use enterA2Mode() for the nook (btw, there is a typo at NoRefreshEnablerActivity.java:29, it should read EINK_NOOK). I've been playing around with this some time ago when I started developing a fast e-ink drawing app for the NST, you can see it here: https://github.com/marspeople/E-Paper (WIP).
With few testing I've done, I guess the 1-bit mode (A2) setting is not applied globally: it should take effect only in the View from which it is called. I haven't investigated further to try to use it globally.
Hi marspeople,
Thanks for pointing out the type, it should read
} else if (DeviceInfo.EINK_NOOK)
Regarding the global value of mode setting. From what I understand, A2 is a permanent mode, so whatever function or app is setting the updatemode, it is kept. With the PRS-T1, it is reset by calling any stock (Sony) app. For the Nook I don't know..
Good luck in compiling, hopefully we come to a version which works on both devices. Then I can proceed to dynamically change the updatemode within an app.
Yes, the A2 mode is kept until any process resets the EPD. Using logcat, I noticed several epd_reset_region messages appearing automatically when I close your app to go back to the launcher. It seems the system overrides the EPD setting, making impossible to use A2 system-wide (at least by this method).
However, if you want A2 just for an app, calling enterA2mode() will probably work, as I used in my own app above.
Can you send me your apk?
salsichad2 said:
Can you send me your apk?
Click to expand...
Click to collapse
You mean the apk for "NoRefresh" or my drawing app?
Hi marspeople,
I would be most interested to know why the initial source code does compile ok, works on the PRS-T1 and does not install on the Nook Touch + the fixes.
With this knowledge I can write either an app to set refresh modes or within apps.
Did you succeed to compile and install on Nook?
Hi again,
in your N2EpdController.java
Code:
83: mtSetRegion.invoke(null, "aarddict", enumsRegion[region], regionParams, enumsMode[mode]);
I would like to replace the hardcoded "aarddict" by something dynamic.
What would be the correct function to infer the wanted name?
Code:
activity.class.getName()
this.getClass().toString()
.. ?
bardo8430 said:
Hi marspeople,
I would be most interested to know why the initial source code does compile ok, works on the PRS-T1 and does not install on the Nook Touch + the fixes.
With this knowledge I can write either an app to set refresh modes or within apps.
Did you succeed to compile and install on Nook?
Click to expand...
Click to collapse
Yes, sorry about the confusion, but I managed to do it, despite the A2 mode didn't work. What I did was just edit the AndroidManifest.xml, changing the android:minSdkVersion parameter to 7 (since the NST runs Android 2.1).
Good luck finding out how to set A2 mode permanently. I guess you don't have a Nook, so feel free to ask me for testing purposes.
Since the Nook A2 mode seems to be overridden when switching foreground activity, I've tried another approach with a background service which toggles A2 mode when requested by user. This way, the foreground activity isn't switched and "fast refreshing" mode works (until you change activity).
This fast refresh mode (called A2) is only possible because it uses only 1-bit depth, i.e, just black on white, meaning you can't see grayscale pictures but it's good enough for black text on white background and scrolling. I have not "created it", it is built-in from the device (you can test using the stock reader, it is activated when holding a page button). What I implemented is a way to activate and deactivate it at user will from inside any app.
Thanks to dairyknight for his N2EpdController class, which made this possible.
Thanks to bardo8430 for bringing the idea.
Thanks to AndroSS source code for screenshots used in automatic contrast.
Changelog:
01/Mar: Now when you launch the app and it is already running, it will activate NoRefresh mode. So you can also use an activation shortcut to the app using NookTouchTools (i.e. B&N's book icon at top left corner).
02/Mar: Improve activation shortcut to perform toggle between modes. Tap gestures aren't needed anymore (use "-noGestures" apk version if you don't want them).
04/Mar: Got rid of initial ghosting by redrawing the screen after activating A2.
04/Mar (2): Minor improvement of removing ghosting at screen edges.
12/Mar (Beta): Now you can adjust contrast in A2 mode. Images shouldn't be dark or black anymore if you raise the contrast a bit.
22/May: Completely redesigned version 2.0:
- Several options can be customized via settings screen.
- NoRefresh can be toggled by manual app shortcut, tap gestures or automatically according to screen animation (new).
- New App Whitelist to avoid unwanted activation in specific apps (except for manual mode).
- Background service can be launched at boot.
- Small improvements and tweaks.
- Custom app icon (finally )
06/Jun: Fix crash on empty whitelist
08/Jul: (Version 2.1)
- Automatic contrast when activating NoRefresh, according to total "brightness" of the screen (simple algorithm). This should ask you for root permission.
- Also supports manual setting in specific situations (customizable).
- Fix possible crash at startup.
26/Jul: (Version 2.2)
- Fix contrast setting behaviour
06/Dec:
- Alternative version with fixed compatibility for FW 1.2.0 available at https://github.com/marspeople/NoRefreshToggle/downloads
First Video: http://youtu.be/6pBPsyno5PY
Other Video: http://youtu.be/kBbl6egyPsQ
Another demo: http://youtu.be/5b7JjllImjM
Repository: https://github.com/marspeople/NoRefreshToggle
Great to see that it works on the Nook! Good job.
When I try to compile on Eclipse, I have to remove the below Override:
//@Override
public boolean onTouch(View v, MotionEvent event) {
otherwise I get an error: The method onTouch(View, MotionEvent) of type A2Service must override a superclass method
When I compile with this mod and run the app, nothing happens after using your gestures. Except that I tap on other icons which then try to launch other apps.
Should NoRefreshToggle keep the focus?
I have a suspicion: The PRS-T1 needs to call a function of the Sony library with extended parameters to pass the updatemode. ANY function carrying the mUpdateMode parameter would do - but it must be called. Which might be the problem here. In the used EinkListView.java, a lot of "injection" functions like below are defined.
Code:
@Override
public void scrollTo(int x, int y) {
try {
Method invalidateMethod = super.getClass().getMethod("scrollTo",
int.class, int.class, int.class);
invalidateMethod.invoke(this, x, y , mUpdateMode);
} catch(Exception e) {
e.printStackTrace();
}
But your code has neither a Listview, nor would any injection function trigger. I am afraid you would have to make the app use a ListView (or WebView).
Can you?
bardo8430 said:
Great to see that it works on the Nook! Good job.
When I try to compile on Eclipse, I have to remove the below Override:
//@Override
public boolean onTouch(View v, MotionEvent event) {
otherwise I get an error: The method onTouch(View, MotionEvent) of type A2Service must override a superclass method
When I compile with this mod and run the app, nothing happens after using your gestures. Except that I tap on other icons which then try to launch other apps.
Should NoRefreshToggle keep the focus?
Click to expand...
Click to collapse
Well, I noticed that problem of accidentally tapping unwanted widgets, I would recommend tapping on a free area of the screen. I could use an overlay button, but it would occasionally get in the way too. What do you mean by "keep the focus"?
---------- Post added at 09:13 PM ---------- Previous post was at 09:05 PM ----------
bardo8430 said:
I have a suspicion: The PRS-T1 needs to call a function of the Sony library with extended parameters to pass the updatemode. ANY function carrying the mUpdateMode parameter would do - but it must be called. Which might be the problem here. In the used EinkListView.java, a lot of "injection" functions like below are defined.
Code:
@Override
public void scrollTo(int x, int y) {
try {
Method invalidateMethod = super.getClass().getMethod("scrollTo",
int.class, int.class, int.class);
invalidateMethod.invoke(this, x, y , mUpdateMode);
} catch(Exception e) {
e.printStackTrace();
}
But your code has neither a Listview, nor would any injection function trigger. I am afraid you would have to make the app use a ListView (or WebView).
Can you?
Click to expand...
Click to collapse
Well, to capture touch events I've used a dummy View which is added to an overlay (see A2Service.java:43). Despite being an android Service instead of Activity, maybe you can instantiate your ListView there and hopefully it will work.
Thanks for the hint on the dummy view, will try.
"keep the focus"?: window manager speak, I mean that a tap stays within your app and does not act on the icons below.
bardo8430 said:
Thanks for the hint on the dummy view, will try.
"keep the focus"?: window manager speak, I mean that a tap stays within your app and does not act on the icons below.
Click to expand...
Click to collapse
Since I'm using a transparent overlay, I have to let touch events pass through, otherwise only my app would see them.
PS: I've added a demo video at a previous post.
I've been trying to improve the functionality of the app by changing from this manual toggle approach to something like: fast mode is triggered (a bit after) when user starts dragging his finger on the screen and restored when released.
However, I've been searching how to do this with no success so far. The invisible overlay that detects touch events currently is only able to capture MotionEvent.ACTION_OUTSIDE event type, which is useful to detect a tap, but can't deal with a drag. I also need that the drag is passed normally to the app below (to perform scrolling or whatever).
I've found this page (http://stackoverflow.com/questions/8073803/android-multi-touch-and-type-system-overlay) in which is proposed a solution that can detect a drag but can't pass it to the app below.
The code is now here: https://github.com/marspeople/NoRefreshToggle . I would appreciate any help from developers.
Maybe it can be run every 1 second when screen is on. I mean nook is not locked. I don't think that changing one parameter would eat battery. Is it worth a try?
Hi marspeople,
thanks again for taking this. My initial intention was to help app developers with no e-ink experience to easily adapt their code. Doing these things inside an app is much easier but needs access to the source.
See the related question on stackoverflow:
http://stackoverflow.com/questions/9391710/adapt-scrolling-swiping-to-e-ink-screens
The external app was used as a mere demonstrator to have it work on the NST and PRS-T1. Good to have a repository for it now.
marspeople said:
Ok, I think I've got it.
Since the Nook A2 mode seems to be overridden when switching foreground activity, I've tried another approach with a background service which toggles A2 mode when requested by user via a touch gesture. This way, the foreground activity isn't switched and "fast refreshing" mode works (until you change activity).
The activation gestures I'm currently using (unfortunately, it seems you can't use hardware keys using this approach) are:
- 4 "downward-right" taps (each tap must be done to the right and below the previous one) to activate (A2 mode)
- 4 "upward-left" taps to deactivate (Normal mode)
Video: http://youtu.be/6pBPsyno5PY
Here is the source code and a apk. bardo8430, I believe it would be easy to port this to the PRS-T1.
Click to expand...
Click to collapse
Noob question.
So I just install the apk and run it and I have Norefresh.
dark_hawk said:
Noob question.
So I just install the apk and run it and I have Norefresh.
Click to expand...
Click to collapse
yes, just open the norefresh app, and like the youtube video tap the screen from top left to bottom right 4 point
but i think the trade off is the screen go black&white with no grayscale (at lease for me)
build.prop edits are very easy and useful, they can be applied on stock rom/kernel, i have compiled this from various sources!
For ICS, most of these will be useless
Locate build.prop
got to system/ and find build.prop
Edit with notepad++. Save and overwrite previous file, then change permissions to rw,r,r!
Change the tweaks already present and add new at the end of file!
Change android name and version
ro.build.display.id=Your ROM name
ro.build.version.release=2.3.6 (Android version number)
Decrease boot time
debug.sf.nobootanimation=1 (Disables bootanimation)
ro.config.hw_quickpoweron=true
persist.sys.shutdown.mode=hibernate
dev.bootcomplete=0
Power saving
ro.ril.power_collapse=1
pm.sleep_mode=1
wifi.supplicant_scan_interval=120 (sets wifi scanning interval, can be increased or decreased)
ro.mot.eri.losalert.delay=1000 (might break tethering)
3G Tweaks
ro.ril.hsxpa=2
ro.ril.gprsclass=10
ro.ril.hsdpa.category=10
ro.ril.hsupa.category=5
ro.ril.enable.a53=1
ro.ril.enable.3g.prefix=1
ro.ril.hep=1
ro.ril.enable.dtm=1
ro.rill.enable.a53=1
Telephony/ring Tweaks
ro.telephony.call_ring.delay=0
ring.delay=0
Proximity (Disable blackscreen issue after call)
mot.proximity.delay=0
ro.lge.proximity.delay=25
Smooth Scrolling
windowsmgr.max_events_per_sec=84(This value is experimental)
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
Disables error reports
profiler.force_disable_err_rpt=1
profiler.force_disable_ulog=1
Force home launcher into memory(use light launchers only)
ro.HOME_APP_ADJ = 1
Render UI with GPU
debug.sf.hw = 1
Disable logcat
logcat.live=disable
dalvik.vm.heapsize = 64m
Note: This value is different for different phones, the value can larger(128m) with larger RAM device, use accordingly!
Phone will not wake up from hitting volume rocker
ro.config.hwfeature_wakeupkey=0
Change LCD density
ro.sf.lcd_density=160
Allows purging of assets to free up RAM
persist.sys.purgeable_assets=1
Locate bools.xml
1. Decompile framework-res.apk
2. Go to res/values and find bools.xml
The file generally contains true and false values for various things, change true->false and false->true to see the magic!
config_sf_slowBlur
Blurred background when power menu comes up
config_automatic_brightness_available
Enable/disable automatic brightness
config_unplugTurnsOnScreen
Screen turns on after unplugging usb
config_animateScreenLights
Keep "true" for CRT OFF animation
config_disableMenuKeyInLockScreen
Disable hard key in lockscreen
lockscreen_isPortrait
Lockscreen in potrait/landscape mode(experimental)
config_batterySdCardAccessibility
Indicate whether the SD card is accessible without removing the battery.
config_carDockEnablesAccelerometer
Control whether being in the car dock should enable accelerometer based screen orientation.
config_deskDockEnablesAccelerometer
Control whether being in the desk dock should enable accelerometer based screen orientation.
skip_restoring_network_selection
If restoring network selection should be skipped The restoring is handled by modem if it is true.
Thanks for this. I have seen these tweaks before but its really nice to have an explanation.
Sent from my SGH-T989D using Tapatalk 2
cwillison94 said:
Thanks for this. I have seen these tweaks before but its really nice to have an explanation.
Click to expand...
Click to collapse
There are a lot of threads on the subject, but would Google any before using them as some work better on other devices or they don't do anything at all.
XperienceD said:
There are a lot of threads on the subject, but would Google any before using them as some work better on other devices or they don't do anything at all.
Click to expand...
Click to collapse
Yes, scrolling speed, vm heapsize, lcd density etc are different for devices!
Sent from mass relay
No point of putting CRT off animation there....
js2892 said:
Allows purging of assets to free up RAM
persist.sys.purgeable_assets=1
Click to expand...
Click to collapse
can u please explain this in details..
thanks
Sent from my GT-S5830i using xda app-developers app
srt99 said:
can u please explain this in details..
thanks
Sent from my GT-S5830i using xda app-developers app
Click to expand...
Click to collapse
allows system to free ram by klling unused assets(programs) !
I once tried to change my phones model via build prop using the same method you wrote up and my phone bootlooped.
Im on n2 sgh-i317.
I fixed it but was wondering what I could have done wrong. Im slowly inching towords getting my feet wet in learning aboutvrom making. Nice thread btw.
freakboy13 said:
I once tried to change my phones model via build prop using the same method you wrote up and my phone bootlooped.
Im on n2 sgh-i317.
I fixed it but was wondering what I could have done wrong. Im slowly inching towords getting my feet wet in learning aboutvrom making. Nice thread btw.
Click to expand...
Click to collapse
u mean the android version or the phone name...
well, irrespective of that, it's quite weird that build.prop edit lead to bootloop...I've edited these things many times and worked normally for me..
if you know how to read logcat etc, u can get a logcat try that to point out the reason for the same!
Thank you, It would be usefull for me.
Thank
Thank u for this post. I will test on my devices.
Before posting things like this, I highly recommend reading this and this just so you know what works and what does nothing (hint: a lot of the tweaks don't work)
pandaball said:
Before posting things like this, I highly recommend reading this and this just so you know what works and what does nothing (hint: a lot of the tweaks don't work)
Click to expand...
Click to collapse
Well, i've read this earlier but forgot to mention about this in OP (i'm still on a GB phone)
Thanks for pointing out, i've edited the OP.
For GB, i've tested them and they work like a charm( with exceptions for some phones).
Thanks for this!
Good Job
Okay
Thanks a lot
Hlpful to me and will be for noobs like me
Really helpful. Should have pressed thanks twice if that was possible
Thanks you
Shadman0 If I help U Pls Give Thanks
My Work http://forum.xda-developers.com/showthread.php?t=2521867
Yea great thread I also am learning android development thanks to you guys. It's cool to know how to modify my devices to my liking.
Sent from my GT-N7105 using Tapatalk
I read that some peoples have issues with the touchscreen sensitivity. I've thinked i've got the same problem until i activate some developers options Options: "Show touches" and "Pointer location". Thereafter i realized that the touchscreen is perfectly responsive, the only issue is that when i click somewhere, my finger sometimes slip a bit and the touchscreen take it as a Swipe, then i have to click another time. The TF701 have a high density PPI (300) and it seem the touchscreen is not calibrated in accordance to that density.
By example (I don't know the real values!)
on my Motorola XOOM (150 PPI), the device need at least 30 pixels movement to detect a swipe = about 2/10 inches
on my TF701 (300 PPI), the device need at least 30 pixels movement to detect a swipe. = about 1/10 inches
What do you think about it?
Is it tunable by an application?
I found TouchScreenTune on the PlayStore but have never tested it since it's not marked as TF701 compatible, and i'm not root.
I found editing the following options makes a huge difference.
In the build.prop add the following lines:
Code:
# Improve Touch Pressure
touch.pressure.scale=0.001
ro.min.fling_velocity=90000
ro.max.fling_velocity=200000
Obviously the first line is just a comment
Also you can speed up browsing by enabling debugging mode in the browser by typing the following in the address bar
Code:
about:debug
Then go to the settings and the new debug menu and enable:
enable hardware accel
enable cpu upload path
enable light touch
Click to expand...
Click to collapse
Or just unlock and flash CROMi-X for all these and loads of other tweaks built in
Is there a way to change these settings without flashing a new ROM?
dutchguy said:
Is there a way to change these settings without flashing a new ROM?
Click to expand...
Click to collapse
Well you need to be rooted but yes just follow the instructions above. The browser set won't stick on a reboot though so you'll have to keep doing it.