It will be literally the same. I didn't go into fine-tuning this and I don't intend to as of right now. If you don't feel comfortable with it, edit the GSI's Mixer Paths or the Mixer Paths in the /vendor partition until it suits your needs.
Ok thanks man I really appreciate all you have done. Do you Know if there is a guide on how to do this?
Maybe something like this would help. Try in both /system and /vendor to be sure (and if files doesn't exist, then jump to the other location).
Of course, needless to say you want to decrease the volume instead of making it go higher, so try decreasing the numbers that guide mentions.
Phh should be getting the Razer phone I shipped him by the end of the week, expect fine tuning and more fixes then, if you can wait a week.
Sent from my taimen using XDA Labs
Sent from my taimen using XDA Labs
A few things not working correct...
The reboot bug that gets you stuck on bootloader
Volume buttons adjusting media instead of ring
Network stays on wcdma
Works really well for something this new.
The reboot bug that gets you stuck on bootloader
Volume buttons adjusting media instead of ring
Network stays on wcdma
Works really well for something this new.
1. Razer's issue.
2. Volume buttons work as they should? I'm adjusting my ring button when I press them, you must have a background service that is using the multimedia one, like Snapchat.
3. Okay, same.
Ir you are using lineageOS or RR, there's an option to choose which volume is adjusted when volume buttons are pressed. I think is set to media by default, which I prefer
El4nimal my good man are correct, I am on rr and just found the setting of which you were referring.
May I make another query, has anyone asked if you had them on speaker phone?
May I make another query, has anyone asked if you had them on speaker phone?
No, but I wouldn't be surprised. It sounds loud when in call, even if I have the volume set to minimum. I even had the impression that adjusting the volume does not actually adjust it.
I can't get magisk to pass safety net check.. I get a double false. Running Magisk v16.3. Any ideas how to fix it?
Flash magisk 16.3 again, mounting your system partition as read-writtable in TWRP, and then follow this https://forum.xda-developers.com/showpost.php?p=76067245&postcount=11
What else other than magisk are you running? Any modules? Root is recognized properly?
Can someone open this issue on GitHub Treble Experimentations?
Phh received the Razer phone from me the other day and can now fix stuff directly.
Guys magisk still wont work with me it keeps giving me "magisk is not installed" despite installing twrp on slot b and switching to a then installing the latest beta (16.3) any help or can someone point out what mistake i have done?
Can you just follow the steps in the first post and the ones described a few posts above you? Magisk is extremely picky and you need to perform the steps as described for it to work properly...
LTE issue solved!
Thanks to @phhusson for noticing why the Hardware Overlay Picker was faulty (and @Exelios for giving him the phone), the LTE overlay now gets enabled properly and it's working as intended in the Razer Phone.
With future compilations of GSIs from him, this issue will be solved.
- - - - - - - - - - - -
However, if you do require to solve this in your current set up, just like I did, get the /system_root/system/priv-app/HardwareOverlayPicker apk, decompile it, open the AndroidManifest.xml and add this right after the package=".........." part:
Now recompile the apk and download a copy of SignAPK and sign the apk with the platform keys (platform.*) from Android AOSP.
You can do so by using the following command:
After that, push it to your system_root/system/priv-app/HardwareOverlayPicker folder, delete the old apk if needed and reboot. You should be able to choose LTE now as network mode.
Or... If you're too lazy, use this version I modded (extracted from a GSI from the 26-03-2018, so be careful since it's a bit old).
BE WARNED, NONE OF THESE STEPS ABOVE IS NEEDED IN UPCOMING VERSIONS SINCE IT'S ALREADY FIXED!!!
- - - - - - - - - - - -
Enjoy your bug-free GSIs! @MishaalRahman
Thanks to @phhusson for noticing why the Hardware Overlay Picker was faulty (and @Exelios for giving him the phone), the LTE overlay now gets enabled properly and it's working as intended in the Razer Phone.
With future compilations of GSIs from him, this issue will be solved.
- - - - - - - - - - - -
However, if you do require to solve this in your current set up, just like I did, get the /system_root/system/priv-app/HardwareOverlayPicker apk, decompile it, open the AndroidManifest.xml and add this right after the package=".........." part:
Code:
android:sharedUserId="android.uid.system"You can do so by using the following command:
Code:
java -jar /path/to/signapk.jar /path/to/platform.x509.pem /path/to/platform.pk8 NameOfTheApk.apk NameOfTheApk_signed.apkOr... If you're too lazy, use this version I modded (extracted from a GSI from the 26-03-2018, so be careful since it's a bit old).
BE WARNED, NONE OF THESE STEPS ABOVE IS NEEDED IN UPCOMING VERSIONS SINCE IT'S ALREADY FIXED!!!
- - - - - - - - - - - -
Enjoy your bug-free GSIs! @MishaalRahman
Last edited:
So if I've been keeping up correctly the only issues left is the reboot bug and the 120Hz refresh rate contently on?
I'm running Xposed module and magisk hide props config currently and am still getting the double false message. Im not sure how to mount twrp in read write mode so I can flash magisk again.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone