Related
Question is does that indicate att is going release there froyo update for thee aria? Sent from my Liberty using XDA App
Where do you see this?
Modders and ROM developers are about to bury themselves in source code today and will chug six packs of Red Bull to stay up late into the night hacking away. HTC has released their valuable Android 2.2 source code for the EVO 4G, DROID Incredible, Aria, and Wildfire today allowing programmers and enthusiasts to get their hands dirty with code.
This is a pretty standard thing, as the Android operating system is open source and anything developed in conjunction with it has to be made available to the public. What’s funny about this release of code is that HTC has basically preempted all carriers except for Sprint as the Aria, Incredible, and Wildfire have yet to see the “official” release of Android 2.2. This confirms that it is the carriers that have slowed down the upgrade process on their devices making options like rooting and modding so popular. Even with the slow down, this release shows that the carriers are getting ready for the “official” releases.
The release of the Android 2.2 source for HTC devices is going to prove to be an awesome edition to what modders have already gained from earlier ROM leaks. So, keep your eyes out for some new ROMs over at xda-developers and other modding sites as it is about to get crazy out there!
Via [Cyanogen, Phandroid]
Source [HTC]
aepowerlifter said:
Modders and ROM developers are about to bury themselves in source code today and will chug six packs of Red Bull to stay up late into the night hacking away. HTC has released their valuable Android 2.2 source code for the EVO 4G, DROID Incredible, Aria, and Wildfire today allowing programmers and enthusiasts to get their hands dirty with code.
This is a pretty standard thing, as the Android operating system is open source and anything developed in conjunction with it has to be made available to the public. What’s funny about this release of code is that HTC has basically preempted all carriers except for Sprint as the Aria, Incredible, and Wildfire have yet to see the “official” release of Android 2.2. This confirms that it is the carriers that have slowed down the upgrade process on their devices making options like rooting and modding so popular. Even with the slow down, this release shows that the carriers are getting ready for the “official” releases.
The release of the Android 2.2 source for HTC devices is going to prove to be an awesome edition to what modders have already gained from earlier ROM leaks. So, keep your eyes out for some new ROMs over at xda-developers and other modding sites as it is about to get crazy out there!
Via [Cyanogen, Phandroid]
Source [HTC]
Click to expand...
Click to collapse
i saw this a while back...i was curious when we would start seeing some mods made from this...i wish i had the know how to develop this stuff id be all over it...perhaps someone on here is and there almost finished with it...i running the cm6 rom and its sweet just wish there was a better oc kernel that worked well with it
HTC has not and does not release "source code" for any of their ROMs, only the kernel sources which they are required to release. So far, kernel source released for the Aria is still behind the kernel source released for the Snapdragon processors that HTC used in it's 2.2 builds. Nothing new has been posted for the Aria for a while.
Ahe... I see not really much of a code monkey ..but i got you
Sent from my Liberty using XDA App
Well props on the froyo mod , using it right note..and thanks as well.
Sent from my Liberty using XDA App
Samsung has released the Android 2.2 source code for its Fascinate 3G+ for Telus. Which is basically the US Vibrant, good news?
Sent from my SGH-T959 using XDA App
I think samsung knows that vibrant owners are frustrated.. so they released the source code for the great developer to create roms off of...
Software must not be ready yet for the US variants and this is the least samsung can do, the source code as a band aid until the official froyo releases for the US vibrant..
edit.. oh samsung will release the code anyway.
Im normally not the type who nags on anyone's twitter... but after reading yesterday's maddening news/rumor about samsung flawed business practices that promotes greediness.. i did on both their twitter accounts.. lol..
After months of speculation, there is finally something clear about the Samsung Exynos processor…
Samsung will open Source the Mali codes Exynos Codes they will provide binaries all most everything.
This appears from the Samsung Developers Session in America. Samsung who hold today.
The entire information Samsung makes clear later but this is very good news for developers. This Samsung creates a big boost in their community.
They say there will be more information in the coming weeks!!!
SamMobile we keep you informed.
Share your thoughts, speculations
Source
http://www.sammobile.com/2012/10/21...nos-will-go-open-source/#.UIRNmGlUJEg.twitter
great news
LastStandingDroid said:
After months of speculation, there is finally something clear about the Samsung Exynos processor…
Samsung will open Source the Mali codes Exynos Codes they will provide binaries all most everything.
This appears from the Samsung Developers Session in America. Samsung who hold today.
The entire information Samsung makes clear later but this is very good news for developers. This Samsung creates a big boost in their community.
They say there will be more information in the coming weeks!!!
SamMobile we keep you informed.
Share your thoughts, speculations
Source
http://www.sammobile.com/2012/10/21...nos-will-go-open-source/#.UIRNmGlUJEg.twitter
Click to expand...
Click to collapse
Happy to hear that
n more happy to own a *SAMSUNG* galaxy S2.. :good:
Everyone calm down.
This is not done yet.
Yes, Samsung will release Exynos source code. "Hurraay!!!" ??? No!
What they mean by releasing Exynos source code, is that they will release source code for hardware modules for Exynos development boards. We had this for months on insignal website (which is down since a few weeks/months, but used to be up), which contains outdated source code for Exynos boards. We had some bits of Ice Cream Sandwich code back in March or April iirc, that helped Galaxy S II hwcomposer, but that's it. Most of the things were stuck at Gingerbread version, and they don't contain any device-related code.
What does this mean ? For instance, Galaxy S III camera will stay closed, because it is NOT part of Exynos development boards. Galaxy S II audio is still Yamaha proprietary crap, and we will NOT get source code. RIL interface will also remain closed, so all exynos phones will keep on having broken/semi-functional GSM connection (broken Sim Toolkit, unstable data connection, unstable roaming). TV Out will still remain undocumented, and Android interface won't be opensourced (as it is part of TouchWiz on official ROMs). Same applies for FM Radio.
Moreover, Insignal code drops were delayed as hell. As of today, we still haven't got anything from official Samsung Jelly Bean, beside kernel source code because they legally have to. As I said, most of the things on Insignal were old, hwcomposer sources for example weren't working on Galaxy S III (exynos4412), and so on.
Now, I could be wrong and MAYBE they will make this A BIT better (faster code drops), but I'm NOT putting my hopes up on things like Sensors HAL source code, Audio source code, RIL interface documentation, or Camera HAL source code. IMO they just spoke like this to calm down community flood, and make everyone happy and make Samsung look like they're the new holy grail of developers. I'm not trusting this until I actually SEE those improvements.
So, users, be careful, and we'll see how it's going to get.
http://forum.xda-developers.com/showpost.php?p=33092439&postcount=10618
anshmiester78900 said:
Everyone calm down.
This is not done yet.
Yes, Samsung will release Exynos source code. "Hurraay!!!" ??? No!
What they mean by releasing Exynos source code, is that they will release source code for hardware modules for Exynos development boards. We had this for months on insignal website (which is down since a few weeks/months, but used to be up), which contains outdated source code for Exynos boards. We had some bits of Ice Cream Sandwich code back in March or April iirc, that helped Galaxy S II hwcomposer, but that's it. Most of the things were stuck at Gingerbread version, and they don't contain any device-related code.
What does this mean ? For instance, Galaxy S III camera will stay closed, because it is NOT part of Exynos development boards. Galaxy S II audio is still Yamaha proprietary crap, and we will NOT get source code. RIL interface will also remain closed, so all exynos phones will keep on having broken/semi-functional GSM connection (broken Sim Toolkit, unstable data connection, unstable roaming). TV Out will still remain undocumented, and Android interface won't be opensourced (as it is part of TouchWiz on official ROMs). Same applies for FM Radio.
Moreover, Insignal code drops were delayed as hell. As of today, we still haven't got anything from official Samsung Jelly Bean, beside kernel source code because they legally have to. As I said, most of the things on Insignal were old, hwcomposer sources for example weren't working on Galaxy S III (exynos4412), and so on.
Now, I could be wrong and MAYBE they will make this A BIT better (faster code drops), but I'm NOT putting my hopes up on things like Sensors HAL source code, Audio source code, RIL interface documentation, or Camera HAL source code. IMO they just spoke like this to calm down community flood, and make everyone happy and make Samsung look like they're the new holy grail of developers. I'm not trusting this until I actually SEE those improvements.
So, users, be careful, and we'll see how it's going to get.
http://forum.xda-developers.com/showpost.php?p=33092439&postcount=10618
Click to expand...
Click to collapse
it was never told to be anything more than Exynos code to be released
If I learnt one thing from buying a samsung was:
Never buy a samsung, unless is a nexus!
I'm not sure what will be the usage of those docs though, most of the developers already migrated from samsung, atleast teamhacksung did
What about Galaxy note 2 AOSP, cm10, aokp ect. roms? Will that be any useful to them as in maybe s pen functionality?
D4rKn3sSyS said:
If I learnt one thing from buying a samsung was:
Never buy a samsung, unless is a nexus!
I'm not sure what will be the usage of those docs though, most of the developers already migrated from samsung, atleast teamhacksung did
Click to expand...
Click to collapse
+1
anshmiester78900 said:
Everyone calm down.
This is not done yet.
Yes, Samsung will release Exynos source code. "Hurraay!!!" ??? No!
What they mean by releasing Exynos source code, is that they will release source code for hardware modules for Exynos development boards. We had this for months on insignal website (which is down since a few weeks/months, but used to be up), which contains outdated source code for Exynos boards. We had some bits of Ice Cream Sandwich code back in March or April iirc, that helped Galaxy S II hwcomposer, but that's it. Most of the things were stuck at Gingerbread version, and they don't contain any device-related code.
What does this mean ? For instance, Galaxy S III camera will stay closed, because it is NOT part of Exynos development boards. Galaxy S II audio is still Yamaha proprietary crap, and we will NOT get source code. RIL interface will also remain closed, so all exynos phones will keep on having broken/semi-functional GSM connection (broken Sim Toolkit, unstable data connection, unstable roaming). TV Out will still remain undocumented, and Android interface won't be opensourced (as it is part of TouchWiz on official ROMs). Same applies for FM Radio.
Moreover, Insignal code drops were delayed as hell. As of today, we still haven't got anything from official Samsung Jelly Bean, beside kernel source code because they legally have to. As I said, most of the things on Insignal were old, hwcomposer sources for example weren't working on Galaxy S III (exynos4412), and so on.
Now, I could be wrong and MAYBE they will make this A BIT better (faster code drops), but I'm NOT putting my hopes up on things like Sensors HAL source code, Audio source code, RIL interface documentation, or Camera HAL source code. IMO they just spoke like this to calm down community flood, and make everyone happy and make Samsung look like they're the new holy grail of developers. I'm not trusting this until I actually SEE those improvements.
So, users, be careful, and we'll see how it's going to get.
http://forum.xda-developers.com/showpost.php?p=33092439&postcount=10618
Click to expand...
Click to collapse
Nice POW I didn't knew all this background before
Sent from my GT-I9100 using xda app-developers app
Samsung actually didnt want its customers to go for custom. Thats why they put so many features as a part of touchwiz in note 2 rather than independent apps. Its because they want to gather their users to be their advertisement material in future. They want to be the next apple. I heard a rumor that samsung is working on its own OS. they only wanted the developers in their bad times. When they were unable to port the ics to their devices. They actually used the dev community. When their stock roms are delayed its he devs that keep us silent by giving us the custom rom. Plus samsung didnt really want to release the source because most of the features of its new flagship phone will be ported to older devices. Like multi screen multitasking on note 2 will be ported to s3 and note 1. They are scared of this. They just want to sell new devices each year.
Sent from my GT-N7000 using xda app-developers app
Be careful man because as I know from past experience that some people like the phrase "never was heard a discouraging word" on here. You never know, you might be accused of making "false statements"!!!!
Sent from my GT-I9100 using xda premium
samsung is a real motherf***er if they will not release the code me and 15 friends will nerver buy any samsung stuff we all 15 friends have s2 s3 and samsung glaxy nexus
here if the samsung will not release the code 15 customer will leave the samsung
Here's Entropy512's take on the recent events:
Entropy512 said:
Ok quick checkin from BABBQ. After this post I'm putting my BT keyboard away and getting drunk, and likely won't return to XDA until Monday or Tuesday evening.
The official announcement was kinda "meh". It's really what's going on behind the scenes that is mattering.
There are multiple devrel people at Samsung, many of whom weren't even aware of each others' existence. They now are, and I have quite a few new contacts. Now, requests from us are probably going to go through multiple chains. Whether this makes a difference, who knows - but it is a potential step forward.
They also had an engineer from LSI that I talked to personally. It was a bit difficult due to the language barrier, but I sort of got the impression that the problems with current Insignal source on our phones aren't phone-specific - some of this **** is broken even on the OrigenBoard itself. Same case for libcamera - it sounds like the current Insignal one is pretty low-quality/broken, and the "new" source may be improved. It won't be directly usable on our devices, but it may represent a significant step forward. e.g. instead of "it's totally and completely broken", it may be "sorta working and needs some tweaking for each camera module" - See, for example, use of the Nexus S libcamera on Aries-family devices - each one has needed device-specific work, but instead of being an insurmountable task, it may be feasible. However, please keep reading regarding maintainer exhaustion...
I also got the impression that future Insignal drops are going to be more aggressively managed by LSI. Again... none of this is official.
November is likely to be another ICS tarball, however, one that is actually working. The engineer I spoke to said that the actual JB differences are minimal. (As in, I know what they are, and in fact we have an implementation of the JB differences in Gerrit already. The problem is the underlying hwcomposer is apparently broken even for OrigenBoard+ICS with the current Insignal source. Functional ICS HWC shouldn't be too hard to JB-ify. (Look at the Nexus S HWC as an example of what needs to be done to go from ICS to JB.)
The new source drop might also allow us to finally fix HDMI.
The problem is - Thanks to the lack of documentation for the past few months, the team of CM maintainers for Exynos are exhausted and far behind on other non-Exynos-specific stuff. So this isn't going to be a magic bullet. It alone probably won't get us M builds.
However the other "behind the scenes" item is that a bunch of Samsung people were here, and they're probably going to be writing trip reports to management. This trip reports are going to likely include the massive amount of pwnsauce Sony dished out. Speaking of that - Espenfjo, xplodwild, and codeworkx, Y U NO FLY HERE? Chainfire, Jerpelea, and Supercurio were all here. U NO GET SMARTWATCH!
So Samsung Mobile might be more receptive to community requests in the future. Our contacts are likely to be in a MUCH better position to facilitate things than before.
So it's a step forward... But it's likely to be months before any of us consider a new Exynos device, and our current devices are likely to always be behind others because we're just too far behind as it is. But if Samsung keeps on improving, after a few months users might see definitive improvements.
With all of that said, I'm off to party and feast. You won't see any more from me until Monday evening at the absolute earliest.
Sent from my GT-N8013 using Tapatalk 2
Click to expand...
Click to collapse
His post is a little more optimistic than xplodwild's, but we should wait and see like he said!
i think this is a step in the right direction
dont let your hope down i think something amazing is coming
bluefa1con said:
i think this is a step in the right direction
dont let your hope down i think something amazing is coming
Click to expand...
Click to collapse
Yeah, at this point it's better to be optimistic. Though we should still keep pressuring them until we have something concrete.
What does it mean for common user? Will that add some extra features for SGS II example or what?
LastStandingDroid said:
After months of speculation, there is finally something clear about the Samsung Exynos processor…
Samsung will open Source the Mali codes Exynos Codes they will provide binaries all most everything.
This appears from the Samsung Developers Session in America. Samsung who hold today.
The entire information Samsung makes clear later but this is very good news for developers. This Samsung creates a big boost in their community.
They say there will be more information in the coming weeks!!!
SamMobile we keep you informed.
Share your thoughts, speculations
Source
http://www.sammobile.com/2012/10/21...nos-will-go-open-source/#.UIRNmGlUJEg.twitter
Click to expand...
Click to collapse
That's most probably useless unless they have a significant changes about exynos docs because that news was for Origen board which so different h/w with s2.
Sent from my GT-I9100 using xda app-developers app
Burgscheinkerkdeiktraast said:
What does it mean for common user? Will that add some extra features for SGS II example or what?
Click to expand...
Click to collapse
This will make CM stable(its already stable for me but not stable for some samsung rom users here) and we will get future android versions without the help of samsung(if they release the correct sources which are required to cm devs)
Hi Everyone,
I just took delivery of my new S4 Exynos (Octa) and am surprised how few custom ROMS are out there for this device.
I had an S3 and so I'm kinda used to being spoilt for choice when it came to custom ROMS.
Any ideas why there's but a few for the Octa? Is it because of the chipset?
I saw Cyanogen have said they nt going to release any ROMS for the Octa
device is relatively new, exynos always gave headaches to devs of CM.....
give it time, some people said its not worth upgrading from an s3 so... yeah less custom ROMs
Really its a bitter truth...9500 has only 2 or 3 Devs till now with no update and fixes in lias 2 or 3 weeks ..that section seems like ghost busted :
9505 too has not as many Devs as HTC One has...however it has quite good dev support
I think after so many issues in s4 Devs are skipping it [probably] for note 3
lets wait and see in the near future if the outcome is bad, its hammer time !
Gboss01 said:
Hi Everyone,
I just took delivery of my new S4 Exynos (Octa) and am surprised how few custom ROMS are out there for this device.
I had an S3 and so I'm kinda used to being spoilt for choice when it came to custom ROMS.
Any ideas why there's but a few for the Octa? Is it because of the chipset?
I saw Cyanogen have said they nt going to release any ROMS for the Octa
Click to expand...
Click to collapse
To be clear - CM rarely says that a given device will NEVER be supported. The last time we did that was with the Snapdragon S1 and CM9 - That hardware was simply too weak to support ICS and later.
However, all of the CM maintainers that have worked with past Exynos variants refuse to touch it, and anyone else with maintainer experience saw what we went through with Exynos4 and also seem to be avoiding it.
There is always the possibility that someone new will pick things up - but honestly, I consider the likelihood to be very slim.
So CM support for the "Octa" is POSSIBLE - but it is HIGHLY UNLIKELY. I think that AndreiLux was the only experienced low-level (kernels, platform bringup) developer to touch the "Octa", and he's not particularly happy with it so far.
Entropy512 said:
So CM support for the "Octa" is POSSIBLE - but it is HIGHLY UNLIKELY. I think that AndreiLux was the only experienced low-level (kernels, platform bringup) developer to touch the "Octa", and he's not particularly happy with it so far.
Click to expand...
Click to collapse
Other than the CCI fiasco I'm relatively fine with the phone. I expected and was prepared to bring MP to the device but I guess that's not happening.
As for CM, I think it's more of a problem of lack of interest than actual technical feasibility. I'd happily dwell into the device platform world if I had time but that's not happening anytime soon as I have a backlog of features in the kernel space to do and finish.
AndreiLux said:
Other than the CCI fiasco I'm relatively fine with the phone. I expected and was prepared to bring MP to the device but I guess that's not happening.
As for CM, I think it's more of a problem of lack of interest than actual technical feasibility. I'd happily dwell into the device platform world if I had time but that's not happening anytime soon as I have a backlog of features in the kernel space to do and finish.
Click to expand...
Click to collapse
Why you will not bring it anymore?
Gboss01 said:
Hi Everyone,
I just took delivery of my new S4 Exynos (Octa) and am surprised how few custom ROMS are out there for this device.
I had an S3 and so I'm kinda used to being spoilt for choice when it came to custom ROMS.
Any ideas why there's but a few for the Octa? Is it because of the chipset?
I saw Cyanogen have said they nt going to release any ROMS for the Octa
Click to expand...
Click to collapse
No CM support does not equal to no dev support just to be clear. There are top.devs here ( Indie and Wanam) and there most likely be more devs to join the party. It is however a surprise that there's only a few Roms for this device at the moment.
Sent from my HTC One using Tapatalk 2
Well because most of the S4 users have the Snapdragon variant. As for CM, as Entropy said, its most probably not going to come out for our device, even if it does, it'll be broken and unusable due to lack of source code/documentation, etc. As for the custom ROMs, we'll have more of them but the best one IMO - Android Revolution HD - is very unlikely for our device.
The Octa is such a great phone yet the support seems to be lacking a little, I mean my Huawei U8800 had more development going on than this phone.
I dont get why alot of people are saying the Octa is crap compared to the S600 when the Octa beats the S600 in every benchmark I've seen.
Is the S600 an easier design to build custom ROMS for?
I have tried Doc Barebones ROM and Wanams Lite ROM. Both work well on the Octa but I found Docs ROM to the give me the highest Antutu scores, always above 30000 with the highest being 30890. Wanam's ROM didn't yield much more than the stock ROM, around 28300, same with the Omega v4 ROM.
I'm back to on the stock firmware, with bloatware removed, for now. having tried those three ROMS I'm itching to try another but alas I cant find any :crying:
Gboss01 said:
Is the S600 an easier design to build custom ROMS for?
Click to expand...
Click to collapse
Yes as Qualcomm is much more open source than Exynos. Not open source = pain in the a** to develop.
Sent from my GT-I9505 using Tapatalk 2
chickentuna said:
Yes as Qualcomm is much more open source than Exynos. Not open source = pain in the a** to develop.
Sent from my GT-I9505 using Tapatalk 2
Click to expand...
Click to collapse
Damn!
I read some where that Samsung might release the source code for the exynos. Is this true?
And if they did would that make it any easie rto develop ROMS for the Octa?
Just simply harder to develop anything for Exynos, i think.
I'd like to remind everyone that developers spend their own time and money on development.
Basically, unless the developer has a strong interest in a device he will not feel obliged to 'hack' features such as camera, noise canceling and so on.
I miss the old days of the HD2
I hope we can get CM on the 9500 because it will open the door for AOKP and Paranoid-Android and possibly MIUI.
Good luck to the developers.
RIP on i9500 haha just joking ... @AndreiLux are u giving up on i9500 ? oh please dont
As Entropy512 said, the problem is mostly because Exynos has terrible source code support. There are a lot of precompiled modules in the source, and these are tied to the Android version that the source code is for. This means that when a new version of Android comes out, you're stuck waiting for Samsung to catch up.
What the devs (like Entropy) have been trying to do is to create open-source versions of these modules, so that they're not reliant on Samsung. This has been extremely frustrating for them, requiring a lot of work for very little gain.
What would be ideal is for Samsung to provide source code and documentation for these precompiled modules. They're promised to do this several times, but so far have only delivered some code that only works for a reference board, not for the hardware configurations that any of their phones use. Even worse, the source code that is available is based on Gingerbread, and has numerous hacks applied to allow it to work with ICS. In short, it's just broken and will not work.
Qualcomm (Snapdragon), on the other hand, provide very good developer support. They and Texas Instruments (OMAP) have a very good reputation with the devs, with lots of source code and documentation available. That's why Snapdragon and OMAP phones are among the first to be supported when new versions of AOSP/AOKP/CM come out.
The I9500 may do better in the benchmarks than the I9505, but that's one of the few advantages it has.
Sent from my GT-I9505
I am not really interested in anything else but AOSP / CM on this phone. We badly need it.. I think we need to build the force on Twitter so that we can bombard their twitter account (@SamsungExynos) and force them to release at least some sorta source for Exynos.
I already started tweeting them like hell. Yes, they do reply with kind of SAFE sided replies..
Gboss01 said:
Damn!
I read some where that Samsung might release the source code for the exynos. Is this true?
And if they did would that make it any easie rto develop ROMS for the Octa?
Click to expand...
Click to collapse
If they did it would make the world of difference and Exynos would be on a level playing field in development terms as the likes of Snapdragon. Unfortunately, Samsung have been saying that since the original Galaxy S and it still hasn't happened, and it's clear they never intended to release anything and it was nothing more than lip service in an attempt to sell more handsets by appearing developer friendly. It's broken promises like this which has made reputable developers wash their hands with the Exynos chipset and any phones that use it. Unfortunately, this leaves people with the I9500 in a bit of a predicament if they're not fond of TW as it's likely to be their only option for the foreseeable, if not full stop.
Gboss01 said:
Damn!
I read some where that Samsung might release the source code for the exynos. Is this true?
And if they did would that make it any easie rto develop ROMS for the Octa?
Click to expand...
Click to collapse
Exynos open source? Highly unlikely and yes it would be much easier building roms, devs wouldn't even need to have the device to build a working ROM.
gdonanthony said:
RIP on i9500 haha just joking ... @AndreiLux are u giving up on i9500 ? oh please dont
Click to expand...
Click to collapse
He never said that, on the contrary he might be having some big plans
Sent from my GT-I9500 using Tapatalk 4 Beta
No Kernel source and so no custom roms
very disappointing ,They said they are going to release some quality source but Its been full 3 months now.
Jan is at its end which makes this almost 4 months
xiaomi released kernel source for mi max 2 after six months, so I guess they will release kernel source for our device after that same amount of time
https://twitter.com/MiIntrnModSeppe/status/955683630487146496
Guys,Check this out but I don'no if its true?!
He is just a mod in forum, I don't think he has anything to do with development. I have read his all reply stating not an employee of xiaomi
Well, Seppe looks like a normal mod, he occasionally posts on mi community and his Twitter looks normal, he said he got "internal sources" (maybe friends?)... Why would he lie? He had nothing to gain... This is interesting
Sources to be Released
Kernel Source released atlast......
Let the devs work their magic on....
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/tissot-n-oss