yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] jlvlawrence:
What exactly are these dead locks I keep reading about? I don't have a nexus 4, but I've been rocking the Marc Landis builds on my manta and toro for the last two weeks without problems.
[Nexus 4 Original Android Development] Jubakuba:
Haven't brought my manta/grouper up to 4.3...but my old toro which I've been testing stuff I'm working on (aka seldom use so not a candidate for a bug-free confirmation) doesn't seem to have 'em either.

"Deadlocks" as they're being called is when your phone basically poops out while you're texting or something and the screen basically locks up.

Different from lag, I'm guessing, but again I haven't experienced them.
[Nexus 4 Original Android Development] antrobi3:
Back to AOKP,coming from CM 10.1.3.Only thing i miss from this rom is the option to call phone numbers directly from the sms app (like missed call messages from the operator).Anyone ?
[Nexus 4 Original Android Development] notbrodie:
to get rid of the deadlocks, use faux kernel. anecdotal evidence says that no one on faux gets them
[Nexus 4 Original Android Development] kurniawan77:
I've got the phone icon on top of Messaging.

---------- Post added at 08:42 AM ---------- Previous post was at 08:42 AM ----------

+1
[Nexus 4 Original Android Development] JG:
that is exactly what it is ,

JUST

Anecdotal evidence !
[Nexus 4 Original Android Development] nikwen:
I'm on the 2013-09-27 build (updated from 2013-09-20) and I haven't experienced them yet.
[Nexus 4 Original Android Development] ben_pyett:
if anyone had some solid evidence based comments or facts on the matter then please share...

As that comment made me attempt to post in faux thread (for first time as a Franco user) and ask question from a larger audience hopefully with many AOKP users with regards deadlocks and the faux kernel.

Although the Gods of android seemed to conspire against me and I literally experienced several deadlocks in quick succession while composing the text of the post, by far the worst instance of deadlocks that I'd ever experienced before (as they're often days apart), and then to add insult to injury I then got a tapatalk permission error and it crap'd out so I lost the actual post and contents......
[Nexus 4 Original Android Development] shr33kant:
Deleted....
[Nexus 4 Original Android Development] pughie:
Running official nightly with hells core b38 and not yet had a deadlock, have tried sending and receiving numerous texts as this usually causes my phone to lock up but so far so good!
[Nexus 4 Original Android Development] nikwen:
Wow. Cool. An official 4.3 nightly: http://aokp.co/devices/mako

Thanks. :good:

EDIT: I think I'll stay with Marc Landis' builds though.
[Nexus 4 Original Android Development] wcn:
AOKP hybrid?

Hi,

Came from bigxie PUB 4.2.2 upgraded to a few JWR based 4.3 ROM and currently on Kecinzer 26/09 build.

Tried a few JSS kernel = screen tearing/stuttered.

Tried a few JWR kernel = zero lag/deadlock.

Can anyone that has installed Official version (or other Devs' build) verify that the ro.build.fingerprint on your build is JWR or otherwise?

AOKP hybrid?
[Nexus 4 Original Android Development] nikwen:
I'm on Marc Landis' build and it says JWR66V.
[Nexus 4 Original Android Development] Black River:
The new nightly is top! Thanks!
[Nexus 4 Original Android Development] andy_rose:
Good battery life on ml build 20.09

See there is a new official nightly, that is cool.
[Nexus 4 Original Android Development] JaylanPHNX:
I'm on the 9/26 ML build and it says jls, which works with the jss version of Faux123's kernel. (No deadlocks BTW).

Sent from an N4 blessed with AOKP and sanctified by Faux123!
[Nexus 4 Original Android Development] nikwen:
That's what I get, too, if I go to the settings > About phone > Build number.

However, he asked for the "ro.build.fingerprint" value. So I downloaded a build.prop editor and searched for that value. It said "JWR66V". It seems to be something else than the ROM build number.

(The kernel can only be JWR or JSS, not JLS.)
[Nexus 4 Original Android Development] Jeeeenx:
I use a JSS kernel with JLS roms. JWR give screen taring problems. AFAIK latest AOKP nightlies are built on the latest instance of the Google source, which is JLS.
[Nexus 4 Original Android Development] JG:
You know with kecinzer last build the funny thing is that to me it works so much smoother with a JWR kernel such as the linaro kernel from LaboDJ which is just a modified franco kernel built with linaro.I get no deadlocks or screen tearing at all! that while I am sticking with it for now!]

