MetropleX

  • a day ago
  • Joined Jun 10, 2022
  • Freedom is the right of ALL sentient beings.
    [Matrix]: @metroplex:m.metroplextech.net
    Twitter: https://twitter.com/Metr0pl3x
    Nostr: npub1gd3h5vg6zhcuy5a46crh32m4gjkx8xugu95wwgj2jqx55sfgxxpst7cn8c

  • Checkerrr please flash the 8a once more and using the tablet take a video of the device booting into a fresh flashed unaltered default state to demonstrate the issue to help us support you.

    If you don't feel comfortable posting a link here or using a video platform to host. Register on Matrix and join our Matrix support room to send it to me there.

    If you can grab them sending it along with the crash logs you can save using the notifications that appear will be immensely useful.

    Your issue is not common and a cursory search across our community portals will show that your 1 in over 250k+ users is not mentioned where there is no underlying issue be it hardware or user configured especially if all steps of the install process are complete properly with the device locked.

    We'll move forward from there and I am more than happy to try facilitate a resolution.

    • As above, @collector it doesn't make sense to view OS components the way you are. This is not a third party app, it's part of the OS.

      The permissions being listed only appears in the permission manager because this component is implemented with the app runtime. The lower level parts of the OS don't appear there. Trying to disable apps or permissions for system components based on a high and narrow interpretation doesn't make sense when it would break more than what you perceive it to represent.

      Camera would be included in the dialer for example for use of VILTE (VIdeo over LTE) where provisioned. You can see the provision toggle under *#*#4636#*#* then Phone Info as just one example where the system would handle the video and not a third party app.

      As for location, this is part of implementing supporting for carriers and cellular. This component being able to work with information about the cellular network and carrier counts as being location data which requires the Location permission.

      It's the implementation of https://en.wikipedia.org/wiki/IP_Multimedia_Subsystem

      Examples of global standards based on IMS are MMTel which is the basis for Voice over LTE (VoLTE), Wi-Fi Calling (VoWIFI), Video over LTE (ViLTE), SMS/MMS over WiFi and LTE, USSD over LTE, and Rich Communication Services (RCS)

    • d9780 yes

      SETTINGS>PRIVACY>TOGGLE OFF ALLOW SENSORS PERMISSION BY DEFAULT

      You can also go to the same Privacy Panel and then select Permission Manager then finally Sensors.

    • androidin it's possible it has a memory corruption issue. (Most likely if running on an outdated unity engine version.) You can see if this is the case by going to the games App Info panel and toggling on Exploit Protection Compatibility Mode

      Please report back.

      • This forum is not the place (however understandable as to why it might have seemed a good place to advertise) for people to be taking part in online commerce.

        There is no buyer protection nor seller verification offered. There are numerous online marketplaces to list this with the above mentioned warranties etc

        Thankyou for understanding.

      • Cleaned up and locked. Original inflammatory post edited.

        Benefit of the doubt no negative intent was behind the phrasing just better for the sake of maintaining a cordial atmosphere.

      • csis01 no it doesn't, not in the way people will determine from that reply.

        The verified boot bootflow only works up until seeing the Orange Warning when left unlocked. It is specifically why the following text is displayed:

        The boot loader is unlocked and software integrity cannot be guaranteed. Any data stored on the device may be available to attackers. Do not store any sensitive data on the device.

        Verified Boot works for the full boot flow ONLY when the the Bootloader is LOCKED either with stock or when an alternate OS custom root of trust has been established.

        • When trying to connect using Orbot, from where it says More... tap that what errors if any does the Log show when you tap the option? Both with and without bridges?

        • DyzelZ Hi Dyzel, thankyou very much for your positive appraisal of GrapheneOS and we certainly appreciate the feedback.

          However as this particular experience is particular to your personal circumstances I am going to lock the thread. We have passed your feedback along.

          If you wish to discuss this further please reach out to me via DM on Matrix:
          https://matrix.to/#/@metroplex:m.metroplextech.net

        • Just trying to troubleshoot:

          1. You've not got Do Not Disturb Active eg caught the toggle or have Bluetooth connected inadvertently?

          2. Boot to Safe Mode and check no third party app inteference:

          3. Power down the phone.

          4. Press the power button. After a few seconds (on Google logo) hold the phone's volume down button. Continue to hold it down until you see Safe mode on the screen.

          5. Seemingly not an isolated issue quick search pulls this up:
            https://www.reddit.com/r/GooglePixel/comments/od2bie/no_sound_on_pixel_4a_5g/
            Possible solution contained therein.

          6. Factory Reset

          Just some things to consider in the interim.

          • Can you restart the device and when you do so grab a bug report:

            SETTINGS>SYSTEM>DEVELOPER OPTIONS>BUG REPORT>INTERACTIVE

            Then open an issue:
            https://github.com/GrapheneOS/os-issue-tracker/issues

            State you have the report and ask where/who to submit it to.

            Then link to the issue here so that if anyone else turns up with the same issue across our portals they can find their way there.

            As we haven't seen or heard anyone else with the issue during internal testing and during the alpha/beta staged release process for now it seems isolated. However doing the above will hopefully shed light on the problem and possible resolution.

          • I have provided these details in the testing channel over on Matrix, however in the interim if you want to try something else, you can install sandboxed play services in owner and attempt to reenable the SIM that way and let me know the outcome.

            • Fulgrim Hmmm do you have sandboxed play installed or did you remove it once eSIM was activated?

              • Fulgrim have you still got DSDS (Dual SIM Dual Standby) enabled?

                Dial *#*#4636#*#* and check for me.

              • DarthData no capture it just after it happens, at least if it does happen again you'll know it's a persistent issue.

              • Honestly, there are so many screen protectors of varying types and quality, all installed with varying degrees of success and skill, it would be hard for GrapheneOS to offer support, hence the change from General to Off-Topic.