Related
is there a mod for CM12 5.0.2 on screen buttons? Please the home button is dead so I need on screen buttons and plus there look really cool lol
edit your /system/build.prop (use CM file manager), and add this line:
Code:
qemu.hw.mainkeys=0
that's it, reboot and you will have on-screen "navigation bar".
andrei53 said:
edit your /system/build.prop (use CM file manager), and add this line:
Code:
qemu.hw.mainkeys=0
that's it, reboot and you will have on-screen "navigation bar".
Click to expand...
Click to collapse
Doesn't work, always says denied
Edit: changed to r/w changed prop now nothing appears after s3 mini logo. Just blank screen
brooker88 said:
Doesn't work, always says denied
Click to expand...
Click to collapse
You need to use a text editor that supports root access mode.
Use CM's built-in File Manager and its editor. To enable root access, go to Settings -> General Settings -> Access Mode, and pick something other than "safe".
andrei53 said:
You need to use a text editor that supports root access mode.
Use CM's built-in File Manager and its editor. To enable root access, go to Settings -> General Settings -> Access Mode, and pick something other than "safe".
Click to expand...
Click to collapse
Will try in a min thanks, do you know how I disable hardware keys after this? I can't stop them from lighting up, bln app doesn't work either
Edit: it worked thanks so much! Been trying for hours to get on screen keys ����
brooker88 said:
Will try in a min thanks, do you know how I disable hardware keys after this? I can't stop them from lighting up, bln app doesn't work either
Edit: it worked thanks so much! Been trying for hours to get on screen keys ����
Click to expand...
Click to collapse
To disable hardware button backlight, Settings -> Buttons -> Backlight.
There you can also set Recents Button -> both long and short press -> no action
The only thing not possible to disable currently is the back button.
andrei53 said:
To disable hardware button backlight, Settings -> Buttons -> Backlight.
There you can also set Recents Button -> both long and short press -> no action
The only thing not possible to disable currently is the back button.
Click to expand...
Click to collapse
I tried that already, and the bln app but still lights up. Guess its cause I'm using f kernel.thanks for all your help
My brand new 3T just arrived and I see it's already encrypting it's contents.
The only point is that I don't know the encryption key.
I would like to unencrypted and re-crypt with my very password.
Any hint or suggestion on how to do it?
Tia.
[UPDATE] There seems to be no unencrypt option in the settings!
Hi,
When u configure your phone for the first time, configuration ask u to set your fingerprint reader and, for this, u have to enter a password... This password is your encryption password too... So, wipe your phone to factory default or try to configure your fingerprint reader, but in that way, i don't know if it will work...
Cheerz
Sent from my OnePlus3T using XDA Labs
I didn't put any fingerprint nor pin nor sequence.
Decrypting the device is available only by running the format data from fastboot or recovery twrp, encryption works from the phone settings
Sent from my Darkside of Oneplus 3T
OK. So, I how can I use my very own encryption password?
Uqbar said:
My brand new 3T just arrived and I see it's already encrypting it's contents.
The only point is that I don't know the encryption key.
I would like to unencrypted and re-crypt with my very password.
Any hint or suggestion on how to do it?
Tia.
[UPDATE] There seems to be no unencrypt option in the settings!
Click to expand...
Click to collapse
I also had that moment.. ; . It was solvable without changing much. I had been on fingerprint & pin entry from locked screen. I could get into TWRP because it wouldn't accept my PIN as password. I tried to change the PIN to a password, then rebooted and TWRP let me in with that password, worked fine, so I tested backup & restore.
The next boot, I changed the password back to my PIN, and from then on TWRP used my PIN for entry. Apparently their system needs a kick of some sort to rewrite the encryption header. Mine was encrypted throughout and I left it that way.
I am on stock system. No TWRP, no supersu.
Uqbar said:
I am on stock system. No TWRP, no supersu.
Click to expand...
Click to collapse
Doesn't matter, same way. Try to configure your fingerprint reader... Configuration will ask you to set in first a password or pin code or diagram...
Easy way to do it imao...
Sent from my OnePlus3T using XDA Labs
satanas17 said:
Doesn't matter, same way. Try to configure your fingerprint reader... Configuration will ask you to set in first a password or pin code or diagram...
Easy way to do it imao...
Click to expand...
Click to collapse
It didn't work like that.
The encryption was effective since the very first boot, according to the "Security" sub menu.
Then I configured a fingerprint and no PIN or password was asked.
Uqbar said:
It didn't work like that.
The encryption was effective since the very first boot, according to the "Security" sub menu.
Then I configured a fingerprint and no PIN or password was asked.
Click to expand...
Click to collapse
So your phone differently booted up first time then my...
Yes, encryption is effective immediately, and again imao, it's a great thing.
Have you tried to go in "security" to set a password?
Sent from my OnePlus3T using XDA Labs
satanas17 said:
So your phone differently booted up first time then my...
Yes, encryption is effective immediately, and again imao, it's a great thing.
Have you tried to go in "security" to set a password?
Click to expand...
Click to collapse
First, there's no such a thing like "set password" or "set encryption password".
There's only, in the very bottom of the menu, a "Encrypt the telephone" menu item. The current value is "Encrypted".
There's nothing else and neither tapping, nor long tapping nor double tapping gives any option.
It's just an informative item.
When my phone booted for the first time it took about one minute before giving me the home screen.
Then I skipped all the questions (GMail, etc.) in order to go to the firmware update.
Once rebooted in the updated version, I walked though all the menus (I am coming from 6+ years with CM) and found
that the storage was being already encrypted by default.
Then I configured my gmail account, updated all the apps and then added a fingerprint.
But still no PIN nor any password has been asked to me.
I am not arguing about encryption itself.
I am trying to gain control over it with my very own encryption key.
@Uqbar
Android is encrpted by default with a default password named "default_password". When you set a PIN or password for your lockscreen, you have an option to use this pin/password for device startup and the encryption is "active". This means android is now asking for password/PIN. When you only use the PIN/Password for your lockscreen, android never ask for it when the device starts. Without defining a password/PIN android uses the default password and no startuplockscreen is shown. That's the reason why android is telling you your phone is encrypted.
If you want to use a password different to the Lockscreen, you can set your own encryption password by using the "Cryptfs Password" app fom Playstore, but Oneplus has changed something on this and the app will not work at the moment. The app says that my currrent password is wrong, when i try to change it. There seems no way at this time, I guess.
* I hope my text was understandable, because english is not my native language *
This is an old thread, I know, but I just used it to find the answer to a similar problem. OxygenOS gives the option to use the PIN for startup. If you select that option the password will be required to boot into both the main system and recovery. To get there, in OxygenOS 5.0+ at least, go into the Security menu, select Screen Lock, and then the PIN option. This will give you a menu that enables requiring the PIN to start the device. Do that and your future boots will be protected by the same PIN you choose for screen unlock.
Must Be on Nougat Rom!!!
I recommend Starting on freshly wiped rom but. This requires Package Disabler Pro Be Installed.
PlayStoreNougatMods.zip
Extract zip
Enable Usb Debugging
Disable Verify apps over USB
Enable all disabled apps
Plug phone into computer watch phone screen accept usb debugging key for computer
Run Install_PlayStore_Rom.bat
Follow Instruction On Cmd Screen
Once Install Is All Done
Select Pixel For Home Launcher
Open Settings/Application/Default Application under Calling Select Phone
Open Language and Input
Open Virtual Keyboards and click manage keyboards and turn on GBoard keyboard
Open Developer Options
Set Window Animation scale to .05x
Set Transition Animation scale to .05x
Set Animation Duration scale to .05x
Open settings goto accessibility
Enable all the servicesexcept talkback unless you want it
In settings open applications
Open applications manager
Goto menu select speciall access
In Phone Administrators enable all except android device manager unless you want that
Now click back button and open Draw over other apps and enable all
Click back button and open Modify system settings enable all
Click back button and open Notification access enable all
Open Rom Control and Everything Installed will be accessed there
Features
Pixel Dialer V8 With working Video Calling
Pixel Contacts
Google Camera
AOSP Browser
Google Messenger
Google Clock
Google Calculator
Call Recording Via BoldBeast
Rom Control Mods
DNS66 Ad Blocking
Status Bar Mod
Torchlight With Volume Buttons
Access To IMS Settings And Advanced Calling
Keylight Duration Settings
Battery Bar +
Status Bar Internet Speed
Recent Bar In Notification Panel
Button Remapping Via AIO Gestures
Volume Button Music Skip
Fingerprint Gesters
Led Control Via Light Flow App
Volume Panel Mod
View attachment 4048810View attachment 4048811View attachment 4048812View attachment 4048813View attachment 4048820View attachment 4048821
Will this work on the nougat stock beta ROM? Since that's the only option for Verizon users at this point for nougat? Also do we have to root? It's under my assumption that there isn't root yet available for the stock nougat for Verizon... Looks awesome and excited to try this out and what options are soon to come for Verizon users because of this. Gives me hope for a nougat stock experience for Verizon s7 Edge users! Thanks again
Sent from my SM-G935V using Tapatalk
jonesj198 said:
Will this work on the nougat stock beta ROM? Since that's the only option for Verizon users at this point for nougat? Also do we have to root? It's under my assumption that there isn't root yet available for the stock nougat for Verizon... Looks awesome and excited to try this out and what options are soon to come for Verizon users because of this. Gives me hope for a nougat stock experience for Verizon s7 Edge users! Thanks again
Sent from my SM-G935V using Tapatalk
Click to expand...
Click to collapse
Inquiring minds want to know
I guess you havent seen this thread https://forum.xda-developers.com/ve...din-stock-nougat-firmware-s7-edge-to-t3558313
It will work on stock beta 2 but I have the official tmobile nougat firmware working on our phones. Only thing that doesnt work is wifi calling and Visual Voice Mail but Volte and Video calling work. So you might want to look into that
Just tried this and it did not work. The xml script for package disabler didn't do anything and once it got to the part where the device should reboot, it never did. Please help or advise?
Sent from my SM-G935V using Tapatalk
jonesj198 said:
Just tried this and it did not work. The xml script for package disabler didn't do anything and once it got to the part where the device should reboot, it never did. Please help or advise?
Click to expand...
Click to collapse
Did you accept the adb key when prompted did it install anything
Here is the package disabler pro import script. You can also just istall all of the apks manually if you have to
View attachment PlayStore.zip
I was never prompted to install an adb key... When does that happen? I click on the .Bat file, it finds my device. Then start following prompts
Sent from my SM-G935V using Tapatalk
jonesj198 said:
I was never prompted to install an adb key... When does that happen? I click on the .Bat file, it finds my device. Then start following prompts
Click to expand...
Click to collapse
When you first start bat file does it show device as unauthorized
jrkruse said:
When you first start bat file does it show device as unauthorized
Click to expand...
Click to collapse
No it shows three lines of text. One is the device ID I think, one says device is recognised, and then something else. Nothing about not being unauthorized, unavailable, not found or anything like that. It sees the device just fine.
Sent from my SM-G935V using Tapatalk
---------- Post added at 08:19 PM ---------- Previous post was at 08:18 PM ----------
It doesn't need root right? Can you possibly post screen shots of the setup steps so we can compare screens and I'll try to post images of mine as well. Thanks for the help id love to get this working and try it out. Installing all the apks one by one just doesn't seem to be the same as what the OP describes
Sent from my SM-G935V using Tapatalk
jonesj198 said:
No it shows three lines of text. One is the device ID I think, one says device is recognised, and then something else. Nothing about not being unauthorized, unavailable, not found or anything like that. It sees the device just fine.
Sent from my SM-G935V using Tapatalk
---------- Post added at 08:19 PM ---------- Previous post was at 08:18 PM ----------
It doesn't need root right? Can you possibly post screen shots of the setup steps so we can compare screens and I'll try to post images of mine as well. Thanks for the help id love to get this working and try it out. Installing all the apks one by one just doesn't seem to be the same as what the OP describes
Click to expand...
Click to collapse
Here if you dont have those numbers before device its not recognized
Is usb debugging enabled and verify apps over usb disabled
Did you accept debugging key. If this never came up. In developer settings click revoke usb debugging the unplug and replug your phone into computet. If the below screen still doesnt come up start the bat file then it will pop up. Accept key close bat then reopen and start process
jonesj198 said:
Installing all the apks one by one just doesn't seem to be the same as what the OP describes
Click to expand...
Click to collapse
Installing apps manually will work just fine. Then just copy the playstore.xml file from the zip of it I posted and import it with pacage disabler pro it should disable 126 packages
stud
Enabling any of the apps in accessibility says this error "*app* does not support the current system language. The text-to-speech language will be set to to null, but this might cause unexpected behavior. When i click turn on settings crashes and it doesn't enable.
CyanideHD said:
Enabling any of the apps in accessibility says this error "*app* does not support the current system language. The text-to-speech language will be set to to null, but this might cause unexpected behavior. When i click turn on settings crashes and it doesn't enable.
Click to expand...
Click to collapse
What build is your rom. Beta 2?
jrkruse said:
What build is your rom. Beta 2?
Click to expand...
Click to collapse
TMobile nougat.
CyanideHD said:
TMobile nougat.
Click to expand...
Click to collapse
If you have the rom control app open it under useful apps and open samsung info and tell me your csc version
Hi,
my Huawei P9 (EVA-L19, Android 6.0 / EMUI 4.1.1, root) is playing with me :/
With SIM #1 I have no access to the menu "caller id" in phone > settings > advanced/additional > caller ID (show my number / hide my number / operator default settings), because the menu is greyed out.
If I put the same SIM #1 in the other device (Samsung Galaxy S5, Android 4.4.2, root) I have access to this menu.
If I put a SIM #2 (other operator) in my P9, menu "caller id" is active.
And so:
P9 + SIM #1 = menu is not active / greyed out
SGS5 + SIM #1 = OK
P9 + SIM #2 = OK
SGS5 + SIM #2 = OK
There are no restrictions like CLIR on the SIM #1. I have tried everything (change the settings, make a call, save the settings, again change the cards between the devices) - no results...
I think, booth SIM-Cards are ok (not damaged), booth devices are working fine as well, so I would like to use some "magic codes" or find a new "hidden option" to activate this menu for the SIM #1, before I try factory reset and setup the device again...
Any ideas?
TIA
t.
PS
My P9 is a dual sim, but I use olny one SIM + SD-Card
Hello Good time
Can any one help me, any solution for VOLTE feature even it is enabled in the settings then also its doesn't work. The same sim's working with another device kt showing volte feature working, i'm unable to use the same
raajroop said:
Hello Good time
Can any one help me, any solution for VOLTE feature even it is enabled in the settings then also its doesn't work. The same sim's working with another device kt showing volte feature working, i'm unable to use the same
Click to expand...
Click to collapse
Hello , to enable VOLTE & VOWIFI , install logkit app here https://www.apkmirror.com/apk/onepl...ase/onepluslogkit-1-0-2-android-apk-download/ and dial *#800# > function switch > Volte, enable > Vowifi , Enable. Then reboot device . It will enable toggle in settings > network > volte , vowifi
Finally , you can uninstall logkit installed version in setting to restore to default version.
Anticolick said:
Hello , to enable VOLTE & VOWIFI , install logkit app here https://www.apkmirror.com/apk/onepl...ase/onepluslogkit-1-0-2-android-apk-download/ and dial *#800# > function switch > Volte, enable > Vowifi , Enable. Then reboot device . It will enable toggle in settings > network > volte , vowifi
Finally , you can uninstall logkit installed version in setting to restore to default version.
Click to expand...
Click to collapse
I was worried about the same thing, but when I tried this procedure, it seems that SIM ON / OFF was repeated immediately after restarting and it failed, but after about 5 minutes the VoLTE icon is displayed and communication and calls are possible. became.
Thank you!
Model:OnePlus Nord CE 5G Oxygen OS 11.0.1.1.EB13AA
SIM:KDDI(japan) LTE-FDD: B1/3/11/18/
afterwards...
When I put two SIM cards in and operated it, the "system" storage became full in one day, and I couldn't catch the radio waves, let alone normal operation.
When I checked from the settings, it was "system", so I couldn't delete the file, so I had no choice but to reset the terminal.
I couldn't find the ROM for "11.0.1.1.EB13AA", so I tried to activate VOLTE by flashing "11.0.3.3" or "11.0.9.9", but it doesn't work by any method. I could not do it.
The method I tried is the one above, or one that uses "magisk" or "PDC.exe".
JamboFE said:
The method I tried is the one above, or one that uses "magisk" or "PDC.exe".
Click to expand...
Click to collapse
so you propose no to use this logkit method? it causes system storage full?
Suncatcher16 said:
so you propose no to use this logkit method? it causes system storage full?
Click to expand...
Click to collapse
The only condition for VOLTE to be enabled with this logkit was that the OS version must be "Oxygen OS 11.0.1.1.EB13AA".
If the ROM version is 11.0.1.1, it may be enabled with this logkit.