Noob

Thanks @tdm for this build, this is awesome. My only question is, in the absense of OTA, how feasible is it to create updated builds? And I presume there'd be no data loss on upgrade, like updating LOS? I noticed that last week when I did my first LOS build for my Droid 4, Android security patch level is "5 December 2019".

/wave Bye bye Pro1, see you again (hopefully) soon. So I sold my Pro1 to Kashif. It's an awesome phone, but after spending days trying to deGoogle it and finding LineageOS not quite ready for prime time I thought I may as well sell it/trade orders given his his eagerness and the fact me made me an offer I "couldn't refuse" As bad as my Droid4 is (currently turns off at random) I can live with it a bit longer. @kashif I'm glad you're enjoying it.

Maybe not. I couldn't tell which version it's at, I did the OTA update last night but maybe there are more updates available after that one. I tried again today and see there's one relating to Google SafetyNet. EDIT: So it seems the updates are installed sequentially, rather than one big superceding one. I installed the SafetyNet update, then a further one (10 Dec) and retested. Still the same behaviour re VoLTE. Two providers, AldiMobile (Telstra MVNO) and Optus. Both seemed to support LTE/4G. LTE does seem to be supported, but just for data. When phone call came through or was made, the phone dropped down to UMTS voice and HDPA data (according to that debug screen). One of the network providers said they support VoLTE but I'm not sure whether they really know. The other I don't know. But I'm guessing there's some extra internal config that needs to be added to support it for providers (isn't that why VoLTE support is such a pain? I keep reading complaints about it, not just for the Pro1)

I'm not sure if anyone else with a Pro1 is in Australia, but you'll need the OTA update to get phone calls working. On the original stock firmware everything worked but outgoing calls which would not dial out and incoming calls would be engaged or straight to voicemail. Same for LineageOS, but currently no update to fix it. There is one other thing I noticed; when I dial *#*#4636#*#* I see that "VoLTE provisioned" is greyed out and disabled. Hopefully that can be turned on in future.

Really? That would be pretty cool. Yes I've definitely appreciated some of the cool features on my LOS 14.1 Droid 4, and they look even better on the Pro1 (privacy guard, ADB over network, extended reboot menu, 5x5 pattern grid, night mode, and the new transfer speed status bar indicator is a nice touch), but running on nightlies has been a bumpy ride over the years; somewhere along the line ADB over USB stopped working, WiFi and Bluetooth can no longer co-exist, the phone reboots when I get incoming calls from contacts with custom ringtones, etc. It was a tremendous volunteer effort that extended the life of my phone by about 5 years (and about as many Android versions) and I'm grateful for it, but I really want my Pro1 to be more stable and I thought staying stock would be a way to do that, even if I had to give up on the nice features. Though as @silversolver pointed out there's the question of what to do when updates come along, especially if the FOTA function is removed. Is it practically impossible to remove GMS after the ROM is built, or did I just mess it up? Done 👍 I also raised an issue for the keyboard backlight. You're right, that worked and was painless. Thank you, if it's that simple no need to bake it in. Is it my imagination, or did older versions of LOS enable root if you pressed the LineageOS version a few times, similar to how "Developer Mode" is enabled? Good to know. If the hardware and software are close to reference and the manufacturer is supportive, I'm hoping that translates into a more stable ROM and I might just stick with it. Though I am wary of my update path again being on the shoulders of a single individual who has to balance maintaining it with other priorities (though maybe I'm misunderstanding how much of the ROM is custom for this phone, and how much is the wider LOS software that everyone works on).

I had to give up un-Googling the stock firmware as I couldn't remove GMS without the phone locking up on boot, so I gave this a spin. Thank you for your efforts on this, and for the detailed explanations as you go :) I put the SIM in and phone calls don't sem to work, either incoming and outgoing (SMS works though). Not sure if this is expected at this stage or if I should file a bug report. Another weird issue; when I changed the pattern lock to 5x5 grid, the lock screen grid was still 3x3 so I couldn't unlock it. It fixed itself on reboot though. A few questions: - at this stage with no suitable TWRP I couldn't install the lineage su extra. Can this be built into the ROM? - how do you rate the difficulty in developing LineageOS on this device compared to other manufacturers? I don't know what support they're offering beyond hardware, I assume source as well or are you still working with closed binaries?

Would it be possible to get an updated firmware with the November OTA update?

I put mine on really badly, but still all but about 3 or 4 air bubbles disappeared over a few days. But as soon as I did it I was pretty annoyed with myself and bought some replacements straight away. I found these specifically for the Pro1, if anyone's interested (they also have an eBay store). If only I had waited a few days; they just emailed me with 15% for Black Friday (if anyone's interested, use the code BLACK15). That page also has a very detailed instruction video (if only I saw it beforehand there wouldn't be dust particles trapped inside). As far as using Windex or harsh cleaners, I thought that was bad for any anti-glare coating on the screen? Or is that just for old LCD screens?

Version numbers don't follow decimal number rules. They aren't a decimal number, as others have mentioned, but major.minor, or in the case of semantic versioning, major.minor.patch. Or really whatever a developer feels like, which hopefully maps to a coherent strategy.

Overreactions like this don't really help the discussion. I posted this late last night, and on reflection I wondered if I should have quietly emailed support instead. In the end I still feel justified raising it in the forum, but let's be sensible. I'm not surprised @Waxberry took offense to this. Please don't get me wrong; I don't think for a second that F(x)tec is doing something untoward or can't be trusted. I totally support this company's products and everyone's hard work. @Waxberry your passion for KB phones is very evident from your posts on TMO and the old IGG comments, and I appreciate you're not a "PR guy", but the above response is a bit tone-deaf in my opinion. I don't know the reason why AdUps was chosen instead of Google, but I'm guessing there were commercial necessities that dictated this choice and I'm sympathetic. But as others have pointed out, you can't say "their record is reliable" when it's clearly not. Yeah it should be above board, but this is something outside of your control, it's really up to AdUps to do the right thing. And while I appreciate that there are contractual obligations, GDPR, Google certification, etc, that doesn't stop them from breaching those things and grabbing data they shouldn't if they have the technical means. Given this is a root application that can change its behaviour in future it's matter of trust in the end, and I don't trust a company that has been caught out once, let alone twice (again, I'm not referring to f(x)tec here). Certainly not with a device that has so much of my life on it. I understand this is, to some extent, subjective, and I know I'm in the minority. I'm sure many (most?) people are comfortable with a company that has "reformed" and no longer steals your data, else no one would be on Facebook. I'm not going to judge f(x)tec for choosing AdUps for OTA because I don't know the factors in the decision and even though I would have thought Google was a better option I trust you had compelling reasons. In my case though, choosing Google for OTA is a moot point given I was trying to scrub GApps from my phone anyway. So, back to my opening question, will there be another way to update apart from OTA?

