yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] jdmcivic:
[MENTION=470754]Franco[/MENTION]

it'd be nice if there was an option to pull the logcat directly from your app itself. just a click away, upload and you're done.
[Nexus 4 Original Android Development] franciscofranco:
As I said I will have 3 themes, the dark one slightly tweaked, a light blue one, and this light green. I like the light green, its fresh and new. Light blue as well, very fresh. Will be released in its due time, I only started a few hours ago.

Nope, last time I added something like that my inbox looked like Best Buy in the Black Friday.
[Nexus 4 Original Android Development] gharrrrrr:
On r127. Bat life is awesome and phone performs well. Sorry to busy to apply actual tests. But my daily use matters more to me. Mostly on T-Mobile hspa+. Can't be happier. Only about 3 hours on WiFi so far today. Thanks Franco. Love new hotplug and interactive. Used to use conservative to get same distance.

Also sleeps like a baby.

Went down to 1% bat with r127 and carbon ROM while out at bars. Made it home with still 1%. Can't ask for more. Deep sleep is awesome.

Sent from my LG-E960 powered toaster.
[Nexus 4 Original Android Development] Trewyy:
I need help...

...killing my battery

But seriously, I have about about 3 hours SOT with WiFi and GBA emulation (Earthbound 2 if you were wondering!) with 45% STILL REMAINING!

At this rate I'll probably hit 5 1/2 - 6 hours SOT.

Running RC1 with min. freq at 702mhz and -125 UV. Most other settings remained on Francos defaults.

Awesome job Franco!
[Nexus 4 Original Android Development] jdmcivic:
what i meant was for an option to just execute the command and saving it to memory. no auto sending of emails. lol
[Nexus 4 Original Android Development] MaluNoPeleke:
Anyone else with this problem?

Sometimes when I charge my phone it only stays at the current battery percentage but doesn't fill up to 100%. If I unplug and plug it in again it works as expected. Fastcharge deactivated.

Thanks for help
[Nexus 4 Original Android Development] franciscofranco:
adb logcat > /sdcard/logcat.txt

adb shell dmesg > /sdcard/dmesg.txt

Done :)
[Nexus 4 Original Android Development] RiThBo:
Using rc1 - no problems with notification draw as I had previously. Thanks Franco :). Also, if I change the input_boost freq, do I lose the new automatic interactive stuff?
[Nexus 4 Original Android Development] :
[MENTION=3292224]franciscofranco[/MENTION]

The issue after ending a call is still present for me on rc1, it happens when I touch the phone trying to press the end call button, the notification bar literally blocks me by coming down
[Nexus 4 Original Android Development] franciscofranco:
You can change that value, no problem.

Literally have no idea about that! Are you running the old touchpanel driver E017?
[Nexus 4 Original Android Development] JarGnex:
No problems here :confused:
[Nexus 4 Original Android Development] khanhtrinh:
Can anyone help with the answer?

Gửi từ Nexus 4 của tôi
[Nexus 4 Original Android Development] :
No mods only changes I've made are through FKu (UV, volume boost, suspend frequency, colors), I installed my current ROM (Xylon 2.7.0) with a full wipe (factory reset/ format system) only thing different is the kernel, never happened before rc0/rc1, I still like the current kernels enough to just ignore so maybe it'll stop :fingers-crossed:
[Nexus 4 Original Android Development] jdmcivic:
alright. just suggesting since u have the clear app data option in your app where u could just go into app manager and clear it. :)
[Nexus 4 Original Android Development] mkamal23:
Yeah.... Just been playing with my phone with RC1 on it now, and I am a believer. No placebo. Great Job
[Nexus 4 Original Android Development] MaluNoPeleke:
No one?
[Nexus 4 Original Android Development] tuilalnvinh:
Unless the game could utilizes efficiently all 4 cores, you can't see any difference in temp between 2 & 4 cores online.
[Nexus 4 Original Android Development] drawde40599:
58 is normal temp if your actually using the phone, new versions bout the same
[Nexus 4 Original Android Development] JNewms:
I don't have that issue. I use the orb to charge at home, if I ever need a charge while out or at work I plug it in. It always goes to 100%
[Nexus 4 Original Android Development] drawde40599:
Stock dose it also sometimes, my orb dose it all the time but after i remove it it says 100

Try letting your phone die then charge to full while off, worth a try
[Nexus 4 Original Android Development] Anytime1157:
Hmm..just few days ago I was comparing the touch screen sensitivity of my n4 with my girlfriend's xperia v(told her to buy the n4 but she didn't like it's design, ahh well :/)

I realized that her device was a little more sensitive to touch, sometimes over sensitive I must say but after rc1 I have no complain for my n4.

Great device, great developer. Awesome people :D
[Nexus 4 Original Android Development] wirtzpeitz:
r125 worked really great for me but r127 brought back a problem I had with some earlier releases: my phone dies while idling at night. It does not freeze or reboot, it simply turns itself completely off. I don't know if this is related to charging (overheating?) or the fact that it's idling for the duration of my sleep. In any case, it never does this during the day while discharging and being used. It's a big problem for me because it means my alarm doesn't go off.

I run the stock ROM.

Any ideas?
[Nexus 4 Original Android Development] gee2012:
Did you maybe undervolt too much?, i don`t have you`re issue and also use r-127.
[Nexus 4 Original Android Development] drawde40599:
U run franco with stock settings ? Do u have any of those "power saving" apps installed?
[Nexus 4 Original Android Development] jabbeboy:
Which do you Guys recommend? rc1 or r127?

Last timme i hade r125, but were not so impressed with the battery life
[Nexus 4 Original Android Development] ckarv:
RC1 has the new touch sensitivity refinements, so that's what I'd go with.
[Nexus 4 Original Android Development] jabbeboy:
Okey. Thanks.

What exactly does the touch sensitivity refinements do?
[Nexus 4 Original Android Development] ckarv:
[MENTION=3390485]jabbeboy[/MENTION] It makes the screen more responsive, less laggy. You'll probably notice it when you try it. ;)
[Nexus 4 Original Android Development] Goku80:
is it really that great the new kernel? looking forward to trying m2 then when it is out:) awesome work franco you made me stick with one kernel finally and rom:D

have to say the volume boost in both headphones and even the phone speaker is pure awesome;)
[Nexus 4 Original Android Development] ImbaWind:
Seems my N4 never got into deep sleep.

Im using touch control, isit the reason ?

**Using RC1
[Nexus 4 Original Android Development] spicediablo:
Don't think so. I am using touch control too

http://img.tapatalk.com/d/13/04/24/8e7apara.jpg

Sent from Mako⁴
[Nexus 4 Original Android Development] Goku80:
i use touch control and my phone sleeps like a baby..provide a log or kmsg for franco to have a look at
[Nexus 4 Original Android Development] trailblazerz11:
Wakelock stats?
[Nexus 4 Original Android Development] ImbaWind:
Currently charging so no wakelock stats

** last_kmsg provided
[Nexus 4 Original Android Development] gee2012:
RC1 runnning great and touch response is much better :good:
[Nexus 4 Original Android Development] santeana:
Where did my voltage control go? It's just gone! Was there yesterday.... Using 127
[Nexus 4 Original Android Development] franciscofranco:
Charging -> no deep sleep.
[Nexus 4 Original Android Development] franciscofranco:
The Snow White and her seven dwarfs stole it from you.
[Nexus 4 Original Android Development] ImbaWind:
You need a nap lol

---------- Post added at 05:26 PM ---------- Previous post was at 05:26 PM ----------

Thanks for the quick reply !
[Nexus 4 Original Android Development] santeana:
Does that mean it's only in mine? Or did I miss something? My app only scrolls down as far as governor control now. That's it.
[Nexus 4 Original Android Development] steviewevie:
Just flashed rc1. I thought my phone's touch sensitivity was fine before, but wow! It's great now! Hoping this helps when gesture typing occasionally doesn't seem to register properly. Thanks Franco!

Sent from my Nexus 4
[Nexus 4 Original Android Development] ckarv:
Is the effect instant or do you need to do something to enable it? I tried changing the values in fku but didn't notice any change. Thank you.

Sent from my Nexus 4
[Nexus 4 Original Android Development] spicediablo:
As far as I remember, it's instantaneous

Sent from Mako⁴
[Nexus 4 Original Android Development] Darkuso:
I think it's under "custom kernel settings", you can find the "headphones volume boost" there, not sure about the other option because I'm using M1 atm.

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Original Android Development] santeana:
Ok, flashed 126 and voltage control is back. Guess I missed the memo. Why was it removed for 127? Actually, 127 effed up a lot of settings in my app. Default gov went to ondemand, min freq went to 1026, hot plug values were all screwed up... And the phone got laggy. I thought my videos are stuttering because of my uv or something so I went in to change it and see if that fixed it and that's how I found out it was gone. But why remove it? Just because the odd bonehead under volts his phone by like 300 and can't figure out why it's not stable doesn't mean you should remove it from the rest of us. I like undervolting. My phone runs cooler and I've had no issues. Just my opinion. I know full well that it's franco's kernel and he can do what he wants with it. But I'll stick with 126 for now and enjoy my undervolting goodness. ;)
[Nexus 4 Original Android Development] franciscofranco:
[KERNEL][GPL][N4] franco.Kernel - r127 | M1

Are you joking? I didnt remove any ****ing UV interface. By your description you were running stock kernel, stop blamming this kernel for something it didnt do, it gives false information to other users ;)
[Nexus 4 Original Android Development] rocklee80:
i was on r127 and i had the voltage control. On rc0 and rc1 i have it too, so maybe you clear franco apps settings before flashing a new kernel to load the kernel defaults.
[Nexus 4 Original Android Development] santeana:
Yes, I tried that. I also uninstalled and reinstalled the app. Nothing worked until I reflashed 126. Although, perhaps reflashing 127 again would have worked as well lol

Sorry, Franco. I did ask earlier, but after the retarded answers I received I figured it must have been removed and I felt stupid for not noticing. But I swear on everything holy I have been running this kernel since I bought my N4 in January.
[Nexus 4 Original Android Development] gerard_f:
Francisco Franco thinks the same

PS: Give me the money from the app :( xD
[Nexus 4 Original Android Development] Goku80:
apologies for the late reply was out my friend...instant and as others stated above go into kernel settings in the app and go to volume boost and play around with them....do not put it to high though as your ears will burst:D
[Nexus 4 Original Android Development] italia0101:
Btw anyone that wants epic smooth just try turning all cores on and down clock to 1.1ghz . feels so damn fast ...
[Nexus 4 Original Android Development] Bobtehblob:
Rc1 feels mint, I could go even more sensitive!
[Nexus 4 Original Android Development] naishadh:
I just flash Rc 1 should I inst any touch send app or its just enough to flash rc1?
[Nexus 4 Original Android Development] Anytime1157:
Enough by just flashing rc1 my friend :)
[Nexus 4 Original Android Development] Perks:
Hello all

I've been my fellow countrymen's kernel since January, when i received my n4

of course I follow this topic religiously, but newer felt the urge to say anything, I guess the search button works :p, and the fku works pretty good,

Anyway I usually wait for the nightly versions, but today after seeing this touch sensitive talk, I had to try it

I must admit that reading your comments I was thinking it was placebo, but because I'm using a screen protector, tried anyway and tested the sensitive before and after, In the developer options

I must say when in #127 I couldn't do better than .52 and after a lot of tries

in rc1 I got .45 right away

I guess this means something it's different and better :)

Portanto, obrigado pelo trabalho fabuloso Francisco, keep it up dude :thumbup:
[Nexus 4 Original Android Development] alphamod:
HELP!! i have a problem everyting was fine until today. i using franco kernel r122 and today i tried to flash rc1. i didnt know how to flash img file.

i tried with TWRP with no sucsses after that i tried with nexus 4 toolkit after i sucssefully done it the phone boot and ....

Type Password to Decrypt Storage. didnt know what to do and tried to do factory image from TWRP but it failed. somehow i managed to

wipe system to order to install new room but now theres new problem. google logo stuck and in TWRP i tried to wipe chace but dalavik chace failed. what to do now???
[Nexus 4 Original Android Development] ÜBER™:
Yeah I know the images. Just not off hand need to look at my themes to find the image I have em themed. I'll get them to you later today hopefully.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Martin_Ro:
What exact option did you have used in toolkit... what exact toolkit ?

normaly you would flash it with

fastboot flash boot

image_name

Sounds like you have flashed it to wrong partition...

what should work anyway (if you're still able to enter bootloader) is flashing factoryimage with fastboot.
[Nexus 4 Original Android Development] spicediablo:
The img file is meant for fastboot. Anyway try a factory reset. I'm not sure why u flash the ROM....

Sent from Mako⁴
[Nexus 4 Original Android Development] scream4cheese:
Kernel*
[Nexus 4 Original Android Development] Slymobi:
If you really need a flashable then the Easiest way to flash the .img from a recovery method is to extract a previous franco kernel zip and replace the boot.IMG with the new one (rc1) then archive it back to zip and flash via recovery.

Someone already made a flash able zip a few pages back !!!

Sent from my Nexus 4
[Nexus 4 Original Android Development] gerard_f:
Or copy the boot.img to the folder kernel_backups and restore it with fkernel.updater.
[Nexus 4 Original Android Development] lemmoned:
Well done Franco and many thx for sharing! :good:

Or he could've tried to type in the beautiful Terminal :

su
dd if=/sdcard/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
reboot

Cheers!
[Nexus 4 Original Android Development] spicediablo:
He said he installed a rom after kernel unless I misunderstood

Sent from Mako⁴

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

Now why didn't I think of that.... :o

Sent from Mako⁴
[Nexus 4 Original Android Development] wirtzpeitz:
I do run the kernel with stock settings. I've not changed a thing, not even the screen colors. I also run Touch Control and Greenify. The point is I also run those apps under r125 and yet the phone never dies on me.

Is there any log I can extract that would show events just prior to the phone turning off?
[Nexus 4 Original Android Development] naishadh:
How can I enable 4 core?I can't find option in Franco updater.
[Nexus 4 Original Android Development] italia0101:
Change the high load threshold to 0 in hot plug controls
[Nexus 4 Original Android Development] PhantomGamers:
I would recommend flashing to /dev/block/platform/msm_sdcc.1/by-name/boot instead, less likely to typo and hard brick your device I'd think...

Also the mount command shouldn't be necessary.
[Nexus 4 Original Android Development] lemmoned:
+1

You're clearly right! Shorter and more secure!
[Nexus 4 Original Android Development] yokuyuki:
Your charger is faulty.
[Nexus 4 Original Android Development] naishadh:
Thanks bro.all core now online.now how can I under clock 1.1 sorry for noon question.
[Nexus 4 Original Android Development] yethz:
I was about going to ask these query. Thankfully i read pages where i left off before.. Wheew.. A bit tiring when we go back to check the thread and then WOW, already 20's+ or 30 pages behind..

But its worth it to read through pages...

Anyhow, i am more comfortable on RC0, it feels stable for me and the performance and reposiveness on my phone's setup is great, i dont have the lock screen statusbar dropdown issues. I tried to replicate it many many times even restartedmy phone few times, left the phone for an hour then press power and swipe to unlock but still no issues.

RC1 suddenly rebooted my phone when on standby, no running apps doing intensive task, data off, wifi off.

Sorry, cant provide the logcat due to i clean wipe, an hour ago just to verify the responsiveness on RC0 and RC1 with a clean state..

°[ Proud user of LG-E960 (Google Nexus 4) ]°
[Nexus 4 Original Android Development] cheapskate88:
Suspend backoff wakelock

I've had suspend backoff decimate my battery for the third time. I turned off tilt scrolling as someone suggested before, but that did nothing to fix the problem.

Franco, do you have any ideas?

logcat and pictures attached

Thank you for you're help!
[Nexus 4 Original Android Development] Haomuch:
Your wakelock is crazy!
[Nexus 4 Original Android Development] cheapskate88:
And this isn't the first time :crying:
[Nexus 4 Original Android Development] bongostl:
Those of you getting 4+h of screen on time, what rom are you rocking?

I'm on aokp and am lucky to get 2.5.......
[Nexus 4 Original Android Development] jarjar124:
MiNCo! Well...are you using hspa+/LTE the whole time? if so maybe thats why?
[Nexus 4 Original Android Development] knapz:
I'd like to know too. Most I got was 3 but had sync off, 2g, auto brightness...
[Nexus 4 Original Android Development] CMNein:
Too many variables. On CM10.1 + r18 I got 2:40 over 41 hours (I slept for 18 hours of that time :good: ) and was at 25%. Sync on, but I was on wifi with the exception of 3 or 4 hours, and it was all light duty use. If I was gaming, or made any phone calls, etc... would have been a different story. I'm lucky to have phenomenal signal 24/7 as well, that makes a huge difference.

Makes more sense to compare with yourself rather than others.
[Nexus 4 Original Android Development] franciscofranco:
I don't have that issue at all!
[Nexus 4 Original Android Development] DroidRC1:
Alright ill flash back to r18 see if that fixes my issue

Edit: fixed! Flashing back to r18 now my phone charges with the screen on
[Nexus 4 Original Android Development] Vanhoud:
Paranoid android

Sent from my Franco'd Nexus 4

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

Flashback too r19 and see if it comes back

Sent from my Franco'd Nexus 4
[Nexus 4 Original Android Development] pedxing:
Aokp 12/20 build and r18 and I'm now getting 5+. Yesterday was good but today I'm already at 3.5 and i still have 45% left.
[Nexus 4 Original Android Development] DroidRC1:
Just flashed back and not charging with screen on again
[Nexus 4 Original Android Development] DroidRC1:
Latest unofficial AOKP from romanbb
[Nexus 4 Original Android Development] franciscofranco:
Ok I need a logcat when you plug the USB on and off please.
[Nexus 4 Original Android Development] DroidRC1:
Will do!
[Nexus 4 Original Android Development] CaspaTheGhost:
Can't fault any version. I'm visiting my parents and the signal up here is shocking! You can see that below.

But its OK as Franco has me covered.

Sent from my Nexus 4
[Nexus 4 Original Android Development] DroidRC1:
--------- beginning of /dev/log/main

I/dalvikvm( 2441): Turning on JNI app bug workarounds for target SDK version 11...

E/Trace ( 2441): error opening trace file: No such file or directory (2)

D/dalvikvm( 2441): GC_FOR_ALLOC freed 63K, 10% free 2483K/2752K, paused 11ms, total 12ms

I/dalvikvm-heap( 2441): Grow heap (frag case) to 3.622MB for 1048592-byte allocation

D/dalvikvm( 2441): GC_FOR_ALLOC freed 3K, 8% free 3504K/3780K, paused 14ms, total 14ms

D/dalvikvm( 2441): GC_CONCURRENT freed

EDIT: and now its charging with the screen on o_0 only thing i did different was a flashed with it unplugged and plugged it in with phone rebooted ...other times i had phone to talking while I was flashing the kernel
[Nexus 4 Original Android Development] kioshi:
Franco, i think i know what he's talking about...granted you dont have the phone physically yet, right?

I had the same problem when i use to have the GNexus on Verizon. SOME kernal nightys would make it where my phone is plugged in but draining 1% slowly..and when i flashed the next nightly or the one after it....the problem would disappear.

So far, i have not had that problem on for the Nexus 4 using Paranoid rom. AOKP might be the culprit also if the above user is using that...i used AOKP for HTC Incredible --> GNexus

EDIT: slow reply..AOKP could be the problem..
[Nexus 4 Original Android Development] Vanhoud:
He has had the phone for a while now lol

Sent from my Franco'd Nexus 4
[Nexus 4 Original Android Development] syncopy:
Not right! Franco has the phone! :thumbup:

Sent from my Nexus 4
[Nexus 4 Original Android Development] kioshi:
LOL..fail.

Its hard to keep up with the many things I'm into, phone hacking, cars, etc.

Thanks for filling me in.
[Nexus 4 Original Android Development] scream4cheese:
Minco V6!
[Nexus 4 Original Android Development] italia0101:
Go to freq/voltages then choose max frequency and choose 1.1
[Nexus 4 Original Android Development] Haomuch:
I have already figured out that my suspend backoff wakelock is related to special Wi-Fi router setting of the university network that it keeps sending broadcast data to the phone. You can also check whether your wakelock only happen in specific environment
[Nexus 4 Original Android Development] cheapskate88:
I was considering that, but I haven't started experiencing the problem until recently. I'm connecting to my same old wifi router. So I figured someone who can read the logcat might figure out what the problem is.
[Nexus 4 Original Android Development] trillo69:
I think that wakelock is ac charging related and happens when you plug and unplug your phone many times. If you click on the ? sign in BBS will give more info about it and how to solve it. Happened to me once but I don't remember how I solved it, I think I reflashed kernel.
[Nexus 4 Original Android Development] cheapskate88:
Charging related? Interesting. I can't say I've been particularly excessive with the plug-ins and outs, but I'll keep it mind... The only thing BBS recommends you do is monitor Chrome; specifically it's tilt scrolling. I've disabled it, and it's happened twice since.
[Nexus 4 Original Android Development] yethz:
And this is the touch-sensitivity i get on RC0 (PRS:0.26),

Really awesome. Thank u so much bro franco.

Its like im using diferrent kernel before with old touch driver init.d script, which franco kernel freezes on startup on my setup when E015 driver used..

But now franco's kernel will be my fav kernel after this touch fix...

°[ Proud user of LG-E960 (Google Nexus 4) ]°
[Nexus 4 Original Android Development] drawde40599:
U sure your phone shutting off or u having a SoD? Freeze those 2 apps one at a time see if fix issue id start with touch control, . I havent seen anyone else having your issue so doubtful its the kernel alone.
[Nexus 4 Original Android Development] diabolicalangle:
+1. I get the crazy high wakelock on Wi-Fi when I'm at my university, but not when I go home. I'd be down to do some testing if needed.
[Nexus 4 Original Android Development] Haomuch:
Yes. But the real problem is that even you can figure out the reason, you don't know how to solve it.
[Nexus 4 Original Android Development] Goku80:
Anyone have the rc1 zip or is M2 on its way?
[Nexus 4 Original Android Development] yokuyuki:
It might be an app. I've gotten wakelocks that aren't powermanagerservice from a live wallpaper that wouldn't sleep. Try uninstalling any recent apps that you have. A quick way to check if it's userspace rather than uninstalling a bunch of apps is to do a nandroid, clear your data, and see if the wakelock still persists.