[KERNEL][GPL][N7]franco.Kernel - r82

[paolocorpo]

Hi guys, for those who want to use FK-R82 with cm-12.1, I've merged cm's ramdisk to franco's ramdisk and I'm using it in my tab, it's working like a charm in last nigthly.

Credits go to Franco, ofc.[emoji1]

Some advises:
- I WILL NOT SUPPORT IT, SO DON'T ASK FOR NOTHING RELATED, NEITHER ME OR FRANCO.
- TESTED WITH TILAPIA SO IT SHOULD WORK WITH GROUPER.

Download:
http://1drv.ms/1Kb71I3

Many thanks
I will try soon and ai will give you my feedback

 

[leechheart]

guys help me please!!
i installed franco kernel with dirty unicorn rom.
the problem is when i am starting my tablet nexus 7 2012 wi fi it appears the system shuts down and i can t do anything only to restart the tablet
the only way to enter in recovery mode is by laptop with nexus root toolkit, when i am trying to enter in recovery mode it is appearing an android with an red angle inside
please help what to do?!!

 

[Spiceworm]

I installed the newest kernel r82 (using the franco updater app) on dirty unicorns (nexus 7 wifi) (DU_grouper_5.1.1_20150813-1329.v9.6-OFFICIAL) , get "Sorry, system ui has stopped" in a loop as well. Using F2FS on data and cache. Reinstalling rom now.

---------- Post added at 12:24 PM ---------- Previous post was at 12:23 PM ----------
@ Leechart above
You'll need reinstall dirty unicorns rom. You can use TWRP to upload the rom image files to the internal storage or use fastboot to install rom.

 

[leechheart]

I have the rom on my de internal storage, but i can t acces it, this is the problem, i can t get into recovery mode because when i m in boot mode when i want to enter in recovery mode it appears an android icon with a red triangle inside

 

[paolocorpo]

guys help me please!!
i installed franco kernel with dirty unicorn rom.
the problem is when i am starting my tablet nexus 7 2012 wi fi it appears the system shuts down and i can t do anything only to restart the tablet
the only way to enter in recovery mode is by laptop with nexus root toolkit, when i am trying to enter in recovery mode it is appearing an android with an red angle inside
please help what to do?!!

I have the rom on my de internal storage, but i can t acces it, this is the problem, i can t get into recovery mode because when i m in boot mode when i want to enter in recovery mode it appears an android icon with a red triangle inside

Ciao
it seems that you have teh recovery stock (android with an red angle inside)
When you are in this situation push VOL UP, after PWR and after UNPUSH only VOL UP
In this way you can achieve the menu of recovery stock
I think that you can initially try doing a factory reset or a simple dirty wipe ...

Or you can surely flash a stock factory

 

[leechheart]

I ve done it thanks guys you are the best

 

[paolocorpo]

I ve done it thanks guys you are the best

Very good
I am happy for you
Ciao

 

[doublin]

I'm running SlimKat 4.4.4, could someone please tell me which kernel version can I install?
Is it r80 from 2014-07-18?

 

[NYLimited]

I'm running SlimKat 4.4.4, could someone please tell me which kernel version can I install?
Is it r80 from 2014-07-18?

I don't know anything about compatibility with Slim at but versions above 80 should be used with Android 5.x

r80 was the last 4.x version.


----
You can chose to ignore reality, but you cannot ignore the consequences of ignoring reality.

 

[shawnbrennan55]

I'm running SlimKat 4.4.4, could someone please tell me which kernel version can I install?
Is it r80 from 2014-07-18?

I can confirm that r80 works great with SlimKat 4.4.4

 

[doublin]

I can confirm that r80 works great with SlimKat 4.4.4

Thank you.

EDIT: Ok, I've just flashed the r80 zip, everything went well.

 

[Thexfactor2011]

I'm guessing this thread is dead, but I figured I post to see if anyone has found a fix or had any luck,
Grouper running CM 12.1 Dec 16, 2015 build
Flashed version r82 and I get a bootloop

This is just repeated over and over again. Any Thoughts?

<7>[  202.773781] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
<4>[  203.352738] stop_machine_cpu_stop smp=2
<4>[  203.352747] stop_machine_cpu_stop smp=3
<4>[  203.352754] stop_machine_cpu_stop smp=0
<4>[  203.352761] stop_machine_cpu_stop smp=1
<4>[  203.355236] stop_machine_cpu_stop smp=0
<4>[  203.355245] stop_machine_cpu_stop smp=1
<4>[  203.355252] stop_machine_cpu_stop smp=2
<6>[  203.692117] Switched to NOHz mode on CPU #2
<6>[  203.692125] Switched to NOHz mode on CPU #3
<4>[  204.483101] stop_machine_cpu_stop smp=1
<4>[  204.483119] stop_machine_cpu_stop smp=2
<4>[  204.483136] stop_machine_cpu_stop smp=3
<4>[  204.483151] stop_machine_cpu_stop smp=0
<4>[  204.487412] stop_machine_cpu_stop smp=0
<4>[  204.487430] stop_machine_cpu_stop smp=1
<4>[  204.487446] stop_machine_cpu_stop smp=2
<6>[  205.051799] iio-buffer, current state requested again
<6>[  205.063282] iio-buffer, current state requested again
<6>[  205.065207] iio-buffer, current state requested again
<6>[  205.065562] iio-buffer, current state requested again
<6>[  205.243162] request_suspend_state: wakeup (0->0) at 205251084002 (2015-12-17 16:49:04.603691001 UTC)
<6>[  205.477912] nvavp nvavp: using SMMU at ff00000 to load AVP kernel
<6>[  205.478118] nvavp nvavp: AVP os at vaddr=d8e00000 paddr=ff00000 reset_addr=0ff00094
<6>[  205.489003] widget AIF3RX AIF3 Playback
<6>[  205.489085] widget AIF3TX AIF3 Capture
<5>[  211.192806] bq27541_get_psp status: Charging ret= 0x0101
<5>[  211.193453] bq27541_get_psp voltage_now= 3779000 uV
<5>[  211.194133] bq27541_get_capacity = 56% ret= 59
<5>[  211.194775] bq27541_get_psp temperature= 280 (0.1óXC)
<5>[  211.195734] bq27541_get_capacity = 56% ret= 59
<5>[  211.196478] bq27541_get_psp voltage_now= 3779000 uV
<5>[  211.197165] bq27541_get_psp temperature= 280 (0.1óXC)
<5>[  211.197903] bq27541_get_psp status: Charging ret= 0x0101
<4>[  211.198244] healthd: battery l=56 v=3779 t=28.0 h=2 st=2 chg=u
<6>[  213.740518] binder: 130:352 transaction failed 29189, size 68-0
<6>[  213.845763] request_suspend_state: wakeup (0->0) at 213853597002 (2015-12-17 16:49:13.206193001 UTC)
<6>[  214.142184] Switched to NOHz mode on CPU #2
<6>[  214.142200] Switched to NOHz mode on CPU #3
<7>[  214.388332] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
<4>[  215.632945] stop_machine_cpu_stop smp=0
<4>[  215.632958] stop_machine_cpu_stop smp=1
<4>[  215.632969] stop_machine_cpu_stop smp=2
<4>[  215.632979] stop_machine_cpu_stop smp=3
<4>[  215.645815] stop_machine_cpu_stop smp=0
<4>[  215.645901] stop_machine_cpu_stop smp=1
<4>[  215.645975] stop_machine_cpu_stop smp=2
<6>[  216.789188] iio-buffer, current state requested again
<6>[  216.796514] iio-buffer, current state requested again
<6>[  216.797854] iio-buffer, current state requested again
<6>[  216.798123] iio-buffer, current state requested again
<6>[  216.929863] request_suspend_state: wakeup (0->0) at 216937788002 (2015-12-17 16:49:16.290395001 UTC)
<6>[  217.216585] nvavp nvavp: using SMMU at ff00000 to load AVP kernel
<6>[  217.217702] nvavp nvavp: AVP os at vaddr=d8e00000 paddr=ff00000 reset_addr=0ff00094
<6>[  217.232412] widget AIF3RX AIF3 Playback
<6>[  217.233170] widget AIF3TX AIF3 Capture
<6>[  226.036781] request_suspend_state: wakeup (0->0) at 226044597002 (2015-12-17 16:49:25.397189001 UTC)
<6>[  226.060199] binder: 130:352 transaction failed 29189, size 68-0
<6>[  226.292139] Switched to NOHz mode on CPU #2
<6>[  226.292158] Switched to NOHz mode on CPU #3
<7>[  226.597162] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
<4>[  227.883000] stop_machine_cpu_stop smp=0
<4>[  227.883020] stop_machine_cpu_stop smp=1
<4>[  227.883037] stop_machine_cpu_stop smp=2
<4>[  227.883054] stop_machine_cpu_stop smp=3
<4>[  227.887223] stop_machine_cpu_stop smp=0
<4>[  227.887241] stop_machine_cpu_stop smp=1
<4>[  227.887258] stop_machine_cpu_stop smp=2
<6>[  229.049416] iio-buffer, current state requested again
<6>[  229.060955] iio-buffer, current state requested again
<6>[  229.063245] iio-buffer, current state requested again
<6>[  229.063647] iio-buffer, current state requested again

Thanks for reading!

 

[fran_xda]

I'm guessing this thread is dead, but I figured I post to see if anyone has found a fix or had any luck,
Grouper running CM 12.1 Dec 16, 2015 build
Flashed version r82 and I get a bootloop

This is just repeated over and over again. Any Thoughts?

It doesn't work for CyanogenMod.

 

[Angristan]

It doesn't work for CyanogenMod.

Is there any version for CM ?

 

[fran_xda]

Is there any version for CM ?

I don't think so for Cm12.

 

[Angristan]

I don't think so for Cm12.

Only for stock ?

 

[Angristan]

By the way, what are the features of this kernel ?

 

[Glock3am]

By the way, what are the features of this kernel ?

Have you looked at this?

http://forum.xda-developers.com/showthread.php?t=2532422 (FAQ link from the OP.)

 

[nanezzu]

Hi guys i use the c ROM with android KK 4.4! And the kernel stock of this ROM is very good...did you think i van improve the battery life AnD speed with franco on this ROM? Thanks for all the answers

 

[arman-teta]

How can i use multirom whit this kernel ?
I cant acses my secendery rom.:crying::crying: