Related
Development thread for Linux on the HTC HD2
PLEASE READ THE FAQ BEFORE POSTING QUESTIONS
Introduction:
To run any Linux based user space on a device -this includes android, debian, ubuntu, openembedded, etc- you need a working Linux kernel.
This thread discusses the development on Linux kernel and user space on the HTC HD2.
All android ports to windows phones are based on the efforts of porting the Linux kernel to these devices. This is what all the porting is about. Nobody is porting Google Android to these phones. It works already.
Contributing:
This is not a secret club. All source code and development information is publicly available. Everybody who is willing to contribute is free to join the development process.
People working on porting Linux to HD2:
You can donate to the developers putting a lot of time into this Linux kernel port.
(putting together android files (=>making "roms") is not the porting)
cr2
NetRipper
dcordes
Markinus
LeTama
Cotulla
dan1j3l
Parad0XUA
manusfreedom
Technical information for interested people:
General Developer Information:
http://htc-linux.org/
Leo/HD2 Wikipage
http://htc-linux.org/wiki/index.php?title=Leo
Leo/HD2 Linux Kernel:
git://git.linuxtogo.org/home/groups/mobile-linux/kernel.git htc-msm-2.6.32
gitweb: http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=shortlog;h=refs/heads/htc-msm-2.6.32
Patches welcome!!
How to compile the Kernel:
http://htc-linux.org/wiki/index.php?title=QuickDeveloperStartGuide#Kernel
=> use htc-msm-2.6.32 branch and htcleo machine type
How to contribute: (Please be aware that this is primarily for developers!)
http://htc-linux.org/wiki/index.php?title=Contact
Newsflash:
Check http://twitter.com/htc_linux for extra quick news
03/24/2010 compass working, battery monitor added
03/26/2010 moved to new htc-msm-2.6.32 branch
03/29/2010 don't use ondemand governor
04/01/2010 add ext3
04/05/2010 dex, rtc, battery monitor, merged with google updates
04/08/2010 naming and pm changes, timer problem is fixed (other low level problems still exist)
04/09/2010 memory remapped
04/14/2010 clock updates
05/01/2010 the cause for the segmentation faults is still unknown. a new kernel was added based on codeaurora (see Leo kernel link 1st post)
05/13/2010 update Image build with latest (minor) changes.
05/19/2010 vfp/neon enabled in the 2.6.32.9 kernel. built with gcc-4.4.4 cross toolchain
05/20/2010 new video player demo added
06/02/2010 nothing new. but we are still working...
06/10/2010 more attention to segfault/illegal instruction problem on lkml
06/12/2010 usb host mode works perfectly. patches and build following
06/12/2010 usb host mode changes committed, kernel build uploaded
06/20/2010 linux is booting on qsd8250 based acer s200 - let's see if same cpu crash problem can be observed
06/21/2010 same cpu crash on s200 - the problem is not specific to leo
06/23/2010 Cotulla discovered desire/bravo bootloader has some workaround for a qsd8250 CPU hardware bug..
06/24/2010 LeTama tried out running patched bravo kernel on leo and got the segfaults
06/25/2010 Mailing list post from K. 'Cotulla' Ivan on how he found the solution to the infamous segmentation / illegal instruction problem on htc leo / hd2. Code in attachment see mailing list
06/25/2010 NetRipper included Cotulla's qsd8250 initialization code in haret. Build available on NetRipper's website also see Mailing List
06/25/2010 http://twitpic.com/20cruy http://twitpic.com/20cohg Messing around with ubuntu and other distributions using usb keyboard and mouse. Full potential of hd2's great speed and big display show. This runs real smooth. Soon as I got something easy to install I will upload it along with instructions on how to power the usb peripherals - without which you can't interact yet.
06/28/2010 Android is working. It was very simple problem with a missing configuration setting in the kernel which is fixed now.
06/29/2010 EXTRA EXTRA Major hurdle taken towards using touchscreen GPIO are xnow fixed. Again it's a problem about initialization so we need to add this in HaRET as well.
06/29/2010 NetRipper - aka Fastest HaRET Developer In The West - made a HaRET with GPIO IRQ fix
06/30/2010 Touchscreen source code now in linuxtogo git
06/30/2010 New wiki page on using usb host mode to connect peripheral devices.
06/30/2010 zImage build with touchscreen, keypad, usb-host mode posted in build section.
06/30/2010 First version of Ubuntu for HD2 released in the Build section
07/01/2010 android with sense for HD2 in Build section
07/04/2010 sensors working - (compass, G, light, proximity) - code available in git. See Build section for set of files to test. zImage in Advanced section updated. Thanks for the patch go to Parad0XUA
07/05/2010 Vibro working too. Code pushed, zImage updated.
07/05/2010 LeTama added WiFi support. Patch and Build following
07/08/2010 Timers updated in htc-msm-2.6.32 kernel
link to frequently updated kernel (zImage) autobuilds in advanced builds section added
new wiki page with detailed status info http://htc-linux.org/wiki/index.php?title=Leo/Status
07/10/2010 initial testing with 3g data connection, WiFi patches in git soon.
07/10/2010 Source code for 3g data connection and WiFi are available from git now
07/11/2010 New extra smooth android kit with the most recent Linux Kernel available in Android section! This has all kinds of stuff like hardware 3d acceleration, bluetooth, WiFi and 3g data connection included.
07/13/2010 support for camera added. taking videos does not work yet
07/14/2010 ongoing merge of Cotullas entire linux kernel sources (which added all the new features in recent builds) with the git kernel source code repository for hd2 Preliminary patch at http://oe.netripper.com/files/cotulla-merge.diff Sorry for the delayed release of the sources!
07/16/2010 Many of the recent changes now in official git repository
07/17/2010 Initial support for battery monitor and audio recording available. Linux kernel zImages on cotulla's site. No code available yet.
07/18/2010 FM receiver working in android
07/19/2010 Proximity sensor working in official git repository
07/20/2010 we created a facebook page for the htc-linux project
07/22/2010 due to legal concerns I will not directly link to ripped android images with proprietary parts which I am not allowed to distribute (e.g. HTC Sense). I don't want to cope with some lawyer mail.
07/24/2010 please read this before releasing HD2 android roms http://forum.xda-developers.com/showthread.php?p=7336826
07/25/2010 some new updates in the local cotulla source tree farm: seems like he added support for switching the panel (display) on/off. Find latest zImage (Linux kernel builds) on cotula's site Unfortunately there is still no source code for the recent changes but it will be released soon.
07/25/2010 turbo mode problem fix source code in official git kernel repository. autobuilds as usual on netripper site (look for zImage builds below)
07/26/2010 Ready to go Ubuntu v0.2 with very big changelog in the making
07/26/2010 a stable solution to the 3g DATA problem is found. I will add the kernel code and builds for the chefs later.
07/27/2010 New ubuntu with working touchscreen, 3g, WiFi, texting, etc. available soon for hd2
07/28/2010 Patchfor stable 3G Data connection in git. Google Android will need some adjustments to make use of it.
07/28/2010 GPS library was successfully patched to make use of the HD2 GPS in android: http://cotulla.pp.ru/leo/Android/libgps.so
07/30/2010 Ubuntu for HD2 v0.2 final version released. Go grab it! It's feature rich and touchscreen friendly.
08/03/2010 New progress with the Linux kernel with audio during calls. A binary image can be downloaded from here. Sorry but no sources are available for this. (Patch author cotulla doesn't show the code yet)
08/03/2010 Speak of the devil. Thank Cotulla for making his entire Linux kernel source code available. Now it's the turn of the fellow developers to merge it for ease of access and modification in the HD2 git kernel source repository.
08/08/2010 All of the recent source code is now available in the Linux kernel git repository. See first post for further information.
08/09/2010 Linux kernel image (zImage) and module autobuilds from the git source code are available at http://oe.netripper.com/files/htcleo_autobuild/ (-latest files always link to the latest build and get automatically update once there are changes in the source code available in git)
08/10/2010 We are working to get a stable solution to use more memory in git. This is a useful initrd to test memory for errors automatically: http://linuxtogo.org/~lgorris/initrd-memtester-armv7a.cpio.gz
08/11/2010 Full memory source code in git - uptodate zImage and modules at http://oe.netripper.com/files/htcleo_autobuild/ use THESE memory settings in startup.txt
08/14/2010 Kernel update: 1) LED driver added 2) Support for WiFi-Hotspot (iptables) enabled. Update kernel and modules via instructions in FAQ page.
08/20/2010 Flashlight support added. Grab the latest development kernel to get it! http://htc-linux.org/wiki/index.php?title=Leo/UpdateKernel
08/31/2010 Many changes in the Linux kernel since the last update:
working flashlight
ppp stability
usb stability (works with windows7 now)
fixed usb host mode kernel
working backlight control in normal Linux distros
working WiFi master (access point) mode: enables tethering (you might need to update firmware files. )
09/05/2010 We have been working on a new kernel base for the HD2 for few days now. Markinus started the initiative by introducing our present HD2 specific changes in the EVO4G release kernel source code. Right now the htc-msm-2.6.32 branch is still more advanced. We might create an autobuild for the EVO4G base kernel in case it will be superior at some point.
Builds
Global notes:
*None of the current releases will touch your internal flash. After restart you are back in the usual winmo.
*When Linux is booted, windoes mobile is shutdown abruptly. Although this is very rare it can cause some data loss. Please save your work and make frequent backups!
*You need at least a 2.08 radio rom version installed on your HD2. If yu have an older version you might not be able to boot Linux.
Separate files
For updating purposes and 'rom' creation
Automatically compiled Linux kernel builds for the HTC HD2 from GIT source code.
SEE FAQ SECTION BELOW FOR HOW TO INSTALL FRESH KERNEL
View GIT changelog
Click here to view autobuild history (archived dated zImages and modules)
Most recent zImage (Linux kernel image)
zImage-htcleo-latest
The Linux kernel is the core element of your operating system. It contains most of the drivers. It is supplied in form of a compressed (gzipped) executable binary Image. Along with an initial rootfilesystem aka initrd it is loaded into memory and executed by the bootlaoder HaRET.
Most recent Linux kernel modules to match zImage-htcleo-latest (has bcm4329.ko)
modules-htcleo-latest.tgz
Kernel modules are drivers that are not included in the zImage. They go seperately in .ko files. bcm4329.ko holds the wifi driver and tun.ko is needed for tunneling. For android use you must extract the modules.tgz file, search for the .ko files you need and copy them into /system/lib/modules/ directory. See FAQ for how to copy files into your android install.
HaRET (bootloader)
HaRET.exe
The haret bootloader is used to start Linux according to the instructions it reads from the file default.txt . If HaRET sees a file called startup.txt it will use this instead and boot Linux directly without any prompt.
startup.txt (bootloader/HaRET configuration - auto updated to match latest GIT kernel)
startup.txt
NOTE: This example configuration only holds the parameters critical to booting with latest GIT. Ask the person supplying you with 'roms' for additional parameters needed. See FAQ section for more detail on parameters.
Android
Please browse the main HD2 Android forum for various recent builds.
It is always important to install a recent kernel. See post #3 for how to.
Ubuntu
Ubuntu for HD2 v0.2
This second version has many new features like connectivity and is fully functional with the HD2 touchscreen. (No more USB stuff needed!)
If you would like to use USB devices like keyboard, mouse, usb stick etc, see here
release date: July 30, 2010
filename: hd2-ubuntu_0.2.zip
size: 773MB
md5sum: 2d67bbe658cc7a9e8599e8adf7724768
torrent: (use encouraged)
http://linuxtogo.org/~lgorris/hd2/hd2-ubuntu_0.2.zip.torrent
http://oe.netripper.com/files/hd2-ubuntu_0.2.zip.torrent
direct mirrors:
http://linuxtogo.org/~lgorris/hd2/hd2-ubuntu_0.2.zip
http://oe.netripper.com/files/hd2-ubuntu_0.2.zip
http://htc-linux.org/stuff/leo/hd2-ubuntu_0.2.zip
Quickinstall
It is important to check included readme.txt for safety notes, usage instructions and other confusion!
*1) get storage card with at least 3GB free space
*2) extract archive into root directory of storage card so that ubuntu folder is in \Sotrage Card\ubuntu
*3) runt haret exe
Features and Changelog
Kernel
*Updated Linux kernel based on htc-msm-2.6.32 revision '3af9a39113d40887f42688108ff0dbdeefd8e4cc' (see first post)
*Improved touch screen and keypad driver allow for decent navigation with the bare device
*WiFi driver
*3g driver
*Vibration driver
*Many [[Msm_Usb_Host|USB host]] drivers added (usb mass storage, audio, networking)
*Battery, panel and bluetooth drivers not installed yet due to lack of available source code. (only zImages available)
*Exact kernel source code with patches used included in archive.
Rootfilesystem based on the Karmic Koala from 0.1 release with
*Enlarged rootfilesystem size (2,6GB)
*Many tweaks for touchscreen use: on screen keyboard, enlarged GUI components, ..
*One touch super easy operation of 3G and WiFi connections, screen rotation and other things
*New packages installed, e.g. firefox and fennec browser with kinetic scrolling, pidgin instant messaging, ..
*Easy installation of extra languages etc
*GUI for the media player (gnome-mplayer) to allow basic control of the video playback
Note for testers of the old 0.2-beta release
Thanks a lot for checking the beta and providing feedback! This allowed for fixing the following in final 0.2 release:
*The off-screen content (e.g. wicd passphrase) problem was resolved adding ALT key (Home button on HD2) to drag windows around
*Add gnome-mplayer gui for the accerlated mplayer
*3G DNS hack removed (opendns caused problems accessing many websites)
*Enlarge on screen keybaord
~
Frequently Asked Questions
FREQUENTLY ASKED QUESTIONS & INSTRUCTIONS
Not so small Smallprint
TRY AND WORK THINGS OUT FOR YOURSELF BEFORE POSTING QUESTIONS. IF THAT DOESNT GIVE RESULTS THEN READ THE THREAD (THE LAST 20 PAGES SHOULD SUFFICE). THEN TRY THE SEARCH BUTTON.
IF YOU ASK A QUESTION THAT HAS BEEN COVERED IN THIS POST THEN YOU WILL BE GIVEN A WARNING AND YOUR MESSAGES WILL BE MONITORED. DO IT AGAIN AND YOU WILL BE GIVEN A 1 WEEK BAN.
IF YOU SEE A QUESTION BEING ASKED IN THE THREAD WHICH IS COVERED IN THE FAQ THEN PLEASE REPLY WITH A SIMPLE LINK TO THE FAQ AND THEN REPORT THE USER TO mskip (moderator).
IT IS RECOMMENDED TO INSTALL A HARDSPL ON YOUR DEVICE FIRST
YOU CAN FIND OUT MORE INFORMATION ABOUT INSTALLING HARDSPL AND CHANGING YOUR RADIO *HERE*
USEFUL SITES
Changelog of official HD2 GIT Linux kernel (shows driver changes etc)
Latest zImage (Linux kernel) and module files (automatically updated from GIT): http://oe.netripper.com/files/htcleo_autobuild/zImage-htcleo-latest
Port progress overview: http://htc-linux.org/wiki/index.php?title=Leo/Status
Android builds and download links: http://gamesquare.co.uk/ or http://robsbay.co.uk/
INSTALLATION INSTRUCTIONS FOR DIFFERENT BUILDS
DarkStone1337 - HTC Sense (Desire build)
1. Download from one of the above sites and extract the contents to your pc
2. Copy all files to the ROOT of your Storage Card
3. Soft Reset your device then using a File Manager goto your Storage Card and run clrad.exe (it wont do anything but it has run) followed by haret.exe (do this within 30 seconds of your phone booting into Windows Mobile)
4. Wait for Android to boot (may take upto 5 minutes)
5. Update your Linux kernel and Linux kernel modules (drivers). See below
DarkStone1337 - Froyo build
1. Download from one of the above sites and extract the contents to your pc
2. Copy the Android folder (including all files within the folder) to the ROOT of your Storage Card
3. Soft Reset your device then using a File Manager goto your Storage Card, Android folder and run clrad.exe (it wont do anything but it has run) followed by haret.exe (do this within 30 seconds of your phone booting into Windows Mobile)
4. Wait for Android to boot (may take upto 5 minutes)
5. Update your Linux kernel and Linux kernel modules (drivers). See below
Patched RootFS files (thanks to michyprima) to gain Root access to your Android Build:
DarkStones DesireV5 build - *HERE*
Useage: Copy the required file across to the right place on your Storage Card, overwrite the existing file. Load Android and thats it.
INSTALLING NEW LINUX KERNEL (zImage) AND MODULES (.ko files)
Three Things to know about the Linux kernel
1) The Linux kernel is the center of your of your operating system. Its core is seated in the kernel image (zImage file - the z means it is compressed). It contains most of the drivers.
2) Some drivers go external via Linux kernel modules (.ko files). E.g. in the HTC HD2 Linux kernel, the WiFi module is supplied as bcm4329.ko
3) The kernel image and kernel modules are made to match. They need to have the exact same version. This means if you pick a random .ko file things might go wrong => Find always up to date kernel image and matching modules here
Editing startup.txt
1) The following lines are needed in startup.txt to make GIT kernels work in any build !
set mtype 2524
set ramaddr 0x11800000
set ramsize 0x1E400000
set initrd_offset 0x00a00000
set kernel zImage
<ADDITIONAL PARAMTERS GO HERE!!!!!!!!1 Remove this line.>
bootlinux
Click to expand...
Click to collapse
2)Additionally you need to specify the following. Those parameters are dependent on the build you use. Look them up in your present startup.txt
*Initial ram disk filename (set initrd initrd.gz)
*Command line paramters (set cmdline "foo=bar google=android" )
Click to expand...
Click to collapse
Installing the latest Linux kernel image (zImage)
1) Download the latest Linux kernel image (right click, save file as)
1a)for Google Android
1b) for classical GNU/Linux based distros (Ubuntu, openemebdded, meego, maemo etc)
Be aware these build links are dynamic and will be updated once the Linux kernel source code is updated. See here for static links
2) Rename the file to zImage
3) Overwrite your old zImage file with the newly obtained zImage file
Click to expand...
Click to collapse
Installing the matching Linux kernel modules (.ko files)
1) Download the latest Linux kernel modules to match your kernel image
1a) for classical GNU/Linux based distros (Ubuntu...)
1b) for Google Android
2) Install the modules...
2a) in GNU/Linux
As root run
cd /
tar xvf /path/to/modules-htcleo-usbhost-latest.tgz
Click to expand...
Click to collapse
2b) For Google Android...
extract the modules-htcleo-latest.tgz file
you will notice it contains a directory structure.
example for module locations within modules-htcleo-latest.tgz :
WiFI module:
lib/modules/2.6.32.9-38151-g827fa85/kernel/drivers/net/wireless/bcm4329_204/bcm4329.ko
Network tunneling module:
lib/modules/2.6.32.9-38151-g827fa85/kernel/drivers/net/tun.ko
Yet Another Flash Filesystem module:
lib/modules/2.6.32.9-38151-g827fa85/kernel/fs/yaffs2/yaffs.ko
Basically you want to copy all .ko files you need into /system/lib/modules directory
Learn 3 Methods to do so detailed in the following:
memin1857 said:
Three different methods for replacing bcm4329.ko (which makes wifi work) Method B seems to be the best.
Easiest: (uses winmo, does not use third party app or commands)
A) (MAY ONLY WORK FOR SHUBCRAFT BUILD) Under winmo, create a folder named root inside your Android folder in your sdcard. This folder named root will be the actual root when Android boots up.
For example:
Create this folder structure under winmo:
STORAGE CARD\Android\root\system\lib\modules
and copy the bcm4329.ko file in it. It will look like this:
STORAGE CARD\Android\root\system\lib\modules\bcm4329.ko
Boot Android and the file gets copied to the protected Android file system. (/system/lib/modules)
If you do this from within Android, reboot to take effect.
B) Start a Terminal Emulator within Android. (Install a terminal emulator from market if not already installed) Copy bcm4329.ko to sdcard root beforehand. Filename has to be all lowercase. Enter these commands:
su
mount -o rw,remount /system
cp /sdcard/bcm4329.ko /system/lib/modules
you should get no response and wifi should work immediately.
you may want to make system readonly again with command
mount -o remount r /system
Delete old bcm4329.ko file if it exists at /sdcard/Android/root/system/lib/modules or it will come back on next reboot.
C) Use a third party app like Root Explorer, Droid Explorer, Root Manager, ES File Explorer and copy the bcm4239.ko file to /system/lib/modules which is mounted in read-write (RW) mode.
(DROID EXPLORER RUNS FROM WINDOWS XP/VISTA/7 and uses adb. No reboot required. Others run from within Android)
You can do A, B OR C. You don't need to do them all. Method A had only been tested in shubcraft v1.2b build.
As a fourth way you can use adb command that comes with android sdk. install usb drivers from within android sdk and connect your hd2 with usb debugging enabled. commands are same with terminal just put adb in front of it and run from folder adb is in.
If you copy an incorrect version of bcm4329.ko that is not matched to your zImage kernel wifi will say error and not work.
You can also WAIT for a new build that properly includes these files already to come out.
You can get bcm4329.ko file from http://oe.netripper.com/files/htcleo_autobuild/modules-htcleo-latest.tgz
Open the tgz file with winrar or similar program. The bcm4329.ko file is under lib\modules\2.32.xxxx\kernel\drivers\net\wireless\bcmxxx
Click to expand...
Click to collapse
Click to expand...
Click to collapse
GENERAL FAQ
*Some Roms are reported to work better with Android than other Roms. Duttys Roms seem to have the robot voice problem on calls. Miri's WM6.5 v17 Roms and NRGz Energy Roms seem to work best and have fewer problems.
* With some old radio rom versions it is impossible to boot Linux. Make sure you install a 2.08 + Radio. known working Radios are 2.10.50.08_2 and 2.12.50.02_2
* With the working Linux kernel any kind of Linux based userspace can be used on hd2. This includes google android and any other Linux distribution.
* This is a work in progress! Lots of stuff is still missing. Check http://htc-linux.org/wiki/index.php?title=Leo/Status for current state of affairs
* We know about most available sources of Linux kernel code for the snapdragon devices. It is not necessary to point to evo, bravo, nexus etc.
ANDROID TIPS AND HELP
No Sound in Android: Make sure you run clrad.exe BEFORE running the haret.exe file to boot Android. When you run it, it will not do anything but it does run.
Mobile Internet isnt working on TMOUS HD2: T-Mous users have to manually enter the APN for the mobile internet to work. Go into Network, Mobile Networks, APN. If the APN screen is blank press the Windows button and choose "Add APN" from the menu that pops up. Enter the following, Name: epc.tmobile.com, APN: epc.tmobile.com. Leave the rest blank. Then press with Windows button again and save. Your mobile internet will now work.
Setting up APN (Access Point Name) for Wireless Internet (other than TMOUS): Get your settings from *HERE* then on Android goto Settings, Wireless & Networks, Mobile Networks, Access Point Names. If bank press the Windows Button, New APN and enter your details.
For those having issues with WiFi turning on and off: Go to Settings>Wireless and Networks>Wi-Fi settings>Advanced(Windows key)>WiFi sleep policy> Select Never
Green Screen when booting into Android: Pull out and reinsert the battery, restart the phone and try again.
Phone gets stuck when loading Android (progresses very slow or stuck in the same postion for several minutes): Pull out and reinsert the battery. Delete all references to Android from your storage card including the cache folders and any folders Android created. Then copy the downloaded files back to the ROOT of your storage card or where you are supposed to place them (including the AndroidApps and media folders if you have them). Soft reset your device and run the clrad and haret files within 30 seconds of WinMo loading or use a program such as JMZ's Bootloader.
Sleep of Death (not coming out of sleep): Update your Linux kernel image and modules as instructed above, then restart your phone and restart Android. If you keep getting Sleep of Death with the newest Linux kernel image and Linux kernel modules files then reformat your storage card with FAT32 and start over again. Always make sure you run the latest Linux kernel image and modules.
How to install .apk files on Android: Copy the .apk file to your storage card that you want to install. (see kernel guide for android file copying howto) Load Android and run 'Linda File Manager' from the programs list, then browse to 'SD Card' (complete action using Linda File Manager if asked) and then to the folder where you put the .apk file. Note: To see more information on the screen minimise the keyboard, then click 'view' and select 'details'. Once you have found your .apk file click on it then tick 'Use by default for this action' and select 'package installer'. Now just follow the onscreen instructions to install your program. OR you can copy the .apk files to the AndroidApps folder in the ROOT of your Storage Card and they should auto install when Android loads (most of the time).
Battery isn’t charging in Android: Install the latest Linux kernel image and Linux kernel modules as detailed above.
Excessive Power Consumption: Remember that all these builds are still in beta version and not complete. Alot of things are still being ironed out.
Programs and system functions not working (such as Video camera, Bluetooth, Keyboard backlight on sleep, etc): Install the latest Linux kernel image and Linux kernel modules as detailed above.
No Ringtones or Notifications in setup (in DarkStone's Builds): Download the following file http://gamesquare.co.uk/media.zip (copy the link into your browsers address bar or it wont download). Extract the 'media' folder (make sure the folder has sub folders with the sounds inside those) to the root of your SD card. Now go to Settings, Sound and Display, Phone Ringtone or Notification Sound and they should be there.
What is a zImage? zImage is a Linux kernel binary image. It is the core of your operating system containing most of the drivers. The prepended z means that it is compressed with the gzip algorithm, making it smaller than the non compressed Image file.
Can I use more multiple zImage files at the same time? No. Your phone can only execute one Linux kernel at a time. HaRET.exe (the bootloader) reads the kernel filename from startup.txt - You can maintain multiple zImage files on your phone but chose only one via startup.txt
How do I change the background wallpaper? Hold your finger on the screen and select Wallapers from the popup list.
How do I change the settings? Press the Start Menu button on your phone (middle hardware button) to bring up the menu, then select the bottom middle button (settings or preferences depending on your Android build).
I cant update an app thats pre-installed (i.e. facebook or twitter): Download Root Explorer from the Market, then open it and browse to the 'system, app' folder. Delete the apk file of the app you want to update then try downloading and installing it again.
If you are trying out a TEST build of Android then you SHOULD have a basic level of intelligence (laughs quietly to self) so PLEASE use your brain and try to work things out for yourself before posting a question.
USEFUL ANDROID APPS
* Android System Info (by ElectricSheep, Excellent system information app): Download FREE from Market
* Battery Indicator (gives battery and temperature % readout in the taskbar): Download FREE from Market
* BatteryMinder (excellent battery information program with time left and temperature): Download FREE from Market
* CalWidget (excellent alternative to the standard calendar with lots of sizes): Download FREE from Market
* Dropbox (from Dropbox inc. excellent way to transfer files to your phone): Download FREE from Market
* FaceBook for Android (v1.2): Download FREE from Market
* Footmob (football from everywhere): Download FREE from Market
* Gmote (allows you to control your pc from your phone): Download from http://www.gmote.org/
* Google Earth (great app for viewing anywhere on the earth): Download FREE from Market
* Google Goggles (visual recognition app, well worth trying): Download FREE from Market
* Handcent SMS (enhances your sms functions and has a nice message widget): Download FREE from Market
* lastfm (really good free music streaming player similar to Pandora): Download FREE from Market
* MoreLocale 2 (nice little program that adds more locales and even add custom ones): Download FREE from Market
* Myplayer (watch on-demand tv programs for free): Download FREE from Market
* Nexus One Torch (by Ben Buxton, LED works when High Brightness is turned on): Download FREE from Market
* Opera Mini Browser (very nice and feature packed internet browser): Download FREE from Market
* Phonebook 2 (excellent contact manager app): Download FREE from the Market
* Photoshop.com Mobile (nice image editing program): Download FREE from the Market
* Qik Video Camera (record and share video, works as video camera on beta roms): Download FREE from the Market
* Ringdroid (create your own RingTones): Download FREE from Market
* SetCPU (great app allows you to tune the cpu for different situations): Download *HERE*, HowToUse it *HERE*
* Sky Remote record (says it all - tested and working fine for UK): Download FREE from Market
* TempMonitor Lite (puts temperature in taskbar): Download FREE from Market
* Zedge Ringtones & Wallpapers (free ringtones, message tones and wallpapers): Download FREE from Market
USEFUL ANDROID INFORMATION
1. The difference between Desire Builds and Froyo Builds (thanks to memin1857)
Desire build is ripped from an HTC Desire. It is Android version 2.1 (Eclair)
Froyo build is ripped from a Nexus One. It is Android version 2.2 (Froyo)
Froyo is a newer and much faster Android version. It is currently only available on Nexus one officially. Other newer phones will get it eventually.
HTC Sense is the user interface on top of Android. Desire builds have it already. It can be disabled for standard Android interface.
2. Importing WM Contacts into Android (thanks to brownman)
You need PIM Backup, a computer with internet access and a Gmail account.
1. Open PIM Backup on your Windows Mobile device. Select the Backup action and unselect everything but contacts, then hit Next.
2. At the "Select backup filename and folder" screen, unselect the "compress backup" and "binary backup" options, then hit Next.
3. Transfer the BACKUP.PIB file that you just made from your phone to your computer. Change the extension from .PIB to .RAR, then extract the file.
4. The extracted file should be BACKUP.CSC. Simply change the extension to .CSV and import the file to your gmail account. All your contacts can now be imported to your phone through gmail - just follow the instructions given in the phone's contact menu.
or activesync with google http://www.google.com/support/mobile/bin/answer.py?hl=en&answer=138636
3. Putting a Shortcut button on HTC Sense, etc to start Linux (in order to boot Android, Ubuntu, etc)
1. Make sure you have your Android build copied to your Storage Card as instructed earlier in this FAQ
2. Install mskip's Android Loader from *HERE* and install to DEVICE Memory
3. Add a Shortcut Button to your Sense, Mobile Shell or other Today Screen Plugin
4. Click on the button to start Android loading
4. Adding languages to Android Operating SystemBU
Read *THIS* thread.
Mark & dcordes
Nice with an update thread like this, but may I ask, is this a "developers only" thread or? - Just to be sure.
mooooooa said:
Nice with an update thread like this, but may I ask, is this a "developers only" thread or? - Just to be sure.
Click to expand...
Click to collapse
you can rant as much as you like.. I will focuse on the first two posts ;P
Is it not possible to take the sw from the new HTC Evo4g is out sprint??
LG (GertS) said:
Is it not possible to take the sw from the new HTC Evo4g is out sprint??
Click to expand...
Click to collapse
Den nye HTC Evo kan jo nærmest ikke sammenlignes med HTC HD2. Andet batteri, HDMI udgang, større kamera, front kamera osv osv. Så nej.
-
Short version @English:
No. - The Evo has different hardware.
Alright, i booted the image... and the flashlight turned on for a sec, then everything turned black... thats it right?
i had to swap the default.txt to get haret to boot :/
This is only somewhat related, but nonetheless should make people less hesitant about trying android if and when we have a working ROM.
I talked to TMobile (US), and, while you cannot use an Android device on a Smartphone plan (which is what the HD2 uses), you can switch back and forth, more or less at will, between Android and Smartphone data plans. Knowing this will certainly come in handy when actually trying to connect to the internet.
Personally, I just purchased the HD2, and after using a G1 with Android for a year and a half, I feel like I am going to puke. Why is Winmo such a confusing mess? For some reason I thought it was a mature operating system, but it feels much less polished and stable than Android. Back to the store with it until linux is cracked!
should i sell my nexus one or the htc hd2? hopfully we see android on this thing and i might consider keeping the htc hd2....what u guys think? keep or sell? the hd2 screen makes my nexus one look silly...ha
ok a bit further on .. I managed to find a working (ahem) config for usbnet .. i have managed to ping my leo from my linux box and managed to get a telnet prompt .. The telnet does not fully let me in due to lack of job control i think but for now this is cool ..
Markinus is working on refining this work and making the config default so we can all benefit without the pain ..
for now if you want to see (well my brain dumps and some other output ...
http://pastebin.com/D2VZYFiv
and try the Image, root filesystem and default.txt (and dot-config if your kernel compile inclined)
The shell is crashy and not useful yet ...
http://www.megaupload.com/?d=IQ55N0Q3
Enjoy !
Cass67 said:
ok a bit further on .. I managed to find a working (ahem) config for usbnet .. i have managed to ping my leo from my linux box and managed to get a telnet prompt .. The telnet does not fully let me in due to lack of job control i think but for now this is cool ..
Markinus is working on refining this work and making the config default so we can all benefit without the pain ..
for now if you want to see (well my brain dumps and some other output ...
http://pastebin.com/D2VZYFiv
and try the Image, root filesystem and default.txt (and dot-config if your kernel compile inclined)
The shell is crashy and not useful yet ...
http://www.megaupload.com/?d=IQ55N0Q3
Enjoy !
Click to expand...
Click to collapse
What about the datasheet for the touchscreen driver? Any news?
chris5932 said:
What about the datasheet for the touchscreen driver? Any news?
Click to expand...
Click to collapse
Not as far as i have heard ..
i've a questino though @ devs. you said that the kernel is the difficult part... and after that we can easily get linux etc on it? even maemo ?.. since it's based on linux
just wanted to drop in and say hi. unfortunately there's no news yet regarding the freeze problem.
that video is just a joke. some VNC client as they say on the site. as you can see he has winmo screenlock ^^
once we have the kernel problem fixed of course you can run maemo on the hd2.
edit: btw, any datasheet news ?
It's kinda quiet in here since the recent news about WP7S.
Thanx for the update DCordes, can you put into perspective on where about you guys are then?
Is Linux booting?
If so, how is it running?
What hardware are you having problems with?
What hardware is working?
Do you have a projected ET for having Android on the HD2? Even if not finalised, but maybe first Boot?
Thanx
Keep up the good work guys (DCordes, Netripper, Markinus, CR2, Tidsk and the rest of the guys)
Seg
it's actually all in the first post. we have that problem with the kernel freezing and we don't know why yet. that's the big show stopper right now.
except for that the overall situation looks very good! sd card and even usb host is working already ^^
Hi from France,
No idea about the kernel freeze problem ... What should happen after SD card driver being loaded ?
About the multitouch datasheet, I've been searching for it for 2 days, I didn't find anything. I just asked Elan about the release date of this. Waiting for reply ...
Thanks for your work
CleM71 said:
What should happen after SD card driver being loaded ?
Click to expand...
Click to collapse
for me it crashes after init is executed (initrd or extracted to mmc, no difference) or when rootdelay is added in cmdline.
CleM71 said:
About the multitouch datasheet, I've been searching for it for 2 days, I didn't find anything. I just asked Elan about the release date of this. Waiting for reply ...
Click to expand...
Click to collapse
thanks I'm very curiious if somebody will get a reply when I tried the same thing for an aptina camera module they never answered.
with usb host working it's actually not so critical. we could use usb mouse or keyboard until we have a working leo ts driver.
ragdoll20 said:
i know, i know, you will take donations once there is some work done *beta* or something.
Click to expand...
Click to collapse
I can't speak for the other devs but I personally never said such things.
Well, the guys that are really actively working on this are written in the first post.
Anyway, Tigerzen, Cass_VM and me, we're working on this with more relax, but we're only active testers and rarely we've helped in the kernel development (if we have).
There are many things working now, but what we really need is a datasheet for our Elan digitizer(/controller) for developing a driver for our touchscreen.
Hoping the best....
The Eugenia Project Developer
-kholk
I am trying to download the source code for SM-N9005 from Samsung Open Source place (however my downloads keep cancelling, 800MB on 2Mb/s connection )
When it eventually downloads, will I be able to compile a kernel for my phone with SELinux set to permissive instead of enforcing?
I have NEVER done custom kernel development but I think this is a good time to start
Bad news: this build is discontinued.
Good news: lineageos is comming to chagallwifi. @Paulicat from TeamExynos5420 is doing a great job: https://forum.xda-developers.com/ga...m-lineageos-14-1-sm-t700-t800-coming-t3535159
CU, Nvertigo
I do not do any further builds of this rom. But thanx to @ristokoo - who is not just talking, but taking action - and thanx to @deadman96385, who will commit future fixes - the rom is carried on. For the most current builds look at the last pages of this thread for @ristokoo's builds. Since @ristokoo has no working build-environment, I'll provode you with security fixes and - propably - monthly updates. Many, many Thanx to @ristokoo for his time, dedication and support!
IMPORTANT: from build 201151118 on it is mandatory to use a Lollopop boot loader!!! You can check your bootloader version in a rooted shell (adb shell or terminal): "getprop ro.boot.bootloader" the third last digit has to be "O". A odin flashable tar for BOJ1 can be found here.
Please refer to posting #3 on how to report an issue.
IMPORTANT: netflix does NOT show HD content for the most devices. For detailed information refer to this posting.
I consider the builds from 20151112 on as non-beta and stable.
Don't expect nightlys. I'm planing one build per 10 - 14 days. @lionheartk is pushing upstream updated builds from time to time. You can find them in the thread when he publishs them - so read the thread. When hunting down an issue or implementing new features, I will push test-builds in the thread - not here in OP.
CyanogenMod (pronounced /saɪ.'æn.oʊ.dʒɛn.mɒd/) is an enhanced open source firmware distribution for smartphones and tablet computers based on the Android mobile operating system. It offers features and options not found in the official firmware distributed by vendors of these devices.
http://wiki.cyanogenmod.org/w/About
Code:
#include
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
Credits
@Barracuda77777 (without his contributitions and encouragement there would be no cm11 rom. He alone saved me from loosing myself in source code! Whenever I got stuck he came up with the brilliant change or the day saving idea. Thank you, brother!)
@UpInTheAir (most of the code changes in the kernel from the last 10 days before Christmas are from his SkyHigh kernel. He let me use his code, and most important: he explained with endless patience to me what I was doing... To reflect this the default branch of our kernel is no longer cm-11.0 but cm-11.0-sh [sh for small sister of SkyHigh]. Thank you, mate!
@crpalmer (for picassowifi device and kernel gits - the base @Barracuda77777 and me sstarted of from)
@eousphoros (for his device git: the base for @crpalmers work)
@lionheartk for providing twice-a-weak-builds.
@diegocr for getting rid of repackrom.
@deadman96385 for the kernel source from build 20151118 on.
@halaszk88, @faux123 and all the others I forgot
Unique Features
Features not to find in cm at the moment:
sswap support (using sswap binary for utilizing the swap partion of chagallwifi)
init.d support
modulized kernel and module loading support through init.d script 01moduleload
Known Issues
MHL has no sound and wrong colors
If you map MENU to a capacitive key (no matter if key itself or "long press", it will not work - workaround: do not map MENU to anything at all, then the apps are forced to show action overflow menu (aks 3 dot menu) - works on some apps (i.e. bootloguptime) on others not.
Some minor crackling when using bt-audio the same time as 2.4GHz wlan (5Ghz wlan is issue free).
No real issue, but a not currently supported feature: no onscreen navbar. If you want it - no problem: This is your chance to give something to the community!!! Untill you fixed it, you can use this untested workaround
YOU tell us...
Before reporting issues install the most recent release, read the thread and in doubt do a clean flash. For reporting an issue, please read posting number three
Installation
I recommend official twrp3 build from http://forum.xda-developers.com/showpost.php?p=65594033&postcount=315
Do a nandroid backup (and try at least once a restore to be sure it works - reboot to recovery in between backup and restore)
Download the flashable zip and check md5 checksum
read thread (reread postings 1 to 5)
Always do a "clean flash" as described in posting #2 (if you are already on my cm12 rom you can try a "dirty flash" as described in #2 - if you come from any other rom "clean flash" is mandatory!)
(optional: flash gapps)
Recomended
Third party installations of busybox may affect rom; read this.
opengapps: opengapps.org. I use the nano package for arm, version 5.1, from 20151129 (newer may work - but 1129 is proofed to work, as 0304 - for example - is proofed to be an issue).
On Xposed
Xposed is not supported in this thread: xposed changes systemfiles, so the resulting system is not the origin rom any longer. I don't want to discourage anybody from using xposed with this rom: if everything works, you are fine. If issues occur, clean flash with only gapps installed and reproduce the issue.
Source code
Device: https://github.com/nvertigo/android_device_samsung_chagallwifi
Kernel: https://github.com/nvertigo/android_kernel_samsung_chagallwifi
Binaries: https://github.com/nvertigo/android_vendor_samsung_chagallwifi
Standard build branch is current-12.1.
(Due to heavy work in progress git repositories are not always up to date.)
WARNING: try to not ask already answered questions - this will lead to bad karma, which leads to unwanted side-effects in your life. Kidding, of course - but really try to read the thread.
Changlog and Download
Mirrors are welcome. Thank you in advance!
For cm-12 upstream changelog please consult: http://www.cmxlog.com/12/#
Build 20161118
Fixed Zygote whitelist after the patchup from android security bullentin.
Build with UBERTC/linaro toolchains instead of aosp's stock toolchains.
ROM: https://www.androidfilehost.com/?fid=457095661767116515
MD5: f1a68ffce9144ecb9582a3deea61286d
History
Build 20160123
No changes in device-tree and kernel - just a maintain-release with all the cm changes (12:00 h GMT).
ROM: link follows, as soon as upload has finished.
MD5: b65a084022752fd753ac5286b7085352
Build 20160113
Changelog:
Double tap to wake: fix settings. — nvertigo
BoardConfig.mk: enable BOARD_HARDWARE_CLASS. — nvertigo
powerhal: enable wake_gesture when screen switches off, and disable wake_gesture when screen switches on. — nvertigo
CMHW: Add Double Tap to Wake support (1/2) — Sean Hoyt
Switch to software h264 decoding — Sean Hoyt
kernel: use [email protected]'s deathly kernel again. — nvertigo
proprietary-files.txt: not maintained, therefore extract-files.sh and setup-makefiles.sh are needless. — nvertigo
cm.dependencies: removed; doesn't work with UNOFFICIAL builds. — nvertigo
sepolicy: allow netd module_request and fsetid. — nvertigo
sepolicy: allow hostapd searching in efs_file:dir. — nvertigo
fstab: add length for encryptable footer. — nvertigo
device.mk: fix PRODUCT_AAPT_CONFIG, this should not contain dpi keywords. — nvertigo
CMHW: Add Double Tap to Wake support (2/2
changed to cyanogenmod_chagallwifi_defconfig. — nvertigo
power_profile: Correct values from stock rom — Schischu
Inform vendor/cm that BFQ is in use — Sam Mortimer
synaptics_dsx: Add double tap to wake support — Schischu
chagallwifi: add IKCONFIG and IKCONFIG_PROC as module. — nvertigo
synaptics_dsx: Add double tap to wake support — Schischu
chagallwifi: add support for /proc/config.gz — Sean hoyt
tc300k: Fix blinking of capacitive buttons — Schischu
ROM: https://www.androidfilehost.com/?fid=24369303960684813
MD5: 4b7a25fd16e9c11bf8f73d2f2bf4da3b
Mirror:
https://github.com/nvertigo/android...-20160113-UNOFFICIAL-nvertigo-chagallwifi.zip
Happy Flashing!
Build 20151118
IMPORTANT: from build 201151118 on it is mandatory to use a Lollopop boot loader!!! You can check your bootloader version in a rooted shell (adb shell or terminal): "getprop ro.boot.bootloader" the third last digit has to be "O". A odin --flashable tar for BOJ1 can be found here.
Also I strongly recomend a clean flash this time - sorry, folks.
Changelog:
Changed kernel source: this rom comes with deathly kernel from @deadman96385 (Thanx, dude!).
Changed kernel graphics driver f-rom t6xx to midgard.
Updated mali blobs to Lollipop.-
Fixed missing selinux domains for macloader and sswap.
If you expirience bt-audo issues, when using 2.4GHz wlan at the same time, you can try flashing an other audio_policy.conf from here. Depending on your bt-audio-device, time of day, moonphase and humidity one or an other will give better results.
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-12.1-20151118-UNOFFICIAL-nvertigo-chagallwifi.zip
MD5: http://charlesingo.mine.nu/ftp/nvertigo/cm-12.1-20151118-UNOFFICIAL-nvertigo-chagallwifi.zip.md5sum
Mirror:
https://www.androidfilehost.com/?fid=24269982086999228 Thanx to @diegocr
http://forum.xda-developers.com/showpost.php?p=63903074&postcount=1617 Thanx to Hannibal226
Mirroring is welcome! Please use Mirror as soon as availible - I'm running out of data volume on my download host!
Happy flashing!
Build 20151113
I'm quite proud to call this build the first non-beta, stable release. As I can tell from the user testing of the last test builds, this is the most reliable, media compatible and nearly issue free combination of the configurations we tested. it has chagalls native kitkat mali blobs. Most of the other blobs are from kitkat, too - only wifi-, bt- and widevine blobs are lollipop. I reverted the introduction od lollipop OMX-blobs, 'cause the lollipop ones were introducing some small issues with media playback.
If you expirience bt-audo issues, when using 2.4GHz wlan at the same time, you can try flashing an other audio_policy.conf from here. Depending on your bt-audio-device, time of day, moonphase and humidity one or an other will give better results.
Changelog:
Update mali blobs to native chagall version.
BoardConfig.mk: derp: fix wrong path. — nvertigo (HEAD -> 121-work
Boardconfig.mk: updated graphics and FIMGAPI settings. — nvertigo
cm.mk: remove \ from last line. — nvertigo
Update to BOJ1: wifi and bluetooth. See also the changes in the vendor-git. — nvertigo
audio: desabled offloading again; makes things worse. — nvertigo
add 48k sampling rate for a2dp — Franco Rapetti
audio: added audio offload. Idea from cm's i9500 git. — nvertigo
BoardConfig.mk: cleanup and beautyfy. — nvertigo
Revert "audio_policy.conf: update from N9005." — nvertigo
Disable journaling on system image for save space — nexor (nvertigo/current-12.1, current-12.1
audio: Fix ril log tag. — Andreas Schneider
hal: audio: Match HAL function prototypes. — Andreas Schneider
Various storage fixes — Sinisa (thermskin
fstab.universal5420: fix vold warnings — Sinisa (thermskin
device.mk: Add permissions for bluetooth and voip — Andrew Tarabaras
Add firmware path for Station, fixes wifi hotspot — Andrew Tarabaras
patches: adjusted OMX-google-ffmpeg.diff to upstream. — nvertigo
audio_policy.conf: update from N9005. — nvertigo
patches: adjusted OMX-google-ffmpeg.diff to upstream changes. — nvertigo
rootdir/etc/fstab.universal5420: enabled the additional use of f2fs for /cache and /data. From [email protected] — nvertigo
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-12.1-20151112-UNOFFICIAL-nvertigo-chagallwifi.zip
MD5: http://charlesingo.mine.nu/ftp/nvertigo/cm-12.1-20151112-UNOFFICIAL-nvertigo-chagallwifi.zip.md5sum
Mirror:
http://forum.xda-developers.com/showpost.php?p=63820133&postcount=1594 Thanx to @Hannibal226
Happy Flashing!
Build 20150413
Updated from cm-12.0 to cm-12.1 - cm-12.1 is based on AOSP 5.1. Remeber to update your gapps package to 5.1. I recommend pa gapps pico: http://forum.xda-developers.com/paranoid-android/general/5-1-x-5-0-x-4-4-x-pa-gapps-mirror-t3069879
ROM: http://162.220.240.98/ftp/nvertigo/cm-12.1-20150413-UNOFFICIAL-nvertigo-chagallwifi.zip
MD5: bdc8dc0937ac7416bad5314a45896719#
Mirrors:
http://forum.xda-developers.com/showpost.php?p=60089014&postcount=893 Thanx to @Hannibal226
Build 20150331
Another sepolicy fix allows the cm-12.0 bootanimation to show up immidietly on boot. ccode is reverted to 00.
Changlog:
sepolicy: allow surfacflinger to add Exynos.HWCService. — Nvertigo
chagallwifi: init: Do not override init.rc! — Christopher R. Palmer
chagallwifi: init: Remove reference to init.recovery.universal5420.usb.rc — Christopher R. Palmer
Revert "Compile stock and Samsung MTPs together [AndreiLux]" — Nvertigo
Revert "enable CONFIG_USB_ANDROID_SAMSUNG_MTP again." — Nvertigo
Revert ccode to 00. — Nvertigo
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-12-20150331-UNOFFICIAL-nvertigo-chagallwifi.zip
MD5: 7161aed1b89f7190702dc5abe77a6f18
Mirrors:
http://forum.xda-developers.com/showpost.php?p=59820711&postcount=806 thanx to @Hannibal226
Build 20150319
This build has a significant advantage: I fixed sepolicy in a way (see git for details), that it's NOT necessary any longer to flash @Chainfires SuperSU. Init.d is working right out of the box. Also Titanium has fixed its problems with cm's superuser. I have adjusted the OP accordingly, so I recommend you read OP again.
I also worked again on MTP and UMS: UMS is only working without problems, if you DON'T use move2sdvard, 'cause sdcard gets unmounted to present it as mass storage to the device on the other end of your usb-cable. BUT: MTP is presenting internal AND external memory WITH ALL DIRECTORIES and not only media containing directories - so you can use it at least on windows machines as substitute for UMS.
The kernel modifications I introduced with rhe seperate keenel are included in roms kernel, and I set ccode for 2.4GHz to EU.
Changelog:
wifi country code: set ccode to EU for 2.4GHz to enable channel 12 and 13. — Nvertigo
Revert "selinux: make init.d work again." — Nvertigo
sepolicy: allow debuggerd access to mali. — Nvertigo
sepolicy: vold: allow module_request. — Nvertigo
sepolicy: fix init.d support for 01moduleload and 10systemtuning. — Nvertigo
include/linux/sched.h: fix my derp from incomplete conflict resolving. — Nvertigo
defconfig: enable CONFIG_CRYPTO_AES_ARM_BS. — Nvertigo
defconfig: adjusted cyanogenmod_chagallwifi_defconfig after incorparating manta's 5.1 from exynos5420. — Nvertigo
for not in cm tree building: adjust CROSS_COMPILE; can be overwritten on command line. — Nvertigo
HID: input: generic hidinput_input_event handler — David Herrmann
net/compat.c,linux/filter.h: share compat_sock_fprog — Will Drewry
sk_run_filter: add BPF_S_ANC_SECCOMP_LD_W — Will Drewry
ARM: pull in <asm/simd.h> from asm-generic — Ard Biesheuvel
crypto: create generic version of ablk_helper — Ard Biesheuvel
ARM: 8120/1: crypto: sha512: add ARM NEON implementation — Jussi Kivilinna
ARM: 8119/1: crypto: sha1: add ARM NEON implementation — Jussi Kivilinna
ARM: 8118/1: crypto: sha1/make use of common SHA-1 structures — Jussi Kivilinna
crypto: arm-aes - fix encryption of unaligned data — Mikulas Patocka
CRYPTO: Fix more AES build errors — Russell King
ARM: add .gitignore entry for aesbs-core.S — Russell King
ARM: add support for bit sliced AES using NEON instructions — Ard Biesheuvel
ARM: move AES typedefs and function prototypes to separate header — Ard Biesheuvel
ARM: 7837/3: fix Thumb-2 bug in AES assembler code — Ard Biesheuvel
ARM: 7723/1: crypto: sha1-armv4-large.S: fix SP handling — Ard Biesheuvel
ARM: 7626/1: arm/crypto: Make asm SHA-1 and AES code Thumb-2 compatible — Dave Martin
arm/crypto: Add optimized AES and SHA1 routines — David McCullough
ARM: add seccomp syscall — Kees Cook
CHROMIUM: ARM: r1->r0 for get/set arguments — Will Drewry
CHROMIUM: ARM: arch/arm: allow a scno of -1 to not cause a SIGILL — Will Drewry
CHROMIUM: arch/arm: select HAVE_ARCH_SECCOMP_FILTER — Will Drewry
CHROMIUM: arch/arm: move secure_computing into trace; respect return code — Will Drewry
CHROMIUM: arch/arm: add asm/syscall.h — Will Drewry
cgroup: remove synchronize_rcu(
power: Avoids bogus error messages for the suspend aborts. — Ruchi Kandoi
freezer: shorten freezer sleep time using exponential backoff — Colin Cross
seccomp: Use atomic operations that are present in kernel 3.4. — Robert Sesek
seccomp: implement SECCOMP_FILTER_FLAG_TSYNC — Kees Cook
seccomp: allow mode setting across threads — Kees Cook
seccomp: introduce writer locking — Kees Cook
seccomp: split filter prep from check and apply — Kees Cook
sched: move no_new_privs into new atomic flags — Kees Cook
Fix execve behavior apparmor for PR_{GET,SET}_NO_NEW_PRIVS — John Johansen
seccomp: add "seccomp" syscall — Kees Cook
seccomp: split mode setting routines — Kees Cook
seccomp: extract check/assign mode helpers — Kees Cook
seccomp: create internal mode-setting function — Kees Cook
CHROMIUM: seccomp: set -ENOSYS if there is no tracer — Will Drewry
seccomp: fix build warnings when there is no CONFIG_SECCOMP_FILTER — Will Drewry
seccomp: ignore secure_computing return values — Will Drewry
seccomp: use a static inline for a function stub — Stephen Rothwell
ptrace,seccomp: Add PTRACE_SECCOMP support — Will Drewry
seccomp: Add SECCOMP_RET_TRAP — Will Drewry
signal, x86: add SIGSYS info and make it synchronous. — Will Drewry
seccomp: add SECCOMP_RET_ERRNO — Will Drewry
seccomp: remove duplicated failure logging — Kees Cook
seccomp: add system call filtering using BPF — Will Drewry
seccomp: kill the seccomp_t typedef — Will Drewry
arch/x86: add syscall_get_arch to syscall.h — Will Drewry
Add PR_{GET,SET}_NO_NEW_PRIVS to prevent execve from granting privs — Andy Lutomirski
prctl: adds PR_SET_TIMERSLACK_PID for setting timer slack of an arbitrary thread. — Ruchi Kandoi
mm: add a field to store names for private anonymous memory — Colin Cross
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-12-20150319-UNOFFICIAL-nvertigo-chagallwifi.zip
MD5: d3164baca1f11987a61a306f87d7985f
Mirrors:
http://forum.xda-developers.com/showpost.php?p=59573116&postcount=693 Thanx to @Hannibal226
Build 20150310
fix vulnerability to FREAK attack in Browser.apk. Until cm (there are curtently two diffrent suggestions in gerrit to fix this) commits a fix, every rom builder can do this before brunching:
Code:
pushd external/chromium_org/third_party/openssl
git fetch http://review.cyanogenmod.org/CyanogenMod/android_external_chromium_org_third_party_openssl refs/changes/39/90739/1 && git cherry-pick FETCH_HEAD
popd
kernel: gone back a few steps (for details see git). After patching kernel to 3.4.106 and applying some additional commits, I hoped increasing speed and decreseaing battary usage, I realized in many loading cycles, that one or some of the additional commits slightly decrease battery life (the opposide of my intention) - so I removed them again. Sadly I have not the time to examine, which commit really did the bad. I will push the questionable commits in branch "questionable". Everybody can test which commit is the culprit patch. My gut feeling suggests the "squash 'enhanced power efficiency' patch" commit. I would be very thankful for help on testing, 'cause it's very time consuming. You need AT LEAST two complete recharging cycles to make an educated decission. Thanx in advance.
UMS mode: fix write acces to device.
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-12-20150310-UNOFFICIAL-nvertigo-chagallwifi.zip
MD5: 77cc7bc67818f1251dcf295482fddd65
Mirrors:
http://forum.xda-developers.com/showpost.php?p=59363050&postcount=578 thanx to @Hannibal226
Build 20150305
Changed wifi countrycode back to 00 (rememner to adjust this to the country code your wifi router is operating in, if expirience wifi issues)
Updated f2fs driver
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-12-20150305-UNOFFICIAL-nvertigo-chagallwifi.zip
MD5: 4229d8df0afd698fe0c10dfaed3327db
Mirrors:
http://forum.xda-developers.com/showpost.php?p=59253368&postcount=540 thanx to @Hannibal226
Build 20150228
KODI/XBMC and some games,no input issue solved.
Power off charging fixed.
Updated kernel to 3.4.106.
Cherry picked some effiziency changes from SkyHigh (thanx to @UpInTheAir
USB UMS mode fixed.
Added mdnie mode setting to init.d/10systemtuning. From: [email protected]
Make wifi 2.4GHz channel 12 (and perhaps channel 13) working again.
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-12-20150228-UNOFFICIAL-nvertigo-chagallwifi.zip
MD5: e6ff3a48b31826cfc5c1e31211062e2e
Mirrors:
http://forum.xda-developers.com/showpost.php?p=59161974&postcount=501 thanx to @Retiredfinally
http://forum.xda-developers.com/showpost.php?p=59175868&postcount=507 thanx to @Hannibal226
http://forum.xda-developers.com/showpost.php?p=59179113&postcount=509 thanx to @Bantryred
Build 20150203
fix move to sd card. (*)— Nvertigo
fix power off charging (lpm charging) partly. (**) — Nvertigo
chagallwifi: sepolicy: Fix denial killing CM's SetupWizard — Christopher R. Palmer
chagallwifi: bluetooth: Fix audit denial — Christopher R. Palmer
sepolicy: fix gpsd: simplify file_contexts; restrict gpsd access to files to the required rights. — Nvertigo
chagallwifi: wifi: Switch to world regulatory domain. — Christopher R. Palmer
(*) Works even if wiping system to do a rom-flash, but be carefull: it takes time. If you have moved some apps to sdcard wait for 10 minutes or so after boot seems completed before logging in. On a test I was impatient and the apps seems to have gone from homescreen (nova) and appdrawer, but after a while they was back in app-drawer and I had to readd them to home screen. If waiting a bit before logging in, everything is in place.
Remember when apps are moved to sd, that a nandroid WILL NOT(!) INCLUDE THE MOVED APPS.
Not all apps are movable. If you move apps, that require root, you will be asked again to allow root (like you just reinstalled them).
(**) power off charging IS working. It charges and does not emergency reboot to recovery any longer. It even shows the sammy charging animation, BUT gpio keys (power, volume and home) do not work. So you can't reboot, while plugged in. You also can't switch on screen with animation again. If you want to reboot, plug off device, then the screen will come on with charging status. Wait til it goes black again, wait for three more seconds, and start your device normally with the power button.
This build is done from the 12-work branches of my three gits. I will push this status to current-12.0 soon.
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-12-20150203-UNOFFICIAL-nvertigo-chagallwifi.zip
MD5: 2d0c5826ba5d2ba1d2f3761c5165664a
Build 20150128
fixed selinux for gps
fixed selinux for init.d support works only if you flash @Chainfire's SuperSU
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-12-20150128-UNOFFICIAL-nvertigo-chagallwifi.zip
MD5: 36bc597e89be0af6233abf4f4824bc69
Build 20150125
fixed netflix
adjusted battary capacity to our 7900 mAH specs
all upstreammcommits till 20150125 18:00 h UTC
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-12-20150125-UNOFFICIAL-nvertigo-chagallwifi.zip
MD5: ac0d1198c4100b407bcc46a01235c6c7
Build 20150123
Set selinux to permissive for now. This fixes: gps and init.d support. repo synced: 20:00 20150123 UTC.
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-12-20150123-UNOFFICIAL-nvertigo-chagallwifi.zip
MD5: d5fc4388c383e9b8a5beb9aa67cde5e2
Build 20150121
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-12-20150121-UNOFFICIAL-nvertigo-chagallwifi.zip
MD5: f2a0a10cd867b34a3d3107ef5640b9c8
Different ways of flashing
Very dirty flash:
flash rom
Dirty flash:
wipe system
wipe cache
wipe dalvik-cache
flash rom
flash gapps
Clean flash
factory reset in recovery - (without wiping /data/media) this resets your settings and deletes your installed apps
[optional for paranoids - 'cause it's done from installer-script in the process of flashing] wipe /system
wipe cache
wipe dalvik-cache
wipe data (without wiping /data/media) this resets your settings and deletes your installed apps
flash rom
flash gapps
Very clean flash
factory reset in recovery - (without wiping /data/media) this resets your settings and deletes your installed apps
[optional for paranoids - 'cause it's done from installer-script in the process of flashing] wipe /system
wipe cache
wipe dalvik-cache
wipe data (without wiping /data/media) this resets your settings and deletes your installed apps
wipe internal memory
flash rom
flash gapps
I recommend ALWAYS a "Clean flash", though myself I do many times "Dirty flash"es while testing. Whenever I run in issues, I reflash the "Clean flash" way. On the issues with Camera2 I even did "Very clean flash"es - to ensure no old data is interfering.
On many threads it is MANDATORY to have done a "Clean flash" before reporting issues. Not so here - and I want to leave it this way. But always ask yourself: how many times have I done a dirty flash? Have I tested and edited files? Is it time to "Clean flash"?
I count on users good judgment.
Reporting issues
Before you report an issue
Make sure you have installed the most current build.
Do a "clean flash" as described in posting #2 (do NOT flash xposed: it's not supported - see above #1). Dirty flashes are ok most of the time. But you can never know when "not most of the time" a dirty flash produces issues, so before repprting an issue it is mandatory to perform a "clean flash", just in case...
What an issue report should contain (at least)
The more detailed information is provided, the better I can iron it out. It's not possible for me to hunt down any issue that I can't reproduce or understand, the only way to undestand your issue and it's underlaying dynamic is a logcat. I don't know automagically all usecases of all users.
Detailed description of steps to reproduce the issue.
logcat, while reproducing the issue (as text)
I'll ignore all other reports, 'cause that would be just guessing and begging for information.
How to get a logcat
Go to settings->about tablet and tab build number 7 times to enable developer options.
Go to just enabled settings->developer options and enable root access as well as local terminal
open terminal from app-drawer and type:
Code:
su -
logcat -d >/sdcard/Download/logcat.txt
zip /sdcard/Download/logcat.txt
Now you have /sdcard/Download/logcat.txt.zip - this file is the oxygen to burn down your issue!
provide this logfile with your report. Alternatly you can skip the zipping step and upload the palin text file to paste.bin or dropbox or something like this.
How to build cm12 for chagallwifi
Most important preperation step!
Learn git. Read all the manpages, that come with git. I don't speak of github - thats a nice service I like to use, but working with git means working on the command line. githubs web interface is a lightwight, impotent version of git. Github is great as server to store your projects, but not that what youmwill need the next days... Learn git or go home.
Setting up the environment
Consult the HOWTOs of your distro. You can use any distro to build android on, there is even a HOWTO on setting up an android build environment on cygwin on win. Ubuntu, archLinux and gentoo are known to work and have detailed descriptions on the settup.
I use gentoo with icedtea-7. But as stated: any distro will work, once you have setup your environment.
Getting cm12
Find a place on your harddisc partitions with at least 18 GB free space and appropriate access rights for the user you are building with. Get a shell as this user and get the scm source:
Code:
mkdir cm12 #you can call the dir how ever you want - but whenever I refer to cm12
# as directory in this howto, I refer to THIS directory. I may also use the
# term: cm build root.
repo init -u git://github.com/CyanogenMod/android.git -b cm-12.1 # this initiates the repo
repo sync # this fetches the code (quite a couple of GBs - get a laaaarge cup of coffee)
Getting chagallwifi specific gits
Copy the following lines as nvertigo_local_manifest.xml to cm12/.repo/local_manifests/
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="tm"
fetch="https://github.com/TheMuppets/" />
<remote name="cm"
fetch="https://github.com/CyanogenMod/" />
<remote name="nvertigo"
fetch="https://github.com/nvertigo/" />
<!-- save us from the step of extract-files -->
<!-- BLOBS for manta -->
<project name="proprietary_vendor_samsung" path="vendor/samsung" remote="tm" revision="cm-12.1" />
<project name="proprietary_vendor_audience" path="vendor/audience" remote="tm" revision="cm-12.1" />
<project name="proprietary_vendor_widevine" path="vendor/widevine" remote="tm" revision="cm-12.1" />
<project name="proprietary_vendor_broadcom" path="vendor/broadcom" remote="tm" revision="cm-12.1" />
<!-- BLOBS for lge -->
<project name="proprietary_vendor_lge" path="vendor/lge" remote="tm" revision="cm-12.1" />
<!-- BLOBS for oneplusone -->
<project name="proprietary_vendor_oneplus" path="vendor/oneplus" remote="tm" revision="cm-12.1" />
<project name="proprietary_vendor_oppo" path="vendor/oppo" remote="tm" revision="cm-12.1" />
<!-- BLOBS, device tree and kernel for chagallwifi -->
<project name="android_vendor_samsung_chagallwifi.git" path="vendor/samsung/chagallwifi" remote="nvertigo" revision="current-12.1" />
<project name="android_device_samsung_chagallwifi.git" path="device/samsung/chagallwifi" remote="nvertigo" revision="current-12.1" />
<project name="android_kernel_samsung_chagallwifi.git" path="kernel/samsung/chagallwifi" remote="nvertigo" revision="current-12.1" />
</manifest>
As you can see, I'm building for more devices then chagallwifi. I've decided to keep this file this way: perhaps it holds a hint on how to save us from extract-files.sh.
After you have put nvertigo_local_manifest.xml in place, make sure all dependencies are there and fetch the additional git repos:
Code:
source build/envsetup.sh
breakfast picassowifi #this pushes the relevant git repos to .repo/local_manifests/roomservice.xml and fetches them
repo sync # this one fetches our additions to nvertigo_local_manifest.xml
Build cm12 for chagallwifi
Now you are ready for build. So let's clean the build environment and fire off the magic to homegrow a cm12 rom for chagallwifi (you guessed it: from cm12 dir):
Code:
source build/envsetup.sh
make -j9 ARCH=arm clean #cleaning from previous build; you have to replace 9 by number of cores + 1
make -j9 ARCH=arm clobber #paranoid; you have to replace 9 by number of cores + 1
time breakfast chagallwifi >make.log 2>&1
time brunch chagallwifi >>make.log 2>&1
# in a second shell: tail -f make.log
make.log is better seacheble then scrolling on terminal. If something goes wrong, search for "Error 1". In the lines before that you can see what breaks your build. On my slightly overclocked amd-fx8150 with 16GB Ram brunching takes about 100 minutes.
Now you have build a flashable rom. Congrats.
Developing
Learn git.
Put the following four lines in your /etc/gitconfig
Code:
[alias]
lg1 = log --graph --all --format=format:'%C(bold blue)%h%C(reset) - %C(bold green)(%ar)%C(reset) %C(white)%s%C(reset) %C(bold white)— %an%C(reset)%C(bold yellow)%d%C(reset)' --abbrev-commit --date=relative
lg2 = log --graph --all --format=format:'%C(bold blue)%h%C(reset) - %C(bold cyan)%aD%C(reset) %C(bold green)(%ar)%C(reset)%C(bold yellow)%d%C(reset)%n'' %C(white)%s%C(reset) %C(bold white)— %an%C(reset)' --abbrev-commit
lg = !"git lg1"
Example 1: You have a fix for the device tree.
Code:
cd device/samsung/chagallwifi
git lg1 # get an impression of the git in treeview; scroll, read, learn the way the source flows
git checkout -b my-branch #you create your own local branch
#edit the files for your fix
#if you add a new file
git add new_file
#if you editied an existing file
git add edited_file
#if you want to remove a file
git rm removed_file
#now each edit is in gits staging area, but it's not commited; to commit it locally:
git commit -em "Fix foobar: foo the bar from... Try to document what you have done and why."
#now the message is taken as title for the commit and an editor opens: you can write in more detail to document your changes.
#if you want to provide such a commit in a way I can use ist
git lg1 # get the hash of the commit you want to provide
git format-patch -1 --stdout hash >/tmp/my-commit.diff
Send me the file - do NOT copy'n'paste the content. That would break tabs and spacing and render the commit unsuable. I will apply the commit with "git am", so authorship remains as well as git history. The latter is important if later one wishes to merge two different gits with simalar commits.
If you decide to keep your own git at this point, go to the github web interface, login with your name (i.e. XXXX), go to my device repository and clone it. Back to your local shell in cm12:
Code:
cd device/samsung/chagallwifi
git remote add yyyy https://github.com/XXXX/android_device_samsung_chagallwifi.git
git fetch yyyy
#remember you have commited your changes locally in your local branch cm-12..0
#the local branch cm-12.0 is setup to follow the branch cm-12.0 of the origin remote git
#but we want the local cm-12.0 to follow the one from yyyy:
git branch --set-upstream-to=yyyy/cm-12.0 cm-12.0
git push
Now you have pushed your local commit to your own remote git. Congrats. Now you write me an email: "Huh, look at my git, it fixes everything and will finally bring peace to earth.... It's in hash." Of course, I want this commit in my repo, and that is
Example 2: Take a commit from an other devs git
Code:
cd device/samsung/chagallwifi
git fetch https://github.com/XXXX/android_device_samsung_chagallwifi.git #I don't want to have this as an additional remote
git cherry-pick hash
...to be continued....
Looking forward to your up coming updates of cm12.:good:
Bushcrafter said:
Looking forward to your up coming updates of cm12.:good:
Click to expand...
Click to collapse
Me too... Would really like to try my build.
It seems my router/3g-stick is broken:
I'm not at home at the moment. I have my development server connected to the internet via a netlink n3000 with a 3g-stick. Sinve yesterday I get connection closings. I tracked that down: I can login to my machine, but as soon as the traffic increases the n3000 reboots... First after 180 to 220 MB of traffik, at the moment after som Kb (if I "tail -n250 /var/log/messages" connection breaks du to reboot...). I'm pissed off.
I'm will be at home at end of the week - hopefully it's the stick (I have a spare one). If the router is broken I need to order a new one...
How ever: sorry for making you expect a cm12 build - but it will be there as soon as I get my developing machine back to an reliable internet connection!
nvertigo67 said:
Me too... Would really like to try my build.
It seems my router/3g-stick is broken:
I'm not at home at the moment. I have my development server connected to the internet via a netlink n3000 with a 3g-stick. Sinve yesterday I get connection closings. I tracked that down: I can login to my machine, but as soon as the traffic increases the n3000 reboots... First after 180 to 220 MB of traffik, at the moment after som Kb (if I "tail -n250 /var/log/messages" connection breaks du to reboot...). I'm pissed off.
I'm will be at home at end of the week - hopefully it's the stick (I have a spare one). If the router is broken I need to order a new one...
How ever: sorry for making you expect a cm12 build - but it will be there as soon as I get my developing machine back to an reliable internet connection!
Click to expand...
Click to collapse
No problem. Hope you get it figured out when you get home!:good: We all need your expertise with cm12 so we can have the best tab s ROM in the WORLD!:laugh: :good:
Bushcrafter said:
No problem. Hope you get it figured out when you get home!:good: We all need your expertise with cm12 so we can have the best tab s ROM in the WORLD!:laugh: :good:
Click to expand...
Click to collapse
+1 :good::
nvertigo67 said:
Me too... How ever: sorry for making you expect a cm12 build - but it will be there as soon as I get my developing machine back to an reliable internet connection!
Click to expand...
Click to collapse
No need to apologize. I doubt the rom development for the tab s would be anywhere close to where it is now without your work.
Now after approx 24 hours of hoping for a cm12 rom that will finally boot on my t805, i almost don't dare to ask if there is a slight chance it will happen this time?
Uh maybe someone (maybe me? I'm trying!) could compile the rom from your GIT and upload it somewhere?
Thread is closed until OP can provide a download link. At that time the OP can contact moderation team for re-opening.
MD
Moscow Desire said:
Thread is closed until OP can provide a download link. At that time the OP can contact moderation team for re-opening.
MD
Click to expand...
Click to collapse
Sorry for the incinvience! Thank you for your help!
Download is up - Known Issues is updated. I will cleanup now and update git repositories.
Remember: IT'S ALPHA - for daily driver use my cm-11.0 build.
Thanx to all for their patience!!!
nvertigo67 said:
Sorry for the incinvience! Thank you for your help!
Download is up - Known Issues is updated. I will cleanup now and update git repositories.
Remember: IT'S ALPHA - for daily driver use my cm-11.0 build.
Thanx to all for their patience!!!
Click to expand...
Click to collapse
I will give it a try!:good: Its good to see that you got your router problems figured out!
Update: Just got your ROM running on the s and so far so good. How good do you expect battery life to be with this ROM?
Bushcrafter said:
I will give it a try!:good: Its good to see that you got your router problems figured out!
Update: Just got your ROM running on the s and so far so good. How good do you expect battery life to be with this ROM?
Click to expand...
Click to collapse
I don't know. I'm using cm12 perhaps 7h h longer then you. As long as I haven't fixed gps I suppose it not too good - but I'm guessing here.
nvertigo67 said:
I don't know. I'm using cm12 perhaps 7h h longer then you. As long as I haven't fixed gps I suppose it not too good - but I'm guessing here.
Click to expand...
Click to collapse
I will run it for a couple of days and see what my battery life is like. Is there anyway to get synapse to work with your kernel? Just curious.
Yay LP thanks will flash when it's a bit more stable
Bushcrafter said:
I will run it for a couple of days and see what my battery life is like. Is there anyway to get synapse to work with your kernel? Just curious.
Click to expand...
Click to collapse
Synapse don't know anything about a kernel - UKM does. UKM does not support our device. Grep the current version of UKM (i belive there is also a git repository for it), take a look at the device files and jason scripts and modify for chagall. You can do it in a way, that settings not availibale in a given kernel are not shown. Everybody would be glad...
My time is limited and I have made the decision to use my time on cm12 for chagall - I have started the above work. I you really want to develop UKM for us all drop me a note and I will push my work to git. But first of all make yourself familar with UKM and git. Propably it would be usefull to read the UKM thread and contact the developer.
Hi, Just to say thanks for this rom and to let you know that I flashed it and have it running now on my T800 there is just a couple of minor issues SuperSU won't update and I don't have access to my external SD card.
Thanks again :good:
Screenshot, wait time batery life
maxal said:
Hi, Just to say thanks for this rom and to let you know that I flashed it and have it running now on my T800 there is just a couple of minor issues SuperSU won't update and I don't have access to my external SD card.
Thanks again :good:
Click to expand...
Click to collapse
Sdcard: read issues section in OP for workaround. init.d support is broken at the moument.
What do you mean with "SuperSU won't update"? Error message? Logcat?
Hi,
I have been playing around with custom ROMs and Kernels already provided by other developers for a while.
And now time has come to build my own from scratch!
I have tried the following steps but seems that I am not getting anywhere.
- Fetch the AOSP from google
- Got the Samsung opensources (kernel and framework) for the device
- Merged the two sources
- Got some device tree and vendor files from github repositories
device tree -> device/samsung/herolte/.
vendor -> vendor/samsung/herolte/.
- Extracted proprietary files from the phone to vendor dir
- source build/envsetup.sh
Now at this point, it seemed as if I was on the right track, but running "lunch" and choosing the device said otherwise.
So my biggest question is, are my steps even closer to the principle of custom kernel building or am I just taking this too simple a process?
If I manage to build this rom by myself, my next step is building the device tree and vendor files by myself too.
Can anyone shade a light on this?
Thanks
When building Android 11 on a device with low ram (typically under 16gb of ram), when you get to metalava compilation it will fail with the error "java.lang.OutOfMemoryError: Java heap space"
I found the below patch which fixes this and should allow you to build the rom on a machine with as little as 8gb of ram.
Code:
Lowram fix for R. Run this command in your rom root directory:
cd build/soong
git fetch https://github.com/masemoel/build_soong_legion-r 11
# Specify heap size for metalava for R
# Reduce initial heap size for java from 2048mb to 1024mb
git cherry-pick b45c5ae22f74f1bdbb9bfbdd06ecf7a25033c78b
# Tune java compiler flags for low ram systems
# This is needed on systems with 8GB physical ram.
# sets the max heap size for java to 3112mb
git cherry-pick e020f2130224fbdbec1f83e3adfd06a9764cca87
# soong will be rebuilt the next time you build anything in aosp
Thanks to masemoel for the patch
Project Sakura have merged this into their repo so if building that rom there should be no need to alter anything
TheFixItMan said:
When building Android 11 on a device with low ram (typically under 16gb of ram), when you get to metalava compilation it will fail with the error "java.lang.OutOfMemoryError: Java heap space"
I found the below patch which fixes this and should allow you to build the rom on a machine with as little as 8gb of ram.
Code:
Lowram fix for R. Run this command in your rom root directory:
cd build/soong
git fetch https://github.com/masemoel/build_soong_legion-r 11
# Specify heap size for metalava for R
# Reduce initial heap size for java from 2048mb to 1024mb
git cherry-pick b45c5ae22f74f1bdbb9bfbdd06ecf7a25033c78b
# Tune java compiler flags for low ram systems
# This is needed on systems with 8GB physical ram.
# sets the max heap size for java to 3112mb
git cherry-pick e020f2130224fbdbec1f83e3adfd06a9764cca87
# soong will be rebuilt the next time you build anything in aosp
Thanks to masemoel for the patch
Click to expand...
Click to collapse
any guide to build with 8gb??
and compiling A10 requirement of ram?
[email protected] said:
any guide to build with 8gb??
and compiling A10 requirement of ram?
Click to expand...
Click to collapse
Building is the same regardless of ram
This patch is to solve the issue of metalava running out of memory if your source rom doesn't already include this patch in soong on android 11
Android 10 uses a different build system which you can find the patch for here
https://review.lineageos.org/c/LineageOS/android_build_soong/+/266411/3/java/droiddoc.go#77
Will this only work for compiling lineageos or any other rom?
I'm trying to build pixel experience.
himanish25 said:
Will this only work for compiling lineageos or any other rom?
I'm trying to build pixel experience.
Click to expand...
Click to collapse
It will work with any rom that is android 11 based (assuming the patch hasn't already been applied)
It just adds the java value to soong. You can look in build/soong/java/droiddoc.go to see if the values are already there or not manually.
Does this still work? I have not applied the mentioned patch.
I have 14G of RAM in my Ubuntu 20.04 in virtual box. Still Android 11 compiling failing when it tries to build the kernel image. Building snoog works fine.
Does this fix my issue by applying the patch?
Also is there a similar patch for Android 12 compiling?
V T Vishwanath said:
Does this still work? I have not applied the mentioned patch.
I have 14G of RAM in my Ubuntu 20.04 in virtual box. Still Android 11 compiling failing when it tries to build the kernel image. Building snoog works fine.
Does this fix my issue by applying the patch?
Also is there a similar patch for Android 12 compiling?
Click to expand...
Click to collapse
This is specifically for soong metalava failing due to
java.lang.OutOfMemoryError: Java heap space
It will not fix any other compiling error
I do not know what changes were made to soong in android 12
The patch only needs to be applied once? Or after / before each repo sync? I have installed the patch but still get an error at the end:
Code:
Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
at com.intellij.psi.impl.source.tree.JavaElementType$$Lambda$160/0x0000000100464840.get(Unknown Source)
at com.intellij.psi.impl.source.tree.JavaElementType$JavaCompositeElementType.createCompositeNode(JavaElementType.java:42)
at com.intellij.lang.ASTFactory.composite(ASTFactory.java:80)
at com.intellij.lang.impl.PsiBuilderImpl.createComposite(PsiBuilderImpl.java:1285)
at com.intellij.lang.impl.PsiBuilderImpl.bind(PsiBuilderImpl.java:1203)
at com.intellij.lang.impl.PsiBuilderImpl.buildTree(PsiBuilderImpl.java:919)
at com.intellij.lang.impl.PsiBuilderImpl.getTreeBuilt(PsiBuilderImpl.java:905)
at com.intellij.psi.impl.source.JavaFileElementType.parseContents(JavaFileElementType.java:82)
at com.intellij.psi.impl.source.tree.LazyParseableElement.lambda$ensureParsed$0(LazyParseableElement.java:206)
at com.intellij.psi.impl.source.tree.LazyParseableElement$$Lambda$216/0x00000001004f2840.run(Unknown Source)
at com.intellij.psi.impl.DebugUtil.performPsiModification(DebugUtil.java:553)
at com.intellij.psi.impl.source.tree.LazyParseableElement.ensureParsed(LazyParseableElement.java:205)
at com.intellij.psi.impl.source.tree.LazyParseableElement.getFirstChildNode(LazyParseableElement.java:254)
at com.intellij.psi.impl.source.tree.CompositeElement.countChildren(CompositeElement.java:449)
at com.intellij.psi.impl.source.tree.CompositeElement.getChildrenAsPsiElements(CompositeElement.java:411)
at com.intellij.psi.impl.source.PsiJavaFileBaseImpl.getClasses(PsiJavaFileBaseImpl.java:66)
at com.android.tools.metalava.model.psi.PsiBasedCodebase.initialize(PsiBasedCodebase.kt:137)
at com.android.tools.metalava.Driver.parseSources(Driver.kt:932)
at com.android.tools.metalava.Driver.parseSources$default(Driver.kt:901)
at com.android.tools.metalava.Driver.loadFromSources(Driver.kt:825)
at com.android.tools.metalava.Driver.processFlags(Driver.kt:235)
at com.android.tools.metalava.Driver.run(Driver.kt:118)
at com.android.tools.metalava.Driver.run$default(Driver.kt:100)
at com.android.tools.metalava.Driver.main(Driver.kt:86)
19:00:14 ninja failed with: exit status 1
TheFixItMan said:
This is specifically for soong metalava failing due to
java.lang.OutOfMemoryError: Java heap space
It will not fix any other compiling error
I do not know what changes were made to soong in android 12
Click to expand...
Click to collapse
Original author of the patch here, it does nothing by the way, thats why I abandoned it. https://review.lineageos.org/c/LineageOS/android_build_soong/+/262657/4
It doesn't work on Android 12 but there's still a way, I have compiled Android 12 with 8gb RAM and 12gb swap.
- In build/soong/java/droidstubs.go find :
cmd.BuiltTool("metalava").ImplicitTool(ctx.Config().HostJavaToolPath(ctx, "metalava.jar")).
- Now after :
Flag(config.JavacVmFlags).
- Add ::
Flag("-J-Xmx6114m").
Or whatever value you want.
Then it works.
In my case I didn't need to change the values in makevars.go and config.go but you may have to depending on your computer.
Good luck guys!!!
jolebaltringue said:
It doesn't work on Android 12 but there's still a way, I have compiled Android 12 with 8gb RAM and 12gb swap.
- In build/soong/java/droidstubs.go find :
cmd.BuiltTool("metalava").ImplicitTool(ctx.Config().HostJavaToolPath(ctx, "metalava.jar")).
- Now after :
Flag(config.JavacVmFlags).
- Add ::
Flag("-J-Xmx6114m").
Or whatever value you want.
Then it works.
In my case I didn't need to change the values in makevars.go and config.go but you may have to depending on your computer.
Good luck guys!!!
Click to expand...
Click to collapse
How long did it take you to complete the compile?
(I want to do that too)
Hello
Does it work for A12 builds also ?
I compiled Android x86_64 r-x86 and LinageOS nougat-x86 (cm 14.1) version with a Dell inspiron 3847 (quad core i5 -4460 , with 12 gb of ram... and 12.5gb of swap space lol) on Ubuntu Server 22.04 LTS. minimal install option.
I installed zram-config first.
I'm kinda dumb and i set up my partition with 250 gb 239 available to me.... so I ran out of space a couple of times and failed building the iso to another drive
i ended up doing --depth=1 on my repo init and repo sync - c to get the folder size down to 80 gb!!!! and finished up the build on one dive.
I did the nougat first and it took me a few days figuring out the right packages and env variables because i was following a couple of diffent guides lol . so i didn't really see how long it took me to compile the whole thing when i got it working... maybe 6.5 hours....
I did the export _JAVA_OPTIONS="-Xmx4g" thing but i don't think it stuck because I restarted my machine once and i didn't add it to a start up script and i don't think i put it in again on my finishing attempt.
Doing Android r-x86 was easy once i had the packages in place and switched my python back to v3. Compile time was like 9.25 hours...
oh i did m -j3 or m -j2 when building , so I didn't really go full tilt....
If I had give some one advice is prob start out with 300 gb or more... prob more on your partition.
And read the official google guide to setting up ur system first.. I kinda ignored warnings and just skimmed Android x86 site guide plus alot of googling of errors.
Oh maybe it would be worth trying a free trial of cloud computing.... sigh..