yashsingh1/xdaforums huggingface dataset:
[G2 and Desire Z Android Development] TpmKranz:
It is also possible to add a 2G/3G toggle to the power widget in the notification drawer if you don't want to go the *#*#4636#*#* way. I used to use this myself when the toggle was not implemented properly and found that it was a little cumbersome.

Just go into system settings -> "System" -> "Notification drawer" -> "Widget buttons" -> check "Toggle 2G/3g", scroll down and tap "Network modes" to decide how the toggle should work ("2G/3G+2G" or "2G/3G only" [which is what you are looking for] or "2G/3G only/3G+2G").

And many thanks to you, blk_jack, for this beautiful ROM and your effort to make it even more beautiful. It is a pleasure to use it and it's the only reason for me to stay with ICS on this device - if it wasn't for Andromadus Mimicry I would flash a Jelly Bean test build every other day :D
[G2 and Desire Z Android Development] Oni-Musha:
I report to you a little bug with Instagram, with the precedent release the camera works fine, now to work i have to open the gallery, go back and it works fine.
[G2 and Desire Z Android Development] DJMartini:
No these were from Amazon and just recent like 2 months ago.
[G2 and Desire Z Android Development] blk_jack:
Nothing changed that would affect camera. Make sure you've wiped the app's data, use logcat, etc.

At least glance at the OP, it's outlines the proper method of reporting bugs.
[G2 and Desire Z Android Development] kbeezie:
Odd that you had it working in previous releases seeing as outside of virtuous infinity I've never had luck with instagram on any ICS rom even back to mimicry 1.1.2

Sent from my T-Mobile G2
[G2 and Desire Z Android Development] farris:
I have this problem that I first feel the vibration, and after some seconds I hear the ring tone.

When the phone is just restarted, they sound at the same time, but after two days or something it's really worse. It first vibrates, and than after 4-5secs, I hear the ring/notification tone.

Has this something to do with trouble going out of sleep mode or something?
[G2 and Desire Z Android Development] ashwinmudigonda:
It's tempting to answer your question...again. Click on Search This Thread and search for "vibrate".
[G2 and Desire Z Android Development] farris:
Thanks, unfortunately it's an G2 ICS bug I see :)
[G2 and Desire Z Android Development] robuser007:
Great rom, even the notification led works while charging :)

Any chance for having the immense 9 app lockscreen from aokp ?
[G2 and Desire Z Android Development] blk_jack:
All lock screen functionality in the rom is unmodified CM9, feel free to file it as a feature request on their issue tracker :)
[G2 and Desire Z Android Development] tarroyo:
I just noticed in /settings/backup & reset/ 'backup account' is greyed out. Is this a ICS issue???
[G2 and Desire Z Android Development] TpmKranz:
DHCP problems (again?) - not complaining, reporting a bug!

Hey there, I've faced a problem using the portable Wi-Fi hotspot.

So here is what happened: I use the Wi-Fi hotspot because I've found that, under certain conditions, my mobile carrier's throttling doesn't work and my housemates don't like it if I occupy our home internet access because it has a limited data volume (and its throttling is very reliable). Anyhow, today I updated from Andromadus Mimicry 1.3.0 to 1.3.2 and activated the Wi-Fi hotspot. After surfing the web a while on my laptop without problems I watched a movie and after finishing it I wanted to access the internet again. So I fired up Chrome on my laptop and found that there were "Server problems" going on, preventing me to access the internet from my laptop. I checked whether I was able to open a website on my phone and it worked. I assumed that it was a problem with my laptop - I'm not a Linux pro and so I thought bringing the [Edit: my laptop's] wlan0 interface down and up again would fix it, but it didn't. I tried rebooting and bringing the interface up again but that didn't work either. Then I checked whether I could access the internet from a housemate's Windows PC and while trying to connect to my hotspot I noticed that the PC was unable to get an IP address by itself. So I set up the static IP settings and it worked. To validate the solution I tried the same thing on my Linux machine and it also worked. So I think that the DHCP broke while I was watching the movie.

I think that pulling a logcat would be an idea but I don't know when exactly I should do this. Maybe when activating the Wi-Fi hotspot?

