yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] nphil:
I'm sorry to revive a dead horse, I tried out the latest a10 colossus version and checked what freq the lp core was running on with the screen off. It's still maxing out at 620mhz. Just for the sake of comparison, I did the same with the latest Trinity kernel alpha, and it scales properly, with the lp freq at 102/204mhz constantly when the screen is off. This could possibly explain the battery drain me and some others have been noticing?

EDIT: Same story with the Titan version, except for the very rare 102mhz. I'm running both with ondemand governor.
[Nexus 7 Android Development] ortrigger:
I never used a8. Went from a5 to a9. I did get them on a9. It was the same situation. If wifi was on and I left my tab in standby for a long time it would sod. I can try and replicate and get logs if you need.

Sent from my lg spectrum rocking ics.
[Nexus 7 Android Development] Metallice:
What others? There was one battery remark and it was in regards to titan compared to the previous builds which makes sense due to the switch to interactive among other performance tweaks in a10. LP core scaling works perfectly fine. Nice big 102Mhz line in cpuspy. If your device and your device alone is having some issue than I'd need logcat and dmesg to help you.

I'd like to help but you have given me no information other than a description of a problem that nobody else seems to have.

Dmesg. Log cat. Please.
[Nexus 7 Android Development] Metallice:
What about on a5?
[Nexus 7 Android Development] ortrigger:
I don't think I ever got a sod on a5.

Sent from my Nexus 7
[Nexus 7 Android Development] Metallice:
Alright thanks. If you manage to get any logs like dmesg or log cat of the SOD that would be great.
[Nexus 7 Android Development] MetalPainis:
I stayed on a10t the whole weekend, sadly I recieved 2 sod's over the time, the first @ stock voltages, the 2nd @ +25mV overall, but it took a lot longer for them to occur. Anyways from last night to tomorrow, I set the minimum CPU-Freq to 204 Mhz and my device awoke from a perfect deep sleep tomorrow ;). I'll stay on that minimum CPU-Freq for a while now ;) The Battery consumption is still great on a10t, I'll post some screenshots later.
[Nexus 7 Android Development] Ryan_Shea:
Is it normal for 860 to be on 20% of the time, I'm only asking because I've heard so much about 620 being the desired frequency for the best battery life. Jw
[Nexus 7 Android Development] ortrigger:
Sure thing. I'll try and get it tonight.

Sent from my Nexus 7
[Nexus 7 Android Development] Metallice:
No that shouldn't happen. That looks like your max freq was set to 860Mhz. Looks like an app or cyanogenmod performance settings were messing with things.

I'll upload a picture of my cpuspy so you know what it should look like :)

EDIT: Here you go. Interactive 102-1300
[Nexus 7 Android Development] _DrG_:
Tried to roll back to a8/a9 but my cpu governor seems to be broke, the cpu seems to be running a constant 1300 no matter what min setting i have. Great for games but rubbish for battery. Been using jays butter... So went back to a10t increase voltage +25 but had another sod today while in bag for 8 hours was on standby for as long as it took to go sod battery was 87% when stowed away turn back on from the sod battery now 56%. Not good considering i cant roll back either. Please help.
[Nexus 7 Android Development] Metallice:
Did you try raising the min to 204Mhz?

Also I don't really understand how a CPU governor can break.
[Nexus 7 Android Development] h.debnath:
Titanium is working a lot nicer and smoother now however when I flashed colossus, I noticed that my boot time was extremely long and the boot animation was lagging. For some reason it took almost 5 minutes for to come to the lock screen lol
[Nexus 7 Android Development] MetalPainis:
Had a sod @ 204Mhz now too. Mh... Kinda out of ideas now. Had absolutely no issues with a7 but since a8, the sod behaviour is as unexpectable as it can be ;)
[Nexus 7 Android Development] ryanrudolf:
Hello from Philippines. Its almost 3AM here. :)

Just flashed A10C, noticed that when I plug in my USB OTG it is not recognized. Reboot several times same behavior. I tried A10T same behavior. Went back to stock PA 2.53 and USB OTG plus flashdrive working.

Dmesg on A10C / A10T, the USB OTG is detected a hub, which is normal but I noticed there are entries -

smb347_charger: [cable_type_detect] Reg39 : 0x11

smb347_charger: [cable_type_detect] Reg3F : 0x00

If i do a cat /sys/module/tegra_otg/parameters/tegra_otg_on_charging it returns N (disabled i assume). I reenable it using

su -

echo 1 /sys/module/tegra_otg/parameters/tegra_otg_on_charging , and then cat /sys/module/tegra_otg/parameters/tegra_otg_on_charging it shows Y (enabled i assume). Dmesg nothing changed, i still have the smb347 entries.

Disable it again using

echo 0 /sys/module/tegra_otg/parameters/tegra_otg_on_charging and when doing dmesg it now detects my flashdrive as sda.

Issue happens on my flashdrive and usb 3g stick.
[Nexus 7 Android Development] _DrG_:
Sorry mate when i say governor break i really just mean the cpu was stuck on max even when idling even if i changed the governor setting, in my case 1300, i tried 204 min but just picked it up after 1 hour of standby and you guessed it sod :(

Am stuck for ideas now
[Nexus 7 Android Development] Metallice:
First off, you shouldn't be worrying about or messing with "OTG on charging" unless you're using a special Y-shaped OTG cable for charging and OTG at the same time. Is that the case?

Second, are you saying that if you toggle "OTG on charging" on and then off the usb flashdrive works fine from there on out?

Finally, USB OTG works without issue for me. The cable type detection message comes up and then the USB mounts fine. What makes you think the cable detection message is a problem?

Here's my dmesg when attaching a flash drive. How does yours compare?

<6>[ 1270.775954] tegra-ehci tegra-ehci.0: Tegra EHCI Host Controller
<6>[ 1270.777601] tegra-ehci tegra-ehci.0: new USB bus registered, assigned bus number 2
<6>[ 1270.806378] tegra-ehci tegra-ehci.0: irq 52, io mem 0x7d000000
<6>[ 1270.826419] tegra-ehci tegra-ehci.0: USB 2.0 started, EHCI 1.00
<6>[ 1270.827181] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
<6>[ 1270.827489] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
<6>[ 1270.827789] usb usb2: Product: Tegra EHCI Host Controller
<6>[ 1270.828314] usb usb2: Manufacturer: Linux 3.1.10-MKernel-446-620-00764-gd3b2f42-dirty ehci_hcd
<6>[ 1270.828614] usb usb2: SerialNumber: tegra-ehci.0
<6>[ 1270.833108] hub 2-0:1.0: USB hub found
<6>[ 1270.833472] hub 2-0:1.0: 1 port detected
<6>[ 1270.835207] Wake39 for irq=52
<6>[ 1270.835740] Enabling wake39
<6>[ 1271.156472] usb 2-1: new high speed USB device number 2 using tegra-ehci
<6>[ 1271.188467] usb 2-1: New USB device found, idVendor=0781, idProduct=5530
<6>[ 1271.188794] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
<6>[ 1271.189326] usb 2-1: Product: Cruzer
<6>[ 1271.189613] usb 2-1: Manufacturer: SanDisk
<6>[ 1271.189898] usb 2-1: SerialNumber: 20051738101AEE612495
<6>[ 1271.196656] scsi1 : usb-storage 2-1:1.0
<6>[ 1271.356439] INOK=L
<5>[ 1271.357073] smb347_charger: [cable_type_detect] Reg39 : 0x11
<5>[ 1271.357897] smb347_charger: [cable_type_detect] Reg3F : 0x00
<6>[ 1271.358189] USBIN=0
<5>[ 1272.198373] scsi 1:0:0:0: Direct-Access SanDisk Cruzer 1.01 PQ: 0 ANSI: 2
<5>[ 1272.203151] sd 1:0:0:0: [sda] 7821312 512-byte logical blocks: (4.00 GB/3.72 GiB)
<5>[ 1272.205942] sd 1:0:0:0: Attached scsi generic sg0 type 0
<5>[ 1272.206534] sd 1:0:0:0: [sda] Write Protect is off
<7>[ 1272.207082] sd 1:0:0:0: [sda] Mode Sense: 03 00 00 00
<3>[ 1272.208926] sd 1:0:0:0: [sda] No Caching mode page present
<3>[ 1272.209462] sd 1:0:0:0: [sda] Assuming drive cache: write through
<3>[ 1272.217596] sd 1:0:0:0: [sda] No Caching mode page present
<3>[ 1272.217823] sd 1:0:0:0: [sda] Assuming drive cache: write through
<6>[ 1272.230604] sda: sda1
<3>[ 1272.235693] sd 1:0:0:0: [sda] No Caching mode page present
<3>[ 1272.235827] sd 1:0:0:0: [sda] Assuming drive cache: write through
<5>[ 1272.236052] sd 1:0:0:0: [sda] Attached SCSI removable disk
[Nexus 7 Android Development] Metallice:
haha not sure that unexpectable is a word. hmm... meaning you are "able to unexpect" it? It's a strange issue as it seems only a handful of people are suffering... which makes things harder.

Okay well the big change from a7 to a8 was the switch to the new source. If I pm you a straight stock build of the MR1 source (the newest one I'm talking about) can you try it out and let me know if you get SODs?
[Nexus 7 Android Development] Jay Aristide:
Are you saying this is implemented? This is pretty much the only thing stopping me from doing a badass case mod (4 - 32 gb removable MicroSD built into the case back)..

I know you said you'd get to it eventually, but this reads like you have.. Have you? :D
[Nexus 7 Android Development] Metallice:
It should be. No way for me to test it though.
[Nexus 7 Android Development] mobutu16:
Not implemented in a10, working fine with a5.
[Nexus 7 Android Development] benkxda:
Hi Metallice,

I was using your kernel for the Samsung Galaxy Tab 2 7.0 as well. This was my nummero uno kernel for using that tablet. Now I'm glad to know you are active on Nexus 7. I did not test your kernel yet, but will try it within the next days. Just wanted to thank you for your work.
[Nexus 7 Android Development] Alexmessy:
Awch, Idk what could be wrong, Im getting terrible benchmarks, I kniw benchmarks arent that important, but I've never gotten so terrible scores, Im not getting more than 8000 on Antutu O.o but aside of that, the kernel is smooth and gives me very good battery life, but does anyone know if something is wrong??

Im on a10T btw
[Nexus 7 Android Development] Metallice:
Impossible. There's no way you could be charging and using USB OTG at the same time on a5.
[Nexus 7 Android Development] mobutu16:
OMG, with a reply so imperative I must check my USB cable ... You're right, do not know why it did not work both times I made it. Reinstall again and fix permissions and works properly. My apologies.

Thank you for your great work!. Take care.
[Nexus 7 Android Development] Jay Aristide:
I think what he meant was he never patched in usb otg+charging prior to a6, so it would be impossible to charge your tablet and use otg at the same time on a5.

It may be there's some confusion as to what we're talking about here.

OTG

Vs.

OTG+Charging

OTG has been around for a while, and though unmounting was never present in stock 4.1, once you rooted your device, the ability to mount and unmount storage devices was possible through a 3rd party app.

OTG+Charging is a relatively new development that allows you - through the use of a usb y-cable - to use USB OTG *as well as* charge your device. This is a modification that has to be patched into a kernel, but once it's working it's kinda the holy grail for n7 case mods, as a case can now be easily built that includes an external MicroSD slot and doesn't interfere with charging..
[Nexus 7 Android Development] ryanrudolf:
1. Im using normal OTG cable, not the Y-type.

2. Initial test i have to manually toggle the OTG charging to ON-OFF for it to detect my usb devices.

3. For the dmesg, I tried to replicate it again under terminal emulator and it does not detect my flash drive. I disconnected the OTG cable and plugged nexus 7 to laptop to be able to get dmesg via adb. Then when i plugged in again the OTG cable with flashdrive it detected it. It survived several reboots, it now seems fixed. I'll try to reflash again stock PA and then kernel a10T to simulate.
[Nexus 7 Android Development] mu3g:
OTG, OTG+Charging support

In addition to a few questions and answers being discussed on this thread, can anyone confirm the following for me:

1. Does this kernel support USB-OTG?

2. If yes, does this kernel support USB-OTG AND charging simultaneously? Would this be done by a Y-Cable?

3. Lastly, does this kernel support USB-DAC? If yes, does this require the USB-DAC to be connected at reboot? Is there an easy toggle to swap modes between USB-DAC and USB-OTG when on this kernel?

I run on the stock 4.1.2 ROM. I'll be moving to SmoothROM, CleanROM or one of those simplistic tablet UI based ROMS in the near future. Personal ROM recommendations are welcome! I'd prefer a bug-free ROM as I spend way too much time screwing around with my HTC Inspire 4G.

Thank you!!
[Nexus 7 Android Development] Warrior1975:
Thank you Mettalice. Flashed A10t last and its running perfectly on AOKP M1. Very snappy.
[Nexus 7 Android Development] Jay Aristide:
1) Yes. All 4.1+ Nexus kernels support USB-OTG

2) According to Metallice, yes. And, yes.

