[KK 4.4][KERNEL] Neo - Kernel CMA TWRP 23.04 Version Linaro 4.8

Search This thread

dzee206

Senior Member
Oct 5, 2011
1,057
693
Seattle
It is difficult for me because i dont have this device but i develop a kernel for it. You tried the kernel in this thread?

Sent from my GT-I9000 using xda app-developers app

definitely not your kernel at fault here, its obvious from the log hes porting roms from the I9000 and messing them up some how or else more people would be commenting about that issue. he should try flashing a rom thats already in the vibrants dev section and post the log here. ive flashed about 20 or so roms with your kernel and its been smooth sailing so far nothing wrong with the recovery.

UPDATE: my recovery log as proof nothing is wrong with the kernel let alone the recovery, i flashed a personal version of C-RoM that i did on my phone while on break at work lol true flashaholic

Sent from my Half Baked Vibrant using XDA Premium 4 mobile app
 

Attachments

  • recovery.log.zip
    12.9 KB · Views: 13
Last edited:

waihung0626

Senior Member
Nov 23, 2013
1,059
160
Shantou
www.lidroid.com
definitely not your kernel at fault here, its obvious from the log hes porting roms from the I9000 and messing them up some how or else more people would be commenting about that issue. he should try flashing a rom thats already in the vibrants dev section and post the log here. ive flashed about 20 or so roms with your kernel and its been smooth sailing so far nothing wrong with the recovery.

UPDATE: my recovery log as proof nothing is wrong with the kernel let alone the recovery, i flashed a personal version of C-RoM that i did on my phone while on break at work lol true flashaholic

Sent from my Half Baked Vibrant using XDA Premium 4 mobile app

Are you have try add this code go to updater-script and flash agin?
Add This:
assert(getprop("ro.product.device") == "vibrant" || getprop("ro.build.product") == "vibrant" ||
getprop("ro.product.device") == "vibrantmtd" || getprop("ro.build.product") == "vibrantmtd" ||
getprop("ro.product.device") == "SGH-T959" || getprop("ro.build.product") == "SGH-T959" || abort("This package is for \"vibrant,vibrantmtd,SGH-T959\" devices; this is a \"" + getprop("ro.product.device") + "\"."););
 

dzee206

Senior Member
Oct 5, 2011
1,057
693
Seattle
Are you have try add this code go to updater-script and flash agin?
Add This:
assert(getprop("ro.product.device") == "vibrant" || getprop("ro.build.product") == "vibrant" ||
getprop("ro.product.device") == "vibrantmtd" || getprop("ro.build.product") == "vibrantmtd" ||
getprop("ro.product.device") == "SGH-T959" || getprop("ro.build.product") == "SGH-T959" || abort("This package is for \"vibrant,vibrantmtd,SGH-T959\" devices; this is a \"" + getprop("ro.product.device") + "\"."););

theres your problem remove those lines and make sure theres no empty line at the top of the updater-script and all should be fine. try that and report back with your results, doing what i suggest should make your mackay and c rom port bootable if not there are other errors going on...

Sent from my Half Baked Vibrant using XDA Premium 4 mobile app
 

waihung0626

Senior Member
Nov 23, 2013
1,059
160
Shantou
www.lidroid.com
theres your problem remove those lines and make sure theres no empty line at the top of the updater-script and all should be fine. try that and report back with your results, doing what i suggest should make your mackay and c rom port bootable if not there are other errors going on...

Sent from my Half Baked Vibrant using XDA Premium 4 mobile app

With neatkernel and cm or sp kernel no problem, so it is not my problem!
 

aznflawless

Senior Member
Jun 16, 2012
474
47
28
San Jose
I'm experiencing a battery drain. I notice that my Vibrant dies much faster. I check the battery usage, and the cell standby is eating my battery. I have airplane mode on all the time (I use my vibrant for multimedia consumption, not as my phone)
 

DerRomtester

Senior Member
Aug 20, 2012
2,899
5,824
27
Neumarkt
I'm experiencing a battery drain. I notice that my Vibrant dies much faster. I check the battery usage, and the cell standby is eating my battery. I have airplane mode on all the time (I use my vibrant for multimedia consumption, not as my phone)

Try bfq scheduler. I also noticed with row a high battery drain ?

Sent from my GT-I9000 using xda app-developers app
 

waihung0626

