Database Users

CyanogenMod MMS not resizing photos

I was told in the main CM thread that starting a new thread about this issue specifically is more likely to get attention, so here it is.
In the last 4 version of CM on my Nexus One (5.0.5-5.0.5.3), the MMS app is not resizing the photos taken with the camera app. When I go to get details on a photo that MMS is trying to send, it shows that it's anywhere between 600kb and 1000kb, clearly too large to send through AT&T. When I flash back to the stock rom, the MMS app resizes these same photos and they go through every time.

I tried sending an MMS earlier today with no luck, I'm on 5.0.5.2
I thought it was something i was doing wrong :/

I have the same problem
I guess we'll have to wait for 5.0.5.4...

I have the same issue. The only workaround I found was to use Handscent SMS instead of the built-in messaging app.

mindfrost82 said:
I have the same issue. The only workaround I found was to use Handscent SMS instead of the built-in messaging app.
Click to expand...
Click to collapse
This is what I'm currently doing. Two things that suck about Handscent (from what I can tell). 1) It compresses the pictures to VERY small, so they actually look pretty lousy on a phone with a high resolution display. I think it compresses them down to 11kb. 2) Handscent doesn't send video.

This has been an issue with CM since the initial release. i switched to using Handcent as well.

Have you gone to the Settings menu in the Messaging App? From there go all the way to the bottom and Select Custom User Agent. Try selecting different ones and see if that changes anything.

importflip said:
Have you gone to the Settings menu in the Messaging App? From there go all the way to the bottom and Select Custom User Agent. Try selecting different ones and see if that changes anything.
Click to expand...
Click to collapse
I have tried all the user agents, none of these settings affect the size of the file being sent so it does nothing for this problem.

Any luck using chompsms?

i've had trouble with both reg message app and handcent....just reporting...HAHA

uh yep. same problem here. super annoying.

hopefully Steve has seen this and will look into it. I have played around with it a lot over last two days. It seems very random, works, then doesn't. I dunno....See if Steve mentions anything in next ROM update changelog, lets all hang tight, he's never let us down!!

chompsms has worked best in resizing mms and such
much prefer it to stock and handcent overall in use as well

I don't think this has anything to do with the CM ROM as I get the same on stock and from what I've read everyone seems to have the same issue.
There are other posts on here about this as well as on Googles Nexus help forum.

I struggled with the same issue. Firstly, as already pointed out, this is not an issue with Cyanogen, its the stock SMS app that is the culprit.
The solution is to edit your Mms.apk and hopefully Cyanogen will implement this fix in a new version.
Just use whatever binary editor on your OS to edit mms_config.xml which is in mms.apk. The limits are clearly visible as ASCII text in there. As the limit is 1048576, you need to make that 0307200 to be on the safe side. I also edited the resolution, 1024x768 would seem plenty for an MMS. The result is that out going messages here are around 100kb when resized and it never hits that 300KB limitation.
So start with unzipping the Mms.apk, then edit the file called mms_config.xml, and just zip it back up again.
Again, hopefully this fix can be implemented in the next Cyanogen version

cyanogen said that hes thinking about making the messaging app be configurable so we can choose which size the app does.
thanks for the tip Untouchab1e, but when i tried to unrar the file opened the xml file, edit with dreamweaver, changed the file size and the resolution (i did 800x600 though), but i rar it back up and rename to apk. Doesnt work. Am i doing something wrong?
EDIT
Well my current workaround for now is, download picsay (free) from the market, open picsay, tap get picture, open the picture you want, hit normal, hit menu button when the picutre is showing (menu on the 4 keys at the bottom) hit export, tap on save to sd card. after the picture has saved, open messaging app, attach a picture, open the picsay folder, select the picture and send. delete the picture from picsay if needed.

Any kind developers willing to recompile the Mms.apk with the edited xml file? I changed the file myself with the recommended settings, but I haven't the programming background to even begin to understand the process of putting the apk back together (everything I read about it gave me a headache).
Here's the zip file that contains everything, which technically just needs to be converted into an apk.

+1 here.
This is the biggest Problem for me with CM-Rom...
Its impossible to take a Picture and send it via MMS.
Iam 100% sure that the Picture-Resizing is working on Stock-Rom.
Please dont get me wrong, iam really happy with CM's Rom but iam wondering why Cyanogen didnt fixed this since the first release because its something like a "Basic-Feature" but it seems to be more important to have fancy color LED-Notifications...
Cyanogen, please fix this soon