I just noticed the following files in "/system" directory: /system/app/AdupsPrivacyPolicy /system/app/AdupsPrivacyPolicy/AdupsPrivacyPolicy.apk /system/app/AdupsPrivacyPolicy/oat /system/app/AdupsPrivacyPolicy/oat/arm64 /system/app/AdupsPrivacyPolicy/oat/arm64/AdupsPrivacyPolicy.odex /system/app/AdupsPrivacyPolicy/oat/arm64/AdupsPrivacyPolicy.vdex From articles like this it seems like this is for OTA updates but the company's app has a bad reputation for being spyware, sending personal data to China. From the article I linked I'm guessing this is the reason why it's being used instead of Google's service: If remove this app, I presume I no longer get OTA updates. Will it be available in other ways? EDIT: I should add that the most recent articles on this were from about 2 years old. Not sure what the current state of this is, but I don't want to take any chances.

Regarding the software, there is one thing that doesn't seem right to me: there doesn't seem to be a way to swipe up from the home screen to see your app drawer. Instead, it shows you the running apps, and you swipe up again to get the app drawer. Maybe this is standard Android now, but it feels clunky to me. Also, the size is growing on me. I'd still prefer a bit smaller, but it's just about thin enough to be more usuable than the Moto Z with one hand 👍

If they reshaped it to be wide and short rather than tall, I reckon it would fit in that flap. I didn't realise this was an FCC requirement, seems strange to me. I'm guessing it has to be somewhere on the phone, but surely it doesn't have to be that clearly visible? If so, why did previous phones have the stickers inside under the battery? Do iPhones and Samsungs in the US have this? EDIT: I missed your comment about the support plate. I suppose that's true. LineageOS has some great features that I miss in stock Android but I'm a bit sick of the flakiness from the Droid 4 (e.g. at some point wifi and bluetooth stopped working together and my phone will immediately reset if I turn off tethering if a client is connected, or a contact with a custom ringtone configured calls me). I'm also don't agree with their view on microG/signature spoofing but at least there's a way to get that working. I might try it out anyway (hopefully it'll be more stable in this case when the effort is supported by the phone manufacturer) but for now I'd like a more "standard" experience. Speaking of GApps, as soon as I set up WiFi on this thing f**king Google Play Services decided to download hundreds of MBs automatically updating its apps. No prompts, no way to stop it, even without a Google account configured. 🤬 The strange thing is even doing a factory reset/fastboot flash didn't seem to "totally" reset everything; the app usage tracking, settings, even the time was still set as before. 😕

Not software features, but 2 small things that bug me about the phone: - That IMEI sticker on the back. I wish it was somewhere less easily visible, like the flap that shows the CE logo when the keyboard is opened (if you don't know why this isn't so nice read the discussion in this thread - The phone is a bit slippery and the back surface, while beautiful, scuffs way to easily I haven't had a chance properly use the phone; now that I've installed Magisk (thanks @Linkandzelda) I'll try to remove all the Google apps and it'll be ready for action.

Yeah that makes sense. Now that I think about it, they did originally refer to it as the Q device. 🙂