yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] Bobtehblob:
Is anyone else having some minor audio stutter on Franco kernel? I thought it was just cm playing up but now that I'm on Pa, it's happening there as well. Not a big issue, just stutters occasionally (roughly every 5-15 mins)
[Nexus 4 Original Android Development] franciscofranco:
Headphones or speaker?
[Nexus 4 Original Android Development] Bobtehblob:
Headphones :)
[Nexus 4 Original Android Development] Redneck Trash:
Delete

---------- Post added at 08:24 PM ---------- Previous post was at 08:23 PM ----------

I've only had it happen through headphones. I also use Viper4Android.

---------- Post added at 08:25 PM ---------- Previous post was at 08:24 PM ----------

I've only had it happen through headphones. I also use Viper4Android.

---------- Post added at 08:25 PM ---------- Previous post was at 08:25 PM ----------

Stupid Tapatalk app. And since when did I have to wait 20sec between posts on XDA?

---------- Post added at 08:26 PM ---------- Previous post was at 08:25 PM ----------

Stupid Tapatalk app. And since when did I have to wait 20sec between posts on XDA?

---------- Post added at 08:27 PM ---------- Previous post was at 08:26 PM ----------

Stupid Tapatalk app. And since when did I have to wait 20sec between posts on XDA?

---------- Post added at 08:28 PM ---------- Previous post was at 08:27 PM ----------

Stupid Tapatalk app. And since when did I have to wait 20sec between posts on XDA?

---------- Post added at 08:29 PM ---------- Previous post was at 08:28 PM ----------

Stupid Tapatalk app. And since when did I have to wait 20sec between posts on XDA?

---------- Post added at 08:31 PM ---------- Previous post was at 08:29 PM ----------

Stupid Tapatalk app. And since when did I have to wait 20sec between posts on XDA?

---------- Post added at 08:32 PM ---------- Previous post was at 08:31 PM ----------

Stupid Tapatalk app. And since when did I have to wait 20sec between posts on XDA?
[Nexus 4 Original Android Development] franciscofranco:
I don't have that, sound control code has been the same for a while. I don't use any sound mod like ViperSomethingSomething.
[Nexus 4 Original Android Development] Bobtehblob:
I feel like it's been happening since the move to 4.3 but I can't be for sure. I've got my own gain and volume boost settings so perhaps that has something to do with it? It also only happens when the screen is off for an extended period of time. I might jump back onto the stock PA kernel for a bit and see if it happens there :)
[Nexus 4 Original Android Development] franciscofranco:
Do you have the suspend freq too low?
[Nexus 4 Original Android Development] Bobtehblob:
It's on the default of 702mhz.
[Nexus 4 Original Android Development] franciscofranco:
Dunno then, sorry.
[Nexus 4 Original Android Development] mymeatb18:
I dont know if it's cuz I used trickster mod with your kernel before getting ur app or if its the switch to 188 but I find my self trying to kill the battery now compared to 184. Never had this much sot. Sweet kernel dude!!!
[Nexus 4 Original Android Development] franciscofranco:
r189:

* Improve my interactive's touch boost implementation to reduce the latency between touching the display and actually boosting the CPU. Should increase the device fluidity and improve the battery in the long run because due to improved latency timings I reduced the boosted time from 1s to 0.25s

* Merged Tassadar's KEXEC patch so that you can run his MultiROM work. More info here: http://xdaforums.com/showthread.php?t=2472295
[Nexus 4 Original Android Development] miqz:
Can i just flash from r188 yo r189 without wipe?
[Nexus 4 Original Android Development] int abacus:
Yes... just flash it in recovery or autoflash from app
[Nexus 4 Original Android Development] Redneck Trash:
I see you set input_boost_freq to 0 which is a departure from the norm. I usually set it to 0 because for my usage I see no benefit in a boost when touching the screen. I'm assuming that the changes in governor control negates any previous benefit to input_boost_freq.
[Nexus 4 Original Android Development] franciscofranco:
Ups, input_boost_freq is not being used, I have to remember not to code at 6am anymore. Anyway, the device is being boosted to 1,2GHz on touch I just checked. I just forgot to initialize that input_boost_freq var.
[Nexus 4 Original Android Development] Redneck Trash:
So currently on r189 there isn't a way disable touch_boost_freq within the app?
[Nexus 4 Original Android Development] franciscofranco:
Apparently not :)
[Nexus 4 Original Android Development] kecinzer:
I'm afraid that Carbon ROM use JSS kernel. According this - https://github.com/CarbonDev/android_device_lge_mako/commits/jb3

