Related
Update-Solutions added
This thread kinda rambles, and covers a couple different issues.
I'll try to summarize the solutions to each to time and eliminate extra reading for those who might end up here later.
Issue #1: My Mesmerize was not recording sound with videos
Solution: Go into Voodoo Sound Control app (download from market if you don't have it) and under [recording profile], select "Original". Solved!
Issue #2: I was having various minor issues that sounded as thought they might be fixed by flashing a new kernel.
scarmon25 suggested that I try out OTB-Reloaded. He was right, this is a great kernel! It allows overclocking and undervolting at the same time. I'm hoping this will give me both better performance and greater battery life.
Solution: Backup everything (Nandroid and TiBackup suggested), Flash the new kernel from recovery (you can use ROM manager to boot into Clockwork Mod Recovery) and reboot.
I'm not about to get into a discussion of backups, recovery, flashing, which kernel you need, etc... This is just a plug/endorsement for the OTB-reloaded kernel, period.
Issue #3: At some point while updating to 2.2 Froyo and flashing new kernels, ROMs, etc... my home screen started rotating along with my apps. I could turn rotation on/off from the notification tray, but that disabled it for apps also.
Solution: It was pointed out by add144 that it's the home screen launcher that controls home screen rotation.
I'm running LauncherPro, be he mentioned that most other launchers (ADW, GO Launcher, etc...) also have the ability to allow or lock home screen rotation.
In my case (LauncherPro), here's the process for locking your homescreen rotation while still allowing auto-rotation in other apps:
1) From home screen, go to Menu (button) -> Preferences
2) Select Behavior Settings
3) Uncheck "Enable Auto-rotation"
4) Done!
I hope this summary saves someone some time and fruitless searching.
Cheers!
-Mike
----Original message follows---
Hi all,
I apologize for this question being a bit light on useful details, but my memory isn't so great.
I have a Mez, running 2.2 Froyo (updated from USCC), a custom ROM (I think), and a custom kernel (not sure which one).
I know that sounds insane, but there was a time a while back when I was flashing different things trying to find something that worked to my liking, and honestly just can't remember what combination I settled on.
It doesn't help that I'm still fuzzy on the whole ROM vs Kernel thing.
Anyway, here's the issue...
The videos I record on the phone have no sound.
You can hear a little background hiss, but no actual sound from the mic.
I can't remember if it worked before I updated to 2.2, but I suspect it did or I think I'd have noticed it before.
I guess I could flash everything back to stock and see if that fixes it, but I'd REALLY rather not do that, since it would take me so long to get it back sorted.
Is there a way to figure out exactly what I currently have installed on the phone?
Also, can anyone think of things I can do to troubleshoot the no audio issue?
Thanks in advance,
-Mike
This sounds like a issue I had on one of the earlier voodoo kernels. The fix was to download the voodoo control appear from the market and set recording preset to normal. This was fixed in the later releases of voodoo. Do you know which kernel your are on. That would help us narrow it down for you.
Edit. If you download the cpu spy app from the market you can pull your info up and see which kernel your on. It won't say exactly which one but should have the authors name in it so we can know which one your on to an extent.
Sent from my SCH-I500 using XDA Premium App
Thanks for the quick reply scarmon.
I checked my voodoo sound options (already had the app) and I don't have a 'normal' recording preset.
My choices are:
Original
Balanced (new default) - with DRC
High Sensitivity - with DRC
Loud Environment - with DRC
I assume this means I have one of the newer versions of voodoo sound?
I'll get that cpu spy app and see what it says about my kernel.
Thanks!
-Mike
Elmojo said:
Thanks for the quick reply scarmon.
I checked my voodoo sound options (already had the app) and I don't have a 'normal' recording preset.
My choices are:
Original
Balanced (new default) - with DRC
High Sensitivity - with DRC
Loud Environment - with DRC
I assume this means I have one of the newer versions of voodoo sound?
I'll get that cpu spy app and see what it says about my kernel.
Thanks!
-Mike
Click to expand...
Click to collapse
Use original
Switched to Original, audio works now, thanks!
I wonder why the "new" profiles don't work?
Is it a limitation of this phone or a problem with voodoo?
The newer voodoo kernels have that issue fixed. I believe it was just a issue with the first few ec10 voodoo kernels. May wanna try one of the new OTB or imnuts kernels. The recording works on those as I have tried both.
Sent from my SCH-I500 using XDA Premium App
scarmon25 said:
The newer voodoo kernels have that issue fixed. I believe it was just a issue with the first few ec10 voodoo kernels. May wanna try one of the new OTB or imnuts kernels. The recording works on those as I have tried both.
Click to expand...
Click to collapse
Good to know, thanks.
Is updating to one of those kernels you mentioned a simple 'boot to recovery and flash zip from SD card' or something more?
Here's a screenshot of my current kernel info from cpu spy...
Does that help any? I don't recognize that author.
EDIT: That OTB kernel sounds really interesting.
Please refer to my above question about the simplicity or complexity of flashing that kernel over the one I have now.
Yeah u flash in CWM. If your on voodoo and 2.2 then you shouldn't have any issues. If u go with OTB make sure to get the voltage control app. So u can adjust it. Just go easy on the over clock and undervolting till u see how your phone reacts. If u go with OTB let me know and I will post my settings. Been running them for a while and they seem pretty stable.
Edit. Switched to PC to correct my spelling.
Sent from my SCH-I500 using XDA Premium App
The above is what I'd try first. If you still find that you're having issues even with a new kernel, I'd consider flashing a new ROM as well.
scarmon25 said:
If u go with OTB let me know and I will post my settings. Been running them for a while and they seem pretty stable.
Click to expand...
Click to collapse
I'll be flashing OTB shortly and would love to get your settings.
Thanks!
-Mike
K, This is what I have been running and it seems pretty stable for me. Keep in mind each phone is different and yours may not respond as well, or it may do even better then mine. I would suggest using the apply for now option in voltage control for a few days and once you know there good, you can apply at boot. Also nemisses included and great feature in CWM that allows you to remove boot settings in the event that you set something at boot and it doesn't work. You will get this once you flash the OTB v1.3 kernel. This will update CWM and the feature is under the advanced section of CWM if you need it. Here's the settings I have been using.
For the Scheduler I use BFQ
I set the Max Clock to 1200mhz
I have the following step and voltage drops enabled
200 mhz -100
400 mhz -100
600 mhz -75
800 mhz -75
1000 mhz -75
1200 mhz -50
With theses settings I am getting about a day of moderate use from my battery and great performance. You may play around with it and may get better results. Hope this helps.
OTB 1.3?
The thread I was watching only goes to v1.2 for OTB-reloaded.
What am I missing?
I also noticed that is was technically a Fascinate kernel, is that a problem?
It works on the mesmerize too. That's what I'm on. There should be a link in the OP that's has v 1.3. Its he second link at the bottom of the OP
Sent from my SCH-I500 using XDA Premium App
Okay, I think I see the issue.
I was looking at this thread, whereas I think you're referring to this thread, right?
What's the difference between those 2 kernels, other than the OTB version?
one is Touch wiz and one is AOSP. If you are on stock Froyo you need touchwiz. AOSP will not work on stock ROM. You posted in the right one for OTB. This is the one you need for Stock Froyo
http://forum.xda-developers.com/showthread.php?t=1011626
The 1.3 link is towards the bottom of the first post.
scarmon25 said:
one is Touch wiz and one is AOSP. If you are on stock Froyo you need touchwiz. AOSP will not work on stock ROM. You posted in the right one for OTB. This is the one you need for Stock Froyo
http://forum.xda-developers.com/showthread.php?t=1011626
The 1.3 link is towards the bottom of the first post.
Click to expand...
Click to collapse
I don't think I'm on stock froyo, though.
As far as I can tell, I'm running SuperFrankenClean 0.292.
I base this on the files I found on my SD card while I was moving some stuff around just now.
In any case, it sounds like the touchwiz kernel is the one I need.
I'm downloading it now and will flash in a few.
Let me know if it looks like I'm about to frag something and I'll wait.
-Mike
OOPS! That should be SuperFrankenClean 2.9.2 ROM and EC10_ulv_voodoo kernel....I think.
Does that change anything?
Wait. Let me pull that ROM and I can tell you.
K this is showing to be used with touchwiz based kernels so u should be good to go.
Sent from my SCH-I500 using XDA Premium App
Yeah your good man flash away. As long as its a touch wizard kernel you good to go. If u used the one I linked u too then u will be fine.
Sent from my SCH-I500 using XDA Premium App
Awesome, flashing now....
If you hear a scream, it means it didn't work. lol
-Mike
Well I'm here all night so if it does go wrong we will fix it. But honestly you shouldn't have any issues
Sent from my SCH-I500 using XDA Premium App
I've seen a couple of posts about this, but can't figure out how to get it to work. I installed Faux's DS OC/UV Kernel Version 0.4.3 kernel, but I can't get that OC/UV kernel to even boot. The soft keys light up, the screen turns off, and the phone just sits there.
Did a nandroid restore, and then installed Faux's DS SV Kernel Version 0.4.3 kernel. No problems with it so far, but I just wanted to know how some people can get the OC/UV kernel to work with the G2x, but others can't (aren't all these phones identical in terms of architecture, chips, etc.?)?
Just wondering if there's any improvement to battery life with this new kernel. I have SetCPU running too and have several different profiles setup.
Which ROM are you using?
Oops. Sorry. CM 7.1.0.1.
hadoob024 said:
I've seen a couple of posts about this, but can't figure out how to get it to work. I installed Faux's DS OC/UV Kernel Version 0.4.3 kernel, but I can't get that OC/UV kernel to even boot. The soft keys light up, the screen turns off, and the phone just sits there.
Did a nandroid restore, and then installed Faux's DS SV Kernel Version 0.4.3 kernel. No problems with it so far, but I just wanted to know how some people can get the OC/UV kernel to work with the G2x, but others can't (aren't all these phones identical in terms of architecture, chips, etc.?)?
Just wondering if there's any improvement to battery life with this new kernel. I have SetCPU running too and have several different profiles setup.
Click to expand...
Click to collapse
Faux has 2 kernel versions.... one that is PRE-Overclocked and PRE-Undervolted; and the other that is starts with stock speeds and voltages.
I've NEVER been able to get the pre-OC/UV'd kernels to work on any of the several phones I have went through. I get EXACTLY what you are getting now, just a black screen and unable to boot.
Download his "SV" rom. That is his kernel that starts off with stock settings. You'll get all the features and you can OC/UV manually.
Cool. Yeah, I got the SV running just fine now. Since you can't mess with the voltages with this kernel, does it still offer any better battery performance than the stock kernel?
You'll get all the features and you can OC/UV manually
Click to expand...
Click to collapse
Are you talking about adjusting these settings through SetCPU? For some reason, SetCPU works fine for changing clock speeds, but when I try and go to the "Voltages" tab in SetCPU, bam, it crashes with:
"The application SetCPU (process com.mhuang.overclocking) has stopped unexpectedly. Please try again."
hadoob024 said:
Cool. Yeah, I got the SV running just fine now. Since you can't mess with the voltages with this kernel, does it still offer any better battery performance than the stock kernel?
Are you talking about adjusting these settings through SetCPU? For some reason, SetCPU works fine for changing clock speeds, but when I try and go to the "Voltages" tab in SetCPU, bam, it crashes with:
"The application SetCPU (process com.mhuang.overclocking) has stopped unexpectedly. Please try again."
Click to expand...
Click to collapse
Make sure you delete setcpu data and cache everytime you change kernels or else you'll see that message.
Sent from my Calculator with Android.
jose makalolot said:
Make sure you delete setcpu data and cache everytime you change kernels or else you'll see that message.
Click to expand...
Click to collapse
Are you talking through Settings->Manage Applications->SetCPU?
hadoob024 said:
Are you talking through Settings->Manage Applications->SetCPU?
Click to expand...
Click to collapse
Yes.
Sent from my Calculator with Android.
jose makalolot said:
Yes.
Click to expand...
Click to collapse
OK. Just tried it. "Clear cache" was grayed out, but I did click on "Clear data" and then rebooted. I launched SetCPU. Chose the Tegra 2 chipset, selected "Set on Boot", created my Profiles, then tried Voltages, but got the same error
Any thoughts?
hadoob024 said:
OK. Just tried it. "Clear cache" was grayed out, but I did click on "Clear data" and then rebooted. I launched SetCPU. Chose the Tegra 2 chipset, selected "Set on Boot", created my Profiles, then tried Voltages, but got the same error
Any thoughts?
Click to expand...
Click to collapse
Never mind, mods please delete.
From my experience, Faux's kernel isn't playing nice with the latest stable CM release. That's why right now I'm back on stock CM kernel.
jamadio said:
From my experience, Faux's kernel isn't playing nice with the latest stable CM release. That's why right now I'm back on stock CM kernel.
Click to expand...
Click to collapse
Hmm.. Interesting. I'll keep an eye out for it. Today's my first full day with that combination of mod and kernel. Other than the weird battery charge amount readings, it seems to be stable with a better battery life than the CM kernel. Wish I could mess with the voltages too to try and eek out even more battery life. Oh well though.
Have you deleted your battery stats in CWM? When I had Faux 0.4.3 and EaglesBlood 2.4 (CM7 based) running together I had the same battery problems. I eventually went back to stock CM kernel and then I cleared the battery stats and everything normalized again.
To appropriately clear the battery stats, you have to be at 100% charge before you do it.
Let me know how it works, maybe I'll go back to 0.4.3.
jamadio said:
Have you deleted your battery stats in CWM? When I had Faux 0.4.3 and EaglesBlood 2.4 (CM7 based) running together I had the same battery problems. I eventually went back to stock CM kernel and then I cleared the battery stats and everything normalized again.
To appropriately clear the battery stats, you have to be at 100% charge before you do it.
Let me know how it works, maybe I'll go back to 0.4.3.
Click to expand...
Click to collapse
No kidding??? Nope. Hadn't heard about that. Will give that a shot late night tonight after I fully charge it when I get home. Thanks for the tip!
Any thoughts on this issue with SetCPU and not being able to access the "voltages" tab?
I went back and read over from the beginning of this thread to refresh myself. Two reasons come to mind:
1. It could be because I don't think Faux's SV kernel is optimized/set up to have it's voltages changed. On his OP, he won't even troubleshoot problems unless they're on the SV kernel. Hence, it makes sense not to give people the freedom to OC/UV it so they can't complain about problems they made for themselves.
2.It could also be SetCPU, I know other's have gone to Pimp My CPU (You can search it on XDA) because PMCPU was built from the ground up to OC and UV, but it's features outside of that are sparse. But eventually SetCPU caught up and is the No.1 for OC/UV.
Maybe giving Pimp My CPU a try wouldn't hurt, if it doesn't work than you know that the kernel won't allow it.
Cool. I guess I'll give this current combo a try and see if I even feel the need to mess with voltages. Got pretty good batter life today so far. Going to go home, charge the phone fully, wipe the battery stats and then resume testing.
I like how I can setup profiles on SetCPU. Wonder if PMCPU has something similar.
Thanks again though!
hadoob024 said:
I like how I can setup profiles on SetCPU. Wonder if PMCPU has something similar.
Thanks again though!
Click to expand...
Click to collapse
No problem. Yeah, that's what makes SetCPU so legit. I don't believe Pimp My CPU has that feature. Just establishing max, min, and their voltages. Could be wrong though.
Cool. I'll give this "clear battery stats" a shot and then might give this other app a try. So far impressed with how much battery life I have left already.
hadoob024 said:
Cool. I'll give this "clear battery stats" a shot and then might give this other app a try. So far impressed with how much battery life I have left already.
Click to expand...
Click to collapse
Any update?
I'm going to have to try later this evening or tomorrow. I forgot but when doing app updates, CW ROM Manager got updated. Anyway, I guess this update did something because when I tried rebooting into Recovery, it never did, it just rebooted normally into CM.
I finally launched CW ROM Manager, chose to "Reboot into Recovery", it then asked for su permissions (or something) and finally worked. Anyway, I rebooted like 4 or 5 times before I realized that this was the issue preventing me from rebooting into Recovery like I normally do. That put enough of a drain on the battery where I didn't want to wipe the battery stats <sigh>
And of COURSE I didn't bring my charger
Will try again this evening and post the results.
Hi all. I've spent more time than I should over the past week or so looking through these forums (thank you all for the amazing amount of work that's been put in), but really haven't been able to figure out the answer to the following question: What's the best configuration for this phone?
I've been running EaglesBlood, which is OK but somewhat buggy (battery drain, random turning on of phone button lights, etc). Is there any configuration that's stable, fast, and decent?
SINGH-UI + Mazout360 Kernel
I am very happy with my setup:
SINGH-UI MIUI with Mazout360's kernel
I was using Faux123's 054 kernel with lg voltage which was working very well but Mazout's kernel is newer, faster and fixes a wifi issue that was causing reboots when turning wifi-related stuff on and off. I'm still testing it for stability but so far so good.
I haven't tried the ICS and Jelly Bean ROMS.
vanilla cm7 w/ mazouts kernel
"my mind draws lots of blanks actually"
Pardon my ignorance, but I don't quite understand how one can be running cm7 (or SINGH-UI MIUI) and mazout's kernel. Aren't they different roms? I'm missing some basic understanding here.
justjackyl said:
vanilla cm7 w/ mazouts kernel
"my mind draws lots of blanks actually"
Click to expand...
Click to collapse
This is more or less how it works. The "rom" is mostly blue stuff.
natescape said:
Pardon my ignorance, but I don't quite understand how one can be running cm7 (or SINGH-UI MIUI) and mazout's kernel. Aren't they different roms? I'm missing some basic understanding here.
Click to expand...
Click to collapse
A kernel is just a layer that interacts between the ROM and the physical hardware.
Like a car:
ROM = Body
Kernel= Engine
You can pull the engine and put it in a different body.
Poor analogy probably lol
"my mind draws lots of blanks actually"
justjackyl said:
vanilla cm7 w/ mazouts kernel
Click to expand...
Click to collapse
Seems it could last for days with the right configuration. I don't know what it would be except turning off data when not in use, and turning off auto sync.
Sent from my LG-P999 using xda app-developers app
adamiscool said:
Seems it could last for days with the right configuration. I don't know what it would be except turning off data when not in use, and turning off auto sync.
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
What?
Sent from my LG-P999 using Tapatalk 2
Mazout's 218 kernel and CM7 2-1-13 works pretty well for me. Although, I think I was getting slightly better battery life on Mazout's 205 kernel.
figuratively said:
Mazout's 218 kernel and CM7 2-1-13 works pretty well for me. Although, I think I was getting slightly better battery life on Mazout's 205 kernel.
Click to expand...
Click to collapse
Agreed. Better battery on 0205.!
"my mind draws lots of blanks actually"
Thanks guys!
So if I was to try one of these configs, first I'd install the ROM, then the kernel?
justjackyl said:
Agreed. Better battery on 0205.!
"my mind draws lots of blanks actually"
Click to expand...
Click to collapse
natescape said:
Thanks guys!
So if I was to try one of these configs, first I'd install the ROM, then the kernel?
Click to expand...
Click to collapse
That is correct
dEris said:
What?
Click to expand...
Click to collapse
Apps like to sync in the background. These settings can be changed to be turned off or run at a different interval of time. The mazkrnl and cm7 nightly has gotten me beyond 24hrs of use, but I think it can go beyond that with the right settings. I believe it could last a week or more. That clear it up?
Edit: haha, I mean...I don't know if you're trolling or what.
Sent from my LG-P999
natescape said:
Thanks guys!
So if I was to try one of these configs, first I'd install the ROM, then the kernel?
Click to expand...
Click to collapse
I'm also fairly new to all this and I would just like to offer some tips:
1. ensure you have the newest baseband before doing anything
Check your phone (Settings->System->About phone) Should be March 2012 Baseband
If you don't have the new baseband, there are a few tutorials such as this one
2. Install ROM and kernel if needed
3. Install the recommended google apps zip as instructed
4. Install GetRIL from app store and use it to install matching RIL
5. I believe you should Install a cpu control app for power saving (I'm using Antutu CPU master)
You could install kernel last. ROMS come with their own kernels.
m3mb3rsh1p said:
I'm also fairly new to all this and I would just like to offer some tips:
1. ensure you have the newest baseband before doing anything
Check your phone (Settings->System->About phone) Should be March 2012 Baseband
If you don't have the new baseband, there are a few tutorials such as this one
2. Install ROM and kernel if needed
3. Install the recommended google apps zip as instructed
4. Install GetRIL from app store and use it to install matching RIL
5. I believe you should Install a cpu control app for power saving (I'm using Antutu CPU master)
You could install kernel last. ROMS come with their own kernels.
Click to expand...
Click to collapse
If you switch to the March 2012 Baseband, you WILL LOSE Bluetooth Calling on any custom ROM used. I HIGHLY advise NOT switching basebands if you are a bluetooth headset user.
New2my8125 said:
If you switch to the March 2012 Baseband, you WILL LOSE Bluetooth Calling on any custom ROM used. I HIGHLY advise NOT switching basebands if you are a bluetooth headset user.
Click to expand...
Click to collapse
+1
"my mind draws lots of blanks actually"
huh
I did not know that. I guess I should find out what's good about the newest baseband and quick one is best...
Quick Question
This post is the guide I used when upgrading my baseband. I'll use it to downgrade when I start using bluetooth audio.
m3mb3rsh1p said:
This post is the guide I used when upgrading my baseband. I'll use it to downgrade when I start using bluetooth audio.
Click to expand...
Click to collapse
its only bt call audio that doesn't work on 21y. media audio works fine.
"my mind draws lots of blanks actually"
I installed CM 7.2 and gapps with no issues, but Mazout's kernel doesn't seem to be loading. I get a "Problem loading widget" error. What might I be doing wrong?
We are now officially on CyanogenMod, this thread is old.
Bug list:
Minor glitch switching from video recording on FFC (switch to back camera before switching back to still images)
Flash while video recording
Pandora while using Bluetooth/wifi at the same time
MMS sizes set too big?
You tell me.
Wontfix:
Chargers that do not send any signals on D+/D-
Enhancements needed:
Panel colors/gamma correction code needs porting from d2 (Galaxy S III)
Seems great so far. WIFI speed is much better.
I am having no luck toggling NFC though. A small request as well: Can the default Bluetooth name be changed back to Relay instead of Galaxy S 3.
I'm finding that if I have headphones plugged in at boot, there's no sound until I unplug them and then reconnect. GPS also seemed to drop a lot on the way to work this morning, but that might be coincidence. Other than that, the new ROM seems to be working very well.
Nardholio said:
We've swapped over to the 3.4 kernel on our nightlies, so I decided to make a new thread.
YOUR WARRANTY IS NOW VOID. WILL EAT YOUR CAT.
Will do proper write-up later
NOTE: You will need to be fully updated on bootloader and modem to use this. You can get the updated versions here http://forum.xda-developers.com/showpost.php?p=41209211&postcount=1
Nightlies: http://ls.infernix.net/jenkins/job/apexq/
ROM Features:
Commonized d2 base (ApexQ blobs for now, trying to integrate)
Fully functional sound/wifi/bt/camera (including wifi direct, meaning your remote wifi display may work now [untested])
Click to expand...
Click to collapse
Regarding the bootloader and modem from that post, can the zip files be flashed via CWM? Also, what versions should it report?
John5788 said:
Regarding the bootloader and modem from that post, can the zip files be flashed via CWM? Also, what versions should it report?
Click to expand...
Click to collapse
I was able to flash them in CWM yes. Just mind the GPS toggle as stated in the previous post.
Going to add one more bug here, I'm having problems with certain chargers, especially if they're plugged in during boot. Looks like I need to spelunk into the kernel a bit more.
lbcoder fixed wifi mac addresses. Here's mine, just for fun
https://www.dropbox.com/s/qpte7lv0ijencic/2013-06-29 10.39.56.png
The wallpaper isn't covering the far left screen on my desktop (5 screens). It happens with trebuchet, nova and apex launchers so it might be something that needs to be adjusted from the d2 settings.
Sent from my SGH-T699 using xda app-developers app
Miracast
I understand that you don't have an adapter, but can you confirm that you see the Wireless Display option?
Settings > Display > Wireless Display
Thanks!
Total Reserve.
Sent from my LG-LS970 using xda app-developers app
I flashed 196 yesterday and everything seems to be working, except that it would not boot (stayed in the boot logo) until I started the boot with my character unplugged. GPS took a long time to sync up right until I did a cold start, and then it took about as long as that normally does. There are still possibly some charger issues which I will report as I find them. BT works (had to repair everything), Wifi works, haven't used headphones yet, am using a 4100mAh w/o the NFC, so I can't test that.
Sent from my SGH-T699 using xda app-developers app
Seems to work well.
1)
However BetterBatteryStats tell me the phone is not achieving deep sleep at all, rather in 'Awake' state 100% of time (under Other) & CPU States illustrates no info for 'Deep sleep'...
2)
Just tested 'wifi direct' with a friend running cm10.1 Stable on his Nexus 4... he can see my device yet the relay cannot see any devices when scanning. Progress but not yet functional :thumbup:
Sent from my SGH-T699 using xda app-developers app
And, interestingly enough, it now says that it is charging (led and spinning meter) when it is completely unplugged. Can we have discovered a way tap into the cosmic background energy pool? Untold wealth awaits!
Sent from my SGH-T699 using xda app-developers app
I am noticing that screen on takes a while once the phone has been locked and screen off for a while. It almost feels like sleep death, but after a while, the screen comes back by itself.
misteropinion said:
And, interestingly enough, it now says that it is charging (led and spinning meter) when it is completely unplugged. Can we have discovered a way tap into the cosmic background energy pool? Untold wealth awaits!
Sent from my SGH-T699 using xda app-developers app
Click to expand...
Click to collapse
Flashing up to 198 fixes this. I think that fixes all of my "daily drive" features. I'll try it with a bunch of chargers today and see if any of them don't work.
Runnning on198 and everything is smooth, even underclocked. Using conservative and very little if any slowdown, and I have 142 apps!
Sent from my SGH-T699 using xda premium
No matter how I try to install the latest 3.4 nightlies I cannot achieve 'deep sleep' ever (100% awake.)
Before installing the 3.4 rom, I installed the MC5 modem & Bootloader & rebooted (as per original post here.)
Back into recovery & I initially tried full system/data/cache/dalvik wipes (and also for the first time on this device I also wiped "/data &/data/media" in the mount menu) before installing the 3.4 rom & gapps.
No deep sleep.
I revert back to my 3.0 nand backup and deep sleep is restored.
Then attempt a flash over the 3.0 restore with the latest 3.4 nightly... same dillema - no 'deep sleep.'
Am I alone or Is anyone else experiencing this?
For anyone who is on 3.4 and achieving 'deep sleep' (I know lbcoder & nard have confirmed they achieve deep sleep via IRC chat) can you please share your exact method in migrating from 3.0 to 3.4 (including when & how you exactly flashed the modem &/or bootloader.)
For what it's worth the recovery I have been on for a while now is CWM Version 6.0.2.8.
Baseband under settings/other shows " T699UBVMC5."
I'm using BetterBatteryStats to determine 'deep sleep' status.
Using 'Android Root Toolkit' (the only method I could find to detail bootloader version) to tell me my bootloader version as "T699UBVMC5."
I can't see that I'm doing anything out of turn.
I'm a well seasoned CWM flasher (well atleast I thought I was ), tried builds 197,8 & 9, same effect for me.
Any thoughts, ideas, cures, methods would be greatly appreciated.
Thanks in advance
Sent from my SGH-T699 using xda app-developers app
Here is a related thread that may help http://forums.androidcentral.com/sp...keeping-my-phone-awake-eating-my-battery.html. also there is a deep sleep app on playstore. I had it but I usually toggle everything on and off from pulldown menu as a need it, which saves enough battery for me.
Sent from my SGH-T699 using xda premium
misteropinion said:
Flashing up to 198 fixes this. I think that fixes all of my "daily drive" features. I'll try it with a bunch of chargers today and see if any of them don't work.
Click to expand...
Click to collapse
My in-car charger still makes my phone stupid, where after I unplug it still says that it's charging. Power consumption is definitely up, my 4100mAh battery is behaving like the 1800 used to.
Hi guys!
I was looking for ways to increase battery life.
As far as I know you can undervolt and decrese CPU speed
Undervolt does not affect performance but does increase temperature right?
Decrease CPU speed obviously decreases the speed of the phone.
Both these things can be achieved by using a custom kernel right? I heard of franco kernel as being the best for these things...
Any other ways of increasing battery life?
Cheers!
nad4321 said:
Hi guys!
I was looking for ways to increase battery life.
As far as I know you can undervolt and decrese CPU speed
Undervolt does not affect performance but does increase temperature right?
Decrease CPU speed obviously decreases the speed of the phone.
Both these things can be achieved by using a custom kernel right? I heard of franco kernel as being the best for these things...
Any other ways of increasing battery life?
Cheers!
Click to expand...
Click to collapse
Why not try Franco first before starting to tweak. The kernel's default settings are reputedly optimal for that elusive balance between performance and battery life.
Sent from my Nexus 5
PhilipTD said:
Why not try Franco first before starting to tweak. The kernel's default settings are reputedly optimal for that elusive balance between performance and battery life.
Sent from my Nexus 5
Click to expand...
Click to collapse
yeah well im using stock now so it was just a matter wether changing to franco would make a difference
nad4321 said:
yeah well im using stock now so it was just a matter wether changing to franco would make a difference
Click to expand...
Click to collapse
Yeah, give it a try. Since I installed it, the phone (and my N7, too) has become snappier, and battery life on standby is awesome (like 1-2%/hr). SOT, on the other hand, is still lamentable, even at dim levels. If you do go Franco, I recommend getting the FK updater app on the Play Store.
Sent from my Nexus 5
PhilipTD said:
Yeah, give it a try. Since I installed it, the phone (and my N7, too) has become snappier, and battery life on standby is awesome (like 1-2%/hr). SOT, on the other hand, is still lamentable, even at dim levels. If you do go Franco, I recommend getting the FK updater app on the Play Store.
Sent from my Nexus 5
Click to expand...
Click to collapse
Cheers! Do you know any good tutorial to unlock bootloader, root and instal custom recovery + kernel? Long process hahaha
nad4321 said:
Cheers! Do you know any good tutorial to unlock bootloader, root and instal custom recovery + kernel? Long process hahaha
Click to expand...
Click to collapse
There's a tutorial on this in the forum. I'd link it to you but I am on my tablet at the moment.
Sent from my Nexus 7 using Tapatalk 4
nad4321 said:
Cheers! Do you know any good tutorial to unlock bootloader, root and instal custom recovery + kernel? Long process hahaha
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2507905
http://forum.xda-developers.com/showthread.php?t=2508284
Sent from my Nexus 5
PhilipTD said:
http://forum.xda-developers.com/showthread.php?t=2507905
http://forum.xda-developers.com/showthread.php?t=2508284
Sent from my Nexus 5
Click to expand...
Click to collapse
Thanks again From your own experience what would you recommend TWRP or CWM
nad4321 said:
Thanks again From your own experience what would you recommend TWRP or CWM
Click to expand...
Click to collapse
TWRP, without a doubt. It's completely stable, and easy to use. CWM used to be really wonky; that's why I switched.
Sent from my Nexus 5
PhilipTD said:
TWRP, without a doubt. It's completely stable, and easy to use. CWM used to be really wonky; that's why I switched.
Sent from my Nexus 5
Click to expand...
Click to collapse
I guess all of these CPU speeds and undervolt can be changed at any time withouth erasing anythign right?
nad4321 said:
Thanks again From your own experience what would you recommend TWRP or CWM
Click to expand...
Click to collapse
Philz touch. Its cwm based, more features than twrp and cwm put together and more stable than both too.
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
nad4321 said:
I guess all of these CPU speeds and undervolt can be changed at any time withouth erasing anythign right?
Click to expand...
Click to collapse
You can set up virtually any configuration with Franco. But, again, I suggest you try his default settings first. He put a lot into figuring it out, and his findings likely are the most reliable. I've never felt the need to customize the kernel any differently.
Some people, however, really like to mess around with the settings as a kind of hobby. I used to do so, and it's a lot of fun (and headaches). So, if you want to get into it, go for it. There are numerous apps you can use to tweak all those settings.
Sent from my Nexus 5
---------- Post added at 07:03 AM ---------- Previous post was at 07:01 AM ----------
rootSU said:
Philz touch. Its cwm based, more features than twrp and cwm put together and more stable than both too...
Click to expand...
Click to collapse
I know, I've been meaning to check out out. Thanks
Sent from my Nexus 5
PhilipTD said:
You can set up virtually any configuration with Franco. But, again, I suggest you try his default settings first. He put a lot into figuring it out, and his findings likely are the most reliable. I've never felt the need to customize the kernel any differently.
Some people, however, really like to mess around with the settings as a kind of hobby. I used to do so, and it's a lot of fun (and headaches). So, if you want to get into it, go for it. There are numerous apps you can use to tweak all those settings.
Sent from my Nexus 5
---------- Post added at 07:03 AM ---------- Previous post was at 07:01 AM ----------
I know, I've been meaning to check out out. Thanks
Sent from my Nexus 5
Click to expand...
Click to collapse
I noticed that by default it has 2 cores working and then uses the other 2 when required... This might sound stupid but did stock already do this?
Try greenify and xposed framework.
https://play.google.com/store/apps/details?id=com.oasisfeng.greenify
Im running the catalysm rom + franco kernel undervolted (which by the way decreases the temperature) and under clocked to 1728mhz. I also am using greenify + xposed. Finally I turn off location reporting, touch sounds, always scanning wifi and set location to "battery saving" mode. Without any gaming I get around 5hr of screen on time. Straight gaming gives me around 2.5hr of SOT. Usually I get around 4hr from my regular day. Any other tips for battery?