yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] alister91:
web browsing with chrome beta??? if you have installed chrome beta, unistall it.... for me it works :D
[Nexus 7 (2013) Original Android Development] AutomaticFailure27:
I've noticed that too. That sometimes the screen will freeze for a good 3 seconds or so, then will go nuts because I tried to touch different places at once and the tablet is attempting to keep up.

Usually, happens once about everytime I use the thing, but after that, all is good.
[Nexus 7 (2013) Original Android Development] Remoteconcern:
It's a problem with the ROM/Android, not the kernel.
[Nexus 7 (2013) Original Android Development] bokagavrilov:
Franco touch control has been released for the n7 could you please enable modules support for this too?
[Nexus 7 (2013) Original Android Development] cowabunga:
Is franco r3 working with the latest cm nightlies?
[Nexus 7 (2013) Original Android Development] mrbradeli:
Chrome beta? No, just plain Chrome. Either way, it happens in both Firefox and Chrome. I think its a GPU issue, considering it also happens when playing video with HW decoding.
[Nexus 7 (2013) Original Android Development] phydo:
I'm just getting a blue screen on boot
[Nexus 7 (2013) Original Android Development] zaclimon:
Its happening with the newer pac nightlies as well, looks like they've done some nasty stuff Lool.

Envoyé depuis mon Nexus 7 avec Tapatalk 4
[Nexus 7 (2013) Original Android Development] Cruiserdude:
Encourage your favorite devs to move their rom to an AOSP base and it'll work perfectly. I don't see any reason for anyone other than CM to be on a CM base on a Nexus device. We have complete, buildable source, and no need to use generic CAF libraries.
[Nexus 7 (2013) Original Android Development] jak3z:
Are you under LTE/3G? All the problems look like your modem derped somehow...
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
You mean the drivers or the hardware itself?

Sent from my Nexus 7²
[Nexus 7 (2013) Original Android Development] jak3z:
90% chance being the driver, as seen on Nexus 4, some people just get random reboots on 3G because the modem is connected internally using USB, and the implementation is a bit... bad.
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
Thanks.

I'm using the wifi version and had one while watching videos on mx player.

Could you please take a look?

http://www.mediafire.com/?n0yu27rcgczd9rb

Sent from my Nexus 7²
[Nexus 7 (2013) Original Android Development] jak3z:
That log doesn't provide any info why sadly, the tablet just rebooted because something asked the tablet to reboot.

When you get another reboot, try getting a log again from /proc/last_kmsg
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
Sure. Thanks. I use this app called Syslog.

https://play.google.com/store/apps/details?id=com.tortel.syslog

Should be fine i guess?

Sent from my Nexus 4
[Nexus 7 (2013) Original Android Development] jak3z:
Never used it, but if the app gets the last_kmsg I don't see why it wouldn't work.

If you want to try manually, open Terminal, type: su and hit enter, then type: cat /proc/last_kmsg > /sdcard/last_kmsg.txt and that should output the file to your sdcard root folder.
[Nexus 7 (2013) Original Android Development] mrbradeli:
Wifi. A lot of my reboots happened with MX Player as well.
[Nexus 7 (2013) Original Android Development] jak3z:
I need more logs to know whats going on.
[Nexus 7 (2013) Original Android Development] mrbradeli:
Sadly all of the last_kmsg's say the same thing so far. I'll try to cause a few more reboots to see if I can get anything more out of it.
[Nexus 7 (2013) Original Android Development] tiny4579:
Look at the top of the file, that's tassadars kernel. I think that is from recovery. Maybe it was a soft (ROM) restart. Logcat is better in that case.
[Nexus 7 (2013) Original Android Development] mrbradeli:
I actually decided to try and capture what was going on via logcat, but my nexus 7 refused to crash whenever I had it running in adb.
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
Insane battery...! Few hours of browsing, and watched a few episodes of Game of thrones. WiFi on all the time. Idle drain (flight mode) is almost negligible. Very impressed. Waiting over the complete stats. Running aokp, hotplug control-screen off max to 384. Everything else default. No uc/uv. :thumbup:

Sent from my Nexus 7²
[Nexus 7 (2013) Original Android Development] Nbsss:
Question, have the browser force closes with the early 4.3 xposed framework been fixed?
[Nexus 7 (2013) Original Android Development] Cruiserdude:
The dev said he fixed them awhile back. I haven't had any issues in over a month. Then again, I haven't used Chrome Beta on my Flo either since then. I do still run Chrome Beta on my GS4, which is running a GPe source-based AOSP 4.3 (as opposed to CM-based, though it still needs some CAF vendor files to work :mad:). Anyway, same Xposed mods on my phone as I run on my tablet, and no issues with FC's, freezes, or reboots. So I'd say you're good to go, and if not, just ditch Chrome Beta for Chrome stable.
[Nexus 7 (2013) Original Android Development] ckisgen:
I'm using Xposed and Chrome Beta currently and have no freezes or RRs.

It's a pretty darn slick setup, IMHO.
[Nexus 7 (2013) Original Android Development] Nbsss:
Thanks man, I loved the app settings module's full screen mode, great to hear I can use it again w/o FC's!

Edit: Gravitybox is.... AMAZING
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
Just gonna leave this here. ;)

Sent from my Nexus 7²
[Nexus 7 (2013) Original Android Development] creeve4:
Thoughts on this Franco?
[Nexus 7 (2013) Original Android Development] Nbsss:
Is kexec support planned?
[Nexus 7 (2013) Original Android Development] Ronaldo Forenucci:
I'm here! (LOL, who is this guy?) :D Just picked up a 32Gig Flo Wi-Fi at Office Max. They honored the Aug 10 20% off coupon - $228 + Tax. Just installed Franco r3. Currently running CleanRom with the Xposed framework and GravityXposed, but waiting for Rasbean Jelly. I need to go back through the 53 pages, but are the Franco defaults what everyone is on? N7 2012 was Ondemand/Deadline. Glad to be here!

RF
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
Yep. The defaults are good. You can find my battery cycle with defaults above.

Sent from my Nexus 7²
[Nexus 7 (2013) Original Android Development] kingston73:
Maybe a stupid question but does this kernel do something with the colors? I swear after changing from this kernel to a different one my colors seem muted but it might just be me making things up?
[Nexus 7 (2013) Original Android Development] Shocky2:
The paid app doesn't work, keeps force closing. :silly:
[Nexus 7 (2013) Original Android Development] Ronaldo Forenucci:
Try clearing app data through the app, or in settings>apps, and re-boot.

RF
[Nexus 7 (2013) Original Android Development] wildestpixel:
Are you on Project Pringles ?
[Nexus 7 (2013) Original Android Development] bobloadmire:
I just bought the paid app installed kernel on cm, and errors and a blue screen. Pretty bummed. Not a cheap app.
[Nexus 7 (2013) Original Android Development] -Jesco-:
CM is now using CAF libs , causing AOSP kernels not to function properly on CM (display issues) blame CM for using caf or hope that franco would make a caf kernel for CM
[Nexus 7 (2013) Original Android Development] goldflame09:
Pac for flo and deb is gonna switch to aosp base
[Nexus 7 (2013) Original Android Development] bobloadmire:
Why did they do that?
[Nexus 7 (2013) Original Android Development] -Jesco-:
Ask cm no one knows why
[Nexus 7 (2013) Original Android Development] poondog:
Could be performance

Could also be to unify a lot of devices with a common kernel source etc
[Nexus 7 (2013) Original Android Development] GialanG:
MultiRom support

Hi OP. I love your kernel in combination with MultiRom since Nexus 7 2012, and now I really miss it on my N7 2013 when using MultiRom. Will you please add the MultiRom support into this kernel like you did? Many thanks!

Here is the link of MultiRom for N7 2013: http://xdaforums.com/showthread.php?t=2457063
[Nexus 7 (2013) Original Android Development] MBQ_:
'The only ROM for stoners.'
[Nexus 7 (2013) Original Android Development] guyd:
Carbon already ditched the caf libraries and went straight aosp.
[Nexus 7 (2013) Original Android Development] Bobtehblob:
It's merged on his n4 kernel so I'm sure it will also be included here when he gets around tonight :)
[Nexus 7 (2013) Original Android Development] spacemanvt:
i just did this as well, how can i flash back to the CM kernel? im kinda stuck :(
[Nexus 7 (2013) Original Android Development] zaclimon:
Take the boot.img out the cm zip you download then flash it with fastboot while in bootloader mode:

fastboot flash boot /path/to/image
[Nexus 7 (2013) Original Android Development] spacemanvt:
dang i just did a full reset and reflash CM. would that have allowed me to install the kernel only without reflashing?
[Nexus 7 (2013) Original Android Development] zaclimon:
Yep only the kernel.
[Nexus 7 (2013) Original Android Development] spacemanvt:
Thanks I'll know for next time
[Nexus 7 (2013) Original Android Development] Nbsss:
Just used my kit kat credit to support you ;)
[Nexus 7 (2013) Original Android Development] Jonnyredcorn:
I'll be interested to see how Franco works with this device. It has some strange thermal issues it seems, I'm getting amazing idle battery life though, best I have ever gotten on my nexus 7 and best I have ever gotten on an Android device. Comparable performance to elementalX(as in both are fast as hell and it's hard to notice a difference) although I did have elementalX OC'd to 1.7gHz.

Only feature I miss which it looks like will get added is doubleknock2wake, comes in handy when it's sitting landscape in my Moko multi angle case.

Sent from my kangabeaned, AT&T Galaxy S4 powered by knonez!
[Nexus 7 (2013) Original Android Development] AnarchoXen:
Works well. http://xdaforums.com/showthread.php?p=45906758
[Nexus 7 (2013) Original Android Development] bokagavrilov:
Franco could you make a 191-like kernel for this? :) with tc module support too if possible? It hasn't been updated for a while. And the 191 it's the best kernel I ever used on my Nexus 4
[Nexus 7 (2013) Original Android Development] jak3z:
As soon as he gets r4 out I will update my Touch Control version :)
[Nexus 7 (2013) Original Android Development] Ramone360:
Does this kernal supports 4.3.1?
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
Yes.

Sent from my Nexus 4
[Nexus 7 (2013) Original Android Development] linkit87:
Hi. I'm with stock kernel right now. I'd like to have stability, good battery life and otg support. Is this the kernel for me?

Inviato dal mio Nexus 7 con Tapatalk 4
[Nexus 7 (2013) Original Android Development] shreddintyres:
Every device is ever so slightly different, and every user has different usage needs, its perfect for me but YMMV test out different kernels to see which works best for you

- Cheers
[Nexus 7 (2013) Original Android Development] TrenchKato:
As far as stability ghost Franco is at the top of my list. Since this device uses the same CPU as the Nexus 4 , most of the things that have been merged thus far have already been tested extensively. The custom hotplug makes battery life amazing. It allows the CPU to use lower frequencies than stock ( the stock kernel seems to be stuck at 1026 MHz because of project butter)

I remember reading in the Nexus 4 thread that Franco would not support OTG but I may be wrong.

That being said, I recommend Franco kernel. No frills no bloat no buzz words. But what works for me might not work for your needs so I do recommend you try others too.
[Nexus 7 (2013) Original Android Development] Ramone360:
Doesn't work!
[Nexus 7 (2013) Original Android Development] bokagavrilov:
Which rom do you use if it's CM I won't be surprised
[Nexus 7 (2013) Original Android Development] Ramone360:
Yes sir cm it is. OP said it works on every rom!

Problem: boot and hangs with blue lines
[Nexus 7 (2013) Original Android Development] bokagavrilov:
The problem isn't the op it's CM they decided to go to their own path with choosing the caf libraries (that breaks the compatibility with every aosp kernel) better change rom or use CM kernel
[Nexus 7 (2013) Original Android Development] farfetch:
Hi, I have r3 Kernel + Paranoid Android 3.99. I can use USB Drive OTG, but not input devices.

