Database Info

[APP] VM Heap Tool 2.4.1 [28/02/12]

Description
I wrote a small application to allow easily changing the VM heap size (no more adb pull, edit, adb push). People on CM ROMs may be familiar with a similar option, but here is a little tool for those who are not running CM. As it modifies a variable which can affect the stability of the system, be careful with how you use it More about the VM heap size is written in the application itself. And of course, if I made any mistakes or if something is incorrect please correct me.
Requirements
root
system write
busybox (1.17.x recommended)
Appearing In
Japanese Jellyfish (ZTE Blade/Orange San Francisco)
If you wish to bundle this application in your firmware feel free to, but let me know if you do and please link back to this page
Download (Android Market):
{
"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"
}
Translating VM Heap Tool
English files which can be translated have been attached (txt files), and the following fields which I will mention do not need to be translated. Once you translate something you may just attach the files in your post or add them in code tags. Of course please mention the language that you translated it to so I can appropriately add it to the application and update.
Do not translate: heapSizeUnit, aboutHeap, defaultHeap, currentHeap, version, thread, heapSizeValues. These just hold key values which should not be translated. Also please don't translate "RPLACE" inside the texts, as this is replaced inside the application on run-time.
Values are stored as
Code:
<string name="aboutHeapTitle">What is the heap?</string>
where the string's name is clearly defined, "aboutHeapTitle", and the value which should be translated is inside the <> and </> tags. Values which are used in similar situations will have a common prefix, for example:
"progress..." - used on a progress dialog to display the message
"toast..." - the little grey messages that you get at the bottom of your screen and with which you can't interact
"dialog..." - used as the title on a dialog box
and so on...
Thank you to all those who are willing to help, your contributions will be noted

great app, wont have to manually erstart on droid inc. wont restart when pushing the button.

ACD168 said:
great app, wont have to manually erstart on droid inc. wont restart when pushing the button.
Click to expand...
Click to collapse
Thanks, so the Incredible has the same problem as the Desire then... If you install ROM Manager it will restart. I'm afraid that has something to do with superuser and how the phone is rooted (correct me if I'm wrong), so some devices will restart while others will not. Sadly Google doesn't allow applications to restart the device, so it has to be done in a roundabout way which may not always work...

Awesome, now everyone can break apps by lowering the heap below the expected 24 megs!

khaytsus said:
Awesome, now everyone can break apps by lowering the heap below the expected 24 megs!
Click to expand...
Click to collapse
Yes, but I hope that most people will be smarter and try to use something like 32

The "apply" and "quit" box cover the "new heap size" box on hTC Hero

skymera said:
The "apply" and "quit" box cover the "new heap size" box on hTC Hero
Click to expand...
Click to collapse
OK, thanks for letting me know. I'll see what I can do about it, but for now you can use your trackpad (or w/e it's called) to move the focus on the button and press it.

skymera said:
The "apply" and "quit" box cover the "new heap size" box on hTC Hero
Click to expand...
Click to collapse
Should be fixed now with version 1.1, as well as support for Android 1.6 and above. Apologies that it took so long.
Icon help, anyone...?

Very nicely done!!!
Thanx!!!

The app is force closing on startup on a rooted orange San Francisco (ZTE-Blade) with stock rom.
Andy.

g1dtf said:
The app is force closing on startup on a rooted orange San Francisco (ZTE-Blade) with stock rom.
Andy.
Click to expand...
Click to collapse
Do any other rooted apps crash, such as Root Explorer, ROM Manager, etc?

Rom Manager and System App Remover both run ok, not got Root Explorer so can't try that.
Andy.

martino2k6 said:
Do any other rooted apps crash, such as Root Explorer, ROM Manager, etc?
Click to expand...
Click to collapse
Forced close for me to on ZTE-Blade Stock/Root.

What happens if you write the following two commands in a terminal emulator or adb?
Code:
ls /system/bin/su
ls /system/xbin/su

If you have rooted the san fran with stock rom and this will not work, root again. Worked for me no probs, even if it says you are rooted. Just root again. It appears that when the San Fran is turned off then on, it unroots (with original rom" Well, that is what I have found after testing. I have stock rom rooted and have picked out all the Orange "tat"
Hope that helps.

System Write Required
Just tried running the app, but ran into an error: "System write required". I have root, adb is installed and recognize Android is read only by default, so I assume that I have to change permissions to include write?

Guilden_NL said:
Just tried running the app, but ran into an error: "System write required". I have root, adb is installed and recognize Android is read only by default, so I assume that I have to change permissions to include write?
Click to expand...
Click to collapse
You can't change that without using a rooting method which unlocks NAND on your device. The application already remounted the partition to write, but wasn't able to write to it because you most likely don't have NAND unlocked.

martino2k6 said:
You can't change that without using a rooting method which unlocks NAND on your device. The application already remounted the partition to write, but wasn't able to write to it because you most likely don't have NAND unlocked.
Click to expand...
Click to collapse
Well guess us Slide owners can't use this until we have s-off. No system r/w for us yet

No love on the MyTouch 3G getting NAND unlocked for Write. Ah well, the MT3G is truly a dog so I am not going to spend anymore time with it. It'll do the job for now, and I use the Nexus One as my main phone anyway.
Thanks for the tip though! At least I know where the issue is on this device.

kapslock4 said:
If you have rooted the san fran with stock rom and this will not work, root again. Worked for me no probs, even if it says you are rooted. Just root again. It appears that when the San Fran is turned off then on, it unroots (with original rom" Well, that is what I have found after testing. I have stock rom rooted and have picked out all the Orange "tat"
Hope that helps.
Click to expand...
Click to collapse
Didn't work but used clockwork and installed custom ROM and worked
Sent from my BladeVillain using XDA App

[TUT][ANDROID]Lockscreen Change

This is a guide in how to change the lockscreen/wallpaper image in a ROM. Read to the end 4 a surprise.
====================
Procedure:
====================
1. Go to system/framework
2. You'll find an apk called framework-res.apk
3. Change extension to .apk.zip & extract it(7-zip preferably) then search for image of default lockscreen it may be called keyguard_default_wallpaper & also default wallpaper
4. Change it to any image as long as you change to the same [HIGHLIGHT]name[/HIGHLIGHT] & [HIGHLIGHT]type[/HIGHLIGHT] of the original
Note: to change the [HIGHLIGHT]type[/HIGHLIGHT] of ur preferred image open it in paint and press save as (for example jpg)
5. Add the folder to archive in 7-zip then change name to framework-res.apk.zip
6. To remove .zip format open it in 7-zip go back & rename to remove .zip at the end
7. Copy framework-res.apk to system/framework & replace it
8. Voila..
{
"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"
}
On Custom ROM changing a video tutorial also set if u have trouble catching up with the guide
So today I made a PACK Wallpapers with Wallpapers I liked most and saved, has 50 Super Gorgeous Wallpapers and legal, no prints, why, prints for? '-' Discover the solo Wallpapers : D by Extreme Tiago
Links
Mediafire
(NOVO) MinhaTeca

sparklingneo23 said:
This is a little tutorial in how to change the lockscreen for every mobile its controversial. Doesn't need a scientist to figure it out
I Don't think it works on stock R0M tho
REQUIREs R00T
**********************************
1. Open any root explorer that u have
2. Then go to /system/wallpaper
3. Copy your desired lockscreen image to that folder
4. Change lockscreen_default_wallpaper.jpg to lockscreen_default_wallpaper.jpg1
5. Rename ur image to lockscreen_default_wallpaper [N0TE: The default is .jpg]
6. Change Permissions to rwxrwxr-x
7. Go to system settings under security choose lock screen options. Enable anything then disable it to update ur lockscreen
8. Voila..
Im gonna upload some cool lockscreen images that I have. Link is down below. Like is much appreciated guyz&Thanks...
Click to expand...
Click to collapse
the problem is dash rom doesn't include the app in changing lockscreen wallpaper
the developer wanted it to be bloatware free
so it's not working

Brian_SGW_CM9 said:
the problem is dash rom doesn't include the app in changing lockscreen wallpaper
the developer wanted it to be bloatware free
so it's not working
Click to expand...
Click to collapse
I have S5301 with Dash R0M & it worked and if it doesn't just do this after changing lockscreen & permissions open cwm and clear cache partition&dalvik cache

sparklingneo23 said:
I have S5301 with Dash R0M & it worked and if it doesn't just do this after changing lockscreen & permissions open cwm and clear cache partition&dalvik cache
Click to expand...
Click to collapse
but what do you mean by going to security page that thing?
i dunno how
can you be specific?

Brian_SGW_CM9 said:
but what do you mean by going to security page that thing?
i dunno how
can you be specific?
Click to expand...
Click to collapse
go to settings
then go to security
change screen lock to swipe then go back u will see "lock screen options"
then for eg. enable/disable shortcuts then go back so that its updated
keep me posted

sparklingneo23 said:
go to settings
then go to security
change screen lock to swipe then go back u will see "lock screen options"
then for eg. enable/disable shortcuts then go back so that its updated
keep me posted
Click to expand...
Click to collapse
alright i will try tonight

GTS5301 Screen don't lock
Can anyone help. My gts5301 screen don't lock. Also, when device boot up use to request pin, now it don't. I checked, the settings is proper. Can anyone help me fix this please.

[GUIDE] Make softkeys smalled ROOT required

First of all. Thank to byrdmang2 as he helped me out to achieve this.
Honestly i think that the softkeys embeded in the screen is a waste of screen area. So i like them smaller. Here's a screenshot of the final result. This guide is for KitKat, i guess you can make it work on 4.2.2 with GravityBox for JB.
{
"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"
}
What you need:
- Moto x (obviously)
- ROOTED
- Xposed Framework
- Gravity Box Module
1) Backup your current ROM in custom recovery.
2) Download Xposed Framework here:
http://dl.xposed.info/latest.apk (original thread in http://forum.xda-developers.com/xposed/framework-xposed-rom-modding-modifying-t1574401) I recommend you to read the whole post.
3) Install it and reboot.
4) Download Gravity box here:
http://forum.xda-developers.com/xposed/modules/app-gravitybox-v2-9-1-tweak-box-android-t2554049 (download in the 2nd post, still read the whole post)
5) Install it and reboot
6) Open gravity box and go to "Navigation Bar Tweaks"
7) Turn the Master Switch ON and enable navigation bar.
8) In the bottom there's a section named "Dimensions" there you can set the height and width (my setting is in 65% but you can make it as small as you like)
9) Reboot
10) Enjoy!

Does anyone know how to make the softkeys as dots?
MOTO X SLAPPED

[email protected] said:
Does anyone know how to make the softkeys as dots?
MOTO X SLAPPED
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=com.janis605.softkeyz

I disable mine completely and use pie controls instead.

nhizzat said:
I disable mine completely and use pie controls instead.
Click to expand...
Click to collapse
Yup. This is what I do as well. I edit the build.prop file and take the navigation keys completely out. Then I install LMT Pie controls. Although, in the past it was always a PITA doing a factory reset because the navigation keys don't come back. I did however remedy that with creating a flashable zip of LMT that can be done via TWRP. It restores your Pie controls as you had them set.

good tip i will make a guide of how to add the menu button in nav bar of stock rom editing the SystemUI

It's actually fairly easy. All you do is add the line: "qemu.hw.mainkeys 1" to the build.prop and it removes the Nav keys.
I've been using Build Prop Editor from the Play Store for a few years now and it works well.
So, if you are using that app it would look like this:
Property Name = qemu.hw.mainkeys
Property Vaule = 1
Then save it and reboot your phone. Just remember if you do a factory reboot or take an update you will lose your PIE controls and will need to remove the "1" and change it to a "0" to get your Nav keys back. Or, do like I did and use App2Zip and make LMT Pie Controls flashable so you can restore them via recovery. Otherwise you'll need to redownload and reinstall it.

thanks a lot, looks great at 65%

yaldren said:
thanks a lot, looks great at 65%
Click to expand...
Click to collapse
No problem man

The Tallest said:
It's actually fairly easy. All you do is add the line: "qemu.hw.mainkeys 1" to the build.prop and it removes the Nav keys.
I've been using Build Prop Editor from the Play Store for a few years now and it works well.
So, if you are using that app it would look like this:
Property Name = qemu.hw.keys
Property Vaule = 1
Then save it and reboot your phone. Just remember if you do a factory reboot or take an update you will lose your PIE controls and will need to remove the "1" and change it to a "0" to get your Nav keys back. Or, do like I did and use App2Zip and make LMT Pie Controls flashable so you can restore them via recovery. Otherwise you'll need to redownload and reinstall it.
Click to expand...
Click to collapse
I believe it needs to be...
Property Name = qemu.hw.mainkeys
Property Value = 1

edthesped said:
I believe it needs to be...
Property Name = qemu.hw.mainkeys
Property Value = 1
Click to expand...
Click to collapse
That's what I said. You only make it a 0 if you want the Nav keys back.

The Tallest said:
That's what I said. You only make it a 0 if you want the Nav keys back.
Click to expand...
Click to collapse
Yes but it should be MAINkeys not keys as you have written, at least thats what I needed to do to get it to work.
Sent from my SM-P600 using Tapatalk

edthesped said:
Yes but it should be MAINkeys not keys as you have written, at least thats what I needed to do to get it to work.
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
Oh, I see. Yeah, in the first line of my post I have it as "mainkeys" and then when I broke it down line by line later on in the post it just says "keys". I'll correct it.

Upper side of home screen so empty

Just updated my S7 G930F and my screen looked like this:
{
"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"
}
Changed the resolution of my screen, but nothing changed.

? So move something up there?

*Detection* said:
? So move something up there?
Click to expand...
Click to collapse
Can't move anything, it is the limit of screen.

Sure it's not the size of the weather widget causing it?
Remove weather widget and try move something over there
Or long press the homescreen > settings > grid size, change to 5x5

*Detection* said:
Sure it's not the size of the weather widget causing it?
Remove weather widget and try move something over there
Or long press the homescreen > settings > grid size, change to 5x5
Click to expand...
Click to collapse
Removed the weather widget, moved another app there and changed the grid, but it's still the same.
By the way this happened after the update.

I've seen on Reddit people complain the same. It happened after the update. I didn't see the change because I am using Nova

PalmCentro said:
I've seen on Reddit people complain the same. It happened after the update. I didn't see the change because I am using Nova
Click to expand...
Click to collapse
So isn't there any solution without rooting and flashing stock or custom ROM ?

Not seeing the problem with the latest update & TouchWiz 6.1.33

Turkish007 said:
So isn't there any solution without rooting and flashing stock or custom ROM ?
Click to expand...
Click to collapse
You don't need root to use Nova

*Detection* said:
Not seeing the problem with the latest update & TouchWiz 6.1.33
Click to expand...
Click to collapse
I do see the issue on mine (Changed back to TouchWiz to check it out)

*Detection* said:
Not seeing the problem with the latest update & TouchWiz 6.1.33
Click to expand...
Click to collapse
Maybe i should update only TouchWiz manually if that is possible ?

