Leaderboard

For what it's worth, I never have auto-rotate turned on. That allows me to occasionally use rotate lock (the little weird icon that mysteriously pops up in the nav bar-- though it may pop up without the nav bar) to get specific rotation effects. I use it to lock Kindle in portrait while I have keyboard out as a handle for easier holding while reading... Kindle in landscape sucks! 😉 I never have trouble with apps not going into landscape when keyboard is out unless the app just doesn't do landscape at all and the auto rotate doesn't help. I've always kept autorotate off on all my phone

AnySoftKeyboard also does not exhibit that bug and does not have that annoying suggestion bar popup either. Sounds like the best and so far only option to use your full vertical screen real estate with keyboard open and gesture navigation without hindrance.

Sorry I do not. I always flash first the bootloader, then the main image to (a), and finally the gapps package to (b). As I never really tried to figure out the logic, just made a batchfile implementing a step-by-step guide from @tdm (The root-part is a rudiment from 16.0) @ECHO off if %2.==. goto :EOF ECHO * Wait for boot to bootloader to finish (or do manually holding VolDown+Power) adb reboot bootloader pause fastboot flash boot_a %1 shift fastboot --set-active=a REM fastboot reboot recovery does not work, so do manually: ECHO * Roll down to "Recovery Mode" with VolDown, and

So I think it does an update file by file instead of pulling up like an image or this kind of sideloaded application already lies on a separate partition.

Now that's interesting. If you try this, I'd be interested to see how it goes, and what banking and other apps say after that.

I found this entry point: https://lineageos.org/Google-Play-Certification/

Worked well here too when applied OTA.

The task-switcher IS quite confusing, and buggy when opened. If working with the keyboard CLOSED, and with autorotate on, it works as expected, Right/Left to switch, and Up to close.. (Though slightly confusing that the 'screenshots' is from last used orientation, and not what you will get selecting it) When the keyboard is OPEN, the task-switcher is double rotated. That is it works Up/Down switches, and Left closes held normally in landscape (And held tilted to portrait it works as it ought to in landscape, rotated only once) ADD: It also matters how HORIZONTAL you hold it, as aut

(lineage-18.1-20210823-nightly-pro1-signed.zip on August 5 security patch installed smoothly using adb sideload and Open_Gapps-arm64-11-pico-20210712) ...But the reintroduced Accessibility / keyboard bug is not (yet) fixed, see above. Did not try to do a factory reset first...

I am currently very sad as (for me) it seems to be a bug in the kernel driver which prevents me to use my device in full functionality, so currently its keyboard is only half-working or less for me... 😞 I am sad because it is unlikely for me to repair it being it is my daily driver and I don't know about other parts which may be related of this scancode modification. Maybe replacing "KF_ALTGR" with "KF_FN" in qx1000.c file would solve it but it is only a guess without deeper knowledge or more serious interpretation of that code and as if it would need experimenting on my daily driver,

On stock OS, these keys only produce 25 and 39 (respectively) and slant arrow has a scan code of 464 independently of these keys, there are no strange multi scancode generation...

I ran into some problems with slant arrow when I have tried to redefine my keyboard map. It seems originally it was named as "fn" but it was renamed to "ralt" under LineageOS. So I have tried to do the same keyboard map for me where national accents should go (for example) to keys '[' and ']'. I have used a layout where keyboard was QWERTY and I could reach national letters by slant arrow+key combination. Currently it seems this kind of definition is not possible for all of the keys, but works on others. If I look of the keycodes in "KeyEvent Display" application, I see the

BUT It works better on LOS than on stock! If you after starting to type, tap the 'down' it actually STAYS down during typing!! So we really only need some hot key-combo that can do this back/down soft-key action....

As mentioned above it should be doable as I can see the key events coming in. Just need to debug it to see what's the hiccup. I got Fx Service working already but that one feature is still not there yet. Btw maybe we should communicate with FxTec to tell them we want that to work better on the Pro1X I mean it looks like they are working on drivers at the moment. The issue is that on the Pro1 I could not see a proper sensor to use for that. Instead we had to rely on those magic key events. Since they are still there in LOS I'm assuming this is part of the blob of closed source drivers.

One of the things (apart from the certification) that holds me back, is that @Slion's nice tool "Fx services" for going into sleep mode when the magnet in a flip case hit the 'magic' spot, does not work on Lineage. (I use an ancient version 0.4 with almost only that functionality, it can now do a lot of other stuff less relevant for me)

No it isn't possible, see above post with link to SwiftKey forums. Major fail from SwiftKey if you ask me. Bummer. That's the one thing I don't like with SwiftKey, either...

If there is, please tell, I have been looking for that for a long time... BTW for examples of input fields, refer to the search field in settings, as everyone got that one 🙂

I think what you see is the bar that swiftkey uses for word suggestions.

Or there are more than one type of "certified", that confuses us. ...Or the guide is just not correct anymore... But it seems active, listing the id's registered. If I remember correctly it took quite a while from the Pro1 was officially accepted by Google, to it appeared as certified in the Android Market, so we just MIGHT be way to impatient Maybe it is not hours but days or weeks...

I'm pretty sure this one is persisted on a solid drive so probably not such a good indicator.

As I read it they explicitly write that we have to redo after a wipe, so NO, A wipe would not do the trick, as you would get a new id. ADD: How often do I need to register my GSF ID? Your device’s GSF ID is reset every time your device is factory reset (or when you wipe the GSF app itself) since it is stored in your data partition, so you must re-register your GSF ID every time you perform either of these actions.

