yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] phonic:
Regarding the popping sound, at least in my case which only occurs after it's been in standby or silent for a while, I noticed something interesting. When the device is in silent mode, the first time I try to do something which causes a sound, I *still* get a 'pop' out of the speaker. If I turn on the sound right away, I don't get anything for a while. So, that leads me to believe it's more an issue with the sound driver then hardware. If the device sound is off, it shouldn't be sending anything to the speaker anyway.

So again, I seriously doubt this is a kernel issue.
[Nexus 7 Android Development] HoochieCoo:
I noticed the same thing the other night. I have Tasker switch the device to silenced late at night. But I would still get the popping when unlocking.
[Nexus 7 Android Development] Metallice:
Even in silent mode the speaker gets "activated". On the galaxy nexus this is also true. On many GNexs a slight sound is heard when the speakers turn off. You'll here this even during silent mode. I think this is common to android in general.
[Nexus 7 Android Development] Metallice:
Also try turning off screen unlock sound. Works for me, and I don't really miss it.
[Nexus 7 Android Development] Fracta1:
Only had one popping issue so far on a4. Battery drain on standby was 100 to 94 percent after 6 hours.
[Nexus 7 Android Development] Tone_Capone:
Is anyone else experiencing the battery being stuck at 100% after charge? Mine hasn't moved in about 3 hours since unplugging. Is this something to worry about?
[Nexus 7 Android Development] mmokk:
inaccurate battery readings after charge

Yes, I also have that "bug" (hopefully not xD)

It is stuck for at least 30 mins of screen on time. Appeared in 33 and 34. I haven't seen any bad behavior or something, just the readings seem to be inaccurate some time after charge.
[Nexus 7 Android Development] Tone_Capone:
:D Hopefully not a "bug," lol. Ya I knew something had to be up. Hopefully Metallice can track it down. I'd rather the thing be accurate than have this placebo affect of great battery life.
[Nexus 7 Android Development] dSlice:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a34

I had a lock up with a34, well actually the screen went black as the game continued to play music and do it's thing. I had to hold the power button down.

Test 7 has been good so far.

Sent from my AOSPA N7 controlled by Metallice's Test 7 Kernel.
[Nexus 7 Android Development] S3tArtist:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a34

20 minutes after I unplugged the device my battery was still at 100%. It was a bit strange to me, so I rebooted the device. As soon it rebooted, battery went down to 99%. I don't know if that was the trick, but now it's back to normal Did u try to reboot?

sent from PAranoid Nexus 7 powered by M-kernel
[Nexus 7 Android Development] Tone_Capone:
I rebooted twice! After 30 mins of screen on time(including 5 minutes of game play in Osmos) the damn thing finally moved down to 99%. This happened to me yesterday too. I think it may be associated with a33 and a 34.
[Nexus 7 Android Development] denzel09:
R: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a34

Both a34 give me SOD always.
[Nexus 7 Android Development] Bitweasil:
Finally... I've posted enough junk in other threads to be able to post here...

When people are getting the failure to wake, is it with or without the screen backlight? I've seen both on mine at this point with a33 and Test6, and haven't sorted out a significant pattern to them. In both cases the screen is "blank," but one involves the backlight being on, and one involves nothing coming up at all.

It seems like the lack of backlight happens after a more prolonged sleep in colder temperatures (overnight, or after a trip home in a backpack exposed to cold ambient temperatures), which, I think, involves a somewhat lower battery voltage on wake. I'm also operating under the assumption that the voltage regulation isn't perfect, and the same requested voltage at a low battery state leads to a lower actual voltage than with a fully charged battery.

Since my device hangs somewhat regularly with the latest kernels, and I'm comfortable with kernel compilation, I'm planning to do some experimentation with regards to the sleep voltages. I currently believe the sleep voltage value poked to the VRM over the I2C bus corresponds roughly to 32mv increments, and that bumping this up or down will make things better or worse with regards to not waking from sleep. Also, setting it to the full wake voltage on sleep would allow testing the i2c communication path without actually dropping the voltages. Since the kernel spins waiting for the i2c controller to acknowledge the command on wake, this seems like an area that could be part of the problem.

It sounds like fun to me. :)
[Nexus 7 Android Development] S3tArtist:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a34

Sounds like a good theory to me :)

sent from PAranoid Nexus 7 powered by M-kernel

