Third Party > Unsupported Builds
Android: rasher's unmodified daily builds.
Timar:
--- Quote from: [Saint] on January 19, 2013, 08:17:26 AM ---I'm going to go ahead and assume you're not able to compile your own builds (based on the fact that you're using someone elses pre-compiled binaries), and based on that assumption the answer in short is, "you can't".
--- End quote ---
Well, I've compiled builds für Sansa devices, but I guess it's a bit more complicated for Android!? Can you tell me which file holds the settings?
Maybe I could even help to implement some menu setting for this. In its current state the font color renders a great feature pretty much useless for the majority of all Android users (I guess the background is dark on most devices).
Timar:
It may or may not be of interest for the port developers that on my device (ARMv9 - Samsung I9100), rockbox frequently crashes (playback continues but the interface stops to react) on Android 4.0.4 but runs perfectly smooth on Android 4.1.2.
Falco98:
Rasher's builds haven't updated in over a month - anyone know what's up?
edited to add: sorry for duplicating a question posted by someone within the last 5 or so posts.. oops :(
dfkt:
--- Quote from: Timar on January 24, 2013, 01:15:35 PM ---It may or may not be of interest for the port developers that on my device (ARMv9 - Samsung I9100), rockbox frequently crashes (playback continues but the interface stops to react) on Android 4.0.4 but runs perfectly smooth on Android 4.1.2.
--- End quote ---
Similar - or even worse - here, on a Samsung Galaxy Tab 7.7 running CM10 (4.1.2). When the screen turns off while Rockbox is the visible app, the screen can't be turned on anymore, the tablet has to be rebooted. Same happened on CM9 (4.0.x) too.
TexasRockbox:
dkft,
The problem you describe has been a problem since CM9 (or maybe before). Look in CM10 display settings and check the "volume wakes screen" or something like that. Then the volume control can then wake the device.
I'm not convinced that it's a Rockbox problem (not yet anyway). I have *never* seen the problem with a commercial, stock Android build whether it be GB, HC or ICS. I have only seen it with CM and it happens with CM on various devices: Samsung Epic 4G Touch (SGSII), Samsung Exhilarate (i577), Samsung Captivate (SGS). Maybe it's a Samsung problem.
Even on devices with stock, nearly unskinned Android ICS such as the Toshiba Excite 7.7 or the Lenovo Thinkpad there is no problem.
On the other hand, I've never seen the problem with other media players on CM9 or CM10.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version