yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] jawz101:
is anyone on cm10.2? I haven't been able to get past the cyanogenmod spinning logo every time I've flashed 176 or 178 JSS. Consequently, I haven't been on Franco for a few weeks. Can someone verify this causes it?

1- make a nand backup

2- flash one of the JSS builds

3- boot

4- reboot just to show that it comes right back up

5- once back in go into FKU, custom kernel settings and disable fsync

6- reboot...

Normally the system comes back up within maybe 10 seconds or so. I've let it sit there for 10 minutes with nothing but a spinning cm logo.

To fix go into cwm recovery and at least restore the Data partition from your backup.

tldr- I don't disable fsync on cm10.2. I don't know if it affects other JSS builds
[Nexus 4 Original Android Development] Testraindrop:
CM10.2 works fine here.
[Nexus 4 Original Android Development] Lownita:
Compared to r163 I noticed that r178 has different stock values for thermal throttle, touch boost, haptic feedback. Is this intended?

Tapatalked from my Nexus 4
[Nexus 4 Original Android Development] jawz101:
with fsync disabled?
[Nexus 4 Original Android Development] sn0warmy:
Thanks for the replies. I'm glad I'm not alone. It's actually comforting knowing it's not actually my phone's hardware that is the issue. :laugh:

I'm going to keep the zip file for 178 on my phone and if I get another reboot tonight/tomorrow I'll flash it and see how it holds up.
[Nexus 4 Original Android Development] Testraindrop:
Yes.

You know that fsync only is effecting anything when there is a system crash/reboot, that you then might lose data?

During normal use it shouldn't affect stability.
[Nexus 4 Original Android Development] jawz101:
yes I know. says it right there in the setting in fact. I'm going to see if it's something else. I normally do a few things in cm performance settings and fku and I'm consistent in what I change so I might be able to reproduce it.
[Nexus 4 Original Android Development] franciscofranco:
Yes. Haptic Feedback is 100 as it ever was though.
[Nexus 4 Original Android Development] jak3z:
Don't know what I'm going to do with my Nexus 7 2013 and without franco kernel :confused: Getting my LTE version on September 2th :)
[Nexus 4 Original Android Development] Lownita:
Flashed r178 jss on a cm kang and fku is showing 70%, but not a big deal :)

Tapatalked from my Nexus 4
[Nexus 4 Original Android Development] franciscofranco:
Ok time for some experiments!

While I was with my GF I took some light readings and in one of those readings I read what Anandtech's mister Brian had to say about the new Nexus 7 and how the frequencies scale up and down during load comparing with the SGS4 which has basically the same CPU and I found it pretty cool: http://www.anandtech.com/show/7231/the-nexus-7-2013-review/3

So I investigated and that is mostly due to 3 things that aren't set by default on Mako:

* CPU core boost on thread migration. Basically if there is a thread running on cpu0 with 1.5GHz that migrates to cpu1, cpu1 will be boosted instantly to 1,5GHz (while cpu0 is scaling normally depending on load). This is helpful during touch inputs because threads can migrate and we want the destination cpu core that receives the thread to run at the same CPU frequency that the original core where the thread running was set to. Flo (the new N7) has this feature enabled by default, while Mako doesn't;

* Optimal Freq tunable on Ondemand is set to 918MHz on Flo and is not set on Mako

* Sync Freq tunable on Ondemand is set to 1026MHz on Flo and isn't set on Mako

These two last tunables work similar to hispeed_freq on Interactive and ensures that the cores run at specific frequencies if the load justifies that. These load thresholds are set with up_threshold_multi_core and up_threshold_any_cpu_load and both are not set on Mako AFAIK, but are set on Flo.

As you can imagine by now for all of this to work we have to be using Ondemand governor. During my tests I can confidently say that the Governor maintains its high frequencies during high load times, like Games or other heavy ****, which is pretty cool and sometimes it does not happen with Interactive unless heavily tuned like I did, and its still not perfect.

