[BETA] Orape Client for Android !

Yo guys,

I worked on a Android version of Orape Client, i need you to see how it performs on different device

It only have basic on-screen controls, and only the pad is working atm, there is also no multi-touch support atm !

If you would like to help me, just test it and report back your experience

What you need ? Adobe AIR 15, you can grab if from the PlayStore

Screen:

Scans:

LAST MINUTE FIX HOLD ON

Seems epic

As always: hackers are the ones introducing features and fixing things...

For idea itself: memory leaks are going to be somewhat a problem, but i've read somewhere that System.gc() works only in flash debugger and AIR so that memory leak fix that we have now (and that dont work on desktops/laptops) just might work on Android.

Originally Posted by theboo

As always: hackers are the ones introducing features and fixing things...

For idea itself: memory leaks are going to be somewhat a problem, but i've read somewhere that System.gc() works only in flash debugger and AIR so that memory leak fix that we have now (and that dont work on desktops/laptops) just might work on Android.

Simply put, invoking the garbage collector manually isn't actually a fix. The reason why it's available for debug environments only is because it's never intended to be relied on.

Originally Posted by krazyshank

Simply put, invoking the garbage collector manually isn't actually a fix. The reason why it's available for debug environments only is because it's never intended to be relied on.

Doesnt change the fact that even Kabam devs resort to hack/workaround to force GC to run instead of fixing leaks themselves:

Code:

getlex                QName(PackageNamespace("com.hurlant.util"), "Memory")
callpropvoid        QName(PackageNamespace("", "#0"), "gc"), 0

is what i found in code by chance. And it tries to force GC by invoking local connection to 'foo' twice.
=\.

Oh, and ontopic: @IziLife (8 hours ago)

Scans:
LAST MINUTE FIX HOLD ON

Originally Posted by theboo

Doesnt change the fact that even Kabam devs resort to hack/workaround to force GC to run instead of fixing leaks themselves:

Code:

getlex                QName(PackageNamespace("com.hurlant.util"), "Memory")
callpropvoid        QName(PackageNamespace("", "#0"), "gc"), 0

is what i found in code by chance. And it tries to force GC by invoking local connection to 'foo' twice.
=\.

Oh, and ontopic: @IziLife (8 hours ago)

That's pretty funny, thanks for the laugh.
You'd think that they'd actually try to fix the prevalent issue that has plagued every player a bunch of times for years now. Oh well.

Originally Posted by theboo

Doesnt change the fact that even Kabam devs resort to hack/workaround to force GC to run instead of fixing leaks themselves:

Code:

getlex                QName(PackageNamespace("com.hurlant.util"), "Memory")
callpropvoid        QName(PackageNamespace("", "#0"), "gc"), 0

is what i found in code by chance. And it tries to force GC by invoking local connection to 'foo' twice.
=\.

Oh, and ontopic: @IziLife (8 hours ago)

Umm, Kabam didn't write the hurlant library, they only use it. Plus, how is calling localconnection twice in hurlant class "Memory" with a function named "gc" == System.gc() ? Maybe it is some kind of hack that works with flash, but still, Kabam didn't write any of that code and I would be surprised if the actual client makes use of that code outside of the hurlant library.

Originally Posted by nilly

Umm, Kabam didn't write the hurlant library, they only use it. Plus, how is calling localconnection twice in hurlant class "Memory" with a function named "gc" == System.gc() ? Maybe it is some kind of hack that works with flash, but still, Kabam didn't write any of that code and I would be surprised if the actual client makes use of that code outside of the hurlant library.

Exactly. 2short

GIMME GIMME GIMME GIMME

if this is legit you should bring it out on iOS

Originally Posted by We-Are-Anonymous

if this is legit you should bring it out on iOS

You need to jail break first

Originally Posted by NameInUseToT

You need to jail break first

Already have

Originally Posted by We-Are-Anonymous

Already have

Sorry guys i got a bit busy these days (working on a new super mega awesome secret thing

)

The client is ready, but i have to send it to jnoob for the last part, i'll re-upload it in few minutes stay tuned

It will probably just implode, but...

crap, where's my kindle fire...

ill test this for you, i have razr m xt907

[BETA] Orape Client for Android !

Similar Threads

Tags for this Thread