Database Info

Sources Kernel Huawei Sonic U8650 + .config

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

[Q]Ubuntu Touch(Cyanogenmod) debugging

Hi all,
I have tried to build CM 10.1 based Ubuntu Touch for Samsung Tab 2 10.1 but all version will be boot looping only. I have not much Android background but I have read about logcat and reading last kernel messages that could reveal reasons for boot looping. Currently I can seen login screen for a few seconds.
Ubuntu Touch has a limited version of Cyanogenmod so it probably requires different ways to debug, track down the kernel fault. If you have been porting Ubuntu to some other Samsung Tablet what ways you have used? Or would you have some handy tip in your sleeve?
/data/ubuntu/var/log contains some informations but none seems to be directly relating to kernal fault.
Thank you for all suggestions how to proceed with fault determination.

simosays said:
Hi all,
I have tried to build CM 10.1 based Ubuntu Touch for Samsung Tab 2 10.1 but all version will be boot looping only. I have not much Android background but I have read about logcat and reading last kernel messages that could reveal reasons for boot looping. Currently I can seen login screen for a few seconds.
Ubuntu Touch has a limited version of Cyanogenmod so it probably requires different ways to debug, track down the kernel fault. If you have been porting Ubuntu to some other Samsung Tablet what ways you have used? Or would you have some handy tip in your sleeve?
/data/ubuntu/var/log contains some informations but none seems to be directly relating to kernal fault.
Thank you for all suggestions how to proceed with fault determination.
Click to expand...
Click to collapse
Succesfully compiled (@ the other thread), see my github for modifications (only forked 2 repos, kernel + device tree, both from Kumajaya's hub)
For the debugging things, isn't the documentation enough ? You should know how to work your way out
- https://wiki.ubuntu.com/Touch
- https://wiki.ubuntu.com/Touch/Testing
- http://developer.ubuntu.com/packaging/html/fixing-a-bug-example.html

Debugging errors in P5100
Sympnotic said:
Succesfully compiled (@ the other thread), see my github for modifications (only forked 2 repos, kernel + device tree, both from Kumajaya's hub)
For the debugging things, isn't the documentation enough ? You should know how to work your way out
- <removed>
- <removed>
- <removed>
Click to expand...
Click to collapse
Thank you Symptonic!
I am finally debugging ...would you happened to see any similar messages when making porting to other Samsung devices?
E/linker ( 690): ics/linker.c:1598| WARNING: Skipping libc.so
...
E/linker ( 690): ics/linker.c:1072| ERROR: Library 'libOpenVG.so' not found
...
E/linker ( 690): ics/linker.c:1072| ERROR: Library 'libPVROGL.so' not found
E/linker ( 690): ics/linker.c:1072| ERROR: Library 'libPVROCL.so' not found
D/libEGL ( 690): loaded /vendor/lib/egl/libGLESv1_CM_POWERVR_SGX540_120.so
D/libEGL ( 690): loaded /vendor/lib/egl/libGLESv2_POWERVR_SGX540_120.so
Click to expand...
Click to collapse
As far as I understand that relates to device/samsung/omap4-common/ and to device (p5100) which does not support libOpenVG.so. Anyway when those errors are shown couple of times in logcat device will reboot itself see "pastebin". Would you have any suggestions how to configure device settings or track down the error?
Thank you for all comments and ideas!
Entire logcat in pastebin: /J2mNneYw

Requesting Repository Forks

If you wish to request omni forks a repository from AOSP, in order to implement a patch into omni, please post this request here. Eventually this will be carried out via jira (http://jira.omnirom.org)
When posting, please give the path to the repository, and a link to what you want to merge, or a description.
For example if you wish to cherry pick a patch into it, a link to the patch and brief description of the reason for the patch.
We'll then have that repository forked and made available on github and gerrit, permitting you to submit your change.
Before you request, please check on github to ensure it isn't already forked!
For example :
frameworks/base - Needing forked so I can introduce multi window functionality (link here to information)

hardware/broadcom/libbt - Mainly for board-specific configurations (link), but newer CM commits also look promising.
If new device bringups aren't planned yet, ignore the followings:
device/lge/p880 and kernel/lge/p880 - Device bringup (kernel has a non-standard naming at CM repo, it should be android_kernel_lge_x3 (x3 is the board name))
vendor/lge (maybe Omni should create one from scratch)

Adam77Root said:
hardware/broadcom/libbt - Mainly for board-specific configurations (link), but newer CM commits also look promising.
If new device bringups aren't planned yet, ignore the followings:
device/lge/p880 and kernel/lge/p880 - Device bringup (kernel has a non-standard naming at CM repo, it should be android_kernel_lge_x3 (x3 is the board name))
vendor/lge (maybe Omni should create one from scratch)
Click to expand...
Click to collapse
We do have a vendor/lge with just mako, although I'm not sure if its current location.
Vendor blob repos are a legal mess, which is why CM kept them at TheMuppets. We'll likely do something similar if we haven't already (I haven't synced since coming home.) Among other reasons to keep them separate is in the case of a DMCA takedown - usually that happens only to a single repo (see the HTC vendor repos earlier this year) but there's always the risk that damage might be more widespread.

android_external_clang
http://review.cyanogenmod.org/#/c/29799/2
Needed for building my msm8960 device (Motorola Photon Q, xt897c).

arrrghhh said:
android_external_clang
http://review.cyanogenmod.org/#/c/29799/2
Needed for building my msm8960 device (Motorola Photon Q, xt897c).
Click to expand...
Click to collapse
CM bootable recovery and some commits over system core

Black_Prince said:
CM bootable recovery and some commits over system core
Click to expand...
Click to collapse
No for CWM - We're working on forking TWRP in, but some fixes still need to be made to allow it to work on devices with unified recovery/boot image. (Probably one of the biggest holdups for the exynos 4210 family - Sonys with unified boot/recovery can at least use Dees_Troy's FOTAKernel trick).
Getting CWM to build in a tree requires hacks all over the tree in multiple repositories. TWRP is much more self-contained, but needs some tweaks to the build system in order to get it to build properly on a userdebug (as opposed to eng) build.

Entropy512 said:
No for CWM - We're working on forking TWRP in, but some fixes still need to be made to allow it to work on devices with unified recovery/boot image. (Probably one of the biggest holdups for the exynos 4210 family - Sonys with unified boot/recovery can at least use Dees_Troy's FOTAKernel trick).
Getting CWM to build in a tree requires hacks all over the tree in multiple repositories. TWRP is much more self-contained, but needs some tweaks to the build system in order to get it to build properly on a userdebug (as opposed to eng) build.
Click to expand...
Click to collapse
Hmm but until the twrp is ported should i test build for some galaxy devices like SG S2 note 1 with cwm ?
It will make me to push changes to git in device tree ... and will be easy to add support

Black_Prince said:
Hmm but until the twrp is ported should i test build for some galaxy devices like SG S2 note 1 with cwm ?
It will make me to push changes to git in device tree ... and will be easy to add support
Click to expand...
Click to collapse
I'll pull up a remote to use for bootable/recovery until we fork (unless plodey already forked it) from TWRP, won't be able to provide it until tonight.
However, right now, it will only build a working recovery if you do an eng build instead of userdebug. If Dees_Troy's talk at BABBQ is ever posted, that's what I was talking about when I trolled him at the end.
Something like:
Code:
. build/envsetup.sh && brunch custom_n7000-eng
or something like that.

Old
def WriteRawImage(self, mount_point, fn):
"""Write the given package file into the partition for the given
mount point."""
fstab = self.info["fstab"]
if fstab:
p = fstab[mount_point]
partition_type = common.PARTITION_TYPES[p.fs_type]
args = {'device': p.device, 'fn': fn}
if partition_type == "MTD":
self.script.append(
'write_raw_image(package_extract_file("%(fn)s"), "%(device)s");'
% args)
elif partition_type == "EMMC":
self.script.append(
'package_extract_file("%(fn)s", "%(device)s");' % args)
Requested
def WriteRawImage(self, mount_point, fn):
"""Write the given package file into the partition for the given
mount point."""
fstab = self.info["fstab"]
if fstab:
p = fstab[mount_point]
partition_type = common.PARTITION_TYPES[p.fs_type]
args = {'device': p.device, 'fn': fn}
if partition_type == "MTD":
self.script.append(
'package_extract_file("%(fn)s", "/tmp/boot.img");'
'write_raw_image("/tmp/boot.img", "%(device)s");' % args
% args)
elif partition_type == "EMMC":
self.script.append(
'package_extract_file("%(fn)s", "%(device)s");' % args)
elif partition_type == "BML":
self.script.append(
('assert(package_extract_file("%(fn)s", "/tmp/%(device)s.img"),\n'
' write_raw_image("/tmp/%(device)s.img", "%(device)s"),\n'
' delete("/tmp/%(device)s.img"));') % args)
else:
raise ValueError("don't know how to write \"%s\" partitions" % (p.fs_type,))
Flash error in write raw image ...
Also can u cherry pick these commits https://github.com/CyanogenMod/android_system_core/commits/cm-10.2/mkbootimg/unpackbootimg.c
My internal SD card isnt got recognsied , there must be some commits missing in vold ...
I dont even know it got formatted or what in flashing ...
All things working WIFI BLUTOOTH TETHERING CALL DATA MSG MMS OMNITORCH
Also u may have look over https://github.com/CyanogenMod/andr...mmit/f22626cdbecfe27c96f205710173458eab14e1a1
and https://github.com/CyanogenMod/andr...mmit/aee5f78ddec238cec016849acaf1d3007b8b1507

https://android.googlesource.com/platform/hardware/broadcom/libbt
Must haz patch:
https://github.com/CyanogenMod/andr...mmit/4028192a4fe8289bf9b7fb202a2bb2c0d85d98c3
//edit: xplod sorted it out already.

android_packages_apps_PackageInstaller
For
HALO and a feat which enables us to see version of the installed and gonna install app

I need this to make it work with my Samsung galaxy s4

I'm not sure if this is the correct thread, but the following two would be great for i9305 support
smdk4412-qcom-common -> needed for i9305 and t0lte (EDIT: I see this one has now been added)
Thanks!

Hey @pulser_g2,
wondering if i could have the following repositories added in for jf devices,
all features are fully functional with these repositories : branch: cm-10.2 for all
device_samsung_jf-common
android_device_samsung_jflteatt
android_kernel_samsung_jf
CyanogenMod/android_hardware_samsung
CyanogenMod/android_device_samsung_msm8960-common
CyanogenMod/android_device_samsung_qcom-common

@pulser_g2
I just talked to @maxwen and he told me i should post here the needed stuff:
I managed to fix the radio issues today on m7, but i need additionally these commits:
https://github.com/TheMuppets/proprietary_vendor_htc/commit/7bbbe83823525090e7d94c47b439c09a254b380f
https://github.com/TheMuppets/proprietary_vendor_htc/commit/19ed957678d13b489da78d704b27811030688078
https://github.com/TheMuppets/proprietary_vendor_htc/commit/51b006bc8f05757c7dd82361ce6d985e996af360
and please DO NOT merge this: https://github.com/TheMuppets/proprietary_vendor_htc/commit/2b86687a460030199fa42d49207957ce285c1a53
as its not needed and breaks build (I allready have everything in m7-common so no need for vendor)
Thanks in advance

@pulser_g2
we dont need to update anything, please forget my post above, i managed to get it working without all these commits and the right vendor

hardware/qcom/gps - Needing forked so I can build the needed GPS module into my Omnirom build.
The link to this repository is: https://github.com/CyanogenMod/android_hardware_qcom_gps/tree/cm-10.2
I hope it gets included, this saves me a ton of time pulling stuff from other repositories.
Greetings PsychoGame

Galaxy S I9000 (galaxysmtd)
@pulser_g2 Device repos are already forked. Kernel is missing: https://github.com/OmniGalaxyS/android_kernel_samsung_aries
It has android-4.3 and android-4.4 branches up.
Device rocking with Omni!
See you!

Fail

PsychoGame said:
hardware/qcom/gps - Needing forked so I can build the needed GPS module into my Omnirom build.
The link to this repository is: https://github.com/CyanogenMod/android_hardware_qcom_gps/tree/cm-10.2
I hope it gets included, this saves me a ton of time pulling stuff from other repositories.
Greetings PsychoGame
Click to expand...
Click to collapse
I also need android_hardware_qcom_gps (probably best from https://github.com/markcs/android_hardware_qcom_gps/tree/cm-11.0)

[ROM][WIP] [4.4.2] Building CM11

We now have a booting CM11 based on 4.4.2 on Galaxy R
Things working (I have checked only these)
Wifi
Audio ( played a youtube video in browser)
2G/3G data
BT scan and pair
ADB
Calls:
Screen goes black at times during call
Call audio is only on speakers
Could not end a call.
Storage:
Both internal EMMC and external SD cards are NOT getting mounted.
So could not play any music or gallery or screenshot doesnt get saved
Camera app is hidden.Could not check
First boot time is pretty long. Subsequent first reboot takes some time to pass the GALAXY R logo.
Link
http://www.mediafire.com/download/sg2ychsh86d772z/cm-11-20131217-UNOFFICIAL-i9103.zip
Just an initial build for testing and demo purpose and please ensure to have a backup .
Sources and credits:
*Device tree : Grarak's cm11 tree ( https://github.com/Grarak/android_device_samsung_i9103/)
*Kernel : Grarak's 4.4 (https://github.com/Grarak/grakernel-n1)
*CM11 sources
*Frameworks/native branch changes merged as TonyP had pointed ( https://github.com/p990-dev/android_frameworks_native/tree/cm-11.0-dev)
*Recovery updater hack (http://forum.xda-developers.com/showpost.php?p=47692333&postcount=15&nocache=1&z=1484923475146786)
Other Devs Who had given us a working device tree historically . Esp Adam, karthik for their patience to answer my newbie questions .

That lib isn't updated for 11 yet. IIRC it's already merged in Omni or it's on Gerrit. You might check that out.
Sent from my OmniROM-powered LG Optimus 4X HD

Thanks for the response Adam. I shall try the Omni RIL.

https://gerrit.omnirom.org/#/c/1701/

Hi Adam
Faced few more generic errors and managed to resolve them.
Now stuck here. Seems something to do with fstab.
Any inputs?
Thanks
Code:
Install system fs image: /home/skishore/cm11/out/target/product/i9103/system.img
/home/skishore/cm11/out/target/product/i9103/system.img+ maxsize=642318336 blocksize=4224 total=321994968 reserve=6488064
Package target files: /home/skishore/cm11/out/target/product/i9103/obj/PACKAGING/target_files_intermediates/cm_i9103-target_files-17d6d7de93.zip
Package OTA: /home/skishore/cm11/out/target/product/i9103/cm_i9103-ota-17d6d7de93.zip
MKBOOTIMG=device/samsung/i9103/recovery/bootimg.mk \
./build/tools/releasetools/ota_from_target_files -v \
-p /home/skishore/cm11/out/host/linux-x86 \
-k build/target/product/security/testkey \
--backup=true \
--override_device=galaxyr,i9103,GT-I9103,GTI9103 \
/home/skishore/cm11/out/target/product/i9103/obj/PACKAGING/target_files_intermediates/cm_i9103-target_files-17d6d7de93.zip /home/skishore/cm11/out/target/product/i9103/cm_i9103-ota-17d6d7de93.zip
unzipping target target-files...
running: unzip -o -q /home/skishore/cm11/out/target/product/i9103/obj/PACKAGING/target_files_intermediates/cm_i9103-target_files-17d6d7de93.zip -d /tmp/targetfiles-2Epmv1
Traceback (most recent call last):
File "./build/tools/releasetools/ota_from_target_files", line 887, in <module>
main(sys.argv[1:])
File "./build/tools/releasetools/ota_from_target_files", line 830, in main
OPTIONS.info_dict = common.LoadInfoDict(input_zip)
File "/home/skishore/cm11/build/tools/releasetools/common.py", line 155, in LoadInfoDict
d["fstab"] = LoadRecoveryFSTab(zip, d["fstab_version"])
File "/home/skishore/cm11/build/tools/releasetools/common.py", line 227, in LoadRecoveryFSTab
raise ValueError("malformed recovery.fstab line: \"%s\"" % (line,))
ValueError: malformed recovery.fstab line: "/efs ext4 /dev/block/mmcblk0p1"
make: *** [/home/skishore/cm11/out/target/product/i9103/cm_i9103-ota-17d6d7de93.zip] Error 1

It seems like a whitespace is missing there after 'ext4'.
Sent from my OmniROM-powered LG Optimus 4X HD

Adam77Root said:
It seems like a whitespace is missing there after 'ext4'.
Sent from my OmniROM-powered LG Optimus 4X HD
Click to expand...
Click to collapse
I find a recovery.fstab in product out recovery root
Is this the one to be changed? Am not sure where else to find this file.
Code:
# mount point fstype device [device2]
/efs ext4 /dev/block/mmcblk0p1
/system ext4 /dev/block/mmcblk0p2
/cache ext4 /dev/block/mmcblk0p3
/data ext4 /dev/block/mmcblk0p6
/preload ext4 /dev/block/mmcblk0p11
/misc emmc /dev/block/mmcblk0p5
/recovery emmc /dev/block/mmcblk0p8
/boot emmc /dev/block/mmcblk0p9
/sdcard vfat /dev/block/mmcblk0p4
/external_sd vfat /dev/block/mmcblk1p1
/sd-ext ext4 /dev/block/mmcblk1p2
This is the content.
FYI i have extracted files for build from my phone running your project equilibrium.

It's the same fstab.n1 in device folder. Why did you extract this kinda files? They're all there in device tree.
Sent from my OmniROM-powered LG Optimus 4X HD

Adam77Root said:
It's the same fstab.n1 in device folder. Why did you extract this kinda files? They're all there in device tree.
Sent from my OmniROM-powered LG Optimus 4X HD
Click to expand...
Click to collapse
Sorry, I meant that .extract-files.sh for vendor proprietary folder. The device folder is cm cloned and untouched.
The issue here I could narrow down further is the misc_info.txt in the target zip file is read by tools/releasetools/common.py for " fstab_version" as for 1 or 2 for further actions. It is fixed as 2 for this branch by the bootable/recovery/Android.mk
There is no such version check in CM10.1 and I assume our recovery.fstab is of version 1.
Is it needed to be rewritten?

kishoreinme said:
Sorry, I meant that .extract-files.sh for vendor proprietary folder. The device folder is cm cloned and untouched.
The issue here I could narrow down further is the misc_info.txt in the target zip file is read by tools/releasetools/common.py for " fstab_version" as for 1 or 2 for further actions. It is fixed as 2 for this branch by the bootable/recovery/Android.mk
There is no such version check in CM10.1 and I assume our recovery.fstab is of version 1.
Is it needed to be rewritten?
Click to expand...
Click to collapse
You cannot build cm 11 with cm 10.1 device tree
at least you will need cm 10.2 tree

Grarak said:
You cannot build cm 11 with cm 10.1 device tree
at least you will need cm 10.2 tree
Click to expand...
Click to collapse
Thanks garak, how to get the 10.2 tree?
But by changing the fstab version to 1, the build completed.
But i could not flash it with my cwm 6.0.3.4
It says installation aborted.status 0
:crying:

If someone can build cm11(4.4 KitKat)for our devices it was great
at least,According from the news 4.4 will more optimize it's memory usage and improve whole performance for low end devices
but I still worrying that may not have or the porting will very hard because our Tegra2 was lack with neon SSIMD

aaa839 said:
If someone can build cm11(4.4 KitKat)for our devices it was great
at least,According from the news 4.4 will more optimize it's memory usage and improve whole performance for low end devices
but I still worrying that may not have or the porting will very hard because our Tegra2 was lack with neon SSIMD
Click to expand...
Click to collapse
Just a heads up if you do get it to work, I tried this for my Galaxy Tab 10.1 and the audio blobs are incompatible with the new audioflinger. I can't get past the boot animation because of this.

AAccount said:
Just a heads up if you do get it to work, I tried this for my Galaxy Tab 10.1 and the audio blobs are incompatible with the new audioflinger. I can't get past the boot animation because of this.
Click to expand...
Click to collapse
We use source-built audio libs, it can be easily modified to work.
For ICS blobs, you have to cherry-pick all old commits, maybe some didn't get into the tree accidentally. I encountered another crash, a function isn't added to the ifdefs yet.
Sent from my OmniROM-powered LG Optimus 4X HD

Adam77Root said:
We use source-built audio libs, it can be easily modified to work.
For ICS blobs, you have to cherry-pick all old commits, maybe some didn't get into the tree accidentally. I encountered another crash, a function isn't added to the ifdefs yet.
Sent from my OmniROM-powered LG Optimus 4X HD
Click to expand...
Click to collapse
Could you please post the source having 10.2 device tree.
And also does flashing CM11 need a new CWM? I have the 6.0.3.5 selinux CWM installed which doesnt allow flashing the zip generated.
Thanks

kishoreinme said:
Could you please post the source having 10.2 device tree.
And also does flashing CM11 need a new CWM? I have the 6.0.3.5 selinux CWM installed which doesnt allow flashing the zip generated.
Thanks
Click to expand...
Click to collapse
https://github.com/tpruvot/android_{device_Samsung_i9103,kernel_samsung_n1}
Yes, you need a newer one which supports the set_metadata_recursive function. You might build one.
Sent from my OmniROM-powered LG Optimus 4X HD

Adam77Root said:
https://github.com/tpruvot/android_{device_Samsung_i9103,kernel_samsung_n1}
Yes, you need a newer one which supports the set_metadata_recursive function. You might build one.
Sent from my OmniROM-powered LG Optimus 4X HD
Click to expand...
Click to collapse
Thanks for the links. Cloned the 10.2 device files/dependencies .
On compiling bionic I am facing compiler issues reporting standard headers missing/pre declared.
Attached log
Could you please help out?

The build completed and the generated cm zip is usable without a new recovery though.
I tried to flash the recovery.img generated during the same with heimdall.
After flashing I Couldnt get into recovery mode.
Is there any other special method to build/flash recovery from cm sources?
or if you can, post a working recovery image.
Sorry that I am bugging more here. This is my first time I try to build CM from sources to get something up on the phone

kishoreinme said:
Thanks for the links. Cloned the 10.2 device files/dependencies .
On compiling bionic I am facing compiler issues reporting standard headers missing/pre declared.
Attached log
Could you please help out?
Click to expand...
Click to collapse
You need to set TARGET_CPU_VARIANT to 'generic' in BoardConfig.mk.
kishoreinme said:
The build completed and the generated cm zip is usable without a new recovery though.
I tried to flash the recovery.img generated during the same with heimdall.
After flashing I Couldnt get into recovery mode.
Is there any other special method to build/flash recovery from cm sources?
or if you can, post a working recovery image.
Sorry that I am bugging more here. This is my first time I try to build CM from sources to get something up on the phone
Click to expand...
Click to collapse
Try to build an image with the online builder at builder.clockworkmod.com. The R can be found among existing devices, but I think it still uses cm-10.1 branch as the official repo isn't updated to 10.2+. Or you can alternatively use the manual mode. I would also prefer the latter.

QUOTE=Adam77Root;47514517]You need to set TARGET_CPU_VARIANT to 'generic' in BoardConfig.mk.
Try to build an image with the online builder at builder.clockworkmod.com. The R can be found among existing devices, but I think it still uses cm-10.1 branch as the official repo isn't updated to 10.2+. Or you can alternatively use the manual mode. I would also prefer the latter.[/QUOTE]
Thanks Adam
I tried manually building at the online builder . Getting the error
Code:
bionic/libc/Android.mk:429: TARGET_CPU_VARIANT is not defined
Console goes here
http://jenkins.cyanogenmod.com/job/recovery/45774/console

4.4.4-CM11 for huawei honor & Ideos X5 U8800 Pro & others KitKat flavours

Hi all. Time to open new Lollipop thread for honor.
http://forum.xda-developers.com/and...u8860-legacyhuawei-roms-t3032641#post58893010
[/COLOR]Huawei Honor u8860 Development​
HI all. after many of you asked me to open a thread about my cm11 builds for honor, i finally decided to do it...
so here is my latest build of cm11 and i will provide also some others kitkat flavour as beanstalk and mokee os and many others....
bugs, wifi tether not working but ok with third party app.
U8800pro users: read post 3
Mini How-to compile 4.4.2 for Huawei honor (u8860) : http://forum.xda-developers.com/showpost.php?p=52922053&postcount=897
see here for wifi tethering
http://forum.xda-developers.com/showpost.php?p=50156494&postcount=3710 (i attached tethering apk)
B919 stock rom base
http://www.mediafire.com/download/z136402ocabf4t6/b919.rar
TWRP-2.8.0.0: http://forum.xda-developers.com/showpost.php?p=55266722&postcount=1444
TeamWin recovery 2.7.1.0-u8860 update= fixed usb storage and file manager http://forum.xda-developers.com/showpost.php?p=54552750&postcount=1282
older : http://forum.xda-developers.com/showpost.php?p=53376000&postcount=1046
TeamWin recovery 2.7.1.0-u8800pro
http://forum.xda-developers.com/showpost.php?p=53378089&postcount=1047
TeamWin recovery 2.7.0.0
http://www.mediafire.com/download/hre1fd1czaq88gw/TWRP2.7-HUAWEIU8860-recovery.img
TeamWin recovery 2.6.0.0
http://www.mediafire.com/download/gi1ng2tp5rd0d8e/recovery-twrp-2.6.0.0-u8860.img
Changelog
http://forum.xda-developers.com/showpost.php?p=51510415&postcount=284
Downloads:
4.4.4
NEW!=Dirty_Unicorn: http://www.mediafire.com/download/kww6t63nbm1rnan/DU_u8860_4.4.4_20140901-1128.v7.9-UNOFFICIAL.zip
new=AOSB http://www.mediafire.com/download/x6m3aqx74nbpc71/aosb_kk_1.3.7_u8860.zip
NEW!=SOKP : http://www.mediafire.com/download/aklta4l3yb6qauk/SOKP-KK444-V-01-20140808-u8860.zip
PacMAn : http://www.mediafire.com/download/yspcsrir7aii7ec/pac_u8860_4.4.4.Beta-1.0_20140702-140013.zip
BeanStalk: http://www.mediafire.com/download/bby7bfpurifbx41/BeanStalk-4.4.4001-20140701-u8860.zip
http://www.mediafire.com/download/36zs4gx3pmc3o2o/BeanStalk-4.4.4001-20140621-u8860.zip
CyanogenMod: http://www.mediafire.com/download/9o8zl2cv8x9ephx/cm-11-testApps2SD-u8860-DAZ.zip --->Apps 2 Sd fixed
older: http://www.mediafire.com/download/1ukim9k4wx55vto/cm-11-444-20140621-UNOFFICIAL-u8860.zip
BlueLightning: http://www.mediafire.com/download/10wzaqvylq6zzx5/BlueLightning-444-20140620-u8860.zip
MokeeOs: http://www.mediafire.com/download/eihlpupd11hz949/MK44.4-u8860-201406201753-UNOFFICIAL.zip
NamelessRom: To come... ^^
Before 4.4.4:http://forum.xda-developers.com/showpost.php?p=53626292&postcount=1142
kernel source: https://github.com/desalesouche/Project-X5pro-Kernel-u8860-u8800pro
TeamWin recovery 2.6.0.0 http://www.mediafire.com/download/gi....0.0-u8860.img
Thread for gamers : http://forum.xda-developers.com/showthread.php?t=2615514
Credits:
- @CrysisLTU
- @Rittick
- @herna
- @gold-concert
- @h33x
- @j.Moihack
-Dazzozo
-ShenduOs
-Fredvj
and many others that i will add as soon as i remember.
thread about google now : http://forum.xda-developers.com/showthread.php?t=2649349
op in construction........
to mods, move that thread to devdb if needed...
in devdb thread my device is not represented .

HOW TO INSTALL
Make sure you're running a proper working ClockworkMod-Recovery/TWRP and that you are on B919 stock rom
Copy Gapps and CM11 ZIPs to your SDCard
Boot into Recovery
Wipe data/factory reset
Wipe Cache and Dalvik Cache
Format System
Flash CM11 zip from SDCard
Reboot
HOW TO COMPILE 4.4.2 ROM FOR HUAWEI HONOR------> http://forum.xda-developers.com/showpost.php?p=52922053&postcount=897

u8800pro users: how-to port rom from u8860 to u8800pro
U8800 pro more to come...
4.4.3 cm11 for u8800pro : http://www.mediafire.com/download/1one0utzb198uh2/cm-11-20140605-UNOFFICIAL-u8800pro.zip
mokee: http://www.mediafire.com/download/jcwcjacnonq32qq/MK44.2-u8800pro-201403150029-UNOFFICIAL.zip
cm11 m3 : http://www.mediafire.com/download/8ikou81fswnkli8/cm-11-m3-20140225-u8800pro-DynamiVSync2.zip
edit: i uploaded here for u8800pro user the bcm4329 wifi module in case some have problem with wifi...
see here how-to port rom from u8860 to u8800pro:
http://forum.xda-developers.com/showpost.php?p=53176802&postcount=961
NEW!our member @Lihis is porting all news rom for u8800pro follow the link...
don't forget to thank him
http://forum.xda-developers.com/showpost.php?p=53520636&postcount=1092

hello, des. thx for great work. i have some ideas, what need the rom:
1. sound for kernel is bad (bass not clear, angel's kernel have good sound)
2. poor sensitivity of the microphone, I was hard to hear. not only me, many users 4pda ask, how to up sensity of micro.
3. if u have time and desire, pls, build for us CarbonROM.
4. pls, need changlog in upper post
thx

for the tether app, what should i put in settings for it to work ?
Sent from my U8860 using Tapatalk

bublz654 said:
for the tether app, what should i put in settings for it to work ?
Sent from my U8860 using Tapatalk
Click to expand...
Click to collapse
link is on op

--

finr0d said:
does the cm11.0m3 include gapps? if not, could you link it in the OP?
Click to expand...
Click to collapse
cm does not support gapps. and here is the link gapps = http://www.mediafire.com/download/79s75mdbmb9bx0l/12-14_GApps_Standard_4.4.2_signed.zip
Sent from my U8860 using Tapatalk

bublz654 said:
cm does not support gapps. and here is the link gapps = http://www.mediafire.com/download/79s75mdbmb9bx0l/12-14_GApps_Standard_4.4.2_signed.zip
Sent from my U8860 using Tapatalk
Click to expand...
Click to collapse
Better to use gapps core for this device due low /system free space.
Here is an xda thread for all 4.4 gapps packages: http://forum.xda-developers.com/showthread.php?t=2012857
Here you will find gapps core and calendar/browser sync (not included in rom/gapps).
Sent from my U8860

that was gapps core, it says standard but all it includes is Google play
Sent from my U8860 using Tapatalk

Could you reupload the recovery image?

T3K0 said:
Could you reupload the recovery image?
Click to expand...
Click to collapse
cwm one?

Just have to paste the link to TWRP again.
I think something went wrong when you copied it. (It tries to open the link with the dots in it)

T3K0 said:
Just have to paste the link to TWRP again.
I think something went wrong when you copied it. (It tries to open the link with the dots in it)
Click to expand...
Click to collapse
Yep. That link on OP is corrupted. I think that was copied from here: http://forum.xda-developers.com/showpost.php?p=50136545&postcount=3703
@desalesouche , in OP should be mentioned that before flashing we need to be on b919 ROM.

I duplicate my message from main thread and in future continue posting here.
---------------START QUOTE--------------------
desalesouche said:
hello camera record doesn't work on 720P , but work on 480P . do you think that not enough ram might be cause for 720P video record? or is there other cause?...
Click to expand...
Click to collapse
Not sure, that I continue test and find this:
1) free memory size in settings apk and /proc/meminfo not equal. In settings i view, that I have 150MB free mem. In meminfo size is 64MB.
2) After record start I found in logs this errors:
Code:
E/OMXCodec( 125): [OMX.qcom.video.encoder.avc] Found supported color format: 21
E/OMX-VENC-720p( 125): get_parameter: OMX_IndexParamVideoProfileLevelQuerySupported for Input port returned Profile:1, Level:512
E/OMX-VENC-720p( 125):
E/OMX-VENC-720p( 125): venc_set_intra_period: nPFrames = 29 nBFrames = 0
I/str_params( 125): key: 'tunneled-input-formats' value: 'get'
D/AudioHardware7x30( 125): AudioHardware::openInputStream devices 8000000 format 1 channels 16 samplerate 48000
D/AudioSource( 125): Start autoramp from 108000
D/AudioHardware7x30( 125): AudioStreamInMSM72xx::standby()
D/AudioHardware7x30( 125): AudioStreamInMSM72xx::standby()
I/MPEG4Writer( 125): limits: 702779264/0 bytes/us, bit rate: 8156000 bps and the estimated moov size 405000 bytes
I/MPEG4Writer( 125): Start time offset: 1000000 us
E/OMX-VENC-720p( 125):
[COLOR="Red"][B]E/OMX-VENC-720p( 125): ERROR: MMAP_FAILED in o/p alloc buffer[/B][/COLOR]
E/OMXNodeInstance( 125): OMX_AllocateBuffer failed with error -2147479552 (0x80001000)
E/OMXCodec( 125): allocate_buffer_with_backup failed
E/OMXCodec( 125): [OMX.qcom.video.encoder.avc] Allocate Buffer failed - error = -2147483648
E/OMXCodec( 125): [OMX.qcom.video.encoder.avc] init failed: -2147483648
E/MediaRecorder( 3770): start failed: -2147483648
E/CAM_VideoModule( 3770): Could not start media recorder.
E/CAM_VideoModule( 3770): java.lang.RuntimeException: start failed.
E/CAM_VideoModule( 3770): at android.media.MediaRecorder.start(Native Method)
E/CAM_VideoModule( 3770): at com.android.camera.VideoModule.startVideoRecording(VideoModule.java:1194)
E/CAM_VideoModule( 3770): at com.android.camera.VideoModule.onShutterButtonClick(VideoModule.java:532)
E/CAM_VideoModule( 3770): at com.android.camera.ShutterButton.performClick(ShutterButton.java:126)
E/CAM_VideoModule( 3770): at android.view.View$PerformClick.run(View.java:18429)
E/CAM_VideoModule( 3770): at android.os.Handler.handleCallback(Handler.java:733)
E/CAM_VideoModule( 3770): at android.os.Handler.dispatchMessage(Handler.java:95)
E/CAM_VideoModule( 3770): at android.os.Looper.loop(Looper.java:136)
E/CAM_VideoModule( 3770): at android.app.ActivityThread.main(ActivityThread.java:5081)
E/CAM_VideoModule( 3770): at java.lang.reflect.Method.invokeNative(Native Method)
E/CAM_VideoModule( 3770): at java.lang.reflect.Method.invoke(Method.java:515)
E/CAM_VideoModule( 3770): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:781)
E/CAM_VideoModule( 3770): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:597)
E/CAM_VideoModule( 3770): at dalvik.system.NativeStart.main(Native Method)
V/CAM_VideoModule( 3770): Releasing media recorder.
this error really caused memory deficit.
I view current codecs and profiles, they identical with official firmware.
I try install and start old Huawei camera app and report about this.
------------------END QUOTE-----------------
I install stock camera application and have same error. symbol-to-symbol.
when I find information about qualcomm SoC hardware decoder I find this post.
Braccoz said:
hey guys, i would like to share some of my findings about the 1080p camera issue
prologue: scverhagen's 1080p hack works but only with the m4v encoder which puts out an h263 file (basically, divx quality). i also found out that the stock rom encodes both 720p and 1080p @h264 baseline lvl 4.0 while CM only encodes h264 baseline level 3.2
the findings: when you try to record 1080p h264 the camera app crashes and this is the logcat:
.....
some log code listing delete. h33x
.....
after some digging i found out that basically every phone (soc) has specific video hardware encoding capabilities and that there is a "standard" layer much like Direct3D/OpenGL for that, and is called OpenMAX (OMX).
it seems that omx implementation for every soc is, of course, closed source, but fortunately there is enough open source stuff to be able to use proprietary binary blobs (i may not be correct here, i am making educated guesses taking the info i found as a base)
so what i'm thinking currently is that the libOmxVenc.so that is provided with CM (seems like qualcomm donated/helped with the code) is intentionally limited to 720p max (and probably level 3.2 too, this would explain why the media_profiles.xml setting has no effect) and it just crashes when trying to encode anything >720p
so what i would like to try is take libOmxVenc.so from an ICS sensation stock rom and see if that is capable of encoding 1080p without modifications to the code (unlikely... 50% probability maybe but still worth a try)
Click to expand...
Click to collapse
Any ideas?
PS. I download official codec samples and documentation and try find answer inside.

jopsinas said:
Yep. That link on OP is corrupted. I think that was copied from here: http://forum.xda-developers.com/showpost.php?p=50136545&postcount=3703
@desalesouche , in OP should be mentioned that before flashing we need to be on b919 ROM.
Click to expand...
Click to collapse
I have updated to the official ICS and nothing else installed.
What are the steps to install this?
Do I have have to install b919 before I can install TWRP?
I dont have the phone here right now so I would like to download everything now so I dont have to when I install everything next week.

hmm i'm not sure what we're talking about here but since that post of mine was quoted i think you'd find the followup helpful.
the real issue was the camera outputting 31 fps while the encoder supported max 30. hacks have gone into the framework to trick the camera to tell it outputs 30 fps so the encoder was happy. you can browse through commits on my github to see what was done. but that is for doubleshot so it may not have anything to do with your huawei...

h33x said:
I duplicate my message from main thread and in future continue posting here
Any ideas?
PS. I download official codec samples and documentation and try find answer inside.
Click to expand...
Click to collapse
the only clue i have is that our media-codecs and media profiles are not good...

desalesouche said:
the only clue i have is that our media-codecs and media profiles are not good...
Click to expand...
Click to collapse
I think, that error reason in kernel code.
if grep "vidc_720p_mp4_enc_mc.fw" in official kernel code, found "./drivers/video/msm/vidc/720p/resource_tracker/vcd_res_tracker.c" file. this file and it top source files should be load proprietary blobs in memory and provides interfaces for using some functions.
I try find this in 3.4 kernel.

T3K0 said:
I have updated to the official ICS and nothing else installed.
What are the steps to install this?
Do I have have to install b919 before I can install TWRP?
I dont have the phone here right now so I would like to download everything now so I dont have to when I install everything next week.
Click to expand...
Click to collapse
first install b919 stock rom.
then go in pink screen and install cmw.
then you can flash the rom following second op post