[KERNEL][3.0.101][JB][PMEM] K^Kernel 3.0.101 v3.1 for JB 4.2.2 and JB 4.1.2 [EOL]

[mhbraun]

i would advice you to make a backup all of you content and format internal and external sd

1. Backup with Titanium Backup of the System
2. Format internal SD (factory reset)
3. Format external SD (this is where my backups are stored, hence I need to move the data to my pc before)
4. Flash Rom r6 + KK 2.8 + Gapps
5. Reboot
6. Repopulate external SD card from pc
7. Restore of all apps with Titanium Backup
8. Reboot

Is this what you are talking about?
What would make the difference to the actual process?

 

[sv2hqx]

Yes but try this before install you apps
First of all to resolve fc
On step at the time

1. Backup with Titanium Backup of the System
2. Format internal SD (factory reset)
3. Format external SD (this is where my backups are stored, hence I need to move the data to my pc before)
4. Flash Rom r6 + KK 2.8 + Gapps
5. Reboot
6. Repopulate external SD card from pc
7. Restore of all apps with Titanium Backup
8. Reboot

Is this what you are talking about?
What would make the difference to the actual process?

 

[mhbraun]

Yes but try this before install you apps
First of all to resolve fc
On step at the time

That's what I intended to say with 5. Sorry for being not accurate.

Found some more glitches in r6 kk2.1 now.

Folder sync has no access anymore to my cloud as it forgets the password.
Amazon store produces FC

I am back @r5 kk2.7 and will give r6 a fresh install hopefully tomorrow evening.
Thanks for the hint.

Sent by i9001 0x07 board running CM10.1rc5 ADC on K^Kernel2.7exUV370MB with i9001XXKPO baseband

 

[XeLLaR*]

That's what I intended to say with 5. Sorry for being not accurate.

Found some more glitches in r6 kk2.1 now.

Folder sync has no access anymore to my cloud as it forgets the password.
Amazon store produces FC

I am back @r5 kk2.7 and will give r6 a fresh install hopefully tomorrow evening.
Thanks for the hint.

Sent by i9001 0x07 board running CM10.1rc5 ADC on K^Kernel2.7exUV370MB with i9001XXKPO baseband

Ok, heres your way to a logcat(Requires working adb setup on pc):

1.Restore your working backup
2.Enable USB Debugging
3.Flash R6
4.Use adb to get the logcat/dmesg after you see the FC message popping up.

(Use these commands)
"adb logcat > /sdcard/logcat.txt"
"adb dmesg > /sdcard/dmesg.txt"

Without the ["].

Gz
X

Sent from my Nexus 4 using Tapatalk 4

 

[mhbraun]

Folder sync has no access anymore to my cloud as it forgets the password.
Amazon store produces FC

I am back @r5 kk2.7 and will give r6 a fresh install hopefully tomorrow evening

Tried to avoid a fresh install, as the i9001 is my productive system and I hesitate to reinstall all the configuration.

Flashed r7 + kk2.8 with the wipes on r5 kk2.7. Instead. Had the same problems.

Restored r5 and flashed r7+kk2.2. Works like a charm.


I guess I need to abandon the 3.0.x Kernel and live with the higher battery drain.


Sent by i9001 0x07 board running CM10.1rc5 ADC on K^Kernel2.7exUV370MB with i9001XXKPO baseband

 

[Christopher83]

K^Kernel 3.0.99 v2.9 for JB 4.1.2 and JB 4.2.2

Hi guys,
I released the new v2.9 builds of the kernel:

- Kernel 3.0.99
- Sources synched with jb-3.0 repo of Arco68 and ADC Team for JB-4.1.2 (CM 10) kernel builds
- Sources synched with cm-10.1_3.0 repo of Arco68 and ADC Team for JB 4.2.2 (CM 10.1) kernel builds
- Built with my latest custom Linaro 4.7.4-2013.09 toolchain optimized for Cortex-A8
- New bootsplash logo
- mm: remove compressed copy from zram in-memory (credits to Minchan Kim)
- lib/lzo: Rename lzo1x_decompress.c to lzo1x_decompress_safe.c (credits to Markus F.X.J. Oberhumer)
- lib/lzo: Update LZO compression to current upstream version (credits to Markus F.X.J. Oberhumer)
- lib/lzo: huge LZO decompression speedup on ARM by using unaligned access (credits to Markus F.X.J. Oberhumer)
- ARM: 7668/1: fix memset-related crashes caused by recent GCC (4.7.2) optimizations (credits to Ivan Djelic)
- ARM: 7670/1: fix the memset fix (credits to Nicolas Pitre)
- msm: vidc: return error in case of init failure (credits to Pushkaraj Patil)
- Switched to SIO I/O scheduler
- Fixed change conflicts between custom settings and init.d settings during boot
- Possibility to disable the redirection to frandom number generator

Additional commits for CM 10 only
- Revert "video: msm: Fix LCD enable sequence for ancora lcd rev.3" (credits to Arco68)
- msm: display: Prevent fb suspend in charging mode for all (credits to Arco68)

Have a nice day!

 

[Mudu kai]

Thanks again, SIR... for most battery efficient kernel (3.0.X) for JB...
kernel version reached 3.0.99...
I wonder what the next version would be named...
"3.1.X" ??

 

[Christopher83]

Thanks again, SIR... for most battery efficient kernel (3.0.X) for JB...
kernel version reached 3.0.99...
I wonder what the next version would be named...
"3.1.X" ??

Thank you too,
no, it will be simply 3.0.100...

 

[Mairo]

Hi, I use latest K Kernel and ehndroix II 4.1.2 rom. Can someone explain something, after unistalling game ( glash of clan - just triaed this ) I did restart and after that all my Widgets disappeared and I see left bottom corner " safe mode " , Why so?

After new reboot no " safe mode" text , but still no widgets. just must add them manually.

 

[alireza7991]

Please turn fsync off in your kernel by default ! Fsync f**cked alot of my really important files . SAVING USERS FILES IS'NT MORE IMPORTANT THAN PERFORMANCE ??

 

[Christopher83]

Please turn fsync off in your kernel by default ! Fsync f**cked alot of my really important files . SAVING USERS FILES IS'NT MORE IMPORTANT THAN PERFORMANCE ??

Hi Alireza,
please describe me what you were doing and what happened before you found your files corrupted...

Sent from my GT-I9001 with Tapatalk 4

 

[alireza7991]

Hi Alireza,
please describe me what you were doing and what happened before you found your files corrupted...

Sent from my GT-I9001 with Tapatalk 4

1- Going to /data/..../xzy.n
2- Changing lots of parts of xzy.n
3- Saving ( successful )
5- closing folder and reopening it
4- No change has been done ?!?!
5- Turning screen off
6- Still no change
7- My changes ?! Where they have gone ?
8- Go to step 1
9-

 

[Christopher83]

1- Going to /data/..../xzy.n
2- Changing lots of parts of xzy.n
3- Saving ( successful )
5- closing folder and reopening it
4- No change has been done ?!?!
5- Turning screen off
6- Still no change
7- My changes ?! Where they have gone ?
8- Go to step 1
9-

It seems that what happened is not due to Dynamic FSync, because as you wrote you haven't an unexpected system crash and you also tried to turn the screen off...
The dynamic fsync could cause, but only in very exceptional cases, an issue on a file if there's a system hang/crash, you pull out the battery, or similar things, moreover when you turn off the screen a fsync is forced to be called to ensure the possible changes inside disk cache to be completely saved and the fsync back to work as usual.
Which is the app are you using to perform these changes?

Thanks.

 

[alireza7991]

It seems that what happened is not due to Dynamic FSync, because as you wrote you haven't an unexpected system crash and you also tried to turn the screen off...
The dynamic fsync could cause, but only in very exceptional cases, an issue on a file if there's a system hang/crash, you pull out the battery, or similar things, moreover when you turn off the screen a fsync is forced to be called to ensure the possible changes inside disk cache to be completely saved and the fsync back to work as usual.
Which is the app are you using to perform these changes?

Thanks.

Yes I did'nt have a system crash . but some times ( not always ) , files in data partition does not take changes while I try to change them using root explorer or other similar tool ( I am sure root acess has been granted ) which I think is because of Fsync force which causes buffers to wait untill screen off and then flush . but I do'nt know why FSync does not work currectly for me in data partition . maybe an OOM ( out of memory ) condition has been forced Fsynced allocated data buffer to be cleaned or a system crash or sth similar ?! maybe not related to FSync but since I have always problems with fsync in my files , I think this is also an fsync related problem

------------

Could you enable "KEXEC" config in your kernel?

 

[Christopher83]

Yes I did'nt have a system crash . but some times ( not always ) , files in data partition does not take changes while I try to change them using root explorer or other similar tool ( I am sure root acess has been granted ) which I think is because of Fsync force which causes buffers to wait untill screen off and then flush . but I do'nt know why FSync does not work currectly for me in data partition . maybe an OOM ( out of memory ) condition has been forced Fsynced allocated data buffer to be cleaned or a system crash or sth similar ?! maybe not related to FSync but since I have always problems with fsync in my files , I think this is also an fsync related problem

------------

Could you enable "KEXEC" config in your kernel?

The problem you're facing is strange, but almost surely not due to fsync, you could also try to reenable fsync at boot by using TricksterMod or PerformanceControl.

About the KEXEC, I'll take a look.

 

[KingKuno]

Is that Kernel working with CM10.1 Release 8 ? Or need I an update ? Thanks .

 

[Christopher83]

Is that Kernel working with CM10.1 Release 8 ? Or need I an update ? Thanks .

No, I need to update it to support latest R8 changes, I haven't found some time in these days...

 

[Christopher83]

K^Kernel v3.0 for JB 4.2.2 and builds for EMMC bricked devices

Hi guys,
I released the new builds of kernel v3.0 for JB 4.2.2, these builds include the fix to proximity sensor made by CastagnaIT (thanks to him!):

- Kernel 3.0.101
- Sources synched with cm-10.1_3.0 repo of Arco68 and ADC Team for JB 4.2.2 (CM 10.1) kernel builds
- Built with my latest custom Linaro 4.7.4-2013.10 toolchain optimized for Cortex-A8
- Resolved problems of magnetic, proximity and orientation sensor (credits to CastagnaIT)
- gp2a_proximity: readded wakelock is necessary to avoid problems with answer calls and some cleanups (credits to CastagnaIT)

Note:
I also created some builds for EMMC bricked devices for latest v3.0 release for JB 4.2.2 and v2.9 for JB 4.1.2, you can find a new subfolder inside the release folder named Emmc_Brick, let me know if they work without problems.
Thanks @houselective and @ktulu84 for their support in testing!

 

[sava92ns]

Hi guys,
Note:
I also created some builds for EMMC bricked devices for latest v3.0 release for JB 4.2.2 and v2.9 for JB 4.1.2, you can find a new subfolder inside the release folder named Emmc_Brick, let me know if they work without problems.
Thanks @houselective and @ktulu84 for their support in testing!

I just flashed JB 4.2.2 390MB+ emmc patched... if you need anything to be tested just let me know. For now everything seems fine, I was so long on stock kernel that I forgot what settings to use...

Anyway, I want to ask is there any setting (governor or whatever) to reduce lags in first few seconds after unlocking device. My friend owns i9000 his phone is responsive the moment he turns it on... Mine has low fps, I need to go back and forth between home screens to make it go fast. Lockscren animation is fine, but after unlocking phone is slow until I do that. Hope you understand my problem...

Thank you so much for this kernel.

 

[käsebr0t]

I just flashed JB 4.2.2 390MB+ emmc patched... if you need anything to be tested just let me know. For now everything seems fine, I was so long on stock kernel that I forgot what settings to use...

Anyway, I want to ask is there any setting (governor or whatever) to reduce lags in first few seconds after unlocking device. My friend owns i9000 his phone is responsive the moment he turns it on... Mine has low fps, I need to go back and forth between home screens to make it go fast. Lockscren animation is fine, but after unlocking phone is slow until I do that. Hope you understand my problem...

Thank you so much for this kernel.

You can try to set a higher minimum frequency. This may help against lags after waking the phone from deepsleep, but may also cause a higher battery drain.

Gesendet von meinem GT-I9001 mit Tapatalk