Related
I'm currently on v0.4 of Naven's Atrix port and can't seem to get Bluetooth to fire up. I don't remember having this problem with older versions of this ROM.
Using both the widget control and the prompt in Settings, Bluetooth tries to turn on and ultimately, fails.
I found these potential fixes doing my due diligence:
1. Uncheck Compatibility Mode in SpareParts
2. Download and run Bluetooth Fix Repair
3. Open Bluetooth Share in Settings>Applications and wipe data/cache
4. Wipe cache and dalvik in Tenfar's System Recovery and reboot
5. Move bluetooth apps back to internal memory
Thus far, nothing has worked.
Any ideas?
Pj
Phoenix, AZ
I'm doing follow-up to my original post, in the event someone ends up experiencing similar issues and searches for a solution.
It's definitely an app or process conflict of some sort. I downloaded a market app, Bluetooth Wall, which has the ability to scan apps and identify those with bluetooth access capabilities.
Unfortunately, I don't have the patience to uninstall all of these apps one-by-one, so I discovered another workaround.
After a reboot, as soon as the home launcher is loaded, I push the Bluetooth toggle to get bluetooth going. This has worked every time, thus far. Unfortunately, if I deactivate Bluetooth at any time afterwards, I cannot reactivate it without a reboot.
According to the battery usage monitor, an unused bluetooth connection (not actively discoverable) is responsible for about 2-3% of total battery life. And with Bluetooth Wall running, my phone should be safe in this state.
Hopefully, I'll get to the heart of this problem after a little more work ...
Pj
Phoenix, AZ
BT works great with the new 234 sbf.
Unfortunately i don't have Atrix so I can't try and see what happens.
I am the developer of Bluetooth Fix Repair, and I'm always looking to support more devices, so I need to ask you: What did my app say? Unsupported Device, or "Fix Applied, good luck!"
Thanks
Phk
Phk,
Thanks for tracking my post down ...
If I recall correctly, Bluetooth Fix Repair ran successfully.
The problem with my X2, though, seems to be an app conflict -- even though I recently flashed to a new build - 2.3.4. from 2.3.3. - the conflict persists.
Pj
Phoenix, AZ
So I found this app which looked really promising but unfortunately doesn't work for me.
Basically would let our Omates send/receive sms via our phones Bluetooth while using our existing phone number. Would be great to not have to rely on wireless or a sim card with a new number.
I was never able to get the Bluetooth to work as it never connected with phone. Im not sure if it is a issue with my phone or with my Omate.
If someone wants to try and see if it works that would be great. The program is $2.99 but you can just refund withing 15 min if it doesnt work like i did.
Heres a full description & link:
Tablet Talk is a tablet SMS texting app that lets you text from a tablet and even make voice calls, while your phone stays in your pocket! It works with all Android tablets, including Nexus, Galaxy, Note, and Kindle Fire tablets. Unlike other apps, Tablet Talk doesn't force you to use a new phone number... your friends, coworkers, and family can contact you with your existing Android phone number. In addition, Tablet Talk does not require an Internet connection, does not store your data, and does not eat your battery!
https://play.google.com/store/apps/details?id=com.apdroid.tabtalk
Does anyone know of another app like this we could use?
Thanks
BT paring/tethering in that manner does not work on any of the x201s.
What works;
Phone > BT Pair/Tether > x201 w/ SIM > Data/Internet
What doesn't work;
x201 > BT Pair/Tether > Phone w/ SIM > Data/Internet
Lokifish Marz said:
BT paring/tethering in that manner does not work on any of the x201s.
What works;
Phone > BT Pair/Tether > x201 w/ SIM > Data/Internet
What doesn't work;
x201 > BT Pair/Tether > Phone w/ SIM > Data/Internet
Click to expand...
Click to collapse
darn that stinks. hopefully one day lol
thanks Lokifish
AndroidFileHost said:
So I found this app which looked really promising but unfortunately doesn't work for me.
Basically would let our Omates send/receive sms via our phones Bluetooth while using our existing phone number. Would be great to not have to rely on wireless or a sim card with a new number.
I was never able to get the Bluetooth to work as it never connected with phone. Im not sure if it is a issue with my phone or with my Omate.
If someone wants to try and see if it works that would be great. The program is $2.99 but you can just refund withing 15 min if it doesnt work like i did.
Heres a full description & link:
Tablet Talk is a tablet SMS texting app that lets you text from a tablet and even make voice calls, while your phone stays in your pocket! It works with all Android tablets, including Nexus, Galaxy, Note, and Kindle Fire tablets. Unlike other apps, Tablet Talk doesn't force you to use a new phone number... your friends, coworkers, and family can contact you with your existing Android phone number. In addition, Tablet Talk does not require an Internet connection, does not store your data, and does not eat your battery!
https://play.google.com/store/apps/details?id=com.apdroid.tabtalk
Does anyone know of another app like this we could use?
Thanks
Click to expand...
Click to collapse
I got this app to work. I figured I've blown more than $3 in my life of silly stuff. I've only tested it once, but it was fun to reject a call from my wrist.
First part:
Both devices are initially detected as a phone. You have to manually go in on the TrueSmart and switch it to "tablet". (Menu->Settings->Setup->Device Type)
Second part:
The bluetooth pairing screen is too big. (It was written for a tablet, no doubt.) If you installed "App Settings" module for Xposed, switching the DPI to 80 will get you past the pairing screen, after which you can put the DPI back to default.
Third part:
The app settings by default don't relay phone controls over to the tablet (watch) so you need to change the settings to make this happen. From the watch, Menu->Settings->Caller ID/Phone Calls.
Post back if you try and it works or doesn't.
jd
jdommer said:
I got this app to work. I figured I've blown more than $3 in my life of silly stuff. I've only tested it once, but it was fun to reject a call from my wrist.
First part:
Both devices are initially detected as a phone. You have to manually go in on the TrueSmart and switch it to "tablet". (Menu->Settings->Setup->Device Type)
Second part:
The bluetooth pairing screen is too big. (It was written for a tablet, no doubt.) If you installed "App Settings" module for Xposed, switching the DPI to 80 will get you past the pairing screen, after which you can put the DPI back to default.
Third part:
The app settings by default don't relay phone controls over to the tablet (watch) so you need to change the settings to make this happen. From the watch, Menu->Settings->Caller ID/Phone Calls.
Post back if you try and it works or doesn't.
jd
Click to expand...
Click to collapse
Awesomw trying it now. Do you have a link to the xposed app settings. The one i just tried didnt work when telling it to change the dpi
Thanks
AndroidFileHost said:
Awesomw trying it now. Do you have a link to the xposed app settings. The one i just tried didnt work when telling it to change the dpi
Thanks
Click to expand...
Click to collapse
I'm still battling this. The app works perfectly on wifi, but very unreliable on bluetooth. Unfortunately, my phone is an SGS3 running CM11 and the bluetooth there is only slightly more reliable than the bluetooth on the TrueSmart so I'm not sure where the problem lies. I haven't gone through the app maker's FAQ yet, and am hopeful I can make it work.
Anyhow, to answer your question:
If you installed Loki's patch, you should have an app called xposed installer. Make sure you have gone in the framework section and done install/update and the reboot required after.
Then go back into the xposed installer and into download. Down in that list somewhere you should find the App Settings module. Download that and install it.
Then go back and into the modules menu. Make sure you have a checkmark in the App Settings module and reboot again.
Now, you can go into app settings (should be a normal app - or you can navigate to it through xposed installer and modules then click on App Settings) and choose the Tablet Talk application and change its DPI to 80. Instead of switching it back to "0" of no override after, I've got it on 92 right now because that makes the dialer portion of the app usable for tablet talk. If you don't care, you may want to go back to default.
Good luck!
jd
jdommer said:
I'm still battling this. The app works perfectly on wifi, but very unreliable on bluetooth. Unfortunately, my phone is an SGS3 running CM11 and the bluetooth there is only slightly more reliable than the bluetooth on the TrueSmart so I'm not sure where the problem lies. I haven't gone through the app maker's FAQ yet, and am hopeful I can make it work.
Anyhow, to answer your question:
If you installed Loki's patch, you should have an app called xposed installer. Make sure you have gone in the framework section and done install/update and the reboot required after.
Then go back into the xposed installer and into download. Down in that list somewhere you should find the App Settings module. Download that and install it.
Then go back and into the modules menu. Make sure you have a checkmark in the App Settings module and reboot again.
Now, you can go into app settings (should be a normal app - or you can navigate to it through xposed installer and modules then click on App Settings) and choose the Tablet Talk application and change its DPI to 80. Instead of switching it back to "0" of no override after, I've got it on 92 right now because that makes the dialer portion of the app usable for tablet talk. If you don't care, you may want to go back to default.
Good luck!
jd
Click to expand...
Click to collapse
most likely its the ts. i own a moto x and have had nothing but issue maintaining a BT connection with the watch. the ts drops the bt connection after 30 secs
rhineymac said:
most likely its the ts. i own a moto x and have had nothing but issue maintaining a BT connection with the watch. the ts drops the bt connection after 30 secs
Click to expand...
Click to collapse
I am having the same issue with the BT on my OTS. It drops connection with my Moto X pretty fast.
Same thing here - about a 30 second connection between the TrueSmart and my stock Nexus7 2013, then it drops.
Sent from my Nexus 5 using Tapatalk
If the range is poor it's an antenna issue. Otherwise it's the firmware.
Lokifish Marz said:
If the range is poor it's an antenna issue. Otherwise it's the firmware.
Click to expand...
Click to collapse
defiantly the firmware on mine dont think its a bad antenna. Really hope they get on the ball and fix this stuff. I cant even get the bluetooth to see my cars bluetooth or headphones. Not sure whats going on. Really frustrating I cant use it for the things i bought it for.
If it is a bad antenna I doubt I'd be able to even request a replacement since every email to them seems to go into a black hole lol
jdommer said:
I'm still battling this. The app works perfectly on wifi, but very unreliable on bluetooth. Unfortunately, my phone is an SGS3 running CM11 and the bluetooth there is only slightly more reliable than the bluetooth on the TrueSmart so I'm not sure where the problem lies. I haven't gone through the app maker's FAQ yet, and am hopeful I can make it work.
Anyhow, to answer your question:
If you installed Loki's patch, you should have an app called xposed installer. Make sure you have gone in the framework section and done install/update and the reboot required after.
Then go back into the xposed installer and into download. Down in that list somewhere you should find the App Settings module. Download that and install it.
Then go back and into the modules menu. Make sure you have a checkmark in the App Settings module and reboot again.
Now, you can go into app settings (should be a normal app - or you can navigate to it through xposed installer and modules then click on App Settings) and choose the Tablet Talk application and change its DPI to 80. Instead of switching it back to "0" of no override after, I've got it on 92 right now because that makes the dialer portion of the app usable for tablet talk. If you don't care, you may want to go back to default.
Good luck!
jd
Click to expand...
Click to collapse
Ya i did his patch but dont have xposed installed. Redid the patch and still nothing. Ill keep tinkering with it. Once i get the dpi working ill test this out further.
AndroidFileHost said:
Ya i did his patch but dont have xposed installed. Redid the patch and still nothing. Ill keep tinkering with it. Once i get the dpi working ill test this out further.
Click to expand...
Click to collapse
xposed and it's required files do not come preintalled with the final release of the patch.
Lokifish Marz said:
xposed and it's required files do not come preintalled with the final release of the patch.
Click to expand...
Click to collapse
ya i looked through the patch and didnt see it so im installing it manually. Thanks for the reply
Lokifish Marz said:
BT paring/tethering in that manner does not work on any of the x201s.
What works;
Phone > BT Pair/Tether > x201 w/ SIM > Data/Internet
What doesn't work;
x201 > BT Pair/Tether > Phone w/ SIM > Data/Internet
Click to expand...
Click to collapse
jdommer said:
I'm still battling this. The app works perfectly on wifi, but very unreliable on bluetooth. Unfortunately, my phone is an SGS3 running CM11 and the bluetooth there is only slightly more reliable than the bluetooth on the TrueSmart so I'm not sure where the problem lies. I haven't gone through the app maker's FAQ yet, and am hopeful I can make it work.
Anyhow, to answer your question:
If you installed Loki's patch, you should have an app called xposed installer. Make sure you have gone in the framework section and done install/update and the reboot required after.
Then go back into the xposed installer and into download. Down in that list somewhere you should find the App Settings module. Download that and install it.
Then go back and into the modules menu. Make sure you have a checkmark in the App Settings module and reboot again.
Now, you can go into app settings (should be a normal app - or you can navigate to it through xposed installer and modules then click on App Settings) and choose the Tablet Talk application and change its DPI to 80. Instead of switching it back to "0" of no override after, I've got it on 92 right now because that makes the dialer portion of the app usable for tablet talk. If you don't care, you may want to go back to default.
Good luck!
jd
Click to expand...
Click to collapse
So i got it to work over bluetooth with the instructions your provided. I can send text messages but it doesnt show any recieved. So thats better then nothing I guess lol. Ill keep tinkering with the settings. Not sure why its not syncing the responses.
Also not being notified of phone calls either but i can make them. So not sure if its just some setting i have wrong that is not letting notifications and things come through. Any ideas?
This didnt help
"Third part:
The app settings by default don't relay phone controls over to the tablet (watch) so you need to change the settings to make this happen. From the watch, Menu->Settings->Caller ID/Phone Calls"
On the phones app it shows the sync log and does show the text messages but the watch is not receiving them. There is a setting on the phone app that says Incoming SMS Fix. Use only if your phones sms app blocks tablet talk from receiving messages.
That doesnt fix the issue. Wonder why you were able to block a call on your watch but I cant.
Ill keep tinkering.
AndroidFileHost said:
That doesnt fix the issue. Wonder why you were able to block a call on your watch but I cant.
Ill keep tinkering.
Click to expand...
Click to collapse
Glad you got it partially working. It looks like the problem is with the BlueTooth on the watch. It can send data to the phone, but it doesn't receive the responses.
The time I did get the call to show up on the watch, I had switched it over to WiFi connect mode. I only realized that after I had already posted.
Anyhow, the app looks pretty decent. Maybe the infamous mythical future firmware update for the watch Bluetooth with fix everything[tm].
jd
jdommer said:
Glad you got it partially working. It looks like the problem is with the BlueTooth on the watch. It can send data to the phone, but it doesn't receive the responses.
The time I did get the call to show up on the watch, I had switched it over to WiFi connect mode. I only realized that after I had already posted.
Anyhow, the app looks pretty decent. Maybe the infamous mythical future firmware update for the watch Bluetooth with fix everything[tm].
jd
Click to expand...
Click to collapse
ok gotcha ya i hope the mythical update makes this work it would be awesome. Im going to write to the developers of the app to see if they can adjust it to better fit on the watch. I doubt they will but cant hurt to ask.
Really hope we see a bluetooth fix for the omate this month but i highly doubt it lol
jdommer said:
Glad you got it partially working. It looks like the problem is with the BlueTooth on the watch. It can send data to the phone, but it doesn't receive the responses.
The time I did get the call to show up on the watch, I had switched it over to WiFi connect mode. I only realized that after I had already posted.
Anyhow, the app looks pretty decent. Maybe the infamous mythical future firmware update for the watch Bluetooth with fix everything[tm].
jd
Click to expand...
Click to collapse
Ya i got it to receive a few times but defiantly is the bluetooth on the watch being funky
AndroidFileHost said:
Ya i got it to receive a few times but defiantly is the bluetooth on the watch being funky
Click to expand...
Click to collapse
At the cost of battery life, ive been running this semi-reliably using my phone as a hotspot and using tablet talk's hotspot mode feature, and connecting on the "tablet"/SmartWatch using wifi mode. Using it like this only makes me wish it worked properly over Bluetooth because short of forwarding all notifications, this is a great great app.
Helgaiden said:
At the cost of battery life, ive been running this semi-reliably using my phone as a hotspot and using tablet talk's hotspot mode feature, and connecting on the "tablet"/SmartWatch using wifi mode. Using it like this only makes me wish it worked properly over Bluetooth because short of forwarding all notifications, this is a great great app.
Click to expand...
Click to collapse
Someone over at Google+ suggested Tablet Notifier. I have received call notifications and SMS successfully over Bluetooth with it. No sending SMS, but that is really not a big deal for me; I hate typing on the watch. Only tried it for a few minutes, but the more of us breaking it, the faster we find if it breaks.
jd
Hi,
I a rooted Xperia Z2 running 4.4.2 17.1.2.A.0.314 and I have lost the ability to use my VPN app. I have happily been using Private Internet Access for a few years and suddenly it has stopped. I went through their customer support but they don't have any ideas. Things I have tried:
Different wifi areas, plus mobile data
Different configurations in the Private Internet Access Software
OpenVPN
OpenVPN Connect
Android OS built in VPN Client, all fail.
Anyone else having this issue? Any ideas?
Many thanks
Steve
Result!
Ok, got this sorted. here is a breakdown of what happened just in case anyone else gets the same problem:
I turned off Xposed modules and tested the VPN app, it was working! I went back and turned them on one at at time, it turns out that a module called "Force Immersive Mode" was stopping the "I trust this application" dialog box from appearing. The Xposed module was set to ignore immersive mode for that app, but I guess the dialog box was system generated rather than app generated.
Either way, everything is fixed.
Steve
Hi buddy, just an update on this in case you or anyone else encounters the same issue. Like you I just ran into the same problem. Luckily I knew it must have been that module as my vpn stopped connecting immediately after enabling the 'force immersive mode' module.
However, I'm the modules settings I just disabled immersive mode for vpn dialogues and system ui (both of which are system apps), and also disabled immersive mode for the xposed auto vpn module (you may not have that installed but I disabled it just to be sure, the module itself just disables android's requirement to accept the vpn connection every time you want to use it).
Hope this helps someone in future, I didn't want to stop using immersive mode altogether but needed my vpn to work so this seems to have solved the issue!
Sent from my GT-I9300 using xda premium
Rassilon7 said:
Ok, got this sorted. here is a breakdown of what happened just in case anyone else gets the same problem:
I turned off Xposed modules and tested the VPN app, it was working! I went back and turned them on one at at time, it turns out that a module called "Force Immersive Mode" was stopping the "I trust this application" dialog box from appearing. The Xposed module was set to ignore immersive mode for that app, but I guess the dialog box was system generated rather than app generated.
Either way, everything is fixed.
Steve
Click to expand...
Click to collapse
You man, have saved my life :good:
worked with xperia zr
Rassilon7 said:
Ok, got this sorted. here is a breakdown of what happened just in case anyone else gets the same problem:
I turned off Xposed modules and tested the VPN app, it was working! I went back and turned them on one at at time, it turns out that a module called "Force Immersive Mode" was stopping the "I trust this application" dialog box from appearing. The Xposed module was set to ignore immersive mode for that app, but I guess the dialog box was system generated rather than app generated.
Either way, everything is fixed.
Steve
Click to expand...
Click to collapse
Thank you so much!! I have been looking for a solution everywhere!! I created an account just to give a thumbs up to you my man!!
this question and solution saved my life! well not literally.. it saved me from reformatiing..
Thank you!
I realize this is an old post, but disabling Xposed Force Immersive Mode completely fixed my VPN issue, so thanks to all!
In my case, I was only using it for a couple apps, so I didn't have it enabled for any of the apps @KingEB mentioned. If anyone knows how to keep the apps I want enabled and disable it for only the VPN related apps, I'd like to know how to do it. Even another immersive mode app, if there is one. Otherwise, I guess I can live without it.
Sorted
Rassilon7 said:
Ok, got this sorted. here is a breakdown of what happened just in case anyone else gets the same problem:
I turned off Xposed modules and tested the VPN app, it was working! I went back and turned them on one at at time, it turns out that a module called "Force Immersive Mode" was stopping the "I trust this application" dialog box from appearing. The Xposed module was set to ignore immersive mode for that app, but I guess the dialog box was system generated rather than app generated.
Either way, everything is fixed.
Steve
Click to expand...
Click to collapse
Thanks for this, same issue with both the official OpenVPN and the OpenVPN for Android apps. Killed 'Force Immersive' and all is good, shame it has too be disabled but I'm going to need VPN for my trip abroad next month
Hey,
I'm suffering some issues with two Samsung mobiles, namely a S3 and a Note2. Push notifications simply won't work reliably on both devices (lacking a data-capable SIM, I could only test on wifi, where other devices work like a charm).
I flashed with M9, then went to nightly, flashed the most recent GApps, and also tried push notification fixer, disabled wifi optimization, re-logged in via Hangouts, to no avail. Without a visible pattern, one or both devices fail getting GCM messages at all. Moving the device to airplane mode and back seems to newly roll the dice.
Wifi on those devices work, as I could ping them reliably, it's just GCM that doesn't work, visible in apps like Threema, but also in the Android device manager that is unable to locate the device, or the Play store when I remotely try to install an app. Putting the device on (unlocking not required) seems to cure the problem for a little while.
Having researched a bit, I'm quite clueless. As both devices IMHO are the same Exynos platform, and have been cleanly installed just a few days ago, is that maybe a known issue, related to Android 4.4 and wifi drivers?
Any chance of debugging GCM to see where the issue is?
Thanks!
AndroUser83 said:
Hey,
I'm suffering some issues with two Samsung mobiles, namely a S3 and a Note2. Push notifications simply won't work reliably on both devices (lacking a data-capable SIM, I could only test on wifi, where other devices work like a charm).
I flashed with M9, then went to nightly, flashed the most recent GApps, and also tried push notification fixer, disabled wifi optimization, re-logged in via Hangouts, to no avail. Without a visible pattern, one or both devices fail getting GCM messages at all. Moving the device to airplane mode and back seems to newly roll the dice.
Wifi on those devices work, as I could ping them reliably, it's just GCM that doesn't work, visible in apps like Threema, but also in the Android device manager that is unable to locate the device, or the Play store when I remotely try to install an app. Putting the device on (unlocking not required) seems to cure the problem for a little while.
Having researched a bit, I'm quite clueless. As both devices IMHO are the same Exynos platform, and have been cleanly installed just a few days ago, is that maybe a known issue, related to Android 4.4 and wifi drivers?
Any chance of debugging GCM to see where the issue is?
Thanks!
Click to expand...
Click to collapse
Are you apply or modifying anything to do with battery saving?
Have you tried reseting to factory setting, wiping /system and /data (warning you will lose all data so backup). reinstall rom gapps plus those specific apps that don't work and tested it?
Thanks for your reply!
Are you apply or modifying anything to do with battery saving?
Click to expand...
Click to collapse
No, not at all.
Have you tried reseting to factory setting, wiping /system and /data (warning you will lose all data so backup). reinstall rom gapps plus those specific apps that don't work and tested it?
Click to expand...
Click to collapse
I did so before installing the system, both devices are a completely fresh setup, incl. wiping of system and data. I thought I had luck with wiping cache & dalvik as it worked yesterday, but today, once again, only one of those devices works.
Seems in fact GCM loses connection on one of the devices (the second one seems to work like a charm now). Removed Google account and re-added it, but status in *#*#426#*#* shows google play failed connection ev:1 err:16 net:1
No idea how to fix that though ;-(
If you have done a complete clean flash and not touched any settings im afraid im out of ideas.
I wanted to post this for people who want to try out MM on the LS990 and have fully working 3G and 4G/LTE data on a Sprint network. I'll explain the exact conditions that I personally went through to get it working.
I CANNOT GUARANTEE THAT THESE STEPS WILL WORK FOR YOU. YOU MAY EXPERIENCE PROBLEMS AS MENTIONED BELOW.
The flashing and setup:
What I personally did was flash BareCee v2 and then updated the PRL and Profile. Afterwards, I dirty flashed BlackSoulxxx's v30b MM port (see: http://forum.xda-developers.com/lg-g3/development/rom-lge-d855-android-marshmallow-ported-t3285025). I rooted the port with SuperSU 2.52 BETA via TWRP. Once I got to the home screen, I was greeted by a notification that stated that I need to update Google Play services. I updated it. Then I confirmed my appropriate APN settings. I'm on RingPlus, so this was important for me to even get mobile data at all.
The fix:
Once I went through all that, I edited /system/build.prop using Solid Explorer with the following lines:
ro.product.model=LGLS990
ro.build.target_country=US
ro.product.locale.language=en
ro.product.locale.region=US
ro.cdma.home.operator.alpha=Chameleon
ro.cdma.home.operator.numeric=310120
ro.cdma.homesystem=64,65,76,77,78,79,80,81,82,83
Click to expand...
Click to collapse
The following two lines might be disabled in your build.prop. If they are active, ensure it's set properly as listed below. It was disabled on mine, so I did NOT touch them or re-enable them:
ro.telephony.default_network=10
telephony.lteOnCdmaDevice=1
Click to expand...
Click to collapse
If you don't care for having your phone unlocked for Global/GSM use, you can edit the following lines to get the Sprint 3G/LTE, airplane mode, etc. status bar icons and branding (as well as disable the Global/GSM network option):
ro.build.target_operator=SPR
ro.carrier=Sprint
Click to expand...
Click to collapse
After you have edited the build.prop, give it a reboot and toggle data/airplane mode in the quick toggle/notification pull-down menu until you get data to finally turn on. Once it switches on, it'll work until your next reboot, I believe. You will need to fiddle with the toggle again once you reboot. This is a bug due to the ports. There's no known fix for this besides dirty flashing over BareCee v2, but I can't really say for certain if everybody will have this fixed just by dirty flashing. Dirty flashing also allows the settings switch and data settings panel to work correctly (sometimes).
From what I can tell, ro.cdma.home.operator.numeric is the key factor for getting 3G data to work properly.
Negative repercussions:
You may have issues with Messaging.app and weather.app NOT working/crashing after launch IF YOU DIRTY FLASH. I'm not sure how to fix this issue other than with a CLEAN FLASH.
Others have expressed issues with google play services not working or force crashing and causing the OS to be unstable. Clean flashing fixes this problem, usually.
Fulmics 3.1 and xpirt was the source of this fix and it was stated that this will be included in the next version of Fulmics 3.X. I personally cannot use Fulmics because it's highly unstable for me. It overheats my phone and there's heavy lag with poor battery life.
Other Notes:
I would like to see somebody clean flash BlackSoulxxx's port or Fulmics 3.1 and try this out. I'm too busy to keep flashing/testing and everything I need is working (I don't bother with the stock Messaging app and weather app works fine for me). Please report back if you do this and let us know what happens. I suspect this is the best possible outcome for avoiding force crashes, but it also may mean that the data may not work properly, even after this fix.
Hope this helps somebody. It took me weeks to resolve this issue.
Thanks to:
blacksoulxxx
xpirt
6th_hokage
jglm4u
This should get its own post: The MM port is unlocked for GSM by default, I believe. Fulmics 3.1 is the same.
No luck for me..
Whenever I make all these changes on a clean flash of fulmics 3.1, I get constant FC's of com.android.phone
spanky34 said:
No luck for me..
Whenever I make all these changes on a clean flash of fulmics 3.1, I get constant FC's of com.android.phone
Click to expand...
Click to collapse
Not sure why you're getting phone FCs, but I'm like 99% sure it may be a fulmics issue. I'm using the blacksoulxxx port right now.
Also, confirmed bug:
ro.build.target_operator=SPR
ro.carrier=Sprint
These two lines cause media services to crash for a media player stuff. Facebook messenger videos and Google hangouts voicemail audio crashed when it searches for sprint-specific players. Strange as hell.
Couldn't you just make a flashable zip to fix the build.prop?