Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
1) get an idea for a cool app
2) evaluate feasibility and execution
3) ensure accessible data streams and APIs
4) get excited and realize the idea is doable
5) see someone has done that exact thing and it's already published on the Appstore :/10 -
Yesterday I bought myself a PSP to relive some of my childhood memories, run custom firmware on it and so on. Unfortunately however, the battery on this one is seriously puffed up, and I need one in order to update the firmware from 5.50 CFW (the seller actually modded it too!) to 6.61 OFW (to then install CFW from there again).
I figured that I might as well have a kick at disassembling the battery for good measure, to take out its controller and power it from my lab bench power supply. I set it to 3.70V, double-checked the connections.. nothing. I raised the voltage to 4V, still nothing.
There is absolutely nothing wrong with the controller from looking at it. The magic smoke is still in there, all I did was removing the housing and snipping off the battery. I measured the cell voltage and it was only some residues at 0.01V. Might be internally shorted or something, normally even dead cells settle back at 3.7V unless you keep them shorted externally.
After seeing this so many times now with controllers, I'm starting to get a feeling that manufacturers actually program these things to look at the battery voltage, and when it reaches 0V, to just make the controller kill itself. Doesn't matter if the controller's electronics are still good, just fucking kill it.
If true, that is very, VERY nasty. It would also explain why batteries in laptops especially all have different form factors, despite having used regular 18650's internally for a very long time. It would explain why they're built like tanks. It would explain why manufacturers really don't want people in there. Yes there are safety issues and you're literally diffusing a bomb. Since recently we've also got space optimization.. anything for half a mm of thickness, amirite? But doing it this way is fucking disgusting. There is absolutely no reason for the controller to kill itself when the cell dies. Yet it seems like it does.
PS: I've posted the original picture on https://ghnou.su/pics/... now if you're interested. I noticed in my previous rant that devRant really squishes these down.
12 -
May 2020, for me, was still a massively shit month. All of my tech has eaten some amount of shit:
- Spare PC: Board and last spare PSU up in literal smoke all at once.
- PS3: Suddenly rejects *just* the OEM HDD. Also refuses all CFW for seemingly no reason despite being hacked.
- Xbox One: External HDD is having more and more corrupt reads and is taking longer and longer to serve data.
- Wii: Nearly ate shit as the OS disappeared mid-game for fucking no reason but thanks to my 5-year-ago forethought, saved. (God bless pre-boot homebrew menus)
- Phone: grabbed it to read an overheat warning with cold-ass hands, screen exploded.
- Desktop: Literally just now, PSU and possibly GPU fucking died mid-game.
Anything else? You still got like 4 days, you still got time to fucking kill me, May, you fucking bitch8 -
Anyone actually took part in the psp community back in the days?
We ran fucking everything on these things.😁3 -
Turns out the reason the selection of RA cores on the PS3 sucks so much dick is that it has a half-complete OpenGL implementation.
Fuck it, we're doing it live. I've got CFW, i'll dynarec if I damn well please. If it won't compile i'll fucking make it compile, I don't give a fuck about "sanity restraints" and "needing OpenGL 2" and "LV1 required" I can fucking replace all of LV1 and LV2 if I fucking want FUCK YOU
The Cell processor is pretty beefy, I could prolly do it all-CPU if I wanted.8 -
Slight behaviour change request. If you hit reply to someone then their id is added to the message. If you go back to view the thread, and hit reply again then another copy of their id is added.
A simple clear won't work as someone may be mid rant reply, but perhaps if the app checks if the id is already in the message window before adding in another copy.
@dfox1
Top Tags
Weekly Rant
View