OESF Portables Forum
Model Specific Forums => Cosmo Communicator => Cosmo Communicator - Android => Topic started by: Steve Goodey on June 22, 2020, 03:49:59 am
-
As per title V22 update is out.
-
As per title V22 update is out.
Yes it is, just got the offer.
Anyone dare to install it (and the CoDI update) yet?
- Did you lose any data?
- Anything broken?
-
Bit early to know yet about anything broken.
Firmware seemed to install OK. CODI resource failed first try at 0% but retry now at 59%.
That's with Duraspeed off, DND and airplane mode.
-
OK, updates seemed to install OK. CODI resource and firmware both failed on first attempt at 0% but retry worked OK.
[ You are not allowed to view attachments ]
[ You are not allowed to view attachments ]
-
OK, updates seemed to install OK. CODI resource and firmware both failed on first attempt at 0% but retry worked OK.
[ You are not allowed to view attachments ]
[ You are not allowed to view attachments ]
The firmware went on OK, just flashing CODI.
One thing, I thought I'd put the phone in aeroplane mode but hadn't and got a text notificaiton mid-way through the flas which carried straight on going. That hasn't happened before so (extremely) early signs are hopeful.
Rosie
-
FW update installed fine, but rooted boot is borked now It keeps asking for my device pin without letting me in. Normal boot works fine, however.
Two steps forward, one step back......
-
Firmware 22 has arrived.
CODI update turning out to be a nightmare like the last time. Sixth attempt so far. Hopefully it will succeed before the 20th attempt.
-
FW update installed fine, but rooted boot is borked now It keeps asking for my device pin without letting me in. Normal boot works fine, however.
Two steps forward, one step back......
UPDATE: after updating CODI in normal boot, rooted boot seems to be working again. However, there's a strange thin vertical line visible on the left of the screen...
-
FW update installed fine, but rooted boot is borked now It keeps asking for my device pin without letting me in. Normal boot works fine, however.
Sounds like I'm better off re-rooting the Cosmo using the unofficial method from these forums...
-
Firmware 22 has arrived.
CODI update turning out to be a nightmare like the last time. Sixth attempt so far. Hopefully it will succeed before the 20th attempt.
FW update installed fine.
Codi first time failed. I am now trying again. Let's wait . Taking a long time...
-
Firmware 22 has arrived.
CODI update turning out to be a nightmare like the last time. Sixth attempt so far. Hopefully it will succeed before the 20th attempt.
FW update installed fine.
Codi first time failed. I am now trying again. Let's wait . Taking a long time...
Again an error. Codi Resources OK, but codi Firmware failed...
Let's try and try again ... ( Now it is installing Codi Resources again ... A pain ... ) . It will took another 30 minutes or more ...
-
Firmware 22 has arrived.
CODI update turning out to be a nightmare like the last time. Sixth attempt so far. Hopefully it will succeed before the 20th attempt.
FW update installed fine.
Codi first time failed. I am now trying again. Let's wait . Taking a long time...
Again an error. Codi Resources OK, but codi Firmware failed...
Let's try and try again ... ( Now it is installing Codi Resources again ... A pain ... ) . It will took another 30 minutes or more ...
I have failed for the 20th time (tried both automatic and manual), Do Not Disturb and Airplane Mode both on. If anyone has succeeded, please share your modus operandi. What does it take beyond infinite patience and stubborn perseverance?
-
Firmware 22 has arrived.
CODI update turning out to be a nightmare like the last time. Sixth attempt so far. Hopefully it will succeed before the 20th attempt.
FW update installed fine.
Codi first time failed. I am now trying again. Let's wait . Taking a long time...
Again an error. Codi Resources OK, but codi Firmware failed...
Let's try and try again ... ( Now it is installing Codi Resources again ... A pain ... ) . It will took another 30 minutes or more ...
4th attempt. CODI update turning out to be a nightmare ...
Manual update didn't work . It closes cover display assistant. I've also tried in airplane mode. ( without success ). Now I've disabled wifi, GPS And checked do not disturb.Also disabled norton AV.( and cleared cache and storage data of cover display assistant ). And I also put in airplane mode.
Let 's wait again. Last attempt in the morning. If it fails, I will try only at night. I have no time now.
-
4th attempt. CODI update turning out to be a nightmare ...
Manual update didn't work . It closes cover display assistant. Tried in airplane mode also. ( without success ). Now disabled wifi, GPS And check do not disturb.Also disabled norton AV.( and cleared cache and storage data of cover display assistant ). And put in airplane mode.
Let 's wait again. Last attempt in the morning. If it fails, I will try only at night. No time now.
Success on the 27th attempt. Aside from Do Not Disturb and Airplane mode, I put it down to patience, perseverance, and ... blind luck.
-
Update went without issues, CODI update went through on second try (didn't bother with offline mode or anything).
Can confirm the vertical bar on the left side for the rooted image, but at least SIM access is working, so I guess that's an improvement. I'm currently booting into the rooted image only for larger changes, but for daily use don't really need it, so I just hope they fix it - and for when I do need rooted access at least it's better than before.
-
Updated from V20 to V22, everything seems ok for now.
CODI update took somewhere between 10 and 15 attempts, here's how it went down for me:
0. Airplane mode on
1. Multiple attempts, kept failing
2. One of the tries didn't fail but hung up at 19% flashing firmware (let it sit for 30 minutes and it didn't move)
3. Canceled the update by manually hitting quit, which essentially soft bricked the CODI display (from what I can tell)
4. Reboot, retried update and it completed on the first try
Maybe disabling "Cover Display" in the Cosmo Settings before attempting the update might have a similar beneficial effect?
-
Updated from V20 to V22, everything seems ok for now.
CODI update took somewhere between 10 and 15 attempts, here's how it went down for me:
0. Airplane mode on
1. Multiple attempts, kept failing
2. One of the tries didn't fail but hung up at 19% flashing firmware (let it sit for 30 minutes and it didn't move)
3. Canceled the update by manually hitting quit, which essentially soft bricked the CODI display (from what I can tell)
4. Reboot, retried update and it completed on the first try
Maybe disabling "Cover Display" in the Cosmo Settings before attempting the update might have a similar beneficial effect?
My update from V19 to V22 has failed 4 times.
I have removed the linux partitions and also done a factory reset and still haven't been able to update to V22.
Anyone have any suggestions?
-
First updated the Android firmware, which went quickly and without any issues. Now updating CoDi, which failed the first time, but is now on 65%. Did not need to set it to DND mode. Fingers crossed.
Edit: Failed... And now hanging at 19% too. Did what mibry did, quit update and restarting now.
Aaaaand.... failed again... and again...
:-( ... "resources flashed successfully" (100%) after turning off the CoDi, which took quite long. Then it continues updating "flashing firmware image" a lot faster and ends in a `flashing error?.
-
Like others, firmware update completed OK on first try.
But like others, having problem getting Codi update to work.
After clicking 'FLASH NOW', I see status message:
"Flashing CODI resources / 0% (please wait, this process can take up to 20 minutes)"
How long did it take to see some progress in it updating?
Every time I try (on my 7th time now...), it just stays on 0% after waiting 10 minutes or so....
And do you keep trying but clicking 'FLASH NOW' again, or do you reboot each time or ???
Have turned off WiFi, Cover Display, Mobile Data, and turned on 'Do Not Disturb'.
Thanks for any help.
Mark
-
Looks like everyone tries to update CODI after android. Shouldn't it be the other way around?
-
FW update installed fine, but rooted boot is borked now It keeps asking for my device pin without letting me in. Normal boot works fine, however.
Sounds like I'm better off re-rooting the Cosmo using the unofficial method from these forums...
No, read my update...
-
Looks like everyone tries to update CODI after android. Shouldn't it be the other way around?
I updated CODI after Android and it worked on the 3rd attempt with Aiplane Mode off.
-
Looks like everyone tries to update CODI after android. Shouldn't it be the other way around?
You literally cannot do that. http://fota.planetcom.co.uk/stm32flash/cos...re_versions.txt (http://fota.planetcom.co.uk/stm32flash/cosmo_stm32_firmware_versions.txt) - note that 1.1.1.14 is only available for V22. So you cannot update Codi until after you have updated Android.
-
Have tried updating CODI about 5 more times since my recent post above....always fails...
But now it fails much quicker, after about 2 minutes trying to flash.....
???
-
Like others, firmware update completed OK on first try.
But like others, having problem getting Codi update to work.
After clicking 'FLASH NOW', I see status message:
"Flashing CODI resources / 0% (please wait, this process can take up to 20 minutes)"
How long did it take to see some progress in it updating?
Every time I try (on my 7th time now...), it just stays on 0% after waiting 10 minutes or so....
And do you keep trying but clicking 'FLASH NOW' again, or do you reboot each time or ???
Have turned off WiFi, Cover Display, Mobile Data, and turned on 'Do Not Disturb'.
Thanks for any help.
Mark
I just kept spamming it until it hung at 19% and I had to quit out, then rebooted because it wouldn't even initialize after that and it worked on first try after the reboot.
-
Updated from V20 to V22. Both the Firmware and the CODI Updates went through with the first try. This is what I did when in CODI phase, after reading the stories above:
1) Downloaded CODI packets. 2) Hit the 'ADVANCED' button and selected 'Stop Cover Communication'. 3) Put 'Do Not Disturb' and 'Aeroplane' modes on, and even put 'Cover Display' off. 4) Hit the 'FLASH' button.
Don't know if those did anything - or were overkill for some part - but one could think that stopping the cover communication makes less disturbation... Anyway, no problems at all. Now, let's see what has changed (although I haven't seen major bugs or random things with the V20 and have been happy with the Cosmo).
-
Finally got CODI updated. It may have been in airplane mode, but I'm not certain--I was lost in my many attempts. cam1965 has the great idea to clear CODI storage/cache, which I think is key after a failed update.
Also, there are two CODI downloads--image and firmware. If you can update image and firmware fails, do not close out or clear cache. Otherwise, you have to flash the image again. Stay in the CODI update screen and keep trying to flash firmware. That eventually worked for me.
Of course, just because Pandora's finally out of her box doesn't mean all is well...
Jake
-
here all updates at the 1st attemp. but still no SIM in Linux. also sometimes there are black boxes or lines all around the screen (android). 5april last security patch is better then my other phones so not that bad.
-
Finally got CODI updated....
Did the manual install. Worked the first time I tried.
-
Encouraged by your results, I also updated to V22 from V20 now. No problems so far. Updated CoDI without any issues on first try without any actions taken (no DND, cover display off, nothing).
No loss of data and so far observing that fingerprint unlock is now working again, unlike with V20.
Also noting that searching in settings seems to work - it did not before.
So maybe they have fixed some other things too.
-
Can't turn on Mobile Data.....
Have tried multiple times in Settings and by tapping icon, but no go.....
In upper right of display I see VoLTE 4G and signal triangle.....
???
-
Other notes:
- CoDi seems faster & responsive (e.g. scrolling through contacts, entering PIN)
- Security level is now April (as promised)
...however, device is probably *not* Certified. At least the old test "Try to install Netflix" from play store doesn't show the app. Also play protect does not show device as certified.
-
Yayyyy, `firmware flashed successfully´!! Now let´s see how long battery will last with CoDi on from now.
-
Can't turn on Mobile Data.....
Have tried multiple times in Settings and by tapping icon, but no go.....
In upper right of display I see VoLTE 4G and signal triangle.....
???
Got Mobile Data working again...had to reselect SIM in settings...
Meanwhile, looked at cover display and see icon for CODI with with diagonal red slash line through it.....
Getting CODI update available message even though updated CODI to V1.1.1.14.
Tried doing Reset cover display, but no go.....
Sigh.....
-
Decided to reflash CODI thinking it may not have completed properly.
Reflash completed successfully.
It then says 'Resetting cover display....'
However, above it shows red triangle with exclamation point and 'Cover display not responding'.
In the settings pulldown window, I turned on CODI.....
Now in Cover Display Assistant window, it shows a green dot and Cover Display Operational.
However, when I look on the CODI on outside of Cosmo, it still shows CODI icon with red diagonal line through it.
????
Thanks for any help.
-
Sorry for the travails, Mark. When you hit "check for updates" in COvID, does it say "Up To Date"?
Jake
-
Sorry for the travails, Mark. When you hit "check for updates" in COvID, does it say "Up To Date"?
Jake
Not sure I can check in'COvID'....but can in CODI....
I still get message 'New Version Available'......even though I see it also says,'Your current CODI version is V1.1.1.14'
Thanks, Jake!
Mark
-
Who truly knows, but when I hit check for updates, I get "Up To Date CODI version is the latest"
So it sounds as if you're in some kind of loop. Could be because of your manual install. I assume you've played with all the features of "Advance" to see if they will let you do a full install.
And yeah, COvID is my new name for this display, patent pending.
Jake
Edit: you could try clearing COvID's storage/cache
-
Am I hallucinating, or did Planet get rid of the maddening Mute button on the COvID screen? If I'm not, THAT'S a relief, no more of people hanging up because they thought they had been disconnected.
Jake
-
Who truly knows, but when I hit check for updates, I get "Up To Date CODI version is the latest"
So it sounds as if you're in some kind of loop. Could be because of your manual install. I assume you've played with all the features of "Advance" to see if they will let you do a full install.
And yeah, COvID is my new name for this display, patent pending.
Jake
Edit: you could try clearing COvID's storage/cache
Thanks, Jake.....
Yes, something is weird....
I've tried the other features, but they never seem to complete their action....
For example, just tried 'Stop Cover Communication', but after 10 minutes, it still says 'Stopping cover communication....' in the status area.....
-
Am I hallucinating, or did Planet get rid of the maddening Mute button on the COvID screen? If I'm not, THAT'S a relief, no more of people hanging up because they thought they had been disconnected.
I just noticed. They got rid of *all* call controls in that screen. Nothing works. Mute, switching to speakerphone, nada.
Frankly, I would call that improvement...
Also, just noticed that they have published a more detailed changelog at http://support.planetcom.co.uk/index.php/L..._Cosmo_Firmware (http://support.planetcom.co.uk/index.php/Latest_Cosmo_Firmware) - it's not that verbose, especially they are not expanding much on "bugfixes", but it's there.
-
Can't turn on Mobile Data.....
Have tried multiple times in Settings and by tapping icon, but no go.....
In upper right of display I see VoLTE 4G and signal triangle.....
???
On a previous update, turning off, removing SIM, turning on and off, replacing Sim and turning on did the job for me. There may be a simpler method.
-
Can't turn on Mobile Data.....
Have tried multiple times in Settings and by tapping icon, but no go.....
In upper right of display I see VoLTE 4G and signal triangle.....
???
On a previous update, turning off, removing SIM, turning on and off, replacing Sim and turning on did the job for me. There may be a simpler method.
Thanks, Tom....
Per my subsequent post (#34), I got it working without removing SIM....
Just reselected SIM in Settings.
Still have CODI issue as noted....
-
Mark, you did both COvID .bin installs, right?
Jake
-
Mark, you did both COvID .bin installs, right?
Jake
Hmmm........good question, Jake.....
I selected Manual Install.
Then in window that opened with files, I selected the smaller file size .bin file....assumed it would install both as part of process....
-
That did it, Jake....thanks!
Got CODI again.....
Mark
-
Hey, that's great.
Jake
-
Updated Android and Codi, booted inti Linux and updated it. Still no resume from sleep unless you manually select sleep from the menu. If you time out and go to sleep, or if you close the Lid you are dead.
I'll check out android to see if the Codi is more well behaved.
-
Am I hallucinating, or did Planet get rid of the maddening Mute button on the COvID screen? If I'm not, THAT'S a relief, no more of people hanging up because they thought they had been disconnected.
I just noticed. They got rid of *all* call controls in that screen. Nothing works. Mute, switching to speakerphone, nada.
Frankly, I would call that improvement...
Also, just noticed that they have published a more detailed changelog at http://support.planetcom.co.uk/index.php/L..._Cosmo_Firmware (http://support.planetcom.co.uk/index.php/Latest_Cosmo_Firmware) - it's not that verbose, especially they are not expanding much on "bugfixes", but it's there.
Did you figure out a fix? That is super annoying and I have it too.
-
Did you figure out a fix? That is super annoying and I have it too.
When I tried to repeat the issue this morning, I cannot... Suddenly CoDI controls during call work.
I did not reboot the phone or anything like that.
Clearly they are not broken all the time. I guess we need to find out what the conditions for lost controls are...
After a full reboot (turned off phone, turned back on) they *still* work.
-
Firmware 22 has arrived.
CODI update turning out to be a nightmare like the last time. Sixth attempt so far. Hopefully it will succeed before the 20th attempt.
FW update installed fine.
Codi first time failed. I am now trying again. Let's wait . Taking a long time...
Again an error. Codi Resources OK, but codi Firmware failed...
Let's try and try again ... ( Now it is installing Codi Resources again ... A pain ... ) . It will took another 30 minutes or more ...
4th attempt. CODI update turning out to be a nightmare ...
Manual update didn't work . It closes cover display assistant. I've also tried in airplane mode. ( without success ). Now I've disabled wifi, GPS And checked do not disturb.Also disabled norton AV.( and cleared cache and storage data of cover display assistant ). And I also put in airplane mode.
Let 's wait again. Last attempt in the morning. If it fails, I will try only at night. I have no time now.
Yesterday night finally codi installed. Everything working now ! Thanks God.
-
Update went without issues, CODI update went through on second try (didn't bother with offline mode or anything).
Can confirm the vertical bar on the left side for the rooted image, but at least SIM access is working, so I guess that's an improvement. I'm currently booting into the rooted image only for larger changes, but for daily use don't really need it, so I just hope they fix it - and for when I do need rooted access at least it's better than before.
Also mine has a vertical bar on the left side ( when booted with root image ).
Twrp also asks for a password.
In linux can't see my sim card.
Android is working OK. Netflix, OK and device certified.
-
Did my V22 update this morning, and CODI went through on the first try! AMAZE!
Phone had just rebooted and finished the V22 update. I just turned off the Cover Display from the Quick Settings pull-down, then in the Cover Display Assistant app, DOWNLOAD and then FLASH NOW. Downloaded the flash and resource image was fast. It started the resource image first (the one that takes longest) and it stayed at 0% for quite a long time, enough to make me start to worry. Then it finally started and took a long time to get through. I kept the display awake as it progressed. The flash image was much faster, and then it was done!
It has been awhile but I think I did the same procedure last time (turning off Cover Display from Quick Settings menu) and it went through on the first try as well. That was back at the update to V19 and I probably did the CODI update right after the Android firmware update as well.
Times before that, I have suffered through trying to get the CODI update to go through and conking out several times.
-
Update from v19 went without issues, CODI took some retries (manual is definitely the way to go). Auto rotate finally seems to be working. Debian finally sees something under list-modems (and also had crash/hanging someone mentioned on updating cosmo hal components, but it seems to have went through regardless). Lets see if battery life improves
-
Update from v19 went without issues, CODI took some retries (manual is definitely the way to go). Auto rotate finally seems to be working. Debian finally sees something under list-modems (and also had crash/hanging someone mentioned on updating cosmo hal components, but it seems to have went through regardless). Lets see if battery life improves
Hi.
I didn't see my sim card under debian. You said something under list-modems. I didn't see anything under /usr/share/ofono/scripts/list-modems ....
Please tell me what command you do to show the modem or sim card .Many thanks .
-
Update from v19 went without issues, CODI took some retries (manual is definitely the way to go). Auto rotate finally seems to be working. Debian finally sees something under list-modems (and also had crash/hanging someone mentioned on updating cosmo hal components, but it seems to have went through regardless). Lets see if battery life improves
Hi.
I didn't see my sim card under debian. You said something under list-modems. I didn't see anything under /usr/share/ofono/scripts/list-modems ....
Please tell me what command you do to show the modem or sim card .Many thanks .
Just 'list-modems', used to return nothing under v19, now lists ril0 and ril1
-
Update from v19 went without issues, CODI took some retries (manual is definitely the way to go). Auto rotate finally seems to be working. Debian finally sees something under list-modems (and also had crash/hanging someone mentioned on updating cosmo hal components, but it seems to have went through regardless). Lets see if battery life improves
Hi.
I didn't see my sim card under debian. You said something under list-modems. I didn't see anything under /usr/share/ofono/scripts/list-modems ....
Please tell me what command you do to show the modem or sim card .Many thanks .
Just 'list-modems', used to return nothing under v19, now lists ril0 and ril1
Ok. Thank you. But mine doesn´t list nothing . Interesting ...
-
Update from v19 went without issues, CODI took some retries (manual is definitely the way to go). Auto rotate finally seems to be working. Debian finally sees something under list-modems (and also had crash/hanging someone mentioned on updating cosmo hal components, but it seems to have went through regardless). Lets see if battery life improves
Hi.
I didn't see my sim card under debian. You said something under list-modems. I didn't see anything under /usr/share/ofono/scripts/list-modems ....
Please tell me what command you do to show the modem or sim card .Many thanks .
Just 'list-modems', used to return nothing under v19, now lists ril0 and ril1
Ok. Thank you. But mine doesn´t list nothing . Interesting ...
Do you have all packages up to date (apt update or apt-get update or even the discover software center should work), maybe the kernel is still old? Probably best to jump into 'geminiPDA' group on telegram, easier to troubleshoot there
-
Update from v19 went without issues, CODI took some retries (manual is definitely the way to go). Auto rotate finally seems to be working. Debian finally sees something under list-modems (and also had crash/hanging someone mentioned on updating cosmo hal components, but it seems to have went through regardless). Lets see if battery life improves
Hi.
I didn't see my sim card under debian. You said something under list-modems. I didn't see anything under /usr/share/ofono/scripts/list-modems ....
Please tell me what command you do to show the modem or sim card .Many thanks .
Just 'list-modems', used to return nothing under v19, now lists ril0 and ril1
Ok. Thank you. But mine doesn´t list nothing . Interesting ...
Do you have all packages up to date (apt update or apt-get update or even the discover software center should work), maybe the kernel is still old? Probably best to jump into 'geminiPDA' group on telegram, easier to troubleshoot there
Ok. Thank you . everything is updated. I will look to geminipda group. Thank you again.
-
Update from v19 went without issues, CODI took some retries (manual is definitely the way to go). Auto rotate finally seems to be working. Debian finally sees something under list-modems (and also had crash/hanging someone mentioned on updating cosmo hal components, but it seems to have went through regardless). Lets see if battery life improves
Hi.
I didn't see my sim card under debian. You said something under list-modems. I didn't see anything under /usr/share/ofono/scripts/list-modems ....
Please tell me what command you do to show the modem or sim card .Many thanks .
Just 'list-modems', used to return nothing under v19, now lists ril0 and ril1
Ok. Thank you. But mine doesn´t list nothing . Interesting ...
Do you have all packages up to date (apt update or apt-get update or even the discover software center should work), maybe the kernel is still old? Probably best to jump into 'geminiPDA' group on telegram, easier to troubleshoot there
Ok. Thank you . everything is updated. I will look to geminipda group. Thank you again.
Tried everything and nothing. Installed some kernels : initial release, last release and my onw compiled kernel. Inslalled gemian-system. Follow the instructions on this link https://github.com/gemian/gemini-keyboard-a...DebuggingMobile (https://github.com/gemian/gemini-keyboard-apps/wiki/DebuggingMobile) and https://github.com/gemian/gemini-keyboard-a.../wiki/DebianTP2 (https://github.com/gemian/gemini-keyboard-apps/wiki/DebianTP2) . But the modem is not recognized. I have android , twrp , android root and debian installed. I think something is preventing debian to access the modem. Not sure about this. I' d really appreciate if someone can help me, Or if someone has the same problem as mine. And also if someone is able to detect the modem in debian , please let me know. Thank you all.
-
Tried everything and nothing. Installed some kernels : initial release, last release and my onw compiled kernel. Inslalled gemian-system. Follow the instructions on this link https://github.com/gemian/gemini-keyboard-a...DebuggingMobile (https://github.com/gemian/gemini-keyboard-apps/wiki/DebuggingMobile) and https://github.com/gemian/gemini-keyboard-a.../wiki/DebianTP2 (https://github.com/gemian/gemini-keyboard-apps/wiki/DebianTP2) . But the modem is not recognized. I have android , twrp , android root and debian installed. I think something is preventing debian to access the modem. Not sure aboiut this. I´d really appreciate if someone can help me, Or if someone has the same problem as mine. And also if someone is able to detect the modem in debian , please let me know. Thank you all.
I would really suggest joining that group on telegram, the gemini/cosmo gurus visit there much more often than here it seems and if troubleshooting will require outputs of 2-3+ commands you might finish it within minutes if one is awake, rather than on forum that people check few times a day at most (not to mention all threads, still worth putting a thread in the relevant subforum once you fix it with detailed steps)
-
Update went without issues, CODI update went through on second try (didn't bother with offline mode or anything).
Can confirm the vertical bar on the left side for the rooted image, but at least SIM access is working, so I guess that's an improvement. I'm currently booting into the rooted image only for larger changes, but for daily use don't really need it, so I just hope they fix it - and for when I do need rooted access at least it's better than before.
Also mine has a vertical bar on the left side ( when booted with root image ).
Twrp also asks for a password.
In linux can't see my sim card.
Android is working OK. Netflix, OK and device certified.
I had that vertical bar too on root at first, but it suddenly disappeared after a couple of hours and hasn't returned since.
-
Update went without issues, CODI update went through on second try (didn't bother with offline mode or anything).
Can confirm the vertical bar on the left side for the rooted image, but at least SIM access is working, so I guess that's an improvement. I'm currently booting into the rooted image only for larger changes, but for daily use don't really need it, so I just hope they fix it - and for when I do need rooted access at least it's better than before.
Also mine has a vertical bar on the left side ( when booted with root image ).
Twrp also asks for a password.
In linux can't see my sim card.
Android is working OK. Netflix, OK and device certified.
I had that vertical bar too on root at first, but it suddenly disappeared after a couple of hours and hasn't returned since.
Hi.
Did a test here. It disappeared after closing the lid. After a new reboot it returns. But closing and opening again the lid it disappears .
-
Did you figure out a fix? That is super annoying and I have it too.
When I tried to repeat the issue this morning, I cannot... Suddenly CoDI controls during call work.
I did not reboot the phone or anything like that.
Clearly they are not broken all the time. I guess we need to find out what the conditions for lost controls are...
After a full reboot (turned off phone, turned back on) they *still* work.
Somebody on indiegogo mentioned to turn off Standby Intelligent Power Saving then turn it back on and what do you know it started working again
-
Do you have all packages up to date (apt update or apt-get update or even the discover software center should work), maybe the kernel is still old? Probably best to jump into 'geminiPDA' group on telegram, easier to troubleshoot there
I think the problem is that I am using the planet cosmo Kde system image and you are using from Jenkins . ( According to your post : https://www.oesf.org/forum/index.php?showto...ommit&st=27 (https://www.oesf.org/forum/index.php?showtopic=36249&hl=commit&st=27) ) . The problem is the system image. and not the kernel , because in that post I think I had already installed the kernel from Jenkins ( basically is the same as my compiled kernel ( please see https://www.oesf.org/forum/index.php?showto...ommit&st=28 (https://www.oesf.org/forum/index.php?showtopic=36249&hl=commit&st=28) ). But I have a lot of things installed , libraries , source codes and if I install this system image I will lost everything . ( about 32 GB ). Maybe if I discover what is different on this image it helps. Thank you again.
-
Update from v19 went without issues, CODI took some retries (manual is definitely the way to go). Auto rotate finally seems to be working.
Autorotate does not work for me. Not on main screen. On codi it worked on v19.
I actually did not notice any functional changes after update thus far, except version numberand security patch date.
-
Update from v19 went without issues, CODI took some retries (manual is definitely the way to go). Auto rotate finally seems to be working.
Autorotate does not work for me. Not on main screen. On codi it worked on v19.
I actually did not notice any functional changes after update thus far, except version numberand security patch date.
It's working for me. Perhaps you need to re-enable it? Remember, there are 2 places it needs to be enabled, Android settings and the Planet menu bar settings.
I hate to say this, for fear of jinxing myself, but I've not noticed any random reboots since installing this firmware; is it too soon to say their fixed?
-
Do you have all packages up to date (apt update or apt-get update or even the discover software center should work), maybe the kernel is still old? Probably best to jump into 'geminiPDA' group on telegram, easier to troubleshoot there
I think the problem is that I am using the planet cosmo Kde system image and you are using from Jenkins . ( According to your post : https://www.oesf.org/forum/index.php?showto...ommit&st=27 (https://www.oesf.org/forum/index.php?showtopic=36249&hl=commit&st=27) ) . The problem is the system image. and not the kernel , because in that post I think I had already installed the kernel from Jenkins ( basically is the same as my compiled kernel ( please see https://www.oesf.org/forum/index.php?showto...ommit&st=28 (https://www.oesf.org/forum/index.php?showtopic=36249&hl=commit&st=28) ). But I have a lot of things installed , libraries , source codes and if I install this system image I will lost everything . ( about 32 GB ). Maybe if I discover what is different on this image it helps. Thank you again.
do you have urfkill installed? also this is needed:
https://github.com/gemian/gemian-debos-reci...bscription.conf (https://github.com/gemian/gemian-debos-recipes/blob/master/overlay/cosmopda/etc/ofono/ril_subscription.conf)
(you can go through commits in debos recipes to see step by step what was added/modified since your debian install and should end up with same system state)
-
Do you have all packages up to date (apt update or apt-get update or even the discover software center should work), maybe the kernel is still old? Probably best to jump into 'geminiPDA' group on telegram, easier to troubleshoot there
I think the problem is that I am using the planet cosmo Kde system image and you are using from Jenkins . ( According to your post : https://www.oesf.org/forum/index.php?showto...ommit&st=27 (https://www.oesf.org/forum/index.php?showtopic=36249&hl=commit&st=27) ) . The problem is the system image. and not the kernel , because in that post I think I had already installed the kernel from Jenkins ( basically is the same as my compiled kernel ( please see https://www.oesf.org/forum/index.php?showto...ommit&st=28 (https://www.oesf.org/forum/index.php?showtopic=36249&hl=commit&st=28) ). But I have a lot of things installed , libraries , source codes and if I install this system image I will lost everything . ( about 32 GB ). Maybe if I discover what is different on this image it helps. Thank you again.
do you have urfkill installed? also this is needed:
https://github.com/gemian/gemian-debos-reci...bscription.conf (https://github.com/gemian/gemian-debos-recipes/blob/master/overlay/cosmopda/etc/ofono/ril_subscription.conf)
(you can go through commits in debos recipes to see step by step what was added/modified since your debian install and should end up with same system state)
Hi thank you very very much ! Worked following your instructions. ( urfkill and ril_subscription.conf ).
Tested with dialer-app and messaging-app with success. Internet data does not work .
messaging-app conflicts with apparmor ( needed by snapd ). I removed snapd.
Thank you so much again.
-
Autorotate does not work for me. Not on main screen. On codi it worked on v19.
It's working for me. Perhaps you need to re-enable it? Remember, there are 2 places it needs to be enabled, Android settings and the Planet menu bar settings.
That was it, thank you!
I sure would not find it myself -- not very obvious that the settings of planet app bar affect other applications.
-
I can confirm that the random locking issue is still there. I entered my pin and started going through my gmail, reading and deleting items, frequent input every 1 or 2 seconds, and then it just locked the screen out of no where.
It's not a big issue, but is very annoying and wouldn't think it would be that hard to fix. My guess is it is again some issue with CODI. Me no like CODI!
And yes, latest V22 and latest CODI, and after a few reboots later.
-
CPU SPIKE / HIGH DRAIN / HIGH TEMP ISSUE - maybe resolved in V22
I've only been on V22 for a day, but my issue with certain apps intermittently causing CPU spike seems to have disappeared.
I had an issue where occasionally the temperature near the rocker switch would go very high. Battery drained much faster. This could go on for hours if unnoticed. Opening/unlocking and going to the desktop, and then scrolling back and forth between desktops was very jerky whenever this happened. The issue would often go away just by closing and re-opening, but I also found it disappeared as soon as I opened GSamBattery app. I noticed in GSam that CPU would spike to constantly 100% during these occurrences.
(I installed GSamBattery to try and track down what was going on, and then once I discovered it has temperature alerts, I set that up to detect whenever this strange CPU spikes occurred)
Over time I discovered that there were a couple of apps that shortly after using them, this CPU spike event would occur much more frequently. However, it didn't necessarily happen right when a particular app was just used. I could have my phone tucked in a pocked for a half hour and no problems, then suddenly the issue starts.
Since V22 I have tried using those apps to see if I could get the issue to recur, and so far it hasn't. So that's good.
POWER SAVING NOTES
I also noticed that after V22, my weechat running in tmux running in termux, would ping-time-out while the phone was closed. It never did that before V22. I guess that is the new more aggro power saving in action? I was able to resolve that by allowing tmux to hold a wakelock.
Finally, I did NOT notice much improvement in battery drain under V22. My battery was pretty much down to 15% by the end of the day, as it normally has been. NOTE that I didn't turn the wakelock on until later in the day.
-
I can confirm that the random locking issue is still there. I entered my pin and started going through my gmail, reading and deleting items, frequent input every 1 or 2 seconds, and then it just locked the screen out of no where.
It's not a big issue, but is very annoying and wouldn't think it would be that hard to fix. My guess is it is again some issue with CODI. Me no like CODI!
And yes, latest V22 and latest CODI, and after a few reboots later.
That was a problem on the early firmware versions on the Gemini as well, and that CERTAINLY does not have a "CODI", so do not think it is necessarily linked to the CODI. But, yes, it IS annoying, regardless of WHAT causes it!
(Haven't really used my Cosmo enough yet that I've come across it there...)
-
I can confirm that the random locking issue is still there.
Interesting you mention it. I have not had random locking problem through my life with v19 firmware until this week. I actually forgot about this problem. But during my epic upgrade to v22 (which took a whole working day, mind you, due to permanent failed update of codi), I switched my home app from T-UI to whatever terrible google-search-taunting default contraption the PC provides, thinking that maybe T-UI was the reason of failures of codi updates. That did not proved true, but I immediately started to get those random lock ups once i let PC default home app take over my device. Eventually in the end of day codi update completed and I switched back to T-UI as home app, and random locking is all gone again, not a problem any more
-
Did you figure out a fix? That is super annoying and I have it too.
When I tried to repeat the issue this morning, I cannot... Suddenly CoDI controls during call work.
I did not reboot the phone or anything like that.
Clearly they are not broken all the time. I guess we need to find out what the conditions for lost controls are...
After a full reboot (turned off phone, turned back on) they *still* work.
Somebody on indiegogo mentioned to turn off Standby Intelligent Power Saving then turn it back on and what do you know it started working again
Update it's only temporary. On screen controls weren't working again today. Had to cycle it again.
-
still got the random reboots with new firmware v22 and CODI V1.1.1.14 when CODI is switched on.. :/
-
Similarly I've still got the random reboots with new firmware v22 and CODI V1.1.1.14 when CODI is switched on.
The reboots are mostly when opening the phone, closing the phone, plugging in or removing the cable for charging using the opposite side from silver button.
previously it would reboot during phone or zoom calls with or without video, on all the cases listed above and also without any interaction.
It appears slightly more stable, but not reliable yet.
So I'm going to run it with Cover Display off and Switch OFF cover display on Power down also off.
My battery percentage always shows -1% no matter the charge level. I have let the phone fuly charge, fully discharge (well until auto power off) and run for a few hours.
At all points it still shows -1% battery.
Regards
Chris
-
Similarly I've still got the random reboots with new firmware v22 and CODI V1.1.1.14 when CODI is switched on.
The reboots are mostly when opening the phone, closing the phone, plugging in or removing the cable for charging using the opposite side from silver button.
previously it would reboot during phone or zoom calls with or without video, on all the cases listed above and also without any interaction.
It appears slightly more stable, but not reliable yet.
So I'm going to run it with Cover Display off and Switch OFF cover display on Power down also off.
My battery percentage always shows -1% no matter the charge level. I have let the phone fuly charge, fully discharge (well until auto power off) and run for a few hours.
At all points it still shows -1% battery.
Regards
Chris
Yes, I've turned off CODI and things are much more stable. I'm not using it as a phone, so CODI doesn't add much anyway. That's one of the reasons I went and backed the slider - it looks like it may easier to use it as a phone.
-
I just drove 200 km over 2 hours, listening to stream all the way. Battery drain about 9%, and no crash. V19 crashed over this period. No problems with v22, so definitely an improvement!
-
Autorotate does not work for me. Not on main screen. On codi it worked on v19.
It's working for me. Perhaps you need to re-enable it? Remember, there are 2 places it needs to be enabled, Android settings and the Planet menu bar settings.
That was it, thank you!
I sure would not find it myself -- not very obvious that the settings of planet app bar affect other applications.
Huh', thank you very much! I had been there once, but thought that setting would only affect the Planet Bar app itself...
Auto rotation seems to be clever, too. I have some apps, that don't behave well in landscape mode. When auto rotation is on, those appear in portrait mode automagically - fine. I even feel that the Cosmo is easy and steady to handle in portrait mode when needed.
-
I installed it successfully a couple days ago. Failed the CODI update the first time, but upon retrying it installed successfully. Battery life is exceptionally improved. I've been able to leave the external screen on and it has lasted the whole day. Responsiveness of the external screen is better, but still not where I'd like to see it. I'll be using it for my daily driver over the next couple days. Wish Me Luck!
-
I even feel that the Cosmo is easy and steady to handle in portrait mode when needed.
I actually find the same: here is an example browsing ebay site in firefox holding the device vertically in left hand while flipping pages by pressing space bar with the thumb of right hand
[ You are not allowed to view attachments ]
-
Apparently, V22 is still screwed up. I had to reboot for the first time since installing V22, but mobile data isn't working anymore, the top bar isn't working anymore, the home and recent apps buttons aren't working anymore (both the soft and keyboard buttons)... It also says that some options are "not available for this user".
Should've stayed with V20 after all. The sudden reboots were annoying, but at least everything was working.
My exceptionally high trust in Planet has diminished now. No more defending Planet as of now, until they get their act together.
-
That's very strange. I've had one hard reboot happen to me since V22. Guess better be careful and make those backups often.
-
With V22 I experience spurious reboots every 3 or 4 hours. So when I booted a rooted Android and leave the device unattended, Cosmo might have booted into the non-rooted Android in the meantime, which can be quite confusing. I did not observe this behaviour in earlier version.
-
With V22 I experience spurious reboots every 3 or 4 hours. So when I booted a rooted Android and leave the device unattended, Cosmo might have booted into the non-rooted Android in the meantime, which can be quite confusing. I did not observe this behaviour in earlier version.
Mine, up to now is OK. I have updated from V19 to V22. No password defined . Everything is fine.
Thanks God !
-
Mine, up to now is OK. I have updated from V19 to V22. No password defined . Everything is fine.
I came to V22 the "official" way ;-) OTA V20 -> manual upgrade to V21 -> OTA V22. I'm not decided whether this can cause the reboots.
-
I have used my Cosmo paired with a Fossil Gen 5 watch, external screen on, and have had no issues over the past couple days. No reboots or crashes so far. I would like to point out that I immediately disable all the Planet Computer apps that are pre-installed, except for the CODI app itself. I also disabled the app bar.
I do not play games on my Cosmo. Used to streaming audio in the car during the day, emails, txt msgs, light internet surfing and I read Google News app about 3 or 4 times through the day. I'm seeing about %50 battery drain from 5:30am to 9pm.
I am actually very pleased with the performance and battery improvements. I could not get through a whole day if I left the external screen on before v22.
-
Hi folks,
I contacted Planet via hello@planetcom.co.uk on the off chance there were responding
They replied the next day which was great.
They want to investigate if my issue is not v22 update related but is physical contact related.
This fits some circumstances but not all, but I'm a patient person and ever the optomist I'll go with it.
So due to their repair backlog I've to wait to ship it to them in 3 weeks so they can look at it under warranty.
So i'm backing it up and parking it on a shelf until then, I'll miss the keyboard and go back to my old Samsung Galaxy Note 3.
I might push my luck and ask if they can configure it with whatever the state of play is on the linux side if I ship it with a 256GB MicroSD card.
Or ask if I can pay for a suitably sized one to be implemented from their end since I think the SD card they shipped to Beta testers is still v19?
What is the largest SD card anyone is prepared to trust/recommend in the Cosmo?
Cheers
Chris
-
I might push my luck and ask if they can configure it with whatever the state of play is on the linux side if I ship it with a 256GB MicroSD card.
Or ask if I can pay for a suitably sized one to be implemented from their end since I think the SD card they shipped to Beta testers is still v19?
What is the largest SD card anyone is prepared to trust/recommend in the Cosmo?
Interesting issue that... There is an issue V19 and V22 include vfat and ext4 support, but not exfat or udf. As such the choice of filesystem on SD card is tricky. Though I do note SD cards tend to have very large erase block sizes which isn't really suitable for anything besides pictures or video. You would need to erase any SD card larger than 64GB (SD card association specifies exfat as the default, despite UDF being far superior).
I imagine kernels with exfat and/or udf will be showing up soon, but in the meantime larger than 64GB is a bit troublesome. Though SD card performance is often questionable.
-
I got my Cosmo yesterday, and it came with V15.. I've updated it to V16, and then went from V16 to V19, but now it tells me that there aren't any more updates available. I've tried to reboot the device, but still nothing. Do i need to do something manually?
-
I got my Cosmo yesterday, and it came with V15.. I've updated it to V16, and then went from V16 to V19, but now it tells me that there aren't any more updates available. I've tried to reboot the device, but still nothing. Do i need to do something manually?
Maybe a factory reset . And maybe a codi update ( it is a pain to update codi ).
If you want to repartition your cosmo it is better to do this first.
Good luck.
-
.. wrote to Planet Computers about it on Facebook, and they tell me that a V23 is being released today. So i will wait for that
-
.. wrote to Planet Computers about it on Facebook, and they tell me that a V23 is being released today. So i will wait for that
v23 is already available. This ota update is 49 MB. V22 ota.zip is 134MB. Maybe this update will work only for v22. ( so maybe you have to update manually to v22 first , I don't know ). Please post here if v23 is available to you. Good luck.
-
.. wrote to Planet Computers about it on Facebook, and they tell me that a V23 is being released today. So i will wait for that
v23 is already available. This ota update is 49 MB. V22 ota.zip is 134MB. Maybe this update will work only for v22. ( so maybe you have to update manually to v22 first , I don't know ). Please post here if v23 is available to you. Good luck.
V23 was available and i made the jump all the way from V19.. Seems to be working though.. Currently updating Codi.. I cannot remember the size of the OS update though
-
.. wrote to Planet Computers about it on Facebook, and they tell me that a V23 is being released today. So i will wait for that
v23 is already available. This ota update is 49 MB. V22 ota.zip is 134MB. Maybe this update will work only for v22. ( so maybe you have to update manually to v22 first , I don't know ). Please post here if v23 is available to you. Good luck.
V23 was available and i made the jump all the way from V19.. Seems to be working though.. Currently updating Codi.. I cannot remember the size of the OS update though
That is very good. Thanks.
-
CPU SPIKE / HIGH DRAIN / HIGH TEMP ISSUE - maybe resolved in V22
I've only been on V22 for a day, but my issue with certain apps intermittently causing CPU spike seems to have disappeared.
I had an issue where occasionally the temperature near the rocker switch would go very high. Battery drained much faster. This could go on for hours if unnoticed. Opening/unlocking and going to the desktop, and then scrolling back and forth between desktops was very jerky whenever this happened. The issue would often go away just by closing and re-opening, but I also found it disappeared as soon as I opened GSamBattery app. I noticed in GSam that CPU would spike to constantly 100% during these occurrences.
(I installed GSamBattery to try and track down what was going on, and then once I discovered it has temperature alerts, I set that up to detect whenever this strange CPU spikes occurred)
Over time I discovered that there were a couple of apps that shortly after using them, this CPU spike event would occur much more frequently. However, it didn't necessarily happen right when a particular app was just used. I could have my phone tucked in a pocked for a half hour and no problems, then suddenly the issue starts.
Since V22 I have tried using those apps to see if I could get the issue to recur, and so far it hasn't. So that's good.
Oh well, the description is exactly what I have now, started somewhere after upgrade to V22 and now on V23 it's still there. Even with Safe Mode it was still reproducible. Cosmo is unusable now :-/