Database Develop

Android 4.4 ROM

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

Why no 3.4.x based kernel?

Dear forum members. I would like to ask why we cant have 3.4 based kernels? Htc one x with almost identical hardware has it..and many other devices using the same processor and other hardware have it too. What is the requirements for 3.4 kernel? I see a lot of developers have put amazing effort for bringing new kernels to us that has greatly improved the performance of our device but we dont have 3.4 based kernels. I would love to know if i would ever get usb otg on my device. Now that nvidia has released a new source for supporting kitkat, is there a chance that we could get 3.4 based kernel anytime soon? Thanks.
Sent from my Optimus 4X HD using Tapatalk

saurav112214 said:
Dear forum members. I would like to ask why we cant have 3.4 based kernels? Htc one x with almost identical hardware has it..and many other devices using the same processor and other hardware have it too. What is the requirements for 3.4 kernel? I see a lot of developers have put amazing effort for bringing new kernels to us that has greatly improved the performance of our device but we dont have 3.4 based kernels. I would love to know if i would ever get usb otg on my device. Now that nvidia has released a new source for supporting kitkat, is there a chance that we could get 3.4 based kernel anytime soon? Thanks.
Sent from my Optimus 4X HD using Tapatalk
Click to expand...
Click to collapse
Have you seen kholks kernel? its 3.4
Its a big undertaking with little benefit compared to the amount of work put in, It can be great if everything is stable and working but it normally requires a team of developers hired by LG to pull it off.

JoinTheRealms said:
Have you seen kholks kernel? its 3.4
Its a big undertaking with little benefit compared to the amount of work put in, It can be great if everything is stable and working but it normally requires a team of developers hired by LG to pull it off.
Click to expand...
Click to collapse
Yes I have seen Kholks kernel, it is 3.4 but apart from that (with all due respect) its not working as it should (RIL, Mobile data, otg, battery drain etc). Moreover it looks like he has abandoned the project and no other projects are 3.4 based.
I did not know that it requires a team of developers hired by LG to pull it off. I thought it was just do able by developers here because they brought us all the amazing android goodies. Sorry for being noob. Since we know that LG is crap in providing support to devices, is it safe to assume that we will never be getting 3.4 version of kernel?

saurav112214 said:
Yes I have seen Kholks kernel, it is 3.4 but apart from that (with all due respect) its not working as it should (RIL, Mobile data, otg, battery drain etc). Moreover it looks like he has abandoned the project and no other projects are 3.4 based.
I did not know that it requires a team of developers hired by LG to pull it off. I thought it was just do able by developers here because they brought us all the amazing android goodies. Sorry for being nobb. Since we know that LG is crap in providing support to devices, is it safe to assume that we will never be getting 3.4 version of kernel?
Click to expand...
Click to collapse
It doesnt require LG but to get it completely polished to OEM standard a team of that size is very handy. We may see another independently developed 3.4 kernel, nvidia has dropped their 3.4 kernel source for tegra which would make it easier, id personally rather backport some of its improvements and features than port it to our device

JoinTheRealms said:
It doesnt require LG but to get it completely polished to OEM standard a team of that size is very handy. We may see another independently developed 3.4 kernel, nvidia has dropped their 3.4 kernel source for tegra which would make it easier, id personally rather backport some of its improvements and features than port it to our device
Click to expand...
Click to collapse
Would be great to get the 3.4 kernel from nvidia used as base for our P880. Great idea !

saurav112214 said:
Dear forum members. I would like to ask why we cant have 3.4 based kernels? Htc one x with almost identical hardware has it..and many other devices using the same processor and other hardware have it too. What is the requirements for 3.4 kernel? I see a lot of developers have put amazing effort for bringing new kernels to us that has greatly improved the performance of our device but we dont have 3.4 based kernels. I would love to know if i would ever get usb otg on my device. Now that nvidia has released a new source for supporting kitkat, is there a chance that we could get 3.4 based kernel anytime soon? Thanks.
Sent from my Optimus 4X HD using Tapatalk
Click to expand...
Click to collapse
HTC One X doesn't have a 3.4.x kernel on Tegra 3. "Android 4.2.2 Sense 5 - kernel 3.1.x

CM11??

Hey
Just wondering if there is any hope of getting CM11 for this tablet? I recently flashed it to my mega i527M and love it would love to extend over to my tablet, I am open to doing any beta testing I wish I could help program but will help troubleshoot where I can or uncover bugs
Cheers
Shadow

shadow1179 said:
Hey
Just wondering if there is any hope of getting CM11 for this tablet? I recently flashed it to my mega i527M and love it would love to extend over to my tablet, I am open to doing any beta testing I wish I could help program but will help troubleshoot where I can or uncover bugs
Cheers
Shadow
Click to expand...
Click to collapse
Edit: this all relates to the i957 and P7320 variants, and not the P7300/P7310
The p5att device (i957) was removed from the msm8660 kernel when CM10.1 was created. I've been trying to get some simple things like the display working using some source from CM10 without much success :-\ So I'm thinking if there isn't the next version of JB working, KitKat is looking unlikely for the time being, unless we can get some more devs to help.

CL0SeY said:
Edit: this all relates to the i957 and P7320 variants, and not the P7300/P7310
The p5att device (i957) was removed from the msm8660 kernel when CM10.1 was created. I've been trying to get some simple things like the display working using some source from CM10 without much success :-\ So I'm thinking if there isn't the next version of JB working, KitKat is looking unlikely for the time being, unless we can get some more devs to help.
Click to expand...
Click to collapse
Why, isn't it possible to backport the old stuff ?

white-energy said:
Why, isn't it possible to backport the old stuff ?
Click to expand...
Click to collapse
Most of the issues seem to be around the display driver and the Qualcomm msm8660 implementation in jb4.2. that combined with nothing else which seems to use the same display panel means no graphics or even worse an MSM core dump. I'm not sure how to debug those either... I did manage to get log output from the kmesg but it didn't help me much, others may have better luck. Half the fun is getting it to compile in the first place...

Well, we all hope that someone will make a port of CM11
AND SOON

[Dev][Experimantal][Kernel][ION] nAa-ION Kernel

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

[Q] Your though about Android L with ART as default

So, finaly, a new Android OS will release tommorow. Because we all know it will be ART by default, will it be possible to making it work on the HP Touchpad or do you think it will be an hardcore challenge ? I fear this build doom the next update of Cyanogenmod or Evervolv for Touchpad. What do you think about this dev ? Will the HP Touchpad be able to run Android L (Lolipop ?) in the next 3-8 month before the next Android release came out after L ? What's the status or ART on Touchpad ? Thank you for your answer guys and continue your great work. :good:

Never under estimate the work of the developers who maintain our Touchpads. Everyone was amazed with the original install of Android and through a lot of doubt we have a working 3.4 kernel and pretty solid Kit Kat 4.4.x builds.
I'd not be one bit surprised at a fully functional version of any update with the amazing and hard work these developers have already shown.

Atari-San said:
So, finaly, a new Android OS will release tommorow. Because we all know it will be ART by default, will it be possible to making it work on the HP Touchpad or do you think it will be an hardcore challenge ? I fear this build doom the next update of Cyanogenmod or Evervolv for Touchpad. What do you think about this dev ? Will the HP Touchpad be able to run Android L (Lolipop ?) in the next 3-8 month before the next Android release came out after L ? What's the status or ART on Touchpad ? Thank you for your answer guys and continue your great work. :good:
Click to expand...
Click to collapse
Well they custom-wrote a 3.4 kernel for the HP Touchpad, so in theory it should be able to handle future iterations of Android, after a lot of work. Maintaining older devices like this can become problematic though. I'm not expecting Lollipop any time soon and wouldn't be surprised if the devs didn't bother with it at all for the Touchpad.

4GivenByChrist said:
Never under estimate the work of the developers who maintain our Touchpads. Everyone was amazed with the original install of Android and through a lot of doubt we have a working 3.4 kernel and pretty solid Kit Kat 4.4.x builds.
I'd not be one bit surprised at a fully functional version of any update with the amazing and hard work these developers have already shown.
Click to expand...
Click to collapse
I've tried CM11 and Evervolv with 3.4 kernel and I get way too many SOD's on both of them...even with lock screen turned off

I'm running Evervolv 4.4.4 with no issues. The ROM is very smooth and fast (I installed the old Seeder app and it seems to be more than a placebo on Evervolv). I switched to ART and it was very unstable. It took a long time for the first boot and a lot of stuff kept crashing. I hope the Devs fix ART soon, since it will be the default in Android L. However, I do hope to have a new Galaxy Tab S by then
Sent from my Touchpad using Tapatalk