yashsingh1/xdaforums huggingface dataset:
[T-Mobile LG G3] Emu:
Alukrad, in my experience and from testing a bunch of things... my goodness. This Dirty Unicorn kernel is the greatest kernel I've ever encountered. Gah! If only it was standalone. Doesn't matter. No need for aCC kernel. This one does way smoother.
[T-Mobile LG G3] Alukrad:
Beastly isn't it? :D I still like to overclock so I have two DU versions saved. One with stock kernel and one with aCC when i need power. The beauty of backups lol.

PS. There's a way to harvest kernels from ROMs :x
[T-Mobile LG G3] Zyker019:
Will do. I just need to find the time to do a full wipe again

How do you harvest kernels? Is it as simple as saving the settings in kernel adiutor?
[T-Mobile LG G3] Emu:
Nah, no need to harvest. What would be nice is if the DU kernel had more governors and more hotplugs.
[T-Mobile LG G3] Alukrad:
Ah, not gonna happen since it's already smooth on stock settings. Which I'm never gonna complain about. But yeah would be interesting to see what this kernel could do with a few other bells and whistles
[T-Mobile LG G3] zzulanas:
New to rooting and ROMS and the such, so is it normal to have your phone restarting over and over again? Not like a boot loop, like I'll be able to use my phone for a while, and then my phone will just restart, for no reason, usually when I'm in snapchat and/or textra. I've tried running another MM ROM (BlissPop) and the same thing was happening, does anyone have any solution to this? Or any idea as to how to help?
[T-Mobile LG G3] Alukrad:
Did you wipe EVERYTHING before you installed DU? (Factory wipe/advanced wipe-system data cache dalvik cache)
[T-Mobile LG G3] johnb380:
When the reboot happens save the last_kmsg and upload and post the link here. It will help the devs to figure out your issue. Maybe get a logcat too.
[T-Mobile LG G3] Emu:
I used to have that issue... but it magically disappeared. What kernel settings do you have? Any mods, anything from Xposed?
[T-Mobile LG G3] zzulanas:
I did the wipe under TWRP, didn't check anything special, I can try wiping with the dalvik cache and data cache.

---------- Post added at 04:36 AM ---------- Previous post was at 04:32 AM ----------

Alright, where would I find the last_kmsg and logcat?
[T-Mobile LG G3] marcdw:
[MENTION=7242074]zzulanas[/MENTION], you said the reboots happen even with another ROM? Can you try using the phone awhile with the charger plugged in and see if it also happens.

If it's not ROM or kernel it could be the battery but I want to make sure.

LG G3 D851, BrokenOS MM ROM, Tapatalk 4.9.5
[T-Mobile LG G3] zzulanas:
[MENTION=6046143]marcdw[/MENTION] Alright I'll try that, and update on the working status, phone still reboots for no reason constantly, and sometimes it will get stuck in a boot loop for maybe 5-6 boots. And now for some reason I can't receive text messages, I'll be able to send them but I won't get the messages until hours later (tested this by texting someone directly next to me).
[T-Mobile LG G3] zzulanas:
Okay so the phone seems to work fine and boot okay when I have it plugged in, does that mean it's a battery issue? And if so how can I fix that?
[T-Mobile LG G3] marcdw:
Yep, sounds like battery. With a full charge it kept happening to me last year so I had to keep it plugged in. A coworker was suffering from that last week (stock, no root). I let her have one of my batteries and all was well. Then I ordered another Anker battery double pack w/charger (still a steal at Amazon).

In the OctOS Hangouts group this issue also popped up.

Getting new batteries is one fix.

Some folks, however, mentioned that the OEM battery can be just loose enough that it can lose "connection". Word has it wedging a piece of paper or something below the battery to keep it "tight" has actually worked. I never got a chance to test that before discarding my old battery.

