yashsingh1/xdaforums huggingface dataset:
[G2 Android Development] ckyy:
I think it's hilarious. I open the camera app, take a single picture and suddenly theres this annoying line. And i checked my temps right after it appeared. Both CPU and battery were at about 40 degrees. The phone wasn't even warm.
[G2 Android Development] chrisexv6:
I believe the cause has been tracked down to the ribbon connector to the LCD screen. It either gets loose or breaks internally or something. Another kernel dev (amperific) was actually able to fix his phone. And autoprime had a bone stock phone show permanent lines when he rebooted (the phone was warm from running adb)

If your lines go away I would guess its loose. My lines did not go away (tried the pixel fixer, etc), so Im guessing something fried it since it had coincided with a bootup having the tearing LG logo and then the bootup after that had the lines and the LG logo was missing completely except for a few red pixels.

I wasnt the only one to have this issue on that build of AICP (wasnt even using Renders kernel) but most people didnt get permanent lines like I did. The dev later said they tracked down what might have caused it and undid it (it was an upstream change from CM). The tearing logo seemed to be from ondemand being the default CPU governor....I think my phone was just at the right temp/age/circumstances to have the lines show up along with the tearing logo.
[G2 Android Development] 1ceb0x:
i have these lines now on my phone :( awaiting for the service center to get the parts... i often ask myself if it would be better to just stay bare stock but then again, I'm an AOSP *****... knowing me, i will restore my LS backup once they fix it.

feel sorry for everyone that has these problems. lg g2 is a beast of a device, too bad they used such a bad quality part on something such important like the connector between the motherboard and the display.

Namaste! Sent from Orion Galaxy.
[G2 Android Development] ckyy:
Looks like i have to repair mine to. Anyway..patiently waiting for r19. :)
[G2 Android Development] bgx:
Me too must repair! After flashing dorimanx and back to render stuck in bootloop and after reflash mahdi with render got that black lines. Hope somebody will find out the reason why this happens. I don't blame the devs, think must be a reason like heat in the booting phase or something else.
[G2 Android Development] markjh:
Well FML, I got the black lines too now...

Gesendet von meinem LG-D802 mit Tapatalk
[G2 Android Development] ckyy:
Where did you get your phone? Telekom?
[G2 Android Development] Raagh:
Dont worry i can wait till you release R19 and make an stable branch so i can follow it :).

Yeah i saw it, i thinkg i ll have to place that in my lge g2-common folder.
[G2 Android Development] RenderBroken:
It really does suck. Luckily my phone has been rock solid. It is a referb but with a brand new screen. I bought it off ebay and cant be happier. I feel for you guys. It really bugs me. So lets have some good news!

I have FINALLY been able to fix the weird screen glitch on bootup before the rom boot image.

Solution:

Re-mutha-f'n-base the kernel again using Savoca's source for time savings. His base is newer (I think) than SimpleKernel's. I am literally using the EXACT same commits yet the issue is now gone. Whatever. I really hate the fact that the source for each variant is so different but at least I have been able to fix the problem. I was tired of chasing my tail yet again. I am pretty happy with this new build and it has been completely smooth. No reboots either. I will build for all asap. It may be tomorrow before I can though. Just thought I would share!
[G2 Android Development] Raagh:
Amazing news i cant wait for it. When you do could you tell me which branch ll be the correct one?

Also. Inside you ramdisk repo there re 2 folders. Ramdisk and ramdisk_aosp. Do i need both?
[G2 Android Development] midan:
RenderBroken :Thank you for your constant commitment in solving the problems of our users
[G2 Android Development] markjh:
Nope, Vodafone

Gesendet von meinem LG-D802 mit Tapatalk
[G2 Android Development] Matze060906:
Is it under warranty?
[G2 Android Development] ckyy:
Guess they got the same batch of **** then.
[G2 Android Development] midan:
Which?
[G2 Android Development] RenderBroken:
Uploading new build: R19!

I will have to update my Github later . . .

Things to note:

Enabled Retention Sleep state. This does not seem to be the cause for the reboots. Another sleep state that has been removed was

Overhauled Interactive and Ondemand

Interactive just keeps the phone running as smoothly as possible while still being conservative with its battery use. Using this has removed any audio issues I had before!

Fast Charge re-added!

Added Quick Wakeup to handle small jobs without completely rising out of the suspend cycle prematurely. Not really sure how much this will benefit battery life so you tell me!

Just plain smooth!

