Database Users

[Q] Troubleshooting boot problems

Disclaimer: This is my first time trying to compile a ROM.
I was hoping that I could get a little advice on troubleshooting my build that won't boot. I'm building Omni for my Motorola Atrix 2 and I have gotten it to build successfully and it installs. It will never completely boot, it hangs at the boot animation indefinitely. I suppose there are probably many things that cause this but I'm lost on where to start. I've looked through a lot of peoples local_manifests to see what repos they were adding/removing and it always ends up the same for me, stuck on the boot animation. So here's a little information about my build:
Device: Motorola Atrix 2 (edison)
PC Mint 15 KDE 64 bit with 8GB or RAM and ~1TB of free space
Devices/kernel sources: https://github.com/MO4 (Tried CM11 and a dev suggested trying slim4.4)
Proprietaries: https://github.com/TheMuppets/proprietary_vendor_motorola
My current local manifest:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- REMOVALS -->
<remove-project name="android_hardware_ti_omap4xxx" />
<remove-project name="platform/hardware/ti/wlan" />
<remove-project name="platform/hardware/ti/wpan" />
<remove-project name="android_hardware_libhardware_legacy" />
<remove-project name="android_external_wpa_supplicant_8" />
<!-- DEVICE -->
<project name="MO4/android_device_motorola_edison" path="device/motorola/edison" remote="github" revision="slim4.4" />
<project name="MO4/android_device_motorola_maserati" path="device/motorola/maserati" remote="github" revision="slim4.4" />
<project name="MO4/android_device_motorola_omap4-common" path="device/motorola/omap4-common" remote="github" revision="slim4.4" />
<project name="MO4/android_device_motorola_spyder" path="device/motorola/spyder" remote="github" revision="slim4.4" />
<project name="MO4/android_device_motorola_targa" path="device/motorola/targa" remote="github" revision="slim4.4" />
<project name="MO4/android_device_motorola_umts_spyder" path="device/motorola/umts_spyder" remote="github" revision="slim4.4" />
<!-- KERNEL -->
<project name="MO4/android_kernel_motorola_omap4-common" path="kernel/motorola/omap4-common" remote="github" revision="cm-11.0" />
<!-- VENDOR -->
<project name="TheMuppets/proprietary_vendor_motorola" path="vendor/motorola" remote="github" revision="cm-11.0" />
<!-- EXTRAS -->
<project name="CyanogenMod/android_external_wpa_supplicant_8" path="external/wpa_supplicant_8" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_external_wpa_supplicant_8_ti" path="external/wpa_supplicant_8_ti" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_hardware_ti_omap4xxx" path="hardware/ti/omap4xxx" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_hardware_ti_wlan" path="hardware/ti/wlan" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_hardware_ti_wpan" path="hardware/ti/wpan" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_prebuilt" path="prebuilt" remote="github" revision="cm-11.0" />
<project name="alteredlikeness/slim_hardware_libhardware_legacy" path="hardware/libhardware_legacy" remote="github" revision="kk4.4-mo4" />
</manifest>
There are a couple of things that I wasn't sure of with my build. First, my phone uses BootMenu Manager for recovery, not TWRP. The source I grabbed for my device are from ROM's that also use BMM. Could this be related to it not fully booting? Second is the omni.dependency file in my device directory. It appears that this might be used instead of a local manifest for devices that are officially supported by Omni? Since mine is not, I used the local manifest to get my device/kernel sources so my omni.dependency file is essentially empty.
After a couple of weeks of trying to get this to boot, I decided to switch to CM11 to see if I could build anything and I got that to boot. Granted this has already been done for my phone so all the leg work with the sources was pretty much done. I just wanted to see if I got the same result with another ROM.
I tried to get ADB working to see if I could get a logcat or something but since I cannot get it to boot, I cannot authorize my phone so it always says "unauthorized" when I try to connect while it's stuck. I don't think it produces a last_kmsg since the kernel doesn't crash. I'm not sure where to go from here other than give up. I'd hate to do that though!
Any advice?

Long Time User, First Time Builder

Hey guys, I'm trying to tackle Liquid ROM after I found out someone has successfully built the ROM for our device. He shared his roomservice.xml and I spent last night syncing the repos for Liquid ROM. However, this morning I went to run the "lunch" command and got this:
Code:
You're building on Linux
Lunch menu... pick a combo:
35. liquid_klte-userdebug
Which would you like? [aosp_arm-eng] 35
ls: cannot access device/*/klte/liquid.mk: No such file or directory
build/core/product_config.mk:231: *** Can not locate config makefile for product "liquid_klte". Stop.
File "build/tools/roomservice.py", line 113
except IOError, ES.ParseError:
^
SyntaxError: invalid syntax
ls: cannot access device/*/klte/liquid.mk: No such file or directory
build/core/product_config.mk:231: *** Can not locate config makefile for product "liquid_klte". Stop.
** Don't have a product spec for: 'liquid_klte'
** Do you have the right repo manifest?
For simplicity, this is my first time compiling, I'm using Arch Linux, and the only file I have to fill in the gaps is the roomservice.xml I'm pasting below:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="gh" revision="cm-11.0" />
<project name="Team-Hydra/android_vendor_samsung" path="vendor/samsung" remote="gh" revision="cm-11.0" />
<project name="Team-Hydra/android_kernel_samsung_klte" path="kernel/samsung/klte" remote="gh" revision="cm-11.0" />
<project name="CyanogenMod/android_device_samsung_msm8974-common" path="device/samsung/msm8974-common" remote="gh" revision="cm-11.0" />
<project name="CyanogenMod/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="gh" revision="cm-11.0" />
<project name="LiquidSmooth-Devices/android_device_qcom_common" path="device/qcom/common" remote="gh" revision="kitkat" />
<project name="android_hardware_qcom_display-caf-new" path="hardware/qcom/display-caf-new" remote="ls" revision="kitkat" />
<project name="android_hardware_qcom_media-caf-new" path="hardware/qcom/media-caf-new" remote="ls" revision="kitkat" />
<project name="Team-Hydra/android_device_samsung_klte" path="device/samsung/klte" remote="gh" revision="cm-11.0" />
<project name="Team-Hydra/android_device_samsung_klte-common" path="device/samsung/klte-common" remote="gh" revision="cm-11.0" />
</manifest>
So my question is, should this xml file be what substitutes my "lunch" choice and am I missing a step to get this thing started? I appreciate any help you guys can offer; I know this can be built successfully I already ran a good build. I just have no desire to Kang work and post it here when I can learn to make my own. Thanks for any guidance you guys have to offer !

[Guide] How to build your own Cyanogenmod 11 for d850/d851/d852/d855/vs985/ls990

Now model vs985 and d850 can get official version at download.cyanogenmod.com
Support model for this method are d850/d851/d852/d855/vs985/ls990
Thank you for source code from @invisiblek (https://github.com/invisiblek)
Thank you for original thread from @Raum1807 (http://forum.xda-developers.com/nexus-4/general/guide-cm11-how-to-build-cyanogenmod-11-t2515305)
Thank you for original manifest from @Skin1980 (https://github.com/Skin1980/local_manifests)
Overview
I. Preparation
II. Installation of the required packages
III. Installing Java
IV. The sources
V. Building the ROM
VI. Rebuilding with newest sources
I. Preparation
Things you need for building:
A computer
An internet connection
An open mind
Time
Patience
First of all, you need a running up-to-date Ubuntu/Linux system. I am using Ubuntu 14.04 64-bit.
Use the terminal to make the steps. A terminal window can be opened by pressing Ctrl+Alt+T. Every single command for the terminal is marked with a $ sign. Just paste every command (without the $ sign) to your terminal window and there shouldn't be any problem.
IMPORTANT: INSTALL EVERYTHING AS A NORMAL USER. DON'T INSTALL AS ROOT!
II. Installation of the required packages (Ubuntu 14.04 64-bit)
Install packages:
Code:
$ sudo apt-get install bison build-essential curl flex \
g++-multilib gcc-multilib git-core gnupg gperf \
lib32ncurses5-dev lib32readline-gplv2-dev lib32z1-dev \
libesd0-dev libncurses5-dev libsdl1.2-dev \
libwxgtk2.8-dev libxml2 libxml2-utils lzop \
openjdk-6-jdk openjdk-6-jre pngcrush schedtool \
squashfs-tools xsltproc zip zlib1g-dev
III. Installing Java
You need a version 6 Java Development Kit for building CM11.0. Usually, the SUN JDK 6 is recommended. But there is another way: you can use the OpenJDK 6. When you installed the required packages as described above, you will just need to configure your Java installation.
Check your Java version:
Code:
$ java -version
Verify the symlinks. Javac, Java, Javaws, Javadoc, Javah, Javap and Jar should all point to the right Java location and version:
Code:
$ ls -la /etc/alternatives/java* && ls -la /etc/alternatives/jar
If they are pointing to the wrong versions you have to change that to OpenJDK6.
Select the default Java version for your system:
Code:
$ sudo update-alternatives --config javac
$ sudo update-alternatives --config java
$ sudo update-alternatives --config javaws
$ sudo update-alternatives --config javadoc
$ sudo update-alternatives --config javah
$ sudo update-alternatives --config javap
$ sudo update-alternatives --config jar
That's it.
IV. The sources
Install repo:
Repo is a tool that makes it quite easy to download and maintain the sources of Cyanogenmod.
Code:
$ mkdir ~/bin
$ PATH=~/bin:$PATH
$ cd ~/bin
$ curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
$ chmod a+x ~/bin/repo
Create the working directory:
Code:
$ mkdir ~/cm11
$ cd ~/cm11
Initialize Repo:
Code:
$ repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
and enter your credentials.
Download the sources:
Code:
$ repo sync
Wait until it's finished - takes some time to download the hefty 12 GB of source code!
Have a break, have a KitKat!
If the process hangs use Ctrl+C to break out of it and resume the download with another
Code:
$ repo sync
If you are running into a lot of syncing errors the reason might be that the 'repo sync' command is establishing four threads automatically. This might be too much. So try to change the command to run with one thread only by using
Code:
$ repo sync -j1
Initialize the environment
Code:
$ . build/envsetup.sh
Obtain the proprietary files:
First get two missing repositories for the Nexus 4 by running
Code:
$ breakfast <your model>
Then create a file with the name local_manifest.xml in the local_manifests directory. To see this directory, you have to press Ctrl-H in your file manager.
Use this code
Code:
$ gedit ~/cm11/.repo/local_manifests/local_manifest.xml
Please make sure you copy and paste code with your correct model
Paste the following lines to the editor
D850
Code:
<manifest>
<!-- D850 -->
<project path="device/lge/d850" name="invisiblek/android_device_lge_d850" remote="github" revision="cm-11.0" />
<project path="device/lge/g3-common" name="invisiblek/android_device_lge_g3-common" remote="github" revision="cm-11.0" />
<project path="kernel/lge/g3" name="invisiblek/android_kernel_lge_g3" remote="github" revision="cm-11.0" />
<project path="vendor/lge" name="invisiblek/proprietary_vendor_lge" remote="github" revision="cm-11.0" />
<!-- CyanogenMod -->
<project path="device/qcom/common" name="CyanogenMod/android_device_qcom_common" remote="github" revision="cm-11.0" />
<project path="hardware/qcom/display-caf-new" name="CyanogenMod/android_hardware_qcom_display-caf-new" remote="github" revision="cm-11.0" />
<project path="hardware/qcom/media-caf-new" name="CyanogenMod/android_hardware_qcom_media-caf-new" remote="github" revision="cm-11.0" />
</manifest>
D851
Code:
<manifest>
<!-- D851 -->
<project path="device/lge/d851" name="invisiblek/android_device_lge_d851" remote="github" revision="cm-11.0" />
<project path="device/lge/g3-common" name="invisiblek/android_device_lge_g3-common" remote="github" revision="cm-11.0" />
<project path="kernel/lge/g3" name="invisiblek/android_kernel_lge_g3" remote="github" revision="cm-11.0" />
<project path="vendor/lge" name="invisiblek/proprietary_vendor_lge" remote="github" revision="cm-11.0" />
<!-- CyanogenMod -->
<project path="device/qcom/common" name="CyanogenMod/android_device_qcom_common" remote="github" revision="cm-11.0" />
<project path="hardware/qcom/display-caf-new" name="CyanogenMod/android_hardware_qcom_display-caf-new" remote="github" revision="cm-11.0" />
<project path="hardware/qcom/media-caf-new" name="CyanogenMod/android_hardware_qcom_media-caf-new" remote="github" revision="cm-11.0" />
</manifest>
D852
Code:
<manifest>
<!-- D852 -->
<project path="device/lge/d852" name="invisiblek/android_device_lge_d852" remote="github" revision="cm-11.0" />
<project path="device/lge/g3-common" name="invisiblek/android_device_lge_g3-common" remote="github" revision="cm-11.0" />
<project path="kernel/lge/g3" name="invisiblek/android_kernel_lge_g3" remote="github" revision="cm-11.0" />
<project path="vendor/lge" name="invisiblek/proprietary_vendor_lge" remote="github" revision="cm-11.0" />
<!-- CyanogenMod -->
<project path="device/qcom/common" name="CyanogenMod/android_device_qcom_common" remote="github" revision="cm-11.0" />
<project path="hardware/qcom/display-caf-new" name="CyanogenMod/android_hardware_qcom_display-caf-new" remote="github" revision="cm-11.0" />
<project path="hardware/qcom/media-caf-new" name="CyanogenMod/android_hardware_qcom_media-caf-new" remote="github" revision="cm-11.0" />
</manifest>
D855
Code:
<manifest>
<!-- D855 -->
<project path="device/lge/d855" name="invisiblek/android_device_lge_d855" remote="github" revision="cm-11.0" />
<project path="device/lge/g3-common" name="invisiblek/android_device_lge_g3-common" remote="github" revision="cm-11.0" />
<project path="kernel/lge/g3" name="invisiblek/android_kernel_lge_g3" remote="github" revision="cm-11.0" />
<project path="vendor/lge" name="invisiblek/proprietary_vendor_lge" remote="github" revision="cm-11.0" />
<!-- CyanogenMod -->
<project path="device/qcom/common" name="CyanogenMod/android_device_qcom_common" remote="github" revision="cm-11.0" />
<project path="hardware/qcom/display-caf-new" name="CyanogenMod/android_hardware_qcom_display-caf-new" remote="github" revision="cm-11.0" />
<project path="hardware/qcom/media-caf-new" name="CyanogenMod/android_hardware_qcom_media-caf-new" remote="github" revision="cm-11.0" />
</manifest>
VS985
Code:
<manifest>
<!--VS985 -->
<project path="device/lge/vs985" name="invisiblek/android_device_lge_vs985" remote="github" revision="cm-11.0" />
<project path="device/lge/g3-common" name="invisiblek/android_device_lge_g3-common" remote="github" revision="cm-11.0" />
<project path="kernel/lge/g3" name="invisiblek/android_kernel_lge_g3" remote="github" revision="cm-11.0" />
<project path="vendor/lge" name="invisiblek/proprietary_vendor_lge" remote="github" revision="cm-11.0" />
<!-- CyanogenMod -->
<project path="device/qcom/common" name="CyanogenMod/android_device_qcom_common" remote="github" revision="cm-11.0" />
<project path="hardware/qcom/display-caf-new" name="CyanogenMod/android_hardware_qcom_display-caf-new" remote="github" revision="cm-11.0" />
<project path="hardware/qcom/media-caf-new" name="CyanogenMod/android_hardware_qcom_media-caf-new" remote="github" revision="cm-11.0" />
</manifest>
LS990
Code:
<manifest>
<!--LS990 -->
<project path="device/lge/ls990" name="invisiblek/android_device_lge_ls990" remote="github" revision="cm-11.0" />
<project path="device/lge/g3-common" name="invisiblek/android_device_lge_g3-common" remote="github" revision="cm-11.0" />
<project path="kernel/lge/g3" name="invisiblek/android_kernel_lge_g3" remote="github" revision="cm-11.0" />
<project path="vendor/lge" name="invisiblek/proprietary_vendor_lge" remote="github" revision="cm-11.0" />
<!-- CyanogenMod -->
<project path="device/qcom/common" name="CyanogenMod/android_device_qcom_common" remote="github" revision="cm-11.0" />
<project path="hardware/qcom/display-caf-new" name="CyanogenMod/android_hardware_qcom_display-caf-new" remote="github" revision="cm-11.0" />
<project path="hardware/qcom/media-caf-new" name="CyanogenMod/android_hardware_qcom_media-caf-new" remote="github" revision="cm-11.0" />
</manifest>
Save the file.
Run
Code:
$ repo sync
again to get the files needed.
Download the necessary prebuilts from cyanogenmod by running
Code:
$ cd ~/cm11/vendor/cm
$ . get-prebuilts
$ croot
And you're done!
V. Building the ROM
Now build it:
Code:
$ brunch <your model>
change <your model> to d850/d851/d852/d855/vs985/ls990
And the building process starts. Now have patience. Building takes around half an hour on fast systems and a lot more on older and slower machines.
When everything worked as it should you will find your new ROM-image in ~/cm11/out/target/product/<your model>
It is called cm-11-DATE-UNOFFICIAL-<your model>-zip.
Before you flash you need to bump it first!
you can get bump from https://github.com/CyboLabs/Open_Bump
go to /cm11/out/target/product/<your model>/
copy boot.img and open_bump in same folder and run
Code:
python open_bump.py boot.img
you will get boot_bumped.img rename it to boot.img and push into "cm-11-DATE-UNOFFICIAL-<your model>-zip"
Now You can flash it via CWM/TWRP as usual.
VI. Rebuilding with newest sources
Whenever you like to update your sources and build a new version you have to run these four simple commands:
Code:
$ cd ~/cm11
$ repo sync
$ . build/envsetup.sh
$ brunch <your model>
Compiling takes less time than it took for creating the ROM the first time because it's only building new parts while reusing old parts that haven't changed.
and don't forgot bump boot.img
Happy building!

CM11 is not support for F400 korean models. Can you port it to F400 korean models? Thanks!

error
cant breakfast or brunch for D852
EDIT....
in the manifest copy paste for d852 there is a typo change the 851 to 852

LS990 issues
I am trying to compile for ls990 sprint g3
Can someone explain this part of the instructions to me? It says to get repositories for nexus 4, but then says "breakfast <your model>. I have tried entering my model "ls990" and it fetches a bunch of stuff. However, then when I "gedit ~/cm11/.repo/local_manifests/local_manifest.xml" and add the ls990 entries, it gives me a duplication error when I try to repo sync. I believe meaning that it already has downloaded the ls990 code from my "breakfast ls990" command.
Am I supposed to be doing a "breakfast mako" for the nexus 4? Please help. Been trying to compile this for a couple of days now.
----------
First get two missing repositories for the Nexus 4 by running
Code:
$ breakfast <your model>
-------------

Won't Compile - LS990
Ok, so after some research I realize that my above question was probably a typo. The problem is that when I create the local_manifest.xml file and add the ls990 info into it, when I do a repo sync I get fatal: duplicate path device/lge/ls990 in /home/mo1991/cm11/.repo/manifest.xml
I am not sure why this happens, perhaps the stuff in the manifest has now been officially added to the cyanogen repo - guessing here - and perhaps is not needed??? Or incorrect
Here is the edit command for the file I am talking about:
gedit ~/cm11/.repo/local_manifests/local_manifest.xml
Anyway, if I get rid of the manifest.xml file and brunch ls990 compile fails with
-------------------
make: *** No rule to make target `/home/mo1991/cm11/out/target/product/ls990/obj/lib/libtime_genoff.so', needed by `/home/mo1991/cm11/out/target/product/ls990/obj/SHARED_LIBRARIES/libandroid_runtime_intermediates/LINKED/libandroid_runtime.so'. Stop.
-----------------
Any help would be appreciated. Thanks.

You're correct that most repos in the local_manifest are now no longer necessary because it's officially supported. However, in order to get the proprietary blobs (which is what it's failing on) you still need to inlcude:
<project path="vendor/lge" name="invisiblek/proprietary_vendor_lge" remote="github" revision="cm-11.0" />
Or the one from TheMuppets. Alternatively, you could extract your own, but getting it from someone else is much easier

cre4per said:
cant breakfast or brunch for D852
EDIT....
in the manifest copy paste for d852 there is a typo change the 851 to 852
Click to expand...
Click to collapse
I have the same issue for d852
Any idea ?

Compiled but no sim card / bluetooth
Ok, I got it to compile by simply changing the ~/cm11/.repo/local_manifests/local_manifest.xml file to only include the proprietary blobs in the local_manifest.xml as per below.
<manifest>
<!--LS990 -->
<project path="vendor/lge" name="invisiblek/proprietary_vendor_lge" remote="github" revision="cm-11.0" />
</manifest>
Now it compiles. But I get no sim card thus no network. Also bluetooth appears to be broken. I know that jholtom at least had radio working, so I'm rying to manually add his changes to my source tree and recompile, but I'm really not sure if this is the right way to do it. On the bright side, I did get the rom to compile, bump, and boot up, so I"m further along than before
Thanks for the help.

Okay so, i have a small problem, let me explain.
The first time i did everything accordingly and everything worked as planned, booted, everything works fine. In fact, i'm running it right now, very stable and so on.
But when i'm trying to update the zip with all the new stuff, i get a very annoying error that i can't get rid of. And i don't know why it does that.
make: *** No rule to make target `device/lge/g3-common/configs/mixer_paths_qcwcn.xml', needed by `/home/android/cm11/out/target/product/d855/system/etc/mixer_paths.xml'. Stop.
make: *** Waiting for unfinished jobs..
Click to expand...
Click to collapse
It never did that when i first compiled it. Bear in mind that my linux knowledge is really limited, but i'm trying as hard as possible to understand where the errors comes from and stuff, but right now i'm stumped, can't get it to update it.
This happens when i "brunch d855", dunno why.
Thanks in advance.
PS: I'm running Builduntu inside of a VM, if that might help.

If you have previously successfully built, then try running "repo sync" again and then build. If that fails, try
Code:
repo forall -vc "git reset --hard"

[Q] ask for help: repo sync error as pull code through local manifests

hi, all, I am a new comer to CyanogenMod. According to the ReadMe instructions in github.com/RaymanFX/device_samsung_trelte, I follow up stey by step. But after I create .repo/local_manifests/roomservice.xml and then type repo sync, below error message pop up:
Fetching project platform/prebuilts/gcc/darwin-x86/arm/arm-eabi-4.7
Fetching project projects/android/android_kernel_samsung_trelte.git
Fetching project CyanogenMod/android_frameworks_opt_calendar
Fetching project platform/docs/source.android.com
Fetching projects: 2% (10/478) Fetching project CyanogenMod/android_external_yaffs2
fatal: remote error:
CyanogenMod/[email protected]:RaymanFX/projects/android/android_kernel_samsung_trelte is not a valid repository name
here's the local manifests file :
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="raymanfx" fetch="[email protected]:RaymanFX/" />
<project name="CyanogenMod/android_hardware_samsung_slsi_exynos" path="hardware/samsung_slsi/exynos" remote="github" />
<project name="CyanogenMod/android_hardware_samsung_slsi_exynos5-insignal" path="hardware/samsung_slsi/exynos5-insignal" remote="github" />
<project name="CyanogenMod/android_hardware_samsung_slsi_openmax" path="hardware/samsung_slsi/openmax" remote="github" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" />
<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" />
<project name="projects/android/android_hardware_samsung_slsi_exynos5433" path="hardware/samsung_slsi/exynos5433" remote="raymanfx" />
<project name="projects/android/android_kernel_samsung_trelte.git" path="kernel/samsung/trelte" remote="raymanfx" />
<project name="projects/android/android_device_samsung_trelte.git" path="device/samsung/trelte" remote="raymanfx" />
</manifest>
I am not familiar about repo&git, I am also searching on internet for answers. But it's highly appreciated If anyone can give me some hint. thanks!

Recon Jet Basic Info

So, I just got my Recon Jet (the self-declared "most powerful wearable computer" running Android 4.1, without Google services), and started doing some basic poking around. What would people like to know?
So far my basic impression is that I feel like I'm using a flagship smartphone running feature-phone software. All the specs are awesome, but the device does almost nothing out of the box, and there are no apps yet. The entire time I'm wearing it, it's like the device is screaming SOMEONE PLEASE MAKE A CUSTOM ROM WITH GOOGLE GLASSWARE SUPPORT.
Anywho, on to the nerdy stuff.
I didn't have the guts to try a fastboot oem unlock, so I didn't get very far in fastboot:
Code:
>fastboot -i 0x2523 getvar all
(bootloader) product: Jet_Fastboot
(bootloader) cpu: OMAP4430
(bootloader) cpurev: ES2.3
(bootloader) secure: GP
(bootloader) serialno: **redacted**
(bootloader) userdata_size: 6501231 KB
(bootloader) Flash Slot: EMMC(1)
all:
finished. total time: 0.031s
>fastboot -i 0x2523 oem ?
...
FAILED (remote failure)
finished. total time: 0.016s
>fastboot -i 0x2523 reboot
rebooting...
finished. total time: 0.000s
In ADB, without root, also didn't find too much interesting, but then again wasn't looking for anything in particular.
Code:
[email protected]:/ $ df
df
Filesystem Size Used Free Blksize
/dev 306M 32K 306M 4096
/mnt/asec 306M 0K 306M 4096
/mnt/obb 306M 0K 306M 4096
/system 503M 237M 266M 4096
/data 6G 255M 5G 4096
/cache 251M 24M 227M 4096
/factory 314M 179M 135M 4096
/storage/sdcard0 6G 255M 5G 4096
[email protected]:/ $ cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 7634944 mmcblk0
179 1 128 mmcblk0p1
179 2 2048 mmcblk0p2
179 3 128 mmcblk0p3
179 4 384 mmcblk0p4
179 5 327680 mmcblk0p5
179 6 16 mmcblk0p6
179 7 8192 mmcblk0p7
259 0 8192 mmcblk0p8
259 1 524288 mmcblk0p9
259 2 262144 mmcblk0p10
259 3 6501232 mmcblk0p11
[email protected]:/ $ ls -al /dev/block/platform/omap/omap_hsmmc.1/by-name
block/platform/omap/omap_hsmmc.1/by-name <
lrwxrwxrwx root root 2015-04-18 21:04 boot -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-04-18 21:04 bootloader -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-04-18 21:04 cache -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-04-18 21:04 crypto -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-04-18 21:04 efs -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-04-18 21:04 misc -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-04-18 21:04 recovery -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-04-18 21:04 system -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-04-18 21:04 ubootenv -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-04-18 21:04 userdata -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-04-18 21:04 xloader -> /dev/block/mmcblk0p1
[email protected]:/ $ ls
ls
acct
cache
charger
config
d
data
default.prop
dev
etc
factory
init
init.goldfish.rc
init.omap4jetboard.rc
init.omap4jetboard.usb.rc
init.rc
init.trace.rc
init.usb.rc
mnt
proc
res
root
sbin
sdcard
storage
sys
system
ueventd.goldfish.rc
ueventd.omap4jetboard.rc
ueventd.rc
vendor
Note that Recon devices do not use a VendorID recognized by standard adb and fastboot, so you will have to take extra steps to use these tools.
Specifically, to use ADB, you will need to modify (or create) an adb_usb.ini file containing 0x2523, and fastboot will have to use the -i option.
Users on the sparsely-used Recon forums (addressing almost exclusively Recon's previous generation of products) report being able to sideload APKs, but I can't think of any apps I would like on my face that don't rely on Google Play Services. Any suggestions?
Mods, please feel free to move this to the appropriate forum for Recon Jet, as soon as one exists. Until then, this seemed to me like the best place.

System app listing
Code:
<?xml version="1.0" encoding="utf-8"?>
<installed-packages>
<package name="android"
versionCode="16"
versionName="4.1.2-eng.linux-jenkins.20150414.021802" />
<package name="com.android.backupconfirm"
versionCode="16"
versionName="4.1.2-eng.linux-jenkins.20150414.021802" />
<package name="com.android.bluetooth"
versionCode="16"
versionName="4.1.2-eng.linux-jenkins.20150211.201015" />
<package name="com.android.certinstaller"
versionCode="16"
versionName="4.1.2-eng.linux-jenkins.20150414.021802" />
<package name="com.android.defcontainer"
versionCode="16"
versionName="4.1.2-eng.linux-jenkins.20150414.021802" />
<package name="com.android.htmlviewer"
versionCode="16"
versionName="4.1.2-eng.linux-jenkins.20150414.021802" />
<package name="com.android.inputdevices"
versionCode="16"
versionName="4.1.2-eng.linux-jenkins.20150414.021802" />
<package name="com.android.keychain"
versionCode="16"
versionName="4.1.2-eng.linux-jenkins.20150414.021802" />
<package name="com.android.packageinstaller"
versionCode="16"
versionName="4.1.2-eng.linux-jenkins.20150414.021802" />
<package name="com.android.providers.applications"
versionCode="16"
versionName="4.1.2-eng.linux-jenkins.20150414.021802" />
<package name="com.android.providers.calendar"
versionCode="16"
versionName="4.1.2-eng.linux-jenkins.20150414.021802" />
<package name="com.android.providers.contacts"
versionCode="16"
versionName="4.1.2-eng.linux-jenkins.20150414.021802" />
<package name="com.android.providers.downloads"
versionCode="16"
versionName="4.1.2-eng.linux-jenkins.20150414.021802" />
<package name="com.android.providers.downloads.ui"
versionCode="16"
versionName="4.1.2-eng.linux-jenkins.20150414.021802" />
<package name="com.android.providers.drm"
versionCode="16"
versionName="4.1.2-eng.linux-jenkins.20150414.021802" />
<package name="com.android.providers.media"
versionCode="509"
versionName="4.1.2-eng.linux-jenkins.20150414.021802" />
<package name="com.android.providers.settings"
versionCode="16"
versionName="4.1.2-eng.linux-jenkins.20150414.021802" />
<package name="com.android.providers.telephony"
versionCode="16"
versionName="4.1.2-eng.linux-jenkins.20150414.021802" />
<package name="com.android.providers.userdictionary"
versionCode="16"
versionName="4.1.2-eng.linux-jenkins.20150414.021802" />
<package name="com.android.provision"
versionCode="16"
versionName="4.1.2-eng.linux-jenkins.20150414.021802" />
<package name="com.android.settings"
versionCode="16"
versionName="4.1.2-eng.linux-jenkins.20150414.021802" />
<package name="com.android.sharedstoragebackup"
versionCode="16"
versionName="4.1.2-eng.linux-jenkins.20150414.021802" />
<package name="com.android.smspush"
versionCode="16"
versionName="4.1.2-eng.linux-jenkins.20150414.021802" />
<package name="com.android.systemui"
versionCode="16"
versionName="4.1.2-eng.linux-jenkins.20150414.021802" />
<package name="com.android.vpndialogs"
versionCode="16"
versionName="4.1.2-eng.linux-jenkins.20150414.021802" />
<package name="com.dsi.ant.plugins.antplus"
versionCode="30100"
versionName="3.1.0" />
<package name="com.dsi.ant.service.socket"
versionCode="40700"
versionName="4.7.0" />
<package name="com.dsi.ant.stonestreetoneantservice"
versionCode="1"
versionName="1.0" />
<package name="com.reconinstruments.QuickstartGuide"
versionCode="7047"
versionName="4.1.1" />
<package name="com.reconinstruments.agps"
versionCode="7047"
versionName="4.1.1" />
<package name="com.reconinstruments.appinstaller"
versionCode="7047"
versionName="4.1.1" />
<package name="com.reconinstruments.applauncher"
versionCode="7047"
versionName="4.1.1" />
<package name="com.reconinstruments.battery.logger"
versionCode="1"
versionName="1.0" />
<package name="com.reconinstruments.ble_ss1"
versionCode="7047"
versionName="4.1.1" />
<package name="com.reconinstruments.camera"
versionCode="7047"
versionName="4.1.1" />
<package name="com.reconinstruments.compass"
versionCode="7047"
versionName="4.1.1" />
<package name="com.reconinstruments.dashboard"
versionCode="7047"
versionName="4.1.1" />
<package name="com.reconinstruments.dashcompass"
versionCode="7047"
versionName="4.1.1" />
<package name="com.reconinstruments.dashlauncherredux"
versionCode="7047"
versionName="4.1.1" />
<package name="com.reconinstruments.dashlivestats"
versionCode="7047"
versionName="4.1.1" />
<package name="com.reconinstruments.dashwarning"
versionCode="7047"
versionName="4.1.1" />
<package name="com.reconinstruments.geodataservice"
versionCode="1"
versionName="1.0" />
<package name="com.reconinstruments.heading"
versionCode="7047"
versionName="4.1.1" />
<package name="com.reconinstruments.hfpservicess1"
versionCode="1"
versionName="1.0" />
<package name="com.reconinstruments.hudserver"
versionCode="16"
versionName="4.1.2-eng.linux-jenkins.20150414.021802" />
<package name="com.reconinstruments.hudservice"
versionCode="7047"
versionName="4.1.1" />
<package name="com.reconinstruments.itemhost"
versionCode="7047"
versionName="4.1.1" />
<package name="com.reconinstruments.jetapplauncher"
versionCode="7047"
versionName="4.1.1" />
<package name="com.reconinstruments.jetconnectdevice"
versionCode="7047"
versionName="4.1.1" />
<package name="com.reconinstruments.jetmusic"
versionCode="7047"
versionName="4.1.1" />
<package name="com.reconinstruments.jetsensorconnect"
versionCode="7047"
versionName="4.1.1" />
<package name="com.reconinstruments.jetunpairdevice"
versionCode="7047"
versionName="4.1.1" />
<package name="com.reconinstruments.lispxml"
versionCode="7047"
versionName="4.1.1" />
<package name="com.reconinstruments.lockdown"
versionCode="7047"
versionName="4.1.1" />
<package name="com.reconinstruments.maps"
versionCode="7047"
versionName="4.1.1" />
<package name="com.reconinstruments.mapservicess1"
versionCode="1"
versionName="1.0" />
<package name="com.reconinstruments.messagecenter"
versionCode="7047"
versionName="4.1.1" />
<package name="com.reconinstruments.mfitester"
versionCode="7047"
versionName="4.1.1" />
<package name="com.reconinstruments.myactivities"
versionCode="7047"
versionName="4.1.1" />
<package name="com.reconinstruments.nativetest"
versionCode="7047"
versionName="4.1.1" />
<package name="com.reconinstruments.offsetkeyboard"
versionCode="7047"
versionName="4.1.1" />
<package name="com.reconinstruments.passcodelock"
versionCode="7047"
versionName="4.1.1" />
<package name="com.reconinstruments.phone"
versionCode="7047"
versionName="4.1.1" />
<package name="com.reconinstruments.power"
versionCode="7047"
versionName="4.1.1" />
<package name="com.reconinstruments.quickactions"
versionCode="7047"
versionName="4.1.1" />
<package name="com.reconinstruments.socialsharing"
versionCode="7047"
versionName="4.1.1" />
<package name="com.reconinstruments.symptomchecker"
versionCode="7047"
versionName="4.1.1" />
<package name="com.reconinstruments.systemui"
versionCode="7047"
versionName="4.1.1" />
<package name="com.rxnetworks.rxnservicesxybrid"
versionCode="7047"
versionName="4.1.1" />
<package name="com.svox.pico"
versionCode="1"
versionName="1.0" />
<package name="jp.co.omronsoft.openwnn"
versionCode="16"
versionName="4.1.2-eng.linux-jenkins.20150414.021802" />
</installed-packages>

That would be awesome to see a google glass ROM port over. I would love to use these for navigation when I am on my motorcycle!
The forums that Recon has is dismal to say the least. Hopefully there will be more support as people get their hands on them.

Common someone please help us out!!

well, this is now available on some sites, but most of the major sites like amazon still have the Jet for preorder for July 1st.
Hopefully, when this gets in the hands of the mod gods, great things will happen.
alot of potential here, with the open sdk and all.

Just picked up a pair of Recon Snow2 goggles, which is fundamentally the same thing as Jet, according the build.props.
Would be great to get a section dedicated to Recon products.

has anyone tried rooting the Jet yet? I got my hands on one and would really like to be able to root it!

Hello everyone, I got the recon jet and I think the on board gps is not working. I'm hoping it's a software issue and not hardware. I'm new here and I'm no hacker but I can follow instructions. If any one can help me find the solution I'd greatly appreciate it.

I have my recon jet..... what to do with it the recon instruments site is dead. My recon jet asks for activation. is there any chance to use it somehow?

Anyone with an Idea?

You can still activate it on the website (it says password not accepted or smtp issue but it still works)
Dev part of the website is down so there is no way to access the sdk to develop any new app but basic usage is working.

Lost my recon jet adb drivers anyone happen to have them?

Did you get the ADB driver? I have a copy if you still need it.
More generally, with Recon now gone, and the JET/Snow2 products no longer supported, it makes sense to try make a useful custom image that can be community supported. Is anyone looking at this?

Activating Recon Jet in 2020
Angelbast said:
You can still activate it on the website (it says password not accepted or smtp issue but it still works)
Dev part of the website is down so there is no way to access the sdk to develop any new app but basic usage is working.
Click to expand...
Click to collapse
I am trying to activate Recon Jet but both the application and website do not work. The display on he glasses is stuck on the 'connect to a PC via USB and activate' screen. The device is detected by the operating system as an MTP device.
I tried to connect with the ADB driver included within the glasses and accessed using via MTP, one obtained from recon website (using the web archive) and ADB installed on Ubuntu via apt. None can detect the device connected via USB.
Does anyone know a way to get past the activation screen or to get ADB to connect to the device? Thank you.

dxxb2020 said:
Activating Recon Jet in 2020
I am trying to activate Recon Jet but both the application and website do not work. The display on he glasses is stuck on the 'connect to a PC via USB and activate' screen. The device is detected by the operating system as an MTP device.
I tried to connect with the ADB driver included within the glasses and accessed using via MTP, one obtained from recon website (using the web archive) and ADB installed on Ubuntu via apt. None can detect the device connected via USB.
Does anyone know a way to get past the activation screen or to get ADB to connect to the device? Thank you.
Click to expand...
Click to collapse
I have the same problem been trying for two days still can't get it to activate.

gpatech said:
Did you get the ADB driver? I have a copy if you still need it.
More generally, with Recon now gone, and the JET/Snow2 products no longer supported, it makes sense to try make a useful custom image that can be community supported. Is anyone looking at this?
Click to expand...
Click to collapse
Hi Can i try it to see if it works. link please

Just pulled out my old Snow2 goggles. Seem to boot up fine and are working. Anyone still using Jets or Snow2? Anyone doing anything interesting with them?

I am hoping to get some Reconjet glasses up and working when they arrive this week, for paragliding , to display flightdata. But it appears all the support has gone awol. I have been trying for ages to find an archive with the Recon SDK to let me do it but without luck. Can anyone assist?. I think the glass is basically the same as the snow2 , snow2 looks a better helmet frendly configuration for my application to be fair.
regards

PLease help. Does anyone have the Recon Uplink Desktop App for windows can seen to fine it anywhere.

Some how I factory reset my Snow2 to a very old version. Anyone know how to get back to the latest?