yashsingh1/xdaforums huggingface dataset:
[Verizon LG G3] ohlin5:
Just updated to the 1/9 official nightly, and pulled the phone out of my pocket a half hour later to find a kernel crash :) Lol
[Verizon LG G3] maximusmullivan:
I gotcha. Thanks for clarifying.

Sent from my Nexus 7
[Verizon LG G3] cowsquad:
How do I download the Gapps. I cannot get the zip file
[Verizon LG G3] Punchieo:
https://www.androidfilehost.com/?w=files&flid=22778

This is the generic stock version mirror pulled off the OP

Sent from my Sump'd and Bump'd G3, Thanks to Team Codefire
[Verizon LG G3] Pbaird1979:
You may have to switch to desktop mode
[Verizon LG G3] Noobla_Khan:
Looks like Dan has an official thread up for CM12 Nightly:

http://xdaforums.com/verizon-lg-g3/orig-development/rom-cyanogenmod-12-0-nightlies-verizon-t2998037

Thanks OP for providing us with unofficials and a place to discuss.
[Verizon LG G3] venuspcs:
invisiblek pulled all vs985 stuff from his site

Just went to look and the entire folder is gone. Does this mean no more updates from him?
[Verizon LG G3] touche112:
We're in official nightlies now. He's the maintainer, but the updates are on CynaogenMod's website. Check the thread in Original Development
[Verizon LG G3] venuspcs:
Thanks

I just went to my phones Settings and sure enough there are 3 official nightlies....WooT WooT
[Verizon LG G3] RyanEJ25:
So does that mean that this thread will not get updates anymore?
[Verizon LG G3] touche112:
That's exactly what it means. It was unofficial, now it's official. Development has moved.
[Verizon LG G3] RyanEJ25:
Thought so. I needed to do a fresh install anyway. :)
[Verizon LG G3] M I N E:
just flash this rom, everything is good but why is the battery and lte icon bar up top so small. how do i make them bigger?
[Verizon LG G3] klanistok:
just enable and disable airplane mode
[Verizon LG G3] Selim873:
Is the IR Blaster working? I just wanna make sure it's not just that none of my devices are compatible.
[Verizon LG G3] zebinadams:
Check this thread out.

http://xdaforums.com/showthread.php?t=2929146
[Verizon LG G3] Selim873:
Thank you so much!! :)
[Verizon LG G3] stu1978:
Deleted, wrong forum
[Verizon LG G3] ariek44:
Swype/gesture not work in the aosp keyboard, option enabled.
[Verizon LG G3] phreak311:
Hey guys, when I switch from CM 12 to 12.1 it royally effs up my phone.

Should I just do a Nandroid from CM12 and do a fresh install of CM 12.1?

Also my mass storage isn't working on CM12. I can't plug my USB cable into my phone and transfer content from my laptop, it simply doesn't show up anymore, so i've been using a USB OTG Flash drive to transfer stuff to my phone from my computer. Just wanted to know if anybody knew a fix for this!?!
[Verizon LG G3] tpayne2345:
Clean flashing 12.1 is the better idea from my experience, I've tried it but keep coming back to 12 for better xposed support

have you tried reinstalling drivers or using a different laptop for transfer? My Surface Pro 3 recognizes my device but I couldn't downgrade to 10b at all until I tried on my work-issued Dell laptop.. just a suggestion
[Verizon LG G3] Giblet535:
APN setup appears to be broken. Creating a "correct" VZWINTERNET APN doesn't save. Editing the existing one makes it disappear.

To reproduce: try to create an APN with MCC: 310 and MNC: 012. Save and observe that it is not there, or is now gone.

Effect: MMS won't work.
[Verizon LG G3] r4zrm4xxx:
Is there a way to get the stock lg camera back? Or is there a advantage to this cm cam? Also wondering the same about the HD calling
[Verizon LG G3] touche112:
Dude, we have official CM 12 and 12.1. Move on over to those threads/ROMs.
[Verizon LG G3] maximusmullivan:
LG camera only works on stock based roms.

Sent from my Nexus 7 2013
[Verizon LG G3] sentry_mode_activated:
Seems that it also fixes Google Maps navigation voice directions as well!
[Verizon LG G3] Airo18:
Does the WiFi Tether app from the play store work? Not sure if its just the native app or not
[Verizon LG G3] Zlatty:
Which app are you talking about. I'd love to give it a try as the native tethering breaks all the things until a restart.
[Verizon LG G3] jamsoolee:
I'm sure this is a known issue, just want to make sure someone reports it.

