yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] dimebagdan65:
The circle is now complete... The Ozzman cometh! Glad to see you here dude! I'm no coder but I'm a hell of a tester! :)
[Nexus 7 (2013) Original Android Development] -Jesco-:
I'll see if I can pull it off :s
[Nexus 7 (2013) Original Android Development] wildestpixel:
I'll have a look Monday or Tuesday when I get device
[Nexus 7 (2013) Original Android Development] SupWiz17:
When will we see some osmosis builds just like in the old nexus 7 thread?
[Nexus 7 (2013) Original Android Development] shreddintyres:
Probably when he gets an n7? Thats the reason he was asking us for help with pulling down the partitions knowing him he would have done that already had he had a N7 2013

FLO'd from my fingertips
[Nexus 7 (2013) Original Android Development] EfrainTrejo:
Sorry nevermind
[Nexus 7 (2013) Original Android Development] thecapitalr:
Hey guys... sorry inadvance for the super noob question. This is the first kernel I have installed on my n7 2013 (running PA). Previously I have used kernels on my SGS3. I am a user and not a dev btw (thanks to all who build these awesome kernels/roms!)

Are you guys playing around with the settings for this kernel using trickster mod or the like? Or are you guys just running the default settings (eg just flashing the kernel and not touching anything). I am looking for whatever settings will give me better battery life (would rather have better battery than a overclock) so any setting recommendations would be fantastic (in threads for SGS3 kernels people usually list their settings... havnt seen that in this thread).
[Nexus 7 (2013) Original Android Development] lndeed:
The default settings are really quite good, especially for battery. If you'd like to tweak anything however, franco.kernel updater from the Play Store is what you want.
[Nexus 7 (2013) Original Android Development] shreddintyres:
has anyone noticed some intermittent screen tearing on R3 using apex launcher? i didnt notice any from r2 or r1? it only seems to affect the wallpaper tho which is beyond odd to me.
[Nexus 7 (2013) Original Android Development] mountainloafers:
Try re-flashing the kernel. Similar thing happened to me when I flashed AOKP. Re-flashed kernel and all was fine.
[Nexus 7 (2013) Original Android Development] shreddintyres:
i've tried exactly that, which is the odd thing. if im on my homescreen it will affect just the background but icons, widgets etc are ok, so far since the last occurrence i havent had any repeats ill try and pull a log next time it happens.
[Nexus 7 (2013) Original Android Development] mountainloafers:
The tearing was happening to me in all screens. Flashed official aokp nightly yesterday. I flashed r3 right after ROM, gapps, SU. Thought I would have to reflash all but r3 and let the ROM sit for a while before doing so again. Luckily that was not the case for me. Hopefully you will be in the clear.
[Nexus 7 (2013) Original Android Development] kptnk:
I'll just leave this here, with r3, on demand/row, max 1458....:D
[Nexus 7 (2013) Original Android Development] DatDude123:
Impressive.

D
[Nexus 7 (2013) Original Android Development] sevenslugs:
What ROM are u using?
[Nexus 7 (2013) Original Android Development] SupWiz17:
Great battery life there. I should have took screenshots but this weekend I was reading a lot of PDFs on my tablet and got 7 hours of screen time with over 2 days of standby and performance is great.
[Nexus 7 (2013) Original Android Development] sevenslugs:
Get Franco kernal updater from the play store its well worth it, plus it supports Franco in his development ..

---------- Post added at 02:49 PM ---------- Previous post was at 02:49 PM ----------

Has anyone undervolted with this kernal ?
[Nexus 7 (2013) Original Android Development] kecinzer:
Hi [MENTION=3292224]franciscofranco[/MENTION]

Do you have any plans to make unifying krnel for mako/flo?
[Nexus 7 (2013) Original Android Development] dmeadows013:
Not possible. Mako is a phone and flo is a tablet. Also, they both have different hardware.

Sent from my super awesome Nexus 7
[Nexus 7 (2013) Original Android Development] kecinzer:
Eh?

Did you hear about unifying mako/flo kernel from CM? https://github.com/CyanogenMod/android_kernel_google_msm
[Nexus 7 (2013) Original Android Development] kptnk:
Dude, that's exactly what i did : mostly reading epud and browsing + undoubtly 1 ep of Breaking Bad :)

Indeed Flo has a stunning battery life, especially for reading. Watchind HD movies sucks a mot of juice in comparison....

---------- Post added at 07:58 PM ---------- Previous post was at 07:56 PM ----------

I was on Dj Lamontagne's Rom , CM + SM Toolchain :good:
[Nexus 7 (2013) Original Android Development] dmeadows013:
It uses the same basis as Linux 3.4, but has to be built with 2 separate configs for each set of hardware. You can't build a zip file that is flashable on both, unfortunately

Sent from my super awesome Nexus 7
[Nexus 7 (2013) Original Android Development] kecinzer:
Well, I know that there is no flashable unifying kernel, I mean just source. There can be only one source for mako and flo.
[Nexus 7 (2013) Original Android Development] dmeadows013:
Oh OK yeah there's unified source. Not sure what Franco's plans are.

Sent from my super awesome Nexus 7
[Nexus 7 (2013) Original Android Development] tiny4579:
I think he already stated he's building straight from aosp.
[Nexus 7 (2013) Original Android Development] Cruiserdude:
Yup, which makes a unified source unlikely. CM can do this easily because they're a CAF clone, which means the same APQ8064 kernel should work with the right asserts and libs. AOSP is built specifically for each device, not SoC. Frank has indeed made it clear that he plans to stick to true AOSP source as his base, which is the only way it should be on a Nexus device IMHO, unless you're doing something crazy like Ubuntu or whatever. Google themselves uses largely identical source for both devices, I don't see how someone sticking with their source could do any different.

We shall see though.
[Nexus 7 (2013) Original Android Development] MikeRL100:
Speaking of CM, guess what? Latest nightly of CM plus Franco kernel nightly r3 equals graphical corruption, at least on the Nexus 7 2013. More fun! Update: Also happens on Nexus 4.
[Nexus 7 (2013) Original Android Development] LoVeRice:
ye i did flash everything again from scratch & now the app franco update keeps FC'ng
[Nexus 7 (2013) Original Android Development] airmaxx23:
I wonder if it has anything to do with the whole CAF thing.
[Nexus 7 (2013) Original Android Development] kecinzer:
Yes, this CAF thing drive me crazy! Noone could explain me what is better on CAF yet.
[Nexus 7 (2013) Original Android Development] airmaxx23:
I know Faux supports CAF with his kernel.
[Nexus 7 (2013) Original Android Development] MontAlbert:
But he doesn't like it... I have been hunting around trying to find a decent combination as it seems me that cm are leading everyone down their caf cm Inc path. I read this in faux thread:

Geek Talk Below:

CAF == Qualcomm's open source branch.

CAF's kernel sources are 100% open as required by GPL. Their libraries, however, are under Apache which means you can use them as you see fit, but not all are open (some are strictly as proprietary lib files).

For ALL NON-Nexus Qualcomm devices, CAF's kernel + libraries will be the closest to AOSP experience (Even Google's AOSP still depends heavily on these proprietary libraries from various vendors including Qualcom/CAF).

Historically, Qualcomm often creates a separate less optimized version of their proprietary libraries for Google to use on Nexus devices (I guess because Google didn't pay them to be their premium partners like Samsung, HTC and LG), but this didn't stop Google from turning these basic libraries and create amazing experiences on their Nexus devices (HTC's Nexus One, Google's Nexus 4, Google's Nexus 7 2013 and the upcoming Nexus 5).

So now you know there are two distinct branches of libraries, AOSP and CAF's own version. Although both were created by CAF, but there exist some differences between the two (These differences are what creates bugs when you mix match the libraries and kernel source).

For reasons unknown, CM has decided to ditch the less optimized libraries and opted for CAF's own libraries for Nexus 7 2013... This created a massive headaches for many novice users and developers. If you load the AOSP kernel on CM ROM, you now have a mismatching kernel / library combination which led to video glitches and broken Slimport on Nexus 7 2013.

It looks like for Nexus 4, they are slowly doing the same thing by replacing the AOSP libraries with CAF versions... over time, the AOSP kernel will no longer be 100% compatible with CAF based ROM... This will eventually lead to fragmentation of Nexus kernels (just like Nexus 7 2013 ￼ )

I am HIGHLY AGAINST this move towards CAF for pure Nexus devices. Nexus devices already work quite well with what's given, and it enjoyed wide compatibility with ALL AOSP derived ROMs. By moving towards using CAF libraries on Nexus devices creates unnecessary FRAGMENTATION and incompatibilities within a Nexus device family!

Also I am not sure about the legality of using CAF libraries... Basically if you build a ROM based from it, you are redistributing the Qualcomm proprietary blobs and Qualcomm has EXTREMELY strict redistribution clause with their binary blobs (basically they need to grant you explicit permissions) where as AOSP it is less stringent than Qualcomm. Whenever you deal with proprietary libraries in general, you are in the gray area of legality and you have to tread very carefully. (This legal issue was what kept Nexus 7 2013 from releasing their factory images for a while between Qualcomm and Google. This is also what eventually led to JBQ leaving Google).
[Nexus 7 (2013) Original Android Development] willl03:
Wow thanks, couldn't explain better what I was googling for
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
Lol, I've been seeing your post in a couple other threads as well. But I'm not going to flame or advise against it, i can only thank you for spreading the word as I'm completely against what cm is right now.

Sent from my Nexus 4
[Nexus 7 (2013) Original Android Development] tiny4579:
This is a Franco kernel thread not cm/caf vs aosp debate. I did want to say quickly that since I don't know the whole story about why cm is doing what they are doing, I don't want to cast judgements on their decisions.
[Nexus 7 (2013) Original Android Development] greogory:
omfg fml bff!!! Bittery werk to good time long now. Cant be whine more. You must broken wakelox put or no pay utility bill i?
[Nexus 7 (2013) Original Android Development] Cruiserdude:
This is all correct, except for the part about CAF being Qualcomm's proprietary, optimized libraries. As mentioned, CAF is their open source playground, maintained and contributed to mostly by Qualcomm, but any developer with an account there can push commits, and changes are made before they are tested and stable. This means the CAF source is constantly changing, which is why the occasional CM nightly will break something, or introduce some new incompatibility requiring everyone to rebuild their CM-based work to make it work. Yes, this is the cutting edge, and many things are indeed an improvement. But this is also where things are being tested, think of it as an alpha build.

Anyone at all familiar with software will know that the bleeding edge is not where stability is found. What lead CM to believe otherwise is beyond me. Granted, many of these commits will eventually go into the source they share with partners including Google, and these same partners may pull other things selectively from CAF. The more heavily optimized proprietary binaries, if that's even really true, are developed internally and shared with select partners. The very definition of proprietary means you don't share source with everyone via a repo forum. So they're not the same thing at all.

Which makes CM's decision all the more perplexing, as they're moving away from a solid, stable base specifically made for our device, to one that's basically an alpha for our general SoC. So I support Franco, and any other dev who wants to keep their Nexus work based on AOSP. Isn't that the entire point of the device??

/
[Nexus 7 (2013) Original Android Development] tni.andro:
Except for all the reported crash/reboot issues.

GPU suspend is broken, as acknowledged here:

https://code.google.com/p/chromium/issues/detail?id=286378

The wifi driver is quite buggy, with channels >11 not working right, the driver crashing and having lots of disconnects (nothing new to see actually, the same was/is already the case for the Nex4). The whole regulatory domain handling is quite broken (and completely redone in the current CAF version).

Wifi driver crash:

[ 388.353149] Unable to handle kernel NULL pointer dereference at virtual address 0000000c

[ 388.353729] PC is at wlan_hdd_crda_reg_notifier+0xff4/0x1c24

[ 388.353790] LR is at vos_lock_release+0x11c/0x144

[ 388.394042] Kernel panic - not syncing: Fatal exception

addr2line:

drivers/staging/prima/CORE/VOSS/src/vos_nvitem.c:2363

\\

I'm not saying using random nightly code from CAF is the right way to go, but the Google stuff is very far from perfect and Google has a very long history of sitting on bugs and not fixing things.
[Nexus 7 (2013) Original Android Development] mrbradeli:
Did PA switch to CAF as well? Would that explain the reboots, graphical corruption, and WiFi issues I've been having with this kernel + franco r3? Would moving back to an AOSP based ROM fix all of this?
[Nexus 7 (2013) Original Android Development] cowabunga:
Dunno about PA and CAF. But if you are running franco r3 and getting display issues, then it's very likely the ROM you are running is on CAF but the kernel is not. You'll have to switch out the kernel or the ROM to a matching pair.
[Nexus 7 (2013) Original Android Development] darkobas:
Pa IS not caf and it runs without those isues on Franco kernel for most users
[Nexus 7 (2013) Original Android Development] tiny4579:
Yes. Paranoid android switched to aosp as a base a while back ( I think with 4.2).
[Nexus 7 (2013) Original Android Development] TheMrcool212:
Not to be rude, but just telling the truth:

Paranoid Android IS using CAF sources (especially for flo) . They did it with this commit:

https://github.com/ParanoidAndroid/android_vendor_pa/commit/18a4860a0407ec957df8221e8e59c7928db6bbcc

Till now:

https://github.com/ParanoidAndroid/android_vendor_pa/blob/jb43/manifests/flo.adds

They're tracking all the Qualcomm CAF repositories from CM, and including the kernel. So using CAF kernel on CAF ROMs would be more stable rather than on CAF ROM and non-CAF kernel or vice versa as stated in previous posts. :)
[Nexus 7 (2013) Original Android Development] tiny4579:
That is kind of disappointing. Do you know what major ROM still uses the AOSP kernel tree? It seems we have to be stock or a slightly modded ROM these days to use the AOSP kernels.

With a CM/CAF based kernel of my own, I'm having a lot of issues with certain tweaks and a strange issue with WiFi crashing on idle.

It seems the smart thing is to base your kernel on AOSP sources but that limits the amount of ROM options.
[Nexus 7 (2013) Original Android Development] tni.andro:
Slim Bean - if you consider them major.
[Nexus 7 (2013) Original Android Development] creeve4:
I'm running AOKP with franco kernel and have not had a single issue. Although I believe they are the CM kernel as well.
[Nexus 7 (2013) Original Android Development] ktkr:
If you are runng the 9/28 nightly it's fine, but any build from now may have those problems.
[Nexus 7 (2013) Original Android Development] tiny4579:
I was reading the faux thread and someone pointed out that Carbon reverted from the CAF userspace drivers. So the AOSP based kernels should start working with Carbon ROM now.
[Nexus 7 (2013) Original Android Development] creeve4:
What has been merged that will cause issues?
[Nexus 7 (2013) Original Android Development] mrbradeli:
Still having a few issues with stock JSS15R and franco r3. I'm willing to pass off the graphical stuff as a problem with one of the apps I'm using (haven't noticed it in anything else), but I'm still dealing with random FCs on stuff like the Launcher, and scrolling in general has been terrible in both Chrome and Firefox. Is this a problem with any kernel and rom combo? Its like I'm still using my original Galaxy S at times. Compared to my new Moto X this really does feel like my old Galaxy S.
[Nexus 7 (2013) Original Android Development] Remoteconcern:
FCs are never to do with the kernel. Scrolling is fine for me here, but that's relatively subjective.
[Nexus 7 (2013) Original Android Development] mrbradeli:
Interesting. I wonder what the problem could be. Is 4.3 in general just buggy? I just had a random reboot, and I couldn't even find a reason for it in last_kmsg. Really not liking the overall experience. Could it be the device itself? I have a July 2013 one.
[Nexus 7 (2013) Original Android Development] catlog:
I am using this kernel with AOKP and while it works fine, if I wipe cache and dalvik cache, it freezes a few second after it gets to the Android is upgrading screen some time when it is optimizing apps. I'm not sure if this has been posted before but I thought I would share as it doesn't seem normal, unless I am missing something.
[Nexus 7 (2013) Original Android Development] cyanoviper:
Is the battery life extender included? Am I just too stupid to find it?
[Nexus 7 (2013) Original Android Development] draco259:
Just wondering. Would anyone be willing to make a list of roms that are based on aosp and ones that use anything caf? Or if someone could point me in the right direction of what to look for I can make one. If we could get one stickied it might help with some confusion :)
[Nexus 7 (2013) Original Android Development] Cruiserdude:
Stock rom + Xposed modules FTW. GravityBox does as much or more than many roms, and let's you stay stock. And yes, this is completely stock, as in the factory image, then custom recovery, then a kernel. I love flashing new stuff, but I honestly have yet to flash any rom on my flo, going on 2 months now. Stick with AOSP kernels and you're golden.
[Nexus 7 (2013) Original Android Development] tni.andro:
I have a kernel patch for that:

http://xdaforums.com/showthread.php?p=46160175
[Nexus 7 (2013) Original Android Development] paaaulo:
Can we use it with 4.3.1 (deb)?
[Nexus 7 (2013) Original Android Development] jak3z:
Try and let us know please.
[Nexus 7 (2013) Original Android Development] paaaulo:
There is no changelog for 4.3.1 so far. As long as I'm not sure if anything changed on the kernel side I prefer to wait for confirmation.
[Nexus 7 (2013) Original Android Development] jak3z:
Nothing bad could happen, I will do it for you. :confused:

---------- Post added at 01:19 PM ---------- Previous post was at 12:34 PM ----------

Kernel works perfectly fine.
[Nexus 7 (2013) Original Android Development] paranoid android85:
That's my same set up. With xposed framework, I never have to flash another rom
[Nexus 7 (2013) Original Android Development] _Sasan_:
Since two major custom ROM developers group(i.e. PA and CM) have switched to CAF sources, can someone please enlighten me what will be the workaround for the end users to enjoy both (franco.kernel based on AOSP) and one the mentioned custom ROMs based on CAF together?

I would really appreciate!
[Nexus 7 (2013) Original Android Development] shreddintyres:
You can flash it irregardless but you will see a decrease in performance whether or not you notice is another question. I would suggest switch to another Rom i prefer Slim (faster and less bloated) otherwise there are numerous other AOSP roms out there.

- Cheers

PS

[MENTION=3292224]franciscofranco[/MENTION] Would it be feasible to add exFAT or NTFS support or enable module loading? FAT32 is rather cumbersome due to file size limitations.
[Nexus 7 (2013) Original Android Development] Cruiserdude:
Stock + GravityBox Xposed + your favorite AOSP kernel of the week FTW
[Nexus 7 (2013) Original Android Development] wildestpixel:
Stock + GravityBox Xposed + franco kernel FTW
[Nexus 7 (2013) Original Android Development] wayne710:
+1. Exactly where I have ended up. Oh, but add the Boot Manager Mod and Application Picker Mod for an excellent setup!
[Nexus 7 (2013) Original Android Development] SaberJ2X:
any update of CAF situation?

I tried the latest cm 10/4 and it was a no go... So i reverted back to 9/28
[Nexus 7 (2013) Original Android Development] Kayak83:
OK I have to ask...does this not support CPU OC? Or does trickstermod not support Franco?
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
No cpu oc.

Sent from my Nexus 4
[Nexus 7 (2013) Original Android Development] OJ in Compton:
Will the new alternative wake methods (double tapping the screen) Franco is currently working on for the N4 make it to a future version of this kernel, or are there differences in the touch screen controller/digitizer that prevent it?
[Nexus 7 (2013) Original Android Development] ktkr:
There's already other kernels supporting that now so it's absolutely possible, I think we just need to wait.
[Nexus 7 (2013) Original Android Development] bokoy:
None of you read the first post from franco, did you?
[Nexus 7 (2013) Original Android Development] bponury:
I hope franco will enable module support in his kernel (just like with Nexus 4) And then TouchControl will work with it. Right now it works with stock kernel with modules enabled and I'll update it to support Faux in a few minutes. I am using Franco on a daily basis so I hope this will happen soon :)
[Nexus 7 (2013) Original Android Development] ktkr:
I know what you mean but this time it's different, Franco mentioned that this feature will come to this device in his G+ post earlier. See: https://plus.google.com/106873500108976028532/posts/StHfb8LqVyX
[Nexus 7 (2013) Original Android Development] bokoy:
Yeah, it was me the one lost, sorry
[Nexus 7 (2013) Original Android Development] tiny4579:
Are there any known issues with root (koush's superuser) and this kernel with the stock Google image?

I did a search in this thread prior to posting and did not see anyone report anything about losing root in this thread. I went back to stock JSS15R and was able to get root working after messing around a lot. I had to manually push install-recovery.sh to /system/etc to get Koush's working on stock. Since 4.3 was released, root has always been an issue.

It seems that something in the boot.img broke root for me. I think I was using this fine with CM and superuser. I guess I'll try supersu with this kernel.
[Nexus 7 (2013) Original Android Development] ascarda:
Smoothness and long battery time. Awesome

Inviato dal mio Nexus 7 con Tapatalk 4
[Nexus 7 (2013) Original Android Development] projectvii:
Hey Franco,

I have a question about your app and automatically installing kernels.

I have some wifi problems here, and everything takes forever to download. While I was downloading your kernel, through your app, my tablet restarted. But, it wouldn't boot past the Google logo. I'm thinking that the app couldn't finish completing the download, and it flashed a messed up version of the kernel.

So in the end, I'm just wondering is there a timeout delay on the auto flash? And if there is, looks like I'm going to have to manually flash the kernels then.

thanks!
[Nexus 7 (2013) Original Android Development] kecinzer:
Do you anyone suffer with touch not reacting sometimes issues?

https://code.google.com/p/android/issues/detail?id=35663

It make me crazy.
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
Me too. Especially when n7 is lying on a flat surface. For the record,I dont think fk is the reason, happens on every kernel i tried.

Sent from my Nexus 4
[Nexus 7 (2013) Original Android Development] kecinzer:
Yes, its not kernel related.

But I know, that [MENTION=3292224]franciscofranco[/MENTION] has experiences with touch screen tuning. May be he can do somthing about it :).