In my AOKP builds (named AOKPK) I compile it with franco.Kernel (https://github.com/kecinzer/francoKernel_mako) directly and also with Linaro toolchain.

Using projects from my repo - https://github.com/AOKPK
[Nexus 4 Original Android Development] Mercado_Negro:
No, Carbon uses a JWR kernel atm
[Nexus 4 Original Android Development] kecinzer:
So they didn't pushed actual source yet. Because due to the repo that I posted, there are not JWR patches.
[Nexus 4 Original Android Development] castironpuppet:
Beautiful! :victory: I've been looking forward to this
[Nexus 4 Original Android Development] Mercado_Negro:
Yeah, that's what I think. In fact, I think this change is not official yet. They've been working out the CAF issues we've seen the last days.
[Nexus 4 Original Android Development] zephiK:
It is official. Carbon uses JWR and Team Carbon member winner00 said it on the same day about CAF. They removed the commits and it uses a JWR kernel full out. Using a JSS causes screen tearing.
[Nexus 4 Original Android Development] Mercado_Negro:
Oh good, I thought it wasn't official yet. Thanks for clarifying that.
[Nexus 4 Original Android Development] thunder9111:
I just tried r189 and my portable wifi hotspot just doesn't works. If I go into settings, it'll actually say "error". Is there anything I can do?

I want to try this kernel badly, but I do need the portable wifi hotspot functioning

(I am using PA3.99r2, and my tethering is not locked, I have been using regularly previously)
[Nexus 4 Original Android Development] zephiK:
Not a problem, I'm actually happy they went the JWR route as it fully gets rid of the deadlock problem regardless or not people encounter it or not. Nice to know it is dealt with once and for all.

Edit: kind of getting off topic but if you do use Carbon, check out https://docs.google.com/document/d/1Zcp6iVWVw_7iH-ErnKgkYy3r5QuqV8PHFoQMb8hoBwQ/edit as it is a nice and condensed spot for the changes of the ROM in a very user friendly format.
[Nexus 4 Original Android Development] Arstoien:
Many changes in the interactive governor settings? Timer now down to 20k an. hispeed 1.2 GHz? Did something messed up on my flashing or that's new defaults? Why lowering the timer, was 35k too much?

Also one thing, which I was curious about: does the touch boost depend on the timer or it's called only by screen touch, so it won't suffer delay if the timer is bigger?
[Nexus 4 Original Android Development] Redneck Trash:
Hispeed_freq was a recent change. I think on the previous version. There has been changes with r189 but so far I haven't come across any issues. Whatever Franco has been tinkering with seems to be working.
[Nexus 4 Original Android Development] ziddey:
Were you coming from an earlier build of franco kernel? It's been said repeatedly that there were no changes to the wifi driver. Certainly there are no changes among the recent builds. Hotspot working just fine over here on CM.
[Nexus 4 Original Android Development] :
[MENTION=3292224]franciscofranco[/MENTION]:

FKU bug - it downloads the JSS version for SlimBean (build 1.6), which actually needs the JWR one.

It autoflashed the JSS version. Is there any problem if I flash the JWR one over that?

How exactly do i cancel an autoflash and choose the right version? (for the next time)

Can you implement a setting, where I can choose which version I need, in case the autodetect fails?
[Nexus 4 Original Android Development] PeQuEsan:
Hi and thanks for your preset but... I don't understand that sentence. You say you've had to bump whites to 71... but as I can see in FKU, your preset sets whites to 103 across all colors... ¿? So I don't see any other way that to increase brightness...

BTW, I also like your preset, but I've got to increase brightness (its 0).
[Nexus 4 Original Android Development] fkrone:
Why not including an "expert mode" in FKU? With this enabled it shows settings like undervolting and choosing the kernel version to flash. This would give the more advanced users all the freedom they want and the normal user will see his settings as before and would not be confused.
[Nexus 4 Original Android Development] :
[MENTION=3292224]franciscofranco[/MENTION]:

I second this. Especially when some ROMs tend to change patches and merges, resulting in JWR vs JSS branch changes.

Pretty please? :D
[Nexus 4 Original Android Development] Redneck Trash:
As far as I know know you should be fine flashing JWR over JSS. I'm not aware of anyone having issues doing so.

As far as the right version being flashed it's known that (and by Franco's admission) fKu is stupid regarding this. For now it'd be best for you to download the correct version from the OP.
[Nexus 4 Original Android Development] sordna:
Why not use a browser to download the kernel of your choice? An advanced user, who would know if his ROM reports the wrong thing, surely can bookmark this link: http://minooch.com/franciscofranco/Nexus4/4.3/

on any phone browser, and download the preferred one straight to the sdcard. You can then use FKU to flash it (just download the .img and put it in the kernel_backups directory), or download the zip and flash it with recovery.
[Nexus 4 Original Android Development] :
Of course, as an advanced user I can. But, that doesn't mean I should.

I'd prefer the simple convenience of having an extremely simple two-option setting in FKU to choose JSS/JWR.

It would be extremely easy to implement, compared to FKU auto-guessing the right one, IMHO.

---------- Post added at 01:55 PM ---------- Previous post was at 01:54 PM ----------

OK. I've flashed the JWR one now. Seems fine so far.

A two-option setting would make it much easier though...

[MENTION=3292224]franciscofranco[/MENTION] - Please? :)

Also, how do I stop an autoflash from happening? I can't seem to find any stop button, while the kernel is downloading. :|
[Nexus 4 Original Android Development] Arstoien:
Let me just say that whatever you've done to increase the touch responsiveness of interactive really makes a difference. Much better and lag-free experience.
[Nexus 4 Original Android Development] kypeth:
don't hit autoflash to begin with, select "Download .zip"
[Nexus 4 Original Android Development] :
Haha, :o, OK then.
[Nexus 4 Original Android Development] arlenwoot:
Same here, this build is amazing so far.
[Nexus 4 Original Android Development] cryingrock:
Idk how to explain but, with r189, although the response to touch is quicker, the smoothness(scrolling etc.) is worse.
[Nexus 4 Original Android Development] pitjago74:
By The way......is by default Deadline?

neXus4
[Nexus 4 Original Android Development] :
Nope, it's ROW.
[Nexus 4 Original Android Development] thunder9111:
Nope I was using stock paranoid android previously. Hotspot worked. I have also used franco kernel with stock rom. Hotspot worked.

Only thing that isn't working is PA + franco, i can't get the hotspot to work at all.
[Nexus 4 Original Android Development] PeQuEsan:
Can't see that, sorry. Interactive is performing good, but I always prefer to wait since we've got 2-3 days up and running to confirm. A recently rebooted android always performs way better than after some days of usage.

[MENTION=3292224]franciscofranco[/MENTION]! Thanks a lot for taking into account our suggestions.
[Nexus 4 Original Android Development] stormtroopercs:
UV=less heat= better performance
[Nexus 4 Original Android Development] blitz911:
Yes. I was on WiFi, but usually the signal bars next to it would either be gray/blue, but it turned black..I didn't turn WiFi off then, but the signal came back after a while..could be an isolated incident..not bugging over it..
[Nexus 4 Original Android Development] franciscofranco:
I've been having some problems with data/internet connection since r27 as well. r28 coming up soon - couldn't make it sooner because we've been setting our stuff for CES in two days.
[Nexus 4 Original Android Development] magictwins:
I mean better than UC

because performance is simply the CPU throughput which is mainly determined by its clocking frequency....

if your CPU can run good under 1.0V, it will have identical performance as when it runs under 1.2V, with less heat generated.

However, the main problem of UV is stability. CPU's real condition varies from chip to chip, the CPU in your N4 can run good under 1.0V doesn't mean the CPU in my N4 can do the same. Not every chip has the same condition, resistors or capacitors in IC can vary from chip to chip by as much as 50% in value and still considered to be qualified. Chip manufacturers set guide lines of the ranges of their product's operating conditions (i.e. voltage, temperature etc...). Those ranges are set according to large amount of field tests and obey the law of normal distribution. They are considered to be the most reliable and safe conditions under which the chips can run. By UV, you are walking out of that safe heaven and you are on your own.
[Nexus 4 Original Android Development] ManOnTheMoon:
Should I be very excited for CES this year?? ;)
[Nexus 4 Original Android Development] Godaemon:
r27 running great till now havent noticed any data or WiFi issues like r26 ...!battery isn't too much different from r23 which was really great
[Nexus 4 Original Android Development] franciscofranco:
Oh yes, at least from our part there will be some exciting stuff.

