I edited the build.prop a bit and reversed the changes but the Camera stopped working entirely. What do you guys recommend as a fix?
zoofie666 said:
I edited the build.prop a bit and reversed the changes but the Camera stopped working entirely. What do you guys recommend as a fix?
Click to expand...
Click to collapse
Did you clear the camera apk data and reboot or wipe dalvik in twrp?
Sent from my Moto E (4) using XDA Labs
amarc78 said:
Did you clear the camera apk data and reboot or wipe dalvik in twrp?
Sent from my Moto E (4) using XDA Labs
Click to expand...
Click to collapse
Neither worked for me, unfortunately.
go to build.prop and change the permissions to 644 which will look like -rw-r--r-- that's what I did and fixed it
Try Changing this to get camera to work again
zoofie666 said:
Neither worked for me, unfortunately.
Click to expand...
Click to collapse
I use build.prop editor to change “camera.disable_zsl_mode” change from 1 to 0 (Zero) if camera does not work and reboot the phone.
Camera did not work for me after adding these two lines to allow tethering on my Moto E4 Plus XT1775: net.tethering.noprovisioning=true and tether_dun_required 0
Once I changed the 1 to a 0 (Zero) the camera regained functionality
ziggyzoz said:
I use build.prop editor to change “camera.disable_zsl_mode” change from 1 to 0 (Zero) if camera does not work and reboot the phone.
Camera did not work for me after adding these two lines to allow tethering on my Moto E4 Plus XT1775: net.tethering.noprovisioning=true and tether_dun_required 0
Once I changed the 1 to a 0 (Zero) the camera regained functionality
Click to expand...
Click to collapse
Thank you, That fixed my issue on Lineage OS!
Awesome
zerogun said:
Thank you, That fixed my issue on Lineage OS!
Click to expand...
Click to collapse
Awesome! ...glad it worked for you.
Related
Hey guys was just wondering if anyone can post a video with a changed DPI? I'm not routes and I heard it can be done without root but wanted to see what it looks like first would really appreciate it
syphern said:
Hey guys was just wondering if anyone can post a video with a changed DPI? I'm not routes and I heard it can be done without root but wanted to see what it looks like first would really appreciate it
Click to expand...
Click to collapse
Not sure where you heard it can be done without root. Because it simply can't. Without root you cannot modify system files.
Sent from my Nexus 6P using Tapatalk
It can be done without root but needs to be done using ADB on a PC.
On your PC while the phone is connected:
ADB shell
WM density 480 (or whatever you want for your device)
Restart your device to complete.
Just try it. U can easily go back to default. But i promise, u dont want :b
I am rooted on my Nexus 6P, although I cannot get it to change the dpi settings.
I tried using texdroider_dpi, tried the adb method and even went to /system/build.prop and changed it via ES File Explorer.
When I set the DPI to anything but 560 my SwiftKey Keyboard breaks but the overall screen density doesn't change.
The value I entered is still displayed in the build.prop though ..
I had it changed already, but when I updated to the latest security patch 2016 I had to reinstall my phone since I flamingod something I guess.
Went ahead with Heisenbergs guide and followed Step 11 (http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928) to get my phone back to work. Only thing not working now is the dpi change ..
Any help?
Are you mounting system as R/W and saving the build.prop after you change the value?
dastinger said:
Are you mounting system as R/W and saving the build.prop after you change the value?
Click to expand...
Click to collapse
I didn't specifially mount the system as R/W - but when I restart the device afterwards the change is still persistent.
Try using another File Explorer (Fx with the root add-on for example) and make the change with that one mounting as R/W before doing anything else.
dastinger said:
Try using another File Explorer (Fx with the root add-on for example) and make the change with that one mounting as R/W before doing anything else.
Click to expand...
Click to collapse
I love you. #nohomo
Thank you very much.
[emoji4]
No problem, mate.
clubtech said:
It can be done without root but needs to be done using ADB on a PC.
On your PC while the phone is connected:
ADB shell
WM density 480 (or whatever you want for your device)
Restart your device to complete.
Click to expand...
Click to collapse
I do this but my Swiftkey is broken and some image elements are huge.
Does anyone know why something like texdroider used to work perfectly scaling everything and now it does not?
Before this update, after flashing the SuperSU 2.66 my twrp would give me the warning my phone was not rooted. Now, I do not receive this warning.
Sent from my Nexus 6P using Tapatalk
Hello everyone,
My sensor went bad after screen replacement. It always detects as near. Until now I was using xposed to disable it. But now after upgrading to Android N, I don't have xposed and I don't know how to fix it.
The screen is turned off when I make/attend a call, making it difficult to end.
Is there any config file or something in source where I can disable it??
Thank you.
You can use settings>accessibility>Use power button to end call...
Thanks. I am doing what you said now. But still it would be better if I get and solution to disable it.
swapnil0545 said:
Thanks. I am doing what you said now. But still it would be better if I get and solution to disable it.
Click to expand...
Click to collapse
I have not tested in N, but it works in MM.
Copy android.hardware.sensor.proximity.xml the known position and change its string
Code:
<feature name="android.hardware.sensor.proximity" />
to
Code:
<feature name="" />
Go to the TWRP.
Mount the partition system.
Check the permission and assignment to groups for file android.hardware.sensor.proximity.xml
Rename the file android.hardware.sensor.proximity.xml
Copy the changed file android.hardware.sensor.proximity.xml to the /system/etc/permissions
Change the file permission and assignment to groups that have the original file.
Reboot.
The solution for that it change the black thing make the bigger hole on sensor of light and the small one with other
Default for that is small one with sensor light and bigger one for something else
So sorry for bad language see that steps here
http://forum.xda-developers.com/nexus-4/help/proximity-sensor-fix-screen-replacement-t2657176
ze7zez said:
I have not tested in N, but it works in MM.
Copy android.hardware.sensor.proximity.xml the known position and change its string
Code:
<feature name="android.hardware.sensor.proximity" />
to
Code:
<feature name="" />
Go to the TWRP.
Mount the partition system.
Check the permission and assignment to groups for file android.hardware.sensor.proximity.xml
Rename the file android.hardware.sensor.proximity.xml
Copy the changed file android.hardware.sensor.proximity.xml to the /system/etc/permissions
Change the file permission and assignment to groups that have the original file.
Reboot.
Click to expand...
Click to collapse
I am going to try this. I hope I don't soft brick it.
swapnil0545 said:
I am going to try this. I hope I don't soft brick it.
Click to expand...
Click to collapse
Hey did you get it to work?
I've tried - no, did not work on 7.1.
Have you any other solution? I've the same issue on nexus 6p After display replacement. And now on nougat i can't fix it. Simeone Can help me?
My other solution was to recompile Dialer.apk with proximity disabled.
digital0 said:
My other solution was to recompile Dialer.apk with proximity disabled.
Click to expand...
Click to collapse
Where is the apk located? I'm running 7.0 and cannot find it in the system/apps folder.
On CM14 it is in /system/priv-app/Dialer/
digital0 said:
My other solution was to recompile Dialer.apk with proximity disabled.
Click to expand...
Click to collapse
Just FYI how it was done - http://forum.xda-developers.com/showpost.php?p=69507586&postcount=253
You are a life saver
digital0 said:
Just FYI how it was done - http://forum.xda-developers.com/showpost.php?p=69507586&postcount=253
Click to expand...
Click to collapse
You just helped me with the biggest inconvenience on my phone. I used sensor disabler on xposed but this is a perfect fix for a broken proximity sensor and android 7 ?
sweetmyke said:
You just helped me with the biggest inconvenience on my phone. I used sensor disabler on xposed but this is a perfect fix for a broken proximity sensor and android 7
Click to expand...
Click to collapse
hello sir
I have this issue in my nexus 6 and want to disable Proximity Sensor but without Xposed Installer Framework for Android 7,I couldn't.
would you please tell me how did you use this Compiled App????
I don't know how I have to run these command:
adb root
adb remount
adb push Dialer.apk /system/priv-app/Dialer/Dialer.apk
Thank You.
driftking132 said:
I don't know how I have to run these command:
adb root
adb remount
adb push Dialer.apk /system/priv-app/Dialer/Dialer.apk
Click to expand...
Click to collapse
You should run these commands on a PC, to which phone is connected by USB cable.
digital0 said:
Just FYI how it was done - http://forum.xda-developers.com/showpost.php?p=69507586&postcount=253
Click to expand...
Click to collapse
Just out of curiousity, what was the reason to comment out the ALTER TABLE line in DialerDatabaseHelper.java?
I've attached my version of the fix that I've been running since CM13, now recompiled for CM14.1. There's effectively only one line of code changed. Source is up-to-date to Feb 6, 2017.
As far as I can tell, digital0's version works just as well, so there's no reason to try mine if you're not having issues with his.
Same way to install the apk. Attached diff for the curious.
Shimakaze said:
Just out of curiousity, what was the reason to comment out the ALTER TABLE line in DialerDatabaseHelper.java?
Click to expand...
Click to collapse
The CM build I used at the time of compiling gave the error. It is most probably not needed now.
driftking132 said:
hello sir
I have this issue in my nexus 6 and want to disable Proximity Sensor but without Xposed Installer Framework for Android 7,I couldn't.
would you please tell me how did you use this Compiled App????
I don't know how I have to run these command:
adb root
adb remount
adb push Dialer.apk /system/priv-app/Dialer/Dialer.apk
Thank You.
Click to expand...
Click to collapse
Sorry for taking so long to respond but I just used root explorer system/priv-app/dialer and replaced dialer.apk. Make sure that you set the permissions to rw-r-r...reboot, let me know if I helped
sweetmyke said:
Sorry for taking so long to respond but I just used root explorer system/priv-app/dialer and replaced dialer.apk. Make sure that you set the permissions to rw-r-r...reboot, let me know if I helped
Click to expand...
Click to collapse
its worked but in call screen there is no answer/ reject buttons please fix this
After updating my HTC desire 820 dual sim to marshmallow . I found out that marshamallw has a hidden feature of multiwindow that can be accesses by changing a line in build.prop but everytime I edit the build prop and reboot my phone the values in build prop again switches to default values.. here is what i did-
1. Install root browser and mount system with read and write permissions.
2. Open /system/build.prop and search for ro.build.type
3. Change the value from user to userdebug.
4. Reboot the system
!!!! After reboot the value again switches to user
I have tried all methods .. by adb by build prop editor apk... But no successs .. i cant see multiwindow option in developer option ...
PLEASE LOOK FOR SOLUTION ASAP...
You must have root,and s-off, I have do and have this feature now after reboot.
Sent from my HTC_D820u using Tapatalk
misisipiman said:
You must have root,and s-off, I have do and have this feature now after reboot.
Sent from my HTC_D820u using Tapatalk
Click to expand...
Click to collapse
i have already rooted the phone but how can i obtain s-off?
Nipun Gupta said:
i have already rooted the phone but how can i obtain s-off?
Click to expand...
Click to collapse
With xtc2clip or s-shine
Hmm... I think that if I edit build.prop, change ro.build.type and restart only Android framework it could be work.
---------EDIT:
^^ this wouldn't work. Only solution that I see is, reboot to TWRP, mount system partition, connect to pc, adb shell and modify /system/build.prop.
these are few collection of mods that do not have a settings menu to enable or disable them,...
so flash them manually until they can be part of the rom
WARNING: works only in custom roms
Update: CM added support for swapping back and menu buttons from cm-13.0-20161112-NIGHTLY-gemini.zip
==================================
Mods
==================================
1) disable finger print wakeup
2) enable finger print wakeup
3) Xiaomi keys layout(Left Button-> Menu & Right Button-> Back)
4) Android stock keys layout(Left Button-> Back & Right Button-> Menu)
==================================
Downloads: Here
==================================
==================================
Workings
==================================
Enabling/Disabling the FingerPrint Wakeup
Source: github
Mod Location: /sys/devices/soc/soc:fpc_fpc1020/enable_wakeup
Code:
[B]Values:[/B]
1 = Enable
0 = Disable
Changing The Keylayout
Source: github
Mod Location: /system/usr/keylayout/synaptics_dsx.kl
Code:
[B]Xiaomi keys layout:[/B]
key 139 APP_SWITCH VIRTUAL
key 102 HOME VIRTUAL
key 158 BACK VIRTUAL
key 143 WAKEUP
[B]Android stock keys layout:[/B]
key 139 BACK VIRTUAL
key 102 HOME VIRTUAL
key 158 APP_SWITCH VIRTUAL
key 143 WAKEUP
Thanks
Works on xiaomi.eu Roms?
alessandro_masci said:
Works on xiaomi.eu Roms?
Click to expand...
Click to collapse
Yes, but actually that mod for non-miui rom, where some Setting not available on non-miui roms
Sent from my MI 5 using Tapatalk
Uhm.. just flashed in twrp the xiaomi layout zip.... but no change. Not working for me.. cm13 here
Henkl said:
Uhm.. just flashed in twrp the xiaomi layout zip.... but no change. Not working for me.. cm13 here
Click to expand...
Click to collapse
Same here .. Error when flashing..
FrankRr said:
Same here .. Error when flashing..
Click to expand...
Click to collapse
folder structure inside .zip is flashable but there is shouldn't have a folder before /Meta-INF and /System. so that's why it give error message, just extract it and replace manually.
Henkl said:
Uhm.. just flashed in twrp the xiaomi layout zip.... but no change. Not working for me.. cm13 here
Click to expand...
Click to collapse
FrankRr said:
Same here .. Error when flashing..
Click to expand...
Click to collapse
arif_kholid said:
folder structure inside .zip is flashable but there is shouldn't have a folder before /Meta-INF and /System. so that's why it give error message, just extract it and replace manually.
Click to expand...
Click to collapse
Ohh yea my bad!!! Will change them....
EDIT: changed and uploaded new zips
chiragkrishna said:
Ohh yea my bad!!! Will change them....
EDIT: changed and uploaded new zips
Click to expand...
Click to collapse
Thanks. Now flashed (Xiaomi keyboard) and all OK. Buttons have changed as they are supposed to..
Yeah it works now. Thanks!
Update: CM added support for swapping back and menu buttons from cm-13.0-20161112-NIGHTLY-gemini.zip
chiragkrishna said:
Update: CM added support for swapping back and menu buttons from cm-13.0-20161112-NIGHTLY-gemini.zip
Click to expand...
Click to collapse
Hi.
Updated to latest nightly but can't find that option...
Where did u find it? In Settings-Buttons there isn't option to swap...
Edit: Find it...
Settings-Additional buttons
Thanks
Enable fingerprint for stock MIUI works?
thanks bro... it's perfect, i follow the instruction and do it myself with explorer
Fingerprint Wakup works for me. Using miui 8.3 from xiaomi.eu.
Evil_Kreis said:
Fingerprint Wakup works for me. Using miui 8.3 from xiaomi.eu.
Click to expand...
Click to collapse
Hi, what I need to flash to make this mod works on miui 8.3 from xiaomi.eu, too?
Odoslané z Mi5
I just changed the file but it's not permanently. I don't know if there is a way to but if you figured let me know.
Thaks for tutorial. The tutorial makes Xiaomi MI5 more fascinating :silly::silly::silly::silly:
FingerPrint Wakeup resets after reboot
chiragkrishna said:
Enabling/Disabling the FingerPrint Wakeup
Source: github
Mod Location: /sys/devices/soc/soc:fpc_fpc1020/enable_wakeup
Code:
[B]Values:[/B]
1 = Enable
0 = Disable
Click to expand...
Click to collapse
@chiragkrishna, I tried flashing the zip to enable FingerPrint Wakeup but it did not work. So I updated the file as per the instructions. I guess that's because the zip file has nothing inside the system folder. It works but the value is reset to 0 after reboot. Any permanent solutions?
Update:
Although I tried the hard way by using Init.d script to reset the value to 1 at every boot, it didn't work.
Then I tried using Tasker to set the value, it worked perfectly.
But then I found a video with an easier solution using Kernel Adiutor.
Here's the Youtube link: Tutorial How to Set Xiaomi Mi5 Fingerprint Always On
Another tweak I found to wake your Lenovo Vibe K5 Plus simply by double tapping the screen.
To activate this:
1. You must have rooted phone.
2. File manager with root access.
Method:
1. Go to root/sys/ANDROID_TOUCH.
2. Open doubletap2wake with any text editor.
3. Change the value "0" to "2".
4. Save.
5. Restart your phone.
6. Done
Hit "Thanks" if worked.
Ok thanks I will try it today evening
Sent from my Redmi Note 4 using Tapatalk
Nikish21 said:
Ok thanks I will try it today evening
Sent from my Redmi Note 4 using Tapatalk
Click to expand...
Click to collapse
Best of luck. :good:
Would it work with los stock kernel?
impulsar said:
Would it work with los stock kernel?
Click to expand...
Click to collapse
No idea. I am using vegito kernel v7
riazul.islam20 said:
No idea. I am using vegito kernel v7
Click to expand...
Click to collapse
Vegito kernel by default supports dt2w right?
impulsar said:
Vegito kernel by default supports dt2w right?
Click to expand...
Click to collapse
Might be. But by default it was inactivated.
Is it possible to add screen of gestures in lenovo vibe k5
Is it possible to lock device by double taping...Just like dt2wake??
jometzz said:
Is it possible to lock device by double taping...Just like dt2wake??
Click to expand...
Click to collapse
Why not?
Just double tap on statue bar
riazul.islam20 said:
Another tweak I found to wake your Lenovo Vibe K5 Plus simply by double tapping the screen.
To activate this:
1. You must have rooted phone.
2. File manager with root access.
Method:
1. Go to root/sys/ANDROID_TOUCH.
2. Open doubletap2wake with any text editor.
3. Change the value "0" to "2".
4. Save.
5. Restart your phone.
6. Done
Hit "Thanks" if worked.
Click to expand...
Click to collapse
It gets reset to 0 on reboot. Why?
afzalsayed96 said:
It gets reset to 0 on reboot. Why?
Click to expand...
Click to collapse
Because why not, but I found a solution.
Init.d support is needed. Probably on every custom rom this feature is working out of the box, but there is an easy way to get it on rooted stock.
How to get Init.d working? Follow this guide https://forum.xda-developers.com/showthread.php?t=1933849.
Download attached "enable_doubletouch2w.zip"(yep I f*** the filename ), extract it anywhere, copy extracted file to your phone internal storage (e.g sdcard).
Now, copy/move (whatever) it to the /etc/init.d., set correct permissions (same as other scripts in the directory) and voila. I used Root Explorer Classic.
So, on every reboot script will run and change value from 0 to 2 in /sys/ANDROID_TOUCH/doubletap2wake
Script itself:
#!/system/bin/sh
echo 2 > /sys/android_touch/doubletap2wake
Click to expand...
Click to collapse
Android_touch
There is no ANDROID_TOUCH folder.
I use pixel experience (8.1.0) ROM, 3.10.108 kernel(came with the ROM), solid explorer that you use.
Please help me!!
Goutham47 said:
There is no ANDROID_TOUCH folder.
I use pixel experience (8.1.0) ROM, 3.10.108 kernel(came with the ROM), solid explorer that you use.
Please help me!!
Click to expand...
Click to collapse
the same here, please help
Please someone who says the correct way to do the procedure in Rom AOSP or LineageOS in 7.1.2
Someone using dt2w on oreo? Please share info if there's a way to activate it under oreo
nonline said:
Because why not, but I found a solution.
Init.d support is needed. Probably on every custom rom this feature is working out of the box, but there is an easy way to get it on rooted stock.
How to get Init.d working? Follow this guide https://forum.xda-developers.com/showthread.php?t=1933849.
Download attached "enable_doubletouch2w.zip"(yep I f*** the filename ), extract it anywhere, copy extracted file to your phone internal storage (e.g sdcard).
Now, copy/move (whatever) it to the /etc/init.d., set correct permissions (same as other scripts in the directory) and voila. I used Root Explorer Classic.
So, on every reboot script will run and change value from 0 to 2 in /sys/ANDROID_TOUCH/doubletap2wake
Script itself:
Click to expand...
Click to collapse
bro...i m getting endless boot animation...what to do...??? plzz help