I am still building for the rest so please be patient. I may not have enough time to build all tonight.
[G2 Android Development] ckyy:
Has that battery thing been added that was linked yesterday ? :0
[G2 Android Development] RenderBroken:
It has been already added a long time ago. Also note that you WILL HAVE TO wipe both caches before booting. It just won't boot till you do.
[G2 Android Development] ckyy:
Just flashed it a few seconds ago. Didn't wipe and it still booted. Maybe i'm just lucky.

Edit : I'm amazed. Tapatalk barely stutters anymore.
[G2 Android Development] Matze060906:
I don't know who it was, but someone here in this thread said: you don't have to wipe cache and dalvik by flashing kernels. I flashed all your builds since R5 without any wipe. Could this be the reason for the reboots?

Btw: R19 for D801 have 12mb and D802 have 11mb. Is this Ok?
[G2 Android Development] bgx:
Yeah its ok. Flashed and running fine!
[G2 Android Development] RenderBroken:
I had to wipe caches to boot. Just keep in mind that this is going to be a test build. There may be issue so please let me know if there are any. Thanks guys.
[G2 Android Development] bgx:
Hey Render! When I try to open the misc task in faux clock it fc. Have tryd to delete app data but after that the same.
[G2 Android Development] ISISTYLE:
Bootloop on liquidsmooth :(
[G2 Android Development] Matze060906:
Which device do you have? Did you wipe cache and dalvik after flashing?
[G2 Android Development] RenderBroken:
Can you get me a logcat?

My issue was with liquid as well. I may need to make more adjustments for it.
[G2 Android Development] ISISTYLE:
No prob mate take ur time!! Well i made a full wipe and didnt backup rom in 3 days lel.
[G2 Android Development] 93fuelslut:
I'm a bit lost. If im vs980, I would go to

Kernel> releases> vs980 8-30r17

And not

Kernel > betas> vs980 hotplug test ?

I've been on stock ROM so its been awhile

sent from your moms phone
[G2 Android Development] blacklight1025:
You'd go into releases and old for now. He hasn't built the latest one he was talking about for the VS980 yet.
[G2 Android Development] 93fuelslut:
Do I need to wipe cache and dalvic b4 I flash? I usually dont, but a member said he did

sent from your moms phone
[G2 Android Development] blacklight1025:
I would just to be safe. I've never flashed a kernel without wiping the caches. Render, himself, said to with the new build coming up.
[G2 Android Development] 93fuelslut:
What set up do yal recommend for battery life?

sent from your moms phone
[G2 Android Development] RenderBroken:
Default setting work pretty nice but since it is my mom's phone, you probably need to the phone on the ground as hard as you can. ?
[G2 Android Development] blacklight1025:
Yea default settings are great for me, the only thing I change is the multicore power savings to 2.
[G2 Android Development] 93fuelslut:
Hey as long as she's able to text me back :D

sent from your moms phone
[G2 Android Development] cortex69:
OC it to 2.8 with some crazy gov on core max frequency . And cooling. Nitrogen should do
[G2 Android Development] glacies:
Flashed and working fine on Alegen. Using default settings for now.

Will underclocking to 96 MHz provide additional battery life?
[G2 Android Development] RenderBroken:
Technically yes. Is it worth it? Thats for you to find out. It may cause issues.
[G2 Android Development] count_martin3z:
Liquid r19 and d802. So far so food. Even better :)
[G2 Android Development] blacklight1025:
Yea, the new kernel runs great! No tcp congestion control or is it just me?
[G2 Android Development] 1ceb0x:
just you.

Namaste! Sent from Orion Galaxy.
[G2 Android Development] blacklight1025:
I meant congestion control lol :p my bad
[G2 Android Development] 1ceb0x:
Yeah.it is not available. Render rebased the kernel again on Savoca's kernel so he might missed it. nice find!

Namaste! Sent from Orion Galaxy.
[G2 Android Development] blacklight1025:
Ahh true, I forgot he said that! The kernel runs so well, I don't know if its really necessary at the moment.
[G2 Android Development] Lazy79:
[MENTION=5438598]RenderBroken[/MENTION] kk-rebuilt is the latest branch with the rebase and so on? I tried to build the kernel (d802 defconfig) but I received some errors while building (bluetooth). May I ask you via PM about such things because I am lost. I cannot find anything related to the error message online via google and so on.
[G2 Android Development] bgx:
Here's the logcat.
[G2 Android Development] glacies:
Just had an sod with r19. All settings default.

