yashsingh1/xdaforums huggingface dataset:
[Nexus 10 Original Android Development] 3DSammy:
[SOLVED] r16 and init.d

UPDATE: I got init.d working by installing Universal Init.d but am a little surprised I needed to use an app, especially as it worked with the stock kernel. Alls good in the end.

I search this thread for anything on init.d and only saw the references to "/sbin/fkbootscript.sh". I saw how that if necessary that script creates and sets permissions for the "/system/etc/init.d" subdirectory. But does not actually execute any scripts in "/system/etc/init.d" at boot time. I'm expecting that "/system/etc/install-recovery.sh" is executed during boot time.

Here is what I found.

Was running rooted (SuperSu 1.93) 442 stock with init.d functioning

Bought and installed Franco Updater

Backed up the stock image using Franco Updater (thank goodness saved some time)

Installed r16 using Franco Updater

init.d scripts no longer executed at boot time

Tried running /system/etc/install-recover.sh in a root termial session and all init.d scripts ran properly

Restored stock kernel using Franco Updater

Now init.d works again

Restored r16 and init.d no longer works

I only used "/system/etc/install-recovery.sh" as that was in the init.d how-to docs I read somewhere on the interwebs. I hesitate to change "/sbin/fkbootscript.sh" and cannot find any settings in Franco Updater for init.d either.

Any suggestions would be appeciated.
[Nexus 10 Original Android Development] bonedriven:
Does anything not working for you?

No offense but I don't understand why people just want "updates" instead of just quality.

If it works perfectly, next update would probably only **** it up.
[Nexus 10 Original Android Development] jodvova:
Franko kernel is not about "anything not working for you". Everything worked fine for me with a stock kernel but I still installed franko one.

I want a better performance, more smooth screens transition and so on.
[Nexus 10 Original Android Development] dodo99x:
Improvements made to other device kernels often trickle down to the N10 once the bugs are worked out.
[Nexus 10 Original Android Development] spinik:
I have a problem with Franco. Kernel I can't seem To connect with miracast, on stock kernel no problem
[Nexus 10 Original Android Development] _chanstar_:
I had that problem with r14 and r15. It works for me on r16 and PTV3000. The same as the stock kernel, I had to keep trying to connect around 1-6x. You'll just have to keep retrying and maybe even bring the tablet closer to the receiver when connecting.

Sent from my Nexus 5
[Nexus 10 Original Android Development] The Gingerbread Man:
**Copy paste post over all current Franco kernel device threads**

I'm trying to list all compatible roms that work with Franco kernel in my Franco Kernel and FKU Learner lounge thread http://xdaforums.com/showthread.php?t=2532422 . If you are using a custom rom with Franco kernel can you report which device your running and the name of your rom? I am keeping a list for each device for reference.

Please post in my thread http://xdaforums.com/showthread.php?t=2532422 don't fill Franco's threads with the answers. I don't own all devices so can't do this single handedly, your help as a community will be greatly appreciated. Thanks for your time!
[Nexus 10 Original Android Development] wwwpuntoit:
Any more "love" for manta??
[Nexus 10 Original Android Development] The Gingerbread Man:
Does anyone want any information added to my learner lounge thread from this thread? I never owned this device and don't have time to read all your thread. Please post http://xdaforums.com/showthread.php?t=2532422 if anyone has something. I'm lacking any decent information for nexus 4 and 10.
[Nexus 10 Original Android Development] jodvova:
This kernel doesn't work with latest CM11 nightlies. Will this ever be fixed ?
[Nexus 10 Original Android Development] The Gingerbread Man:
No, its because the Caf display drivers CM use that it won't work. This is for stock / aosp. Complain to CM devs about it
[Nexus 10 Original Android Development] 3DSammy:
This is not a "fix" situation as CM11 uses caf and Franco is not fully supporting caf (CAF is a*custom Linux kernel branch*in place to support Qualcomm hardware). Some caf patches are included in his Kernel but not so that all custom ROMs are compatible. CM11 is the prominent one that is impacted. I read this in the Nexus 5 Franco kernel XDA thread. A very active email thread I may add. From what I read this will not change in the foreseeable future.

There maybe some good news as Franco commented on that he was looking to release updates in the near future for his other supported devices when asked by a Nexus 7 owner. I'm hoping that will include the Nexus 10.

---------- Post added at 08:43 AM ---------- Previous post was at 08:41 AM ----------

Looks like I can't type fast enough ;)
[Nexus 10 Original Android Development] go4saket:
Youtube Problem

Hello! I am on pure Kitkat 4.4.2 with franco.kernel and have installed some mods via Xposed Installer. Problem is that my Youtube app doesnt work. Everytime I try to start Youtube app, it gives me an error "Unfortunately, Youtube has stopped". This is exactly the same problem I am facing in my Nexus 5 with the same ver of Kitkat and Franco Kernel and mods. I have tried uninstalling Youtube via Titanium Backup and reinstalling a fresh copy from Play but the problem is still there.

Now is this a problem with the Kernel or have I messed up something else. Please help.
[Nexus 10 Original Android Development] Holer Togni:
Try these two combinations:

Franco kernel with Xposed disabled

Stock kernel with Xposed enabled

to see if the kernel actually has something to do with problem.
[Nexus 10 Original Android Development] jesus_c:
Update or disable YouTube adaway in xposed modules

Отправлено с моего GT-N7100 через Tapatalk
[Nexus 10 Original Android Development] JNewms:
That's user space, not kernel. It's most likely caused from xposed.
[Nexus 10 Original Android Development] jodvova:
A bit unrelated question, can I flash stock over CM 11 ? Will it work or do I need to do a wipe first ?
[Nexus 10 Original Android Development] pkelly517:
Uhm, wipe, and flash stock.

Best of luck. Flashing nexus images is probably your best bet on the CM-> Stock path.
[Nexus 10 Original Android Development] franciscofranco:
Pushed r17:

* Merged a couple patches to park kthreads on several key subsystems

* Merged my generic touch boost driver instead of relying on the glued boostpulse solution

* Made the lowest backlight brightness step as low as possible because the default is too bright on low ambient light. The default is 2, which is the minimum before the display turns totally black, but it is user ajustable /sys/module/pwm_bl/parameters/min_brightness

* Merged other misc patches

Enjoy.
[Nexus 10 Original Android Development] e753:
Thank you man!!!!

Does it work with the new versions of CM?

abrazo
[Nexus 10 Original Android Development] ricco333:
It should, since he just pushed the update.

Erik
[Nexus 10 Original Android Development] franciscofranco:
Why shouldn't it? I don't use CM but I don't see any reason not to work.
[Nexus 10 Original Android Development] polluzet:
Did you ever read OP, the first post ?

Franco wrote there :

" Just for general awareness this is compatible with CyanogenMod based roms".

Please read carefully and switch on your brain, if You are flashing ROMs and kernels and the whole stuff here [emoji6][emoji1]

Gesendet von meinem GT-9001 mit KitKat
[Nexus 10 Original Android Development] Beaster:
Thx for the update Franco.

I am seeing some strange behavior with auto brightness.. I think the brightness is way too low than before.

And sometimes the brightness will go up and down again without moving the tablet.

Any ideas?

Thank you very much!
[Nexus 10 Original Android Development] jodvova:
This kernel and its recent versions don't work with CM.

Upon boot you get an error message with phone something failed which impossible to get rid of.
[Nexus 10 Original Android Development] SpudsterZ:
R17 kernel working on SlimRom Manta 3.9.
[Nexus 10 Original Android Development] dowenprs:
Not true, I am on the current CM11 nightly, and r17 is working perfectly fine.

Dan
[Nexus 10 Original Android Development] SpudsterZ:
Same here. Nothing tragic, but it's certainly out of whack.
[Nexus 10 Original Android Development] jodvova:
Did you do a wipe when you installed the kernel or CM11 nightly ?

I've been always installing CM11 nightlies on top of each other. I'm on 23/03/14 nightly and tried to flash r17 yesterday. Upon boot I get an error message that android...phone failed to do something and needs to be close with an OK button. This message never disappears but just sits in the center of the screen no matter how many times I pressed ok.

I haven't tried a wipe though.

---------- Post added at 10:07 AM ---------- Previous post was at 09:51 AM ----------

I just did wipe data, installed CM11 23/03 nightly and r17 on top of it.

Upon boot an error message that com.android.phone failed that cannot be taken off the screen.

It doesn't work.
[Nexus 10 Original Android Development] 3DSammy:
I also noticed the dimmer than before display after installing r17. I had altered my brightness settings with Xposed's Gravity box module and r17 seems to change that even though there is no indication in Gravity box itself. I also own a Nexus 5 and use Franco kernel, with that device's r37 kernel. Franco added his own auto brightness settings which are dimmer than stock. His FKU app includes a setting to turn the new option off, unfortunately I cannot find that FKU option on the Nexus 10. Both devices are using the same FKU version.

In the Nexus 5 forum there was a method to turn Franco's auto brightness feature off through an echo command but that also will not work as the Nexus 10 seems to use a different file for that option.

I'm sure this will be sorted out soon.
[Nexus 10 Original Android Development] Beaster:
Thx for the replies. Lets hope it gets a fix soon!
[Nexus 10 Original Android Development] _chanstar_:
Min CPU Freq doesn't stick and defaults to whatever the input_boost_freq is when changing the Min CPU Freq value and navigating out and back in to CPU Manager.

I also noticed the only frequencies being used and shown in a CPU Monitoring app (BBS) are the Max and Min CPU Freq.

Can someone else confirm?

Sent from my Nexus 5
[Nexus 10 Original Android Development] Estel37:
I can confirm this, i tried to modify the frequencies with both the performance settings menu in omnirom and trickster mod.

However on my device all the frequencies between the min and the max are used.
[Nexus 10 Original Android Development] andynx1:
Hi,

My nexus 10 is rooted, 100% stock 4.4.2, stock kernel, with Xposed. I have various modules, gravitybox, YouTube adaway, etc.

Absolutely no problems with YouTube.

I have Franco Kernel on my nexus 4 with Xposed, no problems with YouTube there either...
[Nexus 10 Original Android Development] jprakes:
Min CPR doesn't stick for me either
[Nexus 10 Original Android Development] FredC94:
Same issue here under CM11 and franco kernel r17 com.android.phone has stopped or something like that, when you select "ok" the popup windows comes over and over.
[Nexus 10 Original Android Development] e753:
same here...

