|
#1
|
|||
|
|||
|
Originally I had european firmware (2.2.5E) on it and it worked fine.
But I wanted a fm radio and swiched to american 2.1.0A using the hint from previous thread. And it works . The radio is great. I even upgraded from 2.1.0A to 2.2.5A using sandisk's updater program. My problem is that now font format (when in play mode) is a little bit bigger (and somehow bold) so it cannont fit ond the screen perfectly. When browsing songs it cannot write song name instantly. Instead I get bunch of merged letters in first second that moment after becomes song name. Artist's name cannot fit on screen at all, I see first 5 or 6 letters. Please tell me if this is normal for american firmw. or am I an isolated case? Can it be fixed? On europen version this was not an issue, font size was smaller and everything could be seen normally. Is this a price for a fm radio. It seems I cannot go back on european. Well, I suppose you win some lose some
|
|
#2
|
|||
|
|||
|
|
|
#3
|
|||
|
|||
|
Sorry to hear about your problem with fonts.
My Player was working fine without problems with fonts. I updated my m230 player to 2.2.5A and I can also confirm that my player has now got screwed up fonts. So now I'm in the same boat as you! I've tried downgrading to the previous U.S Firmware and also reverting back to the Europe Firmware (by a lot of messing about) But it would appear that the 2.25A update changed something that can't be altered by the earlier firmware installation. I think we are stuck with this, unless the 2.25a firmware update has an unrelated bug in it which is causing this font issue. Can anyone confirm they are getting the problem without installing the latest us 2.25A firmware? |
|
#4
|
|||
|
|||
|
I have reported the problem to sandisk's support page. No response yet.
I'll put on this forum whatever I get from them (If I get something at all) I suppose we can't do anything about it but wait for another firmw. release. bye |
|
#5
|
|||
|
|||
|
Yup, count me in. I just updated my firmware today and I've got the same problem.
I've opened a support ticket with Sandisk and asked about this, but they haven't provided me with a solution yet. I'm going to post a link to this forum in my ticket so that they have a better idea of what I'm trying to describe and don't blow me off with a generic "we don't support that blah blah blah". |
|
#6
|
|||
|
|||
|
This is the response I got to my support request, along with the usual "we don't support anything but Windows XP" line that most companies like to give out. Can someone try this and let us know if it works? If using Windows Media Player is the only solution to this, I'm probably going to be unable to enjoy the fix.
==== We recommend that you transfer your music files from your computer to your Sansa m260 by using the “SYNC” function of your Windows Media Player version 10 with the Sansa m260 in MTP (Media Transfer Protocol) mode. To set your Sansa m260 in MTP mode: Please go to the “Settings” menu, then press “Select”. Then, please select “USB Settings” and then select the option that either says “Auto Detect” or “MTP” and not the “MSC” option. Then, please connect your Sansa m260 to your Windows XP computer through an USB port preferably located near the power hub (usually the rear USB port) or to an external self powered USB hub. Then, please launch your Windows Media Player version 10 and go to the “Library” tab first to organize your music file lists. After organizing your music files, please go now to the “SYNC” tab and verify first if on the left pane is the lists of music files you want to transfer and on the right pane is the internal memory of your Sansa m260. Once verified, please click on “Start SYNC” to initiate transfer. Once transfer is complete, please unplug your Sansa m260 and test if the music files will play. |
|
#7
|
|||
|
|||
|
Then it comes back to this for me: http://www.anythingbutipod.com/forum...ead.php?t=2866
|
|
#8
|
|||
|
|||
|
Well, I tried their procedure and it didn't fix the problem. (The sync was dog slow, too). Sandisk closed my support ticket and wanted to RMA my device, but I was able to exchange it at the store for a new one. So now I'm back to glorious 2.2.1A with sane fonts and fast transfers to and from my Linux system. You can bet your $%& I'm not upgrading the firmware on this player either.
Seriously, an RMA? How about a firmware update, better QA procedures, or a method for going back to a previous version that works... Ironic thing about this whole hassle--the bug I had hoped to fix by upgrading the firmware, which is the way some files always show up as an Unknown artist, even though they have ID3 tags, wasn't even fixed in the 2.2.5A firmware. I did get to re-visit the "We don't support any platform other than Windows XP" get out of jail free card companies still try to use, even when the issue at hand has absolutely nothing to do with the OS on the client computer. |
|
#9
|
|||
|
|||
|
Ok i was have same problem and sandisk support give me that.
To instal: Make sure the Sansa is in MSC mode. Download the attached zip file. Extract the files. Copy the files to the CONFIG folder of the player. Now disconnect and turn on the Sansa, then it should update the fonts. Good luck ;P |
|
#10
|
|||
|
|||
|
Quote:
|
|
#11
|
|||
|
|||
|
Thanks for sharing that. It's frustrating that the same support dept. wanted to RMA my player, instead of providing a software fix that I could easily download and apply myself.
I'm still not sure I want to upgrade my firmware to 2.2.5A, even with this font fix. What is different between the two firmware releases? Are there release notes or a list of bug fixes/feature improvements for the firmware releases? |
|
#12
|
|||
|
|||
|
Phew I'm glad we got that fix.
It eases the guilt, since it was me that posted the message that broke everyone's players. I didn't personally feel like contacting Sansa to say, hi I've just hacked your player, can you fix it for me? Still it broke my player as well, so thanks for that. |
|
#13
|
|||
|
|||
|
Quote:
d. |
|
#14
|
|||
|
|||
|
THANKS! This works perfectly.
I wish Sandisk would have been on top of this sooner. I ran into this problem right after upgrading a brand new m260 to 2.2.5, but I couldn't remember if it worked ok prior to updating. I already have an m240 updated to 2.2.5 that worked flawlessly. I tried forcing an older m200 series firmware on it, but that rendered it useless--wouldn't turn on anymore or be recognized when connected to PC. RMA'd it, and with hesitation, updated the replacement only to get the same irritating font problem. THANKS AGAIN for posting this fix.
|
|
#15
|
|||
|
|||
|
Does it works with sansa m230 ?? Please reply
|
|
#16
|
|||
|
|||
|
Yes, it does!!! Thanks a lot!!!
|
|
#17
|
|||
|
|||
|
Does anyone have a copy of the m240 firmware, or know a way to get it, I am interested in trying a Rockbox port but need firmware (to upload over there so that anyone can study it and try to make something of it)
|
|
#18
|
||||
|
||||
|
Quote:
|
|
#19
|
|||
|
|||
|
Quote:
|
|
#20
|
|||
|
|||
|
Just updated and have the same problem. Please repost the fix
|
![]() |
«
Previous Thread
|
Next Thread
»
| Thread Tools | |
| Display Modes | |
|
|
abi Reviews
All times are GMT -5. The time now is 02:52 PM.









. The radio is great. I even upgraded from 2.1.0A to 2.2.5A using sandisk's updater program.


Linear Mode
