I am trying to figure out how to change the max sending size for MMS on the EVO. By default when sending pictures it compresses them down to around 60k. It was accomplished on the Nexus One HERE and the G1 HERE. The MMS.apk for the EVO does not have the same file to modify as the Nexus One, and I can't figure out which xml to edit. The default compression for MMS is ridiculous on the EVO, by default when sending pictures it compresses them down to around 60k. We should be able to set it to 300k and not have any problems.
No offense to anyone, but please do NOT reply with "hancent works for this, xxx can do this, such and such fixed this", or any other app/ROM/etc for that matter.
I am asking how to modify the stock EVO MMS app, not how to install a different ROM or app!
Here is the original EVO MMS.apk (Froyo)
the max on the Evo is 2m it would be nice to have more but thats the max the way you see what your max is set to is go to all message screen then press menu go to settings then it will be maximum message size
stercast said:
the max on the Evo is 2m it would be nice to have more but thats the max the way you see what your max is set to is go to all message screen then press menu go to settings then it will be maximum message size
Click to expand...
Click to collapse
I don't think you understand my question/problem. Read the Nexus One link in the OP. The issue is when sending MMS, the EVO compresses the living hell out of any image. That 2mb setting you are referring to is not the same thing, that is an overall message size, not individual image size.
I was wondering if anyone else was annoyed by this. I wish I could help you in some way though..
I hope this gets resolved.
i believe the evio rom fixed this issue
zaft1 said:
i believe the evio rom fixed this issue
Click to expand...
Click to collapse
Well, the dev of that ROM says he fixed this, but not how. It would be nice if he would share the fix with everyone.
I sure hope someone gets this done, the compression is really annoying.
Tapatalk'd on Evo
Could a possible workaround be to zip said pic and send the zip? I don't remember if I tested this or not when I was experimenting with the mms apps.
SteelH
I have looked in the preference_att.xml and preference.xml and found pref_key_mms_max_size. I dont understand binary so I am not much help here.
dwertz said:
SteelH
I have looked in the preference_att.xml and preference.xml and found pref_key_mms_max_size. I dont understand binary so I am not much help here.
Click to expand...
Click to collapse
I saw that as well, but there is no byte size near it to edit like in the Nexus One.
SteelH said:
I saw that as well, but there is no byte size near it to edit like in the Nexus One.
Click to expand...
Click to collapse
Have you asked Calkulin yet if he would let you know what he did to fix it? I would hope the open nature of everything he would gladly help.
MrDSL said:
Have you asked Calkulin yet if he would let you know what he did to fix it? I would hope the open nature of everything he would gladly help.
Click to expand...
Click to collapse
I have asked him, he has not replied. Also, I can tell you simply using the mms.apk from his ROM will not solve the compression problem.
if you use chomp sms there's a selection for no limit on mms size you could pull that apk apart and see what it uses to regulate the size limit
BLOWNCO said:
if you use chomp sms there's a selection for no limit on mms size you could pull that apk apart and see what it uses to regulate the size limit
Click to expand...
Click to collapse
Good suggestion but unfortunately that won't help us.
I hope someone fixes this issue. I always wondered why the stock MMS compresses images so much. Its terrible. I shall be keeping watch for anything.
Is there a way to be able to dicifer logcat by starting it right when you add the picture and when it autosizes to see what's doing it? Here is a logcat of when I attach a picture to mms when it auto resizes if anyone knows whats doing it.
Code:
D/ComposeMessageActivity( 564): initFocus: true
D/ComposeMessageActivity( 564): syncRecipientListButton:
D/ComposeMessageActivity( 564): mRecipientList.size(): 0
D/Jerry1 ( 564): 2222
I/XT9_C ( 195): [loadDefaultDB] xt9_raw/ldb_0409.ldb size=98056 (loaded)
I/XT9_C ( 195): [registerXT9LDB] ldb_0409.ldb loading [done]
D/XT9_ldb ( 195): wLdbNum=109, first wLdbNum=109, second wLdbNum=0
D/XT9_C ( 195): [registerXT9LDB] current LdbNum=109, First LdbNum=109, Second LdbNum=0
D/dalvikvm( 195): GC_EXTERNAL_ALLOC freed 304 objects / 15192 bytes in 164ms
D/ComposeMessageActivity( 564): get the ContactNameCache
D/MainActivity( 5880): [HTCAlbum][MainActivity][onStop]: Begin
D/dalvikvm( 564): GC_EXTERNAL_ALLOC freed 402 objects / 49256 bytes in 56ms
D/dalvikvm( 564): GC_FOR_MALLOC freed 70 objects / 25688 bytes in 41ms
I/dalvikvm-heap( 564): Grow heap (frag case) to 3.863MB for 63504-byte allocation
D/dalvikvm( 564): GC_FOR_MALLOC freed 0 objects / 0 bytes in 69ms
D/dalvikvm( 564): GC_FOR_MALLOC freed 4 objects / 30840 bytes in 41ms
I/dalvikvm-heap( 564): Grow heap (frag case) to 3.957MB for 129040-byte allocation
D/dalvikvm( 564): GC_FOR_MALLOC freed 0 objects / 0 bytes in 65ms
D/dalvikvm( 564): GC_FOR_MALLOC freed 7 objects / 67784 bytes in 48ms
D/dalvikvm( 564): GC_FOR_MALLOC freed 7 objects / 129272 bytes in 42ms
V/MmsProvider( 212): Insert uri=content://mms/9223372036854775807/part, match=11
D/dalvikvm( 5880): GC_EXPLICIT freed 1562 objects / 103600 bytes in 585ms
D/MainActivity( 5880): [HTCAlbum][MainActivity][onDestroy]: Begin
V/MmsProvider( 212): Query uri=content://mms/part/43, match=12
V/PduPersister( 564): Saving data to: content://mms/part/43
D/MediaPicker( 564): --------original uri: content://mms/part/43, type: null
V/MmsProvider( 212): Query uri=content://mms/part/43, match=12
V/MmsProvider( 212): Query uri=content://mms/part/43, match=12
D/UriImage( 564): ---------mContentType: image/jpeg
V/MmsProvider( 212): Query uri=content://mms/part/43, match=12
D/ComposeMessageActivity( 564): onMediaPicked:media: image/jpeg
I/MessageBodyEditor( 564): addMedia:> [email protected]
D/ComposeMessageActivity( 564): updateMessageBodyContentUI:
V/ComposeMessageActivity( 564): Message type: SMS -> MMS
D/MessageTextEditor( 564): resetCounter:SmsMode> false
D/ComposeMessageActivity( 564): checkReachRecipientMaxNumber> 0, updateUI> true
D/MessageBodyEditor( 564): EditableMediaViewFactory.create()[email protected]
I/EditableMediaViewImpl( 564): onFinishInflate:
D/MessageUtils( 564): loadThumbnailBitmap: content://mms/part/43
D/dalvikvm( 212): GC_FOR_MALLOC freed 11212 objects / 585848 bytes in 60ms
V/MmsProvider( 212): Query uri=content://mms/part/43, match=12
V/MmsProvider( 212): Query uri=content://mms/part/43, match=12
D/dalvikvm( 564): GC_FOR_MALLOC freed 1222 objects / 345504 bytes in 43ms
V/MmsProvider( 212): Query uri=content://mms/part/43, match=12
D/MessageUtils( 564): Create message thumbnail cache file: /data/data/com.android.mms/cache/PART_1282502974576
D/OnlineDataCenter( 5880): [HTCAlbum][OnlineDataCenter][unbindContext]: Begin
D/OnlineDataCenter( 5880): [HTCAlbum][OnlineDataCenter][unbindContext]: [email protected] size: 0
D/OnlineDataCenter( 5880): [HTCAlbum][OnlineDataCenter][unbindContext]: No more clients. release resources.
D/OnlineDataCenter( 5880): [HTCAlbum][OnlineDataCenter][unbindContext]: End 0
I/XT9_C ( 195): [loadDefaultDB] xt9_raw/ldb_0409.ldb size=98056 (loaded)
D/ThumbnailWorker( 5880): [stopWorking] Stop working, now join #-1, Decode Complete!!
I/XT9_C ( 195): [registerXT9LDB] ldb_0409.ldb loading [done]
D/XT9_ldb ( 195): wLdbNum=109, first wLdbNum=109, second wLdbNum=0
D/XT9_C ( 195): [registerXT9LDB] current LdbNum=109, First LdbNum=109, Second LdbNum=0
D/AlbumAdapter( 5880): set thread priority to normal
D/AlbumMapper( 5880): cancel current decode operation
D/AlbumMapper( 5880): cancel current decode operation
D/ThumbnailWorker( 5880): [stopWorking] Stop working, now join #-1, Decode Complete!!
D/AlbumAdapter( 5880): set thread priority to normal
D/AlbumAdapter( 5880): Join worker thread in destroy
D/AlbumAdapter( 5880): Join time: 0
D/dalvikvm( 195): GC_EXTERNAL_ALLOC freed 250 objects / 13312 bytes in 88ms
I/MainActivity( 5880): mWorker finishes jobs at onDestroy().
D/CollectionsActivity( 5880): [HTCAlbum][CollectionsActivity][onDestroy]: Begin
D/AlbColAdap( 5880): [HTCAlbum][AlbumCollectionsAdapter][onDestroy]: Begin
D/AlbColAdap( 5880): [HTCAlbum][AlbumCollectionsAdapter][onDestroy]: End
Yeah someone needs to fix this?
MrDSL said:
Have you asked Calkulin yet if he would let you know what he did to fix it? I would hope the open nature of everything he would gladly help.
Click to expand...
Click to collapse
Good idea Ill shoot him a pm
Calkulins rom sends out mms uncompressed?
Tapatalk'd on Evo
brol1k said:
Calkulins rom sends out mms uncompressed?
Tapatalk'd on Evo
Click to expand...
Click to collapse
His evio rom changelog says mms compression is fixed.
Something else I noticed, if I take an 8MP shot and try to MMS it, it gets squashed down to 60k. If I take a 5MP shot and MMS it, it gets squashed to 300K. Something is clearly screwed up there. So if I send a 5MP image it comes out 5x better than an 8MP image via MMS.
Hello xda,
I have the problem with all networks apps from busybox like ping, wget etc. BTW, the same apps from android work fine:
Code:
bash-4.1# which ping
/system/xbin/ping
bash-4.1# ls -la /system/xbin/ping
lrwxrwxrwx 1 root 2000 20 Jul 26 07:49 /system/xbin/ping -> /system/xbin/busybox
bash-4.1# ping google.com
ping: bad address 'google.com'
bash-4.1# /system/xbin/busybox ping google.com
ping: bad address 'google.com'
bash-4.1# /system/xbin/busybox wget google.com
wget: bad address 'google.com'
bash-4.1# /system/bin/ping -c1 google.com
PING google.com (209.85.148.99) 56(84) bytes of data.
64 bytes from google.com (209.85.148.99): icmp_seq=1 ttl=53 time=44.2 ms
--- google.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 44.271/44.271/44.271/0.000 ms
bash-4.1#
Any solutions?
Thanks
using jping
I have terminal IDE, which includes jping, so I can use:
jping google.com | sed 's/.*: \(.*\)/\1/' | xargs ping
And I get the name resolved for me.
I'm trying to build CM10.1 following these instructions: http://wiki.cyanogenmod.org/w/Build_for_p3110 for the GT-P3110 tablet (wifi only). I already installed the latest M build on the device but am getting the following output when running extract-files.sh:
Code:
~/android/system/device/samsung/p3110$ ./extract-files.sh
Pulling common files...
56 KB/s (5596 bytes in 0.096s)
299 KB/s (39248 bytes in 0.128s)
629 KB/s (2220784 bytes in 3.443s)
152 KB/s (15012 bytes in 0.096s)
remote object '/system/bin/smc.ini' does not exist
remote object '/system/bin/smc_pa.ift' does not exist
521 KB/s (180925 bytes in 0.338s)
529 KB/s (200010 bytes in 0.368s)
498 KB/s (189219 bytes in 0.371s)
542 KB/s (186061 bytes in 0.335s)
16 KB/s (1018 bytes in 0.059s)
16 KB/s (1017 bytes in 0.058s)
545 KB/s (297924 bytes in 0.533s)
371 KB/s (60536 bytes in 0.159s)
53 KB/s (5360 bytes in 0.097s)
57 KB/s (5508 bytes in 0.094s)
149 KB/s (14548 bytes in 0.095s)
57 KB/s (5732 bytes in 0.097s)
147 KB/s (14740 bytes in 0.097s)
189 KB/s (18880 bytes in 0.097s)
198 KB/s (18944 bytes in 0.093s)
251 KB/s (23340 bytes in 0.090s)
603 KB/s (471986 bytes in 0.763s)
324 KB/s (52896 bytes in 0.159s)
remote object '/system/lib/libion.omap4.so' does not exist
139 KB/s (14268 bytes in 0.099s)
95 KB/s (9620 bytes in 0.098s)
143 KB/s (14036 bytes in 0.095s)
317 KB/s (52011 bytes in 0.160s)
640 KB/s (5132164 bytes in 7.821s)
432 KB/s (99632 bytes in 0.224s)
635 KB/s (2444080 bytes in 3.755s)
385 KB/s (72976 bytes in 0.184s)
297 KB/s (38160 bytes in 0.125s)
Pulling device specific files...
270 KB/s (45380 bytes in 0.163s)
140 KB/s (13768 bytes in 0.095s)
235 KB/s (31256 bytes in 0.129s)
adbd is already running as root
Pulling common files...
remote object '/system/etc/powervr.ini' does not exist
remote object '/system/vendor/bin/pvrsrvctl_SGX540_120' does not exist
remote object '/system/vendor/bin/pvrsrvctl_SGX544_112' does not exist
remote object '/system/vendor/bin/pvrsrvinit' does not exist
47 KB/s (4812 bytes in 0.098s)
remote object '/system/vendor/lib/egl/libEGL_POWERVR_SGX544_112.so' does not exist
582 KB/s (445892 bytes in 0.747s)
remote object '/system/vendor/lib/egl/libGLESv1_CM_POWERVR_SGX544_112.so' does not exist
575 KB/s (371532 bytes in 0.630s)
remote object '/system/vendor/lib/egl/libGLESv2_POWERVR_SGX544_112.so' does not exist
remote object '/system/vendor/lib/hw/gralloc.omap4430.so' does not exist
remote object '/system/vendor/lib/hw/gralloc.omap4460.so' does not exist
remote object '/system/vendor/lib/hw/gralloc.omap4470.so' does not exist
remote object '/system/vendor/lib/libIMGegl_SGX540_120.so' does not exist
remote object '/system/vendor/lib/libIMGegl_SGX544_112.so' does not exist
remote object '/system/vendor/lib/libPVRScopeServices_SGX540_120.so' does not exist
remote object '/system/vendor/lib/libPVRScopeServices_SGX544_112.so' does not exist
remote object '/system/vendor/lib/libglslcompiler_SGX540_120.so' does not exist
remote object '/system/vendor/lib/libglslcompiler_SGX544_112.so' does not exist
remote object '/system/vendor/lib/libpvr2d_SGX540_120.so' does not exist
remote object '/system/vendor/lib/libpvr2d_SGX544_112.so' does not exist
remote object '/system/vendor/lib/libpvrANDROID_WSEGL_SGX540_120.so' does not exist
remote object '/system/vendor/lib/libpvrANDROID_WSEGL_SGX544_112.so' does not exist
remote object '/system/vendor/lib/libsrv_init_SGX540_120.so' does not exist
remote object '/system/vendor/lib/libsrv_init_SGX544_112.so' does not exist
remote object '/system/vendor/lib/libsrv_um_SGX540_120.so' does not exist
remote object '/system/vendor/lib/libsrv_um_SGX544_112.so' does not exist
remote object '/system/vendor/lib/libusc_SGX540_120.so' does not exist
remote object '/system/vendor/lib/libusc_SGX544_112.so' does not exist
Thinking "oh well, that can't be that bad" I continued with the build only for it to break with this message message:
Code:
make: *** No rule to make target `vendor/samsung/omap4-common/proprietary/system/etc/powervr.ini', needed by `/home/gardarh/android/system/out/target/product/p3110/system/etc/powervr.ini'. Stop.
make: *** Waiting for unfinished jobs....
I searched for the powervr.ini file on the entire device without luck.
Copying those files from a working CM10.1 build should work, right? Where would I find them in order to complete my build?
PS. This is my first attempt at ever building CM so don't rule out noobish mistakes
When I did same thing on Galaxy S3, it's working fine.
But When it did it on Galaxy Note2, it some times works. once out of 10 times works.
If you look below, ping is working. but it's not working with the domain name.
I did nslookup and it's working.
I browsed to a website throught IP and it's working. but it's not working with domain.
I tried to adjust DNS info in ADB shell but still not working.
it's working some times. but most out of times it's not working.
Please some body gives me any hint.
thank you.
--------------------------------------------------------------
C:\Users\JaeHo>ipconfig
Ethernet adapter Local Area Connection 9:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::99d3:e644:18aa:c0fe%49
IPv4 Address. . . . . . . . . . . : 192.168.137.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
---------------------------------------------------------------
C:\Users\JaeHo>adb shell
[email protected]:/ $ su
su
[email protected]:/ # netcfg rndis0 dhcp
netcfg rndis0 dhcp
[email protected]:/ # route add default gw 192.168.137.1 dev rndis0
route add default gw 192.168.137.1 dev rndis0
[email protected]:/ # ping -c5 philgo.com
ping -c5 philgo.com
ping: unknown host philgo.com
2|[email protected]:/ # ping -c5 168.126.63.1
ping -c5 168.126.63.1
PING 168.126.63.1 (168.126.63.1) 56(84) bytes of data.
64 bytes from 168.126.63.1: icmp_seq=1 ttl=52 time=105 ms
64 bytes from 168.126.63.1: icmp_seq=2 ttl=52 time=100 ms
64 bytes from 168.126.63.1: icmp_seq=3 ttl=52 time=100 ms
64 bytes from 168.126.63.1: icmp_seq=4 ttl=52 time=132 ms
64 bytes from 168.126.63.1: icmp_seq=5 ttl=52 time=100 ms
--- 168.126.63.1 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 100.747/108.058/132.237/12.238 ms
[email protected]:/ # getprop net.dns1
getprop net.dns1
[email protected]:/ # nslookup philgo.com
nslookup philgo.com
nslookup: can't resolve '(null)': Name or service not known
Name: philgo.com
Address 1: 116.122.36.242
[email protected]:/ # ip route show
ip route show
default via 192.168.137.1 dev rndis0
192.168.137.0/24 dev rndis0 proto kernel scope link src 192.168.137.131
When setprop does not set the prop... :
Code:
iptables -t nat -A OUTPUT -p udp --dport 53 -j DNAT --to-destination 8.8.8.8:53
I've been trying different ways to connect to this tablet, but the connection is really slow/laggy/sluggish. When I connect over SSHDroid to this tablet, typing and cursor moving goes slooow - fast - slooow - fast - sloow.
It used to sport Samsung Android 5.0.2. I've flashed the latest LineageOS Android 7.1 (rooted), but nothing changes. I've tried setting the gouvernor to performance, but nothing changes.
In contrast, I have a Xiaomi Mi 5 (Stock MIUI Android 7, rooted) with SSHDroid, and everything goes smoothly as you would expect.
I have no idea what even causes this. I would like to fix this. It's a nice tablet in every other aspect. Does anyone have an idea?
The responsiveness of the cursor in OpenSSH and XSDL Xserver seems to be analogous with this:
Code:
PING 192.168.1.9 (192.168.1.9) 56(84) bytes of data.
64 bytes from 192.168.1.9: icmp_seq=1 ttl=64 time=12.4 ms
64 bytes from 192.168.1.9: icmp_seq=2 ttl=64 time=1428 ms
64 bytes from 192.168.1.9: icmp_seq=3 ttl=64 time=431 ms
64 bytes from 192.168.1.9: icmp_seq=4 ttl=64 time=2500 ms
64 bytes from 192.168.1.9: icmp_seq=5 ttl=64 time=1503 ms
64 bytes from 192.168.1.9: icmp_seq=6 ttl=64 time=503 ms
64 bytes from 192.168.1.9: icmp_seq=7 ttl=64 time=2572 ms
64 bytes from 192.168.1.9: icmp_seq=8 ttl=64 time=1575 ms
64 bytes from 192.168.1.9: icmp_seq=9 ttl=64 time=576 ms
64 bytes from 192.168.1.9: icmp_seq=10 ttl=64 time=12.4 ms
64 bytes from 192.168.1.9: icmp_seq=11 ttl=64 time=1643 ms
64 bytes from 192.168.1.9: icmp_seq=12 ttl=64 time=637 ms
64 bytes from 192.168.1.9: icmp_seq=13 ttl=64 time=11.7 ms
64 bytes from 192.168.1.9: icmp_seq=14 ttl=64 time=1704 ms
64 bytes from 192.168.1.9: icmp_seq=15 ttl=64 time=697 ms
64 bytes from 192.168.1.9: icmp_seq=16 ttl=64 time=11.9 ms