Heads up: if anyone goes to CES I'll be at the Texas Instruments, Delphi and Hyundai booths.
[Nexus 4 Original Android Development] knnhzx:
hi guys, after flashing the kernel in? is there any settings i need to turn on or change for the kernel to work? etc governor or just leave it?
[Nexus 4 Original Android Development] franciscofranco:
Ok r28 is up - shares the same HSIC patches as r23 so data/wifi should be working fine now.
[Nexus 4 Original Android Development] franciscofranco:
This kernel is flash and forget. Although if you're a power user you can always adventure yourself and see what you can adjust for your type of usage. No, I won't give you any "magical" settings because there is none - the most balanced settings I could find I already made them set in the kernel after you flash it.
[Nexus 4 Original Android Development] kitch9:
Shame there's potential data problems on R27... My phone lost 5% battery in 10 hours overnight.... 5 Mins msim wake lock!
[Nexus 4 Original Android Development] blitz911:
r28 is out with some data drop patches from r23. Should be near perfect, using it now..:D

---------- Post added at 10:21 PM ---------- Previous post was at 10:15 PM ----------

It's been said before, but many thanks to Franco. Such tireless efforts to update this kernel. Donated just because I use his stuff:thumbup::thumbup:
[Nexus 4 Original Android Development] KyraOfFire:
dafug you're talking about? I am not going to argue about capacitor/resistor tolerance here, but dude, it's 2013. Technologies are not that s****ty. Man landed on Moon four decades ago. Wake up man!

UV by default kernels has been done on the Nexus 4 by developers of high reputation. N4 CPU ships binning poll has been done with a decent sample size. Choosing to UV, you can have plenty of supports.

BUT..... franco.Kernel for Nexus 4 has no UV (you can add "yet" here if you want), and it has been discussed plenty. People need to move on. Just tell them to move on. Don't give bs facts, that won't help....
[Nexus 4 Original Android Development] knnhzx:
just flashed build 28 working well so far. awesome work!

i see a stable build coming soon
[Nexus 4 Original Android Development] Hrithan2020:
Wow! No need to be impolite.

Don't you think it is better, if you keep quiet if you don't understand a thing what you are saying. I can't say for sure regarding the capacitor/resistor tolerance [variation of 50%], but other things he talked about are correct. Why do you think qualcomm set the voltages at that level? It is because at that voltage, xx.xx% [ a certain threshold] of the CPU's ran fine at that voltage. Obviously it goes without saying that many of the CPU's could have run at a slightly lower voltage/quite low voltage based on the cpu. [ In case of Nexus 4 , maybe qualcomm has set very high threshold, which is why quite a few people are able to get by with even -200 mv UV]

The fact that it's 2013, doesn't change any basic rules of physics/electronics. This is how CPU's are manufactured,lol.
[Nexus 4 Original Android Development] Bigzinewicz:
So far so good on r28 I'm really liking this build so far even lag issue with haptic feedback on keyboard is much improved as well as no issues with data thank you for your hard work franco.
[Nexus 4 Original Android Development] visceralpsyche:
Had issues as well with r27 but r28 is working fine so far with CM10.1 20130103 :)

Cheers for your hard work Francisco!
[Nexus 4 Original Android Development] ben_pyett:
Enough about UV, use the report button to respond to posts that you object to, rather than further pollute an already over discussed topic. if you've read the thread you know this conversation has already been done to death already.
[Nexus 4 Original Android Development] fetto666:
Hm, with r28 there is no deep sleep when the charger is plugged in.

Is it supposed to do that?
[Nexus 4 Original Android Development] franciscofranco:
Thats how Android works since 2008.
[Nexus 4 Original Android Development] Pure Drive GT:
nexus 5 100% official https://www.digitec.ch/Startseite.aspx?param=details&wert=283007
[Nexus 4 Original Android Development] casonswag:
What happen to the 32 gig?!
[Nexus 4 Original Android Development] ben_pyett:
Sorry, this site doesn't translate well, how does this one source make it 100% official and why trust the details ie 16Gb from here rather than the previous leaked unoffical info?
[Nexus 4 Original Android Development] obsanity:
Mine sets it to 7. Are you sure we're talking about the same preset? I've seen a few obsanity presets. I'm talking about the one Franco built in to FKU as recommend settings.

Sent from my Nexus 4
[Nexus 4 Original Android Development] PeQuEsan:
Oops... I was talking about one named "31_obsanity", whichs comes when you download presets from FKU... I'll try that recommende settings instead.

Thanks a lot.

EDIT: Ok I applied recommende settings, and I can see "7" for whites across all colors. I've raised them to 71... but I still find it little dark IMHO... I've had to raise brightness a little bit, and now I'm happy with calibration :). But it's difficult to find a 100% happy preset... :P
[Nexus 4 Original Android Development] fkrone:
Don't believe this is true as it says (translated) that Android 4.2.2 is available on Google's developers site. So for me nothing is official until Google presents it.
[Nexus 4 Original Android Development] alakyr:
i guess franco.kernel still not compatible with cyano right? =(
[Nexus 4 Original Android Development] psyren:
Could someone please tell me exactly what CAF is, and why colours are broken on new ROM builds (and if they're related).

I've tried Googling and combing through various forums, but I've had no luck finding an answer. I either turn up Android Cafes or Code Aurora Forums, which I assume is much closer to the mark.
[Nexus 4 Original Android Development] uglavnom_bezopasni:
On the contrary, cm is not compatible with franco kernel :)
[Nexus 4 Original Android Development] Bill Gamble:
http://xdaforums.com/showthread.php?p=46098546
[Nexus 4 Original Android Development] bokagavrilov:
I might go offtopic here but I really wonder why does people use cm on Nexus devices? I can understand it about Samsung or HTC or other phones that doesn't have the pure stock experience... I found that stock+xposed(gravity box in this case) it's just incredibly stable and it gives me even more features then what cm has. I'm also on the same setup on my n4 and n7 and I never looked back.
[Nexus 4 Original Android Development] psyren:
CM does it again.

While Xposed is great, having the features it offers baked into the ROM allows for greater speed and stability than relying on Xposed to do it.
[Nexus 4 Original Android Development] zephiK:
Well if you're going for a ROM in terms of the number of features then you shouldn't be looking into CM in the first place as CM isn't the rom for features nowadays. They're the ROM for stability and reliability which in this case, doesn't make any sense for Nexus devices since Nexus devices have stable ROMs from day one simply because it is a AOSP supported device and less work is needed to be done to get it stable since we get the newest and latest Android and doesn't need backporting with all the binaries available etc etc etc.
[Nexus 4 Original Android Development] WhoIsJohnGalt1979:
+1000 have been on the above setup for the last one month and I couldn't agree more.
[Nexus 4 Original Android Development] kecinzer:
New poll on http://aokp.co/

Help those CAF stuff disappear and vote first choice.
[Nexus 4 Original Android Development] MaxFTW:
Do you know any good governor setup to improve smoothness on r189?

== Sent from my ParanoidMako ? ==
[Nexus 4 Original Android Development] Pure Drive GT:
- This does not mean that there is not going to be a 32gb version.

- that 4.2.2 is available is irrelevant

- this is basically confirming everything we already knew so why so skeptical

- the device has already been ordered by this shop, but only their employees can see the device as for now. but with this link i technically could already pre-order it. the page has just already been set up and will be made visible for all once oficially released.
[Nexus 4 Original Android Development] :
I found it laggy too. After playing with the governor, I couldn't get a good result so I went back to r188.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Arstoien:
It's slightly laggy after the initial touch boost is over and some animations or scrolling is still going. I think it's too short now. I'd like the option to change the boost time back, but I'd think franco's had a reason to remove it, probably related to the touch responsiveness he was improving.

I still prefer it over the previous version, gotta say!
[Nexus 4 Original Android Development] MaxFTW:
Its worse but you like it more...

ZOMG

== Sent from my ParanoidMako ? ==
[Nexus 4 Original Android Development] joni_strokes:
didn't find any lag on latest build with PA 3.99rc2, uv -125mV, and cpu governor was interactive
[Nexus 4 Original Android Development] MaxFTW:
Lags fixed :thumbup:

(So smooth!)

== Sent from my ParanoidMako ? ==
[Nexus 4 Original Android Development] Arstoien:
Yes, because the lag I see with this is different and less bothering than the previous version. Before sometimes it would lag when dragging the notification tray if I had some specific type of notifications – not any more. And other places in the ui are noticeably more responsive. I've got my animations time reduced to .5 from the developer settings so I don't see any lag when opening or switching apps. The lag which I was talking about shows only sometimes when scrolling. That's a good trade-off for me, but I can only assume franco will keep working on it and improving.
[Nexus 4 Original Android Development] momomok:
r189 is having slower performance when I play Ingress (the only game that I play on my N4) but having overall improved responsiveness in normal apps (like G+, Twitter) with a better battery consumption...