When you flash a new ROM, is it a complete reinstall of the OS, or just changing certain items while still keeping many basic elements as-is? Put another way, when you flash (and select to wipe data in ROM Manager), does it reformat the OS partition and then reinstall a fresh copy of the OS?
I've been rooted for quite a while (just for the free wifi tethering) but haven't flashed custom ROMs until today. I've been having a problem with all my media players' (ACast, Astro, the stock player) pause function since I installed Froyo. Essentially, after I pause a track, the player will hold the place. But just after I resume, the track restarts from the beginning. Because it's on all my players, it seems to indicate that there's an issue in the OS. It's been driving me nuts, and finally got me to flash my first ROM (Virtuous) in hopes that it would eliminate the problem. Everything worked fine, but the pausing issue remains, which would indicate that either every version of DInc Froyo has this problem or that errors that were in my original install of Froyo have been carried over to this custom ROM.
While I've seen mention of this problem with multiple DInc users, it doesn't seem to be widespread. I'm hoping to do a "fresh install" to see if that would get rid of the problem. Sorry if my terminology is too computer oriented, but flashing ROMs is still new to me.
Flashing does not reinstall Android, the OS.
ROMs, a set of instructions/code, sits on top of Android.
Hence, each ROM has it's own set of instructions (apps/features), driven by Android.
There are several ROMs out and about w/ some pretty slick/modded audio players - take a look through the Development thread and the feature list(s) for ROMs with tricked-out audio players.
You could try winamp player, I find it to be one of the best media players.
If you've already flashed Virtuous then I don't see how another ROM could help the problem but perhaps smtom is right as there may be another ROM out there with better audio players.
Thanks to both of you for your reply. Winamp also suffers from this problem for me. Unfortunately, I think that all the media players seem to be built on top of the same area of the Android OS (that appears to be corrupt for me). Since flashing ROMs won't work, is there a way to reinstall the OS?
Would running a RUU work?
Well ...you could try taking it back to stock and start over ...
Sent from my ADR6300 using XDA App
smtom said:
Well ...you could try taking it back to stock and start over ...
Click to expand...
Click to collapse
I just tried to do this - I ran the original Froyo RUU (not the latest) which took me out of root (although I still had S-OFF). The first thing I did (before installing a bunch of apps, rooting, etc) was to try to play media and pause...the problems persists. So frustrating.
chaint said:
I just tried to do this - I ran the original Froyo RUU (not the latest) which took me out of root (although I still had S-OFF). The first thing I did (before installing a bunch of apps, rooting, etc) was to try to play media and pause...the problems persists. So frustrating.
Click to expand...
Click to collapse
OK - color me out of ideas on this one then...
Assume you have read thru the threads of the ROMs you've flashed (CM particularly - not because that's the cause or even that you flashed it, rather that ROM uses SD for lots of stuff) to see if anyone else is encountering this?
Have you tried flashing an AOSP (not a Sense-based) ROM to see if this happens on those too?
Those media players are pure android; some of those ROMs offer players in addition to the pure android player
To be fair, sense ROMs have sense-based players as well as android media players - just a thought to try an AOSP ROM.
Try CM, Ruby, UltimateDroid - lots of choices. I can attest, the media player(s) on UltimateDroid are unlike anything I've used before, although I cannot say whether they'd solve what ails your device unless you try some other stuff.
btw - is your music loaded on the internal memory, or on the SD? Speculation, but have you tried moving it from where it is, to the other (internal to SD or vice-versa) and the issue remains? And, is your radio updated to at least 2.15.xx?
Best of luck - please update if/when you resolve this, so the learning/knowledge can be shared.
smtom, I've seen a few other users mention this problem as well, but as you point out, it doesn't seem to be very widespread. I ran the new Verizon update (supposedly with Bug Fixes) last Friday and that hasn't helped either. Very frustrating.
I found this thread - LINK - that mentioned that the problem may be linked to the Facebook for HTC program.
As a quick background, I haven't flashed any ROMs other than Virtuous, and that didn't help. I'll try CM and report back.
Also, I have music on my stored on my internal drive and podcasts on my SD card. It seems to make no difference.
Do you use any Facebook app? And if so have you tried uninstalling any/all of them and does the issue persist?
Sent from my ADR6300 using XDA App
This does pose an interesting question on completely fresh installing android. Wouldn't a nand flash be a complete resintall? usings pb1331.img?
Related
I don't post here often, but I am on IRC all the time for those of you that do know me. I have been having serious issues with the AOSP Roms. Cyanogen, Ruby, and Incredible Does all either freeze on me or reboot sooner or later. I've went so far as to install nothing else except the Rom and it still freezes or reboots. I've done this test with all three, I even dialed down the processor while on them and still NO DICE. I'm not an Android expert, but I do have a bachelor's in IT so I feel I'm pretty tech savvy. I was told on IRC that others are having similar problems with all the AOSP roms. I'm trying to get a consensus of who else is experiencing this and some more suggestions on how to fix this.
I appreciate all the help
~Thanks , AnthonyKash
Yeah this is very odd. A couple of us in ##incredibleroms have been working with AnthonyKash to figure this out. So far we have had no luck at all. No Sense UI ROMs do this to him, it seems like it's only vanilla ROMs. Very strange............
anthonykash said:
I don't post here often, but I am on IRC all the time for those of you that do know me. I have been having serious issues with the AOSP Roms. Cyanogen, Ruby, and Incredible Does all either freeze on me or reboot sooner or later. I've went so far as to install nothing else except the Rom and it still freezes or reboots. I've done this test with all three, I even dialed down the processor while on them and still NO DICE. I'm not an Android expert, but I do have a bachelor's in IT so I feel I'm pretty tech savvy. I was told on IRC that others are having similar problems with all the AOSP roms. I'm trying to get a consensus of who else is experiencing this and some more suggestions on how to fix this.
I appreciate all the help
~Thanks , AnthonyKash
Click to expand...
Click to collapse
I know you posted this months ago but was wondering if you figured out what is causing this? I too can't use ANY aosp Rome because they all end up being unusable after a couple of hours. It's almost like the CPU slows down to a dramatic crawl. Only way to fix is to do a battery pull to reset. I have cleared cache, dalvik, uninstalled setcpu, all with no luck. Anyone have any insights?
Check integrity and space of SD card - maybe even remove, copy contents to PC, reformat to FAT32, copy a few nandroids back to SD and reinstall in device. Also make sure there is ample space on SD.
Absent that, have you tried a different SD card? AOSP ROMs interface w/ the SD considerably more than Sense ROMs.
Also, check radio version - recommend at least 2.15.xx
HBOOT version may come into play as well.
+1 to the above post. Seems like some sense files are bring left somewhere.
Sent from my ADR6300 using XDA App
smtom said:
Check integrity and space of SD card - maybe even remove, copy contents to PC, reformat to FAT32, copy a few nandroids back to SD and reinstall in device. Also make sure there is ample space on SD.
Absent that, have you tried a different SD card? AOSP ROMs interface w/ the SD considerably more than Sense ROMs.
Also, check radio version - recommend at least 2.15.xx
HBOOT version may come into play as well.
Click to expand...
Click to collapse
I don't think its my SD Card, I just got a new one a month ago and the same thing happened with my old SD Card. I have 4 gigs left empty of a 16 gig sd card. Would it make a difference if I installed from EMMC using RA recovery?
Hboot 0.92
Radio 2.15.00.09.01
Am on the latest versions of Hboot and radio right?
One thing I do find very weird is that even after doing full wipes of user data, cache and dalvik, when I boot up on CM7 my wifi settings still work. I would have expected I needed to reenter all of those settings. Or does this stuff get saved to the SD or internal storage...normal? If it is not, then why are data wipes in Recovery not cleanning up my files?
I've not had this problem.
Sent from my ADR6300 using XDA App
greatchief1 said:
I don't think its my SD Card, I just got a new one a month ago and the same thing happened with my old SD Card. I have 4 gigs left empty of a 16 gig sd card. Would it make a difference if I installed from EMMC using RA recovery?
Hboot 0.92
Radio 2.15.00.09.01
Am on the latest versions of Hboot and radio right?
Click to expand...
Click to collapse
Yep, those are the latest versions.
AOSP ROMs offer automatic reinstall of apps and data to Google when flashing, if that option is checked when flashed. That's where/how/why settings and/or apps still appear as before.
So, if Sense ROMs are not wonky, maybe it is an app you have installed on the AOSP ROM?
Long diagnostic road, (well understood by us IT folk ) but perhaps uninstall apps in reverse install date order of the app, reboot as you go thru, see which one may have been a culprit.
Absent that, perhaps factory reset in recovery, install an AOSP rom w/out choosing to reinstall apps.
Maybe try another different AOSP ROM?
I know the SD interacts quite a bit more with the SD compared to Sense ROMs - again, maybe copy SD card contents to PC, reformat SD to FAT32 either on the PC or in phone, maybe both - then d/l an AOSP ROM on a clean SD, see if it's still wonky.
smtom said:
Yep, those are the latest versions.
AOSP ROMs offer automatic reinstall of apps and data to Google when flashing, if that option is checked when flashed. That's where/how/why settings and/or apps still appear as before.
So, if Sense ROMs are wonky, maybe it is an app you have installed?
Long diagnostic road, (well understood by us IT folk ) but perhaps uninstall apps in reverse install date order of the app, reboot as you go thru, see which one may have been a culprit.
Absent that, perhaps factory reset in recovery, install an AOSP rom w/out choosing to reinstall apps.
Click to expand...
Click to collapse
Sense ROMS work great, its AOSP roms that are giving my phone fits lol. Well last night I tried something new.
-I changed my radio from 2.15.00.09.01 to 2.15.00.07.28 Official Froyo radio.
-Installed CM7 #14 from the EMMC versus SD CARD.
-"Hit Wipe All" in recovery about 10 times in a row before I flashed CM7
I hope changing the radio to "official" is what does it. Anyone running AOSP roms using the leaked radio 2.15.00.09.01 ?
Radio?
Yes, do let us know whether the xx.09 radio was the (a) culprit.
I run the older 2.15.xx.07.28 one, never had issues w/ AOSP ROMs.
I had an issue with this using cm7 nightlies, and I WOULD post it there but the new, ~totally awesome~ rule they are implementing (can't post in the dev forum w/ less than 10 posts) prevents me from doing that (Which means I have to spam the other sub forums?).
ANYWAYS, I got a bigger sd card from a friend, and I went to erase it under the sd card settings. Then i got a low space notification, saying I had 9 mb free of 7 Terbytes. Rebooting the phone caused it to go into boot loop. If your situation sounds like mine then do this
Boot into CWM, and from there you can mount the SD card and format it, as well as copy any backups.
I did not have any luck with restoring the phone to a previous AOSP rom, even after wiping the cache/dalvik. Maybe there's another one that could be wiped that I didn't do. Anyways, I installed a Sense based rom, and from there I was able to install Cyanogen mod.
Good luck.
smtom said:
Yes, do let us know whether the xx.09 radio was the (a) culprit.
I run the older 2.15.xx.07.28 one, never had issues w/ AOSP ROMs.
Click to expand...
Click to collapse
Well it turns out that the radio version I was using was not the issue because the phone became unresponsive this morning when I tried to wake it up. To be specific, it does allow me to swipe to unlock but painfully in slow motion.
So that rules at the radio...which leaves me with its either the ROM/Kernel or some rogue app.
So this morning I wiped all user data in recovery and reinstalled CM7#14 but this time I did not log on to my google account during setup and have not installed any apps. So far no issues, but the true test is trying to wake the phone up tomorrow in the morning. If there are no issues, then that solves it (ITS A FREAKING APP).
If it is a rogue app that has been haunting me these past couple of weeks then who has the best way to identify which one is the offender? Why would a rogue app only affect me using AOSP roms and not Sense?
My suspicions are with..(Locale, Beautiful Widgets, ADW EX, Swype, CardioTrainer, Handcent) but I guess process of elimination is what its going to take.
Thanks to all for the help and recommendations.
cougar618 said:
I had an issue with this using cm7 nightlies, and I WOULD post it there but the new, ~totally awesome~ rule they are implementing (can't post in the dev forum w/ less than 10 posts) prevents me from doing that (Which means I have to spam the other sub forums?).
ANYWAYS, I got a bigger sd card from a friend, and I went to erase it under the sd card settings. Then i got a low space notification, saying I had 9 mb free of 7 Terbytes. Rebooting the phone caused it to go into boot loop. If your situation sounds like mine then do this
Boot into CWM, and from there you can mount the SD card and format it, as well as copy any backups.
I did not have any luck with restoring the phone to a previous AOSP rom, even after wiping the cache/dalvik. Maybe there's another one that could be wiped that I didn't do. Anyways, I installed a Sense based rom, and from there I was able to install Cyanogen mod.
Good luck.
Click to expand...
Click to collapse
Please tell me u meant 7gb not 7tb
If you have a SD card that huge I beg you to tell me where to get it
I've heard of a 2tb SD but they haven't released it
Sent from my Incredible using XDA App
just wanted to give an udate on my issue...as I suspected it was an app that was causing my phone to crash using aosp roms. The offending app is Locale, wierd that a it never gave me problems using Sense based roms.
greatchief1 said:
just wanted to give an udate on my issue...as I suspected it was an app that was causing my phone to crash using aosp roms. The offending app is Locale, wierd that a it never gave me problems using Sense based roms.
Click to expand...
Click to collapse
Good stuff. Glad to see it all finally worked out.
Hey everyone,
Ever since I bought the TP2 I've had issues with every rom I tried. I started with a 6.1 build. not long after that several updates where released by HTC.. but I kept issues with crashing software, freezing etc. This both with a clean build and with some approperiate software installed. I did notice that when I used a backup program the system was more unstable than when it was a complete clean build.
After the 6.5 releases I was about to throw the phone out of my window. I tried a bunch of roms, from the simplest builds available to several others. But no matter what I try the phone keeps freezing, and crashing. I also have issues with the alarm not going off sometimes.
When I installed third party roms I used the recommended radio's. and I followed the instructions given, which includes whiping the system before I install a new radio and rom.
I've searched the web for this but I haven't found out what this could be, maybe any of you have a clue what the problem could be.
Thanks in advance!
Dion
Ownsta said:
Hey everyone,
Ever since I bought the TP2 I've had issues with every rom I tried. I started with a 6.1 build. not long after that several updates where released by HTC.. but I kept issues with crashing software, freezing etc. This both with a clean build and with some approperiate software installed. I did notice that when I used a backup program the system was more unstable than when it was a complete clean build.
After the 6.5 releases I was about to throw the phone out of my window. I tried a bunch of roms, from the simplest builds available to several others. But no matter what I try the phone keeps freezing, and crashing. I also have issues with the alarm not going off sometimes.
When I installed third party roms I used the recommended radio's. and I followed the instructions given, which includes whiping the system before I install a new radio and rom.
I've searched the web for this but I haven't found out what this could be, maybe any of you have a clue what the problem could be.
Thanks in advance!
Dion
Click to expand...
Click to collapse
What ROMs have you tried? When you say you wiped the phone, you mean you ran Task29? If not, I would highly recommend doing so before every ROM flash. Also after the phone boots up after the flash, hard reset to empty the storage memory, just to be safe. May or may not help, but can't hurt.
I run the ROM stated in my signature, and it very rarely freezes or crashes, and thats with the CPU overclocked to 729 MHz.
Most backup software is not meant to move from one ROM to another (and can cause a lot of problems is you do so), only for backing up and restoring within the same ROM. Try some research on the specific backup application you use, to see if this is the case.
I run the 21916 Energy ROM. I have tried several different ROMs and they all seem to pretty much work the same. The only ROM I have ever had crash or lock up on me is the factory TF3D based rom. I always use the task 29 and flash any rom I want to try.
Hope this helps.
First of all, thanks for the fast replies.
I've used task29 with every new flash. I might try it again without using a backup. And I will also try to overclock it a bit. I've done a dozen of hard resets allready, and I soft reset the device on a daily basis. Might this be a hardware issue if I keep getting the issues? If so could it be worth it contacting HTC ?
I think you misunderstand about the overclocking. Overclocking would INCREASE the chances of you having freezes and crashes.
Other than on SOD I got in the 1st week of owning my Tilt 2, all my crashes have been related to overclocking or something I was doing with the phone that I shouldn't have. Yes, I sometimes have to reboot the phone because TF3D has notorious memory leakage, but other than that my phone runs great. I read about a lot of people having random lockups when doing normal phone stuff (mostly TP2 owners) and I have to wonder if they just got defective phones. Other than that 1 unexplainable SOD, I know exactly why my phone doesn't behave as it should and it isn't that often. I've been overclocking it at 748 for a month without issue.
redpoint73 said:
I think you misunderstand about the overclocking. Overclocking would INCREASE the chances of you having freezes and crashes.
Click to expand...
Click to collapse
Well, in that case I will not overclock anything!
Which rom do you guys recommend as one of the lightest and most stable roms? if I got the same issue with a clean build I will put everything to stock and contact HTC about this.
The simplicity ROM that I show in my signature is very lightweight, smooth, and stable. Its the best I've used do far.
I will try that one without restoring a backup then. Many thanks guys !
The UK 3.4.2-117 froyo showed up not to be as stable as first seen, some apps crash all time and the phone to from time to time, especially the screens keeps to timeout alot and sometimes freezing the phone totaly when doing it.
Anyway, when trying to install the sbf rom with eclair 2.51 with RDS i am able to install it but not able to make the phone to start after that. Any suggestions to why, is this due to the current 2.51 eclaire version beeing branded? I started out with a 2.21 version before going to the new gb froyo rom. Pherhaps not downgradable meant exactly what it said
Thanks for suggestion...!
I have had no problems whatsoever with the UK Froyo release. In fact, I find it to be the smoothest release yet, as I have mentioned in its respective thread; Even without overclocking, it is a lot smoother than the Chinese Froyo and 2.34.1 and 2.21.0 before that. Ofcourse the quadrant 'score' is lower, but as I do not use my phone mainly for benchmarking, I do not mind in the slightest.
Anyway, before I go off-topic too far..
Have you made any modifications to the release after you put it on your phone? Did you perhaps not wipe the data/cache? Is it possible that you are overclocking your phone to such an extent that it is no longer stable?
And for some specifics - which applications crash all the time for you?
And indeed - you can not downgrade unless you've followed the instructions in this thread by Higgsy, but I doubt you have.
Incidentally, nor have I, but I have no problems whatsoever with this release and since we have the same phone, I suspect you have changed or installed something to cause your problems.
Hi!
Yes basically i got a new defy, UK retail, it was never rooted or anything and i just applied the new ROM with RDS. So no, I had not done any changes to the version what so ever and i reinstalled it twice, always making sure to offcoures wipe it also.
My main issue is actually that the screen times out alot, and sometimes locks the phone so i need to take the battery out. Also a music app (spotify) crash inevitably all time, it comunicates with the memory card as it catch up the music as you listen so thinkning that it may be some issue there. Have seen some of my other apps also force close, and this has never happen to me on this or my second (my gf's) defy i had had for some months now.
I to however are supprised about this as I can see that no other is experience this issue, espeically the screen timeout issue wich is very annoying and happens alot especially when using the browser
Will try to find a new microSD card later tonight to see if my memory card pherhaps have been somehow dammaged during the ROM installation... (dont belive at all this would have happend but worth a try i guess)
Thanks
Hm. That is quite the pickle you are in.
Can you install Catlog, filter on Errors, and tell us what it reports? You can run the application after you start the phone and have it log to file - you can put the file in
Code:
tags here to make it easier on the eyes. There may, or rather - should be a clue in there.
Alternatively, you can use 'adb logcat' from a command prompt in the Android SDK/platform-tools to get the log files to display outside the phone.
another reinstall of sbf did the trick! Will try to run the logcat to later to figure out what the app problem could be (maybe sd card read write issue I think as sameprobkem with second card) but now the phone works otherwise perfect, many thanks...
Good to hear - enjoy the shiny new release
Same problem help.
Hi I flashed the UK 3.4.2-117 froyo ROM with RSD.
My Defy was T-Mobile UK, 2.51 ROM.
After flashing the phone starts but I only get a black screen.
The softkeys are not responding but I can tap down the notification bar and open a task manager program that I had pre-installed which allows me to switch through applications. I can open various applications and the phone seems to be working like this.
I rooted successfully and then I tried to reboot into recovery using Clockwork Mod but the phones stays at the motoblur logo.
Is there anyway to downgrade or at least make this rom working?
Michalis
I have experienced some things like you sayed; some apps get closed, and frozen phone and can't even turn off the phone
so i uninstall some apps that i don't need, and get a app name SystemPanel that monitorize the CPU use to see whats going on
Since then, i don't see more those things. I'm watching see whats going on
is it possible to install roms to a sd card, and when switch phone on select which one to load to?
I have used sense stock and ARHD since owning phone, and happy with it, just installed a cm nightly, and likling its lightweightness, want to check miui and also will want to try ICS whe navailable, and also wouldnt mind trialling a few of the other roms out there. but hate having to reconfigue it to my settings and re download all my apps again (doesnt seem to do it automatically).
so has anyone developed a way to install roms to a sd card and boot into whichever one, then they can be pre configured, apps stored all in one place that each rom access' al ldata is shared (to save space and eliminate duplicates of same data for each rom)
im not a great techy, but heard you can have multiple os on a pc in partitions?, and thought read something similar was developed for HD2, but cant find anything for the desire HD.
thanks for reading..
I do remember some efforts to dual boot this phone but I dont know where they went. Most likely stopped. There was a beta though.
There's an app in the market called Boot Manager which allows you to do that (for up to four ROMs if I remember correctly). There was a thread in the dev section about while it was still in beta, should still be floating about.
Disclaimer: I've never used it, just pointing out that it does exist.
//sent from my Desire HD using Tapatalk; all errors entirely intentional.
Edit: Double post, because I'm on my phone and still half asleep
There are a few of us out there that use Boot Manager
I've not had any major issues and the Dev's are quick at getting things resolved for user's that may have issues.
Depending on the ROM you are trying to install, due to custom install scripts and the like - you can run into install issues.
#However SmokeyBong has very kindly produced backups that can be restored via boot manager and then they work fine - http://forum.xda-developers.com/showthread.php?t=1257450
The Dev's thread is here - http://forum.xda-developers.com/showthread.php?t=1184173
They also have a forum and some other usefull apps.
Please note I'm not trying to sell you their products and/or services - just a happy user of Boot Manager.
If you go ahead and buy/try etc and have issues someone here will help you out.
Thanks,
Del
Brilliant that sounds like what I need. Ill try. And will buy if does as I would like. Thanks for replies
Sent from my Desire HD using XDA App
So I recently found an old Galaxy SII Epic 4G Touch lying around and I thought I would play around with it a little bit.
Little did I know it was gonna be a complete hell
So in all of the confusion of simply not being able to flash whatever the heck I wanted (since the kernel and recovery are apparently both within one monolithic binary), I have now run into a different issue.
So, on this phone so far, I have somehow managed to crash, break, and soft brick my way into successfully installing CyanogenMod 11 (4.4.4 KitKat), CWM 6.0.5.1(I think yeah totally), and the pico loadout for 4.4.4 gapps. I reeeaaally enjoy taking these phones that manufacturers destroy with preloaded launchers, bloat, etc. and fixing them up nice to look like they just rolled off the Google showroom with a fresh installs of all stock gapps, and silky smooth android. But here's where my issue comes in. I spent the good part of today just looking for a full gapps package with all stock gapps that would work on this thing. I sifted through unsafe websites, dead links, and throughout (what i think is) most of this forum to find something that would work, but couldn't. Thought it was issues with not being able to install PA packages onto Cyanogenmod. But that wasn't my issue. (the recovery kicked out error after error each time I tried. So it was an issue for sure. I realize that. Just not the issue I want to solve here and now) So then, I decided to simply run another factory reset, do another fresh install of the OS, and cave in, and use the nano app package. This package was the only one to give me some kind of response. It essentially said that my /system/ partition was too small to accept all of the apps on it. And then it dawned on me. The internal storage on this phone is separated into 2 partitions. 16gb. 1.97gb for system use, and the rest for downloaded apps, media, etc.etc. . I want to know if there is a process - for this phone specifically - to merge those two partitions together so that I can get a stock looking gapps install on this guy. I don't plan on using this phone for anything in particular. Just doing this for fun.
Anyone got any answers? I've seen similar situations floating around here and other places with other devices. And it's doable(????????), but all of the methods shown are for those specific devices, and I would rather not try and replicate them here if somehow something is critically different.
Thanks for any response at all. Seriously. If it's just to tell me I'm a big stupid and this won't and can't work, I will still appreciate it.