This two commits on Flo also help to improve performance of Ondemand (I merged these two as well):

https://github.com/franciscofranco/mako/commit/96ce97c67b8f972ac60750475f10e9a4a8c6979b

https://github.com/franciscofranco/mako/commit/d15dd85b08c58dc41b5abec12d31af275531f9f5

So I want you guys to run some tests and let me know how this works out. I left Interactive enabled in the Kernel for you to compare both governors freely. I attached two zips below, one for JWR and the other for JSS. All the commits have been pushed to my git so you can take a look if you want.

With all of this I'm not saying Ondemand is better than Interactive or vice-versa, this is just a test and I need more than my own opinion to go forward.

Happy testings :)
[Nexus 4 Original Android Development] zephiK:
Pretty interesting reads that you compared other devices with our CPU and brought it over to the mako. Not many kernel developers do that, especially when it comes to breaking it down for us. Another reason why FK is so good and is always developing & thinking outside of the box.

Makes a lot of sense, super excited to actually experiment with this build.
[Nexus 4 Original Android Development] muzadull:
Do you think OTG will work if we use Nexus 7(2013) drivers as they seem to be using the same Analogix ANX7808 slimport?
[Nexus 4 Original Android Development] franciscofranco:
If the board and the regulator output enough energy for OTG then Google enabled it by default, if not then its a no go without hacks, and I'm not one for hacks that may or may not work. I haven't even downloaded Flo's Kernel sources so I don't know and won't know until I have a N7 with me.
[Nexus 4 Original Android Development] Floydfire:
JSS is only 4byte? Maybe a bad upload, BTW I'm on jwr I will test for you Mr Francisco :)

Inviato dal mio Nexus 4
[Nexus 4 Original Android Development] jak3z:
Flashing experimental kernels makes me feel like a boy with new shoes :victory:
[Nexus 4 Original Android Development] zephiK:
Its a bad download on your part, flashed JSS just fine.

5.33 MB for JSS, 5.31MB for JWR
[Nexus 4 Original Android Development] Floydfire:
No only reading through tapatalk, maybe is a tapa deep :)

Now it say 5.3 MB :P

Inviato dal mio Nexus 4
[Nexus 4 Original Android Development] markd0wn:
Franco, in this latest test, besides the commits you mentioned, did you also do the re-base on r176/add sound control fix like you planned?
[Nexus 4 Original Android Development] vjales:
Can this be comparable to what Apple did to the Mac OS X Mavericks which they named "Timer Coalescing"? Thanks!
[Nexus 4 Original Android Development] droidwrx:
Initial reaction is that the test kernel is fast as hell. We'll see about the battery, but so far it is very impressive.
[Nexus 4 Original Android Development] albundy2010:
Anand did that review of the new 7 Franco. Brian did the initial mini review.

Also why kernel settings play a role I believe the main reason the s4 soc clocks go all over the place compared to the 7 is because of throttling.

Don't know how else to put it but IMHO 1.9 GHz is retarded.
[Nexus 4 Original Android Development] jak3z:
with r180 phone looks so responsive and fluid, I got the feeling battery wont be happy. :confused:
[Nexus 4 Original Android Development] stark_br:
Franco, found that if I set max freq below 1512, it gets stuck on max freq set.

Dont know if it should be this way.

See attach.

Tks

Edit: test kernel, of course.
[Nexus 4 Original Android Development] muzadull:
ok.I hope it works
[Nexus 4 Original Android Development] franciscofranco:
I did what was needed to be done, check git.

Nope, this is different.

Where are you getting that 1,9GHz from?

??
[Nexus 4 Original Android Development] albundy2010:
In the anand article comparing the behavior of the 1.5 GHz nexus 7 to the 1.9 GHz in the s4.
[Nexus 4 Original Android Development] stark_br:
I said that if max freq different from 1512 mhz, it gets stuck, just like the screenshot attached.
[Nexus 4 Original Android Development] franciscofranco:
Thats weird, must be something off with Ondemand code. Thanks.
[Nexus 4 Original Android Development] Redneck Trash:
Trickster can be goofy. Back all the way out of the app then launch again from the app drawer.
[Nexus 4 Original Android Development] stark_br:
Already rebooted my friend and stills the same.
[Nexus 4 Original Android Development] Floydfire:
Just tried to down clock to 1000 and my phone stick to this value if I under clock even when I'm not touching the phone go for the max CPU I have set if <= 1000mhz.. Just tried :) I'm using fk test untouched setting...

Inviato dal mio Nexus 4
[Nexus 4 Original Android Development] Redneck Trash:
I'm not having your issue.
[Nexus 4 Original Android Development] Floydfire:
Here my screen shot. I have also tried to set threshold to 100 didn't change behavior...

Inviato dal mio Nexus 4
[Nexus 4 Original Android Development] stark_br:
Did you set any value other than 1.5ghz?

Thats when it happens, see the post above yours...
[Nexus 4 Original Android Development] Floydfire:
This is when you set CPU >1000. I'm talking about new testing rom.

Inviato dal mio Nexus 4
[Nexus 4 Original Android Development] heirfister:
i'm using the default settings but i also get the same as above, cpu3 and 4 are offline.
[Nexus 4 Original Android Development] Floydfire:
For me happened only when underclocked to 1000 or lower..

Inviato dal mio Nexus 4
[Nexus 4 Original Android Development] heirfister:
i'm on default settings but still cpu 3 and 4 are offline.
[Nexus 4 Original Android Development] adrok76:
I'm no expert, but the touch response seems way better on the latest nightly.
[Nexus 4 Original Android Development] Floydfire:
Sorry I think I need to sleep I have misread your post like if you go under clock will be lock on 1500. Lookin to your screen it's like me, if you go under 1000 you get stuck on max freq you have set if <= 1000 sorry for my misreading I'm going to bed now, good night to all, fk test kernel is good if 1500 is your setting but I think tomorrow Franco will have already fixed... :)

Inviato dal mio Nexus 4
[Nexus 4 Original Android Development] franciscofranco:
Whats the problem? If you want all cores online all the time just change it the threshold to 0.
[Nexus 4 Original Android Development] heirfister:
it becomes a little laggy when i open many apps not like on 178, so i just thought that its the problem.
[Nexus 4 Original Android Development] Redneck Trash:
With max set to 1026 the CPU pegged at that speed with the screen on. With max set at 918 it occasionally dropped to the min but basically stayed at 918, again with the screen on. On screen off they both idled at min. Took the time to try each frequency at max and 1026 and 918 were the only ones with this issue. None of the other frequencies pegged at max.
[Nexus 4 Original Android Development] haxor:
WOW. Nexus 4 for 199 and 249 USD.

http://www.androidpolice.com/2013/08/27/breaking-nexus-4-price-drops-by-100-199-for-8gb-249-for-16gb/
[Nexus 4 Original Android Development] Redneck Trash:
If your phone is just sitting there at idle it's not hitting the threshold to bring the other cores online. I've been using the floating monitor and cores 2 and 3 do come online.
[Nexus 4 Original Android Development] mendozaram:
Hey... Which app is that bro?

Send from my Slimmed N4
[Nexus 4 Original Android Development] Redneck Trash:
System Monitor. I believe the version in fKu is slightly modified per Franco's request. The paid version from the Play Store has the floating widget among other options.
[Nexus 4 Original Android Development] klownk:
I recently updated to cm 10.2 without having any problem. After installing franco kernel #178 my phone took a very long time to boot and after that there were error messages: "NFC Service stopped" and "The process com.android.phone has stopped" and I couldn't get past them. I reflashed the CM .zip in recovery after that and everything went back to normal.

Any advice on this? I'd really like to continue to use franco kernel.
[Nexus 4 Original Android Development] mitchdickson:
Are you using the JSS build?
[Nexus 4 Original Android Development] klownk:
Yes I'm on JSS15Q. I tried to download the Kernel via franco.Kernel updater. So I guess the app just isn't able to choose the right build version yet.

When I'm installing the JSS version manuelly everything's fine.

Thanks for pointing me to the right way.
[Nexus 4 Original Android Development] zephiK:
Are you using the dalvik patches?

Yeah on the changelog it says if you're on JSS go to this link to download the JSS version :)
[Nexus 4 Original Android Development] maulich:
Sounds like data issue to me not kernel.....wipe data and reflash I bet it boots clean.
[Nexus 4 Original Android Development] svnhvn:
[MENTION=3292224]franciscofranco[/MENTION]: Just flashed your r180 and my first impression is: My "sometimes" stuttering is gone!!!

Now set it on ondemand and see how well it goes with the battery. Thanks a lot man.
[Nexus 4 Original Android Development] sordna:
I just flashed r180 as well, I extracted boot.img from the zip and flashed it with Universal Kernel Flasher app.

I noticed that it defaulted to ONDEMAND by itself from what I see in the Franco Updater app even though I had INTERACTIVE before.
[Nexus 4 Original Android Development] khanhtrinh:
Hmm...anyone?
[Nexus 4 Original Android Development] leets4uc3:
Did you not read the post that you downloaded the new kernel from?
[Nexus 4 Original Android Development] BlueHawk:
You don't describe what ROM base you are running JWR or JSS. JSS definitely has lag/scroll issues due to the deadlock problem.
[Nexus 4 Original Android Development] drawde40599:
Seen that, means Nexus 5 is coming! :D they did same with Gnex.
[Nexus 4 Original Android Development] Redneck Trash:
Duh. Of course there'll be a new Nexus phone in November.
[Nexus 4 Original Android Development] DaX05:
They better no disappoint us with the Nexus 5. :)
[Nexus 4 Original Android Development] The Unnamed Time Lord:
I am sorry to ask but is there progress with the issues regarding the Display Controls app in 4.3 roms?
[Nexus 4 Original Android Development] zephiK:
& announced in October. Hopefully this years' Nexus will launch more smoothly.
[Nexus 4 Original Android Development] Luigiesin:
Oh wow.. Now 180 uses ondemand? This is pretty cool.. I don't really see much difference in battery life... And it's definitely a bit smoother!

Sent from my \m/ Nexus 4

PA + Franco
[Nexus 4 Original Android Development] alanwyl:
My bet would be Franco putting the logic into interactive later.
[Nexus 4 Original Android Development] svnhvn:
Yes. So far ondemand quite friendly with my battery.

N5? F**k, just got my N4 3 months ago.
[Nexus 4 Original Android Development] franciscofranco:
Yes, should launch tomorrow, finally have free time, my GF has gone away for a few days with her family :D
[Nexus 4 Original Android Development] drawde40599:
If u mean on build 178 then its the kernel alot of us not all are having what u described, install 176 or new try test build , issue gone ;)
[Nexus 4 Original Android Development] Luigiesin:
Franco, do you plan on using the same concept with interactive? Or you're going to focus on ondemand now?

Sent from my \m/ Nexus 4

PA + Franco
[Nexus 4 Original Android Development] franciscofranco:
Not sure the functionalities are usable on interactive, but I'll look.
[Nexus 4 Original Android Development] Luigiesin:
Franco... Where can I find a changelog for 180?

Sent from my \m/ Nexus 4

PA + Franco

---------- Post added at 11:33 PM ---------- Previous post was at 11:28 PM ----------

Sent from my \m/ Nexus 4

PA + Franco

---------- Post added at 11:34 PM ---------- Previous post was at 11:33 PM ----------

