Hopefully someone a bit more educated than me can help me sort something out. My S4 is rooted and running the latest version of Safestrap since I was dumb enough to take the ME7 update. I also own a 2013 Ram Sport with the UConnect RA3 radio, which I have just updated to the most recent software version.
Prior to the update of the UConnect system, the text messaging features wouldn't work for me, even on my stock ROM. After the update, all of the messaging features worked with stock and while running Hyperdrive 9.1.
I just flashed GoogleEdition 6.0 last night along with the ME7 modules zip necessary for safestrap. Everything is pairing with my UConnect system, except for some reason the messaging function stays grayed out (like it did before I updated the Radio). Am I incorrect in my assumption that all of the bluetooth drivers are identical since I'm running the same Kernel and I flashed the modules zip? Could it be just because the Radio "thinks" its connected to a play store S4, which at the moment isn't fully compatible? Can I "trick" the radio into thinking its a stock Verizon S4?
Any input or suggestions would be very much appreciated. The messaging features are great and I was thrilled to have them working in the truck, and GE 6.0 is something I really want to keep running, so I really want to get it figured out. Thanks!
One bump hoping someone can possibly chime in with SOMETHING that might explain what would cause this to occur.
Sent from my GT-I9505G using Tapatalk
i get strange errors with google edition rom ports and safestrap. id suggest to get a 4.2.2 touch wiz rom.
It's working fine for me honestly...I wouldn't call it an error. It almost seems like if touchwiz isn't on there, the UConnect system thinks it's a different phone. I just don't know if it's getting that info from the drivers, or maybe the build.prop. It pairs and all the features work except for the messaging through the truck.
Sent from my GT-I9505G using Tapatalk
Related
Currently I'm running stock (but rooted) 2.11.605.9 getting great battery life and performance. I don't have any problems besides the fact that BT Phone Book Access Profile (BT PBAP) doesn't work with my car.
The only reason I'm considering moving away from stock is to get working BT PBAP.
When I originally tried the FactoryROM based on the open mobile leak, its BT PBAP worked fine with my car kit, but that was before the MMS fix, and some other things had been tweaked, so I went back to stock.
Now there is also the Thunderstick rom, with more tweaks and customizations.
Is one better than another? Is one more stable than the other for daily use for someone who relies heavily on their phone and needs it working? Are there any other ROMs based on the Open Mobile leak that have been tweaked for Verizon?
been running thunderstick for a while now. It's mostly stock with bloat removed and a bunch of tweaks to make the phone better. it also has a custom kernel with speed tweaks and governors.
I'm a couple versions back as it's been rock solid enough to not need to update. You can try both out to see what you like. You aren't stuck with the first one you pick. And only you can decide what's best for you.
Thanks.
I tried Thunderstick, but unfortunately, I still can't get Verizon's visual voice mail (yes I pay for it) working
KidJoe said:
Thanks.
I tried Thunderstick, but unfortunately, I still can't get Verizon's visual voice mail (yes I pay for it) working
Click to expand...
Click to collapse
Did you ever get Verizon Visual VM to work with Thunderstick? I just flashed to it yesterday
rachbu said:
Did you ever get Verizon Visual VM to work with Thunderstick? I just flashed to it yesterday
Click to expand...
Click to collapse
No. And I gave up. I'm back to stock.
Please let me know if you get it working
rachbu said:
Did you ever get Verizon Visual VM to work with Thunderstick? I just flashed to it yesterday
Click to expand...
Click to collapse
I just tried again...
See -> http://forum.xda-developers.com/showthread.php?t=953746&page=3
Edit the two lines in the build.prop, reboot, and see post #46 of that thread for the APK to install (or download from -> https://play.google.com/store/apps/...SwxLDEsImNvbS52encudnZtLmFuZHJvaWRjbGllbnQiXQ.. ), and it worked to log in, download and play back voice mails.
I broke my wifi tether. I am rooted STOCK via Adams Suck it Verizon program, I installed the record call mods and the ultra cool light saber sounds for my s pen. I added Wifi toggle button and the shutter sound option and black background thru csc menu. Tether was working used it to stream netflix on the PSC for about 4 episodes of Twilight Zone. ALL good so far. After I added the new custom Perseus kernal it stopped working.
No brainer right? must be a problem in the kernel that isnt addressed yet. Still got to love the great work from our Devs and not the end of the world. I created a stock Kernel from Adams Revision3 rom that I had already downloaded and put it in thru recovery.
Still no WIFI tether. Now I'm stuck my "no brainer" just became "oh eff." Anyone have ideas on what else may need to be done? Or what I might have done unintentionally. I can reboot to stock and start tweaking all over but I really didnt want to and please dont comment on the fact that I'm too much of an idiot to have made a back up before I lost the tether.:crying::crying:
I'm still interested in any ideas but I wont be able to implement the fixes anyway to try. Gave up and Reinstalled the rooted stock rom complete already.
ficjay said:
I'm still interested in any ideas but I wont be able to implement the fixes anyway to try. Gave up and Reinstalled the rooted stock rom complete already.
Click to expand...
Click to collapse
Hmmm dude idk you should have backed up but you know that. You may have to go back to stock. Have you tried a third party app?
Sent from my SCH-I605 using Tapatalk 2
First of all, I'd like to say I'm glad to be on this extremely helpful forum with very intelligent members. I have been watching this forum for at least 2 years now to get up to speed on rooting and not being a noob so much. I have successfully rooted, troubleshooted, restored to stock, rerooted and added custom roms on my GSM/HSPA+ Galaxy Nexus from Google Play due to help on these forums and elsewhere and I am very grateful. Because I am new, I was not able to post this question in the forum I wish to, which I have mentioned below, until I reach 10 posts, so please do bare with me.
I have been on Android 4.1.2 due to a sound tweak rom by the name of Nexus LouderBoom.zip which installs the AwesomeBEATS sound equalizer enhancement to the ridiculously low volume of the Galaxy Nexus. I never updated to 4.2.2 for fear that it wouldn't work and also because the upgrades for that particular OS version weren't that necessary to me.
However, I did happen to stumble upon ...Awesome...'s thread on AwesomeBEATS™ v.5 and perused it's pages to see that many people are having success with it as it has now been to designed to work with pretty much any Android Jelly Bean operating system. So I decided to give it a go and update to 4.2.2 via OTA. Prior to the OTA update, I made sure I did a back up through Nexus Toolkit 1.6.3 as well as make a Nandroid backup via TWRP Custom Recovery.
The update went well and everything worked normally. I then applied the AwesomeBEATS v.5 rom via the recovery console and installed it. It had the option under the Sound Settings like it's supposed to. I then began customizing my sound preferences for Headset, Speaker and Bluetooth for which I momentarily noticed a sound change when manually adjusting the equalization in the "Speaker" while playing a song via Google Music. However, after switching to Bluetooth, the adjustments no longer registered and it seemed to bypass the fact that the tweak was installed on the phone. Even after turning off Bluetooth and going back to Speaker, it just didn't work anymore. I even tried to flash an older version (v.4) to no avail as it made the streaming from Google Music quit entirely. Because of this incompatibility, I had to revert back to my previous version 4.1.2 where I was able to utilize the Nexus LouderBoom.zip tweak which worked beautifully.
Looking back on why v.5 didn't work for me, I can only stop at this line in the instructions...
"*STOCK Rom (ROOTED but on stock rom. (ONLY SOUND FILES WILL INSTALL)"
Is the fact that the ONLY the sound files will install part of my problem? Or is there some other technicality I missed along the way?
Thank you so much for anyone who responds... or not.
GPS doesn't work on any KitKat ROMs that I've flashed, but works fine on 4.3 stock, viper, Y18 and sense 5.5.
I feel like I must be the only one who had this issue because nobody else seems to be complaining about it.
At the same time it seems like since I've had this problem on every single one of the 15+ KitKat ROMs, that its got to be happening to others too.
Ideas?
New partitions, fire water s-off, 2.10.0000 HBOOT, running TWRP 2.7.0.8b.
Sent from my EVO using telepathic awesomeness
Seemed to be a fairly common issue with AOSP. Make a backup of your current setup. Flash back to a Sense ROM, turn GPS on and get a good lock. Once you've done this, leave GPS on and restore your AOSP ROM. Furthermore, you can also use an app like GPS Status to clear your A-GPS data. See if any of that helps. I haven't used any AOSP ROM's on the new partition setup but the fix I listed seemed to have worked for quite a few folks on the old setup running various AOSP ROM's.
Sent from my HTC device
Makes no sense to me whatsoever, but it worked! Thanks!
Sent from my EVO using telepathic awesomeness
Magnum_Enforcer said:
Seemed to be a fairly common issue with AOSP. Make a backup of your current setup. Flash back to a Sense ROM, turn GPS on and get a good lock. Once you've done this, leave GPS on and restore your AOSP ROM. Furthermore, you can also use an app like GPS Status to clear your A-GPS data. See if any of that helps. I haven't used any AOSP ROM's on the new partition setup but the fix I listed seemed to have worked for quite a few folks on the old setup running various AOSP ROM's.
Sent from my HTC device
Click to expand...
Click to collapse
YUP! Whenever I get a complaint about GPS on any AOSP roms I suggest the Sense Lock trick. It will work for some time afterward but sooner or later you will need to do it again. I can confirm this works on the new partition format AOSP roms. At least the ones I work on.
Ya I know, this may seem like a stupid question, but believe me I have valid reasons for asking it. So I have a Galaxy Tab 10.1 WiFi (GT-P7510) that had been sitting around not being used for quite some time. I decided to recently take it out and root it to run the snapprefs xposed module alongside snapchat. Well, first things first, the tablet was running Android 3.0 Honeycomb which is way out of date. I upgraded to the last update available for this tablet which was Android 4.0.4 ICS. through standard system update. I then rooted using CWM recovery and flashing over superuser. All worked well and the tablet was rooted. I installed the latest version of snapchat from the play store and attempted to login with ABSOLUTELY 100% VALID credentials. It went through the processes "logging in, verifying device, etc." and then crashed to the home screen. I tried uninstalling, reinstalling, signing up for new accounts, switching google accounts on the device, creating new google accounts, making sure google accounts were syncing correctly, making sure time and date was correct, downgrading snapchat to older versions, EVERYTHING. Absolutely nothing worked. The funny thing is that when initially opening snapchat, it would have the main screen where you see your camera open and have snap/stories notifications, etc. Then it would finish loading and go to the login/signup screen (since no account was logged in). That was when the problems would occur. I'm even able to sign up for new snapchat accounts which would go through just fine (I would receive the email notification from team snapchat), but when it was time to go to the main snapchat screen it would crash the same way as when logging in. At this point I was convinced that snapchat simply had issues running on 4.0.4 or something. I decided to flash a custom ROM to solve this. The first ROM I flashed was Nameless 4.4.4 .. Again, EXACT same issues. I was like wtf?? I then flashed Omni 4.4.4 and yep, same exact issue. I then tried CM 10.1 (4.2.2) and again, same issues. I went back to completely stock ICS 4.0.4 using Odin and ya, same issues as the first time. I really don't understand at this point. I thought it could be snapchat account issues so I tried logging in and logging out with all accounts that I attempted on the tablet using my Galaxy S6 Active which worked completely fine, so it's definitely something with the device. I'm someone that can typically figure out things for myself through researching, but at this point I'm really stuck, and I had to join this forum for assistance. If anyone would be able to help, I would GREATLY appreciate it. Does anyone have a Galaxy Tab 10.1 WiFi (GT-P7510) that they are currently running snapchat on? This is the original 10.1, and not the 2 or 3, and so on. Would anyone know what could possibly be going on? I wouldn't think that it would take much to run an app like snapchat, and I would think that the Tab 10.1's hardware would certainly be more than capable of doing so. The latest version of snapchat requires 4.0 and up, so I wouldn't think the android versions that I used would be an issue. Even the stock ICS 4.0.4 should be able to run it just fine. CM 10.1 was 4.2.2 and the other 2 ROMs that I tried were Omni 4.4.4 and Nameless 4.4.4.
I look forward to any help that can be provided. Thanks ahead of time everyone.
Got any solutions?