Xt51
Android Enthusiast
I restored back to stock..but when i was on cm10 i wasnt having any problems with it. I have pro version and it worked just fine for me!
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root [ROM][WIP]CM10.0.0.l0-BobZ
- Thread starter BobZhome
- Start date
-
- Tags
- lg motion 4g
I restored back to stock..but when i was on cm10 i wasnt having any problems with it. I have pro version and it worked just fine for me!
plasticarmyman
Android Expert
Sigh I try to help..but I guess I can't force people to read or think
TheDemon
Android Enthusiast
Alright the only problems I noticed so far is that the brightness is not working as everyone else mentioned so I'm using root dim app as someone else mentioned. And low internal mic volume.
Other then those two I'm having no problems at all. Besides Facebook not being installed from the play store.
No random reboots, play store is not being glitchy, themes are working perfectly.
This is a pretty well done job for a work in progress. And I am very thankful.
Other then those two I'm having no problems at all. Besides Facebook not being installed from the play store.
No random reboots, play store is not being glitchy, themes are working perfectly.
This is a pretty well done job for a work in progress. And I am very thankful.
BlazingFire258
Well-Known Member
IMPORTANT!!!
I'm not sure if anyone else pointed this out before but if you switch network modes so that 3g works on CM10 and you restore back to stock 4g WON'T work. You'll be stuck on EV.
Solution: While in CM10 go to Network Mode setting select the middle option - LTE/CDMA/EvDO. Once you do that you can restore and 4g will be working again
.
If any of this info is a bit off correct me because I'm writing this off of memory but this should be solid.
I'm not sure if anyone else pointed this out before but if you switch network modes so that 3g works on CM10 and you restore back to stock 4g WON'T work. You'll be stuck on EV.
Solution: While in CM10 go to Network Mode setting select the middle option - LTE/CDMA/EvDO. Once you do that you can restore and 4g will be working again
.If any of this info is a bit off correct me because I'm writing this off of memory but this should be solid.
plasticarmyman
Android Expert
What baseband were you on before you flashed this? c, d, e, or f?
TheDemon
Android Enthusiast
I was using E.
Ubercharrge
Android Enthusiast
No, restore stock, go to dialer, type ##626*, enter spc, scroll down and change the CDMA/EVDO to LTE/EVDO/CDMA i think it is.IMPORTANT!!!
I'm not sure if anyone else pointed this out before but if you switch network modes so that 3g works on CM10 and you restore back to stock 4g WON'T work. You'll be stuck on EV.
Solution: While in CM10 go to Network Mode setting select the middle option - LTE/CDMA/EvDO. Once you do that you can restore and 4g will be working again
If any of this info is a bit off correct me because I'm writing this off of memory but this should be solid.
Also, i flashed it and it worked. i formatted system and did a factory reset before and it worked and flashed fine.
bart2201
Android Enthusiast
Each time I have tried to use the reboot recovery method it boots into morningcall error. Is anyone else experiencing this if so how can I get around it so I can finally try and restore one of the CWM back ups made with 2nd init recovery. I can go to clockwork mod and find the back ups but I can't recover any of them.
plasticarmyman
Android Expert
what baseband were you on when you flashed it over(c,d,e, or f)?...and did you restore those apps from a backup? or are they doing this after you installed them?...
(if you read the thread you'd see that you're not the only person with this problem)
We need more information so we can narrow down what the cause of this problem could be...
Zephyr101
Android Enthusiast
Yeah, I did read the thread. But noticed that person didn't get much help. Haha so I made another post. Whoops :]
But anyways. I flashed it over version F. And they started doing this once they were installed. Straight from the Play Store. I didn't do anything with backups. Other than back up my Stock Collab Rom in case something went wrong.
k0r
Well-Known Member
I think you should follow the unbrick guide to return to stock and try it all again
If you guys / gals are doing any build.prop tweaks, using any start-up optimization scripts, running any task killing apps, or doing anything that is "non standard" that changes the way the OS works, you really should not post your issues in this thread.
Ideally we should find and fix problems with just the ROM installed, then find and fix issues with the ROM and GAPPS installed, and then after that find and fix issue with ROM, GAPPS, and normal apps installed that do not change the way the OS works
These problems I am seeing may be caused by the version of GAPPS we are using, or any number of other things
Ideally we should find and fix problems with just the ROM installed, then find and fix issues with the ROM and GAPPS installed, and then after that find and fix issue with ROM, GAPPS, and normal apps installed that do not change the way the OS works
These problems I am seeing may be caused by the version of GAPPS we are using, or any number of other things
Firmware F
Mods: none
Issues: Music won't stream over stereo bluetooth headphones, although the phone works fine.
Logcat:
Motion cm10 Bluetooth audio log - Pastebin.com
Mods: none
Issues: Music won't stream over stereo bluetooth headphones, although the phone works fine.
Logcat:
Motion cm10 Bluetooth audio log - Pastebin.com
Shabbypenguin
Extreme Android User
plasticarmyman ill go ahead and post a bug report like you want to better help development for the devs here.
Baseband: MB2
Mods: None
Issues: Rom refuses to boot on my SGS3, hopefully we can figure out why.
here is a link to my logcat
Baseband: MB2
Mods: None
Issues: Rom refuses to boot on my SGS3, hopefully we can figure out why.
here is a link to my logcat
i am only kidding but hopefully it gets people to see how they should be posting bugs/issues so that they can be better addressed.
IMPORTANT!!!
I'm not sure if anyone else pointed this out before but if you switch network modes so that 3g works on CM10 and you restore back to stock 4g WON'T work. You'll be stuck on EV.
Solution: While in CM10 go to Network Mode setting select the middle option - LTE/CDMA/EvDO. Once you do that you can restore and 4g will be working again
If any of this info is a bit off correct me because I'm writing this off of memory but this should be solid.
This happend to me i forgot to switch it bk but i got bk 4g by aceesing.hidden menu and chamging.it. Back while on stock
plasticarmyman
Android Expert
Shabby......Lol....maybe try it on a Motion and not the SGS3...we can trade if you'd like...I'll even pay the shipping for you
plasticarmyman
Android Expert
Okay....well..what I personally would like to see is people unbrick to version e, Reroot and install recovery apk and then flash this using the instructions in the first post...please do not use any build prop mods or any apps that 'fix' anything..
Let me know of any issues You have after doing that, using the bug report format
(Disclaimer : I'm not a dev at all...but I'm trying..really hard...to help out BobZ by streamlining the bug report process...if everyone tries to keep to the format...any format not just mine...but some sort of simple format.. then we will have a stable release a whole hell of a lot faster...it's a tried and true method that works real well)
Let me know of any issues You have after doing that, using the bug report format
(Disclaimer : I'm not a dev at all...but I'm trying..really hard...to help out BobZ by streamlining the bug report process...if everyone tries to keep to the format...any format not just mine...but some sort of simple format.. then we will have a stable release a whole hell of a lot faster...it's a tried and true method that works real well)
johnnyolivares
Android Enthusiast
Ondemand
c00lfrij0les
Lurker
Hello,
First off thanks to bob for this wonderful rom.
I had done a software update for no reason and ended up with the morning call problem. So I looked for the unbrick guide and I found this post so I decided to give it a try. I did a fresh install and used baseband C.
Now as far as what's wrong:
Like people are mentioning above for some reason this rom hates facebook. at first at got error 492 in the play store and then it would start installing and then rebooting.
I have random reboots when typing certain thing or using the play store.
sometimes while typing the keyboard freezes.
I do not think gps is working even though you are able to toggle it in the notification bar, Navigations can never locate you and the gps icon does not show up on the status bar.
Voice calling is extremely low.
brightness does not work.
I'm trying to pull a logcat, but I am having a hard time getting them on here.
Posted some screens to show how the GPS icon is turned on and then it doesn't show up on the status bar
Again thx bobz for your work!!!
First off thanks to bob for this wonderful rom.
I had done a software update for no reason and ended up with the morning call problem. So I looked for the unbrick guide and I found this post so I decided to give it a try. I did a fresh install and used baseband C.
Now as far as what's wrong:
Like people are mentioning above for some reason this rom hates facebook. at first at got error 492 in the play store and then it would start installing and then rebooting.
I have random reboots when typing certain thing or using the play store.
sometimes while typing the keyboard freezes.
I do not think gps is working even though you are able to toggle it in the notification bar, Navigations can never locate you and the gps icon does not show up on the status bar.
Voice calling is extremely low.
brightness does not work.
I'm trying to pull a logcat, but I am having a hard time getting them on here.
Posted some screens to show how the GPS icon is turned on and then it doesn't show up on the status bar
Again thx bobz for your work!!!
BobZhome
Android Enthusiast
This is how I plan on fixing things...problems with ROM only are top priority.
That being said, I was look at the 4G issue and discovered that cm10.1(Android 4.2.2) had a lot more code for ICCID than CM10(4.1.2). I tried back-porting some of it, but got some errors...so, I decide that I'm going to move up to cm10.1 and hopefully it will help that issue.
Your using 3rd party apps...please try with stock apps, Thanks!
Great example
Thanks so much for the help...my time is very limited, so any help is appreciated.
I have no issues with GPS, calls being low, or random reboots...with my current ROM with no Gapps and 3rd party apps installed manually.Hello,
First off thanks to bob for this wonderful rom.
I had done a software update for no reason and ended up with the morning call problem. So I looked for the unbrick guide and I found this post so I decided to give it a try. I did a fresh install and used baseband C.
Now as far as what's wrong:
Like people are mentioning above for some reason this rom hates facebook. at first at got error 492 in the play store and then it would start installing and then rebooting.
I have random reboots when typing certain thing or using the play store.
sometimes while typing the keyboard freezes.
I do not think gps is working even though you are able to toggle it in the notification bar, Navigations can never locate you and the gps icon does not show up on the status bar.
Voice calling is extremely low.
brightness does not work.
I'm trying to pull a logcat, but I am having a hard time getting them on here.
Posted some screens to show how the GPS icon is turned on and then it doesn't show up on the status bar
Again thx bobz for your work!!!
For test purposes, I have install the new Play Store and can confirm that Facebook can't be installed
I know for a lot of people that's there life...an alternative is to use your phone's browser 
k0r
Well-Known Member
well whatever gapps could I try ? I see 20121011 which is the one we're not now and for our version 4.1.x , I would of thought try any other ones wouldn't help if it's not for our version
This is how I plan on fixing things...problems with ROM only are top priority.
That being said, I was look at the 4G issue and discovered that cm10.1(Android 4.2.2) had a lot more code for ICCID than CM10(4.1.2). I tried back-porting some of it, but got some errors...so, I decide that I'm going to move up to cm10.1 and hopefully it will help that issue.
Your using 3rd party apps...please try with stock apps, Thanks!
Great example
Thanks so much for the help...my time is very limited, so any help is appreciated.
I have no issues with GPS, calls being low, or random reboots...with my current ROM with no Gapps and 3rd party apps installed manually.
For test purposes, I have install the new Play Store and can confirm that Facebook can't be installed
I think by gps he means the actual location isn't working, like if you go to navigation and enter a random address it will just hang on "searching for gps"
& the call volume does seem a bit lower then normal. I remember this was also an issue in the beta of the other CM build.
Someone other then me should try to install something from the market that I claim is making my phone reboot like the aurora theme for cm9/cm10 , that's just an example so I can know if it's just me or not that is experiencing these reboots when installing certain apps
I just want to clarify that I am not trying to tell BobZ or anyone else how to fix things, or what should be done with the ROM or thread, I was just trying to help.
I always found it annoying when I would release a ROM, and people would start to report problems, and then it turned out they were changing the build prop, or running kernel tweaking scripts, I was just trying to spare Bob that headache, but I gave my opinion, and I will leave it at that.
As far as GAPPS, the link in the OP is the proper version of GAPPS to be used on this ROM, but I would imagine once it is installed and you go into the Playstore, there are updates for a lot of the apps that GAPPS installs
So, if there is a problem with Playstore for example, did it exist before the update, after the update, etc. etc.
I just think if you are reporting a problem with GAPPS it should be known whether it was updated or not