Database Develop

[KBD] [Updated 21-Dec-2009]Russian keyborad layout for HTC Full Qwerty keyboard

Hi,
recently I've found out that it is possible to tweak the HTC full qwerty keyboard,so I decided to share my findings with whoever needs that .
So , I have prepared 2 layouts for Russian language , Portrait and Landscape,
and I am posting them here.
As I am not using Russian often, I'd like to get your feedback and changes requests.
Attached are screen-shots and needed CABs.
HTC_Full_qwerty_russian_layout.cab : Layout files
HTC_full_Qwerty_En_It_Gr_Sp_Fr_Ru.cab : sets the list of available languages in HTC full Qwerty to English,Italic,German,Spanish,French and Russian.You HAVE to soft reset after installing this CAB.
HTC_full_Qwerty_En_It_Ru.CAB : sets the list of available languages in HTC full Qwerty to English,Italic and Russian.You HAVE to soft reset after installing this CAB.
More variations are possible.
I am planning to create a proggy for that, and your help is welcome, due to my lack of experience in WM coding.
Well, waiting for comments/requests and help offers...
Enjoy!
P.S : Tested on my Fuze with HTC Full Qwerty 1.5 Build 33955. On my friends Diamond with HTC Full Keyboard 1.5 different build, it worked a bit differently.
Update 21-Dec-2009
Added Russian layout for EzInput 2.x .
I know it has some minor problems, though I will probably not fix them.
Landscape mode on Fuze/TP will disappoint you, as it is designed for Diamond2/TP2.
I will probably not fix that either.
The file you have to download is ezinput2RusLayout.cab , you don't need the HTC_Full_qwerty_russian_layout.cab , it is for EzInput 1.5.
As before, it is only layout data.
To enable Russian in selection list, use my HTC_full_Qwerty_En_It_Ru.CAB, or
edit the registry manually.
Post your feedback as it pleases me to know people use what I've done.
Regards.

possible to add hebrew keyboard?

Could you add Swedish Keyboard?!
Cindly regards MacRoy

bnm7bnm said:
possible to add hebrew keyboard?
Click to expand...
Click to collapse
It is possible partially. Actually it is already done.
Please visit http://www.htcaddicts.com . Don't want to take a credit
for that.
The thing is , that you won't see "Hebrew" in languages list, so the guy
from htcaddicts maps Hebrew to Italian.
That's why one of my cabs is En_It_Ru .

MacRoy said:
Could you add Swedish Keyboard?!
Cindly regards MacRoy
Click to expand...
Click to collapse
Generally - yes.
But I need you to check something in your device first.
Please check if you have these files in your device :
Code:
\Windows\PQwerty0d1d.txt
and
Code:
\Windows\LQwerty0c1d.txt
If you do, then just let me know which languages you want to appear in selection list of HTC Full Qwerty, and I 'll prepare the cab for you.
If you don't have them, then I'll prepare 2 cabs for you:
One with layouts files (I have them in my ROM somehow, probably original HTC files) , like for Russian.
Second cab to set the selectable languages , as for Russian .
If you want to save time and know how to work with WM's registry, I can tell you which key to edit and what data to add.
Regards.

Hello.
I have a spanish HTC Pro but have put an PTG (portuguese) ROM:
My question is, is it possible to change just the physical layout of my keyboard to spanish ?
I'm requesting because the portuguese layout is as the same as english, but all keys added to spanish keyboard are the same as used by portuguese (???).
So i wanted to rehab the keys so i could use whithout loosing T9 or auto-complete in portuguese.
I have already downloaded the HTC Rom Image in spanish and looked in the image for regarding keymapping, i founded the XT9 folder that seems to me to have what i need but dont know where to go from here.
Link Here

NKTA said:
Hello.
I have a spanish HTC Pro but have put an PTG (portuguese) ROM:
My question is, is it possible to change just the physical layout of my keyboard to spanish ?
I'm requesting because the portuguese layout is as the same as english, but all keys added to spanish keyboard are the same as used by portuguese (???).
So i wanted to rehab the keys so i could use whithout loosing T9 or auto-complete in portuguese.
I have already downloaded the HTC Rom Image in spanish and looked in the image for regarding keymapping, i founded the XT9 folder that seems to me to have what i need but dont know where to go from here.
Link Here
Click to expand...
Click to collapse
I did not fully understand your question, but I think you might find the answer here :
http://forum.xda-developers.com/showthread.php?t=426281

NKTA said:
Hello.
I have a spanish HTC Pro but have put an PTG (portuguese) ROM:
My question is, is it possible to change just the physical layout of my keyboard to spanish ?
I'm requesting because the portuguese layout is as the same as english, but all keys added to spanish keyboard are the same as used by portuguese (???).
So i wanted to rehab the keys so i could use whithout loosing T9 or auto-complete in portuguese.
I have already downloaded the HTC Rom Image in spanish and looked in the image for regarding keymapping, i founded the XT9 folder that seems to me to have what i need but dont know where to go from here.
Link Here
Click to expand...
Click to collapse
Ok, I made some quick research , so it might not work but...
In your windows directory, you should have a file named
Code:
eT9.Raphael.XXXX.kmap.txt
where XXXX is a language code. I guess, that in your PTG ROM the XXXX would be 0416 (pt-br) or 0816 (pt) .
So, you should extract that file (XXXX would probably be 040A there) from Spanish ROM, rename it to eT9.Raphael.0416.kmap.txt (or eT9.Raphael.0816.kmap.txt - you should see in your windows dir) and upload it to Windows dir using ActiveSync, or prepare a cab that will copy it there.Then you have to soft reset the device.
Meanwhile I'll do some more research...

f_mulder said:
Ok, I made some quick research , so it might not work but...
In your windows directory, you should have a file named
Code:
eT9.Raphael.XXXX.kmap.txt
where XXXX is a language code. I guess, that in your PTG ROM the XXXX would be 0416 (pt-br) or 0816 (pt) .
So, you should extract that file (XXXX would probably be 040A there) from Spanish ROM, rename it to eT9.Raphael.0416.kmap.txt (or eT9.Raphael.0816.kmap.txt - you should see in your windows dir) and upload it to Windows dir using ActiveSync, or prepare a cab that will copy it there.Then you have to soft reset the device.
Meanwhile I'll do some more research...
Click to expand...
Click to collapse
Thank You for your support f_mulder.
Did find a eT9.Raphael.wwe.kmap
Don't know if its this one, since its wwe, like the mapping at this point for my Physical Keyboard, but in the spanish there's also this file.
I'm a little confused in finding the right file.
Here's what is in the file:
// N O T E: This file must be saved as Unicode
// This file contains the virtual keys mapping table for the
// Raphael device World-Wide English QWERTY layout.
// The mapping table is defined as follows
// VK_TPOUND = 0x78
// VK_TSTAR = 0x77
// VK_TAB = 0x09
// We do not support escape value yet. So the key/char values should be
// entered explicitly or by encoding start with 0x
// Format:
// {VK VK1 VK2 CH1 CH2}
// VK -> value from keyboard driver
// VK1 -> key mapped, interpret by IME
// VK2 -> key to interpret when for press and hold
// CH1 -> symbols produced by Fn + key
// CH2 -> symbols in 123 mode
// CH4 -> Key Index
//{1 1 1 ! ! 0xff}
//{2 2 2 @ @ 0xff}
//{3 3 3 # # 0xff}
//{4 4 4 $ $ 0xff}
//{5 5 5 % % 0xff}
//{6 6 6 ^ ^ 0xff}
//{7 7 7 & & 0xff}
//{8 8 8 * * 0xff}
//{9 9 9 ( ( 0xff}
//{0 0 0 ) ) 0xff}
//{- - - _ _ 0xff}
//{= = = + + 0xff}
{0x09 0x09 0x00 0x00 0x00 0xff} // TAB - 0x09 = VK_TAB
{Q Q Q Q Q 0x00}
{W W W W W 0x01}
{E E E E E 0x02}
{R R R R R 0x03}
{T T T T T 0x04}
{Y Y Y Y Y 0x05}
{U U U U U 0x06}
{I I I I I 0x07}
{O O O O O 0x08}
{P P P P P 0x09}
{0x08 0x08 0x08 0x2E 0x2E 0xff} // BACKSPACE - 0x08 = VK_BACK, 0x2E = VK_DELETE
{0x14 0x14 0x14 0x00 0x00 0xff} // CAPS - 0x14 = VK_CAPITAL
{A A A A A 0x0a}
{S S S S S 0x0b}
{D D D D D 0x0c}
{F F F F F 0x0d}
{G G G G G 0x0e}
{H H H H H 0x0f}
{J J J J J 0x10}
{K K K K K 0x11}
{L L L L L 0x12}
{0xF2 0x0D 0x00 0x00 0x00 0xff} // ENTER - 0x0D = VK_RETURN
{0xA0 0x10 0x10 0x00 0x00 0xff} // SHIFT - 0xA0 = VK_LSHIFT, 0x10 = VK_SHIFT
{Z Z Z Z Z 0x13}
{X X X X X 0x14}
{C C C C C 0x15}
{V V V V V 0x16}
{B B B B B 0x17}
{N N N N N 0x18}
{M M M M M 0x19}
//{/ / / ? ? 0xff}
{0xF1 0x26 0x26 0x21 0x21 0xff} // UP - 0x26 = VK_UP, 0x21 = VK_PRIOR (PAGE UP)
{0xA2 0x11 0x00 0x00 0x00 0xff} // CTRL - 0xA2 = VK_LCONTROL, 0x11 = VK_CONTROL
{0xEC 0xEC 0x00 0x00 0x00 0xff} // FN - 0xEC = FN
{0xEB 0xEB 0x00 0x00 0x00 0xff} // SMS - 0xEB = SMS/T
{0xEF 0xEF 0x00 0x00 0x00 0xff} // MSG - 0xEF = MSG
{0xE6 0xE6 0x00 0x00 0x00 0xff} // SYM - 0xE6
{0xEA 0x12 0x00 0x00 0x00 0xff} // T9 Menu - 0x12
{0x20 0x20 0x20 0x00 0x00 0xff} // SPACE - 0x20 = VK_SPACE
//{, , , ' ' 0xff}
//{. . . " " 0xff}
{0xF5 0x25 0x25 0x00 0x00 0xff} // LEFT - 0x25 = VK_LEFT
{0xF3 0x28 0x28 0x22 0x22 0xff} // DOWN - 0x28 = VK_DOWN, 0x22 = VK_NEXT (PAGE DOWN)
{0xF4 0x27 0x27 0x00 0x00 0xff} // RIGHT - 0x27 = VK_RIGHT
There's a file called eT9DeadKeys.txt which contains:
// This is a unicode text file that contains the dead-key cycling characters.
// Dead-key cycling characters are defined for per language (XT9 Language).
// In each language section, each line defines the cycling characters.
//
// Format:
// c0, c1, c2, c3,..ck, where
// characters on the first column (c0), trigger the dead-cycling
// (c1,...,c3,c1..) when Symb + [first column character] on SP,
// or Fn + Space (PPC) and the current character macthes character
// on the first column.
// German 0x0107
[language = 263]
a ä
A Ä
o ö
O Ö
u ü
U Ü
s ß
S
// French 0x010C
[language = 268]
a à â
A À Â
c ç
C Ç
e è é ê ë
E È É Ê Ë
i î ï
I Î Ï
o ô ö
O Ô
u ù ú û ü
U Ù Û Ü
// Spanish 0x010A
[language = 266]
a á
A Á
e é
E É
i í
I Í
n ñ
N Ñ
o ó
O Ó
u ú
U Ú
// All the language
[language = 65535]
a ä æ å à á â ã
A Ä Æ Å À Á Â Ã
c ç
C Ç
d ð
D Ð
e è é ê ë
E È É Ê Ë
i ì í î ï
I Ì Í Î Ï
n ñ
N Ñ
o ò ó ô õ ö ø
O Ò Ó Ô Õ Ö Ø
u ù ú û ü
U Ù Ú Û Ü
y ý ÿ
Y Ý
s ß
S
I'm guessing that this is what it matters since, as you can see, it has the special keys for "FN" which belong to the spanish keyboard and others. Those letters in spanish are both used by portuguese and spanish, there is no common sense in removing them for portuguese package unless they wanted to spre some change in making a keyboard just for portugal, which its most likely to be since it would be a smaller market than spain.
I have the idea that the t9 its related to physical keyboard and to change, would require to change t9 to spain and then the keyboard would also. Is there any chance or a tool to change the t9 layout and physical keyboard layout independently ? The problem its, that i don't want to change language or either the virtual keyboard. Just the physical one to match the original, it seems that most country's are pretty satisfy in ignoring most of the special keys in the physical keyboard that are provided in their Pro, me in another case want to recover without having to install the original ROM.
This is the WWE physical keyboard which i don't have now, but if i try to write whith the special keys (FN) these are the symbols that shows:
As soon i find a picture of my keyboard i will post it here.
Cheers

NKTA,can you compare both eT9.Raphael.wwe.kmap files?
Are they same?
Can you also check wheather there are additional eT9.* files on both ROMs?

Yes i can, i have both ROM, will extract from portuguese and spanish and check both.
Well, i got them open, side by side, and they are exactly the same. Going to check the et9DeadKeys, exactly the same in both.
By the way, both ROM's are the WM6.1 original form HTC, not tweaked.
I have already removed from the spanish pack, et9 folder, i posted the link earlier. If u want i can remove the same folder from portuguese pack and post it too.
Portuguese Files:
Spanish Files:

Well, if get it right, your eT9.Raphael.wwe.kmap file should have the following settings, in order to respond to the keyboard on picture correctly :
{Q Q Q Q Q 0x00}
{W W W £ £ 0x01}
{E E E € € 0x02}
{R R R R R 0x03}
{T T T T T 0x04}
{Y Y Y Y Y 0x05}
{U U U U U 0x06}
{I I I I I 0x07}
{O O O O O 0x08}
{P P P P P 0x09}
That is for the first row, I won't edit the whole file, but I hope you've got the idea. Note the bold signs.
I checked that, and it works.

f_mulder said:
Well, if get it right, your eT9.Raphael.wwe.kmap file should have the following settings, in order to respond to the keyboard on picture correctly :
{Q Q Q Q Q 0x00}
{W W W £ £ 0x01}
{E E E € € 0x02}
{R R R R R 0x03}
{T T T T T 0x04}
{Y Y Y Y Y 0x05}
{U U U U U 0x06}
{I I I I I 0x07}
{O O O O O 0x08}
{P P P P P 0x09}
That is for the first row, I won't edit the whole file, but I hope you've got the idea. Note the bold signs.
I checked that, and it works.
Click to expand...
Click to collapse
Well, it doesn't.
If u check one of my previous posts the only row with special characters its the first row.
//{1 1 1 ! ! 0xff}
//{2 2 2 @ @ 0xff}
//{3 3 3 # # 0xff}
//{4 4 4 $ $ 0xff}
//{5 5 5 % % 0xff}
//{6 6 6 ^ ^ 0xff}
//{7 7 7 & & 0xff}
//{8 8 8 * * 0xff}
//{9 9 9 ( ( 0xff}
//{0 0 0 ) ) 0xff}
//{- - - _ _ 0xff}
//{= = = + + 0xff}
{0x09 0x09 0x00 0x00 0x00 0xff} // TAB - 0x09 = VK_TAB
{Q Q Q Q Q 0x00}
{W W W W W 0x01}
{E E E E E 0x02}
{R R R R R 0x03}
{T T T T T 0x04}
{Y Y Y Y Y 0x05}
{U U U U U 0x06}
{I I I I I 0x07}
{O O O O O 0x08}
{P P P P P 0x09}
Click to expand...
Click to collapse
The others have no special characters for the exception to the last row (FN / Space / SMS.MMS / IE ...).
{0xF1 0x26 0x26 0x21 0x21 0xff} // UP - 0x26 = VK_UP, 0x21 = VK_PRIOR (PAGE UP)
{0xA2 0x11 0x00 0x00 0x00 0xff} // CTRL - 0xA2 = VK_LCONTROL, 0x11 = VK_CONTROL
{0xEC 0xEC 0x00 0x00 0x00 0xff} // FN - 0xEC = FN
{0xEB 0xEB 0x00 0x00 0x00 0xff} // SMS - 0xEB = SMS/T
{0xEF 0xEF 0x00 0x00 0x00 0xff} // MSG - 0xEF = MSG
{0xE6 0xE6 0x00 0x00 0x00 0xff} // SYM - 0xE6
{0xEA 0x12 0x00 0x00 0x00 0xff} // T9 Menu - 0x12
{0x20 0x20 0x20 0x00 0x00 0xff} // SPACE - 0x20 = VK_SPACE
//{, , , ' ' 0xff}
//{. . . " " 0xff}
{0xF5 0x25 0x25 0x00 0x00 0xff} // LEFT - 0x25 = VK_LEFT
{0xF3 0x28 0x28 0x22 0x22 0xff} // DOWN - 0x28 = VK_DOWN, 0x22 = VK_NEXT (PAGE DOWN)
{0xF4 0x27 0x27 0x00 0x00 0xff} // RIGHT - 0x27 = VK_RIGHT
Click to expand...
Click to collapse
The special characters such as £ and euro coin simbol is not present in Spanish/portuguese files (.txt).
I have an idea, i'm thinking that the repetition of letters like Z Z Z Z are actualy the options available threw normal key and FN+Key.
So therefore if i edit the file like for Q, lets say like this:
{Q £ Í Ú Á 0x00}
In that case, i will obtain Q by pressing the key "Q" on physical keyboard, and £ by pressing one time FN+Q, Í by pressing FN+2xQ (pressing two times Q).
This just might work without having to tweak anything in registry or editing any more files.
It could also be, that the last two that i can change and windows seems to only support 2 letters / 2 symbols by key, so i could do just like first row and edit like this:
//{1 1 1 ! ! 0xff} and exchange to //{1 1 1 £ £ 0xff} so i can use the £ for example as FN+key in 1 key.
There's something bugging me. I can write the £ and euro symbol, but its not present in any of the txt files. So what's mapping the physical keyboard ?

Your file explains it all :
// Format:
// {VK VK1 VK2 CH1 CH2}
// VK -> value from keyboard driver
// VK1 -> key mapped, interpret by IME
// VK2 -> key to interpret when for press and hold
// CH1 -> symbols produced by Fn + key
// CH2 -> symbols in 123 mode
// CH4 -> Key Index
{Q Q Q Q Q 0x00} == {VK VK1 VK2 CH1 CH2}
{W W W W W 0x01}
{E E E E E 0x02}
{R R R R R 0x03}
{T T T T T 0x04}
{Y Y Y Y Y 0x05}
{U U U U U 0x06}
{I I I I I 0x07}
{O O O O O 0x08}
{P P P P P 0x09}
Got it now?

