Database Users

Nexus S SMS bug still present with 2.3.3

The sms bug i'm talking about was supposed to have been fixed in 2.3.2 for the Nexus S, but, i have just experienced this supposedly fixed bug with 2.3.3, the bug is the one that sends a reply to a totaly different contact to the one that the reply was intened for, for instance, today i replied to an sms from a contact from within a messange thread but the reply was sent to a totaly different contact.
Anyone else experienced this "supposedly" fixed bug with 2.3.3.

I've never experienced it on 2.3.3. But, I never had it on 2.3.2 either.
Sent from my Nexus S using XDA Premium App

get GO SMS.. it fixed it within the app for users who dont have 2.3.2
and 2.3.2 is the version that fixed the SMS bug.. thats why you didnt experience it Zardos66

I used to get this a lot on 2.3.2. But since 2.3.3 I've yet to have this problem again. Although I do still get the random reboots...

d.chatten said:
The sms bug i'm talking about was supposed to have been fixed in 2.3.2 for the Nexus S, but, i have just experienced this supposedly fixed bug with 2.3.3, the bug is the one that sends a reply to a totaly different contact to the one that the reply was intened for, for instance, today i replied to an sms from a contact from within a messange thread but the reply was sent to a totaly different contact.
Anyone else experienced this "supposedly" fixed bug with 2.3.3.
Click to expand...
Click to collapse
Never heard of this issue
Sent from my Nexus S using XDA Premium App

ya I guess I've never had this issue either

i've definitely heard this issue, its a serious one and been in android for over 1 year now. google just fixed it recently, so i'd go post in their bug tracker that you still see this issue. its a real bad one.
i use handcent anyway which is immune to this bug, but still. i'd stop using the stock messaging app.

RogerPodacter said:
i've definitely heard this issue, its a serious one and been in android for over 1 year now. google just fixed it recently, so i'd go post in their bug tracker that you still see this issue. its a real bad one.
i use handcent anyway which is immune to this bug, but still. i'd stop using the stock messaging app.
Click to expand...
Click to collapse
GO SMS has the fix as well. Highly recommend GO SMS, I used to use Handcent but made the switch to GO SMS.
https://market.android.com/details?id=com.jb.mms&feature=search_result

I Have been using Android since the day the G1 launched, as has my girlfriend and neither one of us has ever experienced this bug period on any of our phones. We've had several hand set exchanges, and multiple hand set models. We are also very heavy texters.
Sent from my Xoom using XDA App

Zardos66 said:
I've never experienced it on 2.3.3. But, I never had it on 2.3.2 either.
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Same Here...

Well i've just experienced this text bug again, in fact, i have experienced it a few more times since i created this thread, there are reports on the net that this bug is still present in Android 2.3.3, has anyone experienced this bug since their last post, or has anyone else experienced this bug, feedback would be greatly appreciated.

I'm still new to the nexus s, about a week on CM7 and no encounter with the bug, hopefully it will stay that way.

[Q] Phone App Doesn't Say "Busy" for Busy Calls

I don't know if this is something about Jelly Bean or ParanoidAndroid (the rom) I'm using, but when I make a call and get a busy signal, instead of getting a message that says the line is busy (like I used to with Gingerbread on my Nexus One), the call just abrubtly terminates the second I place it and says " call ended." This makes it seem like there's something wrong with my network and the call didn't go through at all.
Is this how the phone app is supposed to work in Jelly Bean?

cb474 said:
I don't know if this is something about Jelly Bean or ParanoidAndroid (the rom) I'm using, but when I make a call and get a busy signal, instead of getting a message that says the line is busy (like I used to with Gingerbread on my Nexus One), the call just abrubtly terminates the second I place it and says " call ended." This makes it seem like there's something wrong with my network and the call didn't go through at all.
Is this how the phone app is supposed to work in Jelly Bean?
Click to expand...
Click to collapse
I have the same thing with the Nexus 4 on 4.2.2. Tested it with Galaxy Nexus with 4.2.2 and it worked properly, so I think this is an issue with the Nexus 4.

