-
Content Count
5,756 -
Joined
-
Last visited
-
Days Won
338
Everything posted by EskeRahn
-
(Just downloaded, will flash within minutes 😍) It did not install with the previous AICP-q boot.img, but it did install with the latest LineageOS 18.1 .img open_gapps-arm64-11.0-pico-20210712.zip installed as well. So now i'm back on AICP after being 'unfaithfu'l using LineageOS 18.1 for some weeks on the 'final sample' too. Lovely. 😁 Battery saver "Battery may run out soon ....blah blah .... 40%" I would say that kicks in a little early.... But it was when it still installed apps in the background, so the projected remaining time was low as could be expected. I usually turn
-
Thanks @tdm, links added here 😁
-
How to customize the keyboard layout on LineageOS 18.1?
EskeRahn replied to ivoanjo's topic in Pro1 - Thoughts & questions
Thanks. But if it ONLY works with German, this seams to break the whole original idea of letting the qwertz/qwerty switch select all the necessary remapping to get a standard layout so ANY available android standard layout could be selected, fitting the users language. ADD: Obviously if I select a qwerty based language on the qwertz keyboard with the qwertz switch, I EXPECT the letter between T and U to send a Y, and similar others will not match the print. (and obviously similar issues the other way round) No better or worse than if I selected to write with another language on a phy -
Ah I see. Please note that their support mail system (zendesk?) works in a way collecting mails in the queue, so sending in a new mail pulls back the previously mail to the end of the queue.
-
I currently have two Pro1s on Lineage, and am unable to reproduce the issue, no matter how much I let it charge or discharge, and no matter if it is a slow or quick charger. One of them recently factory reset (had AICP on it before). So unless there are unknown hardware sub-variants, it must be something different we got installed that somehow triggers (or remedies) the issue.The only explicitly battery-related I got installed is GSAM battery manager, and 3C all-in-one Toolbox. Both just monitoring the usage.
-
Sad to hear. But just to be sure, are you on stock Android or LineageOS? (Some are having charging-issues on Lineage)
-
As I read what @3zet writes, the point is if you have some software that stops charging when full (to prolong battery life when constantly connected). Charging ought to be accepted again once below a certain threshold.
-
LineageOS 18.1 Official Release for Pro1
EskeRahn replied to Wheeljack's topic in Pro1 - Thoughts & questions
(lineage-18.1-20210913-nightly-pro1-signed.zip on September 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. -
Note that some navigation apps tend to be smart, so if you move at some speed along a road it will snap you to the side of the road it expect you are. (so this could muddle things further)
-
Sorry. I was not trying to say that the GPS on the Pro1 is bad. What I meant to say was that it is surprisingly good on the Titan.
-
Well apart from a good idea, that IS also good news, as this means it is not too deep down the sound is filtered, so that increase the chance of a fix - though I certainly will not hold my breath for it. I would suggest using a dedicated app you do not normally use for video and set it to the lowest possible video-resolution, e.g. 320x200 if offered, as this would mean a less huge intermediate file for long recordings.
-
Indeed, and it sounds similar to what you get using it for calls hands free. If you talk loud and clear as you would at a (physical) meeting, it works fine. But if you talk in a normal voice, the other end complains that they can not hear what you are saying.... It has -unfortunatly- been a known issue since 'day 1' on stock, and I have long given up hoping for a fix and use it with a headset, as I seldom do voice calls. I fear this 'filter' is deep down, either hardware or software in the driver, as I assume they would have fixed it quickly if it was in software they could ac
-
I bought an old house some ten years ago, and found out that part of the insulation used in walls and ceiling was a sheet of metal foil, so to a large extent I live in a Faraday's cage. Thus I can not use my WiFi in the garden - no big deal for me, but a big surprise for many guests. So it was no surprise to me that none of my phones have been able to get an indoor gps fix. (Except when standing under the passage to the attic) The big surprise is that the Titan gets a fix indoor, and with 3-4m accuracy!! (2m under the passage)
-
I got one too. Have not found the time to make a review of it. I'm not a fan of keyboards in the wrong direction, with REALLY few keys though - but to each their own. Though (almost) any real keyboard phone is worth supporting, as it is still better than touch only. But I must accept that I'm simply too old to use a device with that size of screen, despite it being more pocketable, for other than occasional usage. I really struggle with the small print. And yes yes not illustrated by the picture below, that was just a quick one for the content. The hardware feels sturdy and g
-
Yes, I guess it could be argued that it is a bug in recovery that it does not correctly reflect that installing an image might have changed the active slot, before a boot has been made.
-
I believe the last remark is not quite accurate. It is the flashing&install of the main image that also changes the active slot. Reboot to Recovery just boots to that. If you do not want gapps/magisk/... a reboot from the main menu will also boot into slot B
-
Sad to hear you broke the screen. On the call quality, a headset might help you. I use a wired one, and that works fine. (though obviously just a workaround not a fix)
-
Recent changes in LOS 18.1 regarding apps and battery optimisation?
EskeRahn replied to Rob. S.'s topic in General Discussion
Not new at all... Also there on stock Android 9. -
LineageOS 18.1 Official Release for Pro1
EskeRahn replied to Wheeljack's topic in Pro1 - Thoughts & questions
(lineage-18.1-20210906-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. -
Can't believe it's finally happened. (Cracked Screen)
EskeRahn replied to MickH's topic in General Discussion
They do look suspicious, indeed. -
Can't believe it's finally happened. (Cracked Screen)
EskeRahn replied to MickH's topic in General Discussion
PPS looking inside the fastboot_all.bat inside the .7z file, Someone with more understanding of these things might be able to pinpoint the specific file that does the trick: fastboot flash boot_a boot.img fastboot flash boot_b boot.img fastboot flash dtbo_a dtbo.img fastboot flash dtbo_b dtbo.img rem fastboot flash system_a system.img rem fastboot flash system_b system.img rem fastboot flash vendor_a vendor.img rem fastboot flash vendor_b vendor.img fastboot flash vbmeta_a vbmeta.img fastboot flash vbmeta_b vbmeta.img fastboot flash userdata.img fastboot flash abl_a abl.elf fastboot flash -
The clipping seems like a firmware/software issue, so most likely not much point in sending it in. Is it related to the two sources? Someone are talking in the background and the music is playing. Could it be some attempted noise reduction that are teasing? It sounds a bit like when e.g. Skyping with someone in a meeting room, and the equipment struggles with recording what is noise and what is signal.
-
Can't believe it's finally happened. (Cracked Screen)
EskeRahn replied to MickH's topic in General Discussion
PS on how to flash the stock android see this thread