yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] thekendog:
So I got all excited about it, but double tap to wake isn't working now. Neither is swipe to wake. Worked the first few times, now nothing,
[Nexus 7 (2013) Original Android Development] flar2:
dt2w doesn't work very well at the moment, I can make it too easy or too hard, I haven't found just right yet. I have it set "too hard" in the betas so far, maybe next one I'll make it "too easy" and see how people like it.

s2w works well, I use it all the time and it always works. For the moment, it only works on the bottom edge in portrait mode. If you flip it upside down, the s2w spot will be at the top of the screen. It doesn't follow the screen orientation.
[Nexus 7 (2013) Original Android Development] w0ng3r:
hotness
[Nexus 7 (2013) Original Android Development] ktkr:
Just had a random reboot with 1.4, here's the kmsg for your reference: https://app.box.com/s/60xw4r4gaztygm42pjgz
[Nexus 7 (2013) Original Android Development] dimebagdan65:
I can test USB-OTG/Host mode as I have a Y cable. Just let me know, otherwise looks like an awesome kernel ya got here :)
[Nexus 7 (2013) Original Android Development] -viperboy-:
Hey flar, great job with this kernel! I've been using it for a while and its great!

Just a few things... Using chrome or next browser, 1.4 never starts to download. I've downloaded every kernel from my tablet before and not had a problem. Just a heads up, I'll try tomorrow.

Also, if you'd like, I'll start on a kernel app for your kernel. It would be a fun project for me to help improve my java skills. I won't charge for it, of course. But I can have your users test it and see how it goes.

Let me know what you think. I know you'd like to make some money with the kernel though, so it's up to you. Just thought your users might want something for the time being :)
[Nexus 7 (2013) Original Android Development] Philaphlous:
Says the server is offline... Will try later tpday
[Nexus 7 (2013) Original Android Development] airmaxx23:
Chrome took a long time to start downloading from goo.im for me yesterday on my tablet, maybe a 2 or 3 minute wait.
[Nexus 7 (2013) Original Android Development] tni.andro:
It turns out, the USB charge controller consumes quite a bit of fixed power (when USB power is connected). Those measurements were via the power draw from the USB port.

Reconciling them with some real battery drain tests, there 7mW power drain with deep sleep (Wifi/GPS/Bluetooth, ... disabled). doubletap2wake increases that by 55mW.

(I cross checked against an i9000, where I can actually directly power the device from the battery contacts and the deep sleep power consumption is about the same.)
[Nexus 7 (2013) Original Android Development] cobyman7035:
hows.1.4eX? im on 1,2, do i just do a dirty flash as if over it? thanks
[Nexus 7 (2013) Original Android Development] bobloadmire:
Can anyone explain what the trade offs are for disabling fsync? It just says slight risk of data loss, just wondering what the entails in more detail and what kind of performance gains we should see.
[Nexus 7 (2013) Original Android Development] tiny4579:
When you disable fsync data doesnt get written to disk immediately. This is where the risk of corruption comes into play. It still will write to disk later.

The impacts are improved write speeds as data doesnt get written to storage immediately. This speeds up synthetic benchmarks significantly but in real world experience there may be no noticeable improvement.
[Nexus 7 (2013) Original Android Development] flar2:
Just flash it.

NOTE:

Unless you need CIFS Manager or something else that needs to mount directories that can be seen across apps. In that case you need to reflash the boot.img that came with your rom and then install ElementalX.

Thanks!

You can do an app if you want, I'm sure people would use it for other kernels and devices too, so it might be worth your while. Many users here would be happy to test it. I do want to make my own app at some point so I can get a little bit of revenue for all this work. It'll be a while before I have an app though. So far I've made a Hello World app and that's about it.

I don't know why Chrome won't download from goo.im, it's strange. It's been a problem all along.

Let's see if we can get to the bottom of this, I hate seeing people have random reboots. It seems to be a small subset having the reboots, they must have something in common.

If you have a random reboot:

1. make sure you have a nice clean working system, and reinstall latest version of the kernel with no undervolting or overclocking.

2. If you still have reboot, send me a pm with:

/procl/last_kmsg

the kernel settings you chose (eg: s2w on, fastcharge off, etc)

what ROM you are using

description of the reboot incident (ie: what you were doing when it happened)

I will have a look at this information and hopefully I can figure it out. I want you to send a pm so I have a list of users with reboot problems for testing. I've never had a random reboot myself, so I'll need your assistance to solve the problem.
[Nexus 7 (2013) Original Android Development] Philaphlous:
When I flash it says supersu has lost root permissions. I swipe to fix. Is that a big deal or no?
[Nexus 7 (2013) Original Android Development] NekroWolfen:
Weird, that's happening to me too with Bulletproof, you flashed the latest SuperSU update or updated TWRP?
[Nexus 7 (2013) Original Android Development] flar2:
I can't figure out why it says that. I recommend clicking the "Do not fix" button.

You will not actually lose root.
[Nexus 7 (2013) Original Android Development] **Menos**:
Hi flar2, I’ve tried the kernel and it’s great! I’m also trying to enable usb 3G modem, since you have build environment, would you be so kind to build following 5 loadable kernel modules:

option.ko

ppp_async.ko

usbserial.ko

cdc-acm.ko

usb_wwan.ko

these module is required to enable 3G modem, if you can help it would be great!

Thanks a lot.
[Nexus 7 (2013) Original Android Development] Philaphlous:
I read that supersu is saying that I need to upgrade to the pro version...lameeeeee. Do we really need supersu and busybox for just having the stock ROM and new kernel? I wouldnt mind not having root access through apps...
[Nexus 7 (2013) Original Android Development] NekroWolfen:
At least on my end that's not the case, I have flashed SuperSU and don't have the pro version. Of course the app recommends it but it's not mandatory.

[MENTION=4684315]flar2[/MENTION] Thanks for your help, I did more tests turning off the touch2wake feature but the occasional freezing occured. However I did the "take that multi touch" solution and somehow it hasn't freeze in all day, I didn't know that could help with that but I guess it did. :/
[Nexus 7 (2013) Original Android Development] flar2:
Anyone with reboots, are you using Chrome beta?

What modem is it? Some of that is already built in, to get the device working may require specific drivers that aren't part of the main kernel source.
[Nexus 7 (2013) Original Android Development] Cryptecks:
I haven't had one since flashing 1.4 earlier tonight but during the day I had one on 1.3 while the screen was off, there is a very strong possibility that Chrome Beta was running though as I use it as my main browser. I didn't manage to get a kmsg earlier but I will if anything happens on 1.4.

Sent from my Flo
[Nexus 7 (2013) Original Android Development] JCon0320:
Oh I see. I was just curious because the installer goes all the way to 2.2ghz. I was under the impression that I was way below the highest option available. As you have said, I'm just very lucky I guess. I have not have one single reboot, crash, or anything that relates to instability using my current settings. Been rock solid for 2 days w/o turning off the tablet.
[Nexus 7 (2013) Original Android Development] shreddintyres:
I was just browsing the forum but i have been running faux's kernel, a number of users over there are also experiencing random reboots, k was as well so far the common factor ive seen in the faux kernel thread is chrome beta, i was experiencing a random reboot per day at minimum with chrome beta installed since i Uninstalled chrome beta (going on ~4 days) ihave not had any issues with random reboots, mainline chrome installed. I hope this info helps.

On another note are kernel _ debug and kallsyms_all enabled in elemental (for Voodoo n7 calibration)?

-cheers

FLO'd from my fingertips
[Nexus 7 (2013) Original Android Development] RedDevils88:
I have a problem here which is the screen gets responsive while turning the screen on and I require a reset using the long press power button. Anyone else has this problem? Is this kernel related?
[Nexus 7 (2013) Original Android Development] shokwaav:
Actually now you mention it, I am. Seems to happen more often when I sleep while Chrome beta is still open.
[Nexus 7 (2013) Original Android Development] MadMatt89:
Is it really that much more power consumption? Same with only sweep2lock/unlock enabled? Makes me think about turning it off...

Now that everybody mentions chrome, I never a a reboot on your kernel afaik and I did not install chrome, but when I was on stock a few hours after I bought my tablet I recognized a reboot while using chrome or downloading something with it. I guess we could have a possible cadidate here.
[Nexus 7 (2013) Original Android Development] tni.andro:
Yes. But to put things into perspective, the 62mW power drain with sweep2wake is still 10 days until the battery is drained. No big deal, if you charge every couple of days.

Yes.
[Nexus 7 (2013) Original Android Development] MadMatt89:
One more thing:

My tablet does not awake when it is or was in deep sleep when I open my magnetic sleeve. Is there a way to fix this?
[Nexus 7 (2013) Original Android Development] cobyman7035:
yup mine won't either, i think its kernel related, the magnet open only works if the tablet is not on standby for long periods of time

i think 1 hour is ok but longer times it won't auto on

im o/c to 1700, i might want to go higher!

anyone on 1.8ghz and stable with 850UVing? if so, hows the battery
[Nexus 7 (2013) Original Android Development] flar2:
The magnet thing is a known issue, not related to custom kernel.

I think if you leave your wifi on all the time it will work, or something. I can't remember.

I'll test the voodoo calibration later and report.
[Nexus 7 (2013) Original Android Development] flar2:
I have not experienced this, but a few other have. Please provide details (like what ROM, settings, and dmesg output from when it happens...can get it through adb shell)
[Nexus 7 (2013) Original Android Development] sensboston:
Your wife is right; donations (I do have a donateware too) sometimes not working properly. $1.99 sounds very reasonable to me (will be happy to buy that app!); also, you can make your app compatible with all your kernels.

I don't know about other kernels statuses but ElementalX is very stable. UI configurator will be much better addon than some rare used features ;)
[Nexus 7 (2013) Original Android Development] killflaker:
I'm stable on 1,94Ghz, (Max tested stable is 2,05Ghz) whit 800UVing. No problem to boot in 2.21Ghz but not tested in benchmark or stresstest.

Pass one day easy whit 4 hours on screen. (2h gaming Galaxy on Fire 2 HD)
[Nexus 7 (2013) Original Android Development] **Menos**:
Thanks for your time, flar2! I'm use PPP widget with Huawei E1550 modem. With my second tablet(pipo m9 rk3188, stock firmware 4.2.2) this combination works fine, without any additional drivers or modules.
[Nexus 7 (2013) Original Android Development] flar2:
Just tested, supercurio's display calibration works fine with ElementalX

https://plus.google.com/communities/103123288128442067861
[Nexus 7 (2013) Original Android Development] Imppy:
What are your recommendation for colours if you have tried it already
[Nexus 7 (2013) Original Android Development] flar2:
It's alpha right now, he just gives you one preset to test. I just learned of it today, so haven't followed the development. There are several empty tabs in the app, so it looks like he will be adding lots more.

The preset looks good though, it's a bit warmer than stock.
[Nexus 7 (2013) Original Android Development] aamitabh28:
Rock solid kernel with super duper battery life..what more could one want!
[Nexus 7 (2013) Original Android Development] airmaxx23:
I agree, the preset looks pretty good.
[Nexus 7 (2013) Original Android Development] bsw11:
Can you add a option to allow swiping in either direction to turn off or on the screen. A simple toggle would be much easier to remember than the direction which changes based on orientation.
[Nexus 7 (2013) Original Android Development] NoobieExtraordinare:
Yea Chrome beta and random reboots with 1.3

Farting out replies through my Dyson Air Multiplier.
[Nexus 7 (2013) Original Android Development] wintermute000:
To fix CIFs how do we flash boot.img if we're running stock?

Would restoring kernel off TWRP then reflashing this do the same thing?
[Nexus 7 (2013) Original Android Development] flar2:
No, you need to get a fresh boot.img that hasn't had elementalx or another kernel flashed on it before. For stock, you could use the boot.img from Cleanrom (it's stock kernel). For anything but stock, you just need to do a dirty flash.

Then reboot to bootloader and do:

fastboot flash boot boot.img
[Nexus 7 (2013) Original Android Development] wintermute000:
My TWRP is a pure stock JSS1Q via OTA?
[Nexus 7 (2013) Original Android Development] flar2:
Then it will definitely work. I wasn't sure if you had backed up the original
[Nexus 7 (2013) Original Android Development] oias.heeda:
Hey flar2. Love this kernel. However I am having an issue. I have tried both non OC and OC versions of this kernel. They both cause my game Ashphalt 8 to FC. Doesn't happen on built in kernel. Just yours. Any idea? You like a log?
[Nexus 7 (2013) Original Android Development] Philaphlous:
I'm gonna use opera browser this weekend and see if that resolves my random reboot issues. Oddly enough it will typically reboot when I'm on Facebook messages but I'm not sure if its BC of chrome in the background...
[Nexus 7 (2013) Original Android Development] flar2:
I use asphalt 8 for testing. The problem is with your setup. Try stock freqs and voltage, or wipe cache, or full wipe and reinstall

Chrome is my prime suspect right now, I'd get rid of it.

My favourite browser is Boat Browser. Been using it since I started using Android
[Nexus 7 (2013) Original Android Development] Philaphlous:
The boat b seems slow for scrolling, pages will be loading and I will try to scroll and it'll be really laggy... Opera is working pretty good! I'm really hoping for no reboot. I reflashed and whiped the davalak and said no to the supersu prompt...
[Nexus 7 (2013) Original Android Development] Cryptecks:
Had two random reboots fairly close to each other today. Here's the last_kmsg i pulled, I hope it's useful!

Edit: Forget to mention that I was definitely running Chrome Beta at the time. I'd love to use another browser but I rely on too many of the cross-platform features between my desktop, work desktop, laptop, this tablet and my phone.
[Nexus 7 (2013) Original Android Development] flar2:
Chrome. I'm certain that the kernel is rock solid.
[Nexus 7 (2013) Original Android Development] PoedelPCS:
just an idea for browsing..

I am using Naked Browser ..that is pretty fast.. worth a try. Nice gesture features. Unfortunately not that cross-syncing-capable as chr0me.
[Nexus 7 (2013) Original Android Development] darkobas:
Chrome non beta exists also
[Nexus 7 (2013) Original Android Development] Cryptecks:
I know that... He's saying that it's Chrome in general, not just the beta, I was just specifying which one was running. Oh well, I'll see if the reboots lessen or go away, but if not there are plenty of other options to try as well. I'm a full time web developer and working on a startup too, not having Chrome as an option for testing (not to mention it being my preference) doesn't work for me, which is why I uploaded a log to see if anything could be figured out from it.

Sent from my Flo
[Nexus 7 (2013) Original Android Development] mrdingding:
I flashed the boot.img from cleanrom while on the vanir ROM, and that gave me a bunch of errors. I ended up doing a full wipe, and installed clean ROm.

Without flashing your kernel, cifs manager doesn't work as expected.

After flashing 1.3, it mounts my nas for a second,until I try to see the files in browser. No files can be seen and the mount is broken. Afterwards it can't be mounted again. The error message is mount: device or resource busy.

This seems like as fresh a state I can get my tablet to be and i still cannot get CIFS to work. Any suggestions?

All the NAS content has been easily accessible by smb, but i havent had any luck with actually mounting it.

Other than that, your kernel has been working very nicely. Thanks!!!
[Nexus 7 (2013) Original Android Development] irekz:
some issues

First of all thank you for your hard work guys - greatly appreciated!

I use stock ROM + ElementalX 1.4

Here are some of my observations:

1) OTG works great and that was for me the main reason to flash - THANKS!

2) CIFS is also important for me but I could not get it working.

Cifs Manager mouts drive (no errors) but it appears empty for other applications.

I mounted in /mnt/cifs/video (so not on sdcard that apparently can be source of problems).

Has anyone managed to get CIFS working on this kernel?

If yes - what was your mount point, do you use Cifs Manager or something else?

