Help get documentation for Exynos SoC - AT&T Samsung Galaxy S II Skyrocket SGH-I727

I've started this thread in a hope to spread awareness in a major flaw of Samsung. Though they release the source code for their devices usually in a timely manner, unfortunately the same can't be said for their Exynos soc documentation. I know that our phone doesn't incorporate this chip, but it doesn't mean we can't help the fellow community receive the same benefits as the rest of us. This especially is important to me because I planning on purchasing the Galaxy Note 2 :silly:
A thread was started in the International GS3 thread to help acquire the documentation for their device and an already written inquiry is available to be sent to Samsung's open source department, just use the link on the page. I edited the inquiry when posting it myself to include all device that current have the Exynos chip along with future devices.
Link to page:http://forum.xda-developers.com/showthread.php?t=1925709
Let's join together as a community and help Samsung understand how important this to all of us, even if you never plan on owning a device with the Exynos chip. As stated by Codeworkx,
Quote:
Originally Posted by codeworkx
If they don't know that there are a lot of users out who are pissed because of the bad exynos support, then they'll not change anything.
If 10 users are crying -> just 10 users, ignore them.
If 1000 users are crying -> ok, let's think a few minutes about it.
If 100.000 users are crying -> holy ****, we have to do something
If you stop crying, they'll stop paying attention and you've achieved nothing like in the past.
Yes, it's not the nice way. But it's the only way to give the community a voice.

mjwhirly said:
I've started this thread in a hope to spread awareness in a major flaw of Samsung. Though they release the source code for their devices usually in a timely manner, unfortunately the same can't be said for their Exynos soc documentation. I know that our phone doesn't incorporate this chip, but it doesn't mean we can't help the fellow community receive the same benefits as the rest of us. This especially is important to me because I planning on purchasing the Galaxy Note 2 :silly:
A thread was started in the International GS3 thread to help acquire the documentation for their device and an already written inquiry is available to be sent to Samsung's open source department, just use the link on the page. I edited the inquiry when posting it myself to include all device that current have the Exynos chip along with future devices.
Link to page:http://forum.xda-developers.com/showthread.php?t=1925709
Let's join together as a community and help Samsung understand how important this to all of us, even if you never plan on owning a device with the Exynos chip. As stated by Codeworkx,
Quote:
Originally Posted by codeworkx
If they don't know that there are a lot of users out who are pissed because of the bad exynos support, then they'll not change anything.
If 10 users are crying -> just 10 users, ignore them.
If 1000 users are crying -> ok, let's think a few minutes about it.
If 100.000 users are crying -> holy ****, we have to do something
If you stop crying, they'll stop paying attention and you've achieved nothing like in the past.
Yes, it's not the nice way. But it's the only way to give the community a voice.
Click to expand...
Click to collapse
I hate to brake it to you but the skyrocket doesn't have the Exynos soc.

tjsooley said:
I hate to brake it to you but the skyrocket doesn't have the Exynos soc.
Click to expand...
Click to collapse
He mentions that in the second sentence in his post...
That said, I agree that it's a good thing to do. If they get away with it once, they may try it again (providing this was intentional), and again and eventually not release the source for anything.

This thread is off topic. Please keep things here about the Skyrocket. Thank you.

Related

[READ] This is the SGH-T959V(SGS4G) Not The Vibrant, or the Galaxy S 4

Hello Android Developers | ROM Flashers | Hackers | Modifiers | "I want my phone to look cool" People
First of all, I'd like to point out a few interesting things about this device.
-This is an Android powered phone that is officially supported to Android 2.3.6 Gingerbread
-The is the Galaxy S 4G. It is part of the Original Galaxy S (1st Generation) series and was once offered by ]"THREE" carriers. Mainly T-Mobile, secondly Wind Mobile, and most infrequently, Telus. The unique think about this phone is it was the first 4G Galaxy S Phone on T-Mobile.
-The model numbers are SGH-T959V(For T-Mobile), SGH-T959W(For Wind Mobile), and SGH-T959P(For Telus).
-A vast majority of support on this forum goes to the SGH-T959V for T-Mobile as it is the most common. There are a few T959W users on this forum who also have a few important threads, as well as if you are a T959W user, it is smart to note that yes, you can generally flash T959V roms, yet, you should "NOT" flash T959V Bootloaders and other such partitions such as the Boot, SBL, and Param sections as this MAY result in a permanent brick.
-There are no current T959P specific posts, and it is unknown whether there are any Telus users here. It is currently unknown but probably consistent that these users may be able to flash T959V roms.
OST OR ASK QUESTION
NOW THE MAIN POINT
First, If you haven't read the above section. GO BACK AND READ IT
MAIN MESSAGE
To all noobs, the T-Mobile (WInd or Telus) Galaxy S 4G is NOT internally similar to its predecessor, the T-Mobile Galaxy S Vibrant which lacks 4G and Gingerbread support. If you flash a Galaxy S Vibrant ROM, your phone may (and probably will) die, and will likely be void from warranty if you still have it! You should only flash ROMS available in THiS forum. All other Galaxy S variants including Galaxy S I9000, and other Galaxy S SGH model ROMS, Galaxy Y ROMS, Galaxy S II ROMS, Galaxy S III ROMS, Galaxy Note I ROMS, Galaxy Note II Roms, Galaxy Note 10.1 ROMS, Galaxy Tab ROMS, Galaxy Player ROMS, and any other Android Phone ROM will also kill the phone.
The label, Galaxy S doesn't mean Galaxy S "4G". There is a "HUGE" difference.
THERE ARE NOW AN INCOMING FLOOD OF GALAXY S "4" USERS.... THIS IS AN ENTIRELY DIFFERENT DEVICE... PLEASE POST IN THE FORUM THAT CORRESPONDS TO THE MODEL NUMBER BEHIND YOUR BATTERY
THE MAIN PURPOSE OF THIS WARNING IS TO STOP GALAXY S 4G AND GALAXY S VIBRANT USERS FROM FLASHING ROMS THAT ARE NOT FROM THEIR EXACT PHONE'S FORUM AS WELL AS TO STOP AN INCOMING FLOOD OF GALAXY S 4 USERS TO POST QUESTIONS IN HERE
Bump for sticky.
Bump bump BUMP!!!
Sent from my SGH-T959V using xda premium
bhundven said:
Bump for sticky.
Click to expand...
Click to collapse
Seriously, sticky this beast. Its almost every day I see a thread with some poor sap who didn't do ANY research, has a bricked phone because he was trying to flash a vibrant ROM XD
While part of me says that if they can't bother to do the research before messing with a very expencive device then they deserve to be bricked with a voided warranty but then the other part says that this is good info so it is now stuck.
i do have to agree that this is good info, but isn't this referring to #3 in the 10 commandments thread? just wondering.
droidmyst said:
i do have to agree that this is good info, but isn't this referring to #3 in the 10 commandments thread? just wondering.
Click to expand...
Click to collapse
Good point. From some of the threads I've been reading, it doesn't sound like some people even pay attention to the stickies as it is.
Maybe the better question: Does having yet another sticky stop people from posting stupid stuff? Probably not.
I'm proud to be a part of this forum and community, and I'm tired of having to filter through a bunch of crap to find the needle(useful post) in the haystack(thread).
I hope that we, as a community, can band together to report abusive users (by clicking the alert triangle in the title bar of the abusive user's comment) and to help nurture the newbies to feel safe to ask questions so they don't follow bad advise and bootloop or worse... brick.
I hope that this being sticky catches someone's eye so they don't flash the wrong roms, if they are on other phones.
For the record I came to this site after flashing a vibrant rom through(gasp) ROM Manager. You know the story. Only option close to this phone was VIBRANT(this was back in feb and still the same). Some better googling led me here. Fixed my problem without so much as a post. Other people think and act different than I do. They will ask for help. They will be noobs. It's your choice whether or not to help. If you choose not to help than let that be it.
Oh bye the way NO ONE reads stickies
hechoen said:
For the record I came to this site after flashing a vibrant rom through(gasp) ROM Manager. You know the story. Only option close to this phone was VIBRANT(this was back in feb and still the same). Some better googling led me here. Fixed my problem without so much as a post. Other people think and act different than I do. They will ask for help. They will be noobs. It's your choice whether or not to help. If you choose not to help than let that be it.
Oh bye the way NO ONE reads stickies
Click to expand...
Click to collapse
Well then they deserve what they get.
Rewritting the OS on your phone without doing the needed research is just plain stupid
zelendel said:
Well then they deserve what they get.
Rewritting the OS on your phone without doing the needed research is just plain stupid
Click to expand...
Click to collapse
I thanked, because it seems to be the biggest problem with this site.
No one reads the stickies.
Should the site maybe implement a lightbox of some sort that pops up to remind users of the rules and reading the stickies and ops?
EDIT: It would be annoying, but if it worked, it would become less annoying to *not* have to scroll through 100-200 page threads of newbs fighting over stupid crap posted in the sticky and op...
bhundven said:
I thanked, because it seems to be the biggest problem with this site.
No one reads the stickies.
Should the site maybe implement a lightbox of some sort that pops up to remind users of the rules and reading the stickies and ops?
EDIT: It would be annoying, but if it worked, it would become less annoying to *not* have to scroll through 100-200 page threads of newbs fighting over stupid crap posted in the sticky and op...
Click to expand...
Click to collapse
We have tried to make things as easy as we can but in the end this is a development site so when joining is is expected that people research and learn. I just wish people would stop following videos that are mostly out dated. It is amazing how lazy some people are. To be honest I am all out of pity and sympathy for those that don't do their homework. Its not rocket science after all lol
zelendel said:
We have tried to make things as easy as we can but in the end this is a development site so when joining is is expected that people research and learn. I just wish people would stop following videos that are mostly out dated. It is amazing how lazy some people are. To be honest I am all out of pity and sympathy for those that don't do their homework. Its not rocket science after all lol
Click to expand...
Click to collapse
It's not rocket surgery or brain science. The simple fact is people want an easy way to do things. That's why they(myself inluded) are here. My homework is my own. So is my frustration. I ask not for sympathy but for pentance. I am so fuc?ing tired of off the cuff remarks from users of this site that claim to "know it all" but slam some poor ****er asking for help. How do you build a comminity on top of that? Search for sure. Notice the hottest topic right now is this one?
Zeledel
Do not expect people to be you. I sure as hell don't
I don't but I do expect them to do what I did when started, the same thing that everyone is expected to do. And that is to spend a good amount of time reading. When I started I knew nothing of modding and only had basic computer skills. So I joined and spent weeks reading up on what I was doing before I even attempted to software unlock my device. If you asked a question here without doing your research you were flamed left and right as it was and still is expected that people do the research before posting. Mainly sense modding your phone breaks your warranty and if you bricked it there was no way back and no returning to stock to return it.
As for the off the cuff remarks, I am sorry it has come to this. You can ask any one of my team mates. I am the first to spend hours upon hours helping people. Hell I have even spent 4 hours on an international call to help a user that has bricked his phone. In the end it comes down to if you do the research and then after all the work it is still acting up then people are more opted to help.
zelendel said:
I don't but I do expect them to do what I did when started, the same thing that everyone is expected to do. And that is to spend a good amount of time reading. When I started I knew nothing of modding and only had basic computer skills. So I joined and spent weeks reading up on what I was doing before I even attempted to software unlock my device. If you asked a question here without doing your research you were flamed left and right as it was and still is expected that people do the research before posting. Mainly sense modding your phone breaks your warranty and if you bricked it there was no way back and no returning to stock to return it.
As for the off the cuff remarks, I am sorry it has come to this. You can ask any one of my team mates. I am the first to spend hours upon hours helping people. Hell I have even spent 4 hours on an international call to help a user that has bricked his phone. In the end it comes down to if you do the research and then after all the work it is still acting up then people are more opted to help.
Click to expand...
Click to collapse
One thing to remember alot of people are not you. We agree are many things. People are still not you. Because A = B if I am A or B than we are the same. C is always an option. Be the better person don't expect or think humane kind will hold themselves in that same regard. Be who you are but remember C is also an option.
hechoen said:
One thing to remember alot of people are not you. We agree are many things. People are still not you. Because A = B if I am A or B than we are the same. C is always an option. Be the better person don't expect or think humane kind will hold themselves in that same regard. Be who you are but remember C is also an option.
Click to expand...
Click to collapse
Agreed.
For anyone that has been keeping up. Please don't think that I am trying to say that I am like some tech guru. Lol far from it. I only meant to show what can happen when you put some love, effort, common since, strong searchfu toss in some grey hairs into your device. Never know the guy that joins XDA tomorrow may become the next CM.
If you believe you can or if you believe you can't either way you are right.
pft.
Sometimes when your having a bad day, keeping your fingers off the keyboard makes things better.
I had to re-read hechoen 3 times until I got it.
agreed. Also, people should not flash to their phone until they really know what they are doing. When I first rooted my G1, I read for 2 months before trying. Also, I ended up frying my rom and being stuck i bootloader for a day, but I never posted a single thread anywhere(I wasn't a member). So before people say "HELP, am I bricked?" they should try "EVERYTHING" to solve their own problems. The senior members aren't the phone company warranty plans.
google does a good job of leading other galaxy variants to different forum. When i first googled this phone google led me to the i9000 forum, and from reviews and comparisons on other sites they say this phone is very similar to the vibrant so its easy to get confused.Its bad enough samsung has like 10 phones with the galaxy name on it too. I think this thread should be stickied on general and Q and A also, its very easy to be misled here.
Sticky vs. Wiki
airfluip1 said:
To all noobs, the galaxy s 4g isn't the vibrant, if you flash a vibrant rom, your phone may die. You should only flash roms available in this forum. Galaxy S I9000 roms and GS2 roms will also kill the phone. The label, Galaxy S doesn't mean Galaxy S "4G". There is a "HUGE" difference.
Click to expand...
Click to collapse
So, why is the xda-dev wiki leading noobs to believe otherwise?
Clicking on that link (which is supposedly a list of all the Galaxy S models), we see the Galaxy S 4G nestled in amongst all the generic Galaxy S models. Shouldn't there be a separate section here for the 4G just as there is for a Galaxy S II and a Galaxy Tablet?
It's one thing to make this post a Sticky (which may or may not be found via searching), and quite another to deliberately classify the Galaxy S 4G as a Galaxy S on the Wiki (which is much more prominent than a Sticky)!
p.s.
I had specifically asked a moderator to create a new group for the Galaxy S 4G over 6 months ago...
[email protected] said:
So, why is the xda-dev wiki leading noobs to believe otherwise?
Clicking on that link (which is supposedly a list of all the Galaxy S models), we see the Galaxy S 4G nestled in amongst all the generic Galaxy S models. Shouldn't there be a separate section here for the 4G just as there is for a Galaxy S II and a Galaxy Tablet?
It's one thing to make this post a Sticky (which may or may not be found via searching), and quite another to deliberately classify the Galaxy S 4G as a Galaxy S on the Wiki (which is much more prominent than a Sticky)!
p.s.
I had specifically asked a moderator to create a new group for the Galaxy S 4G over 6 months ago...
Click to expand...
Click to collapse
I actually beg to differ. The galaxy s 4g is a 'galaxy s' phone based on the s5pc1xx (specifically the s5pc110 in PoP with the onenand-flex and dram, just like the epic4g and fascinate) processor (hummingbird chipset). The sgs2 is based on the exynos chipset.
The tablet IS in a class of it's own.
I don't understand your post.
Sent from my SGH-T959V using xda premium

Say Goodbye to the Menu Button

So I don't have any where else to put it(I think it should go under development but the rules say - if you didn't create it it doesn't belong there) but I found this post really interesting so Enjoy
I noticed it with the nexus s, may this be the reason we'll not get ICS??
inmortal009 said:
I noticed it with the nexus s, may this be the reason we'll not get ICS??
Click to expand...
Click to collapse
not at all - it has nothing to do with it(as far as I understand)
Interesting read, but why would this belong in the development forum?
You did the right thing posting it in the general forum,as this is exactly where it belongs.
MarkP80nj said:
Interesting read, but why would this belong in the development forum?
You did the right thing posting it in the general forum,as this is exactly where it belongs.
Click to expand...
Click to collapse
I thought it belonged to development because its talking about hmm...development but I guess here was a better place after all
Originally Posted by MarkP80nj
Interesting read, but why would this belong in the development forum?
You did the right thing posting it in the general forum,as this is exactly where it belongs.
Click to expand...
Click to collapse
I thought it belonged to development because its talking about hmm...development but I guess here was a better place after all
Click to expand...
Click to collapse
This is a common misconception about the development forum.
It's not for things talking about development.
It's for things you have developed.
IOW, the only time one should start a thread on that forum is when one has developed something, and wants to share it with the community.
Anyways, sorry for the derail.
Not trying to sound like an ass or anything.
You did the right thing, and thanks for sharing the link.
MarkP80nj said:
This is a common misconception about the development forum.
It's not for things talking about development.
It's for things you have developed.
IOW, the only time one should start a thread on that forum is when one has developed something, and wants to share it with the community.
Anyways, sorry for the derail.
Not trying to sound like an ass or anything.
You did the right thing, and thanks for sharing the link.
Click to expand...
Click to collapse
sure, np don't worry about it
In spite of Samsung's best efforts to bury the news by reporting it a couple of days before Christmas, Friday's disclosure that the Galaxy S and Galaxy Tab won't get upgraded to Android 4.0 drew a lot of justified ire. Now the company seems to be backtracking like a champ, as reported by ajnews in Korea, by claiming that it will review the viability of updating those two devices in response to strong customer demand. While restating the difficulties of fitting its entire software footprint onto the Galaxy S and Tab's limited memory capacity, Samsung has been quoted as saying it'll investigate ways to try and make it work. We've reached out to Samsung for official comment on the matter and will update you as soon as we hear back.
http://www.theverge.com/2011/12/27/2663320/samsung-galaxy-s-and-galaxy-tab-ics-upgrade-review
RaverX3X said:
In spite of Samsung's best efforts to bury the news by reporting it a couple of days before Christmas, Friday's disclosure that the Galaxy S and Galaxy Tab won't get upgraded to Android 4.0 drew a lot of justified ire. Now the company seems to be backtracking like a champ, as reported by ajnews in Korea, by claiming that it will review the viability of updating those two devices in response to strong customer demand. While restating the difficulties of fitting its entire software footprint onto the Galaxy S and Tab's limited memory capacity, Samsung has been quoted as saying it'll investigate ways to try and make it work. We've reached out to Samsung for official comment on the matter and will update you as soon as we hear back.
http://www.theverge.com/2011/12/27/2663320/samsung-galaxy-s-and-galaxy-tab-ics-upgrade-review
Click to expand...
Click to collapse
awesome news - 10x for sharing

Qualcomm releases Adreno 2xx User-mode Android ICS Graphics Driver (ARMv6)

PROGRESS
25 MARCH 12 - Please sign the Groubal petition here (thanks to nfs1mw for the heads up):
http://www.groubal.com/ics-drivers-compiled-for-armv6-from-qualcomm/
27 MARCH 12 - Received an email from the CEO of Groubal (see here).
29 MARCH 12 - Mission accomplished! Qualcomm has released the drivers here.
Click to expand...
Click to collapse
We voiced our opinion. Qualcomm heard our opinion. Qualcomm released the drivers. Time for some serious ICS ports
Article on the XDA portal: http://www.xda-developers.com/andro...no-2xx-gpu-binaries-for-on-ics-armv6-devices/
sweetnsour said:
I started the petition on March 25. Four days later, the drivers for ARMv6 has been released. I would like to thank the following for making this happen:
nfs1mw: It was nfs1mw who had told me about Groubal, and if it weren't for him, I would have never heard of the petition, which means that I would have never made it. He deserves a lot of credit.
Groubal: Groubal gave us the means to voice our opinions. Many of us wanted the drivers but there wasn't much we can do. Our individual voices did not mean much. Groubal helped unify our individual voices into one, making it possible for our voice to be heard by Qualcomm.
Qualcomm: Of course, Qualcomm did not have to listen to us. But they did. Thanks to Qualcomm for listening to what we had to say. The drivers they released will definitely help a lot of developers who are porting CM9. I remember reading a conversation that said a device could not be supported if it used a hack for hardware acceleration. Now, things are going to change with these drivers. We should all head over to Qualcomm's forums and thank them for all they have done.
You: I'm sure that a lot of you that are reading this have signed the petition. We hit almost 4000 signatures over the course of 4 days. Each and every one of you that signed the petition played a role in this. Each and every signature only made our voice stronger and stronger.
Click to expand...
Click to collapse
About the drivers:
This release contains the user-mode driver binaries for Qualcomm's Adreno 2xx GPU on Google Android Ice Cream Sandwich for ARMv6 based chipsets. It has been tested with the CAF release M8960AAAAANLYA1030. Supports any Adreno 2xx GPU on Android ICS using the ARMv6 chipset (7x27). Google's libRS (LLVM) does not currently support ARMv6.
Click to expand...
Click to collapse
[PLEASE READ]"Petition" Qualcomm for ICS Drivers Compiled for ARMv6? I think it is time to change the title of the thread
History of thread:
Hey guys! As many of us know, Qualcomm released Adreno 2xx drivers for ICS. However, these drivers are compiled for ARMv7. Many of us have phones that use ARMv6, so these drivers are pretty much useless for us. So I decided to contact Qualcomm regarding this issue:
I would like to thank you guys for releasing the drivers for Ice Cream Sandwich. It really means a lot as it shows your support for the developer community. However, many of us were quick to find out that these drivers have been compiled for ARMv7. Although ARMv6 may be a thing of the past (or at least becoming quickly outdated), there is still quite a number of us that still have phones that use ARMv6, myself included.
There are many developers that are trying to port Ice Cream Sandwich to a good number of devices. For the devices that use ARMv7, true hardware acceleration is now possible thanks to your drivers. But for the devices that use ARMv6, true hardware acceleration is not possible without your help. Most, if not all, ARMv6 devices that I am aware of use hacks to bring hardware acceleration. Although I am not a developer, I am sure these "hacks" are nothing compared to what your drivers (for ARMv6) may bring.
As big as the developer community is, there are a lot of things that we cannot do without your help. Only Qualcomm can release Adreno 2xx drivers compiled for ARMv6. Other than that, there is not much we can do. Yes, there are still hacks, but between these hacks and your drivers, I'm sure the developer community would choose your drivers. While you may wonder why you should still support an old processor, our Adreno GPUs have a lot of potential, and releasing the drivers for ARMv6 will only prove just that. Please consider this request on behalf of many ARMv6 users.
Click to expand...
Click to collapse
Change of plans: At first I thought contacting them using the "Contact Us" form would be the right method, but it turns out that it wasn't:
myopicrhino said:
Hey people,
I appreciate your enthusiasm, but please don't use the Contact Us form for this. That just generates an email to a handful of us, none of whom have the power to make this happen. I have forwarded on the request to the appropriate people, and any further requests are not going to speed the process along, or make it more likely that we'll do it.
In general, the best method to request things is in the developer forums. Those posts are seen by a much wider audience, and are actively tracked.
Thanks!
Click to expand...
Click to collapse
It is recommended that we use the developer forums and post there. Here are the links to the forums regarding this issue:
https://developer.qualcomm.com/forum/qdevnet-forums/mobile-gaming-graphics-optimization-adreno/8081
https://developer.qualcomm.com/forum/qdevnet-forums/mobile-gaming-graphics-optimization-adreno/10412
Maybe with enough people contacting them, Qualcomm will consider releasing drivers for ARMv6
If you guys can, can you submit this thread as a news tip? Also, in your phone's forum, can you post a link to this thread in any of your ICS-related threads? I would like as much people as possible to see this and contact Qualcomm.
I am sure there is a lot more than just this, but here is a list of phones that I believe should be concerned with this issue (this has been brought to the attention of the phones that are in bold). I will continue to spread the word to more forums until I run out of forums to post in or until I get banned for spamming the same message everywhere (got an infraction for doing so ):
HTC Aria
HTC Nexus One
HTC Wildfire S
LG GT540 Optimus
LG Optimus One/T
LG Optimus V
Samsung Galaxy Ace
Samsung Galaxy Fit
Samsung Galaxy Gio
Samsung Galaxy Mini
Sony Ericsson XPERIA X8
Sony Ericsson XPERIA X10 Mini
Sony Ericsson XPERIA X10 Mini Pro
ZTE Blade
I just send my request Looking for reply on my gmail
Yes, I'm going to contact them!
I have sent my short request too
Thanks so much for releasing Adreno 2xx drivers compiled for ARMv7, but there is a big community over here using devices which have ARMv6. Its true that normally latest technologies are first to be served but we have developers working hard to port ICS to ARMv6 devices like LG P500.
Kindly support us in this case.
Click to expand...
Click to collapse
I sent too.
Sent hope they will respond back
sent, hope they will hear us as they did when asking for ICS drivers
I've also sent. Lets keep sending requests and hope for the best.
I sent one too.
Me too
Hope they reply
Hope they consider our requeast.
Sent from something, I don't remember it...
If you guys can, can you submit this thread as a news tip? Also, in your phone's forum, can you post a link to this thread in any of your ICS-related threads? I would like as much people as possible to see this and contact Qualcomm.
Thank you for submiting your question.
sent
hope they'll consider it
omg got this in reply from them.
Okay, very clearly, someone made a post somewhere encouraging people to use the Contact Us form on developer.qualcomm.com, since I've been getting dozens of nearly identical messages. This is absolutely not the correct way to bring attention to this. Can you direct me to the post in question so I can respond? Thanks ________________________________________ From: [email protected] [[email protected]] Sent: Sunday, March 18, 2012 12:17 AM To: qdn.adreno.questions Subject: Form submission from: Contact Us
Hey people,
I appreciate your enthusiasm, but please don't use the Contact Us form for this. That just generates an email to a handful of us, none of whom have the power to make this happen. I have forwarded on the request to the appropriate people, and any further requests are not going to speed the process along, or make it more likely that we'll do it.
In general, the best method to request things is in the developer forums. Those posts are seen by a much wider audience, and are actively tracked.
Thanks!
myopicrhino said:
Hey people,
I appreciate your enthusiasm, but please don't use the Contact Us form for this. That just generates an email to a handful of us, none of whom have the power to make this happen. I have forwarded on the request to the appropriate people, and any further requests are not going to speed the process along, or make it more likely that we'll do it.
In general, the best method to request things is in the developer forums. Those posts are seen by a much wider audience, and are actively tracked.
Thanks!
Click to expand...
Click to collapse
Of course, we wrote on this forum https://developer.qualcomm.com/foru...ming-graphics-optimization-adreno/8081?page=3. But no reply.
Sent! well hopefully
Posted on ZTE Blade forum
did it before I even found this thread

Is the T-Mobile Dev section Required?

Why has the ''is this necessary'' thread been deleted ? and the other one locked ?
There was more people against this opening of a sub-forum than there was for it.
Please listen to us and remove this tmobile section, It isnt needed, and deleting the threads that wanted this section gone is way out of order.. We didnt break any rules..
This is our section, our phone, We dont need nor want this silly tmobile section.. So please remove it !!
If you think im wrong............Im not, Allow me to open a poll as to whether we should keep it or not ??
c'mon mods be fair ??!!??!!
It got removed because it would just start issues with other members of the forum for people who want it or not same thing with this thread.
This is the wrong section your posting in anyway.
What's so hard about looking in other section and looking in T-Mobile section.
The administrators on the site said they want it as a local moderator just spoke to them about it, Majority want it anyway.
well the poll says different... At least leave this thread for a few days and get some statistics before making a decision.
--
To be fair i agree with azzle here,bit stupid to have some extra thread for tmobile..end of the day this can all be kept in the android dev section. This is daft.
suprised the mod agreed to this anyway,unless he was pm'ed by everyone asking for it,now if thats the case..then fair enough
OK people, i have re-named this thread and moved it to its proper section. I will allow this to continue, unless it turns into a flame war. We all have opinions, i ask you to respect others.
The extra dev section was asked for, and the admin gave it. Its unlikely its going to be removed, so we will have to live with it.
cheers man ! If its what the people want.. Keep it.. I just think its gunna cause so much confusion when development really gets going.. That things would have been better left how they were..
Im all up for the Q&A Section... If there happens to be differences between Tmobile and International version, I will add it to my threads FAQ section...
Reviewers said:
What's so hard about looking in other section and looking in T-Mobile section.
Click to expand...
Click to collapse
Whats so hard of not having that section and making double download links (as rom makers will make 2 different versions anyway).
Let the vote stay here for atleast 2 days, then you can see some "results"
Reviewers said:
It got removed because it would just start issues with other members of the forum for people who want it or not same thing with this thread.
This is the wrong section your posting in anyway.
What's so hard about looking in other section and looking in T-Mobile section.
The administrators on the site said they want it as a local moderator just spoke to them about it, Majority want it anyway.
Click to expand...
Click to collapse
The point is, we have so little development as it is, that splitting the forum into two makes it look like we have even less development, and that could deter people away from the phone and thus more development. Both phones can use both roms so there is no point. If there are small issues such as wifi, we can have stickies.
joshnichols189 said:
The point is, we have so little development as it is, that splitting the forum into two makes it look like we have even less development, and that could deter people away from the phone and thus more development. Both phones can use both roms so there is no point. If there are small issues such as wifi, we can have stickies.
Click to expand...
Click to collapse
True I'm not going to argue with that cause ur right.
but It's not hard looking in both sections.
If there are incompatible features between t-mo-us and the international One S, keep them both, if not, merge them. Or at least rename it t-mo US, as t-mo has presence in other countries as well.
The second tmous thread is not needed, if the dev of the rom would simply add to there title.
[rom][sense 4.0] [tmous/EU] [NAME OF YOUR ROM][ANYTHING EXTRA AOSP/STOCK] [Updated XX/XX/XXXX]
Reviewers said:
True I'm not going to argue with that cause ur right.
but It's not hard looking in both sections.
Click to expand...
Click to collapse
I'm not saying it is, and I usually ventured to the Verizon side when I had a GSM Galaxy Nexus I just don't want development on this device stunted.
Sent from my HTC VLE_U using xda premium
I am going to request another subforum for my own gsm operator. Or maybe even forum for my own mobile :what:
Seriously, this is ridiculous.
Sent from my HTC One S using xda premium
Agreed josh. I was told by senior mods that they did it because "it's what users wanted". Well, that's kind of interesting, because we're NOT wanting it, and we're those users. The initial confusion came on launch day, and that was because nobody was familiar with whether the devices differed. Guides simply need to be updated to reflect compatibility. Now, instead, we've got 2 forums, and in an attempt to alleviate the confusion, they have only caused further confusion, because now it REALLY looks like the devices are different when they are in fact NOT.
When a dev gets into modding, one of the obvious questions is "How many different devices do I have to work with here?". Based off our forum layout, it looks like we've got 2 different devices. This could lead developers to believe that there's more work to be done than necessary to achieve compatibility with both.
ndsvic suidas
I am on the fence with this one.
While I agree that if a rom developed for EU works - for the majority - and only does not function on a scale that reaches very select users, then the dual dev section is not needed.
However, in that same logic, if a rom developed that is incompatible with the counterpart phones due to whatever reason, and something happens while it was not labeled as EU/US or TMOUS or whatever tag a dev would use, then that would start a stir in the forum, IMO, deterring users from moving to this phone and potentially hurting development.
While i agree that it should be SOP to label the rom as EU or US, at the very least posting inside the thread if its for EU or US in the download links. Having a split forum this early in the development phase could hurt the growth of the phone's custom roms.
This being my second android phone, I myself am considering taking a shot at developing a custom TMOUS minimalist rom. (running as little as possible and having the bare necessities required to run the phone) Thinking of a battery saver galore build, completely Sense Free.
I came from the Nexus S, and the dev forum was split into 2 forums - 1 for the GSM Nexus S, and 1 for the CDMA Sprint Nexus S 4G.
I was a i9020T GSM model. In the very same forum, mods and devs posted ROMs for i9020T, i9020A (att), and i9023 (SLCD model , mostly overseas). Not once was there ever a problem. I just think it's kind of silly that we're being told "it's what users want", and yet we clearly don't want it, atleast the majority don't. I was told it was to help with new users, but here's the thing....this isnt newbforums.com or something. This is XDA DEVELOPERS. Enthusiasts and the tech crowd come here. I'm not saying new users don't, because we see them every day, but they've got their own issue with getting up-to-speed, and I fail to see how fragmenting the community into 2 dev forums helps alleviate the issue. Newbs will be newbs. They just have to read stuff....
Is it possible that I can agree with everyone? Probably a result of my incessant blind optimism.
Clearly, there is a divide here. Some people want the separate forum, others don't. Both arguments seem to stem from the same desire... to maximize development for their specific phones. I emphasize like crazy with you.
People that don't want the split fear that this will slow development by dividing troops and possibly give the appearance of a lesser interest from the dev community. However, having two sides essentially working on the "same" device may even prove beneficial in the end.
People that do want it are likely "we" Americans who always fear upon a devices release that there will be some minor radio variance that will cause our new, $600 baby to turn paperweight. Having a T-Mo(US) thread gives someone like me, with a lesser experience in the dev world, more confidence to take the leap into modding a device. I'm more likely to set up a dev environment, root my phone, and become more active in the community. The more people willing to get their feet wet should help everyone, regardless of continent, in the end.
Lastly, the apparent lack of interest may instead be a lack of knowledge. What other snapdragon S4 Krait phones have been released? AFAIK, there hasn't been a single device dropped with this chip, so development will be decidedly difficult until HTC makes available their GPL code. They probably aren't terribly eager to give other phone manufacturers the fruits of their labor, and money, by aiding them prep the S4 phones/tablets that will inevitably follow.
I am incredibly eager to sink my teeth into the underbelly of the one S. I can accept that for the time being, customization may likely be limited to sense-based mods, as I for one am certainly unwilling to part with what is one of the most impressive cameras ever released on a phone. But I do incredibly miss my notification pull down power switches.
majalo said:
Is it possible that I can agree with everyone? Probably a result of my incessant blind optimism.
Clearly, there is a divide here. Some people want the separate forum, others don't. Both arguments seem to stem from the same desire... to maximize development for their specific phones. I emphasize like crazy with you.
People that don't want the split fear that this will slow development by dividing troops and possibly give the appearance of a lesser interest from the dev community. However, having two sides essentially working on the "same" device may even prove beneficial in the end.
People that do want it are likely "we" Americans who always fear upon a devices release that there will be some minor radio variance that will cause our new, $600 baby to turn paperweight. Having a T-Mo(US) thread gives someone like me, with a lesser experience in the dev world, more confidence to take the leap into modding a device. I'm more likely to set up a dev environment, root my phone, and become more active in the community. The more people willing to get their feet wet should help everyone, regardless of continent, in the end.
Lastly, the apparent lack of interest may instead be a lack of knowledge. What other snapdragon S4 Krait phones have been released? AFAIK, there hasn't been a single device dropped with this chip, so development will be decidedly difficult until HTC makes available their GPL code. They probably aren't terribly eager to give other phone manufacturers the fruits of their labor, and money, by aiding them prep the S4 phones/tablets that will inevitably follow.
I am incredibly eager to sink my teeth into the underbelly of the one S. I can accept that for the time being, customization may likely be limited to sense-based mods, as I for one am certainly unwilling to part with what is one of the most impressive cameras ever released on a phone. But I do incredibly miss my notification pull down power switches.
Click to expand...
Click to collapse
I respect your opinion. Please email HTCdev and express your displeasure at their daily willful GPL violations. That code lawfully belongs in the hands of the open source community.
edited.
See, what we're trying to get at is that there isn't any "flash this version or that version", because there's only 1 version: the HTC One S. Unless you're flashing radios, and custom ROMs should typically NEVER have custom radios unless clearly indicated, then it doesn't matter.
And the Galaxy S was divided into subforums because the actual hardware cofigurations, button layouts, chips, etc, varied quite a bit from model to model, whether it was the international SGS, the T-Mo Vibrant, The Verizon Continuum (vastly different), or the ATT version.
The One S is a single phone, with 2 slightly different radio versions. Other than that radio, they are absolutely identical.

Petition to Qualcomm to continue Snapdragon S3 support

Dear villec2 fellow users,
I have just come across a thread from HTC EVO 3D forum calling poor folks like us out there who are stuck with no more updates to sign a petition to Qualcomm.
Apparently due to the lack of driver support from Qualcomm, HTC has been unable to push further updates to our phones. I also think that it is such a shame when we have a relatively new device with remarkable performance but receives no support.
So here's the link: https://www.change.org/petitions/qualcomm-mobile-and-computing-qmc-qualcomm-decided-to-stop-any-further-snapdragon-s3-chipset-support-development-and-not-to-make-kernel-updates-to-provide-compability-for-android-4-2-2-and-newer
Please feel free to sign and share with others, the petition will be sent to Qualcomm and other Android Portals. I do hope that we can make a change . Thanks
Already signed, but I doubt 1k people are enough...
http://forum.xda-developers.com/showthread.php?t=2440548
Thread closed
Not only is there already such a post. (see post above)
Also it has really NO business in development section.

Categories

Resources