[Exynos sources are up]Let's the magic begin ! - Galaxy S II General

http://www.origenboard.org/wiki/index.php/Resources
Thx to http://forum.xda-developers.com/showthread.php?t=2003832

I hope this is it not some broke ass thing Samsung pointed us at to calm us down for a while
Sent from my GT-I9100 using Tapatalk 2

I hope this is what the devs needed, I tried the 4.1.2 leak and I came back to CM10 nightly hope it reaches stable.

Galaxy S2 has a Exynos 4210 processor, and apparently has published the user's guide and pre-built images: http://www.origenboard.org/wiki/index.php/Resources#Software_User.27s_Guide
Surely you can do something with it!

jrsoft said:
Galaxy S2 has a Exynos 4210 processor, and apparently has published the user's guide and pre-built images: http://www.origenboard.org/wiki/index.php/Resources#Software_User.27s_Guide
Surely you can do something with it!
Click to expand...
Click to collapse
Only a dev can tell...someone like entropy maybe
Sent from my GT-I9100 using Tapatalk 2

I doubt that they are not sources but some kind of trolling from Samsung. I wish i would be wrong.
EDIT::I AM SURE THEY ARE NOT THE REQUIRED SOURCES.
Sent from my GT-I9100 using Tapatalk 2

Nothing to see here, devs have already said this is useless for the stuff that needs fixing.

http://git.insignal.co.kr/samsung/exynos/android/platform/hardware/samsung_slsi/exynos4/
Note that the last commit date is October 25. Nothing new at all here. We saw that within a day after it went up, poked at it, and:
It has some additional HDMI stuff
It has some additional Low Power Audio (LPA) stuff
Other than that, it's almost identical in source code (and is identical in behavior) to the outdated broken **** that got Samsung in trouble in the first place. HWComposer is totally broken (indistinguishable in operation from no HWC at all), and without working HWC, the HDMI stuff is useless. (It's all tied together.)

Entropy512 said:
http://git.insignal.co.kr/samsung/exynos/android/platform/hardware/samsung_slsi/exynos4/
Note that the last commit date is October 25. Nothing new at all here. We saw that within a day after it went up, poked at it, and:
It has some additional HDMI stuff
It has some additional Low Power Audio (LPA) stuff
Other than that, it's almost identical in source code (and is identical in behavior) to the outdated broken **** that got Samsung in trouble in the first place. HWComposer is totally broken (indistinguishable in operation from no HWC at all), and without working HWC, the HDMI stuff is useless. (It's all tied together.)
Click to expand...
Click to collapse
i had a feeling our hopes will be crushed any ways how you feeling? got well from your cold ?

Read the schedule people. If its the same old **** on 14 december then they wont provide what they promised.
Close this one please.

Entropy512 said:
http://git.insignal.co.kr/samsung/exynos/android/platform/hardware/samsung_slsi/exynos4/
Note that the last commit date is October 25. Nothing new at all here. We saw that within a day after it went up, poked at it, and:
It has some additional HDMI stuff
It has some additional Low Power Audio (LPA) stuff
Other than that, it's almost identical in source code (and is identical in behavior) to the outdated broken **** that got Samsung in trouble in the first place. HWComposer is totally broken (indistinguishable in operation from no HWC at all), and without working HWC, the HDMI stuff is useless. (It's all tied together.)
Click to expand...
Click to collapse
What is to prevent us from thinking that Samsung wants to fix bugs first before CM / AOSP devs fix them.
I mean pride is at stake here. Especially if the coders are Korean.

Noob question, but what are the reasons that a manufacturer would want to withhold sources?
The only things I can think of are that it might need more qualification and review before the public are allowed to root through it to ensure there's no embarrassing mistakes / inefficiencies in there which would affect their reputation.

seanp25 said:
Noob question, but what are the reasons that a manufacturer would want to withhold sources?
The only things I can think of are that it might need more qualification and review before the public are allowed to root through it to ensure there's no embarrassing mistakes / inefficiencies in there which would affect their reputation.
Click to expand...
Click to collapse
Because manufacturers are MEANIES!!!
Real and possible reasons:
1. Proprietary driver code from third parties which post licensing issues
2. Generally poorly documented source that is shameful to release
3. Because the only people who care about source are geeks which are a very low proportion of their userbase, the rest don't even know source exists for their phone
4. Because their Exynos line isn't fairly widespread like other solutions (Snapdragon/OMAP) except in their own phones, so programming specialists are limited mostly to what Samsung provides (And the less prominent groups that muddle through the broken mess like the CM team)
5. Insert your own reason here
6. Insert Entropy's reasons here
7. loop;

karendar said:
2. Generally poorly documented source that is shameful to release
Click to expand...
Click to collapse
I can't help but feel as though this is the biggest reason. Back when 4210 was being actively developed and mainstream, Samsung had zero intention on making the source available for public scrutiny. They probably didn't bother documenting anything that didn't need it. Now that the pressure is on for them to be more transparent with their source, there is probably little motivation for them to dedicate the manpower needed to go back to what is essentially legacy code and clean it up so that it can be made public.
As more and more people get rid of their SIIs and Notes in favour of the next-gen Sammys, the pressure on Samsung to release 4210 sources becomes less and less. They're almost certainly just hoping that the problem will eventually go away. And unfortunately, it will.

Is this some kind of ad bing run by Samsung. if it is then just *****

Gillion said:
Especially if the coders are Korean.
Click to expand...
Click to collapse
Woah that was kind of racist.
Sent from my SHW-M250K using xda app-developers app

karendar said:
Because manufacturers are MEANIES!!!
Real and possible reasons:
1. Proprietary driver code from third parties which post licensing issues
2. Generally poorly documented source that is shameful to release
3. Because the only people who care about source are geeks which are a very low proportion of their userbase, the rest don't even know source exists for their phone
4. Because their Exynos line isn't fairly widespread like other solutions (Snapdragon/OMAP) except in their own phones, so programming specialists are limited mostly to what Samsung provides (And the less prominent groups that muddle through the broken mess like the CM team)
5. Insert your own reason here
6. Insert Entropy's reasons here
7. loop;
Click to expand...
Click to collapse
Absolutely spot on.
Sent from my GT-I9100 using xda premium

Totally agree with mckeowngoo.
We live in very wired world :cyclops:

Kitschki said:
Woah that was kind of racist.
Sent from my SHW-M250K using xda app-developers app
Click to expand...
Click to collapse
Ummm -_- ..........Sigh....... never mind.

Related

How lucky we all are

Just got done reading a petition about motorola's locked bootloader.
While sifting through the comments people made, pleading for motorola to remove their locks. I could only think of how so many members ridicule samsung. does everyone realize that they (samsung) gave us a great phone? That its almost unbrickable.. Sure froyo took a long time, but they admitted publicly that getting froyo out was a disaster and that they will take measures to make sure it won't happen again. And they even attempted to reach out to the community through samsungjohn.. even if it was just an attempt to calm the community, it shows samsung supports the community.. Or at the very least that they care about what we think and say.. Samsung could be a lot more like motorola, and completely overlook the needs and desires of the small percentage of users that our communities consist of.
my next phone will be a sgs2
Sent from my Rocking dj05, themed superdark w/o swype mod, voodoo 5, with custom boot and shutdown.. With premium xda app.
Yea. With htc following Motorola's path of locking down the bootloader, seems like samsung is one of the last to be developer friendly.
Sent from my SCH-I500
neh4pres said:
my next phone will be a sgs2
Click to expand...
Click to collapse
... unless they lock that too.
Not to many people realize how special this phone will be when we can overclock to 1.6ghz, that was mention in engadget i think. But this phone rocks with root and superclean. But the majority of people dont really take the time to explore android phones and all they offer. For example businessmen, my father who is in the insurance business used his droid x for almost everything. My brother rooted it and set up everything in a much more user friendly way. But just when everyone gets upset about no froyo (official) for fascinate, they forget the beauty of android, and thats its able to be edited by developers and that its open source. We arent supposed to have froyo yet most likely every fascinate owner on this forum has froyo.
sfournie said:
But just when everyone gets upset about no froyo (official) for fascinate, they forget the beauty of android, and thats its able to be edited by developers and that its open source. We arent supposed to have froyo yet most likely every fascinate owner on this forum has froyo.
Click to expand...
Click to collapse
Not to nitpick... but I'd like to just add a little bit of an aside here. There has been no official release of Froyo, which means that according to Samsung and Verizon, we shouldn't have it. (of course, some one will speak up and say "leaked builds are just a sneaky way that samsung gets free public beta testing." To that I say "maybe. But I doubt it.")
Not only that, but most of the cool mods in the dev/themes section are done to precompiled files that have been decompiled, modded, then recompiled, which takes massive amounts of time, and is a dirty process that leaves behind dead code and mismatched signatures. People are jumping through massive hoops to do something because we don't have the source code to edit it directly. Saying that the stock ROM is open, is like saying a jailbroken iPhone is open. It's only "open" because people have poured countless hours working around the restrictions of an already compiled system, using tools that took countless hours to make.
Both of these issues are actually a major gray area of the law, and if a pesky legal team got bored, it's hard to tell what kind of trouble they might be able to stir up (especially when the judicial system is all about $$).
Even after we do get the source code (which we still don't have), there are still lots of binary "blobs" of data that are already compiled, reducing the amount of control we actually have over the hardware devices and proprietary elements of the stock rom.
So Android is mostly open source, but Samsung is only as open as it wants to be. Their delay in releasing the source, bad coding, and use of proprietary code still sets them fairly in the realm of developer unfriendly. They just aren't as bad as some of the others.
GizmoDroid said:
Not to nitpick... but I'd like to just add a little bit of an aside here. There has been no official release of Froyo, which means that according to Samsung and Verizon, we shouldn't have it.
Both of these issues are actually a major gray area of the law, and if a pesky legal team got bored, it's hard to tell what kind of trouble they might be able to stir up (especially when the judicial system is all about $$).
So Android is mostly open source, but Samsung is only as open as it wants to be. Their delay in releasing the source, bad coding, and use of proprietary code still sets them fairly in the realm of developer unfriendly. They just aren't as bad as some of the others.
Click to expand...
Click to collapse
I am forever grateful for the dev teams hours spent on this phone to give us something that we shouldnt have. And I agree, I think its all about the money for the phone manufacturers. The nice thing about android is that you dont pay to upgrade, but thats also their downfall because whats in it for samsung if they work hard and release something that is stable for our phones. Loyal customers which is true and a big part of their business. But for the most part, their client base is so huge, our whining doesnt even put a dent in there sales. Furthermore, Verizon doesn't care about releasing the official froyo update because they have you in a 2 year contract. And as bad as the the wait has been to get froyo, I would never switch carriers because ATT is worse IMO, but who knows now that they bought T-Mobile.
neh4pres said:
my next phone will be a sgs2
Sent from my Rocking dj05, themed superdark w/o swype mod, voodoo 5, with custom boot and shutdown.. With premium xda app.
Click to expand...
Click to collapse
I've been debating getting a Bionic but in thinking more and more about it I have to agree with you. my next phone will be the Sgs2. I absolutely love my sgs even if we don't have an official froyo build, the great devs we have have me rocking a super clean voodoo that blows all my friends various moto, htc, etc devices out of the water.
Do I wish verizon and samsung pushed an official froyo build? Sure
will that lack of support stop me from getting my hands on the sgs2? Hell no.
Dalamar1320 said:
Do I wish verizon and samsung pushed an official froyo build? Sure
will that lack of support stop me from getting my hands on the sgs2? Hell no.
Click to expand...
Click to collapse
+1 I agree totally!!
Pretty sure that I'm going for the sgs2 as well. Bottom line: the Fascinate has been the best smart phone I've ever owned (even as only eclair). I enjoy all the flashing of Roms and Kernels too. Its kinda made owning the phone worth it. In other words, not having official release but trying out these leaks is great fun! I'm not nearly as bent out of shape as some others are about the lack of support by Samsung/Verizon. Sure, it would be nice if they were better about software releases but I ain't losing any sleep over it.
Sent from my SCH-I500 using Tapatalk
SOTK said:
Pretty sure that I'm going for the sgs2 as well. Bottom line: the Fascinate has been the best smart phone I've ever owned (even as only eclair). I enjoy all the flashing of Roms and Kernels too. Its kinda made owning the phone worth it. In other words, not having official release but trying out these leaks is great fun! I'm not nearly as bent out of shape as some others are about the lack of support by Samsung/Verizon. Sure, it would be nice if they were better about software releases but I ain't losing any sleep over it.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
Thats cool but allegedly thats going to have a signed bootloader too.
Used my fascinating voodoo powers

Release Honeycomb Petition!

hey all, i found this little guy floating around cyberspace and though maybe we should sign, who knows we can try right?
http://www.petitiononline.com/honey30/
Why? It will be released when it's ready.
This is dumb. Why would they release it before its done?
People are angry because the xoom has honeycomb, and honeycomb hasnt been released.
The xoom has an unfinished build of honeycomb. The SD card slot doesn't even work yet.
Also, when you say things like "found this floating around", when in reality you actually created it yourself... That doesn't help you gain any support.
Yea because google is somehow required to release honeycomb to the public, grow up
Okay, I know that everyone is infuriated by this petition. But there are still many devs that would enjoy making the source better by working on it now. Not to mention larger companies would like to have the source like barnes and noble and notion ink. It would just be nice if google posted the source with a disclaimker kf its problems
Sent from my PG06100 using XDA App
Lakers16 said:
This is dumb. Why would they release it before its done?
People are angry because the xoom has honeycomb, and honeycomb hasnt been released.
The xoom has an unfinished build of honeycomb. The SD card slot doesn't even work yet.
Also, when you say things like "found this floating around", when in reality you actually created it yourself... That doesn't help you gain any support.
Click to expand...
Click to collapse
Totally agree with you...
Google have some very good reasons for not releasing the source code. Mainly it's because of a key change in their strategy AGAINST the open source nature you love.
They are worried about issues like fragmentation and want to ensure anyone picking up an android device will feel its a 'high quality' device. By releasing the source code anyone can do what they like with it and some devices will fail badly. This makes android look bad. By keeping the source code in house Google can control who develops it and who can use it in their devices. This is all an attempt to maintain a 'high quality' feel to devices running android.
I know this goes against the open source nature everyone says Google has but at the end of the day they REALLY want to dominate the mobile OS war. I dont think a little online petition will send them running to think about their actions and then return to hand over the source code.
Agreed its unfinished. Why would you release code on an unfinished product? This is not about open source or fragmentation, blah blah blah. Its the fact they shoehorned Android on a tablet to compete with the iPad. When the code is finished they'll release it. For now we have gingerbread
Sent from my Eris ADR6200 using XDA App
edcoppen said:
Google have some very good reasons for not releasing the source code. Mainly it's because of a key change in their strategy AGAINST the open source nature you love.
They are worried about issues like fragmentation and want to ensure anyone picking up an android device will feel its a 'high quality' device. By releasing the source code anyone can do what they like with it and some devices will fail badly. This makes android look bad. By keeping the source code in house Google can control who develops it and who can use it in their devices. This is all an attempt to maintain a 'high quality' feel to devices running android.
I know this goes against the open source nature everyone says Google has but at the end of the day they REALLY want to dominate the mobile OS war. I dont think a little online petition will send them running to think about their actions and then return to hand over the source code.
Click to expand...
Click to collapse
What? You are completely wrong.
Honeycomb ISNT FINISHED. It has nothing to do with fragmentation. Google's new stance wont even effect the end user or even rom devs much, its simply to stop big companies from slapping their own terrible UI over the top.
The honeycomb source will be released when its good and ready. I'm pretty sure Google are required by law to release it anywany so just be patient.
Sent from my Nexus One using XDA Premium App
Meltus said:
its simply to stop big companies from slapping their own terrible UI over the top.
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
Galaxy Tab 8.9 and the new 10.1 have TouchJizz 4.0 all over them.
Meltus said:
its simply to stop big companies from slapping their own terrible UI over the top.
Click to expand...
Click to collapse
Its actually to discourage them from doing it.
Meltus said:
What? You are completely wrong.
Honeycomb ISNT FINISHED. It has nothing to do with fragmentation. Google's new stance wont even effect the end user or even rom devs much, its simply to stop big companies from slapping their own terrible UI over the top.
The honeycomb source will be released when its good and ready. I'm pretty sure Google are required by law to release it anywany so just be patient.
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
Completely wrong! The chief editor of engadget agrees that there is huge pressure for Google to change their strategy. Have a look at this article he wrote...
http://www.engadget.com/2011/04/09/editorial-androids-problem-isnt-fragmentation-its-contamina/
He says exactly the same as me, except I took it one step further by suggesting this is the reason Honeycomb hasn't been released yet. I agree with you that honeycomb still has improvements to be made before its source is released. I just don't believe that's all there is to it. There are other considerations too!
Also note this was released today, after my my comment was made
DanWilson said:
Galaxy Tab 8.9 and the new 10.1 have TouchJizz 4.0 all over them.
Click to expand...
Click to collapse
The touchwiz ux on the tabs looks real nice. Much easier to tell what some things do. Just my opinion.
Sent from my always stock, EC05 Epic 4G
Cyanogen himself said Honeycomb was probably a pile of hacks. Google needs to clean it up a little before we get a bunch of half assed horrible android tablets. I just wish they would put a hardware requirement and requires companies to update their devices at least once (like 2.2 -> 2.3) in a timely manner (like 2-3 months after the code is pushed to AOSP)

Samsungs inability to support the community....

Why need it be so hard to support the developers working on Samsung phones....releasing code that is impossible to work with....as on the sgs2 for example.....there are ways to work with and support those working on porting phones...Sony Ericsson has made that effort to support the community....so should Samsung....they make great phones wich could be even greater.....if only they embraced the community and made an effort to work with, and not against......
Sent from my GT-I9100 using Tapatalk
maybe you should research before you post pointless threads that have nothing to back up your points.
Samsung have arguably been the most developer friendly company.
If you're talking about releasing proprietary drivers then what the fk can SAMSUNG do about it? It isn't theirs, they can't give something that doesn't belong to them.
$1 gets you a reply
So then there is no way to make it easier to get things working without releasing proprietary drivers .......then i give up on believing there is a way to get a working port to the sgs2.....but as i refuse to accept that reality , i still believe there are things possible to be change.
To make it easier without releasing proprietary drivers ......
Well people could make their own drivers, but I believe they'd need the full architecture map and the details outlining. Moreover testing and refining would take an immense amount of time.
It's slightly more complicated that this in the software world.
1 - as soon as samsung release anything they become responsible for it, i.e. they also need to release manuals, maybe maintain, support etc.
2 - samsung have how many different active handsets ? And each of them needs to be supported. It's one HELL of a job. I wouldn't be surprised if they just don't have time or don't want to spend money to support community.
Either you have no idea or your just impatient,Think about Samsung,there one of the world largest electronics company's in the world,while your sat at home drinking coffee or tea,there bashing out a new product and ideas to try and make electronic lives that more easier,from TVs,Phones,Fridges,Microwaves,laptops,sound systems,mp3s,hardware for other manufacturers,every second of the every day there working on something,its amazing they have anytime to actually release stuff like this but they do it,they try and support our device as much as they can despite having a patent war with apple at the same time.There about 10 different variants of this device,each one is slightly different,each one has there own different hardware,each one needs there own drivers,each one also needs supported,S2 is also not the one they need to support,Theres S,Nexus S,Galaxy Nexus,ACE,W,R,all need supporting so when they release the code when they do,you have a think of what else there doing and be more grateful they do it compared with say htc,who only manufacture mobiles but are tight arses,Samsung even sent several Galaxy s2 to CyanogenMod to he could bring his software onto the device,they didnt have to but they did.If they didnt care,they wouldnt do any of this,There not perfect but trust me they do try
http://codeworkx.de/wordpress/
And i agree with you about all they are manufacturing and that they have a lot to do....and need not support all of the products if so needed....
Sent from my GT-I9100 using Tapatalk
NickoPulver said:
Why need it be so hard to support the developers working on Samsung phones....releasing code that is impossible to work with....as on the sgs2 for example.....there are ways to work with and support those working on porting phones...Sony Ericsson has made that effort to support the community....so should Samsung....they make great phones wich could be even greater.....if only they embraced the community and made an effort to work with, and not against......
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
wtf are you talking about? Please state how Samsung's released code for the I9100 is impossible to work with. Yes, apparently the original source release had some stability bugs (see Ninphetamine kernel thread), but Samsung fixed that MONTHS ago with update1...
Samsung is, in my opinion, the most developer-friendly manufacturer out there. Download mode (Odin) makes it almost impossible to hardbrick, and they're now the only major manufacturer that is not locking their bootloaders. They also usually release kernel source BEFORE a product even officially launches.
Entropy512 said:
Samsung is, in my opinion, the most developer-friendly manufacturer out there.
Click to expand...
Click to collapse
LOL.
ROFL.
ithehappy said:
LOL.
ROFL.
Click to expand...
Click to collapse
duno why your laughing, they are, not only did they even hire the founder of cyanogen, but they also sent the cyanogen devs a bunch of SGS2's when they first come out so that they would support the SGS2.
I don't understand why Samsung sent team Hacksung free SGS IIs only to hold them up by not giving them what they need to develop on them.
d3ck4rd said:
I don't understand why Samsung sent team Hacksung free SGS IIs only to hold them up by not giving them what they need to develop on them.
Click to expand...
Click to collapse
Good point there my friend.
ithehappy said:
LOL.
ROFL.
Click to expand...
Click to collapse
Name a manufacturer who has done a better job.
HTC? Locked bootloaders, kernel sources withheld for extremely long times.
Motorola? Locked bootloaders
LG? Don't really know - at least in the US, their devices tend to be such bugridden **** (such as the battery-hogging Thrill) that you'd spend months just getting to the point of a stock Samsung firmware.
Samsung donated devices to the Cyanogenmod team and gave them nearly everything they needed to port the device - the only thing that isn't working very well in CM7 is Bluetooth, and you can blame Broadcom for that. Broadcom are ****ing douchebags when it comes to open source, they are one of the LEAST developer-friendly companies on the planet. Unfortunately it seems like these days, your only choices for Wifi/Bluetooth implementations are either the BCM4330, TI's WLAN solution (which is tightly coupled to OMAP), or some wacky niche player (Samsung tried to do that with the Infuse and the STE CG2900 - that epicfailed for them.)
If you're referring to ICS - for ****s' sake, Samsung hasn't even released their own ICS firmware yet. The sense of entitlement on these forums is getting to be utterly ****ing ridiculous. It's almost unheard of for an AOSP bringup to be successful to an Android version higher than the latest manufacturer release.
Entropy512 said:
Name a manufacturer who has done a better job.
Click to expand...
Click to collapse
Sony Ericsson has actually helped with development for CM7, I think they take the cake .
Samsung is pretty cool too for donating phones to devs. Maybe they'll even help them develop in the future. One step at a time
NickoPulver said:
Why need it be so hard to support the developers working on Samsung phones....releasing code that is impossible to work with....as on the sgs2 for example.....there are ways to work with and support those working on porting phones...Sony Ericsson has made that effort to support the community....so should Samsung....they make great phones wich could be even greater.....if only they embraced the community and made an effort to work with, and not against......
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
So what would you like us to do? Petition them?
What outcome would you like?
If the code is "impossible to work with" then why are there so many kernels out there based on their code?
Also, your ENTER key says "hi", and your period key says "ouch".
Sammy might have lots of smartphones and lots of stuf to worry about and its all that story about proprietary drivers, software and all that crap, but the truth is if they wanted, it wasnt that dificult to help the team.
If you do a little search in the forum u will see devices sucessfully running AOSP cm9 alpha on Android 4.01 which is higher than the latest manufacturer release, since only nexus have ics lolol
d3ck4rd said:
I don't understand why Samsung sent team Hacksung free SGS IIs only to hold them up by not giving them what they need to develop on them.
Click to expand...
Click to collapse
That was just very very cheap advertising
Sent from my HTC Desire HD using xda premium
Why would Samsung even release ICS drivers for SGS2 when they are working on their own ICS release for it? You don't give out the plans to something that you are about to bring out to the market before you launch it. Think about that.
I have to agree. The sense of entitlement is a bit crazy.

Buy CM a N7100 for development.?

Is anyone up for the idea to start a collection to buy the CM team a N7100 so they can start working on getting us cm10?
When I spoke to xplodwild this was his reply
Guillaume (@xplodwild) tweeted at 7:21 PM on Fri, Oct 05, 2012:
@iseeguy Assuming someone do it, because as of now nobody have one neither wants to buy one.
(https://twitter.com/xplodwild/status/254149189792047104)
I'm happy to organise this with the CM team to kickoff development
Who's thinks it's a good idea?
I've donated to previous initiatives and will again
Just an FYI:
I not only have no interest in purchasing a device, but if you gave me a free one and offered $2000, I would say no.
I have better things to do than waste countless hours of my time fighting another non-Nexus Exynos.
xplodwild may be more receptive to continuing with Exynos, but at least in the case of myself and codeworkx, we are done. Our current devices are going to be our last Exynos devices unless Samsung makes major changes.
This is why I'll keep my note 1
Already on Jb PA
Maybe when development for the note 2 is already a big boy is change for it. Probably not.
Sent from my GT-N7000 using XDA Premium HD app
Really don't see any redeeming quality to putting cm10 on this device. The software makes this device what it is. Taking all that away makes it nothing more than a mini nexus 7. Nothing against cm10. It's great on most devices... But you are really devaluing the note by neuturing it of 75 percent of its features. This is kinda like running linux on a ps3. Yeah its neat to say you did it, but good luck playing a ps3 game.
Sent from my EVO using xda premium
Gordon Ramsay said:
Really don't see any redeeming quality to putting cm10 on this device. The software makes this device what it is. Taking all that away makes it nothing more than a mini nexus 7. Nothing against cm10. It's great on most devices... But you are really devaluing the note by neuturing it of 75 percent of its features. This is kinda like running linux on a ps3. Yeah its neat to say you did it, but good luck playing a ps3 game.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Well said!
Far enough, but it was worth a try
Can the mods please delete this thread.
Gordon Ramsay said:
Really don't see any redeeming quality to putting cm10 on this device. The software makes this device what it is. Taking all that away makes it nothing more than a mini nexus 7. Nothing against cm10. It's great on most devices... But you are really devaluing the note by neuturing it of 75 percent of its features. This is kinda like running linux on a ps3. Yeah its neat to say you did it, but good luck playing a ps3 game.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
+1,5
- f3w1n -
Entropy512 said:
Just an FYI:
I not only have no interest in purchasing a device, but if you gave me a free one and offered $2000, I would say no.
I have better things to do than waste countless hours of my time fighting another non-Nexus Exynos.
xplodwild may be more receptive to continuing with Exynos, but at least in the case of myself and codeworkx, we are done. Our current devices are going to be our last Exynos devices unless Samsung makes major changes.
Click to expand...
Click to collapse
Sounds like you lost your passion, and the reason you started doing this. Since when did people do it for it being easy? That is beyond dissapointing. I think you forgot how this all started sir.
I completely support this especially if its just for a dev to do it unofficially, but remember guys we can't hold the dev responsible for getting it done. You have to go into thinking your donating for the dev to have the phone and use it as they like not donate thinking your donating for that dev to be obligated to bring cm10. In the rezound forum we got a phone for protekk to help with aosp and people got demanding and were expecting him to bring it since they donated. This tore apart that community for a long time. So if you donate do it as a donation and not an expectation
Sent from my Rezound using xda app-developers app
Gordon Ramsay said:
Really don't see any redeeming quality to putting cm10 on this device. The software makes this device what it is. Taking all that away makes it nothing more than a mini nexus 7. Nothing against cm10. It's great on most devices... But you are really devaluing the note by neuturing it of 75 percent of its features. This is kinda like running linux on a ps3. Yeah its neat to say you did it, but good luck playing a ps3 game.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I would say that Paranoid Android is absolutely perfect for the Note. S-Pen can be handled through different applications like GNote, Memo etc. The ability to run applications in tablet mode is such an enhancement of the device that I don´t see any single feature with the Note II that somehow "compensates".
I can agree that pure CM10 isn´t the most interesting thing on the Note II since it has the phone UI but Paranoid Android is a completely different matter.
Since PA relies on CM, it is very important to get it for the N7100 in order to get going.
Windowed applications is very nice but also a feature I guess will be implemented in either AOSP or CM in the future. Don´t forget Overskreen and FloatNote etc.
I thought at first porting CM10 would be easy in it's current state due to shared hardware with S3. I would understand if they dropped future exynos but this is an existing thing already with minor differences.
I would donate too if we can see a new maintainer taking on the device. Would be a shame not having CM on the device. It brings so much stuff for what it is and also other devs bringing their extra tweaks on top of it. A wonderful ecosystem I wanna to see and follow on xda and my device =(
Sent from my GT-N7100 using xda premium
Gordon Ramsay said:
Really don't see any redeeming quality to putting cm10 on this device. The software makes this device what it is. Taking all that away makes it nothing more than a mini nexus 7. Nothing against cm10. It's great on most devices... But you are really devaluing the note by neuturing it of 75 percent of its features. This is kinda like running linux on a ps3. Yeah its neat to say you did it, but good luck playing a ps3 game.
Click to expand...
Click to collapse
Let's be honest here for just one moment, the Samsung S apps and the stylus are gimmicks that will be used once when the note is purchased then abandoned. I've owned the original note and now the note 2 and I never once pickup up the stylus for anything
What's more valuable is a fast, smooth and reliable OS
Just my opinion of course.
ipguy said:
Let's be honest here for just one moment, the Samsung S apps and the stylus are gimmicks that will be used once when the note is purchased then abandoned. I've owned the original note and now the note 2 and I never once pickup up the stylus for anything
What's more valuable is a fast, smooth and reliable OS
Just my opinion of course.
Click to expand...
Click to collapse
To you, but to many others (the majority of people) what Samsung is doing with features is why they are making the purchase. Honestly its mainly because of the new features as to why I'm going to upgade. I'll still have my OG note running PA CM10, which I love.
Sent from my cm_tenderloin using xda app-developers app
erick161 said:
To you, but to many others (the majority of people) what Samsung is doing with features is why they are making the purchase. Honestly its mainly because of the new features as to why I'm going to upgade. I'll still have my OG note running PA CM10, which I love.
Click to expand...
Click to collapse
Let agree to disagree then!
CurrentlyPissed said:
Sounds like you lost your passion, and the reason you started doing this. Since when did people do it for it being easy? That is beyond dissapointing. I think you forgot how this all started sir.
Click to expand...
Click to collapse
There's a difference between challenging, and utterly freaking impossible.
Challenging: Going through source and fixing bugs or adding new features. For example, for months I've wanted to try and rework the Exynos suspend/resume code to be more power efficient. (It locks cpufreq at 800 MHz and disables cpuidle for the entire suspend/resume cycle, which eats power. Also SOME interrupt service handler eats huge amounts of CPU on resume (the root cause of the classic Gingerbread "Android OS" bugs), and I'd like to figure out which one and see if it can be optimized.
Utterly freaking impossible: On a routine basis, figuring out what Samsung broke in their blobs and why it doesn't work the way it should. Trying to take totally broken nonfunctional source code and get it to work properly with zero documentation. See hwcomposer - unless a miracle happens, we will be continually stuck fighting blobs that Samsung gave us. Their blobs have some sort of significant magic not present in any reference source. The reference source creates a broken piece of **** that's almost indistinguishable from not having any hwc at all.
I've spent 10-20 hours or more per week of my spare time over the past three weeks fighting hwcomposer and making absolutely zero progress. I'm tired of flailing against a brick wall and getting nothing other than bloody knuckles.
jbounours said:
I thought at first porting CM10 would be easy in it's current state due to shared hardware with S3. I would understand if they dropped future exynos but this is an existing thing already with minor differences.
I would donate too if we can see a new maintainer taking on the device. Would be a shame not having CM on the device. It brings so much stuff for what it is and also other devs bringing their extra tweaks on top of it. A wonderful ecosystem I wanna to see and follow on xda and my device =(
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
No, porting CM10 won't be easy due to shared hardware with the S3. Have you noticed no Exynos device has M builds? Have you noticed that Exynos devices are almost always one of the last "flagship-class" devices to receive nightlies?
CM9 should never have been marked stable on Exynos devices - too many bugs remain and we lowered our standards for "stable" too much.
CM10 on Exynos is incredibly far from reaching M builds let alone a stable release and I don't think we have the manpower, motivation, or energy to take it to to the finish line, let alone the documentation needed to do so.
And what about CM11? The whole mess will just start all over again, if any maintainers are left on Exynos by then. Again, we'll be flailing against undocumented crap that didn't even quite work right with the Android version it was designed for, while those working on platforms that have proper documentation and reference source (OMAP and Qualcomm) will start moving ahead immediately. See JB on Qcoms - They took only a month or two to get ahead of where Exynos4 devices are NOW, 4-5 months after JB went live, and over half of the work those guys were doing was forward-merging CM customizations from CM9.
ipguy said:
I've owned the original note and now the note 2 and I never once pickup up the stylus for anything
What's more valuable is a fast, smooth and reliable OS
Just my opinion of course.
Click to expand...
Click to collapse
Then I wonder why did you buy Note at first place! IMO it's that S-Pen which makes this Note series special than other flagships like S series, and in Note II it has just gotten better.
And about your 2nd paragraph, say whatever, but kindly exclude the word 'reliable' from that list.
Sent from my GT-I9100
ithehappy said:
Then I wonder why did you buy Note at first place! IMO it's that S-Pen which makes this Note series special than other flagships like S series, and in Note II it has just gotten better.
And about your 2nd paragraph, say whatever, but kindly exclude the word 'reliable' from that list.
Click to expand...
Click to collapse
I purchased the note for the screen size mainly.
Isn't a reliable OS important?
ipguy said:
I purchased the note for the screen size mainly.
Isn't a reliable OS important?
Click to expand...
Click to collapse
To me a reliable OS is all that matters. But you didn't get the point what I've tried to say.
Sent from my GT-I9100
ipguy said:
I purchased the note for the screen size mainly.
Isn't a reliable OS important?
Click to expand...
Click to collapse
That's the primary reason I got my Note. Even if it didn't have a stylus I would've bought it for the screen.
Also, there are now plenty of pen apps that use the standard Android stylus APIs, so the Samsung-specific stuff is irrelevant at this point. For example, PS Touch works just fine on the Note 10.1 in AOSP. So does Quill, Papyrus, Memo Beta, LectureNotes, and a number of other apps.
The only thing beyond that which is missing are stylus gestures, and that's primarily an issue of manpower. I would've forward ported and cleaned up masiullah's pen gestures patches a month or two ago if there weren't a pile of other massively broken things unrelated to stylus.

How is it going with the Exynos sources?

Anyone know if Samsung has said anything new or is there any other news to the Exynos sources?
I did follow the thread that got locked down witch was good.
I don't have Facebook and I don't know how to use Twitter so it's not that easy to get news about the Exynos that the other thread provided.
It's going as suspected, right down the crapper, that is. Origenboard is "under construction" according to insignal.
Sh*tty as usual.
If there is a breakthrough you'll see some threads pop up about it.
I think it is time that the FESM | Free Exynos Sources Movement
thread should be unlocked and make use of the fact that Samsung needs good publicity with the release of S4. Now the 4412 is getting way behind the current chipsets including the new ones from the Exynos family, what the hell can still hold Samsung from releasing them>
stefankorun said:
I think it is time that the FESM | Free Exynos Sources Movement
thread should be unlocked and make use of the fact that Samsung needs good publicity with the release of S4. Now the 4412 is getting way behind the current chipsets including the new ones from the Exynos family, what the hell can still hold Samsung from releasing them>
Click to expand...
Click to collapse
Simple explanation: Money
Sent from my GT-I9300 using Tapatalk 2
Theshawty said:
Simple explanation: Money
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Yea, but i do see where he's coming from, that same money, or the potential loss it may come from bad publicity by them not releasing said sources may tilt the scales enough for them to find it worth it to release them. They'll be more exposed to bad publicity when they're releasing a new flagship device.
Not sure how farfetched this sounds, but who knows what makes a big corp like samsung tick on their insides... i think it's worth the shot.
Theshawty said:
Simple explanation: Money
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
To be honest there aren't many financial reasons not to release sources especially for hardware used with an open source system. If any thing it looses them money because people will buy more open devices.
We for example like open source if we wanted a closed source system we would get either an iPhone or windows phone, or at the very least not root.
I really can't see what Samsung would loose from not releasing sources, the people who don't care aren't keeping up with the news so they essentially don't matter, what does matter is the people moving to other devices over the sources.
Sent from my GT-I9300 using xda premium
delsus said:
I really can't see what Samsung would loose from not releasing sources, the people who don't care aren't keeping up with the news so they essentially don't matter, what does matter is the people moving to other devices over the sources.
Click to expand...
Click to collapse
They want make people to continuously buy new devices. Who would upgrade his aftermarket phone if it's able to run new software (and, may be provide better experience than current devices)? And this means loss of potential income for them.
Sent from my GT-I9300 using Tapatalk 2
It is true that (not) releasing the sources would affect just a tiny percent of their sales but it is often the case that those people are asked for advice when someone is buying a new phone. After the worst possible experience with LG I have personally revert 10+ people even considering LG as possibility and recommended sony as alternative.
Also there is a case (as myself) that are not informed about the problems with CM before buying the phone as it never came to my mind that the most developed family of phone will have problems with cyanogen.
It would be great if we can work together with the S2 community because when the phone gets into the third year of existence it is more dependent on CM than official moded roms.
---------- Post added at 02:41 PM ---------- Previous post was at 02:37 PM ----------
-error said:
They want make people to continuously buy new devices. Who would upgrade his aftermarket phone if it's able to run new software (and, may be provide better experience than current devices)? And this means loss of potential income for them.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Most of the people who want to run CM so they dont buy new device are familiar with this problem are more likely not to update to Samsung anyway.
so what's so hard about using Twitter?
Well at least we should organise not just some useless spam now and then.
You seriously think it would matter if you organize or spam now and then? They couldn't care less either way.
You have more chance to have Lisa Ann and Amy Reid in your bed at the same time than seeing these sources mate forget about them...CM 10.1 runs prtty nicely on our device even if it could be way better
Darius_AWS said:
You have more chance to have Lisa Ann and Amy Reid in your bed at the same time than seeing these sources mate forget about them...CM 10.1 runs prtty nicely on our device even if it could be way better
Click to expand...
Click to collapse
I agree.
We would also have a bigger chance of Jessica Alba handing out free blowjobs to everyone on XDA than Samsung giving us those sources.
Theshawty said:
I agree.
We would also have a bigger chance of Jessica Alba handing out free blowjobs to everyone on XDA than Samsung giving us those sources.
Click to expand...
Click to collapse
Hahahaha that would be even better than the sources...
Sent from my GT-I9300 using xda app-developers app
endrit9 said:
Hahahaha that would be even better than the sources...
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Fair enough. ^^
After all, Jessica Alba is one very fair lady. A mother I would most certainly like to -beep-
Woah! I just saw one of the most fair comparisons.
chances of Samsung releasing sources < Pornstars on our bed + an actress offering blowjobs..
xD
Well, ONE QUESTION. does UBUNTU TOUCH also require these sources??
Thx for this post
Rom: xperia z 9.6.1
Kernel : boeffla 2.8
supreethms said:
Woah! I just saw one of the most fair comparisons.
chances of Samsung releasing sources < Pornstars on our bed + an actress offering blowjobs..
xD
Well, ONE QUESTION. does UBUNTU TOUCH also require these sources??
Click to expand...
Click to collapse
Yes, because it relies on CM10.1.
And I don't agree with you guys: even if Samsung don't release the sources, it's too easy to leave them alone (they don't comply with their license obligations, plus their promise, and on top of that, nobody bothers them), at least we should let them know we don't like to be f***** and it was the last device we buy from them.
that's cute
you're so naive

Categories

Resources