Database Develop

[CM7/ICSP/MIUI][GPS FIX] Yet Another Software GPS Fix VERSION 2 - 12/13/11

Yet Another GPS Fix
YAGF Version 2
For users running AOSP Gingerbread (CM7) and ICS (CM9/ICS Passion) ROMs​
Why another GPS Fix?
This GPS fix is a modification of the GPS fix by strictlyrude27 (link). The newest builds of CM7 don't play nice with that GPS fix and hang at the kernel boot screen for 10 minutes waiting to download GPS LTO data.
This fix does several things differently:
It addresses the 10-minute hang time by removing GPS LTO data download altogether. I have no problem getting a GPS fix without it! You can see the test results below.
It uses a modified GPS library that actually reads config files (even if you don't have AngryGPS installed), now finally allowing Google's SUPL server to be used.
It lets the GPS use hot fixes now. After getting an initial fix, if you leave and come back to the GPS later you can get a fix in as little as 2 seconds.
It cuts out AngryGPS. You can still use it if you want to do GPS performance testing, but the configuration it writes will not be of any use. You can uninstall AngryGPS if you want now! This is to allow the fix to work properly even if you do not have AngryGPS installed.
Important for ICS users: If you are getting issues with GPS locks after deep sleep, you may need to try WallaceLau's addendum to this fix. As I am not having issues with GPS dying after deep sleep, I cannot vouch for the effectiveness of copying over HTC Desire GPS files, but as it does not overwrite any existing files, it should be fairly harmless.
Note for ICSP RC1 (v13): This fix is only halfway onboard. You should flash this fix after flashing the ROM and cleanup zips to get the proper configuration files.
What does this work on?
This works on the latest CM7 and CM9/ICS PASSION builds.
This has been tested with the stock CM7 kernel, Eugene373's Streamline kernel (EB7 build), and the Glitch V13 kernel.
Users have reported it working with MIUI as well.
I have not tested this on any other configurations! YMMV even on these configurations!
Testing method
To test the GPS effectiveless, the time to first fix (TTFF) was tested using the S/W test mode in AngryGPS. Interval 5 seconds, cold fix, with XTRA download enabled. Timeout was set to 255 seconds.
I wiped and reinstalled nightly 182 between each set of tests. The phone was connected to a wifi network during all the tests to obtain the best possible speed for XTRA data download.
10 TTFF data points were obtained for each test configuration. Error bars are calculated as the standard error of the mean (SEM) of each data set.
Test results
The stock installations of CM7 and the Glitch kernel do not have any sort of GPS fixes built in and fail to lock within 255 seconds. The Streamline kernel has a GPS fix but only acquired a lock 5 out of 10 times (50%).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Comparing only the GPS fix from strictlyrude27 and this fix:
What do the graphs mean?
This shows that these two GPS fixes essentially perform the same, and that removing LTO download (and the 10 minute hang time on boot) has no statistically significant effect on GPS performance.
In addition, one can conclude that using either Streamline or Glitch kernels offers significant GPS performance benefits over the stock CM7 kernel.
Is it safe to flash?
Most likely (though I offer no guarantee of this)! All this does is delete your old GPS fixes if they are present, delete the agpsd daemon that was causing problems on my CM7 Vibrant, and flash the gpsd and gps.conf that were in strictlyrude27's fix. If that fix didn't give you problems, this one definitely won't.
INSTRUCTIONS
Have CM7.1.0.1 or a newer nightly installed on your Vibrant
Transfer yagf2.zip to your phone
Turn off the GPS!
Reboot into recovery
Flash your kernel of choice (if you have not done so already)
Install yagf2.zip from wherever you put the file
Reboot and turn on the GPS. Enjoy!
Download below as an attachment
Mirror
Version 1 (Old version)

Thanks for this. You know, I still can't reproduce the bootloop issue; I'm running the latest nightly. I wonder if this is a kernel thing? I'm on Glitch V13..

I'd only had working GPS on one 2.2 rom since I'd gotten the phone in July of last year...until I'd flashed this! Thank you so much!
Sent from my SGH-T959 using XDA App

strictlyrude27 said:
Thanks for this. You know, I still can't reproduce the bootloop issue; I'm running the latest nightly. I wonder if this is a kernel thing? I'm on Glitch V13..
Click to expand...
Click to collapse
I think it's only in the more recent builds since they redid the init system that it happens. What nightly are you using, or are you on stable? I'm guessing the init scripts were reordered so that the network got initialized after the files in /etc/init.d were run, but I haven't really looked that much into it.
Interestingly enough, they did add in a gpslto service in init.aries.rc that calls a nonexistent file, /system/bin/get-gps-lto, but I was playing around with it and couldn't get it to work.

Already had a pretty stable gps running with Streamline Kernel and CM7 nightly (kb5)
it always took about a minute for it to load up, but it was getting to a point where I could expect a gps lock with a bit of hopeful regularity.
After flashing this, my first attempt for a gps lock would yield no results no matter how long i left it on, and if i exited out of gps test, the gps icon would never reappear. i attempted to delete gps data and do some tiff tests as well, but for some reason the gps icon will only initialize once per boot, and i've never gotten anywhere with it.
Should I re-flash streemline AFTER installing this patch? Do you recommend deleting gps data before you flash?
I've restored a pre-fix backup and reflashed twice now, yielding the same results.
Might try again tomorrow. I was very hopeful for this one.
Streemline has already worked wonders. I'm confident gps will only get better with the vibrant.
edit: hrm. I might have gone about this incorrectly. You have a gpsfix.zip file attacked to this post, yet your instructions are to flash yagf1.zip. I had assumed that you meant your gpsfix.zil file and perhaps made a type or something. going to attempt to flash one more time with the specific mirrored yagf1.zip file. What is the gpsfix.zip file attached to this post? It's not mentioned.
edit 2: also, step 3. in the first post is to flash the kernel of your choice. if i'm already on the kernel of my choice is this necessary? must we reflash the kernel AND the fix in one go from cwm before booting up?
edit 3: HOOOOOLY CRAP! THIS IS AMAZING! I used a kernel cleaning script in cwm, then flashed streamline, then the yagf1.zip file. booted up. and got a lock within 10 seconds. it's the fastest this puppy has ever EVER fired up. I'm so very impressed. Well done sir. This is the best gps signal i've ever gotten, and i was already impressed with the progress with eugenes kernel. Give this a try people!
edit 4: dumb question. in angry gps, what exactly does 'delete gps data' do. does it negate any of this fix? everyone seems to recommend it, but i don't want to ruin any fixes i've flashed.

twotone8 said:
Should I re-flash streemline AFTER installing this patch? Do you recommend deleting gps data before you flash?
Click to expand...
Click to collapse
Reflashing the kernel will overwrite this GPS fix, so no, don't reflash it.
twotone8 said:
edit: hrm. I might have gone about this incorrectly. You have a gpsfix.zip file attacked to this post, yet your instructions are to flash yagf1.zip.
Click to expand...
Click to collapse
Oops. I didn't notice that, you're absolutely right. They're the same file, just with different names. I decided to rename it something with a later letter in the alphabet so I could just hit the vol+ button in recovery a few times to get to the file more quickly I've renamed it now.
twotone8 said:
edit 2: also, step 3. in the first post is to flash the kernel of your choice. if i'm already on the kernel of my choice is this necessary? must we reflash the kernel AND the fix in one go from cwm before booting up?
Click to expand...
Click to collapse
nope, just go ahead and flash this on top of it. This cleans up any interfering GPS fixes that might have been flashed alongside your kernel.
twotone8 said:
edit 4: dumb question. in angry gps, what exactly does 'delete gps data' do. does it negate any of this fix? everyone seems to recommend it, but i don't want to ruin any fixes i've flashed.
Click to expand...
Click to collapse
I think it deletes the temporary data about the satellites in current view generated by gpsd that can be used for a "hot fix" within the next few minutes. Deleting it forces your GPS to do a "cold fix" (assisted by the xtra data and network location). It doesn't negate this fix.

rexrbgh said:
I'd only had working GPS on one 2.2 rom since I'd gotten the phone in July of last year...until I'd flashed this! Thank you so much!
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I finally have a working GPS on my Vibrant. This is the only fix that has worked for me. Every time I turn my GPS on now it actually stays locked on to satellites for the whole time I use it. This has NEVER happened to me before. Thanks alot.

Never had working gps on gingerbread until now. Thank you very much kind sir.
Sent from my SGH-T959 using xda premium

Seemed to work, nice work.. thanks!
Sent from my SGH-T959 using xda premium

Excellent work. I never quite got there with previous GPS fixes for CM or other 2.3.x ROMs.
I love using Waze to monitor traffic conditions, report problems, etc. Lack of reliable GPS had kept me on 2.2. It takes a little while for GPS to get a lock, but I suspect that will improve.
So, do you have a tip jar?
---------- Post added at 07:03 AM ---------- Previous post was at 06:58 AM ----------
twotone8 said:
edit 3: HOOOOOLY CRAP! THIS IS AMAZING! I used a kernel cleaning script in cwm, then flashed streamline, then the yagf1.zip file. booted up. and got a lock within 10 seconds. it's the fastest this puppy has ever EVER fired up. I'm so very impressed. Well done sir. This is the best gps signal i've ever gotten, and i was already impressed with the progress with eugenes kernel. Give this a try people!
Click to expand...
Click to collapse
Which script did you use?

This thing works...
Sent from my SGH-T959 using XDA App

The GPS attempts to lock in maps then the GPS lock icon/indicator never shows up again when I try any other program that requires GPS... until I reboot.
Flashed the latest nightly with everything wiped
Eugene streamline
YASGPS fix
I think I'm in the "results may vary category". From what I've been reading, that is because Vibrant hardware differs from one another. The one I'm using was manufactured Jul/06/2010.

Don't give up yet. That's exactly what mine used top do when I flashed this. just keep trying things. what worked for me one time was simply to disable GPS before a restart, then re enable it and everything worked great.
I had it working perfectly, them had to do a nandroid restore, and that problem came right back. Somewhere between reflashing kernels, fixes, restarts, and finally just turning of GPS before restarting. every thing works great again.
Sent from my SGH-T959 using XDA App

jsparakov said:
The GPS attempts to lock in maps then the GPS lock icon/indicator never shows up again when I try any other program that requires GPS... until I reboot.
Flashed the latest nightly with everything wiped
Eugene streamline
YASGPS fix
I think I'm in the "results may vary category". From what I've been reading, that is because Vibrant hardware differs from one another. The one I'm using was manufactured Jul/06/2010.
Click to expand...
Click to collapse
Can you try fixing permissions and clearing your dalvik cache in recovery? If that doesn't work can you send me a logcat?

chui101 said:
Can you try fixing permissions and clearing your dalvik cache in recovery? If that doesn't work can you send me a logcat?
Click to expand...
Click to collapse
I've cleared dalvik cache many times already. Edit: but I'll continue to do so every time I make an attempt.
I'll go ahead and try those two with the nightly. Let me know if you have any particular way of doing logcat other than adb (I don't do this very often).

jsparakov said:
I've cleared dalvik cache many times already. Edit: but I'll continue to do so every time I make an attempt.
I'd be very happy to follow those other two suggestions. Do you have any link to instructions on how to do those two things properly (what and how to fix the files + creating a logcat)?
Click to expand...
Click to collapse
Fixing permissions is under the 'advanced' menu in CWM recovery, I believe.
You can do a logcat on the phone by opening up the terminal emulator and typing logcat. You can redirect output to a file with -f (i.e. 'logcat -f /mnt/sdcard/logcat.txt'). Run it before you open up Maps, then let it run in the background while you open up maps. When you are done, close it with CTRL-C (VOL- + C in the terminal emulator).
Alternatively, you can do this from your computer by using adb if you have it installed. Just do adb logcat -f /mnt/sdcard/somefile.txt and it'll save a logcat to the same directory as it would have on your phone. CTRL+C exits.

markinct said:
So, do you have a tip jar?
Click to expand...
Click to collapse
Nope, but I'll take atinm's lead and suggest that you show thanks by signing up to be an organ donor!

Thanks a lot for your efforts and help, chui. I had to revert to Stable 7.1.0.1, hopefully that doesn't make a difference. Radio is KB5.
(Any flashing and permissions was done in recovery)
Recover to Stable 7.1.0.1, cleared cache, cleared dalvik, reboot
Flashed Ultimate Cleaning Script v4, flashed EB-Streamline, reboot
Flashed yagpsf, reboot, fixed permissions, reboot
Before Google Maps logcat (permission denied, dev/log/main is 0 bytes)
Open Google Maps
logcat post-Google Maps (again, permission denied for logcat)
Result: GPS icon/indicator works once. If I try to reload maps or turn my screen back on, the indicator no longer comes up. For some reason, logcat isn't being written into to it. The permissions for dev/log/main is rw-rw--w-.
Edit: I just tried alogcat, and it's giving an overwhelming amount of output. So I think it's because I don't know how to use logcat.
---------- Post added at 11:16 PM ---------- Previous post was at 10:51 PM ----------
Alright, got some logs, I'll be PM'ing you.

jsparakov said:
Thanks a lot for your efforts and help, chui. I had to revert to Stable 7.1.0.1, hopefully that doesn't make a difference. Radio is KB5.
(Any flashing and permissions was done in recovery)
Recover to Stable 7.1.0.1, cleared cache, cleared dalvik, reboot
Flashed Ultimate Cleaning Script v4, flashed EB-Streamline, reboot
Flashed yagpsf, reboot, fixed permissions, reboot
Before Google Maps logcat (permission denied, dev/log/main is 0 bytes)
Open Google Maps
logcat post-Google Maps (again, permission denied for logcat)
Result: GPS icon/indicator works once. If I try to reload maps or turn my screen back on, the indicator no longer comes up. For some reason, logcat isn't being written into to it. The permissions for dev/log/main is rw-rw--w-.
Edit: I just tried alogcat, and it's giving an overwhelming amount of output. So I think it's because I don't know how to use logcat.
---------- Post added at 11:16 PM ---------- Previous post was at 10:51 PM ----------
Alright, got some logs, I'll be PM'ing you.
Click to expand...
Click to collapse
I don't know if this helps but i'm not seeing any issues with KA7

kdf2883 said:
I don't know if this helps but i'm not seeing any issues with KA7
Click to expand...
Click to collapse
I've been using KA7 for the longest time now just before flashing it just for this. Yes, the problem persisted using BALI and Software GPS Fix v1.5.1.
In any case, I'll try KA7 again more methodically (KA7 + Clear Dalvik + Fix Permissions) and see if that allows the GPS indicator to work more than once per boot.
Out of curiosity, what's the date on the box/under-battery for your Vibrant? Mine is Jul/2010.

[Root] Replacing Superuser app with Super SU by CF

Super SU by CF
SuperSU is the Superuser access management tool of the future
Features include:
- Superuser access prompt
- Superuser access logging
- Superuser access notifications
- Per-app notification configuration
- Temporary unroot
- Deep process detection (no more unknowns)
- Works in recovery (no more segfaulting)
- Works when Android isn't properly booted
- Works with non-standard shell locations
- Trusts ADB connection
- Always runs in ghost mode
- Wake on prompt
The Pro version additionally offers:
- OTA survival mode (no guarantees)
- Full color-coded command content logging (input/output/error)
- Per-app logging configuration
- Per-app user override
- PIN protection
Who, What Why ? - said by CF
As you may know, I make a lot of apps that use or require root. I also release rooted kernels. I run into a lot of issues with existing Superuser tools. More importantly, a lot of my users run into these issues as well and then email me about it. So I decided to do something about this. Doesn't mean these were problems you have ever seen, or will ever see.
And thus, I have written - pretty much from scratch - SuperSU. I have taken the su binary command line parameter parsing from Superuser, to make sure that is compatible. Aside from that, it is completely rewritten, because how I wanted to do a number of things was incompatible with the existing codebase.
This is not a stab at ChainsDD, or his skills. He has done great work and will no doubt continue to do so, however, I felt the need for some of these changes, and thus made them. This is an early release, so I expect there will be some unforseen issues somewhere.
From now on, all CF-Root and Mobile ODIN Pro (EverRoot) releases will be built around SuperSU.
Please note that SuperSU is not hardened-security-tested or reviewed, and may be exploitable (... as may other solutions ...).
Install :
Flashable Zip v0.93
Market :
Lite
Pro
Note : Pro is key only, you need to install lite version first.
If you install from market, you will have two superuser, remove older one with system appl remover, or any other application can perform same job.
Remember, if you remove older first without installing newer one, you will lose Root n newer won't run.
One more thing market version will be regular application, so hard reset can delete it. So better install with flashable zip, to make it system application.
Source : http://forum.xda-developers.com/showthread.php?t=1538053

Thanks a lot doc. Gonna give it a try.
---------- Post added at 05:52 PM ---------- Previous post was at 05:50 PM ----------
Sorry to say but this belongs to General Section.

Nice one, Dr.Ketan.
Perhaps your fine installation instruction could also include this:
"Superuser (the old one) is a system app and should be removed from /system/app/ folder using Root Explorer, ES Eplorer with root permissions, or similar explorer app. Titanium Backup does not show Superuser in its app list, and therefore cannot remove it."
Otherwise you'll be swamped with Titanium questions.

This is modding
any thing android Mod, should be better place under development.
thogh let's leave it upon moderator..

dr.ketan said:
This is modding
any thing android Mod, should be better place under development.
thogh let's leave it upon moderator..
Click to expand...
Click to collapse
i think it doesnt work if USB debugging is enabled and if it is disabled then it works fine...

grgsiocl said:
i think it doesnt work if USB debugging is enabled and if it is disabled then it works fine...
Click to expand...
Click to collapse
CF says he has fixed that bug in v0.74, and that's the one posted here.

I have no issue with USB debugging ON

Confirmed working fine! Recommended to install via CWM. It will replace the other automatically so you don't have to manually remove it.
Sent from my GT-N7000 using XDA

kopitalk said:
Confirmed working fine! Recommended to install via CWM. It will replace the other automatically so you don't have to manually remove it.
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
Newbie question here, (sorry) so you don't just download from the market/play store..... open and it will install on it's own?
Sent From my Two Tin Cans & String Device on The Wookie Network

It will install, but not as system application. So it is recommended to flash with CWM. as well you have to remove old manually, if you install from market

dr.ketan said:
It will install, but not as system application. So it is recommended to flash with CWM. as well you have to remove old manually, if you install from market
Click to expand...
Click to collapse
Another newbie question... Is there enough of a difference between superuser & supersu for a newbie to risk mucking up their phone?
Thanks!
EDIT : are there instructions as to how to flash with CWM? SORRY!!
Sent From my Two Tin Cans & String Device on The Wookie Network

Superuser v0.75 has been released.
Changelog:
10.03.2012 - v0.75
- Adjustment to OTA survival (better!)
- Slight speedup in Settings
- Fixed native settings update after temp-re-root
- Clear data no longer clears PIN code
- Layout: Prompt: Grant and Deny switch positions (ICS style)
- Layout: AppDetail: Save and Cancel switched positions (ICS style)
- Layout: Added xlarge PIN layout
http://forum.xda-developers.com/attachment.php?attachmentid=940641&d=1331395344
P.S. Dr.Ketan, when I try to download CWM flashable zip from your 1st post I get a 404.

Ya b'coz link replaced by CF with new version
updated now

dr.ketan said:
Ya b'coz link replaced by CF with new version
updated now
Click to expand...
Click to collapse
even mobile Odin is updated with 2.25

Very Slow Boot Up Following Switch to SuperSU Pro
My Note is running rooted stock ROM with Franco.kernel v6. After installing the SuperSU v.75.zip with CWM and installing the Pro key, and removing Superuser.apk my Note is VERY slow to boot up. It took less than 1 minute immediately prior to SuperSU and now takes 5-6 minutes. It runs wifi and mobile data and sync together EVERY time it boots. It never did this before. It also runs "Media Scanning 6-8 times before it finishes booting.
I'm not complaining, just informing. I realize that this is a new work in progress as posted in the OP post #1. Is anyone else having these issues? If not, any suggestions to correct these problems? I have tried clearing Dalvik and cache partition through CWM app.
Thank you for any help and/or advice.
kraz

krazman325 said:
My Note is running rooted stock ROM with Franco.kernel v6. After installing the SuperSU v.75.zip with CWM and installing the Pro key, and removing Superuser.apk my Note is VERY slow to boot up. It took less than 1 minute immediately prior to SuperSU and now takes 5-6 minutes. It runs wifi and mobile data and sync together EVERY time it boots. It never did this before. It also runs "Media Scanning 6-8 times before it finishes booting.
I'm not complaining, just informing. I realize that this is a new work in progress as posted in the OP post #1. Is anyone else having these issues? If not, any suggestions to correct these problems? I have tried clearing Dalvik and cache partition through CWM app.
Thank you for any help and/or advice.
kraz
Click to expand...
Click to collapse
what you said was true...it slows up booting...but what i did was, in supersu app, i selected grant as default and there is no need for prompt...after that, booting as speed up!

I actually found my own solution as you were posting! Thanks for your help, grgsiocl!!! I did leave default access set to PROMPT though as it will only show the first time until i grant permission.
MY SOLUTION: I unchecked the show Notification Toasts, rebooted and total boot up took 50 seconds!
Sorry for wasting space in this thread!!! Hopefully, anyone else having similar trouble will see this.
kraz

Thanks Doc!flashing now

krazman325 said:
I actually found my own solution as you were posting! Thanks for your help, grgsiocl!!! I did leave default access set to PROMPT though as it will only show the first time until i grant permission.
MY SOLUTION: I unchecked the show Notification Toasts, rebooted and total boot up took 50 seconds!
Click to expand...
Click to collapse
Yeah, this is what CF has to say about it in his original thread:
Chainfire said:
PROTIP:
For extra performance, disable notifications. Logging does not impact performance much.
Click to expand...
Click to collapse

I think it would have been better to just link to chainfires thread rather than repost what he posted.

[FAQ] Support thread for EternityProject's CM 10.1! Questions? Post here!

Welcome to the support thread of EternityProject's CM10.1 (CM10.1 EPRJ)!
[ROM]EternityProject's CyanogenMod 10.1 for LG Optimus 4X HDhttp://forum.xda-developers.com/showthread.php?t=2123602​
What is this thread for:
Here you can report all your problems of the EternityProject's CM10.1 ROM that you have and ask for help to see if it's solvable by others methods that doesn't include posting to the original rom thread.
This thread will be easier for him than look for all reports spreaded in the many pages of his thread, but remember, avoid flood!
Before adding your problem(s):
- Be sure to use the latest version of CM10.1!
- Be sure that your report is not already reported by someone, so use the search button.
FAQ:
Q: I'm getting low scores on AnTuTu and Quadrant. What can I do?
A: Disable "Use GPU for 2d apps" under development settings.
Q: How can I open development settings?
A: In About Phone > Settings, press Build Number 8 times.
Let's help kholk and dexter build a stable CM10.1. Thank them!!
BUG LIST:
Confirmed
- Hotspot (doesn't work for both secured or open settings, wifi is stuck at OFF state after attempt to turn on hotspot, work again after reboot) (kholk)
- extsd (root permission is denied) (kholk)
- swipe gesture in aosp keyboard FC keyboard (BUT normal typing has no problem) (kholk)
- mic on Google Now FC the app (kholk)
-Phone doesn't automatically registers into mobile network on pin-locked simcard, I have to go into settings > mobile operators, perform manual search and choose corrent operator, then it works, after reboot i have to do same steps again. (o4i, musklor and Capozz)
- Bluetooth not really working (kholk)
- External SD is accessible only as root (kholk)
- I forgot to enable mass storage mode, so only adb is working. I'll enable it in the next release. (kholk)
- Hotspot can't still work because I didn't even configure it. I'll be sincere: I totally forgot to xD (kholk)
- Dear kholk, you forgot to include a library called libnvcap_video.so: why the hell did you? (kholk)
- installation of purchased apps from market fails (NEW)
Needs confirmation
- No option for USB connection mode (Mikey94)
- Camera no autofocus when hitting the trigger (Mikey94)
- Apps that try to install itselves to the sd card fail miserably, probably related to sdcard access. Some failing apps: Fancy widgets unlocker, ADWLauncher Ex, Exchange by TouchDown Key (ircalf)
- When connected to a wi-fi with no internet connection, mobile data doesn't take over, leaving the phone offline (ircalf)
Fixed
- Vibration (kholk)
- root doesn't work (kholk)
- NFC (the option is not present under settings) (kholk)
- Screen brightness changes inadvertently (still can't point out the reason or pattern) (ircalf)
- Leaving the brigthness to auto renders the screen very dark (ircalf)
TIPS:
- This build is still BETA. So you can, and probably will, find bugs. If so, please report here so I can update this thread and make Kholk's life easier.
- http://forum.xda-developers.com/showpost.php?p=37342594&postcount=79

- No NFC in settings (always activated??)
- No option for USB connection mode
- Camera no autofocus when hitting the trigger

all from kholk:
29/01/2013: Bluetooth not really working
29/01/2013: External SD is accessible only as root
- I forgot to enable mass storage mode, so only adb is working. I'll enable it in the next release.
- Hotspot can't still work because I didn't even configure it. I'll be sincere: I totally forgot to xD
- Dear kholk, you forgot to include a library called libnvcap_video.so: why the hell did you?

Re: [FAQ] Support thread for CM 10.1 by kholk! Questions? Post here!
Why no developer settings?
Sent from my LG-P880 using xda app-developers app

Question: Is it best to install this over a fresh kdz or will installing it over CustoNexus work just as well once cache/data/etc. are wiped in recovery?

Emin3ms said:
Why no developer settings?
Sent from my LG-P880 using xda app-developers app
Click to expand...
Click to collapse
From Dexter_nlb: "in about phone settings, press build number 8 times"
AlderCass said:
Question: Is it best to install this over a fresh kdz or will installing it over CustoNexus work just as well once cache/data/etc. are wiped in recovery?
Click to expand...
Click to collapse
Idk, I installed from my kdz.

For Kholk: 3G network does not work (provider Wind, Italy)

AW: [FAQ] Support thread for CM 10.1 by kholk! Questions? Post here!
I have a big Problem with mobile data and mobile connection!
My provider is three (3 Austria) and problem is following (same problem was also with dexters rom): the signal is kinda low, my phone automatically connect to t-mobile austria...and at the statusbar there is a "R" which stands for roaming, so there is no more internet connection!
With stock V10H i never had this problem!
Any solutions? am i the only person with this problem?
Sent from my LG-P880 using xda app-developers app

Anyone else having trouble reinstalling previously purchased apps? I get an error something along the lines of "cannot install to usb storage or SD card", and it only happens on my purchased apps, no problems installing any free apps. I Googled the error and none of the answers (of which there were a few) worked, such as clearing cache/data for the Google Play app, or installing the apps while the SD card is unmounted, another proposed solution is to delete smdl2tmp1.asec which I can't get at because I can't get root working yet
Speaking of root, superuser's info screen is reporting "note: your su binary cannot be updated due to its location"
Also, I've figured out how to add/remove lock screen widgets but I can't figure out how to get rid of the camera one? -edit- got rid of the lock screen camera with an app called Lockscreen Policy
SD card doesn't seem to be recognised at all (see attachment), tried unmounting and remounting, removing and reinserting, rebooting, no luck
Recovered CustoNexus for regular day's use tomorrow, will do some more "constructive breaking" of CM10.1 tomorrow evening.

AlderCass said:
Anyone else having trouble reinstalling previously purchased apps? I get an error something along the lines of "cannot install to usb storage or SD card", and it only happens on my purchased apps, no problems installing any free apps. I Googled the error and none of the answers (of which there were a few) worked, such as clearing cache/data for the Google Play app, or installing the apps while the SD card is unmounted, another proposed solution is to delete smdl2tmp1.asec which I can't get at because I can't get root working yet
Speaking of root, superuser's info screen is reporting "note: your su binary cannot be updated due to its location"
Also, I've figured out how to add/remove lock screen widgets but I can't figure out how to get rid of the camera one? -edit- got rid of the lock screen camera with an app called Lockscreen Policy
SD card doesn't seem to be recognised at all (see attachment), tried unmounting and remounting, removing and reinserting, rebooting, no luck
Recovered CustoNexus for regular day's use tomorrow, will do some more "constructive breaking" of CM10.1 tomorrow evening.
Click to expand...
Click to collapse
It's a known bug. We have to wait kholk's release a new build.

Another bug:
-Phone doesn't automatically registers into mobile network on pin-locked simcard, I have to go into settings > mobile operators, perform manual search and choose corrent operator, then it works, after reboot i have to do same steps again. (T-Mobile PL)

Re: [FAQ] Support thread for CM 10.1 by kholk! Questions? Post here!
The alarm clock just rang 2 timessage and softbrick the phone, needing to refresh kdz, then I noticed a huge battery drain from this issue.
Enviado desde mi LG-P880 usando Tapatalk 2

AW: [FAQ] Support thread for CM 10.1 by kholk! Questions? Post here!
AlderCass said:
Anyone else having trouble reinstalling previously purchased apps? I get an error something along the lines of "cannot install to usb storage or SD card", and it only happens on my purchased apps, no problems installing any free apps. I Googled the error and none of the answers (of which there were a few) worked, such as clearing cache/data for the Google Play app, or installing the apps while the SD card is unmounted, another proposed solution is to delete smdl2tmp1.asec which I can't get at because I can't get root working yet
Speaking of root, superuser's info screen is reporting "note: your su binary cannot be updated due to its location"
Also, I've figured out how to add/remove lock screen widgets but I can't figure out how to get rid of the camera one? -edit- got rid of the lock screen camera with an app called Lockscreen Policy
SD card doesn't seem to be recognised at all (see attachment), tried unmounting and remounting, removing and reinserting, rebooting, no luck
Recovered CustoNexus for regular day's use tomorrow, will do some more "constructive breaking" of CM10.1 tomorrow evening.
Click to expand...
Click to collapse
I had that problem about the smdl2tmp1.asec ony galaxy ace. I had no root and I could only delete it when I connected to the over and deleted it there! I don't know if you can connect to the over yet,but it helped me!
Sent from my LG-P880 using xda app-developers app

o4i said:
Another bug:
-Phone doesn't automatically registers into mobile network on pin-locked simcard, I have to go into settings > mobile operators, perform manual search and choose corrent operator, then it works, after reboot i have to do same steps again. (T-Mobile PL)
Click to expand...
Click to collapse
Same bug with Dexter's ROM

good job, will try this rom soon, still newbie at android.:victory:

o4i said:
Another bug:
-Phone doesn't automatically registers into mobile network on pin-locked simcard, I have to go into settings > mobile operators, perform manual search and choose corrent operator, then it works, after reboot i have to do same steps again. (T-Mobile PL)
Click to expand...
Click to collapse
Same problem here

Is it right that i have to enable WIFI for 3G Network?
Where can i find the Sync settings?

R: [FAQ] Support thread for CM 10.1 by kholk! Questions? Post here!
Battery is at 67% after 2 hours of use (it was fully charged after booting this morning)
Sent from my LG-P880 using xda app-developers app

- Apps that try to install itselves to the sd card fail miserably, probably related to sdcard access. Some failing apps: Fancy widgets unlocker, ADWLauncher Ex, Exchange by TouchDown Key
- When connected to a wi-fi with no internet connection, mobile data doesn't take over, leaving the phone offline
- Screen brightness changes inadvertently (still can't point out the reason or pattern)
- Leaving the brigthness to auto renders the screen very dark

ircalf said:
- Apps that try to install itselves to the sd card fail miserably, probably related to sdcard access. Some failing apps: Fancy widgets unlocker, ADWLauncher Ex, Exchange by TouchDown Key
- When connected to a wi-fi with no internet connection, mobile data doesn't take over, leaving the phone offline
- Screen brightness changes inadvertently (still can't point out the reason or pattern)
- Leaving the brigthness to auto renders the screen very dark
Click to expand...
Click to collapse
I think light sensor is bugged.

[ROM][LINK] Sailfish OS Droid 4 maserati

I DID NOT MAKE THIS ROM!!!!!! - A developer by the name of TheKit made this rom, so do not give me any credit for this rom, give it all to them.
I am simply linking it because I love this phone, I love Sailfish OS on it, and I think a lot of people would enjoy Sailfish OS on it as well and just don't know it is available.
Q: "What is Sailfish OS and why should I use it?"
A: Sailfish OS is a great OS for many reasons. Having used multiple android roms I can attest to the fact that:
1. It has MUCH better battery life (however it has a weird battery read bug, see issues below)
2. It is MUCH faster and generally more stable when it comes to the things that work (your calls won't drop, your system won't lock up due to lack of ram, etc.)
3. It has a great gesture driven UI that is a joy to use and very gorgeous to look at. No more of this all white bull**** Google has been forcing down our throats since 2014
Q: "How good is the battery life?
A: After a day of playing cave story at work and reading discord and listening to music, I am at about 30-40% end of day (I start at 8:30AM, stop at 4:00PM)
Okay now that the Q/A segment is over, lets get to the real meat
ISSUES
1. Battery Read is wonky, it only goes in 10% increments until it reaches 20%, then it starts going in 5% increments
2. If you use the 2.1.3.7 build keyboard backlight is broken, but it works fine on the 2.1.0.11 build
3. Bluetooth is wonky, I was able to play audio through speakers in the 2.1.3.7 build...
4. FM Radio is broken too
5. As the maemo-talk thread says, CDMA is untested, and like on Photon Q, most likely does not work. GSM works great though! :good:
6. The old 2.1.0.11 build has a slew of issues compared to the new 2.1.3.7 build. These include data not working out of box, wifi requiring a reboot to work, and auto rotation not working in a majority of apps by default. Consult this thread and the maemo talk thread for more help, and if you want rotation anywhere, install patchmanager 2.0 and auto rotate anywhere from warehouse for sailfish os.
Alien Dalvik install tutorial
I did not make this and do not know who did. the developer claims someone threw a brick at them with an sd card attached. The sdcard contained links to these files in the form of a text file names "monkeyAIDS.txt"
https://drive.google.com/file/d/1mS6di1jYfVeDoFBjcANS6SmfkhGyEKoa/view - AD Jolla C (different from the Turing phone rpm, this is built for 3.1.x kernels)
http://sfos.scanf.su/maserati/alien-patched.tar.gz
So extract both files to your ~/ (home) directory and type in the following:
devel-su
[insert root password you set in settings]
zypper in [alien dalvik rpm]
rsync -a /home/nemo/alien/ /opt/alien/
ln -s /vendor /opt/alien/system/vendor
reboot
OPTIONAL: fix for the default 320PPI value
devel-su
[insert root password]
vim /opt/alien/system/build.prop
change ro.sf.lcd.density to the value of your choosing (Droid 4 is 256)
Keyboard Backlight Fix, works on 2.1.0.11, don't know about 2.1.3.7 -- Thank you @moodroid for this legendary patch!
On <2.1.3.7, I got the keyboard backlight to work by creating an /etc/mce/20backlight.ini with:
[KeyPad]
BrightnessDirectory=/sys/class/leds/keyboard-backlight
Then do 'pkcon install mce' and 'systemctl restart mce'.
Download Links
Here is the thread with the Download Link to the 2.1.0.11 build
https://talk.maemo.org/showthread.php?t=99031&page=9
If you don't mind a lack of keyboard backlight and want a more up to date build, grab the new and fabulous leaked 2.1.3.7 Build:
https://drive.google.com/file/d/1k3MOCrMvbFb114Omf0MzSvnQ7wBkTiWH/view?usp=sharing
Basically if you are fed up with how ****ty the latest Lineage OS builds are and just want to try something new, give this a try. Why not? What have you got to lose. All in all great work by TheKit and I am very happy with the port as it is and I think you will be too.

Hi,
On <2.1.3.7, I got the keyboard backlight to work by creating an /etc/mce/20backlight.ini with:
[KeyPad]
BrightnessDirectory=/sys/class/leds/keyboard-backlight
Then doing 'pkcon install mce' and 'systemctl restart mce'.
Hope you get the OK to share your AD success!
Thanks

moodroid said:
Hi,
On 2.1.3.7, I got the keyboard backlight to work by creating an /etc/mce/20backlight.ini with:
[KeyPad]
BrightnessDirectory=/sys/class/leds/keyboard-backlight
Then doing 'pkcon install mce' and 'systemctl restart mce'.
Hope you get the OK to share your AD success!
Thanks
Click to expand...
Click to collapse
dude you are a legend!
I would add that to the OP but you are first comment so anyone viewing the op will see this. I will definitely tell TheKit about this (then again, he gave you the 2.1.3.7 build so you can just tell them yourself)

Greetings,
I've been playing around with SailfishOS on my Droid 4 in the past few days, and I have a few questions about the whole thing. TheKit publicly shared a 2.1.3.7 build for the Droid 4 on his thread at Maemo, is that the one you are talking about or is it a different build? As someone mentioned this specific build seems to have issues with wifi, and I have the same problem. I can't post links, but the download link to the build I mentioned is on page 12.
The 2.1.0.11 build seems to work fairly well, however I wasn't able to install Alien Dalvik. After the installation the "Android Support" button does show up in the settings app, however nothing happens when I click the start button. I also attempted installing an apk both via the GUI (by clicking on it in the downloads) and via the command line by using "apkd-install", but it doesn't seem to work. Full log of the installation process attached.

I talked with TheKit, and the 2.1.3.7 build I mentioned (the one at page 12) is indeed outdated. He just updated the OP at Maemo and added the latest 2.1.3.7 build, which I just flashed and it's working great. Also installed Alien Dalvik following the instructions in the OP and it seems to be working fine as well! However I wasn't successful with the backlight fix method yet.
For anyone wondering how I flashed the latest build I went CM11 --> SailfishOS 2.1.0.11 --> SailfishOS 2.1.3.7 (rel2).

NIKKOS said:
I talked with TheKit, and the 2.1.3.7 build I mentioned (the one at page 12) is indeed outdated. He just updated the OP at Maemo and added the latest 2.1.3.7 build, which I just flashed and it's working great. Also installed Alien Dalvik following the instructions in the OP and it seems to be working fine as well! However I wasn't successful with the backlight fix method yet.
For anyone wondering how I flashed the latest build I went CM11 --> SailfishOS 2.1.0.11 --> SailfishOS 2.1.3.7 (rel2).
Click to expand...
Click to collapse
Hi Nikkos,
Sorry - that was me that posted the backlight fix, and I agree that it doesn't work on 2.1.3.7-rel2. It'd worked on every other version I tried, and I've now edited my post above. Glad everything is working.
Sorry again

moodroid said:
Hi Nikkos,
Sorry - that was me that posted the backlight fix, and I agree that it doesn't work on 2.1.3.7-rel2. It'd worked on every other version I tried, and I've now edited my post above. Glad everything is working.
Sorry again
Click to expand...
Click to collapse
No worries.
If anyone is wondering how to change the SailfishOS UI scale (I find the default one to be way too big) here's how I did it via the terminal:
Code:
devel-su
rm /etc/dconf/db/vendor.d/locks/silica-configs.txt
dconf write /desktop/sailfish/silica/theme_pixel_ratio value
I believe the default value should be around 1.1; you can also reset the value to stock with:
Code:
dconf reset /desktop/sailfish/silica/theme_pixel_ratio
or read the value with:
Code:
dconf read /desktop/sailfish/silica/theme_pixel_ratio
Not exactly droid 4 related, but thought I'd share.

Okay, I got the backlight to turn on!
Type the following in the terminal:
Code:
devel-su
echo 255 >/sys/class/leds/keyboard-backlight/brightness
It seems to properly react to some triggers like standby after being turned on but not to others like sliding the keyboard in and out (which means it will always stay on if the screen is on, regardless if it's been slided in or out). My assumption is that the keyboard sliding trigger got broken in some way, as I believe that's the way the backlight is being turned on. The events which trigger the backlight seem to be stored in the file /sys/class/leds/keyboard-backlight/trigger, so I assume that would be a good starting point to attempt fixing this.
The keyboard backlight intensity can also be changed, just change the 255 to a different value (it goes from 0 to 255).
Note: this change is not permanent, it will need to be applied again at reboot. Writing a script which executes the above commands at boot should be trivial though, and I will include instructions when I get it done myself.
EDIT:
Here's how to make the change permanent. Following these instructions you will create a Systemd service which will turn the backlight on when active and off when inactive; it will automatically run at boot and it can also be controlled like any other Systemd service (i.e. using systemctl via the terminal)
Type the following commands through the terminal:
Code:
devel-su
cd /etc/systemd/system
touch keyboard-backlight.service
chmod 744 keyboard-backlight.service
You will now need to edit the keyboard-backlight.service file with a text editor (either vim or nano will do, vim comes preinstalled, nano does not). Depending on your preferred text editor, type the following:
Code:
vim keyboard-backlight.service
or
Code:
nano keyboard-backlight.service
Now write the following to the file and save it:
Code:
[Unit]
Description=XT894 keyboard backlight service
[Service]
Type=oneshot
ExecStart=/bin/sh -c "echo 255 >/sys/class/leds/keyboard-backlight/brightness"
ExecStop=/bin/sh -c "echo 0 >/sys/class/leds/keyboard-backlight/brightness"
RemainAfterExit=yes
[Install]
WantedBy=multi-user.target
Now type the following to enable the service:
Code:
systemctl enable keyboard-backlight.service
That's it. You can now control the service by using the following:
Code:
systemctl start keyboard-backlight //This will turn the backlight on
systemctl stop keyboard-backlight //This will turn the backlight off
systemctl status keyboard-backlight //This will display the service status

Can anyone share the google drive file from the first post? Is there an alternative link available? Or could you PM me a google drive link? Thanks!

Can anyone suggest the best/correct ROM-slot size for TWRP?
Is it still like for CM/LOS:
800MB for system
10MB for cache
and rest for data as one likes?

[ROM][TMOBILE][S7_SM-G930T][Oreo 8.0 Rooted][WifiCalling]

Updated version of this ROM: [ROM][TMOBILE][S7_SM-G930T][Oreo 8.0 Rooted][WifiCalling]G930TUVU4CRI2
ROM last updated: 10/30/2018
Introduction:
HUGE thanks to the guys that got this going like root & figuring out hybrid stocks! This ROM is a complete rewrite of my ROM [ROM][TMOBILE][S7_SM-G930T][Oreo Rooted] That ROM doesnt have WifiCalling & I couldn't get it to work for the life of me, so I rewrote it. I started with stock, and slowly stepped back making changes, reinstalling each time, confirming it still worked. About 200 installs later & 1000s of changes, this is the result. Yes, it took a LONG time. Hope you enjoy it! Don't forget to say Thanks so I know it is actually helpful to others, and continue doing this!
Description:
Stock Tmobile Oreo 8.0 modified (G930TUVU4CRF1)
EXTREMELY debloated! Nearly bare minimum, while still retaining hardware functionality. Eg, Samsung Gallery & Camera exist so we get 4k recording, and there aren't errors when we pull up the Gallery to edit, etc. Yes, this means NO Samsung or Android Pay. There could be more apps to debloat but Im out of time for now! (Please provide suggestions if interested)
Everything possible I replace Samsung with Google
Solid ROM. It was actually kind of slow for me, but I'm curious how this works for others.
Xposed is part of the guide, which will give you infinite customization & tweak-ability
If you hate Samsung SW and just want a solid working ROM with very few install options to get you up and running this is for you.
This will delete all of your data on the phone! (Not external SD card) This is the only way so don't ask. Backup your data!
Features:
Tmobile Wifi Calling works, along with Visual Voicemail & Mobile Hotspot
Many Aroma Installer app options
(Optional) KevinsFavorites option in Aroma. I'm not sure I'd recommend it due to my tastes. If you're looking for some good common apps tho, it includes: Amazon, AmazonMusic, AquaMail, Gmail, GoogleDrive, GoogleKeep, GooglePhoto, Hangouts, IFTTT, Pandora, RootBrowserClassic, TitaniumBackup, Uber, & Wink (If you install these and want to remove them later, use TitaniumBackup (or similiar) to uninstall
Root Features: See Downloads->Recommended Root Zip & say Thanks!
Debloated
De-Knoxed
Decrypted /data/ partition
OTAs disabled
Speed & Build Prop Tweaks
Dual speaker
Ruthless Launcher
Apps
AdAway
AOD Clock Face Themes
CPUSpy
DisableService
Kernel Adiutor
Samsung Video Editor and Trimmer
Xposed
Many more...
Download Links:
Base.7z & Oreo_Kevin71246Modded_v3.#.#.zip
Installation:
This will delete all of your data! If you continue, you acknowledge that the Author is NOT responsible for anything that happens to your phone!
Summary (for Pros)
Flash Oreo stock
Root
Flashfire
Oreo_Kevin71246Modded_v3.1.##, Auto-mount, Mount /system read/write Option
Go through Aroma setup. When finished, it should boot to Recovery (if not do this). Do a "Wipe data/factory reset"->Reboot
Detailed Steps
Install Stock Oreo:
Download mode & Setup
Make sure you have latest device drivers setup on your PC
Enable USB Debugging on phone in Developer Settings
Boot phone into Download Mode:
Turn off your device
Press and hold Volume Down + Home + Power button
When you see the warning screen, release buttons & press Vol UP. Phone should say "Downloading..."
Download and unzip Base.7z to PC (This contains stock Oreo, ODIN, & root)
ODIN
Open ODIN on PC (\Base\Odin_313.exe)
Connect USB from PC to phone. ID:COM in Odin should turn Blue with a COM port
Select AP, BL, CP and CSC files from the \Oreo_Stock\Base\ folder for corresponding files
Select HERO2QLTE_USA_VZW.pit
Select Start
Finished: Phone will reboot & show Carrier screen for 3-5mins. Wait until Setup screen & go through quickly (bare minimum) since you'll wipe it again. Once in Android, go to Settings->Display->Screen resolution->WQHD->Apply
Root Instructions: (+Flashfire, SuperSU)
Reboot phone into Download mode
Odin
AP: Select \Base\Root\AP_SM_G930_OREO_ENG_BOOT.tar
Start-> Wait for phone to boot to Android OS
Root
Double-click \Base\Root\cmd-here.exe & Type: root.bat [enter]
Option: 1 (Install Root No tweaks) (Or pick whatever you want)
*Note: With this system root, do not update su binary. Disable notifications for SuperSU app. Don't flash any superuser zips in recovery that are not made by jrkruse
Install Custom Hybrid ROM & Xposed
Download & copy Oreo_Kevin71246Modded_v##.zip to phone
Flashfire
Open Flashfire on phone
Red + symbol->Flash Zip or OTA->Oreo_Kevin71246Modded_v#, Auto-mount, Mount /system read/write Option->Check mark
Click Lighting bolt at bottom-> OK
Phone will reboot to Aroma. Go through setup. (See above for what's in KevinsFavorites)
When finished, allow Aroma to exit.
It should reboot into Recovery (If not, do this: immediately hold Vol-Up btn+Home btn until you see recovery on screen. If you missed it, try again: hold Vol-Down+Pwr btn ~10sec until phone restarts & immediately hold Vol-Up btn+Home btn until you see recovery on screen.)
In recovery: Factory Reset->Yes->Restart phone
*Wait 5-10min on loading screens
Go thru Android setup. Ignore "Xposed Installer has stopped" error
Followup-Steps:
Set Dialer: Phone Settings->Apps->Menu->Default Apps->Calling App->Select Phone
Recommendations:
Xposed
Setup Xposed: Xposed Installer app:Install framework option & restart phone
Xposed Installer app: Settings button (3 lines)->Download->Search "GravityBox [O]"->Click it->Versions tab->Download->Install->Back arrow (upper left)->Settings->Modules->Check box next to GravityBox [O]->Restart phone
GravityBox [O] Tweaks: (Open GravityBox app)
Battery indicator: Statusbar tweaks->Battery settings->Turn on Master switch->Battery indicatory style: None->Battery percent text...->Back
Clock: Statusbar tweaks->Clock settings->Turn on Master switch->Center clock...
Firefds Kit [O] Tweaks: (Install same way as Gravity box)
This is a supplement to Gravitybox. Things of note: Advanced power menu, call recording, & disable bluetooth toggle popup, etc
Known Issues:
Visual Voicemail may fail to register, but restart phone and give it a few hours. It works eventually.
RCS (Rich Communication Services/AdvancedMessages/Chat) texts don't show up in Android Messages & Textra, etc apps (This is an issue on stock as well!!)
Fix: (Use Samsung Messages)
How to Install Samsung Messages via ADB (Easiest way though is just reinstall!):
Download Messaging_SEP81.zip, unzip, & manually copy apk to phone via usb/Windows My Computer
adb shell (Get into shell to run beow commands)
su (Run as root)
mount -o rw,remount /system (Mount system read/write since default it read-only)
chmod 755 /system/priv-app/Messaging_SEP81 (Set permissions on folder)
chmod -R 644 /system/priv-app/Messaging_SEP81 (Set permissions on apk file)
ls -l /system/priv-app/Messaging_SEP81 (Check permissions - Should be: -rw-r--r-- 1 root root - not sure what 1 & 2 is)
ls -l /system/priv-app | grep "Messaging" (Check permissions - Should be: drwxr-xr-x 2 root root)
reboot (Reboot device)
Changelog:
Version 3.1.32: First stable build
Ver 3.1.36:
-Disabled encryption on /data/ partition to resolve "Bluetooth paired devices deleted after reboot" issue & so mods play nicer with ROM
-Fixed "Device not supported" error on Google Phone app
Ver 3.1.37:
-Added most of the apps I replaced or added as options in Aroma Installer now
Credits:
- @jrkruse & @klabit87 for Root
- @partcyborg for helping jrkruse
- @jrkruse for his similar ROMs as guides & help
- @Lanc-City for assistance in ROM modding
- @gustco for eng boot.img
- @Raymonf for modified odin
- @amarullz for Aroma Installer
- @Chainfire for FlashFire & SuperSU
- @rovo89 for Xposed
- @JaeKar99 for the cool & colorful boot animation
- @mrRobinson for AdAway ADAway.org
- Brandon Valosek for CPUSpy
- WangQi for DisableService
- Willi Ye for Kernel Adiutor
- @shubby for Ruthless Launcher
- @Craz Basics for Dual Speaker Mod
...
- Please PM me if you were forgotten!

Some screenies:

Saved2

Saved3

Well nice job!

jrkruse said:
Well nice job!
Click to expand...
Click to collapse
...but your'e the best! (You & I both know I couldnt have done it without all your other work!)
Once I FINALLY got WifiCalling to work, I thought... Imagine ALL the S7 XDA members out there with crappy Tmobile signal across Rural America that could TOTALLY use Wifi Calling!!! Haha, but seriously!! & that thought was the birth of this thread

kevin71246 said:
...but your'e the best! (You & I both know I couldnt have done it without all your other work!)
Once I FINALLY got WifiCalling to work, I thought... Imagine ALL the S7 XDA members out there with crappy Tmobile signal across Rural America that could TOTALLY use Wifi Calling!!! Haha, but seriously!! & that thought was the birth of this thread
Click to expand...
Click to collapse
Is this Ufirm firmware?

jrkruse said:
Is this Ufirm firmware?
Click to expand...
Click to collapse
I have so many FW packages on my PC at this point, from so many places that I used while trying to get this to work, but I think it might be a package from one of your threads(?) Since I'm not exactly sure what you're asking regarding "Ufirm FW", I'll elaborate hoping that answers your question. (Tho I'm thinking you mean the U variation/unlocked. So based on these stock files below I guess the answer is no.) If you're question is really, "is it possible to get tmobile wifi calling to work on a U model #", then I'd have to really think about that. But at this point I don't have an answer. I can tell you a million dependencies about it tho! (I seriously have hundreds of revisions I made while testing, & notes. The symbolic & meta links in Aroma initially broke it, as I found out after a week or so of testing - wish I knew a bit more about them, and why they're all there, then I'd know what was wrong about them...)
High-level process:
1)Flash Base/Stock/Oreo Rom:
- AP_G930TUVU4CRF1.tar
- BL_G930TUVU4CRF1.tar
- CP_G930TUVU4CRF1.tar
- CSC_TMB_G930TTMB4CRF1.tar
- HEROQLTE_USA_VZW.pit
2)Root with your method
3)Flash Xposed framework & my ROM (it's a "start with stock then remove what we don't want" type of Aroma/Edify script)

jrkruse said:
Is this Ufirm firmware?
Click to expand...
Click to collapse
BTW, any idea how to prevent the "verification failed" error I mention in the OP steps, after flashing Xposed framework? I tried flashing dm-noverity but no luck. At least my guide covers it at this point tho... Thanks again

kevin71246 said:
BTW, any idea how to prevent the "verification failed" error I mention in the OP steps, after flashing Xposed framework? I tried flashing dm-noverity but no luck. At least my guide covers it at this point tho... Thanks again
Click to expand...
Click to collapse
If you choose the keep safestrap option during root the it will flash the system/vendor/etc/ fstab.qcom that totally removes data encryption but when that fstab.qcom is flashed it also requires a data wipe for phone to boot then when you install xposed you won’t see that error but either way you end up wiping data so your choice
Sent using some kind of device I modified

It works perfectly!!
I have not had any problems so far, here I leave you for the link to download and try those who are interested in VIPER4ANDROID: https://drive.google.com/file/d/1572ORe6TOrsRBuxWWBChH-WMnxkvcUjH/view?usp=drivesdk
You just have to flash it with Flashfire, but if you do not pull them, let me know Thank you very much !!! Kevin for the effort!
---------- Post added at 10:17 PM ---------- Previous post was at 10:15 PM ----------
I have not had any problems so far, here I leave you for the link to download and try those who are interested in VIPER4ANDROID: https://drive.google.com/file/d/1572ORe6TOrsRBuxWWBChH-WMnxkvcUjH/view?usp=drivesdk
You just have to flash it with Flashfire, but if you do not pull them, let me know Thank you very much !!! Kevin for the effort!

First, I want to thank you so much kevin71246. I tried your previous version as I was sick and tired of how sluggish my phone felt after the last two T-Mobile OTA updates. So far the experience on the phone has been great but I wanted to post about an issue I had with that version to see if anyone else has come across it or can figure out what is going on. The reason I am making this a reply in this thread instead of your other is because I will be flashing this update shortly but I want to get the ball rolling on the issue first.
I went through the whole process, installing the minimum with Google Apps, though I did restore everything previously installed once I log in with my Goggle Account. I am unsure if this contributed to the problem but I will not be restoring apps on the next try. It seems no matter what process I attempt to connect my Ticwatch E to my S7 the Wear OS app will not recognize it which causes the watch to get stuck in the setup phase, making it useless. This was after multiple and different connection attempts, resets, reboots and factory (watch only) restores. The watch will show up under bluetooth and create the initial connection but it will not stay connected. Anyone have any idea? Is this ROM missing something?
Edit: Mid way through the install, I wanted to note that I checked for the issue after doing the "Install Stock Oreo" but before Root and everything worked as it should. Wear OS sees the watch instantly and Bluetooth connects fine.
Edit: So I am a day into using the ROM and I am still having issues. While it will connect and work perfectly fine now, when ever I do a reboot of the phone the watch no longer connects. I will just get constant Bluetooth Connection Requests, every single time the watch tries to get data, and it never actually connects. To fix this I need to do a complete reset of the watch and do the whole setup process again. As you can imagine this is no good, expecting to wipe my watch every time my phone reboots makes it still almost useless.

charredchar said:
First, I want to thank you so much kevin71246. I tried your previous version as I was sick and tired of how sluggish my phone felt after the last two T-Mobile OTA updates. So far the experience on the phone has been great but I wanted to post about an issue I had with that version to see if anyone else has come across it or can figure out what is going on. The reason I am making this a reply in this thread instead of your other is because I will be flashing this update shortly but I want to get the ball rolling on the issue first.
I went through the whole process, installing the minimum with Google Apps, though I did restore everything previously installed once I log in with my Goggle Account. I am unsure if this contributed to the problem but I will not be restoring apps on the next try. It seems no matter what process I attempt to connect my Ticwatch E to my S7 the Wear OS app will not recognize it which causes the watch to get stuck in the setup phase, making it useless. This was after multiple and different connection attempts, resets, reboots and factory (watch only) restores. The watch will show up under bluetooth and create the initial connection but it will not stay connected. Anyone have any idea? Is this ROM missing something?
Edit: Mid way through the install, I wanted to note that I checked for the issue after doing the "Install Stock Oreo" but before Root and everything worked as it should. Wear OS sees the watch instantly and Bluetooth connects fine.
Edit: So I am a day into using the ROM and I am still having issues. While it will connect and work perfectly fine now, when ever I do a reboot of the phone the watch no longer connects. I will just get constant Bluetooth Connection Requests, every single time the watch tries to get data, and it never actually connects. To fix this I need to do a complete reset of the watch and do the whole setup process again. As you can imagine this is no good, expecting to wipe my watch every time my phone reboots makes it still almost useless.
Click to expand...
Click to collapse
I believe I know what the issue is, I'm testing a fix (for THIS ROM) as we speak. Stay tuned. Maybe tomorrow if I have time and it works I'll update the OP. BTW, this ROM and my other ROM are TOTALLY different. Thanks for the feedback!

FranMLG said:
I have not had any problems so far, here I leave you for the link to download and try those who are interested in VIPER4ANDROID: https://drive.google.com/file/d/1572ORe6TOrsRBuxWWBChH-WMnxkvcUjH/view?usp=drivesdk
You just have to flash it with Flashfire, but if you do not pull them, let me know Thank you very much !!! Kevin for the effort!
Click to expand...
Click to collapse
What do you mean by this? "but if you do not pull them, let me know"
And tell me more about Viper4Android, and if it works solid for you on this ROM...then I'll consider adding it. Thanks!

New version, see change log in OP for details.

Yeah i.a give this a shot in a little. Do I need to root phone or can I just flash through Odin. Sorry not used to this locked bootloader crap..... s8crj1 are the last 6 digits of the software I'm on. I did receive the latest update will this effect me installing this. Sorry as I said not used to this locked bootloader crap.

jrkruse said:
If you choose the keep safestrap option during root the it will flash the system/vendor/etc/ fstab.qcom that totally removes data encryption but when that fstab.qcom is flashed it also requires a data wipe for phone to boot then when you install xposed you won’t see that error but either way you end up wiping data so your choice
Sent using some kind of device I modified
Click to expand...
Click to collapse
Hi, why you have to flash this - HEROQLTE_USA_VZW.pit on 930t, is it ROM specified? if I do and don't then what are pro and cons?
---------- Post added at 01:36 PM ---------- Previous post was at 01:26 PM ----------
josh2020glacier said:
Yeah i.a give this a shot in a little. Do I need to root phone or can I just flash through Odin. Sorry not used to this locked bootloader crap..... s8crj1 are the last 6 digits of the software I'm on. I did receive the latest update will this effect me installing this. Sorry as I said not used to this locked bootloader crap.
Click to expand...
Click to collapse
since bootloader is locked you can't use TWRP so you have to use Flashfire to install this ROM, as you know flashfire required root so you have to setup the base per OP and then root the base then install the ROM and then root it again, read the first page I don't think you will get a instructions more detailed then his

Okay so I just realised I was posting comments on the old thread, my bad. Coming back to the question, can the boot animation be changed? I've messed with the qmg files in an attempt to replace the weird, nauseating rainbow animation but even after overwriting the latter, it persists. Looking forward to a reply kek

Alkan3 said:
Okay so I just realised I was posting comments on the old thread, my bad. Coming back to the question, can the boot animation be changed? I've messed with the qmg files in an attempt to replace the weird, nauseating rainbow animation but even after overwriting the latter, it persists. Looking forward to a reply kek
Click to expand...
Click to collapse
Nauseating rainbow? LOL. Sorry. This is much more of a general question though, that wouldn't exactly pertain to this ROM specifically. And given I don't have an answer, I'd try searching BootAnimation How-Tos to get this customized. The ONLY thing I did regarding this was replaced the existing files with the rainbow ones. That's it. Apologies in advance.

Just discovered an issue: RCS (Rich Communication Services / Chat) texts don't show up in Android Messages app. See "Known Issues" in OP for a solution. BTW I posted a new ROM version a few days back that allows many choices in Aroma Installer. Make sure to pick Samsung Messages (instead of Google), so you get RCS chat text messages!