Installed and saved logcat with catlog. Hopefully will be useful.

https://docs.google.com/file/d/0B_swjcDi-9PFZjREcThVUUFlWjg/edit?usp=docslist_api
[G2 Android Development] count_martin3z:
Zach, I had reboot on Liquid and R19, D802. Stock settings. Nothing changed. Phone was charching in my car. Wiped cache and dalvik before and after flash your kernel. Grab the log.

https://drive.google.com/file/d/0B8pbuHYEqowcSXZ1U2hpN3pyWWM/edit?usp=sharing
[G2 Android Development] jeff5347:
Render, where are you hiding the d800 r19, lol. I'm not finding it it folders
[G2 Android Development] RenderBroken:
Sure

Thanks!

Its there. I promise! lol

The reboots are the exact reason why OEMs take the middle of the road approach with software/hardware. I have no issues like rebooting and such, others do. Thanks guys for testing the new build. I have some changes to make for the next one.
[G2 Android Development] bgx:
I also have no reboots with R19 and the speed and battery is really outstanding! Thx for the good job Render!
[G2 Android Development] scottricketts:
R19 gave me a lock on first boot. D801 here.

---------- Post added at 09:51 AM ---------- Previous post was at 09:48 AM ----------

Whoops, forgot on CM11 nightlies.
[G2 Android Development] 1ceb0x:
Cm nightlies are still on 4.2.2 sources if i am not mistaken.. how do you use it :/?

no reboots on R19 for me on Liquid smooth and the experience is damn smooth!

i guess i will keep this build on my phone since Render will re-enable the default sleep states, right [MENTION=5438598]RenderBroken[/MENTION]?

Namaste! Sent from Orion Galaxy.
[G2 Android Development] nfin1te:
r19@slimkat 7.8 - flawless, no problems whatsoever. thanks! :)
[G2 Android Development] jcmaddox1:
Not seeing d800 build for r19.
[G2 Android Development] RenderBroken:
Thanks! Yea I will probably drop Retention just so the few don't have reboots. Also may have to rebase again but remove a few commits before applying them all again. Remember I actually created about 500 individual patches from my local source and then apply them all at the same time using

gitam *.patch

Then just fix the merge errors as it goes.

In my own testing I have noticed a couple errors that could be squashed and make the phone more stable. An issue with cpuidle and mdss. Still I will work through them. I am hoping using the newer source will end up being more stable. Once I get the sleep states worked out that will help greatly. It sux though especially knowing that ALL sleep states work just fine for the N5 using the same hardware. Just goes to show why OEMs and their "skins" really screw with things sometimes. How is it that the N5 is capable of 8 hours SoT but with our bigger battery with can hit maybe 6. I want to bridge the gap. Get to a stable source and work out the extra crap that has been introduced in our source. Granted I am essentially using the Stock source with some Hax to make it work for AOSP. I would love a true AOSP source to work with but it may not be possible. Just for example, phones in Japan (G2s still) need to have a few lines of code in MDSS just to handle their special boot logo or it will throw the whole boot process off. But if I can make it as close as possible, I believe our phones will greatly benefit. I know this kernel has not been the most stable besides a few builds and I appreciate yall taking the ride with me. It will get to a point of constant stable builds and the occasional test builds. We are close now. I just need to squash the few issues I am seeing then we should be good to go. Thanks guys!

It is in the folder in my view. Maybe its not shared for some reason. I will share it again. Thanks for letting me know!
[G2 Android Development] RenderBroken:
fixed
[G2 Android Development] RenderBroken:
Fixed! Not used to this new beta layout lol
[G2 Android Development] scottricketts:
I thought they'd move to 4.4.4 since that's the recommended baseband now.
[G2 Android Development] djdeeles:
[MENTION=5438598]RenderBroken[/MENTION] don't forget this patch :) https://github.com/dorimanx/Doriman...mmit/e3b977d6c25d778c7358820cbbd4d0ad9c0aec5f so we will close to n5 in terms of sot. In r19 this is not included.

Really nice work btw. Keep up good work.
[G2 Android Development] 1ceb0x:
it is included since long time ago. in r19 also.

