199 karma · joined March 8, 2021
The devices list, their Doom port names, Doom port authors and source links:
- Kodak DC260 (1998): Doom for Digita, author: James Surine, https://web.archive.org/web/20070720203938/http://digita.mam...
- Barnes & Noble Nook Simple Touch (2011): prboom4android, authors: Florian Schulze, L!TH!UM, Marko Štamcar & others, https://forum.xda-developers.com/t/doom-for-nook-simple-touc...
- Polycom VVX 600 (2012): doomgeneric, authors: ozkl, maximevince, Neil Bostian & others, https://neilbostian.github.io/#/doomphone
- Apple iPod Mini 2nd gen (2005) & SanDisk Sansa Clip+ (2009): Rockdoom, authors: Florian Schulze, The Rockbox Crew & others, https://www.rockbox.org/
- Texas Instruments TI-Nspire CX CAS (2011): nDoom 3, authors: Xavier Andréani, Mrakoplaz, critor & others, https://tiplanet.org/forum/archives_voir.php?id=6631
https://github.com/touchHLE/touchHLE is also great but needs patches for all but the most basic of apps.
For Porsches, it's easier as they do share infotainment stuff with other VAG vehicles and there is an online community that also tinkers with PCMs (Porsche's infotainment).
In my old 991.2 I managed to unlock Android Auto which was never officially supported using that community's efforts - it was completely functional, just disabled in favor of a CarPlay-only offering. (This changed with the 992 where it comes with both systems standard). And by plugging in a Motorola MA1 one has Wireless Android Auto on a car that never supported even the wired version. Sweet.
One day we might see a real Doom on 911 write up because the viral video from a few years ago is sadly fake. But just by going with the information/tools available in the modding community it's completely possible. Most of the GUI on it is Java apps BTW :)
"Android 11 - Gboard not triggering Enter keypress event on <textarea> in Chrome when there are suggested words in the Gboard suggestion strip"
https://issues.chromium.org/issues/40738692
The first frustration was getting push back from every place I tried reporting it - Android bug tracker, Chromium bug tracker,... and of course there is no public Gboard bug tracker, the only option is the "Send feedback" option in modern Android OS on Google devices that I'm sure gets lost somewhere. While I do understand each of the mentioned bug trackers has its rules, I had to give it a try considering there is no other way to actually write a technical bug report and get any Google developer to notice it :(
My suggestion is that each Google product/app should have a public bug tracker of some type. A place where power users and developers can reach the corresponding Google teams more easily.
Dynamically Redefined Character Set (DRCS) was introduced with DEC VT200 and even though online information is scarce, there is enough there to make it work on a real machine.
Even more interesting are the Yugoslavian/Slovenian video terminals with their own custom graphics modes and features - it is a lost art but we at the Museum are working on bringing it back!