yashsingh1/xdaforums huggingface dataset:
[G3 Original Android Development] roli0201:
After using this rom as a daily. My phone lost the simcard a few times. Don't know why. No service for 10 seconds. After it the phone reconnects normally.
[G3 Original Android Development] shephart:
It's a reason why this thread is experimental.
[G3 Original Android Development] Windforce0511:
No problems here.
[G3 Original Android Development] TheSpaceManatee:
He is not wrong to make a bug report, quit being so easily triggered. Bug report helps the dev to discover bugs. I for one also experience this problem once in a while.
[G3 Original Android Development] roli0201:
I'm reporting a big here. Still using it. Pls say nothing or something useful.
[G3 Original Android Development] Cablespider:
Speaking of being useful, you should be including a log when reporting. One report with a log is much more useful than 30 reports without. That's how development works: you test it and when it breaks, attach a log. It's expected of you when reporting in a dev thread.
[G3 Original Android Development] shephart:
But i know what bug report is. That wasnt bug report. :)
[G3 Original Android Development] TheSpaceManatee:
Have you ever considered that the sim card bug is very rare and when it happens one might not be prudent enough to capture a log of it? That doesn't change the fact that the bug happens and it's good for others to keep a lookout for it. The post that [MENTION=5141267]Shepar[/MENTION]t posted after was entirely useless. But I'll take note of that in future. /offtopic
[G3 Original Android Development] Fearup:
i have the same problem but on ALL roms CM13/fulmics/stock i found out its only on LTE it works fine on GSM on CM13 it goes down to no bars at all but i dont get no signal soo if some one calls me i still get the call but on fulmics and stock i get no service and i can get calls for a couple of seconds
[G3 Original Android Development] Cablespider:
Then it is even more important to try and capture a log during these times. Imagine the dev trying to hunt down a bug that he/she may not even be able to reproduce. With nothing more than a post to go off of, chances are the bug receives low priority. Have you considered what the dev has to go through? If people aren't willing to help the dev, then they really shouldn't be posting in a dev thread. Logs are crucial this early in development.

I'll tell you what doesn't change: your responsibilty as a tester.
[G3 Original Android Development] TheSpaceManatee:
My point is that the bug was quite rare and when it happened once I couldn't recreate it again to capture a log, but that shouldnt stop me from putting it out there so that others may be aware of this bug and capture a log for the dev. I didn't say that I deliberately did not want to make a log for it. End of story.
[G3 Original Android Development] rigogolder10:
Is theme engine included with the latest build?
[G3 Original Android Development] PM80:
Any valid kernel for LOS...battery drain is so called fast...
[G3 Original Android Development] engmia:
Hey, that did happened to me on the 24th nightly.

As far as I remember the case scenario was that I was encrypting the device which didn't have a lock PIN or password at the time (just a fresh install).

The encryption screen popped up, and it said it had 0 seconds left. It was stuck there (I waited quite a bit, over 5-10 mins), so I restarted it manually. Upon reboot however, in the Settings menu it said encryption was successful. I was able to proceed and add/change a password later on. Once I installed [MENTION=3362019]sleeplessnerd[/MENTION] 's recovery, I was able to decrypt the same install successfully too, however the password did get "baked" into the system, and I couldn't get rid of it even with adb format. I think that's a bug with the recovery, since when I reverted back to official 3.0.2.0, the adb wipe successfully cleaned the password.

If I had a password set prior to that, the screen did say "X amount of seconds left" and as far as I remember, did reboot automatically.

I'm currently restoring my device and about to encrypt it soon with the latest nightly, will report soon how it went.

No worries at all, I think it's a bug I've discovered in the recovery. I've tried pressing cancel, entered my password and any other combination scenario that I could've thinked of. I noticed that one of my partitions was named /dev/block/dm0/ (it's usually named /dev/block/0p41), unlike the other two which had their usual names /dev/block/mmcblk0p40 and /dev/block/mmcblk0p43. I think that is related somehow.

Also the brightness control doesn't work properly in this version, it only has 2 options: at 100% and if you set it at 10%, it changes the brightness to about 65-70%.

Everything else I've tested for now works. Pretty much minor stuff and nothing you can't easily work around. The two options in the brightness control are actually the only ones I need so..

Thanks again.
[G3 Original Android Development] :
With mine, on any nightly (tried on latest too), it just reboots and then proceeds to show me the insert password to decrypt screen, where the right password doesn't work and I end up having to clean flash.

I've given up at this point.. does anyone know any solutions?
[G3 Original Android Development] engmia:
There is a post literally above you in regards of encryption and how to get it successfully working in the recovery.....

It's not accepting the right password because it's a bug in the recovery you're using.
[G3 Original Android Development] :
I think the case scenario is kind of different...
[G3 Original Android Development] engmia:
I don't think it is mate. Are you sure you are using the recovery I have linked to? (@sleeplessnerd unofficial recovery). It's supposed to be blue like the original.

I have tried any other unofficial TWRP in the old thread (which is locked now, because OP discontinued support). The unofficial recovery from there is version 3.0.3.0, it's red coloured and it claims to have encryption working, but it DOES NOT work. I've tried every build in the thread.

Unlike the official recovery, it asks for a password as it's supposed to, but it doesn't accept the correct one.
[G3 Original Android Development] [GER]Roxxor:
While experimenting, please get logs! So finnq can iron out the issues!

Workaround for now: Encrypt WITHOUT a PIN/Password!(From phone settings). You will have to reboot manually at some point. (seems like finnq fixed that for the next build: https://review.lineageos.org/#/c/161915/) Then after you rebooted, your phone should be encrypted, but without a Password/PIN. Now you can set a PIN/Password and decryption should work.
[G3 Original Android Development] finnq:
Thank you. That's exactly the same scenario I ran into. I've spent two weeks fully understanding android's encryption layer and qc's hardware encryption support. The first problem which prevented already encrypted users from booting were mismatching qsee blobs that prevented the key master app from loading inside qc's trusted environment. The second problem that prevented encrypting the device without an already set pin was deeper inside qc's custom dm req crypt module. They forgot to properly release the holder which forced further actions like the test remount to fail.
[G3 Original Android Development] [GER]Roxxor:
You are talking in past tense. Does that mean you fixed it completely? That is awesome :)

Thank you for this :)
[G3 Original Android Development] darvincye:
same here
[G3 Original Android Development] fabriquesilver:
The battery drain is due to the fact that the device Doesnt go into deep sleep only briefly

NLP wakelock

NLP collector wakelock

And other google service wakelocks responsible for this...

Get BetterbatteryStats to see what's going on
[G3 Original Android Development] :
I'm sorry for the trouble, you were right :D . I'd just like to point out that mine reached 100% (I waiting for about 10min though) before needing manual reboot. I flashed TWRP, changed my security settings to none and began the encryption, adding the password and my screen lock later. This happened without any problem at all.

Thanks for the help :D
[G3 Original Android Development] darvincye:
battery drain so fast
[G3 Original Android Development] PrototypeZero:
Do you know how a possibility to prevent this? Other then going back to the previous build. The battery drain is a little annoying. Other then that, thank you for the impressive work finnq (and the LineageOS team in general)!

The G3 is now a proper device.
[G3 Original Android Development] finnq:
Yes it is :).

Without proper logs I can't help here, sorry. My battery life is insane I've never had such a good battery life as with Android 7.
[G3 Original Android Development] PrototypeZero:
Wow, fast response! Yes, battery life was great but not now anymore. What sort of logs would be valuable for you?

Then I will attach that.
[G3 Original Android Development] :
I'm not being able to decrypt my phone from TWRP... It's working when the device is booted though
[G3 Original Android Development] eradicator006:
No problems with deep sleep or doze here on my d852 (same kernel as d55 I believe). I actually hate doze. My phone spends most of it's time sitting on my desk and I end up missing lots of gmail notifications because of doze. I do get good battery life though.
[G3 Original Android Development] motoralbi:
Hello, I am experiencing random camera switching on during normal use: what happens is that when I use it, sometimes the camera turns on(laser focus is visible) and the phone obviously starts to heat and drain the battery.

What could this be? Using terminal emulator it just says it's Qualcomm camera daemon(taking up 20% of CPU usage).

Inviato dal mio LG-D855 utilizzando Tapatalk
[G3 Original Android Development] ZjemCiKolege:
Check my version recovery based on latest kernel working ota updates+3.0.3
[G3 Original Android Development] ninelore:
I have random reboots and sometimes they will be Bootloop's and I can't use my phone without plane mode. Logcats are impossible because I don't know when the Bootloop's occur. Please Help.

Edit: Data Wipe didn't help

(Post completely rewrote)
[G3 Original Android Development] eradicator006:
There is a way to post a log after a random reboot. After the phone reboots, grab the contents of /proc/last_kmsg and post that.
[G3 Original Android Development] ninelore:
last_kmsg don't exist on my phone. But now my phone is every time hard bricked (cant even boot into twrp (3.0.2.0official)) until I charge my phone. If it is on charger it will boot normally without problems...
[G3 Original Android Development] Sotiris02:
Consider buying a new battery.
[G3 Original Android Development] ninelore:
I got that idea too. I'll give it a try and report back
[G3 Original Android Development] engmia:
That's awesome, would you mind sharing a link for it and I'll test it ASAP.

Is it built by you?

---------------------------------------

[MENTION=4574857]finnq[/MENTION] bad news, looks like "Replace encryption password" seems to be working after all, but not as intented.

After choosing that option instead of having the same encryption and system password, now I am unable to change my encryption password (was able before since I changed it from the one I encrypted it with).

Also I get accidental touches on my phone during a phone call all the time. I can see the screen turning black, so it's not a wonky proximity sensor, but very often during a phone I press plenty of buttons, so the screen stays active even though it shuts off.

I need to focus not nearing the display to my face. I've been observing this behaviour for a long time now (it didn't came up in the latest nightly).

Please tell me if I can give some more relative information.
[G3 Original Android Development] rehawild:
Good

I had a trouble with 21C and 30C but now fixed. Thank you very fast and good designed rom :good:
[G3 Original Android Development] Jason Looi:
Hello, greetings to all. Would like to ask if there is any way to disable power menu and quick settings in lock screen, i've tried some apps frm the play store with no luck, hopefully you guys can help. Thanks in advance.
[G3 Original Android Development] RoadRunnR:
I have 3 (three) D855's that show variations of that problem with twrp (tried various versions of CM and Lineage since December). Most times they will not boot when on charger (LG logo appears, but falls back to charger symbol), sometimes they only boot when on charger (like yours).

All have original batteries and work normally once booted.
[G3 Original Android Development] oia12344321:
Is this normal? My Google services consume so much battery. Is not true that 1 day and 5 hours...I charge my phone many times per day but usually up to 80-90 and it doesn't take it as a full charge
[G3 Original Android Development] S.AMU:
[MENTION=4574857]finnq[/MENTION] : will the next build include aptx on the G3? If I understand it right you just need to add a line to say this phone is compatible?

https://review.lineageos.org/#/c/158337/
[G3 Original Android Development] pitbullx:
I confess I'm confused, first install the room, but do I need root first? And then I just zip room inside sd and, volume + - power and install?

or need more complete? if had tutorial for beginner and something like this put here.

thank you.
[G3 Original Android Development] [GER]Roxxor:
No it will not. aptx is a paid feature provided by Qualcomm. This means every device that is shipped without it, does not have a licence by qualcomm to use it.

If LineageOS would add this now, they could very well get into legal trouble. Therefor aptx will never be included in official builds for the G3.

But I think the standard aptx.zip should work ;) (Didn't test it though, as I do not need it)

http://lineageos.org/Last-Week-in-LineageOS-2/
[G3 Original Android Development] _Chacón_:
lg g3 d855 have aptX on stock :good:
[G3 Original Android Development] oia12344321:
than this means we paid for it when we bought our phones, right? so there is no problem if included in ROM after my logic
[G3 Original Android Development] subboxcb:
It will be included in next weekly release

https://www.cmxlog.com/14.1/d855
[G3 Original Android Development] G-UN1T:
problem

i have problem with entering into twrp, im using d85530b europe, and when root device with kingroot, i install twrp, and than cant enter into. its says like boot verification error... help, someone?
[G3 Original Android Development] ZjemCiKolege:
Hmm this probably don't without this

https://github.com/LineageOS/android_device_htc_pme/commit/f202f21ec6ca229b228d1feb4e5fde78533819ba

https://github.com/TheMuppets/propr...mmit/dada8d8576023a3e82af51ccec1d25a5d322868b

anyway you can test check this zip https://xdaforums.com/attachment.php?attachmentid=3990429&d=1483546137 :)

Updated zip :]

works only when new build from this week :)
[G3 Original Android Development] sochansam:
Edit: Changed my mind.
[G3 Original Android Development] _Chacón_:
Installed 20170221, as far I can tell (10 minutes) it works perfect. Although my headset support aptX, no idea if it's using it but it works. My network operator here is having dificulties and suggest adjust manualy the network setting. That was not working as expected on last weekly, and now it does. Wifi on 5Ghz, GPS ... audio routing, included 'mic' using a webrtc app throught chrome also works perfect, internal and through bt. *** GREAT!. ***
[G3 Original Android Development] AdamWill:
Is there any way we can request a rebuild of the 'experimental' images?

I'm on the d852, and while the new weekly is available, the 'experimental' build is still 20170206. As discussed a bit upthread, that build cannot access previously-encrypted devices - so I can't complete the transfer from CM 13.0 to LO 14.1 using the posted instructions, as I cannot get into the 'experimental' build.

Thanks!
[G3 Original Android Development] kaankandemirrr@gmail.com:
Download and Update

Hello guys ! ,

I am the new on lineage os for lg g3. I have checked for a new version in the about section of settings with lineage os updates section. My device found a new version and then I touched to download. After download finished I said reboot and install. I was expecting lineage will upgrade itself (because CM was doing on my galaxy S2) but my phone is jumped to TWRP recovery menu. Unfourtnatly I could not found image file which I download before. And stuck on the recovery for a while. And the oldest way I download again from website lineage latest release I did system and cache wipe and then install the latest version. After that phone became the normal status.

Does line age os could not update itself ? how should I call it OTA update kind of :) really did not know sorry.

Could you please somebody explain it to me ? According first update my phone was the disaster for me I spen 1 hour to update my phone could not be hard like this :confused:
[G3 Original Android Development] ninelore:
My new Battery arrived and solved the problem.
[G3 Original Android Development] boxama:
The updater downloads the zips to /data/data/org.lineageos.updater/app_updates.

It seems TWRP can't install the updates automatically. Either install the included recovery (developer options > Update recovery), or do the process manually each time.
[G3 Original Android Development] kaankandemirrr@gmail.com:
Thanks for the quick reply :) :good::good: now ı have enabled update recovery in the developer options. So then can I update my phone automatically when I download OS ?
[G3 Original Android Development] subboxcb:
How about updating other things like OpenGaaps zip, SU zip, .....? I have never used before so I would like to know how it's behaving for later use?

Thank you.
[G3 Original Android Development] kaankandemirrr@gmail.com:
Everything seems like working good. I did not reflash gapps and modem. I am not flashing either SU zip because I could not be sure which is for LG G3 :) arm or arm64
[G3 Original Android Development] dszymek:
For G3 is Arm
[G3 Original Android Development] ZjemCiKolege:
Any who have problem with ota updates install this recovery decrypt should be work

https://www.androidfilehost.com/?fid=529152257862700859 [MENTION=8089963]kaankandemirrr@gmail.com[/MENTION] [MENTION=7777276]boxama[/MENTION]

And for any people who say g3 stock don't have aptx

https://www.aptx.com/products/lg-g3-smartphone

[MENTION=2923886][GER]Roxxor[/MENTION]
[G3 Original Android Development] el_angelo:
I'm still running cyanogenmod 20161224, can i just dirty flash lineageos on top of it? or should i wipe?
[G3 Original Android Development] Magnum44pl:
Flash experimental first, next flash weekly.
[G3 Original Android Development] subboxcb:
You can use experimental build to migrate and then weekly build or directly install new build with full wipe.
[G3 Original Android Development] ZjemCiKolege:
Any who have aptx headphone/speaker support test this zip and check in logcat which codec is select if aptx its good :P
[G3 Original Android Development] oia12344321:
Does VoLTE works? If I go to hidden menu (*#*#4636#*#*) is there an option "VoLTE provide"

Thank you!
[G3 Original Android Development] Quatro7:
It is possibility to remove # mark from notification bar?

Wysłane z mojego LG-D855 przy użyciu Tapatalka
[G3 Original Android Development] darvincye:
i think theres a bug on newest build, sometimes screen wont open
[G3 Original Android Development] subboxcb:
Works fine on my phone
[G3 Original Android Development] TwinHeadedEagle:
Bug with Private Number still not fixed. When I call someone in my Call Log it says Private number instead of contact name. Is this a bug or something I don't know?

Is there a recover that can install Lineage update automatically?
[G3 Original Android Development] mistercheese:
I dont have that. Check your carrier setting
[G3 Original Android Development] matze779:
Sorry, but I think, the only way is with xposed.
[G3 Original Android Development] Quatro7:
ok, shame..

And can disable quick launch camera double pressing the power button?
[G3 Original Android Development] clem_ita:
Dear [MENTION=4574857]finnq[/MENTION],

if I'm allowed, I'd like to draw your attention on this fm radio bug. FmRadio has erratic behavior. It works fine for some time after a clean flash of the rom, then it stop working all of a sudden, without any obvious reason. When the bug starts, the only solution is a complete wipe of the device and a new clean flash. A simpler clearing of app data does not work as a fix.

I've grabbed a logcat while affected by the bug. I've just opened the app, let it play the radio for some second through headphones, then switched to lodspeaker, then back again to headphone. Then closed the app.

Some errors jump to my eyes and repeat themselves multiple times in the log, including:

02-15 22:20:13.476 23602 24238 E android_hardware_fm: could not open file for read
02-15 22:20:13.476 23602 24238 E android_hardware_fm: Error in loading threshold file
02-15 22:20:16.635 23602 23602 E FmMainActivity: onOptionsItemSelected, invalid options menu item.
02-15 22:20:23.313 275 24250 E audio_route: unable to find path 'capture-fm'
02-15 22:20:23.333 275 24250 E ACDB-LOADER: Error: ACDB get adm topology for acdb id = 0, returned = -8
02-15 22:20:23.333 275 24250 E ACDB-LOADER: Error: ACDB audproc returned = -1
02-15 22:20:23.334 275 24250 E ACDB-LOADER: Error: ACDB AudProc vol returned = -1
02-15 22:20:23.334 275 24250 E audio_route: unable to find path 'capture-fm'
02-15 22:20:23.345 275 24250 E audio_hw_primary: start_input_stream: cannot open device '/dev/snd/pcmC0D0c': Device or resource busy
02-15 22:20:23.732 275 22753 E audio_hw_primary: start_input_stream: use case assigned already in use, stream(0xb3efd480)usecase(9: audio-record)
02-15 22:20:23.756 275 22753 E audio_route: unable to find path 'capture-fm'
02-15 22:20:23.776 275 22753 E ACDB-LOADER: Error: ACDB AudProc vol returned = -19
02-15 22:20:23.838 275 22753 E audio_hw_primary: start_input_stream: cannot open device '/dev/snd/pcmC0D0c': Device or resource busy
02-15 22:20:35.317 275 24250 E audio_hw_primary: stop_input_stream: Could not find the usecase (9) in the list

Full log is attached for your convenience.

Kind regards
[G3 Original Android Development] armSeb:
The fm radio issue seems to be caused by the "OK google" feature:

jira.lineageos.org/browse/REGRESSION-71

I completely disabled this feature, the fm radio seems to work fine again (I need some time to confirm that).

Instead of flashing, you can use the "spirit fm" app (this app fixes the mixer settings, allowing the base fm radio app to work again).
[G3 Original Android Development] subboxcb:
Go to Settings/gestures
[G3 Original Android Development] finnq:
[MENTION=3877496]clem_ita[/MENTION] Thanks for your detailed report but please fill a bug report at jira.lineageos.org.
[G3 Original Android Development] finnq:
[MENTION=3362019]sleeplessnerd[/MENTION] Do you want to push your twrp encryption commit to https://gerrit.twrp.me/#/q/project:android_device_lge_d855?
[G3 Original Android Development] amirseni:
Sign system appplication

Hi,

I'm trying to get the LG Remote running on the weekly lineageos which requires the QuicksetSDK. It is a system app however when adding it to /system/app, i get this error from logcat:

PackageManager: Failed to parse /system/app/QuicksetSDK: Signature mismatch for shared user: SharedUserSetting{f3fcda3 android.uid.system/1000}

from what i could gather from a gg search: i have to sign the apk using the platform keys for los14, which i got from https://github.com/LineageOS/android_build/tree/cm-14.1/target/product/security

i signed the apk with the "java -jar signapk.jar platform.x509.pem platform.pk8 QuicksetSDK.apk QuicksetSDK-signed.apk" and it exits with no error.

Is this the proper way to do it? Do I have the right certificates?

Thanks
[G3 Original Android Development] finnq:
[MENTION=813053]amirseni[/MENTION] No, this isn't the right key. The key we use for official builds will not be published. However it should work if you push the apk to /system/priv-app.