As we don't have an official thread dedicated to cm 12.1 for T-mobile s4, I create this so that T-mobile users can discuss everything about Official cm12.1 for jfltetmo in just one place. This way, we will be able to help one another better.
https://download.cyanogenmod.org/?device=jfltetmo
NB. I am not the maintainer for this device.
Reserved
stkpxl said:
Is Bluetooth fixed? That is the only reason I am staying away right now.
Click to expand...
Click to collapse
I don't use bluetooth, but I see comments in jfltexx thread that say it is fixed in the latest version which is today's version.
stkpxl said:
That is good to hear. Maybe I will give it a try.
Click to expand...
Click to collapse
Try and report back!
i just installed it along with the official gapps from http://wiki.cyanogenmod.org/w/Google_Apps
wipe dalvik/cache and now having random gapps crashes... gonna play with it a bit more, not sure what my plan is.. i'll probably do a hard flash instead of soft one if it doesn't want to work
PhrostB said:
i just installed it along with the official gapps from http://wiki.cyanogenmod.org/w/Google_Apps
wipe dalvik/cache and now having random gapps crashes... gonna play with it a bit more, not sure what my plan is.. i'll probably do a hard flash instead of soft one if it doesn't want to work
Click to expand...
Click to collapse
No crash at all on my side with pa stock 5.1 gapps
i feel like it should work with the official cm package, no?
it looks like the issue might have something to do with multiple user accounts.. i only have one account. i wonder if there's a way around this. i've been reading some other people's reports about these crashes and many are saying that it doesn't matter which gapps package is used. i guess i'll try pa gapps if i don't have any success
edit: i decided to just try a factory reset instead.. i'll update on my progress
edit: factory reset worked fine.. now i just have to put all my settings back the way i like them
stkpxl said:
Just wanted to post a quick update. I haven't seen a Bluetooth crash yet. I had a bit of trouble pairing my headset though. Took a few tries and shutting BT off and back on but it did pair. My watch has also been consistently syncing. I have yet to stream music through BT, but assuming all the crashing is gone so far, it may be safe to assume that it will work fine.
Click to expand...
Click to collapse
Thanks for your feedback my friend!
No problems here at all. Used heavily since the OTA with the 1+one theme. Loving CM12.1
anyone else having problems with the stock email app and exchange email addresses? I added a hotmail email and i get constant "exchange has sopped working"
I am on 4/29 nightly, Have not seen any issues so far. I will post if I see anything. This phone works flawlessly with cm12.1, I don't even see the purpose
of upgrading to a new device now. lol at chumps that buy a new phone every year.
jobrien2001 said:
anyone else having problems with the stock email app and exchange email addresses? I added a hotmail email and i get constant "exchange has sopped working"
Click to expand...
Click to collapse
I use gmail and inbox from google, have not used the exchange email.
baby281 said:
I use gmail and inbox from google, have not used the exchange email.
Click to expand...
Click to collapse
I have a gmail and gmail works fine, the problem im having is with exchange emails only.
jobrien2001 said:
I have a gmail and gmail works fine, the problem im having is with exchange emails only.
Click to expand...
Click to collapse
try today's nightly see if that fixed your problem?
edit: looking at the changelog, i don't see anything besides email notification lights.
baby281 said:
try today's nightly see if that fixed your problem?
Click to expand...
Click to collapse
No, I am on cm-12.1-20150430-NIGHTLY-jfltetmo.zip atm and the error has been happening since the first release.
Curious if anyone else has a problem with an exchange mail or is it just me...
hows everyone's battery life?
baby281 said:
hows everyone's battery life?
Click to expand...
Click to collapse
same as always... not that great. when i use the uber partner app and drive, my battery slowly dies EVEN WHILE CHARGING! takes about ten hours or so though
stkpxl said:
Is Bluetooth fixed? That is the only reason I am staying away right now.
Click to expand...
Click to collapse
I'd like to save you guys a lot of heartache - Bluetooth is definitely an issue depending on how and where you use it. I've found that if you're pairing with BLE (Bluetooth Low Energy) devices or car head units, Bluetooth will crash consistently. I actually posted my attempts to troubleshoot it in a thread here: forum(dot)cyanogenmod(dot)org(slash)topic(slash)108738-bugs-with-121-on-i9505 (same username, my account here is too new to post links) and you'll see that my last post (as of this writing) is that I'm reverting to stock.
As I type this I'm anxiously waiting for all of the stock updates to finish so I can do some testing with my BT LE HRM and see if Bluetooth is stable again.
stkpxl said:
It seems like a pretty big issue. Not sure why it isn't working correctly since it is a much older model. It is definitely annoying to deal with.
Click to expand...
Click to collapse
Definitely an annoyance. I posted in the other thread and should probably put my update here as well - I flashed back to stock (4.4.4) and have gone a full day without any Bluetooth crashes. I have a Nexus 7 that I've also flashed to CM 12.1 and would like to experiment to see if I have the same BLE problems there, but unfortunately just don't have time since I'm heading out of the country in a few days. Seeing as how I'll be without a high speed connection (no ability to research or download updates) it's more important that I get back to a stable stock while I'm travelling. When I return I may find some time to experiment further and see if it's even possible to extract the Bluetooth packages from my stable 4.4.4 system and somehow use them on the CM 12.1 installation. I'm a newb at this but I'm hoping that there's some level of cross-system compatibility, kind of like how drivers for Windows 7 usually will work on Windows 8.
May I ask what kernel you guys are using?
King Fox said:
May I ask what kernel you guys are using?
Click to expand...
Click to collapse
Cm 12.1 Stock kernel for now
Related
hello. i recently flashed the stable release of cyanogenmod 7 on my evo and i've come to realise that i can receive mms, but cannot send them. every time i attempt sending, it just keeps saying "sending..." but never actually sends...i've been trying to browse around, but wasn't able to find any solution to this problem...anyone able to offer any help on this? thanks in advance!
nelce said:
hello. i recently flashed the stable release of cyanogenmod 7 on my evo and i've come to realise that i can receive mms, but cannot send them. every time i attempt sending, it just keeps saying "sending..." but never actually sends...i've been trying to browse around, but wasn't able to find any solution to this problem...anyone able to offer any help on this? thanks in advance!
Click to expand...
Click to collapse
I am running cm7 final but I have been having the opposite problem, I can send but there are some I can't receive. When I have this issue the mms is usually coming from a person not on the Sprint network ...
If you're having issues sending/receiving mms, try the following.
Using adv launcher, create a shortcut to custom activity.
Specifically, settings/*apn*. I can't remember the exact name, but you'll have to navigate the list of junction points when you do the settings pull down.
Once created, go ahead and tap on the shortcut. You'll see 2 apn settings. One will have sprintpcs.com in the MMSC field, the other wont.
For the one that does not, scroll down to APN type. Change the parameter in that field to 'default' (small letters without the quotes).
For the other one, change it to 'mms'
Reboot. You should be good to go.
nelce said:
hello. i recently flashed the stable release of cyanogenmod 7 on my evo and i've come to realise that i can receive mms, but cannot send them. every time i attempt sending, it just keeps saying "sending..." but never actually sends...i've been trying to browse around, but wasn't able to find any solution to this problem...anyone able to offer any help on this? thanks in advance!
Click to expand...
Click to collapse
Took me about 2 minutes total to find this! I don't know why people don't use the search feature on here....is FREE!!! NO CHARGE AT ALL!!!
http://forum.xda-developers.com/showthread.php?p=12804901&highlight=mms#post12804901
Read post 6321 and that will solve this MMS problem!
Not trying to sound like an ass and if I am then that's fine because I know I am BUT it took you longer to post your question on here then it would of taken you to search for it in the right place.
Why do people call a release that still has issues and needs special fixes, stable?
HipKat said:
Why do people call a release that still has issues and needs special fixes, stable?
Click to expand...
Click to collapse
Well......is kind of like comparing peanuts to apples here BUT take Windows for example! Windows gets released right?! Well is suppose to be BUG FREE and completely sable correct? WELL it isn't! Not every rom on here is 100% BUG FREE and it needs updates/little things fix from time to time because not every phone acts the same way to every rom! CM7 works flawlessly on my phone but as you can see, dude has issues with his MMS! Not trying to start an argument or anything on here BUT don't act all high and mighty because you're using a sense rom where things happen to work a bit better!
It takes bigger balls to do something completely different like an AOSP rom then just play around with .PNGs and call it a ROM! I could take a sense rom and use it as a base and change a couple of things, add some wallpaper and upload it but am I going to?...NO!!...because that's just stupid!
I'm not acting all high and mighty. I just happen to be using a sense ROM now. I've ran CM, too. And Miui, et al.... Like I told someone yesterday, when I buy a new car, I don't need to add things to make the lights go on, or do some fanangling to make the wipers work. MMS is a basic feature of the phone. The basics, like GPS, etc, should work by default, not because you have to type some weird code into you dialer, oh, and do it on another type of mod first, then flash back to CM......
HipKat said:
Why do people call a release that still has issues and needs special fixes, stable?
Click to expand...
Click to collapse
exactly! im not sure why cm7 was finaled, too many bugs yet compared to the deck rom or salvage-mod rom which both are 100% functional.
I'm not getting what you guys are saying about bugs. I have experienced none. Mms, GPS, wimax all work out the box.
Sent from my PC36100 using XDA Premium App
Hello everyone,
I have an error trying to open Spotify with ICS. I have a Premuim account, but when I try to start the app it won't do it.
The error is that when you had filled in username and pasword worns you that you will need a data conexion, and that might be charged apart. when you press "OK" it continues to pop up the same window all over again, non stop.
I tried with Wiffi and also with 3G. Don't work.
I have the 4.0.1. I heard that there is a 4.1.0 OTA update, but if I try to get a newer one it says it's allready updated.
I'm not the only one:
getsatisfaction.com/spotify/topics/spotify_is_crashing_on_open_when_in_online_mode_ics
I'm from Spain, and I have Orange. But the problem I thinck is ICS.
regorsnas said:
I have the 4.0.1. I heard that there is a 4.1.0 OTA update, but if I try to get a newer one it says it's allready updated.
Click to expand...
Click to collapse
There is no 4.1 OTA update officially released, this seems to be a development build by all information online.
regorsnas said:
I'm from Spain, and I have Orange. But the problem I thinck is ICS.
Click to expand...
Click to collapse
The problem is likely with the Spotify app rather than ICS, and Spotify will need to update their app.
Exacty when I said the problem was ICS I meant the incompatibility betwen the S.O an the app. As you say Spotify will have to upgrade the app.
I wanted to make sure that is the problem, and no another thing.
Spotify is working fine for me.. I've been listening to stuff on it all week.
I'm running stock with the paul's kernel, and the only unusual option is force GPU rendering is on.
Okay , it was a problem of username and pasword. Then why they don't show with the exact dialog saying that.
I don't underdtad. At least it works for me now.
regorsnas said:
Okay , it was a problem of username and pasword. Then why they don't show with the exact dialog saying that.
I don't underdtad. At least it works for me now.
Click to expand...
Click to collapse
How did you fix it? I have the same problem and it never lets me put in my username and password.
bluther said:
How did you fix it? I have the same problem and it never lets me put in my username and password.
Click to expand...
Click to collapse
I had the same problem .. It turned out that it automatically became a space Eftr my text. My username stopped thus by a space, deleted it and then it went to login.
Doesn't work for me. I submitted a support request to Spotify and they said "We are sorry but we do not support Android 4.0 and we do not know when we will"
Not very helpful.
I'm running Liquid Smooth 2.5 and have just found that anytime I try and use voice search the microphone icon glows as if it is recognizing but as soon as it goes to search it just errors out with "Cannot reach Google at the moment". Has anyone else encountered this and are there any suggested fixes? I found some threads of making sure the device date and time is correct. It is. Interestingly I just tried on my rooted stock N7 and same thing... Yet I also just tried on my wife's Asus TF300t and it is working properly... I've checked all google account settings I can think of and can't see anything abnormal.
Thanks in advance for any help.
Galloway said:
I'm running Liquid Smooth 2.5 and have just found that anytime I try and use voice search the microphone icon glows as if it is recognizing but as soon as it goes to search it just errors out with "Cannot reach Google at the moment". Has anyone else encountered this and are there any suggested fixes? I found some threads of making sure the device date and time is correct. It is. Interestingly I just tried on my rooted stock N7 and same thing... Yet I also just tried on my wife's Asus TF300t and it is working properly... I've checked all google account settings I can think of and can't see anything abnormal.
Thanks in advance for any help.
Click to expand...
Click to collapse
What color are you signal bars? Grey = No connection to Google, Blue = Connection to Google
Try clearing data for the Google Framework
Signal bars are blue both on wifi and on data with good signal. I just tried clearing Google Services Framework... No go still unfortunately. Thanks for the suggestion however.
Galloway said:
Signal bars are blue both on wifi and on data with good signal. I just tried clearing Google Services Framework... No go still unfortunately. Thanks for the suggestion however.
Click to expand...
Click to collapse
And which ROM is this?
DirtyOldMan said:
And which ROM is this?
Click to expand...
Click to collapse
He's running Liquid Smooth 2.5 as stated in the first sentence.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Galloway said:
Signal bars are blue both on wifi and on data with good signal. I just tried clearing Google Services Framework... No go still unfortunately. Thanks for the suggestion however.
Click to expand...
Click to collapse
Reflash the gapps/addons
KorGuy123 said:
He's running Liquid Smooth 2.5 as stated in the first sentence.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks
I will try refreshing Gapps when I get a chance but the thing that has me puzzled is why my stock rooted N7 is doing the same thing. I can't help but think it is an issue with my account or something. I haven't changed any settings recently that I know of. if it was just a Gapps issue I would have thought it would be isolated to just my SGS3. It isn't likely a location issue as my Wife's tablet is working fine.... Definitely confused...
Again thanks for any and all suggestions
Galloway said:
I will try refreshing Gapps when I get a chance but the thing that has me puzzled is why my stock rooted N7 is doing the same thing. I can't help but think it is an issue with my account or something. I haven't changed any settings recently that I know of. if it was just a Gapps issue I would have thought it would be isolated to just my SGS3. It isn't likely a location issue as my Wife's tablet is working fine.... Definitely confused...
Again thanks for any and all suggestions
Click to expand...
Click to collapse
And all of these are connected to your WiFi?
Remove and Re-add your google account on the affected devices.
Just to try I added my wife's account into Google now and tried voice searching with her account from my N7 and it didn't work either. It works from her tablet. I think this means it is not a ROM issue but rather a settings or similar issue. I will try a Gapps refresh later to see what happens. If anyone else has experienced this regardless of whether there is a fix I'd be curious to know. if others have I may submit it to Google. if it is just a weird issue for me I'd rather try working through it.
Galloway said:
Just to try I added my wife's account into Google now and tried voice searching with her account from my N7 and it didn't work either. It works from her tablet. I think this means it is not a ROM issue but rather a settings or similar issue. I will try a Gapps refresh later to see what happens. If anyone else has experienced this regardless of whether there is a fix I'd be curious to know. if others have I may submit it to Google. if it is just a weird issue for me I'd rather try working through it.
Click to expand...
Click to collapse
Gapps won't fix it... it's 2 devices... bear with me I need to narrow it down....
---------- Post added at 09:52 AM ---------- Previous post was at 09:51 AM ----------
Check PM, sending you my GTalk, add me, so we can chat.
SGS3 wifi or data (LTE mainly) the N7 and TF300T are wifi only...
Galloway said:
SGS3 wifi or data (LTE mainly) the N7 and TF300T are wife only...
Click to expand...
Click to collapse
Check you PM... I sent you my gtalk... add me... you can chat at gmail.com
Galloway said:
I'm running Liquid Smooth 2.5 and have just found that anytime I try and use voice search the microphone icon glows as if it is recognizing but as soon as it goes to search it just errors out with "Cannot reach Google at the moment". Has anyone else encountered this and are there any suggested fixes? I found some threads of making sure the device date and time is correct. It is. Interestingly I just tried on my rooted stock N7 and same thing... Yet I also just tried on my wife's Asus TF300t and it is working properly... I've checked all google account settings I can think of and can't see anything abnormal.
Thanks in advance for any help.
Click to expand...
Click to collapse
I've been having this problem too with an HTC One on a Sense-based custom ROM, and a HTC Evo 4G LTE both stock and custom. I've found better success uninstalling the updates to the Google Search app though it's still slower than it used to be. Some more people have talked about it here... http://forums.androidcentral.com/go...-google-moment-while-online-voice-typing.html
Doesn't seem like there's much of a solution or acknowledgment by Google that there's a problem.
I fixed the issue!! On a hunch I decided to delete my Google account from the phone completely. I then booted to recovery and cleared cache and dalvik. Rebooted and added my Google account back in... it is now working as it used to. If anyone else is having the issue I would recommend trying this and see if it helps you as well.
Almost forgot but I'd really like to thank everyone who contributed ideas and thoughts!
I just verified this fixed my N7 as well!
Thanks
Galloway said:
I fixed the issue!! On a hunch I decided to delete my Google account from the phone completely. I then booted to recovery and cleared cache and dalvik. Rebooted and added my Google account back in... it is now working as it used to. If anyone else is having the issue I would recommend trying this and see if it helps you as well.
Click to expand...
Click to collapse
thanks it worked for me.....
Easier solution
Galloway said:
I'm running Liquid Smooth 2.5 and have just found that anytime I try and use voice search the microphone icon glows as if it is recognizing but as soon as it goes to search it just errors out with "Cannot reach Google at the moment". Has anyone else encountered this and are there any suggested fixes? I found some threads of making sure the device date and time is correct. It is. Interestingly I just tried on my rooted stock N7 and same thing... Yet I also just tried on my wife's Asus TF300t and it is working properly... I've checked all google account settings I can think of and can't see anything abnormal.
Thanks in advance for any help.
Click to expand...
Click to collapse
My impression from searches on Google's forums is that this is a fairly prevalent problem. I don't know what causes it, but I've seen it on S4s, too. I just wanted to add that, anecdotally, I tried clearing the cache (though not dalvik) and removing the Google account, to no avail; however, I found a much simpler solution:
Settings, My Device, Language and input
Change Voice recognizer from Google to something else (in my case Samsung powered by Vlingo)
(Optional) Change Voice recognizer back to Google
This resolved the issue for me, please let me know if it works for others (I don't need a thumbs-up or anything, I'm honestly just curious if it's that simple and we're making it out to be more difficult.)
jacksonpeebles said:
My impression from searches on Google's forums is that this is a fairly prevalent problem. I don't know what causes it, but I've seen it on S4s, too. I just wanted to add that, anecdotally, I tried clearing the cache (though not dalvik) and removing the Google account, to no avail; however, I found a much simpler solution:
Settings, My Device, Language and input
Change Voice recognizer from Google to something else (in my case Samsung powered by Vlingo)
(Optional) Change Voice recognizer back to Google
This resolved the issue for me, please let me know if it works for others (I don't need a thumbs-up or anything, I'm honestly just curious if it's that simple and we're making it out to be more difficult.)
Click to expand...
Click to collapse
This solution didn't work for me...but I solved the problem by cleaning cache / data and doing a "force stop" of Google Search :laugh:
tia08 said:
This solution didn't work for me...but I solved the problem by cleaning cache / data and doing a "force stop" of Google Search :laugh:
Click to expand...
Click to collapse
Whatever works, I guess!
Hi all,
I have been hunting around for the last three days and cannot find a unified answer as to why MMS does not work on my i747. No MMS function is kind of a deal breaker. I have changed APN settings a number of times to no avail. Switched from PA to CM and back no wipe and full wipe etc and still no dice. Does anyone have any solutions that are repeatable? If so I would love to make it known.
Frustratedly,
999
triplenine said:
Hi all,
I have been hunting around for the last three days and cannot find a unified answer as to why MMS does not work on my i747. No MMS function is kind of a deal breaker. I have changed APN settings a number of times to no avail. Switched from PA to CM and back no wipe and full wipe etc and still no dice. Does anyone have any solutions that are repeatable? If so I would love to make it known.
Frustratedly,
999
Click to expand...
Click to collapse
are you using any type of startup programs?
if you are see if you checked the messages app and if you did uncheck it.
Not sure what you mean by startup apps but the phone was pure as the driven snow and still nothing. If you can consider cm pure
triplenine said:
Not sure what you mean by startup apps but the phone was pure as the driven snow and still nothing. If you can consider cm pure
Click to expand...
Click to collapse
Does everything else work? Like phone calls, texting, and cellular data? If so, more than likely APN related. Who is your service provider?
Yeah. Everything else is fine. Sms is good and quick. Data speeds are tip top. Mms messages just stall out at "sending" I use ATT in Colorado.
triplenine said:
Yeah. Everything else is fine. Sms is good and quick. Data speeds are tip top. Mms messages just stall out at "sending" I use ATT in Colorado.
Click to expand...
Click to collapse
Well if everything else is working properly, then I'd almost bet it's APN related. Double check, and make sure everything is entered properly, periods,spaces, capitalization. If so, and it still doesn't work, did u make a backup of stock before u ever flashed a custom ROM? If so, restore it and see if they work. Also, have u updated your modem?
triplenine said:
Yeah. Everything else is fine. Sms is good and quick. Data speeds are tip top. Mms messages just stall out at "sending" I use ATT in Colorado.
Click to expand...
Click to collapse
Can you receive mms messages? Because I recently couldn't send picture messages, but could receive them. Turns out picasa uploader had some corrupt data. I would make sure that app isnt frozen or accidently uninstalled
Some of the newer ROMs have issues with resizing the image being sent - it is larger that AT&T will allow. I don't remember what thread it was in but someone mentioned that there was a change made to the mms.apk that caused the issue. They posted an APK that they pulled from a ROM from June (I think it may have been a CyanogenMod nightly).
--edit--
I think it was polobunny that posted it. I'm too tired to look for it but his post in reply to fastest963's post on a possible CyanogenMod resolution to the issue in the thread listed below.
http://forum.xda-developers.com/showthread.php?p=44953619&postcount=15365
triplenine said:
Yeah. Everything else is fine. Sms is good and quick. Data speeds are tip top. Mms messages just stall out at "sending" I use ATT in Colorado.
Click to expand...
Click to collapse
I had that same problem with Slimbean. I sent them a logcat and the fix had something to do with "the lack of hugemem for kernel".
Not sure if this is applicable, but this guy posted a fix on a thread for MMS issues on a 4.3 ROM. Perhaps worth investigating?
http://forum.xda-developers.com/showthread.php?p=44956784
umm...
what carrier are you? bell? rogers? ect...
i run pac on bell and get mms fine.
I had the same issue as the op. I use the app handcent SMS app from the play store and that fixes the issue sometimes. I was on cyanogenmod 10.2 when I had the issue.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4
So it looks like I was suffering from the ATT/cm photo resizing issue that was referenced a few replies back. The most recent nightly addressed it and it seems to work well now. Going to try to send a bunch of pictures of various sizes to verify its functionality but it looks like people with ATT and i747s should be on an even playing field on CM. I wonder how soon paranoidandroid will have this update.
triplenine said:
So it looks like I was suffering from the ATT/cm photo resizing issue that was referenced a few replies back. The most recent nightly addressed it and it seems to work well now. Going to try to send a bunch of pictures of various sizes to verify its functionality but it looks like people with ATT and i747s should be on an even playing field on CM. I wonder how soon paranoidandroid will have this update.
Click to expand...
Click to collapse
I have had this issue on almost all ports and CM roms. Compounded by living in a poor service area. The only consistent fix for me is what Bruce Lee suggested and use a 3rd party sms, I like GOsms personally. Actually I like stock better so I turn off notifications in Go and greenify it until I need to send a pic.
Bubba Fett said:
I have had this issue on almost all ports and CM roms. Compounded by living in a poor service area. The only consistent fix for me is what Bruce Lee suggested and use a 3rd party sms, I like GOsms personally. Actually I like stock better so I turn off notifications in Go and greenify it until I need to send a pic.
Click to expand...
Click to collapse
Fix permissions, on ATT can send 8mp photos fine on any 4.3 ROM I've tried (CM, Quantum, PA, Illusion).
x0ne215 said:
Fix permissions, on ATT can send 8mp photos fine on any 4.3 ROM I've tried (CM, Quantum, PA, Illusion).
Click to expand...
Click to collapse
I dont think I've tried again after fixing permissions so ill try that. Thanks. If its that easy, I'll be both happy and pissed that I didn't try that. I noticed earlier in this thread someone said something about the picassa uploader. I usually freeze that app, and was just searching for what it does. If you don't mind me asking, are you aware of any issues that may cause in sending MMS? Seems to only be involved with uploading to an account, which I dont have.
Bubba Fett said:
I dont think I've tried again after fixing permissions so ill try that. Thanks. If its that easy, I'll be both happy and pissed that I didn't try that. I noticed earlier in this thread someone said something about the picassa uploader. I usually freeze that app, and was just searching for what it does. If you don't mind me asking, are you aware of any issues that may cause in sending MMS? Seems to only be involved with uploading to an account, which I dont have.
Click to expand...
Click to collapse
Only problems I've had with MMS are as follows:
"Sending" bug - either fix with "Fix permissions" in recovery, or just using a different mms.apk from a ROM it did work on (4.3)
APN settings - only happened once on a 4.2.2 ROM, don't remember which
Never used picassa uploader, or froze it (I don't use TiBu). But recently with the 4.3 ROM's I've tried fixing permissions is all it's taken for me. Just to be safe I've made it a practice to Fix Permissions 3 times before rebooting, also clearing cache/dalvik
QUOTE=x0ne215;45006821]Only problems I've had with MMS are as follows:
"Sending" bug - either fix with "Fix permissions" in recovery, or just using a different mms.apk from a ROM it did work on (4.3)
APN settings - only happened once on a 4.2.2 ROM, don't remember which
Never used picassa uploader, or froze it (I don't use TiBu). But recently with the 4.3 ROM's I've tried fixing permissions is all it's taken for me. Just to be safe I've made it a practice to Fix Permissions 3 times before rebooting, also clearing cache/dalvik[/QUOTE]
Ok. Thanks. I just noticed newest CWM doesnt have fix permission so i did it through scripter. Only tied once though. It didn't work with that one try. I have also tried pushing new mms.apk but no luck. Ill try a couple more fix permissions and try again. Always nice to have new oprions for this fix so thank you again for the response.
Bubba Fett said:
x0ne215 said:
Only problems I've had with MMS are as follows:
"Sending" bug - either fix with "Fix permissions" in recovery, or just using a different mms.apk from a ROM it did work on (4.3)
APN settings - only happened once on a 4.2.2 ROM, don't remember which
Never used picassa uploader, or froze it (I don't use TiBu). But recently with the 4.3 ROM's I've tried fixing permissions is all it's taken for me. Just to be safe I've made it a practice to Fix Permissions 3 times before rebooting, also clearing cache/dalvik
Click to expand...
Click to collapse
Ok. Thanks. I just noticed newest CWM doesnt have fix permission so i did it through scripter. Only tied once though. It didn't work with that one try. I have also tried pushing new mms.apk but no luck. Ill try a couple more fix permissions and try again. Always nice to have new oprions for this fix so thank you again for the response.
Click to expand...
Click to collapse
No problem, but the newest CWM doesn't have it? I'm using Philz CWM ported by blackwing (somewhere in android dev), it's under advanced options for me. Which MMS.apk did you try?
x0ne215 said:
No problem, but the newest CWM doesn't have it? I'm using Philz CWM ported by blackwing (somewhere in android dev), it's under advanced options for me. Which MMS.apk did you try?
Click to expand...
Click to collapse
I'm currently using novaGen ROM cm10. I tried different MMS.apk from his mrom and also a couple themed aosp apk's I grabbed from somewhere. The weird thing is, I use cool tool to monitor data sent and speed, and I can see data slowly going out but they never complete. However gosms worked on the first try. I used TW ROMs like Goodness for a long time with the same results. I also just got a new s3 cause my IMEI and or my hardware got borked and I lost my backup, so ive eliminated the phone as the issue. I do live in a tough service area but still after 45 min it fails. I get around 25% signal strength. I have tried in a better area in the past but not too recently. Same results.
Since I am considered a new member, I cannot post this to the correct section (maybe a MOD can confirm or move?)
However, I have a Canadian Galaxy S3 from Wind, SGH-T999V
Yesterday, I installed CM10. After many issues trying to flash, I realized I have to start at 10.0 and work my way up.
I am now on 10.2 nightlies.
Just wanted to know if anyone else is having issues receiving Hangouts messages?
I get them fine on my Hangouts add-on in Chrome on my Mac, but not on my phone...
Any ideas or does anyone else have the same issue?
Thanks!
unknown243 said:
Since I am considered a new member, I cannot post this to the correct section (maybe a MOD can confirm or move?)
However, I have a Canadian Galaxy S3 from Wind, SGH-T999V
Yesterday, I installed CM10. After many issues trying to flash, I realized I have to start at 10.0 and work my way up.
I am now on 10.2 nightlies.
Just wanted to know if anyone else is having issues receiving Hangouts messages?
I get them fine on my Hangouts add-on in Chrome on my Mac, but not on my phone...
Any ideas or does anyone else have the same issue?
Thanks!
Click to expand...
Click to collapse
Couple things here:
You don't have to work your way up to CM 10.2. Just start with it.
If you are running Hangouts in Chrome on your Mac - if the window is open, the phone will not receive a notification. This is by design.
But if Chrome is not running, you should get them. Also, ensure that you have the notifications enabled in the app, and that the app is actually running in the background.
Aerowinder said:
Couple things here:
You don't have to work your way up to CM 10.2. Just start with it.
If you are running Hangouts in Chrome on your Mac - if the window is open, the phone will not receive a notification. This is by design.
But if Chrome is not running, you should get them. Also, ensure that you have the notifications enabled in the app, and that the app is actually running in the background.
Click to expand...
Click to collapse
I had issues installing 10.2 Direct, and had to do 10.0 first, then 10.1, then 10.2 .. maybe I did something wrong?
Who knows, been flashing roms forever but just recently decided to flash a custom rom again...long story.
Even if Chrome is closed, laptop off, nothing. I have sent from mobile, to a friend, TESTING, PLEASE REPLY. And nothing until I check manually.
Thanks for the suggestion though!