yashsingh1/xdaforums huggingface dataset:
[Nexus 10 Original Android Development] morfic:
While i have not had a chance to add anything new that i want to work on i did add ntfs back in and merged steve kondik's usb dac fix.

Fiio E10 now plays nice on Nexus 10, easy audio internal <-> usb dac rerouting on plug/unplug.

http://goo.gl/kSR7aA TX15

The UV is not back in yet in this one.

I Think I'll mark it somehow when i have it back in.
[Nexus 10 Original Android Development] morfic:
CM does pretty good at 2000MHz.

Sound never hiccuped during the benchmarks, not that it should, just glad it really doesn't.
[Nexus 10 Original Android Development] abdel12345:
So which is the best version to use with 4.3 because on your. Website theyre all under experimental release (sorry if im mistaken). Tx3, tx11, or tx15? :confused:

Sent from my LG-P970g
[Nexus 10 Original Android Development] morfic:
they are all just releases, non final states as 4.3 is new, but there is no better or worse builds other than what you find does or does not work stable for you.

But since you are asking I'd start with TX3 and then watch the thread for info on what you want to flash next.

It's a slow thread, reading a little backwards will catch you up quickly.
[Nexus 10 Original Android Development] tb01110100:
What benchmark (?) is that?

-------------------------------------------------------------------------------------

Sent from my Nexus 10

Devices:

Nexus 10 - Paranoid Android 3.98 - Der Kernel 3X

Nook Tablet - CM 10.2 - NOF Showtime Kernel
[Nexus 10 Original Android Development] iamikon:
Quadrant.
[Nexus 10 Original Android Development] :
Hope you are well again.

While testing over the weekend, I found:

1. When connected to pogo charger antutu always crashes - regardless which version I use.

2. Ondemand/deadline is more stable than interactive/cfq: the latter crashes always (interactive/dealine is inbetween - crashes sometimes)

3. 12d seems to be most stable on my device. No time to test 15 at the moment. (Besifes my own testbuild with the adjusted cflags - which runs antutu most often in row withput crash.)

Edit: Is there a sysfs or proc cpu temprature interface? Or is it eseay to implement?
[Nexus 10 Original Android Development] morfic:
Interesting observations.

And I'm feeling unchanged.

Yes,I plan to expose the temperature it uses internally, so we can see temperature on nexus 10, like on other devices.
[Nexus 10 Original Android Development] stonebear:
I am using interactive/sio and it doesn't seem unstable.
[Nexus 10 Original Android Development] dodo99x:
TX15 @ 2000mhz, performance/deadline, 8/22RBJ
[Nexus 10 Original Android Development] brees75:
Interactive/sio is my choice for performance and stability. That is all I run with Trinity and I have never had issues. I use pretty aggressive tweaks for both of them as well.
[Nexus 10 Original Android Development] abdel12345:
OK thanks. Since it doesn't require a data wipe like Roms I'll take your advice and just try them all. :)
[Nexus 10 Original Android Development] sttovo:
Hey brees, I used a lot of the tweaks you documented for 4.2.x, but they don't seem to match up in 4.3. Could you post your 4.3 tweaks? Assuming you're still doing init.d tweaks?

Pretty please, sugar on top?
[Nexus 10 Original Android Development] brees75:
Actually My wife is taking the kids on a little vacation to her friends later this week and I will have the house to myself with a couple days off so I am at the very least going to make a flashable tweak pack that I will share. My real goal is to put together a 4.3 Linaro beast of a ROM and if I am sober long enough to finish the yard work she has lined up for me it will happen. LOL :D Still finding the sweet spot for 4.3.
[Nexus 10 Original Android Development] htctouchelfin:
Hi, is it only for me that n10 can keep the oc? after some time that i have set max oc to 2 ghz i found it is on 1,7 :(
[Nexus 10 Original Android Development] stonebear:
Use Trickster, it has a setting to keep the frequency.
[Nexus 10 Original Android Development] szale9001:
I've been getting occasional WiFi drops (grey bars). Is this a known 4.3 thing or a kernel thing?
[Nexus 10 Original Android Development] morfic:
Apps like the Trinity Kernel Toolbox protect max from being changed by the OS.
[Nexus 10 Original Android Development] anirudh412:
Grey bars does not mean a Wifi drop, but simply that you aren't connected to Google services. Nothing related to the kernel or ROM.
[Nexus 10 Original Android Development] szale9001:
Well in this case, grey bars means no connection to anything. No websites or data at all. Not just Google.
[Nexus 10 Original Android Development] hanspampel:
Afaik this is not correct. You only have no google sync with grey bars. Internet works fine. I had this alot of time and my internet works fine there.
[Nexus 10 Original Android Development] lynnux:
This has happened to me on various roms/devices, only at home, and it was always a problem with my router. Rebooting it would fix it, sometimes it would go away on its own after a few hours.
[Nexus 10 Original Android Development] EniGmA1987:
While it does mean you are not synced to Google services, nearly every time I get the grey bars on either a tablet or my Galaxy Nexus phone then I also have 0 data in or out of the phone as well. Toggling wifi on and off will usually allow data to work again and the bars will be blue. I can also most of the time go into my Gmail and Google voice and do a manual sync and suddenly the bars will be blue and data starts working again. It is actually quite common for a lot of people with the grey bars to have no data. What I do not know is whether the bars turn grey and out of sync because it is a data problem with either the kernel or ROM, or if a sync issue with Google is causing the data to not function until sync is restored. I mostly get this problem at one of our warehouse locations at work, but every once in a while it also happens at home too. And even more rare is when it happens on regular data and not using wifi. In that case toggling airplane mode on and off will restore data connection.
[Nexus 10 Original Android Development] szale9001:
^ This lol. Yea, I was just thinking it might have been a 4.3 kernel related issue because it started happening around the same time I upgraded to 4.3. It behaves enough that It's not a huge issue. I was just curious to know whether it was a known problem or not.
[Nexus 10 Original Android Development] n0j0e:
I has this problem also with gray WLAN bars and no data in/out. But was not kernel related. It was a little update from Buttered AOKP Rom. Tried many things, delete Google Account, using other TWRP Recovery versions, nothing helps. Restored backup and waiting now for AOKP 4.3.

* Send with much love & Android. * (HTC One S)
[Nexus 10 Original Android Development] hospital349:
[MENTION=1122306]morfic[/MENTION]

Thanks for working so hard on your mantaray Kernel. I've been observing this thread and it's contents on a daily basis. It's been a somewhat interesting journey to date.

Just a quick question regarding TX13 & TX15: Did you change anything that might effect performance between the two builds? - It's just that I have been switching between both builds every so often to experience the feel/experience of each. I have noticed that TX13 feels a little snappier/smoother (using default settings on both). There seems to be a slight stuttering whilst using TX15 on certain apps (e.g. Google+ & Google Play Music) and the same isn't noticeable whilst using TX13.

I'm currently using the latest RBJ build and have very recently performed a full wipe, via Google's Factory Image.

I hope I'm not the only person to notice this difference, as it's something I feel quite strongly about after long-term usage.

Thanks again. :good:
[Nexus 10 Original Android Development] anirudh412:
Wrong. In any Android build, grey bars, be it signal or wifi indicates device not connected to Google services. There is no provision for Android to indicate that you have lost data. However an indication of data transfer would be the one/two arrows that show up within the signal or wifi bars. Now since this (mostly) happens when there is a problem with the data connection, I can see why you would think otherwise.
[Nexus 10 Original Android Development] szale9001:
I get that. I was only trying to say that everytime I get gray bars I also have no data whatsoever. The fact that the bars are gray isn't important to me anyway, its the fact that I am losing data constantly. In the mean time I am trying to mess with certain router settings to see if I can stabilize it. I was only curious if others had experienced the data loss phenomenon as I had when upgrading to 4.3
[Nexus 10 Original Android Development] phillysmako:
After reading your post I decided to give tx13 a go and I have to say i 100% agree with you!!!! Huge difference:good::D
[Nexus 10 Original Android Development] brees75:
I think I might have found the cause for antutu crashing. Can everyone check build.prop and make sure this value is enabled?

dalvik.vm.verify-bytecode

Make sure it is set to true.

It will slow things down a little at first but once everything is cached it won't make a difference.

It could be a fluke so if it can be confirmed either way it will be appreciated.
[Nexus 10 Original Android Development] hospital349:
dalvik.vm.verify-bytecode

This doesn't exist in my build.prop file at all.

Is this ROM or Kernel related?

If this line should in fact be present, is it something that a Kernel developer or ROM developer needs to be informed of?
[Nexus 10 Original Android Development] brees75:
No, generally it's disabled but it seems the latest antutu doesn't like it. If antutu has been crashing for you add that and see if it helps. Just copy and paste this to the bottom of your build.prop:

dalvik.vm.verify-bytecode=true
[Nexus 10 Original Android Development] hospital349:
dalvik.vm.verify-bytecode=true

Thanks for the heads-up. I'll add it and see how things go.
[Nexus 10 Original Android Development] b1g.p0ppa:
I tried it on makelegs' 0831 build running TX13 and Antutu caused a reboot both with and without that setting in build.prop. Could be something unique to the ROM though because I don't remember anyone reporting antutu was causing full-on reboots.
[Nexus 10 Original Android Development] stonebear:
It was causing them for me and others too.
[Nexus 10 Original Android Development] zerocool79346:
So I had some seriously weird behavior last night/this morning after flashing TX11 stable. Flashed it last night onto the stock ROM and got bootloops galore. Shut it down and figured I'd mess with it today.

Well fast forward to noon and I walk into see my should be turned off tablet stuck on the Google splash screen. Guessing from the temp of the device I'd say it's been stuck there for a few hours. Now here's where it gets really strange, held the power and volume button for 10 seconds hoping to get it to boot into fastboot and somehow managed to get the damn thing to reboot all the way.

From what I can tell, it had never been rebooted fully since flashing the kernel 12 hours before (it rebuilt dalvik and cache) but it's acting like nothing ever happened. Anyone have some insights that I'm missing?

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

Spoke too soon. Back to reboot city. I'm completely lost as to what is causing it.

Guessing voltages caused it. Managed to boot long enough to get KTmanta on and no issues thus far with it. I'll be back to play with this when I've got more free time to trouble shoot. Always loved Trinity on the GNexus, keep up the good work Morfic.
[Nexus 10 Original Android Development] morfic:
http://goo.gl/0HfV23 TX17 does not address anything compared to TX15, it does however add something for blind testing.

Those who notice diminished performance, it's likely the heavier throttling.

Those still rebooting likely notice the throttling is not efficient enough to keep them from an emergency reboot.

grab your /proc/last_kmsg and look for temperatures at the end of the log.

I'm feeling a 1700MHz old throttling coming up in the near future, containing the same blind test commit that is in this one.
[Nexus 10 Original Android Development] newellj79:
I've been using tx17 for a day and it seems extremely stable on my device.

Edit... Running latest carbon nightly.
[Nexus 10 Original Android Development] dodo99x:
No reboots or anything weird so far on TX17 (on stock rom, interactive/deadline, 1.7GHz) :thumbup:
[Nexus 10 Original Android Development] phillysmako:
TX17 is running good thanks Mr. Popular :p
[Nexus 10 Original Android Development] stonebear:
No issues here either, been using it at 1.2 Ghz, interactive and SIO as is my wont. :)
[Nexus 10 Original Android Development] tb01110100:
How... Um, /safe/ is it to OC to 2GHz? I sorta want to do it, but I'm also sorta scared. :P

-------------------------

My devices:

Nexus 10 - Stock Rooted

Nook Tablet - CM10.1
[Nexus 10 Original Android Development] newellj79:
I won't comment on how safe it is but for what its worth in benchmarks my tablet scores higher at 1500 than 1800... By the way tx17 has been flawless for me!
[Nexus 10 Original Android Development] phillysmako:
It handles it perfectly in my opinion, murders your battery tho:)
[Nexus 10 Original Android Development] G-Bus:
Hey everybody,

I just installed this kernel, coming from francos r13 and before that project flaming moneys kernel. Overall i do a lot of gaming such as vice city and rr3. Im on tx17 and so far so good however my tablet runs much hotter, compared to francos or flaming monkeys. I guess its due to gpu overclock?
[Nexus 10 Original Android Development] brees75:
AHHHH! It's the FrankenMorfic!!! RUN!!!! We're all going to DIE!!!!!!!!!
[Nexus 10 Original Android Development] kylealanr:
Did you make sure to flash back the stock kernel or the ROM you're using before flashing all these? Franco and Trinity modify the ramdisk, so you have to make sure to flash another kernel in between. If you don't want to flash the ROM again, just find the boot.img in the zip and flash it with adb.
[Nexus 10 Original Android Development] G-Bus:
I wasnt aware of that. If I flash a stock kernel back in between is it okay?
[Nexus 10 Original Android Development] kylealanr:
Yes, just find the kernel included in your ROM, or get the stock one. If you run something like CM 10.2 nightlies you can just flash the new nightly, reboot, and flash the new kernel. Or download flashify from the play store and backup your original kernel and use the app to restore it in between changing kernels.
[Nexus 10 Original Android Development] G-Bus:
Thanks for the heads up man! I will try and report back. It doesnt heat as much as stock 4.1 roms did but its hotter than others.
[Nexus 10 Original Android Development] newellj79:
Are most people using on demand as there governor? If so I was wondering if anyone had played around with the governor settings and had recommendations? Not that mine isn't flying already, but I never mind doing some tweaking. :)
[Nexus 10 Original Android Development] rlattin24:
Is therea mirror link for this?

