Search results

Don't listen to these people. You are doing a great job and many of us appreciate your work. Thank you so much for your effort and keep up the good work! :good:

You seem super argumentative for some reason. I never told the user that it should never be changed ever. Just that I would not advise it. As an IT professional, you of all people should understand there are sometimes multiple solutions to a single problem. You seem to be standing on the point...

You need to go back and read my post. I didn't suggest Viper. I suggested a simple kernel tweak. As an IT professional, my default stance will always be to not compromise security. Doesn't really matter what my use case is. I just said I wouldn't advise it. People that don't understand or know...

1.) The guy asked about getting better speaker volume, not sound quality. So my post is relevant as I never claimed my solution provided better sound quality. I have my speaker gain set to 10 and get no distortion or clipping. 2.) I would advise against setting SEPolicy to permissive is not a...

I flashed 10.3.5 then 8.6.1 10/4/20 build and have not issue with mobile data on Verizon.

I posted this previously in the thread but here is what I do.... I use an app called SmartPack-Kernel Manager for turning up call volume. https://play.google.com/store/apps/d....kernelmanager You can then use the Earpiece Gain option under the Sound panel on the left hand pane.

It's under Settings > Security > gear icon next to Screen Unlock > first setting is called Quick Unlock

Thank you sir, all fixed now! :good:

Getting 'verification failed' using OTA updater. Currently on September 1st build.

I use an app called SmartPack-Kernel Manager for turning up call volume. https://play.google.com/store/apps/details?id=com.smartpack.kernelmanager You can then use the Earpiece Gain option under the Sound panel on the left hand pane.

I would also like to know about this.

I started on RR back in the 8.4.x versions with OOS 10.3.2 as my base and have dirty flashed almost every version and am now on RR 8.5.7 with no issues. Not guaranteed to work for everyone but I don't have issues.

Same here.

Thanks for picking support back up for our phone!

I was having the same issue on the 4/10 build. I was dirty flashed from the 4.1.69. Flashing the 4/13 build doesn't have this issue for me.

I don't use Chrome cast but I can confirm this bug exists for me as well.

Nvm

Same.

Nope, thats exactly what the 493 dpi version fixes.

Textdroider won't work as it require system write access. That's why we have a special DPI build listed in the OP.

Confirmed, you can just install the apk. I then used xposed gel settings to hid the stock dialer from the app draw.

Just checked. Build.prop is correct in version C.

Just checked. Build.prop is correct in version C.

I don't think this is accurate. The screen dims at the 22 second mark and then continues to play the remainder of the 45 second long boot animation. Not a huge inconvenience, but probably not worth it imo.

Will this play the entire boot animation? This would extend boot time by about 20-25 seconds.

To my knowledge, no.

Did you reboot after installing and activating app settings in xposed?

Not aware of a fix for command center, I use dashclock The clock on the lock screen can be fixed by following instructions in the OP:

Well, from one dev to another, I know the hours that go in to what you do for us. You deserve every penny and more. Keep up the good work.

Thanks for the fix. Donation sent to keep the 493 dpi build alive going forward. Transaction ID 5CG99499R1968132K

Possible to get a changelog for this version?

493 DPI build is set to 640 DPI in build.prop ---------- Post added at 09:56 AM ---------- Previous post was at 09:55 AM ---------- Yes, active, I have the same issue.

Think of it like changing the resolution on your monitor. Lowering the DPI on your phone is like increasing the resolution on your monitor. You get more screen real estate and icons don't look as big or take up so much room. Even the default DPI of 640 isn't the native DPI (565) of our screen...

CF, I have flashed and tested this build. Confirming that it fixes issues with hangouts/play store/swiftkey. The fix for Moto display mentioned in your OP also works as intended. For those interested. Here is an album showing some before and after shots of 640 DPI vs the 493 DPI build...

Dont have a fix but can confirm I have the same issue on Verizon.

Have rebooted multiple times as well as wiped cache. I will wait for other users to report and reflash if needed. Thanks.

Getting constant force closes saying Bluetooth Share has stopped.

Confirmed SMS bug is fixed on Verizon s4

Where is the main thread for this rom? Looks like this one isn't active anymore after our device tree was unified. Sent from my SCH-I545 using Tapatalk

Anyone have problems with gapps? Can't download anything. Sent from my SCH-I545 using Tapatalk

Dirty flashed from a very old 2013 weekly. Smoking fast and no issues on RC3! Sent from my SCH-I545 using Tapatalk

Dirty flashed after cache wipe. All good. Sent from my SCH-I545 using Tapatalk

As in, a quick reboot. Just taking a minute to reboot. Sent from my SCH-I545 using Tapatalk

Same here. Quick reboot clears it up. Wouldn't make me go back to The though. Sent from my SCH-I545 using Tapatalk

Switch location settings to device only. Sent from my SCH-I545 using Tapatalk

http://www.teamandroid.com/gapps/

I'll be down if someone steps forward. Sent from my SCH-I545 using Tapatalk 4 Beta

+1 Sent from my SCH-I545 using Tapatalk 4 Beta

+1 I know that MEA soft bricks the phone and you have to nandroid to get going again. But there is no 2.1 update in the ME2 folder.

I am using the ME2