Develop Bugs

"themer beta" does not work.

hi, i have a gnexus with slimbean v1.8 and mpokang-v10 "superam version".
the application is installed correctly, but when I go to download a theme it says that my device is not supported.
Please help me.

ipernexus said:
hi, i have a gnexus with slimbean v1.8 and mpokang-v10 "superam version".
the application is installed correctly, but when I go to download a theme it says that my device is not supported.
Please help me.
Click to expand...
Click to collapse
Had the same problem on my gnex with PA 3.99 RC2, for me it was a problem with the DPI settings. If I remember correctly Slimbean came with a altered DPI setting out of the box. Maybe you can fiddle with that, I know it worked for me

xxxmarienxxx said:
Had the same problem on my gnex with PA 3.99 RC2, for me it was a problem with the DPI settings. If I remember correctly Slimbean came with a altered DPI setting out of the box. Maybe you can fiddle with that, I know it worked for me
Click to expand...
Click to collapse
my LCD density is set to 245.. is this the problem? :S

ipernexus said:
my LCD density is set to 245.. is this the problem? :S
Click to expand...
Click to collapse
Yes, set it to the stock dpi for gnex, 320 I believe. Then you should be good.
Sent from my Galaxy Nexus using xda app-developers app

You also need to keep the navbar size on default...
Gesendet von meinem Galaxy Nexus mit Tapatalk

to get around it and keep the dpi that you want, you could install xposed framework and use the Play Store Fixes module from the downloads section in framework installer, and set it to fake 320 dpi and no restrictions path. i use it on carbon rom with a dpi of 260 and never have a play store issue, including themer beta.

OR you can try a different rom. Dont get me wrong I like slimbean but, Im just saying

I like how the op says themer beta doesn't work at all but he's using a custom rom like slimbeam, really...., you should say it doesn't work on slimbeam instead of blaming the app, works flawless on stock 4.3 even for a beta.

Change LCD density/dpi

I'm running most recent cm11/cMetal ROM and am trying to change the LCD density from stock to 240. I've got ROM toolbox pro and tried to use the built in build.prop editor but it doesn't seem to work.
Is this a 4.4 issue? I've tried in r/w and r/o and it does not work (I only did that because someone mentioned it during my research.)
Has anyone had any success or have any tips?

legal.xchech said:
I'm running most recent cm11/cMetal ROM and am trying to change the LCD density from stock to 240. I've got ROM toolbox pro and tried to use the built in build.prop editor but it doesn't seem to work.
Is this a 4.4 issue? I've tried in r/w and r/o and it does not work (I only did that because someone mentioned it during my research.)
Has anyone had any success or have any tips?
Click to expand...
Click to collapse
I'm also wanting to change and haven't found a way yet .

legal.xchech said:
I'm running most recent cm11/cMetal ROM and am trying to change the LCD density from stock to 240. I've got ROM toolbox pro and tried to use the built in build.prop editor but it doesn't seem to work.
Is this a 4.4 issue? I've tried in r/w and r/o and it does not work (I only did that because someone mentioned it during my research.)
Has anyone had any success or have any tips?
Click to expand...
Click to collapse
Navigate to /system/build.prop using Solid/Root explorer and open it in text editor and change the property ro.sf.lcd_density to 240 or whatever you like. Then reboot.

RajatPatel said:
Navigate to /system/build.prop using Solid/Root explorer and open it in text editor and change the property ro.sf.lcd_density to 240 or whatever you like. Then reboot.
Click to expand...
Click to collapse
Yup, that worked! I'm a little disappointed I didn't think of editing it manually myself. Oh well. Thanks for the help!

I just tried this on the newest CM11 nightly and got a bootloop. Anyway to fix this?

Unchange said:
I just tried this on the newest CM11 nightly and got a bootloop. Anyway to fix this?
Click to expand...
Click to collapse
Dirty flash your ROM.
Sent from my Galaxy Nexus using XDA Premium HD app

mrgnex said:
Dirty flash your ROM.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
I don't mean how to fix the boot loop; I mean how can I get the LCD density change to stick without a boot loop?

Unchange said:
I don't mean how to fix the boot loop; I mean how can I get the LCD density change to stick without a boot loop?
Click to expand...
Click to collapse
There is no reason your lcd density should have caused a bootloop unless you configured the numbers outside of the galaxy nexus proper density radius or you messed with the wrong thing in build.prop. Try downloading Build Prop Editor from the play store and only modify the LCD Density.

DPI 280 is so clear and comfortable.

With latest nightly cm-11-20140120 I am unable to change the lcd density. Seems lcd_density attribute in build.prop is ignored... Anyone experiencing this issue?

mgaw said:
With latest nightly cm-11-20140120 I am unable to change the lcd density. Seems lcd_density attribute in build.prop is ignored... Anyone experiencing this issue?
Click to expand...
Click to collapse
It's the only thing I manually change after dirty flashing each nightly and has always worked for me. I'm on toroplus for what it's worth...and I ran the 20th, 21st and now 22nd nightlies.

yotvb531 said:
It's the only thing I manually change after dirty flashing each nightly and has always worked for me. I'm on toroplus for what it's worth...and I ran the 20th, 21st and now 22nd nightlies.
Click to expand...
Click to collapse
Actually, with 22nd it works again for maguro.

Tweks build.prop [No-Lag] G531H

Especially for G531H
Talk about Build.Prop, one of the most important files on your phone, where you save the values ​​that make it work the way you do.
Whenever we talk about customizing an Android terminal, we usually talk about changing the ROM and some kernel parameters. The build.prop, despite being even more modifiable than the above, is one of the great forgotten. This buil.prop, is a file that contains properties and configurations of the compilation of our Android. Some parameters are added by the manufacturer, and others depend on the hardware of your device and the Android base itself.
As you can imagine, to modify a file of such caliber requires root permissions, and that is necessary write permissions. By default, build.prop comes only in read mode, so we do not change anything by mistake.
☆ Just flash it via recovery
[Tweks]
☆Increase dalvik cache to avoid some FC.
☆Increase performance.
☆To increase the buffer size of Internet connections and improve speed.
☆Forcing launcher in memory (always keeps the launcher in memory allowing him back from applications faster).
☆Improved quality jpeg 100%.
☆Increased virtual RAM memory.
☆Render the system interface with the GPU.
☆Scroll scrolling enhancement (can be edited a little higher or lower according to likes).
☆Improve Screen Response.
☆Improved image quality and video 100%.
You can try it in G530XXXXXXXX or G531XXXXXXXXX and Rom's AOSP: Just add the text of the file that will leave you (Tweaks.txt) in the build.prop below each line has, space and handles. I'll leave you an example ...

how do i install ?

madfox_280 said:
how do i install ?
Click to expand...
Click to collapse
If your on G531H model just download the already edited build.prop that is supported by your device and flash it via recovery.
And if your on device that is not G531H (like G530H, G530A etc.) Download the Tweaks.txt . Open the text file and copy all the texts in there. After that using any Root explorer mount /system as RW and goto /system and first make a backup of your current build.prop and after that open up the build.prop file and paste the text that you copied and reboot your device to see the changes.

should i install stock or slimsamy? (i'm using g531h)

madfox_280 said:
should i install stock or slimsamy? (i'm using g531h)
Click to expand...
Click to collapse
If you have the Stock rom only donwload G531-Stock.zip and flash it via TWRP
Sent from my SM-G531H using XDA Labs

MUELAJE said:
Especially for G531H
Talk about Build.Prop, one of the most important files on your phone, where you save the values ​​that make it work the way you do.
Whenever we talk about customizing an Android terminal, we usually talk about changing the ROM and some kernel parameters. The build.prop, despite being even more modifiable than the above, is one of the great forgotten. This buil.prop, is a file that contains properties and configurations of the compilation of our Android. Some parameters are added by the manufacturer, and others depend on the hardware of your device and the Android base itself.
As you can imagine, to modify a file of such caliber requires root permissions, and that is necessary write permissions. By default, build.prop comes only in read mode, so we do not change anything by mistake.
☆ Just flash it via recovery
[Tweks]
☆Increase dalvik cache to avoid some FC.
☆Increase performance.
☆To increase the buffer size of Internet connections and improve speed.
☆Forcing launcher in memory (always keeps the launcher in memory allowing him back from applications faster).
☆Improved quality jpeg 100%.
☆Increased virtual RAM memory.
☆Render the system interface with the GPU.
☆Scroll scrolling enhancement (can be edited a little higher or lower according to likes).
☆Improve Screen Response.
☆Improved image quality and video 100%.
You can try it in G530XXXXXXXX or G531XXXXXXXXX and Rom's AOSP: Just add the text of the file that will leave you (Tweaks.txt) in the build.prop below each line has, space and handles. I'll leave you an example ...
Click to expand...
Click to collapse
pff I installed zip Tweaks zip in recovery when i reboot the phone it's stay on boot

Dsn Fouad said:
pff I installed zip Tweaks zip in recovery when i reboot the phone it's stay on boot
Click to expand...
Click to collapse
Could you tell what device you have?
and baseband please

MUELAJE said:
Could you tell what device you have?
and baseband please
Click to expand...
Click to collapse
G531h grand prime

Dsn Fouad said:
G531h grand prime
Click to expand...
Click to collapse
Wich rom you are running?
Sent from my SM-G531H using XDA Labs

MUELAJE said:
Wich rom you are running?
Click to expand...
Click to collapse
RR 5.8.4

MUELAJE said:
Wich rom you are running?
Click to expand...
Click to collapse
So ?

[FIX] Proximity sensor on Redmi Note 7 and Note 7 Pro (NEEDS ROOT)

1) Install File Explorer Root Browser
2) Go to System folder
3) Scroll all the way down and opet build.prop file
4) Add these 2 lines at the end of the file:
Code:
ro.lge.proximity.delay = 150
mot.proximity.delay = 150
5) Save the file
6) Reboot

