yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] gajira:
I went back to the M3, whatsapp crashed 6 or 7 times and has not received messages times using r162.
[Nexus 4 Original Android Development] Testraindrop:
No offense, but app crashes are in 99.9% of the time not kernel related.

Gesendet von meinem Nexus 4 mit Tapatalk 4 Beta
[Nexus 4 Original Android Development] gajira:
Sorry i meant stuck or frozen. The only way to receive new message was to close the app and open again. Maybe it's not the kernel, but it didn't happen with the other versions of this kernel so I'm trying downgrading
[Nexus 4 Original Android Development] shengz:
Suddenly one question pop up in my mind after seeing your post.

Is there any script or tweak to make our phone 2G when not connected to data, but 3G when we on data?

Sorry if this sounds silly.
[Nexus 4 Original Android Development] Raijin:
I'm new here. My Galaxy Nexus memory chip died two weeks ago. It has been repaired in SAT and will be here in a few days. It will be for my brother.

I used the situation and I have bought a Nexus 4. It's an excellent device, the quad core and 2 gbs of ram are so much noticeable. It's so fast. I miss the deep blacks of AMOLED.

I have a question, is it possible to disable hotplug? I want to use the four cores.

Thank you!
[Nexus 4 Original Android Development] albundy2010:
2g and 3g are both data. That makes no sense.
[Nexus 4 Original Android Development] drawde40599:
u cant disable hotplug and it uses four cores. I dont no y people think franco made it 2 core

Edit: u can set high load threshold to 0 if u want and 4 cores will be on all the time, but your not going to notice any better performance IMO, just more battery use
[Nexus 4 Original Android Development] franciscofranco:
[KERNEL][GPL][N4] franco.Kernel - r162 | M3

Nothing to do with the Kernel.
[Nexus 4 Original Android Development] franciscofranco:
There is no commits related to USB at all since like forever.
[Nexus 4 Original Android Development] limeaide:
I think tasker can switch to 2G.

Read between the lines mate. The person means when on WiFi.

Sent from my Nexus 4
[Nexus 4 Original Android Development] aldyu:
It's a miracle then, or maybe it's not in the USB, could be something that's related to it. Will run more test but somehow I'm happy with this miracle...

Sent from my Nexus 4
[Nexus 4 Original Android Development] Floydfire:
It's normal that (I think) when on thermal throttle all the core goes online? Because I have set to 90 the high load for bard tale and after some time when I think it reach thermal goes all core online... Only asking cause I'm experimenting a lot with per app setting and just noticed that :)

I'm on latest r162...
[Nexus 4 Original Android Development] Arstoien:
Unfortunately only on some models and our Nexus 4 is not among them. If there was a script, that could be used to switch between 2G and 3G, then Tasker could run that depending on different conditions.

Sent from my Nexus 4
[Nexus 4 Original Android Development] drawde40599:
Would this help battery? I no 2g saves battery but would it matter on wifi? I don't anything about the subject. AOKP (and im sure many roms do) has a 2g toggle very easy access. Ima try it, thanks for the idea
[Nexus 4 Original Android Development] kino1122:
I think what was meant would be something along the lines of:

Screen on - 3G

Screen off, with no data transfer in background (eg. music streaming) - 2G

Screen off, but with data transfer in background - 3G

I believe an app like JuiceDefender did this?
[Nexus 4 Original Android Development] eluspo:
Hi bro! Would you be kind enough to post your color calib here?

Thanks!
[Nexus 4 Original Android Development] ammarii:
My phone always get heated up I never use it while charging but its still get hot even when browsing internet as well as playing games. I'm not advising anyone to under volt but its works for me quite well. Every time I flash an updated kernel I under clock to 1.3 and under volte it -100. I didn't face any problem with that
[Nexus 4 Original Android Development] drawde40599:
Do a FULL wipe, it will fix it. I have absolutely 0 heat with these new builds.
[Nexus 4 Original Android Development] Svid:
Hi,

When i used milestone 2 in system monitor under normal use i had only 1 code online (was good in battery terms).

Now, i'm using latest nightly and i noticed now 2 cores are online.

It supposed to be like this?

Threshold set to 70.

Did i missed something?
[Nexus 4 Original Android Development] ceejay83:
Yes, it's been like that for quite some time now
[Nexus 4 Original Android Development] resynx:
Think this is normal. Pretty sure that I read something a little back from Franco saying that either 2 cores or all 4 cores will be online now depending on what you're doing.
[Nexus 4 Original Android Development] Raijin:
Thank you friend. Working good.

I will try to test with hotplug enabled and disabled but, it's sure that there is no performance loss in daily use (animations, etc)? Maybe it help the heat problems.
[Nexus 4 Original Android Development] rjrjzozo:
"I'm new here. My Galaxy Nexus memory chip died two weeks ago. It has been repaired in SAT and will be here in a few days. It will be for my brother.

I used the situation and I have bought a Nexus 4. It's an excellent device, the quad core and 2 gbs of ram are so much noticeable. It's so fast. I miss the deep blacks of AMOLED.

I have a question, is it possible to disable hotplug? I want to use the four cores.

Thank you!"

Buy franco app. Load halfbreed color profile. Screen will be much better than amoled.....

Envoyé depuis mon Nexus 4 avec Tapatalk
[Nexus 4 Original Android Development] zorginho:
[MENTION=1536375]alex_dr[/MENTION]eik Raise the thermal throttle to 90 and in the hotplug control set 50 to high load value. U will get 21k on antutu.

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Original Android Development] drawde40599:
Fsync

Can Turning Fsync off cause gps settings to change on there own after a reboot? Like go from on to off . Trying to track down y it happens once in a wwhile and i think its fsync, i don't no whole lot about it and ive only see it effect google stuff anytime my phone has rebooted or failed
[Nexus 4 Original Android Development] Lownita:
When I get a notification light, it sometimes happens that it cycles with a red light in between, so: Blue,red,blue,red etc. I have not applied a red light to any of my notifications in the Rom, so I have no idea why this shows up (I had, but switched to another color for testing). Other than that, the phone is behaving normal. Am using latest nightly.

Any ideas where this red led comes from? Perhaps because I am not using fku beta?

Tapatalked from my Nexus 4
[Nexus 4 Original Android Development] ciprianruse88:
Maybe you where low on battery so the red light kicked in

Sent from Inferno
[Nexus 4 Original Android Development] Lownita:
No happens even while charging!

Tapatalked from my Nexus 4
[Nexus 4 Original Android Development] Bill Gamble:
Try the following:

echo "none" > /sys/class/leds/red/trigger

echo "none" > /sys/class/leds/green/trigger

echo "none" > /sys/class/leds/blue/trigger
[Nexus 4 Original Android Development] chielmi:
Do you use CM10.1? Since a recent CM nightly I also have this behaviour.
[Nexus 4 Original Android Development] Lownita:
I am using sabermod. But it uses the cm implementation for notification led I think!

Tapatalked from my Nexus 4
[Nexus 4 Original Android Development] juggies:
Nightly 162 uses a ton of battery on airplane mode overnight when Milestone 3 uses almost none. Any idea why this is?
[Nexus 4 Original Android Development] yellowdie:
You had something go wrong or a random rouge app. I used airplane mode with r162 and lost zero percent on 9 hours of sleep. The kernel is perfect. Something fluked on your end.

:)
[Nexus 4 Original Android Development] juggies:
Thanks for the response yellowdie. Will try and investigate further. :good:
[Nexus 4 Original Android Development] Arstoien:
The current LED features of the rom is interfering with some roms' LED colouring. Disabling it like Bill Gamble said will fix the colours but you won't be able to use the kernel led features.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Lownita:
You mean feature of kernel interfering with Rom led coloring? :)

Tapatalked from my Nexus 4
[Nexus 4 Original Android Development] Arstoien:
Yeah. Or the ROM led colouring bugging out because of the implementation of the kernel led. Don't know what's the better way of saying it but the fact is that with some roms the led colours are messed up if the kernel LED features are active.

Here's my solution if you want: I use Tasker to manually (with a shortcut) enable the red led (lights up in red if the cpu is throttling because of temp) when I want to monitor for throttling. Then the first time the screen goes off, it disables it so it shouldn't mess up the Rom LED colours.

Here's a ZIP with a small app exported with Tasker doing what I just said. After the screen goes off the app unloads itself from memory: http://db.tt/IxT3U9Z2

Sent from my Nexus 4
[Nexus 4 Original Android Development] mountainloafers:
I have a similar issue. Every reboot since one of the r150's my phone says android is upgrading. The apps do not optimize though. I have tried some fixes I found online and did a full wipe. I am stock rooted with few mods. Nothing works. When I flash r153 the message isn't there. Every kernel since, including m3, the message appears. It has something to do with the kernel. At least, for me is. :banghead:
[Nexus 4 Original Android Development] TheByteSmasher:
Do you use titanium backup or a similar program that merges dalvik with the ROM? 'Cause that'll do it...
[Nexus 4 Original Android Development] mountainloafers:
Yes. Used it since day one. It doesn't happen and hasn't happened sine the kernels after r153. Wiping dalvik does show the message with optimization as expected. Any kernel from r153 back is message free.

---------- Post added at 11:58 AM ---------- Previous post was at 11:57 AM ----------

One of the first fixes I tried was deleting TiBu. It didn't solve the issue.
[Nexus 4 Original Android Development] TheByteSmasher:
I mean did you select the option to integrate dalvik cache with the ROM or the automatically integrate feature... if you un-integrate reboot, reboot again, the second reboot should not have the upgrading message
[Nexus 4 Original Android Development] mountainloafers:
Have not integrated.
[Nexus 4 Original Android Development] TheByteSmasher:
Sorry then... I'm outta ideas.... that fixed it for me. :rolleyes:
[Nexus 4 Original Android Development] limeaide:
I think you said you were on stock. Have you thought about backing up all your stuff and flashing the stock image to clear out any gremlins that decided to take residence in your phone? On my old phone the dalvik wipe bug would kick in every once in a while out of no where. For me it was a app that was doing it. However Im not sure what one because there was several I quit installing at the same time because I never used them.

I suggest a clean start flash franco kernel and restore your apps one at a time until it happens again. It seems silly but it could just be a game that has some corrupted data that is causing this.
[Nexus 4 Original Android Development] Lownita:
Thanks! So with

echo "none" > /sys/class/leds/red/trigger
echo "none" > /sys/class/leds/green/trigger
echo "none" > /sys/class/leds/blue/trigger

I can disable all special leds from Franco and Rom led should be working as it should again?

Is there a way to do this from fku beta?

Tapatalked from my Nexus 4
[Nexus 4 Original Android Development] Bill Gamble:
Yes, until after your next reboot unless you put it in an init.d script.

No.
[Nexus 4 Original Android Development] TrenchKato:
Same issue. A clean flash fixed if for a while then it came back

Nexus⁴ Life
[Nexus 4 Original Android Development] Arstoien:
Yes, that's correct. No, Franco hasn't included it yet in the app. Download Terminal Emulator from the app store, run "su" (without quotes), and then run the three lines one after another to disable all of them.

No, there's no need to apply them on each boot. Running them only once is enough actually.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Lownita:
Really? Didn't know that's possible, always thought those echo commands would have to be run on every reboot:)
[Nexus 4 Original Android Development] Arstoien:
Yep, the command only modifies the file. Not all of them are reset on reboot though.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Lownita:
Good to know! But I guess they get lost when flashing a new kernel build?

Tapatalked from my Nexus 4
[Nexus 4 Original Android Development] N_lover27:
[MENTION=470754]Franco[/MENTION] can u please make a Externally Powered USB OTG enabled Kernel ? that would be great
[Nexus 4 Original Android Development] yellowdie:
He's already said repeatedly that he won't add OTG because it could cause unwanted issues.

But Ziddey makes the mod to Franco's kernel here: http://xdaforums.com/showthread.php?t=2181820.

Enjoy. :):D:good::laugh:

_______________________________________________

After a quick search, I found his last mention of OTG was from June 18th here:
[Nexus 4 Original Android Development] N_lover27:
Well wont that make any issue ?
[Nexus 4 Original Android Development] yellowdie:
I've used Ziddey's mod without any issues at all. But the point is, if there ARE issues, don't blame Franco. ;) Just try it and find out if it works for you. :cowboy:
[Nexus 4 Original Android Development] strainhunter:
I use "2g Auto Toggle" to switch to 2g when screen is off or/and WIFI is on.

Or you could use "3g Manager". It has some cool features too.

Gesendet von meinem Nexus⁴

@ <CarbonROM>+faux+franco.Kernel
[Nexus 4 Original Android Development] mountainloafers:
Thank you so much! Undoing actually worked. Funny thing, I don't remember ever integrating... But, it worked and I am grateful for your help. I thought I was going to have to live with it. I am still baffled as to why only the most current releases brought it on... ? :D
[Nexus 4 Original Android Development] i860:
Hi

I have some problems with 161 and 162, during my normal run ( same track since January ) Tunein Radio is cutting off every 20-30 seconds, also gps is disconnecting on Endomondo ( gps signal lost ). I never had this problems before. I uv -100 and uc 1.3 ( like all kernels before and no problems ) the rest is on default. Any ideas?
[Nexus 4 Original Android Development] ben_pyett:
for a start try it without uv'ing could be either a carrier data problem or a temporary application issue, remove the uv and reboot and test again
[Nexus 4 Original Android Development] i860:
Since January i never had any problems with uv or carrier ( i am with O2), yesterday i was on 161 and same problems, today i try 162 and same thing, i don't have any energy to go for 6.6k run now to test again ...
[Nexus 4 Original Android Development] ben_pyett:
merely a suggestion as I'm in UK on T-Mobile with no issues on either 161 or 162 with either tune in pro or absolute radio application which I'm on constantly when out of the house....not that that is any help to you though...
[Nexus 4 Original Android Development] drawde40599:
162

162 is a beast! Google now crap all on, Location on, brightness at 70, all google stuff sync on, OC to 486/1728 with Row, loggers off, fynsc off, everything else stock, aokp rom, still getting 3.5 hours on data bout 4 on wif witch is only about a 6% drop from not OC for ME. and its fast and smooth as hell aabsolutely no heat either :D Loving 162!! Definitely my favorite build to date.

Thanks for your time Franco!
[Nexus 4 Original Android Development] qpqpqp:
I'm fairly new to Franco kernel. What's the difference between milestone 1,2,3. Is it like updated version or different variation of the same thing. BTW I'm on paranoid android. Which should I use?
[Nexus 4 Original Android Development] tkalli:
m3 is latest milestone..
[Nexus 4 Original Android Development] limeaide:
I promise you it is a app that has some corrupted data. Until you clean flash and install EVERYTHING and DONOT restore any app data it will happen. I dealt with this on a different phone. Everything was fine a new update was released. I dirty flashed and something was causing the dalvik to be wiped each time I rebooted. Finally after a clean flash and not restoring any apps and only things like texts and call logs did it stop. I thought after a few days it was fixed so I restored a TiBup and it started to upgrade each time. I removed four apps I used once and never again and it stopped. That was last year so I do not remember what they were. But your problem is NOT kernel related it IS app related.
[Nexus 4 Original Android Development] blankit:
I'm having issues on m3. My signal completely goes off after about 3 to 4 days of use forcing me to do a full wipe and reflash. I get bars but no internet. Is anyone having this issue on m3?
[Nexus 4 Original Android Development] limeaide:
People have reported that they had problems uv'ing from one release to the next. Just because you had no problems in the past does not mean now one pops up. Try bumping your uv up a notch and the NEXT time you go for a run see if it happens again. However you could just as easily test it by walking around your home. Then you can rule out uv.
[Nexus 4 Original Android Development] TheByteSmasher:
No problem... just pass it on when you see the issue pop up again.
[Nexus 4 Original Android Development] TrenchKato:
Thanks. However I didn't restore any apps/data after my last wipe because I accidentally cleared my internal storage instead of doing a factory reset. ( took me days to get my phone back the way I like i

)

The problem did go away and I think it came back after a random reboot. Anyway it doesn't bother bother much. Wish I knew which app is causing it though.

Nexus⁴ Life
[Nexus 4 Original Android Development] drawde40599:
Its what I get in that amount of time I may get worse actually , but by end of day I'm over 4 hours screen on time so ..... And since 23 just came out u can't judge anything yet . I was getting over 4 hours be4 that fix and getting same after so..... I wouldn't set ur hopes to high
[Nexus 4 Original Android Development] mgear356:
For r23 phone indeed gotten less hot while playing nfs mw.. But also noticeable reduced frame rate..

Franco any plans to include different voltage table for slow nominal, fast and faster binning of processors?
[Nexus 4 Original Android Development] Xygod:
Operation Two Day Battery complete with r22! 3 hours of screen time and standard settings, no cutbacks, 5% left. You can see where I slept in the middle.

Should rename phone to Nexus 4 Maxx :laugh:
[Nexus 4 Original Android Development] alcurtis93:
This. I have the faster :)
[Nexus 4 Original Android Development] yokuyuki:
But I do use it all.

Yeah, I can't get remotely close either. Msm_hsic_wakelock is still taking up a huge chunk of my battery even on r22.
[Nexus 4 Original Android Development] Mikk36:
How big of a battery did your last phone have?

