yashsingh1/xdaforums huggingface dataset:
[G3 Android Development] grainybazzles:
I think because the author of the camera port is banned by xda, but I'm not sure. These things are hard to keep up with.
[G3 Android Development] Ainz_Ooal_Gown:
He was complaining of people stealing his work .-. But XDA didn't help him instead they banned him.
[G3 Android Development] m1trand1r:
It was actually that he disobeyed xda mods for several times. And no one was stealing his work. Now please edit your post because everything related to that ex-xda-member is forbidden to post at xda. That's all ;)

And look for yourself :

http://xdaforums.com/lg-g3/themes-apps/mod-htc-one-m9-camera-port-t3056305/page2
[G3 Android Development] Ainz_Ooal_Gown:
.......Bruh I'm only sharing a port, but since your asking nicely I'll simply put the links elsewhere. Since you don't want it here, but that doesn't mean it doesn't belong on XDA.....since their are already sense 7 ports.
[G3 Android Development] m1trand1r:
It's not me that don't want you to post links or share someone elses work. You have to understand that. And none of jishnu's work belongs on xda. I posted link above.
[G3 Android Development] Ainz_Ooal_Gown:
Wow....why do they have to be like that....he's doing great work.
[G3 Android Development] JAWheat411:
Is there a trick to keep WiFi connected. I have played around with everything. Cycled all through the channels on 2.4 ghz and checked settings on the router. I know it isnt a hardware issue because I have the same issue in all the of our G3s running this ROM. I believe the G3s handle WiFi differently because we didn't have the problem with other phones.
[G3 Android Development] schwem:
He does do a fine job but the fact of the matter is that what he does is illegal. He takes closed source applications and alters them for use on other devices without the permission of the developers. It's really no different than pulling any other type of copyright infringement. Yes there's alot of ports on xda but his drew mass attention and in the past he stepped on alot of toes and was posting paid apps as free to use on xda leaving the xda team no choice but to ban him. It's one thing to port a camera from a stock rom but it's another thing to crack a developers hard work and share it for others to use without having to pay for it. It'd be one thing if he had gotten permission but that's obviously not the case. There's no room here for theives.
[G3 Android Development] Ainz_Ooal_Gown:
Damn I didn't know that part
[G3 Android Development] Laexios:
No one have the same issue ? That's really problematic for me.
[G3 Android Development] m1trand1r:
how can you log into your wifi with sim method ?

Which method is that?

---------- Post added at 22:51 ---------- Previous post was at 22:50 ----------

thanks for longer version [MENTION=6089420]schwem[/MENTION] :)
[G3 Android Development] Laexios:
I don't know if it exists somewhere else than France (where I live) but my phone can connect to some free wifi spots where only some users can log in. It depends on your contract distributor.
[G3 Android Development] jreink01:
Is anyone having issues with Bluetooth fc? It used to be rare for it to fc, now it fc 4 to 5 times daily.
[G3 Android Development] takis:
Are there any clues on why only some face random shutdowns??
[G3 Android Development] m1trand1r:
Most likely due to Hotplug or something kernel related.

I am running latest CandySiX and I haven't had any random shutdowns or reboots or such.

But what I do have is MMS app fc's constantly when trying to open it...didn't fetch logs yet....I changed MMS app with another one....oh...and I flashed R22 by [MENTION=4794976]777jon[/MENTION] on top... :)
[G3 Android Development] takis:
I made a poll the other day on g3 community google plus and 180 people voted on having this problem on any cm rom... If a solution is found cm roms will be used much more by users
[G3 Android Development] m1trand1r:
I am running CandySiX for couple hours now...i've had some issues when trying to restore my apps and data...but figured that out...now i'm giving Candy a real deal spin and i'll see what will happen...but so far....nothing such did happen..yet...