is this a permanent fix or what?
and how did u figure it out?
thx by the way

It should be permanent. Waiting to see will it stay fixed after rom update tho.
I did a lot of research, tried some apps but it did not work, and finally found this fix on some chinese forum.

mr_techno said:
1) Install File Explorer Root Browser
2) Go to System folder
3) Scroll all the way down and opet build.prop file
4) Add these 2 lines at the end of the file:
5) Save the file
6) Reboot
Click to expand...
Click to collapse
Delay is already set at 200 in build.prop. I doubt just changing the delay fixes much.
Keep us posted on the fix…ya never know

fox_xda2 said:
Delay is already set at 200 in build.prop. I doubt just changing the delay fixes much.
Keep us posted on the fix…ya never know
Click to expand...
Click to collapse
Well I did not have delay in my build.prop (using pixel experience plus rom) and so far, no more issues with the sensor. Maybe try and change it to 150? What rom are you using?

mr_techno said:
Well I did not have delay in my build.prop (using pixel experience plus rom) and so far, no more issues with the sensor. Maybe try and change it to 150? What rom are you using?
Click to expand...
Click to collapse
PE 10.
AFAIK the instable proximity sensor issue is due to a poor driver released in a Xiaomi firmware, nothing so easy to solve.

Just registered to say my formerly non-operational proximity sensor now works perfectly (Pixel Experience)! Thanks very much.

Sentox6 said:
Just registered to say my formerly non-operational proximity sensor now works perfectly (Pixel Experience)! Thanks very much.
Click to expand...
Click to collapse
Mine too following the OP instructions ?
fox_xda2 said:
Delay is already set at 200 in build.prop. I doubt just changing the delay fixes much.
Keep us posted on the fix…ya never know
Click to expand...
Click to collapse
Worked with OP instructions.
Sent from my Redmi Note 7 using XDA Labs

Thanks, it worked perectly on PE 9!

Thanks a lot! Worked wonderfully on PE 9!

if this fix doesnt work and youve tried all kinds of "fixes" you may want to check out this if you have previously changed the screen or frame or had any hardware repair done to your xiaomi redmi note 7, there may be small peices you forgot to install. https://forum.xda-developers.com/redmi-note-7/how-to/fix-xiaomi-redmi-note-7-proximity-t4008965

Did it, seems that solved my problem to hear whatsapp audios outside in the sun. Ty

For now works like a charm in MIUI 11.0.3.0 Global, thanks.
:good:

Just want to say thanks for this fix. Works with PE10 with latest Delta update. For those who don't want root can uninstall magisk after editing build prop no problem at all

CR Droid 6.2 12JAN release. Nothing has changed unfortunately with this trick :crying:

Thanks. I am on Havoc 3.1 and the it fixed it.

Well, this can be included for sure, if y'all can let me know this actually works, I'd add the prop to the device tree. Thanks!

Disable high volume warning

Hi, I want to disable the High volume warning, I already have a solution, right now I use terminal shortcut pro and have created a shortcut to run the command
Code:
settings put global audio_safe_volume_state 0
it work great but doesn't survive a reboot so I have to run the shortcut after every reboot. I found an old thread on reddit that say adding the line
Code:
audio.safemedia.bypass=true
to build.prop can also disable the high volume warning, but the thread was so old, they were talking android 6.0
I plan to try to add this prop on boot using the magisk module MagiskHide Props Config, I know it work great because I already added a prop to reduce the media volume steps to 15 instead of 30, but i dont know if the prop
Code:
audio.safemedia.bypass=true
is still working on android 10
Another solution would be to have an app that run the terminal command
Code:
settings put global audio_safe_volume_state 0
automatically after boot, but I would prefer to add the prop line if anyone can confirm it still work on android 10
Thank you all !

Nice to know.... what's also wondering from time to time how to overcome the warning. let me know if you get it to a working solution.
Just for the last part: tasker would be the way to go.
Gesendet von meinem HD1903 mit Tapatalk

xe0r said:
Nice to know.... what's also wondering from time to time how to overcome the warning. let me know if you get it to a working solution.
Just for the last part: tasker would be the way to go.
Gesendet von meinem HD1903 mit Tapatalk
Click to expand...
Click to collapse
After 24 hours testing the audio.safemedia.bypass=true with MagiskHide Props Config, I have not seen the warning yet, but I need to test it longer to be sure it work

Just a quick update for future search, the prop
Code:
audio.safemedia.bypass=true
seem to work, I have not seen the high volume warning for the whole week, so problem solved !

Hey one question, how were you able to edit the build.prop file? Whenever I try to do so with Root Explorer, it doesn't save my changes. OnePlus 8 Pro Android 10

memocatcher said:
Hey one question, how were you able to edit the build.prop file? Whenever I try to do so with Root Explorer, it doesn't save my changes. OnePlus 8 Pro Android 10
Click to expand...
Click to collapse
Only with Magisk module MagiskHide Props Config

jacobyo7 said:
Just a quick update for future search, the prop
Code:
audio.safemedia.bypass=true
seem to work, I have not seen the high volume warning for the whole week, so problem solved!
Click to expand...
Click to collapse
Hello and thank you for finding a workaround for this stupid issue! Do you know if this is still working on android 11? After installing the module, how can I correctly set it? Thank you so much for your help

I tried setting it with termux but it's not working

addsfsds said:
I tried setting it with termux but it's not working
Click to expand...
Click to collapse
I still use it with 11 on my OP7T but I am unsure if this prop remove the audio warning or if there is no warning at all on my device. Never tried 11 wihtout the prop so IDK.
Another way you can try is the system UI tuner app on the play store, there is a setting to disable the warning under the audio & sound category. Good luck !

jacobyo7 said:
I still use it with 11 on my OP7T but I am unsure if this prop remove the audio warning or if there is no warning at all on my device. Never tried 11 wihtout the prop so IDK.
Another way you can try is the system UI tuner app on the play store, there is a setting to disable the warning under the audio & sound category. Good luck !
Click to expand...
Click to collapse
Thank you for your reply! I kept trying to no avail. Can't make it work unfortunately. When you upgraded to android 11, did you make the procedure again from scratch? Can you please explain what you did on termux?
Is the system ui app an app that it's aways on background?
Thank you so much!

addsfsds said:
Thank you for your reply! I kept trying to no avail. Can't make it work unfortunately. When you upgraded to android 11, did you make the procedure again from scratch? Can you please explain what you did on termux?
Is the system ui app an app that it's aways on background?
Thank you so much!
Click to expand...
Click to collapse
No the system UI tuner app just change some hidden android settings, it do not run in the background. The description of the app even state you can delete the app once you changed the desired setting. Read the whole description to understand how it work. Try it, I think this might be the best solution.
SystemUI Tuner - Apps on Google Play
PLEASE READ ENTIRE DESCRIPTION BEFORE INSTALLING
play.google.com

jacobyo7 said:
No the system UI tuner app just change some hidden android settings, it do not run in the background. The description of the app even state you can delete the app once you changed the desired setting. Read the whole description to understand how it work. Try it, I think this might be the best solution.
SystemUI Tuner - Apps on Google Play
PLEASE READ ENTIRE DESCRIPTION BEFORE INSTALLING
play.google.com
Click to expand...
Click to collapse
Thank you for your kind suggestion. I tried and again it didn't work, really don't know why.

addsfsds said:
Code:
settings put global audio_safe_volume_state 0
Thank you for your kind suggestion. I tried and again it didn't work, really don't know why.
Click to expand...
Click to collapse
i can confirm that no app does change the setting of safe volume limit.
All tests on rooted device from LOS14-LOS19. Tried different apps like systemuituner, safevolumelimitdisabler, volumesteps+, jamesdsp etc.
Tried to patch the global variable "safe_media_volume" like described here on a rooted device but no luck.
Just ran
[adb shell] settings put global audio_safe_volume_state 0
via adb, when the message popped up, afterits i had to confirm the nag-screen, to raise the volume. it's so weird..