yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] superbellefleche:
Thx! Running it on PA 2.20 with no problems. It seems that I don't have no more problems to reboot (before, I could stay stuck on Google screen...)

I'm already waiting for a 520MHz version !!
[Nexus 7 Android Development] Metallice:
Thanks. I do need time to make sure it is stable and to see how battery life/performance is before I start adding more GPU options.

Lots of little patches and fixes here and there, but I need to see how the LP overclock affects things. Also need time to get feedback that isn't just "I flashed it and it didn't bootloop/break my device" :D ...although it is good to know haha.
[Nexus 7 Android Development] superbellefleche:
lol

I do as I can, with my noob level !!

"That's one small step for man, one giant leap for mankind"
[Nexus 7 Android Development] Jay Aristide:
Well, let's see, here..

Last night, I was getting stuck on the Google screen a lot - even in situations that made no sense. For example, I flashed PA2.2, then flashed the ramdisk you sent me, then flashed the mc446 and it got stuck on the Google screen. THEN I flashed PA, booted it up, then flashed the ramdisk and mc484 and it worked. THEN I flashed mc446 and it worked for one reboot but the reboot after that resulted in stuck at the Google screen...

So, today, I flashed PA2.2, then rebooted, then flashed the ramdisk you sent me yesterday, then the mc446 kernel and it booted right up.

When you announced the alpha, I loaded it right up and it's running great :)

All of this is undervolted -75mV @ 100-1300, interactive/deadline
[Nexus 7 Android Development] Metallice:
Seems like it's happening to people running PA. *shrug* I don't know. I did my testing on the rooted 4.1.2 OTA and never experienced this. .

Hopefully it doesn't happen again with the alpha.
[Nexus 7 Android Development] Jay Aristide:
I've rebooted with the alpha several times and no issues...

Okay, so here's what would make sense for me:

All the various kernel zips (GPU oc's, MK+ & MC, and of course the stock 4.1.2 kernel)

A ramdisk zip containing only the stock 4.1.2 ramdisk

A ramdisk zip containing only the stock 4.1.2 ramdisk, but with init.d support (this zip could create and chmod init.d if it doesn't already exist)

A ramdisk zip containing a proper 4.1.2 ramdisk built for CM and CM-based ROMs like PA (could create /data/local/userinit.d and chmod it if it doesn't exist)

Seems this way people could mix-n-match what they need
[Nexus 7 Android Development] Metallice:
I'd rather not have people flashing ramdisks here and there. The whole point of Koush's AnyKernel is that you can replace the kernel and leave the rom's ramdisk intact. I don't really see the benefit to having all these different ramdisk packages.
[Nexus 7 Android Development] Jay Aristide:
Meh, fair enough. I'm the cover all my bases kinda guy. All those ramdisks laying around would allow me to easily move from any one situation to another. Doesn't really matter, though.. As long as there's a stock 4.1.2 w/ramdisk support floating around, that suits my purposes :)
[Nexus 7 Android Development] Juzman:
I updated to stock 4.1.2, then flashed nightly CM10, then flashed this kernel, getting stuck at Google boot screen.

I am running a 4.1.2 ramdisk (checked with Terminal first).

Edit: Followed brotherandyslb's post below (Wipe Cache, Wipe Dalvik, Flash Kernel, Wipe Cache, Wipe Dalvik and Fix Permissions). Seemed to boot okay so I am guessing it's the Fix Permissions.
[Nexus 7 Android Development] iamelton:
err.. i guess probably my post got misunderstood..

i meant i reverted to stock kernel by flashing the zip file provided in the first post (but its now removed from the post, which i think should be kept in case any one wants to return to the original stock kernel), and the device booted up without problem..

however, my problem with M-Kernel (getting stuck in google screen) remains..

btw, i did not flash the kernel with init.d support.. not sure if this will cause problem as its optional as stated..
[Nexus 7 Android Development] brotherandyslb:
I'm on stock 4.1.2 rooted and I was stuck at Google screen as well. What I did to fix it was:

Cleared Cache

Cleared Dalvik Cache

Flashed the 446 (not alpha)

Cleared Cache

Cleared Dalvik Cache

Fixed Permissions

Afterwards it booted super quick, and it has continued to boot since then as well.
[Nexus 7 Android Development] Jay Aristide:
So, you can boot on the stock kernel no problem, but the M-Kernel sticks you at the Google screen?

Try flashing the stock kernel with init.d support, then flash the m-kernel of your choice. See what that does for you
[Nexus 7 Android Development] iamelton:
yes for ur question..

will try the init.d one then.. thx for the reply..
[Nexus 7 Android Development] brotherandyslb:
I flashed the kernel with init.d support first but was hung at Google screen the method I posted above is what fixed it for me.
[Nexus 7 Android Development] Jay Aristide:
Right on.. I think it might be a fix permissions issue. From what you've said so far, you're running the 446 kernel with the stock+init.d ramdisk. I'll almost guarantee the fix permissions is what cleaned you up, as that's about the time my problems stopped as well
[Nexus 7 Android Development] iamelton:
thx a lot guys.. booted a couple of times and my problem was gone after doing what brotherandyslb suggested..

as i have tried previously to clear cache and dalvik cache in vain, im quite sure this is indeed a fix permissions issue..

and i would suggest to add back the "original 4.1.2 stock kernel" flash zip, just in case anything bad happens or, in my case, for behaviour comparison purpose..
[Nexus 7 Android Development] nphil:
Just curious, does overclocking the LP core affect overall device performance? It was my understanding that it's only active when the device sleeps, watching videos etc. Or is it in use when total cpu usage goes below a certain threshold?
[Nexus 7 Android Development] Metallice:
The last one. Max lp speed increased to 620Mhz and that threshold increased by one step as well.

Edit: No performance or battery problems for me... played beach buggy without issue.
[Nexus 7 Android Development] ecossais:
Never had SOD with r9

I have been using a9 since it's release and have not had SOD with it. I have had SOD with many other kernels that I have flashed. Currently running EOS nightly 37.
[Nexus 7 Android Development] Jay Aristide:
I'm aboit to go back to aosp so I can get the update to 4.2 as soon as it rolls out. Plus I wanna see if it fixes a problem in a game I'm having. Will be flashing a9, of course.
[Nexus 7 Android Development] Fracta1:
Been running a9. Not sure if it's quite as smooth as earlier builds but the sound and boot ups are definitely fixed.
[Nexus 7 Android Development] phonic:
Why would you need to go back to stock ahead of release? When they drop 4.2, you can simply flash boot and system on top and be up and running in the same amount of time.
[Nexus 7 Android Development] WangLung:
Im running the latest Smooth ROM 4.1 with a9. I had the Google boot logo hang at first, took over a minute to boot up. Wiped caches and fixed permissions and now takes about 15 seconds to boot. Everything seems quite smooth, I'm going to leave it for a time to see if I get SOD but so far I'm pretty happy with this and I'm glad to see that the developer is so active in trying to help people, I'll definitely be sticking around.
[Nexus 7 Android Development] h.debnath:
I think sod may occur while WiFi is on, check this out
[Nexus 7 Android Development] bASKOU:
Never got a SOD since got the tab both stock and custom ROMs and kernels. Always having my WIFI on, and never power off the tab day and night.

a9 work perfectly and no more sound crash. Great job.
[Nexus 7 Android Development] ortrigger:
I was getting a few sod's on aokp. I flashed a different rom so wasn't able to see if raising low cpu frequency voltage helped. I'm running liquidsmooth right now and haven't changed voltages yet. Will update if sod happens.

Sent from my Nexus 7
[Nexus 7 Android Development] bervin:
Sod with Wifi on for me too. But won't sod if I manually turn Wifi off after using. I'll try raising voltages.
[Nexus 7 Android Development] Fracta1:
Noticed boot time is really bad on a9. Even after the tablet finishes booting, the widgets and whatnot take forever to load.
[Nexus 7 Android Development] phonic:
First boot or subsequent boots?

aka - did you let it boot all the way, give it time to get settled, and try rebooting it again?
[Nexus 7 Android Development] bobarune:
I would like to flash a9 but goo.im's servers are having an issue. When I tried to download before I was getting 500 B/s. Blazing Fast...:(
[Nexus 7 Android Development] carrsi:
Me too :)
[Nexus 7 Android Development] stonebear:
https://dl.dropbox.com/u/42242524/M-Kernel_a9_446GPU_620LP.zip

That is "M-Kernel_a9_446GPU_620LP". It will only take a few downloads and then Dropbox will disable it but perhaps it will help out for now.
[Nexus 7 Android Development] Kearkan:
I don't know how all these people are getting sod, I'm running a9 520/620 with latest paranoid android and about -50mV undervolt as well as super deep sleep build.prop mod and haven't had a single sod.
[Nexus 7 Android Development] bobarune:
Thanks so much!
[Nexus 7 Android Development] Fracta1:
The first boot and reboot were pretty slow. It just took a while is all. The kernel seems slower in general compared to a7. Even gesture typing is a tad choppy. It's not debilitating... just not as smooth as I'd like :-\
[Nexus 7 Android Development] Kearkan:
to anyone having issues, if you dirty flashed, reinstall after a factory reset, the kernel was rebuilt a few times by metallice so i would think theres a possibility of things misbehaving with dirty flashes. This worked for me anyway, a9 runs flawlessly for me so far.
[Nexus 7 Android Development] Fracta1:
Ugh :P Time to whip out Titanium I guess.
[Nexus 7 Android Development] ortrigger:
Same for me. I was having issues with not being able boot on any of the m-kernel+ releases.

Also, just had sod running a9 with no changes to voltage on liquid smooth rom. Will try raising voltage on lower frequencies to see if it helps.

Sent from my Nexus 7
[Nexus 7 Android Development] FreakyFreakGA:
Idk if it's the ROM I use or the a9 kernel I flashed 520/620 but my battery charge meter wont change even tho it indicates its charging, when its plugged in the numbers wont go past what it was at since last charge, even after wiping battery cache, a9 446/620 seemed to work fine tho.
[Nexus 7 Android Development] Metallice:
Tried AOKP. Performance was terrible even before a9+. Just bad. Hard to tell if a9+ made it any worse. CPU usage idling with one core would be around 40 - 60% for seemingly no reason. CM10? About 10-20%. Same kernel. Also every time an app is opened or closed ramps the frequency up to the maximum and turns on all the cores. CM is fast without doing that.

I'm sticking with CM10 for now.
[Nexus 7 Android Development] pboy:
I just flashed the a9 kernel (both) but I noticed the nfs protocol is no longer supported. Has nfs been taken out of the new version? Thanks.
[Nexus 7 Android Development] zlewe:
Btm right side so hot. 1.1 max on demand. A9

Sent from Mount Olympus via Iris-Messaging.
[Nexus 7 Android Development] Huey85:
Yep I tried both versions and on the lower gpu of version the graphical glitches still are present in NFS MW. I've tried Bricked, faux, trinity and Franco's kernels and the graphical glitches are also present in them too. Only stock kernel runs the game glitch free.
[Nexus 7 Android Development] 416inversed:
Raised my UV to -50mv from -75mv last night and no SOD this morning.... fingers crossed.
[Nexus 7 Android Development] Ryan_Shea:
Ive been running a9 446 620 since its release on pa 2.5 and have had excellent battery life (1d 17hrs lowest 2d 16hrs highest) with WiFi on 90% of the time and 18-10hrs screen on time. Have voltage set to -50 and cpu set at 102-1.3ghz. On demand govenor. Also have jay artiside's tweaks for zram. Just wanted to say I'm extremely happy with this kernel and its performance. Keep up the great work and have a kick ass day.

Sent from my paranoid Nexus 7
[Nexus 7 Android Development] Jay Aristide:
Running 446/620 on completely stock 4.1.2 interactive/deadline, 100/1300 @ -50mV across the board, and my Secret Sauce script (hold the zRam).

Absolutely no issues at all. Runs like a dream, great battery life, and no overheating (even during gameloft games)
[Nexus 7 Android Development] Fracta1:
Damn :( I've been loving AOKP... Time to find a new ROM I guess.
[Nexus 7 Android Development] ortrigger:
Or you could find a new kernel...but this one is probably the best one I've used so far. I switched from AOKP to liquid smooth. It's an aosp based rom with elements of cm and aokp mixed in. It has a lot of the customizations of aokp. In fact, I think I like it better. You should at least check it out. /off-topic

On topic: I went ahead and raised voltages of the lower frequencies by 25 mV and so far haven't seen any issues with sod. I will keep you updated if anything happens.
[Nexus 7 Android Development] BIGSimon:
Does anybody know what the difference is between the a10c and a10t kernels that have been posted on goo http://goo.im/devs/Metallice/Nexus7
[Nexus 7 Android Development] stonebear:
...or try the new CleanROM from Scott, basically stock with tweaks.
[Nexus 7 Android Development] Fracta1:
Flashed Liquid Smooth a bit ago. Speed and performance on the kernel is absolutely amazing now. There's definitely something up with AOKP...
[Nexus 7 Android Development] Metallice:
One is codename Colossus, the other is codename Titan. That's the difference. Purposeful blind comparison.

Haven't been able to update the OP. Away from my PC. Lots of changes. Interactive has been tweaked a lot. For example touch boost to 620MHz and gohispeed load to 1.1GHz instead of max.
[Nexus 7 Android Development] krazeecracker:
About to use this exact setup :)
[Nexus 7 Android Development] BIGSimon:
Ok cheers will download both and test on paranoid 2.54 over the weekend
[Nexus 7 Android Development] Metallice:
I'm liking interactive so far with these changes. Fewer spikes to max frequency and hopefully as a result better battery life. Performance seems fine, but I'm used to ondemand. May keep it as the default. Need more time to test though.
[Nexus 7 Android Development] krazeecracker:
Keep the updates coming. Just flashed a9 and loving it!
[Nexus 7 Android Development] stonebear:
10c feels good so far. :)
[Nexus 7 Android Development] Metallice:
Well you're a whole version behind... I was talking about alpha 10
[Nexus 7 Android Development] krazeecracker:
... updating now lol
[Nexus 7 Android Development] MrDrift42:
Flashed 10c since it had less downloads. Seems great so far. Booted good, seems smooth, wifi is working good, flash works, Zram scripts good.

Hopefully I get better battery life than a9. I was getting 2 hours playing Sims on a full charge.
[Nexus 7 Android Development] Metallice:
I think it is safe to say at this point that people prefer the letter T to the letter C... or that they think Titan is a cooler codename than Colossus.

Also - *fewer downloads :)
[Nexus 7 Android Development] ortrigger:
Just flashed a10c and it already feels snappier than a9. I may try a10t but I already like this one.

Sent from my Nexus 7
[Nexus 7 Android Development] krazeecracker:
Both kernels are the same except for the name? Lol is that what you meant by blind comparison? :confused:
[Nexus 7 Android Development] bjcrj:
Blind comparison means that the kernels are different, but only Metalilice knows how they are different. We decide which is better based on actual use, not preconceived ideas of features in the kernel.
[Nexus 7 Android Development] Kearkan:
18 hours screen on time? I don't know that that's possible.... Can we get a screen shot?
[Nexus 7 Android Development] stonebear:
I think he meant 8-10 hours.
[Nexus 7 Android Development] pboy:
Just tested 10c. I noticed the nfs protocol isn't supported either. Is it broken or is that feature removed from this kernel? Thanks
[Nexus 7 Android Development] MetalPainis:
flashed c yesterday before going to bed, sod when I woke up, flashed t tomorrow and went to work, so far no sod, great performance and nice battery. I'll stay on t a while ;). Thanks for your hard work! Do you consider searching 4 someone to build a kernel app?

sent from a Nexus 7 via Tapatalk 2
[Nexus 7 Android Development] Ricolein_Rico:
a10 feedback

some feedback for the a10 single blinded kernel trial ;)

I am on stock rom 4.1.2 with Jay's tweaks (64 Mb zram) , came from a5 446/620 which was my gold standard so far, flashed a10c after having cleaned cache partition and dalvik cache, fixed permissions. First boot took very long, stuttering on boot logo, app optimization took ages, performance was ok, however not as smooth and snappy as a5, minimal lag when opening app-infos and when typing (swype).

a10t is just awesome, so far no problems at all, fast first boot, fast app optimization, great responsiveness, very smooth and snappy, first time i see a clear bias for 620Mhz (was not the case with a5), low load temp of 45°C (with case and body temp bias). a10t is definitely a keeper, will further watch how battery life is behaving.

Thanks a lot to Metallice for this great kernel!
[Nexus 7 Android Development] stonebear:
I haven't tried t yet but c is fine for me, no issues.
[Nexus 7 Android Development] h.debnath:
I've had 3 sod so far in the past 6 hrs using the titan kernel. My setup as follows:

Interactive 102-1024 Mhz, SIO, PA 2.52, jays buttery tweaks with 64MB zRAM.

I will try colossus kernel next and report back!
[Nexus 7 Android Development] stonebear:
I am trying t now, I think I should mention I use CleanROM, was using SlimBean before that. I use Jays Buttery stuff with no zRam.

The only issues I ever had with this kernel was the sound pop and bootloop (which are known).

t seems the same as c for me so far. :)
[Nexus 7 Android Development] Metallice:
Probably just forgot to enable it. Will do.
[Nexus 7 Android Development] phonic:
Where are the a10 kernels? I don't seem them in the OP.
[Nexus 7 Android Development] Metallice:
Look again
[Nexus 7 Android Development] rootbrain:
Wanting to try this a10 kernel, but with 4.2 about to be released (11-13 is the word), I would have to start over anyway. Metallice, can you say when/if/how long before you would restart rebuilding the a10 with the Android 4.2 kernel?

Think I'm going to wait and keep checking back for 4.2 includes.
[Nexus 7 Android Development] ecossais:
10c and 10t

I have tried both kernels with EOS night lies, currently using 37. I have not had SOD on either kernel. Titan seems to be a little smoother and faster, but it is hard to tell. Both are good for me.
[Nexus 7 Android Development] _DrG_:
Using titan, pretty smooth but would like a 520 GPU version have noticed a little drop in performance on 3d games from a9 cheers
[Nexus 7 Android Development] vn00914361:
Hi guys,

Can anyone let me know the different between the two latest versions? They have the same GPU and LP Core frequencies, from the changelog =/ Thanks guys. I start trying this kernel since it's not OC'ed too high with a medium GPU frequency =)
[Nexus 7 Android Development] BIGSimon:
Test them both and see if you can tell the difference :)

---------- Post added at 11:03 PM ---------- Previous post was at 10:53 PM ----------

Well I've been running a10c all day on paranoid 2.54 and so far so good, booted first time no reboots or FC's, everything is nice and smooth and battery life is excellent especially compared to a9,

Now to try a10t and see what the difference is :)
[Nexus 7 Android Development] krazeecracker:
I'm flashing a10c now.
[Nexus 7 Android Development] krazeecracker:
How long do you plan on letting this run before you decide which is a go lol
[Nexus 7 Android Development] Tycff:
EDIT: Ignore this; I resolved any issues/questions I had in the previous versions of this post.
[Nexus 7 Android Development] vn00914361:
Haha, just tried the mystery c version. My tab was like in total slow motion, lol. It was like hanging and booting at the same time. Good thing I was driving home so I left it running like that. When I got home, everything was done. I hot-rebooted the tab and flashed the mystery t version. Still on it right now. So far so good. Already UV -50mV =/
[Nexus 7 Android Development] than33:
Do you know that go hi speed option and go max speed in interactive is working only when you enable "boost" option which is disabled by default in your kernel?

Also I'm suggesting changing TCP congestion to Vegas which is the best from all methods and is by default enabled on DD-WRT routers.

I'm monitoring CPU speed all the time and it looks like it is now preferring 600 mHz which probably will work great for battery.
[Nexus 7 Android Development] bervin:
how do I enable it then??
[Nexus 7 Android Development] than33:
echo 1 > /sys/devices/system/cpu/cpufreq/interactive/boost

Or you can use trickster mod app.
[Nexus 7 Android Development] Kearkan:
Just moved from 10c to 10t, this one is noticeably smoother.
[Nexus 7 Android Development] codygs83:
I concur. I'm on 10t and my 7 booted a lot faster and is smooth as silk. No sod or issues to speak of so far. Nice work!
[Nexus 7 Android Development] BIGSimon:
Well I've been testing a10t for quite a few hours now and I don't know if this is just a placebo effect but this one feels a lot smoother than a10c, no boot problems with either kernel, battery life is excellent on both, no audio popping, but apps and Web pages seem to open faster on a10t, think I will re-flash a10c just to make sure.

Test done on a fresh install of paranoid 2.54 and gapps with no other tweaks.
[Nexus 7 Android Development] krazeecracker:
A10t made my device melt in my hands from all the buttery goodness. But yes a10t is smooth fast and great battery life for me. No sods to report and heat is non existent. :thumbup:
[Nexus 7 Android Development] Ryan_Shea:
Meant 8-10
[Nexus 7 Android Development] BIGSimon:
Ok re-tested a10c and I don't know what it is but a10t does seem slightly smoother and a little more responsive, so I think I will run this for a while.
[Nexus 7 Android Development] zlewe:
OTG working? I want to confirm because I bought a otg cable.

Sent from Mount Olympus via Iris-Messaging.
[Nexus 7 Android Development] sunman277:
It could just be my imagination but It seems the titan A10 is super smooth. I also ran it through quadrants and it added 500-800 on my score compared to the A5 so it looks like im going to stick with the A10T for awhile. Keep up the good work
[Nexus 7 Android Development] Metallice:
Smoothness is great, but don't forget about battery life.
[Nexus 7 Android Development] Metallice:
Wrong. This is 100% not true. The boost option causes the device to heavily favor hispeed freq and input boost no matter what... instead of only when you touch the screen and when load reaches a certain value.

Enabling it will kill your battery life

Do not do this.
[Nexus 7 Android Development] BIGSimon:
The battery life on a10c is slightly better than a10t.

So long as it lasts a days worth of use then I'll take smoothness and usability any day.
[Nexus 7 Android Development] capez:
Really nice kernel
[Nexus 7 Android Development] _DrG_:
a10t Very smooth still but have noticed quite a bit of battery drain compared to a8/a9 with similar usage
[Nexus 7 Android Development] _DrG_:
Plugged in i have had 2 sod in a row a10t
[Nexus 7 Android Development] krazeecracker:
Try lowering your CPU max to 1.1 or 1.3
[Nexus 7 Android Development] ortrigger:
Have had 2 sod's on a10t while wifi was on. Don't seem to make a difference if wifi is always on or set to turn off while sleeping. It hasn't happened with wifi turned off in the settings though.

Sent from my Nexus 7
[Nexus 7 Android Development] Metallice:
Did you have SODs before the switch to the newest source? I think a8 maybe?

Frustrating as I have never had a SOD. At all.