yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Themes and Apps] ThaiM:
Can't find on Samsung Apps. WTF.

Also, Samsung Apps market honks the big one. Jeebus.
[Galaxy S II Themes and Apps] dubart:
I have to wait like 20 minutes for an activation code to arrive via SMS and it's always invalid :confused:
[Galaxy S II Themes and Apps] lynx2k50:
Here you go:

https://market.android.com/details?id=com.sec.chaton
[Galaxy S II Themes and Apps] Alpha Trion:
:( mine arrived within seconds & worked straight away. Interface seems quite clean, very much like Viber in set out.
[Galaxy S II Themes and Apps] Denny966:
hmm. i've waited like 10 mins now for the activation code
[Galaxy S II Themes and Apps] adam1460:
Be patient guys, the servers must be overloading.. which must mean loads of people must be waiting to use this awesome service :D
[Galaxy S II Themes and Apps] nitishthelegendkiller:
Been waiting for an hour now. Weird.
[Galaxy S II Themes and Apps] groaner:
Yes, as always Canada is the red-headed stepchild left to play in the cupboard under the stairs.

If anyone has the APK would you be so kind as to attach it here?
[Galaxy S II Themes and Apps] izzyq8:
If your phone is rooted why not use market enabler.

Do u really think they give two s**** about me in kuwait :)
[Galaxy S II Themes and Apps] groaner:
Not rooted, yet.
[Galaxy S II Themes and Apps] BdA2:
How can i install this app?
[Galaxy S II Themes and Apps] groaner:
I found it here

http://www.4shared.com/get/exrhMmp9/ChatON.html
[Galaxy S II Themes and Apps] BdA2:
Thanks but. Iam still waiting for activation number
[Galaxy S II Themes and Apps] ImWarped:
Damn, I AM a redheaded stepchild, and Canadian... ;)

http://www.mediafire.com/?c961h0h9ya68akx
[Galaxy S II Themes and Apps] elkikin:
Still waiting for the activation code... for 3 hours...
[Galaxy S II Themes and Apps] groaner:
LOL, Ooops.

**Disclaimer, To all REAL red-headed canadian step-children, this was not meant as a slight against you or your kind.

;)
[Galaxy S II Themes and Apps] gn00my:
Still waiting for activation code here also, from the netherlands
[Galaxy S II Themes and Apps] zkyevolved:
Waiting... waiting... waiting for the stupid activation code!! SPAIN!
[Galaxy S II Themes and Apps] ImWarped:
I think it's everyone... I highly doubt they planned for a flood of activations... And waiting for a text is painful, they should have set it up through email... oh well, he's hoping it lives up to hype!

Bear in mind, it still hasnt launched on other platforms yet.
[Galaxy S II Themes and Apps] BillSplate:
Personally I do not think that ChatOn is going to be a massive succes just like iMessage. WhatsApp has a lot of users in the world and is working 9 of the 10 times instantly. I don't think that current users of WhatsApp are going to switch because they have to pay 2 dollars for a year. WhatsApp is way to populair for that.

BTW, Samsung already had a app like this before right? Palringo. Pre-installed on their devices, but it sucked I guess, since nobody used it and WhatsApp is more populair.
[Galaxy S II Themes and Apps] j1po:
I tried it, and receive verification sms less than 1 minutes

I live on indonesia, maybe you can try my apk : http://db.tt/1rjHHBEj

my friends who download this apk can receive verification sms shortly

The new feature I like that not implemented on other messaging like WA/Kakao

- Group contact, more neat contact, easy to broadcast or made a group chat

- Trunk , you can add comment to media sharing

- also animation message, its cool

But this application a bit laggy, 9MB app size and 28MB RAM usage

not bad for first release <3 it

sorry my bad english :(
[Galaxy S II Themes and Apps] blossom:
Code came in instanly

Less than a minute

Great potential with this app

Smooth and nice inteface
[Galaxy S II Themes and Apps] Galactus:
looks smooth enought but dont no a single person whos using this lol
[Galaxy S II Themes and Apps] Coedy:
WhatsApp rapes the battery, lets hope ChatON isnt the same...
[Galaxy S II Themes and Apps] zkyevolved:
After hours of having it working, it needs a lot of work. Capitalization after full stop doesn't work. Font size in the text writing area is too small compared to the other fonts. I don't like that it's the whole "phone number" thing again. I wouldn't mind a version of BBM for Android because having a pin associated to you is much better than having people have your personal number all the time. I miss the anonymousness of BBM.
[Galaxy S II Themes and Apps] nikzDHD:
Argh can't get no verification code still,my sister got hers instantly. So far seems cool judging it on her phone potential to be good once they multi platform it but still if Rim are smart they would do the right thing and release bbm as a multi platform app which has the potential to dominate. I know its exclusive and it keeps users to the berries but it can be huge.
[Galaxy S II Themes and Apps] tlove_7969:
I uninstalled it twice yesterday and still no code so I emailed the dev. And uninstalled it. Then I tried it this morning and it worked I received my code right away. Now my only concern is that my friends might not get their code and I wont have no use for this.
[Galaxy S II Themes and Apps] elkikin:
After more than 24 hours, I'm still waiting for the code here in Portugal. I tried reinstalling it, but nothing happens...
[Galaxy S II Themes and Apps] c3l5o:
I too can't get a validation code in Portugal.
[Galaxy S II Themes and Apps] giga502:
I got my verification here in Australia.

Yet. I don't know anyone who has it xD
[Galaxy S II Themes and Apps] Alain024:
i tried to get a code 2 days back and didint work now its working i got it instantly :D, Costa Rica!
[Galaxy S II Themes and Apps] Nyssa1104:
Well since this app has only just come out no wonder!

Dutch handset got my code within 30seconds in Wales where lm on a visit. App looks good sobfar just need more of my contacts using this. Yes a personally pin would of been better than using ones phone number but hey.
[Galaxy S II Themes and Apps] dubart:
This app needs delivery reports, like WhatsApp and others have.

Sent from my GT-I9100
[Galaxy S II Themes and Apps] gn00my:
i finally got my verification code yesterday here in holland , after 1 day waiting
[Galaxy S II Themes and Apps] androidkid311:
Looks nice... not 1 of my friends has it though lol :-/.

Sent from my iphone look a like powered by android!
[Galaxy S II Themes and Apps] j1po:
delivery report already implemented, it show as number beside the message, (1) = if you 1:1 chat

the number disappear when message read

or if in group chat, you can see (x) ; x=number of people who unread the message

if the message failed to send, you can see 2 icons, resend or delete
[Galaxy S II Themes and Apps] LordLugard:
Got my code after trying for a day. Sent an invite to my sis in the U.K, she installed and we tried it out. Worked just fine. She kept thinking it should have some calling feature built-in (like Viber). She always wants to "talk" on the phone, I'm the opposite, prefer written communication.

Haven't tried multimedia transfers yet... but impressive so far.

Sent from my SPH-D710
[Galaxy S II Themes and Apps] BuzzFuzz:
Still no activation code. Damn, now running sixth day....
[Galaxy S II Themes and Apps] valenrock:
kind of weird happen to me..i try to install it from 2 different provider. first one gave me less than a miinute to get the code,then i try from second one, its been 2 days waiting for the code...

so i think its a provider matters...Just for information,im from indonesia....
[Galaxy S II Themes and Apps] frakki:
got my code within 3mins or so (o2 Germany) But ive always get an FC when trying to do an animation message!
[Galaxy S II Themes and Apps] btrav:
anyone have any idea when this is going to actually be cross platform?
[Galaxy S II Themes and Apps] j1po:
Just released for iOS device

you can get it on itunes store
[Galaxy S II Themes and Apps] rioferraz:
Never got the confirmation code for me!

I from Brazil, and the code of Brazil is 55. My phone number is 21 (city code) 9111-xxxx. The final number is +55219111xxxx and never get the code = /.
[Galaxy S II Themes and Apps] pSyCh¤_O_O:
Whats the max upload size for videos and pictures?
[Galaxy S II Themes and Apps] XDA_Mod:
I can not deal with this.

I want to receive the verification number but I don't know which is the structure of that number.

It says country and I think that choosing that it the same as writting your +(country number) so when it asks about the number of the mobile that I should be writting ... how shall I complete that GAP?
[Galaxy S II Themes and Apps] norberto877:
now you can go to the website to do the verification. Give it a try.
[Galaxy S II Themes and Apps] fferreyros:
Not really, i was trying to get the code since day 1 of ChatOn, today I tried using ChatOn via Web Browser, I can logon using Samsung account and add contacts manually using their phone numbers, but when i tried to Sync, it asks for my number and then i receive a msg saying: "Please install ChatON on your device first".

Now I'm like :eek: (of course it is installed on my phone a long time ago, with several retries from time to time to get the code :()
[Galaxy S II Themes and Apps] king.316:
No issues at all got the verification sms before the 3 minutes time mentioned works like a charm
[Galaxy S II Themes and Apps] Red_Vex:
After insert verify code i insert name but after that got stuck in endless verifing. Any ideas?

Inviato dal mio GT-I9100
[Galaxy S II Themes and Apps] ruben21:
please help where i can find friens of this app please someone
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
I'll give this a shot and let you know how it works on my RHOD400.
[Touch Pro2, Tilt 2 Android Development] mgross029:
Thanks that would be appreciated...
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
What kernel are you using?

I like the effort, but I honestly don't see any difference to hyc's thread other than this tip:

Which I guess could be the key to getting it all to work? I'm just wondering if this step is required to get it all working properly.

Curious, does speakerphone work for you? Have you ever had audio "just die"?
[Touch Pro2, Tilt 2 Android Development] mgross029:
arrrghhh,

I agree it is very similar to what hyc is doing and that was why I put many references to his thread in my post. I also cleared creating the new thread with hyc before I posted. I did this mainly so this post would not get lost in the audio testing thread.

The main difference between this thread than hyc's is that his was in reference to getting BT to work on FRX06 and if you would follow the same procedures as posted there with FRX07 it essentially would not work and cause problems with the phones ability to operate. I found that putting the libhtc_acoustic.so file into FRX07 really made they system unstable.

My Speakerphone does work... Also, I have tried several combinations of items to see if what worked and what did not... I have lost audio in these tests, but so far with what I've posted using the XDAndroid version of FRX07 everything seems to work correctly for my Rhod500...

Thanks for the input / feedback...

Edit: Sorry missed your first question... My specs are posted in my sig... Currently I am running StarFox's 8/20 Test Kernel...
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Starfox's test kernel supports the new audio routing...? I'm running his kernel without the new (userland) routing stuffs.
[Touch Pro2, Tilt 2 Android Development] detule:
Without JB's libhtc_acoustic, this thread is not in fact testing the "new" audio routing.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Oh, I guess I didn't realize that. Interesting... I ignorantly assumed that this was using the same audio routing from JB.
[Touch Pro2, Tilt 2 Android Development] mgross029:
Trust me I am not a developer nor do I play a developer on TV, but I did stay at a Holiday Inn Express before... :rolleyes:

All I know is by using the information I posted at the top of the thread I was able to get BT in-call audio routing correctly.

I have used the kernel StarFox had posted which was based off the mainline 1348 kernel and was able to get the BT audio routing to work correctly with that as well.

I put this as testing because I am not sure the result that everyone would have with this.

If anyone has been able to test it out I would appreciate if you could post back to let us know if it has worked correct or not...

Thanks...
[Touch Pro2, Tilt 2 Android Development] anish88:
Do you still get the static from the speakerphone when placing an outgoing phone call?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Why don't you try it and tell us...

I would assume so since it's not using the new libacoustic code, but I don't know for sure. It's a minor issue to me, flip speakerphone on/off and it's gone.
[Touch Pro2, Tilt 2 Android Development] mgross029:
Yes... Still some static, but not bad... Kind of a minor hisss.... :)

I left myself a VM on my work phone and I do not hear the hiss in the message... It is actually quite clear...
[Touch Pro2, Tilt 2 Android Development] anish88:
yeah thats the thing that I do too. ill wait too. everything else is working great though.
[Touch Pro2, Tilt 2 Android Development] Dinky:
Test results on Rhod300

Since this is about tests on your efforts, I think it's probably easier for everybody to follow just by moving my post from FRX07 thread to here.
[Touch Pro2, Tilt 2 Android Development] mgross029:
Thanks Dinky, for posting this over here so others can see your results...
[Touch Pro2, Tilt 2 Android Development] Dinky:
Did that. Went directly to BT tests without anything installed/set up after first boot. Exact same result. Earpiece will not reconnect once disconnect. I had to unpair/pair the earpiece again to get it connected again. Are these all working for you? I wonder what differences could it be besides the hardware?
[Touch Pro2, Tilt 2 Android Development] mgross029:
Occasionally, I have had issues where my headset will not automatically connect to my car and I usually will disable BT on the phone and re-enable and that does the trick. Another item to look into is which BT headset are you using? The configuration for the hardware may not be in the database (CSV)... You could actually take some logs to see what the problem is...

If you have adb running do this...

C:\<directory where adb is located>\adb shell logcat -v time > logcat.txt

From a Terminal window:

logcat -v time > /sdcard/logcat.txt

Try to do your pairing while that is running after you are done with your testing Ctrl-C to break out of it and then go to your adb folder there should be the logcat.txt file... This should show what is happening or not happening when pairing or connecting...
[Touch Pro2, Tilt 2 Android Development] Dinky:
OK, did that. I saw some errors pertaining to the BT connection, but what do they mean is beyond me. It looks like there's a permission problem? I have that portion of the log attached below...
[Touch Pro2, Tilt 2 Android Development] mgross029:
Thanks for the log Dinky...

It looks like rfcomm is timing out before it can fully establish a connection to your BT headset... Which headset are you using? I don't think I remember seeing you post that... Sorry if you already did... I know I did some searching and saw some posts where some headsets do not connect as fast as others and that delay caused the connection to fail.

The only other thing I can think that I may have done that most may have not was to install the volume cab files from vzihomes thread. I know that helped with audio routing on my speaker even before I figured out the BT part. I used to boot into android with no sound and then after adding the cab files to WM audio routes through my speaker at first boot.

Just something to try... Not sure if it has anything do with what you are experiencing though...
[Touch Pro2, Tilt 2 Android Development] mgross029:
JB's libhtc_acoustic.so

Just out of curiosity and the fact of what Detule and arrrghhh were talking about with JB's new audio routing that was put in place in the libhtc_acoustic.so file. I opened it up in Notepad++... I found that the file was referenceing the .CSV files from WM and not the ones originally in FRX07 /system/etc. So for instance instead of looking for AudioPara4.csv (FRX07 orginal file) it was looking for AudioPara3.csv. Plus it was looking for the AudioPreProcessTable.csv and the AudioFilterTable.csv.

Now when ever I've tried to add JB's libhtc_acoustic.so to my system/etc folder and boot all things would work until any audio was played it would reboot my phone, so I'm sure there are other items which need to be corrected... I used to do some C programming about 20 years ago... :eek: Along with several other programming languages... I've looked for the source/changes JB made but couldn't seem to find it on gitorious...

If someone could point me to it I would be interested in parsing through to see if I can pick up anything of interest.

Thanks for everyones feedback so far... If anyone else has had success or failures I would like to know what has worked and what hasn't...
[Touch Pro2, Tilt 2 Android Development] Dinky:
Yes, I have both cabs installed at the WM side because that was what I found when I first digged into the BT problem. My earpiece is a Plantronics Discovery 975, and it was discovered as "9xxPlantronics" as shown in the .csv file. I did a little googling too, and it looks like if the problem is caused by timeout, the error will show something like

E/BT HSHFP( 1025): RFCOMM async connect() error: Unknown error: 0 (0), nr = 1

but the error in my log shows

08-29 13:27:25.730 E/BT HSHFP( 1430): RFCOMM async connect() error: Permission denied (13), nr = -1

And since pairing has no problem, I am not sure if it's connection timeout issue. But I'll look around to see if I can get my hand on another earpiece to try out.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
https://gitorious.org/~jbruneaux/

That's JB's gitorious page...

https://gitorious.org/~jbruneaux/li...-home-work/commits/htc-msm-2.6.27-libacoustic

^^ Specifically the libacoustic repo.
[Touch Pro2, Tilt 2 Android Development] mgross029:
Thanks arrrghhh... Much appreciated...
[Touch Pro2, Tilt 2 Android Development] Dinky:
OK, good news. I got a hold of a Samsung WEP200 earpiece, and it tested out fine. Disconnect/reconnect is good. Dial-in/dial-out BT routing is correct. It looks like it might be a earpiece connection timeout issue after all.

I googled a bit, and somebody mentioned of changing the timeout in

packages/apps/Phone/src/com/android/phone/BluetoothHeadsetService.java

from

result = headset.waitForAsyncConnect(500, mConnectedStatusHandler);

to

result = headset.waitForAsyncConnect(1000, mConnectedStatusHandler);

This is beyond me again. I don't even know where the program is located. Here's the original link talking about it:

