yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 4 Original Android Development] optimuspraim09:
Hey guys... For some reason developer wont update changelog on OP so i cant do anything rather than asking... What are the current bugs ?
[Galaxy Note 4 Original Android Development] jackspadeza:
Thanks [MENTION=3463426]RaymanFX[/MENTION]! Reflashing and sticking to the kernel provided solved all my issues. There are very lil to none bugs in this ROM. Battery life is something amazing. Lag her and there. But nothing really stopping you from using this ROM. Thanks again mate
[Galaxy Note 4 Original Android Development] andrew.mackew:
Is there any new kernel?
[MENTION=3463426]RaymanFX[/MENTION] Do you plan to release any new "old" lollipop update?
[Galaxy Note 4 Original Android Development] zxcslo:
I downloaded latest on Friday, installed, setup and I was very satisfied with the battery life for two days. Today I went with my car on drive and tried Bluetooth and.... sh..t... BT calling still don't work. I can hear others, but they can't hear me. That a deal-breaker for me and I went back to previous ROM.

In every other aspect this ROM is very, very good. I like it very much and I want to use it, but I need BT in my car for calling (I don't care for music).

What I can't understand is why, after so much time, BT calling still won't work?
[Galaxy Note 4 Original Android Development] murtadha50:
What is the best kernel to use with this great aosp rom?
[Galaxy Note 4 Original Android Development] onbeskarakterli:
The kernel that comes wtih the ROM. There isn't any active custom kernel development for this ROM.
[Galaxy Note 4 Original Android Development] GialanG:
As far as I know, there are 2 custom kernels for this: Ultimate kernel and the less active Googy-Max
[Galaxy Note 4 Original Android Development] vacs03:
Location and ambient display disabled
[Galaxy Note 4 Original Android Development] Konskl:
Is Ultimate Kernel 51 new functioning with the 15/10 build?
[Galaxy Note 4 Original Android Development] jackspadeza:
Remember UK is banned from xda. including posts about it. bleh

And to answer your question. there are quite a few big issues still lurking on UK AOSP. I wouldn't recommend using it. Stock kernel is fast and stable! :)
[Galaxy Note 4 Original Android Development] murtadha50:
What about googy max kernel is it fine ?
[Galaxy Note 4 Original Android Development] jackspadeza:
I remember trying GoogyMax a few builds back and there was more lag and a few bugs. Remember there's no overclock in GoogyMax as it wasn't completely finished
[Galaxy Note 4 Original Android Development] SaschaHa:
Best kernels for me are Talexop (soft version) and Suemax. I think they should work with AOSP too but don't know (I'm on TW based 5.1.1 rom).
[Galaxy Note 4 Original Android Development] suat6027:
Te kernels dont work... too too many lags...
[Galaxy Note 4 Original Android Development] :
holy cow. Try dual booting another rom and if the problem presists try changing your battery
[Galaxy Note 4 Original Android Development] masaichris:
from the stats you put up there, it seems that your issue might be caused by wifi, try turning wifi off (and all wifi related services like wifi tethering) while not in use, Also disable the "Scanning always available" option in the Advanced wifi options. Check if it brings on any change. if it doesnt, try [MENTION=5545167]SirHydarnes[/MENTION] advice.

---------- Post added at 07:12 PM ---------- Previous post was at 06:58 PM ----------

Googymax kernel was very good for this ROM(less heat when charging) but the developer is no longer developing the kernel. For the latest build and a few builds before, the kernel breaks the Proximity sensor.

I tried Ultimate Kernel 51 but it didnt even boot on the latest build. So i think so far, there is No AOSP kernel for the Exynos Note 4.
[Galaxy Note 4 Original Android Development] jackspadeza:
TW kernels don't work in AOSP and vica versa.

You WILL end up in a boot loop ;)
[Galaxy Note 4 Original Android Development] onbeskarakterli:
One of them breaks MTP and the other one breaks proximity sensor. When I replied, I meant it. There is no custom kernels in active development for this ROM.
[Galaxy Note 4 Original Android Development] :
Hey guys. I haven't used this rom for a while. So can someone update me on the new features and bug list?

The important stuff to me are Music playback bugs (music stops when closing camera, sometimes music played in slo mo!!) and switching to speaker mode and then again to normal while calling used to break the audio completely. And I experienced another bug with screen waking which lagged.

So are any of these fixed?
[Galaxy Note 4 Original Android Development] emenny81:
Screen lag is still present.
[Galaxy Note 4 Original Android Development] masaichris:
I think all the bugs you listed are still present. From my opinion, they are very minor bugs.
[Galaxy Note 4 Original Android Development] alanead07:
Hello guys Is there a new update?

And I want the best kernal for this rom
[Galaxy Note 4 Original Android Development] andrew.mackew:
Agreed :good: Those are minor issues.. the rom is really great! :)

BTW [MENTION=3463426]RaymanFX[/MENTION] any new update coming anytime soon?
[Galaxy Note 4 Original Android Development] :
No it definitely is a great rom but some of those bugs aren't minor to me. I use trusted face instead of fingerprint on this rom and every time i locked the screen and then unlocked it music stopped and it drove me nuts. The screen on lag yes is a minor bug. And about speaker bug, again is a problem for me...

there's no doubt that this is the best rom in terms of performance and battery life but in other terms it needs some work and in some terms it can never be better like supporting fingerprint and stuff.
[Galaxy Note 4 Original Android Development] Alt34:
Hey guys I just notice that Snapchat force close when taking a video with back camera !
[Galaxy Note 4 Original Android Development] Tyrany:
[MENTION=3463426]RaymanFX[/MENTION] sorry for the offtopic, but since you are the person most close to a fully funcional aosp rom on an exynos soc can you please take a look here: http://xdaforums.com/galaxy-s6/general/bounty-aosp-source-code-galaxy-s6g920-t3235453

if you could give some tips/ advices we would be very gratefull

thanks in advance and sorry for the ot
[Galaxy Note 4 Original Android Development] r0gger:
Just to give my 5cents about the problem with the missing SuperSU (root).

I tried almost everything without success :

- flashing stock TW 5.1.1 and then from TWRP flashing the rom

- all caches purge from TWRP, format data etc .. permissions fix ..

- flashing again only 5.1.1 BL via Odin - PDA

At the end I decided to try with CWM .. ( [Update][ English version ] ALL- NOTE4 CWM Based Recovery - http://xdaforums.com/note-4/development/note4-cwm-based-recovery-t2911266 ). Must be flashed with Odin - PDA.

After that I reflashed again TeamEOS and finally I can see SuperSU in settings ..

The interesting part - when using both TWRP and CWM I can see a message that "SuperSU" is successfully applied in "/system" .. but for some reason with TWRP supersu just missing ... I think the actual fix is the Odin - PDA recovery flash part.
[Galaxy Note 4 Original Android Development] white7561:
Can any of u that installed this rom can kindly say what bugs left? The music bugs only if u use the stock player. Not musixmatch or such. And camera working fine i guess? But camera settings on google camera is FC. And i kinda wanna know if any bugs left? And are any bugs left? Really really wanna use the rom thx :)

---------- Post added at 08:49 PM ---------- Previous post was at 08:44 PM ----------

And Btw are lte working?
[Galaxy Note 4 Original Android Development] r0gger:
No idea about lte or music, but about BT - confirmed it is busted for calling. Aside these, the ROM is absolute nexus experience! Super fast and smooth. Plenty of free ram, smashing apps caching (not even a sign of TW aggressive background apps killing and then reloading on start) … Finally the phone can breath freely and the OS is a joke for this hardware.. The built in power saver is a brilliant piece of work too!

I'll compare photo quality next few days and will report back (will compare with stock TW 5.1.1 Note 4 exynos).

Many thanks to our dev for this! Extraordinary work for such small team!
[Galaxy Note 4 Original Android Development] sirnatli21:
new update ?
[Galaxy Note 4 Original Android Development] andrew.mackew:
Good question :confused:
[MENTION=3463426]RaymanFX[/MENTION]: hey my man, I don't wanna pisssssss you off.. but.. any news about MM? or even the old and good LP.. By the way, thanks for your excellent job here! :good:
[Galaxy Note 4 Original Android Development] white7561:
So? How about it? Any bugs that noticeable? And how camera. Working same quality?

---------- Post added at 04:07 PM ---------- Previous post was at 03:50 PM ----------

And btw. Are camera like cant connected sometime? And need to reboot to fix it? Cuz i seen that on all cm on exynos . S4 and note 3. So it WILL soo good. If it didnt exist [emoji14]
[Galaxy Note 4 Original Android Development] m.4_ts@yahoo.com:
I found this while searching something..

But i cant download cause its asking to download something else.. Can anybody try if it is working?

http://droidstockrom.com/upgrade-update-samsung-galaxy-note-4.html
[Galaxy Note 4 Original Android Development] suat6027:
Waoowwww... İs it for exynos?
[Galaxy Note 4 Original Android Development] contramundi:
Probably fake. Tried a download link and got something like I needed to fill out a survey.

Also seeing that aosp 5.1 is not really big I reckon 6.0 will not be a huge deal greater in size so I am wondering why you need to download 3 parts.
[Galaxy Note 4 Original Android Development] r0gger:
Camera looks ok. When you switch from photo to video, rec some vid, and then back to photo, it is crashing. But if you reopen after that, it is working again. No need to reboot. First look on photo quality is ok too. But, no slow mo and fast mo vid in AOSP cam.

Google cam can switch between photo-vid-photo without crashing.

Recent/overview is fast here. I can't see ANY lag!

The only bug I found (and not only me) is when receiving a call - around a sec delay until screen on.. But for this one, I can remember from my nexus days, it is usually related with the kernel config (governor). On my nexus when I changed the kernel from one of the custom builds to Franco kernel or stock, the delay just disappeared. I tried to use the "laggy" screen kernel, and when I changed in current governor settings the "initial" cpu mhz and how for long to keep it, the lag disappeared.

It is possible this to be related with the "phone number" resolving from google servers too .. I just guessing.. must be investigated.

The next bug I am waiting for to be fixed (actually one of the reasons to dump one of my nexus phones) - BT calling ..

Heavy gaming is ok too. I am playing WOT Blitz (which is a extremely cpu intensive game) and with settings on max (without shadows), FPS is all the time 50-60.

Fast charging working fine here too! No overheating and charging at max speed almost all the time.

Fake for sure (or this is only for Snapdragon). I can't see the link to xda thread ..

Small update. About the call screen on delay, I just tested with setting "Performance" governor - still laggy screen on. Then I tested with the same governor (performance) and disabled all settings in the "Dialer" "resolve" (numbers). This time, I can say the screen on delay time is reduced much more. So this must be kernel governor + dialer lookup issue. (I am with the stock rom kernel).

Another small update.

I changed back all "Dialer" settings for phone number/s lookup to default - all on.

Then I changed back default kernel governor to "interactive" and then min CPU mhz to "max", and a new call (two tests - one in address book, and another one "unknown"), immediately bring the screen on.

So as a conclusion I can say, this is a "kernel" issue with the initial CPU power.
[Galaxy Note 4 Original Android Development] masaichris:
I have tried your method, it works, it really is a Kernel issue. But whenever is set the frequency with Kernel Auditor, they reset back to atock, so I cant have he settings permanently.

Sent using XDA One from my SM-N910H | TeamEOS AOSP ROM
[Galaxy Note 4 Original Android Development] r0gger:
If you keep it this way, it will exhaust your battery too fast.

Just to report another observation - under long heavy gaming, the video performing worse compared with TW builds. (It is expected because probably the video driver is reverse engineering or from Samsung public sources which is without all of their proprietary optimizations). (As usual... when these huge corporations will learn their lesson)

Cheers
[Galaxy Note 4 Original Android Development] nasirnada:
Gaaps

Dear brother

Could you please give me a gapps link for this rom
[Galaxy Note 4 Original Android Development] r0gger:
[GAPPS][CM11][CM12.x][4.4.4][5.x.x][6.x.x] Delta Gapps With Modular Addons (All DPI)

I'm using the minimal package, then just install from playstore gmail, calendar etc .. Lollipop Base Gapps package for 5.1.1

And xposed :

[OFFICIAL] Xposed for Lollipop [Android 5.0/5.1, v75, 2015/10/07] by rovo89

[EXPERIMENTAL] Unofficial Xposed for Android 5.1 - v74 / 20150911 / SDK22 by romracer
[Galaxy Note 4 Original Android Development] nasirnada:
Thanks quick support.

---------- Post added at 09:44 AM ---------- Previous post was at 09:42 AM ----------

Downloading Lollipop base gapps.
[Galaxy Note 4 Original Android Development] white7561:
Does fastcharge really works?
[Galaxy Note 4 Original Android Development] RaymanFX:
It's probably not a kernel issue, but related to the power saving feature of the power HAL on screen off.

I'll have a look at it, this should be easy to reproduce for me :)

On another note, I'm still working on the M bringup. I also contributed most of my work to CyanogenMod so other people can reuse my repos and contribute easily.

If all goes well, we'll have official CM and EOS builds in the future, so you can choose between those.
[Galaxy Note 4 Original Android Development] white7561:
Btw [MENTION=3463426]RaymanFX[/MENTION] does lte works?
[Galaxy Note 4 Original Android Development] andrew.mackew:
Awesome!!! :good: :good: :good: :good: :good: Thank you!

By the way, is it coming soon? :D At least an old and good LP? :cool:
[Galaxy Note 4 Original Android Development] agentdeep:
New build

https://mega.nz/#!4MoFGbSI!juL3ID2hYwJuZhm7Ka7D3cUYO1kbRTwHeEeyCQzMpQI
[Galaxy Note 4 Original Android Development] emenny81:
What's new ????
[Galaxy Note 4 Original Android Development] white7561:
Yea. What bugs fixed. And im using the rom(not this build) but. Lte working? And fastcharge 9V working tooo? Even when phone off? Thx
[Galaxy Note 4 Original Android Development] masaichris:
New features and bug fixed?? :confused:

Sent using XDA One from my SM-N910H | TeamEOS AOSP ROM
[Galaxy Note 4 Original Android Development] :
Can anyone upload their battery stats like how long does your battery last or how long is your sot?
[Galaxy Note 4 Original Android Development] CLShortFuse:
See here

https://github.com/TeamEOS/device_samsung_treltexx/commits/lp5.1
[Galaxy Note 4 Original Android Development] andrew.mackew:
Is everything working well compared with the last official one?
[Galaxy Note 4 Original Android Development] :
Thanks a lot.... Can you try and build off mm?? from the looks of it in the commits, RIL has been fixed and several other bugs as well
[Galaxy Note 4 Original Android Development] agentdeep:
I just did. Apparently, there are still errors, maybe [MENTION=3463426]RaymanFX[/MENTION] is still fixing it.
[Galaxy Note 4 Original Android Development] white7561:
Im using the official one. Not this new one
[Galaxy Note 4 Original Android Development] APCOtech:
Plz allow PM , Thanx.
[Galaxy Note 4 Original Android Development] white7561:
Please. Anybody.. Who use this rom and use lte. Does LTE working on this rom? Cuz lte is pretty important here. The 3g speed is unbelievable slow. Thx
[Galaxy Note 4 Original Android Development] empat:
Yes, it works fine here. Regards!
[Galaxy Note 4 Original Android Development] white7561:
Btw. What lte band ur country use?

And where do you live
[Galaxy Note 4 Original Android Development] a13x4nd3r:
I think as long as the lte bands are supported by the device it will work regardless of cm / touchwiz. Does the lte works on your device in touchwiz?

Not related the the people you quoted but i'm in china and using unicom, they are using band 3 fdd lte if i'm not mistaken. I tried also using other operator from indonesia namely xl and telkomsel and they work just as fine..

Regarding battery life.. I get 4 hours sot EASILY with this rom with mostly lte browsing, many wakelock from chinese social media apps, and one year old battery which died at 15 percent already. Best battery life out of any rom. Also one of the smoothest out there.
[Galaxy Note 4 Original Android Development] :
I think you should check send even if not in your contact list below the message box when you want to send.

---------- Post added at 04:26 PM ---------- Previous post was at 04:25 PM ----------

I know that it's the best rom in terms of battery. I asked if anyone could upload their sot
[Galaxy Note 4 Original Android Development] gusmao100:
Can someone pass me the link gapps :confused:
[Galaxy Note 4 Original Android Development] ogo2012:
The choice: Gapps / Gapps / Gapps. :)
[Galaxy Note 4 Original Android Development] r0gger:
Hi folks

By any chance anyone to know is the current cam driver/implementation support slow motion video, and if yes what camera software can be used for that?
[Galaxy Note 4 Original Android Development] ogo2012:
Hi. Someone tested assembly 20151106? Reviews.
[Galaxy Note 4 Original Android Development] CLShortFuse:
If you're coming from 10/15, it adds better support for low power (standby), some radio commands, and it downgrades OpenGL to 3.0

https://github.com/TeamEOS/device_s...a222af1d3309be7280ccf9085ad07ae9f79a9...lp5.1
[Galaxy Note 4 Original Android Development] white7561:
Why downgrade to es 3.0 from 3.1?
[Galaxy Note 4 Original Android Development] slowik515:
I've been using it for a few hours. Everything works fine and crash when switching photos and videos in camera seems to be fixed. I am unable to check other known bugs for now.

Wysłane z mojego SM-N910C przy użyciu Tapatalka
[Galaxy Note 4 Original Android Development] andrew.mackew:
Additionally, the newest build has a smaller footprint if we compare with the previous one. Excellent job [MENTION=3463426]RaymanFX[/MENTION] , thanks for your great work!
[Galaxy Note 4 Original Android Development] CLShortFuse:
The cache partition is fixed to 1gb now
[Galaxy Note 4 Original Android Development] ilker4fun:
Can I use custom kernel like suemax or talexop in this rom?

I forgot to ask:Can I use samsung apps like contact or music?If I copy this file other samsung custom rom and push them to system,is it work?
[Galaxy Note 4 Original Android Development] dannyb0i:
As far as I know most Samsung apps rely on TW framework so most likely won't work...
[Galaxy Note 4 Original Android Development] ilker4fun:
Deleted
[Galaxy Note 4 Original Android Development] emenny81:
Any news on Bluetooth with this new build
[Galaxy Note 4 Original Android Development] empat:
Suemax and talexop are designed for TW, you need to use a kernel designed for AOSP. Here on XDA, besides the original kernel, the only other option is Googymax, although it is no longer supported.

Regards!
[Galaxy Note 4 Original Android Development] Ather:
[MENTION=3463426]RaymanFX[/MENTION] samsung started releasing exynos sources in github!!

http://git.insignal.co.kr/
[Galaxy Note 4 Original Android Development] white7561:
Marshmallow
[Galaxy Note 4 Original Android Development] ilker4fun:
Guys please can somebody tell me where is increasing touch sensitivity option? I look everywhere but I can't find it. Is it missing?
[Galaxy Note 4 Original Android Development] Ranomez:
AFAIK that is a Samsung (TW) ROM only option, never seen it on AOSP on any of my devices.
[Galaxy Note 4 Original Android Development] Ausboy 2011:
Isnt it called glove mode? Thought it was on aosp
[Galaxy Note 4 Original Android Development] travis82:
https://github.com/CyanogenMod/android_device_samsung_treltexx

anyone can compile an alpha build for us? Than we can help him out with debugging and dmsg logs
[Galaxy Note 4 Original Android Development] vacs03:
today I updated to the latest build (20151106) and so far the only issue is that the no sound in call is back after reboot and until I make any sound (example with the volume rockers)...on the prevuis build 20151015 I had no issues, oh and yeah, I'm on the COI4 modem...any fixes or links to newer modems?

edit: sometimes I can't even make a call, it says right away "call ended"
[Galaxy Note 4 Original Android Development] :
I knew that fingerprint wouldn't work on 6.0 aosp but to all who did, Snap variants reported that cm13's fingerprint doesnt support our note's sensor
[Galaxy Note 4 Original Android Development] agentdeep:
I will try..
[Galaxy Note 4 Original Android Development] :
Thanks a lot man. I tried like a billion times before and faced too many errors that couldn't figure out how to solve
[Galaxy Note 4 Original Android Development] gekkehenkie11:
Hey rayman you never confirmed that your baseband is the same version as the kernel sources. I think this might be number one cause of a crashing modem... And also in this case, it would make sense that it's that. Cause what's happening here is:

As you can see in the modem kernel code, that pa stands for "Phone Active". An IRQ returns with pa = 0, telling the modem driver that the radio is not active anymore and thus it sets the modem to state 2 (crashed).

So in other words ... modem boots, modem crashes. Not much in between that you could have done wrong ... It almost has to be a wrong modem that you're booting.

*OR*

or it must be related to that USB stuff before it ... that when the modem is up (when that IRQ returns with pa=1), the USB stuff should be up too and that it crashes because that's not the case ... I guess that could make sense too ... going to look into that ;)

*EDIT* actually I think that would make sense ... Cause it DOES get to that PA status 1 first (as you see in the above) ... but then stock continues with:

cdc_modem 1-2:1.2: usb_probe_interface

whereas CM12 quickly switches to PA status 0 again ... So to me that seems like the modem DOES finish the boot, send IRQ callback with PA=1 and then crashes for some reason, which might be related to that USBprobe .... looking into that again ;)

Yes. Fact is that in stock, before the pa gets to 1, the USB modem has been configured:

15.064227] [c2] usb 1-2: New USB device found, idVendor=04cc, idProduct=2342
<6>[ 15.064239] [c2] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
<6>[ 15.064250] [c2] usb 1-2: Product: ST-Ericsson Thor IPC-Custom

While in CM12 the pa gets to 1 while this hasn't happened yet. I think this might be the reason that it crashes ... So then the next question would be: how do we make the USB detect the modem ...
[Galaxy Note 4 Original Android Development] gekkehenkie11:
[MENTION=3463426]RaymanFX[/MENTION]: So:

1) Check if baseband version matches kernel. If it does:

2) In that case I'd say that the modem crash is related to the USB device not being up. Why that is ? It's hard to say at this moment. In that case it might be worth to have mif_debug print something (mif_debug just is pr_debug, so I think you'd need to change the modem makefile, like this: https://www.kernel.org/doc/local/pr_debug.txt). Then I'd probably try to build the samsung kernel like you've downloaded it, also change that mif_debug to print something and then use this kernel with your stock ROM. And then compare dmesg output again ... Cause in the current dmesg it's hard to see what's going wrong like this.