12-30-2012 01:14 PM - edited 12-30-2012 01:22 PM
tleparskas wrote:beavertail:
what an excellent follow-up and answer!
I hope RIM developershave seen this!
No more returned products for them to deal with. Geez, a warehouse full of fairly decent playbooks, that could be fixed with an OS upgrade!
Nice.
Tom Leparskas
Ok so how come my PB camera is fine if the OS has a problem? Surely Beavertail just proved that a badly written app can hold onto the camera. If that is the case a debrick would fix it.
How can a debricked PB still give error 4003 unless it's hardware. I don't see the logic.
I wrote or maintained thousands of commercial programs and an error code is generated by logic code...
If xxx then write "error 4003". The os developers must know within 5 minutes of searching the code exactly where and how 4003 is generated, yet they are apparently "looking into it"
Where is the error code table? If there isn't one then heaven help us all.
01-01-2013 10:43 AM
jarviser wrote:The os developers must know within 5 minutes of searching the code exactly where and how 4003 is generated, yet they are apparently "looking into it"
Where is the error code table? If there isn't one then heaven help us all.
...or the dependency matrix. I guess RIM are not CMM compliant, else someone (maybe someone from the secret expert conclave) would tell us what 4003 really means..
01-01-2013 11:55 AM
I have fixed my 4003 bug and reported on the developer forum. It has nothing to do with the API but just "Bad" written code.
Goes to show you a lot of things can cause 4003 error. How one can have a dictionary for all its causes is questionable. I am sure the support guy is doing a fine job.
I am very happy with the Playbook. Watching a movie on it with its stereo sound is great. Funny, one of the major complaints of the miniPad is their 4:3 screen which doesn't fit a movie nicely.
How so interesting. I remember Apple fans said 7" is too small. Now they are following the 7" path but pick the wrong consumer screen format.
Goes to show you, media has a big influence on the masses. Enough media blarring the same thing and it will be taken as truth regardless of the underlying truth.
My family bought 8 Playbooks for Video Chatting because it is an amazing deal! All that hardware for just slightly higher than a 1-T storage or four Lightning cables!!
It probably won't be long before the Playbook price returns higher with a BB10 OS release, when the old Playbook can get a free upgrade. This is a double deal for me!!!
01-01-2013 12:44 PM
beavertail wrote:
Goes to show you a lot of things can cause 4003 error. How one can have a dictionary for all its causes is questionable.
That's just plain wrong. Programs put out error codes and only when the conditions mandate it. It's only questionable when poor programmers develop the code. Should be mandatory in any commercial programing shop to have a matrix of requirements versus programming plus all error codes listed along with triggers. You need to learn a bit more about coding before using that "developer" title.
01-05-2013 11:44 PM
Ok if it's not software and it's hardware check this, in my case the issue is intermitent, when my cameras stop working and I get 4003 error I just restart the PlayBook and that's it.
I have been doing this for a couple of months and it always works.
02-08-2013 08:29 AM
Even if the water indicators show it isn't wet, if you dropped it in water as you said, the camera is most likely fried. Sometimes only portions of the device are damaged. My guess is that over time the device will fail due to water.