Namaste! Sent from Orion Galaxy.
[G2 Android Development] RenderBroken:
What kind of SoT are you getting?
[G2 Android Development] RenderBroken:
Actually the changes that Dorimanx made are different than the original commit that this was based off of. I will take another look and apply it in the next build. Thanks for bringing it to my attention! If anyone else sees something helpful somewhere else, please feel free to post it in thread! Thanks guys. I love the community effort here!
[G2 Android Development] Raagh:
hey render dont wont to bother you but, is already a branch i can follow or not yet?

keep up the good work im testing r19 right now :)

edit: another question , did you merged the fm support to your kernel already?
[G2 Android Development] chrisexv6:
Im curious if anyone on Dori's kernel reported better battery life because of the change. Has anyone heard?
[G2 Android Development] arifqur:
Cannot get Seeder app to work after flashing R19 on Liquid as well as latest Mahdi.

Says "Seeder was unable to start the RNG service."

Tried flashing SuperSU but no dice.

Any ideas?
[G2 Android Development] RenderBroken:
Not yet for both questions. I will need to try to rebase one more time before I re-push the branch to its own repo. The problem with updating to Linux 3.4.103 from scratch is there are a crap ton of fixes needed to be made to the source. I still need to group/push them to my temp branch. When I get them where they need to be I will let yall know. Also you are not bothering me. I appreciate the interest!

Well I use Frandom and you have to use a startup script to make the swap. Maybe frandom did not merge cleanly. But I thank you for the reboot and will look into it tonight. I am planning on another release tonight or tomorrow. I will be looking at lowering the clockrates for I2c and the other issues I have made a list about.
[G2 Android Development] arifqur:
My God!

You are an awfully sweet man.

Thanks a lot
[G2 Android Development] RenderBroken:
Its hard work! ;)
[G2 Android Development] djdeeles:
[MENTION=5438598]RenderBroken[/MENTION] torch not working in my unofficial cm11 build.

09-10 22:21:18.685 W/TorchRoot(30756): Caused by: java.io.FileNotFoundException: /sys/class/leds/led:flash_torch/brightness: open failed: EACCES (Permission denied)
[G2 Android Development] NateK:
Just another datapoint. Torch works on LiquidSmooth
[G2 Android Development] pqee:
I haven't been able to get r19 working on LiquidSmooth. Wiping cache and dalvik didn't help. Even tried a clean ROM install with r19 but it still bootloops before the lockscreen or setup screen.

Any suggestions I can try?
[G2 Android Development] Ace42:
For me R19 boots to the LG logo, then reboots again to the LG logo over & over. It doesn't reach the boot animation, and I'm using Mahdi 8-17 for d800.

Transmitted via Geass
[G2 Android Development] RenderBroken:
Thanks guys! Yea I had the issue too. I am going to try another rebase with numerous commits removed. As I said before i create patches from my working tree and some will be duplicates so I worry that there were some merge issues that did not get picked up during the compilation. I am hoping to have it ready this evening. Its 5:45p CST here now. But I do feel this is the route to go and will be worth all the work right now.
[G2 Android Development] bleached45:
R19 boots fine for me on AICP/D800.

Just chiming in.
[G2 Android Development] Ace42:
No rush & thank you, I'll just revert to R17 in the meantime. It has been really stable for me so far.

Transmitted via Geass
[G2 Android Development] count_martin3z:
Yesterday I had two SOD on Liquid and r19 . I have log if you want but for now get back to solid r17.
[G2 Android Development] RenderBroken:
OK the 2nd rebase seems to have gone much smoother this time around. Alot less build errors to fix this time around. As I said I was able to remove numerous duplicate commits and others changes that were not needed. I will be testing and if all goes well I will build.release later. Goodnight guys!
[G2 Android Development] arifqur:
Looking forward to it and take your time.

No hurries.
[G2 Android Development] MaluNoPeleke:
Is the new interactive version still included?

In R18 the audio problems were gone but with R19 they are back.
[G2 Android Development] bgx:
Take your time! Meantime I'm back to stock. Monday I will get my gurantee changed g2 because of the black lines issue. Then I'm back on render!
[G2 Android Development] bleached45:
I nearly s**t myself!

