7-Eleven Fuel App Watch - Nationwide

alvian on 20/01/2022 - 17:24
Last edited 06/04/2024 - 14:09 by 3 other users

This thread serves to let everyone know how much you have saved on your 7/11 fuel app. Please see the archived thread (January 2017 - January 2022) for previous discussions.

Step 1: Subscribe to this thread to get email updates. You can change your subscription settings in your Ozbargain account to enable more/less email updates.

Step 2: Upon filling up simply fill in the details in this format:

  • NAME OF 7/11 STORE
  • PETROL TYPE
  • PETROL PRICE

Example:

  • Richlands QLD
  • ULP
  • 111.9/litre

Step 3: Upvote the comment if you found it helpful

Note: OzBargain are not responsible for your use of the 7/11 app and you should abide by all terms stipulated by the app. This thread's content is not endorsed by OzBargain.

Cheapest prices:

Other Useful Resources:

Further Info/Tips

Working Methods

iOS

Android

Credits to master131

Mod: Please do not ask for vouchers. Obtain the fuel lock yourself or make a request in the Wanted Classifieds.

Automotive Fuel

Related Stores

7-Eleven
7-Eleven

Comments

        • 0HDAM on 14/11/2022 - 10:06

          I have followed that previously through google search instruction, there is no such thing as Developer mode now. I am on ios16.1.1 as of this morning (updated to ios16.1 last week, which also didnt have developer mode settings), so not sure if there is a difference to ios6. No such thing as share with app developers or developer mode anymore, that I can find anyways.

          • jv on 14/11/2022 - 10:09

            @0HDAM: yes there is.

            I set it on mine last night

            I'm also on 16.1.1

            screenshot : https://files.ozbargain.com.au/upload/14180/99441/ios16.jpg

            • 0HDAM on 14/11/2022 - 10:18
              +1

              @jv: AHHH, I found it. Cheers JV.

              Had to turn on Share Iphone & Watch Analytics before you can see that option =.=

              Mine looks different from yours. I dont have anything called developer mode under the mains ection. I have to click into Analytics & Improvements and turn on Share Iphone & Watch Analytics and then Share with Developer appears. Odd cause we have the same ios.

              • jv on 14/11/2022 - 10:22

                @0HDAM:

                Mine looks different from yours

                Might be device dependant? I'm using an XS Max

  • KayaToast on 13/11/2022 - 13:20

    Anyone else having issues with their chopper on android since the app went down for maintenance yesterday? Been receiving E01 errors when trying to lock in, can't see anything wrong with safetynet. Tried reinstalling everything but now receiving a02 errors :(

    • qwerty40777 on 13/11/2022 - 13:47

      A02 over here too, tried creating a new account and the same issue

      • Nexald on 13/11/2022 - 15:44

        A02 when not flying.

        • Nexald on 13/11/2022 - 23:34
          +2

          Managed to fly to the desired destination just now, with no A02 error.

          • ranmalynx on 14/11/2022 - 00:41

            @Nexald: Thanks! Confirmed! I was able to fly as well. No errors.

    • ranmalynx on 13/11/2022 - 16:09

      A02 errors for me too after the maintenance. Tried re-installing the app and got E01 errors. Tried troubleshooting and got back to A02 errors 😢

  • neu11 on 13/11/2022 - 18:46

    E01 error on android as well when trying spoofed and unspoofed as well. bug/error or shadow ban based on some kind of device/uuid?

    • neu11 on 14/11/2022 - 06:56

      managed to lock while off wifi earlier, so 🤷‍♀️

  • ranmalynx on 14/11/2022 - 00:44
    +1

    Those who are getting A02/ E01 errors, try again now. I was able to lock in just now. Thanks to @Nexald for the update.

    • AznLancelot on 14/11/2022 - 18:26

      Can confirm. All good and working now. Cheers bud

  • dontpanic on 15/11/2022 - 02:53
    +25

    ANDROID STUDIO CHOPPER GUIDE (macOS/Linux/Windows)

    OK, first off, these instructions may look really long and daunting, but I promise it’s actually quite easy and simple. Once you have all the tools downloaded, the whole process takes about 5-10 minutes.

    This is basically an update to my previous Nox guide, but rather than using that horrible bloated software and all the spammy crap that comes along with it, we can now use a clean, cross platform solution that should remain functional for as long as this Magisk/Zygisk/LSposed method remains viable on normal rooted phones. Yay.

    I don't have a rooted phone to be able to test this on, but I would assume that if you were able to root your phone and install Magisk, you could follow the instructions at PART 3 to get it working - it would be a lot simpler than the Smali Patcher route.

    PART 1 - Setting Up Android Studio

    • Download Android Studio
    • Install it.
    • When running it for the first time, select the Standard Install option. (If you have a previous install, you might want to check that you've installed ADB by following the instructions in Additional Notes at the end of this guide.)
    • Open Android Studio.
    • On the Welcome Screen, click on “More Actions” under the “New Project/Open” buttons.
    • Select “Virtual Device Manager”.
    • In the new Device Manager window, click on “Create Device”.
    • For our purposes here, we will use a Pixel 4 because it is the most recent phone that includes the Google Play Store (for those who might want it) - but if you have no need for it, or don't want to download another 1GB, or if this guide gets old and you need to use a newer device//Android Version for My 7-Eleven app compatibility) feel free to choose something newer, or just use the preloaded Pixel 3a. But please note that if you choose to use a different device, you will have to modify some of the script commands later in the guide - refer to PART 2D for instructions.
    • On the next screen you can choose the version of Android you want to use - I have successfully tested both R (API 30) and Tiramasu (API 33). For our purposes we will use Tiramasu (API 33) because it is the most recent and should give us longer compatibility with the My 7-Eleven app. If you’re going off-guide and use a different phone and version, pay attention to whether your version is x86 or X86_64 or arm64-v8a, and whether it includes Play Store or not, as you will need this info a bit later on.
    • Hit the download button next to the version you want and once the download is finished (about 1GB) hit “Next”.
    • Confirm your configuration and hit “Finish”.
    • Your device should now be listed in the Device Manager.
    • Launch your device by hitting the “Play” icon next to it. You will need to have your new device up and running as we go through the next steps.
    • With your device now running, we’re going to install Magisk via a nifty little script from Github called RootAVD
    • Download the script (the link is currently on the GitHub page where it says "Click" under "Install Magisk | Download rootAVD via")
    • We're now going to move on to PART 2.
    • If you're using macOS or Linux on an Intel/AMD based machine, use PART 2A.
    • If you're using macOS on a Mac with an M1 or M2 processor use PART 2B.
    • If you're using Windows with an Intel/AMD processor, use PART 2C.
    • If you're using something else, you're on your own and you'll have to work it out for yourself.

    PART 2A - macOS (Intel) / Linux (Intel/AMD)

    (If any of the following instructions confuse you, I suggest watching the video on the Github link so you have a clearer idea of what we’re doing)

    • Open Terminal

    • Type:

      cd [location of rootAVD-master directory] <—— You can just drag the folder on to terminal to get the location

    • If you are following the guide and using the Pixel 4 + Tiramasu combo, you can use the commands below (if not, please refer to PART 2D).

    • Paste the following command and hit Enter:

      ./rootAVD.sh ~/Library/Android/sdk/system-images/android-33/google_apis_playstore/x86_64/ramdisk.img

    • You will probably get an output like this:

      [ ! ] and we are NOT in an emulator shell
      [ * ] Set Directorys
      [ - ] Test if ADB SHELL is working
      [ ! ] ADB is not in your Path, try to
      export PATH=~/Library/Android/sdk/platform-tools:$PATH

    • Copy the last line of your output (i.e. export PATH=~/Library/Android/sdk/platform-tools:$PATH), paste it and hit Enter.

    • Then enter this command again:

      ./rootAVD.sh ~/Library/Android/sdk/system-images/android-33/google_apis_playstore/x86_64/ramdisk.img

    • Once the script finishes successfully, your device should shutdown after a few seconds. We will now progress to PART 3.

    PART 2B - macOS (Apple Silicon)

    (If any of the following instructions confuse you, I suggest watching the video on the Github link so you have a clearer idea of what we’re doing)

    • Open Terminal

    • Type:

      cd [location of rootAVD-master directory] <—— You can just drag the folder on to terminal to get the location

    • If you are following the guide and using the Pixel 4 + Tiramasu combo, you can use the commands below (if not, please refer to PART 2D).

    • Paste the following command and hit Enter:

      ./rootAVD.sh ~/Library/Android/sdk/system-images/android-33/google_apis_playstore/x86_64/ramdisk.img

    • You will probably get an output like this:

      [ ! ] and we are NOT in an emulator shell
      [ * ] Set Directorys
      [ - ] Test if ADB SHELL is working
      [ ! ] ADB is not in your Path, try to
      export PATH=~/Library/Android/sdk/platform-tools:$PATH

    • Copy the last line of your output (i.e. export PATH=~/Library/Android/sdk/platform-tools:$PATH), paste it and hit Enter.

    • Then enter this command again:

      ./rootAVD.sh ~/Library/Android/sdk/system-images/android-33/google_apis_playstore/x86_64/ramdisk.img

    • Once the script finishes successfully, your device should shutdown after a few seconds. We will now progress to PART 3.

    PART 2C - Windows (Intel/AMD)

    (If any of the following instructions confuse you, I suggest watching the video on the Github link so you have a clearer idea of what we’re doing)

    • Open CMD

    • Type:

      cd [location of rootAVD-master directory]

    • If you are following the guide and using the Pixel 4 + Tiramasu combo, you can use the commands below (if not, please refer to PART 2D).

    • Paste the following command and hit Enter:

      rootAVD.bat %LOCALAPPDATA%\Android\Sdk\system-images\android-33\google_apis_playstore\x86_64\ramdisk.img

    • You will probably get an output like this:

      [ * ] Set Directorys
      [ - ] Test if ADB SHELL is working
      [ ! ] ADB is not in your Path, try to
      Set PATH=%LOCALAPPDATA%\Android\sdk\platform-tools;%PATH%

    • Copy the last line (i.e. Set PATH=%LOCALAPPDATA%\Android\sdk\platform-tools;%PATH%), paste it and run it.

    • Enter this command again:

      rootAVD.bat %LOCALAPPDATA%\Android\Sdk\system-images\android-33\google_apis_playstore\x86_64\ramdisk.img

    • Once the script finishes successfully, your device should shutdown after a few seconds. We will now progress to PART 3.

    PART 2D - Choosing a Different Device

    Now if you’ve chosen a different Phone/Version of Android, the above instructions will be the same, BUT your ramdisk.img file may be different. You’ll need to select the proper command for your version.

    We are assuming that you have followed the PART 2A/B/C steps up until the point that it told you to come here

    • In macOS, type:

      ./rootAVD.sh ListAllAVDs

    • In Windows, type:

      rootAVD.bat ListAllAVDs

    • In macOS you will get you an output like this:

      ./rootAVD.sh ~/Library/Android/sdk/system-images/android-33/google_apis_playstore/x86_64/ramdisk.img
      ./rootAVD.sh ~/Library/Android/sdk/system-images/android-33/google_apis_playstore/x86_64/ramdisk.img DEBUG PATCHFSTAB GetUSBHPmodZ
      ./rootAVD.sh ~/Library/Android/sdk/system-images/android-33/google_apis_playstore/x86_64/ramdisk.img restore
      ./rootAVD.sh ~/Library/Android/sdk/system-images/android-33/google_apis_playstore/x86_64/ramdisk.img InstallKernelModules
      ./rootAVD.sh ~/Library/Android/sdk/system-images/android-33/google_apis_playstore/x86_64/ramdisk.img InstallPrebuiltKernelModules
      ./rootAVD.sh ~/Library/Android/sdk/system-images/android-33/google_apis_playstore/x86_64/ramdisk.img InstallPrebuiltKernelModules GetUSBHPmodZ PATCHFSTAB DEBUG
      ./rootAVD.sh ~/Library/Android/sdk/system-images/android-33/google_apis_playstore/x86_64/ramdisk.img AddRCscripts

    • In Windows you will get you an output like this:

      rootAVD.bat %LOCALAPPDATA%\Android\Sdk\system-images\android-33\google_apis_playstore\x86_64\ramdisk.img
      rootAVD.bat %LOCALAPPDATA%\Android\Sdk\system-images\android-33\google_apis_playstore\x86_64\ramdisk.img DEBUG PATCHFSTAB GetUSBHPmodZ
      rootAVD.bat %LOCALAPPDATA%\Android\Sdk\system-images\android-33\google_apis_playstore\x86_64\ramdisk.img restore
      rootAVD.bat %LOCALAPPDATA%\Android\Sdk\system-images\android-33\google_apis_playstore\x86_64\ramdisk.img InstallKernelModules
      rootAVD.bat %LOCALAPPDATA%\Android\Sdk\system-images\android-33\google_apis_playstore\x86_64\ramdisk.img InstallPrebuiltKernelModules
      rootAVD.bat %LOCALAPPDATA%\Android\Sdk\system-images\android-33\google_apis_playstore\x86_64\ramdisk.img InstallPrebuiltKernelModules GetUSBHPmodZ PATCHFSTAB DEBUG

    • There may be more than one set of these, depending on how many Android versions you’ve downloaded.

      To know which one to use, you will need to know the Android API version number you are running, whether your install is x86 or x86_64 or arm64-v8a, and whether or not your install includes Play Store.

      The structure will look something like this and you will need to choose the options in the parentheses that match your install:

      Android/sdk/system-images/[Android API Version]/google_apis[Play Store]/[Installed Processor Architecture]/ramdisk.img

      For instance, a Pixel 6 Pro install of Android Tiramasu (API 33) WITHOUT Play Store on an Intel/AMD based machine (x86_64) will look like:

      macOS:
      ./rootAVD.sh ~/Library/Android/sdk/system-images/android-33/google_apis/x86_64/ramdisk.img

      Windows:
      rootAVD.bat %LOCALAPPDATA%\Android\Sdk\system-images\android-33\google_apis\x86_64\ramdisk.img

      Whereas the install for a Pixel 4 with Android Tiramasu (API 33) WITH Play Store on an Intel/AMD based machine (x86_64) will look like:

      macOS:
      ./rootAVD.sh ~/Library/Android/sdk/system-images/android-33/google_apis_playstore/x86_64/ramdisk.img

      Windows:
      rootAVD.bat %LOCALAPPDATA%\Android\Sdk\system-images\android-33\google_apis_playstore\x86_64\ramdisk.img

      An install for a Pixel 4 with Android R (API 30) WITH Play Store on an Intel/AMD based machine (x86) will look like:

      macOS:
      ./rootAVD.sh ~/Library/Android/sdk/system-images/android-30/google_apis_playstore/x86/ramdisk.img

      Windows:
      rootAVD.bat %LOCALAPPDATA%\Android\Sdk\system-images\android-30\google_apis_playstore\x86\ramdisk.img

      And an install for a Pixel 4 with Android Tiramasu (API 33) WITH Play Store on an Apple Silicon Mac (arm64-v8a) will look like:

      macOS:
      ./rootAVD.sh ~/Library/Android/sdk/system-images/android-33/google_apis_playstore/arm64-v8a/ramdisk.img

    • Once you have found the correct command for your device, copy it and resume the relevant PART 2 instructions above, swapping out the ramdisk.img commands in the instructions for the one you just copied.

    PART 3 - Installing Apps

    • In Android Studio Device Manager, click on the three dot menu button next to your device and select "Cold Boot Now".
    • Once booted, click, hold and drag up anywhere on the device Home Screen to reaveal the App Drawer.
    • If you're NOT using a Mac with Apple Silicon, skip to the next step. If you ARE, you will probably have an app called Alpha with the Magisk logo and an app called Magisk with a generic system logo. Select Magisk and you will be prompted to "Upgrade to full Magisk". Hit "OK". You will prompted to allow the app to install apps. Click on "Settings" on the prompt and then enable "Allow from Source". A new prompt will ask you if you want to update - click "Update". If it's successful, your Magisk app will now have a proper logo.
    • Open Magisk.
    • A popup will tell you that it "Requires Additional Setup" - hit "OK" and let the device reboot.
    • Once rebooted, go back into Magisk, hit the Settings cog icon, and enable Zygisk.
    • Exit the Settings page and hit the circular arrow next to the Settings icon and select Reboot.
    • On your computer, download LSPosed Zygisk (note: you want the Zygisk release, not Riru)
    • Drag the downloaded ZIP to your Android device - it will copy the file to the device storage.
    • In Magisk, go to the modules tab and select "Install from storage".
    • Select the ZIP file from your "Downloads" folder (accessible from the Hamburger menu top left).
    • After the install, reboot.
    • When the phone boots up again it should prompt to place a LSPosed icon on your Home Screen - hit OK (if you cancel this popup or delete the shortcut, just restart the device and you will be prompted to place it back).
    • On your computer, download Hide Mock Location and install by dragging the APK to your device.
    • Download and install My 7-Eleven by dragging the APK to your device (you can also do this via the Play store on the device if you prefer)
    • Download and install Fake GPS by dragging the APK to your device (you can also do this via the Play store on the device if you prefer)
    • Open the LSPosed Manager (that was just placed on your Home Screen), go to the modules tab and select Hide Mock Location, enable it and select My 7-Eleven.
    • Go to your device Settings (via App Drawer or dropping down the notification shade twice)
    • Go to "About emulated device"
    • Scroll down to Build Number and click it repeatedly until it says "You are a now a Developer".
    • Go back a level in Settings and use the search bar to search for "Select Mock Location App"
    • It should now take you to that option - click on it and select "Fake GPS"
    • Reboot (via Magisk or dropping down the notification shade twice to reveal the Power Menu button)
    • Once rebooted, open Hide Mock Location and check that it is activated.
    • In your emulated Android Device, open up Chrome and go to Refinery.fyi (for future ease of use, add it to your Home Screen by clicking on the 3-dot menu icon and selecting "Add To Home Screen")
    • Click on the fuel type you want and it should copy the co-ordinates.
    • Open Fake GPS, go to the hamburger menu and select "Go To", and paste the GPS co-ordinates (you can bring up the paste dialog by long pressing/clicking in the text field) and hit the green button (bottom left) to mock your location.
    • Open My 7-Eleven, login, and lock your price in.

    PART 4 - I Want a Squadron of Choppers!

    Need more than one chopper? Feel like locking in a price every day of the week? Easy peasy.

    • First, fire up some Wangner
    • Secondly, get your device set up exactly how you want it, so you won't have to set it up again multiple times for each new device.
    • Now, go to Device Manager in Android Studio, click on the three dots next to your device and select "Duplicate".
    • That's it. All done. Just start up the new device, set your fake location, and log in to 7/11 with a new account
    • Just a quick note if you're setting up new accounts - there's no need to set up new emails for each new account - you can create a new account with just one Gmail account by inserting a full stop into the email address - i.e. [email protected] can be registered again and again by changing it to [email protected] or [email protected] or [email protected], etc, etc). Don't know if this works with other providers, but honestly, you should be using a throwaway Gmail for this anyway.
    • Repeat as many times as needed.
    • For ease of use I've labeled each of my devices in the Device Manager with the email account that I'm using in My 7-Eleven on that particular device.

    ADDITIONAL NOTES

    • If you're using a newer Pixel device, it probably will have Gesture Navigation as default. The Back, Home and App Switcher buttons should be in the tool panel next to your device. Or you can change the navigation to "3 Button" in the settings (search "Gestures")
    • Scrolling with a mouse is a bit buggy (it seems to click on things when scrolling) - best to click and drag instead.
    • The My 7-Eleven app is buggy as hell. If it doesn't load or doesn't show your spoofed location, close the app (use the app switcher and drag the app off screen to close it) and restart it. Or just restart the device.
    • These are the files that work currently for this guide (I can't guarantee that future versions will work):

    Android Studio Dolphin | 2021.3.1 Patch 1
    LSPosed-v1.8.5-6649-zygisk-release.zip
    Magisk 25.2 (25200) (33)
    Hide Mock Location v2.0.9
    My 7-Eleven 2.17.4
    Fake GPS v2.1.2

    • If for whatever reason you don't have ADB installed, do the following:

    On the Android Studio Welcome Screen, click on “More Actions” under the “New Project/Open” buttons.
    Select "SDK Manager".
    Click on the "SDK Tools" tab (note: it’s not in the side panel, it’s in the top middle of the window next to “SDK Platforms”)
    If “Android SDK Platform-Tools” isn’t installed, tick the box next to it and hit “Apply”, this will install ADB which is needed for our script later.

    • skid on 15/11/2022 - 07:08

      Legend

    • shadowfax1007 on 15/11/2022 - 09:26

      Brilliant work. Will test it tomorrow.

      I see there is a PortableApps version of Android Studio online. I wonder if this would work in a portable environment. Would be great to have it on a USB in my wallet so I can lock in a work, friends houses etc.

      • dontpanic on 15/11/2022 - 10:55

        I reckon the only issue would be if ADB is installed with a portable version.

        You may need to keep the ADB files on the USB and change this part in the script to point to it:

        PATH=%LOCALAPPDATA%\Android\sdk\platform-tools;%PATH%

        PATH=~/Library/Android/sdk/platform-tools:$PATH

        Not sure though… Would need to test.

      • cwongtech on 15/11/2022 - 11:05

        I see there is a PortableApps version of Android Studio online. I wonder if this would work in a portable environment. Would be great to have it on a USB in my wallet so I can lock in a work, friends houses etc.

        You could alternatively share your Android device over the internet via a remote connection service like AnyDesk or TeamViewer, which will allow you to access the remote chopper from anywhere (install AD on the Android VM, connect from your mobile or laptop to target), with Shizuku and AppOps set up to automatically press "Accept Connection" every time.

        This is what I do with my fleet of 9 (except mine are all powered via physical phones) but requires the devices (in this case will be a host computer to run Android Studio) being online permanently (electricity costs).

        The only issues that come to mind with this setup is IP tracking from 7/11 side, make sure the host comp has access to either:
        - A VPN
        - Mobile hotspot (IP address changes with a disconnection to tower, i.e. airplane mode toggle on/off)

        @dontpanic
        What's the resource drain on Android Studio running and each instance of Android being started?
        Are you able to run multiple Android Devices in Android Studio concurrently?

        • dontpanic on 15/11/2022 - 14:47

          You can definitely run multiple VMs, but I think 9 might be pushing the limits, especially if you wanted to leave them running.

          Rather than remote desktoping into each VM, you could just remote into the PC and fire up an individual VM instance - that would save on resources.

          For IP tracking, I guess you could set up a VPN on each VM, so that when you load it up it has a different IP. Do they all need to be Australian IPs?

          • cwongtech on 15/11/2022 - 15:38

            @dontpanic:

            For IP tracking, I guess you could set up a VPN on each VM, so that when you load it up it has a different IP. Do they all need to be Australian IPs?

            Regarding IPs, I'm not sure if they need to be Aus IPs, but for the purpose of ensuring 7/11 can't track us.. I'm sure a foreign IP will be one of the easiest flags to filter for accounts to banhammer/G09.

            You can definitely run multiple VMs, but I think 9 might be pushing the limits, especially if you wanted to leave them running.

            That's what I'm doing at the moment across 2 comps powering 5 Windows VMs connected and mirroring 5 physical android phones, 4 standalone android phones. The windows VMs and standalone phones are remotely connectable.
            I haven't used Android VMs directly at this stage yet.

            Rather than remote desktoping into each VM, you could just remote into the PC and fire up an individual VM instance - that would save on resources.

            I mean as a method to share access to a fleet (for your friends or whatnot). In this case, you'd want to provide access to the Android Instances, not the remote PC hosting the Android Instances.

            • dontpanic on 15/11/2022 - 17:16

              @cwongtech:

              I mean as a method to share access to a fleet (for your friends or whatnot). In this case, you'd want to provide access to the Android Instances, not the remote PC hosting the Android Instances.

              Just fired up 6 Android VMs and whilst it does seem to initially eat up a heap of processing power, it looks like they eventually idle and pull minimal amount of resources. Unfortunately the VMs appear individually in my dock/app switcher, so it's pretty cluttered visually unappealing to have this running on a daily driver PC (unless I can find a way to hide them).

              I was able to successfully remote login and control the VMs using Teamviewer/AnyDesk - however you have to ensure that you return to the TV/AD software and keep it open on the VM before you exit your remote connection, otherwise it will go offline. The only other workaround would be to find a way to automatically open the app every 5 minutes or so - there's probably a way to do that with root enabled.

              with Shizuku and AppOps set up to automatically press "Accept Connection" every time.

              Can you give some more detailed instructions on this? This is a key part of getting remote functionality working, and I'm not familiar with these apps.

              • cwongtech on 15/11/2022 - 17:47
                +1

                @dontpanic:

                Unfortunately the VMs appear individually in my dock/app switcher, so it's pretty cluttered visually unappealing to have this running on a daily driver PC (unless I can find a way to hide them).

                Part of my fleet of nine run on secondary/unused/almost dead computers
                The backend, one of the laptop running VMs with two partner physical phones
                The front-end

                I was able to successfully remote login and control the VMs using Teamviewer/AnyDesk - however you have to ensure that you return to the TV/AD software and keep it open on the VM before you exit your remote connection, otherwise it will go offline. The only other workaround would be to find a way to automatically open the app every 5 minutes or so - there's probably a way to do that with root enabled.

                In my physical phones that power my fleet - I had ensure battery optimization was turned off for both the AnyDesk and AnyDesk Plugin.

                Can you give some more detailed instructions on this? This is a key part of getting remote functionality working, and I'm not familiar with these apps.

                Once you've disabled the battery optimization thing that may disable AD/TV from turning off..

                Try the below
                1) On Chopper phone, grab AnyDesk, install it, start it, and grab the relevant AnyDesk Plug-in for that phone
                2) Download Shizuku, enable the rooted-mode to automatically start
                3) Download AppOps
                4) On main phone/computer, grab AnyDesk, then attempt to connect to Chopper Phone. Go to chopper phone to approve connection, disconnect (point of this is to force a few settings to show in AppOps)
                5) In Chopper phone, go to AppOps, AnyDesk, and allow permissions in the AppOps settings for AD. This will automatically approve any incoming connection without having to manually approve the connection request each time

                • dontpanic on 15/11/2022 - 18:47

                  @cwongtech:

                  In my physical phones that power my fleet - I had ensure battery optimization was turned off for both the AnyDesk and AnyDesk Plugin.

                  What version of Android are you running?

                  It doesn't seem to work on Tiramasu if the AD/TV plugin app is minimised, even with Battery Optimisation. It HAS to be the foreground app in order to be able to connect. As soon as you minimise, the device goes offline.

                  It just means that you have to remember to go back to the app on the VM BEFORE you exit the remote session. Annoying, but not a total deal breaker.

                  Try the below

                  Thanks, I'll give it a go.

                  • cwongtech on 15/11/2022 - 19:04

                    @dontpanic:

                    What version of Android are you running?

                    They range from LineageOS 17/18 (Android 10 was my minimum requirement) to Android 12/LineageOS equivalent, depends what was available on each device.

                    I haven't dared to go any newer as a whole bunch of users (friends and family) rely on my fleet being operational.

                    In all honesty I didn't even know Android Tiramisu was Android 13 til your post

                    • dontpanic on 15/11/2022 - 22:47

                      @cwongtech: I'm only referring to it as Tiramasu because that's how it's listed in Android Studio and I didn't want to cause confusion.

                      I might have a go installing an older version of Android and see if I can get remote control of the VM working better.

                    • dontpanic on 15/11/2022 - 23:12

                      @cwongtech: Seems I was using the wrong Teamviewer App. I was using Teamviewer QuickSupport when what I needed was Teamviewer Host. Now just have to solve the pesky pop-up.

                      • cwongtech on 16/11/2022 - 00:13

                        @dontpanic: Try AnyDesk as an alternative - you just need the Plugin to allow remote access. Without the AnyDesk plugin, you will be able to connect as view-only access.

                        • dontpanic on 16/11/2022 - 00:33

                          @cwongtech: I've tried it, but I can't seem to be able to connect unless the AD app is running in the foreground. I'm trying to make this as foolproof as possible for remote access. Teamviewer Host runs in the background and lets me log in without having to do anything on the VM end. Are there any further settings that I'm missing with AD?

                          • cwongtech on 16/11/2022 - 00:36

                            @dontpanic: Did you follow the App Ops for the permissions for AD?

                            Once you connect, the target Android Device should show which profile you want.
                            Under Settings>Security>Permission Profiles you may need to set up "Unattended Access" and set a password first

                            • dontpanic on 16/11/2022 - 00:40

                              @cwongtech: Yeah, went through all that. But if I have the VM device just sitting there on the home screen, I can't access it remotely. The only way it connects is if AD is running in the foreground on the VM. With TV Host, I can establish a connection no matter what the VM is doing - on the home screen, with another app loaded, whatever…

    • WebWombat on 20/11/2022 - 16:28

      All seemed to be going fine installation wise until I realized my virtual device had not internet access. Kinda needed for the 7/11 app.
      Then found no virtual device had any internet access.
      Much googling and fiddling with DNS addresses, IP addresses and various other spells and potions and still no internet access on virtual machines.
      Tried a different computer. Nope.

      • dontpanic on 20/11/2022 - 22:57

        Weird. I haven't encountered that on the three different machines I've installed it on. Must be something unique to your setup - maybe firewall related?

        • WebWombat on 21/11/2022 - 13:54

          Tried two different machines, and also tried hotspotting internet off my phone to avoid internal routers etc. No dice.
          BUT in the SDK Manager using the Test Connection button, connects to external web addresses with no problem.
          Come on GoogleFu, don't let me down now…..

          • dontpanic on 21/11/2022 - 16:19

            @WebWombat: Windows? Mac? Linux?

            Do you have any third party apps installed that might limit connections? Little Snitch? Lulu? Some sort of firewall or anti-virus app? Check your security settings?

            It works for me on both Mac (MacBook Air M1, MacBook Pro Intel, Hackintosh) and PC (Intel). There has to be something unique to your setup that is causing this.

            • WebWombat on 21/11/2022 - 16:26
              +4

              @dontpanic: Nope, bare bones Pixel 4 Tirimasu as per the directions. Nothing else.
              Thought it might be an issue with something that happened through all the installs etc so went back to new clean AVD.

              Found it's a Chrome issue though. Other internet apps like YouTube work, just not Chrome (which apparently the 7/11 App uses for authentication).
              Installed another browser and can browse internet fine. So looks like Chrome.

              Going down that rabbit hole now…

              Edit: Fixed.
              If anyone else has this problem, do this

              In a text editor (e.g Notepad) I write these two lines.

              Vulkan = off
              GLDirectMem = on

              save as advancedFeatures.ini
              in the ~/.android folder

              restart emulator. All fixed (for me at least)

              • dontpanic on 21/11/2022 - 18:47

                @WebWombat: Weird. Those two lines relate to graphics, so I wonder why it affected your network access. Was it an issue of chrome not having internet, or that it just didn't load? What graphics card do you have?

                • WebWombat on 22/11/2022 - 08:42

                  @dontpanic: Chrome seemed to load and open OK, BUT if you tried to go to a website or do a search it would freeze.
                  No graphics card. Both computers have integrated graphics (one laptop, one NUC)

              • iamnotafish on 29/11/2022 - 10:47

                @WebWombat: Thanks! I had the same issue as you, and your fix worked for me.

              • Underlord on 07/12/2022 - 15:09
                +1

                @WebWombat: This fixed my issue of Chrome freezing when I attempted to login. Cheers!

              • kosantov on 08/12/2022 - 21:13

                @WebWombat: I just wanted to add that this helped fix a glitchy display issue I had with the AVD emulator.

                Every time I would have the chopper running, it would cause the login screen for 7/11 to distort/warp/etc. Thanks to this solution I can actually run a smooth experience with the AVD.

                For anyone that is missing their advancedFeatures.ini (like I was), just create a new one in the folder specified and it should be good. Additionally, for Windows users, the directory should be C:\Users\%USERNAME%/.android (YMMV)

              • jobargain on 09/08/2023 - 17:43

                @WebWombat: Thank you for your fix, it worked for me

    • LittleMIssPanda on 26/11/2022 - 20:47

      Thanks for the guide, I'm near the end but when I double click LSPosed on the home screen it doesnt load! Definitely used the zygisk release, any pointers?

      • dontpanic on 29/11/2022 - 02:27

        Hmmmm… Not sure.

        Have you tried doing a cold boot / restart of the emulator?

        If that doesn't work, maybe try building a second emulation and see if the problem is recreated.

    • Vavoom on 05/01/2023 - 11:58

      I just went through this process and could only find one mistake in your extremely excellent instructions:

      Open Fake GPS, go to the hamburger menu and select "Go To", and paste the GPS co-ordinates (you can bring up the paste dialog by long pressing/clicking in the text field) and hit the green button (bottom left) to mock your location.

      The play button seems to be on the bottom right now but anyone with half a brain can work that out.

      For others wanting to follow this process, I encountered a few errors in dragging APKs across to the emulator. adb errors and parse string stuff. If that happens to you simply shut down the emulator and restart Android Studio. Should clear it all up.

      When logging into the My 7-Eleven app, my emulator screen got all glitchy and you could hardly see what you were typing let alone if you were in the correct field. Simply type your email, press TAB, type in your password and hit the Enter key on the on-screen keyboard. Should work fine after that.

      • dontpanic on 18/01/2023 - 00:53

        Yeah, I noticed that error a bit too late (couldn't edit the post without getting mods involved, but figured y'all could work it out). All fixed on the new guide :)

    • tee123 on 05/01/2023 - 17:50

      thankyou for the guide, just cant seem to load zygisk. I keep getting an error saying unsupported image file. Also magisk didnt give me a prompt for the additional setup. I tried creating another pixel account, same error and cold started multiple times. Considering just finding a cheap Iphone at this point.

      • dontpanic on 18/01/2023 - 00:56

        Feel free to send me your terminal/CMD logs and I can take a look to see what went wrong.

    • So Was Red on 17/01/2023 - 23:57

      Thank you!

    • danred on 01/02/2023 - 20:14

      Had issues with HAXM. Would not let me launch without it so this might help someone else if they have the same issue.

      • Enable Virtualization in BIOS.
        (May be labelled something different. Typically under CPU settings. Search how to enable it with your brand of mobo)
      • in Android Studio, click more actions like before and go to SDK Manager
      • Above the list of items in the main window, change tab to 'SDK Tools'
      • Find the HAXM tool to install it. For me it was called 'Intel x86 Emulator Accelerator (HAXM installer)
      • Tick the box and hit apply and it should install. Make sure you scroll to the bottom of the log to make sure there's no errors.

      I originally tried installing it manually but it seemed the latest version from the intel github was my problem and it worked installing the 7.6.5 version through SDK Manager

    • danred on 01/02/2023 - 21:21
      +1

      I think I am having trouble with ADB if anyone can help! I am not getting this message in cmd prompt

      [ ! ] ADB is not in your Path, try to
      Set PATH=%LOCALAPPDATA%\Android\sdk\platform-tools;%PATH%

      I only get

      [ * ] Set Directorys
      [ - ] Test if ADB SHELL is working

      I have previously used ADB for unlocking my phones bootloader. Is the previous ADB perhaps interfering or not running for another reason?

      Running windows 10.
      If it helps at all, when I run the first command after changing directory, the 'tmpFile' appears in the rootAVD-master' folder.

    • ComfortablyNumb on 09/02/2023 - 12:03

      Head up to all - to get this to work now - if chrome won't load for you on the emulated device, you need to add advancedFeatures.ini file to your users dir.
      See this:
      https://stackoverflow.com/questions/69134922/google-chrome-b….

    • USER DC on 10/02/2023 - 16:52

      Anyone know how to get nox method to work again ?? this android studio is not running fine. Its slow as hell. System UI crashes, Pixel launcher crashes all time. It takes ages, and still doesn't work.

      Nox on already installed PC works fine. But on a new install the step 6 doesn't work "Open Magisk Delta, Grant SU/root access to Magisk Delta, click “Install” under Magisk field and use “Direct Install into system partition” option instead of “Direct Install” option. If you don’t see this option, close and re-open Magisk Delta app. If that doesn't work, restart the emulation." It keeps saying installation path not found etc. And that too it requires installing of Magisk app first then only shows “Direct Install into system partition” option. Otherwise stuck on the Select a path option.

      • dontpanic on 10/02/2023 - 21:35

        I had that issue a few times, but it eventually worked after restarting the emulation and Magisk. I can't really help you beyond that - I no longer use Nox and don't intend to re-install or support it.

        I can perhaps help you with Android Studio - a lot of the System UI crashes are GPU related. I had an issue where if I left the emulation running too long, the System UI would crash. The simple, quick fix was to Cold Boot the emulation again, but I later found that a small change to a setting in the config.ini resolved the problem permanently:

        1. In Android Studio, go to the device manager, click on the 3-dot menu button and select "Show on Disk"
        2. Locate the config.ini file and open in a text editor
        3. Locate the following settings and make sure they read as below:

        hw.gpu.enabled=yes
        hw.gpu.mode=host

        There are other comments in this thread detailing fixes for issue with Chrome not working (again, GPU related) - maybe take a look at those.

        If it's still too slow, then your computer is probably the problem. What are you running it on? I've tested it on desktops, laptops, new machines, 10 year old machines, a M1 Macbook Air, and they all run it sufficiently fast enough for the purposes we need here.

        • USER DC on 10/02/2023 - 21:54

          hw.gpu.mode=host
          changed from
          hw.gpu.mode=push

          definitely fixed the System UI crashes etc. thing But still problems here. Nox was so much easier and faster than this. Using it on Surface book 2. Hopefully Nox will work again with Magisk.

    • db87 on 20/02/2023 - 15:14

      Hey dontpanic,

      Question RE LSPosed and a maze of searches on Github, I can't get it to prompt the notification to install a homescreen icon. I also tried calling the ##5776733## to load it but to no avail.

      Any idea what might potentially be missing or anything you yourself may have come across during the process? Everything else more or less installed without a hitch after a few glitchy goes. My thinking is it may be the LSPosed version but I can't seem to find the 1.8.5 version anywhere.

      I'm using everything as poste in your steps and also whichever is current via github.
      Android Studio 2022.1.1.20
      Magisk 25.2 (25000)(33)
      LSPosed 1.8.6-6712 zygisk release (1.8.5 isn't available)
      Hide Mock Location 2.0.9
      My 711 2.17.10
      Fake GPS 2.1.2

      Any help much appreciated.
      Cheers!

      EDIT Found a copy of LSPosed 1.8.5 that let me install it… fingers crossed I'll post back the results!

  • warmfruit on 15/11/2022 - 17:59
    +1

    Just got an email reply about my claim on the missed discount.

    They’ve cancelled my account for breach of terms. So I won’t get the $20 voucher. They seem to have G09 some of my other accounts as well.

    Some of my accounts still work. I’ll keep using them until they G09 as well, in which case I’ll have to try and make new ones.

    Thank you for contacting us regarding your My 7-Eleven App.

    To help keep our customers’ accounts safe, and to ensure we meet our legal and regulatory obligations, we use a specialist third party provider to verify customer details.

    Your account appears to have breached the My 7-Eleven App Terms and Conditions. As a consequence, 7-Eleven has terminated your My 7-Eleven App account in accordance with the App terms and conditions. This means we will not be able to action your Fuel Price lock and subsequent Missed Discount.

    Should you have any questions concerning this please contact our Customer Service Team on 1800 247 711.

    • cwongtech on 15/11/2022 - 18:01
      +2

      They’ve cancelled my account for breach of terms. So I won’t get the $20 voucher. They seem to have G09 some of my other accounts as well.

      You win some, you lose some, c'est la vie

      I’ll keep using them until they G09 as well, I’m which case I’ll have to try and make new ones.

      Oh no.
      Have you met… warmfruit, lukewarmfruit and humidlywarmfruit?

      • dontpanic on 15/11/2022 - 18:54
        +5

        You win some, you lose some, c'est la vie

        This.

        I think it's probably a bad idea to contact 7-Eleven to get a refund on your discount that you obtained through a breach of terms.

        Why draw more attention to yourself and these workarounds?

        Even if you take a $20 hit every now and then, you're still coming out well on top, and will continue to save money so long as the Fuel Lock keeps going. The last thing we want is to give them an excuse to end it (especially after I spent all that time on the guide).

        • cwongtech on 15/11/2022 - 19:10
          +2

          Why draw more attention to yourself and these workarounds?

          https://www.facebook.com/groups/7ElevenFuelAppUsers

          We aren't the only ones aware of 7/11 fuel locks
          There are people selling them on FB marketplace..
          Another example
          There were a few 7/11 paid services/websites floating around as well

          My thoughts on the matter
          The only barrier to entry now is committing time to follow your guide (even still, we will probably get people saying "its too hard, can u plz lock for me thx")

        • warmfruit on 15/11/2022 - 21:09
          +1

          That's what I thought initially but someone said they had multiple accounts and were able to get the voucher.

          The last thing we want is to give them an excuse to end it

          I think that ship sailed when there was that price error in VIC and heaps of people fired up their choppers. I think my accounts that flew to that location have been G09 already.

          The thing is once something like this becomes popular enough, it will get shut down. I think the only reason it hasn't so far is because most people couldn't be bothered leaning how to do it. When I initially found out about it, it looked too daunting to me so I couldn't be bothered. But then petrol started to get crazy. Eventually I decided to figure it out and I've told some of my friends about them and literally none of them have been bothered to learn how to do it themselves. So I've been doing locks for them as well, hence the multiple accounts.

          When enough people figure out how to fly choppers, 7 11 might decide to end the scheme or place restrictions on it.

          • dontpanic on 15/11/2022 - 21:16
            +1

            @warmfruit:

            When enough people figure out how to fly choppers, 7 11 might decide to end the scheme or place restrictions on it.

            Hmmm… Maybe I should take the guide down. Might be making it too easy 😂

  • V001 on 16/11/2022 - 18:52

    How to know if I am G09? I am able to set the location but app failed while locking the price

    • DoctorCalculon on 16/11/2022 - 19:05

      Could someone please explain the meaning of the G09 error code? Is this platform (e.g. Android) specific?

      • klef on 16/11/2022 - 19:19

        Means the account is banned. Not platform specific.

        • Harry P Ness on 24/02/2023 - 23:46

          I have used the chopper once, at least 12m ago, since then just normal usage. Today I went to log in and it seems I got G09'ed…wonder why after so long?

          • skid on 25/02/2023 - 12:02

            @Harry P Ness: Did you get someone else to lock in for you?

            • Harry P Ness on 25/02/2023 - 16:45
              +1

              @skid: Yes, I did at the time. I imagine they've completed an audit or some such process, but it seems disingenuous to boot people simply for leveraging the app.

      • jv on 16/11/2022 - 19:20
        -4

        meaning of the G09 error code?

        The chose it because it looks similar when viewing it upside down.

        • JoeBogan on 16/11/2022 - 19:39
          +3

          Do you ever contribute anything of value @jv? Clearly not based on your terrible attempt at humour.

          • jv on 16/11/2022 - 19:40
            -4

            @JoeBogan:

            Do you ever contribute anything of value

            Do you ?

        • I Smell Pennies on 25/02/2023 - 00:05

          @jv I know EXACTLY what ur referring to and it’s not what everyone thinks 😂

  • luckylittle on 28/11/2022 - 15:54

    I don't want to use my primary phone for this. Any chances to get this working with the old app 7-Eleven Fuel 1.10.0 (before it was renamed to My 7-Eleven)?

    My setup:
    Android 8.1.0 (Nexus 6P)
    Magisk 23.0 (23000)
    Smali Patcher 0.0.7.4
    Safety Net status: Passed
    GPS JoyStick Guide 4.3.2

    In my Google Play Store, it says:
    Looking for My 7-Eleven? This app won't work for your device

    • jv on 28/11/2022 - 15:57
      +1

      I don't want to use my primary phone for this.

      Just get a cheap second hand phone that it work with then…

      It still have it working fine on an iphone 5

    • dontpanic on 30/11/2022 - 03:44

      You could try the method in my Android Studio guide. Start by doing whatever you need to do to root your phone and install Magisk, then follow the instructions in Part 3 of the guide. It uses a different set of tools than the Smali approach.

  • F1ProjectOne on 29/11/2022 - 15:13

    I just got the message that I timed out when trying to lock in a fuel pirce, tried repeatedly, each time with the same result, does that mean my account is banned?

    • warmfruit on 29/11/2022 - 16:17
      +1

      No, just try again. Maybe try restarting your phone. Banned is G09

    • sween64 on 30/11/2022 - 10:02

      Log out and log in. Or try to lock in a price for a different fuel, don’t complete it, and then go back to locking in the fuel type you want.

  • StonedWizard on 12/12/2022 - 12:04

    Does iOS 16.1.2 work with this? I downloaded the files in the link above, but when I try and lock in I get an error message: Mount failed with status: N/A and error: ImageMountFailed

  • plapic on 13/12/2022 - 07:40
    +2

    Can't use Android app. Wants to update to 2.17.7 but play store doesn't have it yet. Doh!

    • dottydotdot on 13/12/2022 - 08:35

      The update is now available, but mock location is detected and won't let me fuel lock :(

      • Rikkh81 on 13/12/2022 - 09:53
        +1

        Just updated and locked no problem on android

  • vongz on 13/12/2022 - 14:37

    Was forced to update the app today on an jailbroken iphone. Cant get it to work anymore…anyone have solutions?

    • tdw on 13/12/2022 - 15:00

      i don't have a jailbroken iphone and updated as well today but the 3u tools chopper still flies

    • jv on 13/12/2022 - 15:09

      anyone have solutions?

      Coles Express with 8c voucher is cheaper at the moment…

      • cwongtech on 13/12/2022 - 15:11

        Woolies Caltex/ampol is 4c voucher + eg club (5c) then 5% egift stack

        • jv on 13/12/2022 - 15:13

          For the win !!!

          Except that it is not all "Caltex/ampol"

          • cwongtech on 13/12/2022 - 15:13

            @jv: Correct, need to use Woolies store locator to find the Woolies Caltex that have egift.

            Either way, still 9c for non-woolies caltex

    • sween64 on 13/12/2022 - 21:41

      I’m jailbroken. I’ve updated the app. Fake location still works. I haven’t locked in a pride yet but will tomorrow. When do you get an error? What’s the error?

      • vongz on 14/12/2022 - 17:32

        Its working now, thanks. I had an E11 error before.
        What location and bypass tweak are u using?

        • sween64 on 15/12/2022 - 12:50

          Relocate Reborn and Shadow. iOS 14.8.

Login or Join to leave a comment
Login Join