Amazfit Stratos: Run was not saved after I stopped it - Amazfit

Hello everyone
So this is what happened:
- I was running for 45 minutes, around 10km, everything was looking fine, watch was properly tracking every aspect of the run
- I pressed top button to stop recording but nothing happened.
- I pressed again, thinking that it didn`t register my click first time.
- it lagged for few seconds and then displayed "start" screen with options to choose: "run" or "walk" I think... so it went to generic Start Action menu...
my run is gone I think...
Two questions:
- is there a way to recover my data?
- where do I upload the error zip?
Thanks

Related

On 'Cold Boot' my TG01 restarts 2-3 times

If I power my TG01 off completely by pressing and holding the power button and then confirming the 'Do you want to switch off' message, when I restart the device by pressing and holding the power button until the TG01 vibrates slightly, it mostly starts up, gets as far as the 'Today' screen image appears to stall on the installation of the battery and signal strength icons and then goes off immediately before restarting. It will do this 2-3 times before finally starting normally. As a rule, if the 'Messages' pane appears on the 'Today' screen, it is going to stay on. Once started this way, it will be fine until the next reboot.
Once the unit has come on, the screen brightness is at a lower level than I normally have. I used to open up the 'Power' settings from the 'Settings' page of icons, but I have found that putting it to sleep with the Power button then bringing it back out of sleep again with the Power button is quicker and returns the backlight to the correct settings once more.
Is this typical? I don't have anything fancy in the Startup folder, AutoKeyLock, BattClock, poutlook, SMSLoader and USSD. Of those only BattClock is a non original item. I have installed HTX X-Button which I assume is auto starting, but nothing more fancy than that.
You didn't mention which ROM build you are running, but I certainly recognise exactly the same symptoms ocurring while running the original WM6.5 build.
I have just updated to the new build (5005-0001.76) released yesterday; although I have not completed a full re-build of all apps I previously had installed, I have not noticed the same effects.
I'm hopeful that that is one of the bugs which have been ironed out..... time will tell !
try uninstalling ur last installed program(s)
also this utlitiy ,
run all items in the first cleanup menu except for the dead registry option(it will fuccup ur fone) it should halp
also try deleting everything in the notification queue(2nd) window
http://www.dinarsoft.com/memmaid/
kevinpwhite said:
You didn't mention which ROM build you are running, but I certainly recognise exactly the same symptoms ocurring while running the original WM6.5 build.
I have just updated to the new build (5005-0001.76) released yesterday; although I have not completed a full re-build of all apps I previously had installed, I have not noticed the same effects.
I'm hopeful that that is one of the bugs which have been ironed out..... time will tell !
Click to expand...
Click to collapse
I'm just (as we speak - or should that be type?) downloading the newer ROM build from Toshiba. I'll report back once I've backed up my details and updated.
I'm not tremendously bothered by the behaviour, just wanted to know if it was a 'fault' or a 'characteristic'!
I have updated my ROM as suggested, this does appear (in very limited testing...) to have cured the restart problem.
The brightness problem is still there (I still have to press the power button to send the device to sleep and wake it up to restore the correct backlight level) but this is less annoying than having to wait for 2-3 complete boots to finish before the device eventually starts up.
Thanks for your advice KevinPWhite.

A Second First Start?

I like so many other have recently received my gTablet. I have done nothing so far except to charge it and start it to become acquinted with the interface.
When I powered on this morning the system seemed to hang at the gTablet logo. After about 1 minute I pressed the power on button to power off. The next time I restarted I had to go through the whole startup sequence again.
The only thing I noticed that changed is the background. Before it was leaves falling on water, now I have a ocean view.
Has anyone else experienced something similar?
Thanks
Yes, this happened to me too. I updated it, and after two or three startup/shutdowns I got the setup wizard. I did not get this when I started it up the first time.
I then found that I needed to re-install flash. The wallpaper can be changed back by long pressing the screen and selecting Wallpapers -> Live Wallpapers.

[Q] Semi-Brick : is it the hardware or Software

My tablet is HKC P077A with 8GB ROM, 512 RAM and a 7'' Touch screen (Android 4.0.3). I am having 2 problems
When I switch on the tab, first "HKC" logo comes to screen and then disappears to show "android". This is standard. But after that the thing wont move forward. Just keeps on showing "andriod" with a flashing like thing implying the loading process. But after long wait there is no start screen and nothing changes. It just hangs there....
But if somehow got it to get into normal working(I donno how, but It sometimes boots ok and gets into normal working mode, with home screen and apps and everything). So once I get it right the other problem I am having is that the touch is giving VERY bad response. I have to click at spots multiple times to select that thing. Also the response is very slow. Its like the tablet is hanged. But when I tried connecting a mouse (through OTG) and everything works fine again. Is my touchscreen gone bad..??
I am already done with, reset (from "settings> backup and reset") [I cant find how to do factory reset on this model from "off" state(read below)]
I have tried to get into reset screen by pushing "Power Button+Vol up" button. Then I know the tab gets turned on (I can hear a small white noise from the loudspeaker) but nothing comes to screen. So the "Robot with heart open" is never shown. I also tried using "power button + Volume down", this takes me to a screen written in chinese. Now, I don't know Chinese but from the look and feel, its a troubleshooting window, where I can check weather components of my tablet are working (eg. I click one menu(with difficulty), then the front cam turns on, another menu makes loud sounds from speaker and another flashes many colors in screen etc). I found that most are ok except something called "T" (On the screen, its the last item to the right, is it "touchscreen"??)
So, what can I do to get my tab to work smooth again..? Is the touchpad having trouble..? Need I do any specific troubleshooting..?? Any Ideas on which key combinations to get on to the "factory reset" menu from off state..??
Also can u please specify the key combinations to the tablet factory-reset menu from "off" state.

keyboard delay

Hello people,
I've noticed a weird problem with my Samsung S2 running Gingerbread 2.3.5 (yes, I know, it's old... but the last time I've upgraded to anything more recent, the battery lasted less than one day. I'll happily receive any advices on newer versions tho).
let me tell the story:
the phone is "quiet", with the screen black.
...a message arrives! (doesn't really matter if it's an SMS, Telegram, WhatsApp or anything else. Even notes will be affected, everything needing a keyboard input)
I press the power button, the phone "wakes up" and shows me the lock screen - I've set a static image with the time in the upper area.
so the phone starts running and I go to the desired application (sms/telegram/notes/etc...)
the keyboard (swype keyboard, but is the same also with my other 2 keyboards) shows up.
I try to input letters, words, but nothing gets written. If I press longer to get to the special character selection, I can't select any of them, all I can do is touching the Back button and return to the keyboard.
I usually press a key from time to time to see when the keyboard starts working.
After a delay of ~15 seconds it starts working, but I have to be careful not to let the phone going back to sleep or I will have to endure the delay again (this usually happens during a chat and it's quite annoying).
so, I suspect there is some application that gets stuck after waking up from the lock screen, but does anyone have experienced this? Any ideas on what it could be?
Thanks!
Best Regards
Max

Expanded screen mode (autohide top status bar and lower nav bar) locks up tablet

I have been running my Tablet Z (pollux_windy) on the latest Oreo release (15.1) . Have installed a few nightly updates - but the problem below keeps occurring.
It generally runs really well - but I have discovered something that seems to be causing issues for me and wondered if anyone else has the same issue.
I like to use the full real estate of the screen, so found the Settings/Display/Expanded desktop setting that lets you hide the top status bar and the lower navigation keys go into autohide mode (you swipe up from the bottom of the screen to see them).
First time I enabled them all seemed great - Then I left the tab and the screen timed out.
I tried to wake it up (using the power button or double tap on the screen) - Nothing.
Tried this quite a few times over a few minutes.
Did a Hard power off.
Restarted eventually. Seemed ok until the screen blanked out - then the same as above.
I did eventually get the screen to wake back up without a reboot by trying the double tap and quick press of the power key. But it took quite a few attempts.
Finally I turned the full screen mode off (ie brings back the status bar and nav controls) and everything was back to normal behaviour - ie always wakes back up when required.
I have tried changing the expanded desktop mode several times and it always locks things up after the screen times out so have now given up on it.
Anyone else finding that setting this mode causes lockups?
robjg63 said:
I have been running my Tablet Z (pollux_windy) on the latest Oreo release (15.1) . Have installed a few nightly updates - but the problem below keeps occurring.
It generally runs really well - but I have discovered something that seems to be causing issues for me and wondered if anyone else has the same issue.
I like to use the full real estate of the screen, so found the Settings/Display/Expanded desktop setting that lets you hide the top status bar and the lower navigation keys go into autohide mode (you swipe up from the bottom of the screen to see them).
First time I enabled them all seemed great - Then I left the tab and the screen timed out.
I tried to wake it up (using the power button or double tap on the screen) - Nothing.
Tried this quite a few times over a few minutes.
Did a Hard power off.
Restarted eventually. Seemed ok until the screen blanked out - then the same as above.
I did eventually get the screen to wake back up without a reboot by trying the double tap and quick press of the power key. But it took quite a few attempts.
Finally I turned the full screen mode off (ie brings back the status bar and nav controls) and everything was back to normal behaviour - ie always wakes back up when required.
I have tried changing the expanded desktop mode several times and it always locks things up after the screen times out so have now given up on it.
Anyone else finding that setting this mode causes lockups?
Click to expand...
Click to collapse
Hello!
Please write your problem to an official bugreport https://wiki.lineageos.org/bugreport-howto.html to let the LOS developers team about the encountered issue.
Thanks. Signed up to add the fault and found someone witha different device reporting the same bug around a week ago.
Added my confirmation of the problem with different hardware.
Fingers crossed someone may have a look at it when time allows.

Categories

Resources