Jump to content

tdm

Members
 View Profile  See their activity

  • Content Count

    801

  • Joined

  • Last visited

  • Days Won

    84

 Content Type 

Posts posted by tdm

    LineageOS, Current status : 16.0 Test Builds

    in Support

    Posted

    Couple updates, especially for the developers out there...

     

    I'm working with one of the upper level Lineage guys on getting the device/kernel officially imported.  He has made quite a few comments and suggestions for cleaning and improving the device tree.  So the lineage-16.0 branch on my device tree is going to be rebased and rearranged quite a few times in the next couple days.  I tagged test18 so it doesn't get lost.

     

    Said Lineage guy is actually interested in the Pro1 and I will probably send him a prototype unit.  So that's even more development support.  Which is good because he knows about quite a bit of stuff that I don't, especially recent Android things.

     

    I'll be doing at least one, probably two more builds before official Lineage submission just to make sure the cleanup/rearrange changes don't break anything.  So expect a test19 tomorrow that is hopefully still fully functional and also works with VZW.

     

    • Like 3
    • Thanks 11

    LineageOS, Current status : 16.0 Test Builds

    in Support

    Posted

    @SteffenWi that install page is apparently not correct.  I'll look to see if there is a better one available.  I did not write the page, it is a template that is linked in the wiki code.  There are several different ones to choose from.

     

    @Wheeljack I'm hoping that I can get an official TWRP working soon.  If not, I can switch out the TWRP stuff for Lineage Recovery stuff.

     

    • Thanks 2

    Problems w/ Pro1 on Sprint network

    in Support

    Posted

    I have not used CDMA in several years precisely because I like the freedom of moving my SIM to the phone I choose, when I choose.  But I believe the mule method is the most used on VZW. Because the Pro1 is a GSM phone, you will need to rely on volte for voice. So you will need to make sure that is functional on your account. I'm not clear on how SMS is handled.

     

    • Thanks 1

    LineageOS, Current status : 16.0 Test Builds

    in Support

    Posted

    I received the SIM from @Hook today and, just as I mentioned yesterday, adding the missing VoLTE properties fixed VZW voice calls.  I'll include these in the next build, but if you are impatient and willing to tinker here's what you need to do:

     

    1. Ensure adb is running as root, "adb root".

    2. Mount partitions read/write, "adb remount".

    3. Get the /vendor/build.prop file from the phone, "adb pull /vendor/build.prop".

    4. Edit the file and add the following lines at the end: 

    # VoLTE
persist.dbg.ims_volte_enable=1
persist.dbg.volte_avail_ovr=1
persist.dbg.vt_avail_ovr=1
persist.dbg.wfc_avail_ovr=1
persist.radio.calls.on.ims=1

    5. Push the file back to the phone, eg. "adb push build.prop /vendor/build.prop".

    6. Reboot, "adb reboot".

     

    When the phone comes back up, ensure all the carrier settings are correct and it should work.  I think the only thing I had to change was setting "Preferred network type" to "LTE/CDMA".  The rest of the settings were fine by default.  YMMV as always.

     

     

    • Thanks 6

    (solved) locked/broken bootloader "press volume key to select"

    in Support

    Posted

    It's not secret.  My factory restore tool should do the trick.  But, as I recall, the problem @D1ggs had was that he locked his bootloader while on non-stock and the bootloader unlock flag was not set.  This is a one-way trip and needs EDL to fix.

     

    My initial attempt at fixing this involved a custom executable, and we couldn't get that working easily.  I've since helped another user successfully.  I ended up making a very small package that can be flashed with the factory restore tool that manually sets the bootloader unlock flag.

     

    • Like 2
    • Thanks 1

    LineageOS, Current status : 16.0 Test Builds

    in Support

    Posted

    2 minutes ago, SteffenWi said:

    @tdm sorry, was a bit busy today, finally managed to flash the permissive image. For the record, I flashed the permissive image, did a factory reset, flashed the v18 .zip file, rebooted into recovery mode, flashed the GApps zip, rebooted and got into the wizard. I skipped the SIM question, because I don't have a SIM in the device, then connected to WiFi and as soon as the connection was established, the wizard started searching for updates and after that continued on as expected.

     

    Great, thank you.  So you are confirming that the WiFi in the setup wizard does not work in enforcing, but it does work in permissive.  Is that correct?

     

    • Like 1

    LineageOS, Current status : 16.0 Test Builds

    in Support

    Posted

    So I'm wading through all the commits to bring 16.0 up to 17.1 and I found a bunch of VoLTE props that are missing in 16.0.  I probably removed those before I realized that VZW folks actually used VoLTE (the other major carrier that uses it is in India, which is probably why I removed those props).

     

    I would find a VZW customer to work with to test VoLTE with these props set, but I should have a VZW SIM shortly anyway.

     

    Long story short, looks like VoLTE will probably be working Real Soon Now.

     

    • Thanks 1

    LineageOS, Current status : 16.0 Test Builds

    in Support

    Posted

    I've started the process of making this official.  Someone took the time to actually review the device stuff, so I am fixing that now.  Should have a mostly final build in the next day or two.  I also need to create lineage wiki pages for the device which is always a couple hours of fun tracking down the device specs, finding a sample picture, writing instructions, etc.

     

    • Thanks 8

    LineageOS, Current status : 16.0 Test Builds

    in Support

    Posted

    2 minutes ago, EskeRahn said:

    Installed Test 18. During boot after install it says "app keeps stopping" on the "Trebuchet". But it started non the less.

    ADD: Arrows works again 🙂

    Both nova and trebuchet worked for me.  Can you get a log?  Anyone else having issues?

     

    LineageOS, Current status : 16.0 Test Builds

    in Support

    Posted

    21 minutes ago, SteffenWi said:

    I've done a fresh installation (Full wipe and flashing of .img and .zip and gapps), but when I try to get through the setup wizard I'm stuck at setting up a WiFi connection. The connection is established, but the process doesn't continue. I can only skip, but then I get stuck at the next screen (copying apps and files) - regardless of what I select I get an error "Login not possible" ("Anmeldung nicht möglich")

    This did work in test15.

     

    Okay thanks.  There may be something in selinux that is preventing it.  We have two options: I can try to reproduce it here, or you can download a permissive boot image to try.  Which do you prefer?

     

    • Thanks 1

    LineageOS, Current status : 16.0 Test Builds

    in Support

    Posted

    test18 is up.  The only changes are fixing device specific selinux rules (for eg. fingerprint, keyboard, touchscreen margins, etc.)

     

    Again, this is on the verge of being submitted for official Lineage builds.  Please report any issues.

     

    Also pushed up code changes to github.

     

    Enjoy!

     

    • Like 1
    • Thanks 3

    LineageOS, Current status : 16.0 Test Builds

    in Support

    Posted

    1 hour ago, EskeRahn said:

    Oddly Up/Down arrows seem to be swapped with Right/Left

    And a strange long delay/response-time when cycling through languages with Ctrl+Space

    That's another thing, the keyboard idc file isn't properly labeled. That disables the arrow change with orientation.

    LineageOS, Current status : 16.0 Test Builds

    in Support

    Posted

    I started looking into fixing the keyboard layout boot code and noticed several other things are broken.  Basically all the custom device stuff, from the keyboard to the display margin to livedisplay and so on.  I'll get that all cleaned up for the next build.  Probably tomorrow.

     

    • Thanks 4

    LineageOS, Current status : 16.0 Test Builds

    in Support

    Posted

    2 hours ago, Wheeljack said:

    Like I said... hard to trigger. Usually both keyboards work fine.

    Just installed test17 without problems. SELinux shows as "Enforcing". Not seeing any new issues.

     

    Edit: Now that I'm trying to write from my phone, I notice the QWERTZ layout is shifted.

     

    That would be selinux blocking the script which sets the keyboard layout at boot.  I'll try to fix that shortly.  In the meantime, you may set it manually as root (either in a root terminal shell or a root adb shell).

     

    • Thanks 3

    LineageOS, Current status : 16.0 Test Builds

    in Support

    Posted

    10 minutes ago, SchattengestaIt said:

    I have had quite a few system crashes since I installed the custom ROM, always resulting in hard reboots (with the FxTec logo). In most cases it happened while using Bluetooth for a webradio and Google Maps. Luckily no data was lost but it is still inconvenient.
    Which program could/should I use to create and read error logs or crash reports?

    Also I had some issues with the keyboard having no input until I restarted. Probably an issue with a software keyboard.
    Could a soft reboot (system only) be implemented into the power menu? I remember that it was on older LineageOS versions. If you want such recommendations on GitHub only, please tell me.

    A logcat and dmesg live from the system as it crashes is best.

     

    Yes you can add reboot to the power menu.

     

    LineageOS, Current status : 16.0 Test Builds

    in Support

    Posted

    Test17 is up. The only changes are selinux rules and enabling selinux.

     

    This is getting dangerously close to submitting for official builds.

     

    Please test and let me know if anything is broken. I've verified it boots and the lights hal and FP reader work, but not much else.

     

     

    • Like 1
    • Thanks 6
×
×
  • Create New...

Important Information

Terms

  I accept