Related
Hello everyone,
Here is my problem.
My background music (ttpod ) frequently get killed when I open browser or anything other thing, even when I am typing this right now got killed again.
I tried dozens ROM as stock, omega, android revolution...etc, all happens same thing.
I also tried Jkay and Xpose framework to whitelist it, but still...
Anything idea?
Sent from my GT-I9300 using xda premium
Did anyone answer you with this one? I can't restore anything Jkay in my settings it just says restore failed, even though I have not limited access for Jkay on anything?
qtwrk said:
Hello everyone,
Here is my problem.
My background music (ttpod ) frequently get killed when I open browser or anything other thing, even when I am typing this right now got killed again.
I tried dozens ROM as stock, omega, android revolution...etc, all happens same thing.
I also tried Jkay and Xpose framework to whitelist it, but still...
Anything idea?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Hey dude,
Jump on to the Xposed modules site and download the one called AppSettings_0.4.apk located here
Set this in Xposed to make it function. Open the app. Then go back to Xposed Privacy if you have it and enable this settings app to have full control. Then go back to the AppSettings apk and this should then allow you to search and should display all of your apks. This is your permissions controlller app now (not necessarily security like Xprivacy but more so the gateway for your Xposed framework. Think of it like a new toll road that has just been opened, it will allow a better route for traffic to flow to its destination, but there at the moment the toll booth is un-manned and the gates are shut so no one can use the toll road until you put a man in the booth to control the boomgates
Find Jkay app and check allow for all of its functions and bam everything working 100%
Really once you get used to this, this framework can allow for Jkay + more. Jkay should be porting his app to Xposed modules rather than trying to update every freakin framework release there is, especially considering that most of the functionality doesn't change between releases all that much. With Xposed he should publish for the top level of functionality and people who don't have a framework that is equiped with that functionality just won't get it, none of their apps will force close, nothing will screw up if they flash the incorrect version etc.
But....thinking about it, my feeling is that Jkay is more about the money than anything? If he was to do this he wouldn't make any money off people buying his app so I guess that will never work for him.
Jarmezrocks said:
Hey dude,
Jump on to the Xposed modules site and download the one called AppSettings_0.4.apk located here
Set this in Xposed to make it function. Open the app. Then go back to Xposed Privacy if you have it and enable this settings app to have full control. Then go back to the AppSettings apk and this should then allow you to search and should display all of your apks. This is your permissions controlller app now (not necessarily security like Xprivacy but more so the gateway for your Xposed framework. Think of it like a new toll road that has just been opened, it will allow a better route for traffic to flow to its destination, but there at the moment the toll booth is un-manned and the gates are shut so no one can use the toll road until you put a man in the booth to control the boomgates
Find Jkay app and check allow for all of its functions and bam everything working 100%
Really once you get used to this, this framework can allow for Jkay + more. Jkay should be porting his app to Xposed modules rather than trying to update every freakin framework release there is, especially considering that most of the functionality doesn't change between releases all that much. With Xposed he should publish for the top level of functionality and people who don't have a framework that is equiped with that functionality just won't get it, none of their apps will force close, nothing will screw up if they flash the incorrect version etc.
But....thinking about it, my feeling is that Jkay is more about the money than anything? If he was to do this he wouldn't make any money off people buying his app so I guess that will never work for him.
Click to expand...
Click to collapse
thanks anyway , i have ready solve this problem :good:
No problems man. I usually come back and answer my own questions on the forum so that when others search that they can know answers too. So I will leave my post up.
It wasn't just me was it? The information required to solve the problem WAS NOT easily located in the sea of information within the framework thread?
Hello, I dont know if I should be posting here or in the ROM thread, but this may not be ROM related.
I flashed a new ROM recently. I installed these apps from the Play Store to make sure they were working fine :
SwiftKey, Wakelock Detector, and Tapatalk
They worked well without any issues. Later I restored a backup with TiB of multiple apps, including Xposed modules. Now these apps crash upon start or in the case of SwiftKey, when I try to access my themes.
I have many apps. It's there an easy way to find out what the issue is? I'm guessing it's another app, most likely an Xposed module, but I can't imagine what it would be.
Any advice would be appreciated.
Never-ending, the offender was an Xposed module called Force Fastscroll
Never mind *
SuperSU doesn't seem to be working the way it always has on my other devices in the past. After successfully flashing TWRP 2.8.7.0 [6.0] EN (by Sminki *xda* repack) on my Honor 7 with multi-tool and then installing SuperSU via TWRP and gaining root access, I rebooted my phone and immediately Google Play wanted me to update the SuperSU app. I updated the SuperSU app and also installed SuperSU Pro that I had purchased previously on another device. I then installed terminal emulator so I could confirm that I had root access by running the su command. However after running the terminal emulator and attempting to use the su command nothing happened. I didn't get an error that I would expect if root wasn't present such as su not found, it just seems to sit there waiting. It then occurred to me that I hadn't received the usual popup from SuperSU asking me whether I wanted to grant root permission.
From what I have been able to work out I do have root access but for whatever reason SuperSU is not displaying its message asking me to grant or deny access. I have managed to establish that I do have root by going into the SuperSU settings and setting the default access as grant rather than prompt after which terminal emulator is able to use the su command.
Does anyone know how I can get the prompt to work? I would rather have SuperSU prompt me when an app requests root access for security reasons since giving any app that requests root unfettered access probably isn't the best idea.
If your problem has anything to do with SSU Pro then I dont say nothing cause dont use it.
Anyway going the same procedure as you I had, after GPlay update, the problem when trying to open SSU with message "SSU binary cant be found" or sth like this. However my SSU has been working (at least it did look alike) giving prompts.
The solution was SSU cleanup, copying and installing SSU once again. If you check some threads here you will find some kinds of initial problems with SSU are quite common.
It looks like it is H7 speciality ;p. You need to flash B330 twice for 100% and you need to install SSU twice ;p
ps. Also "Draw over other apps" on but it was automatic - at least for me
adxuser said:
If your problem has anything to do with SSU Pro then I dont say nothing cause dont use it.
Anyway going the same procedure as you I had, after GPlay update, the problem when trying to open SSU with message "SSU binary cant be found" or sth like this. However my SSU has been working (at least it did look alike) giving prompts.
The solution was SSU cleanup, copying and installing SSU once again. If you check some threads here you will find some kinds of initial problems with SSU are quite common.
It looks like it is H7 speciality ;p. You need to flash B330 twice for 100% and you need to install SSU twice ;p
ps. Also "Draw over other apps" on but it was automatic - at least for me
Click to expand...
Click to collapse
Thanks. Seems to be working now. Also disabling doze altogether on marshmallow seems to have solved a lot of other issues I was having since the marshmallow update and subsequent custom recovery and root install.
Squall88uk said:
disabling doze altogether on marshmallow
Click to expand...
Click to collapse
By "Doze" you mean those switches to kill apps after screen lock or not?
adxuser said:
By "Doze" you mean those switches to kill apps after screen lock or not?
Click to expand...
Click to collapse
No I mean Marshmallows built in doze feature. I have the switches you're talking about set to let the app keep running for important apps like SuperSU anyway but they only affect EMUIs own power manager. Doze and EMUIs power manager seem to fight each other anyway and I don't like how doze stops my notifications coming through with some apps and interferes with other apps that I like to leave running all the time like AcDisplay.
I completely disabled doze altogether using "dumpsys deviceidle disable" in terminal emulator or using adb shell. The only problem is that it will be re-enabled after a reboot so I used the universal init.d app to run an init.d script on every boot to disable it again since the honor 7 kernel doesn't natively support init.d. I have all the apps that I had on lollipop (plus some more that I didn't have on lollipop, since I didn't have root when I used lollipop) set up exactly the way they were then and let EMUI handle the power management. I get about the same battery life that I had in lollipop which is fine for me since I charge it fully every night anyway.
I am just in process of developing opinion on that. For sure made one mistake prefering Google Clock over Huawei (and uninstalling the latter) but now even with adequate settings (for example it should have auto-start set by PM Plus add-on for Phone Manager) I am not so sure of my alarms ; ) I have been accustomed to Vanilla Android till now.
Ok. I had to do my lecture on MM Doze & App Standby functions. Also I am newbie on EMUI.
It looks like that many important things (background GPS runnings apps, notifications, alarms) can be double complicated on MM Huawei :/ (not to mention other EMUI problems e.g. with lock screen)
We have clean MM Android with its problems even for Nexus owners, then we have EMUI with its own background / notifications problems.
So 'Ignore optimisations' switch is by Google. You do not use it but maybe know which Google / Huawei apps should have optimizations off? (I have there Android System WebView - why? Google product should have it invisible, Fused Locations - the same, HiSuite ?, HwAps ?)
Anyway people report that it does not help for GPS tracking apps shutdown problems, but it is rather related to EMUI I think.
PS. 1. I do not think Huawei / Google power managers fight in any way. Huawei power manager stricly speaking these are drivers for hardware needed + basic user power handling setup.
What they did on higher level is this "keeps running after screen off" switch but I would not be so sure if this, set one or the other way (and Huawei soft in general), works properly with GCM messages and other wakeups. One should keep in mind that Huawei sells a lot without Google apps at all.
PS.1.b. Some apps need some changes to work properly with Doze. They are not allowed now to do what they like and when they like. And if they have to say sth they must use GCM message , if they have sth important to say they must use GCM high priority message. Android 5.1 API level 22 alarms do not fire now, there are 2 new methods from what I read. And Google could block spamming "high priority messages". So idea & direction is good I think. For not MM updated apps put them in Ignored.
PS2. In my opinion also you should not confuse B330 power handling issues with Doze.
It could be just Huawei optimizing things: taking away fast charging switch because it is on default now, making changes to power handling etc. or not making changes needed so now it could be the problem with Android. People claiming worse battery life for B330 claim mostly best on B320.
adxuser said:
For sure made one mistake prefering Google Clock over Huawei (and uninstalling the latter) but now even with adequate settings (for example it should have auto-start set by PM Plus add-on for Phone Manager) I am not so sure of my alarms ; ) I have been accustomed to Vanilla Android till now.
Click to expand...
Click to collapse
What's wrong with the Google clock? And what problems did you have after uninstalling the Huawei clock? I use the Google clock as my main clock app and have had no issues with it on either lollipop or marshmallow even after uninstalling the Huawei clock.
adxuser said:
Ok. I had to do my lecture on MM Doze & App Standby functions. Also I am newbie on EMUI.
It looks like that many important things (background GPS runnings apps, notifications, alarms) can be double complicated on MM Huawei :/ (not to mention other EMUI problems e.g. with lock screen)
We have clean MM Android with its problems even for Nexus owners, then we have EMUI with its own background / notifications problems.
Click to expand...
Click to collapse
Agreed. While EMUI does have some of its own features that can be useful a lot of things are twice as complicated as they need to be. I have generally found that just allowing all apps that have notifications you want to receive e.g. twitter set to be allowed to autostart and run in the background as much as they like seems to reduce issues with notifications (still not worked out if it completely stopped any issues), and even then if I want notifications to display correctly on the lockscreen, not only do I need to allow them for each particular app on the lockscreen through the notification manager I still have to use a lockscreen replacement which in my case is AcDisplay. To be honest I have every app set to run on autostart and in the background and I still haven't found that it has much impact on battery life and this seems to solves a lot of these kinds of issues for me. My previous phone (Samsung Galaxy A3) used touchwiz and never had any of these options so I've always assumed that touchwiz/android allowed apps to run when they wanted and access what they wanted within the scope of their permissions and everything always worked fine, admittedly battery life was an issue on that phone but it had a much smaller battery capacity than the Honor 7 and it still lasted me most of a day.
adxuser said:
So 'Ignore optimisations' switch is by Google. You do not use it but maybe know which Google / Huawei apps should have optimizations off? (I have there Android System WebView - why? Google product should have it invisible, Fused Locations - the same, HiSuite ?, HwAps ?)
Anyway people report that it does not help for GPS tracking apps shutdown problems, but it is rather related to EMUI I think.
Click to expand...
Click to collapse
I tried messing with the Ignore optimisations switch when I first upgraded to Marshmallow and it didn't seem to make any difference apps were still being afflicted with issues. I asked honor uk exactly what it did and whether it was for doze or not and they didn't know. I'm sure if I spoke Chinese and asked the Chinese customer service they would be able to tell me straight away but I never managed to find out. Even with doze disabled completely on my device I still have it set to ignore optimisations for all apps in case its something to do with EMUI.
adxuser said:
PS. 1. I do not think Huawei / Google power managers fight in any way. Huawei power manager stricly speaking these are drivers for hardware needed + basic user power handling setup.
What they did on higher level is this "keeps running after screen off" switch but I would not be so sure if this, set one or the other way (and Huawei soft in general), works properly with GCM messages and other wakeups. One should keep in mind that Huawei sells a lot without Google apps at all.
Click to expand...
Click to collapse
What I meant by fight is that the 2 have their own settings rather than these being integrated with each other. So for example when specify that I want an app to be able to run in the background while the screen is off in an ideal world this would also tell Google's doze that I do not want it to doze that app. otherwise I have to effectively set the same thing twice even though it may be called different things.
adxuser said:
PS.1.b. Some apps need some changes to work properly with Doze. They are not allowed now to do what they like and when they like. And if they have to say sth they must use GCM message , if they have sth important to say they must use GCM high priority message. Android 5.1 API level 22 alarms do not fire now, there are 2 new methods from what I read. And Google could block spamming "high priority messages". So idea & direction is good I think. For not MM updated apps put them in Ignored.
Click to expand...
Click to collapse
I like the idea of doze in general and I'm generally a fan of most things that google do with android. If i was running a nexus or an AOSP rom I would definitely leave doze activated and only disable its optimization for apps that either coded with doze in mind or apps which I personally consider to be high priority regardless of whether google agrees such as twitter. I lie to get twitter notification that I have enabled as soon as the tweet they link to is tweeted not at the intervals that doze allows apps to update at. But that's a personal thing rather than an issue with the idea. So for YouTube notifications for example I would be quite happy for doze to run the show.
adxuser said:
PS2. In my opinion also you should not confuse B330 power handling issues with Doze.
It could be just Huawei optimizing things: taking away fast charging switch because it is on default now, making changes to power handling etc. or not making changes needed so now it could be the problem with Android. People claiming worse battery life for B330 claim mostly best on B320.
Click to expand...
Click to collapse
My intention has never been to confuse EMUI's power handling with Doze. I have just been trying to simplify the issue for me. as I have already said I generally allow any apps to do what they want both in EMUI's settings and by disabling doze as its simpler that way for me. Battery has never been an issue for me with either lollipop (B180) or marshmallow (B330) for me personally but i'm sure for some people it can be.
Squall88uk said:
What's wrong with the Google clock? And what problems did you have after uninstalling the Huawei clock? I use the Google clock as my main clock app and have had no issues with it on either lollipop or marshmallow even after uninstalling the Huawei clock.
Click to expand...
Click to collapse
nothing wrong, in fact I've chosen it deliberately.
Basically prefer Google apps cause they can be updated and whats more new features are added from time to time, with let's say B330 stock you are left with B330 stock unless and if Huawei pushes sth new.
Just for some producers ROM's there are sometimes apps good enough and also interconnected on some levels with launcher / lock screen / power management that it is better to leave them & even make use of them.
Squall88uk said:
Even with doze disabled completely on my device I still have it set to ignore optimisations for all apps in case its something to do with EMUI.
Click to expand...
Click to collapse
Rather strange for me what you're doing.
Squall88uk said:
What I meant by fight is that the 2 have their own settings rather than these being integrated with each other. So for example when specify that I want an app to be able to run in the background while the screen is off in an ideal world this would also tell Google's doze that I do not want it to doze that app. otherwise I have to effectively set the same thing twice even though it may be called different things.
Click to expand...
Click to collapse
It cant be integrated, it is Google licensed system. Doze & App standby these are powerfull, long-term features.
This EMUI function is just easy switch to kill sth after screen off. Not sure of it
Also not sure of this auto-start PM Plus utility It is not only auto-start on system start but also start on events. Powerfull mess with many apps without granular controls.
However I use both ;p
edit. ok, it looks you're right about Doze. I.e. Huawei Doze problem. Here for Mate 8:
http://forum.xda-developers.com/showpost.php?p=64827731&postcount=15
Not solved as I see (but no time to read everything)
So Paul @paulobrien solution is with his ROM, your solution is to shut down Doze, I would prefer Doze properly working on (rooted) stock solution
adxuser said:
The solution was SSU cleanup, copying and installing SSU once again. If you check some threads here you will find some kinds of initial problems with SSU are quite common.
Click to expand...
Click to collapse
I have the same problem on my tablet Huawei MediaPad T1 8.0 Pro.
Please explain exactly what supposed to mean is "SSU cleanup, copying and installing SSU once again".
If one makes SSU cleanup then root access will flee for good and installing SSU again encounter the stark barrier, right?
If of course by "cleanup" you mean SuperSU's SETTINGS -> CLEANUP -> Reinstall (?)
@ioy
Do you have EMUI 4.0 on your tablet?
Some tips & tricks work between some Huawei models but for sure not each on everyone...
Anyway I made (in SSU) cleanup for full unroot (if I remember correctly :/) and by "copying & installing" I mean H7 procedure to copy and install via TWRP.
So full unroot and full root once again and in my case it solved my problem.
@adxuser, and what is EMUI 4.0 and how to check if it is on the tablet?
Where to learn about these tip & tricks?
I do not have TWRP because I wanted to have warranty still intact so not unlocked bootloader, and that's why I have unrooted with KingRooot and afterwards switched to SuperSU with SuperSume.
Please, respond...
How to use cleanup options in SuperSu, there're several ones intended for switching to another su application - all of them work the way they need TWRP or maybe it is possible to switchin the system (booted)?
@ioy
what is EMUI 4.0 and how to check if it is on the tablet?
Where to learn about these tip & tricks?
I do not have TWRP because I wanted to have warranty still intact so not unlocked bootloader, and that's why I have unrooted with KingRooot and afterwards switched to SuperSU with SuperSume.
Click to expand...
Click to collapse
Emotion^^ User Interfece - Huawei visual & control overlay over Android.
For your http://www.gsmarena.com/huawei_mediapad_t1_8_0-6705.php 4.3 not upgradeble Android it is probably 2.0? (settings > about).
Tips & tricks those are some common to EMUI solutions - working on many Huawei models. They are nowhere together to be found, you have to search in all Huawei models if you are looking for sth. special. Anyway as you probably understand from JellyBean EMUI no.x to MM EMUI no.4.0 (or 4.1) that is a long way (some common things could even work however).
And also I am not a root specialist but if you have a locked bootloader SSU will never work so make a full cleanup and do not try again
Maybe this KingRoot will work but search for info on that.
ps. in most "normal" countries unlocked bootloader hasn't got anything to warranty.
Yes, KingRoot worked normally, prompt popup windows worked neatly.
However, Huawei itself warns if you unlock the bootloader then they will not help you anymore in case of trouble. And as you maybe know already, Huawei official assistance is needed in doing unlocking bootloader, it is done through their site and first this terrible warning is displayed... (presumably they register phone's IMEI, serial number and these data is then spread to warranty service outposts worldwide)
Yes, they can track and they probably track a lot more easily
Regarding warranty it may and it vary from continent/country to continent/country but local (e.g. european) regulations take effect on that matter.
So Huawei China can even track what I did with the phone yesterday at 6pm but when I am able to relock the phone (even with status relocked) and it could be seen that it is malfunctioning because of hardware failure then I am talking to Huawei in Europe and I am totally not interested what Huawei China has to say.
So sometimes there are some commom myths and you should check (in a proper way ) what are the possibilities.
And you have cited wrong model, this one is Huawei MediaPad T1 PRO LTE:
http://www.gsmchoice.com/en/catalogue/huawei/mediapadt18.0lte/Huawei-MediaPad-T1-8.0-LTE.html
It has 4.4.4 Android version, and Emotion UI version 2.3, so what are these tips & tricks for this?
Please try to provide any clue, about those tips& tricks in respect of popup windows, as as I can see usual popups for any application are not present in this Huawei model... Apparently something must block them in a regular manner...
ioy said:
And you have cited wrong model, this one is Huawei MediaPad T1 PRO LTE:
http://www.gsmchoice.com/en/catalogue/huawei/mediapadt18.0lte/Huawei-MediaPad-T1-8.0-LTE.html
Click to expand...
Click to collapse
Quite possibly. Just a quick look.
As you probably understand we are on H7 subforum and I am not interested in other devices with its variants.
ioy said:
It has 4.4.4 Android version, and Emotion UI version 2.3, so what are these tips & tricks for this?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=66946525&postcount=12
Allright, how is it possible to switch off / disable this EMUI? What to freeze without bricking the phone? Presumably indeed this blocks popup windows itself and at all it seems providing no gain, plain Android is better and there are many apps on PlayStore with genius functions and full user's control, so please which system or internal memory apks are responsible for this EMUI and one normally can freeze them thus freeing the 'core' Android system from this dubious attraction?
Greenify "went away" as did two apps it had hibernated, now I can't re-install them
Hi,
I recently rooted my AT&T LGv30 and installed TWRP and Magisk 1.6. I then installed Xposed via Magisk Manager and played with it a bit. I went on to install Greenify donation and enabled all the beta and aggressive stuff, as well as Xposed integration. I later discovered that Xposed breaks SafetyNet checks so I decided to remove it. When I did, Greenify "went away". I had to re-install it. It was only later that I noticed 2 other apps were missing, namely Xmeye (a security camera app notorious for consuming battery) and Spotify (here I was just playing around, but Greenify said it was using battery, so...). These were the only two apps I had added to Greenify.
I then attempt to re-install both of these apps from the Google Play store. It goes through the process of downloading, then installing, but at the end of the installation process, the Google Play button simply reverts back to "Install", as if nothing happened. The same thing happens when I try again, on either app. I can install any other app just fine.
I've run the latest Xposed uninstaller zip from recovery, but this didn't help. I do have a vague recollection of Greenify continuing to run in root + Xposed mode after Xposed had been removed, if that makes any sense. Eventually, after a subsequent re-install of Greenify (not if before or after Xposed was removed), it then walked my through the setup again, and is now running only in root mode. Yet, the problem with the two apps remains.
I'm hoping someone has a suggestion before I wipe everything and start over.
Thanks,
Daniel
Following up on my own post. I ended up installing SD Maid, which was able to show me both Spotify and Xmeye as "stopped". From the app I selected to delete both applications, which I could not do anywhere else, as they didn't show up in normal apps. My guess is that Greenify with Xposed and therefore root caused some file ownership issue that the normal utilities were not able to handle.
Daniel
DanielCeregatti said:
Following up on my own post. I ended up installing SD Maid, which was able to show me both Spotify and Xmeye as "stopped". From the app I selected to delete both applications, which I could not do anywhere else, as they didn't show up in normal apps. My guess is that Greenify with Xposed and therefore root caused some file ownership issue that the normal utilities were not able to handle.
Click to expand...
Click to collapse
Root cause likely resides elsewhere; Greenify doesn't mess with permissions.
Davey126 said:
Root cause likely resides elsewhere; Greenify doesn't mess with permissions.
Click to expand...
Click to collapse
Yet the two apps managed by Greenify stopped working. So you're saying correlation does not equal causation? Because the evidence here indicates otherwise. Just sayin'...
DanielCeregatti said:
Yet the two apps managed by Greenify stopped working. So you're saying correlation does not equal causation? Because the evidence here indicates otherwise. Just sayin'...
Click to expand...
Click to collapse
Correlation assumed but unproven. Greenify has been around a long time with a large user base. The situation you describe appears to be an outlier.
First off, T-Mobile version H932 rooted with bootloader unlocked and TWRP installed.
I was a long time user of Cyanogenmod/Lineage on other platforms in the past and overall prefer AOSP based ROMS that are close to stock. So, I have tried PixelExperience, Lineage, and LiquidRemix on my V30. I like them all but overall I like LiquidRemix the best mostly due to some of the LiquidLounge options.
However, I have 3 things I miss. I could probably do without them but I think my overall usefulness of the phone is better when I have them.
1. WiFi Calling - I have poor coverage in my office until TMO deploys Band 12 or Band 71 in my area. Not on schedule for almost a year yet.
2. OK Google support. I have tried numerous things to get this working on all 3 of the custom roms but it simply does not. Sounds like a MIC volume issue currently in all AOSP based ROMS on the V30. I use Android Auto (with a headunit) and not having this is kind of a pain.
3. Google Pay NFC support. I installed Magisk on all 3 custom ROMS but never could get it to fully pass all the safetynet checks.
As for running Stock. I know it would fix 1&2 above, but if I kept the device rooted and bootloader unlocked I am not sure #3 would be fixed. However, I can deal with that. What I hate about LG Stock overall is the interface, all their crap, and especially their dialer. I previously was side loading APK version of Google Dialer but it is missing the SPAM features and such unless you can flash it. I also sideloaded a pixel launcher and GCAM. But the dialer thing was always a pain.
I am going to try the debloated/magisk 20p STOCK. Anyone using this and have suggestions on how to get it working with Google Pay, Google Dialer, etc?
Next phone, I will probably spend the money on a pixel
Havoc is pretty awesome
TheCoryGuy said:
Havoc is pretty awesome
Click to expand...
Click to collapse
Yes, I'm sure it is. The guys doing custom ROMs do great work. But... Does I'm sure none of the 3 things I listed work on it.
Some day we'll get Wi-Fi calling in a custom ROM. One would think this would be more a standard method built into Android itself
I've got a H931 (basically daily driver with us998 20g) and a ls998 that I've used to test various roms and am now experimenting with serious debloating us998 20g on it.
I'm also accustom to Lineage, but as you know, there are not official builds for all devices. While the available roms are good, they are still a bit away from supporting all the basics.
In the meantime (and possibly for longer), just got through debloating the ls998. Now only 27 apps installed. Everything I need is working, very well actually. Looking at debloating even further. Watching to see if there are any ill effects.
It's difficult to determine what is the best, most productive way to go. At this point for me though I think it's debloating a stock rom. Time consuming but I hope worth it.
Good luck with your choice, Cheers
So I am on de-bloated stock with a few mods (google dialer, gcam, pixel launcher. Only thing not working at all is Google Pay. Magisk hide not working to fool it. Not a big deal.
thebitjockey said:
So I am on de-bloated stock with a few mods (google dialer, gcam, pixel launcher. Only thing not working at all is Google Pay. Magisk hide not working to fool it. Not a big deal.
Click to expand...
Click to collapse
That's easily fixed. Go to set->apps->google.services and delete cache and data. Make sure to hide magisk and any apps u don't want to see it first, reboot. Worked for me.
Cheers
AsItLies said:
That's easily fixed. Go to set->apps->google.services and delete cache and data. Make sure to hide magisk and any apps u don't want to see it first, reboot. Worked for me.
Cheers
Click to expand...
Click to collapse
Can you be more specific? I did what I think you mentioned:
Setup Magisk-Hide to hide from GPay, Google Play Store, and Google.
Cleared data and cache for Google Play Services (I assume that's what you meant?)
Rebooted, checked GPay, and it still says I can't use it because my device is rooted/altered.
Running Magisk 18.1, manager 7.1.1. Safetynet passes (both green checkmarks). What am I missing?
schwinn8 said:
Can you be more specific? I did what I think you mentioned:
Setup Magisk-Hide to hide from GPay, Google Play Store, and Google.
Cleared data and cache for Google Play Services (I assume that's what you meant?)
Rebooted, checked GPay, and it still says I can't use it because my device is rooted/altered.
Running Magisk 18.1, manager 7.1.1. Safetynet passes (both green checkmarks). What am I missing?
Click to expand...
Click to collapse
You're not running any Xposed modules, are you?
ChazzMatt said:
You're not running any Xposed modules, are you?
Click to expand...
Click to collapse
Nope, no Xposed at all, never installed it. Only one Masgisk module (Google dialer). VS996 20i otherwise (installed via TWRP... so stock rooted overall).
I thought I read that we need Magisk Canary now, as 18.1 isn't enough by itself. Another tip was to manually Magisk-Hide Google Play Services? I didn't want to dig in that deeply, if others are able to get by without these tricks...
schwinn8 said:
Nope, no Xposed at all, never installed it. Only one Masgisk module (Google dialer). VS996 20i otherwise (installed via TWRP... so stock rooted overall).
I thought I read that we need Magisk Canary now, as both 18.1 isn't enough by itself. Another tip was to manually Magisk-Hide Google Play Services? I didn't want to dig in that deeply, if others are able to get by without these tricks...
Click to expand...
Click to collapse
I don't know. Mine was hiding from Google Pay very well on18.0 and then 18.1 -- until I decided I cared more how my status bar icons looked than Google Pay.
So had to go Xposed route even though I know that can't be invisible from Safety Net. I made the choice on purpose.
ChazzMatt said:
I don't know. Mine was hiding from Google Pay very well on 18.1 until I decided I cared more how my status bar icons looked than Google Pay.
So had to go Xposed even though I know that can't be invisible from Safety Net.
Click to expand...
Click to collapse
Stock rooted US998.
* Battery circle with percentage number inside, instead of TWO stock LG battery icons (wasted space and looks ugly). How complete the circle is also indicates percentage.
* Actual LTE symbol, not silly"4GLTE".
* H for HSPA, not "4G".
* Gradient distinction for both carrier and Wi-Fi strength.
Some are build prop edits, but I'm also running two Xposed modules.
Sent via open market LG US998 V30/V30+
schwinn8 said:
Can you be more specific? I did what I think you mentioned:
Setup Magisk-Hide to hide from GPay, Google Play Store, and Google.
Cleared data and cache for Google Play Services (I assume that's what you meant?)
Rebooted, checked GPay, and it still says I can't use it because my device is rooted/altered.
Running Magisk 18.1, manager 7.1.1. Safetynet passes (both green checkmarks). What am I missing?
Click to expand...
Click to collapse
Funny, in that I just tried my procedure on my 2nd device and it didn't work - but still working / worked on the H931...
My guess is that on one, Titanium bkup wasn't installed (installed after enable gpay), on the other, already installed?
will post back if I figure it out.
Try magisk hide props module
Bupreno said:
Try magisk hide props module
Click to expand...
Click to collapse
What is "props module"?
schwinn8 said:
Can you be more specific? I did what I think you mentioned:
Setup Magisk-Hide to hide from GPay, Google Play Store, and Google.
Cleared data and cache for Google Play Services (I assume that's what you meant?)
Rebooted, checked GPay, and it still says I can't use it because my device is rooted/altered.
Running Magisk 18.1, manager 7.1.1. Safetynet passes (both green checkmarks). What am I missing?
Click to expand...
Click to collapse
Go to Magisk forum. It has detail instructions how to pass Google pay.
You have to install old version of Google service frame work in order to make it.
It's working fine on my phone.