---------- Post added at 09:24 PM ---------- Previous post was at 09:19 PM ----------

Hmm, maybe it just need a few cycles... Maybe metallice noticed something...

sent from PAranoid Nexus 7 powered by M-kernel
[Nexus 7 Android Development] Tone_Capone:
We shall see. I just flashed a33 to see if the issue remains.
[Nexus 7 Android Development] Bitweasil:
Ok, I'm now running a custom compiled a33 with, if I'm correct and my compile was good, LP1_950 running closer to LP1_1010. I think. Somewhere around there, but "more than what the patch initially used."

The only change, other than the kernel name for verification, was changing the lp1 sleep voltage sent out on the bus from 0x1D to 0x1F.

My assumption has been that each step corresponds to 32mv, which is sane enough for a gross control of an i2c bus VRM, and easy to implement in hardware. We'll see.

I'm leaving my core voltages alone for now (so higher than I normally run them), but will drop them back down tomorrow if I don't have any hangs before then. I wanted to eliminate that possibility, though the voltages I've been running have been stable and tested.
[Nexus 7 Android Development] xfrancis14:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a34

Temple run 2 and shadow gun give me sods?.. If I run like a game then switch to one of those games my tablet freezes and I have to shut it down
[Nexus 7 Android Development] Metallice:
I'm not sure you know what a SOD is.

Regardless I would need a last_kmsg to do anything about that, as that seems to be a new issue. That is, assuming your not undervolting/overclocking.
[Nexus 7 Android Development] Fu5ion:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a34

a34 with patch is working beautifully for me. I had a few SODs on 33, but have my had one on 34 yet, even though I am using the low lp voltage.
[Nexus 7 Android Development] Metallice:
Test 8 - http://www.mediafire.com/download.php?75e7m3n3zmx2tm0
[Nexus 7 Android Development] Metallice:
At this point I don't think the LP1 patch has anything to do with any SODs people were having.
[Nexus 7 Android Development] Fu5ion:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a34

If my case is any indication, then I'd say you're right. Which is nice, because I like the idea of the lp patch.
[Nexus 7 Android Development] denzel09:
R: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a34

In test
[Nexus 7 Android Development] ezas:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a34

I'm on a34 without the patch and Zen Pinball is about the same as on earlier versions. If anything maybe a touch better. It's very smooth and not glitchy at all. That's on enhanced video quality. This is with all default kernel settings except for fsync and smart dimmer disabled.

No problems on t7/a34 heading to 8 now.

Dirty AOKP 3.4 <&> m-kernel+ a32
[Nexus 7 Android Development] siddesu:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a34

my experience with a34 (both kernels) so far - both kernels run fine, but both give me shorter battery life than a32.

disclaimer: my usage is undemanding - i read, take notes and sketch on the tablet, i almost never play games and to me bad piggies hd is a stress test.

so ymmv a lot ;)
[Nexus 7 Android Development] Bitweasil:
Could you be so kind as to actually state what you're doing in the tests, for those of us following the development a bit more closely? :) Thanks!

I've not seen any issues so far with my LP1_950+a33 kernel modified for higher voltage sleep (or something). I dropped my core voltages to where I normally run them, and it's OK so far today. I'm not calling it good for another few days without any issues, but I definitely had SOD on a33.

This either means that I'm sending the VRM rubbish and not actually turning the voltage down, or that it's working with the higher sleep voltage. I'm not sure which it is, tbh. I may try dropping the voltage even more on sleep with my suspected decoding to see if this causes more frequent SOD events. If dropping it lower causes a 100% failure to wake from sleep, that would be pretty solid proof it's doing what I think it is. Any ideas on test points to check the voltage? :)
[Nexus 7 Android Development] denzel09:
R: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a34

SOD with test 8
[Nexus 7 Android Development] adstraylight:
Oh I understand, well fwiw I get SODs with 34, whereas t7 seems fine, am now running t8.
[Nexus 7 Android Development] Metallice:
Okay. Assuming Test 7 is okay, then that's good news. Getting closer.

Your god-awful nexus 7 is rather helpful here :D

Test 9 - http://www.mediafire.com/download.php?r4m2ii70onv58u6
[Nexus 7 Android Development] Metallice:
Not until I'm done. I want testing blind.
[Nexus 7 Android Development] Metallice:
Alright I have to correct you as you've said this like 10 times already.

"in test" makes no sense. "In testing" or "Testing it now" would be right.

