yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] STk3000:
Same here with utorrent for Android... Of puts the n7 in a sleep of death situation where I can only reset it.. Running with paranoid 3.99...
[Nexus 7 Original Development] The Gingerbread Man:
I think changing to row fixes torrent issues if I remember right
[Nexus 7 Original Development] DottorSam:
So isn't it a bug? Is it a scheduler limit?
[Nexus 7 Original Development] CPA Poke:
For anyone who wants to run this kernel with MultiRom, I patched it with kexec and it works great. Hopefully the dev won't mind - I didn't touch any of the source, so this should be the exact same as n75 - except with MultiRom compatibility.

Flashable zip: http://www.mediafire.com/?3u2a33q7w5321nz

Boot.img: http://www.mediafire.com/view/?d7gbmigmrzmqa11
[Nexus 7 Original Development] NYLimited:
[MENTION=3292224]franciscofranco[/MENTION]

Is this something that could be added to the N7 kernel also whenever you get back to it?

---

Any clod can have the facts, but having an opinion is an art.
[Nexus 7 Original Development] osm0sis:
Here's the list we've compiled for [MENTION=3292224]franciscofranco[/MENTION] of what's missing in r75 vs. pre-rebase:

f.K grouper: kexec-hardboot; roughly stock freq steps; ?wifi pm fast; cpu temp+freq, ?gpu freq display; ?voltage control; ?gpu oc; ghl + tl; ?min battery update 10 not 60;

Also, f.Ku: some options don't work with other kernels (looking for internal bb?);
[Nexus 7 Original Development] pan.droid:
Is "restrict mem access" implemented in this kernel? If not, could it be?

See:

http://dev.gentoo.org/~swift/docs/s...l.html#item-gt-kernelconfig-restrictmemaccess

Thanx=)
[Nexus 7 Original Development] vietkao:
[[DUMB QUESTION]]

Can I use r75 with a 4.2.2 ROM? Is there any bad effect on the ROM or the device?
[Nexus 7 Original Development] LordDeath:
r75 shouldn't boot on 4.2.2. ROMs. The latest kernels for 4.2.2 can be found here: http://minooch.com/franciscofranco/Nexus7/4.2/zips/
[Nexus 7 Original Development] nexusmaniac:
Hey Franco, have you got a local build better than the current r75? Because even with your current kernel my device feels laggy, it has caused me to stop using it :(
[Nexus 7 Original Development] CPA Poke:
*sigh*
[Nexus 7 Original Development] deadpunk:
This may sound stupid... I have both N4 and N7 2012, with franco.kernel installed on both with FKU (paid version).

There is no headphone boost & amp on the N7(franco.kernel r75) app ?
[Nexus 7 Original Development] nexusmaniac:
Hey! ;) I'm just saying, it's not an enjoyable device to use so I'm just voicing that opinion and asking if there is an even better update in the pipe :) r75 is still much better than any other kernel :)
[Nexus 7 Original Development] The Gingerbread Man:
Basicly that's because tegra platform is locked down pretty tight, down to nvidia not Franco. Its a shame as its a lovely device and out of the box is nice to use but we as consumers buy nexuses as we like to tinker and flash **** and stuff. Other devs offer over clock but that's about all you can do or flash a feature rom. It would be nice for an update to bring some of the stuff Franco has been up to recently on mako to here but I don't think Franco plans on maintaining this device when the n5 is out
[Nexus 7 Original Development] osm0sis:
My fixed version makes it more than usable until Fransisco finds time to show us some love.
[Nexus 7 Original Development] NYLimited:
That is the one from August 25,yes?

---

Any clod can have the facts, but having an opinion is an art.
[Nexus 7 Original Development] osm0sis:
Whichever is on here is the latest:

http://d-h.st/users/osm0sis/jb4_3/grouper/ :good:

Looking like Sept. 7, probably the one where I fixed some potential reboots when using SuperSU. :)
[Nexus 7 Original Development] NYLimited:
I was using one a tad bit older though the same size. Thanks for the effort - will update soon.

I hope Franco will migrate some of the new Mako code like you said he might before he moves on. Some nice things the N4 version now.

---

Any clod can have the facts, but having an opinion is an art.
[Nexus 7 Original Development] osm0sis:
If you're using CWM then it's likely one of these issues:

- SELinux in JB4.3 changes the permissions of su on every boot, so after any boot back to Android you will get a su warning in CWM; it can be ignored.

- If you're using the SuperSU daemonsu then you may want to create /system/etc/.installed_su_daemon to suppress the CWM dialog to disable reflashing stock recovery (the install-recovery.sh it checks for is required to run the root daemon on ROMs without a native service).

Both are harmless and can be ignored if you're using the latest r75-fixed, since SuperSU/Superuser are run as native services from the included ramdisk for JB4.3+. Bottom line: you still have root.
[Nexus 7 Original Development] NYLimited:
Are you using TWRP for recovery? That issue existed in TWRP versions 2.6.x.x - the 2.6.3.0 version corrected it.

---

Any clod can have the facts, but having an opinion is an art.
[Nexus 7 Original Development] Martin-Doc:
The displease of users about Franco not maintaining the device anymore is understandable. Many of us have bought the fKu app, and whilst you shouldn't ask for ETAs at this forum, Franco has made his kernel partially a paid service. People chose him to maintain their device kernel-wise, but without his support, the app is quite useless since r75 suffers many child diseases. Moreover, we cannot even use the app for sucking our d1cks, so yeah, there's that.
[Nexus 7 Original Development] poondog:
No apps are available to suck Dix

However buying a kernel devs app, or most donations in that case should not be buying in hope of more support. I expected the kernel to see less updates with the mako, flo and nexus 5 taking over as more popular

Donations and buying of apps should be for the functionality and as a thanks for what the developer *has* done not to hope for more updates or whatever
[Nexus 7 Original Development] Martin-Doc:
That makes sense. Thank you for this response. I wrote my post with the intention of recieving a response like this, since I have the feeling that many users have the opinion presented in my post, and this discussion will provide a clarification of the current state for many of us.
[Nexus 7 Original Development] fozzie:
No way! I thought I was buying a piece of him. I demand a refund...
[Nexus 7 Original Development] Martin-Doc:
How many percent of his soul do I own by buying the app?
[Nexus 7 Original Development] poondog:
Aha you predicted me? Stop reading my mind

I can't speak for Franco and his dev/tester team though, but that's the mentality of me, most developers who provide apps and teams I'm in

By the look of it mako and flo are stable, tuna is being updated on git with stuff merged from mako so hopefully we're somewhere near the front of the line :P

Although get a flo if you can, its performance is better than Franco on this when its on stock.. I can't imagine what it will be like once I flash Franco kernel on it :D

---------- Post added at 11:38 PM ---------- Previous post was at 11:34 PM ----------

Source?

And what's with the sig pic lolshould I be scared of you?
[Nexus 7 Original Development] poondog:
You link is broken :'(

:D

Ah okay makes sense :)
[Nexus 7 Original Development] jfmcbrayer:
What was the change that fixed some potential reboots with SuperSU? I've been cherry-picking some of Franco's changes into my personal kernel build (not published anywhere yet, probably not interesting enough to publish), and I'm just now seeing those reboots. Do you have a public git repository with your fixes?
[Nexus 7 Original Development] osm0sis:
In init.superuser.rc removed the critical flag from the SuperSU service.
[Nexus 7 Original Development] jfmcbrayer:
Merci Beaucoup.
[Nexus 7 Original Development] nik4energy:
[MENTION=3292224]franciscofranco[/MENTION]

not fair leaving so back this kernel
[Nexus 7 Original Development] osm0sis:
He asked me last week to email him a thorough list and ramdisk fixes like I did for tuna. Doing it in a little while today if I have time, or in the next few days for sure, so expect some movement in the hopefully near future. :good: :D
[Nexus 7 Original Development] The Gingerbread Man:
Perhaps we will get some more of the changes over from mako again. Its looking in real good shape there, same as new n7 is basicly the same as they use same parts etc
[Nexus 7 Original Development] osm0sis:
Yup, I think that's a definite. His exact words were:

:D
[Nexus 7 Original Development] The Gingerbread Man:
I nearly updated to the new n7 earlier, there was a deal trading in your old one and pay £100 for a new 2013 16gb model. I saw it advertised the other day in town and today went back and the deal had expired, was kinda bummed about it. Me and my gf were gonna go in £50 each which for a tab of that quality would have a been a steal! Also wanted it to test some of the dev team stuff on there, I'll wait till the next good deal comes along and try to get in there quicker.
[Nexus 7 Original Development] franciscofranco:
Soon yap ;)
[Nexus 7 Original Development] sotoskawasaki:
Great to see Franco here!!! I really hope his Nexus 7 Kernel gets the magnitude of his Galaxy Nexus Kernel.
[Nexus 7 Original Development] Dragooon123:
Any plans for colour tweaks/Franco app support? Still using your kernels on maguro.
[Nexus 7 Original Development] Jbluna:
Running beautifully so far
[Nexus 7 Original Development] x.Orville.x:
Why no flashable zip thanks
[Nexus 7 Original Development] danielvc:
because you need to learn fastboot and not only install a freaking toolkit for your device.
[Nexus 7 Original Development] demandarin:
Since this build is an early one, OP only wants the more experienced Android users testing/trying it out. The more seasoned Android modders would already know how to flash this through fastboot(needing to be connected to pc to push/flash file to nexus7). Hopefully as later builds come, OP will convert this into a zip which you can flash with TRWP or CWM.

Until then, if you don't know already, I suggesting freshening up your skills on how to flash through fastboot. Plenty of threads and vids(YouTube) on how to do so.
[Nexus 7 Original Development] adfad666:
I just tried it and the kernel builds fine with CyanogenMod. I just had to revert this commit and make a cyanogenmod defconfig (I copied the tegra3_android_defconfig).

As I expected it works fine (at least in the few minutes of play I've given it), the only 'broken' thing I've noticed is that in settings --> about it doesn't display the kernel version.

I'll look for other benefits later, I'm going to relax in the sun for a while :)
[Nexus 7 Original Development] airmaxx23:
I installed the kernel this morning and I now can not boot past the Nexus "X" and/or can not get into recovery (just stays on the Google logo). Suggestions?
[Nexus 7 Original Development] jarjar124:
r u on cm10? if so thats y :)
[Nexus 7 Original Development] airmaxx23:
That should be mentioned in the OP. I just pulled the boot.img from the ROM and flashed it, booting up now. Thanks.
[Nexus 7 Original Development] nobnut:
Press and hold the power and vol down buttons to enter bootloader. From there, you can fastboot flash another boot.img, or enter recovery and restore your original boot.img.
[Nexus 7 Original Development] airmaxx23:
I got it figured out right after I posted this, you replied before I had a chance to edit it, I actually wasn't able to get into recovery. Thanks though.
[Nexus 7 Original Development] Zenoran:
Just curious why you would never include CIFS support? That's one of the coolest things about Android tablets allowing u to share/stream files from a network server to any app.
[Nexus 7 Original Development] x.Orville.x:
I know to do in fastboot;) just aquestion
[Nexus 7 Original Development] lightninbug:
Dropping this here so other users can enjoy better weather icons.. :D

http://xdaforums.com/showthread.php?p=30091580
[Nexus 7 Original Development] jalyn02:
Are we going to get a .zip soon via cwm???
[Nexus 7 Original Development] danielvc:
Fastboot flash boot boot.img
[Nexus 7 Original Development] leelaa:
I hope its next release. I dont have a problem using fastboot. But i aint allways around a computer. Either way if it is or isn't I am just happy i can get franco kernel on my seven :)
[Nexus 7 Original Development] jalyn02:
My point exactly! Like, if I'm out and I want to flash a new kernel and I don't like it or have a change of heart I can just flash back.
[Nexus 7 Original Development] noobandriod:
Does this kernel support USB DAC? Will it ever.
[Nexus 7 Original Development] cwc3:
Was on bricked kernel for a couple days. Not too sure what people are saying about having a smoother feeling, must be placebo. Battery wasn't any better.

r17 is running great so far. Looking forward to 54Mhz option someday :)
[Nexus 7 Original Development] Salv0:
r17 running flawlessly, wifi seems better too.

Anyway I've noticed that in the app ( the paid ) when I use lateral navigation by swyping, the ActionBar's spinner isn't updated with the correct position.

I guess you are using a ViewPager, in that case ( if you want ) you can implements android.support.v4.view.ViewPager.OnPageChangeListener in the main activity and do this:

@Override
public void onPageSelected(int position) {
mActionBar.setSelectedNavigationItem(position);
}
[Nexus 7 Original Development] franciscofranco:
I haven't noticed it until you posted this. It must be because of this screen size because on the GN it shows the tabs name below the action bar and not a spinner like here. I'll test that code, thanks :)
[Nexus 7 Original Development] osm0sis:
Ooh Franco.. that reminds me, I notice on some settings screens in your app landscape works but not others like the main app pages... any way you could see it in your heart to allow landscape mode? :)
[Nexus 7 Original Development] vinny86:
upgrading from r16 to r17 using the free kernel app from you,

Device soft bricked, stuck at the Google screen.
[Nexus 7 Original Development] franciscofranco:
Yeah no problem.

I just tried it and no problems. Must've been a bad download or something, I need to include a MD5 check soon. Hold the power button for a while and it will force reboot and it should boot.
[Nexus 7 Original Development] formicae:
Same issue here. Held down power and it rebooted and got stuck at the Google screen again. Any way out of this?

Edit: Held down vol+power, got into bootloader, flashed manually. Booting fine now.
[Nexus 7 Original Development] myepicyear:
Just to report my experience with 16 to 17 from the updater app, I just did it, and it worked normally. So, it's definitely not everyone.

I did have this happen at one time, however it was many releases ago and it never happened again.

Edit: Oh, and the only way out is to plug into a computer with adb, and choose recovery from the bootloader. You can press all three hardware buttons at once for about 10 seconds to make it restart, then hold power+volume down really fast,(preferably, before you even see the startup Google logo) and that will take you to the bootloader.

Once you're inside the bootloader, plug into the computer that has adb installed, and chose to boot into recovery from the device bootloader.

I'm assuming a certain level of knowledge here, so please don't hesitate to let me know if you need elaboration on any of this. Just don't panic. The device was purposefully designed this way.
[Nexus 7 Original Development] bigeyes0x0:
Last time I tried that code, it was not working saying method setSelectedNavigationItem does not work for spinner type navigation blah blah... (At that time I cursed Romain Guy) It made me wrote my own menu for faster tab navigation in my app. Tell me how it goes for you as I was on an older support library IIRC.
[Nexus 7 Original Development] :
Updated 16--17 fine yesterday..(using paid app) Download did seem to be a little slower than previous releases... I stand next to my router when I update, just makes me feel better..:sly:

//Grouper/Aokp 4/Franco's r17//D2spr/CNA 3.6.6/KT747//
[Nexus 7 Original Development] formicae:
I didn't need to get into recovery. All three hardware buttons, to bootloader, then fastboot flashed r17. Everything went fine after that.
[Nexus 7 Original Development] navlem:
I dun really like the new r17. It keeps making my wifi disconnected and connected randomly.
[Nexus 7 Original Development] franciscofranco:
0 changes on the Wi Fi on r17.
[Nexus 7 Original Development] Salv0:
I can confirm that in my app is working in both landscape and portrait :)
[Nexus 7 Original Development] SquireSCA:
How does one just install the kernel, to something like SmoothROM 3.1? Just flash the file from Recovery like you would a ROM?

Do you have to wipe for a kernel, or just cache and Dalvik?

Never flashed a kernel by itself, I usually use what comes with the ROM...
[Nexus 7 Original Development] ÜBER™:
Its a boot.img and not a flashable. You can either download his free or paid app and it will auto flash it. Or you can download the Boot.img and fastboot flash it.
[Nexus 7 Original Development] Travisdroidx2:
You can not flash a IMG. File in recovery. I recommend using fast boot t flash the kernel however if you have no idea how to do that yet Franco has a free updater app that will install it n the play store. But strongly suggest learning how via fast boot

Fastboot flash boot file name here.img

Ah you beat me Uber :)
[Nexus 7 Original Development] SquireSCA:
Ok, I was confused because the OP says to install from Recovery, but then I saw some people saying what you are saying. I will go get Franco's app from the market and see how that goes.

Thanks!
[Nexus 7 Original Development] Travisdroidx2:
You can install very easy with his free app but you gt even more options when you pay for the paid version. Worth the money and supports Franco's hard work.
[Nexus 7 Original Development] NYLimited:
I am getting amazing battery life and performance from r191 on the N4. If he can bring the original N7 even near that battery life and performance this will be a brand new device! :D

---

Any clod can have the facts, but having an opinion is an art.
[Nexus 7 Original Development] poondog:
Me too! See you around :) it's much better isn't it

I reckon it's the tegra which is the problem
[Nexus 7 Original Development] NYLimited:
Naw, the problem is only Francisco's free time (and desire for sleep occasionally). I am starting to believe he can do *anything* given enough time. ;)

---

Any clod can have the facts, but having an opinion is an art.
[Nexus 7 Original Development] The Gingerbread Man:
Hopefully, just waiting for another good deal to come along at some time, I don't want to get a crap price trading this one in. As far as tegra being the problem its a yes and no answer. Tegra = closed source, Nexus = open source, combined not brilliant. It is a good chip, just not suited to the market of nexus owners who buy and own them to do and flash what they want, entirely different operating systems in some cases! How ever if memory serves correct I think the nexus soc history goes some thing like;

N1- Qualcomm

Nexus S - Exynos

Galaxy Nexus - TI

Nexus 7 2012 - Tegra

Nexus Q (don't know)

Nexus 4 - Qualcomm

Nexus 7 2013 - Qualcomm

Nexus (5?) - Qualcomm

Qualcomm I believe make good documentation of things, not sure about exact drivers but Franco used qualcomms code to make the headphone boost thing on nexus 4 and newer n7 as inrterally they are basicly twins. Exynos is Samsung soc and is almost as closed as tegra. TI were great, they were really open, its a real shame they are pretty much out of the mobile business
[Nexus 7 Original Development] The Gingerbread Man:
Out of the rest they are the most open yeah. I hear you about jbq was sad to see him go, he's now at yahoo and someone else has the job so alls well that ends well
[Nexus 7 Original Development] coohdeh:
maybe can add fastcharge to old nexus 7 tab? :)
[Nexus 7 Original Development] fozzie:
You don't think that if was supported it would already be there?
[Nexus 7 Original Development] NYLimited:
I don't *know* the answer but as best as I recall the Asus / Nexus 7 wall charger puts out about 2000 mA and the device charges quite fast with it - that is it will not decrease the battery level while the the screen is on and charging.

However, the battery level will drop slowly if the screen is on and the device is plugged into a USB car charger, even if the charger can put out the 2000 mA and is using a charge only cable (no data). In this case the Nexus 7 will charge only at 1000 mA (approximate) or roughly half the rate.

Charging at this slower pace suggests that there may be a software issue in the way.

The Nexus7 may well be "cured" by a software solution which would likely be implemented at the kernel level.

*If* the above is correct who would be better than Francisco Franco to come up with some c++ code for this?

---

Any clod can have the facts, but having an opinion is an art.
[Nexus 7 Original Development] fozzie:
It's not a software issue and cannot be fixed in software.
[Nexus 7 Original Development] Martin-Doc:
In that case, can you name the issue and elaborate so we dummies can understand?
[Nexus 7 Original Development] Gspin96:
The wall Charger can put out up to 2 A, although the normal charge rate of our nexus usually is slightly above 1 A. A standard USB port on a PC can safely provide up to 500 mA (which is 0.5 A). Some computers can provide more, but the tab always drains 500 mA to avoid burning the USB controller.
[Nexus 7 Original Development] NYLimited:
Elaborate?

Thanks, that makes sense but there is one small thing that still puzzles me.

How does the N7 know the difference between a 2 A wall charger and a 2 A car charger (not a computer's usb port) and what makes it draw less power?

And, if I look at apps like XPrivacy, Gravitybox and the like, could software not make the 2 A car charger look the same as the wall charger?

---

Any clod can have the facts, but having an opinion is an art.
[Nexus 7 Original Development] fozzie:
It's a moot point and was discussed over a year ago in this thread.

Only dedicated chargers have pins D+ & D- shorted, so a car charger and a computer's USB port look exactly the same, as far as the device is concerned.

http://en.wikipedia.org/wiki/USB#Power might help you out.
[Nexus 7 Original Development] NYLimited:
Naw, learning something new is never a moot point nor is it a waste of time. ;)

Understood. But the cable I use with my 2A car charger has D+ and D- shorted!?

---

Any clod can have the facts, but having an opinion is an art.
[Nexus 7 Original Development] Gspin96:
We can't know how your charger is made:p

But you can, either by opening it (not recommended, and it may be glued so you can't open it without breaking it) and seeing if the two pins in the middle of the USB port are connected between them or by using an ohmmeter: touch each of the 2 pins in the middle of the USB port with one of the nails of the ohmeter, if they're shorted you'll measure a resistance much lower than :silly:
[Nexus 7 Original Development] NYLimited:
I think I wasn't clear before, sorry.

I was saying that my cable DOES have the pins shorted, hence they *are* shorted by the time the device is connected. Also, within / settings / power it indicates (AC), not (USB) while connected to the car charger yet the charge time is drastically different than the wall charger time.
[Nexus 7 Original Development] Gspin96:
Then, probably it's the charger that can't really provide such current, but the limit of my knowledge has been reached here and I can't say more than what I did ;)
[Nexus 7 Original Development] NYLimited:
Actually, that is a good point, thanks! I never actually measured the charger 's output which could claim 2000 mA but not actually provide it. Another idea, another project!

MD Official edit ;)

---

Any clod can have the facts, but having an opinion is an art.
[Nexus 7 Original Development] osm0sis:
A lot of this is covered ad nauseam/in-depth in the All-In-One N7 Charger Issues Thread. It's over in one of the other sub-forums but shouldn't be too hard to find. :)