yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] ptesmoke:
haha, yes I'm reporting that in this ROM and kernel combination it has solved the " bug" I was experiencing. I have no idea how, and no one believes me but every other ROM combination I was getting the half screen freeze every minute at least. its now been almost two straight weeks on omni and haven't seen it once.

and yes that issue on the thread you quoted. everyone seems to think its hardware but I'm fairly certain its software. a wise Dev has revealed to me there's a lot of missing and messed up code for mdss (low power state for display)
[Nexus 6  Original Android Development] wrongway213:
If you're right about mdss code being the problem.. wow. There will be a lot of surprised people, myself being one of them - if I remember correctly we had some of the best and brightest looking into that issue for a bit and nothing software related was ever found, or at least not reported on a large scale - it's widely believed to be hardware as you said. I'm quite curious as to what was pointed out to be missing - if it's some OT reading and you have a link, could you PM it to me so we don't clog the thread? However, I'm not sure it'll be OT at all - are there commits from Omni you have found that fixed this issue? Judging from the official Omni mainter's response to your post, I have a hard time imagining there are.. intriguing to say the least
[Nexus 6  Original Android Development] ptesmoke:
I'll pm you, don't want to clog the thread like you said. I just wanted to point out that either this ROM, or leankernel, or the combination of both has somehow fixed the issue for me, unless the "hardware issue" decided to eff off for 2 weeks lol. at any rate, pm incoming.
[Nexus 6  Original Android Development] Gandalf:
This is very much NOT ot :good: this is great info for everyone please discuss this here
[Nexus 6  Original Android Development] orlzzt:
Info on Sprint eCSFB issue

OK, I don't know if this is the place, but...

I am on Sprint. Anyone on Sprint knows that if you leave the network set to LTE, there's a good chance you won't get incoming calls and your SMS messages might be received by your recipient 2-10 times.

I was keeping my network on 3G, and that seemed to quell the issue with the multiple SMS messages and I could receive incoming calls.

NOW; using OmniRom and LeanKernel... I can leave my band on LTE and receive incoming calls! And FWIW, my texts are still only being received once per recipient. Whoo hoo! :good:

Jake..you are a miracle worker, apparently. Thanks for the great work!

EDIT: tried Code Blue kernel, and also receiving calls and texts while connected to LTE...
[Nexus 6  Original Android Development] ptesmoke:
OK so, here's where we are at, I had the half screen freeze "bug", seldom on stock but it existed. rooted and flashed chroma, still only happened occasionally. flashed CM, couldn't reproduce, flashed chroma and Franco kernel, issue was almost constant, clean flashed omni and lean kernel, haven't seen the issue once in two weeks

I touched base with Franco, he's fairly certain its a software bug, that google left a lot of messy unfinished code relating to mdss, hwcomposer, etc and that literally Steve kondik is the only person that could make any sense of the mess.

I'm in the process of testing out the stock kernel with omni shortly, and will be reporting my findings to [MENTION=3357040]Imoseyon[/MENTION] to determine if its a specific fix in his kernel. or to determine if it is somehow the ROM.

there's been a lot of theories as to what initiates this bug, one as of late was that the device had to be physically cold. so...being I live in northern Alberta I left my device outside in my truck in -25C for 2 hours, came back...no issue.

that's pretty much all I have at this point, more to follow with more testing..
[Nexus 6  Original Android Development] Gandalf:
Well, for omni I have the stock kernel per AOSP sources built in-line. CyanogenMod is the same way except they have a few small things like compilation fixes for OS X , lcd kcal and f2fs. Nothing changed in regards to mdss. It MAY be a display hal thing in hardware/qcom/display but omni hasn't made any changes above AOSP for the non-caf Hals. Cm is tracking a merged up AOSP/CAF for that afaik.

Try to get me the following when this happens:

Kmsg (not last_kmsg unless it forcibly reboots) and a dmesg. Logcat probably wouldn't yield anything useful in something like this but you could grab one as well, it wouldn't hurt.
[Nexus 6  Original Android Development] ptesmoke:
what's the easiest way to do this? I just went back to stock kernel, issue came back instantly, back on leankernel and its gone.

I'm now leaning toward something kernel side is causing it. regardless I'm gonna have to figure out how to narrow it down.
[Nexus 6  Original Android Development] Gandalf:
There's tons of ways to get these logs.

The app syslog will get them all at once and create a zip file you can upload here or use

adb pull /proc/dmesg ~/dmesg

adb pull /proc/kmsg ~/kmsg

adb logcat > ~/logcat
[Nexus 6  Original Android Development] ptesmoke:
OK, I more or less meant when the screen is all funky...what's the easiest way, likely adb pull eh? since when the screen goes half froze its pretty much unusable.

so, if I reflash stock kernel, reproduce issue and pull logs that's what were looking for correct?
[Nexus 6  Original Android Development] Gandalf:
Yup.

As long as you are using adb from a terminal on your PC, you will be able to use those commands whether the device is responsive or not as long as:

adb devices

yields a serial number and says "device" next to it.
[Nexus 6  Original Android Development] Circaflex:
the issue is when you set your phone to LTE only, via the dialer app. using Mobile settings and leaving it on LTE shouldn't result in missed phone calls and what not, the reason why is when you use the dialer code and set the unit to LTE only, Sprint AFAIK doesn't support VoLTE yet so of course it needs 3G to make and receive phone calls.
[Nexus 6  Original Android Development] Bingoig11:
Is there any way to use Google Now Launcher instead of Launcher3?

I successfully installed Google Now but when clicking on it in drawer, it asks me to first remove default action settings in Launcher3. When choosing settings it brings me to Launcher3 app but Default settings are grayed so I can't remove anything.

Try to remove the Launcher3 manually but got into bootloop.
[Nexus 6  Original Android Development] orlzzt:
I can't change the bands in the dialer app settings; only in Settings-- More-- Cellular Network Settings--Preferred Network Type.

On non-stock builds, I can't get into "Carrier Settings" without a FC.

I'm sure it's something with Sprint; however, I've tried many roms on the N6 and this is the first non-stock build on which I was able to receive calls while my network was set to LTE. (and only on Lean and Code Blue kernels. When I ran Franco with Omni, I still couldn't receive calls on LTE).

But thanks for your response! Hopefully, Sprint will get their act together one of these days.
[Nexus 6  Original Android Development] Gandalf:
I can look into adding Sprint ERI stuff to the device, but I use T-Mobile so I can only speak for that.

I have never experienced screen freezing or network errors at all on stock, both when I first got it out-of-the-box stock and the nexus stock images from Google ( which is the same thing), nor on my Omni builds, so I have no idea what could be causing these issues other than potentially crummy hardware. If you look at the sources on Omni github for the device and the kernel, they are both just about carbon copies of the AOSP sources per android-5.0.1_r2 tag for device (since there is not a 5.0.2 tag for shamu yet), and the shamu-3.10 tag for kernel. I only added one futex security to the kernel and the omni defconfig(which was just generating a full defconfig and renaming it), and the device tree just added small things. It could possibly be the vendor files, but again those are just about 100% direct copies from Googles open sourced binaries, with minor changes to organization and the hotword detection fix.
[Nexus 6  Original Android Development] _OverKill_:
compatible app layers?
[Nexus 6  Original Android Development] Gandalf:
Not yet. It is on gerrit.
[Nexus 6  Original Android Development] Mistertac:
I'm also on Sprint and have never had the issue with LTE and missed calls like you're talking about. Very odd , and I've flashed all sorts of stuff to this poor Shamu. I'm downloading Omni now actually.

I have had the multiple text issue but lately thats not been happening either.

If you haven't seen already, Asianflavor is working on getting SprintDM working with RR so we can get into Carrier Settings and update PRL and all that, perhaps if we all helped with testing this for either Jake or Asianflavor we could get it going.

Like Jake... He's not on Sprint so he needs testers.
[Nexus 6  Original Android Development] Gandalf:
Don't drop your shamus , just cracked mine good from a 6" drop
[Nexus 6  Original Android Development] Jn3622:
I so sorry
[Nexus 6  Original Android Development] orlzzt:
Thanks for the info! I am ready, willing, and able to test at any time....

View attachment 3186473

Were you using a case? I have the Spigen Ultra Hybrid. Haven't dropped it yet, but I'm pretty klutzy so I wanted to have the best protection possible, "in the event..."
[Nexus 6  Original Android Development] Bingoig11:
Oh bad :(

Put a glass protection on the screen and a silicone case since when I bought my N5 after 15 days I broke the screen...
[Nexus 6  Original Android Development] Lawlrus:
Some things never change.
[Nexus 6  Original Android Development] Gandalf:
No case just a tempered glass screen pro. Its all good, insurance replacement will be here tomorrow.
[Nexus 6  Original Android Development] orlzzt:
Good thing you have the insurance!

I might buy one of those glass Invisisheilds

Sent from my Nexus 6 using Xparent Skyblue Tapatalk 2
[Nexus 6  Original Android Development] Danish2980:
Any chance for a new build? Would really like to test latest merges ?
[Nexus 6  Original Android Development] Gandalf:
New build in OP.

"Changelog":

look at gerrit
[Nexus 6  Original Android Development] chasew83:
Happy to help test. I'm on sprint and might know a few other guys around here who would help.
[Nexus 6  Original Android Development] cfrank38:
split screen / multiwindow

Hy im a little outdated. I was reading about multiwindow / split screen feature of omnirom.

Is someone working on it ?
[Nexus 6  Original Android Development] Gandalf:
That is a very common topic regarding Omni, xplodwild has made several announcements about it, but lollipop nightlies have not even started yet...

also, preparing a new build w/ expandable volume panel

also pt2: don't expect to get full Layers support anymore.
[Nexus 6  Original Android Development] daftlush:
New update makes my screen split. Turning screen in and off fixes. Problem was on both lean kernel and Franco. What log would help?
[Nexus 6  Original Android Development] Circaflex:
most think its a hardware issue and not software. I purchased the nexus 6 at launch through Tmobile and had this issue, get a replacement and havent seen it happen once on the same roms and kernels i used before.
[Nexus 6  Original Android Development] daftlush:
I think it may be hardware. I left the phone by a window last night and I think the sun's rays may have over heated the phone and now this happens on every ROM on every kernel. Called tmo and replacement is on its way.
[Nexus 6  Original Android Development] Gandalf:
5.1 build is posted in OP.

Bugs I know about (so don't report them):

DRM content will fail (Play Movies, for example)

Global hotword detection is broken again

I WILL FIX THESE TOMORROW

Please report, WITH APPROPRIATE LOGS, any other issues you encounter.
[Nexus 6  Original Android Development] Tasssadar:
I noticed QSeeComd spamming the logcat with these:

D/QSEECOMD: (14693): qseecom listener services process entry PPID = 1
E/QSEECOMD: (14693): Listener: index = 0, hierarchy = 0
D/QSEECOMD: (14693): Init dlopen(librpmb.so, RTLD_NOW) succeeds
D/QSEECOMD: (14693): Init::Init dlsym(g_FSHandle rpmb_init_service) succeeds
I/rpmb (14693): RPMB Mult = 16384, Rel_sec_cnt = 1
E/DrmLibRpmb(14693): rpmb_init succeeded! with ret = 0
D/QSEECOMD: (14693): Init rpmb_init_service ret = 0
D/QSEECOMD: (14693): RPMB system services: init (Listener ID = 8192)
E/QSEECOMD: (14693): Listener: index = 1, hierarchy = 0
E/QSEECOMD: (14693): Init dlopen(libssd.so, RLTD_NOW) is failed....
E/QSEECOMD: (14693): ERROR: SSD_INIT failed, shall not start listener services

It can't find libssd.so, on stock ROM, it is supposed to be in /system/vendor/lib. After I copied it from the stock ROM, it stopped and qseecomd started successfuly - not sure if it breaks anything or not, I _think_ qseecomd is related to encryption somehow, is it part of that HW encryption by Qualcomm, the one that's disabled on nexus 6? Not very important if that's the case. I don't see libssd.so in binary blobs from google either, looks like they "forgot" to pack it in (it is in the package for hammerhead though).
[Nexus 6  Original Android Development] El Daddy:
Thread cleaned.

Please follow the directions of the OP when posting.

Thanks!
[Nexus 6  Original Android Development] Gandalf:
qseecom is part of drm and encryption. that build didn't have any widevine binaries, since they aren't part of the binaries provided by Google. I have another build in which I've added them (back, they were there before). If qseecom isn't spamming with those, then we don't need that file. If it still is, then I'll certainly add it in from Stock LMY47D, good find :good:
[Nexus 6  Original Android Development] sykopompos:
I can confirm with tassadar on it, I got that spam and added libssd in awhile ago to deal with the spam from it
[Nexus 6  Original Android Development] Gandalf:
Gotcha, I will have that added my next build. Thanks guys :good:

I am also removing all 5.0.x builds because apparently flashing a 5.0 ROM with a 5.1 boot loader is causing hard bricks. I will investigate this later when I have time.
[Nexus 6  Original Android Development] HaRdC0r3:
I have yet to flash a 5.1 rom but I flashed the bootloader and radio on my 5.0.2 ROM...it's temaseks ROM though
[Nexus 6  Original Android Development] sykopompos:
I've seen that on g+ about that happening. That's why I did my initial bring up of 5.1 testing on the n5 instead of the n6 like normal
[Nexus 6  Original Android Development] Skripka:
I have to say, the present build of Omni runs slick.

Even likes Viper 2.3.4.0 :good:
[Nexus 6  Original Android Development] R-Rizzo:
I'll have to get you a log when I get home. I'm not able to receive calls while on LTE. I'm on Tmobile and when I was on the stock image VoLTE was working. I think [MENTION=1050103]sykopompos[/MENTION] mentioned something about some missing IMS commits from AOSP that was causing problems.

Again, I'll try to get you a logcat when I get home from work.
[Nexus 6  Original Android Development] sykopompos:
Jake should have those commits from dhacker since he is in the same group chat
[Nexus 6  Original Android Development] R-Rizzo:
Well pewp
[Nexus 6  Original Android Development] sykopompos:
It was late last night and wasn't tested at that point (I did on my own earlier in the day because I noticed those same missing files) but then I ran into Sim card not detected for some users on my n6 bring up and reverted them out.

Zephik from chroma added them from that commit and ran into the same Sim card issue so most like trying to figure out what the cause of the Sim card not detected issue before adding the volte stuff
[Nexus 6  Original Android Development] R-Rizzo:
I ran into the SIM card not detected on your build too. Maybe I'll just go back to stock for a few days and try everyone's next round.
[Nexus 6  Original Android Development] sykopompos:
If you flash it over a build that doesn't have those extra missing files for volte and then flash a build with it, u don't have the issues because it only happens on clean builds
[Nexus 6  Original Android Development] Gandalf:
I'm going to check out the OEM partition tomorrow, along with some other stuff to see what I can find. Its finals week, and although i don't have any exams tomorrow, I have exams weds-fri. Meaning I need to study tomorrow -_-

But the IMS stuff is all good so far, we just need to figure sone specifics out with them. I still have a few things I want to figure out regarding it.
[Nexus 6  Original Android Development] GuyInDogSuit:
Since the 5.1 Gapps have been removed, what Gapps can we use?
[Nexus 6  Original Android Development] Bingoig11:
I'm using these banks gapps on my N10:

http://fitsnugly.euroskank.com/?rom=banks&device=gapps
[Nexus 6  Original Android Development] noonecanhide:
My call speaker & microphone were broken after dirty flashing omni 5.1 from 03/13. Just no sound. Fixed by flashing the 5.0 mixer configuration from the developers thread. Besides that all is fine.

Thank you jake02 for your work, and good luck for your exams
[Nexus 6  Original Android Development] GuyInDogSuit:
Running this so far with only one problem: The notifications crackle and navigation voice fades in and out.

I might try doing that too and see if it fixes it. Where can I find that file?
[Sprint LG G3] bassix187:
Anybody had any luck getting anywhere with getting us a working version of Lollipop, preferably with root? I know other versions of the LG G3 are getting some headway with this, some better than others. But like many of us Sprint user, looking forward to a working Lollipop for Christmas! Please and thank you Santa!

:D
[Sprint LG G3] CyanJustice:
We already have cm12, located in the G3 Original Android Development Forum.
[Sprint LG G3] aheeejd:
Looks like the mods moved those other threads that were in the wrong place & here we go again. Learn where to post. Its pretty simple, you got a question, it doesn't belong in development

Sent from my LG-ls990 using Xparent Green Tapatalk 2
[Sprint LG G3] acparker18:
This belongs in the Q&A section, not development. Please read the rules before posting. Also, not to be rude, but a quick Google search for the words "sprint g3" and "lollipop" would have returned numerous links to different builds of Lollipop for the LS990, not just CM12. Apparently no one ever searches anymore. People on XDA really don't like it when you start a thresd for a question that's been answered a million times elsewhere and is almost impossible to miss.

Mods please remove this redundant thread.
[Sprint LG G3] CyanJustice:
Where are you seeing other L builds? I just did a pretty extensive Goosearch and found nothing, save an article claiming to have a leaked build of LG L, which directed me to Mega, and I hate Mega with a passion.
[Sprint LG G3] gorillaz1:
Yeah I did the same, there are no Sprint LG G3 stock Lollipop builds in the wild that I see. Regardless this thread isn't in the right place.
[Sprint LG G3] AcE XBOX:
Check the Original Development section. Had my G3 running Lollipop earlier today.
[Sprint LG G3] 1619415:
Cm12?
[Sprint LG G3] ZangetsuSX:
Ok GOD! Bunch of morons in this place acting all tough and mighty.
[Sprint LG G3] 1619415:
Here maybe this will help u: http://xdaforums.com/sprint-lg-g3/general/sweet-coming-to-g3-near-t3022710
[One (M7) Q&A, Help & Troubleshooting] Claydelas:
From quite some time i have been having this problem, when if I wake my device after about an hour of off-screen time, my buttons act funky. For example when I go into the menu and try to back, it just vibrates once and nothing happens. After that i can neither press it again nor it vibrates. Same with Home button. I have to mash them/swipe them a couple of times for it to get it fixed and this whole thing lasts like 10 minutes. It's fine afterwards. It's not ROM related since I've went to stock full locked then installed 5.0.1 GPE Fresh. I had the issue on my last ROM (SkyDragon) as well and it really pisses me of. I am about to turn on the nav bar but I will be better off if i fixed it. Any suggestions ?
[One (M7) Q&A, Help & Troubleshooting] Bruce666:
I had the same problem on my old Xperia. You have to disable vibrations. Write here if it works
[One (M7) Q&A, Help & Troubleshooting] Claydelas:
Based on how random it occurs I can't tell for sure but it does make it better. Though I don't feel the good response like with vibrations :(
[HTC Desire 601] pthanaporn:
Could you please advise me for S-Off HTC Desire 601 Dual Sim :crying:
[HTC Desire 601] Child's Play:
If u r on jb, use rumrunner http://rumrunner.us/ if u r on kk, try sunshine http://theroot.ninja/ if it doesnt work, flash a custom kernel or rom
[HTC Desire 601] pthanaporn:
thank Child's Play, i try rumrunner and sunshine not work.

i looking custom or rom...... u can suggest?:)
[HTC Desire 601] Child's Play:
http://xdaforums.com/desire-601/development
[Nexus 5 General] Chad_Petree:
I don't know if it's been mentioned before but I was having annoying lag and stutters , I still am but it's gotten better , for me it was the Google music widget that I had on one of my homescreens ( I only have 3 homescreens in case you ask) , if you have it try getting rid of it and also deactivate the chrome option to have the chrome tabs shown on "recent apps /task switcher " also try to keep your recent tabs with the less amount of cards possible , I know that the fact that they're there doesn't mean they're opened , maybe it's a placebo effect but it feels like some those apps in there are really running in the background even when they're not supposed to do so, sometimes I used the app days ago and it is in the back of the "cards " and it still is running , they're called "recent apps" not opened apps ...

Google music with material design is really laggy ! I will get rid of it completely but its proving to be quite hard since I really enjoy having my music one click away on the cloud .

Chrome still has its "jank " and chopping scrolling sometimes but there's not much we can do .

I don't really understand the lag , it really it's random , sometimes I'm heavy multitasking and I have no issues and sometimes I'm just using chrome and twitter and it lags like crazy , or it just lags while scrolling on the home screen (google now stock launcher )

Have you had any of these issues ?

Gesendet von meinem Nexus 5
[Nexus 5 General] Ben36:
So are you basically saying if you have lag in an app. Delete the app and the lag will be gone? Lol... ?

Sent from my Android 5.0 Nexus 5
[Nexus 5 General] Citizen_Snips:
I use Play Music heavily. All access pass, it's my go to music app. Never noticed any lag on it though. I use it all day, every day.
[Nexus 5 General] borgsta:
System memory leaks have nothing to do with anything you mentioned.
[Nexus 5 General] jayRokk:
Do you even know how multitasking works??

:facepalm:
[Nexus 5 General] galaxys:
So what is the point of this thread? Your using LSD not Lollypoop! :D
[Nexus 5 General] pcphobic:
Have u tried custom kernel like Code Blue?
[Nexus 5 General] Ben36:
And if it lags just delete the kernel too

Sent from my Android 5.0 Nexus 5
[Nexus 5 General] Chad_Petree:
Well they're bogging the whole is down , the lag is not only on the app so I would suggest delete the app until it gets properly optimized Haha [emoji28]

Actually I do and that's why I'm saying it's not normal that they keep running in the background since they're not supposed to , I'm sorry if it sounded misleading ...

Read about it yesterday , I'm hoping it really is the cause of the issue but it looks like people with 5.0.1 are still experiencing lag , maybe we have to wait for 5.1?

Gesendet von meinem Nexus 5
[Nexus 5 General] Curiousn00b:
Jeez guys. Calm down. xD

It does says " If you're... "

He's just trying to help, lol.
[Nexus 5 General] Xlydven:
Google play music is really ****ty..so much lag
[Nexus 5 General] Bl4ckX:
It think you're mixing things up with iOS here. In Android apps are suposed to continue running in the background. It's on iOS where apps in the background are paused and which features no real multitasking.
[Nexus 5 General] Simonna:
I'm using Uber kernel and don't have any lags.