yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] pkelly517:
Damn! I get home from work and it's already solved.

Building now. If it doesn't work, I'll take a day to see if I can fix it first this time :)

Oh, thanks.
[Nexus 4 Original Android Development] Jubakuba:
They'd probably hate an extra option for duration.

But I can increase it to a more standard value of 25.

Petr actually authored that. I just uploaded part of it since he didn't upload the second half.

Edit:

It works =]

Now we just need to convince our lovely themers to update their images, however.
[Nexus 4 Original Android Development] dankoman:
that would be lovely :good:
[Nexus 4 Original Android Development] abjexstallion:
On the latest Whitehawkx, i've tried to use the active display, but i'm not sure if it's working or not... Is it supposed to be like a Moto X notfication type?

After all... It's a NEXUS!!!
[Nexus 4 Original Android Development] Jubakuba:
For now, toggles increased;

http://gerrit.aokp.co/#/c/12817/
[Nexus 4 Original Android Development] pkelly517:
Beats me. I tried the build, and ended up with more FCs in an hour than I had in the last few months.

I went back to the self-rolled Merged build (and added Juba's LTE fix (still booting)) and life is back to rock solid.
[Nexus 4 Original Android Development] abjexstallion:
Which build are you referring to? Links? Thanks in advance. I'm in the hospital and she's asleep, some flashing might ease the boredome.

After all... It's a NEXUS!!!
[Nexus 4 Original Android Development] pkelly517:
Well, the build that you referred to. The latest Whitehawkx. 9-30.

So I went back to the just merged tree, and cherry picked Juba's LTE blue thing fix.

I roll my own.

Juba, The fix did work (grumble, no code to look at.) Thanks! :)

If you want something to flash, here's today's build witha repo sync done ~4am CDT. Juba's LTE fix picked. Nothing else. Only merged tree.

You'l have to live with the AOKP version being 'KellyBean'. I'll share, but I want credit :)

https://www.dropbox.com/s/40szktzu6jg720q/aokp_mako_KellyBean_2013-10-01.zip
[Nexus 4 Original Android Development] JG:
I have tha same setup i will test and get back to you!!!

---------- Post added at 04:52 PM ---------- Previous post was at 04:44 PM ----------

`I am not to familiar with the Active Display ,but when I activated it in kecinzers last build ,everytime my phone display times-out it pops up Active display screen and I dont seem to understand the advantage of it and what it does other than help drain the battery IMO..

---------- Post added at 05:06 PM ---------- Previous post was at 04:52 PM ----------

I have same setup as you and mine is working fine no-issues.FYI - Heres what I am using slim-gapps, photosphere,kecinzers last 9/26 and LaboDJ`s latest JWR linaro franco kernel r186 and like I said

NO - deadlocks,FC`s etc...

,
[Nexus 4 Original Android Development] encho:
It can give you updates on various things, like missed calls or messages afaik. It makes sense on amoled screens like moto's but not on ours. On amoled screens only the lit pixels drain the battery, which is not much, but on LCD screens whole screen needs to be on (as that is the only way for it to operate - not being led based but rather having a backlight). So yes, it will drain the battery like crazy.
[Nexus 4 Original Android Development] santeana:
Exact same as me except I'm using normal gapps. My gf has a TMO gs2.apparently they are having issues with the camera/gallery on 4.3. wonder if a pic from her phone is causing it....
[Nexus 4 Original Android Development] JG:
What if you send an MMS to yourself?
[Nexus 4 Original Android Development] santeana:
Good call.... Worked fine. So weird. The picture I received from her works fine. I can download it using handcent and I can open it and look at it. Yet try to view that mms and it closes before I can even see a word.
[Nexus 4 Original Android Development] dankoman:
Since when has mgerrit been included as system app?
[Nexus 4 Original Android Development] dankoman:
new whitehawkx build has been up on goo for a couple hours, in case anyone didn't see it... http://goo.im/devs/Whitehawkx/mako/aokp_mako_jb-mr2_unofficial_2013-10-01.zip

don't know if it has juba's LTE fully-connected fix cherrypicked or not because i don't use LTE, but the build is up if someone else wants to try...
[Nexus 4 Original Android Development] Jeeeenx:
That LTE fix was pretty much all that was merged for our device...
[Nexus 4 Original Android Development] dankoman:
yes, but merge didn't take place until 4:56pm PDT, whereas build was uploaded early this afternoon (2:28pm PDT), i think its safe to say that, unless the commit was cherrypicked, it didn't make the build.

[MENTION=4406848]pkelly517[/MENTION], on the other hand, specifically said he picked it.
[Nexus 4 Original Android Development] Jubakuba:
How about ALL light vibrations (clicks, etc)?

Ta-da.
[Nexus 4 Original Android Development] fabian.m:
You, Sir, are awesome

Sent from my mako
[Nexus 4 Original Android Development] Mercado_Negro:
Hey Juba, how are you mate? I've seen you've been busy fixing and polishing stuff all over the place and I wonder if you received my PM. Maybe you just missed it :)
[Nexus 4 Original Android Development] Jubakuba:
I can probably write my own version of both of those. I refuse to look at how anyone else did it lol.
[Nexus 4 Original Android Development] Mercado_Negro:
Heh I thought you missed it... And yes, that's what I thought, "Juba will just probably make their own" :) Thanks for replying mate.
[Nexus 4 Original Android Development] jastonas:
How come AOKP doesn't have a T9 dialer?? Can I pull phone.apk from CM and replace it?
[Nexus 4 Original Android Development] zelendel:
Might want to check the settings in the phone app and you will find it there.
[Nexus 4 Original Android Development] jastonas:
oh! I never thought this would be disabled so I came to the (wrong) conclusion that it doesn't exist! Thanx.
[Nexus 4 Original Android Development] ben_pyett:
phone....settings.....dial pad auto complete
[Nexus 4 Original Android Development] dankoman:
You are the one true man. Thanks for listening :D
[Nexus 4 Original Android Development] ben_pyett:
Goodies...

All sorts of new builds in the last couple of days.....

goo.im/devs/kecinzer/aokpk/mako/aokpk_mako_jb-mr2_daily_1310021156.zip

goo.im/devs/Whitehawkx/mako/aokp_mako_jb-mr2_unofficial_2013-10-01.zip

Personally running whitehawkx 10-01 at the moment with Franco JSS (with dealocks) although will try hopefully try kecinzer later once I'm finished work.

EDIT: kecinzer should be run with its own kernel
[Nexus 4 Original Android Development] pkelly517:
What a tease.

Hey everyone! Look at this cool feature! Getcherownlink!

:)
[Nexus 4 Original Android Development] santeana:
Sweet! New kecinzer build is up on goo! :D

---------- Post added at 01:25 PM ---------- Previous post was at 01:21 PM ----------

If running kecinzer remember to use jwr kernel.

[MENTION=4686563]K-JACKS[/MENTION] hey I didn't even think about it... I was using cm's mms app. I prefer theirs because you can customise the vibrate pattern and with aokp you can't. I've always used cm's mms app with all my roms. It's the first thing I replace lol. Well apparently it doesn't agree with this rom because I flashed the new release this morning and left the stock mms this time and received pics just fine. Too bad. I like that app.

New question though... When I do get a pic with this one, it's just a blank white square until I long press and save attachment. Is there a way around that that you know of?
[Nexus 4 Original Android Development] ben_pyett:
WARNING

I Had issues when I flashed the kecinzer build in conjunction with Franco kernel, I even re-downloaded both to rule out a bad zip file.

Franco 188 JWR = black screen - no response - needed power reset and reflash as couldn't see anything.

Franco 188 JSS = colour pallete all screwed and graphic screen issues, not the tearing problem.

It flashed fine and ran without issue with the its own kernel that comes with the ROM though, so a Franco Kernel/ROM incompatibility problem.
[Nexus 4 Original Android Development] DJMartini:
Yea, I had problems with Faux's kernels too!

JSS - Blue screened - no response had to reboot

JWR - Black screen and froze had to reboot

Neither worked for me. I was able to flash just the ROM without kernel and noticed that the version was JLS?
[Nexus 4 Original Android Development] CamoGeko:
Someone else in the Franco thread is having similar issues:

http://xdaforums.com/showpost.php?p=46106639&postcount=48779
[Nexus 4 Original Android Development] evonc:
Haha I was just about to post. Compiled a build maybe half an hour ago with http://gerrit.aokp.co/#/c/12809/ and got the same results. Faux 026 JSS gave inverted/broken colours and 026 JWR gave a black screen.
[Nexus 4 Original Android Development] santeana:
Thanks for catching that so fast! I was gonna go nuts! Couldn't figure out wtf was going on! Lol now I see these problems are popping up in every thread lol
[Nexus 4 Original Android Development] vampire36:
Try neo kernel..test one v14...

https://drive.google.com/folderview...&usp=sharing&tid=0B0Hh7WuhEiuqZjB0ZTFxSGxtb28

One of them should boot...with JWR and JSS within AOKP...m not sure which 1 will boot :P
[Nexus 4 Original Android Development] ben_pyett:
Until it becomes clear what direction CM and AOKP are going in then I'm back on yesterdays whitehawkx build with Franco JSS (as per sig).

This has been a farce now for months, all of Google's own making, since JBQ's initial mistake and their subsequent refusal to release an updated stock image, we've suffered confusion and incompatibility.

Roll on the Nexus 5, along with Android 4.4 and hopefully we'll be finally rid of this confusion, assuming Google don't screw up the sale/distribution as they nearly did with the Nexus 4!
[Nexus 4 Original Android Development] evonc:
Just did another build with no cherry picks and it's giving the same issue with the inverted colours. Can someone else confirm?
[Nexus 4 Original Android Development] menkyy:
Btw, what's the diffrent between kecinzer, whitehawks n marclandis build??

Sent from my Nexus 4
[Nexus 4 Original Android Development] dankoman:
yeah definitely, especially since nexus 5 will have USB OTG support out of the box!

---------- Post added at 11:10 AM ---------- Previous post was at 11:09 AM ----------

+1
[Nexus 4 Original Android Development] CamoGeko:
Maybe I misunderstand something here... wouldn't it be just easier to use JWR builds?

Also, I fail to see how its Google's fault considering these are custom ROMs and not stock images.
[Nexus 4 Original Android Development] dankoman:
kecinzer comes with a modified franco kernel.

whitehawkx and marclandis are pretty much the same, but if you look at the open commits at gerrit.aokp.co, each devs' respective builds are more likely to have their own open commits cherrypicked. everything that merged should be the same.

all three devs are official aokp team members.
[Nexus 4 Original Android Development] DJMartini:
Might have to agree with you here. I use Faux kernel for the gamma, gpu etc. control and now that CM is going to CAF for their kernel's Faux isn't writing for it any longer. It's breaking all his code.
[Nexus 4 Original Android Development] TheDarkDefender:
Hi [MENTION=3087740]Jubakuba[/MENTION]

Could you please clarify why aokp has opted to use cms unified caf kernel ( which is causing all the confusion) ?

And also guide on what commit to revert in the device repo ( which corresponds with the caf changes) so i can build and use usual aosp kernels with the rom?

Thanks. :)

Sent from my Nexus 4
[Nexus 4 Original Android Development] ben_pyett:
1 day, just joking - in all honesty, I couldn't really tell you, although it looks like the kecinzer build which is 1 day later has merged changes which make it incompatible with the major custom kernels (faux and Franco).

The latest kecinzer build runs fine with its own kernel though.
[Nexus 4 Original Android Development] dankoman:
think juba's catching some Zzzs, think this is it though (or at least one of them) http://gerrit.aokp.co/#/c/12468/

there are a bunch of other merged commits that talk about CAF though
[Nexus 4 Original Android Development] ben_pyett:
It would be easier to use JWR builds which is why franco initially only built for that, but since customs like AOKP build from AOSP then they won't be fully compatible and would mean standing still - I choose to have the ability to be able to customize more than stock permits and so I want a custom ROM, my current preferred choice being AOKP.

I see it as Google 'making' as they created the confusion in the first place, by permitting differing builds to land for the N4 and new N7, rather than merge them, Google didn't assist by re-updating then N4, but then again why would they.

Note: I must add that you're probably more of an expert than myself so if I'm talking out of my backside - tell me nicely :)
[Nexus 4 Original Android Development] BLADESMAN1889:
Hey Guy's,

Have been unwell but tried to keep up with thread. I must have missed something though as I just flashed Reznicek build with Semaphore kernel & I have a whole new yellow theme going on :) everything on the status bar is a orangey yellow & green had turned to blue :)
[Nexus 4 Original Android Development] ben_pyett:
simply flash ROM again without custom kernel or flash whitehawkx last build and Semaphore kernel (read the last few pages).
[Nexus 4 Original Android Development] BLADESMAN1889:
Yeah - sorry wasn't asking for help (I'd already reflashed) was more of veiled warning to anyone else thinking of doing same.

But thanks for taking time out :good:
[Nexus 4 Original Android Development] nikwen:
Do I have to do a full wipe when installing Whitehawkx's version? I'm currently on Marc Landis' build.
[Nexus 4 Original Android Development] ben_pyett:
No I happily moved between the two 4.3 builds performing a dirty flash (cache and dalvik).
[Nexus 4 Original Android Development] nikwen:
Cool. Thank you very much. :)
[Nexus 4 Original Android Development] JG:
Kecinzer last builds today ,He has been doing some experimenting on his builds and trying a custom built kernel and modified his ROM for just that .Hence that is why it isnt compatible with franco at the moment but if you use the supplied kernel it should work fine .He will also be releasing a new build really soon that will again be compatible with Francos Kernels.

Hope this settle the confusion..
[Nexus 4 Original Android Development] k3mik4l:
Anybody else on Kecinzers latest build noticing that in the signal part of rom control its missing the use alt gingerbread signal that has always been there ? Now I have no signal showing on my status bar. This is from a dirty flash from his 26 build.
[Nexus 4 Original Android Development] DJMartini:
Faux's kernel's too?
[Nexus 4 Original Android Development] JG:
Not sure about Faux .He just mentioned that he will be going back to Francos kernel on next build so if it worked with it before it should again is my guess.He did say he will be releasing a new build soon.So all i can say is just sit back and wait and see...Whitehawkx I believe has a new build out today that is a pure build so you can try that one for now if you prefer.. I believe that is working on all the kernels.I haven't checked myself .I tend to stick with Linaro builds and Kernels.
[Nexus 4 Original Android Development] hacin:
Hi all, now I had "deadlock" on whitehawkx build 30.09.2013 with stock whitehawkx kernel. ROM is fantastic, but the "deadlock" is not acceptable for me. Is there anny combination of this ROM and Kernel without "deadlocks"? Thanks all
[Nexus 4 Original Android Development] JaylanPHNX:
I would like to add my voice to the chorus calling for reverting the CAF commits. I'm still on ML 9/26 with Faux Kernel, and if I can't use Faux123's stuff, I won't be updating. Fortunately, the build I'm on seems flawless.

Sent from an N4 blessed with AOKP and sanctified by Faux123!
[Nexus 4 Original Android Development] MontAlbert:
It seems carbon are removing all the cm caf crap... I can only hope aokp do the same....

http://xdaforums.com/showthread.php?p=46116475
[Nexus 4 Original Android Development] klasszsrac:
I use Semaphore kernel a self-built my rom. Work perfect.

Nexus4 custom Aokp 4.3
[Nexus 4 Original Android Development] nadiros:
Ok guys I've been following this thread for a long time...where does it say that AOKP are officially going the way of CM? Is AOKP adding all the CAF commits?

I realize the nightlies from single members are experimenting but still....
[Nexus 4 Original Android Development] JaylanPHNX:
A few pages back, you'll see some people building from latest source are experiencing the same issues with custom kernels as CM.

Sent from an N4 blessed with AOKP and sanctified by Faux123!
[Nexus 4 Original Android Development] nadiros:
Thanks, however as I said, I have been reading along. Perhaps I'm missing tweets or g+ stuff that I don't follow.
[Nexus 4 Original Android Development] j0hnh0lmes:
Check the merges. They have a few caf merges recently. :rolleyes:
[Nexus 4 Original Android Development] dankoman:
Go here:

http://gerrit.aokp.co/#/q/status:merged+message:caf,n,z

It links to a gerrit query returning all merged commits containing the word "caf" in the commit message or title, sorted in descending chronological order (most recent first).
[Nexus 4 Original Android Development] nadiros:
Deleted. Not dev related, and nothing nice to say

:(
[Nexus 4 Original Android Development] MontAlbert:
Is there any way to find out if the aokp guys plan to continue with caf? Jako not official member any more but maybe he could find out? Who is the official aokp maintainer for mako?
[Nexus 4 Original Android Development] JG:
kecinzer build.....

as far as kernel I beleive this build is using JSS unlike his 9/26 build let me know! FYI it has a linaro built custom Modified Franco Kernel 3.4.63+ already in ROM..

http://goo.im/devs/kecinzer/aokpk/mako/aokpk_mako_jb-mr2_daily_1310030758.zip
[Nexus 4 Original Android Development] ben_pyett:
If anyone can confirm back in this thread, that this works with Franco and which build ie JSS/JWR I'd be immensely grateful as missing my daily flash fix.

I'm in the process of downloading it now myself, but probably won't get an opportunity until later...
[Nexus 4 Original Android Development] JG:
Kecinzer did say it should work now with francos or similiar ,however he mentioned that it is now JSS but that confuses me a bit since he has been using JWR on his builds not sure why he changed it so therefore I cant confirm until I get it setup myself .which will be not for a few more hours..
[Nexus 4 Original Android Development] ben_pyett:
All good news.....Franco JSS

Found a few minutes, so can confirm Kecinzer latest 1003 build and Franco JSS - run great together. :D

EDIT: after about an hour....got continual Phone FC's, although did dirty flash, reboot resolved the issue.
[Nexus 4 Original Android Development] dankoman:
Aside from asking them yourself or waiting for an announcement, not really. You could always tune into their IRC channel and see if you 'hear' anything...

---------- Post added at 07:47 AM ---------- Previous post was at 07:45 AM ----------

Anybody else getting FCs when trying to view a commit using aokp's native mgerrit app?
[Nexus 4 Original Android Development] ben_pyett:
Yep, getting the same FC here, that wasn't happening last week, but that was several builds ago.
[Nexus 4 Original Android Development] pkelly517:
Funny thing about that link, is that all of the commits are at least a week old.

I built Monday, and it had no issues. A Tuesday build didn't work.
[Nexus 4 Original Android Development] JG:
I believe that app is nolonger in the builds at least not in kecinzer`s if you open it up and look it isn't in there .you can always put it back in the ROM and see if it works that way .I hope I am understanding you correctly!!
[Nexus 4 Original Android Development] nikwen:
Well, there've been other commits: http://gerrit.aokp.co/#/q/status:merged,n,z
[Nexus 4 Original Android Development] JG:
No FC`s for me
[Nexus 4 Original Android Development] dankoman:
all i was doing was answering the original question of where it said there were CAF commits. as it happened, the latest merged commits were a week old. that doesn't mean more recent commits relating to CAF weren't cherrypicked in any given build.
[Nexus 4 Original Android Development] Jeeeenx:
I ****ing love how stable my phone runs. You guys are freaking awesome. Been running your stuff for 2 years and no ROM has even come close to yours. My N4 runs flawless and my gf's d2tmo is 3x smoother since I flashed this bish.

Just wanted to say thanks for all your hard work and effort!
[Nexus 4 Original Android Development] santeana:
Running it right now with jwr. So far so good. Will let you know how it goes.
[Nexus 4 Original Android Development] ben_pyett:
Really :confused: as I tried running the latest 1003 it with Franco 188 JWR and ended up with a blank screen - fine with JSS as we've already said above.
[Nexus 4 Original Android Development] santeana:
Yeah I don't know. Working great for me! And kecinzer just told me he is switching to franco jwr for good now.
[Nexus 4 Original Android Development] ben_pyett:
Confused? I also experienced issues with TiBu constantly failing with ‘insufficient storage space’ errors when attempting a backup on the build from 1003 , the backup directory showed the correct valid location and TiBu showed loads of avialbale space.

Flashed back to previous whitehawkx build (10-01) – TiBu backed up with no issues.
[Nexus 4 Original Android Development] Rod3:
Ben, I am having the same issue. Flashed JSS version and all is well.

Santeana, are you sure you flashed Franco's JWR kernel? If you used his FKU app to download the kernel, it will automatically download the JSS version.
[Nexus 4 Original Android Development] pkelly517:
True, but I didn't see anything that might be the problem.

Some Sony, a few Samsung specific merges, along with a whole lot of mgerrit stuff.

I suppose my repo sync could have failed, and I didn't have the mako blobs merge...

:what:
[Nexus 4 Original Android Development] santeana:
Running linaro JWR from LaboDJ.
[Nexus 4 Original Android Development] dankoman:
this post is intended for informational purposes only.

some people may not be as familiar with gerrit code review as others, specifically with searching for specific commits. fortunately, aokp's gerrit provides detailed documentation of all the search operators you can use to search through commits. i believe that if more people learn how to search through gerrit (which might seem a little scary at first), it will cut down on the amount of unnecessary questions in this thread, and in other threads.

http://gerrit.aokp.co/Documentation/user-search.html
[Nexus 4 Original Android Development] santeana:
What are you trying to back up? I just tried one app and it worked fine. We're you doing a full back up? If so I'll try that....
[Nexus 4 Original Android Development] JG:
Yes he is. However this particular build he planned on using JWR but he ran into issues ..Probably because of the Blobs .So he released it with JSS and once he works it out he will release all future build with JWR Kernels .But we all know that can change.So sit back and see.I myself had one deadlock typing a SMS and again Moving files. [MENTION=3953735]santeana[/MENTION] are you using that JWR with the Prima drivers or without???
[Nexus 4 Original Android Development] santeana:
[MENTION=4686563]K-JACKS[/MENTION] using without prima drivers. Which one are you using?

Double checked. I only have 2 kernels on my phone. 184jwr linaro and 188jwr linaro.

So am positive I'm running jwr. Try it, see how you make out!
[Nexus 4 Original Android Development] ben_pyett:
was doing a full backup, redo of all existing, might have been an app issue, but doubt it, I'll attempt to give it another go once a new build is out. Possibly time for new to do a full wipe again, now we're getting close to a complete 4.3
[Nexus 4 Original Android Development] zelendel:
Anyone ever seen this. I get this on every AOKP build.

Wayne Tech Nexus