Database Info

[ROM] EzGingerbread (Dream and Sapphire) stable-v1.0 2011-12-04

[size=+3]EzGingerbread[/size]
(Latest release: stable v1.0)
Welcome to the ezGingerbread Rom and Development thread
Here we discuss building, testing, and patching a basic gingerbread build for the Dream Sapphire platform.
The goal is for this to be a reasonably bare bones build gingerbread build; Focusing on memory and speed performance.
[size=+2]Installation Guide (of Binaries)[/size]
While ezGingerbread remains as open source as possible this sections will provide some pointers to installing the latest distributed binary.
(The following is automatically done if installed via Rom Manager)
Requirements
EzGingerbread works on most 32b Dream, 32b Magic (MT3G), and 32a magic devices running 2.22, and/or 3.22 radios, and will auto detect the correct configuration on install.
However the following configurations are optimal:
32b Dream: Radio-2.22.28.25 and SPL 1.33.0013d are recommended
32b Sapphire: Radio-2.22.28.25 and either SPL 1.33.0013d or 1.33.0013 (if the SPL is not already installed I recommend 1.33.0013d)
32a Sapphire w/ audio plug (ie MT2.1/fender): Radio-2.22.28.25 and either SPL 1.33.0013d or 1.33.0013 (This is likely what you already have installed, if you don't have this and your phone works you likely you don't have a MT2.1/fender)
32a Classic (no audio plug): Radio 3.22.20.17 + any SPL (however 1.33.2009 or 1.33.2010 may be better) [Note 6.x radio will not work with this rom]
Users of customMTD must have an 87 Meg system '87 2' is common. There is no need to flash the cMTD boot patch as the rom installer automatically patches the boot image for cMTD.
Download Rom related files
> The ROM: GINGERBREAD-DS-Stable-v1.0-20111204.zip (md5: 2ae9f618b0650c98b9621b37ad7e8596)
> GAPPS: gapps-mdpi-gb-20110709_S.zip (mirror)(mirror 2 -- dead) (md5: 6f9a6d27cce1f58be1f34f696212d326)
> GPRS Patch (optional but recommended) gprs_patch_S.zip (md5: fa259735ca394a650710e6b26673c91a)
> Alt Launcher [Zeam] Completely optional, but for those that want a smaller launcher, or just intend to replace the default (Launcher2) anyway with a market download this may apply to you, Note its an older version, and the newer market version has been slightly unstable:
ezgb_ZeamReplacement2_S.zip (md5: 6416ec0efa15f92f3d36f6ec6b524a11)
Language Port/Pack File
If you use (German, English, Spanish, French, Italian, Japanese, Korean, Polish, Portuguese, Russian, and Chinese)
These are contained in the base rom, do not download a language pack.
If you use (Bulgarian, Czech, Danish, Greek, Finnish, Hungarian, Dutch, Slovak, Serbian, Swedish, Tagalog, Turkish, Ukrainian)
These require lang pack 1:
EZGB_lang1_20111204_S.zip MD5: 37ee9cbf4f4c80a4b5fd96269332b853
Copy Files to the phone
Copy all the downloaded zip packages to your SD Card, Remember Ra-Recovery users must put them on the root of the sd-card.
wipe or not to wipe, and other preparations
> Users upgrading from
GINGERBREAD-DS-Alpha-20110509-1, Beta builds, or the Gamma build
There is no need to wipe as long as you wiped when you first installed one of these versions of ezGingerbread. You are however encouraged to uninstall SetCPU or other overclock software, and backup your rom before installing. (if the new built in CPU Speed function is not to your liking feel free to disable and re-install the 3rd party overclock software after upgrading)
> Users New to ezGingerbread (upgrading from a different rom)
You are encouraged to wipe before installing, however feel free to use Titanium or other utility to back up your application and application data to be restored after installation.
Installing the rom
flash in the following Order:
> GINGERBREAD-DS-Stable-v1.0-20111204.zip
> [If you need it] EZGB_lang1_20111204_S.zip
> gapps-mdpi-gb-20110709_S.zip
> [optional but recommended] gprs_patch_S.zip
> [if you chose it] ezgb_ZeamReplacement2_S.zip
Reboot
Reboot the phone and wait for the screen to dim before interacting with the phone
(First boot will take additional time; longer if you had many applications installed and are doing a no-wipe upgrade)
[size=+2]Tips and Tricks[/size]
Now that the system is installed I have some pointers to making the system as fast as possible, you may ignore these if you really must have something they don't allow but if the phone runs slower you know why:
Tip 1: Google Maps: If you can live without it the phone will be much more stable.. (Maybe using mapquest as an alternative) However if you really do need Google Maps note the newer versions require much more resources than the older ones.
If you must have google maps try an older version rather than maps 5+
Google Maps 4.7 (mirror) MD5: b8c558351949be97eb8703d1f4a05807 (download/place on SD card and install with File Manager)
Brut Maps based on Maps v4.6
Tip 2: Facebook: Well I can't say facebook was ever fast on our slow Dream, but the most resent versions run an "Upload Service" 24/7 in the background eating much unnecessary ram.. v1.6.4 is the newest version I know of without this behavior.
Tip 3: Apps2SD, well best to keep apps you want to use frequently of quickly on the system, but to enable Apps2SDext if you have an ext partition here are the directions:
> goto settings->Applications->Development
> Check SD-EXT
> Reboot
> Now you can use the Manager Applications screen to move apps to/from sd-ext .. if you want sd-ext to be the default install location choose it in Settings->Applications->Preferred install Location
> Data2sd will move all your application data to the sd-ext partition.. this will significantly slow down the phone thus best to leave unchecked.
Tip 4: SuperUser
The system by default prevents the update of superuser or anything signed with the same key (such as superuser elite); to temporary lift this restriction goto Settings->Applications->Development and check Update Superuser.
This will allow superuser to be updated, superuser elite to be installed/updated until reboot.
This ensures no application can change Superuser.apk on your behalf when you do not expect it thus can't grant themselves superuser access.
Tip 5: EzGb Extras
Settings->EzGingerbread Extras
This menu has historic "Spare Parts" funcitons, as well as other performance enhancements.
> Configure PowerWidget allows you to configure the powerbar widgets, when you are done configuring either reboot, or rotate the display to re-set the widget and see the update
> Incoming Call TouchUI - enables the slide to answer/end calls when a call comes in, rather than only being able to use send/end hardware buttons
> Busybox NTP Cliemt - If your phone is not keeping time, even with the sync to network time enabled, checking this may help keep the phone in sync with earthly time
> CPU Speeds, This lets you overclock and under volt, I recommend setting Min speed to 128000, leave Max screen off 480000, and max screen on may either stay 528000, or very slightly overclock to 537600. If you want the settings to apply after your next boot tap "Apply On Boot" if you have problems with the settings, before the screen turns off after boot enter this screen and tap "Reset CPU Settings" before rebooting again.
> Compcache RAM Usage, sets the amount of compcache, keep this as low as possible but not so low background services keep restarting.
> Use KSM Module, this may improve ram usage if checked, however may also slightly increase CPU usage and reduce battery life (all three results are very slight and thus hard to notice) no restart is required so test when/if it works best for you
> Window/Transition animatinos, since froyo animation times have been increased.. many find speeding these up make the rom feel more responsive as they are historically used to.
> End button behavior: choose "go to sleep"
> Haptic feedback/Compatibility Mode .. most will leave these alone
Tip 6: Surface Dithering:
Well this is a trade off [Settings->Display->Surface Dithering] if its checked the display may loose some more frames than if unchecked.. but some people rather loose the frames than see the artifacts left by skipping the dither, choose your poison and reboot
Tip 7: sync: disable what you can
Go into settings -> Accounts &sync
Tap your Google Id. Unless otherwise needed, unchecked Sync Picasa Web Albums, and Books
If you have Google plus you may also wish to disable Sync Instant Upload.
Historic versions, and additional addons can be found below in post 2
[size=+2]Kernels:[/size]
Regarding kernels: If you are looking for stand alone kernels (sometimes there is an update between official releases; or for use in other roms):
See the Stand Alone Kernel Post
The Stand Alone Kernel Post contains both the ezgb-2636 kernels and links to the tags in github they are built from.
[size=+2]Developers:[/size]
Developer's Guide (How to build ezGingerbread and the ezgb2636 kernel) is now on GitHub:
https://github.com/ezterry/manifest-gingerbread-DS/blob/gingerbread/README.mkdn
Includes instructions to fetch and build from source both ezGingerbread and its related kernel.

