yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] Steven08:
heat

i have M2 installed.i noticed that my phone gets very qucik to 115-120 degrees.while holding the phone,it feels hot.i also undervolted -100.i have searched the forum,but found nothing.should i be concerned about this?
[Nexus 4 Original Android Development] tlf55:
Does changing I/O Scheduler in the app change the value directly or i have to reboot the phone ?
[Nexus 4 Original Android Development] fozzie:
Directly.
[Nexus 4 Original Android Development] ManOnTheMoon:
I keep getting random reboots. Here's the dmesg. I hoe it helps.

http://pastebin.com/CeEr9SRw
[Nexus 4 Original Android Development] Josuhu:
I have been very happy with Franco, but do you guys get a black screen when someone is calling you ? And then you have to push the power button before the screen wakes up and then you can answer ?

Btw: Franko M2 and latest PA rom
[Nexus 4 Original Android Development] ankn:
R134 - Battery hanged :)

I'm using since yesterday R134: since about 8-9 hours ago my battery discharged by just 2-3%. I switched on the screen just 4-5 times. Just unbealiveable... Thanks.
[Nexus 4 Original Android Development] Underground_XI:
Remove ur screen protector.
[Nexus 4 Original Android Development] synergye:
I would have kept this to PM, but you don't accept PMs (don't blame you).

Hi,

first of all, great work with the kernel. Your hot plugging implementation is top notch and quite good for the android world. I'm messaging you in hopes that you will stop distributing your kernels as full boot images, and instead distribute them as anykernel zips. Whatever you do in ramdisk, whether it be changing governor and frequency settings, or something else entirely, there are better methods. This behavior is unnecessary, breaks custom imports on ROMs that use their own (aokp, cm, cfx, etc), and also breaks boot for some ROMs causing instability due to a boot classpath not being found. In the latter case, cfx uses okhttp as a required, additional boot classpath. As seen the other day, you may then blame it on the rom itself without any evidence, when in reality it's due to your outdated distribution method.

Please consider this small modernization,

Synergy
[Nexus 4 Original Android Development] sNoxious:
Sorry for the OT but I hope CM would implement this on their future releases, Chat Heads for every app sure sounds awesome. :)
[Nexus 4 Original Android Development] theMaDHakkeR:
R134 is very very smooth. Noticing the second core comes on more often due to the hot plug tweaks. With 125UV on all cores I still get amazing battery life. 4 hours screen with over an hour talk time and still have 30% left.
[Nexus 4 Original Android Development] mdaamir1989:
Hey Franco bought your app yesterday . Its awesome i must say . I have a little small request if it can be fulfilled . I dont know if this has been asked already. In the headphones volume boost option can an immidiate change occur after changing the volume level ? I almost have to wait for 20 seconds after pausing the music . Is it just me who faces this issue ?
[Nexus 4 Original Android Development] z3nith66:
Are you guys using 3G or Wifi? Or how do you get that much battery life?
[Nexus 4 Original Android Development] scream4cheese:
Either one gives me great battery life.
[Nexus 4 Original Android Development] z3nith66:
Then something's wrong either with my phone or with my network...it EATS a lot of battery on 3G :/
[Nexus 4 Original Android Development] Dan53:
bad signal?
[Nexus 4 Original Android Development] Jsparta26:
Rogue apps maybe?
[Nexus 4 Original Android Development] z3nith66:
sometimes yeah, but still drains a bit too much.

Don't think so.

I think I'll factory reset it and keep it like that for a few days, see how it behaves.
[Nexus 4 Original Android Development] peschka:
[MENTION=3292224]franciscofranco[/MENTION]

I'm using your kernel from the r33 or so. It's my fav kernel in terms of performance and battery life. Hoewer I recently bought a Sony Smart Watch which uses BT to sync with phone. Here is the problem .. when the phone screen is off - watch is not refreshing widgets and not showing menu (sometimes even loose connection). I tryed more than 10 versions back but still the same. Other kernels like stock or faux works and refreshes whyle screen is off instant. Can you take a quick look at it ? Thanks.
[Nexus 4 Original Android Development] dave0373:
I only have this problem with franco's kernel. Stock CM kernel always reports correctly, even with dirty install after dirty install.

I fully discharged last night and this morning, after charging all night, my battery reported 84%.
[Nexus 4 Original Android Development] Saiger:
just dont charge over night.. the phone reacts crazy sometimes

