yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] zephiK:
Whats useless to you is not useless for all.

(No I don't use TC..... just speaking on other peoples' behalf because I have perspective)
[Nexus 4 Original Android Development] TheQuarterMile:
Sorry if this question was asked before but I want to know if USB OTG hack is enabled in the 4.3 kernel?
[Nexus 4 Original Android Development] zephiK:
Not that I know of.
[Nexus 4 Original Android Development] :
I think I read somewhere in this thread that JSS contains fixes/upgrades that are intended mainly for the N7 and not the N4, so Google will probably not release it as stock for the N4. I might be wrong, though.
[Nexus 4 Original Android Development] i860:
Hi

I one of those people how use TC and for me is important. I use N4 to listen music on my car over BT, the holder is far so i to stretch to reach the button to turn the screen on. Swiping is essayer and safer to operate my phone in my case. So please consider supporting TC.
[Nexus 4 Original Android Development] pawan1993:
That's what JBQ thought! But it had quite a few fixes and upgrades for mako too so he just built JWR for mako and put that up without realising JSS had fixes too for mako.
[Nexus 4 Original Android Development] rest0ck:
Will version 174 work with the latest PA? Because the title says JWR and not JSS..?

Thanks in advance

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] elite_gamer04:
People need to start bloody reading....

NOOOOOOOOOOOOOOOOOOOOOO
[Nexus 4 Original Android Development] Arstoien:
Not to play the devil's advocate but the OP's FAQ needs a slight modification.

"2. This kernel works on Y or X rom?

A: This is one of the worse questions you can ask on my threads. This is a Nexus, it works on every rom you can possibly imagine." – that surely is confusing for anyone showing up here for the first time and checking the OP.

It'd be good to add a note for the JWR and JSS and then simply answer with "refer to OP" to every question about that.

PS: Not defending the people who don't like the search function. Just thinking that would lower the amount of unneeded questions and frustration in the answers.
[Nexus 4 Original Android Development] alanwyl:
For people on PA, Franco has already released his enhanced stock for 3 devices already from the very short pause here, next one to release might be mako. Do please give him a break.
[Nexus 4 Original Android Development] aventu:
[MENTION=3292224]franciscofranco[/MENTION]

I have a few suggestions for the interactive governor:

diff --git a/drivers/cpufreq/cpufreq_interactive.c b/drivers/cpufreq/cpufreq_interactive.c
index 2521d31..3d88c98 100644
--- a/drivers/cpufreq/cpufreq_interactive.c
+++ b/drivers/cpufreq/cpufreq_interactive.c
@@ -68,7 +68,7 @@ static spinlock_t down_cpumask_lock;
static struct mutex set_speed_lock;

/* Hi speed to bump to from lo speed when load burst (default max) */
-#define DEFAULT_HISPEED_FREQ 1026000
+#define DEFAULT_HISPEED_FREQ 702000
static u64 hispeed_freq;

/* Bump the CPU to hispeed_freq if its load is >= 50% */
@@ -101,7 +101,7 @@ static unsigned long above_hispeed_delay_val;
* The CPU will be boosted to this frequency when the screen is
* touched. input_boost needs to be enabled.
*/
-#define DEFAULT_INPUT_BOOST_FREQ 1512000
+#define DEFAULT_INPUT_BOOST_FREQ 702000
static int input_boost_freq;

/*
@@ -242,11 +242,13 @@ static void cpufreq_interactive_timer(unsigned long data)
if (load_since_change > cpu_load)
cpu_load = load_since_change;

+ if (is_touching && pcpu->policy->cpu < 2)
+ up_threshold = HISPEED_FREQ_LOAD;
+ else
+ up_threshold = DEFAULT_UP_THRESHOLD;
+
if (cpu_load >= up_threshold)
new_freq = pcpu->policy->max;
- /* if the cpu load is >= 50% lets bump the cpu to hispeed_freq */
- else if (cpu_load >= HISPEED_FREQ_LOAD)
- new_freq = hispeed_freq;
/* Lets divide by up_threshold so that the device uses more freqs */
else
new_freq = pcpu->policy->max * cpu_load / up_threshold;
@@ -275,6 +277,10 @@ static void cpufreq_interactive_timer(unsigned long data)
else if (new_freq < input_boost_freq || pcpu->policy->cur < input_boost_freq)
new_freq = input_boost_freq;
}
+
+ /* if the cpu load is >= 50% lets bump the cpu to hispeed_freq */
+ if (cpu_load >= HISPEED_FREQ_LOAD [COLOR="Red"]&& new_freq < hispeed_freq[/COLOR])
+ new_freq = hispeed_freq;

