Database Develop

MS OneNote not syncing

Hi all,
It matters not if I use bleutooth or USB - the MS OneNote notes will not sync. They are selected in the WMDC but I cannot access the 'settings' part.
I had to turn off advanced options in the USB sync options or else Vista 32 does not even see the device.
Anyone have any advice?
Rich

Got fed up - reinstalled Vista - got the device working using advanced networking - now it works

OneNote Sync Problem with WP 6.5
Have OneNote 2007 on Windows 7 PC, on my Mobile W6.5 with the mobile version of OneNote 2007
On synchronizing (PC with my Mobile) all Office files are successfully synchronized, except the OneNote files. In the sync window I have got:
Microsoft OneNote: attention required and in the WMDC under mobile settings for OneNote Mobile the sync settings I got the message Catastrophic failure (Exception from HRESULT: 0x8000FFFF (E_UNEXPECTED)) for details see below
Second question can I read a OneNote file made on the PC on my Mobile ?
Additional question where is the location of my OneNote files on the Mobile ?
Thanks for your help. If somebody can help me, I am certainly will donate to XDA
Detailed error message: Microsoft.WindowsMobile.IActiveSyncDataType.DoOptionsDialog(Int64 parentWindow)
at Microsoft.WindowsMobile.DeviceManager.ActiveSyncDataType.ShowSettings(Int64 owner)
at Microsoft.WindowsMobile.DeviceCenter.ActiveSyncDataTypeSettings.ShowControl()
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ListBox.WndProc(Message& m)
at Microsoft.WindowsMobile.DeviceCenter.ChooseDataTypeListBox.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4952 (win7RTMGDR.050727-4900)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
Microsoft.WindowsMobile.DeviceManager
Assembly Version: 6.1.0.0
Win32 Version: 6.1.6965.0
CodeBase: file:///C:/Windows/WindowsMobile/Microsoft.WindowsMobile.DeviceManager.DLL
----------------------------------------
Microsoft.WindowsMobile.Common
Assembly Version: 6.1.0.0
Win32 Version: 6.1.6965.0
CodeBase: file:///C:/Windows/WindowsMobile/Microsoft.WindowsMobile.Common.DLL
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Microsoft.WindowsMobile.Rapi
Assembly Version: 6.1.0.0
Win32 Version: 6.1.6965.0
CodeBase: file:///C:/Windows/WindowsMobile/Microsoft.WindowsMobile.Rapi.DLL
----------------------------------------
Microsoft.WindowsMobile.DeviceCenter
Assembly Version: 6.1.0.0
Win32 Version: 6.1.6965.0
CodeBase: file:///C:/Windows/WindowsMobile/Microsoft.WindowsMobile.DeviceCenter.DLL
----------------------------------------
AnimationLibrary
Assembly Version: 6.1.0.0
Win32 Version: 6.1.6965.0
CodeBase: file:///C:/Windows/WindowsMobile/AnimationLibrary.DLL
----------------------------------------
Accessibility
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
************** Exception Text **************
System.Runtime.InteropServices.COMException (0x8000FFFF): Catastrophic failure (Exception from HRESULT: 0x8000FFFF (E_UNEXPECTED))

nand boot on X1

Hello everyone,
i want to try a little project about nand booting on X1
so i have some questions...
1.How high is the chance to brick my device with the right ram_start and ram_address?
2.Would any one help me?
3.Are the ram start and size right and the other things(tinboot2.S)?
Code:
@
@ Tinboot V 1.0
@ Very simple bootloader for HTC Vogue
@ Martin Johnson - [email protected]
@
.equ LOAD_START, 0x10000000
.equ RAM_START, 0x10000000
.equ RAM_SIZE, 0x08000000
.equ INITRD_START, RAM_START+0x00800000
.equ KERNEL_OFFSET, 0x8000
.equ XIP_END, 0x0100000
.org 0
b boot
.org 0x40
.word 0x43454345
.word romhdr+0x80000000 @ location of wince romhdr
.word romhdr
.org 0x100
tags: .word 5,0x54410001,1,0x1000,0 @ ATAG_CORE, pagesize=4K
.word 4,0x54410002,RAM_SIZE,RAM_START @ ATAG_MEM
.word 4,0x54420005,INITRD_START,fin-initrd @ ATAG_INITRD2
cmdline_start: .word (cmdline_end-cmdline_start)/4,0x54410009 @ ATAG_CMDLINE
.ifdef kovsky
.asciz "gsensor_axis=2,1,3 msmvkeyb_toggle=off htc_hw.force_cdma=1 panic=0 acpuclock.oc_freq_khz=600000 pm.sleep_mode=1 mtdparts=msm_nand:[email protected](nand),[email protected](root),[email protected](system),[email protected](userdata)"
.endif
.align
cmdline_end: .word 0,0 @ ATAG_END
.org 0x00001000
boot: ldr r0,loadstart_ptr
ldr r1,ramstart_ptr
ldr r3,fin_ptr
copycode: ldr r2,[r0],#4
str r2,[r1],#4
cmp r1,r3
blo copycode
ldr pc,start_ptr
start: ldr r0,initrd_ptr
ldr r3,fin_ptr
ldr r1,ird_start_ptr
copyinitrd: ldr r2,[r0],#4
str r2,[r1],#4
cmp r0,r3
blo copyinitrd
mov r0,#0
ldr r1,mtype
ldr r2,tags_addr
ldr pc,kernel_start
mtype: .word MTYPE
start_ptr: .word start+RAM_START
loadstart_ptr: .word LOAD_START
ramstart_ptr: .word RAM_START
initrd_ptr: .word initrd+RAM_START
fin_ptr: .word fin+RAM_START
ird_start_ptr: .word INITRD_START
kernel_start: .word RAM_START+0x8000
tags_addr: .word RAM_START+0x100
romhdr:
.word 0x0 @ dllfirst
.word 0x0 @ dlllast
.word 0x80000000 @ physfirst
.word 0x80000000+fin @ physlast
.word 0 @ num mods
.word 0x80000000+fin @ ramstart
.word 0x80000000 @ ramfree
.word 0x83000000 @ ramend
.word 0 @ copyentries
.word 0x80000000 @ copyoffset
.word 0 @ profilelen
.word 0 @ profileoffset
.word 0 @ numfileshy
.word 0 @ flags
.word 0x20 @ fsrampercent
.word 0 @ drvglobstart
.word 0 @ drvgloblen
.word 0x201c2 @ cputype/flags
.word 0x80000000 @ pextensions
.word 0 @ trackingstart
.word 0 @ trackinglen
.org KERNEL_OFFSET
kernel:
.incbin "kernel/zImage"
initrd:
.incbin "kernel/initrd.gz"
.align
fin:
Yea im a noob in that but i will learn it because everyone must try it to learn
pleasy dont come one with you dont get it to work...or learn first compiling the
Kernel...i know...i want it learn by doing
Hope anyone can help me.
And sorry for my very bad English hope u can unsterstand all >.<

Great to see that somebody start to doing that !!!
I will see with NEOPEEK to help you, maybe he know much more than anyother
PM me please

THAT'S GREAT!
Hope you'll make it soon...

So...i have now downloaded neopeeks xperia x1 tinboot an correctet some thing
if i would do that not i think i would brick my device. Hope i doesn't brick my
device...are there no one who can help or something?
Edit: i had tryed tinboot on my device and it stops at bma150: Registering Bosch BMA150 driver but if i restart
my X1 so come Kernel Panic.... Hope i get more to work.

destrix said:
So...i have now downloaded neopeeks xperia x1 tinboot an correctet some thing
if i would do that not i think i would brick my device. Hope i doesn't brick my
device...are there no one who can help or something?
Edit: i had tryed tinboot on my device and it stops at bma150: Registering Bosch BMA150 driver but if i restart
my X1 so come Kernel Panic.... Hope i get more to work.
Click to expand...
Click to collapse
you should ask X1's android developers for help. they're always active on Android development forum: http://forum.xda-developers.com/forumdisplay.php?f=622

Fake Tablet: P10 zh960 MT6582 Black Screen

Hello everyone!
My generic tablet from china did not work properly, so I decided to edit Build.prop, it did not start any applications and showed infinite error screens.
So I tried to flash rom but I believe that the rom despite having exactly the name indicated was wrong, it seems that this tablet is a hardware Fake.
I tried numerous roms with the title tags and nothing worked
I even use a rom so that the person taking a picture of the motherboard is the same version 4.0 as my being 4.1 and it didn't work
I take a photo of the board and send my original build.prop that I backed up.
I can make Flash rom but it keeps connecting and disconnecting USB always, I have to click Start Flash seconds when it is connected, despite that it seems to normally load the rom through SP Tools but I don't know if that should influence the error.
PLease help!I am new to this:crying:
zoom for view numbers motherboard Image link: ibb.co/f9qX2p5
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=KOT49H
ro.build.display.id=ALPS.KK1.MP1.V2.10
ro.build.version.incremental=vEN4125
ro.custom.build.version=vEN4125
ro.build.version.sdk=19
ro.build.version.codename=REL
ro.build.version.release=4.4.2
ro.build.date=2019年 07月 09日 星期二 11:01:57 CST
ro.build.date.utc=1562641317
ro.build.type=user
ro.build.user=buildserver
ro.build.host=buildserver5
ro.build.tags=release-keys
ro.product.model=zh960
ro.product.brand=alps
ro.product.name=zh960
ro.product.device=zh960
ro.product.board=zh960
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=alps
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=zh960
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=zh960-user 4.4.2 KOT49H vEN4125 release-keys
ro.build.fingerprint=alps/zh960/zh960:4.4.2/KOT49H/1562640954:user/release-keys
ro.build.flavor=
ro.build.characteristics=tablet
# end build properties
# begin mediatek build properties
ro.mediatek.version.release=ALPS.KK1.MP1.V2.10
ro.mediatek.platform=MT6582
ro.mediatek.chip_ver=S01
ro.mediatek.version.branch=KK1.MP1
ro.mediatek.version.sdk=2
# end mediatek build properties
#
# from out_user/target/product/zh960/obj/CUSTGEN/config/system.prop
#
#
# system.prop for generic sdk
#
rild.libpath=/system/lib/mtk-ril.so
rild.libargs=-d /dev/ttyC0
# MTK, Infinity, 20090720 {
wifi.interface=wlan0
# MTK, Infinity, 20090720 }
# MTK, mtk03034, 20101210 {
ro.mediatek.wlan.wsc=1
# MTK, mtk03034 20101210}
# MTK, mtk03034, 20110318 {
ro.mediatek.wlan.p2p=1
# MTK, mtk03034 20110318}
# MTK, mtk03034, 20101213 {
mediatek.wlan.ctia=0
# MTK, mtk03034 20101213}
ro.sf.lcd_density=210
#
wifi.tethering.interface=ap0
#
ro.opengles.version=131072
wifi.direct.interface=p2p0
dalvik.vm.heapgrowthlimit=128m
dalvik.vm.heapsize=256m
# USB MTP WHQL
ro.sys.usb.mtp.whql.enable=0
# Power off opt in IPO
sys.ipo.pwrdncap=2
# Switching Menu of Mass storage and MTP
ro.sys.usb.storage.type=mtp
# USB BICR function
ro.sys.usb.bicr=no
# USB Charge only function
ro.sys.usb.charging.only=yes
# audio
ro.camera.sound.forced=0
ro.audio.silent=0
ro.zygote.preload.enable=0
#
# switch bluetooth stack solution
#
ro.btstack=blueangel
ro.camera.project=zh960
#
# ADDITIONAL_BUILD_PROPERTIES
#
persist.gemini.sim_num=2
ro.gemini.smart_sim_switch=false
ro.gemini.smart_3g_switch=2
ril.specific.sm_cause=0
bgw.current3gband=0
ril.external.md=0
ro.btstack=blueangel
ro.sf.hwrotation=270
ril.current.share_modem=2
launcherplus.allappsgrid=2d
curlockscreen=1
ro.mediatek.gemini_support=true
ro.operator.optr=OP08
ro.operator.spec=SPEC0200
ro.operator.seg=SEGDEFAULT
persist.radio.fd.counter=15
persist.radio.fd.off.counter=5
persist.radio.fd.r8.counter=15
persist.radio.fd.off.r8.counter=5
drm.service.enabled=true
fmradio.driver.enable=1
ril.first.md=1
ril.flightmode.poweroffMD=1
ril.telephony.mode=0
dalvik.vm.mtk-stack-trace-file=/data/anr/mtk_traces.txt
persist.mtk.anr.mechanism=1
mediatek.wlan.chip=CONSYS_MT6582
mediatek.wlan.module.postfix=_consys_mt6582
ril.radiooff.poweroffMD=0
ro.build.customer=1
ro.config.notification_sound=Proxima.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.config.ringtone=Backroad.ogg
persist.mtk.wcn.combo.chipid=-1
ter.service.enable=0
mediatek.extmd.usbport=0
ro.lte.dc.support=0
ril.active.md=0
ril.read.imsi=1
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.4_r5
persist.sys.dalvik.vm.lib=libdvm.so
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
I can do SP Tools memory test
Code:
============ Memory Detection Report ===========
Internal RAM:
External RAM:
Type = DRAM
Size = 0x40000000 (1024MB/8192Mb)
NAND Flash:
ERROR: NAND Flash was not detected!
EMMC:
EMMC_PART_BOOT1 Size = 0x0000000000400000(4MB)
EMMC_PART_BOOT2 Size = 0x0000000000400000(4MB)
EMMC_PART_RPMB Size = 0x0000000000400000(4MB)
EMMC_PART_GP1 Size = 0x0000000000000000(0MB)
EMMC_PART_GP2 Size = 0x0000000000000000(0MB)
EMMC_PART_GP3 Size = 0x0000000000000000(0MB)
EMMC_PART_GP4 Size = 0x0000000000000000(0MB)
EMMC_PART_USER Size = 0x00000003ab800000(15032MB)
UFS:
ERROR: UFS was not detected!
============ RAM Test ============
Data Bus Test:
[D0]
[D1]
[D2]
[D3]
[D4]
[D5]
[D6]
[D7]
[D8]
[D9]
[D10]
[D11]
[D12]
[D13]
[D14]
[D15]
[D16]
[D17]
[D18]
[D19]
[D20]
[D21]
[D22]
[D23]
[D24]
[D25]
[D26]
[D27]
[D28]
[D29]
[D30]
[D31]
OK!!
Address Bus Test:
[A1]
[A2]
[A3]
[A4]
[A5]
[A6]
[A7]
[A8]
[A9]
[A10]
[A11]
[A12]
[A13]
[A14]
[A15]
[A16]
[A17]
[A18]
[A19]
[A20]
[A21]
[A22]
[A23]
[A24]
[A25]
[A26]
[A27]
[A28]
[A29]
OK!!
RAM Pattern Test :
Writing ...
0x44332211,
0xA5A5A5A5,
0xA5A5A500,
0xA500A500,
0xA5000000,
0x00000000,
0xFFFF0000,
0xFFFFFFFF,
OK!!
Increment/Decrement Test:
Writing...
OK!!

On the store's website it says to be 8G RAM 128 gb 10 core, if that helps in anything

fake specifications
xchaoling said:
On the store's website it says to be 8G RAM 128 gb 10 core, if that helps in anything
Click to expand...
Click to collapse
This is a . The real hardware specification for Jlinksz ZH960 P10 is here http://specdevice.com/showspec.php?id=d2d6-d70a-f455-ac97344b9a86
Have you found the solution for your tablet's issue ?

stabik2 said:
fake specifications
This is a . The real hardware specification for Jlinksz ZH960 P10 is here http://specdevice.com/showspec.php?id=d2d6-d70a-f455-ac97344b9a86
Have you found the solution for your tablet's issue ?
Click to expand...
Click to collapse
Looks like more fake specs. These fakes can be troublesome.
Some firmwares here: ftp://BMXC:[email protected]
More, older ones: https://4pda.ru/forum/index.php?s=&showtopic=752796&view=findpost&p=101444462

before blinking
read build
Manufacturing date: Jun 2012
CID: 11010030 31364738 420049CC EE466FFD
Capacity: 14.68 GiB (15,762,456,576 bytes)
Boot1: 2048 KiB
Boot2: 2048 KiB
RPMB: 256 KiB
User area: 14.68 GiB(15,758,000,128 bytes)
USB speed: High-Speed
platform: MT6582, cpu abi: armeabi-v7a
manufacturer: alps
board: zh960, name: zh960
brand: alps, model: zh960
build id: KOT49H, version: 4.4.2 [Lollipop] (ALPS.KK1.MP1.V2.10)
build description: zh960-user 4.4.2 KOT49H vEN71R0 release-keys
name: MTK_PLATFORM_CFG
version: V1.1.1
platform: MT6582
project: MTDTtest
storage: EMMC
bootChannel: MSDC_0
blockSize: 0x00020000
MTK Preloader file info:

hlppp

P20Pro kernel SELinux Permissive

SourceCode:http://download-c1.huawei.com/downl...adId=101178&version=439689&siteCode=worldwide
kernel.img
Code:
HWCLT:/ # cat /proc/version
Linux version 4.9.148 ([email protected]) (gcc version 4.9.x-google 20140827 (prerelease) (GCC) ) #1 SMP PREEMPT Wed Jul 8 22:37:45 CST 2020
HWCLT:/ # getenforce
Enforcing
HWCLT:/ # setenforce 0
HWCLT:/ # getenforce
Permissive

Everything you need to know to fix camera on custom ROM

Hi, in order to get camera working you have to do two things: build custom kernel and add one proprietary driver from stock rom.
I'm almost at the end, if anyone could help me I would be thankful.
Sony E1 uses Samsung CMOS sensor s5k5ca, it's SoC (snapdragon doesn't encoding videos from this sensor). It was introduced in 2010.
How to build custom kernel:
git clone https://github.com/TeamVee-SS/android_kernel_sony_msm8x10.git
make ARCH=arm shuang_defconfig
make ARCH=arm menuconfig
from there change kernel compression from Gzip to XZ, because kernel will be bigger..
Go to "Device Drivers", "Multimedia support"; Enable following:
MSM videobuf2 extensions
Qualcomm MSM camera and video capture support ---> Qualcomm MSM camera and video capture support
Qualcomm MSM camera and video capture 2.0 support --->
Qualcomm MSM V4L2 based video driver --->
go to "Qualcomm MSM camera and video capture 2.0 support" and enable following:
Qualcomm MSM camera sensor support Qualcomm MSM Camera Post Processing Engine support Qualcomm MSM Camera Control Interface support Qualcomm MSM Image Signal Processing interface support Qualcomm MSM Image Signal Processing interface support Sensor S5K5CA (YUV 3MP)
in "Qualcomm MSM camera and video capture 2.0 support"
Qualcomm MSM V4l2 video overlay device
Qualcomm MSM camera sensor support
Also you need to uncomment two lines, revert the one commit, see:
dts: shuang: Disable camera allocation · TeamVee-SS/[email protected]
Change-Id: I85d6b698d9ca0e20717ab79f2f09ea05a635a2cf Signed-off-by: Caio Oliveira <[email protected]>
github.com
then compile kernel by:
make -j8 ARCH=arm CROSS_COMPILE=/opt/toolchains/arm-eabi-4.9/bin/arm-eabi- CONFIG_NO_ERROR_ON_MISMATCH=y
rebuild your mkbootimg but use the same initrd(ramdisk) as was for your custom rom
Spoiler: mkbootimg command
mkbootimg --kernel zImage --ramdisk ramdisk.gz --cmdline "androidboot.hardware=qcom user_debug=23 maxcpus=2 msm_rtb.filter=0x3F ehci-hcd.park=3 msm_rtb.enable=0 lpj=192598 dwc3.maximum_speed=high dwc3_msm.prop_chg_detect=Y androidboot.bootdevice=msm_sdcc.1 androidboot.selinux=permissive" --base 0x00000000 --pagesize 2048 --dt dt --ramdisk_offset 0x02000000 --tags_offset 0x01E00000 -o out.img
If you want to use kernel with stock rom use mkqcdtbootimg
Spoiler: command
mkqcdtbootimg --kernel arch/arm/boot/zImage --ramdisk cwm.img-ramdisk.gz --dt_dir arch/arm/boot/ --base 0x00000000 --ramdisk_offset 0x2008000 --kernel_offset 0x10000 --tags_offset 0x1e08000 --pagesize 2048 --cmdline "androidboot.hardware=qcom user_debug=31 maxcpus=2 msm_rtb.filter=0x3F ehci-hcd.park=3 msm_rtb.enable=0 lpj=192598 dwc3.maximum_speed=high dwc3_msm.prop_chg_detect=Y androidboot.bootdevice=msm_sdcc.1 " -o boot.img
After you boot into system you should see if kernel finds this image sensor
Spoiler: dmesg | grep s5k5
[ 3.292867] msm_s5k5ca_i2c_probe: 639: client->addr = [78]
[ 3.327817] s5k5ca_sensor_power_up: 775: clk_rate = [24000000], clk_info_size = [2]
[ 3.376093] s5k5ca_match_id: 1945: calling i2c_read: i2c_addr = [78], id_reg_addr = [f12]
[ 3.386482] s5k5ca_match_id: 1967: [read id/expected id] = [5ca/0x05ca]
[ 3.392530] s5k5ca_sensor_power_up: 812: HW_VERSION_GPIO = [85], HW_VERSION = [1]
[ 13.659106] s5k5ca_sensor_config: 921: s5k5ca: cfgtype = [8]
[ 13.686368] s5k5ca_sensor_config: 933: sensor name [s5k5ca]
[ 13.691223] s5k5ca_sensor_config: 935: session id [1]
[ 13.696133] s5k5ca_sensor_config: 939: subdev_id0 = [-1]
[ 13.717228] s5k5ca_sensor_config: 939: subdev_id1 = [-1]
[ 13.727085] s5k5ca_sensor_config: 939: subdev_id2 = [-1]
[ 13.740409] s5k5ca_sensor_config: 939: subdev_id3 = [-1]
[ 13.757070] s5k5ca_sensor_config: 939: subdev_id4 = [-1]
[ 13.777061] s5k5ca_sensor_config: 939: subdev_id5 = [-1]
[ 13.793739] s5k5ca_sensor_config: 939: subdev_id6 = [0]
[ 13.810401] s5k5ca_sensor_config: 939: subdev_id7 = [-1]
[ 13.830394] s5k5ca_sensor_config: 939: subdev_id8 = [0]
[ 13.847061] s5k5ca_sensor_config: 939: subdev_id9 = [-1]
[ 13.863854] s5k5ca_sensor_config: 921: s5k5ca: cfgtype = [9]
[ 13.883729] s5k5ca_sensor_config: 1158: init params mode = [0], pos = [0], mount = [90], HW_VERSION = [1]
In some cases you can see this:
Spoiler: dmesg | grep s5k5 -C 5
<7>[ 3.061715] msm_vidc: 1: Q6 hfi device probe called
<6>[ 3.065780] msm_s5k5ca_i2c_probe: 639: client->addr = [78]
<6>[ 3.100655] s5k5ca_sensor_power_up: 775: clk_rate = [24000000], clk_info_size = [2]
<6>[ 3.148995] s5k5ca_match_id: 1945: calling i2c_read: i2c_addr = [78], id_reg_addr = [f12]
<6>[ 3.157982] s5k5ca_match_id: 1967: [read id/expected id] = [5ca/0x05ca]
<6>[ 3.163836] s5k5ca_sensor_power_up: 812: HW_VERSION_GPIO = [85], HW_VERSION = [1]
<6>[ 3.174024] lirc_dev: IR Remote Control driver registered, major 242
<6>[ 3.179614] IR NEC protocol handler initialized
<6>[ 3.184008] IR RC5(x) protocol handler initialized
<6>[ 3.188855] IR RC6 protocol handler initialized
<6>[ 3.193295] IR JVC protocol handler initialized
2. Vendor qcom propriety driver
It was leaked, see:
https://github.com/psychopnk/camera-1/tree/master/vendor/qcom/proprietary/mm-camera
https://github.com/baksosapi/camera/tree/master/vendor/qcom/proprietary/mm-camera
https://github.com/bullik01/camera-1/tree/master/vendor/qcom/proprietary/mm-camera
https://github.com/dfyuan/camera/tree/master/vendor/qcom/proprietary/mm-camera
https://github.com/Puzhenwei/camera/tree/master/vendor/qcom/proprietary/mm-camera
https://github.com/rx78gp01/camera/tree/master/vendor/qcom/proprietary/mm-camera
https://github.com/sandeepbhuyan/camera-1/tree/master/vendor/qcom/proprietary/mm-camera
https://github.com/usernamegemaoa/camera/tree/master/vendor/qcom/proprietary/mm-camera
https://github.com/Vimalraj1/camera-1/tree/master/vendor/qcom/proprietary/mm-camera
https://github.com/Dabi01/camera-1/tree/master/vendor/qcom/proprietary/mm-camera
https://github.com/Bigcountry907/HTC_a13_vzw_Kernel/tree/master/vendor/qcom/proprietary
All this repos has been taken down, but if you search you can get full source code but it's nothing there, support for s5k3l1yx, s5k4e1_u and several other chips but no s5k5ca. If we had leak of git repo of this we could gain what we want.
https://github.com/pier11/kernel_huawei_u8220/wiki/Cameras
According to this page libqcamera.so is filename for our driver, we must use this file directly from stock rom. It's configurable during compilation, it means it have support for sensors only selected during compilation.
We must delete "camera" part of hardware_qcom and other things, add this vendor file and so on. It's for Android 2 but works on 4.4 and it will work on newer Android.
We can use Huawei's/Foxconn's driver for s5k5ca from it's kernel source code but it's complicated.
You can view how many devices use this camera using this site:
Device Info HW Database
Devices and their components database
deviceinfohw.ru
Logcat from working rom:
https://stackoverflow.com/questions/14257760/android-camera-wont-take-picture
List of devices using the same camera sensor:
Nokia X (they managed to get camera full working on lineage 11!)
See https://forum.xda-developers.com/t/rom-unofficial-lineage-os-11-for-nokia-x-xl.3628794/
and https://github.com/Nokia-xl-legacy/vendor_xl/
Huawei Prism II
Huawei-U8687
MediaPad 7 Youth
HUAWEI U8666E
HP Slate 7
I'll fix shuang vendor files, based on vendor_xl and stock rom, then I'll post simplest solution, or ready to go compiled rom, with working camera and gps, as installable zip or image.
Cairo ported sony e1 to other kernel because with stock source we cannot make bootable image using aosp mkbootimg, we must use mkqcdtbootimg. Please note that Cairo disabled camera allocation in dtb. Working blobs are present in lineage 14.1
Currently, I downgraded to stock rom and I will check if custom kernel can handle camera

Oh my god.. If only we could have that leak several years ago..

Arekjk76 said:
Hi, in order to get camera working you have to do two things: build custom kernel and add one proprietary driver from stock rom.
I'm almost at the end, if anyone could help me I would be thankful.
Sony E1 uses Samsung CMOS sensor s5k5ca, it's SoC (snapdragon doesn't encoding videos from this sensor). It was introduced in 2010.
How to build custom kernel:
git clone https://github.com/TeamVee-SS/android_kernel_sony_msm8x10.git
make ARCH=arm shuang_defconfig
make ARCH=arm menuconfig
from there change kernel compression from Gzip to XZ, because kernel will be bigger..
Go to "Device Drivers", "Multimedia support"; Enable following:
MSM videobuf2 extensions
Qualcomm MSM camera and video capture support ---> Qualcomm MSM camera and video capture support
Qualcomm MSM camera and video capture 2.0 support --->
Qualcomm MSM V4L2 based video driver --->
go to "Qualcomm MSM camera and video capture 2.0 support" and enable following:
Qualcomm MSM camera sensor support Qualcomm MSM Camera Post Processing Engine support Qualcomm MSM Camera Control Interface support Qualcomm MSM Image Signal Processing interface support Qualcomm MSM Image Signal Processing interface support Sensor S5K5CA (YUV 3MP)
in "Qualcomm MSM camera and video capture 2.0 support"
Qualcomm MSM V4l2 video overlay device
Qualcomm MSM camera sensor support
Also you need to uncomment two lines, revert the one commit, see:
dts: shuang: Disable camera allocation · TeamVee-SS/[email protected]
Change-Id: I85d6b698d9ca0e20717ab79f2f09ea05a635a2cf Signed-off-by: Caio Oliveira <[email protected]>
github.com
then compile kernel by:
make -j8 ARCH=arm CROSS_COMPILE=/opt/toolchains/arm-eabi-4.9/bin/arm-eabi- CONFIG_NO_ERROR_ON_MISMATCH=y
rebuild your mkbootimg but use the same initrd(ramdisk) as was for your custom rom
Spoiler: mkbootimg command
mkbootimg --kernel zImage --ramdisk ramdisk.gz --cmdline "androidboot.hardware=qcom user_debug=23 maxcpus=2 msm_rtb.filter=0x3F ehci-hcd.park=3 msm_rtb.enable=0 lpj=192598 dwc3.maximum_speed=high dwc3_msm.prop_chg_detect=Y androidboot.bootdevice=msm_sdcc.1 androidboot.selinux=permissive" --base 0x00000000 --pagesize 2048 --dt dt --ramdisk_offset 0x02000000 --tags_offset 0x01E00000 -o out.img
If you want to use kernel with stock rom use mkqcdtbootimg
Spoiler: command
mkqcdtbootimg --kernel arch/arm/boot/zImage --ramdisk cwm.img-ramdisk.gz --dt_dir arch/arm/boot/ --base 0x00000000 --ramdisk_offset 0x2008000 --kernel_offset 0x10000 --tags_offset 0x1e08000 --pagesize 2048 --cmdline "androidboot.hardware=qcom user_debug=31 maxcpus=2 msm_rtb.filter=0x3F ehci-hcd.park=3 msm_rtb.enable=0 lpj=192598 dwc3.maximum_speed=high dwc3_msm.prop_chg_detect=Y androidboot.bootdevice=msm_sdcc.1 " -o boot.img
After you boot into system you should see if kernel finds this image sensor
Spoiler: dmesg | grep s5k5
[ 3.292867] msm_s5k5ca_i2c_probe: 639: client->addr = [78]
[ 3.327817] s5k5ca_sensor_power_up: 775: clk_rate = [24000000], clk_info_size = [2]
[ 3.376093] s5k5ca_match_id: 1945: calling i2c_read: i2c_addr = [78], id_reg_addr = [f12]
[ 3.386482] s5k5ca_match_id: 1967: [read id/expected id] = [5ca/0x05ca]
[ 3.392530] s5k5ca_sensor_power_up: 812: HW_VERSION_GPIO = [85], HW_VERSION = [1]
[ 13.659106] s5k5ca_sensor_config: 921: s5k5ca: cfgtype = [8]
[ 13.686368] s5k5ca_sensor_config: 933: sensor name [s5k5ca]
[ 13.691223] s5k5ca_sensor_config: 935: session id [1]
[ 13.696133] s5k5ca_sensor_config: 939: subdev_id0 = [-1]
[ 13.717228] s5k5ca_sensor_config: 939: subdev_id1 = [-1]
[ 13.727085] s5k5ca_sensor_config: 939: subdev_id2 = [-1]
[ 13.740409] s5k5ca_sensor_config: 939: subdev_id3 = [-1]
[ 13.757070] s5k5ca_sensor_config: 939: subdev_id4 = [-1]
[ 13.777061] s5k5ca_sensor_config: 939: subdev_id5 = [-1]
[ 13.793739] s5k5ca_sensor_config: 939: subdev_id6 = [0]
[ 13.810401] s5k5ca_sensor_config: 939: subdev_id7 = [-1]
[ 13.830394] s5k5ca_sensor_config: 939: subdev_id8 = [0]
[ 13.847061] s5k5ca_sensor_config: 939: subdev_id9 = [-1]
[ 13.863854] s5k5ca_sensor_config: 921: s5k5ca: cfgtype = [9]
[ 13.883729] s5k5ca_sensor_config: 1158: init params mode = [0], pos = [0], mount = [90], HW_VERSION = [1]
In some cases you can see this:
Spoiler: dmesg | grep s5k5 -C 5
<7>[ 3.061715] msm_vidc: 1: Q6 hfi device probe called
<6>[ 3.065780] msm_s5k5ca_i2c_probe: 639: client->addr = [78]
<6>[ 3.100655] s5k5ca_sensor_power_up: 775: clk_rate = [24000000], clk_info_size = [2]
<6>[ 3.148995] s5k5ca_match_id: 1945: calling i2c_read: i2c_addr = [78], id_reg_addr = [f12]
<6>[ 3.157982] s5k5ca_match_id: 1967: [read id/expected id] = [5ca/0x05ca]
<6>[ 3.163836] s5k5ca_sensor_power_up: 812: HW_VERSION_GPIO = [85], HW_VERSION = [1]
<6>[ 3.174024] lirc_dev: IR Remote Control driver registered, major 242
<6>[ 3.179614] IR NEC protocol handler initialized
<6>[ 3.184008] IR RC5(x) protocol handler initialized
<6>[ 3.188855] IR RC6 protocol handler initialized
<6>[ 3.193295] IR JVC protocol handler initialized
2. Vendor qcom propriety driver
It was leaked, see:
https://github.com/psychopnk/camera-1/tree/master/vendor/qcom/proprietary/mm-camera
https://github.com/baksosapi/camera/tree/master/vendor/qcom/proprietary/mm-camera
https://github.com/bullik01/camera-1/tree/master/vendor/qcom/proprietary/mm-camera
https://github.com/dfyuan/camera/tree/master/vendor/qcom/proprietary/mm-camera
https://github.com/Puzhenwei/camera/tree/master/vendor/qcom/proprietary/mm-camera
https://github.com/rx78gp01/camera/tree/master/vendor/qcom/proprietary/mm-camera
https://github.com/sandeepbhuyan/camera-1/tree/master/vendor/qcom/proprietary/mm-camera
https://github.com/usernamegemaoa/camera/tree/master/vendor/qcom/proprietary/mm-camera
https://github.com/Vimalraj1/camera-1/tree/master/vendor/qcom/proprietary/mm-camera
https://github.com/Dabi01/camera-1/tree/master/vendor/qcom/proprietary/mm-camera
https://github.com/Bigcountry907/HTC_a13_vzw_Kernel/tree/master/vendor/qcom/proprietary
All this repos has been taken down, but if you search you can get full source code but it's nothing there, support for s5k3l1yx, s5k4e1_u and several other chips but no s5k5ca. If we had leak of git repo of this we could gain what we want.
https://github.com/pier11/kernel_huawei_u8220/wiki/Cameras
According to this page libqcamera.so is filename for our driver, we must use this file directly from stock rom. It's configurable during compilation, it means it have support for sensors only selected during compilation.
We must delete "camera" part of hardware_qcom and other things, add this vendor file and so on. It's for Android 2 but works on 4.4 and it will work on newer Android.
We can use Huawei's/Foxconn's driver for s5k5ca from it's kernel source code but it's complicated.
You can view how many devices use this camera using this site:
Device Info HW Database
Devices and their components database
deviceinfohw.ru
Logcat from working rom:
https://stackoverflow.com/questions/14257760/android-camera-wont-take-picture
List of devices using the same camera sensor:
Nokia X (they managed to get camera full working on lineage 11!)
See https://forum.xda-developers.com/t/rom-unofficial-lineage-os-11-for-nokia-x-xl.3628794/
and https://github.com/Nokia-xl-legacy/vendor_xl/
Huawei Prism II
Huawei-U8687
MediaPad 7 Youth
HUAWEI U8666E
HP Slate 7
I'll fix shuang vendor files, based on vendor_xl and stock rom, then I'll post simplest solution, or ready to go compiled rom, with working camera and gps, as installable zip or image.
Cairo ported sony e1 to other kernel because with stock source we cannot make bootable image using aosp mkbootimg, we must use mkqcdtbootimg. Please note that Cairo disabled camera allocation in dtb. Working blobs are present in lineage 14.1
Currently, I downgraded to stock rom and I will check if custom kernel can handle camera
Click to expand...
Click to collapse
How to do this step-by-step on LineageOS 11 (Which uses the falconss kernel instead of the shuang one you've linked
What things do I need (Ubuntu 20.04 is installed inside Windows 10)
And exactly how to do it? I'm a beginner, have Sony Xperia E1 D2005 and use LineageOS 11 for performance reasons, which uses the older, falconss kernel

GTAManRCR said:
How to do this step-by-step on LineageOS 11 (Which uses the falconss kernel instead of the shuang one you've linked
What things do I need (Ubuntu 20.04 is installed inside Windows 10)
And exactly how to do it? I'm a beginner, have Sony Xperia E1 D2005 and use LineageOS 11 for performance reasons, which uses the older, falconss kernel
Click to expand...
Click to collapse
I suggest using Ubuntu 18, read documentation on https://source.android.com/setup/build/initializing. Sync repo using https://github.com/TeamVee-SS/android_.repo_local_manifests. I'm working on getting lineage 16 on this device, but don't use it because it's not ready (https://github.com/msm8610/android_.repo_local_manifests). See
Falconss and shuang are very similar, Caio99BR maintained this. On my custom kernel I imported requited syscalls for running new versions of android.

Arekjk76 said:
I suggest using Ubuntu 18, read documentation on https://source.android.com/setup/build/initializing. Sync repo using https://github.com/TeamVee-SS/android_.repo_local_manifests. I'm working on getting lineage 16 on this device, but don't use it because it's not ready (https://github.com/msm8610/android_.repo_local_manifests). See
Falconss and shuang are very similar, Caio99BR maintained this. On my custom kernel I imported requited syscalls for running new versions of android.
Click to expand...
Click to collapse
GitHub - TeamVee-SS/android_.repo_local_manifests at cm-11.0
Local manifest for Sony Xperia E1. Contribute to TeamVee-SS/android_.repo_local_manifests development by creating an account on GitHub.
github.com
This is what I actually need. Seems like I used the wrong repositories, that's why the image building failed

mkbootimg: error: unrecognized arguments: --dt dt.img
So I now succesfully compiled the kernel, and installed mkbootimg also (Ubuntu 18.04) but this is the error above which I have. Any ideas? If I remove --dt dt the out.img after flashing it to the phone will not boot
EDIT: Used another mkbootimg version, which worked

libmmcamera2_sensor_modules.so is invalid in custom ROM, because it's encoded in Macintosh text format

Today I tried to follow your instructions in order to fix the camera glitch, but it was unsuccessful. This time the problem was the dtb (device tree blob) file made with armeabi in /arch/arm/boot. When I create the new boot.img with the original ramdisk, zImage, and dt.img, the kernel works just fine, but when I create it with the new dtb file, the phone turns off every time I try to turn it on