Database Users

Video quality in Google Talk

I bought this tab for the screen and ability to use the built in front facing cam for video chat with my wife and kids while I'm away for 5 months but while testing it out I've noticed the video quality is crap over google talk from my end. My wife's cam looks great. Is there anything I can do to improve the quality. Currently we are testing it over the same wifi connection.
Sent from my GT-P7510 using XDA Premium App

Try this
https://market.android.com/details?id=com.mirial.clearsea
I downloaded the windows app and the android one and it works great. I use this for work to call my clients.
Sent from my GT-P7510 using Tapatalk

interesting, i had the opposite effect, my camera looked fine but there camera look pix-elated, I assumed that there camera was the one with the problem.

I had an even different issue. Video and audio was about expected given the connection I had. However, the video of me slowly turned to 45 degrees during the chat. I saw it in the lower right of my screen when my dad told me. I restarted the tab but still it persisted. Anyone see this??

Strangely....
droxid said:
Try this
https://market.android.com/details?id=com.mirial.clearsea
I downloaded the windows app and the android one and it works great. I use this for work to call my clients.
Sent from my GT-P7510 using Tapatalk
Click to expand...
Click to collapse
Registered, created an account and received the confirmation/activation email. When I click the link the website timeout - Chrome and Firefox....
The wonderful, trusty 'cloud' must be down...I think it started raining......LOL
Thanks anyway - will try it in a day or two when the cloud is up!

@piperp
This happened to me. There was a slide bar right above the picture of me while using gtak on the tab. If u slide it all the way one direction, right i believe, then it goes back to normal

@shawnwojcik
I thought the slider controlled a zoom level of the camera facing me. At least that's the effect I noticed when I tried it. The tilting picture started when I tried moving the tab to show them something next to me. It really made things worse. I honestly can't remember if I had the lock on the screen auto-turning turned on. I disabled it once this weekend for some reason and may have left it off which caused the problem.
In either case, next time I'll try your suggestion but that's a problem that needs to be fixed because it's really quite awful. Even after a restart of the tab it starts again.

piperp said:
@shawnwojcik
I thought the slider controlled a zoom level of the camera facing me. At least that's the effect I noticed when I tried it. The tilting picture started when I tried moving the tab to show them something next to me. It really made things worse. I honestly can't remember if I had the lock on the screen auto-turning turned on. I disabled it once this weekend for some reason and may have left it off which caused the problem.
In either case, next time I'll try your suggestion but that's a problem that needs to be fixed because it's really quite awful. Even after a restart of the tab it starts again.
Click to expand...
Click to collapse
My brief experience suggested the slider both zooms and enables some kind of facial recognition, so when you move, the background instead moves and your face stays central. This can lead to blacked out areas depending on your position in the frame, as well as a tilting background. It's also a bit buggy i found...

How to fix magnetometer

I just fixed the magnetometer on my Vibrant, using advice found on another site. It took me a long time to find it, so I thought I should post it here to help other Vibrant users find it more easily. There is similar advice in forums for other Galaxy S variants, but nothing here.
About a week ago, I noticed that my phone was no longer sensing its position. The screen would not rotate, and the compass was not working. I ran the sensor test using the *#0*# code, and both the accelerometer and magnetic sensor were stuck on one reading regardless of phone position. Rebooting had no effect.
I found the following procedure on a different site. I would post the link to give proper credit, but I don't have sufficient forum privileges because this is my first post. It was on the dp.nonoo.hu blog.
Your Samsung Galaxy S phone’s compass is not working? Auto rotation is faulty? Check your hardware by dialing *#0*# – this is a factory test app for the phone.
If the compass is broken there too, here’s how you can fix it: delete /data/system/ms3c_yamaha.cfg, and if there’s a backup file, delete it too, then reboot.
If it won’t help, make sure the files are deleted and then run /system/bin/sensorcalibutil_yamaha from a root shell, follow the instructions and then reboot your phone.​
I deleted the file using RootExplorer and rebooted. The accelerometer and magnetic sensor were working perfectly.

Lol I fixed mine by simply flipping the phone a few times. Basically I first downloaded and installed the compass app from the market. Then in the app, I calibrate it normally (wave in a figure 8 pattern) a few times. It will still be pointing incorrectly so next all I do it flip the phone on it's vertical axis a few times then repeat with the horizontal axis. Then it will be correct. This always works for my phone, I do it every time after a factory reset since it uncalibrates the magnetometer every time. I've never had problems with the accelerometer though, only the magnetometer. It would always be out of whack no matter what until I figured out what to do.

Cheers Blue,
This fixed it for me.

