yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] SahilC:
'Yeah, I'm using deadline, and everything is super smooth, but it seems the battery is dropping a lot when I'm using the phone (obviously, lol)

But in all seriousness, is there anything I can do? Maybe I should let things settle for a while.

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

'Yeah, I'm using deadline, and everything is super smooth, but it seems the battery is dropping a lot when I'm using the phone (obviously, lol)

But in all seriousness, is there anything I can do? Maybe I should let things settle for a while.

---------- Post added at 06:00 AM ---------- Previous post was at 05:58 AM ----------

'Yeah, I'm using deadline, and everything is super smooth, but it seems the battery is dropping a lot when I'm using the phone (obviously, lol)

But in all seriousness, is there anything I can do? Maybe I should let things settle for a while.
[Samsung Galaxy Nexus] The Gingerbread Man:
Clear Franco data, use defaults apart from hi speed gov control to 729mhz and set on boot. Perhaps change headset volume to +1 other than that stock values on latest osmod should be as good as it gets tbh bud
[Samsung Galaxy Nexus] SahilC:
I'll definitely be here till I get into college.. Won't get a new phone till then :P

By the way, sorry guys. My Internet connection is screwing with me. Some reason it sent my posts a few times. Tried to clean things up :P

---------- Post added at 06:45 AM ---------- Previous post was at 06:04 AM ----------

Yep, did it! Except I'm on deadline. Somehow it feels better.

Yeah, I don't mind, I'm tired of trying to Suck out every last second of battery life, haha. I'm just gonna enjoy the buttery smoothness :D
[Samsung Galaxy Nexus] ilarrain:
Pull-request: dm crypt: backport version 1.11.0 to get support for allow_discards

[MENTION=3292224]franciscofranco[/MENTION]: I've created a pull request on your github repository to backport dm-crypt 1.11.0.

This change provides allow_discards. This enables android 4.3 built-in TRIM feature when using android encryption feature, thus greatly reducing lag and improving responsiveness.

I've been testing this change for 2 months on my only phone without issues. You can also see some successful reviews on CM's gerrit.

I've also compiled latest franco.kernel with this mods for anyone to try: http://goo.gl/z0S7Qm. It is causing frequent reboots. The same patch has been tested for 2 month without issue over CM's kernel. Will do some more testing.
[Samsung Galaxy Nexus] jackyhk02:
How to enable WiFi pm fast in r392? The option is not shown in trickstermod.

Tried the old init.d method but the file does not exist.
[Samsung Galaxy Nexus] thegtfusion:
If im correct, the feature is not working on 4.3.
[Samsung Galaxy Nexus] carlinho77:
A lot of reboot with Vanir !!!
[Samsung Galaxy Nexus] ilarrain:
You are right, the same patch has been tested for 2 month without issue over CM's kernel. Will do some more testing.
[Samsung Galaxy Nexus] nonoperez:
Testing on latest cataclysm, fast and smooth as hell, no reboots in 2 hours

Edit: everything was ok until I tried to make a phone call, it always reboot. :(
[Samsung Galaxy Nexus] ilarrain:
I've been testing the patches over the official CM kernel for 2 months without issues, no reboots whatsoever. There is something wrong on my build over franco.kernel, I don't know if there is a conflict between this patches and franco's, or if I did something wrong in my build.

BTW: [MENTION=3292224]franciscofranco[/MENTION]: the config you use to build your kernel is not in your repo, i had to extract it from /proc/config.gz after booting your release. Please fix this (GPL issue, I think).
[Samsung Galaxy Nexus] Edward Stanbury:
Well its Tuesday and my rock climbing expedition is over :( ah well had a blast of a time haha update flashing as we speak just catching up to all you guys :P also ran into some charging port mishaps but all is good for now I hope haha
[Samsung Galaxy Nexus] sd3993:
Ok so i've overclocked my device using [MENTION=4544860]osm0sis[/MENTION] 's values as a base. But honestly i don't really see the point. If Thermal Throttling is enabled the CPU is automatically underclocked within a few minutes of heavy usage. And if Thermal Throttling is disabled the device gets pretty damn hot(and reboots if by any chance it does cross 110 SoC temp). :/

Anyone have any alternates views on this?
[Samsung Galaxy Nexus] osm0sis:
What are you talking about? I have my device "overclocked" to 1305MHz from Google's 1200MHz, but the board is actually rated at up to 1500MHz. It never goes above 50 degrees Celsius on a hot day while gaming, and the thermal throttle doesn't kick in until 70. :rolleyes::)

Basically it just sounds like you're mixing up all sorts of facts, so I don't know what to tell you, other than read. ;)
[Samsung Galaxy Nexus] metalspring:
Lol, I always run my phone at 1500+ depending on what my current kernels closest frequency is (I like my CPU to run at the speed it was designed for) and it never gets too hot unless you really push it on some benchmark app (which is specifically designed to stress the CPU)
[Samsung Galaxy Nexus] skizofrenic:
that's strange....

i always thought franco was quite hot...

let me explain.. i have your same voltages (checked from your signature, just a +25 on mpu) but i always go at throttle temp easily.

and i m on 1200 not 1300 mhz

example: deer hunter , after 2-3 min game it starts stutter like hell (temp over 70---> throttle e cpu goes down down down )
[Samsung Galaxy Nexus] castaway1:
isnt TRIM enabled by default on all 4.3 ?
[Samsung Galaxy Nexus] ChazzMatt:
He's saying this is trim with encryption enabled. Maybe it's not enabled by default when using encryption?

_________

Sent from my Galaxy Nexus i9250
[Samsung Galaxy Nexus] razi914:
Dont know its my kernel or Rom, but play store speed is ridiculously slow
[Samsung Galaxy Nexus] The Gingerbread Man:
That would be neither it'd related to network connection speed. Data is slower than WiFi
[Samsung Galaxy Nexus] razi914:
No, downloading other files from the internet is fine, only play store is slow
[Samsung Galaxy Nexus] The Gingerbread Man:
Sounds like play store is having a bad day. Busy servers. Nothing to do with rom or kernel etc
[Samsung Galaxy Nexus] sd3993:
I'll explain what i mean. I too run my device at 1305MHz with Thermal Throttling disabled. It runs fine. But after 20 mins of having the SoC temp is around 80°C. right?20 its around 84°C. But on 1536 and higher the temp easily crosses 90°C and the phone reboots. With Temperature Throttling enabled the cpu freq starts fluctuating after around 5 mins of gaming. The battery temperature never crosses 46-47°C in any situation. What i'm asking is this behaviour normal?

[MENTION=4544860]osm0sis[/MENTION] Throttling does take place based on SoC temp right? I don't understand how ur phone never crisses 70°C? :(
[Samsung Galaxy Nexus] osm0sis:
Something wrong in both of these cases. First don't use my voltages; they're not there for you to copy, they're there for you to compare once you've properly figured out your own. Old thinking would say you may be forcing the CPU to work harder at a lower voltage, driving up the heat, and I guess this is a possibility -- though we had a TI engineer in here at one point who said it's all or nothing and I'd tend to believe him. ;)

As for the other temperature trouble, don't turn off the throttle; most don't. What app are you changing settings with? Run my Kernel Emergency Reset Zip to make sure you're not getting any crossover, and only keep the one you use installed. Some people on grouper reported high heat merely from having SetCPU installed at the same time as f.Ku, not even any settings set.
[Samsung Galaxy Nexus] skizofrenic:
ofc i did not simply copied your Volt.

i tested mine with tons of reboot due to low setting. and i finally found a rocksolid with volt like yours. (just mpu unit need a liiiiitle more volt than your)

in fact at idle or with simply thing, temp is 33-35 (idle) ---->40-45 normal task

but the moment i open a game ..... tooooo hot.

example: i used phone as navigator this summer..... 3 hours in car with phone at 65-70° (throttle at 70 go back to 65 and back again to 70 etc etc etc)

i ALWAYS use your reset tool when i change kernel :)

ps: underlined part: u mean that TOO LOW voltage could result in a TOO HOT cpu?

if yes.... i 'll try immediatly !!!
[Samsung Galaxy Nexus] shriom_manerker:
haha dudethings are crazy in wherei live, (india) im whatsapping people here (vanir 4.3 rom) and phones not even overclocked, i saw it hit 75 *C , and im like dafuq is going on ? apparently it heats up a lot under moderate 3g signal and when outdoors, :( so i wanted to request [MENTION=3292224]franciscofranco[/MENTION] to include custom vlues for temperature throttle, i prefer to keep the temperature <65*C, and oh btw ambient temp is 28*-35*C here :\
[Samsung Galaxy Nexus] sd3993:
1) I've already run ur emergency reset zip before flashing ur fixed version of r392.

2) I haven't copied your voltages. I came across then just yesterday and noticed they we're more or less equal to the ones i set for my phone through experimentation.

3) If I don't turn off temperature throttle games like nfs most wanted lag like hell after sometime.

4) Any voltages above 1250(with TT disabled) makes my CPU temp cross 110 within a few minutes causing a reboot.

I'm using Trickstermod Kernel Setting.

Guess I'll be stuck with 1.4GHz forever. :(

Unless i move to Antartica :D :P
[Samsung Galaxy Nexus] osm0sis:
Yeah, it's a possibility. Try everything at default voltages for awhile and see if it's being still weird. I can do some medium gaming with physics calcs like Frisbee Forever and RUA2 and it does heat up but doesn't hit the throttle point, or if it does it doesn't cripple the device.

Holy poop, yeah that's pretty wild! Good request, I know he has bumped it up a bit recently on mako to 75 or so since the calculation there made it lower than he originally thought.

Haha! There is a common saying that "not all silicon is created equal" which could be at play here. Sad but true.
[Samsung Galaxy Nexus] sd3993:
I live in India too! Maybe the ****ty hot and humid climate affects the phone temperature. Although that's still too high :/
[Samsung Galaxy Nexus] skizofrenic:
well, honestly at default i get hot quite immediatly.

lowering volt helps me but maybe thruth is in the middle.... i mean from stock volt i go -25 x3 times on cpu (tot -75)

i'll try -50 and i'll report

question to wise ppl.

is there any Thermal past on our chip ????
[Samsung Galaxy Nexus] ilarrain:
It is, but AOSP's encryption uses dm-crypt, and allow_discards (on which TRIM depends on), wasn't introduced for dm-crypt until kernel 3.1. All Jelly Bean supported Nexus devices are at least on kernel 3.4, except Gnex, which is stuck on kernel 3.0.
[Samsung Galaxy Nexus] Vekhez:
N7 2012. 3.1.10 kernel.
[Samsung Galaxy Nexus] skizofrenic:
here some test:

first of all i noticed that throttle starts at 75 C° (i was sure it was at 70....)

tool: system tuner for cpu temp & stabilitytest for... test

CPU test stock voltage: (1200 mhz) 10 mins: 75 C° and starts throttle

CPU test underclock: (1200 mhz) 30 mins: 66 C° and... i stopped

CPU+GPU stock voltage: (1200 mhz + 512 mhz) 1-2 min: 75 C° and starts throttle

CPU+GPU underclock: (1200 mhz + 512 mhz) 15 min: 68-70 C°

would be reeeeeally nice an option to set our desired throttle temp.

for example i'd like to set it to MAX 65.

And i'd love also to be able to set gpu freq.

i mean, i know that with 512 is stable.... but Lean has this option.

and franco MUST be better--->the more, the better---> must have this option :)

noone else would like to be able to set it ?
[Samsung Galaxy Nexus] osm0sis:
It's a

max

. If your device isn't doing anything intensive GPU stays at 153MHz. Francisco tried variable user-set max in the past but it reduced stability.
[Samsung Galaxy Nexus] ChazzMatt:
Right. As osm0sis said, Franco kernel has GPU ramp up to 512Mhz as you need it. It doesn't stay red-lined at 512Mhz all the time. It's speed on demand.
[Samsung Galaxy Nexus] finesse:
Has anyone lost root permission, since flashing r392 on a 4.3 ROM?
[Samsung Galaxy Nexus] Edward Stanbury:
nope :P
[Samsung Galaxy Nexus] osm0sis:
Not if you flash my fixed version. ;)

Edit: Actually regular r392 should work fine too; I forgot Franco worked around the problem by adding back the install-recovery.sh service. Between that and init.d it should always work. :good:
[Samsung Galaxy Nexus] Edward Stanbury:
bet me to it ;) haha, I think i need to update my sig ohh the laziness
[Samsung Galaxy Nexus] blackdub370:
I feel the same
[Samsung Galaxy Nexus] rickh925:
Same here. I reflashed the 01262012 ROM and it booted just fine. I tried 14.1 and 14.2. Nandroid running now, but I'm going to try 13.1 with today's ROM and see what happens.

Just checked the 01262012 Fits ROM and it also has problems with the Franco 13.1 kernel although I don't get the continuous boot animation, I get the com.android.phone process has failed to start. Press OK. same thing comes up again.
[Samsung Galaxy Nexus] franciscofranco:
There's nothing I can do about that. ****ing CM releases are alphas, buggy as ****, I wonder why anyone would like to use something so broken. I'll take a look into their ramdisk to see what kind of ****ing magic they're cooking.
[Samsung Galaxy Nexus] rickh925:
What ROM are you using? Just curious as I've been on CM ROMs or kangs for 2 years on my N1 and am always looking to see what other more advanced people are doing.
[Samsung Galaxy Nexus] ro_explorer:
I just flashed #14.2. So far .. it booted fine. Let's see how stable it is.

I'm using 350-1200, on demand, no UV, no OC.
[Samsung Galaxy Nexus] franciscofranco:
I'm using AOKP, never gave me a single problem, thats why I don't change roms like I change my underwear. If it's working why change it? ;)
[Samsung Galaxy Nexus] ro_explorer:
Reporting back. With #14.1 until now I would have had at least one gsm signal drop and maybe one reboot.

Currently, with #14.2 none of these problems occurred. It seems fine.

So, the short term test is PASSED .. let's see the long term test.

That why I'm "stuck" with bigxie's ... after I flashed it first time and I saw it running fine, I didn't tried anything else.
[Samsung Galaxy Nexus] DynamicRam:
Working fine on the latest KANG with me

EDIT : Turned out i was on 01252012 KANG it is indeed not working on 01262012
[Samsung Galaxy Nexus] dyndragon:
I know it's an alpha, and really it's not even an official nightly--someone just was compiling it for us on their own on the side. I was just reporting it for those who also run the CM9 kang.

Anyway, I'm the same as you--first ROM was CM, always worked fine (still does now, except for this last nightly), and never bothered to switch. It just happens that my first ROM on the GN was CM ;-)

Thanks for looking into it anyway. I'm gonna try what Dynamicram just suggested.
[Samsung Galaxy Nexus] DynamicRam:
neither franco's nor GLADOS kernel works on the latest KANG
[Samsung Galaxy Nexus] mazubo:
Better battery stats is all you need! A lot of people are using battery widget from the market as well :)
[Samsung Galaxy Nexus] modstorm:
14.2 working great for me with AOKP #20. I can now use the same UV that I had on 13.1 (didnt work on the previous 14.X versions) and so far had no crashes.

