Database Develop

[ROM] GladiAtrix2 v4.2.3 (For 1.57 - CWM - Stable Release - 4/13/2011)

Update 05/10/2011: So, at this point I've just fallen too far behind the curve, and it doesn't look like I will be updating GladiAtrix any further. I'll still support v4.2.3 for 1.57 (which is pretty stable, and almost all the issues I've seen users have up to this point are the installation). I may at some point throw something together for myself to use and release it (as I don't care for the themes/mods of GingerBlur/GreyBlur), but at this point I'm doing all the mods manually and have no current plans to make a flashable zip out of it.
GladiAtrix 2 for 1.5.7 v4.2.3 CWM​News and Important Info - READ FIRST
{
"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"
}
Looks horribly out of place I know ​
04/14/2011 @ 10:00am: Download links are fixed. Sorry all! As I stated in my last post, I will be unavailable for the next few hours. I DO see your questions and I WILL answer them. Please be patient, this isn't my full-time job and I have other things that need my attention today. Thanks!
04/13/2011 @ 11:17pm - NOTICE on theme: The THEMED version does not have reboot/recovery. I've been too busy working out the other kinks to add it in. The NOTHEME version is just like v3 and older, with the reboot/recovery options intact, as well as all the other changes up to this point. That is the only difference between the two.
All the bugs with the fingerprint scanner, wifi defaulting to on, custom keyboards not working, etc. etc. should all be resolved. Please PM me or reply to the thread if you have any issues.
Version 4.2.3 is going to be considered base from here on forward. It will create a backup of all the files it changes and copy them to the root of the internal SD card. PLEASE copy this backup to some place safe. Going forward, all updates will be released on top of 4.2.3, and will create sequential backups of any new files changed, if there's a need to back them up. It does not have any feature updates since 4.2.1, just many bug fixes.
04/13/2011 @ 11:00am(ish) - NOTICE on Reboot/Recovery power menu options: These are currently removed. I added a theme, and I haven't had time to add reboot/recovery options to it yet. If someone who knows what they're doing would like to add them and send me the updated files, it would certainly expidite the process as I'm not even sure how I got them working in the first place on v1-3. Screenshots will be in the second post as soon as I get a moment to upload some.​History and SummaryCWM finally released! Sorry for taking so long with it, I'm very picky about my work and wanted to test EVERYTHING and make sure it was all working as it was supposed to. I hope the extra effort pays off and nobody has any issues with this
I've removed the script version as there's no need for it anymore. CWM is safer and does everything we need it to do with the latest version.
This is only for AT&T phones running firmware version 1.57. If you have 1.52 or 1.26 please go here first: [SCRIPT] GladRoot (Bell 0.37.4, AT&T 1.26/1.52/1.57 Supported) If you are a Bell user, DO NOT INSTALL.
If you need the drivers, they are available here: 32-bit Drivers and 64-bit Drivers
If you run into any issues, please PM me or post your /data/local/tmp/ga2.log here. This will help me diagnose what went wrong, in the very unlikely event something goes wrong.
Come chat with us!​Features:
Deodexed
Creates a backup of your current /system/app and /system/framework directories (This does NOT delete anything outside specific AT&T bloatware files, however)
Custom boot logo (animated version coming soon!)
AppWidgetPicker (better widget management)
Enables sideloading
Ad blocking
Installs AT&T tethering APN
Enables desktop flash content, i.e. Hulu (You MUST install flashplayer 10.2 from market prior to installing the ROM. You must also use a browser that lets you set your user agent to Desktop, such as Dolphin Browser HD)
Clears Dalvik-cache (can cause some third party apps to behave strangely, just clear their data. Known to cause issues with Launcher Pro. Reset of LP data fixes)
Removes the AT&T bloat (see second post for list of what is removed.)
Enables HDMI mirroring
Disables background media scanning (speeds phone up a LOT)
Webtop without need for dock (through micro-hdmi cable)
Xperia Arc theme (ported to Atrix by olieebur)
Preferred install location
Various speed increase enhancements to settings
Replaces stock Gallery with Miui 3D Gallery
Full market access, no more restricted apps (Currently under testing, as it doesn't seem to be working properly)
​Installation instructions:
Download and install Tenfar's latest CWM Recovery.
Download the GladiAtrix2 v4.2.3 THEME zip file here or GladiAtrix2 v4.2.3 NO THEME zip here
If you want the Hulu hack to work, install 10.2 from the market now, BEFORE installing GladiAtrix2 v4.
Put the GladiAtrix2v4.2.3 zip corresponding to the version you selected (normal or notheme) on either internal or external SD card.
Boot into recovery.
Select “Install zip from SDCARD” using the volume keys to navigate and power button to select.
Select "choose zip from sdcard" if you put it on your external SD card, or "choose zip from internal sdcard" if you put it in phone memory.
Browse to the location you put the zip.
Select GladiAtrix2v4.2.3 zip corresponding to the version you selected (normal or notheme).
Install it!
Read disclaimer below
​DISCLAIMER
This script makes significant changes to the /system files on your phone.
By downloading the files you agree that you KNOW WHAT YOU ARE DOING and that you accept responsibility if something goes wrong.
This has been tested to the best of my ability.
We are NOT responsible if this bricks your phone. Thank you.
-Management​Download LinksDownload GladiAtrix2 v4.2.3 FULL here
Download GladiAtrix2 v4.2.3 FULL NOTHEME here​Changelog:* Version 4.2.3 - Released 04/13/2011
Split the theme and notheme into their own versions
Rolled all updates up to this point into a full install
New base install version is this version, all future updates will be incremental.
Cleaned up install methods to not mess with any user settings
* Version 4.2.2 - Released 04/13/2011
Permission fix update for settings.db causing a massive number of issues
* Version 4.2.1 - Released 04/13/2011
Fixed HDMI mirror errors
Changed fingerprint to allow unrestricted market access
Added Motoblur widgets/apps back in as people seem to use them (myself included). AT&T bloat still removed.
Replaced stock MediaGallery with Miui 3D Gallery
Added ability to use webtop without dock through micro-hdmi
Minor settings changes for increased battery life/performance
Fixed issues with flash hack (recompiled the lib as it was corrupt)
Added option for preferred installed locations to Settings -> Applications
Imported Xperia Arc theme (ported to Atrix by olieebur)
* Version 3 - Released 04/10/2011
Now removes some of the Motoblur/AT&T bloat
Added custom boot logo (Animated version coming soon!)
Added HDMI mirroring support (Credit to Weichel)
Turned off stagefright media scanning
Added local.prop tweaks for performance increase
Fixed issues with tethering on non-AT&T carriers
* Version 2 - Released 04/08/2011
Initial CWM release.
Added custom flash lib for desktop flash content (i.e. hulu)
Installation logged with errors to /data/local/tmp/ga2.log
* Version 1
Initial script release.
​Notes/thanks:Special thanks to: kennethpenn for the base installation instructions, shawnbuck/dasmoover/cranch/thews/sogarth/brandon15811/(anyone else I missed, apologies if I did) for all their insight on the script, and Chainfire for the use of his .sh recovery output methods, olieebur for the great work on the theme, weichel for the HDMI mirroring trick, and everyone who helped test in IRC.​If you see any spelling errors or have any other problems, feel free to PM me or post here.
If you have any feature requests, PM ME them. Please read post #2 for my current To Do list to make sure it's not already on there. If you know how to do anything on the to do list and would like to help out, send me a PM. I will ignore any "cn u add grhpix to the statuss bar?" in the thread.​

To Do
bootanimation - Make static logo into animation
Fix reboot/recovery options - Anyone that wants to help with this is more than welcome to.
kill sound on sd mount - Possible?
Uninstall script - Coming soon!
List of Motorola/AT&T apps removed
com.telenav.app.android.cingular.apk
com.att.myWireless.apk
com.blockbuster.app.moto.apk
com.ea.nfsshift.apk
com.mobitv.client.tv.apk
com.mtag.att.codescanner.apk
com.wavemarket.waplauncher.apk
com.yellowpages.android.ypmobile.apk
com.qo.android.moto.apk
Screenshots (coming soon!)Will post screenshots of the major highlights here, but right now, I'm going to bed.​

first !! thanks

Ririal, is it possible to add the option to set "Edge network only" as the stock Android would allow?
PM'd u

When I go to run this it asked too allow superuser, but superuser never asked to allow anything on the phone? Phone just sits there?

Running silky smooth. I'll report errors if they arise.

s0dhi said:
Running silky smooth. I'll report errors if they arise.
Click to expand...
Click to collapse
When you run the .bat file did you have too allow superuser on the phone?

JayRolla said:
When you run the .bat file did you have too allow superuser on the phone?
Click to expand...
Click to collapse
Yes. There are 3 (I think?) points at which you have to allow superuser.
The user interface for the install is really well done.

JayRolla said:
When you run the .bat file did you have too allow superuser on the phone?
Click to expand...
Click to collapse
Never mind had to reboot phone a few times and then it worked.

Ririal said:
To Do
bootanimation - Anyone up to making one is welcome, I'm bad with graphics :x
preferred install location - Need to figure out how to do this.
kill sound on sd mount - Possible?
Fix typo in splash screen - Sigh.
Click to expand...
Click to collapse
there are a handful of boot animations here if anyone is interested. if there's something in particular you want, i'd be happy to give it a go. i too suck at the whole graphics thing, so i wouldn't expect too much.

Please pardon my ignorance, but a few questions:
1) I'm basically on stock 1.26 right now (rooted). Would I have to first flash/ota update to 1.57 (while retaining root and whatnot) and only then be able to install this?
2) or is 1.57 packaged within this and I just have to flash a clean 1.26, retain root, etc. and then flash this, thus updating me to 1.57 via this ROM?
I know they're somewhat silly questions, it's just that a LOT of what I've been looking for in a ROM lately is (almost literally) a one click to 1.57+root.
Thanks for bearing with me...and any kind of ETA on an RC? I see you were up until 5 putting this together, so thanks for your hard work.

