• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [MetroPCS] [ROM][4.4.4]CARBON ROM Kitkat 4.4.4 for LG Optimus F6 [LOTS OF FIXES]

Feel like an ass always botherin DM47021 but its on everyones mind and well just had to ask in winning to test whatever you have since my f6 is back up to my s5 which although a powerhouse is crippled by locked bootloader and well safe strap is not the same so let me ( us ) know
 
But, if you haven't bricked your fone at least once...

You haven't learned what NOT to do..

That's my train of thinking..... If you risk falling into a hole.. And never do.. You won't learn how to get out of it...

The crazy idea of it also takes away the fear of the risk... Because you'll be prepared.....

Or S.O.L. ...ooooohhhh... the adventure.... Without leaving the house......

Unless you completely brick it... Then you well be leaving the house to tell a story... Or get a new fone.. with more space..... More support...CM11 support.... Or 12 ......

Hmmmmm...... time to flash another wonky beta ROM!!!!!!
 
Need to test out some bluetooth and if anyone found out anything about the GPS I have reloaded and tested using GPS Status on a stock JB F6 and my rooted F6. I can pick up atleast 13 Satellites on the stock rom and only 1 maybe 2 unlockable satellites on this rom.
 
Time to warm up notepad++ and start hunting for values..... comparing stock with carbon .... sure bet the files have different names.....

and start fiddling with em .....

I don't use GPS that much ... but, maybe things are as easy as messing with the sitar file...... maybe...

With more hunting tho... I had direction.....

Or maybe I just got lucky with the sitar file.... I'm definitely not dev material....... But, never know if you don't try....
 
Well i have personally never messed with the files on the phone and i really dont even know what i would be looking for personally but i guess i can give it a shot what's the worst i can do learn what not to do. Oh darn never know what i couldpossibly learn and also find a fix possibly.
 
That's the spirit...... Just make sure you back up your important things..... if not a complete back up... I have a complete working back up of miniVOA in case I do damage that I can't recover from on the go ... purely on my part

But,I back up logs, contacts, and messages regularly..

And I'd you use something that has an auto back up scheduled.... If it backed up your installed apps...

there is a chance they'll be counted as being installed the next time you flash this ROM..... just throwing that out there..

Sounds fantastical and improbable... But, I've encountered this more than twice...

Just thoughts.... In no dev... common sense....
 
I wiped everything that twrp gave me access to wipe. Repartitioned SD card, Fashed ROM from first post, then kernal posted, then gapps and rebooted. Let sit 15 minutes then added account and let sit more. I then enabled both cores and upped min clock speed. Still having blsod, reboots, WiFi won't connect half the time, lots of echo in phone calls, and things that crash the app when clicked in settings and in camera. I found that everytime i reboot my wireless mac changes! This is a beautiful and exceptionally smooth ROM, and don't want to uninstall it despite the bugs. Any word on when the final will be released?
 
Last edited:
Don't forget to disable CRT transitions and all vibration... Just about all of it... Besides the enabling of the second core and raising the low ...I put mine at 500 something .... just to see what will start smoking... nothing yet thou.....

And the sitar and build files ... I use smanager to move em and fix the rw-r-r ... for me it's a "Swiss army gotta have" app..
 
Last edited:
You guys just need working system object files. Your lockup is caused by an endless illegal subroutine call. Which nests itself and quickly locks the system an ota update procedure call left in the code. That stumbles over itself repeatedy as the mobile data system object failure too on the ota check. I've contacted dm about a bug fix.

There are parts of the code trying to force an ota update that does not exist . within a matter of seconds you experience massive amounts of mobile data waste. It is a memory hole. and when you max out the process threads due to the illegal call your system halts. :)
 
As much as I liked the look and feel of this ROM, I just had to remove it. I actually went back to stock and will give this phone to my wife. I picked up a Moto X (1st gen) Developer Edition instead and plan to use that as my daily driver.

Just to note it for those considering this ROM, here are the main issues that I had with it that made me stop using it:

1. Bad echo on pretty much all phone calls. I couldn't hear it -- but the other end could and it was pretty bad. I tried several suggestions in this thread to correct it, but still had the problem.

2. Low call volume. Had it turned up all the way and still couldn't always hear the other end. Didn't have this problem at all with the stock ROM.

3. I was starting to get kernel crashes a couple of times a week. I would take it off the charger in the morning and drive to work (about 20 minutes). I'd get to work and pull it out of my pocket to discover that the kernel had crashed again. Reboot would take care of it, of course, but just annoying to find it crashed suddenly.

4. Trying to get around the space limitation I was using some tricks recommended here. They worked great -- except when the phone crashed, those changes would be lost. This isn't as much the fault of this ROM, of course, but the common kernel crashes made it more of an issue.

5. The screen doesn't shut off when talking on the phone (i.e. it doesn't detect when you have your face against it). This was annoying -- especially when driving and it was dark because the screen would stay lit. You could hit the button to turn it off -- but then annoying to turn it back on to hang up and such.

So, great ROM when it worked, but just too much of a hassle for a daily driver at this point.

- John...
 
jgoggan said:
As much as I liked the look and feel of this ROM, I just had to remove it. I actually went back to stock and will give this phone to my wife. I picked up a Moto X (1st gen) Developer Edition instead and plan to use that as my daily driver.

Just to note it for those considering this ROM, here are the main issues that I had with it that made me stop using it:

1. Bad echo on pretty much all phone calls. I couldn't hear it -- but the other end could and it was pretty bad. I tried several suggestions in this thread to correct it, but still had the problem.

2. Low call volume. Had it turned up all the way and still couldn't always hear the other end. Didn't have this problem at all with the stock ROM.

3. I was starting to get kernel crashes a couple of times a week. I would take it off the charger in the morning and drive to work (about 20 minutes). I'd get to work and pull it out of my pocket to discover that the kernel had crashed again. Reboot would take care of it, of course, but just annoying to find it crashed suddenly.

4. Trying to get around the space limitation I was using some tricks recommended here. They worked great -- except when the phone crashed, those changes would be lost. This isn't as much the fault of this ROM, of course, but the common kernel crashes made it more of an issue.

5. The screen doesn't shut off when talking on the phone (i.e. it doesn't detect when you have your face against it). This was annoying -- especially when driving and it was dark because the screen would stay lit. You could hit the button to turn it off -- but then annoying to turn it back on to hang up and such.

So, great ROM when it worked, but just too much of a hassle for a daily driver at this point.

- John...
Click to expand...
OK ....
 
Samsung Galaxy s3 or lg l9. ZTE avid and Samsung moment?

I been around got a lot more experience now though.
 
LoopyD said:
All software problems and can be fixed.
Click to expand...

Oh, absolutely -- but until they are fixed, this ROM isn't stable (for me, at least) as a daily driver. That's all I was saying.

Some people (like me) come looking for good daily driver ROMs so that they can just install them and forget it and just use their phone. This, in my opinion, is NOT the ROM to do that with at this point in time.

Has a lot of potential -- but just has some deal-breaker issues at the present time.

- John...
 
Oh yeah. That's why developers exist my friend. To work out those kinks. It's a lot of hard work... Hopefully I can get my laptop soon so I can clone my Ubuntu image to it... And start messing around. But dm has the source code... Ugh...
 
Agreed -- but I can't help but feel that this particular phone is a lost cause. It has an internal memory problem -- plain and simple. There is simply not enough internal space and trying to get it to use external space is a pain. Regardless of this ROM, there doesn't appear to be a good, stable way to solve the space problem even though many have tried. It's a flawed design, IMO.

For those sticking with the F6, I do hope that the developers can get them closer to a usable daily driver, of course. But, in the long run, it is a phone designed with a significant flaw that is not easily worked around. At some point, it just isn't worth it. There are other phones now in the same price range without that flaw -- so it makes little sense for anyone to continue buying the F6 unless they simply don't know any better (which is how I happened to get one).
 
You must log in or register to reply here.
Back
Top Bottom