CyanogenMod 9.0.0 Pour le galaxy Ace - RC1 - [14/08/12]

[krys940]

moue , Je ne vois pas quel fichier je dois prendre dans le dossier /system/etc/init.d ...

sololonnais tu pourrais me dire quel fichier je doit prendre stp ? ou faire un zip flashable ?

merci

Modifié 19 juin 2012 par krys940

[h@t]

Sur Cyano en général y'a pas de synchro :/

La seule Cyano qui, à ma connaissance arrive à syncroniser les contacts avec Facebook, c'est la Xperia Tized...

Miracle v4 le fait, je te rassure ^^

Bon moi je vous dis, release dans deux semaines.

[NeG]

Fais un full wype, flash la dernière nightly, une fois que c'est fait et que ça a boot :

Reboot en recovery, wype data/factory reset, wype cache

Advanced ==> wype Dalvik

Ensuite reboot, et mets en Smartass v2 245 - 800 pas besoin de script ou quoi que ce soit de (souvent) placébo.

Et pas de lag de wake up dans ce cas ;)

[marshallbob]

et la XperiaTized est basé sur ... le stock a ma connaissance

[LoïcLeDuault]

Sur Cyano en général y'a pas de synchro :/

La seule Cyano qui, à ma connaissance arrive à syncroniser les contacts avec Facebook, c'est la Xperia Tized...

tu est sur de sa? sur ma rom sa le fait des que l'on install FB on choisit ce qu'on veut sincro

et pourtant j'ai rien modifier a ce niveau je suis parti des sources officiel de CM

[Ugoboss]

La seule Cyano qui, à ma connaissance arrive à syncroniser les contacts avec Facebook, c'est la Xperia Tized...

et la XperiaTized est basé sur ... le stock a ma connaissance

C'est sur même ! la Rom Xperia Tized est basée sur Android 2.3.6 donc ça ne peut pas être du CynoagenMod 7, suffit de faire un petit tour dans son build prop ;)

Modifié 20 juin 2012 par UgoBoss

[h@t]

J'aime le nouveau Galaxyics.com

[krys940]

Salut , NeG j'ai fait comme tu as dit mais finalement le problème vient bien de Deep Sleep. Il ne s'active jamais en faite xD

Y'a une solution à ce problème ? ça sera corriger dans la béta 9 vous croyez ?

( Ils mettent dans la liste des chose qui marche Deep Sleep, donc ils mettent des choses qui ne marche qu'a moitié ... )

Modifié 20 juin 2012 par krys940

[NeG]

Chez moi ça marche très bien, et oui ça vient du Deep Sleep...

Essaye de régulièrement fermer les applications avant de verrouiller ton tel, soit tu vas dans les paramètres et tu choisis une option pour tuer toutes les applis dont tu n'es pas en train de te servir (Je ne sais plus ou ça ce trouve)

Ou bien, avant de lock, restes appuyé sur Home, et fermes toutes les applications en tâches de fond en les faisant glisser à gauche ou à droite.

Ce multi-tâches est assez étrange, c'est pas forcément uniquement des applis ouvertes, mais des petits raccourcis d'endroits où tu t'es rendu. En revanche pour les applis comme le navigateur qui se trouvent dans le multi-tâches, ce sont des applis qui sont "réellement" en tâche de fond (Conso de RAM)

Donc fermes les, et en général ça devrait bien marcher.

Oublies pas que Smartass v2 245 - 800 est très efficace, je le trouves bien plus efficace que le conservative... Je vois pas trop à quoi il sert, hormis ralentir le tel ^^'

[LoïcLeDuault]

ya des reglage aussi pour ne pas faire de multitache enfin pour choisir le nombre de tache a la fois

1 2 3 ou 4 si je me souvient bien

[marshallbob]

Au pire, je vais bientôt release la nouvelle version de S3nsation by team ICAce (oui, enfait, j'aime pas faire le travail seul, puis tout vos conseils, que j'ai pu appliqué sur mon travail, n'aurait pu arriver sans vos propositions =) )

Niveau batterie, je suis à 61% pour 15h d'utilisation (enfin ... quelques sms, internet, et musique a wak !)

[krys940]

Je me suis mis en smartass v2 quand j'ai reflasher ma rom hier ;)

J'ai un task killer au cas ou ( mais il ne me sert jamais ) et quand je met la limite de processus en arrière plan à 2 il se remet tout seul en "limite standard" oO

[LoïcLeDuault]

krys ta une poubelle pas loin??

[marshallbob]

Moi je vous le dit : Prochaine release de la CM9 c'est pas encore ... autant, je pensais que maclaw s'etait enfin reveillé, et s'etait enfin magner l'arriere train, mais là je pense qu'il a besoin de quelques coup de pieds au *** pour se remettre au boulot !

[krys940]

mdr je pense que je vais passer au S2 ;)

[LoïcLeDuault]

surtou des € qu'il a besoin lol cette team est celle qui a le plus demander de donation de toute l'histoire de la donation lol

[h@t]

En tout cas, j'aimerais pas qu'ils développent des roms pour S3 :S

Modifié 20 juin 2012 par H@st

[marshallbob]

Je préfere faire confiance aux chinois Doixan (créateur de plein de rom sur le X8 dont GingerDX (enfin) porté sur le Ace)

[LoïcLeDuault]

c claire que personne est au niveau des dev chinoi

[NeG]

Les task killer c'est bon à te bougfer la batterie ça...

Ca ferme les applis systèmes qui ne consomment pas de batterie, sauf que beaucoup d'entre elles se réouvrent toutes seule, et pendant cette réouverture elles consomment de la batterie...

En bref vaut mieux éviter ça ;)

