Database Info

Anyway to remove the stock 'startup' sound and images?

When you are starting up the Droid Charge, it does it's animated thing and makes the 'droid sound'.. this is very annoying when you are in a quiet place and need to reboot your phone... anyway to disable this startup noises?
also, when the phone is charging and hits 100% charge, there is a notification sound... this often goes off in the middle of the night while sleeping and I have keep the phone plugged in overnight... so this 100% charge notification often wakes me up.. anyway to disable this sound?
thanks all!
P.S. - I read through the above posts in this forum, I could not find these issues talked about..

aliensquale said:
When you are starting up the Droid Charge, it does it's animated thing and makes the 'droid sound'.. this is very annoying when you are in a quiet place and need to reboot your phone... anyway to disable this startup noises?
also, when the phone is charging and hits 100% charge, there is a notification sound... this often goes off in the middle of the night while sleeping and I have keep the phone plugged in overnight... so this 100% charge notification often wakes me up.. anyway to disable this sound?
thanks all!
P.S. - I read through the above posts in this forum, I could not find these issues talked about..
Click to expand...
Click to collapse
Android Development is not for Questions or Problems
Please Post in the Correct Forums

sorry I thought you could post questions for developers here...
are you able to move this to the general forum for me so I don't create yet another new post there then get flamed for creating duplicate posts in two forums..

Also the phone fully charged chime that wakes me up at night.

aliensquale said:
When you are starting up the Droid Charge, it does it's animated thing and makes the 'droid sound'.. this is very annoying when you are in a quiet place and need to reboot your phone... anyway to disable this startup noises?
also, when the phone is charging and hits 100% charge, there is a notification sound... this often goes off in the middle of the night while sleeping and I have keep the phone plugged in overnight... so this 100% charge notification often wakes me up.. anyway to disable this sound?
thanks all!
P.S. - I read through the above posts in this forum, I could not find these issues talked about..
Click to expand...
Click to collapse
If your phone is on silent, the animation will still play, but without sound. If you don't want to put your phone into silent to reboot, the other option is to remove the files /system/etc/PowerOn.wav and /system/etc/PowerOn.snd (although I think only the .wav plays)
khanfuze said:
Also the phone fully charged chime that wakes me up at night.
Click to expand...
Click to collapse
This can be fixed then so you don't get the sound or popup notification

how do you fix the fully charged sound?

my phone will NOT let me edit, delete or rename those sound files... so how do you just delete them like you say?

aliensquale said:
my phone will NOT let me edit, delete or rename those sound files... so how do you just delete them like you say?
Click to expand...
Click to collapse
you need r/w access...if you are using a root file explorer on your phone, select that option....in adb just mount as r/w

aliensquale said:
how do you fix the fully charged sound?
Click to expand...
Click to collapse
You have to edit a few of the framework files. I know it can be done because the Fascinate has the same thing. We just need to find the appropriate edit(s) and implement them.

I just have the file explore that came preinstalled on the phone.. what other software would I need to gain this access?
nitsuj17 said:
you need r/w access...if you are using a root file explorer on your phone, select that option....in adb just mount as r/w
Click to expand...
Click to collapse

aliensquale said:
I just have the file explore that came preinstalled on the phone.. what other software would I need to gain this access?
Click to expand...
Click to collapse
Here is how you would do it via adb:
Code:
adb shell mount -o remount,rw /dev/block/stl10 /system
adb shell rm /system/etc/PowerOn.wav
adb shell rm /system/etc/PowerOn.snd
adb reboot

aliensquale said:
I just have the file explore that came preinstalled on the phone.. what other software would I need to gain this access?
Click to expand...
Click to collapse
if you dont want to use a terminal...then root explorer (like $5 in market) is an invaluable tool for root users...that and titanium backup are must buys imo
but i think there are other free su ones too, just dont know them off hand

how do you use the adb terminal?
and for titanium backup.. what does that allow you to backup/restore?

aliensquale said:
how do you use the adb terminal?
and for titanium backup.. what does that allow you to backup/restore?
Click to expand...
Click to collapse
you need to install the android sdk on your computer....vital for all root users anyway
tibu allows you to back up your apps with app data...also vital for rom flashers

okay is there a step by step walkthrough available online about using all this sdk, where to download from, etc.?

aliensquale said:
okay is there a step by step walkthrough available online about using all this sdk, where to download from, etc.?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=9981321&postcount=3

[Q] keyboard to stay lit longer

Howdy,
I have looked at the threads suggested to check out before starting a new one, and they did not help me much. I am a noob, and that may be why.
I have a sidekick 4g and would like the keyboard to stay lit a lot longer than it does. I slide it out and if I pause for the briefest of time, and the light goes out. Id there a way to make it stay lit until I close the keyboard?
Do I have to root the phone in order to make this happen? I have been reading all the root stuff I can find but not quite ready to take the plunge yet. I most likely can do it b sometimes I lack confidence when starting new things.
Thanks for the help ahead of time.
XcntrK

