1.6 Upgrade Check
- This topic has 0 replies, 1 voice, and was last updated April 14, 2026 at 8:54 AM by .
Viewing 1 post (of 1 total)
Viewing 1 post (of 1 total)
- You must be logged in to reply to this topic.
NewHome › Forums › OSSC, OSSC Pro and DExx-vd isl › OSSC – DIY & Repair Support › 1.6 Upgrade Check
tl:dr tried to mod 1.6 OSSC for higher firmwares. Tore off top pad of R35. Soldered to a via labelled LED0 in line with that pad on the kicad PCB diagram instead. Things seem to work, but I’m still a little concerned so I’m asking here what to look out for if this actually failed.
Hello all,
Today I modded my 1.6 OSSC to take advantage of the 1.21 firmware via the hardware mod, in particular the alt firmware loading to run with voidscaler. Anyway while removing R35 I accidentally tore off the pad that would be soldered to for the mod. Instead of soldering to that pad, I instead soldered the wire to a small, nearby via on the underside of the PCB. On the kicad file it was labelled as LED0, went through all of the layers and was on the same trace as the original intended pad. Theoretically, it should work fine, and everything does seem to be working. I’ve tried line 6x mode with 240p, 3x with 480p, setting HDR and VRR flags (although I did not get any sync drop with VRR enabled, it was displaying a picture just fine) and playing with a few other settings and everything seemed to work just fine. Even voidscaler works fine (although the LCD is less bright and seems to flicker), however, I thought I would ask here just in case. What signs should I be looking out for if the modification failed?
Thanks in advance all.
EDIT: Voidscaler seems to work rather intermittently, although I was using a component to VGA converter, so that might have something to do with it more than the OSSC itself, awaiting responses from the a thread about the voidscaler firmware.
| Cookie | Duration | Description |
|---|---|---|
| _gat | 1 minute | This cookie is installed by Google Universal Analytics to restrain request rate and thus limit the collection of data on high traffic sites. |
| Cookie | Duration | Description |
|---|---|---|
| __gads | 1 year 24 days | The __gads cookie, set by Google, is stored under DoubleClick domain and tracks the number of times users see an advert, measures the success of the campaign and calculates its revenue. This cookie can only be read from the domain they are set on and will not track any data while browsing through other sites. |
| _ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
| _gid | 1 day | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
| Cookie | Duration | Description |
|---|---|---|
| IDE | 1 year 24 days | Google DoubleClick IDE cookies are used to store information about how the user uses the website to present them with relevant ads and according to the user profile. |
| test_cookie | 15 minutes | The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies. |
| Cookie | Duration | Description |
|---|---|---|
| ct_checked_emails | session | No description |
| ct_has_scrolled | session | No description |
| ct_mouse_moved | session | No description |
| ct_screen_info | session | No description |
| wordpress_apbct_antibot | session | No description |
| wp_woocommerce_session_9cc3598a6315be16da4f85bb374cf6a5 | 2 days | No description |