[guillane]

oui les devs chinois sont extraordinaire c'est clair... ils innovent vraiment eux! tain vous avez vu leurs systeme UI sur les ROMs du topic rom chinoise? c'est wow ! ils ont été les premier (et les dernier) a utiliser le swap! les dev xda ne font rien de space quelque script quelques icones et c'est tout. pfff c'est a la porté de tout le monde lol sauf pour CM9 ou j'avou j'ai du respect...

une question me brule les lèvres... comment creer un nouvel android? enfin un nouveau system d'exploitation? d'ou sortent-ils les sources? comment les créent-ils ces sources?

regardez:

* # * # 8255 # * # * -> Google Talk Service Monitor (Talk.apk)

* # * # 4636 # * # * -> Test / Debug info (Settings.apk)

* # * # 9696 # * # * -> FTP Test / App (Ftp.apk)

* # * # 8351 # * # * -> * # * # VDL1 # * # * Voice Dialer Logging Enabled (VoiceDialer.apk)

* # * # 8350 # * # * -> * # * # * # # VDL0 Voice Dialer * Logging Disabled (VoiceDialer.apk)

* # * # 7269 # * # * - l'exploitation forestière> Appareil de base (HtcLog.apk) (périphériques, les commandes AT, le noyau [dmesg?], Et le journal facultatif se rapportant à la mémoire flash [logcat?])

* # * # 564 # * # * -> QXDM Logging avant la fin (QxdmLog.apk)

quelques codes secret ^^

j'ai trouvé ma reponse tout seul ^^ pour creer un system UI en tout cas :) je vais m'y mettre:

Hello, World

In this document

• Install a Platform
  
• Create an AVD
  
• Create the Project
  
• Construct the UI
  
• Run the Code
  
• Upgrade the UI to an XML Layout
  
• Debug Your Project
  
• Creating the Project Without Eclipse
  

As a developer, you know that the first impression of a development framework is how easy it is to write "Hello, World." Well, on Android, it's pretty easy. It's particularly easy if you're using Eclipse as your IDE, because we've provided a great plugin that handles your project creation and management to greatly speed up your development cycles.

This tutorial assumes that you're using Eclipse. If you're using the command line, see Building and Running from the Command Line. You can then return to this tutorial and ignore anything about Eclipse.

Before you start, you should already have the SDK installed, and if you're using Eclipse, you should have installed the ADT plugin as well. If you have not installed these, see Installing the Android SDK and return here when you've completed the installation.

Install a Platform

To run the Hello World application, you need to install at least one Android platform in your SDK environment. If you have not already performed this step, you need to do it now.

To install a platform in Eclipse:

• In the Android SDK Manager, choose Available Packages in the left panel.
  
• In the right panel, expand the Android Repository list to display the components available for installation.
  
• Select at least one platform to install, and click Install Selected. If you aren't sure which platform to install, use the latest version.
  

Create an AVD

To learn more about how to use AVDs and the options available to you, see Managing Virtual Devices.

In this tutorial, you will run your application in the Android Emulator. Before you can launch the emulator, you must create an Android Virtual Device (AVD). An AVD defines the system image and device settings used by the emulator.

To create an AVD:

• In Eclipse, select Window > AVD Manager.
  
• Select Virtual Devices in the left panel.
  
• Click New....
  The Create New AVD dialog appears.
  
• Type the name of the AVD, such as "my_avd".
  
• Choose a target.
  The target is the platform (that is, the version of the Android SDK, such as 2.3.3) you want to run on the emulator. For this tutorial, choose the latest platform that you have installed and ignore the rest of the fields.
  
• Click Create AVD.
  

Create a New Android Project

After you've created an AVD you can move to the next step and start a new Android project in Eclipse.

• In Eclipse, select File > New > Project....
  If the ADT Plugin for Eclipse has been successfully installed, the resulting dialog should have a folder labeled "Android" which should contain "Android Project". (After you create one or more Android projects, an entry for "Android XML File" will also be available.)
  
• Select "Android Project" and click Next.
  
  
• Fill in the project details with the following values:
  
  • Project name: HelloAndroid
    
  • Build Target: Select a platform version that is equal to or lower than the target you chose for your AVD.
    
  • Application name: Hello, Android
    
  • Package name: com.example.helloandroid (or your own private namespace)
    
  • Create Activity: HelloAndroid
    

  Click Finish.

  Here is a description of each field: Project Name This is the Eclipse project name — the name of the directory that contains the project files. Build Target This is the version of the Android SDK that you're using to build your application. For example, if you choose Android 2.1, your application will be compiled against the Android 2.1 platform library. The target you choose here does not have to match the target you chose for your AVD; however, the target must be equal to or lower than the target you chose for your AVD. Android applications are forward-compatible, which means an application will run on the platform against which it is built as well as all platforms that are released in the future. For example, an application that is built against the 2.1 platform library will run normally on an AVD or device that is running the 2.3.3. The reverse is not true. Application Name This is the human-readable title for your application — the name that appears on the Android device. Package Name This is the package namespace (following the same rules as for packages in the Java programming language) that you want all your source code to reside under. This also sets the package name under which the stub Activity is generated.

  Your package name must be unique across all packages installed on the Android system; for this reason, it's important to use a standard domain-style package for your applications. The example above uses the "com.example" namespace, which is a namespace reserved for example documentation — when you develop your own applications, you should use a namespace that's appropriate to your organization or entity. Create Activity This is the name for the class stub that is generated by the plugin. This is a subclass of Android's Activity class. An Activity is simply a class that can run and do work. It can create a UI if it chooses, but it doesn't need to. As the checkbox suggests, this is optional, but an Activity is almost always used as the basis for an application. Min SDK Version This value specifies the minimum API Level on which your application will run. The Min SDK Version should be the same as the Build Target you chose. For example, if the Build Target is Android 2.1, then the Min SDK Versionshould be 7 or lower (it can never be higher than 7). For more information, see Android API Levels.

  Other fields: The checkbox for "Use default location" allows you to change the location on disk where the project's files are generated and stored.

Your Android project is now ready. It should be visible in the Package Explorer on the left. Open the HelloAndroid.javafile, located inside HelloAndroid > src > com.example.helloandroid). It should look like this:

package com.example.helloandroid;

import android.app.Activity;

import android.os.Bundle;

public class HelloAndroid extends Activity {

/** Called when the activity is first created. */

@Override

public void onCreate(Bundle savedInstanceState) {

super.onCreate(savedInstanceState);

setContentView(R.layout.main);

}

}

Notice that the class is based on the Activity class. An Activity is a single application entity that is used to perform actions. An application may have many separate activities, but the user interacts with them one at a time. The onCreate()method is called by the Android system when your Activity starts — it is where you should perform all initialization and UI setup. An activity is not required to have a user interface, but usually does.

Now let's modify some code!

Construct the UI

Take a look at the revised code below and then make the same changes to your HelloAndroid class. The bold items are lines that have been added.

package com.example.helloandroid;

import android.app.Activity;

import android.os.Bundle;

import android.widget.TextView;

public class HelloAndroid extends Activity {

/** Called when the activity is first created. */

@Override

public void onCreate(Bundle savedInstanceState) {

super.onCreate(savedInstanceState);

TextView tv = new TextView(this);

tv.setText("Hello, Android");

setContentView(tv);

}

}

Tip: An easy way to add import packages to your project is to press Ctrl-Shift-O (Cmd-Shift-O, on Mac). This is an Eclipse shortcut that identifies missing packages based on your code and adds them for you. You may have to expand the import statements in your code for this to work.

An Android user interface is composed of hierarchies of objects called Views. A View is a drawable object used as an element in your UI layout, such as a button, image, or (in this case) a text label. Each of these objects is a subclass of the View class and the subclass that handles text is TextView.

In this change, you create a TextView with the class constructor, which accepts an Android Context instance as its parameter. A Context is a handle to the system; it provides services like resolving resources, obtaining access to databases and preferences, and so on. The Activity class inherits from Context, and because your HelloAndroid class is a subclass of Activity, it is also a Context. So, you can pass this as your Context reference to the TextView.

Next, you define the text content with setText().

Finally, you pass the TextView to setContentView() in order to display it as the content for the Activity UI. If your Activity doesn't call this method, then no UI is present and the system will display a blank screen.

There it is — "Hello, World" in Android! The next step, of course, is to see it running.

Run the Application

The Eclipse plugin makes it easy to run your applications:

• Select Run > Run.
  
• Select "Android Application".
  

To learn more about creating and editing run configurations in Eclipse, refer to Developing In Eclipse, with ADT.

The Eclipse plugin automatically creates a new run configuration for your project and then launches the Android Emulator. Depending on your environment, the Android emulator might take several minutes to boot fully, so please be patient. When the emulator is booted, the Eclipse plugin installs your application and launches the default Activity. You should now see something like this:

The "Hello, Android" you see in the grey bar is actually the application title. The Eclipse plugin creates this automatically (the string is defined in the res/values/strings.xml file and referenced by your AndroidManifest.xml file). The text below the title is the actual text that you have created in the TextView object.

That concludes the basic "Hello World" tutorial, but you should continue reading for some more valuable information about developing Android applications.

Upgrade the UI to an XML Layout

The "Hello, World" example you just completed uses what is called a "programmatic" UI layout. This means that you constructed and built your application's UI directly in source code. If you've done much UI programming, you're probably familiar with how brittle that approach can sometimes be: small changes in layout can result in big source-code headaches. It's also easy to forget to properly connect Views together, which can result in errors in your layout and wasted time debugging your code.

That's why Android provides an alternate UI construction model: XML-based layout files. The easiest way to explain this concept is to show an example. Here's an XML layout file that is identical in behavior to the programmatically-constructed example:

<?xml version="1.0" encoding="utf-8"?>

<TextView xmlns:android="http://schemas.android.com/apk/res/android"

android:id="@+id/textview"

android:layout_width="fill_parent"

android:layout_height="fill_parent"

android:text="@string/hello"/>

The general structure of an Android XML layout file is simple: it's a tree of XML elements, wherein each node is the name of a View class (this example, however, is just one View element). You can use the name of any class that extends View as an element in your XML layouts, including custom View classes you define in your own code. This structure makes it easy to quickly build up UIs, using a more simple structure and syntax than you would use in a programmatic layout. This model is inspired by the web development model, wherein you can separate the presentation of your application (its UI) from the application logic used to fetch and fill in data.

In the above XML example, there's just one View element: the TextView, which has five XML attributes. Here's a summary of what they mean: Attribute Meaning xmlns:android This is an XML namespace declaration that tells the Android tools that you are going to refer to common attributes defined in the Android namespace. The outermost tag in every Android layout file must have this attribute. android:id This attribute assigns a unique identifier to the TextView element. You can use the assigned ID to reference this View from your source code or from other XML resource declarations. android:layout_width This attribute defines how much of the available width on the screen this View should consume. In this case, it's the only View so you want it to take up the entire screen, which is what a value of "fill_parent" means. android:layout_height This is just like android:layout_width, except that it refers to available screen height. android:text This sets the text that the TextView should display. In this example, you use a string resource instead of a hard-coded string value. The hello string is defined in theres/values/strings.xml file. This is the recommended practice for inserting strings to your application, because it makes the localization of your application to other languages graceful, without need to hard-code changes to the layout file. For more information, see Resources and Internationalization.

These XML layout files belong in the res/layout/ directory of your project. The "res" is short for "resources" and the directory contains all the non-code assets that your application requires. In addition to layout files, resources also include assets such as images, sounds, and localized strings.

Landscape layout

