[Kernel+Tweaks]FennyMod v.B1 For Cyanogen (captivateMTD)

[Kernel+Tweaks]FennyMod v.B1 For Cyanogen (captivateMTD) - Captivate Android Development

So I have a captivate as a loaner from bestbuy until my phone can be junked out and I can get a new one for free (<3 you black tie protection.) And thus I am stuck with again for a while SO... I got tired of redoing the setup I do on my Cyanogen devices every time I update a daily.
Here is the .zip I flash after every update.
Features (What it includes and the components used to do it):
Market/Google Apps (Latest 2011-06-13) From Here: http://goo-inside.me/gapps/
Email Without Exchange Security From Here: http://forum.xda-developers.com/showthread.php?t=848564
TalonMTD Kernel v0.0.1 From here: http://forum.xda-developers.com/showthread.php?t=1215876
Camera from MIUI - From here: http://forum.xda-developers.com/showthread.php?t=1066885
Modified Phone APK with an option to hide the REALLY annoying hold button. (I honestly can't find where I got this from again.)
Instructions.
Get cyanogen mod. If you have it skip to step 2. Otherwise installation instructions are here: http://wiki.cyanogenmod.com/wiki/Samsung_Captivate:_Full_Update_Guide
Once cyanogen-mod is installed, or after each daily update, flash the zip found below. (This can be done in place of the google-apps installation.)
Finally, Download Link: http://fennyfatal.com/android/Captivte.FennyMod.B1.zip
Standard disclaimer applies: Don't do anything stupid, and I am not responsible for any damages. And all credit goes to the original authors for the original mods the only one of which I created is the Exchange Security Removal.
Note: When we have an official+stable build I will start supporting this as a Full Kanged ROM as long as I have a captivate to test it on, but until then it will just be a patch.

First

Why is this thread here?

ninjuh said:
Why is this thread here?
Click to expand...
Click to collapse
The thread is here because it will be a full Rom with tweaks, but I am packaging it as an update to the existing cyanogen builds until there is a stable release to base it off of. If a mod thinks differently it can be moved.

Related

AGPS Patch HTC Thunderbolt 3.1 & 2.2 | GET RAPID GPS LOCK, CAN LOCK ONTO MORE SATS

AGPS Patch HTC Thunderbolt 3.1 & 2.2 | GET RAPID GPS LOCK, CAN LOCK ONTO MORE SATS
AGPS PATCH
REVIEW THE WHOLE THREAD BEFORE POSTING QUESTIONS.
List of officially supported devices is at the bottom of this post.
Use this if you're having GPS issues (unreliability, no functionality, etc.)
This patch provides a worldwide solution to GPS issue for multiple devices. Using a general ROM without this has resulted in 10+ minutes of GPS delay. Also, GPS lock kept being lost. By using this patch, most people experience a GPS lock within 10 seconds (2 - 20 seconds range can be expected). Typically, a device using this patch will lock onto 7 - 9 satellites. Users have reported up to 11 satellites being locked at once. Without this patch, the average satellite count is 4.
HOWTO INSTALL: (Remember to make a backup. See Notes section for what this patch does.)
Method 1:
1. Download the "ADB Push Installer". This contains all versions for the latest build and old v1.3 versions.
2. Extract the files into a specific folder.
3. Plug your device into the computer and get it ready for adb pushing. Nothing out of the ordinary required.
4. Open the batch file called "ADB Installation Script - RUN THIS" if you use Windows. Otherwise, run the Linux SH script if you use Linux.
5. Select the version you want from the list.
6. Follow the prompts to reboot. You're done.
4. Review the NOTES section.
Method 2:
1. Download the patch
2. Copy all file(s)* into /etc/ of the system (not sd-card) using ES File Explorer, Root Explorer, or some other form. You must have SYSTEM set to Mounted and Root enabled. Check your explorer app's SETTINGS to do this.
**Files will be: gps.conf & SUPLROOTCERT -OR- only gps.conf for NO-SSL builds.**
3. Reboot the device
4. Review the NOTES section.
*Files are located in the /system/ folder of the ZIP. Do not copy the other directories or folders.
Method 3 (easiest if you use a compatible version of CWR or CWM)*:
1. Download the patch
2. Boot into CWR (Clockwork Recovery)
3. Mount /system/ partition (on the main menu, select the "Mounts and storage" option, then "mount /system")
4. Flash the patch (on the main menu, select "Install zip from sdcard," then "choose zip from sdcard," and find the zip and select it)
If you receive "(Status 0) Installation aborted" this Method will not work for you. Use one of the other methods.
5. Reboot the device
6. Review the NOTES section.
*This was built for and works on Inspire 4G and DesireHD versions of Clockwork Recovery. The Google CWM Flashable Build has binaries known to work with CWM on the X8. It may work on other devices. Please message me your success if you try and flash with recovery version and phone model as part of the message.
Downloads:
SEE THE NOTES SECTION (PARTICULARLY NOTES 1,2, & 3) FOR ALL SORTS OF INFORMATION AND FACTS ABOUT THIS PATCH, WHAT EACH BUILD IS FOR, VERSION DIFFERENCES, AND KNOWN ISSUES WITH SOLUTIONS.
Recommended Builds (pick either):
Download the Google Specific No-SSL v3.1 build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific v3.1 build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Confused with all the options below? As the Notes section dictates: I recommend the GOOGLE BUILD of all devices. Other builds have changes in their SUPL server information and/or other variables pertinent to that manufacturer. These builds do not appear to operate as fast as Google build's but are available for your enjoyment.
3.x trunk Alternative Options (currently v3.1)
Download the ADB Push Installer here. (contains all current builds and v1.3 builds) (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific NO-SSL build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific CWM Flashable build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the AT&T Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the T-Mobile Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Sony Ericsson Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
*The alternate patch removes a variable that some GPS hardware on older models cannot handle. Try this if you have problems with the standard patch.
2.x trunk Alternative Options (currently v2.2)
Download the ADB Push Installer here. (contains all current builds and v1.3 builds) (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific NO-SSL build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific CWM Flashable build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the AT&T Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the T-Mobile Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Sony Ericsson Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
*The alternate patch removes a variable that some GPS hardware on older models cannot handle. Try this if you have problems with the standard patch.
Changelog: (I'll try to keep this correct and current)
Code:
v3.1 update - New Version
introduced the NO SSL version for Google build. Shows faster performance times.
v3.1(HELP WITH THE MAINTANENCE COSTS - DONATE A FEW BUCKS)
introduced my own NTP pools
repaired the LG Alternate build (was same as standard build, compilation error)
v3.0 (HELP WITH THE MAINTANENCE COSTS - DONATE A FEW BUCKS)
based on v2.2 configuration
has my own XTRA/AGPS server instead of Qualcomm
re-added two AGPS variables from v1.3 (two beta-testers saw instant results with these re-added)
re-added on USE SUPL variable from v1.3 (two beta-testers saw instant results with these re-added)
variables are now divided into sections and sections have descriptions
Code:
v2.2 update - New Version
introduced the NO SSL version for Google build. Shows faster performance times.
v2.2 (additional builds added)
added a new SUPL version using data from Sony Ericsson
added an alternate release using LG SUPL servers
added an alternate release using Google SUPL servers
updated the ADB PUSH to include new versions
fixed broken download links for the patch
v2.2
removed local AGPS variable
removed local XTRA_SERVER variable
created LG Build with LG SUPL servers (some LG ROMs fail to work with non-LG SUPL servers)
reduced redundancy in NTP and XTRA (unnecessary entries)
added newly located SUPL server to T-Mobile build
v2.1 (encompassing changes between 1.3 to 2.1)
removed two NTP server pools
removed xtra1 server
removed multiple SUPL_HOST entries
aligned SUPL_HOST with SUPLROOTCERT in each package
increased QOS timeout from 89 to 100
removed QOS standalone timeout variable
removed extra AGPS variables
Old Versions:
3.x Trunk:
v3.0 ADB Push Installer
v3.0 Google Build
v3.0 Google Alternate Build
v3.0 Google CWM Build
v3.0 AT&T Build
v3.0 T-Mobile Build
v3.0 LG Build
v3.0 LG Alternate Build
v3.0 Sony Ericsson Build
v3.0 GPS Only Build
v3.0 GPS Only Alternate Build
2.x Trunk:
v2.1 Google Generic Build
v2.1 AT&T Specific Build
v2.1 T-Mobile Specific Build
v2.1 GPS.Conf Only Build
v2.1 GPS.Conf Only Build (alternate)
v2.0 Google Generic Build
v2.0 AT&T Specific Build
v2.0 T-Mobile Specific Build
v2.0 GPS.Conf Only Build
v2.0 GPS.Conf Only Build (alternate)
1.x Trunk:
Worldwide 1.3
Worldwide 1.3n (alternate)
North America 1.2
Worldwide 1.2
Worldwide 1.2n (alternate)
North America 1.1
Worldwide 1.1
Worldwide 1.0 (not recommended)
North America 1.0 (not recommended)
Rules For Posting Questions:
Read the Notes Section first. I will refuse to answer questions that can be answered by some reading. If it is based upon something in the Notes Section, REFER TO THE NOTE when asking.
Answer the following questions: What ROM you are using?, What kernel are you using?, What GPS apps you have installed?, Where is your general location?, Are you using a case?, Has your GPS worked fine before?, Does it work fine with some apps and not others?, What else happened around the time your GPS stopped working? -AND- Have you reviewed the Notes Section?
DO NOT criticize the user of custom third-party NTP pools and xtra.bin data as dangerous. You obviously HAVE NOT read the Notes section OR reviewed the concurrent branch 2.x to discover it offers the standard NTP pool and Qualcomm-based xtra.bin server.
Don't indulge yourself in ignornat posts. Provide information that may be relevant to helping. Simply stating "this stopped working" or "I can't get it to work" helps nothing and only annoys other readers AND those who may be willing to help you just will not do it.
NOTES Section:
This patch will work with virtually all Qualcomm, Android phones and has been reported to work with other chipsets as well. That means hundreds of devices could see a benefit to GPS performance from this patch.
This patch has various objectives to ensure stability and efficacy with GPS. Locally, the patch will replace your /system/etc/gps.conf and your /system/etc/suplrootcert if you have this file. You can compare the difference in what you have to this one to get an idea of all the changes. V3.1, onward, contains section descriptions for variables in use. Most notably, starting with v3.1 the aGPS Patch uses my own central NTP DNS pool and my own central xtra.bin server by default. The xtra.bin does have fallback servers should mine fail. But, that is very, VERY much an unlikely scenario. These two imperatives allow for better stability and speed by providing top-rated NTP servers and prime-routed network access to transmit the xtra.bin to your phone.
I recommend the GOOGLE BUILD of all trunks. However, you can use any build with any phone. You may have good luck with specific builds that do not fit your phone or carrier criteria. If you're curious, test it and see.
This works with ANY ROM unless the ROM has aGPS and/or GPS disabled in the code. This happens with CMx nightlies and some betas! I cannot fix this, neither can you.
Remember, this has to be reflashed when you update or change ROMs.
Short patch history: The 1.x trunk only flashed a modified gps.conf file which relied solely on Qualcomm and NTP.ORG. Starting with 2.x, a gps.conf and a matching SUPLROOTCERT file for SUPL server authentication is included. The 3.x trunk offers the same as v2.x but adds better sourcing for NTP data and for the xtra.bin file; it utilizes my own server to do so.
Why toss out SSL?Whether or not you have a current SUPL certificate is questionable. Some have expired. Some will expire soon. Either way, the servers may provide SSL access without proper certificates depending upon configuration. That aside, I have found that SSL and secure communications over data networks slows the response times. I see no reason to use SSL for location information. If someone has a logger to obtain your location, SSL will not assist in stopping it. The bad app will continue to obtain your information by "stealing" it and you have more problems than a simple SSL-SUPL communications leak.
NO-SSL Builds will not have a SUPLROOTCERT because these builds do not use SSL. The SUPLROOTCERT is a certificate used for authentication of SSL connections. There is no need for this file for the GPS at this point.
IF you have issues with v2.x or v3.x, your ROM might require more variables. Try the old worldwide v1.3 version in this instance.
IF you still are facing issues, it might be that your GPS hardware is very much outdated. Try any "Alternate" build to see if this helps.
CMx ROM users may not experience benefits from this patch. However, we have had good reports from CM users with one negative one. Remember to do all of the steps when flashing and the following notes are important too!
Reports indicate that this patch DOES WORK with the next iteration of Android, Jelly Bean. This patch has worked from Android 2.2 (Froyo) up through Android 4.1 (Jelly Bean). Therefore, it works with all iterations on the market. I will remove support as soon as it is confirmed to NOT work with a new version of Android.
Reports show that certain ROM's including some CM builds require a modification in the build.prop. You need to change "ro.ril.def.agps.mode = 2" or "ro.ril.def.agps.mode = 0" to be "ro.ril.def.agps.mode = 1" in order for aGPS to properly function. Only do this IF YOU ARE HAVING PROBLEMS after attempting the standard patch.
Your phone "learns" about the individual GPS satellites. This is part of the aGPS design. Don't be surprised if the first time you use GPS Status that it takes 20+ seconds to "lock".
I have read a lot that indicates that it is best to let your GPS run using any application for a while to "learn" aGPS information. I let GPS Status run for about 10 minutes (it has an option to disable the screen timeout, which I do) each "first time" to learn. I say each because I test a lot of tweaks and fully reset/delete GPS cached information to start retesting.
Remember, this has to be reflashed when you update or change ROMs. Each ROM will have its own gps.conf, normally not suited to all devices.
I use GPS Status to test my signal strength. It isn't 100% accurate, but it gives a very good sense of how the GPS is performing.
If you're wondering why GPS is slow on certain apps? Or, you show up as on a street when you're 6 meters away from it? Well, those apps process GPS data differently which is out of anyone's control except the app developer. Certain apps will force your location to a street until you pass the app error threshold. Food for thought.
DO NOT USE ANY OTHER GPS FIXING APPS with this patch. If you do, and you still have problems, I cannot help you. A number of these Apps will overwrite what my patch does dynamically.
Variables are described starting in v3.0. Open up gps.conf in a text editor to read about what variable sections are for. It isn't in-depth, but should be enough to help you get a general understanding.
Still having weak GPS reception? Take your case off. Cases have been known to affect signal, though some argue against it. Personally, I get 3 more sat's when I remove my case.
There is a reported variable that can cause some GPS units not to work as well as it should with this patch. This is very odd as it's hit-and-miss and only seems to cause problems on less than 10% of handsets. This doesn't mean it screws up anything! It's possibly an older piece of GPS hardware incompatible with this variable. Have no fear, v1.2 will remove this variable for the worldwide version. This issue is more prone to occur in DHD.
Tried taking the battery out for 30 seconds? Some have reported that their phone required the battery to be removed. First, power off the device. Second, remove the battery for 30 seconds. Third, put it back in and give it a try. I cannot explain this except for possible cache clearing.
Some Inspire 4G and DHD devices have hardware problems. There is a known problem that the spring connectors to the GPS antenna sometimes are out of place or quit touching. http://forum.xda-developers.com/showthread.php?t=1101066 provides a video on self-repair.
An error in flashing this patch means that this method will not work for you. Use one of the other methods for flashing this patch. Don't ask why or for a fix. There are hundreds of variations of recovery systems and update binaries. I do not have the time or desire to support them all. This is why I describe other install methods. Reference error: E:Error in /sdcard/android apps/agps.patch.google.build.nossl.v3.1.zip (Status 0) Installation aborted.
Location is way off? Like, not near you at all? This means your GPS is not actually being used. Try the following to resolve it: Goto Settings -> Locations and disable ALL options. Reboot into recovery. Clear Cache and Dalvik Cache. Reboot normally. Go back to Settings -> Locations and only enable GPS. Reboot once more and try your GPS again. If this didn't work, did you read all of the Notes such as the one about the battery or RIL?
Donations: If you wonder why I asked for donations, it's simple. Users of v3.x are gaining extra, noticeable benefit over v2.x. This comes at a cost to someone. I pay the bills to provide a reliable data setup to transmit the xtra.bin data file and to provide the top NTP SERVERS in one DNS pool. To help keep this going, I just ask for the user to consider a donation. Nothing more, nothing less. Thank you for your consideration.
AGPS Patch Officially Supported Devices:
Acer Iconia
Asus Transformer Prime
Asus Transformer (TF101)
Asus Transformer TF300T
HTC Inspire 4G
HTC Desire HD
HTC Sensation
HTC Incredible S
HTC Salsa
HTC Flyer
HTC Evo 3D
HTC Desire S
HTC Wildfire
HTC Wildfire S
HTC Droid Incredible 2
HTC Thunderbolt
HTC Desire
HTC Desire Z
HTC One X
LG GT-540 OPTIMUS
LG Optimus One
Motorola Triumph
Motorola Droid X2
Samsung Galaxy S II Skyrocket (SGH-I727)
Samsung Galaxy S II (I9100)
Samsung Galaxy S II (SGH-T989)
Samsung Galaxy S Plus I9000
Samsung Galaxy Nexus
Samsung Galaxy S III (AT&T, Rogers, Bell, Telus)
Samsung Galaxy S III I9300, I9305
Samsung Galaxy S 4G
Sony Ericcson XPERIA X8
* I do not officially support all devices that this patch is known to work on at this time. You may private message me your success story for official support considerations.
Thanks Section
While this has gone a long distance since its inception, I want to still send thanks to Angeldeath for permitting me to take his early work and start tweaking it for HTC Inspire 4G users. This inevitably led to what we have here today.
Thank you to all those who joined and participate in the testing community. Without their help, I couldn't get enough data to know how well this works on different devices and in various regions of this planet we call Earth.
Thank you eagleeyetom, husky69, and tamagotono for their work in building an ADB pushing environment for Windows and for Linux respectively.
If you are happy with the patch and find this thread useful, please consider pressing the "Thanks" button on any of my posts on this thread. You may also consider rating this thread with five stars if you're satisfied. You may do so just below "Search This Thread" on the right-side at the top of this post. Donations are appreciated (See last NOTE)
REVIEW THE WHOLE THREAD BEFORE POSTING QUESTIONS.

Currently: this is a tentative supporting thread for my aGPS patch. Assuming more report success, I will start officially supporting this device.
Please let me know your success rates. Thus far, a few people have sent me messages and emails stating that this patch works great on this device.
As such, I'm thinking it would be good to provide this officially for this device.
This has been used on over 40 devices successfully. I don't offer official support for all devices. Rather, I offer official support once users convince me to do so for that particular device. That happened here.
Statistically, here is part of my post from mid-December on all official threads:
So, let me give you a general update directed to those 3.x trunk users:
My server has automatically generated an xtra.bin file for your GPS excitement 3,980 times since September 26th when the first beta went online to test it out.
My server attempts to build a new version every 30 minutes. Depending on what it can decypher from other xtra.bin sources, it provides a totally fresh xtra.bin approximately every 1.2 hours.
My server has served up over 500,000 xtra.bin files to users like you on XDA since v3.1 was released.
My server continues to provide a reliable NTP pool to v3.x users by directing your phones to a handful of RELIABLE and FAST-RESPONDING NTP servers around the world. This ensures you can travel and not have to switch NTP pools.
Click to expand...
Click to collapse
Enjoy!

Which one do I pick if doing cwr?
Sent from my ADR6400L using Tapatalk

Turd Furguson said:
Which one do I pick if doing cwr?
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
Any of them should flash with CWR. Almost all were built with CWR binaries. CWM builds use its binaries and are the only ones different from CWR flashables.
I use and recommend the Google Build to all users. Others are just for those wanting to be more in tune with their cellular network. That's a false hope usually.

Any tips to see how many satellites I am hooked up to prior to this patch for verification?
Sent from my ADR6400L using Tapatalk

Turd Furguson said:
Any tips to see how many satellites I am hooked up to prior to this patch for verification?
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
If you have not flashed yet, you can run GPS Status (app from the Market) to see. Then, run the same app afterward.

Does the patch need to be installed each time you change a ROM or is it a permanent change?

Turd Furguson said:
Does the patch need to be installed each time you change a ROM or is it a permanent change?
Click to expand...
Click to collapse
It has to be reinstalled each time as the ROM will require a partition format OR will replace the patch files with its own.

Any testers out there with results positive or negative? This is the last device I have to determine to support or not to support officially.
I'd like to do so, but I need to know that it's good to go and helpful.

I will look in to this a little more tomorrow. I never had a chance today.

I can confirm this patch works. Great job on this!!!

nowetdio said:
I can confirm this patch works. Great job on this!!!
Click to expand...
Click to collapse
Very glad to hear that my suspicions are being confirmed!
I hope to add this to official support soon, like I said.
Otherwise, the first post has been updated to include some more information especially in the Notes section.

All threads have had an overhaul that was way overdue.
High points:
Note discussion of what the patch does and what it replaces.
Note confirming ICS support from various users.
Note section has gotten long, but covers most questions I am repeatedly asked.
A total of 9 officially supported new devices.
Download section reminds people to backup their settings. You only need to backup /system/etc/gps.conf and /system/etc/suplrootcert if you have one. But, I never had to revert!
That being said, welcome to official support. Thank you all who confirmed and worked with me to ensure it was proper to offer official support to this device.
As always, please don't forget to click Thanks if you use or like this patch -AND- don't forget to Rate the thread. Donations are always welcome.
EDIT: Method 1, the easiest of the methods for those unfamiliar with file managers or recovery, has been updated. Some people required that the script also mount the partition. I have added that line to all options available and updated the ZIP file. Thanks enigmaamit for confirming that the new PUSH script works.

Using shifts3nse ROM, stock kernel, wifi off. All 3 GPS options ticked.
Stats via GPSstatus(with out patch)
6-7 Sats locked
With patch
No lock, 0 Sats.
I installed the google build, for CWM. I changed the mount to /system, everything installed fine.

Thacallmehess said:
Using shifts3nse ROM, stock kernel, wifi off. All 3 GPS options ticked.
Stats via GPSstatus(with out patch)
6-7 Sats locked
With patch
No lock, 0 Sats.
I installed the google build, for CWM. I changed the mount to /system, everything installed fine.
Click to expand...
Click to collapse
I'm quite curious why you installed this patch. The first post, third line and in bold, I quote myself:
crypted said:
Use this if you're having GPS issues (unreliability, no functionality, etc.)
Click to expand...
Click to collapse
What was your issue with your GPS reception prior to flashing it? You say you locked on 6-7 sats. Was there a large error range?
You say you have Wifi disabled. Do you have a data connection at all?
Where are you located and what are your surroundings like?
Can you try and flash an "Alternate" build version to make sure you aren't being buggered by a known issue with older GPS hardware? This is
discussed under each download section and in the Notes.

How do I check how many sat I have?
Sent from my ADR6400L using Tapatalk

Upstreammiami said:
How do I check how many sat I have?
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
Download and view them via the Android Market app "GPS Status".

I have 9/9 using zues rom with Ziggy kernel without this patch
Sent from my ADR6400L using Tapatalk

Upstreammiami said:
I have 9/9 using zues rom with Ziggy kernel without this patch
Click to expand...
Click to collapse
Consider yourself lucky and happily a part of an extremely small minority to not have problems!
As the third line of the first post on this thread states, this is to assist those who do have issues. Unfortunately, many of us are plagued by a crap GPS without doing something to fix it...

crypted said:
I'm quite curious why you installed this patch. The first post, third line and in bold, I quote myself:
What was your issue with your GPS reception prior to flashing it? You say you locked on 6-7 sats. Was there a large error range?
You say you have Wifi disabled. Do you have a data connection at all?
Where are you located and what are your surroundings like?
Can you try and flash an "Alternate" build version to make sure you aren't being buggered by a known issue with older GPS hardware? This is
discussed under each download section and in the Notes.
Click to expand...
Click to collapse
1. I'd lose signal from time to time.
2. I'm testing this- thats why. Your curiosity isn't important.
3. This is a sat test right? No need for wifi connection.(All tests were done with wifi off)
4. I have good 3g service where I live.
5. I flashed 3.x google and 3.x google alt. As well as, 2.x for both. Still the same result.

[MOD][APP]LP/KK/JB/ICS Email APK with Exchange Security removed (Updated May 2015)

(edited some content and added a few more instructions on May 25 2015)
I initially posted this when my employer changed their policies to require device admin access to people's phones if they wanted to access company emails or calendars. Spent a few days reading the android source code and came up with a working apk.
This app removes the annoying popup saying that you need to give it admin permissions and add a numeric password. It also does not set any additional policies other than what you already have set on your device. It does not make the email app a device admin.
The app tells the server what it wants to hear - which is they have total control over the device, but it doesn't really do anything on the phone.
DISCLAIMER: I'm not responsible if:
You get fired (a very real possiblilty - companies fire people for far less than "circumventing security" even though most of us know that regular folks' emails have nothing valuable to the competition.
If you get in other sorts of trouble for using this
if this melts your device down or breaks it in any fashion or your ROM gets corrupted.
USE THIS AT YOUR OWN RISK.
How to install:
Copy the files onto your phone storage and install them using a file explorer.
NOTES (read this before you install):
This will install easily on phones that do not have email.apk and exchange2.apk. But if you have an AOSP ROM, you may already have these in your system/app directory. In that case, you'll have to uninstall the system apps email.apk and exchange or exchange2.apk using a root explorer. I use ES explorer's "App Manager" feature and it works well for me. Once the system apps are removed, you can install the files from this post.
If you update your ROM later, the system apps will come back and may conflict with these apks (installed in /data by default) so you'll have to do the removal/installation again.
You don't need Exchange.apk AND exchange2.apk on the same phone. If you use an ICS ROM (older phones), use exchange.apk. For JB or higher, Exchange2 is the one to use. If you already have exchange2.apk on your phone, you don't need to install the one from this post.
I compiled this from source, so it *should* work with all devices. There are no device-specific frameworks needed for these to run as far as I know.
I've only removed the Exchange based security. If there are any other kind of services (POP/IMAP or something else) which has similar policy enforcement, it may not work. I haven't tested it with anything other than Exchange.
UPDATE - Sep 27, 2015)
I'm sorry I disappeared - I hadn't checked back in a while and it looks like I uploaded the wrong apk. Uploading the correct one for Lpllipop.
UPDATE 4 (May 25, 2015)
Patched and compiled the Lollipop email client from CM12 sources. Google remoived exchange support from the AOSP email client, so I had to turn to CM12 for the source code.
The default Exchange2.apk from a CM or AOSP lollipop build should work so I'm not uploading it here.
UPDATE 2 (May 15, 2013)
Added Email.apk compiled from 4.2.2 sources. This gives you the nice JB style expandable notifications.
Also added higher attachment size support per a user request. The default email.apk limits the size to 5MB for atachment downloads/uploads. The attached Email-JB.apk supports 100MB download/50MB upload sizes. I'm not sure if this varies by Exchange server - I spent two whole nights because I set them too high (250M) and my exchange server threw a generic error. I spent the time troubleshooting policies where it was just the attachment size all along. Cost me 8 hours of sleep
Exchange2.apk is not needed if your phone already has Exchange.apk or Exchange2.apk. For people who have HTC phones, this may come in useful. This file was pulled from this ROM - which is compiled from sources. I couldn't get Exchange2 to compile and work properly from sources, but since there is nothing to be changed in here, any working APK (from a JB/ICS ROM) would suffice.
UPDATE 3 (Jan 11, 2014)
Added Email.apk compiled from 4.4.2 sources. This gives you the new gmail-style email view based on the contact pics or the first letter of the sender's name.
It will say that the policy was changed once you successfully connect to the exchange server, but no policy will be applied. You can check the device admins list once you connect - the newly connected exchange server will not be in the device admins list on your phone.
Notes:
I have not made any changes to the Exchange2_4_4_2.apk. I'm just pasting it here for convenience, for people who don't have it on their phones (certain HTC stock ROMS, or others that I don't know of).
If your server has other policies which prevent you from accessing it, this probably won't show an error message before bouncing you back because I've suppressed a few of these security related dialogs.
File List
May 25, 2015
Email-5_0.apk - Compiled from CM12 sources, exchange security and popup security dialogs removed, max attachment sizes changed to 100MB download/50MB upload from 5/5.
No exchange2.apk provided for lollipop - the one already on your phone should work. If you have any problems, please get it from a CM12 or AOSP ROM.
--- Old files----
Email.APK - Compiled from ICS (4.0.1) sources.
Exchange.apk - Compiled from ICS (4.0.1) sources.
May 15, 2013:
Email-JB.apk - Compiled from 4.2.2 sources, attachment sizes increased to 100MB/50MB down/up.
Exchange2.apk - pulled from a CM10.1 port (WFTN ROM)
Jan 11, 2014
Email-4_4_2.apk - Compiled from 4.4.2 (Kit Kat) sources, still retains the increased attachment size mod.
Exchange2-4_4_2.apk - Compiled from 4.4.2 sources [this apk is not needed unless you have a phone which does not already have this]

let me be the first one to say thanks !!!
worked like a charm !!
tested on HD2

I'm glad it helped

Yep thanks it's working on my rooted HTC Desire Z with andromedus

ProcessorHog said:
I'm happy to post my first actual Android dev/mod effort.
Recently my workplace introduced some draconian security policies for email syncing. I just wanted my appointments synced, so I didn't feel like encrypting my device, having zero timeout AND not even having the option of a pattern unlock (they enforce only passwords/PIN). I tried a couple of the Email.apks posted on XDA but for some reason or other, I couldn't get them to install/run. There was a GB based app which would install but when it synced, it said the device did not support some of the policies that were needed by the server. When I compared the Email app's GB source with the ICS source, I saw that there were tons more policies supported in the ICS version.
So I set upon a weekend project to modify the ICS email app, and that ended up taking 4 days part time. I learned a lot about aosp, compiling from source and all that and know that I have so much that I don't know.
Anyway, I was able to successfully modify the source code and finally managed to get the original Android Email app (which comes with AOSP) compiled running perfect, but without the ridiculous policies they wanted.
I tested it on my Evo 3D running MeanRom (4.0.3 build) and also tested it on the Android emulator of course ), and it works great. No annoying popup saying that you need to give it device admin permissions nor does it set any additional policies other than what you already have set on your device. It does not make the email app a device admin.
The app tells the server what it wants to hear - which is they have total control over my device, but it doesn't really do it on the phone. Everyone is happy
DISCLAIMER: I'm not responsible if you get fired or if you get in other sorts of trouble for using this, or if this melts your device down or breaks it in any fashion. USE THIS AT YOUR OWN RISK.
How to install:
Code:
adb install -r /path/on/your/computer/to/Email.apk
This is how I installed it. Alternatively, you can try downloading this on your phone (or copying it to the SD Card) and open it with package installer, and see if it installs.
NOTES:
I compiled this from source, so it *should* work with other devices as well. As far as I know, there are no device-specific frameworks/anything else needed for these to run. I used the android-4.0.1_r1 branch source code.
Since I was running MeanROM on my HTC (a sense-based ROM), Email.apk had some dependencies on Exchange.apk which did not exist on my device. I'm posting this as an attachment for the folks who may need it. I haven't changed any code in that project, so If you already have Exchange.apk (shows up as "Exchange Services" in your Apps) you don't need to install it.
I've only removed the Exchange based security. If there are any other kind of services (POP/IMAP or something else) which has similar policy enforcement, it may not work. I haven't tested it with anything other than Exchange.
This was compiled for the arm-v7 CPU. I'm not too sure whether this means it won't run on any other ones (but knowing that it's dalvik code and not native, it should run I guess). It ran fine on my x-86 based emulator.
[*]This is an eng build (non-optimized). I couldn't find a way to get classes.dex in the APK itself on a full "user" release build. Eng is the least optimized form, userdebug is a bit better. I couldn't find a non-device-specific "lunch" option to build this with a "userdebug" variant flag. If I do figure it out, I'll post an updated APK here.
I'm still learning how to use eclipse and such. I haven't posted the source code here, and frankly I don't know how much of it I should post (I think I changed about 3 files and commented out a bunch of stuff). If anyone is interested in knowing, I can point out the files that I changed. If I figure out how to do a proper diff that shows all the changes, I will post the code diff here.
Update:
Replaced the apks with a "release-user" build.
Click to expand...
Click to collapse
Thanks for share it, I made a CWM flasheable ZIP with your files.

Would this work on 4.2?

I could use some help. I'm trying to run this on SOS M ver 2.6.2 (4.0.3 build) on an Evo 3d. I was under the impression that SOS M was similar enough to Mean ROM so that it would work, but all I'm getting is an immediate crash on startup. Any suggestions?

So glad that someone created this! THANK YOU SO MUCH!
The new security rules are ridiculous!
I wish that app would be maintained with the current version and be put in the google play store. How can I keep up to date with the most recent version of this app?

Recent update
Sorry I haven't been here much - life got too busy! If you post here and don't see a reply from me in a couple of days, feel free to send me a PM.
carm01 said:
what part of the smali code was modified please?
Click to expand...
Click to collapse
No smali code was modified, the apk was compiled directly from the java source code which I modified to take out a few annoying dialog boxes and the actual policies/restrictions that the server wants to set on your device.
zdravke said:
Would this work on 4.2?
Click to expand...
Click to collapse
The ICS version worked fine on 4.2 since it's just regular java code compiled from source, but I recently also added an APK compiled from 4.2.2 sources which has the expanded notifications (the ICS version didn't have it).
pbmurdoc said:
I could use some help. I'm trying to run this on SOS M ver 2.6.2 (4.0.3 build) on an Evo 3d. I was under the impression that SOS M was similar enough to Mean ROM so that it would work, but all I'm getting is an immediate crash on startup. Any suggestions?
Click to expand...
Click to collapse
Could you try the newly updated APK? Make sure your phone has exchange2.apk or exchange.apk as well. Some phones do not have these pre-installed.
sirtom1 said:
So glad that someone created this! THANK YOU SO MUCH!
The new security rules are ridiculous!
I wish that app would be maintained with the current version and be put in the google play store. How can I keep up to date with the most recent version of this app?
Click to expand...
Click to collapse
I don't think this can be put on the play store - I don't regularly maintain it (once compiled it should run without problems), and I recently updated it just because I finally got a JB ROM a few months ago and started missing the expanded notification. The next update will probably be after a long time - after the next version of android gets released.
I'm not bright enough to write something complex like the email app - there's a TON of code in it written by smart and talented people, I just dug around a little to find the policy application code and removed it. The real talented folks are the ones who actually contribute to android

luisjoseb said:
Thanks for share it, I made a CWM flasheable ZIP with your files.
Click to expand...
Click to collapse
Thanks for making this easy for others! If you have the time, could you make one for the 4.2.2 version of it? Someone could find that useful!

Just gave it a try. Works great. Thanks so much
Sent from my DROID RAZR using Tapatalk 2

thank you .. working like a charm ..
Desire with MIUI Rom (VJ - JB-4.1.2)
I had to use this mod as the latest build didnt have an Email app .. and other ROMs' Email2.apk didnt work on this one (due to mishandling the security request) .. !
anyways .. thank you ..

Thanks. I try on US T-mobile HTC One S JB 4.1.1 Sense and it works. I use Email-JB.apk and Exchange.apk

thanks for this, it's working on my galaxy s4 (android 4.2.2) now instead of that ugly samsung mail app. 1 thing i'm missing is option in the nice JB style expandable notifications to directly mark as read or delete the email in the notification panel. this option is present in cm10.1/aosp android 4.2.2 but not in this email app. Is it possible to add this?

elroy944 said:
thanks for this, it's working on my galaxy s4 (android 4.2.2) now instead of that ugly samsung mail app. 1 thing i'm missing is option in the nice JB style expandable notifications to directly mark as read or delete the email in the notification panel. this option is present in cm10.1/aosp android 4.2.2 but not in this email app. Is it possible to add this?
Click to expand...
Click to collapse
For this, I'll have to compile from CM10.1 sources. I haven't tried that - I'll give it a shot when I get some free time and will post the APK here if I manage to do that

ProcessorHog said:
For this, I'll have to compile from CM10.1 sources. I haven't tried that - I'll give it a shot when I get some free time and will post the APK here if I manage to do that
Click to expand...
Click to collapse
Okay, thanks

Getting an error on adb install... Running JDQ39 official Google version for Galaxy Nexus. Rooted/etc, obviously. Leankernel 16.something.
Is this only for AOSP ROMs?
Error I am receiving:
pkg: /data/local/tmp/Email-JB.apk
Failure [INSTALL_FAILED_CONFLICTING_PROVIDER]

No dice...
I managed to get it installed by using Titanium to uninstall Email 4.1 prior to installing yours. This gave me endless "Unfortunately, Email has stopped working" errors.
I installed a fresh AOSP 4.2.2 ROM and tried several iterations of uninstalling Email and Exchange2Google.apk and continue to get the "Unfortunately, Email has stopped working" errors.
I've tried using "apk install" and Package Installer, same results regardless of install method.

Works fine on TF101 EeePad Transformer (EOS4) and Galaxy Ace phone (CM10)

[Important] Sudden Death (SDS) - Don't use older than Android 4.1.2 or CWM 6.0.3.x

Latest Thread update
This section is to alert returning readers to new sections or information as they are added. New readers, please start at "Introduction"
17th Jul 2013 - Added Googy-Max. I thought this thread was dead
21st Jun 2013 - Request: Please don't ask if x.x.x (new release) has SDS fix. See "***" at end of post 1.
19th Jun 2013 - Added Official CWM Link in safe recoveries (Please only use links provided)
18th May 2013 - Revised "Stock section" to be more succinct
13th May 2013 - Added Devil kernel to safe list
3rd May 2013 - Added more about SDS v half SDS in the "What do we think we know" section
12th Apr 2013 - tried to distinguish between Fix 1 and Fix 2
6th Mar 2013 - Added ICS boaotloader to "Other links"
25th Feb 2013 - Added "Other Links" section at end of post 1
26th Jan 2013 - Update on bootloader requirement, courtesy of AndreiLUX
Previous: Added Speedmod K2-5 Test 1 Kernel
Previous: Added quotes around the fixed items for visual prominence
Introduction
Hi All,
I am seeing a lot of Buzz about the Sudden Death issue and recent fixes identified by AndreiLux and implemented into his Kernel here:
http://forum.xda-developers.com/showthread.php?t=1691401 so please take a moment to thank him.
Unfortunately as there seems to be some uncertainty about what is or is not covered by the Fix, I have put this thread together to eliviate some of the many off topic questions posed by members in development threads, which is unfair on the developers.
So what do we think know?
Please be aware, this is not related to the Exynos Memory security issue.
The "Sudden Death" issue is caused by firmware on the (16 GB) VTU00M, revision 0xf1 eMMC (Embedded MultiMedia Card or internal memory if you like). Samsungs Kernel Source Code (Update 7) has been identified as the fix. There is still no evidence that the latest sboot bootloader addresses this issue.
Although we are still not quite 100% Certain this will prevent all S3's suffering the SDS (Predisposition to the fault etc), to the best of our knowledge it does. Even if it does not fully fix it, its closer to a fix and safer than older versions, so if its within your means to do so, an update would be advised. Please don't panic. If it's going to happen, it's going to happen and that's that. It will be repaired under warranty. I had to use a Bold 9000 for 7 days whilst mine was repaired
SDS seems to manifest in 2 distinct ways.
1) Complete eMMC failure. This usually happens over night whilst on charge* - The LED may be lit but the phone will not wake. Subsequent removal of the battery will turn off the LED. You will never get the LED back on. The phone will never turn on again. It needs to go to a service centre and have the motherboard replaced
* Being on Charge is NOT the cause. This is a writing to memory issue and it is more likely to happen when teh device is awake rather than in deep sleep. When the S3 is on charge, it holds a wake lock (so remains awake) throughout the entire charging period, meaning SDS is more likely to occur when on charge This does not mean you should avoid charging your phone. If it's going to happen, it's going to happen
2) Half SDS as it has not-so-affectionately become known. This tends to be more of a boot loop of the Samsung boot splash. the eMMC is partially wiped out. You cannot boot into android or recovery. It fails at the boot screen, but the screen does turn on none-the-less. The only; thing you can do is top boot into Download mode.
One problem Half SDS has is that the information download mode uses to show the status as "Official" appears to be wiped out by the bug, leaving your status as "Custom". This can leave you in a precarious position as this is what Samsung uses to establish warranty validity. You may also see your product field is blank.
Please help me maintain this list by identifying fixes as and when released, Please post the Link and Version number of anything with this fix implemented
How do I check my eMMC?
Using the EMMC check app from play, you can see if your eMMC is the VTU00M 0XF1 (affected chip).
Please note:
1) We only need this app to check the version.
2) Nothing you see in this app will change once you apply a fix. It simply gives you the version. If you expect 0xf1 to change to something else, you are mistaken. Only replacing the motherboard will do that.
What do I need to be "Safe"?
The "Fix" is actually a preventative measure. It cannot revive a "dead" device. It has to be applied before failure.
To be 100% safe, you need:
A bootloader with fixes**
[*]A Recovery with a fixed kernel
[*]A Fixed kernel to run Android
If you are a normal user only using official releases (no custom ROMs, Kernels or recoveries) then we treat you as "Stock" - read on.
Lets get to it... Where is it fixed?
Stock:
All 4.1.2 official releases (stock) include a Kernel, bootloader and recovery with the Update 7 "Fixes" (or newer) applied. If you have 4.1.2, officially consider yourself "Safe".***
Stock (but rooted):
If you rooted a 4.1.2 stock ROM, you will still be safe, however - if you changed to a custom kernel or recovery, you need to look at the below custom sections to ensure your kernel or recovery are listed as safe.
The below official kernels were tested, but we no longer need to test. All 4.1.2 (stock) kernels and newer have fixes.
XXELKC
XXELL1
XXELL4
XXELL5
XXELL6
XXELLA
XXELLB
XXELLC
Fix v1
Please note, you may experience freezes and /or reboots using a Fix v1 ROM (Well actually kernel that is included in this ROM). Essentially any Stock 4.1.2 ROM between:
LKC and MA2
Which means:
2012 November revision 12 and 2013 January Revision 2
...may experience freezes due to the way the fix works. This is annoying but better a freeze than a motherboard replacement.
Fix v2
From what appears to be Update 8 sources (MB1 onwards), the fix seems to be much better with far fewer freezes. I haven't included the MR* vodafone ROMS because who knows? They don't follow the standard naming convention. All I can say is MR2 came out when MBx was around (B = February) but is still only fix v1
People who have never rooted need not read any further. Essentially, if you have an official, never rooted 4.1.2 ROM, you're "safe"
Click to expand...
Click to collapse
-------------------------------------------------------------------
Custom ROMs which include a ROM specific and dedicated kernel (including fixes):
These are custom ROMs that have their own kernel that is not flashable separately. This means it is not packaged with a kernel from the "Custom Kernels" section. If you have the version specified or newer, you are "safe"
Any 4.1.2 (or newer) TouchWiz ROM with a repacked, stock kernel - no need to list them all.
HydRx-D v2.2.1r1 (TW)
CM 10.1 Nightly 20130109 (AOSP)
Tamasek's Unofficial CM10.1 v32 (AOSP)
ReVolt JB Nightly 20130111 (AOSP)
Click to expand...
Click to collapse
Custom Kernels:
These kernels include the update 7 fixes (or newer). If you are rooted with a custom Kernel that is older than (or doesn't match) the versions below, you are not considered "safe"
Perseus Alpha31+ (i9300 TW)
Boeffla 2.6 Alpha1 (i9300 TW
Speedmod K2-5 Test 1 )i9300 TW)
Yank555.lu 3.0a (i9300 TW)
Siyah 1.8.7 (i9300 TW & AOSP)
Devil ALL Versions (i9300 TW & AOSP)
Googy-Max ALL versions (i9300 TW & AOSP)
Yank555.lu 1.4 (i9300 AOSP)
Click to expand...
Click to collapse
Custom Recoveries:
Since the recovery uses a kernel too, to be "safe", the recovery's kernel must also be fixed.
PhilZ Touch 4.00-b04 (i9300)
Siyah 6.0.1.4 (Siyah Kernel users only)
TWRP 2.3.3.1
CWM.img from clockworkmod.com CWM.tar from mskip (6.0.3.2)
CF-auto-root (stock recovery supplied with this)
Click to expand...
Click to collapse
Please be weary of CWM. It can be compiled by anyone which means we cannot guarantee all versions have the latest fixes. Please only download from the links posted above
Obviously, rooted users are probably more familiar with what to do. I don't really want to recommend non-techy people flash official firmwares if they are not comfortable doing it. There will be a fix on its way to you all soon anyway, so the worst that will happen is you are affected and you have to get your phone repaired...
For those who are technical but would prefer to follow an Odin flash guide for official firmware, read the appropriate section here:
http://forum.xda-developers.com/showthread.php?t=1671969
Recap
So to recap, if you checked you have VTU00M 0xf1 with EMMC check , you need to ensure:
If unrooted (never rooted / modded), you are on one of the "Stock" ROMs listed above
If rooted, you have one of the "Custom Kernels" OR "Custom ROMs including kernel" OR rooted "stock" with original kernel AND one of the "Custom recoveries" from the lists below
**Bootloader note
Download mode uses a bootloader packaged micro-kernel
It will only affect those who use download mode. Personally I am rooted so I don't use it so i'll be sticking with one that doesn't mess with the flash counter, however anyone who does use download mode should consider updating. Those who care more about flash counters and will stay with older bootloaders should avoid flashing anything in download mode
*** Please do not ask if newer builds (either not mentioned here, or newer than 4.1.2) include the fixes.
Samsung have a single repository of kernel source code. They continue to develop this code. When they add a fix, it's there forever in every new kernel built after the fix is added. Every fix is in new kernels automatically. They do not have a list of fixes they must add every time.
The only way a new kernel does not contain a fix is if it is manually (and specifically) removed from the source code. Can you think of any logical reason why they would do that?!
Other Links
Ultimate Unusual Freezing thread (The fix causes Freezing, possible solutions)
Ultimate SDS thread (Further discussion of the SDS issue)
ICS Bootloader for those who want to keep custom counter at 1