Thanks in advance!

Irek
[Nexus 7 (2013) Original Android Development] Alex0901:
Cifs is working fine here.

Cifs manager Mount my drives from my ubuntu Server and my desktop Windows PC without issues.

Gesendet von meinem Nexus 7 mit Tapatalk 4
[Nexus 7 (2013) Original Android Development] housepabldroid:
is this kernel support cyanogen 10.2?
[Nexus 7 (2013) Original Android Development] irekz:
Good to know.

are you using /mnt/cifs/ as mount location?

I wonder if this is related to ROM? I'm using stock and not sure if this combination should work or not...?

Cheers,

Irek
[Nexus 7 (2013) Original Android Development] Alex0901:
You can mount where are you want.

2,3 Mount are offline because the Windows PC are offline ;)

Gesendet von meinem Nexus 7 mit Tapatalk 4
[Nexus 7 (2013) Original Android Development] teh roxxorz:
Indeed so.
[Nexus 7 (2013) Original Android Development] flar2:
Cifs support depends on a line being placed in just the right spot in the ramdisk.

I'm trying to use the existing ramdisk from your Rom and add this line, but maybe it's not getting added properly for everyone

I'll post instructions later that show how to add it yourself
[Nexus 7 (2013) Original Android Development] sgt. meow:
The ramdisk (IIRC) will get re written to what was packed with the boot.img, at every boot. So changing it after boot is not usually the right way to go about this. Unless you cook up your ramdisk yourself and pack it with the zImage.
[Nexus 7 (2013) Original Android Development] irekz:
Thank you for your time guys.

Not sure if this helps at all but I did some more digging:

- when using terminal i can issue su and busybox mount -t cifs ... commands

this will mount a drive correctly and I can browse it using that terminal session (for example listing using ls shows content)

but if I switch to any other app - folder appears empty

- not sure if i have some issue with permissions. there is one thing is strange:

in terminal, even in su mode: i can't for exmple to create a directory outside a sdcard. trying to create one gives me an error message saying it's mounted in read only mode. not sure if this is related to cifs issues or to be expected on stock rom

Kind regards,

Irek
[Nexus 7 (2013) Original Android Development] tiny4579:
I thought flar2 said cm diverged from stock and their ROM changes broken cm compatibility.
[Nexus 7 (2013) Original Android Development] flar2:
I'll help you guys out with cifs tonight. I'll be out all day and can't type the instructions on my phone very easily

I guess that it works

The only thing I've heard lately is that slimport doesn't work on cm
[Nexus 7 (2013) Original Android Development] Cruiserdude:
CM switched from an AOSP base to a CAF base, for some reason that I have yet to understand. No idea why they'd do this on Nexus devices that are already supported and fully stable in mainline AOSP, but that's not my department. The result of this are there are 2 different bases out there that people build roms and kernels off of. Run a CM rom with an AOSP kernel, or vice-versa, and you may have problems ranging from minor issues to a failure to boot. Or they may work fine together, it's easy enough to find out.

Still, it's smart to identify whether each rom or kernel you use is CM or AOSP, since they're not really the same thing anymore. If you have issues, use like with like. I would rather stay on a stable AOSP base since that's the whole reason I got a Nexus. So I run stock with Xposed and stick with AOSP kernels. Again, mixing and matching may work, but there's no guarantee.

As an aside, there's a similar situation with devices like the S4, or certain Sony models, that have proper source and device files to build basically pure AOSP. A few cherry-picks from CAF I can understand, but using the entire base even when there's a solid, device-specific alternative doesn't make sense to me. I understand with something like the S3, where the official kernel is Linux 3.0, it made sense to move to CAF to get up to 3.4. But I just don't see the advantage on more modern devices. And I honestly don't mean to disparage the CyanogenMod team or what they hope to accomplish, but I do typically get better results when running true AOSP where it's available, so their choice confuses me.

Sorry to clog up your thread with that, flar, I'll take it down or shorten it if you'd prefer. Just something that's been bugging me for awhile, and this seemed like the time to say it.

:thumbup: