Rockbox Technical Forums
Support and General Use => Theming and Appearance Customization => Topic started by: Braverman on October 10, 2021, 03:55:51 PM
-
I use Friskey2 as both my base skin and the now playing skin.
Had some major trouble with my 2 e280 Sansa's and now I can not get the Now Playing Skin to be that, but any others will. I've tried re-installing, but I'd like to "uninstall" just that and then re-install, but can't figure out how to do that without uninstalling everything.
Any help would be GREATLY appreciated.
************** UPdate ******************
Won't work with V3.15, will wit V3.14.
Can anyone tell me how to manually install 3.14 in a Sansa e280v2 which needs the Sansa firmware along with Rockbox?
-
Is it at all possible it's to do with this change?
Looking at that theme, I notice it uses 14-Nimbus, in a viewport that is only 12 pixels high. Maybe that causes an issue? If this thread is correct, that would cause some of the text not to appear. You'd have to change the viewport sizes from 12 to 14, or change the font from 14 to 12 point.
https://forums.rockbox.org/index.php/topic,54008.0.html
Alternatively, could it be that you simply don't have that font installed? (that would cause the theme to default back to the failsafe theme)
-
Is it at all possible it's to do with this change?
THANK YOU for taking the time to answer.
It is the version change, I put 3.14 on a v2 unit - (through the installer - and the screen was fine.
I also have another v2 with 3.15 - not working - and another with 3.14 that IS working.
Make sense?
Looking at that theme, I notice it uses 14-Nimbus, in a viewport that is only 12 pixels high. Maybe that causes an issue? If this thread is correct, that would cause some of the text not to appear. You'd have to change the viewport sizes from 12 to 14, or change the font from 14 to 12 point.
https://forums.rockbox.org/index.php/topic,54008.0.html
I thought of that at first, but the fonts are there and it IS only the "While Playing" screen, the base theme is dandy - very readable for these old eye(s).
Alternatively, could it be that you simply don't have that font installed? (that would cause the theme to default back to the failsafe theme)
Naw, it's there.
As the installer doesn't allow me to pick an older version (so I could let it take care of the ...) wait a minute - it only needs the Sansa firmware for the bootloader, correct? Not for Rockbox itself. hmmm
I haven't tried a manual install of 3.14 for 2 reasons, 1) bricking it and 2) I can't find the right file for v2 - IN THAT ORDER.
-
You don't say in exactly what way the WPS isn't working.
The change mentioned in that other thread would mean the text not appearing - is that the problem you are having? If not, what exactly does the WPS look like? In what way is it not working?
Is it any better if you change to a smaller font?
-
I believe to install 3.14 you just download it and unzip it to the player (telling it to overwrite all files if it asks). But I don't have one of those players myself.
-
You don't say in exactly what way the WPS isn't working.
Sorry, it doesn't show up - at all - I get, what I believe is - the Rockbox fail-safe screen.
The change mentioned in that other thread would mean the text not appearing - is that the problem you are having? If not, what exactly does the WPS look like? In what way is it not working?
Is it any better if you change to a smaller font?
Obviously see above.
The manual install would be dandy, but, the 3.15 file is called "rockbox-sansae200v2-3.15.zip", all I can find is "rockbox-sansac200v2-3.14.zip". Note the e200 for V3.15 vs. the c200 for V3.14. Not sure if that okay.
-
Try the latest dev version we don't fix bugs in releases 5 years old
-
Try the latest dev version we don't fix bugs in releases 5 years old
I wouldn't expect you to, but FYI I did - same problem.
I just wanna put 3.14 back on a v2.
***************** UPdate **********************
FINALLY found e200_v2 3.14 firmware. Manually installed, then installed fonts and the skin and copied over the config.cfg over and HELLO NURSE!
I'll see in a wee while if it lasts.
-
I don't have a way to update the theme but here is the fix
Friskys2.cfg
iconset: /.rockbox/icons/tango_small.bmp
viewers iconset: /.rockbox/icons/tango_small_viewers.bmp
#Theme Name: Friskys2 (based on Friskys)
#Author: M. Loster (original Theme: T. Kliemann)
#Platform: Sandisk Sansa E200 (176x220)
#Rockbox version 3.7+
#Version: 1.0, Mar 10, 2011
#Licenced CC-BY-SA 3.0
selector type: bar (gradient)
statusbar: off
scrollbar: right
foreground color: E7E7E7
background color: 000000
line selector start color: ff8605
line selector end color: ff8605
line selector text color: 000000
font: /.rockbox/fonts/14-Nimbus.fnt
wps: /.rockbox/wps/Friskys2.wps
sbs: /.rockbox/wps/Friskys2.sbs
fms: /.rockbox/wps/Friskys2.fms
iconset: /.rockbox/icons/tango_icons.12x12.bmp
viewers iconset: /.rockbox/icons/tango_icons_viewers.12x12.bmp
backdrop: Friskys2.bmp
ui viewport: 5,40,166,146,-,-,-
Friskys2.wps
I'm not sure what the %Sx directive was for but I don't see it in the engine..
FrankenPod figured it out
# Filesize / Dir Name
%V(78,136,73,16,1)%Vf(E7E7E7)%Vb(000000)
#%s%ar%fs %Sx(KB)
%wd
%X(back.bmp)
%xl(A,travel.bmp,77,20,7)
%xl(B,bat.bmp,5,17,10)
%xl(C,vol.bmp,102,17,10)
%xl(D,play.bmp,70,188)
%xl(E,pause.bmp,70,188)
%xl(F,wind.bmp,70,188)
%xl(G,rewind.bmp,70,188)
%xl(H,hddled.bmp,37,155,8)
%xl(I,lock.bmp,63,153,2)
%xl(J,charge.bmp,50,150,2)
%xl(K,repm.bmp,5,154,5)
%xl(L,shuffle.bmp,21,155,2)
#%xl(X,codec.bmp,20,137,22)
#%?fc<%xd(Xa)|%xd(Xb)|%xd(Xc)|%xd(Xd)|%xd(Xe)|%xd(Xf)|%xd(Xg)|%xd(Xh)|%xd(Xi)|%xd(Xj)|%xd(Xk)|%xd(Xl)|%xd(Xm)|%xd(Xn)|%xd(Xo)|%xd(Xp)|%xd(Xq)|%xd(Xr)|%xd(Xs)|%xd(Xt)|%xd(Xu)|%xd(Xv)>
# Virtual LED
%t(0.2)%?lh<%xd(Hb)|%xd(Ha)>;%t(0.2)%?lh<%xd(Hc)|%xd(Ha)>;%t(0.2)%?lh<%xd(Hd)|%xd(Ha)>;%t(0.2)%?lh<%xd(He)|%xd(Ha)>;%t(0.2)%?lh<%xd(Hf)|%xd(Ha)>;%t(0.2)%?lh<%xd(Hg)|%xd(Ha)>;%t(0.2)%?lh<%xd(Hh)|%xd(Ha)>
# Hold
%?mh<%xd(Ia)|%xd(Ib)>
# Shuffle
%?ps<%xd(Lb)|%xd(La)>
# Charging
%t(0.5)%?bc<%xd(Jb)|%xd(Ja)>;%t(0.5)%?bc<%xd(Ja)|%xd(Ja)>
# Repeat Mode
%?mm<%xd(Ka)|%xd(Kb)|%xd(Kc)|%xd(Kd)|%xd(Ke)>
# Playback Mode
%?mp<|%xd(D)|%xd(E)|%xd(F)|%xd(G)>
# Volume
%?pv<%xd(Ca)|%xd(Cb)|%xd(Cc)|%xd(Cd)|%xd(Ce)|%xd(Cf)|%xd(Cg)|%xd(Ch)|%xd(Ci)|%xd(Cj)>
# Battery
%t(0.5) %?bl<%xd(Ba)|%xd(Bb)|%xd(Bb)|%xd(Bc)|%xd(Bd)|%xd(Be)|%xd(Bf)|%xd(Bg)|%xd(Bh)|%xd(Bi)|%xd(Bj)>;%?bl<%t(0)|%t(0.5)%xd(Ba)|%t(0)|%t(0)|%t(0)|%t(0)|%t(0)|%t(0)|%t(0)|%t(0)|%t(0)>
# Tape Travel - complex ;)
%t(0.1) %?mp<|%xd(Ad)|%xd(Af)|%xd(Ac)|%xd(Aa)>;%t(0.3) %?mp<|%xd(Aa)|%xd(Ad)|%xd(Aa)|%xd(Ac)>;%t(0.3) %?mp<|%xd(Aa)|%xd(Ad)|%xd(Ab)|%xd(Ab)>;%t(0.1) %?mp<|%xd(Ae)|%xd(Ad)|%xd(Ab)|%xd(Ab)>;%t(0.3) %?mp<|%xd(Ad)|%xd(Ad)|%xd(Ac)|%xd(Aa)>;%t(0.3) %?mp<|%xd(Ab)|%xd(Ad)|%xd(Aa)|%xd(Ac)>;%t(0.3) %?mp<|%xd(Ab)|%xd(Ad)|%xd(Ab)|%xd(Ab)>;%t(0.1) %?mp<|%xd(Af)|%xd(Ad)|%xd(Ab)|%xd(Ab)>;%t(0.3) %?mp<|%xd(Ad)|%xd(Ad)|%xd(Ac)|%xd(Aa)>;%t(0.3) %?mp<|%xd(Ac)|%xd(Ad)|%xd(Aa)|%xd(Ac)>;%t(0.3) %?mp<|%xd(Ac)|%xd(Ab)|%xd(Ab)|%xd(Ab)>;%t(0.1) %?mp<|%xd(Ag)|%xd(Ab)|%xd(Ab)|%xd(Ab)>;%t(0.3) %?mp<|%xd(Ad)|%xd(Ab)|%xd(Ac)|%xd(Aa)>
# Battery (Text) / Sleep Timer
%V(6,4,67,12,1)%Vf(60FF05)%Vb(000000)
%s%t(5)%al%bvV%ar%bl%%;%s%t(5)%ac%bt;%?bs<%t(5)%ac%s%Sx(Sleep Timer): %bs|%t(0)>
# Volume (Text) / Clock / Date / Pitch
%V(103,4,67,12,1)%Vf(60FF05)%Vb(000000)
%t(5)%?mv(3)<%alVOL%ar%pvdB|%ac%?cf<%cH:%cM:%cS|%cI:%cM %cP>>;%t(5)%?mv(3)<%alVOL%ar%pvdB|%ac%cy/%cm/%cd>;%?Sp<%t(5)%ac%s%Sx(Pitch): %Sp|%t(0)>
# Title (Filename)
%V(6,40,147,16,1)%Vf(E7E7E7)%Vb(000000)
%s%ar%?it<%it|%Sx(<Untagged>): %fn>
# Artist (Dir name) / Album (../Dir name) / Track / Year
%V(6,57,147,16,1)%Vf(E7E7E7)%Vb(000000)
%t(8)%s%ar%?ia<%ia|%?d(1)<[%d(1)]|[root]>>;%t(6)%s%ar%?id<%id|%?d(2)<%?ia<|../[%d(2)]>|%?ia<|../[root]>>>%?in<%?id< - %Sx(Tracknum) %in|%Sx(Tracknum) %in>|>%?iy< - %iy|>
# Playlist Num / Playlist Name
%V(6,80,147,16,1)%Vf(E7E7E7)%Vb(000000)
%s%ar%# %pp/%pe %?pn<"%pn"|>
# Next Track (Next Filename)
%V(6,97,147,16,1)%Vf(E7E7E7)%Vb(000000)
%s%ar%?It<%Sx(Next:) %It - %?Ia<%Ia|>|%?Fm<%Sx(Next:) %Sx(<Untagged>): %Fm|>>
# Bitrate / Sample Rate / RepGain
%V(6,119,147,16,1)%Vf(E7E7E7)%Vb(000000)
%s%ar%fbk %?fv<VBR|CBR> %fkk %?rg<%Sx(Replaygain): %(%Sx(Off)%)|%Sx(Replaygain): %rg|%Sx(Replaygain): %rg|%Sx(Replaygain): %rg|%Sx(Replaygain): %rg|>
# Filesize / Dir Name
%V(78,136,73,16,1)%Vf(E7E7E7)%Vb(000000)
%s%ar%fs %Sx(KiB)
# Track Time (Current / Total)
%V(78,155,73,16,1)%Vf(E7E7E7)%Vb(000000)
%ar%?mp<%(%pt%)|%t(10)%pc|%t(10)%pc|%pc|%pc>;%ar%?mp<%t(0)|%t(2)%(%pt%)|%t(2)%(%pt%)|%t(0)|%t(0)>
# Codec
%V(6,135,67,15,1)%Vf(60FF05)%Vb(000000)
%ac%fc
# PBar
%V(4,173,168,8,1)%Vf(60FF05)%Vb(000000)
%pb(0,0,168,8,progbar.bmp)
# Peak Meter
%V(7,194,62,20,1)%Vf(60FF05)%Vb(000000)
%pm
-
IIRC %Sx(text) causes the text in the brackets to be translated to the current language choice.
And if I also remember correctly, if it's used with text that doesn't have a translation listed, it makes the theme fall over. I remember a long time ago thinking that was unfortunate/awkward and it would be better if it just fell back to using the untranslated English
I don't know if that's the problem the theme is having - because my conversion to 320x240 has that line still in it, and it works on the ipod classic (at least it did when I made it). It might depend on what translations exist for each version of rockbox - perhaps the sansa with later rockbox versions doesn't have a translation listed for "KB"?
https://forums.rockbox.org/index.php?topic=52219.0
-
oh you know what I think I changed the Kb symbol to Kib around 3.15
and yep that fixes it!
-
Looking into it a little deeper it appears CHECKWPS doesn't act on those errors :(
I was able to find the logic in skin_parser (l:769) & skin_tokens (l:823)
We could make it output "??" in that case but we can't really get the original string value back at that point
https://gerrit.rockbox.org/r/c/rockbox/+/3894
In reference to your other question:
%?if(%Sx(KB), =, <ERR>)<KB|%Sx(KB)>
-
I think outputting ?? would be preferable to the entire theme just failing. The trouble is the translation stuff can get changed or updated independent of the theme (or the main WPS code?) and thus retrospectively cause themes to stop working, as here.
And it seems like it also varies by target.
At least if you got "??" you would get an immediate indication as to what the problem was.
Putting an error trap line into the WPS script every single time a theme uses the translation function seems a bit of a chore, but I guess it's a solution. Maybe the suggestion to do that could be included in the Custom WPS guide?
-
Yes the sim may have different or missing language strings
I liked making %Sx() return '' on error as this makes the conditionals
easy %?Sx{KB)<%Sx(KB),"KB"> but then It makes it hard to catch the error
for old themes
I already find the brittleness of the theme engine quite hard to deal with itd be nicer if it spit out a log with errorThat is
if anyone is volunteering :P
-
Not wanting to get involved with the programming aspect - it's been a LONG time since I programmed seriously, but the fix I see, while a bit confusing as to what constitutes the cfg file, the first set didn't fix this on 3.15.
can you be more specific? I see 2 lines that have changed, but ...
I didn't expect this to be so involved ... but I remember all too well (that's why the wife won't let me install my language machine)
-
you need both AFAICT...
the cfg file (/.rockbox/themes/Friskys2.cfg)
cfg file has the wrong icon names just copy paste the whole entry to the file or change the (2) lines
the wps file (/.rockbox/wps/Friskys2.wps)
just needs KiB instead of KB (Line 75)
Idk if i will work in 3.15 (maybe if you don't change the first one (.cfg) file
not sure when those icon sets changed TBH
I tested with the latest dev version
Ive also made a patch that will make it return <ERR> when it encounters this but its not in yet -- (need to think about it for a bit)
-
@Bilgus
I'm not clear what you are saying.
Are you saying that putting a conditional like "%?if(%Sx(text_to_translate_goes_here), =, <ERR>)<text_to_translate_goes_here|%Sx(text_to_translate_goes_here)>"
into a WPS script will resolve the problem as things are at the moment, or are you saying that you are planning to amend the codebase in a way that will mean that fix will work in future?
To be honest, I stopped bothering to use the translate function, because there didn't seem to be any easy way to know what terms had translations available on any given target. So a way to properly trap for such errors would seem to be very useful.
-
you need both AFAICT...
the cfg file (/.rockbox/themes/Friskys2.cfg)
cfg file has the wrong icon names just copy paste the whole entry to the file or change the (2) lines
the wps file (/.rockbox/wps/Friskys2.wps)
just needs KiB instead of KB (Line 75)
Idk if i will work in 3.15 (maybe if you don't change the first one (.cfg) file
not sure when those icon sets changed TBH
I tested with the latest dev version
Ive also made a patch that will make it return <ERR> when it encounters this but its not in yet -- (need to think about it for a bit)
I appreciate your efforts in regards to this inconsequential problem that seems to affect only me, but the patches do not work. A reinstalled 3.15/Fonts still leaves me with a working base skin and a fail-safe WPS.
AND this is ok, you need not - obviously - bang your head on the wall just for this. I can put 3.14 back on with little or no sweat.
BUT I DO APPRECIATE YOUR EFFORTS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
-
@Braverman
My understanding is that Bilgus was suggesting you use the latest Dev version, rather than 3.15
-
@Braverman
My understanding is that Bilgus was suggesting you use the latest Dev version, rather than 3.15
As you wish you had NEVER gotten involved with this ...
Nothing works. 3.15, latest DEV build, not changing the cfg file, changing it, changing the wps etc.
AND with the dev version I can not connect the unit to the PC, have to boot into the original F/W and getting into rockbox that way.
JUST to be clear, it's only the WPS screen that screwed.
-
I'll make you a build this evening with that patch I posted, we and I would rather get this fixed than the workaround being going back 2 versions
-
Frankenpod that would be after the patch on Gerrit
Currently it just kills and goes to failsafe when the translation Is missing
After that patch you can trap <ERR>
-
I'll make you a build this evening with that patch I posted, we and I would rather get this fixed than the workaround being going back 2 versions
If you wish ... This feels odd, as I can't see that this affects anyone but me.
BUT I do appreciate it, as I like to see what I did wrong in changing that.
You did see that I can not get into the player with the latest DEV build that the installer shows - it might just be a quirk with the e280.
-
TO be clear this is for the e200V2 I assume thats your player if not don't install it.
https://www.mediafire.com/file/gclbyiopdta5q6d/Sansae200V2_FRISKYSTHEMEFIX_rockbox-full.zip/file
to do the install you will hook to USB rename your current .rockbox folder to .rockbox_old (important in case we need to recover)
now simply unzip the .rockbox folder from th zip file to the ROOT of the device
SAFELY EJECT then restart
I copied the fixed theme into the install already
You say you had to go into the OF to use USB with the latest DEV build?
If after restarting on this latest one (with a clean install) you still cannot use USB let me know
We just fixed some issues for usb in the e200 V1 bootloader and while I doubt they are related I'd
like to get to the bottom of it
Clearly we've had a lot of changes since last release and would like to get
as many bugs as possible worked out before the next one
As long as someone is using the software on their device we (the DEVs) don't mind fixing it it'll likely benefit other users too
-
@Frankenpod I played around with the theme engine last night I was able to make it
do what you suggested but if I do that I will need to make another tag like ?%Lx(ID, FALLBACK)
(BTW I have no idea what I need to do to make a new tag either or the fallout)
Idk if its worth the added complexity and code given that we have a viable workaround
albeit a bit verbose it doesn't really make the theme take more ram once parsed
and it is backwards compatible
-
************ snip *******************
You say you had to go into the OF to use USB with the latest DEV build?
If after restarting on this latest one (with a clean install) you still cannot use USB let me know
We just fixed some issues for usb in the e200 V1 bootloader and while I doubt they are related I'd
like to get to the bottom of it
Clearly we've had a lot of changes since last release and would like to get
as many bugs as possible worked out before the next one
I'm trying but I can not get into the unit via USB. The original problem IS fixed, but this is - obviously - more inportant.
THANK YOU for taking the trouble.
Lemme know what I can do to help fix this.
As long as someone is using the software on their device we (the DEVs) don't mind fixing it it'll likely benefit other users too
I appreciate that - I hope others do as well.
OH BTW, with this can I copy over the config.cfg from a 3.14 unit that has all my settings in it - obviously?
-
@Braverman in regards to the config file.. best answer .. maybe
some settings cause problems --btw if it does act up if you could send me that cfg file
Ive been waiting to see a failing one
For the USB I'm not sure where to begin
you said the USB didn't work in 3.15 either?
First I'll try getting someone with an e200V2 to try a dev version
I'm not sure if there are hardware differences or its more general
if its a hardware issue if you wouldn't mind coming to
IRC I or someone else might be able to spin up some builds
for you to test as we try to narrow down the issue
you might also try another USB port on your pc sometimes device IDs change and cause issues
-
Ill post a few builds for you to try starting from just after 3.15 till present
-- EDIT ALL OF THOSE ARE BROKEN SORRY -
If you would try each till it fails to work..
-
Ill post a few builds for you to try starting from just after 3.15 till present
e280USB_01_278a76b_rockbox-full.zip/file
This allows USB, Theme does NOT work and when at the main menu the top banner is missing, and the backup config.cfg file from my working 3.14 seems to work.
/e280USB_02_7c87467b_rockbox-full.zip/
This allows USB, Theme does NOT work and when at the main menu the top banner is missing, and the backup config.cfg file from my working 3.14 seems to work.
e280USB_03_018372b_rockbox-full.zip/fileAllows USB, Theme works (I forgot to set it in the previous 2), the top banner was there it just wasn't what I expected as I hadn't set Friskys2 to be my skin, haven't copied over the config file.
e280USB_04_f3f9d1fb_rockbox-full.zip/file
All is well. Copied over the skin and that works well, so does the 3.14 config file.
e280USB_05_cb92280e_rockbox-full.zip/file
e280USB_06_99f333c_rockbox.zip/file
e280USB_07_b662ff9_rockbox.zip/file
USB fails, no fonts etc.
If you would try each till it fails to work..
I kinda have to post each or I'll just get way too confused.
I can meet yo on IRC after I do these (one thing at a time) - unless I misunderstood the timing. Just give me the server / group. Got a good program for it? I do NOT like Hexchat, or things have changed too much since I prowled around years ago.
Whatever I did, I can not get to these 2 anymore:
e280USB_05_cb92280e_rockbox-full.zip/file
e280USB_06_99f333c_rockbox.zip/file
-
@Braverman, Apparently this is a know problem we have a patch in the works with potential to fix it
i'll build that for you if you'd like to test
we have a webclient through kiwi IRC up on the page https://www.rockbox.org/irc/
-
@Braverman, Apparently this is a know problem we have a patch in the works with potential to fix it
i'll build that for you if you'd like to test
What is a known problem? What did I bitch about now :-) ?
we have a webclient through kiwi IRC up on the page https://www.rockbox.org/irc/
[/quote]
-
Checking in with other DEVs it appears this is a known problem for the V1 sansas (clip v1/v2, fuze v1, e200 v1 v2)
Short story is that code optimizations wreck the USB code for the V1s
We don't know what part of the code is failing only something specific to the V1AMS
And we have a workaround this build should work for you USB and theme
https://www.mediafire.com/file/acmzh30pilo2xag/e280V2_USB_Disable-Os_rockbox-full.zip/file
-
@frankenpod https://www.rockbox.org/wiki/CustomWPS#Showing_translated_strings_40LANGID_41
-
Checking in with other DEVs it appears this is a known problem for the V1 sansas (clip v1/v2, fuze v1, e200 v1 v2)
Short story is that code optimizations wreck the USB code for the V1s
We don't know what part of the code is failing only something specific to the V1AMS
And we have a workaround this build should work for you USB and theme
https://www.mediafire.com/file/acmzh30pilo2xag/e280V2_USB_Disable-Os_rockbox-full.zip/file
c
Ok, so V1, of which I have 3, will have a problem IF I move above 3.14? That's ok, they work wonderfully on 3.14 except they crash (explain in a minute) so I'll stay with that. This would be getting too many versions on the units I have.
1. In the testing of the several you've linked, I haven't done any exhaustive testing, just checking the basics.
2. (FWIW) In V3.14 possibly on BOTH V1's and V2's when I connected them and "actually do something - write a file, alter something" then disconnect them, I'll start to play/listen for about 4-5 minutes when the unit will freeze/white screen "Don't Panic" (ok Zephod) and I'll have to hold the pwr button down for 20 seconds or so, it'll shut down, then it'll boot right up and that's the end of it. I have never copied down the exception listed AFTER the Don't Panic, as I've always assumed that I was the only one having the problem. If I connect and do NOTHING but look around, it's fine.
Just thought I'd tell ya.
Get to the last 2 or 3 files in a while.
-
There is no need to test the others Sorry I didn't know of the V1 issue
the final one with optimizations disabled should work on all of those V2 e200s
https://www.mediafire.com/file/acmzh30pilo2xag/e280V2_USB_Disable-Os_rockbox-full.zip/file
and we can make another build for the V1s if you desire
-
There is no need to test the others Sorry I didn't know of the V1 issue
the final one with optimizations disabled should work on all of those V2 e200s
https://www.mediafire.com/file/acmzh30pilo2xag/e280V2_USB_Disable-Os_rockbox-full.zip/file
and we can make another build for the V1s if you desire
So do you want me to test the above file? On a V2?
Because I quite happy to leave my V1's on 3.14.
-
Braverman I'm pretty sure they will work as its a know issue and workaround
here is the latest V1 if you want it: https://www.mediafire.com/file/bp3zj096tysbnkr/e280V1_USB_Disable-Os_rockbox-full.zip/file
and again the prior for V2: https://www.mediafire.com/file/acmzh30pilo2xag/e280V2_USB_Disable-Os_rockbox-full.zip/file
-
Braverman I'm pretty sure they will work as its a know issue and workaround
here is the latest V1 if you want it: https://www.mediafire.com/file/bp3zj096tysbnkr/e280V1_USB_Disable-Os_rockbox-full.zip/file
and again the prior for V2: https://www.mediafire.com/file/acmzh30pilo2xag/e280V2_USB_Disable-Os_rockbox-full.zip/file
Ok, as I did throw this party, but left early, are yo happy where things are?
Like I said earlier, with all this in the past, I'd rather stay with 3.14 so that ll the unit are Stepford.
Do you want me to try the above files? Or ...
-
Up to you if you plan on leaving 3.14 the I don't see any reason to check em..
Thanks for your help thus far!
-
@frankenpod https://www.rockbox.org/wiki/CustomWPS#Showing_translated_strings_40LANGID_41
Hopefully that should avoid the problem for future themes. Only problem now, if I understand the situation correctly, is how to know which existing themes now need to be updated. Not helped by the fact that the simulator will behave differently as (as downloaded from 'extras') it uses an older RB version.
-
Up to you if you plan on leaving 3.14 the I don't see any reason to check em..
Thanks for your help thus far!
A bit 'O time later, but I've been migrating my 280's to 3.15 (suddenly too many prblems with 3.14.
... and have found a few (2 right now - well 3 but I can't remember the third) problems.
Should I open another thread?
-
Up to you if you plan on leaving 3.14 the I don't see any reason to check em..
Thanks for your help thus far!
A bit 'O time later, but I've been migrating my 280's to 3.15 (suddenly too many prblems with 3.14.
... and have found a few (2 right now - well 3 but I can't remember the third) problems.
Should I open another thread?
I'm not a developer, so not really for me to answer, but I would have thought you should first check if the problems you refer to still crop up with the most recent developer version. No point reporting issues that have already been fixed.