Beda magic dan hero

by angolming » Fri, 27 Nov 2009 19:39:26 GMT


Sponsored Links
 Guys .... Bisa diberitahu beda spec antara magic dan hero tentang :

1. Screen size and res
2. Proc ... Mana yg lbh cepat
3. Mem ... Mana yg lebih besar

Thnx.
Sent from my BlackBerry smartphone from Sinyal Bagus XL, Nyambung Teruuusss...!
--~--~---------~--~----~------------~-------~--~----~
=========================
Google Groups "

=========================
-~----------~----~----~----~------~----~------~--~---



Beda magic dan hero

by Bayu Wicaksono » Fri, 27 Nov 2009 19:55:32 GMT


 Semuanya sama.. :D
beda ada di Camera, Magic 3,2Mp Hero 5Mp
Hero punya jack 3.5mm Magic kaga... :D

and IMO.. Magic trackball nya lbh enak.. :P





--~--~---------~--~----~------------~-------~--~----~
=========================
Google Groups "

=========================
-~----------~----~----~----~------~----~------~--~---


Sponsored Links


Beda magic dan hero

by widi dream » Fri, 27 Nov 2009 21:30:13 GMT


 trus kalo cliq kira2 berapa om Bayu ?
:D

salam -widi-




Hero barunya klo ga salah sekitar 5.8jt - 6.5 jtan.. berarti 2nd ya sekitar
5.5jt kali yah..?

On Fri, Nov 27, 2009 at 7:27 PM, Gresye wiranata <gresye.wiran...@gmail.com>



--~--~---------~--~----~------------~-------~--~----~
=========================
Google Groups "

=========================
-~----------~----~----~----~------~----~------~--~---



Other Threads

1. Update view on worker thread

Hey Guys,

I am seeing some weird issues and looking to see if anyone knows what
is going on. I have a BroadcastReceiver which updates some views on
receiving an event. Some psudo code is shown below. What happens is
the function runs fine and the app seems to update the textviews BUT
when i then try to clear the textviews parent and add new textviews
the linearlayout(parent) blanks out and will now draw any of it's
children. Has anyone seen this before?

public class PMDynIntentReceiver extends BroadcastReceiver {

public void onReceive(final Context context, Intent intent) {

Thread th = new Thread() {

run() {
// Pull a view out of an array.
// Push the view into a update data as show below
//thats it
}
};

th.start();

}

}


public static void updateData(Hashtable data, View x)
{
textView text = (TextView)x.findViewById(R.id.sbTeamAStat1);
text.setText(data.get(something));
}

Tom

--~--~---------~--~----~------------~-------~--~----~

2. Need to unload driver and restart wpa_supplicant on wakeup from suspend.

All,

Due to a hardware deficiency, whenever I wake up my device from
suspend, my wifi connection status changes to 'disconnected'.  My team
and I have ported several other platforms before to this device and,
for each one, we had to unload my device driver and restart any
services that were associated with it before the connection could be
established.  On our previous iterations, we used apm for power
management which made running a simple script on resume trivially
simple.  With Android, however, it seems that there isn't a reasonable
way to shoe-horn this process in.

My first attempt was to create a broadcast receiver which consumed the
'ACTION_SCREEN_ON' intent and run setWifiEnabled(false); setWifiEnabled
(true); when the intent was seen.  Since these calls don't seem to be
synchronous, I added a 'while(wifiManager.isWifiEnabled())
{Thread.sleep(1000);}' to wait for the first action to run.  (Yes, I
know this is a hack).  This actually WORKED for a hardware suspend
(when I hit the power button on my device) but NOT for a screen
timeout.

After this setback, I started tracing back through the networking code
and found the WifiService.java that seemed to already be consuming the
ACTION_SCREEN_ON intent and doing stuff (albeit apparently
asynchronously with messages).  I have tried several different ways to
get my down / up mechanism to work (in the updateWifiState() and
setWifiEnabledBlocking() methods) but to no avail.  This whole
mechanism seems so interdependent upon itself that adding special
blocks to bring down the driver and supplicant only appear to add
instability and break things.

Can someone who is familiar with this whole mechanism let me know if
I'm even LOOKING IN THE RIGHT PLACE or not?  Ideally, since the
WifiService.java turns on the whole shebang from the persisted state,
I should be able to add some sort of call during the resume to just
unload the driver and stop the supplicant so that everything starts in
a reasonable state.  (maybe in the init.<device>.rc?)

Thanks,
Ben Friedberg

--~--~---------~--~----~------------~-------~--~----~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: 

3. Graceful handling of SD card removal while application writing to file...

4. Full Screen in sub-Preference Screen

5. Force screen orientation and avoid destroy call

6. playing sound on active call

7. Custom list adapter using SQL and line-specific icons