Related
I'm using damage control and I used his JIT thing cause people on here talk about it a lot and it said disable sense.. So I'm guessing that meant don't check it? Now my phone keeps re booting. How can i fix this.. I didn't nandriod back up so is there a easy way to do it by just remaining or something? Thanks
MyDroidHax said:
I'm using damage control and I used his JIT thing cause people on here talk about it a lot and it said disable sense.. So I'm guessing that meant don't check it? Now my phone keeps re booting. How can i fix this.. I didn't nandriod back up so is there a easy way to do it by just remaining or something? Thanks
Click to expand...
Click to collapse
You're gonna have to go to an older nandroid. Sense and JIT just don't play well.
What you should have done is checked "Sense Apps" in the "Banned Apps" screen.
Keep in mind that any sense widget, like the HTC clock, and I think the rosie will stop working.
DevinXtreme said:
You're gonna have to go to an older nandroid. Sense and JIT just don't play well.
What you should have done is checked "Sense Apps" in the "Banned Apps" screen.
Keep in mind that any sense widget, like the HTC clock, and I think the rosie will stop working.
Click to expand...
Click to collapse
Rosie= sense ui
And yes everything htc will not work, wallpapers will give you problems, htc lockscreen gives you problems and every widget connected to sense.
You will need to make sure they are banned in dconfig before you enable jit and reboot.
I know im just restating somethings but im just putting it all in one spot. Making it clear lol
DevinXtreme said:
You're gonna have to go to an older nandroid. Sense and JIT just don't play well.
What you should have done is checked "Sense Apps" in the "Banned Apps" screen.
Keep in mind that any sense widget, like the HTC clock, and I think the rosie will stop working.
Click to expand...
Click to collapse
Rosie= sense ui
And yes everything htc will not work, wallpapers will give you problems, htc lockscreen gives you problems and every widget connected to sense.
You will need to make sure they are banned in dconfig before you enable jit and reboot.
I know im just restating somethings but im just putting it all in one post to make it clear. lol
MyDroidHax said:
I'm using damage control and I used his JIT thing cause people on here talk about it a lot and it said disable sense.. So I'm guessing that meant don't check it? Now my phone keeps re booting. How can i fix this.. I didn't nandriod back up so is there a easy way to do it by just remaining or something? Thanks
Click to expand...
Click to collapse
you could manually pull the required files. not sure what they are, but you can manually edit the DConf file that lists banned programs, etc.
Funny you guys talking about this i just went from the new fresh rom not toast to damage because i tried to get jit to work on the most recent fresh and my phone went in a boot loop after trying to install JIT on it. It works fine for the new damage control tho... even though i manually installed it and didnt know dc config had the option for it all along otherwise this phone is runnin like a crackhead who stole my car radio.
Powers16 said:
Funny you guys talking about this i just went from the new fresh rom not toast to damage because i tried to get jit to work on the most recent fresh and my phone went in a boot loop after trying to install JIT on it. It works fine for the new damage control tho... even though i manually installed it and didnt know dc config had the option for it all along otherwise this phone is runnin like a crackhead who stole my car radio.
Click to expand...
Click to collapse
I did this by accident too ... and during the force close SenseUI loop, it let me get to dconfig (after like 15 force closes) really quickly and uncheck JIT.
Don't swipe the lock screen while JIT + SenseUI enabled either, use Menu, it's more responsive.
I am working on an application which will shut down my sons media player only captivate at a specific time. I have it working but am not particularly good at drawing or coming up with good ideas for an icon for it.
Does anybody have any ideas?
AutoShutdown.apk
FYI I built it for 2.2 but tested it on 2.3 (my captivate) and it requires root access (it essentially creates a service that at a specific time calls "reboot -p".
Update Info:
1.10 Changed to using an Alarm.
1.5 Moved the Save button to the bottom.
1.4 Revamped to use a Handler instead of a thread thus reducing the overhead because I am not checking the time every 45 seconds, I just delay the shutdown for however many milliseconds it would take to get to the requested time.
1.3 Fixed the not shutting down issue (at least under 2.3, I will test on 2.2 tonight). Added alpha channel to the icon.
1.2 Added simple icon
1.1 Added an Enabled checkbox. Setting the shown time to the last time entered. Fixed killing the old thread.
1.0 Basically worked with whatever the last time you entered
Well this worked in testing via the debugger but for some reason my sons phone isn't turning off...
1.3 fixes this problem. I was being a bit too aggressive on waiting for a thread to end.
I have found that 2.2's reboot command does not accept the -p parameter which means that this will not work. If some one has another method I would be more than happy to add it in.
Only tested to work on 2.3, primarily under Fusion XII. Its been working fine for me.
very cool idea., any idea if it'll work on ICS?
No clue since i don't have a device with ICS.
can i use in motorola milestone or other device ?
kevria said:
I have it working but am not particularly good at drawing or coming up with good ideas for an icon for it.
Click to expand...
Click to collapse
I'd suggest a power icon with clock hands on it as the icon. If you want I could make a quick one for you.
saeed.salek.b said:
can i use in motorola milestone or other device ?
Click to expand...
Click to collapse
I have no clue but you can try. It's all based on the reboot executable
codyrt said:
I'd suggest a power icon with clock hands on it as the icon. If you want I could make a quick one for you.
Click to expand...
Click to collapse
That would be neat. My wife made that one up pretty quickly.
I have just verified that the code still works under Android 4.2.2.
cron4phone app, free on google play, does same, and also lets you vary schedule by day, etc, and schedule many other tasks as well. you do need root for it to work.
Good to know. I had originally made it for my sons phone.
Hello kevria,
Are you still working on this project? I have a couple of suggestions.
havork said:
Hello kevria,
Are you still working on this project? I have a couple of suggestions.
Click to expand...
Click to collapse
I havent been but I still have the source code so could modify it as needed. I also havent had a reason to use this since my son's android device died.
My condolences
Well, I can't find a countdown shutdown app anywhere, was wondering if you could make do so.
Not on a specific time, but like 1 Hour or 10 minutes count down.
Hope you will be interested :fingers-crossed:
I will see if I can get the source to build and make the change. Im pretty sure I had it calculating out the amount of time from now until the shutdown time so it should be simple to modify the code.
The app isnt building due to a xml error that I will have to track down when I have time. You could use the app as is and figure out what 1.5 hours from now is...
Hello try creating a shortcut on your home screen, go to the application manager.
I have lost the source code to this app so I won't be able to make any changes.
Sent from my Nexus 4 using Tapatalk
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??
There have beth two apps I've installed lately who's widgets have not shown up in the widget menu immediately after installation. With the Chronus clock it took a while before it showed up as a selectable option. It showed up on the lock screen widget menu, but not the home screen one. The other was a photo frame widget. Has anyone else had this happen or know of a fix? It's super annoying.
Sent from my Moto X
GreenMunky said:
There have beth two apps I've installed lately who's widgets have not shown up in the widget menu immediately after installation. With the Chronus clock it took a while before it showed up as a selectable option. It showed up on the lock screen widget menu, but not the home screen one. The other was a photo frame widget. Has anyone else had this happen or know of a fix? It's super annoying.
Sent from my Moto X
Click to expand...
Click to collapse
I have the same issues. a phone restart will fix it. but that seems to be a bit ridiculous.
jiro09 said:
I have the same issues. a phone restart will fix it. but that seems to be a bit ridiculous.
Click to expand...
Click to collapse
I agree. I installed the GEL today but the issue is still present. Does anyone know of a fix for this?
Sent from my Moto X
GreenMunky said:
I agree. I installed the GEL today but the issue is still present. Does anyone know of a fix for this?
Sent from my Moto X
Click to expand...
Click to collapse
darn it...i was hoping a launcher change would fix it. was it doing this on 4.2.2? Ive only had the Moto X under 4.4...
jiro09 said:
darn it...i was hoping a launcher change would fix it. was it doing this on 4.2.2? Ive only had the Moto X under 4.4...
Click to expand...
Click to collapse
Don't know. I accepted the Kit Kat OTA less than 24 hours after activating my Moto X. Wasn't until after that I tried adding new widgets. They will eventually appear without a reboot but I have not determined the amount of time it takes or if it's some kind of event or action that makes the Widget menu refresh. Really irritated about this.
Sent from my Moto X
jiro09 said:
darn it...i was hoping a launcher change would fix it. was it doing this on 4.2.2? Ive only had the Moto X under 4.4...
Click to expand...
Click to collapse
Okay... I may have found a possible fix. I enabled ART in Developer options => Select runtime. After letting the process of app optimization to finish, it seems that my widget menu now refreshes immediately, as it should. At least it worked immediately when I downloaded the Yahoo! Weather app... maybe just a fluke but I'll take it. After the first reboot I immediately opened every app I use on a daily basis and everything opened snappily and I got no force closes. I even opened Pandora (I had heard a lot of people having compatibility issues with ART) and it started up just fine and played a song all the way through without a skip, hiccup or error. Only time and experimentation will tell if this is truly a fix to the problem, so I'd really like to hear if it works for you too. Cheers!
GreenMunky said:
Okay... I may have found a possible fix. I enabled ART in Developer options => Select runtime. After letting the process of app optimization to finish, it seems that my widget menu now refreshes immediately, as it should. At least it worked immediately when I downloaded the Yahoo! Weather app... maybe just a fluke but I'll take it. After the first reboot I immediately opened every app I use on a daily basis and everything opened snappily and I got no force closes. I even opened Pandora (I had heard a lot of people having compatibility issues with ART) and it started up just fine and played a song all the way through without a skip, hiccup or error. Only time and experimentation will tell if this is truly a fix to the problem, so I'd really like to hear if it works for you too. Cheers!
Click to expand...
Click to collapse
doing it now... will update after a bit of testing
GreenMunky said:
Okay... I may have found a possible fix. I enabled ART in Developer options => Select runtime. After letting the process of app optimization to finish, it seems that my widget menu now refreshes immediately, as it should. At least it worked immediately when I downloaded the Yahoo! Weather app... maybe just a fluke but I'll take it. After the first reboot I immediately opened every app I use on a daily basis and everything opened snappily and I got no force closes. I even opened Pandora (I had heard a lot of people having compatibility issues with ART) and it started up just fine and played a song all the way through without a skip, hiccup or error. Only time and experimentation will tell if this is truly a fix to the problem, so I'd really like to hear if it works for you too. Cheers!
Click to expand...
Click to collapse
It seems to be working for me...DL'd google keep and widget showed up immediately. things feel snappier as well. I know ART is a bit experimnental so ill have to keep an eye out. Its interesting that the original problem occurred under Dalvik. This type of error would not have surprised me if ART was originally enabled. thanks!!
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.