Related
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?
Well, I searched and could find nothing addressing this directly, at least not on the epic 4g touch.
Yesterday, I rooted with the midnight 2.0, and after most of a day of normal behavior, the stock browser stopped scrolling smoothly. Dolphin HD still works fine, as does everything else I have tested. I tried resetting the browser to factory presets, but no change.
Any ideas? I suppose I could drop back to stock and see if that helps, but what a pain...
JV
The scrolling issue is caused by the overscroll mod added to the Rom. Go back to the Midnight thread and follow the links to his site and the Android Development tab (same place you downloaded the Rom). There you'll see a download for a fix. Only use his fix or you'll screw up the No NIQ.
.....
Desert_rhino said:
Well, I searched and could find nothing addressing this directly, at least not on the epic 4g touch.
Yesterday, I rooted with the midnight 2.0, and after most of a day of normal behavior, the stock browser stopped scrolling smoothly. Dolphin HD still works fine, as does everything else I have tested. I tried resetting the browser to factory presets, but no change.
Any ideas? I suppose I could drop back to stock and see if that helps, but what a pain...
JV
Click to expand...
Click to collapse
Download this, flash it and you'll be all good!
http://forum.xda-developers.com/showpost.php?p=17831476&postcount=39
KingOfThaJungle said:
Download this, flash it and you'll be all good!
http://forum.xda-developers.com/showpost.php?p=17831476&postcount=39
Click to expand...
Click to collapse
God, I am such a noob. Flash it as in "move to /sdcard/, rename update.zip, etc... etc.. etc..."?
Edit: Okay, so I did it through CWM, and it caused a complete freeze halfway through the startup animation. I rebooted a couple of times, no change, and flashed the .zip again, then rebooted a couple of times. No change. Fortunately, reloading the midnight2.0 roms restored the phone.
Whew, I was afraid I had a brick.
Further: scrolling in stock browser still hosed.
I *did* get SVVM back up and running. Yay! (I know, but I'm used to it.)
im running the skyrocket nexusmod ics 2 zero on my tmobile galaxy s2 n it an awesome rom but i hate the web browser, i been looking for one thats not gonna cause a boot loop getting tried of restoring my phone can anyone out here help me out?
SN dont want to use the one in the play store
Try the Chrome Beta browser. I find it pretty stable and fast. No real complaints during the 3 weeks I have been using it. Its in the playstore/
Check out ICS browser+ on google play its the stock ICS browser with slight tweaks
Jrude2262 said:
im running the skyrocket nexusmod ics 2 zero on my tmobile galaxy s2 n it an awesome rom but i hate the web browser, i been looking for one thats not gonna cause a boot loop getting tried of restoring my phone can anyone out here help me out?
SN dont want to use the one in the play store
Click to expand...
Click to collapse
If the stock browser (which should just work 100% of the time, I mean it is the stock browser...) is causing your phone to bootloop and wipe itself... you have a magic browser OR something else wrong with your phone. I would try flashing your ROM again, and don't restore anything having to do with the browser (wipe data, too). It should just work, or else there is something wrong with the ROM (maybe redownload?).
daveid said:
If the stock browser (which should just work 100% of the time, I mean it is the stock browser...) is causing your phone to bootloop and wipe itself... you have a magic browser OR something else wrong with your phone. I would try flashing your ROM again, and don't restore anything having to do with the browser (wipe data, too). It should just work, or else there is something wrong with the ROM (maybe redownload?).
Click to expand...
Click to collapse
the stock browser works perfectly i just personally like the ics browser cuz i had it on my hd2 using the rom paranoidandroid (awesome rom by the way) n i love the browser so i tried flashing custom ics browser n they keep causing bootloop grateful for the great suggesting i receive n imma use the one in the play store
I'm not entirely sure where this topic would go, but I have figured out how to get wildchild 2.0 and 3.3 up and running on the VM WFS. It might work for other CDMA Wildfires, but I'm not sure. I figured it out after reading a post by 'threefootsmurf' who said he got it working. I'm just making a tutorial on how to install it and get it running fully without problems, since I had a few problems, and to show that we have a great rom for CDMA phones. Oh and these steps are pretty straightforward, but I left out things like backing up everything since you should be in the habit of it already.
1. Download the wildchild file. Either 3.3 or 2.0, I have found that the odex version for 2.0 and the deodex for 3.3 tend to work better than the other..
2. Download the 'Hensemod' VM patch.
3. Put them on the root of you micro sd.
4. Boot to recovery and factory reset and wipe dalvik
5. Flash the wildchild ROM.
6. Boot the phone and go through everything, you will probably get error messages and the phone may shut off and power back on, but your main goal is to get to the home screen after doing the google setup and everything.
7. Reboot back into recovery and do a factory reset and dalvik wipe again.
8. Flash the hensemod VM Patch. (You may need to reflash the rom again and then the VM patch in one go here, it all depends)
9. Boot the phone and go through the google set up and everything again, and the phone should be in working order.
Those were the exact steps I used. I tested multiple ways to do it, some gave me bootloops, some stayed on the HTC splash screen, and some kept rebooting the phone. I like the wildchild ROM and this tut will open up the wonderful rom for VM and possibly all other CDMA users. I hope this helped you guys.
Wildchild 3.3: http://forum.xda-developers.com/showthread.php?t=1842771
Wildchild 2.0: http://forum.xda-developers.com/showthread.php?t=1652973
Hensmod: http://forum.xda-developers.com/showthread.php?t=1434497
thanks for the shout out.
yeah not sure why exactly but i usually need to flash the keyboard add-on to get any keyboard function. and the flashing of the rom on official CWM for marvelc seems to have its issues like deodexed don't like to load right or boot loops. after i switched to the unofficial CWM touch recovery for our phones not an issue at all loading after flash. and i usually flash it all at one time. if anyone has the same CWM as me, to do a data/cache reset select it then press vol up 5 times and you are on yes even though you can not see the option, press power and let it finish its wipe. definitely a great fast rom. found some new tricks i wasn't to test so might go back up to 3.3 soon for the extra speed boosts, only thing holding me back is i don't want to spend a whole night restoring my apps backups again lol.
love experimenting with this little thing though even if i am slightly noob to droid
I advise you to post tutorials like this in the General section
threefootsmurf said:
thanks for the shout out.
yeah not sure why exactly but i usually need to flash the keyboard add-on to get any keyboard function. and the flashing of the rom on official CWM for marvelc seems to have its issues like deodexed don't like to load right or boot loops. after i switched to the unofficial CWM touch recovery for our phones not an issue at all loading after flash. and i usually flash it all at one time. if anyone has the same CWM as me, to do a data/cache reset select it then press vol up 5 times and you are on yes even though you can not see the option, press power and let it finish its wipe. definitely a great fast rom. found some new tricks i wasn't to test so might go back up to 3.3 soon for the extra speed boosts, only thing holding me back is i don't want to spend a whole night restoring my apps backups again lol.
love experimenting with this little thing though even if i am slightly noob to droid
Click to expand...
Click to collapse
I know what you mean I'm a pretty big noob at this stuff too, but it's fun thinking I have some kind of involvement in something. I'm using WC 2.0 right now since I can't get 3.3 to load on the odexed version with wifi and data working. I gotta edit my post. I got the deodexed version running, but it's got bugs, like FB wont work, and a few apps wont work right either, and of course no A2SD support... Lame. And I tried flashing all at the same time. But i'd get bootloops with 2.0. So I had to do it the way I described. Not sure if it's my phone my recovery or what. But yeah....
THANKS
This should be stickied for marvelc.
Thank's wc running great on marvelc.
Sent from my HTC_A510c using xda app-developers app
I just flashed WildChild 3.3 to my VMUSA Wildfire S last night. Here is my experience so far:
Definitely install WC and the VM patch right on top of each other in one shot
Skip the keyboard tutorial in the setup
If you get to the wifi setup and yours isn't listed, you need to wipe/reset/clear dalvik and install both files again or you're gonna have a bad time
I've got video playback problems. Videos I record playback with horizontal matrix green crap, and videos in the YouTube app give me audio only
Opinion: There are a few things I don't like about WildChild which are causing me to abandon it after 24 hours. The video issue is unacceptable, and a bunch of strange app choices make this not much better than the crap apps that come with HTC/VM Sense to begin with. Stock browser is absent in favor of Dolphin, no Google Talk app, no default Calendar, required use of Startup Manager (Free) which I feel is pretty useless to me, and a whole list of other apps (like a dozen) I am too lazy to deal with. I realize what I am looking for is a barebones setup, and I'm going to look for it starting now.
Thanks for this post. I've been running Wildchild 2.0 for a few months now. The video issue mentioned above comes & goes with certain app installations - oddly enough a reinstall of the youtube app usually clears it up on my WFS.
Hi guys, i swear i searched! for like days! i still haven't found out how to solve this issue. problem started when i tried hellybean a few weeks back, and then i heard someone on the thread said to try and use the latest beta uber kernel at the time, and i did. What end up happening was that my hardware keys are dead, the lights still works but very dim, i think this is because of the swipe to wake thing where it leaves your hardware keys on 24/7 as long as the phone is on, which is not that bad because i'm now used to using the nav bar. but the real problem is that now every time I install a rom that is not JB 4.1 (haven't tried 4.2 though) i.e. 4.3, 4.3.1, it gets stuck at the app optimization screen, it would go about half way through optimizing the apps, and then just reboots itself, and it'll do that over and over, like boot loop but it can actually go into the rom. So i think this is not as bad as a situation as soft bricking or hard brick, but i just really don't know what the heck is going on to even try and fix it. I've tried odin, thinking that there may be something wrong in the boot file, nada, factory reset, nada, the only thing that worked was installing the 4.1 roms, i think it is because the 4.1 roms don't require app optimization.
If anything maybe anyone out there can help me find a way to disable app optimization? maybe that'll let me get into the rom.
btw, i dont really mind using 4.1, but i really want to try the jedi rom, but having my hardware buttons dead and jedi rom being TW and it doesn't seem to have a nav bar make it impossible for me to use the rom, so i've only been able to use cyanogen 4.1, which are great but they are pretty outdated, so if there are anyway to fix that, lmk too.
Anyways, any help would be appreciated thanks a ton guys! sry for essay!
have you used the infamous cache wipe? http://forum.xda-developers.com/showthread.php?t=2235141 try this and it should fix your issues its because your going from AOSP/AOKP to TW they dont like each other lol follow those instructions and you should be good. also what recovery are you using to flash these?
krazierokz said:
have you used the infamous cache wipe? http://forum.xda-developers.com/showthread.php?t=2235141 try this and it should fix your issues its because your going from AOSP/AOKP to TW they dont like each other lol follow those instructions and you should be good. also what recovery are you using to flash these?
Click to expand...
Click to collapse
Lol actually the problem started when I was on 4.3, and then upgraded to 4.3.1 helly bean, in which i tried to use the beta uber kernel, that was when the problem started. So the only roms that allows me to get pass the optimization screen were the 4.1.2 roms, which were TW, pananroid, like i tried a bunch, like super old ones, they all worked, just that when i try to get any rom higher than 4.1.2, it keep going back to that. And yeah when i tried to upgrade from jedi to aosp, to tried using infamous cache and it didnt work :/ because i've heard that's what would fix it... and lastly, Im using twrp 6.1 i think, not the latest one.
Thanks alot for the reply!
PS. I see you running slimbean 4.2.2, how is it? any probs? maybe i can try a 4.2.2 if this doesn't work out, i havn't been able to get any 4.2.2 roms cause the links are all dead, so idk if i'll have problems with 4.2.2. if there's anyway you can link it for me that'll be great! thanks!
PSS: also i've tried odin, but idk if that actually wipes everything, i'm having a feeling that it might be a script problem or something because it goes into the rom once, but it just refused to work and after like 10 seconds it reboots.
quick question are you trying to restore 4.1/4.2 apps on your 4.3 ? apps dont play nice like that sometimes .. also your not restoring any system apps are you? Personally i love all the ROMs/Mods the devs put out for us but im one who likes it really stable with very few bugs so i like to stick with stable ROM's so thats why im still on 4.2.2 its nearly perfect no issues here brother . When you flash the rom what are your actual steps in detail please from the time you boot into recovery until you finish so i can get a better idea here
krazierokz said:
quick question are you trying to restore 4.1/4.2 apps on your 4.3 ? apps dont play nice like that sometimes .. also your not restoring any system apps are you? Personally i love all the ROMs/Mods the devs put out for us but im one who likes it really stable with very few bugs so i like to stick with stable ROM's so thats why im still on 4.2.2 its nearly perfect no issues here brother . When you flash the rom what are your actual steps in detail please from the time you boot into recovery until you finish so i can get a better idea here
Click to expand...
Click to collapse
Ey thanks for the reply, ok so first, I did not try to restore any apps or system apps, I even odin so everything were wiped cleaned. So really dont know whats going on. After I updated to a newer hellybean, not newest by now, and a beta uber kernel, this happens. I see two other people having the same problem too. Also I tried to use 4.2.2 roms, did not work
Anyways any insight would be apreciated!
Thanks!
One more thing, I tried twrp 2.6.1.0 to flash as reccomended by all devs and still no results. :/
Damn sorry brother that's pretty frustrating try dirty flashing helly bean and just wipe dalvik and cache and see if using the stock kernel helps first then see what happens :banghead:
sent from my t mobile S4
krazierokz said:
Damn sorry brother that's pretty frustrating try dirty flashing helly bean and just wipe dalvik and cache and see if using the stock kernel helps first then see what happens :banghead:
sent from my t mobile S4
Click to expand...
Click to collapse
oh well, thanks for the reply then, im trying 4.4, hopefully it'll help... somehow... lmao idk haha