does anyone know how to get the "/" symbol to work in terminal emulator? i tried softkeys, special keys. No luck. Im so close to installing modaco 4.0.0.9
for the final step i need the "/" symbol. i can use the "\" symbol but that's not the right symbol. please help.
Honestly you guys, I do search alot before I post anything. I never thought to use the on screen keyboard. I found out how.. I've been on this site for days and days researching, everything. I always use the hardware keyboard. Never the on screen keyboard. (sighs...sorry)
[email protected] said:
Honestly you guys, I do search alot before I post anything. I never thought to use the on screen keyboard. I found out how.. I've been on this site for days and days researching, everything. I always use the hardware keyboard. Never the on screen keyboard. (sighs...sorry)
Click to expand...
Click to collapse
Yeah, it is a bit of a pisser that key doesn't work correctly in terminals.
http://forum.xda-developers.com/showpost.php?p=17724216&postcount=5
Lol. I did get it to flash modaco tho. Just finished back up with Titanium. Hopefully now i should be able to flash a rom. O ya... When im in Hboot the screen will tell me no image..no image.. no image..no image. It will auto run this in green all the way down the screen. Why?
[email protected] said:
Lol. I did get it to flash modaco tho. Just finished back up with Titanium. Hopefully now i should be able to flash a rom. O ya... When im in Hboot the screen will tell me no image..no image.. no image..no image. It will auto run this in green all the way down the screen. Why?
Click to expand...
Click to collapse
All hboots do that. My g2 does that and my wifes MT4G as well.
Sent from my Undeadk9's Senseless ROM using xda premium
Undeadk9... what an honer to reply to you. I've read all your posts. I wanna flash your latest Senseless..Sounds fast. I myself would like to thank you for all the hard work you put into this forum. You do a wonderful job. Your posts and comments mean alot. I'm such a noob but love phones and cpu's. I really would love to fluently learn how to do anything that involves those things,but have no idea where to begin. What would you suggest I learn? I ask because you know what your talking about. Do you mind if i contact you in a pm or something just to bleed your brain sometime? Think about it. Thanks again!!
The problem is the question mark key.
Check all your other alt keys in terminal emulator - they all work except for the darned question mark key - both regular and alt read as a tilde.
I guess that having the question mark as a hardware key is something that terminal emulators aren't coded for...very few phones have that actual hardware key.
I got a feeling that if you remap the alt character to another key it'll work - it may or may not, but that's where i'd start.
This is one of those "I should look into that" but haven't found the time to do so, maybe check the keylayout mod guide in the dev section to start tinkering with it.
It's on my long list of things to do with this phone, my recent obsession with trying to overclock without kernel source kinda pushed everything else to the side.
Someone will probably get around to this before I do, but if not sooner or later i'll puzzle it out.
Thanx buddy for the reply!! My obsession is this forum... and my daughter of course
I hope you figure out the OC as well! Boy I wish I could help but I don't know how to. Where do you think I should start? Where should a noob begin to learn how to do anything...o_0 lol
You're honestly in the best place to start. XDA is home to some...thinking about it i'd say most... of the people online across all the random messageboards, news postings and whatnot who are all into the same thing and realize that by sharing what we know we can all work on bits and pieces of the larger picture.
Ever since I found XDA, I realized this was the place I was always looking for on the internet. Some of the most learned and skilled people i've met across the internet are scattered around these forums, and I found their works here.
The best advice to anyone new coming to XDA or trying to learn here, specifically, is that since so many people share so much, it's absolutely overwhelming the first time you wander around the XDA forums.
Use the search feature, as everyone rightly suggests, but the one thing that people never get right is managing their excitement.
You're home, you found the place where there are so many answers to and relating to your question, you get giddy. I know I did.
Resist the urge to just dive in and start asking questions. Put away your need to have the answer right now - I know it's just your nature, it's the tendency of people...any people...to just act like that. It's how we've progressed as a species, the aggresive need to know, solve, conquer...right this second.
That's wrong. When I found XDA, I browsed here for a while...sometimes for specific answers, other times just randomly through all the forums looking at...well...whatever random stuff I could find.
The thing about search is, it's great if you want a specific answer, because you keep finding more keywords and phrases to track down that will eventually lead you to the information you seek.
If you can't find the answer here at XDA, your quest to find it on your own without asking will turn up the people you could ask to help figure it out - something you miss just asking for it or exclusively using search.
Basically, just don't be too eager. The boards are way too big, populated by people that want to share what they know, so the amount of information here is too much to get through in one sitting. The first time I found this place I didn't leave my keyboard for more then a few minutes for almost 6 days.
I registered because I finally had something that I could share. My first device was the Nook Color, and by the time I got one the forums were jumping and so many choices for what you could do and how to do it were there ... it was my first android device and development was progressing so fast I couldn't keep up with learning it all from the ground up.
I stopped and focused on some topic I could expand on or in some way contribute, and it ended up being pretty in depth testing on MicroSD cards. I had a handful laying around, and running the Nook Color from the memory card instead of the internal memory will pass or fail depending on the memory card...and the one you instinctively want is wrong.
So, use the search function before posting something specific, don't forget to browse sometimes if you have some free time, it's like treasure hunting.
When I realized what this device ( MT4GS ) was capable of after coming to the MT4GS forums here to research if I really did want it or not...the TV-OUT thread was my seller. I am spellbound by this device, there's nothing else like it on the market at the moment.
I just couldn't miss out on playing with what I think will be the prototype model of what all phones will strive to do as technologies get assimilated across phones and carriers.
Being able to walk up to a TV and use the phone as not only an interactive game controller, but the console itself as well - with the TV bit being done so well that it's something you don't even have to think about other then if you want to or not. No special set up, just plug and play. I'm a fan.
But you know what? It's an unlisted feature that's rumored/probably true/unfinished in the phone.
( haven't looked into this in a while, maybe untrue but I found out about it here at XDA and remember reading that somewhere...every T-mobile rep i've seen has this phone, I talk to every one, and not a single one of them knew they could plug their device into a TV, let alone have some intense gaming experiences.
Not bad for something that's not mentioned - this should have been the selling point for the phone.
Thing is, without XDA, I wouldn't know how to do a fraction of what I know how to do with Android. Just sifting through everything here has taught me so much, but you have to have the patience to sit and take your time learning. Otherwise, even if you pull it off, six months from now you'll have to probably start over tracking down what you read before to do it again.
The more detailed and accurate the information that everyone posts, the more we all learn together.
Know what the big secret is, that I try to tell everyone?
The best way to cement the knowledge you've gained into your brain is to try to teach it to someone else. They'll think of questions you might never, approach from different perspectives with different tactics, and challenge you to know it well enough to be able to answer something you haven't thought about before on the spot.
I've been studying my whole life to be a teacher when I get older and can't hack physical stuff anymore, and try to freely teach anyone anything I know. The more I educate others, the more they educate me, and the more instinctively I know whatever we were working on.
Let me reiterate, again from a different perspective with different reasoning, the only way you learn something is to have the patience to do it - but the same goes for teaching. You have to have the patience to sit there and let the student get the answer, and the restraint to not give it to them and make them work for it so they remember it longer.
Analogies are king in getting through to people, but to be able to use analogies effectively for random people you have to be at least semi-educated on, well, everything.
Take a job in a retail store, any local big box popular electronics store. Sell computers, smart phones, or things like that. Then try to relate how the computer works to everyone you explain it to. Once you know some subject they are familiar with that you know, you can compare like functions to give them understandings.
Do yourself a favor - the next time you go to sit down in front of a television, pick up a book instead. (bonus points if you also grab a thesaurus)
Vocabulary and the contents of the thesaurus are the primary tools you need to use well for search. Forget all the ways a search engine works for you and remember that you need to not only search what you're looking for, but all the other ways of saying or describing what you want.
If you search fire, you get one set of results. What about ember, blaze, smolder, incinerate, char, smoke, fuel, tinder...etc...
If you have to look up all those synonyms every time you want to search for something, not only does it take longer (impatience again) but you are less likely to actually do it because of all the extra steps you have to take.
Phrase your posts well, try to punctualize, capitalize, and generally make what you're saying presentable. It takes me longer to decipher some internet shorthand, because they aren't acronyms I study. It hurts me on messageboards, but helps keep my vocabulary instinctively clean elsewhere.
On that turn, i'm more likely to read and/or respond to someone who actually took enough time to write their post, instead of just scratching out the first string of letters that looked close to some resemblance of the words they were trying to write.
( I know that's extreme, but that's another teaching tool, exploring extremes and understanding boundaries and capability - the foundation for your ability to reason )
So, you caught me at a time where i'm writing a curriculum for learning how to learn, techniques and approaches and such for someone I am going to start teaching android to. As much as it seems like i'm rambling here, all my postings tonight have been sprinkled with little methods or things to do to increase your speed, accuracy and ability to learn itself because that's what i'm working on right this minute.
It's been a long, hard, physical week at work. While rewarding and I feel great about what i've done, my body is not so happy at the moment. Trying to get into a new project with my MT4GS tonight is probably pushing it, so instead i'm just sitting here writing up what i've learned about learning, typing to me is very relaxing and keeps me active in spirit while mostly resting in the physical sense.
This is why they say knowledge is power, because you have to build knowledge on other knowledge. The more you understand and exploit the learning process to work for you, consciously and directly, the more natural and fluid it becomes.
If you learn what you need to learn to learn better (say that 3 times fast) you will become more efficient - and that's part of why we all get together here to do this stuff to our phones.
It's challenging, it's fun, it's a never-ending exercise in discovering cool new things or flat out creating brand new ideas of your own.
Part of what's been feeding my excitement with this phone, besides it's indisputable awesomeness, is the fact that it's new and there's an air of freshness to all the time being put into it. It's not like my last device where I showed up and found all the answers, this time I get to find and share some of them.
But that's the constant state of learning, the browsing all over XDA, setting up specific projects (tonight i'll learn how to make a livewallpaper, etc...) and creating manageable, short term goals along the road to a bigger destination.
The destination is reached much more interestingly with others, and when we all get there it's one big party together. This goal is made easier and sooner the more people that play.
Another thing is, I try to share what I post as thoroughly and accurately as possible. 2 Great reasons to take an extra minute and check something, or look it up again to make sure that it's right.
1-Someone else can build off your solid base, and spend less time learning what you were trying to convey
2-If i'm wrong, someone will speak up. There are so many learned people here, someone will see what I did wrong and if not why, someone else can probably explain it or get us started on finding out why.
So please, don't hesitate to correct me on something if you know i'm wrong. we all benefit from it, and is part of the motivation to be as thorough as I try to be.
Hope that the length of this post is justified by the content I tried to convey, you caught me in a typing mood with an open-ended question.
Blue6IX said:
You're honestly in the best place to start. XDA is home to some...thinking about it i'd say most... of the people online across all the random messageboards, news postings and whatnot who are all into the same thing and realize that by sharing what we know we can all work on bits and pieces of the larger picture.
Ever since I found XDA, I realized this was the place I was always looking for on the internet. Some of the most learned and skilled people i've met across the internet are scattered around these forums, and I found their works here.
The best advice to anyone new coming to XDA or trying to learn here, specifically, is that since so many people share so much, it's absolutely overwhelming the first time you wander around the XDA forums.
Use the search feature, as everyone rightly suggests, but the one thing that people never get right is managing their excitement.
You're home, you found the place where there are so many answers to and relating to your question, you get giddy. I know I did.
Resist the urge to just dive in and start asking questions. Put away your need to have the answer right now - I know it's just your nature, it's the tendency of people...any people...to just act like that. It's how we've progressed as a species, the aggresive need to know, solve, conquer...right this second.
That's wrong. When I found XDA, I browsed here for a while...sometimes for specific answers, other times just randomly through all the forums looking at...well...whatever random stuff I could find.
The thing about search is, it's great if you want a specific answer, because you keep finding more keywords and phrases to track down that will eventually lead you to the information you seek.
If you can't find the answer here at XDA, your quest to find it on your own without asking will turn up the people you could ask to help figure it out - something you miss just asking for it or exclusively using search.
Basically, just don't be too eager. The boards are way too big, populated by people that want to share what they know, so the amount of information here is too much to get through in one sitting. The first time I found this place I didn't leave my keyboard for more then a few minutes for almost 6 days.
I registered because I finally had something that I could share. My first device was the Nook Color, and by the time I got one the forums were jumping and so many choices for what you could do and how to do it were there ... it was my first android device and development was progressing so fast I couldn't keep up with learning it all from the ground up.
I stopped and focused on some topic I could expand on or in some way contribute, and it ended up being pretty in depth testing on MicroSD cards. I had a handful laying around, and running the Nook Color from the memory card instead of the internal memory will pass or fail depending on the memory card...and the one you instinctively want is wrong.
So, use the search function before posting something specific, don't forget to browse sometimes if you have some free time, it's like treasure hunting.
When I realized what this device ( MT4GS ) was capable of after coming to the MT4GS forums here to research if I really did want it or not...the TV-OUT thread was my seller. I am spellbound by this device, there's nothing else like it on the market at the moment.
I just couldn't miss out on playing with what I think will be the prototype model of what all phones will strive to do as technologies get assimilated across phones and carriers.
Being able to walk up to a TV and use the phone as not only an interactive game controller, but the console itself as well - with the TV bit being done so well that it's something you don't even have to think about other then if you want to or not. No special set up, just plug and play. I'm a fan.
But you know what? It's an unlisted feature that's rumored/probably true/unfinished in the phone.
( haven't looked into this in a while, maybe untrue but I found out about it here at XDA and remember reading that somewhere...every T-mobile rep i've seen has this phone, I talk to every one, and not a single one of them knew they could plug their device into a TV, let alone have some intense gaming experiences.
Not bad for something that's not mentioned - this should have been the selling point for the phone.
Thing is, without XDA, I wouldn't know how to do a fraction of what I know how to do with Android. Just sifting through everything here has taught me so much, but you have to have the patience to sit and take your time learning. Otherwise, even if you pull it off, six months from now you'll have to probably start over tracking down what you read before to do it again.
The more detailed and accurate the information that everyone posts, the more we all learn together.
Know what the big secret is, that I try to tell everyone?
The best way to cement the knowledge you've gained into your brain is to try to teach it to someone else. They'll think of questions you might never, approach from different perspectives with different tactics, and challenge you to know it well enough to be able to answer something you haven't thought about before on the spot.
I've been studying my whole life to be a teacher when I get older and can't hack physical stuff anymore, and try to freely teach anyone anything I know. The more I educate others, the more they educate me, and the more instinctively I know whatever we were working on.
Let me reiterate, again from a different perspective with different reasoning, the only way you learn something is to have the patience to do it - but the same goes for teaching. You have to have the patience to sit there and let the student get the answer, and the restraint to not give it to them and make them work for it so they remember it longer.
Analogies are king in getting through to people, but to be able to use analogies effectively for random people you have to be at least semi-educated on, well, everything.
Take a job in a retail store, any local big box popular electronics store. Sell computers, smart phones, or things like that. Then try to relate how the computer works to everyone you explain it to. Once you know some subject they are familiar with that you know, you can compare like functions to give them understandings.
Do yourself a favor - the next time you go to sit down in front of a television, pick up a book instead. (bonus points if you also grab a thesaurus)
Vocabulary and the contents of the thesaurus are the primary tools you need to use well for search. Forget all the ways a search engine works for you and remember that you need to not only search what you're looking for, but all the other ways of saying or describing what you want.
If you search fire, you get one set of results. What about ember, blaze, smolder, incinerate, char, smoke, fuel, tinder...etc...
If you have to look up all those synonyms every time you want to search for something, not only does it take longer (impatience again) but you are less likely to actually do it because of all the extra steps you have to take.
Phrase your posts well, try to punctualize, capitalize, and generally make what you're saying presentable. It takes me longer to decipher some internet shorthand, because they aren't acronyms I study. It hurts me on messageboards, but helps keep my vocabulary instinctively clean elsewhere.
On that turn, i'm more likely to read and/or respond to someone who actually took enough time to write their post, instead of just scratching out the first string of letters that looked close to some resemblance of the words they were trying to write.
( I know that's extreme, but that's another teaching tool, exploring extremes and understanding boundaries and capability - the foundation for your ability to reason )
So, you caught me at a time where i'm writing a curriculum for learning how to learn, techniques and approaches and such for someone I am going to start teaching android to. As much as it seems like i'm rambling here, all my postings tonight have been sprinkled with little methods or things to do to increase your speed, accuracy and ability to learn itself because that's what i'm working on right this minute.
It's been a long, hard, physical week at work. While rewarding and I feel great about what i've done, my body is not so happy at the moment. Trying to get into a new project with my MT4GS tonight is probably pushing it, so instead i'm just sitting here writing up what i've learned about learning, typing to me is very relaxing and keeps me active in spirit while mostly resting in the physical sense.
This is why they say knowledge is power, because you have to build knowledge on other knowledge. The more you understand and exploit the learning process to work for you, consciously and directly, the more natural and fluid it becomes.
If you learn what you need to learn to learn better (say that 3 times fast) you will become more efficient - and that's part of why we all get together here to do this stuff to our phones.
It's challenging, it's fun, it's a never-ending exercise in discovering cool new things or flat out creating brand new ideas of your own.
Part of what's been feeding my excitement with this phone, besides it's indisputable awesomeness, is the fact that it's new and there's an air of freshness to all the time being put into it. It's not like my last device where I showed up and found all the answers, this time I get to find and share some of them.
But that's the constant state of learning, the browsing all over XDA, setting up specific projects (tonight i'll learn how to make a livewallpaper, etc...) and creating manageable, short term goals along the road to a bigger destination.
The destination is reached much more interestingly with others, and when we all get there it's one big party together. This goal is made easier and sooner the more people that play.
Another thing is, I try to share what I post as thoroughly and accurately as possible. 2 Great reasons to take an extra minute and check something, or look it up again to make sure that it's right.
1-Someone else can build off your solid base, and spend less time learning what you were trying to convey
2-If i'm wrong, someone will speak up. There are so many learned people here, someone will see what I did wrong and if not why, someone else can probably explain it or get us started on finding out why.
So please, don't hesitate to correct me on something if you know i'm wrong. we all benefit from it, and is part of the motivation to be as thorough as I try to be.
Hope that the length of this post is justified by the content I tried to convey, you caught me in a typing mood with an open-ended question.
Click to expand...
Click to collapse
You are king of long statements.
Sent from my Undeadk9's Senseless ROM using xda premium
[email protected] said:
Undeadk9... what an honer to reply to you. I've read all your posts. I wanna flash your latest Senseless..Sounds fast. I myself would like to thank you for all the hard work you put into this forum. You do a wonderful job. Your posts and comments mean alot. I'm such a noob but love phones and cpu's. I really would love to fluently learn how to do anything that involves those things,but have no idea where to begin. What would you suggest I learn? I ask because you know what your talking about. Do you mind if i contact you in a pm or something just to bleed your brain sometime? Think about it. Thanks again!!
Click to expand...
Click to collapse
Honor? Im just an every day joe with ubuntu 11.04 and rom kitchen sprinkled with java on my laptop. that also makes roms. Lol.
Sent from my Undeadk9's Senseless ROM using xda premium
The only way I got around not being able to type the / character on my mt4gs keyboard in the terminal emulator when I flashed modaco was to type out the command line in a text message, copy, then paste in the emulator. Works like a charm.
Sent from my Xoom using xda premium
Bravo Blue6lX. That was very well written. Amazing. I personally can relate to a majority of what you spoke of in this post,my favorite being,"the one thing that people never get right is managing their excitement". I am a poster boy for that very same thing. Even in the real world I struggle with that. I have to take a second to breath,lol. When I signed on to this forum I read the rules and began my quest to further educate myself in Android... baby crying gotta run thanks again your posts are very inspiring! I enjoy reading them very much, your a wise man. Thesaurus on the list for the day!! Have a great day
[email protected] said:
Bravo Blue6lX. That was very well written. Amazing. I personally can relate to a majority of what you spoke of in this post,my favorite being,"the one thing that people never get right is managing their excitement". I am a poster boy for that very same thing. Even in the real world I struggle with that. I have to take a second to breath,lol. When I signed on to this forum I read the rules and began my quest to further educate myself in Android... baby crying gotta run thanks again your posts are very inspiring! I enjoy reading them very much, your a wise man. Thesaurus on the list for the day!! Have a great day
Click to expand...
Click to collapse
Glad you got what I was trying to say. Looking back at it now that i've slept, showered, and got a pot of coffee in me i'd have written that a lot differently. I passed out right after posting that, when I got home I was so physically exhausted...yet too mentally awake to sleep. Normally i'd just browse around learning stuff on the computer and be rested, but I really needed to actually sleep.
I figure as long as I make sure anything I post in the developers section is as concise and clear as I can make it, what gets posted in these other sections can be a bit more general, but that posting was a bit convoluted even by my standards.
Not to drag your thread too far away from the original question, but once you free yourself from the "answer right now" impulse, XDA has several lifetimes worth of stuff to learn how to do just sitting here waiting for you to discover it.
The best way to get started is to just pick something, something small, and learn how to do it completely. Then go on from there. The other day I wanted to spend like a half an hour getting some icons...but one thing led to another which led to photoshop and a few hours later I had a new boot animation for my device I made from scratch.
It's not what I came here to do or to learn, wasn't even in my head when I sat down at the computer. But, I let myself just wander and followed the direction my interest evolved in and that's where I ended up. Sometimes that's the way it goes, and it was a fun experience.
You lose the opportunity for something like that to happen when you just ask a question and get spoon-fed an answer. I'm a big fan of the idea that if you really want to get something done, then just do it yourself. Why sit and wait for someone else to do it, while you could be spending that time doing it yourself. You need knowledge to be able to do that, though, and that's what XDA is a place to share.
The more quickly and completely you can process and assimilate the knowledge, the more you can learn in a shorter time with less frustration. It really pays to take the time to develop good habits and methods for learning.
The answer to whatever you want to know in most cases is not nearly as worthwhile as knowing how to figure out that answer.
Sometimes you just need a quick solution to fix something broken, the HTCLoggers security vulnerability is a great example of a valid "need a fix now" situation. Much thanks to undeadk9 for a quick resolution to that issue.
...but if it's not mission critical to do whatever it is right this second, why rush?
The easier you come by the answer, the easier you forget it.
That's why knowing how other related activities can help you across the spectrum of things you get involved in is important. Reading is a great example.
If you read books by a variety of authors, you pick up different ways of saying the same thing, are exposed to different words and so on. When you sit down to search for something, you now have many more avenues to travel in the breadth of keywords and phrases to use before hitting a dictionary or thesaurus or something. Consciously encouraging that fringe benefit of the activity of reading compounds it's effectiveness, because you will intentionally seek out authors that write differently then each other and maximize your gain for time invested.
Back to the subject at hand, the issue with terminal emulator. There are a couple of threads about this issue right here in the MT4GS section of XDA. If you browse through them, you will find different pieces of the puzzle sitting there.
Furthermore, you'll find people who have tested different terminal emulators, so you can ask them what they've found, or encourage them to share their findings to add information to the issue. You'll also find the other people interested in solving the problem, so sooner or later the right combination of people with the motivation, skills, and time to invest will come together in a thread and generate a solution.
...and that's why I love the open source community mindset of XDA. The gratification of "hey, look what I found!" is here, because it's all worthwhile. The puzzle isn't put together until we have all the pieces, and each one that is found and shared is one less to find. For the community as a whole, what you've found is just as important as how you share it.
Some people are great at figuring out what the puzzle pieces are. Others are great at creating those pieces. Other people shine at putting those pieces together to finish the picture. All those talents are expressed to some degree by the people coming through here, this place is amazing.
Now consider, if you just ask a question and get an answer, well, that's great for you or anyone with that exact problem. But for other people in the future trying to figure out that problem, that may not be so helpful.
What if someone comes through with the same problem, but a new firmware version or something where the solution doesn't work anymore. Generally speaking, the method used to find that solution would work again to generate a new, updated answer, but since only the answer and not the method was given...
So the "need it now" attitude really just impairs everyone's ability to move forward past a certain point, because then it gets into people asking questions that have already been answered...sometimes on that very page in the forum...because they didn't take a minute to see if the question had already been fielded and resolved.
I know XDA is huge and can be overwhelming, but having been with the MT4GS since there weren't many posts in this section of XDA, I already see it happening here too. It's just human nature, and some people don't even realize it.
So i'll leave it there, since you were asking about how to get the most out of using XDA, and this is just something i've observed in my time here.
"The answer to whatever you want to know in most cases is not nearly as worthwhile as knowing how to figure out that answer".
"The easier you come by the answer, the easier you forget it".
"So the "need it now" attitude really just impairs everyone's ability to move forward past a certain point".
Your a great teacher Blue6lx! I read your comments that you posted on this page more than a few times. I would have replied sooner if my daughter would've let me
I would like to know more of anything you want to say,so I'll be hearing from you! One way or another!
I ended up sliding the keyboard in and out for that since I am able to use the onscreen keyboard to use the "/". I Slide out for faster typing for everything else.
[email protected] said:
I ended up sliding the keyboard in and out for that since I am able to use the onscreen keyboard to use the / Slide out for faster typing,on screen for"/"
Click to expand...
Click to collapse
While that works, it's an ugly solution. Don't worry, it's what I do too.
I remember reading a while ago here...someone swung by and asked if there had been any problems with the cable that carries the information from the keyboard half of the phone to the screen half.
Sliding in and out wears that cable out over time, and while it's way too early to see any issues arising from that cable wearing out yet because of how new the phone is, it's something to keep in mind.
It's a moving part, a piece of metal that bends (the wiring) when it's slid up and down. Even though it's designed to do it, from everything i've ever learned about physics and metal fatigue I know it'll wear out one day if the phone lasts that long.
I don't mind using it, it was made to take some amount of sliding, but as a developer using the phone in ways it wasn't exactly intended for, you have to be aware of the ways you create additional stresses on the device.
Do you think a normal user slides the phone out as much in a whole weeks worth of playing with it the amount of time you do in a single day working with terminal emulator?
Everything (except the stock battery) about this phone is pretty top of the line, I highly doubt that HTC cheaped out on a part they knew would wear out eventually on it's own, so don't think you're gonna break your cable tomorrow because you slid the keyboard out.
Just be aware of the above-normal stresses you can put on your device over the long term once you become more then a consumer-grade user.
So, yes, it's a solution, but not very elegant in it's execution.
My thoughts are the same. "Ugly solution".
From what I have observed, the text savvy user loves sliding that keyboard in and out. I have no doubt they realize this and built it to last... Let's hope they did not skimp in that area of their development
No one has said it. Try swype. I've used it a few times to get some unresponsive or jumbled as in getting ~ instead / to work or a pesky capital to stay lower case as in I and i .
Sent from my MyTouch 4G Slide using xda premium
As I am working my way through the public transportation circuit back to my dev chair, I have a chance to ask for help if someone(s) are interested in helping the doubleshot development effort at large.
Development in the open source community is about two main points:
1. Being driven by your curiosity to learn something new or make something do whatever it does differently or better.
2. Distributing the workload of what we want or need between multiple people - many hands make light work and if everyone contributes something small collectively it turns into a whole lot of progress and success.
So here's something that would help us all out immensely even though it seems like a small issue on the surface:
.nb0 and .nbh files - how to break them down and an explanation of how exactly they work.
What they are is a proprietary format used to wrap up some of the installer files within OTA and software updates we get from HTC for this device. (Other HTC devices too)
We also need to have or have links to the software we need to break them down with.
This information and how to use it will make a tremendous difference in how quickly and effectively we can assimilate and process our official software updates and continue to deliver both S-OFF and Root solutions when they are stripped from us on OTA pushes.
I'm making too much progress on other fronts and with other issues to stop and take care of this, and the very limited searching I've been willing to spare on this front has lead to dead ends and dead (mostly megaupload) links to what we would need.
Honestly, I've got a lot of dev work I've gotten myself involved in with this device and the progress I make doing other stuff is greater then putting more time into this, based on the project files I have in process. If I was just starting with helping out on doubleshot development this would be what I would be spending time on - just where I'm at I lose momentum focusing on this.
I get PM's from people asking for advice or direction on how to help out in addition to a scattering of threads around here started by people with lot's of enthusiasm but no direction, and I definitely understand! I've been and (believe it or not) continue to be in that very same position!
Sometimes all people need is a nudge in a direction, a path pointed out to them that they can explore and learn about - this is just such a signpost on the way to becoming the developer some of you out there want to be.
Development basically = knowledge + implementation, and the more you know the more creatively you can leverage it to your advantage. We certainly have some creative people who have passed through or are here now surprising us every day.
From the impressively out of nowhere CM7 port kornyone gifted us with in the past to the jaw-dropping brute-force ICS work tbalden blazed a trail into ( and sucked a few people into along the way ) all the way down to the work XMC has been steadily chipping away at building tools for us to use and wrap it all together with - we really have some talent, passion and a lot of success in our small but effective corner of the XDA forums.
...and those are only a few of the people who have made a lot happen around here, there are and certainly have been others who have either left a mark on development for this device or continue to do so.
Excited? I am! There's so much cool stuff to do and who cares if we never get an 'official' ICS update? We (collectively) are producing software the manufacturers/carriers wish they could produce in a fraction of the time it would take them to do so.
What some may not realize, though, is that it isn't this person or that person making it happen, but the collective efforts of us all together that enhance and compliment the individual strengths we all bring to the table separately.
...and it's all built on us sharing what we know and helping each other out. Maybe some out there, especially the more casual viewers or unregistered lurkers don't realize just how much we work together - where the larger sub-forums are more scattered and individualized just because of their population.
As an aspiring dev, this should make our little corner even more appealing because that leaves a lot more new ground to cover and gives everyone who jumps in that much more of an impact on what we have available.
Maybe in other places you're the fiftieth person to make some lockring or point something out, but over here just about anything you get into is new ground for us - so we are definitely excited about everything anyone has to offer, no matter how trivial it may seem to you.
As many of you have gathered by now I'm a bit long winded at times, but it's all so exciting!
So back to the original point, which was that if someone or a handful of someone's wanted to do something to help out, and push development for the device forward but wasn't sure what to do, figuring out how those .nb0 and .nbh files work and finding some software to crack them open with would be a big help in gaining and maintaining S-OFF and Root for this device.
.nb0 files especially, because they are something within the OTA that is a single file that impacts multiple partitions, and we really haven't gotten a look inside of them at what exactly they are doing to our device and how.
The death of megaupload and sites like it cost the open source community a lot of tools that are in some cases still missing and in others maybe never to be replaced...at least not without someone taking the time to sit down and do so.
...could that be you?
gtmaster303 said:
Sorry blue, I got lost in your post. What exactly are you looking for?
A software that can do what with these files?
Click to expand...
Click to collapse
Cliff notes:
Blue6IX said:
The strength of XDA is the community itself and the knowledge it contains. If we want to truly leverage it here in the doubleshot forums, this is how it can be utilized the best.
Click to expand...
Click to collapse
Any and all info on the .nb0 or .nbh file format, anything people can gather.
How do we break them apart?
What is inside of them when we do?
What partitions does it flash it's pieces to, are the individual pieces signed or just the file itself?
Can we make these files?
...How?
.nb0 is inside the OTA packages, .nbh is a type of package like the PG59IMG.zip files, so the tools to work with them are different?
Here is an .nbh thread that could help get someone started...
NBHextract: Extract contents from NBH files with a tool but we don't have any of these files yet?
Here is the wiki page it links to which will help more:
NBH wiki page that it links to on that tool page which might help some more.
I bring up .nbh because that is one of the methods of insertion the auto-install tries to use when booting to hboot:
Blue6IX said:
When loading hboot, the files it automatically looks for on the sdcard are:
- PG59DIAG.zip
- PG59DIAG.nbh
- PG59IMG.zip
- PG59IMG.nbh
- PG59IMG.tar
- PG59IMG.aes
- PG59IMG.enc
Click to expand...
Click to collapse
...and the more people we have familiar with these files and spend time helping us to figure them out, the better equipped we will be to deal with new OTA packages and everything that goes with them.
What do we know? Collectively, here, not very much - if so, someone speak up and if not here's something people can help with.
How do we make .nbh files, or any of the other packages quoted there we don't have?
We've pretty thoroughly examined PG59IMG.zip files but the .nb0 files in them are still somewhat of a mystery - here are the ones from the 3 PG59IMG.zip files you can find links to here:
Restore to Stock
Files:
doubleshot_1-28-531-9_nb0.zip
Download Link
MD5: d5e8721090dbc048c711d7f42404286b
Size: 1.75 MB
doubleshot_1-55-531-3_nb0.zip
Download Link
MD5: dba1925982b4c5e0a41f3291942e09e0
Size: 1.75 MB
doubleshot_1-63-531-2_nb0.zip
Download Link
MD5: aaa9edc7b2c5ec91559ab01caebab8ac
Size: 1.75 MB
These zip files are in uncompressed form, simply zipped in store - small files but 2 each. Here you go, hope someone has fun with them!
Sent from a digital distance.
http://www.ubiquitense.com/technology/how-to-install-android-roms-with-nb0-file-extension/2800/
dont know if this is what you are looking for but maybe........
i think this is better?
http://android-dls.com/wiki/index.php?title=How_to_unpack_and_repack_NB0_file
tl;dr:
Blue is a noob with poor time management skills.
jk, I would love to see more people get involved with development. You can't really ***** about a lack of development and then not be willing to support it.
Sorry blue, I got lost in your post. What exactly are you looking for?
A software that can do what with these files?
Usually, all unknown file types I come across I run through winrar and see how it handles it.
Found this with a quick google:
http://filext.com/file-extension/NB0
I edited the first post, adding the second half to it starting with the quote below:
gtmaster303 said:
Sorry blue, I got lost in your post. What exactly are you looking for?
A software that can do what with these files?
Click to expand...
Click to collapse
As evidenced by my original posting, being concise is not my strong suit.
I posted that from the doubleshot while I was sitting somewhere waiting for people, and so it was a little all over the place even for me. Hope this post and the edits above clarify the intentions of this thread better?
Can someone explain how to break down the nb0 files and find tools to do it properly? See if you can sit down and crack one open and see what's inside.
See how many of the questions can be answered from above, and what other ones we don't know enough to ask are/their answer(s) are?
The doubleshot community benefits from it's developers having how-to references on the things we need to do, and pretty much everything we need to know is scattered all over XDA.
It takes time to funnel, qualify, and share that information here so we can use it.
Many more people will be able to dev for this device if they can come here and learn how to do it, and not have to resort to the XDA scavenger hunt that every other dev who started here had to go through.
If other people can see the value of and want to help out in searching out how to do things and get it here for us to use, the honest truth is that's a resource built by the developers here or not at all.
Learning how to do things and going through that experience and what the pitfalls are and finding where to get what you need to do it is basically development.
Sharing those experiences with XDA is what makes this community a resource.
Bringing it here gives people who want to dev and don't know where to start a learning project that can benefit everyone working here.
Something like this is a good trial for posing this question - there are a lot of things that we would benefit from having here and not just on XDA at large. If someone or people want to get together and solve this mystery because they were looking for a problem to solve, then here is the best way to turn that learning experience into a guide for the rest of us.
...and we can check that off our list of things we need to learn how to do.
I can make a post at some point with a concise listing of things we need to know about, with a link to a summary of what we know about each, and then we could use it as a checklist to start systematically solving our problems and making the device do what we need to do.
The strength of XDA is the community itself and the knowledge it contains. If we want to truly leverage it here in the doubleshot forums, this is how it can be utilized the best.
--------
So, when someone gets so energized by this as many of us have felt at some point - that overwhelming desire to help but complete confusion on where to start?
Go learn something we don't know and share how to do it or what it is here. We all benefit and people already here working on other things can just add how to do whatever that is to their methods.
Please don't think this is a case of me sitting here saying "i'm too lazy to learn how to do this, someone teach me" ...
...this is a case of "does anyone out there want to help explain what this is and how to use it? Here's a project if anyone wants it" ...
...i've written quite a few guides here as i've learned how to do things, and wouldn't pose this kind of question without having contributed first. So just offering a starting point to anyone else willing to do that too.
If there is interest in people taking the project on, I can make a checklist of what we need to know and we can have a point of reference on how to spend our time when looking for projects to do.
If no one's interested in learning this and sharing it here then I won't waste the time it would take to put such a list together and source everything. Eventually i'll figure this out and share it here if no one does, but we would grow as a community for others to do it. Just looking for ways to make everything work more smoothly here.
This place is whatever we make it to be, so do we want this?
You think it would help if we asked HTC dev what they're for?
I would love to help! But I don't know anything about being a Dev.
Hi Blue6IX,
I've read most of your post, but I don't quite understand to what purpose we need the contents of these files.
I mean, I got my Doubleshot, rooted/S-OFF'ed it with revolutionary/unrevoked and SIM unlocked it following this guide and installed an ICS ROM. Is there anything that prevents others from doing the same?
Also, I come from the Moto Milestone, which has a locked bootloader and no way to unlock, and still people managed to get ICS up and running (with 2.2 being the latest version Motorola wanted us to have on the device).
For the Doubleshot, you can just fire up a repo sync with CM9, get the preliminary msm8660 device tree(s) and create a doubleshot device tree. I know it will require some adaptations and coding, but IMHO this is nowhere near the problems other devices face.
Since I didn't really find any information on other hindrances, I would be glad to hear of them. Otherwise, I don't think analyzing HTC's/T-Mobile's original update files will be useful for anything?
Curiously yours,
Stefan
seidler2547 said:
...
I mean, I got my Doubleshot, rooted/S-OFF'ed it with revolutionary/unrevoked and SIM unlocked it following this guide and installed an ICS ROM. Is there anything that prevents others from doing the same?
...
Click to expand...
Click to collapse
Yea - for a while S-OFF was impossible for any device on the 1.55.531.3 software version ( or later ) with hboot 1.45.0013
There was also a time where they couldn't unlock the device and were basically stuck barely able to root.
For most people, S-ON and unlocked is the best it can get at the moment - making it pain to flash roms with custom kernels and completely unable to go back to the stock radio or hboot.
seidler2547 said:
Hi Blue6IX,
I've read most of your post, but I don't quite understand to what purpose we need the contents of these files.
...
Otherwise, I don't think analyzing HTC's/T-Mobile's original update files will be useful for anything?
Curiously yours,
Stefan
Click to expand...
Click to collapse
I cut out most of the post you made ... ( quoting a whole post unnecessarily is rather annoying ) ... But you really answered your own question here.
Do you know for certain they won't help now or in the future?
Have you checked to see?
How can you check if you can't break it open?
If you can, could you share directions how and working links to tools to do it with?
...the OTA and PG59IMG.zip packages are how the manufacturer updates the device and makes changes to things we can't - knowing how they do it can help lead to a way for us to do it.
Especially since we don't have a proper RUU and basically are left begging for scraps at the "official" software table for the device - knowing how the few legitimate software packages work we get becomes even more important.
Every time an OTA update comes out, the possibility exists to lose root, S-OFF or even a working device ( the next broken update will NOT be the first ).
As you mentioned being curious, well, you hit the nail on the head as to the entire purpose of the thread.
I'm curious, anyone serious about helping us keep root at the very least is too ( and if not, now know they should be and a bit about why ).
It's one of many, many pieces to the puzzle, but the more thoroughly we understand each puzzle piece itself, the better of a chance we have at actually putting it together.
Bottom line is we don't know, we should know, and the project of finding out and sharing it here is a great opportunity for someone who wants to learn how to be a dev and has no clue where to start.
This project is on my list, but I figured i'd post it here and create an opportunity for anyone interested in it...otherwise I'll get to it at some point.
For all the time I've put in the thread, I probably could have made progress on the answers to at least some of the questions I've posed. I'd rather see if investing that time in soliciting more participation is worthwhile. It's not something I need, but rather something WE need...
Anyone like a good mystery?
Sent from a digital distance.
Ok, I mentioned in annother thread that I am willing to learn developing so our phone dosent die. I've rrun into a bit of a hiccup in that I'm compeletly new to programming and I've either gotten no response or a negative one when I went looking for pointers. Fear not I am still not giving up it is just going to take longer than expected. So in interest of keeping development moving forward I'm putting out a call to arms. Are there any other aspiring developers out there? If so post in this thread what you are good at and what you can do. Perhaps we can collaborate and push out a rom in the near future. Personally I am an expert at graphic manipulation and can handle all of the ui, still working on the coding part. For everyone else, post things you would like to see and perhaps one of us could pick it up and run with it. Let's work together and make this work better than they ever thought it could!
Sent from my SGH-T839 using XDA
Sigh..
We can't work together if you don't have experience with coding.
If you really want to get a spark, you need to get a promising build onto github. And, you will need experience and attention to detail. Nobody wants to help if you don't comment your code, keep good changelogs, and maintain a good readme.
So far, I don't see it out there.
Furthermore, I can't afford to spend hours working on something that won't pay my mortgage. Most of us can't.
If I hit the lottery, maybe I'm your guy. In the meantime, we can't work together without a leader.
And, let's hope the next developer isn't lacing every file with a bunch of jibber jabber about "don't kang my sh*t, bro." Because, a collaborative effort would require plenty of sharing.
Just my two cents.
I would love to see a new Sense rom. but this place seems dead. Coming from the G1 I was surprised to see barely any roms. Even though the G1 is a ancent phone, it had quite a bit of rom and there's more activity over there than there is activity over here.
Sent from my SGH-T839 using xda premium
orange808 said:
Sigh..
We can't work together if you don't have experience with coding.
If you really want to get a spark, you need to get a promising build onto github. And, you will need experience and attention to detail. Nobody wants to help if you don't comment your code, keep good changelogs, and maintain a good readme.
So far, I don't see it out there.
Furthermore, I can't afford to spend hours working on something that won't pay my mortgage. Most of us can't.
If I hit the lottery, maybe I'm your guy. In the meantime, we can't work together without a leader.
And, let's hope the next developer isn't lacing every file with a bunch of jibber jabber about "don't kang my sh*t, bro." Because, a collaborative effort would require plenty of sharing.
Just my two cents.
Click to expand...
Click to collapse
I appreciate your honesty. But you misunderstand my intentions. I am not looking for someone to hold my hand and walk me through how to do everything. I, at most, am looking for info on how to start. I know I need expirence in coding before I can push out a rom, and that it will take a while to get that. That's why I started this thread. So, instead of waiting for me to finish the learning process we can get any other aspiring developers together to start something new in the meantime. I know there are others out there and if we all start posting what we can do and what we would like to see then maybe something may come from it. Thank you for point me to github, I'm sure I can learn some more from there. I understand about responsibilities getting in the way of hobbies, I have kids and a mortgage too, I'm just looking to get all the new developers together so that we can share and work together. I have a friend that writes code for websites for a living and I'm trying to get him on board to take this up as a hobby. Here's hoping.
Sent from my SGH-T839 using XDA
NightmyreWreckage said:
There are only three devs left for the Sidekick.
HewettBR, me (JiN1337), and nxd (kernel developer)
Reactive was a guy who tried to get everyone banned for using open source work, and thus in turn got banned himself.
I would be welcomed to help teach you a bit. I wish I had a learning curve when I was just beginning how to cook ROMS.
1. Download a ROM, unzip it, browse around files, and open files. Play with things.
2. When in doubt, Google it. It's likely someone else had the same problem before you and is a basis on how I fix 80% of ROM problems.
3. Always, always make a NANDROID. A foolish mistake is to flash your own ROM and not have a backup to go to, and than you have to start all over.
Click to expand...
Click to collapse
Thanks. I have a stack of books on android as tall as my hip lol. I feel like I'm in college all over again. Any help would be appreciated at this point. I'm on information overload.
Sent from my SGH-T839 using XDA