yashsingh1/xdaforums huggingface dataset:
[G3 Original Android Development] Savoritias:
I have the 08/01 build and I tried updating it to the newest one that came out tonight but

The cm updater doesn't work so I true the cyan updated. But it shows up a problem that says a problem showed up during the execution of xdelta. Only position independent executables (PIE) are supported. I tried changing the install location in the apps section to the internal storage but it didn't work. I also tried installing the latest version of cyan delta but I couldn't start so I installed a previous one. I don't have gaps installed. Is this a cyanogen mod issue or I did something wrong? I wiped the system before installing it completely.
[G3 Original Android Development] joaoennes:
Use cyandelta from playstore.
[G3 Original Android Development] rcrocks:
So this patch works then. Will they include it to nightly builds? soon? :confused:
[G3 Original Android Development] diogo.sena:
there's nothing wrong with february builds, stop complaining for nothing!

The only new problem is the bootanimation (which is january btw) , the rest are either old bugs, or your personal programs bugs..
[G3 Original Android Development] GTMoraes:
Do you, by any chance, use a lockscreen? A pattern?

I'm getting a very weird lock up when the phone wakes up and this is driving me nuts!

It seems to get longer the more it happens, or it's me that I'm getting more inpatient lol

I'm using a pattern lockscreen and Smart lock. This lock up never happened before.

Only thing that has changed since January is the kernel, that is now stock

Tapatalked thru my CM12 G3!
[G3 Original Android Development] diogo.sena:
yes i use, lockscreen problems are either smartlock (google app), or proximity (veryyyy old bug)

like i said, nothing wrong with february builds..

edit:

you said earlier that you disabled wakeup for google services.. and you use smartlock, a google app, think about it..
[G3 Original Android Development] GTMoraes:
Worked fine previously. But I'll consider this

I'll enable the wake-up

Tapatalked thru my CM12 G3!
[G3 Original Android Development] GTMoraes:
No dice. Enabled every wake-up, rebooted the phone, it still locks up

Funny that sometimes it locks up SO BAD that it doesn't recover anymore

BUT if I have a music playing, it'll keep playing, and then when it's over, plays the next song and so on.

Volume doesn't change, screen cannot be turned on/off, it doesn't respond to light sensor, calls are given as if the phone was off etc

---------- Post added at 16:19 ---------- Previous post was at 16:12 ----------

@diogo.sena may I ask you which modem are you using? Can't think of anything else rather than this

I'm using the 20H
[G3 Original Android Development] jez9999:
I'm seeing a lot of stuff about the new V20 modem firmware in this thread. I'm not convinced it's worth flashing such low-level firmware given that my phone is working OK at the moment. Is there a way I can tell what my current modem firmware version is?
[G3 Original Android Development] gee2012:
Just flash the latest 20H modem to be sure.
[G3 Original Android Development] diogo.sena:
Still on 20f... try airplane mode, try without smart lock... disable any mods, kernel tweaks, themes.. random flashable zips, etc

Sooner or later you'll discover the problem..
[G3 Original Android Development] GTMoraes:
That'd explain why some people are having problems, while other don't.

Maybe the 20H is giving the CM12 a bad time?

I've tried without smart lock, same thing.

There are no mods installed, nor kernel, themes etc

I'm almost doing a completely clean CM12, and by completely clean I mean even without GApps.

I'll try with Airplane mode on

----

same thing. I'll flash the 20f modem
[G3 Original Android Development] RL77LUC:
Well, bootanimation is a pretty big problem (and it's from january 31, stop quibbling...). There's also the max volume distortions (btw, I've tested this tonight, and well, with volume at max, there are distortions. Must be a recent issue, as 0130 didn't have this...), bugs about "No service" things and that kind of things.

That's not old or personnal, that's pretty big issues who started with 0131 build...

So, we do not complain for nothing, but the point of this thread is also to tell other people which problems they can encounter and share fixes. Deal with it.
[G3 Original Android Development] GTMoraes:
I'm guessing it will be the modem...

Sometimes after a lock-up, the phone wouldn't connect to 3G/4G, and required a restart to do so.

Also, I was getting a "No Service" on the lock screen, while right now, with 20F, it says my operator properly.

But it's still too early to say. It worked fine the first 10 minutes after a reboot, then everything went nuts

---------- Post added at 16:55 ---------- Previous post was at 16:53 ----------

lol no, max volume was there since the beginning. I reported it long time ago, but nothing's been done. There are more serious bugs to dealt with anyway

Yes, from 01/31, it went downhill

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

20F modem. Sweet lord Jesus, it's still locking up the lockscreen.

Time for a nandbackup and a absolutely clean CM12 install. wish me luck
[G3 Original Android Development] RL77LUC:
That's really weird, because I can assure you I didn't have this problem since CM12 official builds. The first time I've heard this is tonight, and I listen to music with max volume everyday...

The only things who differs to you is that I've disabled AudioFX. In first builds, sometimes, when I listened some music, it just crashed without reason, so I've disabled it to avoid this, and I didn't have this kind of problems (no custom audio drivers here). I'll maybe try Viper4Android, which has a custom audio driver, so maybe it'll work with this one ;).
[G3 Original Android Development] GTMoraes:
funny, tried to record the lockscreen locking up, and I could see the proximity sensor turned on and flashing, looking for something. Even with the screen off

Is it supposed to be turned on 24/7?
[G3 Original Android Development] diogo.sena:
all old bugs:

1. dt2w disabling or failing

2. proximity sensor in call and lockscreen

3. volume and distortion

---------- Post added at 06:43 PM ---------- Previous post was at 06:42 PM ----------

You said you use gravity ... ?
[G3 Original Android Development] RL77LUC:
1. DT2W disabling : kernel-side change, from 0131 build. I did not mention this one, since it's a custom kernel issue.

2. Didn't mention this one as well.

3. Never had it since 0202 build (my previous was 0130 and it was working fine), for me, it's not that old.
[G3 Original Android Development] GTMoraes:
Got rid of it this morning, to see if it was the culprit. It worked fine previously, but I have to re-run everything now. Seems like it wasn't

I'm still running a clean CM12 install. Nothing much to do with this super smartphone now, but gotta check if it's me or the CM12
[G3 Original Android Development] consumer2049:
So you are not getting any screen lockups even after a call?

Can I ask if you have these enabled?

- power button to end call

- double tap to wake

- which lock screen do you use?

Also, do you have gapps installed? Only asking because you said that the proximity sensor/lock screen thing is an old bug but I'm still getting it (completely stock cm12 with gapps) and looks like other people as well so must be a certain combination that it doesn't like.
[G3 Original Android Development] diogo.sena:
You misunderstand me, old bugs that still exist!

Screen lockups after call are proximity related.
[G3 Original Android Development] consumer2049:
Ahhhh! Ok that makes sense :)
[G3 Original Android Development] kroonys3:
Next nightly

http://review.cyanogenmod.org/#/c/87841/
[G3 Original Android Development] GTMoraes:
AND THE RESULT IS...

goddamn it seems to be buttery smooth. What did I do wrong?
[G3 Original Android Development] 573W1E:
Updated to the Feb 2nd nightly (black/blue boot animation) and boot times are incredibly long. Usually upwards of a couple of minutes, device then shows "Process system is not responding" as soon as it starts. Also, lock screen seems to ignore any input for a second or two when waking the device up.
[G3 Original Android Development] Meneldur:
Check post 1941 from materismos. Apply that file from recovery. Long boot solved gracefully here on 0204.
[G3 Original Android Development] GTMoraes:
After flashing gapps and letting Google download my apps, The lockscreen problem is back

Tapatalked thru my CM12 G3!
[G3 Original Android Development] GTMoraes:
02/05 build.

Finally the sound bug is gone.

Boot animation bug is still present (how come they didn't change this already?! It's just a Boot animation)

Random unresponsive phone after screen on (lock screen lock-up/freeze) still present

Had a System UI error while pulling the notifications bar

android.view.ViewRootImpl$CalledFromWrongThreadException: Only the original thread that created a view hierarchy can touch its views.
at android.view.ViewRootImpl.checkThread(ViewRootImpl.java:6254)
at android.view.ViewRootImpl.invalidateChildInParent(ViewRootImpl.java:902)
at android.view.ViewGroup.invalidateChild(ViewGroup.java:4637)
at android.view.View.invalidateInternal(View.java:11690)
at android.view.View.invalidate(View.java:11654)
at android.view.View.invalidate(View.java:11638)
at android.widget.ImageView.invalidateDrawable(ImageView.java:231)
at android.graphics.drawable.Drawable.invalidateSelf(Drawable.java:367)
at android.graphics.drawable.AnimatedVectorDrawable.start(AnimatedVectorDrawable.java:430)
at com.android.systemui.qs.tiles.PerfProfileTile$1.run(PerfProfileTile.java:82)
at android.os.Handler.handleCallback(Handler.java:739)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:135)
at android.os.HandlerThread.run(HandlerThread.java:61)

Reported, but I wouldn't hold my breath.

Are we a neglected phone? Builds from other models come first and then ours is served.

Are they doing stuff for other models, then inserting the compatibility bits to our device?

That'd explain why since 01/31 build some things went downhill

Tapatalked thru my CM12 G3!
[G3 Original Android Development] itsbighead:
04/02

Everything good, except theres a bug where when the battery hits less than 95% and the phone is restarted

All Battery usage statistics prior to that restart are lost

Happens in 02/02 as well
[G3 Original Android Development] MalekoUK:
People really need to stop reporting bugs from past nightlies...
[G3 Original Android Development] rocarizt:
But the problem is, some of the old bugs from old nightlies are still present.....

Gesendet von meinem LG-D855 mit Tapatalk
[G3 Original Android Development] bo-l:
0205 gallery app still crash. And still long second and third boot first boot is ok.

Sendt fra min LG G3 @ Android 5.0.2 Custom

---------- Post added at 07:41 AM ---------- Previous post was at 07:38 AM ----------

Some people report bugs on old builds. If they are running on 27-1 and some like they need to update to the latest and see if the bug still are present before they report. There are some who forgot this :)

Sendt fra min LG G3 @ Android 5.0.2 Custom
[G3 Original Android Development] itsbighead:
Does anyone get the problem where after phone has finished charging, if the phone is restarted while the battery level is greater than 90% in all instances the battery usage statistics prior to the reboot are lost everytime.
[G3 Original Android Development] diogo.sena:
That's not a bug, its a android feature

---------- Post added at 06:05 AM ---------- Previous post was at 06:02 AM ----------

Like everything in life, there's an order to build, why so much drama?
[G3 Original Android Development] rocarizt:
I misunderstood you. From this point of view you are right.

Gesendet von meinem LG-D855 mit Tapatalk
[G3 Original Android Development] JohnnyPhate:
Wipe fixed that for me.
[G3 Original Android Development] itsbighead:
Buddy, please explain why when battery level is lower than 90% the statistics dont reset themselves
[G3 Original Android Development] JohnnyPhate:
It treats >90% as full.
[G3 Original Android Development] itsbighead:
What thats so stupid. So what your saying is essentially when the battery is >90% and i restart the phone, Android OS thinks that i just unplugged my phone from the charger?

How stupid is that
[G3 Original Android Development] Novocaine88:
Wifi passwords always seem to be forgotten after EVERY flash. And often after every reboot too, however that's not consistent. Is this a known bug, or have I done something wrong?

I did a dirty flash from the unofficial CM ROM to this one a while back, always had the wifi issue with that ROM too. This is the most frustrating bug I've come across - seems like such a simple problem.
[G3 Original Android Development] MalekoUK:
Happens to me all the time, HOWEVER on 05 nightly it hasn't forgotten it this time :eek:
[G3 Original Android Development] Novocaine88:
Hmm, just flashed 05, passwords forgotten upon reboot :confused:

Also just restarted after flash - still happening.
[G3 Original Android Development] ateam_7:
Hello guys, i'm sorry to interrupt the discussion over the change logs of the nightly updates but can someone list ALL the stock features/apps that will be missing or won't be ported in cm12... i would like to know what I'll be sacrificing before i flash cm. Thank you
[G3 Original Android Development] diogo.sena:
never happened to me, a full wipe should solve it
[G3 Original Android Development] RL77LUC:
It seems to be random... When I was on unofficial, first time, it was always forgetting passwords. One day, I've wiped it : No more forgots. Then I came to CM12 official, and even after wipes, passwords seems to always be forgotten... I can't understand why.

That and the TWRP-vibration issues (one day, it just enabled itself after flashing CM12 without any visible reason, for me) are pretty weird issues...
[G3 Original Android Development] Novocaine88:
Might have to try that next - when I get the time - full wipes take so long :crying:
[G3 Original Android Development] tclayson:
I fixed it by going into /data/data and deleting org.telegram.messenger. I did the same for Google Now Launcher and they both download and work fine.

Looks like the directories were corrupt or something. Not sure how this happened.
[G3 Original Android Development] MalekoUK:
Peoples answer to everything.... As I said in my last reply, in last update it didn't happen, so its NOT a full wipe issue/fix. Seems to be an intermittent bug in the update process.

Also a full wipe would 'fix' it as you then have to re-enter the wifi password during setup anyway! :rolleyes:
[G3 Original Android Development] diogo.sena:
live with your bug, and quit annoying us then...
[G3 Original Android Development] MalekoUK:
So much for bug reporting hey?

You must get annoyed easily ;)
[G3 Original Android Development] JohnnyPhate:
Dirty flashed 0205 over 0203. Everything seems OK so far. No bootloop, gallery app works, dt2w works.
[G3 Original Android Development] diogo.sena:
Sorry, trying to track this thread is getting too hard i guess,

if i'm not mistaken its a selinux context problem, that command "restorecon" maybe will help too.. but a full format will definitely solve it..
[G3 Original Android Development] MalekoUK:
Full format is not the answer though... Doing a full format will obviously kind of solve it as you always have to re-connect to wifi on setup... but the point of a nightly build is that you don't have to full wipe every day. Kind of defeats the point.

Even doing a full wipe this problem can come back with another nightly. I'm sure this bug will get fixed, and as I said, didn't happen with 05 nightly :fingers-crossed:
[G3 Original Android Development] diogo.sena:
what you did'nt uderstand, is that is not a bug for todays nightly, its a bug in your setup.. probably will never get fixed if you didn't wipe at least one more time.. or if you fix by yourself ( try restorecon )
[G3 Original Android Development] NisseGurra:
Latest nightly runs without any bugs so far. Using 20f modem tho.
[G3 Original Android Development] MalekoUK:
*facepalm* what YOU don't understand is that i did a full wipe in the past and the bug came back.

My latest report is that it hasn't happened in latest nightly, that is what I was reporting. Got nothing to do with my setup. Now stop nitpicking and move on.
[G3 Original Android Development] omer323:
how does the new "Update Cyanogen recovery" feature works?

which recovery get installed? what happend if i update via CyanDelta
[G3 Original Android Development] RL77LUC:
As I said before, he's right, even a full wipe doesn't solve this issue. Sometimes the bug disappears, sometime not, without any reason. I've also tried full wipe, and after every nightly build flash, passwords disappears.
[G3 Original Android Development] JohnnyPhate:
Performance or balanced profile? Anyone tried to measure difference in battery life?
[G3 Original Android Development] bo-l:
I cant pick a sound for calls. Its says unknown sound. And when i click to pick Another sound settings shorts down. Its is on 5/2 build. I have made a full wipe

Sendt fra min LG G3 @ Android 5.0.2 Custom

---------- Post added at 02:19 PM ---------- Previous post was at 02:15 PM ----------

android.content.ActivityNotFoundException: No Activity found to handle Intent { act=android.intent.action.RINGTONE_PICKER (has extras) }

at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:1765)

at android.app.Instrumentation.execStartActivity(Instrumentation.java:1602)

at android.app.Activity.startActivityFromFragment(Activity.java:4340)

at android.app.Fragment.startActivityForResult(Fragment.java:1100)

at android.app.Fragment.startActivityForResult(Fragment.java:1084)

at android.preference.RingtonePreference.onClick(RingtonePreference.java:192)

at android.preference.Preference.performClick(Preference.java:983)

at android.preference.PreferenceScreen.onItemClick(PreferenceScreen.java:214)

at android.widget.AdapterView.performItemClick(AdapterView.java:300)

at android.widget.AbsListView.performItemClick(AbsListView.java:1145)

at android.widget.AbsListView$PerformClick.run(AbsListView.java:3046)

at android.widget.AbsListView$3.run(AbsListView.java:3835)

at android.os.Handler.handleCallback(Handler.java:739)

at android.os.Handler.dispatchMessage(Handler.java:95)

at android.os.Looper.loop(Looper.java:135)

at android.app.ActivityThread.main(ActivityThread.java:5256)

at java.lang.reflect.Method.invoke(Native Method)

at java.lang.reflect.Method.invoke(Method.java:372)

at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:898)

at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:693)

Sendt fra min LG G3 @ Android 5.0.2 Custom
[G3 Original Android Development] kjjjnob:
Booster sound :D

http://review.cyanogenmod.org/#/c/87906/

Finally, yeeeeeah :victory:
[G3 Original Android Development] lapocompris:
If you have read or searched a little bit, you would know that the reboot bug was related to the boot animation, just change the boot animation to cure it.

As for the USB connection, go to developper options and uncheck the debugging mode
[G3 Original Android Development] RL77LUC:
If you searched a little bit, you should know that we solved his problem few pages before...

Performance locks CPU to highest frequency available, so it will drain your battery very, very fast. Balanced is the "classic" behavior.
[G3 Original Android Development] Meneldur:
You think? That would be a pity, since our G3s are top notch devices with a decade of lifespan
[G3 Original Android Development] chrissk_2:
Hi all,

since the latest builds are a bit buggy, where can I download the 25/1 - 26/1 builds ? They seem to work well but they are deleted from the repos.

Does anyone have any other build to suggest that worked well ?

Thanks
[G3 Original Android Development] Meneldur:
0204 for one day.

Much much better battery usage. 64% now after 7 h of normal usage and many apps running. Applying the patch for boot animation solved the problem: 6 sec average.

Call bug still present. After a call the screen went off when putting the phone to sleep but the screen always showed the expanded notification panel, unresponsive as if an invisible overlay was there. Volume panel responded to taps but it didn't dismiss.
[G3 Original Android Development] GTMoraes:
Other models I mean other G3's.

Sometimes there are builds for, say, D850, and not for our D855.

Btw is it really "our" D855? Is everybody here D855?

Tapatalked thru my CM12 G3!

---------- Post added at 13:25 ---------- Previous post was at 13:16 ----------

And btw it's not meant to "live with a bug".

The reason there are nightlies is exactly to test bleeding edge stuff and report how's it going.

When people decide to lay back in a build, a tester is lost.

Since 01/31 I've been considering using a old build, as the phone was almost unusable for me, but I decided to give the CM guys a bit more time and things seems to be getting ironed out. 02/05 build still have the same bootloop bug and lockscreen bug, but it fixed the audio and feels overall faster.

Tapatalked thru my CM12 G3!
[G3 Original Android Development] bo-l:
Are there others on build 5/2 that can change the dailtone / notification tone?

Sendt fra min LG G3 @ Android 5.0.2 Custom
[G3 Original Android Development] GTMoraes:
I can

Tapatalked thru my CM12 G3!
[G3 Original Android Development] bo-l:
Mine just says unknown dailtone and if i try to change it settings stops. And its is after a full wipe.

Sendt fra min LG G3 @ Android 5.0.2 Custom
[G3 Original Android Development] GTMoraes:
I can change between stock and custom ringtones and notifications..

What did you flash with CM12?

Tapatalked thru my CM12 G3!
[G3 Original Android Development] javi_ruizs:
SD unrecognized

Hello there :)

I've installed this rom twice because when I finished setting everything up, my phone wouldn't recognize my sd card. When I turn it on, it seems like all the files are there and that I can access to them short after I start to use the phone, it seems as if ther was actually no card. Even ES-explorer says there isn't any sd-card to be found. If it helps, is a SanDisk Ultra 64GB microSD XC I.

Thanks in advantage

:)
[G3 Original Android Development] reepje123:
I got the 20150125 zip in CyanDelta, but it has 478,61MB, so I'm not sure if it's flashable.
[G3 Original Android Development] Rossyyy:
Anyone know how to get root working?
[G3 Original Android Development] reepje123:
you have to enable it in the developer options
[G3 Original Android Development] omer323:
a bug no one mentioned here before:

sometimes, after using the "Profile" tile, it disapears...

it's back if i remove it and set it back again
[G3 Original Android Development] tschmid:
Should be, if you import a fresh cm download in cyandelta you'll have a ~480mb file

Gesendet von meinem LG-D855 mit Tapatalk
[G3 Original Android Development] reepje123:
Ok great, so I could upload it for [MENTION=2988691]chrissk_2[/MENTION] if he wants me to
[G3 Original Android Development] hemo87:
The whole cm ROM is only 250mb...
[G3 Original Android Development] chrissk_2:
Please do, the phone is unusable at this point.

Thank you very much
[G3 Original Android Development] reepje123:
Here is it: dl.reepje123.tk/xda/cm-12-20150125-NIGHTLY-d855.zip

Note: It was imported into CyanDelta, thats why it has 478MB, but it should work
[G3 Original Android Development] hemo87:
Am I missing something here?

Why not just download from cm themselves?

http://download.cyanogenmod.org/?device=d855
[G3 Original Android Development] gee2012:
Don`t see an advantage of Cyandelta either tbh.
[G3 Original Android Development] RL77LUC:
Less data to download, and it can automatically flash additionnal ZIPs...
[G3 Original Android Development] gee2012:
Why is the Cyandelta rom almost twice as big as the CM rom?
[G3 Original Android Development] RL77LUC:
I didn't get that part, to be honest. I don't have this ~480MB ROM to download, deltas are usually ~15-25MB for me, as they should be... :confused:
[G3 Original Android Development] gee2012:
So users only have to download and flash the changed/patched files and new additions instead of the whole rom?