I have been browsing the forums for quite some time now and I have tried alot of roms. Every rom I have tried, has failed or is no longer supported. Can anyone reading this post please share a link or any other information regarding this help. I have the 5110 version note I appreciate all the help I can get.
Sent from my GT-N5110 using XDA Free mobile app
Anyone
Sent from my GT-N5110 using XDA-Developers mobile app
I forced myself to break away and lightly customize a stock ROM made for a provider. It is the only stock ROM that has stagefright fix which is way cool, and a few other usabililty fixes as well. Must allow security update to patch, it helps correct a few wee bugs.
The big issue... you are forced to keep a new boot loader, and cannot revert to any previous Stock ROM, and must deal with boot loader compatibilities unknown by builders as they have stopped with any new builds .
Downside, the new bootloader effects various Root functions. But newer Super Su, Boeffla utility, and other updated older Xposed modules seem to help with the new boot loader. Plus Default Apps no longer lists, but they can be managed through App Manager.
A custom SecSettings from a Note 2 (S5 varient) will bring back the Default Apps function plus many hidden settings options built in thus latest OEM build.
So, if you want all the bells and whistles, you will have to deal with the bugs, no matter how big or how small.
Now to explain what features I had with Gnabo v8 SE that I don't miss at all.
Mag UX, Tab Keyboard, Spen Air Command, 160dpi, Multi boot menu, and enhanced wallpaper picker.
Features I have and use, and are bug free but need a system UI to use them... tested with a custom Note 2 Secsettings that has some issues because it is a S5 variant and made for Note 2 specifically.
Colorblind, Interaction Control, Face Lock (came with my OEM build), Grey Scale (built in partially with new build, but S3 neo System UI is the key), Apps from a broken and defunct custom ROM for the N5110, Quick Connect 1.6.5.
My issues are minimal, but seem to be plagued by the new boot loader more than the ported apps.
Miracast works best, 3 minutes after reboot. WiFi is not stable after using hooked VPN apps of any type. Disabling WiFi for a minute and re enabling corrects the issue 80% of the time. A reboot may need to be done if WiFi is buggy. Reboots are 75% trouble free. Sometimes you get a fast boot soon after system UI loads, sometimes you get GMS forced closes, and must reboot.
It may be because of Triangle Away not being upgraded to work with newer boot loaders, or SU still needs some tweaks to work around the latest build by Samsung.
If I were stubborn I would stick with Gnabo v8 SE and it's patches and run Boeffla kernel, and just deal with 160dpi. But I am comfy with what I did even though the 75% boot issues and Miracast functionality being effected by WiFi with VPN apps.
I have given options for assistance by ROM builders in copying my ROM for building a unique custom one, but because I am using some apps that may be from a closed off ROM to builders, respect to the owners must be made. So it will be all for personal use at most.
Thanks for the detailed reply. I guess stock with some tweaks here and there isn't that bad afterall
Sent from my SM-G935F using XDA-Developers mobile app
as of late beoffla kernal utility works smoothly with its latest update.
Also I noticed better boot ups, so most of my boot issues are from beoffola utility with the new boot loader.
Plus, I had to manually remove earth, as google's earth app is busted for 218 220 dpi on the new rom. Google pushes that version from play store without installing the busted version. I downloaded he nodpi version and run it, just unable to update it through play store.
Also wifi seems to operate smoother changing from miracast, and vpn apps. again beoffola utility finally has gotten it right, to use on newer boot loaders, and the lastest OEM ROM.
Is it possible to have app stock like
\system\priv-app\SamsungCamera3.apk or VoiceNote4T.apk in CM13 or 14.x ??
Which \lib\ should I get ?
(thank you)
maxnuk said:
Is it possible to have app stock like
\system\priv-app\SamsungCamera3.apk or VoiceNote4T.apk in CM13 or 14.x ??
Which \lib\ should I get ?
(thank you)
Click to expand...
Click to collapse
Only if they are not dependent upon the touchwiz framework. For example samsungs internet browser can be installed on any device (example of non touchwiz dependent app) where as gear vr only works on samsung roms (touchwiz dependency) . It wont hurt to try you will just get non functional app or fc. NOTE!!!! I STTONGLY SUGGEST NOT FLASHING ANYTHING ANDROID IS DEPENDENT UPON FOR BOOT OR TOUCHSCREEN FUNCTIONALITY (SYSTEM UI, documents ui....leave anything with ui in package name alone. A phone without the ability to be interacted with would seriously suck. Obviously backup before trying system apps ....the camera isnt going to work ....im doubting voice note will either, but i havent tried either (the cam im certain wont work we have been looking for a working one since march)
Hey guys,
I am running am running LOS 16.0 on a Samsung Galaxy S5 (klte). Recently I encountered an error when trying to update an app via the play store: "This app is no longer compatible with your device. Contact the developers for more info." So I did just that and they told me, that the kernel (3.4.112-lineageos-gf381f40) is no longer supported.
I have two questions:
1) Why is the kernel version important for an app? Without having done much research, I had always thought of the OS being the layer between app and kernel, whereby only the OS version is important for an app to run.
2) Can I update the kernel? If so, how?
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.
Hello XDA community,
I am considering installing a custom ROM on my Samsung Galaxy S22 (Exynos variant) and would like to gather some information regarding the implications of this action, especially if I decide to revert back to the official Samsung firmware later on.
Apps Compatibility: Which apps will no longer work if I switch back to the stock firmware after installing a custom ROM? I understand that tripping the Knox flag by rooting or installing custom ROMs can cause certain Samsung apps like Samsung Pay, Samsung Pass, and Secure Folder to stop functioning. But what about other apps? Specifically, I am concerned about the compatibility of my banking app from Belfius (Belgium) with features like contactless payments.
OTA Updates: Will I still be able to receive Over-The-Air (OTA) updates once I have installed a custom ROM and then switched back to the official firmware?
I understand that the Exynos variant might not differ significantly from the Snapdragon variant in this context, but I thought it's worth mentioning.
Any insights or experiences that you could share would be immensely helpful. Thank you in advance!
So first thing you need to understand is that you would be installing a GSI and not a fully maintained device based Rom.
That means forget about the timely updates.
Secondly, GSIs are not optimized for particular phones and you might encounter bugs. From what I remeber, VOLTE won't work on GSI and for some phones even Bluetooth audio and mobile Hotspot won't work. Not to mention erratic battery life and unoptimized system.
App compatibility won't be an issue. But you have to say good bye to the samsung ecosystem. Also, if you do decide to install a custom rom, you will trip Knox and a few apps like secure folder, Samsung pay, samsung pass and Health might not work (unless they are patched). As for banking apps, they should work fine unless you are rooting your phone. If you do, you just to install a magisk module to pass the play stone security settings (forgot the name of it).
Also, if you again decide to go back on the stock rom, you just need to relock the bootloader and you should be able to get Ota updates again.
Overall, it's a good experience but you will grow tired of the bugs present in the GSI soon.