yashsingh1/xdaforums huggingface dataset:
[G2 Android Development] :
I'm no expert, but wouldn't putting the drivers he overwrote into the f320 device tree as overlays make it only use those for that variant and build normally for the rest? Or would that just cause build errors in general if it still tried to build the standard drivers as well? I wouldn't think it would, but you never know.
[G2 Android Development] RenderBroken:
From what I seen, there would have been issues. We also need to keep in mind that this does not magically fix Wifi 100% for F320 users. There are still reports of issues. I am just not going to put in all the work needed for something that is a partial bandaid and "could" cause bigger issues for the rest. Really, anyone is more than welcome to take my source, do whatever you want with it, and let me know about what you changed. If someone wants to do the work for F320 users, I would be more than happy to put this behind me and merge it in with proper credits. And this is not meant for you Yoinx, but I don't have to defend myself. I took a look, weighed the pros and cons as I seen them, and decided it was not worth it for the time being. When we all were involved in the initial CM12 bring up, I worked for 2 weeks trying to get wifi, BT, and the other issues fixed for the F320. I was tracking down users, building test builds, ETC. I was able to fix some things but not all. But as I said before. If the new LP kernel, that is being worked on, doesn't get here soon then I may take another stab at it. We will just have to play it by ear but from what I have gathered, all we need is just a few more kernel sources to drop and we are good to go.
[G2 Android Development] HueyT:
VS98012B, Vanir 5.1 lateset nightly by Sudorootdev, and Render R12 work well together. Just FYI. Thanks for great kernel. Smartmax is great governor also.:good:
[G2 Android Development] metteduch:
Is the missing dt2s on AOSP ROMs kernel or ROM related? Or maybe just launcher related? It is weird because dt2w works just fine.

Sent from my LG-D802
[G2 Android Development] jeyd02:
It works fine for you? What model you use and what's the rom version.
[G2 Android Development] reemar:
[MENTION=5438598]RenderBroken[/MENTION] , seems like android 5.1 + f2fs of any partition + twrp cause recovery to not be able to boot..

solution for me -> cse kdz flash..
[G2 Android Development] RenderBroken:
Good to know, I guess I will remove f2fs in future 5.1 releases till we have more answer. Thanks for posting your fix!
[G2 Android Development] RenderBroken:
You talking about double tapping the status bar? That's always been a rom feature. Nothing like that is controlled kernel side.
[G2 Android Development] :
No worries, I was just tossing that out there as a possible way to alleviate the code conflict issues when building for multiple sources without having to add in a ton of if cases . No intention of implying that you needed to defend anything, though with the onslaught of complaints... It may have been ill timed.

I don't think anyone here questions your work. Just unfortunate that those f320 guys have such different stuff that its like a different device that someone just slapped a g2 sticker on.
[G2 Android Development] metteduch:
I am talking about tapping anywhere on the homescreen to go to sleep (like on stock ROMs).

Yes, double tap on status bar works. I am just curious to know the reason behind not having dt2s like stock roms.

Sent from my LG-D802
[G2 Android Development] jeyd02:
Well I think that mostly work in Stock LG launcher as far as I know.
[G2 Android Development] :
Because that's baked into the stock rom's framework. For similar functionality you need to find a gesture based launcher (I use apex) and set it's double tap screen action to launch an app that turns off the screen, I think I use this one

It's not kernel related though and can't be controlled from the kernel.
[G2 Android Development] IOmega666:
[MENTION=5438598]RenderBroken[/MENTION] dunno if you saw what i asked but since which version of KK Kernel it's BUMPed? Because i really wanna use Omni and can't because now i gotta have KK Bootloader to use your kernel but Omni uses JB, i guess every AOSP KitKat ROM uses JB Bootloader.
[G2 Android Development] liusi522:
320 can't open wi-fi

320 can't open wi-fi
[G2 Android Development] Lawlrus:
Go to blackbirds thread right under this. And pm him telling him you'd like to try his test kernels if you guys want it working.
[G2 Android Development] liusi522:
OK .

Thanks for your reply and suggestions.I try.
[G2 Android Development] Fobz:
Hi Render, thank you so much for the awesome kernel. Really appreciate your work.

Just wondering if you can give out the smartmax config as I am still on r11.

Thanks again for all the hardwork!
[G2 Android Development] TDSJR:
Would anybody be so kind, as to drop box R12 for D801? I haven't been able to reach the server all day.

