Related
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.
CyanogenMod 7.1 for Huawei U8120
Latest release: v1.4_t [15 November 2011]
This is an unofficial port of cm7 (gingerbread) 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 cm7 port, it is not fully tested
and it has some bugs.
Any help it would be great.
Kernel: 2.6.32-9 (based on subpsyke's u8160 sources)
Jit enabled
Android : 2.3.7 / CM 7.1.0
Working:
RIL
Audio
Bluetooth
Wi-Fi
Sensors
D-pad
UC/OC Kernel (30-768MHZ)
GPS
Camera
Video recording
Calibration
Headphones
Keylights
SDCard mount via notification bar
Bugs/Not working/TODO:
Missing FM
Camera app lag/battery consumption during and after use
For any bugs you find please provide a logcat output if you can.
Releases:
Release 1.4_t - 15 November 2011
Release 1.3_t - 16 October 2011
Release 1.2_t - 2 October 2011
no overclocked kernel. Apply after the 1.2_t release
Release 1.1_t - 30 September 2011
no overclocked kernel. Apply after the 1.1_t release
Release 1.0_t - 28 September 2011
Latest Google Apps package: Google Apps (20110613)
ClockworkMod 5.0.2.7: recovery.img Latest clockworkmod.It seems to work alright.
ClockworkMod 5.0.2.3: recovery.img
Installation:
Reboot your phone to bootloader mode, and then flash with:
Code:
fastboot flash recovery recovery.img
fastboot reboot
Im not responsible for any damage that this software may cause on your device.Dont expect support.
Source code:
device tree - based on joilaroi's work
kernel
One big thank you to the awesome cyanogenmod team for their work and
the rest of the huawei ports devs
Changelog:
28/09/11 - initial release
30/09/11
synced with latest cyanogenmod sources (not RC1 anymore )
fixed keylights
fix screen on/off animation
fix battery drain
better network performance
02/10/11
synced with latest cyanogenmod sources (android 2.3.7 )
fix GPS
re-enable in-call-ui
updated kernel 30MHz - 768MHz
16/10/11
synced with latest cyanogenmod sources (android 2.3.7 )
minor fixes for more responsive UI (I hope)
precalibrated in kernel - no calibration needed.
Use calibration app from kallt kaffe's port in place of old TSCalibration app
updated kernel with compache,tun modules,AHB overclock etc
15/11/11
synced with latest cyanogenmod sources (android 2.3.7 )
fixed sdcard mount to pc
I call this firmware (phone part) works? microphone and speaker works? (sorry for my english)
Downloading ···
I will test it for a Huawei U8100-5...
-----
Men, I think I am stupid, I don't understand how to install this rom, can you help me...
¬¬
can you tell me how to install?
failed...
Tried to install through clockwork recovery with and without signature verification
With:
Finding update package...
Opening update package...
Verifying update package...
E: signature verification failed
Installation aborted
Without
Too quick for me to read it but i think
Finding update package...
Opening update package...
Verifying update package...
Then it just disappears and goes to the main screen without a log.
Tried with Amon Ra as well, same results but it did mention something about 4 files missing.
To the install questions above, u need to install a custom recovery onto ur phone so that you can install .zip files and then install the file given. look at the other custom ROM's for more info on installing a custom recovery.
Hope this helps
Edit: This is on U8120 btw
Its not for flashing as rom it is probably just packed system.img
Sent from my U8120 using XDA Premium App
Its not for flashing via recovery guys.
They are flashed with fastboot.
And is not for daily use etc
ahhh ok thanks ill try that way, i didn't check whats inside the folder...XD
Hey update on my testing, two things that shock me!
A: The speed (Uber slow) but u mentioned that already
B: THE D-PAD WORKS! on U8120. I didnt think it would.....
URL for people that also want to test with zip/dnt know how to do fastboot way:
http://www.mediafire.com/?9x1uxdyeocbcf59
I GOT error 41 compiling
i got dead ubuntu again
reinstalling 2day again
Notification bar rather than scroll through, GPS-and not working, camera not working
anryl said:
I GOT error 41 compiling
i got dead ubuntu again
reinstalling 2day again
Click to expand...
Click to collapse
Can you tell exactly the error message?
Reinstall Ubuntu?Mate thats the window's way of fixing things
Maybe some package is missing or something is misconfigured.
penev89 said:
Notification bar rather than scroll through, GPS-and not working, camera not working
Click to expand...
Click to collapse
The notification bar is unreachable due to missing screen calibration.I have added the GPS bug in the initial post.
i installed qt4 then removed some pkg's than installed nvidia ---> this ****ed my desktop so its faster to reinstall the whole junk compiling now to see if error's continue
btw: windoze pwr-user
Code:
target Java: AccountAndSyncSettings (out/target/common/obj/APPS/AccountAndSyncSettings_intermediates/classes)
target Java: AndroidTerm (out/target/common/obj/APPS/AndroidTerm_intermediates/classes)
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: packages/apps/AndroidTerm/src/jackpal/androidterm/Term.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
target Java: ApplicationsProvider (out/target/common/obj/APPS/ApplicationsProvider_intermediates/classes)
target Java: javax.obex (out/target/common/obj/JAVA_LIBRARIES/javax.obex_intermediates/classes)
target Java: Browser (out/target/common/obj/APPS/Browser_intermediates/classes)
target Java: CMParts (out/target/common/obj/APPS/CMParts_intermediates/classes)
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: packages/apps/ADWLauncher/src/com/android/launcher/Launcher.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
target Java: CMStats (out/target/common/obj/APPS/CMStats_intermediates/classes)
target Java: CMUpdateNotify (out/target/common/obj/APPS/CMUpdateNotify_intermediates/classes)
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.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
target Java: CMWallpapers (out/target/common/obj/APPS/CMWallpapers_intermediates/classes)
target Java: android.test.runner (out/target/common/obj/JAVA_LIBRARIES/android.test.runner_intermediates/classes)
target Java: CalendarProvider (out/target/common/obj/APPS/CalendarProvider_intermediates/classes)
target Java: CertInstaller (out/target/common/obj/APPS/CertInstaller_intermediates/classes)
Note: packages/apps/CertInstaller/src/com/android/certinstaller/CertInstaller.java uses or overrides 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.
target Java: com.android.phone.common (out/target/common/obj/JAVA_LIBRARIES/com.android.phone.common_intermediates/classes)
Note: packages/providers/CalendarProvider/src/com/android/providers/calendar/CalendarAppWidgetService.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
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.
target Java: ContactsProvider (out/target/common/obj/APPS/ContactsProvider_intermediates/classes)
target Java: DSPManager (out/target/common/obj/APPS/DSPManager_intermediates/classes)
target Java: DefaultContainerService (out/target/common/obj/APPS/DefaultContainerService_intermediates/classes)
target Java: DownloadProvider (out/target/common/obj/APPS/DownloadProvider_intermediates/classes)
target Java: DownloadProviderUi (out/target/common/obj/APPS/DownloadProviderUi_intermediates/classes)
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
target Java: DrmProvider (out/target/common/obj/APPS/DrmProvider_intermediates/classes)
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
target Java: Email (out/target/common/obj/APPS/Email_intermediates/classes)
target Java: FileManager (out/target/common/obj/APPS/FileManager_intermediates/classes)
target Java: Gallery (out/target/common/obj/APPS/Gallery_intermediates/classes)
Note: packages/providers/DrmProvider/src/com/android/providers/drm/DrmPushReceiver.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
target Java: HTMLViewer (out/target/common/obj/APPS/HTMLViewer_intermediates/classes)
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: packages/apps/FileManager/src/org/openintents/filemanager/IconifiedTextListAdapter.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
target Java: LiveWallpapers (out/target/common/obj/APPS/LiveWallpapers_intermediates/classes)
target Java: LiveWallpapersPicker (out/target/common/obj/APPS/LiveWallpapersPicker_intermediates/classes)
target Java: MagicSmokeWallpapers (out/target/common/obj/APPS/MagicSmokeWallpapers_intermediates/classes)
target Java: MediaProvider (out/target/common/obj/APPS/MediaProvider_intermediates/classes)
target Java: Mms (out/target/common/obj/APPS/Mms_intermediates/classes)
target Java: SoundRecorder (out/target/common/obj/APPS/SoundRecorder_intermediates/classes)
Note: packages/providers/MediaProvider/src/com/android/providers/media/MediaScannerService.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: packages/providers/MediaProvider/src/com/android/providers/media/MediaProvider.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
target Java: PackageInstaller (out/target/common/obj/APPS/PackageInstaller_intermediates/classes)
target Java: Pacman (out/target/common/obj/APPS/Pacman_intermediates/classes)
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.
Note: packages/apps/PackageInstaller/src/com/android/packageinstaller/UninstallerActivity.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
target Java: Phone (out/target/common/obj/APPS/Phone_intermediates/classes)
target Java: PicoTts (out/target/common/obj/APPS/PicoTts_intermediates/classes)
target Java: Protips (out/target/common/obj/APPS/Protips_intermediates/classes)
target Java: Provision (out/target/common/obj/APPS/Provision_intermediates/classes)
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.
target Java: Settings (out/target/common/obj/APPS/Settings_intermediates/classes)
target Java: SettingsProvider (out/target/common/obj/APPS/SettingsProvider_intermediates/classes)
target Java: SpareParts (out/target/common/obj/APPS/SpareParts_intermediates/classes)
packages/apps/Phone/src/com/android/phone/CallCard.java:199: cannot find symbol
symbol : variable callTypeLabel
location: class com.android.phone.R.id
mCallTypeLabel = (TextView) findViewById(R.id.callTypeLabel);
^
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.
1 error
make: *** [out/target/common/obj/APPS/Phone_intermediates/classes-full-debug.jar] Error 41
make: *** Waiting for unfinished jobs....
Note: frameworks/base/packages/SettingsProvider/src/com/android/providers/settings/DatabaseHelper.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
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.
compiled ascend no error
if libril removed no errors hmm
libril back no errors - strange
the ascend tree have fixed smthing ?
make clean
compile again error
working in Huawei U8100-5
does not work in videos
does not work in games like the SNESOID
camera not working
can not take pictures
@anryl, some encoding problem perhaps?
Try to run dos2unix on all files (if u're on linux).
Cheers.
Wish it will work with u8110!!
minisergium said:
Wish it will work with u8110!!
Click to expand...
Click to collapse
Thanks for making this ROM!!!
I was curius about the overschroll effect in cm7 is this present in this ROM or not? Its one of the things i like most about cm7
tas0s said:
CM7 for Huawei U8120
This is an unofficial port of cm7 (gingerbread) 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 cm7 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.
Any help it would be great.
Kernel: kalt kaffe's 2.6.29
Jit enabled
Android : 2.3.3 / CM7
Working:
RIL
Audio
Bluetooth
Wifi
Key lights
Sensors
Bugs/Not working/TODO:
Camera
SDCard mount via notification bar
Broken layout in usb mass storage screen & dialer
GPS
Missing AGPS
Missing FM
Slow performance
Screen calibration support
For any bugs you find please provide a logcat output if you can.
Releases:
Release 1.0
Im not responsible for any damage that this software may cause on your device.Dont expect support.
One big thank you to the awesome cyanogenmod team for their work
github
Click to expand...
Click to collapse
Hello, can develop the rom-based miui it?
http://en.miui.com/download.html
Get into bootlop,waiting for next update and hope for best.
Download Sources Huawei Sonic U8650
Download the Kernel Sources of Huawei Sonic from this link ---> Here
Direct Link ---> Here
There are about 430 mb as the source contains more Huawei terminal.
Configuration file (. Config)
This file is not present inside the Huawei's rom and not present into boot.img.
But we can find this file into the kernel that we have previously downloaded.
We can find this file in this directory ---> kernel/arch/arm/configs/hw_msm7227_defconfig of 70,4 kb
Take this file ---> hw_msm7227_deconfig copy it into the kernel directory and now change in .config.
hw_msm7227_deconfig ---> .config
Done.
Now we are ready to compile our kernel.
Good Work.
Bye
where can i download the kernel sources for sonic?
carlonchete said:
where can i download the kernel sources for sonic?
Click to expand...
Click to collapse
Try Direct link.....
Hello.
I have downloaded these sources. Setting the crossdev environment in Gentoo was a breezed, and I had no problem compiling the kernel. Well, to tell the truth, I got an error, but was able to pass through by setting CONFIG_NO_ERROR_ON_MISMATCH=y'
Code:
LD vmlinux.o
MODPOST vmlinux.o
WARNING: vmlinux.o(.text+0xe474): Section mismatch in reference from the function msm_map_io.clone.0() to the (unknown reference) .init.data:(unknown)
The function msm_map_io.clone.0() references
the (unknown reference) __initdata (unknown).
This is often because msm_map_io.clone.0 lacks a __initdata
annotation or the annotation of (unknown) is wrong.
To build the kernel despite the mismatches, build with:
'make CONFIG_NO_ERROR_ON_MISMATCH=y'
(NOTE: This is not recommended)
make[1]: *** [vmlinux.o] Error 1
make: *** [vmlinux.o] Error 2
I have no idea if that can have further implications, but that's not what I wanted to ask you anyway.
My question is, what do I do with this thing now?
I've managed to cat /dev/mtd/mtd0 to /sdcard/mtd0, but that gives me a file that is not recognized by Gentoo as an fs of any kind. It could be some kind of custom file with a kernel plus an initrd inside of it, because that's what I read some mobiles do on their boot partition, but there's really no info about this, that I can find.
I guess that if you posted to compile the kernel you also know how to disassemble this boot image. So, can you, please, give me any pointers?
PS. I also tried to mount this as yaffs2, as that seems to be the format for the other fs's inside the phone, as per the output for "mount | grep mtd". Unfortunately, in linux, it doesn't work (yes, I compile yaffs2 myself as a kernel module). I also tried mounting it in my phone, two times, the result was that the boot was corrupted and the next time I booted my phone I had to reflash it with the stock rom to get it booting again with factory settings
Whenever there's an over-the-air (OTA) update sent-out or made available (either leaked or official), there's always a large number of users that end-up reporting that their installations have failed with the infamous and dreaded "E:Error in /sdcard/xxx.zip (Status 7) installation aborted." error message. So, I decided to try to write an app that would help folks figure-out what the issues might be so that they can get their OTA update installed.
The OTA Verifier app can be used to evaluate an over-the-air (OTA) update.zip or other flashable .zip file before you attempt the install or afterwards to help you figure-out why the installation may have failed. OTA Verifier will point-out what files and conditions are being tested so that you can more easily attempt to correct these issues.
Play Market Link (free!): OTA Verifier (beta)
Do I have to be rooted to use this?
No, but rooted devices will have more conditions that the app will be able to test/evalute because it will have access to protected files that non-rooted devices don't.
Will the app actually do the installation or change anything on my device?
No. The app will only evaluate the expressions and conditions contained inside the updater-script file inside the .zip file that's trying to be installed. None of the functions or commands that try to modify your device (i.e., delete/patch/format/extract, etc.) will be evaluated or executed. The app basically operates in "read-only" mode with respect to the .zip file being evaluated.
Will this app work on older devices or flashable .zip files that use the amend update-script files?
No, this app evaluates and interprets the newer edify updater-script files (notice the "r" in "updater").
How do I use this app?
Install and launch the app
Click the "Select File" button and navigate to desired .zip file
Long-press (press and hold) the file entry for the desired .zip file
Click the "Verify OTA .zip" file pop-up
Wait for the app to process the file (should take under a minute, depending on your device)
View the displayed results (text will also be copied to the clipboard)
Miscellaneous info:
1. Savvy root users probably already know that after a failed .zip file installation, you should be able to view the /cache/recovery/log file to view the information about what might have failed. OTA Verifier will try to uncover all of the issues and not just the first one that causes the installation to fail.
2. While I wrote this app principally to evaluate OTA update.zip files, the edify updater-script files are used and written by ROM devs and others who created flashable .zip files. This app can be used to evaluate those file's updater-script files, too.
How does this all work?
Here's the basic outline/structure of what the app does:
1. the .zip file is selected by the user via the file selector
2. list of frozen system apps are identified for later reporting
3. the updater-script file is extracted from the META-INF/com/google/android folder in the .zip file
4. this updater-script file is parsed and converted into reverse polish notation (RPN) for execution
5. edify functions that might modify your device are NOT evaluated; these include apply_patch, delete, delete_recursive, format, mount, package_extract_dir/file, run_program, set_perm[_recursive], symlink, unmount, write_raw_image, etc.
6. note: the update-binary executable is not used by or involved in this app; the edify script interpreter that the app uses was written by me, in Java, specifically for this app
7. the remaining edify script functions that test conditions (such as apply_patch_check, apply_patch_space, assert, concat, file_exists, file_getprop, getprop, greater_than_int, if-then-else-endif, ifelse, is_substring, less_than_int, read_file, ui_print, and various operators (!, !=, &&, (, ), ;, ||, +, ==)) are evaluated using an operand/operator stack from the RPN expression parsed from the updater-script statements
8. expressions that fail (return a null-string) or are bypassed (usually because a resource (file/partition) is protected/secured against read-access) are reported for the user
9. after the entire script has been processed, the results are displayed in a pop-up window on the device and the text of those results are copied to the clipboard
Planned / future features:
- preferences / settings
- logging of the output to a file on the /sdcard
- test if .zip file is signed or not
- display more stats
- "explanation mode" to interpret, in English, what the edify commands are testing
Successfully tested on:
Samsung Galaxy Nexus (CDMA) 4.1.1
Samsung Galaxy Nexus (GSM) 4.1.2
Asus Nexus 7 tablet 4.1.2
Motorola Droid X 2.3.4
The following edify commands/functions/operators are supported:
Code:
[COLOR="blue"]apply_patch_check[/COLOR] // apply_patch_check ( <filepath>, <sha1-checksum> [ , <sha1-checksum> ... ] )
// apply_patch_check ( <compoundvalue> )
<compoundvalue> := [ EMMC : <filepath> : <sha1-size> : <sha1-checksum> [ <sha1-size> : <sha1-checksum> ... ]
[ MTD : <dev-block> : <sha1-size> : <sha1-checksum> [ <sha1-size> : <sha1-checksum> ... ]
[ vfat : <dev-block> : <sha1-size> : <sha1-checksum> [ <sha1-size> : <sha1-checksum> ... ]
<dev-block> := filename in /dev/block
[COLOR="Blue"]apply_patch_space[/COLOR] // apply_patch_space ( <bytes> )
[COLOR="blue"]assert[/COLOR] // assert ( <expression> )
[COLOR="blue"]concat[/COLOR] // conact ( <string> , <string> )
[COLOR="blue"]file_exists[/COLOR] // file_exists ( <filepath> )
[COLOR="blue"]file_getprop[/COLOR] // file_getprop ( <filepath>, <propertyname> )
[COLOR="blue"]getprop[/COLOR] // getprop ( <propertyname> )
[COLOR="blue"]greater_than_int[/COLOR] // greater_than_int ( <integer>, <integer> )
[COLOR="blue"]if then else endif[/COLOR] // if <condition> then <expression> [ else <expression> ] endif
[COLOR="blue"]ifelse[/COLOR] // ifelse ( <condition>, <then-expression> [ <else-expression> ] )
[COLOR="blue"]is_substring[/COLOR] // is_substring ( <string> , <string> )
[COLOR="blue"]less_than_int[/COLOR] // less_than_int ( <integer>, <integer> )
[COLOR="blue"]read_file[/COLOR] // read_file ( <filepath> )
[COLOR="blue"]ui_print[/COLOR] // ui_print ( <string> ) parsed & executed, but output not displayed
[COLOR="blue"]![/COLOR] // logical NOT operator
[COLOR="blue"]!=[/COLOR] // not equals operator
[COLOR="blue"]&&[/COLOR] // logical AND operator
[COLOR="blue"]([/COLOR] // open paren: precedence / grouping
[COLOR="blue"])[/COLOR] // close paren: precedence / grouping
[COLOR="blue"];[/COLOR] // sequence/imperative (terminates & separates statements)
[COLOR="blue"]||[/COLOR] // logical OR operator
[COLOR="blue"]+[/COLOR] // string concatenation operator
[COLOR="blue"]==[/COLOR] // equals operator
[COLOR="blue"]#[/COLOR] // comment line
The following edify functions are NOT supported (the majority of them because they are intended to modify your device):
Code:
[COLOR="blue"]apply_patch[/COLOR]
[COLOR="blue"]delete[/COLOR]
[COLOR="blue"]delete_recursive[/COLOR]
[COLOR="blue"]format[/COLOR]
[COLOR="blue"]mount[/COLOR]
[COLOR="blue"]package_extract_dir[/COLOR]
[COLOR="blue"]package_extract_file[/COLOR]
[COLOR="blue"]run_program[/COLOR]
[COLOR="blue"]set_perm[/COLOR]
[COLOR="blue"]set_perm_recursive[/COLOR]
[COLOR="blue"]symlink[/COLOR]
[COLOR="blue"]unmount[/COLOR]
[COLOR="blue"]write_raw_image[/COLOR]
[COLOR="blue"]is_mounted[/COLOR] // innocuous, but still not supported
[COLOR="blue"]stdout[/COLOR] // innocuous, but still not supported
[COLOR="blue"]show_progress[/COLOR] // innocuous, but still not supported
[COLOR="blue"]set_progress[/COLOR] // innocuous, but still not supported
Keywords:
OTA, over-the-air, updater-script, edify, amend
Screenshots:
updated 9-May-2014
updated to version 1.3
Updated app with root-enabled file browser for navigating to protected/secured directories like /cache to select OTA's update zip file.
Full change log to date:
[v1.3 - 04-Nov-2012]:
- for rooted devices, change file browser to allow navigating and selecting .zip files in protected directories (like /cache)
[v1.2 - 29-Oct-2012]:
- minor fix to handle two reports of null pointer exceptions
[v1.1 - 28-Oct-2012]:
- remove unused SD card write permission
[v1.0 - 28-Oct-2012]:
- initial Play Market release
This is pretty cool.
Any chance you could direct me to an explanation for sha1-size (for apply_patch_check) is though? I'm working on some edify scripting stuff and trying to incorporate some asserts for a specific bootloader (important to what I'm doing), and this is honestly the best reference I've found for it yet.
osm0sis said:
This is pretty cool.
Any chance you could direct me to an explanation for sha1-size (for apply_patch_check) is though? I'm working on some edify scripting stuff and trying to incorporate some asserts for a specific bootloader (important to what I'm doing), and this is honestly the best reference I've found for it yet.
Click to expand...
Click to collapse
You bet!
I'm heading home from work here soon and I'll dig-up the details for you .
(yeah, I scoured the internet for detailed information on Edify scripting as well as reviewed the actual Google/Android code--there's not a complete compendium, unfortunately).
I'll ping you back after a bit...
Cheers!
osm0sis said:
Any chance you could direct me to an explanation for sha1-size (for apply_patch_check) is though?
Click to expand...
Click to collapse
Okay, here's what I know about the apply_patch_check command:
There are basically two formats:
Code:
apply_patch_check // apply_patch_check ( <filepath>, <sha1-checksum> [ , <sha1-checksum> ... ] )
// apply_patch_check ( <compoundvalue> )
<compoundvalue> := [ EMMC : <filepath> : <sha1-size> : <sha1-checksum> [ <sha1-size> : <sha1-checksum> ... ]
[ MTD : <dev-block> : <sha1-size> : <sha1-checksum> [ <sha1-size> : <sha1-checksum> ... ]
[ vfat : <dev-block> : <sha1-size> : <sha1-checksum> [ <sha1-size> : <sha1-checksum> ... ]
The first of which is what I think you typically see in updater-script files where you have a filename, followed by one or more SHA1 digests. Here's an example:
assert(apply_patch_check("/system/app/ApplicationsProvider.apk", "41bb5aaaa2791e68b55622fcca13f0e4efa757b2", "fc845332ae7f706824de73f64ae47f93866ad245"));
The second format is what I call a compound value format, where the file or partition to be checked and the SHA1 digests to be compared, are all concatenated together in a single, colon-separated value. For example:
assert(apply_patch_check("EMMC:/dev/block/platform/omap/omap_hsmmc.0/by-name/boot:4247552:3f4d4f9549d307d152f8503983ee4ff5f46b0a43:4470784:fbd13c778b34fdb7917c1ccee6389aa9b13a92bd"));
In the above, I've colored the sizes in red of file/partition on which to compute the SHA1 checksum (colored in black). I figured this out and verified this by using dd to copy the portions of the partition in question and calculating the SHA1 checksums on it.
My app only supports parsing and evaluating two sets of lengths/SHA1s for the compound format at this time (that's all I've encountered so far in the scripts that I've viewed).
Does that help and/or answer your questions?
Cheers!
Thanks! Yeah that helps a lot, but unfortunately it doesn't seem to solve the problem I've been seeing..
Using dd to grab the partition img I can sha1sum that and that SHA1 doesn't allow it to pass the assert, or even a direct sha1_check of the partition.
Code:
run_program("/sbin/busybox", "dd", "if=/dev/block/platform/sdhci-tegra.3/by-name/USP"), "of=/tmp/bootloader.img")
ui_print(sha1_check(read_file("/tmp/bootloader.img"))); = 8c206a1a87599f532ce68675536f0b1546900d7a (also, bootloader.img is 2097152 in size)
ui_print(sha1_check(read_file("/dev/block/platform/sdhci-tegra.3/by-name/USP"))); = da39a3ee5e6b4b0d3255bfef95601890afd80709
assert(apply_patch_check("EMMC:/dev/block/platform/sdhci-tegra.3/by-name/USP:2097152:8c206a1a87599f532ce68675536f0b1546900d7a")); = Fail
They just don't match and I'm completely baffled by it. I can work around it by using dd to pull the img first and using that for my asserts but it's not as clean as I'd like it.
osm0sis said:
Yeah that helps but I guess unfortunately it doesn't entirely solve the problem I've been seeing.
Using dd to grab the partition img I can sha1sum that and that SHA1 doesn't allow it to pass the assert, or even a direct sha1_check of the partition.
They just don't match and I'm completely baffled by it. I can work around it by using dd to pull the img and using that for my asserts but it's not as clean as I'd like it.
Click to expand...
Click to collapse
Is it for the Gnex or the N7 (I have those same devices)?
I'd be happy to test something for you...just PM me or send me an email ([email protected]).
I don't know if you're using my app to test with, but you can also manually run the update-binary directly on/from your phone (i.e., you don't have to run it in recovery, but you obviously need to be careful what your updater-script does ).
I'm still looking for the exact syntax in my notes, but I'll edit this post when I find it...brb.
~ ~ ~
edit: http://wiki.opticaldelusion.org/wiki/Update-binary shows this:
update-binary <api> <pipefd> <zip>
Click to expand...
Click to collapse
I know I did this during my early testing, but I can't remember the exact syntax...I'll try it and re-re-edit .
Man thanks so much, PM sent.
Sorry for cluttering up your thread with this semi-OT stuff.
osm0sis said:
Man thanks so much, PM sent.
Sorry for cluttering up your thread with this semi-OT stuff.
Click to expand...
Click to collapse
LOL, not a problem...it's all Edify-related and updater-script related...I'm betting that's what'll lead most folks here.
Happy to help .
==================
Detailed Analysis
==================
- you have no frozen system apps (good!)
- there were 2 failed expressions; see below for the details about these tests that will cause your OTA install to fail
- there were no bypassed expressions (good!)
-------------------------------
statistics:
frozen system apps: 0
success count: 526
fail count: 2
ignore count: 1587
partition count: 2
protected count: 2
bypassed count: 0
-------------------------------
updater-script analysis details:
FAILED: line #268:
assert(apply_patch_check("/system/app/XT9IME.apk", "8aba56a4406128e78f5729753252c3d93bc21cb4", "965b437bce65018eeb31ff9a381c3687542099e0"));
----------------------
FAILED: line #1038:
assert(apply_patch_check("EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:5013504:c48f8e86c73fb2c2ba1794f5ec98e27c9e206ed5:5060608:319331fae14fec8a88063751475fce26bae328e0"));
So a question, could this failure above be causing my 32 GB nexus 7 to have system update issues? (Not necessarily XT9IME.apk (which I shouldn't have deleted), more the other one) Is there a fix?
Sent from my Nexus 7 using Tapatalk HD
---------- Post added at 10:44 AM ---------- Previous post was at 10:39 AM ----------
==================
Detailed Analysis
==================
- you have no frozen system apps (good!)
- there were 2 failed expressions; see below for the details about these tests that will cause your OTA install to fail
- there were no bypassed expressions (good!)
-------------------------------
statistics:
frozen system apps: 0
success count: 526
fail count: 2
ignore count: 1587
partition count: 2
protected count: 2
bypassed count: 0
-------------------------------
updater-script analysis details:
FAILED: line #268:
assert(apply_patch_check("/system/app/XT9IME.apk", "8aba56a4406128e78f5729753252c3d93bc21cb4", "965b437bce65018eeb31ff9a381c3687542099e0"));
----------------------
FAILED: line #1038:
assert(apply_patch_check("EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:5013504:c48f8e86c73fb2c2ba1794f5ec98e27c9e206ed5:5060608:319331fae14fec8a88063751475fce26bae328e0"));
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
So a question, could this failure above be causing my 32 GB nexus 7 to have system update issues? (Not necessarily XT9IME.apk (which I shouldn't have deleted), more the other one) Is there a fix?
modwilly said:
So a question, could this failure above be causing my 32 GB nexus 7 to have system update issues? (Not necessarily XT9IME.apk (which I shouldn't have deleted), more the other one) Is there a fix?
Click to expand...
Click to collapse
Looks like you've updated the boot (LNX) partition in addition to deleting (or renaming/moving) the XT9IMG.apk?
So yes, the OTA will not install until you've put both items back to their expected state.
The fix, of course, depends on exactly what you did to change them in the first place.
version 2.1 uploaded to Play Store
Major re-write of app done for version 2.0 and above.
Recent change log:
[version 2.1 - 6-May-2014]:
- fix issue w/identification of non-existent files
[version 2.0 - 5-May-2014]:
- major app update: edify parsing, RPN processing and execution engine completely re-written
- original core app behavior and functionality remain the same, but code cleanup and re-write should mean better and more robust handling of future OTA updater-script expressions
Click to expand...
Click to collapse
Thanks and let me know if you have any questions.
@scary alien could you please tell me how to get apply_patch_space bytes? i am making ota script and i got almost all, still need to generate:
apply_patch_space(bytes) || abort("Not enough free space on /cache to apply patches.");
Click to expand...
Click to collapse
i just dunno how
ZduneX25 said:
@scary alien could you please tell me how to get apply_patch_space bytes? i am making ota script and i got almost all, still need to generate:
i just dunno how
Click to expand...
Click to collapse
It's just the available space (in bytes) in the /cache partition that you want to make sure is available (i.e., free space) for any operations your updater-script file will do concerning /cache.
For example:
apply_patch_space(1000000) || abort("Not enough free space on /cache to apply patches.");
Click to expand...
Click to collapse
Would verify that there is at least 1MB (1,000,000) free bytes available in /cache.
Does that answer what you're asking?
Lemme know--happy to help if I can.
Cheers!
@scary alien not really, i mean i know how it works, just dunno how to generate proper size in updater, for example:
i create regular ota: multiple .p files and some images, zipped, signed OTA.zip size is 20mb, /patch size is 7 mb, images 10 mb and /system (new files) 3mb, how do i know how many bytes i should set to make this ota install in recovery?
should i summarize .p files size or target (patched apk, jar) files size (would be around 90mb) or what else?
I think the size would depend on when your patch files are cleaned-up...i.e., after each patching operation or at the end. If its at the end, you'll of course need to account to all of the space you might use in /cache.
I don't know of a good way to tell you what the high water mark would be other than testing and recording the output of a "df /cache" command at various points in your updater-script file.
I could do that however I don't see it universal or handy, each ota has different size so it would need more/less free space every time.
There is how Google gets this value : https://github.com/MiCode/patchrom_tools/blob/kitkat/releasetools/edify_generator.py#L131 maybe you will understand better.
ZduneX25 said:
I could do that however I don't see it universal or handy, each ota has different size so it would need more/less free space every time.
There is how Google gets this value : https://github.com/MiCode/patchrom_tools/blob/kitkat/releasetools/edify_generator.py#L131 maybe you will understand better.
Click to expand...
Click to collapse
I think I understood what you meant...there's no easy way to make this universal for each OTA except to evaluate each file that might need to use space resources from the /cache partition.
Even the edify-generator git that you referenced does this dynamically:
releasetools/ota_from_target_files:
Code:
for diff in diffs:
tf, sf, d = diff.GetPatch()
if d is None or len(d) > tf.size * OPTIONS.patch_threshold:
# patch is almost as big as the file; don't bother patching
tf.AddToZip(output_zip)
verbatim_targets.append((tf.name, tf.size))
else:
common.ZipWriteStr(output_zip, "patch/" + tf.name + ".p", d)
patch_list.append((tf.name, tf, sf, tf.size, common.sha1(d).hexdigest()))
[COLOR="Red"]largest_source_size[/COLOR] = max([COLOR="red"]largest_source_size[/COLOR], sf.size)
:
:
:
if patch_list or updating_recovery or updating_boot:
script.[COLOR="Blue"][B]CacheFreeSpaceCheck[/B][/COLOR]([COLOR="red"]largest_source_size[/COLOR])
I have seen it, but here comes largest_source_size:
Code:
largest_source_size = 0
https://github.com/MiCode/patchrom_tools/blob/kitkat/releasetools/ota_from_target_files#L532
ZduneX25 said:
I have seen it, but here comes largest_source_size:
Code:
largest_source_size = 0
https://github.com/MiCode/patchrom_tools/blob/kitkat/releasetools/ota_from_target_files#L532
Click to expand...
Click to collapse
Yeah, that's just the initialization of that variable...it gets updated in the for-loop that I included above.
(you know that's not my tool, software, right?)
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