Themes / Apps / Mods Assistant button remapper module (magisk/xposed) - Sony Xperia 1 III

I've created a very simple Magisk module to allow Xposed Edge to properly remap the Google Assistant button. You'll need Magisk and a Magisk-based Xposed implementation (I use LSPosed) for this to work.
Xposed Edge is the only remapping tool I've found so far that can properly detect the assistant button being pressed. The problem is, while you can assign it to an action using Xposed Edge, it will ALSO launch the assistant. What I've done is built a Magisk module that alters the gpio-keys.kl file in /vendor/usr/keylayout to change the keycode the system receives when the assistant button is pressed. Currently I've used PROG_BLUE, which is a keycode used in Android-powered smart TVs with programmable remote buttons.
To use, just download and use the "install from storage" option on the modules screen in Magisk. Once the module's installed and activated, reboot.
Once rebooted, you can open Xposed Edge, and under "Keys", tap "Add...". It will tell you to click the button you want to add, and if all goes well, you can press the assistant button and it will detect a press of PROG_BLUE. Then you'll be able to assign any Xposed Edge action or shortcut to it, and the assistant won't show up.
Usual disclaimers, works for me but not responsible if your phone blows up, etc.
Right now the module tested with the Xperia 1 III. If you own another device with a hardware assistant key and want to let me know what GPIO key number is associated with it (probably under /vendor/usr/keylayout, look for the number on the line with ASSIST), I might be able to expand it to other devices.
It's possible it may work in its current state for other Xperia devices, but there's a risk the changes to gpio-keys may mess up your other hardware buttons including power - so if you try it on, eg, an Xperia 5 III make sure you have another way to reboot if it breaks your power button and you need to uninstall the module!

Thank you for sharing! I recently bought this phone and i really like it!

Update: I figured out how to make it installable through Magisk Manager, new zip in first post.

you need root for this?

tardis_42 said:
Update: I figured out how to make it installable through Magisk Manager, new zip in first post.
Click to expand...
Click to collapse
Thanks for the fine works, I was able to remap the GA key successfully here!!!
Model: XQ-BC72
Build: 61.0.A.11.23
Just listing out things needed to be installed for your module to work.
Magisk module:
Riru
Riru - LSPosed
XperiaGAButtonRemap (install from storage .zip provided on this thread)
Google Play
Xposed edge
As all above modules/apps in place
finally in the Xposed edge adding key, app was able to recognize GA button as "PROG_BLUE", there user should be able to program it however they like (attach is my configuration, and all working smoothly)
{
"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"
}

tukes said:
you need root for this?
Click to expand...
Click to collapse
Yes, Magisk root and systemless Xposed. See @SonySteve's post above for the full list of modules.
There's an app that works for remapping the assistant button on last year's Xperia models without root, and might soon be updated for the 1 iii, but as I understand it it works basically the same way as Bixby non-root remappers, using accessibility services to track when the assistant is opened via a button press and then immediately close it and do something else.
The root approach lets you skip that process and directly reassign the button, which makes it faster and less susceptible to errors.

if i root, i can't use my banking app anymore :-(
hopefully Sony will fix this in the next update...

tukes said:
if i root, i can't use my banking app anymore :-(
hopefully Sony will fix this in the next update...
Click to expand...
Click to collapse
What bank is that? I'm with Bank of Scotland and their app fights me a bit on the root thing, but Magisk Hide plus the Universal Safetynet Fix module gets it working.

i'm in Belgium, all banking apps stop working if you root your phone here :-(
few years ago this wasn't so....

tardis_42 said:
Update: I figured out how to make it installable through Magisk Manager, new zip in first post.
Click to expand...
Click to collapse
tukes said:
i'm in Belgium, all banking apps stop working if you root your phone here :-(
few years ago this wasn't so....
Click to expand...
Click to collapse
I was flashing / locking / unlocking to test on DRM / finance app protection etc.
The good news is after re-locking my device, I was able to return back to Widevine L1 status, for streaming platform that requires it. (certainly stay L3 in unlock / rooted state). Banking apps wise no gurantee even after I relock the phone somehow (for my Taiwan based fiance/bank related apps).
I already have MagiskHide Props / SafetyNet passed etc., all in place and some banking apps still would detect device been compromised / unable to launch.
But, since I'm more accustomed to rooted device, I'm ultimately currently stay rooted.
I was able to get the finance app to run via install this Shelter app from Google PS, able to launch and log in all right for me.
Hope my above experience help there.

SonySteve said:
I was flashing / locking / unlocking to test on DRM / finance app protection etc.
The good news is after re-locking my device, I was able to return back to Widevine L1 status, for streaming platform that requires it. (certainly stay L3 in unlock / rooted state). Banking apps wise no gurantee even after I relock the phone somehow (for my Taiwan based fiance/bank related apps).
I already have MagiskHide Props / SafetyNet passed etc., all in place and some banking apps still would detect device been compromised / unable to launch.
But, since I'm more accustomed to rooted device, I'm ultimately currently stay rooted.
I was able to get the finance app to run via install this Shelter app from Google PS, able to launch and log in all right for me.
Hope my above experience help there.
Click to expand...
Click to collapse
gonna try this later this week! Thx

Great job man. Most useful phone I've ever had got even more useful!

tukes said:
gonna try this later this week! Thx
Click to expand...
Click to collapse
Did you get to try it? I'm interested as well if it works. I recieved my 1 III today and I'm on the fence about sending it back because of the root issues.

I've also removed GA from my xperia 1III, with out installing and modifying my phone, my GA button is also disabled, also removed all these app which is labelled in black and white, some of this app when installed are hidden.

I was able to remap my assistant button. I do not know if my previous uninstall of Google as well as the Google assistant App(s) had any bearing on the results...but I did use ADB to uninstall those things and it did disable the button, because when the phone was unlocked pressing the button did nothing at all. However, I did notice that when the phone was locked if I pressed the assistant button it would call up the login screen, so evidently it was still doing something!
At any rate this is how I did it:
Release 0.6.0 · ivaniskandar/shouko
This is an old release, get the latest release here. Add Assistant Button Override support for Xperia 1 III and 10 III (Thanks to @malibcia, @TheNetAdmin and @andreidobrica for testing) Fix Assist...
github.com
I want to thank each and every person who provided all this information as well as for the technical know-how to make this work!!!
I just wanted to add that when I press the assistant button the app I chose (for now the settings app) opens immediately with no hesitation at all.

svenM said:
Did you get to try it? I'm interested as well if it works. I recieved my 1 III today and I'm on the fence about sending it back because of the root issues.
Click to expand...
Click to collapse
haven't tried it yet...

AMAZING

tardis_42 said:
I've created a very simple Magisk module to allow Xposed Edge to properly remap the Google Assistant button. You'll need Magisk and a Magisk-based Xposed implementation (I use LSPosed) for this to work.
Xposed Edge is the only remapping tool I've found so far that can properly detect the assistant button being pressed. The problem is, while you can assign it to an action using Xposed Edge, it will ALSO launch the assistant. What I've done is built a Magisk module that alters the gpio-keys.kl file in /vendor/usr/keylayout to change the keycode the system receives when the assistant button is pressed. Currently I've used PROG_BLUE, which is a keycode used in Android-powered smart TVs with programmable remote buttons.
To use, just download and use the "install from storage" option on the modules screen in Magisk. Once the module's installed and activated, reboot.
Once rebooted, you can open Xposed Edge, and under "Keys", tap "Add...". It will tell you to click the button you want to add, and if all goes well, you can press the assistant button and it will detect a press of PROG_BLUE. Then you'll be able to assign any Xposed Edge action or shortcut to it, and the assistant won't show up.
Usual disclaimers, works for me but not responsible if your phone blows up, etc.
Right now the module tested with the Xperia 1 III. If you own another device with a hardware assistant key and want to let me know what GPIO key number is associated with it (probably under /vendor/usr/keylayout, look for the number on the line with ASSIST), I might be able to expand it to other devices.
It's possible it may work in its current state for other Xperia devices, but there's a risk the changes to gpio-keys may mess up your other hardware buttons including power - so if you try it on, eg, an Xperia 5 III make sure you have another way to reboot if it breaks your power button and you need to uninstall the module!
Click to expand...
Click to collapse
thanks

SonySteve said:
Just listing out things needed to be installed for your module to work.
Magisk module:
Riru
Riru - LSPosed
XperiaGAButtonRemap (install from storage .zip provided on this thread)
Click to expand...
Click to collapse
I didn't need all of those, you can also just use buttons remaper. I don't have riru or any xposed substitue, or even the APK from the package here, just the magisk module from this thread installed via magisk. On it's own, it remaps the assistant button to PROG_BLUE, which Buttons Remapper (and presumably xposed edge) can then read (it's unable to read the assistant button without this, which is why I went searching for another solution).

Related

[MOD] Patched Google Wallet for Galaxy S4 (Version 1.x - Old Version)

Patched Google Wallet for Galaxy S4
(Version 1.x - Old Version)
{
"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"
}
Description: This method (nearly identical to my previous thread for the Verizon Galaxy S III) will help you get Google Wallet working on your Verizon Galaxy S4, regardless if you have a TouchWiz-based ROM or AOSP-based and whether it's Odexed or Deodexed. This should also work on AT&T/Sprint/T-Mobile Galaxy S4 as well.
Please Note: In order to use this method you need to be rooted and have a custom recovery (1, 2, or 3).
Video Demos of the Full Process (Courtesy of 17akota and DroidModd3rX)
Click to expand...
Click to collapse
Downloads (Version R96 v16)
TouchWiz Only - Download Link
AOSP Only - Download Link
Click to expand...
Click to collapse
How to Apply Mod
1. Make sure you have no Google Wallet pre-installed, or if you do, reset data on it
2. Once you have reset the data, go to the Wallet app in your Application Manager
3. Select to "Clear Cache", then to "Clear Data"
4. If you see "Uninstall Updates", select that button, but if you see "Disable" button leave it alone
5. Using a root explorer and text editor, change build.prop lines to correspond to this
Code:
ro.product.model=Galaxy Nexus
ro.product.name=yakju
ro.product.device=maguro
6. Keep an old version as a backup
7. Copy the TouchWiz or AOSP zip file for the mod to your phone/SD Card
8. Reboot into your recovery and flash the Google Wallet mod
9. Boot back into the OS and open Xposed Installer app (should be installed after flash)
10. Select "Install/Update" and allow root access if it asks
11. Reboot your device
12. Download and install Paul's Xposed Wallet apk
13. Launch Xposed Installer app again and go to the "Modules" tab
14. Enable the module by checking the checkbox for it
15. Reboot your device again
16. Now open Google Wallet and setup everything as needed (PIN/Security/Cards, etc...)
17. After it is all setup and working, change your modified build.prop back to ONE of the below
Verizon Galaxy S4
Code:
ro.product.model=SCH-I545
ro.product.name=jfltevzw
ro.product.device=jfltevzw
AT&T Galaxy S4
Code:
ro.product.model=SGH-I337
ro.product.name=jflteatt
ro.product.device=jflteatt
T-Mobile Galaxy S4
Code:
ro.product.model=SGH-M919
ro.product.name=jfltetmo
ro.product.device=jfltetmo
Sprint Galaxy S4
Code:
ro.product.model=SPH-L720
ro.product.name=jfltespr
ro.product.device=jfltespr
18. Reboot your phone normally one last time and you will be all set
Click to expand...
Click to collapse
When Changing Roms
1. Open Google Wallet
2. Press the Menu key on your device
3. Select "Settings"
4. Select "Reset Google Wallet app"
5. Select "Reset" button
6. Flash your new ROM and/or wipe as needed
7. Follow "How to Apply Mod" directions again from the beginning
Click to expand...
Click to collapse
Updating to New Version Anytime
1. Follow "How to Apply Mod" steps #5 and 6
2. Reboot your device
3. Open the Play Store and update Google Wallet
4. Open Google Wallet and test everything is working
5. If all is good, follow "How to Apply Mod" steps #17
6. Reboot your device again and confirm everything still working
Click to expand...
Click to collapse
Credits
Credit goes to PaulOBrien for providing the patched Google Wallet apk (Original Post)
Credit goes to tonu42 for creating the original thread for the mod (Original Post)
Credit goes to rovo89 for creating the Xposed Mod (Original Post)
Credit goes to joemagistro for creating the deodexed-only version of this mod in the T-Mobile Galaxy S4 section (Original Post)
Everything seems to be working. I will have to head to McDonald's tomorrow and give it a try. Thanks!
Well I got this working from the other thread but looks to be same methods which is fine.
Now poking around... I noticed I have a devices section on the Wallet website and see I can reset it remotely if anything happens (though I wouldn't test that for ROM issues). Nice to know... is this more a secure element self destruct?
Also I notice a section asking to "Verify Identify" which if required... I will. But I am already reading where people have entire Play Store/Checkout locked out over this permanently over this. I just hope I don't get my account screwed one day because Google hates the grocery which I shop at or some lame thing where GPS is off by 500ft and claims I'm not there.... I know farfetched and over the top but just concerned or if anyone had issues with this.
Ok it works for me untill I change my build.prop back. What am I doing wrong
Sent from my galaxy nexus using xda app-developers app
coolsilver said:
Well I got this working from the other thread but looks to be same methods which is fine.
Now poking around... I noticed I have a devices section on the Wallet website and see I can reset it remotely if anything happens (though I wouldn't test that for ROM issues). Nice to know... is this more a secure element self destruct?
Also I notice a section asking to "Verify Identify" which if required... I will. But I am already reading where people have entire Play Store/Checkout locked out over this permanently over this. I just hope I don't get my account screwed one day because Google hates the grocery which I shop at or some lame thing where GPS is off by 500ft and claims I'm not there.... I know farfetched and over the top but just concerned or if anyone had issues with this.
Click to expand...
Click to collapse
I wouldn't worry too much about those, I think the remote reset from the website just wipes the app by itself, the secure element stays working so it can be passed on. Highly unlikely and unnecessary that Google will want to brick a secure element for security purposes.
iTechWNC said:
Ok it works for me untill I change my build.prop back. What am I doing wrong
Sent from my galaxy nexus using xda app-developers app
Click to expand...
Click to collapse
Which method did you use? What happens when you restore the build.prop? I personally have this running back on the stock build.prop using method A, so I know no issues on that one.
Will this work for the at&t phone of the same model sgh-i337? Stock rom rooted.
Sent from my SAMSUNG-SGH-I337 using xda premium
I'm currently stuck in "identity verification hell" and can't use Wallet even on my 100% stock Nexus 7. not happy. I sent them my license and a utility bill already and they still want more (SS card) which seems ridiculous. Amazon Payments was required to collect SSNs not too long ago...but they didn't require a freakin scan of the original document.
ugh.
anyway: Method A works great for me (still on TouchWiz for now sadly).
anyone else notice that when you change the build.prop product name, if you long-press the home button you see three icons along the bottom of the screen instead of "Task manager", "Google", and "Close All"? I believe that's what AT&T/T-Mo users see by default. wasn't enough to get rid of that stupid WiFi notification though
Sent from my SCH-I545
djdef80 said:
Will this work for the at&t phone of the same model sgh-i337? Stock rom rooted.
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
The way I designed it I'm pretty sure it should. Give it a try and let us know.
trogdor3222 said:
I'm currently stuck in "identity verification hell" and can't use Wallet even on my 100% stock Nexus 7. not happy. I sent them my license and a utility bill already and they still want more (SS card) which seems ridiculous. Amazon Payments was required to collect SSNs not too long ago...but they didn't require a freakin scan of the original document.
ugh.
anyway: Method A works great for me (still on TouchWiz for now sadly).
anyone else notice that when you change the build.prop product name, if you long-press the home button you see three icons along the bottom of the screen instead of "Task manager", "Google", and "Close All"? I believe that's what AT&T/T-Mo users see by default. wasn't enough to get rid of that stupid WiFi notification though
Sent from my SCH-I545
Click to expand...
Click to collapse
Wow sorry to hear about all that difficulty. Hope you get it resolved with Google promptly! Glad to hear the method worked for you though (as expected).
On an unrelated note take a read at this thread here regarding the icons instead of words and also the Wifi notification fixes: http://forum.xda-developers.com/showthread.php?t=2295622
!!!! Gonna try this today
Sent from my SCH-I545 using Tapatalk 4 Beta
Awesome! Going to switch to odex rom and try later. Hopefully this works!
Sent from my SCH-I545 using Tapatalk 4 Beta
open1your1eyes0 said:
On an unrelated note take a read at this thread here regarding the icons instead of words and also the Wifi notification fixes: http://forum.xda-developers.com/showthread.php?t=2295622
Click to expand...
Click to collapse
brilliant! thanks for sharing
Sent from my SCH-I545
Method A , Step 7. Reboot into your recovery and flash the Google Wallet mod
The file downloads as JFLTEVZW-Wallet-TW-JB-1.6-R96-v16.zip.zip
It's a nested zip file. does it need to be unzipped one level first or is that just the name of it ?
Mine has been at 'setting up this could take 5 minutes' for 10 minutes. I used Method A.
Nice, just finished Method A.
ZIP file was fine as is.
Everything appears to be working. Will confirm after i get to make a purchase at some point. Thanks!!!!
Edit; I had previously used Google Wallet on my Galaxy Nexus so everthing came back, cards, etc. easy peasy.
What happens if we follow all steps properly and get Wallet working, but then flash the 3Minit framework after in order to use the UI tweaks that the 3Minit app offers? Does that mess anything up for Wallet or is that Xposed framework needed permanently?
Parafly said:
Method A , Step 7. Reboot into your recovery and flash the Google Wallet mod
The file downloads as JFLTEVZW-Wallet-TW-JB-1.6-R96-v16.zip.zip
It's a nested zip file. does it need to be unzipped one level first or is that just the name of it ?
Click to expand...
Click to collapse
My mistake, it's not actually a nested file if you look inside, I just forgot to rename it. I'll reupload with proper name to avoid confusion.
EVOme said:
Mine has been at 'setting up this could take 5 minutes' for 10 minutes. I used Method A.
Click to expand...
Click to collapse
This one did take some time for me as well, usually just let it be there for about 5-15 minutes. It checks a lot of stuff in the background at this point.
open1your1eyes0 said:
This one did take some time for me as well, usually just let it be there for about 5-15 minutes. It checks a lot of stuff in the background at this point.
Click to expand...
Click to collapse
Wow!! That took like 23 minutes to configure, but it's working!!!!!!!!! Solid work on this. This was the only thing my S4 was missing.
THANKS!!!!!!!!!!!!!!!!!!!!!!!!!
just4747 said:
What happens if we follow all steps properly and get Wallet working, but then flash the 3Minit framework after in order to use the UI tweaks that the 3Minit app offers? Does that mess anything up for Wallet or is that Xposed framework needed permanently?
Click to expand...
Click to collapse
The Xposed framework is needed to stay there for Google Wallet to patch properly but if I understand that 3Minit mod correctly I think it just added an additional patch to the Xposed framework to enable and doesn't need to replace it? Could be wrong but I think it should be fine.
I already have xposed framework installed. Do I have to UN install it before doing this? I'll lose all my mods.. and have to set it all up again, grr.
Sent from my SCH-I545 using xda premium
ticrandall said:
I already have xposed framework installed. Do I have to UN install it before doing this? I'll lose all my mods.. and have to set it all up again, grr.
Sent from my SCH-I545 using xda premium
Click to expand...
Click to collapse
In that case not required. All you have to do is update the new one that this mod flashes, the rest should remain the same however.

[MOD][Multi Window][I717][4.1.2 Deodexed]

DISCLAIMER: I'M NOT RESPONSIBLE IF YOU DAMAGE YOUR DEVICE OR DELETE YOUR DATA...BE SURE TO BACKUP BEFORE YOU BEGIN AS ALWAYS!
Well...without further wait i present to u the multi window mod for the I717! First & foremost...i would like to give ALL thanks to the multiwindow master himself @xperiacle because without his work none off these mods would even be possible. Second...please keep in mind that i do NOT actually own an I717 so my help may be limited but i must say that u guys have some of the most dedicated users i have ever seen so i'm sure they will be more than willing to be of assistance in case in any issues may arise. This will be provided in 2 versions one for MD1 & another for MD3 so be sure to download the proper package for your firmware...be aware that this mod will most likely remove certain features from cutom roms so if u cant do without them then u may need to wait until your favorite chef cooks up a version which includes multiwndow
YOU MUST BE USING A 4.1.2 DEODEXED TOUCHWIZED BASED ROOTED ROM TO INSTALL THIS MOD!
INSTALL INSTRUCTIONS
1. Install busybox if not already present on your device
2. Download an alternative launcher (i personally use apex)
3. Open your build prop and find the line "qemu.hw.mainkeys=1" and change it to "qemu.hw.mainkeys=0" then save and reboot (this is what adds the onscreen buttons/bottom bar...MUST be done for phablet/tablet mode to work)).
4. Flash the version which matches your firmware (check "settings/about device/build number" & grab the zip that matches the last 3 digits)
5. Install the xposed framework as well as the app settings module (links below) then set "com.sec.android.app.flashbarservice" to 320 dpi then save & reboot (the edit button will not appear in other dpi settings without performing this step)
6. Open the "FLOATING MW CONTROL" and choose your desired setup
7. If u would like to add extra apps to the multiwindow launcher then download the "MULTIWINDOW APPS MANAGER" xposed module from the link below...u MUST reboot after enabling apps then open the bar, press the "edit" button at the bottom and u should see the list of available apps which need to be dragged over to the tray then press done when finished
KNOWN ISSUES
1. Padawan V4 users MUST install the zip IMMEDIATELY after flashing the rom WITHOUT rebooting to prevent sytemui force closes (alternatively if u do not want to reinstall your rom u can try wiping BOTH caches before/after flashing the mod although this may not help)
2. The icon next to the "edit" button located in the bottom bar when in phablet/tablet mode will cause will cause a force close so do not press it (it was implemented as an expanded desktop switch for N7000 but doesnt function on the I717)
As mentioned in step 6...this mod includes an app called "FLOATING MW CONTROL" (created by & used with the permission of @xperiacle) which not only does as the name suggests but even more, although users should be aware that it was not created specifically with the I717 in mind (it was designed to be used with the international N7000 instead) so there may be options which do not function properly. With that said...this app will allow u to switch from phone to tablet ui as well as from side/flashbar multiwindow mode to the bottom/traybar style and also allow u to hide the navbar as well. There is no proper documentation for the app itself although u will find that it is very intuitive and will not only tell u what step to take next to get the desire results but will also inform why u are not allowed to perform certain actions....well i hope u all enjoy your device a lil more now that it has this useful feature which samsung should have included in the first place
View attachment I717MD1MultiWindowModV1.zip
^MD1 V1
https://drive.google.com/file/d/0B7yxeu9x48ILSlBOcmExbXlLME0/edit?usp=sharing
^MD3 V1
http://forum.xda-developers.com/showthread.php?t=1574401
^XPOSED FRAMEWORK THREAD
http://forum.xda-developers.com/showthread.php?t=2437377
^APP SETTINGS MODULE THREAD
http://forum.xda-developers.com/showthread.php?p=42078224
^MULTIWINDOW APPS MANAGER MODULE THREAD
credit/thanks to: ALL testers who helped get this thing going for u guys but i would like to extend special assistance attention to @scariola as well as @_INSPIREed for going above and beyond to work out the glitches as well as help their fellow I717 owners @xperiacle for the systemui, floating mw control app, & multiwindow apps manager module @rovo89 for xposed & @Tungstwenty for the app settings module
attention all devs: consider this my express permission (although i STRONGLY suggest getting separate permission from @xperiacle before using the included app which is entirely his work) to use this mod in building your roms with proper credit of course BUT i only ask that u actually bake it into the rom itself instead of providing an add-on zip (in that case just link your users back here) which may cause confusion and unnecessary/improperly placed posts...thx
screenshots
here u guys go...a few photos showing the different ui modes and multiwindow styles
{
"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"
}
Great work @THEDEVIOUS1
Much appreciated
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Damn...I limited to 8 thanks.
Thanks. Wonderful job
@THEDEVIOUS1 once again bro thanks for all your work. Been good testing your work, you truly have been an amazing help for this device. And don't worry the thread will run itself. We have a bunch of people who will pitch in when needed, and when in doubt, I think I speak for myself, and @scariola saying I have no problem pitching in like always. I know you have some other devices to attend to . Good luck on them bro :good::good:
_INSPIREed said:
@THEDEVIOUS1 once again bro thanks for all your work. Been good testing your work, you truly have been an amazing help for this device. And don't worry the thread will run itself. We have a bunch of people who will pitch in when needed, and when in doubt, I think I speak for myself, and @scariola saying I have no problem pitching in like always. I know you have some other devices to attend to . Good luck on them bro :good::good:
Click to expand...
Click to collapse
when u get time could u still check the xposed module with the miniapps traybar/bottom multiwindow launcher to see if it will add apps...i recommended the play store app just to be safe and to be honest i'm curious to find the code for my own device as well
Good work on this.
THEDEVIOUS1 said:
when u get time could u still check the xposed module with the miniapps traybar/bottom multiwindow launcher to see if it will add apps...i recommended the play store app just to be safe and to be honest i'm curious to find the code for my own device as well
Click to expand...
Click to collapse
Multi Window Manager wants to patch a file and asks me which device I am running,
What device do I select when it asks me what device I am using? (Of course I717 is not there,)
The xposed module works for me, although there are apps which won't take to multi-window.
pTeronaut said:
Multi Window Manager wants to patch a file and asks me which device I am running,
What device do I select when it asks me what device I am using? (Of course I717 is not there,)
The xposed module works for me, although there are apps which won't take to multi-window.
Click to expand...
Click to collapse
Ya the N7000 patch works for the i717 on the MWM app
hi just a noob question here... which one i should download MD1 or MD3? i'm using stock 4.1.2 i717D (Telus) rooted
I have downloads the md3 file have everything to work in padawan v4 but keep getting system ui has stopped please help
Sent from my SAMSUNG-SGH-I717 using Tapatalk
bongra80 said:
I have downloads the md3 file have everything to work in padawan v4 but keep getting system ui has stopped please help
Click to expand...
Click to collapse
Did you follow Install Step #3?3. Flash the version which matches your firmware (due to force close issues Padawan V4 users MUST install the zip IMMEDIATELY after flashing the rom WITHOUT rebooting)
​As noted in the OP this does break the ROM Customizer options in BlackSTAR BLACKJelly v2. Multiwindow works now though.
Also reporting that the Xposed MW Apps Manager works.
.
in FW app, I go through selections. when I get to Navbar which I want to hide, the multiwindow chooser comes up. stock or floating? I have hit floating twice and phone reboots
I am doing something wrong. attempting to follow.
captemo said:
in FW app, I go through selections. when I get to Navbar which I want to hide, the multiwindow chooser comes up. stock or floating? I have hit floating twice and phone reboots
I am doing something wrong. attempting to follow.
Click to expand...
Click to collapse
I think the original op said to pick stock
frome901 said:
I think the original op said to pick stock
Click to expand...
Click to collapse
reboots on both
LiMITZERO said:
hi just a noob question here... which one i should download MD1 or MD3? i'm using stock 4.1.2 i717D (Telus) rooted
Click to expand...
Click to collapse
Look under Settings/about/ and check your build number.
I do believe it will have MD1 on the end of it. So that would be the MD1 v1 you would use.
captemo said:
reboots on both
Click to expand...
Click to collapse
Does it hide the nav bar? Im still trying to line it out myself, so
frome901 said:
Does it hide the nav bar? Im still trying to line it out myself, so
Click to expand...
Click to collapse
I go through the FW settings one at a time. when I get to the hide the navbar, I hit hide. window then pops up stock or floating. instantly reboots. the navbar never appears. even after reboot.
had to charge phone a bit before playing more.
captemo said:
reboots on both
Click to expand...
Click to collapse
It will reboot on both. What is not happening for you? Touchwiz has no navbar since our phone has capacitance buttons so there is nothing to show or hide. Apex launcher does. That is if this app refers to the onscreen buttons as the navigational bar.
My issue is I can't find the bottom bar no matter what mode or DPI I try. I always get the sidebar.
captemo said:
I go through the FW settings one at a time. when I get to the hide the navbar, I hit hide. window then pops up stock or floating. instantly reboots. the navbar never appears. even after reboot.
had to charge phone a bit before playing more.
Click to expand...
Click to collapse
It reboots so that setting sticks. I have noticed that whenever you change any setting in FW app it will automatically reboot to stick changes
Sent from my SAMSUNG-SGH-I717 using xda app-developers app

[ROM][S905X2] A95X Max - atvXperience v3 - The Ultimate AndroidTV OS Experience!

{
"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"
}
We're back, boys!
This time with with Oreo 8.1.0 atvXperience v3 for S905X2 and specifically A95X Max!
THE FIRST EVER CUSTOM ROM FOR A95X MAX!!
• Android OS version: 8.1.0
• For devices: A95X MAX
• Recovery: AOSP
Those who don't have it, you can buy from this link. Probably the most popular S905X2 TV box with HDD and SSD Support and really fast and stable!
https://www.gearbest.com/tv-box/pp_009379639442.html?wid=1433363&lkid=39289238
Attention:
I don't force you to use the ROM. It's stable and can be used as daily driver except for a few things.
If you don't like something, please ask me on how to remove/add it.
atvXperience and nobody from the team nor the forum moderators are responsible for bricked devices. But we always try to help as much as we can
Click to expand...
Click to collapse
Based on AndroidTV OS. Has all the features of an AndroidTV but since atvXperienceOS provides a different experience, we combine the best of AOSP and ATV.
Credit: SrWladimir
* Nayam Amarshe
* Carmine Rovito
* Taylor Stephen Hadden
* Vadim Mussin
v3A
NOTE
The first boot will take a lot of time! Screen will be glitchy, bootvideo will be laggy and you may not even see anything except for black screen but this is normal and doesn't affect the device in any way. This only happens on the first boot because the encrypted kernel and bootloader try to reject the device but it boots anyway and everything will be OK in the second boot.
v3A
• Based on latest AndroidTV OS, latest Security patches.
• Google Play Works
• All Google Apps Work!
• Recommendations work great! To turn off go to Settings - Home
• Casting Works with Airscreen
• Fully Compatible with A95X Max!
• atvXed up with Multiple USB drivers!
v3B To-Do:
Add USB drivers
Add Navbar and Status Bar
Change Settings shortcut to TVSettings
Change App Drawer Wallpaper
Add some more preinstall apps
DO THE ATVX THING
PLEASE WATCH THE YOUTUBE VIDEO:
https://m.youtube.com/watch?feature=youtu.be&v=hnliXmly7WY
Please consider donating if you like our work
PAYPAL LINK
or
PAYPAL EMAIL
[email protected]
Known Problems:
None my boi
Credits:
Fabio Ciani
Ricky Divjakovski
Superceleron
eric
A95X Max developers
XDA-Developers Members
forumXperience members
My team
atvXperience followers
and the one reading this
Special Thanks to my boi Nitin for making this when I was busy
Rom is *meh*, as it completely throws away the stock android Oreo layout and switches to a straight up TV Box setup like a Roku. Most apk's refuse to work with this setup. The included Youtube app sucks and needs to be REMOVED FROM THE ROM as a system app or at least replaced with YT Vanced. Also, Chrome is simply gone...and you cant find it in the "store" either. The apk can be manually installed with a USB/SD card. Netflix app installed within the store does not work with this rom so its like what are we doing here?... but there is a work around. There is no option to boot straight to recovery either, if there even is one. We need TWRP for this to let us do what we want...Get rid of the Android TV BS and let people install their own launcher and you will profit more than just re-skinning the stock OS with this.
Then don't use it... I use it because of the Android TV layout. He was very up front in the beginning as to what this was and what would and would not work. No 3rd party box is going to work with Netflix or Amazon Apps at this time due to widevine DRM.
If what you have described is what you want, then by all means make your own ROM.
Rumsfield said:
Rom is *meh*, as it completely throws away the stock android Oreo layout and switches to a straight up TV Box setup like a Roku. Most apk's refuse to work with this setup. The included Youtube app sucks and needs to be REMOVED FROM THE ROM as a system app or at least replaced with YT Vanced. Also, Chrome is simply gone...and you cant find it in the "store" either. The apk can be manually installed with a USB/SD card. Netflix app installed within the store does not work with this rom so its like what are we doing here?... but there is a work around. There is no option to boot straight to recovery either, if there even is one. We need TWRP for this to let us do what we want...Get rid of the Android TV BS and let people install their own launcher and you will profit more than just re-skinning the stock OS with this.
Click to expand...
Click to collapse
Parsival1973 said:
Then don't use it... I use it because of the Android TV layout. He was very up front in the beginning as to what this was and what would and would not work. No 3rd party box is going to work with Netflix or Amazon Apps at this time due to widevine DRM.
If what you have described is what you want, then by all means make your own ROM.
Click to expand...
Click to collapse
I'll get right on it.
Rumsfield said:
Rom is *meh*, as it completely throws away the stock android Oreo layout and switches to a straight up TV Box setup like a Roku. Most apk's refuse to work with this setup. The included Youtube app sucks and needs to be REMOVED FROM THE ROM as a system app or at least replaced with YT Vanced. Also, Chrome is simply gone...and you cant find it in the "store" either. The apk can be manually installed with a USB/SD card. Netflix app installed within the store does not work with this rom so its like what are we doing here?... but there is a work around. There is no option to boot straight to recovery either, if there even is one. We need TWRP for this to let us do what we want...Get rid of the Android TV BS and let people install their own launcher and you will profit more than just re-skinning the stock OS with this.
Click to expand...
Click to collapse
Read the title again maybe?
This is an AndroidTV OS and no it's not BS. Maybe it's only you who likes to use a mouse and keyboard on a tv. This is meant for those who don't want the airmouse BS and want a clean look, to have the real AndroidTV Box and not just a phone-UI Android Box and not the *meh* launchers that are meant for phone screens.
All apks work, if it works in the phone rom, it works in ATV. 'Maybe' you're doing something wrong or lack the knowledge of apps installation.
The google play store is meant for AndroidTV, it shows apps which are compatible with your remote, not mouse or keyboard.
Also, Netflix thing, everybody knows you need a Netflix certified box for it, it's even mentioned on their website.
And everybody knows you can use Aptoide Store for other apps that aren't on play store.
If you want your own launcher, go ahead make a ROM but please don't call my work a 'simple reskin' because I am working my ass off for a box that's totally encrypted to the core and has a 'meh' phone UI.
So, please don't think I'm playing copy and paste here, I've worked hard on this and if my work is *meh*, please use another ROM (if it exists).
Thank you for the feedback on v3A
Sent from my Spaceship using Tapatalk
Links Updated!
Please don't forget to watch the tutorial video first.
Thank you for the support.
Sent from my F3116 using Tapatalk
Good... Then you can ***** and complain to yourself rather than crap on someone elses hard work.
Rumsfield said:
I'll get right on it.
Click to expand...
Click to collapse
Parsival1973 said:
Good... Then you can ***** and complain to yourself rather than crap on someone elses hard work.
Click to expand...
Click to collapse
Did I ***** and complain? I simply stated some of this rom's caveats and giving a heads up to people who might prospectively install this not realizing its going to completely change the OS to a dedicated Kodi box.
No browser at all? Youtube that you cant get rid of? If you dont like my opinion you can straight up not listen to it. I doubt you even installed it in the first place or you wouldn't be responding with your sh*t posts.
Rumsfield said:
Did I ***** and complain? I simply stated some of this rom's caveats and giving a heads up to people who might prospectively install this not realizing its going to completely change the OS to a dedicated Kodi box.
No browser at all? Youtube that you cant get rid of? If you dont like my opinion you can straight up not listen to it. I doubt you even installed it in the first place or you wouldn't be responding with your sh*t posts.
Click to expand...
Click to collapse
You can install Puffin Browser from Google Play. It's the best TV Browser out there, 100% remote compatibility.
It's pre-rooted, you can easily uninstall YouTube if you know what root means. AptoideTV Store is there to help.
I thought I included webXperience, It's our own browser. If I didn't, I'll do it in the next release which is going to shut everybody up because as I mentioned, this is the first release and the next will be address all the issues you mentioned and the features that I mentioned.
If you want a phone rom on a tv box, please go elsewhere because this is an AndroidTV thread, please don't argue here, the mods take notice of everything.
Thank you for understanding.
Sent from my F3116 using Tapatalk
N'ayam Amarsh'e said:
You can install Puffin Browser from Google Play. It's the best TV Browser out there, 100% remote compatibility.
It's pre-rooted, you can easily uninstall YouTube if you know what root means. AptoideTV Store is there to help.
I thought I included webXperience, It's our own browser. If I didn't, I'll do it in the next release which is going to shut everybody up because as I mentioned, this is the first release and the next will be address all the issues you mentioned and the features that I mentioned.
If you want a phone rom on a tv box, please go elsewhere because this is an AndroidTV thread, please don't argue here, the mods take notice of everything.
Thank you for understanding.
Sent from my F3116 using Tapatalk
Click to expand...
Click to collapse
I am familiar with rooting aka administrative privileges over apps/os and have had many phones/tablets/matricom boxes all eventually rooted with either magisk or super su, some I actually paid for. This rom doesnt allow me to uninstall anything, just disable which is not the same. How can I grant root access to any app, such as bloatware removal tools? There is no root management on this thing. (that I am aware of?) and there is no recovery I can see to get into to flash anything besides the temp TWRP method with an sd card + paper clip which has not worked with anything on this rom.
Rumsfield said:
I am familiar with rooting aka administrative privileges over apps/os and have had many phones/tablets/matricom boxes all eventually rooted with either magisk or super su, some I actually paid for. This rom doesnt allow me to uninstall anything, just disable which is not the same. How can I grant root access to any app, such as bloatware removal tools? There is no root management on this thing. (that I am aware of?) and there is no recovery I can see to get into to flash anything besides the temp TWRP method with an sd card + paper clip which has not worked with anything on this rom.
Click to expand...
Click to collapse
Try switching on the root switch from settings and reboot.
Another tip, install SuperSU 2.79 and it will fix your root management issues.
The recovery is stock, just like the original ROM. Use quick reboot app to reboot to recovery.
If it still doesn't work, I'll double check and fix anything if wrong. As I said, this is the first release so expect issues unless you know how to fix things but don't worry, the v2B or v2F (whatever I name it) is going to fix all the issues. Trust me, you'll never feel the need to use Navbar and Statusbar again with the new build.
Sent from my F3116 using Tapatalk
N'ayam Amarsh'e said:
Try switching on the root switch from settings and reboot.
Another tip, install SuperSU 2.79 and it will fix your root management issues.
The recovery is stock, just like the original ROM. Use quick reboot app to reboot to recovery.
If it still doesn't work, I'll double check and fix anything if wrong. As I said, this is the first release so expect issues unless you know how to fix things but don't worry, the v2B or v2F (whatever I name it) is going to fix all the issues. Trust me, you'll never feel the need to use Navbar and Statusbar again with the new build.
Sent from my F3116 using Tapatalk
Click to expand...
Click to collapse
Switching off/on root switch doesn't do anything even with restarting.
SuperSu 2.79 does not successfully flash in temp TWRP with paperclip method or with stock recovery (see pic).
Since there is no root management, quick reboot and other root required apps install but dont work.
Ad-Away also will not save host files either, and I prefer to use that in combination with chrome over Puffin.
If I pissed you off with my earlier post, I apologize and that was not my intent. I understand this rom is pretty much in beta at this point but its very frustrating when nothing works for me, pretty much at all except for what worked with the stock OS.
FYI I have the v81 board.
Rumsfield said:
Switching off/on root switch doesn't do anything even with restarting.
SuperSu 2.79 does not successfully flash in temp TWRP with paperclip method or with stock recovery (see pic).
Since there is no root management, quick reboot and other root required apps install but dont work.
Ad-Away also will not save host files either, and I prefer to use that in combination with chrome over Puffin.
If I pissed you off with my earlier post, I apologize and that was not my intent. I understand this rom is pretty much in beta at this point but its very frustrating when nothing works for me, pretty much at all except for what worked with the stock OS.
FYI I have the v81 board.
Click to expand...
Click to collapse
You are not supposed to flash super su. Just install it.
See here:
https://forum.atvxperience.com/viewtopic.php?f=16&t=814
Sent from my F3116 using Tapatalk
N'ayam Amarsh'e said:
You are not supposed to flash super su. Just install it.
See here:
https://forum.atvxperience.com/viewtopic.php?f=16&t=814
Sent from my F3116 using Tapatalk
Click to expand...
Click to collapse
It doesn't matter, it doesn't install either way (flashing vs apk).
All I can think of is to completely re-flash the new link firmware over my version I installed when you made it first available, maybe there is a difference?
Rumsfield said:
It doesn't matter, it doesn't install either way (flashing vs apk).
All I can think of is to completely re-flash the new link firmware over my version I installed when you made it first available, maybe there is a difference?
Click to expand...
Click to collapse
Thanks for letting me know, it's strange it's not working for you. My friend reported it working. I'll fix the su in the new version. Meanwhile, you can flash stock rom because I don't want you to get any issues.
New build will be ready in a week or so and it's going to be great!
Thanks for all the feedback.
Sent from my F3116 using Tapatalk
N'ayam Amarsh'e said:
Thanks for letting me know, it's strange it's not working for you. My friend reported it working. I'll fix the su in the new version. Meanwhile, you can flash stock rom because I don't want you to get any issues.
New build will be ready in a week or so and it's going to be great!
Thanks for all the feedback.
Sent from my F3116 using Tapatalk
Click to expand...
Click to collapse
Thats fine, so now we know why I was a bit brash in my original post.
It still needs a bit of polish. Thanks for you work.
Rumsfield said:
Thats fine, so now we know why I was a bit brash in my original post.
It still needs a bit of polish. Thanks for you work.
Click to expand...
Click to collapse
If you watch this video, you can see that Nicholas tested that the ROM is rooted. That's why I said, I don't know why it's not working for you.
https://youtu.be/hnliXmly7WY
Maybe you can try switching root switch off, reboot, then on and reboot.
I'll update the su anyway, nobody should be getting any problems but this box is one hell of a fighter. They've encrypted everything! I could only get access to system because kernel, recovery and everything else was encrypted.
Sent from my Spaceship using Tapatalk
N'ayam Amarsh'e said:
If you watch this video, you can see that Nicholas tested that the ROM is rooted. That's why I said, I don't know why it's not working for you.
https://youtu.be/hnliXmly7WY
Maybe you can try switching root switch off, reboot, then on and reboot.
I'll update the su anyway, nobody should be getting any problems but this box is one hell of a fighter. They've encrypted everything! I could only get access to system because kernel, recovery and everything else was encrypted.
Sent from my Spaceship using Tapatalk
Click to expand...
Click to collapse
Re-flashing the newer firmware link over last weeks firmware link allowed SuperSu apk to install successfully. Apparently we are good to go now...
Rumsfield said:
Re-flashing the newer firmware link over last weeks firmware link allowed SuperSu apk to install successfully. Apparently we are good to go now...
Click to expand...
Click to collapse
Sweet!
Do lookout for new version as it will include these features:
1. Replace settings shortcut with TV Settings
2. Include pre-install apps like Web browser, Netflix and other apps.
3. Double tap home button for Recent Apps and use arrow keys to clear the apps.
4. Hold Power button for quick shutdown.
5. Add Init.d tweaks for more performance.
6. Add Back-Panic Button.
7. Hold Back button for assistant.
8. Add Navbar and Status bar functionality (if possible)
9. Add Gamepad drivers
Sent from my F3116 using Tapatalk
N'ayam Amarsh'e said:
Sweet!
Do lookout for new version as it will include these features:
1. Replace settings shortcut with TV Settings
2. Include pre-install apps like Web browser, Netflix and other apps.
3. Double tap home button for Recent Apps and use arrow keys to clear the apps.
4. Hold Power button for quick shutdown.
5. Add Init.d tweaks for more performance.
6. Add Back-Panic Button.
7. Hold Back button for assistant.
8. Add Navbar and Status bar functionality (if possible)
9. Add Gamepad drivers
Sent from my F3116 using Tapatalk
Click to expand...
Click to collapse
I spoke too soon lol. SuperSu 2.79 installs after a fresh firmware flash but bootloops (waiting 20 minutes and still stuck on logo screen). Re-flashing and installing SuperSu 2.82 does the same thing. Oh well.
Re-flashing the image brings its back but just beware root doesnt work. I give up, good luck to everyone getting root.

SafetyNet?

Is there anything I can do about this?
Did you try this:
https://forum.xda-developers.com/apps/magisk/fix-magisk-manager-20-3-ctsprofile-t4080921
- Before starting the steps, uninstall all Magisk modules and reboot.
- If your device is not listed in the Props Config, you can try Google Pixel 2 or 3 and Android 10.
- Don't forget to hide Magisk in the Options and Google Play Services, Google Play Store, Google Pay and all banking/game apps in the Magisk Hide menu.
- You should know that all Samsung services (Pay, Pass, Secure Folder, etc.) related to KNOX will never work after rooting (= KNOX tripped)...
LeGi0NeeR said:
Did you try this:
https://forum.xda-developers.com/apps/magisk/fix-magisk-manager-20-3-ctsprofile-t4080921
- Before starting the steps, uninstall all Magisk modules and reboot.
- If your device is not listed in the Props Config, you can try Google Pixel 2 or 3 and Android 10.
- Don't forget to hide Magisk in the Options and Google Play Services, Google Play Store, Google Pay and all banking/game apps in the Magisk Hide menu.
- You should know that all Samsung services (Pay, Pass, Secure Folder, etc.) related to KNOX will never work after rooting (= KNOX tripped)...
Click to expand...
Click to collapse
@jhill110 sorry for necroposting this, but does it work out for you?
Arobase40 said:
SafetyNet fix !
Quicker and easier SafetyNet fix :
Erase the cache from Magisk and flash one of these two fixes :
I used the first one and it works so I didn't test the second...
At least Secure Folder is working fine. Knox deployment is behaving weirdly as it is asking a two pass authentication and it is asking a numerical code when I receive an alphanumerical code... ^^
I don't use Samsung Pay (should at least work with Android Pay but I didn't test it) and I don't use Samsung Pass either but I don't think there should be a real problem as it was asking me to set it up but I removed totally from the system...
Click to expand...
Click to collapse
actually for me safety net fix only works for android 11 version rom of this device, and even then secure folder doesnt work correctly (for me?), it doesnt save the password, and keep poping up asking to set a password whenever I tried to enter it. The device itself become unstable and keep hot rebooting after every unlock, eventually get thermal throttled for no reason. Though the safety net solution I used was this one: kdrag0n/safetynet-fix , and prob not the one you listed actually its the same developer, though his repository does not contain a v2 release. I still gona try it though
edit: working now, not hot rebooting (yet), but secure folder still doesnt save password, thus cant still be used yet
Arobase40 said:
So make sure you pass the SafetyNet test in Magisk. When done and passed, uninstall completely and properly Secure folder from your settings, and reboot.
Click to expand...
Click to collapse
the safetynet fix worked on my device when the rom is still on android 10. That is to say, it passed the safetynet test. It was extremely unstable though, hot rebooting after every unlock (unlock, black screen samsung, then back to lock screen) I couldn't get into magisk and disable it, had to delete it through twrp. It was until android 11 that I tried it again. not extremely unstable, just "useable unstable". That was the release file on kdrag0n's repository. Your uploaded v2 file works amazingly. Thanks for sharing:>
Arobase40 said:
I wonder why you mention Android 10 when we're with Android 11 for a long time now...
So is your issue totally fixed with no instability at all anymore and is Secure Folder working also ?
Click to expand...
Click to collapse
I just want to share my experience about the same device with (prob) the same safety net fix that works on yours, but not my device.
yes, with your safety net fix my tab runs absolutely stable, and I've just tried uninstall secure folder and reinstall it again. Its working perfectly now

