yashsingh1/xdaforums huggingface dataset:
[G Tablet Q&A, Help & Troubleshooting] rajeevvp:
I think the birds went with the CM7 installation. No birds for me either; instead, I have the skateboard droid. The bootup screens are:

1. Power on; blank screen for ~10 seconds.

2. ANDROID for ~15 seconds.

3. CM skateboard droid for ~30 seconds.

4. Finally, the CM lock screen.

I had some old version of ClockworkMod v2.5.0.x or something that I originally loaded to get TnT-Lite installed, so I went to bekit.net and got v2.5.1.3 and flashed it using the standard CWM installation procedure: choose zip from SD card, install zip, etc. It works fine with CM 7.0.2.

Why not try flashing it using the current CWM?

You like them birds, eh? There's no accounting for taste. :)
[G Tablet Q&A, Help & Troubleshooting] aasoror:
I have to differ, I have been installing every nightly/stable released for the last month and I am pretty sure I rebooted several times under the latest nightly (60) and still had the bootup logo.

Thats not the point :)

The thing is (after looking around) according to this thread, the bootup logo resides on a specific partition of the bootloader, a disappearing bootup logo can only mean one thing, that specific partition was over-written.

This might be a side effect of installing CWM (for me) or just an inconvenient coincidence, either way something has been messed up, hopefully it wont go beyond that.

Thanks for your reply.

I guess this answers my question.
[G Tablet Q&A, Help & Troubleshooting] jpjj225:
Same thing happened to me after I installed the new CWM through rom manager. For some reason it deletes that first boot up screen. I didn't have any problems with that CWM until I tried flashing back to tnt lite. Just don't make that mistake like I did or you will be learning up on nvflash very soon.
[G Tablet Q&A, Help & Troubleshooting] thebadfrog:
dont use Rom Manager
[G Tablet Q&A, Help & Troubleshooting] aasoror:
Thanks for the suggestions guys, unfortunately I am past this point now :)

ROM manager gives you the option to flash alternate recovery (CWM 2.5.1.1-bekit-0.8), I wonder if that is indeed v08 we have been using.

For the splash screen I think uninstall, reinstall can't fix it, I think you would need to go through the nvflash and fix the bootloader.

I will keep this updated as I go through it when I have the time,

Thanks again,
[G Tablet Q&A, Help & Troubleshooting] thebadfrog:
Yes that is the right recovery and you can flash it in rom manager and delete rom manager
[G Tablet Q&A, Help & Troubleshooting] aasoror:
Yup restoring the BLO partition via nvflash fixed it.

Then Run

nvflash --bl bootloader.bin --download (BLO parition #) (filename).bmp

Here is the one I ended up with
[G Tablet Q&A, Help & Troubleshooting] roooler:
Hopefully you guys can help me :(

I am on Vegan Ginger Edition on my Gtab.

I also am missing the "Bird Screen" however i have a bigger problem.

When i am in CWM if i do ANYTHING that has to do with "Cache" the phone freezes and i have to hold power to turn it off.

Formatting Cache

Backing up the ROM (when it hits the Cache part it stops)

WIping data/cache (stops at the cache part)

While it doesnt really affect the Gtab while running. I do know its going to end one day.
[G Tablet Q&A, Help & Troubleshooting] K J Rad:
If you are familiar with and have nvflash installed you might try using it to format the cache. The following command should work (Linux Version).

nvflash --bl bootloader.bin --format_partition 12 --go
[G Tablet Q&A, Help & Troubleshooting] aasoror:
"E:Can't mount /dev/block/mmcblk0p2 (File exists)" ...

Might be a side effect of 2.5.1.8

I found that bootloader partition 7 gets overwritten whenever I boot into recovery.

Have also noted that whenever I try clearing dalvik cache I get the following error.

"E:Can't mount /dev/block/mmcblk0p2 (File exists)"

Apparently this doesn't prevent dalvik cache from cleaning, but I tried to find out why this is happening. I looked around and the general recommendation seemed to repartition SD.

I reverted to v08, confirmed that bootloader is no longer messed up, then tried clearing dalvik, got same error, so went through with partitioning (2048,0), cleared cache, data wipe and facory reset went fine. YET, dalvik cache gave the very same error.

Any insights ?
[G Tablet Q&A, Help & Troubleshooting] aasoror:
bump ... ....
[G Tablet Q&A, Help & Troubleshooting] davidukfl:
i get that same error with wiping the dalvik. I think i get the same error on my nook color too. I'll double check tonight when i get home.

I also lost the boot screen when i flashed CM7
[G Tablet Q&A, Help & Troubleshooting] rajeevvp:
Alright, I got my birds back too. Thanks for bringing this up, aasoror.

It seems like I have the gTablet with the non-standard NAND flash partition table. For me, the boot logo is on partition 7 and the MSC (misc?) partition is 6.

So, I downloaded bekit's alternate backup file, nvflash_gtablet_46_2010112600.zip, and reloaded both partitions 6 and 7. The birds came back, and restored the MSC partition which was probably scrogged by CWM. Everything's cool now.

aasoror, that "E:Can't mount /dev/block/mmcblk2p2 (File exists)" means that you don't have an external SD card in its slot. The message goes away if you insert one.

When you select "Wipe dalvik Cache", CWM mounts both /dev/block/mmcblk3p2 (the internal SD card, partition 2) which mounted as /data and /dev/block/mmcblk2p2 (the external SD card, partition 2) which is mounted as /sd-ext, to rm -rf the dalvik-cache on both of them. And it will throw that error message if the external SD card is not present.
[G Tablet Q&A, Help & Troubleshooting] davidukfl:
how do you reload individual partitions with nvflash?
[G Tablet Q&A, Help & Troubleshooting] ttlycnfuzd:
here's the thing with this - if you have the reversed partitions, you will always lose the birds when booting into recovery. the _46_ file has been removed since CM7 does not play nicely with this. as a general rule of thumb, you should NVFlash with the *correct* partition structure should you lose the birds, or bootloop continually when trying to load CM7.

Also, as badfrog said - do not use rom manager. some users have no issues, most do. unless you want your device to boot into apx mode everytime you boot up, stay away.
[G Tablet Q&A, Help & Troubleshooting] rajeevvp:
See post #8 of this thread. On Linux, basically:

sudo ./nvflash --bl bootloader.bin --download 6 06_MSC.img
sudo ./nvflash -r --download 7 07_BLO.img

The second and subsequent nvflash commands need a `-r', resume, flag. And, you only need to load and run the bootloader.bin file once.

That's interesting. I've gone into recovery mode a few times after restoring partitions 6 and 7 just now, and have not lost the birds yet. I've even taken a backup. Maybe it is the CWM restore that will cause problems?

And, I don't use ROM Manager. In fact, I've gone to a bit of trouble to remove the default one that came with CM 7.
[G Tablet Q&A, Help & Troubleshooting] davidukfl:
i reflashed the MSC (5) and BLO (6) partitions but still no birds.

I guess i will just leave it be. It's not really that big a deal
[G Tablet Q&A, Help & Troubleshooting] aasoror:
man I feel so stupid now, went through a whole cleaning round for nothing (facepalm smiley should go here).

+1, I can confirm that its not recovery related but rather the specific version of CWM (v2.5.1.8), I have never lost my splash screen until I upgraded to this version, never lost it since I downgraded back to v08.

btw rajeevvp I have the same partition assignment as yours, that said, why did you restore partition 6 ?
[G Tablet Q&A, Help & Troubleshooting] drx69:
i have been running 2.5.1.8 since i couldnt get 0.8 to keep from locking up on me. I had to use nvflash to get it back. I havent had a problem since then. I am beginning to think there are 2 versions of the gtab out there. I got mine from w00t and the 3588 softare that came with it is NOT the same as the 3588 in the nvflash tutorial. Also, I had all sorts of problems until i used nvflash on linux. I was trying it on windows and i think there is something broke there. But after trying on linux... havent had a problem since.
[G Tablet Q&A, Help & Troubleshooting] thebadfrog:
There are at least 2 versions of the gtab. We know for certain that there are 2 different partition structures and 2 different hardware setups. I believe there are different internal chips being used that don't quite work the same which is why what works for one person will soft brick or APX brick other devices
[G Tablet Q&A, Help & Troubleshooting] ttlycnfuzd:
aahh... yes, I stand partially corrected. if you have the reversed partitions, and try to enter recovery via a widget, or CM7's power/reboot/recovery, then you will lose them. basically 6 & 7 being reversed causes what should be the misc partition to be erased, but in these cases, the blo (boot logo) partition gets erased. This is where you see "erasing MSC" in the text that appears when you reboot into recovery that way
[G Tablet Q&A, Help & Troubleshooting] rajeevvp:
Because I was worried that something like this had happened:

Thanks, ttlycnfuzd. I'll keep this in mind.
[Eee Pad Transformer Q&A, Help & Troubleshooting] Mhotep06:
Is it possible to have a First Impressions thread and have it stickied to the top. Think it would help new users.
[Eee Pad Transformer General] csmall:
I have a dead pixel, just one that I noticed. Should I be concerned? Worth returning? CAN I return for one dead pixel?
[Eee Pad Transformer General] Jocelyn:
It depends where it is IMO. The dead pixel return policy depends on where you bought it from. Places like TD, walmart, and Amazon are generally pretty cool about it, while Newegg has an x number of pixel policy (8 I think?).
[Eee Pad Transformer General] bills742:
I've got several dead pixels (and a dust particle) and I'm returning. But mine is through amazon so their return policy is great. I think it might depend on who you bought it from but most places should return for any defect. If not, just return for refund and buy somewhere else, if you can find one.
[Eee Pad Transformer General] Jocelyn:
How many? I really didn't want to run a test, but I just did and have zero dead/stuck pixels!
[Eee Pad Transformer General] csmall:
OK, how about directely from Asus.
[Eee Pad Transformer General] Jocelyn:
I believe it has to be at least 6 with Asus.
[Eee Pad Transformer General] nxp3:
How do you run a test?

I think if it's just a couple I'm not going to worry about it. My eyes aren't great and I won't notice it. I'd just have a short funeral for the couple of dead pixel and move on. But if it's more than 8-10..yeah I'd return it.
[Eee Pad Transformer General] Jocelyn:
https://market.android.com/details?id=app-net.ujacha.deadpixel
[Eee Pad Transformer General] csmall:
Mine is not in a place that bothers me. I just hoping it doesn't mean there are more to come.
[Eee Pad Transformer General] bills742:
I have at least 3 that I saw easily, 1 almost dead center of the screen. Didn't conduct a full test with the appropriate setting (dark room). 1 in the right location is enough, especially with amazon's return policy.
[Eee Pad Transformer General] Jocelyn:
1 in any location with Amazon. They take everything and anything back, not to mention they pay for return shipping and send the carrier to you for pickup.
[Eee Pad Transformer General] dec3ption:
I'm in a similar situation with the light bleed issue.... don't know if I want to send it back because I could very easily get one that's the same or worse.:mad:
[Eee Pad Transformer General] turbulent28:
crap...

everything is perfect except the ONE dead pixel i saw...

Walmart purchase so im returning this damn thing. but theyre out of stock prob...
[Eee Pad Transformer General] mocelet2000:
Another one here, it has appeared after 8 days of the purchase date.

It's near the right hand border and with the red component dead, so it's not bright when screen is black but isn't white when screen is white. Not very noticeable, but I thought dead pixels were a thing of the past...
[Eee Pad Transformer General] chatch15117:
I'm debating whether or not to return mine. I got mine from CompUSA. There is either a dust particle or a dead pixel on the right side of the screen.
[Atrix 4G General] wookiebush:
Since 1.8.3 I have noticed 2 very annoying issues:

1: Several times a day, my Atrix will stop detecting a finger swipe. No error, just no response. I must reboot to regain finger scanning.

1: Screen Timeout: The screen will frequently, but not consistently go off after only a couple seconds of idle time. It doesn't dim first and if you hit the power button it comes back to the screen you were on, not the lock screen.

Both of these issues happened with vanilla 1.8.3 and with Gingerblur and NEVER before the update.

Anyone else?
[Atrix 4G General] drock212:
Fingerpring issue for me as well but also the button sometimes wont put my phone in sleep and ill have to pull battery cause its unresponsive but never the screen issue you're having. This update is full of bugs they need another update fast just to fix what this one broke. Oh and I think about 90% of people that updated have reported an issue with the fingerprint scanner

But thats just my 2 cents :)

Sent from my Atrix
[Atrix 4G General] wookiebush:
If both of these issues are known and have been reported, feel free to lock or delete. I searched and didn't find any thread titles about this, but did not read every 1.8.3 thread.
[Atrix 4G General] lanyao1920:
I met the fingerprint issue too after 1.8.3 upgrade
[Atrix 4G General] Paschalis:
i had fingerprint sensor issues too, when i had stored fingerprints and restored settings for fingerprint sensor using Titanium backup. A wipe data may solve this(int titanium backup).

in 183 there is a new setting in Location And Security!

The phone is not necessary anymore to lock, when the screen goes off.

the screen can go off in 5 mins(in display settings)

and the mobile can locked in 10 mins(in location and security)!

i like this setting! :)
[Atrix 4G General] charlyee:
Where is the new setting in "Location and Security", I am not finding it. Thanks
[Atrix 4G General] GoodFoot:
I don't see it either in 1.8.3. The item "Security lock timer" that would be used for this is disabled (grayed out).
[Atrix 4G General] Djordjije:
fingerprint issue here too just experienced for the first time yesterday.

i swipe it and there is no response.

good that there is a list of people here with the same issue so motorola can acknowledge it as a legitimate bug and hopefully fix it
[Atrix 4G General] wookiebush:
Can someone else verify this? When I change the screen timeout from 15 to 30 seconds, then reboot the phone, it switches back to 15 seconds.
[Atrix 4G General] slivuh:
this sounds like the GingerBlur 3.0 bug...upgrading to 3.1 fixed this for me
[Atrix 4G General] GatorRuss:
I am having issues with WidgetLocker and the fingerprint recognition, has anyone else experienced this issue with WidgetLocker? I have been having no issues, with the fingerprint scanning, once I turned off WidgetLocker.
[Atrix 4G General] Paschalis:
Yes.

You are right!

I now recorded again fingprnts and that setting grayed out!!

I didn't used fingerprints cs some probs I had after restoring settings from backups, and waited to have 183 with 3.0 gingerblur..
[Atrix 4G General] mk1151:
I found that powering off the device, pulling the battery for a few minutes, re-installing the battery, turning the Atrix back on, then wiping and re-doing the fingerprints permanently fixed my issue.
[Atrix 4G General] drock212:
This issue is not the same issue as when TiBu backs up fingerprint data. This is an issue with the scanner being none responsive. OP this issue has bot be talked about here but on the Moto forums it's been reported by many users.

But thats just my 2 cents :)

Sent from my Atrix
[Atrix 4G General] bandityo:
I also had my first fingerprint issue since owning this phone for the first time yesterday after getting 183. Never had it ever before...somethings wrong with this update if multiple people are getting it for the first time now.

David
[Atrix 4G General] lsxrx7:
add me to the bad fingerprint group
[Atrix 4G General] blehke:
Same issue with Widget Locker. Sometimes when I hit power, I can swipe finger and all is good. Other times, swipe does nothing - I have to slide the screen lock, then I can swipe (or enter PIN).

Can't seem to find any pattern to when it works or doesn't, but it does do this pretty often. Good thing is, it doesn't completely lock up - if I don't get the double-vibrate for a bad finger swipe, I know that I need to do the screen slider first.
[Atrix 4G General] DarkRyoushii:
Just to add to the people on the list, I experienced the fingerprint issue once, hasn't happened since though
[Atrix 4G General] lsxrx7:
the best thing to do is actually complain on the motorola support forum ...

i already did

https://supportforums.motorola.com/thread/50138?tstart=0

moto engineers actually look at that forum ...
[Atrix 4G General] quordandis:
So I read this thread and thought to myself, "Self, Thank G-d you don't have this problem." And then, of course, I jinxed myself. Add me to the fingerprint issues list!!

I did a power-off, battery remove, battery install, power-on, remove fingerprint data, reboot, then redo fingerprint calibration. If you don't hear back from me, assume it resolved the issue....otherwise, I'll report back....

How absurd?!

--Q
[Atrix 4G General] nigebj:
I have a reliable pattern to cause the sensor to become unresponsive (i.e. totally ignores the swipe - but PIN works to get in).

I usually have Bluetooth off, and have never had this issue with 1.83. Recently received a Moto T505 speakerphone for car. Steps.

Enable B/T on Atrix.

Use Audible to play audiobook through T505.

Stop Audible player.

Quit Audible.

Next attempt to start from timed-out sleep will have unresponsive f/p reader.

Same behavior whether B/T is disconnected after using Audible or not.

This does NOT happen if I just use the T505 for regular calls.

I do not have music on the Atrix yet, so cannot say whether it is the Audible app, or streaming music to the T505.

Bizarre circumstance, but this never happens if I do not use the Audible app. Yet the above steps will reliably cause this.

Atrix 1.8.3 OTA, rooted using Gingerbreak.
[T-Mobile LG G2x] JWhipple:
I've been through 2 G2x's , both have had the same problems...

Random reboots

Random freezes

Random shutdowns

Crazy inconsistencies in battery life

I've also gone the route of rooting and trying CyanogenMod with the same results.

With the battery issues, I did the following test 3 nights in a row.

Phone wiped, 100% battery charge, signed into Google and let the apps download, rebooted phone, data connection turned off (airplane mode), unplugged the phone and set in the exact same spot in the same room 3 nights in a row at 11PM.

Come 8AM when I woke here's the results:

Day 1: 30% battery remaining

Day 2: 80% battery remaining

Day 3: 0% remaining - battery was stone cold dead - wouldn't boot until I plugged in.

Phone was fine when I started typing this post, but just now while typing this message I reached over to check my phone for text messages (I keep the alerts volume all the way down while at work) and it's locked up again...

Guess I'll be returning the phone for a refund and borrowing an old flip phone for a month until the Sensation comes out.

Sorry LG - when it works, it works AWESOME, but I need something a bit more reliable considering that work needs to contact me on the phone and I am on call 24/7 !
[T-Mobile LG G2x] aironeous:
In the 2 weeks I've had it I've only had 2 random freezes and no other issues at all. This is my first android phone and the thing i see that's screwed up with android is it leaves applications open, there is no exit buttons on apps. I've been using juice defender and uninstalling any apps that keep popping back up after ending task on them.
[T-Mobile LG G2x] mobilehavoc:
Sorry to hear about your problems. You're doing the right thing by returning it and getting another phone. I don't understand why people have loyalties to corporations who could give 2 craps about you. Buy what works for you and makes you happy.

For me, the occassional reboot on the G2X is a pain but the promise of a stable CM release and an official gingerbread release on this hardware has me sticking it out. Can't wait :)
[T-Mobile LG G2x] kangxi:
I haven't had any issues with my phone except battery life. Buy my battery life isn't as bad as yours. It used to be horrible but I got a new sim and that seemed to make it better.

Regarding the reboots, some apps are causing the phone to reboot. Either the apps aren't optimized for the phone or the other way around. I had one reboot and after I removed the offending app, never happened again.
[T-Mobile LG G2x] JWhipple:
Actually, when I bought the phone I had them put a brand new SIM card as mine was getting to be a little long in the tooth - if getting a new one helps the situation I'd hate to see how it was with my old one :-D

Removing an offending app would prove to be a real problem for me though, as everything that I install has a legitimate work-related function.
[T-Mobile LG G2x] CB620:
im returning mine today for a newer batch one. its may 4 so i expect one that has the date of 4/24 and up as stated in other threads. mine reboots and freezes during random functions.
[T-Mobile LG G2x] Prod1702:
I ordered mine on the 20th so the day the phone was out in the store. I had to order mine online since i am a T-Mobile RSA. I have alittle screen bleed but not much. I will be doing exchanges until i get one with no bleed. Other wise i have had no problems at all. No reboots, lock ups, data problems, nothing the phone is rock solid. I love the phone. Every person that has come into my store with problems i have told them that T-Mobile is going to exchange this for you under the lifetime warranty if you have it for the life of you having the phone. So you have nothing to worry about. The phone is a great phone to have. Do the exchanges until you get a working one. I know i would do it until i did. Even if it meant doing it 100 times.
[T-Mobile LG G2x] diablos991:
A better test would have been to not install any apps. Then you could truly test your phone and not some rogue app, that you keep installing.
[T-Mobile LG G2x] JWhipple:
I'm about to do a complete wipe again and use a secondary Gmail account I have so to eliminate any apps from auto-installing and test throughout the day since I have my work PC handy.
[T-Mobile LG G2x] player911:
or just skip the Gmail sign in process at first and add your Gmail account later from Settings. This will prevent it downloading your apps on first boot.

Also to the New Android User: Back closes apps, Home leaves them open. It isn't the OS's fault if you don't know how to use it.

To the OP: Have you rooted and flashed the Pre-Dexopt Patch from Paul?

http://xdaforums.com/showthread.php?t=1051616

LG left the phone in Dev mode and doesn't dexopt the phone on initial bootup. This is why our phones boot so quickly. The downfall is after a few hours, it starts to lag out and lock up/reboot.

Sounds exactly like the problem you are having.

This patch is required for stock and EaglesBlood Roms excluding CM7. This should be fixed in the upcoming Gingerbread update. I also believe EaglesBlood and future roms will start coming with this patch included.

So do yourself a favor and patch it.
[T-Mobile LG G2x] kangxi:
Basically, it's an awesome phone and many, if not all, of the issues should be resolved with software updates. Gingerbread is already in the works.
[T-Mobile LG G2x] JWhipple:
Yep, have tried without the patch initially and then with it.

I have signed in with the secondary Gmail account - only thing I imported from the original was my contacts, so, it's 100% stock with the exception of Paul's patch and recovery.