This it's one of the most active dev groups on XDA. Hope we get a feel of Jolla Sailfish too when it's eventually released.
Sent from my HTCSensation using xda app-developers app
I really don't know if I see it happening we are starting to slow down and now we got 4.4.3 coming most devs will be all over that
Short answer is yes and no:
Jolla (from rumors) was also working on an application-layer shell of Sailfish for use on phones without switching to the OS as a whole.
The rom itself is only a question if the chipset is supported, and if the drivers are available, and if it's possible to unite them to make the ROM...
I did hear it uses CM10.1 as a base.
Edit: Here is news about Sailfish OS http://forum.xda-developers.com/jol...android-devices-release-t2696409/post51417864
Related
Hi all,
We need Developers to build CM for Micromax A110...it has a forum on XDA....and we've got open source device tree:
http://forum.xda-developers.com/showthread.php?t=2324246
Please, it's a request to all the developers on XDA to help us port CM to our device...
Me and all other users will provide all the support we can...
Eagerly waiting for a Reply...
I will help for our community
Sent from my Micromax A110 using xda premium
As a user of A110 , I am also requesting to help our development team ....pls
Sent from my Micromax A110 using xda app-developers app
Here's a CM9 development on mt6577 http://forum.xda-developers.com/showthread.php?t=2246892
Sent from my Micromax A110 using xda app-developers app
Rahulsingh190 said:
Here's a CM9 development on mt6577 http://forum.xda-developers.com/showthread.php?t=2246892
Sent from my Micromax A110 using xda app-developers app
Click to expand...
Click to collapse
Can you confirm CM9 and CM 10 require similar specs?
Then we can use the source tree used there to edit this MMX one accordingly...
Since varun.chitre has stopped we have to get this done by ourselves....
Sent from my Micromax A110 using Tapatalk 4 Beta
Guys with out the full kernel source which the OEM refuses to provide your not gonna get very far. And the source for the MTK chip is not the full source. We are in talks now about what to do with these forums as they break our gpl rules.
Wayne Tech Nexus
zelendel said:
Guys with out the full kernel source which the OEM refuses to provide your not gonna get very far. And the source for the MTK chip is not the full source. We are in talks now about what to do with these forums as they break our gpl rules.
Wayne Tech Nexus
Click to expand...
Click to collapse
I guess the forum would be closed then...Great...I should jump towards my One then....
Sent from my HTC One 801e using Tapatalk 4 Beta
This ain't no normal phone.
Rahulsingh190 said:
Here's a CM9 development on mt6577 http://forum.xda-developers.com/showthread.php?t=2246892
Sent from my Micromax A110 using xda app-developers app
Click to expand...
Click to collapse
The version you stated uses the same thunderzap kernel by vatun.chitre[most part of it]..and it will work without much problem because cm9 is based on 4.0.4 and thunderzap is based on mmxa110 4.0.4 kernel sources which was released by mmx at the first place....and we still do not know if they will release JB kernel sources or not…so I am not sure if cm10 works will go the same way as of the cm9....I will try to compare the two kernels later today though......
Sent from my HTC One 801e using Tapatalk 4 Beta
This ain't no normal phone.
Guys for now we should first CM 9 booting with the sources available. Then we should think of CM 10.I m learning these things now, so I can contribute something valuable
Sent from my Micromax A110 using xda app-developers app
Rahulsingh190 said:
Guys for now we should first CM 9 booting with the sources available. Then we should think of CM 10.I m learning these things now, so I can contribute something valuable
Sent from my Micromax A110 using xda app-developers app
Click to expand...
Click to collapse
CM9 is not a problem, IMO. I think If someone just starts it it can be completed within a week[atleast boot].. Because everything is available.[ kernel source + CM sources + device tree]. But CM10 requires 4.2 kernel sources which has not been released while CM9 requires 4.0.4 kernel[source code available publicly + thunderzap is based on 4.0.4 kernel, so no need to do much work on kernel.]
EDIT:
A110 Device tree : https://github.com/varunchitre15/android_device_a110
Thunderzap[based on 4.0.4 kernel sources] : https://github.com/varunchitre15/thunderzap_canvas_2
and CM9 sources links : you can get from their website...
4.0.4 Similar Stock Kernel : https://github.com/aquila-dev/wiko_s9081_stock_kernel
Now what I found yesterday is WIKO Cink-King JB kernel sources : https://github.com/wiko-sources/cink-king
So, I now think that If we do some progress we can correctly boot CM10 by using the JB kernel to edit and get a custom kernel for a110...I am not very sure...This is what I think...If anyone can advice, It would be great...
fyi - those build DO NOT REQUIRE any Custom Kernel. i switched zImage in the CM9 boot.img and worked like a charm. we`ll need to get those mediatek propietary sources working. im working on a CM9 myself, does not get further than our french friends here http://forum.xda-developers.com/showthread.php?t=2246892 .
Chrizzly92 said:
......we`ll need to get those mediatek propietary sources working.....
Click to expand...
Click to collapse
I have no idea on this part...because, till today I thought kernel customizations are needed to run cm. So we can use the cink-king sources + device tree a110 for this. I really have no idea...
Sent from my HTC One 801e using Tapatalk 4 Beta
This ain't no normal phone.
me neither xD does not have such coding skillz yet. for this build, on this point, it isn`t necessary. maybe you cant use e.g. TUN/TAP when not compiled in the kernel, but basic features should work.
Delete
I'm one of those frenchies that try to make it work. As you saw we made it boot actually without that much problem, but before saying it works there's a lot of work.
I'd like to explain one small thing here since it seems people or thinking that because Cyanogen released the sources, we can get something working on any device. THIS IS WRONG. Even if we have a kernel sources or a "device tree"
Cyanogen includes some vendor sources, like Qualcomm for exemple. This why you'll get some things like
Code:
BOARD_USES_QCOM_HARDWARE := true
COMMON_GLOBAL_CFLAGS += -DQCOM_HARDWARE -DBINDER_COMPAT -DANCIENT_GL
COMMON_GLOBAL_CFLAGS += -DQCOM_LEGACY_OMX
in your "device tree" configuration.
Then take a look at the stuff that are in android_hardware_* there's some source code for qcom, some for samsung some for texas instrument and strangely nothing regarding mediatek. Those files are important otherwise we need to use the binaries already compiled to make them work.
Looking at the assembly code from the actual wiko-peax running under ICS, some modifications have bee done on hwcomposer. So we can't use directly the provided headers that are inside cyanogen sources since they are not the one used by mediatek. Mediatek hwcomposer for instance uses a mmumapper that nobody else uses.
I didn't look deeply at the JB binaries from mediatek, but I don't think that they like miraculously decided to switch and be directly compatible with the AOSP sources, so here there's a lot of work to do on the sources themselves.
This is why we're trying to work on CM9 since some partial sources have been leaked about an actual device running ICS. Thoses sources are much more modified then the one that goes with the binaries we have, but can be start point.
Android 4.4 KitKat has been officially announced and as usual, the latest version of the Android OS debuts alongside the a new Nexus, the Nexus 5 and it will scale automatically to fit on the devices with as little as 512 MB of RAM.
Google aims to make Android accessible to everyone, even people with low-end hardware. In the past, due to the memory constraints, some lower-end smartphones couldn't get a taste of the newer Android versions, but with KitKat that's about to change. Android 4.4 KitKat removes unnecessary background services and reduces the memory consumption to a large extent, which now allows the OS to run smoothly even on devices with 512MB RAM.
So I am requesting to Dev please Leave JB and make a last work for our O1 one last stable seedy Rom as a tribute to a device which is one of most beloved device of android family currently i am using xperia Z but still i have my old O1 (no one buy old android) it reminds me how much i play wid it in college time..
Thanks Regards
A OPTIMUS user.
This is portion of what cyanogenmod posted on facebook.
Sent from my C525c using XDA Premium 4 mobile app
So you're saying devs should abandon their work?
All they did was wasting time till now?
This is Cyanogenmod ffs. A custom android developing team that makes google stock roms look like a sugar on rain.
Can you be 100% sure that 4.4 will come out to our p500 soon? Or come out at all?
Your post won't make a difference at CM's decisions. I understand why you posted here but stil wrong thread category.
Sent from my LG-P500 using xda premium
Left4DeadMW said:
So you're saying devs should abandon their work?
All they did was wasting time till now?
This is Cyanogenmod ffs. A custom android developing team that makes google stock roms look like a sugar on rain.
Can you be 100% sure that 4.4 will come out to our p500 soon? Or come out at all?
Your post won't make a difference at CM's decisions. I understand why you posted here but stil wrong thread category.
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
I agree. I'm totally keen on kitkat too, but i prefer a stable JB build than yet another buggy build... the devs do a great job *thumbs up*
Gesendet von meinem LG-P500 mit Tapatalk
Read this again.
Sent from my LG-P500 using xda premium
^ WIN I'm sill using the cm10.1.5 with HALO and it's epic win, and I prefer this or a 4.3 stable android version than a full of bugs 4.4. I said it and i'll say it again, if you can't do it for yourself, wait for other to do it, but don't complain about the time.
I'm also excited about 4.4, and if I have known how to port it to our device I would do it. But i'm not writing everyday "PLZZZ A 4.4 ANDROID NOW!!!!" or WE WANT KITKAT!
Exactly ^_^
Newer doesn't mean better.
Oh, the irony
Sent from my LG-P500 using XDA Free mobile app
Pls help me!!!!;!!
I stuck on KitKat rom, it drains battery like hell...and when i tried to flash gingerboard in cwm recovery, installation aborted.... how do i flash gingerbread rom?
Sent from my Optimus One using XDA Free mobile app
Hii everyone
I love my galaxy tab 2
N now i want to make my own rom
Plz suggest me some method so that i can build a rom for this device
Also suggest me videos on building up a rom
kakaana said:
Hii everyone
I love my galaxy tab 2
N now i want to make my own rom
Plz suggest me some method so that i can build a rom for this device
Also suggest me videos on building up a rom
Click to expand...
Click to collapse
Do you want to build or port? Building is where you build a room from source using a device tree. Porting is simply finding a room from a similar phone or tablet. If you Google you can find lots of guides on how to do so. Building will take slightly longer(maybe more) and a device tree and a computer with a distribution of Unix like Ubuntu or Mac os or Linux mint and can take more than a few hours depending on your processor and if you have an ssd
Sent from my HTC Sensation using XDA Premium 4 mobile app
LaputaCake said:
Do you want to build or port? Building is where you build a room from source using a device tree. Porting is simply finding a room from a similar phone or tablet. If you Google you can find lots of guides on how to do so. Building will take slightly longer(maybe more) and a device tree and a computer with a distribution of Unix like Ubuntu or Mac os or Linux mint and can take more than a few hours depending on your processor and if you have an ssd
Sent from my HTC Sensation using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I would prefer porting at the present
So i can modify dem as well right?
Actually i have seen roms that they have built in
Status bar navigation bar etc settings
If i start with cm i want to add them,
Please help me out....
Also i would like to know how to port some other device's rom to my tab.....
kakaana said:
Also i would like to know how to port some other device's rom to my tab.....
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2113479
Sent from my HTC Sensation using XDA Premium 4 mobile app
So, cyanogen finally released the oneplus one kernel source as it mentioned here m.androidcentral.com/oneplus-one-kernel-source-now-available-download does this means the rom can be ported?
well, it could be ported regardless. with lots of work of course. but that kernel is for that device, that hardware. drivers for that device specifically. if it will be ported, it would probably be using a nexus 5 kernel. as porting the kernel would be a much harder and more tedious job. anyways, we have a cm11 for the nexus 5, with a cm kernel?
Kernel source and ROM source are completely different. Kernel source means nothing in the context of this question.
Sent from my Nexus 5
I've also been wanting ask if we are going to be seeing the CM11S ROM port anytime soon for our devices.
Sent from my Nexus 5 using Tapatalk
Chill dudes. I would think we will be seeing nearly all features of the 11s ROM in due time. Most of the apk's from the OnePlus dump are already working on cm11 nightlies for our N5's.
Sent from my Nexus 5 using XDA Premium 4 mobile app
I have a simple request. Could we compile a list of all non Android ROMs for the Nexus 5.
I'll get us started with the 2 I know.... If there are others please share and I will add them!
Also if you know of a link with more current information on a rom listed please let me know.
Firefox OS - http://forum.xda-developers.com/google-nexus-5/development/b2g-firefox-os-hammerhead-t2601556
Ubuntu touch -http://forum.xda-developers.com/google-nexus-5/general/port-ubuntu-touch-nexus-5-t2594874
Sailfish OS is also available for hammerhead
Sent from my Nexus 5 using XDA Free mobile app
List done then. Lol
Thank you for the replies..... has anyone been able to get inferno OS running on the Nexus 5?