yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] very.goot:
When I flashed r34 with the updater app the same thing happened to me. (and I never changed the setting in the app)

Not a huge deal for me, just something I encountered.

Stock ROM, rooted. :confused:
[Nexus 4 Original Android Development] tmcpnet:
Here is the stock bootanimation

http://d-h.st/SE3
[Nexus 4 Original Android Development] ben_pyett:
We need to take care to only offer assistance based on facts, re-flashing a ROM will not resolve issues (unless you've done some extremely daft things), where as a clean install will only likely to be of any benefit if you have dirty flashed the ROM in the first place. Otherwise people will believe this advice and then the circle begins all over again......
[Nexus 4 Original Android Development] siscim23:
There is a setting in the Franco app to change the boot animation... make sure that's not checked.
[Nexus 4 Original Android Development] very.goot:
Thank you, that was the first thing I checked. ::good:
[Nexus 4 Original Android Development] yokuyuki:
Try r33 then and see if it still happens.
[Nexus 4 Original Android Development] very.goot:
Thanks!

noob question, I am still using stock recovery, can this be flashed through fastboot?
[Nexus 4 Original Android Development] vomer:
Firstly, I made a suggestion. Never asked for it. Secondly, if something so trivial bothers you then simply stop reading it.

This will be my last response in regards to this silly discussion.

Sent from my Nexus 4
[Nexus 4 Original Android Development] ctfrommn:
It cant be flashed, but you can push the file to /system/media or /data/local (my preference as it wont get overwritten as easily there). Make sure you fix permissions too.
[Nexus 4 Original Android Development] nellisere:
Reflashed r33 from r34, now I've got com.android.phone and NFCService has stopped working (could me more, got bored constantly pressing OK) Not sure if ROM or Kernel made issue.

Reflashed again, stuck at Google logo. Not a great experience.
[Nexus 4 Original Android Development] very.goot:
Perfect. :good:
[Nexus 4 Original Android Development] tmcpnet:
Try the steps mentioned on below link. Hope something works out for you

http://productforums.google.com/forum/#!topic/mobile/WMeRPJuEQJc
[Nexus 4 Original Android Development] franciscofranco:
Something got frakked in your android installation, kernel does not produce force closes.
[Nexus 4 Original Android Development] nellisere:
I couldn't do anything, I could turn the ringer down, that's it. Everytime I pressed OK another pop-up came up.

Have fastboot flashed r33 img and it's booting now. For some reason the zip refused to work.

Cleared cache + dalvik and fixed permission, it's working now.
[Nexus 4 Original Android Development] deepsunzhine:
I agree with u, but we need to get used to ppl that dont wanna help:mad:

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Original Android Development] zFayZz:
Getting 4hrs screen time.. Pretty good for heavy use and using gps auto brightneess data wifi sync all turned .. Uninstalled weather channel as it used my gps for a full hour probs why it drained quicker

Bout time i lowered brightness n turned off a few settings could get 5-6hrs screen time

I have already underclocked cpu to 918 mhz as it rarely goes higher than that

Is there any other way to improve battery life? Whats the ideal i/o scheduler?
[Nexus 4 Original Android Development] vomer:
You could get better battery stats to check what apps are draining your battery. I think you might be obsessing over it too much, enjoy the experience - don't cripple it :)

Sent from my Nexus 4
[Nexus 4 Original Android Development] Nebucatnetzer:
Well I probably picked a bit the wrong words for this. I just doesn't makes much sense from my point of view sry for that.
[Nexus 4 Original Android Development] deepsunzhine:
20 min of youtube, 30 min of music and alot of tapatalk and webbrowsing...and 54% of battery remainin

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Original Android Development] terranox:
ROM?

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Original Android Development] deepsunzhine:
Stock ROM

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Original Android Development] daishou:
Hello Guys.

Im using Cm 10.1 - Latest Nighty and the latest Franco. I want the max. battery life and still a stable system.

What settings are recommended to achieve this?
[Nexus 4 Original Android Development] ctfrommn:
Flash and forget....Franco's stock settings are amazing. You may gain marginal battery life be underclocking some.
[Nexus 4 Original Android Development] tmcpnet:
default kernel settings works out pretty well :good:
[Nexus 4 Original Android Development] AnthonyAldrete:
would a lot of you say that this Kernel is as if not faster than stock kernel ? just curious
[Nexus 4 Original Android Development] Prod1702:
Yes
[Nexus 4 Original Android Development] DowntownJeffBrown:
Yes

Sent from my Nexus 4 using Xparent Blue Tapatalk 2
[Nexus 4 Original Android Development] ctfrommn:
Maybe as fast....maybe. Stock kernel is ridiculously smooth. Francos has way way better battery life though.
[Nexus 4 Original Android Development] vindikleuk:
Ah, alrighty. I hadn't noticed it before a couple days ago though. Must be me.
[Nexus 4 Original Android Development] chrisgtl:
Anyone else getting sick of the endless pages of battery screenshots/stats?

A new thread needs starting called 'Suck my battery stats' - then all us interested in development/problems can come here and get our information easier.

WE ALL HAVE THE SAME PHONE, SAME BATTERY, 5 FINGERS, 5 TOES, 1 HEAD.

Sorry for making a negative post like this but it really is starting to grind my nipple ends now!!

Sent from my Nexus 4 using www.16hour-on-screen-time.nobodycares
[Nexus 4 Original Android Development] scream4cheese:
I have 10 fingers and 10 toes. :D
[Nexus 4 Original Android Development] benrees21:
All the crap on XDA lately is grinding my gears! I know I was a noob once but I always read the OP thoroughly to understand what I was flashing and what features or bugs were present. Now the noobs don't bother at all. They just come on and hit reply, "does this work with so and so". "Can you add this?" "How do you do this". "Why is this happening?". Anyway, latest kernel running nice. No problems. :)

A Nexus Connoisseur!! AOSPA!!
[Nexus 4 Original Android Development] khanh1289:
Not all phone, battery, fingers, toes, and head are created equal, therefore, people feel the need to prove superiority.

That supposed to be for $hit and giggles not dissing you in anyway! I too get annoy by it.

Sent from my Blenzderz 9000
[Nexus 4 Original Android Development] deepsunzhine:
So u having poor battery life????.....:what:....we are happy for francos work and want to show the results ihis kernel is givin us...dont hate bro
[Nexus 4 Original Android Development] Ibsonic:
Here we go again :banghead:

Verstuurd van mijn Nexus 4 met Tapatalk
[Nexus 4 Original Android Development] yokuyuki:
Useful if you're comparing kernel revisions and I'm just talking about BBS screenshots for idling time. I don't care for the my phone lasts x number of hours with x number of hours in screen time and other people asking them how they did it though. That stuff belongs in PM. We all have different usage patterns so it's pointless to compare those.
[Nexus 4 Original Android Development] franciscofranco:
Comon people, lets all behave, this has to be a healthy environment, not hostile :)

I feel r34 is great, Im almost on 2 days without charging and still 50% left, I'm really happy.
[Nexus 4 Original Android Development] daishou:
This is impossible if you use your device more then 30 minutes a day :eek:
[Nexus 4 Original Android Development] yokuyuki:
Look at all the other Nexus devices he has sharing his time. :p
[Nexus 4 Original Android Development] j.llorente:
I've got some problems with notifications. Sometimes notification doesn't work until I turn on the touchscreen. Some people have got the same problem. I'm using r29 but this problem occurs with r34 also.

---------- Post added at 01:27 AM ---------- Previous post was at 01:25 AM ----------

Hmmm,and I post 2 screenshots with battery drain...It's excellent this kernel is my GOD hahaha.

https://dl.dropbox.com/u/357276/Screenshot_2013-01-16-00-57-43.png

https://dl.dropbox.com/u/357276/Screenshot_2013-01-16-00-57-49.png
[Nexus 4 Original Android Development] Vangelis13:
Are you asking or telling..? :p

(Not kernel dependent..)
[Nexus 4 Original Android Development] franciscofranco:
Hmm... Im always chatting with my GF using WhatsApp, so no. My 3G is always enabled.

That also happened with me on stock kernel/stock rom. We gotta wait for 4.2.2.
[Nexus 4 Original Android Development] yokuyuki:
After a day on r34, I'm still not getting as good of wakelock time as I did on r30 which is perplexing because diffing r30 and r34 on the github shows no differences in /drivers/usb. Is there anything else that would affect msm_hsic_host wakelocks? Going to keep testing r34 to compare though.
[Nexus 4 Original Android Development] j.llorente:
Thanks!! But...I didn't have this problems with stock rom/kernel, I use this 1 month or more. But i don't know if this problem is due to CM10 or your kernel because I changed both. But OK!! I'm waiting impatient for 4.2.2
[Nexus 4 Original Android Development] chinthekng:
And your using stock :eek:
[Nexus 4 Original Android Development] benblb:
Maybe he doesn't use Google Now, Facebook, and Google+. Just a thought because I use all three and my battery is nowhere near that good. :p
[Nexus 4 Original Android Development] lightosx:
I played NFS for an hour and 20 min today after charging to full on r34 and was still at 40% after which is pretty impressive.

Edit: forgot to mention I used Franco's stock settings.
[Nexus 4 Original Android Development] franciscofranco:
No, MiNCO + some local test kernel, but its basically r34.
[Nexus 4 Original Android Development] iFalcon:
+1....lmao....well said.

I just hope some put as much effort into other things in life as done with battery stats.
[Nexus 4 Original Android Development] yokuyuki:
Got a random reboot on r34. Really odd thing was that when it booted back up, the camera didn't work. Had to reboot again to get the camera working again. Here's the last_kmsg: http://pastebin.com/sRaPjqzX
[Nexus 4 Original Android Development] Ok_Kaleidoscope5109:
My issue with comparing BBS screenshots is that it's all theoretical. Like comparing Quadrant screenshots. The +/- 40 points people see moving nightly 1 to nightly 2 is not necessarily attributed to an improvement in the ROM when you can already see run variation like that. Even if you see a BBS difference in wakelock (yeah the HSIC wakelock has been changed recently), does this translate to a battery difference?

Daily use patterns vary, and application behavior is variable too.

I appreciate Franco's work, but is it really a night and day difference? I ran Chainfire's perfmon and played around on stock. Franco changed the ramp to 918mhz instead of 1026 mhz, but for people to say that's gonna be 5 extra hours of battery life is stretching it. Furthermore, swiping instead of tapping ramps the second core, but in standard browsing, phone using, how much tapping are you doing? There's always going to be some swiping. It's not like the stock kernel runs 4 cores at 1ghz constantly when you're touching the screen. It's usually 2 cores and then idles to 1. While someone knowledgeable can point out noticeable differences in core activity, I think most people here could easily confuse the two just looking at separate core monitoring apps if it weren't the difference between 918 and 1026 mhz.

I tend to think if you weren't to look at theoretical wakelock and just look at standard battery life at the end of the day in a blind test, 90% of the people here would mix the kernels up.

I also think that franco ramps core speeds slower and is more conservative in general than the stock kernel which actually translates to performance slowdown. I don't see how people can say it's snappier. But then again I may be wrong. Maybe it's placebo on my end. From the 10 minutes I spent playing with scrolling on each, I found stock CM kernel to be smoother.

I just absolutely hate those who go "OMG r33 = massive battery drain. R32 was good. I'm reverting back." How can people even say this based on 1 day of use only? Unless people run controlled tests, jumping to conclusions like these is very questionable IMO.
[Nexus 4 Original Android Development] Ballastatuz:
First random reboot. I'm on r34 and was posting on the verge through chrome beta.
[Nexus 4 Original Android Development] chinthekng:
I personally haven't gotten "outstanding" battery life with this kernel but it's enough to last me through the day and in the end, to me that's what really matters :laugh: thanks again for all the work you do franco
[Nexus 4 Original Android Development] Vangelis13:
Grab the last_kmsg!

Sent from my Nexus 4
[Nexus 4 Original Android Development] ansysic:
Where's my daily dose of kernel flashing? :silly:

Just kidding, thank you franco for your work!
[Nexus 4 Original Android Development] Ballastatuz:
How do I do that?
[Nexus 4 Original Android Development] zephiK:
He kind of has that already, https://play.google.com/store/apps/...wyLDIxMiwiY29tLm5leHVzNGRpc3BsYXljb250cm9sIl0.
[Nexus 4 Original Android Development] jarjar124:
That's rgb control... I believe. Gamma control is different
[Nexus 4 Original Android Development] dima901:
Yeah, I already purchased this app, some more options like on the galaxy Nexus would be great, maybe in the future?... ;)
[Nexus 4 Original Android Development] zephiK:
Yeah it's different, he asked for color adjustments so I thought he meant by RGB and gamma.

I'm sure if it's possible, he'll add it. I'm pretty satisfied with the stock colors on the N4, a bit missing the blacks but the vibrant color reproduction makes up for it. Can't wait for all the kernel fun and all the extra goodies come as time goes by.
[Nexus 4 Original Android Development] Imperticus:
True, but hopefully the delay is because Google is negotiating with Qualcomm to release the sources.
[Nexus 4 Original Android Development] 0.0:
Maybe as time goes on, they will release. It is a new chip. Once a lot of phones have it, and they start working on another chip set for future phones, then they'll release it. Or the competition ends up doing open source before they do, forcing them to do open source as well