LG G3 D851, PAC-MAN ROM, Tapatalk 4.9.5
[T-Mobile LG G3] zzulanas:
Alright so I think it's not battery as it only restarts when I start certain apps, but then it gets stuck in a boot loop and I have to go into recovery to boot it, WHILE IT'S PLUGGED IN. I did a full data format, new clean ROM install, and nothing changed.
[T-Mobile LG G3] marcdw:
Oh I see. Looks like now we deal with what apps those are and what they have in common.

There are so many variables. The one guy using OctOS got his new batteries but says the problem comes back. Someone mentioned possible thermal issues.

You might have to find a way to get some kind of log if possible.

LG G3 D851, PAC-MAN ROM, Tapatalk 4.9.5
[T-Mobile LG G3] Zyker019:
I finally reflashed DU and reproduced the defect with the stock kernel. Here's a log

http://pastebin.com/GmpkXfUV
[T-Mobile LG G3] nitin.chobhe:
Thanks for the log but I'm not getting much information from it :(

Are you using any theme? I see this entry in log "com.resurrectionremix.pitchblack". What is that?
[T-Mobile LG G3] Alukrad:
It's a theme Nitin. The original RR theme.
[T-Mobile LG G3] Zyker019:
Yeah, that's a theme. I'll post a lengthier log when I get the chance. This one was quick and short because I had to go to work. I still have that bluetooth bug too, I'll post that one as well
[T-Mobile LG G3] nitin.chobhe:
I built a new build today and waiting for testers to test it.

If you want I can link you to that build :good:
[T-Mobile LG G3] callmeshulah:
I can test it
[T-Mobile LG G3] Zyker019:
Yes send the link my way. I'd be happy to test it
[T-Mobile LG G3] Andrewoidd:
I'll be willing to test it. Was going to go back to the first build anymore so mine as well see how the new one fares
[T-Mobile LG G3] Alukrad:
Link it man. What's the good word :)

Edit: I found it in AFH like usual hehe >.> download and testing
[T-Mobile LG G3] nitin.chobhe:
So here is the new build where everything works:

Download link: https://www.androidfilehost.com/?fid=24459283995317027

Changelog:

- Synced with latest DU sources

- new features like breathing notifications (and many more)

- April security patch in

You are too fast. Generally I do not post a link if it is not tested :o

Nitin
[T-Mobile LG G3] nitin.chobhe:
Thanks [MENTION=5126285]odpm1977[/MENTION] for testing the build (as always)

I appreciate that man!

Nitin
[T-Mobile LG G3] odpm1977:
You're very welcome man.:cool:
[T-Mobile LG G3] Alukrad:
Did rapid charge get removed in this new build?
[T-Mobile LG G3] gunner05:
Great... my screen is stock on boot animation. Clean install after full wipe. Been over an hour now... should i reboot?
[T-Mobile LG G3] Alukrad:
Yep. It should only take 10 minuets to boot
[T-Mobile LG G3] gunner05:
Weee back to normal! after reboot, was afraid I bricked it somehow :)

When restoring from titanium backup, should i restore android id ? that's what its asking me. restore id or keep same one. Wonder if anyone know the best answer
[T-Mobile LG G3] nitin.chobhe:
May be du removed it. Please check their gerrit
[T-Mobile LG G3] Alukrad:
Where do I find this gerrit?
[T-Mobile LG G3] marcdw:
Probably late reply but...

For me, if it asks then I say yes, restore id. That should guarantee the data gets restored properly.

TiBu has never asked me that question on an MM ROM. Prolly 'cause backups are made on LP. Anyhind, you should be good to go.

LG G3 D851, PAC-MAN ROM, Tapatalk 4.9.5
[T-Mobile LG G3] nitin.chobhe:
HEre: http://gerrit.dirtyunicorns.com/#/q/status:merged
[T-Mobile LG G3] Zyker019:
TiBu gave me problems coming from LP backups. TiBu also wouldn't let me restore my android ID. I've always clean wiped between different ROMs
[T-Mobile LG G3] Alukrad:
Looks like it's still there.
[T-Mobile LG G3] marcdw:
Yep. After flashing a new ROM I download Device ID Changer, change the ID to the one I always use on KK/LP ROMs (written down but also saved in Google Keep for cut/paste), reboot, then setup TiBu to locate the backups.

Apps and their data then restore properly, via the app or an update.zip.

I go through this all the time. Part of the setup ritual. MM's new storage paths just broke everything. Reconfiguring apps to find their external data, etc. And I thought KitKat's read/write issues back in the day was a pain. ?

LG G3 D851, LiquidDark ROM, Tapatalk 4.9.5
[T-Mobile LG G3] gideonlfc:
Status bar slide to adjust brightness ain't working in the latest update
[T-Mobile LG G3] portillodesign:
Can't install Adobe's apps

I dont know why, but when I try to use any AOSP or CM ROM I cant install any Adobe app, as Adobe DRAW or Adobe Capture CC.

Just dont show on Google Play app and on GooglePlay web it shows that my smartphone cant install this app.

It works on Chroma, no Nexus 5 that is AOSP. The problem is only on LG G3 non-stocks.
[T-Mobile LG G3] Alukrad:
That has alot to do with your screen DPI. Some apps can't be installed if a certain DPI is applied. Check stock settings and apply.
[T-Mobile LG G3] portillodesign:
Thanks, but it doesnt Work

Unfortunately, it doenst works (640dpi). Just shows that my device cant support this version.

[IMG="Screenshot"]https://lh4.googleusercontent.com/-JZ0iCi79Uz4/VxAEp98_cfI/AAAAAAAAlTY/iG7FMxhGHfs-rkFGRk_D0OEzokjqxBOAQ/w464-h824-no/Screenshot_20160414-185433.png[/IMG]
[T-Mobile LG G3] marcdw:
[MENTION=4292163]portillodesign[/MENTION], yeah, I get the same thing. I suppose you're best bet is to see if there's a downloadable apk of those apps. Maybe check apkmirror.

LG G3 D851, PAC-MAN ROM, Tapatalk 4.9.5
[T-Mobile LG G3] CrucialBT:
Anyone else having an issue on incoming calls where the screen turns on, then turns right off again and there's no waking it until the phone stops ringing? At the moment, I have no way of answering the phone unless the screen is already on.
[T-Mobile LG G3] Alukrad:
Nope, mines working normally, maybe your proximity sensor is not working right?
[G4 Q&A, Help & Troubleshooting] deppiedave64:
Dear folks,

today I ran into a problem while trying to root my new LG G4 (H815).

It seems I succesfully unlocked my bootloader since it writes "BOOTLOADER STATUS: UNLOCKED" at every startup.

Now I tried to install TWRP recovery; I downloaded the newest version for my device from the official TWRP website.

I used the following command:

fastboot flash recovery twrp.img

I got the following output:

target reported max download size of 536870912 bytes
sending 'recovery' (31620 KB)...
OKAY [ 0.923s]
writing 'recovery'...
OKAY [ 0.303s]
finished. total time: 1.226s

Then I left fastboot via

fastboot reboot

.

But when I try to boot into recovery mode via

adb reboot recovery

I just get a picture of a broken android figure with a red triangle over its chest.

When I use the hardware key combinations and then answer "YES" it simply does a default factory reset.

I'm using elementaryOS 0.3 (based on Ubuntu Linux). I already tried different ways (with or without sudo, using the adb version which comes with the full Android SDK or the version featured in the Ubuntu repositories).

Nothing seems to work...

I hope I described my problem right and you can help me.

Thanks for all replys and greetings from Germany.

EDIT:

I now got into recovery using

fastboot boot twrp.img

.

From there I installed stock-20a-rooted.zip. That seemed to work. But when I boot the phone normally it just shows me the LG logo forever and doesn't boot into normal os. Only removing the battery gets it off again. Factory reset doesn't help either.
[G4 Q&A, Help & Troubleshooting] DerPedde:
I would suggest to put a copy of the TWRP recovery to your sd card. Then simply boot into the recovery via the command: "fastboot boot twrp.img" and then flash the copy of the recovery from sd card permanently via the so far only booted but not permanently flashed recovery...good luck! ;)
[G4 Q&A, Help & Troubleshooting] deppiedave64:
I did that but now I get a bootloop while starting the normal os. Factory reset doesn't help.
[G4 Q&A, Help & Troubleshooting] deppiedave64:
Update: When I connect my device with my PC while the bootloop is active, sometimes a Window pops up on my desktop asking for my PIN to unlock it. When I enter it nothing happens.
[G4 Q&A, Help & Troubleshooting] DerPedde:
Ouch...corrupt twrp.img file?

---------- Post added at 12:49 PM ---------- Previous post was at 12:42 PM ----------

So maybe its best to start all over again...get into download mode via holding volume up and Power on. Then install original kdz via LGUP tool. Maybe you have a look at the german Android Hilfe forum, there are also the kdz files for download. Good luck!
[G4 Q&A, Help & Troubleshooting] deppiedave64:
Maybe... While in TWRP it looked like always...

EDIT:

Yes, I'm just downloading the KDZ files... Gonna flash it today. However, Thanks for your support!
[G4 Q&A, Help & Troubleshooting] deppiedave64:
I just succesfully installed autoroot kernel, flashing kdz was the solution. However, I still can't write TWRP into recovery partition, but at least I got what I wanted. ;)

Thanks for your support!
[G4 Q&A, Help & Troubleshooting] azZA_09:
you can write twrp by using twrp manager from playstore(2.8.7.0) then when you're IN recovery flash 3.0.0.0 (download from official twrp site or from orginal android development of LG G4) or use in adb fastboot boot (recovery).img
[G4 Q&A, Help & Troubleshooting] 88astro88:
HELP!

Hi everybody. I'm a newbie in root, xda and forums in general, so please don't shoot me and help me if you can..

I rooted my lg g4 te first time thanks xda, but after having installed nougat via twrp, root is missing in any check, and twrp can be installed but not launched in fastboot. I tried EVERY guide i found in xda, but that famous command "fastboot boot something.img" is still not working... any idea?

Thanks
[One (M7) Q&A, Help & Troubleshooting] DomiiiNo:
I just installed NuSenSeven on my phone and now it won't boot, it's in a boot loop. It's freaking hot and I don't know what to do.. I need help FAST.. did I kill my phone?
[One (M7) Q&A, Help & Troubleshooting] bomil:
Hold power button 15 seconds and it should reboot. It will take some time to start. You should update your firmware first to avoid problems with boot.
[Android Q&A, Help & Troubleshooting] Adreno306™:
Hello XDA,

I have a problem.

When I want to flash my ported ROM (via android kitchen), TWRP 3.0.0-0 says: "Update process ended with signal: 11".

How to fix it, please? :crying:
[Android Q&A, Help & Troubleshooting] ChinmayXD:
same here brother i too got d same error while flashing stock rom flashable zip of my device which is moto g turbo edition plzzzz help :(
[Android Q&A, Help & Troubleshooting] ROM-mer:
SAME! Its so annoying bro. I worked hours to port, and now, it dont work. urghh :crying:
[Android Q&A, Help & Troubleshooting] AndroidFL:
downgrade the recovery maybe at least thats what im gonna do because i have the same issue
[Android Q&A, Help & Troubleshooting] budm:
did that solve the issue? I'm running into this issue myself
[Android Q&A, Help & Troubleshooting] AndroidFL:
sadly, this didnt work for me
[Android Q&A, Help & Troubleshooting] Vlk Is My Name:
Any1 know how to fix this? I've got the same problem.. " update process ended with signal 11 "

:crying:
[Android Q&A, Help & Troubleshooting] pijussimke123:
Omg i worked 6 hours on porting rom and it says signal 11?????
[Android Q&A, Help & Troubleshooting] FitseMan:
Updater_script issue

fix your updater-script, i used my PORT ROM updater-script to bypass the issue, the original,
[Android Q&A, Help & Troubleshooting] z3r0c00l_2k:
downgrading the recovery solved my issue.
[Android Q&A, Help & Troubleshooting] alakiname:
Downgrading the recovery also solved my issue.
[Android Q&A, Help & Troubleshooting] osijekweb:
can you help me how to do that?

when I put another TWRP doesn`t work on oukitel k6000 pro
[Firefox OS General] @novski:
Hi, im in need of some help with my phone.

Im no Programmer but managed to build a bootable version of Firefox OS on my Fairphone 2. It boots smooth but the proprietary blobs (drivers) seam to not communicate with the OS so im in need of somebody who would help me debug that hardware bindings. I think it should be able to do that over a remote connection from anywhere... The blobs are available here code.fairphone.com and the problem is that whether Wifi nor LTE has a data connection although i can receive and make calls without problems.

Is there any interested man who knows Firefox OS enough to debug it?

Regards, Novski
[Firefox OS General] @novski:
im also interested in a payed solution...

offers are welcome.
[Firefox OS General] hashroot:
i can try to debug your device

PM me
[Galaxy S6 Accessories] Kyochin:
Does a S6 edge case fit for S6?

There is a nice leather backed case but somehow it's only available for S6 edge.
[Galaxy S6 Accessories] mykehdoom:
No the Edge is thicker than the S6. So the case wouldn't fit properly..
[Galaxy S6 Accessories] Kyochin:
That's a shame, thanks.
[Nexus 6 Q&A, Help & Troubleshooting] sandercutcher:
well, speakerphone mode in stock dialer - works is normal (top speaker only to conversation and bottom speaker to mic)

but in whatsapp and skype works is two speakers at the same time, and because of this, my interlocutor hears himself

how to fix this ??
[Xperia Z5 Compact Q&A, Help & Troubleshooting] mcmanuf:
So some of you with white Z5 compact phones might have had this touch sceen bug with repetitive key presses and unstable touch screen behaviour bug which was previously "fixed" by a software upgrade:

http://www.xperiablog.net/2015/10/21/white-xperia-z5-compact-touch-screen-fix-arriving-next-week/

Lo and behold. This bug is back in MM, and there is another guy in the thread which I can see also have the bug come back :(

It is not always there, but sometimes its just there. I dont know what triggers it. A restart seems to help until it comes back again.

For those of you not familiar with this bug, it usually shows by repetitive touches, and highly unstable touch screen.

For example when i press the key "s", it usually put in "sssssss" like i have pushed that key 5-6 times.

Also the bugs shows, when for example you are scrolling in facebook/internet, it will not let you scroll. Whenever you touch the screen, it will enter, whereever you lay your finger on screen.

Lastly it also shows by the screen becoming completely unresponsive when you press anywhere.

I have clean installed MM and restored my apps via Sony Backup/restore app.

I am so pissed how a phone color (white) can somehow decide the behavior of the phone touch screen, and I believe sony is hiding something.

In the beginning I was thinking that maybe they made different builds for the different Z5 colors, so they might not have included the "newest" touch screen drivers for at launch time for the white version.

But the same bug appearing AGAIN in MM i have a very hard time understanding that should be the case that it was a software bug. I believe there are some hardware bug, they have somehow omitted by a software circumvention, and they forgot to add it to the white version for the MM launch.
[Xperia Z5 Compact Q&A, Help & Troubleshooting] Phidye:
Personally I have always had a problem with the "return" key when the phone is placed. Patch or not, this button works once out of 10.

For information, I just bought this phone. I also think there is a hardware problem. This is average for a manufacturer like Sony. :( I thought for a moment it back in service but when I see the number of dissatisfied with the service Sony in France, I preferred to keep my phone in the hope that a solution comes a day. We have the right to expect in my opinion ... :mad:
[Xperia Z5 Compact Q&A, Help & Troubleshooting] mele80:
I did clean install via flastool also and i have/had this problem. Yesterday i did software repair via pc companion and restores apps after that and so far problem has not occured.
[Xperia Z5 Compact Q&A, Help & Troubleshooting] Phidye:
I also made a repair with PC Companion but nothing changed.
[Xperia Z5 Compact Q&A, Help & Troubleshooting] mcmanuf:
So there are other people here with this annoying problem.

You all have a white xperia yes?

This bug is so annoying I feel sometimes like tossing the phone into a wall.

If there was an alternative to this phone in this form factor and specs, I would have bought it yesterday.

But unfortunately there isn't
[Xperia Z5 Compact Q&A, Help & Troubleshooting] hipsterfont:
It's a poor ground connection from the digitizer most likely. You can replicate this "bug" on any device with a bad USB charger. I had a charger that would cause my Nexus 7 to detect random touches.

The software fix was likely adjusting the voltage threshold for touch events to be considered actual presses. It was likely forgotten about when they updated and just needs to get readjusted again. Too bad we don't have the ability to adjust the threshold ourselves in developer options :(

That being said I have a white z5c and I've only had this "bug" happen once and I just chalked it up to me being plugged into the wall and didn't think much of it. I use my phone constantly too.
[Xperia Z5 Compact Q&A, Help & Troubleshooting] mcmanuf:
Interesting theory. Do you think it is likely that this issue only occurs for one phone color (WHITE), and then only for some whites.

The assembly line for the phones should more or less be the same, no mater the color.
[Xperia Z5 Compact Q&A, Help & Troubleshooting] Pepp-elito:
I also have Sony Z5 compact white version which had the touch problem from start. Now after the Marshmallow update its back. As said above, it could happen while browsing (or on home screen) e.g. Entering links instead of scolling i.e. It triggers multi click. In these situations all menu keys will also be none responsive. Its starts acting normal again after a quick push of the power button, i.e. puttning the screen to sleep.

As a former developer for mobile software, both for apps and the android platform, i thinking i would agree with the above conclusion that the problem is hardware based, and not due to a difference in the delivery software version, as i was hopping. So the question is; will this always be a problem for these versions of Z5c white, i.e. they are forgotten in new builds?
[Xperia Z5 Compact Q&A, Help & Troubleshooting] thimmey:
Unfortunately I'm having the same problem with my white z5 compact...
[Xperia Z5 Compact Q&A, Help & Troubleshooting] albenex:
it happens that for different colors are used different materials.. probably white ones have different properties..

i can confirm that using bad cable/chargers this kind of bug happens with every device, with random touches and impossible scrolling.. if you have a well-known bad adapter and you note no differences with your white z5c, that's definitively the answer..

i think sony should recall all white z5cs and replace them with newer or different release
[Xperia Z5 Compact Q&A, Help & Troubleshooting] Phidye:
What revision of compact Z5 are you? Personally I have a revision 3 (that is written on the box).

I also had a touch of problem before moving to the latest version of Android (6).
[Xperia Z5 Compact Q&A, Help & Troubleshooting] tadei81:
My girlfriend also bought white Z5 Compact and funny thing... I put the Panzer Glass on the screen and guess what? Sometimes she can't turn off the alarm clock in the morning and sometimes navigation buttons are not responding. I tried then without the screen and it works without a problem. I am not sure if this is a problem with Panzer glass or sony's bug.

I have Z5 and have no problems, but mine is black edition :)
[Xperia Z5 Compact Q&A, Help & Troubleshooting] ket_kul:
Mine is z5c white version as well. The bug started again on MM

And the bug quite annoying.

I bought it on updated lollipop.

And never had this problem before.
[Xperia Z5 Compact Q&A, Help & Troubleshooting] civicsr2cool:
This plus Bluetooth is really making me hold off on not moving up from .200 lol