Related
Is there any way to put the m8 softkeys on the m7? I think they looks nice and I miss virtual keys
DigeiDiBaviera said:
Is there any way to put the m8 softkeys on the m7? I think they looks nice and I miss virtual keys
Click to expand...
Click to collapse
Yes, you can easily enable this:
Add this line in your build.prop:
qemu.hw.mainkeys=0
And you will have virtual keys.
Maik268 said:
Yes, you can easily enable this:
Add this line in your build.prop:
qemu.hw.mainkeys=0
And you will have virtual keys.
Click to expand...
Click to collapse
It works fine, thanks.
Just 2 problems:
The stock launcher looks like that: (look attacments)
And the return (or back) key doesnt work.
Then, is there any way to turn off the led of the touchkeys?
Sorry for all the questions and thanks for your help
DigeiDiBaviera said:
It works fine, thanks.
Just 2 problems:
The stock launcher looks like that: (look attacments)
And the return (or back) key doesnt work.
Then, is there any way to turn off the led of the touchkeys?
Sorry for all the questions and thanks for your help
Click to expand...
Click to collapse
That's because all Sense 6 ROMs are using a patched Launcher, so there is no gap if you are not using onscreen keys.
So, I don't know how to solve this issue and I also don't know, why back button isn't working :/
Use this App to turn of the led lights: https://play.google.com/store/apps/details?id=org.sleepydragon.capbutnbrightness
You can also disable the M7 keys completely if you modifie the key_layout file.
Thanks, will find a way to make back button works
Dont forget to hide your old bottons with a black marker.
Try using gravity box with xposed module. It has a softkey setting. I only used it briefly but I don't think I had the issue you had.
I Changed the LCD Density to 350 and your problem was resolved in my case.
But it Changed at Homescreen. Now its not fit in the lockstreen
LCD Density 370
Sent from my HTC One using XDA Premium 4 mobile app
try arhd 60
on the first sense 6 ports the software keys looked perfect when added to the build prop once the launcher got patched it messed up software keys
It failed to work on insert coin 2.4.0
CrazyPhoneHacker said:
It failed to work on insert coin 2.4.0
Click to expand...
Click to collapse
The build.prop command?
Working here on Insert Coin 2.4.0
Maik268 said:
The build.prop command?
Working here on Insert Coin 2.4.0
Click to expand...
Click to collapse
Yea. The build.prop.
Do I have to put a specific spot in the build.prop
CrazyPhoneHacker said:
Yea. The build.prop.
Do I have to put a specific spot in the build.prop
Click to expand...
Click to collapse
Nope. I added this at the bottom of build.prop
qemu.hw.mainkeys=0
Maik268 said:
Nope. I added this at the bottom of build.prop
qemu.hw.mainkeys=0
Click to expand...
Click to collapse
What is the property for that file. rwx --- ---?
CrazyPhoneHacker said:
What is the property for that file. rwx --- ---?
Click to expand...
Click to collapse
You don't have to change it. Simply edit the original file and make a backup before.
But it's rw-r--r--
u have to do a reboot after edit the build.prob ...
gagp2p said:
u have to do a reboot after edit the build.prob ...
Click to expand...
Click to collapse
I did but nothing happen
---------- Post added at 04:12 PM ---------- Previous post was at 03:54 PM ----------
Turns out there are two build.props. in my phone one that's In the sydtem folder and one in aroma. So I just added the line to both build.props and it worked out
CrazyPhoneHacker said:
It failed to work on insert coin 2.4.0
Click to expand...
Click to collapse
Same :good:
hoangps said:
Same :good:
Click to expand...
Click to collapse
If you have es file manager this is what I did to get it to work once you enter the systems folder in the root of the phone search for the build.prop if you are on insert coin 2.4.0 there should be two of them that show up I added the code to both build props then change their properties to rw- r--r-- and reboot and it worked but for insert coin the back button don't work so I switched back to arhd because of that and everything worked and also my extreme power saving mode doesn't activate.
Navbar hide:http://forum.xda-developers.com/showpost.php?p=53099871&postcount=43
Thanks :majrul
Full Phonemaneger:
http://forum.xda-developers.com/showpost.php?p=53080047&postcount=35
Thanks::BeyondTheHorizon
Go guys post more tricks here.
Enable FAST BOOT
Open build.prop in text editor :
Find this line : ro.config.hw_quickpoweron=false Changing the ro.config.hw_quickpoweron=false into ro.config.hw_quickpoweron=true will add in Settings the Fast boot option
Restart required.
After reboot you will fing the option between Printing and Developer options in Settings. It's called Fast boot.
Tested. Result : Working.
ENJOY IT.
kabirjedi said:
Navbar hide:http://forum.xda-developers.com/showpost.php?p=53099871&postcount=43
Thanks :majrul
Full Phonemaneger:
http://forum.xda-developers.com/showpost.php?p=53080047&postcount=35
Thanks::BeyondTheHorizon
Go guys post more tricks here.
Click to expand...
Click to collapse
There are three other threads in general section about B510. There was no need to start a fourth one.
primo said:
There are three other threads in general section about B510. There was no need to start a fourth one.
Click to expand...
Click to collapse
You are moderator ?No?
Then?
Need this. Too much topic less info in one place.
This specific only useful information collection.
Sorry for english.
Thank you BeyondTheHorizon i try now.
Double tap while in Lockscreen and you will get music control.
Also edit this in build.prop to manage what apps will boot when the device starts and also to manage alerts.
Find this line ro.config.hw_privacymode=false and change it into ro.config.hw_privacymode=true
BeyondTheHorizon said:
Double tap while in Lockscreen and you will get music control.
Also edit this in build.prop to manage what apps will boot when the device starts and also to manage alerts.
Find this line ro.config.hw_privacymode=false and change it into ro.config.hw_privacymode=true
Click to expand...
Click to collapse
Epic!
Thanks
How to hide OPERATOR name in status bar
Find this line in local.prop : ro.config.hw_showSimName=true and change it into ro.config.hw_showSimName=false
NOTE : This is local.prop not build.prop
Is Xposed working? Maybe some usefull module..??? thanks
XDAvatar said:
Find this line in local.prop : ro.config.hw_showSimName=true and change it into ro.config.hw_showSimName=false
NOTE : This is local.prop not build.prop
Click to expand...
Click to collapse
This isn't working for me, unfortunately. [emoji22]
EDIT: I even tried adding the line to the build.prop file, and still nothing. *sigh* [emoji22]
Sent from my Huawei P6
XDAvatar said:
Find this line in local.prop : ro.config.hw_showSimName=true and change it into ro.config.hw_showSimName=false
NOTE : This is local.prop not build.prop
Click to expand...
Click to collapse
I have 14 files with names on my device.
With one we have to change?
HornetRider said:
I have 14 files with names on my device.
With one we have to change?
Click to expand...
Click to collapse
All of them.
---------- Post added at 04:24 PM ---------- Previous post was at 04:23 PM ----------
raptor92 said:
Is Xposed working? Maybe some usefull module..??? thanks
Click to expand...
Click to collapse
Yes but not the latest. Use version 2.5.1 and XBLAST module.
XDAvatar said:
All of them.
---------- Post added at 04:24 PM ---------- Previous post was at 04:23 PM ----------
Yes but not the latest. Use version 2.5.1 and XBLAST module.
Click to expand...
Click to collapse
Working without having to modify anything in build.prop?
raptor92 said:
Working without having to modify anything in build.prop?
Click to expand...
Click to collapse
Yes.
XDAvatar said:
All of them.
Click to expand...
Click to collapse
I changed the line in all 14 files, but the name ist still shown.
I'm in Germany with Congstar.
HornetRider said:
I changed the line in all 14 files, but the name ist still shown.
I'm in Germany with Congstar.
Click to expand...
Click to collapse
If it doesn't work, use Xposed Framework + XBLAST module.
NOTE : Do not install Xposed 2.6 because it's not working. Use the version 2.5.1
I already tried to hide the provider text with xblast and Gravity Box.
But this also didn't work.
I was only able to hide the text on the bottom of the notification panel, but not in the statusbar.
No matter what I change in build.prop, after restart it's back to it's previus setting.
I rooted the phone with vroot(does this even work?), but I cannot change build.prop lines.
sale 83 said:
No matter what I change in build.prop, after restart it's back to it's previus setting.
I rooted the phone with vroot(does this even work?), but I cannot change build.prop lines.
Click to expand...
Click to collapse
Root it with TWRP.
Hey,
hope it's ok if i post this here.
For the permission manager, i've extracted the Source of the B507 and B510 PhoneManager apk's.
As far i understand the smali code, it seems that the permission manager is still in place but disabled via source code.
It would be nice if a apk hacker could take a look and compare the two versions.
Have a nice day, all
---------------------------------------------------------------------------
Found a way to start the permission manager in B510.
On the play store get https : //play . google . com/store/apps/details?id=de.szalkowski.activitylauncher
there open from the top "all activitys"
search for Phone Manager and open it
next look for the permission manager entry and start it (long press for shortcut).
there you can enable it.
i've made some rough testing and it seems as it's working the way we expect it.
Happy restricting ^^
XDAvatar said:
Root it with TWRP.
Click to expand...
Click to collapse
Tnx, but I have found the "problem", I tried to change build.prop line with es explorer, but it was on read/only, needed to check read/write option.
This is the new oneplus camera app
All features are working
Camera 2 api required for pro mode
Panorama not work on camera 2 it fully working on camera 1api
Aby lad said:
All features are working except manual mode and panorama
I think our Moto camera app is better than oneplus camera app
Click to expand...
Click to collapse
Are you on stock rom..becoz the camera screen appears to be black on RR latest build
Soham Biswas said:
Are you on stock rom..becoz the camera screen appears to be black on RR latest build
Click to expand...
Click to collapse
Yes
Camera2 api needed
Aby lad said:
Camera2 api needed
Click to expand...
Click to collapse
I apologise but .
What is that i don't know.. Please give a link if possible.
Is it this code?
persist.camera.HAL3.enabled=1
Pasted it on build prop..but not working ?
Soham Biswas said:
I apologise but .
What is that i don't know.. Please give a link if possible.
Is it this code?
persist.camera.HAL3.enabled=1
Pasted it on build prop..but not working
Click to expand...
Click to collapse
persist.camera.HAL3.enabled=1 enables camera 2 but in rr or other custom rom it's not working.
I can see only a black screen with a toast notification "unknown error"
Ashokk8 said:
I can see only a black screen with a toast notification "unknown error"
Click to expand...
Click to collapse
It's working
.
You should have mentioned about root.
Make clear OP before posting
Soham Biswas said:
I apologise but .
What is that i don't know.. Please give a link if possible.
Is it this code?
persist.camera.HAL3.enabled=1
Pasted it on build prop..but not working
Click to expand...
Click to collapse
In custom rom for our device camera2 is not working .
Not works in du...
Sent from my Moto G4 Plus using XDA-Developers Legacy app
Aby lad said:
persist.camera.HAL3.enabled=1 works on any custom rom .
Click to expand...
Click to collapse
Where do you edit that code? Do you have any source?
pissgoat said:
Where do you edit that code? Do you have any source?
Click to expand...
Click to collapse
This only enables camera 2 but Hals,libs,drivers are also required for camera 2 to work
which one to install?
Aby lad said:
All features are working except manual mode and panorama
I think our Moto camera app is better than oneplus camera app
Camera2 required
Click to expand...
Click to collapse
Among the 2 file, which one should i install?
Rajeshkm said:
Among the 2 file, which one should i install?
Click to expand...
Click to collapse
Both are working .
Aby lad said:
All features are working except panorama.
Updated file has pro mode working .
Camera2 required
Raw image
Click to expand...
Click to collapse
How to enable camera2api?
iSpringrolls said:
How to enable camera2api?
Click to expand...
Click to collapse
Add this line in build prop
persist.camera.HAL3.enabled=1
Has someone been able to correctly take a RAW photo? If the answer is yes, how? My ROM has camera2 enabled, and I've tried some apps but all of them end up giving a DNG file that cannot be edited or opened. This camera didn't even created a file!
sagalfisz said:
Has someone been able to correctly take a RAW photo? If the answer is yes, how? My ROM has camera2 enabled, and I've tried some apps but all of them end up giving a DNG file that cannot be edited or opened. This camera didn't even created a file!
Click to expand...
Click to collapse
DNG is the universal raw format from Adobe. Use Lightroom or Photoshop to edit it.
strongst said:
DNG is the universal raw format from Adobe. Use Lightroom or Photoshop to edit it.
Click to expand...
Click to collapse
That Is my issue! I take the pictures, and then every editor in existence fails to open them saying that they can't be opened or that they are corrupt. So I guessed I was doing something wrong or using the wrong apps. Which camera are you using? This one?
Can anyone suggest me how to hide navigation keys ???
himanshuOJHA said:
Can anyone suggest me how to hide navigation keys ???
Click to expand...
Click to collapse
The process requires adb commands thru PC if you are not rooted! Activate Immersive Display using any quick tiles app after granting necessary permissions thru adb..
himanshuOJHA said:
Can anyone suggest me how to hide navigation keys ???
Click to expand...
Click to collapse
If you are rooted, follow these steps :
1. Open build.prop
2. Set "qemu.hw.mainkeys=0" to 1.
3. Reboot
Asder.mko said:
If you are rooted, follow these steps :
1. Open build.prop
2. Set "qemu.hw.mainkeys=0" to 1.
3. Reboot
Click to expand...
Click to collapse
I can not find this entry in build.prop
letschky said:
I can not find this entry in build.prop
Click to expand...
Click to collapse
Yep, I found it in AOSP roms, unfortunately not directly present in build.prop of honor 7x.
aha thanks,i am on Stockrom,I managed to change entries in the build.prop,but it is not that easy,i use a modified build prop from AL10 version
letschky said:
aha thanks,i am on Stockrom,I managed to change entries in the build.prop,but it is not that easy,i use a modified build prop from AL10 version
Click to expand...
Click to collapse
Hello, please can you send me stock HONOR 7x /system/build.prop and /system/vendor/build.prop. Thank you
DallasCZ said:
Hello, please can you send me stock HONOR 7x /system/build.prop and /system/vendor/build.prop. Thank you
Click to expand...
Click to collapse
Sorry I do not have the Honor 7x anymore.
which version L21 Bxxx?
any
DallasCZ said:
any
Click to expand...
Click to collapse
Oreo or Nougat?
letschky said:
Oreo or Nougat?
Click to expand...
Click to collapse
any as i said any.
I have been using System UI Tuner successfully to selectively enable immersive mode on some apps without root:
https://play.google.com/store/apps/details?id=com.zacharee1.systemuituner&hl=en
Its not that hard using adb run adb shell then type (wm overscan 0,0,0,-122) for the perfect setting im running this with a x bar app for swiping the home key instead of keys no root needed
If you have EMUI 8.0 you can do it without root. Go to System - System Navigation - Navigation Bar - Click on navigation bar.
This will enable an extra button on the navigation bar to hide it.
DallasCZ said:
any as i said any.
Click to expand...
Click to collapse
Ok here is it.
and here from vendor
letschky said:
and here from vendor
Click to expand...
Click to collapse
thank you very much
DallasCZ said:
thank you very much
Click to expand...
Click to collapse
No Problem Man
letschky said:
No Problem Man
Click to expand...
Click to collapse
And please. If you have terminal emulator apk, could you just run it and enter the commnad "getprop" and send me the result (list of commands). Thank you very much again.
DallasCZ said:
And please. If you have terminal emulator apk, could you just run it and enter the commnad "getprop" and send me the result (list of commands). Thank you very much again.
Click to expand...
Click to collapse
Command List is here
http://adbshell.com/commands/adb-shell-getprop
and
Terminal Emulator
https://www.apkmirror.com/apk/jack-palevich/terminal-emulator/terminal-emulator-1-0-70-release/terminal-emulator-1-0-70-android-apk-download/
Hi,
My camera2api settings lost when I got latest update of MIUI 10.2.1.0 Global Stable.
My RN5 Pro is rooted having TWRP recovery.
Can anyone help?
jahidkhan1978 said:
Hi,
My camera2api settings lost when I got latest update of MIUI 10.2.1.0 Global Stable.
My RN5 Pro is rooted having TWRP recovery.
Can anyone help?
Click to expand...
Click to collapse
I again tried to enable it by running camera2api enabler Magisk module which I got from XDA thread. But still it doesn't work.
jahidkhan1978 said:
I again tried to enable it by running camera2api enabler Magisk module which I got from XDA thread. But still it doesn't work.
Click to expand...
Click to collapse
Download buildpropeditor from playstore https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor&hl=en_IN
and add the following lines to the buildprop , save it and then reboot.
persist.camera.HAL3.enabled=1
persist.camera.eis.enable=1
jaidev.s said:
Download buildpropeditor from playstore https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor&hl=en_IN
and add the following lines to the buildprop , save it and then reboot.
persist.camera.HAL3.enabled=1
persist.camera.eis.enable=1
Click to expand...
Click to collapse
Thanks bro. It tried this method and it works. Thanks a lot.
jaidev.s said:
Download buildpropeditor from playstore https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor&hl=en_IN
and add the following lines to the buildprop , save it and then reboot.
persist.camera.HAL3.enabled=1
persist.camera.eis.enable=1
Click to expand...
Click to collapse
And how about to disable it? Same method?
Remig83 said:
And how about to disable it? Same method?
Click to expand...
Click to collapse
Absolutely no idea, sorry.
jaidev.s said:
Absolutely no idea, sorry.
Click to expand...
Click to collapse
Hello sir ...
Want to ask about camera2api ..
For the record, my device is RN5 and uses Miui 10.0.6.0 and already UBL, also installed Magisk and TWRP applications and already rooted.
- What impact will it have if we activate camera2api via the Magisk application ..?
- Does activating the camera can increase the default camera result (front or rear camera)?
- Does activating the camera, will not affect other applications that require camera access? For example WhatsApp (VideoCall), Google Duo, Facebook Messenger, etc.
Thanks ..
Remig83 said:
And how about to disable it? Same method?
Click to expand...
Click to collapse
Keep the default build prop copy as backup somewhere & replace if you wish to reverse back. Keep in mind default miui camera won't work but all other third party apps will work properly.
Thanks so much
does vilte call work after enabling the camera2api
shamsud said:
does vilte call work after enabling the camera2api
Click to expand...
Click to collapse
Yes, it works