Database Users

Noticed some bugs today..... :(

OK so biking to work today noticed a few different bugs I had not noticed so far, coming from iPhone I had never experienced these problems with Apple.
My bluetooth simply will not auto connect to my garmin 510, I have to go into both devices and "forget" paired devices and reconnect a fresh, every time I turn either device off/on.
Headphones crackling at high volume (which isn't really that high to be fair) can't be the headphones as there very high spec. Atomic Floyd HiDefDrum
Just tried to compose an email (original email client) and as I write the email the cursor moves by itself back into the middle of the line im writing making it impossible to write a full line??? WTF?
TBF, at the beginning of this note I seem to compare to Apple, but thinking about it these are basics that should work on any device, I have been perfectly happy with the S4 up until now.... But the 3 jobs I wanted it to do properly today, it's failed at....... miserably!!

OK, So I've managed to write my email. Had to switch to original samsung keyboard (from swiftkey)
Can anybody replicate this error using original email app/swiftkey

jus71n said:
OK, So I've managed to write my email. Had to switch to original samsung keyboard (from swiftkey)
Can anybody replicate this error using original email app/swiftkey
Click to expand...
Click to collapse
I think I've read one or two complaints about the cursor issue. You can just install another keyboard from the Play Store. Thats the joy of android..
About the crackling, there's a whole thread on that topic. It seems that the S4, majorly the qualcomm LTE version I think, has crackling issues when you use headphones with a resistance lower than 14-16 ohms, so you're out of luck as of now until that issue is sorted by Samsung. You can find more info here, just search for it next time:
http://forum.xda-developers.com/showthread.php?t=2258831

jus71n said:
Noticed some bugs today.....
Click to expand...
Click to collapse
I recommending this anti bug spray.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is very comfortable, you can carry in a pocket. When you see bugs just spray all over it with this magnificent product.
(But remember, this is not for internal use)

S4 mini (any version) Lollipop issues

Seeing that there are a lot of posts in L topics that mention the same problem, and only 'pollute' topics with useless stuff I thought about making this thread.
This is UNOFFICIAL and I just want to make it 'easier' to fix problems some users are reporting, well least try to put all 'useful' tips into one topic.
All I'm expecting is:
-Post your model i919(0/2/5/7)
-Baseband version (don't forget region)
-kernel
-Lollipop ROM you are using
-list issues you have
-list any fix that has not been posted in this thread before that might help fix some common problems (for example losing audio in call)
-any additional stuff that might be relevant
For lurkers: If a fix helped you, hit thanks, if not - post your solution or wait until a fix
I'm going to start:
-i9195
-I9195XXUCNJ6, europe
-3.4.0-aosp-gdae987b (included in CM12)
-cm-12-20141211-UNOFFICIAL-serranoltexx.zip
-in call my mic stops working (but mostly with pre3 kernel, going to see if it works better with kernel included in cm12)
-did full wipe today, installed clean cm-12-20141208 and upgraded a few hours later to cm-12-20141211

Wrong post. nevermind.

WiFi has lately started going to sleep when the phone is being left idle for 20-30 mins even though I have set it to always stay on. This issue made me get away from CM11 and it's very frustrating to encounter it now here as well. The issue came along with the build before the 11-12-2014 one.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my GT-I9195 using XDA Free mobile app

Mitko said:
WiFi has lately started going to sleep when the phone is being left idle for 20-30 mins even though I have set it to always stay on. This issue made me get away from CM11 and it's very frustrating to encounter it now here as well. The issue came along with the build before the 11-12-2014 one.
Sent from my GT-I9195 using XDA Free mobile app
Click to expand...
Click to collapse
i also have this problem only on lollipop. my workaround is use this app

OK Google is Haunting Me

I intentionally turn off OK Google detection so my phone is doing one less thing, but it still is working and the options are disabled. I've only recently started to notice this. Tried to enable and disable the options again... no joy.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SAMSUNG-SM-G935A using Tapatalk

Anyone?
Sent from my SAMSUNG-SM-G935A using Tapatalk

jgruberman said:
I intentionally turn off OK Google detection so my phone is doing one less thing, but it still is working and the options are disabled. I've only recently started to notice this. Tried to enable and disable the options again... no joy.
Sent from my SAMSUNG-SM-G935A using Tapatalk
Click to expand...
Click to collapse
This may be painfully obvious, and I'm not trying to sound sarcastic at all, but:
Have you tried saying OK Google to see if it's actually working? How about just removing the widget from your home screen and replacing it with one that isn't voice activated? Or perhaps both..

paulhansen said:
This may be painfully obvious, and I'm not trying to sound sarcastic at all, but:
Have you tried saying OK Google to see if it's actually working? How about just removing the widget from your home screen and replacing it with one that isn't voice activated? Or perhaps both..
Click to expand...
Click to collapse
Yes, it does work when saying OK Google. Also, would removing it prevent the mechanism on the backend that's listening from working also? Or would the service still be running?

I know that when I removed it, there didn't seem to be any listening going on. I think it uses this process in Maps as well as a couple other GApps, so after removing it you can try it in there/disable it in there as well. If you have root, you can always freeze it with TB. I completely removed it from my phone, so I don't have it to play with to try to find these things out. That's always the first thing I do, so I know very little about tinkering with system apps without root.

You can enable OK Google in settings.
try disabling your google account in settings.

Mms video only coming through as a photo with audio file seperate

Forgive me if its posted somewhere else but I can't find anything about it.
Galaxy S5, rooted, BL unlocked, latest Resurrection remix ROM (android 7.1.2)
Twrp recovery.
Worked fine with current setup, phone screen broke about a month ago, had to use a Motorola RAZR Maxx in the meantime. Fixed my GS5 screen and started using it again. Ican't remember if I'd recieved successful videos via MMS since then but the last couple days they only show up as a picture, like the first frame of the video being Sent, and also the audio is received from the video, but the video is not there. What the heck is wrong? I have looked through my settings and everything seems to be OK, its not like I changed something that I know of. Even sending a video to myself, sends as a video but received as a photo with a separate audio file.
Google doesn't help me. I searched the site and am not pulling up anything similar. Any help?
Noticed as well that trying to play sent video from conversation to myself, first one will crash messaging, second one plays. Not sure what's going on.
There seems to be a bug in the new RR ROM update I can't find anything about, the stock camera app, as well as others from play store, will occasionally freeze and reboot phone immediately after opening camera. Not every time, but often.
I don't know if the 2 issues are related, I dont think so, but I first noticed MMS video issue after installing 'Open camera' from the market to see if that would fix the camera issue. Any help would be greatly appreciated
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Any luck with this? I am experiencing a similar issue on a different phone with a Nougat ROM.

Google pixel call screening possible on Shamu?

Do you think it is possible to Port to the Shamu?
Checked it out on my brothers pixel 2 and it is awesome.

so i edited my build.prop and changed to pixel 3 xl and "crosshatch" or whatever the codename for the pixel is. that didnt do anything.
i had a little hope because i rebooted and i got a screen "lets finish setting up your pixel" but it still wasnt activated.
then i decompiled the APK and found in smali called DDP.smali i found "allow_speak_easy == false"
changed it to true but nothing changed.

I was just having the same question as OP as updated my Google Dialer to Beta version 27.x which should support it, but not happening on my phone running an 8.1 ROM AOSiP...
Was wondering if a build.prop change might help - seems kidhudi has tried without luck
Here's hoping someone figures out a way..... !!!
Kidhudi - have you had chance to look at logcat around time of incoming call activity or phone/app startup?

relaxable said:
I was just having the same question as OP as updated my Google Dialer to Beta version 27.x which should support it, but not happening on my phone running an 8.1 ROM AOSiP...
Was wondering if a build.prop change might help - seems kidhudi has tried without luck
Here's hoping someone figures out a way..... !!!
Kidhudi - have you had chance to look at logcat around time of incoming call activity or phone/app startup?
Click to expand...
Click to collapse
No i didnt try that sorry
i also found a thread for another phone that people edited the Dialer_Phone_Type.xml. so i tried that too but to no avail.
the search continues

https://github.com/thehappydinoa/google-call-screening
Stumbled across a magisk module. But still no love lol.

left the build prop on Pixel 3 XL for the night and my dialer went from looking like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
to this
but still no screening enabled

kidhudi said:
left the build prop on Pixel 3 XL for the night and my dialer went from looking like this
to this
but still no screening enabled
Click to expand...
Click to collapse
This is the beta version