View Single Post
Posts: 179 | Thanked: 90 times | Joined on Dec 2007
#7
Originally Posted by Benson View Post
Sure, there's no hardware damage, but you wind up with the whole FM radio scenario, wherein:
Things don't work, and you don't know why. Turns out it's because some piece of software you're not using decided to make some changes to hardware configuration and not put it back. As simple as disabling that software? No, of course not! You need to go uninstall it. ******.
I agree that software itself shouldn't make hardware changes that affect other apps without warning the user. But a USB mode status bar applet that doesn't keep changes upon reboot, and doesn't make changes unless clicked?
Right now, there's a community solution, and it works. (Like the 770 BT statusbar applet, but that was before my time.) Nokia takes it, scrambles it, and hands us back a half-way functional, integrated to make it difficult to disable and replace, and we are better off how? Builds character, I guess.
I also agree that Nokia's implementation of some features leaves much to be desired... But they are a business. They are making money off of the hardware only. I for one, don't mind picking up the slack on this end. (That is, as long as Nokia upstreams the fixes from the OS community.)
If I were to add something, it'd be an adapter (either a cable, or short adapter) in the box. Then things just work, which is good. Crude workarounds for suboptimal hardware are OK at best, and likely bad in Nokia's hands.
I hardly consider the hardware suboptimal. I got my n810 for $330 + tax at CompUSA when they were going under. For the price, I couldn't ask for a better piece of hardware. Not that I wouldn't love to have had a OTG-USB micro-B cable included in the box.
As for that bug, it's interesting. That should not be happening, and fixing it in new devices should be a pretty high priority.
Honestly, I do think it's a hardware bug as not every n810 has this problem.(after I defend the quality of the hardware above, LOL...) The pulldown switch in the USB controller sticks on some units. My patch fixes it. But the problem is in the hardware, not the software... (I'm thinking either the mode pullup or pulldown transistor is getting burned on the USB chip...) No big deal for USB OTG, but a pain if you're setting mode via software.

Cheers,
kernelpanic
 

The Following User Says Thank You to kernelpanic For This Useful Post: