Related
Flip4Silence enabled you to flip or shake an incoming call silent! It can also reduce the ringtone volume if you pick up your phone!
Unlike all the other ones I know Flip4Silence do not stress your battery. It's only active when you need it. This got some drawbacks... but hey, it works quiet well!
About "mute via flip/shake":
A friend of mine changed his good old WM6.5 phone into a Android powered device and was annoyed that you can't flip a call silent with a AOSP - now here it is, without the battery stress
About "reduce on pickup":
Someone with an HD2 told me that his phone got this "reduces volume on pick up" feature and I searched the market to find an app for android... Didn't find anything, wrote it myself! Hope you like it too!
Supported android versions: 1.6 and above
Link to Market: Link
Version 1.6.1
- The collection phase is over, thanks everyone for sharing!
Version 1.6.0
- Added "Improve F4S". It would be great if you could help me!
- UI rework
- Maybe fixed "volume not restored" problem
- The fakevibrator used by the "pickup" feature is now stopped when F4S snaps in
Version 1.5.1
- Gingerbread is now supported!
- Fixed 2 rare force closes
Version 1.5.0
- Fixed that "Vibrate only in silent mode" is not a valid mode to enable the pick up volume reducer
- Fixed a bug where the ringer volume is set to early to its normal value
- Fixed the pick up volume reducer behavior
- Fixed shortcut to the audio settings on 1.6
- Added sensitivity settings for the pick up volume reducer
- Added vibration as an option if the pick up volume reducer can't operate
- Minor UI rework
Features:
* flip or shake your phone to mute it (3 modes)
* Pick your phone up from the table and it reduces its volume!
* notifications after hang up (vibration/sound)
* extra battery friendly
Suppoerted modes:
* Mute a call when your phone is laying on its display
* Mute a call when you flip your phone from one side to the oder
* Or mute via a shake
Any feedback/wish/bugreport is welcome!
Will give a try. I've been using Shake2Mute, which is quite similar.
Sent from my HTC Desire using Tapatalk
Version 1.4 is on the market!
Thanks. I wanted this after i saw it on htc.
Sent from my GT-I9000 using XDA App
This wont work on my device: HTC MAGIC, I am confident it has an accelerometer and magnetic sensor because other apps use these features do you have any suggestions?
hayer said:
This wont work on my device: HTC MAGIC, I am confident it has an accelerometer and magnetic sensor because other apps use these features do you have any suggestions?
Click to expand...
Click to collapse
Hm, it seems that something is wrong with the sensorcheck. You are sadly not the only with this issue but the only one who got in contact with me (thanks for this, looking at the comments and see "does not work" is not very nice :/).
I got some questions to investigate this problem:
1) Am I right that the magic is currently on froyo? You got which version?
2) Am I right that a dialog is shown which says "Sorry, no accelerometer and/or magnetic field sensor found"?
3) As you sad other apps are working, which for example (something that uses the phone orientation)?
Currently I have no idea why the code is working on my device (N1) and the milestones I got for testing here...
For the technical people who might have an idea: I'm currently using SensorManager.getDefaultSensor() with the SENSOR_ACCELEROMETER and SENSOR_MAGNETIC_FIELD constants, any idea why this might not work?
Tested on i7500 with 2.2.1 GAOSP.
It lowers the volume when I take it in my hand.
It doesn't mute when flipped.
It does mute when shaked.
Excelent work ! Thanks !
I attached Version 1.4.1 which hopefully fix the issue many people reported. It would be nice if anyone with the message "Sorry your device is unsupported" can try this one and report back how it performs.
hayer said:
This wont work on my device: HTC MAGIC, I am confident it has an accelerometer and magnetic sensor because other apps use these features do you have any suggestions?
Click to expand...
Click to collapse
I finally fixed the issue you reported in version 1.4.3. Thanks for your report!
Luminger said:
I finally fixed the issue you reported in version 1.4.3. Thanks for your report!
Click to expand...
Click to collapse
Thankyou Luminger I appreciate the response and the quick fix and this is now working astoundingly on my magic saved my ass in physics class the other day
Thanks,Luminger, Works great on Moto Qunech XT3...thanks alot...
I've tested it on my LG Optimus One P500.
It works great but there is a little bug.
I have only enabled the option to reduce volume when picking it up. After 1-2 calls, the volume remains lowered. It doesn't come back to normal, I have to raise the ringtone level manual from the hardkeys. Hope you understood.
It is an excelent app ! Thank you !
so it's like one of the feature from HTC Sense, right?
gotta try it when I use clean build with no sense..
Yea, sounds like a bug as F4S should move the volume back to the previous level. I will take a look this evening, thank you for the report!
I really hope that you can fix it.
Thank you !
badeaioan said:
I've tested it on my LG Optimus One P500.
It works great but there is a little bug.
I have only enabled the option to reduce volume when picking it up. After 1-2 calls, the volume remains lowered. It doesn't come back to normal, I have to raise the ringtone level manual from the hardkeys. Hope you understood.
It is an excelent app ! Thank you !
Click to expand...
Click to collapse
badeaioan said:
I really hope that you can fix it.
Thank you !
Click to expand...
Click to collapse
Just wanted to inform you and everyone interested that I'm currently reworking F4S to work around those bugs. Currently I have no clue where this behaviour came from but I think it will be fixed with the rework.
alphadeeto said:
so it's like one of the feature from HTC Sense, right?
gotta try it when I use clean build with no sense..
Click to expand...
Click to collapse
It is suposed to be like the HTC Sense yea, don't know if its working in exact the same way (as I never have seen the Sense config dialog ).
badeaioan said:
I've tested it on my LG Optimus One P500.
It works great but there is a little bug.
I have only enabled the option to reduce volume when picking it up. After 1-2 calls, the volume remains lowered. It doesn't come back to normal, I have to raise the ringtone level manual from the hardkeys. Hope you understood.
It is an excelent app ! Thank you !
Click to expand...
Click to collapse
1.4.4 is out now which should fix your issue. I managed to reproduce the error by accident and reworked the code at this place - seems to be fixed with 1.4.4.
Luminger said:
1.4.4 is out now which should fix your issue. I managed to reproduce the error by accident and reworked the code at this place - seems to be fixed with 1.4.4.
Click to expand...
Click to collapse
1.4.4 appears to keep the "Reduce volume" option always grayed out. That's really the only feature I want from the app, and before this version I had enable flip4silence unchecked and only reduce volume checked.
c00ller said:
1.4.4 appears to keep the "Reduce volume" option always grayed out. That's really the only feature I want from the app, and before this version I had enable flip4silence unchecked and only reduce volume checked.
Click to expand...
Click to collapse
Hm, doesn't sound good...
Are you sure the ringer vibration is off? Off should be the only option F4S accepts.
Did you managed it to get it working when you change the F4S settings ore the vibration settings?
Which device on which version, ROM?
Sorry that I broke it for you, but it's working perfectly on my Nexus One here :-/
Oh, never mind! Somehow my ringer vibration became enabled again before I updated the app. Great app
Hello,
Anyone else experienced this?
When receiving a call, my phone only vibrates once. Ringtone is still there. I'm using LG's QuickCover for Nexus 5.
Is there a way to solve this?
Same here. It's horrible because the phone only vibrates one...
NEXUS % - ANDROID L
I have quick cover too. I was trying call without this cover and vibrate was working. When I closed the phone, vibrate worked as you described...
So it's a bug with the OFFICIAL cover?! I have receiver OTA yesterday and i discover that bug, the battery drains quickly and the lockscreen created by user preferences just disappeared as the silent mode... Common Google what is this?! Please fix that!
Yes, official cover.. Its a pity.. I really do miss a lot of calls because of that bug..
Nexoez said:
Yes, official cover.. Its a pity.. I really do miss a lot of calls because of that bug..
Click to expand...
Click to collapse
I hope Google fix that mess...
Same thing here, but for me it only occurs sometimes.
Noticed it the first time today after flashing the factory image from release day.
Also with the quick cover...
Same problem for me
I'm having the same problem with my Nexus 5 w/quick cover. With the cover on, my phone will only vibrate once for incoming calls when set to vibrate. If I remove the cover the phone will continue to vibrate when receiving an incoming call. GOOGLE, PLEASE FIX THIS BUG.!
Nexoez said:
Hello,
Anyone else experienced this?
When receiving a call, my phone only vibrates once. Ringtone is still there. I'm using LG's QuickCover for Nexus 5.
Is there a way to solve this?
Click to expand...
Click to collapse
Same here!
I tried even with Cyanogenmod 12 unofficial rom (based on 5.0.1) and still the same bug.
Come on Google!
Bug still present in 5.0.1 ?
DennizzNL said:
Bug still present in 5.0.1 ?
Click to expand...
Click to collapse
Bug still present after flashing the 5.0.1 Factory Image
Any workaround with stock?
Yes bug still appearing on Android 5.0.1
Hi guys. Could this be your problem? I was having same issue too.
Search on YouTube: My Google Nexus 5 is Not Vibrating - HOW TO FIX IT
Problem still not fixed after 5.1 update
Issue still in 5.1.1
Installed smart vibtrator and that seems to work..
Short vibrate with LG Quick Cover
I've created this tool to fix the issue on my nexus 5:
play.google.com/store/apps/details?id=org.koradesktop.mylongvibrator&hl=en
Basically,there are 2 bug i find in every marshmallow rom ,but i don't know why any body doesn't discuss it-
1:flashlight tile dissapears but magically appears after a soft reboot.
2:every night to charge,i have to reboot the phone.
anyone else having same problems
Have both those bugs, the second one is only when battery cups below 10% and battery saver mode is on it seems to me... A third bug that I don't find any mention is with the phone app, sometimes searching contacts doesn't work, I have to exit the app and come back... And after 2-3 calls I am unable to exit the app by pressing back button, I have to press home and come back to app for it to work
1. Very low on call voice
2. FM Radio
3. Flashlight disappears (Alternatives are there, though)
Devs, must be working on them, but surely it gonna take time, because Xiaomi hasn't updated Source Code for MM.
Toruk.Makto said:
1. Very low on call voice
2. FM Radio
3. Flashlight disappears (Alternatives are there, though)
Devs, must be working on them, but surely it gonna take time, because Xiaomi hasn't updated Source Code for MM.
Click to expand...
Click to collapse
I have the above bugs plus another one! During calls, when adjusting volume, the slider moves up and down but the actual volume doesn't change! Can anybody confirm whether they also have this bug?
I don't have ny of those with latest cm13
I cant take screenshots with any of the mm roms normally,
Third party apps work,anyone confirm this
1799yd said:
I cant take screenshots with any of the mm roms normally,
Third party apps work,anyone confirm this
Click to expand...
Click to collapse
I can take screenshots with both AOSPA and slimbit.
xiaomiboy said:
I can take screenshots with both AOSPA and slimbit.
Click to expand...
Click to collapse
Cyanogenmod 13 screenshots work fine.
Are you sure you have the correct key press? Volume down and power at the same time.
david_inuk said:
Cyanogenmod 13 screenshots work fine.
Are you sure you have the correct key press? Volume down and power at the same time.
Click to expand...
Click to collapse
Finally after searching i found that it was a problem regarding "pictures" folder
I deleted it,system recreated it,and woilaa,screenshots working,
I was thinking it was a bug.
I'm on official cm13 and proximity sensor is not working.. is there any fix for it?
surajsun22 said:
I'm on official cm13 and proximity sensor is not working.. is there any fix for it?
Click to expand...
Click to collapse
No.
david_inuk said:
I have the above bugs plus another one! During calls, when adjusting volume, the slider moves up and down but the actual volume doesn't change! Can anybody confirm whether they also have this bug?
Click to expand...
Click to collapse
All these issues are known bugs. Doubtful if they will ever be resolved. They have been present since CM13 and probably relate to the fact that Xiaomi have only ever released their source files for a very old version of Android.
Sent from my MI 4i using XDA-Developers Legacy app
---------- Post added at 12:10 AM ---------- Previous post was at 12:08 AM ----------
sharan.nyn said:
No.
Click to expand...
Click to collapse
The official CM13 has other bugs too, notably, no bluetooth. Devs have confirmed they will not be fixing it. They don't image anybody wants CM13 when they have already released CM14.1.
Sent from my MI 4i using XDA-Developers Legacy app
It's finally here ! Oreo for R7 Plus.
https://download.lineageos.org/r7plus
Happy Flashing !
Bugs :
-Double tap to wake not working *FIXED*
-Fingerprint Sensor not working *FIXED*
-Audio stuttering at low volume
rch.aj34 said:
It's finally here ! Oreo for R7 Plus.
https://download.lineageos.org/r7plus
Happy Flashing !
Bugs :
-Double tap to wake not working
-Fingerprint Sensor not working
Click to expand...
Click to collapse
Hooray! Found it! And good to see confirmation that the Fingerprint sensor isn't working.
I can report a Bluetooth bug using Bluetooth headphones. It doesn't matter what app is used and in what environment. The sound is interrupted by a periodic, soft click, followed a nanosecond later by a split second drop off in sound. It's very quick, but noticeable.
Has anyone else noticed this?
If not, if the developer could let me know what files I need to provide to help, I'll gladly provide them
We always report the same bugs snail haha ! there's still the audio stuttering (headphones) issue but i finally found a fix , let me know if you're still having the bug.
rch.aj34 said:
We always report the same bugs snail haha ! there's still the audio stuttering (headphones) issue but i finally found a fix , let me know if you're still having the bug.
Click to expand...
Click to collapse
Haha! I also found this in the [Iron] Maiden Audio app, "Detected problem with app native libraries (libavcodec)", so there might be a codec bug there that's causing the regular dropouts on the wireless phones. It's too disruptive at the moment to tell if the other bug, with wired phones at low volumes, still exists. As I use the phone to compose, the audio issues are problematic. I love Oreo, though.
Are there any developers reading this thread, btw?
And I have issues with the screen not responding when it goes to sleep. I need to hit the power button again to sleep it again and wake it up, but I think that's already been reported.
snaily trail said:
Haha! I also found this in the [Iron] Maiden Audio app, "Detected problem with app native libraries (libavcodec)", so there might be a codec bug there that's causing the regular dropouts on the wireless phones. It's too disruptive at the moment to tell if the other bug, with wired phones at low volumes, still exists. As I use the phone to compose, the audio issues are problematic. I love Oreo, though.
Are there any developers reading this thread, btw?
And I have issues with the screen not responding when it goes to sleep. I need to hit the power button again to sleep it again and wake it up, but I think that's already been reported.
Click to expand...
Click to collapse
I fixed it by downloading a frequency generator app with background playback , set the frequency at 19Hz , and audio is perfectly fine even at 5% volume , i suppose those frequencies are harmless but that's how i fixed it.
as far as screen , double tap to wake is down but hopefully next build it's fixed along with the fingerprint sensor.
rch.aj34 said:
I fixed it by downloading a frequency generator app with background playback , set the frequency at 19Hz , and audio is perfectly fine even at 5% volume , i suppose those frequencies are harmless but that's how i fixed it.
as far as screen , double tap to wake is down but hopefully next build it's fixed along with the fingerprint sensor.
Click to expand...
Click to collapse
Frequency generator app!! Amazeballs!
snaily trail said:
Frequency generator app!! Amazeballs!
Click to expand...
Click to collapse
Yep ! Enjoy your great audio but lack of fingerprint sensor for now hahaha
rch.aj34 said:
Yep ! Enjoy your great audio but lack of fingerprint sensor for now hahaha
Click to expand...
Click to collapse
Except the sound isn't great at the moment! There's also an issue with Norton Password Manager reporting a fault in another API. I'll list it next time it appears
rch.aj34 said:
Yep ! Enjoy your great audio but lack of fingerprint sensor for now hahaha
Click to expand...
Click to collapse
Norton IDSafe has a libvault.so error that might also be non device specific. Very similar to the Bluetooth lib message
snaily trail said:
Norton IDSafe has a libvault.so error that might also be non device specific. Very similar to the Bluetooth lib message
Click to expand...
Click to collapse
Actually i tried the bluetooth in my car and it's perfect , no clicking and much more responsive than lineage 14.
rch.aj34 said:
Actually i tried the bluetooth in my car and it's perfect , no clicking and much more responsive than lineage 14.
Click to expand...
Click to collapse
Oh, bugger!
snaily trail said:
Oh, bugger!
Click to expand...
Click to collapse
I reset the phone and reinstalled 15.1 and Gapps, and the intermittent clicking has disappeared. Something obviously went wrong with the initial installation. So if anyone else has a problem with sound, retrying the fresh install might help. The low volume issue has also gone. The library errors remain for the sound and vault apps, though, so I presume they're non-device specific. And FL Studio is crashing at the end of longer recordings, not saving them in the process, which I think might also be fixed when the library error is addressed.
The wake issue isn't nearly as chronic as it was, either. In fact, I hardly notice it all now. I used the Nano version of Gapps, btw.
snaily trail said:
I reset the phone and reinstalled 15.1 and Gapps, and the intermittent clicking has disappeared. Something obviously went wrong with the initial installation. So if anyone else has a problem with sound, retrying the fresh install might help. The low volume issue has also gone. The library errors remain for the sound and vault apps, though, so I presume they're non-device specific. And FL Studio is crashing at the end of longer recordings, not saving them in the process, which I think might also be fixed when the library error is addressed.
The wake issue isn't nearly as chronic as it was, either. In fact, I hardly notice it all now. I used the Nano version of Gapps, btw.
Click to expand...
Click to collapse
Just upgraded to latest nightly and fingerpint sensor is still dead , i read everywhere that flashing firmware will solve it but no idea how to proceed without losing data.
*BUG Fixed : Double Tap To Wake now working.
rch.aj34 said:
Just upgraded to latest nightly and fingerpint sensor is still dead , i read everywhere that flashing firmware will solve it but no idea how to proceed without losing data.
*BUG Fixed : Double Tap To Wake now working.
Click to expand...
Click to collapse
Expanded desktop still causing havoc. Low audio still produces dreadful stuttering on wired headphones and fingerprint sensor still not there, but it's better. I don't know how to flash the firmware either.
snaily trail said:
Expanded desktop still causing havoc. Low audio still produces dreadful stuttering on wired headphones and fingerprint sensor still not there, but it's better. I don't know how to flash the firmware either.
Click to expand...
Click to collapse
Expanded desktop works perfectly for me. this thread looks like a pm between me and you lol. community dead but so awesome to have 8.1 on the R7 Plus haha.
rch.aj34 said:
Just upgraded to latest nightly and fingerpint sensor is still dead , i read everywhere that flashing firmware will solve it but no idea how to proceed without losing data.
*BUG Fixed : Double Tap To Wake now working.
Click to expand...
Click to collapse
Do you have a link to the information regarding firmware flashing?
rch.aj34 said:
Expanded desktop works perfectly for me. this thread looks like a pm between me and you lol. community dead but so awesome to have 8.1 on the R7 Plus haha.
Click to expand...
Click to collapse
Yep. I'm disappointed the developer hasn't a means of accepting bug reports from users.
I tried this on my r7plusf and wifi does not work. (Australia) Latest 14.1 works and has wifi region selections but 15.1 did not.
steve.rand said:
I tried this on my r7plusf and wifi does not work. (Australia) Latest 14.1 works and has wifi region selections but 15.1 did not.
Click to expand...
Click to collapse
I thought that WiFi should work regardless of the ability to select regions. Perhaps there is another problem. Maybe your persist partition was clobbered in the flashing.
Hello everyone,
anyone experienced the main screen dimming to a very low brightness level " in the sun " and no difference happens if i switched off adaptive brightness and got it to the max. I am not sure if that is related to the phone heating, but in general sometimes it dims very quick without even having the phone that heated.
OR maybe the phone gets heated very fast with simple use in the sun light.. any experiences related to that issue ??
Thank you great people.
Can't confirm your observation ... . But there is an option to dimm the screen in the settings of the energy or battery saving mode.
m.
It's a false positive from the light sensor. Some phones add a special setting to increase the brightness when it's overly bright to offset it, but I haven't come across one for this phone. It's a little impressive that so few phones actually address it after it's been a known issue so long.
I thought this issue was fixed already... what sw version are you on? share the device' model number as well please.
Additionally, submit error report to Samsung Members after reproducing the issue, you should be able to get guidance on how to get the fix...
meduza said:
Can't confirm your observation ... . But there is an option to dimm the screen in the settings of the energy or battery saving mode.
m.
Click to expand...
Click to collapse
no that is not the case, it happens even when not enabling the power saving mode.
twistedumbrella said:
It's a false positive from the light sensor. Some phones add a special setting to increase the brightness when it's overly bright to offset it, but I haven't come across one for this phone. It's a little impressive that so few phones actually address it after it's been a known issue so long.
Click to expand...
Click to collapse
so do you mean there is a solution or it is just a bug with the sensor ?
TheNewGuy92 said:
I thought this issue was fixed already... what sw version are you on? share the device' model number as well please.
Additionally, submit error report to Samsung Members after reproducing the issue, you should be able to get guidance on how to get the fix...
Click to expand...
Click to collapse
can you tell me how to submit this error report ? is it through the samsung members application ??
also the model number is SM-F711B
software version is android 11.. one ui 3.1.1 ..
k.a.h said:
so do you mean there is a solution or it is just a bug with the sensor ?
Click to expand...
Click to collapse
It's a bug that should have been fixed already.
twistedumbrella said:
It's a bug that should have been fixed already.
Click to expand...
Click to collapse
Sadly its not fixed at my side !
k.a.h said:
can you tell me how to submit this error report ? is it through the samsung members application ??
also the model number is SM-F711B
software version is android 11.. one ui 3.1.1 ..
Click to expand...
Click to collapse
If you don't have Samsung Members app installed then go to Galaxy or Play store and download it. In the app, click the Blue circle with+ icon. Then select Error Report.
Provide as much detail about the issue as you can and if possible include any screenshots or screen recording (make sure it's 1 issue per ticket).
Sorry for the late Reply... hope this helps and any future issues, submit a ticket as your first step so Samsung can start working on the issue while you look for work arounds or fixes
It might be a bug related to overheating. Had that happen to mine. The phone becomes too hot and dims the screen, turns off multi-window.