{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
!!!READ THE COMPLETE THREAD BEFORE REPORTING BUGS!!!
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.2.1 (JB), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
RULES
Code:
RULES:
* I doesnt include/execlude a package if you request me!
* Do not spam me with pm ... (Example: Pls add support for Beats :()
* Pls include speed or a2sd scrip, my answer: NO!
* This Rom will Be a CM Vanilla, and nothing else!
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android
community. It can be used without any need to have any Google application installed. Linked below is a package that has come from
another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also
slowly being open-sourced anyway.
Code:
For Moderators: This is my [URL="https://github.com/androidarmv6/android_kernel_samsung_msm7x27"]Kernel Source[/URL]! (Credits: Erikcas + Wayland_ACE)
Code:
[B]WORKING:[/B]
* RIL (Data/Phone/Sms/Mic)
* 3D Acceleration
* Bluetooth!
* WiFi
* Touchscreen
* Youtube LQ/HQ
* Lockscreen Widgets
* Browser
* Sound
* Project Butter
* BLN
* USB Tethering
* WiFi Tethering
* Full HW/SW Encoding/Decoding
* CM10(.1) Themes
* USB
* ADB
* NetworkLocation
* Video Player
* Camcorder
* Panorama
* GPS
* Proximity Sensor
* Offline Charging
[B]NOT WORKING:[/B]
* pls tell me immidientaly
[B]ISSUES:[/B]
* Audio routing issue: in some cases audio routes to handset instead of headset
Never ask for an ETA!!!
No permissions for SLIM Roms and Ports!
Code:
[URL="http://goo.im/devs/OldDroid/CM10.1Builds/beni/stable"]cm-10.1-RC0-beni.zip[/URL]
[B]MD5:[/B] 7001c8473ae289fe81157c5f15a9b6ee
Code:
[B]CREDITS:[/B]
* Wayland_ACE (armv6 patches)
* Me (humm CM10.1 for Fit?)
* All out of our Team (androidarmv6)
* My Friend and Team Member Gangster41
!NOTICE!
Code:
This Guide will be for private use only!
I do not want that you spam Development Section with UNOFFICIAL Nightlys ;)
we all can do, also with this guide xD
You need to install Ubuntu 11.04 x64 for this guide, so make sure you have it! (i know its outdated and isnt supported anymore by ubuntu,
but its simply perfect to build android 4.2.1
Ubuntu 11.04 x64 can be downloaded here
Install Android SDK
First of all: Download the Android SDK r21 for Linux x64
After you downloaded it: open your terminal ...
then type in (1Command = 1 Line!)
Code:
cd ~
mkdir android
tar -zxvf ~/Downloads/android-sdk_r21-linux.tgz
mv android-sdk-linux ~/android/sdk
Next we need to set up the sdk, to run "adb" command from any directory in terminal
Code:
sudo gedit .bashrc
Now add these lines to the bottom of the document:
Code:
export PATH=${PATH}:~/android/sdk/platform-tools
export PATH=${PATH}:~/android/sdk/tools
export PATH=${PATH}:~/android/bin
export PATH=${PATH}:~/bin
Next is, Set up the 51-android.rules, to get an adb connection from usb to ubuntu:
Code:
sudo gedit /etc/udev/rules.d/51-android.rules
Next, add these lines to the document that has been opened:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0502", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="413c", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="0489", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="091E", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="12d1", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="0482", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="1004", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="22b8", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="0955", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="10A9", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="04dd", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="0fce", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="19D2", MODE="0666"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="04e8", ATTRS{idProduct}=="6860", MODE="0666", OWNER="leob" #Galaxy Nexus
Gratulation, u finally setted up the Android SDK (Dont worry if Android SDK wont work [ADB]! it needs a package we download later )
Installing JAVA 6 (JDK)
type in terminal: (remember: 1 line = 1 command)
Code:
sudo add-apt-repository ppa:ferramroberto/java
sudo apt-get update
sudo apt-get install sun-java6-jdk
(TIP: Use to keyboard (Right-Left-Top-Bottom)-Button to press ok & yes)
Installing the SDK
type in terminal (remember 1 line one command!)
Code:
cd android
cd sdk
cd tools
./android
Now the SDK Manager will be opened!
tick the small box leftside of the "SDK Android Platform tools" Part!
After its done, click "install 1 package..."
Now a window gets opened, select "Accept All ..." and click "Install"
After its done, click "close"! gratulations you now have the SDK installed
Installing required depencies
Im devloping on a 64 Bit Platform of Ubuntu 11.04 (I recommend it : (copy and paste this completely in terminal & press ok ^^)
Code:
sudo apt-get install git-core gnupg flex bison gperf libsdl-dev libesd0-dev libwxgtk2.6-dev build-essential zip curl libncurses5-dev zlib1g-dev valgrind gcc-multilib g++-multilib libc6-dev-i386 lib32ncurses5-dev ia32-libs x11proto-core-dev libx11-dev lib32z-dev pngcrush schedtool
After thats done, you need to download an lib manually :/
The name of the lib is libreadline5-dev, download it from ubuntu directly
Download Link (Credits: Ubuntu)
After it has been downloaded, goto your downloads folder and double press it (Name: lib32readline5-dev_5.2-7build1_amd64.deb) ...
Simply tap "install in the opened Ubuntu Software-Center ^^
Syncing the Source
In terminal: (1 line = 1 command)
This is only to initialize the GIT commands to sync the repo later
Code:
cd ~
mkdir bin
Now i recommend to close all Terminals! (BEST: Reboot Ubuntu)
After its done, open Terminal once more and type in (1 line = 1 command):
Code:
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
chmod a+x ~/bin/repo
Now cd to android:
Code:
cd android
Then create a new directory:
Code:
mkdir cm-10.1
(just for example / but you can do it)
Now cd to your created directory:
Code:
cd cm-10.1
After that you can initialize the repo command! (1 line = 1 command!)
Code:
repo init -u git://github.com/androidarmv6/android.git -b cm-10.1
Now you can sync the repo to your local directory! (REMEMBER: This takes minutes [for me] and hours, days maybe for you!)
Code:
repo sync
Do the syncing step before, otherwise all will fail
To build CM10.1 for Fit simply do:
Code:
. build/envsetup.sh && brunch beni
I don't understand why are you making a thread with CM 10.1 , we have already a thread like this by erikas(sorry if the name is wrote wrong).
gabyif said:
I don't understand why are you making a thread with CM 10.1 , we have already a thread like this by erikas(sorry if the name is wrote wrong).
Click to expand...
Click to collapse
+1.......
can u explain the changes made by you??? and how's this build different from erickas build????
i really appreciate your hard work but plz make proper differenciation so that we all may know and will test it asap!!!
but first plz post complete changelog ± how's this build differ from erickas one???
fixed almost all things that were in erkcas build, like wifi hotspot wpa2-psk mode or improved performance, improved kernel, executed adb properly and correctly, fixed some other things and made all in all all a bit smoother, test yourself
@OP: Added Build Guide for cm-10.1
OldDroid said:
fixed almost all things that were in erkcas build, like wifi hotspot wpa2-psk mode or improved performance, improved kernel, executed adb properly and correctly, fixed some other things and made all in all all a bit smoother, test yourself
@OP: Added Build Guide for cm-10.1
Click to expand...
Click to collapse
and is this build resized properly? coz on erickas build there were few resizing problems like for eg that 1 no. on dailpad is not visible!!!
As long it is not kanged work.. therez nothing wrong of posting this cm10.1..
I've tried install this ROM with CWM 5. Before I go on wipe data/reset, wipe cashe partition and in Advanced, wipe dalvik cashe. I flash this ROM and for more than 7 minutes on display is white screenshot.
Not booting......only white screen.......!
Sent from my GT-S5670 using xda premium
AW: [DEV][ROM] CyanogenMod 10.1
ZmisiS said:
I've tried install this ROM with CWM 5. Before I go on wipe data/reset, wipe cashe partition and in Advanced, wipe dalvik cashe. I flash this ROM and for more than 7 minutes on display is white screenshot.
Click to expand...
Click to collapse
you formatted system and retaken in the battery?
Sent from my GT-P1000 using xda app-developers app
OldDroid said:
you formatted system and retaken in the battery?
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
I've not formatted system. What is retaken in the battery.
Please instructions for install this ROM.
ZmisiS said:
I've not formatted system. What is retaken in the battery.
Click to expand...
Click to collapse
retaken = remove battery after flashing the rom
pavel73 said:
retaken = remove battery after flashing the rom
Click to expand...
Click to collapse
O.K. I now understand.
ZmisiS said:
O.K. I now understand.
Click to expand...
Click to collapse
tell me if is boot please :-?
pavel73 said:
tell me if is boot please :-?
Click to expand...
Click to collapse
Not.
White Screen - Not Booting
AW: [DEV][ROM] CyanogenMod 10.1
Kernel error? Can someone post a logcat ???
Sent from my GT-S5660 using xda app-developers app
OldDroid said:
Kernel error? Can someone post a logcat ???
Sent from my GT-S5660 using xda app-developers app
Click to expand...
Click to collapse
Also pl share the steps to install this rom as we have ended up with white screen..
wat abt the camera?? is it working completely?? pics @ 5mp, cam recording(hw many fps??), video playback(smooth)??
thanx a lot for ur valuable effort. :good:
Rohit02 said:
Also pl share the steps to install this rom as we have ended up with white screen..
wat abt the camera?? is it working completely?? pics @ 5mp, cam recording(hw many fps??), video playback(smooth)??
thanx a lot for ur valuable effort. :good:
Click to expand...
Click to collapse
Bro which part of not booting didn't you understand..
if possible give the dev a logcat
@ OldDroid Good job
Related
Hi @all,
This is a unofficial ROM of gingerbread for use in LG-P500 mobile devices.
NO Support by LG and after flashing you can't connect with this ROM to the LG PC-Suite for updates. If you want update a original firmware, u have to flash
a original ROM deployed by LG.
Please, do not ask when i release a build. If a build is ready to test, i upload the ROM and you'll see a download link in THIS post.
For general questions, please look here
Current state of Gingerbread ROM by andy572 (Version 2.3.4 Codename Phoenix)
previous rom for download based on CM7 has been removed, i dont support the latest rom from now.
Latest Changes
* light text color bug fixed
* gallery3D app: pinch to zoom fixed
* gallery3D app: loading a bit slow - fixed
* kernel: wifi not working, kernel module is broken - fixed
* kernel: kernel doesnt support clear ram feature in settings - fixed
* expanded statusbar bugs fixed
* new lockscreen implemented
* modified gps.conf
* modified apns-conf.xml
* network provider search fixed
* contact import from sim card fixed
* crash in contacts app fixed (app was FC'ing when swipe over the tabs on the top)
Very known bugs:
- If no default ringtone is choosen in settings menu, android choose one for u and change this randomly
- FM Radio and USB-/WiFi theasering not working (maybe with 3rd party apps)
- strong pixelation/color banding issues in wallpapers and picture gallery app
- Airplane-, Vibrate modes and audio volume settings change gets not detected in expanded statusbar view toggles
- rom is only working with old baseband and clockwork mod recovery
INSTALL
1.) Install ClockwordMod Recovery, old AmonRA isnt supported anymore.
2.) Flash the ROM file
3.) If you're coming from any other than THIS rom, YOU NEED TO DO A COMPLETE WIPE before reboot!!!
Download
http://www.phoenix-android.com (Android 2.3.4 Phoenix)
Further information:
The new rom is based on CodeAurora's Android Gingerbread, CM7 and android open source code (2.3.4 and 2.3.5).
Many thanks to franco for the cool kernel tips and the funny after work days
Sources
CodeAurora
Phoenix-Android
Whats next coming?
* Electron Beam feature is causing black screen: FIXED (Feature permanent disabled)
* allow swipe in contacts/phone app on call log
* optimize webkit code
* modify music app
* modify and bugfix launcher app again
* modify and bugfix camera app
* modify and bugfix fm radio app
* fix bluetooth audio
Greets from Munich/Germany
Andy
ooh, nice to have someone interested of doing that!
It's nice to have some people interesting in developing a gingerbread custom rom for our optimus P500. I would help if i knew what you need. I don't know what you are talking about so... Sorry
Hi,
i'm talking about to bring up a gingerbread installtion to our mobile.
All what i have is a ready compiled android 2.3.1 without a kernel and without LG addons, there are (possibly) required to boot the phone to gingerbread.
i've tryed yesterday and today to boot with a mix from froyo, but this does not works - even if i disabled some hardware, the system needs some information from modules build by LG - it boots only when gingerbread is flashed over froyo without a complete wipe, nothing but the launcher is working
After a wipe, the system loops around while booting and bringe lot of permission errors in logcat.
Did you look in this thread : http://forum.xda-developers.com/showthread.php?t=901247 ?
There is a kernel and it could help you
Thank you dark-k, but i don't search a kernel but peoples they are interested to help building
i am not a dev but i know how linux works and i got a p500 so if u need help u can count with me buddy.
andy572 said:
All what i have is a ready compiled android 2.3.1 without a kernel and without LG addons, there are (possibly) required to boot the phone to gingerbread.
Click to expand...
Click to collapse
hi can you tell me how to i can compile a clean complete version of android without kernel?
thanks
How about this kernel? The dev says it's supposed to be compatible with any rom.
http://forum.xda-developers.com/showthread.php?t=866774&page=9
How to compile android 2.3.3:
1.) If you use a windows system, install VirtualBox 4.x and than Ubuntu 10.10 Desktop Edition as guest OS (its the smallest version and is enough for compilings)
Attention: Android compiling requires lot of free space.
My Ubuntu virtual harddrives size is 30GB, partitions are 10GB, 512MB (SWAP) and 19.5GB. During install, mount the 10GB partition on /, the 19.5GB partition on /home.
1.1) Prepare user
to have easier system access, we act as root - so set a new password to root and change the current user:
Code:
sudo passwd root
Enter the new password to root and change user:
Code:
su -
1.2) change the shell to bash
Ubuntu 10.10 has a symlink in /bin/sh - this links not to the bash which is required by android to compile:
Code:
rm /bin/sh && ln -s /bin/bash /bin/sh
2.) Install required compilers and software:
Code:
apt-get install build-essential automake autoconf binutils libncurses5-dev xorg-dev git-core gnupg flex bison gperf zlib1g-dev
3.) Prepare home directory
Code:
mkdir -p /home/android/bin
cd /home/android
3.) Install JAVA
- Download latest java-1.6 (it's required by gingerbread to build java apps) from Oracle site:
https://cds.sun.com/is-bin/[email protected]_Developer and select Linux (not Linux64!!!)
Copy file jdk-6u23-linux-i586.bin to /home/android and exec the file:
Code:
./jdk-6u23-linux-i586.bin
and type "yes" to accept the license.
After install, move the new directory to /usr/lib/jvm:
Code:
mkdir -p /usr/lib/jvm && mv jdk1.6.0_23 /usr/lib/jvm
rm -rf jdk1.6.0_23
4.) Adopt JVM and user's bin path to all users env:
Code:
echo 'export PATH=$PATH:/home/android/bin:/usr/lib/jvm/jdk1.6.0_23/bin' >> /etc/profile
echo 'export JAVA_HOME=/usr/lib/jvm/jdk1.6.0_23' >> /etc/profile
echo 'export ANDROID_JAVA_HOME=$JAVA_HOME' >> /etc/profile
source /etc/profile
5.) Download Android 2.3.3
Code:
curl http://android.git.kernel.org/repo > bin/repo
chmod a+x bin/repo
repo init -u git://github.com/CyanogenMod/android.git -b gingerbread
repo sync
6.) Compiling Android 2.3.3
To build a final release on a 32bit machine, we must modify some files and use the target option "user" (default is "eng", which is only a debug build for the emulator).
Attention
following code must be run in root of your repo:
Code:
source build/envsetup.sh
lunch thunderg-user
make -j2
After a build time of 1-2 hours, we have in folder out/target/product/generic our images: system.img,ramdisk.img and userdata.img and in folder prebuild/linux-x86/toolchain our android arm-eabi to compile kernel and so on.
If any goes wrong, please post here - it's possible that i have forgot to post some...
awesome walkthrough
andy572 said:
How to compile android 2.3.1:
1.) If you use a windows system, install VirtualBox 4.x and than Ubuntu 10.10 Desktop Edition as guest OS (its the smallest version and is enough for compilings)
Attention: Android compiling requires lot of free space.
My Ubuntu virtual harddrives size is 30GB, partitions are 10GB, 512MB (SWAP) and 19.5GB. During install, mount the 10GB partition on /, the 19.5GB partition on /home.
1.1) Prepare user
to have easier system access, we act as root - so set a new password to root and change the current user:
Code:
sudo passwd root
Enter the new password to root and change user:
Code:
su -
1.2) change the shell to bash
Ubuntu 10.10 has a symlink in /bin/sh - this links not to the bash which is required by android to compile:
Code:
rm /bin/sh && ln -s /bin/bash /bin/sh
2.) Install required compilers and software:
Code:
apt-get install build-essential automake autoconf binutils libncurses5-dev xorg-dev git-core gnupg flex bison gperf zlib1g-dev
3.) Prepare home directory
Code:
mkdir -p /home/android/bin
cd /home/android
3.) Install JAVA
- Download latest java-1.6 (it's required by gingerbread to build java apps) from Oracle site:
https://cds.sun.com/is-bin/[email protected]_Developer and select Linux (not Linux64!!!)
Copy file jdk-6u23-linux-i586.bin to /home/android and exec the file:
Code:
./jdk-6u23-linux-i586.bin
and type "yes" to accept the license.
After install, move the new directory to /usr/lib/jvm:
Code:
mkdir -p /usr/lib/jvm && mv jdk1.6.0_23 /usr/lib/jvm
rm -rf jdk1.6.0_23
4.) Adopt JVM and user's bin path to all users env:
Code:
echo 'export PATH=$PATH:/home/android/bin:/usr/lib/jvm/jdk1.6.0_23/bin' >> /etc/profile
echo 'export JAVA_HOME=/usr/lib/jvm/jdk1.6.0_23' >> /etc/profile
echo 'export ANDROID_JAVA_HOME=$JAVA_HOME' >> /etc/profile
source /etc/profile
5.) Download Android 2.3.1
Code:
curl http://android.git.kernel.org/repo > bin/repo
chmod a+x bin/repo
repo init -u git://android.git.kernel.org/platform/manifest.git -b gingerbread
repo sync
6.) Compiling Android 2.3.1
To build a final release on a 32bit machine, we must modify some files and use the target option "user" (default is "eng", which is only a debug build for the emulator):
Code:
source build/envsetup.sh
$find . -name '*.mk' | xargs sed -i 's/-m64//g'
export TARGET_BUILD_VARIANT=user
lunch
make
After a build time of 3 hours, we have in folder out/target/product/generic our images: system.img,ramdisk.img and userdata.img and in folder prebuild/linux-x86/toolchain our android arm-eabi to compile kernel and so on.
If any goes wrong, please post here - it's possible that i have forgot to post some...
Click to expand...
Click to collapse
gonna start workin later tonight gonna upload it soon.
Problems ... problems ... more problems
Today, i've merged the LG P500 Froyo source with gingerbread to get the required LG libraries and bin's, but i get over and over compiler errors.
LG didn't provide the complete source to froyo, so many definitions in C-Header files are missig
I've fixed many of these errors, but the end result is a linker error because of missing libraries there are not provided in source code.
I'll try to compile a froyo to test out if this errors only comes with gingerbread.
...Where is my time ????
I have succesfully compile and boot CyanogenMod 7. But everything slow, 3d driver don't work (same as with Legend). Tried to use N1 driver but it crashes, seems it compiled as armv7.
mik_os said:
I have succesfully compile and boot CyanogenMod 7. But everything slow, 3d driver don't work (same as with Legend). Tried to use N1 driver but it crashes, seems it compiled as armv7.
Click to expand...
Click to collapse
Can you share with us??
MAybe we can help you to boost the system.
i didnt have much sleep last night alot of trouble gonna reinstall windows 7 then repack the img gonna post it later its 9:33 here in germany
Du sollst doch Nachts schlafen und nicht am PC sitzen *lol*
FROYO doesn't compile - same problem as to import LG FROYO sources to Gingerbread.
Error:
make: *** No rule to make target `out/target/product/generic/obj/STATIC_LIBRARIES/liblgdrmexpat_intermediates/liblgdrmexpat.a', needed by `out/target/product/generic/obj/SHARED_LIBRARIES/liblgdrmwbxml_intermediates/LINKED/liblgdrmwbxml.so'. Stop.
upd: wifi work
You can find sources at
Code:
https://github.com/mik9
BUT it's dirty (based on htc legend) and not full. I continue work.
Awesome job, you can count on me for any help you need, lol like tester or something
Sent from my LG-P500 using XDA App
<BACON>
This will Allow you to build CM7-Nightlies or "Kangs" at any time you please.
Compatible with Ubuntu or rpm distros
It's a bash/sh script for automation, as simple as a double click.
it's downloading and installing all files/repos/sdk/adb/fastboot and compiles. (If you already have some of this installed, it prompts before installing)
-------
Please test it, and report bugs here (files attached)
No donations wanted, just click that THANKS button
Github: https://github.com/nicandris/CM-from-scratch
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
-------
new build.sh menu
just unzip on ubuntu/linux and run ./douchebuild.sh
if ./douchebuild.sh is not recognized as an executable, just
Code:
sudo chmod 775 douchebuild.sh
You will be asked for sudo pass (since you edit repos and add adb in bin) and some info for git.
after completing you can always create a fresh build from the Desktop shortcut build.sh
ofcourse i don't take any credits for cm, all credit goes to cyanogen and teamdouche. the script is just a shell compilation of the cm wiki.
</BACON>
Reserved
If you want to set only udev try this script
View attachment udev.zip
unzip and
Code:
chmod 755 udev.sh
-----
If you already used the main script and want to have the new build.sh menu, run this script
View attachment buildshcreator.zip
-----
if you don't want all the files for all the devices to be synced, follow this!
Reserved
CHANGELOG
v1
Supporting only Nexus One (initial release)
v2
Supporting all cyanogenmod official devices. Added menu selection for device
v2.0.1
Fixed some nohup issues. Changed some code lines. fixed an if statement
v2.0.2
HD2/Leo support added
v2.1
Various Bugfixes
New build menu
v2.2
Few bug fixes
Some name changes
MORE options in build.sh!!
v2.3
Minor Bug Fixes
Added new devices:
Motorola Cliq XT
LG G2x
LG Optimus 2X
Samsung Captivate
Samsung Vibrant
Barnes & Noble - Nook Color support
Added udev support for Nook Color
v2.3.2
Fixed selection list
Added HTC Incredible 2 Support
v2.4.1
Added Samsung Galaxy S II and Fascinate support
Added Motorola Droid X support
udevs fixed
v2.4.3
Added HTC Tattoo
v2.5.1
Updated Android SDK to v13
Forced repo to sync from github and not from kernel.org (since kernel.org is down for maintenance)
Bugfix
v2.5.2
Added Nexus S 4G
v2.5.3/2.5.4
minor bugfix x4
changed repo fetch URL
v2.7.1
RPM compatibility
Small bugfix
nicandris said:
guys i made a small shell script for automation. tried it twice on clean ubuntu builds and it works just fine!
it's downloading and installing all files/repos/sdk/adb/fastboot and compiles. if anyone has a clean installation (or has the time to create a new vbox to test it try it)
http://dl.dropbox.com/u/6751304/androidmake
just unzip on ubuntu/linux and run ./androidmake
if you are on x64 run this first:
Code:
sudo apt-get update && sudo apt-get install git-core gnupg flex bison gperf build-essential zip curl zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 lib32ncurses5-dev ia32-libs x11proto-core-dev libx11-dev lib32readline5-dev lib32z-dev sun-java6-jdk gitg qt3-dev-tools libqt3-mt-dev eclipse valgrind pngcrush && sudo update-java-alternatives -s java-6-sun
after completing you can always create a fresh build from the Desktop shortcut build.sh
Click to expand...
Click to collapse
Thanks. this should come in handy since I just reinstalled my linux desktop. I'll try it out later tonight.
nicandris said:
guys i made a small shell script for automation. tried it twice on clean ubuntu builds and it works just fine!
it's downloading and installing all files/repos/sdk/adb/fastboot and compiles. if anyone has a clean installation (or has the time to create a new vbox to test it try it)
http://dl.dropbox.com/u/6751304/androidmake
just unzip on ubuntu/linux and run ./androidmake
if you are on x64 run this first:
Code:
sudo apt-get update && sudo apt-get install git-core gnupg flex bison gperf build-essential zip curl zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 lib32ncurses5-dev ia32-libs x11proto-core-dev libx11-dev lib32readline5-dev lib32z-dev sun-java6-jdk gitg qt3-dev-tools libqt3-mt-dev eclipse valgrind pngcrush && sudo update-java-alternatives -s java-6-sun
after completing you can always create a fresh build from the Desktop shortcut build.sh
ofcourse i don't take any credits for cm, all credit goes to cyanogen and teamdouche. the script is just a shell compilation of the cm wiki.
I was planning to do a GUI or text-based version with more options (more phone support etc) but i don't have the time. if anyone wants to do it the script is there have fun
Click to expand...
Click to collapse
Thanks. I'll give it a shot tonight.
can´t test it anymore, as I got all setup..but for future, just great!
rori~ said:
can´t test it anymore, as I got all setup..but for future, just great!
Click to expand...
Click to collapse
well take the ./build.sh only it's helpfull (for me that i'm bored to type the make bacon)
Excellent work, and thanks for sharing. This will be very useful for others. I modified the title and stickied this.
Sounds Good i'm on testing...
thanx for sticking this up
guys please test and if you find anyth wrong msg me to check it out.
After 3 hours i have a compiled Kang-update.zip !!! Thanks
Sweet... great job... nice to have some shortcuts... now I'm gonna use this to schedule sync and build... thanks a million
Trying on Debian right now (commented out the sources update ) Will post back with results.
glad to see that this is helping you guys. if anyone has another phone (except N1) it would be really helpful to send me the proprietary files so i can make this for other devices also (i can do it without but it's easier for users if i have the files) i can explain how to obtain them.
Is this working for you on a x86*nix build? I get a warning when I start building that only x64 is supported.
electrostat said:
Is this working for you on a x86*nix build? I get a warning when I start building that only x64 is supported.
Click to expand...
Click to collapse
i tried it twice on a x86 and it was fine. AOSP or tmobile's theme engine is not compiling on x86 but cm7 is. i think i twitted abt this a couple of days ago.
http://twitpic.com/43mezo
nicandris said:
i tried it twice on a x86 and it was fine. AOSP or tmobile's theme engine is not compiling on x86 but cm7 is. i think i twitted abt this a couple of days ago.
http://twitpic.com/43mezo
Click to expand...
Click to collapse
Sweet. It's building right now, don't care much about tmobile's theme anyway
all works perfectly on ubuntu x64 but one thing: how can i build always latest nightly? repo ar different? i must change this? git://github.com/CyanogenMod/android.git -b gingerbread
what is the repo for latest merge? thank you very much thi topic is fantastic
drigerott said:
all works perfectly on ubuntu x64 but one thing: how can i build always latest nightly? repo ar different? i must change this? git://github.com/CyanogenMod/android.git -b gingerbread
what is the repo for latest merge? thank you very much thi topic is fantastic
Click to expand...
Click to collapse
well this is the latest merge just use the buils.sh shortcut from your desktop
mmmm but the latest merge aren't on rom (like profiles on power down screen etc.)
with this repo we build rc1? or nightly? ^_^
and... build.sh doesn't work properly... i modified like this:
cd ~/android/system/;
repo init -u git://github.com/CyanogenMod/android.git -b gingerbread;
repo sync;
cd;
cd ~/android/system/vendor/cyanogen/;
./get-rommanager;
cd ~/android/system/;
. build/envsetup.sh;
lunch cyanogen_passion-eng;
make -j`grep 'processor' /proc/cpuinfo | wc -l` bacon;
cp ~/android/system/out/target/product/passion/update*.zip ~/Scrivania/update-cm7-N1-$(date +%d_%m-%H.%M.%S).zip
echo -e [=-This is an ALPHA-test version of whatever this is-=];
Click to expand...
Click to collapse
instead of
repo sync ;
cp ./vendor/cyanogen/products/cyanogen_passion.mk ./buildspec.mk;
. build/envsetup.sh;
lunch cyanogen_passion-eng;
make -j`grep 'processor' /proc/cpuinfo | wc -l` bacon;
cp ~/android/system/out/target/product/passion/update*.zip ~/Desktop/update-cm7-N1-$(date +%d_%m-%H.%M.%S).zip
Click to expand...
Click to collapse
is correct? ^^
thanks for you're replay)
Compiling CM7 on the HTC Glacier (T-Mobile MyTouch 4g)
I was trying to learn how to compile CM7 from source on my Glacier as practice for when my new Nexus 4 arrives next month. I originally followed a guide by Sykopompos but it's severely out of date (and didn't work off the bat for me). I figured I'd turn this into a how-to to help anyone out with this. I'm assuming that with the proper blobs you can also use this to compile CM9 and CM10 (I will be testing this in the next few days).
Disclaimer: if you FUBUR your PC, I am not responsible, you do this at your own risk. You SHOULDN'T be able to mess up your PC if you go the VirtualBox route, however there is always a risk of bricking your device. (Although I'd assume if things went tits up you could just reflash a PD15IMG.zip and you'd just need to re-root your device.)
I used Ubuntu 10.04 LTS for this, feel try to with another version (I'd be weary past 11.10 as 12.04 and beyond aren't officially supported by AOSP.) I'll highlight any problem areas you need to be careful of.
This is based off of my experience compiling from source. I may be taking the long way around things, but it works. I am gearing this to the people new to android development (I've just recently gotten into it myself). I will be giving you things you need to copy and paste (for the most part) to make it easier.
This will cover setting up and compiling the source for a working rom, and the basics of custom kernel creation.
You MUST use 64-bit Ubuntu for gingerbread and later!
You can either install Ubuntu on a dedicated partition (Wubi doesn't give you enough space though, just FYI) or use VirtualBox(). If you go the VirtualBox route, you need to install the extension pack (Located on the same page as the download) for later steps to work.
Here are my recommendations (I used the VirtualBox route):
Disk space: 100gb is a good amount. Between downloading the source and my first build, I'm using 24.6gb (according to windows).
Ram: I gave the VM 4gb of my 8gb ram. You can use more or less, but I'd think that if you have less than 4gb of ram allocated, use a 8-12gb swap file just in case (you may not need it, I built with no problems with 4gb of ram and no swap)
Processor: I have a new Ivy Bridge processor that supports virtualization (If you have a K designation Core series (IE Core i5-2500K you don't support virtualization and your build will be... much slower). I gave VirtualBox 3 of my 4 cores, feel free to adjust as necessary (just leave at least one for your main system)
At this point, I'm trusting that you've successfully installed Ubuntu 10.04 64-bit LTS along with the VirtualBox additions (if you went the VirtualBox route). Make sure to run sudo apt-get update . (don't upgrade to 12.04 if it asks)
Thanks to Dragonswithin for updating me about OpenJDK working.
Installing Necessary packages
There are two packages that need to be handled differently from just a simple apt-get install. The first is git-core (the version in the repositories are extremely old and refuse to work correctly with this). The second is Sun-jdk6
First, do the following to add the source for the correct version of git-core.
Code:
sudo add-apt-repository ppa:git-core/ppa
sudo apt-get update
Enter your password when prompted.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Install the following
Code:
sudo apt-get install git-core gnupg flex bison gperf libsdl-dev libesd0-dev libwxgtk2.6-dev build-essential zip curl libncurses5-dev zlib1g-dev gitg qt3-dev-tools libqt3-mt-dev eclipse valgrind zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 gedit lib32ncurses5-dev ia32-libs x11proto-core-dev libx11-dev lib32readline5-dev lib32z-dev gitg pngcrush wput openjdk-6-jre
Hit enter when it asks if you want to proceed
Provided everything went smoothly above, you now have all the correct packages installed!
Next step: REPO
Repo is the script provided by Google that makes it easier to deal with Android source via Git (at least what I gather from it).
The following is the code to get it setup.
Code:
cd ~
mkdir -p bin
export PATH=${PATH}:~/bin
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
chmod a+x ~/bin/repo
doing cd ~/ is an easy way to bring you back to your home folder (IE /home/matada/)
mkdir creates a folder named bin in which we store the repo script.
Export PATH allows us to easily call repo by itself instead of having to use /home/matada/bin/repo
finally, chmod +a gives us everyone access to the repo file, while +x makes it executable (like a .exe or .msi file on windows). Congrats, Two things down!
Setting up the Android SDK
As of this writing you can go one of two ways. Either manually download the SDK and select Linux(i386), extract it then move it to your home folder (/home/username/) and rename it androidsdk. Or you can just copy and paste the following (this works as of the current release of the SDK, I will try and remember to keep this updated, but I can't promise much)
Code:
cd ~/Downloads
wget http://dl.google.com/android/android-sdk_r21-linux.tgz
tar -xvzf android-sdk_r21-linux.tgz
mv android-sdk-linux ~/androidsdk
That's the SDK downloaded, now to install the packages we need in it.
Code:
~/androidsdk/tools/android
Select under tools:
Android SDK Tools (should be installed by default)
Android SDK Platform-Tools
(I'm not sure if the following is required or not, I did it to be on the safe side). Scroll down to Android 2.3.3 (API 10) and select
SDK Platform
Samples for SDK
and Google APIs
Hit install 4 packages, accept the terms and let it download and install (might take a little while based on your network speed) Once that is complete exit out.
The last step for the SDK is to add the following to your .bashrc (add the three lines to the top of the text)
Code:
gedit .bashrc
Then add:
#AndroidDev PATH
export PATH=${PATH}:~/androidsdk/tools
export PATH=${PATH}:~/androidsdk/platform-tools
Restart your system (the VM or your full linux install)
Congrats! Now ADB should be setup correctly, now for a quick test. Plug your phone into your PC. If you're using the VirtualBox way, go up to devices → USB devices and select T-Mobile MyTouch 4g.
Reopen your terminal and type in lsusb and you should see the following pop up:
Next enter
Code:
sudo gedit /etc/udev/rules.d/51-android.rules
and paste in the following:
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0502", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="12d1", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1004", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="22b8", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0fce", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0489", MODE="0666"
SUBSYSTEM==”usb”, ATTRS{idVendor}==”18d1″, SYMLINK+=”android_adb”, MODE=”0666″
SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
Then Save and exit
Now is as good of a time as any to keep a backup of your /system/ partition (and a good way to see if your androidSDK is setup correctly)
First enable development on your phone. For gingerbread it’s under the applications -> development -> then press Android Development.
Code:
cd ~/
mkdir stock
cd stock
adb pull /system/ ~/stock/
When it's complete:
Congrats, if that worked correctly the system setup is done! Time to download the source code!
Downloading the Source
the Cyanogenmod source is pretty large (my VM was using 15gb by the time it was finished, with another 1gb for the kernel source), so don’t use this if you tether your internet or you’ll be dead before you even start.
Here we go! (At this point you can build for Jellybean or ICS (just replace gingerbread with either jellybean or ICS (or ICS-Release)
Code:
cd ~/
mkdir -p android/source
cd ~/android/source
repo init -u git://github.com/CyanogenMod/android.git -b gingerbread
It’s going to ask for your name and e-mail (you can just hit enter twice to skip it), and then hit Y, enter and then Y and then enter again at the color selection. Your folder is now setup.
You MAY have to (out of the four times I’ve done this part I’ve had it happen once) manually specify your e-mail and name. If so:
Code:
git config --global user.email “[email protected]”
git config --global user.name “your name”
(it will error out saying “unable to auto-detect e-mail address" if this is the case)
Repo is the file we downloaded from Google earlier, it now sets up the source folder to clone the CyanogenMod repository, which we’re about to do now.
Code:
repo sync -j2
This starts the download from the CyanogenMod repository. This totally depends on your internet, and may take from 30-minutes to 12 hours. It’s around 5gb to download. At this point go get something to eat / drink, browse XDA Developers or Reddit and we’ll be back when it’s finished. (I happened to watch tonight’s episode of Walking Dead as a nice break )
And X amount of time later We’re back! (it was about an hour and a half for my connection)
Now to get into the nitty gritty of making it work for our Glacier. Unfortunately CM has taken out the easy button for Gingerbread so we need to do things by hand. No big deal, I’ll explain everything here.
The steps SHOULD be the same no matter if you do Gingerbread or ICS or even Jellybean, just adjust as needed (the repositories I include have Jellybean and ICS included)
First step, Include the Glacier in the vendorsetup for when we compile
Code:
gedit ~/android/source/vendor/cyanogen/vendorsetup.sh
Add in:
add_lunch_combo cyanogen_glacier-eng
Save and exit
Next we need to tell git where to find the files we need for the glacier. Again, change gingerbread to ICS or Jellybean (I don’t know the correct setting for the Kernel though) if you want to compile sometihng else.
This next step you’re going to have to do manually as it resides in a hidden folder.
Open your home folder then navigate to ~/android/system/ then hit Control+H to show hidden folders. Find .repo and when in the folder right click, create document -> empty File and name it local_manifest.xml (case sensitive) right click and open with gedit and:
Add in
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_htc_glacier" path="device/htc/glacier" revision="gingerbread" />
<project name="TheMuppets/proprietary_vendor_htc" path="vendor/htc" revision="gingerbread" />
<project name="CyanogenMod/htc-kernel-msm7x30" path="device/htc/kernel-msm7x30" revision="android-msm-2.6.35" />
</manifest>
Save and quit
Final modification that needs to be done
Code:
gedit ~/android/source/device/htc/glacier/glacier.mk
Line 33: change
“device/htc/vision/ueventd.vision.rc:root/ueventd.glacier.rc”
to
Code:
“device/htc/glacier/ueventd.glacier.rc:root/ueventd.glacier.rc”
(check the screenshot if you need help)
Save and quit
Next do repo sync again
Code:
cd ~/android/source/
repo sync
Next it’s time to get RomManager. You’re in the home stretch of compiling CM7. Only a few more steps!
Code:
cd ~/android/source/vendor/cyanogen
bash get-rommanager
Guess what, Time to compile! If you managed to get this far congratulations! (side note I wish I had a guide to get me this far!)
Alright. last few lines of code and you should be home free.
Code:
source /build/envsetup.sh
lunch cyanogen_glacier-eng
make clean
make bacon -j*
Before make bacon
*(If you want to speed the compile up, you can set -j to however many cores you have available to the VM or on your processor (I gave VirtualBox 3) so I would use -j3. If you only have a single core just omit the -j)
If you compiled successfully you should have a nice shiny cm7.zip sitting on your PC that’s ready to flash! If you just want to compile your own version of CM you’re done! Copy the resulting zip to your sdcard, and flash it in Clockworkmod or RomManager! The directory where the file is located will be displayed when the compile finishes successfully. Now! Stay tuned if you want your own kernel too!
Finished!
Remember to flash the correct gapps for your phone!
Making a custom Kernel
Ok, you made it this far, why not go for the full monty right? I don’t know much about making custom kernels (short of making them compile). Here’s a guide I found on a quick search. it rehashes part of what I’ve said here. (Although I didn’t use that source to make this guide. (Look below for my sources)
I’ll keep giving you the step by step here (I’m just going to skip the explanations of what stuff does), just incase you’re still not comfortable being let loose yet.
Code:
cd ~/android
mkdir kernel
cd kernel
git clone git://github.com/CyanogenMod/htc-kernel-msm7x30.git
cd htc-kernel-msm7x30
export CROSS_COMPILE=~/android/source//prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-
export ARCH=arm
make xconfig
At this point you should eventually have a window pop up that looks like:
all you have to do is go to file load and navigate to ~/android/source/kernel/htc-kernel-msm7x30/arch/arm/configs and select “cyanogen_msm7230_defconfig” and hit load. then save and exit. You can tinker around with stuff BUT you can easily make your device freeze at the mytouch logo (you’d need to figure out what went wrong then reflash the kernel (or the rom when you kernel to work correctly).
Last step for compiling. (so anticlimatic)
make -j (if you set -j to something when you compiled CM7 feel free to use it again, if you didn’t omit the -j) Hit enter and you should wind up with a custom kernel and wifi module.
I ignored the wifi module since the same version was already in the sources on CM7. you will need to add it for CM9 and CM10).
The kernel is located at ~/android/source/kernel/htc-kernel-msm7x30/arch/arm/boot/ and wifi is located at ~/android/source/kernel/htc-kernel-msm7x30/drivers/net/wireless/bcm4329/
BE SURE TO BACK UP THE ORIGINALS (either copy them out to a safe spot, or rename them!)
you can either fastboot the kernel (I don’t know how to do it correctly yet so I will skip adding it for now) or put in the CM7 source at /android/system/device/htc/msm7x30-common/msm7230/
Rename zImage to kernel.
Wifi will also go to ~/android/system/device/htc/msm7x30-common/msm7230
In the end it should look like:
at this point do the following to recompile with the new kernel (and possibly wifi)
Code:
source ./build/envsetup.sh
lunch cyanogen_glacier-eng
make clean
make bacon -j (you know what to do now)
When it completes successfully, copy it to your SD card and flash it same as before and you’re set.
[URL=http://i.imgur.com/mfTxyh][IMG]http://i.imgur.com/mfTxyh.png[/IMG][/URL]
And finally (my rom works perfectly and is pretty quick. I'm impressed and satisfied)
[img]http://i.imgur.com/oMblE.png[/img]
I hope this will help someone, as it was a good learning experience for me.
The sources I used were:
Guide to Compiling Posted by Sykopompos . This gave some of the specifics of what I needed to do for the glacier (not all of it sadly)
Compiling from source GSM HTC Desire build page (Out of date but was a good launching off point.)
I owe a lot to the #cyanogenmod-dev IRC channel on Freenode. More specifically to the user Asturel who put up with my constant questions for getting it to work. (Just because he helped me doesn't mean he'll help y'all)
If you need any help feel free to post here, or PM me.
You can also DM me on twitter @zoeyalbini if you need some immediate assistance.
You can also find me (and a lot of other great developers) over on #cyanogenmod-dev if you want to connect with other devs. They seem to accept me fine!
And worst comes to worse you can e-mail me at matada89 (AT) gmail
Thanks for reading!
Thanks for the time you spent creating this guide.
Sent from my LG E960
GEEEEZZZZZ!!How long did it take you to post all of this!talking about filling up a thread from the start!!HAHA JK thanks for the info!alot to read,but probably worth it !again thanx..
[email protected] said:
GEEEEZZZZZ!!How long did it take you to post all of this!talking about filling up a thread from the start!!HAHA JK thanks for the info!alot to read,but probably worth it !again thanx..
Click to expand...
Click to collapse
To figure out everything to do this took about 6 hours. Writing the guide took about four hours. Checking line by line and getting pics (I compiled the rom using only the things I had written) . Posting it here took like 3 hours only because of the 10 post requirement. And doing pictures.. and formatting and other stuff. I'm not done yet (going to Try and compile both CM9 and CM10 following this guide. I'm in bed now as it's 5am.
Sent from my HTC Glacier using xda premium
Alright, since I'm an eager beaver (Or stupid as hell). I'm going to try and compile CM9 and CM10 and see what (if anything drastic) needs to be changed. Will report with a how-to later if it works.
Update: I Seem (almost done compiling) to have CM9 setup correctly, but haven't quite figured out making the Kernel.. Progress. Also, I may have something BIG to release on Christmas.... I'm excited!
Edit: CM9 compiled correctly and it currently working on first boot (Optimizing applications) Cool!
Great guide but most of it won't work on cm9 and definitely not cm10. Great effort though
THEindian said:
Great guide but most of it won't work on cm9 and definitely not cm10. Great effort though
Click to expand...
Click to collapse
Yeah I'm seeing that. I'll figure something out, might have to do a separate tutorial for 9 and 10. Hit a snag right now with a bootloop.
matada said:
Yeah I'm seeing that. I'll figure something out, might have to do a separate tutorial for 9 and 10. Hit a snag right now with a bootloop.
Click to expand...
Click to collapse
I'll be looking forward to the CM10 tutorial, when i was trying to compile it, i had to mash a bunch of guides together, then i realized that my computer wasn't strong enough to build android lol
---------- Post added at 05:33 PM ---------- Previous post was at 05:30 PM ----------
also, this should definetly be in the Android Development section, definetly worthy of the attention
THEindian said:
I'll be looking forward to the CM10 tutorial, when i was trying to compile it, i had to mash a bunch of guides together, then i realized that my computer wasn't strong enough to build android lol
---------- Post added at 05:33 PM ---------- Previous post was at 05:30 PM ----------
also, this should definetly be in the Android Development section, definetly worthy of the attention
Click to expand...
Click to collapse
I discussed the move with The Archangel and it was stated guides no longer go in the Development Sections. I'll live.
I have the source downloaded, but I'm having kernel errors. I tell it what to compile kernel wise, it still fails. I tried compiling separately and it fails too >.< I'd go take a break and play some Warcraft, but the servers are down for at least another 2 hours.
matada said:
I discussed the move with The Archangel and it was stated guides no longer go in the Development Sections. I'll live.
I have the source downloaded, but I'm having kernel errors. I tell it what to compile kernel wise, it still fails. I tried compiling separately and it fails too >.< I'd go take a break and play some Warcraft, but the servers are down for at least another 2 hours.
Click to expand...
Click to collapse
Ran into that. I didn't overcome that...
thanks so much for these guides. among the most clearly stated guides that i've come accross.
thanks again!!!
Sent from my HTC Glacier using xda premium
THEindian said:
Ran into that. I didn't overcome that...
Click to expand...
Click to collapse
I got it to compile with the Dirty kernel (Used in the old AwesomeICS rom), but it boot looped with audioflinger errors (Was missing libalsa.so (some audio file I forget the name and I'm at work right now),
I'm going to start again on Saturday, hopefully make some headroom.
So I don't have much of a clue what I'm doing but I got to this step
Final modification that needs to be done
Code:
gedit ~/android/source/device/htc/glacier/glacier.mk
Line 33: change
And all I get is a blank file. In fact I don't even have a glacier folder only a 7x30-recovery, common, msm7x30-common, and passion-common. Can anyone tell me what step I messed up?
EDIT:
Did a repo sync and the files showed up.
I can't even figure out how to get the JDK. Nomatter what guide I try I run into this:
There is only one alternative in link group java: /usr/lib/jvm/jdk1.6.0_37/bin/java
Nothing to configure.
lortay78 said:
I can't even figure out how to get the JDK. Nomatter what guide I try I run into this:
There is only one alternative in link group java: /usr/lib/jvm/jdk1.6.0_37/bin/java
Nothing to configure.
Click to expand...
Click to collapse
I may be wrong but I don't think that is an error. You only have jdk 1.6 installed so it is telling you that you have no other options to pick from. As 1.6 is the version you need you don't need to change the default.
lortay78 said:
I can't even figure out how to get the JDK. Nomatter what guide I try I run into this:
There is only one alternative in link group java: /usr/lib/jvm/jdk1.6.0_37/bin/java
Nothing to configure.
Click to expand...
Click to collapse
That's fine. continue on. I need to edit the first post to state if you have that, you're totally OK. I Just happened to have openJDK installed when I did it (hence why it shows up in screenshots)
Hi all, I don't have a nexus 7 3G so I decided to post this guide for people that want to build their own ROMs using my AOSP source from github.
Working on both Ubuntu 12.04+
NOTE: DEPENDING ON YOUR COMPUTER'S HARDWARE, COMPILING TIME WILL BE DIFFERENT
If you have a MAC OSX, I do not have a guide for that as I don't have one.
EVERYTHING THAT IS IN A BOX, OPEN TERMINAL AND ENTER THE COMMAND IN THAT SECTION
Guide Requirements:
- Computer
- Common Sense
- Some Linux Experience
- Ubuntu 64-bit Installed
- At least 4GB of ram with a quad core processor.
Required Software to Install:
Code:
sudo apt-get install git-core gnupg flex bison python gawk p7zip-full gperf libsdl1.2-dev libesd0-dev libwxgtk2.8-dev squashfs-tools build-essential zip curl libncurses5-dev zlib1g-dev pngcrush schedtool xsltproc wx2.8-doc lib32z1-dev ia32-libs lib32ncurses5-dev lib32readline-gplv2-dev gcc-multilib g++-multilib libc6-dev x11proto-core-dev libx11-dev libgl1-mesa-glx libreadline6-dev libgl1-mesa-dev mingw32 tofrodos python-markdown libxml2-utils gcc-4.7 g++-4.7
Link libx11
Code:
sudo ln -s /usr/lib/i386-linux-gnu/libX11.so.6 /usr/lib/i386-linux-gnu/libX11.so
1a. Use this guide to install it before continuing. Use java 1.7
http://forum.xda-developers.com/showpost.php?p=33061055&postcount=1
Setting Up Android SDK
2a. Download Android SDK at http://developer.android.com/sdk/index.html
2b. Extract it to your home folder [e. x. ~/android/sdk]
Setting Up the .bashrc file
Code:
gedit ~/.bashrc
Add this to the very bottom of the file:
Code:
export PATH=$PATH:~/bin:~/android/sdk:~/android/sdk/tools:~/android/sdk/platform-tools
Setup Workplace
3a. Downloading the Source
Code:
mkdir -p ~/bin
mkdir -p ~/android/SaberMod
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
chmod a+x ~/bin/repo
(Open a new terminal window after this)
3b. Setup Necessary Source
Code:
cd ~/android/SaberMod
Code:
repo init -u https://github.com/SaberMod/android.git -b sm-jb-mr1
3c. Download Necessary Source. Put the number of cpu's you have where # is
Code:
repo sync -j#
3d. Set up ccache. The suggested cache size is 50-100GB. You will need to run the following commands once you have downloaded the source code:
Code:
prebuilts/misc/linux-x86/ccache/./ccache -M 50G
3e. Extract needed files for building a fully funtional ROM. I've added CyanogenMod's extraction scripts to the device tree for tilapia which is only needed to be run one time. Do not do this with every build. Make sure your device is plugged in and adb is working.
Code:
bash device/asus/tilapia/extract-files
3f. Building the source code
Building The Source
Code:
bash sm-tilapia
Checking for updates
Code:
repo sync -j#
My own current working builds for tilapia can be found HERE
Note which ones are for tilapia and which ones are for grouper
Gapps (optional add-on package) can be found HERE
Original thread for the device I own for a full list of changes is HERE
Full ROM source code including kernel is available from viewing on my github HERE
Will definitely try this out tomorrow
wesStyle said:
Will definitely try this out tomorrow
Click to expand...
Click to collapse
Let me know how it goes.
Sent from my Nexus 7 using Tapatalk 2
This is a great guide. I really like the CM extract-files script. If you go back far enough in AOSP commit history you can find the commit where the blobs file was deleted. Looking at the diff will get you the file before it was nerfed.
Also, unrelated, but figure I'd help support fellow devs as this drove me nuts. Not sure if it is already in CM but the following core res is required if you have any hope of getting network based location services going:
Code:
<string-array name="config_locationProviderPackageNames" translatable="false">
<!-- The standard AOSP fused location provider -->
<item>com.android.location.fused</item>
<!-- The Google Network Location Services location provider -->
<item>com.google.android.location</item>
</string-array>
Got that one from craigacgomes over at rootzwiki
http://rootzwiki.com/topic/36369-rompure-android-42-jelly-bean-aosp/page__st__160#entry1023485
Synman said:
This is a great guide. I really like the CM extract-files script. If you go back far enough in AOSP commit history you can find the commit where the blobs file was deleted. Looking at the diff will get you the file before it was nerfed.
Also, unrelated, but figure I'd help support fellow devs as this drove me nuts. Not sure if it is already in CM but the following core res is required if you have any hope of getting network based location services going:
Code:
com.android.location.fused
com.google.android.location
Got that one from craigacgomes over at rootzwiki
http://rootzwiki.com/topic/36369-rompure-android-42-jelly-bean-aosp/page__st__160#entry1023485
Click to expand...
Click to collapse
The fused location is already in there. And I got it from XDA not rootzwiki. I'll add the blobs file as well thanks for pointing that out. Wonder why it got removed :/
Sent from my Nexus 7 using Tapatalk 2
I was referring to my ROM source which already has fused location services fixed...
Sent from my Nexus 7 using Tapatalk 2
Synman said:
gotcha! thanks again for the share... It got me past my last hurdle building pure aosp
Click to expand...
Click to collapse
I'm really confused on what your talking about man... Are you trying to build my source? This guide is only for discussion of building my Rom source.
Sent from my Nexus 7 using Tapatalk 2
Building now, no problems so far.
I added kernel building to the source yesterday so your name should be in the kernel version
This makes it 100x easier so I don't have to commit the prebuilt kernel into the source and build the kernel seperate from the ROM source.
Sent from my Nexus 7 using Tapatalk 2
Everything went fine. Successfully flashed and booted. And yeah, kernel building is a good feature too.
Glad to hear. Some new features lockscreen shortcut targets and time/date shortcuts are in. Clicking on the time in notification drawer takes you to alarm settings. Clicking on date will take you to calendar. Long pressing either one will take you to date and time settings.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 7 using Tapatalk 2
Hi sparksco,
Sharing, what is your domain.
I love, what you do for the community!!!
Thank you!!!:good:
daveheart14 said:
Hi sparksco,
Sharing, what is your domain.
I love, what you do for the community!!!
Thank you!!!:good:
Click to expand...
Click to collapse
Domain? And NP it's what I love about android
Sent from my Nexus 7 using Tapatalk 2
Updated for building SaberMod
I attempted to build the Xylon ROM for the Galaxy Nexus using the guide at the thread linked below. I tried using your GCC toolchain from the SaberMod github repo since it was the first Linaro 4.9 toolchain I found. It gave me a internal compiler error.
ROM Compile Guide (Galaxy Nexus): http://forum.xda-developers.com/showthread.php?t=2269825
Do you have any idea what might be causing it? Thanks in advance.
Code:
external/aac/libAACenc/src/aacenc_tns.cpp: In function 'INT FDKaacEnc_TnsEncode(TNS_INFO*, TNS_DATA*, INT, const TNS_CONFIG*, INT, FIXP_DBL*, INT, INT)':
external/aac/libAACenc/src/aacenc_tns.cpp:1004:5: error: definition in block 48 follows the use
INT FDKaacEnc_TnsEncode(
^
for SSA_NAME: value_155 in statement:
# DEBUG D#405 => MAX_EXPR <value_155, _111>
external/aac/libAACenc/src/aacenc_tns.cpp:1004:5: internal compiler error: verify_ssa failed
0xc2358c verify_ssa(bool)
../.././../gcc/gcc-SaberMod/gcc/tree-ssa.c:1046
0x9f66e2 execute_function_todo
../.././../gcc/gcc-SaberMod/gcc/passes.c:1970
0x9f704d execute_todo
../.././../gcc/gcc-SaberMod/gcc/passes.c:2002
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.
make: *** [/home/kemikalelite/android/out/target/product/maguro/obj/STATIC_LIBRARIES/libFraunhoferAAC_intermediates/libAACenc/src/aacenc_tns.o] Error 1
Also: There should be a link to the other guide thread I used at the top my quote. This is the fourth fifth sixth attempt to post this at this thread due to a reply bug in Tapatalk. Putting this notice here in case it goes to the wrong thread again.
KemikalElite said:
I attempted to build the Xylon ROM for the Galaxy Nexus using the guide at the thread linked below. I tried using your GCC toolchain from the SaberMod github repo since it was the first Linaro 4.9 toolchain I found. It gave me a internal compiler error.
ROM Compile Guide (Galaxy Nexus): http://forum.xda-developers.com/showthread.php?t=2269825
Do you have any idea what might be causing it? Thanks in advance.
Code:
external/aac/libAACenc/src/aacenc_tns.cpp: In function 'INT FDKaacEnc_TnsEncode(TNS_INFO*, TNS_DATA*, INT, const TNS_CONFIG*, INT, FIXP_DBL*, INT, INT)':
external/aac/libAACenc/src/aacenc_tns.cpp:1004:5: error: definition in block 48 follows the use
INT FDKaacEnc_TnsEncode(
^
for SSA_NAME: value_155 in statement:
# DEBUG D#405 => MAX_EXPR <value_155, _111>
external/aac/libAACenc/src/aacenc_tns.cpp:1004:5: internal compiler error: verify_ssa failed
0xc2358c verify_ssa(bool)
../.././../gcc/gcc-SaberMod/gcc/tree-ssa.c:1046
0x9f66e2 execute_function_todo
../.././../gcc/gcc-SaberMod/gcc/passes.c:1970
0x9f704d execute_todo
../.././../gcc/gcc-SaberMod/gcc/passes.c:2002
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.
make: *** [/home/kemikalelite/android/out/target/product/maguro/obj/STATIC_LIBRARIES/libFraunhoferAAC_intermediates/libAACenc/src/aacenc_tns.o] Error 1
Also: There should be a link to the other guide thread I used at the top my quote. This is the fourth fifth sixth attempt to post this at this thread due to a reply bug in Tapatalk. Putting this notice here in case it goes to the wrong thread again.
Click to expand...
Click to collapse
My toolchain is not Linaro, it's SaberMod toolchain I built myself. Er, this guide isn't for building Xylon it's for building SaberMod
sparksco said:
My toolchain is not Linaro, it's SaberMod toolchain I built myself. Er, this guide isn't for building Xylon it's for building SaberMod
Click to expand...
Click to collapse
EDIT - After 12 hours its finally done
sparksco I am following the guide of CI3kener to build your toolchain. I have repo synced eveything , but when I run the script to make the android eabi folder, it runs fine for first few minutes then hangs. I am using it in virtual box. Have assigned 6 gb ram and have 20 gb of swap size. But its getting forward in a snail's pace. It stops responding then after 15-20 minutes I see 3-4 lines in terminal then the same thing again. Good thing is it hasnt stopped however slow it maybe
Any suggestions.
vikas724 said:
EDIT - After 12 hours its finally done
sparksco I am following the guide of CI3kener to build your toolchain. I have repo synced eveything , but when I run the script to make the android eabi folder, it runs fine for first few minutes then hangs. I am using it in virtual box. Have assigned 6 gb ram and have 20 gb of swap size. But its getting forward in a snail's pace. It stops responding then after 15-20 minutes I see 3-4 lines in terminal then the same thing again. Good thing is it hasnt stopped however slow it maybe
Any suggestions.
Click to expand...
Click to collapse
Check 'Makefile.in'. Variable 'NUM_JOBS' is probably not declared resulting in infinite(!) jobs. Set manually as workaround. I have no clue how this should be handled properly. Maybe i'm missing a parent script here?
Edit: Fixed in latest releases.
vikas724 said:
EDIT - After 12 hours its finally done
sparksco I am following the guide of CI3kener to build your toolchain. I have repo synced eveything , but when I run the script to make the android eabi folder, it runs fine for first few minutes then hangs. I am using it in virtual box. Have assigned 6 gb ram and have 20 gb of swap size. But its getting forward in a snail's pace. It stops responding then after 15-20 minutes I see 3-4 lines in terminal then the same thing again. Good thing is it hasnt stopped however slow it maybe
Any suggestions.
Click to expand...
Click to collapse
I fixed the high resource issue. It was a commit from AOSP I reverted.
Hey, I am a beginer on ROM dev.
I was setting up AOSP build enviroment on Ubuntu 12.04 64 bit and I followed google's tutorial, when i was on the step
$ sudo apt-get install git-core gnupg flex bison gperf build-essential \
zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \
libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 \
libgl1-mesa-dev g++-multilib mingw32 openjdk-6-jdk tofrodos \
python-markdown libxml2-utils xsltproc zlib1g-dev:i386
There is error prompt up,
The following packages have unmet dependencies:
libgl1-mesa-glx:i386 : Depends: libglapi-mesa:i386 (= 9.0-0ubuntu1)
Recommends: libgl1-mesa-dri:i386 (>= 7.2)
E: Unable to correct problems, you have held broken packages.
I can't install libglapi-mesa:i386 or libgl1-mesa-dri:i386, as doing so would remove my xserver component. I am not sure what is the next step.
Hello everyone at xda !
As a newcomer I was searching for a bit of help getting started with android tools and its development.
So I decided to help out the newcomers a bit more by creating this thread..
I found this to be essential for our HTC Explorer Development Forum
This guide contains :
Post 1:
Info about SDK / ADB and how to install them on linux and windows.
Logcat- How to logcat , types of logcats , meaning
Adb wireless
Post 2:
Clean install
Paritioning sd
Flashing kernel , recovery
Permissions
What is overclocking ?
Recover from OC
md5 checksum
Post 3:
Video tuts and credits.
Info about ADB/SDK :
ADB
What is adb ?
Android Debug Bridge (adb) is a versatile command line tool that lets you communicate with an emulator instance or connected Android-powered device. It is a client-server program that includes three components:
A client, which runs on your development machine. You can invoke a client from a shell by issuing an adb command. Other Android tools such as the ADT plugin and DDMS also create adb clients.
A server, which runs as a background process on your development machine. The server manages communication between the client and the adb daemon running on an emulator or device.
A daemon, which runs as a background process on each emulator or device instance.
SDK
What is android SDK ?
Android software development is the process by which new applications are created for the Android operating system. Applications are usually developed in the Java programming language using the Android Software Development Kit, but other development tools are available. As of October 2012, more than 700,000 applications have been developed for Android, with over 25 billion downloads.The Android platform has also grown to become a favorite among mobile developers.
Want to download and use adb and SDK ( its in one package )?
Visit http://developer.android.com/sdk/index.html
Extract the files of the package you downloaded from the site as whatever you want to but remember it ?
Windows Specific (VISTA)
Keep your path name to which is extracted to
Eg : C:\(*package-name*) [ eg of package name : adt-bundle-windows-x86 ]
Rename the Folder to C:\(*Whatever you want to name it*) [ eg change "adt-bundle-windows-x86" to "android" ]
In order to run adb do the following steps :
Click start
Search for cmd
Right click and * RUN AS ADMINISTRATOR *
type the following commands
Code:
C:\Windows\system32\>cd C:\android*\sdk\platform-tools\ [*click enter*]
C:\android*\sdk\platform-tools>adb
C:\android*\sdk\platform-tools>adb devices
Now you should get a huge code block with all the adb commands
That means adb has been installed correctly.
adb devices gives you the list of attached adb devices and if their permissions are right..
Setting up ADB as a command on Windows 7/ Vista
Assuming you have done the above steps correctly you should have no problem going ahead
Right click on Computer
Click on properties
Go the advanced system settings
Click on the advanced tab
Go to Enviornmental variables in the dialog box
In system variables find the variable " Path ".
Double click on it and in variable value add the following line at the end of it :
Code:
;C:\android\sdk\platform-tools\;
Click on OK etc and save the settings
now Run command prompt
Type adb and your adb commands will be in function..
You can now run adb as a command and dont need to go to the directory every time.
Linux Specific ( Ubuntu )
PS (important) if someone has a 64bit linux then they need to download 32bit libs
for this, before all these steps run this
Code:
sudo apt-get install ia32-libs
You should have an updated JDK for this.. Just in case..
Code:
$ sudo add-apt-repository ppa:sun-java-community-team/sun-java6
$ sudo apt-get update
$ sudo apt-get install sun-java6-jre sun-java6-bin sun-java6-jdk
we need to make a new directory by this command
Code:
mkdir android
then extract by
Code:
tar -zxvf ~/Downloads/android-sdk_r21.0.1-linux.tgz
then move it to the directory we just made
Code:
mv android-sdk-linux ~/android/sdk
the open android sdk manager by
Code:
android/sdk/tools/android
this will open android sdk manager
we need to select just android sdk tools and android sdk platform tools for adb and then select install packages
^^this will download everything required
then we need to set a path to include adb
Code:
gedit .bashrc
and then a file opens and paste this text in that file
Code:
export PATH=${PATH}:~/android/sdk/platform-tools
then we make the above bashrc file executable by this
Code:
chmod a+x .bashrc
then we need to setup device rules and make that file executable
ps sample is the username
Code:
]sudo gedit /etc/udev/rules.d/51-android.rules
and copy and paste this
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="0502", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="413c", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0489", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="091E", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0482", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0955", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="10A9", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="04dd", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="19D2", MODE="0666"
and then make rules executable by:
Code:
sudo chmod a+x /etc/udev/rules.d/*
we need to add full path to adb start server
Type :
Code:
sudo gedit /etc/rc.local
this will open a file
now add this line just above where it is written exit 0
Code:
/home/sample/android/sdk/platform-tools/adb start-server
"sample is username"
after this we dont need to cd to adb directory..we can just type adb devices and the phone will surely show up
Guide for Linux by Gnexus. Thank him Here!
Now we have a blooming xda forum at HTC Pico aka Explorer with :
Cyanogen mod 7
Cyanogenmod 9
Cyanogenmod 10
Cyanogenmod 10.1
Sense 3.5(stock)
Sense 4.0
Which is quite a lot considering our device is considered as
A legacy / low activity device
Click to expand...
Click to collapse
Now with all those ROMs come their respective bugs..
Just saying
" Random reboot "
" I dont know but xyz doesnt work "
" Xyz fces "
Click to expand...
Click to collapse
Gives just another burdening job for a ROM dev of trying to find that same mistake and trying to take a log of it..
At times they are on a different ROM and it becomes difficult for them to flash their old ROMs again..
Sometimes they dont even have the same device !!
So.. Try to ease the job of the dev by bringing whats called a logcat so you can do the following to help them out :
You should have installed adb and fastboot by now
For getting a logcat you should do the following easy steps
Connect phone to pc / laptop ( quite obviously )
Assuming you have rooted your phone you should have required drivers installed ?
To enable ADB mode on your phone go to settings > developer options > Debugging > USB Debugging > ON
1st go to cmd and run as administrator and go to the root of adb
simply type
Code:
C:\android*\sdk\platform-tools>adb logcat
and you get a logcat running on your screen
Want to post a logcat somewhere ?
1] A logcat that can be easily copy pasted and given to someone else :
to do that type :
Code:
adb logcat > cat.txt
*cat is just an example .. it can be Anything logcat.txt, catlog.txt, etc ( let your imagination go wild )
This gives you a logcat at the platform-tools folder .
Now if you get your logcat you can post the logcat somewhere in the dev threads as a whole logcat or you can put specific lines where you want the dev to look at or you know the error is present. There is a character number limitation on a single post on xda for which you can simply upload the .txt file or you can also post it on Pastebin and share the link/url on the thread. This helps a lot .
Alternatively there are apps such as aLogcat or Catlog but installing adb and fastboot is essential as it will not only help you with this but other functions also look further down..
Meanings of symbols in a logcat !
You usually see this at the start of a sentence in logcat .
I/> ===> Information
S/> ===> Silent
D/> ===> Debug
W/> ===> Warning
E/> ===> Error
F/> ===> Fatal
For more information about logcats
Help with solving a logcat from fellow members only for pico !
DMESG (*Useful for devs / beta testers alike*)
Go to your adb directory via terminal / cmd on admin privileges
Type
Code:
adb shell dmesg > dmesgLOG.txt
Terminal emulator :
Code:
dmesg > /sdcard/dmesglog.txt
DMESG is useful for finding out errors / bugs in the hardware aspects caused due to software issues and kernel issues (* eg : deepsleep , bluetooth not working , wifi not working etc . *) which cannot sometimes be easily solved through a simple logcat.
Lastly K-MESG
To help solving with respect to kernels (* Yes it is a kernel not kernal... *)
Kernel issues like a kernel panic and similar. Similar steps to dmesg but the code is
Code:
adb shell cat /proc/last_kmsg > kmsg.txt (*via adb*)
cat /proc/last_kmsg > /sdcard/last_kmsg.txt (*via terminal emulator*)
ADB wirelessly
To use adb via Wi-Fi
Download this wonderful app from the playstore adbWireless
Click on the green button and an IP will come on the app screen. (* eg: 123.456.7.890 *)
On your computer go to your adb directory via terminal / cmd prompt
type
Code:
adb connect 123.456.7.890
Voila! You are using adb wirelessly
Some useful extra stuff !
Adb guide
Note : Please do not quote the entire first post in the replies !
Some other essential guides.
What do you mean by a clean install ?
WARNING ! : Do NOT wipe/format External storage . This will result in the loss of data.
A clean install can be done as follows :
On CWM / Yannou's recovery :
Boot into recovery
Do a factory reset
Go into mounts and storage using volume rockers and power button.
Format /system /boot /cache
Go to advanced : Wipe Dalvik Cache.
On TWRP Recovery :
Go to wipe
Wipe Cache , Dalvik Cache , System SD Ext and then do a factory reset.
Done ! Now flash the required ROM you want to flash!
How to partition SD card ?
Note :
This will result in your SD card being formatted. So always keep a backup of all your files on your computer.
For Stock ROM you need a FAT 32 partition which can be done via computer ONLY.
Via Recovery
Boot into recovery
Go to advanced
Partition SD card (*EXT 2,3,4 etc.*)
Select EXT Size *to whatever you want to preferably 512 mb or more*
Select Swap = 0 mb as Explorer doesnt support swap. ( at least till now )
Partition SD card! (*Will take some time*)
After partitioning is done just remove your SD card (*while your phone is off*) and just insert it back in manually.
Reboot /system (*if you have a ROM installed*)
Connect to PC and check for bad partitions just in case.
Steps 7,8,9 are not mandatory but are a good practice.
Via a computer : ( Windows )
Requirement :
SD Card reader
MiniTool Partition Wizard Home Edition 7.7 .
For further details on this visit this great guide
How to flash custom recoveries / kernels ?
How to flash a custom recovery ?
Via computer
Copy the recovery.img of the custom recovery you are try to flash and paste it in the adb directory ( for windows ==> C:\android\sdk\platform-tools\*paste here* )
Boot your Pico into bootloader (*remove battery and after 3-4 secs press vol. down and power button simeltaneously*)
In bootloader menu connect pc to your phone via usb cable and then there will be a red coloured sign just above the options saying
FASTBOOT USB
Click to expand...
Click to collapse
Now start
Windows Go to platform-tools directory in command prompt and type
Code:
fastboot flash recovery recovery.img
fastboot reboot
Linux Go to the directory of adb and fastboot and type in terminal
Code:
$ ./fastboot flash recovery recovery.img && fastboot reboot
or if path is set directly..
Via phone Terminal Emulator
Take the recovery.img that you want to flash and place it on your sd card ( eg /sdcard/(*here*) )
Begin Terminal emulator app (*Download from playstore*)
Type su (*enter*)
Allow superuser permissions (*enter*)
Note : Now you must get a line beginning with $
Enter
Code:
flash_image recovery sdcard/recovery.img
Still racking your brains over this ? Check out post 3 for video tuts !
For kernels do the same thing except replace replace Recovery.img with Boot.img
Setting permissions
Heard about setting permissions ? Ever wondered what they are ?
On a UNIX based system, every single file and folder stored on the hard drive has a set of permissions associated with it, which says who is allowed to do what with the file. Every file (and folder) also has an "owner" and a "group" associated with it. If you created the file, then you are usually the owner of that file, and your group, or the group associated with the folder you created the file in, will usually be associated with that file.
Click to expand...
Click to collapse
So how to configure them ?
You need a file explorer with Root access
Go to the required folder/app you want to set a permission and long press on it ( in most file explorers )
You will get something like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Select what is required and close.
Alternative via adb
Same as before from adb directory on cmd propt / terminal
Code:
adb shell
su
chmod 777 /system/app/Notes.apk
INDEX :
r = read w = write x = execute
Reference for chmod
So 777 = rwxrwxrwx 755 = rwxr-xr-x and so on and so forth..
What is overclocking ?
Overclocking is the process of making a computer or component operate faster than the specified clock frequency by the manufacturer by modifying system parameters. One of the most important techniques is running at a higher clock rate (more clock cycles per second; hence the name "overclocking")..
Operating voltages may also be changed (increased), which can increase the speed at which operation remains stable.
Pros : You get much more performance including gaming performance and overall UI performance..
Cons : Overclocking is always risky if something is configured improperly and may also result in permanent damage of your hardware. As long as it is done safely you are good to go.
You may see some increased power consumption.
Extreme overclocking might kill your hardware.
Undervolting :
The process where you provide less voltage to your cpu rather than the stock voltage.
Advantage:
Reduced heat from your device.
Good battery life.
Disadvantage:
Extreme undervolting will make your device unstable and some times even end up with a boot loop.
Recovering from an OC NAND Wipe..
cute_prince said:
Ok guys, here I am posting NAND Recovery Procedure:
Download the following attachment.. Rename flash_erase.txt to flash_erase ( Its actually a binary file )
Copy this file to /system/xbin directory using Root Explorer. Set permission as 755
Make sure Root Access is enabled for both Apps and ADB in Developer settings
Connect phone to PC .. Now open a terminal ( I am using Ubuntu ) and type the following:
Code:
[COLOR="Blue"]adb shell
su
cd /system/xbin
./flash_erase -N /dev/mtd/mtd2 0 0
./flash_erase -N /dev/mtd/mtd4 0 0
./flash_erase -N /dev/mtd/mtd5 0 0[/COLOR]
Note: when you execute above command you may get an IO error.. Its OK, dont get panic
Now disconnect phone from PC.. Remove battery and reinsert it ..
Goto recovery and:
format /boot
format /system
wipe data / factory reset
Now install your favourite ROM
Once the ROM is booted, goto storage settings.. Everything should be fine now and you should get around 140MB free depending on your ROM
Click to expand...
Click to collapse
What is md5 ? How is it useful?
The MD5 Message-Digest Algorithm is a widely used cryptographic hash function that produces a 128-bit (16-byte) hash value. Specified in RFC 1321, MD5 has been utilized in a wide variety of security applications, and is also commonly used to check data integrity. MD5 was designed by Ron Rivest in 1991 to replace an earlier hash function, MD4. An MD5 hash is typically expressed as a hexadecimal number, 32 digits long.
What does it mean in english ?
For android basically it is used to maintain the uniqueness of a file. It is also used to check wheter the file is the same file that has been uploaded or not .. or wheter the the downloaded file is half downloaded or broken..
You can check the md5 sum of two files. If they match then they are the same file. If they dont .. back to your download screen.
How do I check the md5 sum ?
On windows :
Download this and extract it on your pc..
Just put in the file's location..
Get the md5 sum from the OP
Match them ..
On android
There is an app for it : Android Filve Verifier
Video Tutorial # 1 : How to flash any recovery thru terminal emulator ! By Rishik
Video Tutorial # 2 : How to take a backup of your system! By Rishik
Please thank him for it.. HERE !
Credits : bala_gamer, cute_prince , Genexus , Rishik999, wikipedia , sdk , many tutorials on xda and other forums... and google.
Re: [GUIDE] How to install sdk / adb and do a logcat
Wrong section post in general this isnt any development
Sent from my HTC Explorer A310e using xda premium
---------- Post added at 12:03 PM ---------- Previous post was at 12:01 PM ----------
Mods move this to general!
Sent from my HTC Explorer A310e using xda premium
I knew this was coming .. It is in many development sections even for my old device Sensation. Trust me it is needed in the development section. Mods are free to move it.. Even mentioned it in the first post.. as good as a guide on rooting the pico or even compiling a kernel. Dont you think ?
If you think the people actually read the general section why would the dev thread be full of so much spam ? :silly:
good..nice..
i think this will work on win 7 also??
and give a tut for linux too...if you want i can post one here!!
Adding a lot.. Even video tuts.. if possible..
Video Tutorials
I have recently made a tutor on how to flash recovery.img through terminal emulator
I guess OP needed them?
I hope,he wont mind sharing them
http://www.youtube.com/watch?v=ND9UvfV3G34
Liked it
Please hit the like button on the vedio
Ofc the thanks button also
Disliked?
Nevermind :victory:
Thanks!
Re: [GUIDE] How to install sdk / adb and do a logcat
Can u add guide how to adb via wireless
Sent from my HTC Explorer using xda app-developers app
Re: [GUIDE] How to install sdk / adb and do a logcat
KiranP23 said:
Can u add guide how to adb via wireless
Sent from my HTC Explorer using xda app-developers app
Click to expand...
Click to collapse
Yeah was about to add it soon...
Rishik999 said:
I have recently made a tutor on how to flash recovery.img through terminal emulator
I guess OP needed them?
I hope,he wont mind sharing them
http://www.youtube.com/watch?v=ND9UvfV3G34
Liked it
Please hit the like button on the vedio
Ofc the thanks button also
Disliked?
Nevermind :victory:
Thanks!
Click to expand...
Click to collapse
Adding them bro thanks a lot .. I'll pm you
Sent from my HTC Explorer A310e using xda premium
logcats
Thanks a lot OP for making this noob friendly guide!
This really helped me,in getting logcats ..Where first I use to scratch my brains
Such guide will definitely gonna boost up development ! As there would less of noobish post! :victory:
Please,add as much as u can in these guides! :good:
U can still add on ..How to read logcats?
Anyways,I found it really helpful!
Re: [GUIDE] How to install sdk / adb and do a logcat
Fully Reading logcats and undertanding them in detail
. will need a book on java.. I will add some basics symbols and meanings in a log cat ..
Sent from my HTC Explorer A310e using xda premium
Re: [GUIDE] How to install sdk / adb and do a logcat
akshat.shenoy said:
Fully Reading logcats and undertanding them in detail
. will need a book on java.. I will add some basics symbols and meanings in a log cat ..
Sent from my HTC Explorer A310e using xda premium
Click to expand...
Click to collapse
This will be very helpful if u add meaning of those codes
sometimes after doing the instructions given in your tut for linux adb still returns
HTML:
List of devices
???????????
im on linux mint nadia and this did happen to me
so we need to setup device rules..and because we might use another android phone also its wise to add all the rules, so:
Code:
]sudo gedit /etc/udev/rules.d/51-android.rules
and copy and paste this
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="0502", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="413c", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0489", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="091E", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0482", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0955", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="10A9", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="04dd", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="19D2", MODE="0666"
and then make rules executable by:
Code:
sudo chmod a+x /etc/udev/rules.d/*
and akshat we need to make bashrc also executable..
Re: [GUIDE] How to install sdk / adb and do a logcat
I really don't have linux just added what sprintonfire suggested he gave me a shell of what to do so apart from the linux part I have tried and tested everything else. Free for susuggestions and improvements not only on linux but also for the windows part thanks gnexus your a genius ( what my auto correct typed when I tried typing your name)
Cheers
Sent from my HTC Explorer A310e using xda app-developers app
akshat.shenoy said:
I really don't have linux just added what sprintonfire suggested he gave me a shell of what to do so apart from the linux part I have tried and tested everything else. Free for susuggestions and improvements not only on linux but also for the windows part thanks gnexus your a genius ( what my auto correct typed when I tried typing your name)
Cheers
Sent from my HTC Explorer A310e using xda app-developers app
Click to expand...
Click to collapse
i aint that much of a genius...but thanx bro
check ur pm..
didnt put all that here because it would have crowded the thread..!
Edited first post .
Changed entire Linux guide for installing sdk tools.
Added a small bit of info right at the end.
Reading logcats (basic)
http://forum.xda-developers.com/showthread.php?t=1378491
I guess this can be helpfull for noobs like me xD
This one is perfect
http://developer.android.com/tools/debugging/debugging-log.html
Real S**t xD
akshat you havent given a link from where to download sdk package for linux..
for those who just want adb follow these steps before step 1:
go here
and click on sub category "DOWNLOAD FOR OTHER PLATFORMS"
and under "sdk tools only" download the one for linux!
@akshat include this before step 1 of linux guide!
gnexus said:
akshat you havent given a link from where to download sdk package for linux..
for those who just want adb follow these steps before step 1:
go here
and click on sub category "DOWNLOAD FOR OTHER PLATFORMS"
and under "sdk tools only" download the one for linux!
@akshat include this before step 1 of linux guide!
Click to expand...
Click to collapse
They should understand that at least I guess..
still will include thanks..