Thanks for the great work on this kernel :)
[Samsung Galaxy Nexus] Ben74:
i'm on franco 13.1, and bigxie 8. no major issues, and for the past two nights, i've left my phone off the charger, with wifi on and set to never sleep, and have lost only 1% overnight (7-8 hours). pretty happy about that! i haven't messed with UV, OC, governor, or anything like that. fully stock settings.
[Samsung Galaxy Nexus] Stockmoose16:
This has been asked, but not sufficiently answered: this kernels appear to be great for idle time, but because you've set the current at 700/1200, the battery dies quicker when the phone is in use. I get that the higher clock speed allows processes to finish faster - allowing the phone to get back to idle state as quickly as possible - but isn't this all at the expense of usage time?
[Samsung Galaxy Nexus] dyndragon:
I tried your method, does not work unfortunately. I've been watching the logcat while booting and there's some junk going on that I can't interpret:

I/DEBUG ( 116): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr deadd00d

Along with a bunch of stuff crashing and dying.

Anyway, I'll not clog up the thread here. Franco, if you can figure it out, that's great--but it's not your responsibility so let's keep this thread on topic. This is definitely a problem specific to the CM9 kang that imfloflo is maintaining the thread on.
[Samsung Galaxy Nexus] Arrio:
Without OC.

With OC.

1200mhz is better than 13500mhz?
[Samsung Galaxy Nexus] franciscofranco:
You're device is being throttled, maybe too hot, then it throttles cpu's speed down to prevent damage.
[Samsung Galaxy Nexus] modstorm:
I think you have something wrong cause I get 6400 without OC and around 7000 with OC
[Samsung Galaxy Nexus] Cutting-TM:
Hi francisco

Can you pls tell me the unstable UV settings from 14.1. They work perfectly for me
[Samsung Galaxy Nexus] Arrio:
Glitchy graphics with low fps on gpu oc.

(4-9fps)
[Samsung Galaxy Nexus] ChazzMatt:
Over in a ROM thread where I participate, there's some complaints about losing root over various issues -- flashing kernels among them. 4.3 changed a lot of security stuff. The fix -- which the ROM lead developer does not like -- is flashing SuperSU in recovery. He prefers superuser. He says SuperSU runs roughshod over a lot of the new security features in 4.3. I don't care. I want what works. :rolleyes:

Even in the newest version of Titanium Backup, that developer now recommends using SuperSU instead of superuser.

And Franco kernel now works with SuperSu very well.

So, I keep SuperSU 1.65 stored in my download folder and I flash it in recovery when installing new ROM. There's a link in this post for the standalone APK:

http://xdaforums.com/showpost.php?p=23427715&postcount=1

You can also download from Google Play, but for recovery you need standalone apk you can put into the storage you can access in recovery.
[Samsung Galaxy Nexus] SahilC:
Do you guys force GPU rendering?
[Samsung Galaxy Nexus] shawnaye:
Well i do, forcing GPU rendering makes my WhatsApp load quicker, could be just me though.

Although i do remember seeing someone else mentioning about it somewhere.

Hah.
[Samsung Galaxy Nexus] The Gingerbread Man:
It used to make images not load on tapatalk. I have it enabled
[Samsung Galaxy Nexus] evilssj4:
hello everyone! I just flashed osmosis's r392 version of this kernel and my phone is not going into deep sleep :( I am currently using Vanir 4.3.1 ROM and before I flashed the r392, my phone was going into deep sleep with the kernel that comes with Vanir. Any thoughts on this? any help will be appreciated.
[Samsung Galaxy Nexus] The Gingerbread Man:
Check your apps it is not a kernel error
[Samsung Galaxy Nexus] Phazmos:
Always. Probably the biggest thing to help gui smoothness. But, I hear some apps don't like it. Fortunately none that I use.
[Samsung Galaxy Nexus] evilssj4:
ok so I wiped everything and started from scratch again but during that process I flashed osmosis r392 instead of just letting the stock kernel boot up. I was setting up my phone all over again and I checked on franco kernel updater again and now the phone is deep sleeping! hmmm, not sure but maybe this GPS trick fix was what fixed the problem? The thing is tho, is that I didn't actually go into Google maps at all so the gps shouldn't lock in right? Not sure if this a problem in 4.3 and 4.3.1 ROMs, but I've encountered that problem before where my phone wouldn't deep sleep and I had to turn on GPS, go into maps, wait for gps lock and exit maps, turn off gps and it will finally deep sleep. Only problem is after I did a reboot I would have to do that all over again in order for my phone to deep sleep, which gets annoying. So right now, I'm afraid of rebooting my phone just to check if it was that or if I reboot will my phone still deep sleep haha
[Samsung Galaxy Nexus] The Gingerbread Man:
Honestly buddy its not kernel related, if it were then in the nicest possible way more people would be complaining than just you. A couple of suggestions is turn off your GPS if your not using Google navigation as you don't need it for basicly anything else. Also install wake lock detector or baeeter battery stats and see what they show. All of use have different apps and set ups, the likely hood of anyone having the same device and apps as you is probably smaller than you winning lotto lol Things like facebook, Google current, or most things which have push notification often hold wakelocks (prevent sleeping) in order to keep their *hitty service running.
[Samsung Galaxy Nexus] evilssj4:
oh no, I'm not saying the kernel is the problem I was just saying how weird it is. I installed better battery stats again to see if there is anything that could prevent a good deep sleep or drain my battery, but so far the phone is going into deep sleep. Thanks for the help though. I will most likely reboot the phone later on tonight and see if the problem persists and with BBS I'll try to find out what app could be causing it.
[Samsung Galaxy Nexus] The Gingerbread Man:
Other than the fact your on 4.3.1 which I didn't initially take in I would still say its down to app as by some miracle Franco and Os literally managed to future proof this kernel so it boots on an unofficial android version for the phone lol But back to being serious, install some wake lock detector app, charge your phone to full, unplug it, give it say 8 hours of normal usage and then perhaps post a couple of screenies here and someone could help if not then check a forum for which ever app you went for.
[Samsung Galaxy Nexus] evilssj4:
ok cool sounds good.:good:
[Samsung Galaxy Nexus] SahilC:
Alright, I turned it on! Lets see how it goes.

---------- Post added at 12:51 PM ---------- Previous post was at 12:48 PM ----------

Hey guys,

So I'm running stock deodexed with the latest osmod. Stock settings, but hispeed_freq is 700, and I've changed colors.

No other mods.

For some reason, I'm getting constant lag on the quick settings toggle.

Everything else is perfectly smooth, but when I press the button in the notification tray to switch to quick toggles, it lags terribly.

Any thoughts?

---------- Post added at 12:52 PM ---------- Previous post was at 12:51 PM ----------

Hey guys,

So I'm running stock deodexed with the latest osmod. Stock settings, but hispeed_freq is 700, and I've changed colors.

No other mods.

For some reason, I'm getting constant lag on the quick settings toggle.

Everything else is perfectly smooth, but when I press the button in the notification tray to switch to quick toggles, it lags terribly.

Any thoughts?
[Samsung Galaxy Nexus] Edward Stanbury:
i think google just stuffed something up, it happened to me on stock rom with stock kernel also. atm im using psx rom and its gone not sure what causes it :\
[Samsung Galaxy Nexus] osm0sis:
To gauge the wakelocks you'll actually want to not use your device for as long as possible, 4 hours minimum, then check out what's been creating the most wakelocks in BBS. Look at time and counts. Both are equally important.
[Samsung Galaxy Nexus] LibertyMonger:
Hey Osmosis I suppose this isn't up to date or your current settings Bud? I was just thinking about playing with my settings a little but don't trust myself without help from a guide lol.

Actually you probably don't have the GNex anymore, I haven't been able to keep up with the thread much.
[Samsung Galaxy Nexus] osm0sis:
People keep asking. Not sure how to make this much clearer..:(
[Samsung Galaxy Nexus] LibertyMonger:
Well the date showing for last edit is from July, don't know how much more clearer that could be

3rd December 2012, 12:45 AM

(Last edited by osm0sis; 9th July 2013 at 08:46 PM.) Reason: r384; potential iva voltages
[Samsung Galaxy Nexus] SahilC:
Weird. Guess I'll wait for 4.4!

Anyways, my phone has been getting really, really hot these days. Anyone else?