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

[ROM] Liberation v3.0 [Updated 01/06/2012]

Liberation
"Free yourself from your carrier"​
Features:
[ROM Base] HTC Droid Incredible 4.08.605.2
Android 2.3.4
De-bloated
Deodexed
Battery percentage
4-in-1 advanced power menu
Removed E911 location icon
Red scrollbar and overscroll glow to complement the Incredible's looks
Zip-aligned for optimal memory management
CDROM.ISO removed (prevents that annoying Verizon install prompt when connected via USB)
Uses edify script, will flash in Clockwork Recovery 2.x and 3.x.
Removed Apps:
Adobe Flash Player (install from Android Market if you want it)
Adobe Reader (install from Android Market if you want it)
Amazon MP3 (install from Android Market if you want it)
CityID (annoying 3rd party bloatware)
Facebook (install from Android Market if you want it)
Slacker Radio (install from Android Market if you want it)
QuickOffice (for those who want a free Office reader, try Documents to Go from the Android Market)
Verizon Bloatware (My Verizon, VCAST App Store, Verizon Navigator, Verizon Skype, Verizon Backup; most can be installed via Android Market)
Youtube (install from Android Market if you want it)
Downloads:
Liberation v3.0 - 143.08MB
MIRROR (provided by BrettApple)
Changelog:
v3.0 (January 6, 2012)
Based on the latest official RUU - 4.08.605.2 (Android 2.3.4)
Red scrollbar and overscroll glow to complement the Incredible's looks
v2.0 (September 20, 2011)
Based on the latest official RUU - 4.06.605.3 (Android 2.3.4)
System hardware information corrected in about phone (bug with official OTA)
Removed Sprint section/tile from Market, replaced with Verizon (bug with official OTA)
Only 688MB available to user (see explanation in FAQ)
No longer patched to block Android Market malware (Android 2.2.2 and above are immune by default)
v1.1 (June 25, 2011)
Added battery percentage meter.
More efficient compression (smaller file size)
v1.0 (May 19, 2011)
Initial Release based on November OTA (3.21.605.1)

FAQ:Q: What was the difference between the standard and enhanced versions of Liberation?
A: In simple terms, Liberation Enhanced was deodexed, while the standard version was not. However, since the Gingerbread update, HTC has deodexed the /system/app folder, but has left framework odexed. I've decided to just deodex everything instead of having two separate versions with minimal differences in available storage, but vast differences in customization.
Q: Why is the Android Market outdated!?
A: If I insert the latest market, it won't update on its own, meaning more work for you. The version of the market I'm using is outdated, but auto updates. It will update in the background the first time that you run it, and should be updated within 2-5 minutes depending on your connection. You'll need to exit and re-launch the Market for the update to take effect.
Q: Some of my Google Apps (such as Gmail) are an old version, but don't show up on the Market as installed or needing an update. How do I fix this?
A: This is a bug or "feature" of the stock ROM, I'm not sure which. However, it as a very easy fix. Simply open Gmail from the Android Market. From there, scroll down to "Developer Info" and select "View Applications." This will display all of Google's apps in the market. Scroll down and update every app that shows as needing an update (they'll all display correctly from here). You may also want to disable automatic updates from here.
Q: Why isn't <insert app here> removed, I consider it to be bloat!
A: HTC did their best to put together an experience utilizing their Sense software. I left that intact as every user will get something out of it. Some use Friend Stream. Some use only Facebook/Twitter/Flickr. There is no perfect combination as every user wants something different. My goal was to present a stock experience without the carrier bloat. There are ways for you to remove unwanted apps yourself if you'd like.
Q: Why aren't there any screen shots?
A: It's a stock ROM. I've done nothing to differentiate this ROM in appearance from what your carrier/OEM ships.​

How to customize Liberation BEFORE you flash:
Materials
Windows - 7-ZIP
Linux - nothing
Mac OS X - nothing (note, I have not done this on Mac OS X, so I cannot support this OS)
Steps
Download the above mentioned file(s) for Windows. You can use a different archive manager if you'd like, but my guide is based on using 7-ZIP.
On your desktop, create a folder named "Test." You can name it whatever you want, but I'll be referring to it as "Test" in this guide. If you are new at this, you need to follow the guide to the letter.
Find your downloaded ROM and extract it to the Test folder. The easiest way to do this on Windows is to open the ROM, highlight all of the folders/files (CTRL-A), copy (CTRL-C), then open the Test folder and paste (CTRL-V). Give it a minute to extract the contents.
Once you complete step three, modify the ROM to your hearts content (see details below). Once complete, proceed to step five.
Open the Test folder and highlight everything (CTRL-A). Right click and select "Add to Archive." This will open 7-ZIP's archive manager. On Linux or Mac OS X, just right-click (or equivalent) and select "Compress."
In the options menu that comes up, leave everything at default except the following. The filename should be Test.zip (change Test to whatever you want). Archive format should be zip. Compression level should be ultra. That's it.
Once done, you can copy this zip to your SD card and flash as normal. Keep in mind that I am not responsible for any changes that you made in this ROM, so make sure you Nandroid BEFORE you flash.
Specific Modifications (using the above instructions):
Ringtones - While the ROM is unzipped, open the test folder and look for /system/media/audio. Within this folder you'll see several more folders (Ringtones, Alarms, Notifications). Any should files you put here will show up in the system when you go to change your ringtone (or whatever corresponds to the folder). The benefits to this modification include; no storage space used up in internal, phone, or SD storage; ringtone works even if SD is USB mounted, no errors when the SD card corrupts or is in use. The ringtones (alarms/notifications) are stored in a partition that does NOT count towards your file storage
Replacement "stock" applications - If you use a differnent web browser (like Dolphin HD or Firefox), or a different SMS/MMS program (like Handcent or Chomp), then it is recommended that you remove the stock applications before flashing. This prevents conflicts, slowdown, memory usage, and the annoying popup where you have to constantly re-choose your default application. In these examples, you are looking for /system/app/browser.apk and mms.apk.
Add/Remove apps you don't want - Navigate to /system/app, and remove any APK files that you don't want. If you don't know what app it is, do NOT remove it
Modify Bootup Animation/Sound - Navigate to the /system/customize/resource/ folder. In there, you will see two files; VZW_bootanimation.zip an VZW_Droid.mp3. These files are the bootup animation and "Droid" noise. Simply delete the MP3 if you want a silent bootup. It really is that easy. Replace the ZIP File with another zipped animation (must give it the same name) to replace the animation with one of your own. NOTE: Make sure you verify compatibility. If unsure, don't do it.

Files needed for UOT Kitchen:
Download - framework-res.apk
Download - com.htc.resource.apk
Download - SystemUI.apk
The above files are needed for the UOT Kitchen. Ask questions in this thread if don't know how to use them. UOT Kitchen allows you to change visual elements of your phone's stock interface in a way that no launcher app ever could.

jaykresge, you gonna get anything going with this gingersense leak?

Why is this based off the November OTA? Use the new gingerbread leak!!
Sent from my ADR6300 using XDA App

josh0426 said:
jaykresge, you gonna get anything going with this gingersense leak?
Click to expand...
Click to collapse
I'll mess with it.
tjrocks91 said:
Why is this based off the November OTA? Use the new gingerbread leak!!
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Need to have the stable release out before the test/beta releases

This seems like a cool idea. Looking forward to the download links.
Sent from my PC36100 using Tapatalk

I agree.
I would love to see a ROM of yours based off of the Gingerbread Leak.
Nothing Special is the fastest and most stable ROM out. Hands Down.
I use it as my Daily Driver in a business setting and its perfect.

rosser725 said:
This seems like a cool idea. Looking forward to the download links.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Liberation is uploading right now, should be available in a few minutes. Enhanced is still cooking, might be another 30 minutes or so. As for the "cool idea," this is actually just a renamed update to an existing ROM. See below.
tincbtrar said:
I agree.
I would love to see a ROM of yours based off of the Gingerbread Leak.
Nothing Special is the fastest and most stable ROM out. Hands Down.
I use it as my Daily Driver in a business setting and its perfect.
Click to expand...
Click to collapse
I'm cooking Liberation Enhanced right now, then I'll immediately start playing with the leak. We've seen a few developers upload flashable versions already. I can't commit that I'll release anything on this leak at this point. Let me play with it some and then I'll comment on it.

Both 1.0 ROMs are up based on the November OTA. Currently toying with the leak, will update.

Re-cooking then uploading the beta for 2.00 based on today's Gingerbread leak. Use at your own risk.

I agree with tincbtrar.

Liberation Enhanced v2.00 BETA, based on today's Gingerbread leak, is now up. Use at your own risk.

jaykresge said:
Liberation Enhanced v2.00 BETA, based on today's Gingerbread leak, is now up. Use at your own risk.
Click to expand...
Click to collapse
Downloading now, Thanks.

I'm liking some of the changes. Reboot time (after initial flash) is insanely fast. HTC Car Panel now works in both portrait/landscape, however, most other apps still don't. Feels smoother than 2.2 (and I just did clean flashes of all of my ROMs, it's definitely smoother).
Let me know what you think, but so far, feels good for a beta. I'll make it my daily driver for the next few days and see what happens.

Downloading the beta now. Already a few out there, but I know you put out good work, and it's the slimmest so far. Fingers crossed, already put the new radio on. This is great! Long live the Incredible!

Will definatly give this a try when I get home.
Only thing that stinks is the cool mods (Pulldown Toggles, EVO Camera, ETC) wont work with the beta correct? Those pulldown toggles are amazing for me (Flashlight, Bluetooth and Sounds - especially)
Once that gets sorted out Ill be using your beta. Until then maybe ill flash Liberation for fun.
Great work sir.

Is 2.0 deodexed?
Sent from my ADR6300 using XDA App

BrettApple said:
Downloading the beta now. Already a few out there, but I know you put out good work, and it's the slimmest so far. Fingers crossed, already put the new radio on. This is great! Long live the Incredible!
Click to expand...
Click to collapse
Just an FYI, it works fine with the existing radio. I won't be pushing users to update radio/hboot/etc. until the official release comes out.
tincbtrar said:
Will definatly give this a try when I get home.
Only thing that stinks is the cool mods (Pulldown Toggles, EVO Camera, ETC) wont work with the beta correct? Those pulldown toggles are amazing for me (Flashlight, Bluetooth and Sounds - especially)
Once that gets sorted out Ill be using your beta. Until then maybe ill flash Liberation for fun.
Great work sir.
Click to expand...
Click to collapse
I'm going to work on getting an Evo camera working for it. As for flashing Liberation, it's just Nothing Special under a new name (and the minor change of Car Home switched for Car Panel). All of the mods you used on NS will work here
cabjmb said:
Is 2.0 deodexed?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Yes.

Non-neon Gapps (Android 4.2) dev-discussion thread

Yes, this is a discussion thread, but you are not allowed to make "meaningless" posts in here.
If you have made some discoveries post it, but no one in here is interested in "thank you" posts or similiar.
Okay, let's try to get the Android 4.2 gapps working as good as possible on our phone.
As you know Google dropped support of non-neon phones and tablets with Android 4.2.
Our Tegra2 SoC doesn't support these neon instructions, which results in a couple problems with the default gapps package.
We need to replace a couple files with older ones to get everything back working.
Update 27.04: I finally found some time to work on gapps and provide a (hopefully) fully working non-neon gapps package in the second post now!
One example: the biggest annoyance is probably the dying keyboard.
This happens because the gapps package replaces the libjni_latinime.so file included in the ROMs with a proprietary one by Google to enable Gesture input.
Unfortunately it does need neon, so you should remove the file inside the gapps package (/system/lib/) before flashing it.
In the logcat you'll usually see a SIGILL error, like this one:
Code:
A/libc(3910): Fatal signal 4 (SIGILL) at 0x4f6233a6 (code=1), thread 3910 (putmethod.latin)
I/DEBUG(92): signal 4 (SIGILL), code 1 (ILL_ILLOPC), fault addr 4f6233a6
I'm starting this thread to colloborate together on a gapps package with as much stuff working as possible, so if you do have any insights please share them
You can download the CM10 gapps package and get the nonneon files (they're in /optional/nonneon) - but not all of them are still working with Android 4.2.
P.S.: For the love of God, don't call them fapps - fapps is a foss (free and open source) package which uses OpenStreetMaps instead of GMaps and so on.
We still want gapps, just without neon libs.

Okay, here's my non-neon fixed gapps package.
Important: If you already flashed another gapps package do format /system, reflash your ROM then reflash these gapps.
If you don't do that you'll have leftovers from the former package, which results e.g. in a dying keyboard.
Changes compared to the official package:
Fixed the aosp keyboard crashes
Fixed Google Talk videochat crashing
Fixed Faceunlock
Fixed Google TTS
Fixed Google Now & Voice Search crashes on non neon devices & restored hot-word detection
Fixed Talkback
Removed unuseful stuff
Notes:
Swipe keyboard won't work - nothing I can do about that.
Complain to Google for dropping non-neon support
Same thing goes to Photoshpere - no neon: no love.
Don't try to update Google Now - the new version doesn't properly work without neon (not sure if this still applies?)
Download:
http://goo.im/devs/tonyp/non-neon-gapps
If you're interested in more details what parts I changed - here you go.
This will hopefully ensure that future gapps versions will get provided as well
to fix facelock: replace libfacelock_jni.so with non-neon lib (credits: Adam77Root)
to fix the keyboard closing: remove libjni_latinime.so
to fix google videochat: added libvideochat_stabilize.so, replaced libgtalk_jni.so with non-neon lib and removed libgtalk_stabilize.so
to fix TTS: replaced libpatts_engine_jni_api.so with a non-neon lib and GoogleTTS.apk with the apk from the teameos gapps package.
to fix Google Now and Voice Search I replaced the QuickSearchBox.apk with this one by Steady Hawkin.
Note that the newest Google Now version isn't compatible with non neon devices anymore, thus this version disables the auto-update.
replaced Talkback.apk with a working version from the eos gapps package.
Partial credits for steps 1-4 go to bubor who already started with a non-neon gapps package.
Then I reflected these changes in the 70-gapps.sh backup script.
That's important because otherwise updating the ROM will break the gapps!
Why? Updating the ROM does wipe /system - only the files which are in the script will retain.
This means that e.g. the libvideochat_stabilize.so will poof away and the libjni_latinime.so won't get updates anymore.
Additionally I removed the g.prop file in /system/etc to prevent the GooManager from trying to update the gapps package if new (neon) updates come.
To reduce the package size I completely removed the photosphere stuff.

Just a thought here: since our cpu does not support neon instruction set, wouldn't it be an option to patch the P990's kernel with an neon-emulator? This way, the neon instructions will be translated into something the cpu can process. Corrrect me if I'm wrong.
I'm saying this because I've seen something similar happen on Mac OS X, where version 10.8.x requires a cpu capable of SSSE3 (not SSE3) instructions. They have patched the kernel with an SSSE3 emulator so that it works on older hardware and AMD cpus.
Sent from my LG-P990 using xda premium

Robin2 said:
Just a thought here: since our cpu does not support neon instruction set, wouldn't it be an option to patch the P990's kernel with an neon-emulator? This way, the neon instructions will be translated into something the cpu can process. Corrrect me if I'm wrong.
I'm saying this because I've seen something similar happen on Mac OS X, where version 10.8.x requires a cpu capable of SSSE3 (not SSE3) instructions. They have patched the kernel with an SSSE3 emulator so that it works on older hardware and AMD cpus.
Sent from my LG-P990 using xda premium
Click to expand...
Click to collapse
I'm thinking about the exact opposite - try to disassemble the libs, replace the neon instructions and reassemble. Not sure yet how much work it would take though...

bugadani said:
I'm thinking about the exact opposite - try to disassemble the libs, replace the neon instructions and reassemble. Not sure yet how much work it would take though...
Click to expand...
Click to collapse
this will be an horrendous work. I've seen some projects trying to hack armv6 instructions into the newer armv7 packages - it's really hard as you have to do it in smali as Google won't release it's sources.
I'm extremely full with loads of projects currently - I'm still hoping some people will take this over and try to build a nicely working non neon gapps version. this only requires trial and error, no real technical knowledge. but the interest seems low
Sent from my LG-P990 using xda app-developers app

Developer or not... But since you said yourself that "this will be an horrendous work", allow me include a little something here.
Changelog:
* All apps updated to 4.2.2 versions
* Google Play Store updated to 3.10.14
* Google Play Services updated to 3.0.25
* Gmail2.apk (Gmail) and GoogleEars.apk (Sound Search for Google Play) removed since they are available in the Google Play Store
** May require uninstalling and reinstalling Gmail and Sound Search after flashing.
* Keeps previous version's Photosphere/Picasa sync install on Mako, Manta, and Tuna.
Click to expand...
Click to collapse
From the way I see it, this horrendos work wouldn't really pay off since the earlier version of Gapps has... well... more or less everything the so-called new version has. So why bother if I may ask?
Back to you sir

Soooo, I have been looking into this for the past few days. I think I have got an understand of this that is good enough to make this work.
Since you are working so hard on CM10.1, I'll be willing to put great effort into this. Already started out with some basics, but I am pretty confident that I can make it work by the end of this week.
Will do some proper testing when it has been finished, once everything has been worked out, I'll push it public so you all can have the joy of using it in whatever way you may please

natalya said:
Soooo, I have been looking into this for the past few days. I think I have got an understand of this that is good enough to make this work.
Since you are working so hard on CM10.1, I'll be willing to put great effort into this. Already started out with some basics, but I am pretty confident that I can make it work by the end of this week.
Will do some proper testing when it has been finished, once everything has been worked out, I'll push it public so you all can have the joy of using it in whatever way you may please
Click to expand...
Click to collapse
Any news on your project?

Well, I'm a little disappointed that no one else worked on this - it's basically using Google and trial and error.
Thanks goes to massimo who has offered me some help and did some tests
Anyways, I decided to take matters into my own hands now, as I want to release CM10.1 over the weekend and don't want people to complain because they flashed the wrong gapps packages.
@natalya: If there's anything else you discovered which isn't working please provide it, but as you didn't post what you did in almost 2 weeks now I didn't want to wait anymore.
Changes compared to the official package:
Fixed the aosp keyboard crashes
(note: swipe won't work on non neon devices, nothing I can do about that)
Fixed Google Talk videochat crashing
Fixed Faceunlock
Fixed Google Now & Voice Search crashes on non neon devices & restored hot-word detection
Fixed Talkback
Removed unuseful stuff
Let me explain the steps taken so others can learn what has been done and can update gapps theirselves.
to fix facelock: I replace libfacelock_jni.so with non-neon lib (credits: Adam77Root)
to fix the keyboard closing: I removed libjni_latinime.so
(note: this diables the keyboard swiping - it will never fully work on non-neon devices!)
to fix google videochat: added libvideochat_stabilize.so, replaced libgtalk_jni.so with non-neon lib and removed libgtalk_stabilize.so
to (partially) fix TTS: replaced libpatts_engine_jni_api.so with a non-neon lib
to fix Google Now and Voice Search I replaced the QuickSearchBox.apk and added the libgoogle_recognizer_jni_l.so lib from this one by Steady Hawkin.
Note that the newest Google Now version isn't compatible with non neon devices anymore, so this one disables the auto-update
replaced Talkback.apk with a working version from the above gapps package[/url].
Note the English TTS not working, see below.
Partial credits for steps 1-4 go to bubor who already started with a non-neon gapps package.
Then I reflected these changes in the 70-gapps.sh backup script.
That's important because otherwise updating the ROM will break the gapps!
Why? Updating the ROM does wipe /system - only the files which are in the script will retain.
This means that e.g. the libvideochat_stabilize.so will poof away and the libjni_latinime.so won't get updates anymore.
Additionally I removed the g.prop file in /system/etc to prevent the GooManager from trying to update the gapps package if new (neon) updates come.
To reduce the package size I completely removed the photosphere stuff.
As for the swipe keyboard this feature requires neon-support and will not work properly on our phone, no matter what.
Known bugs:
Google text to speech doesn't seem to work in English. fixed
Download:
http://goo.im/devs/tonyp/non-neon-gapps
If you already flashed another gapps package do format /system, reflash your ROM then reflash these gapps.
This is needed to ensure nothing remains broken from former flashes.
Please give some feedback for this gapps package.
If something doesn't work don't forget to attach a logcat

Okay, I managed to fix the Google-text-to-speech engine as well by replacing the GoogleTTS.apk with the one from the teameos gapps package.
I pushed the new version online and removed the old one.
All bugs I am aware of are now fixed, if you notice anything else that isn't working please give feedback
Time to clean up the OP.

tonyp said:
[*]Don't try to update Google Now - the new version doesn't properly work without neon.
Click to expand...
Click to collapse
Play store is offering me to update Google Search after installing your CM10.1 ROM and this gapps package. Is Google Now part of Google Search so I should avoid this update too?

ciarpame said:
Play store is offering me to update Google Search after installing your CM10.1 ROM and this gapps package. Is Google Now part of Google Search so I should avoid this update too?
Click to expand...
Click to collapse
You can update it and you can use it.
Sadly it has huge lags (as in it freezes from time to time and the waiting times can be taking forever sometimes)
Sent from my LG-P990 using xda app-developers app

For those who want to use the aosp-keyboard, Google recently released Google-keyboard (witch is similar to the aosp, but fully non-neon compatible)
In the US it should be available through the play store, for the others http://dl.androidnext.de/com.google.android.inputmethod.latin.apk
our 2x learns gesture typing

Thread cleaned up.
This is the dev discussion subforum so it's not the right place to ask about specific ROMs.
If you'll find out something new for the non-neon gapps package then you can post in here, everything else goes into the other sections.
Thank you!
P.S.: I've tried extracted the new lib (libjni_unbundled_latinimegoogle.so) from the Google keyboard - it's not compatible to the AOSP one included in ROMs.
If you want to include it into the gapps package you need to rename the apk to LatinIME.apk and add the lib, then it'll overwrite the AOSP keyboard.
(I'm too lazy to update the gapps package in here for a keyboard you can simply install).

I created a non-neon gapps package with the keyboard included.
It will replace the AOSP keyboard by the very similar google keyboard (that fixes gesture typing). Everything else is like tonyps-non-neon-gapps.
Download gapps-jb-20130427-nonneon-tonyp-keyboard.zip
All credits to Google, tonyp and the others mentiont in the first post.
Have fun!
P.S. @tonyp if you want you can put it on the gooserver to the other gapps.

Latest Google Now (26/06/2013) seems to work just fine. I'm not getting those crazy UI lags I got before, if I updated Google Now from the play store

Since the files from tonyp on goo.im are down, here is the working downloadlink for non-neon Gapps:
http://tonyp.basketbuild.com/downlo...on-gapps-/gapps-jb-20130427-nonneon-tonyp.zip

New google keyboard is available: link

DJNoXD said:
New google keyboard is available: link
Click to expand...
Click to collapse
Ah good that you're reviving this thread, I've been meaning to update it with some information.
I never intended to maintain a gapps package and won't do so.
So if someone wants to follow my instructions and offer updated neon-compatible packages for 4.3 and 4.4 go ahead.
The instructions should still apply, but things may have changed a little in the newer versions so they might needs some adaption (e.g. the Talk to Hangouts transition).
Personally I include a mini/tiny gapps neon compatible package in all my ROMs which only contains the most important apps.
I've created the package quite some time ago, it is fully open sourced and can (and already is) used by everyone.
https://github.com/tonyp/android_vendor_google
I update the repo on my own accord, if someone needs a faster update pull requests are always welcome.
But gapps are capable of updating theirselves via the play store, so this usually isn't needed anyways.
I would prefer if others are using my repo and sent pull requests instead of forking and forgetting about the origin, but that's of course your choice.
To include the gapps into your own build you have to add the repo to your manifest and add the following lines to a makefile.
(it doesn't matter which one as long as it's called - an obvious choice would be somewhere in the device tree):
Code:
MINI_GAPPS := true
$(call inherit-product, vendor/google/tiny_gapps_nonneon_tonyp.mk)
P.S.: @DJNoXD This isn't directed at you, I know you're already using my gapps repo in your roms, just a headsup for other potential devs.

tonyp said:
Ah good that you're reviving this thread, I've been meaning to update it with some information.
I never intended to maintain a gapps package and won't do so.
So if someone wants to follow my instructions and offer updated neon-compatible packages for 4.3 and 4.4 go ahead.
The instructions should still apply, but things may have changed a little in the newer versions so they might needs some adaption (e.g. the Talk to Hangouts transition).
Click to expand...
Click to collapse
Hi @tonyp, I hope it's ok to revive this thread again resp. to hijack it a bit from your original intention!? Even if the origin of my following NEON related questions is founded in my lag problems with CM11 2014/11/13 build by @gucky01
gucky01 said:
http://sourceforge.net/projects/lgo...m-11-20141113-UNOFFICIAL-p990.m1.zip/download
Here we go, guys! As promised, here the first build. It`s 100% Tonys work. So we have to thank him for his great work!
All the best to you!
Click to expand...
Click to collapse
I find they fit this thread much better than any other CM10.x/CM11/CM12 ROM XDA thread. Not just one but all of those ROMs are affected by the missing NEON instruction set of the Tegra 2 SOC.
How can one prove wether a current ROM does not call any NEON instructions? Is it sufficient to see that there are no SIGILL entries in the logs?
Let's assume a dev releases a ROM that initially does not call any NEON instructions. Is it possible that updates of Google apps introduce calls of NEON instructions making the ROM misfunctional/unusable?
AFAI understood your trick to assemble non-NEON gapps is to replace shared opjects ( .so files) that call NEON instructions by their (more or less) equivalent non-NEON shared objects. Could there be Google apps or third party apps that call NEON instructions in their core binary?
If so, our P990 will not able to run them, right? I'd like to assemble a list of apps that won't run without NEON support (is there still any list?).
Do calls of NEON instructions on systems that don't support NEON always result in FCs, hot re-boots, or BSODs? Other way round: can calls of NEON instructions on systems that don't support NEON also result in lag or even heavy lag? (gmail 5.0.1 uses to take 10 seconds to start in my recently installed CM11 after the cleanest install possible; I just left the BB and system data/cal un-touched).
I am looking forward for your reply, well-knowing that you don't use the P990 as your daily driver any more for a long time now.
I wish you all a good 2015!

Of Systemless Root, Themed Apps, V4A, Busybox, Layers and Android Pay...

*******MAY 2016 UPDATE
Android Pay is working on the PureNexus May 2016 layers build
To attain this, delete the following files
com.google.android.camera2.xml
Located in system/etc/permissions
And
com.google.android.camera2.jar
Located in system/framework
*******BEGIN PRELIMINARY NOTES*******
-->To go from system root to systemless root,
please use the SuperSU Uninstaller zip linked below and not the unroot feature built into the SuperSU app
-->To fully unroot if on systemless root or system root, use the unroot feature in the apk
*******END PRELIMINARY NOTES*******
If, like me, you've become increasingly desirous of having Android Pay functioning on your rooted device, yet preserving that which you love about your custom setup (see thread title), this thread attempts to provide the resources you need to attain your objective.
For me, I believe that the tipping point came as a matter of principle...I wanted a feature from which I'll likely derive zero utility.
Let me be clear: I see no use whatsoever for Android Pay, and yet, like most Americans, I absolutely must have it.
I found myself returning to the same excuse, "I have a debit card, why do I even want this goofy feature?" That's a good question, but the answer is equally obvious...because it exists.
And I'd see yet another user getting the bloody thing to work on a rooted, custom rom. I hope you can see the urgency.
Just like the one ring to rule them all, the lure of Android Pay is really due to its power that it holds over us...
We Wants It...Stupid HOBBITSES
Many users have grown weary of wading through...
-->Disparate posts within rom threads
-->Dedicated threads for various elements of in the title of this thread, now scattered across xda like the diaspora of a lost tribe (how many Viper4android threads are there?)
-->Posts cross-linked within other threads for a given feature
My reticence would again solidify every time I read another post or series of posts about the precise means a given user went about obtaining Android Pay, and the commensurate loss of a different feature...or, no mention of a feature about which I cared.
So this thread is an attempt to redress these issues; specifically, after reading this, you should be able to have...
1.1-1.5. Systemless Root - If Using System Root
1.6. Updating Systemless Root Versions
2. Properly Themed Apps
2a. Hard-coded themed apps
2b. Theme Ready Google Apps
3. Layers
4. Viper4android that does not break your AUX jack or Chromecast
5. Busybox
6. Android Pay
1. Systemless Root
Whether you are running stock, or one of the few AOSP roms claiming to have Android Pay functioning on your device, this is your first step
If you are running a rooted rom, installing a pre-rooted rom, or want to flash a rom that is pre-rooted, to attain Systemless Root, you'll need the following resources...
1.1. The Latest Systemless SuperSU Zip (scroll to the bottom
http://forum.xda-developers.com/showpost.php?p=64161125
1.2. System Root Removal Tool /unSU
http://forum.xda-developers.com/showpost.php?p=63615067
1.3. Busybox for All Devices (scroll down to the section labeled "Busybox Installer")
http://forum.xda-developers.com/showthread.php?t=2239421
1.4. These Two Terminal Commands (have them in a notepad file, on your computer, or just, literally written down on a piece of paper)
echo SYSTEMLESS=true>>/data/.supersu
echo BINDSYSTEMXBIN=false>>/data/.supersu
1.5. To Install Systemless Root
1.5.1. Boot into Recovery
1.5.2. Install Pre-Rooted Rom + Gapps if Needed
1.5.3. Flash unSU Zip
1.5.4. Go to TWRP Main Menu, Go to Advanced, Terminal Command, type each command exactly as above, one at a time), hitting return in between each line
***you'll only do this once if you plan on staying on systemless root
1.5.5. Flash Systemless Root Zip
1.5.6. Flash Busybox Zip
1.5.7. Flash Custom Kernel if Desired
1.5.8. Fix Folder Permissions
-->Boot your device
-->Using Root Explorer or similar app, navigate to the folder labeled "su," as below...
{
"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"
}
-->Then hard press on the folder labeled "bin" and select the pop-up option for permissions, so below...
-->Set permissions to 0751, or deselect the check boxes as below...
1.5.8. Keep Reading, or...
Boot to System if This Is All You Want
1.6. Updating Systemless Root Versions
If you're already running Systemless Root and wish to upgrade to the latest version, follow these steps...
1.6.1. Flash latest version of SuperSU
1.6.2. Flash custom kernel if desired
***Note that if you omit the second step above, and wish to stay on a stock, no force encryption kernel (like one that ships with PureNexus), there is no need to reflash the kernel that came pre-installed with your rom. Just flash the latest version of Systemless Root.
2. Viper4android
2.1. Grab a Zip from the Viper4android Atmos Thread Here (some recommend the Viper4android Atmos Sony Beats Edition...so why the heck not?)...
http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137
2.2. Flash in Recovery
3. Properly Themed Apps
If one wants properly themed apps, and since the Gapps packages that allow working Android Pay are minimal, one must add them
3.1. Hard Coded Themed Apps
Using the Team BlackOut Updater (linked below), download those you want and flash in recovery...make sure to grant the app write permissions to your internal SD storage
http://bit.ly/1OcThZg
3.1.1. Download the Gapps that you want, flash in recovery
3.2. Theme Ready Google Apps
Go to this thread, download what you want...
http://forum.xda-developers.com/android/apps-games/apps-themeable-hangouts-layers-cmte-t3113192
3.2.1. Flash is recovery
3.3. All At Once in TWRP, in Sequence
You can and should flash all of these one after the other in TWRP...here are a few reasons why...
3.3.1. If you're using Gmail, and the minimal Gapps doesn't include it, you'll now have it waiting for you upon boot
3.3.2. If you've got a ton of downloaded music from Google Music, it'll still be there waiting for you if you flash Google Music during install (ie, you'll not have to download all of your music again)
3.3.3. Do you really want to set up hangouts, Google Plus (I turn off notifications and sync for this app...why do that every bloody time...), etc?
3.5. Layers
3.5.1. Install the latest version of the layers manager, and install whatever layers your want
3.6. Busybox That Works
You've already done that
3.7. Android Pay
3.7.1. Download from the Play Store, Add Cards
3.7.2. Note that not all cards will work...it's not the fault of the tools you've been given on this site...it's symptomatic of the reality that none of your cards is issued by participating Android Pay partners
4. Test Android Pay
4.1. You can download SafetyNet Helper Sample from the Play Store...
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
The app is temperamental, and can throw up a false negative...but you will get a positive result most all of the time
4.2. Buy a dang soda, pack of gum at CVS, some cheap gift from Walgreens...I don't care from where...to see if it works (it should)
5. Odds & Ends
A few items of note...
5.1. All of your previously apps granted root permission will need so again
5.2. Stay on top of themed apps...layers can never properly theme certain apps if there's a stock version in the data partition of your device.
5.3. Thank all of the devs whose tools are linked in this thread, donate to them, and be sure to buy anything that they may have for sale...they are the best in class.
5.4. Many things may or definitely will break Android Pay, even if you've set it up properly, including Xposed, theme engine, some DPI changing apps, etc. Just be mindful that this could change if you install other items.
6. Credits
@nathanchance, for being such a good dude
@inffy, for being helpful at all times, while maintaining near pitch-perfect, subtle venom
@osm0sis, for just everything he has provided
@BeansTown106, for building his rom, and not just stumbling but actually figuring out what prevented Android Pay from working on his rom
@daveyannihilation, for being such a great guy, themer, forum moderator, and finest pineapple lover I've ever encountered
@Woody, for having done the heavy lifting on most all of this prior to me
Chainfire
Viewers like you that contribute to Public Television...thanks for your support
Good luck!

Solid work! Gonna add it to my signature and I will add it to my posts as soon as I can.

Great post, and thanks for the mention!
Venom indeed flings in my veins

Thanks for posting this. Curious what everyone is using in terms of Viper Audio? I just flashed the Huawei one for now.

Subiegsr said:
Thanks for posting this. Curious what everyone is using in terms of Viper Audio? I just flashed the Huawei one for now.
Click to expand...
Click to collapse
I am using the all-in-one package by @guitardedhero

Please link to my thread, not my zip. Thanks.

osm0sis said:
Please link to my thread, not my zip. Thanks.
Click to expand...
Click to collapse
Yes sir...taken care of it.
My apologies.
Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression

Awesome Post. Really covers everything that has been asked over and over, all in one easy to read format.
On Viper: In my testing, I made several backups at each stage after I checked that AP was working. I am glad that I did, as some Viper packages break Pay functionality. I would stress caution and/or patience when flashing, as a backup only takes a few seconds to make, but can save a whole bunch of time. The Viper package that I have linked above is an older one from the N6-Proper device, so it requires Permissive. You are free to use whatever you want, but this works for me. I flashed XTREMEmusic 6.0, 6.2 and 7.3 and all 3 broke Pay. It has been noted that Guitaredhero's zip package works, doesn't break Pay and sounds pretty good. Your choice.
Me from another thread said:
As an aside, I have an almost completely stripped down /system partition as far as gapps go and have even substituted several TBO ThemeReady versions, as well as Clear YouTube. So if I were to put a wager on what trips the Pay failure [I am speaking in systemless root terms], I would lay bets on system/bin, /system/xbin, busybox configurations and changes to some shadow policy that no one has figured out. Because simply adding or removing apks from /system (not including any signature checked apks such as a modified GMusic or Chrome) and utilizing the /su folder correctly doesn't trip the Pay verification, at least not for me.
Click to expand...
Click to collapse

Thanks
Bookmarked in my tips folder.
I'm sure I'll refer to it many times.

viper4android link is down
Sent from my Nexus 6P using Tapatalk

Most excellent! U Rock on XDA!!

galaxys said:
Most excellent! U Rock on XDA!!
Click to expand...
Click to collapse
For so long you've had the Oregon Ducks cheerleaders in your signature. Good to see your "affection" for the cheer spans to other schools.

Woody said:
For so long you've had the Oregon Ducks cheerleaders in your signature. Good to see your "affection" for the cheer spans to other schools.
Click to expand...
Click to collapse
This is true...LOL! I'll continue to scout the teams!

galaxys said:
This is true...LOL! I'll continue to scout the teams!
Click to expand...
Click to collapse
Sometimes looking at the forums via browser really has its advantages.
I'm so glad I looked at this exchange...I'm quite thankful for those cheerleaders...they really want me to have my device exactly as I like it.
Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression

Woody said:
Awesome Post. Really covers everything that has been asked over and over, all in one easy to read format.
On Viper: In my testing, I made several backups at each stage after I checked that AP was working. I am glad that I did, as some Viper packages break Pay functionality. I would stress caution and/or patience when flashing, as a backup only takes a few seconds to make, but can save a whole bunch of time. The Viper package that I have linked above is an older one from the N6-Proper device, so it requires Permissive. You are free to use whatever you want, but this works for me. I flashed XTREMEmusic 6.0, 6.2 and 7.3 and all 3 broke Pay. It has been noted that Guitaredhero's zip package works, doesn't break Pay and sounds pretty good. Your choice.
Click to expand...
Click to collapse
Great summary - Thanks!
I've had no issues with AndroidPay when I've used Guitaredhero's zip package - highly recommend going that route if you want V4A. Besides, the sound is considerably better with V4A and Dolby Atmos than without!
The gotcha I had for breaking Android Pay - was not removing the SU/XBIN_BIND directory (or avoiding the creation by making the appropriate entry to the .supersu file) When I jumped from SUPERSU 2.61 to 2.66 - I had missed that step.
Also - unless you need BusyBox - (V4A doesn't need it and my understanding is Layers won't in the future) - you may want to leave it out until you have an app that requires it)

luigidk said:
Great summary - Thanks!
I've had no issues with AndroidPay when I've used Guitaredhero's zip package - highly recommend going that route if you want V4A. Besides, the sound is considerably better with V4A and Dolby Atmos than without!
The gotcha I had for breaking Android Pay - was not removing the SU/XBIN_BIND directory (or avoiding the creation by making the appropriate entry to the .supersu file) When I jumped from SUPERSU 2.61 to 2.66 - I had missed that step.
Also - unless you need BusyBox - (V4A doesn't need it and my understanding is Layers won't in the future) - you may want to leave it out until you have an app that requires it)
Click to expand...
Click to collapse
Thanks for your input, and sharing your personal experience. This kind of feedback is especially helpful.
As to removing Busybox from the list, at the moment, many Viper4android packages are compatible with Android Pay, and require Busybox...for example, even though I linked one that seems pretty popular, others work, and folks may need Busybox in order to use certain Viper4android packages.
As to the new Layers Manager not requiring Busybox, I'll definitely note that once the app goes from alpha stage to final release.
Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression

luigidk said:
Great summary - Thanks!
I've had no issues with AndroidPay when I've used Guitaredhero's zip package - highly recommend going that route if you want V4A. Besides, the sound is considerably better with V4A and Dolby Atmos than without!
The gotcha I had for breaking Android Pay - was not removing the SU/XBIN_BIND directory (or avoiding the creation by making the appropriate entry to the .supersu file) When I jumped from SUPERSU 2.61 to 2.66 - I had missed that step.
Also - unless you need BusyBox - (V4A doesn't need it and my understanding is Layers won't in the future) - you may want to leave it out until you have an app that requires it)
Click to expand...
Click to collapse
Can you link to that zip? It seems the link in the OP is down. Thanks.
Sent from my Nexus 6P using Tapatalk

micmars said:
Thanks for your input, and sharing your personal experience. This kind of feedback is especially helpful.
As to removing Busybox from the list, at the moment, many Viper4android packages are compatible with Android Pay, and require Busybox...for example, even though I linked one that seems pretty popular, others work, and folks may need Busybox in order to use certain Viper4android packages.
As to the new Layers Manager not requiring Busybox, I'll definitely note that once the app goes from alpha stage to final release.
Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
Click to expand...
Click to collapse
The V4A package at this forum: http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137 doesn't require busybox, so that is just an option. Best V4A install out there in my opinion.
---------- Post added at 04:06 PM ---------- Previous post was at 04:05 PM ----------
darkjedi said:
Can you link to that zip? It seems the link in the OP is down. Thanks.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
For V4A? If so it is here: http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137

darkjedi said:
Can you link to that zip? It seems the link in the OP is down. Thanks.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
The links in the OP all work for me...
http://forum.xda-developers.com/showthread.php?t=2952137
ViPER|Audio || ViPER|Atmos 4.1 * SQ Driver * Audiophile Profile * Beats * Huawei *
They are direct downloads at the bottom of the OP...
Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression

luigidk said:
The V4A package at this forum: http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137 doesn't require busybox, so that is just an option. Best V4A install out there in my opinion.
---------- Post added at 04:06 PM ---------- Previous post was at 04:05 PM ----------
For V4A? If so it is here: http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137
Click to expand...
Click to collapse
Excellent...I'll add this to the OP, along with the one provided by Woody.
Do you mind telling me...
1. The rom you're running
2. The kernel you're on
3. If you're SELinux is set to permissive or enforcing
Many thanks.
Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression

[UNOFFICIAL][MAGISK MODULE] Active Edge Mod for Edge Sense Plus - continuation for patch levels 2021-01-05 and later

EDIT: It's too annoying to maintain and edit 6 separate threads. The installer works across all devices, so please visit this post for the latest version: https://forum.xda-developers.com/t/...or-patch-levels-2021-01-05-and-later.4226343/
Thanks!

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.

i5lee8bit said:
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.
Click to expand...
Click to collapse
awesome work mate, love this mod. i saw ur post on pixel 4xl forum first and downloaded and flashed that. everything seems 2b working fine! but then i noticed this thread posted seperately on our phone's forum. is there any difference between them?? just wanna make sure that i flashed the rite file. thx again for all mate

vdevl said:
awesome work mate, love this mod. i saw ur post on pixel 4xl forum first and downloaded and flashed that. everything seems 2b working fine! but then i noticed this thread posted seperately on our phone's forum. is there any difference between them?? just wanna make sure that i flashed the rite file. thx again for all mate
Click to expand...
Click to collapse
Yep, you flashed the right file. Both posts link to the same zip file. The module installer, like the original module, gathers your device information and then downloads the correct file for your device and installs it. Even has an MD5 hash checksum check to make sure it's all good before installing. It was actually a really fun little project to work on, and interesting to see how Jan designed it to be semi-automated, with several fail-safe checks. For example, there's a post fs data script to also disable the module automatically if the user upgrades the system patch level and hasn't yet upgraded the module, likely to ensure the systemuigoogle mod isn't incompatible with the new update and potentially cause issues. Really well designed by the original dev!

How do I actually map it? I have installed on my pixel 4xl but it only opens an unusable google assistant UI.