CM 10.2 for Canadian Optimus G (E973/E971)
- Thread starter chadouming
- Start date
-
- Tags
- development
I don't know guys if it is just me. But when I use my phone I get a huge battery drain .but if I leave it in stand by. It doesn't drain as much. Why is that?
Sent from my LG-E973 using xda app-developers app
Sent from my LG-E973 using xda app-developers app
Haha. Well I'm sorry. What I mean is that if I use my phone just to read stuff for at least 40 mins. I would have lost 15 to 20 percent of battery. Which didn't happen at all in my note 2. Sorry if I'm might ignore something but I'm asking so I can learn
Sent from my LG-E973 using xda app-developers app
Sent from my LG-E973 using xda app-developers app
The screen is the biggest drainer of battery for this phone as it's Lcd compared to your Samsung oled... Also I would say that's a bit OK... I get about 1hr of screen time for about 20% battery drain... Although should ask that in the questions and answers thread
Also keep in mind that the Note 2 has a bigger battery (3100mAh vs 2100mAh).
I get 5 hours drain per hour on normal usage with using Music apps and data (3.5G) on.
I can't test further for LTE for my provider does not support the LTE band on my E971.
Well this is the ROM I used to use but I am since back on stock (not due to ROM, just no time to keep flashing much anymore)
My battery life was about like that since day one on stock, or on a few different roms, and back on stock again. An hour of screen on with dimmed low can drop 20%.
Screen off and LTE 64aac online radio going will drain about 25% per hour. LTE kills it crazy fast, which really bothers me because I don't play games, I don't have screen on at all most work days, I only want it to last an entire day playing online radio. It's honestly sad that it can't do it.
I get it, most phones probably can't LTE music all day, but they should be able to especially if you have 10 minutes only screen on time in the entire day. LTE is awesome but it also sucks lol.
Sent from my LG-E973 using xda premium
My battery life was about like that since day one on stock, or on a few different roms, and back on stock again. An hour of screen on with dimmed low can drop 20%.
Screen off and LTE 64aac online radio going will drain about 25% per hour. LTE kills it crazy fast, which really bothers me because I don't play games, I don't have screen on at all most work days, I only want it to last an entire day playing online radio. It's honestly sad that it can't do it.
I get it, most phones probably can't LTE music all day, but they should be able to especially if you have 10 minutes only screen on time in the entire day. LTE is awesome but it also sucks lol.
Sent from my LG-E973 using xda premium
Last edited:
Thanks guys for the reply. I knew about the note 2 having a bigger battery but I didn't know the drain was due to the screen. Sorry for the dumb question but I really wanted to know. Thanks again. I appreciate the effort in replying my post.
Sent from my LG-E973 using xda app-developers app
Sent from my LG-E973 using xda app-developers app
I also agree that the drain is due to the screen. If you would notice, the temp increases in short period of time, which is normal.
On stock, non-rooted rom, i get the same results in terms of battery life. Sometimes even worse.
So i say you are good...
Black screen
E973/Bell running 07/05.
I turned off my phone when flying for work travel (first time I've turned off since flashing, I've rebooted, but never turned off) and it won't seem to turn back on. If I hold the power button, I get an LG screen and then black (with the backlight on) which it never seems to get past.
I tried turning it off (long press power button) and letting it sit overnight and then turning it on. Same thing.
Do I need to LGNPST and then re-unlock/re-flash, or is there something I can do to recover? I'm still travelling, so I'd like to avoid re-flashing if at all possible. Even better if I can save some of my data.
Should I be able to power off, or is this expected?
Thanks for any help!
-Dan
E973/Bell running 07/05.
I turned off my phone when flying for work travel (first time I've turned off since flashing, I've rebooted, but never turned off) and it won't seem to turn back on. If I hold the power button, I get an LG screen and then black (with the backlight on) which it never seems to get past.
I tried turning it off (long press power button) and letting it sit overnight and then turning it on. Same thing.
Do I need to LGNPST and then re-unlock/re-flash, or is there something I can do to recover? I'm still travelling, so I'd like to avoid re-flashing if at all possible. Even better if I can save some of my data.
Should I be able to power off, or is this expected?
Thanks for any help!
-Dan
I've turned my phone off a few time never had a problem. Try access to recovery and just dirty flash the rom back.
Nightly changes?
I was wondering what was then difference of the nightly releases just small tweaks and changes?
I'm curious as to if it would be beneficial to to flash a new one whenever released.
Is there a change log that I might of missed? Or just keep track of the thread disscusion.
Apologies if my question is obvious to everyone im relatively new the modding of android and brand new to nightly ROMs.
I was wondering what was then difference of the nightly releases just small tweaks and changes?
I'm curious as to if it would be beneficial to to flash a new one whenever released.
Is there a change log that I might of missed? Or just keep track of the thread disscusion.
Apologies if my question is obvious to everyone im relatively new the modding of android and brand new to nightly ROMs.
Last edited:
The cyanogenmod team is currently generating innovations and fixes. Then it's up to the compiler of each devices supported to migrate the changes to a compatible build then for users to test. Chad, i believe, is just manually building these builds for our device is unsupported by cyanogenmod atm. There is a list of fixes that you can find in the cm10 website or in the BBQlog app for general changes in CM10. If there are new issues, fixes, or changes other than the general cm10 stuff, chad will inform us.
The above is just what I've learned in the early development of this ROM. I'm sure chad or someone else will give you more accurate information.
You can also take a look at http://changelog.bbqdroid.org
There you will have a full changelog of cyanogenmod. I know there is a E975 device log, but that's the official cm changelog.
Thanks for the suggestion. No dice getting in to recovery, unfortunately. So I did an LGNPST back to the 10F version and did a new freegee unlock (installing TWRP 2.5.0). Just for giggles, I turned off and tried booting. This worked fine, both in to the system and in to recovery.
So I installed CM again (07/19) and after booting and setting up my account, shut down and tried booting up again.
Same thing happened as while I was away. Black screen, won't boot in to either the system or recovery.
I'm about to try the same thing using KDZ to 20H as a base. Wish me luck.
Is there a different version I should use as a base?
---
Hmm... so now I get the black screen right after freegee with 10f, 10h, and 20h. So I don't think it's this ROM. Time to hit up IRC, I think.
Last edited:
Just to be sure...your battery is charged?
Plug it in wall charger (not a computer usb) and wait if LG charging logo appear...then, 15-20sec after the logo disappear, just try to Power On.
Maybe when you go back to stock with KDZ, your battery was not enough charged...
Give us feedback. :good:
It's a good thought, but the battery was fine. I actually found Shelnutt2 on IRC and he pointed me at the "SBL Method" unlock option (under the menu) in the latest freegee. Enabling that when unlocking solved this problem (I've since turned the phone off and on ten times in a row to test). As a side benefit, I have a Google logo instead of an LG logo when I start up.
I still don't know why it worked the first time without the SBL method and wouldn't work subsequent times, but I've got a working phone again, so I'm happy.
-Dan
It's a good thought, but the battery was fine. I actually found Shelnutt2 on IRC and he pointed me at the "SBL Method" unlock option (under the menu) in the latest freegee. Enabling that when unlocking solved this problem (I've since turned the phone off and on ten times in a row to test). As a side benefit, I have a Google logo instead of an LG logo when I start up.
I still don't know why it worked the first time without the SBL method and wouldn't work subsequent times, but I've got a working phone again, so I'm happy.
-Dan
That's great news :victory:
Do not hesitate if you have any issue in the future. :good:
I would assume the e971 needs the geeb_ca ROM... but it appears it's never been downloaded. Which ROM is for which phone?
:silly:
Similar threads
- Sticky
- Poll
Top Liked Posts
-
There are no posts matching your filters.
-
48Hi, This is a continuation of the CM 10.1 nightlies thread. Things has been moving on and we are now at CM 10.2. I have been working with xboxfanj, houstonn and bbelos to bring you this. Again, this is based on mako with adapted change for optimus G. This time we are even more in sync with CAF (Code Aurora Forum).
What is working
Everything.
What is not working
You tell me.
Here are the repo needed for our devices :
https://github.com/TeamPlaceHolder
Of course, you have to be rooted, to have bootloader unlocked and a working recovery to flash this custom rom.
DO NOT FLASH NEXUS 4 KENEL MADE BY 3rd PARTY. THIS WILL MOSTLY PERMA BRICK YOUR DEVICE.
This is simply because people tend to use partition number and not by-name and our partition is different than nexus 4 ones. i.e. The rpm partition on our phone is the boot partition on nexus 4. So flashing a custom kernel will flash a boot.img in your rpm partition and then you are bricked. You have been warned.
Like usually, i can't be hold responsible if you damage your phone during any of the process described in this thread.
Thanks :
Thracky and houstonn who also works with me on this.
xplodwild
codeworkx
IOMonster
sk8erwitskil
faux123
dvhexer
Cyanogenmod Team
and a special thanks to shelnutt2 who shown me how to fix 3G
and juggie who found out the good file to change to get wifi working20Download
All the downloads will go here :
ribs.bbqdroid.org
Use geeb package
Gapps package :
http://goo.im/gapps
Modem :
There is a newer modem now available (From JB update. Houstonn and I extracted each of them and made flashable so you don't need to do the painful process of kdz only to get a new baseband)
MAKE SURE TO NOT FLASH KOREAN MODEM.
http://downloads.codefi.re/houstonn/lgog/modem12How to intall that rom ?
This require you to have TWRP or CWM already installed on your device. I recommand the former. On our device, this mainly mean you have rooted your phone and unlocked the bootloader.
Apparently, it seems these instruction where not clear enough. So I'll try to make them dumbproof. If you are not following these instruction and it doesnt work, dont expect support. It's like buying a cake mix where you only need to add milk and call the company saying their product is bull****, you added water and only got a brick. To add to this metaphor, Asking if it's because you used CWM instead of twrp or reverse is like saying : Did it didnt work because i used a fork instead of a whip to mix it ?
To flash this rom, you have to be on older Bootloader. You can alternatively flash the bootloader i linked in this thread. Read the post carefully before you flash.
- Download file in the download section.
- Put the rom AND the gapps on your internal SDCard.
- Reboot into recovery.
- Flash CM rom.
- Flash Gapps package.
- DO A FACTORY RESET (EMPHASIS HERE)
- reboot into system
11There is a new build up. It has fixed bluetooth and has latest cm changes.
Sent from my Optimus G using xda premium8
You sir, deserve a punch in the face. Come on. We are not at optimizing things. I'm still trying to figure out what is working or not. This is really stupid.
Note to all other user : I WILL NOT ACCEPT FEATURE BEFORE EVERY PROBLEMS HAVE BEEN SOLVED.
on a related note to your question, if you would have read carefully, you would have seen that i already use faux123 kernel . . .
Anyway, this is not going to be the case soon.