I just had a vertical black line show up randomly while the screen was off (I was playing music so I know it didn't reboot). long story short I fixed it with a dead pixel detection/fixing app. I don't know if this will help everybody. But I thought I'd share here.

I was/am on R19 and AICP for the D800, but I really don't think the kernel or even the ROM was the cause.
[G2 Android Development] RenderBroken:
It is not, This really really sux guys. Sorry bro. If it continues you can take apart your phone and make sure the ribbon cable is secured properly and not loose.
[G2 Android Development] Lawlrus:
They tested a few dead pixel apps in the screen damage thread, and for the most part it didn't work well, or if it did, it was only a temp fix. Of it was only one line I doubt its the issue most people are having because its more that not, a multitude of lines.

As render said, check your cable if comfortable enough/it persists. A few people seem to have said that replacing the ribbon cable from the mobo to the digitizer is that's fixing the lines. Bad news being you can't just get the cable, you need he whole LCD assembly. May have just been some dead pixels in your case.

Back on topic [MENTION=5438598]RenderBroken[/MENTION]

For whatever reason your kernel charges hella faster than other stock kernels, but, have you or anyone else noticed it getting very warm while charging. Like over 60c? I think my cable is being an ass.

Sent from my Vs980 running Aicp 6.0
[G2 Android Development] RenderBroken:
Do yall prefer to use Franco's Therm control(R19 I think), bricked thermal control (r17) or QCOM's Thermal Control?
[G2 Android Development] bleached45:
Yeah, I have seen it has happened to stock, mostly untouched phones. I wasn't blaming anybody. I'm just so glad it went away.

Hey, I have a question:

I've been going through some of the github sources for your kernel, and stuff faux posted, as well as a little by dori and I'm just curious, what is in control of the audio driver? Are the drivers built into the kernel or the ROM? Or is it both? Do they somehow need to line up in both the kernel and ROM? I ask because of the N5 audio drivers going around and the G2 drivers. I'd like to understand how switching kernels effects this but it is a bit over my head.

Also, faux has developed or is currently working on a driver version 3.6 (you just updated to 3.5). I don't even know if it is officially out yet, but you can see it in the wild in faux's G3 sources. Just thought I't was interesting. I seem to have sound control working with R19 and driver 3.5 (using the beta version of the sound control app) but the poweramp gain (the feature I am most interested in) seems really temperamental. It does seem to set the gain higher (+5, which is part of faux's "quality" preset). But it doesn't seem to bring it down if you move the sliders down. And sometimes it seems to set it too high (maybe after a reboot, which the G2 had issues with the set on boot values sticking, something to do with the lg_snd_ctrl_locked I think?) Opening the app and letting it read the values seems to fix it.

Anyways, I appreciate you looking into the sound and even updating it after my pestering :p

This time I am actually just asking to learn. I'm slowly trying to get a better understanding of Linux, and Android is my main concern and this feature is something I use everyday. Sorry if this is a bit too in depth for a quick answer. Just curiosity getting the better of me. (Most everything under codecs/sound_control on your's and faux's git are way over my head, so it is probably a lost cause, lol).

---------- Post added at 11:27 AM ---------- Previous post was at 11:23 AM ----------

Yeah, though it went up/down the whole screen, Strange for just a random dead pixel. I hope it isn't the start of something. I'd rather not open the phone. Opening my laptop is stressful enough.

Mine does seem to get warm while plugged in, but only if the screen is on for prolonged periods. Most phones I've had did this so I assumed it was normal.
[G2 Android Development] 1ceb0x:
R19 is just damn awesome in terms of temps. i am now charging my phone, using data and browse and the phone barely feels hot. With QCOM and bricked, i always had a hot device.

Namaste! Sent from Orion Galaxy.
[G2 Android Development] RenderBroken:
Not really. Do you have thermal control enabled? It may be your cable. The way electricity works is if you use a charger that is over the recommended Amps, it will not burn up the battery. Electricity is pulled, not pushed. This means that the phone will only take what it can handle. As for your case something else seems to be up. Try a different cable and let me know. I am curious.

Sound control is completely kernel side. In my newest rebase I dumped all the new Sound commits I had made. I will be doing it from scratch because if other merge errors occurred else where, I don't feel comfortable with the state that its at currently. I will just do the work myself. I hope too that the black line is not s a sign of more to come. Thanks for being smart and thoughtful! I appreciate you not pointing a finger.
[G2 Android Development] kgian2007:
Hello to everyone, i have lg f320l i have mahdi rom installed and i tried render kernel for my device, everything works gread but i have one only problem: when i try to backup appl. with titanium backup to external sd(micro sd) i get a message that sd card in not writable, when i try to set from camera appl. external sd as storage for photos and videos i get a message "insert an sd card".I have formatted the microsd card (with erase sd card from storage options) but the problem persists.Same thing happens with s3 kernel from Mahdi.Is there a way to fix that?