EDIT- I sent him a PM to clarify why it is like that .Hopefully he will reply back to me!
[Nexus 4 Original Android Development] Mercado_Negro:
Is the GlowPad working for someone in this first nightly? All options are there but I can't seem to make it work. TIA.
[Nexus 4 Original Android Development] Jubakuba:
Which one?

Phone, Alarm Clock, Lockscreen, Navigation Ring, ROMControl>Lockscreen, ROMControl>NavigationRing?

:p

I'm assuming you mean torch?

Nothing has changed...

One thing though...

Torch...if you reboot while it's on: the setting that says "torch on" stays on.

Glowpad torch has a check to make sure it's not dicking-about with your torch when it shouldn't be...

So go and toggle on/off elsewhere and see if that fixes it.
[Nexus 4 Original Android Development] Mercado_Negro:
As usual, you make a post about it and when you try it again, without changing anything, it works... Classic :p

Thanks Juba, I tried to make it work before going to bed, even rebooted a few times, and just left it alone. Now, I wake up, make my coffee, drink it while reading XDA and thought "let me ask about it"... Once again one your leprechauns fixed it for me :D Cheers mate!

[EDIT] Do you think it wasn't working because I didn't have Google Search installed? That's the only thing that changed in my phone during the night (I flashed BanKs' GApps and left all Google Apps downloading before going to bed).
[Nexus 4 Original Android Development] npiper05:
Sorry for the simple question, but couldn't find answer in search. Is it possible to remove the persistent Google search bar with the stock launcher?

I'm running the last nightly (4.3). Running smooth so far. I was most recently on stock, but have run almost every ROM possible and end up coming back here for the features.

Keep up the great work.
[Nexus 4 Original Android Development] dankoman:
if i recall correctly, juba said some time ago that it required google now (google search) to be installed in order to function.

edit:

ah, yes - here it is:
[Nexus 4 Original Android Development] JG:
If you cant find your answer to get it how you want it .You can always use nova launcher and that has that feature for sure.
[Nexus 4 Original Android Development] Jubakuba:
My dumb face said that?!

Mispoke a little...

Navring won't work. Lock still should.
[Nexus 4 Original Android Development] BLADESMAN1889:
Root Explorer does the job.

System/build.prop

Sent from NEXUS⁴ via XDA Prem [AOKP 4:3 Previews]​
[Nexus 4 Original Android Development] dankoman:
we knew what you meant.

(you should've blamed it on autocorrect though :p)
[Nexus 4 Original Android Development] jokermithun:
hello which clock widget u use:)

Sent from my Nexus 4
[Nexus 4 Original Android Development] BLADESMAN1889:
It was a reply to my post about not having the lock ring work.

& guess what ? It still doesn't :) I don't care anymore as Nav Ring works fine.

I have come to the realisation that I have a very unique Nexus⁴, somehow mine rolled off the production line with the wrong DNA - which caused my nex to be a female NOT a male.

Though only a phone it has the same genetic defects as the human female.

Hence only the Nav Ring works. Time of the month is permanent with female nexus⁴.

Sent from NEXUS⁴ via XDA Prem [AOKP 4:3 Previews]​
[Nexus 4 Original Android Development] evonc:
Is notification bar glow colour not working for someone else? I tried to switch it from holo blue to white and the colour chooser shows white but the glow colour is still holo blue.

Sent from my Nexus 4
[Nexus 4 Original Android Development] nikwen:
If I remember right, you have to click on the rectangle in that color to apply it.

EDIT: Yep, works.
[Nexus 4 Original Android Development] andy_rose:
it is uccw with motif clock from the uccw widget thread.
[Nexus 4 Original Android Development] fone_fanatic:
So now that nightlies are "official" should we be expecting a new thread or is this one's first post and title just going to be edited?

These are crucial matters to how well this ROM works on my device.
[Nexus 4 Original Android Development] maghig:
Got a rather strange issue with the navring. It will randomly reboot when swiping to a target. No pattern to it that i have noticed, I have three targets set up and they all will do it occasionally.

Its been doing it for a while, i was still on the nightly from a month ago until I did a clean flash to yesterday's. I hoped it would fix it but no luck.

Franco kernel with stock gapps.
[Nexus 4 Original Android Development] wcn:
On Kecinzer 26/09 build, WCNSS_qcom_cfg.ini has not been patched as other JWR based ROM.

gEnableActiveModeOffload=0

hostArpOffload=0

Can anyone verify theirs either Official or other Devs build?

I believe this is a hybrid build. No screen tearing nor deadlock with JWR kernel.
[Nexus 4 Original Android Development] Mercado_Negro:
I seriously doubt that could be possible. As far as I know the kernel is either JSS/JL or JWR, it can't be both. Same with the ROM.
[Nexus 4 Original Android Development] Stoozak:
Anyone else still have the black lockscreen on the latest (28/09) build?

Even after I've set a background it remain black...
[Nexus 4 Original Android Development] abjexstallion:
Rom Control/General UI/Transparency Settings... Change the last one "Lockscreen to 0". It should work.

After all... It's a NEXUS!!!
[Nexus 4 Original Android Development] Mercado_Negro:
Fingers crossed for those blobs update for mako :D
[Nexus 4 Original Android Development] Joloxx9:
Which blobs?

Wysłane z mojego Nexus 4 za pomocą Tapatalk 4
[Nexus 4 Original Android Development] Mercado_Negro:
http://gerrit.aokp.co/#/c/12756/
[Nexus 4 Original Android Development] dankoman:
these ones
[Nexus 4 Original Android Development] ben_pyett:
Someone explain to the stupid people like me, will the blobs help with deadlocks? Are these the same changes that CM have made? That appear to have caused and led to the 'feck' fest and anti swearing reaction and subsequent follow up argument that's currently occurring over in the Franco thread? After CM change?
[Nexus 4 Original Android Development] Mercado_Negro:
If I recall correctly, SlimBean team tried a few things before switching to hybrid. These blobs were one of those things, hence my fingers crossed lol

These deadlocks are tied to the kernel level and those blobs are kernel related if I understood that commit correctly.
[Nexus 4 Original Android Development] dankoman:
:laugh: just spent the last 10 minutes catching up on the drama in the franco thread. unfortunately, mods deleted the good parts. it was entertaining, nonetheless.

anyway, stupid is entirely different from uninformed, Ben. this may help explain though:

http://en.wikipedia.org/wiki/Binary_blob
[Nexus 4 Original Android Development] FishFan319:
No audio from ear piece during calls unless on speaker. I searched and found a similar post a bit earlier. The other user had to install the .84 radio? Has anyone else found this problem?
[Nexus 4 Original Android Development] wcn:
Hybrid build (ROM) = JWR base + performance patches from JSS/JLS repos.

There are a few hybrid mako ROM that are freeze free.
[Nexus 4 Original Android Development] Jubakuba:
Delete
[Nexus 4 Original Android Development] Mercado_Negro:
I know about that. I was talking about a ROM which could accept both types of kernel or kernels which could be used in JSS/JLS and JWR ROMs at the same time, which isn't possible at the moment.
[Nexus 4 Original Android Development] casmelad:
Which kernel recommend you ? Matrix,neo, hells or faux?
[Nexus 4 Original Android Development] Mercado_Negro:
Stock or franco.Kernel
[Nexus 4 Original Android Development] soumoks:
Can someone please clear the air here,from what I understand so far the official nigthlies are based on jls whereas the individual dev builds are hybrid,is this correct? I am on marclandis 26th build and no deadlocks at all,it does say jls in the about phone thing but when i check the build prop under ro. Build.description it says jwr.check the attached image.
[Nexus 4 Original Android Development] Mercado_Negro:
What does the kernel say in "About Phone"?
[Nexus 4 Original Android Development] Jubakuba:
If and of you get a minute to play around with this...I think my OCD is obvious.

The fact that I had to make my own images (blasphemy) bugs me enough as-is.

If I see downloads and no reports I'm pulling the download. Seriously, that isn't cool.

Should display itself OVER your lockscreen when you bypass an alarm (or just pop up if you're not on your lockscreen):

Your mission!? Try to break it. Try to make it so it doesn't dismiss your alarm sound (if the "loop" setting is checked)!

Fun game, eh? Do it locked. Do it from sleep. Do it with screen on. Other apps open. Press the last-app button...whatever you can think of to try and fool it.

If you do manage to fool it...start a phone call and the sound will stop (lol, it makes sense in the code for another use) so you don't have to reboot.

Move to /system/app/Settings.apk (replacing old one) and set permissions to match the rest of the apk's there.

Download

No, I'm not a team member. But this will (god willing) be in official AOKP none-the-less...so I'm posting it here.
[Nexus 4 Original Android Development] soumoks:
This is how it came..
[Nexus 4 Original Android Development] Mercado_Negro:
Ok, got the file. It's the in /system/app already. Changed permissions and even rebooted just in case........ How does this work? lol I mean, I've never used quiet hours, I've never felt the need but I'm willing to learn and help to debug in the process :D

---------- Post added at 12:54 AM ---------- Previous post was at 12:49 AM ----------

Argh, it doesn't say there. I read in AOKP's site that official nightlies are now using CyanogenMod's kernel which means it is JLS. I'm using franco.Kernel JSS right now with the latest official nightly and it works fine. The ROM itself is JLS, though.
[Nexus 4 Original Android Development] Jubakuba:
Thanks man =]

Well...

Settings>Sound>Quiet Hours

Quiethours are used when you're asleep generally.

I use them when I'm in class or busy at work as well.

If the times are equal...you can just use a Notification-shade-toggle to turn the WHOLE set of features on/off.

Or you can set it to turn itself on/off at specific times...

Or a combination of both.

The quiethours checkboxes to silence ringer/vibrate/led/notifications weren't by me...nor are they new.

The AutoSMS features just reply to anyone who texts you...or any missed call...with a text message of your choosing.

That's fine, and works %100. No need to test that.

The Bypass features start an alarm (or just act as a quick ring if you set loop to false) on your phone if they text you your "key" or if you miss [your set amount] of calls in 30 minutes.

I never used QuietHours before this...because it always made me nervous that I would miss the frantic calls from a family member or friend needing help or to tell me something important. Now I know they can always reach me if it's an emergency.

So...the alarm feature is what MIGHT be buggy. I'm testing the heck out of it and it seems fine though.

What would go wrong is basically...your phone wouldn't stop alarming even if you dismissed the alarm.

Again, I don't think it'll happen: but this is why I need testing.

The logic was changed fairly drastically between this and the old method...due to extended abilities of a full-screen view that are MORE beneficial and less-hackey...

But I actually found a bug in the old way as well...the "last-app" button dismissed the alarm message but did not silence it. I've fixed that and everything else as-far-as-I-know.
[Nexus 4 Original Android Development] Mercado_Negro:
Ok thx, that's a good start, I'll give it a go... Man, I just ran into your post in G+ and I laughed a lot with the comments, sooo clueless lol
[Nexus 4 Original Android Development] Jubakuba:
#naughtynames
[Nexus 4 Original Android Development] Mercado_Negro:
Ok man, I can see it now. That's a really cool feature you coded there, very handy indeed.

I texted myself a few times from my Nokia and even called. Tried it while playing Need For Speed, browsing XDA via Tapatalk, chatting with a friend in Whatsapp and of course leaving the phone alone. The ringing stops as soon as I touch the screen :thumbup: :thumbup:

As for the screen, well I think a simple "xxxxx wants to contact you" right in the middle would do the trick, no need for the beach ball lol
[Nexus 4 Original Android Development] Jubakuba:
Thank you thank you.

But IR Photoshop m4st3r
[Nexus 4 Original Android Development] Mercado_Negro:
Lolololol

If you get bored someday just let me know, I got a couple of handy features I've had my eye on for a while now that will please your coding hunger lol :p
[Nexus 4 Original Android Development] JG:
kecinzer says his build is built with linaro and uses JWR franco kernel with his and labodj patches...I cant speak for Marcs
[Nexus 4 Original Android Development] ben_pyett:
it's the modified bit that concerns me, as I run Franco, and sure I used JSS version with his last add I do now although can't recall if I had deadlocks , as at that stage I was switching builds on a daily basis, spoilt for choice, back then
[Nexus 4 Original Android Development] JG:
I edited my post above to use his exact words in regards to the kernel.
[Nexus 4 Original Android Development] Jubakuba:
Happy now, jerk? :o

Totally agreed, really...I'm terrible with images.

I'm not one to kang other ROM features, if that's what you mean...

Otherwise, I'm all ears.
[Nexus 4 Original Android Development] nikwen:
As I already said yesterday, Marc's builds are using a JWR kernel. The ROM is a JLS one.

I haven't had any deadlock issues with it.
[Nexus 4 Original Android Development] JG:
Yah I know ..The one I am running is very smooth and fast and I have noticed no deadlocks at all unlike the official release.So I am sticking with kecinzer for now..
[Nexus 4 Original Android Development] ben_pyett:
Unfortunately, Franco JWR and the Marc build from 27th which is the one that I've been running recently causes screen tearing, suggesting that his kernel isnt pure JWR (not in position to look at gerrit at the moment as traveling in a car with bad signal), which is why I run JSS and suffer the deadlocks... :thumbdown:
[Nexus 4 Original Android Development] santeana:
I'm confused now... Should I be running jwr Franco then? I currently use Franco 184 jss on my kecinzer 9/24 build and to my knowledge I've had no issues at all. Been running flawless all week! What am I missing here?
[Nexus 4 Original Android Development] ben_pyett:
cocky answer, if you have no issues then you're doing the right thing ;) so don't charge anything.
[Nexus 4 Original Android Development] Jagdish84:
Im running Marcs 27th, using BCM JSS\JLS kernel(Bytecodemes kernel) and did not encounter any screen tearing nor deadlocks during the past 24 hrs which is when i flashed the rom...
[Nexus 4 Original Android Development] JG:
I can only speak for his latest 9/26 build .The 9/24 I also ran a JSS kernel but with his latest I am running a JWR franco kernel (linaro built by labodj this one.. http://xdaforums.com/showthread.php?t=2307463 ).
[Nexus 4 Original Android Development] purpleman2k:
I'm not sure this is the right thread to post to, but here goes -

I just clean-installed (flash rom+gapps / factory wipe / erase cache+dalvik) latest nightly 4.3 aokp.

I've found what might be considered a serious bug. If you set the system language to Hebrew, after reboot SystemUI will force-close and you won't be able to get past the lockscreen.

This happens on my device even if all I did after installation was go through the next-->next-->next setup process (choosing Hebrew), then reboot once getting to homescreen.

Can anyone please verify this?
[Nexus 4 Original Android Development] vampire36:
Nice to see old mate from desire s thread :P

Neways try hellscore...am with it for last 2 days no deadlocks...using whatsapp with lots of mess...which generally is the best combo to reproduce deadlocks...but with this combo no deadlocks...:)
[Nexus 4 Original Android Development] Romanbb:
alright. recents behavior looks to be fixed! http://gerrit.sudoservers.com/#/c/4687/
[Nexus 4 Original Android Development] ichbinich:
Nice! Do you have planed to compile a new build today?
[Nexus 4 Original Android Development] Romanbb:
I think so
[Nexus 4 Original Android Development] yyz71:
AVRCP really missing it..:D
[Nexus 4 Original Android Development] Romanbb:
That's nice ;)
[Nexus 4 Original Android Development] yyz71:
lol :silly:
[Nexus 4 Original Android Development] jasonwc:
Awesome. I knew you would fix it. Cant wait for the new build.
[Nexus 4 Original Android Development] FSRBIKER:
Has anyone used voice search with Google Now? Once I press the mic it just closes Google Now. I'm on the 12/17 build, 12/12 gapps and clean install.
[Nexus 4 Original Android Development] DutchDogg54:
Working fine for me on 12/17 build, 12/12 gapps & dirty install
[Nexus 4 Original Android Development] Romanbb:
Log cat?
[Nexus 4 Original Android Development] JmPTaz09:
Working fine here; just tested... Did full wipe clean install of 12/17 build and 12/12 gapps last night...
[Nexus 4 Original Android Development] jasonwc:
Working fine here as well.
[Nexus 4 Original Android Development] FSRBIKER:
--------- beginning of /dev/log/main

I/dalvikvm( 4209): Turning on JNI app bug workarounds for target SDK version 11...

D/dalvikvm( 4209): GC_CONCURRENT freed 86K, 10% free 2660K/2952K, paused 2ms+2ms, total 17ms

D/dalvikvm( 4209): GC_FOR_ALLOC freed 10K, 8% free 2761K/2984K, paused 14ms, total 15ms

I/dalvikvm-heap( 4209): Grow heap (frag case) to 4.355MB for 1536016-byte allocation

D/dalvikvm( 4209): GC_FOR_ALLOC freed <1K, 6% free 4261K/4488K, paused 11ms, total 11ms

D/dalvikvm( 4209): GC_CONCURRENT freed 1K, 6% free 4260K/4488K, paused 1ms+1ms, total 10ms

D/dalvikvm( 4209): GC_FOR_ALLOC freed <1K, 5% free 4318K/4544K, paused 9ms, total 10ms

D/dalvikvm( 4209): GC_CONCURRENT freed 8K, 5% free 4960K/5172K, paused 3ms+2ms, total 17ms

W/asset ( 4209): deep redirect failure from 0x01030046 => 0x0208000c, defStyleAttr=0x01010084, defStyleRes=0x0103008f, style=0x00000000

W/asset ( 4209): deep redirect failure from 0x01030046 => 0x0208000c, defStyleAttr=0x01010084, defStyleRes=0x0103008f, style=0x00000000

W/asset ( 4209): deep redirect failure from 0x01030046 => 0x0208000c, defStyleAttr=0x01010084, defStyleRes=0x0103008f, style=0x00000000

W/asset ( 4209): deep redirect failure from 0x01030046 => 0x0208000c, defStyleAttr=0x01010084, defStyleRes=0x0103008f, style=0x00000000

This was just after I flashed rom/gapps again over the top of the build.
[Nexus 4 Original Android Development] Mnemoch:
Bump...and new question: my dialpad rotates even though I have it de-selected in the dialer menu options...had the same behaviour actually on my Galaxy Nexus with Milestone 1 (or 2 can't remember, last Milestone anyways). Seems like a bug to me but maybe I am missing a different menu option that overrides it?

Thanks Roman!
[Nexus 4 Original Android Development] dimsler:
everytime I encrypt my phone my wifi stops working with this rom, any ideas?
[Nexus 4 Original Android Development] DJMartini:
msm_hsic_host wakelock

I know there's a completely other thread regarding this issue [Q] msm_hsic_host wakelock but I'm wondering if the ROM has anything to do with it or the DEV's might have ideas on how to fix?
[Nexus 4 Original Android Development] S7evinK:
At least i stayed on "stock" for 3 weeks.

Flashing now =)