Quote:
Originally Posted by Renate
I emailed you a link to the modified framework.jar
I have 100% faith in this, so it should not be a problem.
|
Thanks a lot!
Quote:
Originally Posted by Renate
Oh, there's a 20M limit on files.
Still, if you keep on modifying stuff having adb run before the animation is important.
|
I will prepare a set of magisk modules, as I'd like to have a reliable adbd to do more hacks: next on my list is firewalling the google and onyx apps, or routing them through tor so that google can't so easily track users.
But that's likely to require some iterative attempts as I only have the faintest idea of what it will require
Quote:
Originally Posted by Renate
Install the new jar (using Magisk module or hardcore using a R/W /system).
Try again. Notice the difference?
|
I'll try to do that later today, as I also have to rooting another reader for a friend (another thing for which I plan to use adbd-static)
About the R/W /system it would be my preferred method for development, because it will let me try various things quickly!
But first, I'd like to understand the drawbacks (or at least the consequences!) and also how to reflash just the system partition so that I can prepare modules for people who are not familiar with command line stuff.
I have a system.img from the 3.2.2 update and also a super.img from the backup of partition 13 with edl. I could flash the super that contains both vendor and system, but why would I want to needlessly cause flash wear and tear?
Also I'm curious about the separation, how the stitching is done (lvm? offsets to be able to dd, mount -o loop?) and it may benefit my google apps firewalling but this will require some reading!
Quote:
Originally Posted by Renate
Note that Onyx is very sloppy. They have zipped up a bunch of stuff off the shoproom floor into the .jar. I saw this in my Poke3 FW and deleted them. Your jar had even more junk. A .jar should only have classes?.dex in them.
|
Indeed, there seems to be a buch of xml files for configuring the telephony stack.
In case anyone is curious:
Code:
jar -xvf framework.jar
extracted: classes.dex
extracted: classes2.dex
extracted: classes3.dex
extracted: classes4.dex
created: res/
inflated: res/vendor.mime.types
inflated: res/debian.mime.types
inflated: res/android.mime.types
created: android/
created: android/widget/
inflated: android/widget/Toast_compat_config.xml
created: android/telephony/
inflated: android/telephony/TelephonyRegistryManager_compat_config.xml
inflated: android/telephony/TelephonyManager_compat_config.xml
inflated: android/telephony/SmsManager_compat_config.xml
inflated: android/telephony/PreciseDataConnectionState_compat_config.xml
inflated: android/telephony/PhoneStateListener_compat_config.xml
created: android/provider/
inflated: android/provider/Telephony.Carriers_compat_config.xml
created: android/os/
inflated: android/os/Environment_compat_config.xml
created: android/location/
inflated: android/location/LocationManager_compat_config.xml
created: android/database/
inflated: android/database/ContentObserver_compat_config.xml
created: android/content/
created: android/content/pm/
created: android/content/pm/parsing/
created: android/content/pm/parsing/result/
inflated: android/content/pm/parsing/result/ParseInput.DeferredError_compat_config.xml
inflated: android/content/pm/PackageManager_compat_config.xml
created: android/content/om/
inflated: android/content/om/OverlayManager_compat_config.xml
created: android/app/
inflated: android/app/SharedPreferencesImpl_compat_config.xml
inflated: android/app/AppOpsManager_compat_config.xml
created: android/accessibilityservice/
inflated: android/accessibilityservice/AccessibilityServiceInfo_compat_config.xml
created: META-INF/
created: META-INF/maven/
created: META-INF/maven/com.alibaba/
created: META-INF/maven/com.alibaba/fastjson/
inflated: META-INF/maven/com.alibaba/fastjson/pom.xml
inflated: META-INF/maven/com.alibaba/fastjson/pom.properties
inflated: META-INF/NOTICE.txt
inflated: META-INF/MANIFEST.MF
inflated: META-INF/LICENSE.txt
I see you have removed them, ty!
I'm quite new to android so I didn't even know what to expect in this jar file. So I wouldn't have known exactly what to remove and what to keep.
I know a bit about Linux given my various tries to use it (though I keep returning to windows lol) but still it took me a long time to understand why I couldn't run things and to make the linker64 do what I wanted.
We seem to have similar interest in eink and readers, making the system stable and minimal, so hopefully we'll be making the Onyx better