yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] DowntownJeffBrown:
Sorry iPhone 5 lol

Sent from my Nexus 4 using Xparent Blue Tapatalk 2

---------- Post added at 12:59 PM ---------- Previous post was at 12:49 PM ----------

Mine was very low the first half if the day then when I went to my parents house it jumped up to 6 min 34 sec within 3 hours from 56 sec the first 4 on this battery cycle. The only difference was my signal is worse at my parents then at my house which has a tower within eye sight. So I'm thinking signal strength is a huge part of why some get more wake lock than others. BTW before n22 I would have been close to 20 min or more at this point so Franco defiantly reduced it down to 1/4 of what it used to be.:thumbup:

Sent from my Nexus 4 using Xparent Blue Tapatalk 2
[Nexus 4 Original Android Development] cobyman7035:
help please! i don't have connection to google servers anymore, im on 4.2.1 franco r72 still, no playstore, no youtube videos loading

help!!!

i tried to reflash r72, no luck,,, do i need to wipe dalvik cache?

i tried unitstalling and reinstalling google playstore apk, no luck :(
[Nexus 4 Original Android Development] franciscofranco:
http://xdaforums.com/forumdisplay.php?f=1909
[Nexus 4 Original Android Development] madgooner2810:
Phone started rebooting on r155 so I reverted to 154 which was stable, that also started rebooting so now I'm back on 151. No last_kmsg is created also. Is anyone else suffering from similar issues?
[Nexus 4 Original Android Development] franciscofranco:
IF theres no last_kmsg then maybe its not a Kernel problem? Stop undervolting? I dunno, too vague.
[Nexus 4 Original Android Development] madgooner2810:
It's all stock settings, maybe it could be a ROM issue. The only thing that confuses me is that 151 is absolutely stable whereas everything after causes reboots. I will investigate further. Would a log help?
[Nexus 4 Original Android Development] franciscofranco:
last_kmsg helps... theres no changes in between releases that could add random reboots though.
[Nexus 4 Original Android Development] madgooner2810:
Had another reboot, got a last_kmsg. It's in the link. https://www.box.com/s/gqrz0t5st53nwdo9nrou
[Nexus 4 Original Android Development] Danny.ns:
Just want to report that r155 has been flawless on my end.
[Nexus 4 Original Android Development] franciscofranco:
Not Kernel derp, something told the device to reboot, and it wasn't on the Kernel.
[Nexus 4 Original Android Development] steviewevie:
If you are undervolting then it is perfectly possible for a seemingly minor kernel update to push you from "stable" to "unstable". Undervolting is not an exact science, and any slight change in the way your phone works could mean that you could start getting problems (e.g. using certain frequencies for longer times).

Sent from my Nexus 4
[Nexus 4 Original Android Development] The Gingerbread Man:
Franco you should remove these guys right to undervolt like you did for nexus 7, galaxy nexus. I'm sure you recall how many less bug reports came though as result of that
[Nexus 4 Original Android Development] jebatkun:
or maybe you can limit undervolt such as -100 or -125?
[Nexus 4 Original Android Development] deltatux:
Signal keeps dropping on Franco Kernel r155 and Franco Kernel Supercharged r155 (supercharged is based on regular Franco kernel code). Have no choice but to revert to r154 >.<"...

deltatux
[Nexus 4 Original Android Development] madgooner2810:
Just to be clear, no undervolting has been done by me. I'll probably do a full wipe and see how it goes. Maybe something is corrupt ROM side.
[Nexus 4 Original Android Development] aliensmille76:
I have the same issue, but doesn't depend on the kernel, had the same reboots completely stock!

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] lorolouis:
Change the your phone Android ID (generate a new random) by Titanium Backup or so.

All Google services will start recognizing your stuff again.

Why you (I and others) are posting this trouble and solutions here, BTW?
[Nexus 4 Original Android Development] cobyman7035:
thanks i will that that random ID by TBU, phone is rebooting now

nope still doesn't work! just grey icon, not blue, so i m NOT connecting to google servers! :(
[Nexus 4 Original Android Development] lorolouis:
Some thoughts, or a joke if you want ... about this (in) famous signal drop:

First, imagine your phone has 4-5 radios (WiFi, GPS, Cell, BT) + GPU chip + CPU chip ... all in several sq. inches space.

All of these devices are generating frequencies in range 0.3 - 2 Ghz.

And even worst ... these frequencies are jumping all around to provide you as smart as possible dynamics and power saving ...

Isn't that too impossible to get an interference or disturbance between each other?

Or ... you think all in this world is now only a software and Franco is responsible :) for it ...

Just run a CPU monitor and watch the WiFi and Cell bars signal ....

What happens when you slide and second CPU turns on?

Are they remain full or they loose some strength temporarily?

Regards.
[Nexus 4 Original Android Development] madgooner2810:
The reboots were not Franco.kernels fault. I feel like a retard. Flashed a few other kernels to check, it's a problem with the ROM or some rogue app.
[Nexus 4 Original Android Development] Net.silb:
It's like a deja vu of a deja vu of people complaining about freaking signal drops, Google servers and WiFi problems...

Guys, [MENTION=3292224]franciscofranco[/MENTION] has already responded hundreds of thousands of times to these complaints...

The answer to your problem is probably one of the following:

WiFi driver is stock.

All 3G/HSIC/data/signal stuff is a problem and we are waiting for Google to fix it.

Gray bars only means you're not connected to Google servers, but your WiFi works just fine.

So please lets get back to actual kernel development related discussion, real bug reports and for crying out loud people, read the damn FAQ!
[Nexus 4 Original Android Development] LibiSC:
Francisco you should put the FAQ in your app.... With a name like bug fixer or something :cool:
[Nexus 4 Original Android Development] zellleonhart:
Hi all, I am using r155 with PA 3.60, UV by 125mV. Before r155 (I presume), I do not have this problem but just today I had 2 random reboots. It happened when I tried to unlock the phone using touch control and it did not respond. then the screen lights up with a totally dark background and rebooted. Happened twice today but never happened before.

Attached is the last_kmsg. Anyone can help me to analyse? I don't really know how to analyse the log. thanks!
[Nexus 4 Original Android Development] mkfort:
1) Don't ask for help when you are undervolting.

2) Touch Control is not supported here.
[Nexus 4 Original Android Development] zellleonhart:
Thing is it never happened before when I am with this UV for like 3 months. I don't think it's touch control though, because one time I unlocked using the power button and it rebooted. I just want to know the reason it reboots so that I can change my way of using it.

If it is touch control or UV, then I can change.. But I can't read the last_kmsg :(
[Nexus 4 Original Android Development] Floydfire:
I just had a 2g data drop, on 155 only reporting, no complaining! Is the first time that I notice drop...

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Original Android Development] :
Why don't you try uninstalling touch control and increasing UV to -100mv? It helps to investigate solutions to your own problems. If it persists try a full wipe and reinstall your ROM
[Nexus 4 Original Android Development] zellleonhart:
I am already doing that but I really love touch control. I cannot replicate this reboot so I don't know if the core problem is really touch control/uV or other stuff.

Fine then. I have no choice do I. I can't read it so I have to try and error.
[Nexus 4 Original Android Development] Dan53:
[ 4486.920226] dpm_run_callback(): power_suspend_late+0x0/0x54 returns -11

[ 4486.920256] PM: Device power.0 failed to suspend noirq: error -11

[ 4486.922210] PM: noirq resume of devices complete after 1.891 msecs

[ 4486.924071] [Touch E] [touch_i2c_read 139] transfer error

[ 4486.925811] PM: early resume of devices complete after 1.586 msecs

[ 4486.925811] PM: Some devices failed to power down

[ 4486.926177] [Touch E] [touch_i2c_read 139] transfer error

[ 4486.928283] [Touch E] [touch_i2c_read 139] transfer error

[ 4486.928954] [Touch E] [touch_i2c_read 139] transfer error

I know you say you can't read it but what do you think this means? it's the error (Google is your friend). Usually the error is near the bottom of the file. Thanks for the log anyway. It's better than what most people give when they have a problem
[Nexus 4 Original Android Development] Cuzz1369:
Undervolting and touch control????? You have absolutely no right to complain of reboots in this thread.

Carbonized and francofied N4
[Nexus 4 Original Android Development] PelegK:
r155 Works great !

Thank you, Franco !
[Nexus 4 Original Android Development] kerngehirn:
[MENTION=3292224]franciscofranco[/MENTION]:

The German translation is not entirely correct. The word load has two meanings.

1. Load as a verb; to load some settings.

2. Load as a noun; to stress something.

The correct German translation would be

"Laden" ... not "Belastung".

sent from my nexus4 with PA, not speaking English natively. so you're welcome to correct me anytime.
[Nexus 4 Original Android Development] Danny.ns:
Its the exact same in swedish translations.

I believe that before there was two different strings (im just guessing here), both saying "load" in english. But in swedish, one said "belastning" and the other "ladda". It worked fine up until recently where the word was changed.

I'll have a look in LinkedIn to see if someone has miss-translated it. But anyway, know that it is not francisco translating for all languages so he cant help you :p
[Nexus 4 Original Android Development] ROFLkopter:
It feels good to be on franco.Kernel once more. Loved it on my Nexus 7 with PA3+. I did freeze my N4 by undervolting too much when I first flashed it though :/ Lol

<(:0)OOO> A wild Weedle appears!

Sent from a Paranoid Nexus 4 with XDA Premium
[Nexus 4 Original Android Development] oSandmaNo:
Just flashed your kernel with a CM- halo kang. (Cr-droid)

Awesome job. Phone is butter :D
[Nexus 4 Original Android Development] MrMagic:
Seriously? I've been using Franco's kernel for a few weeks now and I never had problems with my phone losing data and asking for the PIN over and over again. Since this behaviour started at version 155 I think we are entitled to "complain" about this. It's obvious that the 3G/data changes that were implemented in 155 are causing this IMHO.
[Nexus 4 Original Android Development] roughavoc:
So no hope of getting Franco + MIUI so time to move onto another Kernel. Hope the kernel carries on strong!
[Nexus 4 Original Android Development] schnuffdroid:
i'm also back to r154 because of the data drops.

r154 is more stable in data connection than r155 or the previous r666 image.

i can feel no difference when using different baseband. i'm on the 48 modem atm, it's a little better than 54.

beside of this, my n4 runs great in terms of battery and performance! :)

*nexus4*aokp*franco*
[Nexus 4 Original Android Development] franciscofranco:
No MIUI support, ever.
[Nexus 4 Original Android Development] Pure Drive GT:
Undervolting

Well I've undervolted a couple of times but never gave a lot of thought to it and also never overdid it. Now more for fun reasons i want to see how good/far I can go. I don't really want to just make everything as low as possible. more I want to set voltages for each frequency seperately. is it a good idea to give higher frequencies a higher voltage than lower frequencies? I would be thankful if anybody could also link me to a good undervolting guide (maybe for the nexus 4 specificly).

Thanks in advance!
[Nexus 4 Original Android Development] italia0101:
I was testing a miui ROM port and it had Franco kernel already
[Nexus 4 Original Android Development] Beremus:
Sometimes, FKU bugs. I need to reflash the kernel to get all.my settings back. (Specialy the Voltage and Hotplugs ones). My settings goes to Ondemand, min freq 1048(or something like that). I tried to clear data and reboot, but the only thing that worked for me was to reflash the kernel. Weird.
[Nexus 4 Original Android Development] Brokenme23:
Here's some good read about undervolting also you can use an app called StabilityTest (ROOT optional) you know.. for stability test.

good luck :good:
[Nexus 4 Original Android Development] franciscofranco:
No, FKU doesn't bug. What happens is that you probably flash a rom and forget to flash the Kernel afterwards. When you flash a rom it will overwrite my Kernel and load stock. Kinda obvious.
[Nexus 4 Original Android Development] kszaq:
Are you using LibiSC's kang or the "official" version of this kernel? I had very bad signal issues with r155 from this thread, flashed official r155 and voila! - problemz gone. :victory:
[Nexus 4 Original Android Development] abdi7451:
complete newfag here. franco.Kernel-Milestone.2.zip or franco.Kernel-Milestone.1.zip? I'm running XenonHD 4.2.2
[Nexus 4 Original Android Development] baza14:
Try r155. It's unofficial milestone 3. :D

Odesláno z mého Nexus 4 pomocí Tapatalk 2
[Nexus 4 Original Android Development] strainhunter:
When choosing from Milestones

i would use Milestone2 its newer...

But when choosing from franco.Kernel generaly i would use the nightlies^^
[Nexus 4 Original Android Development] thebryceee:
Well in that case...
[Nexus 4 Original Android Development] cyberon:
Two small bugs Francisco, the PA Halfbreed profile is inverted and when you open the slide the settings tab the word "Updater" becomes "updater", without Caps. :)

Cumps
[Nexus 4 Original Android Development] Arstoien:
Check the first post here: http://xdaforums.com/showthread.php?t=2155495 From my experience the 1.5GHz can't go as low as the rest (I haven't tested anything above 1512 MHz). The limit of the other frequencies for my device is actually mostly linear. I tried going lower on the mid frequencies as suggested in the post but had some reboots and had to go back to almost linear. I've also been experimenting today (for fun mostly) and it seems I can run these values: 384 to 702 MHz -150 mV; 1188 -175; 1350 -150; 1512 -125. I'm telling you not so you can use the same values but to see how the curve goes. My suggestion is to see what's the voltage limit of your chip and just go one step higher.
[Nexus 4 Original Android Development] KingBeike:
I have also Data drops with 2g while surfing With wifi ! So i have no data connection for a few seconds. Using t-mobile in germany, this happens since 155
[Nexus 4 Original Android Development] ciprianruse88:
r155 is super close to milestone.I even lowered max freq to 1.18 ghz and it's freaking smooth.:cool::thumbup:
[Nexus 4 Original Android Development] manulemaboul:
Just had one single signal loss in 9h, certainly not kernel related.

R155 actually improved things as it seems, saw it sending an MMS in actual H+ for the very first time from my couch in my livingroom today.

Usually on edge and ocasionally finding umts lol.

Franco, you've broken my poor signal ! :p

Just kidding, just to say everything is more than OK regarding signal and data here :).

155 is the smoothest so far, it is for almost each nightly actually :p

Still rocking my 4h SOT, and sleep drain is better, probably because of the better signal, maybe not only :).

Envoyé depuis mon Nexus 4
[Nexus 4 Original Android Development] franciscofranco:
Thanks for the heads up, just corrected it. Your post also remembered me to add the SGS4 profile, which I just did.
[Nexus 4 Original Android Development] Testraindrop:
Franco yesterday you wanted to post a list of what you are planning to do...

I'm still curious what you have in mind for the future :D
[Nexus 4 Original Android Development] Godaemon:
I'm experiencing random Hot Reboots don't know if its kernel related its the first time though could someone plz help me ?? Here's the last log :

http://pastebin.com/nDgB135X

Thanks

Edit : Those are the last lines

Sent via NeXuS 4 / Xda-Developers App
[Nexus 4 Original Android Development] yokuyuki:
Somewhat late, but while I see the well-meaning behind the removal of kernel wakelocks, I don't agree with it. In the past, I've had faulty apps keep my phone awake via kernel wakelocks yet it doesn't show in userspace wakelocks. It was really weird, but I confirmed it multiple times by installing and reinstalling the app.
[Nexus 4 Original Android Development] Beremus:
Nop. I didn't flashed any roms since PA 3.15. Only flashed your kernel. Not a ROM issue here.
[Nexus 4 Original Android Development] albundy2010:
It's not a issue period. In your last post you said when after you flashed a rom the settings are borked or whatnot

They are not. When you flash a rom it overwrites whatever kernel you are currently running and uses the one included in the rom.

PA has a stock based kernel with mpdesicion which also runs on demand. It it nothing at all to due with the kernel or Franço's app.
[Nexus 4 Original Android Development] Beremus:
I guess you can't read. Last time I flashed a ROM was ~2 month ago. It happened when I flashed r155.
[Nexus 4 Original Android Development] franciscofranco:
I'll post on G+ in an hour or so, I forgot yesterday!

Something weird must've happened because I'm sure that instead of flashing r155 you flashed stock Kernel, because Ondemand and min 1026MHz is typical mpdecision.
[Nexus 4 Original Android Development] Beremus:
I downloaded it directly from FKU.
[Nexus 4 Original Android Development] albundy2010:
You are mistaken. What you're describing is simply not possible. No other way to put it, It just cant happen.

You're right about me misreading your first post about it. I combined it in my head with francos original response to it. My bad.

By the way I just looked into the pa thread. You mentioned in there in a post a couple days ago about using halo. That is not the pa 3.15 rom from two months ago. The first halo build release was may 4th and was 3.5. You also said you were flashing and reflashing gapps due to sms related stuff.

Again there is no bug. Its something you did. Franco told you that and now you're lying to him and me in this thread.
[Nexus 4 Original Android Development] bleuwave:
Deleted
[Nexus 4 Original Android Development] blankit:
Anyone know why the increase in call volume and headphone volume option s aren't applying when I set them? On r155.
[Nexus 4 Original Android Development] Luigiesin:
BTW... For those having signal loss, try using radio 33 with the audio fix... Since I reverted two weeks ago, I've never had a signal drop with any of the builds Linaro or Franco main.

Give it a test to see if the radio issue has anything to do with the combination of the radio & patches in the kernel.

Sent from my Rock & Roll Nexus 4 \m/

ROM: PA 3.60

Kernel: Franco r1222-Linaro

T-Mobile
[Nexus 4 Original Android Development] copi:
hi [MENTION=410271]fransisco[/MENTION]franco