In another thread a guy got a SDS after flashing ELLA via Odin, so that's weird at least

Yank's kernel has the fix too, I think.
Two questions:
1. When boot into Download Mode- is it safe?
2. Someone said about charging the phone when it is off and off the wallsocket. How about the fix/security then?

Glebun said:
In another thread a guy got a SDS after flashing ELLA via Odin, so that's weird at least
Click to expand...
Click to collapse
Could the failure process already have started? I'll put a caveat next to that....

rootSU said:
Could the failure process already have started? I'll put a caveat next to that....
Click to expand...
Click to collapse
As far as i know he had siyah kernel installed

BTW cm team add the patch too
http://review.cyanogenmod.org/#/c/29932/

yahyoh said:
BTW cm team add the patch too
http://review.cyanogenmod.org/#/c/29932/
Click to expand...
Click to collapse
Thanks. Signed off my Andrei today so I assume that appears in tonights nighty?
#
Sorry guys, ran out of thanks today

It appears the fix is in some older kernels too, but there has definitely been instances of SDS on those, so it's possible that the fix found in update 7 is not the whole story.

theslashy said:
As far as i know he had siyah kernel installed
Click to expand...
Click to collapse
That would make sense as its the kernel not the rom that has the fix. Has anyone got a link please?

mjb said:
It appears the fix is in some older kernels too, but there has definitely been instances of SDS on those, so it's possible that the fix found in update 7 is not the whole story.
Click to expand...
Click to collapse
Best we have right now is from Andrei stating it *looks* complete, but I agree we just cannot know everything for sure yet. I changed teh op to say "what do we think we know"

Great thread. Hope for news regarding the recovery.

Its allways a risk to flash via odin. Anything could of happened during the flash. Am I goin crazy or does everyone not know that all ready. We allways flash at our own risk! Need to keep this issue real. Some people think they have a tickin time bomb in there pocket. Boom!
Sent from my GT-I9300 using xda premium

PhilZ Touch 4.00-b04
Download:
- odin: http://www.mediafire.com/file/3g6ke58rsvs3j8y/philz_touch_4.00-b04-i9300.tar.md5
- cwm: http://www.mediafire.com/file/m6z7wwrd20pd9ln/philz_touch_4.00-b04-i9300.zip
This version wouldn't have been pushed as I did not plan any updates of the binary before 4.00 Final. But since we needed a repack with XXELLA kernel and the code was ready for these changes, I pushed it.
Changes:
- Repack with XXELLA kernel supposed to be SDS safe
- Fix romname added to nandroid backups: now build.prop will be parsed instead of reading system properties
- Custom rom.zip scripts completely revised to add a bit of process progress (beta and will be completely revised in Final build)
Click to expand...
Click to collapse

I do not feel like it is so much of a risk to flash via odin. Unless you are a noob. I am a noob but I usually read a lot before doing anything on my device.

montage mahal said:
Its allways a risk to flash via odin. Anything could of happened during the flash. Am I goin crazy or does everyone not know that all ready. We allways flash at our own risk! Need to keep this issue real. Some people think they have a tickin time bomb in there pocket. Boom!
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Yes indeed but ts a real issue even if you never flash anything.