I tried with:

USB 3.0 drive 8GB: OK

Logitech anywhere MX (wireless mouse): NO

Razer Onza (joypad): NO

I tried these devices on my Galaxy S4 with same rom and they worked

I tried USB drive and mouse on my HTC ONE X with latest MIUI and Mouse and USB drive worked, the joypad din't but maybe is the MIUI interface, I have no game to try with.

I can't try keyboards because I have a Razer Blackwidow and it has 2 USB cables to power it.

Can you help me, please?

EDIT: my Cybord R.A.T. 7 (wired mouse) works. Is maybe a driver Issue? maybe a kernel module or something?
[Nexus 7 (2013) Original Android Development] jak3z:
It's something to do with your input devices xml mapping, I would go deep into this matter but it's annoying as hell, AOSP support some basic USB stuff like universal bus mouse/keyboards/drives, but some of the NAMED usb controllers like the onza won't work because the ROM doesn't contain mapping information about how to handle the input.

You can have a look into this thread: http://xdaforums.com/showthread.php?t=1792531 it's for a Xbox controller (included in AOSP 4.3) but you can get the idea on how to approach your issues :)
[Nexus 7 (2013) Original Android Development] farfetch:
Thanks but... They work on my S4 with same rom (PA 3.99 rc2). I tried to copy InputDevices.apk but unsuccessfully, now it doesn't figure in my installed apps, Imma restore the original one. But what about that xml file?
[Nexus 7 (2013) Original Android Development] jak3z:
the APK got nothing to do, you should compare the files mentioned in that thread, but the ones that got something to do with what you are trying to plug-in. Each device got his ManufacturerID DeviceID, to debug all that information you should read the dmesg output when you plug in the device and see what android says when you plug a device that does nothing.

If you don't know how to do this... It's kinda complicated to do anything else, you should learn how see your dmesg, filter it and some stuff.
[Nexus 7 (2013) Original Android Development] farfetch:
Let me have a breakfast... I'll try to brick my nexus later :D

Inviato dal mio GT-I9505 con Tapatalk
[Nexus 7 (2013) Original Android Development] jak3z:
Thats why you got a nexus, you can't brick it :P
[Nexus 7 (2013) Original Android Development] kgirlx:
Hi all. Just wanted to say I finally installed this on my N7 2013 Flo, running CR 1.7. Using the zip file and TWRP, it installed flawlessly. All is well, looking forward to an even better battery life with this kernel. Thanks
[Nexus 7 (2013) Original Android Development] mrbradeli:
How likely is it that TWRP was the cause of my random reboots and force closes? Is that even a possibility? How about undervolting? Could that cause force closes? I know that could be the source of my random reboots, but I'm just trying to explore every possible option.
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
I don't think twrp is the reason. Undervolting sounds like the probable cause of your issues

Sent from my Nexus 7²
[Nexus 7 (2013) Original Android Development] mrbradeli:
Lets hope so. I'm going to try if I can get this thing to force reboot on stock (though it seems incredibly stable whenever I actually try), and then on Franco r3 without undervolting. Hopefully undervolting proves to be the problem so I can just stop doing it and have a stable device.
[Nexus 7 (2013) Original Android Development] Ronaldo Forenucci:
Encryption and r3

I think I've discovered a problem with r3 when a tablet is encrypted.

I have a flo 32G Wi-Fi. Since purchase, I have run it unlocked/rooted stock JSS15R with r3 - no problems.

PSX v6 JSS15R unlocked/rooted with r3 - no problems.

CleanROM 1.7 JSS15R unlocked/rooted with r3 - no problems.

and finally, RasbeanJelly JLS36I unlocked/rooted with r3 - no problems.

Today, after settling on RBJ as my final choice, I encrypted the Tablet. Once encryption was finished and I rebooted, I noticed that I wasn't getting toast notifications for franco, Avast firewall, etc... I went to SuperSU 1.65 and tried to open it, and was notified that that there was problem that SuperSU couldn't find itself, and to manually re-root. I also checked Busybox, and it too reported a problem and wouldn't open.

So I booted into TWRP, entered my decryption pass, and then re-flashed SuperSU. No joy, problem still existed. I did it again, and also wiped Cache/Dalvik....still no workee, no root.

So finally, I dirty flashed RBJ again (same ROM, so dirty is fine) after a Cache/Dalvik wipe, and BOOM, root was back with the stock kernel that RBJ supplies. I then flashed r3, re-booted, and BOOM, lost root again.

So I think us security minded folks have a problem (for now), in that r3 seems to do something funky when encryption is enabled.

Thanks, let me know what I can test for you franco,

RF
[Nexus 7 (2013) Original Android Development] wildestpixel:
You need to fastboot flash your way out of this.

Modified devices and encryption is both paradoxical and a no no.
[Nexus 7 (2013) Original Android Development] SkaDiZ:
Is it possible to flash Franco Kernel over elementalx? Or do I need to reflash ROM+Gapps then flash Franco?
[Nexus 7 (2013) Original Android Development] jak3z:
You should be fine, but as far as I know ElementalX creates some files like init.d scripts and more stuff, so be careful that when you flash franco those files doesn't mess with the current kernel. It shouldn't but it's a warning :)
[Nexus 7 (2013) Original Android Development] SkaDiZ:
Lol... I think the safe way is to reflash my current ROM then flash Franco.. Any other idea??
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
Yes. Just dirty flash. Don't wipe anything

Sent from my Nexus 4
[Nexus 7 (2013) Original Android Development] jak3z:
Just flash franco kernel, but if you want to go back stock, you will need to flash rom + stock kernel.
[Nexus 7 (2013) Original Android Development] Ronaldo Forenucci:
franco has worked with encryption going all the way back to the GNex...never had a problem. To be clear, I'm not dissing the kernel...I suspect it's a 4.3.x thing...I just ONLY use franco.

I'm not "in" anything, I'm just running stock kernel at the moment. Are you saying if you fastboot flash the franco .img, that root will be retained on an encrypted device?

Disagree on "modified" being a no-no with encryption. I'll give one very good example (there are many): EncPassChanger. It hooks into dm-crypt and allows the PBA pass to be MORE than the Google limited 16 characters AND different than the lock screen pass. I trust AOSP and devs like franco, rascarlo, and corwin...more than I trust stock Google.

RF
[Nexus 7 (2013) Original Android Development] greenro89:
What are stock Franco settings? Rebooting after a flash changed what it was before so now I'm confused :/
[Nexus 7 (2013) Original Android Development] bokagavrilov:
I know what op says I'm a long time user of Franco's kernels but if you used elementalx you would know that it doesn't have nothing to do with touch control... There isn't even touch control for n7...it installs it from the kernel with the A–something installer
[Nexus 7 (2013) Original Android Development] jak3z:
Do you know how hard it was for me to get him the device? :silly:
[Nexus 7 (2013) Original Android Development] ktkr:
Let the story begin. xD
[Nexus 7 (2013) Original Android Development] habylab:
Random reboots, I've tried to attach a log below.