Snapchat closes randomly when viewing videos. Sometimes it will let me view the entire video, sometimes it will crash upon opening.

After the crash I have no service and dalvik/cachc wipe is required to get signal again.

This is even with nuaudio disabled in developer options.
[Verizon LG G3] THEbigSWEEN:
Yea I saw you said you cleared data and cache and added her # with a different contact name, figured I would just mention the contacts and contacts storage since it wasn't 100% clear if the wipe for for the app or the ROM. The only other thing I can suggest if you hadn't done it already is a clean install of the rom. That is a very weird and specific issue for two of you to have it for just one of your contacts... Maybe your phone is getting jealous and just doesn't want you talking to your wife?? :p
[Verizon LG G3] terminal13:
I can say that I clean flashed and have that issue as well
[Verizon LG G3] coheirnt:
New build fellas. http://xdaforums.com/showthread.php?p=57026162
[Verizon LG G3] RPelham:
It is pretty funny that it chose my wife to have this issue with! Haha! =p new (wiped everything but ext SD) install didn't work. I have no clue what could be causing it. Going to revert to KitKat for now (more so for the data issue rather than the wife issue). Hopefully future builds will fix this for us. =)
[Verizon LG G3] Crsdr37:
Any notes for the new build? Or is it just a nightly? Curious its been pretty solid today.
[Verizon LG G3] brochild:
MD5

Can somebody please post MD5 for the ROM and the Gapp

Thanks
[Verizon LG G3] david1985:
can someone help me find the apn settings ? im using tmobile with the verizon G3 and I can't seem to get it :confused:
[Verizon LG G3] terminal13:
http://xdaforums.com/showthread.php?p=57016939
[Verizon LG G3] coheirnt:
Not that I know of. I just flashed it over the other build now I'm getting 505 errors when downloading apps. so I'm going to try a clean install.
[Verizon LG G3] david1985:
thanks:good:

---------- Post added at 05:42 AM ---------- Previous post was at 05:40 AM ----------

confuse is there a new build or the same one still?
[Verizon LG G3] XylerSmith:
Just flashed invisiblek cm12 build and now i have no service lol. Hold off.

Edit- Wiped Cache & Dalvik now it's perfect.
[Verizon LG G3] ohlin5:
Can also confirm that data is working here...and I must say - holy ish this thing is FLYING!!! :p
[Verizon LG G3] HPeterson:
New build here by Tucstwo

http://www.drdevs.com/devs/tucstwo/cm/cm12/vs985/
[Verizon LG G3] Enigmafied:
Does it flash on twrp?

Does Hotspot work?

What is broken?
[Verizon LG G3] WhiteEVO:
Dirty flashed and DPI has changed, other than that I'm not sure,haven't had a chance to test call proximity sensor or BT on call...

Haven't had any problems at all, love this ROM and lollipop...
[Verizon LG G3] Airo18:
https://play.google.com/store/apps/details?id=net.snclab.wifitetherrouter
[Android Themes] Matthew2D:
Could someone please make a swiftkey theme that looks exactly like the galaxy s5 keyboard?
[Android Themes] thedisturbedone:
Might help: http://xdaforums.com/showthread.php?t=1016053
[XDA Assist] XDA Visitor:
I tried connecting with an USB adaptor cable but the memory stick is not detected. Do aI need a special cable or there may be another problem? If a different cabel, which? isense is not selling any cable for that.

Tx

Jose luis
[XDA Assist] Darth:
Hi,

You likely need an "otg cable", which is not the same as the cable that comes with the phone.

You can ask for other opinions here,

> Android Development and Hacking > Android Q&A, Help & Troubleshooting

Good luck,
[One (M7) Q&A, Help & Troubleshooting] shieldeverything:
Hi you all,

So to start things off i might say i tried alot of things to revive my htc one.

What happenend?

I wanted to give my htc one some new life so I thought lets factory reset it. All worked well but then the horror just began. My One began rebooting and rebooting itself over and over. So what i did next was enabled flight mode throught the power button and restarted the phone. So from then on it was running for about 30 seconds untill it starts rebooting again.