Turkish007 said:
Maybe i should update only TouchWiz manually if that is possible ?
Click to expand...
Click to collapse
You can try, but depending on which security update patch you're on, it might error out with a package name conflict, you have to wait for a new update from Samsung, then on first boot you can install updated apps
If you haven't rebooted since the last update it might still work, grab the updated TouchWiz from apkmirror.com
Have you tried clearing Data from that settings storage page on your screenshot? (It'll reset TouchWiz back to default and lose any customisations you've made, app shortcuts, folders etc)

*Detection* said:
You can try, but depending on which security update patch you're on, it might error out with a package name conflict, you have to wait for a new update from Samsung, then on first boot you can install updated apps
If you haven't rebooted since the last update it might still work, grab the updated TouchWiz from apkmirror.com
Have you tried clearing Data from that settings storage page on your screenshot? (It'll reset TouchWiz back to default and lose any customisations you've made, app shortcuts, folders etc)
Click to expand...
Click to collapse
Rebooted many times, installed different versions from apkmirror.com and reset the TouchWiz to factory, but nothing changed.

Turkish007 said:
Rebooted many times, installed different versions from apkmirror.com and reset the TouchWiz to factory, but nothing changed.
Click to expand...
Click to collapse
Very weird, all I can suggest is flashing back to the previous firmware and waiting for the next one, report the problem to Samsung via Twitter or something and hope it's fixed in the next update

General [GSI] Crdroid 8.6 For J716F

Hello everyone!
I got this device last year and always wanted GSI to run properly in the device. In other guide shows GSI can be properly installed however, it rendered wrong rotation and sound sometimes muffled. I want to get rid ZUI 12/13 because notification problem and suspicious with Chinese rom. With GSI we can have long term device support and security. I am using stock recovery only and stock fastbootd. Root with magisk is sometime hit or miss. I managed to fix with a ported miui vendor img and simple build.prop alteration.
Prepare:
Working device
Unlocked bootloader
Win7/8/10/11 (installed FastBoot driver)
Make sure to be based on the ZUI_13.0.430 version (link attached)
Download GSI J716F script.
Type C dongle to mouse. (needed)
Steps:
1) Restore with Qfil to ZUI_13.0.430 (link attached)
2) Download and extract GSI J716F script.
3) Reboot your device to fastbootd with adb reboot fastboot.
4) Run gsi system flasher for j716f only.exe and press 1. On next screen, press any button. Connect your device until it restore.
5) Do factory reset in recovery mode then reboot.
6) Once system is rebooted. Connect type C dongle with mouse to the device and finish the setup. Please note that rotation and touch is not in sync.
7) Install magisk and make sure proper root. Install build.prop editor. (link attached)
8) Open build.prop and grant superuser access. Add entry ro.surface_flinger.primary_display_orientation at first column and ORIENTATION_270 at second column.
8. Save dan reboot.
9. Everything is working now but bare in mind you need to install some magisk module to get proper sound manager, safetynet fix, AOD support and auto brightness fix from Y700.
What is wroking:
1. Wifi
2. Bluetooth
3. Brightness adjustment (Auto brightness need magisk module)
4. 60Hz/90Hz refresh rate
5. Camera, flashlight and face unlock
6. Working sensors
7. Screen rotation
8. Dual speakers
9. Linear motor
Bug: d2tw and flip screen
Please tell me other bugs
Download : https://drive.google.com/drive/folders/1F4oQflyK6PgfnstJacFOPGaQzZMmJyfQ?usp=sharing

Once root and magisk is properly installed. You can install several magisk module to fix, play store verfication, auto brightness, sound manager and APTX (HD) module for bluetooth.
1) Install each modules.
2) Reboot.
Install these 2 apk to get better camera and proper AOD support
1) Install trebleApp(1).apk
2) Gcam MGC_8.1.101_A9_GV2b_snap.apk
3) You can disable the stock camera app.
In case you want to try other gsi system instead of CrDroid 8.6 prepped. You can simply replace system.img in gsi j716f scipt.zip\gsi j716f scipt\bin\system\system.img.
See the difference.

