daniel.schaaaf
Members-
Content Count
125 -
Joined
-
Last visited
-
Days Won
6
Everything posted by daniel.schaaaf
-
PRO1, LineageOS 17.1 Official Builds: Discussion
daniel.schaaaf replied to EskeRahn's topic in General Discussion
Regular audio for sure. I haven't had the chance to try call audio yet. It's still broken in 20210329, only for me apparently, which makes me think that my phone is borked. The only big thing I did the last few days was disassembling and reassembling the phone. Is there an "external" antenna in the case, to which the Bluetooth chip connects? Or is said antenna on the mainboard? The headphones connect to the phone, and I was able to re-pair them. They are actually shown as "active" when I chose the audio stream. One other thing I notices is that I also cannot control the volume of int -
PRO1, LineageOS 17.1 Official Builds: Discussion
daniel.schaaaf replied to EskeRahn's topic in General Discussion
Anyone else with bluetooth trouble on 20210322? My headphones connect alright, but the audio is routed to the phone speaker. -
Utterly disappointed
daniel.schaaaf replied to daniel.schaaaf's topic in Pro1 - Thoughts & questions
Changing the checksum of the system partition only breaks OTAs when they actually patch the partition itself, and not individual files within the partition. I tried to find out how LineageOS updates work, but I did not manage to get any useful information. I remember original Motorola OTAs failing to install on Moto Z phones that had a modified system partition. When it comes to safety, there is no difference between me remounting /system, or an app doing so. If FinQWERTY does its job without root, then it is safe to use and won't/can't modify /system. Nope. You make it sou -
Utterly disappointed
daniel.schaaaf replied to daniel.schaaaf's topic in Pro1 - Thoughts & questions
Don't you have to remount \system rw for that? I thought that would break the (OTA) update process because even just remounting \system will change the partitions checksum. -
Utterly disappointed
daniel.schaaaf replied to daniel.schaaaf's topic in Pro1 - Thoughts & questions
Do people complain about an echo? That's the feedback I get when I use the speaker and my Pro1 is lying on a flat surface. A simple fix would be to use the upper speaker, instead of the lower speaker, which sits next to the microphone. Instead, I feel reminded of how Apple treats their customers: You are holding it wrong! ๐ -
Utterly disappointed
daniel.schaaaf replied to daniel.schaaaf's topic in Pro1 - Thoughts & questions
I am missing an app that provides keyboard customisation (re-defining keys/characters), predictions, possibly a bar with special characters for quick multilanguage use, a dead key to quickly type foreign characters or letters with accents, sticky modifier keys or the possibility to configure whether modifiers keys should be sticky or not, ... There are apps like FinQWERTY that provide some of the missing functionality. But they are (very) difficult to use and I would have to combine several apps to get what I want. F(x)tec asked if we wanted a hardware keyboard, we threw money at them, an -
Utterly disappointed
daniel.schaaaf replied to daniel.schaaaf's topic in Pro1 - Thoughts & questions
Without knowing how much or little F(x)tec actually supports the community, I personally do not see any active support. In the LineageOS thread, bugs were reported by users and the maintainer of the LineageOS port found out themselves what is broken and how to fix it. The number of serious bugs present in LineageOS suggest that there is no active support of the community by F(x)tec at all. The LineageOS port, aka the community, struggles with the same bugs as the official Pro1 Android. I did pay a lot of money for a device that I knew had a bumpy road ahead. But seeing that F(x)tec doesn' -
Utterly disappointed
daniel.schaaaf replied to daniel.schaaaf's topic in Pro1 - Thoughts & questions
This is getting seriously off-topic now. Please, this thread is about disappointment and anger! ๐ -
Utterly disappointed
daniel.schaaaf replied to daniel.schaaaf's topic in Pro1 - Thoughts & questions
I get your point. Unfortunately, hopelessness has the opposite effect on me. I can't just live with it, and my blood pressure only increases ... until, in this case, I switch to another phone. The thing that bothers me most is that I feel that we communicate all of the Pro1's issues. Sure, we only do so here in the forum. But ... is it too much to ask for anyone from F(x)tec or any of their contractors to take a peek at the forum every now and then ... and help us? They get bug reports delivered on a silver plate. Yet, they do nothing. Ooooh, time to think about that blood pressure of min -
Utterly disappointed
daniel.schaaaf replied to daniel.schaaaf's topic in Pro1 - Thoughts & questions
That may be, but as a customer, I couldn't care less. Sorry for those harsh words, they are not directed at you. It has been a year now, and I hate my Pro1. The only reason I still use it is that "moving" to another phone is a time consuming and cumbersome process. I felt betrayed by Motorola, when they screwed up their mods and dropped the whole thing. I feel even more betrayed by F(x)tec, because I expected them to be closer to the community and care more about us customers. F(x)tec makes me feel naive and stupid for having trusted them. I am glad to hear that you are having a positive -
After almost a year with my Pro1, all I am left with is utter disappointment and a reluctance to use this "phone". Yes, I am actually thinking about going back to my Moto Z Play. The hardware is alright, and the keyboard is fine. However, the software is lacking, non-existent or buggy at best. F(x)tec has done nothing to address any of the known software issues. Instead, they released a "new" piece of hardware, the Po1-X. If anyone from F(x)tec is reading this: Get your sh*t together and fix the software before anything else! Living abroad and communicating in three different
-
PRO1, LineageOS 17.1 Official Builds: Discussion
daniel.schaaaf replied to EskeRahn's topic in General Discussion
Hm, has anything happened to the way the fingerprint sensor is controlled? I remember the issue with the sensor not responding whith the screen off having been fixed a while ago. Now (LOS 17.1-20210201) the sensor seems to be unresponsive again. More often than not, I have to push the power button to switch on the screen (wake up the phone), in order for the fingerprint sensor to register my finger. This is happening with the phone resting on a table most of the time. There's no accidentally triggering the sensor in my trousers pockets. I only touch the phone and the sensor to actually unlock -
Spontaneous reboots - discssion on possible causes
daniel.schaaaf replied to VaZso's topic in Pro1 - Thoughts & questions
Other than switching to LineageOS (17.1), probably not. The software f(x)tec provides is disappointing ... in so many ways. Unfortunately, some bugs got carried over to LOS, probably because f(x)tec doesn't provide enough information about drivers and hardware ๐ -
PRO1, LineageOS 17.1 Official Builds: Discussion
daniel.schaaaf replied to EskeRahn's topic in General Discussion
It's a mystery to me how this has not been fixed a long time ago. I have my notification and phone volumes on the lowest setting and it is still too loud. Also, still struggling with speaker mode using the lower loudspeaker ... which is right next to the microphone and causes echo and feedback when the phone is lying flat on any surface. Btw., how does the LOS update process handle changes on /system? Can /system be mounted rw and files changed, or will this cause an update to fail? Afaik, the updates are not incremental ... but checksum errors or other mechanisms might fail ... -
PRO1, LineageOS 16.0 Official Builds: Discussion
daniel.schaaaf replied to tdm's topic in General Discussion
A short update on my missing apps: Restoring the apks with oandbackup made them function again, meaning that the restored apps had access to the data that was still there. While this is making things much better for me, I ask myself why these restored apps have the permission to access their old data. Apparently, the re-installed apks (with oandbackup) got their old UID assigned and SELinux seems to be happy too. Really weird ... Edit: I love the dangerous life ... so, I updated my LOS17.1 to the newest nightly just now, and I only "lost" one app (the F-droid store). -
PRO1, LineageOS 17.1 Official Builds: Discussion
daniel.schaaaf replied to EskeRahn's topic in General Discussion
LOS 17 is working well so far. Should we report bugs here or on https://gitlab.com? Just as with LOS 16 and the original fxtec Android, the in call volume is messed up. Right now, the volume can only be adjusted from "loud" to "extremely loud". -
PRO1, LineageOS 16.0 Official Builds: Discussion
daniel.schaaaf replied to tdm's topic in General Discussion
The SD card is still recognised, and there are no apps installed on it. All my apps were installed to \data. The deleted apps were also not consistently using the SD card either. Some apps only stored data in \data\data, some used \sdcard\Android\data, some had obbs on the SD card. Found something: The data folders all were from the same date. Now I have to find out if I restored these apps from backups made with "oandbackup" or "AppWererabbit". One question still remains: Why were the apps (their folders in \data\app) deleted (and their data in \data\data retained). -
PRO1, LineageOS 16.0 Official Builds: Discussion
daniel.schaaaf replied to tdm's topic in General Discussion
Thanks for your quick reply tdm ๐ I did an OTA update. Unfortunately there is no pattern. Some apps were installed from the SD card, some from F-droid, and some from the Play store. Looks like I have something to do for the weekend ... I am a hoarder and have ... had about 600 apps (mostly games I never play) installed. Now I am down to 350 ๐ There are still 21 GB free on the internal memory. That excludes Android doing weird stuff due to a lack of free space. Well, I seem to be the only one to have missed apps. Then it's not LineageOS or even Pro1 related ... -
PRO1, LineageOS 16.0 Official Builds: Discussion
daniel.schaaaf replied to tdm's topic in General Discussion
@tdm Do you know if LineageOS creates a log file when updating? I updated to 10.0-20201026 (OTA), and now a lot of my apps are missing. The corresponding directories in \data\app are gone, even though the app data in \data\data is still there. -
PRO1, LineageOS 16.0 Official Builds: Discussion
daniel.schaaaf replied to tdm's topic in General Discussion
Is there a way to define a key on the hardware keyboard as a dead key? I would so much like to type รค, รฅ, and the like by typing e.g. "dead key + a = รค" or "dead key + p =รฅ". I couldn't figure out how to do this with Keyboard Mapper. -
May I ask why you don't want Magisk on your phone? In my opinion, Magisk is as important a "tool" as the Xposed framework. Being able to modify /system without actually touching the system partition is ... magic ๐ Magisk also brought Xposed to Pie and Oreo with Riru. OK, it gets fishy and suspicious here ... despite that, I would not touch a phone I could not run Magisk and Xposed modules on ๐
-
Poor call audio quality on Pro1?
daniel.schaaaf replied to Slion's topic in Pro1 - Thoughts & questions
Yes, the signal is low i my apartment, which increases the transmission power of the modem. I never had modem interference as loud as on the Pro1 though. -
Definitively! I am one of those rare people who can't get enough options and settings to screw with Anyway, we have advanced settings and developer options already in AOSP and LOS, and LOS offers more settings than AOSP. I don't think LOS would agree to add even more settings
-
Poor call audio quality on Pro1?
daniel.schaaaf replied to Slion's topic in Pro1 - Thoughts & questions
Distortions is probably the wrong word. Better words are crackling noise or interference. I never asked the person on the other end of the call about the call quality, since I only make "ordinary" phone calls to/with people i don't know . The interference can be so disturbing that I barely understand the other person, but since they never complained, I guess they don't hear it. I know this kind of interference from audio amplifiers and am sure this is what happens in the Pro1. It is only audible on the Pro1 loudspeaker. Lowering the volume is not possible unfortunately because the ca -
Well, one argument I get to hear way too often is "Too many options/settings confuse most users!". It might be as simple as that. In addition, even settings that exist and work on LOS or AOSP might not be easily accessible because it would be too much work to add them to the settings UI (for just a few power users). Having said that, I don't know why the AICP does not add all these settings to LOS and maybe hide them in an "advanced" tab. Apparently, AICP also contains additional software, not just easy access to settings through the UI.