I'm running a bounty for Audience chipset support in re-oriented kernels. I will personally paypal you $50 if you can provide a working GB I9000 reoriented kernel ( and instructions for the rest of the devs ) with working Audience support.
I will keep a list of any further donations here -- I am not responsible for any other donations other than my own.
I haven't done any Android kernel development other than browse the files from time to time. Coming from the linux/freebsd world from what I've seen this should be technically feasible:
The kernel ABI doesn't change much from 2.2 to 2.3 .. if at all:
Kernel:
Android 2.2 – Linux Kernel 2.6.32
Android 2.3 – Linux Kernel 2.6.35
One should be able to simply 'graft' audience enabled makefiles/src/objects/options etc into any kernel build from the captivate 2.2 release on Samsung's opensource site with minor edits.
Additional Contributors:
RichMD $10
othermark said:
I'm running a bounty for Audience chipset support in re-oriented kernels. I will personally paypal you $50 if you can provide a working GB I9000 reoriented kernel ( and instructions for the rest of the devs ) with working Audience support.
I will keep a list of any further donations here -- I am not responsible for any other donations other than my own.
I haven't done any Android kernel development other than browse the files from time to time. Coming from the linux/freebsd world from what I've seen this should be technically feasible:
The kernel ABI doesn't change much from 2.2 to 2.3 .. if at all:
Kernel:
Android 2.2 – Linux Kernel 2.6.32
Android 2.3 – Linux Kernel 2.6.35
One should be able to simply 'graft' audience enabled makefiles/src/objects/options etc into any kernel build from the captivate 2.2 release on Samsung's opensource site with minor edits.
Click to expand...
Click to collapse
I haven't personally looked into them, but I know Atinm had looked at it, and apparently there was quite a few changes involving audio stuff, including the audience chip drivers.
Not saying it can't be done, obviously, but I don't think its a simple copy/paste action either.
I'd throw in $10
Sent from my GT-I9000 using XDA Premium App
Hey guys i was just wondering what the big problem with the hardware acceleration on all of those ICS build are. for what i understand its a kernel problem. amazon build upon android 2.3 with an 2.6 kernel. the new ICS needs a kernel 3+ for driver and open gl to do the hardware acceleration. i'm i right?
in this state i do wonder, if it is possible to get hardware acceleration on ics. is it possible to build a 3+ kernel for the kindle? where is the problem, its only man hour that we need, or is for example the kernel signed to prevent flashing?
I know that they guys at the dev section are doing an amazing job so far, and to this point im very glad to have so many good dev working on the kindle. i do not ask for an date, like: in 3 days there will be an ics build with HWA.
im looking for some insight in the dev roadmap for example what is missing for the mentioned HWA.
thanks so far :>
It will come with time - man hours are indeed what's needed. No signed kernel problem. Needs a lot of hacking to get the new kernel to work.
yeah i would also like to know this
kernel 3.0 is not required for HW acceleration.
watch this video.
http://www.youtube.com/watch?feature=player_embedded&v=6Ug-HNK9XVE(4:50)
This tablet running fine on 2.6.39 kernel with hardware acceleration.
We have only 2.6.35 kernel... (older than 2.6.39)
Just developers can not yet solve the problem.
Android 3.0 kernel is definitely not needed for hardware acceleration. Teamhacksung had it working with a 2.6.35 kernel before they moved to a 3.0 kernel for their supported galaxy s devices.
For hw accelerated ui drawing you will need updated pvr drivers and modified fb drivers.
For hw accelerated video decoding, you will need updated dss bridge drivers, and updated codecs specifically for the IVA processor in the omap 4. I don't know if it is a requirement for our devices, but on the aries(hummingbird) platform they had to modify their framebuffer drivers to have more overlay buffers.
It just a toss up of whether it is easier to get a working 3.0 kernel, or back port all of the udpates.
I guess its time for me to get a VM setup and start hacking away. Or at the very least start comparing parts of our 2.6.35 kernel with the pandaboard, and gnex 3.0.8 kernel.
woolbeo said:
Android 3.0 kernel is definitely not needed for hardware acceleration. Teamhacksung had it working with a 2.6.35 kernel before they moved to a 3.0 kernel for their supported galaxy s devices.
For hw accelerated ui drawing you will need updated pvr drivers and modified fb drivers.
For hw accelerated video decoding, you will need updated dss bridge drivers, and updated codecs specifically for the IVA processor in the omap 4. I don't know if it is a requirement for our devices, but on the aries(hummingbird) platform they had to modify their framebuffer drivers to have more overlay buffers.
It just a toss up of whether it is easier to get a working 3.0 kernel, or back port all of the udpates.
I guess its time for me to get a VM setup and start hacking away. Or at the very least start comparing parts of our 2.6.35 kernel with the pandaboard, and gnex 3.0.8 kernel.
Click to expand...
Click to collapse
After buying the Kindle Fire just recently, I was looking up HWA and found your post. Thanks for the detailed response, much appreciated.
Hashcode is working hard on a 3.0 kernal and is keeping updates on his progress in this thread. He could be weeks away from debugging the kernal he is developing
My understanding is, for HWA to work running ICS, the 3.0 kernel is required. Yes, there are other ROMS that have HWA working but they are not ICS.
That is correct, the current kernel doesn't allow for the changes made in android 4.0. If you need HWA for daily use, stick with a gingerbread rom. Otherwise support and wait for Hashcodes work on the new kernel.
Sent from my Amazon Kindle Fire using xda premium
Sorry for my excitement.But i am quiet depressed that more than 2 to 3 months have been passed but their is no nougat ROM for our device.
If someone has idea whether the making is under processing or yet to be start.please let me know.
Thanx.
i guess kernal source is released by xiaomi, very soon we should be able to see some developments on nougat roms for our devices.
At least a month, I think.
Only when you see msm8937 nougat caf kernel source here -> Android releases (QAEP.release) - XWiki
https://wiki.codeaurora.org/xwiki/bin/QAEP/release
hafeez90 said:
Only when you see msm8937 nougat caf kernel source here -> Android releases (QAEP.release) - XWiki
https://wiki.codeaurora.org/xwiki/bin/QAEP/release
Click to expand...
Click to collapse
Thanx for the nice info.I'll keep checking it regularly.
Source: https://blogs.sonymobile.com/2017/08/31/xperia-android-8-0-oreo/
Got nearly 2 years of updates, but not quite.
On a related note, official XZ1 Compact website is up. I'm thinking about getting one for my wife to replace her Z5C, UFS sounds delicious.
The list of devices in the blog is not final and it is possible that we will see Oreo on our device.
Even though stock will not support Oreo, Custom firmwares will usually always outlast stock
(Lineage and Carbon are using stock blobs on the Z5 Lineup so custom roms are nearly the same quality, if not better, then stock anyway)
nzzane said:
Even though stock will not support Oreo, Custom firmwares will usually always outlast stock
(Lineage and Carbon are using stock blobs on the Z5 Lineup so custom roms are nearly the same quality, if not better, then stock anyway)
Click to expand...
Click to collapse
I was wondering about this myself. Are the stock blobs sdk version specific, so in order to make a custom Oreo rom a stock Oreo ftf is needed first? Or should the nougat blobs potentially be used in an Oreo firmware? Same with hardware drivers that are unique to our device, like WiFi?
cyberwytch said:
I was wondering about this myself. Are the stock blobs sdk version specific, so in order to make a custom Oreo rom a stock Oreo ftf is needed first? Or should the nougat blobs potentially be used in an Oreo firmware? Same with hardware drivers that are unique to our device, like WiFi?
Click to expand...
Click to collapse
From memory, as long as the source is configured right it should be fine (Wifi drivers shouldn't be changing as its still the same hardware, same for screen and all) - Carbonrom and Lineage source are currently being updated to Oreo, along with some of the sony files being configured for it so hopes are high.
nzzane said:
From memory, as long as the source is configured right it should be fine - Carbonrom and Lineage source are currently being updated to Oreo, along with some of the sony files being configured for it so hopes are high.
Click to expand...
Click to collapse
Awesome sauce! I love your Lineage 14, can't wait to see what's next!
nzzane said:
Even though stock will not support Oreo, Custom firmwares will usually always outlast stock
(Lineage and Carbon are using stock blobs on the Z5 Lineup so custom roms are nearly the same quality, if not better, then stock anyway)
Click to expand...
Click to collapse
That's awesome news, I'll add "official" to the thread title for clarification.
They said it was because Qualcomm aren't great at after market support.
so we couldn't get 3.18, but, what would be interesting to do would be to make some interface to act like a middle man.
I'm currently doing something similar for my laptop running Server 2016, and am slowly making it run like a Desktop OS, by enabling all the other stuff left out that I can find
---------- Post added at 16:25 ---------- Previous post was at 16:21 ----------
nzzane said:
...
Click to expand...
Click to collapse
which linux kernel is LOS running?
NeoBeum said:
They said it was because Qualcomm aren't great at after market support.
so we couldn't get 3.18,
Click to expand...
Click to collapse
Where was this said, and why would we need 3.18 for the Z5 family?
A lot of the reporting being done on this has been bad (whatever happened to reading comprehension, especially in reporters??). According to the source being cited, only SoCs produced prior to 2017 (which the Snapdragon 810 is) AND that are being launched in new devices (which the Z5 series is NOT) are required to run on 3.18. Existing devices already designed and sold before the launch of Oreo (which, having launched in 2015, I think the Z5 family would qualify as) "can continue to use their original base kernel version if desired."
-- Nathan
nlra said:
Where was this said, and why would we need 3.18 for the Z5 family?
A lot of the reporting being done on this has been bad (whatever happened to reading comprehension, especially in reporters??). According to the source being cited, only SoCs produced prior to 2017 (which the Snapdragon 810 is) AND that are being launched in new devices (which the Z5 series is NOT) are required to run on 3.18. Existing devices already designed and sold before the launch of Oreo (which, having launched in 2015, I think the Z5 family would qualify as) "can continue to use their original base kernel version if desired."
-- Nathan
Click to expand...
Click to collapse
on github somewhere,
actually, ask and tag greyleshy, he was the one that asked about final kernel for us, and I found the convo somewhere trying to get Bluetooth junk sorted
there might be some msm8994 thing that sony needs but cant use for oreo or something. I dont know
NeoBeum said:
on github somewhere,
actually, ask and tag greyleshy, he was the one that asked about final kernel for us, and I found the convo somewhere trying to get Bluetooth junk sorted
there might be some msm8994 thing that sony needs but cant use for oreo or something. I dont know
Click to expand...
Click to collapse
Hmm, 'k; thanks. I'll do some more digging. But if true this would flatly contradict Google's own public statements (though I realize it's not like this would be a first for that kind of thing).
-- Nathan
NeoBeum said:
They said it was because Qualcomm aren't great at after market support.
so we couldn't get 3.18, but, what would be interesting to do would be to make some interface to act like a middle man.
Click to expand...
Click to collapse
Android Oreo supports Kernel 3.10, but need to patch the kernel (example: patch 1, patch 2).
It would be nice if msm8994 supported kernel 3.18 or 4.4, but it is not.
Apparently QCOM has not provided drivers for 3.18+ and therefore CodeAurora kernel was not released because of compatibility issues.
NeoBeum said:
which linux kernel is LOS running?
Click to expand...
Click to collapse
3.10, CAF kernel
nlra said:
Where was this said, and why would we need 3.18 for the Z5 family?
A lot of the reporting being done on this has been bad (whatever happened to reading comprehension, especially in reporters??). According to the source being cited, only SoCs produced prior to 2017 (which the Snapdragon 810 is) AND that are being launched in new devices (which the Z5 series is NOT) are required to run on 3.18. Existing devices already designed and sold before the launch of Oreo (which, having launched in 2015, I think the Z5 family would qualify as) "can continue to use their original base kernel version if desired."
-- Nathan
Click to expand...
Click to collapse
correct,
actually 4.4 kernel, it's only needed for newer SoCs
so we can go on with 3.10 kernel for now but we need to wait for (potential) CAF changes
GreyLeshy said:
Android Oreo supports Kernel 3.10, but need to patch the kernel (example: patch 1, patch 2).
It would be nice if msm8994 supported kernel 3.18 or 4.4, but it is not.
Apparently QCOM has not provided drivers for 3.18+ and therefore CodeAurora kernel was not released because of compatibility issues.
Click to expand...
Click to collapse
well, there's still Linux mainline / vanilla upstream support for msm8994 since 4.10 kernel in a very rough state with terminal only (AOSP)
and there's the (close to complete) bringup of msm8994 on 3.18 kernel sauce: https://github.com/sonyxperiadev/kernel/pull/972 (for AOSP)
yeah I basically read it as qualcomm have bad after market support
zacharias.maladroit said:
and there's the (close to complete) bringup of msm8994 on 3.18 kernel sauce: https://github.com/sonyxperiadev/kernel/pull/972 (for AOSP)
Click to expand...
Click to collapse
I might have something interesting to build then and I can stop lounging around
any news for official aosp 8.0 release for z5?
Enviado desde mi SGP712 mediante Tapatalk