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.
So I decided to see if I could work around the fact that the keyboard and navigation button backlights on the G1 don't work on ROMs that are taken from keyboard-less devices, e.g. Hero, Eris, Legend, etc. I suspect this will never actually be fixed "properly" because the frameworks etc in such ROM dumps can (in normal circumstances on their intended devices) safely assume there's no keyboard device.
In /sys/class/leds there are "folders" and "files" for each of the lights on the phone, i.e. one for the keyboard backlight, one for the button backlights, the jogball light, and the leds. You can actually manually turn these lights on by piping the number 1 into the brightness file of the corresponding light, e.g. echo 1 > /sys/class/leds/keyboard-backlight will turn the keyboard backlight on.
So, why my script does is sit monitoring logcat for certain lines that indicate appropriate events, and pipe the appropriate number into the right backlight brightness "file" accordingly.
To test, you can push it to your phone as follows:
adb remount (to enable read-write of /system)
adb push lightbodge.txt /system/bin/lightbodge.sh
Then, to test it:
adb shell
chmod 777 /system/bin/lightbodge.sh
sh /system/bin/lightbodge.sh
Note - the filename in the second line is "lightbodge.txt" in one place and "lightbodge.sh" in another. That's not a mistake. The board won't let me attach .sh files.
Check you're happy with it doing what it's supposed to while still connected to your PC. Then, you can do one of two things:
1) just do
su
sh /system/bin/lightbodge.sh &
at a terminal on your phone
or
2) you could probably add it to your a2sd script
Known concerns:
* Bear in mind that I don't have a G1 myself - I have a Magic. So I am dependent on you lot for testing and information! At the moment, it's looking for a "rotate" event because no-one's been able to give me a distinct entry in logcat for the keyboard being opened. So the keyboard light may well come on if you rotate the phone as well as when you pull open the keyboard. Also, if you open the keyboard but aren't triggering a rotate (maybe you were already in landscape?) I'm not sure there's an event for my script to see. Please give me any logcat information you can and join in the discussion so I can get some more info.
* On my MT3G, I'm getting odd results. If my phone is being charged or plugged into the USB in any way - even if the USB is not being used - then it all works as I'd expect. If it's unplugged, it seems oddly unreliable. I need as many testers to try it on their phone and tell me what results they get.
* This script is running once every second, and doing two logcats each time. I'm not convinced about this not being a big hit on performance yet. It needs testing in real life.
How you can help:
* I need as much information about what the G1 does when you pull the keyboard as possible. If anyone can narrow down a consistent logcat line that happens when the keyboard is opened and closed and ONLY when the keyboard is opened/closed, that's the holy grail of this thread at the moment.
* In theory we should be able to do something with LEDs for notifications for things like emails, etc. Again, consistent and unique logcat entries for things like email received, SMS received, would be useful on that front.
* other devs: feel free to tidy up and improve on my script. I freely admit it's just flung together. In particular, there must be a more elegant way of monitoring logcat than what I'm doing. And if any of you can come up with that holy grail logcat line, that'd be great.
Changelog
Version 0.1 (see post 7) - initial version
Version 0.2 - slight tidying up - no reason why you should use it though
Version 0.3 (current version attached to this post)
- changed to detect activities based on log file size rather than grep
- hopefully better logcat triggers being used to the various activities
- tested at least on my MT3G - navigation button lights work when script dumped into A2SD*
Loccy said:
So, as we all know, the keyboard backlight on the G1 is dead on ROMs taken from devices that have no keyboard, e.g. Hero, Eris, Legend, etc. I suspect the reality is we're never going to be able to fix this "properly" because these ROMs simply don't expect this keyboard to even exist.
But, I find myself wondering about the devices in /sys/class/leds having seen Markus214's post in King's Droid Eris thread:
http://forum.xda-developers.com/showthread.php?p=5967098&highlight=led#post5967098
Having been playing with renicing scripts today, I'm thinking that maybe another script in the background that just sat there, and did
echo 1 > /sys/class/leds/keyboard-backlight/brightness
whenever the keyboard needed to be on would essentially fix the problem. It'd be an appalling kludge, but I see no reason why it wouldn't work.
So now, what we need, is a way of, in a bash script, detecting when the keyboard has been opened. Therein is the problem - I don't have a G1, I have a Magic.
What I can do with my Magic at least, to test the principle, is to fix the backlight on the buttons like home, menu etc.
So on my Magic, when I hit such a key, I get
Code:
D/KeyguardViewMediator( 117): pokeWakelock(15000)
in my logcat.
Correspondingly, when the screen is going off (either through timeout or turning it off I get)
Code:
D/SurfaceFlinger( 117): About to give-up screen, flinger = 0x145db8
What I have in mind is a script that sits there, and runs
Code:
echo 1 > /sys/class/leds/button-backlight/brightness
when the first logcat entry happens, and the echo 0 command when the second logcat entry happens. That should, essentially, turn on the button backlights whenever a button is pressed, and turn them off when the screen goes off.
Now if you G1 owners can find corresponding logcat lines for keyboard open and close, we should be able to do the same with keyboard-backlight as well.
I'll keep you all posted how my efforts go with the Magic button backlights go - if some G1 guys can have a look and see if there's any similar logcat activity when the keyboard is opened and closed, it'd be helpful further down the line if I can get this concept working at all.
Click to expand...
Click to collapse
Those same commands happen with us.
Shaquiel Harris said:
Those same commands happen with us.
Click to expand...
Click to collapse
Yes, but what I'm looking for is any different entries you get in your logcat when you open and close your keyboard.
Loccy said:
Yes, but what I'm looking for is any different entries you get in your logcat when you open and close your keyboard.
Click to expand...
Click to collapse
Oh lol im sorry. This is what happens when opened:
I/WindowManager( 9621): Setting rotation to 1, animFlags=1
I/ActivityManager( 9621): Config changed: { scale=1.0 imsi=310/260 loc=en_US touch=3 keys=2/1/1 nav=3/1 orien=2 layout=18}
Click to expand...
Click to collapse
When closed,
I/WindowManager( 9621): Setting rotation to 0, animFlags=1
I/ActivityManager( 9621): Config changed: { scale=1.0 imsi=310/260 loc=en_US touch=3 keys=2/1/2 nav=3/1 orien=1 layout=18}
Click to expand...
Click to collapse
Well that was easier than I thought. Here's a first crack for "fixing" the button backlights on ROMs where they're not supported.
Code:
#!/system/bin/sh
echo "Monitoring logcat"
mkdir /sdcard/logcatmon
# monitor for screen going off
logcat -d | grep "About to give-up screen" > /sdcard/logcatmon/logcat-screenoff.txt
logcat -d | grep "About to give-up screen" > /sdcard/logcatmon/logcat-screenoffX.txt
# monitor for screen going on
logcat -d | grep "pokeWakelock" > /sdcard/logcatmon/logcat-screenon.txt
logcat -d | grep "pokeWakelock" > /sdcard/logcatmon/logcat-screenonX.txt
while [ 1 ]
do
# update monitor
logcat -d | grep "About to give-up screen" > /sdcard/logcatmon/logcat-screenoff.txt
logcat -d | grep "pokeWakelock" > /sdcard/logcatmon/logcat-screenon.txt
# if screen on
diff -i -b -q /sdcard/logcatmon/logcat-screenon.txt /sdcard/logcatmon/logcat-screenonX.txt
if [ ! $? -eq 0 ]; then
echo "Screen turned on"
echo 1 > /sys/class/leds/button-backlight/brightness
logcat -d | grep "pokeWakelock" > /sdcard/logcatmon/logcat-screenonX.txt
fi;
# if screen off
diff -i -b -q /sdcard/logcatmon/logcat-screenoff.txt /sdcard/logcatmon/logcat-screenoffX.txt
if [ ! $? -eq 0 ]; then
echo "Screen turned off"
echo 0 > /sys/class/leds/button-backlight/brightness
logcat -d | grep "About to give-up screen" > /sdcard/logcatmon/logcat-screenoffX.txt
fi;
sleep 1
done;
What this does is create a working directory in the sdcard to stash its working files. Every second it checks to see if there's been a new entry in logcat for screen on or off - it does this by stashing an appropriate grep of logcat every second, and comparing it to the last one. If they differ, then there's been an appropriate entry in logcat in the last second - meaning that the screen has either come on or gone off. Depending on which is the case, we push the appropriate value to button-backlight/brightness.
Concerns about this approach:
* running logcat every second - twice - and grepping the output. That can't be a trivial demand on processing resources.
* when/if logcat wraps (I assume it doesn't just get bigger, and bigger, and bigger) it'll be seen as a change, meaning you'll get a spurious backlight event. In theory it should be immediately followed by a spurious backlight OFF event - so hopefully no harm no foul. But if I'm wrong, I'm not sure what it'll do to battery life.
Ok people. Pick holes in this, tell me it's appallingly inelegant - off you go!
Shaquiel Harris said:
Oh lol im sorry. This is what happens when opened:
I/WindowManager( 9621): Setting rotation to 1, animFlags=1
I/ActivityManager( 9621): Config changed: { scale=1.0 imsi=310/260 loc=en_US touch=3 keys=2/1/1 nav=3/1 orien=2 layout=18}
When closed,
I/WindowManager( 9621): Setting rotation to 0, animFlags=1
I/ActivityManager( 9621): Config changed: { scale=1.0 imsi=310/260 loc=en_US touch=3 keys=2/1/2 nav=3/1 orien=1 layout=18}
Click to expand...
Click to collapse
Hmmm. Is that all? Is the keyboard just treated like a Magic's rotation? Is there nothing more explicitly related to the keyboard? I don't really want to turn on the keyboard every time rotation changes. Basically it'd mean the keyboard would always be on when the phone is rotated into landscape mode.
Ok, so I've just implemented the same scenario as for the home/menu/etc buttons based on those logcat strings Shaquiel gave me. Am not totally convinced that rotation is the thing to look for, but we'll see how it goes.
The keyboard backlight bit I can't obviously test this myself, as I have a Magic. I tested it by making rotation turn the jogball on and off, which seemed to work. For the keyboard backlight I am working a bit blind, though.
Anyway, let's not install this too permanently on anyone's phone just yet, but it'd be appreciated if a G1 person could give it a whirl on an appropriate Sense ROM (e.g. King's Eris, Vega or King's Legend, etc). Here's how:
Stash the lightbodge.txt file on your hard disk somewhere, and then do, from a command line (assuming you have adb here)
adb push lightbodge.txt /sdcard/lightbodge.sh
adb shell
cd /sdcard
sh lightbodge.sh
You should find that pressing the appropriate buttons will result in the lights coming on, and (hopefully) pulling out the keyboard will do the same.
When you're finished testing, press control-C to kill the script. Once I've got some decent test feedback we'll look at how best to make it run on phones in the background.
It might be that you need to be in an app that actually changes orientation when you pull the keyboard out in order for the keyboard light bit to do anything - am not sure about that.
Edit: IF YOU TRY THIS AND POST TO CONFIRM IT WORKING, OR NOT WORKING, CAN YOU PLEASE BE SURE TO TELL ME WHAT ROM YOU ARE TRYING IT ON.
sh: Can't open lightbodge.sh
XZ32 said:
sh: Can't open lightbodge.sh
Click to expand...
Click to collapse
Did you cd /sdcard?
And is lightbodge.sh definitely there on your sdcard?
Loccy said:
Ok, so I've just implemented the same scenario as for the home/menu/etc buttons based on those logcat strings Shaquiel gave me. Am not totally convinced that rotation is the thing to look for, but we'll see how it goes.
The keyboard backlight bit I can't obviously test this myself, as I have a Magic. I tested it by making rotation turn the jogball on and off, which seemed to work. For the keyboard backlight I am working a bit blind, though.
Anyway, let's not install this too permanently on anyone's phone just yet, but it'd be appreciated if a G1 person could give it a whirl on an appropriate Sense ROM (e.g. King's Eris, Vega or King's Legend, etc). Here's how:
Stash the lightbodge.txt file on your hard disk somewhere, and then do, from a command line (assuming you have adb here)
adb push lightbodge.txt /sdcard/lightbodge.sh
adb shell
cd /sdcard
sh lightbodge.sh
You should find that pressing the appropriate buttons will result in the lights coming on, and (hopefully) pulling out the keyboard will do the same.
When you're finished testing, press control-C to kill the script. Once I've got some decent test feedback we'll look at how best to make it run on phones in the background.
It might be that you need to be in an app that actually changes orientation when you pull the keyboard out in order for the keyboard light bit to do anything - am not sure about that.
Click to expand...
Click to collapse
awesome works perfect
Loccy said:
Did you cd /sdcard?
And is lightbodge.sh definitely there on your sdcard?
Click to expand...
Click to collapse
woops sorry was too fast, testing now
the front buttons work just fine!
the keyboard howver gives the following error in logcat:
"lightbodge.sh: cannot creqte /sys/class/leds/keyboard-blacklight/brightness: permission denied"
XZ32 said:
the front buttons work just fine!
the keyboard howver gives the following error in logcat:
"lightbodge.sh: cannot creqte /sys/class/leds/keyboard-blacklight/brightness: permission denied"
Click to expand...
Click to collapse
yeah i was a little quick to same problem with keyboard
XZ32 said:
the front buttons work just fine!
the keyboard howver gives the following error in logcat:
"lightbodge.sh: cannot creqte /sys/class/leds/keyboard-blacklight/brightness: permission denied"
Click to expand...
Click to collapse
Did you type that, or copy and paste it? If my script has blacklight rather than backlight in, no wonder it didn't work! But I can't see that typo here anywhere on my versions of the script.
Assuming it's a typo when you were transcribing it -
What ROM are you running?
And you *do* have a G1, don't you?
Could you do something else for me? In an adb shell,
cd /system/class/leds
ls
and tell me what you see there.
Loccy said:
Did you type that, or copy and paste it? If my script has blacklight rather than backlight in, no wonder it didn't work! But I can't see that typo here anywhere on my versions of the script.
Assuming it's a typo when you were transcribing it -
What ROM are you running?
And you *do* have a G1, don't you?
Could you do something else for me? In an adb shell,
cd /system/class/leds
ls
and tell me what you see there.
Click to expand...
Click to collapse
I typed it lol sorry for the typos, on AZERTY kb here...
I'm currently running Kings DroidEris 1.2, On G1 yes
sec ill try it out
cd: can't cd to /system/class/leds
XZ32 said:
cd: can't cd to /system/class/leds
Click to expand...
Click to collapse
D'oh.
That's
/sys/class/leds
sorry!
AWESOME work Loccy !!!!! It works. Just tried sending a text and the keyboard lights definetley work !!! Work a couple of seconds after you open keyboard on any other screen aswell. Keep up the awesome work
lcd-backlight
blue
green
red
spotlight
keyboard-backlight
button-backlight
XZ32 said:
lcd-backlight
blue
green
red
spotlight
keyboard-backlight
button-backlight
Click to expand...
Click to collapse
Good. So the keyboard backlight is there - for a moment I thought it might not be, and this would all have been for nothing.
So, what happens if you do
echo 1 > /sys/class/leds/keyboard-backlight/brightness
???
I'm trying to turn in the led on boot for a custom thing.....
Anyways the usual echo wont work, i've tried
echo 255 > /sys/class/leds/red/brightness
echo 1 > /sys/class/leds/red/brightness
and blue and green.
When i try
echo 255 > /sys/class/leds/button-backlight/brightness
the buttons light up fine, but leds won't light up...
I'm guessing i'm doing something wrong here, any help?
+1 Same here.
Aaahh said:
I'm trying to turn in the led on boot for a custom thing.....
Anyways the usual echo wont work, i've tried
echo 255 > /sys/class/leds/red/brightness
echo 1 > /sys/class/leds/red/brightness
and blue and green.
When i try
echo 255 > /sys/class/leds/button-backlight/brightness
the buttons light up fine, but leds won't light up...
I'm guessing i'm doing something wrong here, any help?
Click to expand...
Click to collapse
Are you still having a problem or did you fix it? I might have a couple of ideas
sent from my amazingly awesome OnePlus One with Stereo Mod
Don't forget to hit thanks!
abhi08638 said:
Are you still having a problem or did you fix it? I might have a couple of ideas
sent from my amazingly awesome OnePlus One with Stereo Mod
Don't forget to hit thanks!
Click to expand...
Click to collapse
I would be pleased to be enlightened!
Aaahh said:
I would be pleased to be enlightened!
Click to expand...
Click to collapse
Well under /sys/class/leds/led:flash_0, there is a trigger file so that might be causing the blue green and red brightness to be overwritten or not allowed to activate. Try changing the brightness in this directory, I think limit is 1000
sent from my amazingly awesome OnePlus One with Stereo Mod
Don't forget to hit thanks!
That is the flash led, I think the thread is about turning on the notification led from shell. I having the same issue (not able to turn on the notif. led with the above commands). Any solutions so far?
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