yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] hypophysis:
Thanks a lot crpalmer for maintaining this unofficial cm11 version.

Two little things I recognized on this almost flawless port:

There's a bug that screws up the rendering of the pin input screen (see screenshot).

I'm missing a quicksettings tile for the torchlight (cm11 on my phone has it).
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] crpalmer:
What version are you running? I thought I fixed and added Torch around September 1st.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] crpalmer:
Can you

* install stock

+ start logcat and start capturing the output

+ make a call

* install CM

+ start logcat and start capturing the outpu

+ make a call

and the post (or PM) links to the two logcats. That will tell me if I'm using a wrong acdb device which is the most likely reason for something to be worse in CM than on stock related to in-call audio.

Unfortunately, that's only about 50% likely to give me enough information to tell that there really is a problem and how to fix it, but it's worth a try if you want me to look at it...
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] hypophysis:
I'm using the latest nightly. The torch App is there and working, but there should also be a quicksettings tile to toggle the light.
[HTC One Mini] UnicycleWheelie:
HTC One Mini (AT&T)

(bootloader) version: 0.5

(bootloader) version-bootloader: 2.19.0000

(bootloader) version-baseband: N/A

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 1.32.502.3

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) serialno: HT382WA01938

(bootloader) imei: 356482050048610

(bootloader) meid:

(bootloader) product: m4_ul

(bootloader) platform: HBOOT-8930

(bootloader) modelid: PO5822000

(bootloader) cidnum: CWS__001

(bootloader) battery-status: good

(bootloader) battery-voltage: 4299mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-5cc83deb4d

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

I have tried to use this RUU - RUU_M4_UL_JB_50_Cingular_US_1.32.502.3_Radio_1.19.40d.00.14_10.20.40.4408L_release_333483_signed_2

No luck (error 171)

also every time I try to do anything in fastboot I get

(bootloader) signature checking...

FAILED (remote: signature verify fail)

HTCdev - tried to unlock bootloader phone hangs, and the phone doesn't show up in adb

I just got an OTG cable in the mail today...
[HTC One Mini] Shacho:
Did the cable work for you - getting it out of the BL screen?
[Android Q&A, Help & Troubleshooting] JoeFCaputo113:
Looking for an app that when I am at home and on my PC, I can receive and interact (mark SMS as read, dismiss Twitter notification, etc.) with all notifications (SMS, Twitter, Hangouts, etc.). Anyone have any suggestions? I tried THIS app but you could not interact with any notification.
[Android Q&A, Help & Troubleshooting] GuestK00426:
Pushbullet works well,but you need google chrome to be installed on your PC.

P.S. : You posted in the wrong section
[Android Q&A, Help & Troubleshooting] MrBlackCore:
Airdroid

Airdroid
[Android Q&A, Help & Troubleshooting] JoeFCaputo113:
I believe that's only for SMS/calls.
[Android Q&A, Help & Troubleshooting] JoeFCaputo113:
Anyone else?
[Android Q&A, Help & Troubleshooting] JoeFCaputo113:
bump
[Galaxy S 5 Q&A, Help & Troubleshooting] lingowistico:
There should be a stickied S5 dictionary for noobs..

What does "KLTE" mean? I'm asking this because I'd like to flash TWRP through TWRP manager but I have no idea if my phone is KLTE or not..

EDIT: found answer over here http://xdaforums.com/showthread.php?t=2784690

EDIT: 2014-09-29

Let's have a definite confirmed answer as to where these device type names come from. :good:
[Galaxy S 5 Q&A, Help & Troubleshooting] John Bentley:
This question is not answered.

The closest thing to an answer in the thread you linked to,	[Q]Possibly a stupid question... (IDing handset version) is

... which hints at an answer but falls far short. A google search for "klte" or "what is klte" returns XDA forum threads, including this one, which use the term but don't define it.

I'd suggest removing the "[Solved]" from your title until some kind and experienced user can enlighten us noobs.

