Related
Hi guys, I wanted to start a discussion on the benefits of rooting and any available tweaks/mods/apps people are using. Thanks
daveyp187 said:
Hi guys, I wanted to start a discussion on the benefits of rooting and any available tweaks/mods/apps people are using. Thanks
Click to expand...
Click to collapse
For me at least until my SW3 updates to Android 6 I see very little point in rooting my SW3... And as yet other than twrp and Kernel I don't feel there are enough mods etc or even Custom roms(if any) to even bother with rooting... On a phone there are huge benifits but a watch that relies on your phone for most everything I see no advantages yet...
I know what you mean, side loading apps is cool, and being able to change the DPI. Firefox and Google keyboard works well, cm cleaner works perfectly and helps uninstalling apps and es file manager is good for installing apps
Be honest. Do you really need a reason beside "it can be done"?
No lol, but I want tweaks
[NUMINIT] said:
Be honest. Do you really need a reason beside "it can be done"?
Click to expand...
Click to collapse
LOL I guess not. Andhopefull we will get Marshmallow soon and then will have a proper play!
Hopefully, it's been seen in the wild. Just need them to pull their fingers out.
So, while I agree that waiting to root until after 1.4 might be a good idea, here is what I did with root...
Direct wifi access with apps (mostly es File Explorer for on watch app install and uninstall)
Kernel experimenting and tweaking
Uninstall wear apps but keep host apps on phone
All done without a computer (after initial install and setup)
Run most terminal commands with a single tap (like changing dpi)
Sent from my SM-T810 using Tapatalk
currently i am running ubuntu in a chrooted environment on my watch (rooted device needed)
Link?
if this question was dedicated to me, my answer is:
I read posts about android and chrootet linux distros and used a similar technique to do this with my smartwatch 3. As soon as I am allowed to post a DEV-THREAD I will probably make a quick tutorial about it.
Looking forward to it. Not something I've looked at
Release of OsloBridge v1.1.2 can be found here https://github.com/jcarletto27/magisk_module_motionsense_mod/releases
The purpose of this is to broadcast intents that Tasker can pick up as events. I plan on sending a PR to TopJohnWu once i hear back on some QA. Please update me here in this thread if you find any bugs! In my own testing I've found that the official apps like Pokemon wave hello and Headed South still function fine.
This module overwrites the built-in Bridge with a modified one that does not check for Googles signature on the requesting app, essentially letting anyone with knowledge of the bridge api to create an app to use MotionSense. My app which I'm calling OsloBridger (Oslo is the internal name for the MotionSense app) creates a foreground service that works even if the screen is off. I've not noticed any serious battery issues, but time will tell.
If you have issues please post here with the following and I'll do my best to help:
Device : (Pixel 4, Pixel 4XL)
Patch Date: (Oct,Nov,etc)
Are you Rooted with Magisk? : (Yes, No)
Other Modules Installed: (Systemless Hosts, edXposed, etc.)
Do you have Tasker installed ? (Yes, No)
Is "Allow External Access" checked in the Tasker Misc Preferences? (Yes, No)
When you start the service in OsloBridger what does it say in the Notification? (Reach, Flick Gestures Active)
Level of Tasker Experience ? (Novice, Experienced)
Also, please provide the task your trying to run. The steps to do that are Go to Tasks -> Long Press the Task you want to execute -> Click Three Dots in top right -> Export -> Description to Clipboard and paste it here
Update Nov 7, 2019 : I've updated the OsloBridger app to now allow the selection of specific tasks from within the app. No more setting up broadcast receivers in Tasker!
Update Nov 12, 2019: Added 2 new service intent filters to allow the starting and stopping of the Service without needing to use the Toggle intent. Updated the defaults to use what I've found works best (surprise! it's the same settings google uses for the builtin actions)
Advanced Users:
The app will still send those same broadcasts if you don't select a task in OsloBridger, so no changes for those setup already. I find this way to be more flexible because you can add multiple conditions to the event in Tasker, but I get that Tasker can have a huge learning curve.
Not sure if this will help, but I have used a magisk module to replace an apk in the product folder. Not sure if it's the same but the directory is /system/product/..….
I noticed in root explorer that the product directory in system is a shortcut to the one in the root directory
Btw, since you already digging around. Anyway to bypass the country restriction. I live so close to Mexico that it turns off every now and then.
It would be awesome if we can use Soli sensor with Tasker.
Actually, I've posted this suggestion on Tasker forum. and he, joaomgcd, also looking forward to it.
eg1122 said:
Not sure if this will help, but I have used a magisk module to replace an apk in the product folder. Not sure if it's the same but the directory is /system/product/..….
I noticed in root explorer that the product directory in system is a shortcut to the one in the root directory
Btw, since you already digging around. Anyway to bypass the country restriction. I live so close to Mexico that it turns off every now and then.
Click to expand...
Click to collapse
Thanks that might be exactly what I was looking for. In my digging I did find a country code in a preference file somewhere. I've also heard that it's restricted based on which service provider. I'll find the file and you can let me know if it works in your country.
ashergray said:
Thanks that might be exactly what I was looking for. In my digging I did find a country code in a preference file somewhere. I've also heard that it's restricted based on which service provider. I'll find the file and you can let me know if it works in your country.
Click to expand...
Click to collapse
eg1122 said:
Not sure if this will help, but I have used a magisk module to replace an apk in the product folder. Not sure if it's the same but the directory is /system/product/..….
I noticed in root explorer that the product directory in system is a shortcut to the one in the root directory
Btw, since you already digging around. Anyway to bypass the country restriction. I live so close to Mexico that it turns off every now and then.
Click to expand...
Click to collapse
Also looked into Motion Sense APK. Restriction is phone number country code based, can be bypassed. Also looks like its developers left setting to disable country checks at all. TO do that, you just need to change android setting 'pixel.oslo.allowed_override' to '1'. This way modified APK not needed.
I can't try this right now but if you want to check, then connect Pixel 4 with developer mode and execute command in adb shell:
Code:
adb shell setprop pixel.oslo.allowed_override 1
or
Code:
adb shell "setprop persist.pixel.oslo.allowed_override 1; setprop ctl.restart zygote"
or edit system/build.prop with some app
You need root to do this.
Eugnis said:
Also looked into Motion Sense APK. Restriction is phone number country code based, can be bypassed. Also looks like its developers left setting to disable country checks at all. TO do that, you just need to change android setting 'pixel.oslo.allowed_override' to '1' or 'true'. This way modified APK not needed.
I can't try this right now but if you want to check, then connect Pixel 4 with developer mode and execute command in adb shell:
Click to expand...
Click to collapse
i tried the first command, i'll let you know if it sticks
eg1122 said:
i tried the first command, i'll let you know if it sticks
Click to expand...
Click to collapse
Did the override work?
I am from Hong Kong and Google banned my region as well
chris111111 said:
Did the override work?
I am from Hong Kong and Google banned my region as well
Click to expand...
Click to collapse
Well, I live in the US but live so close to Mexico that I get signal from their carriers every now and then and it turns off. Has not turned off since I did the command
eg1122 said:
Well, I live in the US but live so close to Mexico that I get signal from their carriers every now and then and it turns off. Has not turned off since I did the command
Click to expand...
Click to collapse
So Glad to hear that! Gotta try it out when I get my phone
Eugnis said:
Also looked into Motion Sense APK. Restriction is phone number country code based, can be bypassed. Also looks like its developers left setting to disable country checks at all. TO do that, you just need to change android setting 'pixel.oslo.allowed_override' to '1' or 'true'. This way modified APK not needed.
I can't try this right now but if you want to check, then connect Pixel 4 with developer mode and execute command in adb shell:
Code:
adb shell setprop pixel.oslo.allowed_override true
or
Code:
adb shell "setprop persist.pixel.oslo.allowed_override true; setprop ctl.restart zygote"
or edit system/build.prop with some app
You need root to do this.
Click to expand...
Click to collapse
Thanks，According to your prompt, my friend has written the EDXPOSED module to open Motion Sense in any region.
Well ever since I ran the command, motion sense has not turned off
Quick update I've had success. I needed to disable the signature check and modify the bridge app. But I got a custom app seeing gestures.
ashergray said:
Quick update I've had success. I needed to disable the signature check and modify the bridge app. But I got a custom app seeing gestures.
Click to expand...
Click to collapse
Hey, can you DM me? I would love to learn more about your work.
[email protected] on Hangouts, @mrahmanXDA on Telegram, MishaalRahman#5289 on Discord.
ashergray said:
I've modified the Oslo Code [APK found in /product/priv-apps/OsloFeedback/OsloFeedback.apk] and added in some custom code to send intents for Tasker to pick up, but I can't over-write the file because Android 10 locks the /product folder.
I've tweeted at John to ask if Magisk can do this but I'm not sure. Does anyone have any experience with this? I'd really like to have custom actions for the Motion Sense Gestures.
If you can help I'll be happy to share my Module!
Click to expand...
Click to collapse
My Active Edge module modifies the SystemUIGoogle.apk to provide custom squeeze actions via Edge Sense Plus.
So yeah, you can build a magisk module to replace the file. You can check on my github how it works: https://github.com/Magisk-Modules-Repo/active_edge_system_mod/tree/Android10
I also want to inject some custom code, struggling a bit though, because I rely on logcats, because I don't own a pixel.
You hooked into handleContextHubMessageReceipt method in the FlickGestureSensor?
Any news on development? I'm not asking for eta Just curious about the progress as I'm quite disappointed by the actual use of this soli chip... It's useless atm atleast for me
Balino said:
Any news on development? I'm not asking for eta Just curious about the progress as I'm quite disappointed by the actual use of this soli chip... It's useless atm atleast for me
Click to expand...
Click to collapse
Just completed my initial release to github. I'll be sending a pull request to John once I get some feedback on how it's
https://github.com/jcarletto27/magisk_module_motionsense_mod
Well Done!?
i ll give it a try & send u feedback asap
Did this break face unlock for anyone else?
I've tried setting it up 6 times. Successfully saves face data but can't verify my face.
itylermartin said:
Did this break face unlock for anyone else?
I've tried setting it up 6 times. Successfully saves face data but can't verify my face.
Click to expand...
Click to collapse
Appreciate the feedback. Just checked with my device and can't replicate the issue. Can anyone else replicate this?
Edit: are you using the November Android update? I never tested for that
Yes I am. Tomorrow I'm going to do a fresh install see exactly what's causing the issue. Only modules I have installed are BusyBox, viper, sq lite, and this.
I turned face unlock off for the time being. Even if it does conflict with this mod it's worth it! Great work
[Back 2 Basics]
Simple privacy oriented rom based on stock, just like in old days.
[The way you like it]
Keep it simple or modify
Your Phone
Your Rom
[Simplicity]
So simple, your grandparents could use it
[Security]
Privacy is our right
Stop feeding corporations with your data
[Speed]
Do you need to buy visually faster phone every year, so the manufactures would produce more electronic waste?
Use your phone at full potential instead!
XDA:DevDB Information
[TomaHawk]Back2Basics, ROM for the Sony Xperia XZ Premium
Contributors
Doom Slayer
ROM OS Version: 9.x Pie
Based On: Sony Stock
Version Information
Status: Testing
Current Beta Version: 0.2
Beta Release Date: 2020-07-28
Created 2020-07-28
Last Updated 2020-07-28
How To
[Installation]
Assuming you unlocked your bootloader and have TWRP
IF WIPED SYSTEM/USING AOSP/WANT TO ENABLE SECOND SIM ON G8141
Flash This with a newflasher
CONTINUE:
P.S. Keep a TWRP backup of stock rom on your phone, so you won't need to use newflasher again.
Install this on top of the stock/stock based rom (like Tomahawk Project)
Don't forget factory reset!
Links:
AFH
GDRIVE
CONTINUE:
[Freedom of choice]
FOR MAXIMUM SECURITY:
Keep it simple, without ROOT
Install F-Droid and explore open source world. Download APK and send it to your device. I removed browser, pick your own
At your own risk:
If you want download apps from playstore anonymously, try Aurora Store
Want to get accurate Network location and some of the Google apps working properly, then install this Magisk Module
To get Network Location working, signature spoofing is needed. You'll need this or this edXposed module
If you think my work was for nothing:
Install Gapps and never visit this thread again
Changelog
0.1
Initial release
0.2
Fixed broken GSM + Data
Privacy made Easier
Let's find a balance between security and ability to use apps which we have to.
Most of us have people who use messengers we don't trust, but we still need to communicate with those people.
Another CONCERN is a fact that most of the apps rely on google for push notifications. Google get all the content, no matter how secure your messenger is.
If you don't have Google Services, then you have problems with notifications. Here MicroG will help us.
So, let's make a secure environment for apps we use, but don't trust.
You gonna need:
This rom installed
Magisk + "microG installer Revived"
Shelter
Let's do it!
Open Shelter app and let it create work profile.
Then you need to make sure install some apps in there:
If you install Aurora Store inside Shelter it will allow to easily manage apps from Play Store.
You can clone magisk to shelter( enable multi user in the main app first, then clone) and install firewall inside the shelter.
Update:
Another way is to install vpn inside shelter and enable kill switch. So apps inside shelter only won't have internet access unless you enable VPN.
I use protonvpn, it give 3 countries for free and it's more than enough for average user.
Beware that when VPN is outside of the shelter, on the mainland, apps on shelter will bypass it, so you need to have clients on both. You may have 2 different VPN clients enabled if you need to.
What do we get?
See "Contacts" and "Files"?
Those are seperate from the mainland, so you can just add your relatives' phone numbers and WhatsApp will only see those.
We are LIMITING ACCESS TO FILES AND CONTACTS.
Plus we can easily freeze those apps, or limit connectivity with a firewall, or vpn.
Result:
You can use apps, that brings vulnerabilities or privacy concerns in a locked,controlled environment.
Still receive notifications without sending them to Google.
Or you can try VMOS, at your own risk of course
Short message for each of you.
This rom is a result of a project which aim to strip android back to it's core, so WE CAN BUILD IT THE WAY WE WANT IT. Not the way market researchers say we want it.
In short, this ROM is a prototype of community communication device.
Everyone can join the digital freedom project. I am sure each of us can help a cause.
Is ther any way to get real all the 4k working all time
mahmoodsaud said:
Is ther any way to get real all the 4k working all time
Click to expand...
Click to collapse
Not real,but VM
If you set "apply on boot", you will notice that boot animation will become smaller ,but it's the same trickery as adb commands.
g8141 does not work, reboots right after sony logo no bootanimation.
p.s. flashed over .107 stock rom with twrp 3.2.3-0
edit: installation guide is a bit vague, do we MUST flash this? https://androidfilehost.com/?fid=4349826312261694774
It says
IF WIPED SYSTEM/USING AOSP/WANT TO ENABLE SECOND SIM ON G8141
but I didn't wiped system nor using aosp nor want to enable second sim
second edit: Needs few reboots before booting to system, seems to work like intended.
Some suggestions:
Please find a solution to Automatic reboot when sim tray is removed, since I don't use dual sim and switch SD cards frequently it gets frustrating so fast. Thanks in advance.
Qualcomm Device Security still persists on this rom, it has an apk under vendor\app\QualcommTelemetry(?)
Video Enhancement is not working, at least on settings preview.
VERY USEFUL: Show charging current on lock screen, existenz rom had it.
Dark/Full Black System theme
Boot time is unacceptable, it takes around 2 minutes for normal boot, whereas even in a bloated stock it took around 30~ seconds. It is due to your framework changes and deodexing. However, I've been able to restore optimal boot time by changing all frameworks.
@undefine,
Yeah, boot time is longer because because of deodexing. Frameworks are untouched though in this rom.
If you want Video Enhancements, then you need to go back to android 8 and istall drm patch.... Since they fixed the camera on Pie nobody really bothers with other drm related things...
Agree on the dual sim reboot thing, it's annoying, but I have no idea how to disable it for now. If you really don't need to dual sim functionality then you can try flashing this rom on top of G8141 version and make sure you got kernel as well.
Theme is overlay, adding functionality to the lock-screen require modifying services.jar to disable signature (super user mod), both are security risks... You may flash existenz on top and remove what you don't need. At your own risk of course
Doom Slayer said:
@undefine,
Yeah, boot time is longer because because of deodexing. Frameworks are untouched though in this rom.
If you want Video Enhancements, then you need to go back to android 8 and istall drm patch.... Since they fixed the camera on Pie nobody really bothers with other drm related things...
Agree on the dual sim reboot thing, it's annoying, but I have no idea how to disable it for now. If you really don't need to dual sim functionality then you can try flashing this rom on top of G8141 version and make sure you got kernel as well.
Theme is overlay, adding functionality to the lock-screen require modifying services.jar to disable signature (super user mod), both are security risks... You may flash existenz on top and remove what you don't need. At your own risk of course
Click to expand...
Click to collapse
I think boot time is not because frameworks are changed but some are missing, I just reflashed with everything in stock framework folder, it seems to be blazing fast as normal. I'm actually surprised it booted that fast even with Deodex.
As far as I remember Video Enhancements worked on stock 9 at least on my device, I have my drm keys though since I waited for a proper ta backup. However it is not a must feature either.
I'd rather flash opengapps full package than flashing existenz over this rom . I will look into some other tricks for showing charge current, maybe some xposed module exists?
Anyway, thanks for your contribution to this device. Cleanest stock rom I've ever used (besides one bloat called Qualcomm Device Security which I immediately removed).
Hello everyone,
Recently I have been experimenting with custom ROMs on my Samsung phone and was very unpleasantly surprised to find that Samsung does not allow my Galaxy Watch to be used with modded Samsung phone... Yeah, I know there's the option to replace manufacturer and brand in build.prop, however I don't like the idea of unnecessarily modifying the system just for a couple of proprietary apps, so instead I took the approach of patching the apps to make them work with the phone again.
All that needed to be done was patch manufacturer and brand to static string(s). Here's a command to do just that:
Bash:
find . -type f -name "*.smali" -exec sed -i 's/sget-object \(v\|p\)\(.\+\), Landroid\/os\/Build;->\(MANUFACTURER\|BRAND\):Ljava\/lang\/String;/const-string \1\2, \"letitbeheardthisphoneistobetreatedasifitwereofabranddifferentfromtheonestartingwiths\"/g' "{}" \;
Patching the apps, however made the shealth app refuse communication with the wearable app due to mismatching signing certificates and it needed to be patched too. It is possible to either completely bypass signature checking or insert custom certificate - I have attached a patch that does just that.
You can (and probably should) do this yourself if you want to use the modified applications. Just decompile apks with apktool, apply the command in the directory with the apps content (it is necessary for Galaxy Wearable, Samsung Accessory and Galaxy Watch Plugin apps), and insert you own custom certificate into Galaxy Watch Plugin (attached patch - just replace the cert with your custom one). If you use Samsung Health, just replace the certificate string with hex-encoded certificate you used to sign the apps in the attached patch and apply it to the app. Then rebuild the apps and sign using the key whose certificate you just inserted into the apps.
Although you should never trust a random stranger on the internet with apps you install, I understand not everyone wants to go through this process themselves, so hereby I solemnly promise there is no malicious code inserted into the provided apks. And here's the link
App Versions:
Samsung Accessory (com.samsung.accessory): 3.1.94.11128
Galaxy Wearable (com.samsung.android.app.watchmanager): 2.2.42.21083061
Galaxy Watch PlugIn (com.samsung.android.geargplugin): 2.2.05.21042051
Samsung Health (com.sec.android.app.shealth): 6.18.7.005
No idea what you're talking about. My watch works fine with my note 10+ using Dr ketan rom.
Same with Alexis. I just hide it with magisk but it was working just fine before that.
dchd310870 said:
No idea what you're talking about. My watch works fine with my note 10+ using Dr ketan rom.
Click to expand...
Click to collapse
Leon said:
Same with Alexis. I just hide it with magisk but it was working just fine before that.
Click to expand...
Click to collapse
I was talking about AOSP-based ROMs. Generally, I build and sign the ROM whenever possible and so I don't find it necessary to root my devices. Also I don't like the idea of making changes to mask the actual device and when the app is used with Samsung phone, it relies on proprietary interfaces implemented only in Touchwiz, which are not available in AOSP. Since it is an app issue, it makes sense to make changes on the app level instead of the system level.
dansimko said:
I was talking about AOSP-based ROMs. Generally, I build and sign the ROM whenever possible and so I don't find it necessary to root my devices. Also I don't like the idea of making changes to mask the actual device and when the app is used with Samsung phone, it relies on proprietary interfaces implemented only in Touchwiz, which are not available in AOSP. Since it is an app issue, it makes sense to make changes on the app level instead of the system level.
Click to expand...
Click to collapse
Hi,
I 've got the same problem with the rom Beyond V2.0.
Can you explain more precisely what i must do with yours files ? I'm a novice and my english not very good.
Thank a lot
Hello,
I'm using a unrooted (root not available yet) but knox tripped Samsung Galaxy S21 Ultra. Because of no root i'm not be able to edit build.prop to change the tima line. Now I'm searching a way to get Samsung shealth 6.15.1.003 get working with data sync. To be honost i dont really understand how to patch this way. Could somehone explain me what to do? Samsung health is already decompiled with APK Easy Tool. Thanks in Advance
Hallo sir can you update the files or explain a bit further how to do it by ourselves
Could you be more specific. I want to try it but I dont understand how to doit. some one knows how to patch these apks. ? you tube video? thanks.
hi sir, thank you for your hard work. looks good and might be what i wanted. just rooted my phone and i cant seem to pair my gear sport with my rooted S20+.
Do i just install the apk like normal, running it in file manager? or do i need to flash it in through custom recovery?
fwiw i use an Active 2 with a rooted Pixel 2 XL, and dont need any of that and have ECG/BP and Samsung Pay working. Only modified thing is the Samsung Health monitor app on the phone, modded to not detect root or require a Samsung Phone, thats it....
I own a s5neo with lineage 17.1 and I had the same problem as reported, galaxy wearable identified my phone as modified/rooted and exited. Using your apk I was able to launch the app but it fails to install the galaxy buds live plugin, only shows a message that failed to install.
I don't know how to do the patch and I would like to know if you can generate a patched apk for buds live plugin (https://play.google.com/store/apps/details?id=com.samsung.accessory.neobeanmgr&hl=en_GB)
thanks in advance
Can I use it for Spay?
nevermindrs said:
I own a s5neo with lineage 17.1 and I had the same problem as reported, galaxy wearable identified my phone as modified/rooted and exited. Using your apk I was able to launch the app but it fails to install the galaxy buds live plugin, only shows a message that failed to install.
I don't know how to do the patch and I would like to know if you can generate a patched apk for buds live plugin (https://play.google.com/store/apps/details?id=com.samsung.accessory.neobeanmgr&hl=en_GB)
thanks in advance
Click to expand...
Click to collapse
I have Galaxy Buds+ on a Pixel 2 XL
Heres how to do it the easy way...
Install Magisk
Enable MagiskHide in Magisk Manager settings
Tick all Samsung related apps in MagiskHide in Magisk Manager
Hide Magisk Manager
Reboot
Thats how i also have my Active 2 and Samsung Pay working
^yep, magisk is magic!
dansimko said:
I was talking about AOSP-based ROMs. Generally, I build and sign the ROM whenever possible and so I don't find it necessary to root my devices. Also I don't like the idea of making changes to mask the actual device and when the app is used with Samsung phone, it relies on proprietary interfaces implemented only in Touchwiz, which are not available in AOSP. Since it is an app issue, it makes sense to make changes on the app level instead of the system level.
Click to expand...
Click to collapse
Hi,
I am unable to install any of the apk. App not installed.
Please help me.
dansimko said:
Hello everyone,
Recently I have been experimenting with custom ROMs on my Samsung phone and was very unpleasantly surprised to find that Samsung does not allow my Galaxy Watch to be used with modded Samsung phone... Yeah, I know there's the option to replace manufacturer and brand in build.prop, however I don't like the idea of unnecessarily modifying the system just for a couple of proprietary apps, so instead I took the approach of patching the apps to make them work with the phone again.
All that needed to be done was patch manufacturer and brand to static string(s). Here's a command to do just that:
Bash:
find . -type f -name "*.smali" -exec sed -i 's/sget-object \(v\|p\)\(.\+\), Landroid\/os\/Build;->\(MANUFACTURER\|BRAND\):Ljava\/lang\/String;/const-string \1\2, \"letitbeheardthisphoneistobetreatedasifitwereofabranddifferentfromtheonestartingwiths\"/g' "{}" \;
Patching the apps, however made the shealth app refuse communication with the wearable app due to mismatching signing certificates and it needed to be patched too. It is possible to either completely bypass signature checking or insert custom certificate - I have attached a patch that does just that.
You can (and probably should) do this yourself if you want to use the modified applications. Just decompile apks with apktool, apply the command in the directory with the apps content (it is necessary for Galaxy Wearable, Samsung Accessory and Galaxy Watch Plugin apps), and insert you own custom certificate into Galaxy Watch Plugin (attached patch - just replace the cert with your custom one). If you use Samsung Health, just replace the certificate string with hex-encoded certificate you used to sign the apps in the attached patch and apply it to the app. Then rebuild the apps and sign using the key whose certificate you just inserted into the apps.
Although you should never trust a random stranger on the internet with apps you install, I understand not everyone wants to go through this process themselves, so hereby I solemnly promise there is no malicious code inserted into the provided apks. And here's the link
App Versions:
Samsung Accessory (com.samsung.accessory): 3.1.94.11128
Galaxy Wearable (com.samsung.android.app.watchmanager): 2.2.36.20113061
Galaxy Watch PlugIn (com.samsung.android.geargplugin): 2.2.05.20110441N
Samsung Health (com.sec.android.app.shealth): 6.12.3.001
Click to expand...
Click to collapse
how to generate hash from keystore. can anyone help? @dansimko
mohsin1122 said:
how to generate hash from keystore. can anyone help? @dansimko
Click to expand...
Click to collapse
Generate Hex from keystore
keytool -alias mykey -exportcert -keystore my-release-key.keystore -storepass 123456 | xxd -p
To anyone coming across this post who wants to do this themselves, I've made a little guide and some tools here: https://github.com/adil192/SamsungAppsPatcher.
I've also attached the apks I've patched if you don't want to do it yourself (since the ones in OP didn't work for me) here: https://mega.nz/folder/sUFj2C5b#M4zEP-c9ylY-ENxPw7qCUQ. Like OP, I promise I haven't added malware in this.
Edit: I've somewhat automated the process now so if anyone wants me to patch another plugin, just @ me and I'll get it added as soon as possible.
Adil192 said:
To anyone coming across this post who wants to do this themselves, I've made a little guide here: https://gist.github.com/adil192/ab95808fb66b6cde3d63ded6c19b0f1d. I've also attached the latest apps I've patched if you don't want to do that (since the ones in OP didn't work for me) here: https://mega.nz/folder/sUFj2C5b#M4zEP-c9ylY-ENxPw7qCUQ. This is tied to my name so I have no reason to add malicious code.
Click to expand...
Click to collapse
I need assistance with the gear s3plugin apk please.
Got it working..thanks
Would this process work to enable the Galaxy Wearable App to connect if using non-uk galaxy buds live? My app sets up the buds live but then fails to connect, even though Bluetooth connects and buds function.
Samsung have advised I have a Vietnamese version of the buds live which are not compatible with the Galaxy Wearable App in the UK.
There is an issue with Android x86 handling of permissions for play store installed apps which it seems may have been around for some time.
Pie is definitely affected and I do believe Bliss 11.** inherits the issue from Androidx86 Pie.
Basically the issue it seems is some apps installed via Gapps cannot write to their various package directories. For example 'system/data/app/"dedicated_package_directory"/' amongst others post installation.
You can replicate this issue with Gamelofts War Planet Online: Global Conquest which is a free to play game so no purchase is necessary.
This game installs and runs without issue in Android 9 on devices such as Samsung Galaxy Note 8. On Androidx86 it cannot launch as it installs more files as part of the First launch process but does not have permission to do so in Androidx86 Pie.
You cannot twiddle any storage permissions for these app in settings as it does not require any it should not already have.
Seems this is working in Bliss OS 11.13 at least for the game specified