AGPTEK Rocker

[Dulus_No]

A couple of days ago I was interactively mucking with the gain settings (using amixer via adb) and it looked like only the values 1-7 had any effect -- eg set it to 7, then set it to 0, and the output doesn't change, but setting it to 1 had an immediate effect.  Can you see if this is the case for you as well?

Code: [Select]

amixer set 'CS42L51 Gain' 0 - no change.
1-7 - can hear changes.

Code: [Select]

amixer cset numid=3 valuevalue from 0 to 7 works.

[Dulus_No]

I hear a pop after pause only on right channel.

Now after tinkering with amixer I hear pop on both channels.

[sduck]

Sorry for posting this, possibly a bit off topic. Forgive me! But I'm really hoping bluetooth will get enabled for this soon - I'm waiting eagerly. I have a new car that doesn't have an aux jack, but this player works with it quite well. And having rockbox on it would really make it complete - I've had rockbox on all my various DAPs since about 2003. So, any support I can give - just let me know. I'm not a coder, but I'm an excellent tester, and will happily buy pizzas and beer if that'll help. Thanks!

[wodz]

Low level aspect of bluetooth on Agptek has been explored. The lack of time/developers is limiting factor.

[Gavsgovenko]

Hi everybody! I find a bug. In all versions of rockbox screen always on, only backlight is off. You can see this problem on bright ligt, pictures still on screen ang if you choose a theme with moving pictures (jumping equaliser) you'll see mowing pictures when screen(should be, but not) off.

[wodz]

Hi everybody! I find a bug. In all versions of rockbox screen always on, only backlight is off. You can see this problem on bright ligt, pictures still on screen ang if you choose a theme with moving pictures (jumping equaliser) you'll see mowing pictures when screen(should be, but not) off.

Let me guess - Benjie T6?

[Gavsgovenko]

Yes, benjie t6.

[titzesan]

Hi everybody! I find a bug. In all versions of rockbox screen always on, only backlight is off. You can see this problem on bright ligt, pictures still on screen ang if you choose a theme with moving pictures (jumping equaliser) you'll see mowing pictures when screen(should be, but not) off.

Let me guess - Benjie T6?

Just noticed the same behavior this morning in bright sunlight on my AgpTek Rocker (not the the Benjie model or firmware). UI is hard to see, but a white cover image can be noticed if you look closely.. Besides Rockbox the player is running the 1.2 OFW. So far didn't have the time to take a more detailed look.

[alcaier]

Sorry for posting this, possibly a bit off topic. Forgive me! But I'm really hoping bluetooth will get enabled for this soon - I'm waiting eagerly. I have a new car that doesn't have an aux jack, but this player works with it quite well. And having rockbox on it would really make it complete - I've had rockbox on all my various DAPs since about 2003. So, any support I can give - just let me know. I'm not a coder, but I'm an excellent tester, and will happily buy pizzas and beer if that'll help. Thanks!

There is libasound_module_pcm_bluetooth.so and libasound_module_ctl_bluetooth.so on the system. I have no experience on alsa but this is pretty generic linux stuff e.g. https://github.com/mikebrady/shairport-sync/issues/200 .  I think wodz figured out how to make aplay work with this module. I think once one gets aplay to work with it you could modify rockbox to read alsa output device from file and then use a script to modify this file with bluetooth device mac. Ugly but I think it would be sufficient absent better ideas.


Here is a quick way to change alsa device. It looks for /etc/asound_device_override which could be created with a simple echo "alsa_devide" > /etc/asound_device_override from script . I have not even tried to compile this code.

Code: [Select]

diff --git a/firmware/target/hosted/pcm-alsa.c b/firmware/target/hosted/pcm-alsa.c
index f6a3ffc..112779a 100644
--- a/firmware/target/hosted/pcm-alsa.c
+++ b/firmware/target/hosted/pcm-alsa.c
@@ -421,10 +421,21 @@ void pcm_play_dma_init(void)
 {
     int err;
     audiohw_preinit();
-
-    if ((err = snd_pcm_open(&handle, device, SND_PCM_STREAM_PLAYBACK, 0)) < 0)
+       
+       char device_override[64];
+       device_override[0] = 0;
+       FILE *fp = fopen("/etc/asound_device_override", "r");
+       if (fp && fgets(device_override, 64, fp))
+               device_override[strcspn(device_override, "\r\n")] = 0; // remove trailing \n
+               
+       fclose(fp);
+       
+       if (strlen(device_override) <= 1)
+               strcpy(device_override, device);
+
+    if ((err = snd_pcm_open(&handle, device_override, SND_PCM_STREAM_PLAYBACK, 0)) < 0)
     {
-        panicf("%s(): Cannot open device %s: %s\n", __func__, device, snd_strerror(err));
+        panicf("%s(): Cannot open device %s: %s\n", __func__, device_override, snd_strerror(err));
     }
 
     if ((err = snd_pcm_nonblock(handle, 1)))



[sg2002]

Since another Clip+ started dying, and getting them is harder and harder, I've bought a T6, to see if it's a good replacement for them.

Now I'm trying to get Rockbox running on it. First of all, I have a question about the build procedure on github ( https://github.com/wodz/rockbox-wodz/tree/agptek-rocker/tools/agptek_rocker/ ) - I have to provide an existing update.upt from the manufacturer and then it's gonna get patched, right?

Another thing is that while I'm struggling with manual build I've decicded to try the prebuild update files, there's one at head-fi ( https://www.head-fi.org/threads/the-shenzhen-benjie-bj-t6-agptek-rocker.834797/ ) and another on russian 4pda forum ( https://4pda.ru/forum/index.php?showtopic=900933 ). Neither of those worked for me, I get "Insert TF pls", "Updater V 1.1" and "v_v Failed".

Also my About This Player page reports that firmware version is 1.08Beta, maybe it's ther reaspon I cannot update?

Thanks for working on this, this port is what would probably keep rockbox alive.

[JimZipCode]

Story:
 

Last week, Thurs or Fri, I was cooking dinner while playing my Rocker thru my external speakers, when it ran out of charge and "died".  After finishing dinner, I plugged a charging cable into it, and an error notification popped up.  I didn't worry about it, figured it had stopped in an error condition and would reboot fine when it was charged up. Next morning the error screen was still displaying, but I barely glanced at it, just unplugged and turned the player off.  When I powered up, the normal bootloader choice appeared, but when I chose Rockbox it said it could not boot Rockbox.  I tried a few times.  It did boot into the "Hiby player" just fine, but not into Rockbox.  When I booted into the original firmware, it couldn't find any of my music.  When I plugged the player into my computers, it would charge, but the player would not be detected by the computer.  I tried it on a laptop running RHEL7, and on a desktop running Windows 7.  Neither machine detected that anything was plugged in, though the player itself said it was "connecting to computer", and it started to charge.  I took out my microSD card and put it back in, no joy. Eventually on Sunday I bit the bullet.  I used the orginal firmware to restore factory settings.  I used original firmware to re-format my microSD card.  Copied the update_rb.upt file over (I had it stored on one of my computers), and I unzipped the Rockbox dev build from here.  Booted original firmware, turned off, then booted Rockbox.  Success!  Recopied all of my music over, which took an hour or so.  Now player seems as good as "new", ie good as originally Rockboxed.

I dunno if this anecdote is useful to anyone.  Something during normal usage cycle "fried" (technical term) my microSD card, and required reformatting and reinstall of Rockbox to restore to service.  But I don't know what the "something" was.  Also it didn't brick the card, I was able to reformat and continue using the card.  Just lost all the data.  Wish I had paid more attention to that original error message, captured it.

Thanks a lot for merging upstream.  Having the dev build available was super useful.

[wodz]

Now I'm trying to get Rockbox running on it. First of all, I have a question about the build procedure on github ( https://github.com/wodz/rockbox-wodz/tree/agptek-rocker/tools/agptek_rocker/ ) - I have to provide an existing update.upt from the manufacturer and then it's gonna get patched, right?

Yes, you need to provide original update file and it will be patched with bootloader. This is one time process.

Another thing is that while I'm struggling with manual build I've decicded to try the prebuild update files, there's one at head-fi ( https://www.head-fi.org/threads/the-shenzhen-benjie-bj-t6-agptek-rocker.834797/ ) and another on russian 4pda forum ( https://4pda.ru/forum/index.php?showtopic=900933 ). Neither of those worked for me, I get "Insert TF pls", "Updater V 1.1" and "v_v Failed".

Direct this questions to people providing those update files.

[wodz]

I dunno if this anecdote is useful to anyone.  Something during normal usage cycle "fried" (technical term) my microSD card, and required reformatting and reinstall of Rockbox to restore to service.  But I don't know what the "something" was.  Also it didn't brick the card, I was able to reformat and continue using the card.  Just lost all the data.  Wish I had paid more attention to that original error message, captured it.

Its a pitty you didn't note what error it was. Anyway if bootloader popped up it would be enough to run checkdisk on SD card/reformat it and unzip rockbox on it. Flashing patched update.upt is only needed to inject bootloader. Anyway FAT filesystem is rather sensitive to power outages.

[JimZipCode]

...if bootloader popped up it would be enough to run checkdisk on SD card/reformat it and unzip rockbox on it.  ...  Anyway FAT filesystem is rather sensitive to power outages.

I didn't know that.  Thanks.

Its a pity you didn't note what error it was.

Yes.

I apologize for the vague nature of the report.  I only posted so the info would be out there, in case other users report something similar.  Then someone might say "that sounds a little like what happened to JZC" and maybe help spot a "trend", if there turns out to be one.

Great port, by the way.

[sg2002]

Ok, so I was able to patch update.upt. But I'm still not able to flash it, since I could not find any firmware that would flash on my unit. I get the same "Insert TF pls", "Updater V 1.1" and "v_v Failed" every time. Tried 2 different cards formatted by the player.