I've compiled a stock 2.1 ROM and copied the proprietary files from a working 2.1 build to the ROM i'm working on, including the files for lights and sensors. So far the camera, bluetooth, wifi, sounds and softkey lights don't work. I'm building this for the eris. I have the lights.msm7k.so and the camera libs and all the bluetooth and wifi files i can find. My main concern is the sound and softkey lights, everything else i can probably figure out eventually but the sounds and lights are stumping me completely. Does anyone have some type of list of files for sounds or is there something else required for the lights and sound to work?
Related
Is it possible that when i receive an sms / text message the top LED starts to flicker instead of the bottom one? I'm really looking to this as i find it more convenient that the top one starts to flicker.
Does anyone have the answer?
Well I don't know how you go about setting it, or even if you can, but they do work, depending on what ROM you use. If you use a Sense ROM then the LED will blink fine. On Vanilla ROMs they won't. With some of the older AOSP ROM's around you used to get a static LED, amber/green for sms/gmail notifications. With the latest CyanogenMod based ROMs you don't get anything. Only the trackball pulses, which is cool.
However, Elemag has claimed to have the LEDs working on his new ROM - http://forum.xda-developers.com/showthread.php?t=708673
I can't get my led notification to work in any SC 2.X
I know that led control is supported by kernel.
I'm currently on SC 2.8, I tried all the led control app from the market but still a no-go.
Anyone found a way around this?
If by LED control, you mean Backlight Notifications, where the soft keys light up on certain events, then no. We don't have kernel sources so we can't build a kernel with BLN built-in to do so.
The Fascinate doesn't even have an LED (I WISH!!)
deaffob said:
I know that led control is supported by kernel.
Click to expand...
Click to collapse
That's your problem.
We don't have the source code for this rom yet, so this no BLN or high fidelity audio fix from super curio...
misses my voodoo sound fix :-/
Hello
Can anyone please tell me how to disable the camera shutter sound, and the vibration when the battery is full?
bump..........
Not sure you can on a standard ROM but if you pick one of the many custom ROMs out there most already have these set in.
I'd recommend CM7 or Cognition for the more standard look
http://forum.xda-developers.com/showthread.php?t=1124396
If you don't want to install a custom ROM, as long as you're rooted you can disable these sounds by installing ES File Explorer, navigating to the audio files for the Camera shutter and battery notification sound, and renaming them. This prevents the Android OS from calling them.
Instructions in here for the battery notification: http://forum.xda-developers.com/showpost.php?p=17932560&postcount=11 Use the same instructions for the camera shutter but confirm the right file name.
Hope this helped.
Well thankyou for your suggestions, but what does ROM mean? And what does rooted mean?
I have read that a custom ROM is like a custom operating system. I have come across CM7 before when looking for a way to have lock screen gestures.
I still don't know what rooting is. Is that much safer than custom ROMs?
How does any of this affect my warranty?
This appears to be a novice's rooting guide:
http://forum.xda-developers.com/showthread.php?t=1103399
Would that be suitable for me?
lemon2 said:
I have read that a custom ROM is like a custom operating system. I have come across CM7 before when looking for a way to have lock screen gestures.
I still don't know what rooting is. Is that much safer than custom ROMs?
How does any of this affect my warranty?
This appears to be a novice's rooting guide:
http://forum.xda-developers.com/showthread.php?t=1103399
Would that be suitable for me?
Click to expand...
Click to collapse
Hey lemon,
Check out this post here for good basic information about rooting and ROMs etc.:http://forum.xda-developers.com/showthread.php?t=1246131
brahmy said:
If you don't want to install a custom ROM, as long as you're rooted you can disable these sounds by installing ES File Explorer, navigating to the audio files for the Camera shutter and battery notification sound, and renaming them. This prevents the Android OS from calling them.
Instructions in here for the battery notification: http://forum.xda-developers.com/showpost.php?p=17932560&postcount=11 Use the same instructions for the camera shutter but confirm the right file name.
Hope this helped.
Click to expand...
Click to collapse
Works perfectly.
rename cam_start, cam_stop for video.
Slightly off topic but i want to share that my UK model sgs2 on stock ki4 rom 2.3.4 has silent camera when the phone is in silent mode
Sent from my GT-I9100 using Tapatalk
Sorry, but am having difficulty locating those two files.. cam_start & cam_stop? which folders are they in?
the file location is /system/media/audio/ui deletes all files containing camera, shutter, alnd video recording, in total 6 files
Using a file explorer (such as Root Explorer), Create a file in /data called local.prop and add the line "ro.camera.sound.forced=0". Now restart your phone.
This removes both the shutter and focus sounds when your phone is on silent, but keeps the sound when it's not on silent.
To disable full battery vibration, it requires decompiling SystemUI.apk and editing code.
http://forum.xda-developers.com/showthread.php?t=1234738
Using a file explorer (such as Root Explorer), Create a file in /data called local.prop and add the line "ro.camera.sound.forced=0". Now restart your phone.
This removes both the shutter and focus sounds when your phone is on silent, but keeps the sound when it's not on silent.
To disable full battery vibration, it requires decompiling SystemUI.apk and editing code.
Click to expand...
Click to collapse
I have changed this setting, restarted, confirmed it is still there with no typo's and still this makes the auto-focus sound with all volume levels of media, system etc on silent.
the file location is /system/media/audio/ui deletes all files containing camera, shutter, alnd video recording, in total 6 files
Click to expand...
Click to collapse
Can you please advise specifically which 6 files these are, as I have renamed all of the ones I can see that are relevant yet still have the autofocus sound.
I have previously had a camera.apk provided from this forum which had the autofocus sound disabled and the 15% battery limit that stopped recording removed, however I have recently upgraded to 2.3.5 (stock) and this APK no longer removes this annoying focus sound.
With all the files that I've renamed already I've stopped every sound other than the one. Please help
So I'm using the CM11 4.4 Kitkat on my Galaxy S4 and recently found out that my proximity sensor isn't working (when I dial the screen goes black and won't turn on until the call is over). I've read many threads about fixing it but I think it's broken. So all I want now is to disable it but there isn't such option in the Cyanogenmod. Is there anyway to disable it, like with a terminal or something?
bump
bump!
with root explorer go to system/lib/hw and go all the way to the bottom to the last sensors file. its an so file. long press on it and open in text editor. somewhere in the page almost at the bottom you will see where it says ProximitySensor then on one of those line it should say mEnabled. just rename it to mDisabled, then reboot and the proximity sensor is fixed.
qman66 said:
with root explorer go to system/lib/hw and go all the way to the bottom to the last sensors file. its an so file. long press on it and open in text editor. somewhere in the page almost at the bottom you will see where it says ProximitySensor then on one of those line it should say mEnabled. just rename it to mDisabled, then reboot and the proximity sensor is fixed.
Click to expand...
Click to collapse
I know this is an old thread but qman66 you are AWESOME! Was going nuts trying to fix the proximity sensor problem. Ran the commands in terminal emulator that recalibrates the sensor, didn't work for me. Blasted the speaker with compressed air, also didn't work for me. But this method allowed me to disable the proximity sensor while still using an AOSP rom. I will send the phone in for warranty eventually, but I thought I was going to have to use a touchwiz rom until then (touchwiz has the option of disabling the proximity sensor in the call menu).
And I read like 5 or 6 different threads dealing with the Galaxy S4 proximity sensor issue and no one else posted this method before.
kg2128 said:
I know this is an old thread but qman66 you are AWESOME! Was going nuts trying to fix the proximity sensor problem. Ran the commands in terminal emulator that recalibrates the sensor, didn't work for me. Blasted the speaker with compressed air, also didn't work for me. But this method allowed me to disable the proximity sensor while still using an AOSP rom. I will send the phone in for warranty eventually, but I thought I was going to have to use a touchwiz rom until then (touchwiz has the option of disabling the proximity sensor in the call menu).
And I read like 5 or 6 different threads dealing with the Galaxy S4 proximity sensor issue and no one else posted this method before.
Click to expand...
Click to collapse
glad someone found this useful.
While this fixed the call locking problem, it also disables a lot of other hardware sensors. The only one I'd care about is the gyroscope for rotating the camera and watching videos full screen. Any solutions?
sjschoo said:
While this fixed the call locking problem, it also disables a lot of other hardware sensors. The only one I'd care about is the gyroscope for rotating the camera and watching videos full screen. Any solutions?
Click to expand...
Click to collapse
Yeah I noticed that, the best solution is to get the proximity sensor fixed in the end. Then you don't have to disable anything. If your lucky it doesn't even need to be replaced, just cleaned. For me I can live with no rotation, because the screen off during calls is a ridiculous PITA by comparison. Also apps can force landscape mode even with the gyroscope not working. I use force landscape for videos through mx player, and mango reader for manga.
I finally broke down and took the phone apart. There were no warranty stickers to break so assuming you don't mess up royally, it shouldn't effect your resale value. All it took was an eye glass screw driver and a q-tip. Once I was inside I tried the can of air first, but didn't help. Swabbed the back of the glass with the q-tip and that finally provided lasting relief.
i9100 proximity sensor doesn't work
Hi to all!
I have the issue with proximity sensor and didn't manage to find a solution in other similar threads!
The matter is that it is always stay as Released.
In the same time in test screen (*#0*#) there are changing reading for PROXIMITY parameter from 2 up to 240 with no ADC parameter at all. Please look for screenshots. PROXIMITY parameter changes its value when I move my finger in front of the sensor, but as I can understand Android doesn't recognize it because of ADC absence.
Moreover I tried to change proximity sensor for working one (from another phone), but it shows the same as mine (with no ADC readings).
After all I think it is software problem, but I don't know how to solve it. I flashed different firmwares (now it is XWMSE NeatROM v.6.4), but nothing helped.
Please assist! Thanks!
khudko83 said:
Hi to all!
I have the issue with proximity sensor and didn't manage to find a solution in other similar threads!
The matter is that it is always stay as Released.
In the same time in test screen (*#0*#) there are changing reading for PROXIMITY parameter from 2 up to 240 with no ADC parameter at all. Please look for screenshots. PROXIMITY parameter changes its value when I move my finger in front of the sensor, but as I can understand Android doesn't recognize it because of ADC absence.
Moreover I tried to change proximity sensor for working one (from another phone), but it shows the same as mine (with no ADC readings).
After all I think it is software problem, but I don't know how to solve it. I flashed different firmwares (now it is XWMSE NeatROM v.6.4), but nothing helped.
Please assist! Thanks!
Click to expand...
Click to collapse
Changing the rom isn't going to do anything, even factory roms (I've tried it). If a replacement sensor doesn't fix it for you, then it's going to be hard to fix it yourself. All the posts I've seen so far have cleaned the sensor or replaced the sensor and fixed the problem. Otherwise people like me just turn the sensor off.
You were right, proximity software fix didn't help! But how is it possible to work in this (the same wrong) way with changed sensor? Can it be some main board hardware problem? But it doesn't look like this...
Sent from my GT-I9500 using XDA Premium 4 mobile app
Maybe somebody knows how to fix the issue???
Finally fixed
Thanks so much qman66 I have had problems with my proximity sensor on my JFLTEXX pretty much since I got it. Had been using the xposed disable proximity sensor module but xposed doesn't work with CM12. Your simple system tweak has given me use of my phone know call options again
qman66 said:
with root explorer go to system/lib/hw and go all the way to the bottom to the last sensors file. its an so file. long press on it and open in text editor. somewhere in the page almost at the bottom you will see where it says ProximitySensor then on one of those line it should say mEnabled. just rename it to mDisabled, then reboot and the proximity sensor is fixed.
Click to expand...
Click to collapse
Hi, I tied to do this but it says I can't save the changed so file... Can you let me know which root explorer and text editor you are using?
Thanks massively
Not a text file
qman66 said:
with root explorer go to system/lib/hw and go all the way to the bottom to the last sensors file. its an so file. long press on it and open in text editor. somewhere in the page almost at the bottom you will see where it says ProximitySensor then on one of those line it should say mEnabled. just rename it to mDisabled, then reboot and the proximity sensor is fixed.
Click to expand...
Click to collapse
I found sensors.msm8960.so with many references to proximity sensor but it is not a text file!!
Samsung S4 Active w LOS 15.1 (a&Droid 8.1) - how to disable HW sensor(s).
Hi All
Hope some here will help me stay afloat long enough to learn to surf by myself; bit of a noob in this wild ocean here (more of a 'fresh water/indoor pool' kinda dude I guess) - but trying to break out of tis little pond and learn to 'surf'. Anyway, to the point:
1. HW spec
Samsung Galaxy S4 Active
GT - i9295
TWRP 3.3.0-0
Lineage 15.1 20180227 jactivelte
(sometimes with opengapps pico and addonsu15.1 but mostly just LOS and addonsu nothing else)
2. Have the sensors on phone covered up with black electrical tape - all but the notification light are covered and it's gonna stay that way - NOT negotiable!
Obvious Issue: Have the blank screen during phone call problem. Can end calls using power button but I need to use the keypad quite often so need the screen to stay on. How? Ideally want to (SW) disable most if not all hardware sensors - how?
Tried a few fixes but no luck, e.g.:
(a) adding 'the' fix/control many sensors apk no good as not suported under 8.1 (plus want to find out how to do manually myself not use 'hand outs').
(b) edit selected sensor etc ".so" (eg in system hw) files - so far not resulting in the disabled ProximitySensor.
So, I really want to hack this myself at cmd line level, am ok with that (many years IT ops/admin experience in 'fresh water commercial space'). Can mount system using TWRP then adb shell to connect and find and grep for stuff in files but cannot find setttings I need to change to disable sensors for good. Where to look/find more info?
What do I want to achive:
Make calls and have keypad stay on all the time or give me manual option to turn screen on/off with a hw button during call.
How:
I am happy to disable pretty much all sensors (proximity, gyro, compass etc) in system or firmware memory so that I am free from the overlords and really want to be able to use the keypad during calls - and have option to manually turn screen off/on during call would be cool.
Constraint:
Really want to do this from (a) cmd line or (b) edit code/recompile (learning curve) the LOS 15.1 or whatever to disable sensors for good. I will be using this old thing mostly for just call and txt not much else - and cannot be asked to buy an old Nokia handset.
Thanks,
iHAL8999.999... (hi dave...)
Hi, I wanted to change charging sound of custom rom, cuz its so annoying. So I wanted to change it, but I m not able to find charging sounds in system/media/sounds/ui. I even deleted the media folder, and every sound dissapeared, except charging, so it ISNT in system/media. I was able to change lock, unlock, touch and keyboard sounds, but charging ones are no where to be found. Does anyone know where is the file of charging sound in custom roms?