Thunderbolt who? How about HTC Pyramid?

Im surprised no one has pointed out that developers can optionally use the NDK to use dual cores for the apps. Yeah in order to use native activities you need 2.3, but at least for heavier processes like in games, and heavy computing/background processes, you can utilize the second core, significantly reducing the workload on one of the cores.
 
Im surprised no one has pointed out that developers can optionally use the NDK to use dual cores for the apps. Yeah in order to use native activities you need 2.3, but at least for heavier processes like in games, and heavy computing/background processes, you can utilize the second core, significantly reducing the workload on one of the cores.

I doubt many even know about it (I know I don't). But, I would ask, if the SDK has support for developers to use the cores separately, does the SDK not use OS/kernel-level calls? Meaning, even though the developer-level calls are there, doesn't the system-level implementations still need to be there to fully implement?
 
I doubt many even know about it (I know I don't). But, I would ask, if the SDK has support for developers to use the cores separately, does the SDK not use OS/kernel-level calls? Meaning, even though the developer-level calls are there, doesn't the system-level implementations still need to be there to fully implement?

Thing you have to remember is that the Android SDK was designed as a high-level language. All developers calls tell the OS what to do. If the OS cannot tell the system to use a specific core, the developer cannot utilize both cores. However, using the NDK developers can bypass using the OS to do the work and tell the system directly what to do (thats not quite the case, but for all intents and purposes for this discussion thats what it does.)

To be honest, I don't know C, so I havent really experimented with the NDK yet.
 
  • Like
Reactions: DolfanCole
If you do not know what the NDK is... it is not the same as the SDK. NDK = Native Development Kit

This allows use of native code and you could technically use this to make applications that are optimized for use on dual-core devices... even before this functionality is available in the SDK for Android!
 
I'm bringing this thread back to life. I am getting a HTC Sensation june 12th from walmart :o probably.
 
4.3" QHD screen, dual core 1.2ghz snapdragon coming to T-Mobile. WTF Verizon. Don't get me wrong the Bolt is bad ass but damn. Oh well, Verizon will get it a year late. Definitely doing one year on bolt.

Don't worry if the phone turns out to be a winner we will get the improved version in about 6-7 months...
 
Don't worry if the phone turns out to be a winner we will get the improved version in about 6-7 months...

And by the time that comes out tmobile, att and sprint will have another phone that will own what verizon brings late to the table. I really don't understand who is running verizon or who makes the decision on when phones come out or picking what will be released from the phone manufactures. I actually don't even know how this process is done really....oh well.
 
Verizon is in last place on bleeding edge tech and T-Mobile's in first place.
 
Verizon is in last place on bleeding edge tech and T-Mobile's in first place.


T-Mobile gets the nice phones but they get last place in the number of customers that can enjoy those phones.:)
 
So what... it's T-Mobile... I just left them... I was a long time customer with T-Mobile... and they lost all my respect with one very stupid move on their part... not that any other Wireless provider doesn't have one or two issue... I'm not willing to keep paying T-Mobile any more... I'm very happy with my Thunderbolt.

And I purposely got a one year contract because I knew there were going to be a lot of changes in the Smartphone market before the Thunderbolt came out.
 

Forum statistics

Threads
963,228
Messages
6,992,901
Members
3,164,993
Latest member
Maskin01