Database Develop

New Nook Locking Up

Just bought a NC. Installed CM7 and everything seemed to be fine. Now the NC is locking up after less than a minute of use. I rebooted into CWM and wiped cache and dalvik but its still locking up. I checked to make sure it wasn't overclocked... nope... still locking up.
Any ideas?
I'm running the latest nightly....
Not my first time around CM7. I've got a Droid INC that's been running CM since 6.0 and I'm on the latest nightly with it.

Locking up as in it just quits responding? Of you have to fc?
Are you installing to emmc or sd? If the latter, what card do you have?

Completely locks up and I have to hold the power button. Its installed to emmc. I've got a sandisk 2gb in there which I've swapped.
I reloaded the nightly with a cache and dalvik wipe. When that didn't help I did a reload with a full data/factory reset. I'm still getting lockups though not quite as frequent.
Is bad hardware an option?

Always a possibility.
Was it new or refurbished?
Did you use out as stock before you flashed it with cm7?
Can you reinstall 1.2 stock, if it reinstalls ok, does it lock up also?

Brand new. Ran it for 5 minutes before slapping cm7 on it. I was thinking about putting 1.2 back on it and see what I get.

Well, I think I've figured it out. I had setup a Beautiful Widgets clock on my home. This last wipe and reload I didn't reinstall it.I haven't had a single hang. I tried installing BW again and setting up a clock widget. Within 5 minutes it hung. It was right back where I started locking up every couple minutes. I then uninstalled BW. No more lockups...
Weird......

menos08642 said:
Well, I think I've figured it out. I had setup a Beautiful Widgets clock on my home. This last wipe and reload I didn't reinstall it.I haven't had a single hang. I tried installing BW again and setting up a clock widget. Within 5 minutes it hung. It was right back where I started locking up every couple minutes. I then uninstalled BW. No more lockups...
Weird......
Click to expand...
Click to collapse
Yeah it's a common problem. It's Badly coded app.
Sent from my LG Optimus V using Tapatalk

think i am using fancy widgets, if you want something similar, that to date, i havent had a problem with - other than it uses clock cycles for something that you would think wouldnt take anything (showing the clock!?)

Yeah.. I installed fancy widgets. So far no problems. Don't know what the problem with BW is.

I am using BW on my nook as I type this at work..no problems at all.
Sent from my NookColor using Tapatalk

What build are you running? Are you on a nightly or the RC?

ROM with good GPS?

Im currently using CM 7.0.3 and the GPS is pretty much useless. Does it work well in 7.1 or in any of the nightlys? Also I see that the nightlys stopped in the download page, just end of life for the N1?

I'm on CM7 nightly, my GPS is always good.
Do you use GPS Status and Toolbox? It's a good app that download GPS data
to help for faster lock.

+1. What BBF said ^. Using 7.1 myself.
Sent from my Nexus One using XDA App

After reading your title i started to think about when was the last time i had a phone that got a GPS lock in under a minute with no extra apps. The last time i can remember is when i had a my Mytouch 3g about 2 years ago. I had great GPS locks on CM when i had that phone but since (G2, G2X, nexus one) have all has horrible locks unless i download the GPS toolbox and even then it isn't very fast.
Has there been something in the last two years that would cause cell phones to lock GPS signal at a slower pace?

may be your area, but almost always and now on Nightly 253--almost instant locks

Lythandra said:
Im currently using CM 7.0.3 and the GPS is pretty much useless. Does it work well in 7.1 or in any of the nightlys? Also I see that the nightlys stopped in the download page, just end of life for the N1?
Click to expand...
Click to collapse
I haven't had any issues with my phone getting quick locks. And that is throughout my whole time with CM7 (and I never use GPS Status to refresh my agps data). When you upgrade to 7.1, I would highly recommend wiping the device completely including MANUALLY wiping the /system partition through recovery. Then install 7.1 and gapps.
You can back up apps and app data, but don't back up any system settings as restoring those could bring your gps problems back.
Oh, and the reason for no nightlies is the build machine for CM is having hardware problems (and there are no nightlies for any device, not just the N1). There is still life left with our N1

I'll probably upgrade the ROM this weekend. My GPS was great pre-CM 7.0.3 where I was using CM 6.xxx which is why I was asking.
Thanks for the answers.

I use CM 7 and it works well, it's really true that you can get a better signal with other mods?
Thanks

I downgraded to Enomther's last froyo mod a few weeks ago because I have no luck getting similar performance with any gingerbread mod. I've tried CM7,7.1,as well as a lot of the nightlies, Oxygen Mod, and stock gingerbread. The GPS performance just isn't anywhere near as good as on froyo, which is quite frustrating since I depend on it a lot. I've tried the GPS status app which helps occasionally, but it becomes a hassle if you constantly need to use it. :/
Still searching for a good gingerbread mod though.
Lythandra said:
I'll probably upgrade the ROM this weekend. My GPS was great pre-CM 7.0.3 where I was using CM 6.xxx which is why I was asking.
Thanks for the answers.
Click to expand...
Click to collapse
The reason is because CM 6 was based on froyo and CM 7 is based on gingerbread. Same reason my Enomther's mod works so well. There is a huge post on google's message board regarding the GPS problem in gingerbread, and they have claimed that a fix was released, but it never fully solved the problem I think it's fairly clear that the issue is with gingerbread and that any mod based on gingerbread will have this problem.

I haven't had any issues with GPS on my phone, and I have been running CM7 since the alphas started back in December (or maybe January). I have always had quick locks, and I haven't had it lose it signal while using it (and I use it frequently for both short and long distances). I use the 5.08 radio (but I have used the 5.12 as well, and had no issues with GPS while on it).

bassmadrigal said:
I haven't had any issues with GPS on my phone, and I have been running CM7 since the alphas started back in December (or maybe January). I have always had quick locks, and I haven't had it lose it signal while using it (and I use it frequently for both short and long distances). I use the 5.08 radio (but I have used the 5.12 as well, and had no issues with GPS while on it).
Click to expand...
Click to collapse
Very odd. So you'd say it performs equal to froyo?
I'm inclined to believe that it's not hardware related since, as i mentioned, on froyo it's near perfect -- close to instant lock, definitely within 10 seconds, and it never loses it.
I'm going to try another gingerbread mod soon because I miss some of the GB features. I'm also on 5.08. hmm

I would say it performs better than froyo, but it is probably just because my phone tends to run cooler, so I don't have freezing issues.
Make sure when you install the Gingerbread ROM that you MANUALLY wipe the /system partition from within recovery and perform a Factory Reset/Data Wipe. You can back up your apps and app data with a program like Titanium Backup, but stay away from restoring settings as restoring those could restore any incompatibilities between Froyo and Gingerbread. CyanogenMod recommends doing a full wipe when upgrading between Froyo and Gingerbread based ROMs (well, at least for their own).

My cm 7.1 works well
Sent from my Nexus One using XDA App

bassmadrigal said:
I would say it performs better than froyo, but it is probably just because my phone tends to run cooler, so I don't have freezing issues.
Make sure when you install the Gingerbread ROM that you MANUALLY wipe the /system partition from within recovery and perform a Factory Reset/Data Wipe. You can back up your apps and app data with a program like Titanium Backup, but stay away from restoring settings as restoring those could restore any incompatibilities between Froyo and Gingerbread. CyanogenMod recommends doing a full wipe when upgrading between Froyo and Gingerbread based ROMs (well, at least for their own).
Click to expand...
Click to collapse
Thanks. Works like a charm. Locking gps used to take at a least 10+ minutes, it now lock in less than 10 seconds. BTW using kang-o-rama 1.3 s2e version, which is based on CM 7.1.
P.S. was previously on same Rom before. I just did a full wipe without restoring any system data.
Sent from my Nexus One using XDA App

Try FasterFix
Code:
https://market.android.com/details?id=com.Double.FasterFix&hl=en
and select the server that is nearest to you to see if it improves.

Very odd. Tried a CM 7.1 based rom today, and the same GPS issue persists. I cleared the /system partition and everything else, but the GPS would not lock for one, and if it got a lock after minutes, it wouldn't stay locked. After restoring a backup to froyo, the GPS worked perfectly again.
And yes, I tried GPS tools, I tried fasterfix, but no go.

I'm on 7.1.0 and my GPS locks on within around 3 seconds.

zeesix said:
Very odd. Tried a CM 7.1 based rom today, and the same GPS issue persists. I cleared the /system partition and everything else, but the GPS would not lock for one, and if it got a lock after minutes, it wouldn't stay locked. After restoring a backup to froyo, the GPS worked perfectly again.
And yes, I tried GPS tools, I tried fasterfix, but no go.
Click to expand...
Click to collapse
I have been struggling with the same/similar problem ever since the2.3 upgrade.
The GPS doesn't lock for the first time, it gives up after couple of seconds ( no flashing GPS thingy ) and if locks it easily looses signal and never tries to lock again ( no flashing GPS sign ) unless I restart the app.
very annoying since since I'm using mytracks/sports-tracker to record my tracking/cycling.
is there any workaround? other than buying a new phone?

