Obsolete
Status Update
Comments
hb...@gmail.com <hb...@gmail.com> #2
I can attest that Yakju 4.1.2 update on stock Galaxy Nexus broke radio, bluetooth and wifi. The phone enters airplane mode on its own. The radio loses all telco signal (only recover after a 10 second airplane mode). Bluetooth pretends to connect but the headset is unusable. Wiifi that the same issue as bluetooth.
All in all, the phone connectivity is in a really poor state. Most people could not reach me today and I had to keep checking the phone the whole day to see if the radio/wifi was still working which it mostly wasn't.
All in all, the phone connectivity is in a really poor state. Most people could not reach me today and I had to keep checking the phone the whole day to see if the radio/wifi was still working which it mostly wasn't.
nw...@gmail.com <nw...@gmail.com> #3
[Comment deleted]
mi...@gmail.com <mi...@gmail.com> #4
Same on nexus S, wired tethering
Vert bad bug...
Vert bad bug...
da...@gmail.com <da...@gmail.com> #5
[Comment deleted]
sh...@claricetechnologies.com <sh...@claricetechnologies.com> #6
Same issue. Cannot tether. Wifi will connect and assign an IP. No throughput.
Version 4.1.2 Build JZO54K
Version 4.1.2 Build JZO54K
sh...@claricetechnologies.com <sh...@claricetechnologies.com> #7
Update, Bluetooth tether works. Wifi does not.
pa...@gmail.com <pa...@gmail.com> #8
same thing here. Want to get back to previous version :(
hb...@gmail.com <hb...@gmail.com> #9
[Comment deleted]
he...@gmail.com <he...@gmail.com> #10
I have the same issue. 4.1.2 broke wifi tethering
he...@gmail.com <he...@gmail.com> #11
I reverted back to 4.1.1, out of curiosity, what is everyone's frequency? i'm using 850/1900 HSPA. My theory is that 4.1.2 breaks tethering in some way.
[Deleted User] <[Deleted User]> #12
Same to me. Cannot tether. Wifi/usb will connect and assign an IP. No throughput.
en...@gmail.com <en...@gmail.com> #13
Same here on the nexus S.
da...@gmail.com <da...@gmail.com> #14
I was having the same problem but I spoke to my network's help line, they made a setting change on my line and all is working again now.
[Deleted User] <[Deleted User]> #15
Signal Strength suddenly become bad ..along with Some issue with USB Port as its not deducting while connecting to PC
fi...@gmail.com <fi...@gmail.com> #16
@#13: could you please ask them what they changed so others can try?
ch...@gmail.com <ch...@gmail.com> #17
[Comment deleted]
xd...@gmail.com <xd...@gmail.com> #18
Have the same problem in my Galaxy Nexus, tethering does not work. I updated last weekend to Jelly Bean 4.1.2. Everything was fine with ICS.
ts...@gmail.com <ts...@gmail.com> #19
I have the same problem on my Galaxy Nexus 4.1.2. Previously with 4.1.1 everything was fine.
[Deleted User] <[Deleted User]> #20
Ref. my comment #13 and request for further info #15, I have spoken to my network operator and the fix they employed was to send out a service text that updated the APN settings. I'd perhaps suggest checking yours and making sure 4.1.2 hasn't messed with them.
In my case I am with EE in the UK and it was their OrangeBroadband APN settings that needed repairing.
In my case I am with EE in the UK and it was their OrangeBroadband APN settings that needed repairing.
sa...@google.com <sa...@google.com> #21
@#19: thanks for looking into this and providing the update. I think however that your issue is different, since my APN settings were fine (I did a reset right now though just to confirm), and having bad APN settings would mean that the phone cannot access the Internet either, which, in my case, works flawlessly (I can browse, use online apps and stream online radios, the only thing I cannot do is tether)
Description
Create and launch an intent to insert an item into the calendar.
Intent i = new Intent(Intent.ACTION_INSERT);
i.setData(CalendarContract.Events.CONTENT_URI);
// Time corresponds to Feb 27, 2014
i.putExtra(CalendarContract.EXTRA_EVENT_BEGIN_TIME, 1393480800000);
// Time corresponds to Mar 1, 2014
i.putExtra(CalendarContract.EXTRA_EVENT_END_TIME, 1393653600000);
i.putExtra(CalendarContract.Events.TITLE, "Sample name");
startActivity(i);
- What happened.
The Calendar app launched; the title, "All day" switch, and start time were set correctly. However, the end time was set to a time exactly an hour later than the start time, not the end time which I requested with my intent.
- What you think the correct behavior should be.
The Calendar app should respect the start and end dates sent via an intent.
- Additional Info
This was tested on a Nexus 5 running stock 5.0 with the latest Google Calendar app from the Play Store.
Setting the "All day" flag of the event to true did not effect the outcome; it was still incorrect. The start date and end date were the same, even though I requested different dates in my intent.