xcntrk said:
Howdy,
I have looked at the threads suggested to check out before starting a new one, and they did not help me much. I am a noob, and that may be why.
I have a sidekick 4g and would like the keyboard to stay lit a lot longer than it does. I slide it out and if I pause for the briefest of time, and the light goes out. Id there a way to make it stay lit until I close the keyboard?
Do I have to root the phone in order to make this happen? I have been reading all the root stuff I can find but not quite ready to take the plunge yet. I most likely can do it b sometimes I lack confidence when starting new things.
Thanks for the help ahead of time.
XcntrK
Click to expand...
Click to collapse
rooting is real simple
first download one click hedmial root (in either a stick in development or my ref)
go to settings on phone then applications then development turn debugging on
open one click
now hit root
finished
and yes to do anything good you need to root

Changing your screen timeout seems to affect how long the keyboard stays lit also. For example, I changed my screen timeout to 1 minute, and the keyboard stayed lit the whole time. Just go into Android Settings, find "Display" --> "Screen timeout" and set it to your choosing. Also, just tapping the Shift or Alt button turns the keyboard backlight on again.
I concur with immorality, rooting is no big deal. It's when you start messing with the system and flashing ROMs that things can go wonky if you don't know what you're doing and aren't careful, but most failures are recoverable using the aforementioned Heimdall.

Thanks for the info. I am going to go ahead and do the root. I would love to get rid of all this tmobile junk on the phone. And there are some other cool things that I have been reading about that you can do after you have rooted your phone. I will keep the forum up and running though just in case LOL
Thanks again y'all

tell you what, ill look into the keyboard light in the next day or so and when i find how to control them ill create you a flashable zip so you can easily change the time they stay on. or maybe even add it to my aroma package
but for now root your phone as you wont be able to do anything without it, follow the above method if youd like, i personally dont like one click root methods for various reasons so heres a quick guide i made
http://forum.xda-developers.com/showpost.php?p=40198560&postcount=27
again follow any method you would like, and i suggest to at least read up on the various ways. hopefully by the time your done and ready to flash your first rom ill have had time to look into the keyboard lights issue
good luck and happy flashing!

@demkantor thank you so very much. I am downloading the aroma, and have copied the notes on your link.
My Kaspersky is not letting me downliad the rage against the machine. I will see if I can get around it and let you know the outcome
I really do appreciate your help with the lights on the keyboard. I have tried resetting the screen timeout and every other thing suggested or that I can think of and it still goes out a second or so after the last letter entered.

hey no problem! try another browser maybe or turn virus protection off, any script that works to exploit a loophole will through the virus protection. hell some wont let you download superuser
but i assure you its legit
as for the keyboard lights, my sk4g is incapacitated right now so i ran a few tests in another android:
When i run this in a shell:
busybox find / -name 'timeout' 2> /dev/null | busybox grep -i timeout
I get this:
2> /dev/null | busybox grep -i timeout <
/system/xbin/timeout
/sys/class/firmware/timeout
/sys/module/uvcvideo/parameters/timeout
/sys/module/nf_conntrack_netbios_ns/parameters/timeout
and if i run:
busybox find / -name 'brightness' 2> /dev/null | busybox grep -i backlight
gives me:
ss' 2> /dev/null | busybox grep -i backlight <
/sys/devices/platform/pwm-backlight/backlight/pwm-backlight/brightness
so i know where to start digging in my other androids, and hopefully if i find a fix in one it will be similar in the sidekick. ill keep you posted!

Got it, had to shut of part of Kaspersky and then make a exclusion for it when I unzipped LOL BUT I GOT IT YEAH!!! LOL
Thanks for all the effort with this.

[Q] aplogd is eating up the battery. how to fix?

Well, as for me, battery life of Photon Q with CM never was good enough. But after a day ago I've got my phone from 100% to 1% in 6 (yes, six) hours, I've understood, that I have to do something. BetterBatteryStats was excellent, it pointed me at the culprit in just a few taps. Beside turning phone into some heating appliance it also stored gigs of logs onto internal memory (/data/logger). Next question was: how to deal with it. Tries to simply kill it failed, as it respawned right away. After some searching I've come to build.prop tuning. I've changed
Code:
persist.log.aplogd.enable=1
to
Code:
persist.log.aplogd.enable=0
and added
Code:
persist.service.aplogd.enable=0
, rebooted to recovery, wiped cache and davlik cache, rebooted again and... aplogd is still here and its still can't be killed. So, I welcome any hints on how to fix it.