s.illes79 said:
is there any workaround? other than buying a new phone?
Click to expand...
Click to collapse
I think using a Froyo ROM is the only way certain way to fix the GPS issue but you have to be willing to sacrifice battery life.
I haven't heard anything about how GPS is on the latest ICS builds though, so maybe there is hope?

Stock, Cyanogen and Evervolv all support GPS on my Nexus One, it works fine on all of them. It's probable that you're chip's busted.
Edit: that's Evervolv ICS p13, by the way. Previous versions worked too.

[Q] Phone Unresponsiveness

Hello Community!!
I am seeing a problem with my Revo, and I'm putting it out here because you guys are good at finding answers.
I am running Gingervolt 1.3 with the blitzkreig kernel installed. I have previously tried Hicks' little ICS responsiveness script.
Here is my problem. Most days after little to moderate use, Phone/text, I have to reboot my phone by either soft reboot (power button) or a hard reboot (battery pull) because nothing at all is responding. By nothing I mean, touch the screen..nothing, open a program...nothing...etc.
It is a slow degrade sometimes where (and my wife has mentioned it using my phone) that the touch screen is really really laggy and non responsive, especially when using a keyboard or even trying to play angry birds.
I have done a full wipe including data, cache, dalvik. I have formatted my internal and removable SD card, I have not used previous backups, instead resorted to downloading programs and installing from scratch.
This is a very frustrating issue. If it was a computer I'd say either the processor was overworking, or the ram was used up. But since we don't use program killers in GB I'm kind of at a loss. And I'm tired of having to wipe my phone every few days just so I have meh performance (and no, I'm not hating on the phone, or the rom or any of the developers, nor do I have any interest in changing phones,etc)
I'm just looking for suggestions/solutions etc. I'm sure I missed something in my troubleshooting steps.
Thanks in advance for those who read through this and try to give a hand. I appreciate it.

Wow. Since you've already gone to extreme measures, I'm at a loss. My suggestion would be to freeze the apps you do install to look for a culprit there. Or, don't install any and see how the phone performs.
I restored a nandroid prior to Google's 10¢ apps promo and my phone is back in fine form. It was lagging badly before that. I was rebooting daily. Now I go for days and the phone's solid.
Sent from my VS910 4G using Tapatalk

I was experiencing similar issues about a week after updating to blitzkrieg 1.0. I restored from backup and it's been stable since. I just installed 2.0 today, so I'm curious to see if it'll have the same effect.
Sent from my VS910 4G using xda premium

I can't say yet whether or not 2.0 has added to or taken away from the response type issues. I did have to do a couple of battery pulls yesterday just to get firefox to do anything. I'm going to uninstall that one. I may, just for S&G's do one more factory wipe and put all the tweaks and mods in place before downloading anything but the most essential programs. I did this phone, but the unresponsiveness sometimes can be a real pain.

What do you have it clocked at? I have issues at 1.9 so maybe back it down a bit. I get lots of screen freezes and have had some rebooting issues at 1.9
Sent from my VS910 4G using XDA App

revo_65 said:
What do you have it clocked at? I have issues at 1.9 so maybe back it down a bit. I get lots of screen freezes and have had some rebooting issues at 1.9
Sent from my VS910 4G using XDA App
Click to expand...
Click to collapse
Currently I have it at 1.7, before when it was really bad, the oc wasn't sticking and I was at 1024, so not overclocked much. I am sure its an app that is causing the problem, but I'm not sure what.

I've never had this type of issue using Blietzkreig or any of the other tweaks so I'd guess you're right in thinking it's an app. Since you've pretty much tried everything else I would say maybe try going back to complete stock then rooting again? That just seems like what I would try if I had tried everything else and nothing worked.
And yeah you definitely don't want to overclock too much because it could definitely damage the hardware of your phone since it's not meant to run at that level. But you said you had it at 1.0ghz so it doesn't seem like that is the problem unless the damage was cause when running at 1.7ghz. I had mine at 1.9 and didn't see any issues except my phone randomly started to vibrate for a while then just restart. It did that twice when i first flashed everything but it seems fine now. I brought it down to 1.0ghz just cuz i'm not really using it now and I don't want it causing any problems with the hardware.

Thanks for the Feedback everyone. I am not sure what the issue is/was/going to be. I think Firefox was a big part of it and I have since removed it. But I am still getting random freezes, almost like the deep sleep while the screen is on. Oh well, maybe I do need to go back to complete stock.

[Q] Tried Everything - Touchpad Screen Unresponsive (CM9)

Hi
Looked for this issue on the forum and can find instances of it happening occasioinally, but not with the frequency that i have. Symptomns are that the screen will stop responding to input. I.e the screen stays painted but does not respond to my pokes or pros. Flicking the screen on and off for a split second fixes it. I believe its related to software or resource usage -sometimes i can go for ages without issues, however in the last half an hour this has happened around ten times. please help!
I have tried isolating it down to a particular app with no success, and also changed the CPU governance settings, asgin unsuccessfully. I have no such issues in WebOS.
Thanks.
ps running CM9 alpha 2, but had same issue on 0.6

flash the latest nightly.

screen unresponsive281]flash the latest nightly.[/QUOTE]
Thanks for the reply. I may consider doing that, guess that with a Android backup I don't have much to lose. Would like to avoid it if possible as not being as widespread they aren't as proven and I've ironed out all other issues in alpha 2 such as wifi etc ...
Thanks

the latest nightly offers quite a few fixes.....
including vibration from sleep and tons of other stuff. not much can go wrong.

Andysan said:
Thanks for the reply. I may consider doing that, guess that with a Android backup I don't have much to lose. Would like to avoid it if possible as not being as widespread they aren't as proven and I've ironed out all other issues in alpha 2 such as wifi etc ...
Thanks
Click to expand...
Click to collapse
There has been loads of improvements in CM9 wifi has been fixed sound distortion when the screen off is fixed many speed fixes we now have themes working
Do a nandroid backup in CWM then copy that to your pc for safety then wipe system partition DO NOT FACTORY RESET OR WIPE DATA or you will lose you data, then flash latest nightly and latest gapps then wipe dalvik cache/cache partition's then in advanced fix permission's and reboot system

Well.... I dip my hat to you guys.
Went ahead and installed the latest nightly - even if it doesn't fix my issue, I was suprised by how polished it felt compared with Alpha 2. Typically with bleeding edge stuff I'd have expected to have more issues, but alls I had to do was reinstall YouTUbe and flash the gapps-fixer zip for my Calender sync, plus I see lots of lovely new settings to play with.
Will report back if the screen hangs again, here's hoping...

Frustratingly this issue has started happening for me again running 31 May nightly - touch screen has become unresponsive half a dozen times in the last ten minutes.

Maybe trying wiping it and doing a brand new flash from the latest nightly. (I know it sucks to reinstall stuff, but maybe there are some leftover codes that is causing trouble.. )

i agree either to wiping data or up your min cpu speed as it might the amount of apps you have installed that auto start/resume when turn on the screen..

Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A

I only had that problem once. Rebooted by holding home and power never had it again.
Sent from my YP-GI1 using XDA

Had this issue yesterday for the first time since installing cm9 6(?) months ago.
Tried a nightly build as suggested, but given the rarity in the first place, can't be sure it's fixed

This happens to me all the time across all ROMs I have tested.
This happens in OaT's and turning the screen off/on, fixes it temporarily.
This happens in Butta, but turning the screen off/on does nothing. I have to reboot using power/home.
I have also been unable to find a specific app that causes it, but it does seem to occur more often in graphic intensive games.
I can go for days without it happening, then BAM, it stops responding to touch, from that point forward, no about of reboots or full shutdowns seems to fix it for several hours. I'll reboot and sometimes it'll be immediately, sometimes it will be 3-5 minutes, but it will happen again.
Then a few hours later it'll stop happening and I'm good for a few more days.
Do those of you using CM9 find that screen off/on fixes it, or do you need a full reboot?

I am running the night lies and have to say that the only time I experienced this was with the may nightlies. I have not experienced any issues with the 7/04 nightly.
Sent from my cm_tenderloin using Tapatalk 2

Interestingly enough I think I found out what causes the screen to stop responding. When the TouchPad is locked in landscape and then I turn it portrait while its still locked, then the screen becomes unresponsive. Does that make sense?
Sent from my Touchpad using xda app-developers app

I take it back. The screen became unresponsive even in landscape mode. There goes my well formed and thoroughly investigated theory.
Sent from my Touchpad using xda app-developers app
---------- Post added at 07:54 PM ---------- Previous post was at 07:22 PM ----------
I've been using Nova Launcher ... I switched back to Trebuchet and it appears to be working normally. Of course I may be spouting this half-cocked like I did before. What launcher are you using?

