Related
I had always thought that I897 was captivate, and I9000 was all other Galaxy S phones. But I have a captivate that lists its "model number" as GT-I9000, and see here that captivate users are installing I9000 ROMs. Am I wrong about the difference?
Not development.
Captivate = i897
Galaxy S = i9000
Sent from my Captivate using XDA Premium.
QuarkGluonSoup said:
I had always thought that I897 was captivate, and I9000 was all other Galaxy S phones. But I have a captivate that lists its "model number" as GT-I9000, and see here that captivate users are installing I9000 ROMs. Am I wrong about the difference?
Click to expand...
Click to collapse
as mikey said, this isn't development related.
you are merely installing i9000 ROM's with reoriented kernels.
/thread
Kaik541 said:
as mikey said, this isn't development related.
you are merely installing i9000 ROM's with reoriented kernels.
/thread
Click to expand...
Click to collapse
As they both said - what part of development does this fall under?!
I've noticed something around here at XDA that is really kind of odd to me. Whenever a new guy comes here and posts a thread not knowing that it isn't the right thread to post on. There's always the "too cool" attitude thrown out by a few. I know that XDA is here to help others and think that maybe instead of posting smartass replies that maybe an answer to the question and a point in the right direction would be the best thing to help a noob out. I've learned more from the great guys here at XDA (ADAMHOLDEN85, MIKEYMIKE01, KIZZMIAZZ, ZELENDEL, EXTREMEKILLA09, TSACHI) from their positive attitudes and direction than I've learned from any other forum. Keep it welcome here guys.
task650 said:
I've noticed something around here at XDA that is really kind of odd to me. Whenever a new guy comes here and posts a thread not knowing that it isn't the right thread to post on. There's always the "too cool" attitude thrown out by a few. I know that XDA is here to help others and think that maybe instead of posting smartass replies that maybe an answer to the question and a point in the right direction would be the best thing to help a noob out. I've learned more from the great guys here at XDA (ADAMHOLDEN85, MIKEYMIKE01, KIZZMIAZZ, ZELENDEL, EXTREMEKILLA09, TSACHI) from their positive attitudes and direction than I've learned from any other forum. Keep it welcome here guys.
Click to expand...
Click to collapse
^ Amen to that!
yeah, for real, it only takes one guy to correct the miss placed thread and a mod to move it. and you can correct a person and be helpful at the same time.
to the op, if the captivate is saying gt -i9000 on a splash screen on startup or on your computer when plugged in to usb then it is a modded i9000 kernel installed, this is very common because the source code for the i9000 was realeased long before the captivate and things like overclock and color fixes could be baked in. a lack of source on the captivate meant that either you ran 2.1, ran 2.2 basically stock or you used an i9000 kernel to get all the good stuff. if it says i9000 in about phone or in apps then you have an i9000 rom and the build.prop was not changed.
to be clear the att captivate is the i897, the armani is the i9010 the rogers is the i896 and the chinese version is the i9088. the i897 and i896 are identical aside from the rom, the armani has a different battery door and maybe darker plastic, i haven't seen one up close. the chinese version may have other difference like less ram.
the i9000 is sold in many countries and is the real galaxy s. it has a forward facing camera. it is sold in many countries and has several versions including the i9000m and i9000b, the b has an antenna to pickup live digital hd tv and is sold in brazil
the i500 is the fascinate and the mezmerize in the us and is cdma.
the t959 is the vibrant in the us and the t959d is the facinate in canada. these are the closest relatives to the captivates but look more like a i9000.
then there is the epic, i dont remember the model of it but it has a forward facing camera and a slide out keyboard. it is cdma and i think do to the stock software, that it is an epic piece of crap!
there are others now such as the nexus s i9020 which is a google dev phone and has aosp gingerbread, and the indulge which isn't quite a galaxy s but does have the hummingbird chip and adds a keyboard and lte data network
Couldn't have said it better. The same reason why I waited so long to push into the custom side. Sick of the attitude on here(for the most part). Am I new to android or XDA for that matter? Maybe. But I am not stupid and I don't deserve to be treated like I am. Anyways...
Longer story short...I resorted to learning by a q&a session with one of the nicer devs. And by the end of a couple pm's back and forth, I was flashing my first rom with no problems.
A little kindness can go a long way people..
I agree. Calm down folks. Everyone makes mistakes especially whe they are new to something. I'm new to and posted a few questions in the Q&A section but some people act totally anal in response there. Need more people like the nice dev's who are patient and calm with their users.
Wheres the moral fiber thread?
Dani897 said:
yeah, for real, it only takes one guy to correct the miss placed thread and a mod to move it. and you can correct a person and be helpful at the same time.
to the op, if the captivate is saying gt -i9000 on a splash screen on startup or on your computer when plugged in to usb then it is a modded i9000 kernel installed, this is very common because the source code for the i9000 was realeased long before the captivate and things like overclock and color fixes could be baked in. a lack of source on the captivate meant that either you ran 2.1, ran 2.2 basically stock or you used an i9000 kernel to get all the good stuff. if it says i9000 in about phone or in apps then you have an i9000 rom and the build.prop was not changed.
to be clear the att captivate is the i897, the armani is the i9010 the rogers is the i896 and the chinese version is the i9088. the i897 and i896 are identical aside from the rom, the armani has a different battery door and maybe darker plastic, i haven't seen one up close. the chinese version may have other difference like less ram.
the i9000 is sold in many countries and is the real galaxy s. it has a forward facing camera. it is sold in many countries and has several versions including the i9000m and i9000b, the b has an antenna to pickup live digital hd tv and is sold in brazil
the i500 is the fascinate and the mezmerize in the us and is cdma.
the t959 is the vibrant in the us and the t959d is the facinate in canada. these are the closest relatives to the captivates but look more like a i9000.
then there is the epic, i dont remember the model of it but it has a forward facing camera and a slide out keyboard. it is cdma and i think do to the stock software, that it is an epic piece of crap!
there are others now such as the nexus s i9020 which is a google dev phone and has aosp gingerbread, and the indulge which isn't quite a galaxy s but does have the hummingbird chip and adds a keyboard and lte data network
Click to expand...
Click to collapse
Isn't the Nexus S actually made by Samsung,too?
Sent from a place my wife doesn't know about
task650 said:
I've noticed something around here at XDA that is really kind of odd to me. Whenever a new guy comes here and posts a thread not knowing that it isn't the right thread to post on. There's always the "too cool" attitude thrown out by a few. I know that XDA is here to help others and think that maybe instead of posting smartass replies that maybe an answer to the question and a point in the right direction would be the best thing to help a noob out. I've learned more from the great guys here at XDA (ADAMHOLDEN85, MIKEYMIKE01, KIZZMIAZZ, ZELENDEL, EXTREMEKILLA09, TSACHI) from their positive attitudes and direction than I've learned from any other forum. Keep it welcome here guys.
Click to expand...
Click to collapse
Couldn't have said it better myself!
I can't seem to find a good post or thread about this so I'll be the one to ask the dumbest question.
Can a GSM rom be flashed to a CDMA tab? Other than networking issue with the modem, will phone actually boot and be usable on wifi? I'm assuming it most likely will either not work at all or just FC constantly but wanted to ask first.
MODS please delete after a few answers. I don't want to waste thread space...
Anybody has flashed this before ? And i don't know can Verizon tab be able to flash rom for Sprint Tab ?
Waiting for anwser too .
Sent from my SCH-I800
connexion2005 said:
I can't seem to find a good post or thread about this so I'll be the one to ask the dumbest question.
Can a GSM rom be flashed to a CDMA tab? Other than networking issue with the modem, will phone actually boot and be usable on wifi? I'm assuming it most likely will either not work at all or just FC constantly but wanted to ask first.
MODS please delete after a few answers. I don't want to waste thread space...
Click to expand...
Click to collapse
One of the other members did and it worked, I am not sure what was FC'ing but he was using it that way. A word of WARNING, if you accidentally flash the modem with the GSM one, its dead forever! You cannot restore it!!
But yeah it should boot, and be able to use WiFi.
lhttan said:
Anybody has flashed this before ? And i don't know can Verizon tab be able to flash rom for Sprint Tab ?
Waiting for anwser too .
Sent from my SCH-I800
Click to expand...
Click to collapse
Verizon and Sprint use the same radio's so this should not be an issue
OK second question. Where on earth can I find the VZW firmware files to use with Odin or Heimdall? I flashed the Klean ROM and like it but then I realized I was having problems finding the stock pit and pda files to revert back to stock if needed!
I would love if I could use GSM ROM's. I bought a Verizon TAB (mistake now that I realized this) and just use it for WIFI only so network access is not an issue for me.
Is that file you need ?
lhttan said:
Is that file you need ?
Click to expand...
Click to collapse
Downloading now but I'm pretty sure thats it! You are awesome. And I'm a lazy searcher.
try this... its the vzw recovery package i use... unrar and bring it into hiemdall... try using the voodoo overclocked kernal with it... great improvements, blazing fast, and the sound is unmatched... im not sure why, and i could very well be doing it wrong... but when i flash the zImage for the kernal, i always have to flash that zImage into the recovery as well... like i said idk why but 90% of the time my flash will fail unless i do that... so if you have any problems try it... hope this helps!
http://www.megaupload.com/?d=TC4G5IYC
probably the same files... beat me to it haha
I'd actually really like to know this as well... I've got a VZW tab I was given from a friend who updated to a Xoom... I'm only ever gonna use it wifi, and am a bit disappointed in the lack of roms for CDMA tabs... if a GSM Rom would work, and let me use wifi, that would be great for folks like me.
How can I avoid to flash the modem with the GSM one ? I usally use heimdall-frontend.exe to flash !
I could be wrong, but if you go through frontend dont you have to manually palce the moden file into the slot for modem? couldnt you just flash everything but modem? or is it in the kernal as well??
Soft
Brick.
arariel said:
I'd actually really like to know this as well... I've got a VZW tab I was given from a friend who updated to a Xoom... I'm only ever gonna use it wifi, and am a bit disappointed in the lack of roms for CDMA tabs... if a GSM Rom would work, and let me use wifi, that would be great for folks like me.
Click to expand...
Click to collapse
You could always contribute instead of just ***** about the lack of support. You got a free Tab for pete's sake....
Boushh said:
Soft
Brick.
You could always contribute instead of just ***** about the lack of support. You got a free Tab for pete's sake....
Click to expand...
Click to collapse
Wow, ok... I just got the damn thing, let me, you know, learn how to code and program etc... got a while?
Yeah, I got a free tab, and I know next to nothing about it, so I'm trying to find out some information. I dunno that I would call expressing mild disappointment really classifies as "*****ing" but, hey, thanks for YOUR contribution to the thread too, guy. Super helpful. I understand the VZW tab isn't nearly as popular, and that means less people working on it, or maybe there are technical difficulties or something. I have no idea. I just know there is less information, etc. out there about it, and that's disappointing. Nowhere did I say anything like "people here suck for not supporting my device!" The ROM makers here are a talented bunch, that much is obvious... I really like what they're doing, and I'm guessing so does the OP. That's why we're asking about GSM roms... we obviously liked something someone made, and wish we could use it on our device. We're trying to find information, and you come and attack someone with the equivalent of an ER nurse getting mad at a Vet for coming in with a question about their daughter, and demanding that they help treat her themselves.
If I had ANYTHING even CLOSE to as helpful as some of the people here to contribute right now, I would... but I don't... I'm just trying to learn about this device. At my level of knowledge right now, I don't HAVE anything to give. So very sorry if that somehow offends you personally.
That was ugly!
Boushh said:
Soft
Brick.
You could always contribute instead of just ***** about the lack of support. You got a free Tab for pete's sake....
Click to expand...
Click to collapse
Hmm. I wonder what my PM reply from you will have to say in it lol. Anyhow, is a soft brick inevitable? Are there options I can avoid such as obviously not flashing the modem? Or param.lfs? To prevent a soft brick. One person claims it worked on a certain ROM from them. I know I can find out the hard way myself but if I can benefit from someone else's experience I'd like to see if I can do that first.
connexion2005 said:
Hmm. I wonder what my PM reply from you will have to say in it lol. Anyhow, is a soft brick inevitable? Are there options I can avoid such as obviously not flashing the modem? Or param.lfs? To prevent a soft brick. One person claims it worked on a certain ROM from them. I know I can find out the hard way myself but if I can benefit from someone else's experience I'd like to see if I can do that first.
Click to expand...
Click to collapse
Think about it guys you've got devs, and then you have those of us who are just using what the devs design, be it lack of knowledge or lack of effort, either way if you have a free tab, make a backup, make a couple backups, and try it, or maybe get with a dev working on your tab to add the features of the gsm tab to our vzw tab. help them test it, It makes sense that devs get pissed when someone says i got a free tab, do some research, make some effort to further the development for a device in which the devs purchase in most cases with they're own money, and if they brick it in the process they are out alot more money then you are. and the way they save them selves is by again treading on undiscovered territory. So instead of asking make some attempt. learn to use the emulator, learn your device, if you are just getting to know the device then it may not be a good idea to jump right into rooting, and flashing roms....
matthewflinchbaugh said:
Think about it guys you've got devs, and then you have those of us who are just using what the devs design, be it lack of knowledge or lack of effort, either way if you have a free tab, make a backup, make a couple backups, and try it, or maybe get with a dev working on your tab to add the features of the gsm tab to our vzw tab. help them test it, It makes sense that devs get pissed when someone says i got a free tab, do some research, make some effort to further the development for a device in which the devs purchase in most cases with they're own money, and if they brick it in the process they are out alot more money then you are. and the way they save them selves is by again treading on undiscovered territory. So instead of asking make some attempt. learn to use the emulator, learn your device, if you are just getting to know the device then it may not be a good idea to jump right into rooting, and flashing roms....
Click to expand...
Click to collapse
Good post. Hope you weren't referring to me though! Check my sig I've been around the block with Android.
Oh and I'm running Overcome ROM right now on my VZW TAB. I'll be posting a video of the steps to take to ensure this works correctly some time this weekend.
Looks like my VZW may work out afterall...
arariel said:
Wow, ok... I just got the damn thing, let me, you know, learn how to code and program etc... got a while?
Yeah, I got a free tab, and I know next to nothing about it, so I'm trying to find out some information. I dunno that I would call expressing mild disappointment really classifies as "*****ing" but, hey, thanks for YOUR contribution to the thread too, guy. Super helpful. I understand the VZW tab isn't nearly as popular, and that means less people working on it, or maybe there are technical difficulties or something. I have no idea. I just know there is less information, etc. out there about it, and that's disappointing. Nowhere did I say anything like "people here suck for not supporting my device!" The ROM makers here are a talented bunch, that much is obvious... I really like what they're doing, and I'm guessing so does the OP. That's why we're asking about GSM roms... we obviously liked something someone made, and wish we could use it on our device. We're trying to find information, and you come and attack someone with the equivalent of an ER nurse getting mad at a Vet for coming in with a question about their daughter, and demanding that they help treat her themselves.
If I had ANYTHING even CLOSE to as helpful as some of the people here to contribute right now, I would... but I don't... I'm just trying to learn about this device. At my level of knowledge right now, I don't HAVE anything to give. So very sorry if that somehow offends you personally.
Click to expand...
Click to collapse
LOL You just had a *****fit with the best CDMA dev we have, nice work.
How did you do it?
Hey man, watched your video review great stuff, any update date on how you got the rom on your CDMA Tab however? I just got a Sprint Tab and would love to flash Overcome on it...thanks for any advice
connexion2005 said:
Good post. Hope you weren't referring to me though! Check my sig I've been around the block with Android.
Oh and I'm running Overcome ROM right now on my VZW TAB. I'll be posting a video of the steps to take to ensure this works correctly some time this weekend.
Looks like my VZW may work out afterall...
Click to expand...
Click to collapse
connexion2005 said:
Good post. Hope you weren't referring to me though! Check my sig I've been around the block with Android.
Oh and I'm running Overcome ROM right now on my VZW TAB. I'll be posting a video of the steps to take to ensure this works correctly some time this weekend.
Looks like my VZW may work out afterall...
Click to expand...
Click to collapse
hey connexion2005, any update on the video? i´ve been surfing around the forums for a couple of hours now and haven´t found any procedures on how to get overcome on the VZW tab. just wondering
I dont think this will become the official thread for what we're trying to do but more of a gathering of the info to then compile.
My buddy YACO and I are trying to create a excel spreadsheet with all the files that need to be changed, swapped or removed for anyone that wants to take a world version (GSM) to Sprint.
If anyone has any first hand experience with the difference or has even read about some of the things that are different please share...even if you think it's extremely obvious share the difference so we can begin compiling EVERYTHING. Hopefully this will result in some scripts or automation of sorts to help speed up the developments and conversions from the more heavily developed world/uk/gsm versions.
Thanks everyone!
Tyzing said:
I dont think this will become the official thread for what we're trying to do but more of a gathering of the info to then compile.
My buddy YACO and I are trying to create a excel spreadsheet with all the files that need to be changed, swapped or removed for anyone that wants to take a world version (GSM) to Sprint.
If anyone has any first hand experience with the difference or has even read about some of the things that are different please share...even if you think it's extremely obvious share the difference so we can begin compiling EVERYTHING. Hopefully this will result in some scripts or automation of sorts to help speed up the developments and conversions from the more heavily developed world/uk/gsm versions.
Thanks everyone!
Click to expand...
Click to collapse
Can't be done. World phone has the MDM9215 which doesn't have CDMA support. Sprint has the MDM9615
dbman190 said:
Can't be done. World phone has the MDM9215 which doesn't have CDMA support. Sprint has the MDM9615
Click to expand...
Click to collapse
Well, we've gotten the the world version to boot already, data is transferring everything is working. Few things left to work out like the phone FC'ing
It obviously can be done, just have to make sure to swap out the correct files
I think your initial post was slightly confusing. I understood it to be that you wanted to compile a list of differences between phones so you could bring the physical phone itself to sprint which is not physically possible.
If you're trying to port the gsm ROMs over to the sprint version that's a totally different story. . I applaud your efforts and say HELL YES!!!
This makes me happy. I can't wait to be flashing some new roms.
Sent from my HTCONE
kmyerslp said:
This makes me happy. I can't wait to be flashing some new roms.
Sent from my HTCONE
Click to expand...
Click to collapse
Ha, yes...my OP was confusing...but this is what I meant...and I think its a very big positive for the Sprint community.
Just an update: http://forum.xda-developers.com/showthread.php?t=2267057
This is a discussion thread for all things custom; Building steps and tips, problem solving and issue discussion. All questions and/or comments are welcome. Be aware, although I build and customize ROMs, I am not a professional developer and cannot promise a solution for your problem. But, hopefully, we can work together to come up with practical solutions for any problems here at m7spr.
So..The things you were shut down on. Were they CM related, or Sense stuff?
Did they involve you working solo, or with a team? Give more details, get the word out.
Felnarion said:
So..The things you were shut down on. Were they CM related, or Sense stuff?
Did they involve you working solo, or with a team? Give more details, get the word out.
Click to expand...
Click to collapse
I really am leery of pointing fingers at specific people because I'm new here and don't want to make a name for myself as a whiner. But, basically it is both. The custom ROMs I am working on have all been built before by me on other devices, so that's not the issue. I have inquired about possibly collaborating with other devs on some Sense related stuff and was looking into why there was no official or unofficial release of the current CM10.2. The sense stuff really isn't my bag as much, but i was/am interested. Others are working on the CM, but with no official release in play, no one wants to put theirs out. I have built it successfully, but have no intention of trying to lay it out there when other devs have been working on it before I got here. My thing is this: when I got tired of waiting for devs to come up with new things, I was told to put up or shut up. It was good advice; I have no coding experience specifically, but I like to learn and have been successful at not only compiling and maintaining custom builds, but also starting 'Learn to do it yourself' threads in two different device forums. I like to learn and compile and share. That's it. I don't need (or want) attention or grateful fans or any of that crap. All I want to do is open the doors for more builds and more users getting off their asses and building for themselves. It seems like a win-win to me, but I feel resistance and it is disappointing. I will get off my soapbox now
I typically touch base with any dev who is the creator/maintainer of any ROM I am interested in pursuing. My experience has been more of a quick 'try it out and see what you get' response or 'it can't be done'. This is after I have asked for not only a blessing, but for relevant information and possibly assistance. Maybe I am just hitting up devs who are already frustrated and don't want someone like me asking a bunch of questions, I don't know....
BMP7777 said:
I really am leery of pointing fingers at specific people because I'm new here and don't want to make a name for myself as a whiner. But, basically it is both. The custom ROMs I am working on have all been built before by me on other devices, so that's not the issue. I have inquired about possibly collaborating with other devs on some Sense related stuff and was looking into why there was no official or unofficial release of the current CM10.2. The sense stuff really isn't my bag as much, but i was/am interested. Others are working on the CM, but with no official release in play, no one wants to put theirs out. I have built it successfully, but have no intention of trying to lay it out there when other devs have been working on it before I got here. My thing is this: when I got tired of waiting for devs to come up with new things, I was told to put up or shut up. It was good advice; I have no coding experience specifically, but I like to learn and have been successful at not only compiling and maintaining custom builds, but also starting 'Learn to do it yourself' threads in two different device forums. I like to learn and compile and share. That's it. I don't need (or want) attention or grateful fans or any of that crap. All I want to do is open the doors for more builds and more users getting off their asses and building for themselves. It seems like a win-win to me, but I feel resistance and it is disappointing. I will get off my soapbox now
I typically touch base with any dev who is the creator/maintainer of any ROM I am interested in pursuing. My experience has been more of a quick 'try it out and see what you get' response or 'it can't be done'. This is after I have asked for not only a blessing, but for relevant information and possibly assistance. Maybe I am just hitting up devs who are already frustrated and don't want someone like me asking a bunch of questions, I don't know....
Click to expand...
Click to collapse
you can start by helping to get things working in sense 4.2.2 beta rom
flex360 said:
you can start by helping to get things working in sense 4.2.2 beta rom
Click to expand...
Click to collapse
I looked your thread up and I think we'd get along great. Anybody who says 'if you don't like me, GOOD' is someone I wanna hang with. It's also funny you should mention helping with that sense version because that's exactly what I was trying to do. Sense aint even my bag, but I was going to look into it from the SVD side to see what I could learn. Maybe I just rubbed that guy the wrong way or something. Regardless, I can't promise how much help I will actually be, but I'm willing to give it a shot. Tell me what you need and the right places to look and I'll do whatever I can. Be cool
BMP7777 said:
I looked your thread up and I think we'd get along great. Anybody who says 'if you don't like me, GOOD' is someone I wanna hang with. It's also funny you should mention helping with that sense version because that's exactly what I was trying to do. Sense aint even my bag, but I was going to look into it from the SVD side to see what I could learn. Maybe I just rubbed that guy the wrong way or something. Regardless, I can't promise how much help I will actually be, but I'm willing to give it a shot. Tell me what you need and the right places to look and I'll do whatever I can. Be cool
Click to expand...
Click to collapse
do you have google hangout?
I think one issue is that there is an update to 4.3 looking for the Sprint One. This will undoubtely contain new radios and firmware that will help our phones run on 4.3+. Since this is a know update, many devs have decided to forego work on the the current 4.1.2 Sense ROMs. Some are working on the 4.2.2 Sense ROM, but with no leak, or Sprint version it is much harder work. Also, there is only source for up to 1.29. The source from the 1.31 update is not available and it has caused issues with ROMs based on that update.
Personally I don't get your complaint though. There is a lot of development and a wide selection of ROMs available from Stock Android 4.1 to 4.3 to Stock Sense, to heavily themed Sense ROMs. What exactly is not available that you want?
flex360 said:
do you have google hangout?
Click to expand...
Click to collapse
[email protected]
raptoro07 said:
I think one issue is that there is an update to 4.3 looking for the Sprint One. This will undoubtely contain new radios and firmware that will help our phones run on 4.3+. Since this is a know update, many devs have decided to forego work on the the current 4.1.2 Sense ROMs. Some are working on the 4.2.2 Sense ROM, but with no leak, or Sprint version it is much harder work. Also, there is only source for up to 1.29. The source from the 1.31 update is not available and it has caused issues with ROMs based on that update.
Personally I don't get your complaint though. There is a lot of development and a wide selection of ROMs available from Stock Android 4.1 to 4.3 to Stock Sense, to heavily themed Sense ROMs. What exactly is not available that you want?
Click to expand...
Click to collapse
This really wasn't meant to be some complaint thread with a bunch of whining; just the opposite, really. I just wanted feedback on how I am perceiving things around here. I'm cool with being told I have it wrong; was hoping for it actually. And you pointed out exactly what I mean in part. Sense this and stock that is the rule of the day here. That's ok. Everyone is allowed to like whatever they want and if sense and stock are the most wanted builds then so be it. But, I am a self-proclaimed customization junkie, for better or for worse. Personally, I like more fully custom ROM choices and have been beating my head against the wall trying to get some Beanstalk love here but without success to this point. BS is already set in 4.3 and matched with CMs 10.2 releases, so I'm stumped. If you have knowledge, I would be happy to show you some of my errors. I do think you make a great point about the whole place being in flux due to the impending 4.3 release. Like I said before, I just want to open up some development doors and get more interest in development in general. Maybe I have hit up the wrong devs or caught them at bad times. It happens.
BMP7777 said:
[email protected]
This really wasn't meant to be some complaint thread with a bunch of whining; just the opposite, really. I just wanted feedback on how I am perceiving things around here. I'm cool with being told I have it wrong; was hoping for it actually. And you pointed out exactly what I mean in part. Sense this and stock that is the rule of the day here. That's ok. Everyone is allowed to like whatever they want and if sense and stock are the most wanted builds then so be it. But, I am a self-proclaimed customization junkie, for better or for worse. Personally, I like more fully custom ROM choices and have been beating my head against the wall trying to get some Beanstalk love here but without success to this point. BS is already set in 4.3 and matched with CMs 10.2 releases, so I'm stumped. If you have knowledge, I would be happy to show you some of my errors. I do think you make a great point about the whole place being in flux due to the impending 4.3 release. Like I said before, I just want to open up some development doors and get more interest in development in general. Maybe I have hit up the wrong devs or caught them at bad times. It happens.
Click to expand...
Click to collapse
Part of the issue might be that users are afraid of using Cm as it has a nasty habit of bricking phones that no one of notoriety has looked into, acknowledged, or found a solution to.
Kraizk said:
Part of the issue might be that users are afraid of using Cm as it has a nasty habit of bricking phones that no one of notoriety has looked into, acknowledged, or found a solution to.
Click to expand...
Click to collapse
I haven't really been looking at it after my first run (I personally like Sense a lot, and AOSP didn't have a good way of dealing with the limited hardware options for me), but wasn't the brick-spree killed a while back?
Rirere said:
I haven't really been looking at it after my first run (I personally like Sense a lot, and AOSP didn't have a good way of dealing with the limited hardware options for me), but wasn't the brick-spree killed a while back?
Click to expand...
Click to collapse
A couple of people developed a "consensus" that it had been fixed. then 2 more people bricked their phones. ALLEGEDLY the CPU has a tendency to over clock itself and lock at 1.7 Ghz
This is all fine and dandy yet no one can figure out why or how to stop it.
I thought so too
Sent from my One using XDA Premium 4 mobile app
BMP7777 said:
I thought so too
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Like I said no one ever figured out why or how to stop it. A consensus was reached but then more people bricked. No developers could be bothered to take time out of their day to look into it though.
Kraizk said:
Like I said no one ever figured out why or how to stop it. A consensus was reached but then more people bricked. No developers could be bothered to take time out of their day to look into it though.
Click to expand...
Click to collapse
I saw one guy who was addressing it and taking names and such, but then I guess it just faded away. Do you know of ongoing issues like this? Can all of the bricks be undoubtedly proven to be from no other cause? I think that would be the defining characteristic of lack of support; difficulty in proving cause. My build of CM10.2 runs fine as long as I don't try to change the font with Font Installer. And I am reasonably certain that it isn't from CM all by itself. I have the same issue with Illusion ROM 4.2.2. Anybody know why we can't change the font? My thread; I can change topic if I want to
BMP7777 said:
I saw one guy who was addressing it and taking names and such, but then I guess it just faded away. Do you know of ongoing issues like this? Can all of the bricks be undoubtedly proven to be from no other cause? I think that would be the defining characteristic of lack of support; difficulty in proving cause. My build of CM10.2 runs fine as long as I don't try to change the font with Font Installer. And I am reasonably certain that it isn't from CM all by itself. I have the same issue with Illusion ROM 4.2.2. Anybody know why we can't change the font? My thread; I can change topic if I want to
Click to expand...
Click to collapse
It is the only common factor in permanent bricks. Phone gets hot, phone wont charge. All other "bricks" are user induced because people did not understand what S-Off meant, what wiping in TWRP means, what GSM means etc etc.
So how many confirmed permanent bricks and when was the last? Has anyone proven a cause? Contacted HTC or CM or Sprint? If there were twenty cases with only 5 confirmed, then it isn't that big from a larger standpoint. See what I mean? That would explain what you see as a lack of support? Has this happened to you?
BMP7777 said:
I thought so too
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Check your hangouts.
BMP7777 said:
Why does there seem to be very little development going on here and why is the development that is taking place so closely guarded? I thought everyone wanted more choices and new options..... I see that there is current and ongoing 10.2 development (hell, I've even built it), but no one wants to release it. I'm hearing that the last guy who did that got banned. So, if everyone is waiting for OFFICIAL builds to be released first, why are there none being officially worked on? Two times in the last three weeks I have inquired about wanting to work on some new development and have either been told straight out not to release or been effectively threatened with reporting before I have even begun an attempt. I don't know if maybe there has been a rash of jerks who are trying to claim ownership of work that does not belong to them or what, but I've never seen as much negativity about new builds in any thread I have been a part of. I want to claim ownership of nothing; I only want to open doors. I guess I'll just work on things for my own use and leave this forum to the guys currently running it. HMPH :angel:
Click to expand...
Click to collapse
You could build us a GSM version ROM that works on the sprint HTC One. You'd be a hero if you could do that. We've already unlocked our phones and are able to connect to the ATT / TMO but only manually. When the signal is lost it seems to still be looking to auto connect to sprint...I would think this should be a simple setting software but I know nothing about phone ROMs.
Beck04vall said:
You could build us a GSM version ROM that works on the sprint HTC One. You'd be a hero if you could do that. We've already unlocked our phones and are able to connect to the ATT / TMO but only manually. When the signal is lost it seems to still be looking to auto connect to sprint...I would think this should be a simple setting software but I know nothing about phone ROMs.
Click to expand...
Click to collapse
Man, if I could do that I'd be a GOD. :angel:
I love lamp
Haha Naw but I see your point but I love and appreciate every devolepers effort here on this forum ..there not a a lot but a bunch of smart and quietly brilliant devs here ...I'm comfortable but the more the merrier
Sent from my HTCONE using XDA Premium 4 mobile app
Hello All,
I realize this issue has been addressed, and there are a few short threads on the topic. Frankly, I am surprised that there is not more chatter regarding the lack of Android 6.0 - Marshmallow for Nexus 6 devices purchased through T-Mobile!!!!!!!!!!!!!!
I am no expert, but would not consider myself in the "noob" category. I am fully aware of the wider LTE spectrum required for T-Mobile Nexus devices, i.e. Band 12, as well as carrier enabled Wi-Fi calling over T-Mobile's network.
I just can't seem to understand how almost 2 months later, my d*mn Nexus 6 is still on 5.1.1. ?!?!?!?
Does anyone have anymore insight regarding this? Can we discuss and find out WHY they are still in their "Testing" phase? Honestly, I'm glad that they are doing the properly required due diligence and QA testing, but 2 months?!?!?!?!? COME ON T-Mobile/Google!
At this point, I would NOT be surprised to get 6.0 on my Note 5 before my Nexus 6. Wait, on second thought, I doubt it. Will probably get it after the Note 7 comes out.
And please don't tell me I can flash the factory image from https://developers.google.com/android/nexus/images?hl=en I am fully aware and we have all gone this route plenty of times. I simply want to start a meaningful discussion that may shed some light on WHAT in the WORLD is taking T-Mobile so long to finish validating their Marshmallow build, or if it's not truly that, then what is the hold up??????
Do you really think your going to get a meaningful discussion here? Especially when your ranting your head off throwing caps around and cursing in the thread title?
Regardless of if its what you want to hear or not... Google made the update available for you the instant it came out. If you have chosen not to take it, then that was your choice.
Wait patiently, or make the choice to go take the update... Those are your options.
Cursing in the title? I took the courtesy of censoring it, if you haven't noticed and Hell isn't exactly a "bad word". Relax man, it isn't directed at you or anyone else for that matter. If you have nothing "meaningful" to say, then why waste time even replying. Didn't realize there were so many sensitive females on this website.
It's quite obvious you don't like to read things in it's entirety prior to replying to a stranger. I would recommend Neurontin, or maybe Zoloft. Might help with the impulse control.
Punctuation exists for a reason. If I want to complain about a Nexus branded device not receiving a major update two months after release within the context of a website that exists to discuss just these types of issues, I will.
Again, Neurontin... ENN, EE, YOU, ARR, OH, ENN, TEE, EYE, ENN. Talk with your shrink about it. Might help get your head out of your rectum. Unless of course your father prefers it that way.
Then by all means, carry on.
Anyhow, spoke to a T-Mobile tech support representative, not that they have ever been much help historically, but apparently they are testing T-Mobile specific applications to ensure that they play well with Android 6.0 (He Mentioned Visual Voicemail, T-Mobile My Account, etc.). Does that mean that the Nexus 6 devices purchased via T-Mobile will have a disparate build? Based on what this guy said, it looks like it.
Another reason why I didn't just blindly flash the Universal builds. Not to mention, many T-Mobile customers who have already done so, are experiencing bugs with their devices and/or broken functionality.
Android1126 said:
Cursing in the title? I took the courtesy of censoring it, if you haven't noticed and Hell isn't exactly a "bad word". Relax man, it isn't directed at you or anyone else for that matter. If you have nothing "meaningful" to say, then why waste time even replying. Didn't realize there were so many sensitive females on this website.
It's quite obvious you don't like to read things in it's entirety prior to replying to a stranger. I would recommend Neurontin, or maybe Zoloft. Might help with the impulse control.
Punctuation exists for a reason. If I want to complain about a Nexus branded device not receiving a major update two months after release within the context of a website that exists to discuss just these types of issues, I will.
Again, Neurontin... ENN, EE, YOU, ARR, OH, ENN, TEE, EYE, ENN. Talk with your shrink about it. Might help get your head out of your rectum. Unless of course your father prefers it that way.
Then by all means, carry on.
Click to expand...
Click to collapse
That was a great delivery, lmao.
I don't give a **** if you say hell. Just saying if you want the reasonable conversation your claim to, your doing a pretty ****ing bad job of starting it.
Your Nexus branded devices DOES have an update. You're just waiting for it to be sent to you, by all means continue to do so.
scryan said:
I don't give a **** if you say hell. Just saying if you want the reasonable conversation your claim to, your doing a pretty ****ing bad job of starting it.
Your Nexus branded devices DOES have an update. You're just waiting for it to be sent to you, by all means continue to do so.
Click to expand...
Click to collapse
Son, you really DO NOT know what you are talking about. Go look at the Factory Image page at https://developers.google.com/android/nexus/images?hl=en , now go to Shamu, and read the images (might take a bit of scrolling, so resist the urge to give up and rant and rave, in an attempt to teach me etiquette). Do you see where it says "5.1.0 (For T-Mobile ONLY) (LMY47M)" or "5.1.1 (For T-Mobile ONLY) (LYZ28E)" or "5.1.1 (For T-Mobile ONLY) (LYZ28J)" or 5.1.1 "(For T-Mobile ONLY) (LYZ28K)" or "5.1.1 (For T-Mobile ONLY) (LYZ28M)" or "5.1.1 (For T-Mobile ONLY) (LYZ28N)"??
Again, impulse control. Do a little research before replying. Not to mention VoLTE and Cat 14 LTE that only T-Mobile uses (in this country, and at this time). Not saying that the universal build absolutely WON'T work, but there are more than a few stories out there stating that exact opposite. I for one, would like to wait for a build that is catered to the frequencies of my Mobile network for the simple fact that it will address all of those incompatibility issues.
Anger issues? Abused as a child? Watch your dirty little mouth. Also, learn some basic grammar "I don't give a **** if you say hell. Just saying if you want the reasonable conversation "your" claim to, "your"doing a pretty ****ing bad job of starting it"?
I think you meant "you" and you're"
How do we go from hell to F***? You're one sick little boy.
Moderator, please close this thread, as you deem fit.
Also, many people who have downloaded the universal image, wiped their devices, and installed the update, have had to root, downgrade their Radio for 5.1.1. just to get an LTE signal and WiFi calling as well as a number of other features to work properly.
Again, read before you reply.
Android1126 said:
Son, you really DO NOT know what you are talking about. Go look at the Factory Image page at https://developers.google.com/android/nexus/images?hl=en , now go to Shamu, and read the images (might take a bit of scrolling, so resist the urge to give up and rant and rave, in an attempt to teach me etiquette). Do you see where it says "5.1.0 (For T-Mobile ONLY) (LMY47M)" or "5.1.1 (For T-Mobile ONLY) (LYZ28E)" or "5.1.1 (For T-Mobile ONLY) (LYZ28J)" or 5.1.1 "(For T-Mobile ONLY) (LYZ28K)" or "5.1.1 (For T-Mobile ONLY) (LYZ28M)" or "5.1.1 (For T-Mobile ONLY) (LYZ28N)"??
Again, impulse control. Do a little research before replying. Not to mention VoLTE and Cat 14 LTE that only T-Mobile uses (in this country, and at this time). Not saying that the universal build absolutely WON'T work, but there are more than a few stories out there stating that exact opposite. I for one, would like to wait for a build that is catered to the frequencies of my Mobile network for the simple fact that it will address all of those incompatibility issues.
Anger issues? Abused as a child? Watch your dirty little mouth. Also, learn some basic grammar "I don't give a **** if you say hell. Just saying if you want the reasonable conversation "your" claim to, "your"doing a pretty ****ing bad job of starting it"?
I think you meant "you" and you're"
How do we go from hell to F***? You're one sick little boy.
Moderator, please close this thread, as you deem fit.
Click to expand...
Click to collapse
theres only one build for marshmallow. no matter which carrier you use, you use the same build. yes, wifi calling works on it. lte, volte, and everything else too. im on tmobile as well.
Android1126 said:
Anger issues?
Click to expand...
Click to collapse
Yes. You have them.
https://support.t-mobile.com/thread/116433
Please note, as documented by tmobile support, no tmobile specific build is presented because beginning with 6.0 its a unified build.
Android 6.0 (Marshmallow) is a unified build and is the same version across all carriers. WiFi Calling is baked into the OS.
Click to expand...
Click to collapse
simms22 said:
theres only one build for marshmallow. no matter which carrier you use, you use the same build. yes, wifi calling works on it. lte, volte, and everything else too. im on tmobile as well.
Click to expand...
Click to collapse
simms22, thanks for the advice. I do realize that, and I have read as much for the most part. My main point was really an attempt at trying to gain an understanding as to why Nexus 6 devices from T-Mobile have not yet been updated to Marshmallow.
I appreciate your comment. I have also read about a number of incompatibility issues when flashing the universal build, so I like to err on the side of caution, especially considering that I use my Note 5 as a daily driver. Also, not trying to do a full wipe just yet (I realize I can do so without, but from what I have read, that is what is causing the bugs/incompatibility).
Like I stated earlier, the T-Mobile tech. rep. stated that there will be a T-Mobile specific build out soon. Now what that contains, I cannot say. Just trying to gain some insight. It could just be T-Mobile bloatware, though I am fairly certain they are addressing some of the known issues that are affecting a portion of Nexus 6 devices running Marshmallow on T-Mobile.
Thanks again.
scryan said:
Yes. You have them.
https://support.t-mobile.com/thread/116433
Please note, as documented by tmobile support, no tmobile specific build is presented because beginning with 6.0 its a unified build.
Click to expand...
Click to collapse
You just linked me to a site where a bunch of amateurs are discussing flashing a non standard build. Where, by the way, a person poses the question "a) Is that a T-Mobile Build? I am not seeing Wi-Fi calling related section anywhere"
Really, do you read anything before posting replying?
I would look at this page that T-Mobile has published.
https://support.t-mobile.com/community/phones-tablets-devices/software-updates#tmoSUPDocTitle
Do you see what it says? If you need help reading (and then pausing to process), let me know.
Here is a recap for people with learning disabilities (no offense if you really have one, seriously).
UPDATE PROCESS 3 stages. Current: Stage 2 T-Mobile testing.
Please man, just stop replying. Because I can keep making you look like your mother dropped you on your head all night.
scryan said:
Yes. You have them.
https://support.t-mobile.com/thread/116433
Please note, as documented by tmobile support, no tmobile specific build is presented because beginning with 6.0 its a unified build.
Click to expand...
Click to collapse
Also, do you see where the correct answer states "Flashing with a T-Mobile rom is going to require you to unlock your bootloader...." Key words "T-Mobile ROM"
Where does it say that all builds are unified starting at Android 6.0? That may be the case for all other carriers, but it is PRETTY obvious, that this does not apply to the T-Mobile build for 6.0.
Android1126 said:
You just linked me to a site where a bunch of amateurs are discussing flashing a non standard build. Where, by the way, a person poses the question "a) Is that a T-Mobile Build? I am not seeing Wi-Fi calling related section anywhere"
Really, do you read anything before posting replying?
I would look at this page that T-Mobile has published.
https://support.t-mobile.com/community/phones-tablets-devices/software-updates#tmoSUPDocTitle
Do you see what it says? If you need help reading (and then pausing to process), let me know.
Here is a recap for people with learning disabilities (no offense if you really have one, seriously).
UPDATE PROCESS 3 stages. Current: Stage 2 T-Mobile testing.
Please man, just stop replying. Because I can keep making you look like your mother dropped you on your head all night.
Click to expand...
Click to collapse
Your not really making me look like I have been dropped on my head, your making yourself look like a raving lunatic.
I gave you the same answer as simms, other than the fact that I linked to the official support site where the answer marked as correct supports what I said.
Android1126 said:
Also, do you see where the correct answer states "Flashing with a T-Mobile rom is going to require you to unlock your bootloader...." Key words "T-Mobile ROM"
Where does it say that all builds are unified starting at Android 6.0? That may be the case for all other carriers, but it is PRETTY obvious, that this does not apply to the T-Mobile build for 6.0.
Click to expand...
Click to collapse
Flashing ANY rom is going to require a bootloader unlock, so yes flashing a tmobile rom would require a bootloader unlock.
Other carriers then T-Mobile have a unified build? lol, check your definitions there man
u·ni·fy
ˈyo͞onəˌfī/
verb
past tense: unified; past participle: unified
make or become united, uniform, or whole.
It's not united or uniform if its different for tmobile... the entire basis of a unified build is it's the same for everyone.
This thread is too good. Nothing but multiparagraph rants and personal insults from you about how others have anger issues. :laugh:
Android1126 said:
Also, do you see where the correct answer states "Flashing with a T-Mobile rom is going to require you to unlock your bootloader...." Key words "T-Mobile ROM"
Where does it say that all builds are unified starting at Android 6.0? That may be the case for all other carriers, but it is PRETTY obvious, that this does not apply to the T-Mobile build for 6.0.
Click to expand...
Click to collapse
6.0 is one build...I'm pretty sure everyone else that has upgraded by now have already said that...if I take my "sprint" nexus 6 and put a t-mobile sim in...and I have 6.0 after it realizes, hey, I'm on t-mobile...wifi calling will pop up and t-mobile service will work...and before you try to say I'm wrong or t-mobile knows better...why did this work when I tried just that to help someone with the same issue
scryan said:
Your not really making me look like I have been dropped on my head, your making yourself look like a raving lunatic.
I gave you the same answer as simms, other than the fact that I linked to the official support site where the answer marked as correct supports what I said.
Flashing ANY rom is going to require a bootloader unlock, so yes flashing a tmobile rom would require a bootloader unlock.
Other carriers then T-Mobile have a unified build? lol, check your definitions there man
u·ni·fy
ˈyo͞onəˌfī/
verb
past tense: unified; past participle: unified
make or become united, uniform, or whole.
It's not united or uniform if its different for tmobile... the entire basis of a unified build is it's the same for everyone.
This thread is too good. Nothing but multiparagraph rants and personal insults from you about how others have anger issues. :laugh:
Click to expand...
Click to collapse
Yes, I know how to flash an image and/or a ROM, unlocking the bootloader has nothing to do what this conversation, other than I do not want to wipe my device Einstein. Do you know how to SSH into a RHEL Server across a minimally perforated firewall to change jre environments for global profile enabled Linux applications on let's say, an Apache Web Server LBP?
I know how Linux works. Android is child's play.
You are completely ignoring the fact that there is a reason that T-Mobile Nexus 6 devices have NOT been given the green light for Android 6.0.
Really, why do you think that is? If it were such a simple solution, then it wouldn't have been 2 months and no update. Clearly, there are some technical details, that are probably WAY above your intrinsic level of comprehension, that are delaying the release of this image.
If you are too dense to comprehend that, then continuing this conversation is futile.
If anyone has any insight or information as to the delay, feel free to let me know.
Thanks.
A2CKilla said:
6.0 is one build...I'm pretty sure everyone else that has upgraded by now have already said that...if I take my "sprint" nexus 6 and put a t-mobile sim in...and I have 6.0 after it realizes, hey, I'm on t-mobile...wifi calling will pop up and t-mobile service will work...and before you try to say I'm wrong or t-mobile knows better...why did this work when I tried just that to help someone with the same issue
Click to expand...
Click to collapse
Brother, no offense, I'm not following you. The reason Wi-Fi calling pops up when you throw a T-Mobile SIM card into a Sprint phone, is because Wi-Fi calling is baked into Android 5.1.1.
Sorry, not sure what point you are trying to make. You do know that on the Google Developers Factory Images page, there are T-Mobile specific builds for the Nexus 6 right?
Even Verizon users, just started receiving 6.0 in this past week. The only other time this happened was with the Samsung Galaxy Nexus, and we all know what happened there. Exact same thing I am talking about. As a matter of fact, (will link to it later), we have already had an in-depth discussion about this on a different forum on this site. There are in fact different builds for different carriers.
The Universal build WILL work, no one is saying that it won't, but keep doing some research and you will see that many (and I mean many) users have reported incompatibility and/or broken functionality when flashing the Factory Images on their T-Mobile and also Verizon devices.
As far as what you are saying about a T-Mobile SIm card working in a Sprint Nexus 6. I don't think anyone is arguing that. We all know that to be the case, although I can guarantee you that if you put a Verizon SIM card into your Sprint/AT&T/T-Mobile Nexus 6, it will NOT work.
I know because I have Verizon service (for work), and I have tried. That is less about the phone being locked, and more about non Verizon IMEI's being blacklisted. My point is, that we know that the Nexus 6 is unlocked. That is not the question I am asking here.
Android1126 said:
Brother, no offense, I'm not following you. The reason Wi-Fi calling pops up when you throw a T-Mobile SIM card into a Sprint phone, is because Wi-Fi calling is baked into Android 5.1.1.
Sorry, not sure what point you are trying to make. You do know that on the Google Developers Factory Images page, there are T-Mobile specific builds for the Nexus 6 right?
Click to expand...
Click to collapse
For LP yes.
Android1126 said:
Even Verizon users, just started receiving 6.0 in this past week.
Click to expand...
Click to collapse
Yup, VZW took their sweet ass time testing and distributing it too.
Yet check that developer image page... and where is the VZW MM image?
Just because the carrier has not pushed it as an OTA does not mean it's a different build, because M is unified. So even though it took until last week for VZW to push it to their phones.... It's the same unified build that has been out this whole time.
Android1126 said:
As far as what you are saying about a T-Mobile SIm card working in a Sprint Nexus 6. I don't think anyone is arguing that. We all know that to be the case, although I can guarantee you that if you put a Verizon SIM card into your Sprint/AT&T/T-Mobile Nexus 6, it will NOT work.
I know because I have Verizon service, and I have tried. That is less about the phone being locked, and more about non Verizon IMEI's being blacklisted. My point is, that we know that the Nexus 6 is unlocked. That is not the question I am asking here.
Click to expand...
Click to collapse
I have a non VZW phone btw, and on VZW with a VZW sim. It works fine. You need to do your reading on this one, lots of us don't have Verizon issued phones, its only ATT that is carrier locked.
Many people had issues getting VZW to activate their nexus 6, this was not technical as much as it was people bringing their phones to VZW and VZW declining. People also had issues not getting their discount for buying a phone outright, but from early launch you could stick a VZW sim into a nexus 6 and use it
See this droid life article from launch
http://www.droid-life.com/2014/10/31/nexus-6-working-on-verizon-out-of-the-box/
Enough ranting now...
Thread closed