Related
Android 4.2 keyboard with gesture, its as good as swipe.
http://m.pocketnow.com/2012/10/30/android-4-2-stock-keyboard-now-available-for-download-unofficially
After installing go to languages and input and check Android Key board
Hope it will be useful.
Download and Install
Now, getting it on your device is going to be easy for some of you, and less easy for others. You'll need to be on Android 4.0+, to start.
If you're on a phone with a UI overlay that has the stock keyboard disabled (eg, Samsung TouchWiz, HTC Sense, Sony), you can just download the apk below- no root required. To install, make sure you have "install from unknown sources" enabled in your phone settings, and after installation, go into your phone's keyboard settings and enable "Android keyboard." Then, you can switch to the new keyboard. This may also work on some "stock" Android custom ROMs - but it will not work on stock Android builds distributed by Google.
Get the apk here: http://d-h.st/XuS
If the apk doesn't work, you're running a phone that is either A.) running stock Android (as in, AOSP), or B.) running software that has the stock Android keyboard as an option, you'll need to download this ZIP file, and flash it in recovery. That also means you're going to need root. as you'll be writing to /system/apps. Before you do, though, either back up the stock keyboard (if you don't know how, you probably shouldn't be doing this) or create a full image backup, just in case. Here's that ZIP file:
Get the zip here: http://d-h.st/36D
Source: http://www.androidpolice.com/2012/1...d-4-2-keyboard-with-gesture-typing-right-now/
Android 4.2 camera
available now with photo sphere simply move to system apps and set permissions to rw-r-r- and reboot.some reports of photo sphere force closing but had no problems here
http://www.mediafire.com/?927d7dm454g435o
Here's the working zip, flash feom cwm
http://forum.xda-developers.com/showthread.php?p=33551677
Press thanks if u liked
YO YO CYRIN
I have scoured the internet and tried several solutions.
I'm on an AT&T HTC One currently running a 4.3 GPe ROM, and it's rooted, unlocked, and S-ON.
I'm trying to add on screen buttons like a nexus by adding qemu.hw.mainkeys=0 to the build prop.
I've tried ES File explorer, which flat out didn't do anything. I've mounted the system folder using the mount system rw/ro app, then edited it using Root Explorer and build.prop editor, which either immediately reverted to what was before, reverted after reboot, or caused the phone to reboot itself, also reverting the build.prop to what it was before. I've also tried this in MoDaCo Switch (currently my favorite) in both the Sense and GPe sides.
Am I missing something obvious?
Has anyone else tried anything like this or edited the HTC One build.prop in general?
Thanks!
Sent from my HTC One using xda app-developers app
The same problem
Also interested in this. Been trying different methods with no luck.
build.prop
Im trying to figure out the build.prop also. i know on past devices it was easy. im trying to enable my wifi hotspot on a Sprint HTC ONE. ill keep looking and let you know what i find.
Possible fix
I wanted to come back to this thread and let everyone know that it is now (Somewhat) possible to get the stock navbar to work in the Google Play Edition of the HTC One m7 rom. Here's what I did and remember, do this at your own risk:
1) Download either stock HTC One GPe rom or ARHD GPe rom (i did this on the ARHD rom)
2) Download either the stock GPe of the NEW HTC One M8 rom, or there is a port that is posted on the M7 thread called tiKtaK.
4) View the contents of the M7 rom and delete SystemUI.apk ==> /system/priv-app/SystemUI.apk
3) Take the SystemUI.apk file from inside the M8 rom and insert it into the M7 rom. I didn't extract the roms.zip files though, since i wasn't sure if that would prevent the rom from installing correctly. I'm using Ubuntu and the default compression manager allowed me to view the contents of the zip file and add / delete files without extracting them. I'm sure this is possible in windows or in mac.
5) Transfer newly modified rom to your device.
6) MAKE A NANDROID BACKUP (if you don't know what that is, please Google it before continuing... you have been warned)
7) Once you have a backup to fall back on if things go wrong, flash the new rom.
8) Aroma does its thing, and in my case as the installation finishes in aroma but then reboots and gets stuck in the Google logo. Not sure why, but it could be because of my version of TWRP. Who knows.
9) (Optional depending if your phones locks up in boot) I then hard reset my phone back into recovery (hold power for about 15seconds until the phone resets, and when you see the screen go black while still holding the power button, press and hold the volume down button and release the power button after 2 seconds. Select recovery in the menu and hit the power button to confirm). Once you are back in recovery, clear cache and dalvik and reboot.
10) Should be good to go. If not then restore back to your Nandroid, and I'm all out of ideas lol.
I'm fairly certain this wouldn't work if you took the systemui file from say an AOSP rom, or from CM rom, since the two files need to be almost identical. I just figured i'd give this a shot since the two files are probably very similar. And its working so far. No weird bugs or glitches. very pleased. I will update this if i run into any problems.
Another option you could try would be the M8 GPe port from tiKtaK. Its a solid rom with a few hiccups from what i've experienced. The camera will FC if you switch into Panorama or Photosphere, and the data connection can be a little quirky. Had to restart my phone to get it to reconnect on more than one occasion.
If you get this working and want to turn off the capacitive buttons, You can either download an app to turn off the backlight to them or if you're using gravitybox [kk] there is an option in the Display section to turn off the button backlight. If you want to prevent them from doing any actions, there is a file you need to delete the contents of... /system/usr/keylayout/synaptics-rmi-touchscreen.kl just use a file explorer with text editing capabilities and delete the text inside this file. Then save and reboot. g2g.
Hope this helps.
Remember, do this at your own risk.
After many try to enable nfc when screen off, I want to modifie the app (LgNfc.apk) to enable it, but some mistake in version or other parameters make it no working.
So I decide to copy my original app file to the system app, but after doing that and reanble all the permission on the file with ESExplorer my NFC still not working.
So I decide to demand your help!
Can someone upload the orinigal LgNfc.apk here cause mine still don't work.
I'm on an LG H815 and my version is an V10e-EUR-XX
Please help me to renable this great fonctionnality (and if someone of you have a moded file to enable NFC on screen off I was so happy)
nevvjeff said:
After many try to enable nfc when screen off, I want to modifie the app (LgNfc.apk) to enable it, but some mistake in version or other parameters make it no working.
So I decide to copy my original app file to the system app, but after doing that and reanble all the permission on the file with ESExplorer my NFC still not working.
So I decide to demand your help!
Can someone upload the orinigal LgNfc.apk here cause mine still don't work.
I'm on an LG H815 and my version is an V10e-EUR-XX
Please help me to renable this great fonctionnality (and if someone of you have a moded file to enable NFC on screen off I was so happy)
Click to expand...
Click to collapse
You could check if any of these steps fix it
step 1 clear cache of the app
step 2 reboot after you change it
step 3 double check permissions
step 4 clear app cache (again)
if all else fails:
make a backup of your apps/data, reflash your rooted stock rom (it should keep your apps intact, but just in case it's always nice to have a backup)
But you probably already tried all of these
Thanks for the reply.
But I can't find LgNfc in app list, only NfcSetting.
After reset cache for this and check permission, I reboot my phone but no more here nfc can't be enable....
So I think I must to reflash a rooted rom. But I don't have TRWP installed, can you point me the best option to use it??
Finally I Reinstall mt LG G4 to have the NFC fonction back.....
Many configuration to reinstall but finally have a LG G4 back to life.
Feel free to add if you have any mod or hack on G1600. :angel:
Starting with Volume boost. If you are not satisfied with the speaker volume output on your "Samsung Galaxy Folder 2 SM-G1600", download the attached "Volume Boost" mod and install through twrp. Don't forgot to Wipe Dalvik Cache before rebooting back to system. Volume increase Guaranteed . Even you may want to decrease the volume a bit after applying this mod.
I am using ZCU1APK1 . Rooted and supersu installed. Following xposed version working fine with it.
https://www.androidfilehost.com/?fid=529152257862685344
Enable Google Assistant on Your SM-G1600
Open Settings --> Applications --> Application Manager, choose Google and clear Google app data. Then Install CCSWE App Manager ( Root ) from Playstore. Open the app and search for Google app, press on Google Assistant and press show icon. Now go back to the home screen and search for the Google Assistant and launch it finish the setup and it should work with long press home, you can also hide the icon after it works.
Does the volume boost only adresses to the speaker? Or to the headphones too?
lucky58 said:
Does the volume boost only adresses to the speaker? Or to the headphones too?
Click to expand...
Click to collapse
Headphone too. But, I would suggest to install V4A and DAP to get best output from headphone. And present volume settings I posted, is quite annoying !! I think it is too high. So, before trying it , take a backup of your existing mixer file.
I will be updating this thread with a complete stock based deodexed, zipaligned, bloatware free ( as much I can ) - and tweaked ROM to give better battery and speed. I think I can make the volume better in my ROM with new settings.
New ROM published as promised. Please check following thread
https://forum.xda-developers.com/ge...-optimized-eng-rom-samsung-folder-2-t36282551
I'm having issues with Google Assistant. Every time I enable it, it disappears again. I also can't get it to work with the long press of the home button (keeps going to Now on Tap).
What's going on? I tried resetting the Google App and Google Play Services (delete all data)
And I also made sure my language was set to English (US)
Exact same thing happening with me. So, now concentrated on ROM. 1st stock based ROM released with bloatware removed and mostly in english. You may try to flash OpenGapp Aroma based installer to enable Google assistant when flashing the ROM, though I already added ro.opa.eligible_device=true in build.prop, but still having issue to make it work with OpenGApp nano. Not yet tried the AROMA version which is having the function to enable Google Assistant on your ROM. Feel free to research a bit and share your output.
Another problem, this is regarding Google Now and the Pixel Launcher
Have you tried moving the Pixel launcher to /system/app or /system/priv-app ?
Every time I try to convert to a system app it disappears.
What am I doing wrong?
---------- Post added at 08:30 PM ---------- Previous post was at 07:31 PM ----------
I fixed the Pixel Launcher on my stock rom (rooted with magisk)
1. install as a regular app > adb install
2. Use a file explorer or adb to move the entire directory of the pixel launcher to /system/app
3. rename the folder to base (since the name of the apk is actually base.apk
4. Set permissions. You will need to change the APK permissions, folder permissions, and also the permissions for OAT and the folder inside of it.
5. Reboot
6. Go to applications, show system applications, and find the pixel launcher
7. Hit disable, it will prompt you to restore factory version.
8. Re-enable
9. Done! Select default apps, home screen, pixel launcher
10. Swipe left for google now
Still haven't figured out assistant. I await your response on that.
i added in /system/priv-app
Hello. I need verry urgently rom with goole services and all tweakes enabled. I have some problems with accesibility, talkback dosn't turned n, and shine plus screen reader started, but turned f, after few minutes on standby shine plus has stopped woking. Also, when i turned of phone, and tured on again, shine plus osn+'t start, and i must find sited person, for enabling screen reader... T's verry frustrate.
I created a stock based ROM for G1600. Please check my other thread. Though you need to install gapps after flashing it.
bidhata said:
I created a stock based ROM for G1600. Please check my other thread. Though you need to install gapps after flashing it.
Click to expand...
Click to collapse
hi sir,
i couldn' find the other trend with rom for G1600, was it deleted? wher to install gapps? thanks if you could help.
bidhata said:
I created a stock based ROM for G1600. Please check my other thread. Though you need to install gapps after flashing it.
Click to expand...
Click to collapse
Link gives 404, you took it down?
Reuploaded. Please check .
How to root samsung galaxy folder 2 sm-g1600 marsmello 6.0.1 thank you
i dont really know where else to ask this, so im asking it here:
how to i connect headphones to it? will any 3.5mm to microusb adapter off ebay/aliexpress/whatever work?
and can type in swedish with it? does t9 work or am i stuck with multitap? can i type åäö? (important characters in the swedish language)
thanks in advance!
Hello friends!
I need a lot help.
If I fail to repair the operating system and work as before, I am impetuously interested in recovering at least the data on the /sdcard (internal phone storage) because I HAVE NO BACKUP and I need that data lke the air.
I have a Xiaomi Redmi Note 8 (Ginkgo) with stock ROM MIUI India/Global (11.0.6.0.PCOINXM), TWRP (3.3.1.0) and Magisk (v20.1 or 20.3 - I don't remember exactly).
About two days ago Revolut no longer allowed me to use the application because the phone is rooted. I needed to make an immediate transfer, so I started playing with Magisk because it didn't pass the SafetyNet test. Until then I had installed only Magisk, I updated to the latest version v21.2, I also installed two modules: MagiskHide Props Config (latest version) and Universal SafetyNet Fix v1.1.0. Plus the latest version of TWRP (3.5.0_9-0).
After running "props" in the terminal, I followed the steps (1, f, Xiaomi, 71 ...) and selected my phone from the list I managed to pass the SafetyNet test, but Revolut still did not work.
After that I tried to disguise the Magisk application with another name to hide it (that's how I saw it through some tutorials), but without success because I didn't activate install applications via USB (something like that).
I left the phone for about half an hour, and then the PROBLEMS BEGUN.
For each application I want to launch I receive the following message "wait until your device is fully rebooted before opening apps". I restarted the phone countless times and nothing. I noticed that TWRP does not decrypt user 0 or 999, so I changed TWRP to the previous version, uninstalled Magisk, deleted the modules from /data/adb/modules, upgraded to MIUI v11.0.6.0 and then MIUI v12.0.1.0 - and the problem persists.
I mention that using TWRP File Manager all the content from /data/data and /sdcard is encrypted (files and folders have unintelligible names). The rest of the files are ok.
Although developer mode is enabled, I don't have USB debugging enabled, and the default USB connection is set to charging and as I constantly get the error "wait until your device is fully rebooted before opening apps" I can't change them.
When I open the phone, at the lockscreen, I have a pattern that I successfully insert and the phone opens. The same pattern in TRWP does not decrypt the data.
Given the fact that it accepts the pattern password, I think that if I had a USB connection I would have managed to recover decrypted content from the internal storage space of the phone. Or is the error I receive exactly due to the fact that the applications no longer have access to the content because it is encrypted?
If so how can I recover all the encryption keys to backup them and then how can I try to fix this problem? Or if the keys have been altered, can they still be generated again (if the phone is the same, as well as the IMEI or serial number, etc)?
I understand that if I solve this problem I will either recover my phone as before or at least I can decrypt and access the data and make a backup.
It is very frustrating to see that the necessary information is still there, but I cannot access it.
Because I have access to the system with TWRP, I think I can attach logs.
I hope no one feels offended, but I am so desperate that I am willing to pay a reward.
Please help me!
Here is my video for a better understanding.
https://www.dropbox.com/s/ob235116jpnbj/ginkgo.mp4?dl=0
When I used MagiskHide, it changed my default.prop
Is it possible that the above problem is due to this fact?
How can I copy default.prop (original from wife's phone - same model) from SD card to phone?
Nothing changes with TWRP File Manager copy/paste. Can a script be used to be flashed with TWRP?
Any prop changes that were made with MagiskHide or MagiskHide Props Config did not touch any of your actual prop files. Your default.prop (and any other prop files) are going to be exactly as they were before enabling MagiskHide or changing prop values with MagiskHide Props Config.
Magisk does these things systemlessly, which means it doesn't actually alter the files. This (default.prop) is not your issue... How did you come to the conclusion that Magisk had changed your prop file anyway?
Since you've uninstalled Magisk and the modules, and even updated your OS and the problem still persists it is unlikely that it's directly related to Magisk. I know very little of MIUI though, so I'll leave the rest of the troubleshooting to those that do.
Thanks for the help and for the reply!
Didgeridoohan said:
Any prop changes that were made with MagiskHide or MagiskHide Props Config did not touch any of your actual prop files. Your default.prop (and any other prop files) are going to be exactly as they were before enabling MagiskHide or changing prop values with MagiskHide Props Config.
Magisk does these things systemlessly, which means it doesn't actually alter the files. This (default.prop) is not your issue... How did you come to the conclusion that Magisk had changed your prop file anyway?
Since you've uninstalled Magisk and the modules, and even updated your OS and the problem still persists it is unlikely that it's directly related to Magisk. I know very little of MIUI though, so I'll leave the rest of the troubleshooting to those that do.
Click to expand...
Click to collapse
I see a difference between my file and my wife's, although the phones are identical and had the same version of the operating system.
Originel - ro.bootimage.build.fingerprint=xiaomi/ginkgo/ginkgo:9/PKQ1.190616.001/V11.0.2.0.PCOINXM:user/release-keys
Actual - ro.bootimage.build.fingerprint=Xiaomi/omni_ginkgo/ginkgo:16.1.0/PQ3B.190801.002/5:eng/test-keys
Maybe I'm wrong, I'm trying different options...
In the end, I'm only interested in being able to access the decrypted content from /data and /sdcard (the internal phone storage) to backup them. Later I will reinstall everything.
Please help me with some tips, ideas, what else can I do?
If I reinstall the same version of MIUI, TWRP and use the same pattern can I decrypt the data (If I finally manage to backup them).
I'm already trying without success for about 2 days, do you think there is any chance to recover the DATA and/or internal storage (most important)?
Or to transfer it encrypted and then set the same pattern and eventually restore the data after I format and reinstall everything?
If I reinstall the same version of MIUI, TWRP and use the same pattern can I decrypt the data?
Adi H. said:
I see a difference between my file and my wife's, although the phones are identical and had the same version of the operating system.
Originel - ro.bootimage.build.fingerprint=xiaomi/ginkgo/ginkgo:9/PKQ1.190616.001/V11.0.2.0.PCOINXM:user/release-keys
Actual - ro.bootimage.build.fingerprint=Xiaomi/omni_ginkgo/ginkgo:16.1.0/PQ3B.190801.002/5:eng/test-keys
Maybe I'm wrong, I'm trying different options...
In the end, I'm only interested in being able to access the decrypted content from /data and /sdcard (the internal phone storage) to backup them. Later I will reinstall everything.
Please help me with some tips, ideas, what else can I do?
Click to expand...
Click to collapse
That fingerprint wasn't set by Magisk... Looks to me like you've been running a third-party/custom ROM and then didn't do a clean install of MIUI when going from the custom ROM. If so, that's a very likely source of the issues. I'm just guessing wildly though...
Didgeridoohan said:
That fingerprint wasn't set by Magisk... Looks to me like you've been running a third-party/custom ROM and then didn't do a clean install of MIUI when going from the custom ROM. If so, that's a very likely source of the issues. I'm just guessing wildly though...
Click to expand...
Click to collapse
Until 14.01.2021 when Revolut no longer worked on rooted phones, I had the MIUI India 11.0.2.0 version installed. Nothing else. Later in trying to make it work I kept switching between various official versions 11.0.2.0 / 11.0.6.0 and 12.0.1.0, flashed thru TWRP or Mi Flash (with save user data method).
It worked perfectly until I made those settings described in the original post. The problem is elsewhere, I think.
Based on the information in the attached file are the system encryption keys generated based on software or hardware?
Because if is hardware, I still have a chance to recover something, but if it's software, the fact that I tried to switch between versions decreases my chances to recover something.
What do you think?
Didgeridoohan said:
That fingerprint wasn't set by Magisk... Looks to me like you've been running a third-party/custom ROM and then didn't do a clean install of MIUI when going from the custom ROM. If so, that's a very likely source of the issues. I'm just guessing wildly though...
Click to expand...
Click to collapse
After I upgraded to MIUI 12.0.1.0 with MiFlash now I can't downgrade to 11.0.2.0. In logs everything seems to be ok, but the phone don't boot entering in recovery.
Trying to flash any other custom ROM, do you thing may be a solution? Or I will make things worse?
How can I resolve this situation?
If the fingerprint is the problem of FBE decrypting, how to restore the correct prop.default file?
Is any recovery that allow me to edit this file like text?
I have a copy of original prop.default.
Hey, did u mange to find a workaround? Im having the same issue, so frustrating!