I cannot find neither the .cfg fila and or the configuration app.

+1
These files do not exist in ICS AOKP on my Vibrant and my magnetometer still points in the wrong direction lol.
Trying everything I can find on the Internet.
Edit: Removing the battery does not work even after 15 minutes. However, flipping the phone end over end worked immediately. Seems strange that this is not mentioned by any of the Compass apps yet they tell you to draw figure 8's in the air which does nothing on my Vibrant. lol
Thanks to the individual who shared that tip.

same here, a few vertical and horizontal flips did the trick for me. (on ics passion)

Didn't find the "/data/system/ms3c_yamaha.cfg" on my GalaxyS running Slim ICS 3.2. Seems like ICS doesn't have this file. And some vertical/horizontal flips almost did the trick. Now the compass is moving, before it wasn't moving at all. It not showing very good direction like it used to when I first purchased the device almost 15 months ago.
And one more question, does anyone know, what is the testing code for ICS? Because *#0*# isn't working on ICS. I used this code while on gingerbread and it worked before. I thought this code is universal, but now it seems like, its not.

blueguitarbob said:
I deleted the file using RootExplorer and rebooted. The accelerometer and magnetic sensor were working perfectly.
Click to expand...
Click to collapse
1. Doest it still work when the phone is:
- touched with a little magnet like in a standard vertical flip-case (with little magnet) or
- travelling by car/bus/train or
- plugged in headphones
In the one I had (I don't have it any more) while plugging in headphones, or travelling by car/bus/train, or putting it in an flip-case with a little magnet the arrow In Google Maps pointing the direction which a device is currently facing simply freezes. Compass app also freezes at the same time. The app called Android Sensor Box in the scale for magnetometer reaches its maximum level. While moving the little magnet, from mentioned before filp-case, around a phone the arrow travels with it. Move it away and it freezes. It simply won't move. While sticking S4 to the metal part of laptop table the arrow immediately points opposite direction. Only making 8s in the air helps but only for a bit. Neither S3 9305 nor S5 have this problem. Even when stuck with a magnet their arrows in GM works just fine.
2. Does deleting the file fixes the GM's arrow issue also?

Danstek said:
Lol I fixed mine by simply flipping the phone a few times. Basically I first downloaded and installed the compass app from the market. Then in the app, I calibrate it normally (wave in a figure 8 pattern) a few times. It will still be pointing incorrectly so next all I do it flip the phone on it's vertical axis a few times then repeat with the horizontal axis. Then it will be correct. This always works for my phone, I do it every time after a factory reset since it uncalibrates the magnetometer every time. I've never had problems with the accelerometer though, only the magnetometer. It would always be out of whack no matter what until I figured out what to do.
Click to expand...
Click to collapse
**** this worked

compass not working?

I tried a few random compass apps and none of them seem to work (the needle does not point to a fixed direction as I walked around). I tried this with and without wifi/data/location. Can anyone confirm this?
I really like everything else about the phone and I would hate to RMA this just because of the compass.

case-sensitive said:
I tried a few random compass apps and none of them seem to work (the needle does not point to a fixed direction as I walked around). I tried this with and without wifi/data/location. Can anyone confirm this?
I really like everything else about the phone and I would hate to RMA this just because of the compass.
Click to expand...
Click to collapse
I also have troubles with the compass. Tried calibrating it a few times, as per the guidelines Google give out. However it just doesn't seem to want to stick!
Anyone else confirm the issue?
Sent from my Nexus 6P using Tapatalk

I'm also having issues with the compass. Doesn't work as a compass should. Turning around 180dg the phone makes north 180dg from where it was before.

copong said:
I'm also having issues with the compass. Doesn't work as a compass should. Turning around 180dg the phone makes north 180dg from where it was before.
Click to expand...
Click to collapse
I still haven't been able to solve this, not sure if it's a software or hardware issue?

I've just managed to fix it, it was a calibration issue but I fixed it with a different calibration routine as the one in google maps did nothing.
Installed https://play.google.com/store/apps/details?id=com.brothers.compass
Then press the menu button at the bottom right. That goes straight into calibration mode with instructions.

copong said:
I've just managed to fix it, it was a calibration issue but I fixed it with a different calibration routine as the one in google maps did nothing.
Installed https://play.google.com/store/apps/details?id=com.brothers.compass
Then press the menu button at the bottom right. That goes straight into calibration mode with instructions.
Click to expand...
Click to collapse
I've managed to get it to work for a while, but the calibration won't stick after reboot.
Sent from my Nexus 6P using Tapatalk

Damn, same here. Anyone else?

No issues here.

There is a discussion on Google's forum at https://productforums.google.com/forum/m/#!msg/nexus/SK7gbrV5MhU/X4OdqoheBQAJ. Seems the 5X is also having the same issue. Post your problem there to hopefully help get it sorted out quicker.
Sent from my Nexus 6P using Tapatalk

After I finally got the November security update tonight, some of my Play store apps needed updating too. (I'll get to the point in a minute, I promise) One of those apps was Google Maps. I opened it & tapped on the location icon (so the image will turn as I do) & a pop-up came up stating that my compass was not correct & to turn it in several directions in succession to fix it. It may pop up for you too.
If you do not see that, do this: It asks you to hold your phone upright screen facing you (while in Maps) & fan it towards you then away, towards you then away. Then turn it in the air like the 4H queen wave, just twisting your wrist. Then while still facing you, rotate it to the left & right, like you're going to bang the sides of the phone on a table. Do each motion 4 times.
After doing that, the compass is dead on! Unfortunately, it doesn't hold the calibration after shutting the screen off though & backing out of Maps but it's a start without installing an app to do the same thing.

copong said:
Damn, same here. Anyone else?
Click to expand...
Click to collapse
Yep me too. Thank god for XDA. I was thinking I was the only one with no compass (although a 5 minute drive showed navigation works fine). It isn't a deal breaker for me because...
Nearly everything else is just good on the money, great display but not natural white (bit like the old AMOLEDs from the Note 2 that I have) with no pink or yellow hues, great sound (except in calls, loudspeaker only uses bottom to play out the audio), superb fast and crisp camera especially the FFC (but bad stabilisation in videos), beautiful design esp in the frost finish, phenomenal imprint scanner, very good battery life seeing as I'm coming from the venerable Z3 (but it can vary wildly, rogue apps perhaps), excellent build quality as mine doesn't have any QC nicks or rattling noises (apart from the camera lens, which is par for the course), bluetooth works without cutting off via 'cupping', Maps is locked at 60fps for the first time in Android history (and uniquely on this Nexus only), charging is quick and I'm glad it is type C (very convenient).

AOD lighting up the entire screen.

I've noticed that the Always On Display now lights up the entire screen, not just the pixels for the clock and date. As you can see in the pics, even the areas that are supposed to be black (i.e. unlit) are lit up in a dark black-ish kind of glow. This seems to be appearing after the most recent update. Is anyone else seeing this issue on their phones? Is this a software issue or a display problem? Would appreciate some insights on this. Thanks.

I dont have this problem

vrblr2405 said:
I've noticed that the Always On Display now lights up the entire screen, not just the pixels for the clock and date. As you can see in the pics, even the areas that are supposed to be black (i.e. unlit) are lit up in a dark black-ish kind of glow. This seems to be appearing after the most recent update. Is anyone else seeing this issue on their phones? Is this a software issue or a display problem? Would appreciate some insights on this. Thanks.
Click to expand...
Click to collapse
Technically speaking black color on AMOLED displays just turns off the pixels of the phone, it won't light up like what I saw from your picture.
If you are using a screen filter app such as twilight or night owl disable it and check, if not maybe try to reset your phone and I hope that is software related nothing more.

sa3d12 said:
Technically speaking black color on AMOLED displays just turns off the pixels of the phone, it won't light up like what I saw from your picture.
If you are using a screen filter app such as twilight or night owl disable it and check, if not maybe try to reset your phone and I hope that is software related nothing more.
Click to expand...
Click to collapse
Not using those apps. I did a phone reset, but the problem persists.

Did You purchase Your phone from an official Samsung seller? Only phones with non AMOLED panel would light up the whole screen.
Edit: just checked my AOD, Your AOD looks slightly different than mine. On my AOD I can see a date and two small icons.

Can you post similar pictures with the default AOD clock widget?

I'm also experiencing the same issue with my S7 Edge. Problem started out of the blue two days ago; there might have been Play Store updates but I dont reckon any system updates that day. I've been using the night clock for weeks and it was working fine before now.
The problem seems to affect only AOD and night clock, since the edge feed (rubbing the side) works completely fine - only lights the used pixels. AOD and night clock light up the whole screen (not much, but clearly visible in a dark room, grayish background)
Tried resetting and flashing older firmwares via Odin but nothing changed. Hope we find an answer to this, it's shame I cant use the night clock nor the AOD since its killing battery now. :/
I remember S6 edge having the same issue with night clock?

vrblr2405 said:
I've noticed that the Always On Display now lights up the entire screen, not just the pixels for the clock and date. As you can see in the pics, even the areas that are supposed to be black (i.e. unlit) are lit up in a dark black-ish kind of glow. This seems to be appearing after the most recent update. Is anyone else seeing this issue on their phones? Is this a software issue or a display problem? Would appreciate some insights on this. Thanks.
Click to expand...
Click to collapse
Mine is working fine. You must have received an update to something in the last few days if it worked before. Either that or it's a hardware issue.

This seems like a LCD and not AMOLED.. Did you get your display changed due to any reason?

OP stated that the problem occured after an update, so I think it was working fine before that? So I wouldnt say he has S7 edge with LCD display (for whatever reason that's even possible). I can say this for sure about my situation anyway. No display changes or any other repairs, it just started malfunction for no apparent reason.
I tried a third party app for AOD and it worked flawlessy... so the built-in AOD (& night clock) lights the whole screen, while edge feed and 3rd party AOD don't. Confusing.
@vrblr2405 : did you try night clock or 3rd part aod? Is the problem still there?

amritpal2489 said:
This seems like a LCD and not AMOLED.. Did you get your display changed due to any reason?
Click to expand...
Click to collapse
No. This is not an LCD, it's an AMOLED. This is an S7 Edge that I bought two weeks ago. Haven't changed the display or anything like that.
McKis said:
OP stated that the problem occured after an update, so I think it was working fine before that? So I wouldnt say he has S7 edge with LCD display (for whatever reason that's even possible). I can say this for sure about my situation anyway. No display changes or any other repairs, it just started malfunction for no apparent reason.
I tried a third party app for AOD and it worked flawlessy... so the built-in AOD (& night clock) lights the whole screen, while edge feed and 3rd party AOD don't. Confusing.
@vrblr2405 : did you try night clock or 3rd part aod? Is the problem still there?
Click to expand...
Click to collapse
This is the native AOD that comes preinstalled. Version 1.4.02. I've noticed that the edge clock also lights up the whole screen. Could you tell me which third party AOD app to use ? That way I can check and identify if it is a display problem or a software issue.

Try a fresh ODIN install of latest stock firmware

vrblr2405: I used (well, tried) Always on Screen by FayaX. Just make sure you disable the built-in AOD first and give the app the permissions it's asking for. Could you also check if the edge feed is working properly and doesn't lit up the screen? You know, the rubbin' thingy If those two work properly, I'm certain we are facing the same issue
@amritpal2489 : flashing stock didn't help on my situation, but of course it's always good to try.. I've been going through different (stock)firmwares now, just to see if something would change. No luck so far, downloading third one now.
Is there more to reset than the 4 files (AP, BL, CP, CSC)? How's the re-partition in Odin?
I'm unrooted, so I'll stick with stock fw's, but I'm wondering if there is something that's not "resetting" or if I can do something more to get to start every bit and piece from scratch.

Don't even think about re-partitioning in ODIN.. Its not required.
Moreover if you have already flashed stock firmware using ODIN then it is surely a hardware fault buddy. Get it checked at authorised service centre even if it is out of warranty. They will let you know the exact issue. Getting it repaired through them is your choice finally.

Yeah I guess that's what I need to do. Luckily there is a Samsung Service Center nearby.
I just can't understand why would the exactly same function work on a different app if it's hardware related. That's the reason I'm baffled with things to try to get it working.
@vrblr2405, let me know how it works out and share your thoughts, thanks!

McKis said:
vrblr2405: I used (well, tried) Always on Screen by FayaX. Just make sure you disable the built-in AOD first and give the app the permissions it's asking for. Could you also check if the edge feed is working properly and doesn't lit up the screen? You know, the rubbin' thingy If those two work properly, I'm certain we are facing the same issue
@amritpal2489 : flashing stock didn't help on my situation, but of course it's always good to try.. I've been going through different (stock)firmwares now, just to see if something would change. No luck so far, downloading third one now.
Is there more to reset than the 4 files (AP, BL, CP, CSC)? How's the re-partition in Odin?
I'm unrooted, so I'll stick with stock fw's, but I'm wondering if there is something that's not "resetting" or if I can do something more to get to start every bit and piece from scratch.
Click to expand...
Click to collapse
So I downloaded the app you said. The AOD works fine with that app. I tried a couple of other third party AOD apps. The AOD works fine - only the pixels for the clock light up. So it seems to be a software issue with the Samsung AOD.
I tried the edge feeds and it works fine. No lighting up the entire screen. The entire screen being lit up happens only with the preinstalled aod apparently.
I don't intend to root my phone at least till the warranty is valid, so sticking with the original Samsung software. Will go to a service center get this checked.

usmanyasin.bk201 said:
Can you post similar pictures with the default AOD clock widget?
Click to expand...
Click to collapse
Which is the default AOD clock?

Just a dumb thought. Wondering if the clock type might make difference. The default one is just a simple white one. Image attached.

usmanyasin.bk201 said:
Just a dumb thought. Wondering if the clock type might make difference. The default one is just a simple white one. Image attached.
Click to expand...
Click to collapse
I thought so too initially. Tried with all the different clock faces. Entire screen still lights up.

Weird. Have you ever rooted the device or is rooted right now?

Navbar stop working

so i recently replace my mtxp screen and everything was working perfectly until one day i was watching a youtube video and tried using my navbar buttons and they were unresponsive..did everything from rebooted..clear cache..reinstall rom...same problem..its like the bottom of the screen is unresponsive and only works when screen is locked...
anyone else with the same problem/solution?

Hi, I have the same situation: the screen was replaced some 9 months ago and worked fine until a few days ago, when the navigation bar stopped responding. I think it happened during watching a video (on facebook or YouTube) as in your case. I've also tried everything you did, but for no avail. The interesting thing is that the screen itself is reaponsive in that area e. g. during the Setup wizard or on the lock screen (e.g. the button to switch on the camera is working fine). I think I had some similar issue with another android device (LG 4X) when I was using a non-stock ROM (CM) and there was some issue with the installation of Google Apps. As I'm using the stock ROM for my Moto X Style, my best guess is that it might be a potential Google Play Services update that is causing this issue.
Maybe this theory could be checked by installing a third party ROM without Google Apps (I'm not sure if that is possible) to see whether the navbar works that way or not.

vodanium said:
Hi, I have the same situation: the screen was replaced some 9 months ago and worked fine until a few days ago, when the navigation bar stopped responding. I think it happened during watching a video (on facebook or YouTube) as in your case. I've also tried everything you did, but for no avail. The interesting thing is that the screen itself is reaponsive in that area e. g. during the Setup wizard or on the lock screen (e.g. the button to switch on the camera is working fine). I think I had some similar issue with another android device (LG 4X) when I was using a non-stock ROM (CM) and there was some issue with the installation of Google Apps. As I'm using the stock ROM for my Moto X Style, my best guess is that it might be a potential Google Play Services update that is causing this issue.
Maybe this theory could be checked by installing a third party ROM without Google Apps (I'm not sure if that is possible) to see whether the navbar works that way or not.
Click to expand...
Click to collapse
Hopefully I will figure it out.. It's definitely a software problem triggered by a update or system app.. My work around for now is using a nav bar app from the playstore

vodanium said:
Hi, I have the same situation: the screen was replaced some 9 months ago and worked fine until a few days ago, when the navigation bar stopped responding. I think it happened during watching a video (on facebook or YouTube) as in your case. I've also tried everything you did, but for no avail. The interesting thing is that the screen itself is reaponsive in that area e. g. during the Setup wizard or on the lock screen (e.g. the button to switch on the camera is working fine). I think I had some similar issue with another android device (LG 4X) when I was using a non-stock ROM (CM) and there was some issue with the installation of Google Apps. As I'm using the stock ROM for my Moto X Style, my best guess is that it might be a potential Google Play Services update that is causing this issue.
Maybe this theory could be checked by installing a third party ROM without Google Apps (I'm not sure if that is possible) to see whether the navbar works that way or not.
Click to expand...
Click to collapse
Hopefully I will figure it out.. It's definitely a software problem triggered by a update or system app.. My work around for now is using a nav bar app from the playstore

Hi, I have switched on the "Show touches" feature in the Developer options to see whether the screen is detecting touches in the bottom area of the screen: it actually doesn't. It is not an issue on the lock screen though but it is for the navigation bar. So, it seems it is the hardware that is acting up, after all...
I have found a thread about this issue with a workaround to increase the height of the navigation bar by xposed: https://forum.xda-developers.com/moto-x-style/help/navigation-buttons-issue-t3497985
I'll try either that or by installing a custom ROM that has that option built in - e.g. AICP 12.1 (Android 7.1) seems to have such setting.

https://forum.xda-developers.com/moto-x-style/help/solved-navbar-responding-t3993049

Same problem here - at least in my case also a hardware issue after replacing a broken screen. Thought (as many did) it was software because TWRP, lockscreen etc works, but if you actually try touching only the downmost parts of the TWRP or lockscreen buttons, it won't react. "Show touches" from developer tools also shows touches being registered only just above the normal navigation buttons.