Related
Last night i was trying to flash a new update on my tab from Kies when horror there was a power cut thus leaving my beloved tab dead. Today i rang samsung support to book a service and during the conversation the agent told me that later this year samsung will release a honeycomb update for the 7 inch tab. At this point i asked how come as from reading threads i was under the impression that this was not going to happen and the only way was through a port from one of the amazing developers like spacemoose1 (cdma) and ssserpentine (gsm) his answer was that samsung wanted to compete with apple even more. has anyone else been told this from samsung ?
corrosion1970 said:
Last night i was trying to flash a new update on my tab from Kies when horror there was a power cut thus leaving my beloved tab dead. Today i rang samsung support to book a service and during the conversation the agent told me that later this year samsung will release a honeycomb update for the 7 inch tab. At this point i asked how come as from reading threads i was under the impression that this was not going to happen and the only way was through a port from one of the amazing developers like spacemoose1 (cdma) and ssserpentine (gsm) his answer was that samsung wanted to compete with apple even more. has anyone else been told this from samsung ?
Click to expand...
Click to collapse
1st of all ... SPACEMOOSE1 work , and no one else include . SSS is porting , collecting , testing , uploading THE GSM port for us thank him , if u saw him comment in anywhere
2nd .. Do U believe this Sh*t for God sakes .. its is impossible to happen !!!!!!! if they want to run with APPLE they should release it now or before ...
WE ARE REACHED THE FINAL STEP ( GINGERBREAD ) perhaps will be (ICECREAM) but honeyComb hell no ...
To The OP .. pls do change your thread Title is not a question , and if you like to keep it here in THE GENERAL SECTION that not suppose to post A Question thread here ...
thanks for sharing
1st the question i am asking is has anyone else been told this from samsung. if you read the post
2nd the honeycombe thread is now split as spacemoose1 and ssserpentine are now working together space doing the cdma release and ssserp doing the gsm so thanks shoould be given to both parties.
corrosion1970 said:
1st the question i am asking is has anyone else been told this from samsung. if you read the post
2nd the honeycombe thread is now split as spacemoose1 and ssserpentine are now working together space doing the cdma release and ssserp doing the gsm so thanks shoould be given to both parties.
Click to expand...
Click to collapse
i referred to ask you to change the title of the thread because this is the general Thread and is not FOR QUESTIONS >>>> so perhaps next time you post thread with Q you should post it in Q|A section ...
spacemoose1 and ssserpentine are now working together space doing the cdma release and ssserp doing the gsm so thanks shoould be given to both parties
Click to expand...
Click to collapse
LMAO ... you should thank both and i didn't say you don't thank SPACEMOOSE1 because she is the Dev ... and pls .. who told you That SSS who is building THE GSM Honeycomb ...
all the respect to my mate (SSS) but he is not who building the HONEYCOMB ... Correct Me If I'm Mistaken !!!
@k0sh Technically, he is building the GSM version, but a majority of it is a port from Spacemoose.
@OP *sigh* Its bull****. Samsung want us to be happy by telling us lies. Read any other Honeycomb for our Tab related thread (no development threads) and you'll know that no device that launched with FroYo (like our Tab) will get Honeycomb. That's straight from Google who can deny any manufacturer the chance to give their devices updates.
It doesn't matter what anyone from Samsung says, Google said 'no'
| Don't Revive Me Bro | Follow me on Twatter
GANJDROID said:
@k0sh Technically, he is building the GSM version, but a majority of it is a port from Spacemoose.
@OP *sigh* Its bull****. Samsung want us to be happy by telling us lies. Read any other Honeycomb for our Tab related thread (no development threads) and you'll know that no device that launched with FroYo (like our Tab) will get Honeycomb. That's straight from Google who can deny any manufacturer the chance to give their devices updates.
It doesn't matter what anyone from Samsung says, Google said 'no'
| Don't Revive Me Bro | Follow me on Twatter
Click to expand...
Click to collapse
Mate i doubt about it .. can you then explain this for me ..
Second, that thread will be managed by ssserpentine. He will also be handling the distribution, packaging and eventually the kernel development for the GSM as well. This way I'm freer to focus on the development of the base rom for both devices. So expect a new thread with a new GSM release to pop up any minute now. ssserpentine will do a good job of getting things out to you, he's super resourceful and dedicated to making HC a more awesome experience.
Click to expand...
Click to collapse
k0sh said:
i referred to ask you to change the title of the thread because this is the general Thread and is not FOR QUESTIONS >>>> so perhaps next time you post thread with Q you should post it in Q|A section ...
LMAO ... you should thank both and i didn't say you don't thank SPACEMOOSE1 because she is the Dev ... and pls .. who told you That SSS who is building THE GSM Honeycomb ...
all the respect to my mate (SSS) but he is not who building the HONEYCOMB ... Correct Me If I'm Mistaken !!!
Click to expand...
Click to collapse
Taken fron ssserpentines honeycomb gsm thread
This is an ALPHA version. There is no 3g, among many other things. Using an alpha rom can be very dangerous. Don't just flash, because you see its HONEYCOMB, read everything very carefully first!
(6/14/11)
After being up way too many hours in a row, and trying to do too many things at once, work on a new kernel has officially begun!
★what's in the oven. .
»new cwr with internal external support.
»1.2ghz
»uc ability
»reliable charging while power is off.
«doubtful, but cross your fingers for lagfix?
(6/13/11) : GSM owners. Alpha 2.5 has arrived!! (No 3g)I highly recommend you start off in FROYO, as coming from GINGERBREAD causes crashes. Use the overcome 1.6 instructions, if you are currently on GB.
But, beware, changing your bootloaders is very dangerous!
*modded build.prop to identify itself as a Samsung Galaxy Tab as GT-P1000. - test runs, not included in cdma release
*modded audiolib to accept dsp manager setting. (more equalizers comming soon) - test runs, not included in cdma release
*what I have planned, and currently in the works.*
* New kernel with 1.2, 1.4 oc
* Flexible scaling
* Attempted lagfix
* New CRW version with internal and external sd support
* SD cart mount upon boot
that is him as i understand it and it looks like he is developing it now
corrosion1970 said:
Taken fron ssserpentines honeycomb gsm thread
This is an ALPHA version. There is no 3g, among many other things. Using an alpha rom can be very dangerous. Don't just flash, because you see its HONEYCOMB, read everything very carefully first!
(6/14/11)
After being up way too many hours in a row, and trying to do too many things at once, work on a new kernel has officially begun!
★what's in the oven. .
»new cwr with internal external support.
»1.2ghz
»uc ability
»reliable charging while power is off.
«doubtful, but cross your fingers for lagfix?
(6/13/11) : GSM owners. Alpha 2.5 has arrived!! (No 3g)I highly recommend you start off in FROYO, as coming from GINGERBREAD causes crashes. Use the overcome 1.6 instructions, if you are currently on GB.
But, beware, changing your bootloaders is very dangerous!
*modded build.prop to identify itself as a Samsung Galaxy Tab as GT-P1000. - test runs, not included in cdma release
*modded audiolib to accept dsp manager setting. (more equalizers comming soon) - test runs, not included in cdma release
*what I have planned, and currently in the works.*
* New kernel with 1.2, 1.4 oc
* Flexible scaling
* Attempted lagfix
* New CRW version with internal and external sd support
* SD cart mount upon boot
that is him as i understand it and it looks like he is developing it now
Click to expand...
Click to collapse
owh that is really great .. glad to see SSS doing hard work ... ..
anyways .. change the thread title or your thread will be moved shortly i guess
k0sh said:
owh that is really great .. glad to see SSS doing hard work ... ..
anyways .. change the thread title or your thread will be moved shortly i guess
Click to expand...
Click to collapse
EDIT : pls do note that this is SPACEMOOSE1 post and not SSS ...
anyways . its not my business who is building it ... just a hint
corrosion1970 said:
Last night i was trying to flash a new update on my tab from Kies when horror there was a power cut thus leaving my beloved tab dead. Today i rang samsung support to book a service and during the conversation the agent told me that later this year samsung will release a honeycomb update for the 7 inch tab. At this point i asked how come as from reading threads i was under the impression that this was not going to happen and the only way was through a port from one of the amazing developers like spacemoose1 (cdma) and ssserpentine (gsm) his answer was that samsung wanted to compete with apple even more. has anyone else been told this from samsung ?
Click to expand...
Click to collapse
I can't swallow that agent's speech, although i'd wish for it to be genuine.
Sammy has quite a history for letting its customers down, either by delays or no updates at all.
Sҡȳᴪʌɩҡͼṟ said:
I can't swallow that agent's speech, although i'd wish for it to be genuine.
Sammy has quite a history for letting its customers down, either by delays or no updates at all.
Click to expand...
Click to collapse
+1 ... Samsung said . we gonna have galaxy tab 10.1 for free only for the galaxy tab 7.1 owners ... do you believe this Sh*t ? hahaha , just rumors i made
GANJDROID said:
@k0sh Technically, he is building the GSM version, but a majority of it is a port from Spacemoose.
@OP *sigh* Its bull****. Samsung want us to be happy by telling us lies. Read any other Honeycomb for our Tab related thread (no development threads) and you'll know that no device that launched with FroYo (like our Tab) will get Honeycomb. That's straight from Google who can deny any manufacturer the chance to give their devices updates.
It doesn't matter what anyone from Samsung says, Google said 'no'
| Don't Revive Me Bro | Follow me on Twatter
Click to expand...
Click to collapse
Can you please direct me to a source which says that Google said no existing Froyo devices can be updated to HoneyComb? I honestly don't remember any such official statement from Google!
Pat123 said:
Can you please direct me to a source which says that Google said no existing Froyo devices can be updated to HoneyComb? I honestly don't remember any such official statement from Google!
Click to expand...
Click to collapse
I don't have it bookmarked but itbwas about a few weeks after they released the SDK.
| Don't Revive Me Bro | Follow me on Twatter
Pat123 said:
Can you please direct me to a source which says that Google said no existing Froyo devices can be updated to HoneyComb? I honestly don't remember any such official statement from Google!
Click to expand...
Click to collapse
Ill try and dig up the link, but do a search its posted somewhere here on the forums, and their reasoning behind it is;
they don't want 39 million china tablets coming out and giving honeycomb a bad name.
I ran into this problem the other day, someone at uni had a 7inch china tablet with froyo and everyone was talking about how **** android must be
i had to pull out my device and be like, nawwwwwwww.
Majority of people are retards and it only takes one china device to give android a bad name
I know it has been announced only a few hours ago and the source is not available yet. But, when Google finally releases the source code, will there ever be a ROM for the original Galaxy Tab?
I am curious because the answer to this question will help me resist the new tablet temptation
Having a hard time with HC, I doubt it with ICS....even the GB ROMs are not very polished, like Overcome causes warming up problem....
It can be short...
Maybe it will arrive sooner as we think, not with cyanogenmod, even if i want it on my tab, but with MIUI, I just read on the MIUIteam fr that MIUI have the source since they have the status of developpers with the XIAOMI, and they are already work on the Mi-one and the two nexus, so maybe the us team who develop the MIUI Rom for our tab will be able to port ISC on the galaxy tab?
I just hope that we can have ISC on our tab before Christmans it will be great!
ICS
From the news:
"Gabe Cohen from Google claims that most Gingerbread devices may have an upgrade to Android 4.0, claiming that it is theoretically compatible with any Android 2.3.x device"
I would presume (going off the little snippits of info I've gleaned) that almost ANY device will be able to run ICS in some capacity or another since it is designed to be all encompassing. (Think Ubuntu for comparison) Admittedly some older devices will struggle due to the specs but this is the same for every old device.
I could be completely WAY-OFF the mark but I believe el-goog is heading down the Canonical Road and pretty soon we will have OS's that just play well together, be it on mobile, laptop, PC, TV yadda yadda yadda......and then we'll see a small moon appear on the horizon
No wait, "That's not a moon.....It's a SPACE STATION!" cue dramatic music and suddenly everyone and their dog will be screaming "IT'S A TRAAAAAP!" "TURN THIS SHIP AROUND!" but by then we'll all be caught in the tractor beam and headed for a Schwartz-off with Dark Helmet......
Jus sayin
Developers get new devices and forget about old ones. Time's working against us...
In future, post [QUESTIONS] in your separate Q&A section.
The next thread I see in the General section, that asks a [QUESTION] will be deleted, the user will receive a Warning.
I believe there will be a rom, not before Christmas tho
At least not a stable one.
Will Samsung release ICS for Galaxy Tab ??
Do you think people will port it or wait for source code.
andyharney said:
In future, post [QUESTIONS] in your separate Q&A section.
The next thread I see in the General section, that asks a [QUESTION] will be deleted, the user will receive a Warning.
Click to expand...
Click to collapse
How does a question not belong in general? Is the general sub forum not for General discussion. Don't mean to be rude just wondering how that does not encompass a question (heck a development thread could in theory fall under the general category), i understand that there is a specific category for q&a and trying to order the chaos; it just seems to me you can't really claim anything doesn't belong in general in order to delete and or warn a user.
themapleboy said:
How does a question not belong in general?
Click to expand...
Click to collapse
When you pose a question to which you would like an answer, if falls under the Q&A section.
Is the general sub forum not for General discussion.
Click to expand...
Click to collapse
When you would like to discuss & have active engagement on a particular topic then it would fall under the General section.
Don't mean to be rude just wondering how that does not encompass a question (heck a development thread could in theory fall under the general category), i understand that there is a specific category for q&a and trying to order the chaos; it just seems to me you can't really claim anything doesn't belong in general in order to delete and or warn a user.
Click to expand...
Click to collapse
Don't worry, I understand you intent, no rudeness is taken.
The development sections are for posting active development projects. I.e ROMs, APPs & MODs & to receive feedback, help, advice & even thanks.
To use this thread as an example, the OP asked.
when Google finally releases the source code, will there ever be a ROM for the original Galaxy Tab?
Click to expand...
Click to collapse
That is a question, even the thread title has [QUESTION] in it. The answer to this particular question is, we honestly don't know.
IF the OP had worded it similar to this.
When Google finally release the source code, do you guys think there will ever be a ROM for the original Galaxy Tab
Click to expand...
Click to collapse
This, to me is open for discussion, and not a clear cut yes or no. There is a gray (British spelling ) area as you could say the General section is full of questions.
But to clarify, If I see any threads with [Q] or [Question] in the thread title or post, in the General section, it will be deleted & the user Warned, not Infracted, just warned.
If they haven't bothered checking what section they are posting in, its highly likely they haven't bothered searching for the answer either, but that is another kettle of fish
This is all so incredibly exciting... looks like an amazing release and I really hope that I can put it on my SGT very soon!
andyharney said:
Don't worry, I understand you intent, no rudeness is taken.
Click to expand...
Click to collapse
Andy: Thank you for being awesome - lots of admins I've worked with throughout the years would probably throw a hissy over perceived insurrection when questions of protocol are asked. Your professionalism is greatly appreciated.
I am so glad that google appears to have gone with an open model this time around - it looks like they actually worked to maximize compatibility with the wide range of GB running devices and made everything pretty portable. of course we'll know more about that in a week or so when google drops the sources on us.
from what i understand, this will be the first time we've had proper public sources since the GB release.
the new feature set looks like it'll be pretty amazing so long as they optimized it well... I don't really care if newer fancier phones and tabs have more resources... more resources should allow you to do more things better, NOT an excuse to settle for sub-par optimization of code because "oh, it doesn't matter anymore, all new devices have enough ram and cpu speed to handle it!"... </rant>
andyharney said:
When you pose a question to which you would like an answer, if falls under the Q&A section.
When you would like to discuss & have active engagement on a particular topic then it would fall under the General section.
Don't worry, I understand you intent, no rudeness is taken.
The development sections are for posting active development projects. I.e ROMs, APPs & MODs & to receive feedback, help, advice & even thanks.
To use this thread as an example, the OP asked.
That is a question, even the thread title has [QUESTION] in it. The answer to this particular question is, we honestly don't know.
IF the OP had worded it similar to this.
This, to me is open for discussion, and not a clear cut yes or no. There is a gray (British spelling ) area as you could say the General section is full of questions.
But to clarify, If I see any threads with [Q] or [Question] in the thread title or post, in the General section, it will be deleted & the user Warned, not Infracted, just warned.
If they haven't bothered checking what section they are posting in, its highly likely they haven't bothered searching for the answer either, but that is another kettle of fish
Click to expand...
Click to collapse
Ah, I should have formulated the question better!
I apologize. Next time, questions go to Q&A section
tarantulae said:
From the news:
"Gabe Cohen from Google claims that most Gingerbread devices may have an upgrade to Android 4.0, claiming that it is theoretically compatible with any Android 2.3.x device"
Click to expand...
Click to collapse
I agree!!! More so if ICS is the hybrid between honeycomb (tabs only) and gingerbread (smartphones only), it should work on Original Galaxy(OG) tab, at least for those upgraded to gingerbread. Now we have OG 7" on 2.3, sg-tab 7 plus on 3.2 and possibly sg-tab 7.7 on ??4.0(I guess), sammy better get ICS on all otherwise it'll be hard selling all three.
afaebe said:
I agree!!! More so if ICS is the hybrid between honeycomb (tabs only) and gingerbread (smartphones only), it should work on Original Galaxy(OG) tab, at least for those upgraded to gingerbread. Now we have OG 7" on 2.3, sg-tab 7 plus on 3.2 and possibly sg-tab 7.7 on ??4.0(I guess), sammy better get ICS on all otherwise it'll be hard selling all three.
Click to expand...
Click to collapse
I thing the original sgt7 is no longer part of the lineup i belive it has been discontinued. So the 7 plus is 3.2, as is the 10.1, and the 7.7. Samsung has settled on honeycomb for the lot but have already stated that each of these tablets will get upgraded to ics "real soon". On the flipside they all but confirmed that ics wont be coming to the original sgt7 making me very sad.
Samsung imho has really bad support for os updates in that they taje forever to release them and they are notorious for droping hardware / os support way too fast. My original sgt7 came out only about a year ago (last nov iirc).
Sent from my GT-P1000 using XDA App
Some cyanogenmod guys are putting together CM9 for tabs in general and ours looks like its on the list.
Sent from Sprint Galaxy Tab
Dmaxx67 said:
Some cyanogenmod guys are putting together CM9 for tabs in general and ours looks like its on the list.
Sent from Sprint Galaxy Tab
Click to expand...
Click to collapse
yes, that's true, there is lots of private third-party ICS development going on to get a good AOSP rom up and functional. I think that's going to be most dependent on the galaxy tab ics dev thread here and then the cyanogen guys will go ahead and hack it smooth with extra features and the like as they generally do. I was specifically tallking about samsung OEM rom support.
and FIY, there is already a worked over SDK port of honeycomb for the galaxy tab 7 that seems to run pretty smooth that you might want to check out here if you're interested. the ICS stuff looks like it's shaping up, but I expect it to be at least a few months before everything becomes smooth enough for use as a daily rom.
this phone we own has been around for around 6 months now, when i had a galaxy mini (not s3 mini, just galaxy mini) there were so many customization's ROMS in six months, but for our superior phone we have barely anything, i do appreciate everyones effort but there must be more customization's ROMS like AOSP ROMS. :crying:
Maybe because there are too many new phones in this interval of time and our s3 mini is not the most popular
Sent from my Motorola Startac
joshtk98 said:
this phone we own has been around for around 6 months now, when i had a galaxy mini (not s3 mini, just galaxy mini) there were so many customization's ROMS in six months, but for our superior phone we have barely anything, i do appreciate everyones effort but there must be more customization's ROMS like AOSP ROMS. :crying:
Click to expand...
Click to collapse
The main problem seems to be that the ST-Ericsson Novathor sources are not available.
I think that devs are focusing on more powerful devices like the s3 or s4, bigger guns are always better, aren't they?
Sent from my GT-I8190 using xda app-developers app
Take a look in dev section. mostly threads ends with a "this is my code / customization!" war.
There aren't community around this device.
vtetuan said:
Take a look in dev section. mostly threads ends with a "this is my code / customization!" war.
There aren't community around this device.
Click to expand...
Click to collapse
Last war was with me and Oliver, now we're working together in peace. I missed something?
But biggest problem is in no ste sources.
New Macław said:
Last war was with me and Oliver, now we're working together in peace. I missed something?
But biggest problem is in no ste sources.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=42730302&postcount=25
The guy only wants to learn. And I'm not saying that you have no reason.
It's the classical fragmentation in Linux community, and now, in Android community.
New Macław said:
Last war was with me and Oliver, now we're working together in peace. I missed something?
But biggest problem is in no ste sources.
Click to expand...
Click to collapse
How about this?
http://forum.xda-developers.com/showthread.php?t=2327646
Scuppa said:
How about this?
http://forum.xda-developers.com/showthread.php?t=2327646
Click to expand...
Click to collapse
Really chaotic commits. But we've almost ready CM10.1 sources, so don't worry
New Macław said:
Really chaotic commits. But we've almost ready CM10.1 sources, so don't worry
Click to expand...
Click to collapse
We have chaotic commits because we have a Jenkins server that requires sources to be uploaded to github and then synced by the server. We're not testing locally
The important ones you may encounter useful are in libhardware, libhardware_legacy, frameworks_av and frameworks_native, we're trying to use code from jellybean STE_AUDIO and adapt them to cm-10.1 (we're NOT coders so we did our best). Also, we build for two devices now, so we need to adapt the code to be common in some parts.
We can collaborate, maybe you could help us, and we can (if my teammates agree) get you some power (the jenkins) to build and upload automatically
Paul L. said:
We have chaotic commits because we have a Jenkins server that requires sources to be uploaded to github and then synced by the server. We're not testing locally
The important ones you may encounter useful are in libhardware, libhardware_legacy, frameworks_av and frameworks_native, we're trying to use code from jellybean STE_AUDIO and adapt them to cm-10.1 (we're NOT coders so we did our best). Also, we build for two devices now, so we need to adapt the code to be common in some parts.
We can collaborate, maybe you could help us, and we can (if my teammates agree) get you some power (the jenkins) to build and upload automatically
Click to expand...
Click to collapse
I don't need access to your machine, I would like to keep releases on my own hand, but of course I can help you
Poke me at gtalk please: [email protected]
As the title says, it'd be great if there was an updated list with the supported device which will be recieving 'L' from Omni.
Gokulbalram said:
As the title says, it'd be great if there was an updated list with the supported device which will be recieving 'L' from Omni.
Click to expand...
Click to collapse
There won't be, since L is not out and we have no idea what changes it is going to entail from a device support perspective.
As far as devices that are likely to receive "focus" from the team - Oppos and the Sony Xperia Z family. (Probably Z1/ZU also) - Because of how well Oppo and Sony have treated the open source community, in general, team members are more motivated to grab "older" devices they don't use any more in order to work on them.
However here's a list of devices that are likely to be dropped:
All Exynos 4210 devices (i777/n7000/i9100) - No active maintainers remain for these devices, they've been on minimal life support for two years now since Exynos-gate and the Superbrick fiasco of 2012.
I9300 - No active maintainer
Unknowns:
N80xx - Of 3 maintainers, the only one who remains is Humberto and he's kinda spread thin. So highly likely to get removed.
maguro - This didn't have an active maintainer for ages, but I think one did step up. I need to talk with the team.
Honestly, I'd love to just kill Exynos4 with fire with L and be done with that goddamned hell platform once and for all... But that is only my personal opinion.
Entropy512 said:
There won't be, since L is not out and we have no idea what changes it is going to entail from a device support perspective.
As far as devices that are likely to receive "focus" from the team - Oppos and the Sony Xperia Z family. (Probably Z1/ZU also) - Because of how well Oppo and Sony have treated the open source community, in general, team members are more motivated to grab "older" devices they don't use any more in order to work on them.
However here's a list of devices that are likely to be dropped:
All Exynos 4210 devices (i777/n7000/i9100) - No active maintainers remain for these devices, they've been on minimal life support for two years now since Exynos-gate and the Superbrick fiasco of 2012.
I9300 - No active maintainer
Unknowns:
N80xx - Of 3 maintainers, the only one who remains is Humberto and he's kinda spread thin. So highly likely to get removed.
maguro - This didn't have an active maintainer for ages, but I think one did step up. I need to talk with the team.
Honestly, I'd love to just kill Exynos4 with fire with L and be done with that goddamned hell platform once and for all... But that is only my personal opinion.
Click to expand...
Click to collapse
I have still yet use oppo device but from what I have seen so far it is a pretty much quite a kickass device as for sony I main yuga from time to time as this is the only device I got and we all know what happened back in the days of exynos4
iKillCypher said:
I have still yet use oppo device but from what I have seen so far it is a pretty much quite a kickass device as for sony I main yuga from time to time as this is the only device I got and we all know what happened back in the days of exynos4
Click to expand...
Click to collapse
What do you guys hate Exynos for? Kernel Sources?
Gokulbalram said:
What do you guys hate Exynos for? Kernel Sources?
Click to expand...
Click to collapse
https://plus.google.com/u/0/+AndrewDodd/posts/cdPnNjLAb4F
chasmodo said:
https://plus.google.com/u/0/+AndrewDodd/posts/cdPnNjLAb4F
Click to expand...
Click to collapse
Oh wow, even MediaTek is getting better. Meanwhile, this Bull****.
So @Entropy512, I read all the 100 posts, and I finally understand you.
Gokulbalram said:
Oh wow, even MediaTek is getting better. Meanwhile, this Bull****.
So @Entropy512, I read all the 100 posts, and I finally understand you.
Click to expand...
Click to collapse
As bad as Exynos is... MTK manages to actually be significantly worse.
Even if you have complete access to all of the source they give to an OEM (let's just say I've seen a complete leak for one MT6589 device), it's still a blob-ridden disorganized mess.
Entropy512 said:
As bad as Exynos is... MTK manages to actually be significantly worse.
Even if you have complete access to all of the source they give to an OEM (let's just say I've seen a complete leak for one MT6589 device), it's still a blob-ridden disorganized mess.
Click to expand...
Click to collapse
There's only one source for a MediaTek chipset, the one in Android One. At least MediaTek is getting better, they're taking steps.
Hi OmniROM devs,
While waiting for Lollipop to arrive, can you please get around to updating the yuga kernel and blobs? There's no point of Sony going to the trouble of publishing the up-to-date kernel sources if the roms are not going to take advantage of it.
Entropy512 said:
There won't be, since L is not out and we have no idea what changes it is going to entail from a device support perspective.
As far as devices that are likely to receive "focus" from the team - Oppos and the Sony Xperia Z family. (Probably Z1/ZU also) - Because of how well Oppo and Sony have treated the open source community, in general, team members are more motivated to grab "older" devices they don't use any more in order to work on them.
However here's a list of devices that are likely to be dropped:
All Exynos 4210 devices (i777/n7000/i9100) - No active maintainers remain for these devices, they've been on minimal life support for two years now since Exynos-gate and the Superbrick fiasco of 2012.
I9300 - No active maintainer
Unknowns:
N80xx - Of 3 maintainers, the only one who remains is Humberto and he's kinda spread thin. So highly likely to get removed.
maguro - This didn't have an active maintainer for ages, but I think one did step up. I need to talk with the team.
Honestly, I'd love to just kill Exynos4 with fire with L and be done with that goddamned hell platform once and for all... But that is only my personal opinion.
Click to expand...
Click to collapse
S2/S3/Note take a huge percentage in the download counts of any custom ROMs
it's a bad platform... But there is still lots of users using them regularly... Hopefully you guys can give us some L builds... I won't be that sad if you stopped since I know how hard it's to still even offer us some builds for KitKat...
Thanks..
ahmedelhofy said:
S2/S3/Note take a huge percentage in the download counts of any custom ROMs
it's a bad platform... But there is still lots of users using them regularly... Hopefully you guys can give us some L builds... I won't be that sad if you stopped since I know how hard it's to still even offer us some builds for KitKat...
Thanks..
Click to expand...
Click to collapse
https://plus.google.com/u/0/+AndrewDodd/posts/cdPnNjLAb4F
Even I own an S3, but after reading this, I really wouldnt be pissed to see it being dropped
Gokulbalram said:
https://plus.google.com/u/0/+AndrewDodd/posts/cdPnNjLAb4F
Even I own an S3, but after reading this, I really wouldnt be pissed to see it being dropped
Click to expand...
Click to collapse
Yea, I know I already said that I won't be sad to see it getting dropped..
Last week, jakew02 said that he's going to drop support for Galaxy S4 LTE (jflte) when Lollipop arrived. He's leaving the source up, but OmniROM Lollipop on the S4 will need a new maintainer.
The key message here is that the core team can't maintain every device!
As much as we hate to remove devices, there will be a significant number removed, if there's no active maintainer for it. No device will be enabled for L nightlies (and thus official support) if there's nobody active and competent who is maintaining it.
If you've always wanted to get involved, now really is the time - L is upon us, and good things are happening
Going forward, if there is sufficient interest from the community (i.e. go out there and talk to devs and contributors from other projects please!), we are more than happy to facilitate making the 4.4 branch of Omni an ongoing project.
For this to work though, it would require enough developers to come together on legacy devices to make it viable. With new major Android versions, a lot of custom ROMs simply don't continue support for devices "left behind", but we're willing to try this out as an experiment. If there are sufficient (experienced) developers, we'll have 4.4 as an active project which will accept features and patches as normal.
For this to work though, it does require everyone to play their part - we'll need reliable people to review and approve changes etc, as well as active maintainers for devices.
aidfarh said:
Hi OmniROM devs,
While waiting for Lollipop to arrive, can you please get around to updating the yuga kernel and blobs? There's no point of Sony going to the trouble of publishing the up-to-date kernel sources if the roms are not going to take advantage of it.
Click to expand...
Click to collapse
Hi,
that's not really necessary if you ask me. We could always bring the kernel in sync with CAF, but that's it. This is also what OEMs do when updating their kernels (apart from fixes and such). Jerpelea, a Sony Mobile developer, agrees (see this post).
Also there aren't many "active" Xperia fusion3 (Z, ZL, Tablet Z) maintainers at the moment , and I haven't had enough time for such things.
BUT: Contributions are always welcome.
Help
I don't know much of anything about developing but am fairly competent and comfortable with flashing ROM's and kernels. I own an N5, and would be willing to help however possible.
Hunter1998 said:
I don't know much of anything about developing but am fairly competent and comfortable with flashing ROM's and kernels. I own an N5, and would be willing to help however possible.
Click to expand...
Click to collapse
In that case - file bugreports in JIRA, since your device does have a maintainer. One does not gain the skills to be a maintainer overnight. Most people I know, including myself were "co-maintainers" (assisting with bringup but not solo) on devices for a year or more before their first time "flying solo".
Entropy512 said:
In that case - file bugreports in JIRA, since your device does have a maintainer. One does not gain the skills to be a maintainer overnight. Most people I know, including myself were "co-maintainers" (assisting with bringup but not solo) on devices for a year or more before their first time "flying solo".
Click to expand...
Click to collapse
I became one overnight ._. (Nowhere near a skilled maintainer though.) I only know how to compile. Nothing other than that :/
lg e450
sorry if this the wrong thread to post.
I have an old lg e450(mtk 6575), and all the sources has been released by lg. Can anything be done to make this device alive?
Entropy512 said:
In that case - file bugreports in JIRA, since your device does have a maintainer. One does not gain the skills to be a maintainer overnight. Most people I know, including myself were "co-maintainers" (assisting with bringup but not solo) on devices for a year or more before their first time "flying solo".
Click to expand...
Click to collapse
Who do I need to contact to help?
It was a good ride...
https://www.cyanogenmod.org/blog/a-fork-in-the-road
Yep.. All nightlies will be discontinued.. Too bad CM
LineageOS
The link in the word Lineage take us to a GitHub for a new thing called LineageOS. So if I'm guessing what the future holds correctly, CM is getting rebranded as Lineage?
I look forward to the new direction. But I won't be using it until camera on OP3 is as good as stock.
Sent from my ONEPLUS A3003 using Tapatalk
Nooooooo! Please tell me this is an early April Fools joke.
RIP CM
Welcome LineageOS
https://github.com/LineageOS/android_device_oneplus_oneplus3
Yeah that's bad news man! But somehow it will live on we all know that. Thanks 4 the journey
I've used CM since 2.3.3. Thank You CM. Looking forward to the future...
Been using CyanogenMod since v6 on my Motorola Droid until now to v13 on OP3.
Was glad to see CM grow & was really amazing but now it's gone. RIP CM.
XDA loves you and Welcome LineageOS 2017.
Happy Holidays to all, Hope 2017 brings us a new Dawn.
Bring on Lineage.
While it is true that Cyanogen mod will loose it's name, the legacy behind the name will live on. Steve Kondik still owns the rights to his code, just not the name and as you have seen, everything is getting moved over to it's new home under the name of LineageOS. Screw Cygyn, they took CM into a completely different direction of what Kondik envisioned and to tell ya the truth, I am glad this happened, to get the OS back to it's roots and the meaning of what Kondik intended it to be from it's birth. Back to being for the community, by the community, giving the best experience, functionality and customizations for our devices, not about a bunch of corporate bs, greed and money.
kenboyles72 said:
While it is true that Cyanogen mod will loose it's name, the legacy behind the name will live on. Steve Kondik still owns the rights to his code, just not the name and as you have seen, everything is getting moved over to it's new home under the name of LineageOS. Screw Cygyn, they took CM into a completely different direction of what Kondik envisioned and to tell ya the truth, I am glad this happened, to get the OS back to it's roots and the meaning of what Kondik intended it to be from it's birth. Back to being for the community, by the community, giving the best experience, functionality and customizations for our devices, not about a bunch of corporate bs, greed and money.
Click to expand...
Click to collapse
Totally agree, I'm glad this is happening to, CM in its present form just uses too much bandaid and patch works solutions for its many bugs. I miss the CM back in the day. Hopefully lineage will bring that experience that Kondik originally envisioned back.
2016 can't leave normally.... Oh my god R.I.P CyanogenMod if it's true.
_MartyMan_ said:
2016 can't leave normally.... Oh my god R.I.P CyanogenMod if it's true.
Click to expand...
Click to collapse
It's True
Hope that future LineageOS will support OP3 also
GamaX320 said:
Hope that future LineageOS will support OP3 also
Click to expand...
Click to collapse
ALL current devices that have CM support, WILL have LineageOS support. lineageos is the same code a cm, they only had to change the name for legal reasons, as cyanogen inc. owns the cyanogen mod name.
They're importing the code to the github now. Give them a couple more days for nightlies to roll out.
bencozzy said:
Cyanogen is actually looking to bring legal action against the devs trying to rebrand CM as lineage OS so I wouldn't get too excited. It will be more excited to see CM die completely so we can have some real development occur or at least see some OEMS pick up the good developer's out there.
Click to expand...
Click to collapse
I don't know why you think that CM death would give benefit to the whole Android development scene.
It's not like there is lack of good developers in the world available for OEMs and open source ROMs, so her we are: a good established open source project shut OFF and pursued by Cyanogen Inc., and not much good alternatives available.
What is left?
AOSPA? No Nougat release.
Omni? Lights and shadows.
Other interesting custom ROMs not CM based?
bencozzy said:
Cyanogen is actually looking to bring legal action against the devs trying to rebrand CM as lineage OS so I wouldn't get too excited. It will be more excited to see CM die completely so we can have some real development occur or at least see some OEMS pick up the good developer's out there.
Click to expand...
Click to collapse
Without CM or Lineage, there's not much hope for dedicated development for many devices. Even today many devs rely on CM kernel to build newer version of android and wait for CM devs to fix bugs first and then cherry pick them.