Database Develop

Open Source CM10.1 for Dell Streak 7 continuation

First you need to have giveen's original port installed: http://goo.im/devs/giveen/jellystreak (via the old thread: http://forum.xda-developers.com/showthread.php?t=2130081). The most important thing this does is installing the TWRP "recovery" bootmenu thingy. You can use it when powering on/restarting the dell streak 7 and then keeping power+volup pressed and then choosing "install update from sdcard" or so.
With AOKP there is one install image that wipes /system and an ota update. I have not tested the ota update.
Download for the AOKP 4.2 build for the Dell Streak 7: http://w3studi.informatik.uni-stuttgart.de/~haagch/aokp/
The non-ota update wipes /system. So you have to reinstall gapps every time too, preferably before rebooting (android deletes settings for apps that are not installed I think).
The "official" gapps package uses neon instructions that don't work on tegra2. You'll see the keyboard, tts, etc. crashing all the time. "tonyp" has created a gapps package that uses "old" libraries that work without neon instructions. So you should use this instead of the official gapps:
Download for non-neon gapps: http://goo.im/devs/tonyp/non-neon-gapps
Gesture typing on the keyboard doesn't seem to work for me, but tts works and it doesn't seem to be crashing.
Known issues for me:
[*]sensors don't work: rotation, accelerometer, gps (I think), magnet field (Sensor driver is sensors.p3.so for now, maybe later giveen gets open source drivers to work)
headphone jack doesn't mute/transfer for some headsets like ones with built in microphones
bluetooth keyboard
Performance problems. Especially when the ram gets full. You can use a ram manager like https://play.google.com/store/apps/details?id=com.jrummy.apps.memory.manager with the Aggressive or Extreme preset to make that problem go away with the cost of background apps being killed very quickly.
Here is the repository: https://github.com/ChristophHaag/android_device_dell_streak7
And here is how to build it on Archlinux:
AOKP: https://gist.github.com/ChristophHaag/6334554
Cyanogenmod: https://gist.github.com/ChristophHaag/6078249
I'm new to android but maybe some other people know something, so I post whatever I come about. Maybe someone else wants to get started too and finds this helpful.
If you want to engage in bug finding and fixing yourself:
Remote debugging c works like this:
On the android device you do
Code:
gdbserver --remote-debug :5039 --attach 1
Which will attach gdbserver to the process with pid 1 and listen on port 5039 on all interfaces.
For a gui debugger I tried nemiver:
For $ANDROID I use the path where the cyanogenmod was checked out.
Code:
nemiver --remote=<STREAK7-IP>:5039 --gdb-binary=$ANDROID/android/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-gdb --solib-prefix=$ANDROID/android/system/out/target/product/streak7/symbols/ $ANDROID/android/system/out/target/product/streak7/symbols/init
And in edit-preferences for sources I added some paths like symbols/, symbols/system/lib and the android/system directory.
There's also a statically compiled gdb that you can use over ssh or so: http://dan.drown.org/android/howto/gdb.html
Obsolete first look into the CyanogenMod adb bug:
I think the problem is in line 1068 in init.c
Code:
if (!action_queue_empty() || cur_action)
timeout = 0;
each time I looked when it comes there the cur_action->name was "property:sys.usb.config=none".
Maybe it is connected with the adb issue. When I googled for the
Code:
E/UsbDebuggingManager( 367): Communication error:
E/UsbDebuggingManager( 367): java.io.IOException: No such file or directory
E/UsbDebuggingManager( 367): at android.net.LocalSocketImpl.connectLocal(Native Method)
E/UsbDebuggingManager( 367): at android.net.LocalSocketImpl.connect(LocalSocketImpl.java:238)
E/UsbDebuggingManager( 367): at android.net.LocalSocket.connect(LocalSocket.java:108)
E/UsbDebuggingManager( 367): at com.android.server.usb.UsbDebuggingManager.listenToSocket(UsbDebuggingManager.java:79)
E/UsbDebuggingManager( 367): at com.android.server.usb.UsbDebuggingManager.run(UsbDebuggingManager.java:115)
E/UsbDebuggingManager( 367): at java.lang.Thread.run(Thread.java:856)
issue I found surprisingly many people having issues with this, but few answers.
But I also found e.g. this: https://gist.github.com/steven676/5...c-remove-obsolete-ro.debuggable-1-trigg.patch
so the problem may be in https://github.com/ChristophHaag/an...lob/master/prebuilts/root/init.streak7.usb.rc
but I didn't have time to really read documentation to that.
I think this file complements $ANDROID/system/core/rootdir/init.usb.rc
I'll either play around with that or I'll add debug output in android.net.LocalSocketImpl.connect(LocalSocketImpl.java:238)
Code:
connectLocal(fd, address.getName(), address.getNamespace().getId());
Then I would at least know what it's trying to do and it would get easier.
Many of the results I saw from googling mentioned that it might have to do with netd.
On the streak 7 I get this:
Code:
cat /dev/socket/netd
cat: can't open '/dev/socket/netd': No such device or address
I'm not sure if this is how it should behave...
An observation is that adbd run from a command line seems to start without an issue and listens on a port specified with
Code:
setprop service.adb.tcp.port 5555
but the access over adb connect <STREAK7-IP> does only say "unauthorized". And "start adbd" does nothing. None of the programs seem to have --help or -h, so I have to look closer into whether they can be started directly.
I'll change "[ro.adb.secure]: [1]" in /default.prop to 0 and see whether that does anything.
In the other thread from giveen I said that I don't see the log spam. This was with debugging in the developer settings disabled. When I enable it, the logspam starts. But whether it is enabled or not, init still eats 100% cpu. The trouble with the debugging is that each time it is enabled and I want to disable it, the streak 7 immediately reboots.
Now that I had logcat via ssh running I caught this when the reboot happened:
Code:
W/dalvikvm( 367): threadid=50: thread exiting with uncaught exception (group=0x40b0e930)
E/AndroidRuntime( 367): *** FATAL EXCEPTION IN SYSTEM PROCESS: UsbDebuggingHandler
E/AndroidRuntime( 367): java.lang.NullPointerException
E/AndroidRuntime( 367): at com.android.server.usb.UsbDebuggingManager.closeSocket(UsbDebuggingManager.java:125)
E/AndroidRuntime( 367): at com.android.server.usb.UsbDebuggingManager.access$200(UsbDebuggingManager.java:46)
E/AndroidRuntime( 367): at com.android.server.usb.UsbDebuggingManager$UsbDebuggingHandler.handleMessage(UsbDebuggingManager.java:177)
E/AndroidRuntime( 367): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 367): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 367): at android.os.HandlerThread.run(HandlerThread.java:60)
Looks bad.
For looking at the android code I just use grep and ls with globbing for the c and config files and for the java part I imported it in eclipse via this method: http://source.android.com/source/using-eclipse.html
This is a build I haven't tested yet: http://w3studi.informatik.uni-stuttgart.de/~haagch/cm-10.1-20130820-UNOFFICIAL-streak7.zip
This is giveen's original nvflash that I am not sure I am allowed to put there as giveen has not put any license information in there: http://w3studi.informatik.uni-stuttgart.de/~haagch/JB_Beta2.1.zip But then it's all apache code and there are no notices in reagards to the apache license or changed files anyway. If not, you can just tell me and I'll remove it.
------------------------------------------------
So the call to connectLocal() that throws the exception has as parameters
fd: FileDescriptor[263]
address namespace: RESERVED with address name space id: 1 and address name: adbd
That doesn't help me much yet, but there are frequent calls with FileDescriptor[263] and namespace RESERVED, id 1, name rild (radio service) that don't throw an exception.
So it's a "valid" file descriptor... But I think the problem is still that adbd is not started by init...
The whole UsbDebuggingManager.run method is
Code:
public void run() {
while (mAdbEnabled) {
try {
listenToSocket();
} catch (Exception e) {
/* Don't loop too fast if adbd dies, before init restarts it */
SystemClock.sleep(1000);
}
}
}
where listeToSocket() is ultimately throwing the exception.
I have also read a bit about how adbd is supposed to work. Apparently in android 4.2.2 they introduced rsa encryption. It looks very similar to ssh. You have your authorized public keys on the device in /data/misc/adb/adb_keys (like ~/ssh/authorized_keys) and on your computer you have your public key in ~/.android/adbkey.pub
So I put my ~/.android/adbkey.pub in /data/misc/adb/adb_keys on the streak 7 and started adbd from the command line on the device. And indeed, when I connect with "adb connect <STREAK7-IP>" I get "<STREAK7-IP>:5555 device product:cm_streak7 model:Streak_7 device:streak7" with "adb devices -l" and adb shell works. It's a bit unrelated, but this applies: https://code.google.com/p/android/issues/detail?id=48126
But the actually important part, the "start adbd" still doesn't do anything.
It really must be somethin with /init.streak7.usb.rc. The stuff in /sys/class/android_usb/android0/ seem to be set all wrong...
------------------------------------------------
I'll just keep posting random things I discover that I find strange or interesting and if anyone knows anything about any of those, they can just chime in.
In /init.streak7.usb.rc there is the line
Code:
write /sys/class/android_usb/android0/iProduct $ro.product.model
"getprop ro.product.model" says "Streak 7" but /sys/class/android_usb/android0/iProduct apparently doesn't seem to be able to take a string with a space because "cat /sys/class/android_usb/android0/iProduct" returns "Streak". You can write directly to it with "cat "Streak 7" > /sys/class/android_usb/android0/iProduct" but it only saves up to the space. I don't think that's really a problem but strange anyway.
I have googled for another tegra 2 device and looked at its usb init rc: https://raw.github.com/CyanogenMod/android_device_samsung_p4-common/ics/init.p3.usb.rc
Adding a section with on property:sys.usb.config=adb did nothing and it seems I haven't been able to google what should be in /sys/class/android_usb/android0/idProduct for the streak 7.
I think I'll just look into how init on android works and how the triggers work. Then it shouldn't be too hard to figure out what exactly it is trying to do and why it is failing.
------------------------------------------------
I was trying to get my head around why "getprop sys.usb.config" would always return "none" and the system wouldn't respond to "setprop sys.usb.config adb,mtp" in any way. So I got to suspect that /init.streak7.usb.rc was not used at all. Then I compared the imports and found that /init.streak7.rc did use a relative path for /init.streak7.usb.rc while all the other init*.rc were using absolute paths.
So I'm not sure if it this is really the thing that fixed it, but it's the latest thing I tested and now init's 100% cpu and adb are fixed: https://github.com/ChristophHaag/an...mmit/eee0625e11cfafd510c3bada6ae67a133766c0f4
Edit: Wait, it happened again. Maybe not. :/
Hm, no, definitely not it. Can't even reproduce it. It worked after adb sideload and wiping the cache and the dalvik cache.
At least it's clear now that init's 100% cpu usage and adb not working and the dalvik crash when disabling debugging are all the same issue.

Good luck. I'll give you a hint as a parting gift. The USB issue is not kernel related.
I really dont care to licenses anything so you are free to do with as you will. Personally, I will continue to develop in private and if there are kernel changes, as per the GPL, I will make those updates available.

[moved to hidden section in first post]

[moved to hidden section in first post]

[moved to hidden section in first post]

If you really want to help, let me know. I'll let you in on my secret.

giveen said:
If you really want to help, let me know. I'll let you in on my secret.
Click to expand...
Click to collapse
Do I want to help? Does this thread look like I don't?
As I've said I'm new to the android code so I'm not really sure what I'm doing yet.
After rebooting with debugging enabled and adb sideloading an image it works for some reason (until you disable debugging in the developer settings, then it loops on sys.usb.config=none again) but it's all clearly not like intended by /init.streak7.usb.rc. /sys/class/android_usb/android0/idVendor is 18d1 and android_usb/android0/idProduct is d002 which is set in init.usb.rc for on property:sys.usb.config=adb...? I just don't get it yet. The init readme says declaring an action or service twice is an error but this is from upstream, so adb is supposed to always be 18d1:d002?
So if you know something I don't I would obviously greatly appreciate it if you told us. In fact you can directly push to the repository now if you wish to do so.

ccxxx said:
Do I want to help? Does this thread look like I don't?
As I've said I'm new to the android code so I'm not really sure what I'm doing yet.
After rebooting with debugging enabled and adb sideloading an image it works for some reason (until you disable debugging in the developer settings, then it loops on sys.usb.config=none again) but it's all clearly not like intended by /init.streak7.usb.rc. /sys/class/android_usb/android0/idVendor is 18d1 and android_usb/android0/idProduct is d002 which is set in init.usb.rc for on property:sys.usb.config=adb...? I just don't get it yet. The init readme says declaring an action or service twice is an error but this is from upstream, so adb is supposed to always be 18d1:d002?
So if you know something I don't I would obviously greatly appreciate it if you told us. In fact you can directly push to the repository now if you wish to do so.
Click to expand...
Click to collapse
The problem is CM.
I switched to AOKP which is close to Google's AOSP, and the problem solved itself. Something in the way USBManager is programmed in CM screwed things.

I got around to download aokp today.
The build system is slightly different, but easy enough to set up. I first just did an "update" to it, but the adb/init problem persisted, acore kept crashing (but deleting data for the contacts app "solved" that).
So I decided to finally make a factory reset. Not really sure what happens there, but that didn't delete the apps in /system/apps I think so I just wiped everything except sdcard etc. with twrp and installed the image again. This time it works better it seems. adb seems ok for now, cpu usage is okay.
The 4.2.2. google apps for that are these: http://goo.im/gapps/gapps-jb-20130812-signed.zip
Now I'm not sure: Would a factory reset/complete reinstall have helped with cyanogenmod too?
aokp is missing a few features cyanogenmod has, most notably the performance settings where you can overclock and set up zram with the gui.
Keyboard still crashes. Not really surprising that illegal instruction hasn't changed.
There doesn't seem to be recent apps when long pressing the home button. Strange.
Not sure how much I like it yet and whether I'd rather use cyanogenmod.
Here it is: http://w3studi.informatik.uni-stuttgart.de/~haagch/aokp_streak7_unofficial_2013-08-23.zip
Thanks, giveen.

No problem. AOSP keyboard burns RAM like nothing else. If you switch to an 3rd party keyboard , you will no longer crash. This problem is common on a lot of low memory devices. ZRAM doesn't really work. I have a script that I want to test out that DJ_Steve had originally wrote. Also, I will send you the sensor files you need to modify to get them to work.

google has this keyboard in the play store https://play.google.com/store/apps/details?id=com.google.android.inputmethod.latin and I got it from http://dl.androidnext.de/com.google.android.inputmethod.latin.apk. Works ok, but has issues like you can't disable the "ducking" blocking of "offensive" words...
The sensors changes you commited work well. Rotation/acceleration/magnet/light seem to react normally.
It's almost usable now.
For people building it from source: If you get a weird error like "ERROR: couldn't find <type 'property'> in build.prop" and can't find anything useful with google... I deleted out/* and did a complete rebuild and then it worked.
Plugging in a headset still doesn't turn off speakers but it seems only like a minor issue since it seems to be detected just fine:
Code:
V/WiredAccessoryManager( 374): Headset UEVENT: {SUBSYSTEM=switch, SWITCH_STATE=1, DEVPATH=/devices/virtual/switch/h2w, SEQNUM=2006, ACTION=change, SWITCH_NAME=h2w}
V/WiredAccessoryManager( 374): newName=h2w newState=1 headsetState=1 prev headsetState=0
W/AudioPolicyManagerBase( 103): checkOutputsForDevice(): No output available for device 0004
V/WiredAccessoryManager( 374): device h2w connected
Google tts is crashing like the keyboard (
Code:
F/libc ( 6525): Fatal signal 4 (SIGILL) at 0x5dc80738 (code=1), thread 6525 (gle.android.tts)
) but pico tts seems to work, at least with english.
A Google search gave me this:
http://stackoverflow.com/questions/7102606/sigill-in-android-ndk-code/7104177#7104177
And further this might be worth looking into: http://forum.xda-developers.com/showthread.php?t=2186251
Not sure whether it's simply neon instructions or register usage of 16+ since I haven't looked that close into the build system yet. But probably ILL_ILLOPC means it's a neon instruction.

So sensors work now? I've been at that for months and I wasn't sure if I got it right. If I got it right, that was months of work there that I wasn't even sure was going to work.
Headphones and microphones need to be adjusted in mixer_paths.xml

Months of untested work that just works? Impossible! :good:
I haven't done a really thorough test, but they all seem to be doing something. https://play.google.com/store/apps/details?id=imoblife.androidsensorbox seems to have a little problem with the directions with the rotated screen though. But in general it all does something that seems related to what I do to the device.

The AKM8973. is a chip that is normally found on qualcomm devices. So I had to track down the right HAL and then modify to work with Tegra sword ices. It's a terrible hack/slash, modify and pray it works job. I had Just finished. Does the screen rotate?

giveen said:
The AKM8973. is a chip that is normally found on qualcomm devices. So I had to track down the right HAL and then modify to work with Tegra sword ices. It's a terrible hack/slash, modify and pray it works job. I had Just finished. Does the screen rotate?
Click to expand...
Click to collapse
Yes, the screen rotates. And even more impressively, it rotates correctly!

Good. Now i can focus my energy on the camera.

Hm, having difficulty with my compiles booting. Chris, if you compile and upload the zip, I can give you my goo.im information and you can push it as an auto-update. Don't forget to include your name in there somewhere for credit as well as you are now part of the team.

giveen said:
Hm, having difficulty with my compiles booting. Chris, if you compile and upload the zip, I can give you my goo.im information and you can push it as an auto-update.
Click to expand...
Click to collapse
I have edited my first post.
http://w3studi.informatik.uni-stuttgart.de/~haagch/aokp_streak7_unofficial_2013-08-25.zip
http://w3studi.informatik.uni-stuttgart.de/~haagch/aokp_streak7-ota-eng.c-builder.zip
giveen said:
Don't forget to include your name in there somewhere for credit as well as you are now part of the team.
Click to expand...
Click to collapse
Yea, maybe if I contribute something substantial instead of cosmetic changes.

OH yeah, bluetooth keyboard, I see that as one of your issues. I'll upload a bunch of idc files that should at least address that issue, not sure though.

Are you missing any commits? I noticed your update has sensor working but my build does not.

[Q] Start TimerTask in MOD

Hi, all!
I'm developing a module, in which I want to regularly trigger some functions.
So I want to start some TimerTask in Xposed module.
I've tried to put TimerTask code into the initZygote() method, but it lead to infinite booting.
If I put them into the handleLoadPackage() code, it seems breaks functions I initialized in iinitZygote().
It seems that the TimerTask thread "occupys" the running time of main thread.
I also tried ScheduledThreadPoolExecutor, but it doesn't work.
As a green hand for both Android development and Xposed, I have no ideas about this.
Can anyone help me?

You can't have threads in zygote, it'll just boot loop as you've seen.
My advice would be to register, in initZygote, a BroadcastReceiver that does what you want in the onReceive method. Then, make a service for your app, have it run on boot and send the broadcast every X minutes.

[Q] Xposed module with sqlCipher

Hello,
I'm having a problem to load sqlCipher libs in my module.
I'm hooking PackageManagerService, so I'm under systemService context and in my DB Class CTOR i'm trying to execute: SQLiteDatabase.loadLibs(context);
I've all the necessary libs under libs directory and the needed zip file under assets
but i'm getting exception that the libs could not be found .
I've added them to the build path.
I also tried the same configuration with regular android application and it works there...
How can i add sqlCipher to my xposed model?
Thanks,

Hooked code runs as the hooked app. From the way you're loading sqlCipher (I'm not familiar with SQL libraries) that might be the problem.

GermainZ said:
Hooked code runs as the hooked app. From the way you're loading sqlCipher (I'm not familiar with SQL libraries) that might be the problem.
Click to expand...
Click to collapse
From my testing the first exception i get is when sqlCipher runs System.loadLibrary("stlport_shared");
the exception i get is:
*** FATAL EXCEPTION IN SYSTEM PROCESS: Thread-89
E/AndroidRuntime(22675): java.lang.UnsatisfiedLinkError: Couldn't load stlport_shared from loader dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/com.myapp-1.apk"],nativeLibraryDirectories=[/system/lib]]]: findLibrary returned null
E/AndroidRuntime(22675): at java.lang.Runtime.loadLibrary(Runtime.java:355)
E/AndroidRuntime(22675): at java.lang.System.loadLibrary(System.java:525)

shnapsi said:
From my testing the first exception i get is when sqlCipher runs System.loadLibrary("stlport_shared");
the exception i get is:
*** FATAL EXCEPTION IN SYSTEM PROCESS: Thread-89
E/AndroidRuntime(22675): java.lang.UnsatisfiedLinkError: Couldn't load stlport_shared from loader dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/com.myapp-1.apk"],nativeLibraryDirectories=[/system/lib]]]: findLibrary returned null
E/AndroidRuntime(22675): at java.lang.Runtime.loadLibrary(Runtime.java:355)
E/AndroidRuntime(22675): at java.lang.System.loadLibrary(System.java:525)
Click to expand...
Click to collapse
Well the Context you get in the hooked code isn't your app's but the system's context. Hooked code really is completely unrelated to your app – forget you're using Xposed and assume the modification is directly happening in the APK you're hooking. You can't access your app's resources/files/… normally.
So with all that in mind, I don't know if there's a way to directly load the library.
You could try getting your app's context from an existing context (see Context.createApplicationContext(…)). Alternatively, you might have to do the modification from your app instead (by e.g. sending a broadcast from the hooked app to your normal app when necessary).
Of course, maybe there's a way I don't know about.

Package/App not found?

I apologize in advance, because this is surely a question that has been asked and answered before but it isn't in the FAQs and I lack the vocabulary to search for it.
After installing Xposed and getting the clock demo working, I made a very simple module that just prints out package names as they are loaded.
Code:
public class Tutorial implements IXposedHookLoadPackage {
public void handleLoadPackage(final LoadPackageParam lpparam) throws Throwable {
XposedBridge.log("Loaded app: " + lpparam.packageName);
}
}
When running it on an emulated Google Nexus 5 with 5.1 (API 22) via Genymotion, it successfully logs a bunch of com.android/google things as they load, but not other applications. For instance, opening the Cyanogenmod File Manager or Final Fantasy Brave Exvius don't lead to anything being logged. When I decompile their APKs to smali, I see a lot of class names outside of the com.google/android family.
Why can't I see those apps in Xposed? Does it only hook android API functions?

Sorry, but does anyone have an idea why this might happen?

There's nothing wrong, also if your code is logging yet some applications this is a clear sign that it works. Maybe you can hook the oncreate method and log from here as an alternative.

Massi-X said:
There's nothing wrong, also if your code is logging yet some applications this is a clear sign that it works. Maybe you can hook the oncreate method and log from here as an alternative.
Click to expand...
Click to collapse
Okay, so I would use something like this code to scan the methods of loaded packages and hook onCreate methods?
github.com/rovo89/XposedBridge/issues/151
Sorry, it won't let me post a link.

Byrth said:
Okay, so I would use something like this code to scan the methods of loaded packages and hook onCreate methods?
github.com/rovo89/XposedBridge/issues/151
Sorry, it won't let me post a link.
Click to expand...
Click to collapse
I was thinking about hooking all the oncreate methods in every PKG (catching the error if not exists) and logging the PKG name. Another thing that comes to my mind: there where no errors in the log? The packages you want to log were installed before the reboot or you have installed after the module was active?

MagiskHide, and other options, are not available in v23.0

Hi,
I installed Magisk.zip v23 into the system through TWRP, and Magisk.apk v23, on my Samsung Galaxy J5 (2016) Nougat 7.1.1
The phone is clearly rooted as some of the tested apps request root, which I gave.
I noticed that something is not quite alright when I open the Magisk app (see attached image)
In the image, the second part is about the App and shows the latest verion 23.0, so that looks OK.
The first part shows the value of the settings A/B, SAR, Ramdisk and the Installed version (=N/A) .
The setting Installed should show the Magisk version 23.0 instead of N/A, and that is clearly wrong.
Also, clicking the settings cogwheel (top/right) should show a long list of settings, including MagiskHide.
However, that is not the case and the options are just a few.
There is clearly something wrong with the installation of Magish.apk, but what?
So, how can that be fixed?
How do I get back all the missing settings, including MagiskHide.
Help would be very much appreciated.
thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

DiracDeBroglie said:
Hi,
I installed Magisk.zip v23 into the system through TWRP, and Magisk.apk v23, on my Samsung Galaxy J5 (2016) Nougat 7.1.1
The phone is clearly rooted as some of the tested apps request root, which I gave.
I noticed that something is not quite alright when I open the Magisk app (see attached image)
In the image, the second part is about the App and shows the latest verion 23.0, so that looks OK.
The first part shows the value of the settings A/B, SAR, Ramdisk and the Installed version (=N/A) .
The setting Installed should show the Magisk version 23.0 instead of N/A, and that is clearly wrong.
Also, clicking the settings cogwheel (top/right) should show a long list of settings, including MagiskHide.
However, that is not the case and the options are just a few.
There is clearly something wrong with the installation of Magish.apk, but what?
So, how can that be fixed?
How do I get back all the missing settings, including MagiskHide.
Help would be very much appreciated.
thanks
View attachment 5416439
Click to expand...
Click to collapse
Search for kdragon safety net fix

John Wu, the main contributor to Magisk, now works for Google in their Android Platform Security department. So now his job is to prevent MagiskHide to work, and now it seems he removed it from Magisk.

@DiracDeBroglie since your Magisk app doesn't recognise that you have Magisk installed, none of the options you're mentioning will be available.
First thing I would check is if the Magisk app is installed to the internal storage. If it isn't, things won't work correctly.
https://www.didgeridoohan.com/magisk/Magisk#hn_Magisk_not_installed

Revolver said:
John Wu, the main contributor to Magisk, now works for Google in their Android Platform Security department. So now his job is to prevent MagiskHide to work, and now it seems he removed it from Magisk.
Click to expand...
Click to collapse
But that will have no effect on Magisk v23, that the OP is talking about. And, if you take a quick peek on GitHub and the commits over the past month (or follow the conversations in the general Magisk thread) you'll see that MagiskHide still exists, but in the new form of the deny list. Exactly how that'll work will have to wait until John releases the next Canary.

toolhas4degrees said:
Search for kdragon safety net fix
Click to expand...
Click to collapse
OP has a device from 2016. I very much doubt that it uses hardware backed key attestation... Besides, that has nothing to do with the described issue.

Didgeridoohan said:
OP has a device from 2016. I very much doubt that it uses hardware backed key attestation... Besides, that has nothing to do with the described issue.
Click to expand...
Click to collapse
Actually it does be the new zip I told him to get ere3nables magisk hide and repo....

toolhas4degrees said:
Actually it does be the new zip I told him to get ere3nables magisk hide and repo....
Click to expand...
Click to collapse
The latest release of USNF (currently v2.1.1) adds back a few of the props that MagiskHide currently changes, apart from disabling hardwarebacked key attestation. That is not relevant for the OP, since Magisk v23 still has all of that. The issue here is something else...
And it sounds like you're talking about the unofficial Alpha Magisk releases rather than the SafetyNet Fix, since the latter doesn't include anything that has to do with the soon to be removed modules repo.

Thanks for the reply.
I unstalled Magisk with uninstall.zip. That worked fine, rootchecker said that root was gone and banking and ID apps were working again.
Then I installed Magisk.zip again through TWRP, and that went well too.
Following reboot there was some sort of little Magisk app in the app folder (see first image). I double clicked it and it installed the full version of Magisk app (13MB), also that went well.
But the problem persists as before with Magisk app, that is: Installed=N/A and the important Settings, like Magiskhide and the Modules part, are missing, which means btw that Universal SafetyNet Fix cannot be installed anyhow.
My device is from 2016 (design 2015), so I have very strong doubts my device supports any hardware-backed attestation.
The Magisk core elements work flawlessly, Root Checker shows root, root apps like VPN hotspot work fine, and the banking and ID apps .... well, they detected root and refuse to continue working. So root is clearly OK.
Somehow the Magisk app in the user/data partition does not/cannot communicate with the Magisk core elements (sitting in the boot ramdisk I presume).
So, is there any app, tool or software to analyze, study or have a closer look at the communication between the app and the core elements?
If this doesn't work out with v23, then I won't have much of a choice but to install lower versions, v22, v21, ... until I come across a version that works, but that is really my last resort as my preference is v23.
Any suggestions ....

Didgeridoohan said:
The latest release of USNF (currently v2.1.1) adds back a few of the props that MagiskHide currently changes, apart from disabling hardwarebacked key attestation. That is not relevant for the OP, since Magisk v23 still has all of that. The issue here is something else...
And it sounds like you're talking about the unofficial Alpha Magisk releases rather than the SafetyNet Fix, since the latter doesn't include anything that has to do with the soon to be removed modules repo.
Click to expand...
Click to collapse

DiracDeBroglie said:
Thanks for the reply.
I unstalled Magisk with uninstall.zip. That worked fine, rootchecker said that root was gone and banking and ID apps were working again.
Then I installed Magisk.zip again through TWRP, and that went well too.
Following reboot there was some sort of little Magisk app in the app folder (see first image). I double clicked it and it installed the full version of Magisk app (13MB), also that went well.
But the problem persists as before with Magisk app, that is: Installed=N/A and the important Settings, like Magiskhide and the Modules part, are missing, which means btw that Universal SafetyNet Fix cannot be installed anyhow.
My device is from 2016 (design 2015), so I have very strong doubts my device supports any hardware-backed attestation.
The Magisk core elements work flawlessly, Root Checker shows root, root apps like VPN hotspot work fine, and the banking and ID apps .... well, they detected root and refuse to continue working. So root is clearly OK.
Somehow the Magisk app in the user/data partition does not/cannot communicate with the Magisk core elements (sitting in the boot ramdisk I presume).
So, is there any app, tool or software to analyze, study or have a closer look at the communication between the app and the core elements?
If this doesn't work out with v23, then I won't have much of a choice but to install lower versions, v22, v21, ... until I come across a version that works, but that is really my last resort as my preference is v23.
Any suggestions ....
Click to expand...
Click to collapse
Did you check if the app has been installed to external/adoptable storage? That would cause this exact behaviour...
Also, did you previously have Magisk installed with the app repackaged with a random name? If so, that app might still be present and could be the source of your problem. If so, you can uninstall that app and try again (but you might also have to uninstall and reinstall the regular Magisk app as well).
https://www.didgeridoohan.com/magisk/Magisk#hn_There_are_two_Magisk_apps

@toolhas4degrees I'm not sure what you mean by that screenshot, but it just shows exactly the same thing I was talking about in the post you quoted.

Didgeridoohan said:
Did you check if the app has been installed to external/adoptable storage? That would cause this exact behaviour...
Also, did you previously have Magisk installed with the app repackaged with a random name? If so, that app might still be present and could be the source of your problem. If so, you can uninstall that app and try again (but you might also have to uninstall and reinstall the regular Magisk app as well).
https://www.didgeridoohan.com/magisk/Magisk#hn_There_are_two_Magisk_apps
Click to expand...
Click to collapse
No, at the last install there was not any external SD card present.
No, never installed Magisk under any another name, neither did I try to hide it or so.
However, ... I did install the app Magisk.apk first a few days ago at first contact with Magisk, and then later I installed Magisk.zip through TWRP while there was an external SD present. So, .... maybe there is some remnant code laying around in the system.
I could uninstall.zip Magisk again and then look for remnants in the system and delete those. If there are any remnant left, those should probably have "magisk" in their name. Do you have any idea where to look for Magisk remnants after uninstallation?
Remember the device is a Samsung Galaxy J5 (2016) and I am not all too sure if Odin is really the most handy tool to look for code remnants. I got ADB and Fastboot installed that I used before for testing my Asus tablets. Also Terminal in TWRP I can use. If I only knew what exactly and where to look for the stuff ....

