Related
Hi everyone.
Since T-mobile´s version of HD2 is pretty different from the orginal HD2 and it requires a different rom, why not create a subforum only for this version? ..since it might get pretty messy with both types of rom mixed together in the same forum....
Some of the differences between HD2 and T-mobile HD2 version:
T-Mobile:
Radio - WCDMA/HSPA 1700/2100MHz
RAM: 576MB
ROM: 1GB
Standard version:
Radio - WCDMA/HSPA 900/2100MHz
RAM: 448MB
ROM: 512MB
and flashing it with the other rom might damage the phone! so yeah...
Just a thought...
Best regards
Claus
yes would like to see that
It would be nice. However I think it would depend on the developers. They probably don't want to maintain 2 threads if their rom supports both version.
Maybe someone could build a master list of their roms and sort them and maintain that list. Either in a thread here or google spreadsheet.
Yes I'd like that it'd be better i must say
Its an awful idea! If you split it into two different sections it would be much more difficult for someone to support both. In most cases someone would pick one or the other.. aka less rom's.
I disagree because there is too little to justify a whole new forum. If it was drastically different like CDMA and GSM then that would be necessary, but since they are both GSM, and the differences can be "easily solved" then we would just have to see which DEV supports which version in their own appropriate thread.
~~Tito~~ said:
I disagree because there is too little to justify a whole new forum. If it was drastically different like CDMA and GSM then that would be necessary, but since they are both GSM, and the differences can be "easily solved" then we would just have to see which DEV supports which version in their own appropriate thread.
Click to expand...
Click to collapse
I think a new subforum would help. I only say this because there is danger of bricking your device if you flash the wrong ROM. That seems like a good enough reason to me. I'm sure there are other minor reasons at well that might not be known about yet.
Yeah, it shouldn't be that hard, since most of the roms out now won't work with TMOUS, its only right we have a sub-forum, It's a great IDEA
Its not the issue. The issue is that there are far too many LAZY people who either refuse to or dont read things.
If chefs label the threads properly with instructions, then there is NO need for a separate sub section. Go look at the HSPL thread and it already obvious that people cant be bothered reading one or two pages, so brick their phones.
Label things properly and there shouldnt be a problem. Brick your own phone for not reading, then its your own damn fault IMHO.
start a poll if they see enough people they will do it, I did the same thing in the tp2 for Android and once we got 100 votes they did it.
Oh well, it's the "I'm more important than others" mentality again.
It wouldn't be difficult for the devs to state which ROM is suitable for the T-Mob version, no need for another subforum, for more duplicate threads to maintain.
kenkiller said:
Oh well, it's the "I'm more important than others" mentality again.
It wouldn't be difficult for the devs to state which ROM is suitable for the T-Mob version, no need for another subforum, for more duplicate threads to maintain.
Click to expand...
Click to collapse
first of all, what is the difference between a rom that works.. and one that doesn't?
and I don't think anyone has bricked their device by flashing a rom.. thats only when they flash the wrong hspl.
and I'd just like to say once again that making a new sub-forum is an awful idea.
We do not need a new forum. Thanks.
that's a great idea! vote for yes
t69broken said:
start a poll if they see enough people they will do it, I did the same thing in the tp2 for Android and once we got 100 votes they did it.
Click to expand...
Click to collapse
foney said:
Its not the issue. The issue is that there are far too many LAZY people who either refuse to or dont read things.
If chefs label the threads properly with instructions, then there is NO need for a separate sub section. Go look at the HSPL thread and it already obvious that people cant be bothered reading one or two pages, so brick their phones.
Label things properly and there shouldnt be a problem. Brick your own phone for not reading, then its your own damn fault IMHO.
Click to expand...
Click to collapse
EXACTLY! Thats my whole point to not agreeing with the separate sub forum. Since they are almost exactly the same, just different sized NAND space, and radio antennas, the "different" shape happens to all HTC phones when they are sent to US carriers, different colors, button styles. That right there never gets separate sub forums in any of the other device sections, unless different cellphone technologies are involved, like with CDMA or GSM.
No new forum should be added, since well, to much more work for something thats not needed.
foney said:
Its not the issue. The issue is that there are far too many LAZY people who either refuse to or dont read things.
If chefs label the threads properly with instructions, then there is NO need for a separate sub section. Go look at the HSPL thread and it already obvious that people cant be bothered reading one or two pages, so brick their phones.
Label things properly and there shouldnt be a problem. Brick your own phone for not reading, then its your own damn fault IMHO.
Click to expand...
Click to collapse
The key word is IF.
Suppose they don't label the thread properly which DOES happen every once in a while and it could be bad.
~~Tito~~ said:
EXACTLY! Thats my whole point to not agreeing with the separate sub forum. Since they are almost exactly the same, just different sized NAND space, and radio antennas, the "different" shape happens to all HTC phones when they are sent to US carriers, different colors, button styles. That right there never gets separate sub forums in any of the other device sections, unless different cellphone technologies are involved, like with CDMA or GSM.
No new forum should be added, since well, to much more work for something thats not needed.
Click to expand...
Click to collapse
The MyTouch and G1 are essentially the same phone in different packaging and they have their own forums and most of the ROMs are designed for both. It just makes for a cleaner forum.
dornstar said:
The MyTouch and G1 are essentially the same phone in different packaging and they have their own forums and most of the ROMs are designed for both. It just makes for a cleaner forum.
Click to expand...
Click to collapse
That is wrong my friend. They are not. They have shared ROMs is because the SPL's are almost the same, they are different devices.
This is completely different from that.
dornstar said:
The key word is IF.
Suppose they don't label the thread properly which DOES happen every once in a while and it could be bad.
Click to expand...
Click to collapse
I could be wrong, but who's HD2 was bricked from flashing the wrong ROM?
I know I've heard of a few from flashing the wrong HSPL, but I haven't seen even one about the wrong rom..
The key here is that, people need to read, and its not that hard to label a thread. Plain and simple, more complication isn't necessary. I know separation for different devices is important, for the same device, it shouldn't be needed.
We all know that american cellphone carriers always have European phones changed to fit their needs. Here they upped the ROM size, and made the phone 1mm taller for some reason. THAT is nothing really different.
is HTC magic support wireless-N network?
deathscyth1985 said:
is HTC magic support wireless-N network?
Click to expand...
Click to collapse
Is wireless-N software related or more hardware related do you think?
Are you posting methods or ideas to integrate Wireless-N to commonly used roms?
Are you posting or developing software to allow wireless-N compatablity?
If not then I'm moving this to General where it belongs.
I beleive that its more of a hardware based issue. The only other way im guessing if you had extremely low level access you might be able to. Doubt it could be implemented via a ROM
Binary100100 said:
Is wireless-N software related or more hardware related do you think?
Are you posting methods or ideas to integrate Wireless-N to commonly used roms?
Are you posting or developing software to allow wireless-N compatablity?
If not then I'm moving this to General where it belongs.
Click to expand...
Click to collapse
i just asking question about HTc Magic support wireless-N network..
sorry for posting wrong area, pls move it to general.. thx
Don't think the wifi supports 802.11n. Only info I can find, shows 802.11b/g.
So, I posted a thread asking about the Wifi issues I have been experiencing, hoping someone had some insight. Apparently a sincere question that hasn't been addressed in previous threads is unfit however, as pulser_g2 sent me a nice message letting me know he trashed my thread.
So I will ask again.
I noticed with my N1 that I could pick up my Wifi signal at a distance of about 95 feet from the unit with a stable connection. With my fascinate, I am only able to stray about 35 feet before it drops and jumps to 3G.
I was kind of hoping that someone might have some insight as to whether or not this is a PURELY hardware related issue. I was hoping that there might be some tweaking that could help me out.
If someone could maybe please chime in before this somehow offensive inquiry is canned, I would appreciate it. I respect the knowledge base here, and would hate to have to leave for other forums to ask what I feel are legitimate questions.
And yeah, I'm a little annoyed that the question was canned, when there's a veritable plethora of completely useless posts floating around here.
#ModFail
I also have poor wifi reception on my Fascinate compared to my Incredible. I am interested if there is a hardware problem or if its a software fix. Seems a new baseband may fix this... I hope.
sent from my 1.2ghz voodoo fascinate
Copperhed said:
I also have poor wifi reception on my Fascinate compared to my Incredible. I am interested if there is a hardware problem or if its a software fix. Seems a new baseband may fix this... I hope.
sent from my 1.2ghz voodoo fascinate
Click to expand...
Click to collapse
Yeah, hope. It's a fair trade off actually, because I do actually have 3G at home to switch to, unlike when I was on T-Mo. I am kind of hoping this is something that can be addressed however
#ModFail
Click to expand...
Click to collapse
#PosterFail.
This doesn't belong in the development section.
adrynalyne said:
#PosterFail.
This doesn't belong in the development section.
Click to expand...
Click to collapse
We need a Q& A sub forum like the Captivate has
Sent from my 1.2Ghz voodoo fascinate
I don't disagree.
Or a "Daswolven Question Of The Hour" section
Sent from my SCH-I500 using XDA App
adrynalyne said:
#PosterFail.
This doesn't belong in the development section.
Click to expand...
Click to collapse
It fits best. We do need a Q&A section. My logic however had to do with the issue. If it's hardware, fine. If it's possible to improve via hack or tweak, that qualifies as a development issue. If it's a radio issue, then perhaps a fix will come, but again, development issue.
tallnerd1985 said:
Or a "Daswolven Question Of The Hour" section
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
All due respect, I don't ask many questions. I usually take the necessary time to read up and search. This question has not been asked, or I wouldn't have raised it. I am neither new here, or ignorant of the rules. Most of my posts are relevant and some even attempt to be helpful.
Statement of point: this post asks a question, and reply not addressing the question is as useless and improperly placed as this inquiry is being accused of.
Now could someone who understands the question, and has the knowledge to address it take a moment to enlighten me? It would be appreciated.
Sent from my SCH-I500 using XDA App
The point that everyone is making here is that the Development sub-forum is for Development only, not for troubleshooting, questions or feature requests. Thats what the general forum is for, not the development forum. Please stop posting here unless you are contributing to the advancement of the phone or replying to a devs thread.
Sent from my SCH-I500 using XDA App
tallnerd1985 said:
The point that everyone is making here is that the Development sub-forum is for Development only, not for troubleshooting, questions or feature requests. Thats what the general forum is for, not the development forum. Please stop posting here unless you are contributing to the advancement of the phone or replying to a devs thread.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Fair enough, then this should be moved to the general thread, along with about half the other posts. Lol.
Sent from my SCH-I500 using XDA App
@OP
You know it's funny that you of all people should complain about the plethora of useless posts around here when you yourself contribute to the mess.
You don't post in the appropriate sections and I'm quite sure that you remember the useless and misleading thread "iOS port for 2.1 running on my Fascinate! " that you created a while ago. That was blatantly and outrightly spamming the boards, but I let it pass.
Regarding your comment about the XDA Moderators; talking trash about the admin staff is tantamount to flaming and as such you have been issued an infraction. If you have a problem or an issue, contact any of the moderators via PM and we will discuss your issues in a more civilized fashion.
I would advice you to use better judgement going forward.
Back on Topic!
leepriestenator said:
@OP
You know it's funny that you of all people should complain about the plethora of useless posts around here when you yourself contribute to the mess.
You don't post in the appropriate sections and I'm quite sure that you remember the useless and misleading thread "iOS port for 2.1 running on my Fascinate! " that you created a while ago. That was blatantly and outrightly spamming the boards, but I let it pass.
Regarding your comment about the XDA Moderators; talking trash about the admin staff is tantamount to flaming and as such you have been issued an infraction. If you have a problem or an issue, contact any of the moderators via PM and we will discuss your issues in a more civilized fashion.
I would advice you to use better judgement going forward.
Back on Topic!
Click to expand...
Click to collapse
Fair and warranted, also appreciated. My issue was with the post being trashed, instead of moved.
Now that things are situated, does anyone know if the diminished wifi reception on the Fascinate is purely a hardware issue?
Sent from my SCH-I500 using XDA App
Wifi sucks
I agree on QnA my wifi signal and speed is horrible on this device. I would like to see some kind of fix for this my 3g at home is crappy.
given the power output(router and phone), antenna design on both the router as well as in the phone, and the nature of the freq used for WiFi it is clear that you had a mutant N1 and should not expect the same performance from any other phone. NO im not being a smartass just being realistic. as a amateur radio operator i deal with radio freq's on an almost daily basis and give the nature of the freq's used for WiFi they are not going to give you good performance without a better antenna setup or more power. since you cant increase the power output your only other option to extend your range is a batter antenna.
Mylt1 said:
given the power output(router and phone), antenna design on both the router as well as in the phone, and the nature of the freq used for WiFi it is clear that you had a mutant N1 and should not expect the same performance from any other phone. NO im not being a smartass just being realistic. as a amateur radio operator i deal with radio freq's on an almost daily basis and give the nature of the freq's used for WiFi they are not going to give you good performance without a better antenna setup or more power. since you cant increase the power output your only other option to extend your range is a batter antenna.
Click to expand...
Click to collapse
Not sure what you're saying here. I had two Nexus Ones, having replaced the first due to a trackball issue. I have a high end wireless N router. Both N1s had about 90 ft range.
My question is if the differential in the range has to do with hardware entirely? Is the Fascinate not as wireless N friendly?
Sent from my SCH-I500 using XDA App
Just throwing this out even tho I'm sure u have thought of this. I get low bars on my fascinate to no bars of wifi after about 15 feet. However even with no bars it will actaully still work another 30-50 ft out into the driveway. Maybe just a poor signal on my end.
Sent from my SCH-I500 using XDA App
Daswolven said:
Not sure what you're saying here. I had two Nexus Ones, having replaced the first due to a trackball issue. I have a high end wireless N router. Both N1s had about 90 ft range.
My question is if the differential in the range has to do with hardware entirely? Is the Fascinate not as wireless N friendly?
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
"high end" means nothing more than you paid more for a name. WiFi and its speeds are a standard, so no matter if you paid $30 for one or $300 for one they will perform the same. yes, there is a chance that the higher end one MIGHT be made with better components but i doubt it. as the poster above me stated, it could just be an issue with the signal bars not showing up but you still have a connection. download one of the WiFi analyzers from the market and see what that gives your for signal strength as you walk down the driveway.
If your router allows 3rd party firmware (like most Linksys models do), flash a better firmware to the router, such as DD-WRT, that allows you to increase the power output of the wireless system.
I have had the incredible since day one and picked up a facinate a week ago and I too suffer from poor wifi range. I also have an N router and have run up and download speed tests and my incredible smokes the facinate. I am hoping its software related and is fixed with the 2.2 update.
I have to tell you guys, an avid follower of xda I am very disappointed that a useless comment was made (now corrected) towards the issue at hand before trying to help. I thought helping each other is what this forum was designed for not belittling someone needing help? This is now the 2nd thread asking for help this guy has posted and and no help was offered until slapped on the hand... But hey, what do I know. I am only 48 years old.
Sent from my SCH-I500 using XDA App
Lol. I will freely admit I have no knowledge on the topic, only logic. I will check with a wifi signal app when I get home, on the way there now. I merely assumed it was losing signal because it loses wifi, and switches to 3G when I go out on the porch to smoke.
I also know I got the router I did because my older G would put out a very weak signal to the second floor, whereas now I pull almost full bandwidth from there.
Regardless, I will check shortly and post my findings.
Sent from my SCH-I500 using XDA App
There have been a lot of mixed feelings about the Note 5's new direction as far as removing the micro sd card slot, no more replaceable battery, etc. I'm starting this thread for anyone that has a Note 5 and is looking for solutions/band-aids to any Note 5 issues. Here's a video covering four of the major issues and how to fix them (no micro sd, no replaceable battery, no IR blaster, slippery glass back). The main issue without a solution is the very poor RAM management. I'm still looking into a solution for that, but unfortunately that issue will likely need to be fixed by Samsung themselves via software update.
Definitely post your own solutions that weren't mentioned in the video so we can give Note 5 owners as much advice as possible.
P.S. Comments asking how to solve different issues are of course welcome, but any negative comments/lamenting about the Note 5 should go in a separate thread already started for that. Here's the link to that thread:
http://forum.xda-developers.com/note5/general/overall-step-backwards-compared-to-note-t3177999
It's good to, you know, read the rest of the form that alread has threads on all of these things?
Sent from my SM-N920P using Tapatalk
DAvid_B said:
It's good to, you know, read the rest of the form that alread has threads on all of these things?
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Just searched through the forum and found mostly complaint threads about missing features with an occasional solution to one of the problems in a single post buried in 30+ pages of posts. I didn't find anything about using a dbrand skin, getting a harmony home hub, getting a dash micro, etc. Aside from that though, the purpose of this thread was to consolidate solutions and have the post count stay very small so people could find solutions to the most common issues quickly. As far as I could find, this is currently the only "solution" thread with the exception of one thread dedicated to just the missing micro SD card slot.
Maybe if you looked in the proper forum, the Q&A one, you'd find them all?
This internet thing isn't really that hard..
TacticalMissions said:
Just searched through the forum and found mostly complaint threads about missing features with an occasional solution to one of the problems in a single post buried in 30+ pages of posts. I didn't find anything about using a dbrand skin, getting a harmony home hub, getting a dash micro, etc. Aside from that though, the purpose of this thread was to consolidate solutions and have the post count stay very small so people could find solutions to the most common issues quickly. As far as I could find, this is currently the only "solution" thread with the exception of one thread dedicated to just the missing micro SD card slot.
Click to expand...
Click to collapse
Thanks for the video. Much appreciated!
Sent from my SM-N920T using Tapatalk
Thanks i am gonna buy that wireless charger
I wouldn't call the lack of a removable battery an issue but more of a missing feature. Issues are things like app crashing or issues with earpiece etc...
Sent from my MotoG3 using Tapatalk
Agreed... Issue = something not working as intended, not a physical design choice.
Sent from my SM-N920V using Tapatalk
That was an extremely helpful video, thanks very much! I even subscribed to your channel! Thanks for doing it and sharing it. I'm even more inclined to get a Note 5 now after watching it.
PS - It really puzzles me that some people's response would be to criticize it on the basis that you can find the solutions separately elsewhere. It's like criticizing the invention of a smart phone by saying that you can do all the separate functions with different gadgets. (*SMH*). Please ignore those comments and keep making helpful videos!
I've been reverse engineering the bootloader for the G955F in an attempt to find some sort of exploit to let us root our devices and not trip the KNOX flag. It now seems like the next step is to get in to the bootloader UART.
I've looked at guides such as: https://forum.xda-developers.com/showthread.php?t=1901376 where they make a microUSB version of this cable and have attempted to replicate this with the USB-C connector by shorting the CC pins to ground with various resistances but have had no joy.
Looking at the kernel source, I can see this:
Code:
"-MHL:1K",
"-VZW Accessory:28.7K",
"-VZW Incompatible:34K",
"+RDU TA:40.2K",
"+HMT:49.9K",
"-Audiodock:64.9K",
"-USB LANHUB:80.07K",
"-Charging Cable:102K",
"+Game Pad:121K",
"+TYPE1 Charger:200K",
"+Jig USB Off:255K",
"+Jig USB On:301K",
"+Deskdock:365K",
"+TYPE2 Charger:442K",
"+Jig UART Off:523K",
"+Jig UART On:619K",
"+TA:eek:PEN",
"+USB:eek:PEN",
"+CDP:eek:PEN",
"+Undefined Charging:XXX";
Which definitely indicates that the known resistor values should work, but so far, I can not get any serial output at all. Is my assumption that USB-C cables actually have CC wires, rather than an internal resistor in the connector head correct?
UPDATE: I have attached the pinout for the UART cable.
Getting it would be amazing.
I believe This will take time
@Vatsal can you please move this to the right place?
As this forum place here is not how-to/guides/questions.
Thanks very much as always :good:
Tkkg1994 said:
@Vatsal can you please move this to the right place?
As this forum place here is not how-to/guides/questions.
Thanks very much as always :good:
Click to expand...
Click to collapse
Thread moved Sir.
Next time, kindly use the report button.
Thanks:good:
This post, posts of my own, and others I've seen SCREAM that we need a Dev Discussion section like XDA used to have (least majority of the phones I had 3-4 years ago plus had them.) Would be dev discussion only where the OP is actually working on a dev issue (root, getting dex to run sans dock, etc.) and be able to get actual help.
Unfortunately these dev type threads get buried by non dev like questions and I imagine the people capable of helping won't come in here and dig for stuff to help with.
nosympathy said:
This post, posts of my own, and others I've seen SCREAM that we need a Dev Discussion section like XDA used to have (least majority of the phones I had 3-4 years ago plus had them.) Would be dev discussion only where the OP is actually working on a dev issue (root, getting dex to run sans dock, etc.) and be able to get actual help.
Unfortunately these dev type threads get buried by non dev like questions and I imagine the people capable of helping won't come in here and dig for stuff to help with.
Click to expand...
Click to collapse
+1
I would really like to get this working but could really do with some outside input. Having this in the more general section is going to make this vanish quickly.
look what I got
@jujusito @halo87 @nosympathy @dragunbayne @Harry44
Look what I just got in the mail...
...now just to reverse engineer it and make a schematic.
happytomato said:
@[email protected]@[email protected]@Harry44
Look what I just got in the mail...
...now just to reverse engineer it and make a schematic.
Click to expand...
Click to collapse
How would would this take?
@halo87 That sentence didn't make much sense...
You should ask this kind of questions on a proper EE forums because I don't think you'll have useful answers here. We're just a bunch of clueless dudes poking with firmware files.
Excited to see that someone is working (sort of) on exploiting the bootloader and thus avoiding the knox counter
Please let us know with your future progress :good:
happytomato said:
@jujusito @halo87 @nosympathy @dragunbayne @Harry44
Look what I just got in the mail...
...now just to reverse engineer it and make a schematic.
Click to expand...
Click to collapse
Any progress on this? Trying to achieve UART myself, but so far nothing.
militiaOfDeath said:
Any progress on this? Trying to achieve UART myself, but so far nothing.
Click to expand...
Click to collapse
I actually made one and then lost it when formatting my laptop. I shall probably do it again in the next few days, possibly today. Heads up though, it is not a solution in itself. The resistor magic happens within the Anyway Jig and I think that only the S103 is compatible with USB C. In any case, watch this space. If you want to share any findings, please PM me!
happytomato said:
I've been reverse engineering the bootloader for the G955F in an attempt to find some sort of exploit to let us root our devices and not trip the KNOX flag. It now seems like the next step is to get in to the bootloader UART.
I've looked at guides such as: https://forum.xda-developers.com/showthread.php?t=1901376 where they make a microUSB version of this cable and have attempted to replicate this with the USB-C connector by shorting the CC pins to ground with various resistances but have had no joy.
Looking at the kernel source, I can see this:
Which definitely indicates that the known resistor values should work, but so far, I can not get any serial output at all. Is my assumption that USB-C cables actually have CC wires, rather than an internal resistor in the connector head correct?
Click to expand...
Click to collapse
How were you going about reverse engineering the bootloader
happytomato said:
Is my assumption that USB-C cables actually have CC wires, rather than an internal resistor in the connector head correct?
Click to expand...
Click to collapse
Doesn't usb-c spec call for a 56k resistor in the cable? I remember there being a problem with incorrectly manufactured cable having 10k resistors.
STF_TimelessGoD said:
How were you going about reverse engineering the bootloader
Click to expand...
Click to collapse
I am using IDA Pro. I wish I also had hex-rays, but that is a little out of my budget.
vermiciouskanid666 said:
Doesn't usb-c spec call for a 56k resistor in the cable? I remember there being a problem with incorrectly manufactured cable having 10k resistors.
Click to expand...
Click to collapse
I think so, but I am not 100% clear on the USB C spec. I can confirm that there are no resistors at all inside the cable though.
The pinout has now been uploaded. Happy hunting.
By the way, if anyone has an Anyway box and fancies sending it to me, I would be deeply grateful. Progress is getting slowed by how expensive it is to get hold of all of these secret Samsung parts.
someone succed to make uart cable ?