rootSU said:
Best we have right now is from Andrei stating it *looks* complete, but I agree we just cannot know everything for sure yet. I changed teh op to say "what do we think we know"
Click to expand...
Click to collapse
Good.. I think the patch is complete too, but my concern is that we just don't know if this is addressing SDS, another fault, or just part of SDS and there is actually more to the problem than what this patch is "fixing".
I only say this due to finding the strings in the patch in older stock kernels, where people have experienced SDS.

mjb said:
Good.. I think the patch is complete too, but my concern is that we just don't know if this is addressing SDS, another fault, or just part of SDS and there is actually more to the problem than what this patch is "fixing".
I only say this due to finding the strings in the patch in older stock kernels, where people have experienced SDS.
Click to expand...
Click to collapse
Yep no worries. I have reworded the OP a little more to reflect. Please feel free to help me phrase it

I think that best solution is to flash PhilZ Touch 4.00-b04 as is based on XELLA (secure) and using XELLA reom with kernel or Perseus. PhilZ recovery works with exfat - Yank kernel not - so is for me useless

Great news! I hope with this recovery we can avoid SDS issues!.
Thanks for your help and effort

Thanks rootSU for all your support (sorry, out of my 8 thanks as always)
Just an edit to the op: stock recoveries: instead of none, maybe add XXELLA
Bye

