Jump to content
|Topic||Stats||Last action by|
|I miss the themes from the good old msstyles (uxtheme.dll) days||
|Windows 10 Technical Preview||
|Printing via RDP with a none supported printer||
|Quebec resident Alain Philippon to fight charge for not giving up phone password at airport||
|Some changes at the top (Administrators & Founder groups)||
Posted 03 July 2012 - 09:49
Posted 03 July 2012 - 10:23
Posted 03 July 2012 - 10:36
Posted 03 July 2012 - 10:48
So on the S+, the camera doesn't "work" with its own liboemcamera.so, but it does with the one from the Wonder/Exhibit. And on the Wonder/Exhibit, the camera doesn't "work" with their own libcamera.so, but it does with the one from the S+. Yeah that's Samsung for you - totally incompetent and inconsistent. You guys have no idea how much **** I've seen from them by working on this and the kernel. For example they can have one particular camera parameter in one phone, and in another phone they can have the same parameter, just with a different name. I think they must be braindead or something, because how much easier wouldn't it be for themselves and others if they maintained some consistency between phones?
But as I've already said, a major part of the issues are because Samsung are complete twats by insisting on doing everything different from the standard norm.
Posted 03 July 2012 - 10:52
Posted 03 July 2012 - 10:59
Posted 03 July 2012 - 12:57
Posted 03 July 2012 - 13:04
Posted 03 July 2012 - 13:33
Does that include the unofficial ports?
Posted 03 July 2012 - 16:07
Posted 03 July 2012 - 16:27
I wonder how many devices would get android 4.0 if qualcomm released openmax drivers for the MSM7227 chip. As that 600mhz chip is in millions of phones. Cyanogenmod android 4.0 for those users if awful as those drivers are needed to access many functionalities.