So Android Pay finally released and was super excited to get it running. Turns out you can't use it when your phone is rooted. Super pissed. Tried disabling root through developer options and still nothing.
Running the latest Euphoria ROM with the latest ElementalX kernel.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 6 using Tapatalk
I have known that for months. I can't use my banks app either.
Sent from my Nexus 6 using Tapatalk
People have reported it working when disabling root from supersu. Is that what you did?
XabdullahX said:
People have reported it working when disabling root from supersu. Is that what you did?
Click to expand...
Click to collapse
How do you disable root from super su? Also once it's disabled can it be re activated?
dalegg said:
I have known that for months. I can't use my banks app either.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
if you're using chainfire SU, then there is a checkbox in the settings menu.
those nexus 6 having issues with pay and root https://koz.io/inside-safetynet/
Found workaround
simms22 said:
those nexus 6 having issues with pay and root https://koz.io/inside-safetynet/
Click to expand...
Click to collapse
I found simplest workaround for making Android Pay verify your credit card....unroot by removing SuperSU with function to remove at bottom of the app. Then start PAY and allow it to verify whichever card you like. It should take you through a few steps and then instruct you that you need to type unlock pattern to use. Then just reinstall the SU zip from recovery (SuperSU246.zip or the current one you can get at chainfire website). I have not paid for anything just yet but assume it will work since the verification step is completed. If it fails, I will update later over the weekend.
Update: Yes you will need to be on stock ROM (it can be slightly modified with a few apps removed like EMAIL or bloat you do not use) but it cannot be a custom ROM like those in original android forum. That will fail. It uses some things within system partition that must be missing when you flash a custom rom. Maybe some hacker can help figure out what that is.
photolarry said:
I found simplest workaround for making Android Pay verify your credit card....unroot by removing SuperSU with function to remove at bottom of the app. Then start PAY and allow it to verify whichever card you like. It should take you through a few steps and then instruct you that you need to type unlock pattern to use. Then just reinstall the SU zip from recovery (SuperSU246.zip or the current one you can get at chainfire website). I have not paid for anything just yet but assume it will work since the verification step is completed. If it fails, I will update later over the weekend.
Update: Yes you will need to be on stock ROM (it can be slightly modified with a few apps removed like EMAIL or bloat you do not use) but it cannot be a custom ROM like those in original android forum. That will fail. It uses some things within system partition that must be missing when you flash a custom rom. Maybe some hacker can help figure out what that is.
Click to expand...
Click to collapse
i did get android pay installed, and did add a card, while on the m rom jdx. then i deleted my nfc(i always do that). but i never did test if it worked(my mistake). anyways, android pay got updated today.
Right...but it needs nfc to communicate with the terminal and the security thing is because it's directly connected now to bank
Fail for Google
I tested...it gave error...saying cannot use MasterCard xxx. The guy at register was nice enough to wait...I removed root and rebooted. It worked. Wtf...I cannot use crucial apps that I know help save battery life. My friend just told me to check Android xposed framework workaround
SuperSU unroot procedure works on stock ROM
photolarry said:
I found simplest workaround for making Android Pay verify your credit card....unroot by removing SuperSU with function to remove at bottom of the app. Then start PAY and allow it to verify whichever card you like. It should take you through a few steps and then instruct you that you need to type unlock pattern to use. Then just reinstall the SU zip from recovery (SuperSU246.zip or the current one you can get at chainfire website). I have not paid for anything just yet but assume it will work since the verification step is completed. If it fails, I will update later over the weekend.
Update: Yes you will need to be on stock ROM (it can be slightly modified with a few apps removed like EMAIL or bloat you do not use) but it cannot be a custom ROM like those in original android forum. That will fail. It uses some things within system partition that must be missing when you flash a custom rom. Maybe some hacker can help figure out what that is.
Click to expand...
Click to collapse
I can verify that this worked for me also. Added multiple cards before re-rooting and no complaints yet. Will try a McDonalds purchase later .. for research of course.
It failed at panera. I've tried doing rootcloak within xposed framework module and will see if I cab test for small purchase. Update soon. This is retarded that Google is paranoid I'll sue...my bank let's me use rooted...most of their apps are high encryption (192)....hello Google...do same thing!
---------- Post added at 08:18 PM ---------- Previous post was at 07:43 PM ----------
It failed for me but I've tried installing xposed and root cloak....adding pay and nfc and as many other apps I think it might be using under the cover. Hiding just Android pay didn't work...forgot nfc. I'll try at McDonald's in bit. This is so dumb. Why all the fuss with Google? I just dispute transactions if my phone got stolen. I'd obviously wipe it remotely. They do not think chit through!
photolarry said:
It failed at panera. I've tried doing rootcloak within xposed framework module and will see if I cab test for small purchase. Update soon. This is retarded that Google is paranoid I'll sue...my bank let's me use rooted...most of their apps are high encryption (192)....hello Google...do same thing!
---------- Post added at 08:18 PM ---------- Previous post was at 07:43 PM ----------
It failed for me but I've tried installing xposed and root cloak....adding pay and nfc and as many other apps I think it might be using under the cover. Hiding just Android pay didn't work...forgot nfc. I'll try at McDonald's in bit. This is so dumb. Why all the fuss with Google? I just dispute transactions if my phone got stolen. I'd obviously wipe it remotely. They do not think chit through!
Click to expand...
Click to collapse
actually, at this point, they did. you havent gotten it to work with root, have you? and i understand why they are doing it this way, its for the majorities safety, not if the minority can use it or not. anyways, we will have a way around it..
Most of majority do not know how to root....the woman in tech support...trained in this...had no idea what it even means nor did she have clue about some basic internal information. There should be way to use with root....I do not agree that they've considered us...developers that want root. Again let me repeat...banks use 192 bit high encryption...They should do the same. My device isn't all of a sudden horribly vulnerable just from root. Sorry but you are wrong.
Even if you manage to add it, won't work if you root again
laxamar said:
I can verify that this worked for me also. Added multiple cards before re-rooting and no complaints yet. Will try a McDonalds purchase later .. for research of course.
Click to expand...
Click to collapse
Tried to use at a McDonalds, with 2 different credit cards. Both failed saying can't be used at this time. I will unroot and try again to see if this is the issue
It fails with the attached message...and only way it works is if you go into super SU each time and disable...which I guess I could do...it's just one extra step
Well my old Google Wallet apk worked today at the grocery store I will be using that till a work around is found. At least if you want to use NFC payments you can for now.
Google doesn't ha e to consider rooters and modders for this. When Google speaks of developers, there are two types in their mind...
Legit app developers.. And those who aren't... Guess which category a rooter belongs to? Everything Google has done up to this point security wise goes against rooting.
So what reason do they have to allow you, or anyone who roots their phone, usage to a system that uses their servers?
Especially when they're constantly patching and erasing known root methods with every new version of Android..
photolarry said:
It fails with the attached message...and only way it works is if you go into super SU each time and disable...which I guess I could do...it's just one extra step
Click to expand...
Click to collapse
Do you mean un-checked the "Enable Superuser" checkbox? I'm using SuperSU Free v.2.45 by Chainfire.
Thank you!
Yes the checkbox in SuperSu ...as for whom they consider developer...that's really dumb. No I don't make applications but I'm an advanced user like most that own nexus. The fact they actually check for the su binary is idiotic. If that alone makes my device "vulnerable" then I would probably not use it at all. Also, the guy that's still using wallet, it will be forced on you soon. I attempted to reverse and it wouldn't allow me.
Related
This is something I have wanted to do since we figured out how to flash CWM Recovery, it just took me a while to get it working right.
This is not an AOSP Rom, so don't expect a lot, it's just a flashable package that adds some stuff that the Ouya is missing. This is based on the Ouya 264 r1 software.
Changes from stock:
-Added apks - Busybox, Dropbox (should include a free 50gb upgrade), ES File Explorer, Nova Launcher, Pandora, Google Play Music, Superuser, Titanium Backup, and Youtube for Google TV
-Removed Kernel and Recovery flash from the installer
Bugs I have run into:
-OTA updates will still download and install. This will be fixed before the first stable release.
Instructions (shamelessly stolen from mybook4):
-You need CWM Recovery installed to flash this
-Do a backup in CWM before flashing (seriously, you'll have something to go back to if things go awry)
-Wipe cache
-Wipe dalvik cache
-Data wipe is optional, and comes with it's own set of instructions
This is a beta ROM, and I have spent a few hours in testing, but nothing can be fully tested by one individual. It is a flash at your own risk ROM. Don't flash it if you are afraid to break something. Please provide me any feedback or suggestions you have.
I wanted to include Hulu Plus and Netflix, but they don't like being flashed, so I'll add easy download links later. so you can sideload them yourselves, I'm about to head to dinner.
If you do wipe data I recommend for ease of setup that when it asks you which launcher you want to use on first boot, choose Ouya launcher then "only once" and run through the initial setup till you're at the main Ouya launcher screen. then hold down the "Ouya" button in the middle of the controller to simulate the "home" key, and choose Nova Launcher and "always". Enjoy!!
https://dl.dropboxusercontent.com/u/7653846/OuyaPlusB6.zip
cool, if i actually manage to get CWM installed i may give this a try.
How much of a difference is there between this and ChickenStock?
It's similar in that it's a stock based ROM, but Chickenstock is meant to be disaster recovery, a solid base for rom building, or an easy flash to add superuser permissions to the console, but keep the focus on the Ouya experience. I designed Ouya Plus to be a quick flash for people who want to add some additional functionality to their Ouya, to make it do more than the limited minds that designed it intended. This is an Android console, and every media application you could ever want is available for android, so why should we be denied pandora or netflix, just because the Ouya people want to lock down their "console" to only allow things bought off of their store to work?
I wanted to make an easy way to add extra media functionality and system tools to the Ouya, without everyone having to track down and sideload the .apks themselves. I'm working on an easy way to install some of the other apks that i've been having issues with, and I also want to Deodex this rom so that custom themes can be applied, but I've run into trouble every time I've tried to use an automatic tool, so I'm going to try the last one I know of (xultimate) on it, and then I'll resign myself to deodexing each app manually and see what happens.
how exactly do you flash this to ouya?. I installed cwm recovery.
Once CWM is running, copy the zip to your internal storage, use adb or rom manager to reboot into recovery. The choose "install zip from sdcard", select the zip file from it's location, and it'll flash, then just reboot.
Installed and loving it , thx to the OP.
Sent from my Amazon Kindle Fire using xda app-developers app
Nice
Installed via CWM - all working well but controlling some of the apps is a nightmare!
I've got RomToolbox Pro installed and it makes roobooting easier. I also installed MX pro but I can't get any control at all!
sonofskywalker3 said:
Dropbox (should include a free 50gb upgrade)
Click to expand...
Click to collapse
That's cool but how is that possible? And is it 50gb for 2 years?
Sent from my GT-I9300
Probably the SGS3 version of the Dropbox APK or something similar. If it is, then it's version 1.0 of the Dropbox, so it doesn't do well with mobile authentication, but if you disable that for 5 minutes, the 2 year (24 month officially, I believe) upgrade is probably worth the relatively minimal security risk.
Thank you
I managed to install your ROM and so far I am enjoying it very much. I do want to let others know about my experience in dirty flashing this ROM. I wiped cache and Dalvik cache, but did not do a full wipe before flashing.
On the first boot i got a flood of force closures on the OUYA Launcher process. It almost made the system unusable as a new one came up as soon as i acknowledged the previous. After about a minute of this they started to ease up a bit and i could operate Android with around 1-2 force closes every minute. I went to settings->apps->All-> Ouya Launcher->Clear Data.
This immediately stopped the force close errors and the OUYA launcher still works.
Aside from this the only other observation i have is that the on screen pointer for my wireless mouse feels "smoother" than out of the box.
Ohh and thanks for the 50GB dropbox upgrade.
Okay, maybe i didn't notice at home last night because i was on Ethernet, but i took my OUYA to a different location with no Ethernet and realized that my wifi will not initialize.
http://pastebin.com/mt7V3zJj
This sounds great! I'll be sure to try it as soon as I get the balls up to install CWM on it. It's kinda been sitting there gathering dust at the moment as I haven't been that inspired.
Anyone flashes this while on the latest ouya fw?
Sent from my Amazon Kindle Fire using xda app-developers app
Ozz465 said:
Anyone flashes this while on the latest ouya fw?
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
I was on the newest one when i installed... 1.0.298-r1
sonofskywalker3 said:
I also want to Deodex this rom so that custom themes can be applied, but I've run into trouble every time I've tried to use an automatic tool, so I'm going to try the last one I know of (xultimate) on it, and then I'll resign myself to deodexing each app manually and see what happens.
Click to expand...
Click to collapse
Did you ever get a deodexing method working (I see ouyaplusb6.zip is still odexed... as is the 328 OTA), I was reading somewhere that an odexed rom causes issues porting, so I want to get my hands on a deodexed OTA to use as a base.
professorpoptart said:
Did you ever get a deodexing method working (I see ouyaplusb6.zip is still odexed... as is the 328 OTA), I was reading somewhere that an odexed rom causes issues porting, so I want to get my hands on a deodexed OTA to use as a base.
Click to expand...
Click to collapse
Working on it now... Hope to have it done this afternoon if anyone wants it.
Sorry guys, I've been pretty lazy on this front since getting back from my 2 week business trip, but I may get a chance to work on a new version tomorrow evening. MasterZen88 if you can get the latest OTA to deodex that would be awesome, and I'll update Ouya Plus to use it as the base, with your permission.
sonofskywalker3 said:
Sorry guys, I've been pretty lazy on this front since getting back from my 2 week business trip, but I may get a chance to work on a new version tomorrow evening. MasterZen88 if you can get the latest OTA to deodex that would be awesome, and I'll update Ouya Plus to use it as the base, with your permission.
Click to expand...
Click to collapse
Looks like you were right, each app will have to be manually deodexed. No worries. I've created a script to do this so hope to have it done soon.....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Already deodexed it just need to package it with my other bits of added features and I'm good to go for a release.
I was looking forward to trying this, but the wifi isn't initializing.
Ok, I downloaded 4.1.0.524.apk from the link below for my UK T800 running KitKat v4.4.2 and it worked, and knox is still valid.
Build Number KOT49H.T800XXU1ANFB
I am still on the stock rom, I have never flash my T800.
I tried the latest KingRoot a couple of weeks ago and it just failed, both apk and pc.
I have tried 3 root checks and they all say i have root.
http://androidxda.com/download-kingroot-application.
John.
EDIT : I just needed to install an SD Card Fix, All works great now.
Ok, I love File Manger HD Free, I have enabled root in the settings, I can delete files from my microsd, but i cannot delete a directory, I get the cannot message about v4.4 third-party apps not being ablet to do stuff.
So what is wrong.
Thanks.
John.
Tinderbox (UK) said:
Ok, I love File Manger HD Free, I have enabled root in the settings, I can delete files from my microsd, but i cannot delete a directory, I get the cannot message about v4.4 third-party apps not being ablet to do stuff.
So what is wrong.
Thanks.
John.
Click to expand...
Click to collapse
You need to download sdfix from play.
Yeah, I just beat you by 5 mins, I can delete a directory now
John.
ashyx said:
You need to download sdfix from play.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ok, when i go online the app on the right with the Chinese characters, translates as "Purification Master" according to google translate pops up with some message Is this just checking for updates, can i disable it.
I will need the app that pops up when it askes for root permissions is that kinguser, and the other is kingroot all three are running.
What can i remove or disable??
Thanks
John.
Delete it, it'll start bugging you. It's an app management app. Leave kinguser and delete everything else.
Why not convert to supersu?
Do i not need kingroot or is it`s job done? , So if i need to unistall root, I need kingroot or do i just install it from the apk i used to root in the first place.
I will have a look at supersu , is it a replacement for kinguser.
John.
Tinderbox (UK) said:
Do i not need kingroot or is it`s job done? , So if i need to unistall root, I need kingroot or do i just install it from the apk i used to root in the first place.
I will have a look at supersu , is it a replacement for kinguser.
John.
Click to expand...
Click to collapse
You don't need kingroot any more.
To replace kinguser you need to follow my rooting guide.
Should be easy for you you've already done half of it. Just install your original Rom if you want kitkat.
I dont want to do any flashing, I am happy with stock kitkat rom now that i am rooted.
I have done enough for today.
Thanks for your help.
John.
I am not interested in Lollipop, too many reports of problems and i dont like all of the white in the stock apps and settings crazy for an oled tablet, there is nothing new that i need now that i have rooted and can read/write to my microsd, I wonder if we will get Android M.
Look at the amount of power white uses compared to an lcd display.
I had my T800 running constantly for over 260 days, No restarts or shutdowns or crashes or anything, kitkat is totally stable at least the way i use it.
John.
Did lollipop get the battery charge and discharge time listed in the link below.
Android 5.0 Lollipop Changelog - What's new?
Android Lollipop 5.0 brings many new features which some smartphone users will definitely like. We have listed for you in this changelog the most interesting and important features of the new Android Lollipop 5.0 operating system.
Android Lollipop 5.0 Changelog:
- Material Design: The surface is optically flat and held more clearly structured, so that apps and applications can be better recognized
- SMS and WhatsApp messages can be read and answered directly from the lock screen
- If the Android Lollipop 5.0 Smartphone is charged, then the remaining time is displayed until it is fully charged
- Time until the phone runs out of battery power
- Multi-user mode, which is possible by a Google cloud. Advantage: You will be able to log in from any smartphone with Android Lollipop 5.0 in your personal profile.
- The Runtime ART, which is already known from the Samsung Galaxy S5 and Note 4, is standard. This will improve the performance
- OK Google voice command can now also be activated in the standby
Of course, Android Lollipop 5.0 has yet many more features and gimmicks. Hopefully you will receive this update as soon as possible for your smartphone.
Click to expand...
Click to collapse
http://www.solvemix.com/index.php/android-smartphones/166-android-5-0-lollipop-changelog-what-s-new
Tinderbox (UK) said:
Ok, I downloaded 4.1.0.524.apk from the link below for my UK T800 running KitKat v4.4.2 and it worked, and knox is still valid.
Build Number KOT49H.T800XXU1ANFB
I tried the latest KingRoot a couple of weeks ago and it just failed, both apk and pc.
I have tried 3 root checks and they all say i have root.
http://androidxda.com/download-kingroot-application.
John.
Click to expand...
Click to collapse
so you root your device without tripping knox?
Knox checker app says it`s still valid.
John.
alialexali said:
so you root your device without tripping knox?
Click to expand...
Click to collapse
So kingroot really does work on my T700 with Kitkat without tripping Know. BUT - I cannot get rid of it and replace it with SuperSU. Tried any method I found, but it simply seems to protect itself. Did anybody manage to replace the latest Kingroot installation with SuperSU? Any help is VERY MUCH appreciated!
Sorry if this sounds a litlle harsh, but what is it with you guys, do really not bother reading or searching the forum? It's a firm rule of XDA.
Right here in this very forum a few threads away: http://forum.xda-developers.com/gal...-to-root-tripping-knox-kitkat-t3129484/page16
ashyx said:
Sorry if this sounds a litlle harsh, but what is it with you guys, do really not bother reading or searching the forum? It's a firm rule of XDA.
Right here in this very forum a few threads away: http://forum.xda-developers.com/gal...-to-root-tripping-knox-kitkat-t3129484/page16
Click to expand...
Click to collapse
Ah, O.K. I will try the method to remove Kingroot, that is explained there and will propably stay with KitKat.
BUT - if I wanted to go to Lollipop with my SM-T700:
I do not understand this part:
Now we need to flash a Lollipop BOOTLOADER. I have provided a link below for the T800 and T805. If you have a T700/705/T807/T707 or if the ones provided don't work then you will have to extract it from the Lollipop stock ROM and then TAR it up.
Could anybody tell me a little bit more in detail how this is done?
liesenfeld said:
Ah, O.K. I will try the method to remove Kingroot, that is explained there and will propably stay with KitKat.
BUT - if I wanted to go to Lollipop with my SM-T700:
I do not understand this part:
Now we need to flash a Lollipop BOOTLOADER. I have provided a link below for the T800 and T805. If you have a T700/705/T807/T707 or if the ones provided don't work then you will have to extract it from the Lollipop stock ROM and then TAR it up.
Could anybody tell me a little bit more in detail how this is done?
Click to expand...
Click to collapse
I advise to read the rest of thread these questions have already been asked and answered.
NOTE TO OTHER MEMBERS: if someone provides me with the stock sboot.bin for the T700 or T705 I will add it to the op.
ashyx said:
I advise to read the rest of thread these questions have already been asked and answered.
NOTE TO OTHER MEMBERS: if someone provides me with the stock sboot.bin for the T700 or T705 I will add it to the op.
Click to expand...
Click to collapse
sent you a private message with Sboot.bin for the T700, KK and LL versions
Monster212 said:
sent you a private message with Sboot.bin for the T700, KK and LL versions
Click to expand...
Click to collapse
Thanks.
I'll just add the LL bootloader though. Kk not really needed and don't want to confuse people.
ashyx said:
Thanks.
I'll just add the LL bootloader though. Kk not really needed and don't want to confuse people.
Click to expand...
Click to collapse
welcomes... and got ya i was not sure what version you wanted so sent both..LOL
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community
Requirements:
- twrp 3.2.0+ with treble support https://forum.xda-developers.com/showpost.php?p=78708796&postcount=2
- backup everything before install including efs partition
- wipe cache and vendor partitions before install
Install:
- Flash zip in compatible TWRP
- Don't forget about gapps (arm 9.0)
Google apps should be installed via recovery immediately after installing ROM.
If you reboot into ROM before installing Google apps, you must factory reset and then install them, otherwise expect crashes.
Doesn't work:
RIL
Download:
0207 build
T710: https://drive.google.com/open?id=1VScAyyvr8WcAseGAFVmIM4DPd2-Q1Us6
T715: https://drive.google.com/open?id=1q7oHTyV_JJGG3B56h0Wd_QiUsKn6hVzg
Device sources:
https://github.com/bonuzzz
treble-enabled twrp
t710: https://drive.google.com/open?id=1d0YycDthOxo7IM1b5gZbNI7zCdlu2Cix
t715: https://drive.google.com/open?id=1wrZKDMQcosQRrZGDypIG27Oqv-zL6m2G
known issues:
info on data partition is not accessible
Hi, thank you for the build, awesome! I was going to install LOS 15 but now I'll go directly for this one. I'll tell you how it goes
Sent from my Aquaris M5 using Tapatalk
Hello bonuzzz thanks for your hard work, I think there is not a lot of change to do but can you make a lineage rom 16.0 for t810. Thank you in advance.
Hockron said:
Hello bonuzzz thanks for your hard work, I think there is not a lot of change to do but can you make a lineage rom 16.0 for t810. Thank you in advance.
Click to expand...
Click to collapse
Unfortunately it's not so simple. So no new builds for t810/t815 at least in near future (several months). I focus on t710/t715 only.
as usual gr8 job ma8 considering. We got los15.1 stable finally seeing this beta makes me really happy so, keep up the good work...
This project is suspended. Maybe temporarily, maybe not. I tried to estimate how much time I need to get it stable and to be honest I don't want to have deal with it. As I know few developers are already working on lineage16 since november. Maybe they will upload anything to public. What about me, I don't want to spend months and some day one dev just kang my work again. Thanks for understanding.
bonuzzz said:
This project is suspended. Maybe temporarily, maybe not. I tried to estimate how much time I need to get it stable and to be honest I don't want to have deal with it. As I know few developers are already working on lineage16 since november. Maybe they will upload anything to public. What about me, I don't want to spend months and some day one dev just kang my work again. Thanks for understanding.
Click to expand...
Click to collapse
Its very sad for everyone that you abandoned the rom, but I understand what not having the time and the energy means. Thank you very much for the build. In any case I installed as I said before.
I haven't tested it much but for the time being its running pretty smooth. I installed some apps and no crashes so far. Just an error message at boot saying something happened, after closing it everything OK.
I add some screenshots here.
Ill keep posting issues if I find any. Do you think I could compile your sources in my computer?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-T710 using Tapatalk
what to do when you are sick and staying at home? answer is simple:
new lineage16 builds are uploaded.
all hw stuff has been brought up except ril on t175, so no mobile network support yet. everything else should work.
links are in first post.
How much work should it be done to port this onto T810? And do you know anybody is doing it?
frankieboy1233 said:
How much work should it be done to port this onto T810? And do you know anybody is doing it?
Click to expand...
Click to collapse
not so much really but anyway it does
as I heard Ather was doing llineage16 with another dev. Maybe someone else.
T815 plzz. I have no knowledge about porting roms, but if by any way I can help u in porting this to T815 plzz let me know...
sweet, i saw your trebel twrp in the other forum, freaking fntastic
#1. Loaded trwp and ROM only no root
Excellent power 97 percent remain after 13 hours
No 5gz WiFi. But because I had nothing else loaded I couldn't see the nvram_net.txt settings.
So I tried to load pico and lineageos add-on su, and had several boot up and setup issues with the play services kept crashing. After bypassing lots of stuff, gave up and reloaded, I was able to see the root permissions in the developer settings, but lineageOS extras shows only arm 15.1 no 16 for root. Thought that was an issue. Silly me I didn't do a logcat. Before I did #2
#2nd try wipe , load, pico and magisk 17 . no magisk 17 in apps.
Did a bypass load apps to get to desktop. Had a couple " this device has errors, please contact manufacturer "
Play store was able to install apps, but I had no access to my paid apps. See #1 I wanted to fix my 5gz WiFi files. And I use es file explorer pro, but since I didn't have root... Well.
Play store recovered my programs am going to try magisk 18 . BRB
Looks nice, a couple of google play store bugs, an actuall desktop black out.
In conclusion, awesome ! Work !
Will fiddle some more. couldn't get a logcat
Downloaded all my gapps, and I found an unofficial root for lineageos 16 in another forum.
Trying again. Cheers
https://androidfilehost.com/?fid=11410963190603875495
issue with paid apps i think is more gapps issue rather than device specific because i have the same behavior on another devices and had to flash one image several times before got showing my purchases in play store
bonuzzz said:
not so much really but anyway it does
as I heard Ather was doing llineage16 with another dev. Maybe someone else.
Click to expand...
Click to collapse
i have an 815 to test as well
---------- Post added at 05:35 AM ---------- Previous post was at 05:17 AM ----------
bonuzzz said:
issue with paid apps i think is more gapps issue rather than device specific because i have the same behavior on another devices and had to flash one image several times before got showing my purchases in play store
Click to expand...
Click to collapse
Same here.
I got 5gz to work . I changed
Code:
ccode=US
regrev=69
Based on several posts over the years, I researched what regrev is in related to the ccode
It relates to what frequencies and I believe power outputs for different countries legal free and open radio frequencies.
The clues are in the driver for the wireless device source code.
Here is a broadcom driver for the 3.10 kernel
https://android.googlesource.com/ke...drivers/net/wireless/bcmdhd/dhd_custom_gpio.c
In there is a small database that should be consulted when you boot up your device and your country code should be selected when the driver is accessed
This has never worked properly for any lineageos based ROM.
Also most stock ROMs do not have this in their correctly.
All the files in /system/vendor/etc/wifi that have nvram in their name ( total 6 files ) need updated manually with an editor with root access.
As soon as I enter codes and reboot, I see all the 5 gz and many other networks that normally are too far away.
Kind of a chore to do this on every reloaded device, but that's what it takes.
Will this work on the 2015 model? I was able to flash it on my Tab S2 running exynos processor however it won't past the samsung logo.
Tried not flashing the gapps package to make sure that wasn't it... still stuck with recovery only. Any ideas?
samw52000 said:
Will this work on the 2015 model? I was able to flash it on my Tab S2 running exynos processor however it won't past the samsung logo.
Tried not flashing the gapps package to make sure that wasn't it... still stuck with recovery only. Any ideas?
Click to expand...
Click to collapse
Same here I cant flash Gapps with out it sticking on Samsung's boot logo
@samw52000 @legojoe8 read the first post carefully, in particular about twrp
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Google Pixel 3a XL
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 18.1 thread for the Google Pixel 3a XL.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
bonito
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
None.
Find any? Report them according to this guide.
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!
Kernel Source: https://github.com/LineageOS/android_kernel_google_msm-4.9
Going to try it now.
Thank you!
npjohnson said:
Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!
Click to expand...
Click to collapse
syntax error Are we talking about the Kernel being bundled?
ssurell said:
syntax error Are we talking about the Kernel being bundled?
Click to expand...
Click to collapse
What? No, firmware, like modem, bootloader, etc.
Question:
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
So are you saying if we root there is no support? As most of us coming from stock would at least need root temporarily to restore all our apps.
Can anyone confirm if root even works on this build. I woudnt see any reason not but would like to know cause of the above reason.
UPDATE: Decided to just go for it and everything is working great so far. Took a little work to get google apps working instead of the included aosp ones (phone calendar and contacts) and a bt more work to get it to pass safteynet but its all working 100% now. Also tested this build with both ex kernel and mvk and they both seem to work just fine as well. Will report back if anything changes as have only been running it.a few hours but so far no issues or complaints at all.
Great job LOS team
What is the official way to obtain root access? or is there one any more?
cliffordd said:
What is the official way to obtain root access? or is there one any more?
Click to expand...
Click to collapse
Based on the above statement i quoted sounds like root is not "officially" supported at all. That said to get root i followed the process by which you patch a boot image file with magisk manager. Making it pass safteynet net took additional steps.
If you need more details on either process just post back and i can be more detailed
adm1jtg said:
If you need more details on either process just post back and i can be more detailed
Click to expand...
Click to collapse
Yes please - maybe message me off thread, as this topic might not be appropriate on here.
I have Magisk app installed, due to using Titanium Backup to keep a backup of my app. The upgrade went great and everything is working fine under LOS 18.1. But I miss the ability to take backups and use certain features properly on the device (ie clipboard sharing and other features in KDE Connect, scheduling backups etc) There used to be a package provided by LOS to add or remove su - https://download.lineageos.org/extras but that seems to have stopped now. I was just wondering if there was an "official" way of doing it!
I actually held off upgrading due to the previous download being released on 1st April and not finding some previous April fools pranks to be very funny!!
cliffordd said:
Yes please - maybe message me off thread, as this topic might not be appropriate on here.
I have Magisk app installed, due to using Titanium Backup to keep a backup of my app. The upgrade went great and everything is working fine under LOS 18.1. But I miss the ability to take backups and use certain features properly on the device (ie clipboard sharing and other features in KDE Connect, scheduling backups etc) There used to be a package provided by LOS to add or remove su - https://download.lineageos.org/extras but that seems to have stopped now. I was just wondering if there was an "official" way of doing it!
I actually held off upgrading due to the previous download being released on 1st April and not finding some previous April fools pranks to be very funny!!
Click to expand...
Click to collapse
sent you a private
cliffordd said:
What is the official way to obtain root access? or is there one any more?
Click to expand...
Click to collapse
i flashed the version of Magisk (v21.4) via the LineageOS recovery using the adb sideload and just updated to v22 via the app. I haven't had any issues with root since installing.
First off, I want to say thank you for all the hard work on these builds.
I have came across one issue that isn't working for me, but might not be something everyone else uses a lot. My "squeeze" for Assistant isn't working, but I can change it to take a screenshot of any other option, except the Assistant. Am I doing something wrong or is there another settings need to activate for it to work?
Thanks!
Really want to try this, but can't "fastboot boot twrp.img" or "fastboot flash boot twrp.img" in Android 11 to backup my partitions. What's the point of Android OS if I can't backup my system? I can boot into Lineage OS Recovery, enable adb, figure out the partition names, dd the partitions from shell or pull with adb? But good grief, kinda ridiculous if you ask me.
Haven't been able to use twrp since Android 9 far as i know
lineage-18.1-20210401-nightly-bonito-signed.zip
Searching Settings aborts after a matter of seconds and while typing.
Derelict non-clearable notifications requiring reboot or force close.
Desk Clock stuck at "Loading".
The final LOS 17 seems more polished, but lingering notifications are still present requiring force close.
Nevermind, user error.
ssurell said:
lineage-18.1-20210401-nightly-bonito-signed.zip
Searching Settings aborts after a matter of seconds and while typing.
Derelict non-clearable notifications requiring reboot or force close.
Desk Clock stuck at "Loading".
The final LOS 17 seems more polished, but lingering notifications are still present requiring force close.
Click to expand...
Click to collapse
you're using opengapps - don't do that ;p
Use MindTheGapps, which doesn't break that feature.
npjohnson said:
you're using opengapps - don't do that ;p
Use MindTheGapps, which doesn't break that feature.
Click to expand...
Click to collapse
Actually, it's the first time I've used MindTheGapps. I used OpenGapps after falling back to 17.1 though since it is recommended on the LOS site. I kind of liked the Slim Gapps feel of MTG though, and might try it on 17.1
ssurell said:
Actually, it's the first time I've used MindTheGapps. I used OpenGapps after falling back to 17.1 though since it is recommended on the LOS site. I kind of liked the Slim Gapps feel of MTG though, and might try it on 17.1
Click to expand...
Click to collapse
weird - we don't have MTG builds for 17.1 though, sadly.
How do I disable encrypted device? Tried ElemntalX kernel and Disable_Dm-Verity_ForceEncrypt_quota.zip but phone is still encrypted under security settings after first boot.
When I see "Say Hello To Trust", I just want to punch it in the face. Somebody just needs to build an updated LOS 16 so we have TWRP and possible access to /data (formerly user space) and call it a day.
ssurell said:
How do I disable encrypted device? Tried ElemntalX kernel and Disable_Dm-Verity_ForceEncrypt_quota.zip but phone is still encrypted under security settings after first boot.
When I see "Say Hello To Trust", I just want to punch it in the face. Somebody just needs to build an updated LOS 16 so we have TWRP and possible access to /data (formerly user space) and call it a day.
Click to expand...
Click to collapse
Why do you want encryption disabled?
It's hardware backed, and FBE, so very little gain from running unencrypted...
"Trust" has nothing to do with encryption, it can be on, off, trust just reports it to the user.
Why do you want TWRP? Lineage Recovery does the job just fine. What do you mean "/data (formerly userspace)"? That statement doesn't make much sense.
Regardless of all the above, the disabel force encrypt zip, followed by `fastboot -w` to format userdata ought to do it - but be warned, if you set a PIN, Android (AOSP, not a lineage thing specifically) will re-encrypt you... hence there being no point.
Hi All,
This is a revival of the original MagiskHide Props Config module.
I've been working on this all day and its finally ready to start taking fingerprint submissions so i thought id open a new thread here to reach more people.
Disclaimers -
I have copied and pasted from the original thread with a few changes where relevant.
I fully intend on handing this back over to @Didgeridoohan if they ever decide to take the reign again. Im simply just stepping in to fill a much needed void in the custom rom space.
As with any Magisk Module. This comes with risk. You can very easily break your device. I myself have a Samsung Note 10 Plus so i will be testing on my own device prior to making any releases.
I have no intention of collecting donations at all. This project depends upon the community more then myself.
What's this?
If you are wondering anything about what this module can do and how it works or if you're experiencing issues of some kind, take a look at the documentation on GitHub and see if whatever you wonder about is covered there (most things are). If they're not, look again and then post in the thread.
If you're wondering about the latest and greatest after an update, take a look at the changelog and accompanying release notes.
Prerequisites
Magisk v20.4+.
Installation
Install through the Magisk Manager Downloads section. Or, download the zip (attached below) and install through the Magisk Manager -> Modules, or from recovery. Combine a recovery installation with the use of the module configuration file and you can set up a certified fingerprint and any custom props you want without first booting on a clean flash. Instant settings.
Usage
After installing and rebooting, run the command props in terminal (you can find a terminal emulator on F-Droid or in the Play Store), and then follow the instructions to set your desired options (also see the documentation on GitHub). You might have to call su before running the command.
You can also run the command with options. Use -h for details.
Submitting Fingerprints
Now this is where you lovely people come in. There is no way ill be able to spend all my time gathering fingerprints and i have absolutely no intention of doing so. However i've made it very easy to submit your fingerprints in a way that i can process them with very little effort.
How to find your fingerprint
Submit your Fingerprint
Source
GitLab - All scripts are completely opensource and your free to download it yourself directly from source
Download Repository
MHPC Releases & Archive
Support
Discord Invite Link - For the time being i will only be able to support users either on here and Discord.
Credits and mentions
There are lots of people to thank for this project. I've included the main two below
@topjohnwu, for Magisk
@Didgeridoohan, for creating MHPC and maintaining it for so long
Original Module Thread
Link to Original Thread
@vithuselservices You forgot to attach the module in your post.
devnoname120 said:
@vithuselservices You forgot to attach the module in your post.
Click to expand...
Click to collapse
Hi. There haven't been any official releases just yet. ETA for the first beta releases are the end of this week but that's only if everything goes well and I see no issues on my tests. So far there are only Experimental releases that i have stopped uploading to the release fileshare.
Once the new build is ready I can begin working on integrating new Fingerprints from the submissions that have been given to me.
@vithuselservices I tried the latest master, and I rebooted. If I type `props` in Termux it says `No command props found`. I have the same issue with the original module though.
Any ideas how to fix this issue?
Edit: typing `su` before solves the issue..
devnoname120 said:
@vithuselservices I tried the latest master, and I rebooted. If I type `props` in Termux it says `No command props found`. I have the same issue with the original module though.
Any ideas how to fix this issue?
Click to expand...
Click to collapse
type su first
I have a really weird question:
I have a poco f3 (europe) phone. I extracted the props from the phones original system (MIUI 13.0.8.0 EEA). I editet the original printlist in the original magisk module, added the
POCO/alioth_eea/alioth:12/SKQ1.211006.001/V13.0.8.0.SKHEUXM:user/release-keys__2022-08-01
line to it, Then flashed the modified zip, and applied the new prop settings. The YASNAC apps says it passes safetynet, and i can use all my banking app except google wallet, and there is no netflix in the ploay store. If I change the props to a value that was part of the original printlist
POCO/alioth_eea/alioth:11/RKQ1.200826.002/V12.5.3.0.RKHEUXM:user/release-keys__2021-06-01
the google wallet works and the netflix app shows itself in the play store.
Is it something that I missed from the prop values? I cannot understand this behavior.
Any advice?
Is this project still alive? I haven't seen any updates for a few weeks. Did OP just ghost us?
neelchauhan said:
Post has been removed by a Moderator
Click to expand...
Click to collapse
Hi.
This is not the case. Can you please remove this post as its highly inaccurate?
Im still here. Apologies for the lack of updates.
Ive had a lot of work come in so its delayed things somewhat but the final version is indeed ready.
Theres a final bit of testing to be conducted prior to making a official release as the last thing i want is bricked phones or settings being dropped.
The first beta release will be out by sunday.
In future can you please give more then 2 hours prior to making such a claim? Its considered rude to make such a claim without reaching out to a dev with sufficient time to reply. Your welcome to fork it yourself. Thats your right. But be more thoughtful when you spread messages like this
dickta said:
I have a really weird question:
I have a poco f3 (europe) phone. I extracted the props from the phones original system (MIUI 13.0.8.0 EEA). I editet the original printlist in the original magisk module, added the
POCO/alioth_eea/alioth:12/SKQ1.211006.001/V13.0.8.0.SKHEUXM:user/release-keys__2022-08-01
line to it, Then flashed the modified zip, and applied the new prop settings. The YASNAC apps says it passes safetynet, and i can use all my banking app except google wallet, and there is no netflix in the ploay store. If I change the props to a value that was part of the original printlist
POCO/alioth_eea/alioth:11/RKQ1.200826.002/V12.5.3.0.RKHEUXM:user/release-keys__2021-06-01
the google wallet works and the netflix app shows itself in the play store.
Is it something that I missed from the prop values? I cannot understand this behavior.
Any advice?
Click to expand...
Click to collapse
Hi.
I believe google is now blocking basic Attestation on newer firmware. This is something im looking into as part of my android 13 upgrade. Certain devices will work better then others. Im sorry i cannot give you a solid answer at the moment. But once im done with my current release and the fingerprints have been updated i can work on this issue. Its likely going to require device specific configurations as newer phones come out. Some people have had luck. but it seems android 12 is the turning point.
vithuselservices said:
Hi.
I believe google is now blocking basic Attestation on newer firmware. This is something im looking into as part of my android 13 upgrade. Certain devices will work better then others. Im sorry i cannot give you a solid answer at the moment. But once im done with my current release and the fingerprints have been updated i can work on this issue. Its likely going to require device specific configurations as newer phones come out. Some people have had luck. but it seems android 12 is the turning point.
Click to expand...
Click to collapse
I understand your point but I don't think its about luck. I did the same thing with my OnePlus 6. In the original prop module the the latest fingerprint is:
OnePlus/OnePlus6/OnePlus6:11/RKQ1.201217.002/2109171635:user/release-keys__2021-09-01
and with that all apps and wallet was working fine as intended, an netflix and revolut was present in the play store.
I also edited the original print.sh file and added the latest available fingerpint extracted from a latest full OTA rom which is this:
OnePlus/OnePlus6/OnePlus6:11/RKQ1.201217.002/2111252325:user/release-keys__2021-11-01
It also did the exact same behavior as on the Poco F3: YASNAC reports that the Basic Integrity and the CTS Profile match is "PASS", normal banking apps works (local banks like OTP, Erste etc. with NFC payment), but Google Wallet reports that the phone is modified and not certified. Play store also lacks netflix, put reports the device is certified.
The results are the same when I create a printlist file in the root directory in the phone to use my fingerptints as a "Custom" one.
It seems it only happens when I manually add the fingerprint myself, but never with the inbuilt fingerprints. That's why I think something is missing when I use "my" fingerprints. It also the same under android 11. Tested with a Redmi Note 5 Pro LineageOS.
I'm not a dev but if I can help, I'm sure I will.
dickta said:
I understand your point but I don't think its about luck. I did the same thing with my OnePlus 6. In the original prop module the the latest fingerprint is:
OnePlus/OnePlus6/OnePlus6:11/RKQ1.201217.002/2109171635:user/release-keys__2021-09-01
and with that all apps and wallet was working fine as intended, an netflix and revolut was present in the play store.
I also edited the original print.sh file and added the latest available fingerpint extracted from a latest full OTA rom which is this:
OnePlus/OnePlus6/OnePlus6:11/RKQ1.201217.002/2111252325:user/release-keys__2021-11-01
It also did the exact same behavior as on the Poco F3: YASNAC reports that the Basic Integrity and the CTS Profile match is "PASS", normal banking apps works (local banks like OTP, Erste etc. with NFC payment), but Google Wallet reports that the phone is modified and not certified. Play store also lacks netflix, put reports the device is certified.
The results are the same when I create a printlist file in the root directory in the phone to use my fingerptints as a "Custom" one.
It seems it only happens when I manually add the fingerprint myself, but never with the inbuilt fingerprints. That's why I think something is missing when I use "my" fingerprints. It also the same under android 11. Tested with a Redmi Note 5 Pro LineageOS.
I'm not a dev but if I can help, I'm sure I will.
Click to expand...
Click to collapse
How odd.
Ill raise that as a issue on my Git and have a look at it. It likely wont be this week but ill aim to do some testing on it next week. Are you certain the build date is correct?
vithuselservices said:
How odd.
Ill raise that as a issue on my Git and have a look at it. It likely wont be this week but ill aim to do some testing on it next week. Are you certain the build date is correct?
Click to expand...
Click to collapse
Absolutely! I own all the 3 phones , I also did a full stock rom recovery on all to run the getprop command to make sure the fingerprint and the patch date is correct.
Ohh and almost forgot: thank you!
Beta release is now available!
You can download it via the download repo in the first post. Please let me know if you come across issues. For this first release I do not recommend upgrading daily driver devices just yet as there could still be issues.
Not much has been changed in this release. I'm working on improving the verification process during the install process. I know a lot of people are keen to get fingerprints updated so ill be focusing on that over the next few weeks.
vithuselservices said:
Beta release is now available!
You can download it via the download repo in the first post. Please let me know if you come across issues. For this first release I do not recommend upgrading daily driver devices just yet as there could still be issues.
Not much has been changed in this release. I'm working on improving the verification process during the install process. I know a lot of people are keen to get fingerprints updated so ill be focusing on that over the next few weeks.
Click to expand...
Click to collapse
I tried it right now: the installation has a little problem: it says the installation is failed but it installs it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After that it seems the module can't access for some files and it not really working after that.
I attached a log to help.
dickta said:
I tried it right now: the installation has a little problem: it says the installation is failed but it installs it.
View attachment 5759567
After that it seems the module can't access for some files and it not really working after that.
View attachment 5759575
View attachment 5759571
I attached a log to help.
Click to expand...
Click to collapse
How odd. It works for me. Ill have a run through the logs and get it sorted. Thank you for reporting back!
vithuselservices said:
How odd. It works for me. Ill have a run through the logs and get it sorted. Thank you for reporting back!
Click to expand...
Click to collapse
Same for me. After assigning a fingerprint, reboot will clear it and it reverts back to original
This is still being looked into.
Its coming to the end of the year so im having to process a lot of projects to completion in my day job. Sorry for the delay!
New Beta Build is up. This should fix the install issues users have been having.
Ill be uploading a load of fingerprints very soon. Just finishing off testing the ones i have to hand.
For the moment. Android 13 support is very hit or miss. I'm working to find a solution to this.
A future update will need the deletion of the existing module so it can properly overwrite the new install files. This will also be completed with the next update.
The module now installs without problem, but in the app itself the behavior is the same: it not applies the selected fingerprint, always shows that "not accessible file" error in all activity. It's a good start, keep up the good work
dickta said:
The module now installs without problem, but in the app itself the behavior is the same: it not applies the selected fingerprint, always shows that "not accessible file" error in all activity. It's a good start, keep up the good work
Click to expand...
Click to collapse
Can you try uninstalling the original module and do a clean install of this one?
Im afraid i am not able to recreate the issue at all on my device which is quite infuriating