EDIT : I ran into another issue just now....WiFi refuses to turn ON....OMG...
[G3 Android Development] Cryptecks:
CandySix is no longer based on CM, it is a fully AOSP base [or so we've been told]. This leads me to believe, personally, that it is definitely in the kernel/hotplug. Maybe there is still some sorts of CAF/CM remnants in those places that are bugged. They would be bugged in CM, and if the new Candy kernel is using anything from it, could be happening to us for that reason too.

Just a guess though, I've never been a kernel or hotplug dev or maintainer.
[G3 Android Development] m1trand1r:
Well...I flashed [MENTION=4794976]777jon[/MENTION]'s R22 on top....changed hotplug to intelliplug and all is fine...and yeah...I remembered now...when I didn't flash custom kernel at first and I was running stock candy kernel ...I was hammered by hotboot once....but after flashing R22 nothing bad happened yet....so...kernel might be problem...
[G3 Android Development] hokiealumnus:
FWIW, as a very subjective observation, I think the original AOSP CandySiX kernel was more smooth. The animations (especially task switching) and scrolling (Twitter, Facebook) are somewhat jerky with this new kernel.

Part of what I loved about Candy was its smoothness. I'm happy to change kernel settings if need-be (though to what I'm not sure), but I'd rather not have to.
[G3 Android Development] Cryptecks:
I forgot to mention this is my last post, but I'll chime in FWIW to the devs as well. The original AOSP-base Candy kernel gave me absolutely zero issues. Sure it lacked for kernel options, but it was solid. The second AOSP build, with the newly included kernel, has produced around 5 BSODs requiring a battery pull at totally random times. This is partially why I first posted that I think the issue with BSODs on the G3 family in general has to do with the kernel/hotplug, as the issue was reintroduced for me after the 2nd build.

Still loving the ROM in all ways of course, but this is my 2 cents on it.
[G3 Android Development] Cuzz1369:
I have noticed this as well. You can restore the old boot.img from a backup or extract it and flash from the ROM zip for now. It being looked at and will have an update out as soon as it's fixed.
[G3 Android Development] Cryptecks:
You guys are the best, thanks for the update! With PA and PA Legacy on an extended hiatus, I haven't been building ROMs for a few months now but I have loved watching the Candy team get to work on MM with such good focus and communication.
[G3 Android Development] jreink01:
I tried flashing the newest build without clearing caches (as suggested) and it got stuck on reboot, optmizing apps, (it was such for over a hour) do i did a battery pull and again it got stuck trying to optmize apps for over 2 hours. I had to again do a battery pull and this time went into recovery to restore my backup. Anyone have any clue why it's getting stuck in optmizing apps after it reboots? I flashed this after clearing/not clearing caches and same thing happened.
[G3 Android Development] Cryptecks:
Just to jump back to using 777 kernel for a sec. I love the kernel, and used it a LOT on most LP and MM ROMs, but with the new CandySix using an AOSP base, flashing 777 kernel is actually just flashing a CM/CAF-based kernel back onto the AOSP base. It may get rid of BSODs because Jon is a boss and had them pretty well cleared up from his kernel, but there may be other issues introduced by using CM/CAF code in an AOSP ROM. Probably not honestly, but it is possible.
[G3 Android Development] radelon:
Fwiw I was having some weird issues with new kernel too....tried interactive and on demand governors and had the same issues with lag and random hard locks..... Changed governor to Lionheart and its been running great
[G3 Android Development] takis:
First thread i report this and not everyone blames my sayings! You are reffering to the random shutdowns by saying it is looked up right?...

I am actually glad i am not the only one facing those issues that may force you to start pulling batteries whenever and wherever!... Thanks cuzz
[G3 Android Development] Cryptecks:
Random shutdowns (device is actually still on, but can't wake) are commonly called Black screens of death, or BSODs, around the G3 community. They have LONG plagued CM/CAF and now AOSP-based G3 ROMs, all G3 devs have been pulling their hair out due to them for a year now. The fact that Candy and Cuzz are taking a new, closer look into them can only be a good sign. The fact that the initial AOSP-base build did not have them (at least for me and many others) is a very good sign honestly.
[G3 Android Development] takis:
Gonna download that first build !!! Thanks dude... Seems you could also help with the development... :)

Where is the link??
[G3 Android Development] p70shooter:
In the op
[G3 Android Development] takis:
Only the vey latest is available..
[G3 Android Development] p70shooter:
Oops, usually there are a few builds there.
[G3 Android Development] takis:
How can i get that build now?
[G3 Android Development] p70shooter:
https://androidfilehost.com/?w=files&flid=45915 Pretty sure that's it but not 100%
[G3 Android Development] takis:
Thanks a lot... Would be awsome if someone could confirm that this is the no sod build
[G3 Android Development] p70shooter:
Yep asked the boss it is that one.
[G3 Android Development] takis:
Do you know each other personally?
[G3 Android Development] Cablespider:
Personally, I think the kernel rocks on the D851. No stability issues to report and almost 5 hours SOT. zzmoove/ybat
[G3 Android Development] p70shooter:
Sadly yes :D
[G3 Android Development] BakedTator:
I'm on the 1-8-16 build (ls990) and the new kernel isn't giving me any issues! Not random reboots, no bsod or anything! Rock solid man!
[G3 Android Development] blehman:
I'm getting the same issue on my D851. Clean install of the 1/08 build. I tried the Privacy Guard settings, however I don't see where to set it to default (I am showing built-in apps, if I toggle the lock I still get the error). Here is from logcat, sorry for the formatting..

01-11 11:36:27.450 E/AndroidRuntime(15906): java.lang.RuntimeException: Unable to resume activity
{com.android.dialer/com.android.dialer.DialtactsActivity}: java.lang.SecurityException: Requires READ_PRIVILEGED_PHONE_STATE:
Neither user 10007 nor current process has android.permission.READ_PRIVILEGED_PHONE_STATE.
[G3 Android Development] hokiealumnus:
Wow, that really was the ticket. Lionheart fixed all of my tendering quirks. Thanks!

Thankfully I haven't had any BSOD on either build, ever. From the recent posts it seems like that's a D85x problem that doesn't affect the vs985.
[G3 Android Development] kazbek_s:
Is this rom stable for daily use?
[G3 Android Development] Cryptecks:
Yes.
[G3 Android Development] m1trand1r:
You just made my evening :D
[G3 Android Development] hitek86:
I tried to install the latest version yesterday, over my current version from 11/12 and when the update completed, google play services wouldn't work, and I started getting BSOD's... first time this has happened to me.

However after a few full wipes and clean installs of the new version my phone is now working great. I previously had the issue where if my face touched the screen during a call it would hang up. this all seems to be fixed now. so I am very happy with the latest version. cheers
[G3 Android Development] Cuzz1369:
Well if only you knew how to read... Could've saved yourself a lot trouble.

Glad it's working for you now.
[G3 Android Development] mvez73:
After 3 days everything is working VERY well. No BSOD, no FC. Only "invalid number" like every MM roms. The only issue is the option Buttons in Candy interface that is empty...

And battery life is awesome! The rom is awesome! Thank you :)
[G3 Android Development] hitek86:
I followed the usual process...

Updating from previous CandySiX release

1) Download CandySiX.zip

2) Boot into recovery

3) Flash CandySiX.zip

or did I miss something in the last few pages?

anyways works now, only lost a few txt msgs. im happy :D
[G3 Android Development] Cryptecks:
The codebase totally changed between the builds you flashed and multiple folks here recommended a clean flash to start with the new AOSP base.
[G3 Android Development] leeroyjenks:
You missed a lot.
[G3 Android Development] hitek86:
ohh. so it would seem. been on holidays for 3 weeks, haven't looked at a computer in that time. will have a good read of the last few pages. cheers
[G3 Android Development] Ltilt2:
Can someone confirm this issue I am having. When I disable or delete the google app or with root explorer delete Velvet and do a soft reboot my device won't Boot. It will stay at optimizing apps then it goes back to Candy 6 boot animation. Thank you all for any help. The reason I am trying to delete or disable it is cause when I plug my aux cable the voice search goes crazy.
[G3 Android Development] puya.crisan:
What's changed in 08 build? Should i update, cause everything works very good without any problems, seems that no more bsod everything settled nice i'm on candy kernel without any mods. Stable and smooth. Does it worth updating, any major changes?
[G3 Android Development] pramathesh:
Can network be changed yet?
[G3 Android Development] BakedTator:
Nope
[G3 Android Development] TheGripper:
Last version had a perfomance setting in battery options. I always had to change it to "quick" so it wouldn't lag as much. Now with the new version there is no option for perfomance and UI feels pretty laggy. Is it hidden somwhere?
[G3 Android Development] hokiealumnus:
Try downloading Kernel Auditor and switching to the Lionheart governor. Works wonders. :)
[G3 Android Development] CrucialBT:
Hey [MENTION=5088242]Cuzz1369[/MENTION], is there any chance of adding Ambient Display/ext3 support to this for d851? I keep headphones on while at work, and watching the screen light up makes it a lot easier to see notifications. Other than that, this rom works great.

Also, I swapped the system/libril and vendor/system/libril files with the ones from Eliminater74 and I seem to have a lot less problems with the radio. Here's where I got the (updated) drivers: http://xdaforums.com/showpost.php?p=64461819&postcount=2
[G3 Android Development] noidman123:
Does anyone use bluetooth headphones with this rom? Cause I use a Bluedio R+ headset and for some reason when i connect them via bluetooth on this rom, the sound is all garbled and muffled and generally distorted. Another thing is that the volume buttons on my headset now control ALL media volume, rather than just the headphones themselves, like on LP, although this might just be a change from LP to MM. Not rom blaming or anything lol cause all of this could just be MM issues (I wouldn't know though cause this is one of the only roms that boot on my d851), just wanna know if I'm alone here.

Added a pic cause idk if the headphones are popular by name

Edit: forgot to add that i always use link2sd to remove AudioFX then install Viper4Android
[G3 Android Development] happyta5:
Switched to 777 kernel and... No more bsod for 2 days. Guess kernel is main issue....
[G3 Android Development] :
I use some cheap kinivo bt240 bluetooth headphones with viper mod and don't have any issues...plays just like it did on LP & controls work fine. Viper has individual eq controls for bluetooth playback - maybe check those and see if they got messed up somehow. But being that your controls are messed up too it's probably a different issue.
[G3 Android Development] noidman123:
Yeah i set things up how i usually do on LP but it's a no go. I read around that some users of different devices have similar problems so i'm gonna look around more but thanks for the input
[G3 Android Development] purpleurkle:
It's worked wonders for me as well. No more lag or Jerky game play. Ls990
[G3 Android Development] auroraprime:
Hi guys. This rom runs very smooth, but there's one thing that's been bothering me immensely. I get reboots on some notifications and the occasional black screen of death (I heard flashing a different kernel can fix this, so I'll try that). Anyone else have the issue with notifications where their phone just reboots after receiving one?
[G3 Android Development] puya.crisan:
U should detail a little more which model do you have,clean flash, what notifications? Take a log and post it if u want help.

For the begining if u have all those problems i am sure u did not clean flashed.

So do that first, wipe everything, flash rom flash gapps, give it a boot and let it settle a little bit, than install apps u need. If will be the same then take a log and for sure someone will help with advice
[G3 Android Development] jreink01:
Sorry, if this has already been asked but what is the sweetener pack in the OP? I tried to do a search within the thread but didn't come up with any results.
[G3 Android Development] jreink01:
I installed the app but i don't see the option for the lionheart governor? There's 5 other governor options but no lionheart?
[G3 Android Development] hokiealumnus:
Sounds like you might be on the build before 1/8. The most recent one has the extra governor options.
[G3 Android Development] purpleurkle:
Did you go to cpu then cpu governor? Didn't mean to hit the thanks button by the way , so you got a free one lol
[G3 Android Development] takis:
Those shutdowns are not that random. I face them only when using the device... I was on broken with 40 hours screen of time and got one 1 hour later... trying first aosp build now

Ps. I was using lionheart in case of wondering
[G3 Android Development] jreink01:
Yes, i did go to those options but i was on the 1-4 build, i just cleaned flashed the 1-8 build. Still seeing it up but i will check the options now. Thanks

I was able to change it to lionheart.
[G3 Android Development] Ainz_Ooal_Gown:
I guess if I want the newer governors, I'll have to flash a different kernel since the 08 build doesn't work compared to the 04 one on my G3....
[G3 Android Development] takis:
May I ask how difficult the building of a Full Aosp ROM is?

The one made for my tablet is just Awesome... We don't most of the extra features that can be easily obtained via xposed installation...

It is the best way for enjoying aosp on a device. Bug free and clean AF.
[G3 Android Development] Ainz_Ooal_Gown:
Well a different kernel messes with my phones display so if I could somehow get a flashable Kernel from 04, then I could use any AOSP rom...
[G3 Android Development] p70shooter:
Just flash it and backup the boot.img in twrp. Job done, then when you want to use it just flash the rom and then restore the boot.img.
[G3 Android Development] Ainz_Ooal_Gown:
Thank you good sir :)
[G3 Android Development] jreink01:
I have having some disturbing issues. I have clean flashed the latest build 1/08. I installed the 1/8 build, then wiped 2 more times, then installed the build again just to make sure there isnt any remnants left behind. Everything appeared to be working perfectly. I installed kernal auditor and switched governor to lion.... A popup came up on my notifications -settings, please reboot for changes to take effect. I rebooted and once it rebooted the same message was in notifications again so I again rebooted and now it wants to optmize apps. It will get stuck on a particular app. I have rebooted (pulled battery) again and again it wants to optmize apps, goes for a bit, then gets stuck on a different app. Each time, I left it to optmize for more than a hour. I have done 10 different battery pulls and each time it gets stuck on a particular app optmizing. It will not complete the reboot. Please help.
[G3 Android Development] hokiealumnus:
Very odd. I have never had to restart for changing a governor. Indeed, that defeats the whole purpose - everything is set in a running system, hence the "apply on boot" option in Kernel Auditor.

Do you have xposed installed?
[G3 Android Development] Ainz_Ooal_Gown:
yep that fixed the 08 build :)
[G3 Android Development] jreink01:
After another 4 battery pulls and waiting countless times for it to optmize, it finally rebooted correctly. I still have the notification in the notification window that says apply on boot, your changes have been applied. I don't understand why this window keeps coming up.
[G3 Android Development] hokiealumnus:
Because for at least one of your settings changes you turned on "apply on boot". You should never do that while experimenting, lest you accidentally apply the wrong thing and create instability, then it will absolutely keep rebooting on you. Only after you are sure your settings are stable should you turn that on.

As far as the notification itself, you can swipe to dismiss and it will be gone.
[G3 Android Development] neptune_:
You can turn off that notification from Kernel Adiutor settings, and just have a toast popup instead.
[G3 Android Development] jreink01:
Your right, i thought it was normal to turn on apply on boot. I have since turned it off. With booting and optimizing apps, under what conditions is it suppose to optmize apps. When i changed the governor, it again wanted to optmize apps?
[G3 Android Development] noidman123:
The only time it usually wants to optimize apps is when you wipe cache & dalvik cache and occasionally after app updates. Changing governors never requires a reboot, it does that all in realtime. I'm on the same rom, albeit a different kernel (nebula) but i also use Kernel Adiutor and have never had a message saying reboot to apply changes, that sounds like it could be another app. And even if you ticked "Apply on boot", Kernel Adiutor by default sets the on boot delay to 5 secs.

TL,DR: are you sure it's KA and are you sure you aren't wiping caches somehow? Maybe xposed or some other kinda mod? And for the notif saying reboot to apply changes, is that from kernel adiutor? Longpress it and it'll tell you what app its from.
[G3 Android Development] Mr. Jedge:
group chats not working for me :(
[G3 Android Development] leeroyjenks:
The lack of information is strong with this one.
[G3 Android Development] Krystalmyth:
Buttons set fine in the 'Candy interface' (Candy Shoppe, Shack, I mean, plz... Lol) menu when I originally flashed the ROM. No force closes. Its simply the most rock solid ROM I've ever encountered, even in this alpha state. That said bugs are expected. I'm unaccustomed to posting logs so excuse me if this isnt even the right one to post, but here it is. The entire buttons menu has vanished from thin air. I can't reset them or edit them again. Doesn't seem to be anything I can do other than reflash system to get it back. Just thought I'd share to help find out if its just me or something else. Never seen this issue before. Thanks so much for the sweet ROM, puns decadently intended I'm afraid. I've a taste for them.
[G3 Android Development] jreink01:
I have since done 2 different wipes and installs to try to track down what's causing the issues. I suspect it's either kernal auditor or the volume booster for lg g3 that i installed from the play store. This is my 3rd wipe and install and haven't installed either one and have done 2 test reboots and it's been rebooting fine.
[G3 Android Development] noidman123:
At least you narrowed it down. I'm not saying it's impossible that it's kernel adiutor but i don't think it is lol. I've been using it on both my d851 and my Note 2 and never had that.
[G3 Android Development] jreink01:
I'm kinda leaning towards the volume booster. I think that mod changes some settings in the buildprop, which i don't know much about but have heard it can cause havoc if modified wrong. Plus, if i remember correctly, i think i already had that mod installed when i installed kernal auditor and changed governor to lionheart. Can't remember for sure, I've wiped and installed so much today it all blends together.