(inspired by this blog post)

1) Install smalidea plugin

Download the smalidea plugin (see also the related Github Repository).

Open up Android Studio and you should see the welcome screen like the one on screenshot below (if not, close your current project by selecting File -> Close project), go to the Plugins section, and from the wheel icon, select Install Plugin from Disk.... Select the smalidea plugin (ZIP file) you downloaded.

2) Get the third party APK

You first need to know the type of platform where you’ll do your debug tests. To do so, make sure your device is connected to your computer (it could also be a virtual device started from the AVD Manager) with adb devices.
Then, use the command adb shell getprop ro.product.cpu.abi to find the type of processor you have. When I use my phone, I got arm64-v8a.

Go to an APK platform, like https://apkcombo.com/ and search for the Android app you want to debug. Download the APK version that fits to the type you found before:

2bis) Have a look at the APK content

You can use JADX to open the APK and have a quick look at the code.

3) Decompile APK

With APKTool, we’ll use the command: .\apktool.bat d ".\the_original_app_from_apkcombo.com.apk" -o app_to_debug.
A folder called app_to_debug is created with the decompiled version of the application.

Next, we need to copy the source files: create a folder called « src » in the new app_to_debug folder, and type cp -R smali*/* src/.

4) Import project in Android Studio

Open an existing Android Studio project and select the app_to_debug folder where you unpacked APK.

Once the project loads, you need to tell the IDE where is your source code. Make sure you’re using the « Project view » in the left side panel:

Now you can see folder structure in your left panel. Find src/ subfolder right click it and select Mark Directory as -> Sources Root.

5) Prepare App for Debugging

Open AndroidManifest.xml from the app_to_debug and find the XML element <application>. Add the attribute android:debuggable with value « true ». Example:

<application android:debuggable="true" android:allowBackup="true" android:icon="@mipmap/ic_launcher" android:label="@string/app_name" android:largeHeap="true" android:name="org.horaapps.leafpic.App" android:theme="@style/Theme.AppCompat">

6) Repack to APK

You can now repack to APK with the command .\apktool.bat b -d ".\app_to_debug\" -o app_unsigned.apk

7) Sign the APK

7a) Create a keystore

You first need a keystore using keytool and type the below command:
keytool -genkeypair -v -keystore mykey.keystore -alias mykey -keyalg RSA -keysize 2048 -validity 10000

Several questions you’ll be asked, as well as a password. Make sure to remember the password for later.

7b) Validate the APK

You then need zipalign that can be found in the Android SDK folder (e.g. C:\Users\USERNAME\AppData\Local\Android\Sdk\build-tools\31.0.0\zipalign.exe) to validate your APK:
.\Path\to\Android\Sdk\build-tools\31.0.0\zipalign.exe -f -v 4 .\app_unsigned.apk .\app_ready.apk

7c) Sign the APK

Finally you can sign the new created APK with apksigner:
.\Path\to\Android\Sdk\build-tools\31.0.0\apksigner.bat sign --ks .\mykey.keystore --ks-key-alias app_to_debug --out .\app_signed.apk .\app_ready.apk

8) Install the APK

You can install it using adb install app_signed.apk

9) Prepare the host

On your Android device, go to Settings -> Developer options and set USB debugging and Wait for debugger options on. The latter is optional but useful as it allows you wait for debugger connection and not to run app yet.

Finally, you should tap on Select debug app and choose the app you just installed. After all of these, your Developer options menu should look somewhat like this:

Now, launch the app on the Android device, and you’ll get the below message:

10) Forward debugger port

You can use the adb’s port forwarding feature and forward JDWP service where application’s debug interface is listening.

Find the JDWP port with the command adb jdwp, then use this port with the command:
adb forward tcp:5005 jdwp:JDWP_PORT

11) Connect Debugger

Go to Android Studio and from its top menu bar choose Run -> Debug…, then a small message appears with one unique option that is Edit Configurations.... There, in the window, use a plus (+) button at the opt left, and add a new configuration of type Remote. Leave the default configuration as is. Click the Debug button and your app should be running with the attached debugger which means it will stop once a breakpoint is hit and you can investigate the content of app’s variables.

I’m using CapacitorJS for easy development with Android. I needed a way to do an HTTPS request to a box that uses self-signed SSL certificate. To accomplish it, I created my own capacitor plugin.

See this wiki page for details: https://github.com/Aymkdn/assistant-freebox-cloud/wiki/Capacitor-Plugin-for-HTTP-requests-with-self-signed-SSL-certificates

« Erreur du système, les notifications sont indisponibles. Veuillez redémarrer votre téléphone. Si le problème persiste, contactez le fabricant de votre appareil. »

J’ai eu cette erreur sur mon Samsung S20 FE. J’ai réussi à m’en sortir ou désinstallant tout puis en réinstallant… Mais je pense que la solution pouvait être autre : dans les Paramètres du téléphone, chercher Accès aux notifications, puis vérifier que l’application « Santé » est bien cochée !

I wanted to debug an Android app that uses HTTPS requests with a JSON API. Thanks to this article I’ve been able to use my Windows 10 computer to get all the network from my Android phone thru my local network and decode the HTTPS requests !

I’m going to summarize the steps from the above article:

1. Download and Install Fiddler on your computer
2. Once Fiddler is installed, launch it and:
   • Click menu Tools > Options, then select the Connections tab
   • Make note of the “Fiddler listens on” port (normally it’s 8888)
   • Make sure the check box for “Allow remote computer to connect” is checked
   • Switch to the HTTPS tab
   • Make sure the check boxes for “Capture HTTPS Connects” and “Decrypt HTTPS traffic” are both checked
   • Restart Fiddler
3. Go to your Android phone then:
   • Tap on Settings, then Wi-Fi
   • Find the network on which you’re connected (normally the first one listed), then tap and hold
   • Choose Modify network from the pop-up
   • Scroll down and enable “Show advanced options”
   • Change “Proxy settings” to Manual
   • Under “Proxy host name” enter the Windows PC IP address from above
   • Under “Proxy port” enter the Fiddler port from above (usually 8888)
   • Tap Save and wait a moment for the network to reconnect
4. Now we need to add the certificate in Android to have the HTTPS working:
   • On Android start the Chrome browser
   • Navigate to http://IP_ADDRESS_WHERE_FIDDLER_IS:8888/ or http://ipv4.fiddler:8888
   • Tap on the link for the “Fiddler Root Certificate”
   • Name the certificate “Fiddler” and install it (entering your PIN or password if prompted)

You’re now ready to capture the traffic on Fiddler!

Once you’re done you can switch back to normal by following the below steps:

1. Tap on Settings, then Wi-Fi
2. Find the network on which you’re connected (should be the first one listed), then tap and hold
3. Choose Modify network from the pop-up
4. Scroll down and select (enable) “Show advanced options”
5. Change “Proxy settings” to None
6. Tap Save and wait a moment for the network to reconnect
7. Go up a level in settings to Security
8. Tap Trusted credentials, then select the User tab
9. Tap on the Fiddler “Do not trust” certificate, then scroll down to remove it
10. You may need to power cycle your device to get all apps to forget about the Fiddler certificate (e.g., the Chrome browser will continue to try to use it for a while)

I was trying to update my Sony Xperia Z3 Compact from Android 5.0.2 (rooted) to Android 5.1.1, and everything worked well except that I got this issue : mount: Operation not permitted
when I was trying to put in write mode the system folder.

Also I tried SDFix and I got the error « Update failed, platform.xml file could not be updated ».

When I tried « ES Explorer », with Root Mode, I had SuperSU asking for root permission, but then « ES Explorer » said my system is not rooted.

After hours of digging I finally found I had to use that file discovered in that XDA thread. Just download it, unzip, then launch the install.bat

J’ai un Sony Xperia Z3 Compact et, soudainement, le micro s’est arrêté de fonctionner. Je suis passé sous Lollipop il y a quelques jours. Après investigation, cela est peut-être dû à l’utilisation de mon casque pour écouter de la musique… J’ai donc effectué quelques recherches pour trouver un correctif, et c’est finalement venu du Issue Tracker d’Android. Voici la marche à suivre :

• Activer le mode Développeur en allant dans Paramètres > A propos du téléphone > puis tapoter plusieurs fois sur Numéro de build jusqu’à ce qu’un message apparaisse disant que le mode développeur est activé
• Ensuite dans Paramètres > Options pour les développeurs > il faut décocher, dans multimédia, l’option qui s’appelle NuPlayer (expérimental)
• Redémarrer le téléphone

Pour moi cette méthode a fonctionné. N’hésitez pas à cliquer sur l’étoile sur le Tracker d’Android concernant ce problème afin que Google s’occupe de publier un correctif.

La dernière version d’Android est disponible pour le Xperia Z1 Compact, et on trouve tous les tutoriaux nécessaires sur http://www.phonandroid.com :

1. D’abord il faut télécharger la ROM
2. Ensuite on l’installe
3. Puis on peut rooter son téléphone
4. Et enfin on peut installer un recovery

I’ve had a recent issue with my Android 4.4 phone causing a constant network activity and draining my battery like crazy. After searching over Internet I found that could be due to one of my devices on my local network (because of a packet broadcast). I disconnected everything, but no luck. Then I installed an app from the store to find which apps are using my battery, but it states it was Android System…

Some forum posts said that could be some ICMP traffic due to the phone trying to reach the Google servers, or something similar.

Finally I installed several applications to monitor my phone. The best one was « Network Log » that is able to show the trafic received/sent for each application. I found that one of my app might be the issue: I uninstalled it and the trafic stopped!

So I recommend this app to find out which app could be the reason of the bad network activity.

EDIT : SFR a fermé le service le 2 janvier 2017 (annonce sur le forum SFR)

Il est possible d’activer le SIP chez SFR. Pour ce faire, il faut se rendre sur son compte SFR et dans les jours qui suivent vous recevrez votre mot de passe par courrier.

Une fois le courrier reçu il s’agit de configurer correctement l’application SIP. Ici nous utiliserons l’application media5fone qui est disponible sur iOS et Android.

Point de vue configuration voici les éléments qu’il vous faut.

Tout d’abord, sur l’écran d’accueil, vous devez choisir « Paramètres SIP personnalisés > Définir manuellement ».
Dans « Titre » vous pouvez entrer « SFR LIBERTALK ».
Dans « Nom d’utilisateur » entrez +3399{Votre numéro de ligne sur 10 caractères} (Exemple: +33990123456789)
Dans « Mot de passe », celui qui vous a été envoyé par courrier.
Allez dans « Serveurs » :

• Pour l’adresse SIP entrez l’adresse « ims.mnc010.mcc208.3gppnetwork.org »
• Pour le port il faut mettre 5064
• Concernant le « serveur proxy sortant », vous devez l’activer (« Activer Proxy »).
• Dans l’adresse du proxy entrez « internet.p-cscf.sfr.net »
• Dans le port du proxy il faut mettre 5064
• Activez l’option « Retirer header Route »
• Maintenant dans la section « Autre » modifiez « Interval d’enregistrement (sec) » avec la valeur 3600
• Activez aussi « Utiliser rport » dans cette même section

Une fois validé, il va essayer de se connecter et ne va pas réussir, il faut aller dans l’option « Avancé » du compte pour y arriver.
Dans « Avancé » :

• Configurer le « compte utilisateur », avec « ID Appelant » qui est « {Votre numéro de ligne sur 10 caractères} » (exemple: 0123456789)
• Le « Nom d’authentification » est « NDI{votre numéro de ligne sur 10 caractères}.LIBERTALK@sfr.fr » (exemple: NDI0123456789.LIBERTALK@sfr.fr)
• Descendez plus bas jusqu’à la section « SIP Features » et changez « Méthode de transfert » en « BYE »

Et voilà, après avoir validé, et en étant connecté sur du WiFi, vous devriez pouvoir passer tous les appels que vous souhaitez !

Plus d’infos dans l’assistance de SFR et sur le forum de SFR

This is for the Alpha5 of CM9 available on XDA. The ROM is available on GitHub: https://github.com/DerArtem/android_device_toshiba_betelgeuse/downloads (called « update-cm-9.0.0-RC0-2012.04.21-betelgeuse-UNOFFICIAL-signed.zip » here).
Download it from the link above.

I have currently the FolioMod’s Dexter and Windows 7 (64 bits)

Install Android SDK

Go to the Android SDK page and install the package. Make sure you install the Google USB Drivers also after the installation is complete.

Here I have installed the SDK into D:\ANDROID\android-sdk

Once it’s done you want to test if your device is recognized by your computer. Switch it on and plug in it. Then open a Windows console (Windows key + R, then type « cmd ») and go to your installation directory. Then go to the « platform-tools » directory. It will be something like that: > cd D:\ANDROID\android-sdk\platform-tools
You should see the « adb.exe » file. You can call it with the command adb.exe devices

If it returns the message « < Waiting for devices > », then it means you need to do some tricks :

• On your Folio, go to the Settings > Applications > USB Debug : make sure this is checked
• On your computer, find the file called android_winusb.inf (in my case it’s located here: D:\ANDROID\android-sdk\extras\google\usb_driver), and open it with a text editor. We now need to copy/paste the three lines below at the end of the [Google.NTx86] part and at the end of the [Google.NTamd64] part :
  

  ;NVIDIA Tegra
  %SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
  %CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01

  
  Credits – http://philflash.inway.fr/flex/folio100/usb_tegra2.html

• Save the file and close it. Now type the command echo 0x955 > "%USERPROFILE%\.android\adb_usb.ini" into the console.
• Now unplug/replug your Folio and click right on the Computer icon that you have on your desktop or into the Windows explorer, and choose « Manage ». From there you can manage the devices and under « Other devices » you should see the « NVIDIA Tegra2 » :
  
  Credits – http://philflash.inway.fr/flex/folio100/usb_tegra2.html
• Click right on it and pick « Update the driver » and choose the « Locate it on my computer » option. For the path it will be D:\ANDROID\android-sdk\extras\google\usb_driver in my case
• You’ll probably have a warning message, but say yes, that you want it to be installed
• When it’s done you should now see « Android Composite ADB Interface » instead of « NVIDIA Tegra 2 »
• In the Windows console you can now type the below commands (in the « platform-tools » directory) :
  

  adb kill-server
  adb start-server
  adb devices

• Your Folio must now appear in the list of devices

Bootload

First, rename the ROM downloaded as « update.zip » and copy it to your SDCard (at the root dir). (In the mean time copy also the Google Apps zip file)

We’re going to install the recovery :

• Copy the cwm-recovery-5.5.0.4.img file you’ve downloaded into the « platform-tools » folder.
• Switch off your Folio (keep it plugged to your computer).
• Switch it on, and when it vibrates then press three times the Power button, then the Volume UP button : you’ll see a message saying it’s in fastboot mode.
• In the Windows console type : fastboot.exe flash recovery cwm-recovery-5.5.0.4.img
• The message « flashing mbr to device » will appear.
• Press several seconds the Power button to turn it off, then turn it on. When the first messages appear on the screen press the Power button and the Volume UP button. You’ll see some text.
• Make sure to go to the Update System mode (it should be : Volume UP + Volume Down + Volume Up), and you’ll have the Recovery menu. From here I recommend to do a backup (« backup and restore > backup to internal sdcard ») (the Power button permits to validate the choices, and the Volume to go up and down)

Install the new ROM

After the backup you can do a « wipe data/factory reset ». Then install the ROM in choosing the « Install zip from SDCard » option.

At the end of the process the Folio will say « Install from sdcard complete. »

It’s now time to reboot to use CM9 🙂

Install Google Apps

Reboot your Folio. When it vibrates, press the Power button and the Volume UP in the same time. Then go to the System Update (Volume Up + Down + Up), and install the GAPPS file.