yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] flar2:
^^No worries, feel free to discuss things in the thread. I encourage people to post often and help each other out.

****************************

I haven't yet had a chance to look at charge + OTG, but I'm looking forward to it. Figuring out that kind of stuff is actually fun to me. But I need a good chunk of time to sit down and get started.

I also haven't forgotten the usb 3g modem driver.

****************************

Now for CIFS:

Now that I look at it, this is really hard. My installer tries to do it, but it must not be working for everyone.

You need to have this line in your ramdisk:

# Create mountpoint so Dalvik can mark as slave in zygotes.
mount tmpfs tmpfs /storage mode=0050,uid=0,gid=1028

It goes a file called init.rc

And you can't just place it at the end, it needs to be earlier in the file.

It needs to be place somewhere around these lines, like so:

mkdir /system
mkdir /data 0771 system system
mkdir /cache 0770 system cache
mkdir /config 0500 root root

# See storage config details at http://source.android.com/tech/storage/
mkdir /mnt/shell 0700 shell shell
mkdir /storage 0050 root sdcard_r

# Create mountpoint so Dalvik can mark as slave in zygotes.
mount tmpfs tmpfs /storage mode=0050,uid=0,gid=1028

# Directory for putting things only root should see.
mkdir /mnt/secure 0700 root root
# Create private mountpoint so we can MS_MOVE from staging
mount tmpfs tmpfs /mnt/secure mode=0700,uid=0,gid=0

# Directory for staging bindmounts
mkdir /mnt/secure/staging 0700 root root

The first thing you should do is make a nandroid backup of your boot.img.

In order to edit the ramdisk you need to do the following in adb shell:

Grab the abootimg binary from my installer zip and copy it to /system/bin/

Then become root and make it executable:

su
chmod 777 /system/bin/abootimg

Then make a new directory to work in and get your boot.img:

mkdir /sdcard/bootfix
cd /sdcard/bootfix
dd if=/dev/block/mmcblk0p14 of=boot.img

Now unpack the boot.img and extract the ramdisk:

abootimg -x boot.img
mkdir ramdisk
cp initrd.img ramdisk/initrd.gz
cd ramdisk/
gunzip -c initrd.gz | cpio -i
rm initrd.gz
rm ../initrd.img

Now you can edit init.rc, either by using vi or opening it with a text editor on your tablet. Just add the line like I show above.

Then repack the ramdisk and boot.img:

find . | cpio -o -H newc | gzip > ../initrd.img
cd ..
abootimg -u boot.img -r initrd.img

reinstall the boot.img

dd if=boot.img of=/dev/block/mmcblk0p14

Then reboot and it should work. If something got screwed up, reboot to recovery and restore your boot.img from nandroid backup.

If this seems like too much, I'm pretty sure you can mount windows shares with ES File Explorer. Then you don't need cifsmanager.

When I get a chance, I'll download a few of the popular ROMs and make sure the installer works in every case.
[Nexus 7 (2013) Original Android Development] mrdingding:
Thanks flar2!!!!

I have some problem while unzipping the initrd.gz. I was able to extract the init.rc and added the lines, but the repacked boot.img doesn't work. Here's the message while unzipping:

root@flo:/sdcard/bootfix/ramdisk # gunzip -c initrd.gz | cpio -i
cpio: ueventd.rc not created: newer or same age file exists
cpio: ueventd.flo.rc not created: newer or same age file exists
cpio: seapp_contexts not created: newer or same age file exists
cpio: can't create symlink from sbin/watchdogd to ../init: Function not implemented
cpio: can't create symlink from sbin/ueventd to ../init: Function not implemented
cpio: sbin/adbd not created: newer or same age file exists
1426 blocks
root@flo:/sdcard/bootfix/ramdisk #
[Nexus 7 (2013) Original Android Development] irekz:
flar2: thanks!

followed the script but device could not boot (could not get past google logo) so something must have went wrong.

Had no issues or errors with issuing all commands so was hopeful - but no joy this time.

Had to issue all commands when device was in recovery mode as when it's running access to /system/bin is in read-only mode.

I doubt this makes any difference but it might.

Thank you for your time!

Cheers,

Irek
[Nexus 7 (2013) Original Android Development] mystifiyer:
Hi All,

Is there any particular reason why GPU speed is capped at 487Mhz in most kernels including this one when some kernels allowed at a max of 533Mhz?

Is there a way to increase this cap? Mine is stable at 533Mhz when I tested with another kernel earlier.

