Related
I've been having lockscreen reboot issues with the last few Fission roms, and a couple of Matt's. Has anyone else had this problem and resolved it?
I followed the installation instructions and even formatted my SD card. I'm going to try to SBF before I install the next Fission, is there anything else I can do to completely clean out my phone? Such as wiping some system files in recovery or something.
The only data I have left over from other ROMs is backups I made of a few games like Angry Birds.
Any suggestions are appreciated, I've been trying to fix this issue for awhile!
Are you doing a hard reset after flashing roms? Resetting the phone in applications>privacy, at the bottom of privacy?
mikeyinid said:
Are you doing a hard reset after flashing roms? Resetting the phone in applications>privacy, at the bottom of privacy?
Click to expand...
Click to collapse
Yup, after installing the ROM and rebooting I do a hard reset through the privacy menu. Would it make a difference if I sign into my google account on first reboot before doing the hard reset?
kdog349 said:
Yup, after installing the ROM and rebooting I do a hard reset through the privacy menu. Would it make a difference if I sign into my google account on first reboot before doing the hard reset?
Click to expand...
Click to collapse
I never sign into google until after the hard reset. But I dont know if that matters. Next time you flash a rom, try wiping data and cache in recovery, after flashing, but before you reboot. And, are you overclocking or undervolting?
I'll try wiping data and cache before my first reboot. I know I used to do this but not sure if I've done it recently.
I haven't messed with overclocking or underclocking. Do you know if any widgets are known to cause problems? I run Launcher Pro, but I went a day or two with the stock launcher and still had some reboot issue.
kdog349 said:
I'll try wiping data and cache before my first reboot. I know I used to do this but not sure if I've done it recently.
I haven't messed with overclocking or underclocking. Do you know if any widgets are known to cause problems? I run Launcher Pro, but I went a day or two with the stock launcher and still had some reboot issue.
Click to expand...
Click to collapse
Launcherpro wouldnt cause it. I would sbf if i were you, and just keep doing what your doing. After so many flashes there is bound to be some residual bs left behind.
*Fission 2.2.1 will be hitting the forum soon so an sbf is in your best interest Im running it now and its VERY good...
mikeyinid said:
Launcherpro wouldnt cause it. I would sbf if i were you, and just keep doing what your doing. After so many flashes there is bound to be some residual bs left behind.
*Fission 2.2.1 will be hitting the forum soon so an sbf is in your best interest Im running it now and its VERY good...
Click to expand...
Click to collapse
I'll give SBF a try. I've been loving everything about the fission ROMs, can't wait to get 2.2.1
Thanks so much for the help!
mikeyinid said:
Launcherpro wouldnt cause it. I would sbf if i were you, and just keep doing what your doing. After so many flashes there is bound to be some residual bs left behind.
*Fission 2.2.1 will be hitting the forum soon so an sbf is in your best interest Im running it now and its VERY good...
Click to expand...
Click to collapse
I'll give SBF a try. I've been loving everything about the fission ROMs, can't wait to get 2.2.1
Thanks so much for the help!
Lock Screen Reboots are something that seem to be present in all these Moto Droid phones. I always always always get them on both D1 and Dx and D2, with any ROM, theme, etc. Just seems to be a common problem Motorola has, along with their insane fascination with their Motoblur UI which is also a complete mystery.
mjones1052 said:
Lock Screen Reboots are something that seem to be present in all these Moto Droid phones. I always always always get them on both D1 and Dx and D2, with any ROM, theme, etc. Just seems to be a common problem Motorola has, along with their insane fascination with their Motoblur UI which is also a complete mystery.
Click to expand...
Click to collapse
Personally I had a Droid 1 for 6 months and don't remember having any lockscreen reboots, at least not at the frequency of 2-3 a day that I'm having now. Could run the phone for a week without rebooting.
There were a couple of D2 roms that didn't have the reboot issue for me, but most do so maybe it is an issue with the phone like you say. I Don't understand their persistance with motoblur either At least take out eFuse if you're going to throw on motoblur
I've been trying lockbot free to solve my reboot issues. You can basically set it to be exactly the same the normal lockscreen, and so far it seems to be working for me.
I had this problem. Random, intermitten soft reboots during slide to unlock. Ran multiple roms, always had the problem. But I was always removing the same things after sbf. I had found one Dev to seem to find this to follow the music.apk file. So this time I left it on. On my last sbf, I left that in there. Havent had a problem since. Before that I had tried what I thought to be everything, multiple sbfs, multiple roms, completely formatted sd card, and re-sbf'd again. But I always deleted music.apk. Because it always seems to start running, using memory that I thought was unnecessary. Since I dont play music from my phone, other then streaming music. Hope that helps someone. Saved a ton of frustration for me!
But I always deleted music.apk. Because it always seems to start running, using memory that I thought was unnecessary. Since I dont play music from my phone, other then streaming music. Hope that helps someone. Saved a ton of frustration for me!
Click to expand...
Click to collapse
Which music.apk is this? Is it the D2's original application or the google music app? Because I've never taken the music app that's been on the phone or came with any ROM and I've had a few not a big number but a few.
Sent from my DROID2 using XDA App
Not sure what the google music one is, but the file is named music.apk
Please clarify this lol. Mine was working great until I installed that damn black theme for fission rom.
I've had a droid1 and I have never had reboot issues with roms before. I think it may just be a d2/x problem
Sent from my DROID2 using XDA App
Yeah the same thing happens to me. I'm pretty sure the dev's for Fission know about it, so hopefully 2.2.1 from them fixes it.
Sent from my DROID2 using XDA App
I had this same problem until yesterday. I installed the Music.zip that came with fission. Now I haven't had a single problem. (I also installed the 10 percent framework and the Camera.zip) I can't remember who posted it but once I installed the Music.zip everything works great.
Im just curious, are you guys only experiencing these reboots with the non-blur roms, or have you experienced them with other roms also? I have only had one reboot, and that was running fission 2.2.1.
tonorice said:
I had this same problem until yesterday. I installed the Music.zip that came with fission. Now I haven't had a single problem. (I also installed the 10 percent framework and the Camera.zip) I can't remember who posted it but once I installed the Music.zip everything works great.
Click to expand...
Click to collapse
Was it the "Android_Music.zip" or "D2_Music.zip"?
If I use the current version of VISIONary (r14) and ONLY temp-root my MT4G, will ANY residual effects be left once I reboot?
I remember when using VISIONary on my MT3G, it seemed to cause permanent changes even though I only used "temp" root.. eventually my phone seemed to have conflicts with apps and it never really "unrooted"
It's my understanding that VISIONary should be completely safe as it does not write to the system partition..?
Please move this to q&a......
From my don't talk about changelog CM7 Glacier
Anyone?? Need some advice here.
$pitacular1 said:
Anyone?? Need some advice here.
Click to expand...
Click to collapse
VISIONary.apk was designed to only be used on the HTC Vision and the HTC Glacier.
Nandroot was designed to be use on the HTC Magic and HTC Dream. and later came the desktop client SuperOneClick.
If i didn't know any better the reason your Magic went FUBAR is because you used the wrong method and installed something that didn't belong.
But to answer your question my wife's phone is temp rooted with VISIONary.apk and she has had zero usability problems after a reboot.
neidlinger said:
VISIONary.apk was designed to only be used on the HTC Vision and the HTC Glacier.
Nandroot was designed to be use on the HTC Magic and HTC Dream. and later came the desktop client SuperOneClick.
If i didn't know any better the reason your Magic went FUBAR is because you used the wrong method and installed something that didn't belong.
But to answer your question my wife's phone is temp rooted with VISIONary.apk and she has had zero usability problems after a reboot.
Click to expand...
Click to collapse
In the modaco forum I read earlier today that someone was having constant reboots from using VISIONary for temp root.
You said your wife's phone "had zero usability problems after a reboot". What about after temp-rooting, but before rebooting? Any issues there?
$pitacular1 said:
In the modaco forum I read earlier today that someone was having constant reboots from using VISIONary for temp root.
You said your wife's phone "had zero usability problems after a reboot". What about after temp-rooting, but before rebooting? Any issues there?
Click to expand...
Click to collapse
Nope she uses it all day everyday.
Thank you, much appreciated.
Temp-Root here I come!
Btw, is she using the latest version (r14) ?
Noticed no problems
I've seen no problems after a reboot with Visionary r14. On another point, I had it originally set to automatically temproot after every reboot, but once I discovered that the programs that Titanium Pro freezes stay frozen after a reboot even if you're not temprooted, I no longer temproot. Have to use it, though, if I want to add/subtract frozen programs.
ecdy said:
I've seen no problems after a reboot with Visionary r14. On another point, I had it originally set to automatically temproot after every reboot, but once I discovered that the programs that Titanium Pro freezes stay frozen after a reboot even if you're not temprooted, I no longer temproot. Have to use it, though, if I want to add/subtract frozen programs.
Click to expand...
Click to collapse
I wonder if that's normal. It was residual root-like effects like that I was wondering about.
neidlinger said:
VISIONary.apk was designed to only be used on the HTC Vision and the HTC Glacier.
Nandroot was designed to be use on the HTC Magic and HTC Dream. and later came the desktop client SuperOneClick.
If i didn't know any better the reason your Magic went FUBAR is because you used the wrong method and installed something that didn't belong.
But to answer your question my wife's phone is temp rooted with VISIONary.apk and she has had zero usability problems after a reboot.
Click to expand...
Click to collapse
On another note, I had previously experimented on my MT3G with Universal Androot which worked perfectly.. it was only later after the 2.2 update that I needed a root alternative as they had patched the exploits Universal Androot used to get root.. VISIONary was a perfect solution. The only problem is it resulted a permanent "partial" root instead of a temporary root or a full perm root. It was still an excellent tool to use for the job though.. nothing went "FUBAR" lol I was still able to SAPPIMG and then manually update to the official Froyo.
I was just curious if I was going to get the same perm root issue with the MT4G, as I have not yet familiarized myself with the process of restoring the 4G to stock although I am aware of PD15IMG.. just haven't read through the specifics. I swear I'm not a total noob I promise.. I've written tutorials on root for the MT3G
Ok, so last night I used VISIONary for temp root only..
Immediately after temp rooting, my phone started acting weird.. syncing extra long, everything was slow (even after the syncing).. it just seemed to be severly affecting the performance of my device.
I don't know if perhaps I have an active app it was having issues working with or what, all I know is without temp root my phone flies 24-7.
Once I rebooted, everything went back to normal. Don't think I'll be using VISIONary anymore
$pitacular1 said:
Ok, so last night I used VISIONary for temp root only..
Immediately after temp rooting, my phone started acting weird.. syncing extra long, everything was slow (even after the syncing).. it just seemed to be severly affecting the performance of my device.
I don't know if perhaps I have an active app it was having issues working with or what, all I know is without temp root my phone flies 24-7.
Once I rebooted, everything went back to normal. Don't think I'll be using VISIONary anymore
Click to expand...
Click to collapse
i guess you are one in a million who have experienced problems with VISIONary.apk.
I guess if you are that bent on rooting you can do it the old fashioned way.
neidlinger said:
i guess you are one in a million who have experienced problems with VISIONary.apk.
I guess if you are that bent on rooting you can do it the old fashioned way.
Click to expand...
Click to collapse
Well last night when I first tried it, I had not enabled USB debugging..
So this morning, I tried it again, but made sure it was enabled the FIRST time lol..
and it's working flawlessly. I guess my initial idiocy caused something.. but it's fine now!
$pitacular1 said:
Well last night when I first tried it, I had not enabled USB debugging..
So this morning, I tried it again, but made sure it was enabled the FIRST time lol..
and it's working flawlessly. I guess my initial idiocy caused something.. but it's fine now!
Click to expand...
Click to collapse
That's cool. Glad to hear it is working.
Tomorrow is my 46th birthday, and I have tried to stay on top of technological advancements as best possible given my busy schedule. What I have noticed is that my ability to digest the latest techno trends and techniques does have a limit, especially when it interferes with the approaching martini hour at afternoon's end!
I don't know if this is a question or a mid-life existential moment. I bought the Samsung Epic 4G last fall because it was supposed to be cutting edge in terms of hardware for Android, and I as many of you have expressed, I made the decision to buy the Epic because of the promised firmware update that was imminent.
Fast forward half a year, and I now have the 2.2.1 EB13 firmware, which is rooted. I received the SMS yesterday (Wednesday) afternoon from Sprint about Sprint ID coming, but no update. Since I am rooted on EB13 I have no idea whether or not I will ever get the OTA and the last time I tried ODIN I had to take a tranquilizer, so I have no desire to go back to 2.1 to get the OTA.
Will the EC05 OTA be appearing given rooting on EB13? EB13 is giving me problems. I loved moving many (most) apps over to SD (I have a 32 gig card). But WiFi is not good, and I lose the ability to play movies, audio files, visual voicemail, or even hear my phone ringer (all seem connected in terms of the error -- I get an "unable to play message" or "unable to open file" error). I have to turn the phone off completely, then back on, wait for the media scan, etc. for it to go back to normal, then the errors will come back. I was hoping that EC05 would fix this. Maybe not. In perusing and searching I see nobody else has reported these problems which did not exist on DI18 (although I do see reports of WiFi connectivity problems that appear similar).
Does anyone have a bag phone from 1988 they want to trade for my Epic? As I recall, it worked without any hassles or firmware updates. Although it didn't have Angry Birds...
UPDATE: Life is grand at 46 (almost!). I posted later the following URL:
hxxp://forum.androidcentral.com/epic-4g-rooting-roms-hacks/71389-odin-ec05-froyo-ec05-prerooted-cwm-v2-5-1-0-rfs-odexed.html#post761525
When I got home I did as instructed using ODIN, and now I have EC05, with root, no data erasure, all is well! I still see so much consternation going on in the other threads. If you go to this URL and follow the directions, it works without any issues. I noticed immediately my WiFi issues are issues of the past. You can either wait for Sprint/Google to OTA you, under certain limited conditions, or do this, and be whole. Your choice. JJP
There should be an ota coming for those on eb13. As long as you didn't remove any bloatware you should be able to install the update. Besides there might Even be an update.zip on here that you can use before you get the ota. And Odin isn't that bad. I know you worry that it might brick your phone but I've used it about 10 times so far and no problems here. As far as technology goes its developing extremely fast these days. Its hard to keep up with it. Good luck and if you have anymore questions or decide to Odin and need something don't hesitate to ask or even pm me. I answer really quick cause I have it send be an email when.I get a pm.
Sent From My Evo Killer!
Thank you, what a nice response. Hopefully an update.zip will appear for EB13. Stranger things have happened.
drplaud said:
Does anyone have a bag phone from 1988 they want to trade for my Epic? As I recall, it worked without any hassles or firmware updates. Although it didn't have Angry Birds...
Click to expand...
Click to collapse
Unfortunately, all the AMPS and Digital TDMA networks have long since been shut down, so it would do you no good
But I do have a bag phone haha
Sent from my SPH-D700 using XDA Premium App
I wish I was 18 again, but for other reasons.
Yeah it is hard to keep up with tech these days,it changes by the hour now. And Ill have to say that Android is fragmented,this makes it harder; Look at what 2 updates to 2.2.1 and a 2.2.1 leak has done to this Epic forum,it has become a mess,I just hope now that we have CM7 and probably the last update for atleast 6 months,we should start to see some serious progress.
Sent from my SPH-D700 using XDA Premium App
Odin is only a pain the first time around. Now that you have the proper drivers installed its just a matter of selecting the file and clicking the start button. The only thing you have to watch out for is finding the correct usb port that the driver was installed on. As long as you're plugged into the correct one you're golden.
I do not think I will receive the OTA as I used one click to root after installing EB13. Perhaps this is the time to go Bonsai as I understand it now has EC 05 built in. I apologize, but is there a primer on how specifically to go to Bonsai? I have never flashed before (as I thought I might be arrested). Thanks.
Sent from my Samsung Epic™ 4G
You mentioned you're rooted. Do you know if you have CWM3 installed?
Its all a little trial and error but once everything is properly installed flashing roms is a cinch. I'm a big fan of the ACS roms. Bonsai worked well on my phone but there were a handful of idiosyncracies present that I could not put up with. Of course YMMV but don't hesitate to try different roms until you find one that your phone works well with.
stir fry a lot said:
You mentioned you're rooted. Do you know if you have CWM3 installed?
Click to expand...
Click to collapse
I believe so. I used one click root (update.bat).
Sent from my Samsung Epic™ 4G
drplaud said:
I believe so. I used one click root (update.bat).
Sent from my Samsung Epic™ 4G
Click to expand...
Click to collapse
Cool. If you want to give EC05 a shot, go to this thread and download the modem.
http://forum.xda-developers.com/show....php?t=1003447
Insert the modem into the Phone section of odin and hit start
Put aside some time before proceeding. If you have the correct CWM installed it won't take more than ten minutes but play it safe.
Download a rom of your choice, plug your phone into your computer and place it in the root of your SD card. You can download multiple roms if you want to see which works best for you. You will lose all your data the first time installing any new rom as it is not really recommended that you transfer settings of apps between different roms. Once you find a rom your're happy with you can simply update it it with the newest version without having to wipe your data however. Its really not as bad as it sounds and the ACS rom comes with an excellent app recovery program called MyBackup Pro Root that you can backup your apps and data with. You can use it to transfer apps between different roms and even some data but data from different roms can sometimes give you problems and is not really recommended. I have transferred data with some apps without any problems however. Its really just data that is tied to the system itself that will probably give you problems.
Unplug your phone from your computer and long press the Power Button, select Reboot, and then quickly hold down the Power, Volume Down and Camera Buttons.
Now press and hold down the Power, Camera, and volume down buttons. It should boot to the samsung logo and then to a black screen with orange text on it.
Use the volume keys to navigate and the power button to make selections. Choose Wipe Data/Factory Reset and wipe it 3x, then do the same for the Cache Partition and Dalvik Cache which can be found in the advanced options.
Select Go Back and navigate to Install Zip from SD card. Choose the rom you downloaded to it and you're good to go.
If after you do the three finger boot and you're not brought to a black screen with orange text you will need to install the correct CWM. If its black with green you have an old version and if you get a different screen than that this means that you do not have CWM at all. If this is so, just navigate to reboot and press the Home key to select it.
Something to think about
Thank you for the very helpful responses. I will ponder what the best option is, but it may indeed be time to explore custom ROMS, and your responses have given me the courage to do so. Many thanks! Joe
If he doesn't have cwm3 then he's gonna have to run the one click root with cwm3 for eb13 to be able.to flash bonsai. If I were to guess he has cwm 2.5.1.0 installed. On another note HAPPY BIRTHDAY!!!!
Sent From My Evo Killer!
I would Odin to EC05 first and see if it fixes anything for you. If not, reboot your phone into CWM and if you have the correct (orange and black) version, just reboot load the ACS rom onto to your phone and give it a try. If you're not happy with it or even if you are make a backup with Mybackup Root and explore other roms until you find one that works for you.
If you make a backup I would advise making separate backups of your apks, data for your apks, and photos as it makes it much faster to get back to where you were originally. Another tip for my backup is after making one go to View and double check that it actually made one as sometimes it will not.
I would have thrown this phone away by now if it weren't for the ACS rom btw. Its much smoother, has better battery life, doesn't skip keys even without the patch that they will be implementing soon and doesn't have all the god awful bloatware.
musclehead84 said:
If he doesn't have cwm3 then he's gonna have to run the one click root with cwm3 for eb13 to be able.to flash bonsai. If I were to guess he has cwm 2.5.1.0 installed. On another note HAPPY BIRTHDAY!!!!
Sent From My Evo Killer!
Click to expand...
Click to collapse
Where do I obtain one click root with cwm3? Thanks.
musclehead84 said:
There should be an ota coming for those on eb13. As long as you didn't remove any bloatware you should be able to install the update. Besides there might Even be an update.zip on here that you can use before you get the ota. And Odin isn't that bad. I know you worry that it might brick your phone but I've used it about 10 times so far and no problems here. As far as technology goes its developing extremely fast these days. Its hard to keep up with it. Good luck and if you have anymore questions or decide to Odin and need something don't hesitate to ask or even pm me. I answer really quick cause I have it send be an email when.I get a pm.
Sent From My Evo Killer!
Click to expand...
Click to collapse
stir fry a lot said:
Odin is only a pain the first time around. Now that you have the proper drivers installed its just a matter of selecting the file and clicking the start button. The only thing you have to watch out for is finding the correct usb port that the driver was installed on. As long as you're plugged into the correct one you're golden.
Click to expand...
Click to collapse
I agree with all of these except that odin never gave me trouble even the first time i used it..
Odin is cake just read the simple directions and everything should be fine, people dont use there heads when they get that android dude and the computer on there epic, the most ive been through is acore of force closes but its so easy to fix,
people just dont read the instructions all the way through,
Yesterday i was scared to update the prl manually but i read step by step instructions had to play around and find what i needed to do which wasnt on the instructions, and it was cake, almost just as easy as clicking the system updates/update prl button in the settings
but 98% of the time the instructions are flawless and work as long as you read carefully and do step by step.
drplaud said:
Where do I obtain one click root with cwm3? Thanks.
Click to expand...
Click to collapse
Development section stickied
Called One Click Clockwork 3.0.0.6
Oh yes happy birthday as well, have a great one!!
IMO, if you are on EB13, and want to update to EC05, the EASIEST way to do it, if you can wait a bit, is to use the stock SWUpdate for EB13, which will convert your phone back to a clean fresh stock install of EB13, then once/when it is released, install the EB13 to EC05 update via the over the air process, then reroot and move forward.
that all depends on samsung/sprint releasing a EB13 to EC05 OTA update, and your ability to wait for it though
Does anybody have a working PDS for a AT&T unlocked Atrix for Gingerbread they can upload please ?
Having irritating touch screen issues.
I think pds is unique for each device so other pds won't work on your phone. Correct me if I'm wrong.
Sent from my MB860 using XDA Premium App
Andy_Thatcher said:
Does anybody have a working PDS for a AT&T unlocked Atrix for Gingerbread they can upload please ?
Having irritating touch screen issues.
Click to expand...
Click to collapse
pds are for their individual phone but there is a generic one on the forums for touchscreen fix. you are going to have to search for it.
did you do nandroid restore? which recovery? tenfer?
Really unsure to be honest.
Kinda hoping that isn't the case but if it is it is.
Have seem a couple of PDS's here but apart from one once they haven't made a difference so am trying for a definite match to find out.
My screen behaves normally until the phone starts to get warm then...well if I didn't know better I would think it was hacked with random key presses left and right.
Take out the battery for 10 minutes and get another 15 minutes or so and off it goes again.
Edit -
Managed to get some form of stability with the Aura ROM with Faux's Kernel and SetCpu under clocked....have managed to lose Wi-Fi in the mix somehow.
Could be time just to bite the bullet and buy a new one as I am due an upgrade. NOOOO enough of that defeatist talk !
Regrettably I do not have a back up of the original PDS, managed to miss that as being a requirement pre-boot unlock.
I have 2 PDS's from here I have found on here but neither seem to be a permanent fix. One is khoulk's (sp?) but I think that is from a non standard phone and another one that worked....briefly. I also have 2 from my phone but alas they were after the issues started so have doubts about them.
Just changed the CWM from tenfer's to the new one.
At present just playing around trying to get wifi back on the phone, then I will go back to the pds hunt.
Oh just for kicks it seems that I can't download from the market either at the moment. It starts but then after a few seconds stop.
I managed to get the phone to behave normally by going back to 1.2.6.
Then used OTA's to get to 1.8.3.
All stable at that point then SBF'd 4.5.1 with pudding and pre root and then....
Everything went to pot again.
Currently heading back to Froyo and will OTA again up to 1.8.3 and stay there for a while and consider my next move. Trouble is that I really need a working stable phone. so will do the smart thing next time and get a nandroid back up of the 1.8.3 and a copy of the PDS.
Try using the method described in this thread:
http://forum.xda-developers.com/showthread.php?t=1131649
It will fix both touchscreen issues, as well as the problem described in the thread. It worked for me...
Thankyou.
I had already tried that and first time it worked a treat alas not attempt 2,3,4,5,6....
Incubus has posted a rooted version of the OTA in the Devolpment forums! That is all....
Sent from my ADR6300 using XDA App
but no 2.15.10.07.07 radio yet... i want it to get tested and found good...
mirrin said:
but no 2.15.10.07.07 radio yet... i want it to get tested and found good...
Click to expand...
Click to collapse
The radios don't always mean better signal or faster 3G. They vary by location and phone... the leaked radio sucked for me and the 11.19 one seems best so far.
Sent from my ADR6300 using XDA App
And the leaked radio worked best for me, its gunna vary for everyone
Sent from my ADR6300 using XDA App
well i found 5.06 worked pretty well for me but i have been on most of them i only left it because people were saying it killed the wifi on their phones... as long as large numbers of reports of the same thing from 7.7 dont occur ill probably stay on that one...
Can someone who has flashed this try out the speech to text and see if it works properly?
Navigation or anything. Texting or anything. It some of the GB roms with the EVO framework and issues with speech to text.
Well this isn't the EVO GB Release. It's the actual Incredible release. But yes the speech to text does in fact work.
kjsmommy10 said:
Well this isn't the EVO GB Release. It's the actual Incredible release. But yes the speech to text does in fact work.
Click to expand...
Click to collapse
I know. I'm currently on Joel's shooter rewind 3d and working voice search would be the only thing to tempt me off of it.
Sweet
First post on XDA here, I registered primarily to give props to Joel and Incubus.
I grabbed the rooted OTA Incubus posted and flashed it with Rom Manager. Took a lot of patience, but it went pretty smooth. Thanks to you both (and everyone else who had a hand in this).
My DInc is just about to go out of warranty, so I'm going to be trying some other ROMs pretty soon. I'm pretty much locked into the root/S-Off status now, and I'm happy with it that way. I think I'll be hanging on to this phone for some time.
So far I like this update, but I've had a few random reboots. One or two while I was re-installing some of my apps or moving them to the SD card, and at least one while it was just sitting there on the charger.
For the moment, I'm going on the assumption that this is just some early stuff working itself out. When flashing the ROM, I cleared the Dalvik cache, but didn't do a data wipe. Anyone have any idea if this is a problem?
Again, thanks a million guys!
( Oh, LOVE the noob video! )
keyslapper said:
First post on XDA here, I registered primarily to give props to Joel and Incubus.
I grabbed the rooted OTA Incubus posted and flashed it with Rom Manager. Took a lot of patience, but it went pretty smooth. Thanks to you both (and everyone else who had a hand in this).
My DInc is just about to go out of warranty, so I'm going to be trying some other ROMs pretty soon. I'm pretty much locked into the root/S-Off status now, and I'm happy with it that way. I think I'll be hanging on to this phone for some time.
So far I like this update, but I've had a few random reboots. One or two while I was re-installing some of my apps or moving them to the SD card, and at least one while it was just sitting there on the charger.
For the moment, I'm going on the assumption that this is just some early stuff working itself out. When flashing the ROM, I cleared the Dalvik cache, but didn't do a data wipe. Anyone have any idea if this is a problem?
Again, thanks a million guys!
( Oh, LOVE the noob video! )
Click to expand...
Click to collapse
Well first off, welcome! And yes. You should ALWAYS wipe data, cache, and dalvik at the minimum. It ensures that you have a better experience without lag, freezing, FC's, etc.. You have to do the setup every time, but it's worht it and you get used to it. And most devs don't recommend using Rom manager since it's known to have some issues, you're best bet is to go install through your CWM recovery.
kjsmommy10 said:
Well this isn't the EVO GB Release. It's the actual Incredible release. But yes the speech to text does in fact work.
Click to expand...
Click to collapse
I flashed it. Got in my car, sped up to 35 and tried a Voice Search. Like with the GB leak, google voice search throws up its hands and can't understand you.
AJGO23 said:
Well first off, welcome! And yes. You should ALWAYS wipe data, cache, and dalvik at the minimum. It ensures that you have a better experience without lag, freezing, FC's, etc.. You have to do the setup every time, but it's worht it and you get used to it. And most devs don't recommend using Rom manager since it's known to have some issues, you're best bet is to go install through your CWM recovery.
Click to expand...
Click to collapse
Wow, seriously, ALL data? That means having to set up multiple mail accounts (GMail, private, work) and re-installing all my apps - well, Titanium at least.
Initially, I took over a month to get my phone just the way I liked it, and still wound up tweaking the hell out of the look and feel on a regular basis. Can application data backed up with Titanium be restored to get most of that back? Seems like it would take hours to get it back either way. I never found a thread on this, so I apologize if it is answered somewhere - I'd love to get a link to that thread if it is out there.
Now I think about it, this has been the biggest hurdle to my trying different ROMs. Screw the suits whining about how I use the services and devices I pay for, I just don't have the time to be messing with it that much.
Again, thanks for the info!
Cheers!
What did I do wrong? I DL'd the file in the thread, put it onto my SD card, then turned my phone off.
I rebooted into recovery (power and volume down button), chose update from .zip on SD card. Picked the file and let it update...
Now my phone will boot up and just stay stuck on the "Droid" screen. Any help?
was I supposed to rename the file or anything? Please help, my phone is stuck right now...
Install zip from sdcard not update... And u should of wiped data cache all that junk if u didn't do that
Sent from my ADR6300 using Tapatalk
BMWPower06 said:
What did I do wrong? I DL'd the file in the thread, put it onto my SD card, then turned my phone off.
I rebooted into recovery (power and volume down button), chose update from .zip on SD card. Picked the file and let it update...
Now my phone will boot up and just stay stuck on the "Droid" screen. Any help?
was I supposed to rename the file or anything? Please help, my phone is stuck right now...
Click to expand...
Click to collapse
Did you wipe anything? You should do a full wipe (data/system/cache/dalvik/etc.) before flashing a new ROM.
Cant wait for a 2.3.4/3.0 sense Rom.
keyslapper said:
Wow, seriously, ALL data? That means having to set up multiple mail accounts (GMail, private, work) and re-installing all my apps - well, Titanium at least.
Initially, I took over a month to get my phone just the way I liked it, and still wound up tweaking the hell out of the look and feel on a regular basis. Can application data backed up with Titanium be restored to get most of that back? Seems like it would take hours to get it back either way. I never found a thread on this, so I apologize if it is answered somewhere - I'd love to get a link to that thread if it is out there.
Now I think about it, this has been the biggest hurdle to my trying different ROMs. Screw the suits whining about how I use the services and devices I pay for, I just don't have the time to be messing with it that much.
Again, thanks for the info!
Cheers!
Click to expand...
Click to collapse
You can back up app data, but it is strongly recommended that you don't back up system data. And yes it means starting all over, and I too was skeptical to start over when I first started flashing ROMs, but now it takes me about 15-20 minutes to setup everything again. But then again I only reinstall about 45 apps.
Sent from my ADR6300 using XDA App
BMWPower06 said:
What did I do wrong? I DL'd the file in the thread, put it onto my SD card, then turned my phone off.
I rebooted into recovery (power and volume down button), chose update from .zip on SD card. Picked the file and let it update...
Now my phone will boot up and just stay stuck on the "Droid" screen. Any help?
was I supposed to rename the file or anything? Please help, my phone is stuck right now...
Click to expand...
Click to collapse
Boot into recovery and wipe everything 3x. Next choose install zip, then after that DO NOT CLICK ON update.zip, select choose zip from SD, then find your downloaded file (wherever you put it) and select that.
Has anyone tried any Bluetooth devices? Keyboards or such to see if we did in fact get the full bt stack?
Sent from my ADR6300 using XDA App