yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] casonswag:
Why when i flashed the 188 kernel on aokp or carbon im getting a discoloration type thing going on like the colors get inverted? I flashed the jss version
[Nexus 4 Original Android Development] GalaxyGusta:
It is also on cm
[Nexus 4 Original Android Development] anshumandash:
Carbon has reverted those commits from CM. You can try 3rd Oct nightly which is available for download now. Use JWR kernel with 3rd Oct or later Carbon nightly.
[Nexus 4 Original Android Development] ashjas:
ive tested this feature.. strangely, after enabling this feature, whenever i make a call my phones locks itself while on the call(i hear the lock sound too during the ongoing call) and when i end the call i find the device to be locked. Is this a side effect of this feature? because once i disable this feature i get back the default behaviour.

I dont think this should happen?

thanks .
[Nexus 4 Original Android Development] GalaxyGusta:
HI can somebody give me the values of colors and gamma of 44_BUNDI22?

i want to apply them to the CM screen calibration tool and since franco is no longer works on CM I miss this color profile so much!!

---------- Post added at 02:50 PM ---------- Previous post was at 02:38 PM ----------

HI can somebody give me the values of colors and gamma of 44_BUNDI22?

i want to apply them to the CM screen calibration tool and since franco is no longer works on CM I miss this color profile so much!!
[Nexus 4 Original Android Development] zorginho:
Inviato dal mio Nexus 4 con Tapatalk 4
[Nexus 4 Original Android Development] terranox:
hi, can anyone give me the settings for battery?

Enviado desde mi Nexus 4 usando Tapatalk 4
[Nexus 4 Original Android Development] hughfollett:
[MENTION=3292224]franciscofranco[/MENTION] what do you think of battery life extender? Is it useful or just placebo? TIA

Inviato dal mio Nexus 4 con Tapatalk 4
[Nexus 4 Original Android Development] kecinzer:
[MENTION=3292224]franciscofranco[/MENTION]

Can you please tell me how you increase notification loudness? I can't find any changes in kernel source.

Thanks.
[Nexus 4 Original Android Development] Angel0fDeath:
This happened to me too on CM10.2 nightly :/ I had to reflash CM to fix
[Nexus 4 Original Android Development] remydlc:
You need to flash the new radio I believe when you u upgrade to 4.3. Search it.

[/COLOR]

---------- Post added at 09:20 AM ---------- Previous post was at 09:19 AM ----------

---------- Post added at 09:21 AM ---------- Previous post was at 09:20 AM ----------

---------- Post added at 09:22 AM ---------- Previous post was at 09:21 AM ----------
[Nexus 4 Original Android Development] terranox:
Anybody?

Enviado desde mi Nexus 4 usando Tapatalk 4
[Nexus 4 Original Android Development] quiquegabriel:
[MENTION=3292224]franciscofranco[/MENTION] Is it possible to turn a little bit down the mic gain?? Driving me crazy when I record in loud places... :laugh: Thanks
[Nexus 4 Original Android Development] alanwyl:
NO
[Nexus 4 Original Android Development] anshumandash:
It only helps if you want your phone battery to stop charging at 90% or something to reduce battery charge cycles and increase the life expectancy of the battery (Component). I don't see any other benefit of using it. It does not give any extra SOT or something.
[Nexus 4 Original Android Development] Manbot27:
Franco had said he would push out a hot fix of 188 to address the constant toast messages. Anyone know if it's done and I should reflash?
[Nexus 4 Original Android Development] :
Is FKU still on sale? My friend got envious with my phone, he wants to buy it. Sorry, I have to ask here, Google Play Store keeps giving me an error. Thanks for those kind enough to reply.

Sent from my Nexus 4
[Nexus 4 Original Android Development] int abacus:
Yes, it is currently on sale.
[Nexus 4 Original Android Development] hughfollett:
Still on sale ;)

Inviato dal mio Nexus 4 con Tapatalk 4
[Nexus 4 Original Android Development] franciscofranco:
PA Rc2 is just fine, you can use it with r188 without any known problems.
[Nexus 4 Original Android Development] franciscofranco:
You can reduce the gain. Command is on r188 changelog. FKU will have all this, gotta speed up the app re-code.

Well thanks, but the display app has to work. Im gonna take a look.
[Nexus 4 Original Android Development] occtec:
That's the only reason I purchased your fku app :confused:
[Nexus 4 Original Android Development] amirsardari:
hi im on stock 4.3 with r188 and FKU BUT GAMA INJECTION DOESN'T WORK. ONLY COLOR INJECTION IS WORKING
[Nexus 4 Original Android Development] lexcyn:
Happened to me as well... I tried an older version of FK and got the same results, so it could be something CM changed in the latest nightly. But very strange indeed...
[Nexus 4 Original Android Development] Mantulis:
I see Caps Lock working good :rolleyes:

And what you mean injection? Did you try turning screen of/on.
[Nexus 4 Original Android Development] franciscofranco:
Caps lock is fun.

I'll say it for the 10000th time: for Gamma screen off/on. You know IT Crowd? "Did you try turning it off and on again?"
[Nexus 4 Original Android Development] wywerny:
Does r188 come with touch-to-wake feature?
[Nexus 4 Original Android Development] limeaide:
Yes but once search is re-enabled on xda I suggest searching Francisco's posts for the command.
[Nexus 4 Original Android Development] EuroAsia:
Hi guys ;

I use Miui Rom 4.2.2 JDQ39 version.

which one download? JWR-JSS?

thnaks..
[Nexus 4 Original Android Development] Angel0fDeath:
Yeah its CM because I flashed this kernel a couple days ago . It happened when I downloaded and flashed the latest nightly yesterday.
[Nexus 4 Original Android Development] xanthrax:
none , franco deosn`t support miui
[Nexus 4 Original Android Development] EuroAsia:
anyone kernel support miui kernal? hells core vs..

thnaks..
[Nexus 4 Original Android Development] franciscofranco:
Don't use the latest CM nightly if you want to use FK or any custom Kernel for that matter.
[Nexus 4 Original Android Development] xanthrax:
Only miui knows ...

sent from my Darkside of Nexus 4
[Nexus 4 Original Android Development] Angel0fDeath:
Do you why this happened ? Your kernel used to work fine before on previous CM Nightlies.
[Nexus 4 Original Android Development] Testraindrop:
Was already mentioned a few times, but here is a good explanation:

http://xdaforums.com/showpost.php?p=46098546&postcount=15393
[Nexus 4 Original Android Development] franciscofranco:
Because the guys over CM decided to go retard mode and made a single repo for Mako and Flo based on CAF tree instead of AOSP tree so now they use a different hardware composer which is not compatible with AOSP tree unless changes are made. And those changes are possibly going to derp something else on normal custom roms/stock. Its a no go for me.
[Nexus 4 Original Android Development] franciscofranco:
Yes, thats a great explanation! :)
[Nexus 4 Original Android Development] EfrainTrejo:
No worry's for me I use psx
[Nexus 4 Original Android Development] franciscofranco:
PA will be the rom of choice for users who like custom roms coming 4.4, its going to be a no-bullshít rom (it already is though). I'm glad that I'm gonna help them move to another level :)
[Nexus 4 Original Android Development] rxmxsh:
Carbon has removed the CAF mess from their rom for Mako and Flo as of today's build. Now it's compatible w/JWR kernels.
[Nexus 4 Original Android Development] Pipusz:
You mean these?

/sys/module/lge_touch_core/parameters/doubletap_to_wake

Open the doubletap_to_wake and then change the N to 1 then save and exit.

Or run terminal emulator and type:

Su

Echo 1 > /sys/module/lge_touch_core/parameters/doubletap_to_wake
[Nexus 4 Original Android Development] limeaide:
Did you read Francisco's answer above mine?

Sent from my Nexus 4
[Nexus 4 Original Android Development] Pipusz:
Yap, I just posted it, so anyone can write it down, save it to a document or whatever.
[Nexus 4 Original Android Development] llevo3:
when i enable doubletap_to_wake, i can wake up the screen by touching it twice at intervals of a few seconds (1, 2...even 4 seconds between to taps), so problem is that the screen unlocks when i put the phone in pocket etc...

edit: i'm on slimbean 1.4 and r188 jwr
[Nexus 4 Original Android Development] Andre_Vitto:
d2w is experimental now.. there are many things franco will fix in a while.. that is why its advisable not to enable it..
[Nexus 4 Original Android Development] franciscofranco:
Sorry I don't give support for options that I did not announce as being ready for every day use. It has bugs and I know it.
[Nexus 4 Original Android Development] llevo3:
i didn't ask, i just reported
[Nexus 4 Original Android Development] amirsardari:
my caps stucked suddenly sorry for that ;)

i mean gamma setting doesn't work .

turning screen on/off doesn't work neither rebooting device

stock 4.3jwr66y with r188 and FKU and color control .

EDIT : it works after off/on screen with 3 or 4 second delay before turn it on . but its revert back to default when i reboot my device
[Nexus 4 Original Android Development] Tex99:
franco 188 with purity : no problem, no reboot, all perfect. smooth in every situation, wonderful color (thanks to obsanity).
[Nexus 4 Original Android Development] michelemascia7:
With slimrom the kernel work greatly :D

Inviato dal mio Nexus 4 con Tapatalk 4
[Nexus 4 Original Android Development] RohanM:
phew ... just finished reading after 1st oct pages [ took me more than half hour :mad: ].. so far I got is franko released 185, 186 , 187 & finally 188... ahh I am on 184 & will now flash 188.. let's hope there is no 189 now :p
[Nexus 4 Original Android Development] drawde40599:
Wrong guy sorry.

---------- Post added at 10:06 AM ---------- Previous post was at 10:03 AM ----------

There trying to actually fix the deadlock issue instead of just removing code and call it fixed so it broke some **** :P , in the mean time Just use older build before last one it works flawless not like youe going to be able tell the difference anyway.

Funny to see everyone freaking out on a NIGHTLY TESTING build of CM then just ditch them for roms that CM wrote 90 % of the code for the foncy features we like . :P ;)

---------- Post added at 10:07 AM ---------- Previous post was at 10:06 AM ----------

There trying to actually fix the deadlock issue instead of just removing code and call it fixed so it broke some **** :P , in the mean time Just use older build before last one it works flawless not like youe going to be able tell the difference anyway.

Funny to see everyone freaking out on a NIGHTLY TESTING build of CM then just ditch them for roms that CM wrote 90 % of the code for the foncy features we like . :P ;)
[Nexus 4 Original Android Development] JNewms:
186-188 were all released within a short time frame because people were really quick and helpful in getting Franco logs so he could fix the problem immediately. You gotta love watching helpful development discussion in real time. :)
[Nexus 4 Original Android Development] InsaneJester17:
so, I hate to ask, but is there any fix for the color issues on the latest CM nightly? or should I revert to an older nightly?
[Nexus 4 Original Android Development] rxmxsh:
90% That seems high. I left CM a while ago because they do not allow customization to the same level as others. Also, I believe for many, leaving CM wasn't based off this one nightly. It's based on the direction CM is moving toward and not everyone agrees with it.
[Nexus 4 Original Android Development] drawde40599:
Dont alow ANYMORE , your 100% right, but if u dig deap deap enough CM is involved in..... Even if they dont support anymore
[Nexus 4 Original Android Development] thebryceee:
Sure. Hold down power button until menu pops up. Press Power Down Phone.
[Nexus 4 Original Android Development] limeaide:
I really think you are fighting a losing battle in this thread trying to hype CM.

Sent from my Nexus 4
[Nexus 4 Original Android Development] drawde40599:
I Didn't realize that was what im trying to do , . Thank u for clarification
[Nexus 4 Original Android Development] limeaide:
Well that is how I interpret your statement here and the subsequent ones.

Ive also seen you tell people to stop using pa because it is the root of their problems when you have no clue what the problem really is.

So forgive me if I think you are trying to hype CM if that is not your intention.
[Nexus 4 Original Android Development] franciscofranco:
Ok lets all be friends :)
[Nexus 4 Original Android Development] limeaide:
:D

[YOUTUBE]hKkIiOsxvxM[/YOUTUBE]
[Nexus 4 Original Android Development] Floydfire:
I know is offtopic but I want to tell how ****ing unbrickable is a nexus 4 and how much I'm dumb... So I was flashing latest version of twrp through flashify but without paying too much attention I have flashed it in boot image partition (kernel) so every time I reboot the phone it go to recovery. So after some time of thinking I thought well I'll try in fastboot to flash Franco! Yeah and I booted on fastboot and typed on my PC fastboot flash recovery boot-r188.img , yeah! You read well... But it booted also on twrp so reflashed pa +gapps and then I thought what I stupid I'm. BTW reflashed Franco and now I have also fixed the problem with aptic... I think is because the first time I have booted pa I didn't booted with his stock now work really well!

Inviato dal mio Nexus 4 con Tapatalk 4
[Nexus 4 Original Android Development] GerhardKi:
Is it normal, that cpu 1 never goes below 1.5 GHz in kernel version 188. All other cores scale just fine. Rebooting, resetting fku and reinstalling the kernel doesn't change that. This does not happen when I use 182.
[Nexus 4 Original Android Development] Arstoien:
No, that's not normal. Used to have similar issue but Franco fixed it. Did you try to clean franco's app data and then reflash the kernel in that order? I'm not having such issues.
[Nexus 4 Original Android Development] Angel0fDeath:
So I could just flash the older CM build over the newer one ? No problem right ?
[Nexus 4 Original Android Development] drawde40599:
Yep its what i did, works with no issues, i think i have the build from the 1st (battery dead on N4's) so cant check, im using G2 atm :P
[Nexus 4 Original Android Development] Angel0fDeath:
Could you tell me if you have the build from the 1rst when you can? (Just to make sure)
[Nexus 4 Original Android Development] drawde40599:
The second was last build before everything went nuts, so its the first. But i can look when i get home np, if someone dosent beat me to it
[Nexus 4 Original Android Development] Angel0fDeath:
I think it might be the first because I'm on the Oct. 2nd build right now and I have the problem.
[Nexus 4 Original Android Development] franciscofranco:
Thats not normal. Which governor are you using?
[Nexus 4 Original Android Development] gtr-kir:
FranciscoFranco, hi! :)

Can you tell, what will be with CM + your kernel? Will you replace drivers(i dont now correctly whats happened with last builds CM) from AOSP to CAF? And what drivers are better: CAF or AOSP? Explain please just what is happening at the moment, and that scared some strange words, do not want to work CM+franco.kernel ..

Sorry for my bad English(i'm using g.translate + some knowledge from schoo;) and limited knowledge in the field of software about CM and your kernel.

Thanks :)
[Nexus 4 Original Android Development] Das IceDice:
If I'm understood correct orientation sensor consume less power than touch sensor? Would it be possible to make that touch sensor is only active when phone is orientated "stand up"? Even if power consumption is equal this would be neat option to reduce false wakes. Or is this even possible on kernel side, only app level thingy?
[Nexus 4 Original Android Development] terranox:
Thanks

Enviado desde mi Nexus 4 usando Tapatalk 4
[Nexus 4 Original Android Development] redandr:
The answer to this question would be interesting for me too :)
[Nexus 4 Original Android Development] sNoxious:
Revert.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Testraindrop:
0110 nightly was working, but for me it had some weird hiccups and lockups (not deadlocks), so right now I'm back to 2709 nightly until CM reverts it or I can find another good Rom.
[Nexus 4 Original Android Development] franciscofranco:
Touch sensor? Theres no such thing.

Those sensors are only accessible from Android side.

The explanation is 2 pages ago or something.
[Nexus 4 Original Android Development] Testraindrop:
Franco you wanted to fix some SU issues recently in FKU, have you already found the root cause?
[Nexus 4 Original Android Development] tarroyo:
Anyone know if [MENTION=3292224]franciscofranco[/MENTION] is gonna move away from AOSP kernels? So that this color kernel issue can be resolved.
[Nexus 4 Original Android Development] gharrrrrr:
:rolleyes:
[Nexus 4 Original Android Development] BytecodeMe:
Hopefully not.
[Nexus 4 Original Android Development] franciscofranco:
I know what the problem is, just been a bit busy and I didn't get around of working on that yesterday.

I am not moving away from Google tree.With all due respect CM can go kiss their own arse for what I care :)
[Nexus 4 Original Android Development] epidemic11:
I just want to clarify something. If doubletap to wake is enabled, would the digitizer be turned on for the whole time? If so, won't this damage the digitizer? Thanks!
[Nexus 4 Original Android Development] franciscofranco:
Digitizer is kept active is. No, it won't damage it. That would be the same as saying that using the device would damage it, which is false.
[Nexus 4 Original Android Development] :
Franco how different is your implementation from Touch Control?

Sent from my Nexus 4
[Nexus 4 Original Android Development] franciscofranco:
I don't know what is inside Touch Control, the code is not public.
[Nexus 4 Original Android Development] ashjas:
[MENTION=3292224]franciscofranco[/MENTION], i have an issue with double tap to wake.. after few hours of deepsleeping.. the screen becomes unresponsive to touches.. the power button can wake the device, but since touch screen has gone unresponsive, i cant unlock it.. cant take up call etc.. only solution is to reboot the device. any way i can help next time this happens?

secondly, i had posted earlier that after enabling touch to wake, during ongoing call, the device locks itself after few seconds of putting the phone to ear(i.e after the proximity sensor kicks in) i can hear the lock sound as well when this happens during the call.

And i have tested that this does not happen when touch to wake is disabled.. is this a side effect of this feature?

Im on Nexus4 franco kernel r188
[Nexus 4 Original Android Development] franciscofranco:
Yes its a side-effect. I'm aware of it. The functionality is not ready for every day usage.
[Nexus 4 Original Android Development] GerhardKi:
I am using the default governor. I also had a very strange reboot after 1h using 188 where the PA start animation would draw very slowly. I am running PA 3.99.

I will try to get you a logfile next time it happens. I am currently back to 182 as this is very stable and smooth. I will try 188 again over the weekend.
[Nexus 4 Original Android Development] markd0wn:
Say hello to Android 4.3.1 (JLS36I)...

Obligatory questions that we don't yet have the answers to:

1. Will this arrive to all Nexus devices, meaning they'll all have the same build and we can go back to having one custom kernel for all?

2. Does this fix the deadlocks for JLS branch?

(if the answer to both is yes, CM will revert the hardware composer changes thingy, there will be an end to JWR vs. JSS vs. JLS thing, and one version of franco for all roms, at last).

Time will tell.

(Personally, I wouldn't be surprised if this changes nothing -- deadlocks still a problem, and a new JWR build shows up which is 4.3.1 for non-Nexus 7 devices)
[Nexus 4 Original Android Development] michelemascia7:
What is the difference between hispeed_freq and max CPU frequence?

Inviato dal mio Nexus 4 con Tapatalk 4
[Nexus 4 Original Android Development] miqz:
sorry if this already asked

which one i can use for PA 3.99-RC2, JWR or JSS ?

this is my first day use N4 ;)

thanks
[Nexus 4 Original Android Development] genkralyz:
jwr :)

Sent from my Nexus 4
[Nexus 4 Original Android Development] blsrbl:
JWR.
[Nexus 4 Original Android Development] zephiK:
And source.. http://www.androidpolice.com/2013/1...e-nexus-7-receiving-android-4-3-1-ota-jls36i/
[Nexus 4 Original Android Development] miqz:
ok and last question can i use JSS kernel with all rom e.g Purity or PSX ?

thank you for the answer
[Nexus 4 Original Android Development] Pipusz:
Use the one that matches the base of the ROM (either JWR or JSS) or you are likely to encounter problems like screen tearing and what not.
[Nexus 4 Original Android Development] GalaxyGusta:
Yes but pay attention to the base

And don't use it on CM
[Nexus 4 Original Android Development] PnkPwrRngr:
Anyone try r188 with cm nightly 201310004?
[Nexus 4 Original Android Development] Tobias.C:
wrong colors

Hi,

I have problems since the release of 187. Same Problem with 188. Running CM 10.2

There is something wrong with the colors.Example: Everything blue turned into yellow. The screen looks very weird.

When I make a screenshot and look at it on my computer, the colors are right again.
[Nexus 4 Original Android Development] RohanM:
It's no more compatible with CM since last nightly.. until Franko do some magic... :cowboy:
[Nexus 4 Original Android Development] Tobias.C:
Yes I tried. No problems, just the colors yet.

---------- Post added at 03:58 PM ---------- Previous post was at 03:52 PM ----------

okay thats good to know, but he offers the JSS versions of the kernel so i thought it supports cm 10.2...
[Nexus 4 Original Android Development] jmudrick:
You all on CM really need your own thread. Getting tiresome.
[Nexus 4 Original Android Development] :
Lol"

Sent from my Nexus 4
[Nexus 4 Original Android Development] arlenwoot:
They have their own thread, they're just not bothering to read it.
[Nexus 4 Original Android Development] Waldos:
First at all, Thats why i think that it is not a good idea to have two kernerls: JWR and JSS. Now JSL... dont f*** me Google.

Second, [MENTION=3292224]franciscofranco[/MENTION] on the tpa2028d1.pdf page 22, there are the "AGC RECOMMENDED SETTINGS" im not an audiophile, so my ears are limited. So, I think that the best vales are "Rock". [MENTION=5087599]Mercado_Negro[/MENTION] can you tell us if this is correct??
[Nexus 4 Original Android Development] Mercado_Negro:
Yes, that would be a good start point. Using those values as default wouldn't hurt either (keeping the compressor off by default of course).
[Nexus 4 Original Android Development] franciscofranco:
I can make them default no problems :)
[Nexus 4 Original Android Development] RohanM:
BTW what is this JWR & JSS ? How do I find which one I have ? :confused:
[Nexus 4 Original Android Development] franciscofranco:
That was me when I read your post. There has been 20 daily posts about that since 4.3 is here :)
[Nexus 4 Original Android Development] Waldos:
Why? The datasheet says 2:1. Is too loud? I ask you because i didnt read more ppl talking about this topic.
[Nexus 4 Original Android Development] RohanM:
Nevermind, I got it.. JWR66Y is mine. :cowboy:

But then who got that JSS ? is it region specific ? :eek:
[Nexus 4 Original Android Development] Waldos:
I watched that game, and that coach (America's team) went crazy when wons that cup.
[Nexus 4 Original Android Development] arlenwoot:
http://xdaforums.com/showthread.php?t=2382880