Related
Hello guys
Based on my investigation several time ago,,I was look up some ROM and development for Triumph n X6 from several forums
For now,,development of Moto Triumph stepping far from Huawei X6,,I was looked some new update ROM especially ICS ROM
I want asking to someone who know about development
What different Triumph from X6?just CDMA >< GSM or more??Is Motorola have individual brand build?
Is possible to get flash ROM based from Triumph??
I'm asking because I found Triumph have AOKP ICS developers
Since edowar who develop AOSP ICS gone,,X6 device development for AOSP ICS stuck at alpha5,,
Sorry if I like blaming or flaming developers,,but I just want to know if X6 can use Triumph ROM or not
Sent from my CSL-MI410 using Tapatalk 2
I don't agree with you. Triumph not stepping far from X6. Both features have the same progress, even triumph camera capturing still not work on ICS while ours already work.
Some devs... Tj and ardX still in progress for AOSP ICS for our device, we also have a step forward for camera. Zuk also available to port it, and I think he will definitely port it to any other rom for this ICS. But be patient, they're working on it. They work to make camera work perfect with video and not interfere with wifi functionality also. After that, here... will be more ICS roms port and mod... Zuk, elol and other porter will get additional spirit to port and may be me also .
X6 can use Triumph rom, but it will not get the signal and may be you can't use touch screen also. Need some touch to port it, but then the features still lack of camera. Camera is a must for me and for some of us. I can't use ICS if camera not work.
CacingKalung said:
I don't agree with you. Triumph not stepping far from X6. Both features have the same progress, even triumph camera capturing still not work on ICS while ours already work.
Some devs... Tj and ardX still in progress for AOSP ICS for our device, we also have a step forward for camera. Zuk also available to port it, and I think he will definitely port it to any other rom for this ICS. But be patient, they're working on it. They work to make camera work perfect with video and not interfere with wifi functionality also. After that, here... will be more ICS roms port and mod... Zuk, elol and other porter will get additional spirit to port and may be me also .
X6 can use Triumph rom, but it will not get the signal and may be you can't use touch screen also. Need some touch to port it, but then the features still lack of camera. Camera is a must for me and for some of us. I can't use ICS if camera not work.
Click to expand...
Click to collapse
whatabout u8800? zuk has some roms from there as well. and u8800 has ICS based on u8860 (huawei honor).
huawei honor's chipset is MSM8255T, mi410 is MSM8255. I've posted the link to the files, but the firmware is only in .app file.. no idea how to extract or turn it into .nb0 to extract the libs and stuff..
cheezzzz said:
whatabout u8800? zuk has some roms from there as well. and u8800 has ICS based on u8860 (huawei honor).
huawei honor's chipset is MSM8255T, mi410 is MSM8255. I've posted the link to the files, but the firmware is only in .app file.. no idea how to extract or turn it into .nb0 to extract the libs and stuff..
Click to expand...
Click to collapse
The features here meant for hardware related with the kernel. Any port need specific kernel to those device it self, including ours. Ofcourse we can use some library from identic device hardware, but kernel drive them.
CacingKalung said:
The features here meant for hardware related with the kernel. Any port need specific kernel to those device it self, including ours. Ofcourse we can use some library from identic device hardware, but kernel drive them.
Click to expand...
Click to collapse
so does this mean to get a working ICS rom lets say aurora ICS which is derived from U8860, we need to rebuild our kernel that will function on our devices? because kernels are device specific right?
if that's the case how do people port across different OS ie SE mini pro running eclair with an unofficial GB port? is it because the kernel remains the same?
cheezzzz said:
so does this mean to get a working ICS rom lets say aurora ICS which is derived from U8860, we need to rebuild our kernel that will function on our devices? because kernels are device specific right?
if that's the case how do people port across different OS ie SE mini pro running eclair with an unofficial GB port? is it because the kernel remains the same?
Click to expand...
Click to collapse
Correct me if I'm wrong....
Kernel need to build to work on specific device and specific android version, what ever kernel version is, that's so far what I know. Some drivers integrated in kernel, one of them is touch driver which related with touch panel hardware type.
To port rom from another device, we "just" pull the framework of the source rom and push it to the our android version which the framework will work. Of course with some additional "touch" to make it perfect.
To develop a rom from another device, not just port but we have to customize (made change and build from source) our device kernel to work with a destination android version. Also build from source for some libraries and drivers because of related things.
What things should be customize in kernel or libraries... well... I'm not a dev.
Owh I'm sorry mate,,actually I just looking for development team for Motorola,,they have development team focus on ICS build
Sorry if I mistake because I don't know much about this,,our device have many developers to port/make ROM and modified something
But so far I looked,,our device doesn't have development team like Triumph,,sorry if I wrong
I just want to know,how much important development team works/personal developer for ROM build
Cz I think it would be better if our device have development team
Once again mate,sorry if I wrong and asking fool
Sent from my CSL-MI410 using Tapatalk 2
Arya_3RDNumber said:
Owh I'm sorry mate,,actually I just looking for development team for Motorola,,they have development team focus on ICS build
Sorry if I mistake because I don't know much about this,,our device have many developers to port/make ROM and modified something
But so far I looked,,our device doesn't have development team like Triumph,,sorry if I wrong
I just want to know,how much important development team works/personal developer for ROM build
Cz I think it would be better if our device have development team
Once again mate,sorry if I wrong and asking fool
Sent from my CSL-MI410 using Tapatalk 2
Click to expand...
Click to collapse
You're not asking fool... I agree with you if it will be great if we have devs team to work and focus on ICS... but we can't push devs, since they also have their real work in real world . But what we have now are Tj and ardX are still on the path of developing ICS for our device. So for now, they are already a team.
CacingKalung said:
You're not asking fool... I agree with you if it will be great if we have devs team to work and focus on ICS... but we can't push devs, since they also have their real work in real world . But what we have now are Tj and ardX are still on the path of developing ICS for our device. So for now, they are already a team.
Click to expand...
Click to collapse
Yes mate,,,absolutly great since I know some device with lower quality than our device got ICS ROM (Before using CSL,I'm Galaxy Ace user and I look at SGA forums,they have Both ICS AOSP&AOKP Build n some ICS ROM Ported)
It's mean if ICS running on our device,absolutly more perfects than the other device
Ardx said,,he still resync repo,,I also asking about this on andro-id forum
Bro Ardx was told me it's repo AOKP
It means he fully rebuild this ICS project,am I right?
Sent from my CSL-MI410 using Tapatalk 2
Arya (quite Indian Name) ... there is one team, what CK mention already who is working on ICS and that is of TJ and adrX, there is another team for our device, that is of ZUK and Whyzee, they worked together for many GB ROMS . May be after getting custom kernel for ICS from Napstar and after getting ICS ROM from adrX, they can port other ICS ROM too. Even elol may team up with them.
Also we can expect MIUI ICS from CK and FR. for FCKR software they already worked together ...
vivekb said:
Arya (quite Indian Name) ... there is one team, what CK mention already who is working on ICS and that is of TJ and adrX, there is another team for our device, that is of ZUK and Whyzee, they worked together for many GB ROMS . May be after getting custom kernel for ICS from Napstar and after getting ICS ROM from adrX, they can port other ICS ROM too. Even elol may team up with them.
Also we can expect MIUI ICS from CK and FR. for FCKR software they already worked together ...
Click to expand...
Click to collapse
Yes mate,,,most important is "together",,I just want to know(sorry maybe I really2 fool) how much best dev team / personal dev.
Now I know althought we haven't real dev team,at least we have people who cares with they great works to develop our device,,
Sadly I can't doing anything to develop our device,,because I have many limitation mate,,maybe next time I just can be tester
Sent from my CSL-MI410 using Tapatalk 2
The Jelly Bean ROM's are great, but for me there's just too many bugs.
We have the ICS source now and I'd love a stable CM9 build. Unfortunately it looks like attn1 may have moved on, and all the other devs seem to be just working on JB.
Dude your not alone...count me in for that...if i knw step by step guide to at least to compile an AOSP kernel I would do it now
i ll waiting too but however stable cm9 or cm 10 doesnt exisit by now
Be patient
No I'm waiting for CM9 o CM10 too for a valid porting of MIUI
Everyone is waiting for CM9 but we need a kernel to get everything working propably! Our devs are working on it but they have a life, too. Don't expect sb to do a one-man Jesus show here;D Be patient, we will get fully working CM9 when kernel boots up
And in the future you can post stuff like this in our famous OFF-Topic-thread Keeps the G-Sec clean
Raithmir said:
The Jelly Bean ROM's are great, but for me there's just too many bugs.
We have the ICS source now and I'd love a stable CM9 build. Unfortunately it looks like attn1 may have moved on, and all the other devs seem to be just working on JB.
Click to expand...
Click to collapse
It doesn't really matter much which ROM to make - ICS based or JB based CM. Because to make a proper and stable ROM, all you need is to make a stable AOSP\AOKP compatible kernel (and we still don't have one).
PS: AFAIK CM team wont add CM9 support for any more devices, i.e. if they will make a CM for our IncS it will be JB based CM10 and not CM9.
I thought that once we had sources, the kernel would be pretty easy, but then I don't know much about it. Who is working on the kernel?
I also thought that CM would only support a phone if source was available. Since we only have ICS source right now, that would rule out CM10 wouldn't it?
Sent from my Incredible S using Tapatalk 2
Raithmir said:
I thought that once we had sources, the kernel would be pretty easy, but then I don't know much about it. Who is working on the kernel?
I also thought that CM would only support a phone if source was available. Since we only have ICS source right now, that would rule out CM10 wouldn't it?
Sent from my Incredible S using Tapatalk 2
Click to expand...
Click to collapse
Many of the CM10 ROMs don't have manufacturer source for JB (only ICS) therefore it is safe to assume that our ICS kernel can be used with CM10.
If we want official support we need a maintainer
The maintainer for the 7x30 HTC devices like ours, dhd, desire s etc
Our maintainer, Kali- moved on to Sony devices iirc
If we ask nexx and nk111 (cm devs from desire s) nicely maybe they might build for us
Sent from my HTC Incredible S
I understand that attn1 is still our maintainer.
weaselEST said:
I understand that attn1 is still our maintainer.
Click to expand...
Click to collapse
Orly? Anyone heard from him/her?
Sent from my HTC Incredible S
I sent him a tweet some time ago after he bought S3 and I wrote something like this: "So you're not the maintainer for IncS anymore". And he replied "What makes you think that" . He still owns a vivo and a vivos.
Sent from my Incredible S using xda premium
weaselEST said:
I sent him a tweet some time ago after he bought S3 and I wrote something like this: "So you're not the maintainer for IncS anymore". And he replied "What makes you think that" . He still owns a vivo and a vivos.
Sent from my Incredible S using xda premium
Click to expand...
Click to collapse
That's good, hopefully he can compile CM10 soon and bring official support for CM9/10
I would be very grateful of that
I really want CM9 without any bug. Even now im usin CM7! i didt find any ICS AOSP rom. So im thinking about change my phone
Plz coock it...
Sent from my Incredible S using Tapatalk 2
Hey guys, I'm thinking of compiling a CM ROM from source next month (have to wait for data cap to reset) and was wondering what you guys would prefer, a significantly more stable CM9, or a more buggy (and more headaches for me) CM10 ROM? I personally would prefer to do a CM9 ROM since it would be easier to support and fix bugs on, since we already have relatively stable, working builds of AOSP ICS. CM10 would be great as well, but it would be much harder for me to support, since I would be the second dev for the Inc S to build a JB ROM from source for us. I just don't think I have the know-how to be the only one working on it, and the only one fixing bugs and whatnot, without any already working source code to view and compare.
So I could compile CM9.2 stable, and we would have the latest CM9 code using kaijura's IceColdSandwich as a reference. I would have an easier time supporting the ICS ROM since I would have working source code to compare and review. Also, it would be significantly more stable simply due to the fact that multiple devs for our device have already worked on it. I'm sure I'd be able to fix bugs and support it fairly easily, other devs are the best resource around
Or I could compile a CM10 ROM. I would have to take device proprietary files from nik's JB ROM's, which would mean my compiled ROM would share a lot of the same bugs our current JB ROM's already have. I could support and fix bugs in CM10, it would just take longer and be harder to do. Nothing's impossible though, so if that's what the community wants, then that's what I'll build!
So what do you guys think? CM10 or CM9?
It's your time and effort you do what Rom you want to do. Any Rom would be great!
Sent from my HTC Incredible S using Tapatalk 2
vizzy said:
It's your time and effort you do what Rom you want to do. Any Rom would be great!
Sent from my HTC Incredible S using Tapatalk 2
Click to expand...
Click to collapse
I'm torn between the two! On the one hand, I want a stable ROM which would be CM9, but I also love that JellyBean goodness. I've also seen some people here that simply want a stable CM9 that's up to date, and other's that want the latest CM10 despite bugs. That's the point of this thread
I would tell u is that first for cm9 when we get a stable awesome cm9 for sure it will be easy to get a cm10... btw are u going to build a kernel?
My vote goes towards CM9! been using codename for the past couple months and although i'm enjoying all the new features, i still find myself yearning for a rock solid & stable ASOP based build.
Sent from my Incredible S using Tapatalk 2
linezero said:
I would tell u is that first for cm9 when we get a stable awesome cm9 for sure it will be easy to get a cm10... btw are u going to build a kernel?
Click to expand...
Click to collapse
I could give it a try, but if nik and others couldn't get a 3.0 kernel up and running for AOSP, then I'll have a damn hard time. I'd prefer to have someone else make the new kernel, I don't know much about compiling them. Till then, I would just use X-ICS4.0 for the kernel.
Make a CM9, CM10 would have in the end too much bugs and they would just chance again. I'm waiting for a stable cm9 anyway
Sent from my HTC Incredible S using xda app-developers app
Kernel 3, Cm10 got my vote
sent from my jellybean device
ZaySk said:
Hey guys, I'm thinking of compiling a CM ROM from source next month (have to wait for data cap to reset) and was wondering what you guys would prefer, a significantly more stable CM9, or a more buggy (and more headaches for me) CM10 ROM? I personally would prefer to do a CM9 ROM since it would be easier to support and fix bugs on, since we already have relatively stable, working builds of AOSP ICS. CM10 would be great as well, but it would be much harder for me to support, since I would be the second dev for the Inc S to build a JB ROM from source for us. I just don't think I have the know-how to be the only one working on it, and the only one fixing bugs and whatnot, without any already working source code to view and compare.
So I could compile CM9.2 stable, and we would have the latest CM9 code using kaijura's IceColdSandwich as a reference. I would have an easier time supporting the ICS ROM since I would have working source code to compare and review. Also, it would be significantly more stable simply due to the fact that multiple devs for our device have already worked on it. I'm sure I'd be able to fix bugs and support it fairly easily, other devs are the best resource around
Or I could compile a CM10 ROM. I would have to take device proprietary files from nik's JB ROM's, which would mean my compiled ROM would share a lot of the same bugs our current JB ROM's already have. I could support and fix bugs in CM10, it would just take longer and be harder to do. Nothing's impossible though, so if that's what the community wants, then that's what I'll build!
So what do you guys think? CM10 or CM9?
Click to expand...
Click to collapse
cm9 bro! because ics kernel source is out and bugs can be fixed!
Yeah. CM9 would be OK for me too. I can help with testing if needed.
But what would be those great JB features we would be missing out? Sry I haven't been following the differences between 4.0 and 4.1.
IncS community is desperate for at least one fully functional, bugless AOSP ROM, so my vote goes for CM9
CM9 bro..wishing for bugless one.. gud luck..
Sent from my HTC Incredible S using xda app-developers app
My 2 cents.
CM9. Kernel sources for ICS has been release by HTC and ANY AOSP rom that is stable would be very welcome in our community.
(I know there is gingerbread roms.. But.. Its ginger bread..)
Jelly Bean is nice and all,
But the odds of getting a stable AOSP rom are much higher with cm9.
CM9 I would say. I hope you can fix data problems for Vodafone NL users. We always have problems with data connection on AOSP ROMs.
CM9 would be great....!!
Its great to see devs are enthusiasticaly working on Roms..!!
You are the one dude...
Jst for info u might already aware of
This thread
http://forum.xda-developers.com/showthread.php?t=1914015
CM10 test build
Sent from my HTC Incredible S using xda app-developers app
my vote a CM9 ASOP rom and bugless
Sent from my Incredible S using xda premium
naathaanb96 said:
cm9 bro! because ics kernel source is out and bugs can be fixed!
Click to expand...
Click to collapse
Totally agree. I don't like much sense ROMs, CM9 with working camera and camcorder would be perfect!
Thanks ZaySk
CM9!!!!
ZaySk said:
Hey guys, I'm thinking of compiling a CM ROM from source next month (have to wait for data cap to reset) and was wondering what you guys would prefer, a significantly more stable CM9, or a more buggy (and more headaches for me) CM10 ROM? I personally would prefer to do a CM9 ROM since it would be easier to support and fix bugs on, since we already have relatively stable, working builds of AOSP ICS. CM10 would be great as well, but it would be much harder for me to support, since I would be the second dev for the Inc S to build a JB ROM from source for us. I just don't think I have the know-how to be the only one working on it, and the only one fixing bugs and whatnot, without any already working source code to view and compare.
So I could compile CM9.2 stable, and we would have the latest CM9 code using kaijura's IceColdSandwich as a reference. I would have an easier time supporting the ICS ROM since I would have working source code to compare and review. Also, it would be significantly more stable simply due to the fact that multiple devs for our device have already worked on it. I'm sure I'd be able to fix bugs and support it fairly easily, other devs are the best resource around
Or I could compile a CM10 ROM. I would have to take device proprietary files from nik's JB ROM's, which would mean my compiled ROM would share a lot of the same bugs our current JB ROM's already have. I could support and fix bugs in CM10, it would just take longer and be harder to do. Nothing's impossible though, so if that's what the community wants, then that's what I'll build!
So what do you guys think? CM10 or CM9?
Click to expand...
Click to collapse
My request would be neither CM9 nor CM 10.... it will be great if you can work on Kernel Version 3.... Becz that is the only roadblock for us for Jelly Bean and would open doors for may developers to come up with fresh and exciting jelly bean ROMs.....Why stay behind the world guys... lets target Jelly bean step by step.....who knows if you start working on kernel it may really turn out to be good.....Try for kernel bro......all the best.. try to compile it from source....
A rock solid cm9 would be great!
Sent from my Incredible S using xda app-developers app
Is there any ROM that has pdroid 2.0 (or openpdroid, but but this seems less stable) preinstalled?
(I know there is a n autopatcher thread..., but I wonder why no one add this more-than-essential feature to their ROMs)
thanks
I don't believe so, it is something that they would throw in their main feature list if they did. Also PDroid doesn't even officially support the i9305 but I guess you can try the I9300 version at your own risk.
Sent from my GT-I9305 using xda premium
since cm is not yet available for the 9305, the autopatcher can't do the job either...
openpdroit seems a good intention, but the ROM brewers seem not to recognize the tool
LordValen said:
since cm is not yet available for the 9305, the autopatcher can't do the job either...
openpdroit seems a good intention, but the ROM brewers seem not to recognize the tool
Click to expand...
Click to collapse
Cyanogenmod (unofficial - http://forum.xda-developers.com/showthread.php?t=2084604) and Liquid Smooth (official - http://forum.xda-developers.com/showthread.php?t=2149746) are released for the I9305
positive
This will be possible, according to the developers, see
http://forum.xda-developers.com/showthread.php?t=1923576&page=66
anyone also intersted please support collegedev
This sound amazing. I liked pdroid for the SGS2. The only thing missing now is a good working cm10.1
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