To disable aplogd, you don't have to do silly things like editing build.prop or such.
It's controlled by persistent property (physically stored in /data/property), so your setting of this property will stick as long as you don't wipe your data.
build.prop just specifies the default behaviour - what's set in /data/property (usually set by setprop command) always wins over the persistent property value indicated in build.prop.
In terminal emulator:
Code:
su
setprop persist.log.aplogd.enable 0
This will make the init process to stop the aplogd process and it won't be started again even after subsequent reboots (till the wipe of data, as mentioned above).
But, what exact output from BetterBatteryStats makes you think that aplogd is the actual cause of your battery issues?
It's behaving pretty harmless regarding the battery here by all accounts as far as I was able to check.
I've enabled aplogd on xt897 CM by default to help users to be able to deliver the logs to developers. As you probably understand: no log provided, no issue exists (from the dev point of view). Bugs can't be fixed when the developer is blindfolded, same as a disease can't be cured over mute phone line to a doctor....
Also, the size and number of files created by aplogd in /data/logger is strictly limited, so when you say
it also stored gigs of logs onto internal memory
Click to expand...
Click to collapse
what exact size of /data/logger folder content have you seen in your case?
(I ask about this because there may be a bug in the aplogd log file size/number limiting code, so I'd like to know if I should look into it or not...).

kabaldan said:
To disable aplogd, you don't have to do silly things like editing build.prop or such.
Click to expand...
Click to collapse
Learning is not about avoid to do silly things its about not to repeat them. I found the forums (http://4pda.ru/forum/index.php?showtopic=386024&view=findpost&p=16243763 for example) where people advised to add "persist.service.aplogd.enable=0" to build.prop and swear it's working.
kabaldan said:
It's controlled by persistent property (physically stored in /data/property), so your setting of this property will stick as long as you don't wipe your data.
build.prop just specifies the default behaviour - what's set in /data/property (usually set by setprop command) always wins over the persistent property value indicated in build.prop.
In terminal emulator:
Code:
su
setprop persist.log.aplogd.enable 0
This will make the init process to stop the aplogd process and it won't be started again even after subsequent reboots (till the wipe of data, as mentioned above).
Click to expand...
Click to collapse
Thanx!
kabaldan said:
But, what exact output from BetterBatteryStats makes you think that aplogd is the actual cause of your battery issues?
It's behaving pretty harmless regarding the battery here by all accounts as far as I was able to check.
Click to expand...
Click to collapse
Process section showed aplogd as eating times more CPU time than any other. Also CPU States section showed that processor was almost all the time runing at 1,5Ghz.
kabaldan said:
I've enabled aplogd on xt897 CM by default to help users to be able to deliver the logs to developers. As you probably understand: no log provided, no issue exists (from the dev point of view). Bugs can't be fixed when the developer is blindfolded, same as a disease can't be cured over mute phone line to a doctor....
Click to expand...
Click to collapse
Of course. I suspect it was kind of "exclusive" to me. I don't argue about enabling it by default, just asked about issue.
kabaldan said:
Also, the size and number of files created by aplogd in /data/logger is strictly limited, so when you say
what exact size of /data/logger folder content have you seen in your case?
(I ask about this because there may be a bug in the aplogd log file size/number limiting code, so I'd like to know if I should look into it or not...).
Click to expand...
Click to collapse
I've cleared all files in /data/logger about same time as posted this topic . Now there is 5086 files. Size according to 'du -sk' is 99820 - almost 100M. So maybe I exaggerated a bit about "gigs", but there was definitely hundreds of "megs" of backup* files.

Disable Touch wake, a way to save battery.

Hey guys, this is my first post so probably i will have a lot of erros. Pls dont be angry haha.
First Everything here is at your own risk so if your watch stop working is your fault no mine. You have been warned. Lets start:
-You need to instal TWRP in your smartwatch.
Here some links:
-(MOTO 360) http://forum.xda-developers.com/moto-360/development/unofficial-twrp-2-8-1-0-moto-360-t2966750
-(SONY SMARTWATCH 3) http://forum.xda-developers.com/sma...overy-twrp-2-8-3-0-sony-smartwatch-3-t2986907
-(LG G R) http://forum.xda-developers.com/g-watch-r/development/root-root-twrp-r-t2960511
Click to expand...
Click to collapse
-When you have installed, start in recovery mode, and go to mount and press system. Connect your watch to your computer and open ADB
adb root
adb pull /system/usr/idc/sec_touchscreen.idc <where you want to save the file>
Click to expand...
Click to collapse
-Make a copy of the file and open the file with notepad++, you will se the following things
# Copyright 2014 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#
# Input Device Calibration File for the Dory touch screen.
#
device.internal = 1
touch.deviceType = touchScreen
touch.orientationAware = 1
touch.wake = 1
Click to expand...
Click to collapse
-Remove the part of ( touch.wake = 1 , please make a copy, because you will need it .
-Now go other time to adb and putt he following
adb push /system/usr/idc/ <where you have the file>
Click to expand...
Click to collapse
-Restart the watch.
-Now you will see that is impossible to block the watch, calm down xD. Restart other time the watch in recovery.
-Now with the copy of the original file, mount system on twrp and puth this on adb (the file must have the same name as the original)
adb push /system/usr/idc/ <where you have the copy>
Click to expand...
Click to collapse
-Restart the watch and now, you will se that the screen is only going to be unlocked by the button of your watch.
Also if you want to sabe more battery you can change the cpu governor

Looks like you have mistyped adb push into adb pull.
Good idea. Tryin.
EDIT : looks like you don't know adb pull and push:
Push means Computer to Device
Pull means Device to Computer
---------- Post added at 19:51 ---------- Previous post was at 19:46 ----------
And shouldn't 'sec' means Samsung? This guide may only work for Samsung devices. Please modify.
Maybe we have to find the exact file using ls.
Nice work.

I know hahaha, muy mistake .Also i want to know if this work for mor people
Sent from my A0001 using XDA Free mobile app

Thanks! Ill wait a bit for you to work out the typos. I also have to decide if i want to keep my LG R or get the zenwatch2 when it is out... But hanks all the same. This has been bugging me since i got the watch. Theater mode doesn't send notifications and I cross my arms while I sleep, waking my watch up all night...
Also thanks for posting the other sources for each watch. Great first post!

Working on Gear 2.. no need to copy the original file back.

working on LG g watch (wear 5.1) fine too, but the .idc-filename is
/system/usr/idc/synaptics_rmi4_i2c.idc now!
Only replace the last line
Code:
touch.wake = 1
with
Code:
# touch.wake = 1
I'm sure
Code:
touch.wake = 0
instead of commenting out, would work to! - But didn't test it...
and push the file back...
after reboot touch2wake is disabled and rotateWRIST2wake works fine!
Lets see how much battery drain will be decreased...
Thanx @dataonlycod ! (for finding and your solution):good:

No measureable benefit
Disabling touch2wake gave me no longer battery life here !!!

I've done the mod on my LGWR by simply booting (not flashing) TWRP
funny thing is that now the watch won't wake when touched, but it is still possible to scroll through notifications
bitstra said:
Disabling touch2wake gave me no longer battery life here !!!
Click to expand...
Click to collapse
as scrolling notifications is still possible, the touch screen is still active
to save battery, you would have to find a way to really disable it - but the power reduction sould be negligible

2k4ever said:
as scrolling notifications is still possible, the touch screen is still active
Click to expand...
Click to collapse
how can i block scrolling in ambient mode?

starbase64 said:
how can i block scrolling in ambient mode?
Click to expand...
Click to collapse
I don't know
keep in mind that disabling touch 2 wake is just a hack
the most probable way would be an xposed module that disables the toch screen when the watch goes into ambient mode

I was hoping this would fix the issue i have when i cross my arms and the watch starts doing things because it thinks my arm is my finger... ugh

Thanks
La:good:

Has anybody managed to get this hack working on the Sony Smartwatch 3.
The file that appears to need editing is called 'synaptics_dsx.idc'.
I have ensured the edited file is pushed back to the phone, but the hack never works.

hi friends/ does it work for URBANE ?

Hi friends, anyone get it to work with Moto 360 ?

persichini said:
I was hoping this would fix the issue i have when i cross my arms and the watch starts doing things because it thinks my arm is my finger... ugh
Click to expand...
Click to collapse
I had the same issue.
And here's what I did:
1. Set touch.wake = 0 on the file
2. Installed 'Showear: Android Wear Lock ' app from google play
link: https://play.google.com/store/apps/details?id=com.jdd.showear&hl=fi
3. Set lock method as sequence of swipes: Just one swipe from left to right
4. Set the following setting:
- Auto-lock on standy
- Lock on startup
- Vibration (to notify me when I unlock the screen since I set the lock screen invisible)
- Hide lock screen on standby
- Transparent lock screen
- Transparent (unselected) lock elements (Answer no to the msg box after setting this on)
Yes this way needs me to swipe the screen from left to right every time I want to use touch on the watch with my finger, but it is now impossible for any touch event to occur when the screen is dimmed since the lock cannot be unlocked from dim mode with the option 'Hide lock screen on standby' selected.
And having that no-touch on dim mode is way more important to me than the added swipe.
Hope this helps

very useful tip , thanks

Thank you

nice woooooooork

Fine
I will try, anyway I get pretty decent batt life with my Sony sw3, 4 days.

Themes / Apps / Mods Quick tip on adjusting screen saturation on rooted pixel

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