i have an Archos 50 Helium Plus phone, this phone uses a MT6735P MTK chipset, Archos didn't release the source code of the phone kernel, however, i found a Lenovo phone, the Lenovo Vibe C2, that uses the exact same MTK chipset MT6735P as my archos phone and the source of the kernel of this phone is publicly available containing the vendor and device trees and the kernel source
I wonder if using this source could work for my phone, since the two phones have the exact same hardware chipset
i'd like, with it to build TWRP recovery and Cyanogenmod for this phone
I'd recommend you to ask Archos directly for the source code for your phone model (https://www.archos.com/fr/support/support_tech/contact_support.html).
They have to give you the source code of their own version of Android according to GPL 2.0 (https://www.gnu.org/licenses/old-licenses/gpl-2.0.html).
Related
developing an app for the 2013 nexus 7 with android studio on windows 8.1. i have the app running on a few different devices. when adding a driver, i get a dialog:
with the clockwork mod manufacturer, i get other choices like: google nexus 7 adb interface version 7.0.0.1 or 7.0.0.4.
i assume that i want an adb interface or a composite one, but sometimes there are many choices.
which interface should i use for the 2013 nexus 7?
thanks
Please find the OEM USB Drives from here.
Android Composite interface is higher level interface that includes Android ADB (Android Debug Bridge) interface, Android MTP (Media Transfer Protocol), PTP (Picture Transfer Protocol), Mass Storage Protocol etc.
I think you can go forward with ADB Interfere v8 as it's backward compatible.
Make the choice as per your requirment.
You can use the newest ADB driver fine.
But if you are having problems picking the device up in Android Studio, then make sure you have the device connected using the correct protocol.
Usually you have the choice between Media (MTP) or Camera (PTP).
This can vary between devices but use whichever one works for you, and makes the device appear in Android Studio.
You can use pdanet if you are using mac or windows.
it supports most of the devices for debugging and is really helpful for some country based manufacturers.
You should download and install the driver from Google
https://developer.android.com/sdk/win-usb.html
The CWM ones may work, but the Google drivers are the officially supported drivers for the Nexus 7
I have read that some phones, specifically kernels do not support the use of systrace.
It hit me when the same pc configuration that does not work on my phone works on my emulator.
So ultimately my question is: How to check if my android phone supports the use of systrace debugging?
Also, If possible, if the phone does not support it by default, can it be enabled?
Other relevant information:
Running on a rooted android phone (JellyBam 7.1 Rom)
Android Version: 4.2.2
If it matters I am running systrace from a windows 7 ADT (also tried command-line: Phython versions 2.0.x, 2.7.x and even 3.x)
I was looking on Sony's developer center for the kernel source of the Xperia E dual's 11.1.A.0.68 firmware, which, to my knowledge, is the latest ICS firmware for the device (all later ones were Jelly Bean). The only ICS firmware I can find there is 11.1.A.0.53, and that is a firmware I do not currently have access to. Help?
I don't believe you'll be able to find it. Sony isn't supporting development much on its low end devices. I tried finding Xperia M kernel but did not get anything from sony. Try using a kernel from xda dev or building your own kernel.
Is there a list anywhere of which Android devices (phones, tablets) support the ADK / accessory mode? From what I have read, I known that the Nexus One, Nexus S and Xoom do support it. Are there any other devices (custom ROMs included) that also support it? I have an ADK and can't get it working with my phone, I am basically looking for the cheapest phone that I can use with ADK.
** UPDATE ** I found this list of tablets that work with the ADK
The offical Android 2.3.4 is based on the kernel 2.6.35, ADK need kernel 2.6.35. Some Android 2.3.4+ do not support adk because the kernel is not 2.6.35+. I used to copy the adk need jar into my milestone (Android 2.3.5, kernel 2.6.32, cm7), and install the DemoKit.apk but it doesn't work.
The phone I know ADK works: Nexus One, Nexus S, HTC Desire(need to do something to make it work)
I think if the phone have kernel 2.6.35+ and android 2.3.4+ it will support ADK too, but I can't find a 2.6.35+ kernel for my Milestone.
When I was digging around in the CyanogenMod 7.1 kernel sources for my Galaxy S2 I found that the USB accessory driver missing from kernel 2.6.35.7 (I think the kernel .config flag is CONFIG_USB_ANDROID_ACCESSORY).
From what I've found by a lot of searching and forum digging was that the accessory driver was implemented in Honeycomb (3.x) but backported to Gingerbread (2.3), and should be available from kernel 2.6.35.15. I made a few unsuccessful attempts to compile my own kernel, with the plan to cherry pick the driver but for some reason I was not able to make the phone boot with my custom kernel.
I am now running an early experimental CyanogenMod 9 ICS (4.0.3) build on my SGS2 and it is possible to have the phone talk with my Arduino board. I made the phone able to toggle an LED on the board so I guess it is time to start working on my plans for world domination.
In theory, any device running Android 2.3.4+ or 3.1+ should be compatible with the ADK (as long as they have a USB port). I don't think any manufacturers remove the ADK from their builds (I don't see why they would), but it's not impossible either.
So, you either update your phone to 2.3.4 (if it's possible), buy a phone that runs 2.3.4+ (the minor version is important -- 2.3.3 does not have the ADK) or buy a tablet that runs 3.1+.
If you're going to buy a phone, I recommend a Google-branded phone, such as the Nexus S.
Known good: Nexus S (not 4G) running ICS 4.0.4.
ICS 4.0.3 is known not to work. Don't know anything about 2.3.x.
My environment is: windows xp sp3, eclipse, all available software installed using SDK Manager.
Following Android developer site's guide, I could write and run hello world app on Android 2.3 emulator. Then I wanted to see if I could run my app on a real device - vodafone 845 (huawei U8120?) in my case. Here I stuck for two days now trying to install windows usb driver for my device. When I connect my device through usb with Debug setting On, windows keeps to ackowledge it as usb mass storage. On Device Manager, I tried Update Driver, selected C:\Program Files\Android\android-sdk-windows\google-usb_driver\android_winusb.inf file. it complained like:
"The specified location does not contain information about your hardware"
It's probably because of missing manufacturer/product information (VID_12D1&PID_1031) in inf file, right?
http://developer.android.com/sdk/win-usb.html site lists supported devices and says that any additional devices will require Windows drivers provided by the hardware manufacturer but so far I couldn't any information.
I guess many developers are facing this issue with their own devices that is not supported by Android SDK and I wonder how they overcome this issue - especially for vodafone 845 device.
Thanks in advance
Bob
This thread states that the USB drivers are included on the phone. Once the phone is connected as a USB mass storage device, browse the contents and look for the driver installer. If you have deleted it or are using a custom ROM you may need to search for the drivers on google.
PS This isn't really a hardware support site.
Yes this works like charm. Everything is located on the sd card. There are some weird things though:
- You can't to choose, if you want to mount the your phone as storage, on other phones you can.
- For us the install did not work at first, only the second time.