LOL
Yeap got it.
{VK VK1 VK2 CH1 CH2} is indicating the position of each "type of key" pressed.
If i truly want those symbols i will edit the file in the right spot.
So ishould always edit the fourth key, CH1 (symbols produced by Fn + key)
But why isn't £ and euro showing up on this mapping since i can use them ?

As I told, in order to correspond to the keyboard on picture, W should have following settings :
{W W W £ £ 0x01} , which in turn corresponds to the
{VK VK1 VK2 CH1 CH2} structure, which is explained here :
// Format:
// {VK VK1 VK2 CH1 CH2}
// VK -> value from keyboard driver
// VK1 -> key mapped, interpret by IME
// VK2 -> key to interpret when for press and hold
// CH1 -> symbols produced by Fn + key
// CH2 -> symbols in 123 mode
// CH4 -> Key Index
In my Fuze , VK2 doesn't work, it still types same symbol as VK1 does.

NKTA said:
LOL
Yeap got it.
{VK VK1 VK2 CH1 CH2} is indicating the position of each "type of key" pressed.
If i truly want those symbols i will edit the file in the right spot.
Click to expand...
Click to collapse
Great!
Hope I helped

Yes you did help me, and i thank you.
Now thats the problem in this Pro, the physical keyboard layout is english and the files are wwe, which means is english too. But they don't match.
Resuming, i can write with the physical keyboard as equal in the picture. My actual ROM seems to be using the physical keyboard layout for wwe and i want to change it to the spanish one.
The question is, how is it possible to write with the wwe, if the mappings for the wwe (eT9.Raphael.wwe.kmap.txt) seems not to have mapped the £ and euro key.
I see that each key is mapped from left to right, from 1st row until the 5th.
If you check the second row, in the original file (eT9.Raphael.wwe.kmap), £ and euro are missing.

NKTA said:
so i could do just like first row and edit like this:
//{1 1 1 ! ! 0xff} and exchange to //{1 1 1 £ £ 0xff} so i can use the £ for example as FN+key in 1 key.
There's something bugging me. I can write the £ and euro symbol, but its not present in any of the txt files. So what's mapping the physical keyboard ?
Click to expand...
Click to collapse
Keep in mind that "//" sequense means remark - which means that line
beginning with "//" , won't have any effect.
Regarding the mapping of physical keyboard, you should check the registry...
What do you have in the following key :
HKLM\System\CurrentControlSet\Control\Layouts ?

f_mulder said:
Keep in mind that "//" sequense means remark - which means that line
beginning with "//" , won't have any effect.
Regarding the mapping of physical keyboard, you should check the registry...
What do you have in the following key :
HKLM\System\CurrentControlSet\Control\Layouts ?
Click to expand...
Click to collapse
I have several folders:
00000409 ->(inside folder) Layout File + Layout Text + PS2_AT
00000816 -> Layout File + Layout Text + PS2_AT
e0010409 -> Ime File + Keyboard Layout + Layout Text
e0010816 -> Ime File + Keyboard Layout + Layout Text

python help

which of these are correct? several can be correct
it will print out 61 words
1
Code:
j = 0
while j < 61:
s = namn[j]
print(s, end=" ")
j += 1
2
Code:
j = 0
s = ""
while j < 61:
s += namn[j]
j += 1
print(s)
3
Code:
j = 0
s = ""
while j <= 61:
s += namn[j]
j += 1
print(s)
4
Code:
j = 1
while j < 61:
print(namn[j], end=" ")
j += 1
5
Code:
j = 1
s = namn[0]
while j < 61:
s += namn[j]
j += 1
print(s)

[Q] new Google Photos crashes on start

Google photos worked fine until the new google photos (that one announced on Google I/O)
It crashes on start with the following LogCat Output
Code:
06-08 17:22:34.304: A/libc(6280): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 6338 (network)
06-08 17:22:34.994: E/InputDispatcher(556): channel '222e0488 com.google.android.apps.photos/com.google.android.apps.photos.home.HomeActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
06-08 17:22:35.004: E/InputDispatcher(556): channel '2227a0d8 com.google.android.apps.photos/com.google.android.apps.photos.onboarding.IntroActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
06-08 17:22:35.054: E/IMGSRV(797): :0: PVRDRMOpen: TP3, ret = 44
06-08 17:22:35.064: E/IMGSRV(797): :0: PVRDRMOpen: TP3, ret = 45
06-08 17:22:35.074: E/IMGSRV(144): :0: PVRDRMOpen: TP3, ret = 58
06-08 17:22:35.154: E/JavaBinder(556): !!! FAILED BINDER TRANSACTION !!!
06-08 17:22:35.154: E/JavaBinder(556): !!! FAILED BINDER TRANSACTION !!!
06-08 17:22:35.564: E/IMGSRV(144): :0: PVRDRMOpen: TP3, ret = 33
Anyone experiencing the same problems?

leuofiridia said:
Google photos worked fine until the new google photos (that one announced on Google I/O)
It crashes on start with the following LogCat Output
Code:
06-08 17:22:34.304: A/libc(6280): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 6338 (network)
06-08 17:22:34.994: E/InputDispatcher(556): channel '222e0488 com.google.android.apps.photos/com.google.android.apps.photos.home.HomeActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
06-08 17:22:35.004: E/InputDispatcher(556): channel '2227a0d8 com.google.android.apps.photos/com.google.android.apps.photos.onboarding.IntroActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
06-08 17:22:35.054: E/IMGSRV(797): :0: PVRDRMOpen: TP3, ret = 44
06-08 17:22:35.064: E/IMGSRV(797): :0: PVRDRMOpen: TP3, ret = 45
06-08 17:22:35.074: E/IMGSRV(144): :0: PVRDRMOpen: TP3, ret = 58
06-08 17:22:35.154: E/JavaBinder(556): !!! FAILED BINDER TRANSACTION !!!
06-08 17:22:35.154: E/JavaBinder(556): !!! FAILED BINDER TRANSACTION !!!
06-08 17:22:35.564: E/IMGSRV(144): :0: PVRDRMOpen: TP3, ret = 33
Anyone experiencing the same problems?
Click to expand...
Click to collapse
Problem solved with a update launched this week

Phone Stuck in Bootloop After Dead Battery

I gave up and called T-Mobile. They're sending me a replacement next-day air. Should I try to re-lock this one?
So a bit of background. I was running unlocked the latest stock 6.0.1 without root or custom kernels etc.
Last night I noticed my battery indicator was orange but my phone never entered battery saver. Went into battery saver to turn it back on; the toggle didn't work. I figure that's weird, but a reboot should fix it. I attempt reboot my device. It has been stuck in a bootloop since (at the dots animation). After giving up on it, I left it to charge overnight off (just incase it was some weird low battery thing). Try again this morning and still no luck.
Troubleshooting
Booted into stock recovery; wiped cache. No luck.
I snagged the latest images from Google and flashed boot and system. No luck.
I booted into stock recovery; wiped cache. No luck.
Downloaded TWRP and used the 'boot' command to boot into it without flashing. Used that to backup the contents of my internal storage.
Booted back into stock recovery. Did a factory rest and wiped cache. No luck.
I flashed the full image (radio, bootloader, boot, system, userdata, cache, recovery). No Luck.
Booted into stock recovery; wiped cache. No luck.
Booted into stock recovery. Did a factory rest and wiped cache. No luck.
I flashed the full image (radio, bootloader, boot, system, userdata, cache, recovery)(thinking maybe I missed an image last time). No Luck.
edit2:
Fastboot erased userdata and cache. No luck.
edit3:
Fastboot formatted userdata and cache. No luck.
Booted into stock recovery. Did a factory rest and wiped cache. (figured that might initialize the partitions if they were left blank)No luck.
Used the 'boot' command to boot into TWRP without flashing. Wiped /data, /cache, and dalvik cache in TWRP No luck.
I always gave it at least 5 minutes (once as long as 40 minutes) of booting before moving on to the next step. As you can see, I'm long past trying to preserve anything, I just want a useable phone again.
Edit: also weird. I can only turn the phone off via bootloader > power off. Holding the power button always causes a reboot instead of a power off.

Wait a minute... nobody's answered this?? I'm stuck in the EXACT SAME situation. The N6 was running a ROM AOK forever and once I tried powering it on after allowing it to completely drain its battery... NO LUCK
Were you able to get your unit working again? Does anyone have any idea outside what's in the OP?

skielbasa said:
I gave up and called T-Mobile. They're sending me a replacement next-day air. Should I try to re-lock this one?
So a bit of background. I was running unlocked the latest stock 6.0.1 without root or custom kernels etc.
Last night I noticed my battery indicator was orange but my phone never entered battery saver. Went into battery saver to turn it back on; the toggle didn't work. I figure that's weird, but a reboot should fix it. I attempt reboot my device. It has been stuck in a bootloop since (at the dots animation). After giving up on it, I left it to charge overnight off (just incase it was some weird low battery thing). Try again this morning and still no luck.
Troubleshooting
Booted into stock recovery; wiped cache. No luck.
I booted into stock recovery; wiped cache. No luck.
I flashed the full image (radio, bootloader, boot, system, userdata, cache, recovery). No Luck.
Booted into stock recovery. Did a factory rest and wiped cache. No luck.
Fastboot erased userdata and cache. No luck.
edit3:
Booted into stock recovery. Did a factory rest and wiped cache. (figured that might initialize the partitions if they were left blank)No luck.
Used the 'boot' command to boot into TWRP without flashing. Wiped /data, /cache, and dalvik cache in TWRP No luck.
I always gave it at least 5 minutes (once as long as 40 minutes) of booting before moving on to the next step. As you can see, I'm long past trying to preserve anything, I just want a useable phone again.
Edit: also weird. I can only turn the phone off via bootloader > power off. Holding the power button always causes a reboot instead of a power off.
Click to expand...
Click to collapse
Did you flash all partitions separately and erase command and then format? Are you using an official Nexus 6 cable?

biggiesmalls657 said:
Did you flash all partitions separately and erase command and then format? Are you using an official Nexus 6 cable?
Click to expand...
Click to collapse
lol, thats a question from 3 moths ago.. i highly doubt that they are waiting on an answer :angel:

simms22 said:
lol, thats a question from 3 moths ago.. i highly doubt that they are waiting on an answer :angel:
Click to expand...
Click to collapse
I didn't read the timestamp but maybe its lying around somewhere.

From SELinux Denials to Sensor Failure
biggiesmalls657 said:
Did you flash all partitions separately and erase command and then format? Are you using an official Nexus 6 cable?
Click to expand...
Click to collapse
I've flash each partition individually with 71.18 BL Stock & 71.21 BL N Preview Stock to no avail.
Mixing 71.18 & 71.21 Roms brought about a SeLinux issue but that was solved by getting the BLs and their appropriate Roms right.
Now I'm running into an odd sensor failure in my LogCat that I can't get around:
Code:
--------- beginning of main
02-09 20:45:15.323 245 245 W auditd : type=2000 audit(0.0:1): initialized
02-09 20:45:17.385 252 252 I /system/bin/tzdatacheck: tzdata file /data/misc/zoneinfo/current/tzdata does not exist. No action required.
--------- beginning of system
02-09 20:45:17.396 246 246 I vold : Vold 3.0 (the awakening) firing up
02-09 20:45:17.396 246 246 V vold : Detected support for: exfat ext4 f2fs ntfs vfat
02-09 20:45:18.099 279 279 D QSEECOMD: : qseecom listener services process entry PPID = 1
02-09 20:45:18.099 279 279 E QSEECOMD: : Listener: index = 0, hierarchy = 0
02-09 20:45:18.099 277 277 I mdm_helper: 1 supported modem(s) found
02-09 20:45:18.099 277 277 I mdm_helper: Setting up mdm helper device structure
02-09 20:45:18.099 277 277 I mdm_helper: Found private data for MDM9x25
02-09 20:45:18.099 277 277 I mdm_helper: ESOC Details:
02-09 20:45:18.099 277 277 I mdm_helper: Name:MDM9x25
02-09 20:45:18.099 277 277 I mdm_helper: Port:/dev/esoc-0
02-09 20:45:18.099 277 277 I mdm_helper: Link:HSIC
02-09 20:45:18.099 277 277 I mdm_helper: Device configuration loaded
02-09 20:45:18.099 277 277 I mdm_helper: Starting MDM helper
02-09 20:45:18.099 277 277 I mdm_helper: Creating thread for MDM9x25
02-09 20:45:18.099 277 280 I mdm_helper: Starting MDM9x25
02-09 20:45:18.099 277 280 I mdm_helper: MDM9x25 : switching state to POWERUP
02-09 20:45:18.100 277 280 I mdm_helper: MDM9x25: Initializing environment
02-09 20:45:18.100 279 279 D QSEECOMD: : Init dlopen(librpmb.so, RTLD_NOW) succeeds
02-09 20:45:18.100 279 279 D QSEECOMD: : Init::Init dlsym(g_FSHandle rpmb_init_service) succeeds
02-09 20:45:18.100 279 279 I rpmb : RPMB Mult = 16384, Rel_sec_cnt = 1
02-09 20:45:18.100 279 279 E DrmLibRpmb: rpmb_init succeeded! with ret = 0
02-09 20:45:18.101 279 279 D QSEECOMD: : Init rpmb_init_service ret = 0
02-09 20:45:18.101 279 279 D QSEECOMD: : RPMB system services: init (Listener ID = 8192)
02-09 20:45:18.101 279 279 E QSEECOMD: : Listener: index = 1, hierarchy = 0
02-09 20:45:18.101 279 279 D QSEECOMD: : Init dlopen(libssd.so, RTLD_NOW) succeeds
02-09 20:45:18.101 279 279 D QSEECOMD: : Init::Init dlsym(g_FSHandle ssd_init_service) succeeds
02-09 20:45:18.101 279 279 E SSD : ssd_init_service succeeded!
02-09 20:45:18.101 279 279 D QSEECOMD: : Init ssd_init_service ret = 0
02-09 20:45:18.101 279 279 D QSEECOMD: : SSD system services: init (Listener ID = 12288)
02-09 20:45:18.102 279 279 D QSEECOMAPI: : QSEECom_get_handle sb_length = 0x400
02-09 20:45:18.102 279 279 D QSEECOMAPI: : App is not loaded in QSEE
02-09 20:45:18.107 274 274 I lowmemorykiller: Using in-kernel low memory killer interface
02-09 20:45:18.122 278 291 E Sensors : sns_fsa_la.c(78):realpath failed for directory name2
02-09 20:45:18.123 278 291 E Sensors : sns_reg_la.c(289):Error creating registry file
02-09 20:45:18.123 278 291 W Sensors : sns_reg_mr.c(370):File init failed 5
02-09 20:45:18.136 276 276 I SurfaceFlinger: SurfaceFlinger is starting
02-09 20:45:18.136 276 276 I SurfaceFlinger: SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
02-09 20:45:18.143 276 276 D libEGL : loaded /vendor/lib/egl/libEGL_adreno.so
02-09 20:45:18.176 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:18.176 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:18.252 276 276 D libEGL : loaded /vendor/lib/egl/libGLESv1_CM_adreno.so
02-09 20:45:18.260 276 276 D libEGL : loaded /vendor/lib/egl/libGLESv2_adreno.so
02-09 20:45:18.277 276 276 I Adreno : QUALCOMM build : 52af4d2, I8366cd0437
02-09 20:45:18.277 276 276 I Adreno : Build Date : 10/20/15
02-09 20:45:18.277 276 276 I Adreno : OpenGL ES Shader Compiler Version: XE031.05.13.02
02-09 20:45:18.277 276 276 I Adreno : Local Branch : M14
02-09 20:45:18.277 276 276 I Adreno : Remote Branch :
02-09 20:45:18.277 276 276 I Adreno : Remote Branch :
02-09 20:45:18.277 276 276 I Adreno : Reconstruct Branch :
02-09 20:45:18.584 279 279 D QSEECOMAPI: : Loaded image: APP id = 2
02-09 20:45:18.586 279 279 D QSEECOMD: : Parent qseecom daemon process paused!!
02-09 20:45:18.587 331 331 D QSEECOMD: : qseecom listener service threads starting!!!
02-09 20:45:18.587 331 331 D QSEECOMD: : Total listener services to start = 5
02-09 20:45:18.587 331 331 E QSEECOMD: : Listener: index = 0, hierarchy = 1
02-09 20:45:18.587 331 331 D QSEECOMD: : Init dlopen(librpmb.so, RTLD_NOW) succeeds
02-09 20:45:18.587 331 331 D QSEECOMD: : Init::Init dlsym(g_FSHandle rpmb_start) succeeds
02-09 20:45:18.587 331 331 D QSEECOMAPI: : QSEECom_register_listener 8192 sb_length = 0x5000
02-09 20:45:18.591 331 331 D QSEECOMD: : Init rpmb_start ret = 0
02-09 20:45:18.591 331 331 D QSEECOMD: : RPMB system services: Started (Listener ID = 8192)
02-09 20:45:18.591 331 331 E QSEECOMD: : Listener: index = 1, hierarchy = 1
02-09 20:45:18.591 331 331 D QSEECOMD: : Init dlopen(libssd.so, RTLD_NOW) succeeds
02-09 20:45:18.591 331 331 D QSEECOMD: : Init::Init dlsym(g_FSHandle ssd_start) succeeds
02-09 20:45:18.591 331 331 D QSEECOMAPI: : QSEECom_register_listener 12288 sb_length = 0x5000
02-09 20:45:18.592 331 331 D QSEECOMD: : Init ssd_start ret = 0
02-09 20:45:18.592 331 331 D QSEECOMD: : SSD system services: Started (Listener ID = 12288)
02-09 20:45:18.592 331 331 E QSEECOMD: : Listener: index = 2, hierarchy = 1
02-09 20:45:18.593 331 331 E QSEECOMD: : Init dlopen(libsecureui.so, RLTD_NOW) is failed....
02-09 20:45:18.593 331 331 E QSEECOMD: : Listener: index = 3, hierarchy = 1
02-09 20:45:18.599 331 331 D QSEECOMD: : Init dlopen(libdrmtime.so, RTLD_NOW) succeeds
02-09 20:45:18.599 331 331 D QSEECOMD: : Init::Init dlsym(g_FSHandle atime_start) succeeds
02-09 20:45:18.599 331 331 D DrmLibTime: QSEE Time Listener: atime_start
02-09 20:45:18.599 331 331 D QSEECOMAPI: : QSEECom_register_listener 11 sb_length = 0x5000
02-09 20:45:18.600 331 331 D DrmLibTime: registering fs service to QSEECom is done!
02-09 20:45:18.600 331 331 D DrmLibTime: begin to create a thread!
02-09 20:45:18.600 331 331 D DrmLibTime: Creating a pthread in atime_start is done! return 0
02-09 20:45:18.600 331 331 D QSEECOMD: : Init atime_start ret = 0
02-09 20:45:18.600 331 338 D DrmLibTime: QSEE Time Listener: dispatch
02-09 20:45:18.600 331 331 D QSEECOMD: : time services: Started (Listener ID = 11)
02-09 20:45:18.600 331 338 D DrmLibTime: before calling ioctl to read the next time_cmd
02-09 20:45:18.600 331 331 E QSEECOMD: : Listener: index = 4, hierarchy = 1
02-09 20:45:18.600 331 331 D QSEECOMD: : Init dlopen(libdrmfs.so, RTLD_NOW) succeeds
02-09 20:45:18.600 331 331 D QSEECOMD: : Init::Init dlsym(g_FSHandle fs_start) succeeds
02-09 20:45:18.600 331 331 D QSEECOMAPI: : QSEECom_register_listener 10 sb_length = 0x5000
02-09 20:45:18.601 331 331 D QSEECOMD: : Init fs_start ret = 0
02-09 20:45:18.601 331 331 D QSEECOMD: : file system services: Started (Listener ID = 10)
02-09 20:45:18.601 331 331 D QSEECOMD: : QSEECOM DAEMON RUNNING
02-09 20:45:18.711 276 276 I qdutils : PartialUpdate status: Enabled
02-09 20:45:18.711 276 276 I qdutils : Left Align: 8
02-09 20:45:18.712 276 276 I qdutils : Width Align: 8
02-09 20:45:18.712 276 276 I qdutils : Top Align: 1
02-09 20:45:18.712 276 276 I qdutils : Height Align: 1
02-09 20:45:18.712 276 276 I qdutils : Min ROI Width: 8
02-09 20:45:18.712 276 276 I qdutils : Min ROI Height: 1
02-09 20:45:18.712 276 276 I qdutils : Needs ROI Merge: 1
02-09 20:45:18.712 276 276 I qdutils : Left Split=720
02-09 20:45:18.712 276 276 I qdutils : Right Split=720
02-09 20:45:18.715 276 276 I qdhwcomposer: Initializing Qualcomm Hardware Composer
02-09 20:45:18.715 276 276 I qdhwcomposer: MDP version: 500
02-09 20:45:18.715 276 276 I SurfaceFlinger: Using composer version 1.5
02-09 20:45:18.715 276 276 I qdhwcomposer: hwc_registerProcs
02-09 20:45:18.715 276 276 I qdhwcomposer: Initializing UEVENT Thread
02-09 20:45:18.715 276 276 I qdhwcomposer: Initializing VSYNC Thread
02-09 20:45:18.716 276 342 I qdhwcomposer: vsync_loop: Reading event 0 for dpy 0 from /sys/class/graphics/fb0/vsync_event
02-09 20:45:18.716 276 276 D qdhwcomposer: hwc_getDisplayAttributes disp = 0, width = 1440
02-09 20:45:18.716 276 276 D qdhwcomposer: hwc_getDisplayAttributes disp = 0, height = 2560
02-09 20:45:18.717 276 276 I SurfaceFlinger: EGL information:
02-09 20:45:18.717 276 276 I SurfaceFlinger: vendor : Android
02-09 20:45:18.717 276 276 I SurfaceFlinger: version : 1.4 Android META-EGL
02-09 20:45:18.717 276 276 I SurfaceFlinger: extensions: EGL_KHR_get_all_proc_addresses EGL_ANDROID_presentation_time EGL_KHR_swap_buffers_with_damage EGL_KHR_image EGL_KHR_image_base EGL_KHR_lock_surface EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_3D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_KHR_reusable_sync EGL_KHR_fence_sync EGL_KHR_create_context EGL_KHR_surfaceless_context EGL_EXT_create_context_robustness EGL_ANDROID_image_native_buffer EGL_KHR_wait_sync EGL_ANDROID_recordable EGL_KHR_create_context_no_error
02-09 20:45:18.717 276 276 I SurfaceFlinger: Client API: OpenGL_ES
02-09 20:45:18.717 276 276 I SurfaceFlinger: EGLSurface: 8-8-8-8, config=0xb6a86978
02-09 20:45:18.718 276 342 I qdhwcomposer: vsync_loop: Reading event 1 for dpy 0 from /sys/class/graphics/fb0/show_blank_event
02-09 20:45:18.719 276 342 I qdhwcomposer: vsync_loop: Reading event 2 for dpy 0 from /sys/class/graphics/fb0/cec/rd_msg
02-09 20:45:18.721 276 342 E qdhwcomposer: vsync_loop:unable to open event node for dpy=0 event=2, No such file or directory
02-09 20:45:18.722 276 342 I qdhwcomposer: vsync_loop: Reading event 0 for dpy 1 from /sys/class/graphics/fb-1/vsync_event
02-09 20:45:18.722 276 342 I qdhwcomposer: vsync_loop: Reading event 1 for dpy 1 from /sys/class/graphics/fb-1/show_blank_event
02-09 20:45:18.723 276 342 I qdhwcomposer: vsync_loop: Reading event 2 for dpy 1 from /sys/class/graphics/fb-1/cec/rd_msg
02-09 20:45:18.726 276 276 I SurfaceFlinger: OpenGL ES informations:
02-09 20:45:18.726 276 276 I SurfaceFlinger: vendor : Qualcomm
02-09 20:45:18.726 276 276 I SurfaceFlinger: renderer : Adreno (TM) 420
02-09 20:45:18.726 276 276 I SurfaceFlinger: version : OpenGL ES 3.1 [email protected] ([email protected])
02-09 20:45:18.726 276 276 I SurfaceFlinger: extensions: GL_OES_EGL_image GL_OES_EGL_image_external GL_OES_EGL_sync GL_OES_vertex_half_float GL_OES_framebuffer_object GL_OES_rgb8_rgba8 GL_OES_compressed_ETC1_RGB8_texture GL_AMD_compressed_ATC_texture GL_KHR_texture_compression_astc_ldr GL_OES_texture_npot GL_EXT_texture_filter_anisotropic GL_EXT_texture_format_BGRA8888 GL_OES_texture_3D GL_EXT_color_buffer_float GL_EXT_color_buffer_half_float GL_QCOM_alpha_test GL_OES_depth24 GL_OES_packed_depth_stencil GL_OES_depth_texture GL_OES_depth_texture_cube_map GL_EXT_sRGB GL_OES_texture_float GL_OES_texture_float_linear GL_OES_texture_half_float GL_OES_texture_half_float_linear GL_EXT_texture_type_2_10_10_10_REV GL_EXT_texture_sRGB_decode GL_OES_element_index_uint GL_EXT_copy_image GL_EXT_geometry_shader GL_EXT_tessellation_shader GL_OES_texture_stencil8 GL_EXT_shader_io_blocks GL_OES_shader_image_atomic GL_OES_sample_variables GL_EXT_texture_border_clamp GL_EXT_multisampled_render_to_texture GL_OES_shader_multisample_interpolation GL_EXT_texture_cube_map_arr
02-09 20:45:18.726 276 276 I SurfaceFlinger: GL_MAX_TEXTURE_SIZE = 16384
02-09 20:45:18.726 276 276 I SurfaceFlinger: GL_MAX_VIEWPORT_DIMS = 16384
02-09 20:45:18.730 276 276 D SurfaceFlinger: Set power mode=2, type=0 flinger=0xb6aa4000
02-09 20:45:18.730 276 276 D qdhwcomposer: hwc_setPowerMode: Setting mode 2 on display: 0
02-09 20:45:18.730 276 276 D qdhwcomposer: hwc_setPowerMode: Done setting mode 2 on display 0
02-09 20:45:18.730 276 342 I qdhwcomposer: handle_blank_event: dpy:0 panel power state: 1
02-09 20:45:18.841 344 346 D libEGL : loaded /vendor/lib/egl/libEGL_adreno.so
02-09 20:45:18.888 344 346 D libEGL : loaded /vendor/lib/egl/libGLESv1_CM_adreno.so
02-09 20:45:18.896 344 346 D libEGL : loaded /vendor/lib/egl/libGLESv2_adreno.so
02-09 20:45:18.907 344 346 I Adreno : QUALCOMM build : 52af4d2, I8366cd0437
02-09 20:45:18.907 344 346 I Adreno : Build Date : 10/20/15
02-09 20:45:18.907 344 346 I Adreno : OpenGL ES Shader Compiler Version: XE031.05.13.02
02-09 20:45:18.907 344 346 I Adreno : Local Branch : M14
02-09 20:45:18.907 344 346 I Adreno : Remote Branch :
02-09 20:45:18.907 344 346 I Adreno : Remote Branch :
02-09 20:45:18.907 344 346 I Adreno : Reconstruct Branch :
02-09 20:45:18.923 344 346 E BootAnimation: couldn't find audio_conf.txt
02-09 20:45:19.617 276 276 D SurfaceFlinger: shader cache generated - 24 shaders in 267.772125 ms
02-09 20:45:19.637 276 276 D qdutils : DEBUG_CALC_FPS: 0
02-09 20:45:19.637 276 276 D qdutils : period: 10
02-09 20:45:19.637 276 276 D qdutils : ignorethresh_us: 500000
03-21 17:30:31.580 245 245 I auditd : type=1403 audit(0.0:2): policy loaded auid=4294967295 ses=4294967295
03-21 17:30:31.580 245 245 W auditd : type=1404 audit(0.0:3): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295
02-09 20:45:28.065 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:28.066 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:28.069 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:28.069 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:28.071 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:28.071 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:28.074 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:28.074 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:28.076 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:28.077 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:28.078 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:28.078 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:28.079 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:28.080 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:28.081 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:28.081 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:28.082 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:28.082 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:28.083 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:28.083 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:28.085 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:28.085 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:28.087 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:28.087 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:28.089 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:28.089 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:28.090 278 291 E Sensors : sns_reg.c(255):Invalid ID: 3040
02-09 20:45:28.091 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:28.091 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:28.093 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:28.093 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:28.094 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:28.094 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:28.096 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:28.096 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:28.097 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:28.097 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:28.098 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:28.098 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:28.099 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:28.099 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:38.108 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:38.108 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:38.109 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:38.109 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:38.111 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:38.111 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:38.111 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:38.111 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:38.111 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:38.111 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5

KLBrey said:
I've flash each partition individually with 71.18 BL Stock & 71.21 BL N Preview Stock to no avail.
Mixing 71.18 & 71.21 Roms brought about a SeLinux issue but that was solved by getting the BLs and their appropriate Roms right.
Now I'm running into an odd sensor failure in my LogCat that I can't get around:
Click to expand...
Click to collapse
Hardware. Are you using an official fastboot cable? Did you flash the binaries of the sensor drivers?

Can My Poor N6 Bounce-Back from Seeming Complete Sensor Failure??
biggiesmalls657 said:
Hardware. Are you using an official fastboot cable? Did you flash the binaries of the sensor drivers?
Click to expand...
Click to collapse
Since you're the 2nd to mention USB cable quality, I'll address that:
I have my OEM Turbo Charger and I'm sure I still have the OEM Cable that came with it, but I'm currently using an Amazon Basic Branded 5ft replacement to one my cat devoured. Since it seems that Cable Matters, I'll wrangle the one's I have with me when the Sun's is up.
The Immediate Worse Case S:
I'll have to wait until I return home Monday if none of the cables with me are The One*.
Flash Binaries of Sensor Drivers:
whaaa
[* thanks Moto, one more Must Match in my life]

[SOLVED] Bootloop with Major Sensor Failure
After looking into physical things like cable quality and low-level drivers provided to ROM bakers (neither were my particulate issue), I pieced together a diagnosis and resolution that worked for me:
Validating my /persist partition OR Creating a new ext4 one if it's currupt​I dropped to TWRP v3 recovery, opened an ADB Shell and checked which partitions were automatically mounted. Alas, /persist wasn't there... it was gone, baby, gone! So I tried to recover it using
Code:
e2fsck /dev/block/platform/msm_sdcc.1/by-name/persist
Which resulted in a Bad Superblock with no backups. Using an alternate Superblock (ie. e2fsck -b 8197) also failed. So I crossed fingers that my N6 retained specs about how /persist should be and created a fresh ext4 version
Code:
make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/persist
That solved (nearly) everything. I was able to watch live logcat as my N6 successfully booted into 6.0.1 MM again. Everything seems AOK so far, but it's late and I'm about to crash. When the Sun's up again, I'll test it and post once more.

[ROM][UNOFFICIAL-ABANDONED][11] LineageOS 18.1 for Samsung Galaxy S5 (klte*)

{
"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