This patch was originally created for Samsung Galaxy S II and Galaxy S III, but it might work for other devices* running Android 2.3 or 4.x because it patches the Email application that you have on your phone. This is not a pre-patched Email.apk.
* Motorola Blur (Droid), LG G2 and HTC Sense - based ROMs are not supported!
What does it do?
It will make the Email app ignore Exchange-pushed policy on your device, including things like mandatory pin lock (a.k.a. keyguard), minimum password length, encryption, etc.
How to apply this patch?
Root your phone. Your phone must be rooted. It is impossible to apply this patch without root access. You need root to proceed.
Get Java (Java SE JRE v7 or later)
Get USB ADB drivers (for Samsung, install Samsung USB Drivers). Most likely you already have this because of step 1.
Note - ADB via Wi-Fi is also supported. In that case no USB drivers are needed.
Enable USB debugging on the phone (Settings->Applications->Development->USB debugging)
* For CM9 users, also go to Settings > Developer Options > Root access, and select ADB.
Download and unzip attached patch
Run apply-patch.cmd or apply-patch.sh
Note 1: Although the Email app will prompt you for device admin access, it won't actually enforce any policy on your device. Let the app install the device admin!
Note 2: any shortcuts to the Email app as well as any Exchange accounts will disappear and will need to be re-created.
Note 3: The patch will reboot your phone, this is needed for the changes to take effect.
Note 4: If you already installed another Email application and it doesn't work, first restore your original Email application before applying this patch.
A Special Note to those experiencing performance issues! This is not an issue of my patch. This is an issue in the Email app itself. Sometimes calendar sync can't finish properly, causing battery drain. It often happens after you just added a new exchange account. A reboot usually solves this issue. Again, this is not my issue!
Change Log
4.6 - Added basic lollipop support (generic AOSP and CM, no Samsung, alpha, untested)
4.5 - More fixes for Android 4.3 and 4.4
4.4 - Minor release with fixes for KitKat 4.4
4.3 - Bugfix release (adb path errors)
4.2 - ...
4.2 - Bugfix release (IOException)
4.1 - Bugfix release (connection timeout bug fix)
4.0 - Improved ADB support for Mac and Linux (beta)
3.4 - JB 4.3 support (improved boot class path detection)
3.3 - JB 4.2 support (updated adb)
3.2 - Improved Jelly Bean support
3.1 - Added Jelly Bean support (alpha, do not use), minor optimization and cleanup
3.0 - Added Galaxy S III support
2.4 - Bugfix release
2.3 - Will now patch both Email.apk and Exchange.apk, added patch for ProvisionP****r.hasSupportablePolicy(), courtesy of boost252525
2.2 - added ICS isSupported() patch
2.1 - added support for EmailGoogle.apk
2.0 - New patch method based on patching SecurityPolicy's isActive() and isActiveAdmin()
1.1 - Fixed a bug with /system remounting
1.0 - Initial revision based on patching SecurityPolicy.PolicySet <init>
Did the patch work for you? Donations are welcome!
Already patch Email.apk
Your "How to install this patch "is a little to difficult for me.
Is it possible for you to supply an already patched Email.apk ?
In advance thanks
For those who are interested in the source code of this patch, here it is.
https://github.com/rustyx/email-policy-patch
Thanks you
I use the Email.apk with the how to you supply, and All work like a charm.
I want to thanks you very much.
Thank You
Thanks so much for your effort. just want to get one thing clear, since you provided the patched Email.apk can i just install it directly, or do i need to be in recovery mode for example. because in your note you mentioned not to install!
Thanks again
Root explorer will also work! no ADB required!
1) Put Email.apk on your sdcard
2) Go to /system/app and press mount rw
3) remove Email.apk and Email.odex
4) move Email.apk from /sdcard/ to /system/app/
Then you need to setup your email again!
I had to clear the data also in applications -> email
Edit1:
your Email.apk is weird. When i reboot i get the notification that i need to set extra security. But when i press it nothing happends.
And after the email.apk the phone doesn't feel as smooth.. weird
Edit: removed Email.apk (modified) and wen't back to stock! phone is smooth again and works fine
May I ask why u use const/16 ?
const/4 goes from -8 to 8 (2^4) and should be preferred for small constants I think
Fr4gg0r said:
May I ask why u use const/16 ?
const/4 goes from -8 to 8 (2^4) and should be preferred for small constants I think
Click to expand...
Click to collapse
const/4 has also a limited range of destination register numbers, and with the p-format in smali the mapping of p-registers to actual v-registers depends on the number of v-registers. It may happen that in the future more v-register are added, and an existing p-register does not fit in const/4 anymore. Using const/16 is thus more or less future proof.
This is awesome, it woks great
I am on KF1 and it works flawless push with no lag or so
I wonder what happened when we deleted the Email.odex and didn't replace it? we only replace the Email.apk
At first to all, I used tool "FroyoMailUnlocker" to generate my new mail.apk and it worked fine for SGSII on 2.2.3 and also on GT7100 on Honeycomb 3.0.1.
Only problem is that after flashing new OS it need to be installed again.
Does anybody what settings should/can be saved to have an easier restore of the mailbox setup (for my exchange and hotmail accounts)?
Frank
This looks very interesting, but please help me figure out if it will solve my problem:
I have complete security enforced by my work Exchange account.
I need to sync email and calendar with that account.
I want to be able to set a timeout delay to the PIN lock engagement (now it is on immediately as the screen goes black), and it would be nice to use swipe unlock instead of PIN/password.
Will this hack do the trick for me? If so, even with calendar sync?
Thanks!
/Edit: I use the standard email app and calendar om my SGS2
too bad
Hi,
in general I was searching for a long while for this!!!!
Now I have all done as decribed and once I try to create the exchange account it comes back with: "the server requires security settings which your phone dosn't support"
too bad...any ideas?
update:
now it's working...I'd to be patient..
THANK YOU VERY MUCH!!!!
Just to clarify the instructions here (I am noob):
After installing Android SDK, do I unzip the attachement on my PC or phone?
The shell commands, I type them in the adb shell with the phone in recovery mode, or what?
Thanks!
I've been using this hacked app in the past week or so, and it does great what it is supposed to do.
BUT: lately I wanted to see what is draining the battery so fast, and imagine the surprise when I saw that the biggest drainer by far is email.apk, far above the display itself, which is supposed to be the main consumer!!!
Is anyone else seeing this? Do you know about any resolution to this? For now, I just froze the application, but that's not acceptable, since one of the main uses of the phone is to sync up mail, calendar, etc with the corporate one.
catastrat said:
I've been using this hacked app in the past week or so, and it does great what it is supposed to do.
BUT: lately I wanted to see what is draining the battery so fast, and imagine the surprise when I saw that the biggest drainer by far is email.apk, far above the display itself, which is supposed to be the main consumer!!!
Is anyone else seeing this? Do you know about any resolution to this? For now, I just froze the application, but that's not acceptable, since one of the main uses of the phone is to sync up mail, calendar, etc with the corporate one.
Click to expand...
Click to collapse
Do you have push enabled on the account? Try disabling it (setting it to a pull every 15 mins for example).
I had the same issue (without this hack though!) on one of my Exchange accounts, and not using push fixed the issue. It must be an Exchange provider issue, because my work account uses push with no issues.
I don't use push - I have it set for every 1h check during the workday and every 12h for off hours.
I even have disabled all notifications from it...
catastrat said:
I don't use push - I have it set for every 1h check during the workday and every 12h for off hours.
I even have disabled all notifications from it...
Click to expand...
Click to collapse
Hmm I see. Well, if this hack introduces another possible battery draining culprit, I'm not so sure I want to try it. I've spent too much time identifying battery draining apps/processes on my new phone already.
Has anyone else experienced email.apk battery drain after applying this hack?
Me. My phone also slowed down!
There are many factors that may cause a slowdown, which I have no way to reproduce. I can only say that my company's Exchange server is 2003 and that it is the only non-google mail account that I have configured on my phone. I have push enabled. The hack works great with this setup, i.e. no slowdown of the phone, no extra battery drain.
If someone who is experiencing issues can post more details about the version of exchange, sync mode, and any other pop/imap mail accounts configured, I may be able to investigate the issue further.
rustamabd said:
If someone who is experiencing issues can post more details about the version of exchange, sync mode, and any other pop/imap mail accounts configured, I may be able to investigate the issue further.
Click to expand...
Click to collapse
I am running your modded Email.apk in a Galaxy Tab with Gingerbread (Overcome Hermes) and I have no problems with slowdowns or battery drain either. However I am always getting a FC from the mail application when rebooting the Tab. Afterwards it works correctly. I guess it's natural since it is not the native mail application.
I have tried to mod myself the native Gingerbread Email.apk from the Galaxy Tab using your posted code, but it does not work (FC continuously). Although very similar to the Galaxy S II mail application, there must be some differences that make it impossible to just blindingly use your modifications.
Would you be so kind as to have a look at the original Email.apk from the Tab Gingerbread Overcome firmware and suggest a possible mod? Thanks in advance.
Related
Does anyone know of a Bypass Exchange Security Policy mod that will work with the NuSenseONE ROM?
Thanks!
gdemore said:
Does anyone know of a Bypass Exchange Security Policy mod that will work with the NuSenseONE ROM?
Thanks!
Click to expand...
Click to collapse
This ROM comes with an optional sense 5.5 exchange bypass mail.apk
I tried this out a few weeks back on a sense 5.5 ROM and it worked until I tried to reply to an email. I didn't try to troubleshoot the issue as I was just looking at the feasibility of running a 4.3 based ROM. I'm guessing you could get this to work.
Another option would be Enhanced Email on the playstore. I used that on my gs3 whenever I'd run AOSP ROM's, because I didn't have very good luck with the exchange bypassed native email app. I dunno if it's something about my work's exchange server settings or not, but it would still try to force security policies on my phone.
You can install Xposed and they have a module for Sense and AOSP to bypass Exchange Security. Easy to install, check it out.
brucekr said:
This ROM comes with an optional sense 5.5 exchange bypass mail.apk
I tried this out a few weeks back on a sense 5.5 ROM and it worked until I tried to reply to an email. I didn't try to troubleshoot the issue as I was just looking at the feasibility of running a 4.3 based ROM. I'm guessing you could get this to work.
Another option would be Enhanced Email on the playstore. I used that on my gs3 whenever I'd run AOSP ROM's, because I didn't have very good luck with the exchange bypassed native email app. I dunno if it's something about my work's exchange server settings or not, but it would still try to force security policies on my phone.
Click to expand...
Click to collapse
Thanks brucekr. Sorry, but how do I access this optional apk within the ROM?
gdemore said:
Thanks brucekr. Sorry, but how do I access this optional apk within the ROM?
Click to expand...
Click to collapse
I unzipped the entire archive and did a search for the Mail.apk file. I forget where it was located, but it's pretty straight forward.
Hi,
I'm trying to find an exchange security bypass mod for Samsung Galaxy Note 8.0 (3G)
Have tried the following and they all don't seem to be compatible with the stock ROM
XPosed Module - http://forum.xda-developers.com/nex.../xposed-mod-bypass-exchange-security-t2483361
Xposed module - Exchange Security Bypass (No PIN/No Admin) - Android 4.1+ [v6.0] http://forum.xda-developers.com/showthread.php?t=1749921
Any thoughts?
My Device and Software details are
Android version: 4.1.2
Model No: GT-N5100
Kernel version:3.0.31 (KST 2013)
Build number: JZ054K.N5110XXBMD1
consultguru said:
Hi,
I'm trying to find an exchange security bypass mod for Samsung Galaxy Note 8.0 (3G)
Have tried the following and they all don't seem to be compatible with the stock ROM
XPosed Module - http://forum.xda-developers.com/nex.../xposed-mod-bypass-exchange-security-t2483361
Xposed module - Exchange Security Bypass (No PIN/No Admin) - Android 4.1+ [v6.0] http://forum.xda-developers.com/showthread.php?t=1749921
Any thoughts?
My Device and Software details are
Android version: 4.1.2
Model No: GT-N5100
Kernel version:3.0.31 (KST 2013)
Build number: JZ054K.N5110XXBMD1
Click to expand...
Click to collapse
OK, what is doing the hack to accomplish??? Exchange uses security features, so wouldn't that break functionality???
gooberdude said:
OK, what is doing the hack to accomplish??? Exchange uses security features, so wouldn't that break functionality???
Click to expand...
Click to collapse
Trying to check my corporate exchange email w/i being forced to 'always key-in a PIN', encrypted drive etc. I'm OK for all other enforcements that come with the exchange sync (e.g. force data wipe etc). Looking for a convenience factor.
Makes sense?
consultguru said:
Trying to check my corporate exchange email w/i being forced to 'always key-in a PIN', encrypted drive etc. I'm OK for all other enforcements that come with the exchange sync (e.g. force data wipe etc). Looking for a convenience factor.
Makes sense?
Click to expand...
Click to collapse
Ah, OK, I see... Have seen some thing about bypassing PIN for corporate email a few months back. Will look for it again, when I have time Monday. I thought you were disabling it completely or something.
OK, I don't have a corporate setup with exchange so I cannot test.
My xposed module has a security option though it is not enabled and I have no way to test.
Here is a thread on another site... http://mobility.forumsee.com/a/m/s/p12-9290-072026--exchange-security-bypass-no-pin-android.html
I would just unzip the two files and side load them from SD, after doing a complete backup in TI Backup, and removing the two installs associated with the replacement apps.
This way no old settings or double apps will be created.
Hello!
I decided to finish CM10 and CM10.1 ROMs for Wildfire S. This thread is about CM10.1. Here's the ROM.
What's working:
- GSM
- Data (2G/3G)
- A2DP
- SMS / MMS
- FM Radio (use spirit FM)
- GPS
- USB
- Bluetooth
- WI-FI
- LED
- Camera
- Camcorder.
- Panorama mode (Laggy, but works.)
- Video playback [fully]
- VPN
- USB Tethering
- Wifi tethering
- Bluetooth tethering
- etc
What's not working:
- All ARMv7 features (Google Now, keyboard gesture input, offline voice search and etc)
- You tell me
Download​
XDA:DevDB Information
CyanogenMod 10.1, ROM for the HTC Wildfire S
Contributors
niks255, modpunk, PecanCM, armv6team, JDevs, everyone else I forgot to mention
ROM OS Version: 4.2.x Jelly Bean
ROM Kernel: Linux 2.6.x
Version Information
Status: Stable
Stable Release Date: 2014-12-08
Created 2014-10-17
Last Updated 2015-02-15
thanks a lot for this final version!
But one thing I realised already... I additionally installed GAPPS 'gapps-jb-4.2.2-light-20130824-signed' and one function does not run:
'GoogleTTS'. It crashes.
Can you have a look please?...
Falk2 said:
thanks a lot for this final version!
But one thing I realised already... I additionally installed GAPPS 'gapps-jb-4.2.2-light-20130824-signed' and one function does not run:
'GoogleTTS'. It crashes.
Can you have a look please?...
Click to expand...
Click to collapse
Well, no problem. Just give me a logcat of the error.
I re-uploaded the rom cause GPS was not working. Now it does.
Where can I find this 'logcat'?...
Maybe TTS is not a problem with CM10.1 but with the GAPPs package that contains an incompatible GoogleTTS.apk!?
Do you activate the update function in Android options at 'phone infos'? (no option for that right now)
Would really make sense for left errors like that, don't you think so?
Meanwhile I could just flash over the old one, right?...
By the way... Will there be a final CM10.2 version as well?...
Will it be possible to update from 10.1 to 10.2 by just flashing over CM10.1 ? (it is all 'Jelly Beans'...)
Falk2 said:
Where can I find this 'logcat'?...
Maybe TTS is not a problem with CM10.1 but with the GAPPs package that contains an incompatible GoogleTTS.apk!?
Click to expand...
Click to collapse
Probably. I don't really remember TTS working on Android 4.x for armv6. Maybe it uses some armv7 libs. I suggest you download these and flash it on a clean ROM. It doesn't contain anything unnecessary.
To make a logcat just download an app named "Catlog", start it, give it root access, then make google tts crash and then save the log in txt file and post it on pastebin.
Falk2 said:
Do you activate the update function in Android options at 'phone infos'? (no option for that right now)
Would really make sense for left errors like that, don't you think so?
Click to expand...
Click to collapse
Updater has nothing to do with this. And it was not working anyway cause this port is unofficial.
Falk2 said:
By the way... Will there be a final CM10.2 version as well?...
Will it be possible to update from 10.1 to 10.2 by just flashing over CM10.1 ? (it is all 'Jelly Beans'...)
Click to expand...
Click to collapse
There won't be stable CM10.2 for sure. I could make a stable CM11, but man, even CM10.1 is pretty heavy for WFS. I shared all fixes I have with ARMv6Team, so A2DP and wired headset are fixed in CM11 now. But I won't join the development since I don't see the point.
okay, thank you. I will send you the Logcat later this night.
To TTS:
1) Is it used/necessary e.g. by GoogleMaps for the voice to navigate you? If so this would mean that lite-weight GAPPS packages do not support GoogleMaps navigation?...
2) It could be that the GAPPS package I mentioned before (s. this link http://forum.xda-developers.com/showthread.php?t=1917411) misses a folder 'tts'. I added it and will flash it later. Maybe that's the reason for the TTS crash. I will let you know.
3) Why didn't you include at Android settings the two options 'developer options' and 'performance'? (in CM9 they are included!) They would be very helpful!!
4) Can I just flash over your CM10.1 version from 17th Oct. the actual version from 18th Oct.? I work with INT2EXT2 !!
[Maybe I could avoid reinstallations each time by using LINK2SD instead?...] Or which part of the new version do I have to flash over?...
4b) May I just overwrite a CM10.1 version with version CM10.2 ?... (both are Jelly Bean!)
To 2): I just saw that the folder 'tts' is already included in your CM10.1 package. So I suppose that it should not be added in GAPPs again.
What I suppose now: While 'PicoTts.apk' is an offline TTS module the 'GoogleTTS' is an online one workimg together with the Google server. (It might be necessary for other online components like GoogleMaps navigation.) Right?
Falk2 said:
1) Is it used/necessary e.g. by GoogleMaps for the voice to navigate you? If so this would mean that lite-weight GAPPS packages do not support GoogleMaps navigation?...
Click to expand...
Click to collapse
Well yes, TTS is probably being used for voice output. I'm not sure it's being used in google maps though.
Falk2 said:
3) Why didn't you include at Android settings the two options 'developer options' and 'performance'? (in CM9 they are included!) They would be very helpful!!
Click to expand...
Click to collapse
Actually, I did. To unlock those you have to go settings - phone information and tap on build number seven times. Then you'll have those settings unlocked.
Falk2 said:
4) Can I just flash over your CM10.1 version from 17th Oct. the actual version from 18th Oct.? I work with INT2EXT2 !!!
Click to expand...
Click to collapse
You don't need to reflash. Just extract /system/lib/hw/gps.msm7x27.so and /system/etc/gps.conf from the zip and put them into the same places on your phone.
Falk2 said:
4b) May I just overwrite a CM10.1 version with version CM10.2 ?... (both are Jelly Bean!)
Click to expand...
Click to collapse
I think you can't since 10.2 is much different. Never tried it by myself though. Just make a backup, then do whatever you want.
Falk2 said:
What I suppose now: While 'PicoTts.apk' is an offline TTS module the 'GoogleTTS' is an online one workimg together with the Google server. (It might be necessary for other online components like GoogleMaps navigation.) Right?
Click to expand...
Click to collapse
I never actually used TTS since it does not support Russian, which is my native language. All I can do is take a look into logcat and see if I can fix it.
Regards.
I just sent you the logcat of the TTS problem by pastebin to niks255.
(I did not use a clean system but I think it will go anyway, will it?...)
Furtheron I would like to ask you the important question 4 again:
How can I update a (same) CM version (e.g. CM10.1) (if I do not have informations about the exact components changed!) WHEN using a link script like INT2EXT2?... (I already made some tries but failed)
Another little question...
I am missing in the boot menu (long press on power button) the (earlier) options like reboot to recovery, reboot to bootloader, etc.
Is there any reason why this disappeared at CM10+ ?...
Falk2 said:
How can I update a (same) CM version (e.g. CM10.1) (if I do not have informations about the exact components changed!) WHEN using a link script like INT2EXT2?... (I already made some tries but failed).
Click to expand...
Click to collapse
I suggest you copy /system/etc/init.d folder from your phone, add it into zip you flash and then flash it.
Falk2 said:
Another little question...
I am missing in the boot menu (long press on power button) the (earlier) options like reboot to recovery, reboot to bootloader, etc.
Is there any reason why this disappeared at CM10+ ?...
Click to expand...
Click to collapse
This option is still there. Go to settings - developer settings and set "Advanced reboot menu" option checked. To unlock developer settings, follow steps from the post above.
And please, provide a link to your logcat on pastebin here.
This is the link to the log: http://pastebin.com/FHGPrQfc .
I hope that you can find out the TTS crash reason!... Please let me know.
I will soon check if the way of update described works. However it sounds logical. Could work...
Falk2 said:
This is the link to the log: http://pastebin.com/FHGPrQfc .
I hope that you can find out the TTS crash reason!... Please let me know.
I will soon check if the way of update described works. However it sounds logical. Could work...
Click to expand...
Click to collapse
Seems pretty simple to me. Remove google now and install this from google play https://play.google.com/store/apps/details?id=com.google.android.voicesearch&hl=en then give me your feedback.
hmmh, I don't think that this is the reason...
Cause the TTS error message came already directly after login of the pretty new flashed CM10.1 package.
At LogCat I used 'Voice Search' of GoogleNow ('GoogleNowVoiceSearch.apk') just for starting TTS to demonstrate the error.
So you think that gapps-jb-4.2.2-light-20130824-signed does not suit to your CM10.1 package?...
Refering updates of same CM versions with SD-ext link scripts you are right: it worked just to copy the script to folder init.d. A good solution. Thank you!!
And also the two additional boot options can be activated.
What about the warm restart option. Doesn't this exist anymore?...
May I ask you some additional questions?...
* How would you compare CM9 with CM10.1 considering power consumption?
* Is there anything left that will not work of Bluetooth at CM10.1 ? Cause in the forums there is often mentioned s.th...
* And is it possible that design/themes/background collections are available like it is at CM9? I just see that files like MagicSmokeWallpapers.apk, VisualizationWallpapers.apk and LiveWallpapers.apk are not included anymore in your CM10.1 package. That's why the options 'background pictures' and 'Live background' don't find anything.
And there is still another point (no forum thread about that)...
It seems as if there is no local contacts 'account' at CMx (normally called 'phone') but only the own Google account. Isn't this unusual?...
Not wanting to use the Google account would mean to create an extra one?...
Thanks for your feedback!
If I remove 'GoogleNow.apk' and even 'GoogleNowVoiceSearch.apk' I still cannot install app VoiceSearch (it is still installed).
It is another app in the system folder that you want me to exchange: VoiceSearch.apk. It does not seemt to have s.th. to do with 'GoogleNowVoiceSearch.apk' which I used to execute TTS.
Do you want me to remove this as well?...
I can also use 'Android settings -> Speech and Input -> text-to-speech output' to start TTS. It crashes here as well!... So the problem should not be the VoiceSearch module.
Does the option 'Speech search' just above works on your mobile? Here it does not work as well!...
Falk2 said:
If I remove 'GoogleNow.apk' and even 'GoogleNowVoiceSearch.apk' I still cannot install app VoiceSearch (it is still installed).
It is another app in the system folder that you want me to exchange: VoiceSearch.apk. It does not seemt to have s.th. to do with 'GoogleNowVoiceSearch.apk' which I used to execute TTS.
Do you want me to remove this as well?...
I can also use 'Android settings -> Speech and Input -> text-to-speech output' to start TTS. It crashes here as well!... So the problem should not be the VoiceSearch module.
Does the option 'Speech search' just above works on your mobile? Here it does not work as well!...
Click to expand...
Click to collapse
Reflash the ROM and flash those Gapps I gave you then install voice search from google play.
I don't understand...
That makes no sense cause those Gapps are unnecessary small. I have more ROM.
Furtheron they do not contain the necessary GoogleTTS.apk which is the one that crashes.
So with a small Gaps package your version will always work as it does not have the available, additional features!...
So could you meanwhile test your CM10.1 with my Gapps version? That would be a good idea as well, I suppose, wouldn't it?
And would you be so kind and just comment my last requests? ( I assure you I won't ask anymore afterwards ) )!
Thank you so much !!
Falk2 said:
I don't understand...
That makes no sense cause those Gapps are unnecessary small. I have more ROM.
Furtheron they do not contain the necessary GoogleTTS.apk which is the one that crashes.
So with a small Gaps package your version will always work as it does not have the available, additional features!...
So could you meanwhile test your CM10.1 with my Gapps version? That would be a good idea as well, I suppose, wouldn't it?
And would you be so kind and just comment my last requests? ( I assure you I won't ask anymore afterwards ) )!
Thank you so much !!
Click to expand...
Click to collapse
That makes perfect sense cause TTS seems to be using CM10.1 voice input according to your logcat. Just try it.
And live wallpapers are included in CM10.1. They were not in CM10, but it's also fixable.
Talking about battery life. I got the best results on CM10. On CM9 I was having some strange battery drain sometimes. I could even find my phone turned off when I wake up. That problem does not exist on CM10 and higher.
So you mean that 'my' Gapps (for v4.2.2!) are unnecessary big? And your ZGapps already include all possible and necessary functions?... E.g GoogleTTS.apk must not be included as TTS is 'double-functioned' then?...
So how do I have to configure it now (which apks do I need and which are unnecessary (e.g. 'GoogleNowVoiceSearch.apk', 'GoogleNow.apk', GoogleTTS.apk, etc.). Just check it in my GAPPs please!) that...
1.) GoogleNow Voice search does not crash?
2.) 'Android settings -> Speech and Input -> text-to-speech output' does not crash?
And yes, I saw that LiveWallpapers are included as an apk. BUT when I go to Background->Live-Backgrounds the entrance is EMPTY!!
(and option 'background pictures' contains just one picture)
Why is that so?...
The only working option I have right now is 'CM background pictures'!...
Thank you for your feedback concerning power consumption.
So Bluetooth works fine now on CM10 and CM11 ??
By the way...
Do you think the CM11 version for Marvel is already stable enough to be ready for normal/daily use?
And are there (functional) reasons why KitKat should be prefered to Jelly Beans?...
Falk2 said:
So how do I have to configure it now (which apks do I need and which are unnecessary (e.g. 'GoogleNowVoiceSearch.apk', 'GoogleNow.apk', GoogleTTS.apk, etc.). Just check it in my GAPPs please!) that...
1.) GoogleNow Voice search does not crash?
2.) 'Android settings -> Speech and Input -> text-to-speech output' does not crash?
Click to expand...
Click to collapse
I don't know about CM 10.1 as I'm running CM 10 now, but on CM10 with those Google apps TTS works just fine.
Try mine google apps for CM10.1 https://cloud.mail.ru/public/ed9c151ccbf5/Gapps.zip
Falk2 said:
And yes, I saw that LiveWallpapers are included as an apk. BUT when I go to Background->Live-Backgrounds the entrance is EMPTY!!
(and option 'background pictures' contains just one picture)
Why is that so?...
The only working option I have right now is 'CM background pictures'!...
Click to expand...
Click to collapse
Live Backgrounds is empty because you don't have any live wallpaper installed. Download one from google play and you'll be fine.
The ROM contains just one background to reduce ROM size. It hardly fits internal memory, so I guess devs just had to slim it as much as possible. You can set any picture as a background.
Falk2 said:
Thank you for your feedback concerning power consumption.
So Bluetooth works fine now on CM10 and CM11 ??
Click to expand...
Click to collapse
Not sure about CM11 yet, but on CM10 and CM10.1 it works just fine.
Falk2 said:
By the way...
Do you think the CM11 version for Marvel is already stable enough to be ready for normal/daily use?
Click to expand...
Click to collapse
It isn't stable enough and it will never be.
niks255 said:
I don't know about CM 10.1 as I'm running CM 10 now, but on CM10 with those Google apps TTS works just fine.
Try mine google apps for CM10.1 https://cloud.mail.ru/public/ed9c151ccbf5/Gapps.zip
Click to expand...
Click to collapse
* How should Google TTS work if GoogleTTS.apk is not installed on your side? As I already mentioned: your Gapps package does not contain it!... So both options ('Speech Search' and 'Online TTS') do not even appear in your settings menu!!!
* You write that you don't know about CM 10.1?... I thought you have finished both 10.0 and 10.1 and that you are a developer!?.... Didn't you fix the last problems at CM10.x? The way you announced it.
If not could you please inform me what you exactly did/improve at both (CM10.0 and CM10.1 ) compared to the most actual version I know: 'cm-10.1-20131025-OWLPROJECT-marvel.zip'?
* 'My' Gapps link http://forum.xda-developers.com/showthread.php?t=1917411 include very nice additional features! Did you check meanwhile?... Those should work properly with proper stable running CM10.x versions, of course - GoogleTTS included, shouldn't they?...
So don't you care for those functions as well (not just suggest a smaller Gapps package).
Didn't you say: "What's not working:... You tell me." So I did...
* Can you please tell me otherwise where to find another most actual and proper working CM10.1 version (of this year)?
* By the way, which CM10.x version did you take as the basic version of yours?
Three more little questions:
- All CM10 apk files in your packages are dated from February 2008. Isn't that strange that one cannot see the real date/actuality of each component?...
- Do you know why there are different packages for each three JB versions?... (maybe my GoogleTTS.apk was mixed up!)
- How can I test other Gapps easily? I should clean and overwrite the Gapps. My only idea would be to format only system folder and flash Rom and Gapps again. Any better idea?...
-------------
However this discussion is difficult because I don't have informations about the function of each Gapps app. How can I find out? Don't you know maybe any explaining listing/document?
niks255 said:
Live Backgrounds is empty because you don't have any live wallpaper installed. Download one from google play and you'll be fine.
The ROM contains just one background to reduce ROM size. It hardly fits internal memory, so I guess devs just had to slim it as much as possible. You can set any picture as a background.
Click to expand...
Click to collapse
Hmmh. Again I don't understand... At last you wrote: "And live wallpapers are included in CM10.1. They were not in CM10, but it's also fixable." So I should have Live Wallpapers. But now you say I havn't...
In fact LiveWallpapers.apk is not included in your CM10.1, Nick! Now I took the one of CM9: I could install it but they cannot be loaded. It shows 2 pictures. The same app shows in CM9 9 pictures...
Anyhow, they are wrong for CM10. Do you know where I can get LiveWallpapers.apk for CM10.x compatible with Trebuchet ??
niks255 said:
Not sure about CM11 yet, but on CM10 and CM10.1 it works just fine.
Click to expand...
Click to collapse
Okay, fine.
Why don't you are using CM10.1?...
niks255 said:
It isn't stable enough and it will never be.
Click to expand...
Click to collapse
I have a CM11 version here that seems to run fine (up to now). But I am not sure about its power consumption and speed.
Hallo again Nick,
meanwhile I tested your Gapps. My complaints are right.
As I mentioned above: GoogleTTS cannot crash with your Gapps because it is not installed.
At 'Settings->Speech&Input->Text-to-Speech output' you cannot choose between Google TTS and Pico TTS but you have only the last one!
But if you - as I wrote - choose the online-TTS version (sounds much better!!) with GoogleTTS.apk it crashes.
So it really does not seem to work together with your CM10.1 and you should improve this please.
The same with 'Settings->Speech&Input->Speech search': it does not work. If I choose this option everything hangs on.
This is the second point/problem that obviously should be fixed.
Please just install GoogleTTS.apk and VoiceSearch.apk in your systems folder of your CM10.1 version.
Now please test the mentioned two functions!
By the way: I just did so at another CM10.1 release (which I do not like so much than yours) and it worked fine! So it should generally work with yours as well but doesn't !...
Would be perfect if you could find solutions for both problems.
Thank you very much!
PS: I tested all this also at CM9. Here GoogleTTS is also included (in a lite Gaps package!). And here both functions work perfect: Speech Search AND Text-to-Speech Output !!
It seems to be sure: There is s.th. wrong at your CM10.1 version!
[Back 2 Basics]
Simple privacy oriented rom based on stock, just like in old days.
[The way you like it]
Keep it simple or modify
Your Phone
Your Rom
[Simplicity]
So simple, your grandparents could use it
[Security]
Privacy is our right
Stop feeding corporations with your data
[Speed]
Do you need to buy visually faster phone every year, so the manufactures would produce more electronic waste?
Use your phone at full potential instead!
XDA:DevDB Information
[TomaHawk]Back2Basics, ROM for the Sony Xperia XZ Premium
Contributors
Doom Slayer
ROM OS Version: 9.x Pie
Based On: Sony Stock
Version Information
Status: Testing
Current Beta Version: 0.2
Beta Release Date: 2020-07-28
Created 2020-07-28
Last Updated 2020-07-28
How To
[Installation]
Assuming you unlocked your bootloader and have TWRP
IF WIPED SYSTEM/USING AOSP/WANT TO ENABLE SECOND SIM ON G8141
Flash This with a newflasher
CONTINUE:
P.S. Keep a TWRP backup of stock rom on your phone, so you won't need to use newflasher again.
Install this on top of the stock/stock based rom (like Tomahawk Project)
Don't forget factory reset!
Links:
AFH
GDRIVE
CONTINUE:
[Freedom of choice]
FOR MAXIMUM SECURITY:
Keep it simple, without ROOT
Install F-Droid and explore open source world. Download APK and send it to your device. I removed browser, pick your own
At your own risk:
If you want download apps from playstore anonymously, try Aurora Store
Want to get accurate Network location and some of the Google apps working properly, then install this Magisk Module
To get Network Location working, signature spoofing is needed. You'll need this or this edXposed module
If you think my work was for nothing:
Install Gapps and never visit this thread again
Changelog
0.1
Initial release
0.2
Fixed broken GSM + Data
Privacy made Easier
Let's find a balance between security and ability to use apps which we have to.
Most of us have people who use messengers we don't trust, but we still need to communicate with those people.
Another CONCERN is a fact that most of the apps rely on google for push notifications. Google get all the content, no matter how secure your messenger is.
If you don't have Google Services, then you have problems with notifications. Here MicroG will help us.
So, let's make a secure environment for apps we use, but don't trust.
You gonna need:
This rom installed
Magisk + "microG installer Revived"
Shelter
Let's do it!
Open Shelter app and let it create work profile.
Then you need to make sure install some apps in there:
If you install Aurora Store inside Shelter it will allow to easily manage apps from Play Store.
You can clone magisk to shelter( enable multi user in the main app first, then clone) and install firewall inside the shelter.
Update:
Another way is to install vpn inside shelter and enable kill switch. So apps inside shelter only won't have internet access unless you enable VPN.
I use protonvpn, it give 3 countries for free and it's more than enough for average user.
Beware that when VPN is outside of the shelter, on the mainland, apps on shelter will bypass it, so you need to have clients on both. You may have 2 different VPN clients enabled if you need to.
What do we get?
See "Contacts" and "Files"?
Those are seperate from the mainland, so you can just add your relatives' phone numbers and WhatsApp will only see those.
We are LIMITING ACCESS TO FILES AND CONTACTS.
Plus we can easily freeze those apps, or limit connectivity with a firewall, or vpn.
Result:
You can use apps, that brings vulnerabilities or privacy concerns in a locked,controlled environment.
Still receive notifications without sending them to Google.
Or you can try VMOS, at your own risk of course
Short message for each of you.
This rom is a result of a project which aim to strip android back to it's core, so WE CAN BUILD IT THE WAY WE WANT IT. Not the way market researchers say we want it.
In short, this ROM is a prototype of community communication device.
Everyone can join the digital freedom project. I am sure each of us can help a cause.
Is ther any way to get real all the 4k working all time
mahmoodsaud said:
Is ther any way to get real all the 4k working all time
Click to expand...
Click to collapse
Not real,but VM
If you set "apply on boot", you will notice that boot animation will become smaller ,but it's the same trickery as adb commands.
g8141 does not work, reboots right after sony logo no bootanimation.
p.s. flashed over .107 stock rom with twrp 3.2.3-0
edit: installation guide is a bit vague, do we MUST flash this? https://androidfilehost.com/?fid=4349826312261694774
It says
IF WIPED SYSTEM/USING AOSP/WANT TO ENABLE SECOND SIM ON G8141
but I didn't wiped system nor using aosp nor want to enable second sim
second edit: Needs few reboots before booting to system, seems to work like intended.
Some suggestions:
Please find a solution to Automatic reboot when sim tray is removed, since I don't use dual sim and switch SD cards frequently it gets frustrating so fast. Thanks in advance.
Qualcomm Device Security still persists on this rom, it has an apk under vendor\app\QualcommTelemetry(?)
Video Enhancement is not working, at least on settings preview.
VERY USEFUL: Show charging current on lock screen, existenz rom had it.
Dark/Full Black System theme
Boot time is unacceptable, it takes around 2 minutes for normal boot, whereas even in a bloated stock it took around 30~ seconds. It is due to your framework changes and deodexing. However, I've been able to restore optimal boot time by changing all frameworks.
@undefine,
Yeah, boot time is longer because because of deodexing. Frameworks are untouched though in this rom.
If you want Video Enhancements, then you need to go back to android 8 and istall drm patch.... Since they fixed the camera on Pie nobody really bothers with other drm related things...
Agree on the dual sim reboot thing, it's annoying, but I have no idea how to disable it for now. If you really don't need to dual sim functionality then you can try flashing this rom on top of G8141 version and make sure you got kernel as well.
Theme is overlay, adding functionality to the lock-screen require modifying services.jar to disable signature (super user mod), both are security risks... You may flash existenz on top and remove what you don't need. At your own risk of course
Doom Slayer said:
@undefine,
Yeah, boot time is longer because because of deodexing. Frameworks are untouched though in this rom.
If you want Video Enhancements, then you need to go back to android 8 and istall drm patch.... Since they fixed the camera on Pie nobody really bothers with other drm related things...
Agree on the dual sim reboot thing, it's annoying, but I have no idea how to disable it for now. If you really don't need to dual sim functionality then you can try flashing this rom on top of G8141 version and make sure you got kernel as well.
Theme is overlay, adding functionality to the lock-screen require modifying services.jar to disable signature (super user mod), both are security risks... You may flash existenz on top and remove what you don't need. At your own risk of course
Click to expand...
Click to collapse
I think boot time is not because frameworks are changed but some are missing, I just reflashed with everything in stock framework folder, it seems to be blazing fast as normal. I'm actually surprised it booted that fast even with Deodex.
As far as I remember Video Enhancements worked on stock 9 at least on my device, I have my drm keys though since I waited for a proper ta backup. However it is not a must feature either.
I'd rather flash opengapps full package than flashing existenz over this rom . I will look into some other tricks for showing charge current, maybe some xposed module exists?
Anyway, thanks for your contribution to this device. Cleanest stock rom I've ever used (besides one bloat called Qualcomm Device Security which I immediately removed).
Hello everyone,
Recently I have been experimenting with custom ROMs on my Samsung phone and was very unpleasantly surprised to find that Samsung does not allow my Galaxy Watch to be used with modded Samsung phone... Yeah, I know there's the option to replace manufacturer and brand in build.prop, however I don't like the idea of unnecessarily modifying the system just for a couple of proprietary apps, so instead I took the approach of patching the apps to make them work with the phone again.
All that needed to be done was patch manufacturer and brand to static string(s). Here's a command to do just that:
Bash:
find . -type f -name "*.smali" -exec sed -i 's/sget-object \(v\|p\)\(.\+\), Landroid\/os\/Build;->\(MANUFACTURER\|BRAND\):Ljava\/lang\/String;/const-string \1\2, \"letitbeheardthisphoneistobetreatedasifitwereofabranddifferentfromtheonestartingwiths\"/g' "{}" \;
Patching the apps, however made the shealth app refuse communication with the wearable app due to mismatching signing certificates and it needed to be patched too. It is possible to either completely bypass signature checking or insert custom certificate - I have attached a patch that does just that.
You can (and probably should) do this yourself if you want to use the modified applications. Just decompile apks with apktool, apply the command in the directory with the apps content (it is necessary for Galaxy Wearable, Samsung Accessory and Galaxy Watch Plugin apps), and insert you own custom certificate into Galaxy Watch Plugin (attached patch - just replace the cert with your custom one). If you use Samsung Health, just replace the certificate string with hex-encoded certificate you used to sign the apps in the attached patch and apply it to the app. Then rebuild the apps and sign using the key whose certificate you just inserted into the apps.
Although you should never trust a random stranger on the internet with apps you install, I understand not everyone wants to go through this process themselves, so hereby I solemnly promise there is no malicious code inserted into the provided apks. And here's the link
App Versions:
Samsung Accessory (com.samsung.accessory): 3.1.94.11128
Galaxy Wearable (com.samsung.android.app.watchmanager): 2.2.42.21083061
Galaxy Watch PlugIn (com.samsung.android.geargplugin): 2.2.05.21042051
Samsung Health (com.sec.android.app.shealth): 6.18.7.005
No idea what you're talking about. My watch works fine with my note 10+ using Dr ketan rom.
Same with Alexis. I just hide it with magisk but it was working just fine before that.
dchd310870 said:
No idea what you're talking about. My watch works fine with my note 10+ using Dr ketan rom.
Click to expand...
Click to collapse
Leon said:
Same with Alexis. I just hide it with magisk but it was working just fine before that.
Click to expand...
Click to collapse
I was talking about AOSP-based ROMs. Generally, I build and sign the ROM whenever possible and so I don't find it necessary to root my devices. Also I don't like the idea of making changes to mask the actual device and when the app is used with Samsung phone, it relies on proprietary interfaces implemented only in Touchwiz, which are not available in AOSP. Since it is an app issue, it makes sense to make changes on the app level instead of the system level.
dansimko said:
I was talking about AOSP-based ROMs. Generally, I build and sign the ROM whenever possible and so I don't find it necessary to root my devices. Also I don't like the idea of making changes to mask the actual device and when the app is used with Samsung phone, it relies on proprietary interfaces implemented only in Touchwiz, which are not available in AOSP. Since it is an app issue, it makes sense to make changes on the app level instead of the system level.
Click to expand...
Click to collapse
Hi,
I 've got the same problem with the rom Beyond V2.0.
Can you explain more precisely what i must do with yours files ? I'm a novice and my english not very good.
Thank a lot
Hello,
I'm using a unrooted (root not available yet) but knox tripped Samsung Galaxy S21 Ultra. Because of no root i'm not be able to edit build.prop to change the tima line. Now I'm searching a way to get Samsung shealth 6.15.1.003 get working with data sync. To be honost i dont really understand how to patch this way. Could somehone explain me what to do? Samsung health is already decompiled with APK Easy Tool. Thanks in Advance
Hallo sir can you update the files or explain a bit further how to do it by ourselves
Could you be more specific. I want to try it but I dont understand how to doit. some one knows how to patch these apks. ? you tube video? thanks.
hi sir, thank you for your hard work. looks good and might be what i wanted. just rooted my phone and i cant seem to pair my gear sport with my rooted S20+.
Do i just install the apk like normal, running it in file manager? or do i need to flash it in through custom recovery?
fwiw i use an Active 2 with a rooted Pixel 2 XL, and dont need any of that and have ECG/BP and Samsung Pay working. Only modified thing is the Samsung Health monitor app on the phone, modded to not detect root or require a Samsung Phone, thats it....
I own a s5neo with lineage 17.1 and I had the same problem as reported, galaxy wearable identified my phone as modified/rooted and exited. Using your apk I was able to launch the app but it fails to install the galaxy buds live plugin, only shows a message that failed to install.
I don't know how to do the patch and I would like to know if you can generate a patched apk for buds live plugin (https://play.google.com/store/apps/details?id=com.samsung.accessory.neobeanmgr&hl=en_GB)
thanks in advance
Can I use it for Spay?
nevermindrs said:
I own a s5neo with lineage 17.1 and I had the same problem as reported, galaxy wearable identified my phone as modified/rooted and exited. Using your apk I was able to launch the app but it fails to install the galaxy buds live plugin, only shows a message that failed to install.
I don't know how to do the patch and I would like to know if you can generate a patched apk for buds live plugin (https://play.google.com/store/apps/details?id=com.samsung.accessory.neobeanmgr&hl=en_GB)
thanks in advance
Click to expand...
Click to collapse
I have Galaxy Buds+ on a Pixel 2 XL
Heres how to do it the easy way...
Install Magisk
Enable MagiskHide in Magisk Manager settings
Tick all Samsung related apps in MagiskHide in Magisk Manager
Hide Magisk Manager
Reboot
Thats how i also have my Active 2 and Samsung Pay working
^yep, magisk is magic!
dansimko said:
I was talking about AOSP-based ROMs. Generally, I build and sign the ROM whenever possible and so I don't find it necessary to root my devices. Also I don't like the idea of making changes to mask the actual device and when the app is used with Samsung phone, it relies on proprietary interfaces implemented only in Touchwiz, which are not available in AOSP. Since it is an app issue, it makes sense to make changes on the app level instead of the system level.
Click to expand...
Click to collapse
Hi,
I am unable to install any of the apk. App not installed.
Please help me.
dansimko said:
Hello everyone,
Recently I have been experimenting with custom ROMs on my Samsung phone and was very unpleasantly surprised to find that Samsung does not allow my Galaxy Watch to be used with modded Samsung phone... Yeah, I know there's the option to replace manufacturer and brand in build.prop, however I don't like the idea of unnecessarily modifying the system just for a couple of proprietary apps, so instead I took the approach of patching the apps to make them work with the phone again.
All that needed to be done was patch manufacturer and brand to static string(s). Here's a command to do just that:
Bash:
find . -type f -name "*.smali" -exec sed -i 's/sget-object \(v\|p\)\(.\+\), Landroid\/os\/Build;->\(MANUFACTURER\|BRAND\):Ljava\/lang\/String;/const-string \1\2, \"letitbeheardthisphoneistobetreatedasifitwereofabranddifferentfromtheonestartingwiths\"/g' "{}" \;
Patching the apps, however made the shealth app refuse communication with the wearable app due to mismatching signing certificates and it needed to be patched too. It is possible to either completely bypass signature checking or insert custom certificate - I have attached a patch that does just that.
You can (and probably should) do this yourself if you want to use the modified applications. Just decompile apks with apktool, apply the command in the directory with the apps content (it is necessary for Galaxy Wearable, Samsung Accessory and Galaxy Watch Plugin apps), and insert you own custom certificate into Galaxy Watch Plugin (attached patch - just replace the cert with your custom one). If you use Samsung Health, just replace the certificate string with hex-encoded certificate you used to sign the apps in the attached patch and apply it to the app. Then rebuild the apps and sign using the key whose certificate you just inserted into the apps.
Although you should never trust a random stranger on the internet with apps you install, I understand not everyone wants to go through this process themselves, so hereby I solemnly promise there is no malicious code inserted into the provided apks. And here's the link
App Versions:
Samsung Accessory (com.samsung.accessory): 3.1.94.11128
Galaxy Wearable (com.samsung.android.app.watchmanager): 2.2.36.20113061
Galaxy Watch PlugIn (com.samsung.android.geargplugin): 2.2.05.20110441N
Samsung Health (com.sec.android.app.shealth): 6.12.3.001
Click to expand...
Click to collapse
how to generate hash from keystore. can anyone help? @dansimko
mohsin1122 said:
how to generate hash from keystore. can anyone help? @dansimko
Click to expand...
Click to collapse
Generate Hex from keystore
keytool -alias mykey -exportcert -keystore my-release-key.keystore -storepass 123456 | xxd -p
To anyone coming across this post who wants to do this themselves, I've made a little guide and some tools here: https://github.com/adil192/SamsungAppsPatcher.
I've also attached the apks I've patched if you don't want to do it yourself (since the ones in OP didn't work for me) here: https://mega.nz/folder/sUFj2C5b#M4zEP-c9ylY-ENxPw7qCUQ. Like OP, I promise I haven't added malware in this.
Edit: I've somewhat automated the process now so if anyone wants me to patch another plugin, just @ me and I'll get it added as soon as possible.
Adil192 said:
To anyone coming across this post who wants to do this themselves, I've made a little guide here: https://gist.github.com/adil192/ab95808fb66b6cde3d63ded6c19b0f1d. I've also attached the latest apps I've patched if you don't want to do that (since the ones in OP didn't work for me) here: https://mega.nz/folder/sUFj2C5b#M4zEP-c9ylY-ENxPw7qCUQ. This is tied to my name so I have no reason to add malicious code.
Click to expand...
Click to collapse
I need assistance with the gear s3plugin apk please.
Got it working..thanks
Would this process work to enable the Galaxy Wearable App to connect if using non-uk galaxy buds live? My app sets up the buds live but then fails to connect, even though Bluetooth connects and buds function.
Samsung have advised I have a Vietnamese version of the buds live which are not compatible with the Galaxy Wearable App in the UK.