yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] siealex:
No, no bootlooping and hardresets, just plain boot.
[Samsung Galaxy Nexus] siealex:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Does this kernel support SWAP?
[Samsung Galaxy Nexus] Mikes30000:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Confirmed as well especially on larger apps. 361 fixed it.
[Samsung Galaxy Nexus] jcmm11:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

I mentioned in a earlier post that for some reason I was also having trouble setting this via init.d. Same script run once I've finished booting works fine.

Tried sleep as well still no dice. I finally gave up for the moment and just set it to run at boot via Script Manager https://play.google.com/store/apps/details?id=os.tools.scriptmanager and it works fine.

May be ROM related (current ROM has options in settings for this, but I prefer setting it myself) and I'll look at it again eventually but for the moment it'll do.
[Samsung Galaxy Nexus] akash3656:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

The same happened to me while I flashed back to stock 4.0.4 for experimenting Android without Project Butter on the Galaxy Nexus.

Totally stock 4.0.4, was about to flash the last ICS Trinity kernel. I was transferring the kernel via USB MTP and then the speaker buzzed and the screen showed graphical corruption. Battery pulled, and ever since then the phone died. And totally dead phone, fastboot, download mode totally inaccessible. OMAP Flash could detect the phone but it couldn't bring it back to life. I tried with another battery, my phone still couldn't boot up. I also tried my battery on my friend's phone, his phone didn't start up either. So both my phone and battery is fried? I have no idea. And it also gets very warm if I plug it in to the charged but it shows no charging animation.

What is more saddening is that this happened a few hours after I got my phone back from my 2nd screen replacement.

I love the phone but I'm fed up with what hardware Samsung uses to build the phone. I already had 2 screen replacements (and they replaced the screen badly for both replacements), and a USB port that is getting loose. Also, Samsung service centres in my country also seems to do a crappy job on repairs too.
[Samsung Galaxy Nexus] bigbear6708:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Woke up to my alarm this morning on 364.. alarm was going off, screen would go on and off with power button, but phone was unresponsive. Had to pull battery to snooze my Alarm. All stock settings. First time this has ever happened. Ran 361 great for two weeks. This was after a clean install of updated rom i always use...market restore...no turanium.The alarm app was prob screwed up, as this kernel does no wrong...:rolleyes::confused:
[Samsung Galaxy Nexus] Adan.Mejia3:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

I use alarm every weekday and have had no problems with 364, sorry man.
[Samsung Galaxy Nexus] bigbear6708:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Was a market app.. heavy sleeper and need the" do math to snooze" option.. Lol... could be some bad data. Will test again Monday morning!
[Samsung Galaxy Nexus] Fenvarien:
AW: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

I have zero market problems on my and my wife's GNex. Both devices have >200 apps installed and updates occur quite frequently.

There's only a slight slowdown during the actual updating process, but this has always been the case.
[Samsung Galaxy Nexus] simms22:
faux sod, a typical example. an android 4.2.1 issue.
[Samsung Galaxy Nexus] Elganja:
my reasoning more or less to stay with 700-1200
[Samsung Galaxy Nexus] Thracks:
No. The Samsung battery driver does not report current.
[Samsung Galaxy Nexus] Danthemanz:
Im very very sorry if you took what i said as i a threat, it was never my intention at all, i swear.

I simply feel i will end up with another kernel because of the GPU OC, i dont really understand how its a threat because neither of us have anything invested in what i do with my phone :confused:

I love Franco's kernel, ive just found a way that others were superior in some ways and im giving feed back to the community on my own personal testing which found a difference in speed when pushing the graphics rendering of the phone.

We are running 720p on a GPU that has been pushing 800x480 most of its life, is it that hard to believe some users are pushing it to the max outside of gaming?

The GPU is what makes the Tegra2 tablets so choppy and to me the non OC GPU is a step towards it, obviously not to the same extent but im having the same occasional stuttering/low frame rate.

As is said, im sure most users wont notice, but that doesnt make what others do with the phone any less real.

Its totally upto Franco what he does, doesnt do or how many versions he wants to build, im simply trying to give him all the information from my testing.

Again, so sorry if anything came across hostile in any way, i would never intend to do that.

I love you all ;)

-Daniel
[Samsung Galaxy Nexus] Nebucatnetzer:
I already explained a couple of pages ago why I think it's better to use the lower frequency as well. I don't want to bring the discussion up again.

The main reason though is that I listen a lot to music so It's better for me to use the lower frequency because it uses less power.
[Samsung Galaxy Nexus] jhericurls:
I think you can lower your 350mhz slot a bit more. I'm running 350mhz @ 750 mV.

@Franco, I finally got around to purchasing your app, so show some support for the great work you been doing :)
[Samsung Galaxy Nexus] psycho2097:
thats tru,but use battery monitor widget and it gives an estimate based on actual percent drops n voltages.completely useless over short periods,but gets decently accurate after 60-90 mins idle time. useful for idle drain estimation ONlY.
[Samsung Galaxy Nexus] loudaccord:
Fair enough :)
[Samsung Galaxy Nexus] aron7awol:
Even if you used the same voltage for 350 MHz and 700 MHz, the CPU would still use about twice as much power at 700 MHz. In that case, you could almost certainly reduce the voltage at 350 MHz, anyway.

Here's a real world example from ro_explorer's power consumption tests: at 100% CPU usage, 350 MHz used 0.398 W and 700 MHz used 0.932 W.

Edit: Even a small reduction in voltage makes a big difference because voltage is squared in the power consumption ratio.
[Samsung Galaxy Nexus] onyxogen:
BUT: And that's the question I'm asking myself for a long long time (now I'm asking all of you - including the kernel developers) : Since the AMOLED screen uses so much battery - is it even measureable in terms of battery time to squeeze the last mV out of the Kernel? Let's say 70% of the power consumption is due to the screen. The remaining 30 % may be optimized. And with a superb tuned kernel you can save maybe 1% of that 30 %. Then you have a few minutes more left every day ... :confused: Is it worth it?
[Samsung Galaxy Nexus] ljwnow:
Oh come on. Who is abusing this good guy?
[Samsung Galaxy Nexus] ellesshoo:
This... all this monkeying over a few mV is so insignificant and at the same time destabilizing and a huge source of user complaints and belly aching posts about how their phone is rebooting or attributing problems caused by user UV to other features. I had no problem with Franco not having user controlled UV settings. At this point I think it would be a good idea to have two builds that are exactly the same except for UV control and a gentleman's agreement that you don't complain or report bugs unless you experience them running the version with no UV control.

Yes I know, you could just simply leave it on default settings. But you're kidding yourself if you think even 75% of the people who post here have that kind of restraint or self control
[Samsung Galaxy Nexus] Felixpau86:
I'm with the person above.
[Samsung Galaxy Nexus] franciscofranco:
Totally true, but when users undervolt they are on their on, I don't answer to problems caused by UV at all, that's been my policy for a while now.
[Samsung Galaxy Nexus] psycho2097:
Can I get a feedback on this Franco? Is what I am observing correct? How do I go back? I tried reflashing 7.1,but no avail. Would this be a rom problem?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
I'm seeing a lot better battery with the latest 13.1 so I really can't help with that, and plus I don't support older versions, it's been a standard since I build android kernels. If you're seeing high Android OS percentage it's apps problem, if it's not apps problem then I strongly believe it to be a rom problem. If I can't replicate bad battery on my device that is always running with almost vanilla roms with almost no apps, then I'm 99% sure that what other users have is rom/apps problems.
[Samsung Galaxy Nexus] MFD00M:
LISTEN TO THIS MAN!!

i just learned the hard way

i UV 100mv across the board and got stuck in endless bootloops. fastboot wouldn't even recognize device anymore =(

THANK GOD for ODIN

im on toro btw

EDIT

i should mention, 13.1 was was running great with good battery life on 1200max 350 min ondemand until i decided to UV myself

Def will not be UV'ing anymore
[Samsung Galaxy Nexus] franciscofranco:
Exactly! People need to think a little bit before undervolting as every device is different. Yesterday I was testing some values and I too got into bootloops, it just happens, but that's entirely on users responsibility ;)
[Samsung Galaxy Nexus] MFD00M:
no doubt...i accepted those risks the minute i did fastboot oem unlock and pushed a custom recovery ;)

