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

Root [ROM] CyanogenMod 10 for the LG Motion 4G LGMS770 (l0)

When you go into CM wallpapers it crashes out if you don't do it fast enough. Lock screen shows backlight if not locked twice. (Might unbrick and go back to stock and re flash Cyanogen)

These are persistent issues so flashing back really wouldn't change much.. It is always a good idea to start from factory stock rooted and 100% battery when flashing a new rom though..
 
Upvote 0
Does Bob's build(s) have the same backlight issue??

From what I remember when I first tested this new build yes..
EDIT: I know on Bob's build I would get glimpses of the crt off and backlight stayed on. I don't know on yours whether or not I remember seeing crt off, but I do know it had the same issues with backlight for sure.
 
Upvote 0
From what I remember when I first tested this new build yes..
EDIT: I know on Bob's build I would get glimpses of the crt off and backlight stayed on. I don't know on yours whether or not I remember seeing crt off, but I do know it had the same issues with backlight for sure.

Hey Swainsmith, what are the correct permissions for cm10.tar in system/xbin?
 
Upvote 0
From what I remember when I first tested this new build yes..
EDIT: I know on Bob's build I would get glimpses of the crt off and backlight stayed on. I don't know on yours whether or not I remember seeing crt off, but I do know it had the same issues with backlight for sure.

I think CRT off messed with wake instead of the backlight. Do believe I have CRT disabled in the overlay.


OP/Wiki updated with new build 0809. ;)
 
Upvote 0
I think CRT off messed with wake instead of the backlight. Do believe I have CRT disabled in the overlay.


OP/Wiki updated with new build 0809. ;)


When it was an issue for me on Bob's the only time I would get the screen to stay off was to hit power til I got crt then the light would stay off. I'm pretty sure I don't think I saw crt on yours, but like I said I don't really remember. I tried to look into it back then but my son had ruined my computer and I couldn't edit much of anything in the framework from the phone..
 
Upvote 0
Hello all. Firstly I would like to thank PG, Hroark, bobz and the whole CM team. I've been using PG's last may release until yesterday as a daily FW and was thrilled to see that the GPS and low call volume issues had been resolved. While the call volume seems to have improved I am unable to get a fix on a single GPS sat. Furthermore 4g has never worked and I'm not sure why as it appears others have not had this issue. I have 2 of these phones, one on stock fw and one on PG's 8-4 cm10 and while the stock unit has no problem connecting to LTE in covered areas the cm unit will not. I've verified this through the network status as well as a speed test app as I am aware of the 1x/4G icon issue.

When I did the install I did the requisite factory reset as well as a cache, dalvik and data wipe. Does anybody have any thoughts on what may be causing the aGPS and LTE problems and a possible fix? I should also point out that EVDO/3G works and indicates properly in covered areas.

TIA,
sz

Edit: As a side note, and this may mean nothing at all, but when the stock phone is connected to 3G it indicates a network mode of "EvDo rev. A:8" whereas this version of cm indicates "EvDo rev. A:6"..... I'm not sure how much that matters or if it does at all but I just figures I'd point it out.

Edit #2: I just noticed a new build has been posted addressing low call volume. While I believed that had improved with my last flash I just made a call and it appears to have not so I will be giving that a try. Perhaps I didn't flash the ROM correctly last time and that is the cause of my current GPS/LTE problems? Does anybody have any suggestions on how to flash this? I was considering wiping everything again, including data.
 
Upvote 0
Hello all. Firstly I would like to thank PG, Hroark, bobz and the whole CM team. I've been using PG's last may release until yesterday as a daily FW and was thrilled to see that the GPS and low call volume issues had been resolved. While the call volume seems to have improved I am unable to get a fix on a single GPS sat. Furthermore 4g has never worked and I'm not sure why as it appears others have not had this issue. I have 2 of these phones, one on stock fw and one on PG's 8-4 cm10 and while the stock unit has no problem connecting to LTE in covered areas the cm unit will not. I've verified this through the network status as well as a speed test app as I am aware of the 1x/4G icon issue.

When I did the install I did the requisite factory reset as well as a cache, dalvik and data wipe. Does anybody have any thoughts on what may be causing the aGPS and LTE problems and a possible fix? I should also point out that EVDO/3G works and indicates properly in covered areas.

TIA,
sz

Edit: As a side note, and this may mean nothing at all, but when the stock phone is connected to 3G it indicates a network mode of "EvDo rev. A:8" whereas this version of cm indicates "EvDo rev. A:6"..... I'm not sure how much that matters or if it does at all but I just figures I'd point it out.

Edit #2: I just noticed a new build has been posted addressing low call volume. While I believed that had improved with my last flash I just made a call and it appears to have not so I will be giving that a try. Perhaps I didn't flash the ROM correctly last time and that is the cause of my current GPS/LTE problems? Does anybody have any suggestions on how to flash this? I was considering wiping everything again, including data.

Did you flash C modem? Helps with 4g although I'm not sure if it's already included in the build
 
Upvote 0
Another bug that I would like report that may or may not be being experienced by others has to do with the proximity sensor during calls. Since the last version from May as well as the 8-4 version, perhaps to a lesser extent though I've only been testing for less than 24hrs, the screen goes black when the phone is put up to ones ear as it should. However when removing the phone while still in a call to access the key pad or speakerphone the screen remains black and only after a number of presses of the lock button does it sometimes open back up without terminating the call. I hope thats helpful, if this is an isolated instance of this bug I'd be more than happy to provide more info.

s3cz0ne
 
Upvote 0
Another bug that I would like report that may or may not be being experienced by others has to do with the proximity sensor during calls. Since the last version from May as well as the 8-4 version, perhaps to a lesser extent though I've only been testing for less than 24hrs, the screen goes black when the phone is put up to ones ear as it should. However when removing the phone while still in a call to access the key pad or speakerphone the screen remains black and only after a number of presses of the lock button does it sometimes open back up without terminating the call. I hope thats helpful, if this is an isolated instance of this bug I'd be more than happy to provide more info.

s3cz0ne

I get that one also :p
 
Upvote 0
Did you flash C modem? Helps with 4g although I'm not sure if it's already included in the build

I know I should search and I will once I get home. Unfortunately I'm on 1X right now and replying from my phone. Do you know where I could get the &C" modem? Also what makes that different than others and how can I tell which modem FW I am currently using?

Thanks for the reply!

-s3cz0ne
 
Upvote 0
I know I should search and I will once I get home. Unfortunately I'm on 1X right now and replying from my phone. Do you know where I could get the &C" modem? Also what makes that different than others and how can I tell which modem FW I am currently using?

Thanks for the reply!

-s3cz0ne

Version C modem: http://www.sendspace.com/file/w0ps07
 
Upvote 0
I'll have to ask Bob what it was he edited in the cm10.tar. His commit just says vibration fix and its the tarball, which is the ramdisk 2nd-init uses. I'll try to see if I can catch him tomorrow some time. ;)
after: setprop vold.post_fs_data_done 1
add: write /sys/class/timed_output/vibrator/amp 70
in: init.grand.rc
The low call volume has something to do with

system/etc/snd_soc_msm

I do believe... I'm just not sure which after exactly. This is what bobz mentioned he updated when the volume was Increased on his newest build.
that's correct the two snd_soc_msm files control volume
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones