Related
model : KAIS130
SPL-1.93.0000
CPLD-8
unit come from hong kong new with box and cd and everything inside and when charge and swich on going to first windows logo screen and with sound switch itself off.
first soft - 1.56.00.00 , 22.45.88.07 , 1.27.12.11
my new - 1.82.72.11 , 22.51.88.13 , 1.27.15.32
i find rom from HK (becose with other soft not possible to flash) reflash it two times - one via USB ,second via SD card - soft numbers changes but same story - not loading windows and sw -off alone.
can you help me?
rumensat said:
model : KAIS130
SPL-1.93.0000
CPLD-8
unit come from hong kong new with box and cd and everything inside and when charge and swich on going to first windows logo screen and with sound switch itself off.
first soft - 1.56.00.00 , 22.45.88.07 , 1.27.12.11
my new - 1.82.72.11 , 22.51.88.13 , 1.27.15.32
i find rom from HK (becose with other soft not possible to flash) reflash it two times - one via USB ,second via SD card - soft numbers changes but same story - not loading windows and sw -off alone.
can you help me?
Click to expand...
Click to collapse
HardSPL???
if you mean hard reset - not working
htc spl not working because of missing windows and active synch
no what he means is flashing hardspl (its a program that flashs a spl by olipro. it cid and sim unlocks ur device allowing u to flash rom of ur choice) on to ur device.
instructions on how to flash it can be found in kaiser wiki and also under the first sticky in kaiser rom development forum.
Here is the link for HardSPL which you should use before any other ROM or Radio upgrade. You only need to flash it once.
And here is the link for the Kaiser WIKI where all or most information can be found.
Don't forget to make sure that when you flash a new ROM that you need to also have a compatible radio.
i can not use kaizerhardspl becose can no reach active synch !
well u can flash hardspl from bootloader i believe but check hardspl thread on more info about that.
if some how u messed up ur spl and u weren't security unlocked than i don't know what should be ur next step. i know recently gsleon3 with jockyw's help was able to revive a bricked tilt. i would suggest searching for following thread in kaiser rom dev forum:
"its a true brick (task2a solved)"
that should bring up post on how they did and from there email gsleon3 to help u.
no chance to change 01_spl.nb via usb w/o synch , can flash only with hk rom but nothing after that
if i have tool like nbhextract but nbhcomlete to remake spl after that to turn it back in image may be will decide problem
when run kaizercustomruu with modifyed spl unit stay at 0% and not start flashing
Oh boy looks like you need help from GSLEON3...again, he helped me and he even made a patch to fix easily RUUNBH with 1.92 or 93.
You need this 3 attachments. Sadly I can only attach one because the other two are to big, or something happens because it tells me it's an invalid file.
But anyways this is what you need.
1. The first one is called MTTY. This is a program that lets you go deep into the lowest level of your device and stuff, codes boot, etc. Don't play with it. Just follow the steps from GSLEON3 or any one here with lot of knowledge. With this one you can remove RUUNBH flags.
2. The second, you need to have the original ROM in case something doesn't work. You have to register here www.htc.com and get into software download, find the Original HTC ROM they offer.
3. And the third one is the HARDSPL with JUMPSPL that GSLEON3 made.
NOTE: Don't do what I did, which was that I run the ROM without any HARDSPL installed in my device first.
I hope I helped. It was hell to me when I had the same problem, or similiar.
thank you for explanation,
i try mtty but very different blocs formated as description.
in spl 1.93.00 mtty commands are different from explanation in mtty
in mtty i can go only via usb port
3 color screen i can go only pressing camera and reset
on other words no change.
i have mailed to GSLEON3 and waiting for instructions
regards
here it is some data from mtty
Cmd>info 0
Platform Model ID:KAIS13000
Platform HW Board ID:31, PVT1
Cmd>info 1
Cmd>info 2
HTCSDOPOD001U<wHTCE
Cmd>info 3
HTCSv" §ea0V™?Mi=e}?†?
Cmd>info 4
HTCSDOPOD001U<wHTCE
Cmd>info 5
Cmd>info 6
HTCST UEOHTCE
Cmd>info 7
CPLD ID=0x8
Cmd>info 8
--- 2K bytes sector version ---
DEVICE NAME=samsung_k9k2g08
DEVICE ID=0xAA
DEVICE MAKER ID=0xEC
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x800
BLOCK PAGE=0x40
Checking block information
BLOCK 2 (0x2) is reversed block
BLOCK 8 (0x8) is reversed block
BLOCK 9 (0x9) is reversed block
BLOCK 130 (0x82) is bad block
Partition[0], type=0x20, start=0x2, total=0x63E
Partition[1], type=0x23, start=0x640, total=0x700
Partition[2], type=0x25, start=0xD40, total=0x8780
Partition[3], type=0x4, start=0x94C0, total=0x11E00
CE Total Length(with sector info) = 0x4AAA600
CE CheckSum Length(without sector info) = 0x4A60000
Cmd>info 9
Storage Start Addr=0x54D00000, length:0x8F8F000
Cmd>checkimage
SPL CRC checksum = 0xAA92BA68
CE CRC checksum = bad=0x1A2
0xF36CD2C7
ExtROM CRC checksum = 0x0
valid commands for SPL1.93.00.00 :
tdevinfo
ResetDevice
progress
ruustart
rbmc
waddr
wdata
password
set
info
task
emapiWlanMac
emapiCountryID
emapiInit
emapiTest
emapi
erase
checkimage
checksum
fmrouter
btrouter
wdatas
lnbs
lrs
* some of commands require password!
i thing nand flash is with bad sector and have to format with bad sector take off
but dont know how
Can somebody help?
may be i find problem - it is in Power Management chip PM7500 some register inside - faild
Cmd>task 38
BUFFER = 0x80200000, Sig = 0x444C4F47, SIZE = 0x769B1 restore sign:NOST
GOLD±il for ARM (Thumb Enabled) Built on Jul 22 2007 at 15:44:36
ProcessorType=0b36 Revision=4
sp_abt=ffff1000 sp_irq=ffff0800 sp_undef=ffffc800 OEMAddressTable = 800010a0
+OEMInit
page pool size = 0xc00000
InitDriverGlobals+
02/07/2116 06:28:15 [K :: KERNEL] GetCID - CID is DOPOD001
sizeof(pDriverGlobals->misc)is 0x200
sizeof(pDriverGlobals->eth)is 0x100
sizeof(PV_DRIVERGLOBAL->config)is 0x400
sizeof(PV_DRIVERGLOBAL->debug)is 0x100
sizeof(PV_DRIVERGLOBAL->battery)is 0x80
sizeof(PV_DRIVERGLOBAL->power)is 0x80
InitDriverGlobals-
MainMemoryEndAddress = 0x83500000
PmemHeapPhyAddr = 0x00100000
dwPmemHeapSize = 0x00800000
OEMInit 1
RegCp15(0x00A5387F,0x80000007)
OEMInit 2
OEMInit 3
B4WaitARM9DexReady PV_DRIVERGLOBAL->fixAddress.bIsBatteryReplaceB4=0x0
+Kernel::SoftReset
Windows CE Kernel for ARM (Thumb Enabled) Built on Jul 22 2007 at 15:44:36
ProcessorType=0b36 Revision=4
sp_abt=ffff1000 sp_irq=ffff0800 sp_undef=ffffc800 OEMAddressTable = 800010a0
+OEMInit
page pool size = 0xc00000
InitDriverGlobals+
01/01/1980 00:00:00 [K :: KERNEL] GetCID - CID is DOPOD001
sizeof(pDriverGlobals->misc)is 0x200
sizeof(pDriverGlobals->eth)is 0x100
sizeof(PV_DRIVERGLOBAL->config)is 0x400
sizeof(PV_DRIVERGLOBAL->debug)is 0x100
sizeof(PV_DRIVERGLOBAL->battery)is 0x80
sizeof(PV_DRIVERGLOBAL->power)is 0x80
InitDriverGlobals-
MainMemoryEndAddress = 0x83500000
PmemHeapPhyAddr = 0x00100000
dwPmemHeapSize = 0x00800000
OEMInit 1
RegCp15(0x00A5387F,0x80000007)
OEMInit 2
OEMInit 3
B4WaitARM9DexReady PV_DRIVERGLOBAL->fixAddress.bIsBatteryReplaceB4=0x0
ARM9 DEX READY
DEX_CMD_STATUS_COMPLETE
DEXCORE:loop=191
Get RTC 0x345dd244 from ARM9 ok
system time : 11/03/2007 13:31:48
OEMInit 4
11/03/2007 13:31:48 [K :: KERNEL] Battery Inside in InitBatterySettings....
11/03/2007 13:31:48 [K :: KERNEL] +EnableI2CController: 1
11/03/2007 13:31:48 [D :: I2C] I2C Status ERROR[KR0]: 0x2101, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] I2C Status ERROR[KR1]: 0x2101, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] I2C Status ERROR[KR2]: 0x2101, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] K:I2C Read Failed, status: 0x2101, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] I2C ReStatus ERROR[KR3]: 0x2101, ID = 0x6c
11/03/2007 13:31:48 [K :: KERNEL] I2C Read..Error opening device
11/03/2007 13:31:48 [D :: I2C] +[K]I2C_HWReset_fcn_7500
11/03/2007 13:31:48 [D :: I2C] -[K]I2C_HWReset_fcn_7500
11/03/2007 13:31:48 [D :: I2C] I2C Status ERROR[KR0]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] I2C Status ERROR[KR1]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] I2C Status ERROR[KR2]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] K:I2C Read Failed, status: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] I2C ReStatus ERROR[KR3]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [K :: KERNEL] I2C Read..Error opening device
11/03/2007 13:31:48 [D :: I2C] +[K]I2C_HWReset_fcn_7500
11/03/2007 13:31:48 [D :: I2C] -[K]I2C_HWReset_fcn_7500
11/03/2007 13:31:48 [D :: I2C] I2C Status ERROR[KR0]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] I2C Status ERROR[KR1]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] I2C Status ERROR[KR2]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] K:I2C Read Failed, status: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] I2C ReStatus ERROR[KR3]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [K :: KERNEL] I2C Read..Error opening device
11/03/2007 13:31:48 [D :: I2C] +[K]I2C_HWReset_fcn_7500
11/03/2007 13:31:48 [D :: I2C] -[K]I2C_HWReset_fcn_7500
11/03/2007 13:31:48 [K :: KERNEL] GI_Status_Config= 0
11/03/2007 13:31:48 [D :: I2C] I2C Status ERROR[KR0]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] I2C Status ERROR[KR1]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] I2C Status ERROR[KR2]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] K:I2C Read Failed, status: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] I2C ReStatus ERROR[KR3]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [K :: KERNEL] I2C Read..Error opening device
11/03/2007 13:31:48 [D :: I2C] +[K]I2C_HWReset_fcn_7500
11/03/2007 13:31:48 [D :: I2C] -[K]I2C_HWReset_fcn_7500
11/03/2007 13:31:48 [D :: I2C] I2C Status ERROR[KR0]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] I2C Status ERROR[KR1]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] I2C Status ERROR[KR2]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] K:I2C Read Failed, status: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] I2C ReStatus ERROR[KR3]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [K :: KERNEL] I2C Read..Error opening device
11/03/2007 13:31:48 [D :: I2C] +[K]I2C_HWReset_fcn_7500
11/03/2007 13:31:48 [D :: I2C] -[K]I2C_HWReset_fcn_7500
11/03/2007 13:31:48 [D :: I2C] I2C Status ERROR[KR0]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] I2C Status ERROR[KR1]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] I2C Status ERROR[KR2]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] K:I2C Read Failed, status: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] I2C ReStatus ERROR[KR3]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [K :: KERNEL] I2C Read..Error opening device
11/03/2007 13:31:48 [D :: I2C] +[K]I2C_HWReset_fcn_7500
11/03/2007 13:31:48 [D :: I2C] -[K]I2C_HWReset_fcn_7500
11/03/2007 13:31:48 [D :: I2C] I2C Status ERROR[KR0]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] I2C Status ERROR[KR1]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] I2C Status ERROR[KR2]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] K:I2C Read Failed, status: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] I2C ReStatus ERROR[KR3]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [K :: KERNEL] I2C Read..Error opening device
11/03/2007 13:31:48 [D :: I2C] +[K]I2C_HWReset_fcn_7500
11/03/2007 13:31:48 [D :: I2C] -[K]I2C_HWReset_fcn_7500
11/03/2007 13:31:48 [K :: KERNEL] GI_Status_Config= 0
11/03/2007 13:31:48 [D :: I2C] I2C Status ERROR[KR0]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] I2C Status ERROR[KR1]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] I2C Status ERROR[KR2]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] K:I2C Read Failed, status: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] I2C ReStatus ERROR[KR3]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [K :: KERNEL] I2C Read..Error opening device
11/03/2007 13:31:48 [D :: I2C] +[K]I2C_HWReset_fcn_7500
11/03/2007 13:31:48 [D :: I2C] -[K]I2C_HWReset_fcn_7500
11/03/2007 13:31:48 [D :: I2C] I2C Status ERROR[KR0]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] I2C Status ERROR[KR1]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] I2C Status ERROR[KR2]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] K:I2C Read Failed, status: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] I2C ReStatus ERROR[KR3]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [K :: KERNEL] I2C Read..Error opening device
11/03/2007 13:31:48 [D :: I2C] +[K]I2C_HWReset_fcn_7500
11/03/2007 13:31:48 [D :: I2C] -[K]I2C_HWReset_fcn_7500
11/03/2007 13:31:48 [D :: I2C] I2C Status ERROR[KR0]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] I2C Status ERROR[KR1]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] I2C Status ERROR[KR2]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] K:I2C Read Failed, status: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] I2C ReStatus ERROR[KR3]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [K :: KERNEL] I2C Read..Error opening device
11/03/2007 13:31:48 [D :: I2C] +[K]I2C_HWReset_fcn_7500
11/03/2007 13:31:48 [D :: I2C] -[K]I2C_HWReset_fcn_7500
11/03/2007 13:31:48 [D :: I2C] I2C Status ERROR[KR0]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] I2C Status ERROR[KR1]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] I2C Status ERROR[KR2]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] K:I2C Read Failed, status: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] I2C ReStatus ERROR[KR3]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [K :: KERNEL] I2C Read..Error opening device
11/03/2007 13:31:48 [D :: I2C] +[K]I2C_HWReset_fcn_7500
11/03/2007 13:31:48 [D :: I2C] -[K]I2C_HWReset_fcn_7500
11/03/2007 13:31:48 [K :: KERNEL] GI_Status_Config= 0
11/03/2007 13:31:48 [D :: I2C] I2C Status ERROR[KR0]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] I2C Status ERROR[KR1]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] I2C Status ERROR[KR2]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] K:I2C Read Failed, status: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] I2C ReStatus ERROR[KR3]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [K :: KERNEL] I2C Read..Error opening device
11/03/2007 13:31:48 [D :: I2C] +[K]I2C_HWReset_fcn_7500
11/03/2007 13:31:48 [D :: I2C] -[K]I2C_HWReset_fcn_7500
11/03/2007 13:31:48 [D :: I2C] I2C Status ERROR[KR0]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] I2C Status ERROR[KR1]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] I2C Status ERROR[KR2]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] K:I2C Read Failed, status: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] I2C ReStatus ERROR[KR3]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [K :: KERNEL] I2C Read..Error opening device
11/03/2007 13:31:48 [D :: I2C] +[K]I2C_HWReset_fcn_7500
11/03/2007 13:31:48 [D :: I2C] -[K]I2C_HWReset_fcn_7500
11/03/2007 13:31:48 [D :: I2C] I2C Status ERROR[KR0]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] I2C Status ERROR[KR1]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] I2C Status ERROR[KR2]: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] K:I2C Read Failed, status: 0x8701, ID = 0x6c
11/03/2007 13:31:48 [D :: I2C] I2C ReStatus ERROR[KR3]: 0x8701, ID = 0x6c
................
Has anyone else tried compiling and loading kernel modules for the new ROM?
I'm getting panics like this just after returning from the module_init function, even in a "hello world" style module that does absolutely nothing.
Guessing it won't work until we get the new kernel sources. (This was from compiling against a vanilla 3.1.10 tree).
Anyone know if it's possible to run the new stock Jelly Bean ROM with the ICS kernel?
Code:
<1>[13:03:10 00:11:38.645] Unable to handle kernel paging request at virtual address e7be5484
<1>[13:03:10 00:11:38.645] pgd = d37a0000
<1>[13:03:10 00:11:38.645] [e7be5484] *pgd=a6941811, *pte=00000000, *ppte=00000000
<0>[13:03:10 00:11:38.645] Internal error: Oops: 7 [#1] PREEMPT SMP
<4>[13:03:10 00:11:38.645] Modules linked in: max8971_forcer(-) bcmdhd raw_ip_net gator
<4>[13:03:10 00:11:38.645] CPU: 1 Not tainted (3.1.10-gedcab5a #1)
<4>[13:03:10 00:11:38.645] PC is at module_put+0x50/0x128
<4>[13:03:10 00:11:38.645] LR is at sys_init_module+0x1830/0x1a18
<4>[13:03:10 00:11:38.645] pc : [<c00a0a74>] lr : [<c00a377c>] psr: a0000013
<4>[13:03:10 00:11:38.645] sp : def8ded0 ip : def8def8 fp : def8def4
<4>[13:03:10 00:11:38.645] r10: 0000001c r9 : 00000024 r8 : 00000001
<4>[13:03:10 00:11:38.645] r7 : c00a377c r6 : 00000002 r5 : bf0807f8 r4 : bf0807f8
<4>[13:03:10 00:11:38.645] r3 : def8c000 r2 : e6ac4484 r1 : 01121000 r0 : 00000001
<4>[13:03:10 00:11:38.645] Flags: NzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user
<4>[13:03:10 00:11:38.645] Control: 10c5387d Table: 937a004a DAC: 00000015
arararagi said:
Has anyone else tried compiling and loading kernel modules for the new ROM?
I'm getting panics like this just after returning from the module_init function, even in a "hello world" style module that does absolutely nothing.
Guessing it won't work until we get the new kernel sources. (This was from compiling against a vanilla 3.1.10 tree).
Anyone know if it's possible to run the new stock Jelly Bean ROM with the ICS kernel?
Code:
<1>[13:03:10 00:11:38.645] Unable to handle kernel paging request at virtual address e7be5484
<1>[13:03:10 00:11:38.645] pgd = d37a0000
<1>[13:03:10 00:11:38.645] [e7be5484] *pgd=a6941811, *pte=00000000, *ppte=00000000
<0>[13:03:10 00:11:38.645] Internal error: Oops: 7 [#1] PREEMPT SMP
<4>[13:03:10 00:11:38.645] Modules linked in: max8971_forcer(-) bcmdhd raw_ip_net gator
<4>[13:03:10 00:11:38.645] CPU: 1 Not tainted (3.1.10-gedcab5a #1)
<4>[13:03:10 00:11:38.645] PC is at module_put+0x50/0x128
<4>[13:03:10 00:11:38.645] LR is at sys_init_module+0x1830/0x1a18
<4>[13:03:10 00:11:38.645] pc : [<c00a0a74>] lr : [<c00a377c>] psr: a0000013
<4>[13:03:10 00:11:38.645] sp : def8ded0 ip : def8def8 fp : def8def4
<4>[13:03:10 00:11:38.645] r10: 0000001c r9 : 00000024 r8 : 00000001
<4>[13:03:10 00:11:38.645] r7 : c00a377c r6 : 00000002 r5 : bf0807f8 r4 : bf0807f8
<4>[13:03:10 00:11:38.645] r3 : def8c000 r2 : e6ac4484 r1 : 01121000 r0 : 00000001
<4>[13:03:10 00:11:38.645] Flags: NzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user
<4>[13:03:10 00:11:38.645] Control: 10c5387d Table: 937a004a DAC: 00000015
Click to expand...
Click to collapse
I red just now the problem you posted and it's interesting, but since we got the JB sources...
It may be interesting still if we have some interesting feature from old kernel to port in new one.
Anyway, just for "developer sport" is interesting to know whats was specifically the fact or the code which can't make run modules.
Pesach85 said:
I red just now the problem you posted and it's interesting, but since we got the JB sources...
It may be interesting still if we have some interesting feature from old kernel to port in new one.
Anyway, just for "developer sport" is interesting to know whats was specifically the fact or the code which can't make run modules.
Click to expand...
Click to collapse
I think it was mostly to do with the compiler or flags used.
Not really worth investigating any more now that we can just change anything in the kernel sources.
It is problem when compiling with gnueabihf modules don't load.
Sent from my LG-P880 using xda app-developers app
Hi,
Concerning GT-N7000 Android 4.1.2
Every day at 7:23, my battery drains, but nobody uses the Note :
Cf Image at i38.servimg.com/u/f38/12/37/00/20/batter10.png
Here is a graph of processes (PID) activity made from the logcat :
i38.servimg.com/u/f38/12/37/00/20/logcat10.png
At 7:27, first the screen turns ON (while I am sleeping, as I am on holidays).
[ 07-07 07:27:01.282 2016: 2076 D/KeyguardViewMediator ]
onScreenTurnedOn, seq = 286
[ 07-07 07:27:01.282 2016: 2076 D/KeyguardViewMediator ]
notifyScreenOnLocked
[ 07-07 07:27:01.282 2016: 2079 D/KeyguardViewMediator ]
handleNotifyScreenOn
[ 07-07 07:27:01.282 2016: 2079 D/LockPatternKeyguardView ]
screen on
[ 07-07 07:27:01.282 2016: 2076 D/WindowManager ]
mSetIgnorePWR
[ 07-07 07:27:01.282 2016: 2079 D/CircleUnlockRippleRenderer ]
onResume isUnlocked = false
[ 07-07 07:27:01.287 2016: 2079 D/CircleShortcutWidget ]
onResume()
[ 07-07 07:27:01.312 2016: 2079 D/UnlockScreen ]
max failed attempt for device disable :0
[ 07-07 07:27:01.312 2016: 2079 D/UnlockScreen ]
isDeviceDisabledForMaxFailedAttempt return :false
[ 07-07 07:27:01.312 2016: 2079 V/LockPatternKeyguardView ]
Restoring widget state
[ 07-07 07:27:01.392 1736: 1736 I/AudioHardwareYamaha ]
AudioHardware::setParameters(keyValuePairs="screen_state=on")
[ 07-07 07:27:01.402 2016: 2059 I/TvoutService_Java ]
TvoutService Action : android.intent.action.SCREEN_ON
[ 07-07 07:27:01.512 2176: 2176 I/TwDVFSBroadcastReceiver ]
onScreenOnIntent
[ 07-07 07:27:01.572 1733: 1942 D/SurfaceFlinger ]
Screen about to return, flinger = 0x410ba008
[ 07-07 07:27:01.582 1733: 1895 D/SecTVOutService ]
virtual void android::SecTVOutService::setSuspendMode(uint32_t) TV suspend mode = 0
...
Process 2016 is system_server.
Then at 9:50, the process activity increases (I am still sleeping, nobody is using the Note) :
As the drain slope does not increases, I guess the may cause is the screen being ON.
[ 07-07 09:54:11.047 2016: 2077 V/AlarmManager ]
waitForAlarm result :2
[ 07-07 09:54:11.127 2016: 2027 W/AlarmManager ]
FACTORY_ON= 0
[ 07-07 09:54:11.182 22463:22465 D/dalvikvm ]
GC_CONCURRENT freed 399K, 11% free 12960K/14535K, paused 8ms+3ms, total 81ms
[ 07-07 09:54:11.427 2016: 2071 D/BatteryService ]
update start
[ 07-07 09:54:11.432 2016: 2071 D/BatteryService ]
level:50 scale:100 status:3 health:2 present:true voltage: 3758 temperature: 280 technology: Li-ion AC powered:false USB powered:false icon:17303251 invalid charger:0 online:0 charge type:0 current avg:1
[ 07-07 09:54:11.442 2159: 2159 D/STATUSBAR-BatteryController ]
onReceive() - ACTION_BATTERY_CHANGED
[ 07-07 09:54:11.442 2159: 2159 D/STATUSBAR-BatteryController ]
onReceive() - level:50
[ 07-07 09:54:11.442 2159: 2159 D/STATUSBAR-BatteryController ]
onReceive() - plugged:0
[ 07-07 09:54:11.442 2159: 2159 D/STATUSBAR-BatteryController ]
onReceive() - BATTERY_STATUS_DISCHARGING: stat_sys_battery
[ 07-07 09:54:11.462 2159: 2159 D/STATUSBAR-PhoneStatusBar ]
ACTION_BATTERY_CHANGED
[ 07-07 09:54:11.462 2159: 2159 D/STATUSBAR-PhoneStatusBar ]
NORMAL_BATTERY
[ 07-07 09:54:14.127 2016: 2077 V/AlarmManager ]
waitForAlarm result :2
[ 07-07 09:54:14.197 2016: 2403 W/AlarmManager ]
FACTORY_ON= 0
[ 07-07 09:54:17.197 2016: 2077 V/AlarmManager ]
waitForAlarm result :2
[ 07-07 09:54:17.332 2016: 2671 W/AlarmManager ]
FACTORY_ON= 0
[ 07-07 09:54:17.537 2016: 2017 D/dalvikvm ]
GC_CONCURRENT freed 1962K, 25% free 54844K/72519K, paused 44ms+13ms, total 334ms
[ 07-07 09:54:18.377 2016: 2253 E/Watchdog ]
[email protected] 14583
[ 07-07 09:54:20.327 2016: 2077 V/AlarmManager ]
waitForAlarm result :2
[ 07-07 09:54:20.402 2016: 2404 W/AlarmManager ]
FACTORY_ON= 0
[ 07-07 09:54:23.402 2016: 2077 V/AlarmManager ]
waitForAlarm result :2
[ 07-07 09:54:23.472 2016: 4137 W/AlarmManager ]
FACTORY_ON= 0
[ 07-07 09:54:26.472 2016: 2077 V/AlarmManager ]
waitForAlarm result :2
[ 07-07 09:54:26.547 2016: 2267 W/AlarmManager ]
FACTORY_ON= 0
[ 07-07 09:54:29.547 2016: 2077 V/AlarmManager ]
waitForAlarm result :2
[ 07-07 09:54:29.622 2016: 2027 W/AlarmManager ]
FACTORY_ON= 0
[ 07-07 09:54:32.622 2016: 2077 V/AlarmManager ]
waitForAlarm result :2
[ 07-07 09:54:32.692 2016: 2419 W/AlarmManager ]
FACTORY_ON= 0
[ 07-07 09:54:35.692 2016: 2077 V/AlarmManager ]
waitForAlarm result :2
[ 07-07 09:54:35.762 2016: 2667 W/AlarmManager ]
FACTORY_ON= 0
[ 07-07 09:54:38.762 2016: 2077 V/AlarmManager ]
waitForAlarm result :2
[ 07-07 09:54:38.827 2016: 2027 W/AlarmManager ]
FACTORY_ON= 0
[ 07-07 09:54:41.827 2016: 2077 V/AlarmManager ]
waitForAlarm result :2
[ 07-07 09:54:41.902 2016: 4144 W/AlarmManager ]
FACTORY_ON= 0
[ 07-07 09:54:44.902 2016: 2077 V/AlarmManager ]
waitForAlarm result :2
[ 07-07 09:54:44.972 2016: 2016 W/AlarmManager ]
FACTORY_ON= 0
[ 07-07 09:54:47.972 2016: 2077 V/AlarmManager ]
waitForAlarm result :2
[ 07-07 09:54:48.042 2016: 2027 W/AlarmManager ]
FACTORY_ON= 0
[ 07-07 09:54:48.377 2016: 2253 E/Watchdog ]
[email protected] 14584
[ 07-07 09:54:51.047 2016: 2077 V/AlarmManager ]
waitForAlarm result :2
[ 07-07 09:54:51.117 2016: 4137 W/AlarmManager ]
FACTORY_ON= 0
[ 07-07 09:54:51.582 2016: 2071 D/BatteryService ]
update start
[ 07-07 09:54:51.587 2016: 2071 D/BatteryService ]
level:50 scale:100 status:3 health:2 present:true voltage: 3755 temperature: 280 technology: Li-ion AC powered:false USB powered:false icon:17303251 invalid charger:0 online:0 charge type:0 current avg:1
[ 07-07 09:54:51.597 2159: 2159 D/STATUSBAR-BatteryController ]
onReceive() - ACTION_BATTERY_CHANGED
Any idea to cure that ?
notworking said:
Hi,
Concerning GT-N7000 Android 4.1.2
Every day at 7:23, my battery drains, but nobody uses the Note :
Cf Image at i38.servimg.com/u/f38/12/37/00/20/batter10.png
Here is a graph of processes (PID) activity made from the logcat :
i38.servimg.com/u/f38/12/37/00/20/logcat10.png
At 7:27, first the screen turns ON (while I am sleeping, as I am on holidays).
[ 07-07 07:27:01.282 2016: 2076 D/KeyguardViewMediator ]
onScreenTurnedOn, seq = 286
[ 07-07 07:27:01.282 2016: 2076 D/KeyguardViewMediator ]
notifyScreenOnLocked
[ 07-07 07:27:01.282 2016: 2079 D/KeyguardViewMediator ]
handleNotifyScreenOn
[ 07-07 07:27:01.282 2016: 2079 D/LockPatternKeyguardView ]
screen on
[ 07-07 07:27:01.282 2016: 2076 D/WindowManager ]
mSetIgnorePWR
[ 07-07 07:27:01.282 2016: 2079 D/CircleUnlockRippleRenderer ]
onResume isUnlocked = false
[ 07-07 07:27:01.287 2016: 2079 D/CircleShortcutWidget ]
onResume()
[ 07-07 07:27:01.312 2016: 2079 D/UnlockScreen ]
max failed attempt for device disable :0
[ 07-07 07:27:01.312 2016: 2079 D/UnlockScreen ]
isDeviceDisabledForMaxFailedAttempt return :false
[ 07-07 07:27:01.312 2016: 2079 V/LockPatternKeyguardView ]
Restoring widget state
[ 07-07 07:27:01.392 1736: 1736 I/AudioHardwareYamaha ]
AudioHardware::setParameters(keyValuePairs="screen_state=on")
[ 07-07 07:27:01.402 2016: 2059 I/TvoutService_Java ]
TvoutService Action : android.intent.action.SCREEN_ON
[ 07-07 07:27:01.512 2176: 2176 I/TwDVFSBroadcastReceiver ]
onScreenOnIntent
[ 07-07 07:27:01.572 1733: 1942 D/SurfaceFlinger ]
Screen about to return, flinger = 0x410ba008
[ 07-07 07:27:01.582 1733: 1895 D/SecTVOutService ]
virtual void android::SecTVOutService::setSuspendMode(uint32_t) TV suspend mode = 0
...
Process 2016 is system_server.
Then at 9:50, the process activity increases (I am still sleeping, nobody is using the Note) :
As the drain slope does not increases, I guess the may cause is the screen being ON.
[ 07-07 09:54:11.047 2016: 2077 V/AlarmManager ]
waitForAlarm result :2
[ 07-07 09:54:11.127 2016: 2027 W/AlarmManager ]
FACTORY_ON= 0
[ 07-07 09:54:11.182 22463:22465 D/dalvikvm ]
GC_CONCURRENT freed 399K, 11% free 12960K/14535K, paused 8ms+3ms, total 81ms
[ 07-07 09:54:11.427 2016: 2071 D/BatteryService ]
update start
[ 07-07 09:54:11.432 2016: 2071 D/BatteryService ]
level:50 scale:100 status:3 health:2 present:true voltage: 3758 temperature: 280 technology: Li-ion AC powered:false USB powered:false icon:17303251 invalid charger:0 online:0 charge type:0 current avg:1
[ 07-07 09:54:11.442 2159: 2159 D/STATUSBAR-BatteryController ]
onReceive() - ACTION_BATTERY_CHANGED
[ 07-07 09:54:11.442 2159: 2159 D/STATUSBAR-BatteryController ]
onReceive() - level:50
[ 07-07 09:54:11.442 2159: 2159 D/STATUSBAR-BatteryController ]
onReceive() - plugged:0
[ 07-07 09:54:11.442 2159: 2159 D/STATUSBAR-BatteryController ]
onReceive() - BATTERY_STATUS_DISCHARGING: stat_sys_battery
[ 07-07 09:54:11.462 2159: 2159 D/STATUSBAR-PhoneStatusBar ]
ACTION_BATTERY_CHANGED
[ 07-07 09:54:11.462 2159: 2159 D/STATUSBAR-PhoneStatusBar ]
NORMAL_BATTERY
[ 07-07 09:54:14.127 2016: 2077 V/AlarmManager ]
waitForAlarm result :2
[ 07-07 09:54:14.197 2016: 2403 W/AlarmManager ]
FACTORY_ON= 0
[ 07-07 09:54:17.197 2016: 2077 V/AlarmManager ]
waitForAlarm result :2
[ 07-07 09:54:17.332 2016: 2671 W/AlarmManager ]
FACTORY_ON= 0
[ 07-07 09:54:17.537 2016: 2017 D/dalvikvm ]
GC_CONCURRENT freed 1962K, 25% free 54844K/72519K, paused 44ms+13ms, total 334ms
[ 07-07 09:54:18.377 2016: 2253 E/Watchdog ]
[email protected] 14583
[ 07-07 09:54:20.327 2016: 2077 V/AlarmManager ]
waitForAlarm result :2
[ 07-07 09:54:20.402 2016: 2404 W/AlarmManager ]
FACTORY_ON= 0
[ 07-07 09:54:23.402 2016: 2077 V/AlarmManager ]
waitForAlarm result :2
[ 07-07 09:54:23.472 2016: 4137 W/AlarmManager ]
FACTORY_ON= 0
[ 07-07 09:54:26.472 2016: 2077 V/AlarmManager ]
waitForAlarm result :2
[ 07-07 09:54:26.547 2016: 2267 W/AlarmManager ]
FACTORY_ON= 0
[ 07-07 09:54:29.547 2016: 2077 V/AlarmManager ]
waitForAlarm result :2
[ 07-07 09:54:29.622 2016: 2027 W/AlarmManager ]
FACTORY_ON= 0
[ 07-07 09:54:32.622 2016: 2077 V/AlarmManager ]
waitForAlarm result :2
[ 07-07 09:54:32.692 2016: 2419 W/AlarmManager ]
FACTORY_ON= 0
[ 07-07 09:54:35.692 2016: 2077 V/AlarmManager ]
waitForAlarm result :2
[ 07-07 09:54:35.762 2016: 2667 W/AlarmManager ]
FACTORY_ON= 0
[ 07-07 09:54:38.762 2016: 2077 V/AlarmManager ]
waitForAlarm result :2
[ 07-07 09:54:38.827 2016: 2027 W/AlarmManager ]
FACTORY_ON= 0
[ 07-07 09:54:41.827 2016: 2077 V/AlarmManager ]
waitForAlarm result :2
[ 07-07 09:54:41.902 2016: 4144 W/AlarmManager ]
FACTORY_ON= 0
[ 07-07 09:54:44.902 2016: 2077 V/AlarmManager ]
waitForAlarm result :2
[ 07-07 09:54:44.972 2016: 2016 W/AlarmManager ]
FACTORY_ON= 0
[ 07-07 09:54:47.972 2016: 2077 V/AlarmManager ]
waitForAlarm result :2
[ 07-07 09:54:48.042 2016: 2027 W/AlarmManager ]
FACTORY_ON= 0
[ 07-07 09:54:48.377 2016: 2253 E/Watchdog ]
[email protected] 14584
[ 07-07 09:54:51.047 2016: 2077 V/AlarmManager ]
waitForAlarm result :2
[ 07-07 09:54:51.117 2016: 4137 W/AlarmManager ]
FACTORY_ON= 0
[ 07-07 09:54:51.582 2016: 2071 D/BatteryService ]
update start
[ 07-07 09:54:51.587 2016: 2071 D/BatteryService ]
level:50 scale:100 status:3 health:2 present:true voltage: 3755 temperature: 280 technology: Li-ion AC powered:false USB powered:false icon:17303251 invalid charger:0 online:0 charge type:0 current avg:1
[ 07-07 09:54:51.597 2159: 2159 D/STATUSBAR-BatteryController ]
onReceive() - ACTION_BATTERY_CHANGED
Any idea to cure that ?
Click to expand...
Click to collapse
is your phone rooted? any wakeclocks app installed. try flashing stock rom again on stcok JB kernel.
I have just rooted it. And before that used Wakelock Detector.
I also tried to reboot, free memory (that killed some unused apps), just before going to sleep. But the same bug appears : at 7h27, "onScreenTurnedOn" in the logcat, system_server and com.android.systemui draining the battery.
One night, "S Note" wake up at 7h27, so, as I do not use this app, I have just removed it (since my Note is rooted now). We will see.
Cured !
FYI,
I removed "S Note" (a samsung application) and have no battery drain this night !
It is a pain to need root privilege to do that.
Anybody switched its Note to plain Android, with no samsung app ?
Is it difficult ?
To be complete, the onScreenTurnedOn is still present in logcat at 7h27, but it is followed by a onScreenTurnedOff 1 second later.
notworking said:
FYI,
I removed "S Note" (a samsung application) and have no battery drain this night !
It is a pain to need root privilege to do that.
Anybody switched its Note to plain Android, with no samsung app ?
Is it difficult ?
Click to expand...
Click to collapse
might be coincidence, but few days ago both my Notes lost the ability of syncing SNotes, which resulted in heavy battery drain - in my case it was enough to turn it's sync off (and add SNOTE folder to Folder sync which I use anyway)
Switching to plain Android is easy, every ROM thread has instructions how to do it (check Slimbean, Carbon, CM), what you gain is much faster and battery friendly system.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps) . LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.
Device source code:
msm8974-common (shared by all Samsung msm8974 devices): LineageOS/android_device_samsung_msm8974-common
klte-common (shared by all klte* devices): LineageOS/android_device_samsung_klte-common
klte: LineageOS/android_device_samsung_klte
klteactivexx: LineageOS/android_device_samsung_klteactivexx
kltechn: LineageOS/android_device_samsung_kltechn
kltechnduo: LineageOS/android_device_samsung_kltechnduo
klteduos: LineageOS/android_device_samsung_klteduos
kltedv: LineageOS/android_device_samsung_kltedv
kltekdi: LineageOS/android_device_samsung_kltekdi
kltekor: LineageOS/android_device_samsung_kltekor
Kernel source code:
LineageOS/android_kernel_samsung_msm8974
My picks:
https://github.com/haggertk/cm_build_stuff/blob/lineage-18.1/picks.sh (other than the open device/kernel changes on gerrit)
Build Compatibility:
The noted models are the only ones supported. If you have a model that isn't listed and ask politely then I might work to add compatibility.
BuildModelklteSM-G900F, SM-G900M, SM-G900R4, SM-G900R7, SM-G900T, SM-G900V, SM-G900W8klteactivexxSM-G870FklteaioSM-G900AZ, SM-S902LkltechnSM-G9006V, SM-G9008VkltechnduoSM-G9006W, SM-G9008W, SM-G9009WklteduosSM-G900FD, SM-G900MDkltedvSM-G900I, SM-G900PkltekdiSC-04F, SCL23kltekorSM-G900K, SM-G900L, SM-G900S
Downloads:
https://androidfilehost.com/?w=files&flid=321278
Installation Instructions:
Download latest build
Boot into recovery
Lineage recovery images are included in the download section and that's what I support. If you feel like using TWRP and something isn't working then take it up with the TWRP maintainer
If not updating from one of my earlier unofficial builds, then format/system, /data, and /cache
For Lineage recovery:
Format -> Format data/factory reset (this does /data and /cache)
Format -> Format system partition
For TWRP figure it out. And no, "wipe data" isn't the same as formatting data
Install LineageOS zip
If this is your initial installation of LineageOS 18.1, then flash any addons (e.g., gapps)
Reporting Bugs:
DO NOT even think about reporting bugs if you are running a custom kernel, Magisk, or Xposed
Grab a logcat after the problem has occurred
If there is a random reboot then grab /proc/last_kmsg. A logcat AFTER the reboot will be worthless
Note which build AND device you have
Read the thread, at least the last month's worth of posts. Don't report things that others already have.
Compatibility Notes:
Bootloader version doesn't matter. Anyone who tells you so doesn't know what they are taking about. My Developer Edition G900V is still running the original 4.4.2 KK aboot. My G900W8 is running the latest 6.0.1.
All builds except for klteactivexx MUST be running a marshmallow (6.0.1) radio for RIL to work. If you are about to report that RIL/radio isn't working then I pretty much guarantee this is your issue.
You MUST be running a marshmallow (6.0.1) NON-HLOS for the fingerprint reader to work. If you are about to report a fingerprint reader problem then you either have old firmware (update it), your /data was previously encrypted and you performed a "clean" flash without FORMATTING /data (start over and FORMAT /data), or your reader is just broken.
External SD cards don't support POSIX (ext*, f2fs) or NTFS filesystems anymore. It was kind of broken in 17 and we likely won't merge the changes to add it back in for 18. I'm not going to pick the open changes to re-add support because I'm not going to deal with "but it worked on haggertk's unofficial builds" bug reports after we eventually go official. If this affects you then just bite the bullet, copy any data off you really want to save, and reformat as exfat.
Donations:
I absolutely don't personally accept them. If you really feel that this work deserves it, then find a local food bank or animal shelter/rescue and throw some money their way. You can also throw some the way of LineageOS, but we're actually doing pretty well right now.
Reserved -- just in case.
Tx so much for keeping our beloved S5 alive
Thank you Mr. @haggertk for keeping our old S5 up to date.
It's not mentioned in the OP @ the present but could you tell me please if SELinux is set to Permissive or Enforcing?
If it's SELinux Permissive would you say that it's not ready to be used as a daily driver with important user accounts @ the present?
***
curiousrom said:
Thank you Mr. @haggertk for keeping our old S5 up to date.
It's not mention in the OP @ the present but could you tell me please if SELinux is set to Permissive or Enforcing?
If it's SELinux Permissive would you say that it's not ready to be used as a daily driver with important user accounts @ the present?
***
Click to expand...
Click to collapse
Hi
I already flashed and it is enforcing
G900T.. CrDroid 7.0 lineage-18.1-20201225-INOFFICIAL-klte.zip... BitGapps v19 .. Magisk 21.1 ... TWRP 3.4... latest Modem.
Radio: G900TUVU1GRJ1 (6.0.1)
Good news: mostly everything works fine (including cellular data, calls, apps).
Problems: Google Maps crash (have to use incognito mode as workaround), Location data limited to GPS only (not AGPS/cellular).
Abnormal errors (most were there in previous releases, and these are periodic/frequent, seen in some other 18.x ROMs):
AGPS Location (partly related to BitGapps v19):
12-28 09:22:53.058 2118 2118 E IndoorOutdoorPredictor: Failed:
12-28 09:22:53.058 2118 2118 E IndoorOutdoorPredictor: java.lang.SecurityException: uid 10005 does not have android.permission.ACCESS_FINE_LOCATION.
12-28 09:22:53.058 2118 2118 E IndoorOutdoorPredictor: at android.os.Parcel.createExceptionOrNull(Parcel.java:2373)
12-28 09:18:28.399 866 1040 W ActivityManager: Appop Denial: Accessing service com.google.android.gms/com.google.android.location.internal.server.GoogleLocationService from pid=2118, uid=10005 requires appop COARSE_LOCATION
TCP read errors:
12-28 09:29:36.462 1321 2335 E TcpSocketTracker: Unexpected socket info parsing, family 10 buffer:java.nio.HeapByteBuffer[pos=96 lim=588 cap=60000] xAAAABQAAgAAAAAAKQUAAAoBAADVBBRsAAAAAAAAAAAAAP//CsRBmgAAAAAAAAAAAAD//0p9ibwAAAAAAIt51wAAA
....
12-28 09:29:36.469 1321 2335 E TcpSocketTracker: java.lang.IllegalArgumentException: Bad position 65632/588
12-28 09:29:36.469 1321 2335 E TcpSocketTracker: at java.nio.Buffer.position(Buffer.java:259)
12-28 09:29:36.469 1321 2335 E TcpSocketTracker: at java.nio.ByteBuffer.position(ByteBuffer.java:812)
12-28 09:29:36.469 1321 2335 E TcpSocketTracker: at com.android.networkstack.netlink.TcpSocketTracker.skipRemainingAttributesBytesAligned(TcpSocketTracker.java:427)
Missing hardware:
12-28 09:27:59.244 0 0 E sdhci_msm_vreg_disable: vdd-io Cannot find Regulator
12-28 09:27:59.253 0 0 E samsung_dsi_panel_event_handler: unknown event (7)
RIL:
12-28 09:23:00.594 474 815 E RIL-QMI : qmuxd: TX message on fd=21, to qmux_client_id=0x1, len=72
12-28 09:23:00.596 474 474 E RIL-QMI : qmuxd: RX 47 bytes on fd=21 from qmux_client_id=0x1
Thank you. And if anyone built with signature spoofing, please contact me. We still have no convenient method to patch android 11 after building.
ttesty said:
G900T.. CrDroid 7.0 lineage-18.1-20201225-INOFFICIAL-klte.zip... BitGapps v19 .. Magisk 21.1 ... TWRP 3.4... latest Modem.
Radio: G900TUVU1GRJ1 (6.0.1)
Good news: mostly everything works fine (including cellular data, calls, apps).
Problems: Google Maps crash (have to use incognito mode as workaround), Location data limited to GPS only (not AGPS/cellular).
Abnormal errors (most were there in previous releases, and these are periodic/frequent, seen in some other 18.x ROMs):
AGPS Location (partly related to BitGapps v19):
12-28 09:22:53.058 2118 2118 E IndoorOutdoorPredictor: Failed:
12-28 09:22:53.058 2118 2118 E IndoorOutdoorPredictor: java.lang.SecurityException: uid 10005 does not have android.permission.ACCESS_FINE_LOCATION.
12-28 09:22:53.058 2118 2118 E IndoorOutdoorPredictor: at android.os.Parcel.createExceptionOrNull(Parcel.java:2373)
12-28 09:18:28.399 866 1040 W ActivityManager: Appop Denial: Accessing service com.google.android.gms/com.google.android.location.internal.server.GoogleLocationService from pid=2118, uid=10005 requires appop COARSE_LOCATION
TCP read errors:
12-28 09:29:36.462 1321 2335 E TcpSocketTracker: Unexpected socket info parsing, family 10 buffer:java.nio.HeapByteBuffer[pos=96 lim=588 cap=60000] xAAAABQAAgAAAAAAKQUAAAoBAADVBBRsAAAAAAAAAAAAAP//CsRBmgAAAAAAAAAAAAD//0p9ibwAAAAAAIt51wAAA
....
12-28 09:29:36.469 1321 2335 E TcpSocketTracker: java.lang.IllegalArgumentException: Bad position 65632/588
12-28 09:29:36.469 1321 2335 E TcpSocketTracker: at java.nio.Buffer.position(Buffer.java:259)
12-28 09:29:36.469 1321 2335 E TcpSocketTracker: at java.nio.ByteBuffer.position(ByteBuffer.java:812)
12-28 09:29:36.469 1321 2335 E TcpSocketTracker: at com.android.networkstack.netlink.TcpSocketTracker.skipRemainingAttributesBytesAligned(TcpSocketTracker.java:427)
Missing hardware:
12-28 09:27:59.244 0 0 E sdhci_msm_vreg_disable: vdd-io Cannot find Regulator
12-28 09:27:59.253 0 0 E samsung_dsi_panel_event_handler: unknown event (7)
RIL:
12-28 09:23:00.594 474 815 E RIL-QMI : qmuxd: TX message on fd=21, to qmux_client_id=0x1, len=72
12-28 09:23:00.596 474 474 E RIL-QMI : qmuxd: RX 47 bytes on fd=21 from qmux_client_id=0x1
Click to expand...
Click to collapse
This seemed to fix a few of the problems. Some of the problems might not be exclusive to the ROM - rather GAPPS etc:
pm grant com.google.android.gms android.permission.ACCESS_COARSE_LOCATION
pm grant com.google.android.gms android.permission.ACCESS_FINE_LOCATION
Just installed this. Smooth af.
Once again thanks a lot Mr Haggertk for bringing android 11 to our beloved Samsung Galaxy S5. Here are some screenshots made with my SM-G900F
Thanks for all your hard work <3
gaindelioide said:
...Here are some screenshots made with my SM-G900F
Click to expand...
Click to collapse
Thanks for the effort but 2 comments:
You should not post personal data like your device's IMEI & Vorschau > Eindeutige id. You could black them out with an image editor or just delete those screenshots.
Because the common language in this thread is English maybe you could change the System language to that before taking the screenshots?
How does the Settings panel looks like?
***
And for you guys who ran LineageOS 17.1 previously: any noticeable changes you could comment on?
***
Pretty stable. I get a lot of these messages for many different applications and during boot time. Probably normal page faults (data missing from memory).
12-30 00:24:14.808 0 0 F : pgd = d4dbc000
12-30 00:24:14.808 0 0 F : [00000000] *pgd=00000000
12-30 00:24:14.808 0 0 W Pid : 32432, comm: hone.app2sd.pro
12-30 00:24:14.808 0 0 W : CPU: 0 Tainted: G W (3.4.113-lineageos-g11473dbb0031 #18)
12-30 00:24:14.808 0 0 W : PC is at 0x7215022a
12-30 00:24:14.808 0 0 W : LR is at 0x72150227
12-30 00:24:14.808 0 0 W pc : [<7215022a>] lr : [<72150227>] psr: 600e0030
12-30 00:24:14.808 0 0 W sp : be853ce0 ip : 00000000 fp : be853d4c
12-30 00:24:14.808 0 0 W : r10: 136b32c0 r9 : ade4ce00 r8 : 00000000
12-30 00:24:14.808 0 0 W : r7 : 00000000 r6 : 136b32c0 r5 : 00000000 r4 : 00000000
12-30 00:24:14.808 0 0 W : r3 : 00000001 r2 : 00000000 r1 : 00000000 r0 : 717b4f84
12-30 00:24:14.808 0 0 W Flags : nZCv IRQs on FIQs on Mode USER_32 ISA Thumb Segment user
12-30 00:24:14.808 0 0 W Control : 10c5787d Table: 14dbc06a DAC: 00000015
12-30 00:24:14.808 0 0 W : [<c010be28>] (unwind_backtrace+0x0/0xec) from [<c01121a8>] (__do_user_fault+0x100/0x14c)
12-30 00:24:14.808 0 0 W : [<c01121a8>] (__do_user_fault+0x100/0x14c) from [<c011251c>] (do_page_fault+0x328/0x36c)
12-30 00:24:14.808 0 0 W : [<c011251c>] (do_page_fault+0x328/0x36c) from [<c0100358>] (do_DataAbort+0x10c/0x200)
12-30 00:24:14.808 0 0 W : [<c0100358>] (do_DataAbort+0x10c/0x200) from [<c01059d4>] (__dabt_usr+0x34/0x40)
12-30 00:24:14.808 0 0 W : Exception stack(0xd222bfb0 to 0xd222bff8)
12-30 00:24:14.808 0 0 W bfa0 : 717b4f84 00000000 00000000 00000001
12-30 00:24:14.808 0 0 W bfc0 : 00000000 00000000 136b32c0 00000000 00000000 ade4ce00 136b32c0 be853d4c
12-30 00:24:14.808 0 0 W bfe0 : 00000000 be853ce0 72150227 7215022a 600e0030 ffffffff
12-30 00:29:17.388 0 0 F : pgd = d8634000
12-30 00:29:17.388 0 0 F : [00000000] *pgd=00000000
12-30 00:29:17.388 0 0 W Pid : 4629, comm: verycallcontrol
12-30 00:29:17.388 0 0 W : CPU: 0 Tainted: G W (3.4.113-lineageos-g11473dbb0031 #18)
12-30 00:29:17.388 0 0 W : PC is at 0x7215022a
12-30 00:29:17.388 0 0 W : LR is at 0x72150227
12-30 00:29:17.388 0 0 W pc : [<7215022a>] lr : [<72150227>] psr: 600b0030
12-30 00:29:17.388 0 0 W sp : be854930 ip : 00000000 fp : 132bb498
12-30 00:29:17.388 0 0 W : r10: 132bc0a8 r9 : ade4ce00 r8 : 00000000
12-30 00:29:17.388 0 0 W : r7 : 00000000 r6 : 132bc0a8 r5 : 00000000 r4 : be8529b8
12-30 00:29:17.388 0 0 W : r3 : 00000001 r2 : 00000000 r1 : 00000000 r0 : 717b4f84
12-30 00:29:17.388 0 0 W Flags : nZCv IRQs on FIQs on Mode USER_32 ISA Thumb Segment user
12-30 00:29:17.388 0 0 W Control : 10c5787d Table: 1863406a DAC: 00000015
12-30 00:29:17.388 0 0 W : [<c010be28>] (unwind_backtrace+0x0/0xec) from [<c01121a8>] (__do_user_fault+0x100/0x14c)
12-30 00:29:17.388 0 0 W : [<c01121a8>] (__do_user_fault+0x100/0x14c) from [<c011251c>] (do_page_fault+0x328/0x36c)
12-30 00:29:17.388 0 0 W : [<c011251c>] (do_page_fault+0x328/0x36c) from [<c0100358>] (do_DataAbort+0x10c/0x200)
12-30 00:29:17.388 0 0 W : [<c0100358>] (do_DataAbort+0x10c/0x200) from [<c01059d4>] (__dabt_usr+0x34/0x40)
12-30 00:29:17.388 0 0 W : Exception stack(0xd86b9fb0 to 0xd86b9ff8)
12-30 00:29:17.388 0 0 W 9fa0 : 717b4f84 00000000 00000000 00000001
12-30 00:29:17.388 0 0 W 9fc0 : be8529b8 00000000 132bc0a8 00000000 00000000 ade4ce00 132bc0a8 132bb498
12-30 00:29:17.388 0 0 W 9fe0 : 00000000 be854930 72150227 7215022a 600b0030 ffffffff
12-30 00:29:17.616 0 0 E [SSP] : proximity_open_calibration - Can't open cancelation file
12-30 00:29:17.616 0 0 E [SSP] : set_proximity_threshold - SENSOR_PROXTHRESHOLD
How's the gaming performance? Has anyone tested it with PUBGM or CoDM?
curiousrom said:
Thanks for the effort but 2 comments:
You should not post personal data like your device's IMEI & Vorschau > Eindeutige id. You could black them out with an image editor or just delete those screenshots.
Because the common language in this thread is English maybe you could change the System language to that before taking the screenshots?
How does the Settings panel looks like?
***
And for you guys who ran LineageOS 17.1 previously: any noticeable changes you could comment on?
***
Click to expand...
Click to collapse
Hi curiousrom,
Thank you for yours advices. Could you please tell me precisely what you mean with the "Settings panel"? The QS panel or the General Settings panel?
I can tell you that since I flashed the ROM I have not had any particular issue worth a mention in my system. Only WhatsApp crashes from time to time. The phone app is behaving the way I expected it. The sensor is functioning properly since I do not see a black screen anymore after a call. With LineageOS 17.1 that still persist.
I will stay in touch through this thread for reporting any misbehavior of the system. Mr Haggertk is really doing a great job for the owners of our legendary device Samsung Galaxy S5. I own an SM-G900F.
Some of the unhandled page faults on startup (there are many):
[ 60.743339] CPU: 1 Tainted: G W (3.4.113-lineageos-g11473dbb0031 #18)
[ 60.743345] PC is at 0x7118e758
[ 60.743348] LR is at 0x7118e755
[ 60.743353] pc : [<7118e758>] lr : [<7118e755>] psr: 60000030
[ 60.743355] sp : 92bec890 ip : 00000000 fp : 92bec904
[ 60.743359] r10: 92bec940 r9 : ac1f1400 r8 : 00000000
[ 60.743364] r7 : 137cbb60 r6 : 00000000 r5 : 00000000 r4 : 57fb4540
[ 60.743368] r3 : 00000000 r2 : 00000000 r1 : 00000000 r0 : 70831754
[ 60.743374] Flags: nZCv IRQs on FIQs on Mode USER_32 ISA Thumb Segment user
[ 60.743379] Control: 10c5787d Table: 2489c06a DAC: 00000015
[ 60.743399] [<c010be28>] (unwind_backtrace+0x0/0xec) from [<c01121a8>] (__do_user_fault+0x100/0x14c)
[ 60.743410] [<c01121a8>] (__do_user_fault+0x100/0x14c) from [<c011251c>] (do_page_fault+0x328/0x36c)
[ 60.743419] [<c011251c>] (do_page_fault+0x328/0x36c) from [<c0100358>] (do_DataAbort+0x10c/0x200)
[ 60.743429] [<c0100358>] (do_DataAbort+0x10c/0x200) from [<c01059d4>] (__dabt_usr+0x34/0x40)
[ 60.743435] Exception stack(0xe3acdfb0 to 0xe3acdff8)
[ 60.743440] dfa0: 70831754 00000000 00000000 00000000
[ 60.743446] dfc0: 57fb4540 00000000 00000000 137cbb60 00000000 ac1f1400 92bec940 92bec904
[ 60.743452] dfe0: 00000000 92bec890 7118e755 7118e758 60000030 ffffffff
[ 60.778394] Thread-1: unhandled page fault (11) at 0x00000000, code 0x005
[ 60.778402] pgd = e489c000
[ 60.778591] [00000000] *pgd=00000000
[ 67.835852] Pid: 2836, comm: APIGuard3Backgr
[ 67.835860] CPU: 2 Tainted: G W (3.4.113-lineageos-g11473dbb0031 #18)
[ 67.835867] PC is at 0x7d48bc70
[ 67.835871] LR is at 0x712ba17f
[ 67.835877] pc : [<7d48bc70>] lr : [<712ba17f>] psr: 000f0030
[ 67.835880] sp : 7b20aa80 ip : 00000000 fp : 00000060
[ 67.835885] r10: 00000000 r9 : a9774e00 r8 : 00000000
[ 67.835891] r7 : 12cd26e8 r6 : 12cd24b8 r5 : 12cd2708 r4 : 710feac8
[ 67.835897] r3 : 70f53c50 r2 : 12cd2708 r1 : 00000000 r0 : 00000003
[ 67.835904] Flags: nzcv IRQs on FIQs on Mode USER_32 ISA Thumb Segment user
[ 67.835910] Control: 10c5787d Table: 1e69406a DAC: 00000015
[ 67.835932] [<c010be28>] (unwind_backtrace+0x0/0xec) from [<c01121a8>] (__do_user_fault+0x100/0x14c)
[ 67.835945] [<c01121a8>] (__do_user_fault+0x100/0x14c) from [<c011251c>] (do_page_fault+0x328/0x36c)
[ 67.835957] [<c011251c>] (do_page_fault+0x328/0x36c) from [<c0100358>] (do_DataAbort+0x10c/0x200)
[ 67.835969] [<c0100358>] (do_DataAbort+0x10c/0x200) from [<c01059d4>] (__dabt_usr+0x34/0x40)
[ 67.835976] Exception stack(0xdecdffb0 to 0xdecdfff8)
[ 67.835982] ffa0: 00000003 00000000 12cd2708 70f53c50
[ 67.835990] ffc0: 710feac8 12cd2708 12cd24b8 12cd26e8 00000000 a9774e00 00000000 00000060
[ 67.835998] ffe0: 00000000 7b20aa80 712ba17f 7d48bc70 000f0030 ffffffff
Minor issue. When logging in to my wifi which is wpa enterprise it requires a domain name as the phase 2 authentication defaults to MSCHAPV2 and has no option for "do not authenticate". Since I don't know my domain name is there a workaround?
haggertk said:
...
All builds except for klteactivexx MUST be running a marshmallow (6.0.1) radio for RIL to work. If you are about to report that RIL/radio isn't working then I pretty much guarantee this is your issue.
You MUST be running a marshmallow (6.0.1) NON-HLOS for the fingerprint reader to work. If you are about to report a fingerprint reader problem then you either have old firmware (update it), your /data was previously encrypted and you performed a "clean" flash without FORMATTING /data (start over and FORMAT /data), or your reader is just broken.
Click to expand...
Click to collapse
See S5 Odin Flashable Modem & Bootloader and S5 Screen Lock Fingerprint Battery Tests @ Idle - BetterBatteryStat.
***
It seems like my SC-04F doesn't show charging when I plugged in. The % goes up after rebooting.
Baseband: SC04FOMU1XQH1 (latest)
ROM Build: kltekdi, build 20201225
These are the logs when I only wiped System and Cache. I later formatted Data and it's still the same.
Thank you for your work!
e: Logcat: https://pastebin.pl/view/4de644ca
dmesg is the uploaded file.
e3: after formatting. Had to have Magisk to get dmesg log
dmesg: https://pastebin.pl/view/46bc06dc
logcat: https://pastebin.pl/view/1d2b50a8
Hey @haggertk, I have a SM-S902L. Can I use the rom for SM-S900L for my device? If not would you be so kind and add support for my model? I had been waiting for lineage 17.1 for quite some time now and installed an unofficial build to get android 10. I just found this amazing thread which is a way for me to get android 11. Please consider my request. Thanks
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