:(
[Nexus 10 Original Android Development] jodvova:
Yeap. I went back to a stock firmware.

To my taste, I prefer a speed up that this kernel gives over CM11 features.
[Nexus 10 Original Android Development] UK_Wildcats_Fans:
I am using the latest AOKP Manta nightly with Franco r17 without any issues.
[Nexus 10 Original Android Development] ChemicalSymphony:
This kernel screams with Scanno's Homebuilt OmniROM. Thanks for keeping it up to date Franco.
[Nexus 10 Original Android Development] 3DSammy:
As some people have commented the Franco r17 manta release has changed the auto dimming to very low values. Too low for a number of people. Here's an additional observation I recently stumbled across.

I had already purchased Lux for a different device so installed it on my Nexus 10 in an attempt to work around the r17 dimness in low light conditions. It worked to a degree but when the lux value went from 5 to 4 the dimness dropped way too much. It was not smooth at all. I tried playing around with the Lux profiles but nothing seemed to work. I started to just live with it.

For a totally unrelated reason (tacking down a video playback glitch) I returned to a stock kernel and did a factory reset. As I was re-installing my apps including Lux I noticed that the lux level 4/5 issue had disappeared. There was no abrupt brightness transition, it was very smooth.

After resolving the issue which forced the factory reset. I decided to re-install the Franco r17 kernel. As you have likely surmised the lux level 4/5 issue returned. As I had taken a FKU backup of the stock kernel I restored it. Bad news the lux level 4/5 issue was not corrected. Thankfully I had taken a nandroid backup just before applying the Franco r17 kernel. That fixed the dimming issues.

So even though I would love to use the Franco r17 kernel on my Nexus 10 I will not until the issue is fixed. At this point I consider the abrupt change in brightness to be a bug. I've purchased the FKU app and am part of Franco's beta program. The latest FKU app for the Nexus 10 does not have any options to set lowest dim level threshold or disable the autobrightness enhancements which the Nexus 5 FKU app includes.

I will gladly test any new Nexus 10 kernel builds, to try to help out.
[Nexus 10 Original Android Development] Khaon:
I think [MENTION=3292224]franciscofranco[/MENTION] has just to update the ramdisk to make its kernel compatible with cm11. ( not sure tho)
[Nexus 10 Original Android Development] Ted C.:
Auto dimming....

My initial reaction to the latest release was that the lowest screen setting was too dim. I've since become accustomed to and appreciative of this setting.... :good:
[Nexus 10 Original Android Development] e753:
so eventually it doesn't work with CM11. It should be written at least in the 1st page
[Nexus 10 Original Android Development] pkelly517:
True enough.

Any thread that has the info in the OP should keep it up to date.

It's not so effective to tell a user to read the OP when it doesn't have the latest answer.

That said, I bet it will come. Hammerhead is currently fighting a couple of issues. Or maybe when 4.4.3 comes out...
[Nexus 10 Original Android Development] Aleq:
I have strong feeling that with this Kernel, Dungeon Keeper makes the device very hot (hotter than with stock kernel) and thermal throttling kicks in (underclocks the cpu/graphics periodically)
[Nexus 10 Original Android Development] michaelearth:
This is probably a stupid question but how do you enable overclocking while using this kernel? I just flashed it and installed setcpu but it doesn't let me go above stock frequencies. Plus the rom i'm on doesn't have performance settings either.

Also can you over clock the ram with this kernel? If you can, how?

Thank you
[Nexus 10 Original Android Development] patsmike:
Confirmed also happening here - I'm running Omni. Are you also running Omnirom? The guy below you who had the same problem is also Omni, maybe isolated to just 1 ROM?
[Nexus 10 Original Android Development] blipp:
You cant overclock on Francos kernels, he just doesn't do it because it usually just causes more problems. The only time he does it is if a chip is for some reason underclocked by the OEM, but even then it's only to the actual stock max of the chip.
[Nexus 10 Original Android Development] Estel37:
I tried the kernel on purity and rastakat and I didn't have any problem, so it's probably caused by the rom.
[Nexus 10 Original Android Development] _chanstar_:
I'm running stock ROM with Xposed (GB + BBS).

Good to know about the issue not happening with those ROMs.

Sent from my Nexus 5
[Nexus 10 Original Android Development] alcurtis93:
Has anyone compiled Franco r17 with overclocking abilities? Don't actually have my nexus 10 yet should be getting it this week or next but heard it needs it at times.
[Nexus 10 Original Android Development] beekay201:
#offtopic

I also own a N5.. Which is running Franco's r47...

There's OC steps up to 3GHz... And I'm pretty sure that 3GHz isn't the "actual stock max of the chip".

Franco simply doesn't feel the need to have the CPU OC/UV implementation on N10.

a hammerhead wrote this.
[Nexus 10 Original Android Development] alcurtis93:
Get yourself on r48
[Nexus 10 Original Android Development] kaivalya97:
I cannot change my min. CPU frequency from 1300 MHz. Anyone else have the same problem?
[Nexus 10 Original Android Development] CWalkop:
Yep, just noticed the exact same thing. Trickster doesn't work, either.

Edit: rebooting the tablet solved the issue.
[Nexus 10 Original Android Development] kaivalya97:
That did it! I didn't try turning it off and on again :P
[Nexus 10 Original Android Development] CWalkop:
It's odd; after some uptime the kernel seems to get locked to 1300MHz minimum.A reboot fixes the issue, but it's strange nonetheless. Running yesterday's version of OmniRom.

Edit: happens on today's revision, even after a kernel reflash, if that means anything. ?
[Nexus 10 Original Android Development] CWalkop:
~Deleted~
[Nexus 10 Original Android Development] _chanstar_:
Hmmmmm I never tried a reboot to see if it solves the min CPU issue.

Anyone here use a Netgear PTV3000 for miracast? Doesn't seem to connect with Franco after their latest firmware update but works with stock kernel and Trinity.

Sent from my Nexus 5
[Nexus 10 Original Android Development] alcurtis93:
Has development died here?
[Nexus 10 Original Android Development] Langduscher:
No, but the N10 is last on the list of supported devices.

Anyway, Francisco is off to Silicon Valley & 4.4.3 has just been released so we'll have to hang in there.

Kernel is great as it is anyway (I'm still on r14 because that kernle gives me best battery life).
[Nexus 10 Original Android Development] CWalkop:
4.4.3 is out??? Why did I not see this? ?
[Nexus 10 Original Android Development] blipp:
T-Mobile posted a tiny changelog saying that 4.4.3 for the N4, N5 and 2013 N7 would start going out today. I dont think anyone's actually gotten it yet, it was probably just a date google gave them as the earliest the update would go out.

Edit: hah. Minutes after posting, Google has put up the 4.4.3 factory images, so ignore what I said.
[Nexus 10 Original Android Development] nigelhealy:
https://developers.google.com/android/nexus/images#mantarayktu84l
[Nexus 10 Original Android Development] jodvova:
If I flash OTA 4.4.3 will it override franco kernel ?
[Nexus 10 Original Android Development] Izeltokatl:
Yes, always.
[Nexus 10 Original Android Development] nigelhealy:
Yes.

However typically OTA automatically flashed will fail as you have system files changed.

I always just do a full fresh install and then manually install my apps from Play then configure them. It leads to a greenfield as much mainstream solution as possible which helps avoid the bugs from uniqueness. e.g. you get a future issue which none with 4.4.3+Franco have..because you upgraded in a unique way.
[Nexus 10 Original Android Development] usafle:
I'm going to take your advice and "downgrade " to that version. On my Nexus5, this kernel is great...on my N10.... I can actually watch the battery drop as soon as I turn it on. Dissatisfied to say the least.

Ill try the R14 before I try KTManta or some other Kernel.
[Nexus 10 Original Android Development] Holer Togni:
My sweet spot is r16. Lowest brightness on r17 is just to dark on my device plus it seems to consume more battery (getting about 30 mins less SOT on average)
[Nexus 10 Original Android Development] usafle:
Wow. What a difference switching to R14. Its definitely not a placebo effect!!! Thanks for the suggestion.
[Nexus 10 Original Android Development] zoltrix:
is there anyway to just restore the stock kernel ?
[Nexus 10 Original Android Development] nigelhealy:
By backing up stock before you apply like I did.....
[Nexus 10 Original Android Development] blipp:
If you didn't back it up before you flashed FK, you can go to the Google website and download the stock system image. Go into the zip and there's a boot.img that's the stock kernel that you can take out of the zip and flash. Just make sure it's the right android version.
[Nexus 10 Original Android Development] Holer Togni:
Did the rounds of Manta kernels after upgrading to 4.4.3 and I gotta say: this one is still the best (for me). The ui is so much more fluid with this kernel and also the raw performance is just awesome (just scored 23447 in Antutu, settings 1700 MHz main/max, everything else stock). Thanks a lot!

(Purity 6/8 KTU84M 4.4.3, Z2 bionic, FK r17)
[Nexus 10 Original Android Development] usafle:
My main concern is extended battery life then raw performance. I'm glad I did the "downgrade " to R14. I've got my CPU Max at 1100mhz. I just wish we could undervolt like I can on my N5
[Nexus 10 Original Android Development] JNewms:
UV wouldn't extend battery life any way.
[Nexus 10 Original Android Development] usafle:
Why is that?

The other kernels support UV. Must be there for a reason? Just curious....
[Nexus 10 Original Android Development] JNewms:
UV is for lowering heat. It doesn't really do anything for battery life
[Nexus 10 Original Android Development] Reiven89:
Nexus 10 is often warm in the back near the camera, i tried 2 nexus 10 so i guess its not hw problem. I think its the processor heating that side ? Well then the uv might be useful since its going to be less hot
[Nexus 10 Original Android Development] blipp:
Hey [MENTION=3292224]franciscofranco[/MENTION], I was wondering if you could post your Nexus 10 Per-App Modes for us. I saw on your G+ the other month when you posted a few of your modes you said you had a specific Nexus 10 mode and was just wondering what was different. I applied what I could from them, but I couldn't find paths for the GPU stuff, if that stuff is even tuneable for us. I searched for a while and couldn't find anything about gpu paths for the exynos chip. Maybe we just can't change that stuff, be regardless I was just wondering. Thanks! :good:
[Nexus 10 Original Android Development] emd2009:
Any update?
[Nexus 10 Original Android Development] alcurtis93:
Nexus 10 development seems dead. We had a good run ;) thanks for all your hard work though Franco
[Nexus 10 Original Android Development] blipp:
What? Franco has been working on FacesIn a lot recently, and besides a few little improvements, most of the devices haven't been updated a lot recently. And I/O just happened. Updates will come when he thinks there's something to add that will improve it. If it's "dead" that's because there's really nothing needed. The N10 was always a device he wanted to use first and a development device second anyway.
[Nexus 10 Original Android Development] nick w:
Any chance of a .zip file. Im at work and cant fastboot images!

Thanks

N
[Nexus 10 Original Android Development] Endless7:
If you compare to other gov, you will find there is some slight but obvious frame dropping.Some guys reported the same problem too in KT's thread. Anyway,it's not a big problem because video can still be watched.

---------- Post added at 06:20 PM ---------- Previous post was at 06:18 PM ----------

All IO schedulers are row+noop+deadline. And default is row.
[Nexus 10 Original Android Development] SpecRek9:
R2 is already great, I've gamming nova 3 for an hour last night and the device barely got warm with no lags whatsoever.
[Nexus 10 Original Android Development] dowenprs:
R2 has been fantastic for me, the only issue I've ran into is a couple of random reboots. Not sure if that is kernel related or rom related, really wish someone could stomp out these random reboots.

Thanks for the kernel, love your work!

Peace

Dan
[Nexus 10 Original Android Development] SpecRek9:
I had those in the past when using stock kernel, AFAIK that is a bug related to 4.2.1