closed Re: need help journey ga mau konek network

by bayu ferdinata » Thu, 13 Jan 2011 17:44:52 GMT


Sponsored Links
 kayanya mang harus bgitu deh bro, krena ga punya stock rom eclair jadi ya
balik lagi ke apanda rom, makasih buat pencerahannya :)


berextensi


network.
works
mau
so
(klo

-- 
===============
"



Re: closed Re: need help journey ga mau konek network

by Indra D. Kusuma » Fri, 14 Jan 2011 08:42:26 GMT


 Sama2 karena ngalamin gitu waktu coba roti jahe dari CM ga dapet sinyal kudu
balik ke original rom baru bisa. :D tp klo dari CM roti jahe ke official
froyo ga masalah. Karena radionya dah ada difile. nb0
On Jan 13, 2011 4:44 PM, "bayu ferdinata" <bayumilis.andr...@gmail.com>



CM
dibenerin,

bayumilis.andr...@gmail.com

tulisan

-- 
===============
"


Sponsored Links


Other Threads

1. Standardizing and promoting open intents (latest android blog post)

Note that there exists already a place for promoting and discussing
intents which is already used by many developers:
http://www.openintents.org/en/intentstable

We would like to help to improve this service in the near future, so
any feedback from developers, users, and from Google's side is very
much appreciated.

We are also discussing this issue in the OI group:

2. Certificate problem with updating even though I still have the same keystore

Hello

I know there have been countless posts about people forgetting their
passwords or losing their keystores, but for me it's different: I
still have the old keystore file and I do have the password. I tried
jarsigner -verify with -storepass and -keystore set for both, my old
signed apk and my new one, and in both cases the jar gets verified.
When I try to upload however, I get the "The apk must be signed with
at least one certificate in common with the previous version."
How can that be? I didn't create a new keystore since...

An odd thing is, that if I enable -certs I get this message:
[certificate is valid from 4/16/09 9:53 AM to 6/5/91 9:53 AM]

1991!! could that be the problem? I did read about the requirements of
expirations and I remember being within that limit. I couldn't even
have uploaded my app had it expired in the past since there's this 30
years something restriction.... how can that happen?

Does anyone have an idea of what else could have gone wrong? Or can
anyone tell me how I can properly compare the certificate between the
2 apks myself.
thanks
yannick

-- 

3. contacts application dependency issues

4. How to integrate 3rd party buildsystem into Android BuidSystem

5. Android 1.6 running on kernel 2.6.28

6. Problems with the new ContactsContract API when picking a contact

7. is Android app qualified for LBS Challenge?