So what I did is unlock the phone and tried several Custom Roms. The only ones working are old cm11 roms, but I can not get S-Off to reflash the firmware because I am stuck with an eMMC 9001xxxxx... chip, so I guess bad luck for me.

So now my phone will not detect ANY SIM Card and will not show any imei number or baseband in the os. In the bootloader however they are still there, both of them.

RUU's will not work for me as I am S-ON and stuck on hboot 1.57

SunShine is not working either as my phone shuts down after aprox. 30 seconds on sense rom.

Firewater is not working either as it has an 9001.... eMMC chip.

my getvar stats:

(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3972mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

So my question is are there still any suggestions for me, that I didn't do or just overlooked?

So I would appreciate anything, before tearing it apart.. :)

Cheers
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
You don't need s-off to flash firmware. You only need s-off to downgrade or to use custom firmware. You will however need to relock your bootloader. Although I should tell you Unknown imei & Baseband often turns out to be a hardware problem.

You can flash this firmware with a relocked bootloader. You will need to 're flash custom recovery and Rom to boot the phone afterwards. Unless you flash a stock Rom first, Stock Rom can be downloaded here http://xdaforums.com/htc-one/development/rom-4-4-3-sense-6-6-09-401-5-100-stock-t2854300

Firmware download

http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One/401/6.09.401.10.zip

Download it and put it in your fastboot folder and rename it firmware.zip.

Reboot the phone to the bootloader and Connect fastbootusb. Now open your Fastboot command line and type

fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader

fastboot oem rebootRUU

--- case sensitive. ---^^^

The phone will reboot to a black screen with a Silver HTC LOGO. This is RUU mode. Now we're going to flash the firmware.

fastboot flash zip firmware.zip

The first flash will be short. It's just a preupdate preparing the hboot for the new firmware. So we need to do the same command again.

fastboot flash zip firmware.zip

The second flash will take a little longer and this time it will flash the full firmware. The progress bar on the phone screen will not reach 100% this is normal as long as the command window has completed its output the flash is done.

fastboot reboot-bootloader

If you found my posts helpful, no need to say thanks. There's a button for that ;)
[One (M7) Q&A, Help & Troubleshooting] shieldeverything:
Ok cheers m8!

I am gonna try it right now. Yeah I heard about the hardware problem, but I was thinking mine might be not because it happened after a factory reset (done in the os itself). I once was able to bring back baseband and imei but I just can't remember what exactely I did.

So I am going to report back as soon as I tried. I am wondering.

Btw you know what hardware defect actually would cause it (just wondering)

Thx!
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
With your phone s-on and on the latest firmware there's not much else you can do but flash the firmware package I linked. If you can get s-off you can try an ruu.

From a hardware perspective It's the antenna connector pin that causes the issue as far as I'm aware. I only know of one that was repaired without returning to HTC and the antenna connector pin was the cause. Replacing it solved the problem.

If you found my posts helpful, no need to say thanks. There's a button for that ;)
[One (M7) Q&A, Help & Troubleshooting] shieldeverything:
So I did everything and it worked. But only for 5-10 minutes and then it startet rebooting again and again. So I guess this is a hardware problem too and as I don't have any warranty or something there my m7ul goes...

Thx for your help anyways!
[One (M8) Q&A, Help & Troubleshooting] viper2011:
Hi all. I have a Telus One M8 that i recently converted to GPE using the non rooted GPE 4.4.4 RUU. Since converting I have noticed poor LTE reception. I have done some digging and found out that the GPE M8 does not support the 1700Mhz bands. Unfortunately Telus uses 1700Mhz for much of their LTE coverage. To fix this it should be as easy as flashing the correct Telus supported radio, correct? In the process of converting I changed the CID to GOOGL001 in order to receive the upcoming 5.0 update. In order to flash a different radio on the GPE RUU I will have to SuperCID? Which will then not allow me to take the 5.0 OTA update (most likely)? Just want to make sure I am correct in that I will have to choose between a Radio img that supports 1700mhz, or being able to accept the 5.0 OTA update.

Also, once the GPE RUU was flashed, do I have to go back and "fastboot oem unlock" the bootloader, or does it stay unlocked? Currently when I boot into fastboot the pink banner at the top says unlocked, I just want to make sure im not needlessly wiping my data.

I have tried searching (both in the GPE RUU thread, and the Canadian thread), but everytime I search within a thread I get "Sorry - no matches. Please try some different terms." even on terms that i know would come up in a search

Thanks for the Help!
[ONE General] itsdacj:
Really nice investigation right here! Appreciate it!
[ONE General] Theshawty:
Nice find!
[ONE General] memphian:
I luckily don't have a problem, or the guts to help with the theory. I did however figure it was hardware issue. Had similar issues with nexus 7 (2013) that many people believed to be a grounding issue, although I'm not sure where it may be.
[ONE General] rkuijpers:
I do have these touch problems on my OPO, most of the time.

Only thing that helped me making my phone useable, is Franco kernel (version 33 at the moment). Using franco kernel makes the phone useable with almost no touch glitches.

So only one kernel to choose from for me at the moment. With all other kernels I ran into ghost touches as soon as the phone got a little warm.

And now I'm trying to figure what is the smartest thing to do, RMA the phone, or just keep using franco kernel and enjoy my otherwise errorfree OPO?

As I read it takes about 4 weeks from sending in the faulty phone, to receiving a new one. That's not an easy choice for me, as I don't have another phone that I can use in the meanwhile.

Fixing it myself is not an option either, as my hands simply aren't steady enough.

Choices, choices... [emoji37]
[ONE General] fgaurano:
An announcement from OnePlus. :)

https://forums.oneplus.net/threads/touch-screen-issues-were-listening.186829/
[ONE General] Chad_Petree:
Oh wow ,that's Great news ! I wonder what they will do now

Gesendet von meinem Nexus 5
[ONE General] vantt1:
Deny it.
[ONE General] memphian:
This. Although I love the phone. Let's face it. They aren't making enough profit off of a phone sale to be able to swallow this cost of a mass rma .
[ONE General] ek69:
Looks like pretty much this

From one plus one forums

https://forums.oneplus.net/threads/touch-screen-issues-were-listening.186829/

There is a video at the post that supposedly shows 10 touches being registered. But it shows the number 10 before the guy even touches the screen?? Is that how the app is supposed to behave? I thought it showed the touches as you did them in real time... Hmm...
[ONE General] S M G:
Now this is what XDA forums is all about. Great job man !
[ONE General] AcmE85:
This app has been used for testing:

https://play.google.com/store/search?q=multi touch&c=apps

The number shows the maximum amount of simultanious touches which has been registered previously.

It stays this way, even if you restart the app or even the device.

There's an option to "reset touches" which resets the counter to 0 if you restart the app afterwards.

So the app works as intended.
[ONE General] beastlykings:
I just use the "show pointer location" option in the developer options menu, shows that number of touches in the top right corner and I don't have to install any apps ;)
[ONE General] ek69:
Either way looks like they are denying any issues in their end lol

I wonder if the device they were using is the older tpk display or newer wintek display...

Newer display wouldn't have any issues I imagine
[ONE General] Teio:
I only have the touch issue when I have slightly longer nails (I'm a professional musician), then when I am sliding my finger along the screen, my nail touches the screen rather than my finger, then the sliding breaks... Specially annoying when using Swiftkey or any slide to type keyboard...

This is issue doesn't happen on my HTC One m8 or my wifes Note 4...
[ONE General] P1an:
Hello, I have used this guide to fix my grounding issue http://xdaforums.com/oneplus-one/general/repair-guide-oneplus-one-disassembly-t2979351

Everything went fine exept I could not use two laywers of 3M tape (1mm and 3mm)

But I used one laywer and that went very well.

With two laywers I was not able to get the display in to the mid-frame .

And I put electric tape to isulate the digitizerflex just like the pictures.

But it did not do any diffrence, the phone still has the same grounding issue.

Does anybody have any tip on what I should/could do?

Thanks /P1an
[ONE General] vantt1:
Did you test the screen without it installed in the chassis? And does your issue escalate with heat? (i.e. warmer phone = more prominent issue)
[ONE General] P1an:
No I did not. It seemed hard to do from the pictures in the guide.

Yes it does, home in Sweden (cold) my phone works pretty okey, maybe a little bit better after the teardown.

But I was on vacation in Egypt like (30-35 C) about 1 mouth ago and over there it was terrible.

Before Egypt i did not have any problems.

I have tried having the phone in the bed and under a cover at home so it gets like bodytempreture and then I have more touch issues. (This was before the disassemble)

I tried the same thing now but could not replicate the problem.

Now it's just semi bad all the time.
[ONE General] vantt1:
Try putting tape on the back of the LCD (along the left, right and top edges) such that it is insulated from the chassis too. If that doesn't help, then the digitizer itself may be faulty :(
[ONE General] nazfalas:
I replaced my brother's screen before and the new one neither had the copper insulation nor additional insulation on the display flex cable.

(it is working fine, btw., he never had touch issues, though. Was the ~$70 part from aliexpress)

And as was the case with my insulation fix today: does not fix the touch issues.
[ONE General] nhshah7:
okay after half a day's use, I do have to say it's much improved. I'm using swiftkey now and don't notice any issues with swyping over dead spots or having unresponsive keys. Occasionally when I'm typing, I'll have a weird glitch here or there like what I used to get before. This may just be placebo, but I haven't gotten pissed at my phone yet today, which happened several times daily before flashing their "fix" (aka 44S) then upgrading to the newest version of 12S. There may also be a hardware component to this, but as of right now, it definitely feels improved.
[ONE General] nazfalas:
Gently heat the front of your device with a blow dryer and see if the issue gets worse. No danger in doing that in moderation.

BTW

Went back and isolated even more parts -> no improvement.

As soon as the device gets warm multi touch issues reappear.

Also connected the parts without the frame separating everything with cardboard and same behaviour.

Digitizer is very likely to be faulty.

This is, as I have stated before, after more than 7 months without issues.
[ONE General] Gryfter:
Hey guys. Been trolling these XDA threads since my gnex days and now with my OPO that was manufactured in Feb 2015. My touchscreen sensitivity is also garbage with heat so I requested an RMA. They sent me a ROM to flash that I didn't even try after finding others had tried it with no luck. I sent one plus videos of my issues and we had a team viewer session that I was stood up on. They then didnt email me back for 3 weeks.

Just yesterday they sent me a file that I haven't been able to find in the search function. Its called OPO-Display-patch.zip and its a 496mb file. I've uploaded it to my google drive and as soon as I've made ten posts I'll link it haha.

Anyone come across this file yet?

---------- Post added at 07:53 PM ---------- Previous post was at 07:31 PM ----------

Sorry......found a new reddit thread discussing the file. It isn't fixing anything. Big surprise
[ONE General] @work:
I may have posted this in here before, but I have had the occasional touch issue. Typically during times when the phone is warm from the CPU, I uber drive and keep it in a cradle in the Florida sunshine very often without issue. Since my first android phone I have had a habit of turning on the developer option that tracks you fingers. Anyways the times I have had issues I noticed that android still recognized my finger taps but the OS was not responding. Seems to me like a software issue?
[ONE General] djbenny1:
I haven't submitted an RMA yet but I've been experiencing the touch issue for about a month after leaving my phone in a window sill for a few hours.

I flashed the fix ROM someone else linked to in another thread which put me back to 4.4.4 last night. Since then I've gone on to flash all the OTAs and now I'm on the latest OTA 5.0.2 with no touch issues since I flashed last night.

Very early days but if you really can't be a*sed with the prospect of RMAing, I wouldn't rule out flashing their fix as a last resort (and obviously leaving it for at least a few days).

I'm completely stock now other than rooting and flashing TWRP. Antutu scored me 49.5k if it matters.
[ONE General] Genericxx:
Since the last couple of weeks i've discovered some kind of touch issues, especially after carrying the device in the pocket. In 90% of the cases, after taking it out of my pocket, screen is more than unresponsive. I'm usually not able to swipe to unlock in an easy way, which is a single-touch-gesture. Takes usually a couple of attempts. After a time this behaviour acclimates itself. A reboot does the same but is mostly not neccessary. I've thoght that this could be caused by Proximity-Sensor and some softare related fooked up stuff, maybe the applied tempered glass could play a role also? All tests are done with different ROM. Official Cyanogen OS, different unofficial nightlies with custom firmware, official nightlies and aosp-based ROM, so i can exclude Firmware/ROM-Related culprits.
[ONE General] vantt1:
A faulty digitizer was something I hadn't really considered, but after a few users are having issues even when the screen is isolated, it seems like it should be noted.
[ONE General] marwan91:
I have to confirm this, just heated my screen a little with a hair dryer. And the screen became unresponsive. Looks like is really a faulty digitizer, and i will have to get new one before the hot days come.