why on ur fku doesn't have touch accuracy setting, led setting and mpdecission toggle? it would be complete if u add that, afterall touch accuracy is ur signature right.. or maybe u dont want us user will make a mess with the value haha,, ok ok
[Nexus 4 Original Android Development] Luigiesin:
Mpdecision is history man... This is all about hotplug and dynamic governor scaling which you can uncheck already with the app.

Sent from my Rock & Roll Nexus 4 \m/

ROM: PA 3.60

Kernel: Franco r1222-Linaro

T-Mobile
[Nexus 4 Original Android Development] LibiSC:
Lol?

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Original Android Development] copi:
hmm.. that actually make sense since he used his own hotplug code,, and fku is only for franco kernel then.. ok ok for mpdecision
[Nexus 4 Original Android Development] Mr Djoegoe:
I've been trying other kernels the last 2 weeks but after flashing r155 I know that franco's kernel is the best for me :) No more weird lag when I unlock my phone or when I clear the resent apps and it feels real fast and smooth :D

I'm using the latest PA, r155 and .54 never had an signal loss :thumbup:

Verstuurd van mijn Nexus 4 met Tapatalk
[Nexus 4 Original Android Development] DesertVelo:
Reaching out to anyone who has been experiencing bluetooth disconnects/connects when using a bluetooth headset (LG Tone HBS700) on R155. During phone calls (or playing music to a bluetooth speaker), I will be momentarily disconnected (about 4 seconds) and then brought back online. I will be testing earlier builds but I do not recall having the connection interrupted prior to R155. Any feedback would be helpful to determine if it is CM or recent kernel build.
[Nexus 4 Original Android Development] ptesmoke:
I'm a convert. this kernel is insane. here to stay. Franco if you got my email about the app don't worry its sorted..my transaction got cancelled be cause I uninstalled the app by mistake. bought again. no worries. THANKS FOR #BEASTMODE kernel :)
[Nexus 4 Original Android Development] TwinkyOfHope:
I've been using Franco's kernel since the Galaxy Nexus, it's just been so kick ass and he is so involved in it. There's just no competition. I was actually disappointed that the Nexus 4 didn't have a separate Kernel Updater app to buy. My old purchase took care of both my phones and gave me so much control. I was ready to shell out my little dollars with no hesitation. Thank you Franco!
[Nexus 4 Original Android Development] buizon:
Hi,

I have been thinking if this is possible in this kernel to have 4 cores online in a certain load in a certain cpu freq? like in minimum load we have 2 cores online but when we reach a certain high load it will up 4 cores with minimum freq of 1ghz then if it hits again a much higher load, 4 cores will still be online but freq will increase gradually per load?

Sorry if its a little bit confusing

Thanks in advance!
[Nexus 4 Original Android Development] thebryceee:
AFAIK you can only set it using High Load Threshold in governor settings.
[Nexus 4 Original Android Development] Arstoien:
This is how it's currently working. The hotplugging onlines all 4 cores when the load has been high for a certain period of time. Then the governor scales the cores' frequencies according to the current load. If you want to control how "difficult" it is for all cores to come online, you can change the High Load Threshold under Hotplug control in Franco's app. If you want to control the governor, you'd have to uncheck "dynamic scaling" and change hispeed_freq, though I'm not sure if that's currently doing anything. Franco said once he got tired of it and I think he might not be using it at all currently – if anyone could confirm?

And fyi "dynamic scaling" is changing the governor values depending on the number of working cores, so when 4 cores are all working, it changes the gov.values to make the experience more responsive. But the values can't be changed by the user (with the exception of input_boost_freq). If you want to use custom values, you've got to uncheck dynamic scaling.
[Nexus 4 Original Android Development] buizon:
Thank you guys for all the response!
[Nexus 4 Original Android Development] limeaide:
Which one is the sgs4 profile?

Sent from my Nexus 4
[Nexus 4 Original Android Development] :
Is there any way to use the kernel app if you don't use gapps anymore. I've just flashed a new rom without gapps (Want to get rid of all the spying on me) but now when I try to start the app, it doesn't work anymore because it says it can't verify that I bought it (Which makes sense since I don't have the play store installed anymore). Any ideas?
[Nexus 4 Original Android Development] eths83600:
I don't think there's any solution to that.

Since as you know it the app uses play store every time you lunch it to verify if you paid the app or not
[Nexus 4 Original Android Development] fozzie:
Install just the Play Store.
[Nexus 4 Original Android Development] kerngehirn:
Lunch :D

sent from my nexus4 with PA, not speaking English natively. so you're welcome to correct me anytime.