Senior Member
Nov 23, 2013
1,059
160
Shantou
www.lidroid.com
The Bluetooth have issue.waiting nights time I'll upload my video!
Sorry my had English.

https://www.dropbox.com/s/7jnws994xpdrph2/SCR_20140501_190033.mp4

Sent from my SGH-T959 using xda app-developers app

---------- Post added at 11:29 AM ---------- Previous post was at 11:28 AM ----------

And use sp kernel, neatkernel,no problem!

Sent from my SGH-T959 using xda app-developers app
 
Last edited:

dzee206

Senior Member
Oct 5, 2011
1,057
693
Seattle
nothing funky with bluetooth going on for me, was able to pair up with my old evo 4g fine.

Sent from my Half Baked Vibrant using XDA Premium 4 mobile app
 

Attachments

  • 1398966983163.jpg
    1398966983163.jpg
    26.2 KB · Views: 106
  • Like
Reactions: DIARADOUGOU

fscussel

Senior Member
Jul 1, 2007
517
13
Can I use this with android 4.2.2 ??? Is twrp working? why there's no version of twrp for vibrant in the official page?
 

DerRomtester

Senior Member
Aug 20, 2012
2,899
5,824
27
Neumarkt
Can I use this with android 4.2.2 ??? Is twrp working? why there's no version of twrp for vibrant in the official page?

No you cant use for 4.2.2.
This kernel is experimental. I am not yet a real developer and i dont know how to fix bugs. So if you notice bugs i am able to revert changes i made but not more.

Dont know why there are Bluetooth problems i did not made any changes. You should give NEAT kernel a try it is more optimized for vibrant.

Sent from my GT-I9000 using XDA Free mobile app
 

waihung0626

Senior Member
Nov 23, 2013
1,059
160
Shantou
www.lidroid.com
Guys i stop vibrant development. There arent as many downloads as for i9000.
And i dont wanna develop for only 60 users.

The news Too bad!!

and very thanks DerRomtester work!


but you can make and update final version for fix bluetooth problem:confused:

Thanks,thanks......

sorry my had English!
 
  • Like
Reactions: DerRomtester

dzee206

Senior Member
Oct 5, 2011
1,057
693
Seattle
Guys i stop vibrant development. There arent as many downloads as for i9000.
And i dont wanna develop for only 60 users.

The news Too bad!!

and very thanks DerRomtester work!


but you can make and update final version for fix bluetooth problem:confused:

Thanks,thanks......

sorry my had English!

no no no wtf man, this is bad. its still a hell of a kernel just wish it didn't end this way... @DerRomtester really enjoyed your work. wish you the best of luck on your projects and future projects.

Sent from my Half Baked Vibrant using XDA Premium 4 mobile app
 

DerRomtester

Senior Member
Aug 20, 2012
2,899
5,824
27
Neumarkt
no no no wtf man, this is bad. its still a hell of a kernel just wish it didn't end this way... @DerRomtester really enjoyed your work. wish you the best of luck on your projects and future projects.

Sent from my Half Baked Vibrant using XDA Premium 4 mobile app

I am so sry for you guys. I dont have the time to work on two different kernels with different ramdisks.
My source code also isnt optimized for two different ramdisks.
I also did not find a fix for the bluotooth problem some users reported. ( i didnt get a logcat which could be useful)

P.s. give neat kernel a try
(Also very fast)
:)

Sent from my GT-I9000 using XDA Free mobile app
 

dzee206

Senior Member
Oct 5, 2011
1,057
693
Seattle
will miss checking the thread for updates but i will continue to rock neo until its no longer compatible with roms or till 4.4.3 comes out.

Sent from my Half Baked Vibrant using XDA Premium 4 mobile app
 

Top Liked Posts

  • There are no posts matching your filters.
  • 7
    At first i have to say that i am not a developer.
    I only pick comments from other devs and add them into my kernel.
    This kernel is based on didhiy sources with some additions.
    Thanks a lot to didhiy who helped me to get this working.
    Sry for my bad english
    And thx to kasper_h for his Mackay-TWRP

    Differts to didhiy:
    - Build using the Cortax-A8 optimized Linaro 4.8 toolchain of Christopher83: http://xdaforums.com/show....php?t=2098133
    - O3 optimization
    - hard float + neon
    - ROW tweaks from francisfranco
    - CPU boost driver
    - Lowered swappiness 60->45
    - fifo + zen scheduler
    - sry no own kernel logo till now
    - 415 mb ram cause of CMA

    Source + Changelog:
    https://github.com/DerRomtester/android_kernel_samsung_aries/commits/stable

    Credits:
    -didhiy
    -pawtip
    -DerTeufel1980
    -Alberto96
    -Christopher83
    -faux123
    -TK-glitch
    -neobuddy89
    -kasper_h
    -stratosk
    6
    Changelogs

    09.03 Changelog
    - Now working with latest nightly
    - one version with and one without zram
    - 144 mb zram available
    - ramdisk: from cm-11-20140307-NIGHTLY
    - 1100 mhz step
    - dma-contiguous: do not retry other addresses

    13.03 Chagelog
    - samsung bootsplash
    - completly removed zram (causing lags)
    - kernel: Prevent unnecessary rfkill event generation. (maybe increases battery life)
    - AIO: Don't plug the I/O queue in do_io_submit() Asynchronous I/O latency to a solid-state disk greatly increased between the 2.6.32 and 3.0 kernels. By removing the plug from do_io_submit(), we observed a 34% improvement in the I/O latency

    15.03 Changelog

    - Entropy Tweaks
    - tmpfs: fix mempolicy object leaks
    - switch the protection of percpu_counter list to spinlock
    - timer slack controler
    - optimized AES and SH1 routines
    - backport CPUIDLE from 3.5
    - backport AIO (Asyncronous IO) from linux 3.5
    - mm: Dont use CMA pages for page cache
    - irq: Set CPU affinity right on thread creation
    - sync: allow async waits to be canceled
    - powerpc: Align p_dyn, p_rela and p_st symbols

    16.03 Changelog
    - latest toolchain from Christopher83 4.8.3 for cortex a8

    26.03 Changelog

    - Many Entropy tweaks (cherry-picked from faux123)
    - some Mutex changes
    - some vmalloc changes
    - ARM: 7583/1: decompressor: Enable unaligned memory access for v6 and above
    - ARM: dcache: select DCACHE_WORD_ACCESS for little-endian ARMv6+ CPUs

    31.03 Changelog

    - gcc 4.9 linaro toolchain from Cl3Kener
    - enabled graphite

    7.04 Changelog
    - ramdisk: update from cm-11-20140331-NIGHTLY
    - latest bfq v7r2 added
    - mm: vmscan: If kswapd has been running too long, allow it to sleep
    - net: loopback: set default mtu to 64K
    - ksm: check and skip page, if it is already scanned
    - defconfig: Enable Advanced TCP Congestion Control
    - defconfig: Enable KSM_CHECK_PAGE

    Changelog 14.04.2014

    - mm/readahead.c: fix readahead failure for memoryless NUMA nodes and limit readahead pages
    - ARM: s5pv210: enable IDE support in MACH_TORBRECK
    - ARM: msm: add missing include of linux/module.h
    - ARM: msm: export legacy DMA interfaces
    - cma: Remove potential deadlock situation
    - cpufreq: interactive: Remove unnecessary cpu_online() check
    - reverted to christophers83 toolchain lets wait for his optimized cortexA8 toolchain

    Changelog 23.04.2014
    - sry guys i am tooo lazy now for a changelog check my github account stable branch :D
    - updated ramdisk
    3
    It is difficult for me because i dont have this device but i develop a kernel for it. You tried the kernel in this thread?

    Sent from my GT-I9000 using xda app-developers app

    definitely not your kernel at fault here, its obvious from the log hes porting roms from the I9000 and messing them up some how or else more people would be commenting about that issue. he should try flashing a rom thats already in the vibrants dev section and post the log here. ive flashed about 20 or so roms with your kernel and its been smooth sailing so far nothing wrong with the recovery.

    UPDATE: my recovery log as proof nothing is wrong with the kernel let alone the recovery, i flashed a personal version of C-RoM that i did on my phone while on break at work lol true flashaholic

    Sent from my Half Baked Vibrant using XDA Premium 4 mobile app
    2
    will miss checking the thread for updates but i will continue to rock neo until its no longer compatible with roms or till 4.4.3 comes out.

    Sent from my Half Baked Vibrant using XDA Premium 4 mobile app
    2
    New kernel is online look at first page :D

    great work, fix your source link or add github to your profile ;)