3) I don't think so, nor do I know how much app support there is/would be for such a feature. Were such a feature to exist, I'd imagine the device would have to be present at startup so oss knows what to do, and the kernel would pretty much auto-detect anything else once connected.

I *suppose* oss/alsa/whatever android uses could auto-detect a usb-dac device, but I'm not sure how easy it would be to code, or what could become of actually stopping and restarting the audio subsystem... In linux it can be done with little fuss, but here, things are a little more close-quartered..

Stay on stock, IMO, if you're looking for the fastest, most fluid, least troublesome experience.
[Nexus 7 Android Development] mu3g:
I have a USB-DAC hooked up to my laptop running Linux Mint. I was able to configure swapping between my audio out and USB out fairly easily. Let's hope this happens on future releases on this kernel! It's been a good 1 hour and I'm liking it.
[Nexus 7 Android Development] Metallice:
1. Yes.

2. It should, but I have no way to test.

3. It should, but I have no way to test. USB audio is enabled in kernel config. It must be connected at boot to work. If its not working it may be due to a specific driver for that DAC I need to enable in the config.
[Nexus 7 Android Development] Metallice:
a11 up. Based on T version, which, in addition to Titan, stood for tegra autohotplug. Seems people like it more than the C version, which, in addition to Colossus, stood for cpuquiet. May try cpuquiet without runnable threads in the future, but for now, sticking with the standard hotplugging.
[Nexus 7 Android Development] ortrigger:
Hey, I got a dmesg and logcat for you from my tab. I'm not sure how much good they'll do you because I can't actually replicate the sod right now but there may be something that can help. Here's the link.
[Nexus 7 Android Development] Metallice:
Thanks. Unfortunately dmesg, a kernel "event viewer", isn't much help without the "event".

Last_kmesg after a sod would be ideal.
[Nexus 7 Android Development] Metallice:
200 downloads and no comments. I'll take that as a sign that a11 is running well :D
[Nexus 7 Android Development] phonic:
I'm assuming this won't work properly on 4.2, right?
[Nexus 7 Android Development] ortrigger:
I attempted to get last_kmesg but couldn't remember exactly how. If it happens again I'll make sure to grab it for you though. A11 is pretty slick though. Highest quadrant benchmark I've ever had for what it's worth.
[Nexus 7 Android Development] Metallice:
Very, very little :)

oh and the command from PC would be - adb shell "cat /proc/last_kmsg > /sdcard/last_kmsg.txt" which will put the long in the root of your internal sdcard.
[Nexus 7 Android Development] mrbeardy:
a11 seems the fastest so far, no idea about battery drain yet
[Nexus 7 Android Development] adstraylight:
Just had a SOD with a11, last kmsg attached.

View attachment last_kmsg.zip
[Nexus 7 Android Development] Jay Aristide:
This.

I'm on 4.2 now. Will a10-11 work?
[Nexus 7 Android Development] Metallice:
Someone needs to try it and find out :) Make a backup of your boot.IMG in TWRP so you can revert if something goes wrong.

But... my guess would be no.
[Nexus 7 Android Development] Jay Aristide:
I can root without it, and don't have TWRP (just don't quite trust it, yet), so I'll wait until they release the kernel source for 4.2 and you build from that :)
[Nexus 7 Android Development] opz187:
Google just released the 4.2 source like 2 min ago
[Nexus 7 Android Development] chaplinb:
Just flashed 10t yesterday and thought it couldn't possibly get any better. Now a11 is out. You're the kernel developer that just keeps giving :D.