[ROM][8.0] AEX 5.0 [BETA - 24/09/2017] [Source : club.lenovo.cn]

Hi Guys!
I was browsing through pages of zukfans.eu and found links to what is said to be the xda-test Beta of AospExtented v5.0. I'm a big fan of AEX so I chose to share what I found to you guys for fun.
*MIGHT NOT BE THE OFFICIAL AEX OR DEVELOPED BY @davidevinavil AS SUGGESTED BY @optimumpro, PROCEED ON YOUR OWN RISK*
I personally haven't tried the rom yet so I don't know what it beholds. I'm not the developer, so no use complaining here. I'm merely sharing.
I found certain changelogs and test comments (Google Translated from Chinese) :-
** AEX 5 beta release, thanks xda dalao personal test bug: multi-task app interface upside down (nothing affected)
It is said to repair the camera, wifi, specific bug everyone test their own, feedback Kazakhstan, landlord to play the sea one day, without a cell phone, hey Machine friend test bug:
Current test
1: camera, Wi-Fi, phone, SMS basic normal
2: After entering the English version, in the settings in the upper right search language, select the plus sign, the Simplified Chinese can be set to the first Chinese
3: no authority, can brush brush supersu official website latest version of the package.
4: there is temperature control, you can use zui2.5 temperature control file in the etc folder replacement
5: known bug, the screenshot is down, the fingerprint button function is not clear, very confusing
Recommendation: recommend multi-system brush (specific tutorial please carefully turn the forum) **
As you can see, the OP recommends to try flashing in multiboot. So it's personal risk amd choice of each of you flashing this build.
Original Post :- http://club.lenovo.cn/detail/4228091
Repost on Zukfans.eu :- https://zukfans.eu/community/threads/aex-5-8-0.7108/
Unofficial Gapps I found (try on your own Risk) :- https://androidfilehost.com/?fid=745425885120757578
Mega upload of Rom (thanks to Rodolph21 @zukfans.eu) :- https://mega.nz/#!3cBBSBga!4ux6eM-CnrL7CESuTpIltWtFG7805A5B27MqsBqgr08
If you choose to try the rom, please post reviews and screenshots in comments, will be certainly useful for others. I will try and update the important points of the review in the post.

