Related
I was looking since a while for a transparent stautsbar for the nexus one running CM7.
Pendo made one running on CM7 nightly #62.
In the post there are some screenshots, if you want to see, how it looks like.
Great thanks to pendo for his awesome work!
UUU yes please, this would hit the spot.
Looks nice, another vote here
Out of interest I tried flashing the Desire HD file, it rebooted twice and then worked. The mods work when the screen is locked and then revert to it's previous look once unlocked. Therefore it may not take a whole lot to actually port this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I found this have not tried but will later:
http://forum.xda-developers.com/showthread.php?p=7377678#post7377678
http://forum.androidcentral.com/lg-optimus-s-rooting-roms-hacks/49049-how-port-theme.html
http://samsunggalaxysforums.com/showthread.php/736-Port-Any-Android-Theme-to-Any-Build
Sergio PC said:
I found this have not tried but will later:
http://forum.xda-developers.com/showthread.php?p=7377678#post7377678
http://forum.androidcentral.com/lg-optimus-s-rooting-roms-hacks/49049-how-port-theme.html
http://samsunggalaxysforums.com/showthread.php/736-Port-Any-Android-Theme-to-Any-Build
Click to expand...
Click to collapse
Thanks for the helpful links! I'll give it a try
Would it not be possible to do this using the uot kitchen
http://uot.dakra.lt/
Sent from my Nexus One using Tapatalk
Here ya go...semi-transparent status bar, also a semi-transparent shade. All the rest is stock (well, I also put a new shade handle on it).
Flash in recovery
CM7-N1-trans_status_shade.zip
pendo said:
Here ya go...semi-transparent status bar, also a semi-transparent shade. All the rest is stock (well, I also put a new shade handle on it).
Flash in recovery
CM7-N1-trans_status_shade.zip
Click to expand...
Click to collapse
Hi pendo,
first at all, thx so much for your effort!! But i'm afraid, it doesn't work on my N1.
I wiped dalvik and cache, flashed the zip-file via recovery. I tried it on ADW Launcher EX and Go Launcher EX with Wallpaper hack unchecked.
Are there any tips you can give?
zahni_tue said:
Hi pendo,
first at all, thx so much for your effort!! But i'm afraid, it doesn't work on my N1.
I wiped dalvik and cache, flashed the zip-file via recovery. I tried it on ADW Launcher EX and Go Launcher EX with Wallpaper hack unchecked.
Are there any tips you can give?
Click to expand...
Click to collapse
Well...I'm unsure, lol. I made a few downloads yesterday morning and it was working all fine. I didn't expect this, but I suppose it makes sense now that I actually think about it but even though this hack is done in the /system/app directory, it IS build specific. That was built using CM-7.0.2.1 Is that what you're running?
I just tried it on yesterdays nightly and no-go...lol. SystemUI FC.
So, if you're on another build you can let me know, or if you know how to work in smali, you can either decompile the apk or baksmali the classes.dex file. You need to edit StatusBarService.smali. For a transparent pull down, search for
Code:
.method onBarViewAttached
go down 5 lines of text and if you see this
Code:
const/4 v5, 0x2
then you change it to this. It may already be that.
Code:
const/4 v5, -0x3
Also, double check the same 5 lines under
Code:
.method onTrackingViewAttached
For a transparent status bar, in that same file you need to edit
Code:
method protected addStatusBarView
The value we need to change isn't conveniently at the beginning of the method, like the other 2, it's in the middle. Easiest way to locate it is just to copy this text and search for it:
Code:
invoke-direct/range {v0 .. v5}, Landroid/view/WindowManager$LayoutParams;-><init>(IIIII)V
When you find that, the line directly above it change
Code:
const/4 v3, 0x2
to
Code:
const/4 v3, -0x3
Then recompile and viola
pendo said:
Well...I'm unsure, lol. I made a few downloads yesterday morning and it was working all fine. I didn't expect this, but I suppose it makes sense now that I actually think about it but even though this hack is done in the /system/app directory, it IS build specific. That was built using CM-7.0.2.1 Is that what you're running?
I just tried it on yesterdays nightly and no-go...lol. SystemUI FC.
So, if you're on another build you can let me know, or if you know how to work in smali, you can either decompile the apk or baksmali the classes.dex file. You need to edit StatusBarService.smali. For a transparent pull down, search for
Code:
.method onBarViewAttached
go down 5 lines of text and if you see this
Code:
const/4 v5, 0x2
then you change it to this. It may already be that.
Code:
const/4 v5, -0x3
Also, double check the same 5 lines under
Code:
.method onTrackingViewAttached
For a transparent status bar, in that same file you need to edit
Code:
method protected addStatusBarView
The value we need to change isn't conveniently at the beginning of the method, like the other 2, it's in the middle. Easiest way to locate it is just to copy this text and search for it:
Code:
invoke-direct/range {v0 .. v5}, Landroid/view/WindowManager$LayoutParams;-><init>(IIIII)V
When you find that, the line directly above it change
Code:
const/4 v3, 0x2
to
Code:
const/4 v3, -0x3
Then recompile and viola
Click to expand...
Click to collapse
Well, i'm afraid i am not familiar with smali. but i'm running CM7.0.2.1. So i guess, this can't be the problem
Any other idea?
zahni_tue said:
Well, i'm afraid i am not familiar with smali. but i'm running CM7.0.2.1. So i guess, this can't be the problem
Any other idea?
Click to expand...
Click to collapse
which recovery are you using?
pendo said:
which recovery are you using?
Click to expand...
Click to collapse
i'm running CWM 3.0.0.5.
zahni_tue said:
Well, i'm afraid i am not familiar with smali. but i'm running CM7.0.2.1. So i guess, this can't be the problem
Any other idea?
Click to expand...
Click to collapse
which recovery are you using? edit, I missed your reply.
I'm wondering if it even installed. Did the handle to close the status bar change? If it didn't, that would indicate that it didn't actually flash.
If you have root explorer, you can copy SystemUI.apk from that zip and copy/paste it in /system/app.
If it did in fact install, but you still aren't getting transparency, then I'm not sure what happened. I just repeated the exact same steps for the latest nightly #62 and this is what I see:
Just a note....this does not work with SPB Shell 3D. If I get a chance I'll try to see why, but my guess is it may be difficult.
pendo said:
which recovery are you using? edit, I missed your reply.
I'm wondering if it even installed. Did the handle to close the status bar change? If it didn't, that would indicate that it didn't actually flash.
If you have root explorer, you can copy SystemUI.apk from that zip and copy/paste it in /system/app.
If it did in fact install, but you still aren't getting transparency, then I'm not sure what happened. I just repeated the exact same steps for the latest nightly #62 and this is what I see:
Click to expand...
Click to collapse
Oh man, i don't know what i'm doing wrong, but i just did the same as you did: i did wipe dalvik and cache, flashed the nightly #62 and then your zip-file, reboot.
After booting, a FC of systemUI occurs
Perhaps i have to do a full wipe? I'll give it a try tomorrow...
Anyway, great thanks to you pendo!!
I just hope, to have a nice statusbar like yours on the screenshot!
zahni_tue said:
Oh man, i don't know what i'm doing wrong, but i just did the same as you did: i did wipe dalvik and cache, flashed the nightly #62 and then your zip-file, reboot.
After booting, a FC of systemUI occurs
Perhaps i have to do a full wipe? I'll give it a try tomorrow...
Anyway, great thanks to you pendo!!
I just hope, to have a nice statusbar like yours on the screenshot!
Click to expand...
Click to collapse
Oh no...my bad I should've been more clear. I didn't use the same actual file for nightly 62, but I repeated the same procedure for enabling the transparency with it.
Here...I made another one that doesn't have all my blue signal bars and stuff. This IS for nightly 62:
CM7-N1_nite62-trans_status-shade.zip
pendo said:
Oh no...my bad I should've been more clear. I didn't use the same actual file for nightly 62, but I repeated the same procedure for enabling the transparency with it.
Here...I made another one that doesn't have all my blue signal bars and stuff. This IS for nightly 62:
CM7-N1_nite62-trans_status-shade.zip
Click to expand...
Click to collapse
Hey pendo, thx a lot for your fast response!
I flashed this zip-file, but now it stopped at the screen with the google logo
Do you think, a full wipe can solve this problem?
zahni_tue said:
Hey pendo, thx a lot for your fast response!
I flashed this zip-file, but now it stopped at the screen with the google logo
Do you think, a full wipe can solve this problem?
Click to expand...
Click to collapse
well, this is quite embarrassing....the SystemUI.apk is fine. Works as I said, but I carelessly left a modified services.jar for an evo that I had made earlier in the framework directory of that zip. So that was the problem.
In the highly unlikely event you haven't already restored to a working condition, I've included services.jar from #62 with this download. It is safe to flash if you have restored as well. Wiping shouldn't be required with this...I just tested flashing this package (not just pushing the apk) without wiping and it worked fine. I've fixed the link above, but I'll include it again here. Please accept my appologies...I really did manage to make this much more difficult for you than it needed to be.
CM7-N1_nite62-trans_status-shade.zip
@ Pendo: Thanks man looking good. But once you change wallpaper it goes back to black status bar. Although it is still transparent in lock screen.
@ zahni_tue: What if you edit the first post and turn it into the transparent status bar thread?
Sergio PC said:
@ Pendo: Thanks man looking good. But once you change wallpaper it goes back to black status bar. Although it is still transparent in lock screen.
Click to expand...
Click to collapse
Disable the wallpaper hack in ADW.
Introduction
This is the optimal method for reducing and almost eliminating rotation lag in EpicMTD CM7. For those of you looking for the old method that involved hacking framework.jar, please see the second post in this thread, Deprecated (Old, Archaic) Rotation Lag Fix How-to
DISCLAIMER
I have personally used this method and know it works. Furthermore, many others have used this method and it seems pretty reliable. That said, should anything unpleasant happen, to include bugs being introduced, your phone bricking, or your firstborn child emerging as the anti-christ, well, it's not my fault. You did it.
Rotation Lag Eliminator Guide
If you have a ROM setup that you're fond of, or high-scores that you want to keep, I recommend doing some backups
Nandroid from ClockworkMod Recovery ("CWM") will backup your entire ROM, which you can restore after the fix and have your phone back to the state it was in before you made the backup. (Kentucky.)
Alternatively, after step 5 you can restore just the /data partition from a previously-created Nandroid backup.
Titanium Backup can back up & restore individual apps and settings, as well as restore from a previously created Nandroid backup.
Flash a GB ROM (not sure if it must be MTD, but I recommend it), I recommend toadlife's Clean-GB MTD
Go to [Settings] > [Display] > [Horizontal Calibration]
Calibrate. (Obvious, no?)
Flash your favorite EpicMTD CM7 Nightly, AKA the latest one. (You know I'm right!)
Think to yourself "That AmericanJedi001 just might be a genius. He damn sure knows how to fix rotation lag!"
Immediately follow that with the self-rebuttal "Yeah, but it's not like this required anything previously unknown in this community."
Caveats & Notes
Slight risks are involved in flashing ROMs and backing up and restoring Nandroids and individual apps.
This fix should persist across ROM flashes, and therefore Nightly flashes. There may be something that breaks it, but I haven't found it yet. (I'm not trying to break it, but I don't know where the calibration data is saved, therefore I don't know what mods will break it.) I suspect that either a) switching minor versions of Android, such as going from Froyo / 2.2 to Gingerbread / 2.3; or b) switching partition maps, such as going from BML to MTD, is what breaks it.
Thanks and Acknowledgements
Thanks to Decad3nce for pointing out that not everyone has had issues with rotation lag in EpicMTD CM7, which got me to thinking that the framework.jar hack might not be the optimal fix.
ISSUES / PROBLEMS / BUGS?
I'm reluctant to provide any active support for this fix because all of its steps are well-known and -documented elsewhere. That said, if you have any issues that you think are specific to rotation-lag elimination, post 'em here. If you post something in the vein of "I flashed blah-blah-blah and now my phone figuratively resembles a brick..." or "Why won't my backup restore?" I'm going to ignore you, because that's not specific to this fix. Those questions have been beaten like Jim Caviezel in Passion of the Christ, and like his character sometimes I wonder how they're not dead yet. Please use good judgement before you look for help here.
Deprecated (Old, Archaic) Rotation Lag Fix How-to
Introduction
This is the old, deprecated fix for minimizing rotation lag in EpicMTD CM7. It has been superceded by the method described in the OP above. Feel free to play with this hack, but know that I will not be supporting it, nor will I go any deeper into the how-to guide: this is a moderately broad overview, and the details of learning how to hack .jar files will be left to the reader to discover. I learned 95% of this hack by searching and reading what others had done, not by asking people to spoon-feed me instructions. Take that to heart!
DISCLAIMER
I have tested the framework.jar file and the flashable .zip on my own phone, with awesome results. However, I refuse to be held accountable for any issues you may have.
Installation
-- "framework.jar" Replacement Method
Delete or rename /system/framework/framework.jar (I recommend you simply rename it so that if you have issues you can easily switch back to your "stock" file
Copy framework.jar to /system/framework, then reboot.
???
Profit from the blazing rotation speed!*
-- Flashable .zip Method
Copy EpicMTD_CM7_Rotation_Lag_Eliminator.zip to the root of your SD card
Boot into CWM Recovery (or possibly ACS Recovery?)
Flash the "EpicMTD_CM7_Rotation_Lag_Eliminator.zip" file
Breakdance.
Reboot and enjoy a lag-free* experience!
-- Caveats
THIS METHOD IS DEPRECATED! USE THE METHOD IN THE OP TO FIX YOUR ROTATION LAG PERMANENTLY, RATHER THAN HAVING TO HACK framework.jar FOR EACH NEW RELEASE!
* At least one person has successfully replaced framework.jar, but was not impressed with the improvement in rotation speed
Users of previous versions of this fix reported their phones hanging during boot (I have never experienced this)
One person reported that menus were changed, but I suspect he flashed this fix (created specifically for CM7) on top of another ROM
For other GB ROMs the fix should be basically the same, though I would recommend using the framework.jar from that specific ROM. See the Resources section below if you're interested in learning the technical end of the fix.
Downloads
-- Standalone File
framework.jar - Pulled from CM7 Nightly-10 (4G Toggle in Notification Widgets)
-- Flashable .zip
EpicMTD_CM7_Rotation_Lag_Eliminator.zip - Pulled from CM7 Nightly-10 (4G Toggle in Notification Widgets)
-- Resources
my post in Chris41g's EF02 Rotation Lagfix topic
Chris41g's original fix for EF02
ISSUES / PROBLEMS / BUGS?
I will no longer support this hack. I have since learned of a much better method for almost eliminating rotation lag, a method that persists across ROM flashes and therefore does not require updating periodically when new versions of framework.jar accompany a new release of CM7. This is here simply because I can't delete the topic, and for historical interest.
Thanks and Acknowledgements
Thanks to Chris41g for the original fix, without stumbling upon that topic I would never have figured this out myself!
How-to Overview
With chris41g's original fix, here's what he had to say about it:
chris41g said:
...some framework edits will need to be made [to] \system\framework\framework1.jar.out\smali\android \view\WindowOrientationListener.smali
Code:
.prologue
.line 54
const/4 v0, 0x3
needs to be changed to
Code:
.prologue
.line 54
const/4 v0, 0x2
Click to expand...
Click to collapse
I pulled my "/system/framework/framework.jar", then pulled "classes.dex" from there and smali'd it, then browsed "...\classout\android\view\WindowOrientationListener.smali" in Eclipse. I found
Code:
.method public constructor <init>(Landroid/content/Context;)V
.registers 3
.parameter "context"
.prologue
.line 67
const/4 v0, 0x3
invoke-direct {p0, p1, v0}, Landroid/view/WindowOrientationListener;-><init>(Landroid/content/Context;I)V
.line 68
return-void
.end method
which is the closest to what chris41g posted for the original fix. I changed the "0x3" to read "0x0".
I then baksmali'd it into "classes.dex" and inserted that back into framework.jar, which is then copied into /system/framework, replacing the stock framework.jar. Done!
If anybody has any insight, tips, improvements, etc., send 'em! This is my first real contribution that involved any coding (not that I did much!) and I want to learn anything you Grand Masters have to share.
will this also have an effect on miui? not that the lag is bad or anything, but less is more in this case
FrankyFiggz27 said:
will this also have an effect on miui? not that the lag is bad or anything, but less is more in this case
Click to expand...
Click to collapse
As I stated above, I'm not an expert developer, so take this with a grain of salt... If you're experiencing rotation / orientation-change lag with MIUI on GB, first try using the"Horizontal Calibration" option in [Settings] > [Display]. You may have to apply it with your phone face-down, just hanging over the edge of the table/desk/counter so you can click the button to calibrate. If that doesn't work or is unavailable, try the"sensorcalibutil_yamaha" fix (you must be rooted for this):
Open a terminal emulator
Type "su" [Enter], then "/system/sensorcalibutil_yamaha" [Enter]
Follow the instructions to calibrate
If that doesn't work--and if you're using a GB ROM, I don't think it will--then the fix I posted above is your only other option. Should you decide to try it, I highly recommend you build your own "framework.jar" by pulling it from your ROM of choice and following the instructions provided by chris41g and me. If it works, let me know and I'll add it to the OP and change the title to reflect what ROMs we have framework.jars and/or flashable zips for. Good luck!
* FYI, I have no experience beyond CM7 with GB ROMs, & I've only used SRF ROMs & related kernels with Froyo.
AmericanJedi001
This can be fixed in the cyanogenmod framework source code
Good first attempt. There's a problem with your patch though. It messes up the homescreen menu and shutdown popup. if you are on homescreen and press menu, there is usually a tab that says "More" and has the unlock/lock desktop option, the patch changes this to "text from clipboard" also when you hold the power button and select shut down, the popup says reboot instead of power off. I think the problem is just a matter of line spacing being off in the Framework.jar or something, but this is an uneducated guess. Either way just wanted you to be aware. I think a better option would be to have it edit that one line of text in the framework.jar rather than replacing the .jar file completely. Good luck, happy coding.
AmericanJedi001 said:
...If that doesn't work or is unavailable, try the"sensorcalibutil_yamaha" fix...
Click to expand...
Click to collapse
sensorcalibutil_yamaha was pulled from gb...
counterfeit187 said:
Good first attempt. There's a problem with your patch though. It messes up the homescreen menu and shutdown popup. if you are on homescreen and press menu, there is usually a tab that says "More" and has the unlock/lock desktop option, the patch changes this to "text from clipboard" also when you hold the power button and select shut down, the popup says reboot instead of power off. I think the problem is just a matter of line spacing being off in the Framework.jar or something, but this is an uneducated guess. Either way just wanted you to be aware. I think a better option would be to have it edit that one line of text in the framework.jar rather than replacing the .jar file completely. Good luck, happy coding.
Click to expand...
Click to collapse
Editing a single line in a jar file isn't currently possible via CWM flash - this is the same reason themes and mods must often be combined, because they are modifications to the same file, and we can only replace files, not merge them
Sent from my SPH-D700 using XDA App
counterfeit187 said:
Good first attempt. There's a problem with your patch though. It messes up the homescreen menu and shutdown popup. if you are on homescreen and press menu, there is usually a tab that says "More" and has the unlock/lock desktop option, the patch changes this to "text from clipboard" also when you hold the power button and select shut down, the popup says reboot instead of power off. I think the problem is just a matter of line spacing being off in the Framework.jar or something, but this is an uneducated guess. Either way just wanted you to be aware. I think a better option would be to have it edit that one line of text in the framework.jar rather than replacing the .jar file completely. Good luck, happy coding.
Click to expand...
Click to collapse
styles420 said:
Editing a single line in a jar file isn't currently possible via CWM flash - this is the same reason themes and mods must often be combined, because they are modifications to the same file, and we can only replace files, not merge them
Click to expand...
Click to collapse
Styles420 is correct, that's why the fix (framework.jar or flashable.zip) replaces the "stock" CM7 framework.jar file. I assure you the only thing I changed was the digit after "0x", as in "0x1", then I recompiled/rebuilt everything. As far as I know, that shouldn't have far-reaching side-effects such as you're describing, but I'll look into it. Did you flash the file (any of the three) on the latest CM7 (10/22) , or another version of CM7, or another ROM entirely (if so, which)?
AmericanJedi001
noobnl said:
This can be fixed in the cyanogenmod framework source code
Click to expand...
Click to collapse
Sweet! BTW, where would I find the source for framework.jar? I know where the repo is, but I got lost searching thru all the different sections. Any specific directions?
bender beerman said:
sensorcalibutil_yamaha was pulled from gb...
Click to expand...
Click to collapse
Just as I suspected. I wonder if the fix chris41g found will be all we need for GB rotation / orientation-change lag? I hope so!
AmericanJedi001
Wow, out of 500+ views there have only been five other people post on here? Come on people, give me some kind of feedback! Does it work, are there issues, etc.?
I Installed on my phone and it got stuck at the samsung screen during boot up. Re flashed ROM and it was all better
couldn't get this to boot when on CM7. Froze at Sammy screen for me. tried this on MIUI Beta 3 just for giggles but no sucess there either. Too bad. Rotation lag is my mortal enemy. Lol.
Sent from my MIUI-ified Epic using XDA App
Aloth600 said:
I Installed on my phone and it got stuck at the samsung screen during boot up. Re flashed ROM and it was all better
Click to expand...
Click to collapse
After you reflashed the ROM (CM7?) did you try the fix again, or did you just not have rotation lag after the reflash?
sniperwitagun said:
couldn't get this to boot when on CM7. Froze at Sammy screen for me. tried this on MIUI Beta 3 just for giggles but no sucess there either. Too bad. Rotation lag is my mortal enemy. Lol.
Sent from my MIUI-ified Epic using XDA App
Click to expand...
Click to collapse
Were you on CM7 10/22 or an earlier release? I'm not surprised it didn't work for MIUI: the files I posted are the framework.jar and a flashable framework.jar from CM7, with only one digit difference from my stock framework.jar with CM7.
In other words, I will really be surprised if the files in the OP work for any ROMs besides CM7, and they may not work for anything besides CM7 10/22.
If you guys are using CM7 10/22, then you may want to follow the directions and pull your own framework.jar (rather than using the one I posted) and do the edit on your own file, then copy it back over. Let me know if you need any clarification on any of the steps.
I'm hoping that future builds of EpicCM will have this fix coded directly into the framework.jar--noobnl posted that it would be possible, so I'm hoping that it is on the to-do list.
were the ppl with the issues were running a modified framework.jar to facilitate an ext4 kernel?
AmericanJedi001 said:
After you reflashed the ROM (CM7?) did you try the fix again, or did you just not have rotation lag after the reflash?
I just re-flashed and didn't attempt again but, rotation lag is still there.
Click to expand...
Click to collapse
Aloth600 said:
I just re-flashed and didn't attempt again but, rotation lag is still there.
Click to expand...
Click to collapse
If you used the CWM flashable zip, try just replacing your framework.jar with the one I provided. Be sure to save your original (either rename or move to another location), copy the provided framework.jar over, then reboot. If *that* doesn't fix it, then you may need to manually do the hacking yourself, though I hope not--that's why I created this thread with the available files, to save people time!
bender beerman said:
were the ppl with the issues were running a modified framework.jar to facilitate an ext4 kernel?
Click to expand...
Click to collapse
This is a good point--if you're already running a framework.jar that's modified from the original provided with your ROM of choice (to use an EXT4 kernel, for example*), then you'll need to hack that framework.jar file. The framework.jar that's available here will probably only work with the RFS version of CM7, not any modified versions, nor other ROMs. Of course you folks are welcome to try it, but YMMS (Your Mileage May Suck)!
* I'm not sure that an EXT4 kernel will require a modified framework.jar, but you get the point.
I was on cm7 10/22. It still didn't work.
Sent from my SPH-D700 using XDA App
sniperwitagun said:
I was on cm7 10/22. It still didn't work.
Click to expand...
Click to collapse
Would you feel comfortable editing your own framework.jar file? If you're familiar with Smali/Baksmali, you should be able to follow the directions and hack up your own framework.jar to fix the rotation lag. If not, send it to me and I'll mess with it the next chance I get (no guarantees, it might be after Thanksgiving before you get it back!).
I feel ya, it's one of my pet peeves as well, thus the fix!
AmericanJedi001 said:
If you used the CWM flashable zip, try just replacing your framework.jar with the one I provided. Be sure to save your original (either rename or move to another location), copy the provided framework.jar over, then reboot. If *that* doesn't fix it, then you may need to manually do the hacking yourself, though I hope not--that's why I created this thread with the available files, to save people time!
Tried it and it locked up at the sammie screen.... flashing back now.
Click to expand...
Click to collapse
All versions of the Android Market (Play Store) above version 3.0 will self-update automatically (even if you freeze/rename/delete the Market Updater application). The following version of the Android Market has been patched to ignore the self-update check.
Note: Android Market (Google Play Store) v3.4.7 is the last available version that allows Titanium Backup to control the Market links in the application.
Note: Using the command "pm disable com.android.vending.updater" does NOT stop the Android Market 3.0+ from self-updating. Other methods of preventing the market from self-updating, such as creating a read-only file that blocks the installation procedure, are also not recommended because the market will still download market updates and use up precious internal memory and extra cpu cycles.
Code:
diff -ru Vending.3.4.7/smali/com/google/android/finsky/utils/SelfUpdateScheduler.smali Vending.3.4.7-noupdate/smali/com/google/android/finsky/utils/SelfUpdateScheduler.smali
--- Vending.3.4.7/smali/com/google/android/finsky/utils/SelfUpdateScheduler.smali 2012-04-04 02:21:11.729877751 +0200
+++ Vending.3.4.7-noupdate/smali/com/google/android/finsky/utils/SelfUpdateScheduler.smali 2012-04-04 02:33:51.870385096 +0200
@@ -29,7 +29,7 @@
invoke-direct {p0}, Ljava/lang/Object;-><init>()V
.line 42
- const/4 v0, 0x0
+ const/4 v0, 0x1
iput-boolean v0, p0, Lcom/google/android/finsky/utils/SelfUpdateScheduler;->mUpdateInProgress:Z
Logcat of Android Market with "noupdate" patch applied:
Code:
D/Finsky ( 4890): [1] SelfUpdateScheduler.checkForSelfUpdate: Skipping self-update check as there is an update already queued.
Note: Also provided below is an additional variation of the Android Market that includes an additional "no restrictions" patch applied. The additional patch removes restrictions on certain applications in the market placed by specific countries. If the country you live in has blocked the application you are looking for, this patch will allow you to see it in the market. There are still server side restrictions in place when you download an application that is blocked within your country and the use of a proxy or VPN might also be necessary. The "no restrictions" patch also removes the device application compatibility check, so every application should be visible in the Android Market (even if they "say" it is not compatible with your device). Credits to L.D.B. for the "no restrictions" patch.
Code:
diff -ru Vending.3.4.7/smali/com/google/android/finsky/api/model/Document.smali Vending.3.4.7.mod/smali/com/google/android/finsky/api/model/Document.smali
--- Vending.3.4.7/smali/com/google/android/finsky/api/model/Document.smali 2012-04-05 21:49:58.647890272 +0200
+++ Vending.3.4.7.mod/smali/com/google/android/finsky/api/model/Document.smali 2012-04-05 21:49:20.751889471 +0200
@@ -3236,6 +3236,8 @@
.line 674
:cond_0
:goto_0
+ const/4 v2, 0x1
+
return v2
.line 662
Note: A third patch for the Android Market is the "DPI 160" patch. If you change the default DPI settings on your device, the Android Market might not detect the required DPI settings and specific applications will then not be visible in the Android Market. The "DPI 160" patch forces the Android Market to think you are using a DPI of 160, which makes specific applications in the Android Market visible.
Code:
diff -ru Vending.3.4.7.orig/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali Vending.3.4.7/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali
--- Vending.3.4.7.orig/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali 2012-04-10 23:06:45.156379816 +0200
+++ Vending.3.4.7/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali 2012-04-10 23:06:55.795879255 +0200
@@ -257,7 +257,7 @@
move-result-object v15
- iget v0, v12, Landroid/util/DisplayMetrics;->densityDpi:I
+ const/16 v0, 0xa0
move/from16 v17, v0
Note: A "DPI 240" patch is also posted below. Some high resolution devices (ie; HTC Desire and Samsung Galaxy SII) require a 240 DPI in order for certain applications to be visible in the Android Market. The "DPI 240" patch forces the Android Market to think the device is using a DPI of 240.
Code:
diff -ru Vending.3.4.7.orig/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali Vending.3.4.7/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali
--- Vending.3.4.7.orig/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali 2012-04-10 23:06:45.156379816 +0200
+++ Vending.3.4.7/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali 2012-04-10 23:06:55.795879255 +0200
@@ -257,7 +257,7 @@
move-result-object v15
- iget v0, v12, Landroid/util/DisplayMetrics;->densityDpi:I
+ const/16 v0, 0xf0
move/from16 v17, v0
Note: Similar to the previous DPI patches, a "DPI 320" patch is also posted below. Some of the higher WXGA resolution devices (ie; Galaxy Nexus) require a 320 DPI in order for certain applications to be visible in the Android Market. The "DPI 320" patch forces the Android Market to think the device is using a DPI of 320.
Code:
diff -ru Vending.3.4.7.orig/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali Vending.3.4.7/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali
--- Vending.3.4.7.orig/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali 2012-04-10 23:06:45.156379816 +0200
+++ Vending.3.4.7/smali/com/google/android/finsky/utils/DeviceConfigurationHelper.smali 2012-04-10 23:06:55.795879255 +0200
@@ -257,7 +257,7 @@
move-result-object v15
- iget v0, v12, Landroid/util/DisplayMetrics;->densityDpi:I
+ const/16 v0, 0x140
move/from16 v17, v0
If your device is using a custom DPI setting, then you will need a version of the Android Market that includes one of the three "DPI Hacks" mentioned above (dpi160, dpi240, or dpi320). Without the "DPI Hack" applied, updates might not be visible in the Market.
The default DPI value for your device can be determined by looking it up in it's device specifications. When you change the default DPI setting on your device, it may cause compatibility problems for the Android Market. Therefore, we want the Android Market to think we are still using the same default value that is found in the specs.
For example, the Samsung Galaxy SII has a default DPI of 240 in it's device specifications, so we want to make the Android Market think we are still using that setting (if the default value has been modified).
For most devices, the standard default DPI values are 160, 240, and 320.
All modified versions of the Android Market that are signed by another key are unable to make purchases from within the Android Market application itself because the signing key does not match Google's signing key. Because the new signing key of the modified Android Market no longer matches with Google's signing key, the modified version of the Android Market is unable to connect with GoogleServicesFramework. There are also modified versions of the Android Market available (in post #132 of this thread) that are made using the original Google signature which makes it possible to purchase applications again within the modified Android Market.
http://forum.xda-developers.com/showpost.php?p=26102810&postcount=132
All applications can still be purchased via the web browser.
How to install:
Rename file to "Vending.apk" and copy to /system/app/Vending.apk. Make sure to uninstall any updates of previous versions first. Root Required. If you are running ICS 4.0.4, "Vending.apk" might be substituted for "Phonesky.apk".
NOTE: If you are testing a "DPI Hacked" version of the Android Market and you are still experiencing incompatibilities with certain applications or the changes are not "sticking", see post #92 in this thread for further solutions. The following link explains what additional patches may be needed: http://forum.xda-developers.com/showpost.php?p=25720539&postcount=92
Additionally, the following links contain modified versions of GSF uploaded to this thread:
http://forum.xda-developers.com/showpost.php?p=29401924&postcount=334
http://forum.xda-developers.com/showpost.php?p=30074336&postcount=390
http://forum.xda-developers.com/showthread.php?t=1631070
http://forum.xda-developers.com/showpost.php?p=26423837&postcount=161
** Google Play 3.4.4 with "market purchase fix and dpi120" has been added to the following link: http://forum.xda-developers.com/showpost.php?p=31027248&postcount=460
** Google Play 3.4.7/3.5.19 with "market purchase fix" has been added to the following link:: http://forum.xda-developers.com/showpost.php?p=26102810&postcount=132
** Google Play 3.7.11 has been added to the following link: http://forum.xda-developers.com/showpost.php?p=28029688&postcount=222
** Google Play 3.7.13 has been added to the following link: http://forum.xda-developers.com/showpost.php?p=28207664&postcount=243
** Google Play 3.7.15 has been added to the following link: http://forum.xda-developers.com/showpost.php?p=29466370&postcount=344
** Google Play 3.8.15 has been added to the following link: http://forum.xda-developers.com/showpost.php?p=30317127&postcount=399
** Google Play 3.8.16 has been added to the following link: http://forum.xda-developers.com/showpost.php?p=30387825&postcount=409
** Google Play 3.8.17 has been added to the following link: http://forum.xda-developers.com/showpost.php?p=30563737&postcount=436
** Google Play 3.9.16 has been added to the following link: http://forum.xda-developers.com/showpost.php?p=32768509&postcount=505
** Google Play 3.9.17 has been added to the following link: http://forum.xda-developers.com/showpost.php?p=33747629&postcount=544
** Google Play 3.10.9 has been added to the following link: http://forum.xda-developers.com/showpost.php?p=34774989&postcount=566
** Google Play 3.10.10 has been added to the following link: http://forum.xda-developers.com/showpost.php?p=35741543&postcount=599
** Google Play 3.10.14 has been added to the following link: http://forum.xda-developers.com/showpost.php?p=38633857&postcount=660
** Google Play 4.0.25 has been added to the following link: http://forum.xda-developers.com/showpost.php?p=40237365&postcount=694
** Google Play 4.0.26 has been added to the following link: http://forum.xda-developers.com/showpost.php?p=40822664&postcount=705
** Google Play 4.0.27 has been added to the following link: http://forum.xda-developers.com/showpost.php?p=40823085&postcount=706
** Google Play 4.3.10 has been added to the following link: http://forum.xda-developers.com/showpost.php?p=44365806&postcount=769
Not working for me. Getting a parsing error
Parsing error? Where? Did you follow the installation steps?
quorn23 said:
Parsing error? Where? Did you follow the installation steps?
Click to expand...
Click to collapse
Yes, but I used root explorer. Should I use adb
I downloaded using tapatalk numerous times. The apk is only 554 bytes. Obviously that's the problem. I will jump on a PC and see...
fitz420 said:
Yes, but I used root explorer. Should I use adb
Click to expand...
Click to collapse
Well yes and no, to answer your question you can use root explorer. just make sure you set it to read/write and set the permissions right.
fitz420 said:
I downloaded using tapatalk numerous times. The apk is only 554 bytes. Obviously that's the problem. I will jump on a PC and see...
Click to expand...
Click to collapse
Still 554 bytes when downloaded from browser
I think my browser did not upload the file properly the first time. I have re-uploaded it and verified it this time. Thanks for letting me know.
What browser are you using? Chrome on the phone has problems with downloading apks
Sent from my HTC PH39100 using xda premium
I added an additional version of the market that includes a patch to remove restrictions placed on applications by the market.
1) Removes device compatibility check so all applications are visible to your device
2) Removes restrictions places on certain applications by specific countries. If the country you live in blocks a specific application in your market, then it should now be visible.
Credits to L.D.B. for the "no restrictions" patch.
Tsjoklat said:
Note: Also provided below is an additional version of the Android Market that includes an additional "no restrictions" patch applied. The additional patch removes restrictions on certain applications in the market placed by specific countries. If the country you live in has blocked the application you are looking for, this patch will allow you to see it in the market. The "no restrictions" patch also removes the device application compatibility check, so every application should be available to download (even if they "say" it is not compatible with your device). Credits to L.D.B. for the "no restrictions" patch.
Click to expand...
Click to collapse
This does not work. I already tested this exact patch, and while apps are visible in Market app, they cannot be downloaded, as additional checks are being done server side.
Eddie1506 said:
This does not work. I already tested this exact patch, and while apps are visible in Market app, they cannot be downloaded, as additional checks are being done server side.
Click to expand...
Click to collapse
I wonder if this could work in conjunction with a tor proxy.
Tsjoklat said:
I wonder if this could work in conjunction with a tor proxy.
Click to expand...
Click to collapse
Suppose so. But for me, the solution is running Android Market 2.3.6 on ICS as it does not do IP checks, only SIM operator check. I hacked it to report to servers that my SIM card is from USA, so no need for Market Enabler, it just works.
I have a device that has not yet been rooted (without hardware modifications).....is there a way to install the google play store (it comes with old market) and still use the feature where it ignores device incompatiblity? I find it tells me alot of my apps are incompatible even if I know they work.
Hey google...here's a clue...if the app is already INSTALLED on the device odds are it works.
famewolf said:
I have a device that has not yet been rooted (without hardware modifications).....is there a way to install the google play store (it comes with old market) and still use the feature where it ignores device incompatiblity? I find it tells me alot of my apps are incompatible even if I know they work.
Hey google...here's a clue...if the app is already INSTALLED on the device odds are it works.
Click to expand...
Click to collapse
Mines rooted and still get same incompat issue even when previous ver installed!
Anyway is there to be an updated market version?
lohtse said:
Mines rooted and still get same incompat issue even when previous ver installed!
Anyway is there to be an updated market version?
Click to expand...
Click to collapse
Did you uninstall updates to the app like the directions say? Did you remount the system partition to made it r/w instead of read only? It worked fine on all 4 of my rooted devices and I installed apps that previously failed except through sideloading.
lohtse said:
Anyway is there to be an updated market version?
Click to expand...
Click to collapse
As of today, the latest version of the Android Market (Play Store) is v3.5.16. But, I had chosen v3.4.7 because I wanted a version that is fully functional with Titanium Backup. If you want to add the "no restriction" patch to the latest version of the Android Market (v3.5.16), then this is what the changes will look like (slightly different than with v3.4.7):
Code:
diff -ru Vending.3.5.16/smali/com/google/android/finsky/api/model/Document.smali Vending.3.5.16.mod/smali/com/google/android/finsky/api/model/Document.smali
--- Vending.3.5.16/smali/com/google/android/finsky/api/model/Document.smali 2012-04-05 21:35:12.551888812 +0200
+++ Vending.3.5.16.mod/smali/com/google/android/finsky/api/model/Document.smali 2012-04-05 21:54:49.299397643 +0200
@@ -3216,6 +3216,10 @@
.parameter "library"
.prologue
+ const/4 v0, 0x1
+
+ return v0
+
const/4 v9, 0x2
const/4 v5, 0x1
I have added Vending.3.5.16.noupdate.norestrictions-signed to the first page. A modified version of the Android market with this "no restrictions" patch can already be found on various other webpages, but the version found in this thread has also the self-update feature disabled. The modified versions can not self-update because the signing keys no longer match the original, so we might as well prevent it from trying and downloading the updates that will not apply anyway.
Tsjoklat said:
As of today, the latest version of the Android Market (Play Store) is v3.5.16. But, I had chosen v3.4.7 because I wanted a version that is fully functional with Titanium Backup. If you want to add the "no restriction" patch to the latest version of the Android Market (v3.5.16), then this is what the changes will look like (slightly different than with v3.4.7):
Code:
diff -ru Vending.3.5.16/smali/com/google/android/finsky/api/model/Document.smali Vending.3.5.16.mod/smali/com/google/android/finsky/api/model/Document.smali
--- Vending.3.5.16/smali/com/google/android/finsky/api/model/Document.smali 2012-04-05 21:35:12.551888812 +0200
+++ Vending.3.5.16.mod/smali/com/google/android/finsky/api/model/Document.smali 2012-04-05 21:54:49.299397643 +0200
@@ -3216,6 +3216,10 @@
.parameter "library"
.prologue
+ const/4 v0, 0x1
+
+ return v0
+
const/4 v9, 0x2
const/4 v5, 0x1
I have added Vending.3.5.16.noupdate.norestrictions-signed to the first page. A modified version of the Android market with this "no restrictions" patch can already be found on various other webpages, but the version found in this thread has also the self-update feature disabled. The modified versions can not self-update because the signing keys no longer match the original, so we might as well prevent it from trying and downloading the updates that will not apply anyway.
Click to expand...
Click to collapse
So should I assume my attempt to install a version of google play store where practically everything is NOT listed as incompatible on my NON rooted device is hopeless by your lack of response? The logitech revue runs on honeycomb 3.1 and originally comes with market...it was later upgraded to google play. Your versions of course fail to install. Is it possible to apply your fixes to the version I am attaching to this post while keeping signatures so it will work as an install? This is the apk of the version that it was upgraded to. Thank you for your time.
famewolf said:
So should I assume my attempt to install a version of google play store where practically everything is NOT listed as incompatible on my NON rooted device is hopeless by your lack of response?
Click to expand...
Click to collapse
I'm afraid that root is going to be necessary. When I make changes to an apk, I have to resign it (but I don't have the original keys). Since the modified apk is now signed with a different signature than the original, it can not be installed on top of the original. Therefore, you will need to have root access to replace the original apk with the modified version (since the signature keys no longer match).
The file you uploaded is only 554 bytes in size. That seems to not be correct. There seems to be problems uploading files to XDA lately. Also, make sure the files are not odexed (the apk must contain a classes.dex in order to be modified).
Tsjoklat said:
I'm afraid that root is going to be necessary. When I make changes to an apk, I have to resign it (but I don't have the original keys). Since the modified apk is now signed with a different signature than the original, it can not be installed on top of the original. Therefore, you will need to have root access to replace the original apk with the modified version (since the signature keys no longer match).
The file you uploaded is only 554 bytes in size. That seems to not be correct. There seems to be problems uploading files to XDA lately. Also, make sure the files are not odexed (the apk must contain a classes.dex in order to be modified).
Click to expand...
Click to collapse
the logitech revue has not yet been rooted without some rather drastic hardware modifications so I guess for now I'm stuck. Thanks for the reply.
Can someone upload the kindle fire hulu apk?
I have the hacked version from earlier this year, but the interface sucks.
I've edited build.prop to identify itself as a Galaxy Nexus. This still didn't work. I can download the app from the place store, but of the amazon store.
poormanq45 said:
Can someone upload the kindle fire hulu apk?
I have the hacked version from earlier this year, but the interface sucks.
I've edited build.prop to identify itself as a Galaxy Nexus. This still didn't work. I can download the app from the place store, but of the amazon store.
Click to expand...
Click to collapse
I manage to make the latest hulu plus (2.6.201000) by using the android.os.Build.SERIAL from my original KF rom, I have no idea how to change it in the device so I hacked the apk. All you need to do is unpack the hulu plus apk using apktool, make the following changes (I hope you have no trouble reading the pseudo diff format):
diff -ur hp/smali/com/hulu/plus/Application.smali hp_hack/smali/com/hulu/plus/Application.smali
--- hp/smali/com/hulu/plus/Application.smali 2013-01-06 13:34:28.756020730 -0500
+++ hp_hack/smali/com/hulu/plus/Application.smali 2013-01-05 21:49:04.281291030 -0500
@@ -510,6 +510,8 @@
move-result-object v0
+ const-string v0, "YOUR SERIAL HERER"
+
check-cast v0, Ljava/lang/String;
if-eqz v0, :cond_c
This overwrite the real SERIAL from your device, I am using the CM10 rom by twa_priv, and the value is 'unknown'. Then repacking and sign your new apk and you are done.
I want to mention I have login to HULU in the original amazon rom before I use its serial number for the hack and I can see it in my hulu account, not sure if it is necessary, I did not tried any fake serial either. I cannot upload the apk since it is hardcoded with my serial number.
Hi! I wanted to doze GMS on my pixel 2 running Pie, but I didn't find any functional solution, so I made it :victory:
Use it, if you want, ONLY on Pixel 2 running Pie. I made it and tested it for PPR2.180905.005 version. I had to modify GoogleSettings.apk so you could brick your device if you will use it on other version or other phone. I take no responsibility if you will brick your device or something else
How to apply:
for sure make backup of your phone
download gms_pie_doze.zip
flash via MagiskManager
reboot device
set optimization for GMS via settings
and enjoy
thats all, save, recompile and use it
UPDATE:
add HOW TO
HOW TO:
copy your SettingsGoogle.apk from system/priv-app/SettingsGoogle folder to your PC
copy your google.xml from system\etc\sysconfig\ to PC
decompile SettingsGoogle.apk with apktool (or use smali/baksmali on classes.dex file) -> there are tons of tutorials on XDA and google, so search for it or look here, small tutorial by me
find PowerWhitelistBackend.smali in com\android\settingslib\fuelgauge\ folder
in this file find .method public isWhitelisted(Ljava/lang/StringZ, you could find it twice, we are looking for the first one, it should start on line 193 (but it is not necessary)
at the end of this method you could find this code:
Code:
if-eqz v4, [COLOR="Blue"]:cond_3a[/COLOR]
.line 91
return v1
[COLOR="Red"].line 94
:cond_3a
iget-object v4, p0, Lcom/android/settingslib/fuelgauge/PowerWhitelistBackend;->mAppContext:Landroid/content/Context;
const-class v5, Landroid/app/admin/DevicePolicyManager;
invoke-virtual {v4, v5}, Landroid/content/Context;->getSystemService(Ljava/lang/Class;)Ljava/lang/Object;
move-result-object v4
check-cast v4, Landroid/app/admin/DevicePolicyManager;
.line 96
.local v4, "devicePolicyManager":Landroid/app/admin/DevicePolicyManager;
invoke-virtual {v4, p1}, Landroid/app/admin/DevicePolicyManager;->packageHasActiveAdmins(Ljava/lang/String;)Z
move-result v5
if-eqz v5, :cond_4b
.line 97
return v1[/COLOR]
.line 100
[COLOR="Lime"]:cond_4b[/COLOR]
return v2
.end method
what we have to do is: delete all red code
and now we need to change blue code to match with green code, so from
Code:
if-eqz v4,[COLOR="Blue"] :cond_3a[/COLOR]
we will get
Code:
if-eqz v4,[COLOR="Lime"] :cond_4b[/COLOR]
now the code will look like this:
Code:
if-eqz v4, :cond_4b
.line 91
return v1
.line 100
:cond_4b
return v2
.end method
save it and recompile
now open google.xml file
find and delete:
Code:
<allow-in-power-save package="com.google.android.gms" />
now put these files back to your phone (via Magick, TWRP .... it is on you)
well, you are done, enjoy it :good:
Works great!! Thank you for taking the time to develop this module for us Pie users! GMS was eating my Pixel 2 until I installed this.
Did anyone try with ppr2.181005.003 (Oct patch)?
moviti said:
Did anyone try with ppr2.181005.003 (Oct patch)?
Click to expand...
Click to collapse
Installed and showing as optimized
kamzz said:
Installed and showing as optimized
Click to expand...
Click to collapse
Thanks! It looks working fine!
Added version for ppr2.181005.003
somin.n said:
Added version for ppr2.181005.003
Click to expand...
Click to collapse
The original version seems to be working on ppr2.181005.003, should I stick with it or use the newer one?
kamzz said:
The original version seems to be working on ppr2.181005.003, should I stick with it or use the newer one?
Click to expand...
Click to collapse
If it is working, you could stay, but this mod edits system settings apk and I don't know, if there are some major changes from google in newer version, so it is better to use the newest one allways.
Any chance you could get this to work on the 2 XL?
Maverick Jester said:
Any chance you could get this to work on the 2 XL?
Click to expand...
Click to collapse
Hi! I could try it, just send me your "SettingsGoogle.apk" from private-app folder and i will look on it.
somin.n said:
Hi! I could try it, just send me your "SettingsGoogle.apk" from private-app folder and i will look on it.
Click to expand...
Click to collapse
Awesome, appreciate it. I've attached it to the reply, but had to archive it because of XDA's file size limitations. For reference, I am also on build PPR2.180905.005.
Maverick Jester said:
Awesome, appreciate it. I've attached it to the reply, but had to archive it because of XDA's file size limitations. For reference, I am also on build PPR2.180905.005.
Click to expand...
Click to collapse
Here is it, for sure make necessary backup, I didn't test it, but it should be ok It is Magisk module, so don't flash via twrp.
somin.n said:
Here is it, for sure make necessary backup, I didn't test it, but it should be ok It is Magisk module, so don't flash via twrp.
Click to expand...
Click to collapse
This has worked perfectly, thank you!
To the first post added version for November update (181105.017).
somin.n said:
To the first post added version for November update (181105.017).
Click to expand...
Click to collapse
I'm trying to flash through Magisk and Magisk keeps force closing, I'm on the latest November update so i grabbed your latest modded settings app from the OP.
FilthyFord said:
I'm trying to flash through Magisk and Magisk keeps force closing, I'm on the latest November update so i grabbed your latest modded settings app from the OP.
Click to expand...
Click to collapse
Hi, I re-download November version a try it again and everything is ok on my side. What is you magisk version? I am on 17.1 and app version is 6.0.1....
somin.n said:
Hi, I re-download November version a try it again and everything is ok on my side. What is you magisk version? I am on 17.1 and app version is 6.0.1....
Click to expand...
Click to collapse
Same here. 17.1 and 6.0.1. I'm new to Magisk so I'm probably screwing something up in my end. Lol I'll redownload and try again.
My Magisk still just close when i try to install it. Can you tell me if I'm doing it right, i open Magisk go to modules, clock on the + go to where i downloaded the zip file and just click on it correct? It's at that point that Magisk closes
FilthyFord said:
My Magisk still just close when i try to install it. Can you tell me if I'm doing it right, i open Magisk go to modules, clock on the + go to where i downloaded the zip file and just click on it correct? It's at that point that Magisk closes
Click to expand...
Click to collapse
Yeah, it looks right... Just maybe, try to look in to settings and verify that Magisk has "storage permission" enabled...
somin.n said:
Yeah, it looks right... Just maybe, try to look in to settings and verify that Magisk has "storage permission" enabled...
Click to expand...
Click to collapse
Yes it has storage permission. I'll keep messing with it and see what i can figure out.
Edit: i figured it out. I use root explorer as my file manager and for what ever reason it is what was making Magisk force close. I reinstalled the factory file manager and everything installed properly. Thanks @somin.n for the help.
Now GMS Doze can be activated in any phone running on pie but you've to disable device admins first.