Has anyone tested out all the different CM10 versions that our out?
I've been using CM 10.1 unofficial nightly from 06-09-2013. It had all the features working that i use (wifi + BT audio for example) which is why I hadn't updated since.
But seeing the development that was made for 10.1 with 3.4 kernal, and 10.2, I was wondering if anyone had a suggestion of the most stable ROM
Thanks!
I'm using the "last stable" from here : http://forum.xda-developers.com/showthread.php?t=2180163
volume's a bit quiet on bluetooth HSP and Audio also in phone calls, i can't use half my chargers either but battery life, speed and stability are great.
you should carry on in this thread, though, as this one is in the wrong forum and I created this one 2 days ago asking the same thing.
... http://forum.xda-developers.com/showthread.php?t=2453657
WiFi + bt together broke when we changed kernels. If that's important to you, you may not want to upgrade.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
actually i discovered (which you may have already known) its just the 2.4ghz band. I have a 5.0ghz wireless N router which i can use with bluetooth no problem.
Related
When NS is connected to my car audio system, it randomly disconnects and then re-connects after a few seconds.
This does not happen with other android phones I have tried.
I'm running AOKP ICS Milestone 6 rom.
Is this related to the radio(modem) being used or is it ROM related ?
I couldn't tell you what the issue is but you could try bumping your minimum cpu speed up. I've found in the past that seems to help with stability issues with bluetooth and gps sometimes. I've gotten to where I've basically given up on using bluetooth after having a lot of problems with it on 2 different phone models and multiple versions of android on each. Some people seem to run it fine but I always have issues. You could try a different kernel too.
Sent from my Nexus S 4G using xda premium
(NOTE: I'm still not allowed to post in the appropriate Android Developers forum, as of yet.)
...tonyp's ParanoidAndroid JB so far, has been the go to ROM for my G2X; far smoother and slicker than the EB ICS I used to run. Aside from the foreseeable battery drain (I always keep a charged spare on me, but usually a single overnight charge lasts a full work day), this ROM is the closest thing to stable I've encountered.
But one question:
My G2X has always suffered from a Sleep of Death about two out of every three times, all and only during voice calls (incoming or outgoing); regardless of Android ROM used.
This makes it a headache retrieving voicemails (keypad not accessible), leaving voicemails (cannot end calls), or the inability to end calls with people (i.e., my dad) who do not manually hang up on their end. (Luckily, I'm more of a texter and people rarely call me; so I wouldn't know what would happen in a call waiting situation.)
My only recourse is to take apart my Trident casing, remove the back plate and take out the battery. Ugh.
After asking around XDA about an in-call SoD solution, a majority said to up the CPU processor to about 500-600 mHz. But alas, the minimum CPU configuration is greyed-out in Performance settings.
(I've flashed the new baseband file after the ROM installation because I'm using the V21y March 2012 kernel. As well, I've used the GetRIL app to match the recommended baseband, just to be sure.)
So how exactly can I configure the minimum CPU settings?
(Or am I just not allowed to?)
Again, this SoD during phone calls is universal to my G2X regardless of Android ROM. So any help (or plausible alternate methods and solutions) are more than appreciated.
Seasons beatings,
Francis.
Sent from my Nexus 7 using xda app-developers app
meatfest1974 said:
(NOTE: I'm still not allowed to post in the appropriate Android Developers forum, as of yet.)
...tonyp's ParanoidAndroid JB so far, has been the go to ROM for my G2X; far smoother and slicker than the EB ICS I used to run. Aside from the foreseeable battery drain (I always keep a charged spare on me, but usually a single overnight charge lasts a full work day), this ROM is the closest thing to stable I've encountered.
But one question:
My G2X has always suffered from a Sleep of Death about two out of every three times, all and only during voice calls (incoming or outgoing); regardless of Android ROM used.
This makes it a headache retrieving voicemails (keypad not accessible), leaving voicemails (cannot end calls), or the inability to end calls with people (i.e., my dad) who do not manually hang up on their end. (Luckily, I'm more of a texter and people rarely call me; so I wouldn't know what would happen in a call waiting situation.)
My only recourse is to take apart my Trident casing, remove the back plate and take out the battery. Ugh.
After asking around XDA about an in-call SoD solution, a majority said to up the CPU processor to about 500-600 mHz. But alas, the minimum CPU configuration is greyed-out in Performance settings.
(I've flashed the new baseband file after the ROM installation because I'm using the V21y March 2012 kernel. As well, I've used the GetRIL app to match the recommended baseband, just to be sure.)
So how exactly can I configure the minimum CPU settings?
(Or am I just not allowed to?)
Again, this SoD during phone calls is universal to my G2X regardless of Android ROM. So any help (or plausible alternate methods and solutions) are more than appreciated.
Seasons beatings,
Francis.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Are you using an app to change settings? Like SetCPU, or Pimpmycpu, or any other app?
Also what ROM are you currently using? From reading your post, is it CM7?
Sent from my LG-P999 using xda app-developers app
I'd like to mention, that every time I use GetRIL I always get a lot more battery drain and it gives me problems, if you're using CM7 like me (or anything else) don't change the RIL, because someone mentioned before that it makes it somewhat incompatible or whatever and I have noticed that it makes my battery drain faster and my phone run hotter, thats just my experience from GetRIL.
Sent from my Nexus 7 using xda app-developers app
... uh, it's CM10 and it's build 8 of Hackfest JB ParanoidAndroid v.2.24.
Insofar as the settings go, I've been using the Settings->Performance in trying to configure the CPU; which is greyed out.
I understand that wanting JellyBean on a G2X may be a bit too much to ask, but heck, it sure is fun to have.
Sent from my Nexus 7 using xda app-developers app
Hmmm, I'm in a bit of tough spot.
My Wifi speeds are horrible on a CM7.2 ROM. I'm using a custom rom (from cm forum) that someone built to solve the bad bluetooth headset profile that was regressed into the cm7.2 release. I need cm7.2 cause its' bluetooth also supports HID. Unfortunately, wifi speeds suck in this rom. I can't remember whether the cm7.2 stable had poor wifi speeds.
Does anyone recall what this wifi problem was, and how to fix it?
Thx,
rickbol
rickbol said:
Hmmm, I'm in a bit of tough spot.
My Wifi speeds are horrible on a CM7.2 ROM. I'm using a custom rom (from cm forum) that someone built to solve the bad bluetooth headset profile that was regressed into the cm7.2 release. I need cm7.2 cause its' bluetooth also supports HID. Unfortunately, wifi speeds suck in this rom. I can't remember whether the cm7.2 stable had poor wifi speeds.
Does anyone recall what this wifi problem was, and how to fix it?
Thx,
rickbol
Click to expand...
Click to collapse
You could use smanager ads or pro along with v6 supercharger ( http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021 ). There is a 3g and wifi hack in that script.
blakeatl said:
You could use smanager ads or pro along with v6 supercharger ( http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021 ). There is a 3g and wifi hack in that script.
Click to expand...
Click to collapse
It's actually in the 3G TurboCharger script, but it is on the thread you linked to.
Thanks, I'm reviewing those scripts.
Additional info... I disabled N support on my AP and my wifi throughput increased from 300-1000 kbs to a consistent 3000-4000 kbs. So that's alot better. But, CM7.2 wifi consistently shows a ~10DBm sensitivity deficit compared to another phone sitting next to it. Also, the Evo Shift stock ROMs sensitivity was more on order with this other phone. So I don't know if the sensitivity deficit is a bug, or part of the power\battery management.
I'm new to CM7.x, so I don't know how I can best test these thing. If I plug the phone in, does it automatically run in "Performance" mode for all features?
The issue I'm facing is I'm trying to use GrooveIP (VoIP) over Google Voice. I was having issues with this phone, and I beleive they were related to the wifi performance.
Any other suggestions for testing or debugging?
rickbol
As I continue to investigate this wifi issue, I discover that this CM7.2 has no tiwlan*.ini anywhere on the system. Other "slow wifi" reports mention using a CM6.x tiwlan.ini to fix CM7.2 wifi issues.
Can anyone confirm that a CM7.2 ROM should have tiwlan.ini? Where is it? The only file in /etc/wifi, /system/etc/wifi on this machine\rom is wpa_supplicant.conf.
What I'm really looking for is a ROM that: supports all the standard evo shift hardware stuff (inlcluding wimax), plus, bluetooth HID. It be great if it also improved on battery life.
Any contenders\suggestions?
Thx,
rickbol said:
As I continue to investigate this wifi issue, I discover that this CM7.2 has no tiwlan*.ini anywhere on the system. Other "slow wifi" reports mention using a CM6.x tiwlan.ini to fix CM7.2 wifi issues.
Can anyone confirm that a CM7.2 ROM should have tiwlan.ini? Where is it? The only file in /etc/wifi, /system/etc/wifi on this machine\rom is wpa_supplicant.conf.
What I'm really looking for is a ROM that: supports all the standard evo shift hardware stuff (inlcluding wimax), plus, bluetooth HID. It be great if it also improved on battery life.
Any contenders\suggestions?
Thx,
Click to expand...
Click to collapse
I don't know if you have any options with all those on the Shift.
If you are having trouble with CM7 not working well enough for you then stick with a STOCK based sense rom, every asop GB rom is based around the work done on CM7.
BigSplit said:
If you are having trouble with CM7 not working well enough for you then stick with a STOCK based sense rom, every asop GB rom is based around the work done on CM7.
Click to expand...
Click to collapse
I would suggest strapped365's 2.77.651.8 [Rooted Stock-O.T.A] Rom, or Chad The Pathfinder's Stock Mod [SENSE 2.1 | 2.3.4]. There are quite a few others, these are just two of the latest that are quite stable .
Thanks for the ROM suggestions. I actually have the StockMod as my Sense rom for when I have to update Profile and PRL (I recently switched to Ting... so far, so good).
I've been able to poke around a bit down in linux on CM7. I'm suspecting the bcm4329.ko driver has some config wrong in it, but I don't know how to t-shoot settings really. Since the sensitivity is down by ~-10dBm, but otherwise working, I almost think misconfigured antennas or something. "iwconfig eth0" often reports relatively high "Noise level" and some "Tx excessive retries" although I don't have lots of 2.4GHz equipment competing for the spectrum (afaik).
Regarding the linux layer in Android, do both CM and Sense use pretty much the same implementations with regards to (wifi) hardware, or do they use different "management" interfaces? I guess CM is the one that departs most from "stock", but I don't yet have a feel for whether these departures are mostly in the Android layer, or whether they go deep under the hood into the kernel.
This "low-sensitivity wifi" issue is a widely reported issue thru all makes of phones and versions of (at least) CM, but I have yet to come across any positive diagnosis of the source of the issue (although, given the reports, I suspect a common cause). My hunt continues. Seems all the later dev of CM forgoes wimax functionality... and while wimax hasn't proved to be widely available, it does exist in my area, and 3G is so saturated that it's worth trying wimax when available.
Thanks for the help,
rickbol
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.
I have this strange issue when it comes to Bluetooth with my N5...
The audio works fine on AUX and that is not an issue. The issue is that when I play music through Bluetooth it sounds really crappy, and all the high frequencies are very distorted.
It sounds perfect with CM11 and ElementalX kernel, but I want to use PA with franco.kernel, as I get much better battery life and performance, plus there are more features that I like in PA.
From this, I have worked out that it's a problem with AOSP, as CM is CM based and PA is AOSP based.
Can anyone suggest a solution? I've tried installing Viper4Android and although the sound is amazing with AUX, it is still piss poor with A2DP.
Any solutions would be greatly appreciated. I might even buy you a beer! :good:
Bump?
Sent from my Nexus 5 running PA 4.1 and franco.kernel
Not sure if I fall under this same issue. I have Stock with Xposed with Franco r34 didnt tweak any of the kernel settings too. What happens with me. I have music saved in my phone. When screens is off and its playing from my bluetooth stereo it lags the hell out. It just started happening this morning. I need to test out to see maybe the phone needed a reboot. I am playing music right now with the screen off without bluetooth no issues. I just need to play out of the bluetooth see if it was just a glitch now that I rebooted my phone.
Turn the volume down two notches when playing via bluetooth
Sent from my Nexus 5 using Tapatalk
Wow sorry, I totally forgot I made this post.
Turning the volume down does nothing to help.
Sent from my Paranoid, ARTified and Francoed Nexus 5 via XDA Premium