i had the same problem
[Nexus 4 Original Android Development] Ollie_17:
Hi Ive flashed r134 onto my stock rom but ive noticed when i run antutu i get a low score at around 14,000-15,000 and when i compare it to the average nexus 4 in the chart section the ram and the cpu scores are a lot lower. Also for some reason im getting around the same screen on time as the stock kernel anybody know whats happening?
[Nexus 4 Original Android Development] JNewms:
Franco will tell you he doesn't give two $hit$ because benchmarks are pointless.

If they are important to you for some reason, just enable all 4 cores and over clock your phone. You can then be the king of benchmarks
[Nexus 4 Original Android Development] michael_ta315:
Just ignore the freaking benchmark. Is your phone running smooth? yes? GOOD. And SOT is varied upon usages. Franco kernel does not increase the battery by 50%. It's mostly lower power consumption during sleep. So if you have around 2-3hr SOT with Wifi, full sync, location services and such, you're doing fine.
[Nexus 4 Original Android Development] Ollie_17:
I know i just thought i was too low and that it could be the cause for my battery life being the same
[Nexus 4 Original Android Development] nexusmaniac:
Same thing happens to me too and I haven't been able to find a fix :(

N4/N7 - CM 10.1 Nightly, Franco Kernel
[Nexus 4 Original Android Development] andyli1985:
Dancing naked in the garden?
[Nexus 4 Original Android Development] :
Franco, would be great if you could consider synergye's ideas. I'd love to have your kernel on cfx. Thanks
[Nexus 4 Original Android Development] italia0101:
Ok . I was worried I'd have to eat my phone .... What a game .

Bet balotellis gf was worried at the end ;)
[Nexus 4 Original Android Development] Nethojs29:
Almost lose $100... Thanks borussia for beating who beat Manchester United.

Two days without playing and my phone still at 40%, that sleep is amazing and I still got 4 hours of SOT. Will try this again to get screens

Enviado desde mi Google Nexus⁴
[Nexus 4 Original Android Development] Underground_XI:
That's what Webb must have thought when he did not give the penalty against higuain min 13:)
[Nexus 4 Original Android Development] cpu004:
Is this related to your kernel? Someone suggested it might be related in another thread, though milestone 2 gives same issues.
[Nexus 4 Original Android Development] justibasa:
Had an sod about half hour after flashing 134. Will see if it happens again and get a logcat.

Don't like me......BITE ME!!!!
[Nexus 4 Original Android Development] yokuyuki:
You mean turbo boost? Turbo boost only kicks in when the task is lightly threaded so it can afford to shutdown the other cores in order to raise the frequency of one core and still stay within TDP. I'm not sure if Android can determine if something is lightly threaded or not though. It'd also complicates the governor a lot more to know when to offline cores to boost one core's frequency and when to back off from that.
[Nexus 4 Original Android Development] mrgwap:
Chat heads on every app would be gangster... I love that feature
[Nexus 4 Original Android Development] Foxnov1990:
Or you just wait for Facebook Home (launcher)
[Nexus 4 Original Android Development] italia0101:
Nooo this will crap all over Facebook home . it isn't the same . its every app . literally . every one
[Nexus 4 Original Android Development] franciscofranco:
I don't know what you're compiling from, but that won't happen if you fork my sources. That just means the compiler can't find that function.

Thanks for the input, but it doesn't make sense here in this arch, sorry!

Directly.

Distributing boot.img is not old and outdated. That is how Google distributes their boot images when you download their Nexus Images. Proving a boot.img for me gives me tons of benefits in customization and helps the ease of flashing through my app, and that is what I care.

If other third party roms decide to change their ramdisks why do I need to change to cater for their mumbo jumbo? I build the Kernels for myself and I share it with you all, I don't make Kernels to be compatible with other roms. I may eventually add a classpath like I did with CM if it doesn't break overal compatibility.

Yes I blame it on the rom, it was the rom that ****ed it, not me. Its always easy to blame the Kernel developers though.

I didn't change anything related to Bluetooth. Are you sure it works with stock? Can you show me a video please?
[Nexus 4 Original Android Development] synergye:
You're right. Catering to CM, AOKP, and any other custom ROMs is silly. Best to only cater to pure release aosp by using a method that hasn't been adopted into custom development for a plethora of reasons. What a shame. I won't clog up this thread any longer.

Edit: tldr: no reason for a kernel to hold back ROM development, and only supporting the aosp release branches.
[Nexus 4 Original Android Development] franciscofranco:
But why do I always have to adopt what others do if this method works for me? This method WORKS for a number or reasons. I don't remember seeing ****ing CM catering for us when me, Ezekeel, morfic and Imoseyon asked them to ****ing use the same code as we used for the Color Control on the Galaxy Nexus, instead after 3 months of us asking them they didn't give a ****. Its always the same, Kernel developers are the ones trashed because the methods they use are probably the ones they are more confortable with and that gives them the best results. I haven't seen anyone complaining though. I will eventually add the ****ing classpath like I did for CM, but I'm not going to stop using this method because it gives me the flexibility I want and its best for everyone.

Don't take it personally though.
[Nexus 4 Original Android Development] benblb:
tl;dr at bottom

I'm assuming this is not a kernel issues, but since the fine people on this thread are power experts, I wanted to post here. I recently purchased LG's WCP-300 Wireless Charging Pad for use with my Nexus 4 (Stock ROM, FK r127).

Last night after running my phone down to ~8%, (with some bump charging a few percent points with a cable during use) it got really hot. Once it got hot, all connection dropped. The phone showed greyed out wifi and cell service bars, and I could not send SMS or access the web.

Once I let the phone cool down and rebooted, everything was fine. I figured that it was a normal response for the phone to prevent itself from overheating and was okay with it. When it overheated I was in a Google+ hangout.

Here is where the wireless charging comes in. I put it on charge last night, and when I woke up this morning my phone was around 60% power. Looking at the attached screenshots, the phone appears to have stopped charging a couple hours later, and thinks it has been on battery power for over one day. To me that indicates that the phone did not realize it was charging.

If anyone could help me out I would really appreciate it.

tl;dr: Phone overheated, dropped all connection. When phone cooled and I rebooted connection came back. Wireless charging pad only charged phone for a couple hours from ~8% to ~60%. Solutions?
[Nexus 4 Original Android Development] synergye:
Can you name one thing you need this method for that you can't do with an any kernel method? Getting one boot image to work on all ROMs as they intended seems more of a feat to me. Not looking to pick fights here.
[Nexus 4 Original Android Development] LaboDJ:
I cloned your sources: git clone https://github.com/franciscofranco/mako.git -b nightlies

Anyway I read mako_hotplug.c directly from you github HERE, i cannot see where that fuction is defined, only used @ line 145.

I didn't control included .h files :rolleyes:
[Nexus 4 Original Android Development] Scottyfer:
Can you name one reason why he should stop doing what he's doing to make his kernel compatible with your rom? One rom out of the dozens we have is incompatible with franco. Put in your OP that it isn't compatable and get on with life.
[Nexus 4 Original Android Development] franciscofranco:
I need it to properly mount the partitions with the options I want, to have a custom .sh file doing some changes during boot, specially removing the PowerHAL that we don't use, to set some special parameters from init.rc, to add init.d support, to remove mpdecision, to remove thermald, to change permissions of a bunch of files, to remove some logging, to auto-flash directly from my app. This is the method I'm confortable with and that I enjoy the most. I'm not going to change to something else because this is what I like.

Easy if you just tell me the classpath I need to include and I'll gladly include it on the ramdisk, no harm done.

Function comes from here #include <linux/rq_stats.h>
[Nexus 4 Original Android Development] Warbuff:
But you are tho
[Nexus 4 Original Android Development] synergye:
It also gets rid of the cm and aokp custom rc's, as well as any other changes custom ROMs make. I would say these are also incompatible just because it's no longer kernel only changes that are being forced onto users.

Edit: saw the post above by Franco. What a shame considering all those can be done using the any kernel method. Thank goodness people started using git over svn even though they were most comfortable with svn.
[Nexus 4 Original Android Development] Scottyfer:
Forced? Who is forcing anyone to use any kernel/rom? I choose to use franco because it works great and is generally cleaner than other custom kernels. If rom developers want to put a warning in their OP that franco could possibly break things, that's fine, but trying to make another dev change his ways is just ridiculous.
[Nexus 4 Original Android Development] synergye:
I gave a suggestion for assimilating with the rest of the kernel developers, then was cursed at. Now I understand some of what I've heard. No more clogging up this thread by me.

Franco: the classpath is system/framework/okhttp.jar. would be appreciated if you could add it. I imagine more devs will switch to using it over libcore's implementation due to the performance benefits.
[Nexus 4 Original Android Development] ceejay83:
Why are other kernels that use any kernel still not booting on your ROM?
[Nexus 4 Original Android Development] trueblueram:
Glad to see devs talking to each other on issues. Let's please not have firestokers(is that even a word?) Adding to stuff. Trust them to know what they are talking about
[Nexus 4 Original Android Development] stratosk:
Forgive my interference. But what is the 'other' way to distribute a kernel?

Just out of curiosity, how can you distribute a kernel for nexus that it's not in boot.img format?
[Nexus 4 Original Android Development] Cuzz1369:
Because that ROM has never been very stable.
[Nexus 4 Original Android Development] DeZire17:
I've noticed that clearing app's data doesn't reset to the default settings, like governor settings / Maximum Frequency..
[Nexus 4 Original Android Development] vowywowy:
First day on r134 and something absolutely killed my phone. Something called keystore, I know for sure its not an app I have installed because I only have the default Google apps. As you can see from the screenshot my screen was barely on today and some randy system app ate all of my battery. Anyone know what this is or how to fix it?

EDIT: To anyone reading this having the same problem: I have isolated what the issue is but have no idea how to stop it or where it originated from.

My school use a credential system for logging in to the WiFi and apparently, after looking at the keystore method, it seems that it will constantly try to login to the WiFi while it is connected. If the login fails, keystore will retry the login an unlimited amount of times until the phone dies or it gets in. I feel like this is an incredibly detrimental bug in Android and I still don't know why I haven't experienced this bug until r134.

Current Nexus 4 Setup is as follows:

CM10.1 M2

franco.Kernel r134 (all default values)

All stock Google Apps
[Nexus 4 Original Android Development] tkalli:
SEE HERE
[Nexus 4 Original Android Development] Redneck Trash:
You gave to reboot after clearing data.
[Nexus 4 Original Android Development] vowywowy:
This helps me 0%. I Googled keystore on my own and nothing tells me why it sucks phones battery life. As the name suggests it is a method called by the operating system to store crypto-keys. But why is is being accessed so frequently (if that is the cause of the battery loss) and how can it be fixed?

Your post isn't very helpful.
[Nexus 4 Original Android Development] nexusmaniac:
How do I get back to stock kernel settings because wiping app data didn't seem to reset the settings and I've unticked set on boot?

N7/N4 - CM10.1 Nightly, Franco Kernel
[Nexus 4 Original Android Development] PetritH:
Open FKU then click the first option and u have the option to clear data.

BORUSSIA DORTMUND BTW :highfive:
[Nexus 4 Original Android Development] CaspaTheGhost:
As above, clear app data and reboot.

Sent from my BAKED N4
[Nexus 4 Original Android Development] :
Good to see some conversation going on here. I love both franco kernel and cfx and frankly, I don't have much of an idea of the technical side of things, but it would be great if you could find a way to get all that to work.

[MENTION=371528]Everybody[/MENTION] else here: no need to protect franco and attack synergye. They are both great devs and I'm pretty sure that franco can take care of himself. Show some respect for these guys' work.
[Nexus 4 Original Android Development] synergye:
From what I've seen, both of us could bash on the other one all day long, and neither of us could give a ****. That wouldn't change the fact that I hold franco's coding abilities quite highly...it really is quite rare to come across an android kernel dev who can actually write good looking C. I'm sure that adding this to the bootclasspath would work fine. I said tomatoe, he said tomato, it can still end up in the same place.
[Nexus 4 Original Android Development] tkalli:
I posted because You wanted to know what keystore was.

I didn't know either so I Googled it and posted the link.
[Nexus 4 Original Android Development] yokuyuki:
Wait, I thought Facebook Home could do chat heads on every app.

He wanted to know how to fix it. I don't see how googling what it means helps.
[Nexus 4 Original Android Development] sNoxious:
Only for Chat Heads, not every app like Google Talk, SMS, Viber, etc.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Vangelis13:
It's never good when developers have open discussions like this in a thread and we regular users can interfere and possibly add -unnecessary- aggravation. Pm, email, g+, anything is better than the wide openness of a public thread.

You're both great devs with a big faithful following; no need to segregate them over a line of code..

I hope you understand and excuse the direct tone..
[Nexus 4 Original Android Development] obsanity:
So I'm getting a delay with r134 just when pushing the power button to turn the phone on. Up until the m2 it wasn't there. Anyone else?

Sent from my Nexus 4
[Nexus 4 Original Android Development] franciscofranco:
Thanks for the nice words, really appreciate it!

I'll add it to the classpath, no harm done :)

Try to re-flash r134 ;)
[Nexus 4 Original Android Development] PetritH:
Did you flash the new r134? Franco reuploaded and the problem is gone
[Nexus 4 Original Android Development] kyokeun1234:
I personally don't have this but I remember some people mentioning something about delay when pressing the power button to wake the phone up.
[Nexus 4 Original Android Development] thebryceee:
Maybe you flashed the new r134 before the old one was up
[Nexus 4 Original Android Development] kyokeun1234:
Maybe but I did flash it right away so I don't know
[Nexus 4 Original Android Development] obsanity:
No I flashed after but just now I reflashed for ****s and giggles. I'll check it out and let you know. BTW, been running 1.7ghz all day without issues.

Sent from my Nexus 4
[Nexus 4 Original Android Development] little-vince:
As far as I can tell, there is nothing wrong with discussing the development of a kernel in the kernel thread. I mean, it's under Android Development for a reason.

synergye gave a suggestion that would provide better compatibility between franco kernel and other roms, something that end users would benefit from. But people thought he was attacking franco and "forcing" him to do things differently. franco justified why he's doing things the way he is, and that's it. Quoting franco here:

The problem isn't developers discussing in a development thread. It's, like you said, the regular users who can interfere and add possible aggravation.
[Nexus 4 Original Android Development] Vangelis13:
^^ We're saying the same thing. :)
[Nexus 4 Original Android Development] yokuyuki:
Ah, he should have said just not facebook messenger. I'm guessing it hooks into the contacts stuff on Android?
[Nexus 4 Original Android Development] JNewms:
Not only that. It hooks into every app with notifications. If you look at paranoid android Google + page there is quite a bit of description of it in the comments.

Sorry for off topic guys.
[Nexus 4 Original Android Development] Luigiesin:
Hey guys... I'm noticing better battery life with 134V2... Better battery and performance than M2... Are you noticing the same or its just placebo? Being running it since last night.

Sent from my Rock & Roll Nexus 4 \m/

ROM: PA 3.15

Kernel: Franco r134

T-Mobile
[Nexus 4 Original Android Development] PetritH:
Yeah it feels faster and smoother to me too.
[Nexus 4 Original Android Development] ÜBER™:
[MENTION=3292224]franciscofranco[/MENTION] I know you dont support UV related issues. Just wanted to say that i was playing with UV and OC and got bent over... Got stuck at the bootani :\. Tried [MENTION=4544860]osm0sis[/MENTION] 's emergency zip, didnt seem to help. Guess something got corrupted.

Point being, dont mess with **** unless you're prepared to face some ****. :

:)
[Nexus 4 Original Android Development] kyokeun1234:
For me, battery is worse but it could well be because it has only been like 2 days since flashed and it could well be the fact that the kernel hasn't settled in yet. Not to mention that I was on 3g a lot when I was using it. So that could be it.
[Nexus 4 Original Android Development] Luigiesin:
134 just came out last night... Maybe you're talking about M2?

Sent from my Rock & Roll Nexus 4 \m/

ROM: PA 3.15

Kernel: Franco r134

T-Mobile
[Nexus 4 Original Android Development] kyokeun1234:
Nah I'm talking about r134 and yeah it has been a day but really, day and a half for me so I just rounded it up :p but what I said is still true :p whether it has been a day or two, I don't think I'm having a great battery life due to the fact that kernel didn't settle in yet
[Nexus 4 Original Android Development] leets4uc3:
What is everyone running for hot plug settings? Stock, 4 cores on? I tried 90,65,25 but didn't see any benefits over stock. I am looking to save some battery
[Nexus 4 Original Android Development] ceejay83:
Everyone uses stock settings
[Nexus 4 Original Android Development] Mercado_Negro:
3G uses a lot of battery, doesn't it? I've never had half the battery life people here says and shows on graphs. I've checked for wakelocks and I've never had any problems with them. I guess it's just my data connection, which by the way, isn't that solid either.