I know "test" is a noun so I understand how one could think "in test" would be correct considering preposition-noun phrases usually work fine like that (although with an article like "a" or the" before the noun), but it's not here.

People do say "I'm in a test", but that always refers to the kind of test you take in school for example.
[Nexus 7 Android Development] ezas:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a34

I have to ask, was "makes not sense" intentional?

No problems on 8. I'm downloading and flashing test kernel 9 now.

Dirty AOKP 3.5 <&> m-kernel+ a34(t8)
[Nexus 7 Android Development] Metallice:
Lol no.
[Nexus 7 Android Development] Bitweasil:
Fair enough. I hope for a full report at some point. :)

Still no issues with a33+0x1F sleep voltage.
[Nexus 7 Android Development] adstraylight:
The interesting thing is that you can have something "on test"...
[Nexus 7 Android Development] Stuphologist:
T9 is working like a champ. That said, T8 didn't give me any problems either

Dave
[Nexus 7 Android Development] Metallice:
I've never heard that before. If someone said they had "something on test" to me I'd look at them funny. Maybe it's regional.
[Nexus 7 Android Development] Metallice:
Thanks. I'll see what denzel09 and his magic SOD-machine have to say first.

His Nexus 7 = miner's canary
[Nexus 7 Android Development] flim flamin:
Just wanted to let you know, I've been running a34-patched and have yet to run into any issues.
[Nexus 7 Android Development] siddesu:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a34

same here so far, and good battery life on T9. thumbsup.
[Nexus 7 Android Development] Metallice:
test 10 - http://www.mediafire.com/download.php?16ccww835mw9u64
[Nexus 7 Android Development] xfrancis14:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a34

Turns out it was a problem with pa pie 4 cause pie 3 works but yea the app doesn't start the screen goes black right when I click the app, Ik what an sod is tho I assumed that would be considered one but I guess not
[Nexus 7 Android Development] Metallice:
SOD is when the devices fails to resume from deep sleep. So... not that :)

AKA "Sleep of Death" or "Screen Off Death"
[Nexus 7 Android Development] spinkick:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a34

Made it through an entire day on 34,no lockups or crashes.
[Nexus 7 Android Development] ace-user:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a34

a34 gave me quite a lot of problems...it hangs on lockscreen, and i have to force reboot...wreck it ralph hangs when i try typing my name, have to force reboot also...and sometimes when i press power button, the screen wont wake...it happens very often...
[Nexus 7 Android Development] xfrancis14:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a34

Oh okay sorry I thought it was a bit different
[Nexus 7 Android Development] ezas:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a34

Nothing interesting to report on 9. Zero issues. What ever gave me my two SODs must have been 'tuned' out a couple of rev's ago.

But going to 10 in case I can contribute something useful moving forward.

Dirty AOKP 3.5 <&> m-kernel+ a34(t9)
[Nexus 7 Android Development] Metallice:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a34

Not really. i went backwards on big steps from a33 untilI had a range of patches where the SOd causer must be, and now I'm moving forward one patch at a time towards a33 until we get to it.

No SODs means we haven't gotten to the SOD causer yet.

Sent from my Galaxy Nexus
[Nexus 7 Android Development] uberbania:
16 hours on a34 with PA 2.99 Pie 4. 2 cores active, 416 GPU, CPU at 204/860, ondemand governor.

95% battery remaining. SugarSync keeps turning WiFi on. 10min of total screen time. SugarSync was set to sync every hour. Oops.

SugarSync responsible for 41% of use

Tablet Idle 25%

Screen 20%

I'm happy.

Question: would setting two_phase_freq in Ondemand control to 666000 keep main cores from coming online initially. Will this help with battery longevity given min/max at 204/860 with only 2 cores max active?

I greatly appreciate this kernel and everyone's input and efforts that have already gone into it. Thank you guys!
[Nexus 7 Android Development] ezas:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a34

Sounds good to me. I'll keep flashing them as you put out builds.

Dirty AOKP 3.5 <&> m-kernel+ a34(t.10)
[Nexus 7 Android Development] adstraylight:
It's used in the UK mainly in the context of reviews of cars and other machines. I suppose the journalists or editors think it sounds tougher and more manly than the word review :cowboy:
[Nexus 7 Android Development] qwerty123321:
Is there a reason to upgrade to A34 from A33 when I don't get SOD and everything works fine in A33?
[Nexus 7 Android Development] _DrG_:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a34

Fyi i have been running a34 for 26 hours, over night here in the uk, and it woke fine from a 7 hour deep sleep, no sods no random reboots, the only fc is system ui but that's a pa 3.1 issue so all good here on a34 plus battery is sound; 35% remaining, 1day 1hour on battery with 4.5hours screen time and gaming. Cheers

N7 PA M-Kernel
[Nexus 7 Android Development] fossean:
Running A0.8 overnight without reboots, then woke normally but froze while swiping through nova home screens.

Last_kmsg attached, though this N7 was perfectly stable with A33 & A34, so it may be of limited usefulness.
[Nexus 7 Android Development] denzel09:
R: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a34

No one SOD with 9 test kernel;)

I need to test the 10 test kernel?
[Nexus 7 Android Development] adstraylight:
Yes, he is now adding patches to see what causes the problem. So success will be when one of us gets a SOD.
[Nexus 7 Android Development] denzel09:
R: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a34

OK testing #10
[Nexus 7 Android Development] denzel09:
R: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a34

No SOD with #10 kernel
[Nexus 7 Android Development] johnnyman25:
hello!!just installed m-kernel a34 and still cant see cpu temp and max active cpu cores setting in trickster mod....anyone have the same problem?
[Nexus 7 Android Development] _DrG_:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a34

Running a34 i can see both those fields fine

N7 PA M-Kernel
[Nexus 7 Android Development] johnnyman25:
hmm.so maybe its rom related issue?any suggestions?thx!

edit:i fixed it.i installed Awesome Kernel Cleaning Script and then flashed m-kernel a34 version!!settings are back!!also what's the difference between low voltage LP1 patch and no low voltage LP1 patch?

http://xdaforums.com/showthread.php?t=2121649
[Nexus 7 Android Development] ezas:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a34

Deleted

Dirty AOKP 3.5 m-kernel+ a34(t.10)
[Nexus 7 Android Development] fossean:
Running A0.10, no UV or OC.

Device froze when tapping shortcut to Root Explorer app. Unresponsive (with screen on) for approximately 60s, then spontaneously rebooted.

No SoD.

Last_kmsg attached.
[Nexus 7 Android Development] Fu5ion:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a34

Tests 9+10 both sod-free thus far. And a34 ran excellent with the low voltage lp1.
[Nexus 7 Android Development] ezas:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a34

I tried to reproduce this and it worked fine. I'm not trying do diminish your finding, just trying to see if it was tied to launching Root Explorer from a shortcut.

Dirty AOKP 3.5 <&> m-kernel+ a34(t.10)
[Nexus 7 Android Development] fossean:
I agree, probably just a coincidence that I was launching an app when it happened. Can't reproduce it.
[Nexus 7 Android Development] R3dbeaver:
I just had to pitch in... I hear "on test" every day at work. It means they are working in TEST environment, instead of live production or learning environment.

Of course, it is simple the short version of "in test environment" but I thought I pitched in...

Ps: i work in a hospital so this can range from testing new drugs to new app to deploy...

Pps: in Canada.

---------- Post added at 10:00 AM ---------- Previous post was at 09:57 AM ----------

On another note (lol forgot my original intention), about a day with a34 w/o patch and I have no issues whatsoever. Battery drained and charged normally. However, it *feels* like battery drains much faster. I play Shadowgun sometimes a few hours, sometimes 30 minutes, so I cant say for sure its better/worse than previous version. Still very much acceptable though...

Maybe I should try the one with patch?

---------- Post added at 10:02 AM ---------- Previous post was at 10:00 AM ----------

Personally, I'd say no.
[Nexus 7 Android Development] dSlice:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a34

Test 8-10 have been fine each time...

Sent from my AOSPA N7 controlled by Metallice's Test 7 Kernel.
[Nexus 7 Android Development] Metallice:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a34

Damn you UK and your colonies (Other than us)! Messing up your own language!

Yeah I'm pretty sure nobody in the US would ever say that... Maybe if they are up north. It would nostly be "in testing" instead.

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

And 'nostly' is correct in which language?
[Nexus 7 Android Development] Bitweasil:
Well, FWIW, my own compiled a33 with 0x1F sleep voltage is still behaving. Stock a33 had frozen a few times by this point. Not sure if 0x1F is a valid voltage to set and it's good with that, or if it's just not dropping the voltage. Theoretically it is... I was going to email the original commit author & see if they could share anything useful.
[Nexus 7 Android Development] Metallice:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a34