Sent from my Nexus 4
[Nexus 4 Original Android Development] franciscofranco:
The power hals will be open sourced like Tuna powerhal sure of it. The binaries thermald and mpdecision will not be opensourced Im sure of that.

Im trying to reverse engeneer the power.msm8960.so but nothing useful comes up using an hex editor. I'll see if its possible to turn the hex code into assembly and maybe'll get more clear code.
[Nexus 4 Original Android Development] digweed4me:
I have no idea what u just said but it sounds interesting. I wish I was smart like u.
[Nexus 4 Original Android Development] morfic:
not happy having power.mako.so in aosp?

BS, i had manta on my brain, sorry
[Nexus 4 Original Android Development] franciscofranco:
Manta's in there but power.msm8960.so no =( Both mpdecision and the power hal mess with something inside /dev/socket/mpdecision according to the binaries when I opened them in the hex editor, but theres nothing inside that directory... crap :(
[Nexus 4 Original Android Development] morfic:
What i really wanted to say is that despite PowerHAL, no frequency fückery since mpdecision was removed.

Maybe they made it a dummy since they use their mpdecision, would explain why your hex editor came up empty.

Either way, no mpdecision, no freq fückage.
[Nexus 4 Original Android Development] franciscofranco:
Its not empty, but mpdecision seems to control everything indeed and take control over every other frequency ****age binary etc. **** mpdecision.
[Nexus 4 Original Android Development] IAmAN00bie:
Haha, that seems to be Faux's opinion of it too, hence why he got rid of it. It's been great ever since, all the settings stick, no more aggressive bumping up to 1026MHz on touch, etc...
[Nexus 4 Original Android Development] Dragooon123:
Does this kernel also include the old touch drivers which increase responsiveness?
[Nexus 4 Original Android Development] elliot.newnham:
You couldn't use the search function? It contains an accuracy filter though.
[Nexus 4 Original Android Development] jarjar124:
no and it never will
[Nexus 4 Original Android Development] Dragooon123:
Thought so, thanks for the answer.
[Nexus 4 Original Android Development] franciscofranco:
He got rid of it because his Intellidemand has hotplug routines. If I take mpdecision down we'll lose hotplugging capabilities, thanks but no thanks.
[Nexus 4 Original Android Development] Dragooon123:
Ah what the hell, flashed test build 9. Let's see how the battery pans out.
[Nexus 4 Original Android Development] davey11:
I like how the kernel has given the haptic a boost...stock was weak and lame. It feels stronger...or my imagination?
[Nexus 4 Original Android Development] yokuyuki:
I don't really compare with others. I just compare with myself as my usage may cause more or less kernel wakelocks than others. For me, the hsic wakelock translates directly into a difference in deep sleep time in cpu states and that definitely has a correlation with battery life.

I don't know about it being snappier or faster as I'm using this kernel for battery and if you're using one that is optimized for battery, it's hard to get outstanding performance and that's a sacrifice I can live with.

Read FAQ. Use file manager and grab the /proc/last_kmsg.
[Nexus 4 Original Android Development] jmejiaa:
Franco's Kernels have been giving me much better life while the phone is sleeping, which helps a ton. Before I'd get drain even with just the phone sleeping, it was getting a ton better - the latest doesn't seem as good for this as the previous ones but I think it makes sense based on the changes.

If you don't set your phone down and have the screen on all day I don't think anything is going to break the laws of physics and give you 10 hours of battery life.
[Nexus 4 Original Android Development] ansysic:
https://play.google.com/store/apps/...t=W251bGwsMSwxLDEsImNvbS50b3J0ZWwuc3lzbG9nIl0.

Or with this app.

I think it's too late now to grab any messaged related to the reboot.
[Nexus 4 Original Android Development] digweed4me:
Hspa + and 3g all the time whole day .

Thank u franco for r34
[Nexus 4 Original Android Development] XxKillerKev7xX:
Hey Everyone just wondering if I make a clockwork recovery is there a way to save it to my computer so I can delete it from my phone for more storage.. I want to go to minico but dont want to loose the option of stock after because Google took down the OTA links. Also is there any way I can get the OTA link?
[Nexus 4 Original Android Development] shamu11:
what rom and what kernel settings are you using?
[Nexus 4 Original Android Development] Ballastatuz:
Well here is the long anyways

http://db.tt/FQ2m39HY
[Nexus 4 Original Android Development] franciscofranco:
Interesting post. The big difference between my kernel and stock is that we are free from mpdecision to control the cores and the cpu frequencies.

On stock the behavior is too eratic in favoring performance over battery because: touching the screen onlines the second core and it changes the minimum frequency from 384mhz to 1026mhz. Yes it changes it instead of ramping up, then ramping down. I had times where I looked at my device and for 10 minutes straight without me doing anything the first core was at 1026mhz and for me thats ****ed up.

Using my kernel with the custom hotplug driver not only we have control over the cores frequencies and states but it also ramps accordingly and scales like it should. The current state of the hotplug driver is that good - and it only onlines the second core if your finger moves 100 pixels away from the original touching point thus saving battery. The stock kernel does NOT do that.

In the end stock kernel will always be a tad bit smoother because of their stupid core and frequency control. Do you really want that?
[Nexus 4 Original Android Development] mobilehavoc:
What about remove the 100px limit and make it on touch at least? That would eliminate any lag and still be better than stock. I notice keyboard and one press items (no swiping actions) are much smoother on stock and motley that don't have this swipe threshold. Battery life doesn't seem much worse.

I love Franco kernels and they have great battery life and are stable as a rock but they make the device too laggy and feel like my Galaxy Nexus. Battery life is huge but in the end you also want to take full advantage of the hardware
[Nexus 4 Original Android Development] digweed4me:
Aokp jan13 and francoa r34 no undervolt no oc
[Nexus 4 Original Android Development] franciscofranco:
I completely disagree, since when do you need two cores to type or touch stuff? Do you know you actually need the software to take advantage of multi cores for threading? Since when touching-only requires more than one thread to dispatch touch events?
[Nexus 4 Original Android Development] ansysic:
The question is: why shouldn't you be able to copy it to your computer? For me (cyanogenmod), clockworkmod backups are saved under /data/media/clockworkmod. They won't appear in MTP mode (USB connected to your PC), so you have to move them to /data/media/0 or transfer them in an other way.

About the OTA files: you probably mean the nexus factory image. google for it, I'm sure it is somewhere ;)

Edit: damn, couldn't resist :D http://xdaforums.com/showthread.php?t=2042699
[Nexus 4 Original Android Development] XxKillerKev7xX:
Thanks :D
[Nexus 4 Original Android Development] trailblazerz11:
Smoother on stock because its constantly on 1026 freq.

Franco has to scale up, if you have slight lag play around with interactive go_hispeed for the boost you need.

I was suggesting a input_boost on frequency not just onlining a second core however go_hispeed seems to achieve the same thing when tuned with less unnecessary boosting.
[Nexus 4 Original Android Development] JNewms:
I gave my phone a voice command to make me a bacon sandwich, and it didn't do it, instead it brought up a page about bacon. I believe this bug is kernel related. Franco, could you make the kernel able to make bacon sandwiches? Fastboot/givemebacon

Sent from my Nexus 4 using Xparent ICS Tapatalk 2
[Nexus 4 Original Android Development] mobilehavoc:
Fair enough do you know for sure that the keyboard process doesn't run as a separate thread? I'm sure it does and so would benefit from another core. Multithreading isn't just if an app supports it but running multiple processes simultaneously without introducing wait states since you have more active queue. Just saying I can noticeably feel the difference typing on stock keyboard on other kernels and yours. Not a dig but there's something tangible. Maybe I type too fast?
[Nexus 4 Original Android Development] ansysic:
- remove thermal threshold

- fire up all 4 cores on default

- set min_freq at 1500 Mhz

- place ham on your phone

Voilà ;)
[Nexus 4 Original Android Development] Ibsonic:
100 PX is just as big as your nail on our huge resolution screen.. So its just tapping on letters.. And if you make a little .. Yes, a little, swipe gesture the second core will jump in.

Verstuurd van mijn Nexus 4 met Tapatalk
[Nexus 4 Original Android Development] veyka:
Do we really need 2 krait cores at 1026mhz just to type smoothly?

My gnexus and sgs2 could get by fine at lower clock on slower cores, i get the whole project butter stuff, but stock is far to aggressive!

I'm not having a go, it just seems a bit sad if we really need to chuck that much grunt at something as basic (I won't say simple due to the heavy auto correct needed to make typing on screens ok) as text entry :(