yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] denzel09:
R: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

Yes
[Nexus 7 Android Development] ezas:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

I just had the power button issue. It was after my device had been sitting for an hour or so. I think it would help to give our configurations to find something in common.

I'm on t11 on Dirty AOKP using Apex launcher.

Dirty AOKP 3.6 <&> m-kernel+ a35 (t11)
[Nexus 7 Android Development] snarlytaz:
I should be curious for the same question, but I rather like tasker. Haven't needed it as much on the tab, but does wonders for my POC Droid3. Only have two more months to go with that fortunately.
[Nexus 7 Android Development] FitAmp:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

Rasbean
[Nexus 7 Android Development] ace-user:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

looks like quite a number of people are experiencing the power button issue, hope metallice can get into the problem...
[Nexus 7 Android Development] siddesu:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

tasker now supports javascript tasks that have an api to the task actions and variables. when you throw in the zoom ui library and the app factory, the only thing that comes close is the sdk with a full-blown IDE.

BTW, I also see (once in a blue moon) slow waking up from power button and "smart case" (is that what you call it?), but it does happen only once in maybe 5-10-15 normal wakeups, so I am not really sure it is a kernel issue.

Or even an issue, for that matter, as closing and opening the lid again or pressing the button again works every time.
[Nexus 7 Android Development] ace-user:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

just noticed a weird bug...i was using the facebook app but all of a sudden the tablet starts to act on it's own...it starts swiping up and down on it's own..i had this problem before about two months ago and i sent it to Asus for repair and that seems to solve it..but yesterday i flashed a35 and the problem surface again...
[Nexus 7 Android Development] FitAmp:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

I use Facebook ALL day mostly everyday and never had this issue
[Nexus 7 Android Development] ace-user:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

the problem doesn't exist only in facebook, sometimes it happens in the home screen as well
[Nexus 7 Android Development] Metallice:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

What makes you think this has to do with the kernel?

Sent from my Nexus 7
[Nexus 7 Android Development] ace-user:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

I'm not really sure...but the problem starts when i flashed a35...maybe it's just a coincidence..
[Nexus 7 Android Development] Metallice:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

Ha. Fair enough. Well I guess it all depends on whether anyone else experiences it

I wish you all could have my nexus 7. No issues.

Sent from my Nexus 7
[Nexus 7 Android Development] NicoGa:
Just a follow-up for the 100 % stuck battery bug (sorry if it is off topic):

It is definitely not related to the kernel as many people have the same problem, even stock unrooted unlocked N7 ... the following thread might be useful:

http://xdaforums.com/showthread.php?t=2090826

I tried to fully discharge my N7 and charge it again while turned-off ((as discussed previously) but it did nothing.

Now I deleted /data/system/batterystats.bin, I will let fully discharge and charge it again while turned on ... will see ...
[Nexus 7 Android Development] scottx .:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

Wanted to play with the latest cm nightly and it was all good. Then I flashed the newest kernel, cleared cache and it did the upgrading apps then rebooted itself and looped forever. Rather than mess with it I just restored aokp.
[Nexus 7 Android Development] Metallice:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

You've got to be kidding me... CM changed their ramdisk again?!

Sent from my Nexus 7
[Nexus 7 Android Development] FitAmp:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

Maybe you're just unlucky, has never happened on my end. Plus I always run the latest m-kernel
[Nexus 7 Android Development] tobitronics:
Upgraded to a4 460/475 and still got sound pop on every unlock. Running pa2.50

Beamed from my Paranoid Google Nexus 7
[Nexus 7 Android Development] Metallice:
Really? Every unlock? Dang. I only have it once in a few days. Have yet to have it on a4. Gah. This is annoying because it is definitely a hardware issue or the cause and effects would be much more normalized.
[Nexus 7 Android Development] HoochieCoo:
I went for broke and installed the 520/620 version. I'll let you know if I run into the issue with getting pops with the screen off (notifications), or if my device combusts.
[Nexus 7 Android Development] phonic:
Thanks for the info about the sound, didn't know that. I wonder why....

Yeah, I disabled that unlock sound a couple months ago when the problem first started. I had originally thought that it might solve the problem, by giving the N7 a little time to "wake up" before using the sound - but that didn't help. Even if I waited 2-3 mins before hitting a button or making a sound, it still "popped". It's a very weird problem that only began surfacing for me around 2 months after I got my N7.
[Nexus 7 Android Development] Alexmessy:
I dont know you guys, but I'm gettin more battery drain on a4 446/620 than on a3 on normal use :/
[Nexus 7 Android Development] Metallice:
That's expected. It should be minor though? I made the CPU g core "turning on" speed too slow in a3. It would theoretically help with battery life, but it was interfering with performance. It's now 1/2 way between stock and a3. I think it's a better compromise now. Still more battery conservative than stock.

Also... there hasn't been enough time to really get a good assessment of a4 battery life. Well except for me, because I've had it a couple days longer, and it still seems great for me.
[Nexus 7 Android Development] Alexmessy:
Hmm thats true, I know havent been enough time yet with it, but it just got my attention that Im barely hitting 3 hours and a half screen-on time and Im at 46% already since full charge O.o but lets see how this keeps going, but anyways Im sticking with it lol
[Nexus 7 Android Development] BillGoss:
I've done a comparison on Motley's classic (my default kernel) and the a3 battery saving kernel. Results are very, very similar.

In fact the only noticeable difference is that a3 pops when I unlock the screen.

I use my tablet only to read email, XDA, and books.

My battery drains at 10%/hr of screen time on both kernels.

Here are the details:

Battery:

A3

Motley

AnTuTu;

A3

Motley

Sent from my Nexus 7
[Nexus 7 Android Development] prestige777:
Using the a4 520/620 not running hot at all, its quite cool actually, battery life is good 8+ hours browsing the internet and listening to music mostly. Flash works much better. I set the cpu to 204/1600. I could probably squeeze some more battery life if I set the minimum to 475 since it jumps between 204 and 475 so much.

---------- Post added at 06:36 PM ---------- Previous post was at 06:27 PM ----------

a 400 cpu setting would be great or maybe release a experimental kernel with a broader lower range. 205, 240, 280, 305, 340, 380, 405, 440, 480 etc, to see what gives the best quitest results.
[Nexus 7 Android Development] HoochieCoo:
Running the 520/620 for most of the day with no abnormal issues until just a few minutes ago. After every unlock, I get a pop for the first sound, then no sound at all for a short time. I can literally put the device to sleep and wake it with the issue over and over.
[Nexus 7 Android Development] Metallice:
No no no. For one there is hardly any jumping between min and 475. If you're using cpuspy as your reference, the high 475Mhz usage is due to it being the g core min. If you're watching the current frequency in realtime whatever app you're using to view the current freq is causing the spikes.

Setting the min to 475Mhz will destroy your battery life in all circumstances. I don't even understand how you're making that conclusion.

Also, I will not add more LP frequency slots. It will accomplish nothing. 102Mhz is the minimum for a reason.
[Nexus 7 Android Development] Metallice:
Thanks for the feedback. I'm looking into it. Waaaay too many hours upon hours so far...
[Nexus 7 Android Development] R3dbeaver:
A4 tested and working great on mine. Probably as smooth as a3 in GUI but games are noticeably better. Granted I grabbed the high clock one this time, but just played Zombiewood for about 30 min on Performance governor and its not even warm to the touch.

Need to check skype though...

Oh, n i never experience any popping... is it from the speakers? Some nexus got defect speakers, u can fix this easily. Find my thread titled Speakers in General forum.
[Nexus 7 Android Development] stonebear:
But if it only happens with this kernel it's not the same is it? :silly:

Actually I had it with the a3 series but the a4 battery saver seems ok, a2 super battery was ok for me too. Need to try the other a4's.
[Nexus 7 Android Development] Kearkan:
Running a4 520gpu for a few days now. The speaker pop still happens. Everything seems to run quite smoothly but, boot up and restart is definitely quicker, but there seems to be a more noticeable battery drain, does the 520gpu affect the battery life all the time or just during games and videos etc?

This version seems a bit more problematic than a3, I actually notice the speaker pop more now. Also I just had 2 resets in a row, I was playing cosmic colony (2d game) and I'm pretty sure the device got to its 60c temperature, because the back bottom left was very hot, and it restarted (I remember reading somewhere this is a safety feature to prevent damage to the cpu, please correct me if I'm wrong) so I let it reboot, opened up xda to post about it and it happened again, I opened system tuner and it was reporting 57C and heading down.

Interestingly enough, I was playing eternity warrior yesterday and the new nfs most wanted today, both 3d games, for a few hours straight, and the tablet barely heated up at all. Not sure if this points to a problem with the LP overclock?

My 32gb n7 will arrive in a few days and considering my current one is one of the first versions (c70) ill be able to give a comparison then.

Edit: just noticed the new a5 will flash that now and see what it's like tonight, is there supposed to be no link next to the 520gpu version?

Also, I just reread your recommended settings, what are the main differences between ondemand, and interactive governors?
[Nexus 7 Android Development] Metallice:
60 degrees is nothing to worry about. Dynamic EDP doesn't kick in until 68 degrees, and the force reset temp is something like 78 degrees. You should be okay temp-wise.

The heat and reboots when "not" playing games points to a problem with your device and the LP overclock, not to a problem with the LP overclock. And the speaker pop is only more noticeable because you know what it is and are looking for it :)

Either way try a5. May be better for ya.

520 version isn't available yet. I just got the 446 up. Geez gimme a break.

There are a ton of threads on the differences between governors. Google it.
[Nexus 7 Android Development] Kearkan:
I'd just noticed interactive seemed to be the default everywhere so was wondering if there was anything in particular here to make ondemand a better option, but I'll do my own research and swap it and see how my battery/performance goes.

And yes, I understand it's probably my device, I was just trying to pinpoint if it is the LP causing it in my particular case. as I said, 32gb coming soon and I believe they're all c90 which I'm assuming will solve the heat issue.

Just flashed a5 now, had to fix permissions but besides that everything is fine so far.

haha, not trying to rush you, just wasn't sure if there was a link missing or if you were just indicating its on the way =P

Keep up the good work mate!
[Nexus 7 Android Development] Metallice:
Interactive is default because it's set that way in the ramdisk. Any kernel that preserves ramdisk will therefore have it as default whether the dev likes it or not.

There's no reason that a newer device would be more tolerant of LP overclocking than an old one. The chips are the same. Its really just luck of the draw.
[Nexus 7 Android Development] jetdite:
Noticed this "pop" with A4 332/620. I unlocked the tablet and hear a "pop" instead of a "click" as usual. Then I locked/unlocked the tablet another several times, but can't hear anything at all (neither "pop" nor "click"). Then suddenly the usual "click" came back.

Not a big deal really. Normally I turn off the unlock sound. Just read the problem in this thread and want to report my testing. Hope this help.

EDIT: With my Nexus 7 running A4 332/620, this problem is hard to reproduce. But when it happens, the tablet has no sound at all for a short period.

EDIT: Just flashed A5 446/620 and couldn't reproduce the prolem (locked/unlocked the tablet dozens of times). I will test further later.
[Nexus 7 Android Development] Metallice:
Heh. Sorry. I guess I'm just too fast :). Just getting feedback on a4 after i upload a5 haha. I'll slow down in the future. Just wanted to get this weird sound bug ironed out quickly.

_________________________________

I have yet to have any kind of pop or click on a5 no matter how hard I try :victory: I think the problem may finally be "fixed" :fingers-crossed:

Unfortunately I still have no clue what caused it. I went all the way back and tried to pinpoint the origin but I couldn't. Hard to explain but the logic of it all didn't end up working...

To try to explain what I mean it's like "Base + patch 1 + patch 2 + patch 3" gives popping. "Base" gives no popping. "Base + patch 1 + patch 2" gives no popping. So you'd think patch 3 would be the cause..., but "Base + patch 1" gives popping and "Base + patch 2 + patch 3 gives no popping". So yeah. The logic doesn't work out and it's frustrating as *(insert expletive).

Just have to be very careful and cautious from here on out.

_________________________________
[Nexus 7 Android Development] FitAmp:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

Oh god... -__-
[Nexus 7 Android Development] ezas:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

Just an update on my power button. I ran leankernel all day today and did not have a time when I needed to press the power button twice. I'm going to put back this kernel and see what happens over the next 12 hours our so. I'm not trying to make this a big deal cuz it's impact on using my tab is close to zero.

Dirty AOKP 3.6 <&> m-kernel+ a35 (t11)
[Nexus 7 Android Development] Foggy79:
I have this power button issue to.

Have it since a few kernel versions now. Running a35 atm.
[Nexus 7 Android Development] adstraylight:
I'm using the latest CM10.1 nightly with a35, with no such problems.

@scottx.,what bootloader version are you running?

EDIT: it sounds more like you flashed the wrong version of gapps.

EDIT EDIT: It also has nothing to do with having cleared the cache/dalvik cache, as whenever I upgrade my nightly I flash a mod that does this at the same time as I flash M-kernel.

EDIT EDIT EDIT: I just flashed today's nightly (?) with no issues.
[Nexus 7 Android Development] Leonhan:
Hey guys, can someone tell me a configuration that is battery friendly? I am going to be busy at school and I will mainly use my N7 for ebook reading and occasional surfing. I am not the type to tinker the settings since I do not have extensive knowledge about these. Any config is greatly appreciated.:)
[Nexus 7 Android Development] Metallice:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

Thank you for that last sentence haha.

If it doesn't happen for you on a32 then I would say it's because of your device and the low volt LP1 patch. Worth it? I dunno.

Sent from my Galaxy Nexus
[Nexus 7 Android Development] skylinegt77:
i must be really lucky since i have been using a32 for about a week and no issues at all, tried all the more recent ones but they dont apear to be as fast as a32 so i guess ill just stick with it till i find a better 1
[Nexus 7 Android Development] Nosferatu.:
it's called always have a nandroid backup handy but more importantly with oddball issues that no one else has you need to do a full wipe and reflash your ROM/kernel to remove all other variables causing issues

Sorry.
[Nexus 7 Android Development] piupiu piu:
Your kernel is the best! But with a 35 I found some issues. I also have problems with temprl run 2. And in flip board there is some miss frames
[Nexus 7 Android Development] xfrancis14:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

Metallice my nexus 7 is charging very slow lately like it won't charge full over night, do. Think it's from your kernel?
[Nexus 7 Android Development] bervin:
hey metal! is there any way to boost the volume of the headphones at a kernel level?
[Nexus 7 Android Development] kahei036:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

I was sticking with a32 for some while as well, until yesterday I updated to a35, no issues at all, battery life even better. Quite happy with that
[Nexus 7 Android Development] scottx .:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

I have the latest bootloader. I checked that long ago.

I didn't install the wrong gapps, I'm not new to this. I'm an old school pro, don't you know? :)
[Nexus 7 Android Development] Tone_Capone:
I did the same thing with no effect. I'm doing a factory reset and clean install of my rom to see if that will solve the issue as the thread you posted suggests.

Hopefully this fixes the issue!

I'll let you know

Thanks!
[Nexus 7 Android Development] skylinegt77:
yeah i also noticed battery life increased with a35, but performance went down a bit especially when it comes to ram speed thats why im a lil relutant to change. btw @metallice, do you know which part of the kernel affects the native memory allocations?

---------- Post added at 06:17 PM ---------- Previous post was at 05:48 PM ----------

i here by correct my former statements, performance is about the same, the problem is my new (replacement) nexus 7 seems to hate oc'ing above 1.5 ghz, even at 1.6 if i run 2 benchmarks in a row, the 2nd one will give me a lot less points, so it seems to me that the third nexus 7 i have is a lesser quality soc than the previous 2
[Nexus 7 Android Development] adstraylight:
Ok, no offence ;) Just the assumption that this was a kernel issue made no sense to me based on my experience. Text format can seem so cold but I was actually trying to help.
[Nexus 7 Android Development] BillGoss:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

The default settings work very well. I lose 10%/day plus 10%/hr of screen time. 9 hours screen time in one day is easily achievable.

Sent from my Nexus 7
[Nexus 7 Android Development] FitAmp:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

I have no issues playing temple run 2. Runs just fine. Probably not a kernel issue. Can you be a little more descriptive? List what the problem is in depth.... It will help debugging your problem.
[Nexus 7 Android Development] Tone_Capone:
After a factory reset, my battery issues seem to have been fixed (this is after a little testing). I will see if this holds after a long charge over night.

Cross your fingers... :)

Tony
[Nexus 7 Android Development] Southrice:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

Install trickster mod from Google play store, then set max CPU cores to 2, then under volt -50 mpu voltages. Lastly setcpu at 1300000 max with ondemand governor.
[Nexus 7 Android Development] ezas:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

I use Flipboard and have not noticed anything wrong. What do you mean by 'miss some frames'?

Dirty AOKP 3.6 <&> m-kernel+ a35 (t11)

---------- Post added at 02:20 PM ---------- Previous post was at 02:09 PM ----------

It's possible that it's the patch since I never used the low power patch before you baked it in to the kernel. My device sat on my night table all night and woke today with just one press.

Personally I'm willing to consider it just one of those things.

Dirty AOKP 3.6 <&> m-kernel+ a35 (t11)
[Nexus 7 Android Development] Stuphologist:
Interesting. My original N7 (which finally just got too yellow to tolerate) wouldn't of above 1500 for anything. My new one rocks along at1700 no problem.

Dave
[Nexus 7 Android Development] k29er:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

For me it depends on the ROM. I run several ROMs in backup. I started to notice this with a33, some ROMs will freeze instantly if set over 1300 and others are stable at 1700 all with the same n7. Pa was the best with a33, antutu scored 16600 at 1700mhz.
[Nexus 7 Android Development] skylinegt77:
problem with mine is i tried almost every rom out there with the same results... anything above 1.5 ghz will not work, it doesnt even begin to heat up or anything, i just set it to 1,7 and i get less points than at 1.0 even without it heating up, i have gotten anywhere from 10k points to 5k O_o btw, do you use any extra tweaks or just pa and m-k?
[Nexus 7 Android Development] scottx .:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

I keep mine at 1.6 no matter what rom I run and I never have any reboots or problems. If I even set it to 1.7 it will lock up and reboot itself so I don't even try.

Can you add sio please?
[Nexus 7 Android Development] prestige777:
Not sure why my tablet hates the 1.7 slot on M-Kernel only, it also hates high over clocking of the GPU on M-kernel. I can run trinity at 1.7ghz and 700mhz GPU all day and get a lot higher benchmarks, not that I care about benchmarks. I also ran Clemsyns 2.0ghz kernel with good stability and even better performance. I'm not sure what it is that causes that. I like M-Kernel though and I determined to figure out why my tablet hates it all of the sudden.
[Nexus 7 Android Development] Milamber33:
Check voltages. That's probably the most likely culprit.
[Nexus 7 Android Development] siddesu:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a35

2 days of 7.5+ hours screen time doing useful stuff from full charge to the low twenties! a35 rocks seriously and massively. That's nearly double wha i get with the regular kernel.
[Nexus 7 Android Development] berkos:
can you share your settings and which governor and apps you are using? i can't get that mileage with anything above a25...
[Nexus 7 Android Development] luke05dee:
HI Metallice, did you ever work out the 700mhz memory OC? As you sad if you went higher errors would appear meaning something was happening. But then you said you tired to OC to an insane amount and according to all debugging it was running at that imposable frequency. May I ask could it be that there is code on the kernel side somewhere that when it detects a frequency out of a range it defaults it to stock as a safty feature? Just thinking a way you could test if 700mhz worked could be to run the gpu at 700mhz, in which case the memory bandwidth is almost certainly be a bottleneck, and run benchmarks like basemark es 2 and see if there is absolute any change how ever small? Just thinking as the memory bandwidth is the thing holding this device back the most on the gpu side of things, especially as the t33 with the same memory as us but OC'd to 800mhz, GPU out performs ours by quite a bit at the same freq :) Sorry about all my waffle, getting a bit tired... need coffee!! :P
[Nexus 7 Android Development] katestar:
Same actually, I ran Clemsyns at 1.8ghz at not a high voltage for about a week with no instability at all. I also ran trinity at 1.7ghz for about a month at a low voltage. Yet on M-Kernel 1.7gh reboots after a few minutes at any voltage, how ever high. In case it was just my SOC starting to show stress, I flashed trinity a few days ago and ran stress test at 1.7ghz for quite a while and it was stable completely so my hardware is fine. Voltage doesn't seem to be a problem. Just what I'm finding anyway :')