Database Info

LG Phoenix - Distorted Colors

Hello everyone,
Ive seem to run into some trouble, that I cant find a solution too.
I rooted my phone with Gingerbreak V1.20, and flash my recovery with CWM.
I proceeded to add the Nightly Four E rom, than the trouble began.
My colors on the phone display are diffused and distorted, mainly showing the color green and blue.
I read thatI need to flash the stock 2.2 rom again and it would fix it but it didnt.
Can someone help me with this, its quite annoying.

Trytohaxme said:
Hello everyone,
Ive seem to run into some trouble, that I cant find a solution too.
I rooted my phone with Gingerbreak V1.20, and flash my recovery with CWM.
I proceeded to add the Nightly Four E rom, than the trouble began.
My colors on the phone display are diffused and distorted, mainly showing the color green and blue.
I read thatI need to flash the stock 2.2 rom again and it would fix it but it didnt.
Can someone help me with this, its quite annoying.
Click to expand...
Click to collapse
It's a kernel issue. From what you've stated, stock 2.2, your device never got it's official 2.3 update. So, you have an old baseband P505. You should be able to flash ROMs made specificially for the P505 as well as P500 ROMs. Since your device is old baseband, you also have the option to flash P509 ROMs. P509 never got an official GB update so it's always an old baseband device, same with the P506. The catch with P500 ROMs and most P505 ROMs is they are build for new baseband so an additional patch, old baseband, will need to be applied after flashing the ROM. P506 devices use a different touchscreen than the others so you'll have issues installing one of those ROMs.
The old baseband patch is to get your radio, cell signal, working with new baseband ROMs. I hope this wasn't information overload If you used ROM Manager, it's possible that is screwed up the radio too. ROM Manager is not friendly to the Optimus One device family. Android Flash Recovery, link in my signature, is designed for flashing recoveries via fastboot and fastboot mode. You may, especially if color banding is an issue with your recovery, want to reflash your recovery too.
Oh, and have you seen the LG Optimus One FAQ?

I appreciate the reply you've giving, but this is my first time using the Optimus One.
You stated its a kernel issue, how would I go upon fixing a kernel issue?
You also stated I should reflash the recovery, is there a specific recovery I should be using?

Trytohaxme said:
I appreciate the reply you've giving, but this is my first time using the Optimus One.
You stated its a kernel issue, how would I go upon fixing a kernel issue?
You also stated I should reflash the recovery, is there a specific recovery I should be using?
Click to expand...
Click to collapse
For the kernel issue, you can search the forums here to find some that are compatible with your device. The kernel you need will depend on the version of Android you are wanting to install since there isn't a universal kernel for all Android versions. Most of the newer kernels are for ICS( Android 4.0 ) and JB( Android 4.1, 4.2 ). I've never used it but they say Franco has a kernel for GB ( Android 2.3 ). SweetnSour has a kernel for JB and the AndroidArmv6 Team has a new 3.0 kernel for JB.
If you like GB, then you may want to look at this CM7.2 ROM( Direct download ). It is for a P500, so you will need the old baseband patch from post #9 in the LG Optimus One FAQ. I''m using that ROM on my P509 ATM.
As for the recovery, I only suggest reflashing it if you are experiencing color issues with it too. I use CWM 5.0.2.7 Touch, but it will only allow P500 ROMs to be flashed. It's no big deal for me, but for someone new to the game it can be troublesome. CWM 5.0.2.0 is also a good recovery. I don't recommend using ROM Manager to flash anything. If you should decide to reflash your recovery, I would recommend using Android Flash Recovery for Windows( in my signature ) or FlashImage GUI which can be found in the Play Store.

It seems no matter what I do, the color will not correct.
I've tried switching roms, flashing a new kernel and recovery nothing seems to be working..

Trytohaxme said:
It seems no matter what I do, the color will not correct.
I've tried switching roms, flashing a new kernel and recovery nothing seems to be working..
Click to expand...
Click to collapse
Do you still have a backup of your stock ROM? I mean a backup that was made while in recovery mode. If you do you can try booting in to recovery and then try wiping and formatting everything but your sdcard. Then restore the backup you made and reboot the device. Other than that, I hate to say it, but I'm at a loss.

I just flashed the CM 7.2 ROM, and franco.Kernel | 2.6.35.10.
I just about did everything, but the color remains distorted once the actual ROM boots up.
Note* If the phone is off and I power it on, the first LG logo has perfect color and clarity but once the ROM kicks in the colors wacks out.
Edit - The phone no longer allows me to access CWM it's just a black screen.

Trytohaxme said:
I just flashed the CM 7.2 ROM, and franco.Kernel | 2.6.35.10.
I just about did everything, but the color remains distorted once the actual ROM boots up.
Note* If the phone is off and I power it on, the first LG logo has perfect color and clarity but once the ROM kicks in the colors wacks out.
Click to expand...
Click to collapse
The kernel is part of the boot image. It's possible that somehow your partitions have been damaged.
---------- Post added at 06:30 PM ---------- Previous post was at 06:27 PM ----------
Trytohaxme said:
I just flashed the CM 7.2 ROM, and franco.Kernel | 2.6.35.10.
I just about did everything, but the color remains distorted once the actual ROM boots up.
Note* If the phone is off and I power it on, the first LG logo has perfect color and clarity but once the ROM kicks in the colors wacks out.
Edit - The phone no longer allows me to access CWM it's just a black screen.
Click to expand...
Click to collapse
Hmm. I'm about convinced there's something wrong with your partition tables. Your data is getting corrupted.

So basically I just ruined the phone?

Trytohaxme said:
So basically I just ruined the phone?
Click to expand...
Click to collapse
Yes and no. If you can find or get a hold of the partition.mbn for your device you can use LGMDP to repair the partitions. The P500 one might work too, I'm not sure tho.
EDIT:
You can also install a recovery and ROM in the same process with LGMDP

shinobisoft said:
Yes and no. If you can find or get a hold of the partition.mbn for your device you can use LGMDP to repair the partitions. The P500 one might work too, I'm not sure tho.
EDIT:
You can also install a recovery and ROM in the same process with LGMDP
Click to expand...
Click to collapse
Yeah, I'm screwed I have no idea how to do that so I'm just gonna have to buy a new phone.. :crying:

Im sorry didn't read too well, bad luck, i didn't read your posts before, i knew how to fix the blue colors on your screen

gabo_lope said:
Im sorry didn't read too well, bad luck i didn't read your posts before i knew how to fix the blue colors on your screen
Click to expand...
Click to collapse
Well how exactly do you fix the screen color than?

Trytohaxme said:
Well how exactly do you fix the screen color than?
Click to expand...
Click to collapse
you only had to flash this on your p505 after the rom https://code.google.com/p/sweetnsour-kernel/downloads/list; one of these
kernel-20130224_1312.zip version4-CFS-P505-P506 for battery life
kernel-20130224_1306.zip version4-BFS-P505-P506 for performance

You have saved my phone my good sir, and I thank you greatly!
Now that I have the correct kernel, can I install different roms now?

Yes, but only ics and jellybean roms , if you use the kernel on gingerbread you will get a lot of troubles...

I just flashed the unofficial CM 10.1, and booted the phone and the color was diffused again.
So I flashed the kernel again and booted the phone, and everything is working perfectly.
Thank you so much!
P.S - CM 10.1 doesn't come with Google Apps or Rom manager, how do I get that back?

To get the google apps you will need to flash a gapps.zip, but first you need to trim the cm 10.1 rom, because
The recommended gapps package is not quite small enough to fit along with the rom in our limited /system partition. The size of the rom can be trimmed by deleting or converting some system apps to user apps, deleting unwanted ringtones and fonts.
Click to expand...
Click to collapse
Also
Take off anything that can be installed from Play, same for gapps.zip!!
Click to expand...
Click to collapse
There is a tool designed for that, is in shinobisoft's signature, oone rom editor, download that tool and in the help docs you will find information about trimming, and what can be removed safely... Here it is http://forum.xda-developers.com/showthread.php?t=1959023
If this the first time you are installing roms, i will recommmend you to stay in ice cream sandwich, because is more stable, and it has a lot better battery life than jellybean...

[Q] Anyone succeed with GPS with custom rom

Hi all,
Did anyone able to use gps with custom rom ( I would say CM base). I research and try everything that's I could find here but not success.
Every time I do clean wipe everything including a internal storage. So that will nothing left behind.
I know that stock is work fine with gps. some said that install and replace stock but I have no idea that what file will left in our device when we delete all.

Always had the same problem when running Paranoid Android (not tried other ROMs). Had to return to stock, where GPS runs fine. Would also love to kknow how people have got it functioning.

I am trying too. I modified gps.conf files, tried some workarounds mentioned in cm11 thread like restoring GPS Status backup from stock with titanium so far with no success. Some people say that it works but it doesn't on mine whatever I do.

I run on CM and I don't have any problem. Everything works fine with gps and I didn't use any fix or something similar.
I'm on CM 11-20140627 and I have 1032 phone.

Interesting, why does it work on some while it doesn't on others? Maybe some variants are having problems...
I have xt1033 asia version.

spajdo said:
I run on CM and I don't have any problem. Everything works fine with gps and I didn't use any fix or something similar.
I'm on CM 11-20140627 and I have 1032 phone.
Click to expand...
Click to collapse
Which recovery did you use?

CWM

As I wonder is about library missing or some partition need from stock ?

I've also been using the micro gapps package, would this matter?

I had problems with Paranoid Android and GPS too... If anyone know something about that, please comment!

TMaxtor said:
I had problems with Paranoid Android and GPS too... If anyone know something about that, please comment!
Click to expand...
Click to collapse
Hey i found a solution, you have do this flash following in this order.
- flash stock 4.4.4 (depend on your current)
- flash cm
- flash gapp
I try this twice and work like a charm.
Sent from my Moto G using XDA Free mobile app

thestory101 said:
Hey i found a solution, you have do this flash following in this order.
- flash stock 4.4.4 (depend on your current)
- flash cm
- flash gapp
I try this twice and work like a charm.
Sent from my Moto G using XDA Free mobile app
Click to expand...
Click to collapse
I am having he same problem on XT1032 running Carbon ROM. GPS worked fine on stock, no signal with Carbon.
I found many answers saying to flash stock and then reflash custom ROM. I will try it, but I wonder, how does this help? Isn't the phone restoring the whole system? Do I have to keep the gps.conf from stock?

I've read in some CM thread on here you need to flash stock ROM then enable GPS and get a lock. Once you've done that then flash your custom rom. Sounds STUPID and dosent make sense I know, but a lot of people say this is how they got it to work.
EDIT: I can confirm. I've just flashed stock 4.4.4 and played around with google maps. Flashed CM11 nightly and my GPS is now working ok

am05 said:
I've read in some CM thread on here you need to flash stock ROM then enable GPS and get a lock. Once you've done that then flash your custom rom. Sounds STUPID and dosent make sense I know, but a lot of people say this is how they got it to work.
EDIT: I can confirm. I've just flashed stock 4.4.4 and played around with google maps. Flashed CM11 nightly and my GPS is now working ok
Click to expand...
Click to collapse
Did you wipe anything, like Dalvik, Cache and Data, or you just flashed it over?

am05 said:
I've read in some CM thread on here you need to flash stock ROM then enable GPS and get a lock. Once you've done that then flash your custom rom. Sounds STUPID and dosent make sense I know, but a lot of people say this is how they got it to work.
EDIT: I can confirm. I've just flashed stock 4.4.4 and played around with google maps. Flashed CM11 nightly and my GPS is now working ok
Click to expand...
Click to collapse
Sorry people, I was so happy to have my phone back working, I forgot to write it back here.
Yes it worked indeed, all I did was flashing back the stock, going outside to have a gps lock with gmaps, then re-flashing back the Carbon. I also kept a copy of the gps.conf, but I never needed it, the GPS got a fix quickly. Working fine so far, it only takes some tens of seconds to fix, from time to time.
I can't remember if I also did all the wiping, I think I didn't, but I made so many trials in a couple days, I am not sure.
Thanks a lot guys!

am05 said:
I've read in some CM thread on here you need to flash stock ROM then enable GPS and get a lock. Once you've done that then flash your custom rom. Sounds STUPID and dosent make sense I know, but a lot of people say this is how they got it to work.
EDIT: I can confirm. I've just flashed stock 4.4.4 and played around with google maps. Flashed CM11 nightly and my GPS is now working ok
Click to expand...
Click to collapse
Yes, this worked for me too on PA.
I couldn't even see a single sat (it wasn't just a lock problem). No matter with gps patch, gpx fix app, or gps.conf I used.
What I did?: Back to stock, lock GPS, flash again the custom ROM (but don't wipe /system!).
Good luck on that guys, it should work for you too.

thestory101 said:
Hi all,
Did anyone able to use gps with custom rom ( I would say CM base). I research and try everything that's I could find here but not success.
Every time I do clean wipe everything including a internal storage. So that will nothing left behind.
I know that stock is work fine with gps. some said that install and replace stock but I have no idea that what file will left in our device when we delete all.
Click to expand...
Click to collapse
GPS works fine on this unofficial CM11 rom for me. Stable daily driver rom for me, YMMV.
General advice is to:
- make sure you get a GPS lock on stock rom first
- flash CM11 (or other custom rom)
There may not be a file left on the device. it may just be that stock contains the code to initialize the GPS functionality on the SoC or chipset firmware. Whatever, it works...

CWM - Screen Flickering (Optimus 3D)

Hi,
after flashing various ROMS over the last months, entering ClockWork Mod today to flash GAPPS, I realized that the lower part of the screen is flickering.
(only in clockwork mod)
I coudlnt find much about this. Is there a fix ? Whats causign it ?

itsmemario said:
Hi,
after flashing various ROMS over the last months, entering ClockWork Mod today to flash GAPPS, I realized that the lower part of the screen is flickering.
(only in clockwork mod)
I coudlnt find much about this. Is there a fix ? Whats causign it ?
Click to expand...
Click to collapse
Try stock ROM, if it stops then it's a ROM related issue if not then check your cables/screen

TechMinerUK said:
Try stock ROM, if it stops then it's a ROM related issue if not then check your cables/screen
Click to expand...
Click to collapse
I entered CWM again to flash another ROM and this time screen was not flickering.
Then I wanted to flash the Google "L" keyboard and the whole screen was flickering this time.
Never ever happened on this ROM before.
Good to know it can be ROM related, but how can the ROM influence ClockWork Mod ? Sorry, me noob.
I googled it and others seem to have it too. But why doesnt it flicker in "Phone mode" ? What is this all about :S
Im not in the mood to open my device now. I hope it wont die. :S

[Q] Phone Randomly Reboots Itself?!

So after doing a wipe to my phone (was becoming slow) my phone randomly restarts itself for no reason as if it just crashes. I am running the latest version of the beanstalk rom. http://forum.xda-developers.com/showthread.php?t=2091900 I don't have the greatest understanding of flashing, roms, blah blah blah, but managed to get kit kat working for the last year or so, I don't understand why this is happening now, did I choose a bad rom or something? Everything else on the phone works but obviously constant restarts get to be very annoying.
Any help would be appreciated,
thank you!

Infused4life said:
So after doing a wipe to my phone (was becoming slow) my phone randomly restarts itself for no reason as if it just crashes. I am running the latest version of the beanstalk rom. http://forum.xda-developers.com/showthread.php?t=2091900 I don't have the greatest understanding of flashing, roms, blah blah blah, but managed to get kit kat working for the last year or so, I don't understand why this is happening now, did I choose a bad rom or something? Everything else on the phone works but obviously constant restarts get to be very annoying.
Any help would be appreciated,
thank you!
Click to expand...
Click to collapse
Try leaving it turned on in recovery mode (CWM). If it still reboots, then you have a hardware issue. If it stays stable, I would blame the ROM and try a different version or a different distro.
Sent from my MyTouch 4G Slide

joel.maxuel said:
Try leaving it turned on in recovery mode (CWM). If it still reboots, then you have a hardware issue. If it stays stable, I would blame the ROM and try a different version or a different distro.
Sent from my MyTouch 4G Slide
Click to expand...
Click to collapse
Thanks for the reply,
I don't think it is a hardware issue as it never did this when I had Jelly Bean or even the last time I had Kit Kat, never know though! Also, I will try to leave it in recovery and see if it does it but a few questions:
-What is "distro" (does it has to do with the OS of the phone?)
-Is there some ROM you could recommend to me for this phone that is stable.. When I install the beanstalk ROM there are like 10 to choose from, I'm guessing they are all older/newer versions!?
-Finally something I was wondering for the longest time but wasn't sure of is can I go back to say, Jelly Bean? Or is it "irreversible"?
Thanks again, glad there's people out there who can help the noobs like me!

Infused4life said:
Thanks for the reply,
I don't think it is a hardware issue as it never did this when I had Jelly Bean or even the last time I had Kit Kat, never know though! Also, I will try to leave it in recovery and see if it does it but a few questions:
-What is "distro" (does it has to do with the OS of the phone?)
-Is there some ROM you could recommend to me for this phone that is stable.. When I install the beanstalk ROM there are like 10 to choose from, I'm guessing they are all older/newer versions!?
-Finally something I was wondering for the longest time but wasn't sure of is can I go back to say, Jelly Bean? Or is it "irreversible"?
Thanks again, glad there's people out there who can help the noobs like me!
Click to expand...
Click to collapse
Methinks it is the specific ROM. I call the different types of OM out there distributions (or "distros" - in light of what is commonly used in the Linux world), but there may be a better term. It could be the version of Beanstalk you are using, it could be any version of BeanStalk with your phone. Hard to say.
In light of above, I would try CarbonROM. I tried it out briefly, and haven;t had a problem with it (and have heard no issues form the guy I sold the phone to with it installed).
But if you want to go back to JellyBean, there is still a version of 4.2 kicking around (CM 10.1) in the development threads. You can downgrade, at worst you may have to ODIN back to stock. But try to flash in CWM first. I was quite satisfied with that version. My biggest gripe is that the mobile data quick setting didn't work fully (but the long way around did). There is CM 10.2 as well, but I could never get that one installed on my phone (installer would break). Between the two, I would try 10.1 (and if you cannot find a copy, I can dropbox it to you).

5529
joel.maxuel said:
Methinks it is the specific ROM. I call the different types of OM out there distributions (or "distros" - in light of what is commonly used in the Linux world), but there may be a better term. It could be the version of Beanstalk you are using, it could be any version of BeanStalk with your phone. Hard to say.
In light of above, I would try CarbonROM. I tried it out briefly, and haven;t had a problem with it (and have heard no issues form the guy I sold the phone to with it installed).
But if you want to go back to JellyBean, there is still a version of 4.2 kicking around (CM 10.1) in the development threads. You can downgrade, at worst you may have to ODIN back to stock. But try to flash in CWM first. I was quite satisfied with that version. My biggest gripe is that the mobile data quick setting didn't work fully (but the long way around did). There is CM 10.2 as well, but I could never get that one installed on my phone (installer would break). Between the two, I would try 10.1 (and if you cannot find a copy, I can dropbox it to you).
Click to expand...
Click to collapse
YES!
So, after I left the phone in CWM for 25 minutes or so and it being fine I decided to get Carbon as I seen in your "signature" that you had that ROM on your Infuse, it has been good for 2 hours+, looking good! I guess it was the Beanstalk ROM after all.
Thanks for the downgrading information as well, wasn't sure if you could downgrade or what would happen!
Finally, what is flashing? (I could google it but since your here, could you give me a noob friendly definition!?)
Thanks for all your help

Infused4life said:
YES!
So, after I left the phone in CWM for 25 minutes or so and it being fine I decided to get Carbon as I seen in your "signature" that you had that ROM on your Infuse, it has been good for 2 hours+, looking good! I guess it was the Beanstalk ROM after all.
Thanks for the downgrading information as well, wasn't sure if you could downgrade or what would happen!
Finally, what is flashing? (I could google it but since your here, could you give me a noob friendly definition!?)
Thanks for all your help
Click to expand...
Click to collapse
Went to reply about the camera issue and notice it was no longer in the post. Glad you got it sorted.
So flashing, as I understand it, is just another term for installing something via recovery. Not sure of the origin, maybe have something to do with installing to flash memory.

joel.maxuel said:
Went to reply about the camera issue and notice it was no longer in the post. Glad you got it sorted.
So flashing, as I understand it, is just another term for installing something via recovery. Not sure of the origin, maybe have something to do with installing to flash memory.
Click to expand...
Click to collapse
Ah ok, so it's essentially as I thought it was. I thought I was doing something wrong in terms of "flashing" but guess not! Sounds like it should just be called "Installing custom ROM".. !
Yeah, in terms of the camera thing, I'm an idiot and had USB storage turned on *facepalm*, So it wouldn't let me open the camera app!

Infused4life said:
Ah ok, so it's essentially as I thought it was. I thought I was doing something wrong in terms of "flashing" but guess not! Sounds like it should just be called "Installing custom ROM".. !
Yeah, in terms of the camera thing, I'm an idiot and had USB storage turned on *facepalm*, So it wouldn't let me open the camera app!
Click to expand...
Click to collapse
I am not sure if you are still facing the same issue but if you are facing reboots, then considering doing a fresh install after cleaning your internal storage as well since the remnants of the apps from previous installs have caused me problems. Ever since I started doing a fresh install (Factory reset, wiping the cache, wiping the dalvik cache and even the cache partition along with the wiping of the internal storage), there have been no reboot issues.

Music issue...

Hey guys, I can't seem to get this figured out, so I have resorted to coming to the forum for help. On every single ROM I have ran lately EXCEPT the old LiquidSmooth 4.4.4(most recent version), I have had issues playing music through AUX. WHenever I would plug in my aux cable, play a song, then turn off my screen, the music would start lagging and there would be lots of static. but if I waked the device it would be fine. Turn the screen back off, same thing. It started happening after flashing this GPE ROM found here http://forum.xda-developers.com/htc-one-m8/development/rom-m8-gpe-01232015-t3010825
Now it does it on Viper, any GPE or AOSP other than LiquidSmooth 4.4.4. I flashed Fluent ROM in the Verizon Dev thread last night and same thing. It will also do it on all versions of Viper(4.4.4 and 5.0.1). Is anyone else experiencing this? BTW I have not tested Bluetooth, so I don't know if it does it there too. I have tested the actual speakers on the phone, and it does not do it there, just on aux. kinda making me think it may be my cable, but I'm just looking to see if anyone else is having these issues.
Thanks in advance guys!

blkhrt13 said:
Hey guys, I can't seem to get this figured out, so I have resorted to coming to the forum for help. On every single ROM I have ran lately EXCEPT the old LiquidSmooth 4.4.4(most recent version), I have had issues playing music through AUX. WHenever I would plug in my aux cable, play a song, then turn off my screen, the music would start lagging and there would be lots of static. but if I waked the device it would be fine. Turn the screen back off, same thing. It started happening after flashing this GPE ROM found here http://forum.xda-developers.com/htc-one-m8/development/rom-m8-gpe-01232015-t3010825
Now it does it on Viper, any GPE or AOSP other than LiquidSmooth 4.4.4. I flashed Fluent ROM in the Verizon Dev thread last night and same thing. It will also do it on all versions of Viper(4.4.4 and 5.0.1). Is anyone else experiencing this? BTW I have not tested Bluetooth, so I don't know if it does it there too. I have tested the actual speakers on the phone, and it does not do it there, just on aux. kinda making me think it may be my cable, but I'm just looking to see if anyone else is having these issues.
Thanks in advance guys!
Click to expand...
Click to collapse
Did you flash any audio mods or new firmware?

loonatik78 said:
Did you flash any audio mods or new firmware?
Click to expand...
Click to collapse
I have not flashed either. However, as we speak, I am updating my firmware to the new 5.0.1 firmware found here...http://forum.xda-developers.com/showthread.php?t=2723159...and I downloaded the version for TWRP users, and I have the latest TWRP 2.8.5.0 installed. So maybe that will make a difference?

blkhrt13 said:
I have not flashed either. However, as we speak, I am updating my firmware to the new 5.0.1 firmware found here...http://forum.xda-developers.com/showthread.php?t=2723159...and I downloaded the version for TWRP users, and I have the latest TWRP 2.8.5.0 installed. So maybe that will make a difference?
Click to expand...
Click to collapse
Possibly, but I doubt it. There's something telling the kernel to sleep which is why it happens when you turn your screen off. I'd try wiping /system before flashing a ROM. There might be something from liquid being left behind. Factory resets don't wipe /system. If you're ROM requires an intact /system such as Adrenaline, flash a stock rooted ROM first, then the custom ROM. That's what I'd try. Someone else might have a better idea.

loonatik78 said:
Possibly, but I doubt it. There's something telling the kernel to sleep which is why it happens when you turn your screen off. I'd try wiping /system before flashing a ROM. There might be something from liquid being left behind. Factory resets don't wipe /system. If you're ROM requires an intact /system such as Adrenaline, flash a stock rooted ROM first, then the custom ROM. That's what I'd try. Someone else might have a better idea.
Click to expand...
Click to collapse
Actually every single time I flash a new rom, I go into advanced wipe and wipe system, data, cache and dalvik cache 3 times. Every Time. But I flagged that new firmware and was rubbing digital high rom from the Verizon thread and did not have the music issue. I'm running fluent rom sense 7 from the Verizon thread now but have not tested the music yet But will update you guys in the morning. Thanks for all your replies