We are looking into why the device name is now showing where it should not.
It is a very minor thing but these are supposed to be unbranded so we are checking it out.
universal launcher gps bad response problem when updating to faw 1.1 in version 1.0 does not happen
No it’s fine.
Just unfortunate for you for some reason.
The weather issue is nothing to do with the firmware.
Did you factory reset?
Its always a choice if you do or not but if you don’t there may be issues later on.
It works fine in v1.1 if you enable GPS and WiFi and google location accuracy.
After first weather update you don’t need GPS.
This is all working well in the stock launcher. Any issues with the UL is separate from this and according to Eric… It’s ok.
After the update to faw1.1, the first GPS lock also take time for me. You may install the app “GPS Data”, and delete/download a-gps data to speed up the first lock. Without a recent a-gps data, the first lock may take up to 30-45 minutes to obtain the info from the GPS satellite (the transmit speed of a-gps data is very slow from the satellite).
1 Like
@tobor
Yes you are exactly right.
This is because the watch is built and configured in favour of China.
Not to mention the GPS antenna is extremely small and not very sensitive.
In the FAW international firmware it should be a little quicker but not much.
Wiitee and the factory sets the nvram partition and obviously the FAW firmware does not change this partition.
This is because it contains the IMEI, GPS config, BT Mac address and WiFi Mac address.
However, one of the improvements that we will talk to them about it making the GPS config adjustable for different regions.
It makes sense but it is also not as easy as it sounds…
We will see 
2 Likes
Hello Dear Pablo11,
1: I think everyone appreciates your work (your work for us) 
2: everyone respects your private life. (family and your work)
3: over time, I wrote a quote that Stephen Hawking wrote to impatient people.
I wrote this quote for your protection, not against you ! You may have misunderstood so you deleted it. Anyway, you know why you deleted it.
4: please write that Face Unlock will work someday? 
KP2 AND LEM14 is out now! 
Thank you for patiently reading this post and not deleting it !
I have been living in a wheelchair for three years, because of an accident,
believe me I know what it means to wait patiently for something! 
I remain respectfully.
Best Regards
Michel56 
Face unlock is removed by Android for a very good reason and I’m very sorry but no, it’s not coming back.
End of discussion.
1 Like
OK
I’m understand 
Thank You
Best Regards
Michel56
I’m not yet sure about this, so I’m asking it as a question … I updated to version 1.1 the day before yesterday. Does anyone else have the sense that:
a) the battery is draining more quickly?
b) it’s taking AGES to charge? - on both the charging cable and the battery charging unit. It’s taken about an hour and a half to charge from 28% to 42% tonight - which I feel is much longer than before.
I haven’t been scientific in measuring this, but I’ve noticed both of these things over the last 36 hours. I’d be interested to know whether others have experienced the same thing.
I will look into it and see if I have any issues…
Thanks
1 Like
I am seeing nothing unusual here with charging.
Has anyone else had issues?
2 Likes
Okay, I charged it overnight to 100% and this morning the discharge rate seems okay, no worse than version 1.0. I’ll let it discharge to a low percentage then check on the re-charge rate.
1 Like
Every time we factory reset, there will be a whole lot of updating the first day in the background, with Google services etc. This causes high battery usage, so we can never trust the usage from first day after updating or purchase.
4 Likes
Very good point! As a bonus, it seems to me the weather app is updating itself…
2 Likes
Just wanted to update on this location issue with Universal Launcher. According to Eric it’s NOT ok now. The Yahoo weather API changed and it won’t work any longer. He released 3.5.1 but something is still broken with it. I cannot use it all any longer due to not stop overlay messages even on the new version. This is not an issue with 1.1. It started for me on 1.0, I upgraded to 1.1 thinking it might help but it did not since it was unrelated.
Also unrelated to the above, one new thing I noticed now is if I actually use the watch to do anything, like browse the web for a bit or talk on a video call for a long period of time, I’m starting to get these hellacious warning sounds and a message that takes over the screen about the battery overheating and telling me to remove it. Why am I getting that now and how can I turn this off?
I was trying to tell you that it was not related to the firmware apart from the silly message which is now removed from the next update (you will be warned but it is not going to tell you to remove the battery)
About the UL… This is what I was interested in you testing on stock firmware…
The heat warning is normal for using the watch for video calls for any calls that last more than a couple of minutes.
The screen, the radio activity (Wi-Fi or 4G /3G cellular) and all inside a very small, sealed space. It’s gonna get hot and if gets over 50 °C it will warn you.
If I browse the Web and only Wi-Fi or cellular is enabled (not both, and BT off) then I don’t get issues.
However, if I browse the Web for long periods of time with WiFi, cell data and BT enabled, I notice the heat.
I think for you it would be a good idea to flash back to stock for comparison and try and see if you have any issues like these you have mentioned.
3 Likes
Understood. It was getting hot before but I wasn’t getting screamed at so I just want to be clear I’m not blaming the firmware update for the heat, only this crazy warning. The first time it started going off it went crazy (alerted about 20 times in a row) and my wife looked at me like WTF? It was obnoxious.
Regarding UL, I just wanted to make it clear going back to stock was NOT going to fix it. The good news to anyone reading here, @Eric_Crochemore fixed the issue and posted an updated 3.5.2.
1 Like
We will discuss some possibilites to reduce the thermal discharge of the system.
About the warning you don’t have to worry, it doesn’t indicate any immediate danger.
You can check this post for more information:
3 Likes
It would have been much better if it had to go below a certain temperature or wait for a certain amount of time before it was allowed to alert you again
This would be the ideal behaviour, but i assume this warning app was designed in a time were advanced security and throttling protocols weren’t implemented yet.
It basically just register the warning temperature of 50°C and then constantly fires the alarm, even if there is no immediate danger.
If it would come to this the device would have already shut itself down, either due to the kernel battery driver or the temperature protection on the battery pcb itself.