After doing hours of searching and reading I found I'm not the only person that faces this issue, but many have solved this issue by editing the mms_config.xml inside res/xml/.
I've changed the "maxMessageSize" and also "maxImageHeight" and "maxImageWidth" to a variety of different numbers (up from stock 640x480), and it HAS made some difference, however neither max image size nor image resolution is being reached and my resulting MMS is still somewhat blurry. I recall fixing this issue fully for my S4 back in the day with 0 resulting blur but I must be missing something else in the apk here.
I'm thinking the uaProf and UserAgent strings may have something to do with it, but any strings I've managed to find via google make no difference at all to the size/quality of the outgoing MMS.
Looking for a native solution and not "use handscent/gosms instead" alternatives, seen these suggestions as "fixes" in almost every thread related to this.
If anyone is aware of anything else I can test or a different xml file in the apk that can be tweaked would appreciate it.
Carriers max MMS is 1.2MB but even 300-400kb images are being compressed to 70kb but like I said it has made a difference, just that the numbers I'm entering aren't being respected fully
Thanks
Meanwhile a friend of mine on the same carrier can send me a crystal clear image in almost 2k resolution from an iphone. Just standard MMS nothing 3rd party, if they can do it why should Google's official Android messaging app be so terrible to such an extreme degree. 640x480 found in the stock mms_config.xml is almost unbelievable when the network is capable of transmitting over 3x that resolution
Related
Hi Guys,
I've done some searching and cannot seem to find anything recent about this issue. I'm wanting to write a camera application that shoots and stores the raw camera data from the EVO.
It looks like someone has put together a class that will take the byte array and dump it to DNG format which would be ideal. However, when the callback fires, I get an empty byte array and a null pointer exception.
Now, I'm not sure it's a coding error because the jpg callback works just fine.
Some older threads seem to imply that the raw callback doesn't actually do anything. I think there is one where a google developer said they thought they should nuke it all together....but that was 2008, I think.
So can this callback actually do anything? Does the SDK from HTC give me lower level access to the camera? What are my options? I think the camera in the EVO is okay, but the jpg compression just doesn't seem good to me....
Thanks!
Crud, since I'm new I can't post a link to the google thread I was referencing above with the dev saying he'd like to deprecate raw, but the thread id is: 65191ea020f6bb27 if anyone is interested. But that was in 2/2009.....
It looks like the Android dev implies they might add or support native signal processing, which would be fine but I have no idea how one might accomplish this in Java....(isn't the point of java to work at an abstracted layer?).
Anyway, I'll amend my questions to include this: do any of the ROMs out there support either native signal processing or raw camera call backs?
Maybe this is something I need to take directly to google?
I know this has been discussed before as an issue with the 3G Slide but I'm wondering if anyone wants to try to get magenta to do something about it. With how much they advertise this phone and used it in everything that had to do with them why did they either not set a user agent for mms messaging, resulting in the server to default to the lowest setting or, why did they set it so low for our phone? My Blackberry 8900 sent pics well over 1MB just fine with no resizing (with EDGE at that) as many other phones do.
I've had enough of the 1KB - 25KB mms messages, sending and receiving. I know a few apps attempt to fix this but even with CM6 having that option built in - it still does it, as I'm sure many of you notice for large pics. So maybe we should do the same thing that was done with the source code and bluetooth code issue. Anyone up for it?
On a secondary note: In the mms.apk the UA is listed as: http://www.htcmms.com.tw/Android/common/mytouch3g/ua-profile.xml which has a max height/width of 480x640 and max size of 307200 (300K). If I replaced that with say: http://www.htcmms.com.tw/gen/HTC_HD2_T8585-1.0.xml with a h/w of 1600x1600 and size of 600K, would it work? Yes I know it's windows but that shouldn't effect the mms aspect.
mikechannon - if you will, please keep this open for a while and delete it at your discretion.
I have an issue with photos taken in dark conditions, they are all messed up, or broken if you will, looking like corrupted JPG. In slightly better light conditions everything is fine. Reboot did not help. It happens now with default camera in sebaastian15's AIO 2.5 but I have also noticed it in AIO 2.2. Is there a way to upgrade/replace stock (sense 3.5) camera? Did anyone experienced such an issue?
I could insert image of screwed up photo but "noobs" like me have no access rights, so to look at it, make up and URL from this "img43.imageshack.us/img43/3977/imag0616d.jpg" or that one "img838.imageshack.us/img838/5885/imag0610g.jpg".
Also do not ask me to ask this question on the ROM thread... again, I am just a dumb "noob" so I cannot comment on super-duper-exclusive dev threads.
-andy.
jedreg said:
...make up and URL from this "img43.imageshack.us/img43/3977/imag0616d.jpg" or that one "img838.imageshack.us/img838/5885/imag0610g.jpg".
-andy.
Click to expand...
Click to collapse
Unable to see these images.
same here
the same happened with me too
but on older versions of runnymede and runnymedemod007
mine even used to restart the whole phone
i suggest using market apps like camera 360 or others if you prefer
I was trying to avoid non-sense (hehe) cameras, but I will give it a try to be able to take night picture despite low quality... what I have noticed (but have to prove tonight) is that after I changed preferred ISO to 800 the picture taken is ok, and even when I set it back to "auto" - this sounds like ISO property is not really set and may mess up when pixel brightness computation in low light conditions (just a theorem).
ckpv5, I copied&pasted address to URL bar of web browser and it works for me, maybe you do not have access to imageshack server. When I reach "10 mails level" I will just embed it here.
-andy.
jedreg said:
ckpv5, I copied&pasted address to URL bar of web browser and it works for me, maybe you do not have access to imageshack server. When I reach "10 mails level" I will just embed it here.
-andy.
Click to expand...
Click to collapse
Yeah.. I guess it is no access as this is what I got http://imageshack.us/img/blocked_login.jpg
Anyway... your workaround on the problem is good.
Night test done... default camera screws up pictures unless you manually set ISO. Re-checking "auto" does not help, but setting 400 or 800 helped me to make couple souvenir pictures.
-andy.
Hello,
Does anyone know if there is a way to change the standard name format Google gives images: IMG_20160101_121728.jpg to something else like N5X_01Jan16_12.45.11.jpg? I found one app that seems to do this after the fact here: https://play.google.com/store/apps/details?id=ro.ciubex.dscautorename
I was just wondering if there was another native way in-camera phone to do it? Or is there another app some recommend?
Lastly, does anyone know what the last set of digits represent in the name? I know the first represent the date.
Thanks,
Derek
dereksurfs said:
Lastly, does anyone know what the last set of digits represent in the name? I know the first represent the date.
Click to expand...
Click to collapse
The time, in 24-hour format.
I doubt there's any way to change the name format. You could whip up a shell command to change them.
the standard camera app does not have an option for that.
also, as crachel pointed out, the second set of digits is the time of recording in 24h format.
this way the values are all ordered from largest to smallest (Y/M/D_H:M:S) and therefor will always be in chronological order.
as you see the file names include already everything you want (apart from the N5X part), just in numerical form, and in an order that is at least for machines easier to work with.
if you still want another format i'd be curious of what you would expect from that.
Interesting, when I looked at the last set of numbers, they did not match the timestamp of the file system. So I thought they were just random unique numbers. But if I look at EXIF data on Google Photos, the time looks correct. So, at least they provide more meaningful information than I initially thought. I would still prefer a more reader friendly format like the one I posted above for my own archival purposes. IMG is too generic as I have many cameras along with their associated images. I could care less what Google or anyone thinks is machine friendly. I program for a living and know user experience trumps whatever someone assumes is easiest on a computer. Plus, a computer can read any format since its simply a date pattern. I just prefer another pattern.
I've looked into the last 6 numbers too. In my findings it's the second when the photo/video was taken/started recording. Same for exif. The filesystem contains the second when it was finished written to "disk".
Also sometimes you get _1, _2, ... after that if more photo was recorded in the same second.
Hey guys,
So I'm enjoying my note 10+ so far, but I'm having an issue when trying to send live messages. The messages come out very compressed and after doing some research, it was advised to send them as mp4s instead of gifs. So I tried that, but it was even worse.
So I said forget it and that I would just send gifs like I did on my lg v30. But the same issue persists, even with tiny gifs. The gifs are severely compressed and washed out. I tried using the stock messenger, signal and textra, but they all seem to be exhibiting the same issue. Whereas on my v30, textra never gave me any issues and I could send very large gifs even with no problem.
My phone is an n975u1 us model that I purchased and imported into Canada, running xaa firmware and not xac. My apn settings are all fine, I can send and receive calls, etc. Does anyone know what's going on or have the same issue?
Here is a screenshot of the issue:
https://ibb.co/qd6zhgB
crushdancexz said:
Hey guys,
So I'm enjoying my note 10+ so far, but I'm having an issue when trying to send live messages. The messages come out very compressed and after doing some research, it was advised to send them as mp4s instead of gifs. So I tried that, but it was even worse.
So I said forget it and that I would just send gifs like I did on my lg v30. But the same issue persists, even with tiny gifs. The gifs are severely compressed and washed out. I tried using the stock messenger, signal and textra, but they all seem to be exhibiting the same issue. Whereas on my v30, textra never gave me any issues and I could send very large gifs even with no problem.
My phone is an n975u1 us model that I purchased and imported into Canada, running xaa firmware and not xac. My apn settings are all fine, I can send and receive calls, etc. Does anyone know what's going on or have the same issue?
Here is a screenshot of the issue:
https://ibb.co/qd6zhgB
Click to expand...
Click to collapse
There are limits to how big of a file you can send via MMS (or via RCS)... If the messaging application is compressing the image then the size of the file you tried to send exceeds the limit. With larger sized images/files the compression will probably be more aggressive (and more noticeable).
On my phone looks like the limit is 105mb file size for RCS messaging
I know that there are file limits. But I've never had an issue with this using the lg v30.
crushdancexz said:
I know that there are file limits. But I've never had an issue with this using the lg v30.
Click to expand...
Click to collapse
I can't tell you why brand X works and brand Y doesn't. Also in the same token it's not really conducive to finding out why your having (solving and/or identifying the cause of) image quality issues on a Note 10+ using a Note 10+ to send a mms image.
Try this to see if the file size limit is being enforced:
Reduce your image size to less then 105 megabytes and try again. Save the file and compare file size (refer to note 1 below)
Create an image file a little larger then 105 megabytes.. If the image appears normally then save it and compare file sizes (refer to note 2 below)
Create an image file like what you had before and send it. Save the file and view the file size (refer to note 3)
~Notes~
Compare the file size of what you received (with that of what you had sent) to see if it is the same size.
You are trying to see if anything a little over 105mb gets reduced in both quality and file size. Compare what you sent with what you received. If the file size of what you received is smaller then what you sent, then file size limits are being enforced
Again like above you are trying to see if the file size is reduced to 105mb or less. If the file size of what you received is smaller then what you sent file size limits are being enforced.
If file size limits are being enforced I am not aware of any method or way to remove or disable said limit set by the carrier. If you have a larger image you wish to send then you may want to consider alternative file transfer methods (Facebook messenger, email, etc)
scottusa2008 said:
I can't tell you why brand X works and brand Y doesn't. Also in the same token it's not really conducive to finding out why your having (solving and/or identifying the cause of) image quality issues on a Note 10+ using a Note 10+ to send a mms image.
Try this to see if the file size limit is being enforced:
Reduce your image size to less then 105 megabytes and try again. Save the file and compare file size (refer to note 1 below)
Create an image file a little larger then 105 megabytes.. If the image appears normally then save it and compare file sizes (refer to note 2 below)
Create an image file like what you had before and send it. Save the file and view the file size (refer to note 3)
~Notes~
Compare the file size of what you received (with that of what you had sent) to see if it is the same size.
You are trying to see if anything a little over 105mb gets reduced in both quality and file size. Compare what you sent with what you received. If the file size of what you received is smaller then what you sent, then file size limits are being enforced
Again like above you are trying to see if the file size is reduced to 105mb or less. If the file size of what you received is smaller then what you sent file size limits are being enforced.
If file size limits are being enforced I am not aware of any method or way to remove or disable said limit set by the carrier. If you have a larger image you wish to send then you may want to consider alternative file transfer methods (Facebook messenger, email, etc)
Click to expand...
Click to collapse
I sent a static jpeg and it went from 881Kb to 351Kb on the Note. On the V30 it was still 881Kb.
I really don't think this has anything to do with my network because the v30 on the same network does not do this. With *any* text program.
crushdancexz said:
I sent a static jpeg and it went from 881Kb to 351Kb on the Note. On the V30 it was still 881Kb.
I really don't think this has anything to do with my network because the v30 on the same network does not do this. With *any* text program.
Click to expand...
Click to collapse
What your LG can or can not do is not conducive nor helpful for what the Note 10+ is or isn't doing (and why). For example here's why it doesn't help...
What if a toggle exists on the LG phone that doesn't exist on the Note 10+? - You can't root the Note 10+ variant you have so you can't make a toggle appear without either the carrier enabling it (or an app that has it added).
What if the LG phone was provisioned differently then the Note 10+? - You can't make changes to the Note 10+ variant your using within regards to carrier provisioning...
What if an LG app allows larger files? - That's not gonna be of any help with a Samsung Note 10+
I did some research today on the subject and what I found across different providers support forums as well as Samsung support forums is that the issue is related to MMS limitations on image size. Yes some people mentioned that there "LG phone could do it" but it isn't exactly as simple as that. In some cases (whether phone, stock applications or within 3rd party apps) a setting exists which allows one to choose the quality of the image being sent. In your stock apps or 3rd party apps your gonna want to see if you can find this setting. If you can't find the setting then this means it isn't something you can change, and if this is the case then nothing can be done.
In my Note 10+ case I don't see this on Google Messages app nor my stock messaging app, so when I send a MMS of 240kb in size (or a test image that was over 2mb in size) it gets compressed. Again this isn't a phone issue, it is something that is set and controlled by my carrier... Which in your case I imagine your being effected by the same limitations.
Thank you for looking deeper into it. I read the same thing on the Samsung boards and across reddit as well during my research. It's just very frustrating because I really enjoy mms and sharing content with my friends. I was going to sell the v30 and keep the note, but now I'm not sure what to do. Even the edge lighting for the phone is broken and there's no real solution for that either based on my research. Yes they're different phones, but using the range app didn't even resolve the issue, on the same carrier. So what's the difference if not the phones? It just seems like Samsung likes saying this and that, but the features are half baked. I'd even trade gifs for live messages, but that's even more broken. Thanks again though for trying to help. You're a pretty cool person.
Hey, Crush. Just curious - what app were you using on the LG? If the same one on Samsung, was it the same version? If not, you could try exporting the APK from the LG and installing it on the Samsung.