It appears this is fixed in the upcoming 5.0.6 ROM, or at least it is in the test version.
You can also push the older 5.0.4.x version to get it working in 5.0.5.x, instructions are here.

I have a feeling that these settings only affect those using the Nexus One on AT&T, and since CM's ROM's are used by people in numerous countroes and various networks, it would make sense to keep it open for those carriers to allow larger pictures. That's just my guess though.
I tried 5.0.5.6 briefly just to test this and the results seemed to be the same. I'm going to try pushing the older version, but I don't want to lose the black background. I think it's slick.
Edit: Just reverted to the 5.0.5.4 MMS file as posted above without theme options and it's still not working. I also forgot that the old and stock version of this app have that inconsistent behavior when pressing the back button (sometimes you load all threads, sometimes you get kicked back to the home screen). Nandroid restoring now...

[REQ] Custom rom for high pixel density

I'm finding the standard LCD density too small and prefer a setting of at least 200 on my Streak. I also find that 3rd party widgets tend to look better on a setting of at least 200 and best on 240.
Only issue I have is various stock apps no longer look right at the higher setting e.g. the Gallery doesn't display the buttons at the top correctly, the dialer shortcut doesn't appear correctly in the Stage launcher, when receiving an incoming call in landscape mode the number is not fully visible, dialer looks weird and I'm sure I will find more things.
Basically, the two biggest annoyances for me are the dialer and the gallery. Can versions of these apps be baked into a rom that is designed to be used at the higher LCD dencity?
THANKS!!!
Krisbo

agreed the high density looks very sharp, I like it.
but trying to enter text in some fields, you cant even see the input field, Dialer incall buttons and contact names become b0rked, among other things,
Can anyone fix this so they dont get so blown out of proportion?
Thanks. The highest I went is 200, but back to 160 on djsteves 1.5.1 because of issues mentioned above.

I do believe you'd have to open up each apk and completely redo all the graphics so they don't look out of proportion blown up. I guess all you'd have to do is make them all smaller but it will probably be much more complicated than that!
So yes, it can be done. But i doubt anyone will do it.

Could you copy an apk from another phone with a higher pixel density? E.g. nexus one I think has 252ppi.

nexus by default is 240 yes, ill have a look at doing a 1.5.1 huge version wen i get a sec

You are awesome!
Could you possibly make it no baseband because I use a rebel sim?
Thanks

Before flashing the zip, unpack the whole thing and open system/build.prop with a text editor (like notepad or your favorite IDE). Then search for "ro.sf.lcd_density=160" and change it to a value you like. Save the file and repack it into the zip file (with WinRAR for example). Flash the ROM using StreakMod or ClockWorkMod and have fun with it!
Another option is to get Root Explorer - or a similar program - and go to system/build.prop. Set the permissions to r+w. Now you can edit this file using Root Explorer or copy it to your MicroSD and edit it like I said before. After the edit copy it back if you have too or save it. Then set the permissions back to r+o and reboot.
I have mine set to 220, which is a great size but I guess 200 is nice too!

alex3305 said:
Before flashing the zip, unpack the whole thing and open system/build.prop with a text editor (like notepad or your favorite IDE). Then search for "ro.sf.lcd_density=160" and change it to a value you like. Save the file and repack it into the zip file (with WinRAR for example). Flash the ROM using StreakMod or ClockWorkMod and have fun with it!
Another option is to get Root Explorer - or a similar program - and go to system/build.prop. Set the permissions to r+w. Now you can edit this file using Root Explorer or copy it to your MicroSD and edit it like I said before. After the edit copy it back if you have too or save it. Then set the permissions back to r+o and reboot.
I have mine set to 220, which is a great size but I guess 200 is nice too!
Click to expand...
Click to collapse
I think we understand that, the issue we have is that anything higher than stock 160 and apps get blown out of proportion, escpecially phone app for me, 180 is the highest /usable/ for me. I would love to have to cranked to the max, after owning an iphone 4 for a while, sweet display; but software is too simple.
Thanks DJ_Steve for looking into this,
please see if you can sort out the blurry contact pictures in-call, they look horrible even on stock 160, is it just me?

chrisrotolo said:
I think we understand that, the issue we have is that anything higher than stock 160 and apps get blown out of proportion, escpecially phone app for me, 180 is the highest /usable/ for me. I would love to have to cranked to the max, after owning an iphone 4 for a while, sweet display; but software is too simple.
Thanks DJ_Steve for looking into this,
please see if you can sort out the blurry contact pictures in-call, they look horrible even on stock 160, is it just me?
Click to expand...
Click to collapse
Exactly. I'm running mine at 220 but if the phone happens to put itself in landscape mode while it's ringing (happens sometimes) I can't see who is calling.

sorry i don't get it. how is the pixel density supposed to increase if the resolution of the LCD screen is fixed (480 by 800 pixels, not one more not one less)? to clarify, I am not denigrating, I just do not understand

Very frustrating. I dont have "ro.sf.lcd_density=160" in my build prop. Im on official ota update from a couple days ago

Hi Steve,
Any news on this?
Krisbo

carhigh said:
Very frustrating. I dont have "ro.sf.lcd_density=160" in my build prop. Im on official ota update from a couple days ago
Click to expand...
Click to collapse
Me neither.
Sent from my Dell Streak using XDA App

deekdeek said:
Me neither.
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse
I don't think this line is in the stock build.prop. Just add it under #other edits. If that's not their either, look for either debug.sf.hw=1 or debug.sf.hw=0 and add it after that.

You can use Incoming Call Plus (beta) as a replacement for incoming calls. This works great and has no negative side-effects for me.

Krisbo said:
I don't think this line is in the stock build.prop. Just add it under #other edits. If that's not their either, look for either debug.sf.hw=1 or debug.sf.hw=0 and add it after that.
Click to expand...
Click to collapse
Adding it worked. Thanks, i can read more now

alex3305 said:
You can use Incoming Call Plus (beta) as a replacement for incoming calls. This works great and has no negative side-effects for me.
Click to expand...
Click to collapse
That's not bad although the answer/reject buttons are UGLY!!! Does the job though and I can see who is calling

Any progress Steve?

I took this Gallery apk out from the Cyanogen Mod HTC Evo zip. It should scale properly when you change your DPI although stuff becomes real small when you go back to stock 160 DPI. It also fixes the "this is an audio file only" or whatever the hell that is if that wasn't already fixed.
It seems Dell changed the DPI of the dialer and gallery app to make use of the screen real estate while also using 160 dpi for the rest of the system.

Tried that apk n didn't do **** for me but I might have done it wrong...no biggy 1.5.3 looks like it might have this area sown up
Sent from xda app Dell streak dj 1.5.2
1190=1861qrdnt

Adjust MMS compression settings

Anyone know if there's a way to adjust the mms compression settings? I use shootme to take screenshots and when I send them to friends, it's completely unreadable and blocky. I'm guessing because it gets compressed so dam much.

Some roms raise the mms size limit, that should help.
Sent from my PG06100 using XDA App

Hey guys, my fiance's Shift has somewhat of the same problem. She'd take a picture with every possible setting on 'high' and they look great on the phone itself. If you view the pics on a PC from the SD card, they look pretty good, too. The problem appears when she sends pics as mms to me or other phones (other 'droids, iphones, BBs...you name it): these attachments arrive in 'thumbnail' format! You can zoom in, but all the original quality goes down the drain
Shift is rooted and I flashed....don't remember what lol. I think it was the 'official' update...is it called AOSP? Sorry, kinda of a n00b here
Any ideas?

dragon_0n4 said:
Hey guys, my fiance's Shift has somewhat of the same problem. She'd take a picture with every possible setting on 'high' and they look great on the phone itself. If you view the pics on a PC from the SD card, they look pretty good, too. The problem appears when she sends pics as mms to me or other phones (other 'droids, iphones, BBs...you name it): these attachments arrive in 'thumbnail' format! You can zoom in, but all the original quality goes down the drain
Shift is rooted and I flashed....don't remember what lol. I think it was the 'official' update...is it called AOSP? Sorry, kinda of a n00b here
Any ideas?
Click to expand...
Click to collapse
Might want to try MikShifted G v1.76 or Supreme Sense v8 . Both have the MMS Compression settings adjustments your talking about. The pic quality is also great even when you send an MMS.

To add to prboy1969's point the you will probably need to be on a custom rom that has those settings tweaked. Although you should still be able to send a pic and have it come out ok on the other end.

[how to] More volume steps & Smooth scroll for stock 4.4.2

HOW-TO:

... reserved ...

Will try these than you.
Whatchu talking bout willis!

Guys, this appears to work very well on my Nexus 5 running SlimKat 7.8. I had some trouble, but when I finally managed to edit the files and swap out the framework.jar file, scrolling is out of this world!!! No more slow facebook scrolling, or laggy gallery scrolling. It is so good, that I am wondering - are there any drawbacks??? If not, why aren't all ROMs doing this by default. It's just great!!!
p.s. to the OP - Don't reference lines in the code!!! Lines in my file were different (for example your line828 to edit, on my framework was line850). Watch out for this guys! Just look at what you change, don't look at the line number! (e.g. not line828, but rather look for "setScrollingCacheEnabled(Z)V")

granets said:
Guys, this appears to work very well on my Nexus 5 running SlimKat 7.8. I had some trouble, but when I finally managed to edit the files and swap out the framework.jar file, scrolling is out of this world!!! No more slow facebook scrolling, or laggy gallery scrolling. It is so good, that I am wondering - are there any drawbacks??? If not, why aren't all ROMs doing this by default. It's just great!!!
p.s. to the OP - Don't reference lines in the code!!! Lines in my file were different (for example your line828 to edit, on my framework was line850). Watch out for this guys! Just look at what you change, don't look at the line number! (e.g. not line828, but rather look for "setScrollingCacheEnabled(Z)V")
Click to expand...
Click to collapse
Lines are referenced because the thread is named "stock".
You might feel its a little worse if you scroll one line at a time but flings should be smoother. Personally I feel no difference.
ふかつどう

I did everything as instructed for scroll mod. Apps didn't load. Nexus 5 SlimKat 7.9
any ideas?

Gcam recomendations for V35

Are any v35 users using a gcam mod? If so, can you share which one and your experiences?

Well for 5-th branch hands down the best one is GoogleCamera_5.2.025-Final_fu24-18c1.apk and can be found here
Regarding 6-th latest Gcam_6.1.021_Advanced_V1.7.190716.1800 by Arnova works flawlessly with this XML config.

On a project fi v35, the GoogleCamera_5.2.025-Final_fu24-18c1.apk was too laggy for me. I ran 01.MGC_6.1.021_G7_test_v1.apk and was able to snap pictures with front and rear, but the 02.MGC_6.1.021_BSG_Arnova_TlnNeun_04.02.19.12.54.apk crashed on launch.
Will post a logcat once i can.

Have you properly applied the XML setting (step 8) after installing MGC_6.1.021_BSG_Arnova_TlnNeun_04.02.19.12.54.apk?
Lag in viewfinder is cause by overloaded buffer in this version which is easily fixable either by applying XML as shown or by enabling the Buffer Fix switch in app Settings.

Nope, after installing the 02 apk, it crashes on launch so I don't get the chance. Tweaked settings w/ the other one and got it working at least, thanks!

You are welcome!
N.B.: If you want to have it working you need to follow the guide up to the letter, so whenever you get bored and want to try again just uninstall the current GCAM, restart your phone and start again.
Do not forgot to take again 2 pictures after installing 1st apk and to properly import the XML settings after installing the 2nd apk and starting it for the first time.

mcsterling said:
Nope, after installing the 02 apk, it crashes on launch so I don't get the chance. Tweaked settings w/ the other one and got it working at least, thanks!
Click to expand...
Click to collapse
Same problem, I can't do step 8 because the camera crashes when trying to open.

I have LG V30+ H930DS, and I use this two Gcams.
One is 90% wokring (maybe panorama doesnt work) but all other is perfect (wide, noraml, portrait front/back, HDR+, SlowMotion) and its fast. (To chagne between lenses, just hold switch button, it will redirect to settings, after you close settings lense will be changed.
The other one I use only for NightSight. This camera has problem with selfies, they have green tint. It also have Wide/Normal switch, ( just chage between selfie and back camera, and each time ju go back to main camera it will be diferent lense)
I'm satisfied with this phone, for me everything is perfect, but i found LG V35 for good price and I would like to konw if there is somebody with V35 who will try this two Gcams, and tell me does they work properly, or if there is some others which works good, because i wouldn't change V30 for v35 if I can't have good working Gcam.
https://drive.google.com/file/d/1PcSs31bSenYiC3At0p_1So6xpBA7SaGm/view
https://drive.google.com/file/d/1OsyM99VdOLjUMxRryoFtR15Wkqt6LSVG/view

Latest GCam with respective easy import settings can be found in one archive here

vlad48 said:
Latest GCam with respective easy import settings can be found in one archive here
Click to expand...
Click to collapse
Thank you for the link. I downloaded, installed and restored the supplied config file for my V35.
Regarding Night Sight, is there a setting to change to fix the choppy motion when moving around the viewfinder?

No way for now on improving Night Sight viewfinder lag.

vlad48 said:
Have you properly applied the XML setting (step 8) after installing MGC_6.1.021_BSG_Arnova_TlnNeun_04.02.19.12.54.apk?
Lag in viewfinder is cause by overloaded buffer in this version which is easily fixable either by applying XML as shown or by enabling the Buffer Fix switch in app Settings.
Click to expand...
Click to collapse
where is step 8 described? I can find no reference on how to apply this xml config.

Step 8 originates from really old installation guide.
Now you need only to install the camera apk and import the xml settings file.
Where/how to extract the xml file and how to import it afterwards you can check here

vlad48 said:
Step 8 originates from really old installation guide.
Now you need only to install the camera apk and import the xml settings file.
Where/how to extract the xml file and how to import it afterwards you can check here
Click to expand...
Click to collapse
Thanks. I must have been downloading wrong version, since double clicking didn't work. Tried again this morning and it works now.

After applying the xml fix to v6.1 camera, it works, but I wouldn't call it "good". It's super annoyingly slow to make pictures. 5.2 also lags substantially, and won't load xml settings. So far, lg camera is hands down better

so... MGC_6.2.030_MI9SE_V4_plus2.apk has been the only version for me that has worked without issue...problem is pictures are not clear. although the viewfinder is fixed with the buffer fix toggle, when taking photos its not quick therefore the pictures blur slightly.
do you all encounter the same and if not which version and configuration has given you a fast shutter?

Here is what I posted on arnova's thread with the suggestion of another member.
hachiroku said:
thanks...i Gcam_6.2.030_Advanced_BF_V2.2.1.190822.1145.apk works for my V35 as it seems BF means it has the buffer fix built in. shame it doesn't allow for zero shutter lag as for phones that don't need a buffer fix. as the OEM camera can take photos super fast.
here are my settings for my LG V35 on Pie on Gcam_6.2.030_Advanced_BF_V2.2.1.190822.1145.apk
back camera: Pixel 3 XL
front camera: Nexus 6P
AWBGains Mod: OFF, was causing GREEN photos with it on
RAW FORMAT: RAW_SENSOR
Image Format: JPEG (if i set YUV_420_488 GCam crashes)
P3 wide-color, Wide Color gamut
playing around with Custom Lib Repo by cstark and with Eszdman v2.6 beta 2
image quality is awesome, and no blur upon shutter snap as with other GCams! Thanks @arnova!
Click to expand...
Click to collapse

Hey everyone, I'm currently exploring some gcam options and I found that the latest Arnova Gcam works great with no lag (it does take a bit longer to capture a photo than it does on my sd820 device) but sadly it doesn't offer wide camera mode.
Now, there is the cstark camera and wide angle mode actually does work, but using the camera is impossible because the preview (you know, the thing you see on your screen before you take a picture) changes once every 5 seconds or something. I tried importing some xmls and that sped it up just a bit but not by much.
Is there some working version that was tested for v35? My v35 is Korean model

vlad48 said:
Well for 5-th branch hands down the best one is GoogleCamera_5.2.025-Final_fu24-18c1.apk and can be found here
Regarding 6-th latest Gcam_6.1.021_Advanced_V1.7.190716.1800 by Arnova works flawlessly with this XML config.
Click to expand...
Click to collapse
I get terrible stutter on the night site with this 6-th and the config file. Any fixes?

You need to be on Pie and you can use Gcam_6.2.030 with working Night Sight without lag.