I currently use Swiftkey, but really would love to use the stock Samsung keyboard mainly because of the numbers above the letter keys. The only reason I am sticking with Swiftkey is because you can change the long-press duration for selecting special charactors/punctuations - if I stuck with the samsung keyboard it would slow me down greatly and annoy the crap out of me because the long-press take so long.
Is there anyway to change the long-press duration? Any files you can edit to affect it? or something?
Thanks!
ItsTommyGun said:
I currently use Swiftkey, but really would love to use the stock Samsung keyboard mainly because of the numbers above the letter keys. The only reason I am sticking with Swiftkey is because you can change the long-press duration for selecting special charactors/punctuations - if I stuck with the samsung keyboard it would slow me down greatly and annoy the crap out of me because the long-press take so long.
Is there anyway to change the long-press duration? Any files you can edit to affect it? or something?
Thanks!
Click to expand...
Click to collapse
Yes, there is:
1. To change the long press delay
In PointerTracker:
Code:
###################################################
# Change the long press delay to 200ms from 500ms #
###################################################
.line 498
const/16 v0, 0xc8
.line 499
.local v0, delay:I
packed-switch p1, switch_data_0
.line 504
const/16 v0, 0xc8
.line 507
:goto_0
int-to-long v1, v0
return-wide v1
.line 501
switch_0
const/16 v0, 0xc8
Check out this thread for more info: http://forum.xda-developers.com/showthread.php?t=2093588
unkellsam said:
Yes, there is:
1. To change the long press delay
In PointerTracker:
Code:
###################################################
# Change the long press delay to 200ms from 500ms #
###################################################
.line 498
const/16 v0, 0xc8
.line 499
.local v0, delay:I
packed-switch p1, switch_data_0
.line 504
const/16 v0, 0xc8
.line 507
:goto_0
int-to-long v1, v0
return-wide v1
.line 501
switch_0
const/16 v0, 0xc8
Check out this thread for more info: http://forum.xda-developers.com/showthread.php?t=2093588
Click to expand...
Click to collapse
I can't find anywhere Pointertracker to edit it. I even copied the .apk onto my computer and browsed it. Am I missing it??
I'm also a little worried about installing the apk listed since it's for a different device.
Do you know the location of PointerTracker?
Related
Trying to figure out how to make a shortcut to settings. When you browse to the settings folder in file explorer and open it it's empty. I don't want to open individual .cpl's I would like to emulate what happens when you hit "settings" on the start menu and open the settings window. Thanks.
juiceppc said:
Trying to figure out how to make a shortcut to settings. When you browse to the settings folder in file explorer and open it it's empty. I don't want to open individual .cpl's I would like to emulate what happens when you hit "settings" on the start menu and open the settings window. Thanks.
Click to expand...
Click to collapse
i have been searching for this too, but i didnt find it
i dont know if its possibe
Done it but not certain how!
I have done this before - using VJKeypress you can simulate a keypress in a shortcut which takes you straight to Settings. I can't remember which it was (probably ctl+alt+something lol) but it did work.
Dig around and you'll have it working soon.
littld said:
I have done this before - using VJKeypress you can simulate a keypress in a shortcut which takes you straight to Settings. I can't remember which it was (probably ctl+alt+something lol) but it did work.
Dig around and you'll have it working soon.
Click to expand...
Click to collapse
Here's the keycode list. Any of these ring a bell?
VK_LBUTTON 1
VK_RBUTTON 2
VK_CANCEL 3
VK_MBUTTON 4
VK_XBUTTON1 5
VK_XBUTTON2 6
VK_BACK 8
VK_TAB 9
VK_CLEAR 12
VK_RETURN 13
VK_SHIFT 16
VK_CONTROL 17
VK_CTRL 17
VK_MENU 18
VK_PAUSE 19
VK_CAPITAL 20
VK_HANGEUL 21
VK_HANGUL 21
VK_KANA 21
VK_JUNJA 23
VK_FINAL 24
VK_HANJA 25
VK_KANJI 25
VK_ESCAPE 27
VK_CONVERT 28
VK_NONCONVERT 29
VK_ACCEPT 30
VK_MODECHANGE 31
VK_SPACE 32
VK_PRIOR 33
VK_NEXT 34
VK_END 35
VK_HOME 36
VK_LEFT 37
VK_UP 38
VK_RIGHT 39
VK_DOWN 40
VK_SELECT 41
VK_PRINT 42
VK_EXECUTE 43
VK_SNAPSHOT 44
VK_INSERT 45
VK_DELETE 46
VK_HELP 47
VK_0 48
VK_1 49
VK_2 50
VK_3 51
VK_4 52
VK_5 53
VK_6 54
VK_7 55
VK_8 56
VK_9 57
VK_A 65
VK_B 66
VK_C 67
VK_D 68
VK_E 69
VK_F 70
VK_G 71
VK_H 72
VK_I 73
VK_J 74
VK_K 75
VK_L 76
VK_M 77
VK_N 78
VK_O 79
VK_P 80
VK_Q 81
VK_R 82
VK_S 83
VK_T 84
VK_U 85
VK_V 86
VK_W 87
VK_X 88
VK_Y 89
VK_Z 90
VK_LWIN 91
VK_RWIN 92
VK_APPS 93
VK_SLEEP 95
VK_NUMPAD0 96
VK_NUMPAD1 97
VK_NUMPAD2 98
VK_NUMPAD3 99
VK_NUMPAD4 100
VK_NUMPAD5 101
VK_NUMPAD6 102
VK_NUMPAD7 103
VK_NUMPAD8 104
VK_NUMPAD9 105
VK_MULTIPLY 106
VK_ADD 107
VK_SEPARATOR 108
VK_SUBTRACT 109
VK_DECIMAL 110
VK_DIVIDE 111
VK_F1 112
VK_F2 113
VK_F3 (green key) 114
VK_F4 115
VK_F5 116
VK_F6 117
VK_F7 118
VK_F8 119
VK_F9 120
VK_F10 121
VK_F11 122
VK_F12 123
VK_F13 124
VK_F14 125
VK_F15 126
VK_F16 127
VK_F17 128
VK_F18 129
VK_F19 130
VK_F20 131
VK_F21 132
VK_F22 133
VK_F23 134
VK_F24 135
VK_NUMLOCK 144
VK_SCROLL 145
VK_OEM_FJ_JISHO 146
VK_OEM_NEC_EQUAL 146
VK_OEM_FJ_MASSHOU 147
VK_OEM_FJ_TOUROKU 148
VK_OEM_FJ_LOYA 149
VK_OEM_FJ_ROYA 150
VK_LSHIFT 160
VK_RSHIFT 161
VK_LCONTROL 162
VK_RCONTROL 163
VK_LMENU 164
VK_RMENU 165
VK_BROWSER_BACK 166
VK_BROWSER_FORWARD 167
VK_BROWSER_REFRESH 168
VK_BROWSER_STOP 169
VK_BROWSER_SEARCH 170
VK_BROWSER_FAVORITES 171
VK_BROWSER_HOME 172
VK_VOLUME_MUTE 173
VK_VOLUME_DOWN 174
VK_VOLUME_UP 175
VK_MEDIA_NEXT_TRACK 176
VK_MEDIA_PREV_TRACK 177
VK_MEDIA_STOP 178
VK_MEDIA_PLAY_PAUSE 179
VK_LAUNCH_MAIL 180
VK_LAUNCH_MEDIA_SELECT 181
VK_LAUNCH_APP1 182
VK_LAUNCH_APP2 183
VK_OEM_1 186
VK_OEM_PLUS 187
VK_OEM_COMMA 188
VK_OEM_MINUS 189
VK_OEM_PERIOD 190
VK_OEM_2 191
VK_OEM_3 192
VK_OEM_4 219
VK_OEM_5 220
VK_OEM_6 221
VK_OEM_7 222
VK_OFF (power off) 223
VK_OEM_AX 225
VK_OEM_102 226
VK_ICO_HELP 227
VK_ICO_00 228
VK_PROCESSKEY 229
VK_ICO_CLEAR 230
VK_PACKET 231
VK_OEM_RESET 233
VK_OEM_JUMP 234
VK_OEM_PA1 235
VK_OEM_PA2 236
VK_OEM_PA3 237
VK_OEM_WSCTRL 238
VK_OEM_CUSEL 239
VK_DBE_ALPHANUMERIC 240
VK_OEM_ATTN 240
VK_DBE_KATAKANA 241
VK_OEM_FINISH 241
VK_DBE_HIRAGANA 242
VK_OEM_COPY 242
VK_DBE_SBCSCHAR 243
VK_OEM_AUTO 243
VK_DBE_DBCSCHAR 244
VK_OEM_ENLW 244
VK_DBE_ROMAN 245
VK_OEM_BACKTAB 245
VK_ATTN 246
VK_DBE_NOROMAN 246
VK_CRSEL 247
VK_DBE_ENTERWORDREGISTERMODE 247
VK_DBE_ENTERIMECONFIGMODE 248
VK_EXSEL 248
VK_DBE_FLUSHSTRING 249
VK_EREOF 249
VK_DBE_CODEINPUT 250
VK_PLAY 250
VK_DBE_NOCODEINPUT 251
VK_ZOOM 251
VK_DBE_DETERMINESTRING 252
VK_NONAME 252
VK_DBE_ENTERDLGCONVERSIONMODE 253
VK_PA1 253
VK_OEM_CLEAR 254
littld said:
I have done this before - using VJKeypress you can simulate a keypress in a shortcut which takes you straight to Settings. I can't remember which it was (probably ctl+alt+something lol) but it did work.
Dig around and you'll have it working soon.
Click to expand...
Click to collapse
I tried this software but only the follo no. worked
223 Power Off
27 Escape
91 Start Menu
93 Context Menu
112 Left Soft Key
113 Right Soft Key
133 Device Lock (WM5 only)
I was looking also to get setting & Program menu shortcuts
Can some one help.
I looked
I looked at the list but can't remember which - I think I'd set up a macro and incremented by one each time with the number to see what they all did. It's a long time ago!
I do know for a fact that there is a keyboard shortcut to the Settings window and it works perfectly.
Bad news - there is no such way to get to the Programs screen. I did write a little app which could call it (thought the Start menu) but I can't find it.
Good luck.
maybe here are what you are looking for.................
medkid said:
maybe here are what you are looking for.................
Click to expand...
Click to collapse
Thankyou medkid
Anyone can help me with VJKeypress
I want to use FtouchFlo from Efrost to emulate keypress (from D-pad) right and left.
check here :
http://www.xs4all.nl/~itsme/projects/xda/xda-controlpanel.html
sudist said:
Anyone can help me with VJKeypress
I want to use FtouchFlo from Efrost to emulate keypress (from D-pad) right and left.
Click to expand...
Click to collapse
I PM Vj but no reply yet.
Thanks u guys 4 ur help,
I still do not know how to shortcut 2 Program & setting menu
ie Start - Program
Or Start - Setting
This needed 4 FtouchFlo 2 gesture from left to right - right to left.
I was looking for this for ages with no luck.
Recently installed Wisbar Advance 3, was playing about with linking up my desktop icons and found that it can be done...
hold tap on an icon, properties, set path to executable as:
\Program Files\Lakeridge\Wisbar Advance 3\Control.exe
this will bring up the Settings page as normal.
(another tip- in the same folder as that .exe is StartPanel.exe, check that one out if you want a funky looking full-page version of your regular Start menu)
not sure if this is the same in earlier versions of Wisbar, but i thought I'd mention it if any of you have the program, and there was also a way of doing the same thing in iLauncher. hope this helps somebody...
Dr J, thanks for the tip, I have pocket plus 4 and wisbar 3, so it is perfect for a shortcut to open the settings panel.
I would like to change the font size options that come with the Nook Reader.
The reader.apk comes with seven different font sizes : from 7.0 to 27.0
The smaller at 7.0 is too small to be useful
and the largest at 27.0 is too large
and the jump from the fifth size (13.0) to the sixth size (20) is too big a jump.
I have used apktool to take apart the apk as in this post http://forum.xda-developers.com/showthread.php?t=1735858
The font size options appear to be set in /com/bn/nook/reader/commonui/ReaderCommonUIConstants.smali
lines 117 to 129
I changed the font sizes to 11.0, 12.0, 14.0, 16.0, 18.0, 20.0 and 22.0.
Saved the .smali file.
I then used apktool to put it all back into a newreader.apk
signed newreader.apk
deleted the existing reader.apk from my nook
adb pushed this apk to /system/app/reader.apk
But when I open a book, the font size options are just the same as before my changes. It is as if no changes were made at all
Any suggestions?
ladykayaker said:
I would like to change the font size options that come with the Nook Reader.
The font size options appear to be set in /com/bn/nook/reader/commonui/ReaderCommonUIConstants.smali
lines 117 to 129
Click to expand...
Click to collapse
For those who don't feel like taking apart the apk, the lines referenced are:
Code:
.field public static final FONT_SIZE_1:D = 7.0
.field public static final FONT_SIZE_2:D = 8.5
.field public static final FONT_SIZE_3:D = 9.75
.field public static final FONT_SIZE_4:D = 11.0
.field public static final FONT_SIZE_5:D = 13.0
.field public static final FONT_SIZE_6:D = 20.0
.field public static final FONT_SIZE_7:D = 27.0
Which looks like a pretty reasonable place to make the changes, right?
To understand why this doesn't work, you need to know a little bit more about the Java compiler, specifically what it means to declare a value as static final.
Consider the following Java code:
Code:
private static final double TEST = 9.75;
private static void test() {
double myVal;
myVal = 1.23;
if (myVal != TEST)
myVal = TEST;
}
Since you've flagged the TEST value as static final, you're making a promise to the compiler. And that promise is: "I promise to never, ever change the value of TEST. It's 9.75 now and it's going to be 9.75 every time you run this program no matter what."
When the compiler hears you make that promise, it's just going to go ahead and substitute the value 9.75 every single time it comes across a reference to TEST.
So, to the compiler, the above code "pre-compiles" to:
Code:
private static final double TEST = 9.75;
private static void test() {
double myVal;
myVal = 1.23;
if (myVal != 9.75)
myVal = 9.75;
}
which we can verify against the resulting smali code:
Code:
# static fields
.field private static final TEST:D = 9.75
.method private static test()V
.registers 4
.prologue
.line 6
const-wide v0, 0x3ff3ae147ae147aeL
.line 8
.local v0, myVal:D
const-wide v2, 0x4023800000000000L
cmpl-double v2, v0, v2
if-eqz v2, :cond_13
.line 9
const-wide v0, 0x4023800000000000L
.line 10
:cond_13
return-void
.end method
(0x4023800000000000L is the hexadecimal representation of the double value 9.75)
Notice that there is still a static definition of TEST as 9.75. But in the code, there are no more references to TEST, just references to the value of TEST at the time the code was compiled.
In this example, if you were trying to replace 9.75 with 12.0, you would need to find the value 0x4023800000000000L and replace it with 0x4023800000000000L each place in the code. Of course, you need to be careful: since the constant labels have been stripped, you have no way of knowing if the original code referenced TEST, or 9.75 or OTHER_DEFINITION that also happened to be 9.75 and you don't want to change it in places where it may be referring to 9.75 as the price of a book instead of 9.75 as the size of a font.
Fortunately, 9.75 is a pretty unique value so a quick search through the Reader code results in only one result:
Code:
D:\nook\Reader>grep -ir 0x4023800000000000 *
smali/com/bn/nook/reader/commonui/ReaderCommonUIConstants$5.smali: const-wide v1, 0x4023800000000000L
Looking at the file, we can see in the Init() function is basically preparing a hashmap with the following values
Code:
1 => 0x401c (7.0)
2 => 0x4021 (9.0)
3 => 0x4023800000000000L (9.75)
4 => 0x4026 (11.0)
5 => 0x402a (13.0)
6 => 0x4034 (20.0)
7 => 0x403b (27.0)
Which is funny, because it's actually using 9.0 instead of 8.5 as the second font size despite the defined value and all of the values except 9.75 are defined as integers rather than Doubles. It looks like some B&N programmer ignored the FONT_SIZE_X definitions and just hard coded the values herself. Anyhow, this creates that mapping that is (most likely) used internally by the reader to find the proper sizing to use for each of the 7 font size options.
I don't have Reader.apk installed on my Nook so I can't actually test this out. But I'm pretty sure if you change the values in ReaderCommonUIConstants$5.smali you'll end up with the results you want.
If that doesn't work, let me make a plug for Cool Reader, which among many other advantages versus the stock Reader has a much larger range of font sizes to choose from.
Yes, that did it. I didn't consider that the values would actually be hard-coded!
Some people have expressed a need to read foreign language media on their nook, with the stock reader.
I am trying to work out how to make the necessary changes to the stock reader so that the user can select their own font family, such as thai, hebrew, korean, etc.
Using apktool to extract the smali files - I have changed the following lines
(changing from Amasis30.ttf to Hebrew.ttf)
com\bn\nook\reader\activities\ReaderActivity$34.smali
.field public static final FONT_FAMILY_AMASIS:Ljava/lang/String; = "Amasis30"
.field public static final FONT_FAMILY_AMASIS_PATH:Ljava/lang/String; = "/system/fonts/Amasis30.ttf"
com\bn\nook\reader\commonui\ReaderCommonUIConstants$6.smali
const-string v1, "Amasis30"
com\bn\nook\reader\commonui\ReaderCommonUIConstants.smali
.field public static final FONT_FAMILY_AMASIS:Ljava/lang/String; = "Amasis30"
.field public static final FONT_FAMILY_AMASIS_PATH:Ljava/lang/String; = "/system/fonts/Amasis30.ttf"
com\bn\nook\reader\commonui\TextSettingsView.smali
const-string v1, "/system/fonts/Amasis30.ttf"
But, this doesn't seem to be enough.
The font name in the list of six options still says Amasis, but it is in the new font type.
The font in the book has defaulted to Malabar font.
The preferences.xml gives the new font type.
Where else is should I look to find the references to the font file?
Quick answer: replace the two in-code references below with /system/fonts/Hebrew.ttf (assuming this is the correct path and capitalizaton for the font file)
Code:
smali/com/bn/nook/reader/activities/ReaderActivity$34.smali: const-string v3, "/system/fonts/Amasis30.ttf"
smali/com/bn/nook/reader/commonui/TextSettingsView.smali: const-string v1, "/system/fonts/Amasis30.ttf"
Leave everything else untouched. Don't worry about the "static final" definitions.
This line
smali/com/bn/nook/reader/commonui/TextSettingsView.smali: const-string v1, const-string v1, "/system/fonts/Amasis30.ttf"
sets the font for font name in the popup window where the user selects the font.
This line at first doesn't appear to make a change,
smali/com/bn/nook/reader/activities/ReaderActivity$34.smali: const-string v3, "/system/fonts/Amasis30.ttf"
the book hasn't changed to hebrew font, but on closer look the book is now in Malabar font(the one in the list above Amasis)
after digging around it appears the font may be stored in FONTFAMILY_MAP
but then again, I go round in circles following this, and it might only be used to write the ReaderPrefences.xml file.
It seems the font file names are being stored somewhere, perhaps not in Reader.apk
but I can't find where.
You might find the info in this blog:
http://phanquochuy.me/?p=114
and this thread
http://bookclubs.barnesandnoble.com...n-t-display-Vietnamese-characters/td-p/494819
helpful re: some other approaches to adding alternative fonts.
My idea is to make it easier for a user to change font in the stock reader.
I think this is done in com\bn\nook\reader\activities\ReaderActivity$34.smali
If I change the lines referring to Amasis font, to the new font name (spelling, uppercase, etc checked to be correct)
then it doesn't use the new font, it also doesn't use Amasis, but uses the previous in the list, that is Malabar.
I looked through the older threads and couldn't instructions what to modify to turn the Home Button Wake Feature off on a rooted S5. If someone could tell me how to do this it would be greatly appreciated. Thanks.
If anyone can point me in the right direction it would be greatly appreciated. I have tried editing the file specified for other S series phones without success. Thanks.
I was able to do it on the S4 when it first came out. It was trial and error though. I edited every file I could find in the system folder that said "home Wake". I deleted the word "wake".
I agree it's annoying though. I have to keep a pin code lock because my phone constantly calls people from my pocket even with swipe to unlock turned on
Sent from my Galaxy S5
there is option in Wanam expose to do that, i didnt tried it yet so cant really tell it work or not.
Needed to bump this thread. I have done some serious pocket dialing. The ex and 911 are 2 examples.
I have a pin for the lock screen, but sometimes it work.
Thanks for the suggestions. I tried Wanam and it did not work on my ATT S5. I also went through some of the files in the key layout folder and only found two instances of Home Wake. I tired deleting Wake on both of them and that didn't solve the issue. If anyone has any other ideas I would be glad to try them.
So far the only solution I have is to not put it in my pocket. I have a gear2 for notifications and to let me know when I have a call, otherwise it sits on my desk, or in my briefcase.
Couldn't they make it a gesture using the gyroscope and pedometer?
My not so smartphone goes upside down in my pocket and it's counting my steps. I think the would be a simple solution.
Find this method in phonestatusbar.smali in android.policy.jar....
.method private isWakeKeyWhenScreenOff(I)Z
Find :sswitch_2
And put....
return v1
So in full....
Code:
.method private isWakeKeyWhenScreenOff(I)Z
.locals 3
.parameter "keyCode"
.prologue
const/4 v0, 0x1
const/4 v1, 0x0
.line 6699
sparse-switch p1, :sswitch_data_0
.line 6723
:cond_0
:goto_0
return v0
.line 6704
:sswitch_0
iget v2, p0, Lcom/android/internal/policy/impl/PhoneWindowManager;->mDockMode:I
if-nez v2, :cond_0
move v0, v1
goto :goto_0
:sswitch_1
move v0, v1
.line 6721
goto :goto_0
:sswitch_2
return v1
nop
.line 6699
:sswitch_data_0
.sparse-switch
0x3 -> :sswitch_2
0x18 -> :sswitch_0
0x19 -> :sswitch_0
0x1b -> :sswitch_1
0x4f -> :sswitch_1
0x50 -> :sswitch_1
0x55 -> :sswitch_1
0x56 -> :sswitch_1
0x57 -> :sswitch_1
0x58 -> :sswitch_1
0x59 -> :sswitch_1
0x5a -> :sswitch_1
0x5b -> :sswitch_1
0x7e -> :sswitch_1
0x7f -> :sswitch_1
0x82 -> :sswitch_1
0xa4 -> :sswitch_0
0xde -> :sswitch_1
.end sparse-switch
.end method
That should stop home from ever waking device
Sent from my SM-G900F using Tapatalk
Goldie said:
Find this method in phonestatusbar.smali in android.policy.jar....
That should stop home from ever waking device
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
Thanks. I think this solution is slightly above my technical ability right now. I did some looking and understand what needs to be done to modify the jar file, but not exactly what programs I need. Can you point me in the right direction to the noob guide to decompiling and recompiling the jar file?
Does anyone have another way to disable the home button wake? Thanks.
I put my phone in a larger case. And it has prevented some of the home button wakes, but now am having issues with the screen locking up, as if my finger was held in one spot on the screen. I have to pop the battery out and restart the phone.
ampm325 said:
I put my phone in a larger case. And it has prevented some of the home button wakes, but now am having issues with the screen locking up, as if my finger was held in one spot on the screen. I have to pop the battery out and restart the phone.
Click to expand...
Click to collapse
My phone is also pocket calling 911. Gets past my lock setup, too. Haven't found a forum yet stating that rooting my ATT G900A is possible.
Hello Gents
Have a look below.
Code:
##################################################
# Select Positioning Protocol on A-GLONASS system
##################################################
# 0x1: RRC CPlane
# 0x2: RRLP UPlane
# 0x4: LLP Uplane
#ifndef [email protected] enable all bit mask for GLONASS
#A_GLONASS_POS_PROTOCOL_SELECT = 0
#else
[B][COLOR=Red]A_GLONASS_POS_PROTOCOL_SELECT = 15[/COLOR][/B]
#endif
Source: https://review.lineageos.org/c/Line...8998-common/+/200009/26/gps/etc/gps.conf#b132
I am intrigued about the value "15" .
I can't seem to find any documentation on internet or in the research papers. I tried to email the guy but the email bounces back.
Now it really really made me curious: how did they come up with these values? There must be some documentation for it somewhere...
Would any of you guys know where did they pick up their values from?
Thanks
Quick update
A_GLONASS_POS_PROTOCOL_SELECT = 0x2 (GSM, без LTE, без CDMA)
A_GLONASS_POS_PROTOCOL_SELECT = 0x6 (GSM+LTE, без CDMA)
https://4pda.ru/forum/index.php?showtopic=597293&st=760
A quick google translation of the pages shows it as:
A_GLONASS_POS_PROTOCOL_SELECT = 0x2 (GSM, no LTE, no CDMA)
A_GLONASS_POS_PROTOCOL_SELECT = 0x6 (GSM + LTE, no CDMA)
That post is from 2014 and it does not explain anything.
There must be some documentation they are picking these values up from , but I can't find it.