https://app.box.com/s/7wigm6juap0i7b3h46bn
[Nexus 7 (2013) Original Android Development] deezid:
Here on my Nexus 7 LTE (DEB, razorg) it ends in a bootloop. :(

Device is rooted and has latest firmware installed (jls36c).

Have to flash new boot.img and system.img (and data wipe) to recover... :(
[Nexus 7 (2013) Original Android Development] jak3z:
As far as I can see you are using Chrome Beta, uninstall that and you should not have any random reboots. :good:

---------- Post added at 12:51 PM ---------- Previous post was at 12:50 PM ----------

My device is a Nexus 7 LTE, and it works perfectly, so you did something wrong while flashing, what did you do to flash this kernel?
[Nexus 7 (2013) Original Android Development] deezid:
My device is a Nexus 7 LTE, and it works perfectly, so you did something wrong while flashing, what did you do to flash this kernel?[/QUOTE]

Flashed the kernel with TWRP and rebooted. -> bootloop

Wiped Dalvik and cache. -> started, then updating Android screen -> after 15 minutes still the same screen...

reboot

wiped Dalvik and cache -> bootloop.

factory reset -> bootloop

Flashed new System and Boot images (franco is uninstalled)

boots fine!

flashed franco kernel through TWRP -> bootloop

lol
[Nexus 7 (2013) Original Android Development] jak3z:
Probably the zip is wrong then, flash the boot.img using flashify or franco kernel updater app, or using fastboot .
[Nexus 7 (2013) Original Android Development] deezid:
Will try his boot.img (maybe something is wrong with TWRP, downloaded the Zip-File twice)
[Nexus 7 (2013) Original Android Development] jak3z:
Make sure you are using the 2.6.3.0 TWRP, the 2.6.0.0 was very experimental.
[Nexus 7 (2013) Original Android Development] deezid:
Even for DEB, nice! :)
[Nexus 7 (2013) Original Android Development] habylab:
Really? So why is it causing it? Normal Chrome instead then?
[Nexus 7 (2013) Original Android Development] jak3z:
Use normal chrome if you want, or install AOSP browser, it's a Beta after all, so this kind of stuff can happen, if I was google I would not have released an app that could cause phones to reboot but it does.

Some proof:

[ 803.557525] type=1400 audit(1379327762.030:3333): avc: denied { create } for pid=2352 comm="com.chrome.beta" name=".com.google.Chrome.Au2205" scontext=u:r:untrusted_app:s0:c90,c256 tcontext=u:object_r:unlabeled:s0:c90,c256 tclass=file
[ 803.558197] type=1400 audit(1379327762.030:3334): avc: denied { read write open } for pid=2352 comm="com.chrome.beta" name=".com.google.Chrome.Au2205" dev="mmcblk0p30" ino=90591 scontext=u:r:untrusted_app:s0:c90,c256 tcontext=u:object_r:unlabeled:s0:c90,c256 tclass=file
[ 803.560028] type=1400 audit(1379327762.040:3335): avc: denied { rename } for pid=2352 comm="com.chrome.beta" name=".com.google.Chrome.Au2205" dev="mmcblk0p30" ino=90591 scontext=u:r:untrusted_app:s0:c90,c256 tcontext=u:object_r:unlabeled:s0:c90,c256 tclass=file
[ 803.560455] type=1400 audit(1379327762.040:3336): avc: denied { unlink } for pid=2352 comm="com.chrome.beta" name=4C6F63616C205374617465 dev="mmcblk0p30" ino=90792 scontext=u:r:untrusted_app:s0:c90,c256 tcontext=u:object_r:unlabeled:s0:c90,c256 tclass=file
[Nexus 7 (2013) Original Android Development] deezid:
Guess what? -> Bootloop. (stock, factory resetted JSS15J, Nexus 7 DEB LTE razorg europe)

Used the boot-r1.img

Very strange.

I'll wait for a new version
[Nexus 7 (2013) Original Android Development] habylab:
Wow. Thank you for that! Very odd considering it is fine on my Galaxy S3, and has been for months!
[Nexus 7 (2013) Original Android Development] shreddintyres:
Reproduce the random reboot and please post your last_kmsg found under /proc it will help Franco and the rest of us to narrow down the exact cause for the reboot.

- Cheers
[Nexus 7 (2013) Original Android Development] jak3z:
Verify that your downloads are correct, I will provide you a .img with the MD5, just to be sure, I have dumped this .img from my Nexus 7 LTE.

MD5: C958A92845C52BF03321E76EB000B6AC

IMG attached.
[Nexus 7 (2013) Original Android Development] deezid:
I've reproduced the bootloop at least 5 times now. ;)

How can I access this folder?
[Nexus 7 (2013) Original Android Development] jak3z:
It's not a random reboot, he is on a bootloop everytime he tries to flash the kernel.