Thanks
[Nexus 7 (2013) Original Android Development] tiny4579:
Just because it may be stable doesn't mean it will help anything. Any evidence 533 was faster in benchmarks for you in the other kernels you used?
[Nexus 7 (2013) Original Android Development] cobyman7035:
do i need to use this CIFS manager to view my SMB on win8? im trying to stream my share folders on win8 LAN but can't connect
[Nexus 7 (2013) Original Android Development] mpmilestogo:
Hi. For my own limited test. Running rooted image available on xda. installed chrome beta and this kernel. Reboots daily after chrome use. Removed the beta and zero reboots. The tablet would reboot within 5 minutes of running the beta. The last kmsg would end with panic.

Observed this on two nexus 7 tablets.
[Nexus 7 (2013) Original Android Development] thahackr:
So can I simply flash the zip of elemental x 1.4 or do I have to do all of that that u guys are saying in other words does it work? I feel dumb:silly:
[Nexus 7 (2013) Original Android Development] mystifiyer:
I don't run benchmarks but I do play games. On Riptide 2 for example, on the initial start of game where there are multiple players and water streams in front, I tend to notice better frame rate or less stuttering in 533MHz then 487MHz.

I won't rule out placebo but I kick in the throttling for my cpu at least 80C and later
[Nexus 7 (2013) Original Android Development] Cryptecks:
Thanks a lot for at least doing some preliminary research on this. If you end up having the time, I think it would be good to see if the device reboots when using the stable build of Chrome under the same conditions you used for the first, because if the issue is a Beta-only one, then it is much more manageable for me and I'm sure others having the issues.

Sent from my Flo
[Nexus 7 (2013) Original Android Development] Keksdt:
Sorry to ask here but will you release this kernel for deb in the future or is this out of the question?
[Nexus 7 (2013) Original Android Development] flar2:
As far as I know, it works on deb already.
[Nexus 7 (2013) Original Android Development] Keksdt:
The worst which could happen is for me to reflash a different kernel?
[Nexus 7 (2013) Original Android Development] flar2:
Just do a android backup of boot

But I'm 99.9% sure that this will be fine on deb
[Nexus 7 (2013) Original Android Development] Windsor1959:
I've tried a few kernels and ROMs in the past week. I find that this kernel, combined with CleanROM 1.6, gives an amazing blend of performance and great battery life. YMMV, of course. Still, great work!

PS - I don't use Chrome and I don't know what CIFS Manager is, so I haven't had those issues. Smooth as silk.
[Nexus 7 (2013) Original Android Development] Keksdt:
[MENTION=4684315]flar2[/MENTION],

thank you very much, seems to work so far including LTE. So now is testing time :)
[Nexus 7 (2013) Original Android Development] mpmilestogo:
After a day of my use including numerous Starbucks, home Wi-Fi, lots of chrome browsing I have had no reboots. This leads me to believe the regular chrome browser is OK.

I click on links in taptu and flipboard and also have multiple tabs open and swap between. I'm satisfied.
[Nexus 7 (2013) Original Android Development] jlevy73:
+1 to that statement. I just follow Flar2 from device to device, I'm like a device stalker. He's made my One, now this device that much better.
[Nexus 7 (2013) Original Android Development] Philaphlous:
Mine seems to crash every time I've got fb messenger up... Used it all weekend without fb without 1 reboot, got on fb messenger last night, crashed within 5 minutes... I took a bug report but I dunno how to read it, what am I looking for? Used opera all weekend without any issues.
[Nexus 7 (2013) Original Android Development] flar2:
That, and the Chrome Beta thing, are really strange. I've worked on a lot of kernels, and I don't recall seeing apps cause hard reboots.

Just to verify, are these hard reboots, where it goes all the way back to the google screen, or soft reboots, where just the system crashes and it goes back to the boot animation?

I've still never had any reboots on this device, using stock ROM, and my whole family has been using the tablet quite a bit. Internet surfing, gaming and watching movies mostly.
[Nexus 7 (2013) Original Android Development] nikr123:
I think it's the same that happened to me when I used this kernel. I was just playing asphalt 8
[Nexus 7 (2013) Original Android Development] flar2:
I play asphalt 8 all the time, that won't make it crash. If it does, you're clocked too high or undervolting too much.
[Nexus 7 (2013) Original Android Development] nikr123:
What is your settings?
[Nexus 7 (2013) Original Android Development] flar2:
I run 1728 on all cores, elementalx optimization, undervolt to 850, gpu 487, ondemand gpu governor, fsync disabled, dt2w and s2w enabled, fastcharge enabled.

You should never have a reboot on my kernels. If you do the first step is to install with stock settings:

1512 on all cores, stock optimization, stock voltage, gpu 400, ondemand for both governors, fsync enabled, everything else disabled.
[Nexus 7 (2013) Original Android Development] shokwaav:
They're hard reboots.

EDIT: apparently it's getting a fix? http://www.androidpolice.com/2013/0...ce-reboots-but-a-fix-is-already-in-the-works/
[Nexus 7 (2013) Original Android Development] Cryptecks:
Just came to post the same link. I'm really glad this isn't a kernel or device issue (though I never really suspected it was) and I'm perfectly fine just waiting for the Beta to get an update. Easily reproducible bugs in beta software don't bother me a bit, I'm just glad it's being tracked now.
[Nexus 7 (2013) Original Android Development] nikr123:
Hey flar2 I still get reboots but it might be my custom ROM. Have you tried switching quickly between all the cars for some time then suddenly it reboots. Anyway thanks for all your great work!
[Nexus 7 (2013) Original Android Development] tni.andro:
It does look like it's a kernel issue. The GPU suspend times out and the kernel watchdog reboots the device. Userspace shouldn't be able to trigger that.
[Nexus 7 (2013) Original Android Development] celkin:
Just wanted to thank the dev on this kernel. Been running it for awhile now, but since the 1.4 update my battery has been amazing. Easily hitting 8 hours screen on time and going 2-3 days between charges.

Just a little update from a very happy user. :)

Zero reboots, zero lag, zero overheating issues. So few issues i would swear i was running stock but its fast... So f*+ & #'n fast!

Sent from my Nexus 7 32gb (flo) Running Carbon Rom/Elemental Kernel
[Nexus 7 (2013) Original Android Development] Cydras:
[MENTION=4684315]flar2[/MENTION]: what for a Rom you use?

Gesendet von meinem Nexus 7 mit Tapatalk 4
[Nexus 7 (2013) Original Android Development] owerner:
I just tried to flash the Kernel on my DEB (!!!) nexus.

Its working.

edit

After some time touch freezes. I can swipe through the menu, but dont "click". It started to happen after I flashed the kernel. Is this the famous MultiTouch bug on the new nexus devices everyone is talking about?
[Nexus 7 (2013) Original Android Development] mpmilestogo:
This is excellent news. On chrome beta for me the reboots were not immediately. Usually after 5 minutes or so the tablet would show the Google logo and reboot. Now without chrome beta I am at 64 hours on the tablet according to settings uptime.

Thanks for this great kernel and the link regarding issues with the beta.
[Nexus 7 (2013) Original Android Development] celkin:
Tapatalk 2 will no longer let me upload pictures. But its a momentus occasion.

My Nexus 7 has been running for 1 day 22 hours 14 min since last charge. But the really amazing thing is... 8 hours 32 min and 51 sec on the screen with an astonishing 9% battery remaining.

Always wanted to be able to post one of these threads!

Sent from my i337m rockin Kangabean
[Nexus 7 (2013) Original Android Development] flar2:
I always use stock for initial devlopment. Now that most of the features are working well I'll probably check out some other ROMs.
[Nexus 7 (2013) Original Android Development] nikr123:
Have anyone tried this with PA?
[Nexus 7 (2013) Original Android Development] En Kee:
I have, it's just perfect :good:
[Nexus 7 (2013) Original Android Development] nikr123:
I think I will install it when the new version comes out. What version of PA are you running? And which settings in ElementalX?
[Nexus 7 (2013) Original Android Development] En Kee:
ParanoidAndroid 3.99 + ElementalX 1.4

CPU 1728Mhz - GPU 487Mhz - CPU Interactive governor - DoubleTap2Wake
[Nexus 7 (2013) Original Android Development] nikr123:
I will switch when the new version comes out and that's hopefully soon. Thanks!
[Nexus 7 (2013) Original Android Development] oias.heeda:
I was having Asphalt crashes, tried a few different settings then I tried these. Asphalt working fine. I must say though, even though I had Asphalt crashes, my system worked fine totally OC. Thanks flar. :)
[Nexus 7 (2013) Original Android Development] nikr123:
What is your settings now then?
[Nexus 7 (2013) Original Android Development] oias.heeda:
1728 on all cores, elementalx optimization, undervolt to 850, gpu 487, ondemand gpu governor, fsync disabled, dt2w and s2w enabled, fastcharge enabled
[Nexus 7 (2013) Original Android Development] cuongdhytn:
does it works on lg model ? :confused:
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
Lol. Wut?

You mean lte?

Sent from my Nexus 4
[Nexus 7 (2013) Original Android Development] lovenovelistic:
not work??