Instead of using max freq for 1 sec I would use a solid freq like 702MHz and a very agressive up_threshold like HISPEED_FREQ_LOAD. So you get 702MHz for things which absolutely don't need performance but also very high frequencies when the load reaches 50%.

And maybe there was a bug in the code:

If the load is 70% and the current freq 1512 * (70 / 85) = 1245 the new_freq will be DEFAULT_HISPEED_FREQ, so less than actually calculated.
[Nexus 4 Original Android Development] Bobtehblob:
And on an off topic but related posts JBQ has left AOSP over issues with the 2013 Nexus 7 and the release of factory images. This is bad news :/
[Nexus 4 Original Android Development] blueren:
So, N7-2013 isn't going to be supported by CM? Or other custom roms? Planned on picking up one.
[Nexus 4 Original Android Development] bokagavrilov:
It was like that for the n4 too Qualcomm its messing things up we had to wait but at the end we got them so there's still hope..
[Nexus 4 Original Android Development] Haomuch:
That's a great news. Could you provide us a ini file with the ARP offloading active?
[Nexus 4 Original Android Development] franciscofranco:
A small request for everyone - lets try and be friendly with everyone. I'd rather see posts get ignored rather than giving unfriendly replies. I'm just ignoring what I don't want to answer ;)

Finally Kernel code discussion!!

Interesting approach but I'm not sure that is going to cut it. Unfortunately Android has turned itself into a bit of a power hog - needing to be on max frequency for UI interactions to be smooth is really bad. Relying on cpu_load to be 50% during UI interactions to be bumped to max is a freeway to lag because when we are interacting with the device the cpu load is not 50%, unless we start opening apps and multi tasking. Swiping around as far as I know won't get you above 50% and then you'll be stuck to, in the case of your example, 702MHz.. I'd rather see it on max for 1 second and not see it struggle and have all the fancy animations and **** being taken care of as fast as possible than see it struggle and relying on the cpu_load calculation. But I'm willing to hear some numbers from you with raw data that back your idea :)

About the second part, the cpufreq function call will choose the highest frequency close to the new_freq, if its on the cpu table or not:

__cpufreq_driver_target(pcpu->policy,

max_freq,

CPUFREQ_RELATION_H);

Swapping CPUFREQ_RELATION_H with CPUFREQ_RELATION_L would be the opposite and it would choose a the lowest frequency closer to new_freq. That code part is in the cpufreq_interactive_up_task function.
[Nexus 4 Original Android Development] pawan1993:
Oh no! He was one of the more involved members of AOSP and really filled in the development community with development in AOSP. They will find someone to fill his place but JBQ didn't deserve the crap he got and there really could have been a quick OTA update to fix his mistake. Awesome dev but back on topic!

Franco are you going to consider enabling ARP offloading? Or is that to do with a system file rather than the kernel.
[Nexus 4 Original Android Development] jak3z:
ARP Offloading is turned on/off on a system file, and with root it's accessible to everyone, just needs to change a value so hardly got anything to do with a kernel.
[Nexus 4 Original Android Development] nachordez:
System file.

There's even a flashable zip in a thread (sorry, don't remember which one) for more easy editing.

Nexus4 / Cataclysm / Franco