Or is there even anything else I could do?
[G2 and Desire Z Android Development] blk_jack:
What might have happened was dhcp was killed by androids oom killer. In that case hot rebooting your phone is here best course of action, though I'm completely speculating since without logs it could be a large number of thjngs.
[G2 and Desire Z Android Development] TpmKranz:
Alright, so I fired up adb logcat and cancelled it to get rid of things that happened before I do relevant stuff (that's my guess, at least), activated the portable Wi-Fi hotspot, connected to it with my laptop, disconnected again, deactivated the Wi-Fi hotspot and put adb logcat's ouput into logcat.log (which is now logcat.txt).

I also put adb shell ps's output into ps.txt because I thought it would help deciding whether dhcp was killed or is still running.

PS: I didn't reboot since the issue came up.
[G2 and Desire Z Android Development] heybobitsme:
1.3.2 is running pretty good for me, however, the phone doesn't recognize when I push the button on my headphones. I have a set Jays One+, and the button worked on previous versions. I have not performed a wipe, just the standard cache/dalvik-cache as I don't have the time right now to reset everything. Could this be related to the headset volume fix?
[G2 and Desire Z Android Development] blk_jack:
Just tested with my stock HTC headphones/headset and everything works great out of the box both for calls as well as controlling music.

Backup, full wipe, test, log, report. Follow the instructions in the OP and the screen that comes up after you wipe for responsibly recreating and reporting issues.
[G2 and Desire Z Android Development] goister:
Does anyone know how to specify an additional timeout after screen off before screen lock(PIN/password/pattern) activates. It's quite irritating to always have to authenticate myself when I turn my screen off and on again, even if it's just 2s later. Under my screen lock settings, I have "Automatically lock" is set to "1 minute after sleep", my "Power button instantly locks" is disabled and my "Screen lock" is "Secured with pattern". However, I still get screen lock immediately after I screen off.
[G2 and Desire Z Android Development] blk_jack:
This appears to be a glitch w/ CM9's settings (I haven't looked into it yet, though I did find a workaround). Set your security type to Slide and then set the timeouts (both) for 1 minute after sleep.

After you do that change your security type to pin/password or whatever you use and setup the timeouts there. That seemed to work for me.
[G2 and Desire Z Android Development] blk_jack:
Okay, just looked into this very briefly and it appears to be an issue a bunch of people are having using a variety of CM9-based ROMs. Check out these links here, here, and a google search here.

Someone mentioned that since MMS uses data that using MMS while tethering could be causing issues, but I've never encountered this issue myself personally.

Let me know if that helps :)
[G2 and Desire Z Android Development] philosophics:
I have a problem like this quite similar with my tablet. Waydownsouth provided the solution to what appears to be what you're experiencing.

The solution was to turn wifi off, then go to /data/misc/dhcp and delete the 2 or 3 files that are in that folder then reboot.

It does seem to work everyone but then again, this is with my tablet. Not sure if it will work with the phone but it wouldn't hurt to try. The files you'd be deleting will rebuild themselves during boot...
[G2 and Desire Z Android Development] chan1628:
Anyone have any suggestions about how to improve the contract picture quality? Both the caller id & contact detail screen show very pixelated pics

"there is no spoon"
[G2 and Desire Z Android Development] heybobitsme:
I backed up 1.3.2, restored 1.3.1, tested the headphones and they work. I then restored 1.3.2 and they work. :confused: For the life of me, I could not get the headphones to work properly.
[G2 and Desire Z Android Development] shady503403:
Everytime I flash a new rom it always makes the pics low quality unless its the pic from g+. There's a couple guides on xda. I just reset them from gallery all the time.
[G2 and Desire Z Android Development] J-Hop2o6:
Jellybean fixes this natively, but if you have facebook,DL facebook contact sync from the market. If not, try to search on google for contact photo sync (not sure its on the market yet).
[G2 and Desire Z Android Development] ashwinmudigonda:
Finally got some time to flash 1.3.2 Full wipe and installed. The initialization screen glitched out and restarted. After that, Play Store would not auto install my apps. I had to go through them manually. But for that, everything checks out fine. The ROM is zooming and I can't stop waking the phone to just swipe about the home screens every now and then! Thanks for your time and effort, blk_jack!
[G2 and Desire Z Android Development] mcsmart:
Thanks for this great ROM. About the text-corruption issue: I've been using Gen.Y VisionX B3 (Sense 4.0A) for a couple of days now and it did not cause any text corruptions. The author states that they have been fixed. Maybe this might help here too:

http://xdaforums.com/showpost.php?p=29854509&postcount=212

Anyway, keep up the good work!
[G2 and Desire Z Android Development] SnapplerX:
Will there ever be a 720p video recording support update or is that not possible? Because that is pretty much the only thing missing from this rom.
[G2 and Desire Z Android Development] Roolio:
I don't know if this is a ROM-specific issue or more of an ICS issue. I also think it's more a 'feature' than a bug. But when I turn on the flashlight, it turns off again when I turn off the screen. And I want to turn off the screen, or else I'll press the screen accidentally a lot when I'm holding the phone in a flashlight kind of way.

So for me it would be nice to make it an option to be able to turn the screen off with the flashlight on.

Edit: I was just reading about the text glitch bug a few posts above this one. I just wanted to say I've never experience that bug with any of the mimicry ROMs so far.

Oh and a more annoying bug is when I'm typing on the internet, when a sentence has reached the end of a the text box, it won't let me do a space. It just doesn't register it, or the space disppears instantaniously, I don't know.

But maybe that's more a browser related bug, probably not mimicry-specific.
[G2 and Desire Z Android Development] TpmKranz:
Thanks for your efforts but the problems described there aren't actually the same as the one that I'm having. One the one hand, I don't even use MMS (who needs this service anyways?) and on the other hand, the hotspot doesn't turn off by itself, though I'd encountered this once or twice in the past, but it would work normally again after a reboot.

But...

Thanks for this hint, but first I would try rebooting without doing anything else.

But...

One of this conditions is that I have to change from 3G to 2G, change back to 3G and see if my network speed is acceptable again. And this has to be done approximately 10-100 times everytime I lose 3G data connectivity. No joke!

So I avoid rebooting if it is possible. I'll give feedback if I encounter conditions that force me to reboot (like the occasional freeze while using the browser) or if I feel motivated enough to repeat that procedure.

---------- Post added at 11:53 AM ---------- Previous post was at 11:47 AM ----------

I've found this quite annoying too, but I was too lazy to report it. I think it is associated with the quick torch feature, but I am not sure because the problem persists after turning off that feature.
[G2 and Desire Z Android Development] Ditamae:
Hey blk_jack. Loving the update... seems a bit smoother & snappier than the previous version, but it could be a placebo effect. ;) At any rate, 1.3.2 is working well. I have noticed that the volume level of the UI touch screen sound appears quieter than in previous builds. Even with system volume all the way up, the Effect_Tick.ogg still doesn't sound as loud as it did on a lower system volume setting in < 1.3.2. Any idea why this might be? It's very nerdy, but I love the touch screen sound. :p

As always, thank you for your time.
[G2 and Desire Z Android Development] blk_jack:
Guys, please read the OP. Specifically when it mentions Mimicry and Andromadus and how they differ and how bugs should be reported in regards to either. Mimicry is a code fork from Andromadus. All the framework and base functionality, as well as all CM-related patches are merged into Andromadus upstream before they hit Mimicry. Any bugs I fix "in" Mimicry are fixed in the Andromadus repo as a whole and also any Andromadus bugs fixed by others will be pushed to Mimicry.

That said, you need to post about these things in the general Andromadus threads (as well as on the Audacity/Test Builds issue tracker). Right now very little changes are being made over & above Mimicry/CM9 specific things on ICS. All the new work is on JB so you need to inquire in Flinny's test builds thread.

This is built into the CM Torch tool. The way I understand it is that the LED flashlight itself doesn't use wakelock. So what happens is your phone goes to sleep, and in sleep shuts off the CPU, which in term shuts down the torch. It's also a safeguard against accidentally leaving the LED flashlight on indefinitely with the screen off.

Again, like what I said above though, this is a CM specific "issue" in that it's their Torch tool and the changes I made were mostly to the framework to actually use the native Torch app for the QuickTorch feature, as well as add the new intents to let it toggle on/off explicitly.

Thanks!

