EskeRahn

If you can easily press it down, but it just pops up again, I think adhesive is a very likely guess. If on the other hand something prevents it from being pressed down easily, something more severe could be the reason.

As far as I know the keyboard foil is mounted with heat and&or adhesive, so my GUESS would be that your specimen had had this foil mounted with a little too low amount of adhesive and/or is placed ever so slightly wrong with a bit of tension in the foil, that then popped up due to the bump. I would try gently heating with a heat-gun (or hair drier) to attempt to make the adhesive more liquid, so the keyboard can be pushed in place. and then let the device cool back to room temperature, and see if it stays in place You could also try contacting support, and hear if they have a bet

I think it would work just fine, and I believe someone in here have actually done it, unless my memory fails me. BUT note that the off centre placement of the USB-plug might make it hard to place in a suitable way, as they most likely will come with a flat cable.

Some good news: The v2 seems just as lean on the battery as the Test22 (This is from the unit without GSM) The dip at the right side is all the install mess described above, but that apart it seems pretty parallel after a few hours sleep.

After a whole hour it finally continued. And failed to boot.... Suggesting me to retry the boot or do a factory reset... The retry failed too... I will try a manual flash, and see if that fixes stuff... That fixed stuff, and it booted (almost) normally except launching the qx1000 install wizard - that I just skipped.

Doing it manually will DEFINITELY be faster that the OTA way. After 20 minutes it is only at around 30% in the "Finalising package installastion" stage... I explicitly omitted it to see how it would handle the update without. Previously I have had the gapps as part of my batch installation previously described in this thread a few times. And I will most likely go back to that, and use the updater for notifying me only....

Oh I let it do the update, it is almost finished with the "Preparing for first boot" stage.... 🙂 If it is still there I will try to boot into recovery and sideload, and see if that fixes it 🙂

Installing V1 over Test 22 without reinstalling the gapps leads to a repeated "Google play services keeps stopping...." ...But the updater fetches the next version as it is supposed to 🙂

Great, then we can eliminate that as a possible reason, thanks.

Oh indeed, but battery charging above 30°C should be avoided if possible. Oblivious it is not a sharp limit. from https://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries

I have not had it reach the point of booting, but I certainly had it go way beyond 30°C. Both with an aPple S6-, a BB Priv, a Samsung S8- and the Pro1.

Yes I never had wiped moving forwards between your test versions. Only when I tried to move backwards. 🙂

Well please enlighten me on how I was supposed to know you knew what Giteki is? Did F(x)tec or BicCamera tell you when the phones in question were ordered? And the amount? For what I know, these could be old orders too. But sure they might not. I'm not taunting, but a little tired of accusations that seems to be based on assumptions in here.

Well I can not answer the "why", but for all we know they could have had an old order too. And since they are already "Out of stock", it is not that it is in any way in general availability in the Japanese market either. When I checked their web-store on July 11, it was the same. Marked as "in stock", but browsing through the actual stores they were marked as coming at a later day. So if they really had just one for each store it must have sold as hot cakes, as there are none now. And unless I misunderstood something, Giteki is not a matter of a special version, but a mater of test

If the Japanese market (one seller BicCamera) ever had it, how many did they get? 1?, 2?

Sorry for being unclear. Indeed use plugged in. BUT charge the phone before starting the navigation. This way the battery is 'idle' at 100% during navigation, and thus any heating affects the battery less. Worst case is: Quick charge heating the device and battery Heavy usage of the phone, heating the device and battery (And if placed at a hot place it is even worse) LiIon batteries generally dislikes being charged while the temperature is above about 30 deg Celscius. It shortens the overall lifespan of the battery.

Sometimes going back without wipe works. There was a similar issue when attempting going from 9 to 8 (if I recall correctly) but OFTEN it will work if changes were minor, but do not expect it in general unless they explicitly say so. And the changes 20 to 21 as well as 21 to 22 clearly was not minor. So stepping back without wipe is unlikely to work.

Did you wipe user data between flashes? In general there are no compatibility going backwards only forwards. So you should not expect a stable system if you do not wipe your user data stepping backwards.... It is just as when you switch between Stock and Lineage (in either direction). You must wipe the user data.

This COULD be a thermal issues. IF a device is quick charging while using GPS at the same time, the risk of overheating is quite high. (But sure the phone OUGHT to throttle down the charging rate if the temperature gets too high) In general if using a phone for car navigation I would strongly advise to charge it before the trip. So the battery is not charging while the device is hot. See e.g. this

Battery stamina MUCH improved with 22. Here 20, 21 and 22 within the last few days;

I do believe that there was an immediate visible change with the boot and redraws from 21 to 22, Will report back on the battery after some hours 🙂

I would not have noticed if you had not said it... So if it helps someone, then fine by me 🙂

Installed Test22...

There should be a charge_full_design and charge_full also, that might help the calibration. Found this googling https://dev.bettermobileapp.com/article/10435402/-+removed+-

I saw no substantial differences going from 19 to 20, but did from 20 to 21.