Tomaxda said:
I have the same thing with the Nexus 4 on 4.2.2. Tested it with Galaxy Nexus with 4.2.2 and it worked properly, so I think this is an issue with the Nexus 4.
Click to expand...
Click to collapse
Are you using stock Jelly Bean or a custom rom? Just trying to figure out if this issue is introduced by Paranoid Android or is part of AOSP.

cb474 said:
Are you using stock Jelly Bean or a custom rom? Just trying to figure out if this issue is introduced by Paranoid Android or is part of AOSP.
Click to expand...
Click to collapse
I'm using stock JB, so I think it is part of AOSP.

Tomaxda said:
I'm using stock JB, so I think it is part of AOSP.
Click to expand...
Click to collapse
Thank. It's funny that this is a hardware specific problem, since you don't see it on the galaxy nexus.

cb474 said:
Thank. It's funny that this is a hardware specific problem, since you don't see it on the galaxy nexus.
Click to expand...
Click to collapse
Well guess what guys, android 4.4 on a stock Nexus 4.... no call busy when you call someone, just disconnects "Call Ended"
Absolute fail ever since launch!!!

istiaquechoudhury said:
Well guess what guys, android 4.4 on a stock Nexus 4.... no call busy when you call someone, just disconnects "Call Ended"
Absolute fail ever since launch!!!
Click to expand...
Click to collapse
Thanks for the info. It's weird that such a basic and simple bug can persist for so long. I guess calling is just irrelevant on phones these days.

UK nexus 4 16gb on the latest 4.4.2 sw , still no busy notification

I recently switched from PA to Cyanogen 11 (KitKat), but still have this problem. If I call someone who is on the phone, I do not get a busy tone and I do not see the "busy" message on the screen. Instead the call terminates and I get a messages saying the call ended. This is confusing, because there's no way to tell that the call didn't just drop or fail to complete, rather than that the line you're calling is busy.
I see people mentioning in the Google forums that this problem exists on stock Android and even in Lollipop.
Anyone know of a solution? When I first got the Nexus 4 I did not have this issue.

[Q] Delayed Notifications in Nexus 4 - Really a 4.2.2 problem?

First of all, I'm sorry because I know this is a recurrent topic, but I have my Nexus 4 for less than a week and the only issue (a big one) is these delayed notifications.
I've asked in more than a place about it and everyone say it is a 4.2.2 problem.
My question is why this does not happen in my Galaxy S3 with Cyanogen 10.1 (ie, android 4.2.2)? Any ideas?
I'm also currently using Cyanogen 10.1 in my Nexus 4, but problem persists. I got it while using stock too.
PS: I have installed Push Notification Fixer and set interval to 5 minutes. Delay remains.

This is a known problem for the nexus 4.
My old galaxy s is also running 4.2.2 and does not have this problem.
The problem is at Googles side.
However, you could try to flash a kernel with the wifi notification fix.
Link
I personally have not tried it yet.

Well, the S3 will have different WiFi drivers, for a start.
Sent from my Nexus 4

steviewevie said:
Well, the S3 will have different WiFi drivers, for a start.
Sent from my Nexus 4
Click to expand...
Click to collapse
I have this problem over 3G as well
Well, so it's a Nexus problem, not a 4.2.2 problem. That makes sense!

respider said:
I have this problem over 3G as well
Well, so it's a Nexus problem, not a 4.2.2 problem. That makes sense!
Click to expand...
Click to collapse
same here evn i hav this problem over 3g as well as 2g..did u find a solution yet??

VanirAOSP ROM

here is new rom i discovered today and built for serranoltexx already.
if anybody interest and if someone can open support thread here, i plan to share it. i dont want open 5 threads and share roms and i cant support them. so i need someone help me on this.
regards..
here sample thread for it, for info and screenshots
http://forum.xda-developers.com/showthread.php?p=44597437
source
https://github.com/vaniraosp
community
https://plus.google.com/communities/111378032131473754160

Screenshots
Sent from my GT-I9195 using xda premium

proxuser said:
Screenshots
Sent from my GT-I9195 using xda premium
Click to expand...
Click to collapse
How do you need supporting?
Sent from the dark side of the moon.
Want to know how to boost your devices performance and battery life? See my thread here: http://forum.xda-developers.com/showthread.php?t=2495269

