Hi,
I was hoping to get some clarification about what is going on with the camera on Android 6.
I think what from reading so far the camera needs some closed source blob, that is kind of like a driver for it, specifically for one version of the Android Kernel.
And this blob must exist for CAF/Qualcomm 3.4 Kernel used in the Stock rom and lately also Sony 3.10 Kernel used in the 5.1 AOSP build?
What I do not get is, why can none of the existing blobs not be used with the Kernel Android 6.0 AOSP requires.
And also: Is this just a matter of time until someone gets it working, or are we totally dependant on Sony to release the blob for the new kernel, or camera will never work.
Any insight would be nice
user822 said:
Hi,
I was hoping to get some clarification about what is going on with the camera on Android 6.
I think what from reading so far the camera needs some closed source blob, that is kind of like a driver for it, specifically for one version of the Android Kernel.
And this blob must exist for CAF/Qualcomm 3.4 Kernel used in the Stock rom and lately also Sony 3.10 Kernel used in the 5.1 AOSP build?
What I do not get is, why can none of the existing blobs not be used with the Kernel Android 6.0 AOSP requires.
And also: Is this just a matter of time until someone gets it working, or are we totally dependant on Sony to release the blob for the new kernel, or camera will never work.
Any insight would be nice
Click to expand...
Click to collapse
Hi,
first of all - sony released MM (6.0) blobs for 3.10 kernel on 2. February, so there are all things that developers need from sony. (including camera)
Existing blobs can't be used because all custom roms were using very old camera blob from 4.3 Jelly bean stock - newer blobs have some (DRM) protection on them so that they cannot be used. And unfortunately this old camera blob is not usable on MM, so CM team decided to wait for sony to release open source (they just call it open source, blobs are still closed source, but they are compatible with AOSP, unlike stock ones) one.
And why it still isn't working? Because there is still a lot of work ongoing on sonyxperiadev github, so I guess CM is waiting till the changes are complete.
Last thing I want to say - I'm not a developer, so I may be wrong. This is just how I understand the situation there.
SuperLamic said:
Hi,
first of all - sony released MM (6.0) blobs for 3.10 kernel on 2. February, so there are all things that developers need from sony. (including camera)
Existing blobs can't be used because all custom roms were using very old camera blob from 4.3 Jelly bean stock - newer blobs have some (DRM) protection on them so that they cannot be used. And unfortunately this old camera blob is not usable on MM, so CM team decided to wait for sony to release open source (they just call it open source, blobs are still closed source, but they are compatible with AOSP, unlike stock ones) one.
And why it still isn't working? Because there is still a lot of work ongoing on sonyxperiadev github, so I guess CM is waiting till the changes are complete.
Last thing I want to say - I'm not a developer, so I may be wrong. This is just how I understand the situation there.
Click to expand...
Click to collapse
I don't think that's entirely correct. Sony released blobs have never worked for AOSP camera. They have also not released anything for 3.10 kernel. I also don't think that jb blobs were used in up to LP5.1.1, as 4.3 camera never fully worked. If you look at CM gerrit, they say that they were able to have camera work once on MM with 3.4 kernel, but then they couldn't repeat it. Then, out of frustration and because they know Sonyxpdevs have abandoned 3.4 for good, CM have decided to switch to 3.10 kernel and wait for Sony to fix it. Good luck: Sonyxpdevs couldn't have camera work on ANY aosp rom...
So, the answer is, in my view: (i) potentially, we can have camera in MM with 3.4 kernel, but nobody is working on it in favor of 3.10; and (ii) not in our lifetime on 3.10. This is a pity and really has very little sense: Both 3.4 and 3.10 are hopelessly outdated (Linux is using 4.x already), so, why not to try to have it with 3.4, which worked fine up to MM? One of the reasons is that many developers just don't like CM (jealousy?), and CM isn't going to lift a finger for 2 devices (Z1 and Z1c), which they consider legacy devices. So, no luck. But in my view, M is crap (LP is crap too) LOL... Kitkat is still a lot more preferable...
optimumpro said:
I don't think that's entirely correct. Sony released blobs have never worked for AOSP camera. They have also not released anything for 3.10 kernel. I also don't think that jb blobs were used in up to LP5.1.1, as 4.3 camera never fully worked. If you look at CM gerrit, they say that they were able to have camera work once on MM with 3.4 kernel, but then they couldn't repeat it. Then, out of frustration and because they know Sonyxpdevs have abandoned 3.4 for good, CM have decided to switch to 3.10 kernel and wait for Sony to fix it. Good luck: Sonyxpdevs couldn't have camera work on ANY aosp rom...
So, the answer is, in my view: (i) potentially, we can have camera in MM with 3.4 kernel, but nobody is working on it in favor of 3.10; and (ii) not in our lifetime on 3.10. This is a pity and really has very little sense: Both 3.4 and 3.10 are hopelessly outdated (Linux is using 4.x already), so, why not to try to have it with 3.4, which worked fine up to MM? One of the reasons is that many developers just don't like CM (jealousy?), and CM isn't going to lift a finger for 2 devices (Z1 and Z1c), which they consider legacy devices. So, no luck. But in my view, M is crap (LP is crap too) LOL... Kitkat is still a lot more preferable...
Click to expand...
Click to collapse
well, you're not watching community here so much alviteri is woring on Z1 even he doesn't have the device and here you go.
And yes, they made camera working like two months ago on Lollipop on 3.10 kernel with aosp blobs and now - a few days ago even on marshmallow. It's only matter of time when it will work.
Check this: https://github.com/SonyAosp (there you have blobs and everything from alviteri)
SuperLamic said:
well, you're not watching community here so much alviteri is woring on Z1 even he doesn't have the device and here you go.
And yes, they made camera working like two months ago on Lollipop on 3.10 kernel with aosp blobs and now - a few days ago even on marshmallow. It's only matter of time when it will work.
Check this: https://github.com/SonyAosp (there you have blobs and everything from alviteri)
Click to expand...
Click to collapse
Well. As I said before, no one is working on making camera work with 3.4. Also, as far as blobs, according to davitery, "there is nothing to do" because of Sony: http://forum.xda-developers.com/showpost.php?p=64582482&postcount=33
optimumpro said:
Well. As I said before, no one is working on making camera work with 3.4. Also, as far as blobs, according to davitery, "there is nothing to do" because of Sony: http://forum.xda-developers.com/showpost.php?p=64582482&postcount=33
Click to expand...
Click to collapse
yes, this post was right on 31st December, but now is 6th February and the blobs ARE now available as I said before (and you can see screen with working camera in my previous post)
https://github.com/SonyAosp/platform_vendor_sony/commit/4f7409446779f371973035720935c36dbd09d7cc
SuperLamic said:
yes, this post was right on 31st December, but now is 6th February and the blobs ARE now available as I said before (and you can see screen with working camera in my previous post)
https://github.com/SonyAosp/platform_vendor_sony/commit/4f7409446779f371973035720935c36dbd09d7cc
Click to expand...
Click to collapse
I think the picture about camera is for Z3, which is not rhine. Also, if you look at the new blobs, there is nothing new for rhine devices; they just took out some older binaries, which are useless anyway. And this is consistent with Sony saying there won't be M for Z1. We will see, but I am not holding my breath.
Edit: I just downloaded the latest M blobs and everything in rhine and honami folders is dated August 2015. So, there is definitely nothing new for our device...
optimumpro said:
I think the picture about camera is for Z3, which is not rhine. Also, if you look at the new blobs, there is nothing new for rhine devices; they just took out some older binaries, which are useless anyway. And this is consistent with Sony saying there won't be M for Z1. We will see, but I am not holding my breath.
Edit: I just downloaded the latest M blobs and everything in rhine and honami folders is dated August 2015. So, there is definitely nothing new for our device...
Click to expand...
Click to collapse
Well, I didn't test it, so I don't know. But does it even make sense to release camera for Z3 and not for Z1 in the same package?
Anyway why do you think that they are useless? I tried that crdroid rom and it's not that bad (except for touchscreen driver and camera). And AOSP camera was definitely working on Lollipop (I personally tried it on build from erikcas), so it wouldn't make sense not to update it too when it requires only update their wrapper - and they can even use the one from Z3. (I don't really understand CM developers why they can't use Lollipop camera AOSP blob with simple wrapper to fit on Marshmallow, but I understand that it's more work and it's easier to wait)
I'm not that optimistic about Marshmallow officially, but I do think that they will release at least a bit usable blobs.
SuperLamic said:
Well, I didn't test it, so I don't know. But does it even make sense to release camera for Z3 and not for Z1 in the same package?
Anyway why do you think that they are useless? I tried that crdroid rom and it's not that bad (except for touchscreen driver and camera). And AOSP camera was definitely working on Lollipop (I personally tried it on build from erikcas), so it wouldn't make sense not to update it too when it requires only update their wrapper - and they can even use the one from Z3. (I don't really understand CM developers why they can't use Lollipop camera AOSP blob with simple wrapper to fit on Marshmallow, but I understand that it's more work and it's easier to wait)
I'm not that optimistic about Marshmallow officially, but I do think that they will release at least a bit usable blobs.
Click to expand...
Click to collapse
"make sense to release camera for Z3 and not for Z1 in the same package"
No, it doesn't, because Sony engineers do work on Z3 and NOT on rhine (Z1 and Z1c) devices.
You are confusing several things: the fact that camera worked with LP AOSP has nothing to do with M blobs, but rather the fact that Sony released a crippled AOSP camera for lollipop. This camera has nothing to do with M. And note, Sony released LP camera only after Android has moved to M.
Now, about M. The reason I think real blobs are not coming is that first Sony engineers must create stock M for rhine devices (and it ain't coming, because Sony said so). Then, they dumb stock down for custom roms. That's the usual way. But because M isn't coming to rhine devices, there is nothing to dumb down, unfortunately. And rhine is a different platform, as compared to Z3 and up. Not to mention that 3.10 kernel is the whole new deal on top of that. So, if there is a chance we could have a fully functional camera on M, it would rather be with 3.4, but no one seems to be working on 3.4 in favor of 3.10...
optimumpro said:
"make sense to release camera for Z3 and not for Z1 in the same package"
No, it doesn't, because Sony engineers do work on Z3 and NOT on rhine (Z1 and Z1c) devices.
You are confusing several things: the fact that camera worked with LP AOSP has nothing to do with M blobs, but rather the fact that Sony released a crippled AOSP camera for lollipop. This camera has nothing to do with M. And note, Sony released LP camera only after Android has moved to M.
Now, about M. The reason I think real blobs are not coming is that first Sony engineers must create stock M for rhine devices (and it ain't coming, because Sony said so). Then, they dumb stock down for custom roms. That's the usual way. But because M isn't coming to rhine devices, there is nothing to dumb down, unfortunately. And rhine is a different platform, as compared to Z3 and up. Not to mention that 3.10 kernel is the whole new deal on top of that. So, if there is a chance we could have a fully functional camera on M, it would rather be with 3.4, but no one seems to be working on 3.4 in favor of 3.10...
Click to expand...
Click to collapse
Ok I understand. But it's still android, isn't it? So camera API is not changed that much and there must be some way how to put another layer between the blob and kernel (the wrapper). Every time I see another device's tree updated to Marshmallow I see updated camera wrapper (only one or two lines changed). So I'm wondering why this isn't possible on our device, especially when CM was using a wrapper on stock blob.
SuperLamic said:
Ok I understand. But it's still android, isn't it? So camera API is not changed that much and there must be some way how to put another layer between the blob and kernel (the wrapper). Every time I see another device's tree updated to Marshmallow I see updated camera wrapper (only one or two lines changed). So I'm wondering why this isn't possible on our device, especially when CM was using a wrapper on stock blob.
Click to expand...
Click to collapse
Current stock blobs don't work on 3.10, and there is no stock for 3.10. So, there is nothing to wrap...
You should ask the devs why they prefer to bang their heads (in the dark) on a totally foreign to Sony 3.10, when they can work on adapting 3.4 to work with August M blobs.
optimumpro said:
Current stock blobs don't work on 3.10, and there is no stock for 3.10. So, there is nothing to wrap...
You should ask the devs why they prefer to bang their heads (in the dark) on a totally foreign to Sony 3.10, when they can work on adapting 3.4 to work with August M blobs.
Click to expand...
Click to collapse
so what's this? http://www.cas-online.nl/author/erikcas/
edit: my bad, I ment why is not possible to wrap aosp ones
SuperLamic said:
so what's this? http://www.cas-online.nl/author/erikcas/
edit: my bad, I ment why is not possible to wrap aosp ones
Click to expand...
Click to collapse
Sony has opened the entire camera (not just blobs) for Lollipop, so, because it is open and you know your "addresses", it will work with other kernels (like 3.10). This is different from having closed source blobs (with uknown addresses) wrap around for a particular kernel. When they release crippled camera for M, then it would be possible. But why would Sony release crippled camera for M if M isn't coming to Z1?
So, the answer is, in my view: (i) potentially, we can have camera in MM with 3.4 kernel, but nobody is working on it in favor of 3.10; and (ii) not in our lifetime on 3.10.
Click to expand...
Click to collapse
So anything AOSP 6.0 with working camera will never come to Z1 ?
Camera works, (of course with poor quality) in the latest cRDroid 6.0.1 build.
hey @optimumpro
have you seen this? https://github.com/SonyAosp/platform_vendor_sony/commit/43c92897de18e71d40aa4fe3da350ea19c5c7ba9
I can see there some new camera blobs for honami, what do you think?
SuperLamic said:
hey @optimumpro
have you seen this? https://github.com/SonyAosp/platform_vendor_sony/commit/43c92897de18e71d40aa4fe3da350ea19c5c7ba9
I can see there some new camera blobs for honami, what do you think?
Click to expand...
Click to collapse
@SuperLamic i hope it's have deal with kernel 3.10
from i read the discussion the old blobs can deal with 3.4 and not 3.10 but all favor 3.10
what do you think?
DectonX said:
@SuperLamic i hope it's have deal with kernel 3.10
from i read the discussion the old blobs can deal with 3.4 and not 3.10 but all favor 3.10
what do you think?
Click to expand...
Click to collapse
huh, I'm not really sure that I understand.
But - yes new blobs should not be compatible with old 3.4 kernel (though I didn't test it and I'm not planning on to)
so now all 6.0-MM roms use 3.10 kernel and new blobs. I don't think that it's that bad as optimumpro says. Many things improved, but it's true that we have to wait for it because of still ongoing development.
SuperLamic said:
huh, I'm not really sure that I understand.
But - yes new blobs should not be compatible with old 3.4 kernel (though I didn't test it and I'm not planning on to)
so now all 6.0-MM roms use 3.10 kernel and new blobs. I don't think that it's that bad as optimumpro says. Many things improved, but it's true that we have to wait for it because of still ongoing development.
Click to expand...
Click to collapse
Here is a fact: sonyxpdev team has NEVER had camera fully working on any aosp rom. So, what makes anyone think things are going to be different on MM? They won't. The only chance was to have it work with cm device trees and 3.4 kernel, but that ain't coming, because CM and everyone else switched to aosp trees and 3.10.
So, if you want MM, buy a new device.
Related
This topic is for other developers, not for users who are eagerly waiting for something that may never come
I know that upstream p970 development has stopped. However, I still find it a challenge to get JB4.3 running on the p970. Main reasons is that on the Samsung Galaxy Tab 10.1 (which has also been discontinued by CM-team due to the outdated tegra2 chipset) CM10.2 actually seems to run smoother than CM10.1 (possibly due to the code cleaning from JB4.2 -> JB4.3).
I have started by adding some missing variable to BoardConfig.mk and enabling SELinux in kernel, but already bumped into some compiling issues. Are there any others working on this, or interested in helping?!
Not going into technical part but I have heard and strongly believe that new version means not really a high-end hardware only. According to my knowledge KLP will run smoothly on a device having 512mb of RAM.
and how are you going to get 5.0 if you don't have the source code?! it will be just full of bugs, unusable
recl said:
and how are you going to get 5.0 if you don't have the source code?! it will be just full of bugs, unusable
Click to expand...
Click to collapse
????
JB is build based on pure android code from google. So that is the source code necessary...
Honestly,if I could choose from android 4.3 and android 5.0, I'll prefer to wait for android 5.0! Android 5.0 is designed to ensure the performance on old and low-end devices !
I am looking forward for developers to port android 5.0 into our device!!!
I'm willing to help in testing so ring me up anytime!
Sent from my LG-P970 using Tapatalk 4
kasper_h said:
This topic is for other developers, not for users who are eagerly waiting for something that may never come
Click to expand...
Click to collapse
What this mean for you guys?
It is booting already!
only running into some stagefright issues so the display isnt turning on, but i already get access to the logcat to debug.
our target is getting closer and closer
Nice job
When we will have available an android 4.4 rom ? Is someone working on this ?
SilentGTX said:
When we will have available an android 4.4 rom ? Is someone working on this ?
Click to expand...
Click to collapse
Hey, well we can get some pre-alpha 4.4 AOSP builds maybe, but these will definitely have bugs, i do believe adam has built a 4.4. omni rom but i don't know much about bugs/boot status etc.
We are still waiting for cyanogenmod to merge sources, however they have stated that they are in no rush to start dishing out 4.4 roms as they have only just sunken their teeth into 4.3 Roms, we will get them eventually, however any builds within the next few days will have little customization or lots of bugs, patience is all we have till then
I hope this answered your question, also, this needs to be in the Q&A section next time bro
Good evening.
penguin449 said:
Hey, well we can get some pre-alpha 4.4 AOSP builds maybe, but these will definitely have bugs, i do believe adam has built a 4.4. omni rom but i don't know much about bugs/boot status etc.
We are still waiting for cyanogenmod to merge sources, however they have stated that they are in no rush to start dishing out 4.4 roms as they have only just sunken their teeth into 4.3 Roms, we will get them eventually, however any builds within the next few days will have little customization or lots of bugs, patience is all we have till then
I hope this answered your question, also, this needs to be in the Q&A section next time bro
Good evening.
Click to expand...
Click to collapse
Yeah thank you very much , it was very helpful , sorry for the wrong section . I can't wait for Android 4.4 ROMs :fingers-crossed: Good evening .
SilentGTX said:
Yeah thank you very much , it was very helpful , sorry for the wrong section . I can't wait for Android 4.4 ROMs :fingers-crossed: Good evening .
Click to expand...
Click to collapse
Please understand that all the great things you've been hearing about android 4.4 wont apply to us for quite some time, what i mean by this is all the efficiency/ performance improvements will be somewhat mitigated buy bugs and firmware incompatibilities, these things take time for devs to work through, 4.3 still isnt mature enough on this device to call it stable.
I just don't want people to get overly excited by a 4.4 port, its improvements will come gradually.
JoinTheRealms said:
Please understand that all the great things you've been hearing about android 4.4 wont apply to us for quite some time, what i mean by this is all the efficiency/ performance improvements will be somewhat mitigated buy bugs and firmware incompatibilities, these things take time for devs to work through, 4.3 still isnt mature enough on this device to call it stable.
I just don't want people to get overly excited by a 4.4 port, its improvements will come gradually.
Click to expand...
Click to collapse
I understand , of course , but still I can't wait :victory:
Gonna join this group, too
4.4 sure is on its way for our device, BUT:
Google is removing more and more support for our device, as it already is pretty old. So we need to re-add everything.
Even if it's booting, we still need a lot of work in order to get the most important stuff working (like SurfaceFinger, Audio, and ofc also data/RIL)
So regarding 4.4, all I can say is: Have patience
BTW, Thread moved to Q&A section
JoinTheRealms said:
4.3 still isnt mature enough on this device to call it stable.
Click to expand...
Click to collapse
im using pa 3.99 rc2 wich is 4.3 and it is perfectly stable, has great performance and no big bugs, i use it as a daily driver and it is the most perfect rom i used on my p880 till date
~MaX~ said:
im using pa 3.99 rc2 wich is 4.3 and it is perfectly stable, has great performance and no big bugs, i use it as a daily driver and it is the most perfect rom i used on my p880 till date
Click to expand...
Click to collapse
Yes they are functionally stable to a user, but to call a rom stable (at least by Cyanogenmods standards) requires more than that.
JoinTheRealms said:
Yes they are functionally stable to a user, but to call a rom stable (at least by Cyanogenmods standards) requires more than that.
Click to expand...
Click to collapse
please define stable then
~MaX~ said:
please define stable then
Click to expand...
Click to collapse
Doesn't use dirty patch code to fix issues in source, usually done to get a release out quicker, between release candidates to stable this code is refined.
JoinTheRealms said:
Doesn't use dirty patch code to fix issues in source, usually done to get a release out quicker, between release candidates to stable this code is refined.
Click to expand...
Click to collapse
Well.... Thank you
That's Well explained
I hope you are working on 4.4 rom
laufersteppenwolf said:
Gonna join this group, too
4.4 sure is on its way for our device, BUT:
Google is removing more and more support for our device, as it already is pretty old. So we need to re-add everything.
Even if it's booting, we still need a lot of work in order to get the most important stuff working (like SurfaceFinger, Audio, and ofc also data/RIL)
So regarding 4.4, all I can say is: Have patience
BTW, Thread moved to Q&A section
Click to expand...
Click to collapse
i'm really excited to see you releasing the 4.4 rom Aosp or custom, anyway your work is cool
You guys really doing great work here so l know that stable 4.4 will come eventually
Sent from my HTC Explorer A310e using Tapatalk 2
JoinTheRealms said:
Doesn't use dirty patch code to fix issues in source, usually done to get a release out quicker, between release candidates to stable this code is refined.
Click to expand...
Click to collapse
Sometimes it's still necessary to do. This is the case with our EGL libs for example. The best would be getting an update from LG, but this is very unlikely to happen. I got 4.3 BSP partially working, updated all graphics-related libs to 4.3 from grouper, but it broke a few things. Porting the full BSP might not be even possible.
Regarding Omni 4.4, I gradually found probably all needed patches for it, will see when I get to computer.
Sent from my OmniROM-powered LG Optimus 4X HD
This is Strictly Development i u know something plz share if don't then be slient
What is ION .?
Noob way :- It makes things awsome -by lauppenstepperwolf
there is awsome explaination on LX git Wiki
LX said:
#### What is Shared Memory?
Memory is usually private; an app takes a chunk and nothing else can access it.
Sometimes, it makes sense to share memory between processes; for example, an app writes to the screen buffer, while the gfx driver reads that same buffer to put it on the screen. You need a special memory system for that.
####PMEM vs. ION
Back with Gingerbread, every ARM chip maker (Qualcomm, TI, nVidia, Samsung, more?) had their own way of doing shared memory. The Qualcomm way was a system called **PMEM**.
Problem: when a vendor sells a chip to Sony and Samsung, he needs to write two drivers, one for each shared memory system.
To reduce maintenance efforts, Google introduced **ION**, a unified shared memory system, that all vendors use since ICS
Problem: from ICS forward, Qualcomm only provides graphics drivers for ION. PMEM is obsolete.
For a while, stuff still worked, but it is getting worse for us - see the Google Maps app for example.
####Move to ION
An option is to rework the kernel, replace the PMEM system with ION, and replace the old PMEM drivers with newer ION drivers. A common problem on several old devices is, that the camera chip is non-standard, and Sony (Samsung, HTC) never wrote ION drivers for the old cameras. Moving to ION then means you lose the camera completely.
A new solution is to move the kernel to ION, but have a PMEM system on top of ION so that the old camera libs can connect to it. As far as I know, this was pioneered by the Dev_Connection team that maintains the Samsung S+ i9001 (great team, hats off to Christopher83 especially).
Another implementation of an ION/PMEM hybrid was made by galaxyfreak for the HTC Explorer (Pico).
The i9001 and the Pico have similar hardware to our 2011 Xperias (2011, MSM, 512MB RAM, similar specs).
Feedback for the ION builds is very positive. Performance is good and it solves some graphics problems like the Google Maps flickering, and it solves the slow browser.
####ION on LegacyXperia
It would be the next big step after the 3.x kernel, but, it's a lot of work.
On the i9001, 8 devs work on 1 device, while on our side, 1 dev works on 8 devices.
The i9001 approach was to migrate 10.1 to ION, then 10.2, then 11; instead of directly doing 11-ION.
Click to expand...
Click to collapse
ETA :- Nowhere to release
============================================================================
THIS IS A REWORK ON nAa-kernel to use ION but with no video recording support ... until mike does spread his awsome magic with his new scratch ported kernel...
Source :- http://www.github.com/rebel-x/msm7x30-3.4.x-nAa
Current Progress : Intial Pushes done "yay" lets hope it boots
NOTE :- We need your help , i m not able to do alone since i have very limited knowledge about kernels , Please forgive me if my coding somewhere wrong cause
ok so thank you i will post progress as we all get step further ,
thank you
Credits :
Mike : we all know why
nAa : Awsome dev
szezso : always helpful
XDA:DevDB Information
ION-Kernel, a Kernel for the Sony Ericsson Xperia Arc
Contributors
officiallysonyrebel, szezso, Mike
Kernel Special Features:
Version Information
Status: Testing
Created 2014-01-08
Last Updated 2014-01-07
Don't ever give up!
you also need To build rom with ion accelator
offical
its offical jb kernel ?
mahsun72 said:
its offical jb kernel ?
Click to expand...
Click to collapse
Can you read? It's not even official. It could be also for CM11 since he mentioned browser lag, which is an existing bug in CM11.
To OP, I should be able to check the coding and whatnot. Only problem is I'm currently in the army and unable to access my computer on weekdays.
僕のLT18iから送られてきた
@n1kolaa i guess you can start work on this if you have time.. I have seen you working.. Seems a real genius can you?
Sent from my Nexus 5 using Tapatalk
I should also be able to check the code as I'm proficient in C++. Let me know where I can help out, it's a good initiative.
ION and PMEM should'nt be device specific, no ? Isn't the work done on i9001 reusable here ?
First it could be interesting to locate all patches applied on the kernel to implement the hybrid memory allocation.
Edit :
I suppose the kernel in question is this one :
https://github.com/AriesVE-DevCon-TEAM/samsung-kernel-msm7x30/tree/cm-11.0_ion_pmem_adsp
Boudin said:
ION and PMEM should'nt be device specific, no ? Isn't the work done on i9001 reusable here ?
First it could be interesting to locate all patches applied on the kernel to implement the hybrid memory allocation.
Edit :
I suppose the kernel in question is this one :
https://github.com/AriesVE-DevCon-TEAM/samsung-kernel-msm7x30/tree/cm-11.0_ion_pmem_adsp
Click to expand...
Click to collapse
ion is different for every device i guess
Update :
finished initial kernel part (lets hope it boots know)
vishal_android freak said:
@n1kolaa i guess you can start work on this if you have time.. I have seen you working.. Seems a real genius can you?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
im now focus on shool,also i give my arc to my sister i now have only idol mini
n1kolaa said:
im now focus on shool,also i give my arc to my sister i now have only idol mini
Click to expand...
Click to collapse
Well, that's still fine.. Mini you have for testing.. Give it a try, you never know what you can end up with, probably a working kernel with ion support.. :thumbup:
Regards,
vishal_android freak
vishal_android freak said:
Well, that's still fine.. Mini you have for testing.. Give it a try, you never know what you can end up with, probably a working kernel with ion support.. :thumbup:
Regards,
vishal_android freak
Click to expand...
Click to collapse
its idol mini form alcatel,how can i test new kernel with it explain it to me
n1kolaa said:
its idol mini form alcatel,how can i test new kernel with it explain it to me
Click to expand...
Click to collapse
Ohh.. My bad.. Sorry..
Sent from my Nexus 5 using Tapatalk
I think I can develop based on this. Is the ION kernel actually booting and working preperly etc. ?
CedArctic said:
I think I can develop based on this. Is the ION kernel actually booting and working preperly etc. ?
Click to expand...
Click to collapse
i have completed allocation but that f**kin msmfb code is a heck since we are using drivers from 3.0 need a lot of work
rebelos said:
i have completed allocation but that f**kin msmfb code is a heck since we are using drivers from 3.0 need a lot of work
Click to expand...
Click to collapse
all the best bro.. Any improvements?
gpkumaran said:
all the best bro.. Any improvements?
Click to expand...
Click to collapse
yea its compiling know but no where Close to Boot ... i have changes locally purchased a XMP with screen destroyed only for kernel debugging purpose
rebelos said:
i have completed allocation but that f**kin msmfb code is a heck since we are using drivers from 3.0 need a lot of work
Click to expand...
Click to collapse
Thanks for your work! I love KK rom and im wait ion kernel :thumbup:
Regards
To many 4.4 roms are coming out....in my opinion all kitkat devs should focus on just 2 roms and this really good kernel.
At least with 2 different 4.4 roms there is still competiton for improvement without scattering work to much.
A nicely developed kitkat will save out Arc from retirement.
Btw i was wondering, since HDMI sources for kitkat are not available, would it be possible to create-compile a MHL compatibility for our arc? so we can use MHL accessory instead of HDMI? Or a virtual machine on kitkat running the stock ICS HDMI feature?
I'm no dev so i have no idea how hard it could be.....just asking out of curiosity, many use hdmi on arc for movies or android desktop with OTG mouse and keyboard. Its really a pity we cannot make it work on 4.4 yet.
Dr.SAM88 said:
To many 4.4 roms are coming out....in my opinion all kitkat devs should focus on just 2 roms and this really good kernel.
At least with 2 different 4.4 roms there is still competiton for improvement without scattering work to much.
A nicely developed kitkat will save out Arc from retirement.
Btw i was wondering, since HDMI sources for kitkat are not available, would it be possible to create-compile a MHL compatibility for our arc? so we can use MHL accessory instead of HDMI? Or a virtual machine on kitkat running the stock ICS HDMI feature?
I'm no dev so i have no idea how hard it could be.....just asking out of curiosity, many use hdmi on arc for movies or android desktop with OTG mouse and keyboard. Its really a pity we cannot make it work on 4.4 yet.
Click to expand...
Click to collapse
A better Kitkat .. lets summerize current kernel situation
1. nAa 3.4 full of hacks
2. using drivers and stuffs from 3.0.x
3. Stuck on Abandoned PMEM {with every increasing android version we are using patches more than before to maintain PMEM causing soo many graphic lags
4. msm_fb code /* lets not focus on it currently */
why this mess /* to bring 3.4 kernel faster */
i m trying on 3.0.x-nAa kernel cause it is Pure CAF and also mike is working on Pure CAF 3.4.x MHL enablin gis such a lot and lot of work we are not in fully stable stage to look at MHL and other workaround first..
our device is a 3 year old piece of hardware without camera and HDMI libs using outdated kernel and drivers what should be the main goal
1. To make kernel updated with current sources
2. then make things working
3. then wprkaround for all abandoned hardware(like HDMI)
hope u know why we are focus on kernels and roms know ... and to come at point of compeion in roms
there is no compeition we are not selling our products .. we are working cause we like it and more roms means more respect for developers who are working tirelessly on maintaining those roms @Marchinho6 please no these kinds of post ..!these will spam thread
most of us here are either using cm11 or omnirom or AOKP no idea if anyone here actually realised it but the blobs we are using are based on 4.1.2 which some patched to get it working in kitkat most of the time there is nothing wrong with it.. but as this blobs are closed source we are not aware of the changes thus we may be lacking in important improvement like more smoothness ? cutting down our battery usage etc
also I have no idea if the latest kernel changes are merged in but it looks like this hopes of this device becoming down hill is starting to rise..
I really hope this device isn't forgotten due to google play edition or the z1
iKillCypher said:
most of us here are either using cm11 or omnirom or AOKP no idea if anyone here actually realised it but the blobs we are using are based on 4.1.2 which some patched to get it working in kitkat most of the time there is nothing wrong with it.. but as this blobs are closed source we are not aware of the changes thus we may be lacking in important improvement like more smoothness ? cutting down our battery usage etc
also I have no idea if the latest kernel changes are merged in but it looks like this hopes of this device becoming down hill is starting to rise..
I really hope this device isn't forgotten due to google play edition or the z1
Click to expand...
Click to collapse
I have *no* idea what you're talking about.
Kernel: https://github.com/CyanogenMod/android_kernel_sony_apq8064/commits/cm-11.0
Commits to look at: https://github.com/CyanogenMod/andr...mmit/f16949940d1cf4a292de0a02409b284713bd8c5c (merge .2.67 release)
https://github.com/CyanogenMod/andr...mmit/289394f3bd6b121ec5b42453f5b6b1c8614196ba (merge old cm11 commits to new cm-11.0 branch)
https://github.com/CyanogenMod/andr...mmit/751383c3b257f23485b5aa7981573db1b6289282 (merge kk2.7 to new cm-11.0)
What this means: Contains .2.67 code from Sony, plus kk2.7 code from codeaurora, making the kernel arguably more up to date than Sony's.
Vendor: https://github.com/TheMuppets/proprietary_vendor_sony/commits/cm-11.0
Commits to look at: https://github.com/TheMuppets/propr...mmit/0a442f0b87e168ebdbc0f30b70d05dbe01a18ed3 (update blobs to .2.67)
What this means: Blobs updated to .2.67
The last I checked, .2.67 was 4.2.2, not 4.1.2. I'm not even sure why I'm so mad, maybe it's just that I don't like misinformation, particularly misinformation that can be *easily* checked.
As an example i could state the old modem they use? There are massive improvements in the modem in the 4.3 official version, but all these are missing when running CM11. It's the reason why i went back to 4.3 official.
beN.. said:
As an example i could state the old modem they use? There are massive improvements in the modem in the 4.3 official version, but all these are missing when running CM11. It's the reason why i went back to 4.3 official.
Click to expand...
Click to collapse
It would be nice if you could show what the "massive improvements in the modem in the 4.3 official version" are I mean, I'm not trying to be sarcastic, but new things for the sake of new things doesn't make much sense unless there are provable differences. Besides, the 4.3 stuff is probably being worked on right now, you can see that the camera is already being tested, for example.
For me the massive improvement is getting stable Wi-Fi at places where CM11 doesn't even find the network or fails to connect.
Range and stability is improved a lot in 4.3 official.
hey pandaball
I just spoke to Kali- few hours ago and it seems like they will be pushing for 4.3 blobs updates soon... for cm 11
also the kernel it seems like I got mislead cause there was no gerrit updates on it ? is it confirm that the latest CM11 is indeed using the latest kernel source from Sony ?
18<Kali-18> i got a talk with cdesai about Z 11.0 blob
18<Kali-18> and we should move to 4.3.3 blob/kernel
18<Kali-18> no update on 10.2
iKillCypher said:
hey pandaball
I just spoke to Kali- few hours ago and it seems like they will be pushing for 4.3 blobs updates soon... for cm 11
also the kernel it seems like I got mislead cause there was no gerrit updates on it ? is it confirm that the latest CM11 is indeed using the latest kernel source from Sony ?
18<Kali-18> i got a talk with cdesai about Z 11.0 blob
18<Kali-18> and we should move to 4.3.3 blob/kernel
18<Kali-18> no update on 10.2
Click to expand...
Click to collapse
The kernel typically doesn't get committed via gerrit, it is pushed directly to the CM github. It isn't using the latest Sony kernel, it uses the 2.67 kernel with the kk2.7.1 branch from codeaurora, which is more up-to-date than the Sony kernel in terms of SOC drivers.
At best this is a Q&A thread.
So lets just consider the question answered and put this baby to bed.
Thread closed
hi all
for those impatient and dare to try, plus able to handle problems ON YOUR OWN as i cannot offer any help at this point:
anyone interested to test an updated version of BeastMode Kernel R154 by @freeza with the latest samsung firmware N960FXXU8FUD1?
please be noted that:
- this might be EXTREMELY DANGEROUS or could BRICK YOUR PHONE in a few seconds, and I am not responsible for bricked devices or any damages which may arise. so, you have been WARNED
- I have NOT TESTED on my n960f yet (just updated to TH4 from pie but not rooted yet for some reasons). SO THINK TWICE!!
- chances the phone may not boot up properly (boot loop or hang) due to the toolchains used to compile the kernel. I have encoutered this before with only one of the four or five gcc i had which booted up the phone successfully
ideal situation to minimize uncertainties:
- already on ud1
- data/cache partition is ext4 formatted (ideally NOT f2fs as supported by bm kernel)
- capable of diagnostic/identify the problems by examining the logcat/last_kmsg and the like would defintely a plus
to be continued...
Hello, Is this gonna work on newer BL version? FUE5 version, also @CyderXDA would wanna try it, but he's on newer BL. We also have Exynos9810 Telegram Chat, there's N9/S9/S9+ users in there that maybe could test for you and stuff if you're interested
JC1126 said:
Hello, Is this gonna work on newer BL version? FUE5 version, also @CyderXDA would wanna try it, but he's on newer BL. We also have Exynos9810 Telegram Chat, there's N9/S9/S9+ users in there that maybe could test for you and stuff if you're interested
Click to expand...
Click to collapse
hi
samsung has just posted a newer firmware N960FXXS8FUE5, probably hours ago, i am going to update it first. will let you guys know
thanks for your interests
ykkfive said:
hi
samsung has just posted a newer firmware N960FXXS8FUE5, probably hours ago, i am going to update it first. will let you guys know
thanks for your interests
Click to expand...
Click to collapse
Alright Goodluck!
JC1126 said:
Alright Goodluck!
Click to expand...
Click to collapse
update 20160616
updated to samsung ue5 sources
i have built 2 different versions, one with gcc 4.9 and the other with gcc 12. there will be only one version in the future (either gcc4 or 12). the reason i built 2 versions this time is in case one of the gcc used doesnt boot probably there's another one to try
differences between @freeza 's R154:
- kernel sources updated (N960F) without any fix or new feature
- not pre-rooted/pre-patched by magisk since the magisk version may differs from what u r using
- NOTE: other devices preiously supported are not recommeded yet, although you may try, i cant make any promise it will work since i didnt look at other devices sources
thinking if i should release it for testing now or wait until i have time to test it myself coz i don want to brick anyone's phone, including mine of coz
ykkfive said:
update 20160616
updated to samsung ue5 sources
i have built 2 different versions, one with gcc 4.9 and the other with gcc 12. there will be only one version in the future (either gcc4 or 12). the reason i built 2 versions this time is in case one of the gcc used doesnt boot probably there's another one to try
differences between @freeza 's R154:
- kernel sources updated without any fix or new feature
- not pre-rooted/pre-patched by magisk since the magisk version may differs from what u r using
- f2fs supported as R154 (cache/data)
thinking if i should release it for testing now or wait until i have time to test it myself coz i don want to brick anyone's phone, including mine of coz
Click to expand...
Click to collapse
Holy that's insane, you added f2fs that's exciting, wonder if it supports AOSP because most of n9 users use aosp, some use noblerom
JC1126 said:
Holy that's insane, you added f2fs that's exciting, wonder if it supports AOSP because most of n9 users use aosp, some use noblerom
Click to expand...
Click to collapse
i didnt add anything new, but i found in his fstab, f2fs is ready. i didnt examine the kernel sources yet. this it true for aosp etc also
so in case f2fs/aosp etc was supported in his R154, it should be, i believe...
sorry, but NO f2fs there in his kernel!!
ykkfive said:
i didnt add anything new, but i found in his fstab, f2fs is ready. i didnt examine the kernel sources yet. this it true for aosp etc also
so in case f2fs/aosp etc was supported in his R154, it should be, i believe...
Click to expand...
Click to collapse
that's cool, can't wait to try it out in lineage a11 lol
JC1126 said:
that's cool, can't wait to try it out in lineage a11 lol
Click to expand...
Click to collapse
i just checked the output, there's no f2fs unfortunately but i can add it later after test
ykkfive said:
i just checked the output, there's no f2fs unfortunately
Click to expand...
Click to collapse
that's still fine tbh, not much difference on ext4, good thing is it works on aosp, idk if it'll boot on oneui3.1 because it needs a permissive kernel to boot so yeah
JC1126 said:
that's still fine tbh, not much difference on ext4, good thing is it works on aosp, idk if it'll boot on oneui3.1 because it needs a permissive kernel to boot so yeah
Click to expand...
Click to collapse
tbf i have not built one with both sammy and aosp supported kernel, and i even don't know his kernel supports aosp
for the one ui 3.1 thing, u mean the ported one? i believe he's made it to run on existing kernel so it should be fine. of coz it needs to be tested first
ykkfive said:
tbf i have not built one with both sammy and aosp supported kernel, and i even don't know his kernel supports aosp
for the one ui 3.1 thing, u mean the ported one? i believe he's made it to run on existing kernel so it should be fine. of coz it needs to be tested first
Click to expand...
Click to collapse
Ohh alright then
update 20210618
the ue5 kernel works properly so far, tested on stock rom only due to unable to get a ue5 custom rom atm
will be released soon
thanks a lot
released, closed