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...
Hi all!
As many of you have noticed, the multitasking on Stock ROMs is not that great, especially if you are coming from some custom ROMs like CM, etc. The thing is that if you want to recall an app that was closed 5 minutes ago, it has to be started again. To change this it's very easy by editing the build.prop file.
Requirements:
- Stock ROM or stock based, maybe others but I doubt that this isn't included within
- Root
- File manager/ Root explorer with text editor
Instructions:
1. Navigate to /system, find the build.prop file and copy it to /data (just as a backup).
<<Later on if you will face any bootloop/troubles, restart the phone in TWRP, go to file manager and simply copy the original build.prop from /data to /system and overwrite it.>>
2. Open the build.prop in /system with a text editor and at the bottom, add the following lines:
sys.config.spcm_enable=false
ro.config.fha_enable=true
3. Save your modifications to the file and before restarting, check the permissions again to be correct (rw-r--r--).
4. Reboot.
That's it. Enjoy and report if you notice any strange behavior. Normally it shouldn't be any, but who knows...
DISCLAIMER: Do this at your own risk. I will not be responsible if something bad will happen.
Can you explain wat exactly those lines doing? What is different in the multitask experience / behavior? Many thanks
If you'll open up Chrome, go to a webpage, then press the home button and go back to Chrome again. In most cases you'll notice that it starts reloading the page. I've noticed that a lot of apps are restarted/refreshed after a short time if I leave them in the background and mostly you never get to the same point where you left off in the app.
I'm not a programmer and I just saw in S6 edge+ forums how to improve multitasking: http://forum.xda-developers.com/s6-edge-plus/general/root-ram-management-multitasking-fix-t3228917. As you can read there, the guys are changing plenty of values, but at the suggestion of member @citytrader who changed only 2 lines, I tried this in my Le Max 2 and it worked pretty well. Somehow I don't have the redraws that I had before. Battery life seems unchanged. No lag (there was none before as well), but the most important thing no more redraws (with some small exceptions but in any case, far less than before).
You can find articles/threads on xda about spcm and fha/dha.
I think the reason for that is that EUI is pretty agressive in closing apps to save battery.
Did you try to lock the app so its doesnt close.
Locking the app does not help. As you said, EUI is pretty aggressive at RAM management. I'm pretty sure that you have viber/whatsapp locked but if you switch to 2-3 apps and then come back to viber for instance, the app is redrawing.
So Marshmallow uses this new format for configuration files for apps on the EPD. Maybe we can start collecting recommended configurations for various apps? I noticed that the default files it comes with don't include the Kindle app this time, tho it had a default config in the old LP settings.
So, if you've found good settings for a particular app, please post them here! And I might go look on the Russian site to see if there are any there already - tho if one of the Russian-speaking users here wants to do that first I wouldn't complain
edit: I just found an app for editing the new configuration files, it's by x2009xxx on this hi-pda thread. Attaching for convenience. The button at the bottom to save the configuration and the toast that pops up when you do so aren't in English, but all the options are, so I'm pretty sure you can figure it out. (Don't forget to reboot to activate your changes)
I am wondering is there possibility to set epd to full refresh after 5 pages or every page. There is no sign in readme file. I tried adding ""slowmode" : true" in the configuration cfg but notting happens.
I'm not sure, but I have gathered that you have to reboot for changes to take effect.
Sent from my YD201 using Tapatalk
I know, when I change something (ex. dithering, sharpening etc.) there is effect but problem is that i don't see command which can set full refresh of epd screen after some interval (previously it was slowmode). I'm using moon+ reader (white letters on black background) and without full refreshing after some pages ghosting is terrific and reading seems to be nearly impossible.
Remove the Android GUI transitions/effects on Developers Menu, not only makes your phone faster but it also helps EPD to have less ghost when using the other Android Apps, and folders...
I just edited the first post to add a tool I found for editing the config files.
ahigienix said:
I know, when I change something (ex. dithering, sharpening etc.) there is effect but problem is that i don't see command which can set full refresh of epd screen after some interval (previously it was slowmode). I'm using moon+ reader (white letters on black background) and without full refreshing after some pages ghosting is terrific and reading seems to be nearly impossible.
Click to expand...
Click to collapse
I'm looking at the readme.txt that lives in the epd_optimizer directory, and the option that sounds related to what you're talking about is "update_timeout - timeout of fullscreen update after content change. Use -1 to disable."
Tried to change update_timeout value. There are some changes in update mode but EPD still not doing full refresh (like in Yotareader for example). Still after flipping some pages black background is full of gray shades from previously viewed pages. Tested on CoolReader, Moon+ FBreader, Allreader.
Is there anyone who figured out how to set full refresh of EPD in any book reader?
Nice thread, I had in mind creating one like this. I haven't played with the configuration file yet, but I can post here what I found from other xda posts and a file from Russian Telegram group.
For Whatsapp (but I think it should work also on other similar apps) a configuration found here is the following:
Code:
{
"name": "com.whatsapp",
"description": "WhatsApp",
"dithering": "ATKINSON_BINARY",
"update_timeout": -1,
"sharpening": 2,
"contrast": 0,
"brightness": -5,
"stretch_black": 50,
"stretch_white": 220,
"regional_update": false
}
For Vkontakte (VK - Russian social network) I found this one:
Code:
{
"name": "com.vkontakte.android",
"description": "VKontakte",
"update_type": "GRAYSCALE",
"dithering": "ATKINSON_BINARY",
"update_timeout": 0,
"sharpening": 1.0,
"contrast": 50,
"brightness": 10,
"stretch_black": 50,
"stretch_white": 200,
"regional_update": true
}
Maybe we could develop some configurations for groups of apps: chat, social, e-book readers, office, browser, etc. and post them here!
Don't know if I'm missing something but I've tried all sorts of different values for dithering, update type, contrast, brightness, stretch_black, and stretch_white but after restarting nothing seems to have any effect. No matter what I do, everything just looks way too bright/low contrast and washed out. On the other hand, the Yotahub looks fine--deep blacks and easy to read.
This is on a YD206. Everything looked fine on lollipop. I submitted bug reports to yotadevices but they told me that the YD206 isn't supported. Anyone else having this issue? And if so, are you on YD206?
EDIT: Anyone know how to query what epd_optimizer settings an application is using? The backscreen is the only thing that looks good and AFAIK its package name is com.yotadevices.yotaphone2.launcherbs . Unfortunately there's no corresponding entry in the epd_optimizer directory.
Here is a stock EPD_optimizer folder after OTA upgrade from 5.0. Try replacing your files and reboot.
I figured out that changing values via application make a mess in cfg files. Better to check package name using app, copy some stock cfg, rename it to package name and edit via Total Commander it works fine.
I have yd206 and changing values take effect but i can't set full EPD refresh.
EDIT: Anyone know how to query what epd_optimizer settings an application is using? The backscreen is the only thing that looks good and AFAIK its package name is com.yotadevices.yotaphone2.launcherbs . Unfortunately there's no corresponding entry in the epd_optimizer directory.
Click to expand...
Click to collapse
From readme.txt
If these parameters are missing in app's configuration as well, the system will use parameters which defined in master.cfg configuration file. If this file is deleted, the system will use parameters that are stored within Android framework.
ahigienix said:
Here is a stock EPD_optimizer folder after OTA upgrade from 5.0. Try replacing your files and reboot.
I figured out that changing values via application make a mess in cfg files. Better to check package name using app, copy some stock cfg, rename it to package name and edit via Total Commander it works fine.
I have yd206 and changing values take effect but i can't set full EPD refresh.
From readme.txt
If these parameters are missing in app's configuration as well, the system will use parameters which defined in master.cfg configuration file. If this file is deleted, the system will use parameters that are stored within Android framework.
Click to expand...
Click to collapse
Thanks, I'm no longer using the app to modify the values as you suggested and changing settings has an effect now. (using vim in an arch chroot environment) Using your stock values for a separate firefox config seems to have improved things. Still not nearly as good as 5.0 but I can actually read text now.
However, there is this issue where from moment to moment the screen brightness seems to switch back and forth between two settings: a config with deeper blacks (clear) and a config that's too bright. It's almost as if there are two configs fighting for control. If I let the phone sit (so there are no screen updates), it will eventually settle on one of those configs but not reliably on any particular one--it almost seems random. I spent several hours trying a variety of different settings but I can't seem to get rid of this problem or manage a config that's comparable to 5.0.
At this point I think I'm just going back to 5.0 as I can't really put any more time into this. Maybe the problem will sort itself out in future releases but I'm not hopeful given the lack of support for the YD206.
I have three yd206, one which firmware was sideloaded from 1.1.31 had simmilar to your EPD glitchs, try to delete your epd_optimizer folder, create new one and copy files from attachment, then do a hard reset. It helped me and now this yd206 runs flawlessly.
I found the file /root/sdcard/TitaniumManager/mirror.cfg has some information similar to files in .../android/epd_optimizer and create a configuration for FBReader, but makins some test it seems nothing change.
Follow the last solution for my file org.geometerplus.zlibrary.ui.android.cfg
{
"name": "org.geometerplus.zlibrary.ui.android",
"description": "FBReader",
"dithering": "ATKINSON_BINARY",
"update_timeout": -1,
"sharpening": 1.0,
"contrast": 70,
"brightness": -10,
"stretch_black": 50,
"stretch_white": 220,
"regional_update": false
}
Have you any suggestion?
ahigienix said:
I have three yd206, one which firmware was sideloaded from 1.1.31 had simmilar to your EPD glitchs, try to delete your epd_optimizer folder, create new one and copy files from attachment, then do a hard reset. It helped me and now this yd206 runs flawlessly.
Click to expand...
Click to collapse
Hi, couldn't get this off of my mind so I took another stab at it. I've tried everything you've suggested but haven't been able to get things to an acceptable level. I've put together a couple images comparing 5.0 and 6.0 image quality (attached to this post) with the epd_optimizer .cfgs you've provided.
The two images have a few different icons on the home screen but demonstrate the difference in both brightness and clarity pretty well. I'm not saying those .cfgs didn't improve things--they definitely did (yes, it originally looked even worse than the 6.0.jpg image prior to using the .cfgs you provided) but it still doesn't look nearly as good. Looking at the 6.0.jpg image, you can probably imagine how difficult it would be to read an ebook or browse the web.
I think there's more to this than the .cfg files. Note that I upgraded to 6.0 by restoring the "MMB29M.6.0.1-RU1.1.147" backup provided in this thread via TWRP. I was coming from LRX21M.5.0.0-HK1.1.124d (I always clear the cache and dalvik between firmware changes of course).
EDIT: Whoops, I've mixed up the image names. Fixed the images.
Excuse me i do not know about changing that values for the epd
but as a person who works and edits photos the difference between the pics is remarkable in my eyes
beacuse it seems to be that there are different grey scales that are produced, especially the black value.
You can edit every photo you made into greyscale (8bit or 16bit) and it normally looks fine.
but you can also convert it into a black/white (1bit) picture with a filter like diffusion and it is more grainy.
so for me it looks that the 6.0jpg is too grainy and is not the correct grayscale. It can be washed out but the black part seems not that fine as it is in the 5.0jpg pic.
maybe this isn't that important but i want to point on that.
GetSAS said:
Excuse me i do not know about changing that values for the epd
but as a person who works and edits photos the difference between the pics is remarkable in my eyes
beacuse it seems to be that there are different grey scales that are produced, especially the black value.
You can edit every photo you made into greyscale (8bit or 16bit) and it normally looks fine.
but you can also convert it into a black/white (1bit) picture with a filter like diffusion and it is more grainy.
so for me it looks that the 6.0jpg is too grainy and is not the correct grayscale. It can be washed out but the black part seems not that fine as it is in the 5.0jpg pic.
maybe this isn't that important but i want to point on that.
Click to expand...
Click to collapse
I see, thanks for the insight. Maybe this will help with determining what's causing this.
I changed contrast in the master to 40, and I'm pretty happy with the results.
Full master file:
Code:
{
"name": "master",
"description": "This is default epd update setting. Please modify with caution.",
"update_type": "MONOCHROME",
"dithering": "STUCKI_BINARY",
"update_timeout": -1,
"sharpening": 1,
"contrast": 40,
"brightness": 10,
"stretch_black": 30,
"stretch_white": 220,
"regional_update": false,
"color_inversion": false
}
epd refresh problem
after i upgrade official stock 6.0.1 my epd stop refreshing. am i in the right place? i dont know how to change the values mentioned above. can someone help me please? thanks
lgk350tr said:
after i upgrade official stock 6.0.1 my epd stop refreshing.
Click to expand...
Click to collapse
My navigation program has the same probem. Too much ghosting. Is there a possibility, to set a refresh time? (Maybe a background program with timer and torch screen?) I can do it with developer options (show surface updates). Is it possible, to make a shortcut or start and stop it automatically?
If the yotaphone is in standby, the epd screen is constantly flashing (after 2 minutes) and I don't know, why.
I am experiencing the same. I own a YD206 converted to 201 and running lates MM OTA update.
EPD screen was fine for couple of days, but know ghosting is terrible specially when navigating thru full Android. Also black color on widgets is totally grayed out.
Right now I am trying the full discharge and leave it for couple of hours before I fully charge it.
Any other solution/suggestion on what to try? This is definetly a refresh problem which is not eliminating previous images.
Thanks
On the Zenpad I have the issue where the YouTube app is vastly over sharpened to the point it harms the visual experience. I can't find a way to turn this off, I have tried force stopping Splendid but it doesn't work. Anyone know of a fix? Ideally lineage os is what I need to get away from this Zenui (it's alright I guess but has weird things that can't be turned off, like this visual enhancement)
I think it's the "Tru2Life" Program, I think it is only removed thru root
Yes, it's the Tru2Life app, aka VisualMaster. The way it makes YT look is total BS. But it's not just YT. There's a database of about 15000 eek apps that it applies different display profiles to. These apps are mostly video, photo, games and other multimedia.
So you do need to have root to disable it. Or at least a custom recovery. The easiest method is probably to use a root-level app manager that can safely disable Tru2Life, which is a system app. Or you can manually edit the package manager config files yourself if you have the skills and don't want root.