I run SPB 3D launcher and do not experience any response issues with the latest nightlies. I use my touchpad constantly as a laptop replacement so mine gets a workout every day. To my knowledge, no one was ever able to find any one app that was responsable for this behaviour but it was noted in earlier builds.
,
Sent from my cm_tenderloin using Tapatalk 2

I too still have this issue - as per others, fine for days, then it will occur consistently and I keep having to screen off/on and eventually it stops of its own accord. Am sure its a software issue, but someone here says they also had it in WebOS and HP provided a replacement.
http://rootzwiki.com/topic/20740-screen-unresponsive-in-cm9/
For me as simply flapping the screen on/off fixes it and I've never had the issue within WebOS, it has to be software - this started as soon as I first installled CM9.

Bump - still no fix identified for this by anyone with this issue please?

To anyone still following on, followed nevertells advise and completely started again from scratch and it happened after about twenty mins of using the stock browser. I think i've tried not using that app before so am just going to assume that this is either a software bug or a hardware issue that only manifests itaelf within Android

Droid4 Stock ICS Bugs

All,
We don't have an ICS Bugs thread going on. I wanted to check with some of the people here on XDA to see if they are experiencing what I am. Currently on .213, but most of these bugs I've seen since the begining. Oh, I'm also in Canada running on 3G HSPA+. I'm stock, but rooted with safestrap installed.
1) When placing a phone call, the phone hangs up immediately (you here the disconnected beep), then retries the phone call a few seconds later (it always succeeds). I have tried this on a freshly wiped phone and found the same experience. I have also tried disabling the Assisted Dialing, but have found ikt's the same thing
2) When using Google Chrome, if there is a input box, most of the time my keyboard won't appear (I'm using Swype as my default keyboard)
3) Phone runs hot sometimes, and when it's running hot it slows down to a halt. Usually happens after a day or two without a restart
4) My photo doesn't appear in the text messaging app (worked in AOKP/CM9 on my D3, as well as it works on my gf's Nexus S)

The only bug I noticed was that it initially booted up in global mode, and wouldn't connect to 4G/CDMA. Switching it to CDM+LTE fixed the issue and I haven't seen a bug since (213).:good:

podspi said:
The only bug I noticed was that it initially booted up in global mode, and wouldn't connect to 4G/CDMA. Switching it to CDM+LTE fixed the issue and I haven't seen a bug since (213).:good:
Click to expand...
Click to collapse
Is your chrome working properly? Specifically the bug I mentioned in the OP...?

I didn't comment on that because I use Opera
Just tried the Chrome Beta now just to see, and I can confirm I am seeing the same behavior. I use Swiftkey, so it isn't a Swype-specific bug either.
What exactly is the difference between Chrome and the built-in browser? Aren't they both Webkit-based? Why is Google bothering to work on both?

podspi said:
I didn't comment on that because I use Opera
Just tried the Chrome Beta now just to see, and I can confirm I am seeing the same behavior. I use Swiftkey, so it isn't a Swype-specific bug either.
What exactly is the difference between Chrome and the built-in browser? Aren't they both Webkit-based? Why is Google bothering to work on both?
Click to expand...
Click to collapse
Chrome is way faster at many things since it users hardware acceleration for video. Does text input work properly on opera?
Sent from my XT894 running ICS

I'm in the US also running .213
I haven't noticed any bugs, its working fine for me. I do not use chrome beta so I can't comment on that. The stock is not too bad, I don't use it much anyways.
Sent from my DROID4 using xda app-developers app

danifunker said:
Chrome is way faster at many things since it users hardware acceleration for video. Does text input work properly on opera?
Sent from my XT894 running ICS
Click to expand...
Click to collapse
Text entry works fine in both the stock browser and Opera. BTW, Opera also has hardware acceleration, which is why it never worked in any of the Frankbuilds of ICS based off the GB kernel ... So you can have your teh snappy and type with it too :laugh:

I'm on the 212 build and i can't screencap using power + volume down.
Is this fixed in 213 or am i just doing it wrong?
Also on 212 i can't control the default google music app or winamp from my bluetooth headset when the screen is off. I could do this before with the same version of the winamp app when i was back on gingerbread. I tried upgrading winamp, but that did nothing. Is there any change in 213?
Thanks ahead of time
Edit: just tried it and the volume down + power combo worked. Lol

One question, possible thought to ponder.
Are the bugs being described here really bugs of Android 4 or are they bugs in the individual app itself not being fully compatible with Android 4 yet?
Do similar bugs happen on a non-motorola device with android 4?
I'm considering flashing one of the leaks, so I'm trying to understand how you are sure these are ics bugs before I make the leap and run into issues.
Thanks.
Apologies if this constitutes hijacking the thread, if it does let me know and I"ll edit it to delete the question.

I was able to figure out bug #4, I had to login with my Google+ account again, since the update yesterday everything seems to be working fine.
Bugs 1 through 3 still exist, although I've switched off Global mode for now and put it to GSM only, it seems like the phone runs a lot cooler in this mode.
Even after updating Chrome to the final version, I'm still experiencing that text input bug. Maybe it's a Motorola issue... Can't wait for the next version of the leak!

I have tasker reboot my phone every morning at 6am. The phone doesn't need to be rebooted every day, but it ensures that it is fresh and ready to go every morning :laugh:
Nothing more annoying than trying to do something with your phone and having to reboot it because it is slow for whatever reason.

podspi said:
I have tasker reboot my phone every morning at 6am. The phone doesn't need to be rebooted every day, but it ensures that it is fresh and ready to go every morning :laugh:
Nothing more annoying than trying to do something with your phone and having to reboot it because it is slow for whatever reason.
Click to expand...
Click to collapse
for this reason I think there will be other leaks, ICS is supposed to handle killing processes much better than GB, however the settings seem to not be aggressive enough in 213.

Probably there will be, though I likely won't update again for a while. Don't feel like losing all that data...

podspi said:
Probably there will be, though I likely won't update again for a while. Don't feel like losing all that data...
Click to expand...
Click to collapse
You could just do what I do: once you have root install safestrap and then take a backup of your phone before flashing the upgrade.
Once you're all done upgrading, re-root and re-install safestrap, then do an advanced restore and only restore the data. Voilla, all your apps are back.

podspi said:
Probably there will be, though I likely won't update again for a while. Don't feel like losing all that data...
Click to expand...
Click to collapse
I don't know, just had a random reboot after watching a youtube video in firefox, most likely memory related, not sure who's fault though, Motorola or Firefox. gotta root and use system tuner to change memory mgmt states.

danifunker said:
You could just do what I do: once you have root install safestrap and then take a backup of your phone before flashing the upgrade.
Once you're all done upgrading, re-root and re-install safestrap, then do an advanced restore and only restore the data. Voilla, all your apps are back.
Click to expand...
Click to collapse
That is a great idea. Though there hasn't been another leak since 213, so

Notification Bar Sticking/Wont Pull Down
I am on 212 currently, and I have noticed in 208 and 212 something that has happened only twice so far. Today, I just tried to check my notifications, and the bar will not pull down.
After a reboot it works fine, and it has only happened 2 times in the past couple weeks since the leaks first appeared.
Obviously it is a minor glitch, but just thought I'd throw it out there in case anyone else has seen it and overlooked it. :cyclops:

danifunker said:
You could just do what I do: once you have root install safestrap and then take a backup of your phone before flashing the upgrade.
Once you're all done upgrading, re-root and re-install safestrap, then do an advanced restore and only restore the data. Voilla, all your apps are back.
Click to expand...
Click to collapse
I have heard of a few others using this method successfully. If you are not using safestrap or just don't want to go this route take a look at the post link in my signature. It's a modified version of the original Droid 4 Utility and includes a script to jump from one ICS leak to another without losing data. It also flashes the GB files and the Kernel (boot.img) in one script, thus making it easier to go from one leak to another.
Regarding bugs, my wife got a razr yesterday. It wouldn't pull down the ICS update, so I just sideloaded it. We both run some of the same apps. So this gave me a chance to do side by side comparisons.The issue with some of the icons being small in the left top of the status seems to be a app issue. The chrome issue isn't present on the razr, of course there isn't a physical keyboard. Otherwise my 213 ICS seems to run great.

I found a new bug, it looks like GSM call forwarding doesn't work properly... at least it doesn't with my SIM card, I'm on Rogers in Canada.
Does Verizon support call forwarding? Does it work on there?

I have noticed in Chrome that pressing shift and then one of the symbol keys (like @) will only work if you hold the shift key.
More importantly I don't get notifications of app updates from google play. Check to see if you have any apps that need updating. Superuser had a update on July 1, dropbox yesterday and voodoo rootkeeper on June 28, I think. Anyone else?