OESF Portables Forum
Model Specific Forums => Gemini PDA => Gemini PDA - Android => Topic started by: gidds on October 10, 2018, 12:11:58 pm
-
My Gemini (4G x27) has just offered a firmware update! When I clicked Download, it crashed; but I was able to download it by going to Settings -> About phone -> Firmware Update.
It promises:
• The latest Android security patch has been applied, device security has been further enhanced.
• Optimize keyboard settings and performance.
• Optimize speaker sound quality.
• Optimize performance and stability.
• Fix other bugs
The PatchID shows as ‘Gemini-7.1-Planet-12062018-V2.<2018-06-1216:54>’. (2018-06-12 was about when the last one was released; perhaps the ‘V2’ is the significant bit here.)
I'm about to try installing it — fingers crossed… I'll post my experience here. Please do comment if you've tried this and/or can confirm what it does!
-
My Gemini (4G x27) has just offered a firmware update! When I clicked Download, it crashed; but I was able to download it by going to Settings -> About phone -> Firmware Update.
It promises:
• The latest Android security patch has been applied, device security has been further enhanced.
• Optimize keyboard settings and performance.
• Optimize speaker sound quality.
• Optimize performance and stability.
• Fix other bugs
The PatchID shows as ‘Gemini-7.1-Planet-12062018-V2.<2018-06-1216:54>’. (2018-06-12 was about when the last one was released; perhaps the ‘V2’ is the significant bit here.)
I'm about to try installing it — fingers crossed… I'll post my experience here. Please do comment if you've tried this and/or can confirm what it does!
I cannot succede to install nothing in my Gemini triple boot rooted Android. The build number is already Gemini-1.1-Planet-12062018-V2, however...
But here the Security Pactch Level is still November 5 2017...
Salvo
PS: I tried with Flash Tool and "Download only" method, as in dual/triple boot is NOT possibile to update via OTA...
-
The update failed!
It took only a few seconds to apply the patch, and reboot. But after a few seconds more it was showing the Android Recovery screen. At the bottom it said:
Update.zip is not correct
Installation aborted.
I pressed Enter to select ‘Reboot system now’, and it then booted Android as normal.
All looks unchanged so far, with no ill effects (thank goodness).
It hasn't applied the update; the current Build number is ‘Gemini-7.1-Planet-12062018-V2’, and Firmware Update still offers to download the new version.
The only cause I can think of is that I previously installed the rooted firmware. Maybe this update is only for the original, non-rooted version? Though if so, I'm surprised it was offered automatically…
-
The update failed!
It took only a few seconds to apply the patch, and reboot.
Unless you have a really fast connection that does not seem right, the patch is 187.5 MB.
I used the Detect Update option in the Android settings and it seems to have installed correctly, although for some reason it rebooted to the recovery volume but just selecting Reboot there started Android which according to the Detect Update now has the latest version..
-
Gemini-7.1-Planet-08102018-V2.<2018-10-08-19:35
Update succesfull
Original Android, not rooted/no multi-boot.
However:
1 After reboot i had to pick a language and Dutch isnt offered, so had to choose English but when complete it was all OK
2 All widgets were gone. Had to put that together again but thats not a big problem.
-
Unless you have a really fast connection that does not seem right, the patch is 187.5 MB.
Oh, it took a couple of minutes to download the update; it then took just a few seconds from tapping Install to showing the Android Recovery page.
FWIW, I found the update file: /cache/update.zip, 196600590 bytes. ‘unzip –t’ reports that it's a valid zip file, and all the CRCs match, so it doesn't look like it got truncated or corrupted.
Looks like it doesn't work on rooted machines…
-
The file /cache/recovery/last_log looks like it might have details of the update process.
My best guess at the most relevant section is:
[ 3.383955] failed to stat "/cache/saved.file": No such file or directory
[ 3.383963] failed to load cache file
[ 3.383971] script aborted: E3005: "EMMC:/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/boot:<lots of numbers>" has unexpected contents.
[ 3.678415] E:Error in /cache/update.zip
[ 3.678461] (Status 7)
[ 3.678500]
[ 3.786711] W:failed to read uncrypt status: No such file or directory
[ 3.786855] I:/cache/update.zip
[ 3.786861] 0
I don't really know, but if I had to guess, I'd suspect that the EMMC:… filename (which is a symlink to /dev/block/mmcblk0p22) is pointing at the boot firmware, and that the ‘unexpected contents’ is because it's checking the existing firmware before applying the upgrade. Presumably mine doesn't match because it's the rooted one…?
-
Curious that Planet has not yet updated the Gemini firmware page: http://support.planetcom.co.uk/index.php/Gemini_Firmware (http://support.planetcom.co.uk/index.php/Gemini_Firmware)
======
After tapping "Firmware Update" I see:
Progress (its' bar is not moving)
Update started, please do not power off unit...
Testing update mistake, please download the update package again.
======
Perhaps the "mistake" is auto-downloading and updating over cellular date instead of WiFi.
Re-trying via WiFi... (is SLOW) instead of fast 4G cellular data.
WiFi download is many, many minutes too slow.
Only "Patch:ID..." scrolling info.
Me thinks this update is another too-soon mistake because it is not-ready (again) for prime time use.
The download process has got to be faster... clock ticking away at 15 minutes downloading via WiFi.
WTH is up with that nonsense?!
======
UPDATE: Download failed three times.
Gemini popup wants (SLOW and ONLY) WiFi on for downloading. It refuses download via cell data and that means turning the SIM card off.
======
UPDATE: Download success on the fourth attempt because SIM card / cell data switched OFF.
That seems counter-intuitive and a waste of time trying successively to get this DL to happen and installed.
"System Upgraded - Congratulations....!" popup.
Settings>About Phone>Build number: Gemini-7.1-Planet-08102018-V2
======
-
What Jos said.
My update worked flawlessly and the current "Firmware" screen confirms that it is the update of 10082018 and no newer available.
Indeed, I needed to pick the language.
The entire language list was in Dutch (Engels/English , Italiaans/Italiano, Frans/français... you got the picture).
Only one language was missing: Nederlands/Dutch !
Whatever...
I chose Engels VK / English UK and got the entire Gemini in English.
I then went into configuration, added Nederlands, changed its priority to #1... and hey, presto... the Gemini is back in Dutch again !
Otherwise, it seems to be fine.
Well, it needed to confirm its quirky reputation...
-
I got a fail too.
Specs: Gemini x27/US Keyboard; T-Mobile; 3 partitions [ 1) Stock Android 2) Debian 3) Sailfish--partitioned with same sample sizes from tutorial ]
Download is correct, authenticated, but on reboot:
Error: Partition table not match
Update.zip not correct
Installation aborted
Tried 3 times, same result (also copied ota.zip to sd card and upon reboot, tried to install from sd card with same fail),
Jake
-
I just installed the update. Now my Gemini keeps booting into TWRP. Any suggestions?
-
Another fail from my device. I had been meaning to wipe Debian and Sailfish and go back to stock Android full-time.
I did so, successfully, and I'm STILL getting a "Error: Partition table not match" upon reboot.
So my amateur opinion is that if you have custom flashed your device, even if you've returned to stock settings afterwards, you're SOL, so far, with this update.
Geez,
Jake
-
Another fail from my device. I had been meaning to wipe Debian and Sailfish and go back to stock Android full-time.
I did so, successfully, and I'm STILL getting a "Error: Partition table not match" upon reboot.
So my amateur opinion is that if you have custom flashed your device, even if you've returned to stock settings afterwards, you're SOL, so far, with this update.
Geez,
Jake
UGH!!!!!! Now I'm without a phone today because of this update which is bad news for me to get any work done at all.
-
What Jos said.
My update worked flawlessly and the current "Firmware" screen confirms that it is the update of 10082018 and no newer available.
Indeed, I needed to pick the language.
The entire language list was in Dutch (Engels/English , Italiaans/Italiano, Frans/français... you got the picture).
Only one language was missing: Nederlands/Dutch !
Whatever...
I chose Engels VK / English UK and got the entire Gemini in English.
I then went into configuration, added Nederlands, changed its priority to #1... and hey, presto... the Gemini is back in Dutch again !
Otherwise, it seems to be fine.
Well, it needed to confirm its quirky reputation...
I too got the update without any problems. (But was a bit apprehensive of the screen with "reboot now" and some other options; thought it would restart automatically by it self. Could I have messed things up with choosing another option...??)
What DID puzzle me a bit was that the only "Norwegian" I could choose in the setup after applying the update was "nynorsk" (which is a "construct" of a written language from different dialects in Norway back in the 1840's to "counter" the terrible written language we had which was heavily influenced by Danish, since we recently were under Danish rule, and traded much with them...), and not "bokmål" (a little more than 10% in Norway prefer "nynorsk" the rest prefer "bokmål"). I needed to go into the settings and correct it again afterwords. (YEs, you assume correctly that I am no big fan of "nynorsk"...)
And it, as usual, didn't take my keyboard selection from the setup after upgrading, I needed to set it up from settings (actually from the notificatin the first time). And when I changed to "bokmål" instead of "nynorsk" it broke the keyboard-setting again...
The update has brought these changes as far as I can actually SEE so far:
- I've got system wide spell-checking! (I needed to set it to Google to get Norwegian, and you need to go in to settings to change it if you temporarily need another language. And don't know how it plays with office-editors with their own spell-checking yet...)
- You can now disable the silver button from starting voice-assistant! (And a few other new settings too under "Gemini settings"...)
I still have a "shortcut-list", which doesn't do what it says (I thought it had disappeared, after seeing it under "Gemini-Keyboard" configuration earlier, but I think it has been there all the time). It is under "Language and input" or something similar (my Gemini is still in Norwegian...). Under "Physical keyboard" the bottom choice is "Shortcut-keys" or something similar. It lists a few "magnifying glass" + "key" (which should be the silver button + "key"...). But I can't get it to do what it says... Anybody else getting any shortcuts to work? It even lists correct icon for just the silver button, so it must have some access to the system (I have set up Saiy for voice assistant).
-
My upgrade completed successfully or so i thought. I missed a call which went to answer phone. This asked me to phone an 0800 number. When trying to use the phone it refused to make the call as card 2 had no provider! My sim to Virgin is in slot 1 with no card in slot 2. Why did it try to use slot 2 to make the call? It has worked using the sim in slot 1 and the update obviously changed a setting when it shouldn't have done!
-
My upgrade completed successfully or so i thought. I missed a call which went to answer phone. This asked me to phone an 0800 number. When trying to use the phone it refused to make the call as card 2 had no provider! My sim to Virgin is in slot 1 with no card in slot 2. Why did it try to use slot 2 to make the call? It has worked using the sim in slot 1 and the update obviously changed a setting when it shouldn't have done!
It did the same for me: First call I was attempting to make after the upgrade didn't go trough with a warning/message of something like "the card isn't enabled, enable now?". It is of course just a matter of going into settings and change "Calls" back to "Card 1", but a bit annoying anyway. It should have worked for incoming calls even without changing the SIM back??
-
'Tis borked here with the partition not match message. Looking at the recovery log it ppears that the scatter file is expecting a particular partition size/layout so if you've done something rash like dual boot the device using Planet's own tool this isn't going to work for you.
I do absolutely love my Gemini but this kind of nonsense? <SIGH>.
Rosie
-
This is simple - read the docs - it states it clearly, that it is only possible to do the automatic update on non-modified android installation. As soon as you create your own partition layout, the automatic update can not work. You shoule be able to do a manual update thru SD card. This is very similar to other android devices.
My update with original Android was smooth.
I do have a different issue - before the update it was possible to select more keyboard layouts in Gemini keyboard configuration. Now there is a new dialog for the keyboard configuration and it only allows one keyboard layout selection. I can not switch the keyboard layouts fast anymore. Does anybody know how to solve this?
-
Same here with the first phone call.
Did not work.
The thing offers "to switch on the card". Yeah.... that sounds like a good idea.
Still doesn't work.
But wait... it switched on CARD 2 and there is no CARD 2.
Sigh... computers...
Oh... and I received a new business laptop yesterday. Which is cool, of course.
But that new machine, supposed to be a copy paste of the old Windows one, is also missing all kinds of things and settings.
-
>> You shoule be able to do a manual update thru SD card. <<
Not with this download. It's labeled ota.zip and when you try a manual install of it from sd card at boot menu, those who have used a custom scatter file will get an aborted install error.
Jake
-
Thanks covex, that's helpful. I'll give it a go (once I work out where to find the update.zip).
This is simple - read the docs -
What a novel idea.
I'm guessing they might even have the download location in them as well.
Rosie
-
This is simple - read the docs -
What a novel idea.
And where, precisely, are the docs on an OTA update??
All you get is the page listing the improvements — which I posted at the top of this topic. Nothing there about it failing to work if you've made any changes, or direct downloads, or anything else…
Also, my Gemini is not dual-boot: I installed a rooted Android, but left the partition layout exactly the same as when it was delivered. But the upgrade still failed. So I think it needs not just a specific partition layout, but also a particular (non-rooted) Android firmware installed.
-
This is simple - read the docs -
What a novel idea.
And where, precisely, are the docs on an OTA update??
All you get is the page listing the improvements — which I posted at the top of this topic. Nothing there about it failing to work if you've made any changes, or direct downloads, or anything else…
Also, my Gemini is not dual-boot: I installed a rooted Android, but left the partition layout exactly the same as when it was delivered. But the upgrade still failed. So I think it needs not just a specific partition layout, but also a particular (non-rooted) Android firmware installed.
Good call gidds, I'm having some trouble locating the elusive docs as well. \The update.zip is downloaded to /cache. I can't getto that as I've not rooted my phone (some of the banking apps I use won't play with a rooted phone). As you have then you should be able to use adb to pull the update.zip to the connected computer then copy it over to an sdcard, boot to recovery and update from there.
I'm still puzzling out how to get the update.zip without rooting my phone because I don't want to spend the rest of the evening setting it up as I like it again. Any hints appreciated.
Rosie
-
Just applied Firmware Update to my Gemini 4G + WiFi running out-of-the-box stock Android.
All went well. On bootup language was requested as was Gemini keyboard configuration. Nothing seems to have been lost. All apps present. I don't use the device as a phone, only as a productivity device, so I could not test telephony. My Sim card worked, though, as 4G was enabled.
Guess it's safe to be a simpleton.
-
Here is the doc I was referring to: http://support.planetcom.co.uk/index.php/D....2FLinux_Gemini (http://support.planetcom.co.uk/index.php/Debian_Notes#Updating_Android_on_a_Android.2FLinux_Gemini)
-
Here is the doc I was referring to: http://support.planetcom.co.uk/index.php/D....2FLinux_Gemini (http://support.planetcom.co.uk/index.php/Debian_Notes#Updating_Android_on_a_Android.2FLinux_Gemini)
Thanks, I knew about that one and have even read it multiple times (unconventional, I know). It doesn't have the latest firmware available or, if it does, I can't see the link. Just in case it's my old eyes if anyone can point me to the link I'm missing that'd be appreciated. Also, this is the procedure for completely reflashing the phone rather than just applying an update, which would mean spending an evening setting the phone up to work the way I want it to. Again.
Rosie
-
Here is the doc I was referring to: http://support.planetcom.co.uk/index.php/D....2FLinux_Gemini (http://support.planetcom.co.uk/index.php/Debian_Notes#Updating_Android_on_a_Android.2FLinux_Gemini)
Thanks, I knew about that one and have even read it multiple times (unconventional, I know). It doesn't have the latest firmware available or, if it does, I can't see the link. Just in case it's my old eyes if anyone can point me to the link I'm missing that'd be appreciated. Also, this is the procedure for completely reflashing the phone rather than just applying an update, which would mean spending an evening setting the phone up to work the way I want it to. Again.
Rosie
You're in the right direction... My understanding is that if someone has made their Gemini multi-boot or rooted, then they have to do updates as per the link's instructions. The issue is that the latest firmware is OTA and not yet out on the Gemini Firmware page... Why these two things can't be made available simultaneously is a mystery, but I believe we just have to wait!
-
You're in the right direction... My understanding is that if someone has made their Gemini multi-boot or rooted, then they have to do updates as per the link's instructions. The issue is that the latest firmware is OTA and not yet out on the Gemini Firmware page... Why these two things can't be made available simultaneously is a mystery, but I believe we just have to wait!
this is true. Are there good reasons to delay the "not OTA" firmware update? Please...
Salvo
-
Good call gidds, I'm having some trouble locating the elusive docs as well. \The update.zip is downloaded to /cache. I can't getto that as I've not rooted my phone (some of the banking apps I use won't play with a rooted phone). As you have then you should be able to use adb to pull the update.zip to the connected computer then copy it over to an sdcard, boot to recovery and update from there.
Though after thinking about it a bit there's probably not much point as I don't think that'll work either. I'm not a huge expert on Android firmware but I think it's likely the partition table the update is expecting to work with is zipped up inside the update.zip. All you'll achieve by trying to work around it this way is waste a load of time and end up exactly where you are now.
The only way I could see an OTA image for partitioned Gemini's working is if it were generated on the fly with the partition table expected zipped into the OTA image you end up downloading. I'm guessing that something like this is whata's done with Planet's custom partition tool but the difference there is it doesn't have to worry about not destroying everything in its path as you're reflashing the phone anyway. So the custom partitioning must just generate the scatter file with the download itself bunging all the images into the appropriate place.
Solving how to make that work for an update which could end up with an arbitrary set of partitions to work with AND doesn't lose any data would be an interesting problem to solve, though probably not an easy one. I'm guessing that's why we're only getting the plain vanilla version of OTA and may never see a custom partition version.
Rosie
-
It is interesting to note that even if a user uses the partition tool to return to stock android, not other installs, the OTA fails.
The scatter file, even if it's for a default reinstall, must leave some kind of byte residue that flips out the OTA.
I seem to remember reading about PC plans to allow OTAs for rooted Android--which would solve our problem, given the custom scatter--but I may be hallucinating.
Early users: did any of you ever root, then later install the June 12 OTA successfully? Or was root not available before June 12?
Jake
-
Here is the doc I was referring to: http://support.planetcom.co.uk/index.php/D....2FLinux_Gemini (http://support.planetcom.co.uk/index.php/Debian_Notes#Updating_Android_on_a_Android.2FLinux_Gemini)
Ok, I have X27 with triple boot... OTA is not safe, so I must download firmware manually? But I cannot find it?
Did anyone managed to updated triple boot gemini without erasing linux and sailfish partitions?
-
Any solution for rooted Android-only Gemini PDA?
-
I have stock Android image.
Upgrade OK, but no matter what I select in Gemini Settings, the silver button will not start the Google Assistant.
Same for Go to desktop on startup option - it does not work for me.
-
I have stock Android image.
Upgrade OK, but no matter what I select in Gemini Settings, the silver button will not start the Google Assistant.
Same for Go to desktop on startup option - it does not work for me.
Mike Hasley put a post here [Planet - Voice assistant (https://geminiplanet.com/new-features-in-7-1-1-disable-the-voice-assistant/)]. Please, see whether it is good for you.
salvo
-
Same problem here
Before the update,the silver button launched the voice assistant, now it doesn't. Also Fn+space doesn't do anything. All settings are correct, nothing happens...
-
Same problem here
Before the update,the silver button launched the voice assistant, now it doesn't. Also Fn+space doesn't do anything. All settings are correct, nothing happens...
Uninstall and reinstall voice assistant from the store worked for me.
-
Same problem here
Before the update,the silver button launched the voice assistant, now it doesn't. Also Fn+space doesn't do anything. All settings are correct, nothing happens...
Uninstall and reinstall voice assistant from the store worked for me.
It didn't work for me unfortunately....
-
Same problem here
Before the update,the silver button launched the voice assistant, now it doesn't. Also Fn+space doesn't do anything. All settings are correct, nothing happens...
Uninstall and reinstall voice assistant from the store worked for me.
It didn't work for me unfortunately....
try clearing the google assistant and Gemini voice cache too
-
Another issue I've found is that my keyboard is no longer mapped correctly.
I have a US keyboard and have selected US keyboard and language in Gemini Keyboard. Even rebooted, but the following keys are mapped incorrectly:
Shift-2 gives " instead of @
Shift-3 gives £ instead of #
Fn-1 gives | instead of ~
Fn-2 gives # instead of `
Fn-M gives ` instead of '
Fn-K gives @ instead of ;
Fn-L gives ; instead of "
\ gives ' instead of \
Shift-\ gives ~ instead of |
This upgrade is a bit of a train wreck for me, I'm afraid......
Anybody else have the same issues with US keyboard mapping?
-
try clearing the google assistant and Gemini voice cache too
Uninstalling and installing Gemini Voice Assistant did the trick. Thanks for helping!
-
Another issue I've found is that my keyboard is no longer mapped correctly.
I have a US keyboard and have selected US keyboard and language in Gemini Keyboard. Even rebooted, but the following keys are mapped incorrectly:
Shift-2 gives " instead of @
Shift-3 gives £ instead of #
Fn-1 gives | instead of ~
Fn-2 gives # instead of `
Fn-M gives ` instead of '
Fn-K gives @ instead of ;
Fn-L gives ; instead of "
\ gives ' instead of \
Shift-\ gives ~ instead of |
This upgrade is a bit of a train wreck for me, I'm afraid......
Anybody else have the same issues with US keyboard mapping?
You are stuck in UK mode! Have you tried another keyboard? I use SwiftKey and find it very good on the Gemini, better than stock tbh. You could try it to see if it's and issue with PC Gemini keyboard software rather than firmware.
-
Another issue I've found is that my keyboard is no longer mapped correctly.
Anybody else have the same issues with US keyboard mapping?
You are stuck in UK mode! Have you tried another keyboard? I use SwiftKey and find it very good on the Gemini, better than stock tbh. You could try it to see if it's and issue with PC Gemini keyboard software rather than firmware.
Just looked SwiftKey up on Google Play and it appears to be a software keyboard for on-screen typing. How will it solve my keyboard mapping issues on the Gemini physical keyboard?
-
Another issue I've found is that my keyboard is no longer mapped correctly.
I have a US keyboard and have selected US keyboard and language in Gemini Keyboard. Even rebooted, but the following keys are mapped incorrectly:
Shift-2 gives " instead of @
Shift-3 gives £ instead of #
Fn-1 gives | instead of ~
Fn-2 gives # instead of `
Fn-M gives ` instead of '
Fn-K gives @ instead of ;
Fn-L gives ; instead of "
\ gives ' instead of \
Shift-\ gives ~ instead of |
This upgrade is a bit of a train wreck for me, I'm afraid......
Anybody else have the same issues with US keyboard mapping?
I always have to "reset" my keyboard at least a few times after firmware update before it actually "takes". It seems to have the right setting, but I need to go trough the setup again to make it stick. I usually end up setting it up from the notification (if you still got that, it is a quite firm confirmation that the keyboard-selection hasn't taken hold properly...), and then reboot almost immediately, to make sure it "sticks". (I loose the direct access to all the special Nordic/Norwegian characters, which kind of defeats the purpose of the Gemini for me, until I get it sorted again...)
So even though you THINK you have got the keyboard set up correctly, it might not be... (At least for me, that is usually the case, and like I said, it usually takes a few tries each time to get it right again.)
-
Another issue I've found is that my keyboard is no longer mapped correctly.
Anybody else have the same issues with US keyboard mapping?
You are stuck in UK mode! Have you tried another keyboard? I use SwiftKey and find it very good on the Gemini, better than stock tbh. You could try it to see if it's and issue with PC Gemini keyboard software rather than firmware.
Just looked SwiftKey up on Google Play and it appears to be a software keyboard for on-screen typing. How will it solve my keyboard mapping issues on the Gemini physical keyboard?
SwiftKey integrates with the Gemini physical keyboard very well without the need for the on screen keyboard but you can opt for a bottom bar on the screen for predictive text etc
-
Update will not install on my vanilla x25. Although the installer says the file is valid after reboot I get a message saying the file is defective. Can't investigate the file myself because not rooted and the option to copy to the SD card doesn't work. Reported to Planet last week and still waiting for a fix. :-(
Handling of OTAs is a mes! Reflected in the lack of updates to the support website. It's especially annoying not being able to use OTA zips with something like TWRP.
-
>> SwiftKey integrates with the Gemini physical keyboard very well without the need for the on screen keyboard but you can opt for a bottom bar on the screen for predictive text etc <<
That is so intriguing. Can you actually remap pkb keys via SwiftKey? Wow.
Jake
-
>> SwiftKey integrates with the Gemini physical keyboard very well without the need for the on screen keyboard but you can opt for a bottom bar on the screen for predictive text etc <<
That is so intriguing. Can you actually remap pkb keys via SwiftKey? Wow.
Jake
No remapping required, they work out of the box. The only one (I have found) that doesn't is the emoji short cut (function .) but there is an option to select an emoji menu from the SwiftKey bottom bar so no biggy for me.
-
I've spent some time dabbling with the OTA update. It does appear to be impossible to have a rooted/TWRP-enabled version that is up to date, so the choice is between the June 2018 version with root or latest version without. That much we know. However it is possible to slip the .img files from the OTA into an existing rooted setup, so at least the DSP and other device drivers have been updated even if the OS is old.
-
It's less a rooted issue and more of a scatter file--I went back to stock Android only and still can't use the OTA.
But that's interesting, that you can dump and overwrite with updated files from newer image. I wonder if you've updated your security as well.
Jake
-
Tried configuring Gemini Keyboard one more time and it worked. Really frustrating, but at least I can type properly now!
-
It's less a rooted issue and more of a scatter file--I went back to stock Android only and still can't use the OTA.
But that's interesting, that you can dump and overwrite with updated files from newer image. I wonder if you've updated your security as well.
Jake
If you look at the OTA.zip file, it consists of various .dat files (which are the block patches) and a few .img files. Only the img files can be used as-is. So no, it's only the device drivers that I have been able to update.
I don't know enough about altering scatter files to make it fit or why substituting the rooted boot image breaks an OTA-updated installation.
-
If you look at the OTA.zip file, it consists of various .dat files (which are the block patches) and a few .img files. Only the img files can be used as-is. So no, it's only the device drivers that I have been able to update.
I don't know enough about altering scatter files to make it fit or why substituting the rooted boot image breaks an OTA-updated installation.
How are you getting the OTA.zip file? It stubbornly fails to copy to SD for me and I can't access /cache. If I could get the file I could do a manual flash. Update Planet have provided me with links to the OTAs but asked not to make them public. Unfortunately, the instructions on the wiki don't work as advertised because there is a problem with the scatter file so you have to wipe the user partition.
-
If you look at the OTA.zip file, it consists of various .dat files (which are the block patches) and a few .img files. Only the img files can be used as-is. So no, it's only the device drivers that I have been able to update.
I don't know enough about altering scatter files to make it fit or why substituting the rooted boot image breaks an OTA-updated installation.
How are you getting the OTA.zip file? It stubbornly fails to copy to SD for me and I can't access /cache. If I could get the file I could do a manual flash. Update Planet have provided me with links to the OTAs but asked not to make them public. Unfortunately, the instructions on the wiki don't work as advertised because there is a problem with the scatter file so you have to wipe the user partition.
I used Planet's tool to set up multi-boot, which gave me a scatter file. Has anyone else tried using one of these in combination with the OTA.zip (which, TBH, I'd love to get my paws on) to manually apply the upgrade? If so - does it work?
Rosie
-
I used Planet's tool to set up multi-boot, which gave me a scatter file. Has anyone else tried using one of these in combination with the OTA.zip (which, TBH, I'd love to get my paws on) to manually apply the upgrade? If so - does it work?
Rosie
Yes, I tried it and it doesn't work. Turns out the OTA comes with its own scatter file. I couldn't get it to download so had to do a firmware update but that worked fine. You can deduce the URL for the OTA from the release date and using FOTA4. I'm going to start documenting my experiences using DVCS because I think Planet's wiki approach, while well intended, is fatally flawed.
-
The new firmware should be ready also for rooted Android and dual/triple boot: see the Support page and [http://support.planetcom.co.uk/partitionTool.html (http://support.planetcom.co.uk/partitionTool.html)].
I'm going to trying it...
Thanks Planet Computers!
-
Nice find, salvomic!
Jake
-
Nice find, salvomic!
Jake
Well Jake,
Installed just now (Download only, deselecting user data). Android 7.1.1, patch level September 5 2018, build Gemini-7.1-Planet-08102018-V2), Rooted (that says Root Checker Pro).
There was the "bug" with SIM2 for call, I changed it in Settings -> SIM.
I've again issues with spell checkers (here I've Italian, Ensligh, French, Russian installed) that works in Word but not in Notes. Why? First of the upgrade it was the same or so...
Salvo
PS:
To upgrade in rooted Android triple boot with 10 GB Linux/Sailfish OS:
***
Go to http://support.planetcom.co.uk/partitionTool.html (http://support.planetcom.co.uk/partitionTool.html), set your layout (for me rooted A + Debian + SFO, 10 GB for Linux), download all: scatter file, normal and extra files, put in a directory, use Gemini Flash Tool (Windows) with your Gemini connected via USB (left side), choose "donload only" and select all but not "user data" (to not lose your apps and data), restart Gemini (already connected, ESC and "restart"), wait for the process starts and ends, disconnect cable. Then press ESC to restart and wait for the system starts, it asks for language and keyboard... then if all went ok, the new firmware is on.
***
-
For multi-boot and rooted Android follow the new Android Manual Update page (http://support.planetcom.co.uk/index.php/Android_Manual_Update)
-
As salvomic said, the new firmware (Gemini-7.1-Planet-08102018-V2) is now available from Planet's support site (http://support.planetcom.co.uk/partitionTool.html), and can be used to reflash any Gemini!
I've just upgraded mine (rooted Android only), and it went very smoothly. (It's a tedious process, but I noted down everything last time, and this time worked just the same. Planet's new manual update page (http://support.planetcom.co.uk/index.php/Android_Manual_Update) looks pretty good, too.)
It took a couple of minutes to boot up. Everything still works: all my apps, files, data, &c are intact, and Android is still rooted.
I can confirm that:- Earphone/headset buttons now work while the Gemini is closed, so you can pause/play music and answer/reject/end calls without opening it. (This is the fix I've been most waiting for.)
- The built-in speakers now play in stereo, and I think the phase has been corrected too. (It seems louder and clearer, anyway.)
- Includes the latest Android security patches (as at 2018-09-05).
- There's a new selector for locale and keyboard type; you have to reselect these on first boot. (Both of mine are vanilla UK; no issues there.)
I had already installed the new Planet Data app, so I can't confirm that's included. I don't have an eSIM, so I can't test that out. (People reported issues with it being spuriously selected, but I didn't have that.) LEDison doesn't seem to have the enhancement to work with other apps, but I haven't upgraded it.
I can't tell whether keyboard ghosting has improved. (3-key combinations don't cause problems, but 4-key ones can still cause spurious keypresses. I didn't test this before, so I can't tell if that's an improvement.)
The Google Voice Assistant still crashes and then fails to start — but I don't care coz I never used it anyway!
So: for me, a straightforward upgrade, giving a few small improvements, and no problems at all so far.
—————
[…later…]
Actually, there's one problem: my (portable, unadopted) SD card is now writable only by root. It was always owned by root, but my normal user could read and write. Now it can only read, and I can't seem to change the permissions on it…
Any ideas?
-
thanks Andy.
I confirm that Ledison 0.72 hasn't the "App enhancement". Maybe other people could have a different version... Here Ledison was installed first of upgrade (like Data), so I couldn't say if the app included are the same or different.
Anyone else?
Salvo
-
[…later…]
Actually, there's one problem: my (portable, unadopted) SD card is now writable only by root. It was always owned by root, but my normal user could read and write. Now it can only read, and I can't seem to change the permissions on it…
Any ideas?
I too have noticed that I now have "trouble" with saving to the SD card. I wasn't sure if it was the firmware upgrade, or the fact that I updated my office-app, that caused the problems. SOMETIMES I get it to save properly (and it seems I "fooled" it once when it wouldn't save a document, by creating a new one and saving it to the SD-card, before trying to save the "original" again, but it might have just been random luck...).
X-plore doesn't seem to have any problem with the card, and my office-apps can read from it, but trying to save to it usually fails... I have set the SD-card as "main storage", so just saving a file will usually work, but editing ALMOST always fail... Strange
So now I will probably have to copy/move the file I want to edit to the internal storage with a filemanager, edit and save, and then move it back...?
Not rooted by the way...
And it is nice that it seems that the problems with sound and earphones now seem to be solved!
-
Upgraded... Grr, WiFi won't turn on... just sits at this screen. Any thought/ideas re what to do?
-
Problem #2: there's a process called ‘android.process.media’ which is running in the background, chewing up about half of my CPU! I killed it, but it returned, and has been running for several hours now… Help!
-
Problem #2: there's a process called ‘android.process.media’ which is running in the background, chewing up about half of my CPU!
I seem to have fixed this: after doing Settings->Apps->Show system->Media Storage->Force stop, although it restarted, it's no longer using significant CPU.
I'll still keep an eye on it, though...
(It's lucky I spotted it; my battery dropped from about 70% to under 20% in a couple of hours!)
-
I seem to have fixed this: after doing Settings->Apps->Show system->Media Storage->Force stop, although it restarted, it's no longer using significant CPU.
I'll still keep an eye on it, though...
(It's lucky I spotted it; my battery dropped from about 70% to under 20% in a couple of hours!)
strange problem...
Not here: 96% of battery since 8:30 AM till now (about 2 PM) but I used very few Gemini today...
Salvo
-
Same here, Wifi will not turn ON. Well, that is not good.
Upgraded... Grr, WiFi won't turn on... just sits at this screen. Any thought/ideas re what to do?
-
Well, I reverted back to previous version. After bit more looking I saw that the new firmware even does not contain rooted boot image. For me it is useless, I will rather continue with buggy buetooth than no root or wifi.
-
For those who repartitioned for multi-boot, Planet published the image for manual updated on their flashing page
http://support.planetcom.co.uk/partitionTool.html (http://support.planetcom.co.uk/partitionTool.html)
$ unzip -l Gemini_x27_08102018_base.zip
Archive: Gemini_x27_08102018_base.zip
Length Date Time Name
--------- ---------- ----- ----
0 2018-10-10 14:56 Gemini_x27_08102018/
17934720 2018-10-08 13:31 Gemini_x27_08102018/md1rom-verified.img
135168 2018-10-08 13:31 Gemini_x27_08102018/secro.img
204308 2018-10-08 13:31 Gemini_x27_08102018/preloader_aeon6797_6m_n.bin
1007760 2018-10-08 13:31 Gemini_x27_08102018/md1dsp-verified.img
10644947 2018-10-10 14:27 Gemini_x27_08102018/root_boot.img
94208 2018-10-08 13:31 Gemini_x27_08102018/trustzone.bin
10398592 2018-10-08 13:31 Gemini_x27_08102018/boot-verified.img
2424911328 2018-10-08 13:31 Gemini_x27_08102018/system.img
5447562 2018-06-19 12:39 Gemini_x27_08102018/logo_s.bin
73776 2018-10-08 13:31 Gemini_x27_08102018/tinysys-scp.bin
9044296 2018-10-08 13:31 Gemini_x27_08102018/cache.img
4192 2018-10-08 13:31 Gemini_x27_08102018/md1arm7-verified.img
4093232 2018-10-08 13:31 Gemini_x27_08102018/md3rom-verified.img
53470088 2018-10-08 13:31 Gemini_x27_08102018/userdata.img
459824 2018-06-15 13:59 Gemini_x27_08102018/lk_s.bin
11893632 2018-10-08 13:31 Gemini_x27_08102018/recovery.img
--------- -------
2549817633 17 files
-
I flashed the stock Android (no multi-boot) and all went well. A word of caution: I found the spinning-balls screen (upon reboot) to stay on for an exceptionally long time, longer than my other flashes. Be extra patient.
And Salvo, thanks for your fine instructions.
Jake
-
I saw that the new firmware even does not contain rooted boot image.
Well, I used it to reflash my already-rooted Gemini, and it's still rooted…
I found the spinning-balls screen (upon reboot) to stay on for an exceptionally long time, longer than my other flashes.
Mine too. I think it was about 2 minutes.
-
Fascinating! I thought my wifi was just a random hiccup, but now that I read it here: my wifi doesn't really want to work either. So is this an issue with the new image?
I don't have issues with the SD Card, but I set it to be part of the "internal storage" (repartitioned/reformatted to be "integrated") so maybe that's the reason why it works fine...?
I used the rooted variant by the way. Works fine, other than the update process being a horribly abysmal joke. (https://www.oesf.org/forum/index.php?s=&showtopic=35572&view=findpost&p=290339)
-
Ah, I see. Those with partitioned Gemini (like me) should not use the Android firmware from Planet support page, but the firmware downloadable from page with partition tool. The first one is (or was at the time I downloaded it) lacking rooted boot image. Which somehow in combination with custom scatter file messed my wifi. Meantime I solved my problem by fresh install of not rooted stock and rooting by myself (using TWRP and Magisk). Now it seem to work OK.
-
Ah, I see. Those with partitioned Gemini (like me) should not use the Android firmware from Planet support page, but the firmware downloadable from page with partition tool. The first one is (or was at the time I downloaded it) lacking rooted boot image. Which somehow in combination with custom scatter file messed my wifi. Meantime I solved my problem by fresh install of not rooted stock and rooting by myself (using TWRP and Magisk). Now it seem to work OK.
Well if I have root without TWRP it has to be the rooted image, right? I think I got the right one. However, this whole flashing nonsense just illustrates how much it sucks that Planet Computers doesn't provide a proper update mechanism for the rooted variant... really, really annoying. I suppose I'll have to contact support and see if they have an idea...
Edit: just as an additional note, I did a fresh wipe (including resetting userdata) with the original image and an upgrade to the new one with a flash without userdata on the same day, so I'm pretty sure it's not something deeper messed up by me changing settings or whatever. I wrote to support now, hoping they can figure out what is wrong with the image such that Wifi breaks after updating
-
Upgraded... Grr, WiFi won't turn on... just sits at this screen. Any thought/ideas re what to do?
OK, so when I downloaded and used the "LATEST - Gemini x27 Android FOTA4 08/10/2018 - MD5: e524742864bf683932c8e9d6d7f21abf" from the 'PC Gemini Firmware' page it borked my WiFi. However, when I went to the 'PC Gemini Partition Tool' page and downloaded using the 'Download Base Firmware button and used that file it did not bork the WiFi, so now I appear to be good to go.
There apparently are slight differences in the files you get between these two...
-
Ah, I see. Those with partitioned Gemini (like me) should not use the Android firmware from Planet support page, but the firmware downloadable from page with partition tool. The first one is (or was at the time I downloaded it) lacking rooted boot image. Which somehow in combination with custom scatter file messed my wifi. Meantime I solved my problem by fresh install of not rooted stock and rooting by myself (using TWRP and Magisk). Now it seem to work OK.
Yep, you got it!
-
>> There apparently are slight differences in the files you get between these two... <<
Excellent find!
Jake
-
Upon reboot after flashing October firmware, users have noted that they must manually choose sim card 1 for calls. This bug continues after any restart.
I've looked at apps that manage sim cards, but they seem like overkill (e.g. make work contacts use sim 1). Any basic app available that will automatically choose sim 1 for everything and be done with it?
Jake
-
My Gemini (T-Mobile Metro USA) also resets at every reboot / startup its SIM for "calls" to the empty second SIM slot that is automatically switched on.
I suspect that is a EU cell phone preference glitch. Maybe not.
Planet says they are aware of that issue and the next update ought to correct it presently (year's end).
BTW, other known bugs still alive or newly born since the latest firmware update are also under review.
Some like Bluetooth coms being interrupted by faulty do-not-disturb functionality and notifications are believed to be fixed in the OREO update Planet is striving to have available also by year's end.
So, we shall see....
Ifanafi
Upon reboot after flashing October firmware, users have noted that they must manually choose sim card 1 for calls. This bug continues after any restart.
I've looked at apps that manage sim cards, but they seem like overkill (e.g. make work contacts use sim 1). Any basic app available that will automatically choose sim 1 for everything and be done with it?
Jake
-
FWIW, I've had no issues with SIM cards, or with wifi — both work fine as they did before.
However, the upgrade replaced my custom /etc/hosts file. Luckily, I have a backup, so was able to restore that once I spotted the problem.
-
FWIW, I've had no issues with SIM cards, or with wifi — both work fine as they did before.
However, the upgrade replaced my custom /etc/hosts file. Luckily, I have a backup, so was able to restore that once I spotted the problem.
Hm, I've applied the update on my triple-boot x25 (following the instructions at http://support.planetcom.co.uk/index.php/A...d_Manual_Update (http://support.planetcom.co.uk/index.php/Android_Manual_Update). Wifi is fine, but it cannot see the SIM. The SIM works, I can call from it in Sailfish, but not in Android.
I have tried removing and re-inserrting the SIM, also wiping the cache from the recovery menu, but the SIM icon stayed grayed out with a line through it and everything in the settings menu relating to the SIM is deactivated.
Any ideas, anyone?
Edit: I cannot turn aeroplane mode off: the aeroplane icon in the pull-down status menu just blinks slowly if I tap it. I can turn both Wifi and Bluetooth on and off, and both work.
Under "SIM status" and "IEMI information", everything is either unknown or not available. However, I don't think that I have somehow lost the NVRAM. First, I can call from Sailfish. Second, I backed up the NVRAM partition according to http://support.planetcom.co.uk/index.php/L...NVRAM_partition (http://support.planetcom.co.uk/index.php/Linux_Flashing_Guide#Backup_the_NVRAM_partition) and the file I got is identical to the one that I got from when I originally backed it up before the first time I reflashed.
-
Right. I just restarted the Gemini and found indeed that it reverts to the non-existing second card for voice calls. Very annoying.
I had a few 'runs' of the Gemini where it succeeded to carry on on one battery charge for 3 or 4 days.
Since about 1,5 weeks it is back to its original "barely 2 days".
This did not happen immediately after the update (so the update is not at fault) and I did not change my use of the Gemini (as far as I know).
-
Right. I just restarted the Gemini and found indeed that it reverts to the non-existing second card for voice calls. Very annoying.
I had a few 'runs' of the Gemini where it succeeded to carry on on one battery charge for 3 or 4 days.
Since about 1,5 weeks it is back to its original "barely 2 days".
This did not happen immediately after the update (so the update is not at fault) and I did not change my use of the Gemini (as far as I know).
I do believe that the SIM2-activation might be related to the eSIM Wallet app. If you just open the app it changes the calls to SIM2 (the eSIM). (WHY does it need to change the SIM if you just open the app??!?) So it might be activated on some level on a restart, and that might be why it changes to SIM2??? I just tried to open the app now, and on first open, it changed the SIM for calls. The next time it gave some crash-report, but still CLAIMED it changed the SIM for calls... (but it didn't...??). (I looked at the different settings in the app too, so that might have "triggered" the crash/crash-report somehow??)
But I would like to hear if somebody has got an office app (or any app that edits files...) to work properly with SD-card (unadopted!) after the upgrade. Like I said in an earlier post I have got it to work sporadically, but not reliably...
And I still get about 2 days use out of my Gemini on "normal" (for me!) use. It usually uses 1-2% of the battery per hour. So I don't see any change in regard to that.
-
Hm, I've applied the update on my triple-boot x25 (following the instructions at http://support.planetcom.co.uk/index.php/A...d_Manual_Update (http://support.planetcom.co.uk/index.php/Android_Manual_Update). Wifi is fine, but it cannot see the SIM. The SIM works, I can call from it in Sailfish, but not in Android.
I have tried going back to the June 2018 firmware, but the SIM still isn't recognised. I'll have to take this up with Gemini next week.
-
Just as an update to everyone with broken wifi on rooted android: you most likely have the wrong, regular non-root image installed as an upgrade to the rooted one (which as already mentioned above, is slightly different).
How to fix it:
Go to the gemini partition manager website ( http://support.planetcom.co.uk/partitionTool.html (http://support.planetcom.co.uk/partitionTool.html) ), specify rooted android in all boxes as usual, then click download firmware image from there.
Unpack the folder you get, throw in your original scatter file you got when you first installed, then open it in the firmware flasher and choose "Download Only" with "userdata" unchecked (such that your configurations and apps will remain). Then press the flash button and reboot your gemini while attached over USB as usual for the flashing, and wait for it to finish. This worked for me and fixed the wifi.
Edit: added direct link to partition manager
-
Ah, I see. Those with partitioned Gemini (like me) should not use the Android firmware from Planet support page, but the firmware downloadable from page with partition tool. The first one is (or was at the time I downloaded it) lacking rooted boot image. Which somehow in combination with custom scatter file messed my wifi. Meantime I solved my problem by fresh install of not rooted stock and rooting by myself (using TWRP and Magisk). Now it seem to work OK.
Yep, you got it!
I started out with that one, got spontaneous reboots right after booting.
Tried to kick Magisk off, then used non-rooted boot.img (from the generic download). Reboots all along the way, sometimes I had much more time to do things adn then when rebooting, it wouldn't stop rebooting anymore..
Spontaneous reboots now happen when I connect to the local wifi network.
Then I found this thread.
Reinstalled the rooted image from the partition tool download (fresh download, but same file anyway). No improvement.
Any ideas welcome.
Mailed Planet Computers, will keep you posted.
-
Hello,
thanks for the hint, I didn't update yet because rooted image was mentioned nowhere.
But:
(...)Go to the gemini partition manager website(...)
A link would be much appreciated. Saw that kind of referrence in another post, too ("Go to page with ..."). I don't know what page you mean.
Thanks
Kind regards
P.S.: Ok, found it accidentally: http://support.planetcom.co.uk/partitionTool.html (http://support.planetcom.co.uk/partitionTool.html)
P.S.: @bloblo: thank you for pointing out that method. I flashed the new rooted firmware now and it worked marvelously. I forgive you thus for not giving the actual link
-
Mailed Planet Computers, will keep you posted.
Planets responded appropriately, but that dd not solve the problem.
I dug a bit through all the changes I made, and started undoing my habitual config changes.
When I revert "Enablw Wi-Fi verbose logging" (to off, aka disabled), the reboots cease. That was unexpected...