yashsingh1/xdaforums huggingface dataset:
[G3 Android Development] dantezinn:
Dat temperature...
[G3 Android Development] $am$am:
Anyone ?
[G3 Android Development] dcop7:
I'm on RR (still lollipop) and it works. Do you have any error?
[G3 Android Development] $am$am:
No errors it just did nothing. Working on XenonHD. Thanks for your reply
[G3 Android Development] daltendo:
I'm having the same problem. ls990. need dat hotspot for going around school firewall!
[G3 Android Development] RMarques:
Any good kernel recommendation to be used with this ROM and compatible with F2FS guys?

Sent from my LG-D855 using Xparent Skyblue Tapatalk 2
[G3 Android Development] randyrampage609:
Didn't know where to direct this question but problems with Instagram force closing when trying to upload a picture
[G3 Android Development] Cablespider:
Log?
[G3 Android Development] randyrampage609:
I have logcat not used to it yet how do I go about getting it posted
[G3 Android Development] randyrampage609:
This is what I got hopefully I did it right
[G3 Android Development] Visionikz03:
No caller id dialer bug still going strong. Missed a call and just shows "N" and the caller is not private because they left a voicemail and it announced their number.
[G3 Android Development] happyta5:
Have a couple of dsob using the lastest build. I switched to diff kernels but make no diff. I m using D852.. Switched back to 0201 build and no more problem...
[G3 Android Development] jionny:
volume control

great rom, thanks for al your hard work cuzz, I have a question, in the previous cm builds volume control was listed under tiles to add to notification drawer, however since aosp I have not seen volume control as a tile, is there anyway I can add it as one of the tiles for notification, Thank you
[G3 Android Development] jreink01:
Anyone else still having Bluetooth share FC on the most recent build? I am still getting them? Any suggestions?
[G3 Android Development] ridikolous:
Does weather in notif qs panel work you guys. I select the option but I can't see the weather info
[G3 Android Development] brand0ng:
best MM rom by far. only bug ive noticed is you gotta reinstall busybox via busybox on rails everytime you wanna remove layers.
[G3 Android Development] MBCO:
What kernel settings are you guys using. No matter what gov, voltage, GPU setting I seem to still get random reboots, hand warmer and glitchy lags
[G3 Android Development] Crotty.Josh:
Now this is just me. VS985 on Lionheart, Undervolt Global at -20. No heat and no lag. With the kernel that comes on the rom. So meh.
[G3 Android Development] MBCO:
Thanks, ls990 and I'll give it a try.
[G3 Android Development] jreink01:
Where is the lion heart governor?? View attachment 3665330
[G3 Android Development] Crotty.Josh:
If you look closely at what you screen shot and what I screen shot, you might find that one is not like the other. So two guesses on my end. One is the governor settings are not the same from one hardware to the next. Now I could be wrong, but I highly doubt that's the case. The second guess is your not on the same build/kernel. Which maybe the issue?
[G3 Android Development] Cablespider:
CPU govs; not GPU.
[G3 Android Development] Crotty.Josh:
For the sake of saving some time. Ensure your ROM and Kernel info (Respectively) are the same as my screens attached... If they don't then maybe that's the issue?
[G3 Android Development] Crotty.Josh:
I see what you did there, and now we are all the wiser.

Edit: In all my time of romming phones I have never edited the GPU in any manor to smooth out the ROM. Sense the GPU has very little effect on the ROM anyways, because the ROM is mostly rendered in 2D. Where as the CPU does all the heavy lifting. Someone feel free to correct me if I'm wrong.
[G3 Android Development] jreink01:
Cable spider answered it for me, thanks though.
[G3 Android Development] Crotty.Josh:
I merely agreed with his obvious observation. Although if you take a second look at the conversation I believe I was the one to answer all of your questions. Although I guess giving spider credit does make for a better plot twist.
[G3 Android Development] MBCO:
Same from what I can see
[G3 Android Development] dodgem2012:
I must be missing something, I'm not getting voice mails, just a text with the number. Do I need to set up voicemail again? Do I do it on MyVerizon or on the phone. Sorry I've been on mostly stock based roms, this is my first foray into ASOP since my Galaxy S3.
[G3 Android Development] Crotty.Josh:
Different conversation.
[G3 Android Development] Latentk:
Further testing basically confirmed that this ROM is working PERFECTLY. No errors outside of user error! Thank you for the great ROM!
[G3 Android Development] jreink01:
Hello I am using the stock launcher that came with the rom (launcher 3). This may be a silly question but how do I access the settings for this launcher? I normally use Nova and they have a app that you go through for settings. I didn't see a app labeled launcher 3.
[G3 Android Development] yochananmarqos:
Nova is based on Launcher 3, so it's the same. Tap Home while on the home screen or long press anywhere there's blank space.
[G3 Android Development] marcdw:
The Launcher3 I am seeing on recent ROMs has no configuration. One setting/option is all I see. A bit different from the one that was in LP ROMs it seems.

LG G3 D851, PAC-MAN ROM, Tapatalk 4.9.5
[G3 Android Development] iluvamk:
Can someone point me to navbar button color? Can't seem to find it.
[G3 Android Development] p70shooter:
There is no nav bar colour
[G3 Android Development] jreink01:
Ditto, same for me, only 1 option to change, unlike Nova.
[G3 Android Development] Ferdimage:
I have to say this rom is pretty fast and stable from the get go.

The kernel that comes with the rom is very quick on lionheart settings and using layers for the first time is pretty neat.

Than you for this awsome rom!

Just a small request, can we have an option to force media volume on volume press.
[G3 Android Development] jdgesmlls:
This ROM is great, very smooth and stable. The only issue I am having is when I am in a call (with the phone to my ear) my screen locks after my set timeout (1 min after screen off) and I can't wake the display up unless I hit the power button. It is especially annoying when I need to hang up from a call and the screen won't wake up. Is anyone experiencing this or know possibly which setting I need to change?
[G3 Android Development] mvez73:
Last version installed and it's fast and stable. The only issue I have is the theme that's going back to dark when I set it to light.

Envoyé de mon LG-D852 en utilisant Tapatalk
[G3 Android Development] justthefacts:
Stock kernel?
[G3 Android Development] mvez73:
Same here

Yes stock kernel for me.
[G3 Android Development] Cuzz1369:
Might not be ideal but there is a setting to have power button end call.
[G3 Android Development] jdgesmlls:
Yes, I am also using the stock kernel. I did read about the power button ending calls, but I remember this issue in 5.1.1 for some time and it was fixed.

I did some searching and found that Google Phone 2.21 (which is included in the 2/22 release) was suppose to address this. I found that Google Phone 2.3.17 was released on Feb. 3rd so I downloaded the apk and to my surprise I figured if I installed it, it would upgrade the dialer built in. This isn't the case, and it is its own stand alone app. So I have two 'Phone' icons in my app draw, but I now am using 2.3.17 on my home screen to dial out. I figured that incoming calls would still use the built in 2.21 version, and this might be the case....

Initial tests seem to be promising, I made a call and held the phone to my ear for about 90 seconds... took it away and screen lit right up...

I also called my phone from another phone, picked up the call and again held it to my head for about 90 seconds, took it away and it lit right up again. So a potential workaround is to install Google Phone 2.3.17 and use it as your normal dialer. I still don't know how it would change incoming calls but it appears to be working now... :p

Link on apkmirror:

http://www.apkmirror.com/wp-content/themes/APKMirror/download.php?id=58950

Anyone know if you can just replace the apk in /system/priv-app/Dialer/ and set the correct permissions to replace the one packaged with the ROM?
[G3 Android Development] yochananmarqos:
Link to the page, not to the direct download link.

No, Google Dialer has a different package name. There are flashable ZIP's around that add the proper system files / symlinks. I haven't tried it on my G3 yet.

Do some research and check the contents of the ZIP before you flash. Just pushing it to /system/priv-app is not enough for incoming caller ID.
[G3 Android Development] jdgesmlls:
Dialer fixed

I think I resolved the screen black issue with the dialer, here is what I did.

1. Download and install Google Phone 2.3.17 from apkmirror or equivalent.

2. Disable Phone 2.21 that is built into the ROM.

3. In 'Settings' -> 'Apps' -> 'Gear Icon on top right -> 'Default Apps', the 'Phone app' should have no default app listed. Click on 'Phone app' and choose 'Phone' (it should be the only choice as the default has been disabled.)

Try some test calls, outgoing and incoming. My phone lights up as soon as I take it away from my head, on multiple tests today.

Although this is not a huge issue, it tended to be quite annoying when trying to hang up from a call, needing to hit the power button and unlocking the phone.
[G3 Android Development] klo:
Just flashed this over the weekend - nice job!

A few things I've noticed (with solution), in case this helps anyone:

** GPS **

If you have GPS running in background already (e.g. using GPS Locker) but lose lock when switching to another application that makes use of GPS, try setting CAPABILITIES to 0x31 in /system/etc/gps.conf and reboot

May be a MM issue - see this post.

** bootloop after reboot / bootloop after optimising app **

I had a bootloop after disabling "Launcher3" (com.google.android.googlequicksearchbox) - leave it enabled after wiping system + data and re-flash.

Maybe another MM issue - see this post

** Taking call with headphone plugged in **

Caller can't hear me when I receive a call with a standard headphone (with no mic) plugged in - just unplug headphone to take the call.

** Stock FM app FC **

Use spirit2

** DT2W proximity check doesn't work **

No idea if this is cased by xposed or whatever - put phone in pocket screen facing out ;)

** Menu key missing in Navigation Bar buttons **

Set Menu Visibility to "Always show"

Clean flash (0222 build) with recommended banks gapps, xposed [gasp!] (appsettings, Lockscreen disabler, Xposed Torch)

(on a 10A > kdz-ed 30B > kingroot > autorec D855 16G)
[G3 Android Development] yochananmarqos:
Very informative post, however without logs it might be difficult for the developers to address the issues if they can't reproduce them.
[G3 Android Development] jreink01:
Does anyone know where the apn settings are? I tried settings-cellular networks-carrier settings but I get that process.com.android.com error window. Anyone have any ideas on how to fix this? I am trying to look into my wifi hotspot issue and I believe it could be related to apn settings.

On a different note, I have resolved a few issues that I was having that I wanted to share in case anyone else is having a similar issue.

Issue 1 not seeing any Storage files when connected to pc via USB.

Solution settings - developer settings - select usb configuration, toggle to charging then back to mtb, then you will see the files.

Issue 2 random reboots

I am using the zero lemon extended battery and case and last night discovered that the battery was a little lose in the case which I believe was causing a loss of power and the reboots. I put some tape around the edge of the battery so it is a bit snugger and haven't had a reboot yet that I have seen. This is not rom related but still wanted to include just in case others might also gave this issue.
[G3 Android Development] mvez73:
Anyone please? Thank you
[G3 Android Development] jreink01:
View attachment 3673087

Does anyone know why in a few different apps when I click on a drop down menu, the options are there but it blends in with the background of the drop down menu so I can't see the text. Would this be remedied by some setting in themes or layers, just asking. Thanks.
[G3 Android Development] Crotty.Josh:
For the last couple posts. There appears to be no issues with this ROM for many people. If you are having trouble with your install it maybe smart to observe some very basics. First you need to install fresh. Dirty flashing may introduce issues that would not otherwise be. Second is if you opt to use addons or third party kernels you assume risk of any malfunction that could be associated. Another words don't do it. The stock items work fine. Last but not least... Themes are not 100% stable sense they are designed for the base OS. This ROM is not 100% base. So know as soon as you install a theme you once again assume any associated risks.
[G3 Android Development] mvez73:
i wiped my phone couple days ago. I did a clean install and i didn't flash anything else like kernel or camera. Just the last build of Candy6 and my apps. The screen locked after a call seems to be fix with the installation of the google phone app on the play store. My other issue is the dark theme that always come back. I set it to light couple times a day because at one moment or another, it goes back to dark... Everything else is perfect. Battery life is awesome and performance is very good too. I really like this rom and for me it's better than every other roms i tested.
[G3 Android Development] jionny:
Concur, tried the above and works, Thanks
[G3 Android Development] Crotty.Josh:
With regards to your specific issue. What Gapps package are you using? What bootstack? Which phone?
[G3 Android Development] mvez73:
I always use Banks gapps and my phone is a d852. What is bootstack? Sorry i speak french.
[G3 Android Development] Crotty.Josh:
Bootstack is the firmware package for phone. http://xdaforums.com/lg-g3/general/quebec-lg-g3-d852g-videotron-t2970938 appears to have the ones for your phone in a TWRP flashable package.
[G3 Android Development] mvez73:
I never changed or touched that. What am i supposed to do with that?
[G3 Android Development] Crotty.Josh:
Make sure it's on the newest build. Sense the newest roms rely on your phone being up to date.
[G3 Android Development] yochananmarqos:
It appears to be a Layers theme specific issue.
[G3 Android Development] jreink01:
Ditto, worked for me also, on the first couple tests I've done.
[G3 Android Development] Klaus1983:
Great ROM!

Inviato dal mio LG-D855 utilizzando Tapatalk
[G3 Android Development] Crotty.Josh:
Ain't it the truth. Best ROM I have ever come across including stock OS's and going back 5 phones worth of roming. This ROM is butter.
[G3 Android Development] daltendo:
Agree with previous posts, this is a really high quality ROM. However, even after the most recent update for ls990, Hotspot simply doesn't work. Also, speaker mode is muffled, quiet, a d hard to hear. There are other small things, but these are probably the most important.
[G3 Android Development] jreink01:
Does anyone know where the apn settings are? I tried settings-cellular networks-carrier settings but I get that process.com.android.com error window. Anyone have any ideas on how to fix this? I am trying to look into my wifi hotspot issue and I believe it could be related to apn settings. Any help with this issue would be greatly appreciated.

Also, has anyone that has the ls990 installed xposed and if so, is there a tutorial or link I could follow to get it installed. I did a search but could not find anything difinitive. Thank you.
[G3 Android Development] jreink01:
For speaker gain, go to settings-kernel auditor-sound and you can change the speaker sound. Hotspot is still a issue I believe. I have asked for help with APN settings as l believe the issue with hotspot lies there.
[G3 Android Development] daltendo:
I tried adjusting the gain, haven't tested yet. Do you recommend lower or higher gain? As far as the hotspot, I hope a simple APN setting is the issue. Then it would be an easy fix rather than a kernel fix.

I just remembered a huge problem with this ROM that slipped my mind earlier. Randomly, while playing a video or a game, or even browsing instagram, the screen randomly dims and if a video or game is playing, it pauses. I'll turn the brightness up on my phone at night and it'll go back down. This happens with auto-brightness on and off, and I thought at first it was my blue light filter (twighlight app), but it still happened after an uninstall. This is not new either. This happened on my old CM12 ROM. I wouldn't think too much of it if it didn't pause videos and games on my phone as well, but am I the only one getting this? (ls990)
[G3 Android Development] souler456:
If your ROM has Adaptive Brightness enabled, try to disable it...

:D :) ;) :good:
[G3 Android Development] daltendo:
If it wasn't already clear, I did disable that already. I also don't think adaptive brightness would pause videos and games.
[G3 Android Development] jreink01:
I changed mine to higher gain and it is louder. Don't know about the APN, thats why I'm hoping a developer will chime in about that. With the video and games that pause, don't know, its not happening to me, sorry.
[G3 Android Development] gordo2212:
View attachment 3676574 cellular networks, access point names
[G3 Android Development] jreink01:
This is what I have, like I said, carrier settings does not open.View attachment 3676595
[G3 Android Development] randyrampage609:
My carrier settings also does not open and I get that error message too
[G3 Android Development] jreink01:
That's good to know it's not just me. Hopefully the developers will have a chance to look into this because if I remember right, it's FC ever since the alpha build.
[G3 Android Development] hokiealumnus:
Bug check: can anyone else confirm that Netflix won't play video on Candy?

I tried clearing app data, uninstalling/reinstalling and even a clean install with no success. It works on stock-based and CM-based ROMs, just not Candy (and maybe other AOSP ROMs?). YouTube & Amazon video both work fine, just not Netflix.
[G3 Android Development] p70shooter:
Just a heads up for you all. The rom is busy being rebased at the minute so updates will be a bit slow till we're up and running again.
[G3 Android Development] silvbm:
Rebased to? CM?
[G3 Android Development] p70shooter:
No still staying aosp and removing more if not all of cm stuff.
[G3 Android Development] Crotty.Josh:
I know I might get flamed for this, but I for one am glad. I have never had great experience with CM base. AOSP is much better IMO. Knowing how this project is going I'm guessing this dev will only do what's best for the project.
[G3 Android Development] p70shooter:
I choose Candy whatever it's based on but yes aosp is always better, especially with the way cm is going. As for the devs doing the best for the project, that's 100% right. They want to make the rom the best they can so that's why it's being rebased. A lot of work for them to do in there limited free time but it needs doing to improve Candy. The core features have been done, now it's just adding all the candy love back.
[G3 Android Development] mjjcb:
FYI, I'm running CM 13 with the ls990. I have the same menu options, and I get the same error. Must be a CM bug.
[G3 Android Development] jionny:
Yay!
[G3 Android Development] souler456:
CM sucks. AOSP rocks. I always loved pure AOSP ROMs, and getting it customizable like Candy is a real treat!

:D :) ;) :good:
[G3 Android Development] Cuzz1369:
Let's not start cm bashing please. No custom ROMs would be what they are today without the groundwork they have laid down and continue to improve and fix code whenever they can. Custom ROMs wouldn't exist on 90% of the devices(including g3) without them. I wouldn't say "they suck". They are just evolving into their own "OEM like ROM"
[G3 Android Development] LeoPosas:
"Android Kids" this days...Don't knew those times when CyanogenMod were the only "cool" ROMs out there, every android user, low until high performance devices wanted to install it. Memories...

Thanks to Cyanogen team, we have everything that can be customized and those thing that we want to personalize, CyanogenMod gave us the guide.
[G3 Android Development] jreink01:
With the newest Google phone app, it appears that any number not in my contact list is coming up private number. After doing more testing, it appears that even my contacts are coming up as private number now. Anyone have any ideas why this is happening? Thanks
[G3 Android Development] hokiealumnus:
Truth! My first ROM was CM on a first generation Motorola Droid. :)

Looking forward to the Candy re- re-basing. :laugh:
[G3 Android Development] Crotty.Josh:
Just want to be clear I was not CM bashing. I have both good and bad memories of CM. I just prefer AOSP. CM has always had its own set of quirks, but that does not make it bad. Like I said a bit back the truth is I have not seen a ROM up until now that I didn't have some sort of issue with. I appreciate CM just like I appreciate other major projects, but they always have an agenda that does not always mean including all phone. No big. That's why I'm thankful that this project is so amazing. For the first time I don't feel like I'm getting the leftovers. This ROM rocks and is rock solid. Thank you devs!
[G3 Android Development] jreink01:
Just in case anyone ran into the same issue as me, I am posting the solution. After contacting another developer, as I had no feedback on resolution, he suggested I made sure the new phone app was set to system app, did that and so far, working correctly. Just a fyi for others, hope this helps.
[G3 Android Development] jionny:
I did not encounter that problem, however on the third day of installing I did convert it to system app via Tibu
[G3 Android Development] jreink01:
That's how I converted the app to system. Seems to be working fine now, thanks for the feedback.
[G3 Android Development] hokiealumnus:
Found a simple, effective fix for this if anybody has this Netflix problem: http://xda-forum.blogspot.com/2016/01/lg-g3mm-fix-for-not-working-netflix.html?m=1

Works like a charm!
[G3 Android Development] yochananmarqos:
Keep your waiting to yourself. Not only is a post like this completely useless and a waste of space, notifying us you're waiting is a passive-aggressive way of breaking XDA rules. No asking for ETA's.
[G3 Android Development] jdgesmlls:
Is there any special instructions to convert to a system app in TiBu? I am trying to convert Phone 2.3.17 to a system app via TiBu and it has been "Processing" for about 10 minutes now....
[G3 Android Development] jreink01:
It did that to me too. After 15 minutes of processing I just rebooted to interrupt the process and when it rebooted, it worked.
[G3 Android Development] joosegoose:
Wait, this is really an issue with all MM roms? I've spent all evening switching around, looking for ROMs that might solve my speaker woes. On Resurrection Remix people could hardly hear me at all, then with this I could be heard fine but people hear an echo.

Should I just go ahead and use CandySix and deal with it since every ROM is going to have an echo? Any idea when we might have a fix? A functional speakerphone is a non-negotiable for me in a phone, I would even consider going back to pure stock if I had to for it.
[G3 Android Development] jionny:
it does that I waited one min the rebooted and it was converted
[G3 Android Development] hokiealumnus:
I know this is being re-based again, but I feel the need to say after finding the Netflix fix, using the Lion Heart governor and -15 global voltage, Candy is the ideal, basically perfect ROM. Thanks again for this excellent ROM!
[G3 Android Development] luca.digrazia94:
Is there a way in order to sue IR with a Aosp?

Inviato dal mio LG-D855 utilizzando Tapatalk
[G3 Android Development] hokiealumnus:
I use Galaxy Universal Remote from the play store.

Annoyingly, the IR blaster is pretty weak on the phone, but that doesn't have anything to do with the ROM.