hey at least we know the UV interface is actually working now! LOL
[Samsung Galaxy Nexus] psycho2097:
thanks for the reply.... I appreciate that. But I was kinda interested in the extra battery drain of newer versions compared to 7.1. I had the same apps,nothing new. Just rom and kernel changed...anyhoo,I m trying 13.1. Pretty good reports...awesome job! :-)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] sishgupta:
I'm perfectly willing to sacrifice a little bit of battery life for more stability. I don't touch the UV interface at all.

I like that I've been given the option though. That's why we're here we want more features/development than stock.
[Samsung Galaxy Nexus] osm0sis:
The ROM probably sets it with a sysctrl.conf or another script on its own, this was happening after your init.d script so you never saw it change. To gain control delete sysctrl.conf or add a sleep 35 before the readahead of the init.d to make it perform it later. If 35 doesn't work, keep bumping it up by 5 until it does. Deleting the ROM's stupid script would be easiest though.

That's great that you guys have confirmed it but we need logs to figure out why - /proc/last_kmsg from after the reboot occurs. Make sure logging is on in f.Ku; if it was off then reboot before you try to reproduce since turning logging back on doesn't take effect until the next boot.
[Samsung Galaxy Nexus] joaquinf:
i haven't had any issues on the latest release. I've tried to replicate the market random **** with no luck. Any known way to reproduce the issue?

So far everything has been rock solid and smooth as usual :)
[Samsung Galaxy Nexus] galakanokis:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Yeah, I'm starting to wonder if the problems I was having weren't more ROM related. Switched back to CM last night and I have had no issues since. But my slow down semi hang ups stopped after SuperSU was updated.

No issues charging or with SOD's. Are people under volting again?

G
[Samsung Galaxy Nexus] bigknowz:
Download Link

Is there a problem with the server? Can't load http://minooch.com/franciscofranco/Galaxy Nexus/JB/JB-4.2.
[Samsung Galaxy Nexus] Wynnded:
It was goofy a little while ago, maybe give it a little time and it will sort itself out.
[Samsung Galaxy Nexus] bigknowz:
Back Up

Thanks, links working again, got the download.
[Samsung Galaxy Nexus] BuTuCuTz:
Camera problem

I was taking a few photos and the phone stopped working. I had to do a battery pull. Tried it again and the same result. Is this a known problem of the kernel? I am running on Franco 364.
[Samsung Galaxy Nexus] cucisan:
AW: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Had this freeze while saving photosphere picture (only tried once)

normal pictures and Video worked though

using r364 and stock 4.2.1
[Samsung Galaxy Nexus] siealex:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Downgrade to r361 and try again. I had no freezes on r361 but three in two days on r364.
[Samsung Galaxy Nexus] osm0sis:
Yup. Should be fixed for most, if not all now:

:good:
[Samsung Galaxy Nexus] wrext0r:
Well I'm trying some settings especially for the lower frequencies. But for the time I'm just plaing with the CPU voltages, the two others (IVA and core) are current at stock.
[Samsung Galaxy Nexus] whitedragonz83:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Undervolting isn't possible still. Franco hard coded the current voltages so any change is placebo.
[Samsung Galaxy Nexus] ~Phil~:
AW: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Is there a possibilty to get an notification of there is a new Kernel Version online?
[Samsung Galaxy Nexus] doomed151:
But my phone froze when I put 1100 mV for 1228 MHz.
[Samsung Galaxy Nexus] Khrushy:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Well it froze for some reason other than the voltage change, because they're still hard coded...
[Samsung Galaxy Nexus] doomed151:
I've read about something being hard coded somewhere but I don't believe the voltage values themselves are hard coded.

Tried setting various values to the 1228 MHz slot, and I think voltages are being applied properly.

1225 mV (default) -> OK

1220 mV -> OK

1250 mV -> OK

800 mV -> Insta-freeze

If changing the values really does nothing and the freeze was caused by something, I'm curious of what caused the freezing.
[Samsung Galaxy Nexus] shreddintyres:
install this, then whenever you want to check you fire up the app and if there is a new version you can just download it from the app
[Samsung Galaxy Nexus] wrext0r:
Well it wold be nice to know if the're really hard coded or not before I spend time for testing :P

What ist the reason thaht they're hard coded? I mean there is a lot of potential to save battery life...
[Samsung Galaxy Nexus] Kapetan:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Did you lovered almost 50% voltage and then come here to ask why your phone has frozen?? C'mon ppl, don't act like kids..... Chips NEED voltage to work properly.... Don't mess with that if you aren't sure what are you doing.
[Samsung Galaxy Nexus] whitedragonz83:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Read a bit. He was trying to prove if undervolting was hard coded or not. He is proving it isn't hard coded, though I don't see when Franco took it out.
[Samsung Galaxy Nexus] doomed151:
I guess you're not getting the point. Try reading the last 2 pages.
[Samsung Galaxy Nexus] malaroth:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

The reason is that there was such idiotic misuse of the voltages and lack of accepting responsibility for changing something that WOULD make your phone freeze that Franco couldn't get any REAL feedback about problems through everyone complaining about SOD and hotboots. Once he hard coded them he was able to fix the real problems

Franco r364
[Samsung Galaxy Nexus] galakanokis:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Pretty sure UV is back in as I can insta-crash my phone by going to low. Very repeatable as well. No other crashes in over two days. Once SuperSU is updated on your phone it should be much more stable. This is why I asked if people were UVing again as I have had zero issue on a stable ROM and 364 with the updated SuperSU.

G
[Samsung Galaxy Nexus] Angelakaro:
I know this kind of feedback is useless,but the only thing i can say is that i haven't any problem with play store nor super SU (stock rom,r364)
[Samsung Galaxy Nexus] irminsul:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Battery life is so relative. I was at home today for the whole day, so only on my home WiFi network. Screen on for 2 hours and still sixty percent level on 2000 mah battery.

On a normal work day when I travel a lot and use ****ty WiFi at work it takes so much more power. I hardly do 2,5 hours on battery during the day.

So if anyone is complaining about battery consumption: check the networks you're using, it makes a difference as day and night.
[Samsung Galaxy Nexus] siealex:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

No, no uv at all, but freezes in Market...
[Samsung Galaxy Nexus] osm0sis:
I think we decided UV was back since people could freeze when they lowered it. Check Device Monitor.

Market should be fine once you update SuperSU to 1.04 and reboot.
[Samsung Galaxy Nexus] gaich:
UV is certainly back, one can easily change it, just try! But the sad thing is that poweramp stutters are back too...:crying: Testing right now with other kernels on the same frequences and observing that max 1228. min 1924, screen-off 729, interactive (intact) can save the situation using many of them, including 361, but with 364 the stutters still remain...
[Samsung Galaxy Nexus] nuwan32:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

By switching to undervolting, I just saved 1 hr of screen time of battery
[Samsung Galaxy Nexus] whitedragonz83:
I call shenanigans! Not even sure you could prove this mathematically to be true.
[Samsung Galaxy Nexus] siealex:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

What's the connection between market and supersu???
[Samsung Galaxy Nexus] Khrushy:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Apologies if others can UV. I'm definitely getting nothing in device monitor, and can set good old 1mv without crashing - but that could just be me, we encountered that bug before on my phone.
[Samsung Galaxy Nexus] osm0sis:
Yeah that's a bit much.. UVing shouldn't save that much, even if you do have exceptionally strong silicon, which nuwan32 does - I seem to recall he was the only one who could UV 192MHz to 675mV stably.

Read back a few pages. I posted Chainfire's release notes.
[Samsung Galaxy Nexus] nuwan32:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Oh yea forgot to mention I uc'd to 729 and laxed the governor settings a little
[Samsung Galaxy Nexus] RevengeFNF:
But saving battery its not all... The phone will not get so hot if we UV.
[Samsung Galaxy Nexus] bartolinio:
me also caught up with today's freezing of when updating applications from market, and the first freeze, reset the device once a second attempt to update and re-freeze of :/
[Samsung Galaxy Nexus] osm0sis:
Bro. SuperSU.
[Samsung Galaxy Nexus] bartolinio:
yes, I've seen this information, it might be the susersu

but I have not seen the information that has already been solved somehow? I have the latest version of supersu
[Samsung Galaxy Nexus] marcuso:
about these freeze issues during market-updates:

