Hi, I have a p920 working fine, and I recently bought another p920 to my sister.. but that phone got a problem, the 3d feature doesn´t work well, the 2 images get overlaped, getting a double image mixed in the screen, this is happening with any 3d feature in the phone (games, camera, images, videos, etc). It is like a 3d tv without glasses, all blurry
I don´t know what can cause that, I tried a hard reset, and nothing happened.
I can´t find any kind of 3d setup inside the phone either.
Any clue??
Thank you
For first what system is there?
In build.prop you have to check:
ICS - ro.lge.capp_real3d=true
GB - user.feature.real3d=true
If is false change to true. Must be root.
Maybe will help.
bether said:
For first what system is there?
In build.prop you have to check:
ICS - ro.lge.capp_real3d=true
GB - user.feature.real3d=true
If is false change to true. Must be root.
Maybe will help.
Click to expand...
Click to collapse
thank you, where do i find build.prop ? i´m really noob sorry
it is GB, and its not rooted yet but i can do it
thanks in advance
build.prop is is system/ of device.
You can look first that what you have in user.feature.real3d=true or false (you can use some filebrowser)
If is true that you problem is in hardware that device
If is false you must do root and edit build.prop changing to true.
Hi, Guys
My R530's HW version(Setting-About-HW version) was changed to "DingTai" last week, and I want to change it back to "R530U.01", however I could not find any available way to implement this. I tried modifing the build.prop, but it did not work at all. I also tried using adb with setprop command but it back to "DingTai" after reboot.
Seems the HW version information is stored in the RTN data and will not be changed by ROM updates. Is there anyone know how to change it persistently?
Thanks a lot!
Does anyone have a solution for this?
Since I started using PureNexus Lollipop I just can't stand the big soft keys anymore
I tried editing SystemUI.apk, but :
1) I wasn't exactly sure what to change
2) It refused to work after reboot
If anyone has anything that would help me, I would be so happy. :fingers-crossed:
I have installed Cataclysm 6, it has this feature out of the box.
Hello,
I noticed that many of you don't like the CyanogenMod superuser indicator ('#') in the status bar and that some of you even flash SuperSU or Xposed, just to get rid of it. Well, that's not necessary, because there is a much easier way. So here is the "right way" to remove the # in CM13/14.x/Lineage 15.x (probably not working in CM12.x):
Edit: @Dyt199412syam found an easier way to do this, please take a look: https://forum.xda-developers.com/showpost.php?p=73916650&postcount=35
==== Original post ====
1. Go to Settings > status bar > icons
2. Uncheck and re-check one of the items (to make sure the required settings entry is created)
3. Backup the file /data/system/users/0/settings_secure.xml
4. Open /data/system/users/0/settings_secure.xml with a text editor (as root)
5. Search for "icon_blacklist"
6. you will find something like this:
Code:
<settings id="269" name="icon_blacklist" value="" package="com.android.systemui" />
(ID may vary)
7. Add "su" between the quotation marks after value, so it looks like this:
Code:
<settings id="269" name="icon_blacklist" value="su" package="com.android.systemui" />
If value is not empty, just append ",su" (with a seperating comma):
Code:
<settings id="269" name="icon_blacklist" value="other,icons,su" package="com.android.systemui" />
8. Double check the XML syntax (a mistake here might cause a bootloop)
9. Save and reboot
For ROM builders:
If you want to implement an option to hide superuser icon in your ROM, please do not use a hacky, unclean way to do so. The right way is the following:
Open frameworks/base/packages/SystemUI/res/xml/tuner_prefs.xml.
- Search for
Code:
<com.android.systemui.tuner.StatusBarSwitch
android:key="alarm_clock"
android:title="@string/status_bar_alarm" />
and below insert
Code:
<com.android.systemui.tuner.StatusBarSwitch
android:key="su"
android:title="@string/status_bar_su" />
- Add
Code:
<string name="status_bar_su">Superuser</string>
to strings.xml
Or simply apply this patch to frameworks/base.
Working fine! Thanks!
Send with my Moto G4 Plus (XT1642) on CyanogenMod 14.1, Android 7.1, using Tapatalk!
Excellent... Works perfectly on Xeperience 7.1.1 for Moto G 2
Enviado desde mi Moto G 2014 mediante Tapatalk
Works on my LG D724 running CM14.1! Thanks for this!
It works great on CyanogenMod 14.1
Sent from my Moto G 2014 using XDA-Developers mobile app
Thanks!!! Working great on Lineage OS 14.1 using in my Xperia Z2!!!
This works fine on cyanogenmod 14 (lineageOs), droid turbo. Thanks!
Couldn't find "icon_blacklist" on the file, using official LOS 14.1for my device LG v500, can I manually add the line?
Any help?
aaswar said:
Couldn't find "icon_blacklist" on the file, using official LOS 14.1for my device LG v500, can I manually add the line?
Any help?
Click to expand...
Click to collapse
Have you tried to uncheck / check one of the items in Settings/Status Bar/Icons? icon_blacklist should be created after this.
MaxMustermann2.0 said:
Have you tried to uncheck / check one of the items in Settings/Status Bar/Icons? icon_blacklist should be created after this.
Click to expand...
Click to collapse
Thanks a lot, appreciated.
Works fine on Lineage, thanks??
Love you, works fine without having to install xposed mods.
Thank you very much
Which text editor do I use? Im use one without option to "Double check XML syntax" and cause a bootloop on my device
Onedmunds said:
Which text editor do I use? Im use one without option to "Double check XML syntax" and cause a bootloop on my device
Click to expand...
Click to collapse
Double check your XML syntax just means that you shall pay attention that the number of opening and closing brackets (<>) matches and that you don't forget a quotation mark or sth like that.
delete
Thanks to OP this worked on Lineage OS 14.1 on Mi 5
Hello everybody,
Probably, or also surely, caused by the Nova Launcher, always the root # symbol is displayed in the status bar.
This help here would work for me on the S5 and OP3. The Moto G4 does not work that way. After I changed the concerned and then restart the smartphone, suddenly all settings are set to the factory setting .... I copy the previously saved original file over it again, it remains nevertheless there by ... everything on factory setting...
Does anyone know another way that symbol is going to hide?
This Way here does not seem to work with the G4.
Or someone know, maybe what is the Problem?
Thanks in advance
Gustl6500 said:
Hello everybody,
Probably, or also surely, caused by the Nova Launcher, always the root # symbol is displayed in the status bar.
This help here would work for me on the S5 and OP3. The Moto G4 does not work that way. After I changed the concerned and then restart the smartphone, suddenly all settings are set to the factory setting .... I copy the previously saved original file over it again, it remains nevertheless there by ... everything on factory setting...
Does anyone know another way that symbol is going to hide?
This Way here does not seem to work with the G4.
Or someone know, maybe what is the Problem?
Thanks in advance
Click to expand...
Click to collapse
Works fine with Nova Launcher. It is probably the editor or explorer you are using. Are you sure that it has enough permissions to overwrite the file?
Try another editor or root explorer.
tested on seraph unofficial lineage OS on my OP2.
working like a charm, thanks a lot to @MaxMustermann2.0
used MiXplorer to find and edit settings_secure.xml file, and edited it via inbuilt text editor.
So I finally upgraded from my oneplus 7 pro to a oneplus 8t. I'm loving the phone and I found 2 or 3 custom rom options I like.
The problem I keep running into is that I need to modify my build.prop because an app I need to use for work "only runs on samsungs". I've been using my 7 pro for over a year with no problems because I just type in galaxy s8 info to the build.prop.
When I try and modify the build.prop on any android 11 rom, the phone stops booting past the bootloader unlocked screen. I can quickly get back by using fastboot rominstaller.
I've tried using multiple build.prop apps, I've tried editing the file through root managers, I've tried moving it to a different folder then editing it and putting it back and that doesn't work either. I tried magiskhide props config and it looks like it works but doesn't.
Did something happen with android 11? I don't even know where to start on this.
Thanks for absolutely any help at all
f2bacon said:
I tried magiskhide props config and it looks like it works but doesn't.
Click to expand...
Click to collapse
If you post a detailed description of what you've tried and why you say that it doesn't work in the MagiskHide Props Config thread, preferably with the module logs attached, I might be able to help with that at least...
i'll do that, thank you very much