Database Users

[Q] Hauwei Ascend M860 Why do you hate me?

Ok,
So Ive been scouring the net to find out if there is anyway I can get my device to be recognized. So far I've tried:
Windows 7 Ultimate 64bit, phone goes into storage mode and loads the drivers. although the drivers are not signed so windows refuses to load them, nice microsoft.
Ubuntu 10.04 64bit, ok i've installed usb_modeswitch and setup a bunch of udev rules (attached) and I can get the device to be detected but not recognized ie if I execute
Code:
adb devices
I get
Code:
List of devices attached
???????????? device
if I try
Code:
adb shell
I get dropped right into the user shell on the device. *Nice* score one for linux, but this doesn't do me much good because if I try to bring up the dalvik monitor it refuses to recognize the device grrr bad linux
I've attached my udev rules and a listing from when I tried to start the dalvik monitor, if anybody has some idea how I can get either windows to load the provided drivers or ubuntu to recognize the device I would be eternally greatfull
Thanks
Tired and wear from trudging around the net all day
Ben

Motorola Xoom running Debian with KDE 4 natively (without chroot)

Hi All,
The following is a custom setup based on LIV2's original tutorial, running Debian Linux with KDE 4 natively (no chroot) instead of Gnome and a few tweaks of my own.
Please follow LIV2's original tutorial and note my changes below:
I have posted the video on my Youtube page (can't add due to insufficient posts)
I will upload the boot.img image and files shortly.
What works
- Booting into KDE 4
- On screen keyboard based on xvkbd
- Wireless bcm4329 driver loads (must configure manually via wpa_supplicant)
- USB keyboard USB OTG cable (made by Motorola)
Instructions
1. Follow LIV2's original instructions until:
Code:
# echo “deb ftp.debian.org/debian/ squeeze main contrib non–free” > /etc/apt/sources.list
2. Also add this:
Code:
echo “deb backports.debian.org/debian-backports squeeze-backports main contrib non-free” >> /etc/apt/sources.list
3. Refresh repo:
Code:
apt-get update
4. Run this:
Code:
apt–get install xserver–xorg–video–fbdev xserver–xorg–input–evdev gnome initramfs–tools
Aptitude install kde-desktop
apt-get install bluez kdebluetooth xvkbd
(instead of this):
Code:
# apt–get install xserver–xorg–video–fbdev xserver–xorg–input–evdev gdm3 gnome initramfs–tools wpa-supplicant
Don't worry about wpa-supplicant, it will be installed as part of kde-desktop packages.
5. Edit the following files to make the on screen keyboard (xvkbd) work properly:
/etc/kde4/kdm/kdmrc
Code:
UseTheme=false
/etc/kde4/kdm/Xsetup
Code:
xvkbd geometry -300-100 -no-back-pointer &
6. Continue with LIV2's instructions
7. Make following directories under your chroot and copy the wireless firmware files:
Code:
/vendor/firmware for fw_bcm4329.bin
/system/etc/wifi for bcm4329.cal
Copy files above in the noted directories. I had to slightly alter LIV2's step here since the module wouldn't load when files where copied to those other folders mentioned in his tutorial.
8. Continue with LIV2's instructions but run this:
Code:
sudo make INSTALL_MOD_PATH=[PATH_TO_CHROOT_DIR] modules_install
(instead of):
# export INSTALL_MOD_PATH=[PATH_TO_CHROOT_DIR]
The original step above failed to install/copy the modules into the correct location.
9. Follow LIV2's instructions to the end
Please use the NDK mentioned in LIV2's tutorial, android–ndk–r5b and not newer otherwise it will not work.
These steps are based on the Tiamat 1.4.4 kernel (stock GPU)
Updates will follow...

Does sound work?

No sound support. I did not see any support in the kernel for the CPCAP 2.2TC22 SoC.
LE: Actually, it's gotta have something, just does not seem to work out of the bat. dmesg shows CPCAP info and plenty of related devices in /dev . Have to figure out how and if I can use them.

Cool. Love KDE 4! Would it be possible to add the Bodhi-repo and install E17 and use the Tablet-profile of E17?

Got it to work... but too many errors still. Need help.
Thanks for the great work and explanations.
I have setup Debian 6 (and also Ubuntu 10.10) from scratch + latest updates, to build it. But installing the packages (xserver etc...) produces lots of errors with qemu such as:
unsupported system call 341
many packages failed to install
...
The worse case is with gnome, complete failure to apt-get update. With KDE, I succeeded using aptitude and removing some recommended packages. Still the final system is not working as on the video.
After hours of googling, I came to the conclusion that you guys must use some customized system that I couldn't reproduce. Would you care sharing what is your environment, packages installed and patches?
Thanks

any progress done?
hi everyone,
i'm dying to move away from android to debian. i was wondering was there any progress done? is there a project going on? did anyone fix the sound+bluetooth not working?

NICE !
Awesome Project :good: :good:
The only thing that makes me wonder ist... android should be a openSource project based on Linux.
But we have to struggle and "fight" to make linux run on it?!?!?!
Can you give us an update on what works and what not and if you or who continues this project, please?
The XOOM ist still one of the best tabletts on the market since it has UMTS build in.
I would love to see Debian etc. running on it and most of the functions (camera, GPS, USB, WLAN) working fine.....
....don't leave us hanging now
At least leave full infos on how you approached the task and where you left it, oki.
thx

...
illuminate7 said:
Awesome Project :good: :good:
The only thing that makes me wonder ist... android should be a openSource project based on Linux.
But we have to struggle and "fight" to make linux run on it?!?!?!
Can you give us an update on what works and what not and if you or who continues this project, please?
The XOOM ist still one of the best tabletts on the market since it has UMTS build in.
I would love to see Debian etc. running on it and most of the functions (camera, GPS, USB, WLAN) working fine.....
....don't leave us hanging now
At least leave full infos on how you approached the task and where you left it, oki.
thx
Click to expand...
Click to collapse
+1

[Q] Andriod 4.2.2 adb on linux

Hi,
Need latest adb and fastboot under linux which works for andriod 4.2.2. Whenever i tried to connect it says. I solved on windows by downloading the latest adb from xda site.
List of devices attached
0062bdd0d056b091 offline
Regards,
Lokesh

lokeshv said:
Hi,
Need latest adb and fastboot under linux which works for andriod 4.2.2. Whenever i tried to connect it says. I solved on windows by downloading the latest adb from xda site.
List of devices attached
0062bdd0d056b091 offline
Regards,
Lokesh
Click to expand...
Click to collapse
Same issue, any help would be great... the sdk says up to date.

I've attached the adb and fastboot binaries from the latest Android SDK for Linux. Also make sure you check the phone for the popup to confirm adding the PC's signature to the device's whitelist.

I assume you're using Ubuntu in which case android-tools is in the Ubuntu Repository for 12.10.
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
If you want a more update ADB and Fastboot use this ppa http://www.webupd8.org/2012/08/install-adb-and-fastboot-android-tools.html
I have the one from Ubuntu repository installed on 13.04 and it works fine with my 4.2.2 devices.
Also, like tuxdude said, make sure you have your PC whitelisted so it is able to connect via adb. New security feature in 4.2.2

Try disabling and re-enabling usb debugging while plugged in. It's the only way i got the rsa verification on osx, which before i had the offline device output message.

I had a same problem, and I found the solution.
If the adb the newest, and RSA windows doesn't appear on phone, check the .android directory (in your Home directory) ownership and permission. Mine was wrong, root was the owner.

ADB device communication protocol

I am developing (currently in plan phase ) a framework to allow developers to connect to a remote android machine while working on eclipse.
The idea is, there will be a java program running on the developer's comp, which will behave as an emulator and pass all the adb commands to a remote machine (mac, windows, or linux: over net). There will be another java client app on that remote machine which will receive those commands and give them to the local adb demon (which in turn will give it to the connected android device).
This will allow remote debugging where direct port forwarding is not possible, like solving specific customer's issue.
Does such a framework already exist?
Where can I find the documentation on how to emulate an android device and how does adb demon communicates with the device?

turn old phone as arm board project

hi all,
so , i've 4 old phones arm based uc :
htc wildfire, acer liquid e1 , thomson every40, and a ms lumia 640 ,
i would like to reuse them in a arm board project .
my goals are:
to set up one as "home nas" conneted in wifi to my providerbox and provide ssh(at least ) ,vpn and files server service.
And a second one set up as: a mobile hotspot (open wifi) where connected user can drop and drag files .
and add a webgui where I will able to turn the wifi card into a wifi repeater .
i don't need user interface (screen on the device) the goal is to turn on and get the system loaded and setuped
so guys , do you have some leads, advice or trick for load mini linux(openwrt or debian arm ) directly by the bootloader .
thx

I don't know about the Lumia, but you can easily run a Linux desktop distro on the Android phones. If you have experience with Linux, or just Google a bit, you can easily find tools that provide what you want. To get a desktop distro running, root the device. Then you can either chroot into a distro manually (plenty of guides on XDA for that), or use an app called Linux Deploy. Both methods will give you a complete, un-emulated distro. Both methods need booting into Android, but even such old phones should be able to handle a minimal Debian or Ubuntu ARM chroot pretty well. Just do not install a DE, do the initial set up over SSH. I don't think you can boot into something other than Android on those devices.

grip-it & rip-it
an even easier option (and better, imho) is to just download termux and yer set. You can download appropriate packages, dependencies, libs. etc... from inside the terminal. and that's all m8.
ch33rs