Related
i hope all the bugs are fix the develop. i know its to hard to develop..
thnx to many developer...hooray.
Just flash the latest aokp rom its genius and i dont have any issues with it, its working even faster than the stock rom on my double speeded gt-p6200... have fun. By the way, there will never be a final ics on custom roms, there is always an idea to make it better ;-)
Sent from my GT-P6200 using XDA
marvz098 said:
i hope all the bugs are fix the develop. i know its to hard to develop..
thnx to many developer...hooray.
Click to expand...
Click to collapse
There is no such thing as 'bug free' buld that is why we always have new versions(builds) untill the dev team decides to move on to something new. Therefore I would imagine there won't be 'Final' ICS untill Android 5 (Jellybean) available and the dev team decides to move on to Jellybean (assuming many of us still sticking to our G-tab 7 and plenty developers still willing to crack one for us.)
However the latest builds of ICS are very stable and suitable for daily use.
yappoe said:
There is no such thing as 'bug free' buld that is why we always have new versions(builds) untill the dev team decides to move on to something new. Therefore I would imagine there won't be 'Final' ICS untill Android 5 (Jellybean) available and the dev team decides to move on to Jellybean (assuming many of us still sticking to our G-tab 7 and plenty developers still willing to crack one for us.)
However the latest builds of ICS are very stable and suitable for daily use.
Click to expand...
Click to collapse
You right, i'm using AOKP for my daily use. 3G,wifi, active sync exchange, dropbox all of them working smoothly only usb tethering not working in milestone #5 but overall great rom...
Sent from my GT-P1000 using Tapatalk 2
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
Hello everyone, Like everyones know Galaxy mini (s5570) received kitkat/Jelly Bean(cyanogenmod 11/10.2[unofficial]) , since samsung stopped supporting this device devs've started a hard work to update this device.
All AndroidArmv6 Team specially @erikcas , @yajnab , @psyke83 (remember if i forget you and sorry)
and at the moment we're getting stable rom of kitkat and already stable jellybean
Kitkat 4.4.x:
Whats Working ??
everything
what is wrong on this rom ?
batery drains too faster this problems contains in many others kk ROMs including devices . ask google to fix .. xd
Jelly Bean 4.3.x:
Whats working ??
everything
Whats wrong on this rom ?
only small things
the rom was in alpha stage, but already is stable, some people using it daily.
At the moment Jelly beam 4.3 was a amazing rom for daily, lastest's releases from jenkins are incredible.
where i can find more info ?
- you can search for yajnab Tread in Original development section.
Where i can download the rom ?
- look for Jenkins.androidarmv6.org/view/Android/Builds (download only "TASS" builds)
you can look too for Review.androidarmv6.org (see it for reviews of fixed etc)
Where can i find Gapps ?
- i think no was a full package for Gapps (no much space left in the system)
Whats never going to be fixed ?
- google now voice search (dont wait for it, never going to be fixed, why ? device its armv6 google now voice search works only in armv7 .) and others few things
batery- KitKat really takes so much batery!
do thanks for devs of armv6 Team.
if possible donate or pay a drink for their
if you have anything that can help with the development post here. (fixes solutions etc)
i stopped testing with this Device since i buyed a Lg optimus L5(E612)
but i'm here you can use my PM to help (question possible solutions littles things too)
and sorry for my slower updates, its why i'm not at home theses days and i have only 5% of free time to check the forum.
Hot News!!! :
all changes are going to be merged so if any build have a old bug dont worry . only report .
psyke83 said:
Please folks, always take the time to upload logs. You appear to have no active developer who owns a Mini at this moment, so we (other androidarmv6 developers) rely exclusively on users to assist in fixing bugs specific to your device.
Click to expand...
Click to collapse
Link to CyanogenMod 11 for Galaxy Mini thead
AntiBillOS said:
Yes
Click to expand...
Click to collapse
So any progress? Just interested.
ast00 said:
So any progress? Just interested.
Click to expand...
Click to collapse
Working hard on get it builded.
AntiBillOS said:
Working hard on get it builded.
Click to expand...
Click to collapse
so any possible fix for android 4.3 cm 10.2 camera ? i think people forget it
AfonsoADR said:
so any possible fix for android 4.3 cm 10.2 camera ? i think people forget it
Click to expand...
Click to collapse
I even don't want to look at Android 4.3 coz it mutch laggy than 4.2*. Also I have no mutch free time, so I focused at Android 4.4.
AntiBillOS said:
I even don't want to look at Android 4.3 coz it mutch laggy than 4.2*. Also I have no mutch free time, so I focused at Android 4.4.
Click to expand...
Click to collapse
so contiue so. really no bigger diference of android 4.2 to 3 .
looks better work in 4.4 . ur correct . really looks lost time work in cm 10.2 i see this now
I've been looking at the Jenkins build bot from androidarmv6 team. It seems that they haven't managed any successful builds either.
programmargorp said:
I've been looking at the Jenkins build bot from androidarmv6 team. It seems that they haven't managed any successful builds either.
Click to expand...
Click to collapse
I don't it for boot.
on general kitkat just need minimum 512MB RAM right?? for JB need 1GB ram ??
sorry for my english
Guys,I dont want to destroy your hope but, I have 4.4 on my XT and RAM manager is still pretty same as it was on CM10.2 ..still 300mb +- RAM in use.
Maybe is minimum requirement 512MB but mini have only 279MB.
Villeness said:
Guys,I dont want to destroy your hope but, I have 4.4 on my XT and RAM manager is still pretty same as it was on CM10.2 ..still 300mb +- RAM in use.
Maybe is minimum requirement 512MB but mini have only 279MB.
Click to expand...
Click to collapse
384MB* About 105MB of it is system reserved, which is not accounted by the requirements.
Why are we worried? JB needs 1gb and it ran on Mini. KK needs half of it, it should run just fine.
android 4.4 was made by google optimized to take less ram memory.
will work better than cm10-10.1-10.2 .
galaxy mini no have a totally hardware support but no have problem try right ?
As my Gio just died, I'm back to reading these forums for the sake of keeping my brother's Mini decent now, haha.
Speaking of which, yeah, I'm curious how CM11 will run, seeing how anything up to CM10 runs smoothly (CM10.1 not so much, CM10.2 horribly).
We'll get a surprise. Two possibilities is that it's either going to run so horribly that we'll not even consider using it, or it'll be as nice and smooth as CM9 is if not better (Although I wouldn't count on that).
Harakhti said:
As my Gio just died, I'm back to reading these forums for the sake of keeping my brother's Mini decent now, haha.
Speaking of which, yeah, I'm curious how CM11 will run, seeing how anything up to CM10 runs smoothly (CM10.1 not so much, CM10.2 horribly).
We'll get a surprise. Two possibilities is that it's either going to run so horribly that we'll not even consider using it, or it'll be as nice and smooth as CM9 is if not better (Although I wouldn't count on that).
Click to expand...
Click to collapse
cyanogenmod 11 promisses , why kitkat was optimized low memory and more other optimizations.
lastest release of cm 10.1 was better than cyanogenmod 10 .
kitkat will run great on mini. i'm 100% of this
Cheer up, Jenkins seems to be able to build again.
For those who are interested in knowing about our progress.
http://jenkins.androidarmv6.org/view/Android/builds
I hope soon we will see a tass cm11 there :laugh:
cyanogenmod 11 on LG P500
1st release of armv6 device P500 (LG optimus one) was received a first cyanogenmod 11 : submission-test .
check'out here : http://jenkins.androidarmv6.org/job/submission-test/755/
now cooper(Galaxy ACE) receive submission test : http://jenkins.androidarmv6.org/view/Android/job/submission-test/757/
Sucess
Galaxy 5 received Cyanogenmod 11 : http://jenkins.androidarmv6.org/view/Android/job/android-experimental/340/
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