The requested URL /simms/TX17-4.3-2000-ANY.zip was not found on this server.
[Nexus 10 Original Android Development] tb01110100:
Here's a quick mirror I made: http://72.49.13.20/TX17-4.3-2000-ANY.zip

Edit: My ISP decided to be a jerk and change my IP address. I fixed the mirror link. :P

-------------------------

My devices:

Nexus 10 - Stock Rooted

Nook Tablet - CM10.1
[Nexus 10 Original Android Development] morfic:
Since my n10 refuses to take a charge, there won't be much verified work coming. Still got 2 more things to try, pogo cable and new battery (if I can locate one), but for right now....sucks.
[Nexus 10 Original Android Development] iamikon:
Have you just tried a different cord?? I know it sounds dumb but I've found sanmsung cords to be weak. Glad I kept my old blackberry ones.
[Nexus 10 Original Android Development] rlattin24:
thanks
[Nexus 10 Original Android Development] stonebear:
Oh no, that does suck!
[Nexus 10 Original Android Development] morfic:
Three cables (one part of a Jabra charger), three chargers, both cables also via usb.

I see it gets power through them, only then the empty battery icon lights up when power is pressed.

I tried up to disconnecting the battery as often suggested.

Nothing makes a difference.
[Nexus 10 Original Android Development] sttovo:
If it's any help, this happened to my wife's iphone. I found something online (which means it's true :) ), that putting the device in the freezer for a few hours somehow fixes the charging problem. I wasn't brave enough to try the freezer, so I used the fridge part. I also put the phone in a ziplock bag. Amazingly it worked. But, please only do what you're comfortable doing to your N10.
[Nexus 10 Original Android Development] stonebear:
I hope is still under warranty?
[Nexus 10 Original Android Development] newellj79:
Damn...
[Nexus 10 Original Android Development] morfic:
Did I forget to mention I went as far as disconnecting the battery?

Seemed reasonable as that brings the n4 back out of a low battery situation, a link I found confirmed it as a solution for the n10.

So I doubt it's under warranty now.
[Nexus 10 Original Android Development] stonebear:
I missed that bit, sorry.
[Nexus 10 Original Android Development] morfic:
No worries.

Unless you broke my Ten!
[Nexus 10 Original Android Development] monkfish_lad:
This has happened to my N10 at least twice since I have had it. I called Google and they said to leave it plugged in for 48 hours. I did this and it still would not boot so I left it for another day and finally it booted (still showing an empty battery). Never let my N10 run out of battery now.....
[Nexus 10 Original Android Development] stonebear:
lol, not guilty!
[Nexus 10 Original Android Development] morfic:
Either you are a god damn genius or the time it spent unplugged was what it needed. (Charged my 7"over night, n10 laid unplugged until I tossed it into freezer)

Got it out of freezer now and for the first time, haptic feedback.

Empty battery sign on a full brightness screen and shortly after the animation of a charging battery was back.

I hate this empty battery design flaw.

Now if it survives the being fûcking cold out of its freezer bag condensation risk I'll be back in business.
[Nexus 10 Original Android Development] morfic:
It was plugged when it ran out, was watching Netflix, so battery want visible when I unplugged it to take it with me to kitchen.

Needless to say, this HTC charger left the building
[Nexus 10 Original Android Development] sttovo:
Awesome news! Glad you got it working again!

PS - I'm OK with genius, been a rough week, need a little positive feedback :)
[Nexus 10 Original Android Development] stonebear:
If it helps - I think your a genius too. :angel:

Nice one, Morfic has a working N10, good news for all of us! :)
[Nexus 10 Original Android Development] brees75:
Glad you got it working!

For those of us that don't OC the CPU, can we please get the latest kernel with UV added back?
[Nexus 10 Original Android Development] morfic:
Now if it holds a charge so I can test kernels, sure, been taking care of other nexii lately, time to crack down on that n10 todo.
[Nexus 10 Original Android Development] morfic:
Like new, well, minus one screw :P

Was fully charged when I got home.

Just in case it's true that a pogo charge cable will charge from 0, I should grab one.

:)
[Nexus 10 Original Android Development] cien12:
Good news that your Nexus 10 working again.

