Related
Hi,
I wish to permanently use the "Restrict background data" feature ( under settings->data usage ) on my JB rom, but the problem is that when I enable that feature, I always get a notification, asking me to "touch to remove" that feature...
I don't wish to do that, even by mistake! I want that notification GONE completely, but to retain the "restrict" feature...
I understand, it's possible to permanently disable notifications, by altering "Settings.apk" somehow - but I don't know what and where to change ( wish file inside that apk ).
I used "apktool" to unpack the apk, but again - which file should I change ? what value/line should I delete ?
My rom is VJ's AOKP v2.2, so "Settings.apk" file is from that rom's version.
Any help would be great :highfive::fingers-crossed:
EDIT:
Guess it has something to do with "DataUsageSummary.smali" (after unpacking the Settings apk -> smali\com\android\settings):
BUT WHAT SHOULD I CHANGE ?!
please reply
gps3dx said:
Any help would be great :highfive::fingers-crossed:
Click to expand...
Click to collapse
Seriously ? Not even the smallest hint you ppl can give me ?:crying::crying:
Can't you even redirect me to the most prevalent sub-forum, here at XDA, for that kind of question ?:silly:
gps3dx said:
Seriously ? Not even the smallest hint you ppl can give me ?:crying::crying:
Can't you even redirect me to the most prevalent sub-forum, here at XDA, for that kind of question ?:silly:
Click to expand...
Click to collapse
Something called the search function; it's really useful.
You can't just expect others to answer your questions promptly. As for your questions, that's part of the android system and if you want to modify it, go ahead. It's not a notification because you can't swipe it away; it's an ongoing thing. SO if you want to go on with that kind of attitude, you can try it yourself.
droid_<3er said:
Something called the search function; it's really useful.
As for your questions, that's part of the android system and if you want to modify it, go ahead. It's not a notification because you can't swipe it away; it's an ongoing thing.
Click to expand...
Click to collapse
I really do appreciate your reply man - even though I googled xda from top to button.
( there are thread about modifying various stuff inside settings.apk / SystemUI.apk - but NON are about that "restriction notification" i'm talking about. )
I've seen this thread in the unread threads of XDA app and although I don't use that feature, I got curious to try it out. So I've quickly put together an Xposed module that removes the notification.
You have to install Xposed framework. Get it here: http://forum.xda-developers.com/showthread.php?t=1574401
Also, install my module from the attachment, enable it and do a soft reboot in Xposed.
It works for me on my Galaxy R with CM10.1 and I assume it will work for you too, as the module doesn't change the Settings, but com.android.server.net.NetworkPolicyManagerService class. If you have any problems, post a logcat and /data/xposed/debug.log
Update: For a while now it's already available in Xposed modules repository: http://repo.xposed.info/module/org.adam77root.removerestrictednotification.
Adam77Root said:
I've seen this thread in the unread threads of XDA app and although I don't use that feature, I got curious to try it out. So I've quickly put together an Xposed module that removes the notification.
You have to install Xposed framework. Get it here: http://forum.xda-developers.com/showthread.php?t=1574401
Also, install my module from the attachment, enable it and do a soft reboot in Xposed.
It works for me on my Galaxy R with CM10.1 and I assume it will work for you too, as the module doesn't change the Settings, but com.android.server.net.NetworkPolicyManagerService class. If you have any problems, post a logcat and /data/xposed/debug.log
Click to expand...
Click to collapse
WOW thnx... but just a few moments before you posted your message I to fulfill that wish of mine... I SOLVED IT !
Although I admit - I DO NOT KNOW if I disabled all of the "restrict background" feature, but I DO managed to enable the "restrict backgound data" checkbox ( then press OK at the popup ) WITHOUT getting any notification at all !
HOW TO DISABLE NOTIFICATION ALERT FOR "RESTRICT BACKGROUND DATA" ( under settings-> data usage-> options )( I tried that fix on JB 4.2.2 ( to be specific: AOKP VJ Jelly Bean v2.2), BUT I guess it works on all JB 4.2.2 )1. copy "services.jar" from "/system/framework/services.jar" to your computer.
MAKE A SAFE COPY OF THIS FILE IF SOMETHING HAPPENS TO YOU.
2. extract the jar file using Winrar or any compatible app.
3. using MultiTool decompile the "classes.dex" file as instructed by Multitool's thread.
4. open with any txt editor ( I used Notepad++ ) the file "NetworkPolicyManagerService.smali" under "decompiled\classout\com\android\server\net\" ( which is a sub-folder of Mulitool's folder that you've previously extracted )
5. A . search for:
Code:
invoke-interface/range {v0 .. v6}, Landroid/app/INotificationManager;->enqueueNotificationWithTag(Ljava/lang/String;Ljava/lang/String;ILandroid/app/Notification;[II)V
delete completely that line or add "# " in the start of that line ( which is what I did ) so that line looks like that:
Code:
# invoke-interface/range {v0 .. v6}, Landroid/app/INotificationManager;->enqueueNotificationWithTag(Ljava/lang/String;Ljava/lang/String;ILandroid/app/Notification;[II)V
B. search for:
Code:
invoke-virtual {v0, p1}, Ljava/util/HashSet;->add(Ljava/lang/Object;)Z
add "# " in the start of that line ( which is what I did ) or delete completely that line
6. SAVE that smali file that you've just edited.
7. using Multitool, recompile the classes.dex file.
if everything went good, you'll have classes.dex file under MultiTool's sub-folder named "output"
8. using Winrar, open "services.jar", replace the current "classes.dex" with the recompiled one that you've made.
9. copy the remade "services.jar" to your device(using adb etc ):
Code:
adb push "services.jar" /system/framework/services.jar
10. chmod "services.jar" to "-rw-r--r--", meaning you need to:
Code:
adb shell chmod 644 /system/framework/services.jar
11. restart your device, and It should rebuilt your dalvik cache.
ONLY if it didn't, I guess you should delete "/data/dalvik-cache/[email protected]@[email protected]" file, reboot again so your OS will create that dalvik-cache file.
I'll be happy to know if anyone can verify that indeed my fix just remove his/her notification, but retain the ability to disable background data. THANKS !
Sorry I doubted you. You are a genius!
Many thanks!!
Adam77Root, thank you so much for that module! I can confirm it working on my Galaxy Note 2. That notification was unbelievably annoying.
gps3dx, thank you too for this thread and your fix. While I didn't try it because I already have Xposed framework installed and I'd rather use the less invasive approach, I am still grateful for your seeing a problem, addressing it, and proactively doing something about it. My respects to you. I searched around quite a bit and came across many other forums on different sites where people had this same problem unanswered. I hope they find their way to this thread.
To the above poster who jumped down the OP's throat for bumping this topic 4 days after it went unanswered, obviously you didn't do any search on this topic yourself. I did. And until this thread, I found nothing really useful. And lo-and-behold, someone was kind enough to actually do something useful instead of pointlessly sitting there and criticizing. The squeaky wheel gets the grease. Rudely telling someone to 'check their attitude and search' is not helpful- it's just rude and pointless. Just FYI.
I have an i9300 and I can't find the first line in that archive...
eXtremeDevil said:
I have an i9300 and I can't find the first line in that archive...
Click to expand...
Click to collapse
mybe it is because you run JB 4.1.2 not 4.2.2 like I do, plus mybe you're running some custom framework ( it is not AOKP as I suspect from you sig )
Adam77Root said:
...I've quickly put together an Xposed module that removes the notification.
Click to expand...
Click to collapse
@Adam77Root
Big thanks for this module: I installed another 4.2.2 JB rom for my HTC Desire, and your module works !:good::good:
Adam77Root said:
I've seen this thread in the unread threads of XDA app and although I don't use that feature, I got curious to try it out. So I've quickly put together an Xposed module that removes the notification.
You have to install Xposed framework. Get it here: http://forum.xda-developers.com/showthread.php?t=1574401
Also, install my module from the attachment, enable it and do a soft reboot in Xposed.
It works for me on my Galaxy R with CM10.1 and I assume it will work for you too, as the module doesn't change the Settings, but com.android.server.net.NetworkPolicyManagerService class. If you have any problems, post a logcat and /data/xposed/debug.log
Click to expand...
Click to collapse
this was working fine on my aokp jb mr1 Milestone 2, but stopped working when i installed the nigthly nightly (jb-mr1)2013-08-21 (wich fixes my camera issues and soe other stuff)
is there anything i can try myself to fix this or is it just incopatible with that nightly? (its still 4.2)
I'm using Lenovo phone, 4.2.1 Version. In "services.jar" I see only folder "META-INF" and file "MANIFEST.MF". I tried to rename the file to classes.dex then using MultiTool decompile but I receive: "Unexpected top-level exception:java.lang.RuntimeException:bad magic value...etc"
So what's wrong, where to find classes.dex? Someone?
new edit: Thanks a lot for all the replies, also Xposed framework+module didn't work.
Adam77Root said:
I've seen this thread in the unread threads of XDA app and although I don't use that feature, I got curious to try it out. So I've quickly put together an Xposed module that removes the notification.
You have to install Xposed framework. Get it here: http://forum.xda-developers.com/showthread.php?t=1574401
Also, install my module from the attachment, enable it and do a soft reboot in Xposed.
It works for me on my Galaxy R with CM10.1 and I assume it will work for you too, as the module doesn't change the Settings, but com.android.server.net.NetworkPolicyManagerService class. If you have any problems, post a logcat and /data/xposed/debug.log
Click to expand...
Click to collapse
Thanks a lot. Works awesome. Is it possible to post the source code to this?
css771 said:
Thanks a lot. Works awesome. Is it possible to post the source code to this?
Click to expand...
Click to collapse
I'm almost certain I don't have the original files anymore. Since it's pretty simple, you can either decompile the apk or check Android source of the class I mentioned in the post you quoted. Only one function is replaced with returning null.
Edit: Just checked, the function is enqueueRestrictedNotification.
Sent from my OmniROM-powered LG Optimus 4X HD
Xposed module works perfect on LG G2. Thanks a bunch!
Sent from my VS980 4G using Tapatalk
Adam77Root said:
I've seen this thread in the unread threads of XDA app and although I don't use that feature, I got curious to try it out. So I've quickly put together an Xposed module that removes the notification.
You have to install Xposed framework. Get it here: http://forum.xda-developers.com/showthread.php?t=1574401
Also, install my module from the attachment, enable it and do a soft reboot in Xposed.
It works for me on my Galaxy R with CM10.1 and I assume it will work for you too, as the module doesn't change the Settings, but com.android.server.net.NetworkPolicyManagerService class. If you have any problems, post a logcat and /data/xposed/debug.log
Click to expand...
Click to collapse
nice module.. work perfectly.. thanks
rooting?
do i have to root my phone to do this? will the module work without rooting? i'm new to playing with codes on my phone but I have done a lot of work with linux before so i can understand the process, i've just never rooted my phone before. i'd really like to get rid of this notification and the "usb connectivity" app's notification: internal storage &SD card- internal storage &SD card connected to PC. I mean, do i really need a notification to tell me that my phone is connected to my PC?
that last request isn't as important, at least if i accidentally click on that i'm not turning on background data use!
-yasboss
xperia z1s
jb 4.3
(just joined xda devs)
p.s.
is this the right place to ask this question?
yasboss said:
do i have to root my phone to do this? will the module work without rooting? i'm new to playing with codes on my phone but I have done a lot of work with linux before so i can understand the process, i've just never rooted my phone before. i'd really like to get rid of this notification and the "usb connectivity" app's notification: internal storage &SD card- internal storage &SD card connected to PC. I mean, do i really need a notification to tell me that my phone is connected to my PC?
that last request isn't as important, at least if i accidentally click on that i'm not turning on background data use!
-yasboss
xperia z1s
jb 4.3
(just joined xda devs)
p.s.
is this the right place to ask this question?
Click to expand...
Click to collapse
you need root to use xposed installer..
what else can it be used for?
ajeesh vijayan said:
you need root to use xposed installer..
Click to expand...
Click to collapse
can i use it for other notifications like i asked? I mean there's more than just the USB connectivity etc
Hello,
I've seen many threads implying that editing your build.prop file is simple, yet many other threads exclaiming that people have bricked their devices.
Has anyone successfully edited their SGH-T989/D phones to emulate the SGH-1337M? I have an odd reason, but I don't want to screw up.
Here is a link to the Galaxy S4 (I9500) build prop:
http://www.androidpolice.com/2013/0...gb-system-dump-leaked-and-ready-for-download/
Here is a link to the SIIx build.prop:
http://forum.xda-developers.com/showthread.php?t=1697142
How simple is this process? Which lines should I edit? What is your recommended editor app?
Thanks, I'd rather ask now than beg for solutions later.:fingers-crossed:
fishstick2k8 said:
Hello,
I've seen many threads implying that editing your build.prop file is simple, yet many other threads exclaiming that people have bricked their devices.
Has anyone successfully edited their SGH-T989/D phones to emulate the SGH-1337M? I have an odd reason, but I don't want to screw up.
Here is a link to the Galaxy S4 (I9500) build prop:
http://www.androidpolice.com/2013/0...gb-system-dump-leaked-and-ready-for-download/
Here is a link to the SIIx build.prop:
http://forum.xda-developers.com/showthread.php?t=1697142
How simple is this process? Which lines should I edit? What is your recommended editor app?
Thanks, I'd rather ask now than beg for solutions later.:fingers-crossed:
Click to expand...
Click to collapse
What exactly are you trying to do in the build prop to emulate the S4?
smokinjoe2122 said:
What exactly are you trying to do in the build prop to emulate the S4?
Click to expand...
Click to collapse
Maybe 'emulate' is the wrong word, but I am under the impression that I can swap the model number by changing the ro.product.model in the build.prop file. I want Google to think my SIIx is an S4 so I can access advanced apps that aren't optimized for my SIIx.
Here is a guide I found for simpletons like myself, but I just want to see if anyone else has done so successfully.
http://forum.xda-developers.com/showthread.php?t=1948558
I got impatient and changed the model number in the Build.prop and the phone did not brick. The System Settings on the phone does in fact confirm the updated model number as being SGH-1337M but the Play store hasn't updated the device yet so I can't confirm if my 'illusion' has completely worked.:laugh:
Get play store set correctly
http://www.howtogeek.com/116456/how-to-install-incompatible-android-apps-from-google-play/
looks like you done it all right except for the final step.
I changed my build.prop to make my LG L70 work with my Gear 2 watch. The watch got boring so I sold it, now I am looking to switch it back. I copied the original and tried to delete the modded one and it did not allow me. I tried to manually edit build.prop and it wouldnt save.
Any of you know how to revert?
Change permissions to rw
Sent from my MB855 using XDA Free mobile app
zzEvilGeniuszz said:
I changed my build.prop to make my LG L70 work with my Gear 2 watch. The watch got boring so I sold it, now I am looking to switch it back. I copied the original and tried to delete the modded one and it did not allow me. I tried to manually edit build.prop and it wouldnt save.
Any of you know how to revert?
Click to expand...
Click to collapse
yess...
if you have rooted your phone and then edited your build.prop with a change in android version....
then you have to root it again, and then go through the same process....
Hello!
This morning i was just looking in build.prop when ive seen a line regarding multi-window.
On EMUI 5 / Android 7, we can enable MultiWindow by pressing for few seconds the multitasking/recents icon in the navigation bar.
This feature is available on EMUI 4.1 as well.
REQUIREMENTS:
- EMUI 4.1
- Unlocked bootloader
- Rooted phone
- a file manager with root support ( im using the good old version of ES File Explorer)
Click to expand...
Click to collapse
[HOW-TO] Huawei Nova:
1) Grant root access to the file manager.
2) Go to /system and open build.prop.
3) Search for ro.huawei.multiwindow and change it from false to true.
ro.huawei.multiwindow=false becomes ro.huawei.multiwindow=true.
4) Save and reboot. After reboot, you can use MultiWindow by pressing for few seconds the multitasking / recents icon from navigation bar.
Click to expand...
Click to collapse
[HOW-TO] Other Huawei phones:
If you have followed the instructions for Huawei Nova and it didnt work, then check if you have HwMwLauncher folder in /system/app or /system/priv-app.
If it is missing, then check this post. People reported that MultiWindow is working after they got HwMwLauncher.
CONFIRMED DEVICES:
- Huawei Honor 8
If your phone isnt on this list, then it doesnt mean that it doesnt work. Just try and report back. I think it should work on all Huawei phones which are running EMUI 4.1.
Click to expand...
Click to collapse
EDIT: I just seen that you can use MultiWindow by swiping up two fingers on navigation bar too.
When you are in Multiwindow with 2 apps open, press HOME button.
I have a big bug!
The Home is in half screen.
VNS-L21C432B170
Emui 4.1.2
Inviato dal mio HUAWEI VNS-L21 utilizzando Tapatalk
millo1978 said:
When you are in Multiwindow with 2 apps open, press HOME button.
I have a big bug!
The Home is in half screen.
VNS-L21C432B170
Emui 4.1.2
Inviato dal mio HUAWEI VNS-L21 utilizzando Tapatalk
Click to expand...
Click to collapse
I have no issues. When I press home button it just disable MultiWindow.
Nova CAN-L11 running EMUI 4.1 CANC432B100.
Maybe this is my firmware problem... I don't know.
But only with home button.
With back button all is ok.
Screenshot:
http://cloud.tapatalk.com/s/58ff90231cc85/Screenshot_2017-04-25-20-02-43.png?
Inviato dal mio HUAWEI VNS-L21 utilizzando Tapatalk
I enabled this on my mate 7 with emui 4 marshmallow quite a while ago. If I try to use it I just get a pop up message saying this application does not support dual windows. Haven't found a practical use for it yet.
RobboW said:
I enabled this on my mate 7 with emui 4 marshmallow quite a while ago. If I try to use it I just get a pop up message saying this application does not support dual windows. Haven't found a practical use for it yet.
Click to expand...
Click to collapse
It's same for me.
When you press the "+" on homescreen after you enable MultiWindow I think it shows only the apps which support it.
Personally, I'm not using MultiWindow. I just wanted to share the small trick I've found.
Strange - it doesn't seem to have any effect on my rooted Honor 8 (still on MM with EMUI 4.1).
I used BuildProp Editor to set ro.huawei.multiwindow=true and rebooted. Holding the "recents" button does nothing apart from a quick burst of haptic feedback after about half a second or so.
Any ideas?
Thanks.
stooby said:
Strange - it doesn't seem to have any effect on my rooted Honor 8 (still on MM with EMUI 4.1).
I used BuildProp Editor to set ro.huawei.multiwindow=true and rebooted. Holding the "recents" button does nothing apart from a quick burst of haptic feedback after about half a second or so.
Any ideas?
Thanks.
Click to expand...
Click to collapse
Exactly the same phone and software here but it shows the toasts messages and the MultiWindow interface but doesn't work. I think EMUI 4.1 is simply Nougat ready and that is the reason why it has the option to enable or disable MultiWindow but the system (MM) has not this function and that is why it doesn't work. So the result is only the GUI of MultiWindow being shown but is only EMUI trying to do something as layer that system in fact isn't capable.
I was wrong follow @#Henkate instructions here here
stooby said:
Strange - it doesn't seem to have any effect on my rooted Honor 8 (still on MM with EMUI 4.1).
I used BuildProp Editor to set ro.huawei.multiwindow=true and rebooted. Holding the "recents" button does nothing apart from a quick burst of haptic feedback after about half a second or so.
Any ideas?
Thanks.
Click to expand...
Click to collapse
carmeloamg said:
Exactly the same phone and software here but it shows the toasts messages and the MultiWindow interface but doesn't work.
Click to expand...
Click to collapse
1) Do you have HwMwLauncher.apk in /system/app/HwMwLauncher or /system/priv-app/HwMwLauncher ? I don't think it matter if it is in app or priv-app, but it must exist. I have it in /system/app.
2) After you enable MultiWindow, do you see the process named HwDualWindowLauncher at Settings > Developer Options > Running services (check also cached processes there)?
3) In build.prop I have the following line: ro.config.hw_multiscreen=true. I think it might be related to MultiWindow as well, but I'm not sure. I didn't try yet to set it to false and see what happens.
carmeloamg said:
I think EMUI 4.1 is simply Nougat ready and that is the reason why it has the option to enable or disable MultiWindow but the system (MM) has not this function and that is why it doesn't work. So the result is only the GUI of MultiWindow being shown but is only EMUI trying to do something as layer that system in fact isn't capable.
Click to expand...
Click to collapse
Well, it works for me on Nova CAN-L11 running EMUI 4.1
MultiWindow has been introduced in Android 6. Why Huawei hid this option in EMUI 4.1 (Android 6) and introduced it as a new feature in EMUI 5 (Android 7)? That's what I'm asking too.
#Henkate said:
1) Do you have HwMwLauncher.apk in /system/app/HwMwLauncher or /system/priv-app/HwMwLauncher ? I don't think it matter if it is in app or priv-app, but it must exist. I have it in /system/app.
2) After you enable MultiWindow, do you see the process named HwDualWindowLauncher at Settings > Developer Options > Running services (check also cached processes there)?
3) In build.prop I have the following line: ro.config.hw_multiscreen=true. I think it might be related to MultiWindow as well, but I'm not sure. I didn't try yet to set it to false and see what happens.
Click to expand...
Click to collapse
1). I don't have HwMwLauncher.apk in either location (or anywhere, in fact).
2). No, I don't see the HwDualWindowLauncher process running.
3). I tried that, but it doesn't appear to have any affect.
Thanks anyway.
I'm not too bothered whether this works or not, but if it can be enabled, I will just for the fun of it!
stooby said:
1). I don't have HwMwLauncher.apk in either location (or anywhere, in fact).
2). No, I don't see the HwDualWindowLauncher process running.
3). I tried that, but it doesn't appear to have any affect.
Thanks anyway.
I'm not too bothered whether this works or not, but if it can be enabled, I will just for the fun of it!
Click to expand...
Click to collapse
The missing HwMwLauncher could be the problem since it is related to MultiWindow.
I've uploaded HwMwLauncher folder from my Huawei Nova.
1) Download HwMwLauncher.zip from HERE and extract it.
2) Copy HwMwLauncher folder to system/app.
3) Set the correct permissions for folders and files (.apk and .odex). I've attached screenshots with the permissions as well. The permissions of oat and arm64 folders must be same as the one for HwMwLauncher folder. And the permission of .odex file must be same as .apk one.
4) Reboot. Now I'd say that it should work. Make sure that ro.huawei.multiwindow=true in build.prop, but also ro.config.hw_multiscreen=true (just in case, I still don't know the purpose of this line as I didn't try to set it to false yet).
@carmeloamg :
If you don't have HwMwLauncher neither, then follow the same steps I've wrote in this post and report if it works.
#Henkate said:
The missing HwMwLauncher could be the problem since it is related to MultiWindow.
I've uploaded HwMwLauncher folder from my Huawei Nova.
1) Download HwMwLauncher.zip from HERE and extract it.
2) Copy HwMwLauncher folder to system/app.
3) Set the correct permissions for folders and files (.apk and .odex). I've attached screenshots with the permissions as well. The permissions of oat and arm64 folders must be same as the one for HwMwLauncher folder. And the permission of .odex file must be same as .apk one.
4) Reboot. Now I'd say that it should work. Make sure that ro.huawei.multiwindow=true in build.prop, but also ro.config.hw_multiscreen=true (just in case, I still don't know the purpose of this line as I didn't try to set it to false yet).
Click to expand...
Click to collapse
That's fixed it!
Thanks for your help.
#Henkate said:
The missing HwMwLauncher could be the problem since it is related to MultiWindow.
I've uploaded HwMwLauncher folder from my Huawei Nova.
1) Download HwMwLauncher.zip from HERE and extract it.
2) Copy HwMwLauncher folder to system/app.
3) Set the correct permissions for folders and files (.apk and .odex). I've attached screenshots with the permissions as well. The permissions of oat and arm64 folders must be same as the one for HwMwLauncher folder. And the permission of .odex file must be same as .apk one.
4) Reboot. Now I'd say that it should work. Make sure that ro.huawei.multiwindow=true in build.prop, but also ro.config.hw_multiscreen=true (just in case, I still don't know the purpose of this line as I didn't try to set it to false yet).
@carmeloamg :
If you don't have HwMwLauncher neither, then follow the same steps I've wrote in this post and report if it works.
Click to expand...
Click to collapse
I didn't have it. Placed and fixed but it only allows to use three system apps as second window even having some other multi window ready apps. For instance I've got WhatsApp and Telegram I can use multi window each one separately with gallery, files and videos but not both together. Snapshot attached. Same for you @stooby ?
Thanks @#Henkate !
very easy and smart! working very well without problems ...thanks
carmeloamg said:
I didn't have it. Placed and fixed but it only allows to use three system apps as second window even having some other multi window ready apps. For instance I've got WhatsApp and Telegram I can use multi window each one separately with gallery, files and videos but not both together. Snapshot attached. Same for you @stooby ?
Thanks @#Henkate !
Click to expand...
Click to collapse
Yes, same for me. When I had my Note 4, there was an Xposed module that enabled all apps for multi window use. Unfortunately, it's not working on these devices. I'll keep investigating.
stooby said:
Yes, same for me. When I had my Note 4, there was an Xposed module that enabled all apps for multi window use. Unfortunately, it's not working on these devices. I'll keep investigating.
Click to expand...
Click to collapse
HONOR 8: Installing this version of HwMwLauncher makes the multi window natively supported apps to be selectable and the multiwindow_whitelist_apps.xml file placed in /cust/hw/normal/xml make it usable from many other apps that before says not compatible. Only two issues, sometimes launcher (nova launcher) gets stuck on half of it size buy as it comes it goes. The other issue is that you can not use two apps that not appear in HwMwLauncher, just able to open one that is not and then launch another that is on it. See screenshots (example using chrome and instagram).
#Henkate said:
The missing HwMwLauncher could be the problem since it is related to MultiWindow.
I've uploaded HwMwLauncher folder from my Huawei Nova.
...
Click to expand...
Click to collapse
VNS-L21C432B170 Emui 4.1.2 (P9 lite)
I tried now again...
and now it works good!
tested in Portrait and Landscape.
No issues at the moment!
Thanks a lot
working here to
wishing for a fix for Knuckle Sense too...ive searched for that app everywhere with root explorer and just cant find it...
Knuckle sense is renamed branded Qeexo Finger Sense... double knock for screenshot/draw a letter to open an App. ect.
its activated in Intelligence Assistant but not working ...
looks like its disabled by root
---------- Post added at 04:11 PM ---------- Previous post was at 03:55 PM ----------
I have found in /system...
knuckle_gesture.bin...
but cant open it
1) Install File Explorer Root Browser
2) Go to System folder
3) Scroll all the way down and opet build.prop file
4) Add these 2 lines at the end of the file:
Code:
ro.lge.proximity.delay = 150
mot.proximity.delay = 150
5) Save the file
6) Reboot
is this a permanent fix or what?
and how did u figure it out?
thx by the way
It should be permanent. Waiting to see will it stay fixed after rom update tho.
I did a lot of research, tried some apps but it did not work, and finally found this fix on some chinese forum.
mr_techno said:
1) Install File Explorer Root Browser
2) Go to System folder
3) Scroll all the way down and opet build.prop file
4) Add these 2 lines at the end of the file:
5) Save the file
6) Reboot
Click to expand...
Click to collapse
Delay is already set at 200 in build.prop. I doubt just changing the delay fixes much.
Keep us posted on the fix…ya never know
fox_xda2 said:
Delay is already set at 200 in build.prop. I doubt just changing the delay fixes much.
Keep us posted on the fix…ya never know
Click to expand...
Click to collapse
Well I did not have delay in my build.prop (using pixel experience plus rom) and so far, no more issues with the sensor. Maybe try and change it to 150? What rom are you using?
mr_techno said:
Well I did not have delay in my build.prop (using pixel experience plus rom) and so far, no more issues with the sensor. Maybe try and change it to 150? What rom are you using?
Click to expand...
Click to collapse
PE 10.
AFAIK the instable proximity sensor issue is due to a poor driver released in a Xiaomi firmware, nothing so easy to solve.
Just registered to say my formerly non-operational proximity sensor now works perfectly (Pixel Experience)! Thanks very much.
Sentox6 said:
Just registered to say my formerly non-operational proximity sensor now works perfectly (Pixel Experience)! Thanks very much.
Click to expand...
Click to collapse
Mine too following the OP instructions ?
fox_xda2 said:
Delay is already set at 200 in build.prop. I doubt just changing the delay fixes much.
Keep us posted on the fix…ya never know
Click to expand...
Click to collapse
Worked with OP instructions.
Sent from my Redmi Note 7 using XDA Labs
Thanks, it worked perectly on PE 9!
Thanks a lot! Worked wonderfully on PE 9!
if this fix doesnt work and youve tried all kinds of "fixes" you may want to check out this if you have previously changed the screen or frame or had any hardware repair done to your xiaomi redmi note 7, there may be small peices you forgot to install. https://forum.xda-developers.com/redmi-note-7/how-to/fix-xiaomi-redmi-note-7-proximity-t4008965
Did it, seems that solved my problem to hear whatsapp audios outside in the sun. Ty
For now works like a charm in MIUI 11.0.3.0 Global, thanks.
:good:
Just want to say thanks for this fix. Works with PE10 with latest Delta update. For those who don't want root can uninstall magisk after editing build prop no problem at all
CR Droid 6.2 12JAN release. Nothing has changed unfortunately with this trick :crying:
Thanks. I am on Havoc 3.1 and the it fixed it.
Well, this can be included for sure, if y'all can let me know this actually works, I'd add the prop to the device tree. Thanks!
Hi, I want to disable the High volume warning, I already have a solution, right now I use terminal shortcut pro and have created a shortcut to run the command
Code:
settings put global audio_safe_volume_state 0
it work great but doesn't survive a reboot so I have to run the shortcut after every reboot. I found an old thread on reddit that say adding the line
Code:
audio.safemedia.bypass=true
to build.prop can also disable the high volume warning, but the thread was so old, they were talking android 6.0
I plan to try to add this prop on boot using the magisk module MagiskHide Props Config, I know it work great because I already added a prop to reduce the media volume steps to 15 instead of 30, but i dont know if the prop
Code:
audio.safemedia.bypass=true
is still working on android 10
Another solution would be to have an app that run the terminal command
Code:
settings put global audio_safe_volume_state 0
automatically after boot, but I would prefer to add the prop line if anyone can confirm it still work on android 10
Thank you all !
Nice to know.... what's also wondering from time to time how to overcome the warning. let me know if you get it to a working solution.
Just for the last part: tasker would be the way to go.
Gesendet von meinem HD1903 mit Tapatalk
xe0r said:
Nice to know.... what's also wondering from time to time how to overcome the warning. let me know if you get it to a working solution.
Just for the last part: tasker would be the way to go.
Gesendet von meinem HD1903 mit Tapatalk
Click to expand...
Click to collapse
After 24 hours testing the audio.safemedia.bypass=true with MagiskHide Props Config, I have not seen the warning yet, but I need to test it longer to be sure it work
Just a quick update for future search, the prop
Code:
audio.safemedia.bypass=true
seem to work, I have not seen the high volume warning for the whole week, so problem solved !
Hey one question, how were you able to edit the build.prop file? Whenever I try to do so with Root Explorer, it doesn't save my changes. OnePlus 8 Pro Android 10
memocatcher said:
Hey one question, how were you able to edit the build.prop file? Whenever I try to do so with Root Explorer, it doesn't save my changes. OnePlus 8 Pro Android 10
Click to expand...
Click to collapse
Only with Magisk module MagiskHide Props Config
jacobyo7 said:
Just a quick update for future search, the prop
Code:
audio.safemedia.bypass=true
seem to work, I have not seen the high volume warning for the whole week, so problem solved!
Click to expand...
Click to collapse
Hello and thank you for finding a workaround for this stupid issue! Do you know if this is still working on android 11? After installing the module, how can I correctly set it? Thank you so much for your help
I tried setting it with termux but it's not working
addsfsds said:
I tried setting it with termux but it's not working
Click to expand...
Click to collapse
I still use it with 11 on my OP7T but I am unsure if this prop remove the audio warning or if there is no warning at all on my device. Never tried 11 wihtout the prop so IDK.
Another way you can try is the system UI tuner app on the play store, there is a setting to disable the warning under the audio & sound category. Good luck !
jacobyo7 said:
I still use it with 11 on my OP7T but I am unsure if this prop remove the audio warning or if there is no warning at all on my device. Never tried 11 wihtout the prop so IDK.
Another way you can try is the system UI tuner app on the play store, there is a setting to disable the warning under the audio & sound category. Good luck !
Click to expand...
Click to collapse
Thank you for your reply! I kept trying to no avail. Can't make it work unfortunately. When you upgraded to android 11, did you make the procedure again from scratch? Can you please explain what you did on termux?
Is the system ui app an app that it's aways on background?
Thank you so much!
addsfsds said:
Thank you for your reply! I kept trying to no avail. Can't make it work unfortunately. When you upgraded to android 11, did you make the procedure again from scratch? Can you please explain what you did on termux?
Is the system ui app an app that it's aways on background?
Thank you so much!
Click to expand...
Click to collapse
No the system UI tuner app just change some hidden android settings, it do not run in the background. The description of the app even state you can delete the app once you changed the desired setting. Read the whole description to understand how it work. Try it, I think this might be the best solution.
SystemUI Tuner - Apps on Google Play
PLEASE READ ENTIRE DESCRIPTION BEFORE INSTALLING
play.google.com
jacobyo7 said:
No the system UI tuner app just change some hidden android settings, it do not run in the background. The description of the app even state you can delete the app once you changed the desired setting. Read the whole description to understand how it work. Try it, I think this might be the best solution.
SystemUI Tuner - Apps on Google Play
PLEASE READ ENTIRE DESCRIPTION BEFORE INSTALLING
play.google.com
Click to expand...
Click to collapse
Thank you for your kind suggestion. I tried and again it didn't work, really don't know why.
addsfsds said:
Code:
settings put global audio_safe_volume_state 0
Thank you for your kind suggestion. I tried and again it didn't work, really don't know why.
Click to expand...
Click to collapse
i can confirm that no app does change the setting of safe volume limit.
All tests on rooted device from LOS14-LOS19. Tried different apps like systemuituner, safevolumelimitdisabler, volumesteps+, jamesdsp etc.
Tried to patch the global variable "safe_media_volume" like described here on a rooted device but no luck.
Just ran
[adb shell] settings put global audio_safe_volume_state 0
via adb, when the message popped up, afterits i had to confirm the nag-screen, to raise the volume. it's so weird..