Related
the FolioMod thread is start to get rather big, and maybe its time for another one with Kernel and Tweaks for our Folio..
I suggest we write tweaks / Kernels and maybe apps here too?
Wiki pages available here and here
Other non-FolioMod , but folio100 threads General questions thread
I requested an admin to include a Folio sub-forum, let's see if they can help us.
I'm starting with a keyboard recomendation for every Tablet with 7-10 inches:
htt p://dl.dropbox.com/u/13094844/com.beansoft.keyboardplus-1.apk
hi,
i am on foliomod 1.2.
Correct the version Folio Widget 0.3.1.
how I run both the CPU and the best optimal parameters Please.
I am also on FolioMod 1.2.
Is there a possibility to include usbnet.ko-driver? I'd like to use a USB-Ethernet interface, but the kernel driver is missing on the Folio.
Where can I get the Kernel sources and the correct kernel configuration file to compile the module?
wineraser said:
Is there a possibility to include usbnet.ko-driver? I'd like to use a USB-Ethernet interface, but the kernel driver is missing on the Folio.
Where can I get the Kernel sources and the correct kernel configuration file to compile the module?
Click to expand...
Click to collapse
look in the WIKI as mentioned in FolioMod post #1 (now also added to this thread in post #1)
Hello from Italy!
I'm using original Toshiba rom, updated (for now
I'm trying to use the FolioWidget 0.3.1 but I cannot install it; if I rename it to .apk , my Folio100 says is not correct
If I leave as .zip, It starts ES File explorer...
How can I install it? thank you.
ps: SOLVED, probably the first time the zip was corrupted
Folio Accelerometer Fix - BETA
This is a first BETA version of the rotation/accelerometer fix for the Folio 100, tested on FolioMod 1.2 only.
Checked with these applications:
- Wave Blazer Lite
- Raging Thunder 2 Lite
- Abduction! 2
Known Issues:
- Compass is not working, i.E any Compass app or for example Google Sky Map does not point you in the correct direction.
Note, this is NOT an update zip, at the moment I have no SDCard to verify that the update works, therefore you must push the files manually onto the device. Or wait until someone provides an update zip for these files.
Installation instructions.
- unzip the attached zip file into any directory you like
- enter the bin directory, where you should find 2 files (framework.jar, libsurfacflingeR_client.so)
- verify that your device is connected by running adb devices from a command line
- Remount the system partion read/write by entering: adb remount
- push the framework.jar to the device: adb push framework.jar /system/framework/
- push the sufraceflinger library to the device: adb push libsurfaceflinger_client.so /system/lib/
- reboot the device
Make sure you make a backup from the original files, I wont be able to fix any issues until next week, as I am away from my PC, still as my Folio is with me I'll check the boards to see if any issues have come up.
For developers/dexter:
the zip also includes the files I've modified for the fix, these are based on the NVIDIA tree. I hope that all modified locations shoukld be marked with // XXX:
Installation instructions.
- unzip the attached zip file into any directory you like
- enter the bin directory, where you should find 2 files (framework.jar, libsurfacflingeR_client.so)
- verify that your device is connected by running adb devices from a command line
- Remount the system partion read/write by entering: adb remount
- push the framework.jar to the device: adb push framework.jar /system/framework/
- push the sufraceflinger library to the device: adb push libsurfaceflinger_client.so /system/lib/
- reboot the device
Any easier way to do this ???
this is done on the Toshiba Folio itself or from a computer?
How do i "verify that your device is connected by running adb devices from a command line" ?
Is there any software required to do this ?
Sorry for asking so many questions, really a noob here and really tempted to get my folio fixed. I am running on dexter's foliomod 1.2, so far it works great, but the accelerometer doesnt seem to work correctly. I've tried some games like ibeer, the orientation is totally out. Hope that this can be fixed.
Eugene
weeds2000 said:
Note, this is NOT an update zip, at the moment I have no SDCard to verify that the update works, therefore you must push the files manually onto the device. Or wait until someone provides an update zip for these files.
Installation instructions.
- unzip the attached zip file into any directory you like
- enter the bin directory, where you should find 2 files (framework.jar, libsurfacflingeR_client.so)
- verify that your device is connected by running adb devices from a command line
- Remount the system partion read/write by entering: adb remount
- push the framework.jar to the device: adb push framework.jar /system/framework/
- push the sufraceflinger library to the device: adb push libsurfaceflinger_client.so /system/lib/
- reboot the device
Click to expand...
Click to collapse
Here is the update.zip edition and rollback edition.
remember to rename files to update.zip and install via recovery.
Dexter_nlb said:
Here is the update.zip edition and rollback edition.
remember to rename files to update.zip and install via recovery.
Click to expand...
Click to collapse
it works great with asphalt 5!!!
still some issue, but not related, with white texture in games like assassins creed...
Dexter_nlb said:
Here is the update.zip edition and rollback edition.
remember to rename files to update.zip and install via recovery.
Click to expand...
Click to collapse
I tought compass needs GPS? (and we don't have a GPS chip?)
@killerbie
no, e compass is electroic magnetic sensor.. but also a accelerator chip here...
the hardware GPS is for sat position reception.
Do This update work on stock rom, too?
girello71 said:
Do This update work on stock rom, too?
Click to expand...
Click to collapse
i dont think installer works on stock recovery..
Hello
Tested in the FolioTNTMod and didn't start after the ecompass.zip, ecompass_rollback didn't solve, so had to resinstall, just advertising, don't know if generic or just my setup.
viaper said:
Hello
Tested in the FolioTNTMod and didn't start after the ecompass.zip, ecompass_rollback didn't solve, so had to resinstall, just advertising, don't know if generic or just my setup.
Click to expand...
Click to collapse
confirmed.
does not work with clean TNT. just flashes the bootlogo over and over.
i'll wait for fmod1.3 though
edit: i didn't have the patience
works great on 1.2
kepler1982 said:
edit: i didn't have the patience
works great on 1.2
Click to expand...
Click to collapse
been busy with other tasks, so the orientation is working with some new games now or simply handled like we got a portrait tablet?
It should handle things like a portrait device. The changes in surfaceflinger library do just that. Within the Sensormanager class sensor values are rotated back 90 degrees. The fix for compass could be as simple as not rotating the sensor values if the sensor type matches the compass sensor.
The fix does not work with TNT mod because the framework jars are different (a plain Nvidia framework.jar does not work either) However it should be possible to add these changes to the tnt framework.
weeds2000 said:
It should handle things like a portrait device. The changes in surfaceflinger library do just that. Within the Sensormanager class sensor values are rotated back 90 degrees. The fix for compass could be as simple as not rotating the sensor values if the sensor type matches the compass sensor.
Click to expand...
Click to collapse
i tested it with the 3D Tilt game, it works (not perfect but close).
and im including your changes into the v1.3 FolioMod im preparing now..
a quick test of Asphalt also shows its working fine...
its worth including for sure..
as long as we got full 360 rotation, it works great..
ps: Tnt does not have full 360 rotation, nvidia edition got it with my my patched framework..
3G USB modem support possible ?
The ZT180 has support for 3G USB modem (Huawei make).
Assuming there is no hardware support in that machine I would speculate that
what is needed is,
a) A driver for the kernel
b) Changes to the framwork (?)
c) An app to handle it (AT commands probably).
Anyone have input on this ?
My phone so far:
SM-A320FL with the current stock Android 8.0 DBT. Flashed with Odin3.
Magisk 18.1 thx topjohnwu
[*]Xposed 90 beta 3 thx rovo89
Xposed systemless over Magisk module "Xposed Framework"
TWRP 3.2.3 for SM-A320 thx McFy
First of all I am not able to make a backup within TWRP. Seems to be a problem of Magisk.
I also encountered the following problem which I found a solution for:
After every reboot all of the paired Bluetooth devices are lost. I had to pair them again. Pretty annoying, especially the pairing with my car.
After searching around I found the solution within a Xposed thread, which I adapted to my phone.
There are two ways to solve this problem.
You lose all of your saved Wifi passwords and you need to pair all Bluetooth devices again.
First Method:
Go into Magisk and look for the module:
libsecure_storage companion for rooted Samsung devices
Follow the instructions that are given with the module. It works fine with my SM-A320FL.
Second Method:
First of all you need ROOT access and a root explorer (e.g. ES File Explorer) on your phone. You also lose all of your saved Wifi passwords.
Every time you do something on your phone make a BACKUP
Download the file at the bottom
Extract the Zip file to your hard drive
Copy the extracted system folder to your SD card
Copy the four files (2x libsecure_storage.so and 2x libsecure_storage_jni.so) within the subfolders (lib and lib64) to their respectable positions. The folders lib and lib64 are found in the systems folder on your phone. I didn't need to override any files.
Add the following line at the bottom of the build.prop file (system folder):
Code:
ro.securestorage.support=false
Reboot
Now the paired Bluetooth devices should stay paired.
I had to delete all Wifi connections and enter the password again to get them going. That's because the Wifi passwords are stored encrypted.
simple_s said:
My phone so far:
SM-A320FL with the current stock Android 8.0 DBT rom. Flashed with Odin3.
Magisk 16.4 thx topjohnwu
Xposed 90 beta 3 thx rovo89
TWRP 3.2.1 for SM-A320 thx McFy
First of all I am not able to make a backup within TWRP. Seems to be a problem of Magisk.
I also encountered the following problem which I found a solution for:
After every reboot all of the paired Bluetooth devices are lost. I had to pair them again. Pretty annoying, especially the pairing with my car.
After searching around I found the solution within a Xposed thread, which I adapted to my phone.
To solve the problem I did the following steps:
First of all you need ROOT access to your phone. You also lose all of your saved Wifi passwords.
Every time you do something on your phone make a BACKUP
Download the file at the bottom
Extract the Zip file to your hard drive
Copy the extracted system folder to your SD card
Copy the four files (2x libsecure_storage.so and 2x libsecure_storage_jni.so) within the subfolders (lib and lib64) to their respectable positions. The folders lib and lib64 are found in the systems folder on your phone. I didn't need to override any files.
Add the following line at the bottom of the build.prop file (system folder):
Code:
ro.securestorage.support=false
Reboot
Now the paired Bluetooth devices should stay paired.
I had to delete all Wifi connections and enter the password again to get them going. This is because the Wifi passwords are stored encrypted.
Click to expand...
Click to collapse
cool, i mean nice fix...working also on s9+
thx for this
Working here too!
Galaxy S9 with Magisk root.
Installed Xposed v90-beta3 yesterday, problem that BT connections were gone. Also WIFI passwords were incorrect. Not a problem that I had to re-enter WIFI passwords, but BT connections were gone each (re)boot.
This fixed the problem.
Thnx!
Deleted
Thanks works for my S9
Ok, I noticed that you said \system\lib and \system\lib64
And no overwrite is required because they don't exist...
That's because the files are actually in \system\vendor\lib and \system\vendor\lib64
The question is...
As you mentioned, no overwrite while on github says place them in their respective location... Which path is the right path...
I used Vendor, before I found this thread...
Because I simply searched for the file name...
Dante63 said:
Ok, I noticed that you said \system\lib and \system\lib64
And no overwrite is required because they don't exist...
That's because the files are actually in \system\vendor\lib and \system\vendor\lib64
The question is...
As you mentioned, no overwrite while on github says place them in their respective location... Which path is the right path...
I used Vendor, before I found this thread...
Because I simply searched for the file name...
Click to expand...
Click to collapse
I put the files in system / lib
And but pairing stays now
Alex-V said:
I put the files in system / lib
And but pairing stays now
Click to expand...
Click to collapse
Same, pairings stay for system vendor lib...
Maybe as long it's lib, doesn't matter which one ?
Deleting WIFI Passwords is not mandatory (at least for me). I had to reinstall Xposed and clear Cache (not Dalvik/ART) in order to get it working again. Without reinstalling Xposed and clearing cache the lib files got deleted every reboot.
Thanks.
For S7e with Oreo, beside forgetting paired devices on every bluetooth off/on, enabling bluetooth took noticeably longer time.
Placing libs in /system/lib and /system/lib64 did not work (build.prop edited, of course), placing them in /system/vendor/lib and /system/vendor/lib64 helped.
Is there a way to avoid replacing the files? On the xposed issue page (https://github.com/rovo89/Xposed/issues/294) ahronshor mentions backing up /data/system/secure_storage/com.android.bluetooth/, and then copying it back in place. Maybe that's the way to go, provided you are before rooting a freshly installed original firmware.
Another thing. I have flashed a new firmware (G935FXXS3ERKE), then flashed TWRP back even before rebooting. Then booted to TWRP and installed "remove encryption.zip", SuperSU and xposed, and finally booted the system (for the first time after update).
Bluetooth works now, on new firmware's original libraries and build.prop (btw, .so files are identical with previous G935FXXS3ERJ2, build.prop has just dates and versions changed). Off/on, restart - paired devices stay where they should, bluetooth enable time as usual.
Maybe the libsecure_storage.so patch (jnl was not modified at all) was to stop trying to read encrypted bluetooth data and to create an unencrypted container. It seems once the Bluetooth data file on /data is unencrypted, original code manages it correctly.
Thanks! Works on Note 9 Oreo 8.1
Reporting this solved my problems on J7 2017 with Oreo 8.1. Magisk 18 and Xposed. Thanks.
simple_s said:
First of all I am not able to make a backup within TWRP. Seems to be a problem of Magisk.
Click to expand...
Click to collapse
How did you solve the backup problem? I also can't make backup. It gives me some error.
The BT problem is solved. Note 9.
There is a magisk module that can do the trick without need to xposed.
Sent from my SM-N960F using Tapatalk
is there a way to fix the issue on stock 8.0 (last update december 2018 patch) without rooting?
It happens to me during last month...
thanks!
Ninolina said:
How did you solve the backup problem? I also can't make backup. It gives me some error.
The BT problem is solved. Note 9.
Click to expand...
Click to collapse
I couldn't solve it.
iltoffa said:
is there a way to fix the issue on stock 8.0 (last update december 2018 patch) without rooting?
It happens to me during last month...
thanks!
Click to expand...
Click to collapse
I don't think so.
I added new informations to the guide.
Apparently there is a Magisk module for some phones who does the same thing. You find it in Magisk under
libsecure_storage companion for rooted Samsung devices
It works perfect on my SM-A320FL.
My personal solution has been to remove IFTTT which was installed. From that, no disconnections found at all
I found a file called "PPPPStrand_xxx_Ricky" in my Internal Storage, anyone know what this is? It almost seems like a virus. I opened it as a text file and it seemed like a random string of alpha characters, there's a "VSTA" and "VSTB" in the string.
I tried Googling this but came up with nothing, thought maybe one of you devs would know what this is.
There is some consistency with this file however, it exists on my two Android devices:
1) Nvidia Shield K1 running LineageOS 14.1, Magisk, Adaway
2) Samsung Galaxy Note 4 - Verizon running MODest ROM, Magisk, Adaway
I found this file on both platforms, I thought maybe there's something common between the two?
Can anyone help me with this please...
For me , galaxy s5 the same. an my parner also the same file in root dir. Original rom. What is it?
Curious, do you use any IP cameras from Vstarcam? I use Vstarcam with their Eye4 software on my Android devices and Windows machines, and both Android devices had this file, I deleted the Eye4 software from my Android device, and the file still remained, I deleted the file, and the file never came back.
I installed the Eye4 software, no file, but after logging into my Eye4 profile to access my cams, the file came back. So the conclusion is that it's tied to the Vstarcam/Eye4 in some way...
Just to chime in, I also found that file on my phone and I also use Eye4. Has anyone tested it using Suneyes TS instead to see if this file also comes up? If not, I might switch back as they both are very compatible with each others cameras.
nuclear_bullet said:
Curious, do you use any IP cameras from Vstarcam?
Click to expand...
Click to collapse
Just to confirm that I do use Vstarcam's PNP VsCam and I do have that file.
I have the same...and i use StarCam.Olsow i have bitdefender full license and they tald me that this is not ,,a problem,, . S9 Samsung
Recently my trusty old box stopped finding streams in kodi. I suspect it's related to the expired DST Root CA X3 cert that no longer is usable since last week. Since this OTT box hasn't been updated in over 5 years I'm left with few options short of tossing it and starting over, BUT I'de like to try to get android functioning again instead of scrapping the hardware.
Soo...hoping someone could provide some insight how to safely add the new certs to the existing system store -OR- completely replace it. I'm semi-proficient with ADB and the device is rooted AFAIK.
Option #1 : add in the new certs. Per https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/ and https://letsencrypt.org/docs/certificate-compatibility/ I have installed the IdentiTrustCommercialRootCA onto the device (ISRG Root X1 I believe) but it installed as a personal cert, and I'm preparing to move it to the system store but I think theres an intermediate cert I need to install as well. I just don't know what it is, or where to find it.
Option #2 : add in the entire Mozilla cert package. http://wiki.cacert.org/FAQ/ImportRo...ect=ImportRootCert#Android_Phones_.26_Tablets has a nice walkthru and a cert package, but the docs get confusing when they explain how to import the two certs, and their download package has over 130 certs in it.
Option #3 : rebuild the entire system store from scratch. Googles github site has all the certs shipped with android 7, but I'm guessing I'll have install each one as a personal cert before moving each one to the system directory similarly to option 1.
Option #4 : REPLACE the entire cacerts.bks file from another android device via ADB. Is this SAFE ? https://forum.xda-developers.com/t/...h-kindle-app-just-stop-syncing.3205615/page-2
Anyone tried any of these, or any insight to any of these options ?
UPDATE : Worked option 1 last weekend, installed 5 certs- 2 from lets encrypt, 2 from identrust, and 1 I extracted from my browser. It was stupidly easy and without ADB since the box was rooted when I got it. Seems to have solved alot of issues, but how can I be sure the cert chain is intact and hashed properly ?
Hi there, could you please go into further details on this procedure on How you installed without replace the entire cacerts, or if you have found a better way.
I know a few friends with older devices and they could surely use my help as well I myself have an old Amlogic S812 device laying around which I wanted to put to some use. Thanks
ocd_amp said:
Hi there, could you please go into further details on this procedure on How you installed without replace the entire cacerts, or if you have found a better way.
I know a few friends with older devices and they could surely use my help as well I myself have an old Amlogic S812 device laying around which I wanted to put to some use. Thanks
Click to expand...
Click to collapse
My box came rooted, and it was required for the procedure I'm about to list here. I've inserted 5 new certs so far and havent seen any adverse effects, but I can say the SSL errors I was seeing in kodi logs no longer appear. I'm also still on android 5.1 so google isn't updating me. I wouldn't attempt this on a supported OS.
I've installed this one first : IdenTrust Commercial Root CA 1 from here : https://www.identrust.com/support/announcements
...also 3 from here : https://letsencrypt.org/certificates/
specifically ISRG Root X1 , Let’s Encrypt R3 , and the DST Root CA X3 ,
Get your certs in CRT format.
Now comes the FUN part :
Install certs normally (as user cert)- lockscreen method , as program certs.
I saw they were installed by looking at the user certs menu afterwards.
Start terminal program
type SU
mount -o rw,remount /system
The directory /data/misc/user/0/cacerts-added is where your user certs are stored. WRITE DOWN the filenames, you'll need them later. The names are now hashes of the actual certs
mv /data/misc/user/0/cacerts-added/FILENAME.0 /system/etc/security/cacerts/
This is where you actually move the certs into the OS folders. Use the 'hash names' you wrote down earlier, entered at the FILENAME.0 spot in the line above, for EACH file.
chmod 644 /system/etc/security/cacerts/FILENAME.0
As above, you'll need to chmod all the new certs.
You'll also need the chown root : root each new file as well.
mount -o ro,remount /system
Reboot
After reboot all your new certs should be system certs.
Hello everyone. As you might know, the global model doesn't come with GPS dual-band support, unlike the Chinese one. This is a completely arbitrary decision from Realme, since the hardware is the same.
I developed a way to enable the additional bands on the global model with a simple Magisk module. You can find the download link at the end, but first, some context.
How does it work?At each boot, it extracts the oplusstanvbk partition, patches it by changing the /nv/item_files/gps/cgps/me/gnss_multiband_configuration property, and saves it in the module's directory.
Then, a loop device pointing to the patched file is created and the symlink under /dev/block/bootdevice/by-name is changed to point to the patched block device instead of the original one.
The change is applied only to the current slot, so that you can install OTA updates without problems.
What if I don't want to install Magisk?You can manually patch the oplusstanvbk partition and flash it with fastboot. Of course you need an unlocked bootloader. You can find the gnss_patcher Windows executable on the GitHub page below, and if you're on Linux, you know how to compile. In the future I will add macOS support.
How to test if it works:Download the GPSTest app, go to a place with good reception, and see if L5/E5a/B2a satellites show up. If they don't, you can check the log file in the module's directory to see if something went wrong.
Changelog:v0.0.3:
Fix OTA updates with module enabled
Show module version in log
v0.0.2:
Attempt to fix triple-reboot issue
v0.0.1:
First release
Help needed:In theory, this should work on other OPPO/realme/OnePlus phones with Qualcomm Snapdragon processors and hardware support. If you test it on other models, please let me know about the results.
This module should also enable NavIC support, since it's available in the Chinese model, but I can't test it since I'm in Europe. If someone in or near India can see NavIC satellites show up, please let me know.
More info and download:The source code and download links are available on GitHub. The Magisk module is also provided as an attachment here.
If you find any problem with the module, please let me know.
For developers:In order to make this mod, I needed to investigate the NVBK file format. I then decided to write a library to manipulate NVBK images. You can find all the info about it on GitHub, but for now it's in a very early stage. I plan to add more functions in the future, as needed by me or others, since I'm developing a complete tool to manipulate NVBK images.
In any case, if you want to make a similar mod, please take a look at it.
I have a Chinese RMX3300 with global rom installed. The GPSTest app showed L1 and E1 satellites only. I installed your patch and now I see L5 and E5a satellites. To confirm, I uninstalled, tested and reinstalled the patch. I never flashed oplusstanvbk partition. Weird.
Anyways, excellent work!
i flashed it via magisk still l1 & e1
Quake94 said:
I have a Chinese RMX3300 with global rom installed. The GPSTest app showed L1 and E1 satellites only. I installed your patch and now I see L5 and E5a satellites. To confirm, I uninstalled, tested and reinstalled the patch. I never flashed oplusstanvbk partition. Weird.
Anyways, excellent work!
Click to expand...
Click to collapse
Even if you didn't originally flash the partition, it got updated with an OTA, probably.
vampire war said:
i flashed it via magisk still l1 & e1
Click to expand...
Click to collapse
Please post the log at `/data/adb/modules/RealmeGPSL5Enabler/post-fs-data.log`.
Slot: _a
lrwxrwxrwx 1 root root 15 Mar 14 20:54 /dev/block/bootdevice/by-name/oplusstanvbk_a -> /dev/block/sdf3
lrwxrwxrwx 1 root root 15 Mar 14 20:54 /dev/block/by-name/oplusstanvbk_a -> /dev/block/sdf3
Running patcher
Found RF_ID 0xFF: entry 0, size 0x2CE00, offset 0x400.
Found gnss_multiband_configuration at pos 0x43C.
gnss_multiband_configuration data match!
Success!!!
Created loop device /dev/block/loop36
context of /dev/block/loop36 changed to ubject_r:vendor_custom_ab_block_device:s0
'/dev/block/by-name/oplusstanvbk_a' -> '/dev/block/loop36'
'/dev/block/bootdevice/by-name/oplusstanvbk_a' -> '/dev/block/loop36'
lrwxrwxrwx 1 root root 17 Mar 14 20:55 /dev/block/bootdevice/by-name/oplusstanvbk_a -> /dev/block/loop36
lrwxrwxrwx 1 root root 17 Mar 14 20:55 /dev/block/by-name/oplusstanvbk_a -> /dev/block/loop36
Slot: _a
lrwxrwxrwx 1 root root 15 Mar 14 20:54 /dev/block/bootdevice/by-name/oplusstanvbk_a -> /dev/block/sdf3
lrwxrwxrwx 1 root root 15 Mar 14 20:54 /dev/block/by-name/oplusstanvbk_a -> /dev/block/sdf3
Running patcher
Found RF_ID 0xFF: entry 0, size 0x2CE00, offset 0x400.
Found gnss_multiband_configuration at pos 0x43C.
gnss_multiband_configuration data match!
Success!!!
Created loop device /dev/block/loop36
context of /dev/block/loop36 changed to ubject_r:vendor_custom_ab_block_device:s0
'/dev/block/by-name/oplusstanvbk_a' -> '/dev/block/loop36'
'/dev/block/bootdevice/by-name/oplusstanvbk_a' -> '/dev/block/loop36'
lrwxrwxrwx 1 root root 17 Mar 14 20:55 /dev/block/bootdevice/by-name/oplusstanvbk_a -> /dev/block/loop36
lrwxrwxrwx 1 root root 17 Mar 14 20:55 /dev/block/by-name/oplusstanvbk_a -> /dev/block/loop36
Click to expand...
Click to collapse
On restart, phone now only starts on the third try. The first two times it gets to pin code unlock before immediately restarting on its own. Can you confirm if this issue also happens on your device?
EDIT: Ok, this could've been caused by a bugged Shamiko 0.71 Magisk module rather than your patch. I installed the newest version 0.72, so far no issues.
vampire war said:
Slot: _a
lrwxrwxrwx 1 root root 15 Mar 14 20:54 /dev/block/bootdevice/by-name/oplusstanvbk_a -> /dev/block/sdf3
lrwxrwxrwx 1 root root 15 Mar 14 20:54 /dev/block/by-name/oplusstanvbk_a -> /dev/block/sdf3
Running patcher
Found RF_ID 0xFF: entry 0, size 0x2CE00, offset 0x400.
Found gnss_multiband_configuration at pos 0x43C.
gnss_multiband_configuration data match!
Success!!!
Created loop device /dev/block/loop36
context of /dev/block/loop36 changed to ubject_r:vendor_custom_ab_block_device:s0
'/dev/block/by-name/oplusstanvbk_a' -> '/dev/block/loop36'
'/dev/block/bootdevice/by-name/oplusstanvbk_a' -> '/dev/block/loop36'
lrwxrwxrwx 1 root root 17 Mar 14 20:55 /dev/block/bootdevice/by-name/oplusstanvbk_a -> /dev/block/loop36
lrwxrwxrwx 1 root root 17 Mar 14 20:55 /dev/block/by-name/oplusstanvbk_a -> /dev/block/loop36
Click to expand...
Click to collapse
What system version are you on?
Rapper_skull said:
What system version are you on?
Click to expand...
Click to collapse
Rmx3301_c18_ex01 13.0.500
this
vampire war said:
this
Click to expand...
Click to collapse
I have not updated yet because this version has some bugs. Are you sure you're in an area with good GPS reception?
hello realmi gt 2 pro android 13 c16 Eur update. I installed the magisk module and it works very well now there are L5 / E5a / B2a satellites. I don't know if I'm being exploited by the system? thank you for your excellent work
Quake94 said:
On restart, phone now only starts on the third try. The first two times it gets to pin code unlock before immediately restarting on its own. Can you confirm if this issue also happens on your device?
EDIT: Ok, this could've been caused by a bugged Shamiko 0.71 Magisk module rather than your patch. I installed the newest version 0.72, so far no issues.
Click to expand...
Click to collapse
Have the same issue with the double-reboot from the lockscreen code screen, not using Shamiko, only have LSPosed module installed (and GPS Enabler). Also on the same latest firmware (C18, INdia).
On 3rd reboot everything proceeds normally, and all satellite bands are shown in GPSTest.
Strange with the reboots, but it all works. Thankyou for this option!.
murakh said:
Have the same issue with the double-reboot from the lockscreen code screen, not using Shamiko, only have LSPosed module installed (and GPS Enabler). Also on the same latest firmware (C18, INdia).
On 3rd reboot everything proceeds normally, and all satellite bands are shown in GPSTest.
Strange with the reboots, but it all works. Thankyou for this option!.
Click to expand...
Click to collapse
Yeah, even with the updated Shamiko module I still have the issue. I also have the LSPosed module. Not sure if it's caused by LSPosed, the new OTA (EX01) or maybe the GPS mod. I didn't investigate it further.
murakh said:
Have the same issue with the double-reboot from the lockscreen code screen, not using Shamiko, only have LSPosed module installed (and GPS Enabler). Also on the same latest firmware (C18, INdia).
On 3rd reboot everything proceeds normally, and all satellite bands are shown in GPSTest.
Strange with the reboots, but it all works. Thankyou for this option!.
Click to expand...
Click to collapse
Quake94 said:
Yeah, even with the updated Shamiko module I still have the issue. I also have the LSPosed module. Not sure if it's caused by LSPosed, the new OTA (EX01) or maybe the GPS mod. I didn't investigate it further.
Click to expand...
Click to collapse
Do you get this problem at every reboot, or only after installing/updating a Magisk module?
Rapper_skull said:
Do you get this problem at every reboot, or only after installing/updating a Magisk module?
Click to expand...
Click to collapse
With minimal testing, it happens only when choosing "power off" from the restart option. Choosing "restart" does not result in the triple boot. Minor issue as in my use I do not reboot or power off often.
Only started after installing the GPS enabler module (from within Magisk), have not updated Magisk or any modules since then.
More out of curiosity, just uninstalled the GPS module (from within Magisk) and powered off for a few minutes. Rebooting was normal (went to lockscreen and did not reboot).
Edit: An additional thought - could this be a hardware issue? My hardware was (is) originally an RMX3300 (Chinese version, from China) and with the Chinese ROM all bands were active, later changed to the India ROM version and lost the additional bands.
Rapper_skull said:
Do you get this problem at every reboot, or only after installing/updating a Magisk module?
Click to expand...
Click to collapse
In my testing it is random. Typically immediately after the issue happens and phone boots on the third loop, if I restart again right away, it restarts on the first try. Contrary to what murakh said, in my case the issue happens both on power off and restart. Just like murakh, I have the rmx3300 chinese converted to global. I also haven't been screwing around with various regional ROM's. I only flashed to global (TW) once, then kept installing OTA updates.
Magisk 26.1
My list of Magisk modules:
Shamiko v0.7.2
SafetyNet Fix mod by Displax v2.4.0 mod v1.2
Zygisk LSPosed 1.8.6
Remove YouTube (by Ip)
Basic Call Recorder v1.44
And your GPS mod
I will try disabling the GPS mod and give it a couple days to see if the issue returns.
@murakh @Quake94 I managed to reproduce the issue only once on my device, but v0.0.2 should fix it. Please update from the Magisk app or download the new version from the first post and let me know.
Since a new update is rolling out, I released v0.0.3 that fixes the problem of OTA updates not installing when the module was active.
Rapper_skull said:
I managed to reproduce the issue only once on my device, but v0.0.2 should fix it. Please update from the Magisk app or download the new version from the first post and let me know.
Click to expand...
Click to collapse
Thankyou very much for looking into it, even though it was only a minor annoyance. Have not tried 0.03 yet, but can say that 2 reboots and 2 restarts on 0.0.2 and the multi-boot did not happen any time. All GPS bands detected.
Much appreciated.