I now also followed the discussion about SuperSU playing a role here .. I am also on latest SuperSU (which is supposed to have some fixes related to that) but still I got those freezes with 364. I went back to 361 which did not have these issues and right now I am testing/experimenting with Leankernel which also seems to be fine here.

(but of course I do prefer beeing on Franco again ;)

So at least some relation to the kernel (364) seems to be there still.

When I have some time I´ll try to get back to 364 and enable/get logs during crash/freeze reproducing.
[Samsung Galaxy Nexus] ptmax13:
Could someone please clarify me this:

With the last nightlies of franco for 4.2.1, do I still need this [MOD] [GNEX] BEATS+XLOUDER! for my Gnex? I only need to have a louder speaker not the other enhancements.

Thanks and sorry for the noob question...
[Samsung Galaxy Nexus] siealex:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Try to remove supersu completely (but do not remove su binary).
[Samsung Galaxy Nexus] Angelakaro:
You can install that patch and uninstall the apps that comes with it later. Easy ;)
[Samsung Galaxy Nexus] mrasquinho:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Sorry for the off topic, but I had to share this!

Look at the sign!

@ Wax Museum, Madrid - Spain

:D
[Samsung Galaxy Nexus] doomed151:
At first, I thought the picture was irrelevant until I enlarged it. :p
[Samsung Galaxy Nexus] alexdemonumber3:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Alright, I've been running r364 since it dropped. I haven't had one SOD or freeze of any kind, and that's with super heavy UV'ing. Everything is silky smooth. Battery life is still good. And basically its perfect. And the sound enhancements are killer. I'm running it at 1300-384, interactive (default config) and deadline. No complaints whatsoever.

I'm running it on the Overdrive 4.2.1 final release.
[Samsung Galaxy Nexus] irminsul:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

That's not the best guy to be compared with ;)
[Samsung Galaxy Nexus] malaroth:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Running stock (winning) 364 freq 1305/384. Forget about battery, here's my CPU usage. Granted the weekend was my video game time so I used Wifi hot spot all weekend.

Franco r364
[Samsung Galaxy Nexus] nuwan32:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

As I stated earlier, after some simple under clocking and under volting, I got over one hour more screen time, compared to the 2.5 hours I usually get. If anyone wants, I'll post my governor control and uv settings as well.
[Samsung Galaxy Nexus] 11768:
Yes please :good:
[Samsung Galaxy Nexus] nuwan32:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Min freq - 384

Max freq - 729

Voltages

384 - 750

537 - 800

729 - 875

governor settings

Ahd - 30k

Go_highspeed - 95

Highspeed_freq - 537

Min_sample - 45k

Timer_rate - 30k

Target_loads - 85
[Samsung Galaxy Nexus] Sik-1:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Oh nice I use the same voltages :D:thumbup::cool::beer:
[Samsung Galaxy Nexus] SayWhat10:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Which governor you using? On demand? Interactive?
[Samsung Galaxy Nexus] nuwan32:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Haha nice

---------- Post added at 10:55 PM ---------- Previous post was at 10:55 PM ----------

And I use interactive governor and deadline scheduler
[Samsung Galaxy Nexus] osm0sis:
The volume boost in the kernel has only ever been for headphone jack only. If you want anything else louder you need a mod.
[Samsung Galaxy Nexus] J-Hop2o6:
What theme is this?
[Samsung Galaxy Nexus] Bl4ck3urn:
this one http://xdaforums.com/showthread.php?t=1881702
[Samsung Galaxy Nexus] bigknowz:
Music Stutter

So I am having the same issue with Rocket Player. I listen to music on my way to/from work. Stutter happens when I have a signal, when I go into the subway and turn on Airplane, there is no stutter. I'm trying to figure out if TCP Congestion or Scheduler is more important in resolving the issue. Considering the no signal, no issue, I'm leaning toward TCP. However, the scheduler may have more work trying to give time to radio related tasks. Any and all thoughts appreciated. Setup is

noop

2048 read ahead

interactive with stock settings aside from go_hispeed_load, which is 80

On other kernels, I found SIO was best, and didn't have good luck with ROW.
[Samsung Galaxy Nexus] doomed151:
Try 256 - 512 KB read ahead.
[Samsung Galaxy Nexus] J-Hop2o6:
Do you have the Google Play link?