Jump to content

Hook

Keymaster
  • Content Count

    1,974
  • Joined

  • Last visited

  • Days Won

    264

Posts posted by Hook

  1. 7 hours ago, Hook said:

    I think I am also seeing it on my Pro1x. I'm testing this week-end.  But I also have been getting unusual battery drain on my Pixel 7 Pro.  Coincidence? Or is the problem an Android 15 update problem and not a purely Lineage problem.  I did a simulated battery pull on both devices (to clear out janky stuff going on and will watch both.

    I am actually seeing much better battery performance after the simulated battery pull.  My Pro1x only dropped from my max of 85% to 77% in 7 hours, and my Pixel only dropped to 80% with quite a bit of use.  I'll keep monitoring just to make sure I'm not jumping to conclusions, But I have to admit simulated battery pull is my go-to for weird stuff happening.

    However, now I need to try it with my Pro 1, which I haven't used much for a couple of weeks.

  2. 37 minutes ago, TeZtdevice said:

    I can confirm the issue with the energy usage, since LOS 22.2

    I think I am also seeing it on my Pro1x. I'm testing this week-end.  But I also have been getting unusual battery drain on my Pixel 7 Pro.  Coincidence? Or is the problem an Android 15 update problem and not a purely Lineage problem.  I did a simulated battery pull on both devices (to clear out janky stuff going on and will watch both.

    • Like 2
  3. I don't know if I have a suggestion, but I suspect more information is needed. Is this a Pro1x that was formerly working ok and this just suddenly happened?  Or did it do this when you got it.  If the former, what kinds of things were you doing with the phone? Is it Stock Android or did you flash some other ROM?  Anything you can tell people will help them decide if they know something you can try.

  4. 15 minutes ago, EskeRahn said:

    As the download is still unavailable I did an OTA that WAS available. So now on
    lineage-22.2-20250419-nightly-pro1-signed.zip on April 5 security patch

    I don't really understand what mirrorbits is or what it's advantages are (even after reading their Github, lol), but Saturday's Pro1 update downloads just fine from the official Lineage download sites. Just FYI for folks.

    • Thanks 1
  5. The same thing happened to my Pro1 about a month before the end of its 2 year warranty. Replacing the screen didn't fix it, so it isn't the screen or at least not entirely. Luckily this was 2021 and FxTec accepted it for warranty repair. I had to wait 6 months until they got their Pro1 parts shipments. Unfortunately, I didn't ask what the exact problem was and what they did to fix it. I was just happy to get my phone back 6 months later. It has never reoccurred.

  6. 1 hour ago, CornholioGSM said:

    Does not work you mean cannot be installed or cannot work correctly?

     

    ...i can test to edit apk for newer api support.

    BUT first - have you tested apk sideload from pc?

    Test this:

    adb install --bypass-low-target-sdk-block path/to/PACKAGE.apk

    EDIT - adb install is working on los22.2. If apk runs correctly i am not sure

     

     

    Interesting,  I *think* but do not know that it means does not work correctly.  The trouble is, to test it, I would need to replace the screen, and I'd rather not.  Lol.  But you raise a good possibility. If I ever have a screen fail on my Pro1x, I will test.

  7. Lineage-22.2-20250414-NIGHTLY-pro1x with April 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.

    Notes: I encountered no problems after the OTA going from 22.1 to 22.2.  I use Magisk, but only as SU, I don't use any Magisk modules.  

    Also, since I update OTA, I don't flash newer packages of MindTheGapps. My contention is, that since Google updates both the Gapps and Play services, there is no need to flash the newer MTG packages unless you are moving to a new full version of Lineage (new version of Android) that can't be installed OTA.  I don't know 100% that I'm right, but it makes sense to me and until I run into a problem, I'm sticking to my story.  🙂

    • Like 3
    • Thanks 1
  8. 1 minute ago, EskeRahn said:

    Oh indeed this is also simpler for Pro1, but would be really great if it also worked for pro1X, where there are no known fix at all (except using a Pro1 to do it)

    The main problem for the Pro1x is that the app doesn't work on any version of Android after Android 10 (Lineage 17) and the Pro1x doesn't have any options older than Android 11.

    • Sad 1
  9. The lineage page is correct.  CPU-Z misreports it.  I've had Lineage on for a very long time and it works fine.  Lineage is currently on Android 15 (Lineage 22) which you will probably not be thrilled by if you don't like Android 11. Android 11 is the earliest Android the Pro1x can take. But yes, you can reinstall stock Android 11 if you don't like Lineage, but you will get no security updates.

    Make sure you thoroughly investigate the Pro1x's call and text performance on Stock. Lineage will not affect that, either ofr better or worse, so make sure you know what the problems are ahead of time.

    • Like 1
    • Thanks 2
  10. 40 minutes ago, claude0001 said:

    OK. I just think: this sounds like a general regression in AOSP, as keyboard support in Android is generally nothing specific to the Pro1 (hence my question whether this is also observed in the Pro1-X port). I just wonder if it could be worthwhile to open a bug against LineageOS because of this.   

    I just tested on my Pro1x with LOS.  I think it works there.  That is (just to confirm I know what is being talked about).  I added Dansk (Denmark) to my list of system languages (the main one is US English).  When I go to type in an editor, I am typing in English. and then I hold the yellow arrow and press spacebar and I get a notification that I am now typing in Dansk and I can get that weird ae mashup ;-).  I can use the yellow arrow spacebar as a toggle between the two.

    Doesn't work on my Pro1. yellow arrow + spacebar pulls up search.  Don't know why.  My Pro1 is currently Google Free, though I may be changing that.

    • Thanks 2
  11. 12 minutes ago, Kenny said:

    Rubber band worked for me, but now my battery shows 1% - plugged in, can't charge right now. Occasionally it will go up to 35 to 65 percent, but if unplugged it drops to 1 almost immediately. Not sure if it's software or hardware related. It does turn off after a bit if I unplug it. Anyone else experiencing this?

    Yeah, that's not normal.  Try a different charging cable or even a different charging brick (you are using wall charger and not USB port on computer, right?) If either is faulty, after the rubber band got it going, the cable or wall wart alone might not be enough to charge faster than discharge. Start with the cable. Try a different cable and leave it plugged in for a while.

  12. I doubt I "rubbished" you as that is generally not my style.  All I see in that thread is us kind of agreeing on what works.  Lol.

    Basically, what works for me (and I can only vouch for me) is that I side load Magisk as a zip when I first install a full version of LOS, then open the app and let it do the automatic install which takes care of the whole patching the boot sector.  After that, OTA always maintains root.  But as long as you have found a method that works for you, that's great.

     

    • Like 1
×
×
  • Create New...

Important Information

Terms