[OFFICIAL] LineageOS 19.1 for the Google Pixel 4

{
"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 4
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 19.1 thread for the Google Pixel 4.
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.
flame​
flame - My unofficial with Google Apps/Pixel goodies included. Passes SafetyNet by default. OTA's roll roughly once a month. Support not guaranteed or implied.​
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.14
Great news! Thanks for bringing Android 12 to this device!
I just reading the installation instructions and there are some questions:
1. The instructions don't mention wiping the system/data partition. Does this mean that my device will work as before, that I will not have to reinstall my apps and data after upgrading? My device is neither rooted, nor do I use anything like Magisk.
2. The instructions say:
"Note: If you previously had any Google Apps add-on package installed on your device, you must install an updated package before the first boot of Android! If you did not have Google Apps installed, you must wipe the Data partition (or perform a factory reset) to install them."
That confuses me: when I installed LOS 18.1, I also installed the MtG package, that was available for the P4 at that time. After that, I never installed anything else via adb, I only updated what was offered in the PlayStore or by the OTA updater function.
How should I interpret that instruction:
A) I need to install the latest MtG, that is available for LOS 18.1, and then I can install LOS 19 plus MtG for LOS 19.
B) Installing LOS 19 plus the appropriate MtG at the same time (=before the first booting) is sufficient to make the system work again.
Thanks in advance for any help!
dvdram said:
Great news! Thanks for bringing Android 12 to this device!
.
.
.
Thanks in advance for any help!
Click to expand...
Click to collapse
Simply - boot into LOS 19 recovery
- Goto advance factory reset Format Data
- Then apply Update via ADB
- Reboot to recovery
- Apply MTG Packg [Gapps](https://wiki.lineageos.org/gapps.html) for LOS 19
- Boot into system
dvdram said:
Great news! Thanks for bringing Android 12 to this device!
I just reading the installation instructions and there are some questions:
1. The instructions don't mention wiping the system/data partition. Does this mean that my device will work as before, that I will not have to reinstall my apps and data after upgrading? My device is neither rooted, nor do I use anything like Magisk.
2. The instructions say:
"Note: If you previously had any Google Apps add-on package installed on your device, you must install an updated package before the first boot of Android! If you did not have Google Apps installed, you must wipe the Data partition (or perform a factory reset) to install them."
That confuses me: when I installed LOS 18.1, I also installed the MtG package, that was available for the P4 at that time. After that, I never installed anything else via adb, I only updated what was offered in the PlayStore or by the OTA updater function.
How should I interpret that instruction:
A) I need to install the latest MtG, that is available for LOS 18.1, and then I can install LOS 19 plus MtG for LOS 19.
B) Installing LOS 19 plus the appropriate MtG at the same time (=before the first booting) is sufficient to make the system work again.
Thanks in advance for any help!
Click to expand...
Click to collapse
reboot to recovery, flash newest ROM, reboot to recovery, flash MTG 12.1 - reboot to OS - done.
npjohnson said:
reboot to recovery, flash newest ROM, reboot to recovery, flash MTG 12.1 - reboot to OS - done.
Click to expand...
Click to collapse
So, no need to reinstall all personal apps and stuff?
dvdram said:
So, no need to reinstall all personal apps and stuff?
Click to expand...
Click to collapse
Correct. Again. Follow the wiki upgrade guide and all will be fine.
I had a problem with the March 17 update of my P4a. Thus, I didn't update the P4 that is also in my household. The problem is with visual voicemail failing. I created an issue here: https://gitlab.com/LineageOS/issues/android/-/issues/4523
Does anyone know if this also happened with the P4? I imagine the move to LOS19 would carry the same problem, since (I think) this update https://review.lineageos.org/c/LineageOS/android_packages_apps_Dialer/+/325978/ caused the issue.
Thanks for your work on this & keeping my old V20 useful.
npjohnson said:
Correct. Again. Follow the wiki upgrade guide and all will be fine.
Click to expand...
Click to collapse
That worked out very well. Thank you!
A few things I have not been able to figure out yet:
1. I can't find the quick setting tile for system profiles.
2. If the lockscreen's clock is set *not* to use two lines, it sticks to the upper left corner of the screen. The same is true for the "always-on-screen".
3. The owner's information used to be displayed directly beneath the clock and date, taking only one line. Now it is displayed at the button, taking more than one line.
4. How to change the white background when entering the unlock code?
I guess some, if not all of these things have not yet been implemented.
dvdram said:
That worked out very well. Thank you!
A few things I have not been able to figure out yet:
1. I can't find the quick setting tile for system profiles.
2. If the lockscreen's clock is set *not* to use two lines, it sticks to the upper left corner of the screen. The same is true for the "always-on-screen".
3. The owner's information used to be displayed directly beneath the clock and date, taking only one line. Now it is displayed at the button, taking more than one line.
4. How to change the white background when entering the unlock code?
I guess some, if not all of these things have not yet been implemented.
Click to expand...
Click to collapse
1.search for "Profiles" they're there
2. Intentional
3. An android 12 thing.
4. Don't think you can.
npjohnson said:
1.search for "Profiles" they're there
2. Intentional
3. An android 12 thing.
4. Don't think you can.
Click to expand...
Click to collapse
4: It was possible in A11.
3: Well, it looked better in A11.
2: Hm, why?
1: The system profiles are usable, there's just no tile for the quick settings. These are all quick setting tiles that I can see:
Hello guys...does this rom support VoLTE or VoWi-Fi? I don't know why, but if i insert the same SIM into my other phone, i have both of these services active...but not in my Pixel phone.
aresbv2000 said:
Hello guys...does this rom support VoLTE or VoWi-Fi? I don't know why, but if i insert the same SIM into my other phone, i have both of these services active...but not in my Pixel phone.
Click to expand...
Click to collapse
If stock supports it for your carrier, then yes. If not, no.
npjohnson said:
If stock supports it for your carrier, then yes. If not, no.
Click to expand...
Click to collapse
Thank you. So the answer is "No, it doesn't support VoLTE ot VoWi-Fi", since stock android 12.1 doesn't support . In my area the GSM signal is weak, VoWi-Fi was great on the other phone. So sad that Google decides to block some functions on different markets.
An old security issue has risen again: profiles should not switch while the device is locked.
Why? Because of this:
- create a profile with no screen lock.
- set a trigger for that profile: activate when connecting to a known wifi
- turn off wifi, switch to normal profile and make sure device is locked
- swipe down quick settings and activate wifi
- after a few seconds, wifi will connect, the new profile will be activated and the device will be unlocked without having to enter the unlock PIN!
I think this is a serious security issue, because any one who will find your "lost" phone and reaches the area covered by that specific wifi, will have instant access to your unlocked phone!
dvdram said:
An old security issue has risen again: profiles should not switch while the device is locked.
Why? Because of this:
- create a profile with no screen lock.
- set a trigger for that profile: activate when connecting to a known wifi
- turn off wifi, switch to normal profile and make sure device is locked
- swipe down quick settings and activate wifi
- after a few seconds, wifi will connect, the new profile will be activated and the device will be unlocked without having to enter the unlock PIN!
I think this is a serious security issue, because any one who will find your "lost" phone and reaches the area covered by that specific wifi, will have instant access to your unlocked phone!
Click to expand...
Click to collapse
That's intended behavior.
If you set up a profile to automatically unlock the device when you are at Wi-Fi, you can expect that anyone using the device would have that, how should we know it's out of your hands?
how should we know it's out of your hands?
Click to expand...
Click to collapse
That's exactly the point: you can't, but you also can not be sure that it's the rightful owner who holds the phone in his hands when the profile switches and the device unlocks!
I agree that there is a point in making things as convenient as possible for the user. But convenience and security exclude each other.
So, what about an extra option that, when activated, will not switch profiles while the device is locked? This option could be hidden in the developers options, so normal users are not even bothered to take care of it.
I remember this "feature" in LOS 16, and it was fixed, and I am surprised to see it again.
Thanks for the hard work. Will there be an update that bypass the screenlock when double press power button to launch the camera? In stock android 12 it doesn't require to unlock.
The camera app now stores its pictures in "pictures" instead of "dcim/camera". Is there a way to change this path to the old setting?
Starting with the very last 18.1 update, and continuing through now, with the 19.1 upgrade...
I can manually create shortcuts on the homescreen, but none of my apps can do it. In fact, when I did an OTA update of the last 18.1, it deleted all the widgets and shortcuts created by various apps. My browser cannot create shortcuts. Neither can the "Shelter" app, which I use to put a few "big brother" type apps into my work profile as a sandbox.
Am I missing some permission that I should change? What allows apps to create shortcuts?
Everything else works fine. Love this OS; been using it for years now!
npjohnson said:
Google Pixel 4
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 19.1 thread for the Google Pixel 4.
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.
flame​
flame - My unofficial with Google Apps/Pixel goodies included. Passes SafetyNet by default. OTA's roll roughly once a month. Support not guaranteed or implied.​
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.14
Click to expand...
Click to collapse
Perfect ROM for the Pixel 4, thank you so much!
Question though: is SOLI/RADAR working?
I can't find motion sense feature, and AOD only has the option to be on (or even off - no 'tap to wake' or motion sensing).
Cheers

Categories

Resources