Nexus4 / Cataclysm / Franco
[Nexus 4 Original Android Development] franciscofranco:
Nope, ARP offloading will stay as Google leaves it, either on or off, its their call.
[Nexus 4 Original Android Development] aventu:
Yes, it really makes a difference. But I use my device a lot when I'm bored, so I want a good compromise between smoothness and on screen time.

Yes. 1245 would be 1350 with CPUFREQ_RELATION_H. But I'm not sure if HISPEED_FREQ_LOAD works correctly.

if (cpu_load >= up_threshold)
new_freq = pcpu->policy->max;
/* if the cpu load is >= 50% lets bump the cpu to hispeed_freq */
[COLOR="Red"]else if (cpu_load >= HISPEED_FREQ_LOAD[/COLOR])
new_freq = hispeed_freq;
/* Lets divide by up_threshold so that the device uses more freqs */
else
new_freq = pcpu->policy->max * cpu_load / up_threshold;[COLOR="Red"]//this code will be ignored with 50 < cpu_load < 85[/COLOR]

If we have 50% load, the governor would calculate 1512 * (50 / 85) = 889 -> 918MHz, but it will be set to 1GHz default. That's a bit more.

But if get 70% load, it should be 1512 * (70 / 85) = 1245 -> 1350, but it will be set to 1GHz again. Less than it should be.
[Nexus 4 Original Android Development] franciscofranco:
Ok thanks, I will experiment with that.
[Nexus 4 Original Android Development] franciscofranco:
Try this:

new_freq = pcpu->policy->max * cpu_load / up_threshold;

if (cpu_load >= up_threshold)
new_freq = pcpu->policy->max;
/* if the cpu load is >= 50% lets bump the cpu to hispeed_freq */
else if (cpu_load >= HISPEED_FREQ_LOAD && new_freq < hispeed_freq)
new_freq = hispeed_freq;

I haven't tested it (not on my Android environment OS at the moment) but I think this will work fine. We calculate the new_freq regardless, if the load is higher than up_threshold bump to max. If the load is higher than HISPEED_FREQ_LOAD but new_freq is for some odd reason is lower than hispeed_freq then we set to hispeed_freq. Does that make sense to you?

EDIT: Fúck it, gotta reboot to Linux and test :)
[Nexus 4 Original Android Development] steviewevie:
Did you see my kernel panic posting [MENTION=3292224]franciscofranco[/MENTION]? http://xdaforums.com/showthread.php?p=44407072

Sorry if this seems rude or like I am hassling for an instant fix, but I wanted to make sure it wasn't lost in all the other chat.

Sent from my Nexus 4
[Nexus 4 Original Android Development] thebryceee:
Isn't it off on JW but on on JS? Both google builds. Unless you're talking about OTA and AOSP.
[Nexus 4 Original Android Development] franciscofranco:
Someone asked me to share the aosp build I'm using to test JSS, here it is: http://franciscofranco.minooch.com/Nexus4/4.3/aosp/

fastboot flash system system.img

fastboot flash userdata userdata.img

fastboot flash boot boot.img

Has no su, you gotta flash supersu.zip or something. For gapps you can just flash the package PA shares with the google apps. Has nothing other than pure AOSP, black BG instead of gradient and removed dumb packages so its pretty lean. Rest is AOSP, no other changes.

There is no support for this, just flash if you know what you're doing. If you break something else, I won't give a single fúck.
[Nexus 4 Original Android Development] JamesInsights:
Awesome. Note taken haha
[Nexus 4 Original Android Development] pawan1993:
Oh alright. From what the others are saying it should be easy enough to change :)
[Nexus 4 Original Android Development] franciscofranco:
Its very easy ;)
[Nexus 4 Original Android Development] markd0wn:
Thanks for sharing!

For others I'd also recommend possibly trying BaNkS gapps instead (this is not an official franco recommendation obviously) since it only includes the core essential Google stuff (store, sync services, etc) and is only 17mb (instead of like 190) as a result.

Most people won't need all the Google apps preinstalled (Maps, Earth, Keep, and so on), and other than the core package, those are all installable via the store optionally for those who want it.
[Nexus 4 Original Android Development] rascarlo:
eheh
[Nexus 4 Original Android Development] Pure Drive GT:
Pure AOSP Rom

[MENTION=3292224]franciscofranco[/MENTION] thx a lot for sharing your build really appreciate it :) just wanted to ask what kind of kernel that boot.img is i'm strongly assuming stock jss15.. but just wanted to be sure xD
[Nexus 4 Original Android Development] franciscofranco:
r175 JSS.
[Nexus 4 Original Android Development] Pure Drive GT:
wooooooooooooooooooooohoooooooooooooooooo

you the boss! loving the CORRECT boot animation :D
[Nexus 4 Original Android Development] rmead01:
won't flashing the userdata erase internal memory? just in case some people dont realize this. I could be wrong but I remember skipping that step when flashing the 4.3 images because I wanted to keep my sdcard.

and +1 for the secret r175. I prefer official franco, public release or not
[Nexus 4 Original Android Development] philipepi:
Sorry for asking this here, i dont know what else to try..

im with jwr and jss build, both have wifi issue ( delay notification after lockscreen ).. ive tested with every kernel and nothing, ive downgraded to 4.2.2 and updated via OTA and nothing

does with franco kernel can fix this? I mean, is he related with drivers? qcom .ini ? it will fix that issue about delay notification?

what should i do? help :(
[Nexus 4 Original Android Development] thesebastian:
Sorry for the questions i tried to search them but couldn't find a good answer....

Is there any risks or disadvantage using USB Fast charge? (Why it's disabled by default on all Nexus?).

You could try disabling "Wi-Fi Optimization" (Note: I tried this settings this week and think this settings almost disables "Deep Sleep"...).
[Nexus 4 Original Android Development] rmead01:
was hoping this would boot on PA 3.95 but no such luck :(
[Nexus 4 Original Android Development] zephiK:
Same, boot animation doesn't load and is stuck on starting up.
[Nexus 4 Original Android Development] mitchdickson:
Sure you guys made a nandroid first, right?

Sent from my iPad Mini
[Nexus 4 Original Android Development] rmead01:
nope. Just reflashed PA and everything is normal.
[Nexus 4 Original Android Development] zephiK:
No, why would I make a nandroid? I'll just fastboot (or go into recovery mode) and flash the previous kernel.
[Nexus 4 Original Android Development] thesebastian:
Don't forget to re-flash the ROM. Just in case Franco still has a different ramdisk.
[Nexus 4 Original Android Development] rmead01:
tried that. reflashed the rom, gapps, went right into bootloader, flashed boot.img and nada.

Just so franco is aware, i'm not complaining. just trying to save others some time if they were also going to try.
[Nexus 4 Original Android Development] asm19:
Yes, confirm. Not working in all JSS. I tried CM 10.2 and stay bootloop.

Sent from my Nexus 4
[Nexus 4 Original Android Development] franciscofranco:
I never said it would boot on PA.
[Nexus 4 Original Android Development] davidbar93:
CPU TYPE: SLOW. What does it means?

JWR66V with r174
[Nexus 4 Original Android Development] rmead01:
No problem. I was just hoping it would since it's a JSS build. I would never ask a dev for something they aren't ready for. I just wanted to post the info in case other people had the same thought and my comment could save them some time.
[Nexus 4 Original Android Development] franciscofranco:
Yes. I will release something compatible with PA sometime, they use a different ramdisk.
[Nexus 4 Original Android Development] franciscofranco:
Means its slower than a turtle.
[Nexus 4 Original Android Development] StephenSpig:
It's NOT working with CyanogenMod 10.2?!
[Nexus 4 Original Android Development] zephiK:
Was able to flash that and r175 works :D

http://xdaforums.com/showpost.php?p=44425730&postcount=182

The boot.img Franco posted in /aosp/ doesn't work due to something with ramdisks. But the flashable zip posted above should work for any jss15j roms.

proof:

http://i.imgur.com/o0irL2V.png
[Nexus 4 Original Android Development] Bill Gamble:
Perhaps, but that same CPU may have binned as "Nominal" under 4.2.2
[Nexus 4 Original Android Development] zephiK:
Its probably calculating it wrong in the app as I remembered reading another person who had the same problem as you that reported it lower than expected. You can check using terminal emulator for prep CVS (something similar to do that.. do a google search for the proper command)
[Nexus 4 Original Android Development] Bill Gamble:
If you mean

dmesg | grep PVS

that returns the same thing, iow, what was considered "Nominal" under 4.2.2 is seen as "Slow" under 4.3.
[Nexus 4 Original Android Development] zephiK:
Very odd. Maybe make a nandroid backup and flash 4.2.2 for the giggles and run grep PVS again to see if it appears as slow or nominal.

At the end of the day, it shouldn't make much of a difference imo. Maybe it'll affect your ability to undervolt.
[Nexus 4 Original Android Development] Bill Gamble:
No, the update didn't change the binning, it changed the method by which it's calculated and the descriptions that are assigned. There's now a "Fastest" label, for example, that often gets returned for CPUs that were labeled "Faster" under 4.2.2. The new process also assigns "Slow" to many CPUs labeled "Nominal" previously (like mine). The CPU voltages didn't change: 900 mV is still assigned to 384 MHz.
[Nexus 4 Original Android Development] asm19:
I tried and it doesn't working, is stay in bootloop ... Using version unoffial.

Sent from my Nexus 4
[Nexus 4 Original Android Development] zephiK:
Works fine with me on unofficial.

My fast is still fast after update. Did you update bootloader?

I think a lot of people are just assuming that it would work as its a AOSP JSS15J build.
[Nexus 4 Original Android Development] franciscofranco:
I didnt say it boots in any rom besides the AOSP I posted.
[Nexus 4 Original Android Development] KSLevel11:
Hello Nexus 4 Community.

I would like to buy Nexus 4 in near future. But I read really a lot of information about thermal throotling in this phone. Some people say that installing custom kernel like the one from this thread solves the problem.

Could someone tell me how it looks in practice?

Thanks in advance.

Greetings.

Wysłane z mojego GT-I9000 za pomocą Tapatalk 4
[Nexus 4 Original Android Development] Pure Drive GT:
Pure AOSP Rom Compiled by Franco himself

Well as you might have read i flashed franco's AOSP Build and am very happy with it. In case you want to flash it there are a few things you should know:

1. You won't have the (layout) of 4.3 camera nor photosphere, cause not opensource (photosphere at least), however you could just intall the apk :)

2. I don't know if derpe's on me but for me the AOSP(Google) Keyboard simply did not work, but I don't care cause I use Swiftkey.

3. I installed a very light gapps package which kind of had an old google now apk, these outdated version tend to crash, simply update it and it will be fine.

4. It does not come pre-rooted all you got to do is flash supersu from chainfor (example) and root works just fine now :)

5. It's absolutely awesome and has no bull**** in it whatsoever and that's exactly what i was looking for, completely clean slate.

And incase you still run into some trouble please don't immediatley ask for help and blame "bad rom" as franco is purely sharing this with us out of good will and we should be nothing but thankful.

BTW: [MENTION=3292224]franciscofranco[/MENTION] are you using a 8GB Nexus 4 ? cause i think this rom thinks my phone is a 8GB version :)
[Nexus 4 Original Android Development] Testraindrop:
Franco do you know how the XDA devDB stuff works? DO you have to apply for it?

Would be nice to have your Kernel also there :D
[Nexus 4 Original Android Development] Pure Drive GT:
Well On Stock OS thermalthrottling also is done when the battery gets hot, not sure but i think 40C° was the threshold for it (correct me). This however is pretty dumb for good user exprience, it's only good to keep your battery pseudo healthy. Franco's implemantation however only observes the CPU temp and throttles it at a level you yourself can set (usually 60-70 °C) So you won't be loosing performance for stupid battery reasons at times :)
[Nexus 4 Original Android Development] gianton:
r174 running great on Stock 4.3 ROM.

Thanks
[Nexus 4 Original Android Development] jmartino5920:
Thanks for the breakdown. Was debating whether or not to take the time to flash it. :)

As far as your device thinking it only has 8GBs...when I flashed the stock images from Google, my device thought it was an 8GB too. Did some digging and found a fix, but it requires you to flash stock recovery to fix it.

Once stock recovery is flashed, boot into it. When you see Andy on his back with a red exclamation point, press the power and volume up buttons at the same time. This may take a couple tries but eventually, when it works, you'll get a basic Android recovery menu. Do a factory reset, then wipe cache. This will solve the problem.

It is best to do this after booting into the ROM (to see what the device things the storage size is) but before installing anything, for obvious reasons.

Not sure why this bug exists, but it does.

Hope that helps.

jmar

LTE Mako
[Nexus 4 Original Android Development] nithin1992:
Boot to recovery and try a factory reset and it should show 16gb again
[Nexus 4 Original Android Development] Bill Gamble:
Yes. If your Nexus was "Fast" under 4.2.2, it seems to still be defined as that under 4.3. The changes I've been seeing are "Nominal" to "Slow" and "Faster" to "Fastest".
[Nexus 4 Original Android Development] Testraindrop:
One should note that this actually changes nothing regarding the speed of the device... just saying...
[Nexus 4 Original Android Development] Bill Gamble:
Yes, as I said, nothing has changed except the labels. The voltages assigned to the CPU speeds have remained the same for my device.
[Nexus 4 Original Android Development] gpvecchi:
Guys, I have to insist: with 173> kernel, my phone doesn't charge @ more that 50% when off. No issues if phone is on.