"Sent from my Galaxy Nexus"

Gimme a break here. It's a touchscreen keyboard and autocorrect failed me.

And yes gimme is most definitely a word.
[Nexus 7 Android Development] Metallice:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a34

Test 10 has the LP1 patch and works fine.

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

Sorry metallice i have to agree with r3d i work in a software corp and we use it all the time shorthand for "application currently deployed to the test environment" but if it makes you feel better I'm in the UK too ;)

N7 PA M-Kernel
[Nexus 7 Android Development] adstraylight:
Surely the use of the word "most" is redundant within the context of this statement?:silly:
[Nexus 7 Android Development] Metallice:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a34

It's always redundant before the word definitely, not just in this context. I was kinda being sarcastic/hyperbolic on purpose.

And yes, kinda is least definitely a word.
[Nexus 7 Android Development] Metallice:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a34

That's why I said it was regional. No need to apologize because agreeing with him is agreeing with me too. Nobody is wrong here.

I just said that I've never heard "on test" before and it must be regional... Which it apparently is.

Just like people from NY/NJ say they are waiting "on line" for something, and in every other state we says waiting "in line" for something.

Nobody is wrong here.

(What do you Brits say? You're queueing? :D I heard you guys LOVE to do that.)

Besides, everyone knows that American English is the "true" English, regardless of the language's origin. :D Whether you guys like it or not we win the culturally, and thus american English becomes the norm and, eventually, the correct way.

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

Ha yes we queue a lot, all very civilised! Good things come to those who wait.. Right

N7 PA M-Kernel
[Nexus 7 Android Development] Metallice:
Test 11 - http://www.mediafire.com/download.php?ujwkq6v5dpvqe0l
[Nexus 7 Android Development] Tone_Capone:
I'm still having this weird 100% battery issue. Should I do the old school run it until its dead, clear battery stats, and recharge?
[Nexus 7 Android Development] Metallice:
You can try. Something might messed up with your battery calibration, but AFAIK software calibration *should* reset at full charge and hardware calibration *shouldn't* be a problem with Li-Ion batteries.

I have seen this issue before. Although it was with my old Nexus 7. I've yet to experience it on my new Nexus 7 or with any of the 3x alphas. I don't believe it to be a kernel problem or a ROM issue, but a pure hardware bug, as I've seen people complaining about their battery being stuck at 100% for an hour or two and then dying at 20% battery in every sufficiently long kernel thread, every ROM thread, and many General/QA section threads.

Fully draining your nexus 7 and then charging it back up to 100% might be a quick fix (although the HW bug will probably pop back up again). This is how it was on my old Nexus 7. I would first try leaving the device off when charging it back up from completely dead. If that doesn't work you could then try charging it back up to 100% with the device and OS on.
[Nexus 7 Android Development] fossean:
Haha, I actually felt my knee jerk when reading this. Almost retorted with a bit of cultural imperialism before I realized you were writing in jest.:laugh:
[Nexus 7 Android Development] FReaKRaNT:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a34

Everybody knows the saying, The English invented the language but the Canadians modified it and took it out of beta. Hello! :D

Metallice, I think a lot of this issue stems from Pie4. I was running a33 for ages on Pie3.0 tilapia with absolutely no problem. Then after I flashed Pie4 I had lock screen freezing with every kernel I flashed. I went back to Pie3.0 and A33 runs fine once again. I am still in test. Your thoughts?

Cheers, FReaKRaNT
[Nexus 7 Android Development] Metallice:
That would be the most likely culprit. Most of the time an userspace issue (such as apps force quitting, apps failing start, apps freezing while system is still responding) is, unsurprisingly, due to a problem in userspace (AKA ROM or an app)

Of course there are numerous exceptions, for example, I could make it so LowMemoryKiller is FUBAR, and that would cause issues in userspace. Another examle would be the flash corruption bug due to the kernel that seems to have no discernible cause.

The fact that the Last_kmsgs for a lot of non-SOD problems I've read seem to show no problem (No kernel errors, with a system shutdown called for and subsequently executed) supports this.
[Nexus 7 Android Development] Metallice:
Anything so far? :)
[Nexus 7 Android Development] denzel09:
R: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a34

is in testing