Here is an update.
As my device is still rooted by Magisk I checked out the filesystem starting from root with Solid Explorer File Manager (SE).
I found folders and files from Magisk in /root/data/adb/magisk (folder), /root/data/adb/modules (empty folder) and the file /root/data/adb/magisk.db
I uninstalled Magisk by installing uninstall.zip (from Magisk.zip) through TWRP.
And as SE needs root, I installed SuperSU-v2.82-SR5.zip through TWRP, which then worked fine.
With SE I removed magisk.db and any magisk folder at /root/data/adb/
Next thing I did was to remove, uninstall and unroot SuperSU through its own settings.
But after having clean-installed Magisk.zip again from TWRP, having installed the Magisk app using the Magisk preinstaller app in the apps folder and rebooting the device a few times, the problem hasn't gone!
And so the Magisk app pane still shows Installed = N/A, and MagiskHide, Modules and the other options are also still missing from Settings.
Any suggestions for a next move would be welcome.
thanks

DiracDeBroglie said:
installed the Magisk app using the Magisk preinstaller app in the apps folder
Click to expand...
Click to collapse
What does this mean? What's a preinstaller?

Didgeridoohan said:
What does this mean? What's a preinstaller?
Click to expand...
Click to collapse
If one performs a clean installation of Magisk.zip -- so there is no Magisk on the phone anywhere -- through TWRP, not only the core elements are installed, but also in the /data part some little Magisk app is installed that shows up in the apps folder, which I call a (pre)installer. See first image #9. Double clicking that will install the full Magisk app in the user or /data part.
So all looks ok during the installation, and rooting definitely works, but that annoying problem just persists.
I would be glad to hear any suggestions...

Ah... Now I get it. It sounded like you were using some custom unofficial stuff, and that would definitely have been a possible source of issues.
I have no suggestions, but you haven't posted any Magisk log, have you? Might be a good idea, to see if anything shows up in there. First it would be good if you could install the Canary release though, since it has more verbose logging.

Didgeridoohan said:
Ah... Now I get it. It sounded like you were using some custom unofficial stuff, and that would definitely have been a possible source of issues.
I have no suggestions, but you haven't posted any Magisk log, have you? Might be a good idea, to see if anything shows up in there. First it would be good if you could install the Canary release though, since it has more verbose logging.
Click to expand...
Click to collapse
I just had a look for those log files but couldn't find any. Any idea where to look for? In /root/data/adb/ there are no log files.

DiracDeBroglie said:
I just had a look for those log files but couldn't find any. Any idea where to look for? In /root/data/adb/ there are no log files.
Click to expand...
Click to collapse
The Magisk log is in /cache.

Didgeridoohan said:
The Magisk log is in /cache.
Click to expand...
Click to collapse
So this is what I have in the log.
01-05 19:43:01.276 262 262 I : Magisk 23.0(23000) daemon started
01-05 19:43:01.281 262 262 I : * Device API level: 25
01-05 19:43:01.296 262 264 I : ** post-fs-data mode running
01-05 19:43:01.297 262 264 I : * Mounting mirrors
01-05 19:43:01.298 262 264 I : mount: /sbin/.magisk/mirror/system
01-05 19:43:01.298 262 264 I : mount: /sbin/.magisk/mirror/data
01-05 19:43:01.299 262 264 I : link: /sbin/.magisk/mirror/cache
01-05 19:43:01.299 262 264 I : link: /sbin/.magisk/mirror/persist
01-05 19:43:01.299 262 264 I : link: /sbin/.magisk/mirror/vendor
01-05 19:43:01.299 262 264 I : * Initializing Magisk environment
01-05 19:43:02.901 262 264 I : * Running post-fs-data.d scripts
01-05 19:43:02.906 262 264 I : * Running module post-fs-data scripts
01-05 19:43:02.906 262 264 I : * Loading modules
01-05 19:43:07.207 262 538 I : ** late_start service mode running
01-05 20:43:07.209 262 538 I : * Running service.d scripts
01-05 20:43:07.227 262 538 I : * Running module service scripts
09-25 19:09:50.969 262 2470 I : ** boot_complete triggered
09-25 19:31:29.395 262 12576 W : su: request rejected (10166)
09-25 19:31:41.551 262 12618 W : su: request rejected (10166)
09-25 19:31:53.716 262 12667 W : su: request rejected (10166)
09-25 19:32:05.877 262 12707 W : su: request rejected (10166)