Noticed none of the current builds have the CRT animation enabled, thought I'd share how to turn it on. Please note that it is at times a bit buggy. For me it works about 8 out of 10 times.
What it is:
Note: 1 - This will work on any device and on any version of Android back to GB. (Obviously the Nexus specific tools wont work on anything other than the Nexus)
Note 2 - You will have to redo this every time you update your rom.
Here's the quick rundown -
First, you'll have to pull the framework-res.apk from your tablet.
This can be done via adb, but the easiest way would be to either use WugFresh's Nexus Root Toolkit or mskips Google Nexus 7 TOOLKIT.
When asked what file to pull, type in "/system/framework/framework-res.apk" (without quotes)
Once you have that pulled, install this tool: http://forum.xda-developers.com/showthread.php?t=1432152
Follow the directions on how to use it in the thread.
Once you have decompiled the apk, you'll want to edit the "files-to-edit\framework-res.apk\res\values\bools.xml" file.
The value you want to change in the bools value is the "<bool name="config_animateScreenLights">true</bool>" change "true" to "false". I reccommend downloading Notepad++ to edit.
Make sure you save it. Once saved, recompile the apk using the tool you install, then create an update zip (I renamed mine to crtanimation.zip for ease).
Reboot into recovery, flash the zip, clear cache, reboot.
Tada!
Krunk_Kracker said:
Noticed none of the current builds have the CRT animation enabled, thought I'd share how to turn it on. Please note that it is at times a bit buggy. For me it works about 8 out of 10 times.
Here's the quick rundown -
First, you'll have to pull the framework-res.apk from your tablet.
This can be done via adb, but the easiest way would be to either use WugFresh's Nexus Root Toolkit or mskips Google Nexus 7 TOOLKIT.
When asked what file to pull, type in "/system/framework/framework-res.apk" (without quotes)
Once you have that pulled, install this tool: http://forum.xda-dev...d.php?t=1432152
Follow the directions on how to use it in the thread.
Once you have decompiled the apk, you'll want to edit the "files-to-edit\framework-res.apk\res\valuesbools.xml" file.
The value you want to change in the bools value is the "<bool name="config_animateScreenLights">true</bool>" change "true" to "false".
Make sure you save it. Once saved, recompile the apk using the tool you install, then create an update zip (I renamed mine to crtanimation.zip for ease).
Reboot into recovery, flash the zip, reboot.
Tada!
Click to expand...
Click to collapse
"Once you have that pulled, install this tool: http://forum.xda-dev...d.php?t=1432152"
This link is not working.
TahrirSquare said:
"Once you have that pulled, install this tool: http://forum.xda-dev...d.php?t=1432152"
This link is not working.
Click to expand...
Click to collapse
Apologies.
Fixed now
Why would someone want to do this?
Guardsix said:
Why would someone want to do this?
Click to expand...
Click to collapse
Why would someone want to put a custom rom on N7?
Sent from my Nexus 7 using Tapatalk 2
They most likely don't know what CRT animation is, NOT why they might want to make changes to the system.
Nothing in the OP provides a hint as to what that is or what it does. To be honest, I'm not sure I know what it is. A quick search shows that it is enabled in a lot of ROMs but not what it actually is or does.
Sent from my Nexus 7
krelvinaz said:
They most likely don't know what CRT animation is, NOT why they might want to make changes to the system.
Nothing in the OP provides a hint as to what that is or what it does. To be honest, I'm not sure I know what it is. A quick search shows that it is enabled in a lot of ROMs but not what it actually is or does.
Sent from my Nexus 7
Click to expand...
Click to collapse
OK, makes sense, I was assuming most knew what it meant.
I'll make a quick video.
Just made a video, uploading it.
krelvinaz said:
They most likely don't know what CRT animation is, NOT why they might want to make changes to the system.
Nothing in the OP provides a hint as to what that is or what it does. To be honest, I'm not sure I know what it is. A quick search shows that it is enabled in a lot of ROMs but not what it actually is or does.
Sent from my Nexus 7
Click to expand...
Click to collapse
If you don't know what it is then you obviously haven't flashed many roms and therefore should probably not even attempt this...
Thanks OP and sry for the ungrateful ones here.
updated OP with a demo vid
I guess the CRT animation is more obscure than I thought.
Okay... I get it... It enables animation effects when turning the device off, rather than just blanking the screen.
I get the same effect turning on and off with
https://play.google.com/store/apps/details?id=com.soulfulz.android.turnoffscreen
You can select from a number of effects, sounds for both when the device is turned on and off via the button. You have to hit the button for it to do it, but for the risk of modifying system files, this is easy and safe to do.
krelvinaz said:
Okay... I get it... It enables animation effects when turning the device off, rather than just blanking the screen.
I get the same effect turning on and off with
https://play.google.com/store/apps/details?id=com.soulfulz.android.turnoffscreen
You can select from a number of effects, sounds for both when the device is turned on and off via the button. You have to hit the button for it to do it, but for the risk of modifying system files, this is easy and safe to do.
Click to expand...
Click to collapse
Except your solution is wakelock city on top of having to enable it as a device administrator. Sounds like you also have to hit the shortcut or use the app itself to get the desired effect versus it being naturally accomplished when hitting the power button/screen timeout. And if it doesn't work in ICS, not sure it will work on JB.
krelvinaz said:
Okay... I get it... It enables animation effects when turning the device off, rather than just blanking the screen.
I get the same effect turning on and off with
https://play.google.com/store/apps/details?id=com.soulfulz.android.turnoffscreen
You can select from a number of effects, sounds for both when the device is turned on and off via the button. You have to hit the button for it to do it, but for the risk of modifying system files, this is easy and safe to do.
Click to expand...
Click to collapse
My way is easy and safe to do, if you follow the direction.
All your doing is turning something on. It's something that Google intended to be toggled.
Krunk_Kracker said:
My way is easy and safe to do, if you follow the direction.
Click to expand...
Click to collapse
Something users of XDA are so good at doing? Reading and following instructions.
All your doing is turning something on. It's something that Google intended to be toggled.
Click to expand...
Click to collapse
Curious, they didn't implement it in their flagship first tablet and first official device to have Jelly Bean?
BTW, I am not knocking you, just have a lot of experience dealing with users that don't read, can't follow instructions...
The info on extracting and the tool was good reading, I just know a lot of users that will botch this up and start posting BRICKED threads.
Via my HTC Rezound
krelvinaz said:
Something users of XDA are so good at doing? Reading and following instructions.
Curious, they didn't implement it in their flagship first tablet and first official device to have Jelly Bean?
BTW, I am not knocking you, just have a lot of experience dealing with users that don't read, can't follow instructions...
The info on extracting and the tool was good reading, I just know a lot of users that will botch this up and start posting BRICKED threads.
Via my HTC Rezound
Click to expand...
Click to collapse
I'm sorry if people are unable to follow direction, but honestly that's not my problem.
If they mess it up, it wont brick, and if it does, all they have to do is dirty flash their rom and it's fixed.
I asked the question "Why" because it seems a lot of trouble just to see your device (N7, in this case) turn off. I've done a great deal of modding to my ICS devices, but haven't really found much reason to mod a JB device. I know there are tons of boot animations which make your device really different when turned on, but having CRT just for turning off your device seems a waste of time.
Of course, this is only my opinion and I'm glad you figured out how to do this, but I still don't understand why!
Guardsix said:
I asked the question "Why" because it seems a lot of trouble just to see your device (N7, in this case) turn off. I've done a great deal of modding to my ICS devices, but haven't really found much reason to mod a JB device. I know there are tons of boot animations which make your device really different when turned on, but having CRT just for turning off your device seems a waste of time.
Of course, this is only my opinion and I'm glad you figured out how to do this, but I still don't understand why!
Click to expand...
Click to collapse
Why not?
To sound cliche, Android is all about options.
I present you with yet another modding option.
Sent from my Nexus 7 using Tapatalk 2
I'm not really understanding the animosity with this simple mod...
Neat! I am sure that I will get around to this eventually but I am surprised that I haven't noticed that there was no CRT animation enabled already.
Sent from my Nexus 7 using xda app-developers app
Guardsix said:
I asked the question "Why" because it seems a lot of trouble just to see your device (N7, in this case) turn off. I've done a great deal of modding to my ICS devices, but haven't really found much reason to mod a JB device. I know there are tons of boot animations which make your device really different when turned on, but having CRT just for turning off your device seems a waste of time.
Of course, this is only my opinion and I'm glad you figured out how to do this, but I still don't understand why!
Click to expand...
Click to collapse
Don't understand why you don't just switch to an iphone
Ok I tried what the OP has posted but the compiler tool is borked, no way to recompile the file after editing the file. Read over the original posting and found that the issue is still not fixed, any other way to do this??
Related
I was looking around for a thread for this phone, but found nothing. I hope people start working on it, I'd like to mod it.
Is there anything I can do to help, like dumping the rom? Do any of the current tools even work on it?
I read somewhere Kyocera was going to put out an upgrade to 2.1, bit I can't find anything besides a mention of that.
EDIT: FEB 22, 2011
NEW 2.2 THREAD
YES! It is actually out! For real!
EDIT: Jan 27, 2011
It was released (somewhere around page 76) that Android 2.2 would be released Late Feb to early March.
START NEW THREADS!
If you have questions other than modding, it would help to put it in a new thread with the prefix subject "Kyocera Zio M6000 - "
I figure if lots of threads pop up like that it would be more likely that they'd notice it and actually create it's own forum. If everything is just tagged onto this thread, then it will just get huge and unnavigable, and the mods won't notice enough activity.
Update:
hotaru was awesome enough to post a full dump of the Zio for us:
http://forum.xda-developers.com/showpost.php?p=8907621&postcount=287
If you look around this thread you'll find info about rooting the phone. Also in this thread a port Clockwork Recovery was released. There are some issues with it that were not resolvable. Such as if you boot to Clockwork and don't actually reset the phone, it will lose the Cricket settings and revert to Verizon. So it will work to recover a ROM and backup, but you need to also need to reset or restore when you go there.
Wasn't sure where to post this since there is no HW section for this phone, so I put it here in hacking general...
Could someone create a forum for it and move this post to it?
EDIT:
To root the phone people have had success with 1-click root for N1
And the MSL# is 000000
The debug ACCESS CODE is #777468
A copy of the 1.6 rom here
Will update here with any usefull info.
Also, this thing has absolutely no multi-touch, even though all the blogs says it does.
For Tethering. PdaNet (I can't post any links cause i'm a new user, just do a Google Search and click "I'm Feeling Lucky")
Works like a Charm.
Currently Using the Free Version and it works GREAT.
Even has an SMS client built in so you can reply to your messages while your tethered.
Just make sure USB Debugging is on and you'll have no problem.
I also put in a request for a user group for this phone. I emailed one of the admins directly and he told me if they get enough requests they may create it.
What I have really been looking for is either a hacked up upgrade Rom to either enclair or group for this phone.
Sent from my PC36100 using XDA App
I second that motion. The seems to be the first legit prepaid android phone, and it isn't really getting any attention, anywhere :-/
Which I find quite odd. I personally have the EVO and love it but I did buy this phone for my girlfriend and she absolutely loves it and for a prepaid phone with a price point of 230 bucks you really cant beat it. Especially for 55 a month. I would think more people would be flocking to this. I have even considered giving up my evo for it but I do like the 4g. And the Build of the Evo is much higher quality.
Root
I think getting the thing rooted is important. All of the wifi tether apps require that. I read somewhere that someone had done it.
Do you find your girlfriend's Zio crashes when trying to watch video that you are opening from a link? Mine does every time :-(
Yup, lots of freezing, soft and hard.
I can't get rid of a "cdma: reorder" error after installing GoogleVoice. Now I can only make calls through GV or I'll get the error. I really need a better ROM, they better come out with 2.1 ASAP.
I also hope the no multitouch is only a sw issue and not a hw one.
i totally agree with you guys this phone needs some tweeking
phazei said:
Yup, lots of freezing, soft and hard.
I can't get rid of a "cdma: reorder" error after installing GoogleVoice. Now I can only make calls through GV or I'll get the error. I really need a better ROM, they better come out with 2.1 ASAP.
I also hope the no multitouch is only a sw issue and not a hw one.
Click to expand...
Click to collapse
Multitouch is something that is enabled in the kernel. I'm sure that the update to 2.1 will bring multi touch.
ROOTED!
The Zio can be rooted, download the file, email it to yourself, and open it on the phone. It is easy peasy ;-)
Paste this into the search up top: 1-click root for N1
(I would have posted the link but the forums rules won't allow me because...I don't have many posts?)
Wifi tether works like a champ.
No problems with my girlfriends phone I played with it for at least 2 or 3 hours when I first got it and eveything appeared to work fine. The only thing that I really didnt like was the factory keyboard I heard swiftkey got a major upgrade and was thinking about using it as a replacement especially cause it has the voice to text feature. And I may root her phone as well to give that wifi tether a shot. But what I would really like to see is some kind of upgrade to 2.X I think that it what will really make this phone shine.
cas8180 said:
No problems with my girlfriends phone I played with it for at least 2 or 3 hours when I first got it and eveything appeared to work fine. The only thing that I really didnt like was the factory keyboard I heard swiftkey got a major upgrade and was thinking about using it as a replacement especially cause it has the voice to text feature. And I may root her phone as well to give that wifi tether a shot. But what I would really like to see is some kind of upgrade to 2.X I think that it what will really make this phone shine.
Click to expand...
Click to collapse
you should download apn backup and restore from the market and show us the apn used on that phone
awe215 said:
The Zio can be rooted, download the file, email it to yourself, and open it on the phone. It is easy peasy ;-)
Paste this into the search up top: 1-click root for N1
(I would have posted the link but the forums rules won't allow me because...I don't have many posts?)
Wifi tether works like a champ.
Click to expand...
Click to collapse
Got my Zio rooted the same way, but now how do I enable Wifi tethering?
There is an app called "Barnacle Wifi Tethering", look it up in the app store. Once it is installed it is self explanatory,
If you like it, you should donate to the developers ;-)
Thick-buttons
Ah, there is an app called "ThickButtons", it's free, and it helps!
awe215 said:
There is an app called "Barnacle Wifi Tethering", look it up in the app store. Once it is installed it is self explanatory,
If you like it, you should donate to the developers ;-)
Click to expand...
Click to collapse
Got that and it seems kinda buggy. I always get some type of error the first time I try to start tethering. Always works on the second shot though.
xTONEx said:
you should download apn backup and restore from the market and show us the apn used on that phone
Click to expand...
Click to collapse
I second this motion.
Step 1: Download APN Backup & Restore from Market
Step 2: Open APN Backup & Restore
Step 3: Backup APNs
Step 4: Plug phone into computer with USB cable.
Step 5: Drag notification bar from the top, tap the USB connection notification, and Mount the SD card to your computer.
Step 6: Find the mounted drive on the computer (may be D:, E:, F:, G:, for example) by opening My Computer. Open it.
Step 7: Go into the APNBackup&Restore folder.
Step 8: Right click on your backed up APNs (maybe like 201009041233-apns.xml or something or whatever you named them when you did a Backup APNs)n
Step 9: Open with Notepad or Word Pad if it asks you.
Step 10: Highlight all text with your mouse, or use Ctrl + A to select all.
Step 11: After all text is highlighted, use Ctrl + C to copy the text OR go to the 'Edit' menu at the top with your mouse, and choose 'Copy'.
Step 12: Reply to this topic in this thread, right click in the text box where you type, and choose 'Paste'.
Step 13: Revel in good feelings as you provide very valuable help to the Android community.
Thank you ahead of time, if you are willing to help.
yea do that for sure! and also maybe somebody who has root can grab the mms.apk and .odex files too =\
Uploaded with ImageShack.us
Okay so I've made a custom theme pack for myself, now I just need to know if there's a program out there, for un-rooted users, that will allow me to manually change each existing icon myself? If anyone knows of such a program please reply with it, including some information on where I could find the program.
Thanks in advance to anyone who takes the time to help out, there's a couple quid in it for the 1st successfull program/method that works exactly how I want it to.
Please note, I don't particularly want to edit each file .apk manually to change its icon =D
How many views and no one wants to make any money?
Sent from my HTC Hero using XDA App
It is not possible to change something like the icons without root as it would need access to modify the apk files
Okay so given that I'm looking for a nice simple 1 click root, once found what would be the cards in the deck then?
Sent from my HTC Hero using XDA App
You could change the shortcut icon on the homescreen for example with a program called anycut, or the paid one called bettercut
Otherwise you will need root acses
Edit: Or (Don't know if this works someone might need to correct me ) if you get each apk of the app you want to change the icon on, just open the apk and replace the icon
EDIT2: Nvrmnd read the first post slowly
I've already sussed out the homescreen icons and yeah it makes a massive difference to me, but idealy I want every icon changing to the way I want it, is there a 1clickroot method for Hero?
LeeRiley said:
I've already sussed out the homescreen icons and yeah it makes a massive difference to me, but idealy I want every icon changing to the way I want it, is there a 1clickroot method for Hero?
Click to expand...
Click to collapse
Don't know if it works but I know there is an app called "Universal Androot" (not sure it's on the market) that you can search for on google
LeeRiley said:
I've already sussed out the homescreen icons and yeah it makes a massive difference to me, but idealy I want every icon changing to the way I want it, is there a 1clickroot method for Hero?
Click to expand...
Click to collapse
Hmm... Umm... I got two methods that im not sure if they'll work, first search the market for androot (i think) and try root it that way, second download ROM Manager from the market and install the clockwork mod recovery, there the closest ways to 1 click i think
Max, you got any kind of IM, this reward looks like it's going to you lol, just need a couple of things clearing up, you sound like you know what you're doing and the fact that I've had a pub in the county you live in makes it that little bit better!
C0mpu13rFr34k said:
Don't know if it works but I know there is an app called "Universal Androot" (not sure it's on the market) that you can search for on google
Click to expand...
Click to collapse
Obviously you've rooted your Hero? What method did you use, I'm all for the confusing methods, I'm just not that familiar with ADB and the commands and what my phones running or what 'MOD' I'm currently on. It's all a lickle hazy to me as of right now, hence why I'm willing to pay someone for their precious time =D
LeeRiley said:
Max, you got any kind of IM, this reward looks like it's going to you lol, just need a couple of things clearing up, you sound like you know what you're doing and the fact that I've had a pub in the county you live in makes it that little bit better!
Click to expand...
Click to collapse
Thanks ; But btw i'll do it w/o the reward thanks Umm.. sorry not at the moment otherwise id have MSN if you need anyhelp just PM me
Also, somewhere good to check out would be www.theunlockr.com
I'm not willing to accept time without payment! I've had a little look but I don't understand all this build number and software stuff
Sent from my HTC Hero using XDA App
LeeRiley said:
I'm not willing to accept time without payment! I've had a little look but I don't understand all this build number and software stuff
Sent from my HTC Hero using XDA App
Click to expand...
Click to collapse
Haha Okay
First thing, could you go into (on your phone) Settings, ABout phone, Software infromation and then write what it says under Firmware version
Hey I've got to go for a bit now
I reccomend looking here seems simple
http://theunlockr.com/2010/10/11/how-to-root-your-android-phone-superoneclick-method/
And that should work
Now we're down to business! 2.1-update1, I done that myself =D lol then I updated something else to 3.35.61.2 if this is to any use =S
Hehe I can't keep up anymore. It's such a long time since I rooted my phone I have no idea what I did Anyways the trick is to let out what you don't need. Software number etc. often doesn't matter. It's pretty easy actually. When you get root you can very easily install a recovery. Basically you just download Amon_RA from the dev section and type in some basic commands in a terminal emulator on your phone AFAIK (that is when you have gained root which you hopefully can with a one-click method) and then you can start modding flashing etc.
ADB is really easy to set up. You download the zip file from here, extract it and (I recommend) put the extracted folder on your system drive. Now you can rename it to something easy like "adb" or "Android". If you open your command prompt by typing in "cmd" in the search bar in start (if you're using Windows Vista or 7) or opening "run" and then typing in "cmd". You can now type in "cd yoursystemdrive:\thenameofthefolder\tools" and start using ADB commands. Like adb ls -1 system/app (this will list all your system apps. You can replace "system" with "data". Thos will list all your installed apps) or adb pull nameoftheapkyouwanttoedit.apk \adirectoryyouwanttocopyitto (this will copy an app you want to modify. To modify it you can extract with WinRAR or 7zip etc. and edit the images (except the ones that ends with ".9.png")) and at last adb push \thedirectorythemodifiedapkisin systemordata/app (this will put the modified apk on your phone).
Hope this helps a little
Rooted with ease (http://forum.xda-developers.com/showthread.php?t=803682) thanks to Max for the help with the link and what not. Just looking at RomBuddy now to flash some custom shiznet over, quite exciting stuff to be honest, any help on that won't go missed C0mpu13rFr34k
LeeRiley said:
Rooted with ease (http://forum.xda-developers.com/showthread.php?t=803682) thanks to Max for the help with the link and what not. Just looking at RomBuddy now to flash some custom shiznet over, quite exciting stuff to be honest, any help on that won't go missed C0mpu13rFr34k
Click to expand...
Click to collapse
You did see my previous post right?
Logging onto my pc now
Sent from my HTC Hero using XDA App
Okay maybe not lol, keep getting an error with Rom manager saying can't download cyanogen and when I tried to backup I got a black screen with a red triangle?
Sent from my HTC Hero using XDA App
I have used my moto x as a droid pod so i have no cellular connection and my home wifi is screwy so i can't set automatic time and rely on it. The time doesn't set itself when using automatic options. which is fine with me i can just do it manually no problem, right?
Wrong, i haven't really discovered a pattern yet but it seems that every time i reboot my clock sets itself ahead 1h 3m. i think after a series of reboots its totally wrong now. my time currently is 9:50pm and the clock on the phone is 2:58am. the clock in recovery is in synce with the os time but it also skips ahead with reboots i think as i said i really havent determined a clear pattern among issue
any advice? build.prop edit? i did my first edit this evening and it made me feel like a fricken genius so im cool with that but i doubt that there is anything wrong with build.prop. my OS is heavily modified with exposed framework using Xblast and/or gravity box. any help appreciated and will be thanked therefore.
me myself and i said:
my OS is heavily modified with exposed framework using Xblast and/or gravity box
Click to expand...
Click to collapse
i'd start there. recover from stock firmware and start over.
640k said:
i'd start there. recover from stock firmware and start over.
Click to expand...
Click to collapse
ill try thanks for the response
Hey all,
First off, I'm a newbie. Sorry if I offend the order around here, or anything!
So I am a long-time lover of substratum, and was looking forward to theming 9.0 on this Razer phone 2... But I've tried my damnedest since I got it back in early March, and from where I am now, it appears it's hopeless. Anybody gotten Subs working? I'm running mr0, magisk fully updated, trying to apply swift dark. (And yes, the magisk module installed properly for Subs), and I even get no error codes (in fact, the app claims everything's working), but no themes appear under the 'manage' tab. Halp!
Razer Phone 1 & 2 can only use themes signed with the system key thru Razer Theme store. It's coded in framework-res.apk to verify if I remember correctly. Someone might be able to remove the code check and make a install zip for TWRP that can be used with the deodexed ROM here.
DarkestSpawn said:
Razer Phone 1 & 2 can only use themes signed with the system key thru Razer Theme store. It's coded in framework-res.apk to verify if I remember correctly. Someone might be able to remove the code check and make a install zip for TWRP that can be used with the deodexed ROM here.
Click to expand...
Click to collapse
Deodexed ROM? For the phone 2? Also is twrp available besides the kernel one? Am I just missing something? ?
xttweaponttx said:
Deodexed ROM? For the phone 2? Also is twrp available besides the kernel one? Am I just kidding something? ?
Click to expand...
Click to collapse
just look on some xda threads smh ?
RKBD said:
just look on some xda threads smh ?
Click to expand...
Click to collapse
Yeah sorry, I sent that post super late last night, made a bad typo. And as far as I was aware, there isn't any ROM's or TWRP..? But I guess I missed something, eh?
xttweaponttx said:
Yeah sorry, I sent that post super late last night, made a bad typo. And as far as I was aware, there isn't any ROM's or TWRP..? But I guess I missed something, eh?
Click to expand...
Click to collapse
...
https://forum.xda-developers.com/razer-phone-2/development/rom-mr1-stock-deodexed-zipalign-t3916502
Working fix for substratum
found this on another thread and im suprised to not see this anywhere else but anywho, this is the only working way to get substratum on the Razer 2 ive been able to find and its pretty easy to use. https://forum.xda-developers.com/apps/magisk/module-smali-patcher-0-7-t3680053 get this, run the .exe, patch for signature verification (if you have any problems try a different charger, make sure you have usb debugging on, and run .exe as admin) then when its done running look for the .zip and run it through twrp/magisk.
Geneticus21 said:
found this on another thread and im suprised to not see this anywhere else but anywho, this is the only working way to get substratum on the Razer 2 ive been able to find and its pretty easy to use. https://forum.xda-developers.com/apps/magisk/module-smali-patcher-0-7-t3680053 get this, run the .exe, patch for signature verification (if you have any problems try a different charger, make sure you have usb debugging on, and run .exe as admin) then when its done running look for the .zip and run it through twrp/magisk.
Click to expand...
Click to collapse
GASP. I will give this a shot! Thank you -- you have quite possibly made my day!
Geneticus21 said:
found this on another thread and im suprised to not see this anywhere else but anywho, this is the only working way to get substratum on the Razer 2 ive been able to find and its pretty easy to use. https://forum.xda-developers.com/apps/magisk/module-smali-patcher-0-7-t3680053 get this, run the .exe, patch for signature verification (if you have any problems try a different charger, make sure you have usb debugging on, and run .exe as admin) then when its done running look for the .zip and run it through twrp/magisk.
Click to expand...
Click to collapse
Hey actually I wanna confirm; have you gotten this working on mr1?
You've got me cautiously giddy -- the day may have come that google play music will release it's white and orange grip on my eyeballs ?
Work's fine for me
xttweaponttx said:
Hey actually I wanna confirm; have you gotten this working on mr1?
You've got me cautiously giddy -- the day may have come that google play music will release it's white and orange grip on my eyeballs ?
Click to expand...
Click to collapse
Lol now what kind of person would I be to say stuff like that and not test it myself? In all seriousness yeah it works in running pitch black/biohazard as we speak.
Geneticus21 said:
Lol now what kind of person would I be to say stuff like that and not test it myself? In all seriousness yeah it works in running pitch black/biohazard as we speak.
Click to expand...
Click to collapse
lol! Very kind of you -- super stoked, gonna try it today!!! Thanks so much!
xttweaponttx said:
lol! Very kind of you -- super stoked, gonna try it today!!! Thanks so much!
Click to expand...
Click to collapse
yw mate
Ok so update! Using both swift dark and swift black results in the same 2 issues=
-notifications almost go black, but are instead a light light gray on swift dark (making the white text hard to read) and go dark gray on swift black. I've never used swift black prior to tonight, so maybe I've just never seen how dark swift black does it's notifications, and am thus ignorant! For this issue, I double and triple checked I had both Android system & system ui themed, reboot, enable, reboot. To no avail.
I also noticed with both theme packs that the play store doesn't theme at all, but that when viewing an app's page, the title text is white (and thus invisible).
This is just a heads up for those of us working with this now. I'm gonna let the devs know and see if they have any advice or are able to bugfix. Thanks again guys -- play music is buttery black!
Just to clarify...
Geneticus21 said:
Lol now what kind of person would I be to say stuff like that and not test it myself? In all seriousness yeah it works in running pitch black/biohazard as we speak.
Click to expand...
Click to collapse
In order to get Substratum working is the custom ROM https://forum.xda-developers.com/razer-phone-2/development/rom-mr1-stock-deodexed-zipalign-t3916502 required or can a stock MR1 rooted ROM be used using the method described here https://forum.xda-developers.com/apps/magisk/module-smali-patcher-0-7-t3680053
Thanks in advance,
RJR
rrusek said:
In order to get Substratum working is the custom ROM https://forum.xda-developers.com/razer-phone-2/development/rom-mr1-stock-deodexed-zipalign-t3916502 required or can a stock MR1 rooted ROM be used using the method described here https://forum.xda-developers.com/apps/magisk/module-smali-patcher-0-7-t3680053
Thanks in advance,
RJR
Click to expand...
Click to collapse
So I've been running subs for a little while through both methods, so either works. Both methods produce the same result, but I've found that the ROM has some minor bugs that can be obstructive at their worst. EG, every now and then my taps register as long holds (for example, on my keyboard I'll look up and see a bunch of jumbles of symbols instead of the words I tried to type)
But regardless, both methods fail to get the system themed. They try, but notifications are unreadable, and the theme color of the quick settings panels doesn't change from the Razer green.
tl'dr, I'd stick with the smali patcher method, as the ROM has some quirks that can make it a hassle to use as a daily driver.
xttweaponttx said:
So I've been running subs for a little while through both methods, so either works. Both methods produce the same result, but I've found that the ROM has some minor bugs that can be obstructive at their worst. EG, every now and then my taps register as long holds (for example, on my keyboard I'll look up and see a bunch of jumbles of symbols instead of the words I tried to type)
But regardless, both methods fail to get the system themed. They try, but notifications are unreadable, and the theme color of the quick settings panels doesn't change from the Razer green.
tl'dr, I'd stick with the smali patcher method, as the ROM has some quirks that can make it a hassle to use as a daily driver.
Click to expand...
Click to collapse
Thanks for the response..
Just to followup regarding the smaili method, do I generate the signature for the Substratum install apk or the theme or both. Once the zip is generated then I install using TWRP? Just not really clear what needs the signature and what order things should be installed.
Thanks,
RJR
rrusek said:
Thanks for the response..
Just to followup regarding the smaili method, do I generate the signature for the Substratum install apk or the theme or both. Once the zip is generated then I install using TWRP? Just not really clear what needs the signature and what order things should be installed.
Thanks,
RJR
Click to expand...
Click to collapse
Generate the module zip for your phone. Copy it over and install with Magisk. As for theming, it's seems that the systemui overlay is the issue. Any theme that I install just seems to combine with the systemui one instead of replacing it, causing notifications and certain other areas like parts of setting menus to be unreadable. If we could disable systemui's theming, I think we could get somewhere.
xttweaponttx said:
So I've been running subs for a little while through both methods, so either works. Both methods produce the same result, but I've found that the ROM has some minor bugs that can be obstructive at their worst. EG, every now and then my taps register as long holds (for example, on my keyboard I'll look up and see a bunch of jumbles of symbols instead of the words I tried to type)
But regardless, both methods fail to get the system themed. They try, but notifications are unreadable, and the theme color of the quick settings panels doesn't change from the Razer green.
tl'dr, I'd stick with the smali patcher method, as the ROM has some quirks that can make it a hassle to use as a daily driver.
Click to expand...
Click to collapse
What quirks have you noticed? I don't see anyone in that thread mentioning issues.
I have an issue with the action pill on the bottom of the screenshot attached. Absolutely ignoring the context of the The huge contextual pill on top of my search bar, I seem to get those for a lot of the services I trigger which is fine, it's normal. My issue is they stay on the screen for a really really long time.they last several seconds to almost a minute.
Does anyone know how to reduce the time for those or why that may be happening? Has anyone else faced this issue with their pixel devices specifically? I don't seem to have this issue with my Samsung note 10 plus.
If anyone can provide clarity for me on this I really would appreciate it because it's starting to get annoying lol thank you!
https://github.com/samchugit/Immersive_Gestural_Nav_Bar
Use this module or can be found in magisk app.
The pill is there to avoid the accidentally touch navigation gesture.
keaheng said:
https://github.com/samchugit/Immersive_Gestural_Nav_Bar
Use this module or can be found in magisk app.
The pill is there to avoid the accidentally touch navigation gesture.
Click to expand...
Click to collapse
My apologies I should have been more clear I'm not talking about the tiny pill on the very bottom for navigation I meant that big white contextual overlay on top of my search bar with the contextual text.
Why it is there doesn't bother me it's just that it's there for 30 seconds to a minute sometimes I'm wondering if anybody's been able to come across how to fix that.
plus I don't know how to root my device nor I'm able to learn based off I need tutorials that have been posted so rooting is not an option sadly.
thepersona said:
My apologies I should have been more clear I'm not talking about the tiny pill on the very bottom for navigation I meant that big white contextual overlay on top of my search bar with the contextual text.
Why it is there doesn't bother me it's just that it's there for 30 seconds to a minute sometimes I'm wondering if anybody's been able to come across how to fix that.
plus I don't know how to root my device nor I'm able to learn based off I need tutorials that have been posted so rooting is not an option sadly.
Click to expand...
Click to collapse
Roots super easy on these as long as you can OEM unlock.
Assuming so install the magisk app, pull boot.img from your factory image, patch it with magisk (it will end up in your download folder as magisk_patched.img) and flash it. Boom, wham, pow.
madscribblerz said:
Roots super easy on these as long as you can OEM unlock.
Assuming so install the magisk app, pull boot.img from your factory image, patch it with magisk (it will end up in your download folder as magisk_patched.img) and flash it. Boom, wham, pow.
Click to expand...
Click to collapse
Thanks for the simplification, I gotta figure out if my device can oem unlock. It's an unlocked device purchased in Canada.
This is what I was talking about in my original post. Ignoring why it's there, or it's context. I know why those pop up. My complaint is that they are there for 30 sec to a minute in length. Why does my device do that. It's been getting annoying. Cause other devices I own have the same contextual pill but don't stay for as long as they do on my P4xl
thepersona said:
Thanks for the simplification, I gotta figure out if my device can oem unlock. It's an unlocked device purchased in Canada.
This is what I was talking about in my original post. Ignoring why it's there, or it's context. I know why those pop up. My complaint is that they are there for 30 sec to a minute in length. Why does my device do that. It's been getting annoying. Cause other devices I own have the same contextual pill but don't stay for as long as they do on my P4xl
Click to expand...
Click to collapse
That's definitely not normal behaviour. Could be caused by one of your apps hogging resources and slowing down your phone.
But if it's not that, maybe try a Factory Reset?
thepersona said:
Thanks for the simplification, I gotta figure out if my device can oem unlock. It's an unlocked device purchased in Canada.
This is what I was talking about in my original post. Ignoring why it's there, or it's context. I know why those pop up. My complaint is that they are there for 30 sec to a minute in length. Why does my device do that. It's been getting annoying. Cause other devices I own have the same contextual pill but don't stay for as long as they do on my P4xl
Click to expand...
Click to collapse
Fair. I thought I'd help on root, albeit a tangent.
What you're seeing is not normal. Have you tried a third party launcher like Nova?
madscribblerz said:
Fair. I thought I'd help on root, albeit a tangent.
What you're seeing is not normal. Have you tried a third party launcher like Nova?
Click to expand...
Click to collapse
Much appreciated! And yes I explicitly transfered everything fr pixel launcher on to Nova. I am explicitly using nova as it adds much more freedom and customization, as well as integration with sesame.
But that pop up always pops up in Spotify or files or anything giving me context on what I've done wether I've deleted something, updates a playlist, moved a photo, etc. So I know it's supposed to be there whenever it show up.
The issue is that it should not last longer than like 5 seconds max. And on my device it's 20 seconds or even longer especially when moving Giles around in device storage etc, it's a while before it goes away and has become annoying lol.
madscribblerz said:
Fair. I thought I'd help on root, albeit a tangent.
What you're seeing is not normal. Have you tried a third party launcher like Nova?
Click to expand...
Click to collapse
Plus with regard to root I figure I'm better off waiting until my device is no longer supported because if I root now, it's going to be like going through hell and back trying to get monthly updates or feature drops flashing this flashing that.
that whole procedure seems very tedious and filled with a lot of leg work. And not only am I dumb but I'm also lazy LOL so I hope in three years time rooting a device namely p4xl will become foolproof. Lol
But I might have the spine to delve into it once the p4xl isn't supported by Google
thepersona said:
Much appreciated! And yes I explicitly transfered everything fr pixel launcher on to Nova. I am explicitly using nova as it adds much more freedom and customization, as well as integration with sesame.
But that pop up always pops up in Spotify or files or anything giving me context on what I've done wether I've deleted something, updates a playlist, moved a photo, etc. So I know it's supposed to be there whenever it show up.
The issue is that it should not last longer than like 5 seconds max. And on my device it's 20 seconds or even longer especially when moving Giles around in device storage etc, it's a while before it goes away and has become annoying lol.
Click to expand...
Click to collapse
Not an exact answer, given, but that is a toast message that you're dealing with. You may want to look for options on how to modify the default behavior for toast messages. It likely requires root to modify but if you can do so then that's where it'll be. you may want to look in the settings for the apps where it displays to see if there is some kind of toast notification option to disable.
---------- Post added at 07:41 PM ---------- Previous post was at 07:39 PM ----------
thepersona said:
Plus with regard to root I figure I'm better off waiting until my device is no longer supported because if I root now, it's going to be like going through hell and back trying to get monthly updates or feature drops flashing this flashing that.
that whole procedure seems very tedious and filled with a lot of leg work. And not only am I dumb but I'm also lazy LOL so I hope in three years time rooting a device namely p4xl will become foolproof. Lol
But I might have the spine to delve into it once the p4xl isn't supported by Google
Click to expand...
Click to collapse
It is kind of foolproof, but does require a few manual steps each time you update. Do know that Google does not void the warranty for devices that are rooted.
Personal preference I respect, but I wouldn't let technical obstacles overcome your desire to root at some point. It's actually very simple compared to other devices I've had including the earlier pixels, so if all things are equal the Pixel 4 is the easiest to deal with.
madscribblerz said:
Not an exact answer, given, but that is a toast message that you're dealing with. You may want to look for options on how to modify the default behavior for toast messages. It likely requires root to modify but if you can do so then that's where it'll be. you may want to look in the settings for the apps where it displays to see if there is some kind of toast notification option to disable.
I looked into the settings there's nothing on there specifically or explicitly talking about toast notifications. But that is a clearer answer I just can't seem to figure it out I thought it would have been notification dots but it's not that. Ah well lol
---------- Post added at 07:41 PM ---------- Previous post was at 07:39 PM ----------
It is kind of foolproof, but does require a few manual steps each time you update. Do know that Google does not void the warranty for devices that are rooted.
Personal preference I respect, but I wouldn't let technical obstacles overcome your desire to root at some point. It's actually very simple compared to other devices I've had including the earlier pixels, so if all things are equal the Pixel 4 is the easiest to deal with.
Click to expand...
Click to collapse
Yeah I agree with what you're saying and that's interesting I did not know that Google doesn't void the warranty if one decides to root their device. Thanks for the tidbit. Yeah I agree with you having a technical obstacle overcoming the desire right now is pretty high and it stings because if I knew I could do it in a way where I won't break my device or really mess it up that would have helped. I just recently learned about ADB and I haven't fully grasped the concept but I know enough to just get by lol.
If you know of a guaranteed method on how to root the Pixel 4 XL without damage to the device I would appreciate a link to a thread or even a video. Because everything that I've heard has been hit or miss everybody's gotten different results and potentially bricked or messed up their device there has been more mess ups then success and not been one guaranteed solution on how to root the device in a way where it wouldn't mess something up.
thepersona said:
If you know of a guaranteed method on how to root the Pixel 4 XL without damage to the device I would appreciate a link to a thread or even a video. Because everything that I've heard has been hit or miss everybody's gotten different results and potentially bricked or messed up their device there has been more mess ups then success and not been one guaranteed solution on how to root the device in a way where it wouldn't mess something up.
Click to expand...
Click to collapse
Ok,I'll give you a 101.
First unlock flashing. It's the same for all pixels and consists of 2 steps. The first is changing a setting under developer options (to enable developer options click the build number in about several times until you see it enable) and then toggle OEM unlock to enabled.
Step 2 is booting into fastboot mode (vol down while booting) and actually unlocking the phone (fastboot flashing unlock).
There are help files everywhere on that part so find one you like to get you through those steps. Again in this all pixels are equal, so don't stress if you can't find help for the 4 specifically. Note you do not need to unlock critical, and also note doing this will wipe your device. If you've done it right on startup you'll get a yellow warning screen (ignore).
The next part is rooting. Update your device to the latest factory image (boot in fastboot mode and run flash-all from the zip (remove the -w from the bat file if you don't want to wipe the phone).
Boot the phone after and let it run the ROM upgrade app. Install the magisk app and choose install and in the ROM image you downloaded is a boot.img file you will tell magisk to patch. Do so and in download you'll have a magisk_patched.img file. Move that to your computer, reboot into fastboot mode, and fastboot flash boot magisk_patched.img.
Reboot and you're in business.
I'll keep an eye on this thread and if you run into any problems I'll help you quickly. Also note you can't really destroy a pixel. There is a lot to cover to explain why (and I'm sure some creative soul has managed to) but you can always flash the factory ROM with the -w included in flash-all.bat to recover.
It is scary if you haven't done it, but if you're like me once you're rooted it was so easy you'll feel silly.
To update monthly download the ROM, extract boot.img, patch it with magisk, apply the ROM (no -w), reboot and let the ROM finish, reboot to fastboot mode, flash magisk_patched.img (like above), boot and all is good.
Any questions, just ask.
madscribblerz said:
Ok,I'll give you a 101.
First unlock flashing. It's the same for all pixels and consists of 2 steps. The first is changing a setting under developer options (to enable developer options click the build number in about several times until you see it enable) and then toggle OEM unlock to enabled.
Step 2 is booting into fastboot mode (vol down while booting) and actually unlocking the phone (fastboot flashing unlock).
There are help files everywhere on that part so find one you like to get you through those steps. Again in this all pixels are equal, so don't stress if you can't find help for the 4 specifically. Note you do not need to unlock critical, and also note doing this will wipe your device. If you've done it right on startup you'll get a yellow warning screen (ignore).
The next part is rooting. Update your device to the latest factory image (boot in fastboot mode and run flash-all from the zip (remove the -w from the bat file if you don't want to wipe the phone).
Boot the phone after and let it run the ROM upgrade app. Install the magisk app and choose install and in the ROM image you downloaded is a boot.img file you will tell magisk to patch. Do so and in download you'll have a magisk_patched.img file. Move that to your computer, reboot into fastboot mode, and fastboot flash boot magisk_patched.img.
Reboot and you're in business.
I'll keep an eye on this thread and if you run into any problems I'll help you quickly. Also note you can't really destroy a pixel. There is a lot to cover to explain why (and I'm sure some creative soul has managed to) but you can always flash the factory ROM with the -w included in flash-all.bat to recover.
It is scary if you haven't done it, but if you're like me once you're rooted it was so easy you'll feel silly.
To update monthly download the ROM, extract boot.img, patch it with magisk, apply the ROM (no -w), reboot and let the ROM finish, reboot to fastboot mode, flash magisk_patched.img (like above), boot and all is good.
Any questions, just ask.
Click to expand...
Click to collapse
Thanks brother I appreciate the guide and your patience in explains this and willing to help me out with this. The language and terminology I think is the most intimidating lol. I've got a MacBook pro so hopefully I can give this a shot and it will work with that device.
I'll keep you posted.
thepersona said:
Thanks brother I appreciate the guide and your patience in explains this and willing to help me out with this. The language and terminology I think is the most intimidating lol. I've got a MacBook pro so hopefully I can give this a shot and it will work with that device.
I'll keep you posted.
Click to expand...
Click to collapse
No worries
Only change with a Mac is the flash-all.bat I mentioned will be flash-all.sh.
thepersona said:
Much appreciated! And yes I explicitly transfered everything fr pixel launcher on to Nova. I am explicitly using nova as it adds much more freedom and customization, as well as integration with sesame.
Click to expand...
Click to collapse
I briefly tried Nova (but went back to Action Launcher) and I don't remember having that kind of problem. Did you have this problem before you switched to Nova?
fclifton said:
I briefly tried Nova (but went back to Action Launcher) and I don't remember having that kind of problem. Did you have this problem before you switched to Nova?
Click to expand...
Click to collapse
Nope not at all I think it occured after some update probably March.because it's been occurring to the point where I've noticed all throughout March I'm now updating to the April security patch so hopefully that will fix it
madscribblerz said:
No worries
Only change with a Mac is the flash-all.bat I mentioned will be flash-all.sh.
Click to expand...
Click to collapse
Hey man do I need to install any Google drivers onto a Mac apparently when I go to the website it says I don't need to but for rooting do I have to do that?
And do I just Google how to fast boot flash a pixel or something in order to get the zip folders you talked about?
Is this walkthrough in the video below the same as the method youre describing? Cause I can't seem to find any guides on how to do that method.
thepersona said:
Hey man do I need to install any Google drivers onto a Mac apparently when I go to the website it says I don't need to but for rooting do I have to do that?
And do I just Google how to fast boot flash a pixel or something in order to get the zip folders you talked about?
Is this walkthrough in the video below the same as the method youre describing? Cause I can't seem to find any guides on how to do that method.
Click to expand...
Click to collapse
That is a much more detailed guide to the approach that I'm describing. I think following it you'll be able to do it without issue. It's the same approach I've been using for months with no issues. I've even gotten so confident in it I don't even back up my phone before I update monthly. I just know things are going to work.
The zip folder comes from Google just search for Pixel 4 factory image and there will be a page with downloads of the most recent ROM files. April was just released yesterday. That's the file that you want to download and will have the boot.img in it.
I'm not certain on a Mac, but on a PC you have to download the USB drivers and then the platform tools from Google in order to have what you need to make this work. But I think the guide you're referring to will be able to give you that stuff.
---------- Post added at 06:25 PM ---------- Previous post was at 06:01 PM ----------
thepersona said:
Hey man do I need to install any Google drivers onto a Mac apparently when I go to the website it says I don't need to but for rooting do I have to do that?
And do I just Google how to fast boot flash a pixel or something in order to get the zip folders you talked about?
Is this walkthrough in the video below the same as the method youre describing? Cause I can't seem to find any guides on how to do that method.
Click to expand...
Click to collapse
The ROM site is https://developers.google.com/android/images
I figured out my original issue on this post. It was in accessibility, the setting was called time to take action timeout! Now it's fixed. The bloody toast notification is back to default!
thepersona said:
I figured out my original issue on this post. It was in accessibility, the setting was called time to take action timeout! Now it's fixed. The bloody toast notification is back to default!
Click to expand...
Click to collapse
Awesome news. I learned something so win-win. :good: