yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] grgana:
Flashed, so far good! Few reboots no yellow demi good screen,

i only missing auto rotate option in launcher (at least cant figure it out) and appdrawer, could i install trebuchet from CM 10.1 via TB? Or use Nova? And is there possible to put toggles in notification bar?

Cheers
[Nexus 4 Original Android Development] nikwen:
For the launcher: I'm not sure about Trebuchet but I guess that it won't work (aren't all settings in the system settings). Nova should work fine.

You can change the Toggle style in the toggle submenu of ROM Control.
[Nexus 4 Original Android Development] kecinzer:
[MENTION=4377503]evonc[/MENTION]

You can find it on gerrit on my github.com/aokpk and on aokp gerrit.

So today build work for everyone, great :).
[Nexus 4 Original Android Development] jimbohurt:
Hey bro, is your Franco kernel included a prima one? Will I still need to flash dePrimator in order to use the original Franco?
[Nexus 4 Original Android Development] j0hnh0lmes:
Can you make the APN editable please?
[Nexus 4 Original Android Development] yoyoz808:
Nope. My process android.media FC everytime. I even did a full wipe and still happens.
[Nexus 4 Original Android Development] mixtapes08:
Yes please compile a faux kernel i need his sound enhancements mod.. Thanks :)

Sent from my Nexus⁴
[Nexus 4 Original Android Development] kecinzer:
My franco kernel included contains faux sound control mod ;)
[Nexus 4 Original Android Development] Sick1:
As Usb-Otg working perfectly on your builds with faux kernel, would it be possible to make it work with your new builds with franco on default? As franco it always needs ziddeys tweaked version.
[Nexus 4 Original Android Development] JG:
if you really wanted to you can take the boot.img the WCNSS_qcom_cfg.ini and the WCNSS_cfg.dat from the previous build and put it in the new build and you will have his faux version already to go.Of course if you know what your doing - otherwise dont try it! of course you can make it into a flasshable zip form like I did just to have just in case.
[Nexus 4 Original Android Development] yethz:
Perfect update [MENTION=525305]kecinzer[/MENTION] on build 10/19/13..

Thanks a lot and I have a feature request too but its on the tip of my tonque ;) forget what was it but Its definitely useful one like font size on mms.

Anyways, theres an update from LaboDJ;

http://xdaforums.com/showthread.php?p=46617674

_____________________________

Device: Google Nexus 4 (LG-E960)

ROM: AOKP JB-4.3.1-MR2-(JLS36I) Kecinzer (Oct-18-13)

Kernel: Franco Kernel #190v2-JWR-Prima (Linaro@LaboDJ)

Recovery: PhilZ Touch (CWM) Recovery v5.15.0
[Nexus 4 Original Android Development] evonc:
Sounds lovely! I'll give it a whirl this weekend. Thanks!

Sent from my Nexus 4
[Nexus 4 Original Android Development] imeem:
any1 try the oct. 18 version? The links doesn't work for me. Also, does this mean the 4.3.1 is offical now since the title has changed?
[Nexus 4 Original Android Development] mixtapes08:
Yeah i know how to do that.. Thanks for the tip bro.. :)

Sent from my Nexus⁴
[Nexus 4 Original Android Development] defffizz:
I'm amazed at how smooth and fluid last kecinzer build is... Fantastic rom

Sexy Nexy, Kecinzer AOKP+franco
[Nexus 4 Original Android Development] shr33kant:
I found a little bug: if you flash the deprima file then the latest official Franco 191 jwr, go to settings -> storage, you get an fc every time.

Can't post a log at the minute because not at home but I'll be able to later today.
[Nexus 4 Original Android Development] churchmice:
Same here i think this is also the cause for com.android.media process to FC when connecting the PC with mtp enabled. From the logcat I see it complains about /storage/usbdisk0 .

But i don't think the deprim zip will cause this, which affects the wifi driver.
[Nexus 4 Original Android Development] kurniawan77:
Share the zip bro... We all so lazy;)
[Nexus 4 Original Android Development] shr33kant:
I thought so too but I re-flashed the rom and everything works fine now. :confused: I'm getting the com.android.media process FC too if I stay on Franco's Official 191 as well. I'm not sure whats going wrong here :(. I'm using SuperSU with both configurations but I doubt that's the problem either because it works fine on other roms...
[Nexus 4 Original Android Development] xanthrax:
Try hellscore b40 t9 or t11 , is all good here , I'm using t11 atm

sent from my Darkside of Nexus 4
[Nexus 4 Original Android Development] churchmice:
The root cause is franco 191 jwr, i flashed 1019 build, no FC, I then applied the deprime zip, still no FC.
[Nexus 4 Original Android Development] JG:
Moved to different thread
[Nexus 4 Original Android Development] 1ceb0x:
Had the FC from media.acore service but I resolve it by doing this:

flash latest kecinzer build.

flash dePRIMAtor.zip

flash franco jwr r191 prima by LaboDJ.

Now the only FC that I have is the one from Storage. Maybe something borked in ramdisk?:)

Glad to see i'm not the only one though.

Ohh... didn't knew that kecinzer moved again on franco.

[MENTION=525305]kecinzer[/MENTION] can you please tell me if your built in franco kernel is the same as the one made by LaboDJ? It has prima drivers?

I want to know so that I'm going to install the new version without flashing franco by Labo again :).

TIA
[Nexus 4 Original Android Development] TeddyBeers:
Dirty flash build 18/10 on 17/10 - wifi broken.

Clean flash 18/10 - wifi ok

Dirty flash 19/10 on 18/10 everything works fine.

Wifi, BT etc. No single FC.

Thanks for great builds Kecinzer.

One quick question.

It's possible to hardcode Franco recommended gamma settings to kernel?
[Nexus 4 Original Android Development] kecinzer:
I think thats caused because one derp in RAMdisk. Just looking at it ;).
[Nexus 4 Original Android Development] ben_pyett:
Excellent news, as to experience this type of error in your recent builds was quite unexpected. ;) will eagerly await next build. :D
[Nexus 4 Original Android Development] 1ceb0x:
goo.im is offline. is there any way we could download kecinzer's build?
[Nexus 4 Original Android Development] yethz:
If u can wait for kecinzer's next build i think goo also would be back online again at that time (maybe a day or two coz kecinzer is working hard to give us a true rom for daily use)..

_____________________________

Device: Google Nexus 4 (LG-E960)

ROM: AOKP JB-4.3.1-MR2-(JLS36I) Kecinzer (Oct-18-13)

Kernel: Franco Kernel #190v2-JWR-Prima (Linaro@LaboDJ)

Recovery: PhilZ Touch (CWM) Recovery v5.15.0
[Nexus 4 Original Android Development] 1ceb0x:
I can wait, but I'm on 18th build and I cannot access mtp :)
[Nexus 4 Original Android Development] churchmice:
[MENTION=3137706]shr33kant[/MENTION]

The FC issue is caused by the missing line in the /fstab.mako

/devices/platform/msm_hsusb_host/usb2	/storage/usbdisk0 auto defaults	voldmanaged=usbdisk:auto

I unpack and repack the official franco r191 jwr kernel with this fix, and the FC in Setting->Storage and when connected to PC using MTP are gone.

I also attached the modified zip, hope this could be of any help.
[Nexus 4 Original Android Development] churchmice:
Forget to mention I also changed ro.secure from 1 to 0 in default.prop so when adb will default to root, which is much more convenient for me.
[Nexus 4 Original Android Development] BLADESMAN1889:
Hey Church,

I also have the missing nexus from pc.

Thanks for the fix I shall try it now, will it be ok to just boot in recovery and flash [I'm using Kecinzer 19/10] or re-install zip, gapps and dePRIMAtor ?
[Nexus 4 Original Android Development] churchmice:
Just flash this zip in recovery mode and everything should be fine.
[Nexus 4 Original Android Development] BLADESMAN1889:
Yep, that fixed it - nexus is now visable :D

Many Thanks
[Nexus 4 Original Android Development] PJcastaldo:
Are the official nightlies still CAF? I know I can use kecinzer builds but he uses some different drivers so I can't use what ever kernel I want May as well be CAf. Not that I font appreciate it, because I do.

I'm just using the build with faux baked in cause I prefer faux.. he has the voltage turned down a bit which is why some of you guys get radio failure (yellow bark screen).

Faux is just better than Franco.. but that my opinion.
[Nexus 4 Original Android Development] BLADESMAN1889:
Thats what the dePRIMAtor.zip is for - just flash it before the kernel you want to install. The info is on the last couple of pages direct from the dev himself.
[Nexus 4 Original Android Development] PJcastaldo:
I seen that and I attempted tlto use it and I ended up with no wifi connection. Do I need to flash it in steps? After the rom and before the kernel no reboot necessary between files?
[Nexus 4 Original Android Development] JG:
Hey is this an issue with Francos 191 build itself or only apply to this configuration.Reason being if it is a problem across the platform maybe you should inform franco of this and your fix..So it can be revised by him.:D
[Nexus 4 Original Android Development] churchmice:
You need to flash the deprim zip first.
[Nexus 4 Original Android Development] 1ceb0x:
Agreed to this statement! If kecinzer forked LaboDJ's work (which is based on Franco), the two of them need to know about it.

+ [MENTION=3292224]franciscofranco[/MENTION] and [MENTION=702102]LaboDJ[/MENTION]
[Nexus 4 Original Android Development] bruce7373:
Is the fix for this ROM only? I'm running Cataclysm 4.3 (JWR) with r191. I don't have that missing line either in fstab.mako. I don't have FC issues, but I can only get Windows to see the N4 if I have it set to PTP (and then only the camera folder).

Sent from my Nexus 4
[Nexus 4 Original Android Development] churchmice:
I really don't investigate that much.

Previously I mainly used ML's build with franco r191 jss build, no problem.

This is the first time I am using franco's official jwr kernel since I want the touch control feature with kecinzer build. The builtin doubletap2wake is too much sensitive, and it is designed such that a long touch will also wake up the screen. I don't like that so I tried the official franco jwr kernel.

When the FC happens, I just took a look at the logcat ( thanks for the CatLog app) , and found the first error is related to the /storage/usbdisk0 so I suspect the reason lies in the fstab. I extracted both boot.img ( one from the kecinzer zip and the other from franco 191 jwr official ) and did a compare. This is how I find the missing line in the official franco 191 jwr official kernel in fstab.mako.

In my point of view, I think this is more likely a problem of the kecinzer build ( I mean no offense, I think the ROM by far is the most featured one ), else there would be flood of complains in the franco's kernel thread. I think it may be related to the OTG support ( /storage/usbdisk0 seems like the mount point for external usb disk ).

---------- Post added at 03:31 PM ---------- Previous post was at 03:27 PM ----------

If you don't encounter FC, I don't think you need to flash this zip.

As explained in my previous post, think it is more like a ROM issue.

You mean you could not get MTP working ? Have you installed the required MTP driver ? I use win7 and it will install the driver automatically the first time my nexus 4 is connected to PC.

If you are using xp, you may need to install it manually.
[Nexus 4 Original Android Development] JG:
That makes sense .since it doesnt seem to be a topic on his thread...BTW as far as TouchControl .we are waiting on response from bponury in relation to TouchControl support for the Labodj Linaro version of franco that kecinzer`s kernel is based off of.Still have not got any answer yet .just thought you might want to know that there is others wishing to have that support as well.:D
[Nexus 4 Original Android Development] churchmice:
Yes, thanks, keep me informed on that :D
[Nexus 4 Original Android Development] JaylanPHNX:
I'm beginning to agree with [MENTION=3087740]Jubakuba[/MENTION] that the kecinzer builds should have their own thread. This one is becoming filled with talk of various built in kernels, dePRIMAtors, and various builds that are somewhat tangential to official AOKP.

I'm not saying anything bad about kecinzer or his builds, and I appreciate all the work he's putting into deCAFinating official AOKP. I'm just seeing the potential for confusion in this thread as well as really a benefit for users of the kecinzer builds having their own thread for discussion.

Sent from an N4 blessed with AOKP and sanctified by Faux123!
[Nexus 4 Original Android Development] JG:
I agree fully! lets ask him.

Edit ..I asked him via PM to please add a new thread in development ,So lets see if he decides to.-if it is something that he doesn't want to do for whatever reason,maybe will ask if okay for one of us to add a thread if it is something that is agreeable to others .You are so right it adds so much confusion with newcomers following info for one ROM that is meant for another .I have been following this thread for a long long time and I still find myself confused from day to day.

BTW goo.im is replacing servers and they have no estimate of downtime .at least that is what I deciphered from twitter..
[Nexus 4 Original Android Development] bruce7373:
It used to work with MTP (I think I had to disable USB debugging). I have the Universal USB driver installed. When I plug the N4 in, Windows says device is ready. It shows up in Safely Remove Hardware, but nothing in Explorer, unless I connect with PTP, and then I cannot navigate out of the Camera folder.

Sent from my Nexus 4
[Nexus 4 Original Android Development] grgana:
Hy does any one knows what should i do... im running 10.19 kecinzer with his in built franco, but i didnt flash deprimator at all,so in order to use provided fix, do i need to flash deprimator or not? Thanx

Greets!
[Nexus 4 Original Android Development] churchmice:
Deprim first, or your wifi won't work with my modified zip.
[Nexus 4 Original Android Development] JG:
Yes.Flash first then the kernel with fix
[Nexus 4 Original Android Development] churchmice:
Mtp and usb debugging can be enabled at both time. Did you see on your mobile that "connected as a media device" in the notification bar ? I would like to suggest you to find a working computer ( eg. A friend's whose phone could be recognized ) to further distinguish this problem into ROM issue or PC setup issue.
[Nexus 4 Original Android Development] JG:
So yah when his thread is up all of us that use kecinzer not sure about the other unofficials can move over to the new thread and free this one up for the official Aokp and that should clear up any confusion as far as things like caffeinated and de- CAF-feinated and other such confusing issues ie.Which kernel etc..etc..and maybe move any related mods such as the one churchmice posted etc..over to new site .IMO.I believe he is making new thread now if I understood his message correctly...

okay see you there! http://xdaforums.com/showthread.php?t=2491689
[Nexus 4 Original Android Development] kecinzer:
Ok guys, I start my own thread here - http://xdaforums.com/showthread.php?t=2491689

You can continue with discuss of my builds there.
[Nexus 4 Original Android Development] JG:
You heard it ! aokpk (kecinzer) users please use new thread only. As this thread is back to its intended audience. Official aokp or other - based on OP discretion of course.
[Nexus 4 Original Android Development] BLADESMAN1889:
It wasn't PC setup with mine. Once plugged into PC the sound played to confirm the connection & the icon showing connected device popped up - if I hovered over icon it displayed "mtp device"

Despite this Win Expl didn't show nexus⁴. Switching into camera didn't make any difference either.

Whatever cause was - your zip fixed it so all is well.

Sent from NEXUS⁴ via XDA Prem [AOKP 4:3:1]​
[Nexus 4 Original Android Development] cantevencode:
New whitehawkx build on goo

http://goo.im/devs/Whitehawkx/mako/aokp_mako_jb-mr2_unofficial_2013-10-19.zip

I'll update with kernel type and caf status etc when it's downloaded and flashed

EDIT: Can't get it to boot so can't update with more details
[Nexus 4 Original Android Development] bruce7373:
Got it sorted. It was a PC driver issue. I uninstalled the ADB driver the N4 toolkit put in, and replaced it with the universal ADB driver. Now the PC sees my N4 as an MTP device. :thumbup:
[Nexus 4 Original Android Development] davey11:
I did both dirty and clean flash on this build and black screen both times. Did a deprimator flash as I was coming from kecinzer. No third party kernel flash. YMMV

Sent from my Nexus⁴ (:p)
[Nexus 4 Original Android Development] nexicon:
Same black screen. How do i get it fixed??

Sorry I'm coming from the milestone build 4.3 and flashed the latest whitehawkx build. Something I'm missing?
[Nexus 4 Original Android Development] cantevencode:
Booted to black screen for me too. Just flashed a custom jss kernel and the colourfix zip and now it's working fine. Also, it's based on JLS36I
[Nexus 4 Original Android Development] Jubakuba:
Question...which I may or may not ignore the answer to dependant on how one-sided the answer is...

Lockhandle image changer...

Or simple colorizer?
[Nexus 4 Original Android Development] JaylanPHNX:
I think I like the idea of an image changer. Some of the best WidgetLocker themes are when the unlock handle is an image that matches the wallpaper. Some clever things can be done with just an image change.

Sent from my Nexus 4 blessed by AOKP and sanctified by Faux123.
[Nexus 4 Original Android Development] davey11:
So now we have to jump through hoops when trying to install the last few nightlies. Whitehawkx's builds have always been so solid, this one shocked me.

This caf chit is no good.

All the above no apply to kecinzer, his rom is guud. :eek:

Sent from my Nexus⁴ (:p)
[Nexus 4 Original Android Development] Mercado_Negro:
Hard to tell. Colors would match the navigation/status bar and clock while an image would fit the wallpaper style. I say both :D
[Nexus 4 Original Android Development] Jubakuba:
That's cheating!

One option only lol.

And if I just use colorize...I can color the little glowdots as well...

NOT doing an image picker for those little things.

Colorizing would also be 100x easier for the casual user who just wants it to match...
[Nexus 4 Original Android Development] Mercado_Negro:
I had to try my luck, no? lol

Yeah, colorizing would be way easier for the casual user but where will you let the fun of having boobies there as an image? :p

Now, being serious, I think I've never felt the need of having an image there because a padlock just makes sense, it's just one of those things that are perfect and carry the message on first sight. Also, the little glowdots colorizing sell idea right away because it would make it look more consistent.
[Nexus 4 Original Android Development] menkyy:
FYI! goo is back online :D

Sent from my Nexus 4
[Nexus 4 Original Android Development] pqee:
Anyone else have a few blank buttons on the calculator? The / - * signs are all blank buttons. I've had this on nearly every 4.3 version of aokp I've tried but haven't seen a single other person post about it.
[Nexus 4 Original Android Development] churchmice:
Glad to hear that you figured it out finally. Rock your N4.
[Nexus 4 Original Android Development] dankoman:
I'd personally prefer colorize. I like the stock look of the lock slider.
[Nexus 4 Original Android Development] GalaxyGusta:
Hi guys I'm on aokp milestone 2 android version 4.2.2 do I need to wipe before moving to the 4.3 nightlies and are they stable as of now?

Oh and custom kernels like Franco work on it cuz I know that CM is not working with most custom kernel
[Nexus 4 Original Android Development] dankoman:
i used to have that issue, but no longer have it.

try this:

https://play.google.com/store/apps/details?id=com.android2.calculator3&hl=en
[Nexus 4 Original Android Development] imeem:
i would say yes because going from 4.2.2 to 4.3 is consider a major update. As for stability of aokp 4.3.1, the only issues i have with it is random but lock deadlocks/freeze.
[Nexus 4 Original Android Development] GalaxyGusta:
oh well I haven't had any deadlocks with CM 10.2 so do you think i will have them with this one?

oh and can you briefly tell me what are the new features of AOKP in 4.3?
[Nexus 4 Original Android Development] Jubakuba:
Thank ya.

Colorize it is...and I agree. Poll closed ;)
[Nexus 4 Original Android Development] saranyan:
Does the latest official or whitehawxx nightly boot with its stock kernel?
[Nexus 4 Original Android Development] Lush78:
No... Not without fixes...
[Nexus 4 Original Android Development] pkelly517:
Perfect!

Colorize and Status bar User Font!

:thumbup:
[Nexus 4 Original Android Development] BLADESMAN1889:
The one thing that's struck out at me recently is the WHITE keypad on pin unlock - when everything else is matching color on Lockscreen - clock, nav buttons & on screen user message.

Sent from NEXUS⁴ via XDA Prem [AOKP 4:3:1]​
[Nexus 4 Original Android Development] core720:
the latest version is in black screen on boot
[Nexus 4 Original Android Development] dankoman:
kernel is fubar. need to flash alternative.

read two pages back, others fixed it by flashing aftermarket kernel.
[Nexus 4 Original Android Development] core720:
flash franco kernel and dont work
[Nexus 4 Original Android Development] imeem:
I had deadlocks/freeze even on stock 4.3 so it might be only me. (didn't have it in Puirty rom 4.3 tho).

As for features in AOKP 4.3, i'm not quite sure the difference but the ones I use at least are present in both version.

I personally went back to 4.2.2 milestone 2 build because i want more stability and less bugs.
[Nexus 4 Original Android Development] Andre_Vitto:
tell me more
[Nexus 4 Original Android Development] wuud:
when using october 12 build and any franco kernel (r191, r188, r184) I only get blackscreens.

When reflashing aokp with the stock kernel my screen works?! is there a problem with francos kernel and aokp builds atm?
[Nexus 4 Original Android Development] imeem:
on stock some apps and activities would freeze for a few seconds, then it resumes. For example if i were to press the recent window button, it would freeze and the nav bar glow would stay on even when i stop touching the button. But it wasn't as frequent and long compare to this rom and oct. 12 build.
[Nexus 4 Original Android Development] someboy:
MarcLandis' 10-22 night has black screen too,how could i fix it?
[Nexus 4 Original Android Development] JaylanPHNX:
I think you have to flash the color fix and a custom kernel like Faux123 or Franco. Again, I THINK.

Sent from my Nexus 4 blessed by AOKP and sanctified by Faux123.
[Nexus 4 Original Android Development] someboy:
i did that,flash color fix and franco jss,but the animation is broken.
[Nexus 4 Original Android Development] aanonymoushuman:
Dumb question, but do I use jss or jwr kernels?
[Nexus 4 Original Android Development] Jubakuba:
Boop.
[Nexus 4 Original Android Development] nikwen:
Good job. :good:

http://gerrit.aokp.co/#/c/13154/

http://gerrit.aokp.co/#/c/13155/
[Nexus 4 Original Android Development] bisco:
AWESOME!!

thanks for your work!!
[Nexus 4 Original Android Development] AlexForTomorrow:
Just wanted to report latest Marclandis build doesn't boot with either JWR or JSS kernels.

(Damn, it's been a long time since my last post here LOL)
[Nexus 4 Original Android Development] j0hnh0lmes:
It'll boot using colorfix and custom kernel, but there is a horrible screen tearing every time you scroll.
[Nexus 4 Original Android Development] AlexForTomorrow:
Well I tried with the JSS + colorfix but it was stuck on the boot animation.

Guess we'll have to wait next build for a fully CAF-free JWR compatible build.

Sent from my #HOLO Nexus4
[Nexus 4 Original Android Development] ieatacid:
This is what I'm getting too.
[Nexus 4 Original Android Development] pkelly517:
Someone's been looking at gerrit.

All the caf stuff has been removed from mako and flo. JWR kernel is being called, so deadlocks should be gone. It was a good night for mako.
[Nexus 4 Original Android Development] dankoman:
kit, works great! patchset 2 to RC commit fixes the text color changing after canceling lock icon color dialog thingy, as expected :good: