|
LastInLine posted:Talk works? It's specifically the Talk service that changes the indicators blue. If by Talk you mean Hangouts  then yes it also is working fine. Which is why I'm so confused!
|
#
?
Jun 30, 2013 03:51
|
|
|
|
| # ? May 16, 2024 09:06 |
|
|
SeaborneClink posted:If by Talk you mean Hangouts
|
|
#
?
Jun 30, 2013 04:36
|
|
|
LastInLine posted:Actually by Talk I mean the GTalk service which controls c2dm. I would imagine Hangouts uses the same service but I wouldn't know as Hangouts are unusable garbage. If you're running a CM-based ROM you might have the GTalk Service Monitor in the Developer Tools where you can verify the connection. It says it's connected, but the packet status says it hasn't sent or received poo poo. 
|
|
#
?
Jun 30, 2013 08:15
|
|
|
SeaborneClink posted:It says it's connected, but the packet status says it hasn't sent or received poo poo.
|
|
#
?
Jul 1, 2013 00:21
|
|
|
HTC One Settings Menu posted:Kernel version This might be a silly question, but does this mean my phone is rooted? After some googling, the kernel revision number matched up to a third party kernel (Bulletproof.) I just bought this phone from AT&T not even a month ago, and I definitely didn't make any attempt to root the phone yet. Edit: I don't seem to have root/su access, but does this still mean that someone rooted it, returned it, and AT&T and/or HTC relocked it with a custom kernel in place? enojy fucked around with this message at 10:01 on Jul 1, 2013 |
|
#
?
Jul 1, 2013 07:44
|
|
|
Protocol7 posted:I know I took the gamble when I flashed it, but PA on my Note 2 is terrible. Halo is cool and all, but app syncing does not work. For any app. I've already tried the obvious solutions and a few not-so-obvious. I haven't had any problems with the Carbon Rom or Slimbean on my Note. Maybe try one of them?
|
|
#
?
Jul 1, 2013 09:23
|
|
|
enojy posted:This might be a silly question, but does this mean my phone is rooted? After some googling, the kernel revision number matched up to a third party kernel (Bulletproof.) I just bought this phone from AT&T not even a month ago, and I definitely didn't make any attempt to root the phone yet. quote:root@abm001 #1 That is just the user and server for which your kernel was compiled. More than likely, if you haven't rooted and you don't have a custom ROM, you probably are not rooted. I would suggest abm001 is the Android Build Machine 001 server within HTC. Boner Wad fucked around with this message at 15:34 on Jul 1, 2013 |
|
#
?
Jul 1, 2013 15:31
|
|
|
Alan_Shore posted:I haven't had any problems with the Carbon Rom or Slimbean on my Note. Maybe try one of them? I just went back to Jelly Beans build 18 and everything works flawlessly again. I'll just wait for people to develop ROMs for TouchWiz base 4.2.2, whenever Samsung releases that.
|
|
#
?
Jul 1, 2013 15:42
|
|
|
My wifes captivate is running SlimJB (4.1.2) and she's not happy with the battery life. Anyone know if it would get better battery life running CM9 (ICS) instead?
|
|
#
?
Jul 1, 2013 16:51
|
|
|
Ashex posted:My wifes captivate is running SlimJB (4.1.2) and she's not happy with the battery life. Anyone know if it would get better battery life running CM9 (ICS) instead? As a general rule you aren't going to get the greatest battery life unless you're on a Touchwiz-based firmware. Of course, this comes with trade-offs.
|
|
#
?
Jul 1, 2013 17:02
|
|
|
LastInLine posted:At least we know the problem now. If you hit the Reconnect option in the ⋮ menu does it fix it? Nope but rebooting again did!
|
|
#
?
Jul 1, 2013 17:22
|
|
|
ScarletBrother posted:I'm running CM 10.1 Stable on my Nexus 4 currently. The battery life is poo poo. What are some ROMs with good battery life? I'd like to be able to go 24 hours without having to plug in ideally. Thanks in advance. Anyone?
|
|
#
?
Jul 1, 2013 18:01
|
|
|
nimper posted:As a general rule you aren't going to get the greatest battery life unless you're on a Touchwiz-based firmware. Of course, this comes with trade-offs. Interesting, I was under the impression it was the other way around. In that case, will I get better battery life with CM9? Using a stock rom on the Captivate is a minor PITA.
|
|
#
?
Jul 1, 2013 18:17
|
|
|
10.1 works fine on the captivate, is there a reason you're intentionally sticking with 9?
|
|
#
?
Jul 1, 2013 19:03
|
|
|
Ashex posted:Interesting, I was under the impression it was the other way around. In that case, will I get better battery life with CM9? Battery life is impacted by several factors. How you use the phone and the reception in your area will impact battery life most significantly, however. So if you have crappy signal and/or send a billion texts per day, the phone won't last very long.
|
|
#
?
Jul 1, 2013 19:12
|
|
|
SeaborneClink posted:10.1 works fine on the captivate, is there a reason you're intentionally sticking with 9? Primarily for performance, when I was using the Captivate I noticed it didn't run as smoothly with JB. I figure it'll run better with ICS. nimper posted:Battery life is impacted by several factors. How you use the phone and the reception in your area will impact battery life most significantly, however. So if you have crappy signal and/or send a billion texts per day, the phone won't last very long. The fun part is my wife doesn't have a data plan, she uses it purely on WiFi and rarely makes phone calls on it. She primarily uses it for Skype/Viber calls, WhatsApp, and Facebook.
|
|
#
?
Jul 1, 2013 20:26
|
|
|
ScarletBrother posted:Anyone? Having said that, 24 hours on a N4 is a bit optimistic if you actually plan to use it for something.
|
|
#
?
Jul 1, 2013 21:29
|
|
|
Tunga posted:Use BetterBatteryStats to find out what is killing your battery. ROMs generally do not determine battery life (although custom kernels can make a difference). It's probably some dumb app. "suspend_backoff", "msm_hsic_host", and "PowerManagerService" are the big three offenders on kernel wakelock. Any clue what these are? Is kernel wakelock even what I should be looking at? Thanks for the reply, btw.
|
|
#
?
Jul 1, 2013 21:53
|
|
|
ScarletBrother posted:"suspend_backoff", "msm_hsic_host", and "PowerManagerService" are the big three offenders on kernel wakelock. Any clue what these are? Is kernel wakelock even what I should be looking at? Thanks for the reply, btw.
|
|
#
?
Jul 1, 2013 22:01
|
|
|
Mostly as above. You can try Franco kernel, it has some fixes for those issues but they don't work for everyone.
|
|
#
?
Jul 1, 2013 22:42
|
|
|
I don't know if this is any better place to ask than any loving where else on the Web, but does anybody, anywhere, know of a fix for wifi tether on a Galaxy Note 2 with an AOSP rom and kernel? XDA's brilliant policies prevent me from taking the issue up with anyone remotely intelligent there.
|
|
#
?
Jul 2, 2013 01:12
|
|
|
ArcMage posted:I don't know if this is any better place to ask than any loving where else on the Web, but does anybody, anywhere, know of a fix for wifi tether on a Galaxy Note 2 with an AOSP rom and kernel? I didn't even know there was an issue, personally. CM10.1 wifi tethering on my AT&T Note 2 works fine for me. Edit : in similar news : For anyone on the fence about CM10.1 being good enough for a daily driver, as of the 6/30 nightly, it is. I had been holding out until horrid bluetooth issues were solved, and it seems they were. Nerdrock fucked around with this message at 01:47 on Jul 2, 2013 |
|
#
?
Jul 2, 2013 01:44
|
|
|
Nerdrock posted:I didn't even know there was an issue, personally. CM10.1 wifi tethering on my AT&T Note 2 works fine for me. That's good news already, then. I've been thoroughly enjoying both carbon rom and matrix/plasma kernel, but I have found zero working configs for wifi tether. What are you using, please? Version and settings and things.
|
|
#
?
Jul 2, 2013 02:46
|
|
|
I'm one of the losers who updated his d2vzw to CM 10.1.0.1 without checking to make sure the "stable" update wouldn't render his phone useless... Has anyone successfully fixed the no mobile data, no phone calls issue without having to flash all the way back to stock? Will flashing 10.1.0.2 be a waste of my time?
|
|
#
?
Jul 2, 2013 03:01
|
|
|
ArcMage posted:That's good news already, then. I've been thoroughly enjoying both carbon rom and matrix/plasma kernel, but I have found zero working configs for wifi tether. I came from CleanROM ACE 4.9 , but it's just the CM10.1 6/30 nightly from here, and the included kernel. Edit : Kernetl 3.0.64-CM-g31f128d , and no special tools for the hotspot, just the feature built in to the system. (One thing that bums me out about the stock wifi hotspot system compared to TouchWiz roms is that you can't hide your SSID). Nerdrock fucked around with this message at 13:19 on Jul 2, 2013 |
|
#
?
Jul 2, 2013 12:56
|
|
|
Nerdrock posted:I came from CleanROM ACE 4.9 , but it's just the CM10.1 6/30 nightly from here, and the included kernel. My native hotspot fails entirely to start, but I'm on Carbon nighties and Plasma, so I am expecting to chalk it up to some combo of rom, kernel, and carrier. Oh well. Gonna buy into a proper dedicated device anyways, most likely. Thanks much!
|
|
#
?
Jul 2, 2013 15:53
|
|
|
So, I was a dumbshit and accidentally accepted an over-the-air update on my rooted Verizon Galaxy S3, and I'm getting the yellow triangle of death when I try to enter recovery, along with red text in the upper left saying - Secure Fail: Kernel. What do I do from here, or am I straight-up bricked? Edit 1: I can get into Odin mode! (Home button, volume down, power - wait for it to vibrate once, release power but keep holding the other two buttons.) Edit 2: Flashed the VRBLK_3 bootchain, and it got me up and running again. Edit: FIXED, so nevermind. Harettazetta fucked around with this message at 16:52 on Jul 2, 2013 |
|
#
?
Jul 2, 2013 16:27
|
|
|
Mogomra posted:Will flashing 10.1.0.2 be a waste of my time?
|
|
#
?
Jul 2, 2013 17:34
|
|
|
I decided to take the plunge yesterday and after much pulling of hair got my USC Galaxy S3 flashed to CM 10.1. Really I just couldn't stand the Samsung apps, but the stable version of 10.1 breaks the camera for some reason. I read that the nightly builds fix this but I worry about flashing a nightly and losing something more important then my camera. Maybe CM isn't even the way to go, I've been reading about all the different roms I can get but I really don't even know where to start. What rom do the S3 users around here prefer?
|
|
#
?
Jul 3, 2013 16:54
|
|
|
Mogomra posted:It certainly was a waste of time! Surprisingly, flashing back to stock wasn't necessary. I flashed plain old 10.1, no .0.1 or .0.2, and mobile data works. What a mess. CM's G+ post explains the problems, and 10.1.0.3 should have it all sorted out: https://plus.google.com/u/0/+CyanogenMod/posts/3WRFRuWgPWd This may also address USC issues? I'm not sure.
|
|
#
?
Jul 3, 2013 16:58
|
|
|
FuzzyPickles posted:I read that the nightly builds fix this but I worry about flashing a nightly and losing something more important then my camera.
|
|
#
?
Jul 3, 2013 18:20
|
|
|
FuzzyPickles posted:I decided to take the plunge yesterday and after much pulling of hair got my USC Galaxy S3 flashed to CM 10.1. Really I just couldn't stand the Samsung apps, but the stable version of 10.1 breaks the camera for some reason. I read that the nightly builds fix this but I worry about flashing a nightly and losing something more important then my camera. Japanese quad-core SC3 here, I use CM10.1, one of the older nightlies. It works perfectly for me now though I had to flash twice since the first time hosed up my actual phone functionality somehow and I never realized it -- it was never ringing or notifying me that I had incoming calls.
|
|
#
?
Jul 3, 2013 20:43
|
|
|
After a little messing around I noticed the SMS issue and I wasn't getting audio on notifications so I updated to the nightly from Sunday and it fixed all issues. Thanks guys.
|
|
#
?
Jul 3, 2013 23:24
|
|
|
Alarbus posted:CM's G+ post explains the problems, and 10.1.0.3 should have it all sorted out: https://plus.google.com/u/0/+CyanogenMod/posts/3WRFRuWgPWd And it looks like 10.1.0.3 has issues with stereo audio not working. Good grief.
|
|
#
?
Jul 4, 2013 02:32
|
|
|
Honestly the 10.1 RCs went on for far too long. And stable doesn't really make a whole lot of sense for actively-changing devices where folks keep finding new bugs and fixing them. The M-series makes more sense here. It's basically "wait a few days for recent changes to settle down, release, then push forward" and, ironically, ends up being less buggy that way.
ExcessBLarg! fucked around with this message at 03:50 on Jul 4, 2013 |
|
#
?
Jul 4, 2013 03:48
|
|
|
Protocol7 posted:I know I took the gamble when I flashed it, but PA on my Note 2 is terrible. Halo is cool and all, but app syncing does not work. For any app. I've already tried the obvious solutions and a few not-so-obvious. What do you mean app syncing? PA on my nexus 4 is amazing but it's an aosp-based rom running on a nexus device so of course its gonna be stable and work right. Also Halo is polished and impressive but really only cool cause its facebook messenger heads for not facebook
|
|
#
?
Jul 4, 2013 20:35
|
|
|
nigga crab pollock posted:What do you mean app syncing? Emails would not sync. I had to check for app updates manually. That kind of stuff.
|
|
#
?
Jul 4, 2013 20:37
|
|
|
Has anyone else with a Nexus 4 tried out the CM nightly for today? SystemUI just continually crashed for me. Edit: just checked on the G+ community, and it looks like it's a known issue.
|
|
#
?
Jul 4, 2013 21:40
|
|
|
Alarbus posted:CM's G+ post explains the problems, and 10.1.0.3 should have it all sorted out: https://plus.google.com/u/0/+CyanogenMod/posts/3WRFRuWgPWd Yep, I'm on .0.3 now too. I just noticed my phone will only output the right channel of any audio through the headphone jack now.  I know it's not my headphones, I hope it's a software issue, and my phone isn't mysteriously falling apart like my Nexus 7...
|
|
#
?
Jul 5, 2013 04:21
|
|
|
|
| # ? May 16, 2024 09:06 |
|
|
Mogomra posted:I just noticed my phone will only output the right channel of any audio through the headphone jack now. Maybe wait until tomorrow.
|
|
#
?
Jul 5, 2013 04:23
|
|