[UNOFFICIAL][MAGISK MODULE] Active Edge Mod for Edge Sense Plus - continuation for patch levels 2021-01-05 and later - Google Pixel 4 XL Themes, Apps, and Mods

----------------------------------------------------------------------------
Download link here: https://www.androidfilehost.com/?fid=7161016148664789606 (2021-08-05)
** CROSSHATCH (PIXEL 3 XL) FILE MISSING FOR 2021-08-05!! ALL OTHERS ARE GOOD.
Older Releases (not sure why I'm bothering, since newer releases will install fine on older A11 system versions, but whatever):
https://www.androidfilehost.com/?fid=14943124697586362458 (2021-07-05)
https://www.androidfilehost.com/?fid=14943124697586348210 (2021-06-05)
https://www.androidfilehost.com/?fid=2188818919693794137 (2021-05-05)
https://www.androidfilehost.com/?fid=2188818919693776406 (2021-04-05)
https://www.androidfilehost.com/?fid=17248734326145747020 (2021-03-05)
https://www.androidfilehost.com/?fid=17248734326145727328 (2021-02-05)
https://www.androidfilehost.com/?fid=17248734326145726589 (2021-01-05)
Edge Sense Plus has been hidden from the Play Store by the original dev, and I believe it won't show up unless you've previously added it to your account before it was officially discontinued. As far as most of us can tell, everything seems to still work fine (for now), but I've also seen a few people ask about the app scattered across these threads across the different Pixel devices. So here is a download link to the latest version of the APK.
Edge Sense Plus v1.32.0 APK: https://www.androidfilehost.com/?fid=7161016148664805712
Again, please don't expect any support from the dev since the mod has been discontinued by the original dev. Also, I'm not sure if you'll be able to unlock the pro features, nor what will happen if you attempt to pay for the pro license. Basic functionality, however, should work fine, at least for now. Also, it seems the app no longer properly recognizes whether the Magisk / Xposed mod is correctly installed, so it will likely always give you an error when you open it. Just hit ignore.
EDIT MARCH 2, 2021: THE ACTIVE EDGE MOD / EDGE SENSE PLUS PROJECT HAS OFFICIALLY BEEN RE-CONTINUED BY JAN'S DUDE, THE LEGENDARY TEAM VIPER MEMBER, MIKHAIL (@mikalovtch)!! NO NEED FOR ME TO CONTINUE MAKING THESE - PLEASE REFER TO THE MAGISK MANAGER REPO FOR FUTURE UPDATES. IT WAS FUN WHILE IT LASTED!!
SINCE IT HASN'T YET BEEN UPDATED AS OF TODAY THOUGH, I RAN MY SCRIPT AND BUILT FOR ALL PIXEL 3 / 3A / 4 VARIANTS AND UPDATED MY MODULE. PLEASE REFER TO DOWNLOAD LINK BELOW.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~​
(now updated to also install for 3 / 3 XL / 3a / 3a XL as well)
ONLY WORKS FOR PIXEL 4 XL "CORAL" AND PIXEL 4 "FLAME"!!!!
(WON'T EVEN INSTALL ON OTHER DEVICES, SO DON'T BOTHER)
tl;DR - A continuation of the "[Discontinued]Active Edge Mod for Pixel devices" Magisk module on the Magisk Module Repository, discontinued and last released for 2020-12-05 patch level. This is simply the same exact mod applied to the 2021-01-05 patch level. PLEASE DO NOT BOTHER THE ORIGINAL DEV FOR ANY SUPPORT - THIS IS AN UNOFFICIAL MOD.
As my wife and I love and can't live without, and basically purchased Pixel 4's, for the ability to retain the (advanced, custom) squeeze function that we've become so accustomed to over our years with the HTC U11 and U12+, I've modded the current month's SystemUIGoogle.apk file with the Active Edge Mod with the developer's permission. Please DO NOT bother him with any support requests and/or questions. Edge Sense Plus (the app itself) continues to work perfectly fine as far as I'm aware, and I only aim to continue keeping the Active Edge Magisk mod up to date for as long as I have the ability to do so. Also note that the Xposed Active Edge mod will continue to work in its capacity to remap short squeeze functions, though unfortunately since 01-2021 update we lose the long squeeze functionality without an updated Magisk module.
Since I've already done the work for our phone models, I decided to share it with you all. We really love this mod, and it brings back those sweet memories of the good ol' HTC days.
Again, PLEASE DO NOT ask the official developer for any support for this mod - this is an UNOFFICIAL continuation of his work!
Cheers, and long live Edge Sense Plus!
----------------------------------------------------
* Like I said, the original Edge Sense Plus dev gave me permission to modify and share this with you guys. This is just the base Active Edge / Edge Sense Plus magisk mod with no extras. This targets SystemUIGoogle.apk, and so will not play nicely with many of Tulsadiver's mods. Though if you're a regular user of his mods, you'll probably notice he often slipstreams the Active Edge mod option into his mods and offers separate packages - you'll need to refer to them if you use his mods.
All I wanted to do was bring Edge Sense Plus's advanced functionality back to our devices, updated to play nicely with the newest security patch levels. This is literally just an unofficial continuation of the Active Edge Mod that used to be offered on the Magisk Download Repository (now marked as [Discontinued]). AGAIN, PLEASE DON'T BOTHER J TO THE 4N (OR TULSADIVER FOR THAT MATTER) FOR ANY SUPPORT - THIS IS AN UNOFFICIAL MOD!

NOTE: Download link in the OP will install mod for the current patch level down to January 2021. It will detect your current patch level and install the correct file. For earlier system builds from 2020 and prior, please use the official discontinued module on the Magisk Manager repo. I did not clone the entire Active Edge Mod repository; my unofficial repository only hosts January 2021 and later builds.
Changes:
I know, I know... I said I was done with releasing my Unofficial Active Edge Mod installer, yet here's another month's update. I might keep doing it for those that update immediately and want it a bit sooner, so long as it's fortunate enough to happen on a day when I'm able to do it relatively quickly. Since I'm building these anyway and sending them over to the dev, for now, to upload to the official Magisk repo, for now I don't mind also updating it here a bit sooner. Anyway, more on this below and some of the headache involved moving forward...
04-05-2021: Soooo... the script I wrote to churn these out as quickly as possible as Google releases the updates, relied on system image dumps on GitRip... unfortunately the domain was seized by the FBI (lol) and so it looks like the old dumper is no longer updating his Android dumps repo on GitRip. Fortunately, mikalovtch pointed me over to a new source that hosts such system dumps, and I was able to get these done relatively quickly afterwards. OP is updated with the 04-05-2021 installer now!
03-02-2021: Meant to post an update a week or two ago. Noticed the magisk module on the official Magisk repo now says [RE-CONTINUED], so there really isn't much need for me to continue updating this anymore! As a final gift, I ran my batch builder script and built the modded apk's for all variants for the 2021-03-05 patch level, and download link for the module installer is in the OP.
02-02-2021: February 2021 mod is now uploaded. Updated installer is in the link in the OP.
02-01-2021: Modified and uploaded modded SystemUIGoogle.apk files for 3 / 3 XL / 3a / 3a XL to GitHub repository. Updated Magisk installer slightly to accommodate this, and removed a few unnecessary lines. Won't make any difference if you already installed the first release.

is there a chance for the unlocked active edge app? would also pay for it but is unfortunately no longer possible

IchiroKatsu said:
is there a chance for the unlocked active edge app? would also pay for it but is unfortunately no longer possible
Click to expand...
Click to collapse
Sorry, but I can't help you with that. Like I mentioned, I'm not at all affiliated with the original developers. However, I would encourage you to check out the dev's telegram - maybe they can help you there.

sorry, but i can't use it with edge sense plus. after flash modul via magisk, edge sense plus
announced 'magisk module required'.

fRuzzy said:
sorry, but i can't use it with edge sense plus. after flash modul via magisk, edge sense plus
announced 'magisk module required'.
Click to expand...
Click to collapse
using
Can you make sure the module is activated in Magisk Manager? If you updated to February patch level, depending on the order you did everything, the module might be disabled and greyed out. Also, you're using a Pixel 4 XL (or 3 or 3a) right? Also did you reboot after flashing?

fRuzzy said:
sorry, but i can't use it with edge sense plus. after flash modul via magisk, edge sense plus
announced 'magisk module required'.
Click to expand...
Click to collapse
Click on ignore

i5lee8bit said:
using
Can you make sure the module is activated in Magisk Manager? If you updated to February patch level, depending on the order you did everything, the module might be disabled and greyed out. Also, you're using a Pixel 4 XL (or 3 or 3a) right? Also did you reboot after flashing?
Click to expand...
Click to collapse
i'm using pixel 4xl, rooted, January patch level. thanks for create share this mod

IchiroKatsu said:
Click on ignore
Click to expand...
Click to collapse
i did it, thanks you

I ended up releasing for April 2021 firmware as well... I was going to stop, but this month was a bit complicated due to the closure of GitRip, requiring some tweaks to my build script. More details in 2nd post. Anyway, I figured I'll keep releasing my unofficial version anyway, at least for the time being. I'm basically using my script to build these really quickly in an automated fashion and sending them to the dev, who then updates the Magisk repo. So the official version on the Magisk repo won't take very long to get updated anyway, but maybe for those that like to update as soon as it drops may find this thread useful.

Gah! Everything was working fine on my Pixel 3, but I just installed the updated official Active Edge module that was released today, and I'm borked. Phone either bootloops or goes to the "corrupted" screen. Am I really going to have to factory reset and start over?
Edit...Whew! What a pain. It wouldn't even get through the stock firmware flashing process successfully until I manually flashed the stock boot image to both slots first. After that I was able to boot to stock, then reboot to safe mode, re-flashing the Magisk patched image along the way, then reboot with modules disabled and get everything working again.
Has anybody successfully flashed the new Active Edge module? I'm afraid to try again, but I do miss my squeeze for flashlight.

Hey guys, sorry about this month. I'm actually not sure because I didn't generate the files this month. Been so busy with fixing up the new house I haven't communicated with the dev yet this month; heck I haven't even updated my wife's Pixel either. Anyway, I'll take a look as soon as I can (probably won't be til at earliest tomorrow) and compare the hash checksums to see if maybe there was a silly mistake somewhere. Sorry for those that ran into problems, but I'm glad you got it all sorted out! Stay tuned for hopefully some good news and an update....

CSX321 said:
Gah! Everything was working fine on my Pixel 3, but I just installed the updated official Active Edge module that was released today, and I'm borked. Phone either bootloops or goes to the "corrupted" screen. Am I really going to have to factory reset and start over?
Edit...Whew! What a pain. It wouldn't even get through the stock firmware flashing process successfully until I manually flashed the stock boot image to both slots first. After that I was able to boot to stock, then reboot to safe mode, re-flashing the Magisk patched image along the way, then reboot with modules disabled and get everything working again.
Has anybody successfully flashed the new Active Edge module? I'm afraid to try again, but I do miss my squeeze for flashlight.
Click to expand...
Click to collapse
I had the same issue after @mikalovtch updated the repo module.
I was able to adb shell in while at the white spinning G screen before the phone rebooted to corrupted message. Once in went into /data/adb/modules and rm -rf the ESP mod.
Went through this twice then notified him in the Telegram channel.
I've mostly reverted to just using ESP in non root mode (hide it from Magisk) since usually by the time we get a working mod it is time for monthly update again. It sucks to not have long squeeze, but double works (kind of a pain to pull off reliably though).
I appreciate the time that the devs put in to keeping this going, and sometimes when I'm too busy to update monthly I can still get a month or two of use from it.

Anybody try V.82 module yet?

OP updated... though Pixel 3 XL is missing. All others should work fine. If I noticed sooner that mikalovtch had already updated the official repo, I probably would have skipped, but whatever... Feel free to use the unofficial one or the official one.
newkydawg said:
Anybody try V.82 module yet?
Click to expand...
Click to collapse
Apologies again to everyone. I literally didn't get a chance to start building the files until tonight... only to realize it looks like Mikhail already updated the official repo with fixed files. Have you (or has anybody) tried the updated module yet? The comment on GitHub says that blueline and crosshatch were fixed.
Btw, unfortunately the dumps I usually source the SystemUIGoogle.apk files from didn't dump crosshatch (3 XL), or blueline (3) this month, so I manually pulled the file from the Pixel 3. But I still don't have the Pixel 3 XL file. Again, this was all before I noticed he had updated the official repo again and luckily it looks like he already took care of them. I know we're heading towards the end of the month already, but late is better than never I suppose... Can't wait til these bigger, more urgent new house projects are over with! This last week was basically dealing with 3 brand new toilets, but poorly placed water supply lines... and not realizing the new ones wouldn't fit til after one of the old ones was already taken out and thrown in the garbage. Among a million other projects... FUN!! I can't wait til I can get more than 3-4 hours of sleep in a row again, D:

i5lee8bit said:
Mikhail already updated the official repo with fixed files. Have you (or has anybody) tried the updated module yet? The comment on GitHub says that blueline and crosshatch were fixed.
Click to expand...
Click to collapse
Yes, the official v82 works on blueline. I appreciate the work you and Mikhail put into this!
I can relate on your house renovation work. I just went through one on our master bedroom and bath last year. It wasn't planned, but made necessary after the bath flooded when the tub drain seal failed. :-/ Since so much work had to be done anyway, we did some more things, including replacing faucets and the toilet.

So should we just grab the Edge Sense Plus apk online? Because it's no longer on the Play Store.

blksith0 said:
So should we just grab the Edge Sense Plus apk online? Because it's no longer on the Play Store.
Click to expand...
Click to collapse
It didn't show up for me when I searched either, but when I go here I can at least see this page with an "Installed" button:
https://play.google.com/store/apps/details?id=eu.duong.edgesenseplus

CSX321 said:
It didn't show up for me when I searched either, but when I go here I can at least see this page with an "Installed" button:
https://play.google.com/store/apps/details?id=eu.duong.edgesenseplus
Click to expand...
Click to collapse
Oh interesting. For me it's just a 404 page.

blksith0 said:
Oh interesting. For me it's just a 404 page.
Click to expand...
Click to collapse
Strange. I cleared my browser cache, and it still shows up. Are you signed into your Google account in your browser? I noticed that I get a 404 if I open it in incognito mode.

Related

UPDATED 6/17/17 [ROM] The Arko Project G3 Edition (6.0-MM-30D)(LG-D851)

Welcome to The Arko Project​
About The Arko Project: I first started this project on the LG G5 when development was still slow for that device. That version as well as a version for the LG G Stylo was never released publicly due to image burn from a botched deodex attempt, and coffee respectively. I had been on the forum's for a while at that point, and seeing the amount of devices being locked down was worrying to me. I wanted to give back to the community in some small way of my own. While learning as much as possible along the way. While also helping others do the same. I haven't had any formal education in programming or android. just what I've managed to pick up, and learn (I still am learning). It has been a long journey (as well as a humbling one), but it is not over yet. Nor do I believe it ever will be for me. There is always more to learn. That said I test run every build to make sure it's stable, and reliable before releasing.
However as with any Modification to your device: Your warranty will voided, and I am not responsible for direct or indirect damage to your device(s), and no warranty of any kind is given, or implied. You flash this rom or any other modifications linked in this thread at YOUR OWN RISK.
please read all installation instructions, and warnings. It also wouldn't hurt to read through the thread if anyone had posted.
I couldn't have dreamed of this being possible without the help of these great members of our community
@SuperR. (For his Amazing work with SuperR's Kitchen) @HPTesla for giving me tips, and information as to getting started) @Chainfire (For SuperSU) @bcrichster (For help with ota's)@cesarandres_8911 (For encouragement, and help with adding rounded corners)​
If I by chance forgot anyone please let me know, and I'll add you to the op.
Features
Deodexed* (See notes)
Debloated * (See notes)
dpi (560)
Enabled Adoptable Storage
Enabled All Apps Multiwindow
Jpeg max quality (As well as other tweaks faster/smoother streaming/scrolling etc.) (Needs some testing just for further validation)
Dithering Enabled
No Call Delay
Increased WI-FI scan interval to 300
Enabled 4way homescreen rotation (Launcher must support this feature) (Tested with Nova)
Quick power on
Disabled error reporting
Adaway, Xposed Installer, and SuperSU integrated in Settings (See notes)
Custom boot animation/removed power on sound (See notes)
su.d support
Insecured Kernal
Disabled LGincallbubble
Rounded corners (recents, notifications, and quick settings)
Increased call and media volume steps to 30
Selinux Permissive via su.d script
Removed safe volume warning
Features I would like to add
4-way reboot
remove safe volume warning
volume orientation toggle
Aroma installer with possible systemless root via magisk mod for those wishing to use apps such as Pokemon GO
UI themes
Anything else you guys/gals can think of.
Notes​
1*Deodexed: I did not personally deodex this rom, nor do I know if the Stock rom was even odexed. I pulled the system/boot images from my phone running 30d after downgrading from 30e to gain root. (If someone could enlighten me on this matter I would be grateful.) Edit: Rom was deodexed from oem.
2* Debloated Full List
Google Play Books
Google Drive
Gmail
Hangouts
LGFOTA
LG Weather
Maps
Google Play Music
News stand
Google Play Games
Tmo Visual Voicemail
Google Play Movies
Youtube
Tmobile My Account
Amazon
Tmobile TV
Tmobile Caller id
LG Browser/Email/Music
LG My Guide
LG My Wellness
Lookout
3*Integrated apps: Xposed Installer, SuperSU, and Adaway all have their launcher icon removed. I have no idea if an update will break that (Although my guess is probably) SuperSU however remains in the launcher as well as in settings. So if you don't want to see it then you'll have to hide it manually for now. SuperSU should now be hidden also. (Adaway is version 57. I got an error recompiling version 60. You can update manually if you like, but it will probably break the hidden launcher icon.)
4*Custom Boot Animation: Please be forgiving. I have very, very little graphic design experience, but managed to pull something that I think looks halfway decent that was made frame by frame, and took a considerable amount of time. (Also I ran into an issue with the phone only displaying the images after a couple of folders so there are a couple of empty ones.)
That being said this whole project has taken a considerable amount of time. I like most others work 40+ hours a week. I am open to criticism, as long as it is constructive, and done in a polite way.
Install Instructions​
1. Flash Multirom TWRP (Normal twrp gives error with updater-script) Can be found here:https://forum.xda-developers.com/lg-g3/development/multirom-v32-resurrected-d855-testers-t3147242 (Make sure you download the correct TWRP for our device D851.)
2. Make TWRP backup (Heavily suggested, but optional)
3.Perform a Full wipe (Dalvik cache, System, Data, Internal Storage,Cache) via TWRP>>wipe>>advanced wipe
4. Flash and reboot
LG incall bubble is disabled 120 seconds after boot via a su.d script.
DOWNLOAD LINKS​
https://www.androidfilehost.com/?w=files&flid=191468
SOURCE: Rom stock lg d851 MM 6.0 30d
Kernal: Stock LG MM 6.0 30d (In-secured) via SuperR's Kitchen http://opensource.lge.com/osList/list?m=Mc001&s=Sc002
Reserved#1
New build out! Screenshot updated with DL link in the op. I think I'm gonna use this post for the latest changelogs.
CHANGELOG REV2
Code:
Added Selinux permissive su.d script
Themed added icons to match stock system icon colors
Increased call volume steps to 30
Increased Media Volume steps to 30
Added rounded corners to recents, notifications, and quick settings panel
Removed safe volume warning
CHANGELOG REV3
Code:
Took LG File Manager off debloat list
Removed Permissive su.d script *See op
Fixed Ota updates (No longer uses su.d script to disable service)
CHANGELOG REV4
Code:
Updated Apps:
Cloudprint
calculator
Added Apps:
LG Quick Remote (Couldn't find the latest version so it still needs to be updated from "App Updates" in Settings if you want the latest version available for our phones.)
I'll try to see if I can't just add the update apk in the next update, but it's odexed for some reason. I'll see what I can do though.
Consider this a mini test run for updating Gapps and the like. I tried updating Google Play services and the Playstore, but got force closes. So those will still have to be updated manually I plan on updating more apps in furture updates.
Readded:
Chrome
Permissive su.d script (In preparation for hopeful approval to add Viper for android into the rom.)
Reserved #2
Reserved #3
Thanks, Bro. Nice Job!
Sent from my Resurrection Remix-M N9515 using Tapatalk
Nice. Always up for trying something new. Will give 'er a test run after work.
LG G3 D851, Fulmics v6.9 ROM, MultiROM, Tapatalk 4.9.5
bcrichster said:
Thanks, Bro. Nice Job!
Click to expand...
Click to collapse
Thanks man still got a ways to go, and a lot to learn. The encouragement however means wonders. Thanks I appreciate it.
marcdw said:
Nice. Always up for trying something new. Will give 'er a test run after work.
LG G3 D851, Fulmics v6.9 ROM, MultiROM, Tapatalk 4.9.5
Click to expand...
Click to collapse
Awesome thanks for trying it out. Let me know if you have any issues.
I'm probably let the Rom sit for a week, and make sure there isn't anything that needs to be fixed right away. I've xposed installer fc's on boot, but haven't seen one in a while. Either way it still opens, and works fine. I used it to install all my xposed tweaks.
I'll probably start working on a very basic ui theme. Mainly navbar, qs toggles notification shade etc. Then I'll look into the 4 way reboot. I've seen some old sammy threads searching on xda. We'll see if the same principle will work for lg.
Also if anyone would like to help test new builds let me know.
Will also let it sit for awhile and settle in. Preliminary go-through was okay. No issues other than that initial Xposed Installer FC.
Just want to confirm that the Xposed Framework is _not_ installed? Installer said it was not which caused me to get a little confused at first.
Now that I've had a look at what is and is not included I can reflash and setup properly. Essentially the same way as I do Nimax Slim Fit, Tekcafe, and Fulmics.
This is UX4? I forget. Last year I realized the old G3 TweaksBox themes for LP work on MM just fine. I used a few just to liven things up a bit on two ROMs running UX4.
LG G3 D851, PAC-MAN LP ROM, MultiROM, Tapatalk 4.9.5
marcdw said:
Will also let it sit for awhile and settle in. Preliminary go-through was okay. No issues other than that initial Xposed Installer FC.
Just want to confirm that the Xposed Framework is _not_ installed? Installer said it was not which caused me to get a little confused at first.
Now that I've had a look at what is and is not included I can reflash and setup properly. Essentially the same way as I do Nimax Slim Fit, Tekcafe, and Fulmics.
This is UX4? I forget. Last year I realized the old G3 TweaksBox themes for LP work on MM just fine. I used a few just to liven things up a bit on two ROMs running UX4.
LG G3 D851, PAC-MAN LP ROM, MultiROM, Tapatalk 4.9.5
Click to expand...
Click to collapse
No the framework itself isn't preinstalled. Just the new installer. I'm not sure exactly what you mean by UX4? If you let me know how I can find out. I'll let you know though. Also I never used g3 tweaksbox's theme engine myself, but if it works just let me know. I'm looking at options for managing my future themes, as decompiling, and retheming every one after an update would be tedious. Thanks for the feedback I appreciate it. ?
Sorry about the UX4 questions. Brain is scattered. I forget that some of the stock-based ROMs out there have incorporated the user interface, launcher, and whatnot from elsewhere like the G4 or G5. Also forgetting that Arko is essentially straight stock, debloated. A good thing.
EDIT: The following had all kinds of goodies, mostly G5 compatible stuff with some stock G3 compatible mods. Maybe the dev over there can help out on the theming front.
http://forum.xda-developers.com/showthread.php?t=3292164
[MOD][UI]G5 SystemUI, QSettings background MODs and Softkeys (G3Tweaksbox)
LG G3 D851, PAC-MAN LP ROM, MultiROM, Tapatalk 4.9.5
I've found this guide:https://forum.xda-developers.com/showthread.php?t=2038675
For a bunch of different samsung mods while searching for info on 4 way reboot. 4wr however is my main focus as having it could save a lot of time rebooting to recovery, and what not. I'm having issues getting a custom zip with a minor colors.xml change to test if that would work vs having to manually edit pngs & 9pngs. It flashes fine but won't boot past the animation.
I probably won't have time to look into it too much this week as I'm going to begin the process of moving, but most of my spare time if not spent working on the rom. Is spent reading about rom related things, and trying to learn as much as I can. Thank guys ?.
Thought I would post an update on the 4 way reboot progress.
I have finally managed to find the right dl links to the latest est smali/baksmali and new commands baksmalied services.jar (formally com.android.policy.jar) and found where to paste the smali resource files. Now as far as I can tell the are rather old. Probably even pre kk not sure. Assuming they work however (Not really expecting it hoping, but not expecting lol). They only issue will be finding the right GlobalAction number for the reboot button. The thread I linked to ealier said something about possibly being able to find it by tracking mreboot (have absolutely no clue.) I'm just gonna try the number listed in the guide,and go from there. If anyone knows how to find it however let me know. Thanks guys. ?
I let my phone go dead last night, and upon recharging my double tap to wake isn't functioning dt2sleep is. As well as google now isn't opening links. It grays slightly, and that's it.
I don't know if they are related, but I'm planning on hopefully releasing a new build with just minor changes. Volume steps mostly. So I may just reflash the boot.img, and see if that helps. If it does I'll make a zip, and post it here in case it happens to anyone.
I know updates have been far, and few inbetween lately. That's because I'm working on some android n dev courses I bought through xda-depot, and having to work a bit of overtime as well.
I haven't given up though just have a lot to do, and too little time to do it in. Lol. Thanks guys.
Edit: I also tried to start it up before charging and it made it to the homescreen with 1% and killed over. So that may also have something to do with it.
Edit 2: I discovered at least one other person was experiencing issues with google now as well, after a few reboots the dt2w starting working just fine. I haven't been able to finish the new build as I'm setting up a new enviroment. Got a desktop pc with a intel core 2 quad cpu 2.4 GHz 2.3GHz
5 gigs of ram, and nvidia quadro fx 570 with 256 mb dvram.
I plan on upgrading this pc quite a bit, but until it exceeds my quadcore laptop. I'll be running linux on my laptop, and windows on the desktop. Now all I need is KVM switch. Once my desktop can handle it I'll probably build with linux on a vm.
In case you're wondering I do all my apk editing/building/coding in windows.
Hey all I was hoping to have a the new build up today, but I haven't been able to make it because after setting up my new desktop the hd went bad so I had to have it replaced. I'm gonna start resetting up tonight when I get off of work. So I'll hopefully have it uploaded by Thursday, or Friday.
Edit: The vm took a little while longer to get set up, but rest assured I'm working on it. I'll get the new build up as soon as I can. Thanks guys.
New build is up guys. Enjoy!
WiFi Calling?
bgon04 said:
WiFi Calling?
Click to expand...
Click to collapse
Hi sorry for the late reply. I didn't get a notification, and my computer has been in the shop. Wi fi calling works just fine as far as I'm aware, but let me know if you run into any issues & let me know if you try it out. Thanks!
The loss of my G3's SD slot has curtailed my ROM flashing. No longer able to have half a dozen ROMs running on the phone but I still had enough internal space to try.
TAP runs fine. Data, Bluetooth, WiFi okay. Went through all the settings. All good.
GApps are ancient but that's okay I guess.
Needs some kind of file manager though. I like to setup Google later during ROM testing so I usually need to install certain tools first. Not possible via the ROM's DocumentsUI. I think the only flashable file manager I have is CM's. It might work.
About to flash ROM again with some extras and give 'er a longer test.
Oh, almost forgot. An OTA update of about 75MB came through. Not gonna take it, of course, but was surprised to see it.
ZTE Axon 7 A2017U, PureNexus ROM, Tapatalk 4.9.5

[ROM] [Unofficial] [LOS15.1] Lilly's LineageOS CookieJar

Hi everyone!
This is just my corner where I drop the builds of Lineage-15.1 that I personally use. They do contain a few smaller customisations, like a custom kernel and other goodies that I personally need. I'm posting this here in case somebody finds them to be useful.
Nooby Disclaimer:
I'm not a developer and just because I've got a thread here, doesn't mean I fully know what I'm doing when modding or building ROMs. What I publish is used by myself personally and thereby tested as daily driver. If something still breaks and your phone doesn't survive the smoke test, that's your problem and not mine.
Builds will mostly cater towards my needs if I have any special wishes with the hopes that the changes are useful or interesting for someone else as well (won't be too deep changes I think).
Some info/bugs specific to this build:
SELinux defaults to permissive
Make sure you tell OpenGapps to keep LineageOS Snap installed, Google Camera crashes.
Fails SafetyNet Test, don't use if you need that to verify.
OTA Support (Can somebody confirm that it works?.). The Updater should notify you of a new version.
Other than that, there's not much to say about it. It's LineageOS 15.1, what more could you wish for?
Download link:
http://tf2glados.dynv6.net:8080/
(It's in the LineageOTA folder)
Sources:
http://github.com/LineageOS
http://github.com/LineageOS/android_device_nextbit_ether
http://github.com/LineageOS/android_kernel_nextbit_msm8992
https://github.com/linckandrea/Pop-kernel-ether-LOS14.1-15.1
http://review.lineageos.org/
Mine mineminemineminemineminemine
Another one
It's kind of impressive you managed to miss that I post 15.1 unofficials in the 14.1 thread.
javelinanddart said:
It's kind of impressive you managed to miss that I post 15.1 unofficials in the 14.1 thread.
Click to expand...
Click to collapse
I'm going to ignore the passive-aggressiveness and just go ahead and argue that with time that my builds will deviate a tiny bit from vanilla Lineage here and there, be it only tiny tweaks and goodies like Pixel Navbar, kernel with Kali Nethunter support and OTA support. Besides, I wouldn't expect a 14.1 thread to contain Lineage15.1, now would I? Fss.
Alexandroid99 said:
I'm going to ignore the passive-aggressiveness and just go ahead and argue that with time that my builds will deviate a tiny bit from vanilla Lineage here and there, be it only tiny tweaks and goodies like Pixel Navbar, kernel with Kali Nethunter support and OTA support. Besides, I wouldn't expect a 14.1 thread to contain Lineage15.1, now would I? Fss.
Click to expand...
Click to collapse
No need to get snippy. Just commenting that I've been running builds for weeks now bringing up 15.1, and there's 40+ people in the hangouts group I made. I can't stop you from releasing builds or building from my sources (and nor do I care to), just letting you know that it's incorrect to say nobody's been building unofficials.
Sorry, I do apologise, but your comment did sound passive-aggressive even after reading over it multiple times. My point still stands though.
working like a champ but having issue with the figer print
karthikpl said:
working like a champ but having issue with the figer print
Click to expand...
Click to collapse
Working for me just fine. Just a tiny bit inaccurate as always.
http://tf2glados.dynv6.net:8080/LineageOTA/builds/full/lineage-15.1-20180401-NIGHTLY-ether.zip
Hello. I installed the UNOFFICIAL version. But the Nighly version is not. How do I install the Night version?
kinhkinhls said:
Hello. I installed the UNOFFICIAL version. But the Nighly version is not. How do I install the Night version?
Click to expand...
Click to collapse
Not sure what you are asking, but I had to override the build type branding to NIGHTLY in order to have the OTA server working. Just flash it over the old version. If you're using twrp and it doesn't want to flash, I'll have a Lineage recovery here, flashing that and then flashing the update using the lineage recovery always worked for me. http://tf2glados.dynv6net:8080/LineageRecovery/
Otherwise, just update TWRP. I tried it with the latest TWRP version just now and it works.
Download link is not working
Link is not working bro. Send me link
Quick note:-
OP is away at the moment and shall update the links upon return. :good:
Edit :- Download links are up an running.
Hello, thank you for working on this.
I flashed it yesterday and had an issue with mounting USB to my windows computer.
It worked on the first boot, and I was able to pull down the notification bar and tell it to transfer files. However on subsequent boots it did not give me such an option, although rebooting to recovery with the cable plugged in the same way mounted the device in my computer.
batp said:
Hello, thank you for working on this.
I flashed it yesterday and had an issue with mounting USB to my windows computer.
It worked on the first boot, and I was able to pull down the notification bar and tell it to transfer files. However on subsequent boots it did not give me such an option, although rebooting to recovery with the cable plugged in the same way mounted the device in my computer.
Click to expand...
Click to collapse
I haven't had any issues with that and I wouldn't consider it a build-specific bug, but I might be able to help you anyway. Plug in the phone, go to developer options and tap on "Select USB Configuration" and set it to MTP. That mostly fixes hiccups with USB modes for me. Otherwise, try replacing the cable if you're using the original Nextbit one that came with it. Mine became really unreliable soon after buying the phone, so I replaced it with a better (USB 3.1, even) cable and now it just works.
batp said:
Hello, thank you for working on this.
I flashed it yesterday and had an issue with mounting USB to my windows computer.
It worked on the first boot, and I was able to pull down the notification bar and tell it to transfer files. However on subsequent boots it did not give me such an option, although rebooting to recovery with the cable plugged in the same way mounted the device in my computer.
Click to expand...
Click to collapse
I might have found the technical reason behind it.
https://github.com/LineageOS/androi...mmit/99a8ea97e55cc7f9e28a2b7009325647110dc638
I'll rebuild when I get home, so that will include this fix.
Short note here, my Raspi server died on me again, so sorry for the dead links again. Buuut I'll be home soon, so I can get around fixing the Pi and the downloads will be up again just in time for a new build.
Enjoying the new build so far! Pretty good for me.
http://tf2glados.dynv6.net:8080/LineageOTA/builds/full/lineage-15.1-20180605-NIGHTLY-ether.zip

CalyxOS - Secure, de-Googlefied

I recently managed to bollux up my 2XL, particularly the ability to install Recovery, TWRP or any other. After trying to install a series of ROMS, I found CalyxOS at https://calyxos.org/ CalxyOS is an interesting, security-focues de-Googlefied ROM that does not require or permit a Recovery installation, nor have I been able to root it. It's installed via use of a batch file run while booted to bootloader. CalxyOS comes with a lot a FOSS software, as well as the ability to use Google services if you want them (I do). I found that the best way to get some Google items installed at the system level was to use the Aroma version of Open Gaaps 11 https://opengapps.org/ and select the minimum of what I wanted, and then using the Aroma installer delete all the included stuff I did not want to make sufficient room for the installation. There is not enough room even to install Pico gaaps if you don't do it this way. I'm using this as a 2nd phone, mostly for tracking mileage in my car, so it has a Google Fi data chip, only. I booted TWRP from my computer and tried to install Magisk, unsuccessfully. Anyway, I at least have a working phone again!
From the CalxyOS website, it looks like only Pixel 3 and up are getting updates.
calyxos rapes my battery and lacks many basic android features, touts itself as secure while not taking amny extra steps to do so, beyond that of which every non-stock rom does
wheres the hardened or at least changable webview
the app isolation?
frequent security updates?
the list goes on, this rom seems just like an excuse to sell a overpriced product, a door to door scam that reminds me of purism or apple
2022-02-11
CalyxOS 2.14.0 - Android 11, February 2022 Security update is now available for the Pixel 2, 2 XL and Mi A2.
Sadly, we will no longer be able to provide OS updates for the Pixel 2, and Pixel 2 XL. The Xiaomi Mi A2 should get Android 12 at a later date, if everything goes well.
Pixel 2, Pixel 2 XL​
This is the final CalyxOS update for these devices. Google stopped updating the Pixel 2 series as of December 2020.
Up till now, we extended these phones useful lifetimes by patching the open source components: AOSP and the Linux kernel. Linux kernel 4.4 was a long-term support kernel, but has stopped receiving updates this month. ( see https://en.wikipedia.org/wiki/Linux_kernel_version_history )
Unfortunately due to the kernel dependency, it is also not feasible to have Android 12 fully working on these devices. There are various community efforts, but there’s no fully working port as far we know.
As such, we have decided to stop updating these devices. Applications such as Chromium and microG will still continue recieving updates.
Click to expand...
Click to collapse
Like Graphene, i will not spect any upgrade anymore, even microG ........

Question Pixel 6 pro android 13 Beta 2.1.

How is it possible pixel 6 pro to be faster and smoother on a beta version than stable android 12???
Fingerprint sensor is very good, brightness is higher than android 12 specially under sun and camera is far way more derailed than android 12 stable... Why is this happening? Are they trolling us?
Presumably because this is a beta build release that is much further ahead in the current development schedule. Keep in mind that stable Android 13 releases in about two months and a week or so (August is currently the scheduled release).
It wouldn't really be a great idea in development to only start optimizing your product for stability and performance after it releases. So, that is what they are working on now; optimizing the stability, speed and performance so that they can spend the last few months of development ensuring that the new system functionality works well and is a pleasant update for us Pixel 6 users.
Also, it's important to make sure that you are releasing a great OS build - especially when that OS version's effectiveness will aid in the sales of your upcoming smartphone product that is going to launch with it (the Pixel 7 series)!
So overall, there are *Noexcusses* for being crummy with your software development and management =). Google had suffered enough with their Pixel 6 series release as they were still lacking funds in their phone development department due to a crummy lawsuit. But as a result of that issue, I'm assuming that they are shaping themselves up for that upcoming Pixel series.
NippleSauce said:
Presumably because this is a beta build release that is much further ahead in the current development schedule. Keep in mind that stable Android 13 releases in about two months and a week or so (August is currently the scheduled release).
It wouldn't really be a great idea in development to only start optimizing your product for stability and performance after it releases. So, that is what they are working on now; optimizing the stability, speed and performance so that they can spend the last few months of development ensuring that the new system functionality works well and is a pleasant update for us Pixel 6 users.
Also, it's important to make sure that you are releasing a great OS build - especially when that OS version's effectiveness will aid in the sales of your upcoming smartphone product that is going to launch with it (the Pixel 7 series)!
So overall, there are *Noexcusses* for being crummy with your software development and management =). Google had suffered enough with their Pixel 6 series release as they were still lacking funds in their phone development department due to a crummy lawsuit. But as a result of that issue, I'm assuming that they are shaping themselves up for that upcoming Pixel series.
Click to expand...
Click to collapse
I want my phone better than pixel 3xl at least on camera and still it is not. Im using pixel phones from Nexus 6p..
There is no Beta 3 yet. The latest release is Beta 2.1 which has some bug fixes for Beta 2.
More info here
biohaz55 said:
There is no Beta 3 yet. The latest release is Beta 2.1 which has some bug fixes for Beta 2.
More info here
Click to expand...
Click to collapse
Ok then Beta 2,1!
Noexcusses said:
I want my phone better than pixel 3xl at least on camera and still it is not. Im using pixel phones from Nexus 6p..
Click to expand...
Click to collapse
And it will be. Beta 2.1 (on a newly wiped 6 pro) is excellent. Battery life has settled and is more consistent, image processing is getting better and so is the overall experience.
I also have the 3 XL and I remember that it took 6 months for the device to improve. When it was upgraded to A10, it was a different phone. This happens on all Pixels/Nexus devices. Software optimization takes time and is probably more visible on Google devices just due to the way they develop and improve their software over time (just different than apple or other oems, not necessarily better or worse)
Alekos said:
And it will be. Beta 2.1 (on a newly wiped 6 pro) is excellent. Battery life has settled and is more consistent, image processing is getting better and so is the overall experience.
I also have the 3 XL and I remember that it took 6 months for the device to improve. When it was upgraded to A10, it was a different phone. This happens on all Pixels/Nexus devices. Software optimization takes time and is probably more visible on Google devices just due to the way they develop and improve their software over time (just different than apple or other oems, not necessarily better or worse)
Click to expand...
Click to collapse
Hope so... Im on beta 2.1 also and i have realised brightness improvements and charging improvements too... Battery duration on 2.1 isn't so good as Android 12 but is fine as soon as is so early Beta.
Beware if you're on Android 13 Beta 2.1. There is a Magisk update that released today, however, it prevents the phone from booting if installed. Requires a device wipe and reinstallation if you install that update =(.
(or maybe I'm just an unlucky duck lol)
NippleSauce said:
Beware if you're on Android 13 Beta 2.1. There is a Magisk update that released today, however, it prevents the phone from booting if installed. Requires a device wipe and reinstallation if you install that update =(.
(or maybe I'm just an unlucky duck lol)
Click to expand...
Click to collapse
Patching the boot image works for me on A13B2.1. Direct install may cause bootloops though. If you encounter a bootloop using direct install you can just boot into the bootloader and flash your patched Canary 24313 (or whatever you were on) and it will boot and then patch the boot image rather than using direct install with 24314. No need to wipe the device, in my experience.
I also have verity and verification disabled.
Lughnasadh said:
Patching the boot image works for me on A13B2.1. Direct install may cause bootloops though. If you encounter a bootloop using direct install you can just boot into the bootloader and flash your patched Canary 24313 (or whatever you were on) and it will boot and then patch the boot image rather than using direct install with 24314. No need to wipe the device, in my experience.
I also have verity and verification disabled.
Click to expand...
Click to collapse
You're correct here. I forgot a few words in my original comment there, haha. It should have said "if the patched boot image was installed via Magisk". Sometimes I make comments too soon after rolling out of bed LOL.
Regardless, I did a full wipe and reinstall as I hadn't done my typical device setup when I had first upgraded to 13B2.1. I usually install all updates onto both slots (a and b), however, I hadn't done that initially. So a full wipe and installation onto both slots was required by my standard practices - as I wasn't even sure which one I was currently using, haha. Anyway, I've been trying to resolve some problem with Google Phone as the Visual Voicemail hasn't been working for me. So, I had figured a full wipe and reinstallation across both slots would have definitely resolved the boot loop as well as that visual voicemail problem....but it hasn't fixed the latter... =(
NippleSauce said:
You're correct here. I forgot a few words in my original comment there, haha. It should have said "if the patched boot image was installed via Magisk". Sometimes I make comments too soon after rolling out of bed LOL.
Regardless, I did a full wipe and reinstall as I hadn't done my typical device setup when I had first upgraded to 13B2.1. I usually install all updates onto both slots (a and b), however, I hadn't done that initially. So a full wipe and installation onto both slots was required by my standard practices - as I wasn't even sure which one I was currently using, haha. Anyway, I've been trying to resolve some problem with Google Phone as the Visual Voicemail hasn't been working for me. So, I had figured a full wipe and reinstallation across both slots would have definitely resolved the boot loop as well as that visual voicemail problem....but it hasn't fixed the latter... =(
Click to expand...
Click to collapse
Here's Google's workaround for visual voicemail bug on Android 13 betas
Rolling back to a v81 release of the Phone by Google app can fix the issue
www.androidpolice.com
uicnren said:
Here's Google's workaround for visual voicemail bug on Android 13 betas
Rolling back to a v81 release of the Phone by Google app can fix the issue
www.androidpolice.com
Click to expand...
Click to collapse
Thank you for this! Unfortunately, downgrading the phone app to V81 didn't resolve the issue. I have also tried some of the other methods that were being discussed in that Reddit post but haven't had any luck with those tricks either.
I'm going to try removing myself from the Google Phone Beta next though. Worst comes to worst (if removing myself from the phone beta list doesn't work), I'll have to wait a few weeks for the next Android 13 beta update.
Woah! This is offtopic but the pictures are so good! You're lucky that you have a pixel 6 pro
NippleSauce said:
Beware if you're on Android 13 Beta 2.1. There is a Magisk update that released today, however, it prevents the phone from booting if installed. Requires a device wipe and reinstallation if you install that update =(.
(or maybe I'm just an unlucky duck lol)
Click to expand...
Click to collapse
Im not rooted sir
notnoelchannel said:
Woah! This is offtopic but the pictures are so good! You're lucky that you have a pixel 6 pro
Click to expand...
Click to collapse
On android 13 beta 2,1 photos are much better than android 12...
NippleSauce said:
Beware if you're on Android 13 Beta 2.1. There is a Magisk update that released today, however, it prevents the phone from booting if installed. Requires a device wipe and reinstallation if you install that update =(.
(or maybe I'm just an unlucky duck lol)
Click to expand...
Click to collapse
I updated to A13 beta 2.1 without a full wipe, using canary 24314 just fine. I did of course disable all modules before installing the A13 update.I also removed the -w command in the flash all bat file.
Amd4life said:
I updated to A13 beta 2.1 without a full wipe, using canary 24314 just fine. I did of course disable all modules before installing the A13 update.I also removed the -w command in the flash all bat file.
Click to expand...
Click to collapse
It seems to be a known error after clean wipe updates to the latest A13 beta build based on @uicnren 's post. According to users on the Reddit thread, the issue has to do with the beta and a current OS build miscommunication with the phone carriers in the United States. So, if this is truly the case, users experiencing this issue won't have it resolved until the next beta build release (or later). Time will tell =)
I'm abut ready to jump in and load the 13 beta on my P6 and wanted to know it there are any hotspot issues since that would be the one deal breaker for me.
Does anyone know When would be next Beta update?
Thanks...

Development [CLOSED][EOL][Odin Installable][ROM][OneUI 4.1] RayOS S21FE for Galaxy A52s 5G

RayOS S21FE Port for Samsung Galaxy A52s 5G​Here we go again. I can't live without S21FE system, so now I ported it to my newest device, the Galaxy A52s 5G. It was a little bit more tricky with limited options when it comes to recovery, but it's now available. Since TWRP isn't released yet, I packaged it together to flash with Odin. I've tested it myself and it works for me, but as everything in XDA in uncertain, flash at your own risk.
Code:
* Warning, your warranty is now void.
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about flashing this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you. HARD!
Supported variants!​
SM-A528B
Features!​
Based on S21 FE June firmware (G990U1UEU3CVF2)
Debloated
DeX working (wireless and wired to PC via USB)
Live Blur
Allow screenshots on secure apps
Fixed Private Share and Secure Wifi
Fixed Secure Folder
Fixed Smart View (normally broken on rooted devices)
Smart Widgets (Already on S21FE FW by default)
Object eraser (Already on S21FE FW by default)
Remaster picture (Already on S21FE FW by default) [Avoid updating any app related to Gallery or you might lose this option]
Edge Lighting fully enabled (Already on S21FE FW by default)
Higher audio quality (Disabled DRC, which deeply compresses audio)
High-End Animations (Already on S21FE FW by default)
Enhanced processing (this also probably doesn't do anything, but give it a try) (Already on S21FE FW by default)
CSC Features like:
Stock call recording
Speed meter on status bar
Spam call blocker
Added camera privacy toggle to remove camera access across apps (Already on S21FE FW by default)
Added HDR10+ lines (improves effect in HDR content)
Screenshots!​Soon...
Sources!​I decided to show my work so to speak on GitHub. You can see the list of all the apps I removed and all the lines that were added to camera and floating features. Feel free to take a look and make pull requests if you want me to add something on potential future releases.
https://github.com/ShaDisNX255/RayOS-S21FE-Port
Kernel source: Samsung Open Source
Bugs!​
Remaster picture breaks if you update system apps with Galaxy Store. I still don't know the exact app update that breaks this (it's not Gallery) but you have been warned.
SSRM Warning on every reboot. You can bypass this by flashing the SSRM Warning Removal magisk module in this thread. Will hopefully add this fix natively on future updates
You tell me
Changelog!​
18/July/2022: Release based on June S21 FE Firmware (G990U1UEU3CVF2)
Links!​
RayOS S21FE for Galaxy A52s 5G
Odin 3.14.1 (Give thanks in the original post)
Instructions!​
This will wipe your phone, including media. So backup any media you may have on the phone.
Extract all the files using 7-Zip
Make sure you've correctly unlocked your bootloader
Reboot phone into download mode
Place each AP, BL, CP and CSC in their respective locations
Flash
Odin will reboot your phone once complete
Done
Recover camera!​Samsung software locked the camera on the a52s for some reason. It's easy to bypass, just change the props to anything else [A52 4G should work, but you can chose literally anything other than A52s to make it work]
For those who are less knowledgeable on how to do it, here's a quick guide:
Install the Magisk app from the official GitHub releases (The fw is already Magisk patched, so just installing the app normally should give you root access)
Download the Magisk Props Config Magisk module from their thread (make sure you give them a like on the thread)
Install a terminal emulator (Termux recommended from Playstore)
Install the Magisk Props Config module using Magisk
Reboot
Open your terminal emulator and type su to give it root permission
Type props and it should take you to the props menu
Select Edit device fingerprint (option 1)
Select Pick a certified fingerprint (option f)
Select Samsung (option 26) and select any model you want (It can be Android 11 or 12, doesn't matter)
After selecting a model, it should ask you to reboot
After reboot, your camera should work. If it doesn't work, force stop it and delete any data it may have already saved and then try again.
Credits!​@SuperR. For his Super R's Kitchen which you can find here: https://forum.xda-developers.com/ap...dows-linux-superr-s-kitchen-v3-0-0-0-t3601702
@topjohnwu for Magisk
@SkylinesHD for his continued work in the A72 scene and continuing to share his knowledge
@ricci206 for various fixes and mods posted here: https://forum.xda-developers.com/t/mods-samsung-not-android-mods-collection-exynos.3772017/
@Pokemetti2 for discovering the method to bypass camera by changing props
@ All my testers
@ Samsung for the firmware
@ To users like you!
If you feel I missed you, please give me a PM so I can add you
Join our Telegram group​
Code:
Check out the latest projects on our Telegram group, where we share our advancement on new things and try to help as best as we can.
For anything already released, please ask here in XDA
Link: Telegram Group
Follow our Telegram update channel​
Code:
Check out the latest updates on our Telegram Channel. Here you'll find the latest news in regards to custom releases (ROMs, TWRP, etc)...
For anything already released, please ask here in XDA
Link: Telegram Channel
Android group in spanish
Link: Grupo Android​
FAQ​Q: Will this work on A52 4G or A52 5G?
A: No, I included A52s 5G specific vendor with hw libs. This will only work on A52s 5G. There is already an A52 4G version here: https://forum.xda-developers.com/t/...s21fe-port-for-galaxy-a52-sm-a525g-f.4454855/
Q: Will this work on A73?
A: I have no clue. I've been told HW is very similar with a few lib exceptions but I honestly have no interest on supporting this device. Anyone else is free to try and flash and fix it for A73, you've got my support.
Q: How can I report a bug?
A: Try and be as detailed as possible on how you encountered the bug. If you can include a logcat then even better. The more information provided the more likely it is to get the bug fixed.
Enjoy guys!
Sorry if you get bombarded with bloat at initial set-up. I deleted the apps but they still show up. The good thing is that 90% of them are uninstall-able by long pressing and installing them from home
Hope I can get them fully removed on future updates.
Yoooo a Custom ROM pooog! OneUI based, but at least something! Not gonna flash right now, I'm on vacation and don't have access to Odin, but maybe later.
HAHA second, going to give this a try, keep you informed....
Dohh thanks man i will try it tomorrow
I already tested the og version of this and it was really good. Fantastic work. Follow instructions and try it you'll like it! Dex ftw!
I have this installed, gone through most of my prefered setup steps. Only thing I've noticed so far is connection to pages and setups requiring connections is extremely slow. Google timed out. XDA timed out. Whatsapp was slow with verification code and accessing drive backup. Otherwise all else is going ok so far.
bobfrantic said:
I have this installed, gone through most of my prefered setup steps. Only thing I've noticed so far is connection to pages and setups requiring connections is extremely slow. Google timed out. XDA timed out. Whatsapp was slow with verification code and accessing drive backup. Otherwise all else is going ok so far.
Click to expand...
Click to collapse
Give it a few minutes to settle. Usually it should take about 10 minutes for everything to pick up.
ShaDisNX255 said:
Give it a few minutes to settle. Usually it should take about 10 minutes for everything to pick up.
Click to expand...
Click to collapse
I'll let thing settle for a few days.
Edit: found the reason. An ad blocker app I installed added a vpn entry in my phone. I uninstalled the app and presto all working good now.
Cool. Very complete tutorial. Tnx bro
app lock ?
sahil chandel said:
app lock ?
Click to expand...
Click to collapse
No
Edit: Maybe in a future release.
Can I flash it over stock 11? I have Polish PRT, which seems to be OXM.
Just got device and dunno what to start with - stock XEO rooted or this?
Question is if it will be maintained, so any updates will be available
bobfrantic said:
I'll let thing settle for a few days.
Edit: found the reason. An ad blocker app I installed added a vpn entry in my phone. I uninstalled the app and presto all working good now.
Click to expand...
Click to collapse
Why not just try Adaway? Been working awesome since like forever.
ch3mn3y said:
Question is if it will be maintained, so any updates will be available
Click to expand...
Click to collapse
I'll try to maintain it but don't expect monthly security updates. It's such a pain to try and release updates monthly on my part.
ShaDisNX255 said:
I'll try to maintain it but don't expect monthly security updates. It's such a pain to try and release updates monthly on my part.
Click to expand...
Click to collapse
No need to monthly. It's already half a year as I'm updating my Note 20 Ultra to A12 of Ketans rom xD
But sometimes, once a while, updates could happen
"Recover camera!" - it should happen on all devices, or not?
It's just that when I launched Camera right after first boot and setup it gave me fail message, but since 2nd launch of the app it works fine and I'm not sure if I still should follow this procedure or I'm just one of the lucky ones that my camera is nor broken?
ch3mn3y said:
"Recover camera!" - it should happen on all devices, or not?
It's just that when I launched Camera right after first boot and setup it gave me fail message, but since 2nd launch of the app it works fine and I'm not sure if I still should follow this procedure or I'm just one of the lucky ones that my camera is nor broken?
Click to expand...
Click to collapse
Hard to tell since we don't know the exact culprit of losing the camera. If camera works for you then you can skip this. But, if you want to pass safetynet this will be necessary since there is a fingerprint miss-match between system and vendor.

Categories

Resources