I rooted my MD7 GS4, and Recently (re)discovered Xposed Modules. I figured, hey why not. I wanted as much of a stock experience as possible, but stupid little things like the Text Messages on the lockscreen bothered me.
After downloading and installing Xposed and Wanam, and rebooting, my phone seems to not get any service for a few minutes before finally getting cell service. while searching, at times it will even ask me to switch to global mode? and if I press cancel, sometimes "Sorry, com.android.phone has stopped" and it will freeze. sometimes it wont force stop and then my cell data FINALLY comes on.
I have since deleted and uninstalled Wanam, Xposed, removed the framework, and still having the issue. I just cant figure out what it may be.
I had the same issue. When you install wanam, it makes a backup of the features.xml file and removes most of the original text from thr file in /system/csc. Go there, see if there is a backup (will be called features.xml.bak and should be about 15 KB or so) and rename it to features.xml after deleting the current features.xml. Reboot. Voila. Profit.
Sent from my SCH-I545 using Tapatalk 4
roboots21 said:
I had the same issue. When you install wanam, it makes a backup of the features.xml file and removes most of the original text from thr file in /system/csc. Go there, see if there is a backup (will be called features.xml.bak and should be about 15 KB or so) and rename it to features.xml after deleting the current features.xml. Reboot. Voila. Profit.
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
Thanks,
Unfortunately, it still does not work. I deleted the new and renamed the .bak and now I'm still stuck on no service, and process stopped.
took about 6 minutes for cell service to come on.
I am having same problem since installing framework and related modules. Not having same length of delay but it's long enough to get attention. Sometimes it asks for SIM card to be installed. Still reading and searching for solution. Wiki check back later.
Thanks.
Sent from my SCH-I545 using xda app-developers app
I am finding this with the latest update 1.4.5. I TiBU back to 1.4.3 and don't see the problem. Then I used TiBU to not allow Wanam to auto update and all is well.
I found the same problem with Wanam or xTheme whenever I make changes with it and I just reboot and service comes right back. Or just don't use a soft reboot
justinisloco said:
I rooted my MD7 GS4, and Recently (re)discovered Xposed Modules. I figured, hey why not. I wanted as much of a stock experience as possible, but stupid little things like the Text Messages on the lockscreen bothered me.
After downloading and installing Xposed and Wanam, and rebooting, my phone seems to not get any service for a few minutes before finally getting cell service. while searching, at times it will even ask me to switch to global mode? and if I press cancel, sometimes "Sorry, com.android.phone has stopped" and it will freeze. sometimes it wont force stop and then my cell data FINALLY comes on.
I have since deleted and uninstalled Wanam, Xposed, removed the framework, and still having the issue. I just cant figure out what it may be.
Click to expand...
Click to collapse
I have the same device, with the same issues after installing Xposed and Wanam. None of the suggestions here worked for me. However, for me, normal operation resumed after deleting Wanam and the Xposed framework. I'd love to find a solution to this, so I could use the Xposed & Wanam.
kenkamm said:
I have the same device, with the same issues after installing Xposed and Wanam. None of the suggestions here worked for me. However, for me, normal operation resumed after deleting Wanam and the Xposed framework. I'd love to find a solution to this, so I could use the Xposed & Wanam.
Click to expand...
Click to collapse
Even deleting it didn't fix it for me. I ended up unrooting and going back to stock. Since then move stayed stock unrooted. If I can't get a ROM then I might as well stay safe
Sent from my SCH-I545 using Tapatalk 4
NilsP said:
I found the same problem with Wanam or xTheme whenever I make changes with it and I just reboot and service comes right back. Or just don't use a soft reboot
Click to expand...
Click to collapse
I know I am repeating myself but if you follow these steps you will be fine.
1) Apply whatever you want.
2) Exit out of whatever you are applying to home screen
3) Use the power button reboot option - Do Not use the reboot options in the xPosed modules
4) If you don't have signal bars in a few seconds when the lock screen come up just reboot with power again
Side note: Do not install or activate any more than 1 thing at a time. For example, install xPosed, reboot, install, Wanam, reboot, make selections in Wanam, then reboot. All reboots from the power button.
NilsP said:
I know I am repeating myself but if you follow these steps you will be fine.
1) Apply whatever you want.
2) Exit out of whatever you are applying to home screen
3) Use the power button reboot option - Do Not use the reboot options in the xPosed modules
4) If you don't have signal bars in a few seconds when the lock screen come up just reboot with power again
Side note: Do not install or activate any more than 1 thing at a time. For example, install xPosed, reboot, install, Wanam, reboot, make selections in Wanam, then reboot. All reboots from the power button.
Click to expand...
Click to collapse
I followed all your rules as I tried this again today, and still not having any luck. I have narrowed my problem down to the installation of Wanam. I did a reboot between each step of installing the Xposed framework, and had no issues there. Yet, after installing Wanam (and before activating the Wanam module) upon reboot, the phone cannot find cell service for at least a few minutes after booting up. Rebooting again (and again and again) makes no difference.
Related
Alright guys, I'm in need of some help.
I've been flashing MIUI on my Fascinate for months now and recently I've run into a problem. On RickS' 1.12.9 I'm getting a lot of FCs. About 24-48 hours after flashing and setting up my phone I get a notification at boot that every GApp along with TB, Facebook, Script Manager have "stopped unexpectedly" and need to be force closed. My flash process is as follows:
1) ODIN either DL09 or EH03
2) ODIN CWM4
3) 3 finger boot to CWM and flash RickS 1.12.9
4) Everything is fine up to here
5) TB - Restore missing user apps (just apps, not data)
6) Set up Supercharger script (update9 RC5 test 2), Voltage Control OC/UV, Glitch kernel leakage/screen state
7) Reboot
8) Wait about a day and a couple of reboots later for the force close party to start.
Has anyone run into a similar problem? I've tried a few solutions (i.e. mixing up my flash routine, fix permissions...)
Thanks,
EJ
EDIT: Also, whenever I flash weblexa's builds after step 7 I get stuck in a bootloop. I'm going to try to just flash it and reboot to see if I don't get stuck (which, if I don't probably means that something I'm doing while setting up my apps and such is the cause of the problems).
.Ejekt said:
Alright guys, I'm in need of some help.
I've been flashing MIUI on my Fascinate for months now and recently I've run into a problem. On RickS' 1.12.9 I'm getting a lot of FCs. About 24-48 hours after flashing and setting up my phone I get a notification at boot that every GApp along with TB, Facebook, Script Manager have "stopped unexpectedly" and need to be force closed. My flash process is as follows:
1) ODIN either DL09 or EH03
2) ODIN CWM4
3) 3 finger boot to CWM and flash RickS 1.12.9
4) Everything is fine up to here
5) TB - Restore missing user apps (just apps, not data)
6) Set up Supercharger script (update9 RC5 test 2), Voltage Control OC/UV, Glitch kernel leakage/screen state
7) Reboot
8) Wait about a day and a couple of reboots later for the force close party to start.
Has anyone run into a similar problem? I've tried a few solutions (i.e. mixing up my flash routine, fix permissions...)
Thanks,
EJ
EDIT: Also, whenever I flash weblexa's builds after step 7 I get stuck in a bootloop. I'm going to try to just flash it and reboot to see if I don't get stuck (which, if I don't probably means that something I'm doing while setting up my apps and such is the cause of the problems).
Click to expand...
Click to collapse
I have had this same issue, and for months it drove me nuts cause I couldn't figure out the problem.
It didn't happen so much with all google apps, mainly the market, but I did get it on others.
What used to work for the market, set your language in the phone settings. Not market settings, the phone. I set mine to English (United States) and I didn't get a FC on market since.
With other google apps, or other apps in general there are a couple a things you can try.
1. If you changed any permissions, i.e. disabled apps from loading on boot, turn them back on 1 at a time. When I disable Google Talk from loading.. I get FC's.
2. Try a clearing data/cache for the app and re-installing over the app... or clearing data/cache and uninstall... and re-install.
3. Have you changed your screen DPI? Below 190ish causes problems for me, like if I dial a number it FC's.
There is a couple more, I just got out of class and can't think of em for the life of me. I will post when it comes to me.
Hope this helps!
Maniac
MrManiacNF said:
I have had this same issue, and for months it drove me nuts cause I couldn't figure out the problem.
It didn't happen so much with all google apps, mainly the market, but I did get it on others.
What used to work for the market, set your language in the phone settings. Not market settings, the phone. I set mine to English (United States) and I didn't get a FC on market since.
With other google apps, or other apps in general there are a couple a things you can try.
1. If you changed any permissions, i.e. disabled apps from loading on boot, turn them back on 1 at a time. When I disable Google Talk from loading.. I get FC's.
2. Try a clearing data/cache for the app and re-installing over the app... or clearing data/cache and uninstall... and re-install.
3. Have you changed your screen DPI? Below 190ish causes problems for me, like if I dial a number it FC's.
There is a couple more, I just got out of class and can't think of em for the life of me. I will post when it comes to me.
Hope this helps!
Maniac
Click to expand...
Click to collapse
Thanks for the quick reply!
1) No permissions were changed.
2) I tried wiping davik/cache. As for the individual apps, the vast majority of the ones that are FCing are system apps; uninstalling isn't exactly an option unless I just remove them from the rom.
3) DPI hasn't been touched.
-EJ
I would be willing to bet you have alot of apps installed and your datadata folder is full. There is a thread on rootzwiki on how to fix this if uninstalling or moving apps to sd is not an option for you.
I have found a good work around for those of you who may enjoy more usable space on your screen. With the screen the S4 comes with it only makes sense to use it. Only follow these steps after you are running on Hyperdrive ROM successfully (I am guessing this will work with other roms as long as Xposed Framework can be installed).
Background Work (no major changes yet)
1) Open the app Hyperdrive Control
2) Navigate Custom Settings > Advanced Mods > Framework Installer
3) Click Install/Update
4) Select the tab 'modules' from the top
5) Check all the boxes you see (I had 3)
4) Click Reboot
Let's get started
1) Reopen Hyperdrive Control
2) Navigate Custom Settings > Advanced Mods > Per App DPI Settings
3) Select Google Keyboard
4) Turn the switch to ON
5) Enter 160 for DPI, 100 for Font and check the box labeled 'xlarge res'
6) Click save and click yes.
7) Repeat steps 4-6 with the apps Swype and Samsung Keyboard
8) Make sure you followed the above steps then continue
9) Now find an app called Android System from the list and select it.
10) Enter 280 and don't change anything else (I don't know what you would be doing so I stayed away)
11) Click save and click NO.
12) Restart and enjoy.
I went back and changed System UI to 340 as I didn't like how small the notification bar became. Also recommending ExDialer as the stock keypad won't 'stretch' and lastly as a must, look into a good launcher. I am using NOVA Prime.
If you want to undo changes you can simply turn everything 'Off' and click Save and No. Then restart.
Hopefully this helps some!
If I am missing anything or if anyone wants to add more detail let me know! Side note: random but AOSP helper was installed on my device also allowing easy toggle from 3G to 4G with JuiceDefender...
Colton
Mods can you list this as a [HOWTO]... sorry left that out.
awesome.. .thank you!
OMG thank you for this, i has given up on how to do anything on it. I did not know how to use Xposed frameworks, this is what i needed, than you very much:good:
Has anyone tried changing the overall system DPI and then changing just the misbehaving Samsung applications back to stock (i.e., Contacts/Dialer, Camera)? I pretty much manually set all of my apps to between 320 and 340, but the Notification dropdown is way too big. (Email and Gmail both at 320 in order to become usable).
This made my launcher grid super tiny and the keyboard is unusable it is so small. I can imagine how some slight DPI adjustment could be good, but this is aweful!
that being said, I will use this method to adjust things how I would like them.
I'm glad it worked well for you guys but both of those changes made things worse for me. I put it back on stock and am very happy with it.
I'm running 320 DPI in my build prop. To fix the dialer I went into the per app DPI and changed the contacts app and phone app to stock 480 DPI and also the calculator app as well. They all run just like stock now no problems at all
Forgot to mention gallery as well
Sent from my SCH-I545 using xda premium
im using 360 in my build.prop. and have had no problems. only thing i had to fix was my market. which i used this market found here
http://forum.xda-developers.com/showthread.php?t=1839871
using the correct version of the one in my current rom(hyperdrive). Dont ask me why this works. But someone else said they tried it and it worked. so i did and it worked. Sometimes ive noticed it will all the sudden on reboot, change to a different version of the market. But that has only happened a couple of times. and usually it didnt matter(most apps still showed up like normal). But i dont know that this will work the same way for everyone since it seems to be a semi flakey method.
It works fine in HyperDrive RLS 4. Don't try to change the build.prop for the first boot, though. Let it boot once, then change it. Let's just say that the results were a hung device first.
I added clock back to 480 because there are issues with it.. The year view in Calendar is a bit off, but that's the only screen that doesn't work right... The Market works fine at this resolution (360). This is much easier than what I was doing before...
Now Touchwiz can be somewhat usable as it isn't huge gigantic text everywhere (even on the Tiny selection in Screen)
My system ui keeps crashing whenever I change anything related to Android System. Followed the directions but no luck so far.
kcellb said:
My system ui keeps crashing whenever I change anything related to Android System. Followed the directions but no luck so far.
Click to expand...
Click to collapse
That's why I just went the other way around and changed build.prop then made things larger as needed. Less problems this way...
jeffreycentex said:
That's why I just went the other way around and changed build.prop then made things larger as needed. Less problems this way...
Click to expand...
Click to collapse
I will be the first to admit that I am not an expert at this in anyway. This is just how I got it to work...
You said Hyperdrive Build 4 is working for you? I flashed it and have had nothing but troubles so far. It always hangs at SAMSUNG Custom boot screen... I have tried everything and now once I went back to my Nandroid of 3.1 it boots up with no issue, Then I go to reboot through the power menu and it hangs on that screen again.
Colton
PS I guess an easier approach also to allow most programs to stay stock would be to allow the android system to stay stock and just change what you need like the launcher...
I had the same problem about system ui... make sure you are pressing NO to the option it gives you and then reboot. I also had some DPIs that the phone just didn't like (240)... everything kept fc'ing...
colton22 said:
I will be the first to admit that I am not an expert at this in anyway. This is just how I got it to work...
You said Hyperdrive Build 4 is working for you? I flashed it and have had nothing but troubles so far. It always hangs at SAMSUNG Custom boot screen... I have tried everything and now once I went back to my Nandroid of 3.1 it boots up with no issue, Then I go to reboot through the power menu and it hangs on that screen again.
Colton
PS I guess an easier approach also to allow most programs to stay stock would be to allow the android system to stay stock and just change what you need like the launcher...
I had the same problem about system ui... make sure you are pressing NO to the option it gives you and then reboot. I also had some DPIs that the phone just didn't like (240)... everything kept fc'ing...
Click to expand...
Click to collapse
I had problems with the first two downloads. Then I was able to get one to work early this morning... Also note that it is supposed to be a wipe'd flash, so make sure you do the format data/cache 3 times, then format system... I generally do a flash of the rom first to make sure that there aren't problems, though, before I format system...
I only use 320, 360, and 480's as DPI's on the S4.
Your approach is the way I used to do, but I wanted everything smaller, so every time I installed a program, I changed it to 320/360.. But then I wanted 320/360 to be the overall and only make exceptions for the things that demand stock DPI.
Understood - I didnt wipe to flash as i never did before without an issue. I am downloading stock ODIN now as something is up with my data partition...? It hangs on every second+ boot from restore/install and will not even boot off an install. I will go to stock odin, root, recovery and then install. Also downloading a fresh copy of Hyperdrive RLS4... Thank you for the tips.
C22
Found a better way!
Okay so I am now on RLS 10.2.0...
Download some type of Root file manager... I paid for/use Root Explorer love it.
Navigate to /system and long press build.prop
Find the line that contains screen density =480 and change it to your desired DPI (I am using 280)
From there all apps/everything is changed to that dpi... some stock apps you will have to use xposed to change them back to 480 just to make it work because they show different resolutions horribly.
I followed these steps...
http://forum.xda-developers.com/showthread.php?t=2269483
works great! Enjoy.. Also on the Multi DPI stock app post, the only one that works with the Verizion phone is the Gallery S4 v2.zip file... The others I am trying to work with the dev on getting up and running for our phones.
Colton22
deleted
Thanks
After a lot of trial and tribulation, I found a method to get long press on volume skipping tracks in all music apps. To be clear this works on STOCK ROOTED ME7.
If you need info on rooting, check out this thread
To get it working you need XPosed Framework and Wanam Xposed to send the correct long press command. This can then be intercepted by the HeadsetButton Controller app, available on Google Play, in order to skip tracks.
INSTALLATION
1) Install XPosed Framework. Then REBOOT
2) Install Wannam Xposed from the google play store and REBOOT.
3) Open up XPosed Installer, and click Install/Update. Reboot.
4) Open Xposed Installer again, and click the Modules tab. Click the check mark on Wanam Xposed. Reboot.
5) Open Wanam Xposed and click the Sound option. Make sure "Skip tracks with volume keys" is checked. Reboot.
6) Install HeadsetButton Controller . (There is a trial version available for you cheapskates ) Open it up, and go to the advanced settings. Make sure "Enabled" is checked. Make sure that under "Target music app" that "Currently running music app" is selected.
7) Finally, REBOOT and enjoy.
I know there's a lot of reboots. I'm not sure that all are necessary, but I do know that if you do follow all of these steps, you will be enjoying long press volume skip as much as I am.
I do all of that with only one reboot. Also you don't need the app. Volume skip works for me on me7.
Sent from my VZW Galaxy S4 using Tapatalk 4
nativi said:
I do all of that with only one reboot. Also you don't need the app. Volume skip works for me on me7.
Sent from my VZW Galaxy S4 using Tapatalk 4
Click to expand...
Click to collapse
Definitely doesn't work for me without the app.
ayemiller said:
Definitely doesn't work for me without the app.
Click to expand...
Click to collapse
Check out MoDaCo Toolkit xposed module. It also has that feature. And I know it works with that too. For me at least.
Sent from my VZW Galaxy S4 using Tapatalk 4
I'm on the previous stock release and have only rooted (and custom recovery for future use). I'd LOVE to get this feature back (had it on my GNex)
I thought the Xposed framework only worked on deodexed ROMs?
Interestingly the long press volume up is one of the only features I'm greatly missing (I use my phone on my motorcycle all the time and really want to get back the ability to skip tracks while riding). I was contemplating changing ROMs but really I'm happy w/ stock except for not having this.
Kidd_Funkadelic said:
I'm on the previous stock release and have only rooted (and custom recovery for future use). I'd LOVE to get this feature back (had it on my GNex)
I thought the Xposed framework only worked on deodexed ROMs?
Interestingly the long press volume up is one of the only features I'm greatly missing (I use my phone on my motorcycle all the time and really want to get back the ability to skip tracks while riding). I was contemplating changing ROMs but really I'm happy w/ stock except for not having this.
Click to expand...
Click to collapse
Don't know for sure whether or not it will work for MDK, but I'm guessing it would. And yes, Xposed framework works with regular, stock (rooted) ROMs.
It not happens always, but when it happens, it's always when the system is starting, when the apps are starting and being granted root permissions, etc. If I don't do anything, is fine, but If I unlock my screen while the apps are loading on startup and start to open some apps, it reboots(not always). I don't know If it overloads or something, but aLogcat doesn't record anything after the system reboots. I've already used Boot Manager to disable some apps from starting, but the problem persists. It's a Moto X 4.4.4 Stock and I never had this problem before. I belive t's a Xposed Module, but I want to know which one is. I've already did a factory reset, then rooted again, but the problem persists.(before I rooted I wasn't having this problem, this is why I believe it has to do with some Xposed Module or something related to root.)
PS: I will pay you 5 dollars(via Paypal) If you help me and find the problem (what's causing it) via these 2 logs. I know it isn't much, but I want to show some appreciation for helping me.
Here's the kernel message:
https://www.dropbox.com/s/5v9bcbsbqk3z3sq/kernel.pdf
Here's another one that I got right after the reboot happened.(I've waited for the device to start, connected my device to USB, then went to adb and wrote # adb shell dmesg.
https://www.dropbox.com/s/l2ghokfk2w97yv4/Kerneldef.pdf
Thanks.
Xposed Module
I belive t's a Xposed Module, but I want to know which one is.
Click to expand...
Click to collapse
Try to uninstall the modules one by one and see which one is causing the problem. What are the modules that you installed as of this moment?
PS: If you're rooted try wiping cache + delvik cache in case you didn't do that.
I've already tried cleaning the cache. Xposed modules: ActivityForceNewTask, Complete Action Plus, GravityBox, Smooth System Progress Bar, Statusbar Scroll to Top, Statusbar Volume, TintedStatusBar, XBlast Tools.
Just happened again. Uploaded another kernel log .
alex91s said:
I've already tried cleaning the cache. Xposed modules: ActivityForceNewTask, Complete Action Plus, GravityBox, Smooth System Progress Bar, Statusbar Scroll to Top, Statusbar Volume, TintedStatusBar, XBlast Tools.
Click to expand...
Click to collapse
Try uninstalling them all first and see what happens. Then install them one by one and check which one coincides with the others in order to see which one causes the problem.
I looked through as many threads as I could before post posting. I suddenly have an issue that is vexing me to no end. Certain apps, with no rhyme nor reason that I can discern, have suddenly become greyed out when attempting to install them via traditional means. . .and by that I mean, via the package installer. When using an app such as APK Installer Pro, I have no issue whatsoever. I am not running any apps such as screen dimmers that employ a screen overlay and I took the extra step to disable all screen overlays to test my theory. The only change I tried was playing with the Xposed Framework for Nougat. Upon installing it, I noticed this behavior. So, I deleted Xposed, reflashed my ROM (LineageOS for Shamu) and went back to exactly as I had before. I am really struggling with this. Any thoughts and/or help would be appreciated.
ClubWDW said:
I looked through as many threads as I could before post posting. I suddenly have an issue that is vexing me to no end. Certain apps, with no rhyme nor reason that I can discern, have suddenly become greyed out when attempting to install them via traditional means. . .and by that I mean, via the package installer. When using an app such as APK Installer Pro, I have no issue whatsoever. I am not running any apps such as screen dimmers that employ a screen overlay and I took the extra step to disable all screen overlays to test my theory. The only change I tried was playing with the Xposed Framework for Nougat. Upon installing it, I noticed this behavior. So, I deleted Xposed, reflashed my ROM (LineageOS for Shamu) and went back to exactly as I had before. I am really struggling with this. Any thoughts and/or help would be appreciated.
Click to expand...
Click to collapse
You updated to September security patch?
I believe so. I update the moment LOS releases their update.
ClubWDW said:
I believe so. I update the moment LOS releases their update.
Click to expand...
Click to collapse
I think it's a bug in all ROMs which have october security patch. From the package installer open recents apps and then select the installer again, that fix the problem.
It is a bug in LOS. If you'll minimize installation window, and execute it again from file manager - install button becomes active