OESF Portables Forum
Model Specific Forums => Cosmo Communicator => Cosmo Communicator - CoDi => Topic started by: mithrandir on December 10, 2019, 05:40:11 pm
-
Just got a CODI update from V1.1.1.11 to V1.1.1.12. To get the update start the Cover Display Assistant app and press "check for updates". It took two attempts to flash the update. So if it fails, just retry. The flashing takes quite long (the app tells it might be about 20 minutes), so it might be better not to start with a nearly empty battery. For me the battery charge went down from 87% to 82% while flashing. For me the CODI feels snappier and I hope for better standby time. But maybe my perception is wrong.
Using the camera preview on the CODI still is slow, maybe a two seconds lag.
-
It took two attempts to flash the update.
It failed for me 3 times - once right away, once after 20 minutes loading resources, and then again right away. After which I completely turned of cosmo, and after power on went straight to updating - and this time it worked without hiccup.
Landscape mode is there, need to be enabled from external setting. Curiously, it can be set to automatic orientation, while internal display needs to be switched to landscape manually.
-
Landscape mode is there, need to be enabled from external setting. Curiously, it can be set to automatic orientation, while internal display needs to be switched to landscape manually.
I think it is quite natural: When you open the phone the natural way of holding it will be landscape (and having the option of turning "on" portrait when you need it with a setting, manually). For the outside screen it will be more natural to change it to the way you are holding it, and it is more natural to hold it in both landscape and portrait...
-
Just a word of warning - I am up to attempt 10, and at least the progress bar has started this time. The flashing appears *very* flaky. First time, mine got to around 90% then bombed out. Repeated, between 80-90% twice. Tried rebooting, advanced reset cover. 3 times didn't even establish comms and get to the progress bar. Up to 8% now (it is *very* slow) - we'll see if 10 is the charm
If you haven't updated, I would probably wait - once you start to flash, the cover is inoperable until the flashing succeeds. This means that quitting the updater/rebooting/resetting will all result in a completely black, broken cover display. I have probably just been unlucky, and this attempt will work wonderfully, but just so you have been warned - expect the firmware update to fail many times before it (hopefully) works.
I've entered a support request on the new cosmo troubleshooting page, so hopefully we might get some tips and tricks to getting it working more reliably.
PS. as a firmware engineer who flashes devices dozens of times a day, I understand there can be problems, but these seem a bit excessive.
EDIT: Yay - got to 100%, but still no cigar. "Error updating cover display!". Oh well, I should get better battery life now, and my smartwatch will do everything the cover did. Pity.
-
everything downloaded for me first try. first attempt to flash failed in like 30 seconds. second attempt worked but probably actually took the full 20 mins it said it might. it does feel more responsive to touch commands.
-
everything downloaded for me first try. first attempt to flash failed in like 30 seconds. second attempt worked but probably actually took the full 20 mins it said it might. it does feel more responsive to touch commands.
I'm up to attempt 15, I might actually run out of battery before it works Dropped 30% trying to flash. It now gets to 100%, but always fails. Anyone know where the file is stored? Maybe it is corrupted, and the flashing program doesn't check the file with a checksum.
-
It appears there are two parts to the flash, resources and image. For me, the resources fails every time, so I never even get to try the firmware update. I have cleared the cache/data for the cover app, and started again. Failed first time as I expected (I think it has for everybody else too), but we'll see how it goes. 46% so far. I must say that up till now, everything was going well with the cosmo.
Getting closer.....The resources has succeeded, but the firmware failed. The firmware is much smaller than the resources, so I can retry many times. All up, 18 attempts to get the resources flashed. First 6 attempts at the firmware file have failed, but luckily it only takes a few minutes each failure.
Yehar! Finally - on the 10th attempt for the firmware (after 18 for the resource file) we are there!!!!!! PERSISTANCE wins the day.
-
So everyone flashing but what does it do apart from landscape does it fix the battery drain issues with the front display on?
-
I seem to get stuck at 91% when flashing the image. Not sure why.
-
The update seems to make the screen faster/more responsive, for most operations. But until the main device firmware is released I don't think there are many other changes (happy to be proven wrong). The release notes (such as they are) on IGG are not overly helpful.
However, one thing it has done for my device is disable charging from the right hand USB port It's far from the end of the world, but this was only supposed to happen if the cover display is set to off when the cosmo is off - and that is a new option in the to be released firmware. Is this just me?
Like all of you, my update took several attempts. Hopefully future releases will go smoother.
Battery life is the same for me right now though, 5% used after 3 hours. Not too bad, hope it can be made better though
-
So if this doesn't work I should just keep trying over and over again?
For me, just the resource section took more like 35 minutes and not 20 minutes, and even then it failed (3 times so far).
-
Someone on Indiegogo suggested to put the Cosmo in do not disturb mode before the CODI update. Mine has been (by chance) in do not disturb mode during the update. Maybe that is the reason why it only took two attempts. Hard to tell…
-
So if this doesn't work I should just keep trying over and over again?
For me, just the resource section took more like 35 minutes and not 20 minutes, and even then it failed (3 times so far).
Yeah, wash, rinse, repeat.
Might be an idea to do a full reset (power off, then back on) of the Cosmo. It will happen eventually, but it's probably the crumbliest, flakiest firmware update process in the world.
-
Mine failed the first time -- I received an SMS in the middle of it -- but I saw the DND suggestion on IGG, did that, and it worked. It did fail to contact the thing after the process, and claimed it wasn't responding, but I reset it from the 'Advanced' menu, and it all seems happy.
If you have anything which regularly polls and triggers a transient notification (email being an obvious one), then DND may well help.
-
For what it is worth, I had cosmo connected to USB power during update -- 4 retries not too bad comparing to others. Also success was only after power cycle
-
After 50+ attempts, I finally got it to work. Here are the things I did:
1. Do Not Disturb
2. Airplane Mode with Do Not Disturb
3. Removing all notifications including persistent notification like weather and my watch connection.
4. Cover Display ON or Cover Display OFF
So at the end, I had Do Not Disturb, Airplane Mode, No Notifications, and Cover Display OFF. It still said it failed, but one more reboot and it took anyway. Now it says it is the latest. I thought there was supposed to be something about the Cover Display working in landscape mode, but it doesn't for me. However, I don't care about that, at least I have a External Display again and can answer the phone with the device closed. What an ordeal!
-
After 50+ attempts, I finally got it to work. Here are the things I did:
1. Do Not Disturb
2. Airplane Mode with Do Not Disturb
3. Removing all notifications including persistent notification like weather and my watch connection.
4. Cover Display ON or Cover Display OFF
So at the end, I had Do Not Disturb, Airplane Mode, No Notifications, and Cover Display OFF. It still said it failed, but one more reboot and it took anyway. Now it says it is the latest. I thought there was supposed to be something about the Cover Display working in landscape mode, but it doesn't for me. However, I don't care about that, at least I have a External Display again and can answer the phone with the device closed. What an ordeal!
Landscape mode is hidden under settings (swipe right to left to get icon menu, then the cog icon). You can then change the layout to Fixed portrait or landscape or auto rotate. Personally I found the auto rotate a bit too sensitive, but YMMV.
Glad you got it updated in the end!
-
After 50+ attempts, I finally got it to work. Here are the things I did:
1. Do Not Disturb
2. Airplane Mode with Do Not Disturb
3. Removing all notifications including persistent notification like weather and my watch connection.
4. Cover Display ON or Cover Display OFF
So at the end, I had Do Not Disturb, Airplane Mode, No Notifications, and Cover Display OFF. It still said it failed, but one more reboot and it took anyway. Now it says it is the latest. I thought there was supposed to be something about the Cover Display working in landscape mode, but it doesn't for me. However, I don't care about that, at least I have a External Display again and can answer the phone with the device closed. What an ordeal!
Just got my Cosmo today (yeah!....)......
Did the firmware update OK......
But like most, I'm having problem getting the CODI update to flash......
Have tried the settings shown in Tom's post shown above, but to no success....have tried a lot of times, including restarting, but always fails with the Error updating cover display! message.
Should I just keep trying and hoping it will eventually work or ?
thanks,
Mark
UPDATE
Well, kept trying again and again and finally, it started to flash......took about 20 minutes or so, then when it appeared to be done, it started all over again by itself. This time it got to 100% and said it was successfully updated!
Crazy......
-
I just went through the same pain. The same combination of things did not work for me. Swapping settings while in the flash program, not touching the second screen or fingerprint sensor seemed to eventually make it work for me. You know it is working when a yellow bar starts progressing slowly across the screen. This took about 30 mins for the resources and then it does a second stage where it is flashing the firmware. Don't abort before the second stage. Flashing said successful afterwards but it failed to reset the cover display (it still seemed to be showing 'Hello I am Cosmo' when it wanted to be able to talk to the display. Be persistent is all I can suggest.
-
The "takes 20-30 minutes and fails" isn't just me then? ... sooo frustrating!
So from reading this thread, am I right in thinking that the communications channel between the primary Cosmo processor, and the secondary cover processor used for relaying notifications, is the same channel used for firmware updates, and ANY notifications (has anyone noticed CODI itself sets a notification) that might be sent to the screen corrupt the transfer because they get injected in with the firmware data?
Does anyone else think that not being able to exclusively lock the channel during a firmware update is a tad bonkers?
Edit: Ok.. I did the following:- Switched back from Nova Launcher to Launcher3
- Disabled notifications explicitly on AccuBattery
- Set Do Not Disturb
- Set Airplane mode
- Disabled WiFi
- Disabled NFC (noticed it wasn't working whilst display wasn't working, have GPay enabled, thought they could be related / using common data channel)
- Avoided touching the cover display touchscreen at any time during update
- Cleared app switching cache (Eg. Alt tab screens) so prior CODI status forgotten
-
Just thought I'd report my experience:
Opened the Cover Display Assistant, was informed of new update. It downloaded the flash and then the resource download.
It started to apply the resource download first. It failed out almost immediately.
I remembered what I had read here earlier (thank you to all who went before!) and so I tried:
1) Turn Cover Display off (swipe down from the top, Quick Settings : Cover Display to OFF); and
2) Enable Airplane Mode
After this, the resource update took a long time (15-20 minutes as it says) but it proceeded without error.
Then the flash update took less time (5 minutes or less) and proceeded without error.
-
Got it successfully flashed on the fifth time, look like I should feel lucky...
Done nothing special, first time I rebooted the device, then I tried the four next times one after the other. (isn't that the definition of madness ?)
First time it failed instantly.
Second, and third times after the reboot it failed at 36%
Fourth time instantly again.........
Fifth time was fine....the only one time I didn't look at the device. (may be pudic )
-
All in all, it took 9 attempts for me until the cover display update was successfully flashed. Four times, it showed an error right at the beginning after some 30s or so. For the rest of the unsuccessful attempts, it just got stuck at some point, the progress bar didn't move on anymore, but no error message appeared. This seems to have been triggered by events on the Cosmo:
- The first time, I didn't know how flaky the flashing was and started doing other stuff on my Cosmo. The update immediately got stuck.
- The second time, it stopped when an email came in. From then on, I used flight mode and do not disturb.
- Not sure about the third time, but I think the "problem" may have been reaching 100% state of charge. Just to be sure, I deactivated Tasker, then.
- The fourth time, it got stuck when I switched off the lights in the room and the display was dimmed down. So I switched off adaptive display brightness. I also took the Cosmo off the mains because I wanted to take it somewhere else with me. I don't think this had an effect, but who knows?
- The fifth time it worked.
It seems to me that whenever something happens in the background that uses a considerable amount of CPU, flashing the cover display fails. I hope this will be improved. Right now, it's a bit like trying to burn CDs under Windows in the nineties.
-
It seems to me that whenever something happens in the background that uses a considerable amount of CPU, flashing the cover display fails. I hope this will be improved. Right now, it's a bit like trying to burn CDs under Windows in the nineties.
At least we don't have to throw away the CODIs after each unsuccessful burn attempt
-
Today did an update from V1.1.1.12 to V1.1.1.13.
The same trouble as previous time i updated it. But after about 7 tries it finally works.
-
I don't suppose anyone has the v12 firmware update files by any chance?
My Cosmo is not working properly & I want to downgrade v13 to v12 as a test
-
After update to Codi v13...
Try to phone my voicemail from the cover closed.
Can't connect (number types but call connect button on screen does nothing)
Speakerphone works but Headset earspeaker doesn't.
Have rebooted, turned SIM on and off, sworn, prayed and promised to be a good boy....
Any other Cosmonauts got any advice?
-
After update to Codi v13...
If you are talking about latest update - that one has version v14. Maybe your update failed and you need to keep trying
-
After update to Codi v13...
If you are talking about latest update - that one has version v14. Maybe your update failed and you need to keep trying
Sorry, my mistake v14 Codi actually and v22 system..
So all as up to date as possible currently. (Ten or so attempts at flashing.)
Not hearing anything through the headset earpiece - you know like using the Cosmo in a traditional phone manner.
If I use a headphone, then I can hear my voicemail box, but when I take out the Jack plug the earspeaker works for a second then just faint static sound - although the call is still connected.
C'mon Planet - this is basic functionality for a communicator phone, surely?
-
In my first CoDI flashing attempt, the resources phase passed, but it failed in the firmware phase. I suspect that now using the manual install method (http://support.planetcom.co.uk/index.php/Latest_Cosmo_Firmware#Manual_CoDi_firmware_update) to install just the firmware file will work and take less time than running the whole standard update process from the start for each attempt. As I write this post, I can see it's proceeding significantly faster than the resources phase - like 1% per second. And wo-oah! It worked
Note the below part of the linked instructions, which was required for me - selecting either image file from the Downloads section of the file selector view caused the CoDI Assistant to instantly crash.
On the file selector view, you might have to tap on the "Show Internal storage" option under the more option icon on the top right of the screen (the icon with the 3 round dots).
I would expand on this to say you need to then select Internal Storage from the drawer and browse to the file from there. I know there are a number of file access APIs in Android, and my guess is this method passes the file back to the app using a different mechanism.
-
...
Note the below part of the linked instructions, which was required for me - selecting either image file from the Downloads section of the file selector view caused the CoDI Assistant to instantly crash.
On the file selector view, you might have to tap on the "Show Internal storage" option under the more option icon on the top right of the screen (the icon with the 3 round dots).
I would expand on this to say you need to then select Internal Storage from the drawer and browse to the file from there. I know there are a number of file access APIs in Android, and my guess is this method passes the file back to the app using a different mechanism.
Thank you for this advice - this restored my ability to "Flash Image Manually" after the Cover Display Assistant would crash immediately on selecting an image file. I was able to complete the Codi update (2 attempts to do the firmware) and restore my unresponsivce Codi.
Simon