Hi.
I bought this phone some months ago, and for the basic thing is being horrible: making calls.
All the people (no matter where the other person is around the globe) tell me that they hear themselves when they are talking to me. That they are hearing a echo of themselves. And also noise and very bad quality.
I wasnt paying attention to that, coz I was just happy with my new phone. And someties, lowing the volume was enough to fix the things... even though, the other person was telling me "well... i cant hear you well, but better than before".
Today I gave my phone to friend to call to my phone its HORRIBLE!!!
The thing is, the person who calls to my phone:
- hears himself/herself with echo
- the audio quality is horrible
- if you slide your fingers around the phone (it doesnt matter where... on the screen, on the back, on the side..) or just if you move a finger or the hand... it makes a lot of noise like annoying wind. you hear a lot more of this than the voice.
I am the only person with this problem???
How can I know if its a hardware or software problem?
Thanks
I have the same issue. I called the support and they try different things - without success. It seems to be a hardware issue.
I have to send the phone to Sony. With the problemnumber I have to order via the support website a repairpackage for free delivery. The repair include shipping can be 2 weeks. During this time I have no phone. Therefore I didn't it till now.
When I use external microphone - via Bluetooth - I don't have the issue
Sent from my E5823 using XDA-Developers mobile app
i have the same problem......
I use speakerphone and it happens. It seemed to have happened on a z3 compact i had for a short period of time as well.
secfincorp said:
i have the same problem......
I use speakerphone and it happens. It seemed to have happened on a z3 compact i had for a short period of time as well.
Click to expand...
Click to collapse
Same problem here on three different Z5 Compact phones, 2 of them shipped from Sony quality control. Seems like a systemic issue.
Hi Everyone,
Same here. Nobody hears me when I speak. It occurs often when the network signal is poor like 2 bars...
Does anyone find a solution?
Mine is still under warranty. I'm hesitating if I should send it to Sony...
Thanks,
This problem is easy to solve if an unlocked bootloader.
You need to edit the config mixer_paths.xml
Code:
<!-- Gain offset target for dmic1 unit calibration -->
<path name="dmic1-adj-gain">
<ctl name="DEC7 Volume" value="84" />
</path>
<!-- Gain offset target for dmic2 unit calibration -->
<path name="dmic2-adj-gain">
<ctl name="DEC9 Volume" value="84" />
</path>
dmic1 - the main microphone;
dmic2 - noise-canceling microphone.
You need to change the config roughly like the following:
Code:
<!-- Gain offset target for dmic1 unit calibration -->
<path name="dmic1-adj-gain">
<ctl name="DEC7 Volume" value="[COLOR="Red"]87[/COLOR]" />
</path>
<!-- Gain offset target for dmic2 unit calibration -->
<path name="dmic2-adj-gain">
<ctl name="DEC9 Volume" value="[COLOR="red"]81[/COLOR]" />
</path>
grayleshy said:
This problem is easy to solve if an unlocked bootloader.
You need to edit the config mixer_paths.xml
Code:
<!-- Gain offset target for dmic1 unit calibration -->
<path name="dmic1-adj-gain">
<ctl name="DEC7 Volume" value="84" />
</path>
<!-- Gain offset target for dmic2 unit calibration -->
<path name="dmic2-adj-gain">
<ctl name="DEC9 Volume" value="84" />
</path>
dmic1 - the main microphone;
dmic2 - noise-canceling microphone.
You need to change the config roughly like the following:
Code:
<!-- Gain offset target for dmic1 unit calibration -->
<path name="dmic1-adj-gain">
<ctl name="DEC7 Volume" value="[COLOR="Red"]87[/COLOR]" />
</path>
<!-- Gain offset target for dmic2 unit calibration -->
<path name="dmic2-adj-gain">
<ctl name="DEC9 Volume" value="[COLOR="red"]81[/COLOR]" />
</path>
Click to expand...
Click to collapse
I am trying this, unlocked bootloader and root, but the mixer_paths.xml file gets overwritten with the old values everytime i save it. Any suggestions? I am using X-plore file manager. Thanks
pyraohms said:
I am trying this, unlocked bootloader and root, but the mixer_paths.xml file gets overwritten with the old values everytime i save it. Any suggestions? I am using X-plore file manager.
Click to expand...
Click to collapse
The answer is simple, use another file manager!
grayleshy said:
The answer is simple, use another file manager!
Click to expand...
Click to collapse
This fix really did the trick! I set the high value to 99 and the low to 70.
Mic sensitivity: Auto
Automatic optimization: On
Equalizer: Normal
Big thanks!!
just received my new z3 compact...and until making calls ( who does that nowadays ? ) i didn't even notice the problems other people were having with echo.
I guess this fix will work for all z phones...will have to find the step by step guide to avoid bricking anything, but big thanks anyway
worse than before
I tried this solution but now if I run google play for example it goes into a loop without leaving any sound and I can not finish the app anymore. just restarting the phone. if I do or receive a call I do not hear anything and I am not even listened to by the person who called.
I returned the values in the mixer file, restart the phone, but the problem continues.
any clue ??? :crying:
GreyLeshy said:
This problem is easy to solve if an unlocked bootloader.
You need to edit the config mixer_paths.xml
Code:
<!-- Gain offset target for dmic1 unit calibration -->
<path name="dmic1-adj-gain">
<ctl name="DEC7 Volume" value="84" />
</path>
<!-- Gain offset target for dmic2 unit calibration -->
<path name="dmic2-adj-gain">
<ctl name="DEC9 Volume" value="84" />
</path>
dmic1 - the main microphone;
dmic2 - noise-canceling microphone.
You need to change the config roughly like the following:
Code:
<!-- Gain offset target for dmic1 unit calibration -->
<path name="dmic1-adj-gain">
<ctl name="DEC7 Volume" value="[COLOR="Red"]87[/COLOR]" />
</path>
<!-- Gain offset target for dmic2 unit calibration -->
<path name="dmic2-adj-gain">
<ctl name="DEC9 Volume" value="[COLOR="red"]81[/COLOR]" />
</path>
Click to expand...
Click to collapse
puiatmp said:
I tried this solution but now if I run google play for example it goes into a loop without leaving any sound and I can not finish the app anymore. just restarting the phone. if I do or receive a call I do not hear anything and I am not even listened to by the person who called.
I returned the values in the mixer file, restart the phone, but the problem continues.
any clue ??? :crying:
Click to expand...
Click to collapse
These parameters affect only the microphone, and since you have restored them, it means that you spoiled something earlier.
Fixed
GreyLeshy said:
These parameters affect only the microphone, and since you have restored them, it means that you spoiled something earlier.
Click to expand...
Click to collapse
Problem fixed. Was the file permissions. I think my file explorer change the permission after save the file.
Change the permissions to default and all back to work.
Tks.
No sounds after
After changing values in mixer_paths and reboot, microphones and speaker stopped working. I'm using lineageos 14.1. Any clues why that's happening?
GreyLeshy said:
This problem is easy to solve if an unlocked bootloader.
You need to edit the config mixer_paths.xml
Code:
<!-- Gain offset target for dmic1 unit calibration -->
<path name="dmic1-adj-gain">
<ctl name="DEC7 Volume" value="84" />
</path>
<!-- Gain offset target for dmic2 unit calibration -->
<path name="dmic2-adj-gain">
<ctl name="DEC9 Volume" value="84" />
</path>
dmic1 - the main microphone;
dmic2 - noise-canceling microphone.
You need to change the config roughly like the following:
Code:
<!-- Gain offset target for dmic1 unit calibration -->
<path name="dmic1-adj-gain">
<ctl name="DEC7 Volume" value="[COLOR="Red"]87[/COLOR]" />
</path>
<!-- Gain offset target for dmic2 unit calibration -->
<path name="dmic2-adj-gain">
<ctl name="DEC9 Volume" value="[COLOR="red"]81[/COLOR]" />
</path>
Click to expand...
Click to collapse
Will this work for stock rom 32.4.A.0.160?
My bootloader is unlocked.
thundastruck said:
Will this work for stock rom 32.4.A.0.160?.
Click to expand...
Click to collapse
Yes, will work.
GreyLeshy said:
Yes, will work.
Click to expand...
Click to collapse
I guess I have to be rooted, right?
thundastruck said:
I guess I have to be rooted, right?
Click to expand...
Click to collapse
No, You can do all this through recovery.
GreyLeshy said:
No, You can do all this through recovery.
Click to expand...
Click to collapse
Oh wow! Definately wanna give it a shot then. Gonna google for a guide. Thanks!
Sent from my SM-G930F using Tapatalk
thundastruck said:
Oh wow! Definately wanna give it a shot then. Gonna google for a guide.
Click to expand...
Click to collapse
Replace the file in archive with your own.
https://forum.xda-developers.com/z5-compact/development/soundmod-nougat-2-33-0-160-t3629243
Related
Noise Tracker
Noise Tracker measures the loudness by taking an audio sample and calculating its mean average. The black bars are the mean values and the current wave is drawn in blue. Don't know yet what a real use case for this app could be. Anyway, hope someone will find it useful. Tested on a wm6 prof. device.
With 'Scale' the bars drawing height of the bars can be changed.
With 'Rate (ms)' the length (in milliseconds) of the audio sample can be changed.
Info
In case there are no bars visible, change the rate to > 400ms. (thanks nir36)
The measured values are not dB! Will be changed in the app (when some additional features will be implemented).
v1.1
select different channels if available
show bps
v1.2
auto volume setting (measures loudness every x minutes and adjusts the ringing volume)
Thanks,
heliosdev
this could actually help me with my studies.. thank you
What units is the maximum shown in?
The values are in dB and calculated using the root mean square on the audio data.
If x is the array with the audio data then it is
value = sqrt(1/n * sum(x1*x1+x2*x2+...+xn*xn))
Not sure if there is some 'magic' factor in the audio data, it's just an array of bytes.
heliosdev said:
The values are in dB and calculated using the root mean square on the audio data.
If x is the array with the audio data then it is
value = sqrt(1/n * sum(x1*x1+x2*x2+...+xn*xn))
Not sure if there is some 'magic' factor in the audio data, it's just an array of bytes.
Click to expand...
Click to collapse
how can that be that it is in dBs? the highest value I've gotten is around 2, normal sound would be 60+ atleast...
I'm getting values around 80 when playing some music or watching tv and holding the phone close to the speakers. I'll need to write some more info into a log file to find out the reason why you only get small values.
heliosdev said:
I'm getting values around 80 when playing some music or watching tv and holding the phone close to the speakers. I'll need to write some more info into a log file to find out the reason why you only get small values.
Click to expand...
Click to collapse
sounds good, I'll keep an eye here and keep testing for you...
Is there a chance that you could put Shannon's formula inside this thing?
(that is, B*log(1+s/n)) to check the bandwidth used and the bps transfered each sec?
A great use for this would be to automatically turn up (or down) the in-call volume if there's a lot (or very little) of background noise.
Zoltair Wright said:
A great use for this would be to automatically turn up (or down) the in-call volume if there's a lot (or very little) of background noise.
Click to expand...
Click to collapse
Agree! this could be a great use
It doesn't work on my AT&T Fuze
nir36 said:
Is there a chance that you could put Shannon's formula inside this thing?
(that is, B*log(1+s/n)) to check the bandwidth used and the bps transfered each sec?
Click to expand...
Click to collapse
The bps is calculated now. I'm not quite sure if the time (rate in ms) should be taken also in this calculation. Currently it isn't. Should this bps be multiplied by (recording time in ms / 1000)?
Btw, the used Bandwidth is 11025Hz.
pandaboyy said:
It doesn't work on my AT&T Fuze
Click to expand...
Click to collapse
Can you try again with the latest version and see if it works when changing the channel?
Zoltair Wright said:
A great use for this would be to automatically turn up (or down) the in-call volume if there's a lot (or very little) of background noise.
Click to expand...
Click to collapse
That could be useful. And this app could start when an incoming call starts, adjust the volume and close again.
Plenty of uses!
Very cool indeed! I can think of lots of uses..including my kids and the neighbors! Actually, I have some clinical applications for this little beauty!
Thank you so much!!
heliosdev said:
Noise Tracker
Noise Tracker measures the loudness ... hope someone will find it useful
Click to expand...
Click to collapse
heliosdev, you can build a app to play a mp3 file when someone claps or whistle
(I'm not joking, you can find your phone that way...)
Seriously cool, thanks for the app! As others mentioned, if you could add a function where this thing could call or be called by opther programs it could be hugely useful. How about sampling the background noise every 15 min or so and adjusting the ring volume so I don't miss calls in noisy places or get a heart attack when someone calls me while I'm in bed reading a book. If it's sensitive enough it could be used to bug a room, when voices are detected it starts the voice recorder...etc., etc. TONS of possibilities!!
P.S. ff2005, try calling your phone if you can't find it
That would be nice! Right now I can tell you that such a feature is scheduled for April 1st!
ff2005 said:
heliosdev, you can build a app to play a mp3 file when someone claps or whistle
(I'm not joking, you can find your phone that way...)
Click to expand...
Click to collapse
New version is up which sets the ringing volume. This needs to be tested because I haven't a second phone to call myself.
It takes the current loudness l and sets the ringing volume to:
l > 70 -> 5
l > 50 -> 4
l > 30 -> 3
l > 10 -> 2
else -> 1
I'm setting the registry value
CurrentUser\ControlPanel\SoundCategories\Ring\InitVol
Zoltair Wright said:
A great use for this would be to automatically turn up (or down) the in-call volume if there's a lot (or very little) of background noise.
Click to expand...
Click to collapse
orb3000 said:
Agree! this could be a great use
Click to expand...
Click to collapse
mlalahoi said:
Seriously cool, thanks for the app! As others mentioned, if you could add a function where this thing could call or be called by opther programs it could be hugely useful. How about sampling the background noise every 15 min or so and adjusting the ring volume so I don't miss calls in noisy places or get a heart attack when someone calls me while I'm in bed reading a book. If it's sensitive enough it could be used to bug a room, when voices are detected it starts the voice recorder...etc., etc. TONS of possibilities!!
P.S. ff2005, try calling your phone if you can't find it
Click to expand...
Click to collapse
It works on my xda flame.
Should be useful as or detector of noise: do something when the level is over a value, or when the level is below a value (end of noise)
I dont see a similar thread to do this after searching so im starting a new one
*Root is required for this method*
Browse to data\data\com.sec.android.app.camera\shared_prefs
The folder has one .xml file, open it with text editor
Look for <int name="pref_setup_shuttersound_key" value="1" />
Change the value to 0 and its done, enjoy!
Actually this is in the camera settings normal users are able to disable shutter sound
yanchenglee said:
Actually this is in the camera settings normal users are able to disable shutter sound
Click to expand...
Click to collapse
Maybe your rom can but mine couldnt
Hongkong's Gingerbread/Froyo doesnt allow this function
You can only choose one of three shutter sound, theres no "silent" button
The sound file is bound to apk too
You can also delete/rename the shutter sound from system/media/audio/ui, i do this in all the roms i use. Its easier than editing xml.
Ya maybe it's illegal to turn off shutter sound in Hong Kong I understand
yanchenglee said:
Ya maybe it's illegal to turn off shutter sound in Hong Kong I understand
Click to expand...
Click to collapse
Don't know about Hong Kong in Japan the iPhone doesnt have the option to disable shutter sound xD
http://www.quickonlinetips.com/arch...hone-makes-loud-shutter-sound-in-silent-mode/
OnTopic: I'm a big fan of Tasker so I disabled the sound using it:good:
Its because it can be ilegal in some countries
Sent from my GT-S5660 using xda premium
What about to take picture in silent mode? Easiest way to do that
yanchenglee said:
Ya maybe it's illegal to turn off shutter sound in Hong Kong I understand
Click to expand...
Click to collapse
Hey im from Hong Kong too
Sent from my GT-S5830 using xda premium
tnuh said:
What about to take picture in silent mode? Easiest way to do that
Click to expand...
Click to collapse
Screen Capture?
Then whats the point of 5MP camera:angel:
I working on a rom and while modding the settings.apk I found a value in arrays.xml
<string-array name="wifi_htc_sleep_policy_entries">
<item>After 15 min</item>
<item>Never when plugged in</item>
<item>Never</item>
Would it be possible to stop wifi disconecting when screen off, if i manage to add this into the settings?
---
parrotgeek1 said:
don't have this device, but could someone try decompilng framework-res.apk and go to res/values/config.xml and add these
Code:
<!-- Is the notification LED intrusive? Used to decide if there should be a disable option -->
<bool name="config_intrusiveNotificationLed">true</bool>
<!-- Is the battery LED intrusive? Used to decide if there should be a disable option -->
<bool name="config_intrusiveBatteryLed">true</bool>
<!-- Does the battery LED support multiple colors? Used to decide if the user can change the colors -->
<bool name="config_multiColorBatteryLed">false</bool>
<!-- Default color for notification LED is white. -->
<color name="config_defaultNotificationColor">#ffffffff</color>
Of course you can change config_defaultNotificationColor to any html color in lowercase, but start with white for testing.
Then download lights.shamu.so from aosp (one that supports notifications afaict)
https://android.googlesource.com/device/moto/shamu/+archive/master/liblight.tar.gz extract the tgz
and put the .so in /system/lib/hw (replace the old one)
then recompile framework-res DON'T SIGN IT! or use a kitchen and reflash
reboot go into notification settings and turn the lights on
it COULD also enable the green battery charging led natively, idk
Click to expand...
Click to collapse
Didn't work... I see the option for "Pulse Notification Light" and it's enabled but it doesn't light up when I try to text myself and receive the message with the screen off.
1. There is no config.xml.
2. I modified the bools in bools.xml and the color in colors.xml (no modification needed for colors).
parrotgeek1 said:
don't have this device, but could someone try decompilng framework-res.apk and go to res/values/config.xml and add these
Code:
<!-- Is the notification LED intrusive? Used to decide if there should be a disable option -->
<bool name="config_intrusiveNotificationLed">true</bool>
<!-- Is the battery LED intrusive? Used to decide if there should be a disable option -->
<bool name="config_intrusiveBatteryLed">true</bool>
<!-- Does the battery LED support multiple colors? Used to decide if the user can change the colors -->
<bool name="config_multiColorBatteryLed">false</bool>
<!-- Default color for notification LED is white. -->
<color name="config_defaultNotificationColor">#ffffffff</color>
Of course you can change config_defaultNotificationColor to any html color in lowercase, but start with white for testing.
Then download lights.shamu.so from aosp (one that supports notifications afaict)
https://android.googlesource.com/device/moto/shamu/+archive/master/liblight.tar.gz extract the tgz
and put the .so in /system/lib/hw (replace the old one)
then recompile framework-res DON'T SIGN IT! or use a kitchen and reflash
reboot go into notification settings and turn the lights on
it COULD also enable the green battery charging led natively, idk
Click to expand...
Click to collapse
Hey so I tried by baking it into my AOSP build. ( config_multiColorBatteryLed is not in the XSD so i did not include that) Nothing so far. Good thought! Im going to keep looking, at least I was able to add allow All Rotation to my build .
There is no ledtrig heartbeat trigger included and stock kernel does not support loading modules
.
parrotgeek1 said:
Please elaborate.... what's a heartbeat trigger
Click to expand...
Click to collapse
Well to put simply, it's the method that causes the LED's to flash like a heartbeat. (From what I can remember).
ie. OFF - - - ON OFF ON OFF - - - ON OFF ON OFF (so on and so forth).
The way Linux led works in nutshell as i understand it from my quick research is either setting brightness level manually (slow and unreoiable, better to be done at low level) or setting max brightness and setting appropriate trigger kernel module, e.g. set trigger to none to disable or mmc0 to blink to indicate card write activity and so on, ledtrig_heartbeat used to pulse the led and it is not an option in our triggers in nexus 6 (not in kernel) and without modules support we can not load it.
So just enabling led string would not be enough to get pulse notifications. Waiting for custom kernels.
Take a look http://fabiobaltieri.com/2011/09/21/linux-led-subsystem/
So, its working for me. What I did was just used light flow. I enabled root mode, then I enabled run every command as root, then I enabled direct mode. Then I had to choose the correct led for it to use in the other menu and when I ran the test it came on.
Xileforce said:
So, its working for me. What I did was just used light flow. I enabled root mode, then I enabled run every command as root, then I enabled direct mode. Then I had to choose the correct led for it to use in the other menu and when I ran the test it came on.
Click to expand...
Click to collapse
I believe the goal here is to have led notifications natively, without an app running in the background constantly.
Roger that, sorry wasn't sure, figured I would share just to be safe
The source is available, why not just compile a kernel with module support?
Random mutterings...
Note: I don't have a personal build environment set up at the moment, so it's really difficult for me to check these things properly.
# should already be set
CONFIG_LEDS_QPNP=y
CONFIG_LEDS_TRIGGERS=y
CONFIG_LEDS_TRIGGER_DEFAULT_ON=y
Using these, it's already possible to, for example, activate a charging LED. (echo battery-charging-or-full > /sys/class/leds/charging/trigger) Where is the kernel support for those charging related triggers? Not finding it in drivers/leds/trigger, but it might be specific to a charging chip? No build environment means no grepping code for the strings...
# not set, but why not? does QPNP not support it?
#CONFIG_LEDS_TRIGGER_TIMER is not set
A "timer" trigger is one of the methods to create a blinking LED. (not heartbeat) the ONESHOT might also be useful. FYI, the heartbeat trigger is documented in the kernel as:
This allows LEDs to be controlled by a CPU load average. The flash frequency is a hyperbolic function of the 1-minute load average.
Click to expand...
Click to collapse
How are the triggers configured for hammerhead or perhaps for a motoX device, and how is that different from shamu? As well as kernel support, there needs to be liblights.so support for the kernel parameters, JNI support, and JAVA support. Some or all of these might already exist. Not sure yet.
The "three" LED's (red/green/blue) in shamu are configured as GPIO devices (see apq8084-shamu.dtsi.) In leds-qpnp.c, blink_store(), an ID of 8 (GPIO) will result in an error. Does that matter? If they are GPIO devices, why not configure them with leds-gpio instead of leds-qpnp?
In contrast, the "charging" LED in shamu (defined in apq8084-moto-common.dtsi, I think) appears to set up differently (MPP?) and should support blink types (that does work, actually.)
...
Why is the "charging" LED handled so differently from the 3 color LED? If I'm going to mess with the LED's, I'm going to get them blinking the way they should, dammit.
What is the disconnect between the kernel (which, at the very least, supports a charging LED properly) and the rest of android? It's been several years (i9300 -- galaxy S3?) since I've messed with the LED code in android...
Odd: there's no source for liblights.so in the shamu code device tree (just a compiled lib), but there IS source for liblights for other platforms (if there's any lib at all.) Not sure I've ever seen the LED stuff being considered a proprietary blob (especially when it's kernel driven and the kernel source is all intact.)
You know your losing your mind when you start excessively replying to yourself in forum threads. It's worse when you have to re-learn something you were very familiar with just a few years ago.
android notification system uses LightsService for various LED related stuff. (This includes the screen lighting.) LightsService relies on some jni code (com_android_server_lights_LightsService.cpp) to interface to the liblights library. The JNI module is tiny, and really doesn't need to be mucked with. However, it's a really nice place to put logging code. The JNI only has three methods: init_native(), finalize_native(), and setLight_native().
The init is called for each type of LED "device". they are backlight, keyboard, buttons, battery, notifications, attention, bluetooth and wifi. Add logging code here to see which ones are returning a valid pointer, and which ones aren't. (I'm guessing that only backlight is being returned. I hope I'm wrong, but if I'm not, then lights.shamu.so will have to be re-written from scratch to support the other device types.)
The only other interesting place will be in setLightnative(). This takes a crapload of parameters, which are all packed down to a light device pointer and a "state" structure. These are passed to the native (lights.shamu.so) code for processing. Adding logging here might be useful. It also might not be (depending on if the damn light initializes or not.)
Why does this all seem so damn familiar to me? (because I've done it before and managed to forget most of it.) (hopefully, by typing all this, I'll be able to find it again in the future via google searches.)
I was getting bored, so figured I'd reply to myself. Again.
It appears that lights.shamu.so is the base of the problem. (There might be other issues, of course, but one of the ways to dig these things out is to start at the lowest level and work your way up...)
Kernel: has support
sysfs supports (if somewhat limited)
The next layer is liblights.so (or, in this case, lights.shamu.so.) The ONLY "light" that this lib seems to support is "backlight." The following all give errors: "keyboard", "buttons", "battery", "notifications", "attention", "bluetooth" and "wifi"
I am curious what the "battery" light type is. Is that designed to be the charging LED, or have some other purpose within android? Will need to check that out...
Anyway, I'll whip up a "lights.shamu.so" replacement and see what happens with that..
hrmm.. I've never seen this before:
Code:
E/HAL ( 957): load: module=/system/lib/hw/lights.shamu.so
E/HAL ( 957): dlopen failed: empty/missing DT_HASH in "lights.shamu.so" (built with --hash-style=gnu?)
Of course, the obvious thing would be to edit device/moto/shamu/liblight/Android.mk and add "LOCAL_LDFLAGS := --hash-style=both", but that's giving me a compiler error:
Code:
arm-linux-androideabi-g++: error: unrecognized command line option '--hash-style=both'
Now, why is an LD flag being passed to the c++ compiler and not to the linker? For that matter, why is it using g++ instead of gcc? hmm... This should be easier than this.
I figured I should thank you for doing all these
garyd9 said:
hrmm.. I've never seen this before:
Code:
E/HAL ( 957): load: module=/system/lib/hw/lights.shamu.so
E/HAL ( 957): dlopen failed: empty/missing DT_HASH in "lights.shamu.so" (built with --hash-style=gnu?)
Of course, the obvious thing would be to edit device/moto/shamu/liblight/Android.mk and add "LOCAL_LDFLAGS := --hash-style=both", but that's giving me a compiler error:
Code:
arm-linux-androideabi-g++: error: unrecognized command line option '--hash-style=both'
Now, why is an LD flag being passed to the c++ compiler and not to the linker? For that matter, why is it using g++ instead of gcc? hmm... This should be easier than this.
Click to expand...
Click to collapse
I believe in you Gary! Seriously though thanks for taking the time to work on this.
I appreciate the support, but I hope everyone remembers that I have a full time job that takes priority. That generally means that most of my android "fun" work gets deferred during the working week.
The task will get done, but please be patient...
Take care
Gary
We definitely appreciate everything you and the other devs do! I'm very much enjoying the AOSP Email! I did not want to use Gmail for my work email. I know it might have some benefits but I just needed the basic email app so that was very much appreciated!
So apparently the 1 III suffers from the same issues as its Sony Predecessors... The Flashlight is very bright when you use it as camera flash, but when you turn on the flashlight, its artifically throttled to idk, prevent overheating?
So for the older Xperias there were ways to modify flashlight configs and librarys. However, I havent found a way to edit the current parameter for the flashlight on the 1 III. For the 5 II the GodlyTorch App seemed to work, according to a report in https://forum.xda-developers.com/t/...ness-fix-torch-light-not-photo-flash.4203293/, but that doesnt want to work on my 1 III (I have Root)
Now the question: Can someone find the parameters to increase Flashlight LED Current via Magisk Module, XPosed/LSPosed Module or manual edit? I'd be even willing to donate to a kind developer who builds a usable flashlight mod for the 1 III.
Thanks in advance.
When flashlight is on and your device is rooted, you can change the value of
Code:
/sys/class/leds/led:torch_0/brightness
/sys/class/leds/led:torch_3/brightness
(There are two flash LEDs)
The max value you can set is given by the max_brightness file in the same directory.
I didn't find a way (yet) to apply this by default, you have to have the flashlight running in order to change its brightness that way.
However, I do warn you that I am not responsible in any way if using your LED at full power causes damage to your device.
MK73DS said:
When flashlight is on and your device is rooted, you can change the value of
Code:
/sys/class/leds/led:torch_0/brightness
/sys/class/leds/led:torch_3/brightness
(There are two flash LEDs)
The max value you can set is given by the max_brightness file in the same directory.
I didn't find a way (yet) to apply this by default, you have to have the flashlight running in order to change its brightness that way.
However, I do warn you that I am not responsible in any way if using your LED at full power causes damage to your device.
Click to expand...
Click to collapse
Thanks for this info, working fine for me!
I played a bit around with this and tested the brightness values with 150; working fine in terms of short term heat development.
Edit 2: After a few days I start to notice a very slight discoloration of the diffusor with a value of 150. Its not affecting anything and barely visible, but I'd recommend to go lower than 150, because I suspect the LED may get too warm for the diffusor. I changed the guide to use 30 for now (which equals double the brightness compared to stock), please test your values for yourself, its probably better to not exaggerate it.
Make sure you type in the values right! Too high values and the LED Diffusor may melt, or the LED might die. Do this modification at your own risk, no matter at which brightness you target! I am not responsible for side effects resulting from the mod.
With Terminal Shortcut Pro and assigned Root Priviliges I made myself a Home Screen Icon that will boost the values for me in the current "Torch session" once the LED is turned on before. Other terminal emulator apps will work too.
In the Shortcut I set Run with Root and used the following command
Code:
echo 30 >> /sys/class/leds/led:torch_0/brightness && echo 30 >> /sys/class/leds/led:torch_3/brightness
Basically just a command that writes the 30 brightness value to the 2 files.
If someone can find a terminal command that turns on the flash in the first place, we could combine the commands to potentially make a simple but working replacement quick settings for the torch.
Edit: Thanks to the XDA Community and a Tool I was able to recreate the Torch experience with a Quick setting
You need https://play.google.com/store/apps/details?id=com.quinny898.app.customquicksettings
You have to buy the premium in app purchase for 1,29€ to unlock Root Command Running. Then you configure your quick setting (choose the Advanced -> Root Command under Preset) and paste the following script (credits to https://forum.xda-developers.com/t/increasing-torch-power-with-root.3637773/post-73098701, modified by me for 1 III)
Code:
#!/system/bin/sh
toggle=$(cat /sys/class/leds/led:switch_0/brightness)
if [ "$toggle" = "0" ];then
echo 30 > /sys/class/leds/led:torch_0/brightness
echo 30 > /sys/class/leds/led:torch_3/brightness
echo 1 > /sys/class/leds/led:switch_0/brightness
echo "on"
else
echo 0 > /sys/class/leds/led:torch_0/brightness
echo 0 > /sys/class/leds/led:torch_3/brightness
echo 0 > /sys/class/leds/led:switch_0/brightness
echo "off"
fi
Once again, make sure you type in the values right! Too high values and the LED Diffusor may melt, or the LED might die. Do this modification at your own risk, no matter at which brightness you target! I am not responsible side effects resulting from the mod.
Then you get rename the toggle, give it a nice Torch Icon and set the color to grey. It will function like the normal quick setting: Tap once, it turns on, Tap again, turns off. Even works locked.
Good luck and best regards.
If you want to use the Google Assistant Button as a torch toggle and also have Quick Settings Toggle (sadly its always toggled on) i found an app that can do both.
You need:
LSposed/Xposed
Root Shell access (adb shell)
Xposed Edge pro
Busybox for Android NDK (Magisk Module)
XperiaGAButtonRemap (Magisk Module)
Open a cmd or powershell
execute adb shell
execute su
accept root permissions on your phone
execute vi /bin/torch
press the key i
paste the script:
einhuman197 said:
Code:
#!/system/bin/sh
toggle=$(cat /sys/class/leds/led:switch_0/brightness)
if [ "$toggle" = "0" ];then
echo 150 > /sys/class/leds/led:torch_0/brightness
echo 150 > /sys/class/leds/led:torch_3/brightness
echo 1 > /sys/class/leds/led:switch_0/brightness
echo "on"
else
echo 0 > /sys/class/leds/led:torch_0/brightness
echo 0 > /sys/class/leds/led:torch_3/brightness
echo 0 > /sys/class/leds/led:switch_0/brightness
echo "off"
fi
Click to expand...
Click to collapse
press ESC
type :wq and press ENTER
execute chmod +x /bin/torch
Now you can execute /bin/torch as root and it will toggle the torch with higher brightness values.
In Xposed Edge enable "Keys" toggle and open it. Tap on "+ Add" at the bottom, press the Google Assistant Button, it should be recognized as "KEYCODE_PROG_BLUE", then set the action of either click/double click/long press (whatever you prefer as the torch toggle) to execute a Shell command, enter /bin/torch in the input field and enable the "Root access" toggle.
If you want, you can also set other custom things to the Google Assistant button for the other 2 states.
For the quicksettings menu tap on "Quick settings tiles" in the main menu of Xposed Edge and enable the first tile and open the settings for that tile. Set the action, again, to a shell command, input /bin/torch and enable Root Access. You can set the label to "Torch" and choose the Torch icon found in "Built-in icons". As i already said, the toggle will always be turned on for some reason. It just executes a shell command after all.
Good luck
Amazing, thank you everyone.
However, please let me insist that this may damage your phone if you put values too high... trust me. I accidentally put a brightness of 350 instead of 150 while trying the script in a terminal, and a few seconds were enough for the plastic underneath the glass to melt... Thankfully, it is still transparent so I can still use my flashlight, but no doubt it could have done a lot more damage if I let it run for longer. So please, use this with a lot of care (and double check what you write).
That's why in lots of countries, rooting voids your (hardware) warranty, you can do physical damage to your device so again, please be careful. Thankfully, this plastic bit and even the LED underneath are easily replaceable (the plastic bit is separated from the rear glass and the LED is on a separate ribbon cable). However, there don't seem to be a lot of OEM replacement parts for this phone yet.
Seems like a lot of work for little return and added threat of damage to an expensive phone. I agree that the brightness is dimmer than other phones I have had...but I did a test in a completely dark room and it actually is bright enough to find "whatever" you may be looking for. So I can live with it. Maybe Sony will do something to improve it a little?
jaseman said:
Seems like a lot of work for little return and added threat of damage to an expensive phone. I agree that the brightness is dimmer than other phones I have had...but I did a test in a completely dark room and it actually is bright enough to find "whatever" you may be looking for. So I can live with it. Maybe Sony will do something to improve it a little?
Click to expand...
Click to collapse
Sony could definitely improve it. But it seems like they had a history for compareably dim Flashlights.
I edited my explanation post to adapt lower brightness, because 150 as value starts to slightly discolor my diffusor, so I suspect we should run it lower.
MK73DS said:
太棒了，谢谢大家。
但是，请让我坚持，如果您将值设置为高，这可能会损坏您的。......我相信在终端中尝试手机时，我不小心将恢复设置为 350 而不是 150 ，几秒钟就可以让玻璃下面的恢复正常……幸好还是可以的，所以我可以使用我的手电筒，但有疑问，如果我能运行更长时间，它会请小心使用它（并仔细检查你写的内容）。
这就是为什么在国家/地区，root 导致您的许多（硬件）故障，您可能会再次对您的设备造成物理损坏，请小心。值得庆幸的是，塑料钻头甚至下面的 LED 都可以轻松更换（塑料钻头与后玻璃分离，LED 还位于单独的带状电缆上）。
Click to expand...
Click to collapse
darken5404 said:
Click to expand...
Click to collapse
You can't say I didn't warn you!
Indeed flashlight in mark 3 and older xperias is very bad.
I compared it to an iPhone and it's like day and night. Many aspects xperia brand is suffering like front camera, flashlight, no 21:9 pics, missing 4k 60fps recording in main app with stabilization, poor screen brightness, insufficient battery capacity, no any cooling system (especially at this price there should be vapor chamber or any other advanced cooling and not throttling cpu as a solution...), Not to mention regular software apps like Album, email and others :/
MK73DS said:
You can't say I didn't warn you!
Click to expand...
Click to collapse
I got it fixed through sony aftermarket and has ip68,fixed the screen for me by the way
On android 12 after rebooting the function stops working.
So I got to the area of the phone you guys specified, but as of today, the default values are WAY different that what yall found. Let me take a few screen shots
Here is the systems default peramitors. Any idea why they are so different?
Edit- Okay, so extra piece to the puzzle. When torch is off, the brightness file is 0, but when it is on the file is set to 15.
editing the file while the torch is on does nothing.
Edit 2 - Just wanted to note that for those who just want a demonstration of the changes possible, the fallowing app will do just that
Release v1.4.6 · BRoy98/GodlyTorch
Merge pull request #2 from TheDorkKnightRises/patch Fix LED file path for OnePlus One (bacon), proper device names for OP Merge pull request #3 from TheDorkKnightRises/patch Fix default double-...
github.com
this app needs root. Run it as a HTC 10 and it works just fine. However, I would like to recommend NOT going over the half way point. its VERY bright and will probably kill your LED if you do. You have manual control over the brightness. You can add it as a shortcut in the drop down menu of your phone. simply use the standard torch button, and then click the godly torch button to activate whatever preset you gave it.
Edit 3 - setting the brightness in Godly Torch to 50% Intensity sets the brightness to 135. Given that we know damage starts to happen at 150, I set the brightness in Godly to 15% (under the "toggle Intensity" shown in the screen shot), which brings the brightness to a value of 45. Its easily double as bright. I would not recommend going past this point.
I would say by using godly torch as a HTC 10 worked...mind you I double checked the brightness by just hitting the quick toggle and then messing with godly torch. The lower setting is matching just turning on the quick toggle the higher setting is what I'm comfortable with, but idk how long I'm comfortable running it at that brightness.
BlazingKahn35 said:
On android 12 after rebooting the function stops working.
Click to expand...
Click to collapse
For those on stock who use the assistant button :
If it stops working after reboot, copy the binary file to somewhere safe on your sd card, then using XPosed edge just add a long press gesture to your assistant button that recopys the file from your sd card, then sets the permissions again (make sure to check run as root)
cp /sdcard/torch /bin/ | chmod +x /bin/torch