iKlutz said:
How do you need supporting?
Sent from the dark side of the moon.
Want to know how to boost your devices performance and battery life? See my thread here: http://forum.xda-developers.com/showthread.php?t=2495269
Click to expand...
Click to collapse
rom is released in original android development section.
we can use this thread for questions and answers.

Hi proxuser
what are the key unique features of this ROM ?
i already tried carbon rom

@proxuser
Hi, topic, im a noob so i cant yet post in the developement section, I tested your latest kernel, flashed:
Kartal-JB4.3-AOSP-eur_3g-10.29.2013.zip
and my device didnt want to start up. It hung on the samsung startup screen.
I'm using using cm10.2 official nightlies 25 October rom. I have previously flashed your 1.9ghz overclocking kernel, it worked fine.
Had to restore my backup
Ive got the 3g handset
Sent from my GT-I9190 using xda app-developers app

BushTechy said:
@proxuser
Hi, topic, im a noob so i cant yet post in the developement section, I tested your latest kernel, flashed:
Kartal-JB4.3-AOSP-eur_3g-10.29.2013.zip
and my device didnt want to start up. It hung on the samsung startup screen.
I'm using using cm10.2 official nightlies 25 October rom. I have previously flashed your 1.9ghz overclocking kernel, it worked fine.
Had to restore my backup
Ive got the 3g handset
Sent from my GT-I9190 using xda app-developers app
Click to expand...
Click to collapse
i will upload no-oc version in half hour. please test it and tell me.
edit://
i9190 users pls can u test Kartal kernel in original thread, if bootloops can u test this one
http://d-h.st/Bxc
i need someone reports.

Thanks! I'm really thrilled about this one. Hands down best Rom on my Nexus 7. Downloading now.
Hope you get BLN working. Have you considered Active Notifications alternatively? Might even be the better solution.

Efzekawe said:
Have you considered Active Notifications alternatively? Might even be the better solution.
Click to expand...
Click to collapse
Don't see the benefit in that. You could just use Apps like NoLED or https://play.google.com/store/apps/details?id=com.greatbytes.activenotifications&hl=de
benefit of BLN is less battery drain

Thanks for the advice. I already gave them a try. Knock2 ist too far removed from a stock like appearance, NoLED has a hughe battery drain and DN has had a known issue with low res icons for several versions on the S4 mini, which is still not fixed.
Besides, the big advantage would be a tighter integration of the functionality with the rom hence potentially lowering battery consumption even further and resolving problems with unlocking the phone, those apps tend to run into.

I am using: https://play.google.com/store/apps/details?id=com.ledblinker.pro&hl=en
I compared it to NoLED and it drains less battery.
Try it

Turns out, we had Active Notifications all along. It can be found in the display settings.

Thread closed at OP's request.

who think that jelly bean was better???

Who think that jellybean was more stable and fast and great then kitkat ????

Im on MJ7 and since the kitkat update leaked im thinking of updating but not sure because theres no going back.On MJ7 i have no issues whatsoever (at least none that i know of) battery life with powesaver is also very good 2 days.Any advice should i upgrade?

It is because it is the first release. Just wait the next KitKat version, flash it and wipe your phone, it must be better than Jellybean.

thats what i thought but it past 1 month and nothing new from sammy.. :S

Hallos,
I upgraded from mj7 yesterday. I use Crashrom v4.3 kk. It is just as stable and alot faster then JB. The only problem i encountered was that tomtom couldnt find its drawer on extSdCard. Copying it to internal SD solved it. Not a great solution but i expect it to be fixed soon. Batterylife is absoluteluly great for me, better then my JB was. Hope this helps.
Sent from my SM-N9005 using xda premium

I think that na06 kitkat is just great the only downside is that there are no custom kernels for it yet,but we will get there in time.
Sent from my SM-N9005 using Tapatalk

I just decided i wont update now im rethinking my decision..

metko said:
I just decided i wont update now im rethinking my decision..
Click to expand...
Click to collapse
Same here, every day I was thinking to update. But a whispering voice said, wait and be patient.......and I will be

Pierre118 said:
Same here, every day I was thinking to update. But a whispering voice said, wait and be patient.......and I will be
Click to expand...
Click to collapse
haha exactly the same situation that i have

demirlijanp said:
I think that na06 kitkat is just great the only downside is that there are no custom kernels for it yet,but we will get there in time.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
There's a couple of custom kernels available.

bubu23 said:
Who think that jellybean was more stable and fast and great then kitkat ????
Click to expand...
Click to collapse
kitkat my opinion, faster, more stable, it consumes very little battery even with the stock kernel
---------- Post added at 05:30 AM ---------- Previous post was at 05:25 AM ----------
demirlijanp said:
I think that na06 kitkat is just great the only downside is that there are no custom kernels for it yet,but we will get there in time.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
I use as a kernel-civiz katEngime. excellent

Im very happy with the stock na1 firmware on my phone. Its an n9002 anyway so I dont have much of a choice. I'd probably stick to this firmware until something really major comes out.

Absolutely kitkat is better, more smooth yhen jelly bean. Honest opinion.
Sent from my SM-N9005 using xda app-developers app

bubu23 said:
Who think that jellybean was more stable and fast and great then kitkat ????
Click to expand...
Click to collapse
The real question is not if JB was "greatest ever", the real question is if KK brings (much) more advantages than disadvantages.
JB 4.3:
- stable, extremely well tested
- no SD problem
- voice recorder
- I am on MI7 bootloader and I can install any stock Samsung 4.3 and still have Knox 0x0 and root
KK 4.4.2:
- unstable in many configurations
- new SD permisssions, many older programs have problems
- no voice recorder
- no coming back after the new bootloader
- there WILL be another KK release from Samsung to fix known problems
- only apparent advantage is better battery and somehow better latency (mostly in stock programs) - but on my 4.3 configuration I already have excellent battery (my record is 4 days and almost 10 hours of screen) and I am using programs like Apex launcher and exDialer that already have excellent latency in most of my normal tasks.
So for the moment I am staying with 4.3. and being very happy with it
EDIT:
Also an advantage of KK is the fact that there seems to be more free memory (which IMHO is just the video driver no longer reserving stuff in advance). But since I have most of the stuff that I do not use frozen in Titanium Backup I have plenty of memory for the moment (I am coming from an i9300 where you were basically getting less than 800MB in total, around 300MB free in stock-derived ROMs, so from under 300MB to 1000+ is kind of OK for my immediate needs )

Im also holding back to upgrade to KK,
I've got no issues so far with my rooted MK2. I know there's no turning back once you jumped shipped to KK, so i'm patiently waiting for a more stable release before i let my itchy hands loose

I'm perfectly happy on 4.3.
Send From My Samsung Galaxy Note 3 N9005 Using Tapatalk

I'm playing with the idea. One day I want it. Next I don't. . Purely based on user reviews and personal experience using Stock 4.4 in another device.
Waiting on BTU update. . Frustrating!
Sent from my SM-N9005 using xda app-developers app

ShadowLea said:
I'm perfectly happy on 4.3.
Send From My Samsung Galaxy Note 3 N9005 Using Tapatalk
Click to expand...
Click to collapse
Same here. But I havent tried a kitkat rom yet

NA6 + NA7 had fixes to my previous MJ1 problems, and reacts faster to my actions.
Hence, KK for me.

I was sitting on the fence too about upgrading to KK nut as I have 2 note 3's I thought bugger it, I'll go with one of each...
Set up both Note exactly the same to see what would happen. Jb ate up arond 30% battery over 8 hours while KK only used 20%.
Overall KK was faster. it isn't majorly different eye candy but under the hood has been tweaked big time.
I never had the problems with the sd cards, the flash went off without a hitch and everything was working fine.
I gave myself 3 days to test then upgraded the other one as the experience was so much better...
Only missed some of the theme mods as most others I use worked but that has been fixed with time...
Would recommend going to KK as you will find it better, though you might nee to find the mods again that work with KK...