Rockbox Development > New Ports
Sony NWZ-E370
pamaury:
Hi,
I'm going to buy another one. In the mean time, some questions:
* Does that happne with the OF ?
* Can you try the following procedure and report the result ?Procedure:
* Boot player, go to System > Debug (keep out) > View hardware info
* In the list, go to button and press select: the screen should display a big table with many numbers
* NOTE: I don't have the player, it is possible the table doesn't fit on the screen or is not exactly as described
* One of the lines should be "vddio: 0[2/2] (raw=XXX) ...."
* If you press up and down, the raw number above (XXX) should change: confirm this
* Some lines should be "BBB: 0[2/2] (raw=YYY) ...." where BBB is a button name like "up" or "down"
* Repeat the following for all offending buttons (like left, home, etc) :
* press the button, write down the value YYY in the corresponding line together with the corresponding VDDIO value
* release the button, write down values as above
* press up or down several time to change the value of vddio
* press the button, write down values as above[
* release the button, write down values as above[
mxyzptlk:
--- Quote from: pamaury on February 13, 2016, 10:20:33 AM ---Hi,
I'm going to buy another one. In the mean time, some questions:
* Does that happne with the OF ?
* Can you try the following procedure and report the result ?Procedure:
* Boot player, go to System > Debug (keep out) > View hardware info
* In the list, go to button and press select: the screen should display a big table with many numbers
* NOTE: I don't have the player, it is possible the table doesn't fit on the screen or is not exactly as described
* One of the lines should be "vddio: 0[2/2] (raw=XXX) ...."
* If you press up and down, the raw number above (XXX) should change: confirm this
* Some lines should be "BBB: 0[2/2] (raw=YYY) ...." where BBB is a button name like "up" or "down"
* Repeat the following for all offending buttons (like left, home, etc) :
* press the button, write down the value YYY in the corresponding line together with the corresponding VDDIO value
* release the button, write down values as above
* press up or down several time to change the value of vddio
* press the button, write down values as above[
* release the button, write down values as above[
--- End quote ---
A lot to go through here, not all of it may make complete sense (at least for now). And for the record, these issues don't occur in the OF.
First: When I go to that HW Info scree, I see the big table, but not all of it -- the right-hand side is cut off.
Furthermore, the raw numbers are hard to make out, because they look like they're all a 4-digit number, but the 4th digit is constantly changing. It looks like the last digit is just running through all the numbers 0-9 over and over again. Only one button doesn't show this, the Right button, but I think that's because it's cut off on the right side, so it only shows the first two digits of what's probably a 4-digit string.
Second: Three of the buttons don't change any of the numbers, but just kick the user back out to the previous menu. Those include HOME (also BACK) and PWR/HOLD (also OPTION). The BACK button is one of the problem buttons, so can't really check that one.
Third: The first time I tried checking these buttons, the entire device locked up, and I had to do a hard reset. I think that has to do with the Up button (see below).
Fourth: Not sure if this is related to the button issue or not, but lately a new issue has emerged, where the device will do two things, often until a hard reset:
* The device will put whatever's playing into a quick pause every 6-7 seconds or so, then automatically resume playback. I have it set to rewind a few seconds after pause, but it doesn't rewind when this issue occurs -- so just a regular pause and resume on its own.
* Pressing any buttons when this happens does nothing. The screen will respond, but veeeerrrrryyyy slowly. If I hold the PWR button down for about a minute, it may turn off. If I power back up and resume on the same file, it will often (but not always) have the same problem. Note: This is not the file itself. I've deleted the file, done a hard reset, re-added the exact same file, and the problem didn't occur.
* This pausing issue began a while ago, and stopped when I reset the device's settings in the Rockbox firmware (Settings >> Manage Settings >> Reset Settings). However it resumed again a few days after the reset, but the random pausing occurred less frequently -- so not every 6-7 seconds, but sometimes only once every 20 seconds or so, and sometimes only once or twice during a 20-minute-long file, like a podcast.
Fifth: The device not responding unless it reaches a certain temp (almost body temp) is occurring much more frequently now. Room temp in my place is around 65-70 degrees F (around 20 degrees C -- it's winter on the North American Atlantic coast). At room temp, the device's HOME (BACK) button pretty much does nothing. Warm the device up, and it works again.
So, on to what I think you were asking for with the table and the vddio numbers:
Pressing Up and Down repeatedly seemed to change the screen's brightness as well as the vddio number; pressing Up makes it brighter, pressing Down makes it dimmer. But if I pressed up too many times, the device locked up with a solid light screen -- the same screen as when you go to Plugins >> Applications >> lamp, and all I could do was power down.
Pressing HOME (BACK) and PWR/HOLD (OPTION) doesn't change vddio numbers, but just kicks the user back out to the previous menu (as noted above).
So that leaves me with left, right, up and down. Here are the initial raw numbers recorded, and then the numbers as they appeared after pressing down about 8 times (note that I'm only putting the numbers I could see, and am leaving off cut-off and rapidly-changing numbers at the end of the string, and I believe that string is 4 digits long):
* Left: 342; pressed = 218; released = 342; after pressing down a few times, pressed = 245 and released = 385.
* Right: 34 (probably 342, but cut off); pressed = 18 (think it was 185, but cut off -- the other buttons read 185); released = 34; after pressing down a few times, pressed = 207 and released = 385
* Up: 342; pressed = 245; released = 332; after pressing down a few times, pressed = 276, released = 374
* Down: 342; pressed = 296; released = 353; after pressing down a few times, pressed = 265, released = 310 (but pressing down kept changing all the numbers for every button)
I have no idea if I did this right or if this info is helpful or useful, but here's hoping.
mxyzptlk:
I fear this thread is dead, but...
I've found that the quick pause every 6-7 seconds almost always happens when a file is added to the current playlist. So you're listening to a file, decide to add something to the current playlist, do so, and the thing you're listening to then starts that annoying pausing.
I'm not sure if it continues to pause on the added item, because I've just done a hard reset every time -- because it's just not worth listening to that repetitive pause.
EDIT:
Just a note that when it does go into that weird pausing phase, the top of the Now Playing screen changes to look like all the other screens, with the battery indicator, volume indicator (which just reads -33), time, and a little lightning bolt in the upper-right corner. (This is with the standard cabbiev2 theme.)
Not sure if that helps or not, but there it is.
pamaury:
Hi All,
I'm working on the problems, so let me summarised:
* Button problem: here is a modified build, please tell me if it helps: https://www.dropbox.com/s/17mlziuobfvjunh/rockbox_nwze380_buttonfix.zip?dl=0
* Bootloader buttons: currently the bootloader uses Play/Pause to boot instead of Power. I am investigating the possibility of using Power instead. Currently I am running into issues.
* Play/pause bug every 6/7 seconds: I have no been able to repeat the problem so far. I have one theory but I need to check it.
* Keymapping issues: while I'm at it, some people reported awkward/suboptimal keymaps, could you please restate them so I can fix them ? (I almost never use the player so I don't know about them)
mxyzptlk:
Thanks! Trying out the new version presently. The button problem this build addresses -- is that the one where the Home/Back button doesn't work unless the device is sufficiently warm?
I've been trying something else to pinpoint that play/pause bug. I've reset the device to it's base settings to see if it was an adjustment that caused this to happen. The only thing I've adjusted is the bass/treble, and I've left everything else as is -- and so far, about five days into that test, no play/pause issues. (Did JosieQ have a similar issue? Seems jrbb had something like that happen as well.) Here's what I've adjusted in the past whenever those issues occurred:
* Commented out the big yellow "NOW PLAYING" progress bar from the cabbiev2.wps
* I'm a podcast head, so I set "Start File Browser Here" as the PODCASTS directory.
Under Settings > Playback Settings:
* Fast-Forward/Rewind: > FF/RW Min Step: 5 s
* Auto-Change Directory: Yes
* Constrain Auto-Change Directory: No
* Skip Length: 7 s
* Prevent Track Skipping: Yes
* Rewind Before Resume: 10 s
* Rewind on Pause: 3 s
Under Settings > General Settings:
* Had the Start Screen set to Resume Playback
* Idle Poweroff was set at 3 min
* Automatic resume: Yes
* Resume on automatic track change: Always
Under Settings > General Settings > Bookmarking:
* Bookmark on Stop: Yes - Recent only
* Bookmark Update on Stop: Yes
* Load Last Bookmark: Yes
* Maintain List of Recent Bookmarks: Unique only
I'm messing with some things in the new build you uploaded. One thing that seemed to be a problem in the past -- a trigger for the play/pause issue -- was playlists. Often, if there was more than one file in a playlist or if I added some files to the current playlist, that problem would occur. At this moment, with the new build I've got a playlist of 5 files going, and I've not experienced any of those play/pause issues. (Nor have I monkeyed with any settings at this point.) Hell, maybe it was something weird like removing the progress bar from the wps, no idea. But in any case, it's not happening at the moment.
On to the keymapping issues --
I went through the thread and tried to find what the keymapping issues were. Two common ones are the power vs play buttons for turning the device on, and that there doesn't seem to be a way to lock the device while playing in Rockbox. But three others (some of which were repeated/confirmed by other users, but a while back, so don't know if there have been other changes):
evilseabsti said:
--- Quote ---All buttons works. Only thing weird is that it turns on with de play/pause button, and turns off with power button. I will feedback any issue i have. Do you know any method to lock the keys?
--- End quote ---
jrbb said:
--- Quote ---I'm having that key-Issue which was already mentioned somewhere. Some keys(!) sometimes(! actually pretty often at the moment) don't work.
Especially the Back/Home- and the Play-Keys often don't work. Sometimes also the forward and back keys don't work, but they work most of the time. The up and down keys always work!
Additonally sometimes a key is triggered multiple times in a row, i.e. press forward to select an entry and it selects x entries in a row until it reached a leaf of the file-tree.
If a key is not working, a reboot has no effect. I can't reproduce it or see anything that influences the behaviour.
All the keys work perfect all the time in the original fw.
--- End quote ---
I said:
--- Quote ---I still have muscle-memory from years and years of Sansa Clip use, and am finding that not all the keys work quite the same. Take the game plugin solitaire; in order to get it to deal new cards, need to hold the Option and then Up (it's the upper-left Back button on the Sansa).
--- End quote ---
EDIT
Just tried connecting the device to my computer (usb) while it was paused, and it caused a panic and needed a hard reset. Here's the info from the panic screen:
-----------------------------
*PANIC*
buflib error (CTX:0 X600f9138,30841580 bytes0; crc mismatch: 0xBA9DF4F4, expected:0x3F87B1B9 pc: 60049828 sp: 00004C(the screen cuts off here) A: 00004CD0
bt end
start of logf data
(bunch of stuff that runs off the screen, four beginning with Codec: entering run, then Codec: calling entry, Codec: cleaning up, Codec: entering run, Codecn: calling entry, end of logf data)
-----------------------------
Tried plugging it in while on in a few different screens, and it caused a panic every time.
Anything else I can do to help?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version