As for sounds, nothing was touched on my end to raise or lower volumes and I don't believe any patches I merged affected sound in that way. Have you tried wiping and seeing if it is the same on a fresh environment vs. the backup from 1.3.1?
[G2 and Desire Z Android Development] austriker27:
why did you fully wipe? I thought the OP said we can just flash upgrades without wiping so we dont lose everything. I am thinking about upgrading to 1.3.2 but dont want to wipe.
[G2 and Desire Z Android Development] TpmKranz:
Wiping /data prevents that unexpected errors occur. You don't need to. But you should always have a backup from which you can restore apps/app data/SMS/settings/[...] just in case weird things happen and wiping /data becomes necessary.

I usually make a nandroid backup and fully wipe before flashing an update. After the initial setup I just restore the things I need from my backup and the ROM should work without unexpected issues.

So it depends on what you prefer. If you are afraid of wiping then you don't need to, but you should always have a backup of some kind just in case.

---------- Post added at 04:38 PM ---------- Previous post was at 04:28 PM ----------

Thanks, I was also interested in why the LED would shut off after some time even if the power button remains untouched (for example if the screen timeout it reached). So that means that the phone goes into deep sleep immediately after hitting the power button and just "snoozes" a while before sleeping deeply if the screen turns off by itself?
[G2 and Desire Z Android Development] J-Hop2o6:
He's correct. The reason is its a new CM sound (about a few months ago), which is wayy lower in volume compared to the old touch sound. Plus the new effect tick sound sounds horrible compared to the old original ICS effect tick sound. I got tired of having to replace the CM version with the original ICS version so I just turned off touch sounds all together.
[G2 and Desire Z Android Development] blk_jack:
Thanks for explaining the whole data / wipe thing. So many issues arise from people not wiping when things are clearly bugged because of some bad data in an app (or entire partition). These ROMs are constantly changing and as such so is the data. Ideally you just flash a new version of Mimicry and you're good to go but sometimes it's just a toss up depending on what data you use & what was updated.

As for deep sleep, the phone will try to IMMEDIATELY go into deep sleep. Deep sleep completely shuts off the CPU and just keeps the radios on, so something like that led flash that doesn't hold wakelock should also shut down. Though this is just my theory on it. I haven't looked at the code for the torch in awhile.
[G2 and Desire Z Android Development] ashwinmudigonda:
OCD!! I have noticed that right after a full wipe and clean install, the ROM is the quickest! I tend to do a full wipe every third or so flash. Also helps me to do some spring cleaning when I get rid of unused apps.
[G2 and Desire Z Android Development] farris:
I noticed that Gmail is very, very slow since I updated to 1.3.2. It's not workable anymore. Whenever I type a mail that's longer then 4 sentences, my whole device is getting slow. When I type a sentence on my keyboard, the letters appear 1-3 seconds after each other. You can't type a mail in this way. the whole phone is slow so restarting takes lots and lots of time.

I deleted cache etc in the gmail app but this doesn't help. Any suggestions? Haven't had it in 1.3.0.
[G2 and Desire Z Android Development] chan1628:
"contact photo sync" worked for me.... thx again

its jsut a pain cuz i have to redo all my contact pics again.. but hopefully, this is the last time i need to do this
[G2 and Desire Z Android Development] ashwinmudigonda:
Titanium Backup. NANdroid backup. Wipe all. Flash ROM+Gapps.
[G2 and Desire Z Android Development] timskyline86:
Is anyone else experiencing problems with Wifi Calling when you try to call out it will ring once then give the Out of Service error and hangs up and fc's the app. I can recieve calls no problem.

Tried in on 3.1 and 3.2, and even maunally flashed it on both. Same thing happens on both, its wierd.

Leaving the country for awhile and would love to get this fixed instead of having to revert back to another rom.
[G2 and Desire Z Android Development] EdKeys:
What version is your SIM card? You'll have to pull it to know for sure. If you haven't updated recently it would be a good idea to stop by a T-Mobile store and get the latest version if you don't have it before your trip.. See the OP for a link to my thread for more info.
[G2 and Desire Z Android Development] timskyline86:
I have the 9177

It's worked before, not sure whats happening. What's weird is that I reverted back to CM7, clean wipe/install, reinstalled radio and using the apk that comes with CM7 and its still doing the same thing. Only difference is on cm7 it doesn't fc the app. Looking through the logcat and it just cuts the audio and ends for no apparent reason.

EDIT

Well I found the problem, apparently it was my router/cordless phone causing the issue not the phone itself. Conflicting channels caused the phone to drop the connection for a brief enough time that it would give the Out of Service code. Changed the channel and it works now.
[G2 and Desire Z Android Development] Zelych:
Hi, I have a problem that I sometimes overflows graphics, viz. screenshot:

Is it possible to eliminate this problem through the setting?
[G2 and Desire Z Android Development] kbeezie:
Happens with just about every ICS rom out there, only fix is to either force close the app or restart.
[G2 and Desire Z Android Development] jevring:
What's keeping Jelly Bean?

I'm curious, what's keeping Jelly Bean from our, or even any phone? I don't mean to rush or complain, I'm merely curious.

Clearly we have the source code, and clearly people can build complete images.

Is it just a matter of testing (and hacking the source to fix the bugs), or do we need drivers, or some hardware thing, or some sector alignment or some other magic that needs to be discovered?
[G2 and Desire Z Android Development] NeverGone\RU:
We don't have (and never will) an official ICS/JB release from HTC.

It's needed mostly to have proprietary drivers (especially for camera).

As these devices' datasheets are not public, there's a lot of work being done 'blind', just experimenting what could <some source change> lead to: complete malfunction or a huge success and fully working device.

Correct me if I'm wrong.

As for graphical glitches/font corruption, I get these even on my Samsung tablet, so it's probably an Android 4.x problem itself.
[G2 and Desire Z Android Development] Nospin:
Testing and hacking right now. We will never have the drivers we need, so our devs have had to work magic to get everything functional.
[G2 and Desire Z Android Development] jevring:
Ok. I'm guessing, then, that given the fact that we have 4.0 running on our phones, 4.1 isn't as much of a stretch as, say, 2.3 -> 4.0.
[G2 and Desire Z Android Development] kbeezie:
In theory that's true, but there's also some internal framework changes between 4.0 and 4.1, but it wouldn't take quite as long as say 2.3 to 4.0. I mean there is a JB test build right now, but course it's not exactly perfected yet, still lots and lots of testing to do.
[G2 and Desire Z Android Development] dave_id:
hello

thanks again for this great rom!

I still have 2 problems:

-sometimes (randomly?) when I answer a call, I have the external speaker on, I thought it was corrected?

-also my keyboard is now a QWERTY when all that I want is an AZERTY (french phone)

can you help?

thanks a ton.
[G2 and Desire Z Android Development] kbeezie:
Don't know about the first, but regarding the second, just go back into System Settings -> Language & Input , and change the keyboard layout for the specific input method (should have a lil config icon off to the right).

I'm not sure if it's possible with the stock android keyboard without changing the whole locale, but I do know you can uncheck 'use system language' for the android keyboard, and then select one of the other languages and see if it also happens to change the layout.

On swiftkey3 or such, layout is actually pretty obvious as you press the tiny lil keyboard icon next to the selected language such as in the screen shot I attached. (just be aware swiftkeys has a lil bit of a bug with the hardware keyboard in regards to the alt button).
[G2 and Desire Z Android Development] blk_jack:
Since others aren't having these issues you need to provide more information and/or a logcat on the speaker issue. Please start a QA thread with all the proper information needed to let someone help you.
[G2 and Desire Z Android Development] TpmKranz:
After getting up today I found my network speed slow again and so I had no reason to avoid rebooting anymore. The dhcp problem is fixed now. I guess blk_jack was right with his theory of dhcp being killed.

Is there a way to prevent Android from killing it?
[G2 and Desire Z Android Development] blk_jack:
What I meant before was, even if your symptoms don't match those of the URLs I linked, the error message itself is, which is what I thought might let you gain some insight into the issue.

It's hard to say, and even harder to say if it will ever be addressed now that everyone is moving forward to Jelly Bean (Yay! Tons of new issues to fix!!!)
[G2 and Desire Z Android Development] geokuttan:
Is anyone else having issues with tether. I tried both Barnacle Wifi tether and Clockwork tether. I even tried different roms. Is it because of Tmobile ? I get NAT error for wifi tether and for usb tether its just says limited connectivity.
[G2 and Desire Z Android Development] blk_jack:
I've had no issues using ICS' built in tethering functionality. Not sure about using 3rd parties apps, though.