-
[off_topic]
@ HaTax
Dude, Thank you for the push.
I started looking at building aps late last night.
I have already send the "send me my keys " email to blackberry
5 minutes after that I received the file to set up my keys.
I have now successfully written a "test" app that calculates the material needed for a ceiling tile installation .
I have singed said app.
I have installed said app.
Now I am gonna upload said app.
Thanks again.
[/topic]
This process form start to finish, literally took 2 hours TOPS.Last edited by molson0; 07-29-11 at 11:47 AM.
07-29-11 11:29 AM - Molson, glad you could find some use from the knowledge! Once you're setup and you understand the steps, it really does go fast. AIR development isn't too bad either if you're familiar with java/ecma. Once you get it down, building and testing goes pretty fast.
Just as an update, I've got the newer market working now, but I'm working on the downloading bug. Kind of a pain as they've obviously made this area complex to prevent this kind of stuff. Ohh well, I'm sure I'll figure something out.07-29-11 06:25 PM - Is the fact that this is an older version of the Market the reason some apps don't show up in the market? Works almost flawlessly though!Molson, glad you could find some use from the knowledge! Once you're setup and you understand the steps, it really does go fast. AIR development isn't too bad either if you're familiar with java/ecma. Once you get it down, building and testing goes pretty fast.
Just as an update, I've got the newer market working now, but I'm working on the downloading bug. Kind of a pain as they've obviously made this area complex to prevent this kind of stuff. Ohh well, I'm sure I'll figure something out.07-29-11 11:50 PM - Could be that, could also be that the thumbprint that is reported is not recognized. That's actually something I can probably fix in the app itself, so that people don't have to jump through endless hoops to modify the build.prop file.
I'll keep this in mind as I'm doing my work on V2. Currently it's downloading 90% of the time, so I think I'm getting the hiccups worked out. You'll all be much happier when this version is done. It sees all the installed apps and all the content panes work. Honestly everything but the queued downloads work great.07-29-11 11:58 PM - Well, your work is definitely appreciated! I has actually uninstalled the app player until I came across this thread. Making for a fun weekend so far. lolCould be that, could also be that the thumbprint that is reported is not recognized. That's actually something I can probably fix in the app itself, so that people don't have to jump through endless hoops to modify the build.prop file.
I'll keep this in mind as I'm doing my work on V2. Currently it's downloading 90% of the time, so I think I'm getting the hiccups worked out. You'll all be much happier when this version is done. It sees all the installed apps and all the content panes work. Honestly everything but the queued downloads work great.
Can't wait to give the new stuff a shot!07-30-11 12:10 AM - Hey!!! You're all getting quiet again!
Guess it's time to stir the pot with some new news. I've got version 2.3.3 working extremely well, all the functions of the application itself work for me without a hitch. Shows all installed apps, does updates, downloads on a consistent basis, installs them properly, etc.
What's that? Somewhere I hear in the background "pics or it didn't happen"...
Here ya go.07-30-11 06:47 PM - So, I can haz!? No seriously dude, you need to be a BBM contact of mine! lolHey!!! You're all getting quiet again!
Guess it's time to stir the pot with some new news. I've got version 2.3.3 working extremely well, all the functions of the application itself work for me without a hitch. Shows all installed apps, does updates, downloads on a consistent basis, installs them properly, etc.
What's that? Somewhere I hear in the background "pics or it didn't happen"...
Here ya go.07-30-11 06:51 PM - wow looking forward to this version, great workHey!!! You're all getting quiet again!
Guess it's time to stir the pot with some new news. I've got version 2.3.3 working extremely well, all the functions of the application itself work for me without a hitch. Shows all installed apps, does updates, downloads on a consistent basis, installs them properly, etc.
What's that? Somewhere I hear in the background "pics or it didn't happen"...
Here ya go.Last edited by Covsteve; 07-30-11 at 07:12 PM.
07-30-11 07:09 PM - Well, right now they don't have the OpenGL system working in hardware mode and we're stuck with software rendering. That's slow, and doesn't emulate a lot of the OpenGL commands that a full hardware driver would. This is easily the most difficult portion of the system to pass through or wrap in the Android environment. It's not impossible, but it would be the most time consuming to get it working.
Actually I think they will get this working before launch as not many games will work properly without it. And really, both systems are using OpenGL, so they may just have to write a wrapper for the OpenGL instructions to be passed to QNX.
If anything, this will be the portion of the system they'll be releasing bug fixes on.
Yup! The Playbook has a completely stock 2.3.3 build on it, or at least that's how it started... I think most of the compatibility issues stem from the modifications done to the core system and the oddities that come along with it.
For instance, the network connection. It's passed through to Android as not having a real IP address and such. Some applications determine network connectivity in different ways, (Asking the system vs checking it's IP address vs if it can see an internet address) and sometimes they're not able to properly determine what's going on because of the changes.
And also, the file system is not what you would find on a normal Android system. We're missing the entire "/cache" folder and a lot of applications use that folder for cache storage. If the application is written well enough to work without needing that particular directory, it works. Otherwise if the programmers depended on that folder being there, the application crashes. There's lots of other little oddities here that cause some apps to just crash and burn.
I'm actually working on making GMail functional right now. I'm not sure how feasible it is overall, but I think I can get a working copy made with not too much effort. There's quite a few apps that just don't work right if they want to display HTML content, and I am assuming it is from changes to the core system. Honestly I wonder if it's because they're wanting to build a wrapper for HTML content to run it through the QNX HTML rendering system.
Anyway, Market has survived the last 24 hours with no downloading issues. This looks like it will be a good Market for use on our devices! Also, when this is released initially it won't have "all" the apps as I haven't done anything with the thumbprint yet. Normally you'd just modify your build.prop file, but since we don't have easy access to that, I'll need to see if it can be fixed from the application side. NOT ideal in the slightest, but I want to make this a drag and drop install to keep things easy for people.
I think I'll be posting up a performance guide in the next few days. I've noticed adjusting a few settings here and there really speed up the UI and I figured a setup guide would help everyone get the most from the system. Actually the speed of it after the Google apps are installed and some other apps from Marketplace surprised me, it's still nice and "snappy!"07-31-11 02:07 PM - You are the man. Any idea when we can try this out?Well, right now they don't have the OpenGL system working in hardware mode and we're stuck with software rendering. That's slow, and doesn't emulate a lot of the OpenGL commands that a full hardware driver would. This is easily the most difficult portion of the system to pass through or wrap in the Android environment. It's not impossible, but it would be the most time consuming to get it working.
Actually I think they will get this working before launch as not many games will work properly without it. And really, both systems are using OpenGL, so they may just have to write a wrapper for the OpenGL instructions to be passed to QNX.
If anything, this will be the portion of the system they'll be releasing bug fixes on.
Yup! The Playbook has a completely stock 2.3.3 build on it, or at least that's how it started... I think most of the compatibility issues stem from the modifications done to the core system and the oddities that come along with it.
For instance, the network connection. It's passed through to Android as not having a real IP address and such. Some applications determine network connectivity in different ways, (Asking the system vs checking it's IP address vs if it can see an internet address) and sometimes they're not able to properly determine what's going on because of the changes.
And also, the file system is not what you would find on a normal Android system. We're missing the entire "/cache" folder and a lot of applications use that folder for cache storage. If the application is written well enough to work without needing that particular directory, it works. Otherwise if the programmers depended on that folder being there, the application crashes. There's lots of other little oddities here that cause some apps to just crash and burn.
I'm actually working on making GMail functional right now. I'm not sure how feasible it is overall, but I think I can get a working copy made with not too much effort. There's quite a few apps that just don't work right if they want to display HTML content, and I am assuming it is from changes to the core system. Honestly I wonder if it's because they're wanting to build a wrapper for HTML content to run it through the QNX HTML rendering system.
Anyway, Market has survived the last 24 hours with no downloading issues. This looks like it will be a good Market for use on our devices! Also, when this is released initially it won't have "all" the apps as I haven't done anything with the thumbprint yet. Normally you'd just modify your build.prop file, but since we don't have easy access to that, I'll need to see if it can be fixed from the application side. NOT ideal in the slightest, but I want to make this a drag and drop install to keep things easy for people.
I think I'll be posting up a performance guide in the next few days. I've noticed adjusting a few settings here and there really speed up the UI and I figured a setup guide would help everyone get the most from the system. Actually the speed of it after the Google apps are installed and some other apps from Marketplace surprised me, it's still nice and "snappy!"
Posted from my CrackBerry at wapforums.crackberry.com07-31-11 02:13 PM - Soon. I want to do some additional testing this time around, make sure everything is ship shape before it's released to the masses. Also would like to include some other bonuses, like GMail working.
There's some other things in motion as well, this may end up being more then just a post here in the forum.
Just figured I'd take a little more time with it this time around. Last time, I posted that (very buggy) version up pretty hastily after I got it working. This time I want to pull out all the debugging code and such, keep it to a bare minimum of modifications, etc.
No worries, you'll have a (better) working Marketplace very soon.
07-31-11 03:10 PM - I can't wait to try it!Soon. I want to do some additional testing this time around, make sure everything is ship shape before it's released to the masses. Also would like to include some other bonuses, like GMail working.
There's some other things in motion as well, this may end up being more then just a post here in the forum.
Just figured I'd take a little more time with it this time around. Last time, I posted that (very buggy) version up pretty hastily after I got it working. This time I want to pull out all the debugging code and such, keep it to a bare minimum of modifications, etc.
No worries, you'll have a (better) working Marketplace very soon.07-31-11 03:37 PM
