Unihertz Atom Bluetooth Connection Lost Dexcom G6

roco5 commented 5 years ago

Xdrip will not stay connected to the sensor, as after about 15-20 mins of being disconnected, xdrip phone gets stuck in the "Scanning" state and the only way I can get it to connect again, after losing the connection, is to restart the phone. I have tested seemingly every setting in xdrip, android, fitbit, and specific to atom, and can't say that any configuration has helped at all.

Settings: Unihertz Atom running new November 2018 build of firmware Xdrip 12/27/2018 Nightly Build Fitbit Versa running Glance and new 3.0 software

Observations:

The connection seems very stable between sensor and xdrip when the phone and sensor are in range - to get readings. When the phone goes out of range for more than 1 or two readings, the data stops getting captured from the sensor and the phone gets stuck "Scanning". The only way I know how to resolve this is to reboot the phone (Restarting the collector does not seem to reslove this.)
One user has suggested that when they try to use SSW3 watch and atom phone, with xdrip, they have the same connectivity problems I do, but when they don't use the watch the phone functions much better. I have a Fitbit Versa with updated 3.0 Fitbit firmware and need to be able to use the phone and watch combination, so I am reluctant to call it a problem using a watch.
It also seems possible that after watching a video or surfing on the phone, the phone misses a couple of readings and gets stuck scanning as well, but I have not completely verified this.

+++

The phone has a perfect form factor for a collector, and I would very much like to work with you to get it to function properly, for me and for others. Thank you for your assistance.

jamorham commented 5 years ago

It sounds like the phone's bluetooth stack has problems. I don't have one of these phones to test with. If anyone can loan me one I should be able to discover more quite quickly.

AdrianLxM commented 5 years ago

The Atom BT stack is quite messed up it seems. I also have problems keeping the BT connection up with a combo pump and with a Dana RS. So neither BLE nor older BT standards seem to work reliably.

It would be good if you could contact the tech support of unihertz. They will give you a guide how to send them system logs. I hope if they get them with different setups they will find a fix. I don't have much hope as the December update still had the may security patch level of android :(

tech-support-unihertz commented 5 years ago

Hi, We are the technical support of unihertz. As the document describes, can Xdrip app give some instructions and why is it broken? log-check-20190109.pdf

2flea commented 5 years ago

Hey guys, I am currently using ATOM (latest firmware) together with xDrip (latest nightly) reading G6 and AAPS (latest dev) with Dana RS pump. It works so far (> 1-2 weeks) without the need to do regular restarts. When I try to add my Sony SWR50 I get BT communication problems - mostly with AAPS.

I was in contact with Unihertz since I got the phone back in October and we have tried to identify what's amiss (I guess the log above is from mine from end of Nov) but without any success.

I really would like to use the ATOM with my setup together with a smartwatch - this would be my idea of a perfect system for looping.

Please let me know if I can help with any testing.

I have made screenshots of my current system and app settings for your reference: https://photos.app.goo.gl/bi8axT9pnRTHBuH9A

Adrian, Unihertz says on their ATOM FB group that the patch level was updated with their latest FW but not recognized by Google.

jamorham commented 5 years ago

@tech-support-unihertz I am the developer of the OB1G5Service. The dexcom transmitter wakes up periodically (every 5 minutes) for a short period of time and during that wake up window we need to connect to it to retrieve the data. That is what the service is doing.

I don't have an atom device to test here in the lab but the reports from users have been that the whole phone needs to be rebooted which in my experience implies that it is quite likely the android bluetooth subsystem itself is crashing.

tech-support-unihertz commented 5 years ago

@jamorham Can you help analyze this log? (Thanks for the log provider @2flea :) https://www.dropbox.com/s/0f2cmdvxjqmt5ni/mtklog_20181127.zip?dl=0 From the log analysis, Bluetooth data interaction is normal from 21:02 to 21:38. At 21:39:38 seconds, because there is no data interaction, Bluetooth switches to IDLE mode, causing the connection to be disconnected. Can you tell us if the xdrip app received an error code when the problem occurred?

2flea commented 5 years ago

As far as I remember the log set above was done with the pre-release firmware including the "Bluetooth has stopped" message not the current version. Also I had different settings in the Atom battery saving. @tech-support-unihertz, @jamorham I can provide new log data with the current setup and then with the Sony smartwatch if you want. Let me know if should add anything special in xDrip log settings.

roco5 commented 5 years ago

Hey guys, I am also currently using ATOM (latest firmware) together with xDrip (latest nightly) reading G6, and fitbit versa and have struggled to keep a connection to bluetooth when adding a smartwatch (Fitbit Versa) to the configuration.

History:
Test1: Tried atom and versa with xdrip and Atom October firmware. Tested every battery, fitbit, and collector setting combination imaginable with no joy. Result1: Had tons of connection drops and the only way to resolve them was to reboot phone. Happened every few hours.

Test2: Updated atom firmware to November (latest) and tuned xdrip, fitbit, and android settings. Also "Forgot" Sensor in Bluetooth, and let xdrip populate a new Dexcom Bluetooth connection. Still using versa smartwatch. Result2: Seemed to stay connected a little better, but still had disconnects when the phone was out of range and brought back into range. Many unrecoverable disconnects a day that required rebooting the phone to solve.

Test3: Did a factory reset with latest november atom firmware installed. Installed xdrip but not fitbit versa yet. Result3: So far, we are going on about 36 hours without needing to reboot, and data capture has been consistent where phone has come in and out of range with sensor after being separated from more than 25 mins.

Test4: Will install fitbit versa on atom, and try to use Versa smartwatch with Test 3 configuration and collecting log data on xdrip and per unihertz instructions. Result4: ????

jamorham commented 5 years ago

I have received a unihertz atom phone to test with. It is early days, but my initial findings are that the problems are due to the manufacturers power saving additions to android which shut down xDrip.

PowerSaveService: forceStopThirdApp processName: com.eveningoutpost.dexdrip pid: 6814, packageName:com.eveningoutpost.dexdrip

This happens even though the custom setting for the app "Background activity" is enabled for xDrip and that xDrip is already supposed to be excluded from battery optimization via its standard android runtime permission for the same.

The MTK setting for Intelligent power saving standby is also disabled as well as battery saver in the general battery settings.

xDrip is running a foreground service and does not target oreo sdk (targets sdk 23)

This is running on an atom with build number 20181130

As far as I can tell the custom setting for whether Background activity is allowed for a specific app either is not implemented or doesn't work within the framework. I could be wrong but that is exactly how it looks from my initial testing.

roco5 commented 5 years ago

Could someone from Unihertz please comment on what can be done to get this fixed, so that we can use the phones and watches effectively with Bluetooth CGM softwares?

On Tue, Feb 12, 2019, 5:22 AM JamOrHam notifications@github.com wrote:

I have received a unihertz atom phone to test with. It is early days, but my initial findings are that the problems are due to the manufacturers power saving additions to android which shut down xDrip.

PowerSaveService: forceStopThirdApp processName: com.eveningoutpost.dexdrip pid: 6814, packageName:com.eveningoutpost.dexdrip

This happens even though the custom setting for the app "Background activity" is enabled for xDrip and that xDrip is already supposed to be excluded from battery optimization via its standard android runtime permission for the same.

The MTK setting for Intelligent power saving standby is also disabled as well as battery saver in the general battery settings.

xDrip is running a foreground service and does not target oreo sdk (targets sdk 23)

This is running on an atom with build number 20181130

As far as I can tell the custom setting for whether Background activity is allowed for a specific app either is not implemented or doesn't work within the framework. I could be wrong but that is exactly how it looks from my initial testing.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/NightscoutFoundation/xDrip/issues/734#issuecomment-462702776, or mute the thread https://github.com/notifications/unsubscribe-auth/AGoAaDFEYkQPCrNbCFEEKj0UTdWmLq_Jks5vMpX0gaJpZM4ZySTM .

jamorham commented 5 years ago

Okay, I think I have found where this is actually controlled:

Go in to Android Settings -> Smart Assist -> Power Save Manager -> Tick xDrip on in the whitelist

jamorham commented 5 years ago

100% capture rate so far on G5 with that setting applied. Using 10th Feb nightly.

roco5 commented 5 years ago

Yes we have tried it with that setting and it works!

But....the biggest issue we are having now is if we try to use a Bluetooth watch with the phone it seems to break the Bluetooth stack on the phone.

On Wed, Feb 13, 2019, 7:19 AM JamOrHam notifications@github.com wrote:

100% capture rate so far on G5 with that setting applied.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/NightscoutFoundation/xDrip/issues/734#issuecomment-463178937, or mute the thread https://github.com/notifications/unsubscribe-auth/AGoAaLZUDF3UOaCty38XIkLOGS7GHZh-ks5vNALRgaJpZM4ZySTM .

tech-support-unihertz commented 5 years ago

Dear Sir, Sorry for the late reply. The attached file will guide to keep the apps not be cleaned up by the background.

Regards,

Technical Support

+86-21-62207593 Ext 8007 www.unihertz.com

From: JamOrHam Date: 2019-02-13 17:40 To: NightscoutFoundation/xDrip CC: tech-support-unihertz; Mention Subject: Re: [NightscoutFoundation/xDrip] Unihertz Atom Bluetooth Connection Lost Dexcom G6 and Fitbit Versa (#734) Okay, I think I have found where this is actually controlled: Go in to Android Settings -> Smart Assist -> Power Save Manager -> Tick xDrip on in the whitelist — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

roco5 commented 5 years ago

I assume you have a patch file or something? It was not linked to or attached to your last message....

tech-support-unihertz commented 5 years ago

I assume you have a patch file or something? It was not linked to or attached to your last message....

How to ensure App will not be cleaned up.pdf

roco5 commented 5 years ago

Thanks for those instructions. My xdrip has been running fine on atom with those settings.

The issue is that within minutes of indroducing another Bluetooth device to the phone(atom) - especially a watch (Fitbit versa), the watch fails to.sync after one or.two syncs and then the phone fails to collect readings.from the.sensor.as.well???

It is.acting like.a.crashed.bluetooth stack??

On Wed, Feb 13, 2019, 10:01 PM tech-support-unihertz < notifications@github.com> wrote:

I assume you have a patch file or something? It was not linked to or attached to your last message....

How to ensure App will not be cleaned up.pdf https://github.com/NightscoutFoundation/xDrip/files/2863094/How.to.ensure.App.will.not.be.cleaned.up.pdf

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/NightscoutFoundation/xDrip/issues/734#issuecomment-463468045, or mute the thread https://github.com/notifications/unsubscribe-auth/AGoAaD4CHtkym23DhBNH3cR5PyiYri8Uks5vNNGBgaJpZM4ZySTM .

jamorham commented 5 years ago

Okay so we have resolved the power saving issues with xDrip getting shut down. Now beyond that in extended testing (>12 hours run) I can see what looks like bluetooth stack crashing which I'm looking at now.

tech-support-unihertz commented 5 years ago

Dear Sir， Some users feedback that this issues may be related to colleagues using Watches. We think we need more log file for analysis this issues. Wolud you please open the MTKlog, restart the phone,when you find the abnormal bluetooth connect with your watch, record the time(make a screenshot), then send us the log file and the screenshot. The attachment will guide you how to catch the log file.(BTW: Click the menu Open Bluetooth log Tool-> More Settings -> Firmware Test Situation: -> choose debug) Wait for you feedback.

tech-support-unihertz commented 5 years ago

Okay so we have resolved the power saving issues with xDrip getting shut down. Now beyond that in extended testing (>12 hours run) I can see what looks like bluetooth stack crashing which I'm looking at now.

Thank you for your support. If you have any questions about the Bluetooth stack, please feel free to communicate with us. Thank you.

tech-support-unihertz commented 5 years ago

The attachment will guide you how to catch the log file.(BTW: Click the menu Open Bluetooth log Tool-> More Settings -> Firmware Test Situation: -> choose debug) How to get Bluetooth mtklog for Atom.pdf

gobeti commented 5 years ago

@tech-support-unihertz I am the developer of the OB1G5Service. The dexcom transmitter wakes up periodically (every 5 minutes) for a short period of time and during that wake up window we need to connect to it to retrieve the data. That is what the service is doing.

I don't have an atom device to test here in the lab but the reports from users have been that the whole phone needs to be rebooted which in my experience implies that it is quite likely the android bluetooth subsystem itself is crashing.

@jamorham The same issue seems to be the case for the FINOW Q1 PRO --. Android 6 (using as collector and uploader to nightscout for a G6). Linked to #648 Exactly same issue. It is very unstable because of this. Only solution found to turn off and on the BT until it eventually connects again. Otherwise it keeps scanning without success. Let me know if I should send some logs as well or it is not necessary.

roco5 commented 5 years ago

Okay so we have resolved the power saving issues with xDrip getting shut down. Now beyond that in extended testing (>12 hours run) I can see what looks like bluetooth stack crashing which I'm looking at now.

@jamorham - any luck identifying bluetooth stack crashing or what is causing it?

tech-support-unihertz commented 5 years ago

Hello， Some users feedback that this issues may be related to colleagues using Watches. So can you please confirm whether you use the watch at the same time?Can xDrip be used normally after removing the watch. Wait for you feedback.

Ringelschlingel commented 5 years ago

After removing the watch and restarting the phone xdrip starts working fine again. It is not possible to use watch and xdrip at the same time

roco5 commented 5 years ago

And I am pretty sure that the only reason that xdrip works by itself is because it has a automatic in app feature that allows it to restart the unihertz atom Bluetooth stack after it crashes.

On Sat, Mar 2, 2019, 1:36 PM Ringelschlingel notifications@github.com wrote:

After removing the watch and restarting the phone xdrip starts working fine again. It is not possible to use watch and xdrip at the same time

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/NightscoutFoundation/xDrip/issues/734#issuecomment-468947627, or mute the thread https://github.com/notifications/unsubscribe-auth/AGoAaIpMG2QJU43ZFX2mnu_veP6IFFwEks5vSsTKgaJpZM4ZySTM .

thomasmenges commented 5 years ago

@roco5 I think you're right ! But what could be the recommendation for @tech-support-unihertz ? In my opinion the bluetooth software implementation on the ATOM smartphone isn't up to date and should be replaced by a better one.

Ringelschlingel commented 5 years ago

Edit - two days later (since using the watch the last time) and I still have several crashes which make it necessary to restart the phone :-(

tech-support-unihertz commented 5 years ago

We need a new log to analyze the problem. The attachment will guide you how to catch the log file.(BTW: Click the menu Open Bluetooth log Tool-> More Settings -> Firmware Test Situation: -> choose debug) How to get Bluetooth mtklog for Atom.pdf

tech-support-unihertz commented 5 years ago

Thank you all for your support.

We have released a new temporary version of atom, which may solve the Bluetooth problem. Please download the new version from the following URL. Please copy the downloaded .zip achive to your ATOM for upgrade as shown in the attachment. By the way, if the new version still has problems, please help grab the Bluetooth log. phone upgrade from Internal Storage for Atom.pdf

https://drive.google.com/file/d/1mg6MMzM2qxi2bGMK3Rnw1uC15bHtglub/view?usp=sharing

dv1 commented 5 years ago

@tech-support-unihertz Could the BT stack be made open source? So the community can help with testing, analyzing, bugfixing?

szpaku80 commented 5 years ago

@tech-support-unihertz I made an update. Unfortunately, data from the DEXCOM G5 transmitter are lost, they come every 10 minutes. :( I will try to attach a Bluetooth log file

szpaku80 commented 5 years ago

@tech-support-unihertz I have a log file, I can upload . Can I send to an email address?

thomasmenges commented 5 years ago

@szpaku80 Yes you can send it to tech-support@unihertz.com

By the way: The file is often too big to send via mail. Here you have to use a cloud service where unihertz can download the uploaded file.

tech-support-unihertz commented 5 years ago

@tech-support-unihertz I have a log file, I can upload . Can I send to an email address? Thanks for your support. We have downloaded the log For this log, can you describe the process of xDrip-DexcomG5 working abnormally. @jamorham Can you help analyze the log of xDrip-DexcomG5 working abnormally from @szpaku80 https://drive.google.com/open?id=1048rYAOmooqf_ga_5_4kMiWL-kpIETwV

adrian-hidothealth commented 5 years ago

Losing every 2nd value was typical for having the "smart" power feature activated on Jelly/Atom before this update. @tech-support-unihertz could it be that it got now activated by default? I've seen that you worked on the power saving features in the change-log.

tech-support-unihertz commented 5 years ago

Losing every 2nd value was typical for having the "smart" power feature activated on Jelly/Atom before this update. @tech-support-unihertz could it be that it got now activated by default? I've seen that you worked on the power saving features in the change-log.

What is "smart" power? Can you describe it? Thanks!

adrian-hidothealth commented 5 years ago

@tech-support-unihertz on the Jelly you can find it under Battery -> "Standby intelligent power saving". If you activate that, it will only wake up for every second sensor value. As I haven't got my Atom with me, I don't know how it is called there. But it must be similar.

szpaku80 commented 5 years ago

My settings: Smart Assistant / Power save manager / White list: xDrip + - selected Ruffy - selected AndroidAPS - selected

DuraSpeed on xDrip + - selected Ruffy - selected AndroidAPS - selected

Battery / Battery optimization: Not optimized: xDrip + - selected Ruffy - selected AndroidAPS - selected

I just found one new setting that I missed. Smart Assistant / Battery Saving mode / Battery profiles My profiles: Bluetooth - on I'm changing it to "off" now and see if it works.

tech-support-unihertz commented 5 years ago

@tech-support-unihertz on the Jelly you can find it under Battery -> "Standby intelligent power saving". If you activate that, it will only wake up for every second sensor value. As I haven't got my Atom with me, I don't know how it is called there. But it must be similar. We did not automatically add it to the whitelist. The 《How to ensure App will not be cleaned up》 file will guide to keep the app not be cleaned up by the background.

roco5 commented 5 years ago

Thank you all for your support.

We have released a new temporary version of atom, which may solve the Bluetooth problem. Please download the new version from the following URL. Please copy the downloaded .zip achive to your ATOM for upgrade as shown in the attachment. By the way, if the new version still has problems, please help grab the Bluetooth log. phone upgrade from Internal Storage for Atom.pdf

https://drive.google.com/file/d/1mg6MMzM2qxi2bGMK3Rnw1uC15bHtglub/view?usp=sharing

If I install this version, can you send me instructions to undo it if it doesn't work? We rely on this phone for tracking and managing blood sugars and cannot be without it for any period of time. Right now with xdrip's restart bluetooth feature, we are able to keep the atom working despite bluetooth stack crashes.

I'll collect a log file from versa and atom right now for you using old version.

roco5 commented 5 years ago

Thank you all for your support. We have released a new temporary version of atom, which may solve the Bluetooth problem. Please download the new version from the following URL. Please copy the downloaded .zip achive to your ATOM for upgrade as shown in the attachment. By the way, if the new version still has problems, please help grab the Bluetooth log. phone upgrade from Internal Storage for Atom.pdf https://drive.google.com/file/d/1mg6MMzM2qxi2bGMK3Rnw1uC15bHtglub/view?usp=sharing

If I install this version, can you send me instructions to undo it if it doesn't work? We rely on this phone for tracking and managing blood sugars and cannot be without it for any period of time. Right now with xdrip's restart bluetooth feature, we are able to keep the atom working despite bluetooth stack crashes.

I'll collect a log file from versa and atom right now for you using old version.

I have sent the log file to you by email. When you respond with instructions on how to revert to old firmware if update corrupts phone's connections (or anything else) I will do another test for you with the new firmware you just sent.

roco5 commented 5 years ago

Thank you all for your support. We have released a new temporary version of atom, which may solve the Bluetooth problem. Please download the new version from the following URL. Please copy the downloaded .zip achive to your ATOM for upgrade as shown in the attachment. By the way, if the new version still has problems, please help grab the Bluetooth log. phone upgrade from Internal Storage for Atom.pdf https://drive.google.com/file/d/1mg6MMzM2qxi2bGMK3Rnw1uC15bHtglub/view?usp=sharing

If I install this version, can you send me instructions to undo it if it doesn't work? We rely on this phone for tracking and managing blood sugars and cannot be without it for any period of time. Right now with xdrip's restart bluetooth feature, we are able to keep the atom working despite bluetooth stack crashes. I'll collect a log file from versa and atom right now for you using old version.

I have sent the log file to you by email. When you respond with instructions on how to revert to old firmware if update corrupts phone's connections (or anything else) I will do another test for you with the new firmware you just sent.

I also sent you a longer log that should show how over time having two bluetooth connections crashes both of them. (xdrip - dexcom and fitbit app - fitbit versa)

Again these are all on previous firmware. with XDRIP, DEXCOM 6 transmitter, Fitbit Versa watch with Glance watchface and Fitbit app.

tech-support-unihertz commented 5 years ago

Thank you all for your support. We have released a new temporary version of atom, which may solve the Bluetooth problem. Please download the new version from the following URL. Please copy the downloaded .zip achive to your ATOM for upgrade as shown in the attachment. By the way, if the new version still has problems, please help grab the Bluetooth log. phone upgrade from Internal Storage for Atom.pdf https://drive.google.com/file/d/1mg6MMzM2qxi2bGMK3Rnw1uC15bHtglub/view?usp=sharing

If I install this version, can you send me instructions to undo it if it doesn't work? We rely on this phone for tracking and managing blood sugars and cannot be without it for any period of time. Right now with xdrip's restart bluetooth feature, we are able to keep the atom working despite bluetooth stack crashes. I'll collect a log file from versa and atom right now for you using old version.

I have sent the log file to you by email. When you respond with instructions on how to revert to old firmware if update corrupts phone's connections (or anything else) I will do another test for you with the new firmware you just sent.

I also sent you a longer log that should show how over time having two bluetooth connections crashes both of them. (xdrip - dexcom and fitbit app - fitbit versa)

Again these are all on previous firmware. with XDRIP, DEXCOM 6 transmitter, Fitbit Versa watch with Glance watchface and Fitbit app.

Can you re-crawl bt log after updating to the latest version online? Thanks for your support. The hyperlink in the document has all new and old official versions of the atom phone: https://drive.google.com/drive/folders/1nnpyOLzNT25rqNo6uQ36DSths1I8uNvP?usp=sharing By the way, 2019030120_g35v63c2k_dfl-ota.zip is the latest official version, and other versions are old versions. phone upgrade from Internal Storage for Atom.pdf

tech-support-unihertz commented 5 years ago

Dear Sir, Thank you for your support. The hyperlink in the document has all new and old official versions of the atom phone: https://drive.google.com/drive/folders/1nnpyOLzNT25rqNo6uQ36DSths1I8uNvP?usp=sharing By the way, 2019030120_g35v63c2k_dfl-ota.zip is the latest official version, and other versions are old versions.

Regards,

Technical Support

+86-21-62207593 Ext 8007 www.unihertz.com

roco5 commented 5 years ago

Yes - And I have downloaded old version, placed it on phone root via USB, and attempted to update with local file back to November 2018 version but get this error: https://photos.app.goo.gl/Comepc24RZvk22nW7 and have not been able to roll back to that previous version.

Best, Rob Conley

On Mon, Mar 18, 2019 at 10:15 PM tech-support-unihertz < notifications@github.com> wrote:

Dear Sir, Thank you for your support. The hyperlink in the document <phone upgrade from Internal Storage for Atom> has all new and old official versions of the atom phone: https://drive.google.com/drive/folders/1nnpyOLzNT25rqNo6uQ36DSths1I8uNvP?usp=sharing By the way, 2019030120_g35v63c2k_dfl-ota.zip is the latest official version, and other versions are old versions.

Regards,

Technical Support

+86-21-62207593 Ext 8007 www.unihertz.com

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/NightscoutFoundation/xDrip/issues/734#issuecomment-474171140, or mute the thread https://github.com/notifications/unsubscribe-auth/AGoAaL1DcBE7-k83YqfzZdMxpdjwMMaTks5vYEg1gaJpZM4ZySTM .

roco5 commented 5 years ago

[image: image.png] Best, Rob Conley

On Mon, Mar 18, 2019 at 10:18 PM Rob Conley rconley@gmail.com wrote:

Yes - And I have downloaded old version, placed it on phone root via USB, and attempted to update with local file back to November 2018 version but get this error: https://photos.app.goo.gl/Comepc24RZvk22nW7 and have not been able to roll back to that previous version.

Best, Rob Conley

On Mon, Mar 18, 2019 at 10:15 PM tech-support-unihertz < notifications@github.com> wrote:

Dear Sir, Thank you for your support. The hyperlink in the document <phone upgrade from Internal Storage for Atom> has all new and old official versions of the atom phone: https://drive.google.com/drive/folders/1nnpyOLzNT25rqNo6uQ36DSths1I8uNvP?usp=sharing By the way, 2019030120_g35v63c2k_dfl-ota.zip is the latest official version, and other versions are old versions.

Regards,

Technical Support

+86-21-62207593 Ext 8007 www.unihertz.com

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/NightscoutFoundation/xDrip/issues/734#issuecomment-474171140, or mute the thread https://github.com/notifications/unsubscribe-auth/AGoAaL1DcBE7-k83YqfzZdMxpdjwMMaTks5vYEg1gaJpZM4ZySTM .

tech-support-unihertz commented 5 years ago

How about "The new version crashes unrecoverably, and the phone has an android error."
Can you show it to me? BTW, if there is no way to roll back to the previous version via a local ota upgrade. You can flash a ROM for Atom.

roco5 commented 5 years ago

In the new version, the bluetooth stack crashes until I either reset bluetooth connection or restart the phone. Xdrip stops getting readings from the sensor and fitbit stops sending readings to the watch. Here are photos of that and of the xdrip log and also the interfaces: https://photos.app.goo.gl/z8WW6XikYp9fqZRt7.

Best, Rob Conley

On Mon, Mar 18, 2019 at 10:25 PM tech-support-unihertz < notifications@github.com> wrote:

How about "The new version crashes unrecoverably, and the phone has an android error." Can you show it to me? BTW, if there is no way to roll back to the previous version via a local ota upgrade. You can flash a ROM for Atom.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/NightscoutFoundation/xDrip/issues/734#issuecomment-474173192, or mute the thread https://github.com/notifications/unsubscribe-auth/AGoAaFQ2_cqj1-JiiGYbXpbvVxXYAsTzks5vYEq2gaJpZM4ZySTM .

roco5 commented 5 years ago

How do I flash the ROM? Is that going to delete everything on the phone?

Best, Rob Conley

On Mon, Mar 18, 2019 at 10:37 PM Rob Conley rconley@gmail.com wrote:

In the new version, the bluetooth stack crashes until I either reset bluetooth connection or restart the phone. Xdrip stops getting readings from the sensor and fitbit stops sending readings to the watch. Here are photos of that and of the xdrip log and also the interfaces: https://photos.app.goo.gl/z8WW6XikYp9fqZRt7.

Best, Rob Conley

On Mon, Mar 18, 2019 at 10:25 PM tech-support-unihertz < notifications@github.com> wrote:

How about "The new version crashes unrecoverably, and the phone has an android error." Can you show it to me? BTW, if there is no way to roll back to the previous version via a local ota upgrade. You can flash a ROM for Atom.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/NightscoutFoundation/xDrip/issues/734#issuecomment-474173192, or mute the thread https://github.com/notifications/unsubscribe-auth/AGoAaFQ2_cqj1-JiiGYbXpbvVxXYAsTzks5vYEq2gaJpZM4ZySTM .

NightscoutFoundation / xDrip

Unihertz Atom Bluetooth Connection Lost Dexcom G6 #734