yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] deedeeceleb:
#1221 is a new deb version

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 7 (2013) Original Android Development] levicius:
Did you test it ?
[Nexus 7 (2013) Original Android Development] deedeeceleb:
I don't own a deb version, only flo

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 7 (2013) Original Android Development] The Gingerbread Man:
I'm not being a fan boy, its down to users to check supported devices. If someone buys a galaxy s4 is Franco supposed to make his kernel compatible with that just because they bought the app? Franco is working on it now please go and untangle your knickers else where
[Nexus 7 (2013) Original Android Development] levicius:
Just tried to install and its bootlooping , like pr0di9y , same problem .

Enviado de meu Nexus 7 usando Tapatalk
[Nexus 7 (2013) Original Android Development] Sleepy!:
It stays stuck on the Boot Animation...
[Nexus 7 (2013) Original Android Development] levicius:
Do you have the deb version ? I didn't manage to install any Franco kernel so far because it seems that deb versions aren't supported, even though there is a r11 deb version ,isn't working too.

Enviado de meu Nexus 7 usando Tapatalk
[Nexus 7 (2013) Original Android Development] Sleepy!:
Yes, I have a Deb, and I know Franco hadn't got Deb support. I've pestered him quite a few times to support it. :P

Great to see he's finally doing it. :)

And I flashed the last boot.IMG he posted, but it seems to be bootlooping.
[Nexus 7 (2013) Original Android Development] v12xke:
Still no go on stock Deb device.

http://pastiebin.com/52dfd71bc2c3f

There seems to be some misunderstanding in this forum because I am reading things like "it don't work...why doesn't he test kernel before uploading?" People need to understand that Franco does NOT have a Deb device and the hardware is different from Flo. He has the Flo version of the hardware. So he is shooting in the dark, working off crash reports. Give the guy a break and don't run him off Deb ffs!

If you have a Deb device, test what he puts forward as quickly as possible, and state you are testing the DEB images on a DEB device.

Franco- anything intended for Deb, even test images should be tagged as such to avoid any confusion.

Thank you.
[Nexus 7 (2013) Original Android Development] bokoy:
Is r12 working good for the flo users?

Thanks
[Nexus 7 (2013) Original Android Development] deedeeceleb:
Just try it yourself :) for me it's working nice

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 7 (2013) Original Android Development] pr0di9y:
Couldn't have say this better myself. Somehow today I've notice that there is some browser issues with Chrome with pastebin than pastie website. Then I hit my head, that I have Opera browser installed, so manage to post the last_kmsg up from my DEB.

Anyway thread follower should always track back on the posts to avoid confusion altogether, tagging the files appropriately or not is not the main issue here.
[Nexus 7 (2013) Original Android Development] arhung:
Delete

Sent from my Nexus 7 (2013)
[Nexus 7 (2013) Original Android Development] HTC Venom:
Lol with r12 my touchscreen has turned to respond much better, I really don't know why, but thanks
[Nexus 7 (2013) Original Android Development] levicius:
Guys , does anyone know this kernel ?

http://xdaforums.com/showthread.php?t=2457886

In the description says its compatible with deb , can anyone confirm if this works in a 4.4.2 ?
[Nexus 7 (2013) Original Android Development] MöCkY_1:
Me too, thanks franco.

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 7 (2013) Original Android Development] deedeeceleb:
The project stopped some time ago

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 7 (2013) Original Android Development] levicius:
Yeah , I am using the elementalx while Franco works in a deb version .

Enviado de meu Nexus 7 usando Tapatalk
[Nexus 7 (2013) Original Android Development] deedeeceleb:
The only thing I'm missing is dt2w

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 7 (2013) Original Android Development] levicius:
Yes,very nice feature !!!

Enviado de meu Nexus 7 usando Tapatalk
[Nexus 7 (2013) Original Android Development] mdamaged:
Francos kernel supports loadable modules, which means you can use this, it works fine for me:

https://play.google.com/store/apps/details?id=me.paranoid.touchcontrol
[Nexus 7 (2013) Original Android Development] deedeeceleb:
I'm actually using tc, but if you want to use dt2w, you have to purchase the app though it's already inbuilt in other kernels. That's no complaint, just my opinion about dt2w :)

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 7 (2013) Original Android Development] creeve4:
Does anyone know of a CIFS module that can be loaded with Franco's kernel?
[Nexus 7 (2013) Original Android Development] mdamaged:
That's only half the battle, something has changed so that even if you get the module loaded, and a cifs share mounted, there is some problem with it using private namespaces.

Here's a rant regarding this change.
[Nexus 7 (2013) Original Android Development] creeve4:
[MENTION=3292224]franciscofranco[/MENTION] what are your thoughts on adding cifs support to the kernel?
[Nexus 7 (2013) Original Android Development] mdamaged:
Actually I just checked, if you do:

cat /proc/filesystems

You can see it has cifs support already.
[Nexus 7 (2013) Original Android Development] jpde:
Sorry if this has been discussed before, but I'm having an issue with the FKU app on my N7 (it's working fine on my N4). It says I don't have root, although I do have it and other apps using supersu (xposed, adaway etc) work. Running r12, supersu 1.91 and the latest OmniRom Nightly (4.4.2.). It's not a huge issue since I don't really need the app, but I was wondering if there's a way to fix it :)
[Nexus 7 (2013) Original Android Development] mdamaged:
Try reflashing supersu.
[Nexus 7 (2013) Original Android Development] jpde:
That was the first thing I tried :) I also set it to accept all root requests, but there isn't even a toast/notification thing of the app asking for root.
[Nexus 7 (2013) Original Android Development] mdamaged:
Did you try uninstalling/reinstalling FKU app? You might want to try booting into recovery and wiping caches.
[Nexus 7 (2013) Original Android Development] jpde:
Haha, nevermind. Apparently I accidentally changed the XPrivacy default to disallow pretty much everything. I added another Xposed module and that wasn't able to get root access either so that seemed curious and I checked XPrivacy.. working just fine now :) Sorry for taking your time :D
[Nexus 7 (2013) Original Android Development] mdamaged:
It's ok, I don't have a lot going on anyway...uhhh, wait...I just made myself sad. :(
[Nexus 7 (2013) Original Android Development] v12xke:
Open up SuperSU and "forget" FKU. Restart FKU and it will request root access again. Works normally after that. Its happened a few times to me as well. Cheers.
[Nexus 7 (2013) Original Android Development] mdamaged:
He fixed it already, it was a setting change in Xprivacy he did.
[Nexus 7 (2013) Original Android Development] em2drvr03:
Is there a way to change the colors with this kernel? App says color control doesn't work.
[Nexus 7 (2013) Original Android Development] :
Color control is (currently) only for Nexus 4, Nexus 5 and Galaxy Nexus :)
[Nexus 7 (2013) Original Android Development] brotbuexe:
If you own both a n7 and n5 and have running franco kernel on them, do you feel that the n5 behaves a lot more snappier with default settings than the n7?

When scrolling in plume or tapatalk for example I don't get the "project butter" feeling on the n7 like I did on the n5.

If you don't have this "issue", did you changed any setting for this in FKU?

I already raised the input_boost_freq to 1,6 ghz but it does not feel better.
[Nexus 7 (2013) Original Android Development] MikeRL100:
I just got a sleep of death on r12, but the issue only seems to happen on OmniROM on this device.
[Nexus 7 (2013) Original Android Development] drdrewdown:
i had SoD too on my self compiled PA build sometime in the past 12 hours while i wasn't using it.
[Nexus 7 (2013) Original Android Development] DanielQQ:
I am feeling the same, but i think it's because the performance difference between the two Snapdragon's
[Nexus 7 (2013) Original Android Development] The Gingerbread Man:
Yes exactly. The snapdragon 800 is a beast of a CPU, the Max speed is 2.26 GHz and the s4 pro from n7 is 1.7 and the 800 uses less juice. The thing is it doesn't need to be as fast as is. The s4 pro chip is the sane chip as the nexus 4, last years flag ship. Its just the natural progression of technology. Soon we see truely silly spec phones with 2k and 4k resolutions and the power the will need to push so pixels will dwarf this generation of devices.
[Nexus 7 (2013) Original Android Development] deedeeceleb:
N7 has a snapdragon 600 locked to 1,5 GHz

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 7 (2013) Original Android Development] The Gingerbread Man:
Its an s4 pro with 1.7ghz on Franco kernel

(Edit) the difference is small, I can't remember exactly what it is. Let me find a link

http://en.m.wikipedia.org/wiki/Nexus_7_(2013_version)

http://cpuboss.com/cpus/Qualcomm-Snapdragon-S4-Pro-(APQ8064)-vs-Qualcomm-Snapdragon-600

https://play.google.com/store/devices/details?id=nexus_7_16gb_2013

http://xdaforums.com/showthread.php?t=2157201
[Nexus 7 (2013) Original Android Development] deedeeceleb:
A s4 pro can't handle ddr3l and since someone opened it, he recognized that it is a snapdragon 600. That's why everyone wonders about Google's understatement! Go read some news site :D

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 7 (2013) Original Android Development] The Gingerbread Man:
Please check the my previous post, especially the one from the Google devices site with tech specs showing s4 pro and Wikipedia and the cpu website showing its native speed of 1.7ghz. The difference is small, something to do with architecture of the core
[Nexus 7 (2013) Original Android Development] deedeeceleb:
That's why I wrote about Google's understatement. Just google "nexus 7 snapdragon 600". And it's the wrong thread :D

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 7 (2013) Original Android Development] The Gingerbread Man:
OK, I see your point but still android news websites aren't always that accurate although at least android authority did go into a little detail. Still these kind of websites reputation isn't the same as Wikipedia for instance and why would Google down play the CPU name, its a marketing point to have a better CPU, the unit would still cist the same to produce and sell
[Nexus 7 (2013) Original Android Development] zaclimon:
Anandtech did open the device and saw that the cpu (APQ8064–1AA) is different from the one on the Original S4 pro. (APQ8064) The main difference is that there's Krait 300 cpu cores instead of Krait 200 like with the S4 Pro inside the Nexus 4, which makes it looks like more of a Snapdragon 600 than an actual S4 pro. The naming however I think is more because of the defafult clock speed (1.5 vs 1.7 in base SD600)

Here's the link if you need it:

http://www.anandtech.com/show/7176/nexus-7-2013-mini-review/4
[Nexus 7 (2013) Original Android Development] nickj2010:
Also got a SOD on stock rom, was getting them on r10 and hoped that the reboot fix on r11 would help, guess it's back to stock kernel again as I use my tablet as an alarm, so it can't randomly turn off at night :(
[Nexus 7 (2013) Original Android Development] bervin:
[MENTION=5521507]TheGinger[/MENTION]breadFANBOY

THE S4 pro is a underclocked and re-branded s600. If you did study economics and business you would know that there a variety of reasons as to why they would list this as a s4 pro. But I'm sure your reply will lack any intellect and just be filled with for a lack of better word. Ignorance. :eek:
[Nexus 7 (2013) Original Android Development] albundy2010:
Sigh. Google didn't downplay anything

Qualcomm decides what gets labeled what. Nobody else. They decided to draw a messy line in their product line as to what is what.

A s600 cpu clocked down is a s4 Pro. A s600 with two cores is a s4 Pro.

If you want to know the difference between a krait 200 core and a krait 300 core and you're looking at Wikipedia, Android blogs ( all of them, no exceptions) you're looking in the wrong places.

This is what we get when our tech "reviewers" are nothing more than people who read the specs off the box and go it feels nice etc.
[Nexus 7 (2013) Original Android Development] Bobtehblob:
Wondering if any of you guys are able to help my friend. He's on stock 4.4 with Franco Kernel installed and he wants to install the ota. Obviously he needs to flash back the stock kernel but what files does he have to rename?
[Nexus 7 (2013) Original Android Development] habylab:
Did the max CPU get reverted back to 1.5 instead of 1.7? Deadline did not change either, had to manually.
[Nexus 7 (2013) Original Android Development] poondog:
Hi, why are we being so attacking? I'm not trying to create trouble at all

The processor in this device is not the same as nexus 4, nor is it the same as the s600 of the One and SGS4

It sits in the middle, let's call it a s4+ or s4s and stop the conflict please?

Thanks
[Nexus 7 (2013) Original Android Development] The Gingerbread Man:
Now let's not make this personal, I won't fall into making about personal attacks. Say what you like I will just ignore you. Have a nice day

---------- Post added at 11:03 AM ---------- Previous post was at 11:00 AM ----------

Its easier to just fastboot flash system system.img and fastboot flash boot boot.img from the Google factory image site.

---------- Post added at 11:05 AM ---------- Previous post was at 11:03 AM ----------

Iv learnt something new, I thought they were near enough the same but there is some differences as provided by some one. Thanks for sharing your knowledge and helping me learn

---------- Post added at 11:06 AM ---------- Previous post was at 11:05 AM ----------

I wasn't really trying to make a conflict just discussing that's all. I have come away with some new knowledge thanks guys
[Nexus 7 (2013) Original Android Development] GrijzeGeest:
Deadline did change for me after clearing fku app settings, but 1.7 indeed changed to 1.5 . The settings for the interactive gov still seem optimised for 1.7 though?
[Nexus 7 (2013) Original Android Development] The Gingerbread Man:
Hmm seems your half right, I have 1.5 GHz Max as default but deadline is showing as default scheduler.
[Nexus 7 (2013) Original Android Development] conantroutman:
Well, that was unnecessarily rude. :(

Let's try and keep the conversation civil and free of flaming shall we gents? Much appreciated. :)
[Nexus 7 (2013) Original Android Development] The Gingerbread Man:
thanks, you should see how it started
[Nexus 7 (2013) Original Android Development] LouisTran:
is r12 work for Nexus 7 LTE ver? I have just flashed and boot looping :(
[Nexus 7 (2013) Original Android Development] The Gingerbread Man:
Not yet I'm afraid. Its being worked on but franco has the WiFi only model, they differ in hardware and its proving to be difficult to get the kernel to boot because of the hardware variance
[Nexus 7 (2013) Original Android Development] LouisTran:
So sad but thanks you, Is there any kernel work with LTE ver?
[Nexus 7 (2013) Original Android Development] brotbuexe:
About the "scrolling" performance. Thanks for the explanation about the cpus.

I played a little bit with FKU and used cpu core percentage and freq overlays (with Usemon) to see whats going on while scrolling in tapatalk threads and plume timeline.

When I just enable the perfomance govenor with 1,72 GHz I get scrolling like butter, which is obviously because of the lock of all CPUs to full thrust. In plume I get short hickups sometimes when it loads a picture. But for me its a lot snappier as with interactive. Of course no one would like to have all the cores to 1,7 GHz all the time.

But could you check if you have the same behaviour / experience with a setting like that?

I tried limiting to 1,4 GHz, it was not so good anymore but I felt it was better than interactive max 1,7 GHz.

With interactive I see that when I touch the display it sets two cores to the "input_boost_freq". Then after some time other cores are getting up too, but at that time I already had the stutter in scrolling.

I don't understand all the settings in FKU, perhaps there is a better way, but would it be good to have something like a "input_boost_cpus" where you can set how many cpus the governor should wake to input_boost_freq when I touch the display?

I think I could live with a boost of all cores to 1,4 or even 1,7 GHz when I touch the screen to get response like I get from my n5. When I not hit the display it could get down again like it does now.

---------- Post added at 08:25 PM ---------- Previous post was at 08:17 PM ----------

The others already answered your question that it is built in (no need for loading modules).

I tried mounting stuff via adb shell and "busybox mount -t cifs ...", but I could only get it accessible inside the adb shell, not from android apps. Someone had this issue too (on stock rom) and found a little crazy solution, by using custom mountscripts and do mounting through a ssh session to localhost to switch the namespace. :) http://xdaforums.com/showthread.php?t=2469040

Perhaps you could try that if you have time. I didn't had it yet.

But we should use the cifs thread to talk about using the nokernel solution he posted.

The same issue should be with nfs, but it seems nfs is only in francos n5 kernel for now.

---------- Post added at 09:06 PM ---------- Previous post was at 08:25 PM ----------

Is it only me or does the PerAppMode settings only works after starting the FKU app one time after boot?

For now I use PerAppMode to change the govenor to performance while using stuff like Tapatalk or Plume.
[Nexus 7 (2013) Original Android Development] TheMrcool212:
Nvm
[Nexus 7 (2013) Original Android Development] bervin:
Yeah, he should. Naivety and such fierce loyalty(Fanboyism) from yourself and clearly instigating me with your now edited post in which in open by cursing at me using vulgarities.

touché old chap.

Now to make this post not so absolutely off topic, does anyone know where in gerrit can i find the code to disable magnetic wake. Much thanks
[Nexus 7 (2013) Original Android Development] E.Cadro:
He did not edit his post another Moderator did and honestly it doesn't make a difference a senior moderator asked that you guys stop. So I am going to ask one more time please stop and get back on topic. Thanks
[Nexus 7 (2013) Original Android Development] cobyman7035:
seriously thinking of jumping from eX to franco on my FHD

1) does it have color control profiles like the nex5?

2) fast charge usb work?

thanks
[Nexus 7 (2013) Original Android Development] brotbuexe:
1) no

2) yes
[Nexus 7 (2013) Original Android Development] mdamaged:
FWIW, it happend to me too on r10 and r12 just now, with stock ROM.
[Nexus 7 (2013) Original Android Development] frozst:
[MENTION=3292224]franciscofranco[/MENTION] do you know if is it possible to have support on the USB OTG driver for the N7 2013? I am trying to use a Logitech keyboard and mouse but they don´t work. Seems that only a few kernels support it.

http://xdaforums.com/showthread.php?t=2425622&page=2

Thanks!
[Nexus 7 (2013) Original Android Development] aamitabh28:
Use stickmount app
[Nexus 7 (2013) Original Android Development] InfectedSoap:
StickMount only works for mounting storage. This is quite a separate thing.
[Nexus 7 (2013) Original Android Development] osm0sis:
I know USB OTG storage isn't even set up yet. I was looking into it last night since I noticed it wasn't in the fstab.
[Nexus 7 (2013) Original Android Development] drms12:
Franco , I just noticed that using latest r12 my tablet reboots itself while sleep with screen off.
[Nexus 7 (2013) Original Android Development] Sleepy!:
^This
[Nexus 7 (2013) Original Android Development] frozst:
I will try with another kernel but seems that is detected but doesn't sound...
[Nexus 7 (2013) Original Android Development] LouisTran:
Sorry, wrong thread
[Nexus 7 (2013) Original Android Development] shreddintyres:
My understanding of how it all works requires that a key layout be present, not kernel related, now depending on whether the device is providing enough power to utilize the devices is another story use an otg diagnostic app on the market (otg Helper I think it's called) to check if the device is recognized if it is not then it's likely not getting enough juice from the n7 which may be kernel related however if it is detecting a device but doesn't know what it is you need to provide a new key layout for it. Just like when you are trying to use 3rd party Xbox 360 controller or ps3 controller you will need to know the vendor and product ids for your device, how ever i suspect you are using a universal Logitec dongle which may add some complexity to it, I hope this info helps somewhat

-cheers
[Nexus 7 (2013) Original Android Development] rodrigo9411:
Mine does that too. Noticed because the right icon in the dock (gel) disappeared several times
[Nexus 7 (2013) Original Android Development] TrenchKato:
The icon disapearing is a bug in gel... It's not fully compatible with the n7 yet
[Nexus 7 (2013) Original Android Development] rodrigo9411:
I know that, I was just saying that's how I noticed that the tablet rebooted itself while screen was off
[Nexus 7 (2013) Original Android Development] GeoVali99:
The Logitech Unifying Receiver is surely the problem.I connected a Microsoft wireless mouse to the tablet,it worked.But,when I tried the wireless Logitech keyboard,it didn't.
[Nexus 7 (2013) Original Android Development] justibasa:
Reboot on carbon latest nightly with r12. http://pastie.org/8687653
[Nexus 7 (2013) Original Android Development] Exostenza:
I'm running Franco on my nexus 5 and it is amazing. Looking to run it on my new n7 but this rebooting issue is holding me back. How active is fanco here guys? Seeing how active he is on the n5 it would stand to reason that he wouldn't be very active in his other projects. He is the bomb though and that wasn't a knock against him as there is only so much one person can do and I realize that.
[Nexus 7 (2013) Original Android Development] The Gingerbread Man:
So the thing is the n5 is where stuff is being tried and tested and things get ported to here and nexus 4. As they are all Qualcomm chips its all compatible. There's been a few updates here bringing stuff from the nexus 5 here. I can't remember where I said this before but the sort of rules which seem to apply are

1 newer devices first

2 phones before tablet

3 port success to other devices
[Nexus 7 (2013) Original Android Development] Exostenza:
Thanks for the answer. So, are most people running this kernel just fine or is the reboot while issue wide spread?
[Nexus 7 (2013) Original Android Development] The Gingerbread Man:
Personally not an issue I'm facing. Are you undervolting?
[Nexus 7 (2013) Original Android Development] mdamaged:
Some N7 users, including myself have had sleep of death issues (I'm not UVing or OCing and I'm on stock ROM) franco was notified in G+ about it, he said he'd look into it, I'm not sure if it's related to the reboot issue though. For now, I'm back on stock kernel which is doing fine.