A response here, rather than the other thread, would be better given this current thread is descriptively titled ("What does "KLTE" mean?").
[Galaxy S 5 Q&A, Help & Troubleshooting] vndnguyen:
klte is just a Device Type for Galaxy S5, as hlte is Device Type for Galaxy Note 3...

You can see more detailed info in Phone INFO ★Samsung★ app.

(Model name, Device type, Product name, Product code, etc...)
[Galaxy S 5 Q&A, Help & Troubleshooting] John Bentley:
Thanks vndnguyen. That provides a partial picture. For example I now can see the "Device Type" field in the Phone INFO Samsung app (which, incidentally, for my Samsung Galaxy S2 repeats the value for "Phone Model", GT-I9100.

That contradicts the information provided by gee2012. That is, that for one phone model, such as the Samsung Galaxy S5, there can be multiple device types. This is further illustrated at teamw.in/twrp_view_all_devices, looking at one model, for example, the Samsung Galaxy S4 you see multiple device types:

TWRP for Samsung Galaxy S4 (Canada) [jfltecan]

TWRP for Samsung Galaxy S4 (Cricket) [jfltecri]

And this misses the basic questions. Is "klte" a designation internal to Samsung or do other manufacturers use it? Are the letters random or based on some code that references something (the above examples seem to reference a region and carrier)? Where is the list, at least for the Samsung Galaxy S5, of device types? Does "ktle" reference a region or a piece of hardware? etc.

Edit 01: Fix quote format.
[Galaxy S 5 Q&A, Help & Troubleshooting] lingowistico:
K stands for Krait (name of cpu) and LTE stands for well LTE.

Basically KLTE is used as short for S5's based on the Snapdragon 801 chipset.

That's how I see it.
[Galaxy S 5 Q&A, Help & Troubleshooting] vndnguyen:
LTE is correct, but K does not stand for Krait, as Note 3 also use the same CPU, but its Device Type is hlte.

---------- Post added at 10:47 AM ---------- Previous post was at 10:33 AM ----------

And also please be noted that you can easily change the Model Name (SM-G900F), Device Type (klte), Product Name (kltexx) by editing the build.prop file.
[Galaxy S 5 Q&A, Help & Troubleshooting] John Bentley:
famtour Friends

Thanks [MENTION=5045554]lingowistico[/MENTION] and [MENTION=2018502]vndnguyen[/MENTION] for your responses.

vndnguyen thanks for providing information about where these values reside (build.prop). Of course if those values where changed then they would simply inaccurately reflect the intentions of Samsung to identify its model, device, and product.

lingowistico, vndnguyen has claimed that your speculations are not, in fact, true. Given that, and that the basic questions remain, what do you think of my suggestion?
[Galaxy S 5 Q&A, Help & Troubleshooting] lingowistico:
Yes of course. You can't have two different devices with the same name. So what does the K stand for? How do you know for sure that it doesn't stand for krait?

What is your suggestion? I'm sorry I didn't get it.
[Galaxy S 5 Q&A, Help & Troubleshooting] John Bentley:
vndnguyen's point is that that there are two different devices, a Samsung Galaxy S5 and a Samsung Note 3, with *different* device types strings; and if "K" stood for krait, a group of snapdragon processors, then the Note 3 variant with a snapdragon 800 would have a device name with a "K" in it. But the (relevant variant of the (I assume)) Note 3 has a device type of "hlte", so ndnguyen claims.

Even if vndnguyen was mistaken about that you seem to be guessing ("That's how I see it.") at how the device type string is derived, not making a claim to know how the device type string is derived based on evidence. What I'm after is knowledge.

Me:
[Galaxy S 5 Q&A, Help & Troubleshooting] vndnguyen:
IMO, the Device Type is just a random name, it has no meaning.

Here is some Device Type for your reference:

Galaxy Tab 2 10.1 - espresso10wifi

Galaxy Tab 2 7.0 - espressowifi

Galaxy Tab 3 10.1 - santos10lte

Galaxy Tab 3 7.0 - lt02lteatt

Galaxy Tab 3 8.0 - lt02lte

Galaxy Tab 3 - lt01lte

Galaxy S3 - m0

Galaxy S4 - jflte

Galaxy S5 - klte

Galaxy Note 2 - t03g

Galaxy Note 3 N900 - ha3g

Galaxy Note 3 N9005 - hlte

As you can see, the suffix of the Device Type is type of network supported (wifi, 3g, lte) or network provider (att - AT&T, spr - Sprint, tmo - T-Mobile, vzw - Verizon...). But the prefix is random and can not be predicted.
[Galaxy S 5 Q&A, Help & Troubleshooting] lingowistico:
The point of of this thread was to have a simple answer to the following question:

Can I flash "KLTE" roms? I got my answer.

But since you've now embarked on a quest for some actual knowledge behind "KLTE" I'm going to go ahead and remove SOLVED from the title. Because you've intrigued me.
[Galaxy S 5 Q&A, Help & Troubleshooting] lingowistico:
http://developer.samsung.com/home.do is a good place to look for an answer I think.
[Galaxy S 5 Q&A, Help & Troubleshooting] John Bentley:
Good on you lingowistico. That's the spirit!

[MENTION=2018502]vndnguyen[/MENTION]. Yes it does seem that Device Type is used by Samsung with no deterministic algorithm. The suffixes do seem to be some combination of the most advanced (or more costly?) radio in the device (wifi, 3g, lte) with an optional carrier. Yeah I don't know what the prefix could reference. Perhaps it's just a sequence designator.

Again, the biggest list of device types to model name mappings I've found is http://teamw.in/twrp_view_all_devices

So that establishes one of my issues: Is device type specific to Samsung? No. For example HTC has device types.

And indeed I've found an official Android definition at http://developer.android.com/reference/android/os/Build.html , which explains most of the values found in /system/build.prop. So ro.product.device (it seems) is explained as

Not that "The name of the industrial design" is especially meaningful. But it seems to be the clue that its a field is used by Manufacturer's however they like, for their internal purposes.

From SM-G906S/K/L/ S805 Info Sharing thread (Root/CWM/Custom Rom)

Which is not quite right given that a SM-G900H has a ro.product.device of "k3g" as shown in a build.prop dump at Any Indian here Owning Galaxy S5? Need help > Post 3

What we need is an official or unofficial list of all device types for all Samsung devices, or at least for all Samsung Galaxy S5. lingowistico, for that purpose thanks for the http://developer.samsung.com/home.do link. I'm rooting around there, so far without success.
[Galaxy S 5 Q&A, Help & Troubleshooting] shohag2018:
[MENTION=2018502]vndnguyen[/MENTION] i have a 900F "klteZH" . will brick it if try to flash klteXX roms on it?
[Galaxy S 5 Q&A, Help & Troubleshooting] vndnguyen:
I don't own S5, but the answer is most likely yes.

ZH is Hong Kong version and XX is international version. These variants are not compatible with each other.

If you want to flash klteXX rom, you need the PIT file from that variant.
[Galaxy S 5 Q&A, Help & Troubleshooting] shohag2018:
Where can i get it?

EDIT: ok now this is what happened. i just flashed the universal gsm built for cm12 unofficial, and now the device is being shown as kltexx. is it in any way possible that first two letters maybe denote only the Region and has nothing to do with the hardware? its shown as 900F afterall.. not M/i/k/s or anything..
[Galaxy S 5 Q&A, Help & Troubleshooting] halo12lol:
not really, its more of software, as you know that klte and kltexx are international, you flash Roms for "klte" or "kltexx". in reality, I think its the same thing.
[Galaxy S 5 Q&A, Help & Troubleshooting] UltraNoob:
Thanks a lot for this thread. It helped clear up my confusion about my phone. I just got this s5 and was trying to figure out if i could flash a rom
[Galaxy S 5 Q&A, Help & Troubleshooting] Noman Tahir:
Samsung Galaxy S5 Duos Sm-g900fd

plzzz get Custom roms for (Samsung Galaxy S5 Duos Sm-g900fd)
[Galaxy S 5 Q&A, Help & Troubleshooting] itradsk:
Waht about canadian KOT49H?? )900W8(

There are limited supports for this device.. but i figure what the heck try an 'F' rom or an 'H' ROM??
[Galaxy S 5 Q&A, Help & Troubleshooting] nalgrim:
Itradsk I've tried omega rom it works fine, I've tried the cyanogen version and it worked fine without me having to play with any kind of connection settings. Currently I am using xtreolite and its smooth and I didn't have to do anything.

Just remember to flash the lollipop kernel and bootloader

Telus Samsung G900W8
[Galaxy S 5 Q&A, Help & Troubleshooting] thanksall:
According to Wikipedia, https://en.wikipedia.org/wiki/Samsung_Galaxy_S5

KLTE is the "codename" for the Samsung Galaxy S5

You'll see it at the top of the right hand sidebar there.
[Galaxy S III Q&A, Help & Troubleshooting] talk2montu:
Hey Guys,

I was wondering if there is a way to be on custom rom (IE: CM, AOKP etc) and still have samsung apps, so that I can do all-share cast, stream videos to my tv ETC. I have a sprint S3.

Thanks,
[Galaxy S III Q&A, Help & Troubleshooting] the Doctor:
All of the Samsung apps and services require the TouchWiz framework to function. Non-TouchWiz ROMs like CM and AOKP will not support them, but there may be equivalent apps out there.

BTW, questions should be posted in the Q&A section.
[Galaxy S 4 Q&A, Help & Troubleshooting] reg66:
as per title really. is there any way to get long press back button to kill app running stock 4.4.2?

cheers
[Galaxy S 4 Q&A, Help & Troubleshooting] XxLordxX:
Hi,

If you root your device and install Xposed you can try this:

http://xdaforums.com/xposed/modules/app-wanam-xposed-customize-stock-t2383484

All the best,

~Lord
[Galaxy S 4 Q&A, Help & Troubleshooting] reg66:
thanks but i want to stay without root, any other suggestions?
[8525, TyTN, MDA Vario II, JasJam General] schwaitz:
I have a vodafone 1605 and there is something weird happening. When I turn on the Wlan to find my wireless network, the phone find the current network, but the phone can´t connect to the network. The IP showed in the phone ( 169.254.25.138) is not from the range of the IP´s I´ve assumed ( 192.168.0.1 to192.168.0.100 ). How can I make the phone connect to my network ??
[8525, TyTN, MDA Vario II, JasJam General] vua777:
i met this problem when i change my wifi wep, i just reset/del old connection profile, and the system ask me to reconfig if it detect new wlan

control panel -> connections -> Network Cards -> Wireless tab

you'll see detected wlan, tap&hold to del its config profile

hope it work for you
[G3 Q&A, Help & Troubleshooting] deedscreen:
So most of us know about the System UI crash when using Chromecast, but this is even stranger. [Edit: an OTA update fixed this.] Some times, when I wake my phone up at the lockscreen or at times in the middle of a call - the touch screen stops responding. I can press and/or hold the volume buttons and there is a response on screen but I can not interact with the phone at that point. I can't continue to do battery pulls everytime. This is crazy. I'm on stock software. No crazy mods or anything. I've done a reset in the past and flashed the stock package again but this still happens every few hours. Only happens when the screen just wakes up...

Edit: This is a confirmed fix for me.

If you face the same issue, try:

open dialer

press 3845#* INSERT THREE DIGETS OF YOUR MODEL NUMBER THE PRESS #, for example, I am the F400K, so 3845#*400#

Hardware Device Test > Touch

update touch firmware

touch firmware version

wait 10 sec

reboot
[G3 Q&A, Help & Troubleshooting] Lennyuk:
I would say there is a misbehaving app causing the phone to lag in wake (that is all the unresponsiveness will be, extreme lag).
[G3 Q&A, Help & Troubleshooting] deedscreen:
[MENTION=2315688]Lennyuk[/MENTION] - tried for over 30minutes after leaving it alone, I doubt it's a delay... Battery pulls work, but that's not the point.
[G3 Q&A, Help & Troubleshooting] Epix4G:
That was not his point.....to Find the app that is causing it go one by one uninstalling until you find it.... Something probably to do with app and the screen

Sent from my SM-N900P using Xparent BlueTapatalk 2
[G3 Q&A, Help & Troubleshooting] mikeythedude:
Totally agree with [MENTION=4257843]Epix4G[/MENTION] on this one. I am assuming you had a korean variant? The SK Telecom stock image is pretty ugly. Took me 3 debloat attempts before I had it behaving the way I wanted it to, but before I debloated, I had some lag issues (SK Telecom... grrrhhh).

Historically, Korean carriers (much like AT&T and Verizon) love putting useless junk on the phones for "productivity" but really they are there to charge Korean users more for other services, etc.

If you haven't done so, I would root and debloat, and see how big of a difference it makes (absolutely amazing performance after debloating on my F400S).
[G3 Q&A, Help & Troubleshooting] deedscreen:
^^^^ - Will take that into consideration.

This may be a possible fix for now, can't yet confirm

open dialer

press 3845#* INSERT THREE DIGETS OF YOUR MODEL NUMBER THE PRESS #, for example, I am the F400K, so 3845#*400#

Hardware Device Test > Touch

update touch firmware

touch firmware version

wait 10 sec

reboot

It may or may not help

EDIT: It's been a few weeks and I haven't had this issue again. Usually every 4-6 hours it used to happen after powering on the screen, but so far so good.
[G3 Q&A, Help & Troubleshooting] Daum Ex:
Tried that with 855 version, it's not working. This is REALLY depressing as i just got a new phone and from day one i'm having this problem. I just can't believe LG screwed up like this, and there's no mention of this anywhere online other than this XDA thread. I hope i don't have to root and install custom rom as this really defeats the purpose of the phone.
[G3 Q&A, Help & Troubleshooting] xedahh:
[MENTION=3142385]deedscreen[/MENTION]

I'm having exactly the same problem on an 850 and tried your firmware method. The version number of the firmware did not change after reboot.

ic_fw_version info

SYnaptics 5.5

PanelType 1

version: v1.22

IC_product_id[PLG313]

Touch IC : s3528(family_id = 1, fw_rev = 1)

What version is your firmware? Also, did you find out about the fix from somewhere?
[G3 Q&A, Help & Troubleshooting] deedscreen:
I have the F400K, but just got a US T-Mobile edition, (I'll eventually switch my signature). I would honestly suggest waiting for an OTA update. Call LG so they can document this. If that touchscreen update method doesn't work, I'm not sure what to do. I found the method somewhere online, I don't recall where exactly. If someone can figure out how to side load the touch screen firmware from a working Korean model to others, that would be great. For now, keep calling LG. It won't do much at first, but at least they'll have reports of this issue.

I have (RAW) touch screen firmware version: 30 05 51 96
[G3 Q&A, Help & Troubleshooting] icon71:
Same problem, but not only on lock screen

Since 5 days I have my G3 (855 Modell). I was happy the first two days, then I discovered the problem, that the device is always unlocking itself, when in my front pocket. It's because of the Knock on feature. I deactivated this now.

But since yesterday i have the same issue: three times, i was unable to unlock my phone. The touchscreen simply did not respond. I had to remove battery. Today, I read this post and tried the firmware update of the touch, but I have the impression it did not change something in the version.

After this, today I had again once time the non responding touch while unlocking and shortly after, I had the issue after ending a phone call! The touch did no longer respond and had to remove the battery again!

I hope this is not a hardware issue, otherwise I will hurry up to the seller to exchange the phone, because its only 5 days old.
[G3 Q&A, Help & Troubleshooting] J_Dutch:
This is happening when the screen is on right? Or is the screen turning off and then not turning I again?
[G3 Q&A, Help & Troubleshooting] Daum Ex:
You need to keep Knock feature on, someone already said this. That's why your screen is freezing.
[G3 Q&A, Help & Troubleshooting] icon71:
Upps, yes, I just read this message now. To late: I was in the shop now and got mine exchanged. Anyway, that issue with the knock on feature should be solved also by LG: it's not acceptable, that the phone is always unlocking in my pocket.But then I wait with deactivating knock on for the moment.

So bad: such a good phone and such an annoying bug :(
[G3 Q&A, Help & Troubleshooting] Daum Ex:
I sold mine after a few days, i was sick with it. I disabled the knock feature through the hidden menu only to have the screen freeze every day. What, i can't use the phone the way i like? I have to face the screen outwards in my pocket and risk damaging it? Screw that...

That, plus the overheating and horrible build quality (back got scratched in my pocket) was a deal breaker for me...
[G3 Q&A, Help & Troubleshooting] icon71:
Yes, indeed i also think about it. I got an official statement from support, regarding that the phone is unlocking all the time by itself in my pocket. They told me stuff like:

- this is a normal behaviour and can happen (!!)

- don't put your phone in the front pocket

- use the quick circle case to prevent...

- disable knock on (which is at least not possible over a standard setting, but only via the hidden menu).

I wrote back:

- that for me, this is not a normal behaviour

- that 90% of male users are wearing the phone in the front pocket

- that I don't like to buy a case only to prevent a bug of a premium telephone and

- finally, that they please could tell me, where and how to disable knock on ;)

I am curious about their answer...
[G3 Q&A, Help & Troubleshooting] Daum Ex:
Good luck with that, disabling it through the settings doesn't change anything and they probably won't have a fix for months. They'll probably fix it though Android L update which will sadly come 6 months from official release at least.

Next time i purchase an Android phone i'm going with Nexus line...
[G3 Q&A, Help & Troubleshooting] deedscreen:
So what happened? How is it doing now?
[G3 Q&A, Help & Troubleshooting] OffDatGoGo:
Hey everyone, I just wanted to report my results of this touchscreen bug.

Well, I've only had my D851 for a week now. Of course I rooted it the same day I received it.

I had no touch issues until after restoring apps with Titanium Backup. I'd restore all user apps, then very few system app via XML. Since I just upgraded from a Galaxy S3 T999 I limited the system apps greatly. So much in fact that I only restored 1 system app......Media Storage 4.4.4 (Playlist). THAT WAS MY SCREEN KILLER!

The media scan on my D851 would render my screen unresponsive. I could only hold the power button and click power off or restart or whatever else was on that power menu. Then the phone would reboot after minutes of of a dead screen.

I flashed back to stock and reproduced the same issue. So now I've been running this device for 3 days without any screen lockups. I just have to rebuild my playlist again LOL.

I hope this helps someone here.
[G3 Q&A, Help & Troubleshooting] jr12866:
Knock

If you turn off the ability to wake by knocking the screen, it causes this issue where the screen locks. Turn it back on and the problem seems to go away.

I think LG really has to deal with this issue.
[G3 Q&A, Help & Troubleshooting] mrng:
Hi guys, I have red a lot about this issue but I'm still confused with my LG G3 855.

First I realize problem with unlocking the phone using double click. Tried to upgrade touch software firmware using hidden menu and the screen became almost totally unresponsive. Tried to re-flash original 5.0 and 4.4.2, factory reset, battery removed, etc. but no luck.

I'm wonder if this is a software problem or became hardware. Should I consider replacing display or problem is in motherboard?

I really don't know what to do! Appreciate any comments or suggestions!!!

Thanks in advance!