I see. I have obviously no idea how long the registration process takes... Regarding root, I'd say if you didn't sideload Magisk you aren't rooted, and if you did, you are, no matter if you made actual use of it (i.e. granted root to some apps) or not. (I asked because I don't know whether root might interfere with Google Play Store honouring the certification registration...)

Again, if it makes a difference, I never have used Trebuchet. I use Nova sometimes and Launch Time sometimes (can't make up my mind which I like better because, since I rarely use my Pro1 in portrait, it really doesn't make much difference)

I can't reproduce that task-switcher bug anymore. I did a reboot earlier so I'm going to assume that fixed it... and as I was writing this I realised I did enable that Allow Home screen rotation in that Trebuchet Home app. Sure enough once you enable that option you can't reproduce the bug. Disable it and it is back. That makes it low priority bug then cause I guess most Pro1 users including myself will have this enabled.

I'm assuming Gapps should survive LOS sideload update much like it survived my OTA update @EskeRahn should know.

I don't think I'm no. I could fetch that android id after all, see above posts. Did not need root on the device, just adb root. However that GSF registration did not do anything. Maybe a wipe is needed, an also installing gapps before first boot which I did not do.

Yes, MindTheGApps should include all necessary services... Are you rooted now, or not?

Sorry for a dumb question, but when I sideload an updated LineageOS, should I also always sideload Gapps? So will LineageOS update everything or only if the same file exists?

Yes, a command syntax issue for passing arguments to a command run via adb shell directly. Perhaps more escaping is needed??? But a simple Pipe will do the job, though slightly silly. Experimented a bit with the apostrophes, the right form seems to be apostrophes around both of the two arguments to sqlite3: adb shell sqlite3 '/data/data/com.google.android.gsf/databases/gservices.db' '"select * from main where name = \"android_id\";"'

If you want it scripted, then for dos (windows), use: adb root echo sqlite3 /data/data/com.google.android.gsf/databases/gservices.db "select * from main where name = \"android_id\";"|adb shell adb unroot

Tried the same, and tried both a simple restart, and a hold-power-long deep one. No cigar. Let us give it a few hours.... And hope it works.

Could extract that android ID for GSF registration after all, just needed to do: adb root adb shell sqlite3 /data/data/com.google.android.gsf/databases/gservices.db "select * from main where name = \"android_id\";" However after registration and Google Play storage reset it is still not reported as certified. Maybe it takes a bit of time to actually register? Maybe there are other storage I need to clear? I tried clearing data for both Google Play Store and Google Play services, no joy…

Right, I don't use gestures... It's the same, though, whether I come from the home screen or from another app.

That's what I originally thought, too. I started out with unrooted LineageOS 16.1, which was already installed when I got my device (pre-owned) and generally I was fine with it. It turned out, though, it is more likely to get all or most of those apps running with a rooted device than with an unrooted one. More and more apps check for modifications which deviate from an unchanged phone with stock and complain even if it the device running LineageOS is not rooted. As soon as you have Magisk properly set up with MagiskHide and passing SafetyNet, at this point (possibly impending changes in Googl

I see, I was hoping it would be easier if you have no root access. If having root access is in fact a requirement I don't mind really, other than the fact that it seems to be taking quite a few steps to get there.

Full update I guess, the package was over 700MB. It was not exactly speedy to apply but since it does its stuff in the background it a no-brainer.

Yup that's what that bug I've opened is about. Hope they can get it fixed. I guess it would help if you post on GitLab too.

Are they still sending the full images for OTA updates, or are they doing incremental upgrades. Last I tried the full image OTA it was terribly slow. Much faster with manual download, and a batch-file - and it is easier if you need to reflash. ;)

I'm pretty sure you are stuck on stock, if you want that without root and tricks. 😢

Nope, not ground related if that's what you're referring to. All my tests were done away from a charger, so 100% just the phone itself.

OK so basically the initial "massaging" thing I was doing on the corner initially. Thing is my problem actually started with "dancing"... meaning if I tap anything on that strip, the phone would go crazy for a few seconds tapping random things above AND below that strip. It was to the point I couldn't unlock my phone after a reboot (or that dreaded "Too many attempts" message when I haven't even touched my phone once). That's when I found out when the phone works fine if the screen is not attached. I took it apart and applied some electrical tape at random locations to experiment, an

Okay... never mind. I switched VoLTE back on just now and it works fine. Bloody gremlins. 😄

Oh, and Fidor Bank just answered my support request, apologized for not supporting my phone and changed the account from pushTAN via app back to mTAN via SMS, even though this isn't officially available anymore. So while this isn't the best of all possible solutions and will only be supported, as they say, for a limited time, for the time being I can now do everything with the Pro1! And the Moto Z3 Play can finally go back into the drawer, as soon as my employer's fine tech support people will have bound my Pro1 to that VPN token account... 🙂

Don´t see how that would impact either, but I did have some strange IT-issues lately, must be my aura. Suddenly all file associations on my WIN10 laptop are gone, the network config file on Debian server became corrupt, my router running DD-wrt had a file system crash, and my Cisco switch is not responding to SSH any longer. And all this whitin 3 weeks time... start feeling really scary anyway, If I map scancode 468 to keycode 133 it should work?

So far it fails saying: Error: unable to open database "/data/data/com.google.android.gsf/databases/gservices.db": unable to open database file