Thanks, in advance.
[G2 Android Development] RenderBroken:
What kind of error you getting accessing the server? If no mirrors it for you, I will update my mirrors. Sorry bro.
[G2 Android Development] RenderBroken:
Last time I used bump on my kk kernel was some time ago and it didn't boot right. Does loki method not work? All of my kk kernels are loki. Let me know. Thanks!
[G2 Android Development] TDSJR:
Of course, when I go to get the exact error I'm receiving, it works. LOL

Thanks, as always.
[G2 Android Development] jeyd02:
Hey, render awesome work. Any plan to add aculard or cquiet hotplugs?
[G2 Android Development] RenderBroken:
Lol thats how it goes, I am going to did through the logs to see what was up. It could be an issue with the CDN I am using. They have been a pita lately but that's what you have to do when you are getting over 5000 unique hits a day. gotta protect yourself. Thanks anyways!

i have tried Alucard but there are build errors and they are weird ones too. Meaning I am missing a number of subsystem changes needed. Also with cpuquiet, it will need alot of bringup to work as well. I would have to lok at the Omnirom G2 source but if its like the OnePlus One, its pretty close to pure CAF which I am not so certain functions would be missing and such to fully utilize the driver. Also this is conjecture, I will have to look.

I do know that I tried Alucard on my OPO kernel as a test and it was not any better than my tried and trusted MSM_Hotplug. I also believe that it has to do more work (Code wise) to achieve the same goal.
[G2 Android Development] liusi522:
Can you fix the WiFi?F320…

---------- Post added at 07:29 AM ---------- Previous post was at 07:28 AM ----------

:):)
[G2 Android Development] bolt890:
You should read some previous posts, they were all about this.
[G2 Android Development] ProcityMax:
Render I just want to tell you that Lollipop ota is coming out today for the D800. Hopefully this is good news for the future!
[G2 Android Development] RenderBroken:
Yea I am pretty excited about this. Right now we have some awesome devs working to put together a new LP kernel to replace the ones we are using.

Still thanks for the heads up!
[G2 Android Development] RenderBroken:
Awe man, you broke the "search before you post" rule :(

No, I will not merge in the "fix" to fix wifi for F320 Users, Its not that I don't love yall, or that I don't care for the F320x Community. I hope my track record proves otherwise lol Still, we are working on a NEW LP Kernel that should encompass ALL Variants and it will be based on the new LP source! At least we will be using LP Blobs on top of CAF. So with that in mind I will not be working to fix Wifi for F320, Win7fun has already done an amazing job doing so and its based on R11 (I believe). I do know that other Devs have tried to merge in his commits and the builds failed. Not only do they fail to build for F320, but for other variants as well. Thus showing that this Fix is not a real fix in the sense that I can easily use it and all will play well together. I do have to worry about 6 other variants as well.
[G2 Android Development] deathrowz_sri:
Thanks for explaining and committing yourself to work on it later. When do you expect LP sources to drop? Does it mean that we can finally move away from JB sources coz if im correct, our KK kernels and current LP kernels are based on JB sources right?

Why do think CM never bothered to build a separate tree for F320? I got myself a F320 simply because in my country these Korean variants are considerably cheaper compared to Intl variants but comparing the specifics its almost the same or for me better with removable battery and SD.

I can wait till LP sources arrive. But please dont give up on us!! :)
[G2 Android Development] liusi522:
Thank you for your explanation！I known WIn7fun has fixed a lot of problems and I have been using his kernel to fix the problem.:oBut this can not be used in 5.1:crying:.So I just raised it in 5.1.:crying:I really appreciate what you have done for G2.Thank you again.Then I will wait for your good news.All the best.:)
[G2 Android Development] ProcityMax:
No problem! Glad to hear, and I hope things are going well. Can't wait to see what you guys are cooking up!
[G2 Android Development] RenderBroken:
No, kk source for as based on kk source, that is why it worked for all variants. Not sure why CM never coded for f320x support but I would imagine that it has to deal with how different the dependencies their JB source had compared to the others, then when KK came out, there wasn't any real push by anyone to update the CM kernel to the new source so they just stuck with the JB source. Eight now there is a pretty big push by Rashed and others to bring up a new kernel for LP.
[G2 Android Development] RenderBroken:
No worries, I do understand we all want the latest and greatest.
[G2 Android Development] hambalos:
Hello guy's i am new in this thread.i flashed this ROM but i dont have LTE connectivity option on network.is there a fix.......thank's.:o

---------- Post added at 05:56 PM ---------- Previous post was at 05:55 PM ----------

Sorry pls delete wrong thread.My apologize.
[G2 Android Development] RenderBroken:
No worries, thanks for letting us know!
[G2 Android Development] jeyd02:
Hey render, anything new you guys working on?
[G2 Android Development] illxf:
try search but can't find good answer

one stupid question:

i use this kernel on my D802 and install synapse

in the synapse i turn low the cpu1/2/3 max frequency,and loader the spearker

i click all the setting,but after reboot the phone,i have to open synapse and click the "X" to let all the setting apply

i try some combination in the setting-boot service but no help

how can i set,and then each time the phone reboot it will auto set CPU frequency and speaker gain?
[G2 Android Development] secret.animal:
It is set so that any reboot before an hour is considered a fault and rests your changes. Make sure you are hitting the check mark.
[G2 Android Development] screenager:
Bootloader confusion

Hi guys!

Its been a long time since i last updated my device (about a year) and i decided its time to move to aosp. Iam currently coming from Clodystock 1.3 with simplekernel v1 and philz touch.

To get to the point: I dont remember which bootloader iam on. Is there a way to find this out? I tried booting into Bootloader from philz recovery but it just goes straight to system. :confused:

I did some reading the last couple of days and i dont want to brick my device flashing this kernel on top of the wrong bootloader!

Should i take the safe route and just let Autorec run through - after that i should be on jb bootloader right?

Can someone help me out?

THX
[G2 Android Development] RenderBroken:
always, I am working on a new way to flash kernels for the g2 so devs don't have to worry too much about the roms ramdisk.

so When you reboot, can you clarify which settings are highlights in light grey?

Not sure how you can tell which bootloader you are on but I am sure someone knowledgeable will come by to answer your question. I too would like to know.
[G2 Android Development] TaRsY:
You mean anykernel? Flar2 and show-p are masters of it. :)
[G2 Android Development] RenderBroken:
Right, the problem for us though is adding loki/bump to the mix. That's really the only hangup. Also having the ability to add boot scripts as well. They have to work with selinux being set to enforcing. Just a few hurdles have to be jumped but I am certain that I can swing it.
[G2 Android Development] screenager:
Really appreciate your kindness. I´ll make sure to let you know, when i have more informartion.
[G2 Android Development] bamonkey:
I wish i could answer this better but i CAN say i remember the factory reset prompt looked different depending on the bootloader installed. The JB bootloader *which i am on to use aosp lollipop* is basically a white screen that prompts you twice to hit the power button to factory reset *which will put you into recovery if you have twrp installed*

On the newer one it has been awhile since i even TOUCHED my bootloader but i know it looked different and had you use the volume keys to select the option..like this i think.

[IMG="G3 hard reset"]http://solverbase.com/images/2/28/LG-G3-HARD-RESET-FINAL.png[/IMG]

to get to the factory reset screen may also be different depending on your bootloader and model i want to say...
[G2 Android Development] renaltosonylevi:
Not sure how you can tell which bootloader you are on but I am sure someone knowledgeable will come by to answer your question. I too would like to know.

Unless you have gone and installed lg's official 5.0.2 lollipop release it is easy to tell which boot loader you have by the button combination to enter the factory reset screen.

Jellybean requires vol down + power followed by vol down + power.

KitKat requires vol down + power followed by vol up + power.
[G2 Android Development] screenager:
Indeed this works. Could enter recovery with pow down&vol down. Then it asked me to press the pow button to do factory reset -> jb bootloader

After some more research the picture bamonkey posted means that you are on an kk bootlaoder.

So i guess it is save to flash render kernel then?!

THX Guys
[G2 Android Development] bamonkey:
Sounds like you are ready to go! just make sure you flash the correct version *KK or LP* that is in the OP. was debating trying stock LP but realized that i would have to give up the 5.1 which performs noticibly faster than 5.0.x. Happy Flashing:good:
[G2 Android Development] screenager:
THX, any 5.1 aosp you can recommend?
[G2 Android Development] jeyd02:
I would positively recommend BlissPop 3.1.

Only issue with it so far is that when you enable dt2w the screen goes randomly on when screen it's off. But the team is looking into that.

---------- Post added at 12:55 PM ---------- Previous post was at 12:39 PM ----------

Hey render, I was checking the OP for some updates and I have noticed that you still haven't released the R12, are you still optimizing it or something because Idk if you remember but you gave me a initial test release for me test and it works great. But since I didn't seen any OP updates just wanted to know if it's going to be any different from mines [emoji14].
[G2 Android Development] phoenix_rizzen:
R12, which only works with Android 5.1 ROMs, was released several days ago. Been running it here with Bliss v3.1.

Typos courtesy of my Blissfully Rendered LG G2 (D803).
[G2 Android Development] jeyd02:
I don't see the R12 build in the OP..
[G2 Android Development] phoenix_rizzen:
See post 5807 in this thread. :)

The OP may not be updated, but if you follow the download links, R12 is available.

Typos courtesy of my Blissfully Rendered LG G2 (D803).
[G2 Android Development] tropenfrucht:
As you are on philz recovery i would say you are on JB bootloader. As far as i know there is no bumped version of philz recovery, only loki which runs only on JB bootloader.

You can also try button combination for entering recovery.

press and hold power + vol down, release and press + hold again when you see LG logo -> JB bootloader

press and hold power + vol down, release when you see LG logo and immediately press and hold vol up + vol down -> kk bootloader
[G2 Android Development] screenager:
thx, already figured it out!
[G2 Android Development] jeyd02:
Why not an OP update? ?
[G2 Android Development] Lawlrus:
Probably busy.

I for one would much rather be working on new merges then wasting time updating an op when you can see all the changes on his git.

Wouldn't you?
[G2 Android Development] jeyd02:
I'm sure... Yes. As well as updating the OP to inform/update everyone to prevent meaningless questions and request and pointless ota. :) many people don't know the github. However, I couldn't agree with you more. We should all appreciate the work he gives us really.

Soo I was just saying...
[G2 Android Development] Lawlrus:
"Prevent meaningless questions" LOL really?

Half the people that visit this site don't even read an op. How many times have people asked/tried to flash this on stock?

I get it, dumb down development so people that want the answer now, in laments terms, versus people actively trying to learn what git is, or how it operates.

I'm sure he will update it, but there's bigger and better things he could be doing, so I say carry on. Let the people that don't actively want to gain knowledge wait.
[G2 Android Development] RenderBroken:
Lol. so true sometimes. I am the worst at updating OP. Here is my normal roadmap to release.

Build

Upload Test Build to Google Drive

Test the build

Decide build is stable

Copy to my Download Server

Generate Change log

Create Post about new release

Write up post of info

Go to bed lol

So, the main reason why I have not been able to work on my G2 kernel as much lately are 2 reasons, 1 yes I have the OPO so that leads to 2, my wife has my G2 and she has been out of country the past 3 weeks and will be back in 2 weeks so its hard for me to build and test. Those who have access to my test build folders will see that I usually build about 30-40 test builds before I release. Its hard to do that through others remotely. SO I am working on AnyKernel for the G2 (Has to work with Loki and Bump) in the meantime. I just wanted to let yoos guys know. I will not be abandoning development for the G2, and have no plans in the future. Th3 g2 will remain relevant WAY longer than my Ol' Cappy (GS1) did. I do have some cool stuff queued up. Some cool fixes. One HUGE fix is how the circle wipes (Clicking buttons, Quick Select Tiles and hitting the call button are good examples) are complete trash in LP and I believe I know the fix for it. I am also kinda waiting for new Kernel source to be completed and ready to go, Also waiting for Roms to adapts the new source will take time. I imagine I have another LP build left on the current source. Kernel source will continue. I may keep plugging along with it. Thanks guys for your patience, it is appreciated!
[G2 Android Development] jeyd02:
I know he's working busy and he'll eventually update, like I said I appreciate all the work all the devs do here for free.. I am aware of that.

And no, I rather let him focus on his work but like what I am was trying to saying and not sure why this discussion came about but anyways... since he posted an update on the releases of R12 on some post I wondered why he didn't updated it to the OP. I know he has a lot on the plate. So carrying on
[G2 Android Development] nklenchik:
Does Bliss still have the wake issue with the Render kernel?
[G2 Android Development] phoenix_rizzen:
Yes. But if you turn off ambient display, and turn on proximity sensor check, then it turns off correctly most of the time. When it doesn't, just cover the sensor and hit power and it always turns off.

Makes DT2S a bit useless ATM, but it's usable.