Sent from my \m/ Nexus 4

PA + Franco

---------- Post added at 11:36 PM ---------- Previous post was at 11:34 PM ----------

Sent from my \m/ Nexus 4

PA + Franco

---------- Post added at 11:37 PM ---------- Previous post was at 11:36 PM ----------

Sent from my \m/ Nexus 4

PA + Franco

---------- Post added at 11:37 PM ---------- Previous post was at 11:37 PM ----------

Sent from my \m/ Nexus 4

PA + Franco

---------- Post added at 11:39 PM ---------- Previous post was at 11:37 PM ----------

Sent from my \m/ Nexus 4

PA + Franco
[Nexus 4 Original Android Development] mr xombie:
septuple kill !!!
[Nexus 4 Original Android Development] Redneck Trash:
On the test build as far as a good mix of performance and battery I'm getting good results with CFQ set as I/O.
[Nexus 4 Original Android Development] Luigiesin:
Haha sorry... Freaking Tapatalk

Sent from my \m/ Nexus 4

PA + Franco
[Nexus 4 Original Android Development] khanhtrinh:
I'm on Cataclysm franco r178, which bases on JWR build. And I need some app which people widely agree on it's scrolling smoothness to test. Is there any?
[Nexus 4 Original Android Development] Manbot27:
Speed is really good and fluid on the r180 test kernel. Unlike the usual sucking up posts I have to say that this is actually a definitely noticeable improvement in speed. I'll gauge the battery life as I go through my normal day.
[Nexus 4 Original Android Development] Arstoien:
Just flashed the latest build with Ondemand and what worries me battery wise is that it stays on high frequencies even when not interacting with the screen. On the homescreen goes down to 384, then up again, then down, etc. When in some apps it usually stays on 1GHz and higher. Interactive currently scales very intelligently.

As for smoothness, they seem equally smooth to me. Can't see a noticeable difference as of yet. What I've noticed is that a screen touch doesn't necessarily keep the frequencies at 1.5, but usually stays at either 1.5 or 1GHz (which it does most the time when I'm not touching it anyway).

Sent from my Nexus 4
[Nexus 4 Original Android Development] Luigiesin:
Yup... Same here... But I don't see a considerable hit on battery.

For some reason I feel it more efficient than interactive in this build.. That's why I asked if this build is based on 176 for interactive.

Sent from my \m/ Nexus 4

PA + Franco
[Nexus 4 Original Android Development] slybunda:
nexus 4 battery life is fairly poor as stock, does this kernel make much of a difference?
[Nexus 4 Original Android Development] arlenwoot:
Definitely. There's considerable amount of battery life improvement using this kernel.
[Nexus 4 Original Android Development] slybunda:
how much would you say is considerable improvement? how much screen on time can be obtained?

im thinking of getting this phone now that its gone really cheap since the price drop.

im worried about having a phone with a non removable battery, since the battery seems to die in the long run rendering the phone useless into the future.

