Jump to content

npjohnson

Members
  • Content Count

    15
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by npjohnson

  1. 6 hours ago, brunoais said:

    Qualcomm has turned their back to F(x)tec and with a complete F*ck you, even after having fully promised to deliver and having been paid. Yeah, you can't make that **** up.

    So, we are left with 2 major choices with which F(x)tec has already tried to choose from. I wish we were consulted as a community first but I guess, when under stress, people make mistakes. Specially such newcomers into this business.

    1. Redesign of PRO¹ (possibly into PRO²) and use a much more recent SoC as powerful or more powerful than SD 835 (9 months delay)
    2. Slight redesign of PRO¹ to accommodate SD662 and get the phone earlier (5 months delay)

    See announcement here: https://www.indiegogo.com/projects/pro1-x-smartphone-functionality-choice-control/x/14443522

    Given our situation, I ask the community wether they prefer to wait longer, until the end of 2021 or very early 2022 for a better product (which will require significant work and considerable silence periods from F(x)tec's part!) or to get an inferior product but almost guaranteed on August/September?

    Vote! Show them your POV on it.

    QCOM isn't at fault here - they're probably entirely unaware of any of this given they haven't supported the SD835 for years.

    It's IdeaLite, the ODM that went back on their word.

    • Like 2
    • Thanks 1
  2. 39 minutes ago, EskeRahn said:

    Sorry, Did not guess that it was moved to

    Settings ► System ► Buttons ► Extra ► Additional buttons,

    🙂

     

    It is required - system mounts are handled differently, ROM will probably flash but GApps won't -- just use 17.1 recovery lol.

    1 hour ago, EskeRahn said:

    I do not know if you NEED it, but it looks substantially different, so I would suggest so, unless someone can say explicitely that they know you do not need it.

     

    And yeah, we moved all button settings to, well, button settings haha.

    • Like 1
  3. 8 hours 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. 🙂

    In Recovery Menu: Advanced -> Enable ADB - it's supposed to be secure by default 🙂 

    2 hours ago, SteffenWi said:

    I'm sorry but could someone take another look at https://wiki.lineageos.org/devices/pro1/install

    The instructions for flashing the recovery image are...weird. Something about temporary flashing? And the command doesn't match what we previously used either.

    Before: fastboot flash boot_a lineage.img

    According to the install page: fastboot flash lineage.img

    And then those confusing notes about wether an A/B device is used? I thought the Pro1 *is* an A/B device?

    I have no clue where you're seeing `fastboot flash lineage.img` - that's no where on there.

    And yes, you're temporarily flashing a custom recovery - flash to boot, then boot to recovery - it will be overwritten by the install of the ROM.

    And again, it is an A/B device - not suer where the confusion lies here.

    1 hour ago, acrux said:

    Temporary because the following updates already include boot.img.

    You made an inaccuracy here, according to the install page:

    
    fastboot flash boot <recovery_filename>.img

    It does not matter to which slot boot partition it is flashed if it is install and not a update.

     

    Yeah, like I said, that's the correct syntax.

    1 hour ago, SteffenWi said:

    oh, okay.

    But you need to know which slot it is to switch back to it to get to recovery and sideload the zip file? Or is the switch back no longer neccessary?

    Stop worrying about slots - we handle it all. Just follow the guide, flash recovery, boot to recovery, flash the ROM, format data, (optionally) reboot to recovery, install Google Apps.

    41 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.

    There's multiple ways to do these things - follow the wiki for official builds and things will go swimingly.

    • Like 1
  4. 1 hour ago, acrux said:

    Well, if somebody asked my opinion, then I'd put all efforts to get the official LineageOS for Pro1 out.

    It is always possible to tweak things later, make test builds and discuss them here etc...

    Yeah, sorry, we have to adhere to LineageOS's charter - and Wi-Fi dropouts definitely violate that - the good news here is that with our findings today, I'm confident we can ship ETA Soon^TM.

    19 minutes ago, Wheeljack said:

    For whatever reason I expected the statusbar change to involve some gigantic fonts - but it's just a few pixels bigger with no change to the font.

    Nah... totally reasonable modification. 👍

    And good to hear 🙂

    I tried like 10 different values and picked the one that was least intrusive to other users, and allowed those of us with early prototypes to interact with that area as well.

    Additionally, from a UX perspective - it doesn't warp test as badly on the curve now in landscape, so that's something.

    Untitled-1.psd

    OT: On the fingerprint image, if anyone has recommendations, I am attaching the PSD, feel free to iterate and improve - I'm not a designer in any sense of the word lol

    • Thanks 4
  5. 31 minutes ago, EskeRahn said:

    Well to give you some valid data I would have to flash a phone with Test20, without the VPN, wait a day or so, and then flash Test21, wait a day or so...

    So it will clearly be faster to see if someone else without VPN have a battery monitor installed, and see the same difference switching from Test20 to Test21.

    Additionally, can we get your greenify stats?

  6. 2 minutes ago, EskeRahn said:

    Well I have NetGuard active all the time, It will be a show stopper for Lineage for me if that no longer works.

    I understand - I want to get it working - I'm asking purely for testing purposes.

     

    If you can't I likely can try some stuff today.

  7. 8 hours ago, EskeRahn said:

    Despite the more aggressive power management, to my surprise the Test21 is substantially MORE power-hungry than Test20?!? see below from 3C All-in-one toolbox. (It looks similar on the rooted) - note also the x on the WiFi, Mobile data,  the screen dump is taken shortly after unlocking with fingerprint.
    Roughly at ratio 7:4 or a factor 175%

    And no, there aren't additional stuff running. I checked with Greenify and Android Assistant and only a few user and system apps I explicitly have white-listed are running

    LieneageTest20vs21.png

    This screenshot makes me think you have a persistent VPN (blockada or similar?) can you try without that? Recent QCACLD merge may be the issue - I've heard of issues with persistent VPN's after that.

  8. 7 hours ago, Wheeljack said:

    I see a lot of disconnects/reconnects with my WiFi as well. It's even happening while watching a YouTube video. Could this also be aggressive switching between 2.4 and 5GHz?

    Edit: I'm also getting a message to please disable airplane mode on my first call attempt after waking my phone.

    So, interesting test, can you make your wpa_supplicant_overlay.conf match this? https://github.com/LineageOS/android_device_motorola_nash/blob/lineage-17.1/wifi/wpa_supplicant_overlay.conf

     

    See if that helps anything.

  9. 17 minutes ago, EskeRahn said:

    A tiny bit of stick splitting. You got the full blown install and using guide for the ADB, and this is fine, but for the user just wanting to Install LineageOS, less will do it.
    They do not need to fiddle with the path, as long as they do the commands from the subdir the tree in the zip was unfolded to.

    So a more minimal (and thus less scary) version of the guide could be used for Install. That is just a link to the download, and then a few words on unfolding and running the commands from that folder, perhaps adding a sample path to the examples for the recovery and sideload flashes

    (I only read did not attempt the Build part)

    So, we add to $PATH, as our bug report system and most debugging relies on it being installed -- no point in expecting it to be in local dir/explicitly called by path each time.

    I'll make sure to do end-to-end tests of the install instructions and get the wiki up to par as needed - I work on Lineage's Wiki too pretty frequently.

    Also OT: Am the guy TDM is talking about above. Stoked to help out with the device.

    • Like 5
    • Thanks 5
×
×
  • Create New...

Important Information

Terms