GT-I9300_JB_Opensource_Update12.zip landed on Samsung OSRC this morning (XXUGMJ9). :good:
[KERNEL][AOSP/TW][27 Dec] War Kernel r3 // colder than ever
- Thread starter GeeckoDev
- Start date
Can those 4.3 kernel sources help develop the great kernel you've built for our Notes?
I'm particularly interested in missing feature of CM 4.2.x and later kernels: dock audio.
Ok, so after a little inspection of the sources, here's what i found :
* r2p4 and r3p1 drivers are still here, in drivers/media/video/samsung/
* r3p2 appeared in drivers/gpu/mali400/, which is unusual for a samsung but corresponds to hardkernel drop
* API version is 23 (r3p2-01rel3), compared to API 17 for r3p1 drivers
* no signs of orion platform (Exynos 4x10), only pegasus (Exynos 4x12)
The last point is quite embarassing. It means some more work for me to bring that up, and also, maybe, that there will be no updated drivers for the official firmware on all Exynos 4210 devices, including the Galaxy Note and Galaxy S2. Or they didn't take care of that yet.
EDIT:
Nevermind, it's named pegasus-m400 but there's a lot of ifdefs dedicated to the orion platform
Right now I'm messing with Makefile and Kconfig to get it to compile, it shouldn't take long.
EDIT2:
It's finally compiling. commit history
EDIT3:
Launching the kernel without the proper blobs warns about an API mismatch, which is good. I put libUMP.so and libMali.so but I get no logcat output. I think it's due to the voltage table set too low for the exynos 4210.
EDIT4:
IT WORKS ! :victory:
* r2p4 and r3p1 drivers are still here, in drivers/media/video/samsung/
* r3p2 appeared in drivers/gpu/mali400/, which is unusual for a samsung but corresponds to hardkernel drop
* API version is 23 (r3p2-01rel3), compared to API 17 for r3p1 drivers
* no signs of orion platform (Exynos 4x10), only pegasus (Exynos 4x12)
The last point is quite embarassing. It means some more work for me to bring that up, and also, maybe, that there will be no updated drivers for the official firmware on all Exynos 4210 devices, including the Galaxy Note and Galaxy S2. Or they didn't take care of that yet.
EDIT:
Nevermind, it's named pegasus-m400 but there's a lot of ifdefs dedicated to the orion platform
Right now I'm messing with Makefile and Kconfig to get it to compile, it shouldn't take long.EDIT2:
It's finally compiling. commit history
EDIT3:
Launching the kernel without the proper blobs warns about an API mismatch, which is good. I put libUMP.so and libMali.so but I get no logcat output. I think it's due to the voltage table set too low for the exynos 4210.
EDIT4:
Code:
D/libEGL ( 2014): loaded /system/lib/egl/libEGL_mali.so
D/libEGL ( 2014): loaded /system/lib/egl/libGLESv1_CM_mali.so
D/libEGL ( 2014): loaded /system/lib/egl/libGLESv2_mali.so
E/ ( 2014): Device driver API match
E/ ( 2014): Device driver API version: 23
E/ ( 2014): User space API version: 23
E/ ( 2014): mali: REVISION=Linux-r3p2-01rel3 BUILD_DATE=Wed Oct 9 21:05:57 KST 2013
Last edited:
Announcing Raw Kernel r3p2 test build
It's a long time due. ONLY FOR TESTING - MAY NOT BE STABLE
Source code branch with history: https://github.com/GeeckoDev/raw_kernel/commits/raw-10.2-r3p2
Changelog :
* Updated Mali drivers to r3p2-01rel3 with some hacks to support the orion platform (exynos 4210)
* Isn't it enough?
The UI feels smoother, Epic Citadel average fps went up (47.7fps on last test, it varies). Small graphical glitches still not resolved (checkerboard effect on transitions). You'll tell the rest!
Download :
* raw_kernel_r3p2_test.zip (userspace binaries included)
:good: :good:
It's a long time due. ONLY FOR TESTING - MAY NOT BE STABLE
Source code branch with history: https://github.com/GeeckoDev/raw_kernel/commits/raw-10.2-r3p2
Changelog :
* Updated Mali drivers to r3p2-01rel3 with some hacks to support the orion platform (exynos 4210)
* Isn't it enough?
The UI feels smoother, Epic Citadel average fps went up (47.7fps on last test, it varies). Small graphical glitches still not resolved (checkerboard effect on transitions). You'll tell the rest!
Download :
* raw_kernel_r3p2_test.zip (userspace binaries included)
:good: :good:
Last edited:
I got a black screen at bootup :/ Latest CM 10.2
I'll try reflashing.
I'll try reflashing.
Can you put your adb logcat output on pastebin please.
EDIT: allllllright the libraries are misplaced in the archive... sorry. you'll have binary blobs in /system/ now
Last edited:
Sure, I'll just reflash CM, let it boot up, reboot to flash Raw and try again.
Both issues fixed :highfive:
G
GuestK00219
Guest
Works good on latest cm10.2
Above all, the browser is much smoother and faster.
There seems to be an incompatibility with Tegrak oc, if I try to click on gpu optimization, the app crash.
Inviato dal mio GT-N7000 con tapatalk
Above all, the browser is much smoother and faster.
There seems to be an incompatibility with Tegrak oc, if I try to click on gpu optimization, the app crash.
Inviato dal mio GT-N7000 con tapatalk
Works good so far.
Flashed over asylum omni 05.11.13 and it fixed some problems with sleep of death.
Flashed over asylum omni 05.11.13 and it fixed some problems with sleep of death.
13 hours of uptime. Definitely smoother. Tegrak doesn't work as well, I may have to get in touch with the developer. Maybe this issue happens with the official 4.3 firmware? The screen flickering issue with the AOSP browser seems to have disappeared. Battery life doesn't seem bad. 58% after 11h unplugged, light use, Wi-Fi + mobile data + GPS enabled. Had a freeze yesterday, but can't reproduce...
I have defconfigs for other devices to ajust, and then I will submit the patch to @codeworkx so it gets reviewed and merged.
I have defconfigs for other devices to ajust, and then I will submit the patch to @codeworkx so it gets reviewed and merged.
Feels great, agree its smoother on OMNI asylum than the stock kernel.
Sent from my GT-N7000 using xda app-developers app
Sent from my GT-N7000 using xda app-developers app
The one issue that i get in every raw kernel:
Device is turned ON, USB debugging checked, Connect the device via USB and in command prompt execute "adb shell" and i get message "error: device not found". Am i the only one facing this issue?
I am on Slim ROM Version 2.
Device is turned ON, USB debugging checked, Connect the device via USB and in command prompt execute "adb shell" and i get message "error: device not found". Am i the only one facing this issue?
I am on Slim ROM Version 2.
Are you sure it happens with kernel only? I have proper connectivity.. You need to get the latest adb drivers 1.0.31 and authorize you computer..
It would be extra nice if you'd submit it to Omni gerrit as well.I have defconfigs for other devices to ajust, and then I will submit the patch to @codeworkx so it gets reviewed and merged.
I'll provide a patch but i'm so lazy about syncing the repo again and submitting it directly to gerrit... It will take ages with my crappy connection.It would be extra nice if you'd submit it to Omni gerrit as well.
Currently running smooth on AOKP from 6 hours. Feels smoother without any lags. Battery behavior seems normal with stock settings(haven't changed anything yet)
working great here, 16 hours uptime, no issues exept for tegrak.
It feels about as smooth as it was when i overclocked it.
It feels about as smooth as it was when i overclocked it.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone