Hi XDA,
I am trying to make my Hero work with the Arduino Mega ADK (Accessory Development Kit), but it never detects it.
The files com.android.future.usb.accessory.jar and android.hardware.usb.accessory.xml have been added to the system, as proposed on this thread: https://github.com/ezterry/manifest-gingerbread-DS/issues/32.
The Arduino says:
Code:
Device addressed... Requesting device descriptor.
found possible device. swithcing to serial mode
Data packet error: 5could not read device protocol version
I am currently under SHPONGLE v3.5, but exactly the same happens with Elelinux 7.2.
Does someone knows a ROM that can handle it? I think it should be possible, because the HTC Dream can.
Maybe recompiling the kernel is necessary ?
Thanks!
Related
First a short question. What is the device configuration.(For example:https://github.com/TeamICS/android_device_htc_heroc) Which information does it contain? I don't think it's the whole Rom, but they update it, change stuff and so on?
Now my actual question:
I want to port a Kernel+System on an unsupported device.
Where do I have to start. Is there a difference between building it from source or port one from a similar device? Is one solution slower, more complicated or anything? There are many tutorials for porting, just bundle a system with a working kernel, but what to do if I want to have the Kernel also?
How do I extract the Device Proprietary Files without an github of the device?
Links, short explanation of the steps or anything else would be helpful.
I am sorry if this post seems to be ill informed, but I am searching and searching and can't find really helpful information..
chaoskoch said:
First a short question. What is the device configuration.(For example:https://github.com/TeamICS/android_device_htc_heroc) Which information does it contain? I don't think it's the whole Rom, but they update it, change stuff and so on?
Now my actual question:
I want to port a Kernel+System on an unsupported device.
Where do I have to start. Is there a difference between building it from source or port one from a similar device? Is one solution slower, more complicated or anything? There are many tutorials for porting, just bundle a system with a working kernel, but what to do if I want to have the Kernel also?
How do I extract the Device Proprietary Files without an github of the device?
Links, short explanation of the steps or anything else would be helpful.
I am sorry if this post seems to be ill informed, but I am searching and searching and can't find really helpful information..
Click to expand...
Click to collapse
First off what device do you have?
This link might be helpful
How to Port Android to Another Device
Now in regard to your questions i'll do my best to answer them best I can. The device configuration think of it as a fingerprint every fingerprint is unique (Although some a very similar), basically when building from source is tells the build what device you want the version of android your compiling to run on. They update and change the device configuration to reflect changes in the different versions of Android (Going from Gingerbread to ICS for example). Porting Kernels is not easy if you don't know C, things about embedded systems, basic Linux knowledge, among other skills but take a look at Guidance regarding Kernel porting, and what do you mean by port system? Here is a basic place to start for kernels AOSP Building Kernels and Building Your First Kernel. Yes their is a difference between porting a kernel and building from source, porting implies taking a kernel from device A and porting it to device B, while building from source means your building directly for device A. Porting in your case is probably going to be harder then building from source. If you want to have the kernel also again you have to modify it to run on the device you are porting it too. To extract proprietary files you have to hook your device up to your computer, turn on usb debugging, and using ADB run these commands:
Code:
cd ~/android/system/device/motorola/sholes/ # Replace Motorola and Sholes with your vendor such as HTC, Samsung, etc. and your device codename
Then run:
Code:
./extract-files.sh
Look at this guide for more info Compiling ICS from Source. Hope this helps you in some way :good:.
Hi
Could anybody point me in the direction of sourcing, locating and compiling a kernel module please? I have found many guides but they all seem to start halfway in the process ("assuming you have already managed to...", "assuming you are already proficient with...")
I have a cheap Android Chinese TV box. It came without joydev.ko so I can't use it with joypads/sticks, which is a pretty big limitation considering it has 4 usb ports which work fine with keyboards, mice and webcams.
I already have an Eclipse environemt set up which I use for Java/Android development but I've never dabbled with anything like this before.
I guess the steps required are something like this:
Locate source code for my particular Android version (Android 4.2.2, Kernel 3.3.0) - where do I do that? Do I need the entire source or can I just download and compile the module by itself?
Set up the cross compiler - is this a standard thing, or does it depend on my hardware? My chipset is an Allwinner A20 ARM Cortex-A7(Dual Core)
Compile the module.
So, have I got the steps right? If not, please correct me. If so.... how do I go about doing the above?
My company has recently received some new android hardware and has requested that I create a custom operating system for the device. The manufacturer has agreed to provide us with the existing android source, but I have a few questions to get started:
On the following link: http://source.android.com/source/initializing.html
It states that I need to add lines similar to the below to my "51-android.rules" file:"
# adb protocol on maguro/toro (Galaxy Nexus)
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="6860", MODE="0600", OWNER="<username>"
How do I determine the correct information to use for this process? Should I collect this information with the device connected to a windows PC?
Once connected, I would like to scrap their existing operating system and begin from AOSP source, what information from their original source should I retain (Kernel, bootloader, etc), and what information would I be required to remove to bring in AOSP?
I have found many guides which help me to answer these questions, but most seem to be specifying nexus devices, or devices which already have a strong developer backing, neither of which apply to this hardware.
Edit:
I think I've found the guide I'm going to use, if anyone is actually interested I will post my results of success or failure when we have received the source code.
Link: http://forum.xda-developers.com/showthread.php?t=1598713
maybe help
http://www.youtube.com/watch?v=1_H4AlQaNa0
Hello,
I have an MTK device (Ixion MS155, with MT6737 chipset, to be pricese) that I flashed with a custom ROM. Unfortunately, being new to flashing, I carelessly didn't backup the NVRAM with the IMEI numbers, which got reset to Null. I know that this problem can be addressed through the MTK Engineer Mode. But to activate the right menu option, I need an auxiliary package usually called CDS_INFO.apk, which was not included in the ROM. I found some versions of that package online, but they don't seem compatible with my specific device and/or ROM combination (one version almost works, but it seems that it was compiled against a different Android API/ABI version). This is not a very popular device model, so there are not many ROMs available for it, and I've not yet found one that is capable of running Engineering Mode with the right menu options.
Now, my main question is this: I did find a repository on GitHub (can't post a direct link: user Danile71, repository android_kernel_zte_run4g_mod, path /tree/master/mediatek/packages/apps/CdsInfo) with the source code for CDS_INFO.apk (as well as other low level packages like EngineerMode.apk itself). What could really help me is compiling these packages against the Android 7.1 API/ABI (which I believe would be API version 25). Now, I don't have any direct experience building APK packages from source. Could some kind soul help me out and build an appropriate version of these packages? CDS_INFO.apk and EngineerMode.apk would be sufficient for my purposes, but they might have some other internal dependencies.
Please let me know if there's a better subforum where to direct this request. Thank you in advance for any help!
caveat: I'm new to java Dev and Android as Python is my main language.
I purchased a ZX808 from Topin
From what i can see its using a custom Rom developed in house. on a mt6580 (android 5.1)
Kernel 3.10.72
gcc 4.8
For the life of me i cannot get location manager working on the device. Running a multitude of different apps, i've come to a conclusion that there is some sort of proprietary override.
My hope is that this is potentially Software based and not Hardware based (i hope!)
My question to you guys, is where to start. and what is my backup plan?
I've done an ADB Backup, but where i'm going i don't think this will be enough of a parachute.
1. What is the best way to backup this proprietary rom (if possible)
2. Any recommendations for simplistic Rom to install on this chipset? (looking at this one
3. Any way to enable USB debugging from the Rom itself on install? (Headless unit so only control i can get seems to be USB debugging via totalcontrol)
Really worried about the device being screenless. Any Recovery mode and things like that all have to be guesses based on other peoples screenshots. any way around this? It does have a small ribbon cable attachment. Maybe i find a matching screen first?
I cannot attach links to the Screenshots and Aliexpress site for the device i'm too new
glen020 said:
I cannot attach links to the Screenshots and Aliexpress site for the device i'm too new
Click to expand...
Click to collapse
Here is the link: https://www.aliexpress.com/i/32963286807.html