Why are you guys so much active nowadays sharing Oreo roms which were not meant for public sharing? When the developers think it is right time, they will release it themselves. Please refrain from sharing any oreo stuff anymore without their permission

Please, change link for download the ROM. Thank's!

GostJr said:
Please, change link for download the ROM. Thank's!
Click to expand...
Click to collapse
Download link changed.

hp5942 said:
Why are you guys so much active nowadays sharing Oreo roms which were not meant for public sharing? When the developers think it is right time, they will release it themselves. Please refrain from sharing any oreo stuff anymore without their permission
Click to expand...
Click to collapse
I just reposted what was already public in zukfans forum.
I thought it might be useful.

mirror https://drive.google.com/file/d/0B09M1OeWOzhmVHRtMWtOMWtSYTQ/view?usp=drivesdk
Considerations on the rom: its pretty stable, i flashed unofficial oreo opengapps and magisk 13.3 (i dont like 14.0) and only the camera doesnt work. However u should install some kernel manager and be sure to set all governors on interactive. The original launcher and some stock apps are vanilla android so they're very old but its pretty easy to install pixel launcher etc.
Btw i used the device with wifi only so i cant report on calls and so on since this is not my main device.
Screenshots: https://m.imgur.com/gallery/MD4xg
Fingerprint works too, bluetooth is unstable.

fantamadnesss said:
mirror https://drive.google.com/file/d/0B09M1OeWOzhmVHRtMWtOMWtSYTQ/view?usp=drivesdk
Considerations on the rom: its pretty stable, i flashed unofficial oreo opengapps and magisk 13.3 (i dont like 14.0) and only the camera doesnt work. However u should install some kernel manager and be sure to set all governors on interactive. The original launcher and some stock apps are vanilla android so they're very old but its pretty easy to install pixel launcher etc.
Btw i used the device with wifi only so i cant report on calls and so on since this is not my main device.
Screenshots: https://m.imgur.com/gallery/MD4xg
Fingerprint works too, bluetooth is unstable.
Click to expand...
Click to collapse
Good to know :good: :good: Thanks!

fantamadnesss said:
mirror https://drive.google.com/file/d/0B09M1OeWOzhmVHRtMWtOMWtSYTQ/view?usp=drivesdk
Considerations on the rom: its pretty stable, i flashed unofficial oreo opengapps and magisk 13.3 (i dont like 14.0) and only the camera doesnt work. However u should install some kernel manager and be sure to set all governors on interactive. The original launcher and some stock apps are vanilla android so they're very old but its pretty easy to install pixel launcher etc.
Btw i used the device with wifi only so i cant report on calls and so on since this is not my main device.
Screenshots: https://m.imgur.com/gallery/MD4xg
Fingerprint works too, bluetooth is unstable.
Click to expand...
Click to collapse
Dude you have posted wrong screenshots, that are of gzaosp not AEX

Tried... Almost stable...
A major problem I faced was that the VoLTE doesn't work at all... (is there any workaround?!)

Jintu Jose said:
Tried... Almost stable...
A major problem I faced was that the VoLTE doesn't work at all... (is there any workaround?!)
Click to expand...
Click to collapse
I don't think so. The point of such alpha & beta releases is not to be a daily driver with all features working but just to check system stability in a bunch of phones.

Anyone has the new version?

Where can we find updates about newer realeases for this rom?

First of: If the developer wants it for open use ... itll be here .... second of all theres allready aex5 out in the rom area of this form ..... thrid of all please stop sharing or posting about a rom without permission.
Check it: https://forum.xda-developers.com/lenovo-zuk-z2/development/rom-aospextended-rom-v5-0-t3683254

SM-N981U/U1/W ROM

Disclaimer:Your warranty is now void.I am not responsible if you use this and brick your device or if your device blows up, implodes. Follow the instructions and you should be good.This is stock ROM with modifications. I do not own this device any issues let me know.You must have an Unlocked Boot loader. This is only for SM-N981U, SM-N981U1 should work on SM-N981W.ALWAYS BACKUP YOU’RE DATA BEFORE FLASHING.Instructions:• Download the zip file.• Put the ROM.tar in AP slot with Odin.• Reboot• Wipe data• Enjoy!• Any Issues let me know!ROM FEATURES:Rom removed request this Thread to be closed.Mod Edit: TG link remove.To get your phone unlocked see this thread or contact @afaneh92 for boot loader unlock or Click Here >> UnlockTWRP Included Thanks to @afaneh92Donations are not required but are encouraging, If want to support my work just click Here

Request this Thread to be closed.

Reserved

Oh thankswill try asap.
Nope, i'm on 981B

bklyn_syed said:
Disclaimer:
Your warranty is now void.
I am not responsible if you use this and brick your device or if your device blows up, implodes. Follow the instructions and you should be good.
This is stock ROM with modifications. I do not own this device any issues let me know.
You must have an Unlocked Boot loader. This is only for SM-N981U, SM-N981U1 should work on SM-N981W.
ALWAYS BACKUP YOU’RE DATA BEFORE FLASHING.
Instructions:
• Download the zip file.
• Put the ROM.tar in AP slot with Odin.
• Reboot
• Wipe data
• Enjoy!
• Any Issues let me know!
ROM FEATURES:
- Force Encryption off
- Safetynet-fix from kdrag0n included in ROM just enable MagiskHide
- ViPER4AndroidFX included just install drivers.
- Heavily Debloated
- Bluetooth, Screenshare and Shealth working.
- Disable shutter sound menu
- AppLock Protection menu
- Support RealTime Network Speed
- Enable Camera during call
- Voicecall recording
- Data usage view on quick panel
- Block call number menu
Telegram BKLYNROM
To get your phone unlocked see this thread or contact @afaneh92 for boot loader unlock or Click Here >> Unlock
TWRP Included Thanks to @afaneh92
Donations are not required but are encouraging, If want to support my work just click Here
Click to expand...
Click to collapse
bklyn_syed said:
Disclaimer:
Your warranty is now void.
I am not responsible if you use this and brick your device or if your device blows up, implodes. Follow the instructions and you should be good.
This is stock ROM with modifications. I do not own this device any issues let me know.
You must have an Unlocked Boot loader. This is only for SM-N981U, SM-N981U1 should work on SM-N981W.
ALWAYS BACKUP YOU’RE DATA BEFORE FLASHING.
Instructions:
• Download the zip file.
• Put the ROM.tar in AP slot with Odin.
• Reboot
• Wipe data
• Enjoy!
• Any Issues let me know!
ROM FEATURES:
- Force Encryption off
- Safetynet-fix from kdrag0n included in ROM just enable MagiskHide
- ViPER4AndroidFX included just install drivers.
- Heavily Debloated
- Bluetooth, Screenshare and Shealth working.
- Disable shutter sound menu
- AppLock Protection menu
- Support RealTime Network Speed
- Enable Camera during call
- Voicecall recording
- Data usage view on quick panel
- Block call number menu
Telegram BKLYNROM
To get your phone unlocked see this thread or contact @afaneh92 for boot loader unlock or Click Here >> Unlock
TWRP Included Thanks to @afaneh92
Donations are not required but are encouraging, If want to support my work just click Here
Click to expand...
Click to collapse
Thank you sir. I've been unlocked since before christmas and this is first custom rom installed (though i had a lot of these mods done just individually). i'm doing one for android 10 (first custom rom) just because for whatever reason a lot of patching seems to more consistent than on 11, at least for my methods and knowledge. that boot animation though..... bad ass. anyway you would share how you pulled that off? i've been banging my head against the wall for 2 months on that. Regardless, thank you so much, awesome to see the note 20 5g getting some love!! shout outs to @afaneh92 and @jrkruse for all the help on everything else.

kernal_root said:
Thank you sir. I've been unlocked since before christmas and this is first custom rom installed (though i had a lot of these mods done just individually). i'm doing one for android 10 (first custom rom) just because for whatever reason a lot of patching seems to more consistent than on 11, at least for my methods and knowledge. that boot animation though..... bad ass. anyway you would share how you pulled that off? i've been banging my head against the wall for 2 months on that. Regardless, thank you so much, awesome to see the note 20 5g getting some love!! shout outs to @afaneh92 and @jrkruse for all the help on everything else.
Click to expand...
Click to collapse
Actually I am working on V2.0 I was in accident so I should be done soon so it will have alot of features that will match with other roms
I used superr kitchen to edit super.img and csc files. To add mods to a rom you need to edit framework.apk and systemui.apk along with create apk that can control the mods, which I have released for other devices.
On android 10 its different file that patches the safety net. Other features like call recording and stuff can be added with csc

bklyn_syed said:
Actually I am working on V2.0 I was in accident so I should be done soon so it will have alot of features that will match with other roms
I used superr kitchen to edit super.img and csc files. To add mods to a rom you need to edit framework.apk and systemui.apk along with create apk that can control the mods, which I have released for other devices.
On android 10 its different file that patches the safety net. Other features like call recording and stuff can be added with csc
Click to expand...
Click to collapse
well first off, thank you again! secondly, i hope you are recovering well from your accident. also i will be looking forward to your 2.0 release. and thanks to @afaneh92 i have safetynet patches for 10 and 11 ( and someone has a fix on here for a more recent 11 update that fixes it).
one more question for clarity if you dont mind. is it possible for me to add your boot animation to android 10?

kernal_root said:
well first off, thank you again! secondly, i hope you are recovering well from your accident. also i will be looking forward to your 2.0 release. and thanks to @afaneh92 i have safetynet patches for 10 and 11 ( and someone has a fix on here for a more recent 11 update that fixes it).
one more question for clarity if you dont mind. is it possible for me to add your boot animation to android 10?
Click to expand...
Click to collapse
Yes sure

Sorry man one more question, so di$ you add your boot animation to the systemUI or framework apks, or where is that located in Android 11 because I can't find it for anything. Sorry to bug man, I appreciate it though

kernal_root said:
Sorry man one more question, so di$ you add your boot animation to the systemUI or framework apks, or where is that located in Android 11 because I can't find it for anything. Sorry to bug man, I appreciate it though
Click to expand...
Click to collapse
Files are in system/media bootsamsung.qmg bootsamsungloop.qmg shutdown.qmg sound system/media/audio/ui PowerOn.ogg PoweOff.ogg

2.0 uploaded I did not test, let me know on telegram if there are any issues

bklyn_syed said:
2.0 uploaded I did not test, let me know on telegram if there are any issues
Click to expand...
Click to collapse
No issues on 2.0. It's a solid rom. The font changer is great and the boot animation is awesome!

trook said:
No issues on 2.0. It's a solid rom. The font changer is great and the boot animation is awesome!
Click to expand...
Click to collapse
Good

Hey man, you did a very good job with the rom. I have a note205G I would like to help you improving the firmware quality with mods and things like that. How can I help? Thank you very much for the rom. I will donate very soon

Petition to have the "Recognized Developer" rule apply for this ROM thread. As, this ROM is not stable, V4A does not work at all, Magisk cannot pass safety net. It is a liability, and should be removed.
Edit: OP admits they have not tested the 2.0 ROM. Rolling back to 1.0, after wiping data, did not allow completion of setup. Just reboots on both 1.0 and 2.0 at this point. No matter how many times either version is reinstalled.
OP, this is not your free experiment grounds to throw untested software out and have other users be guinea pigs. Remove the 2.0 ROM until you have tested it.

asrah said:
Petition to have the "Recognized Developer" rule apply for this ROM thread. As, this ROM is not stable, V4A does not work at all, Magisk cannot pass safety net. It is a liability, and should be removed.
Edit: OP admits they have not tested the 2.0 ROM. Rolling back to 1.0, after wiping data, did not allow completion of setup. Just reboots on both 1.0 and 2.0 at this point. No matter how many times either version is reinstalled.
OP, this is not your free experiment grounds to throw untested software out and have other users be guinea pigs. Remove the 2.0 ROM until you have tested it.
Click to expand...
Click to collapse
First of all this ROM was tested by 2 people as the OP clearly states that I do not own the device. If the ROM was downloaded 47 times without any issues until now. This ROM was based on same based as my other ROM SM-G988U and SM-G981U which alot of people are using without any issues.
People have been using this ROM for over a month without any issues. I was working on an update no reason to waist my time.
To make life easy for me and you I will request to have this Thread closed and move on.

Thread closed at OP request.

Database Users

welcome