When you want a different design for landscape, put your layout XML file inside /res/layout-land. Android will automatically look here when the layout changes. Without this special landscape layout defined, Android will stretch the default layout.

The Eclipse plugin automatically creates one of these layout files for you: main.xml. In the "Hello World" application you just completed, this file was ignored and you created a layout programmatically. This was meant to teach you more about the Android framework, but you should almost always define your layout in an XML file instead of in your code. The following procedures will instruct you how to change your existing application to use an XML layout.

• In the Eclipse Package Explorer, expand the/res/layout/ folder and open main.xml (once opened, you might need to click the "main.xml" tab at the bottom of the window to see the XML source). Replace the contents with the following XML:
  <?xml version="1.0" encoding="utf-8"?>
  <TextView xmlns:android="http://schemas.android.com/apk/res/android"
  android:id="@+id/textview"
  android:layout_width="fill_parent"
  android:layout_height="fill_parent"
  android:text="@string/hello"/>
  Save the file.
  
• Inside the res/values/ folder, open strings.xml. This is where you should save all default text strings for your user interface. If you're using Eclipse, then ADT will have started you with two strings, hello and app_name. Revise hello to something else. Perhaps "Hello, Android! I am a string resource!" The entire file should now look like this:
  <?xml version="1.0" encoding="utf-8"?>
  <resources>
  <string name="hello">Hello, Android! I am a string resource!</string>
  <string name="app_name">Hello, Android</string>
  </resources>
  
• Now open and modify your HelloAndroid class and use the XML layout. Edit the file to look like this:
  package com.example.helloandroid;
  import android.app.Activity;
  import android.os.Bundle;
  public class HelloAndroid extends Activity {
  /** Called when the activity is first created. */
  @Override
  public void onCreate(Bundle savedInstanceState) {
  super.onCreate(savedInstanceState);
  setContentView(R.layout.main);
  }
  }
  When you make this change, type it by hand to try the code-completion feature. As you begin typing "R.layout.main" the plugin will offer you suggestions. You'll find that it helps in a lot of situations.
  Instead of passing setContentView() a View object, you give it a reference to the layout resource. The resource is identified as R.layout.main, which is actually a compiled object representation of the layout defined in/res/layout/main.xml. The Eclipse plugin automatically creates this reference for you inside the project's R.java class. If you're not using Eclipse, then the R.java class will be generated for you when you run Ant to build the application. (More about the R class in a moment.)
  

Now re-run your application — because you've created a launch configuration, all you need to do is click the green arrow icon to run, or select Run > Run History > Android Activity. Other than the change to the TextView string, the application looks the same. After all, the point was to show that the two different layout approaches produce identical results.

Note: You may have to unlock the screen on the emulator to see your application — just as you would unlock the screen on a device. If you have problems running the emulator, see Using the Android Emulator.

Continue reading for an introduction to debugging and a little more information on using other IDEs. When you're ready to learn more, read Application Fundamentals for an introduction to all the elements that make Android applications work. Also refer to the Developer's Guide introduction page for an overview of the Dev Guide documentation.

R class

In Eclipse, open the file named R.java (in the gen/ [Generated Java Files] folder). It should look something like this:

package com.example.helloandroid;

public final class R {

public static final class attr {

}

public static final class drawable {

public static final int icon=0x7f020000;

}

public static final class id {

public static final int textview=0x7f050000;

}

public static final class layout {

public static final int main=0x7f030000;

}

public static final class string {

public static final int app_name=0x7f040001;

public static final int hello=0x7f040000;

}

}

A project's R.java file is an index into all the resources defined in the file. You use this class in your source code as a sort of short-hand way to refer to resources you've included in your project. This is particularly powerful with the code-completion features of IDEs like Eclipse because it lets you quickly and interactively locate the specific reference you're looking for.

It's possible yours looks slightly different than this (perhaps the hexadecimal values are different). For now, notice the inner class named "layout", and its member field "main". The Eclipse plugin noticed the XML layout file named main.xml and generated a class for it here. As you add other resources to your project (such as strings in theres/values/string.xml file or drawables inside the res/drawable/ directory) you'll see R.java change to keep up.

When not using Eclipse, this class file will be generated for you at build time (with the Ant tool).

You should never edit this file by hand.

Debug Your Project

The Android Plugin for Eclipse also has excellent integration with the Eclipse debugger. To demonstrate this, introduce a bug into your code. Change your HelloAndroid source code to look like this:

package com.example.helloandroid;

import android.app.Activity;

import android.os.Bundle;

public class HelloAndroid extends Activity {

/** Called when the activity is first created. */

@Override

public void onCreate(Bundle savedInstanceState) {

super.onCreate(savedInstanceState);

Object o = null;

o.toString();

setContentView(R.layout.main);

}

}

This change simply introduces a NullPointerException into your code. If you run your application again, you'll eventually see this:

Press "Force Quit" to terminate the application and close the emulator window.

To find out more about the error, set a breakpoint in your source code on the line Object o = null; (double-click on the marker bar next to the source code line). Then select Run > Debug History > Hello, Android from the menu to enter debug mode. Your app will restart in the emulator, but this time it will suspend when it reaches the breakpoint you set. You can then step through the code in Eclipse's Debug Perspective, just as you would for any other application.

Creating the Project without Eclipse

If you don't use Eclipse (such as if you prefer another IDE, or simply use text editors and command line tools) then the Eclipse plugin can't help you. Don't worry though — you don't lose any functionality just because you don't use Eclipse.

The Android Plugin for Eclipse is really just a wrapper around a set of tools included with the Android SDK. (These tools, like the emulator, aapt, adb, ddms, and others are documented elsewhere.) Thus, it's possible to wrap those tools with another tool, such as an 'ant' build file.

The Android SDK includes a tool named "android" that can be used to create all the source code and directory stubs for your project, as well as an ant-compatible build.xml file. This allows you to build your project from the command line, or integrate it with the IDE of your choice.

For example, to create a HelloAndroid project similar to the one created in Eclipse, use this command:

android create project \

--package com.example.helloandroid \

--activity HelloAndroid \

--target 2 \

--path <path-to-your-project>/HelloAndroid

This creates the required folders and files for the project at the location defined by the path.

For more information on how to use the SDK tools to create and build projects, please read Developing in Other IDEs.

j suis choquer par cette découverte ^^ je m'y met now!!! j'espere que sa pourra te servir sweetpurple :) pour modifier ta ROM

bon je pense qu'il doit y avoir des gens que sa interesse donc je vous donne un lien utile je pense: http://www.google.fr/url?sa=t&rct=j&q=android%20developpers&source=web&cd=1&ved=0CG0QFjAA&url=http%3A%2F%2Fdeveloper.android.com%2F&ei=cirjT7aAHeek0AX0ueivAw&usg=AFQjCNEdmRjrTtsLKW_llg9S_nJjwX4lnw

[LoïcLeDuault]

sa c'est pour la création d'application pour android fau dl les sources les modifier et les compiller

regarde mon tuto https://forum.frandroid.com/topic/96730-tutocompiller-cm7-cm9-android-a-partir-des-sources-sur-ubuntu/page__st__20

[guillane]

tiens regarde ici: http://www.google.fr/url?sa=t&rct=j&q=comment%20construire%20un%20os%20android&source=web&cd=10&ved=0CGsQFjAJ&url=http%3A%2F%2Fthibault-koprowski.fr%2Ftutoriel-android%2Ftutoriels-android%2F&ei=kzTjT8LeOcjB0gWch5S0Aw&usg=AFQjCNEXGdcbCufVPKrtiLFF0tNkAAPKGw

[Asty38]

La bêta 9 ne sera pas pour tout de suite.

Maclaw annonce que Qualcom ne donnera pas les drivers pour l'apercu des photos et la vidéo :

Ok, we’ve reply from Qualcomm:

Unfortunately we are not able to support video codecs for ARMv6 OMX IL libs for Qualcomm’s QDSP5 on MSM7x27. The architecture of MSM7x27 cannot support OpenMax video codecs for ARMv6 OMX IL on QDSP5 running on Android Ice Cream Sandwich (ICS).

I don’t know how much true in that, but we couldn’t count on something from Qualcomm.

But don’t worry, I’ll invent something

Cheers

PS. Don’t sign petition anymore.

Donc ce ne sera pas pour tout de suite.

[marshallbob]

Ca ne vous paraît pas bizarre ?! Maclaw a certifié que l'apperçu marchait maintenant et qu'il l'intègrera directement dans la B9 ...

Et maintenant il dit que Qualcomm ne veux pas lâcher le truc pour l'apperçu ?! Je dois me planter quelques part, mais si il a déja réparé l'apperçu, pourquoi doit-il demander un codec a qualcomm ?