Mine did have a 1500 mAh versus the current 2100 mAh and I'm seeing an appropriate rise in the charging time.
[Nexus 4 Original Android Development] joshndroid:
Hey anyone got unvolting settings open.. I havmt looked till now as phone has been super stable so was going to coax a little UV but setting on boot is only there.. Maybe Franco still hasn't included it yet or I'm the retard ATM lol
[Nexus 4 Original Android Development] resynx:
UV hasn't been added yet.
[Nexus 4 Original Android Development] ReD_AvEnGeR:
On r23 games like gta or mc4 begin to lag. On r22 it is ok.
[Nexus 4 Original Android Development] ceejay83:
It's probably the new thermal control
[Nexus 4 Original Android Development] mundixx:
Maybe you have bad signal.. The wakelocks go up when i am in a location with bad signal :sly:
[Nexus 4 Original Android Development] republicano:
6.30 hours display on

well i managed to get a very good second run on r22, goal was to get a good display time with wifi on web browsing, adobe/pdf for reading,without compromising the buttery goodness, the ui was still acceptable, i noticed it started to lag at about 14%.

6.30 hours display on auto brightness

13 hours on

Paranoid android beta 8, cpu binn nominal

my stock was 4.30hours, so an extra 2 hours in this test was an improvement.

location settings off, google now,window,transition scale off, animator scale 0.5%

franco.kernel app

max cpu 1134mhz

min 384

governor control

hispeed load 60

hi speed freq 810mhz

cpu was not hot during this run.now time to try r23
[Nexus 4 Original Android Development] Vangelis13:
- Go to /sdcard/download

- Delete all other kernels you've downloaded

- Subscribe to this thread

- Sit back & enjoy the fireworks knowing that you don't need to worry about battery life & kernel choice anymore.

:thumbup:;):thumbup:
[Nexus 4 Original Android Development] evostevo1:
The only thing that I notice is some lag when scrolling through the widgets in the app drawer of stock launcher. R23
[Nexus 4 Original Android Development] galanakop:
Watts you rom???

Thanks...

Στάλθηκε από το Nexus 4 μου
[Nexus 4 Original Android Development] pac213:
My go_hispeed_load is 65 and hi_speed_freq is 594. I think it's good, I have no lags.
[Nexus 4 Original Android Development] franciscofranco:
Ok so this is simple: users treat the devices like consoles -> device gets hot -> complain to kernel dev -> kernel dev makes the thermal driver more aggressive to protect the device internals -> user treats the device like a console again -> complains that gaming fps maybe suffers a little bit over extensive periods of gaming because the device is trying to cool itself. Whats up? There are no miracles here, I can't make both happen. Even your ps3 or xbox gets hot, your computer gets hot, then the fans come up and the internal clocks get throttled to cool it down. Thats how it works.
[Nexus 4 Original Android Development] republicano:
running paranoid android beta 8,
[Nexus 4 Original Android Development] Keitaro:
I got my N4 a few days ago and this kernel was the first thing I installed along with franco's app. Whenever I run logcat in adb I get this error message...

"Unable to open log device '/dev/log/main': No such file or directory"

In the app, the "Turn Logger off" is unticked meaning that logcat should be enabled but, as seen above, it's not working. I have tried ticking it, trying logcat, unticking it, trying logcat again but I get the error in adb, even after a reboot.

Also, yes my N4 is rooted and I have allowed Franco's app in SuperSu.

Is this setting saved in a file somewhere, like the setting for Fsync is, so that I can manually edit it?
[Nexus 4 Original Android Development] blitz911:
Ok, just played temple run for 15 mins and watched an 18 min YouTube video in HD and couple other shorter vids and the phone hasn't gotten warm:thumbup: each nightly is getting better and more polished..oh, I'm on r23, auto flashed from r22..screen on time is about 3.5 hours, so far with about 20% left..can't say thanks enough..:D
[Nexus 4 Original Android Development] ben_pyett:
still sounds like some form of corruption, do you run default and have fsync on or have you turned it off?

A random reboot could theoretically cause application data corruption. Take full nandroid backup and then wipe and reflash Rom, gapps and kernel and see if it happens
[Nexus 4 Original Android Development] Testraindrop:
At the guys with the "optimizing Android" screens, look for .odex files (if you don't have a 100% stock rom) in your data/app directory.

If you find one, delete it (back up first).
[Nexus 4 Original Android Development] devdx:
Hi, using M3 from last 7-8 days..no lag / frame drops observed yet..very happy with it..just wanna know for this kernel any suitable task killer required for background apps? thanks (:
[Nexus 4 Original Android Development] gallardo5:
Don't use taskkillers with any kernel :) since Android 4.0 it is not needed and makes system instability and lags more than actually helping:)