I have an other simple question:

Is it really no preference whether a rom based on JSS or JWR for the kernel?

Works the Trinity Kernel with both ROM Types without problems?
[Nexus 10 Original Android Development] brGabriel:
I actually just had the same problem with my N10 not holding a charge a few days ago. First thing I thought to do was buy a pogo charger. When that didn't work, I gave up and decided to take it back to where I purchased it, with my original receipt, and try to exchange it for a new device.

So, a few days later I did a complete format of all data on the internal SD (basically every wipe possible through TWRP), and resigned myself to bring it back. But before doing so, I decided to give it one last try. After booting up, I plugged in my charger and let it sit. To my surprise it actually began to charge again. :eek:

I never fully understood why (I initially assumed it had to be some hardware failure), but l now wonder since the full format of system and internal sd seemed to fix the problem. (May have only been coincidental) But Its been running and charging great ever since. :fingers-crossed:
[Nexus 10 Original Android Development] rodeo_calling:
Man, never knew manta had such problems. Gonna be careful from now on.

I'm fairly new to this kernel. Where do I download the latest one? The OP link lists TX11 as the latest, but following the thread, I believe it's TX17? The link to that takes me nowhere :what:
[Nexus 10 Original Android Development] brGabriel:
TX17 may have only been a test build and has since been removed. TX11 is still running great.

http://www.derkernel.com/jb-manta.php
[Nexus 10 Original Android Development] rodeo_calling:
Oh so TX11 is the latest? Gonna try it now with purity. Thanks.
[Nexus 10 Original Android Development] VertigoOneX:
Op says: Use an app that protects the sysfs files to not have OS meddle with freqs.

Which one for example?
[Nexus 10 Original Android Development] newellj79:
Trickstermod
[Nexus 10 Original Android Development] dreitzell78:
I'm running TX17.. running great. Someone posted mirror a few pages back .. Here is the link... http://xdaforums.com/showthread.php?p=45466390
[Nexus 10 Original Android Development] tb01110100:
My ISP decided to be a jerk and change my IP address. I fixed the mirror.

-------------------------

My devices:

Nexus 10 - Stock Rooted

Nook Tablet - CM10.1
[Nexus 10 Original Android Development] stonebear:
Good job, thanks man. I am still using 17 myself with Purity ROM and liking it. :)

I suggest using 1.2 Ghz max CPU and letting the 620 Mhz OC of the GPU do the work. I also like SIO and a 512mb read ahead and Interactive governor.

Just for people new to the thread. Some of us veterans use these settings, lol. :)
[Nexus 10 Original Android Development] newellj79:
Testing some of those settings for liking. Thanks!
[Nexus 10 Original Android Development] stonebear:
Cool, you should find the 1.2 cpu to be just as snappy in general use as 1.7 ghz.

It will also play videos etc just as well and stop the cpu hitting 1.7 for no reason.

Stops thermal throttling in games...
[Nexus 10 Original Android Development] tb01110100:
Can Franco Kernel updater be used for tweaking, or is it better to use some other app?

-------------------------

My devices:

Nexus 10 - Stock Rooted

Nook Tablet - CM10.1
[Nexus 10 Original Android Development] b1g.p0ppa:
Not sure what all franco's can do but you'll have the best experience on this kernel using this kernel's developer's toolkit. It's called Trinity Kernel Toolbox and it's available in the Play Store.
[Nexus 10 Original Android Development] morfic:
Funny, i watch Videos at 800 or 1000MHz, and 600MHz when on a plane and can't charge it for 10+ hours

No, not saying UI would be fun at 600MHz, but battery will be happy.

no, that's a lie, *I* was happy to have plenty of battery to make it through the flight
[Nexus 10 Original Android Development] morfic:
No need for mirror, it's on www.derkernel.com
[Nexus 10 Original Android Development] stonebear:
I know, I just think 1.2 is a good compromise. Videos would play fine at much less yes.
[Nexus 10 Original Android Development] morfic:
I want to add clock profiles to TKT just for that.

Been thinking about it ever since watching netflix at 600MHz.
[Nexus 10 Original Android Development] stonebear:
That would be cool.

The chips in this thing are so powerful yet so mismanaged.
[Nexus 10 Original Android Development] tb01110100:
Just thought I'd share some settings that I like. They aren't too hard on the battery, while giving you decent performance.

2000MHz max

Interactive governor

SIO I/O Scheduler

-------------------------

My devices:

Nexus 10 - Stock Rooted

Nook Tablet - CM10.1