Binaries
"NIGHTLY" BINARIES:
Builds 20110116-1 and newer are EBI0/EBI1/2708+ auto kernel, Flash and the rom will install the correct kernel
Builds 20110107-1 and older are 2708+ kernel only
20111204-1: GINGERBREAD-DS-Stable-v1.0-20111204.zip
(md5: 2ae9f618b0650c98b9621b37ad7e8596)
Note: Release v1.0 (stable): clean resync with android.googlesource.com, Fix Japanese IME force quit, Update timezone data (removal of DST from the Moscow Time Zone), add libpico fix to build (fix text to speech force quit), Add Russian dictionary to keyboard, Fix SuperUser lock down to properly allow unmodified apk to be locked down, and cleanly allow update/elite install, update Superuser.apk, Force Quite fix on entering About Phone with no keyboard installed, some translations via AndDiSa, add new Cpu Speed settings to EzGb extras (note you will want to disable this if you wish to continue using 3rd party overclocking apps).
/
20111107-1: GINGERBREAD-DS-Gamma-20111107-1.zip
(md5: f57ebc7ccd0819e0536407d066f02c6b)
Note: Gamma release (beta+1): Kernel update to v1.5.2 w/ patches for time skew, updates to android 2.3.7, wifi lease fix, add pt_BR to language set, various framework patches fixes speedups from CM7, KSM (Kernel SamePage Merging) support to dalvik-vm with supporting kernels (eg: ezgb-2636) MMS Time display and MDPI icon from CM7, compress xbin and move various libs to a compressed xlib, compact (pngcrush + zip -9 resources.arsc) apks, superuser 3.0.6, Odex framework (shrinks the framework jars, and moves the framework dalvik-cache into system) EzGbExtras also now has options for KSM, Incoming Call TouchUI CompCache chooser, ntpd background service for better time sync. Security fixes based off digitalgardian certs, Settings no long has compcache (moved to EzGb Extras)
Edit 20111110:PICO Fix (ie: text to speech for navigation)
/
20110828-1: GINGERBREAD-DS-Beta-20110828.zip
(md5: 0161b47d36ce3ae24b85907fe19fe4ca)
Note: Kernel update to v1.5.1, Android update to 2.3.5, Pan networking from CM7 (allows bluetooth tethering without extra software, just link the devices and use tether to your phone) Gallery 3d: CM7 patches for MT zoom bug and MDPI patches, Phone: CM patches for 2g/3g power widgets toggle, framework updates thanks to AndDiSa/ADS Magpie, "Disk" (MTD) io enhancements, wifi renew logic described starting here; auto custom MTD via bootcmdutil (no need to flash boot patcher anymore) , some translation updates. Faster boot time patch from Firerat
Please read the security notice here regarding ca certs and DigiNotar
/
20110716-1: GINGERBREAD-DS-Beta-20110716.zip
(md5: 8c3293e26b6aef25851a9ce5c53fc81b)
Note: Kernel update to v1.5 (as previously released here, USB Accessory support working, update to minfree levels, improvements to services, statusbar power widgets (configure in Settigns->EzGingerbread Extras) Spare parts replaced with EzGb Extras, GPS improvements, HW3D settings improvements, please note gapps package 20110709 is recommended (however 20110508b should still work)
/
20110626-1: GINGERBREAD-DS-Beta-20110626.zip
(md5: d03a960c90b80eb077a1fe46581cc759)
Note: Kernel update to v1.4 (as released last week in the stand alone version, Fix out of space install bug when user had no sd-ext partition or sd-ext disabled, add option in Settings->Applications->Development to allow superuser updates until subsequent reboot, fix an outstanding reboot menu bug, superuser, and stability updates.
/
20110605-1: GINGERBREAD-DS-Beta-20110605.zip
(md5: fc2a33cad7affe4cf656067118eecfcb)
Note: Kernel update (Wifi disabled drain solved with hack, MMC temp log in ram for 30s after SMS details, Surface Dithering option added to Display settings, French translations, Update to services. Attention if you have long stalls after update/clean install run fix permissions [logcat shows CPU pegged], also its highly recommended to clear dalvik cache on the install of this rom.
/
20110529-1: GINGERBREAD-DS-Beta-20110529.zip (md5: 50fba2c5adabe0f83a4e4b9616680ba1)
Note: BETA!!!! Features magpie, to enable you first need to allow sd-ext to be mounted Settings->Applications->Development->Attempt to mount sd-ext.. Other features: Data 2 sd bind mount, touch screen edge bugfix, and some other bug fixes including many for better memory maintenance. Available on rom manger including options for gapps, zeam launcher and small older stable facebook [manual links below]
/
20110509-1: GINGERBREAD-DS-Alpha-20110509-1.zip (md5: e22dd434aa41cbdd744893951b12e5bc)
Note: Security updates, preventing Settings and Superuser apps to have another app using their keys on /data (this prevents a non-system app from having access to all your settings, or able to give its self root privileges), in addition I've changed the platform key, Kernel updates, swipe notification now visually swipes away (thanks to update in CyanogenMod), some settings tweaks, and minor bug fixes. Starting this version you must use GAPPS: 20110508b due to the new Platform key in use.
/
20110502-CheckPoint: GINGERBREAD-DS-CheckPoint-20110502.zip (md5: 5c0969ebf1209922add7a1e357d969ca)
Note: A re-sync with aosp to fix various bugs in the sync on 2011-05-01, APN now can be created w/o error [new IPV4/IPV6 protocol caused the confusion] various other projects got updates in AOSP as well synced into this build (additional CheckPoint build info here) ATTENTION: kernel update possible fix to camera and other crashes here for use with 20110425-1 and newer
/
20110501-CheckPoint: GINGERBREAD-DS-CheckPoint-20110501.zip (md5: d5a3765001f6fa69321bcffb642ce516)
Note: Checkpoint of the android-2.3.4 initial release. Updated to head of Gingerbread branch and the 2.3.4 release. Also renamed typo CompCache script and lowered 32b default CompCache to 8MB, 32a remains disabled by default. (build info here)
/
20110425-1: GINGERBREAD-DS-Alpha-20110425-1.zip (md5: d69b689e4aeb12335c6e67123abf20fd)
Note: New kernel 2.6.36.4-s1-ezgb-v1 / Built in zram compcache (default enabled on 32b, disabled on 32a) settable in Settings->Applications->CompCache; {requires kernel with built in zram module} / new lowmemorykiller min free and Home App memory levels for hopefully better memory use.
/
20110308-1: GINGERBREAD-DS-Alpha-20110308-1.zip (md5: bf0f6a922b3afd5c9faa15333b1e32f5)
Note: Update to android 2.3.3, add in white-listed unrestricted packages (fixes Facebook sync), Add build.trout to make dream not identify as sapphire, make sound recorder visible in launcher (was always included), include file manager (CM's version), allow download of all file types.
/
20110304-CheckPoint: GINGERBREAD-DS-CheckPoint-20110304.zip (md5: 715eba3cf37270a5ff3456c9e5c04563)
Note: Checkpoint of the android-2.3.2 ezGingerbread build; all future builds will be 2.3.3 See checkpoint information here
/
20110208-1: GINGERBREAD-DS-Alpha-20110208-1.zip (md5: 2211d8f9a1f8071b28734999d4908f3a)
Note: Added CM7 dictionaries to LatinIME (word auto completion), added pl_PL bringing supported locales to: en_US en_GB fr_FR it_IT de_DE es_ES ja_JP es_US ko_KR pl_PL pt_PT ru_RU zh_TW zh_CN (let me know if you have font issues), updated LatinIME touch logic, fix_permissions, enhanced blend/blur transforms to libsurfaceflinger.
/
20110129-1: GINGERBREAD-DS-Alpha-20110129-1.zip (md5: 87d74801b43fb97740799bacd8adccc7)
Note: Various patch sets from Cyanogen Mod 7: Javascript engine switched to V8, armv6j JIT and processor support (was previously v5), swipe to dismiss individual notification, some webkit and skia patches.. the combo of these among other things fixes gmail; Also pushed in this build to su from ChainsDD, build env updates (32bit builders, try a clean environment); some additional graphic speed enhancements.
/
20110122-1: GINGERBREAD-DS-Alpha-20110122-1.zip (md5: 74c081f42cb25cef79b5c6077866a239)
Note: some graphics framework updates, Superuser.apk, Fonts.sqf + fallback fonts (from issue 3), LiveWallpaper picker, busybox sh in use for all sh needs, super tiny toolkit.. and some small fixes. (For a terminal get one you like from market or elsewhere .. I just use connection bot for both local and remote)
/
20110117-1: GINGERBREAD-DS-Alpha-20110117-1.zip (md5: b6aa8732517f52565efac3d9febe0f5c)
Notes: GPS working, cleanup camera shim, update opengls and agl framework (video) details, builders please delete and regenerate your vendor/htc/sapphire directory (extract-files or unzip-files)
/
20110116-1: GINGERBREAD-DS-Alpha-20110116-1.zip (md5: aef05eef5e7be24e46d2f6cc70218c63)
Notes: Auto kernel (EBI1/EBI0/2708) using ez-exp20110109-cm binaries, Audio hack (corrects AudioPara4.csv on flash, gziped versions of all profiles in /system/etc/.audio/) SpareParts included, run-parts, fix modprobe (had wrong path for modules), modules.sqf
/
20110107-1: GINGERBREAD-DS-Alpha-20110107-1.zip (md5: 3f0cc16aac87a8ebc3f8c9aa3c11a3fe)
Notes: Updated proprietary files, video decoder now working in gallery3d, update internet calling permissions, fix a bug with restart menu.
/
20110103-1: GINGERBREAD-DS-Alpha-20110103-1.zip (md5: b81545dcbd5ae0f2da388d77aa3b5997)
Notes: fixed video recording thanks to CM framework patches (playback still fails), reboot power menu option thanks to CM, gsensor thanks to havlenapetr. Current Languages: en_US en_GB fr_FR it_IT de_DE es_ES ja_JP
/
20101222-1: GINGERBREAD-DS-Alpha-20101222-1.zip (md5: e16ac0bcfbf6c6e163410a3ded97fb8a)
Notes: first build released, kernel is my 2708+ port of the cm 285 nightly kernel, overall drawing speed increased.
/
20101219-1: GINGERBREAD-DS-Alpha-20101219-1.zip (md5: bef700cf0e04de003788365de469dd49)
Notes: first build released, kernel is my 20101106, better results with CM nightly or pershoot kernels however.
/
ADDONS:
Additional non-open addons that may be useful
Zeam Launcher By cloakt(replacing Launcher2 on system, also reduced to MDPI only):
ezgb_ZeamReplacement2_S.zip(md5: 6416ec0efa15f92f3d36f6ec6b524a11) [updated june 26th, 2011]​
LANGUAGE PACK1:
The packages above include support for: de, en, es, fr, it, ja, ko, pl, pt, ru, zh and are recommended for most users
If however your preferred language is not listed above, this LANG PACK 1 will replace the above languages with support for:
bg, cs, da, el, fi, hu, nl, sk, sr, sv, tl, tr, uk
Please download the version matching the ROM you are installing (see: adtl. details)
20111204-1:EZGB_lang1_20111204_S.zip(v1.0)
(md5: 37ee9cbf4f4c80a4b5fd96269332b853)
20111107-1:EZGB_lang1_20111107_S.zip
(md5: 957a943e10c81699070bd415d74ae9c8)
20110828-1:EZGB_lang1_20110828_S.zip
(md5: 054d28fe41976eabdb6d26b92bcfc045)
20110716-1:EZGB_lang1_20110716_S.zip
(md5: dfb83772e2a0d9edf6f72cdc23966e8b)
20110626-1:EZGB_lang1_20110626_S.zip
(md5: eb354f34573db67270da57cc27fa737b)
Mobile Data GPRS Tool:
A tool to update GPRS settings form gprsclass=10 to gprsclass=12 (also enables dtm)
Most users will experience better mobile network rates if they flash and choose yes, however if you run into problems simple re-flash choosing no to revert to the ezGingerbread defaults,
This tool will likely work on most Dream/Sapphire roms, however as always best to make a backup first
gprs_patch_S.zip
(md5: fa259735ca394a650710e6b26673c91a)​
GAPPS:
GAPPS: 20110709 (Please note if you are using 20110502-CheckPoint or an older build you must use gapps 20110205)
gapps-mdpi-gb-20110709_S.zip (mirror)(mirror 2 -- dead)
MD5: 6f9a6d27cce1f58be1f34f696212d326
Cleaner 2.3.4 gapps package, recommended over 20110508b. Restore from Google corrected in this package, Talk2 has been replaced with the original talk app due to incompatibilities with voice/audio chat. However you may manually install it if you wish to use the newer interface w/o the newer features. While not 100% support of all languages, core apps support more languages in this package. Mirror thanks to SilentTweak.
GAPPS: 20110508b (Please note if you are using 20110502-CheckPoint or an older build you must use gapps 20110205)
gapps-mdpi-gb-20110508_b_S.zip
MD5: 475fbf654977af73f30e509cb4adb21c
Also see information about Talk
Previous GAPPS: 20110205
gapps-mdpi-gb-20110205_S.zip (mirror)
md5: 70ddd820738b902d9b9f9b109e8fad5a
Note do not install both 20110508 and 20110205
MDPI Facebook App:
http://depositfiles.com/files/sdhr9ol3g [gb_facebook_fix_S.zip] (outdated)
md5: 17cb43e88f42cdf513f2c7c960347f21
v1.6.4 is newer w/o some of the newest memory eating services get the apk from:
http://www.apktops.com/facebook-for-android-1-6-4.html
For additional gapps:
1) Log into your Google account
2) tap gtalk to make sure its running
3) install the gapps you want from market (some common ones):
You Tube
GMail
Voice Search
Google Translate
*Maps and Streetview may also be grabbed from market; however Maps v5.* appears to be very resource intensive and overwhelms our poor devices; therefore I recommend either installing MapQuest; and/or an older version of GoogleMaps example extracted from froyo gapp pacakges. This will provide a much better gingerbread experience both while running maps and while not running maps.
Brut Maps based on Maps v4.6
Google Maps 4.7 (mirror) MD5: b8c558351949be97eb8703d1f4a05807 (download/place on SD card and install with File Manager)
​
Apps2Ext: (Included in 20110529-1 onwards)
This enabled in Settings->Applications->Development->SD-EXT
Sim Toolkit:
See: http://forum.xda-developers.com/showpost.php?p=15742165&postcount=2618
A friendly reminder... One hopes users of this thread know how to wipe their device .. and if they fail how to see they missed something in logcat.. but if not Super Wipe because regardless of subsequent errors all of these do boot to the Launcher.
Other uses are free to post custom builds in the thread for reference and testing.
Note however all of the above builds were cleanly made from the repo without modification. (ie. you are getting the file produced by the build system)
[SIZE=+2]For full credits check github; Many peoples hard work (particularly that of the CyanogemMod's team make this rom possible)[/SIZE]

GINGERBREAD-DS-Alpha-20101222-1.zip boots very well.
Under android version it still says 2.2.1. Almost ready for a daily driver.
I hope this becomes CM7 someday
Edit: I seem to have battery life issues using pershoots 2708 2.6.34.*... Any other kernel I should try (that does not have usb unplug bug)?

mschoolbus said:
Terry,
I am unable to get the alpha1 to boot no matter what kernel I try. I am using your +15mb ram hack and 2708 kernels on cm6.1 just fine.
Am I missing something?
Your work is fantastic btw! So nice you are continuing support for our old dreams
Click to expand...
Click to collapse
Not that I know much, did you check if you have the latest radio and SPL?

sada23 said:
Not that I know much, did you check if you have the latest radio and SPL?
Click to expand...
Click to collapse
I have: HBOOT-1.33.0013d
RADIO-2.22.28.25
Thanks for the help!

Did you get it to boot?
The first time i installed, it would not boot, I waited for like 15 minutes or so, then tried a different kernel, same thing.
Just to try it, I flashed the gingerbread alpha again, and tried one more time, and it booted up.
I did notice the first time I flashed it, the "progress bar" did not move at all, the second time I was able to see it move.
-Jeff

um worked fine for me but, on the setup "Touch Android to Begin", is irresponsive
the android flashes on touch but no continuation, hhelp?

Love it! Looking forward to a beta next year
mschoolbus said:
Terry,
...
I am unable to get the alpha1 to boot no matter what kernel I try.
Click to expand...
Click to collapse
1. backup
2. superwipe
3. shutdown
4. boot to recovery
5. flash the alpha rom (do not reboot)
6. flash pershoot latest New SPL + Radio 2708 Combo
7. unplug USB and reboot
Let it boot all the way up and let it sleep on it's own.
Don't expect a fluid UI and don't compare it to other ROMs. It's not intended for public consumption.

im able able to get it boot, but it hangs at the setup
when I touch the android an error pops up that launcher force closed and I cant go on with the setup

Since001 said:
im able able to get it boot, but it hangs at the setup
when I touch the android an error pops up that launcher force closed and I cant go on with the setup
Click to expand...
Click to collapse
Um.. setup is part of gapps .. we have not hacked gingerbread gapps to work yet on this.. so I'd not install whatever non gingerbread gapps you have.

I haven't flashed any gapps. I just flashed your alpha, nothing else.
Sent from my HTC Dream using XDA App

While trying to build gingerbread I've experienced some trouble:
Code:
. build/envsetup.sh
including device/htc/sapphire/vendorsetup.sh
debian:~/Desktop/android/gingerbread$ lunch
You're building on Linux
Lunch menu... pick a combo:
1. generic-eng
2. simulator
3. full_sapphire-userdebug
Which would you like? [generic-eng] 3
prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-gcc: /lib/i686/cmov/libc.so.6: version `GLIBC_2.11' not found (required by prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-gcc)
prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-gcc: /lib/i686/cmov/libc.so.6: version `GLIBC_2.11' not found (required by prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-gcc)
prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-gcc: /lib/i686/cmov/libc.so.6: version `GLIBC_2.11' not found (required by prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-gcc)
prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-gcc: /lib/i686/cmov/libc.so.6: version `GLIBC_2.11' not found (required by prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-gcc)
prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-gcc: /lib/i686/cmov/libc.so.6: version `GLIBC_2.11' not found (required by prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-gcc)
prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-gcc: /lib/i686/cmov/libc.so.6: version `GLIBC_2.11' not found (required by prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-gcc)
prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-gcc: /lib/i686/cmov/libc.so.6: version `GLIBC_2.11' not found (required by prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-gcc)
prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-gcc: /lib/i686/cmov/libc.so.6: version `GLIBC_2.11' not found (required by prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-gcc)
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=2.3.1
TARGET_PRODUCT=full_sapphire
TARGET_BUILD_VARIANT=userdebug
TARGET_SIMULATOR=false
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=GINGERBREAD
============================================
prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-gcc: /lib/i686/cmov/libc.so.6: version `GLIBC_2.11' not found (required by prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-gcc)
prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-gcc: /lib/i686/cmov/libc.so.6: version `GLIBC_2.11' not found (required by prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-gcc)
A quick and brutal fix is to:
1) go to gingerbread/prebuilt/linux-x86/toolchain
2) rename arm-eabi-4.4.3 to arm-eabi-4.4.3.old
3) link arm-eabi-4.4.0 to arm-eabi-4.4.3
Code:
cd gingerbread/prebuilt/linux-x86/toolchain
mv arm-eabi-4.4.3 to arm-eabi-4.4.3.old
ln -s arm-eabi-4.4.0 arm-eabi-4.4.3
One more fix needed to build on x86 is to change
Code:
# This forces a 64-bit build for Java6
LOCAL_CFLAGS += -m64
LOCAL_LDFLAGS += -m64
in the Android.mk files of the gingerbread/external/clearsilver/ directory
and subdirectories to:
Code:
# This forces a 64-bit build for Java6
LOCAL_CFLAGS += -m32
LOCAL_LDFLAGS += -m32
This should be fixed in a more elegant way based on the host arch.
Started to compile now....................................Done.
Works so far.
Patch attached to fix build on 32 bit hosts.
Code:
repo diff
project build/
diff --git a/core/main.mk b/core/main.mk
index 6113e52..72e32c8 100644
--- a/core/main.mk
+++ b/core/main.mk
@@ -72,7 +72,8 @@ $(info Checking build tools versions...)
ifeq ($(BUILD_OS),linux)
build_arch := $(shell uname -m)
-ifneq (64,$(findstring 64,$(build_arch)))
+#ifneq (64,$(findstring 64,$(build_arch)))
+ifneq (i686,$(findstring i686,$(build_arch)))
$(warning ************************************************************)
$(warning You are attempting to build on a 32-bit system.)
$(warning Only 64-bit build environments are supported beyond froyo/2.2.)
project external/clearsilver/
diff --git a/cgi/Android.mk b/cgi/Android.mk
index 21c534b..2c7bf36 100644
--- a/cgi/Android.mk
+++ b/cgi/Android.mk
@@ -13,8 +13,12 @@ LOCAL_C_INCLUDES := $(LOCAL_PATH)/..
LOCAL_CFLAGS := -fPIC
# This forces a 64-bit build for Java6
-LOCAL_CFLAGS += -m64
-LOCAL_LDFLAGS += -m64
+#LOCAL_CFLAGS += -m64
+#LOCAL_LDFLAGS += -m64
+
+# This forces a 64-bit build for Java6
+LOCAL_CFLAGS += -m32
+LOCAL_LDFLAGS += -m32
LOCAL_NO_DEFAULT_COMPILER_FLAGS := true
diff --git a/cs/Android.mk b/cs/Android.mk
index 9f0e30a..4807b3f 100644
--- a/cs/Android.mk
+++ b/cs/Android.mk
@@ -9,8 +9,10 @@ LOCAL_C_INCLUDES := $(LOCAL_PATH)/..
LOCAL_CFLAGS := -fPIC
# This forces a 64-bit build for Java6
-LOCAL_CFLAGS += -m64
-LOCAL_LDFLAGS += -m64
+#LOCAL_CFLAGS += -m64
+#LOCAL_LDFLAGS += -m64
+LOCAL_CFLAGS += -m32
+LOCAL_LDFLAGS += -m32
LOCAL_NO_DEFAULT_COMPILER_FLAGS := true
diff --git a/java-jni/Android.mk b/java-jni/Android.mk
index 21b4fd1..cc6d3ce 100644
--- a/java-jni/Android.mk
+++ b/java-jni/Android.mk
@@ -34,8 +34,10 @@ LOCAL_C_INCLUDES := \
LOCAL_CFLAGS += -fPIC
# This forces a 64-bit build for Java6
-LOCAL_CFLAGS += -m64
-LOCAL_LDFLAGS += -m64
+#LOCAL_CFLAGS += -m64
+#LOCAL_LDFLAGS += -m64
+LOCAL_CFLAGS += -m32
+LOCAL_LDFLAGS += -m32
LOCAL_NO_DEFAULT_COMPILER_FLAGS := true
diff --git a/util/Android.mk b/util/Android.mk
index 386f379..fc27bbf 100644
--- a/util/Android.mk
+++ b/util/Android.mk
@@ -18,8 +18,12 @@ LOCAL_C_INCLUDES := $(LOCAL_PATH)/..
LOCAL_CFLAGS := -fPIC
# This forces a 64-bit build for Java6
-LOCAL_CFLAGS += -m64
-LOCAL_LDFLAGS += -m64
+#LOCAL_CFLAGS += -m64
+#LOCAL_LDFLAGS += -m64
+
+# This forces a 64-bit build for Java6
+LOCAL_CFLAGS += -m32
+LOCAL_LDFLAGS += -m32
LOCAL_NO_DEFAULT_COMPILER_FLAGS := true

I saw you changed a few things so i made a new build, 3d seams faster, but it will crash still:
http://cyanogenmod.pastebin.com/eSGptyBR
Click to expand...
Click to collapse
I build the test rom with the Pershoot 2.6.35.10.
Also i attached the script im using for the build, isnt "mine", just adapted it a bit
p.s make the directory for the repo, put this script in in, chmod a+X G1Ginger.txt, ./G1Ginger.txt

roalex said:
I saw you changed a few things so i made a new build, 3d seams faster, but it will crash still:
I build the test rom with the Pershoot 2.6.35.10.
Also i attached the script im using for the build, isnt "mine", just adapted it a bit
p.s make the directory for the repo, put this script in in, chmod a+X G1Ginger.txt, ./G1Ginger.txt
Click to expand...
Click to collapse
You could add processor number autodetection to your the script:
Code:
processors=`grep -c processor /proc/cpuinfo`
and substitute the -j n switch with:
Code:
-j $processors

Going to give this a try on my spare G1.
Is this designed to require the 2708 or do we need to run a different kernel for 2708 support?

brentil said:
Going to give this a try on my spare G1.
Is this designed to require the 2708 or do we need to run a different kernel for 2708 support?
Click to expand...
Click to collapse
ATM it is a 2708 kernel.
If you dont have lastest radio you can always try to flash pershoot's Kernel 2.6.35.10 – OC-UV-RAM-FP – Dream/Sapphire (32B/A) here right after flashing the rom.
I have'nt tested it myself, but I changed and used pershoot's 2708 kernel zImage instead of ezterry's since it was getting a lil old when we first started working together on this...
It worked fine so it should work...

Yeah, I'm running the newer radio on both my G1 & MT3G.
Ok so I tried flashing the Gingerbread rom after super wiping my G1. I get the following error.
Code:
Installing update...
assert failed: || getprop("ro.bootloader") == "1.33.0011" ||
...
|| getprop("ro.bootloader") == "1.33.0013d"
(status 7)
So I thought maybe it was the spoofed SPL so I refashed back to engineering HBOOT 2005 and fastbooted 2013d without spoofing it and I get the same issue,

farmatito said:
You could add processor number autodetection to your the script:
Code:
processors=`grep -c processor /proc/cpuinfo`
and substitute the -j n switch with:
Code:
-j $processors
Click to expand...
Click to collapse
normaly you dont access /proc/cpuinfo w/o sudo tho right ?
in any case people can just change it as they see fit

brentil said:
Yeah, I'm running the newer radio on both my G1 & MT3G.
Ok so I tried flashing the Gingerbread rom after super wiping my G1. I get the following error.
Code:
Installing update...
assert failed: || getprop("ro.bootloader") == "1.33.0011" ||
...
|| getprop("ro.bootloader") == "1.33.0013d"
(status 7)
So I thought maybe it was the spoofed SPL so I refashed back to engineering HBOOT 2005 and fastbooted 2013d without spoofing it and I get the same issue,
Click to expand...
Click to collapse
If you have the newest radio and spl combo, you don't need to spoof the SPL.
You can always remove the SPL check in the updater script (\META-INF\com\google\android\updater-script) :
Code:
assert(getprop("ro.bootloader") == "1.33.0011" ||
getprop("ro.bootloader") == "1.33.2011" ||
getprop("ro.bootloader") == "1.33.3011" ||
getprop("ro.bootloader") == "1.33.0013" ||
getprop("ro.bootloader") == "1.33.2013" ||
getprop("ro.bootloader") == "1.33.3013" ||
getprop("ro.bootloader") == "1.33.0013d");
and resign with test-keys the modded update.zip and it will flash without checking the installed SPL.

roalex said:
normaly you dont access /proc/cpuinfo w/o sudo tho right ?
in any case people can just change it as they see fit
Click to expand...
Click to collapse
Code:
dr-xr-xr-x 69 root root 0 2010-12-06 10:16 /proc
-r--r--r-- 1 root root 0 2010-12-22 17:17 /proc/cpuinfo
/proc/cpuinfo is world-readable.

CM6 for Huawei U8120 (under development)

CM6 for Huawei U8120
This is an unofficial port of cm6 (froyo) for huawei u8120 (vodafone joy/845).
It may work on u8100/u8110 models but I dont know because I havent any of these devices.
I would like to make it clear that this is an unofficial cm6 port, it is not fully tested
and it has some bugs.Its still under development and NOT for daily use.Only for bug fixing/testing.
If all bugs get fixed we can try to make it official.I work also on a
cm7(gingerbread) port with quite a success so far, but it has more mayor bugs than cm6 port.I will create
the corresponding thread for cm7 port when it reaches a usable state.
Any help it would be great.Some of the bugs are common in froyo and cm7 port.So if
they are fixed on one port it may be fixed on the others to.
Kernel: kalt kaffe's 2.6.29
Jit enabled
Android : 2.2.1 / CM6.2
Working:
RIL
Audio - not so good volume states.Too low.
Bluetooth
Wifi
TSCalibration - use it with a pen/stick
Bugs/Not working:
Camera can take pictures.Still to fix : b/w preview and video record crashes on stop
SDCard mount via notification bar
Broken layout in dialer FIXED
Key lights FIXED
Missing AGPS
Missing FM
For any bugs you find please provide a logcat output if you can.
Build instructions on git.
Releases:
v.0.2 Fixed lights,use libloc api, add boot splash image
v.0.1. Initial Build
Im not responsible for any damage that this software may cause on your device.Dont expect support.
gapps
github

gonna test it and report any bug. thanks

i'm in finished with car gona test after work

Nice Any idea what wrong with camera?

bitye said:
Nice Any idea what wrong with camera?
Click to expand...
Click to collapse
The same reason as the other ports.I have built it without camera support
Actually I will get to the camera problem after the sdcard bug.I think that its more important.I may have fixed the key lights.Im going to test it later because now Im working.

What you know, Camera, SD Card mount on PC, and I found an other, phone can't recognize my SD when ext2 available on that. I formated to fat only now works. Dialer layout broken, wifi and Bluetooth OK, Calibration ok, dpad ok.

bitye said:
What you know, Camera, SD Card mount on PC, and I found an other, phone can't recognize my SD when ext2 available on that. I formated to fat only now works. Dialer layout broken, wifi and Bluetooth OK, Calibration ok, dpad ok.
Click to expand...
Click to collapse
How about the mac-adress?
And plz make the CM7 Treath fast so we can See you fixes and help you.
thx

I have no problem with audio volumes
Sensors not working

Can you upload cm7?

CM7 is not in a functional state right now so I will not make a thread/upload the configs.Also I'm sure that the're going to be roms based
on it as soon as possible
And I don't think that's right.
Please let me explain my opinion:
Take for example the cm6 port.
The cm6 port is not fully tested (I have run it for just a day or two and I haven't tested all the provided features).
So if cedric123 or bitye or any other guy, that is cooking roms (very good roms to be honest) ,
provide roms based on the cm6 port (as already have ) then we will have this situation:
+ the number of users/testers will grow (that's good because bugs and possible fixes are discovered more quickly)
- because of the already known bugs and the undocumented ones, many users, who have not the experience/knowledge
of the rom state and the whole procedure,will get disappointed and frustrated about cyanogenmod.So this is bad and
unfair for the cm team because they are doing an awesome job.
That's the reason I'm providing only img files and not a complete rom zip.To avoid unexperienced users
To make it clear that's just my opinion/point of view.

tas0s said:
CM7 is not in a functional state right now so I will not make a thread/upload the configs.Also I'm sure that the're going to be roms based
on it as soon as possible
And I don't think that's right.
Please let me explain my opinion:
Take for example the cm6 port.
The cm6 port is not fully tested (I have run it for just a day or two and I haven't tested all the provided features).
So if cedric123 or bitye or any other guy, that is cooking roms (very good roms to be honest) ,
provide roms based on the cm6 port (as already have ) then we will have this situation:
+ the number of users/testers will grow (that's good because bugs and possible fixes are discovered more quickly)
- because of the already known bugs and the undocumented ones, many users, who have not the experience/knowledge
of the rom state and the whole procedure,will get disappointed and frustrated about cyanogenmod.So this is bad and
unfair for the cm team because they are doing an awesome job.
That's the reason I'm providing only img files and not a complete rom zip.To avoid unexperienced users
To make it clear that's just my opinion/point of view.
Click to expand...
Click to collapse
Absolutely right. Besides: from a practical point of view, its will be easier to implement a CM7 port once a CM6 port has successfully tackled the quirks and required changes to adapt the code to the U81*.

CyanogenMod
Interesting: Tom Giordano has merged Huawei U8220/U8230 into the CM repository, which will eventually make it a officially supported device.
See: http://review.cyanogenmod.com/#change,3670

poruid said:
Interesting: Tom Giordano has merged Huawei U8220/U8230 into the CM repository, which will eventually make it a officially supported device.
See: http://review.cyanogenmod.com/#change,3670
Click to expand...
Click to collapse
To talk about the huawei 8220 device
this device is almost the same as ours........
so cant we use some of their drivers and libs to fix the camera and sd mount???

cedric123 said:
To talk about the huawei 8220 device
this device is almost the same as ours........
so cant we use some of their drivers and libs to fix the camera and sd mount???
Click to expand...
Click to collapse
I have looked in tomgiordano's device tree from the begining
We have different camera from the u8220 as I know.
Im working on camera and sdcard bug.Im looking in other device trees also to
see whats wrong.

tas0s said:
I have looked in tomgiordano's device tree from the begining
We have different camera from the u8220 as I know.
Im working on camera and sdcard bug.Im looking in other device trees also to
see whats wrong.
Click to expand...
Click to collapse
Nice please post your archievments and bug fixes and plx make a threath about cm7 cuz i want to know what you fixed so i can get to work too...
Seached a bit
HTC ledgend cm6 mod is running 2.6.29 kernel too and HAD a sd mount bug + camera bug.........
They fixed sd card bug by enabling USB-debugging(Just enable it and it will work????)
Camera i dont know how they fixed it..
Are you planning to fix Mac-adresss too?

i have still problems with sources my repo is not building right my ubuntu 64 is [email protected] up again and the git -u command is not working
cd <cm6 source>/device/
mkdir -p huawei/u8120
git init -u git://github.com/tas0s/cm_huawei_U8120.git ---- not working
cd huawei/u8120
git init
git pull git://github.com/tas0s/cm_huawei_U8120.git
git checkout
Code:
packages/apps/CMParts/src/com/cyanogenmod/cmparts/activities/DisplayActivity.java:96: cannot find symbol
symbol : variable ELECTRON_BEAM_ANIMATION_ON
location: class android.provider.Settings.System
Settings.System.ELECTRON_BEAM_ANIMATION_ON, value ? 1 : 0);
^
packages/apps/CMParts/src/com/cyanogenmod/cmparts/activities/DisplayActivity.java:102: cannot find symbol
symbol : variable ELECTRON_BEAM_ANIMATION_OFF
location: class android.provider.Settings.System
Settings.System.ELECTRON_BEAM_ANIMATION_OFF, value ? 1 : 0);
^
packages/apps/CMParts/src/com/cyanogenmod/cmparts/activities/DisplayActivity.java:108: cannot find symbol
symbol : variable ACCELEROMETER_ROTATE_180
location: class android.provider.Settings.System
Settings.System.ACCELEROMETER_ROTATE_180, value ? 1 : 0);
^
packages/apps/CMParts/src/com/cyanogenmod/cmparts/activities/UIActivity.java:125: cannot find symbol
symbol : variable OVERSCROLL_EFFECT
location: class android.provider.Settings.System
Settings.System.OVERSCROLL_EFFECT, 1);
^
packages/apps/CMParts/src/com/cyanogenmod/cmparts/activities/UIActivity.java:196: cannot find symbol
symbol : variable OVERSCROLL_EFFECT
location: class android.provider.Settings.System
Settings.System.putInt(getContentResolver(), Settings.System.OVERSCROLL_EFFECT,
^
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
11 errors
make: *** [out/target/common/obj/APPS/CMParts_intermediates/classes-full-debug.jar] Error 41
make: *** Waiting for unfinished jobs....
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
java version "1.6.0_22"
Java(TM) SE Runtime Environment (build 1.6.0_22-b04)
Java HotSpot(TM) Server VM (build 17.1-b03, mixed mode)

Would CM5.0.8 eclair be faster than our eclair ROM now??

anryl said:
i have still problems with sources my repo is not building right my ubuntu 64 is [email protected] up again and the git -u command is not working
cd <cm6 source>/device/
mkdir -p huawei/u8120
git init -u git://github.com/tas0s/cm_huawei_U8120.git ---- not working
cd huawei/u8120
git init
git pull git://github.com/tas0s/cm_huawei_U8120.git
git checkout
Code:
packages/apps/CMParts/src/com/cyanogenmod/cmparts/activities/DisplayActivity.java:96: cannot find symbol
symbol : variable ELECTRON_BEAM_ANIMATION_ON
location: class android.provider.Settings.System
Settings.System.ELECTRON_BEAM_ANIMATION_ON, value ? 1 : 0);
^
packages/apps/CMParts/src/com/cyanogenmod/cmparts/activities/DisplayActivity.java:102: cannot find symbol
symbol : variable ELECTRON_BEAM_ANIMATION_OFF
location: class android.provider.Settings.System
Settings.System.ELECTRON_BEAM_ANIMATION_OFF, value ? 1 : 0);
^
packages/apps/CMParts/src/com/cyanogenmod/cmparts/activities/DisplayActivity.java:108: cannot find symbol
symbol : variable ACCELEROMETER_ROTATE_180
location: class android.provider.Settings.System
Settings.System.ACCELEROMETER_ROTATE_180, value ? 1 : 0);
^
packages/apps/CMParts/src/com/cyanogenmod/cmparts/activities/UIActivity.java:125: cannot find symbol
symbol : variable OVERSCROLL_EFFECT
location: class android.provider.Settings.System
Settings.System.OVERSCROLL_EFFECT, 1);
^
packages/apps/CMParts/src/com/cyanogenmod/cmparts/activities/UIActivity.java:196: cannot find symbol
symbol : variable OVERSCROLL_EFFECT
location: class android.provider.Settings.System
Settings.System.putInt(getContentResolver(), Settings.System.OVERSCROLL_EFFECT,
^
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
11 errors
make: *** [out/target/common/obj/APPS/CMParts_intermediates/classes-full-debug.jar] Error 41
make: *** Waiting for unfinished jobs....
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
java version "1.6.0_22"
Java(TM) SE Runtime Environment (build 1.6.0_22-b04)
Java HotSpot(TM) Server VM (build 17.1-b03, mixed mode)
Click to expand...
Click to collapse
Sorry anryl you are right.
Try
git clone git://github.com/tas0s/cm_huawei_U8120.git
EDIT: maybe the pull/checkout procedure is more correct.Updated
For the compilation error just do
cd packages/apps/CMParts && git checkout 69613a248519fed7d971bd6292013d36097d0107
Something is missing in CMParts master
I have updated the README in github with the corrections.Thanx

tas0s said:
Sorry anryl you are right.
Try
git clone git://github.com/tas0s/cm_huawei_U8120.git
EDIT: maybe the pull/checkout procedure is more correct.Updated
For the compilation error just do
cd packages/apps/CMParts && git checkout 69613a248519fed7d971bd6292013d36097d0107
Something is missing in CMParts master
I have updated the README in github with the corrections.Thanx
Click to expand...
Click to collapse
ok it worked so gona start test.ing
EDIT nice first try no rill used boot.img from AOSP
updated ramdisk lets see ---- ok RILL FINE
removed partitions on sdcard left with fat32 only
restoring apps with titanium
calibration ok
gps working
QtADB WORKING fine
for starters AOK thnx

cedric123 said:
Nice please post your archievments and bug fixes and plx make a threath about cm7 cuz i want to know what you fixed so i can get to work too...
Seached a bit
HTC ledgend cm6 mod is running 2.6.29 kernel too and HAD a sd mount bug + camera bug.........
They fixed sd card bug by enabling USB-debugging(Just enable it and it will work????)
Camera i dont know how they fixed it..
Are you planning to fix Mac-adresss too?
Click to expand...
Click to collapse
I have no MAC problems, please explain what's wrong with yours. (Maybe special for me)
USB Debugging not fix the problem here, I tested.

[Q] Compiling CM7: Error parsing XML: syntax error

Hello,
I am trying to build my own CyanogenMod.
My motivation: As a french freemobile customer, i ld like to have EAP-SIM enabled. I have tried everything i could find on internet but couldn't succeed.
So here I am, trying to build CM7 and i have this:
Code:
packages/apps/Settings/res/values-zh-rTW/arrays.xml.orig:201: error: Resource entry backgroundWidget already has bag item ^index_1.
packages/apps/Settings/res/values-zh-rTW/arrays.xml:205: Originally defined here.
packages/apps/Settings/res/values-el/arrays.xml.rej:1: error: Error parsing XML: syntax error
packages/apps/Settings/res/values-nl/arrays.xml.rej:1: error: Error parsing XML: syntax error
make: *** [out/target/common/obj/APPS/Settings_intermediates/src/R.stamp] Error 1
make: *** Waiting for unfinished jobs....
I am using openjava, so i switched to sun-java thanks to update-alternatives (Debian/linux user) and i had something about using -Xlint:deprecated wich is java related.
I can t figure out how to use this "-Xlint" thing.
Thanks in advance.

I ve my answer.
The patch eap-sim-aka adds "SIM" ans "AKA" auth options in the menu. It has to add those options for all languages available so that you can do the selection in wifi menu.
The problem is that the files packages/apps/Settings/res/value-el/arrays.xml and value-nl/arrays.xml are missing the basic auth option entries: Lines 103 and 130 approximately, PEAP TLS and TTLS are missing whereas other languages are fine.
So the patch will add 2 lines (SIM and AKA) in the middle of nowhere breaking balises, etc...
I didn t figure out how to disable support for other language, so i fixed the nl and el language.
A cyanogenmod Dev should fix this in the git.

EAP SIM support in CM 7.2
Hello,
For the same reason as you, I try to build CM 7.2 with eap-sim support.
Did you manage to get it running ?
After solving a couple of issues, I did build the system but I doesn't work. The phone hangs on the cyanogenmmod logo at startup.
While installing the official cm-7.2.0-hallon.zip works fine...
Here are the steps I followed :
1. I did setup my environment (also forcing java version to 1.6) and download cyanogenmod from source repository for gingerbread.
2. I used 'get_rommanager' in android/system/vendor/cyanogen (instead of the not existing 'get-prebuilts' script which is - I guess - for jellybean...).
3. I did 'source build/envsetup.sh'.
4. Then 'breakfast hallon' (for xperia neo phones...).
5. 'extract-files.sh' in device/semc/hallon did retrieve all proprietary blobs but 3 : tiwlan.ini, tiwlan_firmware.bin and tiwlan_firmware_ap.bin.
The first two were, on the phone, in system/etc instead of system/etc/wifi. I copied them in vendor/semc/hallon/proprietary/etc/wifi.
The third one was actually called softap_firmware.bin... I copied and renamed it as vendor/semc/hallon/proprietary/etc/wifi/softap/tiwlan_firmware_ap.bin.
6. I had a missing lib32xxxx (I can't remenber exactly which one...) and added it with apt-get.
7. I added PRODUCT_PACKAGES += libpcsclite in device/semc/hallon/device_hallon.mk (because of a missing makefile rule when compiling).
8. I then applied the following 4 patches for EAP SIM support :
patch -p1 -i eap-sim-aka_0.4.1.patch
patch -p1 -i smartcard-api.patch
patch -p1 -i uicc.patch
patch -p1 -i pcsc_system_service_v098.patch
9. I removed the resulting "array.xml.orig" and "array.xml.rej" files from all "packages/apps/Settings/res" subdirectories (also because of error messages while compiling).
10. Finally, I modified AndroidProducts.mk in vendor/cyanogen/products to keep only the entry corresponding to my phone :
PRODUCT_MAKEFILES := \
$(LOCAL_DIR)/cyanogen_hallon.mk
While compiling, I got lots of warnings (?). At the end, I also had several times the following message :
Sanitizing environment...
Unpacking /home/tourlet/android/system/out/target/product/hallon/cyanogen_hallon-ota-eng.tourlet.zip...
Please install pngcrush, optipng, or pngout
...
Please install pngcrush, optipng, or pngout
Zipping package...
Signing package...
Cleaning up...
Package complete: /home/xxx/android/system/out/target/product/hallon/cm-7-20130305-UNOFFICIAL-hallon.zip
7022f728f18fc1bed559c83c6ec2a309 cm-7-20130305-UNOFFICIAL-hallon.zip
Can somebody please help me through this built ?
I also hope the above details will be of some interest / help for other people trying to get eap sim support on their phone...
Kind regards.

[GUIDE] How to build an unsupported rom using sources from other roms

Hello all and welcome to my first how-to guide
I began the process of learning about ROM about 4 months ago (so excuse this post if there are any inaccuracies and please feel free to correct me in the comments - I will absolutely update this post to ensure it has the best information)
Whilst I was trying to learn, I noticed there was a lack of information regarding how the actual build process works. Many roms will provide instructions allowing you to build your own unofficial version for one of their official devices, but very rarely do they inform you as to how you may do this for a device not officially supported.
This is what I shall try and explain here.
Building for a newer version of android is another challenge, so this guide will focus on building an unsupported rom from device sources that support the same version of android (e.g building Lineage oreo from AOSCP oreo sources etc)
Requirements
A relatively fast PC with a least 4 cores (less may work but it will take a long time)
At least 8GB ram
A swap-file set up in the event that your ram is fully filled
A significant amount of storage (each build can take 150-200GB)
Set up your PC for building
Firstly, allocate Jack enough memory to complete the build process by running
Code:
export ANDROID_JACK_VM_ARGS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx4G"
And adding that line to your ~/.bashrc file
Also (optional) enable ccache by running
Code:
export USE_CCACHE=1
and adding that to your ~/.bashrc
If you choose to use ccache, also allocate a set amount of memory to use with
Code:
ccache -M $G
Where $ is a value of your choice between 50 and 100
First things first, we need to download the main source code for the target rom
Firstly you need to sync the sources from the manifest of your chosen rom. This will normally be called android, or manifest (or something similar) and will contain some xml files layed out like the example local manifest below
Find this repo and copy the link. Then move to the location you wish the entire android code to be stored, and then perform the following command
Code:
repo init -u <url of manifest repo>.git -b <branch you want to build>
e.g. for lineage 15.1 it would be
Code:
repo init -u https://github.com/LineageOS/android.git -b lineage-15.1
Finally, run "repo sync" to download the source code. It is very large (approximately 30GB) so it will take a while. Should you need to cancel this, a simple CTRL+C will stop it, and it will continue from where it stopped next time you run repo sync
Now we need to understand which components we need to build a custom rom.
We need (anything inside the <> needs to be replaced with relevant information for your device)
A device tree. This contains all the information needed to configure the rom build to your device's needs. Often this comes as more than one repo (one for your exact device and one for the general model - e.g. for my LG G4 H815, we have the h815 repo and the g4-common repo). The format for these repos is generally android_device_<vendor>_<device model>
A kernel. This contains all the drivers and more needed for your device to be able to run Android. Often these are named using your device's chipset name and follow the format android_kernel_<vendor>_<chipset>, although occasionally they can use your model name instead of the chipset.
Proprietary blobs. These are the closed source blobs that come bundled in your OEM software and contain the non-OSS (open source software) drivers for your device. They normally come in a repo labeled proprietary_vendor_<vendor> which normally contains blobs for all the devices released by that vendor (that are supported).
Any other repos specified by the dependencies file (more on that later)
All of the above repos go into the path specified in the name - for example, android_device_<vendor>_<device model> will go into the device/<vendor>/<device model> directory.
To sync these, you should create a local manifest in the <android source>/.repo/local_manifests/ folder. Name it anything you like (make sure it's an xml file) and fill it out like so
Code:
<manifest>
<remote name="<your chosen name for this url>"
fetch="<url to your git organisation>"
revision="<branch if different to the one used in repo init (otherwise, miss out revision)>"
<project name="<name of repo inside git org>" path="<destination of the repo>" remote="<remote name chosen earlier>" revision="<revision if different to one specified above>" />
</manifest>
After adding this manifest, re-run repo sync to pull the extra repos
Understanding the device tree.
Inside the device tree (model specific one if there are more than one) there will be a file with a naming scheme along the lines of <rom brand>.mk (e.g. lineage.mk). This is the starting file for your device and is detected when you begin a build for your device. (Pie roms are currently using AndroidProducts.mk as a placeholder containing a link to this file). It contains links to the common configuration of your device (phone, tablet etc) at the top, and also specifies the name of the product (normally <rom>_<device model>) which is part of the command used to build the device.
There will also be some build prop overrides - these contain information like the device name and the build fingerprint (used to verify to google what device you are - lots of devices leave this as the last stock fingerprint to pass google CTS)
In most device trees, there will also be a <rom>.dependencies file. This contains all the additional repos needed to build for your particular device. This file is parsed automatically if you use the official methods and use the breakfast command. If you do it manually, they must be added to a local manifest.
The <device model>.mk file is what defines what open source packages need to be built in the build. Devices either include everything in this file or they can link to a product folder in which every .mk file is included.
BoardConfig(Common).mk includes configuration options for the device, and often links to config files to inform the builder of certain flags that need to be applied for the build. Similarly to the <device model>.mk, this is often linked to a board folder containing configurations
The kernel
The kernel is a massive topic and one that I cannot explain in depth here. However, for rom building it is useful to know that the defconfigs used to build a kernel are located in kernel/<chipset/device model>/arch/<arm or arm64 depending on device>/configs and the one used is normally in the format <rom>_<device model>_defconfig (e.g my lineage one is lineageos_h815_defconfig). Should you wish to change the name, simply change the name and alter the defconfig name in the BoardConfig.mk for your particular device.
So...to the main part - how do you build a rom.
Essentially there are a few main commands that are spoken about
"source build/envsetup.sh". This runs the builder script and loads all the custom commands.
"breakfast". This simply pulls the device specific code from the official repos. You do not need this if you are building unofficially
"brunch". This effectively performs breakfast, but assuming everything is synced correctly, it will finish without an issue. Then it will go on to begin the build. Normally brunch is run as brunch <rom name>_<device model>-userdebug (or eng if you are developing). User is used for OEM releases but most roms use userdebug as it is slightly more relaxed on conditions
To build a rom from unsupported sources requires a bit of thought. Firstly, ensure you have all the dependencies synced (hopefully from the target rom) as well as the device sources.
Then you need to go into the device tree and modify
The <rom>.mk file to now be renamed to your new rom.
You need to enter that file and modify any stuff relating to your old ROM look for your new rom instead (device type configurations are normally the main one here).
You need to remove any stuff inside your device tree relating to features not in your new rom.
Then run "source build/envsetup.sh"
"brunch <rom>_<device model>-userdebug"
This will hopefully begin the build and assuming everything is setup correctly, should continue through to finish building the rom of your choice
If you have any questions/issues with this process, I will be happy to answer to the best of my ability
Also, big thanks to the LineageOS guide for giving me a basis upon which to base this guide on

PRODUCT_COMPATIBILITY_MATRIX_LEVEL_OVERRIDE directly
Specify Framework Compatibility Matrix Version in device manifest by adding a target-level attribute to the root element <manifest>. If PRODUCT_COMPATIBILITY_MATRIX_LEVEL_OVERRIDE is 26 or 27, you can add "target-level"="1" to your device manifest instead.
how to implement this?

nadeem_naddy said:
PRODUCT_COMPATIBILITY_MATRIX_LEVEL_OVERRIDE directly
Specify Framework Compatibility Matrix Version in device manifest by adding a target-level attribute to the root element <manifest>. If PRODUCT_COMPATIBILITY_MATRIX_LEVEL_OVERRIDE is 26 or 27, you can add "target-level"="1" to your device manifest instead.
how to implement this?
Click to expand...
Click to collapse
Sorry for the late reply
What Android version are you building (this determines the api level). Also, what rom and device (links are helpful as I can see what it going on)
I would imagine you need something like https://github.com/LineageOS/androi...mmit/c24f0fff1fb1fc46d638e91777281ec7efc3e239

ThePiGuy said:
Sorry for the late reply
What Android version are you building (this determines the api level). Also, what rom and device (links are helpful as I can see what it going on)
I would imagine you need something like https://github.com/LineageOS/androi...mmit/c24f0fff1fb1fc46d638e91777281ec7efc3e239
Click to expand...
Click to collapse
i did not get the way to override or more precisely i dont know where to put the code to over ride this flag so i simply commented this in BoardConfig.mk itself. as it says its deprecated.
now i encounter this -
66% 2/3] glob frameworks/base/core/java/**/*.java
ninja: error: unknown target 'nitrogen_X00TD'
01:34:03 ninja failed with: exit status 1
it would be great help if you let me know from where does frameworks pick the device info in device tree. where do we need to set path.. i am building nitrogen pie for my device X00TD. thanks

the latest issue am facing is -
ninja: error: '/home/matin1117/nitrogen/out/target/common/obj/java_libraries/qcrilhook_intermediates/classes.jar', needed by '/home/matin1117/nitrogen/out/target/common/obj/packaging/boot-jars-package-check_intermediates/stamp', missing and no known rule to make it.
please suggest a fix.
thanks,
Nadeem

nadeem_naddy said:
the latest issue am facing is -
ninja: error: '/home/matin1117/nitrogen/out/target/common/obj/java_libraries/qcrilhook_intermediates/classes.jar', needed by '/home/matin1117/nitrogen/out/target/common/obj/packaging/boot-jars-package-check_intermediates/stamp', missing and no known rule to make it.
please suggest a fix.
thanks,
Nadeem
Click to expand...
Click to collapse
Is Pie ready for your device. For most ROMs it requires a lot of cherry-picking etc before it will build

ThePiGuy said:
Is Pie ready for your device. For most ROMs it requires a lot of cherry-picking etc before it will build
Click to expand...
Click to collapse
yes the device have many pie roms but i want to build nitrogen. i
can see niteogen os pie built for many other phones using sd636.

nadeem_naddy said:
yes the device have many pie roms but i want to build nitrogen. i
can see niteogen os pie built for many other phones using sd636.
Click to expand...
Click to collapse
Pie is an oddball case at the moment. Many ROMs work if you cherry-picking fixes off Gerrit (I built Pie Lineage for my G4 but it required about 20 cherry-picks off the lineage Gerrit before it built)
In your case, it looks like you are possibly missing a ril-caf repo (look in the nos.xml and you will see only the non-caf repo is being synced). You can add the caf one but it's possible it isn't ready yet

thanks a lot, i can see one ril related entry in nos.xml. let me do some research on it.
thanks a lot for all your help buddy.

iam facing this error ? can u help please..... ?
see attachment ! 
 @ThePiGuy
Thanks in advance

vignesh95 said:
iam facing this error ? can u help please..... ?
see attachment !
@ThePiGuy
Thanks in advance
Click to expand...
Click to collapse
Ok can you show me the result of
Code:
ls device/oneplus

here u have it (see attachment)
ThePiGuy said:
Ok can you show me the result of
Code:
ls device/oneplus
Click to expand...
Click to collapse
Hi @ThePiGuy

vignesh95 said:
Hi @ThePiGuy
Click to expand...
Click to collapse
ok. And now
Code:
ls device/oneplus/oneplus2

here u have it (see attachment)
ThePiGuy said:
ok. And now
Code:
ls device/oneplus/oneplus2
Click to expand...
Click to collapse
revised 
 @ThePiGuy

vignesh95 said:
revised
@ThePiGuy
Click to expand...
Click to collapse
Ok. Sorry for the late reply.
You need to open the AndroidProducts.mk file and rename the lineage_oneplus2.mk line to aosp_oneplus2.mk.
You also need to change the lineage_oneplus2.mk file so it is called aosp_oneplus2.mk, and inside it you need to change any occurrences to aosp (basically you are rebranding the device tree to use the aosp versions rather than the lineage branded ones)

ThePiGuy said:
Ok. Sorry for the late reply.
You need to open the AndroidProducts.mk file and rename the lineage_oneplus2.mk line to aosp_oneplus2.mk.
You also need to change the lineage_oneplus2.mk file so it is called aosp_oneplus2.mk, and inside it you need to change any occurrences to aosp (basically you are rebranding the device tree to use the aosp versions rather than the lineage branded ones)
Click to expand...
Click to collapse
thanks! @ThePiGuy
now i am getting this error
[944/944] including vendor/qcom/opensource/dataservices/Android.mk ...
device/oppo/common/configpanel/Android.mk: error: ConfigPanel (APPS android-arm64) missing org.lineageos.platform.internal (JAVA_LIBRARIES android-arm64)
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.
build/make/core/main.mk:837: error: exiting from previous errors.
20:05:06 ckati failed with: exit status 1
#### failed to build some targets (03:05 (mm:ss)) ####
Please help !

vignesh95 said:
thanks! @ThePiGuy
now i am getting this error
[944/944] including vendor/qcom/opensource/dataservices/Android.mk ...
device/oppo/common/configpanel/Android.mk: error: ConfigPanel (APPS android-arm64) missing org.lineageos.platform.internal (JAVA_LIBRARIES android-arm64)
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.
build/make/core/main.mk:837: error: exiting from previous errors.
20:05:06 ckati failed with: exit status 1
#### failed to build some targets (03:05 (mm:ss)) ####
Please help !
Click to expand...
Click to collapse
Sorry, I don't think I can help with that
Make sure your build environment is set up correctly (wiki.lineageos.org/devices/oneplus2/build will help with that) and also ensure you are using Pie device sources (from what I have gathered you are trying to build Pie, but if you are using device trees and kernel from Oreo or anything else then it will require much more than this guide details)

Hi bro, i want to build lineage OS for unsupported device(Xiaomi Vince), please give me the step
---------- Post added at 08:57 AM ---------- Previous post was at 07:58 AM ----------
iam get error like this
including vendor/lineage/vendorsetup.sh
build/make/core/envsetup.mk:264: error: TARGET_ARCH not defined by board config: device/xiaomi/vince/BoardConfig.mk.
15:41:16 dumpvars failed with: exit status 1
Device vince not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
Repository for vince not found in the LineageOS Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml.
build/make/core/envsetup.mk:264: error: TARGET_ARCH not defined by board config: device/xiaomi/vince/BoardConfig.mk.
15:41:18 dumpvars failed with: exit status 1
build/make/core/envsetup.mk:264: error: TARGET_ARCH not defined by board config: device/xiaomi/vince/BoardConfig.mk.
15:41:19 dumpvars failed with: exit status 1
** Don't have a product spec for: 'aosp_vince'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
Click to expand...
Click to collapse

Help me
Hey
I have a common device source, which has linked my device to 3 more configuration files. I tried to change lineage to other rom in every possible location I can find but on building this error comes into action.
The error is same for every AOSP based rom
[email protected]:~/AEX$ mka aex -j4
vendor/aosp/config/bootanimation.mk:32: warning: Target bootanimation res is undefined, using generic bootanimation
============================================
▄▄▄ ▓█████ ▒██ ██▒
▒████▄ ▓█ ▀ ▒▒ █ █ ▒░
▒██ ▀█▄ ▒███ ░░ █ ░
░██▄▄▄▄██ ▒▓█ ▄ ░ █ █ ▒
▓█ ▓██▒░▒████▒▒██▒ ▒██▒
▒▒ ▓▒█░░░ ▒░ ░▒▒ ░ ░▓ ░
▒ ▒▒ ░ ░ ░ ░░░ ░▒ ░
░ ▒ ░ ░ ░
░ ░ ░ ░ ░ ░
AospExtended-v6.3 9
============================================
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=9
EXTENDED_MOD_VERSION=AospExtended-v6.3-20190311-0935-UNOFFICIAL
TARGET_PRODUCT=aosp_fortuna3g
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv8-a
TARGET_CPU_VARIANT=cortex-a53
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-4.15.0-20-generic-x86_64-Linux-Mint-19
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=PQ2A.190205.001
OUT_DIR=/home/jmpfbmx/AEX/out
PRODUCT_SOONG_NAMESPACES= hardware/qcom/audio-caf/msm8916 hardware/qcom/display-caf/msm8916 hardware/qcom/media-caf/msm8916
============================================
[1/1] /home/jmpfbmx/AEX/out/soong/.minibootstrap/minibp /home/jmpfbmx/AEX/out/soong/.bootstrap/build.ninja
[55/56] glob prebuilts/ndk/stl.bp
[80/80] /home/jmpfbmx/AEX/out/soong/.bootstrap/bin/soong_build /home/jmpfbmx/AEX/out/soong/build.ninja
/home/jmpfbmx/AEX/out/build-aosp_fortuna3g-cleanspec.ninja is missing, regenerating...
vendor/aosp/config/bootanimation.mk:32: warning: Target bootanimation res is undefined, using generic bootanimation
/home/jmpfbmx/AEX/out/build-aosp_fortuna3g.ninja is missing, regenerating...
vendor/aosp/config/bootanimation.mk:32: warning: Target bootanimation res is undefined, using generic bootanimation
[25/1110] including development/build/Android.mk ...
development/build/build_android_stubs.mk:43: warning: android_stubs_current
development/build/build_android_stubs.mk:43: warning: metalava_android_stubs_current metalava_android_stubs_current
development/build/build_android_stubs.mk:43: warning: android_system_stubs_current
development/build/build_android_stubs.mk:43: warning: android_test_stubs_current
development/build/build_android_stubs.mk:43: warning: metalava_android_system_stubs_current metalava_android_system_stubs_current
development/build/build_android_stubs.mk:43: warning: metalava_android_test_stubs_current metalava_android_test_stubs_current
[271/1110] including frameworks/av/camera/Android.mk ...
frameworks/av/camera/cameraserver/Android.mk:18: warning: Target has integrated cameraserver into mediaserver. This is weakening security measures introduced in 7.0
[607/1110] including system/sepolicy/Android.mk ...
system/sepolicy/Android.mk:88: warning: Be careful when using the SELINUX_IGNORE_NEVERALLOWS flag. It does not work in user builds and using it will not stop you from failing CTS.
[1110/1110] including vendor/samsung/serranovexx-common/Android.mk ...
bootable/recovery/Android.mk: error: recovery (EXECUTABLES android-arm) missing libhealthd.lineage (STATIC_LIBRARIES android-arm)
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.
device/samsung/qcom-common/doze/Android.mk: error: SamsungDoze (APPS android-arm) missing org.lineageos.platform.internal (JAVA_LIBRARIES android-arm)
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.
hardware/interfaces/health/1.0/default/Android.mk: error: [email protected] (SHARED_LIBRARIES android-arm) missing libhealthd.lineage (STATIC_LIBRARIES android-arm)
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.
hardware/samsung/AdvancedDisplay/Android.mk: error: AdvancedDisplay (APPS android-arm) missing org.lineageos.platform.internal (JAVA_LIBRARIES android-arm)
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.
system/core/healthd/Android.mk: error: charger (EXECUTABLES android-arm) missing libhealthd.lineage (STATIC_LIBRARIES android-arm)
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.
build/make/core/main.mk:850: error: exiting from previous errors.
10:40:35 ckati failed with: exit status 1
build/make/core/main.mk:21: recipe for target 'run_soong_ui' failed
make: *** [run_soong_ui] Error 1
#### failed to build some targets (05:24 (mm:ss)) ####

itexpert.120 said:
Hey
I have a common device source, which has linked my device to 3 more configuration files. I tried to change lineage to other rom in every possible location I can find but on building this error comes into action.
The error is same for every AOSP based rom
[email protected]:~/AEX$ mka aex -j4
vendor/aosp/config/bootanimation.mk:32: warning: Target bootanimation res is undefined, using generic bootanimation
Click to expand...
Click to collapse
Ok so what it looks like - did you sync only the device trees and any common ones and then use the "brunch" or "breakfast" command to download the rest of the repos. If so, then it's still pulled the repos from lineage (in all the dependency files, you can see where they come from)
If you did, try finding the AEX equivalent repo and replacing that in the .dependency file that it is referred to in.
If this is not what you did, please detail what you did to get your environment

[Android 10] Add external lib to iptables

Hello everyone!
I want to use extra flag in iptables (connlabel), but in default make this extension is not available. I found in iptables/extentions/Android.bp file this code:
gensrcs {
name: "libext_srcs",
tool_files: ["filter_init"],
cmd: "$(location filter_init) $(in) > $(out)",
output_extension: "c",
srcs: ["libxt_*.c"],
exclude_srcs: [
// Exclude some modules that are problematic to compile (types/headers)
"libxt_TCPOPTSTRIP.c",
"libxt_connlabel.c",
"libxt_cgroup.c",
"libxt_dccp.c",
"libxt_ipvs.c",
],
So i delete "libxt_connlabel.c" from this list, and while compilation I have this error:
out/soong/.intermediates/external/iptables/extensions/libext_srcs/gen/gensrcs/external/iptables/extensions/libxt_connlabel.c:8:10: fatal error: 'libnetfilter_conntrack/libnetfilter_conntrack.h' file not found
#include <libnetfilter_conntrack/libnetfilter_conntrack.h>
I see this library in path: external/libnetfilter_conntrack/include/libnetfilter_conntrack/libnetfilter_conntrack.h but I don't know how to add this lib to Android.bp
Thanks for any help!

I think that is the wrong modification to make.
Instead you should undo that change and just enable these module(s) for your device's defconfig:
CONFIG_NF_CONNTRACK_LABELS=y
and also maybe:
CONFIG_NETFILTER_XT_MATCH_CONNLABEL=y
Here are examples for a random devices defconfigs that I found:
https://github.com/search?q=org:Lin...TRACK_LABELS=y"+filename:*defconfig&type=Code
Note that I have personally not tried building with these modules before and I also don't know what device kernel you are building on, so you'll need to experiment with the different combination of config changes above to see what works for your device kernel.
You can look at this Makefile in your particular device kernel's tree, to see what netfilter CONFIG_ flags are available for you to enable (do not modify this file, again only modify your device's defconfig to enable it):
net/netfilter/Makefile
For example:
android_kernel_moto_shamu/Makefile at lineage-17.0 · LineageOS/android_kernel_moto_shamu
Contribute to LineageOS/android_kernel_moto_shamu development by creating an account on GitHub.
github.com