Cheers dude.
[Nexus 7 Android Development] krazeecracker:
Honestly is there a HUGE benefit to 520 instead of 446?
[Nexus 7 Android Development] Kearkan:
In my experience, yes, especially for games not optimized for Tegra (eg nova 3 before they patched it) if you really want to see the effect gpu speed can have, flash the trinity gpu overclock kernel or faux and kick it up to 700mhz and open nfs most wanted and you'll notice the difference.

If you only play less graphic intensive games, or Tegra games, and do non game related stuff then there's no point.

I find the 520 can use more battery generally too, so I run the 446 and just flash 520 when I want to play games.

Addition: has anyone tried this kernel with 4.2 yet?
[Nexus 7 Android Development] Jay Aristide:
Yes, but at the [rather hefty] price of battery life. Pretty much anything you throw at it at that GPU click will run like melted butter. If you undervolt by 75mV it doesn't level it out, but it makes a big difference...

For those wondering, BTW, 4.2 is REALLY nice.. A lot of stuff broken, though..

I'm on a debloated stock, rooted with two users. Apps are NOT shared, BTW.
[Nexus 7 Android Development] ortrigger:
+1 to your comment about 4.2 I haven't noticed anything broken but I've only been using it for a few hours.
[Nexus 7 Android Development] krazeecracker:
Not too concerned about battery life as I'm always by a charger. 446 works well for Tegra games. But seeing as how I just bought nfsmw. I might need the 520 to smooth it out?
[Nexus 7 Android Development] Jay Aristide:
NFS:MW works pretty good for me on 446..That's still OC'd from stock. I'll let you know how it runs on 4.2 here shortly after Order and Chaos installs
[Nexus 7 Android Development] phonic:
The App APKs are shared. They simply don't "install" for that user by default. They are still on the system, and if User2 tries to install them, they instantly "download" (it just uses the existing apks), but keeps the config and other data separate. This is good if you think about it. Do you really want all the users to see every other users apps when they install them? If your wife/daughter/son/girl-friend/etc. installs a bunch of stupid crap, do you want them in your app list? If you want to use the same apps you can, but if you don't, you don't have to. And it doesn't take up any extra storage space.
[Nexus 7 Android Development] ryanrudolf:
For meantime I'll just stick to PA2.54 until google releases a 4.2.x. PA2.54 and A11 works ok for me. Thanks very much. No sod yet.
[Nexus 7 Android Development] Ricolein_Rico:
a11 vs. a10t

a11 generally feels a bit less snappy on my N7 (stock 4.1.2, 102-1300 Mhz, interactive + Jay's magic with 64 Mb zram), battery life is marginally better (e.g. almost no loss in overnight deep sleep compared to ~2% loss with a10t). When completely closing apps via app-info I get more temporary screen freezes with a11.

Strange issue with a11: After overnight deep sleep the max. CPU frequency was somehow automatically reduced to 700 Mhz, though my max setting was at 1300 Mhz and SetCPU was running and supposed to keep it at 1300 Mhz?

On the whole I prefer a10t but let's see how things will evolve with 4.2 ...
[Nexus 7 Android Development] chaplinb:
TBH I find that my tablet doesn't appreciate anything Above 420 when it comes to the GPU. I get better performance on the lower GPU speed kernel. It's device specific though, of course all the chips are slightly different and therefore work better with different clock speeds xD
[Nexus 7 Android Development] $wissdroid:
Hey Metallice

What for an Amazing Kernel are you doing :D

I'm on Version a9 and Battery Life and Smoothness is Great :)

After 2 Days 14 Hours without Charge & 9.5 hours Screen-on-Time i must bring my Nexus to 'Loading-Station' :) --> Without UV.

Actually i use Baked Rom #6.

Much Respect. So Please let the Nexus Rock the Future with your Kernel.

One Question: Is it Possible to integrating Auto-Wifi Off when Screen turn Off?

As an Example is Dorimanx Kernel in the Galaxy S2.
[Nexus 7 Android Development] DZonikg:
I guess i was lucky,mine works even 700 GPY all day long :D And i read so many sods on different threads ,i flashed so man different kernels and had only one single SOD since i bought nexus 7.
[Nexus 7 Android Development] Jay Aristide:
So, I'm on stock 4.2, rooted, and I've noticed something..

I was under the impression that flash was screwed up in a10/a11 because they're built from a new source, but I'm on the 4.2 stock kernel and flash works perfectly..

Just thought I'd share
[Nexus 7 Android Development] stonebear:
I got my first sod ever with M-kernel series and it was with a11. I was still using 4.1.2 at the time (CleanRom), I haven't tried it with 4.2, probably won't until you release kernel for it.

:)

---------- Post added at 07:35 PM ---------- Previous post was at 07:03 PM ----------

I think TWRP is trustworthy, I had a mental block about it but now I wouldn't go back to CWM for this device. :)
[Nexus 7 Android Development] Metallice:
Yeah its a custom kernel issue. Pretty sure every custom kernel has it. At the moment I don't know what causes this, nor do I think anyone else does.
[Nexus 7 Android Development] Metallice:
Can't release a new kernel without new source.
[Nexus 7 Android Development] Metallice:
You're free to modify the interactive parameters yourself if you want more performance like alpha 10t with an app like setcpu. Lower gohispeed load, raise touch freq, etc.
[Nexus 7 Android Development] Metallice:
The issue with a11 and 4.2 is probably the ramdisk. The multiuser stuff changes the mounting stuff around.

Can't get to fixing that at the moment. Sorry. Have a biochemistry test and my interview at Jefferson Med tomorrow. Time to suit up.
[Nexus 7 Android Development] Kearkan:
In sure I speak for all of us when I say good luck mate! And we all understand important stuff comes first, m kernel 12 will be worth the wait anyway =)
[Nexus 7 Android Development] opz187:
Wow dude I just read this about cyanogenmod http://www.cyanogenmod.org/blog/psa-transition-to-cyanogenmod-org today is so sad.
[Nexus 7 Android Development] Stuphologist:
Good luck!
[Nexus 7 Android Development] eugenechiuu:
Wow good luck man.. future medic and kernel developer just doesnt correlate for me lol
[Nexus 7 Android Development] Metallice:
I like knowing how things work. Fixing and making them better. I don't think they are that different.
[Nexus 7 Android Development] mobutu16:
Thanks for your explain and ....good luck Metallice!
[Nexus 7 Android Development] stonebear:
No rush. :) Good luck with your exam and interview.
[Nexus 7 Android Development] krazeecracker:
How's 446 for everyone? Smooth here lol
[Nexus 7 Android Development] Alexmessy:
Almost perfect, except that I notice more battery drain than with a10T? O.o
[Nexus 7 Android Development] mobutu16:
Any with boot hangs? Stock rooted and a11, nothing more...
[Nexus 7 Android Development] Metallice:
Alright... I made it out alive... Although I think my biochemistry grade might have taken some collateral damage from the interview. Oh well. Need to get my mind of school and my efforts to have the privilege of one day being $300,000 debt making $40,000 a year (in the beginning). Thank god I'm not in it for the money...

So... to take my mind off things... Guess I'll make some kernels then. Stay tuned :)

By the way it looks like the source I built on starting with alpha 8 IS actually the 4.2 source. Hah. I guess I was a week or so ahead of the game. Only reason alpha 11 doesn't work is the ramdisk because of the multiuser sdcard mounting.
[Nexus 7 Android Development] bonzer2u:
congrats and look forward to your blessed 4.2 release