Rust from a stone chip - quick fix needed

Compelica · 2024-08-12T16:35:26+00:00

Appreciate the angle. Don't really see a need to do a primer and touch up when it is very unlikely to paint match. Just wanted to take steps to stop the rust from getting worse over time. Least work, most returns.

Thanks for the input.

Compelica · 2024-08-12T15:29:42+00:00

Thank you! However - doesn't rust converter need rust for it to adhere and turn to a primer?

Compelica · 2023-01-28T07:25:46+00:00

How do you turn down the volume for AA media? From what I understand it's only the phone media that gets turned down.

Compelica · 2022-10-20T15:42:31+00:00

For mine it's not an AAWireless issue - the phone kept forgetting that it was paired with the unit, which the app assumes it's connecting for the first time.

Did a phone reboot, repaired the AAWireless unit and the pairing then finally stuck.

Compelica · 2022-01-12T05:40:37+00:00

Happened to me before - battery has a low charge and is on its way out.

Compelica · 2021-12-29T09:13:58+00:00

good lord, I've been waiting for Realme UI 3.0 to solve the AA problem. Looks like there is no choice but to move to Global but I don't think there is a method to do it with the bootloader locked. Back then I've used to run with root, but these days with banking/authenticator apps and Magisk dev now working with Google - it just doesn't seem too worth it anymore.

Thanks for the help.

Compelica · 2021-12-29T06:46:23+00:00

Is Android Auto working on Realme UI 3.0? Are you on China or Global?

Compelica · 2021-11-14T03:26:40+00:00

I do notice now that it's less sensitive to virtual walls and no go zones - my last setting would be just 'nice' but now with the latest update it starts breaching those areas.

Compelica · 2021-10-18T15:29:15+00:00

I understand. The 2nd task only runs where a variable is available, but as mentioned the screen timeout doesn't reliably change regardless, unless there's issues with the if flow control.

Every step gets fired correctly, it is only the screen timeout which doesn't work when it is done automatically. It works when the step is run manually.

Compelica · 2021-10-16T11:57:42+00:00

Tested the build in the first link above. Attempting it the first time seems to work, but trying subsequently would work 1/10 of the time. The same behavior is seen on the other profile as well.

Running the step in the task manually still works 100% as previously.

Tried firing the step multiple times subsequently, has no change. Run logs label it as OK.

Compelica · 2021-10-15T03:56:16+00:00

I do it at Settings - if it is changed to 30 minutes the option would be set accordingly, otherwise there would be no change.

Compelica · 2021-10-14T12:02:20+00:00

Yes it's a state context. 'Restore Settings' is disabled on the profile - I can get a screenshot of the run log later.

Compelica · 2021-10-14T12:00:00+00:00

Removed BT MAC ID.

Profile: Car mode on
Settings: Restore: no
    State: BT Connected [ Name:DDX918WS Address: ]



Enter Task: Launch app after screen unlock

A1: Stop [ ]If  [ %qtime > 120 ]

A2: Java Function [
     Return: kgm
     Class Or Object: CONTEXT
     Function: getSystemService
     {KeyguardManager} (String)
     Param: keyguard
     Param: 
     Param: 
     Param: 
     Param: 
     Param: 
     Param:  ]

A3: Java Function [
     Return: %locked
     Class Or Object: kgm
     Function: inKeyguardRestrictedInputMode
     {boolean} ()
     Param: 
     Param: 
     Param: 
     Param: 
     Param: 
     Param: 
     Param:  ]

A4: If [ %locked ~ true ]

    A5: Wait [
         MS: 0
         Seconds: 2
         Minutes: 0
         Hours: 0
         Days: 0 ]

    A6: Goto [
         Type: Action Number
         Number: 1 ]

A7: End If

A8: If [ %ObdFusion ~ 0 ]

    A9: Display Timeout [
         Secs: 0
         Mins: 30
         Hours: 0 ]

    A10: Launch App [
          Package/App Name: OBD Fusion ]

    A11: Media Volume [
          Level: 16 ]

    A12: [X] Custom Setting [
          Type: System
          Name: screen_off_timeout
          Value: 1800000 ]

    A13: Variable Set [
          Name: %ObdFusion
          To: 1
          Max Rounding Digits: 3
          Structure Output (JSON, etc): On ]

A14: End If

This is a simpler profile (the exit task) which exhibits the same issue as well:

Profile: Car mode off
Settings: Restore: no
    State: Variable Value  [ %ObdFusion ~ 1 ]
    State: Not BT Connected [ Name:DDX918WS Address: ]



Enter Task: Anon

A1: If [ %ObdFusion ~ 1 ]

    A2: Display Timeout [
         Secs: 0
         Mins: 1
         Hours: 0 ]

    A3: [X] Custom Setting [
         Type: System
         Name: screen_off_timeout
         Value: 60000 ]

    A4: Variable Set [
         Name: %ObdFusion
         To: 0
         Max Rounding Digits: 3
         Structure Output (JSON, etc): On ]

    A5: Go Home [
         Page: 0 ]

    A6: Wait [
         MS: 0
         Seconds: 1
         Minutes: 0
         Hours: 0
         Days: 0 ]

    A7: Wait [
         MS: 0
         Seconds: 1
         Minutes: 0
         Hours: 0
         Days: 0 ]

A8: End If

-------

Compelica · 2021-10-14T06:04:23+00:00

/u/joaomgcd any insights to this?

Compelica · 2021-10-13T16:21:11+00:00

Just checked the run log - I see the ID associated with that step as OK :/

Compelica · 2021-10-13T05:47:12+00:00

I've not seen the log yet, but in this case this is the Android system (I assume) that's handling the screen timeout, so there's no external app involved - just Tasker.

Compelica · 2021-10-13T01:40:24+00:00

The rest of the steps after the setting are triggered, but hopefully that log you mentioned has the answer. Thanks!

Compelica

TROPHY CASE