Craig 1,435 Posted January 31, 2020 Share Posted January 31, 2020 (edited) @D1ggs People who've used the previous test build have all reported it's pretty stable, certainly as stable as stock, it's just lacking some features and has some rough edges, but some people have already chosen to use it as daily driver. If I were you, I'd wait a few days to see how people react to the test version he's about to release, usually any big problems are noticed right away if enough people test, anyway. Or you could help test yourself if you don't demand stability. Or just play it safe until they make it 'official' which is when they (the devs) think they've ported all features/support all hardware, etc. Edited January 31, 2020 by Craig 1 Quote Link to post Share on other sites
tdm 2,322 Posted January 31, 2020 Author Share Posted January 31, 2020 33 minutes ago, D1ggs said: Hey @tdlnxhow far along is the ROM? Is it cause for a daily driver or should we wait until it gets more stable. That will be up to you to decide. If you are hesitant, wait for a few days after I release test3 tomorrow and see what others say. But I believe it will be mostly on par with stock except for the FM radio. 1 4 Quote Link to post Share on other sites
D1ggs 141 Posted January 31, 2020 Share Posted January 31, 2020 2 hours ago, tdm said: That will be up to you to decide. If you are hesitant, wait for a few days after I release test3 tomorrow and see what others say. But I believe it will be mostly on par with stock except for the FM radio. Thanks looking forward to it. Quote Link to post Share on other sites
_DW_ 628 Posted January 31, 2020 Share Posted January 31, 2020 (edited) 10 hours ago, tdm said: That will be up to you to decide. If you are hesitant, wait for a few days after I release test3 tomorrow and see what others say. But I believe it will be mostly on par with stock except for the FM radio. Thats good to hear, I was presuming an install and wipe as it's a test build. Might try setting up most things I use on it then see what happens 🙂 Edited January 31, 2020 by _DW_ Quote Link to post Share on other sites
Gigadoc2 54 Posted January 31, 2020 Share Posted January 31, 2020 @tdm: Is the switch from test2 to test3 requiring a wipe because of switching from stock vendor to lineage vendor? I am asking because I've built from your repositories already and for me it does, but I could be doing something wrong. Quote Link to post Share on other sites
tdm 2,322 Posted January 31, 2020 Author Share Posted January 31, 2020 2 hours ago, Gigadoc2 said: @tdm: Is the switch from test2 to test3 requiring a wipe because of switching from stock vendor to lineage vendor? I am asking because I've built from your repositories already and for me it does, but I could be doing something wrong. I have not tested this, but it is plausible. Quote Link to post Share on other sites
tdm 2,322 Posted January 31, 2020 Author Share Posted January 31, 2020 test3 is up on my server. I haven't fixed FM radio or the fingerprint reboot issue yet, but I'm tossing this out because it's been way too long since any updates. 2 2 Quote Link to post Share on other sites
Craig 1,435 Posted January 31, 2020 Share Posted January 31, 2020 (edited) 1 hour ago, tdm said: test3 is up on my server. I haven't fixed FM radio or the fingerprint reboot issue yet, but I'm tossing this out because it's been way too long since any updates. THANKS!! Does this include netman's kernel fixes (keyboard chording/etc), and mccrearys work on keyboard and slider stuff? Edited January 31, 2020 by Craig Quote Link to post Share on other sites
tdm 2,322 Posted January 31, 2020 Author Share Posted January 31, 2020 8 minutes ago, Craig said: THANKS!! Does this include netman's kernel fixes (keyboard chording/etc), and mccrearys work on keyboard and slider stuff? Nope, not yet. That will come soon. 3 Quote Link to post Share on other sites
tdm 2,322 Posted February 1, 2020 Author Share Posted February 1, 2020 Found the issue with the fingerprint reader. The hardware and Android keep separate lists of registered fingerprints. When you wipe data, Android list is cleared but the hardware list is not. Eventually the hardware has all 5 slots filled and won't accept any more. So the new data only exists in memory and fails to write to persistent storage. I'll investigate more to see how this is supposed to work, and I should have a fix soon. In the meantime you can delete the fingerprint files under /persist to fix it. 1 4 Quote Link to post Share on other sites
Gigadoc2 54 Posted February 1, 2020 Share Posted February 1, 2020 Why is that stored in persist in the first place? Has it something to do with the FDE of stock? Though you'd always unlock before using Fingerprint anyway? Quote Link to post Share on other sites
tdm 2,322 Posted February 1, 2020 Author Share Posted February 1, 2020 (edited) 9 minutes ago, Gigadoc2 said: Why is that stored in persist in the first place? Has it something to do with the FDE of stock? Though you'd always unlock before using Fingerprint anyway? No way to tell. The fingerprint files are just tossed into the bsp as binaries. So only BetterLife (the fingerprint vendor) knows for sure. Edit: yeah for FDE, data is decrypted long before the FP service starts. Edited February 1, 2020 by tdm Quote Link to post Share on other sites
D1ggs 141 Posted February 1, 2020 Share Posted February 1, 2020 @tdm Hey bud, I noticed you have a typo in your lineage os instructions on your site. The command fastboot flash boot_a lineage-16.0-pro1-test2-boot.img Shouldn't have the _ and should look like: fastboot flash boot lineage-16.0-pro1-test2-boot.img I'm embarrassed to admit it took me way too long to figure out what the heck was going on. Maybe your version is different, but if someone else has this issue, this is what I did and it worked. 1 Quote Link to post Share on other sites
tdm 2,322 Posted February 1, 2020 Author Share Posted February 1, 2020 (edited) 2 minutes ago, D1ggs said: @tdm Hey bud, I noticed you have a typo in your lineage os instructions on your site. The command fastboot flash boot_a lineage-16.0-pro1-test2-boot.img Shouldn't have the _ and should look like: fastboot flash boot lineage-16.0-pro1-test2-boot.img I'm embarrassed to admit it took me way too long to figure out what the heck was going on. Maybe your version is different, but if someone else has this issue, this is what I did and it worked. Actually boot_a works and I use it to be explicit. But test2 should be test3. Edited February 1, 2020 by tdm Quote Link to post Share on other sites
D1ggs 141 Posted February 1, 2020 Share Posted February 1, 2020 (edited) 9 minutes ago, tdm said: Actually boot_a works and I use it to be explicit. But test2 should be test3. Weird, my version of adb and fastboot was insistent that it wasn't working. I kept getting this error: fastboot: error: cannot determine image filename for .. Either way, i'm glad to have it working. Edited February 1, 2020 by D1ggs Quote Link to post Share on other sites
bmccrary 39 Posted February 1, 2020 Share Posted February 1, 2020 Is there anything specific to be done to update? I've tried several times but can't get it to boot. The Lineage recovery is saying the OS can't start and to do a factory reset but I have several hundred apps and GB of data already on the phone and would prefer not to if I can somehow get it to work. Reflashing test2 won't boot either at this point. The adb sideload completes without any problem. Quote Link to post Share on other sites
tdm 2,322 Posted February 1, 2020 Author Share Posted February 1, 2020 2 minutes ago, bmccrary said: Is there anything specific to be done to update? I've tried several times but can't get it to boot. The Lineage recovery is saying the OS can't start and to do a factory reset but I have several hundred apps and GB of data already on the phone and would prefer not to if I can somehow get it to work. Reflashing test2 won't boot either at this point. The adb sideload completes without any problem. No, that is strange. This usually happens when data fails to mount/decrypt. Had you previously been running test2? Full disclosure: I didn't test this exact zip, I flashed one that I built on another machine. But it should be the same exact code. I can try this one later tonight or tomorrow if others also have problems. Quote Link to post Share on other sites
tdm 2,322 Posted February 1, 2020 Author Share Posted February 1, 2020 @bmccrary Can you adb in to recovery? You can edit build.prop and set adb on at boot to see the error in the log. 1 Quote Link to post Share on other sites
bmccrary 39 Posted February 1, 2020 Share Posted February 1, 2020 3 minutes ago, tdm said: No, that is strange. This usually happens when data fails to mount/decrypt. Had you previously been running test2? Full disclosure: I didn't test this exact zip, I flashed one that I built on another machine. But it should be the same exact code. I can try this one later tonight or tomorrow if others also have problems. Yes, I had been running test2 before. I repeated the steps to install the test2 build but I didn't reset anything. I can try that but was just hoping to not have to. I understand what you're saying though if it can't access the main decryption key my PIN would then use to decrypt the /data partition. Quote Link to post Share on other sites
bmccrary 39 Posted February 1, 2020 Share Posted February 1, 2020 2 minutes ago, tdm said: @bmccrary Can you adb in to recovery? You can edit build.prop and set adb on at boot to see the error in the log. Ah cool, didn't know you could do that! I've got a shell up, I'll play around. Quote Link to post Share on other sites
mcdinner 375 Posted February 1, 2020 Share Posted February 1, 2020 I can confirm boot problem. @tdm @bmccrary Also test2 installed 1 Quote Link to post Share on other sites
SteffenWi 139 Posted February 1, 2020 Share Posted February 1, 2020 (edited) got a new issue - I can't get the virtual keyboard to popup now. But at least it boots fine for me after wiping it as described in the manual 😉 Edited February 1, 2020 by SteffenWi 1 Quote Link to post Share on other sites
tdm 2,322 Posted February 1, 2020 Author Share Posted February 1, 2020 5 hours ago, mcdinner said: I can confirm boot problem. @tdm @bmccrary Also test2 installed Please try wiping data. Quote Link to post Share on other sites
bmccrary 39 Posted February 1, 2020 Share Posted February 1, 2020 @tdm Wiping data allowed me to boot ok. I reflashed test3 and it would boot but the boot animation would just run on forever. I had problems with the first flash for some reason, at least I think that was my initial problem as I never could get /system to mount using the menu in the recovery, or was able to mount it in the recovery adb shell. 1 Quote Link to post Share on other sites
tdm 2,322 Posted February 1, 2020 Author Share Posted February 1, 2020 I suspect something with the built vendor image is different than the stock vendor image. @Gigadoc2 mentioned a few posts back that he had to wipe after the switch, and I guess we now have two people that have confirmed it. I'm sorry for that, wiping data is usually not necessary -- even in the test stage. It should not be necessary again. 1 1 Quote Link to post Share on other sites
Recommended Posts
Posted by tdm,
Pointer to new thread on official build
Recommended by EskeRahn
5 reactions
Go to this post
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.