So my screen likes to flicker sometimes when I'm typing on my keyboard (the new Swype keyboard and swiftkey as well).
It only does it sometimes but I've only noticed it happening when typing . What I mean by flickering is that the screen goes darker and then back to normal.
I'm on an aosp rom but it also happened on viper 4g.
I don't have the latest tp firmware.
Soff and hboot 2.09 (or whatever the latest one is)
Sent from my EVO using xda app-developers app
Only time I've ever noticed it is the setup wizard on every AOSP rom I've flashed for this phone.
Only time I've noticed it though
Sent from my EVO using xda app-developers app
Preform a clean install if you haven't tried that already. Wipe Cache, Cache/Delvik, System, and Data before flashing.
If you mean that the screen dims, since you explain it as getting light and dark, then I'm not quite sure what to tell you. I've never experienced that issue on any ROM. If you actually mean flicker then I've only experienced that with ROM's of which I also tried a custom kernel. That means you need to up your voltage using a voltage script, kernel tuner, or another app. Usually caused by overclocking.
Delakit said:
Preform a clean install if you haven't tried that already. Wipe Cache, Cache/Delvik, System, and Data before flashing.
If you mean that the screen dims, since you explain it as getting light and dark, then I'm not quite sure what to tell you. I've never experienced that issue on any ROM. If you actually mean flicker then I've only experienced that with ROM's of which I also tried a custom kernel. That means you need to up your voltage using a voltage script, kernel tuner, or another app. Usually caused by overclocking.
Click to expand...
Click to collapse
Hmmm.
I guess I'll try to get video of it happening,but I'm underclocked right now and it still happens occasionally. Thanks for the help though
Sent from my EVO using xda app-developers app
I see exactly what you're talking about. It happened to me for the first time ever last night, on meanbean, while typing in the address bar. Only happens in the dark for me. Maybe I just don't notice it in the lighter areas. No idea what the deal is with that. Only happens with certain sites, mainly dark sites.
Delakit said:
I see exactly what you're talking about. It happened to me for the first time ever last night, on meanbean, while typing in the address bar. Only happens in the dark for me. Maybe I just don't notice it in the lighter areas. No idea what the deal is with that. Only happens with certain sites, mainly dark sites.
Click to expand...
Click to collapse
Yeah, I don't know if I should take it in to Sprint or not
Sent from my EVO using xda app-developers app
jesuscash said:
Yeah, I don't know if I should take it in to Sprint or not
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
No need. I'm pretty positive that it has nothing to do with your device.
Sent from my EVO using xda app-developers app
Related
Idk randomly my screen flickers sometimes it's very faint but it happens.. Anyone know why this would happen? Running rejuvenated now and ran mean rom before.. Help please
Sent from my EVO using xda app-developers app
joebarkho said:
Idk randomly my screen flickers sometimes it's very faint but it happens.. Anyone know why this would happen? Running rejuvenated now and ran mean rom before.. Help please
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Search and you will find your answer.
Sent from my released from customs Evo Lte!
It happens to me ONLY when using the stock texting app. See if the same happens to you.
Sent from my EVO using xda app-developers app
I dont mean to extend this thread as to there is one, but mine happens randomly, home screen sometimes, play store grey screen... random.
Same issue here see it on a daily basis. I notice it on the stock messaging app and twitter but happens other places as well.
I have had the same issue while typing on stock sms and/or just typing in general. It doesn't happen all the time but it happens.
WUESTSIDER!
Sent with my rEVOLTe, the Family JEWEL!
Anyone know what causes this any way to fix it for good
sent from my badass galaxy s3 *****
Hey... Me too!
+1
Sent from my SAMSUNG-SGH-I747 using xda premium
jmtz345 said:
Anyone know what causes this any way to fix it for good
sent from my badass galaxy s3 *****
Click to expand...
Click to collapse
I thought it was related to root but I've had these hot reboots even before rooting so it's not just root. Most likely an app.
Same problem here
Sent from my SGH-T999 using xda app-developers app
dimaf999 said:
Same problem here
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Will take a while to hunt down the app but anybody else have 'LinkedIn' app installed? It just hot rebooted while launching that app from a fresh restart - quickest hot reboot I've ever seen.
It might not be that app but then I went to the Play Store page and there are tons of 1 star reviews because the last update failed on people's phones - more interestingly the most recent comment is from a GS2 user who says latest update reboots his phone.
I've uninstalled it and I doubt I can be that lucky that it's that app and I find it so quickly but crossing my fingers.
Mine rebooted after I opened the Navigation app.
Mine is random, many different apps
Sent from my SGH-T999 using xda app-developers app
dimaf999 said:
Mine is random, many different apps
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Mine happened again. I've now uninstalled BetterBatteryStats. I'm going to start uninstalling stuff that uses root to roll that out. I've had these issues on stock but it happened rarely, lately it's been happening very frequently so something is going on.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Anyone? Developers? Any input?
Sent from my SGH-T999 using xda app-developers app
Bump this thread!
sent from my badass galaxy s3 *****
I've had the same on mine. I rooted mine day 1, so no idea if it would have done it without root. I've defrosted everything in TB and still no luck.
Sent from my rooted & debloated SCH-I535
Well I'm tired of the random hot reboots! Some people say it happened to them before rooting, but I don't believe it happened to me until I rooted and installed CWM touch......so I'm going back to stock to start all over again so I can try to narrow down the issue. I'll report back on my progress as it becomes available.
Sent from my SAMSUNG-SGH-I747 using xda premium
hanfordrob said:
Well I'm tired of the random hot reboots! Some people say it happened to them before rooting, but I don't believe it happened to me until I rooted and installed CWM touch......so I'm going back to stock to start all over again so I can try to narrow down the issue. I'll report back on my progress as it becomes available.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Happening often to me. The search continues. I've now uninstalled adfree. I'm positive this is an app since I had it occur on stock after two weeks of using the phone and installing crap.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
I had the same problem on my previous Captivate and am having it now on the GS III; no rhyme or reason to the reboots that I can see.
I still have heat problem but I played w/ different settings to see what it is.... I had att s3 which got really really hot... So returned it for Verizon s3. Verizon is better but learned that the data (lte/s3) makes it really hot and battery drain. Also the screen, of course.
If you're rooted then go get Phone info and disable lte. I tried CDMA auto for Verizon and it got much better... But at lowered download speed. I change it when I speed the speed... Doesn't require reboot so it's easy to change.
U can also under clock using setCPU.
I don't need it to be fast normally except when playing games... So just have it at 384min and 1024max... I find this helps allot w/ heat as well... U can try and find your setting that's acceptable speed and heat.
Just sharing my experience here.... So good luck.
Sent from my SCH-I535 using Tapatalk 2
Happens here too with the T-Mobile GS3. I think they rushed their fabrication process to deliver a high volume and fubared a few hardwarewise. I've even had it lockup/freeze once when not even in the OS but just in the recovery menu's. But yeah, the usual is a totally random unpredictable hot reboot throwing out my resident programs, homescreen, ect. Starts with the screen being frozen and not accepting input, then a short vibration, then back to homescreen reloading and all regular apps and widges that are supposed to run at boot load again. It's as if there's a micro static short or something. Anyway, I'm sick of problem solving and looking through logcats. Going back in for warranty. This is a dream phone except for this ultra annoying bug that it seems not many people have.
the-Mike_D said:
Happens here too with the T-Mobile GS3. I think they rushed their fabrication process to deliver a high volume and fubared a few hardwarewise. I've even had it lockup/freeze once when not even in the OS but just in the recovery menu's. But yeah, the usual is a totally random unpredictable hot reboot throwing out my resident programs, homescreen, ect. Starts with the screen being frozen and not accepting input, then a short vibration, then back to homescreen reloading and all regular apps and widges that are supposed to run at boot load again. It's as if there's a micro static short or something. Anyway, I'm sick of problem solving and looking through logcats. Going back in for warranty. This is a dream phone except for this ultra annoying bug that it seems not many people have.
Click to expand...
Click to collapse
Are any of you have this happen purely on stock without rooting or anything else ?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
mobilehavoc said:
Are any of you have this happen purely on stock without rooting or anything else ?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Happened to me once or twice (that I noticed) in the two weeks before I rooted (stock UCALEM), and a few more times after. It's just TouchPiz being pizzy. Maybe someone can catch the logcat, but there's nothing we can do about it (except install a better ROM )
How would anyone be able to diagnose this BS
"OK. My phone is hot. And it randomly reboots".
"Crap - u r out of luck buddy. Go change ur damn phone".
Provide ur phone model, ROM version, apps installed. Check ur battery stats.
As a solution - flash any custom ROM which removes bloatware.
I feel like my phone is REALLY slowing down, almost at the hardware level.
Pressing the power button the reaction time to turn the screen on varies, sometimes right away, sometimes a full second later.
When I wiped my cache and dalvik from recovery it took a good 30 seconds(its normally a 5 second wipe) and while backing up can take some time, it felt like it took 3 times as long.
Is there a hardware issue with the phone or could it possibly be a kernel problem?
Fully Unlocked running Beants 17 moving to 18 to see if it helps..
Hitman3984 said:
I feel like my phone is REALLY slowing down, almost at the hardware level.
Pressing the power button the reaction time to turn the screen on varies, sometimes right away, sometimes a full second later.
When I wiped my cache and dalvik from recovery it took a good 30 seconds(its normally a 5 second wipe) and while backing up can take some time, it felt like it took 3 times as long.
Is there a hardware issue with the phone or could it possibly be a kernel problem?
Fully Unlocked running Beants 17 moving to 18 to see if it helps..
Click to expand...
Click to collapse
Mine was acting like that for the past few days, I had Beans 17 with Perseus. It even got to the point that I posted a thread asking for Kernel suggestions, because it was fine with Sabre, so I was thinking it may have been Perseus or my settings since I had tweaked Perseus.
When 18 came out I did a clean install, and this time just for the heck of it I went with Faux. So far I haven't had the sluggish performance and haven't regretted my choice. Downside is I have no idea what was causing it since I did a clean install. It may have been the kernel, the rom, any number of settings, or any number of apps.
Sorry not the most helpful in the world, but at least it should give you a ray of hope.
rbowen87 said:
Mine was acting like that for the past few days, I had Beans 17 with Perseus. It even got to the point that I posted a thread asking for Kernel suggestions, because it was fine with Sabre, so I was thinking it may have been Perseus or my settings since I had tweaked Perseus.
When 18 came out I did a clean install, and this time just for the heck of it I went with Faux. So far I haven't had the sluggish performance and haven't regretted my choice. Downside is I have no idea what was causing it since I did a clean install. It may have been the kernel, the rom, any number of settings, or any number of apps.
Sorry not the most helpful in the world, but at least it should give you a ray of hope.
Click to expand...
Click to collapse
Did a clean install to 18 and used beans kernel and still having the issues
Sent from my SCH-I605 using xda app-developers app
Hitman3984 said:
Did a clean install to 18 and used beans kernel and still having the issues
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
Then try a different kernel like Faux, Sabre, or any of the other TW kernels.
Sent from my SCH-I605 using XDA Premium HD app
Hitman3984 said:
Did a clean install to 18 and used beans kernel and still having the issues
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
Try to wipe cache, dalvik-cache, data, and system for 3 times.
Factory reset for 2 times.
Then install the ROM again.
Edit:
Also verify the MD5 to make sure you have a good download of the ROM.
torr310 said:
Try to wipe cache, dalvik-cache, data, and system for 3 times.
Factory reset for 2 times.
Then install the ROM again.
Click to expand...
Click to collapse
Ill have to give it a shot. Thanks
Sent from my SCH-I605 using xda app-developers app
a second or two delay for the screen to turn on is normal with tw roms. the cpuhas to come out of sleep and there is an average of about 1.7 sec delays.
themichael said:
a second or two delay for the screen to turn on is normal with tw roms. the cpuhas to come out of sleep and there is an average of about 1.7 sec delays.
Click to expand...
Click to collapse
Bingo! Especially if you have S-voice activated. I don't know if it comes activated automatically on Beans on not though.
Sent from my SCH-I605 using XDA Premium HD app
No s voice and the delay is noticeable enough that it's not normal from a week ago. And like I said it's effecting other things, backup speeds etc
Sent from my SCH-I605 using xda app-developers app
Hitman3984 said:
No s voice and the delay is noticeable enough that it's not normal from a week ago. And like I said it's effecting other things, backup speeds etc
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
If I were you I would try booting into recovery and wiping the cache, if that doesn't fix it I would suggest trying some of the excellent kernels we have. That's your best bet.
Sent from my SCH-I605 using XDA Premium HD app
Try turning off window animation scale, transition animation scale, animator duration scale. It is located in settings under developer options. Sped up my phone.
i605 rooted, stock rom and pimped out.
Sent from my SCH-I605 using xda app-developers app
I've had the same slowness problem. I dont think it has to do with the kernel. I am using Perseus and after installing 17 then 18 the slowness happened after using it for a while. I think it has to do with a certain app I dl'd although I havent had the time to start fresh and see which app is causing the delay.
Ok, so I froze S-voice in titanium backup, then wiped cache in twrp, rebooted and it worked!! The home button delay is gone when switching from other screens to my home screen. I defrosted S-voice and so far so good, my note 2 is still very responsive.
Lets see if the delay happens again. If it does I will clear cache without defrosting S-voice to see which one was the culprit. I would tend to agree with shangrila500 that its the cache.
pharmnatr said:
Ok, so I froze S-voice in titanium backup, then wiped cache in twrp, rebooted and it worked!! The home button delay is gone when switching from other screens to my home screen. I defrosted S-voice and so far so good, my note 2 is still very responsive.
Lets see if the delay happens again. If it does I will clear cache without defrosting S-voice to see which one was the culprit. I would tend to agree with shangrila500 that its the cache.
Click to expand...
Click to collapse
Set s voice to not open when you double click the home button. Unless I misread this thread. That causes alot of delay. Hell I never even use s voice anymore haha
Sent from my SCH-I605 using Tapatalk 2
hopesrequiem said:
Set s voice to not open when you double click the home button. Unless I misread this thread. That causes alot of delay. Hell I never even use s voice anymore haha
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
It never occurred to me that the "open s-voice by double clicking home button" setting might be slow down my responsiveness but thats the case. Unchecking the box has made a noticeable difference.
pharmnatr said:
It never occurred to me that the "open s-voice by double clicking home button" setting might be slow down my responsiveness but thats the case. Unchecking the box has made a noticeable difference.
Click to expand...
Click to collapse
I only remember that from the s3. It was a legit night and day difference haha. Thought the home button was broken on that phone till I tried that
Sent from my SCH-I605 using Tapatalk 2
Has anyone experienced issues with the screen sensor not responding well while on a call?
Sometimes if you lock the screen while on a call and you try to unlock it the screen with shut off as soon as you touch it and will remain on that behavior until the call is ended, therefore not letting you unlock the phone or perform any other activities on the phone.
Anyone?
Sent from my HTC One using Tapatalk 2
Yes! It happens to me rather frequently. Thanks for starting this post. Hopefully someone can shed some light on this.
Sent from my HTC One using xda app-developers app
girlygirl00 said:
Yes! It happens to me rather frequently. Thanks for starting this post. Hopefully someone can shed some light on this.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
It's funny because this is the 2nd HTC phone that I can report with this bug. I had the Evo 4G LTE before this one and it suffered the same issue even after all official updates.
The only solution with that phone was to flash a custom ROM which was good, but up to now I'm still on the fence about rooting this one; stock on this phone is stable and bloatware is minimal, I haven't justified taking the plunge yet.
Sent from my HTC One using Tapatalk 2
I'm with you there. I did root mine... but only for data restore purposes. It may sound crazy.. but I don't want SwiftKey to start over with learning my typing habits. Other than that, like you, this phone and my Nexus 4 are the only two phones that I have had no desire to install a custom ROM. Fingers crossed that there is a solution other than that.
Sent from my HTC One using xda app-developers app
megabiteg said:
Has anyone experienced issues with the screen sensor not responding well while on a call? Anyone?
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Yes, happened with me quite a few times. Once a call is initiated (phone speaker on or off) and the screen goes black (due to proximity sensor), no amount of tinkering will bring it back until you press the power button which kills the call. It is damn annoying and am hoping there is a fix.
The phone is on 1.29 M7 TMobile ROM, rooted with S-OFF
I had that problem too on LG L7. Tried with various roms and nothing. But I fixed somehow with the app called "proximity actions". It lets you command your phone with hand suggestion via proximity sensor. I only installed it to check the hardware, wether the sensor works. I have no idea what happened, but it started to work again. The app somehow toggled the sensor and brought it back to life.
Sent from my LG-P700 using xda app-developers app
Not sure if all ROMs have the option but you can go in to the accessibility options and turn off power button ends call.
Sent from my HTC One using xda app-developers app
I've noticed this issue has significantly increased amongst other things like freezing since I unlocked my bootloader. :what:
Sent from my HTC One using xda premium
sbihue said:
Yes, happened with me quite a few times. Once a call is initiated (phone speaker on or off) and the screen goes black (due to proximity sensor), no amount of tinkering will bring it back until you press the power button which kills the call. It is damn annoying and am hoping there is a fix.
The phone is on 1.29 M7 TMobile ROM, rooted with S-OFF
Click to expand...
Click to collapse
Never once has this happened to me. Bone stock.
Guess that's another reason I don't trust "IMAROM CHEFS!" ROMs that are "cooked up" on some random internet user's computer.
Stock is fine these days, IMO. Outgrew the glitchy nature of kitchen ROMs and such.
ericshmerick said:
Never once has this happened to me. Bone stock.
Guess that's another reason I don't trust "IMAROM CHEFS!" ROMs that are "cooked up" on some random internet user's computer.
Stock is fine these days, IMO. Outgrew the glitchy nature of kitchen ROMs and such.
Click to expand...
Click to collapse
Been using ROMs for years and I've hand,y ups and downs, I can't say I've had a horrible experience with any ROM I've used on any of my past phones. Now I do agree with you about the stability of stock ROMs these days and also the better specs of the phone. For instance I haven't rooted nor unlocked my phone because I personally feel that the delivered product is good and haven't felt the necessity to tinker with it. The issue described is with stock, not custom ROM.
With that said or you haven't had the scenario for it to happen or your just the lucky one....
Sent from my Nexus 7 using Tapatalk 2
im currently running ViperA1.7.1 I was previously using Energy_8.6.2012.Amaze.Sense.3.6_ICS both worked well no problems, but after about a week or so I start getting wifi errors and have to reflash the rom. ive done this numerous times and it gets tiresome having to set everything up again. is there a reason why I get wifi errors periodically ?
I'm not sure. But Viper is funny with wifi. Only with Viper I can't sign into my college wifi. Either way. Back up, format all partitions (except sd) , flash and restore?
Sent from my Amaze 4G using Tapatalk 4
oh ok whats another rom I should try ? I did the format, flash, and restore but wifi still isn't working.
hrsa_13 said:
oh ok whats another rom I should try ? I did the format, flash, and restore but wifi still isn't working.
Click to expand...
Click to collapse
Super Sense 3.2 Choose wipe all when installing it.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
SuperAfnan said:
Super Sense 3.2 Choose wipe all when installing it.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
installed super sense but it just boots into htc white logo screen
update: re flashed and it worked, but this morning when I got up I got the wifi error again.
I have the same problem!
Sent from my Amaze 4G using XDA Premium 4 mobile app
hrsa_13 said:
installed super sense but it just boots into htc white logo screen
update: re flashed and it worked, but this morning when I got up I got the wifi error again.
Click to expand...
Click to collapse
thelordofkings97 said:
I have the same problem!
Sent from my Amaze 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Alright here we go,
If you haven't done so already, flash the most stable T-Mobile RUU. The most stable is not the latest. If you are S-OFF then you don't need to relock the bootloader. The RUU is NOT a stock custom ROM, it's a program that flashes the original stock ROM onto your phone and usually fixes all software related issues.
Check to see if Wi-Fi works. You can unlock the bootloader again if you're not S-OFF then re-root.
Now you may flash a ROM. :thumbup:
Sent from my SAMSUNG-SGH-I747 using Tapatalk
SuperAfnan said:
Alright here we go,
If you haven't done so already, flash the most stable T-Mobile RUU. The most stable is not the latest. If you are S-OFF then you don't need to relock the bootloader. The RUU is NOT a stock custom ROM, it's a program that flashes the original stock ROM onto your phone and usually fixes all software related issues.
Check to see if Wi-Fi works. You can unlock the bootloader again if you're not S-OFF then re-root.
Now you may flash a ROM. :thumbup:
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
On this one I don't know if I can agree with you. Here in Miami, where T-Mobile has already finished refarming and reallocating its bandwidth from the Metro acquisition my WiFi and data is better than ever with the latest baseband. My connection is both fast and stable, and I don't have a single issue. This wasn't the case a couple of months ago, but then a call to T-Mobile tech support resulted in them giving me a new SIM card which resolved all of my problems. My previous SIM card was only 6 months old at the time, but tech support informed me of changes in how the new cards are programmed to take advantage of the new post merger configurations. Like I said, my service and connectivity is now the best it's ever been with the latest radio ruu.
SuperAfnan said:
Alright here we go,
If you haven't done so already, flash the most stable T-Mobile RUU. The most stable is not the latest. If you are S-OFF then you don't need to relock the bootloader. The RUU is NOT a stock custom ROM, it's a program that flashes the original stock ROM onto your phone and usually fixes all software related issues.
Check to see if Wi-Fi works. You can unlock the bootloader again if you're not S-OFF then re-root.
Now you may flash a ROM. :thumbup:
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
I need your help!!! My bootloader was unlocked... and then i flash the t-mobile RUU!!! but i still have the problem ... what should i do ?!?! (
Does it say "Wi-Fi error" when you turn Wi-Fi on? I mean in the settings menu where it normally says "connected to..."
If it does you have a hardware issue.
There are two tricks to try.
1. Clean the little gold connectors on the back cover of your case. Those are the antenna connectors. Use a rubber eraser on a pencil. Get all the rubber shavings out before you reassemble.
2. There it's a tin foil trick that is a hardware mod. There a thread on it with pictures. The jist of it it's to put foil over the connectors to give it a bigger antenna. There are pros and cons of doing this. I did this for a while and didn't really see any results.
The Wi-Fi issues generally with earlier versions of viper amaze were from modules that didn't match the kernel. That has been resolved since before I added the aroma installer.
Also, one last thing. If you have two amazes ruining viper, they screw up the Wi-Fi. Going from sense 3.5 to sense 4.1 and up, there's something weird about how the phone gets its address, so if my dev device is on and Wi-Fi is on and my daily phone is on with Wi-Fi on, I don't get Wi-Fi on either.
Hope that helps!
Sent from my HTC Amaze using XDA Premium 4 mobile app
chevycowboyusa said:
Does it say "Wi-Fi error" when you turn Wi-Fi on? I mean in the settings menu where it normally says "connected to..."
If it does you have a hardware issue.
There are two tricks to try.
1. Clean the little gold connectors on the back cover of your case. Those are the antenna connectors. Use a rubber eraser on a pencil. Get all the rubber shavings out before you reassemble.
2. There it's a tin foil trick that is a hardware mod. There a thread on it with pictures. The jist of it it's to put foil over the connectors to give it a bigger antenna. There are pros and cons of doing this. I did this for a while and didn't really see any results.
The Wi-Fi issues generally with earlier versions of viper amaze were from modules that didn't match the kernel. That has been resolved since before I added the aroma installer.
Also, one last thing. If you have two amazes ruining viper, they screw up the Wi-Fi. Going from sense 3.5 to sense 4.1 and up, there's something weird about how the phone gets its address, so if my dev device is on and Wi-Fi is on and my daily phone is on with Wi-Fi on, I don't get Wi-Fi on either.
Hoe that helps!
Sent from my HTC Amaze using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You forgot the "p" in hope
Sent from my HTC_Amaze_4G using xda app-developers app
KT-82166 said:
You forgot the "p" in hope
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Sorry, I'm a cowboy. My spell checker doesn't correct things like that because I use words like hoe down....
Sent from my HTC Ruby using XDA Premium 4 mobile app
It could have been worse.
KT-82166 said:
You forgot the "p" in hope
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
I have seen much worse here. Some people spell "Chevy" as "CHAVY". I even saw someone spell Chevy as "Chewy". I want to cry because it was so bad but I can't. -_-
Someone spelled my name as "Superafman" once, I think it was shubham.
It can't really be helped.
If XDA had a voice-messaging feature and we could record our voices and send them, you will be surprised at how funny people on this forum will sound!
SuperAfnan said:
I have seen much worse here. Some people spell "Chevy" as "CHAVY". I even saw someone spell Chevy as "Chewy". I want to cry because it was so bad but I can't. -_-
Someone spelled my name as "Superafman" once, I think it was shubham.
It can't really be helped.
If XDA had a voice-messaging feature and we could record our voices and send them, you will be surprised at how funny people on this forum will sound!
Click to expand...
Click to collapse
Ha Ha Ha! I saw some of those. By the way the first time I saw your name I thought it was SuperAfrican
Sent from my HTC_Amaze_4G using xda app-developers app
KT-82166 said:
Ha Ha Ha! I saw some of those. By the way the first time I saw your name I thought it was SuperAfrican
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Lol yeah my first name is Afnan. Some people never had good opportunities to learn English so I can't say it's entirely their fault.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Lol, I've been abridged.... It started as chevycowboyusa. Now it's just Chevy, but that works for me.
I'm not chubby, nor am I chewy.
Lmao
Had to edit this three times. Stupid spell checker!
Sent from my HTC Ruby using XDA Premium 4 mobile app