Reserved

is L1 working?

lordzinh said:
is L1 working?
Click to expand...
Click to collapse
Nope.

Thanks for this...
I hate ZUI, been wanting to try GSI for a while, just didn't want the bugs...
This looks like it's mostly working now .

gunalarix8 said:
lease tell me other bugs
Download : https://drive.google.com/drive/folders/1F4oQflyK6PgfnstJacFOPGaQzZMmJyfQ?usp=sharing
Click to expand...
Click to collapse
Some files on the "3 Tools folder have 0 bytes size" could you reupload them
{
"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"
}

Please remove double post

Awesome work, thanks so much. Hoping to try this soon, how's the battery life been though compared to stock?

eDooM85 said:
Some files on the "3 Tools folder have 0 bytes size" could you reupload themView attachment 5730137
Click to expand...
Click to collapse
sorry for late reply, files has been updated. thank you

gunalarix8 said:
sorry for late reply, files has been updated. thank you
Click to expand...
Click to collapse
Thx I'll try to install a GSI this weekend.

I have been waiting for this, looks like it is mostly working. saw the video too.
thank you for doing this. I will try this because I hate ZUI

gunalarix8 said:
lease tell me other bugs
Click to expand...
Click to collapse
Just installed it, Look good so far just a couple of question:
How did you enable Linux SE?
also how do you customiz/disable this bar?

eDooM85 said:
Just installed it, Look good so far just a couple of question:
How did you enable Linux SE?
View attachment 5736353
also how do you customiz/disable this bar?
View attachment 5736359
Click to expand...
Click to collapse
We cannot enable selinux, however we can disable the notification in security.
I dont know how to customize the naz bar.
How is the system? Fully working now?

gunalarix8 said:
We cannot enable selinux, however we can disable the notification in security.
I dont know how to customize the naz bar.
How is the system? Fully working now?
Click to expand...
Click to collapse
the only thing complicated is the setting up part without touch control (my mouse was also detected as a keyboard) and pretty much I had to config without conecting to the internet (couldnt enter my wifi password),
but after the "build.prop" step, everything else is working fine so far

gunalarix8 said:
We cannot enable selinux, however we can disable the notification in security.
I dont know how to customize the naz bar.
How is the system? Fully working now?
Click to expand...
Click to collapse
Just an update, streaming apps just give errors, I tried Disney+/HBO Max/Paramount only youtube works fine, that's a deal breaker for me , I will try other GSI

eDooM85 said:
Just an update, streaming apps just give errors, I tried Disney+/HBO Max/Paramount only youtube works fine, that's a deal breaker for me , I will try other GSI
Click to expand...
Click to collapse
Isn't that because the widevine level (DRM) is wrong due to the unlocked bootloader?
I think all GSI roms will suffer the same problem... unless someone knows how to fix it with a magisk module or something ... as I they all need an unlocked bootloader..
Other than the DRM issue how does itbrun?

tinybilbo said:
Isn't that because the widevine level (DRM) is wrong due to the unlocked bootloader?
I think all GSI roms will suffer the same problem... unless someone knows how to fix it with a magisk module or something ... as I they all need an unlocked bootloader..
Other than the DRM issue how does itbrun?
Click to expand...
Click to collapse
The problem it's not widevine Lv1 with Lv3 you can view content, the diference is that you can see it only in SD (480p) right now just throws an error loading content for example disney+ show this:

Do you know if OTA updates will work with this method? Or would you have to manually set everything up again.

gunalarix8 said:
With GSI we can have long term device support and security.
Click to expand...
Click to collapse
You say you care about security but you're okay with selinux in permissive mode?
I have just tried this but I'm not convinced this is a secure rom. Theres this chinese app that randomly appeared and dissapeared. It's called com.iflytek.inputmethod and is made by iFlytek, a chinese state owned company which has been sanctioned by the US for spying.
I'm reverting to another GSI without autorotate.