The charge current may be tuned too, you can try (as root)
echo 500000 > /sys/class/power_supply/twl4030_usb/charge_current
to reduce it further to 500mA in case there are still problems.
Same can be done with the charger port (.../twl4030_ac/charge_current).
I don't know if it matters, but I think it would be better to run the simulation at 1.25V as that's what 1.5GHz needs and where all the problems start...
Well, don't make a big deal out of it, if you look at the changelog there's nothing substantial in there for a span of 7 months (or so). There is also no company involved, there were never any work or financial relations between me and OP (except some free hardware), it's pretty much my personal...
Previous release has some known bugs, so I've simply fired a new build with what we have now. I've been meaning to do that since months ago, but it either was slipping away because of other things in life or I simply had no energy left to do anything after work.
Changelog (since SZ 1.75)...
As a continuation of armhf stuff, I've added some missing armhf libs and enabled various kernel options needed by Docker and it seems to work for me.
Installation
warning: if things go wrong, you'll most likely have to reflash.
First run "Upgrade Pandora OS" from the system menu to get the...
This one is also an interrupt from the chip, "VBus drops below the VBus valid threshold during a session". I guess this means the regulator driving VBUS is fried, which unfortunately sits inside the PMIC. A crude hack would be to cut the VBUS trace and route a wire from the big USB port, and...
That's not good, the message is printed when twl4030 fires an interrupt, not by some software decision. The temperature sysinfo reports is from a different chip, so the connection to that monitoring chip is fine, but perhaps not to the charger. If your pandora works without a battery, you may...
Well the charger tends to misbehave like that in certain situations. You can force restart it in software by writing "0" to /sys/class/power_supply/twl4030_ac/enable and then "1" again after a short while, then it comes back to it's senses in some cases (pndevmapperd does it from time to time...
The uEVM (eval board) has multiple caps, so that indeed is one departure from the reference design. AFAIK it ended up that way because of lack of space on the CPU board.
Do you think it may be the cause of the issue?
If you have experience in this area I think @hns would be interested to hear you.
So you did a full reflash?
Does the corruption also affect menu or the desktop?
Could be this too, for that you need additionally to "upgrade pandora OS" from the system menu.
You can also try deleting or renaming appdata (/media/<card>/pandora/appdata/pcsx_rearmed/), maybe it's some config...
You might need to run "ifconfig -a" to see the interface if NetworkManager ignores it for some reason.
Otherwise bad luck as there is no useful output in the log. Unless you can find some other driver not much can be done.
If it's that slow it's probably using floating point for samples, where both Cortex-A8 and the DSP aren't that great.
You could 'nice' the other processes (can be done with top) to give the audio player priority.
Edit: I've downloaded random 96kHz sample from http://www.2l.no/hires/index.html...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.