or is battery easily obtainable and replaceable for a nexus 4?
[Nexus 4 Original Android Development] jak3z:
If you are in 4.2 yes, if you are in 4.3, a bit.
[Nexus 4 Original Android Development] mohammad2010:
battery life in r178 is bad :(

r176 was better
[Nexus 4 Original Android Development] slybunda:
did 4.3 stock give battery life increase over 4.2 stock?

wondering if i should get the phone, lack of memory card and removeable battery are my main concerns. although i can probably live without the memory card but removeable battery is an issue seeing as how my last iphone died of poor battery life issues and apple wanted £65 for new battery replacement. and everywhere i look its just fake batteries on sale.
[Nexus 4 Original Android Development] Pure Drive GT:
This is with r178. This is the first time i got such good battery life. I play lots of games but don't use 3g

On stock i usually got 4 with like 60min gaming (muffin knight/tapped out/minion rush)
[Nexus 4 Original Android Development] slybunda:
seems acceptable to me although my current galaxy s1 gets over 6 hours screen on time all the time so dunno how to proceed on this one.
[Nexus 4 Original Android Development] zephiK:
Try it for yourself.......? It is free after all. What do you have to lose?
[Nexus 4 Original Android Development] jak3z:
Does your Galaxy s1 have as many power as your Nexus 4?

Try turning down the speed of your cores to 1000 Mhz, you will have a quad core 1Ghz compared yo your 1Ghz single core, and you will get more battery.

More processing power, more battery. Apples to apples dude.
[Nexus 4 Original Android Development] swiftyy:
I tried r178 and battery life and smoothness is better on the r176. Therefore I reverted back to r176.
[Nexus 4 Original Android Development] arlenwoot:
Except he doesn't own the n4 yet.
[Nexus 4 Original Android Development] svnhvn:
For all you guys information, 'till right now my battery still rockin' on at 61%. So i guess ondemand in this build on par with interactive in term of battery consumption.
[Nexus 4 Original Android Development] alanwyl:
Ctrl f in that post for my username

It was me who posted the link to the LG site and posted a pic of the label on the box several days ago. Likely in page 2:)

Edit: just gone back and found my s/n, it starts with 212KPF.

It's rev_11 BTW.
[Nexus 4 Original Android Development] Vangelis13:
Well, what kind of an answer would you expect to receive now..? Here's the mildest sort: yes, it is leading to a stable version.

Happy? :thumbup:
[Nexus 4 Original Android Development] ben_pyett:
NO his plan is to un-stabilize the kernel as much as possible and then UV to obscenity!:p

You are far too considerate!
[Nexus 4 Original Android Development] noneabove:
Just had my first ever reboot on franco ! (and been running it for weeks!!) :(

Attaching last_kmsg, very odd! Hope it helps! running r23 on AOKP screen was off at the time connected to wifi with no foreground applications

min 384 max 1350

all governor controls set to defaults that come with

if attaching it as a txt is wrong let me know i'll upload to dropbox
[Nexus 4 Original Android Development] leets4uc3:
R26 its great so far. Data is working just fine.

What TCP congestion is everyone using?
[Nexus 4 Original Android Development] Boergen:
Seems that with r26 60/918 is the new default in interactive?
[Nexus 4 Original Android Development] Ibsonic:
Holy, triple orgasms here.. Franco my man ! You're great !! 2013 is our year :D

Verstuurd van mijn Nexus 4 met Tapatalk
[Nexus 4 Original Android Development] samwebbo1990:
What colour settings are people using? :)
[Nexus 4 Original Android Development] Ibsonic:
Franco,

could enable_all_load_threshold = 600 cause a little bit lag?

ah wait ! hispeed_freq is 918 now, setting it back to 1026 :D
[Nexus 4 Original Android Development] siscim23:
Search 'color' in this thread, there are a few posts with color settings. I have 223, 204, 195. Saw these settings in here where someone calibrated with something and a bunch of people agreed so I'm using those.
[Nexus 4 Original Android Development] calanizzle:
255 246 246 atm
[Nexus 4 Original Android Development] Godaemon:
35 minutes unplugged ...

At these wakelocks normal?
[Nexus 4 Original Android Development] CMNein:
SNS = texting or social thing? Aside from those wakelocks (SNS_.....) nothing out of the ordinary.
[Nexus 4 Original Android Development] calanizzle:
Seems fine
[Nexus 4 Original Android Development] capcanuck:
26 running beautifully so far, data is golden, super buttery.. Kernel porn is the best way for me to describe it right now... Gracias Franco.. Muy Bien..
[Nexus 4 Original Android Development] pa.pn2:
play a bit

https://docs.google.com/spreadsheet/ccc?key=0AoDp2qRui0u0dGE4T2gtSDBTRHVFSldPS2RrX1Rya0E#gid=0