Related
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, I'm new here, I searched a lot through this forum, but no result. My problems:
1) When I'm typing on hw qwerty keyboard, it very often types double (sometimes even triple) letter, some letters doesn't work at all time-by-time (mostly "l" and space key). Its really annoying when you wanna type on hw qwerty (much more comfortable then sw keyboard for me)... Is here anyone with same problem or with solution?
2) Everyone knows that notification color LED light at the top-right corner , but mine has a software bug or something. After buying the phone, everything was good, but after few weeks, this led starts lighting blue (even not blinking, just keep lighting).. When I press power button (phone goes to standby) this LED's intensity goes lower, but when I wake phone up, LED starts lighting blue more intensively (like you have 4 levels of intensity: 0-no lightening, 1-the one in stand-by, 2-when the screen is on, 3-same intensity as blinking when new msg or so).. I tried to restore phone, but same as before - at the beginning no problem and after few weeks, blue led light is back.. I even tried turn off, pull the battery, get it back, but in the moment I pressed the power button, the blue LED starts lighting again.. I tried even one app which can set the color of LED (Blink?) but no help.. Then I thought that I have some app installed which doing this, but I didn't find anything.. Please help me with this if anyone can..
3) I noticed that in my phone are installed few apps which I'm really not using at all and even some of them are not in drawer.. These apps are in phone since I unpacked the phone, it is:
- News, Weather and News, ESMusica, HipHopOfficial, RevolverTV, Rock On Altitude, TrueCountry
Will some of the root apps and then just uninstall those useful apps help me?
Sorry for this long thread, but I didn't know how to write it, to make it understandable. Thanks a lot for your help..
To your LED problem.. if a flash doesnt fix it.. nor a Reset.. i would mail the support.. and send it to repair.. since the updates are very very slow on motorola...
And your Spam apps.. well those can be removed by Titanium backup and freezing them (See: Freeze Motoblur and Other apps) Or you can use root explorer find the right APK's and remove them fully of your device.. (Works via Shell as well by using "RM" to remove files..) (you need root though isnt hard to get via z4root or even step for step root like i did)
thx
thanks a lot .. I rooted my M2 and freeze those apps..
then I downloaded root explorer and made some digging through the phone root files/folder, now here is my question: when you go to /sys/class/leds there are some files, included the "blue" file.. it has no extension and I can't copy it to SD.. I'm worried to delete it, when have no backup of it.. also there is in folder /sys/devices/system/leds/leds0/ file "event" which might be useful to.. but I wanna ask, might this (delete/edit these files) solve my problems with the LED light ???
and still don't know what to do with the keyboard
I think the Keyboard problem is serious and will be fixed at some point.. Also Try turning off every keyboard setting like: "Auto add spaces" "Auto capitals" and those.. maybe that helps ive seen it on another post
to your LED problem.. i never touched the files you talked about.. i wouldnt delete them. . first copy them to some place .. and look what they are .. maybe even google the name of it. some are stock files and similiar to other phones!
Well i just touched them now ... anyway they seem to be not accessable i dont know.. "cd: can't cd to /sys/class/leds/blue/brightness/" nor can i copy them or even CAT them.. it just cant be accessed... (i tryed the devices one aswell)
seem to be placeholders or something that the kernel access's .. i guess... im not that pro on this.. all i can do is c++ and thats not even close to this .. on Linux Kernels and Linux system i only have basic skills.. i only work on Windows NT
I tried it too, but same result.. in emulator I typed cmd but permission is denied.. in file manager it can'n be deleted.. I guess the only thing I can do right now is wait till gingerbread for M2 will be released (also for keyboard issue).. thanks a lot for your help ;-)
Sent from my Milestone2 using XDA App
Hi, I have the same problem with the keyboard.
Is there any solution yet?
http://forum.xda-developers.com/showthread.php?t=1058544 have a look. it has been there since forever
thnx a lot
I'll give it a try.
Not sure what style lock screen my android install uses but it's the one like a rainbow shape that you drag downwards and it's awful as I keep finding the phone unlocked when I take it out of my pocket.
I'd like to change the lockscreen to either what I think is the Frodo one (sideways sliding icons for lock and volume/speaker mode?), or the X10 one which is like quarter circle swipe.
Is there some app (free ideally!) that will let me do this or a manual way I can do it if there's a source for necessary files (without too much grief).
I read that if I delete the htclockscreen.apk file then the phone will revert to the froyo one (as I use a froyo build), but when I try that with a file manager I can't delete the file - presume it's a permissions thing or something?
Thanks for any help!
ETA that most lock related apps I see in the market seem to relate to disabling locks rather than anything to change the one you already have.
Forgot to say I'm trying out Lockbot at the moment and it sort of works but it seems a little hit & miss.
In particular when you unlock the phone and it normally makes that little click sound (if you haven't turned that off of course), it sounds more like a machine gun before the lock screen comes on, and that worries me a little bit that there's something not right going on.
You could try a-lock from the Market,which is somewhat like S2U2
You could flash a cyanogenmod rom like this onetycoon cm7 comes with 4 different lockscreens ..or try simply lockscreen from the market..
Had the same issue of phone unlocking with the "arch style locker" so bought widget locker, which works perfect, it allows you to have different styles of lock screen & add widgets, cost next to nothing, I'd recommend it.
www.appbrain.com/app/widgetlocker-lockscreen/com.teslacoilsw.widgetlocker
But if you really don't want to pay for a lock screen, I've attached a different lockscreen for you to try.
Worked fine for me before I bought WL, see my sig for rom, but as always when changing system files, use at your own risk, tho there shouldnt be a problem.
The LS with 2 circles was extracted from a htc dhd build (free), the other pic is WLocker (paid)
Try if you like... don't try if you like, just an option
I feel CM7 may be your best shot, I use and love it! Very easy to customize.
kwtf said:
You could flash a cyanogenmod rom like this onetycoon cm7 comes with 4 different lockscreens ..or try simply lockscreen from the market..
Click to expand...
Click to collapse
Sent from my HTC HD2 using Tapatalk
Thanks for the replies dudes.
Will have a look at A-lock. And Simply Lockscreen (or did you mean it's simply called 'Lockscreen'?). Not being facetious there - just clarifying!
Kam333 - thanks for that file mate. Will check it out definitely.
I am now trying Wlocker as Lockbot was too erratic. Wlocker seems to be ok so I might end up buying it but I like to try out options first before deciding.
That Rom is tempting too I must admit but the bit about the high drain on BT standby concerns me a bit as I leave BT on all the time.
Decisions eh! But I appreciate all the suggestions, thanks.
Not sure how to use your one Kam - when I run an installer against the apk file it only gives be an option to UNinstall it, which I guess means it just maybe has the same name as the existing one. Am assuming once an uninstall is successful then it will allow me to install it, but why won't it let me remove the other one first?
I've tried that but it failed. Similar problem to not being able to delete the standard apk file from its directory either.
Hey
You need to push the 2 files to your system folder,
For the build I'm using, I placed the files in a folder [DL_update/root/system/app]
This goes on the root of your sd card then reboot,
You should check on your build thread for the name/path of the folder "dl_update" is specific to the build I'm using, the rest should be the same tho.
If you have any probs let me know.
Kam
Thanks - have tried doing that but with a file manager I can copy ok, but paste is not available for some reason when I try to overwrite the existing ones.
Thought I'd do it via the PC as well but that won't work as I can't see the folder structure on the phone itself, only the SD card.
I'm now trying Lock 2.0 which 'would' be great except that when locked, you can use the hard keys (home key and power key I think) to bring up menus, some of which can basically unlock the phone so despite having a better slider I still find it unlocked in my pocket, and doing stuff like trying to dial my mum while I'm having a swearing contest etc.
I can't find a menu option in the program to disable these menus but I'm sure they wouldn't have been stupid enough to make a decent lock app that is full of holes like that and couldn't be disabled?
Cret said:
Thanks - have tried doing that but with a file manager I can copy ok, but paste is not available for some reason when I try to overwrite the existing ones.
Thought I'd do it via the PC as well but that won't work as I can't see the folder structure on the phone itself, only the SD card.
I'm now trying Lock 2.0 which 'would' be great except that when locked, you can use the hard keys (home key and power key I think) to bring up menus, some of which can basically unlock the phone so despite having a better slider I still find it unlocked in my pocket, and doing stuff like trying to dial my mum while I'm having a swearing contest etc.
I can't find a menu option in the program to disable these menus but I'm sure they wouldn't have been stupid enough to make a decent lock app that is full of holes like that and couldn't be disabled?
Click to expand...
Click to collapse
Hey,
the lockscreen is a system file, you wont be able to modify/edit systems files without root permissions, you'll need to use a root capable explorer such as Root Explorer or ES in root mode.
or use the method in my last post.
if you view this & not logged into xda ive just pm'd you
kam
Heya, new to fiddling with root files but really wanted to get rid of camera click. Followed advice about renaming camera_click.ogg in terminal Emulator using:
ADB shell
SU
mount -o remount,rw /dev/block/mtdblock4 /system
mv /system/media/audio/ui/camer_click.ogg /system/media/audio/ui/camera_click.ogg.old
(source: www droidforums net/forum/droid-hacks/23107-droid-remove-camera-click-shutter-sound html) - sorry new poster not allowed to post url
Now have issue when open stock camera and vid in Motorola Atrix (gingerbread 2.2.2) where:
1) camera opens, but have lost all previous images.
2) camera takes silent shot
3) camera 'locks' open and can't return to 'desktop', can't view image taken,, can't access menus etc
Basically camera is stuffed...
is there a solution, is there code to go back and follow some of the other advice in here etc?
It is a setting. What's the point?
Sent from my MB860 using xda premium
it's a setting what's the point? Thanks for taking the time to reply. I did mention this is all new to me. I asked a question because i do't know the answer. It's a swttibg whats the point is hardly helpful.
To anyone else, i'd appreciate any help or advice. As i mentioned i'd just like to undo what i've done usibg script i found on another forum. looking forward, hopefully, to hearing from you!
have you tried to add the following line to local.prop file located in /data?
ro.camera.sound.forced=0
If you don't have the file then just create the file and add it, otherwise append it to the end of file.
File permission is: 0644
Good Luck
I never heard of adding ".old" on the end of the file. I always add ".bak", then reboot. Works everytime.
EchoK8 said:
it's a setting what's the point? Thanks for taking the time to reply. I did mention this is all new to me. I asked a question because i do't know the answer. It's a swttibg whats the point is hardly helpful.
To anyone else, i'd appreciate any help or advice. As i mentioned i'd just like to undo what i've done usibg script i found on another forum. looking forward, hopefully, to hearing from you!
Click to expand...
Click to collapse
I giggled when I read gingerbread 2.2.2
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Thanks for pointing that out, that gave me a good laugh to start the day off.
Phalanx7621 said:
I giggled when I read gingerbread 2.2.2
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Click to expand...
Click to collapse
EchoK8 said:
it's a setting what's the point? Thanks for taking the time to reply. I did mention this is all new to me. I asked a question because i do't know the answer. It's a swttibg whats the point is hardly helpful.
To anyone else, i'd appreciate any help or advice. As i mentioned i'd just like to undo what i've done usibg script i found on another forum. looking forward, hopefully, to hearing from you!
Click to expand...
Click to collapse
I was on my phone at the time (tiny keyboard) and was trying to succinctly say that if you open the camera app and touch "settings", there is an option to quiet the click.
When I first read your OP I didn't notice that you identified Gingerbread as v2.2. You are confused. v2.2 was named Froyo (frozen yogurt). Gingerbread is v2.3. My answer relates to Gingerbread. If you are actually on Froyo, I don't remember if the setting was available on that release.
So, in Gingerbread silencing the camera is a setting and there is no point performing internal surgery.
Yep, ok, noob blunder. Novice blunder, amatuer, beginner whatever blunder. Glad you all got a giggle, and thanks for pointing it out. I was told at the shop it's Gingerbread. The About phone states 2.2. So, if that makes it Froyo then great, i've learnt the basics today. Thanks for your help again!
Well re- the settings, froyo or otherwise, yes there is a setting to turn sound off. You turn it to off and it still makes the click sound, volume can't be altered. Hence diving off the deep end and into something i know very little about - internal surgery!!
Live4nyy - is there a simple way to rename to .bak (you see my level of expertise here - none! - in asking).. forward some script for me at all?
or
CSharpHeaven that sounds gr8... any way to explain to a complete novice how to do that?
I thank anyone who sticks with me to reply after this MUCHLY as you know you are dealing with a friking novice
Seriously....why would you want to silence your camera again?
Do you have root? If yes, then you can just use any file manager that has root access, ES File Explorer works I've heard, and just go to the folder where the sound file is (/system/media/audio/ui) and just select to rename the file and add ".bak".
EchoK8 said:
Yep, ok, noob blunder. Novice blunder, amatuer, beginner whatever blunder. Glad you all got a giggle, and thanks for pointing it out. I was told at the shop it's Gingerbread. The About phone states 2.2. So, if that makes it Froyo then great, i've learnt the basics today. Thanks for your help again!
Well re- the settings, froyo or otherwise, yes there is a setting to turn sound off. You turn it to off and it still makes the click sound, volume can't be altered. Hence diving off the deep end and into something i know very little about - internal surgery!!
Live4nyy - is there a simple way to rename to .bak (you see my level of expertise here - none! - in asking).. forward some script for me at all?
or
CSharpHeaven that sounds gr8... any way to explain to a complete novice how to do that?
I thank anyone who sticks with me to reply after this MUCHLY as you know you are dealing with a friking novice
Click to expand...
Click to collapse
I'd like to replace my shutter sound. Does anyone have a sound file of a shotgun blast/ slide rack?
Thannnks
island-guy said:
Seriously....why would you want to silence your camera again?
Click to expand...
Click to collapse
i actually dont want or need to silence it again. my query is how to restore my camera to a mode where it is functional bcs at the moment its stuffed. If theres a simple string to go back that'd be ideal.
live4nyy said:
Do you have root? If yes, then you can just use any file manager that has root access, ES File Explorer works I've heard, and just go to the folder where the sound file is (/system/media/audio/ui) and just select to rename the file and add ".bak".
Click to expand...
Click to collapse
Ok, got 'root explorer'... so simple just to enable R/W and rename.. Thanks. Changed to .bak . Seems better, actually appears to take photos and has more functionality than after i ran that script... but
I don't know what that original script did. Here's what using my built in camera is like:
1) Turn Camera on. Opens, appears normal. Take photo fine. Thumbnail (link to camera roll) in bottom corner as per usual, which disappears after a few seconds as per normal.
So far so good.
2) After taking another photo decide to click on thumbnail to open camera roll. Camera Roll opens but says there are no pictures to display. return (via 'back' menu button) and the thumbnail of the images is there again. Ok, weird.
3) Try take another photo... nothing happens, wait a few seconds and camera switches off back to ;desktop'. Try open camera again but no dice. In fact all phone functionality gone, frozen, locked up, including menu buttons below screen. Put phone to sleep by pressing rear button briefly. Press rear button again to awake. Unlock swipe is slow to respond (a few seconds) and then back to main desktop screen. Can once again open camera. Repeat process from dot point 1).
4) next time go to camera roll, this time locks up on camera roll (which has no images to display again). Sleep and wake up camera, slow swipe unlock, can take photos again when open camera. repeat step 1 - 3 again!
5) Sleep, wake up phone. This time straight to gallery instead of camera. Gets stuck telling me it's loading media files. Frozen.
6) sleep- wake - slow swipe unlock. This time to video. Same thing as camera. Frozen.
I could go on.... but im sure the idea is clear!
used root explorer to simply remane camera_click.ogg to original name. Same as above
Tried camera zoom fx app incase it was the built in camera app. This won;t even open - well, it starts but then says i need to force it to close.
Does this need a factory reset??!
Ta
Have you rebooted? Maybe try and go into "Manage Applications" under the "All" tab and find the camera and "clear data"?
EchoK8 said:
Ok, got 'root explorer'... so simple just to enable R/W and rename.. Thanks. Changed to .bak . Seems better, actually appears to take photos and has more functionality than after i ran that script... but
I don't know what that original script did. Here's what using my built in camera is like:
1) Turn Camera on. Opens, appears normal. Take photo fine. Thumbnail (link to camera roll) in bottom corner as per usual, which disappears after a few seconds as per normal.
So far so good.
2) After taking another photo decide to click on thumbnail to open camera roll. Camera Roll opens but says there are no pictures to display. return (via 'back' menu button) and the thumbnail of the images is there again. Ok, weird.
3) Try take another photo... nothing happens, wait a few seconds and camera switches off back to ;desktop'. Try open camera again but no dice. In fact all phone functionality gone, frozen, locked up, including menu buttons below screen. Put phone to sleep by pressing rear button briefly. Press rear button again to awake. Unlock swipe is slow to respond (a few seconds) and then back to main desktop screen. Can once again open camera. Repeat process from dot point 1).
4) next time go to camera roll, this time locks up on camera roll (which has no images to display again). Sleep and wake up camera, slow swipe unlock, can take photos again when open camera. repeat step 1 - 3 again!
5) Sleep, wake up phone. This time straight to gallery instead of camera. Gets stuck telling me it's loading media files. Frozen.
6) sleep- wake - slow swipe unlock. This time to video. Same thing as camera. Frozen.
I could go on.... but im sure the idea is clear!
used root explorer to simply remane camera_click.ogg to original name. Same as above
Tried camera zoom fx app incase it was the built in camera app. This won;t even open - well, it starts but then says i need to force it to close.
Does this need a factory reset??!
Ta
Click to expand...
Click to collapse
live4nyy said:
Have you rebooted? Maybe try and go into "Manage Applications" under the "All" tab and find the camera and "clear data"?
Click to expand...
Click to collapse
Thanks L4NYY.. yep had rebooted. Tried clearing data but all the same
Had a quick look in the internal storage DCIM folder..All files appear to be there. The one vid file has a play button icon. The .jpg's have the android robot icon. I don't know what was there before. Trying to open the files from here freezes the phone.....
Connecting usb and viewing dcim shows that any images taken since the change to camera_click.ogg appear unknown thumnails in the PC explorer..and can't be opened on the PC via USB connection or when stored locally on the PC itself 'can't display this is an empty file' . This is probably all irrelevant but might be useful to someone, somehere...
Have just noticed today that battery was going flat very quickly. Realised since rooting and using that script (can't decipher which) that location services are no longer working, hence apps that provide location services are continually searching and draining battery. Yes i can turn those services off, but wouldrather resolve the issue!
I'm thinking more and more like factory reset Any thoughts?
Just factory reset. Used Astro File Manager to backup apps before hand, which for interest worked well (although did have to reinstall one by one). Of course Appstore keeps a lsit of purchased apps as a failsafe for thsoe.
After rest, reinstalled apps, including Root Manager. Simply followed Live4NYY's advice, renamed camera_click.ogg to camera_click.ogg.bak
All issues described earlier resolved. Camera functional and silent.
just goes to show sometimes you should ask noob questions. I tried following instructions on a post to avoid annoying the experts with a mum-mum dad-dad question! Anyhow, thnaks to live4nyy for taking the time.
Ciao
The ".bak" just stands for "backup". It will essentially hide any file/app and keep it from running (which in turn frees up RAM). So if you had a system app that you don't use you can just add ".bak" and it would be the same as freezing it. It's much safer than deleting files and apps as you can always go back and remove the extension (and reboot) and it will be back to normal.
EchoK8 said:
Just factory reset. Used Astro File Manager to backup apps before hand, which for interest worked well (although did have to reinstall one by one). Of course Appstore keeps a lsit of purchased apps as a failsafe for thsoe.
After rest, reinstalled apps, including Root Manager. Simply followed Live4NYY's advice, renamed camera_click.ogg to camera_click.ogg.bak
All issues described earlier resolved. Camera functional and silent.
just goes to show sometimes you should ask noob questions. I tried following instructions on a post to avoid annoying the experts with a mum-mum dad-dad question! Anyhow, thnaks to live4nyy for taking the time.
Ciao
Click to expand...
Click to collapse
Hi can't post yet in development threads.
But I'd like to know why there is an issue for ICS either not seeing or mis-reporting an empty sdcard. Even though it shows a 'used' value.
I've searched about and read a few Q's about the issue and even claims of apparent fixes.
But I can't find any, but I can't figure why the problem in the first place.
I just 'zed's an empty card.
there is no problem with the sd card it was located in emmc.
go get io file manager or es file manager and go to directory /mnt/emmc.
cheers
Format
Is the card formated? Could be the problem.
Yes it is half full (16gb) and used daily Before flashing.
So is there a reason the card is. 'hidden' in eec?
and how do apps know where it is assuming I can remember as well.
I also don't see the root in stock FM, I wonder what its doing when it does a media scan.
So anyway how do I make it normal?
Many thanks
Also got a say luving this ice (slim)
But a couple of issues with wifi.
First someone like me might not know on the settings page, you have the regular switch, but to configure and choose a network, press the txt liable to the same switch.
Not exactly obvious
And 2nd wifi absolutely eats battery. maybe there's a way to reduce power etc?
cleverdicky said:
Also got a say luving this ice (slim)
And 2nd wifi absolutely eats battery. maybe there's a way to reduce power etc?
Click to expand...
Click to collapse
Change the Modem File. Different Modemfiles have different battery drain´s.
Also you can change the Kernel, the is a relationship ( right Word ?) between Modem & Kernel.
Thanks, yes I agree but was a struggle to get this working as it was for UK. (Do all devs live in the us or Poland)
I use the jpy modem & busy box but even that was taxing for my poor brain.
One other thing I found using ics is appalling sms.
Terrible button layout that doesn't show contacts and a tiny type area again A bad point for android anyway.
But if you go through phone button to see contacts, if you select a mobile no and start typing, it changes to home number.
Also if your not carefull, it just dials and hard to cancel.
Annoying and quite a disappointment .
I'm just going to see if go SMS does a better job.
Shame to have to though.