tdm
-
Content Count
801 -
Joined
-
Last visited
-
Days Won
84
Posts posted by tdm
-
-
7 minutes ago, _DW_ said:
Just swapped to this build today from ubuntu touch all went fine. (Had to install Gapps twice for some reason but went on in the end!) Also play store crashed until it did an update (Am sure I saw this mentioned somewhere else)
I have noticed it is sluggish compared to ubuntu touch I mean animation wise. Problem is I can't remember what stock was like now :S I guess this could be power saving features?
Perhaps it is the animation speed? Go into developer settings and set the animation scales to 0.5x. That should feel faster.
-
11 minutes ago, Brettjames22 said:
I am very tempted to drop this piece of s--t phone on the railroad tracks and see what happens when a train hits it unless anyone has any fixes for the above?
The phone works perfectly fine on reasonable GSM carriers. Verizon is neither reasonable nor GSM.
Your fix is to switch to another carrier. T-Mobile, AT&T, or any of their MVNOs work perfectly fine. I'm on PureTalk which is an AT&T MVNO. Paying $80/mo for four lines.
Or, if you insist on being abused by Verizon, I'm sure someone would be happy to buy the phone from you.
-
2
-
1
-
-
39 minutes ago, SteffenWi said:
So, I just finished setting up Lineage on my phone and then wanted to connect it to my PC so I could copy some files over from the previous phone...and now the Pro1 isn't recognizing the USB connection (in USB settings everything is greyed out) and my PC isn't seeing the device either (nothing in dmesg, nothing in lsusb).The phone is charging though. Connecting my old phone to the same USB cable works (phone is recognized). I'm not sure what to do now. Could the USB port on the Pro1 be broken already?Nevermind, phone is also not recognized in bootloader nor recovery mode. This is great...
Perhaps your PC is having issues with USB?
Lineage supports ADB over network. I frequently use this instead of USB because it is super convenient.
Enable developer settings (tap on build number 7 times), then go into developer settings and enable ADB over network. The adb address will be shown. On your PC, run "adb connect <address>".
-
3
-
-
4 hours ago, acrux said:
Is there a particular reason for that? Moving Gapps and other addons?
My Nexus 6 with no Gapps usually performs an LineageOS OTA update in 2-3 minutes.
It is because A/B. See this link:
Incremental OTAs are much faster, but don't work with addons. I would like to fix that at some point.
-
4
-
-
33 minutes ago, Jordi said:
Thanks for your answer.
In fact I see now, in the recovery screen, that I'm in slot a, with lineageOS Nightly.
Knowing this, your answer above is still valid? (and I came from the test version 15, not the 22)
If I were you, I would install test22 first, before the nightly. It is what others have done, so it is known to be working.
-
2
-
-
34 minutes ago, dicer said:
Does this contain updated (modem) firmware partitions? I very early on switched from stock to Lineage so I didn`t get any OTAs for stock. I assume they did contain some updates to the firmware for modem, bluetooth etc?
So does it make sense to flash this to update those partitions?
Also see
Yes it is the complete factory package with the modem and everything else, just as you would get from the OTA.
-
1
-
-
16 minutes ago, Jordi said:
I tried to install the new official version like I did to install the test versions (and I also deleted /data/system/packages.xml) but I had an error during the process. I rebooted and now I'm stuck with a system with very limited apps but with some of my parameters, like my background screen. I guess this is the recovery.
Question : Can I save my phone? (and keep apps and parameters) 😔 If yes, how?
I wrote this message still in the former thread as I'm not yet with the official version.
Just redo the test22 install, following the instructions as if it were the first time. That is, flash the boot image, boot into recovery, flash test22, reboot recovery, flash gapps, reboot.
If you booted into Android without gapps, various Google apps get unhappy and may need to be removed and reinstalled (like hangouts, etc.) But your data should still be there.
-
1
-
1
-
-
2 minutes ago, SteffenWi said:
sorry, I didn't type the 'boot' part in there. Before we had to specifically select a boot slot (for example boot_a) but taking your later response to another issue I had we don't have to worry about boot_a/boot_b anymore now that this is an official lineage image. Thanks.
To be clear, fastboot talks to the bootloader and that is never changed by Lineage (or any custom OS). I merely specified the suffix _a/_b to make the user aware of exactly what is happening. You have always been able to fastboot flash any partition without the suffix. It just writes to the active one. But you may not know which one is active, so I considered this a bit dangerous.
-
2
-
2
-
-
33 minutes ago, Hook said:
So, forgive my noobness, but if I am updating (preserving data) from Test 22, can I just adb sideload the new nightly, then use the advanced menu on the phone to reboot into recovery (which should be the new recovery image) and carry on with suaddon and Gaaps, or do I need to fastboot flash the new recovery first?
The former. Basically update just like you always have with my test builds, but using the official zip. When you reboot into recovery to install gapps/su, you will be in the official recovery. You can tell because should see the version string show nightly instead of unofficial and adb shell will be unauthorized. And when you flash gapps, it will complain about the signature (but it will let you proceed anyway). After gapps installation, reboot and you should be running the official build without issues.
This is all theory .. I haven't actually done it, as I typically don't run official builds. But @EskeRahn and others indicate it works.
-
2
-
-
I have created an official LineageOS discussion topic:
https://community.fxtec.com/topic/3037-lineageos-160-official-builds-discussion/
This thread should die down and the new one should take over.
-
4
-
1
-
-
19 minutes ago, SteffenWi said:
@tdm That is the thing: I lack the knowledge to know if things just changed because it is now a lineage image or if the wiki is wrong. There are just a lot of differences between what was on your site and what it says on the lineage site.
Oh, I see. I honestly never really look a the Lineage wiki. I just assume that it is clear and correct because it is used by so many people. Again, if you or anyone else finds issues that need to be addressed, both myself and @npjohnson can assist in getting the text fixed and/or updated.
-
I am pleased to announce that the Pro1 has received official support in LineageOS 16.0.
You can find the builds and installation instructions on the official LineageOS Downloads page.
Please note that LineageOS does not include the proprietary Google apps (aka. "gapps", Play Store, etc.), nor a "su" binary. These are "extras" or "add-ons". You may use any appropriate gapps package for Android Pie. I personally recommend MindTheGapps which can be found here. LineageOS maintains an official su add-on and a couple other extras here. Note the Pro1 is arm64 and be sure to select the appropriate version (Android Pie 9.0, LineageOS 16.0).
Many thanks to those who helped with this project, including @npjohnson and @Sean McCreary. And of course, a huge thanks to Ethan Chen (intervigil) who isn't here but gave the code some very nice polish at the last minute.
-
21
-
-
Guys, I appreciate the critique of the wiki. But please do note that virtually everything except the device specifications are templates that are linked -- I did not write it. Here is the actual code for the Pro1 device page:
https://github.com/LineageOS/lineage_wiki/blob/master/_data/devices/pro1.yml
Notice it says "install_method: fastboot_nexus". That means the recovery install instructions come from here:Also note it says "is_ab_device: true", so the wiki will follow that path when generating the page.
If you would like to contribute to the Lineage wiki, I'm sure they would appreciate the help.
-
17 minutes ago, Maplesteel said:
For clarity, I meant the newly appeared Lineage OS nightly builds located here.
Are those the same builds as your ongoing test builds, @tdm ? Do they connect to your, or LineageOS OTAs?
The LineageOS nighly builds on lineageos.org are the "official" Lineage builds. I have imported the code for test22 to the Lineage github, so they will be functionally equivalent to that (at least to start, we will continue development there). There are only a couple differences for official Lineage builds:
- They are signed with a "real" key, not a "test" key. This is more secure and will make the Trust warning go away.
- I have a couple changes to my code locally. Nothing you should really notice except for a small anti-spam hosts file.
- Signature checking and adb auth is disabled in my recovery.
And yes, if you install the official Lineage build, you will get official Lineage OTAs. These should be done weekly, I believe, regardless of whether anything actually changes. Conversely, if you install my build, you will get my OTAs. I will only publish an OTA when something changes.
-
2
-
1 hour ago, Maplesteel said:
If we install a nightly build, are we eligible for OTA updates?
Yes. Just be prepared for the OTA install to take nearly an hour.
-
1
-
-
3 hours ago, EskeRahn said:
Thanks.
Is there an 'officially signed' version of the gapps package we should use, or should we just ignore the warning?
Just ignore the warning.
-
1
-
-
29 minutes ago, EskeRahn said:
Thanks. I get this after flashing trying to run the usual "adb reboot recovery" though:
error: device unauthorized. This adb server's $ADB_VENDOR_KEYS is not set Try 'adb kill-server' if that seems wrong.
The suggested kill server does not help. (I can manually reboot to recovery from the menu though)
It then complains about the signature of the gapps-package, but I am allowed to overwrite that.
(Same for adb reboot)
But overall it installed gracefully and preserved my user data. 🙂
This is expected. The official lineage recovery has stricter security. I have a patch in my build that disables adb auth in recovery.
-
4
-
-
49 minutes ago, marmistrz said:
Ok, I see what's the reason for the unexpected behavior of alt/fn+alt. fn is handled using these arrays: https://github.com/LineageOS/android_kernel_fxtec_msm8998/blob/2120e09d09b3a94c4de9395523a587d9909224d4/drivers/input/keyboard/qx1000.c#L257-L335
It appears that KP_LEFTALT is handled in this part of the file: https://github.com/LineageOS/android_kernel_fxtec_msm8998/blob/2120e09d09b3a94c4de9395523a587d9909224d4/drivers/input/keyboard/qx1000.c#L649-L654 and no check is made for the state of the fn key.
What kind of key event is emitted on stock for fn+alt? (I can't find the kernel sources for stock)
@tdmis there any reason why alt is handled the same way as fn+alt, is it a bug or a feature?
The OEM/stock kernel sources are here:
https://github.com/tdm/android_kernel_fxtec_msm8998/tree/oem-history
This also exists as history in the Lineage tree, but it is not a separate branch. You would need to go find that commit manually.
As for fn+alt, I don't think I ever considered that combination.
-
1 hour ago, Wasmachineman_NL said:
How better is it compared to stock Android? Does it unfuck the camera? Do things like EdgeNull and Audipo work?
Better is subjective. But there are many fixes and features.
Not sure what your issue is with the camera.
EdgeNull is not needed, I added my own solution. Don't know what Audipo is.
If you are interested, give it a try. You should not expect people here to give you a sales pitch.
-
1
-
-
1 minute ago, JooJooBee666 said:
FWIW, I compiled and flashed a new build with TheMuppets and Lineage OS device/kernel repo. Everything seems to be working fine.😎
@tdm As far as the 17.1 stuff goes, which repos should I be watching?
Probably Nolen's. I'm taking a break for a bit to do other stuff and he is still fresh and energized.
-
1
-
1
-
-
17 minutes ago, Wasmachineman_NL said:
What is LineageOS supposed to be, a Android fork?
Precisely.
Google makes Android and publishes the sources. The LineageOS team takes those sources and fixes bugs, adds features, etc.
Of course it is more complicated in practice and I left out all of the history. But that is the takeaway.
-
3
-
-
58 minutes ago, Craig said:
I'm just trying to understand. So with the slow OTA method you chose for your unofficial builds, we will have to to reinstall gapps/su? Or we won't?
And the fast method you're not going to use because it wouldn't work for those with gapps or su, unless you made and additional build specifically for those with gapps/&su, in which case upgrades would be fast and we wouldn't need to reinstall gapps/su? And if this additional build were in fact made, would it require user use a certain version of gapps? (For example I use opengapps-mini; I like that it replaces AOSP apps and up to date so I don;t have to go thru long upgrate process.)
And lastly, how does this relate to official OTA, will we have to reinstall gapps on updates then?
The intent is always for updates to keep you addon packages. But when the A/B system arrived, the lineage folks only got this working with OTA. They haven't yet figured out how to make it work with sideload on A/B devices. So yes, if you switch to OTA updates, your addons will stay. And no, you don't need any particular version except the correct one for your Android version.
You will need to install the first official build via sideload. After that, OTA works and keeps your addons.
-
2
-
-
4 minutes ago, EskeRahn said:
Installing V1 over Test 22 without reinstalling the gapps leads to a repeated "Google play services keeps stopping...."
Oh. Interesting. I did exactly that and it was fine. Try rebooting into recovery and install gapps again?
-
This is kind of off topic, but something to think about for future testing of 17.1, perhaps.
I got my OTA server running and tested it with a full (not incremental) update. Took roughly 45 minutes from the time the download completed. Google intentionally makes this process low priority because you are expected to be able to continue using your phone normally while the update installs. But there is an updater option to increase performance which helps some.
It would be much faster, both for download and install, to do incremental updates. But incremental updates require a pristine, unmodified device. So no adding in gapps, su, etc. The only thing I could do to satisfy everyone would be to make two (or four!) builds. And I'm not going to do that.
So... from now on I'll be providing my builds with OTA capabilities. You can feel free to use the OTA or download and install manually like you always have. Your choice.
To kick off the OTA builds, here is a v1 and v2 for anyone that cares (I know you're all probably waiting for the official build to install). You can install v1 and watch it update to v2. Or just install v2 and wait for my next build.
https://ota.nwwn.com/roms/lineage_16.0_pro1_unofficial_2020-07-17_v1.zip
https://ota.nwwn.com/roms/lineage_16.0_pro1_unofficial_2020-07-17_v2.zip
Note: my builds have the default check interval set to one day. But if you have ever opened the updater, it probably is already set to the official Lineage default of one week. So I recommend checking that. One week is a long time for build updates.
-
1
-
PRO1, LineageOS 16.0 Official Builds: Discussion
in General Discussion
Posted
Hmm, interesting. Is anyone else seeing this? I certainly don't notice it.
Also FYI... the first build missed a kernel configuration to enable EAS (the Energy Aware Scheduler, a key part of the new power stuff). So that may be causing some performance issues. It's been fixed and the next build will have it enabled.