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

Opengl white textures problem and froyo 2.2

Has anyone ran into problems with Opengl textures on Froyo 2.2, cant seem to get the textured triangle sample to display a texture on my 2.2 nexus one, works fine on the 2.1 emulator. But when I build and run the API demos from the SDK and select the texture triangle it works fine, this is driving me crazy why the same code doesnt display any textures if it’s built as a standalown app. I have tried adding ‘nodpi’ and ‘drawable’ dir’s with the texture images too.
Oh I'm pretty sure it worked fine when my nexus one was running 2.1.
Thanks

Think I solved it, i will post the fix later.

So what was the problem? I'm experiencing this to. I noticed the issue happens if I have ndroid:anyDensity="true" in my app manifest, but if I use anything else, I don't get the full 800x480 screen resolution available to me.

Same issue is happening to me as well. My little opengl 2D test app ran fine in my Nexus 2.1 and after upgrading to 2.2 textures are completely white. Would you please tell us what was your problem?
Thanks!

I think I have your solution.
First, as people may already know, to get the full resolution you want <supports-screens android:anyDensity="true" /> in your application manifest.
The textures are white because when you load them from a Bitmap, android has resized them and the resizing has made them a size that is not a power of 2, so it borks when you load the texture into opengl.
So how to you stop Bitmap from doing that?
create a folder in your "res" directory called "drawable-nodpi" and move your images in to that folder and the system will stop resizing them.
this is only an issue if you are using resources, if you load your images from assets or some other place, then I don't think the system resizes them.
Hope this helps, it worked for me.
-James

Hey James, thanks for your insight
However I just did as you said but I'm still getting the same result. I never used power of 2 textures and they were perfectly rendered; I'm guessing GLUtils.texImage2D already does the dirty work.
anyDensity is set to true, bitmaps are inside drawable-nodpi, all screens are set in SupportedScreens... dunno; I'll guess I'll try to load the texture from elsewhere, not the resources, and see if I can pinpoint the problem.

Hi,
I almost forgot to post here. All James said is true and doing as he said (and using power of 2 widths & height for textures) made it work, but a special circumstance was blurring my point of view here.
The circumstance is that NPOTs seem to be supported in Nexus One with Android 2.1, but not 2.2. Why this support was removed remains a mystery to me

Sorry about not posting what I found and I dont have thread update email reminders turned on. All I did was strip down the api demo (which works) to just a single project and used it as a template.

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.

Atrix Screen Color profile

Hello,
I`m new on this device and just make a color profile that seems to be acceptable.
It`s not perfect but usefull to simulate in photoshop how an image will looks like on the Atrix. It`s good for themers.
Just download attached file and put the .icc file in windows\system32\spool\drivers\color. Then in photoshop : CTRL-Y, go to menu display/image format and choose the profile. Also tick Keep RVB numbers.
As you can see in the attached picture, atrix screen is not able to reproduce all the sRGB color space, (very) bad screen ...
Note that if your monitor is not correctly calibrated this will not be useful.
Enjoy.

That's a very spikey gamut. I just made my own using a Huey and Argyll on Linux. I ran an X server on my Atrix and had the 'dispread' program display on it. My result is much more like sRGB, just transposed a little in the green direction.
I've attached the profile I made and screen shots of 'iccexamin' displaying the gamut of your profile and mine.

IanTester said:
That's a very spikey gamut. I just made my own using a Huey and Argyll on Linux. I ran an X server on my Atrix and had the 'dispread' program display on it. My result is much more like sRGB, just transposed a little in the green direction.
I've attached the profile I made and screen shots of 'iccexamin' displaying the gamut of your profile and mine.
Click to expand...
Click to collapse
Thanks for that, I didn`t know about this linux soft and will try later.
What sensor are you using (mind is spyder3) ? Did you run a calibrate or profile only process ?
My first impressiom is that my profile shows me a better result in photoshop. I will test it with other images.
Calibration subject is a headache subject ...

A new and better profile attached.
@IanTester, I think you have a problem in your calibration process.

an other one. seems slightly better ...

What exactly do you mean by "calibration"? The documentation for Argyll says that calibration of a display means "1) Changing controls or internal settings that it has. 2) Applying curves to its color channels."
I've made a second profile using the same data as before but using a different "algorithm" argument with colprof. The previous profile used '-as', which generated a "shaper + matrix", this one used "-aX" to generate "XYZ cLUT + matrix".
I understand the basics of colour management but don't really know much about generating profiles. The dry and error-prone documentation for Argyll doesn't help much. Basically I have a shell script that I run to profile my monitor and it seems to work with the few colour-managed programs I have. Any help would be welcome.

IanTester said:
What exactly do you mean by "calibration"? The documentation for Argyll says that calibration of a display means "1) Changing controls or internal settings that it has. 2) Applying curves to its color channels."
I've made a second profile using the same data as before but using a different "algorithm" argument with colprof. The previous profile used '-as', which generated a "shaper + matrix", this one used "-aX" to generate "XYZ cLUT + matrix".
I understand the basics of colour management but don't really know much about generating profiles. The dry and error-prone documentation for Argyll doesn't help much. Basically I have a shell script that I run to profile my monitor and it seems to work with the few colour-managed programs I have. Any help would be welcome.
Click to expand...
Click to collapse
Hello,
I just installed dispcalGUI on my Fedora partition. It seems to be a good calibration soft, easier to use than argyll ...
Then I tried to configure a remote desktop via VNC but it`s too slow. The image generated on linux arrives to late on the android screen ... :laugh:
So I need your help too. What apps are you using to have a copy of your linux desktop on your phone ?
There are usually two modes when using a colorimeter : calibration & caracterization. Wee need the second one as it is just to use the profile to simulate the atrix screen. Calibration is to be loaded into the graphic card and correct as well as possible the screen colors. I don`t know any app able to load a color profile in android system, unfortunately.
Is it more clear ? Sorry for english ...

Can any one tell me of Software for windows that would allow me to output my screen via HDMI? I have the hardware but no available Linux terminal to run it.
Sent from my MB860 using xda premium

There's no way to apply a color profile system wide in Android?

There kinda is. If you're on CM, you can go to Settings > CyanogenMod settings > Interface > Render effect. There you'll find a predefined set of somethings that can loosely be called color profiles.

Oh yeah I almost forgot about that one.

NST Screen Saver Frequency Setting?

I've successfully rooter my Nook Simple Touch and explored all of its files and databases that I can find. But I cannot locate the setting to change that will update the frequency at which the screen saver changes images.
My goal is to have a folder of image files that change every 30 seconds or so. Unfortunately, the stock screen saver's change timer is much longer than that.
As a workaround, I set the screen saver activation time to 500 hours and installed Perfect Viewer to run its slideshow function, but this is less than ideal. I'd rather just do it the right way.
Does anyone know where this setting is located?
Thanks!

Reaperducer said:
I've successfully rooter my Nook Simple Touch and explored all of its files and databases that I can find. But I cannot locate the setting to change that will update the frequency at which the screen saver changes images.
My goal is to have a folder of image files that change every 30 seconds or so. Unfortunately, the stock screen saver's change timer is much longer than that.
As a workaround, I set the screen saver activation time to 500 hours and installed Perfect Viewer to run its slideshow function, but this is less than ideal. I'd rather just do it the right way.
Does anyone know where this setting is located?
Thanks!
Click to expand...
Click to collapse
That would seem to be a poor decision as far as battery life is concerned. Are you sure you really want to do that?

nmyshkin said:
That would seem to be a poor decision as far as battery life is concerned. Are you sure you really want to do that?
Click to expand...
Click to collapse
Battery life is not a concern in my application.

Reaperducer said:
Battery life is not a concern in my application.
Click to expand...
Click to collapse
OK, so I have to admit I didn't even know this happened. It's been a long time since I used a folder of images for a screensaver. What I seem to recall from that time was the images changing each time the NST went to sleep, but not during sleep.
Let me take a look. I guess one possible approach would be to consult a logcat after an image change and see if there are clues there.

I've come up empty on a search through the various B&N app databases and settings files.
Just to see this actually happen, I changed my screensaver from a static book cover image to one of the packages of images I installed years back. That was nearly 24 hours ago and there is still no change, which is what my memory told me to expect. So without an automatic change, there is nothing to look at in the logcat.
Are you sure your images actually change by themselves during the standby/sleep process? I know they change when you wake up the device and then let it fall asleep again.
You've already tried the slideshow idea or I would suggest that, but did you know there is a built-in slideshow (probably associated with the demo mode)? I don't know what the parameters of that are or whether you could replace the images with your own without breaking it.
Maybe a better question to help me understand what you'd like to do is: will the NST be used for something other than the slideshow display (either running in the background or running on demand when the device is awakened)? If all you want is the slideshow then any number of apps (like the PerfectViewer you mention) would work. Maybe something simple if you just need the slideshow. But if you really are using the device for other things and just want the sleep screen to change periodically, that's either got to be supported in the settings in an accessible way (which I'm doubtful about) or it has to be a custom alteration of the OS.