Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - mithrandir

Pages: 1 2 3 [4] 5 6 ... 13
46
Cosmo Communicator - Android / Where can I download Android ROM?
« on: December 20, 2019, 08:06:43 am »
Quote from: irukandji
My cosmo is on its way and I would like to mod the rom in advance. Does someone have link to Cosmo Android ROM, so I can start modding?

Thank you
ROMs are not published, yet. Will be available in future at: http://support.planetcom.co.uk/index.php/Main_Page

47
Cosmo Communicator - Hardware / USB-C
« on: December 19, 2019, 12:06:08 pm »
Quote from: NormMonkey
Does anyone from the Gemini world have any experience with getting a second display to work?  Has anyone used OXI or Leena or Sentio?
As expected...
With the Gemini with the propietary Adapter it works out of the box (afaik mirror only, but don't know for sure, using Debian mainly). With Linux using the adapter is not possible (yet) and required changes to the hwcomposer driver. So don't expect to get this working soon.

48
Cosmo Communicator - Android / Possible cause for battery drain
« on: December 18, 2019, 03:46:18 pm »
I have identified a process "android.hardware.nfc@1.1-service" occasionallly using up one cpu core (top in termux) and draining the battery then. Turning off nfc heals the problem. After reenabling nfc cpu usage stays down. I can see this happen every one or two days.

For the time being it might be best to keep nfc disabled until one needs it. Bug ticket @PC already opened.

49
Gemini PDA - Hardware / Gemini screen line and not boot
« on: December 18, 2019, 02:38:07 pm »
Quote from: stdlogicvector
How long did it take for the battery to die completely?

My Gemini has run for several hours yesterday showing the graphics error, then went dark and started vibrating in short bursts in irregular intervals. It wouldn't show the splash screen anymore, regardless of how long/often I pressed the Esc/On-key.

This had stopped this morning and when I connected it to the carger, the battery animation showed up on the screen and then vanished in the same graphics error as the splash screen did before. Now its back to black screen and irregular bursts of vibration.

I'm going to give it a few more hours to die and then try again...

You could remove the back cover. Then unscrew the back plastic side cover on he cable side and remove the cover. Afterwards unscrew and remove the small metal clip holding the battery plug. Then pull the plug. Then it is quite fast.

...and more healthy for the battery.

50
Cosmo Communicator - CoDi / CODI update
« on: December 15, 2019, 06:41:55 am »
Quote from: zottel
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

51
Cosmo Communicator - Hardware / New Cosmo Firmware Update
« on: December 14, 2019, 08:51:11 am »
Quote from: mithrandir
This is the original boot image backup (before 1st OTA). Unless I have a wrong understanding of the update process (mostly guessing) , for further updates we will need the one after the 1st  update.
ZimbiX has published his boot images after the first OTA:
https://www.oesf.org/forum/index.php?s=&...st&p=293538

Thanks!

52
Cosmo Communicator - Hardware / New Cosmo Firmware Update
« on: December 14, 2019, 08:27:05 am »
Quote from: TauPan
Completely agree!

There's a backup of the original boot image here: https://www.oesf.org/forum/index.php?s=&...st&p=292918

I also have one from my device, which I could share but I think that's not necessary.

Also I've learned that it's quite convenient to keep a backup of your seccfg partition before *and* after unlocking the bootloader, as you can just unlock and re-lock your bootloader by flashing either version. I haven't tested the unlocking version personally yet, but locking the bootloader by flashing a locked seccfg definitely works (and I do have a backup of the unlocked seccfg now, so I could test it).

This is the original boot image backup (before 1st OTA). Unless I have a wrong understanding of the update process (mostly guessing) , for further updates we will need the one after the 1st  update.

53
Quote from: mmbika
This is my second day with Cosmo and fell in love with it ... It gave me two OTA updates, one for COD and one for main system ... I just plunged in and now my COD is not working ... Cover Display Assistant flashed (every time I tried again and again) the CODI resource image sucessfully but gives an error on flashing firmware image after that. So it stopped working. In Advanced options, nothing works ... Reset Cover Display, Start, Stop etc.

Also two bright blue LEDs glow all the time when Cosmo is closed on the finger print panel ...turning COD on and off has no effect ... I do not know if COD was turned on or off from the drop down menu before the first time flashing ... but I guess it should not be a pre-condition. I tried even factory reset and tried again with same results ...

Any help appreciated ...
Looks like  you can only try again and again until it hopefully works (Try to enable "do not disturb" and "flight mode", so there is less chance for things getting interrupted, at least there have been reports of the update being more reliable then). When I have flashed the update, CODI has been enabled. (Don't know if this is related to success, and still needed two attempts to complete)

54
Cosmo Communicator - Hardware / New Cosmo Firmware Update
« on: December 14, 2019, 07:12:48 am »
Quote from: TauPan
Quote from: mithrandir
Quote from: TauPan
I have just looked at the OTA ZIPfile linked here.

The ZIPfile contains binary patches for the boot partition. Patching a binary that has already been modified results in garbage, most likely. This is why booting fails for people who tried to update their rooted Cosmo.
Right, the boot image would be outdated, but I on't think there have been changes to it. From the changelog all seems UI related. If there were a new kernel build, ok, but I don't think so.

Excuse the repetition: I looked inside the zipfile, which you can do too and there is a binary patch to the boot image, which is the reason why people have been soft bricking their cosmos.

If there were no changes to the boot image, there would be no reason for it to be patched. So there are definitely changes to the boot image in the OTA, we just don't know which.

It could be changes that were too small to be mentioned in the changeloog, such as small bugfixes, or compatibility fixes, or even changes required by the following updates.

Also, if the next OTA update also patches the boot image, you won't be able to fix it by flashing your outdated boot image before, as the next patch will require the updated boot image to work!


Right, so we have to keep in mind there might be changes causing problems. Didn't expect changes to the boot image. Obviously it would be better to "magisk" the patched boot image an keep a backup of the non-magisked version for later updates. Well, I didn't backup this image before flashing the old magisked version again... Since for the time being it seems to work somehow I'll just wait for the flashable images from PC.

The next OTA will fail anyways in that case, no matter if we have the first or the second boot image patched with magisk. The only way to use OTA then would be to have the image patched by the first OTA (which I did not backup).

So the advice should be to at least keep a backup of the original OTA-patched version for later updates or to use the PC supplied images once available. We most probably will be getting a pre-rooted image, so this is the way to go, since we will then be able to lock the bootloader again and get rid of the 5 sec. boot delay.

55
Cosmo Communicator - Hardware / New Cosmo Firmware Update
« on: December 13, 2019, 04:23:39 pm »
Quote from: TauPan
I have just looked at the OTA ZIPfile linked here.

The ZIPfile contains binary patches for the boot partition. Patching a binary that has already been modified results in garbage, most likely. This is why booting fails for people who tried to update their rooted Cosmo.

I don't know if the binary patching employed in google's `update-binary` command does any kind of safety checks, but apparently not, otherwise the update would just fail, I guess.

Flashing back the original boot image should work, but then you don't have an updated boot image, so the following leads to a working Cosmo:

Quote from: mithrandir
Got the update installed on the rooted Cosmo..

1.  Flash the original boot image using SP flash tool (Gemini version is outdated and does not work for Cosmo)
2.  Perform the OTA update
3.  Flash the magisked boot image again

Images come from here: https://www.oesf.org/forum/index.php?showtopic=35879 (Thanks ZimbiX)



Mith

but the boot image will be outdated (but rooted).

Instead I suggest the following procedure (Step 1. and 2. unmodified):

3. Read back the updated, but unrooted boot image via SP
4. Patch it with magisk
5. SP flash the modified image to the Cosmo
6. Maybe upload it here for additional karma points.

Right, the boot image would be outdated, but I on't think there have been changes to it. From the changelog all seems UI related. If there were a new kernel build, ok, but I don't think so.

56
Cosmo Communicator - Hardware / New Cosmo Firmware Update
« on: December 12, 2019, 03:20:28 am »
Quote from: TheProfessorNQ
[Thanks Mith! I'll give that a shot tonight. Gotta go have dinner with the in-laws first. I had it apart at work, but that battery connector looked real odd to me. More like it was soldered on. Probably a mix of bad vision + light that are far too bright in my lab. I'm assuming it pulls up, not out? As in away from the keyboard, not towards the other end of the device. Oh! And to be clear, it doesnt make it to the rotating planets. Just the initial PC splash screen.

Thanks again!
-Prof (the NQ means "Not Quite")
Yes, for he Gemini it pulls up. Assuming the Cosmo uses the same battery you should be able to pull the connector upwards. Before one has to remove (for the Gemini, did not open the Cosmo, yet) the black plastic side cover on the connector's side and unscrew a small piece of metal that holds the connector in place. Bu most probably it is the same here.

Mith

57
Cosmo Communicator - Hardware / New Cosmo Firmware Update
« on: December 11, 2019, 05:12:23 pm »
Quote from: TheProfessorNQ
I went ahead with the firmware update. Hit restart or reboot, whatever it said. Now I'm stuck in a boot loop that doesn't get past the splash screen to the boot animation. Then powers off, and immediately restarts. One boot/power off cycle takes about 13-14 seconds. Holding any key/button combinations seems to be of no help. Additional information! I was rooted with magisk. Two failed attempts to install the new firmware, so I flashed the original boot image back to the device and rebooted. That went no problem. Tried the OTA update one more time. This time I didn't get an error message at the end of it. Phone restarted, and here I sit 6 hours later, hoping the battery eventually drains so I can try ADBing in. If anyone has any suggestions, I'd appreciate it. Something I'm noticing as I'm typing this, just as the phone powers down, the screen has a glitch-in-the-matrix style flicker. I doubt that really means anything to anyone, but just in case.

A pre-thanks to everyone!

Most probably you have already tried:
-Press Esc long (takes about 10 secs at the rotating planets)
-Press Esc+silver  button (side) long
-Press Esc+Vol Up/Down (next to the cover display) long

Also had a similar (seemed to be related to a magisk module I am trying to develop...) behavior. For me it helped to "reboot" several times using the Esc long press. Booting works when the blue caps lock led turns off. If it stays on the phone is frozen.

If not faint-hearted you might try to remove the back and pull the battery plug. Once I had to resurrect  the Gemini (now it's undead  this way. It refused to turn on.

Mith

58
Cosmo Communicator - Hardware / New Cosmo Firmware Update
« on: December 11, 2019, 04:45:29 pm »
Quote from: mithrandir
Same for me, so it seems so. How to install the update on an rooted device? If we already had the flashable images things would be quite easy...

Mith

Got the update installed on the rooted Cosmo..

1.  Flash the original boot image using SP flash tool (Gemini version is outdated and does not work for Cosmo)
2.  Perform the OTA update
3.  Flash the magisked boot image again

Images come from here: https://www.oesf.org/forum/index.php?showtopic=35879 (Thanks ZimbiX)

Mith

59
Cosmo Communicator - Hardware / New Cosmo Firmware Update
« on: December 11, 2019, 03:33:19 pm »
Quote from: ArchiMark
Quote from: AP756
You can find the changelog here: http://support.planetcom.co.uk/index.php/L..._Cosmo_Firmware

Bye for now  Fred

PS: update does not complete on my preliminary rooted Cosmo...


Don't know if it's same on Cosmo, but on Gemini PDA, OTA updates would not install on rooted devices. You had to install updates manually.

HTH,

Mark
Same for me, so it seems so. How to install the update on an rooted device? If we already had the flashable images things would be quite easy...

Mith

60
Cosmo Communicator - CoDi / CODI update
« on: December 11, 2019, 06:51:13 am »
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…

Pages: 1 2 3 [4] 5 6 ... 13