Android: rasher's unmodified daily builds.

[Timar]

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".

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]

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.

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.

[Falco98]

My TB recently got the newest OS upgrade (now running 4.0.4).
Rockbox ran fine for several minutes, despite turning the screen on/off, going to the home screen and back, etc.  Then playback stopped, and I had the following error screen.  I can now exit RB, kill the process, reset my phone and/or install the app again, and any time I try to resume playback I instantly get essentially the same error:

Code: [Select]

*PANIC*
Stkov audio
pc:###### sp:#####
 A: #####
bt end
I haven't tried removing / reinstalling fully yet, but will try if anyone thinks it'll actually do any good.  I kinda expected a full restart of the phone to do the trick at least temporarily, but no dice.

[Mr Whippy]

wow. amazing.  Just installing on galaxy ace GT-5830i. Just a couple of small things

Set default location of file view. At the bottom it says "start file browser at" then click that says cleared. Setting to sdcard\media would be good.

There is a tiny bit of over scanning going on on the top edge, probably one or two pixels. I've used the correct resolution build

[[Saint]]

You are thinking of:
Settings - General Settings - File View - Start File Browser at /

Which as you've found, sets the starting location of the File Browser to /.

That menu entry exists solely to revert the starting location of the File Browser to the default, which is /, a legacy of the fact that Rockbox typically runs on devices that make use of the entire disk. The fact that it isn't /sdcard or /storage0 for RaaA on Android is perhaps an issue, but...not really, keep reading.

What you *want* is:
Files - <Navigate to desired starting location of File Browser> - <bring up context menu on desired selection> - Start File Browser Here

This allows you to set the starting location of the File Browser to any location your heart may desire, provided the path actually exists.


[Saint]

[Mr Whippy]

installed 800x480 build on samsung player 4.2, and it's in the incorrect rotation- it's in landscape mode (tried the built in rotation and made no difference) Bug? Or can I rotate it within Rockbox itself?

[bluebrother]

installed 800x480 build on samsung player 4.2, and it's in the incorrect rotation- it's in landscape mode (tried the built in rotation and made no difference) Bug? Or can I rotate it within Rockbox itself?

800x480 is a landscape format. If you want portrait you need to use 480x800.

Rockbox cannot rotate the display. It can flip it, but that's something different. It's definitely not a Rockbox bug. You can call this a user bug if you like

[mr.pi]

Hello rasher,

i have a motorola defy (android 2.3) an run rockbox 3a1ba75 in 480x800. Now I downloaded the new rockbox 9e7bd64-130315 and tried to install it. But the system gave me the error "application not installed". Up to now the installation was every time without problems. What went wrong and what are the different version mips and x76 for?

thx for reply

the pi

[gevaerts]

Hello rasher,

i have a motorola defy (android 2.3) an run rockbox 3a1ba75 in 480x800. Now I downloaded the new rockbox 9e7bd64-130315 and tried to install it. But the system gave me the error "application not installed". Up to now the installation was every time without problems.

Did you uninstall the previous build first? The builds are now done on a different system, so I imagine that maybe the signing key changed.

What went wrong and what are the different version mips and x76 for?

They are for MIPS and x86 based systems

[florin]

My TB recently got the newest OS upgrade (now running 4.0.4).
Rockbox ran fine for several minutes, despite turning the screen on/off, going to the home screen and back, etc.  Then playback stopped, and I had the following error screen.  I can now exit RB, kill the process, reset my phone and/or install the app again, and any time I try to resume playback I instantly get essentially the same error:

Code: [Select]

*PANIC*
Stkov audio
pc:###### sp:#####
 A: #####
bt end
I haven't tried removing / reinstalling fully yet, but will try if anyone thinks it'll actually do any good.  I kinda expected a full restart of the phone to do the trick at least temporarily, but no dice.

Do you have "Gather Runtime Data" enabled by any chance? I get a similar error when I set this option to Yes. And database update seems to be broken - every time I start Rockbox it adds the same entries to the DB - if I started RB 3 times since install I'll have 3 "Hell's Bells" under AC/DC.

[Philip]

Hi Rasher,

Loved your builds on my old phone but my new one is 1080x1920.

Any chance you could add this resolution to your builds

Thanks,

Philip

[Falco98]

Do you have "Gather Runtime Data" enabled by any chance? I get a similar error when I set this option to Yes. And database update seems to be broken - every time I start Rockbox it adds the same entries to the DB - if I started RB 3 times since install I'll have 3 "Hell's Bells" under AC/DC.

I figured I'd be able to just fish through and find this setting, but apparently I was wrong. Any hints?