Related
Some people fine the startup sound completely annoying and the fact that it's tied to "media volume" means just putting the phone in silent mode doesn't fix it.
To turn it off semi-permanently:
First root your phone (you don't have to perform the Recovery Image portion of the guide, you just need to get to the root shell (#))
http://forum.xda-developers.com/showthread.php?t=581577
Once you are at the root shell, perform the following commands:
Code:
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
# mv /system/media/bootscreen/boot.mp3 /system/media/bootscreen/boot.mp3.old
If you ever want to revert, just swap the filename of the last command above:
Code:
# mv /system/media/bootscreen/boot.mp3.old /system/media/bootscreen/boot.mp3
This works on the stock ROM once rooted.
Fantastic. Thanks.
can i do the same with the Sprint.gif with out editing the XML?
Negrito said:
can i do the same with the Sprint.gif with out editing the XML?
Click to expand...
Click to collapse
I don't see why not...I think some people have! Just mv the old one to another name (in case you want it back later) and put a different one there (it may have to conform to certain lengths/size so you might have to play around with it).
Or if you just wanted to remove it, you can...people have and just have a blank screen during bootup (it doesn't speed anything up, just removes the animation during it)
thecodemonk said:
I don't see why not...I think some people have! Just mv the old one to another name (in case you want it back later) and put a different one there (it may have to conform to certain lengths/size so you might have to play around with it).
Or if you just wanted to remove it, you can...people have and just have a blank screen during bootup (it doesn't speed anything up, just removes the animation during it)
Click to expand...
Click to collapse
Oh i was hoping for a speed boost, but not seeing that horribly pixelated animation would be a good start. thanks for the info.
Why does everyone seem to think that the boot splash screen is slowing down the bootup? It isn't, that screen is something for you to look at while the background processes are initializing, this is true for most applications such as Windows and almost all games.
The sound is annoying yes, I will be nuking it.
/edit, worked great, thanks.
Hi people,
I'm the developer of an application distributed on the market called "Unlock At Home Using Wifi", I've developed this basically because I was tired of having to unlock the phone's dots security pattern in every time and place, specially when I was at secure locations, like home f.e.
The idea of the application is that whenever the phone is connected to a wifi network defined as secure, you'll have to unlock the device just ONCE, and then after disconnection, lock will be again automatically enabled. Also you can define a different wifi sleep policy depending if you are in a secure location or not.
NOTE: I'm deleting my xda-developers account (this thread will stay here I think) but isn't supported for me anymore. If you want to contact me please use the provided email at market. Thanks everyone!
UPDATES
*** version 1.5.9 *** (05/12/2011)
(RECOMMENDED BRANCH)
Free market application link
- Enforced and default activation of "(Wifi) White-Network Always On" option (sleep policy RECOMMENDED), if it's off the application might get some issues.
*** version 1.5.8 *** (04/28/2011)
- Several issues fixed in service (unlock finally holds all the time it shoulds)
- Added option to disable the screen flick on wifi off/screen off locking situations (NOT RECOMMENDED)
*** version 1.5.7 *** (04/25/2011)
- Fixing keyguard
- Better app behavior
*** version 1.5.6 *** (04/11/2011)
Now when app detects a white-list network connection, it'll show a yellow status bar icon, indicating that after unlocking, phone will switch to fixed unlocked status (red icon). Known issue: From time to time, at least in my phone (CM7) keyguard is coming back on his own, it this happens also to you, you'll have to unlock again to fix it, I'm looking for a solution to this... (I feel a bit at the limit of OS posibilities now...)
*** version 1.5.5 ***
More app behavior fix... Hope this is the last. Screen now will flick a little when disconnecting. (it'll fix keygyard state).
Remember now you just have to unlock the device once, when connected to a secure located wifi network. It's safer and fits quite well inside the OS limits.
*** version 1.4 ***
NOTE: This branch is a bit outdated now, the recommended one is the 1.5, try this for curiosity if you want, view the (outdated) source) and so if you want, but this is, I repeat it: OUTDATED.
If you don't like the idea of a totally unlocked device, try this, is only for Android 2.2 onwards, it will change from dotted lock to slide lock on secure locations, requires a rooted phone and installing the app in /system/app.
APK version 1.4 android 2.2+
Github source code repository (v.1.4)
If you don't know how to install this, better go for the 1.5 free market app.
FINAL WORDS
If you find useful this application, please consider a small donation via the donation app. Thank you very much!
Works on Galaxy S! Great app thx! how is the battery drain?
Hi DasPrinzip,
in my experience, almost inexistent, it's just hooked to wifi up/wifi down events, also has a very low memory footprint.... check for yourself
Greetings,
Ruben
Works well on Desire Z CM7 nightly #32
Tested today and no problem yet.
Thanks
fantastic idea. feel like I saw a post here or somewhere else where you were asking opinions on pricing. Did you decide yet if/what you are going to charge for this? This app would make a great partnership with something like widget locker.
ThePitboss said:
fantastic idea. feel like I saw a post here or somewhere else where you were asking opinions on pricing. Did you decide yet if/what you are going to charge for this? This app would make a great partnership with something like widget locker.
Click to expand...
Click to collapse
Thank you ThePitboss, the app is GPL3 free software, may be you saw another app that was inspired on mine, recently on the xda-news ...
You can get the github repo and compile for yourself if you want...
Thanks khroma. Just getting into android development, and it's great to read code for apps like this.
Sent from my PC36100 using XDA App
Unlocking doesn't work affter reboot
It worked successfully for a certain time yesterday, after reboot I realize that the phone get lock even when on wifi whitelist. Then when I unlock the phone, the green lock icon is still there. I have to click on "Tap for modify networks lock configuration" in notification area to unlock the phone again ( I see the red unlock icon in status bar). It works for a few minutes, then it revert back to green lock icon even when unlock.
I'm using the github apk installed with adb push.
Using CM7 nightly #32 on rooted Desire Z
Will try CM7 RC4 today with all the usual wipe dalvick cache etc...
Any Ideas?
No success after upgraded to CM7 RC4 and reinstalled apk. No significant messages in logs. UnlockAtHome icon still switching to green lock even when my sreen is on :-(
droidoz said:
No success after upgraded to CM7 RC4 and reinstalled apk. No significant messages in logs. UnlockAtHome icon still switching to green lock even when my sreen is on :-(
Click to expand...
Click to collapse
I'm sorry droidoz ... if you like the new approach, uninstall the v.1.4 of /system/app space and try the app directly from market. Please tell me what happens there.
Wont install from the Market :-(
droidoz said:
Wont install from the Market :-(
Click to expand...
Click to collapse
Did you delete it first from /system/app?
Steps:
[plug phone]
adb remount
adb shell
cd /system/app
rm UnlockAtHome.apk
exit
Khroma said:
I'm sorry droidoz ... if you like the new approach, uninstall the v.1.4 of /system/app space and try the app directly from market. Please tell me what happens there.
Click to expand...
Click to collapse
It works but reboot erase configs. I went to an internet coffee shop to test it and it last 2 hours without any problem, then I came back at home enter my shema to unlock and it works well. I tried a reboot, then it lost all configs like if it was a new app. I did the same config as the first time: settings wifi always on a you suggested. Waited a few minutes... still working. Did another reboot and lost again my all configs.
Could it be a permission problem? I did a fix permission from recovery, but didn't change anythings.
droidoz said:
Waited a few minutes... still working. Did another reboot and lost again my all configs.
Could it be a permission problem? I did a fix permission from recovery, but didn't change anythings.
Click to expand...
Click to collapse
Weird... yes it seems a permission problem, may be your phone still contains the old /system/app aplication data (?), look in /data/data directory using adb shell, the app id is com.accedo.unlockathome, compare user/permissions of the directory, or if you want to make to make sure the directory is created again (sample commands, take care with this):
[uninstall unlock at home once again, plug your phone]
adb shell
cd /data/data
ls -ld com.accedo.unlockathome
[if you see some dir here delete it with this command:]
rm -rf com.accedo.unlockathome
Install the app again, you'll need to configure your data again but I hope this time you get no issues
Installed from Market for me! Nice app - will try it out over next few days.
Great that your offering is Free / GPL unlike the other one
I am running Pongsters HyperDroidGBX-v11 on an HTC HD2
Cheers
UPDATE
Uninstalled - used 70% battery overnight - normal usage is 3%. I normally turn everything off using a power widget - no WiFi, etc - phone in airplane mode. Despite this left with 9% battery when I woke up - was at 79% 8 hours before going to kip!
Khroma said:
[uninstall unlock at home once again, plug your phone]
adb shell
cd /data/data
ls -ld com.accedo.unlockathome
[if you see some dir here delete it with this command:]
rm -rf com.accedo.unlockathome
Install the app again, you'll need to configure your data again but I hope this time you get no issues
Click to expand...
Click to collapse
ls: com.accedo.unlockathome: No such file or directory.
But there was a file in dalvik-cache which I deleted. Removed copmpletly the app and did a reinstall and it reverted back to the same problem. It works for a few minutes and then locks again. It solved configs problem at reboot, but still no improvement.
droidoz said:
ls: com.accedo.unlockathome: No such file or directory.
But there was a file in dalvik-cache which I deleted. Removed copmpletly the app and did a reinstall and it reverted back to the same problem. It works for a few minutes and then locks again. It solved configs problem at reboot, but still no improvement.
Click to expand...
Click to collapse
Soooo weird... now my only guess is CM7 RC4, I'll try to test this ASAP, when the ROM is available for my phone, sorry for the inconveniences. Please see also my PM.
jellywobbles said:
Great that your offering is Free / GPL unlike the other one
[..]
UPDATE
Uninstalled - used 70% battery overnight - normal usage is 3%. I normally turn everything off using a power widget - no WiFi, etc - phone in airplane mode. Despite this left with 9% battery when I woke up - was at 79% 8 hours before going to kip!
Click to expand...
Click to collapse
Thank you anyway for your confidence and your feedback!
The app it self it's a service that runs only on wifi app - down events, should not drain at all, but I'll check this today
Regards
Khroma said:
Thank you anyway for your confidence and your feedback!
The app it self it's a service that runs only on wifi app - down events, should not drain at all, but I'll check this today
Regards
Click to expand...
Click to collapse
Thanks - if the battery drain can be solved, this will be a brilliant product!
jellywobbles said:
Thanks - if the battery drain can be solved, this will be a brilliant product!
Click to expand...
Click to collapse
Please could help me with this issue checking what process are draining the battery, I've tested it for a few hours and here everything is running ok, just a guess: Did you checked the "white network always on" checkbox? Maybe the problem is some process over-using wifi?
Anyway I'm interested (if you can do some more testing) about what process are draining your battery, you can check it in "About the phone > Battery use"
(I've never seen my process in that list in my phone)
Two things:
Firstly, when I type in the browser the screen moves up on every key press...weird.
Secondly, the top of the screen (in expanded desktop mode, with full screen lab running) gets corrupted - legacy downloading blue lines and tabs - which should disappear. Weird.
Any ideas from the brains trust out there? It's been happening sporadically for a couple of weeks - I'm on CM10.1 Nightlies - been the same with various versions of CM10.1.
dgjl said:
can anybody explain and /or solve the following two things:
Firstly, when I type the screen moves up on every key press...weird and annoying.
Secondly, the top of the screen (in expanded desktop mode, with full screen lab running) gets corrupted - legacy page downloading blue lines and tabs - which should disappear remain in the top part of the screen.
Any ideas from the brains trust out there? It's been happening sporadically for several weeks - I'm on CM10.1 Nightlies - been the same with various versions of CM10.1.
Click to expand...
Click to collapse
Bump - any ideas? Has this really never been seen before (did a clean install yesrerday and it still happpens).
Over 100 views and no ideas? Someone must know something. Surely it's not a unique set of problems .
It's definitey an issue with the 'labs' setting - turn that off and it goes away. Any reason why this should happen? can anyone replicate this?
dgjl said:
It's definitey an issue with the 'labs' setting - turn that off and it goes away. Any reason why this should happen? can anyone replicate this?
Click to expand...
Click to collapse
Hi dgjl-
I'm replying to this post with your same settings and having none of the same problems. No scrolling when I typing, no ghosted tabs or lines above? I do have some wierdness with the cursor positioning though and positioning the cursor with the arrow keys does not work in desktop mode but does in mobile mode (user agent). Also the page seems to have a white hue like its been whitewashed.
Labs, Developer Settings, and Experimental all mean about the same thing. It means its a new feature that hasn't been fully tested so use it at your own risk. I tend to avoid these settings unless you want to be a beta test site for Asus. You may then have to disable other settings that previously worked fine to run your new setting as they may conflict. You may have to "experiment" to find the combination of settings that work together.
If you type "about:debug" into the address line, then go back into settings there is a new menu item "debug" and in there are a slew of new settings to check out. Enabling "enable cpu upload path" speeds things up, and there is also controls for OpenGL and WebGL that you might experiment with. Also try disabling "fast scroller" under the advanced settings as it may conflict with the labs flyouts. I am also running my Multi browser2RAM startup script which is the same as browser2RAM.
elfaure said:
Hi dgjl-
I'm replying to this post with your same settings and having none of the same problems. No scrolling when I typing, no ghosted tabs or lines above? I do have some wierdness with the cursor positioning though and positioning the cursor with the arrow keys does not work in desktop mode but does in mobile mode (user agent). Also the page seems to have a white hue like its been whitewashed.
Labs, Developer Settings, and Experimental all mean about the same thing. It means its a new feature that hasn't been fully tested so use it at your own risk. I tend to avoid these settings unless you want to be a beta test site for Asus. You may then have to disable other settings that previously worked fine to run your new setting as they may conflict. You may have to "experiment" to find the combination of settings that work together.
If you type "about:debug" into the address line, then go back into settings there is a new menu item "debug" and in there are a slew of new settings to check out. Enabling "enable cpu upload path" speeds things up, and there is also controls for OpenGL and WebGL that you might experiment with. Also try disabling "fast scroller" under the advanced settings as it may conflict with the labs flyouts. I am also running my Multi browser2RAM startup script which is the same as browser2RAM.
Click to expand...
Click to collapse
Thanks. I've been through the various debug settings already - what's strange is that when debug is operating (i.e., in the same browsing session as 'about:debug' is launched) the problems don't seem to occur. Is there anyway to make debug permanent - as it is on Cromi, for example?
dgjl said:
Thanks. I've been through the various debug settings already - what's strange is that when debug is operating (i.e., in the same browsing session as 'about:debug' is launched) the problems don't seem to occur. Is there anyway to make debug permanent - as it is on Cromi, for example?
Click to expand...
Click to collapse
This is the first I'm hearing about the "about:debug" settings you change not being "permanent". I don't follow you. When I change a debug menu setting in a browser session, then launch a new tab and url "about:debug" in that session, all the settings I changed in the previous session are applied to all new tabs I create. Same is true if I shut it down and relaunch the browser. The settings persist. Yours don't?
Are you running the old browser2RAM that loads the actual browser app as well as its cache into RAM ["mount | grep tmpfs" to check all mounts from the terminal] so the session data doesn't persist? If so, use my startup script 3 in my signature instead - data persists. Its a more versatile replacement for browser2RAM that works on 4.2 as well. For 4.1 and below you can run it from the terminal as su after boot. For 4.2 you need to run it as su *at boot* using either an init.d method or the Script Manager (Devwom) app.
I'm kinda liking this lab flyout! Makes for quick navigation. But this cursor thing is starting to P me O. I use Chrome instead.
@sbdags do you have any suggestions?
elfaure said:
This is the first I'm hearing about the "about:debug" settings you change not being "permanent". I don't follow you. When I change a debug menu setting in a browser session, then launch a new tab and url "about:debug" in that session, all the settings I changed in the previous session are applied to all new tabs I create. Same is true if I shut it down and relaunch the browser. The settings persist. Yours don't?
Are you running the old browser2RAM that loads the actual browser app as well as its cache into RAM ["mount | grep tmpfs" to check all mounts from the terminal] so the session data doesn't persist? If so, use my startup script 3 in my signature instead - data persists. Its a more versatile replacement for browser2RAM that works on 4.2 as well. For 4.1 and below you can run it from the terminal as su after boot. For 4.2 you need to run it as su *at boot* using either an init.d method or the Script Manager (Devwom) app.
I'm kinda liking this lab flyout! Makes for quick navigation. But this cursor thing is starting to P me O. I use Chrome instead.
@sbdags do you have any suggestions?
Click to expand...
Click to collapse
Actually I'm running your script for b2r… As for 'permanent' I just meant the menu for debug being always available, not the settings. When it's there as an option the typing doesn't move the screen up - though screen corruption still happens as described.
Using Dolphin currently as I'm a full screen addict and Chrome doesn't offer that - or flash.
dgjl said:
Actually I'm running your script for b2r… As for 'permanent' I just meant the menu for debug being always available, not the settings. When it's there as an option the typing doesn't move the screen up - though screen corruption still happens as described.
Using Dolphin currently as I'm a full screen addict and Chrome doesn't offer that - or flash.
Click to expand...
Click to collapse
Ah, gotcha. About:debug>enable cpu load path fixed some of the corruption I was having with my cursor. Its not just for speed. Developer Options>Force GPU rendering fixes random reboots and other things if you haven't tried that. Make sure you have my script version 3 for Dolphin support. That's about all I've got for you @dgjl.
elfaure said:
Ah, gotcha. About:debug>enable cpu load path fixed some of the corruption I was having with my cursor. Its not just for speed. Developer Options>Force GPU rendering fixes random reboots and other things if you haven't tried that. Make sure you have my script version 3 for Dolphin support. That's about all I've got for you @dgjl.
Click to expand...
Click to collapse
Thanks for taking an interest, Elfaure. Looking around the 'web' I don't think I'm the only one with ths issue, but there's no one out there with the solution yet. It's just strange that it started without an obvious cause...
SORTED:
I found this thread http://code.google.com/p/android/issues/detail?id=39811
I had downloaded a notifiation app which ran under Settings>Accessibility. The moment I disabled it the probem went away!
Marvellous!
dgjl said:
Thanks for taking an interest, Elfaure. Looking around the 'web' I don't think I'm the only one with ths issue, but there's no one out there with the solution yet. It's just strange that it started without an obvious cause...
Click to expand...
Click to collapse
You might want to unload my script and see if the problem persists. If it does then ? If not, then maybe some switches could be added to your mount line (nodev, nosuid, gid=...etc.)
elfaure said:
You might want to unload my script and see if the problem persists. If it does then ? If not, then maybe some switches could be added to your mount line (nodev, nosuid, gid=...etc.)
Click to expand...
Click to collapse
The solution is in my previous post - anything running in Settings>Accessibility with conflict with the stock browser/lab and cause this to happen. trouble is now I don't know what to do for a notification widget as they all use 'accessibility' and I don't want the notification bar to be visible. Good old Android - there's always something!
dgjl said:
The solution is in my previous post - anything running in Settings>Accessibility with conflict with the stock browser/lab and cause this to happen. trouble is now I don't know what to do for a notification widget as they all use 'accessibility' and I don't want the notification bar to be visible. Good old Android - there's always something!
Click to expand...
Click to collapse
So its either accessibility notifications and a different browser or labs flyouts with the stock brower - your choice. Good you got the bottom of it. That's always the first step in fixing a problem. Looks like you can't have your cake and eat it too on this firmware.
OK guys I hope this hasn't already been covered but here goes anyway. I have found this fix for notifications not arriving when doze is enabled. Iff you go into the particular app e.g what's app then into data usage you must select the following settings see pic below. then all the notifications will arrive straight away regardless of doze state.
sam00561 said:
OK guys I hope this hasn't already been covered but here goes anyway. I have found this fix for notifications not arriving when doze is enabled. Iff you go into the particular app e.g what's app then into data usage you must select the following settings see pic below. then all the notifications will arrive straight away regardless of doze state.
Click to expand...
Click to collapse
Yes that seems to be the problem. I had made a post months ago. It's very hidden feature by Lenovo and I think it's wrong to pre-restrict all background data. User should decide what to do.
I think they lenovo did it to block unnecessary data usage but i agree it is not needed and people are thinking their is something wrong with their phones.
Thanks for the tip
Thanks Sam, I saw this on the JJ review of Nougat. Is this for Nougat as my MM P2 settings don't look like the screenshot.
Sent from my Lenovo P2a42 using Tapatalk
Hi yes it is for Nougat the comment posted on JJs review regarding this fix was posted by me also.
Confusing settings these as the first one makes it look like enabling the "Restrict background data" option will disable background data, when in fact it does the opposite. You need to have both of these options enabled so the sliders are green, then you need to open Settings > Power Manager > Battery Optimization
Then you need to search for the apps that you need to fix notifications and change the option so it says "Don't optimize". Then the phone won't 'helpfully' close the app when the phone has been unused for a long time. This is why notifications are stopping.
precisely i agree quite confusing it took me a while i had to get a friend to send me whats app messages continuously untill i figured all this out but im glad i finally did.
If you make the changes to fix the notifications, shut down and power the phone back on rather than do a reboot. The settings don't seem to work until the phone has properly rebooted.
Is it worth noting that elsewhere it's stated that turning off doze altogether (using ADB) might be a saner option? Consensus seems to indicate it's basically a curse with little value, and that would certainly hold water in light of the battery capacity of the P2.
https://forum.xda-developers.com/lenovo-p2/help/regretting-purchase-t3611968
I think the following helps. Credit goes to JasonMR and manototh (Taken from oneplus.net forum)
JasonMR
KitKat
JasonMR, Nov 2, 2016 :
Guys, to avoid having to run the ADB command after each reboot follow these instructions (please note, the files should be downloaded to a PC and then transferred to your phone via USB otherwise they mess up sometimes):
You need to enable USB debugging mode in Developer options first
Download and install this apk and transfer it to your phones storage - https://drive.google.com/file/d/0BxD...w?usp=drivesdk
Then connect phone to PC and allow the drivers to install
Download and install ADB here - https://drive.google.com/file/d/0B0M...ljU2NPR0k/view
Go into the ADB folder, hold shift, right click and select "Open command prompt here"
Type the command: adb devices (now hit enter)
It should return your phones serial number is connected correctly
Run this command in ADB: adb -d shell pm grant com.adamioan.scriptrunner android.permission.DUMP (now hit enter)
Download this file and transfer it to your phones storage - https://drive.google.com/open?id=0Bx...VA4YmxGTS1OX3c
Open the SH Script runner app and tap the three dots in the top right corner, select "Load" and locate the file from teh previous step
Click the Circle button with the play sign at the top of the screen
You should see the message "Idle mode disabled" which means that Doze has now been disabled.
Whenever you reboot your phone, open the SH Script runner and the command will still be there, just click the play button to run the script again.
And that is it, two clicks to disable Doze after each reboot.
Full credit to manototh for putting this together originally.
Doze does not need disabling iff you follow my advice in the initial post i have tried and tested this and can confirm it works fully.
This is really frustrating. No matter what settings I use I still don't get notifications after a while. I don't want to go modifying my phone, can someone post a step by step if they have it working properly?
Spacedog79 said:
This is really frustrating. No matter what settings I use I still don't get notifications after a while. I don't want to go modifying my phone, can someone post a step by step if they have it working properly?
Click to expand...
Click to collapse
Follow my ordinal post and also go into battery optimisation and disable optimization for things like sms eggs what's app Facebook etc all the things you need notifications for should be disabled from sleep mode under battery optimization.
Like this
sam00561 said:
Like this
Click to expand...
Click to collapse
Yes thats exactly how I've done it. I've also tried every combination of settings under Apps for Unrestricted data usage.
And also the setting here
sam00561 said:
And also the setting here
Click to expand...
Click to collapse
Yep doesn't work either.
Perhaps your only option left is to try the disable doze app which has worked for many people but it's a paid app.
Just to update it does seem to be working properly now. I'm not 100% sure but I think turning the phone all the way off and on again instead of rebooting with the settings correct had the desired effect.
I always found stock pixel color saturation to be a bit washed out. I prefer the look of more saturated color palette. Even choosing "adaptive" color on display options is still not good enough for me.
If you're rooted and want to increase color saturation do the following:
Open any Android terminal with root capabilities, I personally use Termux.
Type "su" and hit enter to grant root privileges. I don't know if it's a necessary step, but I change the directory to the root of the phone by typing "CD /". Then I copy and paste the below code into the terminal. I personally set my "x.x" to 1.25. hit enter and it will automatically take effect. You can change the values at anytime afterwards to go higher or lower. Values will go back to stock after a reboot using this method, so if you don't like it, just reboot to go back to stock values.
"service call SurfaceFlinger 1022 f X.X" (x.x sets saturation up to 2.0)
I HAVE NOT TESTED THIS, but in the past I have used this code to permanently set the saturation level on boot:
Setprop persist.sys.sf.color_saturation X.X
using this, the saturation level will remain to the chosen value on boot. Again, I have not tested this on the pixel 7 Pro.
That's interesting as I also find the "adaptive" setting too washed out on Pixels.
I wonder if this could be used through a root app with more control over colors and such?
works - thank you!
Ghisy said:
That's interesting as I also find the "adaptive" setting too washed out on Pixels.
I wonder if this could be used through a root app with more control over colors and such?
Click to expand...
Click to collapse
I'm sure it could but that's beyond my capabilities lol l
Gotta wonder what effect this might have on...everything? Battery life...screen life...brightness level adjustments when on auto? YMMV
But what can we use after
"service call SurfaceFlinger 1022 f X.X" to disable if needed ?
Attinderkahlon said:
But what can we use after
"service call SurfaceFlinger 1022 f X.X" to disable if needed ?
Click to expand...
Click to collapse
I believe 1.0 is the stock value. So you can either enter the line again and replace whatever previous value you used with 1.0, or you could just reboot the device and it'll go back to the stock saturation settings.
jaseman said:
Gotta wonder what effect this might have on...everything? Battery life...screen life...brightness level adjustments when on auto? YMMV
Click to expand...
Click to collapse
It could have a negative effect on battery life....but I would guess its minimal. Been using a custom saturation value for 2 days now, no known issues.
I haven't checked yet but going by previous devices, there is probably a way to access other color modes using tasker. "boosted" has been taken away from the menu, my guess is its still there and can be accessed with tasker. I'll check it if i keep the phone.
Thank you for this, legit the only thing driving me crazy was the dull colors now it looks more like I wanted. You da man.
Glad I could help!
Dope. Going to give this a shot whenever I decide to root.
Now, has this always been a thing? If so, I wish I knew about it so I didn't have to use apps the entire time to tweak it to my liking.
Curiousn00b said:
Dope. Going to give this a shot whenever I decide to root.
Now, has this always been a thing? If so, I wish I knew about it so I didn't have to use apps the entire time to tweak it to my liking.
Click to expand...
Click to collapse
I've been using this mod since the OnePlus 6T....so it's been a thing for a while at least for me.
Has anyone tried this? Getting a Parcel Null error when I enter the code. Rooted. That "CD /" comes back as inaccessible too. It's probably me, but not able to get this to work as of now.
Unable to set up after boot, i get the setprop inaccessible
System is read-only for now. There's no rw mount mod so can't really edit build prop to set it on boot. We'll just have to wait for twrp or any system rw mount mod
xgerryx said:
Has anyone tried this? Getting a Parcel Null error when I enter the code. Rooted. That "CD /" comes back as inaccessible too. It's probably me, but not able to get this to work as of now.
Click to expand...
Click to collapse
I get parcell null response as well but it still works.
Also, I just tested changing directory in not necessary so you can skip the "CD /" part.
Trust me on this, run the script with a value of 0.5 and hit enter. Go to your home screen, open apps and scroll through your phone. Then open your emulator again, run the script with a value of 3.0 and hit enter. Then look about your phone it will look completely different. From there, just keep messing around with different values until you get one you like.
Pain-N-Panic said:
I get parcell null response as well but it still works.
Also, I just tested changing directory in not necessary so you can skip the "CD /" part.
Trust me on this, run the script with a value of 0.5 and hit enter. Go to your home screen, open apps and scroll through your phone. Then open your emulator again, run the script with a value of 3.0 and hit enter. Then look about your phone it will look completely different. From there, just keep messing around with different values until you get one you like.
Click to expand...
Click to collapse
Ok yes I'm seeing it now. Thanks for following up. It does change exactly what we're looking for. I bet you someone can make this into a little app or a magisk module.
xgerryx said:
Ok yes I'm seeing it now. Thanks for following up. It does change exactly what we're looking for. I bet you someone can make this into a little app or a magisk module.
Click to expand...
Click to collapse
Glad ya got it working! Yeah I'm sure it's possible, having to run the script everytime you boot is kind of annoying
I wish we could adjust the white balance. This screen is so yellow looking