I went from the 9/8 build to the 9/10 build, and the Recent Apps hardware key does absolutely nothing, no matter what function i assign it in system settings (very annoying not having a Menu button!). Tried flashing multiple times, re-downloading multiple times, flash boot.img, fix permissions, wipe cache/dalvik, etc. Nothing fixes it. Flashed back to the 9/8 build and everything works like a charm. Anyone else having this issue?
Sent from my EVO using xda app-developers app
Came here to investigate the same thing, except I went from 9/7 to 9/10, looks like we're having the same problem tho. Initially neither the app-switch button or long pressing home worked. Ran fix permissions from twrp and got the long press home working again. You think reverting to an earlier build would fix it?
Sent from my LTEVO
Do a clean flash mine still works on 0910 nightly
Sent from my Cm10 powered Evo Lte!!
As always......
If you dirty flash and have issues.... do a full wipe. Making bug reports on a dirty flash doesn't help anyone. If the problem persists after a clean wipe then I'd like to know about it
My apologies, i guess i just learned the hard way what the definitions of clean and dirty flashing are. Sorry to waste your time, and thank you for the learning experience! (And for not tearing me a new(b) one!!!)
Sent from my EVO using xda app-developers app
Mockingbird946 said:
My apologies, i guess i just learned the hard way what the definitions of clean and dirty flashing are. Sorry to waste your time, and thank you for the learning experience! (And for not tearing me a new(b) one!!!)
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
This is still useful for others that have dirty flashed and will experience issues.
But now you know to do a clean wipe if you run into issues after dirty flashing :highfive:
Not a problem I actually dirty flashed up. Always do then if I have a issue. I clean install to make sure it's not my end. Usually fixes things.
Sent from my Cm10 powered Evo Lte!!
Since these are nightlies you should do a clean install or factory reset after flashing
Rxpert said:
This is still useful for others that have dirty flashed and will experience issues.
But now you know to do a clean wipe if you run into issues after dirty flashing :highfive:
Click to expand...
Click to collapse
Thanks again! Your guidance is greatly appreciated. Looking forward to clean flash when i get home!
Sent from my EVO using xda app-developers app
kaos420 said:
Not a problem I actually dirty flashed up. Always do then if I have a issue. I clean install to make sure it's not my end. Usually fixes things.
Sent from my Cm10 powered Evo Lte!!
Click to expand...
Click to collapse
Alright, so I rebooted into TWRP 2.2.2.0 and did wipe cache, wipe dalvik, factory reset, and wipe system, in that order. I then flashed from my SD card CM10 nightly 9/10 and gapps jb. Cleared cache/dalvik. Booted up, ran fix permissions. Still no luck; recent apps hard key still doesn't do anything (yes, I went in to system settings and set the key functions,) but it does vibrate when touched. Did I miss a step somewhere?
Sent from my EVO using xda app-developers app
Mockingbird946 said:
Alright, so I rebooted into TWRP 2.2.2.0 and did wipe cache, wipe dalvik, factory reset, and wipe system, in that order. I then flashed from my SD card CM10 nightly 9/10 and gapps jb. Cleared cache/dalvik. Booted up, ran fix permissions. Still no luck; recent apps hard key still doesn't do anything (yes, I went in to system settings and set the key functions,) but it does vibrate when touched. Did I miss a step somewhere?
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Idk basically what I've done. Mine all works. Flash the 0911 build in irc then
Sent from my Cm10 powered Evo Lte!!
I suppose you could try a wipe script as they are written to erase all possible data that could cause unintended side effects with a new flash
Had the same problem going from 9/8 to 9/10 but I just went into the settings and changed the hard key functions. Then everything was all goodie goodie again
Sent from my EVO using xda app-developers app
Ok. Did a superwipe 3 times, clean install 9/10 build, changed system settings hard key function, still doesnt work. I'm downloading the 9/12 build so hopefully i get better results with that one.
Sent from my EVO using xda app-developers app
Are any of you guys getting an issue where the mic won't pick up your voice for voice commands but work fine during calls?
Sent from my EVO
I hope the newer build is a lot better then the 9/6 build so many glitches on the one I flashed :/
Sent from my EVO using xda app-developers app
Related
Just a quick comment, FWIW...
There was a time, when I was more of a noob than I am now, that I used to smirk at people who said they always wiped cache and data 2 or 3 times between loading different ROMs. I thought they were being a little anal - after all, a wipe's a wipe.
I've since learned differently. Recently I had a nasty FC problem that just wouldn't go away until I wiped data three times and then reflashed my ROM. Don't know why, but it works sometimes when nothing else will.
I thought it was anal too haha
I wipe 2 times before a flash.
Its weird how things work
Sent from my DROID X2 using XDA App
Robin M said:
Just a quick comment, FWIW...
There was a time, when I was more of a noob than I am now, that I used to smirk at people who said they always wiped cache and data 2 or 3 times between loading different ROMs. I thought they were being a little anal - after all, a wipe's a wipe.
I've since learned differently. Recently I had a nasty FC problem that just wouldn't go away until I wiped data three times and then reflashed my ROM. Don't know why, but it works sometimes when nothing else will.
Click to expand...
Click to collapse
Cvpcs wrote a great blog on wiping. I too have had nasty fc issues w/ our current recovery. You would think if it's not wiping correctly then 50 wipes would still produce the same bad wipe. I mean, the code doesn't change w/ each wipe we perform
Never had an issue with other recoveries on older phones. Properly written cwmr shouldn't need to wipe more than once b/c the code will only do what it's written to do. Improper coding leads to improper wiping. Just my $.02
Sent from my DROID X2 using xda premium
X0dus said:
Cvpcs wrote a great blog on wiping. I too have had nasty fc issues w/ our current recovery. You would think if it's not wiping correctly then 50 wipes would still produce the same bad wipe. I mean, the code doesn't change w/ each wipe we perform
Never had an issue with other recoveries on older phones. Properly written cwmr shouldn't need to wipe more than once b/c the code will only do what it's written to do. Improper coding leads to improper wiping. Just my $.02
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Well its a hacked version of CWM so its not as developed and refined.
Sent from my DROID X2 using XDA App
IDMA.DROID.X2 said:
Well its a hacked version of CWM so its not as developed and refined.
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
Right, but if one wipe fails to wipe correctly do you suppose the second will clean up what it missed? I don't think code has become self aware of mistakes.
Sent from my DROID X2 using xda premium
All I know is I always wipe data 3 times andncache/dalvik twice each.
And have never had 99% of the.problems I see others having after flashes such as FCs and all...unless it was a known bug everyone was experience.
ashclepdia said:
All I know is I always wipe data 3 times andncache/dalvik twice each.
And have never had 99% of the.problems I see others having after flashes such as FCs and all...unless it was a known bug everyone was experience.
Click to expand...
Click to collapse
Too many don't wipe anything and clutter threads. :/
Sent from my DROID X2 using xda premium
True story xodus
X0dus said:
Right, but if one wipe fails to wipe correctly do you suppose the second will clean up what it missed? I don't think code has become self aware of mistakes.
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Maybe not, but there is less chance of irritation (pun intended).
Sent from my DROID X2 using xda premium
Here is more irritation : I ran 234update.zip from stock 233 recovery FOUR TIMES w/o leaving recovery. 1st: got a status (0) and stopped. 2nd correct status err and went faster. 3rd went fastest. 4th no more speedup.
garywojdan81 said:
Maybe not, but there is less chance of irritation (pun intended).
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Glad I'm not the only one laughing at this entire thread of puns of whiping, being anal about doing it over and over and wiping again!
You guys are right though, everytime a wipe is done, seems the later ones are much faster.
Apparently the more you wipe, the cleaner you get, it get's easier it is to wipe again.
grnsl2 said:
Apparently the more you wipe, the cleaner you get, and the easier it is to wipe again.
Click to expand...
Click to collapse
Yeah, that was my point. It's definetly a progressive action. Very strange. I wudda thought like XOdus, that the code would do exactly the same thing each time.
The puns are fun.
They get faster b/c there's nothing else to wipe from the directory. My final post here.
Sent from my DROID X2 using xda premium
X0dus said:
The puns are fun.
They get faster b/c there's nothing else to wipe from the directory. My final post here.
Click to expand...
Click to collapse
Of course. But all punning aside, the point he was making is that they get progressively faster, indicating that not all is cleared with earlier wipes. There's no denying that multiple wipes can clear up sticky problems. Even if the reason is "bad code", that's still strange.
CVPCS Blog entry:
http://cvpcs.org/blog/2011-06-05/time_to_wipe_data/cache
I only wipe once with our recovery and only once have I had an issue. I simply reflashed the ROM and it went away.
I bet he wiped the second time though. So he wiped twice
Sent from my DROID X2 using XDA App
X0dus said:
CVPCS Blog entry:
http://cvpcs.org/blog/2011-06-05/time_to_wipe_data/cache
I only wipe once with our recovery and only once have I had an issue. I simply reflashed the ROM and it went away.
Click to expand...
Click to collapse
I hear ya. The blog article makes perfect sense. Hard to argue with the logic expressed there. And yet... experience tells me otherwise. As I said in the OP, I resenctly had a persistent FC problem with a system file - may have been ProgramMenuSystem.apk, can't remember for sure. Re-loaded my nandroid (that was fine before). While anyone would fully expect that to reslove the problem, the problem continued. Wiped again and re-flashed same version of my ROM. Problem still there. Wiped three times and re-flashed ROM again. Problem gone and never re-appeared.
I cannot explain why wiping data three times eliminated the problem that persisted even after wiping and re-flashing. Yet it did. Go figure.
Robin M said:
I cannot explain why wiping data three times eliminated the problem that persisted even after wiping and re-flashing. Yet it did. Go figure.
Click to expand...
Click to collapse
Technology can be the best and it's the worst crap ever at times, isn't it? Haha Ya think you have something figured out and logical then blam!
Sent from my DROID X2 using XDA App
dingleberries.... they'll get ya every time!
garywojdan81 said:
Maybe not, but there is less chance of irritation (pun intended).
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
I think the direction of said wipe also needs to be mentioned. Front to back or back to front?
So Is this normal whenever new Rom installed or cache/dalvik is wiped? Takes quite awhile to do 313 everytime.
Sent from my EVO using xda premium
Yes. Don't wipe dalvik without a good reason for it.
Its a new thing in ICS that helps your phone adjust to changes
Sent from my GT-I9300 using XDA
ipclark1 said:
So Is this normal whenever new Rom installed or cache/dalvik is wiped? Takes quite awhile to do 313 everytime.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
yerp..seems that it'll happen everytime cache/dalvik is wiped. Since I'm assuming you're not new to this wiping process, you'll probly remember that boot always take a little longer after you wipe the dalvik..it's still the same, just now it provides a visual indication of its progress.
I like it since now you know your phone has actually booted as opposed to the OG Evo where you're left wondering whether it's stuck or not
KERKEDAGAIN said:
yerp..seems that it'll happen everytime cache/dalvik is wiped. Since I'm assuming you're not new to this wiping process, you'll probly remember that boot always take a little longer after you wipe the dalvik..it's still the same, just now it provides a visual indication of its progress.
I like it since now you know your phone has actually booted as opposed to the OG Evo where you're left wondering whether it's stuck or not
Click to expand...
Click to collapse
Outstanding, that makes sense. thanks for the helpful responses.
Sent from my EVO using xda premium
I see. I learn something from you guys! Thank you!
Also happens whenever you change something in the /system folder.
Seems that recently the LEDs for the flash and what are also used for the flashlight are no longer operating on my husbands phone. I've tried wiping and reflashing JellyBlur v1.3 and trying various applications - but it seems that this doesn't help and that those LEDs just don't want to come on. Is there something that I can do to fix this or are they out for good?
I'm also running JellyBlur v1.3 on my phone and my flash/flashlight are working fine. While I'm waiting I'm going to try flashing another ROM to see if that solves the problem, but any tips or helpful posts are greatly appreciated. Thank You. :good:
Update It seems that switching ROMs didn't help it either. The flash still doesn't want to work nor does any flashlight application including stock. Not sure what happened, but hopefully someone can suggest a fix. (Could it be kernel or something similar related?)
- Tried reflashing JellyBlur v1.3 and Skyraider Zeus v1.3
Thundeshed is good and any Rom based off of it is too.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
Thundeshed is good and any Rom based off of it is too.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Do you think flashing that might fix the flash issue? I've never encountered this problem before on our phones so it's new to me.
I would definitely make a backup of what you have now, do a good/clean wipe and install a nandroid backup from a different ROM in which the flash was working to see if the flash will work for you again.
If not, the flash may have just given up on you. =\
Note: Clear data 3x, cache once, and dalvik once. (I always recommend clearing data at least 3x because data doesn't always clear within the first or even second time around)
Sent from my ADR6400L using xda premium
RBarnett09 said:
I would definitely make a backup of what you have now, do a good/clean wipe and install a nandroid backup from a different ROM in which the flash was working to see if the flash will work for you again.
If not, the flash may have just given up on you. =\
Note: Clear data 3x, cache once, and dalvik once. (I always recommend clearing data at least 3x because data doesn't always clear within the first or even second time around)
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
Yep, tried doing super wipe then cache/dalvik... doesn't work on any of the ROMs I have tried. I guess the flash just went out on his phone. *sad pandas*
I guess he will just have to do for now until I can buy him a new phone. :crying:
WalkerGFX said:
Yep, tried doing super wipe then cache/dalvik... doesn't work on any of the ROMs I have tried. I guess the flash just went out on his phone. *sad pandas*
I guess he will just have to do for now until I can buy him a new phone. :crying:
Click to expand...
Click to collapse
Yeah, that sucks!
I know you can buy the replacement parts for the flash, but you can't find directions on how to repair it anywhere.
Sent from my ADR6400L using xda premium
I think it would be a difficult repair and some soldering would definitely be necessary.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
I think it would be a difficult repair and some soldering would definitely be necessary.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Yeah, I would imagine the same thing.
Just a big pain.
Sent from my ADR6400L using xda premium
I would suggest a warranty replacement if you have the option.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
I would suggest a warranty replacement if you have the option.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Good news. I was able to put ICS (Liquid Desensed36) and applied the new combo radio someone developed.
Using the Wi-Fi w/ root from play store using generic ics/jb (wlan0), channel 2, password protected, with router fix was able to fix his Wi-Fi tether.
Also the ICS Liquid Desenesed36 fixed his Flash and flashlight! (Don't know how; I don't question it) :good::good::good::good::good:
good day all,
i'm trying to flash to this rom, i've tried both clockworkmod recovery and 4ext. the rom flashes, reboots and stays at the cool blue "Startingi ICS" for 10's of minutes, resulting in a pulled battery/recovery/restore to backup.
i'm a complete n00b at this, so its likely i'm making mistakes but cannot figure out the path forward. i've not tried any other roms yet, may have a look at nusense and see it if boots.
any help appreciated.
--- michael
You need to wipe system,and both caches. In 4ext use format all except SD
Sent from my ADR6400L using Tapatalk 2
thanks! that indeed resolve my issue. whew, nice to finally be free of sense.
-- michael
disconnecktie said:
You need to wipe system,and both caches. In 4ext use format all except SD
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
You have to wipe between flashes most of the time. There some times were wiping only caches will work but it really is better to just wipe everything and eliminate any issues that could come from not wiping everything.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
but it really is better to just wipe everything and eliminate any issues that could come from not wiping everything.
Click to expand...
Click to collapse
This is also the advice I'm giving my 2yo as we've begun potty training
Sent from the Great Beyond
John.E.Boi said:
This is also the advice I'm giving my 2yo as we've begun potty training
Sent from the Great Beyond
Click to expand...
Click to collapse
This is funny I don't care who you are rofl.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
This is funny I don't care who you are rofl.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
i totally agree... LOL
I have wiped & wiped and also tried 3 different releases of this rom but I always get caught in the bootloop. I know that some folks are having the same issue but I was hoping that my TB wouldn't be one of them.
My first foray into this ROM is 12/6 build and I haven't seen a reason to try a newer build. Works pretty good, very few complaints.
I am rooted and all the stuff that comes with that but I wiped all contents of system data cache dalvik and flashed just cm11 and no matter what I do, my sms fails to send until I toggle my radio or reboot. I even wiped. I didn't even flash a kernel. I tryed to look for the thread to see what I missed but I couldnt find the thread. I have been superusering since the ally but I haven't in a little while. It's weird cause it has no problems on the source based roms like Venom.
Sent from my HTC6435LVW using xda app-developers app
biggiesmalls657 said:
I am rooted and all the stuff that comes with that but I wiped all contents of system data cache dalvik and flashed just cm11 and no matter what I do, my sms fails to send until I toggle my radio or reboot. I even wiped. I didn't even flash a kernel. I tryed to look for the thread to see what I missed but I couldnt find the thread. I have been superusering since the ally but I haven't in a little while. It's weird cause it has no problems on the source based roms like Venom.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Same thing happens to me but I am on PAC-man. I didn't change the radio or anything. This phone has been nothing but frustration for me
For me if I disable 4G LTE through the *#*#4636#*#* menu I can send texts but then I go down to 1g
biggiesmalls657 said:
. It's weird cause it has no problems on the source based roms like Venom.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
The kit kat roms are ported. There are several issues with them that cannot be "fixed" until the source code is released.. Viper 2.52 is an excellent rom that has no bugs to speak of.
Agreed...
Apparently Verizon changed some SMSC numbers to screw with rooted people. I guess we will have to wait for the updates to resolve this.