Related
Hi all,
this is my very first post here on xda, so please forgive me if this is not the proper section for my thread. I searched for other thread about similar issues, but I didn't find anyone. I'm Italian, so I even hope to not being wrong in English writing.
I recently bought (on November 2014) an Huawei Ascend Y550-L01 (Android 4.4.4, EMUI 2.3, ROM B137), coming from a (Portuguese) Samsung Galaxy Y Pro GT-B5512. Soon I experienced a very strange GPS behaviour: GPS turns itself off. No problem in signal fixing, nor in quality or precision. It simply deactivates.
First I noticed this using the OruxMaps app (which works fine on many phones, even my old one), simply recording the track. Indeed, at the beginning the app was being killed (because of the integrated task-killer) when screen was off, but after setting it as a "protected" app, when I record a track, GPS works while screen is on and, if screen turns off, then most of the times (not always) GPS is deactivated from within Android settings.
I even received (from the purchasing time) some GPS errors while in the home screen... I don't remember exactly that error, but in a fast Internet search it was told being caused from the weather widget, precisely from the "actual position" setting. I deactivated it and added manually my town and those errors were gone.
Then I noted another strange behaviour: GPS turns off even in standby, during night. It is on "extreme precision" on evening and it's off at morning. Sometimes I notice these deactivation (in the notification menu or into the energy saving widget) while I'm using the phone (but always when screens is off), without any error or message popping out... It simply gets deactivated.
Any other experiencing this strange issue? What could be the cause? I sent a mail to official support, but they asked me to take the phone in a service point... I can't stay without phone, so I would like to avoid this if it's not strictly needed.
I think it's a ROM issue (said that even in the mail), but unfortunately still there is no alternative one (or at least I found none). I think also that (almost) every app that uses GPS suffers for the same behaviour I faced using OruxMaps.
PS: phone IS rooted by a couple of week, but I'm facing this issue from the first day.
What the hell is going on? Any help, idea or trying suggestion is appreciated...
Many thanks!
Up?
I also see strange problems on the Y550-L01 connected to GPS.
In my case the GPS does not disconnect completely, but during car navigation the signal gets lost from time to time (tested with different navigation apps).
This is only the case when the Y550 is NOT connected to the charger. If I connect it to the power supply, GPS works quite reliable and accurate!
For me this sounds like a software problem (maybe connected to a power saving mode?). I hope a firmware update will fix this soon.
Even to me this is a firmware issue. Before of your answer, I was really beginning to think it's a fault of my phone. Now that I'm not the only one, I went back to think of a bug.
If it is a power save problem, then try to use this app to stop the power save mode :
https://play.google.com/store/apps/details?id=eu.thedarken.wl
(ultra light : 35K, free/no adds)
"Wake Lock gives you control over the Android Power- and WifiManager.
For example, you can force the PowerManager to keep the screen on or have the CPU still running in standby mode or make sure the Wifi connection keeps running at full performance.
You can use it on any android phone or tablet.
Use it to keep the screen on in full brightness or dimmed mode during movies or slideshows.
To make sure the CPU is still running in the background doing your tasks when you press the standby button."
Thank you for the report.
It seems that the new huaweï G620S has the same GPS problem :
https://www.google.fr/search?q=G620S+GPS+problem+fix
Any news of an Huaweï update ? Hope yes...
magooz85 said:
Hi all,
this is my very first post here on xda, so please forgive me if this is not the proper section for my thread. I searched for other thread about similar issues, but I didn't find anyone. I'm Italian, so I even hope to not being wrong in English writing.
I recently bought (on November 2014) an Huawei Ascend Y550-L01 (Android 4.4.4, EMUI 2.3, ROM B137), coming from a (Portuguese) Samsung Galaxy Y Pro GT-B5512. Soon I experienced a very strange GPS behaviour: GPS turns itself off. No problem in signal fixing, nor in quality or precision. It simply deactivates.
First I noticed this using the OruxMaps app (which works fine on many phones, even my old one), simply recording the track. Indeed, at the beginning the app was being killed (because of the integrated task-killer) when screen was off, but after setting it as a "protected" app, when I record a track, GPS works while screen is on and, if screen turns off, then most of the times (not always) GPS is deactivated from within Android settings.
I even received (from the purchasing time) some GPS errors while in the home screen... I don't remember exactly that error, but in a fast Internet search it was told being caused from the weather widget, precisely from the "actual position" setting. I deactivated it and added manually my town and those errors were gone.
Then I noted another strange behaviour: GPS turns off even in standby, during night. It is on "extreme precision" on evening and it's off at morning. Sometimes I notice these deactivation (in the notification menu or into the energy saving widget) while I'm using the phone (but always when screens is off), without any error or message popping out... It simply gets deactivated.
Any other experiencing this strange issue? What could be the cause? I sent a mail to official support, but they asked me to take the phone in a service point... I can't stay without phone, so I would like to avoid this if it's not strictly needed.
I think it's a ROM issue (said that even in the mail), but unfortunately still there is no alternative one (or at least I found none). I think also that (almost) every app that uses GPS suffers for the same behaviour I faced using OruxMaps.
PS: phone IS rooted by a couple of week, but I'm facing this issue from the first day.
What the hell is going on? Any help, idea or trying suggestion is appreciated...
Many thanks!
Click to expand...
Click to collapse
Hi! Better post your question in our small Huawei Ascend Y550 thread. Maybe there someone of us can help.
If you understand German:
http://www.android-hilfe.de/huawei-...gation-unzuverlaessig-nur-im-akkubetrieb.html
These folks have the same proplem, but no solution.
Try it while a charger is attached.
Hi all,
I am still on stock ROM (unmodified and unrooted) G925FXXU2QOH8.
I have noticed, that WhatsApp messages quite often come through exactly when I turn my phone on via the home button. So when I wake my phone. Coincidence? Unlikely
And yesterday someone tried to call me three times and I neither got the call nor a notification of the missed call until I woke my phone.
Does anybody know what is causing this? Seems like WiFi and mobile are effected. Somehow the phone does not seem to wake properly when it receives a message etc.
Hope someone can help me out
Hello while I really love this phone it's got a few annoyances. I created this thread to see if I'm the only one and if anyone else reports any more.
Frequent FC of the Google and Google photos app
Random things happening if phone is not restarted frequently (eg all sound went quiet until restart)
Keyboard skin doesn't change for lock screen
Let me know if your having these issues or if you have any not listed.
Bugs I've had so far:
- one reboot while using snapchat
- sometimes it takes a lot of time for the device to wake up
- autobrightness is terrible in low light conditions(stuttering and inconsistence)
- while streaming audio with bluetooth in my car the radio somtimes shows audio paused while it's still playing. In this case remote controls also stop working
My xperience
I only had the phone for four days, because I found a dead pixel on my screen. I am currently expecting a replacement or a refund. During that time I noticed that changing the theme does not change anything else besides the home and lock screens. There were some random drops in wi-fi connection. I also noticed a couple of stutters here and there. Two or three apps crashed on exit. I also miss the picture album widget with the swiping pictures on screen. That is not present here.
So no one seems to be getting any issues like me ?
Sent from my Sony Xperia XZ1 using XDA Labs
kistigun said:
Bugs I've had so far:
- one reboot while using snapchat
- sometimes it takes a lot of time for the device to wake up
- autobrightness is terrible in low light conditions(stuttering and inconsistence)
- while streaming audio with bluetooth in my car the radio somtimes shows audio paused while it's still playing. In this case remote controls also stop working
Click to expand...
Click to collapse
Agree about the autobrightness, it's inconsistent and keeps changing in low light conditions. Makes reading an absolute chore.
I'd also love a way to quick enable glove mode, my previous Samsung had that in the drawer menu.
for those of you who have owned sony phones, has there been timely updates to fix bugs like the ones being reported in this thread? some companies like to release updates with new features but without fixing bugs so im just making sure before i pull the trigger on an XZ1
thank you all!
I've had this issue after the recent update to build 47.1.A.2.324 . Google assistant doesnt work with Music ( default sony music app) . it used to work before this update, and it doesnt work anymore and asks me to set google music as the default music service.
WiFi signal drops when I hold my hand on the backside.
1. The phone seems to reboot itself frequently.
2. Sometimes no sound when alarm is going off. I overslept once because of this
3. Quite often no sound when phone is ringing. Need to reboot the phone for it to act normal again.
4. Crashing when picking up phone. Call goes to call waiting and phone rings again. When picking up there is a very loud biping sound throughout the conversation. This goes away when rebooting.
NockIt said:
1. The phone seems to reboot itself frequently.
2. Sometimes no sound when alarm is going off. I overslept once because of this
3. Quite often no sound when phone is ringing. Need to reboot the phone for it to act normal again.
4. Crashing when picking up phone. Call goes to call waiting and phone rings again. When picking up there is a very loud biping sound throughout the conversation. This goes away when rebooting.
Click to expand...
Click to collapse
I've aso had problem 2 & 3. I also overslept myself 3 times over this, very anoying!!!
Edit: found this on the sony forum on how to get smart lock menu back:
https://talk.sonymobile.com/t5/Xperia-XZ1/47-1-A-2-374-new-update-13-10/m-p/1268608#M467
Its a android 8 bug
Solution:
Disable trusted agents on security settings.
Restart phone
Enable security settings. Thats it.
NockIt said:
1. The phone seems to reboot itself frequently.
Click to expand...
Click to collapse
Oh god, i was going to change to the XZ1 this week after returning my Compact due to the rebooting, I thought they'd be different enough internals to not have the same issue. I guess its a Sony/Oreo issue then.
a freeze occourred waking up the phone from camera button. The camera button was set to "open and shot"
I had to reboot via vol+ and power...
Updated to 47.1.A.2.374 yesterday, sadly all bugs remain the same. And I can add one; the smart lock menu is empty and all smart lock function dont work anymore
kistigun said:
Updated to 47.1.A.2.374 yesterday, sadly all bugs remain the same. And I can add one; the smart lock menu is empty and all smart lock function dont work anymore
Click to expand...
Click to collapse
Its a android 8 bug
Solution:
Disable trusted agents on security settings.
Restart phone
Enable security settings. Thats it.
I can add another issue. That is bluetooth delayed when I watch video on youtube and play some games.
NockIt said:
1. The phone seems to reboot itself frequently.
2. Sometimes no sound when alarm is going off. I overslept once because of this
3. Quite often no sound when phone is ringing. Need to reboot the phone for it to act normal again.
4. Crashing when picking up phone. Call goes to call waiting and phone rings again. When picking up there is a very loud biping sound throughout the conversation. This goes away when rebooting.
Click to expand...
Click to collapse
Similar problems here even on the latest build 47.1.A.2.374. Also Google assistant frequently stops responding and then the phone becomes unresponsive and eventually restarts without prompting. Never had problems like this on the XZ when that was released. Seems to be some issues with Google services on this Sony hardware. Suggest everyone having issues pound the send feedback option and hope that someone in Google or Sony are listening!
My notification tones keep going off at random intervals and nothing's in the status bar that could've set it off.
Can confirm random reboots.
Bought the phone from clove and Amazon.
Amazon was horrendous reboots during setting the phone up - returned.
The clove one had no reboots until today, several times.
Some fkd up kernal CPU bogusness going on here.
Sony need to sort this.
I'll check with matlog tomorrow if anything stands out
Phone Idle is always 1st entry of battery drain list, does anyone have similar situation?
roytam1 said:
Phone Idle is always 1st entry of battery drain list, does anyone have similar situation?
Click to expand...
Click to collapse
same here.... battery life is suffering. Stock firmware was better
Hi,
yesterday i received my Amazfit Verge.
I could not test it completely before an upgrade to OS 3.2.0.7 (I was running 3.2.0.5) came in.
I tested this watch on 2 phones (samsung s9 plus and a Motorola G4 plus).
Before testing I did a reset of the watch.
Both show the same problem, when testing the warnings the incoming call warning does not work.
When a call comes in the warning also does not work on the watch, all other warnings work.
Is this a problem with the watch or is it a software glitch in 3.2.0.7 and how to solve this?
Do you have latest version of Amazfit app installed on phone with all permissions granted? If yes, try adding the phone/contacts/favorites to the notification settings in the app.
deboopi2 said:
Is this a problem with the watch or is it a software glitch in 3.2.0.7 and how to solve this?
Click to expand...
Click to collapse
Interesting - I just checked it with my Verge on 3.2.0.7. The first time I tried, it took relatively long - about 10 secconds - before I received the notification on my watch. The seccond time it came right away.
Have you tried to let it ring a little longer?
I'm running on release 2.6.7
Phone/contacts/favorites are hidden by the smart filter, they should not get selected.
I selected them anyway but the result is exactly the same
I've been waiting for 20 seconds now and I still do not have a notification on the watch.
I have exact same problem. Notification works only when I enable BT call function on watches.
I have the same problem, incoming calls are not visible. Samsung Galaxy S8 Android 9.
same problem here with a Samsung S10.....anyone solved it???
deboopi2 said:
Hi,
yesterday i received my Amazfit Verge.
I could not test it completely before an upgrade to OS 3.2.0.7 (I was running 3.2.0.5) came in.
I tested this watch on 2 phones (samsung s9 plus and a Motorola G4 plus).
Before testing I did a reset of the watch.
Both show the same problem, when testing the warnings the incoming call warning does not work.
When a call comes in the warning also does not work on the watch, all other warnings work.
Is this a problem with the watch or is it a software glitch in 3.2.0.7 and how to solve this?
Click to expand...
Click to collapse
Did you marked in Watch App, notification section call/phone? Do you getting all others notifications like message, calendar and ect.? In 3rd screenshot https://play.google.com/store/apps/details?id=com.huami.watch.hmwatchmanager you can see notification area. Here you must add all apps from yours phone from which you want to get notifications. If will not help, try reset factory settings of watch. For me working everything fine. Also, if in watch you will not see caller name, need to give permission of that (in smartphone). By the way i hope you understand that watch with smartphone must be connected via bluetooth?
P.S. I got 3 updates, now i got latest where was integrated Alexa (working in US only). With all software versions which i had and have working all notifications very well, included call. I guest you will not added it in Watch App notification section that. I have not Xiaomi brand smartphone too. Brand of smartphone havn't any effect in getting notifications I hope But maybe China manufactor don't like Samsung, so... you can chat with Amazfit support us.amazfit.com. But i'm really don't want to believe that this is true. Maybe something bad is with Samsung smartphones, cos this problem have a lot of people here
I had a Xiaomi Mi9 before and all worked very well!!
Now that i switched to a S10 with all the same settings that i had before, the notifications (whatsapp, telegram, gmail..ecc..) are perfect BUT if someone calls me the Verge vibrate for a second, the screen lights up and...stop!! no name, not even number calling.....when the call attempt ends it also notify me the missing call....!! I am pretty sure this problem is connected to samsung phones with pie but i really hope there is a way to fix it because i would hate to sell my Verge.....
agv83 said:
I had a Xiaomi Mi9 before and all worked very well!!
Now that i switched to a S10 with all the same settings that i had before, the notifications (whatsapp, telegram, gmail..ecc..) are perfect BUT if someone calls me the Verge vibrate for a second, the screen lights up and...stop!! no name, not even number calling.....when the call attempt ends it also notify me the missing call....!! I am pretty sure this problem is connected to samsung phones with pie but i really hope there is a way to fix it because i would hate to sell my Verge.....
Click to expand...
Click to collapse
I starting to think that this is not Verge problem, but problem is with Samsung smartphones, even newest models. I have none Xiaomi smartphone and it's working fine. It's not Samsung too. So i advise you to chat with Samsung support too, but ofcourse try to talk with Amazfit support us.amazfit.com (it's US, but only this support have live chat) if will be closed chat, try en.amazfit.com via mail support, but keep in mind today is saturday, so answer via mail or chat will be opened only from monday. It can be that these models working with each other with this problem
Answer from Amazfit Support:
Amazfit Support (Amazfit)
May 12, 23:02 PDT
Hi Milan,
Thank you for contacting Amazfit Customer Support. We apologize if the product caused you any inconvenience!
Could you please let us know where did you purchase your watch? Please kindly attempt the following steps:
1. On the home screen of the Amazfit Watch App tap Me in the lower right hand corner tap Setting tap Notifications setting tap the toggle switch to enable Push notifications tap App notification setting and select app in the list to enable or disable the specific notifications.
2. Make sure Not push, phone’s screen is ON is turned off.
3. Check if you enabled the Silent mode on the watch. If you enabled silent mode, you can't receive any notifications at all.
4. Make sure your phone notification bar is functioning. Please note that alerts will only appear on watch if they pop up on phone.
5. Open Amazfit Watch APP MeSettingSystem PermissionsAccess notificationstoggle on Amazfit Watch if it’s off. If it’s on, turn it off and on, reboot your phone, restart App and try again.
6.Open Amazfit Watch APPMeSettingSystem PermissionsAutostart tap Background operation permission setting to add Amazfit
Watch APP to the white list of background operation permission.
7. Open Amazfit Watch App Me Setting System Permissions Read contacts to allow Amazfit watch app to read your contacts in settings or the security app on your phone.
If the issue persists, please send us all the pictures and show us how you enabled the permissions. Then submit a feedback from the watch and Amazfit Watch App. Also send us the Amazfit ID to help us locate the issue.
Sincerely,
Seven
Amazfit Support
everything is checked and there is no incoming call anyway
yeah same preset answer they give to anyone.......
i also have all checked but the problem persists!!
I think it's standard form of answer to costumer. So consultants doing just copy - paste process from base of information. I think company request to do that from theirs workers, so don't be suprised. By the way i got some too about battery, but it's better to get answer like this one if don't get it at all, i had some examples when i did not got answers at all or answers into my questions
Any idea how to fix it?
zapas17 said:
Any idea how to fix it?
Click to expand...
Click to collapse
Try to do factory reset of watch. I tried several times and after last reset i could hear caller when i answered to ring. But i need to check again that. By the way i did some reset of watch without restore of my data. So maybe this can help you.
No helps. I think it's problem new software for verge.
Still happens on my new Note 10 too, damn it! Coming from Note8 I havent experienced this before.
Since I've tried everything i could to solve this issue, searched all forum/reddit/google for 14 hours, I'm asking for help here as a last resort.
Symptoms:
When i receive a phone call i tap on green to accept, the watch act as everything is fine (jumps to in call screen, starts to count...etc) but actually the phone doesn't accept it, just keeps ringing.
If i accept the call afterwards on the phone itself, everything works fine watch acts as a BT headset automatically.
Remarks:
Disabling+Enabling "bluetooth phone function" on the watch solves the problem temporaly, probably until next notification/sync.
-Amazfit Verge 3.2.2.0 3.2.3.0
-HTC U Ultra (tried with both stock Android 8.0 and LineageOS 9.0)
-Amazfit Watch (2.7.0.1) app permissions are enabled (call logs, camera, contacts, location, storage, telephone)
-Android Battery optimisation disabled for: Amazfit Watch, Amazmod, Bluetooth, Call management, Contacts, Phone, Phone services
-Amazfit Watch/Amazmod notification: As battery opt. above, but i've even tried it with adding everything (including all system apps)
-Enabled: Android settings/Google/Vocie/Allow Bluetooth request with device locked
-Tried it with and without Amazmod
-Watch factory reset, apps reinstall are done
Update: I did more testing, and the answer call does work if I wait at least 4-5 seconds before tapping the accept button.
It is probably an issue of both sides: the phone needs some time to accept the watch as a BT headphone, while the watch does not have any check/redundancy for accepting call during this phase.
DraX8 said:
Since I've tried everything i could to solve this issue, searched all forum/reddit/google for 14 hours, I'm asking for help here as a last resort.
Symptoms:
When i receive a phone call i tap on green to accept, the watch act as everything is fine (jumps to in call screen, starts to count...etc) but actually the phone doesn't accept it, just keeps ringing.
If i accept the call afterwards on the phone itself, everything works fine watch acts as a BT headset automatically.
Remarks:
Disabling+Enabling "bluetooth phone function" on the watch solves the problem temporaly, probably until next notification/sync.
-Amazfit Verge 3.2.2.0
-HTC U Ultra (tried with both stock Android 8.0 and LineageOS 9.0)
-Amazfit Watch (2.7.0.1) app permissions are enabled (call logs, camera, contacts, location, storage, telephone)
-Android Battery optimisation disabled for: Amazfit Watch, Amazmod, Bluetooth, Call management, Contacts, Phone, Phone services
-Amazfit Watch/Amazmod notification: As battery opt. above, but i've even tried it with adding everything (including all system apps)
-Enabled: Android settings/Google/Vocie/Allow Bluetooth request with device locked
-Tried it with and without Amazmod
-Watch factory reset, apps reinstall are done
Click to expand...
Click to collapse
Maybe problem that you using a lot of unofficial apps, software and ect.? By the way for me working fine, i'm with stock ROM, today got new update 3.2.3.0 where was fixed some bugs
xdauser2019 said:
Maybe problem that you using a lot of unofficial apps, software and ect.? By the way for me working fine, i'm with stock ROM, today got new update 3.2.3.0 where was fixed some bugs
Click to expand...
Click to collapse
Thank you for your reply/suggestion.
I tried it with clean watch+phone, no changes at all. New update did not helped either.
Meanwhile i got some testing time with it, and found out i have to wait before i accept a call.
After 5-6 vibrations on the watch i can accept the call with success, i would guess this bug is due to the phone needs some time to set the device as bluetooth headphone.
Probably the watch SW does not have any checks is it done already, also no redundancy for answering a call (sending the OK signal a few times for example, if that is possible).
make sure that in the bluetooth, you have the voice profile enabled for the watch connection
1immortal said:
make sure that in the bluetooth, you have the voice profile enabled for the watch connection
Click to expand...
Click to collapse
Thank you for the suggestion, it was enabled already.
Meanwhile i could do some testing, updated the OP also as:
I did more testing, and the answer call does work if I wait at least 4-5 seconds before tapping the accept button.
It is probably an issue of both sides: the phone needs some time to accept the watch as a BT headphone, while the watch does not have any check/redundancy for accepting call during this phase.
Click to expand...
Click to collapse
Do you think it is possible to solve this issue with Amazmod? Implementing some kind of redundancy or check for the phone watch app?
DraX8 said:
Thank you for your reply/suggestion.
I tried it with clean watch+phone, no changes at all. New update did not helped either.
Meanwhile i got some testing time with it, and found out i have to wait before i accept a call.
After 5-6 vibrations on the watch i can accept the call with success, i would guess this bug is due to the phone needs some time to set the device as bluetooth headphone.
Probably the watch SW does not have any checks is it done already, also no redundancy for answering a call (sending the OK signal a few times for example, if that is possible).
Click to expand...
Click to collapse
I recommend you to test without any amazmod and ect., problem can be with 3rd parties software, apps. If you still have problem when you using everything from manufactors: stock rom on smartphone/smartwatch and everything is updated, i recommend you to connect with Amazfit support https://en.amazfit.com/support.html or https://us.amazfit.com/contact (this is US support, but they taking advice for all costumers, keep patience checking, often is disconnected). I don't have this porblem, coz if say honest i don't talk right now over watch. But maybe need to test someday too. By the way for me need to wait a little bit too when watch will be vibrate after ring smartphone, it's all, if i'm not wrong, problem of Amazfit watches. With other manufactor i did not had this problem. But if say honest time between ring and vibrate is about 1-2 second in my situation
xdauser2019 said:
I recommend you to test without any amazmod and ect., problem can be with 3rd parties software, apps. If you still have problem when you using everything from manufactors: stock rom on smartphone/smartwatch and everything is updated, i recommend you to connect with Amazfit support https://en.amazfit.com/support.html or https://us.amazfit.com/contact (this is US support, but they taking advice for all costumers, keep patience checking, often is disconnected). I don't have this porblem, coz if say honest i don't talk right now over watch. But maybe need to test someday too. By the way for me need to wait a little bit too when watch will be vibrate after ring smartphone, it's all, if i'm not wrong, problem of Amazfit watches. With other manufactor i did not had this problem. But if say honest time between ring and vibrate is about 1-2 second in my situation
Click to expand...
Click to collapse
I did, factory reset on both watch and phone stock rom (then LineageOS 9.0 on phone), the same issue.
Wrote to official support also today, no reply yet thou.
I also have a second of lag when the watch starts to ring, but i have to wait over that a few seconds to be able to really answer the call.
It is usable now with waiting 4-5 seconds, i just have to not forget it and answer the call too fast...