http://www.mail-archive.com/android-porting@googlegroups.com/msg13870.html

If somebody can make the change for me or point me to the right direction, I might be able to do some experiment again. Thanks.
[Touch Pro2, Tilt 2 Android Development] AkumaX:
sounds like you need to edit the source code for the phone.apk
[Touch Pro2, Tilt 2 Android Development] rpierce99:
You'd have to make that change in the android sources (http://xdandroid.com/wiki/Getting_the_Source) and compile your own system image to test that. Yay google for putting settings that could potentially need changed directly into your source code! That's what settings xml files are for!
[Touch Pro2, Tilt 2 Android Development] Dinky:
Well, I am not a chef, so I am not in the position to compile my own system image, at least not right now. But, the good thing is, now we know exactly what we need to fix the BT routing problem. Hopefully the great almighty chef(s) will include the fix in next release.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
You seem pretty confident without testing the change at all.

How do you know it even works?

I could probably make this change and build a system image, but it hardly seems worth it. I don't see how this "fix" is "fixing" anything related to BT audio routing. It only adjusts timing, so perhaps some headsets will have an easier time connecting? I'm not exactly sure the gravity of the change you are suggesting.
[Touch Pro2, Tilt 2 Android Development] Dinky:
Oh, I don't think this addresses the BT routing problem, it only "might" fix the problem of reconnecting for my Plantronic Discovery 975 earpiece, or maybe some other earpieces out there. But without this, mgross029's "one-stop" collection seems to fix the BT routing issue. Even though he just "re-collected" others' findings/fixes, but I have to give him credit because his collection definitely helps people like me to address the BT routing problem. I've searched for the fix for a while but there are a lot of discussions out there and each points to different directions. Me as a non-programmer really had a hard time to follow all those threads.

As I stated in your thread, I really like this build and it seems to be stable enough for daily use. But without BT working, I can't use it because I am often on the road and the state law requires hand-free device for cell phone while driving. That's why I'm so eager to have the problem fixed so I can use it daily to see if it is really stable enough (I saw a lot of posts mentioning self-rebooting intermittently). There. arrrghhh, thank you for bringing this bundle to us, and mgross029, thank you for putting the fix together, and of course, thanks for the people whom you "steal" the idea from. ;)
[Touch Pro2, Tilt 2 Android Development] mgross029:
I myself am not a developer either... I have done some Assembler, C, Cobol, RPG, Basic (non-visual) :) , VB, VBA and VBS... But not to the calibler of what some of these dev's have done and most of it was about 20 years ago...

I was just hoping with this thread to get the wheels turning again for BT and audio routing... I have broken this image many times to try out different things that others have put together, but so far with the help of HYC's Audio Routing Thread, some of arrrghhh speed improvement ideas over in this thread and using the ext4 partitioning that StarFox put in this thread with his new test kernels. And Detule with the new liblights which makes it look cool. :D This has truly become a daily usable functioning phone now. It get pretty good battery life too...

Dinky I did find that post about the .java modification which as stated would only fix those headsets that need the extra delay... Here is a link to the code, but as arrrghh stated is it really worth it for the few headsets this may fix. Maybe when they get the other major bugs worked through. I am glad you were able to get another headset to work though. Thanks for all of the testing you did...

So my question to any others out there is, have you tried this to see if it works correctly for you? I would be really be interested to see others feedback as well... Thanks!
[Touch Pro2, Tilt 2 Android Development] Dinky:
Yes, that's the impression I got. It just addresses the delayed connection for some BT headsets/earpieces. The problem is, without this fix ("maybe"), I can't use my Plantronics earpiece. I just borrowed the Samsung earpiece from others. That is, if I have to buy another earpiece to work with current timeout setting, I am bumping into the same problem - which earpiece does not have the connection delay like the Plantronics (the Samsung WEP200 doesn't really fit in my ear)? Since it's just a timeout setting for waiting the BT device to connect, I don't expect it to break anything (well, maybe I'm too naive since I'm really not qualified to make that claim).

I thought our purpose of having this forum is to help each other out to make the amazing happens on our devices. I was just hoping that somebody with the expertise can kindly make the modification, so other people will not suffer the same issue while a plausible work-around, if not the final solution, for BT routing issue is already in place. I would imagine that there are already good number of states require hand-free devices for cell phone while driving?

Just my 2 cents. Thanks.