I've been in touch with Google the past few weeks cause I hardly get any updates through the market since about three months.
Google noticed that everybody or at least most users with a non-standard screen density have this issue. Many apps give a 'your device is not compatible with this application' error when browsing the internet/desktop market version (not the phone market app).
And than in the market you won't see your apps under 'My Apps'
When you switch back to 'default density (240) the problem is gone.
Google is investigating the issue but does not know yet if they will support non-standard densities.
If this is a double post, sorry for that.
They dont't need to support non standard dpi but they should let applications to show up in Market. This is the reason I downgraded the Market version on my phone, but this is not a solution. I hope Google will let the users decide what dpi is best for them.
Yep but as long as they fear claims and complaints nothing may happen...
At the same time the 2 persons I've been dealing with have been very cooperative and asked me lots of questions. Gave them app details, logs and after a few weeks they came back with this conclusion.
Which sort of makes respect them, after all, I'm only one of nearly 200 million Android users!
blackspp said:
I've been in touch with Google the past few weeks cause I hardly get any updates through the market since about three months.
Google noticed that everybody or at least most users with a non-standard screen density have this issue. Many apps give a 'your device is not compatible with this application' error when browsing the internet/desktop market version (not the phone market app).
And than in the market you won't see your apps under 'My Apps'
When you switch back to 'default density (240) the problem is gone.
Google is investigating the issue but does not know yet if they will support non-standard densities.
If this is a double post, sorry for that.
Click to expand...
Click to collapse
Seen a couple of these pop up so far. The problem has been affecting me for a while now, but I just figured out what caused it last week. Lots of people (myself included) seem to have thought nobody else had this problem.
Post: Changing DPI and new market makes apps incompatibility
Post: [Q] Cannot update multiple installed apps, is it the new market?
blackspp said:
Yep but as long as they fear claims and complaints nothing may happen...
At the same time the 2 persons I've been dealing with have been very cooperative and asked me lots of questions. Gave them app details, logs and after a few weeks they came back with this conclusion.
Which sort of makes respect them, after all, I'm only one of nearly 200 million Android users!
Click to expand...
Click to collapse
I'm almost surprised it took so long for them to notice that trend, considering they surely have facilities to notice trends in their databases. Score one for XDA! (Very cool of Google to provide such tailored support, though!)
So, no "permanent" dpi change solution for now?
I kinda missed my streak because of this high DPI on the SGS2. Everything getting so big, i losed some of my productivity...
schizo said:
So, no "permanent" dpi change solution for now?
I kinda missed my streak because of this high DPI on the SGS2. Everything getting so big, i losed some of my productivity...
Click to expand...
Click to collapse
To "permanently" change your DPI to "XYZ", add these lines to /data/local.prop:
Code:
ro.sf.lcd_density=XYZ
qemu.sf.lcd_density=XYZ
(Note: If /data/local.prop does not exist, you may create it yourself.)
- OR -
If you would prefer that the change not persist when flashing a new ROM, you could edit /system/build.prop, which should already contain the "ro.sf.lcd_density" property unless you're on a 160dpi device. /system/build.prop will be overwritten any time you flash a new ROM, even if you do not wipe first.
Both of these methods will require a reboot for changes to take effect.
---
Alternately, if you would like to avoid editing system files by hand, there is an app called Blade Buddy which allows you to modify various properties in /data/local.prop, including LCD density.
To save your changes from Blade Buddy, tap Menu -> Save. If you choose not to reboot, you can then tap Menu -> Apply to apply the changes in RAM and restart the UI to see them in action. (Applying density without rebooting seems to be hit-or-miss.)
---
Regardless of how you set your LCD density, the Market will exhibit the incompatibility bug.
As a workaround, I have set my density "permanently" with Blade Buddy and use LCDDensity for Root to revert to default once and a while, so I can launch the Market and get all my updates. LCDDensity for Root is designed specifically to change density temporarily, on-the-fly, and on as many devices as possible.
Thanks, Mr. Bezeek. Actually what I'm looking is the permanent solution of not having to temporarily switch back and forth. As for editing .props I already have experience before with my Streak. Hehehehe
But still, thanks anyway and hope you not offended. I like it the way you help others in precise and detailed manner. Keep it up, bro *thumbs_up*
Not a problem, just doing my bit to make sure the information is out there.
As far as avoiding the temporary switching goes, I'll be on vacation for the next week, but I intend to try a little hacking when I get back, to see if I can find a way to spoof the dpi. That is, if Google doesn't throw us a bone in the meantime.
Users have reported that older versions of the Market still work. The one shipped with the latest OTA for my Evo worked for me, and I suspect that any version released before they changed the Market UI will. YMMV.
Just thought I'd toss this out there... I have a Droid X. When running MIUI 1.8.19 on it, I don't have this problem. I can set my density to 200 and the newest market (3.1.3) still works as expected. Seems as though with all the other ROMs I've tried (both blur and 2nd init), I couldn't access a lot of stuff unless I set density back to 240. I can't remember for sure, but I might have been able to set stock .602 (rooted) to 200 with no problems as well - but I'm a little iffy on that. So it would seem that MIUI has done something (perhaps not intentionally) to work around the problem. I just wish I had the smarts to figure out what that might be.
Edit: I realize that this is not a Droid X forum, but I was thinking this info might help somehow. Thanks.
tslovejoy1969 said:
Just thought I'd toss this out there... I have a Droid X. When running MIUI 1.8.19 on it, I don't have this problem. I can set my density to 200 and the newest market (3.1.3) still works as expected. Seems as though with all the other ROMs I've tried (both blur and 2nd init), I couldn't access a lot of stuff unless I set density back to 240. I can't remember for sure, but I might have been able to set stock .602 (rooted) to 200 with no problems as well - but I'm a little iffy on that. So it would seem that MIUI has done something (perhaps not intentionally) to work around the problem. I just wish I had the smarts to figure out what that might be.
Edit: I realize that this is not a Droid X forum, but I was thinking this info might help somehow. Thanks.
Click to expand...
Click to collapse
Good to know! Being able to compare a "working" ROM to mine will surely make it easier to identify a workaround.
Nice info never noted this before!! yeah i dint get any updates over a last few weeks. Im at 200 dpi.
I've been switching back to 240 periodically to get updates, not a big deal to me, but would be nice if things worked normally. My only real issue with running lower dpi (160 here) is that some apps don't scale properly. IE the Dialer.
blackspp said:
I've been in touch with Google the past few weeks cause I hardly get any updates through the market since about three months.
Google noticed that everybody or at least most users with a non-standard screen density have this issue. Many apps give a 'your device is not compatible with this application' error when browsing the internet/desktop market version (not the phone market app).
And than in the market you won't see your apps under 'My Apps'
When you switch back to 'default density (240) the problem is gone.
Google is investigating the issue but does not know yet if they will support non-standard densities.
If this is a double post, sorry for that.
Click to expand...
Click to collapse
Thank for this information! I've been wondering why some standard apps weren't compatible.. It's weird, since they work if you side load them ...
I hope google finds a solution.
---------- Post added at 02:59 PM ---------- Previous post was at 02:51 PM ----------
I just switched from 190dpi to 160. Angry birds seasons is now compatible( wasn't with 190dpi)
Dank U vriendelijk
Wow. This has been driving me crazy trying to work out why apps where missing. Guess I need to swap to 240 occasionally for updates.
I am using 200 / 192 DPIs from day one. (3 months). its working fine.I never faced incompatibility issue with market. however some games doesn't run correctly which usually i don't play.
i have a workaround idea, and i started a thread to discuss here: http://forum.xda-developers.com/showthread.php?t=1288150
The google support thread for this is here: http://code.google.com/p/android/issues/detail?id=19744#makechanges
I still have this issue and if you do a web search you'll see that many still do. Reply in the support thread to raise awareness ! or if you have a workaround please share You also might want to check out his Idea thread, if you have some developing skill please help.
schizo said:
So, no "permanent" dpi change solution for now?
I kinda missed my streak because of this high DPI on the SGS2. Everything getting so big, i losed some of my productivity...
Click to expand...
Click to collapse
I came from a streak as well and it's this is the biggest annoyance I've had with the sgsii.
The reason why i enjoy Android over any other mobile OS is because i can tailor the OS to how i want it. Not allowing me to download apps because I'm using a non standard density is crippling.
For now, i urge everyone to go to the google support thread and simply press click the star. No need to comment (unless you found a fix), the more stars the issue gets, the more likely Google will look into it.
Seems to be fixed with the latest market version.
Sent from my GT-I9100 using XDA App
Ke11ett said:
Seems to be fixed with the latest market version.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
yeah i seem to be ok ive just got the version from androidpolice last night. im on 3.3.11 now, still cant install stuff from the website though says my phone is incompatible for everything lol
Hey,
I didnt know where i should Post my Bug Report so if its the wrong section dont hold back to tell me.
I'm currently using my Galaxy S2 for daily use and after flashing some Kitkat Roms Omni is in my opinion the most stable rom and with Nova + ART a damn fast Rom, so thank you very much for supporting my Device.
I dont know whats happening the last weeks but it all began with an Opendelta Issue, i wiped all Data / Factory Reset via TWRP and flashed the Rom completely new and OpenDelta still didnt work, it just said every day its all up2date. Now after a couple of days it is working again, dont know if it was a Server Issue or something else - at the official Omni Page no one post News so i have always to guess whats happening
Currently i found 2 Bugs, if you want to call someone you open up the Dialer and then the Button for the Numbers but after clicking it, theres nothing(Screenshot is attached). You have to go back and try it again then the Numbers are there. The second Problem is that there is no Zoom in the AOSP Camera App if you record a Video. My currently workaround is the Google Camera App, there all is working fine. Also there are some Issues with Apollo , freezing , doesnt update the Song DB etc. , dont know why its so popular - its horrible. Replaced it also with a 3rd party App - Omich/Rocket Player.
The last Problem is that not everywhere in the Settings the correct language is used, if you need some translation help im sure many users would like to help(including me) but that is in my opinion nothing critical .
...and sorry if my Text was hard to read, its not my native language but im working on it :silly:
Regards
Per the FAQ, this is not the place to put bug reports.
However, I9100 hasn't been maintained in a long time, so filing a bug report will be a waste of time. Support for this device is currently going to be dropped with Android 5.0, and if it receives 4.4 bugfixes, that'll have to come from a new maintainer as none of the former maintainers have time/motivation for the Exynos 4210 devices these days.
Some of the issues you describe with Apollo aren't Apollo issues, but the result of a very deep-down core bug that has a side effect of screwing up storage access. This bug has been known for nearly a year (there's a big thread disucssing it somewhere around here...) and still no one has found a fix for the root cause. In fact, it's one of the #1 reasons the device is getting dropped for L. (It will absolutely not receive nightlies unless someone finds and corrects the root cause.)
Hey,
Thank you for your response. :good:
I reported the Bug on jira and there is a workaround for the Dialer Bug: Setting The Animator Scale higher than 0.
The Drivers are the problem right?
pfxandroid said:
Hey,
Thank you for your response. :good:
I reported the Bug on jira and there is a workaround for the Dialer Bug: Setting The Animator Scale higher than 0.
The Drivers are the problem right?
Click to expand...
Click to collapse
Well, there are three things you listed:
1) Dialer stuff - probably some sort of odd HDPI issue and/or graphics subsystem stuff. The Exynos4 graphics subsystem is why many developers don't want to ever touch the platform again.
2) Zoom in video - What resolution was Google Camera? Zoom has NEVER been available for 1080p resolutions on the Exynos 4210 family, not even stock firmware will zoom in 1080p
3) The storage issues are a symptom of a deep-down kernel bug that no one has found the root cause of. This is the #1 reason the device is getting dropped for 5.0 - there is no chance even if a new maintainer steps up that nightlies will resume until someone tracks down the root cause of this one. http://forum.xda-developers.com/showthread.php?t=2612329 has more discussion (warning: It's long...)
Modifications for stock 4.4.2
drakeheart77 said:
Modifications for stock 4.4.2
Click to expand...
Click to collapse
I have found that custom ROMS/Kernels and much else for this phone to be sorely lacking. This is by no means an attack on my respected dev peers, simply an observation.
Throughout the woes of our limited forums I see a trend in the gripes about this little wonder.
I am offering my personal settings & preferences that MAY unleash what we can do here.
FIRST THINGS FIRST- Just forget needing buggy builds of TWRP for KK+ rom flashing. There's not much to flash, and TWRP 2.7.1.0 forced me to dl the KK stock firmware & start from square zero.
*NOTE FOR REASONS STILL UNKNOWN EVERY SINGLE PARTITION WOULD RESTORE- EXCEPT THE SYSTEM.
Enough said.
I am using CWM 6.0.2 for stability reasons, and have no issues.
Now I will begin the good stuff.
After my mods/tweaks etc, I am running about 97 apps with 3.9GB internal memory remaining, can go about 11hrs without needing to charge, give or take, and can multitask seemlessly with around 410mb free RAM at stationary.
Obviously, one needs to utilise the KK SD card fix. After this, begin:
Install /system/app/mover from Play Store & BE CAREFUL!!
I proceeded to begin moving bloatware preinstalled apps from being system apps to User apps, freeing essential system rom space & allowing for safe uninstall and transfer to ext sd.
Now on to build.prop.
Unleash what we can do here.
Here is the link to my build.prop zip. Please note all mods & adds specifically, as they are unique to the likings of this phone.
https://docs.google.com/file/d/0B-a-fg6mIteHakZfYXk1eklla3M/edit?usp=docslist_api
Next, I HIGHLY suggest the Override DNS for KitKat. Only one that works for 4.4 & above. Set to Google, which is also feasable in bud.prop, but my experience has been iffy with that, and this app flushes DNS cache w/o reboot and sets DNS KitKat specific.
GPS- FasterGPS.
Here is the link to the Advanced Settings data after basic configuration. The results speak for themselves.
https://docs.google.com/file/d/0B-a-fg6mIteHellndldvUG5Eb1k/edit?usp=docslist_api
Dl and rename to .txt to view.
I use RAM Manager Pro for memcleaning & management.
Use default option, the select custom afterwards to fine tune settings to preference.
If ANYONE needs recovery files for any soft brick needs AND has CWM, please PM me & I will upload mine.
Hope this gives some insight on how to begin using this guy properly.
Open forum. Ask/request away, add to it please!
Screenshots
RAM Manager Pro Custom settings that I use:
NOTE: Notice custom launcher in screenshots- by using /system/app/mover to convert Touchwiz to user, I freed up substantial rom space, mem, and performance. I use Apex Pro.
App Tools
Link to some utilities
Dl, unzip, rest is easy to figure out.
https://docs.google.com/file/d/0B-a-fg6mIteHeXowU1hTakRrZTA/edit?usp=docslist_api
I've begun modding my stock sgh t399 and I was wondering if u could talk with me a lil. I've seen massive potential over cost n this phone. Mainly don't understand build prop yet. Don't wanna brick it
Sent from my SGH-T399N using xda Forum
drakeheart77 said:
Screenshots
RAM Manager Pro Custom settings that I use:
NOTE: Notice custom launcher in screenshots- by using /system/app/mover to convert Touchwiz to user, I freed up substantial rom space, mem, and performance. I use Apex Pro.
Click to expand...
Click to collapse
You guys are in luck. .. the gods had pity and sent someone to steal my galaxy s3 and 5 and Tablet 7.0... so, I ended up with this phone. . But there's little to no development, especially for the metro variant. .. sooo... I'm doing a little work. ... look up .. team rejects.... you'll understand soon. ..good things coming. .
timmetal6669 said:
You guys are in luck. .. the gods had pity and sent someone to steal my galaxy s3 and 5 and Tablet 7.0... so, I ended up with this phone. . But there's little to no development, especially for the metro variant. .. sooo... I'm doing a little work. ... look up .. team rejects.... you'll understand soon. ..good things coming. .
Click to expand...
Click to collapse
Unjustified Dev is working on CM12 for this phone, but he's pretty much the only one. Whether you team up with him or you work independently, it'll certainly be good to have more people working on this phone. Bummer you had to lose your other devices though.
A different route
Hey all, thanx for the attention & activity in getting this thread moving.
I readily & always tell all I am not a Dev, I assist true devs here & there to work towards
stables, patches, fixing kernels, and so on.
That's out of the way, now on to the progress.
I have been using an AOSP deodexed stock 4.4.2 ROM, and praises to the efforts of
the community member, and much to my discredit I can't readily recall who this person
is to post a link to that thread, as is proper. oh well.
While the AOSP stock build is a big showing of progress, I say with a heavy heart that
it is very, very buggy.
What the positive effort was: It is debloated to such a level that upon a fresh install,
the user still has 4.2GB Internal Storage.
This, I've found, is the single most common misdirected goal and focus of efforts with
throw-away-yet-kinda-quality nocontract phone.
After I installed TB Premium, I discovered that the system ROM had around 182Mb available.
I now come to reports.
Every Stock 4.4.2 system app was still there, however the writer replaced a few (ie Camera
with Google Camera, for one) that completely eat up what precious limited RAM/
ROM performance we do have.
The build.prop showed only a few mods/edits, less than five.
The dalvik.vm.heapsize was 128m, heapstart was 8m, and growth limit 256mb.
That was same as stock. Speaking only for me, that was the biggest oversight that
tainted almost all efforts. Those sizes are entirely TOO big for this phone's britches.
If I seem like I just will not stfu, I can't blame you.
I feel I have to be as thorough as possible out of respect for my colleagues.
Now, since I am using Chrome from my device for all of this, you all will find up look oads
and images following this reply, fyi.
My first inspection was to install SetCPU, in small hopes that a customized kernel
had magically came. I am BEGGING for more governors and I/O schedulers, our less-than-
primitive 5/3 is downright insulting.
Kernel supports absolutely no tweaks, VM swap, O/C or min freq. U/C.
My goal is to take the only alternative given on 4.4.2 at all, and make lemonade.
System/app mover from Play Store.
There are countless threads on what is & isn't safe, my mods on that are my prefs.
In the end, I was able to free ROM up to just over 406MB. I can't begin to describe
the difference.
On to build.prop
To compliment my new device I just got, I set dalvik.vm sizes to a less audacious level.
I chose the more conservative of 8m, 64m, 128m. *Note any less on any 3 values, your FCs
will never cease.
Next, I made a few other edits I've favored on several devices, will upload my .txt.
Use of SD Fix for KitKat, along with Force2SD paid, I have 104 apps, many being very large
games, as well as the evil Chrome and FB storage rapists, all Google offenders at that.
I have a smug 4.32 GB Internal Storage available, saving me much embarassment by killing all my ROM wins.
AdAway 2.9 for KitKat, Override DNS for Root Users, the ONLY DNS mod that works on
KitKat, FasterGPS, Seeder 2.0, Root Explorer paid, TB Pro, NG Cache Cleaner, SignalGuardPro
and SD Booster make up my arsenal.
Touchwiz & Trebuchet are gone, I use Nova Launcher Premium.
Restoring TB app backups from external SD put my phone into bootloop.
I am clueless as to any reason why.
Using ANY root sysApp delete to debloat will also softbrick.
System/App Mover seems to be the only way. I speak from a few experiences and Nandroid
system part. restores.
I COMPLETELY CONDEMN MY PRIOR CONVICTION TO CWM.
I completely f*"$ed that up.
TWRP 2.8.0
NOTHING ELSE.
I even attempted a rash Aroma Installer to compensate for MusicFX being gone.
Ac!D Sound Mod.
Worked. And Improved.
RAM Manager Pro is gone too. I've found my build.prop edits are just right.
Any app tweak mucks it up.
Battery Callibrate Root, free on Store. Another win on battery life.
This is the most I can really do now.
Without a custom kernel, we'll be left behind like nearly all Prepaids, non flagships.
That's MY report, I beg for input/feedback/comments/criticism/ridicule, whatever.
Next Replies will be build.prop.txt, gps.conf, screenshots.
Follow up links scrnshots
My modded gps.conf, using FasterGPS
https://docs.google.com/file/d/0B-a-fg6mIteHellndldvUG5Eb1k/edit?usp=docslist_api
My build.prop txt
https://docs.google.com/file/d/0B-a-fg6mIteHWEd1U2pFNUJ5emc/edit?usp=docslist_api
some srcnshots are attached as well.
Plz PM or Reply if I can provide anything else.
DISREGARD BUILD.PROP UPLOAD FROM PREVIOUS.
I missed some critical errors & edits that will negatively impact the phones performance and memory allocation, dang my bad all!
I've been at this phone non stop it seems since my previous post. Need to be less trigger-happy with reporting progress smh.
I'm uploading what I promise is my finished build.prop, for real this time.
Since I am sticking with this stock AOSP build, I was able to successfully flash an Aroma recovery installer mod, the Ac!d Sound Engine.
I should note that the only EQ offered that will work is Nooxide. Awesome Beats EQ is not designed for 4.4 platform.
The Ac!d enhancement and Dolby Mod both have made positive enhancements.
The Play Store that is built in to the .zip install MUST be replaced. Initially the writer included that Play Store will FC upon install, but clearing cache/data in app manager would fix, and was correct.
I can't assume that I'm the only one who has caught this, but I am reposting in writer's thread that Play Store will update to 5.4 build, and it becomes all but unusable.
Any Play Store update beyond 5.2... has never functioned properly for me, it seems Google is making a path for Lollipop migration, and the Play Store versions 5.3 and above are, I believe, geared for 5.0 platform, but still giving it to 4.4 users.
I downloaded a Play Store 5.2 apk from a third party site, saved to my external.
What I now believe is the present solution to this situation is this;
Get 5.2.** apk, keep it on External, or readily available.
Get System/app mover
Root Explorer
After flashing, use System/app mover, and convert Play Store from system to user app.
Reboot. Uninstall Play Store as regular user app. Install 5.2.** apk. open System/app mover & convert Play Store to system app. Hit "cancel" on reboot prompt in app. Go to app manager, Google Play Services, clear cache and ALL data under "Manage Storage". Then reboot.
This has fixed, for good, my issues.
As stated before, use System/app mover at your own discretion and what is your preference, just make a backup first and understand what you are doing.
I am satisfied with what I've worked out, and do not have any other work to do that I can see.
Thanks all.
Next reply is RIGHT build.prop
apologies again.
Drakeheart77
https://docs.google.com/file/d/0B-a-fg6mIteHU081Uko0MU9ENms/edit?usp=docslist_api
Update- have recently corrected setting dalvik heapsize and limit to lower settings, causes many MANY problems, fc's etc.
Set to 8m, 64m, 256m.
Absolutely primed.
Further system mods gave me 433Mb free ROM space, and around 4.1Gb internal storage free.
Happy thus far.
If anyone is keeping up on CM12 build, share to this forum please.
I wish to aid the dev in any way possible.
drakeheart77 said:
Update- have recently corrected setting dalvik heapsize and limit to lower settings, causes many MANY problems, fc's etc.
Set to 8m, 64m, 256m.
Absolutely primed.
Further system mods gave me 433Mb free ROM space, and around 4.1Gb internal storage free.
Happy thus far.
If anyone is keeping up on CM12 build, share to this forum please.
I wish to aid the dev in any way possible.
Click to expand...
Click to collapse
I am using the CM12 build and its pretty good. If you havent tried it yourself you should its pretty stable. I do like to see that you are working on the stock rom though. I like that one too just too much bloatware and not enough free space, so this is good!
I've tried keeping tabs on that here & there, can't seem to find dl link for latest/stable build. I've given up on this stock ASOP, just flashed back to stock 4.4.2. Added all those mods I've been posting, runs 110% better.
Would you be so kind as to point me the right way to dl this CM12? I'm looking again, but it would help a lot lol.
Ty for your participation.
drakeheart77 said:
I've tried keeping tabs on that here & there, can't seem to find dl link for latest/stable build. I've given up on this stock ASOP, just flashed back to stock 4.4.2. Added all those mods I've been posting, runs 110% better.
Would you be so kind as to point me the right way to dl this CM12? I'm looking again, but it would help a lot lol.
Ty for your participation.
Click to expand...
Click to collapse
Here's a link to the cm12 development thread http://forum.xda-developers.com/android/development/dev-cyanogenmod-porting-t2918432
And here's the link to unjustified dev's samsung galaxy light folder that has the latest cm12 build http://forum.xda-developers.com/android/development/dev-cyanogenmod-porting-t2918432
Thanks
Ty I actually found it shortly after I requested that from you.
Been running it since then, a LOT of trial-and-error runs, but I've
managed to get it running just right for me, almost...
Fixed constant soft reboots by setting location to device only
Have no issues at all with phone calls, only the persistent
proximity during a call, I must position my phone a certain way,
my cheek kept touching the speaker and mute icons.
Any advice on that is welcome, I've tried the build.prop edit:
ro.lge.proximity. delay=25
mot.proximity.delay=25
without much luck lol.
And, the MMS issue. I'm on MetroPCS, so I have set the default
APN accordingly.
After researching CM Mod forums & searches, the only
solution anyone has ever provided is to use third-party SMS,
Textra was the specific example.
It seems to be arbitrary, I've had continuous successful deliveries,
then shortly after they fail every time..rebooting has AND has
not fixed this...too random of success/failures to pinpoint myself,
but I by no means am a master at this ☺.
Any help or ideas are most welcome!
Did you clean install? I set my APN to metro fast or whatever its called and have had no problems with texting. The only issues I have other than the proximity that you mentioned, is that videos don't always play. Plus the newest Netflix doesn't work and neither does play TV and movies. Both force close when I try to open
Sent from my SGH-T399N using XDA Free mobile app
Yeah when I had cm12 installed I had no problems with mms after changing the apn to metropcs lte or whatever it's called.
Well, I've since returned to Stock KitKat w/ root & modifications. The Cm12 was nifty at first, but in the end I desire functionality over custom.
Too many apps/features that I want & use often just didn't work unfortunately. Oh well, I'm still willing to pitch in & help out devs!
Maybe you could help develop the cm12 rom. Unjust lent his galaxy light out, and idk if he got it back yet
Sent from my SGH-T399N using XDA Free mobile app