Typos courtesy of my Blissfully Rendered LG G2 (D803).
[G2 Android Development] RenderBroken:
I dont remember reading anything about a wake issue, Can you go into some detail about it? Thanks!
[G2 Android Development] Hid3rs:
If DT2W is enabled, then the screen will turn on 95% of the time right after you turn it off. All 5.1 ROMs have this issue unfortunately.
[G2 Android Development] RenderBroken:
Thanks! Thats a weird one lol.
[G2 Android Development] jamesd1085:
I haven't tried any 5.1 roms yet...is lift to wake still a feature?...it caused the wakeup after dt2s issue in early lollipop roms
[G2 Android Development] abby_nitewolf:
I've been getting these issues too. Here are a couple of logs. Hopefully they can help.

https://www.dropbox.com/s/xqpuv5co0j9hyq3/2015-04-13_22.53.zip?dl=0

https://www.dropbox.com/s/35kfc6tkzv2glrv/2015-04-15_16.59.zip?dl=0
[G2 Android Development] thackoon:
Are you referring to the Lollipop kernel source? Are we still waiting for the different carriers to release this? What will the advantage be to using the new source? Stability and speed?
[G2 Android Development] phoenix_rizzen:
It's an upstream issue with either CM or AOSP that's affecting all 5.1 ROMs.

Turning the screen off with DT2W enabled causes the screen to immediately turn back on. The only work around is to enable the proximity sensor and cover it when turning the screen off.

Bliss also has the "disable ambient display" workaround to make it work most of the time.

Disabling DT2W prevents the screen from turning back on, but removes one of the more useful features of the G2. :)

Typos courtesy of my Blissfully Rendered LG G2 (D803).

---------- Post added at 06:14 PM ---------- Previous post was at 06:12 PM ----------

Yes, it's still a feature. Pretty sure it doesn't affect this bug as I always disable it and have to cover the proximity sensor to keep the screen off.

Typos courtesy of my Blissfully Rendered LG G2 (D803).
[G2 Android Development] Lawlrus:
Yes

Yes - Sprint

Yes

There's a few 5.0 ROMs on the vs980 that use 4.4 and 5.0 kernel source and it is infinitely better.

Better battery, faster, no issues whatsoever aside from what seems to be some soft reboots when using high accuracy GPS, which may be connected with cm based ROMs not being full caf.

Not a single person is complaining about VoIP issues, so I'm pretty sure that's fixed too.

Plus its on the native bootloader, so 5.0 modem, and it may or may not cut down on screen damage because in all of the tin foil hatting people were doing, they thought the fact we were still using the 4.2 bootloader might be one of the reasons.

These builds are bump only, no more loki
[G2 Android Development] thackoon:
Thanks for the explanation!
[G2 Android Development] phoenix_rizzen:
D803 source also hasn't been released yet. :(

Typos courtesy of my Blissfully Rendered LG G2 (D803).
[G2 Android Development] Lawlrus:
What the hell. Canada needs to step up their game then.
[G2 Android Development] timmyja:
Whit kernel I need for android 5.0

Will R12 work or I need R11
[G2 Android Development] TDSJR:
You need R11 for 5.0.x. R12 is for 5.1
[G2 Android Development] hoangtungst:
Have flashed R26 for my D802 and TWRP show: error excuting updater binary in zip ....
[G2 Android Development] ThatKidDrew:
State twrp version? You probably need to update your twrp to 2.8.6.0 or higher

MODEL: VS980 ?

ROM: Temasek's CM12 ?

KRNL: Stock ?

RCVRY: TWRP 2.8.6.1 ?
[G2 Android Development] hoangtungst:
I'm using TWRP 2.8.6.1
[G2 Android Development] TDSJR:
Delete

---------- Post added at 04:29 AM ---------- Previous post was at 04:28 AM ----------

Which ROM are you flashing?
[G2 Android Development] RenderBroken:
If you are flashing a KK Kernel then your recovery actually may be too new.
[G2 Android Development] Lawlrus:
Misread the initial post. Does this ROM boot with the stock kernel? That error typically indicates you're on a 4.4 or 5.0 bootloader. That's why Loki fails.
[G2 Android Development] hoangtungst:
Sorry , seem it is my fault .This kernel only work on AOSP based rom ?
[G2 Android Development] Lawlrus:
How did you not even read the first tangible sentence of the op, that is bolded?