Related
I've tried about many ROM's such as miui, CM7, decks, etc.... I've had no luck, the wifi is just so horrible in many places where in a sense ROM I'd have perfect wifi or good, compared to poor wifi disconnecting after a while.
Thanks for reading Anyone have a solution?
I use CM7 and have absolutely no problem with my wifi. Have you tried CM7? If so, have you tried anything else?
UndeadCircus said:
I use CM7 and have absolutely no problem with my wifi. Have you tried CM7? If so, have you tried anything else?
Click to expand...
Click to collapse
Yeah I've tried it just bit ago and the past days as well but I'm sure it isn't a hardware issue because on nrg 3.5 rom from Nov18 my wifi works perfect where I would I couldn't get wifi signal at all on cm.
The problem is that sense doesn't show the right signal. Compare the speeds and you'll see what I mean
Sent from my PC36100 using Tapatalk
Crossrocker said:
The problem is that sense doesn't show the right signal. Compare the speeds and you'll see what I mean
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
It has nothing to do with speed, please read what I said... I lose signal on aosp ROM's on common areas that I get nearly excellent coverage in, note I tested this with airplane mode on to ensure my wifi doesn't disconnect and switch to 3G. A couple of other others on the miui thread have also said that same.
I'm using the new aosp ROM ice cream sandwich for my phone and wifi works like a charm. Using it now
Sent from my Nexus S 4G using XDA App
xyience said:
I'm using the new aosp ROM ice cream sandwich for my phone and wifi works like a charm. Using it now
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
I'm guessing it has a new kernel? I will flash it tomorrow to see how it works, just to clarify, you are talking about the alpha build right?
CaliBoyPhillip said:
It has nothing to do with speed, please read what I said... I lose signal on aosp ROM's on common areas that I get nearly excellent coverage in, note I tested this with airplane mode on to ensure my wifi doesn't disconnect and switch to 3G. A couple of other others on the miui thread have also said that same.
Click to expand...
Click to collapse
I don't think you understand what I said. Sense shows the wrong wifi signal. It shows 3 bars for me while aosp shows 1. Aosp shows true signal because I am far from the router
Having trouble with AOSP? http://forum.xda-developers.com/showthread.php?t=1295702
Are you using the included kernel or flashing custom ones? While your signal may show lower, you shouldn't notice a drop in actual connectivity. Flashing an incompatible kernel, like a Sense kernel, can mess up your wifi.
I'm on MIUI right now showing a full wifi signal. I haven't used Sense in a very long time, but I don't remember getting better wifi reception while I was using it. I'm using Tiamat right now, maybe try a different kernel next time you flash AOSP and see if that helps. There are also a few tweaks you can do to help with your wifi signal, like changing the wifi scan interval in build.prop, but I haven't actually done anything like that since my signal is fine.
Supersonic Evo 4G | MIUI | Tapatalk
plainjane said:
Are you using the included kernel or flashing custom ones? While your signal may show lower, you shouldn't notice a drop in actual connectivity. Flashing an incompatible kernel, like a Sense kernel, can mess up your wifi.
I'm on MIUI right now showing a full wifi signal. I haven't used Sense in a very long time, but I don't remember getting better wifi reception while I was using it. I'm using Tiamat right now, maybe try a different kernel next time you flash AOSP and see if that helps. There are also a few tweaks you can do to help with your wifi signal, like changing the wifi scan interval in build.prop, but I haven't actually done anything like that since my signal is fine.
Supersonic Evo 4G | MIUI | Tapatalk
Click to expand...
Click to collapse
I've been sticking to the stock kernel that the ROM's have and savaged. I'll give the tiamat kernel a try with miui, what Tiamat version are you using so I can try it if not maybe I'll try getting a phone replacement to see if I might have a fault or evil mojo evo that hates aosp lol! hardware 004 here.
CaliBoyPhillip said:
I've been sticking to the stock kernel that the ROM's have and savaged. I'll give the tiamat kernel a try with miui, what Tiamat version are you using so I can try it if not maybe I'll try getting a phone replacement to see if I might have a fault or evil mojo evo that hates aosp lol! hardware 004 here.
Click to expand...
Click to collapse
I've heard that 004s can be problematic, I have a 003 and only get issues when I go a while without wiping fully. I'm using 4.1.0 right now, start there and maybe try other versions if you want. I ran SZ for a while and it started off smooth but eventually got laggy and unresponsive at times despite anything I would do (wiping caches, etc). Switched back to Tiamat and all has been working well since.
Give it a go, if it doesn't work for you then maybe it's some kind of hardware issue. Just to be sure, do a full wipe and try to avoid restoring anything unless you absolutely have to - definitely don't restore system data. Unfortunately you can't take your phone in to Sprint and get a replacement since your wifi is dodgy on AOSP. If it happened on stock then you might have a case.
Supersonic Evo 4G | MIUI | Tapatalk
plainjane said:
I've heard that 004s can be problematic, I have a 003 and only get issues when I go a while without wiping fully. I'm using 4.1.0 right now, start there and maybe try other versions if you want. I ran SZ for a while and it started off smooth but eventually got laggy and unresponsive at times despite anything I would do (wiping caches, etc). Switched back to Tiamat and all has been working well since.
Give it a go, if it doesn't work for you then maybe it's some kind of hardware issue. Just to be sure, do a full wipe and try to avoid restoring anything unless you absolutely have to - definitely don't restore system data. Unfortunately you can't take your phone in to Sprint and get a replacement since your wifi is dodgy on AOSP. If it happened on stock then you might have a case.
Supersonic Evo 4G | MIUI | Tapatalk
Click to expand...
Click to collapse
I've been using the tiamat for now and it seems more stable on wifi, funny though, the wifi seemed bad on the default miui kernel. I also moved my router to a higher place on a shevel with nothing steel or bad around it. Oh and don't worry my local sprint store in Los angeles is a big time Hispanic corporate... they replace devices for any complaining here to avoid issues with the people lol! I got to love it.
Edit: you are leet according to your post count ahaha.
check it out
CaliBoyPhillip said:
I've tried about many ROM's such as miui, CM7, decks, etc.... I've had no luck, the wifi is just so horrible in many places where in a sense ROM I'd have perfect wifi or good, compared to poor wifi disconnecting after a while.
Thanks for reading Anyone have a solution?
Click to expand...
Click to collapse
i used to have a problem like this, click in the link in my sig and go to the Q&A section in it and follow the steps on how to fix the wifi issue. if you have any questions or anything feel free to post it in that thread. hope i helped ^_^
Well i have a big problem, i'm using the DINC2 over a GSM network with the 900Mhz freq for 3G.
I had the 2.3.4 then i downgraded the rom to 2.3.3 using the method posted in the development section.
Then installed CM7 and everything was perfect until the moment i made a nandroid backup, after that the handset went crazy, first dropping the 3G until the point that it drops the signal completely not even gsm.
I have tried several radio version and the problem persists, i'am willing to go back to official 2.3.4 if the problem is solved but again since i'm not in the US i cannot upgrade the device via OTA.
I need help i cannot use it without 3G.
EDIT: I managed to get it to work stable at 2G, but whenever it makes the handover to 3G it drops the signal completely and return back to 2G, it works stable if i leave it in GSM only.
Have you found anything out? This us exactly what my phone is doing. Installed touch pros beta 3 ICS and had a sporatic signal (like it'd be fine and for no reason I'd have no service). Yesterday I installed beta 6 and everythings fine until I got it set up and did a nandroid. I am using the 722 radio, but saw a little about a 1111 radio...have u tried that radio?
Touchpros ics rom does not officially support GSM, it works in general but there is no support for it. This means that you can use ics but there are multiple issues, like the radio dying when you restart your phone.
So you can use it but remember it is not finished
yurilebbie said:
Touchpros ics rom does not officially support GSM, it works in general but there is no support for it. This means that you can use ics but there are multiple issues, like the radio dying when you restart your phone.
So you can use it but remember it is not finished
Click to expand...
Click to collapse
I just read Touchpro won't be supporting this ROM any longer, do you know of this is true? Or will there be further development with it? I really like it so far but not sure I can deal with this radio issue...thanks for the input!
Sent from my Incredible 2 using XDA App
forgiven90 said:
Have you found anything out? This us exactly what my phone is doing. Installed touch pros beta 3 ICS and had a sporatic signal (like it'd be fine and for no reason I'd have no service). Yesterday I installed beta 6 and everythings fine until I got it set up and did a nandroid. I am using the 722 radio, but saw a little about a 1111 radio...have u tried that radio?
Click to expand...
Click to collapse
Tried that radio but is the same bro.
Sent from my U8800Pro using xda premium
Been running AOKP for quite some time now but I've been getting random blackouts lately where my phone will show zero bars of service with an X through it and it will come back within 30 seconds but it has been known to drop calls and it generally just ****s everything up. Happens a few times daily. Anyone else?
I've been running AOKP build 36 and Franco Kernel r166. I have experienced a couple data drops. It rarely ever happens for me.
What build and kernel are you running?
Syn Ack said:
Been running AOKP for quite some time now but I've been getting random blackouts lately where my phone will show zero bars of service with an X through it and it will come back within 30 seconds but it has been known to drop calls and it generally just ****s everything up. Happens a few times daily. Anyone else?
Click to expand...
Click to collapse
Maybe try wiping cache/dalvik?
i heard it's an issue with most if not all 4.0.4 builds out right now. some people suggest trying different kernels, others just say to do a clean install, etc. The only time it really happens to me is when connect to wifi, then disconnect. it doesn't go connect my data unless i reboot. can still get calls/texts though. this was on milestone5. I just upgraded to b38 and it may have cleared up, but i'll keep running tests.
soapbox23 said:
Maybe try wiping cache/dalvik?
i heard it's an issue with most if not all 4.0.4 builds out right now. some people suggest trying different kernels, others just say to do a clean install, etc. The only time it really happens to me is when connect to wifi, then disconnect. it doesn't go connect my data unless i reboot. can still get calls/texts though. this was on milestone5. I just upgraded to b38 and it may have cleared up, but i'll keep running tests.
Click to expand...
Click to collapse
Hmmm, I always wipe everything good when I install new builds. I also usually use Franco kernel, sometimes the AOKP kernel when I'm lazy or forget to install Franco.
This is a known issue with AOKP and also Franco's kernel.
Good to know thanks.
More like it is a known issue with AOSP in general from reading around as CM has it as well.
Sent from my Galaxy Nexus using xda premium
I was having the SAME EXACT issues, I fixed it 100% buy doing a full wipe (user + system data, plus dalvik) through recovery, and re-installing the most current CM9 Nightly (6/3/2012 for me) and now my phone hasn't dropped the signal ONCE in the 8+ hours I have been using it heavily.
I'm thinking the full wipe was all it needs and the ROM doesn't really matter, but I read somewhere (probably here) that if you underclock your CPU to anything below 400 Mhz then it will have issues connecting to the towers, I don't know how accurate that is, but I can confidently say that I have my Nexus back!
I'm using the most recent radios included in CM9 Toro 6/3/2012 which are the newest ones that Verizon pushed out with their 4.0.4 update.
My battery life is horrible now but I could care less at this point (4 months with a shoddy signal).
Liskrig said:
I was having the SAME EXACT issues, I fixed it 100% buy doing a full wipe (user + system data, plus dalvik) through recovery, and re-installing the most current CM9 Nightly (6/3/2012 for me) and now my phone hasn't dropped the signal ONCE in the 8+ hours I have been using it heavily.
I'm thinking the full wipe was all it needs and the ROM doesn't really matter, but I read somewhere (probably here) that if you underclock your CPU to anything below 400 Mhz then it will have issues connecting to the towers, I don't know how accurate that is, but I can confidently say that I have my Nexus back!
I'm using the most recent radios included in CM9 Toro 6/3/2012 which are the newest ones that Verizon pushed out with their 4.0.4 update.
My battery life is horrible now but I could care less at this point (4 months with a shoddy signal).
Click to expand...
Click to collapse
Well there ya go, Franco stock settings have a low end of 384Mhz I believe.
I was on AOKP b37 with the 4.0.4 radios on my old phone and had the same problems, but they happened from day 1 on stock software and were what caused me to root. If you always had the problem before rooting, then it is more than likely the phone. Full wipes didn't work, new radios didn't work, only getting a new phone worked.
It is a problem with AOSP..
Sent from my Galaxy Nexus using xda premium
joshnichols189 said:
It is a problem with AOSP..
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
So, should I wait for a fix, or wipe everything and install Gummy's rom?
Because it's having a phone without it's functionality www4.slikomat.com/11/0605/rew-DSC004.jpg
I have no issues on build 38 running ezekeels kernel 1.34
does gummy have the compass fixed all roms are backwards and that sucks
Chopders said:
So, should I wait for a fix, or wipe everything and install Gummy's rom?
Because it's having a phone without it's functionality www4.slikomat.com/11/0605/rew-DSC004.jpg
Click to expand...
Click to collapse
Gummy is made from AOSP..
Sent from my Galaxy Nexus using xda premium
Chopders said:
So, should I wait for a fix, or wipe everything and install Gummy's rom?
Because it's having a phone without it's functionality www4.slikomat.com/11/0605/rew-DSC004.jpg
Click to expand...
Click to collapse
No, return it to stock and have Verizon send you a new one.
Running AOKP B38 + Franco M3, and NEVER had this issue. Always clean install, and even in AOKP M5, up to every build leading to 38, never had data connection issues.
Sent from my Galaxy Nexus running AOKP+Franco
I was having the same issue with data drops happening on a regular basis even in strong LTE areas to the gray X. I tried flashing every radio out there and several roms and never fixed it. finally got VZ to send me a replacement and the new one works flawlessly, zero drops.
I'd just get it replaced.
I've been able to fix this problem by running the UGLC1 kernel. Also make sure your RIL matches your radio: https://play.google.com/store/apps/...t=W251bGwsMSwxLDMsImNvbS5zaWJib3IuZ2V0cmlsIl0.
After flashing UGLC1 and making sure my RIL matches I haven't dropped signal once.
Tynen said:
I've been able to fix this problem by running the UGLC1 kernel. Also make sure your RIL matches your radio: https://play.google.com/store/apps/...t=W251bGwsMSwxLDMsImNvbS5zaWJib3IuZ2V0cmlsIl0.
After flashing UGLC1 and making sure my RIL matches I haven't dropped signal once.
Click to expand...
Click to collapse
+1 to this
https://play.google.com/store/apps/details?id=com.sibbor.getril
Sent from my Galaxy Nexus using Tapatalk 2
android01 said:
+1 to this
https://play.google.com/store/apps/details?id=com.sibbor.getril
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I still agree
Sent from my Galaxy Nexus using xda premium
hey guys im new to the forum.
i have a rooted nexus (maguro) on the Three "3" network in the UK and i was running AOKP for around 8 months with no signal problems at all. I flashed a new rom(jellybean) back in august and now my signal drops around every few mins and then comes back for a few mins and drops again. I have tried restoring to my old AOKP backup and the problem continues. i have flashed other jb roms and tried all different ril's using getril off the market but i just cant seem to stop this problem.
can anyone help? would be very much appreciated, thanks.
Try the app GetRIL and look if you have the right RIL and Baseband. If you don' have the right, you can change it ith the app.
Sent from my Galaxy Nexus using xda premium
Thyria said:
Try the app GetRIL and look if you have the right RIL and Baseband. If you don' have the right, you can change it ith the app.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
hey, that's what ive been trying but even when i have a matching RIL and Baseband i still get the signal loss. i know it isn't my network as my gf is on the same network and her signal is fine
Try a different radio?
http://forum.xda-developers.com/showthread.php?t=1405345
Anyway, the GSM antenna on the Nexus is not the best around, so you may get slightly worse signal compared to other phones.
Mach3.2 said:
Try a different radio?
http://forum.xda-developers.com/showthread.php?t=1405345
Anyway, the GSM antenna on the Nexus is not the best around, so you may get slightly worse signal compared to other phones.
Click to expand...
Click to collapse
Thanks. If i flash a new radio will that then be on the phone even if i flash a new rom? or will i have to reflash the radio again after a new rom has been flashed?
addles said:
Thanks. If i flash a new radio will that then be on the phone even if i flash a new rom? or will i have to reflash the radio again after a new rom has been flashed?
Click to expand...
Click to collapse
custom rom zips don't include any radio.
flashing a stock google image using fastboot will flash the radio over.
I have the same problem with you, but i am in Vodafone's network in Greece.
When i flashed the first aokp jb i started having problems with disconnections. The XXLF1 radio was extremely buggy.
Then i tried a ics rom and downgraded my radio to matching xxla2. But the problem remained so i changed back to aokp jb again.
Now i still have a buggy radio (total signal loss, data drops) but not so much as before.
It might be a problem with the frequencies each carrier use. I say that because when i had "2G only" enabled i had no signal but when i turned on 3G i had three bars at the same spot.
Anyway, i hope they release a better radio on the next update.
Sent from my AOKP Nexus using xda Premium
EliasKir said:
I have the same problem with you, but i am in Vodafone's network in Greece.
When i flashed the first aokp jb i started having problems with disconnections. The XXLF1 radio was extremely buggy.
Then i tried a ics rom and downgraded my radio to matching xxla2. But the problem remained so i changed back to aokp jb again.
Now i still have a buggy radio (total signal loss, data drops) but not so much as before.
It might be a problem with the frequencies each carrier use. I say that because when i had "2G only" enabled i had no signal but when i turned on 3G i had three bars at the same spot.
Anyway, i hope they release a better radio on the next update.
Sent from my AOKP Nexus using xda Premium
Click to expand...
Click to collapse
Refer to the link I included above, try different radios and remember to match the RIL.
Will the next nexus have a longer screen?
I'm just trying to keep these straight, since I've seen bits and pieces of various problems on the various dev threads. Would someone be so kind as to check my logic here? Thanks in advance!
Problem: Can't get a GPS lock after flashing any AOSP-based 4.3 rom
Solution: Flash back to stock (RUU?), open up Maps or otherwise get a good GPS lock, flash back to your rom of choice
Burning Question: Why does this happen and why does stock flashing work?
(Idiot Newbie Question: RUU is basically a stock image? I need an encrypted version? Do I need to worry about breaking my rumrunner s-off/root?)
Problem: When on a phone call, and the other party hangs up, you get "call lost" instead of the standard graceful disconnect.
Solution: Isn't one yet. Gotta wait for a fix to be made.
Problem: Signal strength meter shows impossibly low values, despite data, voice, LTE all working as expected.
Solution: No idea. Of the 3 roms I've tried, (CM10, Liquid, Carbon), all do this. Minor problem, but anyways.
Problem: Purplish tint on the camera in dark scenes.
Solution: Phone's defective, send it in. / Or: Wait for a software patch.
Which is it?
@Karunamon
Problem 1. Not really figured out yet. All you need to do is flash any Sense rom.
Problem 2. Is fixed! For a couple of days now for any ROM built after 11th of this month.
Problem 3. I get the same dBm on Sense and AOSP. Sure a lot of other people do also. But people panic when looking at the network bars.
Problem 4. I get no purple/pink tint when on Sense but after flashing AOSP I get the purple/pink tint on my FFC. So I would wait til 4.3.
Is the issue with AOSP roms killing the radios on certain phones fixed as of the 11th?
adrenalinemotion said:
Is the issue with AOSP roms killing the radios on certain phones fixed as of the 11th?
Click to expand...
Click to collapse
That isn't AOSP fault. Something was happening after the s-off procedures that people need to do a factory reset from HBOOT before flashing anything to reset their radio
Sent from my One using Tapatalk now Free
Flyhalf205 said:
That isn't AOSP fault. Something was happening after the s-off procedures that people need to do a factory reset from HBOOT before flashing anything to reset their radio
Sent from my One using Tapatalk now Free
Click to expand...
Click to collapse
I s-off'd, unlocked my bootloader and rooted with no issues. I was stock rooted and everything functioned. As soon as I flashed an AOSP rom, the radio broke. I had data, but no voice. (You posted in a thread I started and helped me fix my radio)
I'm not trying to argue or anything, just trying to understand.
Are you saying that I should now be able to flash an AOSP rom and have no radio issues now since I reflashed the stock recovery to fix the radio, then flashed back to TWRP?
adrenalinemotion said:
I s-off'd, unlocked my bootloader and rooted with no issues. I was stock rooted and everything functioned. As soon as I flashed an AOSP rom, the radio broke. I had data, but no voice. (You posted in a thread I started and helped me fix my radio)
I'm not trying to argue or anything, just trying to understand.
Are you saying that I should now be able to flash an AOSP rom and have no radio issues now since I reflashed the stock recovery to fix the radio, then flashed back to TWRP?
Click to expand...
Click to collapse
I really think you can go back to an AOSP rom. I have no problems and tons of other people with no problems. I noticed that the guys who s-off with sonic didn't have these issues. That is just why I think it is something with the whole current s-off process.
But if you do decide to give AOSP another try. I would flash when you have about a hour of free time with a computer just to make sure it doesn't crap out again.
Does one need to have the stock recovery to reset from Hboot?
Sent from my HTC6500LVW using Tapatalk now Free
Flyhalf205 said:
@Karunamon
Problem 1. Not really figured out yet. All you need to do is flash any Sense rom.
Problem 2. Is fixed! For a couple of days now for any ROM built after 11th of this month.
Problem 3. I get the same dBm on Sense and AOSP. Sure a lot of other people do also. But people panic when looking at the network bars.
Problem 4. I get no purple/pink tint when on Sense but after flashing AOSP I get the purple/pink tint on my FFC. So I would wait til 4.3.
Click to expand...
Click to collapse
Excellent, seems I just need to dig up a sense rom and then reflash something new and i'll be good on 1 and 2.
Any idea what could be causing 3, though? For comparison, when I was on stock, the meter was completely full for LTE in my home. Now, it's one bar. Coverage is still good though and data still works at breakneck speeds, so I don't think it's an actual signal issue.
Karunamon said:
Excellent, seems I just need to dig up a sense rom and then reflash something new and i'll be good on 1 and 2.
Any idea what could be causing 3, though? For comparison, when I was on stock, the meter was completely full for LTE in my home. Now, it's one bar. Coverage is still good though and data still works at breakneck speeds, so I don't think it's an actual signal issue.
Click to expand...
Click to collapse
check DBM isntead of looking at your bars to see if you even have an issue.
The signal issue sounds the same as AOSP on the Rezound. The signal strength would be same, but the signal icon would be different. Basically, HTC has set the icons to show more than AOSP.
I didn't factory reset after using rumrunner and the only thing I have noticed was I would not connect to 4g as much or as fast as before. It seems to be getting better though. I am running bonestock.
Sent from my phone using an app
Like it was explained to me the bars are kinda like the idiot lights on a cars dash. They really don't do much. Aosp shows your true signal and sense and so on shows a false truth just so people doesn't complain about poor signal. As long as my data works I don't care if I have zero bars.
Sent from my M7 using Tapatalk
Are there any bluetooth issue's ?
nujackk said:
Are there any bluetooth issue's ?
Click to expand...
Click to collapse
No issues using a Bluetooth headset here.
Can't say anything about Bluetooth audio streaming, haven't tried that yet.
sawedust said:
No issues using a Bluetooth headset here.
Can't say anything about Bluetooth audio streaming, haven't tried that yet.
Click to expand...
Click to collapse
IR work yet?
exzacklyright said:
IR work yet?
Click to expand...
Click to collapse
IR is working on VanirAOSP.
I'm using Smart IR Remote to control my devices; great interface and works well with the majority of the stuff that I have.
Not sure what the progress is re: IR with the other AOSP ROMs.
With smart ir remote it should work on any Rom.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
sawedust said:
No issues using a Bluetooth headset here.
Can't say anything about Bluetooth audio streaming, haven't tried that yet.
Click to expand...
Click to collapse
The streaming is my main concern, Use is inmy truck and main reason I will try to keep my unlimited data FOREVER
adrenalinemotion said:
I s-off'd, unlocked my bootloader and rooted with no issues. I was stock rooted and everything functioned. As soon as I flashed an AOSP rom, the radio broke. I had data, but no voice. (You posted in a thread I started and helped me fix my radio)
I'm not trying to argue or anything, just trying to understand.
Are you saying that I should now be able to flash an AOSP rom and have no radio issues now since I reflashed the stock recovery to fix the radio, then flashed back to TWRP?
Click to expand...
Click to collapse
Did this happen using twrp or cwm? Some folks are thinking its cwm causing this.
Sent from my HTC6500LVW using Tapatalk
---------- Post added at 08:29 AM ---------- Previous post was at 08:28 AM ----------
Flyhalf205 said:
I really think you can go back to an AOSP rom. I have no problems and tons of other people with no problems. I noticed that the guys who s-off with sonic didn't have these issues. That is just why I think it is something with the whole current s-off process.
But if you do decide to give AOSP another try. I would flash when you have about a hour of free time with a computer just to make sure it doesn't crap out again.
Click to expand...
Click to collapse
This happened to people who hardware s-off'd and flashed the gpe rom too. Don't think it has anything to do with it.
Sent from my HTC6500LVW using Tapatalk