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.
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.
Hi,
My goal is to successfully install the Xposed framework on the HTC10. I have a stock RUU ROM, unlocked the bootloader, installed TWRP recovery, and rooted it with Supersu with force encryption per Rootjunky.com videos on YouTube. Specifically, I'm using the xposed-v86-sdk23-arm64.zip, SuperSU-v2.71-forceencrypt_v2, TWRP-3.0.2-6-pme. Then I proceeded to install the Xposed framework and APK. It flat out dosesn't work. the Bin folder and log folders are empty and I receive "The latest version of Xposed is currently not active. Did you install the framework and reboot?" I have verified my root is working with a number of other apps. I have tried resolved the issue by executing the methods listed in this article: Can't post links yet cause I'm a noob. And they didn't work. I have completely wiped my device internal and external and tried rerooting and reinstalling and I still get the same result. I also have tried installing older version of the Xposed framwork. I have spend days troubleshooting it and I can't figure it out. No matter what I get the Currently not active.
Some of my reading points to the SE Linux Mode being set to "Enforcing" being the culprit as to why it is not working. I have no idea what this is. However, I can confirm that mine is set to Enforcing despite me executing all three steps in the aforementioned article. I installed that lean kernel so it should be set to permissive I would think but Device Control app shows otherwise.
When I click on Logs in the the Xposed Installer, it says Could not read log /data/data/de.robv/android/xposed.installer/log/error.log. I can confirm that it is installing something because the DE.ROBV.ANDROID.XPOSED.INSTALLER directory is there. And all of the sub directories are present. But bin and log directories are empty which I find odd. I would expect to see many files in there especially the Bin folder.
Any ideas how to resolve this without a log file? I'm sure the HTC10 is arm64 so that shoudn't be the issue. any ideas why this isn't installing correctly? Is it the SE Linux Mode? Do I need to S-Off of something? Any help appreciated!
Regards, Matt.:good:
@topjohnwu
Its been long i have been experiencing this same problem since magisk v15 and i am not the one who is getting this issue.
When you flash magisk everything is fine and you get su prompt without any issue.
But if you see after sometime maybe like 10 or15days its not sure it comes random and new app you install yoj never get prompt of su request.
Issue in magisk log is same as others
04-26 07:54:08.656 26879 26879 E Magisk : write failed with 32: Broken pipe
04-26 07:54:23.254 27099 27099 W Magisk : su: request rejected (10240->0)
04-26 07:54:57.742 27473 27473 W Magisk : su: request rejected (10230->0)
04-26 07:55:06.003 27527 27527 E Magisk : write failed with 32: Broken pipe
04-26 07:55:12.932 27541 27541 W Magisk : su: request rejected (10262->0)
04-26 07:55:18.934 27571 27571 W Magisk : su: request rejected (10211->0)
04-26 07:55:26.091 27612 27612 W Magisk : su: request rejected (10217->0)
04-26 07:55:26.093 27613 27613 W Magisk : su: request rejected (10217->0)
04-26 07:58:20.432 27670 27670 W Magisk : su: request rejected (10211->0)
Click to expand...
Click to collapse
that 10412 is random number maybe uid
But saved su request apps keeps working as fine they can execute su commands which are saved in magisk manager but new apps never get the prompt.
So i think this issue is somewhat related to magisk manager app which doesnot repond, even though i have made sure magisk manager is in my recent app not killed still no prompts.
Now i am fed up with this so posted this issue.
The only thing which works for me i have taken data backup of magisk manager and restore it so my apps stays working fine.
Temp fix whivh always work for me is i have tk flash system image in twrp backup restore and then after sometime after reboot magisk shows prompt, dont know whats this.
My devices are s7 and s9+ exynos same issue on both since v15 i started using magisk.
Full logs attached.
I think I faced the same issue (or at least something similar) two or three times, I will try to get some logs for the next time.
This needs to be analyzed properly every user gets this but we ignore wven for me it is not working even after jninstalling and installing magisk
Every user is not experience this... As an example, I've never seen it. But, that doesn't mean that there isn't an issue, of course.
You're completely correct that it would need further analysis to know what's going on with your device. To me it sounds like your system is killing of the Magisk daemon (or something similar).
Your mention that you have to reflash the system to get things working, but that sounds a bit drastic. What else have you tried? Have you tried simply force closing the Magisk Manager, etc?
And of course, if you're really serious about analysing things you'll have to grab logs showing exactly what's going on.
Didgeridoohan said:
Every user is not experience this... As an example, I've never seen it. But, that doesn't mean that there isn't an issue, of course.
You're completely correct that it would need further analysis to know what's going on with your device. To me it sounds like your system is killing of the Magisk daemon (or something similar).
Your mention that you have to reflash the system to get things working, but that sounds a bit drastic. What else have you tried? Have you tried simply force closing the Magisk Manager, etc?
And of course, if you're really serious about analysing things you'll have to grab logs showing exactly what's going on.
Click to expand...
Click to collapse
hi this issue has been reported many times in this magisk sections you can search and find this,even google search can brings many issues like this.
i dont know what fixes the issue cus nothing works, but flashing system and starting then popup doesnot come immediately it takes time to come even when you ran app 5mins back then back to normal
full magisk logs attached
BytesReverser said:
hi this issue has been reported many times in this magisk sections you can search and find this,even google search can brings many issues like this.
i dont know what fixes the issue cus nothing works, but flashing system and starting then popup doesnot come immediately it takes time to come even when you ran app 5mins back then back to normal
full magisk logs attached
Click to expand...
Click to collapse
I've seen reports of it, yes, but it's far from a universal issue. The main problem is that the required details for any kind of "fix" generally is missing from the reports (just a plain Magisk log is usually inadequate).
My guess is that it's likely caused by to aggressive OEM implementations of battery optimisation or the likes thereof.
Didgeridoohan said:
I've seen reports of it, yes, but it's far from a universal issue. The main problem is that the required details for any kind of "fix" generally is missing from the reports (just a plain Magisk log is usually inadequate).
My guess is that it's likely caused by to aggressive OEM implementations of battery optimisation or the likes thereof.
Click to expand...
Click to collapse
I have already added magisk manager to unoptimized apps in battery, dont know what is wrong only @topjohnwu can help.
Right now i didnot flashed system because i want to figure jt out whh this is happening, i can test if topjohnwu guides what he needs
hope topjohnwu will fix it soon
I managed to get it work again. Sharing what i did in sequence:
1. Delete all module in magisk. Trash can icon. Reboot.
2. In magisk manager, uninstall > clear images. Reboot.
3. In magisk manager, uninstall > complete uninstall. Reboot automatically.
4. Reboot to recovery. Flash magisk uninstaller .zip. clear dalvik/cache. Reboot to system.
5. Install magisk manager apk. Reboot.
6. Reboot to recovery. Flash magisk 19.1 zip. Clear dalvik/cache. Reboot to system.
Try su at terminal trigger magisksu prompt after step 6.
Hope this helps.
I have a blu dash l 4.4.2 with twrp and I'm also facing this or similiar issue with su request rejected in log, permission denied in terminal, modules flash but magiskhide and superuser do not. I have tried many things with no luck.
No display over other apps, battery, or any other permission settings included. Only 20.4 flashes on my devices others say unsupported image format. 7.1.1 magisk manager seems to be only one which says additional update but then goes to setup failed. Magisk app settings others ok, tried toggling root access, canary settings crash. Have tried to copy and chmod rw 600 to libdirect file from another device to vendor and lib folders because my device does not appear to have it included. Minimal adb fastboot module tip no luck as well as reflashing stock.
Would like to try to add "(sleep) 1 to early_mount " as I read somewhere but not sure how exactly. No luck yet manually updating magisk.db but I am hoping there is someway to have it fully functioning automatically somehow. Any help much appreciated
i have the same issue ,i was rooting my huawei with magisk ..
To resolve this you need to go to magisk manager press install (the first one) ,recovery mode (if needed) and then direct install ,this worked for me
Good Morning. I have an elephone u pro with 660 snapdragom processor. I installed a custom rom that had as "SU" the magisk. the device was giving an error in the wifi that was not active (address mac 02: 00: 00: 00). so I entered magisk in the module session and installed the only module that has on wifi. I also installed a "GNU" package that has the. did not solve the problem of wifi so I uninstalled the modules and realized that it started to present another problem much bigger. (any camera that is installed from the playstore) displays the error "camera_disconnected (2)". another problem is the youtube app that just turns the ball and does not open the content. Another problem also set is the flashlight which is disabled. I returned to install the modules in the magisk and returned everything (except the wifi). only then turned everything off and nothing else solved. the strange thing is that I made the rom the "qfil" partition partition wipe and even then the problems persist (the wifi returns to normal in the rom stock). it's as if magisk erased files that go beyond the rom. I do not know what else to do. help, please
thanks god I was able to fix this problem by installing the rom stock. I think the problem was in the partitions. of both installing and uninstalling other roms I think gave file problem in some partition. I installed the stock and then applied a rooted version of it. At least I managed to solve the problem of wifi and camera.