SM-P900 LOS 14.1 couldn't run CM Spen / no S-pen functionality - Galaxy Note Pro 12.2 Android Development

Hey, everyone.
New to ROMs here.
Glad to have discovered the world of LOS and breathe new life to my obsolete machine.
i came from stock Android 4.2 and upgraded to CM 5.1 as jump pad to 14.1.
was able to successfully install 14.1 (2020.10.30)
i installed superSU 2.46 and tried running CM sPen but failed. SuperSU needed update on SU binary
Reinstalled superSU 2.81 and updated it to 2.82
SuperSU now working
Reinstalled CM sPen 1.09 apk, granted permission and enabled it. No haptic fb when I unmounted the pen. Also tried using it with note buddy but no nothing.
Replaced it 1.05 apk. Same result
Tried with 1.07 nothing
Am I missing something here?
SPen worked perfectly when I was on 4.2

Related

[HELP] Cyanogenmod 12 Root Access

After months of sitting on the stock rooted rom I finally decided to install CM12 [Official] this morning.
everything is working fine but I have one issue. I've lost my root during install and can't seem to get it back.
So far I've installed SuperSU from the play store and the only thing that happens after telling me that the su binaries need to be updated is me getting the failed message when i hit update. I've also tried the secondary option of installing through TWRP but once you click that it does absolutely nothing.
Obviously there's something that i'm missing or doing wrong. does anybody have any input
Under development you have to enable Root for it to work
Sent from my LG-D851 using Tapatalk
That's the thing.... It is enabled under development.
I've restarted my phone numerous times and even did another fresh install enabled it again and the only difference this time around is that root checker is saying i have root now but supersu still wont update the binaries.
Root is now built into Privacy Guard for CM Roms, so if you need to manage anything you have to go to Privacy Guard in the settings. (In other words supersu is no longer needed)
I dont know if you should do this, but i did....
I launched odin and "re-rooted" my phone and it worked.
I already had Cyanogenmod 12 installed. I just put it in download mode and installed supersu through odin and its worked so far
SuperSU and Xposed are built in to Cyanogenmod 12. There is no need for either. Enable root access under Developer Options from the settings.
Sent from my LG-D851 using XDA Free mobile app

Root broken after nightly cm12.1 update

I am not very knowledgeable with the android operating system as a whole, I tried to learn as much as I can but mostly just wanted functionality so I installed cm12.1 for simplicity and root capabilities. Everything was going fine until one day the superuser built into cm12 stopped working after a nightly update(about 3 weeks ago i think), I didn't know what to do, so I tried downloading the app superuser from the play store. When I launched the app there was a notification saying the binaries needed updating and it wasn't working so I found the xda tread for SU 2.46 and downloaded it from chainfire's website. Then everything was back to normal, root checker was showing proper root and all apps were working fine.
When I updated to the current nightly (20151229) and booted back up I had the same problem where root checker shows no root and none of my apps work. So I thought all I need to do is reflash the binaries for SU. After I selected to reboot but right after the s4 mini screen it goes to a black screen and stays there.
Just reading about superuser now, I read that there can only be one super user method so I am thinking that when I downloaded SU from the play store I broke the cm12 internal rooting method, which caused real problems when I flashed the nightly as it overwrote that new method.
What I don't get is why cm12's superuser stopped working in the first place? If somebody knows what I am doing wrong I would really appreciate the help!
My plan as of now is to try and remove the app cleanly remove the app superuser and hopefully restore function to the in built cm12 superuser.
PLEASE HELP :cyclops:

A320FL viper4android

Hello, anybody successfully installed viper4android on A320FL? I am not begginer (using xposed and a lot of other apps needed root), but I can't install it fine. I tried normal install, install through twrp, freeze knox apps (with titanium backup), etc.. After first launch app I install drivers (successfully), but in drivers stats it's off.. Just not working, guys I really want viper4android, please help and sorry for english .
Edit. I using newest stock firmware with recovery and root + some features like xposed, etc..
It installed fine for me and driver status reports positive but its not working. With Spotify the sound drops for like two seconds when seeking like its trying to initiate the sound engine and then crashing and reverting to default. Id like to know how you got xposed to work though!
Got it working!
I used V4A Enforcing patch from this post for the A5 2016 and it works for me (stock rooted Android 6, TWRP) and i also got xposed working (thread here). Unfortunately V4A kicks in very late so there is an annoying dip when scrubbing in Spotify. Maybe this will improve when there are solid AOSP roms

Magisk and camera2api breaks after Lineage OS update

I'm on the official Lineage OS builds. I unlocked my bootloader last week and immediately flashed LOS. Magisk 17.1 followed next. Tried the camera2api enabler magisk module which doesn't work weirdly for some reason, I mean the build prop file was not edited. So I manually edited the build.prop to enable camera2api. All was good until, the latest build hit the update. Update went smoothly but Magisk was uninstalled, camera2api reverted back and a MI A2 camera mod was also removed.
I used Lineage OS 14.1 on Redmi Note 3 pro(kenzo) but never faced such issue on that. Magisk usually had a script that enabled itself during the OTA and it almost never broke. Camera2api too persisted
As for the mod, it is my first time experimenting with a camera mod so dunno if I have to flash it after every OTA.
Can anyone explain what might have caused this?

[A320] Viperfx with stock rom

Hi
Im back to stock after months of struggling with Lineage bugs.
All i need is viperfx, which improves internal speaker so much, whem properly configured !
I guess the only way to get it is by using magisk (i tried with a supersu root and a viperfx flash but it didnt work).
So I just spent many hours trying to get magisk to run properly but failed.
I flashed 17.1 in twrp, seemed to work, but it didnt find any module to install, so i updated magisk manager to latest version.
Then i was unable to run magisk manager, instant crash at launch, fc.
Any tip please ?
Thanks

Categories

Resources