No problems nor with stock kernel, nor with Semaphore...
[Nexus 4 Original Android Development] franciscofranco:
1 - True.

2 - AOSP Keyboard has a bug I believe all roms compiled from JSS15J have that 2s freezing problem, nothing I can do about it, I have no idea what it is. I think PA fixed it partially, I'll take a look.

4 - True that too.

5 - Yep, has no bull****, just works.

I'll add it as soon as possible.

Coincidence.
[Nexus 4 Original Android Development] gpvecchi:
Sorry Franco, but no. Full wipe and clean install. When phone is off it reaches about half battery overnight. If then I turn screen on, animations shows battery charging, and not full charged one. I don't know what's next, I had to unplug it. Same charger, same wall plug, same cable.
[Nexus 4 Original Android Development] ziddey:
Kernel is irrelevant when phone is off.
[Nexus 4 Original Android Development] Cuzz1369:
[MENTION=3292224]franciscofranco[/MENTION] any plans for FLO kernel eventually? Have you even picked one up yet? Sorry if this has been asked.
[Nexus 4 Original Android Development] steviewevie:
When you flash the stock ROM, does the problem go away, and then it comes back again when you re-flash Franco?

Sent from my Nexus 4
[Nexus 4 Original Android Development] zevim2005:
same thing for me!
[Nexus 4 Original Android Development] franciscofranco:
Unfortunately for you both other than fast charge (which is disabled) there is 0 changes on the battery/charger drivers. Where is the kernel log?
[Nexus 4 Original Android Development] drawde40599:
What rom r u on? Because Looking at your signature your using wrong rom?
[Nexus 4 Original Android Development] Laurentwb:
Could someone provide a link to this apk because I could'nt find it ?

Thanks.

Nevermind. I got it : http://www.mediafire.com/download/k3i4qza1cm4pcnv/Googleeditioncamera.apk
[Nexus 4 Original Android Development] bombadier:
I am on 174 with Cataclysm which is JWR66V based,the quicktile toggle doesn't work,I have to enable fast charge via the app,the developer was asking if the sysfs path had changed,has it and to what,

Is fast charge working (Changelog says yes)

Thanks in advance
[Nexus 4 Original Android Development] TToivanen:
The tile works for me on Cataclysm. You must not be plugged in when you toggle it.