This is after you have done retain root and updated and the afterupdate retain root.
Sent from my MB860 using XDA Premium App

xyrovice said:
Please pardon my ignorance, but a few questions:
1) I'm basically on stock 1.26 right now (rooted). Would I have to first flash/ota update to 1.57 (while retaining root and whatnot) and only then be able to install this?
2) or is 1.57 packaged within this and I just have to flash a clean 1.26, retain root, etc. and then flash this, thus updating me to 1.57 via this ROM?
I know they're somewhat silly questions, it's just that a LOT of what I've been looking for in a ROM lately is (almost literally) a one click to 1.57+root.
Thanks for bearing with me...and any kind of ETA on an RC? I see you were up until 5 putting this together, so thanks for your hard work.
Click to expand...
Click to collapse
You need a 1.57 rooted to proceed with this as it says in the OP. if you are at 1.26 rooted then use the retainroot in xda to get rooted on 1.57 and then use this.

Will this work on the Atrix on Bell?

itsonlym3 said:
there are a handful of boot animations here if anyone is interested. if there's something in particular you want, i'd be happy to give it a go. i too suck at the whole graphics thing, so i wouldn't expect too much.
Click to expand...
Click to collapse
I was looking for a custom one. I have a friend who's going to be whipping up some images for me, but you're welcome to take a stab at it.
xyrovice said:
Please pardon my ignorance, but a few questions:
1) I'm basically on stock 1.26 right now (rooted). Would I have to first flash/ota update to 1.57 (while retaining root and whatnot) and only then be able to install this?
2) or is 1.57 packaged within this and I just have to flash a clean 1.26, retain root, etc. and then flash this, thus updating me to 1.57 via this ROM?
I know they're somewhat silly questions, it's just that a LOT of what I've been looking for in a ROM lately is (almost literally) a one click to 1.57+root.
Thanks for bearing with me...and any kind of ETA on an RC? I see you were up until 5 putting this together, so thanks for your hard work.
Click to expand...
Click to collapse
This rom does not update you to 1.57. You will need to be on 1.57 with root before this will work.
jayhammy said:
Will this work on the Atrix on Bell?
Click to expand...
Click to collapse
No, it will not.

I have a 1.57 w/ root (using before/after update script). Will Deodexing my Atrix make it faster/snappier?

kpfury said:
I have a 1.57 w/ root (using before/after update script). Will Deodexing my Atrix make it faster/snappier?
Click to expand...
Click to collapse
A bit, yes.

Ririal said:
To Do
kill sound on sd mount - Possible?
Click to expand...
Click to collapse
If you figure this out please share how you did it.

I don't think that sound can be killed. But then again I'm no expert. Also are there any known issues with GladiAtrix?
I have it installed but can't really tell for now. Great great work man!!

Any chance of some screen shots of this theme? If we had CWM I would just flash and check it out.Thanks.
Sent from my MB860 using XDA Premium App

[APP] Flash Image GUI - Flash Kernels and Recoveries from normal Android mode!

