yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 4 Original Android Development] empat:
Use this app: http://xdaforums.com/showthread.php?t=2447534. It works with our device. Regards!
[Galaxy Note 4 Original Android Development] jiansheng:
Isn't that a Qualcomm based Galaxy S4? Would it work on an Exynos based N910C? Also, do I have to root my device that's currently running on 5.1.1?
[Galaxy Note 4 Original Android Development] agentdeep:
This is not the appropriate place to ask questions about dual boot.

Go to that thread and ask there. And yes, it is working in N910C and yes, you need root to dual boot.

Now enough and ask question to that thread, this is EOS development...
[Galaxy Note 4 Original Android Development] ogo2012:
Available link to download a new build. Try.

Some news here and here.
[Galaxy Note 4 Original Android Development] agentdeep:
I hope the camera photo quality is fixed on this build.

I will try.

EDIT: Photo quality is good now
[Galaxy Note 4 Original Android Development] doctor78SI:
Anyone can confirm BT calling is fixed?
[Galaxy Note 4 Original Android Development] jiansheng:
I'm sorry. I shall ask there then. I shall discontinue this topic. Thanks anyways! ?

Also, may I ask what are the current bugs and issues for the latest 20150906 build ?
[Galaxy Note 4 Original Android Development] masaichris:
So far, what can be confirmed (from my end) is S-Pen works fine in both portrait and Landscape modes & Camera is working fine on the 20150906 build.

Sent via Tapatalk from SM-N910H | TeamEOS AOSP Rom
[Galaxy Note 4 Original Android Development] mailme2nani:
Hey I'm seeing a weird issue, when I open my text message app, and open any text msg, it is automatically dialing to that contact.

Anyone having this issue??
[Galaxy Note 4 Original Android Development] masaichris:
Go into settings of the Messaging App and disable Smart Call under extra settings.

Sent via Tapatalk from SM-N910H | TeamEOS AOSP Rom
[Galaxy Note 4 Original Android Development] mailme2nani:
Thanks, I'm able to view my texts now.

But I also use Smart Call, hope this bug will be solved son.
[Galaxy Note 4 Original Android Development] white7561:
Sorry for asking. New on this thread. So what didnt working in this rom? Or didnt work well as on stock? And any method to get fingerprint working on aosp? Thx :)
[Galaxy Note 4 Original Android Development] jiansheng:
Can you elaborate on the camera? What do you mean by working? ?
[Galaxy Note 4 Original Android Development] andrew.mackew:
As far as I know, there is no method to have fingerprint to work until Android M, which will probably gonna get it embed..

Furthermore, the rom is pretty stable.. It have a few issues with Bluetooth.. Actually, the first OP post has a summarized list of what is or not working.
[Galaxy Note 4 Original Android Development] agentdeep:
Video recording is broken :(
[Galaxy Note 4 Original Android Development] CLShortFuse:
Landscape works with SPen.

Twitch video works (doesn't hang)

SPen still doesn't work with overview button in either orientation
[Galaxy Note 4 Original Android Development] masaichris:
I forgot to check Video recording. It's broken (camera crashes when I press record)

Sent via Tapatalk from SM-N910H | TeamEOS AOSP Rom
[Galaxy Note 4 Original Android Development] jiansheng:
Thanks! ?
[Galaxy Note 4 Original Android Development] slowik515:
I just want to add that default camera app does not react when I touch record button (just nothing happens) but Google Camera crashes in the same scenario. Of course this is just my case.

Wysłane z mojego SM-N910C przy użyciu Tapatalka
[Galaxy Note 4 Original Android Development] Ali_0781:
update thread plz
[Galaxy Note 4 Original Android Development] andrew.mackew:
After [MENTION=3463426]RaymanFX[/MENTION] merged 5.1.1 source into his source seems that maybe something is missing and it's probably resulting in camera crashes. When [MENTION=3463426]RaymanFX[/MENTION] finished to merge 5.1.1 sources these and other problems will probably fade away. Hopefully our beloved and skilled dev [MENTION=3463426]RaymanFX[/MENTION] will fix it soon. Thanks for his excellent work!
[Galaxy Note 4 Original Android Development] white7561:
Hey. Are google camera hdr is the same quality with tw one? And can we record FHD60FPS on google camera? Or any way to port them? Thx
[Galaxy Note 4 Original Android Development] leondestiny:
getting random reboots on latest build.. dont know if it is because of googy kernel :l anyone else having this issue?
[Galaxy Note 4 Original Android Development] empat:
Hi! No reboots here, also using googy kernel. Regards!
[Galaxy Note 4 Original Android Development] leondestiny:
thats weird..

i reflashed with wiping data and kept stock kernel and now no random reboots.
[Galaxy Note 4 Original Android Development] :
Can anyone confirm if android wear devices such as moto 360 work with this rom
[Galaxy Note 4 Original Android Development] x7uc0x:
around 1 month ago when I was trying this rom, it was working.
[Galaxy Note 4 Original Android Development] jackspadeza:
Random reboots probably because of Privacy Guard, i experienced this as well. Reset Privacy Guard, reboots will be gone :)!
[Galaxy Note 4 Original Android Development] masaichris:
On the Latest Build 20150906, the Googymax kernel breaks Proximity Sensor (Screens remain on during calls), I checked with Stock kernel it works but once I flash this kernel it doesn't. I didnt notice any random reboots just the proximity sensor. Anyone else noticed this?
[Galaxy Note 4 Original Android Development] slowik515:
I use Privacy Guard for a few months without any issues (including this build) and I do not have any random reboots. So I don't think that that's the case. But good for you if it helps.
[Galaxy Note 4 Original Android Development] empat:
Hi! Yes, I have the same happening here. Regards!
[Galaxy Note 4 Original Android Development] S.Y.:
I've never had the reboots thing, but freezes requiring a battery pull happen roughly every other day.

And is anybody else getting this: I enabled Fling, which was supposed to disable the Overview and Back buttons. It did indeed, but when I rebooted the phone, they started working again.
[Galaxy Note 4 Original Android Development] sa3d12:
Flashed the latest build 20150906 today and i have to say it is great..... great performance no lags no freeze no random reboots ..great battery life and ram management and its very stable though ... Ofcource the known bugs which is video recording is the only problem so far .....thanks for your effort !
[Galaxy Note 4 Original Android Development] leondestiny:
same here , after wiping everything kept everything stock and installed my apps and so far its very smooth and good to use as dailydriver.

cm >>>>>>>>>>>>>>>>> tw.
[Galaxy Note 4 Original Android Development] Skreedi:
Well I spammed other threads in S6 section but I might try here aswell. How was the CM possible on Note 4 Exynos? Many people are waiting for miracle on S6/S6Edge and I wonder if mainating on Exynos 5433 is easier than on 7420 or there are some sources for this SoC? I'm just curious and I'm thinking about S6 but honestly I'm not sure if I can live without AOSP/CM magic :P

This time in correct thread! xd
[Galaxy Note 4 Original Android Development] empat:
The miracle was possible thanks to an angel, known as [MENTION=3463426]RaymanFX[/MENTION]...
[Galaxy Note 4 Original Android Development] calj17:
We got together and raised funds to buy Raymanfx a note 4 exynos unit so that he build CM12.1 for us. You guys could do the same for s6. Talk to him after

Enviado de meu SM-N910C usando Tapatalk
[Galaxy Note 4 Original Android Development] Skreedi:
I know about that epic magician but I just wonder how. I know about fundraiser but I'm curious about software side magic. It's based on some sources or mostly everything is written from scratch? Also what can hold devs on Exynos 7420, are those chips vary that much that nothing can be taken/or be used as some kind of example from Exynos 5433?
[Galaxy Note 4 Original Android Development] gekkehenkie11:
There are no sources for the 64 bits versions and from what I understood it's very unlikely that they will be released. So AOSP might never happen for S6 and the note 5.
[Galaxy Note 4 Original Android Development] TANKRED_ENDURES:
I wander maybe Rayman's exynos 5433 sources can be used to make 32bit build for s6
[Galaxy Note 4 Original Android Development] leondestiny:
phones without CM makes them garbage for me ..

i had the exynos s5 and swapped it with a snappy one just for CM.

and atm. i have the exynos note4 but luckily we have this stable CM build which is very cool and makes me keep my n4.

when i checked the dev. section of the s6 and seeing no CM ever making it on the device totally killed the s6 for me,

so yeah the n5 seems to be similar with the s6 so meh.

will wait and see what the s7/n6 will be like if Sammy still makes it Exynos locking CM for it , i will defintely move to a different Smartphone.

preferablly the NEXUS series. why ? hint : CM <3

so yeah either a nexus 6 or nexus 5 2015 < i will get one of these.
[Galaxy Note 4 Original Android Development] mailme2nani:
Regular hangs are killing me. So frustrating. Trying to wipe everything and install a fresh copy, but can't get a GApps suitable. Can someone suggest me a link for GApps.

Need to do a hard reset eveytime when the phone hangs :confused:
[Galaxy Note 4 Original Android Development] RaymanFX:
My Exynos 5433 work is split into several parts:

1) The device tree.

I started this one from scratch, because I didn't find any reference sources I considered a good base. I'm working together with the Galaxy Alpha maintainer right now (Exynos 5430) to continuously improve our trees, and we're constantly cherry-picking fixes from each other.

2) The kernel.

The situation with this one is similar to the device tree. I'm constantly working on improving it (which right now means bringing in the latest Linux mainline patches for our kernel version - 3.10.y) and I want to keep it clean to avoid headaches during the more important platform development (which means I'm not messing around with pointless overclocking or undervolting).

3) The hardware repos (aka HALs aka drivers).

I basically took the open source repositories from Insignal and added support for the Exynos5433 chipset to it.

In this process, numerous people (including me) were working together with CM platform maintainers to review, share and improve our code.

After all though, I'm the only one working on Exynos5433 specific support.

Looking towards the Galaxy S6, there are a few points to watch out for.

First of all, the Exynos 7420, which is being used in the S6, is essentially just a rebranded 5433, so the two SoCs are almost identical.

The only real difference here is software - Samsung decided to give the S6 the 64bit treatment, while the Note 4 was left out (for whatever reasons).

Now the difficulty in getting AOSP on the S6 is essentially fixing the hardware repos for 64bit support. This could very well be a long road to go and hard to debug. What would probably yield faster success is trying to get a 32bit build first, fixing up the blocking issues (audio, etc) and then taking a look towards 64bit platform support. From what I know of my own experiences with 64bit devices, each should be able to run 32bit builds just fine because they all ship with multilib support.

I was contacted by a developer working on the S6 (Brandon Mc Ansh), who sadly didn't have the device available to him all the time, thus not being limited in his development activities. The last thing I heard from him was that he wanted to give a full 32bit build a shot, after we discussed the matter for a bit. other than that, I don't know of anybody working on an AOSP implementation for the Galaxy S6 and upwards Exynos devices.
[Galaxy Note 4 Original Android Development] TANKRED_ENDURES:
Hi, thnanks for your great work. Do you have any plans to add CPU and GPU throttling to kernel, cause without it devices with low and medium ASV overheats heavely under load, especially in games. CPU temp rises up to 100C within fiave minutes of playing. And no plans to add kernel tweaking support in future?
[Galaxy Note 4 Original Android Development] gekkehenkie11:
I'd like to add my 2 cents here. For the 910F I found out that the main throttle code is inside the java framework. Of course CM itself doesnt feature throttling. Hence that's indeed the reason that without additional throttling, the device would get very hot. I bet the same happens on the Exynos.

I solved this by implementing faux'es intellithermal in the kernel which seems to work fairly well

---------- Post added at 05:23 PM ---------- Previous post was at 05:19 PM ----------

I think it's a dead end here for CM on Samsung devices. Maybe someone will take up the challenge but it's going to be a damn difficult road with lots of problems ahead.

Me, I'm probably just going to kiss samsung goodbye after the Note 4. I'm just hoping really hard the new Nexus 6 is going to be any good ;)
[Galaxy Note 4 Original Android Development] calj17:
I AM SURE THAT IF GEKKEHENKIE11 JOIN RAYMANFX THEY TOGETHER CAN BRING CM12.1/13 TO NOTE 5 EXYNOS OCTA 64BITS. IF WE RAISE FUNDS AGAIN TO OTHER DEVICE

Enviado de meu SM-P601 usando Tapatalk
[Galaxy Note 4 Original Android Development] RaymanFX:
Hey, I think we should be able to implement this in the power HAL actually. And if not, we can always write a daemon for it like QC's mpdec/thermald.

Do you have the exact location of the throttling implementation in the frameworks?

I'd probably give it a shot, just for the fun of it.

When I was donated the Note 4, I told people I might not be able to pull it off (because of lacking resources for the Exynos SoC), but I also told them I'd throw everything I got at it. I'm sure (and I hope) people know and accept the insecurity of possibly never running an AOSP ROM on their device, even if they donate one to a developer. In the end, we're not getting paid for this (we're given the device 'for free' at the very best), so it should be clear to everyone there's always a chance of success, but no guarantee, let alone an ETA.
[Galaxy Note 4 Original Android Development] doctor78SI:
Me 2 was thinking to abandon Sammy bandwagon but i must admit the ne s6 edge plus looks very tempting. Also I dont like that the new Nexus 6 will be made by Huawei. And LG's Nexus 5 is not going to be proper flagship so I am deciding between new sammy or new iphone 6s plus.
[Galaxy Note 4 Original Android Development] joelteixeira:
For one, I'm forever grateful for the brilliant work done here. But as soon as nexus 5 (2015) hit the market I'll get one. Surely a downgrade in a few aspects I know. But I'm ready for some sacrifices to get a device really developer friendly. I said the same when not long time ago I got a galaxy s4 and note 4 captivate me. I won't let this happen again.
[Galaxy Note 4 Original Android Development] doctor78SI:
If Nexus 5 2015 inherita the awsome camera from G4 then I will consider it ofc. But it does not look like it will be able to compete with flagships. And Nexus 6 will be Huawei made and 2 big imo.
[Galaxy Note 4 Original Android Development] joelteixeira:
Agreed, won't be as good as G4 or other flagships, but if rumors are right it will include OIS and laser focus. Can't be a bad camera just because of 12mpix. IMO :)

Edit: sorry about the off topic guys, ending here.
[Galaxy Note 4 Original Android Development] gekkehenkie11:
Hey mate, yeah I remembered I posted about this, just searched and found my post detailing all this. Here it is: http://xdaforums.com/note-4/orig-de...-910f-910g-t3046965/post61458997#post61458997

The sysfs node might be different for Exynos but my best guess is that it works similar (user space java framework writing to a similar kernel sysfs node)

Re-reading my post, it's probably another piece of java code that uses that CustomFrequencyManagerService.java code to manipulate the cpu frequency based on the temp, but that should be easy to find. I dont remember 100% but I think I didnt look into all that, I think I remember that I just saw that that sysfs node was being manipulated from user space, based on the temperature and this was the only code that accesses that node.

Amen. You did an incredible job on this device already, hats off to you sir !
[Galaxy Note 4 Original Android Development] calj17:
Hey gekkehenkie11 you could join raymanfx for future ports of cm13 for note 5 exynos octa 64 bits. You guys together are capable of solving anything. Congratulations for both of you

Enviado de meu SM-P601 usando Tapatalk
[Galaxy Note 4 Original Android Development] TANKRED_ENDURES:
As far as I know AOSP GOOGY MAX kernel adds throttling to this rom, but he no longer maintains it
[Galaxy Note 4 Original Android Development] leondestiny:
i have to agree with you , i am sick of Sammy .. especially with their new phones :l no cm no go for me ..

i want pure stock android cause thats what i love the most, and seeing the Nexus having the best dev. support urges me to get Nexus phones from now on..

so i will jump away from Sammy and will move on to the Nexus series..

preferably might get either a Nexus 6 or the new Nexus 5 2015..

( The latest build of CM on this thread is simply amazing, this is the reason why i love my exynos n4 atm.!! so a huge thanks to the team here! Sorry for the offtopic talk) <<<<< gave my feedback on this Rom , it is beast <3
[Galaxy Note 4 Original Android Development] :
Can anybody confirm that bluetooth works perfectly with Android wear devices? I just bought a moto 360 and it keeps disconnecting it barely even connects to my phone but it is added in my android wear app
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] QA Bot:
Q&A for [ROM][4.2.2]{I9300}ColorOS 2.0 for GALAXY S3

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for [ROM][4.2.2]{I9300}ColorOS 2.0 for GALAXY S3. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] Zax013:
Are you came from Mars? This thread already exist!!
[XDA Assist] XDA Visitor:
there is some kinda way to change th imei?
[XDA Assist] dagger:
Yes you can by using XPrivacy xposed moule, but i believe that is illegal in some countries.

So please make it sure before using it. :)
[iPAQ rw6828, XDA Atom General] PrEEcY:
Hi i've sync'd my Atom with a Plantronics bluetooth headset. The problem i have is... i tend to leave the headset in the car which is usually on my drive way or in the office car park. Whenever i receive/make calls from the office or home (on the atom without the headset) i can not hear the other person as the atom still thinks im using my headset since the car is near by. The headset and atom must be still in bluetooth distance from each other as i can still see the headset symbol on the atom. The obvious thing to do would be to turn off the headset however i forget to do this. Is there any way to use the headset and still have the speaker active on the atom at the same time ?

thanks in advance
[Wear OS General] akware:
mod edit: Please do not post paid apps on XDA
[Galaxy Tab Pro 12.2, 10.1, 8.4 Q&A, Help & Trouble] pego99:
This is very annoying. I open the magnetic cover swipe to unlock and touch any icon on the home screen and nothing happens but in a few seconds the unit restarts and then works ok. Has anyone seen this problem and know of a solution. The unit was rooted with towelroot.com but I removed the root with the su manager.
[Xperia Z3 Q&A, Help & Troubleshooting] toledo22:
A big advantage that I realized on Moto G above the Xperia Z3 was the dialing function in contact with more than one phone number . Whenever I call a contact, it apears a box asking me wich SIM I'd like to use to call that contact and a box underside to save that choice. So I'll never need to select the SIM i'd like to use for that contact. Anyone knows an app or a mod that do that?
[Xperia Z3 Q&A, Help & Troubleshooting] unmaskedfalesh:
If u talking about z3 dual then the option while dialing there are 2 dialer icon..fr calling
[Xperia Z3 Q&A, Help & Troubleshooting] toledo22:
Yeah, but only if you use the dialer, if you dial by the contacts it will show a box asking which SIM you want to make the call. It doesn't have the option to memorize your choice.
[Xperia Z3 Q&A, Help & Troubleshooting] toledo22:
Waiting anxiously for Android 5.1 that will have this resource.
[Xperia Z3 Q&A, Help & Troubleshooting] slonn:
Pixelphone Pro does that.
[Xperia Z3 Q&A, Help & Troubleshooting] toledo22:
I discovered an app that does that (dual sim selector) but it doesn't has a way to remove the the native window to select the Sim.
[Xperia Z3 Q&A, Help & Troubleshooting] browngeek:
Hi. I had asked about this previously and you had suggested Pixelphone Pro. I'm trying out their app PP - dialer and contacts: https://play.google.com/store/apps/details?id=pixelrush.xphonefree&hl=en which I presume will have the same functionality. While it does have dual sim ability, when using the app what I find is that when you select a contact it still requires you to select sim1 or sim2 and there is no way of saving a default. The call then goes through the stock dialler, rather than the Pixelphone dialler. I've played around with the dual sim settings, but to no avail.

Am I missing something there?
[Xperia Z3 Q&A, Help & Troubleshooting] slonn:
If you use the stock Contacts app then yes, it will prompt you every time. But if you use Pixelphone's contact app then you will only get prompted the first time where you have the option to choose a sim to use and tick the box to remember that option.
[Xperia Z3 Q&A, Help & Troubleshooting] browngeek:
Will give it another go, but I remember when I tried it last time, from the Pixelphone's dialler (which I presume is connected to the Pixelphone contact app), I was prompted for which sim (i.e. as per using the standard dialler) and then the call was made via the sony dialler app.

Has anyone else tried using Pixelphone?
[Xperia Z3 Q&A, Help & Troubleshooting] slonn:
Odd...

For me only when calling a number I haven't called before via Pixelphone does the app prompt to choose a sim. I then choose the sim and tick the box to remember the choice and then it goes to the default dialer (and calls the number) . The next time I call the same number via pixelphone it just goes to the native dialer and initiates the call but no sim prompt appears.
[Xperia Z3 Q&A, Help & Troubleshooting] browngeek:
From the other thread (i.e. the one I am the OP on) I think you mention you are not on Lollipop at the moment. So I think Sony have tweaked their settings for Lollipop so at the moment pixelphone won't work with Lollipop like we want it to.
[Xperia Z3 Q&A, Help & Troubleshooting] slonn:
Pixelphone has been updated over the past few days. Perhaps you can give it another try?
[Xperia Z3 Q&A, Help & Troubleshooting] browngeek:
Thanks for that. So Pixelphone's dual sim selection is based on the "Dual SIM Selector" section. The same dev also has an app called "Dual SIM Selector" which was updated on 1 May: https://play.google.com/store/apps/details?id=net.pixelrush.dualsimselectortrial.

I downloaded the "Dual SIM Selector" app and it works a treat. Now debate, do I get the full dialler or just stick to the sim selector app. They are both priced the same - US$2.99.
[Xperia Z3 Q&A, Help & Troubleshooting] slonn:
I went for the full version of the dialer because it works great. First time I found a dialer that fit what I wanted. Also, supporting the dev is always a good...

That being said I found a bug where the dialer shows incorrect favourites. Emailed the dev about it and hope it gets fixed soon.