This module patches OPLongshot's code so that it produces PNG screenshots, as it should, instead of JPEG screenshots (ew!). It patches only the VDEX/ODEX files, which have no signature on them — only the APK is signed, which we do not modify, so OPLongshot still retains system signature privileges. The original APK is included to avoid version mismatches (although I don't think there will be much issue even if it isn't includd).
Note that the OPLongshot was taken from the OnePlus 5T's system image. YMMV for other devices on OxygenOS (or even HydrogenOS?).
The current version uses the version of OPLongshot from OnePlus 5T OxygenOS 5.1.0/5.1.1 (same), with version 1.1.0.180328153957.6a699c8.
Remember to clear Dalvik/ART cache after installing this.
GitHub repository (also details of how the patch is done).
Download zip (temporary until the Magisk repo bot refreshes)
Hello, could you make a valid version for Nougat? Try yours but it does not work. You could also add the option of 9999 captured pages instead of 12 (do not do it). I saw several values to modify but it did not work ... if you want I'll give you the latest version of nougat. Thank you! @angelsel
PD: Here the apk (OPLongshot) https://mega.nz/#F!KY1gHR6A!taK5YsqI4pwOpe3ewrdAWg
Youtube_Ll0r3nt3 said:
Hello, could you make a valid version for Nougat? Try yours but it does not work. You could also add the option of 9999 captured pages instead of 12 (do not do it). I saw several values to modify but it did not work ... if you want I'll give you the latest version of nougat. Thank you! @angelsel
PD: Here the apk (OPLongshot) https://mega.nz/#F!KY1gHR6A!taK5YsqI4pwOpe3ewrdAWg
Click to expand...
Click to collapse
Could you run (on your device) `oatdump --oat-file=/system/app/OPLongshot/oat/arm64/OPLongshot.odex --export-dex-to=some/dir` and get the resulting DEX file?
angelsel said:
Could you run (on your device) `oatdump --oat-file=/system/app/OPLongshot/oat/arm64/OPLongshot.odex --export-dex-to=some/dir` and get the resulting DEX file?
Click to expand...
Click to collapse
Bro, the .odex file in the longshot folder that happens to you the mega, also throws me this:
Some output directory not found or symlink
Thanks!
Youtube_Ll0r3nt3 said:
Bro, the .odex file in the longshot folder that happens to you the mega, also throws me this:
Some output directory not found.
Thanks!
Click to expand...
Click to collapse
Eh? What's the exact error?
angelsel said:
Eh? What's the exact error?
Click to expand...
Click to collapse
https://ibb.co/k3UcJc
Youtube_Ll0r3nt3 said:
https://ibb.co/k3UcJc
Click to expand...
Click to collapse
Yeah, err, I didn't mean to type "some/dir" verbatim, but some path on the sdcard perhaps to export the dex to.
I guess just /sdcard will do.
angelsel said:
Yeah, err, I didn't mean to type "some/dir" verbatim, but some path on the sdcard perhaps to export the dex to.
I guess just /sdcard will do.
Click to expand...
Click to collapse
https://mega.nz/#!2U5mFSYL!i-EkFdHd5auzuY0hGUPC_ArW30MDDhQwct8gT-WLOMU
Thanks bro
Hello I tried on 5.0.4 but screenshot app crashes
This module works flawlessly on my OnePlus 5, in case anyone else wanted to try it on theirs.
Who at OnePlus decided JPGs should be used for screenshots? Gross.
Thanks!
does it work on android pie? Testing it on OnePlus 6 and it's not working. can't take screenshot anymore
Can anybody confirm if this Xposed module works on OnePlus 7T using Android 10, thanks.
---Edit---
Can confirm that it doesn't work on OnePlus 7T after attempting to flash w/ Magisk.
Related
Hi,
Previously, I would edit the build prop to change the DPI on my Nexus however with CM12 nightlies, it is annoying to have to edit it every day. I noticed in CyanDelta that there's an option to flash a zip after updating and I'm wondering whether or not there is (or if I could create) a zip that lowers the DPI.
Thanks!
p3ntyne said:
Hi,
Previously, I would edit the build prop to change the DPI on my Nexus however with CM12 nightlies, it is annoying to have to edit it every day. I noticed in CyanDelta that there's an option to flash a zip after updating and I'm wondering whether or not there is (or if I could create) a zip that lowers the DPI.
Thanks!
Click to expand...
Click to collapse
Extract the zip and edit build_prop.sh to your liking, the one default in this zip changes 480 to 470.
You could probably also use a backuptool/addon.d script instead of flashing a zip if your ROM supports it.
Edit: Reuploaded, forgot to save
Lethargy said:
Extract the zip and edit build_prop.sh to your liking, the one default in this zip changes 480 to 470.
You could probably also use a backuptool/addon.d script instead of flashing a zip if your ROM supports it.
Edit: Reuploaded, forgot to save
Click to expand...
Click to collapse
Thanks! I've just edited it to my preferred DPI and I'll see if it works with tomorrow's nightly! I'm just wondering what a backuptool/addon.d script is? Would it be easier to use even though the zip will automatically be flashed with the ROM update (through CyanDelta)?
EDIT: I just found an addon.d folder in the System directory. Can I just leave the '.sh' file in there?
p3ntyne said:
Thanks! I've just edited it to my preferred DPI and I'll see if it works with tomorrow's nightly! I'm just wondering what a backuptool/addon.d script is? Would it be easier to use even though the zip will automatically be flashed with the ROM update (through CyanDelta)?
EDIT: I just found an addon.d folder in the System directory. Can I just leave the '.sh' file in there?
Click to expand...
Click to collapse
Scripts in addon.d are executed during a ROM flash if your ROM supports it. It might work if you put the .sh in, try it.
Lethargy said:
Scripts in addon.d are executed during a ROM flash if your ROM supports it. It might work if you put the .sh in, try it.
Click to expand...
Click to collapse
I've just put the .sh file in the addon.d folder and I'll see if it works tomorrow.
Thanks for your help!
Lethargy said:
Scripts in addon.d are executed during a ROM flash if your ROM supports it. It might work if you put the .sh in, try it.
Click to expand...
Click to collapse
I just received today's update and unfortunately the addon.d method didn't work. Following that, I tried flashing the zip but TWRP says, 'E:Error executing updater binary in zip '/sdcard/Download/ro.sf.lcd_density.zip'
Do you know what this might be?
p3ntyne said:
I just received today's update and unfortunately the addon.d method didn't work. Following that, I tried flashing the zip but TWRP says, 'E:Error executing updater binary in zip '/sdcard/Download/ro.sf.lcd_density.zip'
Do you know what this might be?
Click to expand...
Click to collapse
Yeah redownloaded and noticed I missed a line.
Lethargy said:
Yeah redownloaded and noticed I missed a line.
Click to expand...
Click to collapse
Thanks! Before I save it, I just want to make sure it is the second number that I should change to my preferred dpi (it says 480 and 470).
p3ntyne said:
Thanks! Before I save it, I just want to make sure it is the second number that I should change to my preferred dpi (it says 480 and 470).
Click to expand...
Click to collapse
Yep
Lethargy said:
Yep
Click to expand...
Click to collapse
Awesome, thanks! Once again, I'll test it out tomorrow.
Hello guys. I found this annoying bug on CyanogenMod 12.1 based ROM, that the swipe feature on AOSP keyboard does not work. So I have made a flashable zip of few hundred KBs that allows you to use Swipe. You can flash it over any ROM (might work on older versions of android too) and it won't require any kind of wipe.
Requirements
Root
Custom Recovery
SwipeFix.zip - 464.4KiB
Do not mirror please.
How to use the mod?
Boot into custom recovery
Flash the zip
Reboot into system
profit
If you want to use the mod, give proper credits
Hey MZO
Thanks
IRRITATING bug indeed, I cannot believe this is not corrected in a nightly! (what is the actual solution please?)
I can report it works on the latest trltexx (SM-N910F, Note 4)
Thanks
beng
BenG7 said:
Hey MZO
Thanks
IRRITATING bug indeed, I cannot believe this is not corrected in a nightly! (what is the actual solution please?)
I can report it works on the latest trltexx (SM-N910F, Note 4)
Thanks
beng
Click to expand...
Click to collapse
Yeah, the actual solution is a missing library actually. It's not built in CM or any custom ROM, I'd include the lib in my builds tho.
Sent from my FIND7 using XDA Free mobile app
Thanks again MZO
What is the missing lib then, libjn_latinime.so?
I looked into it, and I read at some point that it had been renamed to libjn_latinimegoogle.so...
thanks
beng
2 Years later still Keyboard Swipe Problem
It's over 2 years now and this problem still appears.
I'm using an otherwise great custom ROM but the AOSP keyboard Gesture/Swipe function isn't working although it's shown.
I tried flashing this zip solution with TWRP 3.0 but the flash failed. Any ideas how to get this working? Should this zip solution still work?
Laugh2 said:
It's over 2 years now and this problem still appears.
I'm using an otherwise great custom ROM but the AOSP keyboard Gesture/Swipe function isn't working although it's shown.
I tried flashing this zip solution with TWRP 3.0 but the flash failed. Any ideas how to get this working? Should this zip solution still work?
Click to expand...
Click to collapse
Hi
I use the script but with lib64. And I can swype :good:
You have to create a lib64 folder and put the last version of the file. (Open a ROM file or gapps and take the last one)
And you have to edit the updater-script with lib64 folder.
musklor said:
Hi
I use the script but with lib64. And I can swype :good:
You have to create a lib64 folder and put the last version of the file. (Open a ROM file or gapps and take the last one)
And you have to edit the updater-script with lib64 folder.
Click to expand...
Click to collapse
Would the binary file still work? I am asking because it is 32 bit executable: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), statically linked, stripped but I am not sure how to get it for arm64. (I have a S7 btw, and the absence of swipe-typing is a big issue.)
aarem said:
Would the binary file still work? I am asking because it is 32 bit executable: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), statically linked, stripped but I am not sure how to get it for arm64. (I have a S7 btw, and the absence of swipe-typing is a big issue.)
Click to expand...
Click to collapse
You can use nanodroid with twrp
Hello There,
I downloaded official Oreo Pixel image in order to extract the LatinIME.apk file from it, but I can't open the img files with 7-Zip, I believe they must be encrypted or something...
Where can I find the Oreo ASOP keyboard ?
I'd like to install it on my Xperia XZ1 Compact (On Oreo as well), I can't live without it since Gingerbread !
how to unpack system.img on windows
how ro unpack system.img on linux
These are basically how you mount a system.img. They are actually a packed partition that you can mount.
And, as far as I know, pixel and nexus devices have Gboard as default keyboard which you can download from play store, not the LatinIME.apk. If you would like to find LatinIME I would suggest you to unpack a AOSP Oreo ROM.
I've been on the exact same page (the first one, regarding unpacking on Windows) before posting here, but the ext4 unpacker software does not seem to exist anymore. The sourceforge repository is empty...
I face so many roadblocks just to get this tiny LatinIME.apk file, it's now getting on my nerves !
Well, I managed to get it installing LeneageOS (Oreo) on some old phone that I have at home.
So I successfully transferred the LatinIME.apk to my XZ1 and installed it, but it forces closes when it should popup :crying:
Any idea ?
JackyJacks said:
Well, I managed to get it installing LeneageOS (Oreo) on some old phone that I have at home.
So I successfully transferred the LatinIME.apk to my XZ1 and installed it, but it forces closes when it should popup :crying:
Any idea ?
Click to expand...
Click to collapse
If you get a log, it will be easier to identify the problem.
My phone is not rooted, ho can I grab the log ?
JackyJacks said:
My phone is not rooted, ho can I grab the log ?
Click to expand...
Click to collapse
Tutorial on how to get log
You don't need to have a rooted phone to get logs.
I got ARCore version 1.1.180312063-180312063 running on my Oneplus 5T running lineagos 15.1. I haven't done too much testing other than running the Ikea place app and it worked but was a little buggy. The calibration files definitely need to be configured for our device and could be what is causing the bugs in the Ikea place app. For whatever reason after installing ARCore the libraries were not being copied over. To get around this the two folders arm and arm64, in lib.zip, need to be copied into the lib folder located at /data/app/com.google.ar.core-"somerandomnumbers"/lib, you will need root permission to copy them.
If anyone wants to point me in the right direction on correcting the focal distance and principal point I would appreciate it. If you want to experiment with fixing the calibration files yourself you can unzip the APK and replace the two relevant file in the the device_profile_database folder. The ones currently being used are just renamed copies of the Oneplus 5's calibration files.
TLR;
Steps to install:
1. Install the apk
2. Unzip lib.zip and copy arm and arm64 to the folder at /data/app/com.google.ar.core-"somerandomnumbers"/lib
You can get some of the "incompatible" AR apps using something like Yalp to download them.
Will work on stock?
I think so but you need to have root to install the libraries.
I already have had this working with gcam for a long time. There is a magisk module that automatically fixes the calibration.xml
se7ensde said:
I already have had this working with gcam for a long time. There is a magisk module that automatically fixes the calibration.xml
Click to expand...
Click to collapse
I must have missed it when I was looking. I'll check it out, thanks!
Justjusten said:
I got ARCore version 1.1.180312063-180312063 running on my Oneplus 5T running lineagos 15.1. I haven't done too much testing other than running the Ikea place app and it worked but was a little buggy. The calibration files definitely need to be configured for our device and could be what is causing the bugs in the Ikea place app. For whatever reason after installing ARCore the libraries were not being copied over. To get around this the two folders arm and arm64, in lib.zip, need to be copied into the lib folder located at /data/app/com.google.ar.core-"somerandomnumbers"/lib, you will need root permission to copy them.
If anyone wants to point me in the right direction on correcting the focal distance and principal point I would appreciate it. If you want to experiment with fixing the calibration files yourself you can unzip the APK and replace the two relevant file in the the device_profile_database folder. The ones currently being used are just renamed copies of the Oneplus 5's calibration files.
TLR;
Steps to install:
1. Install the apk
2. Unzip lib.zip and copy arm and arm64 to the folder at /data/app/com.google.ar.core-"somerandomnumbers"/lib
You can get some of the "incompatible" AR apps using something like Yalp to download them.
Click to expand...
Click to collapse
Works like charm. Thnx
se7ensde said:
I already have had this working with gcam for a long time. There is a magisk module that automatically fixes the calibration.xml
Click to expand...
Click to collapse
where to download the module file?
is there a similar solution available for ARcore 1.2 ?
OnePlus 5T now officially supported with ARCore 1.3
Just install from play store.
https://play.google.com/store/apps/details?id=com.google.ar.core
I made a mistake like https://forum.xda-developers.com/t/...a-sideload-zip-or-openrecoveryscript.3673284/
Edit: Original title
Would someones send me copies of "settings_global.xml" & "settings_secure.xml" in /data/system/users/0
What I have tried:
1; 2 xml files from #4 of this thread were replaced (not official), uselessly.
2; It looks like no dpi or resolution parameters in build.prop. If you know, please tell me the details.
3; I have done sideload official ota.zip and flashed factory.zip but kept data. NOT WORKS.
Questions:
1; As I haven't turn on USB debugging, I can't use some ADB commands or GUI ADB tools, so how can I turn on it?
2; Or some ways like I can flash a zip file in custom recovery?
3; I find there are many differences between Android in Pixel series and other brands' manufactures, so maybe a slove is effective on the others, but ineffective on Pixel phone.
Anyway, to edit some files without ADB authority or flash some modified zip are better ways for me.
please!
Or tell me where are these two files in offical ota .zip
Or a second way to solves this issue better, like flashing some zip package anyway
thank you!
OR，please tell me what code of "display_size_forced" in settings_global.xml, just as numbers in yellow box.
Xml file is opened by Notepad++，I understand a little about ASCII like NUL/ETX/STX,maybe I could edit it by myself.
CDShue said:
OR，please tell me what code of "display_size_forced" in settings_global.xml, just as numbers in yellow box.
Xml file is opened by Notepad++，I understand a little about ASCII like NUL/ETX/STX,maybe I could edit it by myself.
View attachment 5731893
Click to expand...
Click to collapse
Attached. Don't know if it makes a difference, but this is from LineageOS.
dcarvil said:
Attached. Don't know if it makes a difference, but this is from LineageOS.
Click to expand...
Click to collapse
Although I find the files you post are different from mine (especially the 'codes'), I replace these two files. Sadly It does not work. Many thx, anyway.
Why not simply sideload the OTA, or dirty flash the factory image?
CDShue said:
Xml file is opened by Notepad++
Click to expand...
Click to collapse
That's no XML file. It looks to be an SQLite database.
Settings in Android have been in an SQLite DB or in XML files in different Android versions.
V0latyle said:
V0latyle said:
Why not simply sideload the OTA, or dirty flash the factory image?
Click to expand...
Click to collapse
Maybe I have turned off USB debugging on my phone, then I followed this site https://stackoverflow.com/questions...evice-unauthorized-in-android-adb-host-device and got temporary adb authority. Sideload in TWRP failed.
Click to expand...
Click to collapse
Dirty flash the factory image did't work neither, if you mean the steps below:
Delete '-w' in 'flash-all.bat', save it, then open it.
V0latyle said:
Why not simply sideload the OTA, or dirty flash the factory image
Renate said:
That's no XML file. It looks to be an SQLite database.
Settings in Android have been in an SQLite DB or in XML files in different Android versions.
Click to expand...
Click to collapse
Thanks for your correction.
Click to expand...
Click to collapse
Renate said:
That's no XML file. It looks to be an SQLite database.
Settings in Android have been in an SQLite DB or in XML files in different Android versions.
Click to expand...
Click to collapse
Thanks for your correction.
Taps visual feedback, SO BIG!
( I photoshoped my fingers, )
If there's no other way to solve it, I'm considering to backup /data in TWRP, but there is no free space.
How to backup the whole /data to PC directly?