Support and General Use > Hardware
Sansа Clip Zip - Improve battery life
johnb:
--- Quote from: saratoga on January 01, 2015, 10:26:53 PM ---Looking at the as3525 datasheet, I think we are clocking the DBOP too high due to increased PCLK, and the DBOP is accessed during LCD update, so lets try lowering it:
http://web.mit.edu/mgg6/www/rockbox-fuzev2_2.7z
--- End quote ---
That was a quick test:
Firmware update, USB unplug, Rockbox asks if it should reboot due to the new firmware -> yes:flickering display, stays in rolo-> screen goes white
Restart, stays in Rockbox boot screen: Boot Vers. 4.0, display turns off due to timeout, moving wheel -> Boot screen blends into grey screen
Restart by plugging USB ->screen goes grey/ white
USB connection sometimes works, sometimes doesn't. At least I was able to replace the .rockbox folder without booting into the original firmware.
In short: even worse than the first build, since I don't get out of the boot screen.
johnb:
--- Quote from: saratoga on January 02, 2015, 01:36:56 AM ---Setting PCLK to 64MHz fixes the problem on my Clipv2.
Edit: Heres a Fuze v2 build with the lower clock. Would also be interesting to know if this one works:
http://web.mit.edu/mgg6/www/rockbox-fuzev2_64MHz.7z
--- End quote ---
Reboot question: yes. Stays in 'Rolo executing'. Screen timeout.Scroll wheel -> white screen.
Power down. Fresh reboot: Stays in Rockbox logo/ Boot Ver. 4.0 screen. Need to power down.
Connecting to USB: USB symbol appears, drive mounts. Screen timeout, moving wheel turns on grey screen or fades from Rockbox logo to grey screen. USB still works.
Edit: Since I just noticed that I had created some recordings in the root dir, I figured that navigation somehow was possible even though I was still in the logo screen.
So new trial: I prepared a track that I could easily navigate to blindly. Rebooting, I can navigate to the song eventhough I still see the Rockbox boot screen. After starting the song, volume change and skipping to the next song is possible. The screen is alive though distorted. Moving the wheel - thus changing volume- every now and then the screen updates and I can see an undistorted WPS screen. Triggering any further update it distorts again.
saratoga:
I think devices with a wheel will boost whenever the wheel is used. Here is one more build:
http://web.mit.edu/mgg6/www/rockbox-fuzev2_64MHz_2.7z
johnb:
I was about to say this is the most stable one. Tried the following:
1. Boots properly into the main menu. Browsing the main menu with the wheel for a while, it freezes.
2. Reboot, go immediately to Files and select the first song, it plays. From WPS trying to go to Main Menu/ System it crashes:
undef. instr. @ 300C7BF8 sp: 308049E0
3. Again going directly to Files and play a track, in WPS I am fine: screen updates (long title scrolling, track time counting), FF, pause, resume, screen turns off and on again on activity, track skipping back and forth.
From WPS going to the file browser (center button), playback stops with some crackling noise, then freezes and silence.
4. Boot into main menu, just scrolling for a while, going into the settings menu.
The wheel is very sensitive, don't manage to select the General Settings for a while, cursor rather jumps. Finally I manage to hover over the General Settings, but neither middle button nor right click does anything.
Finally freezes.
5. Again happily in the WPS. Using the Home button to invoke the Playlist, selecting the next track it crashes:
undef. instr. @ 30804A6C sp: 308049A4
Screen turns off.
And this is where I take back the 'most stable' statement. I am not able to power down or reboot (>30s power button; USB connection, ....)
Inserting the headphone I hear two clicks, so I hope it's just not responding and will wait for the battery to drain :-(
saratoga:
Usually if it crashes bad like that it will eventually reboot if you keep holding power, although it can take a while.
To summarize testing:
Zip: Works fine.
Clip+: Seems to be working, but needs slightly higher voltages on some devices.
Clipv2: Will not work at PCLK = 96MHz, but 64 MHz works fine (verified on skips device as well).
Fuzev2: Lowering PCLK helps, but does not solve the problem.
Since 64MHz works, but 96MHz seems limited to newer models, I wonder if some of the earlier revisions of the 3525v2 had the v1's limit of 65MHz for the PCLK. Would be interesting to know how much highe PCLK can go on the Zip too, in case we are already out of spec.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version