:(
[Nexus 7 (2013) Original Android Development] flar2:
??

This works on everything. All roms and both deb (lte) and flo (wifi only).
[Nexus 7 (2013) Original Android Development] Philaphlous:
I can go days without a reboot, I load chrome, have it open in the background and it'll hard reboot in less than 5 minutes...lol
[Nexus 7 (2013) Original Android Development] cuongdhytn:
I use lg optimus lte3/ f7:(

sr,I'm not good at English
[Nexus 7 (2013) Original Android Development] flar2:
Never, ever flash a kernel meant for a different device. This is only for the new Asus Nexus 7 tablet.

When I say "works on everything" I mean every ROM and hardware variant of new Nexus 7.
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
You are in the wrong forum Sir.

Sent from my Nexus 4
[Nexus 7 (2013) Original Android Development] cuongdhytn:
I only want the same features as Knockon in G2 :)
[Nexus 7 (2013) Original Android Development] sgt. meow:
Someone said he had no issues running Chrome BETA on his GS3, right, but ran into reboots on this?

Can you check for the following, please and provide answers ASAP?

GS3:

What version of Android and what kernel do you run? - 1

Is SELinux enabled? - 2

N7 2013:

Is SELinux enabled? - 3

Can all reboots be attributed to the avc error? - 4

If 1, 3 and 4 are positive then I may have a theory regarding the reboots (which aren't really random). In either case Google did a crappy job at this (even considering it's a beta).

A PM is appreciated (please quote this post when you are answering) but a thread reply will do too. I don't have this device myself but I find development for this device very interesting (as hardware (certain bits of it) is so closely related to the OG N7). :)

Thanks in advance.

sgt. meow
[Nexus 7 (2013) Original Android Development] matrix.bharath:
Been using since i got the tab.. works perfectly with PA. without any issues.

EDIT - Im Getting a System UIDs Inconsistent issue with the latest PA release. no issues with stock kernel. any heads up guys ?

---------- Post added at 10:50 PM ---------- Previous post was at 10:15 PM ----------

Im Getting a System UIDs Inconsistent issue with the latest PA release. no issues with stock kernel. any heads up guys ?
[Nexus 7 (2013) Original Android Development] flar2:
Go to recovery and clear cache and dalvik cache. Then select fix permissions.
[Nexus 7 (2013) Original Android Development] penguin449:
I wonder whether the N7 has variants of CPU? for example, if i tried to set the CPU at say the highest Clock in Aroma, after Aroma is done, it will black screen but still be in recovery? Can then adb reboot, but upon boot, nothing is working (FC's) and then immediate boot into bootloop?

I wiped cache and dalvik cache before flashing, not troubleshooting here, wondering whether this could be answered? Rather than being told 'Well flash at a lower freq' because, well i'm not a noob xD

If their are variants, like Tegra 3 had 4 variants (old N7) would their be a way to check?
[Nexus 7 (2013) Original Android Development] flar2:
I am going to tell you to flash at a lower frequency :D

I wouldn't recommend anything over 1728. Some people just like overclocking and tweaking so I've made extreme frequencies available. I doubt that many can run at the 2GHz+ frequencies.

The cpus are all the same in this device, except they've been binned according to required voltage (PVS). The PVS level is accounted for in the kernel code.
[Nexus 7 (2013) Original Android Development] penguin449:
Obviously i was gonna flash a lower freq, i can hit the 1998, but anything higher is a no go for me, i flash OC and then bench, then go back to stock freqs, 1.5ghz is more then enough for normal people.Getting about 26k on antutu, however benchmarks don't mean anything too significant, however it's a great kernel, 5k more then the other kernels for the N7 2013. Great Work, Ive had it for 3hours and i'm already flashing away :3
[Nexus 7 (2013) Original Android Development] flar2:
I agree there is not much need to OC for daily use on this device, I don't notice much difference between stock and 1728 (which I run most of the time). On my HTC One (basically same chipset but stock freq is 1728), I can't even run stable at 1998, so I just run stock freqs.
[Nexus 7 (2013) Original Android Development] penguin449:
Ive only ever used a Snapdragon S1 chipset at 767mhz, and Tegra3 from my 4x HD and N7, both variant 3, but rarely get about 17-18k antutu with them, and lags on tose non optimized games so bad and they heats up fast! Have you had any heating problems with this chipset? And like tegra 3 does battery decrease when you charge and game at the same time? xD Ridiculous questions, but it seriously does happen!
[Nexus 7 (2013) Original Android Development] flar2:
This one heats up very quickly, but the battery life is amazing. You can game for hours on a single charge.
[Nexus 7 (2013) Original Android Development] Philaphlous:
Could we get a breakdown in the OP of the different clocks for the l2 cache overclocking and the temperature settings? I always like to know the exact numbers, I'm sure others do too! Thanks!
[Nexus 7 (2013) Original Android Development] :
I got the black screen twice, once cuz I forgot to clear dalvik and cache and the second after installing 15R. In both cases a hard reboot (holding power) got it going and everything loaded good. After I went back in recovery and flashed it again proper just incase.
[Nexus 7 (2013) Original Android Development] flar2:
I will update the op sometime soon.

****************************************

I worked on the OTG + charging thing tonight. I have it working but I need to clean up the code and make sure the driver can deal with various plugging/unplugging scenarios. I hope to release something later this week.
[Nexus 7 (2013) Original Android Development] cobyman7035:
I went back to stock uv and 1.5ghz.. feels smoother then 1.7ghz n uv ing

Via Google voice Δ |\|€×u$™ 7 FHD on Tapatalk²
[Nexus 7 (2013) Original Android Development] matrix.bharath:
Thanks FLAR, this fixed the UID issue, but still Settings keeps FC'ing time to time .. !!

Think there is some other bug?
[Nexus 7 (2013) Original Android Development] flar2:
I'm not sure, I haven't used PA. These are not kernel bugs though, I just knew fix permissions would solve the UID problem. You may have to wipe data and reinstall.
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
That's the issue with the rom, take a logcat and post it in the PA THREAD

Sent from my Nexus 4
[Nexus 7 (2013) Original Android Development] mpmilestogo:
Hi all. Anyone using this kernel with the latest ota update? Curious because new boot loader and not sure what under the hood changes happened.I flashed the zip that scrosler provided very recently. Thanks.
[Nexus 7 (2013) Original Android Development] flar2:
I haven't tried it but I'm 99.9% sure it will work fine.

EDIT: I just checked googlesource and the kernel only had one small commit added for the update. So it will work just fine.

I will update the kernel with that commit later this week once I polish up the new otg + charging feature.
[Nexus 7 (2013) Original Android Development] whoamanwtf:
I use this kernel with the new boot loader, no issues here.
[Nexus 7 (2013) Original Android Development] Ronde90:
Hi. I've been playing around with trickster mod and the kernel and wanted to ask if I can disable mp decision. Does the kernel kernel have an alternative? I'm just really curious as to what it does and the benefits of disabling it. Sorry if this has been asked a lot; I can't seem to find a solid explanation. Thanks for the help and the great kernel!!!
[Nexus 7 (2013) Original Android Development] flar2:
I recommend leaving mpdecision enabled. It turns cpu cores on and off as needed. There is no benefit to disabling it and I do not have an alternative because I find mpdecision works very well. It's quite efficient and gives very smooth performance.
[Nexus 7 (2013) Original Android Development] mpmilestogo:
Thanks! I installed on both of my wifi nexus 7 2013 tablets and all is well. Someone reported it blacked the screen out at the end but I did not see this. I have an older version of TWRP installed and it will always report that root is lost but its not. Thanks for verifying what changed under the hood in the kernel and boot loader as well. I saw some things which looked different for the new bootloader.

The kernel is working great. I love the battery life on this kernel!!
[Nexus 7 (2013) Original Android Development] flar2:
I've been getting great battery life too, even with s2w and dt2w enabled.

For best battery life, s2w and dt2w can be disabled. But I'd much rather have features than battery life, because even stock battery life is more than adequate on this tab.
[Nexus 7 (2013) Original Android Development] penguin449:
Even at >1.9ghz i can still game for like 4 hours solid and stil have time for taking mug shots of my teachers during class! Get nearly 28k Antutu, if you want more battery, and i don't know whether this would work or not, clock your first 2cores to 1.5 and then your 3rd and 4th to 1.9? I can't remember whether this kernel as multicore saving or not too? If it does put it at 2cores and it should be the first 2, then turn it off when you wanna game and when the 3rd and 4th kick in it can give ya a boost?

Please correct me if that theory is wrong, never tried or looked into it, just seems to make sense?
[Nexus 7 (2013) Original Android Development] jlevy73:
I believe it's cpu0 and cpu3 that are turned on first. So you would clock those higher for smoother performance clock cpu1 and cpu2 lower to get a balance between performance and battery life.

---------- Post added at 08:32 AM ---------- Previous post was at 08:30 AM ----------

I agree, can't live without dt2w. Volume 2 wake would be a nice feature too but I'm not sure if that's kernel related and Rom. From what I understand that's a rom based tweak