Hi all, I rooted my dell streak last night with superoneclick, it worked fine after a bit of messing around, but ever since if I d/l an app from the market or elsewhere, itll d/l but hangs on installing. Ive searched but to no avail, not much on google either. Is this a common issue? Ive tried reboots and clearong market cache, but even have the same issue when Installing from sdcard. Any thoughts? Cheers for any replies. Sanders
Also, just tried to play some music, loudspeaker aint working??
rooting shouldn't be causing an issue here as far as I know, I take it you are running stock rom? Do your headphones still work? Sounds like you may have bigger problems though unfortunately. You can always try unrooting to see if the problems go away or do a dell factory reset...
Funnily enough, speakers working fine now. Still no apps installing though, yes im on dells 2.2. Ill try unrooting.
Thanks
Sent from my Dell Streak using XDA App
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"?
Hi everyone, I've been trying to search around for a way to fix my phone and I have not been able to. I permanently rooted my mytouch 4g with cyanogen 7. Everything was fine except I realized today that none of my sound works. I have music on my phone and it will play if I set it as a ringtone but it wont play in any of the music players I have tried and sound on the internet does not work either.. such as youtube. I've tried hooking up headphones and that does not work as well. Can anyone help? I'm new to rooting phones and may need a noob version of how to fix it. Thank you!
First try rebooting. If that doesn't work I'd wipe the phone completely, and then re-flash CM7 and Gapps.
TeeJay3800 said:
First try rebooting. If that doesn't work I'd wipe the phone completely, and then re-flash CM7 and Gapps.
Click to expand...
Click to collapse
Took the words right out of my mouth
Sent from my HTC Glacier using XDA Premium App
I've been searching for the last few days and have yet to really find anything to help me fix my problem.
the story:
Phone was rooted, back in Jan and I was running GummyJar 2.5, no problems, went to Apex V 1.3, no problems, but it ran a little slow. Today I decided to switch to something else to attempt and fix the speed problems, first I tried Incredibly Re Engineered v1.0, the phone ran well, but every 2-3 minutes it was rebooting me and sending me to the clockwork screen. So then I figured it had something to do with the ROM, so I went to Fission 2.5.7. Same problem, the phone runs great when it's on, but the constant restarted is unreal. I've done a factory reset, unrooted then rerooted the phone, then reinstalled the ROM, same problem.
Anyone ever have this issue and have a solution?
Thank you,
Eric
edit: Phone acts fine while plugged in to the computer or wall charger. Also made and attempt with SBF, to no avail.
Try an sbf....then go back to fission.
Just my thoughts. No overclock at first.
Running the SBF restore again...we will see what happens.
Hopefully someone else will stop by with thoughts.
Fission for me is real stable, ran it for long time now.
Worried it may be hardware problem....?
Might want to only install important apps at first also.
Try wiping data from Clockwork several times.
If that doesn't work you should definitely try SBFing and wiping data several times afterward.
Sent from my DROIDX using XDA App
I agree, I also loaded several ROM's and had a growing list of issues, SBF took care of everything for me.
Mine reboots when I pause video playback when connected with hdmi. But only since gingerbread, and I'm on my fourth version of gb. They have all done it so far, hoping official .596 will fix.
DX 2.3.3
Did the SBF'd it. Phone works flawlessly. I am now running Fission and Launcher 7, all without a hitch. Guess the phone just had to much going on and needed a fresh start.
Thank you all for the input. After I get a few more posts, I will post links and a DIY on how to do what I did. It was difficult for me to find anything with all of the steps and links in one spot, I want to make it easier for the next person experiencing this problem.
Yay! ....
Hey I been having the same problem with my droid x mines runnin stock 2.2.1 tho but it just keeps restarting and I don't know how to fix it lol. Im kinda new to this phone so does anybodyy have any suggestions?
Sent from my DROIDX using XDA App
CHip0,
SBF it...it's fairly easy and you can even find a youtube on how to do it....
http://www.youtube.com/watch?v=c58XaWnr6XE
Thank u very much! Lol
Sent from my DROIDX using XDA App
So like the title says, I'm a new Nexus 6P user, and I had problems out of the gate.
I bought the device 2nd hand from a guy off craigslist, after my S6 edge started over heating after I had the screen replaced (don't buy Samsung "edge" phones, I know your careful, but on the off chance you drop it, your in a world of trouble).
I tested the phone, before I bought it, it appeared pretty much brand new, everything worked. When I got home, and hard reset it again for good measure all hell broke lose.
After a hard reset the phone wanted to update to build 19 something. After the update and a reboot, the phone app kept crashing before I could finish the setup process. The only thing I could do is factory reset it again. This appeared to clear up that problem. I did the near by device thing, and restored it from what Google could find out about my S6 edge. I wish it was more of a restore like what you can do in the iOS world, but it's better then what we had before so it's cool. I noticed that Chrome would crash everytime you tried to use it only in less I uninstalled the update. After I got the phone to the point where I wanted it, I thought I was free in the clear. When I started trying to use music apps, they all crash. Apple Music, Spotify, Soundcloud. Then I noticed YouTube also crashed the same way. When I tried to make a phone call, the phone app would crash too... So the phone was useless. I downloaded the SDK and the most current build which I think was 20 something. I followed a guide on here and formatted the phone reinstalling everything around build 20. The only thing this fixed was the phone issue.
I could now make phone calls without it crashing, but I was in the same boat with some applications working, and the same ones that didn't work not working. I flashed this phone 5, or 6 times, with the last time me formatting the userdata. I read that it wasn't a good idea because it could lock me to only 32GB ( I had a 64GB version), but after I did the flashing along with the usedata format, I still had 64GB of useable space, however I still had the same issue with the same types of applications crashing. I tried older builds, same issue (also the older builds all had the problem with the phone app crashing to the point that the phone wasn't usable).
I ended up sending the phone to the manufacturer, which appears to be in the same metroplex I live in. Hopefully they can find a hardware problem under warenty and fix it. I'm making this post to see if anyone else ran into similar issues, and if anyone knows if this is a hardware build issue, that was hopefully resolved.
I'm sorry to be so long winded...
Is the phone rooted and running a custom ROM?
Pappy35 said:
Is the phone rooted and running a custom ROM?
Click to expand...
Click to collapse
Everything appeared to be stock, I don't know if it was rooted before, but when I was finished with it it was stock, I even locked the boot loader again (it was locked before I started flashing it)
vmiyoshi said:
Everything appeared to be stock, I don't know if it was rooted before, but when I was finished with it it was stock, I even locked the boot loader again (it was locked before I started flashing it)
Click to expand...
Click to collapse
How much did you pay for it?
Sent from my LG-H830 using Tapatalk
RidinNerdy said:
How much did you pay for it?
Sent from my LG-H830 using Tapatalk
Click to expand...
Click to collapse
I paid 4 for it...
I recently updated my xt575 with the September security patch. Since then my microphone doesn't work only when making a phone call on speakerphone. Normal phone calls, audio and video recording, and voice commands all work just fine. I have tried booting into safe mode with no success, and then did a full factory reset and held off on downloading anything before trying again, still with no success. Is anyone else having this issue? Does anyone know of a fix or workaround for this before I try contacting Motorola? Thanks.
P.s. I am on stock ROM on Att network. I use Android pay a lot so would like to avoid rooting.
SirMiks said:
I recently updated my xt575 with the September security patch. Since then my microphone doesn't work only when making a phone call on speakerphone. Normal phone calls, audio and video recording, and voice commands all work just fine. I have tried booting into safe mode with no success, and then did a full factory reset and held off on downloading anything before trying again, still with no success. Is anyone else having this issue? Does anyone know of a fix or workaround for this before I try contacting Motorola? Thanks.
P.s. I am on stock ROM on Att network. I use Android pay a lot so would like to avoid rooting.
Click to expand...
Click to collapse
Same man. It's weird too. It will fix itself after a couple days - or at least mine did
Sent from my iPhone using Tapatalk Pro
Odd... I am on AT&T, for the moment at least, and use my speakerphone all the time, never had an issue before or after the update.
Try clearing your cache partition maybe?
Same problem
Hello. I'm trying to solve my Moto's mic for over a week now.
I was trying many ROMs, but ended up using TruePureXMM ROM along with franken kernel.
It was all working fine, except some overall phone lag and constantly trying out other kernel auditor settings...
...untill about 2 weeks ago. Phone's microUSB port got damaged, and I had to return my phone to repair service.
After I received it back, I wanted to try out some Nougat ROMs, and tried couple of them, but found out that the mic isn't working properly there.
Decided to return back to stock, using this forums tutorials, done it without any single errors or problems in the process, I did many devices roms changes before.
It didn't help at all. The receiver don't hear me at all, the only sound they can hear is when I blow into the mic's direction.
*Note that when I change to speaker mode, the receiver hear me with some breaks in between, but it's the only way to call from now on...
I'm confused now, completely no idea if it is really the OS problem, or if it's just something with the microphone itself.
Looking forward for any tips, thanks for help.
SR3TLAW said:
Same man. It's weird too. It will fix itself after a couple days - or at least mine did
Click to expand...
Click to collapse
I hope so. It's been a few weeks already... If it doesn't fix itself then hopefully the nougat update will help.
Sent from my Moto X Pure using XDA Labs
acejavelin said:
Odd... I am on AT&T, for the moment at least, and use my speakerphone all the time, never had an issue before or after the update.
Try clearing your cache partition maybe?
Click to expand...
Click to collapse
I have tried that too. Nothing send to help and I've been searching online for a while for a solution with no results. I don't think being Att has any relevance but figured I'd share that anyways just in case.
Sent from my Moto X Pure using XDA Labs
Also on att with September security update and speaker phone works fine.