• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

Search results

  1. jabashque

    Post [ROM][OFFICIAL][fajita][11] LineageOS 18.1

    Well, yeah, the prebuilt kernel in that twrp.img doesn't contain the changes to work on R fw without entering crashdump mode. It's less hassle to just follow what the wiki says for updating vendor + fw: https://wiki.lineageos.org/devices/fajita/fw_update
  2. jabashque

    Post [ROM][OFFICIAL][fajita][11] LineageOS 18.1

    Not quite sure what you're facing... I have not encountered any of these issues at all on my own self-builds. (I did run a `mka installclean` just in case before building, since the entire set of proprietary blobs was changed.)
  3. jabashque

    Post [ROM][OFFICIAL][fajita][11] LineageOS 18.1

    As @Eric_Lev mentioned, update to the newest build first before updating to Android 11 vendor + fw. Without the kernel changes from the newest build, your phone will end up booting into crashdump mode on Android 11 fw, whether you try booting android or recovery. I'd suppose if you already did...
  4. jabashque

    Post [ROM][OFFICIAL][fajita][11] LineageOS 18.1

    No, not entirely. The changes to the device tree and kernel still keep compatibility with Q vendor+fw, but you'll lose ANT+ and DASH charging support. However, once lineage-19.x comes about, support for Q vendor+fw will be dropped. EDIT: that being said, I converted my fajita to intl from tmo...
  5. jabashque

    Post [ROM][OFFICIAL][fajita][11] LineageOS 18.1

    No, that's completely wrong. The existence of fastbootd is not because Lineage broke abl's ability to accept fastboot commands--it's because of this: https://source.android.com/devices/tech/ota/dynamic_partitions And since abl (bootloader) won't be able to detect the partitions within said...
  6. jabashque

    Post [ROM][OFFICIAL][fajita][11] LineageOS 18.1

    Go to Settings -> Connected Devices -> that little cog wheel next to your Bluetooth device, and then turn off HD audio. SBC HD is being turned on by default in this week's fajita build, but not all Bluetooth devices can handle it. If the BT device doesn't work well with it, the audio will end up...
  7. jabashque

    Post [ROM][OFFICIAL][fajita][10] LineageOS 17.1

    I have it working on my dad's fiancée's car (Mazda2, using MZD AIO Tweaks implementation of Android Auto). Don't have any other cars to test with though.
  8. jabashque

    Post help with wont work with carrier, (yes its unlocked)

    Just double-checking, did you already call MetroPCS about transferring her line to a new phone? (since I know they still whitelist one IMEI at a time for each line and require you to call in to change which IMEI your line is associated with, even though there's no technical reason for them to...
  9. jabashque

    Post [ROM][OFFICIAL][fajita][10] LineageOS 17.1

    would you happen to be using magisk, xposed, etc.? Will ask you to try core-only mode for Magisk if you have that installed.
  10. jabashque

    Post [ROM][OFFICIAL][fajita][10] LineageOS 17.1

    Just to check, is this happening to both of you on the 20200430 build?
  11. jabashque

    Post [ROM][8.1.0][OFFICIAL] LineageOS 15.1 for Nextbit Robin (ether)

    Well, IMS doesn't work at all on 16.0, so you don't even get VoLTE as a result. IMS works partially on 15.1 and at least allows VoLTE, but not wifi calling. As for a custom rom with wifi calling support, I'm afraid you'll have to stick with Nougat for that.
  12. jabashque

    Post [ROM][8.1.0][OFFICIAL] LineageOS 15.1 for Nextbit Robin (ether)

    I'm not sure if this ever got mentioned in any place other than javelinanddart's old Hangouts group.
  13. jabashque

    Post [ROM][8.1.0][OFFICIAL] LineageOS 15.1 for Nextbit Robin (ether)

    Last I recall, whatever IMS-related blobs that were being used for 15.1 only supported VoLTE, not wifi calling. javelinanddart couldn't get wifi calling to work at the end.
  14. jabashque

    Post Essential Phone lock-out after factory reset

    I was able to bypass FRP on a used Essential Phone I got from eBay, which was running PPR1.180610.091 (August 2018 Pie release, the first one ever). Most instructions seem to involve using TalkBack or GBoard input settings to navigate to the online Help & Support activity, then searching for a...
  15. jabashque

    Post LineageOS 16.0 appears to be live for the Essential Phone. Anybody try it yet?

    A fix for this has been merged and will be present in the 08/04 nightly.
  16. jabashque

    Post [ROM][OFFICIAL][G4][7.0.0] A.O.S.C.P: CypherOS Project

    Regarding people getting ancient app versions when downloading off Google Play, I remember seeing something similar on LineageOS 16.0 for bacon where Google Play was serving 3-4 year old app versions to devices with the bacon CyanogenOS Marshmallow fingerprint (which LineageOS was using)...
  17. jabashque

    Post [OFFICIAL] [NIGHTLIES] LineageOS 16.0

    The device tree for the official TWRP builds haven't been updated since the Marshmallow days and has very awful graphical performance. The one linked in the wiki was built off the Lineage trees instead, if I recall right, and graphics performance isn't utter crap.
  18. jabashque

    Post [ROM][TREBLE][X72X][9.0.X] LineageOS 16.0 (Pie) for LeEco Le Pro3

    selinux has already been enforcing on 16.0 for at least a few weeks now. (not to mention that it's required for official Lineage builds anyway)
  19. jabashque

    Post [ROM] [TREBLE] [9.0] [Official] AICP 14.0 (Pro3 aka zl1, zl0, X727,X720,X722)

    Last I've known, he's been trying to figure out why he can't get his zl1 to boot with the February Security patch merged into AICP.
  20. jabashque

    Post [ROM][TREBLE][X72X][9.X][pre-OFFICIAL] OmniROM 9 Pie

    I took a look and it actually flashes the thermal engine config that I made and got merged into LineageOS, AICP, RR, and (unofficial) AOSiP.
  21. jabashque

    Post [ROM][TREBLE][X72X][9.0.X] LineageOS 16.0 (Pie) for LeEco Le Pro3

    I guess we could cherrypick this commit to fix that: https://github.com/shivatejapeddi/kernel_leeco_msm8996/commit/7770fcb8d2b112e0b5468c67d116a4ff116c8645 I was playing around with thermal-engine.conf and did notice that even if I unplug only one of the big cores, performance tanked. Sure...
  22. jabashque

    Post [ROM][Official][Nightly] LineageOS 16.0 for OnePlus 3/3T

    I took a look at the Havoc OS op3 device tree and saw this: https://github.com/Havoc-Devices/android_device_oneplus_oneplus3/commit/65be9bf117b22d2e6436445b64cffb12b76049c7 So apparently they just force WhatsApp to use HAL1 camera.
  23. jabashque

    Post [ROM][TREBLE][X72X][9.0.X] LineageOS 16.0 (Pie) for LeEco Le Pro3

    EDIT: pfft, the not-equals sign broke XDA forums and the rest of my comment was lost. Lemme fix this... EDIT 2: Meh, never mind. The main idea was that I had thought you were confusing VoLTE and HD Voice. VoLTE refers to placing calls while connected to LTE, and HD Voice refers to using...
  24. jabashque

    Post [ROM][TREBLE][X72X][9.0.X] LineageOS 16.0 (Pie) for LeEco Le Pro3

    I don't think VoLTE and/or HD voice indicators in the status bar is standard in AOSP; those indicators were added in custom roms, but Lineage isn't a custom rom that has those indicators. The only true indicator is seeing if your device drops down from LTE to H+ during a call.
  25. jabashque

    Post [ROM][TREBLE][X72X][9.0.X] LineageOS 16.0 (Pie) for LeEco Le Pro3

    I'm pretty sure this rom has had VoLTE support for a while; I was able to place a call over LTE about a month ago before I switched carriers. It's just that it's via a somewhat hacky way that results in you having to choose a SIM to use as your primary every time you reboot. Of course, that's...
  26. jabashque

    Post [ROM][OFFICIAL][G4][7.0.0] A.O.S.C.P: CypherOS Project

    You probably should've clarified earlier that you meant 14.1, not 14.0 lol EDIT: I missed the fact that there was another page of this thread where this was clarified, oops.
  27. jabashque

    Post [ROM] [TREBLE] [8.1] [Official] AICP 13.1 (Pro3 aka zl1, zl0, X727,X720,X722)

    You can also check your current capacity (which would also be around your max capacity if you're at 100%) by reading /sys/class/power_supply/battery/charge_counter, which doesn't depend on estimating capacity by comparing input amperage and battery percent increases like what AccuBattery does.
  28. jabashque

    Post [ROM][OFFICIAL][G4][7.0.0] A.O.S.C.P: CypherOS Project

    Hi, I'm running a LineageOS 14.1 build I made earlier this week, with changes to the one-handed mode feature to shrink down to a quarter of my screen, since the right half of my screen is all screwed up. Anyway, here's the logcat for me pairing my bluetooth headphones to my LG G4...
  29. jabashque

    Post [ROM] [TREBLE] [8.1] [Official] AICP 13.1 (Pro3 aka zl1, zl0, X727,X720,X722)

    So, actually, ThE_MarD found out how to fix WiFi calling with the Gemini blobs (which doesn't screw with deep sleep unlike the bardockpro blobs from 5/10) and the fix is present in today's LineageOS build. Not sure if Moshe merged those changes into the AICP device tree yet, or if he's focused...
  30. jabashque

    Post Unbrick leeco X722 using qfil and flashone 2.0

    Now, is this while your phone is plugged in? Because for some reason, the Leeco kernel sources includes code to lower the touch screen sample rate from 120Hz to 60Hz when plugged in. I'm not even sure why though, since I removed that code and my device is still fine when plugged in...
  31. jabashque

    Post [ROM][TREBLE][X72X][8.1.X][OFFICIAL] LineageOS 15.1 (Oreo) for LeEco Le Pro3

    Steps: 1) Spawn a root shell with whatever method you like. 2) run `mount -o rw,remount /vendor` to make vendor writeable 3) Open /vendor/etc/init/hw/init.qcom.rc and make the changes shown here...
  32. jabashque

    Post [ROM][TREBLE][X72X][8.1.X][OFFICIAL] LineageOS 15.1 (Oreo) for LeEco Le Pro3

    I mean, it's really more like ThE_MarD found it some weeks ago and was trying to figure out how to fix it all this time without just outright removing dpmd from starting up (which was what I ended up doing to my phone since I needed a quick fix), but sure I guess? EDIT: oh no I got hit by the...
  33. jabashque

    Post [ROM] [TREBLE] [8.1] [Official] AICP 13.1 (Pro3 aka zl1, zl0, X727,X720,X722)

    I have Magisk installed too, and the battery drain problem for me came from dpmd constantly crashing and init trying to restart dpmd every two seconds (which you can see in your dmesg). I believe the maintainers are replacing our DPM stack (which came from the OnePlus 3) with the one from the...
  34. jabashque

    Post [ROM][TREBLE][X722][8.1.X][OFFICIAL] LineageOS 15.1 (Oreo) for LeEco Le Pro3 Elite

    Turns out that was actually not the solution for 15.1; it's only for 16.0 because codeworkx kanged the DPM stack from the Nokia 7 for 16.0. A different solution that keeps dpmd is needed for 15.1.
  35. jabashque

    Post [ROM][TREBLE][X722][8.1.X][OFFICIAL] LineageOS 15.1 (Oreo) for LeEco Le Pro3 Elite

    So, init has been randomly using 30% cpu every 2 seconds because it keeps trying to spawn dpmd every two seconds, and dpmd keeps crashing. It actually is already fixed (https://review.lineageos.org/#/c/LineageOS/android_device_leeco_msm8996-common/+/229524/) BUT only for the lineage-16.0 branch...
  36. jabashque

    Post [ROM][8.1.0][OFFICIAL] LineageOS 15.1 for Nextbit Robin (ether)

    Probably because Google took it down due to the app offering to install Rootless Pixel Bridge to allow Google Feed integration. Source: https://www.androidpolice.com/2018/09/04/google-pulled-rootless-pixel-launcher-play-store/
  37. jabashque

    Post [ROM][Official][Nightly] LineageOS 15.1 for OnePlus 3/3T

    Has anyone else been having issues with qcom_rx_wakelock blocking their OP3t from entering deep sleep? This is a friend's phone, so I can't immediately check things aside from telling him to generate bug report zips that I can run through Battery Historian, but this was a similar problem that...
  38. jabashque

    Post [ROM][TREBLE][X722][8.1.X][OFFICIAL] LineageOS 15.1 (Oreo) for LeEco Le Pro3 Elite

    Magisk has been able to pass SafetyNet all this time. Google just changed how applications can query for SafetyNet status, which broke all the SafetyNet checking applications out there a few weeks ago. Use this app to check your SafetyNet status instead until topjohnwu fixes Magisk's built in...
  39. jabashque

    Post [ROM][8.1.0][OFFICIAL] LineageOS 15.1 for Nextbit Robin (ether)

    The change he made back then (https://review.lineageos.org/#/c/LineageOS/android_device_nextbit_ether/+/204499/) is still present in the 15.1 device tree, so whatever issue you were having back then would still be present. Now, I definitely was able to control the speakerphone volume after that...
  40. jabashque

    Post [ROM][8.1.0][OFFICIAL] LineageOS 15.1 for Nextbit Robin (ether)

    I'm using the TWRP linked in the LineageOS wiki. The offiical TWRP builds use a device tree that hasn't been updated since Android Marshmallow, and the UI is laggy to hell and back. This is not the case in the unofficial one from the Lineage wiki.
  41. jabashque

    Post [ROM][8.1.0][OFFICIAL] LineageOS 15.1 for Nextbit Robin (ether)

    Please use either of the following: MindTheGapps, from http://downloads.codefi.re/jdcteam/javelinanddart/gapps/MindTheGapps-8.1.0-arm64-20180808_153856.zip Open GApps nano from August 19th or earlier. (or any OpenGApps variant, as long as the dialer doesn't get replaced with Google Dialer)...
  42. jabashque

    Post [ROM] Official Omni Oreo [8.1.0] [VoLTE]

    Delete /system/addon.d/70-gapps.sh, then dirty flash OmniROM and a GApps package that doesn't include the camera (or the aroma version, if you untick Google Camera). Easiest way would be to boot into TWRP, mount /system, then delete 70-gapps.sh using the file manager.
  43. jabashque

    Post [ROM] Official Omni Oreo [8.1.0] [VoLTE]

    Update your TWRP to version 3.2.1. EDIT: I have no idea if you can actually dirty flash OmniROM 8.1.0 over 7.1.2, since I know that for LineageOS, they have to prepare special transition builds that upgrade various databases or whatever. But, if dirty flashing does work, then yes, you would...
  44. jabashque

    Post [ROM] [7.1.x] LineageOS 14.1 OFFICIAL Builds (ether)

    Yeah, that was why I ended up adding in the EDIT in my previous post after I realized that I didn't really know what I was trying to achieve at the end, especially when you were referring to overall lagginess when interacting with the phone in general and not just when waking the phone up. Sorry...
  45. jabashque

    Post [ROM] [7.1.x] LineageOS 14.1 OFFICIAL Builds (ether)

    I hadn't observed that big core behavior back on the Nougat-based roms. Instead, I'd end up seeing both the little cores and big cores being slowed down (787MHz for the little cores, 384MHz for the big cores), but the big cores never being shut off. For what it's worth, on Omni 8.1.0, I went...
  46. jabashque

    Post [ROM] [7.1.x] LineageOS 14.1 OFFICIAL Builds (ether)

    Oh, no, I am finding my experience to be overall smoother on Omni with the CAF power hal, but I wanted to know if you were able to narrow down what tweaks were causing the issues. I remember that javelinanddart had pulled in a bunch of tweaks from the sambar (Yu Yutopia) device tree for the...
  47. jabashque

    Post [ROM] [7.1.x] LineageOS 14.1 OFFICIAL Builds (ether)

    I meant that as in "what particular tweaks in the custom power hal were causing the lag", though I didn't really make that clear in my previous post.
  48. jabashque

    Post [ROM] [7.1.x] LineageOS 14.1 OFFICIAL Builds (ether)

    Ah, I see. Could you clarify what sort of issues the custom power hal had, just out of curiosity?
  49. jabashque

    Post [ROM] [7.1.x] LineageOS 14.1 OFFICIAL Builds (ether)

    (Might want to keep in mind that the most recent build javelinanddart posted defaults to running the display at 45Hz. If you run `setprop persist.sys.display.frame_rate 2` in a root or adb shell, you can change the framerate back to 60Hz.)
  50. jabashque

    Post [ROM] Official Omni Oreo [8.1.0] [VoLTE]

    Okay, well that wouldn't be a problem for me then. (though I'd guess a clean flash would be highly recommended once you switch back to using your own kernel instead of lineage's)