yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 Android Development] bladecgn:
Yes, maybe get the boot animation fixed + some more ggodies :) Thanks for your efforts!
[Galaxy Note GT-N7000 Android Development] XxPixX:
Looks like they've begun work:

https://gerrit.nameless-rom.org/#/q/status:open
[Galaxy Note GT-N7000 Android Development] GeeckoDev:
So their magical solution is to run the proprietary hwc? :rolleyes:

From my observations hwcomposer is not the problem, gralloc is.

I've set up a gralloc-mali repo to see the differences between each release of the open-source gralloc module provided by ARM (these f***ers never provide a changelog). It seems that our current gralloc is based on the r2p3-01rel0 release with some Exynos-specific changes (and hacks) on top. I would love to start working on that but I need my desktop PC first.

I've realized that each Mali release (blobs + kernel source + gralloc) is targeted for a specific version of Android:

r2p3 -> ICS (makes sense since our gralloc is based off Insignal release for ICS)

r2p4/r3p0 -> JB 4.1 (Samsung uses r2p4 on JB 4.1 for performance reasons)

r3p1 -> JB 4.2

r3p2 -> JB 4.3

r4p0/r4p1 -> KitKat (Samsung uses r3p2 on KitKat maybe for performance reasons too)

r5p0 -> Lollipop (we have yet to see this release on an Exynos 4 device, will probably never happen)
[Galaxy Note GT-N7000 Android Development] :
[MENTION=5145944]GeeckoDev[/MENTION]

Can't we use their (r4p0) blobs and gralloc for our note? Same CPU tree and same GPU.

GT-N7000 cihazımdan Tapatalk 2 ile gönderildi
[Galaxy Note GT-N7000 Android Development] GeeckoDev:
I tested r4p0 recently, it's not very good, I had a lot of issues and reduced performance. Maybe I did something wrong though, but I have no idea what could be the cause.

Edit: *quack*
[Galaxy Note GT-N7000 Android Development] GeeckoDev:
Announcing Raw Kernel r7

Time for a new release.

Changelog :

* Latest Omni changes included

* Restore stock GPU steps, thresholds and voltage (2 steps: 160/267MHz instead of 134/200/267)

* 59hz panel refresh rate instead of 57hz

* gralloc with refresh rate drift fix included

These three changes should bring another increase in smoothness and responsiveness. Do not expect Touchwiz smoothness though, we still need to fix userspace :laugh:

Download :

* raw_kernel_r7_k44.zip

* raw_kernel_r7_l50_alpha.zip <- This is an early Christmas present for those few people who run Lollipop. It even has a semi-working recovery from Omni.
[Galaxy Note GT-N7000 Android Development] bladecgn:
Dear GeeckoDev, thank you so much for your kernel!!!!

I now have the perfect combination to make my note fast, battery friendly and reliable with much comfort and security.

Things I am using and that I can recommend:

* Your kernel (for undervolting, faster graphics)

* SlimSaber KK 4.4 ROM (fast and comfortable with many options)

* XPosed-Framework (with XPrivacy, AppSettings)

* LLama + SecureSettings (for saving battery e.g. turning off Wifi/GPS when on battery and screen goes off, turning on bluetooth when in Car mode, ...)

* Larger (6GB) /data Partition (repartitioned with .pit file)

* Greenify to hibernate all the apps not in use

* Titanium Backup for freezing system apps I do not use

* AdBlock (for faster browsing without apps)

* FolderMount for moving some folders to ExtSdCard

* From time to time I flash lanchon kernel and use recovery trimmer to do TRIM (makes nand memory faster), then back to your kernel

I am over the moon and very amazed that my "old" Note 1 is so fast and well-useable. Hope I can use it for some more years to come. Congrats and thanks to every developer who made this possible.
[Galaxy Note GT-N7000 Android Development] acidglory:
Guys

I flashed r7.K44 on my rom but its just makes my phone fc at boot...it says 'android system ui has stop' bla bla...etc.....

Try wipe dalvic cache same prob.

Is it normal?
[Galaxy Note GT-N7000 Android Development] LAKAME_MAN:
Dunno what your ROM is, but it works fine for me on Slim. Although I did lose root (which I should've realized because this is based on Omni).

[MENTION=5145944]GeeckoDev[/MENTION] thanks for all of your hard work! Out of curiosity, are you planning on updating the recovery? Not demanding or requesting or anything of that sort, since the recovery is functional enough anyway, but I just wanted to know if you have that in mind.

And I'm only asking because we can't change the recovery without changing the kernel on our device, and your kernel seems to be the best we have right now.

Sorry if my question was rude in anyway. And thank you for all your hard work.
[Galaxy Note GT-N7000 Android Development] GeeckoDev:
If your rom is CM11 based, it will not run properly. Try [MENTION=4576973]forest1971[/MENTION]'s CM11 kernel.

Oui
[Galaxy Note GT-N7000 Android Development] acidglory:
Yup...my rom is cm11 base....sigh....
[Galaxy Note GT-N7000 Android Development] 180490:
ok, i installed r7 on slimkat, it's much faster than stock but what can i do to regain root? it's enabled in developer setings

:confused:
[Galaxy Note GT-N7000 Android Development] LAKAME_MAN:
I don't know what the "correct way" is, but I just flashed SuperSu from the recovery.
[Galaxy Note GT-N7000 Android Development] bladecgn:
I have the impression that when using SlimSaber just on its own (with the included kernel) graphics / scrolling is smoother.

With raw r7 i get some (little) microstutters.
[Galaxy Note GT-N7000 Android Development] Hakem:
+1

Verstuurd vanaf mijn GT-N7000 met Tapatalk
[Galaxy Note GT-N7000 Android Development] GeeckoDev:
This is interesting, can you (and [MENTION=239740]bladecgn[/MENTION]) push SlimSaber's gralloc to your device like this:

adb root
adb remount
adb push gralloc.exynos4.so /system/lib/hw
adb reboot

and observe the result?
[Galaxy Note GT-N7000 Android Development] GeeckoDev:
I made another interesting discovery today. :) It's related to the Insignal graphics stack I tried to merge last year.

So, last year, Insignal released their jb-mr1.1 source for Exynos 4412 that was insanely great because their graphics stack is entirely revamped from the ground up, looking a lot like what's found in the Nexus 10 which uses an Exynos 5 SoC. When doing the diff, it turns out this SoC is not so different from our Exynos 4, so the code is like 95% similar.

The first thing to do was to merge the userspace code. That's a slightly modified gralloc with an entirely new hwcomposer that does the job. After testing it, it was barely working, crashing a lot, and after some inspection it turned out that we needed to update some kernel drivers.

The Insignal kernel is based on the 3.4 Android kernel reference, s3cfb driver is nuked and replaced by a new s3c-fb framebuffer driver that interacts with the new hwcomposer and uses dmabuf/ION. This new driver in turn depends on a new 3.4 ION driver and Mali blobs with UMP disabled and dmabuf enabled (r3p2).

I could merge the new ION driver without much problems, and the Mali driver was just a matter of replacing the blobs. However, removing the old s3cfb driver meant that the panel driver was also gone (the Origen board uses a LCD, which is completely different), and I had no idea how to get the panel working at this point. Also, merging the s3c-fb driver meant that the kernel was crashing early with no way to debug it. I was hitting a wall...

This morning I looked at the i9500 (S4) kernel code and guess what... Everything's there, the new framebuffer driver with all the panel drivers, even OUR panel driver! It includes: s3c-fb, MIPI-DSI driver, lcdfreq driver, s6e8aa0 panel driver. I know how to merge this sh*t. And we have three reference sources: exynos4 insignal, exynos5 nexus, exynos5 i9500 that share almost the same code.

One problem though, Insignal has taken down the sources and binaries a few months ago. However, we have it all backed up: kernel source, userspace code (1, 2), and the last missing piece, the blobs (thanks [MENTION=2995885]sbrissen[/MENTION] !).

This is our chance to get a graphics stack that surpasses what Samsung ships and will ever ship with Touchwiz for i9100/N7000/i9300/N7100 :victory:

Edit: I'm writing this wall of text to help other developers understand what's going on. This is something I needed when I started developing... It is very hard to get any documentation, so I hope it will help others that would like to take part of this.

Edit2: by looking at gralloc_priv.h, it seems Insignal's gralloc is based on r3p2-01rel0 release.
[Galaxy Note GT-N7000 Android Development] bladecgn:
Did as you wished. Now it is as smooth as SlimSaber is. Hope this helps.
[Galaxy Note GT-N7000 Android Development] kazuya_kun:
Okay thx for the Info! I am still new here so sorry for my stupid question ^^ Does that actually mean that Developers can actually build up-to-date kernels with the very newest drivers end espacially mali drivers, which can surpass the current version a lot (by performance)? Or is it possible to eplain it for less experienced people in this matter? ^^

Thank you in advance ^^

greetings kaz
[Galaxy Note GT-N7000 Android Development] GeeckoDev:
Gaming performance won't improve much (if not at all), but I expect a steady 60fps UI, just as it should be.
[Galaxy Note GT-N7000 Android Development] kazuya_kun:
ah alright so it is more about the overall stability right?
[Galaxy Note GT-N7000 Android Development] GeeckoDev:
No idea about stability.. There's also a battery life gain if hwcomposer is working properly.
[Galaxy Note GT-N7000 Android Development] kazuya_kun:
okay thx for the answers ^^
[Galaxy Note GT-N7000 Android Development] f0xy:
[MENTION=5145944]GeeckoDev[/MENTION] always fighting the good fight! Very good to see this!
[Galaxy Note GT-N7000 Android Development] acidglory:
This r7 is for cm what base actually as it cannot use on cm11? Tq
[Galaxy Note GT-N7000 Android Development] DerTeufel1980:
What do you think about open source hwc used by namelessrom, based off hardkernel mali r4p0? AFAIK they got hwc working on i9300 and N7100.

Gesendet von meinem GT-N7105 mit Tapatalk
[Galaxy Note GT-N7000 Android Development] szotaa:
AFAIK its still not finished
[Galaxy Note GT-N7000 Android Development] LAKAME_MAN:
I did the same thing (although I'm on Slim, not SlimSaber) and it does feel smoother now. Hope this helps.
[Galaxy Note GT-N7000 Android Development] ardicli2000:
First of all, [MENTION=5145944]GeeckoDev[/MENTION] you are amazing :D

Secondly, what I understand from your post is that, due to lack of necessary documentation for exynos devices, Devs were having hard times and difficulties to develop better even TW and AOSP based Roms. Now with your new findings, they are going to be able to dig more info and will have the chance to implement new changes which will bring a stable Rom with a truly and fully working HWComposer, gralloc nad 60Hz Screen.

If these implementations will not result in performance boost at all, they will bring us to the edge of using our Note at full performance with Custom Roms and maybe with TWs. Like Lollipop Rom developed by [MENTION=799465]bauner[/MENTION], we can use our devices even one year or two more. This time more stable and efficient.

Hope I am right :)

Regards,

Kerem
[Galaxy Note GT-N7000 Android Development] rafi_android:
Can i flash r7lollipop with bauner alpha 5.0?
[Galaxy Note GT-N7000 Android Development] arasgym:
I have flashed it through custom recovery in bauner alpha7.1, seems smooth, keep up the good work, thanks a lot :)
[Galaxy Note GT-N7000 Android Development] GeeckoDev:
Can you put the result of "adb logcat" on pastebin?
[Galaxy Note GT-N7000 Android Development] urviagarwal:
Sorry if it sounds nonsensical but...I flashed r7.k44 over Carbon ROM.. got continious FC on startup ..

I had to remove the battery and then boot on recovery and reflash the ROM and then restore..

Few pages back someone posted about flashing the previous version with Carbon and seemed to have worked fine..
[Galaxy Note GT-N7000 Android Development] CryNickSystems:
I would like to use your Kernel, but unfortunately I'm getting FCs all the time after booting..

Btw.: using latest CM11 on my Note.
[Galaxy Note GT-N7000 Android Development] GeeckoDev:
Okay. Hang on. I'm tired of this sh*t
[Galaxy Note GT-N7000 Android Development] ardicli2000:
This kernel does not support cm11.

That's so simple....
[Galaxy Note GT-N7000 Android Development] CryNickSystems:
Then why does it say the Kernel supports AOSP roms with KK?

CM11 = AOSP KK
[Galaxy Note GT-N7000 Android Development] ardicli2000:
If AOSP and the CM were to be the same thing, then why the hell would we call it CM???

They are not the same....
[Galaxy Note GT-N7000 Android Development] GeeckoDev:
Announcing Raw Kernel r4 for Touchwiz

Changes over Raw Kernel TW r3 :

* FPBug patch included

* misc fixes for initramfs and build

Only compatible with Touchwiz roms.

Download :

* raw_kernel_r4_tw.zip (r3p1 blobs + libc.so included)

FPU corruptions are gone. Touchwiz will be more stable than it ever was. It also seems to fix a little glitch I had where, when using the Google Now Launcher, the wallpaper was slightly lagging behind.

Edit: also fixes unstable USB tethering !

Coming soon for AOSP roms (Omni, CM11, CM12). :good:
[Galaxy Note GT-N7000 Android Development] User_99:
Any chance to get this fix included in TW r1 kernel becouse of Gallery bug? Finger crossed :)
[Galaxy Note GT-N7000 Android Development] Cinthiar:
Are there any mirrors for download? Ge.tt down atm?
[Galaxy Note GT-N7000 Android Development] korkunov:
Link for download, PLZ

Confirm, I can`t download too...
[Galaxy Note GT-N7000 Android Development] 01000010:
Can we use r7 on [MENTION=799465]bauner[/MENTION]'s beta 1?

---

gt-n7000 with Bauner's Nightowl beta 1
[Galaxy Note GT-N7000 Android Development] kazuna69:
I was thinking the same thing too, but I do experience freeze in 7.1 alpha using this kernel/recovery, :silly:

but I'm pretty sure, [MENTION=5145944]GeeckoDev[/MENTION] have looked into this matter, I think it would be wise to wait for his new releases :highfive:
[Galaxy Note GT-N7000 Android Development] ardicli2000:
Yes.

Someone already tried that and reported back that everything is alright.
[Galaxy Note GT-N7000 Android Development] FabreFaction:
[MENTION=5145944]GeeckoDev[/MENTION]

Hi

The link for 4.4V7 seems to be down (((raw_kernel_r7_k44.zip)))

When I click on the link it is directing me to http://ge.tt/2xXs4y62/v/0?c

Not sure if this is correct as this is the first time I've tried to download V7

It does look as though ge.tt might be down for some reason though

I don't suppose you've mirrored the file anywhere?

NOTE: Just quickly checked the links for 5.0 and TW, they aren't working either.

Thanks for a groovy year of N7000 development.

Long may you continue to push and improve our ageing device.

All your efforts are much appreciated.

Best wishes to you and yours over the festive season and into the New Year.

Cheers..................... FF
[Galaxy Note GT-N7000 Android Development] User_99:
Link for r4_TW also not working...
[Galaxy Note GT-N7000 Android Development] GeeckoDev:
ge.tt is back up. :good:
[Galaxy Note GT-N7000 Android Development] snow:
HWC for i9300 is alive!!! :D

http://xdaforums.com/showpost.php?p=57661297&postcount=1992
[Galaxy Note GT-N7000 Android Development] sir44:
r7 for KK4.4 works very good with slimsaber 12/02 ;)
[Galaxy Note GT-N7000 Android Development] GeeckoDev:
They have rebased their kernel on n7100 sources, with zero support for 4210 devices (S2/Note). Also I don't see any public userspace modifications for this in their repo.
[Galaxy Note GT-N7000 Android Development] bladecgn:
Just out of curiosity: Now that you seem to have the parts needed for the graphics driver (drivr, hwcomposer, blobs...), did you make any progress?
[Galaxy Note GT-N7000 Android Development] notabenem:
installed r4 for KK4 on my S2 (with the latest Omni on it) and I am getting weird display artefacts and the phone would not get past the bootloader. Not even the yellow triangle was showing correctly (all kinds of weirds lines around it). Fortunately, ODIN worked, so I am back to a usable system.
[Galaxy Note GT-N7000 Android Development] GeeckoDev:
No offense, but.... are you retarded? Did you see any mention to the S2 on this thread?
[Galaxy Note GT-N7000 Android Development] GeeckoDev:
I didn't work on it yet. Do not ask for ETAs, do not spam me, when something interesting comes out, I will post here. :D
[Galaxy Note GT-N7000 Android Development] pSyCh¤_O_O:
Lol
[Galaxy Note GT-N7000 Android Development] bladecgn:
Hmmm... my cunnning plan to casually ask for an ETA without asking for it as forum rules forbid it seems to have been revealed. Excuse-moi, mon ami. Won't happen again ;)
[Galaxy Note GT-N7000 Android Development] notabenem:
As a matter of fact, I did!

What makes things worse, I was redirected here from the FPBug thread where we mostly dealt with S2. You forked the Omni kernel (which is common). You're right, I should have been more careful. I have confused common source (which I hope it still is) with common binary.

Anyway, no harm done. But I hope once you got that hwc working, it will also be applicable for the S2.
[Galaxy Note GT-N7000 Android Development] GeeckoDev:
Flashing another kernel than the one built for your device can hardbrick your phone, so be careful next time :laugh:
[Galaxy Note GT-N7000 Android Development] XxPixX:
Although I agree 100% with that, usually kernels check in the updater-script whether you are flashing it to the right phone, might be worth adding to the next version just in case ;)
[Galaxy Note GT-N7000 Android Development] GeeckoDev:
Damn, it seems recovery is broken with r4/TW (flashing screen). I'll release r5 soon to fix that, you'll have to flash using ODIN/heimdall.
[Galaxy Note GT-N7000 Android Development] abdullahchoudhary97:
Hey [MENTION=5145944]GeeckoDev[/MENTION] can u or anybody else please help me?

i'm running nightowl cm 12 for my note. How can i flash kernel to that?

Should i hav to wipe everything or just going to recovery flash the kernel ???
[Galaxy Note GT-N7000 Android Development] kazuna69:
No need to wipe the whole thing, ;)

you can choose to wipe only cache from the cwm bauner's recovery, then flash the raw v7 kernel Lollipop by geeckodev

:laugh:

done, your phone rock and roll' :silly:
[Galaxy Note GT-N7000 Android Development] snow:
[MENTION=5145944]GeeckoDev[/MENTION], look here: https://bitbucket.org/arter97/arter97-i9300-release/commits/5e2d7c9dab6282e40748c0a6956e17b5bed81841

Files extracted from Nameless ROM thanks to arter97 :D

I made an experiment, copied all files into device. Bootloop (SAMSUNG screen).

Then I copied one file at once, rebooted. If device booted, I copied another one and so on...

I copied 4 files till now. And device & ROM it's working. Not sure if I made something with this experiment, but when I opened Agenda book the text was missing for less than 1 sec, like HWC made actually something! :D Not sure if glitch, but I saw this just a single time. :)

These are the files I copied into device:

lib/hw/hwcomposer.exynos4.so

lib/libExynosHWCService.so

lib/libExynosIPService.so

lib/libhwconverter.so

Maybe we need (more/another) files from Nameless ROM, I really don't know.

libsurfaceflinger.so seems to bootloop device, so DO NOT COPY IT!

Best Regards!
[Galaxy Note GT-N7000 Android Development] honf:
[MENTION=5145944]GeeckoDev[/MENTION], is it possible that you enable a few kernel modules when you compile so USB cameras can be used via OTG?

Some help on what to enable here in the kernel configuration:

http://xdaforums.com/showthread.php?t=2656922

Edit:

Seems only the

CONFIG_USB_VIDEO_CLASS

needs to set to yes. Everything else is already enabled if I'm looking at the right git branch. Can't find the Lolipop one though.
[Galaxy Note GT-N7000 Android Development] GeeckoDev:
Cool experiment, I was about to do the same thing. Since this HWC uses fences I think it needs to be enabled in the kernel, and there are likely other kernel changes (in s3cfb) to merge, too. What is the logcat output?
[Galaxy Note GT-N7000 Android Development] snow:
Look here for logcat: https://paste.ee/p/gHIhT ;)
[Galaxy Note GT-N7000 Android Development] GeeckoDev:
Thanks. Well, it's pretty clear that hwcomposer isn't working because libhdmiclient.so is missing, see line 737. I'm 99% sure you'll have problems with missing ioctls in the kernel after you get it to load. :D
[Galaxy Note GT-N7000 Android Development] snow:
Yeah, I saw that and I tried to add missing file(s) [because are more than just one]. :)

More recent logcat:

So far these files are working:

lib/hw/hwcomposer.exynos4.so

lib/libExynosHWCService.so

lib/libExynosIPService.so

lib/libhwconverter.so

lib/libhdmi.so

lib/libhdmiclient.so

lib/libTVOut.so

lib/libedid.so

lib/libddc.so

Copied libcec.so into device, but it seems is not working for our device (after SAMSUNG logo just black screen). :P
[Galaxy Note GT-N7000 Android Development] ardicli2000:
Hi [MENTION=5145944]GeeckoDev[/MENTION],

Check this out: http://www.sammobile.com/2013/03/18...roid-5-0-for-the-galaxy-s-iii-galaxy-note-ii/

Maybe you can find something interesting within the updated kernel. What do you think?
[Galaxy Note GT-N7000 Android Development] GeeckoDev:
Hmm I think you gave me the wrong link because it's news from two years ago and I don't see what kernel you're talking about.
[Galaxy Note GT-N7000 Android Development] GeeckoDev:
It's too early to give up. Do you have a logcat up to this point?
[Galaxy Note GT-N7000 Android Development] snow:
Nope, but I will test tommorow again and I will post logcat.

Almost forgot.... One weird thing is that when I copied some files and rebooted, I've lost network signal and I got error when trying to search/select network (

I think kernel-related issue; happens without Nameless ROM files

). :)

EDIT: It seems I have a logcat saved on PC. :D Last logcat from a working device: http://pastebin.com/rDkiKT7w :)

P.S.: I have "refresh rate = 60.00 Hz" because I added your gralloc fixed on my S2 which works without any issue! :D

EDIT 2: Hmmm... I got logcat after black screen (copied libcec.so). Very interesting logcat is here: http://pastebin.com/Actt60BL

I copied all the files I mentioned in my earlier post + libcec.so :D
[Galaxy Note GT-N7000 Android Development] GeeckoDev:
It's handy to look at the android_hardware_samsung commit history to see what needs to be updated. This looks related to the crash you're getting.

Copy gralloc, libfimg and libfimg. ;)

Edit: for reference, here's what the logcat should look like once it's working http://pastebin.com/cbdJigNj
[Galaxy Note GT-N7000 Android Development] snow:
I copied gralloc, libfimg and libfimg. Somehow after 5 minutes, device booted up (after about 2 bootloops; image stuck after 1-2 sec [I just saw half of cyanogenmod text, not even the logo of CM 11]; [second boot was a little bit better, I saw cyanogenmod text and logo, logo was a little bit dark, blue to black color]; it remains stuck a lot of seconds). Finally it booted. But it works really slow, I mean there's a big lag. Is not loading wallpaper, I see just black wallpaper. System is working, but when I try to "unsleep" (aka wake up) phone, I can see just clock, battery and signal (no lockscreen, rest of screen black). First 20 secs (When I "wake up" phone from lock screen) was a working phone (with lag, but somehow it worked). Device is up, but I can't do anything. Logcat here (when I was stucked): http://pastebin.com/8CAiYC31 And another logcat when device already booted: https://paste.ee/p/UKOUy

One funny thing (and weird at the same time) is that I hear lock sound (that sound when you press lock button) at every 3 seconds. I'm scared :D [happened only once]

EDIT: It reboots suddenly.

EDIT2: Sometimes boots, sometimes not. :D

Anyway, what means "E/SECHWC_LOG( 4322): runCompositor:stretch failed retry#XYZ"? (XYZ represents any number). I see this message spammed in logcat. :)