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...

Reduce LCD Density Setting in Build.Prop For Higher Res Look

Update: I installed Spare Parts, as mentioned by appelflap later in this thread, disabled compatibility mode, then followed the directions in this post, and I have a working status bar, good resolution, and in a better place in most cases.
Update: Check out appelflap's APK that makes this whole process a lot easier. Note that some users are reporting a black screen after using the file, so be prepared in case you have to use adb shell to put your original build.prop file in place. If you do not want to risk it, Notepad++ makes for an easy edit once you pull the file to your PC. If you have fallen prey to the black screen problem, lpsi2000 found a solution that uses an update.zip approach.
In the /system/build.prop file, I changed this line:
ro.sf.lcd_density=240
Click to expand...
Click to collapse
to this:
ro.sf.lcd_density=160
Click to expand...
Click to collapse
This is a setting that Google normally recommends if you have a larger screen (like Dell's Streak), but the side effect of using it on the 800x480 screen of the captivate is that everything is smaller.
With this, menus have smaller text (more options on screen), in-app buttons are smaller, and it just has the same feeling of being on a PC and moving from a low resolution LCD monitor to a high resolution LCD monitor.
There are a couple of glitches so far. It appears that some apps want to render in the previous resolution. For example, Skyfire and Root Explorer would not render in full screen, Android Market renders full screen but the search is in the old resolution, and the status bar is slightly garbled but still usable. Also, the dial pad is smaller (as you would expect showing a picture made for a low res display on a high res display) but the rest of the phone app is fine. The camera app fills the screen just like it did before.
With this setting, I really feel like I'm getting some use out of the high resolution display on this phone.
The apps that are rending in the low res mode of the original setting seem to be pulling their setting from somewhere else. Does anybody have an idea where that setting may be? After trying this, I can't imagine going back to what almost seems like an "accessibility mode".
I've only used LauncherPro with this setting, so no idea how the Samsung launcher looks. I attached screenshots of what some things look like. I can put some game screenshots in another post if anybody is interested. 3D games look sharper to me in this mode, but I have no scientific way of testing if it is because it is rendering in higher res or if my own excitement is clouding my vision.
Update: I suspect the missing setting is found in the /system.prop file. It has the ro.sf.lcd_density=240 setting. I tried changing it to 160, but it keeps going back to 240 after a reboot of the phone. Any ideas how to make this stick?
Warning:: TWLauncher does not play well with these changes. Make sure to have LauncherPro set up as your default launcher before trying this.

So you're pulling it off the cappy then editing putting back....do you need to change permissions?

The way that I pulled it out to edit on my PC was with this:
adb pull /system/build.prop
Click to expand...
Click to collapse
You will need root access in order to put the changed file back. What I did was
adb push build.prop /sdcard
Click to expand...
Click to collapse
I then used Root Explorer to copy the build.prop from /sdcard to /system. I didn't change any permissions other than just copying the file and rebooting.

Wow man that's pretty cool, it's got a few little glitches but nothing serious. One of the things I wish I could so though is make my Beautiful widgets clock go all the way across the top. I'm not sure if this is a placebo effect (I donno if that's possible since this should have nothing to do with it) but it seems like my soft buttons respond more often....I'm prolly nuts but it doesn't seem like I need to push....push...%$^&*^ PUSH.....and back to home.

I'm hoping someone will have a great idea on how to keep the /system.prop file from updating itself on boot. I'm thinking that if we can get the ro.sf.lcd_density=240 setting to stick to 160 after a reboot, that might fix the few instances where an app won't render full screen.
I've tried chmod 666 system.prop and chown root.root system.prop but it still gets returned to normal after rebooting.

Wow I'm excited to test this out. Couldn't we get someone to code this into the startup script theoretically?
Edit: Tried it out. Really really nice. If only we could get the rest of the apps to work the right way... right res.

One thing also that's cool is in launcherpro you can add more columns to the drawer so you can fit an insane amount of apps on screen.
Sent from my GT-I9000 using Tapatalk

Also out of curiosity, have you tried any other DPI like 200? Our does it need to be either or to keep it proportional?
Sent from my GT-I9000 using Tapatalk

Lower resolution works as well. Here are some comparisons. 160, 240, 320. 200, since someone asked.

wow, this could REALLY be nice.. Just need to fix everything, but like others have said no HUGE things that cause it to be unusable, but I would love to see everything correct.

Also out of curiosity, have you tried any other DPI like 200? Our does it need to be either or to keep it proportional?
Click to expand...
Click to collapse
No, the only reason I chose 160 was because it is listed as "MDPI" in the Android SDK. (We were using "HDPI" with 240.)
I only figured it was a "supported" number, so I started there, but most any number will do. You can see a chart where it recommends certain numbers based on resolution or screen size, but I think these recommendations are to cover everybody, which includes folks who can't (easily) see small text or icons.
The chart that shows Google's recommendations is here.

reading around, it seems that the files need to be put back to read only.

phlunkie said:
reading around, it seems that the files need to be put back to read only.
Click to expand...
Click to collapse
I thought so also, but you don't need to. All I'm doing is copying it with root explorer to sd, then using astro to edit the line and root explorer to put it back. Reboot and your GTG. Everything works fine.
Sent from my GT-I9000 using Tapatalk

So the settings are sticking after a reboot? I will have to try this when I get home.
Sent from my SAMSUNG-SGH-I897 using XDA App

phlunkie said:
So the settings are sticking after a reboot? I will have to try this when I get home.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
After I edited the build.prop and the build.prop.bak files in the /system directory it works fine after reboot. A problem that I have is that TouchWiz force closes after editing the files.

Using this on SGS made:
- notification bar unreadable (kindof text overlap@240160 setting).
- Launcher pro works.
- Market scales nice.
- big list's buttons are now nice
//edit: changed to 200 - seems to be great compromise.
@up
Bad practice. U shouldnt have edited ur build.prop.bak file, becouse it is actually a backup of original build.prop, made by RootExplorer (guess). In case u want to revert to original content, u just delete edited file and delete .bak from this one.

xan said:
Using this on SGS made:
- notification bar unreadable (kindof text [email protected] setting).
- Launcher pro works.
- Market scales nice.
- big list's buttons are now nice
//edit: changed to 200 - seems to be great compromise.
@up
Bad practice. U shouldnt have edited ur build.prop.bak file, becouse it is actually a backup of original build.prop, made by RootExplorer (guess). In case u want to revert to original content, u just delete edited file and delete .bak from this one.
Click to expand...
Click to collapse
Any pics? Love to see the difference.
Sent from my Nexus One using XDA App

Here they are.

I'm trying to figure out how to make those other applications also use the full screen when at a different resolution. I tried the method here
http://forum.xda-developers.com/showthread.php?t=739647
to run a script that rewrites the /system.prop file, and it didn't fix anything, so either that is not where the applications are getting the property from, or we need to rewrite the file earlier in the boot process.

Are you sure those apps are graphically able to scale? Maybe touchwiz does not take scaling into account (at least with native apps) because the screens are all 4 inches.

LCD Density !

I'm not entirely sure if someone has already said this or if anyone knows how to do it, but I have and its really useful !
Basically you can drop the Density of the screen and give it a larger appearance. Best way to do this in my opinion, is to grab yourself a copy of Droid Explorer, browse into the system folder in your root, save a copy of Build.prop to the desktop, open it with notepad, find LCD DENSITY=240 or whatever it is and change the value to 180, replace the build.prop in Droid explorer with the one from your desktop and reboot your device
If you don't like it you can always go back in and change it back ^^

Sorry for the noobish question. But I am not quite sure I understand what this does. Could you explain just a wee bit? Even better if you could post before and after screenshots.
Cheers....

Uhm, Nothing new I'm afraid. There are already some apps in the market that let you do just this.
xpstyle36 said:
I'm not entirely sure if someone has already said this or if anyone knows how to do it, but I have and its really useful !
Basically you can drop the Density of the screen and give it a larger appearance. Best way to do this in my opinion, is to grab yourself a copy of Droid Explorer, browse into the system folder in your root, save a copy of Build.prop to the desktop, open it with notepad, find LCD DENSITY=240 or whatever it is and change the value to 180, replace the build.prop in Droid explorer with the one from your desktop and reboot your device
If you don't like it you can always go back in and change it back ^^
Click to expand...
Click to collapse
Sent from my GT-I9000 using XDA App

Its Changing the resolution of the screen so that everything is slightly bigger (or smaller) by editing the value.
Thank you for the info!
EDIT - Sorry I posted this too late! A mod can remove it if you want...

Oooooooh. Got it.
But IMHO I dont see why I (or anyone else for that matter) would personally want to do something like that. Unless, it just for kicks.

It's not changing the resolution. It's changing the dpi settings.
Why is this in the dev forum?

Rawat said:
Why is this in the dev forum?
Click to expand...
Click to collapse
For the same reason Samsung went with Rfs : unknown

There is an app on the market. LCDDensity it is.
Sent from my GT-I9000 using XDA App

Is this still being applied after restarting your phone?

The point of it is to have a larger viewing area, which is great for things like viewing webpages or documents but it can break games and certain designed UI's (like touchwiz)
Having ADW + Density change looks good though.

Pff. Changing this value kills too much apps (like LauncherPro, Simi Clock and others).
So, changing this value renders most of your apps unusable.
Not working for me anyhow.
ps. I do not like the changed settings either, the screen feels like having a blur on it. (tried 100 and 180 as values).

jbrugger said:
Pff. Changing this value kills too much apps (like LauncherPro, Simi Clock and others).
So, changing this value renders most of your apps unusable.
Not working for me anyhow.
ps. I do not like the changed settings either, the screen feels like having a blur on it. (tried 100 and 180 as values).
Click to expand...
Click to collapse
Thanks for all the feedback sorry i was un-aware that there was an app for this ^^ also if you go to the Android Market and grab "Spare Parts" and turn off Compatibility mode, 99% of apps will scale fine to the change

Seems not to be a good idea on my galaxy s. Everything resizes and loks cool except the build-in apps:agenda, calculator, dailer, mp3player cdmode. Those apps did not change resolution ;(
But still i have to admit: density of 200 looks much better than 240
Cool app, stupid samsung apps!
Sent from my GT-I9000 using XDA App

Changing Icon & Font Size

So I followed the steps here and my icons look so big and beautiful only problem is whenever I use anything but the default 240 size the dialer crashes and cannot be used whatsoever, anyone know how to fix this????
"use root explorer and edit /system/build.prop
find:
Quote:
ro.sf.lcd_density=240
Change the 240 to 260 (or something else), save the file, and reboot the phone
A Higher # will make everything BIGGER, including icons, fonts, etc
A lower # will make everything smaller"

Please somebody. Has anybody done this edit before??? Thanks

there must be another setting to change to get the Dialer to work. i tried 248 and 275 (listed in the build.prop file) and it didn't work for me either. on my other android devices, i would simply find a font file and rename to DroidSans.ttf and DroidSans-Bold.ttf and then copy to /system/fonts/. i tried this on my first Atrix and it went into a continuous boot loop. i had to exchange for another device. DO NOT MAKE THE SAME MISTAKE I DID!

cortez.i said:
there must be another setting to change to get the Dialer to work. i tried 248 and 275 (listed in the build.prop file) and it didn't work for me either. on my other android devices, i would simply find a font file and rename to DroidSans.ttf and DroidSans-Bold.ttf and then copy to /system/fonts/. i tried this on my first Atrix and it went into a continuous boot loop. i had to exchange for another device. DO NOT MAKE THE SAME MISTAKE I DID!
Click to expand...
Click to collapse
It would be great if someone knew how to fix this. I really think the icons look great its too bad the dialed keeps crashing!!

cortez.i said:
there must be another setting to change to get the Dialer to work. i tried 248 and 275 (listed in the build.prop file) and it didn't work for me either. on my other android devices, i would simply find a font file and rename to DroidSans.ttf and DroidSans-Bold.ttf and then copy to /system/fonts/. i tried this on my first Atrix and it went into a continuous boot loop. i had to exchange for another device. DO NOT MAKE THE SAME MISTAKE I DID!
Click to expand...
Click to collapse
It would be great if someone knew how to fix this. I really think the icons look great its too bad the dialer keeps crashing!!

The Atrix checks and rechecks all files on every boot so this will brick your phone if the files dont match

neer2005 said:
The Atrix checks and rechecks all files on every boot so this will brick your phone if the files dont match
Click to expand...
Click to collapse
yep! i can testify to that, lol! makes me appreciate the ease of root and customization for my Nexus One (will never give it up!) and my wife's Inspire4G. i'd also like to punt this MotoBlah crap! i'm using Enhanced Email and the Blah contacts app is disabling my ability to select accounts i want to use to add new contacts...
not holding my breath on this, but i hope Moto makes good to unlock the bootloader and allow us to customize our devices.

neer2005 said:
The Atrix checks and rechecks all files on every boot so this will brick your phone if the files dont match
Click to expand...
Click to collapse
Well the only thing i can see so far that has been negatively affected is the dialer. Everything else works fine.
With the higher resolution the icons have shrunk and to me look a little disproportionate on the ATRIX. This makes it look really nice and well spaced.

Need bigger icons for StreakDroid GingerStreak 2.4.4

Hi,
I like StreakDroid GingerStreak 2.4.4 very much. I would like to have bigger icon size. Is there any option to set within StreakDroid GingerStreak 2.4.4 ROM?
It is amazing that there is hundred of similar question of how to increas the font size and icon size within the android world, however there is no such universal solution. People then have to tie back to specific ROM on their specific phone. some ROM has font size control, some don't.
As far as I know there is no ROM has icon size setting available for the user.
Few app on the market offer font size or icon size management, however those only work for specific application (SMS for example) or for icons for home screen only ( BIG ICON app for example but it only work for a specific launcher)
I am not looking for universal way to adjust the font size or icon size for android OS ROM in general because I know it is unrealistic, even thought these functions suppose to be really trivial for MS Windows or MAC.
Since I am using StreakDroid GingerStreak 2.4.4 ROM, my question is just about looking a way to increas the icon size for this ROM.
Thanks

You can edit your /system/build.prop to achieve what you are looking for. Look for a line that starts with so.rf.lcd_density and adjust that to what you want. If there is no such line, put one in there. The default is 160. I have mine at 240 and like it, seems more phone-like rather than tablet-like.. There have been some reports of incompatibilities with some apps and such if you change it to anything but 160 or 240. Make a backup of your current build.prop first.

As @lord said
It is that simple
If you use streakdroid then read whole OP of it

lordmorphous said:
You can edit your /system/build.prop to achieve what you are looking for. Look for a line that starts with so.rf.lcd_density and adjust that to what you want. If there is no such line, put one in there. The default is 160. I have mine at 240 and like it, seems more phone-like rather than tablet-like.. There have been some reports of incompatibilities with some apps and such if you change it to anything but 160 or 240. Make a backup of your current build.prop first.
Click to expand...
Click to collapse
Yay! Thanks for much for the info. I got what I want. Below is what has been done:
Download File Manager (free app) from Market
Set permission R/W for /system folder as well as write permission for /system/build.prop file for owner and all other parties
Open the prop file and add this line: ro.sf.lcd_density=240
Save the file and reboot
It works...
Thanks again.

Kolteabhiman said:
As @lord said
It is that simple
If you use streakdroid then read whole OP of it
Click to expand...
Click to collapse
Dear, what stand for OP? Can you give me info where to find OP to read more?
I like to digg into system files and properties...
Thanks

Original Post. He is referring to the original post for streakdroid. Glad you got it working.
Sent from my Dell Streak using xda premium