Author
Topic: Sony NWZ-E370 (Read 36827 times)

Hi, great thanks for the report ! Let me try to answer your points:1) I *think* it depends on the theme (I only develop the low-level stuff so I'm not 100% sure), and I *think* we have other themes for this resolution, you should have a look on our theme website, just pick a player with the same resolution (select search by lcd size and enter "128x160"). It is also possible that it is a bug of the theme engine.2) I think your suggestion is okay, we could have both buttons power the player, to be honest I don't even remember why we selected play. That will require a bootloader change though but I'll add this to my TODO list.3) yeah the pad is just not great for games4) Ok, then I have no idea what to do, if the battery life is not impacted I'd say just ignore it.

About battery reports, I'll try to have a look at it, the battery meter is really calibrated for the NWZ-E370 and calibration is probably not the same on the NWZ-E380 which may explain the problem. If you have the time to do it, you could help by doing a battery benchmark: start with full battery, select repeat all, start a long playlist (at least 30 files), and start the battery_bench plugin. Let your player alone until battery is drained, and send me the battery bench log (it should be at the root of device I think).

I did manage to put a numeric display for battery and volume into my theme, so that problem's fixed and I appreciate that clue.

And finally (took a bit of time), I did the battery bench test for you! (Also for me, since it's my player after all, heh.) I'm attaching it and, assuming I'm understanding any of this correctly, it did last over 26 hours.

Thanks for the report I have another question: does the battery percent "swing" only in the bootloader screen or also in Rockbox ? I kind of expect this behaviour in the bootloader because at the moment the "raw" voltage is displayed, whereas in Rockbox it is smoothed, thus removing the most abberant values.

It seems to be only on the bootloader screen, you're right. The only thing it does weird-ish with the battery while IN Rockbox is that the graphical battery value shows a tiny bit missing even when it's 100% and never displays full graphical. (It does however show full in the while-playing screen.)

Oh, I did have a weird glitch while playing music yesterday. I went into a different folder from the one I was in and started clicking around on different mp3 files trying to find a song... and the music stopped playing and behaved as if it was paused. The icon still showed a "play" status and I could switch between "play" and "pause" with the button but it was just sitting there, not playing or advancing the time, as if paused. I tried a bunch of songs with no luck, and then I restarted and that fixed it.

Cuuuuuurious.

« Last Edit: December 11, 2014, 11:37:08 AM by JosieQ »

Logged

It makes me mad when people say I turned and ran like a scared rabbit. Maybe it was like an angry rabbit, who was going to fight in another fight, away from the first fight.

I'm using the rockbox firmware since about half a year on my nwz e384. It's great, but I'm having a few issues:

1)I'm having that key-Issue which was already mentioned somewhere. Somekeys(!) 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!Addionally 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.

Since this seems not to be a "regular" (i.e. logical bug) I was wondering whether it might be some kind of a low level threshold issue. Is there some threshold that determines whether a button was pressed or not? Is it possible, that the voltage might be a little different depending on battery voltage, temperature, humidity? This could also explain the multiple trigger issue (button is pressed but the noisy voltage triggers key-released multiple times in a row).

Any ideas? I had the issue with a fw version from approx 6 month ago and updated my fw two days ago with no effect.

2)The playback stops even though the play indicator says playing bug -- see JosieQs post -- also occurs sometimes. Not often and not really annoying, a reboot fixes the issue.

I had a brief look at the code. I think I found the thresholds ("expected value") but since I'm not familiar with the code and I don't have a build environment setup I think I would take me quite a lot effort the figured out how to fix it. But if there's a plugin or debug facility that displays the raw button values I could provide those values.

Hi,it could be that the E380 uses sligthly different values than the E370. You can view the raw values in the debug menu: System > Debug > View HW Info > Button.However, out of memory, I think the E380 screen might be too small to correctly display this information, if that's the case, I'll commit a fix tomorrow to make it more readable and so that you can provide the values

can't get values for the other keys, because they quit the debug view.

I.e. they are of by almost the threshold in the code and a little bit of vddio scaling imprecision might cause the problem.

What do you think of just increasing the threshold value? This would be platform independent and since the values are spread for enough from each other there should be no overlapping. Might this cause any side effects?

Anyway, it's a complete new and great experience to use a rockbox with fully working buttons after half a year of annoying work arounds

Hum, to be honest I don't really like the idea of simply increasing the value because it affects many targets and may broke some of them. Furthermore, it doesn't really solve the problem which you identified: imprecision increases with vddio because of scaling. A quick fix could be to have a per-target threshold. But in this case it seems some of the values you are off compared to the expected values, which means that:

either I made a mistake when writing the expected values, in which case it suffces to fix them

either the NWZ-E370 and NWZ-E380 are slightly different and need different values

I'm going to double-check on my E370 as soon as possible. I'll also commit something so that one can try all the buttons in the menu.Anyway thanks for the report and stay tuned

The buttons-not-working issue! Initially I read jrbb's post and it had never happened to ME before, so naturally I (as I'm sure most of us did) assumed he was completely insane.

But yeah, I did get this issue the other day with the "Play" key and it was strange. Pushing it hard or soft did nothing, and pushing it a bunch of times in succession didn't do anything either. A restart did not fix it and eventually it just... fixed itself. Although then it did play-pause-play-pause-play-pause real fast a bunch of times, so maybe it was sort of, I dunno, catching up with the past presses? Is that possible? Hmmm.

Everything else is going swimmingly.

Logged

It makes me mad when people say I turned and ran like a scared rabbit. Maybe it was like an angry rabbit, who was going to fight in another fight, away from the first fight.

Hi,the nighlty build contains all the features of Rockbox except the radio. Also the installation of the bootloader must still be done by hand but I have begun some work on this so it can be done automatically by Rockbox Utility. As for the radio, I have some patches but they are very unreliable, this is difficult matter because we don't have any doc.

i try to plugin and some themes but themes have a problem, i generelly try other player's themes but screens different and for this reason have a problem.. And this rockbox have a little bit problem its not have a memory about of eq setting.. I make a some eq setting and 2 or 3 day later eq setting change by itself and alwany i obligation make new eq settings and themes setting. Can you fix it ? or are you make a new update ? (thank you so much for this application)

I put this on my nwz-385. Thank you very much, pamaury, for making this available!

There are some posts in this thread talking about strange activity with the buttons. I used this player for over 6 months before putting rockbox on it, and had similar problems even then. With the OF, it usually required resetting it, to fix the problem. In rockbox, turning off then back on fixes it.

After installing rockbox, I once booted into the OF just to prove it was possible. After booting back into rockbox...I noticed all settings were reset. When I went to reload the cfg and theme files, they were gone. All the bookmarks, shortcuts, and playlists were too. It seems that when booting into the sony firmware, it deletes anything that wasn't put on the player through its software? How rude!

I haven't been able to get timestretch to work. Searching the forum suggests that once it's enabled, it still needs to be activated in the pitch screen. On players with a record button, it's enabled by pressing it...Is there a button combination on these players to activate timestretch?

Again, thank you so much. I really appreciate all the extra features as compared to the rather basic OF.