Anyone using this app on Android experiencing major battery drain?
I am using a Nexus S, flashed with the latest CM9 Nightly build. The app drains 15% of my battery life even when I only occasionally use it. I can't uninstall it cause its the only chat app that some of my friends use.
I have emailed the developer about this issue about 6 months ago, but they still havent addressed it. Is there anything else I can do?
No one uses Kakaotalk here on JB or ICS?
AsianXL said:
No one uses Kakaotalk here on JB or ICS?
Click to expand...
Click to collapse
I am also using it on the Galaxy Nexus GSM running Jelly Bean ROM 4.1.1 it does not matter what ROM I use I cannot connect to Kakaotalk server. I always get the symbol that says I am connected but as soon as I try and send someone a messege than it says that it is not connected....It only does this when I am connected to WiFi when when I connect to 2g or 3g it works just fine. I am using Kakaotalk 3.3.3 and I have emaied Kakaotalk about the issue and they told me that they dont have support for ICS or Jelly Bean right now. There is no timeline when they will start to support the 4.0+ ROMS. I have started to use Whatsapp as an alt until they fix it. If anyone else figures this out please let me know thanks.
kt
kkt is way cool
post your ID to meet up !
AsianXL said:
No one uses Kakaotalk here on JB or ICS?
Click to expand...
Click to collapse
I do.
no prob with jb here. 4.2.1 jb
Related
Is there a page that lists the known issues with the official CM10 nightlies on our GS3? I'm running it and haven't run into anything. Considering using it as my daily, but want to know what I might run into. Also, is there any Jelly Bean ROM that is 100% stable for our GS3's yet?
I just read you can sometimes follow the developer, does anyone know who that might be?
docdockstader said:
Is there a page that lists the known issues with the official CM10 nightlies on our GS3? I'm running it and haven't run into anything. Considering using it as my daily, but want to know what I might run into. Also, is there any Jelly Bean ROM that is 100% stable for our GS3's yet?
Click to expand...
Click to collapse
I can tell you that the 8/25 nightly breaks the dialer. 8/23 was working quite nicely, though. Only thing that was flaky for me was the bluetooth stopped auto connecting in my car.
http://code.google.com/p/d2vzw-cm10-bugs/issues/list?q=label:Priority-Medium
docdockstader said:
Is there a page that lists the known issues with the official CM10 nightlies on our GS3? I'm running it and haven't run into anything. Considering using it as my daily, but want to know what I might run into. Also, is there any Jelly Bean ROM that is 100% stable for our GS3's yet?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1840414
Some informal tracking is going on in ^this thread.
Official/Nightly CM10 is still suffering from occasional screen flicker (never did get that one resolved on MY phone) and the odd hot reboot now and again. Tell you what though... It was a lot smoother than ICS.
Unfortunately the S3 is my daily driver so I'm back on SynergyROM for the moment.
Back to Synergy 1.7 R50 & Theme DarkHorse v2.1
noobabuser said:
http://forum.xda-developers.com/showthread.php?t=1840414
Some informal tracking is going on in ^this thread.
Official/Nightly CM10 is still suffering from occasional screen flicker (never did get that one resolved on MY phone) and the odd hot reboot now and again. Tell you what though... It was a lot smoother than ICS.
Unfortunately the S3 is my daily driver so I'm back on SynergyROM for the moment.
Click to expand...
Click to collapse
Have had jb unofficial & official roms loaded this week and still
for me not a daily driver. Nice work and canot wait to use jb
as daily. Aug 29 I think they release jb international and will see
how long it takes to see the new roms & themes hopefully. Until
then spoiled on the Synergy 1.7 r50 & theme DarkHorsev2.1
dingurt said:
I can tell you that the 8/25 nightly breaks the dialer. 8/23 was working quite nicely, though. Only thing that was flaky for me was the bluetooth stopped auto connecting in my car.
Click to expand...
Click to collapse
Now that your mention it, this has been happening for me too. My Sync in my Ford can't find it and I have to toggle the bluetooth on my phone so it sees it again. I can live with it for now. I am just happy they have the boot loader unlocked now.
First, with only one bar, I can't access the play store, etc etc. Nothing with network. Gmail is not synching at all. No notifications etc.
Everything was working previously. My other verizon GS3 which is totally stock is working as it should, so this is an issue with the rom, kernel or combo.
Are these known issues?
Everyone says they run the AOKP and LeanKernel and it's the best combo for the verizon gs3.
Did you install the 3g fix? I cant even use aokp because of wifi issues so i feel your pain.
fix-this! said:
Did you install the 3g fix? I cant even use aokp because of wifi issues so i feel your pain.
Click to expand...
Click to collapse
Never heard of the 3g fix. Link?
Im mobile but its on rootzwiki. The verizon gs3 section under the official aokp thread.
I was wondering if anyone is using Heytell with Jelly Bean? Heytell is one of the cleanest and simplest walkie talkie apps, and I rely on it a fair bit.
Every since I upgraded to Jelly Bean (CleanRom 5.5.1), Heytell is behaving oddly. I can send or receive 1 message, and the rest of the message will be stuck and won't download or send. I have to kill the Heytell app, before I can receive the next message. If I have 2 messages waiting, then I have to kill heytell again, before the 2nd message will download.
Once I restore my phone back to ICS, heytell is back to normal.
It's possible that this is just an odd behavior on my phone, so I was wondering if anyone else has experienced this on Jelly Bean.
I had that EXACT problem with CleanRom 5.5.1! Did the exact same thing for a solution too.
Eventually, I moved to my preferred rom of euroskank and HeyTell functions as normal.
But as least we know it wasn't an isolated case...
oilfighter said:
I was wondering if anyone is using Heytell with Jelly Bean? Heytell is one of the cleanest and simplest walkie talkie apps, and I rely on it a fair bit.
Every since I upgraded to Jelly Bean (CleanRom 5.5.1), Heytell is behaving oddly. I can send or receive 1 message, and the rest of the message will be stuck and won't download or send. I have to kill the Heytell app, before I can receive the next message. If I have 2 messages waiting, then I have to kill heytell again, before the 2nd message will download.
Once I restore my phone back to ICS, heytell is back to normal.
It's possible that this is just an odd behavior on my phone, so I was wondering if anyone else has experienced this on Jelly Bean.
Click to expand...
Click to collapse
I'd guess the app isn't fully compatible/updated to work with jelly bean yet..
Sent from my SCH-I535 using xda app-developers app
InfamousDX said:
I had that EXACT problem with CleanRom 5.5.1! Did the exact same thing for a solution too.
Eventually, I moved to my preferred rom of euroskank and HeyTell functions as normal.
But as least we know it wasn't an isolated case...
Click to expand...
Click to collapse
HA, thank you for your feedback! I knew I wasn't crazy.
Is euroskank Jelly Bean?
oilfighter said:
HA, thank you for your feedback! I knew I wasn't crazy.
Is euroskank Jelly Bean?
Click to expand...
Click to collapse
Yes, it's based off of CM 10.1 with cherry picked features that aren't officially merged into CM yet.. It's the bleeding edge.
Sent from my SCH-I535 using xda app-developers app
I and anyone I know with an S3 have this exact same issue with Heytell as well. Doenst seem like Voxillate is doing anything about it as their responses to support requests are they will send it to the engineers. Not sure if it is jellybean only as one friend has the original stock ATT ICS rom and it hangs for him as well. Very annoying...
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Hi All,
On my Verizon Samsung Galaxy S3 I cannot get anyone to hear me when I do a Video Call with the new Google Hangouts...
Anyone else have this issue or a Solution?
adrianvfx said:
Hi All,
On my Verizon Samsung Galaxy S3 I cannot get anyone to hear me when I do a Video Call with the new Google Hangouts...
Anyone else have this issue or a Solution?
Click to expand...
Click to collapse
Identical problem here, s3, d2tmo, 10.1 stable
My girl had that problem she just fix it by adjusting the settings
clean Rom/xda powerd by zero-lemon & tweaked out!!
Hulk0069 said:
My girl had that problem she just fix it by adjusting the settings
clean Rom/xda powerd by zero-lemon & tweaked out!!
Click to expand...
Click to collapse
I've looked at all the settings, which ones did she adjust?
bump.....
Let us know!
I want this issue narrowed down. Let's please post current rom that the bug is present on, any rom that it is working on, and any possible fixes (other than adjusting settings!?! ).
So far I've read reports throughout the aosp threads that the audio is broken on the receiving side of the call (the person you called cannot hear you, but you can hear them). This is known to be the case on liquid, carbon, and rootbox.
I'm currently running liquid 2.4 and can confirm the bug is present. I currently do not have a fix, nor have I heard of one.
Sent from my Nexus 7 using Tapatalk HD
annoyingduck said:
I want this issue narrowed down. Let's please post current rom that the bug is present on, any rom that it is working on, and any possible fixes (other than adjusting settings!?! ).
So far I've read reports throughout the aosp threads that the audio is broken on the receiving side of the call (the person you called cannot hear you, but you can hear them). This is known to be the case on liquid, carbon, and rootbox.
I'm currently running liquid 2.4 and can confirm the bug is present. I currently do not have a fix, nor have I heard of one.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I was using Liquid Rom as well!
I read somewhere(cannot remmber where) but any AOSP based ROM will not work.
Currently only Touchwiz(TW) Roms work.
So I had to flash a TW Rom, and confirms it works!
Anyone else have a working AOSP ROM?
adrianvfx said:
I was using Liquid Rom as well!
I read somewhere(cannot remmber where) but any AOSP based ROM will not work.
Currently only Touchwiz(TW) Roms work.
So I had to flash a TW Rom, and confirms it works!
Anyone else have a working AOSP ROM?
Click to expand...
Click to collapse
That's good info, I had no idea it was working on tw. I would assume by this point then that the big gun devs in aosp are aware of this, and hopefully are working on a fix...?
Sent from my Nexus 7 using Tapatalk HD
Using omega rom v44.4 jb 4.2.1
Tried hangouts with no issues,just hoping for updates like making the vid interchangeable not the switching of front back cam but the layout on set of video calk and make it adjustable.
But everything else is awesome..lovin it
Sent from my GT-I9300 using xda premium
JDroid Freak said:
Using omega rom v44.4 jb 4.2.1
Tried hangouts with no issues,just hoping for updates like making the vid interchangeable not the switching of front back cam but the layout on set of video calk and make it adjustable.
But everything else is awesome..lovin it
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
This is the Verizon s3 section, your running the international.
annoyingduck said:
This is the Verizon s3 section, your running the international.
Click to expand...
Click to collapse
Even if he is running INIT. It should be fine. The problem is universal for all S3's it seems...
I really hope someone knows of a fix!
adrianvfx said:
Even if he is running INIT. It should be fine. The problem is universal for all S3's it seems...
I really hope someone knows of a fix!
Click to expand...
Click to collapse
Again, great info. Didn't know it was across the board on all S3's.
Same problem here, both myself and my friend are having problems on our rooted AT&T SIII's running custom roms
I am running RootBox Nightly 20130514 on Verizon S3. I was absolute that my girlfriend was doing something wrong when she kept telling me she couldn't hear me. Glad to see I was wrong and there is an actual issue. Has anyone seen a fix for this posted? I guess I could flash over to a TW ROM. I haven't had TW since my phone came out of the retail box...
Glad this issue is being reported and seen by many.
No fix still
I went ahead and put back TW. Using Cleanrom now. Google hangouts works just fine. BUT I miss 4.2.2 and AOSP
Same issue here, using LiquidRom 2.3.2 and KT747 5/9 kernel
Looks like this will be fixed in tomorrow morning's nightly.
Restola said:
Looks like this will be fixed in tomorrow morning's nightly.
Click to expand...
Click to collapse
This was fxed with liquid smooth?
Not yet
Sent from my Nexus 7 using Tapatalk HD
Slim bean build 6 changelog says they fixed the Hangouts issue (haven't had a chance to test myself yet).
vine working for anyone on our phone? I'm on AOKP 4.1.2 and the app gets stuck "initializing" when I try recording a video.
salmanj1 said:
vine working for anyone on our phone? I'm on AOKP 4.1.2 and the app gets stuck "initializing" when I try recording a video.
Click to expand...
Click to collapse
I've got a Vibrant running Rem-ICS JB 4.2.1 with the same issue.
Cannot get past the initializing message, despite being able to see the camera working in the background behind the popup.
Viruss57 said:
I've got a Vibrant running Rem-ICS JB 4.2.1 with the same issue.
Cannot get past the initializing message, despite being able to see the camera working in the background behind the popup.
Click to expand...
Click to collapse
Saw someone with an S2 having the same problem, even after this last update. Well, I guess we wait!
I have the same phone and am running AOKP ICS. Also having the same issue. Hoping this can be fixed soon or I'm going back to stock!
laurenlee653 said:
I have the same phone and am running AOKP ICS. Also having the same issue. Hoping this can be fixed soon or I'm going back to stock!
Click to expand...
Click to collapse
I doubt it's a kernel issue, other phones are having this problem too. Besides, Vine works on 4.0+ devices only so stock wouldn't work. I guess we just have to wait..
I have a Nexus S (pretty much same hardware) running CM10.1 and I as well have the same issue, still, after the update.
I'm having the exact same problems on my Razr HD running CM 10.1 and I just updated the app today. Hopefully it gers fixed soon.
Sent from my XT926 using Tapatalk 2