Related
So, I have a barebones version of MeeGo (barely) running on the Nexus S. I can't really do much with it on my own, but I'm posting the info here so you can build it and try it for yourself.
What works:
• ADB root shell
• X11 & UI apps
• Super-AMOLED brightness control (fixed! still off-colour tho…)
What doesn't work currently:
• Touchscreen
• WiFi
• Anything else
If you've never built a MeeGo rootfs before, it's relatively straightforward, and all the binaries are precompiled for you (but it's definitely for developers only).
I have my boot.img (kernel + ramdisk) and a MeeGo kickstart file at http://blog.steventroughtonsmith.com/2011/01/nexus-s-meego.html ; you can use fastboot to boot the image, or flash it to the recovery partition to dual boot. The actual MeeGo rootfs is run from a rootfs.ext2 file you can drop onto the Nexus S using Mass Storage mode - no need for messy flashing or the like, you can thank me later).
There's not much else I can do on my own right now, so if you want to see anything become of this do get involved!
My kernel is stock git://android.git.kernel.org/kernel/samsung.git ; make herring_defconfig; the only change was modifying the .config to turn on CONFIG_VT (needed for X11).
Go nuts!
Well done on the port so far. This is way beyond my area of expertise, but I do hope that some people can help build off of what you've done so far. Always nice to see what kind of fun stuff we can run on these devices...
Looking forward to more development on this!
Great stuff!
I have been waiting for someone to start something like this, I work as an embedded developer during the day so not much time at night but I will chip in were and if I can, I am pulling the source and looking at the build system / process.
Looks like you have done the heavy lifting of bootstraping the device now its just about porting drivers.
Cheers and great start!
What driver are you using for the X11 and is it accelerated?
ilfccd said:
What driver are you using for the X11 and is it accelerated?
Click to expand...
Click to collapse
It's using unaccelerated graphics; although, with luck, SGX 540 graphics drivers are available for other devices (like the OMAP4) so in theory you may be able to patch those to run.
Update - backlight working; color is still fscked, might be gamma:
According to PowerVR rep on CES there should be an open source driver later this year (info from Phoronix, but they are lately not really reliable source of info).
Here is another question though. Have you tried using the omap tree of linaro for the kernel build?
I don't have Nexus S around currently and I'm doing all my work on TI OMAP (A8) based IGEP v2 board and TI OMAP 44xx Panda (A9) board. As they both have PowerVR 530/540 graphics I'll check tonight or tomorrow if the closed driver is compatible with linaro's kernel as I'm currently running that on the IGEP. As Samsung is part of linaro, there could be some patchests for the hummingbird in there. The current uname -r for the linaro is: 2.6.35-1008-linaro-omap so it could be compatible w/ MeeGo's kernel, there could be even newer version in the git tree.
Keep up the great work, I'm really interested in what you are doing with MeeGo. Thanks!
ilfccd said:
According to PowerVR rep on CES there should be an open source driver later this year (info from Phoronix, but they are lately not really reliable source of info).
Here is another question though. Have you tried using the omap tree of linaro for the kernel build?
I don't have Nexus S around currently and I'm doing all my work on TI OMAP (A8) based IGEP v2 board and TI OMAP 44xx Panda (A9) board. As they both have PowerVR 530/540 graphics I'll check tonight or tomorrow if the closed driver is compatible with linaro's kernel as I'm currently running that on the IGEP. As Samsung is part of linaro, there could be some patchests for the hummingbird in there. The current uname -r for the linaro is: 2.6.35-1008-linaro-omap so it could be compatible w/ MeeGo's kernel, there could be even newer version in the git tree.
Keep up the great work, I'm really interested in what you are doing with MeeGo. Thanks!
Click to expand...
Click to collapse
I'm not sure how compatible the kernels will be, the Hummingbird is not an OMAP device (and it would be more akin to the OMAP3 than OMAP4); but if the kernel works, then it should work with MeeGo too. MeeGo is relatively versatile.
Graphics drivers would be nice!
I actually use the linaro distro (ubuntu essential, which i hate) to build meego inside it, because of the work the linaro guys did on the gcc compiler (should be better versed for arm chips). according to the wiki here https://wiki.linaro.org/Platform/UserPlatforms/2010-09-13
the drivers for omap3 should be freely accessible (the 530 core). there is a mention of the 540 core in there also, but I haven't really used them as I don't run X on the boards. You could try the PVR 540 driver for the OMAP4, you might be lucky with the build, could be compatible with the one in the hummingbird. If it is, this could potentially be far better than the Nexus and HD2 MeeGo 'ports' .
ilfccd said:
I actually use the linaro distro (ubuntu essential, which i hate) to build meego inside it, because of the work the linaro guys did on the gcc compiler (should be better versed for arm chips). according to the wiki here https://wiki.linaro.org/Platform/UserPlatforms/2010-09-13
the drivers for omap3 should be freely accessible (the 530 core). there is a mention of the 540 core in there also, but I haven't really used them as I don't run X on the boards. You could try the PVR 540 driver for the OMAP4, you might be lucky with the build, could be compatible with the one in the hummingbird. If it is, this could potentially be far better than the Nexus and HD2 MeeGo 'ports' .
Click to expand...
Click to collapse
I'd try the OMAP4 driver if it was easy to get! I can only find instructions for the PandaBoard, and no repo or download links.
I will try too, if I can't locate them myself will ask someone there. First of all I have some urgent IPoIB business to attend to, though. Probably later tonight or sometime tomorrow.
Edit:
I forgot to ask, did you build MeeGo from scratch or only the kernel and used the daily userland from the arm tree?
ilfccd said:
I will try too, if I can't locate them myself will ask someone there. First of all I have some urgent IPoIB business to attend to, though. Probably later tonight or sometime tomorrow.
Edit:
I forgot to ask, did you build MeeGo from scratch or only the kernel and used the daily userland from the arm tree?
Click to expand...
Click to collapse
Prebuilt userland, no compiling required. I always use the daily RPMs (when the repo is working…)
google just released new graphics driver dunno if that will help your screen problems https://groups.google.com/group/android-building/browse_thread/thread/90d5498622a6ea4
As far as I've seen this was the most promising thread about porting meego here..
So I would suggest to just contact the ones who dived deeper into the matter and even made some progress.
Thread: http://forum.xda-developers.com/showthread.php?t=764255
tomqman said:
google just released new graphics driver dunno if that will help your screen problems https://groups.google.com/group/android-building/browse_thread/thread/90d5498622a6ea4
Click to expand...
Click to collapse
Unfortunately the graphics driver they released is specific to Android, and Android's version of libc. I don't believe there's a way to get that running on GNU/Linux or MeeGo :-(
Being the noob I am what is meego?
tominater12 said:
Being the noob I am what is meego?
Click to expand...
Click to collapse
Nokia (and Intel)'s future smartphone/tablet platform. A real Linux distribution designed for mobile devices, entirely new touch based UI, GPU acceleration, multitouch, etc.
Whoever gets this done gets a beer from me I am really excited about meego but I wont be able to buy the n9 because im on contract untill march next year. If you can get this to run on the nexus s than it should run on the sgs too, that way I can use meego wothout buying a new phone Keep it up
tomislavp4 said:
Whoever gets this done gets a beer from me I am really excited about meego but I wont be able to buy the n9 because im on contract untill march next year. If you can get this to run on the nexus s than it should run on the sgs too, that way I can use meego wothout buying a new phone Keep it up
Click to expand...
Click to collapse
Am hoping to have it up and running on the HD2 first, and then hopefully some of the work we do for that will port over to the Nexus S. Can't wait for the N9…
Hello.
I am sorry I could not post on the development thread. this is my first post. I have been checking the TI developer site and noticed that they just posted an official android Froyo devkit available for download. the link is:
software-dl.ti.com/dsps/dsps_public_sw/sdo_tii/TI_Android_DevKit/02_02_00/index_FDS.html
and the documentation is at:
/processors.wiki.ti.com/index.php/TI-Android-FroYo-DevKit-V2.2_UserGuide
The source code is included and has new drivers for the SGX chip and a devkit for the WL1271 including bluetooth stack.
Also the kit include drivers for the DSP for video decoding and Flash acceleration in android.
I think this could be good to allow update to nookie froyo. I am in the process of testing the release on an OMAP 3530 dev board and will let you know.
Wow this could be just what we need!!!
Plus maybe the CM7 folk can port this over to gingerbread and deeperblue to honeycomb then we can have a true daily driver tablet as I believe these were the rate limiting steps!!!
Canadoc said:
Wow this could be just what we need!!!
Plus maybe the CM7 folk can port this over to gingerbread and deeperblue to honeycomb then we can have a true daily driver tablet as I believe these were the rate limiting steps!!!
Click to expand...
Click to collapse
Kind of neat how these things pop up...
Glad to be on board with the Nook!
Fifcic said:
Hello.
I am sorry I could not post on the development thread. this is my first post. I have been checking the TI developer site and noticed that they just posted an official android Froyo devkit available for download. the link is:
software-dl.ti.com/dsps/dsps_public_sw/sdo_tii/TI_Android_DevKit/02_02_00/index_FDS.html
and the documentation is at:
/processors.wiki.ti.com/index.php/TI-Android-FroYo-DevKit-V2.2_UserGuide
The source code is included and has new drivers for the SGX chip and a devkit for the WL1271 including bluetooth stack.
Also the kit include drivers for the DSP for video decoding and Flash acceleration in android.
I think this could be good to allow update to nookie froyo. I am in the process of testing the release on an OMAP 3530 dev board and will let you know.
Click to expand...
Click to collapse
Lack of OMAP36xx as supported platform (read: NC) by this release is kinda disconcerting...
Thanks for posting. I'll take a look when I get home.
aludal said:
Lack of OMAP36xx as supported platform (read: NC) by this release is kinda disconcerting...
Click to expand...
Click to collapse
The thing to understand is that all the OMAP 3 serires share the same software register interface. the part numbering is based on generation and intended market:
OMAP34xx: High Volume ODM 65nm
OMAP35xx: Embedded Low volume customers (same features as OMAP34xx)
OMAP36xx: High Volume ODM 45nm (Higher clock speed, SGX double clock speed)
AM37xx and DM 37xx: Embedded low volume customers (same features as OMAP36xx)
if you look at the release. this is intended for non ODM customers and enthousiasts access to the SDK they provide to their high volume customer. this is why the OMAP 34and 36 are not mentioned. TI provides them different SDK. the important part is that this provides a stable hardware accelerated kernel with drivers to the comunity.
the OMAP 3621 is an OMAP 3630 nutered. it has the same core but the pins to support pop memory and camera interface are not conected. It is still very powerfull as it still has the DSP and SGX core inside.
I hope this helps.
Thanks for the info - looking at it, and i do see things like the OMAP3630 stuff in there, so this may every well be a useable Kernel for Froyo. Hot damn, maybe i will try my hand at compiling again (or if we are more lucky, dalingrin will find useful stuff, and really knock our socks off. )
Fifcic said:
The thing to understand is that all the OMAP 3 serires share the same software register interface. the part numbering is based on generation and intended market:
OMAP34xx: High Volume ODM 65nm
OMAP35xx: Embedded Low volume customers (same features as OMAP34xx)
OMAP36xx: High Volume ODM 45nm (Higher clock speed, SGX double clock speed)
AM37xx and DM 37xx: Embedded low volume customers (same features as OMAP36xx)
if you look at the release. this is intended for non ODM customers and enthousiasts access to the SDK they provide to their high volume customer. this is why the OMAP 34and 36 are not mentioned. TI provides them different SDK. the important part is that this provides a stable hardware accelerated kernel with drivers to the comunity.
the OMAP 3621 is an OMAP 3630 nutered. it has the same core but the pins to support pop memory and camera interface are not conected. It is still very powerfull as it still has the DSP and SGX core inside.
I hope this helps.
Click to expand...
Click to collapse
Updated drivers/dsp, updated linux kernel and bluetooth stack! This should really make for some interesting progress with nookie froyo, BT support, CM7 and possibly even the honeycomb builds
Assuming this kernel can be made to work, yes, it should really help. Some of the thing that i was looking for that are in the eclair kernel are missing (some of the OMAP stuff specific to our hardware), though, it may be a case of taking them and dropping them in. Either way, i hope this help, as i am dying to see our hardware put to better use.
Shouldn't this be in the development thread?
haganme said:
Shouldn't this be in the development thread?
Click to expand...
Click to collapse
Fifcic said:
Hello.
I am sorry I could not post on the development thread. this is my first post.
Click to expand...
Click to collapse
Yes, but new people to the forum can't post in Dev subforum until we have 10 posts.
Somebody had linked to this thread in the Dev forum, and for some reason, the mods closed it. OK, maybe we don't need two threads, but this really should be in the dev forum. It will get more attention there, and will hopefully be seen by those who need to see it..
I linked it as i thought more devs would see it there. Got a slightly rude post in reply that devs read both so.....
Indeed, i saw that, and it was uncalled for. Fact is, this is a dev thread, and should be there. Yes, a dev MAY read this forum, but truly, I don't expect them to, and things like this need to be as visible as possible - this is not the forum for that.
So.. any actual dev care to give feedback on the usefulness of this package, or are all the dev's handing out in just the dev forum still?
So Google has released the SDK for ICS here: http://developer.android.com/sdk/android-4.0.html
I've been doing some dev work on my Toshiba Thrive and wanted to know if anyone wanted to start working to port over ICS to our phones. I'm unsure about whether or not we'll get an actual ICS update so I figured I'd post up and gauge interest!
Let me know guys
Correct me if I'm wrong but don't we need the ICS source to be released to even start on a official port?
Sent from my MB860 using XDA App
parsa5 said:
Correct me if I'm wrong but don't we need the ICS source to be released to even start on a official port?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Its possible to port the SDK, but it will be harder, messier and things generally wont work 100%. This was the case with Honeycomb
The Cyanogen Mod team issued a statement saying that they will not release CM9 until the source is released. Don't you guys think that it's way too risky to use the SDK? Afterall, the source will be made available just a few weeks after the Galaxy Nexus will be made available to the general public (Source: Android Police).
Jibraldor said:
The Cyanogen Mod team issued a statement saying that they will not release CM9 until the source is released. Don't you guys think that it's way too risky to use the SDK? Afterall, the source will be made available just a few weeks after the Galaxy Nexus will be made available to the general public (Source: Android Police).
Click to expand...
Click to collapse
The problem with an SDK port is that you have no control over it. Its entirely up to luck if things work, and even then things wont work as well as they could were they to be compiled for the device in question. Also because of this, any work that goes into an SDK port would be 100% useless once the source is released, so there's no point in even starting it. For that reason I highly doubt CM9 will see any work done until the source hits.
Its not going to be too long now. The Galaxy Nexus will be out in a few weeks to a month, and the source shouldn't be too far behind. I dont expect us to have stable ICS this year, but hopefully we'll have something by early 2012.
Over in the desier hd forum they have a dump from a working device that we might be able to do something with.
I figured working on porting the sdk would prepare us for the source code release. We should be able to quickly port it over once the source is released.......hopefully. I don't see the GNex coming to at&t until early next year so I'm hoping to get a working port of ICS as quickly as possible on my atrix and I figure the only way to ensure that is to take initiative.
I really want the GNex though. That phone looks pretty cool. I hope it doesn't get a Verizon only release in November
spitefulcheerio said:
So Google has released the SDK for ICS here: http://developer.android.com/sdk/android-4.0.html
I've been doing some dev work on my Toshiba Thrive and wanted to know if anyone wanted to start working to port over ICS to our phones. I'm unsure about whether or not we'll get an actual ICS update so I figured I'd post up and gauge interest!
Let me know guys
Click to expand...
Click to collapse
hobbit19 is starting too, lets all work together on this
When you have something to post, then we can re-open this thread. Threads about the intention to develop are not necessary in the development lounge. PM me when you have made progress on a port and we'll re-open this thread. Good luck, mate!
Yesterday I had a short chat with arcee.
A huge thanks to him for taking his time to answer these rather "easy" questions.
I focused mainly on the questions which are floating around at xda these days, now we do have some educated answers (aka "the truth").
If someone wants to read a little more, I had collected a couple G+ quotes about Nvidia/LG from him some time back, see here.
To make this post clearer I removed some of the crap I wrote and focused on the important answers from him.
Didn't change anything in his lines of course.
tonyp: first, what's your opinion about LG & Nvidia here.
tonyp: at least it looks like we'll get an official update eventually, Paul's post from his internel LG source looks promising
arcee: LG has been working on that model since February
arcee: as far as I know, they've been stamping out bugs ever since
...
arcee: in any case, there's 2 sets of issues for a device like the 2x
arcee: 1 - for people like me, nvidia is utterly useless
arcee: I can't do anything on a tegra device unless the vendor does it first
arcee: 2 - as far as stock updates are concerned, that's almost entirely up to LG
Click to expand...
Click to collapse
tonyp: yes, that's really something TI and otheres are ahead of Nvidia
tonyp: but shouldn't LG have some kind of reference source code?
tonyp: aka something that would help "people like you" to implement it yourself
arcee: the reference code is nvidia's
arcee: LG, or any other nvidia customer, can't share it. even if they customize it (and they do), it still started from nvidia intellectual property
tonyp: yes that's obvious
tonyp: what I meant was if LG needs help from Nvidia or if they could help themselves with these reference source code
arcee: they usually have to work together, especially early on
arcee: nvidia is sloppy, their first iterations tend to be, to various degrees, broken
Click to expand...
Click to collapse
tonyp: Is the tegra2 chipset a problem here?
arcee: no, it isn't
arcee: the chipset is common as much
arcee: *muck
arcee: the problem is that nvidia chose a very uncommon approach to their android design
arcee: in particular, the userspace libraries and HALs have a ton of hardware-specific logic
arcee: **** that on other platforms is confined to kernel space (like "how to enable the audio amplifier" or whatever), is put in libraries when it comes to tegra
arcee: so for the most part, you can _not_ use a device's libraries on another, unless they share the same hardware components
arcee: and since nvidia publishes zero code, we can't just write our own
tonyp: iirc even things like auto brightness are controlled with nvidia libs?
arcee: yes. sensors, in this case
Click to expand...
Click to collapse
tonyp: and how specific is this implementation - would we need another device which uses the star platform (which aren't many) or could the Samsung Galaxy R for example help as well
tonyp: you wrote at Twitter that the ZTE Grant (or Mimosa) X won't really help
arcee: at all
arcee: the star, the galaxy R, and the grand X are completely different devices
arcee: different components, different resolutions, different radios
arcee: different audio amps, different panel manufacturers, different almost everything
arcee: the designs have nothing in common other than being T2
tonyp: so it's either LG or nothing?
arcee: yes
Click to expand...
Click to collapse
tonyp: and you're planning to get CM10 to the 2x then?
tonyp: because if I understood you correct you won't release any "broken" releases like you did with CM9 anymore. I do get the point, people blaming the apps when in reality the facebook rotation crash is related to a failed attempt of 2d hardware drawing.
arcee: if LG does come out with a release I can use, yes
arcee: else, no
tonyp: that's something
tonyp: and which updated libraries are exactly needed? Or are there too many to list?
arcee: pretty much everything
arcee: ICS is just too different from GB
Click to expand...
Click to collapse
Ricardo Cerqueira:
Google+
[*]Twitter
[*]his Donation Link
follow him, don't bother him - and don't threadjack his G+ posts!
this will surely clear up all those queries in the ics discussion page
I have my doubts.
Sent from my LG-P990
Thank you! It really helped me to understand the current situation with lg and other tegra 2 devices
Sent from my LG-P990 using xda app-developers app
Thanks a ton bro
Clears out any confusion regarding what will be of use, and what will not be if any use to us, plus who is to blame for this mess.
Many thanks Tonyp for this, so as I can see, the problem is nVidia...And the same what happened to us with O2X can happen to Tegra3 users... So bye bye Nexus 7...and I do not understand Google why they choose Tegra3 for Nexus7... I will never buy anything which will contain something from nVidia company....
jura55 said:
Many thanks Tonyp for this, so as I can see, the problem is nVidia...And the same what happened to us with O2X can happen to Tegra3 users... So bye bye Nexus 7...and I do not understand Google why they choose Tegra3 for Nexus7... I will never buy anything which will contain something from nVidia company....
Click to expand...
Click to collapse
I will for sure get a N7 as soon as it is launched here in the EU. It's a Nexus device after all.
And I don't think that he said Nvidia is the only one to blame - but don't make this thread to a LG vs. Nvidia one, so let's not start with that!
Just got myself a new signature
arcee: the star, the galaxy R, and the grand X are completely different devices. different components, different resolutions, different radios, different audio amps,different panel manufacturers, different almost everything. The designs have nothing in common other than being T2
tonyp: so it's either LG or nothing?
arcee: yes
Man TonyP, you've tested his nerves quite badly, answering those boring questions again and again...:laugh:
Ferrum Master said:
Man TonyP, you've tested his nerves quite badly, answering those boring questions again and again...:laugh:
Click to expand...
Click to collapse
Yeah I know I did feel a little bad about that.
He said that most of the stuff he said there isn't new and has been said by him several times.
The plan is that by pinning it out here it will become common knowledge now.
tonyp, you're hero of the forum. thanks.
perhaps the most positive line is arcee's "LG has been working on that model since february; as far as I know, they've been stamping out bugs ever since" and it's nice to know that, at least, for many of us here had doubts if LG is aware of that device at all. however it's a question of teamwork and both companies willings to do the job.
arcee was clear about not releasing cm10 nightie without LG/nvidia libraries at all, but we couldn't blame him. there are hopeful posts lately so we feels less forgotten
tonyp thanks again for sharing teh conversation!
Thanks tonyp, so for me, no Nvidia or Lg again, (only if it's nexus).
Reading the conversation i can only come to one decision. Android=Nexus nothing more nothing less.
I'm really tired of waiting, tired of translating korean to english from lg mobile korea, tired of the same answers every single day, tired of coming here and see some double/triple posting from someone who doesn't search first.
Tonyp i'd like to thank you for those posts you shared. They gave some peace if mind.
Sent from my LG-P990 using xda app-developers app
So am I wrong to assume that CM10 even with official ICS release has very few chances to come to our mobile;
Tony big kudos to you for bothering RC with such "annoying" questions:thumbup:
loipol84 said:
So am I wrong to assume that CM10 even with official ICS release has very few chances to come to our mobile;
Tony big kudos to you for bothering RC with such "annoying" questions:thumbup:
Click to expand...
Click to collapse
Yes, you are wrong. He means to say that if LG releases official ICS, it can probably be used to help in building CM10 too.
From Tweeter:
- when CM9 stable for LG Optimus 2X?
RC: never. At this point, if and when LG does the ICS update, it'll be used for CM10
Thats a good news.
I was telling ever since beginning LG is less responsible for our situation but nvidia
Sent from my LG-P990 using Tapatalk 2
spica1234 said:
Thats a good news.
I was telling ever since beginning LG is less responsible for our situation but nvidia
Sent from my LG-P990 using Tapatalk 2
Click to expand...
Click to collapse
I blame them equally and Google. NVIDIA for being secretive about their source code, doing non-standard Android integration implementations, being sloppy with development and continuously releasing bug-filled code to the OEMs it sells to (even the most current release of Tegra2 code has bugs known at release). LG for using NVIDIA SOC. Google for allowing phone OEMs, such as LG, to use chips from companies, such as NVIDIA, which hide their code so that independent developers can't modify/update Android.
Google should stop tolerating closed-source code from companies such as NVIDIA in order to popularize Android and, instead, require that all companies which use Android must provide complete and transparent open-source code for everything in a device which uses Android. That would mean that LG or any other company that uses Android in a device wouldn't be able to sell that device if it uses NVIDIA or another company's chips/hardware if it doesn't provide open-source human readable source code for micro-code, firmware, etc., and the development tools too.
Core Memory said:
I blame them equally and Google. NVIDIA for being secretive about their source code, doing non-standard Android integration implementations, being sloppy with development and continuously releasing bug-filled code to the OEMs it sells to (even the most current release of Tegra2 code has bugs known at release). LG for using NVIDIA SOC. Google for allowing phone OEMs, such as LG, to use chips from companies, such as NVIDIA, which hide their code so that independent developers can't modify/update Android.
Google should stop tolerating closed-source code from companies such as NVIDIA in order to popularize Android and, instead, require that all companies which use Android must provide complete and transparent open-source code for everything in a device which uses Android. That would mean that LG or any other company that uses Android in a device wouldn't be able to sell that device if it uses NVIDIA or another company's chips/hardware if it doesn't provide open-source human readable source code for micro-code, firmware, etc., and the development tools too.
Click to expand...
Click to collapse
Without the Apache license which is used by Google Android wouldn't be that popular.
So that is no argument, it's the customers choice which brand to choose after all.
Sent from my LG-P990 using xda app-developers app
Hello
I'm reading a lot of comment about people never buying a SAMSUNG phone again on this forum.
I believe it has something to do with CM team ( who are these guys? ) and the CPU type and source code.
Could you please care to elaborate? As I am planning on upgrading to GN2 but ofc I need root access and the latest OS all the time
Thank you.
Which post are you refering to? I just seem to see post saying how awesome the Note 2eand SIII are!
Dmwitz said:
Which post are you refering to? I just seem to see post saying how awesome the Note 2eand SIII are!
Click to expand...
Click to collapse
It's not just 1 post,
All around the forum , especially in the GN forum ( where I spend most of my time ) I see people complaining about Samsung devices in the future and how they will never buy another samsung again ...
I guess it all depends whether or not you want to run CM custom roms on your device.
Furthermore Samsung promised to release the Exynos sources...So we'll just wait and see
Problem ist that the source code is no available and without no new CM AOSP AOKP Roms possible. The company said in the past that they will release the code, but till today they don't.
Other companies like Sony did it better and supports the community. That's also a reason why great Dev won't work for our Note...
It's not impossible to bring new roms without sourcecode - we still have CM10 and will get CM10.1 - but the experience is not the best, and devs have to put A LOT of work to even make it work.
Samsung promised they will release their sources - yet untill today - they didn't. So it's simple as that, if they release sources - devs might finally fix some bugs and push CM10 into stable. Without sources we might never go out of nigthlies because some bugs might never get fixed.
As for SONY, yes they release all their sources, but remember that they used to be like Samsung untill their market share shrinked, so now they're most likely just trying to appeal to customers with that. Hope they won't change their mind about it when/if their sales go high again ( I'm looking at you Xperia Yuga )
User_99 said:
Problem ist that the source code is no available and without no new CM AOSP AOKP Roms possible. The company said in the past that they will release the code, but till today they don't.
Other companies like Sony did it better and supports the community. That's also a reason why great Dev won't work for our Note...
Click to expand...
Click to collapse
Very true, but I think they don't give a ....about a few devs and users being frustrated when they sell millions of devices...Like most of the big selling companys
bebseh said:
It's not just 1 post,
All around the forum , especially in the GN forum ( where I spend most of my time ) I see people complaining about Samsung devices in the future and how they will never buy another samsung again ...
Click to expand...
Click to collapse
I think u r talking abt this thread..especially this one..
a pall of gloom has descended on the community it seems
check out CM 10 thread
i hope its a temporary phase -
http://forum.xda-developers.com/showpost.php?p=35210934&postcount=1651
Samsung didnt want the devs to work for the android community because in the end it gives an advantage to google and its os. Samsung wants people to buy its phones because of their new features added in their TW that are not available on true android. They in the future wants their devices ti be free from the android pool. Because of the tiring update process. No source code release is just what keeps dev from moding their devices so they can market their new phones and limit those features in the old models. I dont think they will care about dev going to other vendors. Because once they got hold of a new indigenous OS. they will market its dev kits and hardware for developers and they know how to bring them back.
Sent from my GT-N7000 using xda app-developers app