Skip to content

Conversation

@LTeder
Copy link

@LTeder LTeder commented Sep 8, 2023

iced_native was renamed to iced_runtime in iced release 0.10.0.

Bumping these two versions produces more errors.

Removed extraneous parameter in scrollable::StyleSheet::hovered in style.rs (added in 69235a9). Now I can build for release and launch the application, but I'm unsure if removing the parameter breaks anything.

Please let me know if this checks out, or if there's anything else I can provide. I'm currently using MX Linux.

`iced_native` was renamed to `iced_runtime` in `iced` version 0.10.0
Removed extraneous parameter in scrollable::StyleSheet::hovered in style.rs (added in 69235a9)
Bumping versions produces more errors
@LTeder
Copy link
Author

LTeder commented Sep 12, 2023

Using this version I successfully ran the program with my phone, making changes then later reversing them with a backup. There is an error I encounter on a few packages which I'll include here for completeness' sake, even though the air is a bit stale in this repo... :)

Out of a few dozen that I manipulated, these four could not be re-enabled:

  • com.android.LGSetupWizard
  • com.google.android.apps.walletnfcrel
  • com.lge.gdec.client
  • com.lge.smartenabler

The latter two are undocumented. I assume this has got something to do with OEM funny business. (The final realization of my using the tool recently has been that Verizon locks my phone out from SIM cards from other companies. Hooray.)

Here is the error they all encounter.
2023-09-11 20:27:33 ERROR [src/core/sync.rs:129] [Unlisted] pm enable --user 0 com.lge.gdec.client -> 
Exception occurred while executing 'enable':
java.lang.SecurityException: Shell cannot change component state for null to 1
	at com.android.server.pm.PackageManagerService.setEnabledSettings(PackageManagerService.java:3928)
	at com.android.server.pm.PackageManagerService.-$$Nest$msetEnabledSettings(Unknown Source:0)
	at com.android.server.pm.PackageManagerService$IPackageManagerImpl.setApplicationEnabledSetting(PackageManagerService.java:5738)
	at com.android.server.pm.PackageManagerShellCommand.runSetEnabledSetting(PackageManagerShellCommand.java:2365)
	at com.android.server.pm.PackageManagerShellCommand.onCommand(PackageManagerShellCommand.java:270)
	at com.android.modules.utils.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:97)
	at android.os.ShellCommand.exec(ShellCommand.java:38)
	at com.android.server.pm.PackageManagerService$IPackageManagerImpl.onShellCommand(PackageManagerService.java:6255)
	at android.os.Binder.shellCommand(Binder.java:1049)
	at android.os.Binder.onTransact(Binder.java:877)
	at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:4472)
	at com.android.server.pm.PackageManagerService$IPackageManagerImpl.onTransact(PackageManagerService.java:6239)
	at android.os.Binder.execTransactInternal(Binder.java:1285)
	at android.os.Binder.execTransact(Binder.java:1244)

@Skallwar
Copy link

Really important because at the moment, uad fails to compile using cargo install

@Frigyes06
Copy link

See #923

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants