Related
Unless someone knows why I keep getting these errors now.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sorry for the large imgs but I'm not able to shrink them on my iPad right now.
Zethmir said:
Unless someone knows why I keep getting these errors now.
Sorry for the large imgs but I'm not able to shrink them on my iPad right now.
Click to expand...
Click to collapse
If I was you and having these problems, the first thing I would do would be to run the RUU and get back to stock. Easiest way to find out if it's the Rom or the phone.
in ur settings to a factory reset
You are on a rooted phone and you are going to return it due to errors that might be a result of the root?
No root and I mean no ROOT is perfect and each phone can act differently. Try to reflash again and clear out all your data/cache and try it again.
Try another ROM just to see.
Yet another user error. This is YOUR fault. Heck they could report your to HTC if they didn't like you.
WoW just wow. You talk to me like I am the biggest noob on the forums.
For your information the root was fine for over 2 weeks and this just started last Friday. I had a launch evo and rooted it the first day it was available. Also I flashed back to stock ruu and had the same problem.
Maybe before you open your mouth and let the **** flow out ask yourself a simple question : Is my comment going to help or just make me look like an ass.
Also I would like to comment on the fact I am pretty good at phone jailbreaking and rooting. I know how to read guides and I have been doing this kind of stuff since the pocket pc's. I have never ran into a much ruder group then the people that posted on this topic. Heck even a rom dev talked to me nicer then you guys did when I asked about a project he hadn't worked on in months.
I have returned my EVO but haven't lost hope in you guys. Just let me know if you guys ever apply at my work so I can avoid you at all costs.
Note: This only applies to the ones that deserve it. Thanks for mentioning the stock RUU Roman G, and for mentioning the factory reset toenail78. I had already tried that but to no avail. Also note I even told the store I rooted the phone and flashed it back to stock and neither worked and they were just as puzzled as I was. I am not your 15 year old teenager, but thanks for treating me like one.
I'm still confused as to why anyone would ever return this phone except for physical damage(screen ripping off). Everything software based can be fixed. And its only been 2 weeks. In another 2 weeks, we'll probably have Gingerbread running on this thing. The devs here are simply just amazing. Hell i got these errors BEFORE i rooted. So I'm guessing it was just the network being raped by a new device. I haven't seen them for awhile now.
WoW just wow. You talk to me like I am the biggest noob on the forums.
For your information the root was fine for over 2 weeks and this just started last Friday. I had a launch evo and rooted it the first day it was available. Also I flashed back to stock ruu and had the same problem.
Maybe before you open your mouth and let the **** flow out ask yourself a simple question : Is my comment going to help or just make me look like an ass.
Also I would like to comment on the fact I am pretty good at phone jailbreaking and rooting. I know how to read guides and I have been doing this kind of stuff since the pocket pc's. I have never ran into a much ruder group then the people that posted on this topic. Heck even a rom dev talked to me nicer then you guys did when I asked about a project he hadn't worked on in months.
I have returned my EVO but haven't lost hope in you guys. Just let me know if you guys ever apply at my work so I can avoid you at all costs.
Note: This only applies to the ones that deserve it. Thanks for mentioning the stock RUU Roman G, and for mentioning the factory reset toenail78. I had already tried that but to no avail. Also note I even told the store I rooted the phone and flashed it back to stock and neither worked and they were just as puzzled as I was. I am not your 15 year old teenager, but thanks for treating me like one.
Click to expand...
Click to collapse
Whoa whoa whoa hey now... can I have a job?
-------------------------------------
Sent via the XDA Tapatalk App
Zethmir said:
WoW just wow. You talk to me like I am the biggest noob on the forums.
For your information the root was fine for over 2 weeks and this just started last Friday. I had a launch evo and rooted it the first day it was available. Also I flashed back to stock ruu and had the same problem.
Maybe before you open your mouth and let the **** flow out ask yourself a simple question : Is my comment going to help or just make me look like an ass.
Also I would like to comment on the fact I am pretty good at phone jailbreaking and rooting. I know how to read guides and I have been doing this kind of stuff since the pocket pc's. I have never ran into a much ruder group then the people that posted on this topic. Heck even a rom dev talked to me nicer then you guys did when I asked about a project he hadn't worked on in months.
I have returned my EVO but haven't lost hope in you guys. Just let me know if you guys ever apply at my work so I can avoid you at all costs.
Note: This only applies to the ones that deserve it. Thanks for mentioning the stock RUU Roman G, and for mentioning the factory reset toenail78. I had already tried that but to no avail. Also note I even told the store I rooted the phone and flashed it back to stock and neither worked and they were just as puzzled as I was. I am not your 15 year old teenager, but thanks for treating me like one.
Click to expand...
Click to collapse
You asked people to make assumptions, so thanks for being so offended by it. You come here with an immature ultimatum, "Help me or I'm sending this back!" and give us no other information. Only your signature gives any information about your phone, "rooted." Now you fly off the handle and insult everyone.
Probably because your an apple fanboy and god hates you.
It has nothing to do with being a "noob" or "super cool neeto phone pro". I has to do with the ultimatum of returning a phone that you messed up.
Everything will be ok.
Zethmir said:
Unless someone knows why I keep getting these errors now.
Sorry for the large imgs but I'm not able to shrink them on my iPad right now.
Click to expand...
Click to collapse
Yeah, I'd like to know where in your original post we could safely assume you knew what you were doing. You gave absolutely NO information, except that you have no patience. This is a developer's forum, which means if you don't give out useful information that people can use to help you, they're going to assume you don't know what you're doing.
I simply asked if anyone knew about these errors. I didn't say fix them.
BTW if I was an Apple fanboy I would have preordered a iPhone 4 instead of the EVO. But sorry your way off on that lol. I am just a gadget person. My iPad and MacBook are for work and school. Heck if I wouldn't be getting so much for my student loan I would of never gotten either, well maybe the iPad because it was a great replacement for the iPhone.
I am going to stick with android, and going to go buy a Nexus One. I am thankful for your guys help, sorry if I offended anyone but it just struck a nerve. This is the reason I don't post on forums often for help. Anyways I will keep an eye on the EVO for future possible purchase. I guess when it came down to it, the screen issue (separation and faulty grounding), the meh battery life (I didn't say it was bad it was just sub par), the 30fps limit (which shows), and the poor service in my area were the downfalls for me with the EVO.
I hope you guys all have better luck then me and enjoy your great phone.
I love that your screen shots show the Evo battery as yellow. Thats the only color my battery ever is...
Im wondering why you didn't just exchange the phone for a new one if you suspected a hardware problem?
Zethmir said:
I am going to stick with android, and going to go buy a Nexus One. I am thankful for your guys help, sorry if I offended anyone but it just struck a nerve. This is the reason I don't post on forums often for help. Anyways I will keep an eye on the EVO for future possible purchase. I guess when it came down to it, the screen issue (separation and faulty grounding), the meh battery life (I didn't say it was bad it was just sub par), the 30fps limit (which shows), and the poor service in my area were the downfalls for me with the EVO.
I hope you guys all have better luck then me and enjoy your great phone.
Click to expand...
Click to collapse
The screen separation isn't rampant, and a silly reason to dump the phone if you're not suffering from it.
I have a Nexus One and an EVO 4G. I also have every version of the iPhone from day 1, and should be receiving an iPhone 4 this afternoon if FedEx delivers as promised, so I can speak to each of these with some experience.
I think you'll be EXTREMELY disappointed in the Nexus One if you switch to it after having an EVO 4G. The Nexus One's screen is over-saturated and biased towards too much, I mean TOO MUCH, red. The camera puts a large pink blurred circle into every picture you take. The touch input is very flakey, regardless of ROM you use. It's almost impossible to type accurately on it unless you install Swype or ShapeWriter. It's extremely difficult to see the screen outdoors - I couldn't even get a podcast playing while walking to lunch the other day until I found a big shade tree to stand under. Battery life on the Nexus One is probably the worst of any phone I've ever owned, though that may be a network lack of signal issue (T-Mobile). Speaking of T-Mo, if you get T-Mobile version instead of AT&T you can look forward to lots of missed calls and lots of no 3G coverage areas.
The Nexus One has some great features, including the awesome speaker phone and noise canceling mic, a beautiful hardware design that puts even the legendary styling of iPhones to shame, and it fits great in your hand. And don't forget the fantastic ROMS by Cyanogen and Modaco, but if you're not happy with an EVO 4G I think we'll see you posting over in the Nexus One sections soon enough with some ultimatum about "fix the touchscreen or I'm returning this phone" or some other such issue.
Good luck with whatever phone you pick, because with Android phones, there's ALWAYS some glitch or flaw with the phone that will annoy you, and there's ALWAYS a much better phone coming out next month or two (Droid, then N1, then Desire, then EVO, and upcoming Galaxy S). iPhones have issues too, but at least with your iPhones you don't have to worry about a new better model but once per year - but then you have far fewer options for hacking and the latest hardware. ;-)
Zethmir said:
WoW just wow. You talk to me like I am the biggest noob on the forums.
For your information the root was fine for over 2 weeks and this just started last Friday. I had a launch evo and rooted it the first day it was available. Also I flashed back to stock ruu and had the same problem.
Maybe before you open your mouth and let the **** flow out ask yourself a simple question : Is my comment going to help or just make me look like an ass.
Also I would like to comment on the fact I am pretty good at phone jailbreaking and rooting. I know how to read guides and I have been doing this kind of stuff since the pocket pc's. I have never ran into a much ruder group then the people that posted on this topic. Heck even a rom dev talked to me nicer then you guys did when I asked about a project he hadn't worked on in months.
I have returned my EVO but haven't lost hope in you guys. Just let me know if you guys ever apply at my work so I can avoid you at all costs.
Note: This only applies to the ones that deserve it. Thanks for mentioning the stock RUU Roman G, and for mentioning the factory reset toenail78. I had already tried that but to no avail. Also note I even told the store I rooted the phone and flashed it back to stock and neither worked and they were just as puzzled as I was. I am not your 15 year old teenager, but thanks for treating me like one.
Click to expand...
Click to collapse
I know it's too late to help in this instance, but in the future try asking your questions over at ppcgeeks. They play nicer over there. Most of us here on xda seem to have personality problems and can't play too well with others. You said you might try a nexus one. I have one of those too. I prefer the Evo hands down... If I were you I would go back to Sprint and buy another Evo, You will be much more satisfied down the road. Don't let these folks get under your skin!!
i know its a late reply but ill post anyway. i had the exact same problem. a sprint tech helped me out and called me throughout the day to see if it was working. basically he helped me do a reset of the phone to attempt a fix of the low reception. after that we had to grab a tower and because the tower was down i was getting the exact same problem as OP.
he noted that the phone couldnt be processed in the system yet because of the tower so he would call me and let me know if it went through or not. and if it did to continue troubleshooting it.
i kept on trying all day and it went through a couple of minutes before he called me as if he knew i got through. then it was fixed.
dont remember what we did because we entered a bunch of numbers in the dialer, but i know we reset everything and updated everything. it was durring the update that was causing the problems and recurring errors like what the OP had.
if its rooted id say update but i dont know which not to update since you could lose root. i would unroot, run all updates and register phone automatically and if it works then root. if not call tech and see if it can be registered automatically somehow. when it works, root.
just posting this for future reference because i didnt see anyone mention something like this here
UPDATE 8-30-11 @ 0900 CST
Dev update 8-30
general update for all projects
Ok guys, guess who's semi-back
short story long....
Left arm-much better now
Right arm....whoa, real bad, can hardly move it.
Projects im going to cover and then paste in all my threads..
Pardon any grammar issues, spacebar is all fubar on the laptop
Roms,
VZW & Sprint GB 2.3.4
MIUI
CM7
Kernels,
VZW & Sprint
First the Kernels.......
I started back to work on the kernels saturday. Trying a few things here and there, got some boot ups, got some boot loops. of course the goal is and always will be 100% CWM, EXT4 with auto convert, 3G and of course a seperate kernel for Sprint and Verizon. I ammaking progress. Soon i hope.
I have compiled a few test kernels, was testing on my "dev" tab (its a verizon model that has no 3G) when i bricked it, hardbrick. was my fault, should haveknown better, so I started using my daily driver tab that has 3G, I am down to just the one tab now, which sucks because I use the tab for pretty much all forms of typing based communication, gtalk, texting, email as its easier on my hands than the phone or the pc keyboard, even still i need a larger tab like the xoom, or other 10" tab so i can reduce hand cramping when using it.
Roms,
As far as the roms are concerned, im going to pull Version 2.0 links, put Version 1.0 links back up, to many issues with 2.0 and the theme i think.
Future builds will now be as stripped down, themeless, with a basic launcher, no bells and whistles. I will be releasing as close to a non TW as I can until done with CM7 so I can use that for the base. Ill explain more as that time gets closer.
For now, I recommend using 1.0 on both Sprint and Verizon, and if you need 3G stick with the factory kernel and recovery, if you use the tab for wifi only, and do want CWM+ext4, then there is the perfect kernel avaliable now, ill post the links to stock, and custom kernels.
MIUI/CM7
MIUI, yeah I havethe build released, yes i did work on it a bitmore before my right arm went on strike, yes I will continue, i kinda liked it. But for it to really work 100% I need to finish CM7
CM7.
CM7, the one everyone is waiting for, the build I need to go to more advanced builds for other roms, the base I need for as AOSP as we are going to get, the base I need for MIUI, Oxygen, AOSP, Honeycomb,etc
Im now focusing 100% on CM7, starting almost from scratch, I nuked my dev machine and started fresh in hopes that any issues i may have been experiencing were due to a botched setup. best way to find out, nuke and re-install all dev tools. I am tooling up and syncing CM7 today.
Honeycomb.
Yes, I said it.
I am and will be picking up where Spacemoose left off with Honeycomb. First thing i will release will be a re-release of his v2.5, however I will be including the Audio and BTHID fixes I did for him back then that never made it to a release. Those fixes take care of the ability to use headphones, or exterior speakers and allowing you to plug in and unplug and it switches from headphones to internal speakers, and the audio sounds wicked effing good to, i was shocked. it was these 2 fixes i did that got me into developing, and the first of any dev work i did. BTHID, cant tell you how well it works, maybe im a jerk, but i see no point in mouse/keyboard on a touch screen device small enough to hold, and i dont have BT mouse/keyboard anyway.
Version 3.0, or 2.9, whatever, its the 3G version. I have it, have always had it, supposidly the 3G works, is recognized, however upon booting the damn phone app force closes so much the actual system is almost impossibleto use, or test the 3G, that will be a side project.
Physical abilities,
Well so some of yall understand what is going on with me,because all i do is mention arm pain, ill explain...
Last year I was hurt at work. I fractured a vertibre, and my disc's L1-L5 vary from split, hemmoraged, herniated, and even one has a piece that broke off.
Itsucks sitting because I have 2 nerve bundles that are pinched, so my legs go numb, and it also hurts to sit. alot of the time any period longer than 10 minutes results in both legs going fully numb, and i cant stand on my own for 20 minutes following, kinda funny sometimes cause if that happens i start to look like david hasselhoff trying to get a burger....
Also, this goes for both arms...
Both inner and outer joints in elbows damaged. Tendon damaged and seperated in elbows and forearms, nerve damage that can only be described as pure suck is also known as full on carpal tunnel in both wrists, have 40% sense of feeling in all fingers, pinky, ring, middle and thumb are constantly numb, tingle, and hurt. Left elbow feels a bitbetter now, right arm, i cant even support the weight of my tablet in any way shape or form, arm has a brace from shoulder to fingers, and in a sling that keeps it to my chest to keep from moving anyway. sucks, but you make adjustmentsin life.
So, i got help from my wife, and friends to make a desk i can stand at, and a platform that raises my mouse and keyboard up and almost to my neck so i can use the mouse as i am a righty. I have been taken off work since december, and probably will either not be able to go back to janruary, or...at all if these nutbag dr's cant fix me and im labeled disabled for life. I no longer stress out over this, and just keep moving forward.
So it gives me all day and night 7 days a week to work at a computer if i can pending the pain in arm is not bad enough, standing actually feels much better for my back. I watch my 2 kids all day while i make my wife go to work ( lol ) and feel like Mr. Mom sometimes, my 4 year old daughter helps so much, its gotten to the point where its actually fun trying to teach her how to do things to help me, she knows how to use the macbook, and calls it the "Apple" without me ever telling her it is an apple, she obviously knows what an apple symbol is....duh.
Wife supports me spending all evening and weekends on pc, knowing i like doing this, so the ability to do this is there. I wont lie, going from a nice income to almost nothing sucks, put us behind, and yes I will end up selling anything needed to make sure my kids have a house, food, electricity before i have a tab, multiple tabs, computer, woodshop, etc. They are above and beyond way more important than anything else inmy life, so dont feel sorry for me, it's the responsible thing to do, and if it ever gets to the point where i have to ditch the remaining tab, then i will upload all work, source, material, etc, and create a writeup for all projects for someone else to pick up. that way yall aint left hanging without a CDMA developer anymore.
Now this is the most important thing of all.....
I am not doing this for the donations, or for the income, etc. I do this because i enjoy it, i have the time to do it, and it keeps me occupied during the day and its fun. Nothing i mentioned above is to gain a pity party, **** happens, and there are people out there who have it worse than i do financially, physically, etc.
So, if you feel the absoloute need to get in touch with me, my gtalk is the same as my username here. same for email. I am bad about getting back to people because i reserve typing for dev work, it does suck trying to type, i am more of a phone person, i wear a headset, its easier on my in alot of ways. I'm sorry but i can not give any type of tech support via gtalk right now, it would eat up an entire day to just troubleshoot 1 tab and it's unique issues, sorry but i cant, got some pointers on building kernels, stuff like that, feel free to jump in.
So, there you go, a well rounded and long ass update posted in every one of my threads, lol, just to drive people nuts i suppose. Next update should be with new projects.
Jim
=======================================================================================================================================================================================================
Version 2.0 of Future Echos
Changelog
Created and built TouchBlur theme.
New TouchWiz 4.5 with rotation fix and extras
Details
Ok, Only issues I was aware of, no rotation in TW, long press on screen, the bland look of Samsung's Tab, and of course 3G with the custom Kernel.
Call it a port of Moto Blur, dont call it a port of Moto Blur, however you can call it not finished. Ver 3 will see other apps matching the rest of the rom
TouchWiz Launcher
There are so many version of TW4, and 4.5 out there for anyone to grab, i hope nobody thought i pulled some rabbit out of a hat, yes i spent the time to make sure it would work, and 2 out of the 11 versions i tried worked. I released one of those versions in V1 of the build.
I have reached out to both Devs on those projects, one of them is abondonedware that I have taken over for future releases, the other one I asked the Dev if i could strip out his build and include it in my second release, as well as theme it as i have, and he gave me the blessing to do that.
What Works in TW 4.5
Long press on home screen
Rotation (enable in settings, reboot tab)
Themed, and left Original Dev's Donate link in settings
I use Smart Keyboard Pro with HTC theme. I wont include as it is a paid app in the market.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Installation Instructions.
READ ME
First, get Heimdall 1.1.1 Why? Because thats what I use, if you choose to use a different version, I can not provide support.
I use 1.1.1 because it works, I've always used it, i see no point in upgrading something that is not broken.
Heimdall 1.1.1 Windows
Heimdall 1.1.1 OSX
There are 32 and 64 bit versions for Linux.
You will lose all of your data and apps, it is a requirement to wipe data, wipe cache, wipe dalvik. Any deviations will result in a non working system.
Unzip package.
Open Heimdall
Put Tab into download mode
Place Filesystem in the filesystem
Place zimage in kernel
Place zimage in recovery
IMMEDIATELY upon first boot!!! force tab into recovery.
WIPE DATA
WIPE CACHE
REBOOT
This method has worked on many tabs over the past week. These are the methods and tools I use.
If you do not wipe data and cache, you will boot loop.
Even if you do not bootloop, i doubt Touchwiz will run.
Touchwiz.....
press menu and go to preferences.
Select Homescreen Settings
Check "Landscape Mode"
Reboot Tab
You now have rotation.
The Donate button in the TouchWiz settings, is for the original Dev is built the app. I did not remove his Donate button. If you wish to donate to me, use the link in my post, if you wish to donate to him, use the donate button in the app.
The Rom has 3G data access
The Rom does not have a custom Kernel and recovery yet.
You can not flash any other kernels from any other devs unless it is for your tab, ie: Sprint kernel for Sprint Tab, Verizon Kernel for Verizon Tab.
Spacemoose and I are working on a 3G enabled Kernel.
Have fun, enjoy, see ya for V3.0
Better Than Life Future Echos V2.0 GB V 2.0 HERE
If you like my work, feel free to donate.
..
Changelog and Updates
Update 8-7-11
Uploading new Sprint only build right now. I have no way to test the 3G ability, however I am sure ya'll be nice enough to let me know if it works.
From now on, I will work on what I am calling "the twins" the Sprint and Verizon Version together at same time, Both Carriers will recieve IDENTICAL builds now.
Enjoy.
Jim
reserved 2
SWEET!!
Nice... Thanks Jim, Us CDMA Tab owners appreciate it!! Can you overclock the Kernal for us... 1.4 - 1.6GHz?? Maybe even some Voodoo Lagfix??
wow, weeks or is it months of watching and waiting...very cool.
Yes Sir. Thank you Jim.... We do appreciate all the time and effort...
Well done Jim! can't wait to test that bad boy out!
Very Well Done!
Cant wait to see what this becomes
It's so...b e a u t i f u l !
Updated OP
hope surgery goes well man, and thank you for everything
there are scripts floating around that will convert back and forth between rfs and ext4.. so those might help in the process if the CWM install doesn't automatically do it.
I hope all goes really well with your surgery. Us CDMA folks have been waiting forever and a day, but it will not hurt us any more than your constant pain is, so handle your stuff First. We can wait longer, no big deal.
vabeach454 said:
I hope all goes really well with your surgery. Us CDMA folks have been waiting forever and a day, but it will not hurt us any more than your constant pain is, so handle your stuff First. We can wait longer, no big deal.
Click to expand...
Click to collapse
I concur with vabeach454. We can wait, even if we are impatient. I wish you luck on your surgery, may there be no complications.
I am excited about this. Good luck with your surgery.
This will b awesome but take care of yourself first. We will wait.
Sent from my Epic on Midnight or my Galaxy Tab rooted (feels naked without a ROM)
you need to release a rom for us. After your suregery you may not be able to even scratch your own ass or even hold a tab.
(This is a joke and a best wishes with the surgery post )
teezle said:
you need to release a rom for us. After your suregery you may not be able to even scratch your own ass or even hold a tab.
(This is a joke and a best wishes with the surgery post )
Click to expand...
Click to collapse
I am.......effing tore up right now, ****.
But, ......but......however.......so........it..... lol
I am going to pop a few dozen pain pils, and get to work today. I want this damn kernel released tonight. I am so kernel out tonight.
Spacemoose built the first one, i compiled the second one after pulling the ext4 module out, still wont boot a rom on my tab, however, that poor tab, so abused, i am shocked it boots at all.
Ill get with Dan when he wakes up, try a few things with his help, maybe get a basic kernel with recovery only released, and worry about the bells and whistles next week.
Damn, my **** is killing me, but i cant sit around and keep a forum full of half ass ****, gotta wrap up Psirens, release Cassandra, release this kernel, so i can get back to the CM7 i started. The surgery taxed my bank account today, damn co-pay, ****.
I tried pulling a Vanilla Sky, but the Dr's wouldn't let me sing. lol
Dude, seriously. It's all good, they're just ROMs. Put down the SDK and rest. Our need for your work is less than your need to focus on your health.
So I just got this phone today. This is a brand new phone just taken out of the box. I plugged it into the charger and BOOM!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now This is where I stand:
Cannot boot into Recovery
Cannot boot into Download Mode
Cannot flash anything using Odin
No button combo's help get into anything
Phone will not boot normaly
The only 2 things I have yet to try:
A MicroUSB Jig (Which is in the mail as I type this)
A ROM that could possibly be loaded using Heimdall
What is a brother to do!!
Don't think they have any support for the T-Mobile version of the SGS2. Think you flashed CM7 for a different SGS2.
Um dude I hate to be the one to tell you this but that version was for the international gs2, not the tmo one. You're pretty much hard bricked.
Sent from my Hercules with xda Premium.
What don't you people get? I put it in download mode and this is what happened. I didn't even get to the point of installing a custom recovery in order to installing a custom ROM. This happened right out of the box. so version numbers mean nothing cause nothing was loaded on it. I'll take this up with T-mobile cause its obv something with the phone since I DID NOT LOAD **** ONTO IT.
I understand that this version of Cyanogen is not supported for the T989 however I did not even get to that point to its irrelevant.
*EDIT* But yes I would have ****ed it up regardless if I didn't fully read everything before starting *EDIT*
Sharpie603 said:
What you you people get? I put it in download mode and this is what happened. I didn't even get to the point of installing a custom recovery in order to installing a custom ROM. This happened right out of the box. so version numbers mean nothing cause nothing was loaded on it. I'll take this up with T-mobile cause its obv something with the phone since I DID NOT LOAD **** ONTO IT.
I understand that this version of Cyanogen is not supported for the T989 however I did not even get to that point to its irrelevant.
Click to expand...
Click to collapse
Okay, sorry I misunderstood man but either way you're a bit SoL. How do you intend to explain the situation to T-Mobile regarding why they should replace your phone "I was in the process of voiding my warranty but couldn't get far enough into it so you should give me a new one so I can do all the stuff you don't want me to do"? Good luck mate.
FYI This is the first report of this happening to someone, many people have used the current ODIN root method without having this happen.
After reading what kenvan19 said, then going back to read this, with the Rebecca Black instrumental playing in the background...... Lmmfao!! This is crazy comedy lollll!
Sharpie603 said:
So I just got this phone today. I noticed Cyanogenmod 7 Supports this device and they have a stable build. Was like hearing My b-day was tomorrow. I got excited and started reading the Full update Guide just to see if some steps might be different then the Vibrant and Galaxly S 4G. I wasn't going to worry about a backing it up because simply.....this is a brand new phone just taken out of the box. There was nothing to backup, however there's allot I'd like taken off (Bloat)
Click to expand...
Click to collapse
Sent from my SGH-T989 using Tapatalk
Odin will pick it up on Com port 6 but will not flash anything. And I don't have to explain to t-mobile what I was going to do. This phone is 1 day old.... I have at least 14 days to return it. Exp. if its defected.
Just got off the phone with T-mobile. I told them what I did...
I took the phone out of the box, plugged it into the charger and after 5 minutes looked like the picture (Yellowish Green)
she transferred me to the technical department, once I was there I explained what happened again and the second I said yellowish green screen the guy said STOP. This is a "Known issue with this device and Samsung is aware of it" I am in the process of getting a replacement.
**EDIT** T-mobile Tech informed me of a faulty display crystal that can sometimes "crack" due to overheating. even tho it was plugged in for 5 minutes, it could have been a bad crystal **EDIT**
Sharpie603 said:
What don't you people get? I put it in download mode and this is what happened. I didn't even get to the point of installing a custom recovery in order to installing a custom ROM. This happened right out of the box. so version numbers mean nothing cause nothing was loaded on it. I'll take this up with T-mobile cause its obv something with the phone since I DID NOT LOAD **** ONTO IT.
I understand that this version of Cyanogen is not supported for the T989 however I did not even get to that point to its irrelevant.
*EDIT* But yes I would have ****ed it up regardless if I didn't fully read everything before starting *EDIT*
Click to expand...
Click to collapse
Well that was a wall of text that no one was going to read threw after you mentioned Cyanogen. That is why a few of us blamed that. Could of easily have just said "I went into recovery and got this screen"
LOL i didn't even get into recovery. Should just start over. Let me edit the original post
+1
Sharpie603 said:
Just got off the phone with T-mobile. I told them what I did...
I took the phone out of the box, plugged it into the charger and after 5 minutes looked like the picture (Yellowish Green)
she transferred me to the technical department, once I was there I explained what happened again and the second I said yellowish green screen the guy said STOP. This is a "Known issue with this device and Samsung is aware of it" I am in the process of getting a replacement.
**EDIT** T-mobile Tech informed me of a faulty display crystal that can sometimes "crack" due to overheating. even tho it was plugged in for 5 minutes, it could have been a bad crystal **EDIT**
Click to expand...
Click to collapse
this is good to know, i'll add it to the Confirmed Known issue list
Sharpie603 said:
Just got off the phone with T-mobile. I told them what I did...
I took the phone out of the box, plugged it into the charger and after 5 minutes looked like the picture (Yellowish Green)
she transferred me to the technical department, once I was there I explained what happened again and the second I said yellowish green screen the guy said STOP. This is a "Known issue with this device and Samsung is aware of it" I am in the process of getting a replacement.
**EDIT** T-mobile Tech informed me of a faulty display crystal that can sometimes "crack" due to overheating. even tho it was plugged in for 5 minutes, it could have been a bad crystal **EDIT**
Click to expand...
Click to collapse
Well look at all the good things that came from this, you get a brand new device and you found another known issue to add to the list to be avoided and fixed lol
Very true very true. that's what you get for being a tester..
This bad crystal...is it a 'dark' crystal, or more like a crystal ball?
It was more like a dark crystal... like the movie. Took me forever to get my hands on it
Well atleast you found a problem early and not after the 14 days
Ill tell ya what we don't get is a bricked phone. No need to get nasty with members especially when you seek help.
Sent from my SGH-T989 using XDA Premium App
***UPDATE***
First.... I'd like to apologize to everyone when I was a little rude. As you know when getting a new device you expect it to work right out of the box and this one did not. It definitely put a hole in my day. So for the attitude I am sorry for.
Second...I have received the new phone. This one seems to be holding up alot better then the last. So far here is what i have done.
Rooted the device using Odin (My Fav tool of all)
Installed Custom CWM Recovery
Installed Superuser ( Had to try this 4 times to finally get it to install, known issue I guess) However it did end up installing.
All from the following procedure: http://forum.xda-developers.com/showthread.php?t=1311194
Now I am successfully ROOTED and running CWM recovery. Looking at Rom's now. Anyone have any suggestions?
***EDIT***
Just installed EaglesBlood, I'll test this for about a week. If I see anything out of the normal I'll update. However on Stock ROM Unrooted I ran a 3100 benchmark. With this Eaglesblood ROM I just ran one at 2195
Update:
Took off EaglesBlood, it was not as fast/smooth as I expected. Currently testing convrgence and so far.... WOW.
Blogger.com bro.
Alright... So there I was, walking through the wilderness, all alone.. When all of the sudden..
Just kidding. Okay, so I was running AOKP for a few days (Awesome ICS rom by the way, for those looking). I was trying to figure out why my MMS.apk was cutting me off at 160, instead of going to page 2. I asked about it and a lovely gentlemen told me that I needed to flash the Mirror'd link because it supported SMS split (or something along those lines). Okay, awesome. I downloaded it to my SD card, boot into Rogue Recovery and flash it. I was watching something on TV (can't remember what it was). About 3 minutes go by and there was no real sign of progress from the phone. Me, being distracted by the TV and not thinking, decided to restart it and try to flash it again. I held down the volume down and power, and attempted to reboot recovery in the middle of a flash. OPPS.
Phone shut off. I tried to turn it back on, and all I got was a pretty blue light from the LED. There was no sign of anything on the screen, at all. No button combination worked. Download mode, recovery, nada. I pulled the battery (duh) and it still did nothing. I researched how to fix brick's and found a tutorial by another wonderful gentlemen explaining a USB Jig (I hadn't heard of such a device). He walked through how to make one. I accepted the challenge. Tore apart a phone charger I had, soldered 300k oHm resistors in a series from 4-5, and crossed my fingers. Pulled the battery, plugged in my home-made Jig AND... Nothing. Actually, that's a lie, it made the pretty blue light come back on. Not quite the outcome I was hoping for, but still pretty cool, right? Whether I made the Jig incorrectly or not is debatable, I hadn't made one before, so it's possible I did something wrong, but the phone did recognize something being plugged into it, so that's kind of cool.
Anyways, phone still wouldn't do anything. I called the Sprint store and they closed at 8:00pm, it was 7:45. Got in the car, 110mph on the highway and walked in the door at 7:57. I figured he would be completely unhelpful since I walked in RIGHT before he closed, but he was actually really cool. He was a new guy too, which helped tremendously. I handed him my GS2 and told him that it was "Not working anymore". I told him that "The screen won't come on. The only thing that works is that LED at the top, which as awesome as that is, doesn't help with the whole 'phone' aspect." He asked when it started doing it. I told him that "It started earlier this morning. I thought maybe it would straighten itself out. I'm new to this whole 'smart phone thing'." He laughed at me and asked if I had downloaded any new apps or if the phone had updated. I said, "No sir. I woke up this morning, was running late for something. Jumped in the shower and when I got out I pulled my phone off the charger. That blue light always came on when the phone was fully charged, so I didn't suspect anything. I walked out to my car and tried to turn the screen on and it wouldn't do anything. I have no idea what caused it to do that. Maybe it over heated?..." He said "Man, that's strange. These are really good phones, I haven't ever heard of one doing that before." Then, the words that I wanted to here.. "Here's what's going to happen Mr. Kuhns. I'm going to do an Advanced Exchange. You have insurance, so that's covered. Can you sign *here* and *here* please."
My new phone will be here on Friday. If not Friday, then it will ship to the store on Monday. I ordered a USB Jig from Ebay for $5 and it will be here around the same time, so if this happens again, maybe I can save myself the hassle.
I know this is a REALLY long and drawn out story, but I wanted to share in case some of you had a similar situation, or wanted to know what I said in order to talk him into getting me the new phone. I thought about trying to pull the "Can I have a white one..?" card, but didn't want to push my luck. I may bring it up when I go in Friday. Oh, and in the mean time, I have to use an old Black Berry 8703e. It's not AWFUL, but it's pretty ****ing close. Only a few more days and I'll have my baby back.
Also, I was serious about AOKP. Those of you looking for an ICS rom that is customizable and smooth, you aren't going to find one right now that can do better than AOKP. There are plenty of customizations, and the rom runs super smooth. I can't really tell you about battery life. I run a 3800mAh battery, so I don't really pay attention, but it really is an awesome ROM. Check it out if you're into the ICS game.
Here's a shot of the BB I'm currently on. Pitiful.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Cool story bro.
Too long to read tho
yeah i dont feel like reading all of that.
I ended up reading it. Felt guilty for poking him.
Its got all the makings of a great movie. Random opening scene. Drama, intrigue, a plot twist... Hell, its even got a teaser at the end hinting at a sequel!
Sadly, no gratuitous frontal nudity.
No sexy girls? No sex or stripers party? Hellz no! How dare you!
Answer to your question
If you try that again at the moment with the new phone it will probably have the same result. For now the general consensus is to not recommend flashing anything by CWM while the ICS kernel is installed. Instead, use ODIN or Mobile ODIN to flash a GB kernel (such as EL26/EL29)
That *might* be subject to change soon so do keep an eye on a couple of threads such as the "How Not to Brick Your E4GT" stickied at the top of this forum. It will be one of the first to be updated should the situation change.
Glad you got your phone swapped out though.
Lmao. Glad you enjoyed the story. There was some serious thought put into that writing. As for flashing in GB, I knew that.. and I read about that.. but there was that whole "I don't need to do that.. That's stupid" thought, and well... Yup, this Black Berry is dreadful. From now on, or until an update is out.... Flash ICS with GB. Lol don't try to rebel, your phone will give you the finger.
That blackberry is horrid but its better than nothing :thumbup:
Sent from my SPH-D710 using xda premium
AAAAHHHH!!!
Easy AE at any Sprint service center - just make sure you can't get into download mode. If they can't verify your ODIN count, then you have no way to prove that you rooted it, flashed any custom kernels, etc.
Worked great for me, and I used to work for Sprint, so I know for a fact that this method works - as long as there's no physical or board-level damage, make sure you can't see the ODIN count and you're golden.
Everyday Legend said:
Easy AE at any Sprint service center - just make sure you can't get into download mode. If they can't verify your ODIN count, then you have no way to prove that you rooted it, flashed any custom kernels, etc.
Worked great for me, and I used to work for Sprint, so I know for a fact that this method works - as long as there's no physical or board-level damage, make sure you can't see the ODIN count and you're golden.
Click to expand...
Click to collapse
Good to know. I ordered that Jig for future uses, but hopefully I won't have to use it.
This BB is awful. If I get a MMS, it texts me a link that I have to load in the browser, and the browser is unGodly slow. It's all around dreadful. Not to mention EVERYTHING was on that GS2. You don't really realize what you have until it's gone. Lol music, pictures, work schedule, notes.... The list grows each day I go to find something. -_-
And it is possible you made the jig right. In that type of situation with the blue led hard brick a USB jig won't work.
MeWarning said:
And it is possible you made the jig right. In that type of situation with the blue led hard brick a USB jig won't work.
Click to expand...
Click to collapse
That would make sense. I will admit, I'm not entirely sure what the difference is between a hard and soft brick. I assumed a hard brick would be absolutely no response from phone at all, and the blue LED made me think there was a light at the end of the tunnel.
Apparently not. :/
Just another blue light of death horror sorry containing AOKP/AOSP+ICS+CMD9. My friend i have done it all on cwm rougue. From flashing ICS ROMS to wiping and restoring. Now the only 2 times I've used cmd9 (luckily i was on GB) and nearly bricked both times. First time i was on a rogue kernel and flashed to cmd9. seemed ok, then my phone randomly crashed. Tried to reboot and went to blank black screen with only blue light. Tried to restore and my recovery looked like a mix of rogue and cwm9. Didn't work anyhow. So tried to reboot and threw me into a boot loop. Luckily it went into download mode. Tried to Odin to stock GB- failed. Tried Odin again, boot loop + yellow triangle that it didn't have before. Odined back again-passed and booted. Whew. That was on gb. I'm sure i would have bricked had i been on ICS at that time. I won't even tell you about the other time with cmd9. Anyway i realized that you need to Odin between cmd and anything else and before flashing but while on stock one should do a full wipe and factory data reset. And if on ICS Odin back to GB before wiping or backing up or flashing. Sorry bud but i respectfully disagree with you about cmd9. You already bricked one device. Hope you learned something by this experience. Good luck with your new phone man. Oh and one more thing, of you update to GB or ICS it z also updates your boot loader. Everything after eg30 has an updated boot loader and your jig won't work. You would have to flash the eg30 boot loader to whatever ROM you're on prior to abrick. And still no guarantee. So hopefully you won't have to do the walk of shame back into sprint.
timmetal6669 said:
Just another blue light of death horror sorry containing AOKP/AOSP+ICS+CMD9. My friend i have done it all on cwm rougue. From flashing ICS ROMS to wiping and restoring. Now the only 2 times I've used cmd9 (luckily i was on GB) and nearly bricked both times. First time i was on a rogue kernel and flashed to cmd9. seemed ok, then my phone randomly crashed. Tried to reboot and went to blank black screen with only blue light. Tried to restore and my recovery looked like a mix of rogue and cwm9. Didn't work anyhow. So tried to reboot and threw me into a boot loop. Luckily it went into download mode. Tried to Odin to stock GB- failed. Tried Odin again, boot loop + yellow triangle that it didn't have before. Odined back again-passed and booted. Whew. That was on gb. I'm sure i would have bricked had i been on ICS at that time. I won't even tell you about the other time with cmd9. Anyway i realized that you need to Odin between cmd and anything else and before flashing but while on stock one should do a full wipe and factory data reset. And if on ICS Odin back to GB before wiping or backing up or flashing. Sorry bud but i respectfully disagree with you about cmd9. You already bricked one device. Hope you learned something by this experience. Good luck with your new phone man. Oh and one more thing, of you update to GB or ICS it z also updates your boot loader. Everything after eg30 has an updated boot loader and your jig won't work. You would have to flash the eg30 boot loader to whatever ROM you're on prior to abrick. And still no guarantee. So hopefully you won't have to do the walk of shame back into sprint.
Click to expand...
Click to collapse
Good to know. The walk of shame isn't too bad as long as you have a decent story backing it up. I just pretend to know absolutely nothing about the phone at all. "Has the phone installed any updates or anything recently?" - "You know, I couldn't tell you. I barely know how to text on this thing. My friend does everything for me when it comes to technical stuff."
Anyways, hopefully I won't have to through with it again. Maybe I should just stick to a GB Rom until the bricks have cleared out. I'm not entirely sure though. I liked AOKP, but it's not worth resorting back to this BB while the Sprint people order my new one. Lol
funny...i just did the same thing tryin to get Aokp on my et4g(i wanted to try the tablet mod)...needless to say i bricked!..panicked...thought about how my warranty is surely voided,then about all the private pics and everything i lost(and that sprint might see..lol)..luckily i had a senior member kinda walk me thru the process of what to do and how to do it...used my touchpro 2 for a few days and my new et4g came in today!(about to root now..)..had to laugh while reading your post cause i thought about goin white too...decided against it when i saw the most feminine lookin dude i ever seen rokin a white iphone..haha...good luck and good flashing!
I'm going insane trying to find a solution for this. All my calls are really quiet, and for some reason I believe are being routed to the back speaker of the phone. If I rotate it towards the back, it's much louder. Speaker phone is twice as loud. I'm more worried about people listening into my calls or me looking stupid with a backwards phone on my ear.
I tried reflashing roms, rebooting, using soundabout to redirect audio to earpiece, and also swapping the earpiece out with a new earpiece. (The long ribbon cable with the earpiece at the top) and it's still super quiet so I'm beginning to believe it's not a hardware issue. Has anyone else encountered this? I haven't been able to find much information. I love this phone but god damn this is driving me nuts.
Are you running stock or custom?
And have you tried flashing your firmware with Odin and factory resetting? (Will wipe internal sdcard)
I'm running crom 7.1 and I haven't. I lost my backup when I had a hard drive die on me. Was hoping I didn't have to go back to stock though.
Its the best way to tell if its hardware or firmware/rom related. Otherwise you'll have to get with some long time cm users to start investigating it. I dont use cm roms so im not familiar enough to troubleshoot a problem like this.
I have seen other reports of similar issues with cm. Most who flashed stock firmware found it worked fine so it wasn't hardware. I have seen some thst were hardware related though, but it is more likely related to the rom in your case.....I think.
If you're worried about going back to stock though, why not make a new nandroid backup so you can restore back to it after testing stock?
DocHoliday77 said:
Its the best way to tell if its hardware or firmware/rom related. Otherwise you'll have to get with some long time cm users to start investigating it. I dont use cm roms so im not familiar enough to troubleshoot a problem like this.
I have seen other reports of similar issues with cm. Most who flashed stock firmware found it worked fine so it wasn't hardware. I have seen some thst were hardware related though, but it is more likely related to the rom in your case.....I think.
If you're worried about going back to stock though, why not make a new nandroid backup so you can restore back to it after testing stock?
Click to expand...
Click to collapse
I guess that works. ^.^, honestly, I just don't like touchwiz and the bloat. I guess since I'm rooted I can find a way to debloat though. I'll give it a try in a bit.
So the best thing I can do would be to flash
Wind VLFNF1
PDA: T999VVLUFNF1
CSC: T999VYVLFNF1
Version: 4.4.2 KK
Date: June 23,2014
From the http://forum.xda-developers.com/showthread.php?t=1949687 thread, use towelroot to reroot (or will I lose root going back to official firmware?), and test. If it's botched there, it might be a hardware defect, correct?
I am with Wind Mobile, I just don't know if I am able to flash back to an older version or if I should stay on KK.
After 4.3, you can only flash the same or newer builds, so if you flash NF1 firmware, that's alk you can flash from now on. You can still flash old roms though.
Other than that, youve pretty much got a handle on it. And yes, you'll need to reroot. See my Towelroot thread in General for instructions.
DocHoliday77 said:
After 4.3, you can only flash the same or newer builds, so if you flash NF1 firmware, that's alk you can flash from now on. You can still flash old roms though.
Other than that, youve pretty much got a handle on it. And yes, you'll need to reroot. See my Towelroot thread in General for instructions.
Click to expand...
Click to collapse
Yeah I remember hearing about not being able to revert to a certain version and wanted to ensure I didn't brick my device. I guess I'll flash the latest KK one then. Thanks so much Doc!
Well I flashed the OTA 4.4.2 and it still has the same problem, this sucks big time doc.
Have you factory reset? Sorry if i missed it when going back over the thread.
If you've done that after having flashed the stock firmware with Odin (not Mobile Odin), it usually means its got a good chance of being a hardware problem. But you said you already replaced the speaker right? That tells me if it really is hardware, it may be on the motherboard. Perhaps a shorted or broken connection. Or just some component going bad.
Unfortunately, the only way to know this for sure is to put your motherboard in another S3 and see if you get the same result.
Maybe try swapping SIM cards with someone else who uses Wind. Its not likely to be a SIM card problem, but its an easy thing to test, just to make sure.
I hate to say it, but other than that, im out of ideas... Maybe someone else might chime in with something I haven't thought about, or overlooked. Ill still try to think of anything else you could try and will let you know if I do. I am very sorry I dont have more for you now though...
DocHoliday77 said:
Have you factory reset? Sorry if i missed it when going back over the thread.
If you've done that after having flashed the stock firmware with Odin (not Mobile Odin), it usually means its got a good chance of being a hardware problem. But you said you already replaced the speaker right? That tells me if it really is hardware, it may be on the motherboard. Perhaps a shorted or broken connection. Or just some component going bad.
Unfortunately, the only way to know this for sure is to put your motherboard in another S3 and see if you get the same result.
Maybe try swapping SIM cards with someone else who uses Wind. Its not likely to be a SIM card problem, but its an easy thing to test, just to make sure.
I hate to say it, but other than that, im out of ideas... Maybe someone else might chime in with something I haven't thought about, or overlooked. Ill still try to think of anything else you could try and will let you know if I do. I am very sorry I dont have more for you now though...
Click to expand...
Click to collapse
I'm with Koodo now since I moved where Wind has no reach so that meant a new sim card already.. I hope it's not motherboard, that'd be indicative of this phone being toast eh? I did factory reset. When taking the motherboard out the components appeared fine. Unfortunately I don't know anyone else with an s3. Crap.
It may not be hardware still, but I am kind of leaning that way if it acts the same on any setup, including different versions of full stock.
It is possible it could be an account, SIM card, or other firmware corruption issue. (Firmware as in, not the partitions that are generally flashed when using Odin) I dont know of any way to determine if it is, or how to fix it if confirmed to be that though. Im not sure if there is anything in the NV Data that is used for audio. I will try to take a look later on.
Did it work fine previously on Koodo?
Anyone else out there have any ideas? @Perseus71 @Aerowinder @serio22 ?
DocHoliday77 said:
It may not be hardware still, but I am kind of leaning that way if it acts the same on any setup, including different versions of full stock.
It is possible it could be an account, SIM card, or other firmware corruption issue. (Firmware as in, not the partitions that are generally flashed when using Odin) I dont know of any way to determine if it is, or how to fix it if confirmed to be that though. Im not sure if there is anything in the NV Data that is used for audio. I will try to take a look later on.
Did it work fine previously on Koodo?
Anyone else out there have any ideas? @Perseus71 @Aerowinder @serio22 ?
Click to expand...
Click to collapse
I moved up north so I switched to Koodo about a month ago. It never worked on Koodo, but it also did not on Wind. This problem surfaced about half a year ago where I literally couldn't hear people. I was struggling cancelling my internet 3 months before I left. In between then and when I moved I had changed the piece (I've been building PC's for the majority of my life) I know I did the swap correctly. Sucks. It seems twice as loud reversing the phone (back of phone on my ear) or top of phone on ear, are most phones like this but at a higher volume? I wonder if the speaker relocated itself or flipped during reassembly. It does work better than when it did when I initially had problems but it's still not where it used to be, it's highly diminished.
Thanks for the help so far Doc.
Hmm.. have you checked if something is blocking the earpiece section? Or maybe try cleaning it. It would make sense why you can hear it better through the back but I don't know, that's the only thing I can think of right now that I haven't seen covered.. definitely doesn't sound like a software issue
@ chevymeister
Please try 2 things for me.
1. Use a good Bluetooth device for calls. See how the quality of sounds is over that one compared to the phone itself.
2. There are several known complaints with C-Rom's Volume issues. Some CM commits have borked it and those need to be reverted. From your point of view, please try another AOSP Rom such as Liquidsmooth or my personal SlimKat. Especially since you don't like Stock.
Make sure you do factory reset before flashing these roms. First thing you should do after flashing these roms is checking in-call volume before you restore any of your apps.
Perseus71 said:
@ chevymeister
Please try 2 things for me.
1. Use a good Bluetooth device for calls. See how the quality of sounds is over that one compared to the phone itself.
2. There are several known complaints with C-Rom's Volume issues. Some CM commits have borked it and those need to be reverted. From your point of view, please try another AOSP Rom such as Liquidsmooth or my personal SlimKat. Especially since you don't like Stock.
Make sure you do factory reset before flashing these roms. First thing you should do after flashing these roms is checking in-call volume before you restore any of your apps.
Click to expand...
Click to collapse
Come to think of it, ever since I got my bluetooth deck in my car my calls started acting up on my earpiece but that was awhile ago so maybe I'm just imagining it.. In call volume is fine using bt though compared to my in call. I'll try your rom a bit later tonight. I'll let you know. Ever since returning to stock my 15hr uptime turned into 3hr uptime. God I hate stock.
Can't help myself.
People talk about stretching a dollar. I stretched the battery to prove a point to some other users.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Perseus71 said:
Can't help myself.
People talk about stretching a dollar. I stretched the battery to prove a point to some other users.
Click to expand...
Click to collapse
That's what I'm talkin about!
I installed slimkat a few minutes ago, call volume definitely didn't improve. I'm going to tear this phone apart this weekend and see what I find I guess. This is depressing. I guess trying to be optimistic at least I'm off that stock battery sucking abomination. Haha.
Quit hating on stock guys, I got 2 days on a single charge right now on stock with 1:13hr screen time
But I'll admit I haven't used it heavily but I got similar results as you guys on aosp/cm when this was my main phone
I think each OS just has a particular way it likes to be held. If it doesn't like the way you are handling it, it takes its revenge by sucking up your battery!
Can't think of any other reason why TW is great for some and only cm/aosp for others!
Just a theory! Lol!
Sorry for going OT, couldn't help it!