[HaTaX]

Well, just wanted to throw this out there to help boost morale for BB10 on the PlayBook. Recently a BAR file for the clock application in 10.2 was released and I was surprised to find 1024x600 assets in there.

http://forums.crackberry.com/bb10-le...-alarms-816491

I didn't try loading it to the PB, but the fact that the assets are in there for the PB's screen size tells me they haven't forgotten about it just yet. In fact I'm willing to bet that the work needed to bring BB10 to the PB has proved far more challenging as that entire UI will need to be reworked to provide a decent user experience.

Anyway, just passing that along for a boost to the hope that some may still be hanging on to...

[Bilaal]

10.2 or not, BB10 on the PlayBook WILL be a good and fresh experience.

[RADEoN1337]

I just sideloaded the BAR onto my playbook, got nothing. rebooting it now for good measure

[antiRIM]

Well, just wanted to throw this out there to help boost morale for BB10 on the PlayBook. Recently a BAR file for the clock application in 10.2 was released and I was surprised to find 1024x600 assets in there.

http://forums.crackberry.com/bb10-le...-alarms-816491

I didn't try loading it to the PB, but the fact that the assets are in there for the PB's screen size tells me they haven't forgotten about it just yet. In fact I'm willing to bet that the work needed to bring BB10 to the PB has proved far more challenging as that entire UI will need to be reworked to provide a decent user experience.

Anyway, just passing that along for a boost to the hope that some may still be hanging on to...

Look at a clock version in 10.1 and see if 1024x600 is in that. Then we might have something if it isn't.

[antiRIM]

I opened it and this is what is in the assets file.

{
"type" : "PlayBook",
"orientationChangeSupported": "true",
"squareView": "false",
"listItemHeight": "109",

"alarmRowMinHeight" : "190",
"alarmRowMaxHeight" : "190",
"buttonBarHeight" : "121",
"buttonBarPadding": "20",
"noteTransPorDig" : "260",
"noteTransPorAlg" : "170",
"noteTransLanDig" : "50",
"noteTransLanAlg" : "50",
"timeLeftLabelTranslation" : "-20",
"nameAllowedSettingItem" : "true",

"timerSettingsStartPickerExpanded": true,

"worldMapDescriptor" : "720",
"worldClockListItemHeight" : "121",

"wcCityFontSize" : "9",
"wcCountryFontSize" : "7",
"wcTimeFontSizeLandscape" : "16",
"wcAmpmFontSizeLandscape" : "8",
"wcListItemHeightLandscape" : "109",
"wcListItemPaddingLandscape": "10",
"wcTimeFontSizePortrait" : "23",
"wcAmpmFontSizePortrait" : "11",
"wcListItemHeightPortrait" : "109",
"wcListItemPaddingPortrait" : "20",
"wcMapInList" : "false",

"sortLapListAscending": "false",

"": "" // This item allows every other item line to end with a comma - makes merging easier
}

[antiRIM]

And we have the A10...

{
"type" : "A-Series",
"orientationChangeSupported": true,
"squareView": false,
"listItemHeight": "109",

"alarmRowMinHeight" : "190",
"alarmRowMaxHeight" : "190",
"buttonBarHeight" : "121",
"buttonBarPadding": "20",
"noteTransPorDig" : "260",
"noteTransPorAlg" : "170",
"noteTransLanDig" : "50",
"noteTransLanAlg" : "50",
"timeLeftLabelTranslation" : "-20",
"nameAllowedSettingItem" : "true",

"timerSettingsStartPickerExpanded": true,
"timerTrailColor" : "#49b2e3",
"timerTrailMinuteRadiusLandscape": 192,
"timerTrailMinuteWidthLandscape" : 37,
"timerTrailMinuteMarginLandscape": -0.02,
"timerTrailMinuteRadiusPortrait" : 258,
"timerTrailMinuteWidthPortrait" : 51,
"timerTrailMinuteMarginPortrait" : -0.02,
"timerTrailHourRadiusLandscape" : 49,
"timerTrailHourWidthLandscape" : 9,
"timerTrailHourMarginLandscape" : -0.01,
"timerTrailHourRadiusPortrait" : 63,
"timerTrailHourWidthPortrait" : 11,
"timerTrailHourMarginPortrait" : -0.01,

"worldMapDescriptor" : "720",
"worldClockListItemHeight" : "91",

"wcCityFontSize" : "9",
"wcCountryFontSize" : "7",
"wcTimeFontSizeLandscape" : "16",
"wcAmpmFontSizeLandscape" : "8",
"wcListItemHeightLandscape" : "91",
"wcListItemPaddingLandscape": "20",
"wcTimeFontSizePortrait" : "16",
"wcAmpmFontSizePortrait" : "8",
"wcListItemHeightPortrait" : "91",
"wcListItemPaddingPortrait" : "20",
"wcMapInList" : false,

"sortLapListAscending": false,

"": "" // This item allows every other item line to end with a comma - makes merging easier
}

[FF22]

I just sideloaded the BAR onto my playbook, got nothing. rebooting it now for good measure

Would not even load:

"result::failure 821 Application-Requires-System: unrecognized system name 'BlackBerry 10'"

[jeroen_13]

Would not even load:

"result::failure 821 Application-Requires-System: unrecognized system name 'BlackBerry 10'"

Open up the bar file, change the 'target' from 10.0 to 2.1 in the bar-descriptor.xml and resign the app. Now it will sideload, but i dont think it'll work

[BB_Bmore]

If Kris shows us how to load the crippled 10.0 dev OS and we load some of these 10.2 updated bar with the PlayBook res...maybe just maybe...*fingers and toes crossed*

Sent from  using Tapatalk

[masterscarhead1]

If Kris shows us how to load the crippled 10.0 dev OS and we load some of these 10.2 updated bar with the PlayBook res...maybe just maybe...*fingers and toes crossed*

Sent from  using Tapatalk

You load the 10.0 dev by downloading it, and installing via dingle

[sok2507]

Just came across this video of OS10.x on PB - uploaded last week....

[BB_Bmore]

I thought I read a comment from him stating that he used Dingle but with a work around that he would tutorial at a later date? He warned not to try and load it as it would soft brick the PlayBook.

You load the 10.0 dev by downloading it, and installing via dingle

[FF22]

Open up the bar file, change the 'target' from 10.0 to 2.1 in the bar-descriptor.xml and resign the app. Now it will sideload, but i dont think it'll work

Thanks but I don't sign and since it probably won't work......

[jeroen_13]

Thanks but I don't sign and since it probably won't work......

It wont work anyways since the Native/Cascades/Air SDK's are very different from the Playbook SDK.

When BB10 hits the Playbook the SDK's will be the same.

[SCrid2000]

It wont work anyways since the Native/Cascades/Air SDK's are very different from the Playbook SDK.

When BB10 hits the Playbook the SDK's will be the same.

I'm pretty sure it won't be signable without BlackBerry keys with system level permissions. Also, you'd need to include the cascades libraries.

[anon(4243545)]

I haven't understood if 1024x600 assets are present also in OS 10.1 apps. However, the fact that 10.2 apps support PlayBook resolution isn't it an overwhelming evidence that OS 10 will soon arrive on our tablets?

[FF22]

I haven't understood if 1024x600 assets are present also in OS 10.1 apps. However, the fact that 10.2 apps support PlayBook resolution isn't it an overwhelming evidence that OS 10 will soon arrive on our tablets?

Well, you have used rim/bbry's favorite word when it comes to the PB - SOON. In their dictionary (those Canadians) it can mean anywhere from a month or two to months and months - maybe even a year. But it does not generally mean, well, SOON!

[DurdenLunarius]

Well, you have used rim/bbry's favorite word when it comes to the PB - SOON. In their dictionary (those Canadians) it can mean anywhere from a month or two to months and months - maybe even a year. But it does not generally mean, well, SOON!

"When will then be now?" "...Soon"



I think the important question we all seem to not be asking is: "How soon?"

[anon(4243545)]

Well, you have used rim/bbry's favorite word when it comes to the PB - SOON. In their dictionary (those Canadians) it can mean anywhere from a month or two to months and months - maybe even a year. But it does not generally mean, well, SOON!

Ok, F2, you're right, but you did not answer to my question: do you know if also 10.1 apps got 1024x600 assets? Thanks you in advance. Irony against RIM is not useful: I'm very angry too for this update, but now we must find evidences.

[FF22]

Ok, F2, you're right, but you did not answer to my question: do you know if also 10.1 apps got 1024x600 assets? Thanks you in advance. Irony against RIM is not useful: I'm very angry too for this update, but now we must find evidences.

I don't know about inclusion of pb's "needs" in the newer OS versions. While I do occasionally read about experiments and dissections of the OS' components to see if the pb is addressed, until there are actually real working versions (even unofficial ones), it remains more conjecture than valuable.

[anon(4243545)]

Ok... but now I'd like an answer from HaTaX or antiRIM! What do you know about OS 10.1 apps? And do you think that the presence of PlayBook resolution means that OS 10.2 will come on our tablets?

[antiRIM]

Ok... but now I'd like an answer from HaTaX or antiRIM! What do you know about OS 10.1 apps? And do you think that the presence of PlayBook resolution means that OS 10.2 will come on our tablets?

Unfortunately the 10.1 clock app also supports 1024x600 resolution under assets. Anyway, located in the manifest.mf file in any app, you will see what OS is required for that app to work. Only ONE app sys.bugreporter.bar actually states Tablet OS 10.0.9.0 Required. All other apps say Blackberry 10/10.0.9.0 (or higher) .

[pacoman03]

According to Xsacha, "The apps on Blackberry 10.2 all support Playbook The ones from 10.1 didn't." http://forums.crackberry.com/bb10-le...aybook-817805/

[Synerworks]

The Playbook can work with BB10.2 but Blackberry has added restrictions to keep it from running by removing screen resolution support and target platform checks. Sure the bloated BBOS will have a tough time running with the limited memory resources, but the Playbook is essentially a STL100-1 without a radio and extra GB. If the security framework was stripped from BBOS, the Playbook would have been running BB10.2 already instead of us just waiting for them to get around to it when their developers are bored and don't have anything better to do.

[joshua_sx1]

So, it is a glimmer of false hope then...

Posted via Z10