RockChip mp4 player with OSX

[onlyinkenya]

Hi,

I'm happy to find this great forum! Yesterday I bought an Orion OMP4-106 player which has rockchip inside (i suppose). Everything is fine while using Windows XP but I have problems with OSX. As I don't have Windows PC at home, I think it's a big problem. For me at least. I bought this player because the manual said it is usable under OSX but it seems it isn't...
My problem is: after plugging into my iBook I can see the files on it, but when I try to copy anything on it it freezes. I mean not the iBook just the player. I tried with 2 other Macs but the same problem occured. I think the problem is with the usb handler chip inside the mp4 player, so... if you have ANY idea please do not hesitate to help me

I know this not exactly a player problem, it's an OS related issue but still.. I "hope" somebody had/have the same problem and can help me.

PS: under Linux I could fix the bogus USB behaviour, but I have no idea how to do it under OSX.

Thanks!

[NOLA MPx Fan]

Well...it should work. I'm a Mac guy, and that was part of my decision process in picking one. I'm sure you have, but did you try a different cable?

What did you do under Linux? Since they are quite similar, we should be able to extrapolate and so the same thing under OS X. heck, if you used a linux command line function, it might work in an OS X terminal as well ;-)

[onlyinkenya]

Originally Posted by NOLA MPx Fan";p=&quot

Well...it should work. I'm a Mac guy, and that was part of my decision process in picking one. I'm sure you have, but did you try a different cable?

What did you do under Linux? Since they are quite similar, we should be able to extrapolate and so the same thing under OS X. heck, if you used a linux command line function, it might work in an OS X terminal as well ;-)

No, I didn't try with other cables... as I have this one with me at the moment But this makes no sense. It works perfectly in Windows. And in Linux after adding a new udev rule

BUS=="scsi", SYSFS{vendor}=="RockChip", RUN+="/bin/sh -c '/bin/echo 128 > /sys/block/%k/device/max_sectors'"

under /etc/udev/rules.d/ and restarted udev.

but as OSX doesn't have udev and I'm not enough qualificated for OSX 's BSD subsystem, I don't know what to do. My girlfriend will kill me, if I can't solve this problem, because I said to her to buy this kind of players as it's supported in OSX

What OSX version do you have? I'm using Tiger with latest updates.

[NOLA MPx Fan]

Gimme the rest of the day. I'm going to go ask some of the bsd geeks I know over on the Apple boards what to do to that command. Who knows, it might even help the other rockchip player I have connect.

Yes, I have one that does not, but then it never promised it would. has a completely different firmware identifier as well. Something like "sdk-1.65" where the player that works is a longer string of numbers and a date.

I'm on vacation, so I won't be checking in too often, but like I said, give me a bit of time and I'll see if anyone knows what to do.

[onlyinkenya]

Thanks! Enjoy your vacation

Btw, I tried with different cable but same result.

[cdenley]

I think I have the same mp4 player, except it is a Chinese knock-off. Do you know where I can find firmware for your player?

Thanks for the Linux fix, that was really annoying.

[NOLA MPx Fan]

Hey, I sent a message off and while the reply wasn't totally unexpected, it wasn't totally bad, either.

When I drill down through all the BSD speak, what it boiled down to was "if I had a player I might be able to figure out how to write a driver for it". That said, I doubt either of us are willing to part with or spring for players for any of these guys.

So, that's the bad part. Good part is I know these folks and they really can't resist a challenge. So while there is not a solution forthcoming today, I wouldn't be surprised if someone sent me a message in the near future asking if something works.

As the Mac sees it and can read it, but then fails to copy info, it sounds like either the chip isn't all there or (more likely) the driver OS X has decided this thing needs isn't quite right. Maybe I'll ask again from the standpoint of "how do I change which driver loads for a given device" rather than "how do I get a udev rule like thing under BSD?"

I haven't forgotten you, just there was no internet connection on the Wisconsin River this past week. ;-)