Credits:
Original version created in the summer of 2011. Thanks to birbeck for the usual random java guidance, slushpupie for his previous java guidance, dodgejcr for extreme amounts of testing, and one_love_420 and shift for some great graphics!
testers: JT-, couga6442, happytweak and many others I might have forgot in the furry of three days I built the initial app from scratch!
Special thanks to tiny4579 and ghul21 for testing on the OnePlus One!
Thanks to SDX
Requires:
Unlocked bootloader (shouldn't be a concern here!) and root access!
Background:
flash_image (bmlwrite) is an extremely useful utility for flashing custom kernels, boot logos (so far ONLY select Samsung devices) and recoveries. This binary has made it possible to easily flash all these items and is used almost everywhere behind the scenes (i.e. in custom recoveries, packaged into a kernel /sbin directory, included in custom ROMs, etc).
Description:
This android application, FlashImageGUI, is a GUI interface for the linux binary, flash_image provided by google in AOSP for loading custom kernels and recovery images onto the phone.
This app allows the flashing of kernels and custom recovery images in normal android mode!
Current Device Support:
Full Kernel (Anykernel and boot.img) Flashing and Recovery (zip file or image) flashing: OnePlus One, HTC One M8 (GSM), Moto G, Sprint Galaxy S4, International HTC One (M7), T-Mobile HTC One (M7), Sprint HTC One (M7), HTC EVO 4G LTE, HTC One S, HTC EVO 3D CDMA and GSM, HTC One XL, HTC Droid DNA, HTC Amaze, HTC Vivid/Holiday, HTC EVO 4G, HTC EVO Shift, Google Nexus 5, Google Nexus 4, Google Nexus 10, Google Nexus 7, Samsung Google Galaxy Nexus, Nexus S/Nexus S 4G & LG Optimus
Full Kernel, Logo and Recovery flashing: Samsung Moment, Transform, Intercept and Acclaim - the s3c6410 series of devices
Full Kernel (zImage) Flashing: Samsung Epic
Check application version for updates
Future Support:
Let me know if there are any issues. Feel free to post the encountered issue and a link to the exact file that was flashed. Thanks for the support!
Install Directions:
Install process is the same as any other .apk. Download to computer and adb push or mount sdcard on computer and copy over or download directly to the phone. Use any file manager, adb, connectbot/terminal emulator to install.
My preferred method, maybe a bit technical: ./adb install c:\downloads\FlashImageGUI.apk
Download Locations
Market (99 cents!): Flash Image GUI
Release version (free): Flash Image GUI
Contact:
Any questions, comments, concerns, or issues, please post in this thread or send me an email! Thanks for all the help and support!
FAQ:
Q: Will this app support a marketplace to pick and chose kernels from?
A: No.
Q: Can I flash nandroid kernel backups?
A: Yes. Rename the specific image to boot.img and select from inside of Flash Image GUI. **Make sure to also load the associated modules or WiFi might stop working!
Screenshots:
{
"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"
}
Feedback:
Please post any helpful feedback. I'm always looking to improve the application!
Users Guide for flashing ONLY a Kernel (zip file):
1) Ensure the bootloader is unlocked and root access is properly setup
2) Make sure the selected Kernel is compatible with the currently loaded ROM. If not, this will result in a lot of frustration!!! See troubleshooting steps below.
3) Download kernel zip file to /sdcard.
4) Open Flash Image GUI, browse and select kernel zip file, downloaded/loaded to sdcard in previous step.
5) Flash Image GUI will validate that the kernel zip file contains the minimum required files
6) Select the Flash Image button and Flash Image GUI will load the kernel and the kernel modules from the source kernel zip file.
7) Reboot
Troubleshooting after Rebooting:
First step, when experiencing issues flashing is to RE FLASH the files again. Many times, re flashing again will clear up any issues. If not, see the issues/solutions below.
Issue #1: If the device hangs or reboots while on the splash screen, the kernel itself or the ramdisk packaged in the kernel is NOT compatible with your device!!!
Solution for #1: Have to boot into fastboot (or directly into the custom recovery) and load the custom recovery to flash a known good kernel or restore a previously known good nandroid backup. Command: fastboot boot c:\downloads\cwm-recovery.img
Issue #2: If the device hangs or reboots while on the boot animation, the ROM is likely NOT compatible with the kernel!!!
Solution for #2: Have to boot into fastboot and load the custom recovery to flash a known good ROM/kernel combination either from a zip file or restore from a nandroid backup.

Completely surprised your thanks meter is not higher than what it is for the length of time you been helping out with your apps up in here. If I remember right you go way back to the winmo days right?
Thx for your app and allow me to be the first to thank you in the 1+ section :good:

playya said:
Completely surprised your thanks meter is not higher than what it is for the length of time you been helping out with your apps up in here. If I remember right you go way back to the winmo days right?
Thx for your app and allow me to be the first to thank you in the 1+ section :good:
Click to expand...
Click to collapse
I have been around a long while, and spent more time on here before the thanks meter was added (Dec 2010).
I appreciate the support and feel free to provide feedback as I'm always interested in improving!

Quick question, how does this app differ from one like Flashify? Is it another alternative?
Don't get me wrong, I'm all for lots of new development and different alternatives, just trying to understand if this app provides something different (or at least does it better) than some other similar apps.
Thanks!

pinoymutt said:
Quick question, how does this app differ from one like Flashify? Is it another alternative?
Don't get me wrong, I'm all for lots of new development and different alternatives, just trying to understand if this app provides something different (or at least does it better) than some other similar apps.
Thanks!
Click to expand...
Click to collapse
I can't speak to Flashify, other than it didn't exist when I created Flash Image GUI ~3 years ago. I'm also unsure about their business model, whether they're free and charge for usage or whether they charge for the app.
Either way, I host a free copy of Flash Image GUI for XDA users and do my best to monitor this thread for any issues, concerns, or bugs, as I've done for around 30 devices over the last three years!
Thanks for your support!

Nice to see you around here @joeykrim! I still have my Moment around here somewhere running something crazy from SDX.

Hi joeykrim
Nice to see you start a thread in here
Some time ago i post you an email to support Oneplus One and we made some tests
thx for the app and finaly full support for OPO on XDA. Glad it finally work for "all" of my devices
One more time THX for amazing app
Regards
Marcin :highfive:

ghul21 said:
Hi joeykrim
Nice to see you start a thread in here
Some time ago i post you an email to support Oneplus One and we made some tests
thx for the app and finaly full support for OPO on XDA. Glad it finally work for "all" of my devices
One more time THX for amazing app
Regards
Marcin :highfive:
Click to expand...
Click to collapse
Yes, I appreciated you reaching out and requesting support, plus spending time testing as I added support. I've added your XDA name to the credits at the top. Thanks again for your help!

Thanx for adding support for opo, but could you make recognize the "any kernel" zip files as it does not contain img's.several kernel dev's are using this method nowadays,so their kernel is compatible across all rom's..

zodiaxe66 said:
Thanx for adding support for opo, but could you make recognize the "any kernel" zip files as it does not contain img's.several kernel dev's are using this method nowadays,so their kernel is compatible across all rom's..
Click to expand...
Click to collapse
I do support the method on devices where the kernel devs follow common and standard usage of the anykernel method, but didn't see this on the OPO a few weeks back.
Can you provide links to the specific kernels on the OPO that are using this method? When I checked a few weeks back, there was only one and they were using an unusual variation of the anykernel method that I hadn't seen on any other device before.
Thanks for your support!

joeykrim said:
I do support the method on devices where the kernel devs follow common and standard usage of the anykernel method, but didn't see this on the OPO a few weeks back.
Can you provide links to the specific kernels on the OPO that are using this method? When I checked a few weeks back, there was only one and they were using an unusual variation of the anykernel method that I hadn't seen on any other device before.
Thanks for your support!
Click to expand...
Click to collapse
Here you go and thanx
Ups my link in gone
Posting it later when i'm home..it's AK kerne by AK in original Android dev
http://forum.xda-developers.com/oneplus-one/orig-development/kernel-ak-t2832168
EDIT: heres a screenshot of chosen kernel I tried to flash. Your app doesn't recognize the zImage..

Device not supported?

zodiaxe66 said:
Here you go and thanx
Ups my link in gone
Posting it later when i'm home..it's AK kerne by AK in original Android dev
http://forum.xda-developers.com/oneplus-one/orig-development/kernel-ak-t2832168
EDIT: heres a screenshot of chosen kernel I tried to flash. Your app doesn't recognize the zImage..
Click to expand...
Click to collapse
The link is helpful and that was the one kernel using the "AnyKernel" method but in a less common manner that I'm hesitant about adding support for. I appreciate the request and can investigate it further but at this point, that one kernel likely won't be a high priority unless many other people request it, mostly due to the less common manner it uses to load. I view there be additional risk to adding less common loading methods in that I don't want to damage any devices using less proven methods. Given that I don't own the device myself, I'm also less likely to ask testers to risk using a less common loading method to test support.
lqdcat said:
Device not supported?
Click to expand...
Click to collapse
The screenshot is very helpful and ironically shows that this is the kernel, quoted above, that I'm hesitant to add flashing support to as it uses less common methods of loading. It seems that either the kernel or the ROM changes how the device identifies itself and breaks compatibility with Flash Image GUI. Which ROM are you using?
While you're still using that kernel and ROM combination, can you share the output from the following adb shell command? adb shell getprop ro.product.device

joeykrim said:
The link is helpful and that was the one kernel using the "AnyKernel" method but in a less common manner that I'm hesitant about adding support for. I appreciate the request and can investigate it further but at this point, that one kernel likely won't be a high priority unless many other people request it, mostly due to the less common manner it uses to load. I view there be additional risk to adding less common loading methods in that I don't want to damage any devices using less proven methods. Given that I don't own the device myself, I'm also less likely to ask testers to risk using a less common loading method to test support.
The screenshot is very helpful and ironically shows that this is the kernel, quoted above, that I'm hesitant to add flashing support to as it uses less common methods of loading. It seems that either the kernel or the ROM changes how the device identifies itself and breaks compatibility with Flash Image GUI. Which ROM are you using?
While you're still using that kernel and ROM combination, can you share the output from the following adb shell command? adb shell getprop ro.product.device
Click to expand...
Click to collapse
Okay I understand, Thanx for your response and to clear things up.
PS. I have no problem with my opo getting recognized, so apparently it's as you pointed out, only the one kernel, sadly, but there are many other ways to flash it, so no worries.. :highfive:

it took about 2 seconds to flash a new recovery.img
Excellent
Thank you very much!!

Is there any Custom rom that comes preinstalled with Superuser instead of SuperSU?

See the title. Right now, I dont have ADB on my PC and Java JDK and I cant be arsed to install it, and reinstall Twrp and flash.
Thank you for your time.
SuperSU is propietary and this situation with android and recent developments have pissed me off alot.
You know;, I dont want to use a browser, without 50 trackers spying on me ,and having SuperSU do god knows wha.t.
A clear no no.
I dont care If I have to run Stock AOSP. The only thing I need is to feel private enough without feeling spied on.

no. superuser is old and outdated. it hasn't been worked on in a while.

Kinguser or cyanogenmod?

shadowcore said:
See the title. Right now, I dont have ADB on my PC and Java JDK and I cant be arsed to install it, and reinstall Twrp and flash.
Thank you for your time.
SuperSU is propietary and this situation with android and recent developments have pissed me off alot.
You know;, I dont want to use a browser, without 50 trackers spying on me ,and having SuperSU do god knows wha.t.
A clear no no.
I dont care If I have to run Stock AOSP. The only thing I need is to feel private enough without feeling spied on.
Click to expand...
Click to collapse
Could always make one yourself. Oh wait if you dont want to go through the effort to accomplish what you want, then you most likely wont want to do that either.
At the moment if there is a rom that doesnt use SuperSU then I have never personally seen it. The Dev has earned the trust of users and the staff over the years.

@simms22,
If it's outdated and no longer being supported, then what do you make of this?
http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
Sent from my Nexus 6 using Tapatalk

Choose any rom you want, flash, and flash unSU script( http://forum.xda-developers.com/showpost.php?p=63615067&postcount=2459 ) then.
And proceed with your preference.
If you really think SuperSU is spyware, you can block internet connection(....) of SuperSU, else something other APP OPtionS are available.
If you want open-source app, I guess CM superuser may be.

My guess is you could live in a tinfoil house in the forest and you would still feel spied on.

reignlight said:
@simms22,
If it's outdated and no longer being supported, then what do you make of this?
http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
its a fork, someone else is working on it, koush isnt.

The problem the OP is having seems to be the same one doitright has in his "Root Done Right" thread in Nexus 6 General: a lack of transparency. The argument essentially boils down to this. Because SuperSU is closed source, you can't check it and can't trust it. Therefore you shouldn't use it. In that thread, the reasoning behind the lack of trust is because we know nothing about the entity that now owns SuperSU, and that there's no reason known for the SuperSU binary to manipulate the SELinux policies and reload them, if necessary.
Because of the lack of transparency, doitright feels that SuperSU is too dangerous to use. In order to ensure that there is an avenue to provide full control over our devices should the company now owning SuperSU decide to do something underhanded with the software, he forked Koush's Superuser so that it would support the latest versions of Android.
I know the link given was to PHH's Superuser thread, but I think he's thinking along the same lines as doitright, and is concerned about the potential future impact of the change in ownership. Even I have that concern, but it's not enough for me at this time to stop using SuperSU. Until the time comes that SuperSU is no longer a viable option, any FUD regarding SuperSU is premature.
For the OP, if you're that worried about SuperSU, don't root and don't install a custom ROM. With the exception of Cyanogenmod, custom ROMs all use SuperSU. I don't expect that to change any time soon.

Cyanogenmod roms
Sent from my Nexus 6 using Tapatalk

Thanks for the helpful replies people, at least those that arent condescending.
Does anyone know how the CM root is implemented. ? doitright specifically mentioned that the selinux policy is respected with his fork, and I dont know if CM does so aswell.
I am experimenting with stock CM 13.0 a bit. I wish other custom roms respected the user and left flashing superSU as a choice, not come preinstalled.
I cannot trust SuperSU and I wish not to support a propietary root method.

@shadowcore: Koush's SU hadn't been updated in the last few years, once he stopped working on both it and Clockworkmod. ChainsDD's SU hasn't been updated for an even longer period. Neither option supported SELinux, and ROM developers didn't see the need to add it since Chainfire already had done so with SuperSU. I would know. My stock ROM in the Dell Streak forums was a fork of another ROM (with permission of course), and replaced the included custom superuser binary with SuperSU, despite that device being old enough to work with both Koush and ChainsDD's superuser apps as is. The reason I made the change was simple: SuperSU was being actively worked upon, and the options were not.
I do take some exception to your statement that it's up to the ROM developers to respect user choice. Many of these ROMs are personal projects that the developers saw fit to release to the public, rather than commercial efforts like Cyanogenmod. Thus what is included in the ROM is what the developer prefers, and you either accept it, or you fix it. In the case of SuperSU, you can fix it yourself since the SuperSU app includes a means of removing it within the app so you can install an alternative. However it is up to you to find and install that alternative, not the developer.

simms22 said:
no. superuser is old and outdated. it hasn't been worked on in a while.
Click to expand...
Click to collapse
What the frig are you talking about?
http://forum.xda-developers.com/nexus-6/general/root-t3231211
---------- Post added at 07:40 PM ---------- Previous post was at 07:38 PM ----------
PielunA said:
Choose any rom you want, flash, and flash unSU script( http://forum.xda-developers.com/showpost.php?p=63615067&postcount=2459 ) then.
And proceed with your preference.
If you really think SuperSU is spyware, you can block internet connection(....) of SuperSU, else something other APP OPtionS are available.
If you want open-source app, I guess CM superuser may be.
Click to expand...
Click to collapse
I'm not sure how you think you can accomplish that.... are you talking about app-ops? If so, do you realize that that would only block the android application and not the actual binary? The daemon process has unrestricted access to the kernel and cannot be blocked.
---------- Post added at 07:42 PM ---------- Previous post was at 07:40 PM ----------
simms22 said:
its a fork, someone else is working on it, koush isnt.
Click to expand...
Click to collapse
Two words for you: OPEN SOURCE.
Kind of the whole point of it is that it isn't dependent on any single person. Multiple people work on it, multiple people check each other's work, and if that one person stops working on it, the project isn't lost.
---------- Post added at 07:46 PM ---------- Previous post was at 07:42 PM ----------
Strephon Alkhalikoi said:
The problem the OP is having seems to be the same one doitright has in his "Root Done Right" thread in Nexus 6 General: a lack of transparency. The argument essentially boils down to this. Because SuperSU is closed source, you can't check it and can't trust it. Therefore you shouldn't use it. In that thread, the reasoning behind the lack of trust is because we know nothing about the entity that now owns SuperSU, and that there's no reason known for the SuperSU binary to manipulate the SELinux policies and reload them, if necessary.
Because of the lack of transparency, doitright feels that SuperSU is too dangerous to use. In order to ensure that there is an avenue to provide full control over our devices should the company now owning SuperSU decide to do something underhanded with the software, he forked Koush's Superuser so that it would support the latest versions of Android.
I know the link given was to PHH's Superuser thread, but I think he's thinking along the same lines as doitright, and is concerned about the potential future impact of the change in ownership. Even I have that concern, but it's not enough for me at this time to stop using SuperSU. Until the time comes that SuperSU is no longer a viable option, any FUD regarding SuperSU is premature.
For the OP, if you're that worried about SuperSU, don't root and don't install a custom ROM. With the exception of Cyanogenmod, custom ROMs all use SuperSU. I don't expect that to change any time soon.
Click to expand...
Click to collapse
FYI: PHH and I work on the *same* fork of Superuser. I've been pretty lax on it lately due to growing family, but intend to put some more hours into it soon. We aren't competing with each other at all, but rather working on improvements to the same thing. So don't think of it as being along the same lines, but rather *with*.
And also, I think its probably important for me to also point out that Pierre has certainly put a lot more hours into it than I have. Nevertheless, everything useful is useful.
---------- Post added at 07:54 PM ---------- Previous post was at 07:46 PM ----------
shadowcore said:
Thanks for the helpful replies people, at least those that arent condescending.
Does anyone know how the CM root is implemented. ? doitright specifically mentioned that the selinux policy is respected with his fork, and I dont know if CM does so aswell.
I am experimenting with stock CM 13.0 a bit. I wish other custom roms respected the user and left flashing superSU as a choice, not come preinstalled.
I cannot trust SuperSU and I wish not to support a propietary root method.
Click to expand...
Click to collapse
I haven't actually looked at CM's selinux policy in depth. I *suspect* that they probably go permissive in their su-equivalent context.
What you might want to look at, are custom roms that, rather than "shipping" with one or the other, **DON'T** ship with ANY. I know for one that Omnirom ships WITHOUT root, and while they may recommend supersu, you can use anything.
I'm not sure if my stock-ish boot images will work properly with omnirom. You can try it? If not, you could also try PHH's update.zip installation method.
Personally, I prefer omnirom over cyanogenmod. CM is... very unstable, they are too fast and uncontrolled with the "additions", and adds in certain things that are spyware-ish. Omnirom is more balanced. Far less aggressive, but rather focused on bringing in actual useful features rather than blinging the crap out of it.
---------- Post added at 08:03 PM ---------- Previous post was at 07:54 PM ----------
Strephon Alkhalikoi said:
I do take some exception to your statement that it's up to the ROM developers to respect user choice. Many of these ROMs are personal projects that the developers saw fit to release to the public, rather than commercial efforts like Cyanogenmod. Thus what is included in the ROM is what the developer prefers, and you either accept it, or you fix it. In the case of SuperSU, you can fix it yourself since the SuperSU app includes a means of removing it within the app so you can install an alternative. However it is up to you to find and install that alternative, not the developer.
Click to expand...
Click to collapse
While I don't agree with the choice to use supersu, I absolutely agree with this statement and perspective. Those building custom rom's don't owe anything to anybody, and obviously can make it however they like personally. If that happens to line up with the needs or wants of some group of end users, then those end users benefit from the generosity of whoever is sharing it. If not, then there are others sharing their work, and of course, there is the option to run your own builds.
Having said that, I don't think that the statement was actually meant in quite the way it came off. I think it was meant a little more softly, that from an end user point of view, options are nice.
Frankly, the only ones who actually *owe* you anything, in terms of the operating system, is GOOGLE. That is who you paid for the support by purchasing the product. Of course, that only applies to Nexus branded phones, if you buy something from someone else, they are the ones who owe you support.

please delete thread

Ainur JamesDSP is now available in Magisk Manager. Thanks to the devs for their great work. Enjoy!

Not working on pixel xl with magisk 14.3. Repeatedly showing the app has shut down unexpectedly. And then my system started an automatic factory wipe (good thing I forced shut down before the wipe started)

biribiribiri said:
Not working on pixel xl with magisk 14.3. Repeatedly showing the app has shut down unexpectedly. And then my system started an automatic factory wipe (good thing I forced shut down before the wipe started)
Click to expand...
Click to collapse
Yikes. I wonder if AML doesn't support Pixel yet. I will look into it and add a note to the OP. Thanks for the heads up.

biribiribiri said:
Not working on pixel xl with magisk 14.3. Repeatedly showing the app has shut down unexpectedly. And then my system started an automatic factory wipe (good thing I forced shut down before the wipe started)
Click to expand...
Click to collapse
By the way, were you running any other audio mods at the time?

s8m said:
By the way, were you running any other audio mods at the time?
Click to expand...
Click to collapse
no

I am getting a blank screen when opening jamesDSP upon flashing and rebooting. Then if I got to recovery and wipe cache and dalvik and reboot it just does a constant FC, over and over. I provided a log through ADB. I am running ABC ROM, Android O, Angler. As you can also see I have audmodlib and ainur audio as well. Also, before I wiped cache and dalvik and the JamesDSP screen was just blank it did show in notification. Basically, Not working at all here. Thanks for the work bud. The first link is the constant FC with ADB, and the second link is Matlog with the blank JamesDSP screen when opening.
https://haste.blamealexcruz.com/WoNVF1m7XX.swift
https://haste.blamealexcruz.com/8EdpzPLtrU.pl

yung40oz84 said:
I am getting a blank screen when opening jamesDSP upon flashing and rebooting. Then if I got to recovery and wipe cache and dalvik and reboot it just does a constant FC, over and over. I provided a log through ADB. I am running ABC ROM, Android O, Angler. As you can also see I have audmodlib and ainur audio as well. Also, before I wiped cache and dalvik and the JamesDSP screen was just blank it did show in notification. Basically, Not working at all here. Thanks for the work bud. The first link is the constant FC with ADB, and the second link is Matlog with the blank JamesDSP screen when opening.
https://haste.blamealexcruz.com/WoNVF1m7XX.swift
https://haste.blamealexcruz.com/8EdpzPLtrU.pl
Click to expand...
Click to collapse
Thanks - very helpful! Looking quickly at your logcat this may be related to libjamesDSPImpulseToolbox.so being placed inside /system/lib/ instead of /system/lib64/ (my device is ARM64 but accepts /system/lib/). I'll look into a workaround and update this in next build.

s8m said:
Thanks - very helpful! Looking quickly at your logcat this may be related to libjamesDSPImpulseToolbox.so being placed inside /system/lib/ instead of /system/lib64/ (my device is ARM64 but accepts /system/lib/). I'll look into a workaround and update this in next build.
Click to expand...
Click to collapse
Great! Looking forward to it.

When users provide logs...

I already submitted this to the repo. Why are you posting our module as yours? V1.1 is BETA. There's a reason why it is unreleased.
Please have this thread removed. You're going to cause issues for other users, which is already happening.

ahrion said:
I already submitted this to the repo. Why are you posting our module as yours? V1.1 is BETA. There's a reason why it is unreleased.
Please have this thread removed. You're going to cause issues for other users.
Click to expand...
Click to collapse
I'm confused... this is built off a fork of your AM3D repo but my fork is not your repo. V1.1-beta is the version I created. Like the OP says I created this module, combining your AML/Unity framework and james34602's JamesDSPManager.
If you are working on a JamesDSPManager module that is news to me (hence why I made this module). If you are working on a module that is also v1.1-beta that is quite a coincidence! Are you saying you don't want other devs building off of your AML library and sharing with the community? I thought that was welcome (you are planning a template after all) but I will remove this module if you would rather control development.

s8m said:
I'm confused... this is built off a fork of your AM3D repo but my fork is not your repo. V1.1-beta is the version I created. Like the OP says I created this module, combining your AML/Unity framework and james34602's JamesDSPManager.
If you are working on a JamesDSPManager module that is news to me (hence why I made this module). If you are working on a module that is also v1.1-beta that is quite a coincidence! Are you saying you don't want other devs building off of your AML library and sharing with the community? I thought that was welcome (you are planning a template after all) but I will remove this module if you would rather control development.
Click to expand...
Click to collapse
Ahhhh. I didn't check the GitHub repo. I thought you just built the thread with my GitHub repo (which I submitted through Magisk).
That's so weird lol.
You're good then, but using the latest sources will cause things to be wonky with the current stable version of the other mods. It will cause FC all day.
False alarm. Sorry about that! I'm still gonna make a thread for this however.

ahrion said:
Ahhhh. I didn't check the GitHub repo. I thought you just built the thread with my GitHub repo (which I submitted through Magisk).
That's so weird lol.
You're good then, but using the latest sources will cause things to be wonky with the current stable version of the other mods. It will cause FC all day.
False alarm. Sorry about that! I'm still gonna make a thread for this however.
Click to expand...
Click to collapse
OK no worries! That's a good point that using unreleased sources can cause other unwanted problems. I will take this down if you are creating a separate thread. It's probably better for everyone if you are able to manage the development of AML modules.

s8m said:
OK no worries! That's a good point that using unreleased sources can cause other unwanted problems. I will take this down if you are creating a separate thread. It's probably better for everyone if you are able to manage the development of AML modules.
Click to expand...
Click to collapse
It's up to you man. I submitted the stuff yesterday to the Magisk repo, along with a V4A as well as Unity Xposed.
Since you're looking from outside, in. Was Unity easy to configure for you? The entire point for AML is to link everything to together for Magisk. Then we created Unity to be an all in one installer. Any AML modules are encouraged and welcome. Ainur is running AML currently.

Yeah I must say Unity is really well done. I've only ever done very simple Magisk modules (for personal use) so I may not be the best judge, but there wasn't much learning curve at all with Unity. The way the patching and multi-arch handling is set up is really intuitive and logical. This module was really simple to create compared to your ViPER4Android module but it was nice not to have to think about modifying the install-binary or add custom sed commands. All in all - #impressed !

s8m said:
Yeah I must say Unity is really well done. I've only ever done very simple Magisk modules (for personal use) so I may not be the best judge, but there wasn't much learning curve at all with Unity. The way the patching and multi-arch handling is set up is really intuitive and logical. This module was really simple to create compared to your ViPER4Android module but it was nice not to have to think about modifying the install-binary or add custom sed commands. All in all - #impressed !
Click to expand...
Click to collapse
Awesome. You can thank @Zackptg5
Another addition is SETools-inject for Android, that functions like sepolicy inject that MagiskSU/SuperSU have. Essentially, it allows rootless and other forms of root to also use it via init.d. As of yet, no one has actually used SETools for this.
We've also added init.d patching, for rootless and other root methods. Essentially, ramdisk will be automatically patched for AML system modules to use init.d (even if your rom didn't support it before). So init.d patch for all Android versions, MM/N+, has been added. Currently nearly all (if not all) init.d support is broken.

ahrion said:
I already submitted this to the repo. Why are you posting our module as yours? V1.1 is BETA. There's a reason why it is unreleased.
Please have this thread removed. You're going to cause issues for other users, which is already happening.
Click to expand...
Click to collapse
I hope your mod will be in the repo soon, topjohnwu has been very picky with your soubd mods.

24imelqui said:
I hope your mod will be in the repo soon, topjohnwu has been very picky with your soubd mods.
Click to expand...
Click to collapse
It's not that he has been picky. It's just it takes some time to get approved.
Topjohnwu is a busy man.

BTW, Unity allows system mode installation natively if Magisk is not installed, includes addon..d as well.
Magisk is not required for any Unity zips.

ahrion said:
It's up to you man. I submitted the stuff yesterday to the Magisk repo, along with a V4A as well as Unity Xposed.
Click to expand...
Click to collapse
It may be a dumb question, but does your Ainur JamesDSP module require Ainur or can it run independently without Ainur installed?

Google Dialer v37 & Contacts v3.7.7 on Stock ROMs (any ROM really) August 1st, 2019

Google Dialer v37 & Contacts v3.7.7 on Stock ROMs (any ROM really) August 1st, 2019
I maintained a simple little project on the V20 forum that added Google's Pixel Dialer app and Google Contacts to (any device, really) my V20, and I thought it might be a good idea to post in here about it too, since I am now on a LS998 V30+
Link to the thread in V20's apps section HERE
These zips should work on any android running nougat and above, but I will only support the V30 for sure, since thats what I have.
Installing this will not remove anything you already have on your phone, it will only add google's dialer app and framework as a second phone app.
as always, my latest updates and newest files can be found in this shared Google Drive folder
This link has been changed, the correct one is above. I had (wanted) to move this project to a separate dedicated account that was not so personal. Reshare the folder to yourself using Google Drive and/or update your bookmark.
August 1st, 2019
- updated both apps to latest version of each as supplied by Google, app versions are below...
arm64 zips
Phone-com.google.android.dialer-(arm64)-33.0.247985459-publicbeta-3998624.apk
Contacts-com.google.android.contacts-3.5.51.247103087-2209215.apk
OLD Changelog:
August 1st, 2019
- updated both apps to latest version of each as supplied by Google, app versions are below...
- updated all the framework files to match the ones in the latest release from opengapps
- removed LGInCallUI app as it is not completely necessary in this particular project
arm64 zips
Phone-com.google.android.dialer-37.0.260231449-publicbeta-4339080.apk
Contacts-com.google.android.contacts-3.7.7.260733580-2243311.apk
April 25th, 2019
- updated both apps to latest version of each as supplied by Google, app versions are below...
arm64 zips
Phone-com.google.android.dialer-31.0.241960258-publicbeta-3785841.apk
Contacts-com.google.android.contacts-3.5.7.243634183-2209036.apk
arm(32) zips
Phone-com.google.android.dialer-31.0.241960258-publicbeta-3785840.apk
Contacts-com.google.android.contacts-3.5.7.243634183-2209035.apk
All files can be found and downloaded from my shared Google folder (above) or attached to this post (below).
March 27th, 2019
- updated both apps to latest version of each as supplied by Google, app versions are below...
arm64 zips
Phone-com.google.android.dialer-31.0.240233734-publicbeta.apk
Contacts-com.google.android.contacts-3.4.6.234021015-2191599.apk
arm(32) zips
Phone-com.google.android.dialer-31.0.240233734-publicbeta-3785464.apk
Contacts-com.google.android.contacts-3.4.6.234021015-2191598.apk
February 22nd, 2019
- updated both apps to latest version of each as supplied by Google. App versions are below...
arm64 zips
Phone-com.google.android.dialer-29.0.234661434-publicbeta-3570857.apk
Contacts-com.google.android.contacts-3.4.6.234021015-2191599.apk
arm(32) zips
Phone-com.google.android.dialer-29.0.234661434-publicbeta-3570850.apk
Contacts-com.google.android.contacts-3.4.6.234021015-2191598.apk
questions or comments? leave a reply here and I will see it. I don't visit here often but I should get back to you either immediately or within 2-3 weeks.
~syndre
- I don't think it's necessary, but by request (and to avoid confusion) I have made a Android 9.0+ PIE compatible flashable zip to install just the dialer's framework.
January 22nd, 2019
- Updated apks to latest versions from Google
Phone-com.google.android.dialer-28.0.229824408-publicbeta-3464836.apk
Contacts-com.google.android.contacts-3.3.3.226019458-2171201.apk
-I uninstalled any updates to the phone and contacts app I had installed, and flashed the non-magisk version on to my V30+, both apps are working fine.
-I copied those files into the magisk template I've been using and zipped that to create a magisk installable version. I have not tested this one but I assume it will work for those who use it.
- expect arm versions within the next week.
downloads are attached below, to this post.
December 20th, 2018
I am still not sure why it was happening, but the Phone app started randomly force closing on me a few days ago. I do a lot of playing around with mods and stuff so it could just be me. I have updated and tested both of the zips being released today, and the app is working again for me. I use a stock Oreo LG ROM. Everyone who hasn't had this issue or if you're on another device or on AOSP, ignore this paragraph. Theres a few files different in here from the previous version, so please flash this update so I know we're all on the same page. ty
- Updated dialer to latest apk from Google: v27.0.225573798-publicbeta-3347328.apk
- Updated/changed a couple framework related files to get the app to stop force closing on my device.
- arm (32) versions made and posted, too. Make sure you use the correct zip for your device!
New files can be found attached onto this post below and/or in the drive folder linked to above.
November 26th, 2018
updated phone to today's release from google
These are a little different from the previous (Nov 26) version, if you experience any issues at all please let me know!
attached below, and also available HERE
November 26th, 2018
updated arm64 apk's
arm update soon
flashable zips are attached below
November 15th, 2018
seems like they always put one out after I post... v26 is supposed to officially have dark mode in the dialer app (now both phone and contacts).
attached below
November 13th, 2018
my last post in this thread
Updated APK's to versions:
Phone-com.google.android.dialer-25.0.220310144-3118535.apk
Contacts-com.google.android.contacts-3.2.4.220343473-2161331.apk
both regular and magisk flashable zips are attached to this OP.
You can also find everything related to this project here in this shared drive folder.
New Favorites Section and Dark Mode on display in this Screenshot Album...
{
"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"
}
Above is still not Google official, but easy to manipulate. See thread started by @JonnyTrulove HERE!
October 27th, 2018
Updated arm64 APKs to Google's newest version of each, both released today:
Phone-com.google.android.dialer-25.0.218361296-3118167.apk
Contacts-com.google.android.contacts-3.1.6.218196352-2149637.apk
I'll upload zips with version 25 for arm devices soon. I'm literally on my phone, typing this from a pitch dark cabin in the woods in the Midwest U.S. with someone sleeping a foot away from me.
Download arm64 zip to flash directly to system, also attached below OP
Download arm64 zip packaged as a magisk module, instead, also attached below OP
LINK CHANGED/UPDATED
Link to my NEW shared drive folder.
October 8th, 2018
arm64 versions with new contacts v3.1.3 update
arm64 version with new contacts v3.1.3 update -Magisk Module
I built these and edited this top post totally on mobile, I hope it works..
I'll fix[/IMG] the rest later
it has just come to my attention that some people (on other devices) are having problems because I never switched over to the 2018 dialer framework in these zips. Both versions have always been there, I just had it named in such a way that the 7.0 version wax being used.
I have changed it over to the newer Oreo 8.0 framework, and will use that from today onwards.
Any issues because of this on LG phones? Please leave a response about it.
download 8.0 framework below, or here
October 3rd, 2018
Updated all apk's involved, and put together an arm version so I could use it on my older arm devices.
arm64 version for V30 and newer phones, magisk'd
arm64 version that writes directly to /system partition
arm version for your older phones , magisk'd
arm version that writes directly to /system partition
I have also attached the same 4 zips to this top post. They must have raised the file size limit recently or something ¯\_(ツ)_/¯
September 28th, 2018
Updated APK's to Phone v24 and Contacts v3.0.7
regular /system flashable zip HERE
NEW
Magisk Module I put together HERE
After flashing onto your device, you will have to manually enable all the permissions for each app.
Also you'll need to change the default phone app in your settings.
As far as I can tell, everything in the phone app works (caller ID, spam filter, nearby places)
Unless you use google voice, you will still need to have your carrier's voicemail app installed to use Visual Voicemail.
using either of these methods will allow you to download updates from the play store, so you will not need to wait for me post an update to have the latest versions of both phone and contacts.
I don't expect any problems on your device, as this zip is fairly simple and straightforward. If any bugs do show up, though, I will work with V30 users. I make these zip files for my own personal use. I am sharing them because you might want them too!
Lastly, I often will upload newer versions to a folder on google drive without updating this top post every single time.
You can access that HERE, and share it to yourself or whatever. I'm just trying to make it easiest on myself and anyone interested in following the project.
unattached file DL count -
arm64:3640 | arm64-magisk: 1332 | arm:398 | arm-magisk: 436

syndre said:
I maintained a simple little project on the V20 forum that added Google's Pixel Dialer app and Google Contacts to (any device, really) my V20, and I thought it might be a good idea to post in here about it too, since I am now on a LS998 V30+
These zips should work on any android running nougat and above, but I will only support the V30 for sure, since thats what I have.
Link to the thread in V20's apps section HERE
September 28th, 2018
Updated APK's to Phone v24 and Contacts v3.0.7
regular /system flashable zip HERE
NEW
Magisk Module I put together HERE
After flashing onto your device, you will have to manually enable all the permissions for each app.
Also you'll need to change the default phone app in your settings.
As far as I can tell, everything in the phone app works (caller ID, spam filter, nearby places)
Unless you use google voice, you will still need to have your carrier's voicemail app installed to use Visual Voicemail.
using either of these methods will allow you to download updates from the play store, so you will not need to wait for me post an update to have the latest versions of both phone and contacts.
I don't expect any problems on your device, as this zip is fairly simple and straightforward. If any bugs do show up, though, I will work with V30 users. I make these zip files for my own personal use. I am sharing them because you might want them too!
Lastly, I often will upload newer versions to a folder on google drive without updating this top post every single time.
You can access that HERE, and share it to yourself or whatever. I'm just trying to make it easiest on myself and anyone interested in following the project.
Thanks
Click to expand...
Click to collapse
You don't need to move contacts to the system. Just the phone app.

TotallyAnxious said:
You don't need to move contacts to the system. Just the phone app.
Click to expand...
Click to collapse
Ok, and?
I like it in /system, where it won't get accidentally removed.
I assume since you took the time to comment that you think its better installed as a user app for some reason.. I'm curious now, what is/are those reasons?
Putting apps like that on the system partition makes no difference in functionality, and saves space it would otherwise be taking up on /data...
Your stock contacts app comes out of the box on /system, most if not all gapps packages put contacts onto /system.
There are many, many apps that will work on either system or installed as a user app.
I put it there because I like it there. phone and contacts in my installer come together as one package. There's no reason to not keep it simple and put both apps in the same destination.
Thanks for commenting, I guess... but I don't know why you are telling me something I'm well aware of.
Once you have the framework and permission files on the system partition for the phone app, you can sideload that APK too onto /data, if that's what you prefer.
I don't plan on changing anything, and look forward to later in the day when I'll hopefully forget about being confused about why you needed to mention this, especially with zero context.
Sent from my LGE V30+ using XDA Labs

I used this on my phone - I previously had Contacts from the Play Store and a modified copy of Phone from Martin.077 (I was using version 20). Anyway I wanted to mention with this version, the visual voicemail feature built into the Phone app is working for me with a retail US998+ on Verizon, and this is mostly stock firmware. I say mostly stock because I have the Verizon modem flashed - signal strength at my home doesn't seem as good with the V30 as it was with my Droid Turbo, so I've been experimenting.

If I install and use Magisk module, does disabling the module let me use original dialer?
nvm, installed Magisk module. Working great. Thanks!

tagor said:
If I install and use Magisk module, does disabling the module let me use original dialer?
nvm, installed Magisk module. Working great. Thanks!
Click to expand...
Click to collapse
Installing any of my zips from this thread will not do anything to your stock dialer app (as far as I know).
You will have to go into the phone settings and switch which one you want set as the default.
To use stuff in the google one, you must set google phone as default.
If you ever need to update your PRL or anything like that, you will have to switch it back to the LG contacts app, or else the dialer "secret codes" wont do anything.
I should have mentioned that in the OP..
Installing this will not remove anything you already have on your phone, it will only add google's dialer app and framework as a second phone app.

hitokage004 said:
Anyway I wanted to mention with this version, the visual voicemail feature built into the Phone app is working for me
Click to expand...
Click to collapse
Replying to myself to indicate this apparently isn't correct (based on info from another thread). I didn't know when people referred to visual voicemail, they were referring to the text transcription stuff. I have a Google voice number that isn't really used, but I've seen the transcriptions on the website from people who misdialed and left a message - I wasn't particularly impressed and had to listen anyway.
It was mentioned that there is configuration files that will make it work though, so what I said is partly correct - as the voicemail tab shows in the Google dialer when using this version. The modified version I used before didn't have that tab.
EDIT - See below.

ChazzMatt said:
Visual Voicemail is not transcription. Visual Voicemail is merely a list of voice messages so you can pick and choose the order you wish to listen or even delete without listening. It MAY also include voicemail-to-text transcription, but that is not the purpose of the visual voicemail definition. Early visual voicemail applications (from when the name came) did not have voicemail-to-text transcription and was called that because you could SEE the list of messages on a video interface.
https://www.lifewire.com/what-is-visual-voicemail-3426762
https://en.wikipedia.org/wiki/Visual_voicemail
__________
If they were referring only to voicemail-to-text transcription, they are wrong. That can be INCLUDED in a "Visual Voicemail" service, but is not what visual voicemail means.
Google Voice does have "visual voicemail" (list of messages on the website) as well as having voicemail-to-text transcription (website, text, and email). Both my wife and I have Google Voice numbers and I appreciate both the text and email transcriptions I receive.
Click to expand...
Click to collapse
:good:

Working on one plus 6 with magisik module. Posting your work in one plus forum.

saxena1 said:
Working on one plus 6 with magisik module. Posting your work in one plus forum.
Click to expand...
Click to collapse
thats fine just please don't forget to mention where you got it from

syndre said:
thats fine just please don't forget to mention where you got it from
Click to expand...
Click to collapse
Already mentioned you name
please update your post regularly ?

saxena1 said:
Already mentioned you name
please update your post regularly
Click to expand...
Click to collapse
I just finished one
there's new framework file being used now. I never had problems with the nougat version, but some on the V20 board have been having issues, so I switched the file in the zip to the newer one.
I suspect these LG phones work fine on stock ROMs (my original intention) with the nougat framework ive been using all along, and that other devices are the ones not working properly without the updated Oreo framework.
I don't really have any way to test on phones I don't own, so I'll have to rely on you guys for help. I've included both Nougat and Oreo frameworks now attached to the top post. All the zips dated October 8th have the newer 8.0 framework

syndre said:
I just finished one
there's new framework file being used now. I never had problems with the nougat version, but some on the V20 board have been having issues, so I switched the file in the zip to the newer one.
I suspect these LG phones work fine on stock ROMs (my original intention) with the nougat framework ive been using all along, and that other devices are the ones not working properly without the updated Oreo framework.
I don't really have any way to test on phones I don't own, so I'll have to rely on you guys for help. I've included both Nougat and Oreo frameworks now attached to the top post. All the zips dated October 8th have the newer 8.0 framework
Click to expand...
Click to collapse
How do I get VM to show up in the Google dialer?
I have my stock T-Mobile VM app installed.
Sent from my LG-H932 using XDA Labs

Contacts installed fine, but not the dialer. I get "App not installed". Anyone know how to fix this?

This may be a silly question, but is there an APK version of this that I can install without TWRP. My v30 isn't rooted and I've done that in the past with my Google phones but I'd be a little nervous to do it with this one in case I bricked it.

nobdow said:
This may be a silly question, but is there an APK version of this that I can install without TWRP. My v30 isn't rooted and I've done that in the past with my Google phones but I'd be a little nervous to do it with this one in case I bricked it.
Click to expand...
Click to collapse
This doesnt need root or TWRP. Just download and run the apk.

You don't need root? I've got no where to put the zips (but I don't have root)
The APK for contacts installs but phone does not install on my v30 h933 - the package installer sometimes doesn't even give an error and other times it just says "not installed".

I can't get the apk to install either.
Sent from my LG-H931 using Tapatalk

Yeah, can't get it to stick on a stock 932.

You can use this without root, but the bootloader must be unlocked and TWRP installed. Unlocking the bootloader and installing TWRP doesn't require you to install a root app like Magisk.
For those who want to use the Google Dialer (aka Phone) without unlocking the bootloader - I used Martin.077's patched copy previously. With that version though, you'll have to wait for them to update it - it can't use the updates from Google in the Play Store. Google Contacts will install and update from the Google Play Store without any modifications.