Samsung Galaxy Nexus: the radio crash bug resolution

Android Open Kang Project

Android Open Kang Project

Two days ago I wrote about my struggle with the first, very serious and very annoying Android Ice Cream Sandwich bug, which causes the phone radio to crash, resulting into behavior like the phone is in Airplane mode and fixable only by phone reboot.

Today I’ve some developments to report:

Switching off 3G mode

When I switched off the 3G, the ill behavior changed dramatically! The phone radio never hung, causing Airplane Mode-like behavior. Instead, the phone started rebooting! With approximately the same frequency, the phone was crashing and causing sudden reboots. I can’t really weight which behavior is “better” in this case: to have the phone rebooting itself, or to have crashing radio. I left it in “crashing” mode, because after I removed the SIM card PIN, at least I was always reachable (when it reboots, usually it restarts OK).

Update to 4.0.3!

In the Google thread about issue 22503, today I found extremely useful comment! The comment suggests that the issue is not seen on 4.0.2! So far I was forgetting to check if there are any updates to the OS. My crashing phone was with Android 4.0.1, i.e. vulnerable to the problem. The commenter stated that after 4.0.2, the issue did not show anymore.

I immediately asked for help how to locate the official update, but alas… it seems my phone is not in the phones, which is being updated by Google (or at the moment). I’ve no idea how this happen, but I was on my own for this one.

That’s when I decided to turn to the good, old forum!

After some reading there, I’ve got to the conclusion that the only chance to try resolving the issue is to install custom ROM, which is based on 4.0.2 or 4.0.3. After some more reading, I decided to put Android Open Kang Project, a ROM, which has excellent feedback so far and looks like it’s “alive and developing”.

Once the decision was made, I had to get the tools for updating. In the forum, there’s already plenty of useful Google Galaxy Nexus information about rooting the phone. I had to use the following resources in order to do the job:

It took me about hour, hour and a half from start to end. The whole thing was 5-6 hours ago, no sudden restart of cell hang so far. The phone is cold, no battery overheat and the battery discharge rate looks times better than before.

I hope this is the end of the saga, but if there’s more on this topic, you’ll most probably read about it here.

The first quite serious Galaxy Nexus bug

Samsung Galaxy Nexus (cc-by-sa) Sham HardyIt’s my 3rd week (or 4th? It doesn’t matter!) with the Samsung Galaxy Nexus phone.

Since few days it started to show pretty weird problem: suddenly it starts reporting that Airplane mode is on and I can’t make any call. If I press and hold power, the menu there says the airplane mode is on. If I click to switch it off, it grays out and nothing happens. At the same time, in Settings the Airplane checkbox is not checked. Pretty weird and very annoying problem, solvable only with reboot of the phone. The worst thing is that you can’t know when the problem will popup, so you may end up without coverage for hours, until you see that your phone is off again (already happened to me!). The issue is also discussed in Radio randomly goes off and [Q]Airplane mode keeps turning itself on and won’t turn off threads at XDA Developers forum.

Today I got sick and stopped uninstalling applications, but started the research. Pretty quick I came to the fact that the issue is also discussed in Radio randomly goes off and [Q]Airplane mode keeps turning itself on and won’t turn off threads at XDA Developers forum. Which led me to the thread at Google, which looks like acceptance of this as an official bug. The priority of the bug is “Medium”, which simply means that… well it means that it won’t be fixed anytime soon. I doubt Google guys are out of bug with high and critical severity, so they can fix that Medium one 🙁 .

I’m pissed :(! Let’s see what will happen, but I’m not very optimistic!

Windows 8 DP Bug: Overwriting Credentials when in HomeGroup

Well, it’s been almost a week with Windows 8 Developer Preview. I installed it on a brand new, purchased just for this purpose, Dell Inspiron Duo netbook. As expected, installation was quick and easy. Network setup came up and then I made a call, which revealed this very interesting bug in the Developer Preview version.

Then I decided to join my machine in my HomeGroup. My HomeGroup consists of few workstations and my Windows Home Server 2011. WHS, of course, has most of the data.

Immediately after joining, I wanted to see the shares on my network. Obviously, that could not be done with my current, Windows 8 credentials, since they were with my Windows Passport (WHS does not recognize Windows Passport). I had to enter an additional credentials, but I could not see how, initially. In Win7, if a login fails, I was presented with a dialog, where I could put different credentials. For some reason (maybe even by design), Windows 8 did not show me such dialog, it directly popped “Access Denied” kind of message.

I asked in the Windows Developer Preview forums. And I got my answer there: the Credentials Manager seemed to be the key to my success. In the Credentials Manager I’d be able to put credentials on per-server base, which credentials later on will be used to access the specified server.

I put my correct credentials there, and retried. Nope. Does not work.

Then I dug a bit more. Tried other different things (verified once again that I do have access from Win7 machine). Still nothing. Finally it enlightened me. I restarted my explorer and somehow automagically the credentials worked and I was presented with the contents of the share. At that point the Credentials Manager looked like this:

Correct Credentials

I was glad. Then I restarted and… the problem came back. “Access Denied” kind of message, yuck!

I started the Credentials Manager and I was quite surprised to see this:

Credential after Login

As you can see, my previous credentials were replaced by the default HomeGroupUser$ system-wide share, which of course did not had access to that private share, available only for my user and not for my whole Home Group.

I fixed the credentials again, it worked. Then I logged out, logged in and… it again replaced the credentials.

So here is the bug title

When joined in Home Group, Windows 8 Developer Preview incorrectly replaces any custom credentials with the default, HomeGroupUser$ credentials.

Steps to repro

  • Windows Home Server 2011 might be a prerequisite, can’t confirm that at the moment, but the problem was found in a setup with Windows Home Server 2011.
  • Create share on the Home Server and set special permissions to that share. Disable access to anyone, but a custom Windows Home Server user.
  • On Windows Developer Preview, login using Windows Live based login
  • Using the Credentials Manager, set custom access privileges for that server/share combination.
  • Verify that the credentials are working
  • Log off, log on with the previous credentials
  • Try to access the same share. Access fails with “Access Denied” error message.
  • Open the Credentials Manager and verify what are the access credentials for the specified server/share. The access credentials are reset.


    If the machine is disjoined from the Home Group, the bug cannot be reproduced.


    The workaround is good for me at this point. I disjoined the machine from the Home Group and I’m cool. But if this bug confirms, it’s a must-fix. So far I’ll do the only thing I could: will report it. And then we’ll see.

    Prior publishing this, I tried to locate the official feedback page, so I can post the link there too. It seems there’s no such page right now, but I keep searching. If you know it, I’ll appreciate telling me.

Y не може да прави Z Undo, нали?

Пиша това, за да може материалът на Michael Kaplan относно бъга в Bulgaria Phonetic клавиатурата да се намира и при търсене с думи на кирилица.

Вчера получих бъг репорт от Стилгар Наиб, моят любим Facebook трол Smile. Човекът с основание се оплакваше, че Ctrl+Z не работи в Bulgarian Phonetic клавиатурата. Много гаден бъг, ако човек е свикнал с удобната Undo комбинация.

Честно казано, бях леко скептичен, че този бъг репорт ще стигне до Windows екипа, защото Bulgarian Phonetic не е от най-често използваните клавиатури. Говоря за ЧШЕРТЪ глупотевината на екипа на БАН, този самозвано (и предварително!) наречен “стандарт за българска фонетика”. Е, та точно при него Ctrl+Z е дефакто неработещ в почти всички приложения (БАН, разбира се, няма конкретна вина за това Smile).

Използвайки всички възможни канали, ескалирах нещата. Нашенци от Редмънд (мерси, Митко и Стефчо) ми помогнаха да стигна до правилния човек и ме подкрепиха, когато имаше нужда да се докаже защо смятаме, че това е бъг.

За съжаление, този бъг не може да бъде поправен в съществуващия layout. Michael е написал защо. За да се оправи, ще трябва да се напише (още) един Bulgarian Keyboard Layout, което едва ли ще стане. Най-вероятно бъгът ще се “оправи” с Knowledge Base Article, т.е. хората, които ползват тази подредба, ще трябва да се научат.

Якото в случая е, че Майкъл, човекът занимаващ се дефакто с всички клавиатурни подредби в Windows (откъм продуктова гледна точка разбриа се) се погрижи да напише подробно обяснение. Яко е, че това дойде от community-то, и че само за един ден компанията чу и отговори на въпроса. Да, не винаги проблема може да бъде оправен. Но може да се даде работещ workaround.

И то само за един ден! Яко е, когато си помогнал това да се случи.

Thanks, Michael, for your support!