yashsingh1/xdaforums huggingface dataset:
[Atrix 4G Q&A, Help & Troubleshooting] stratax:
+1 cant agree any more with that!
[Atrix 4G Q&A, Help & Troubleshooting] neer2005:
Suit yourselves
[Atrix 4G Q&A, Help & Troubleshooting] madnav:
reply embedded in the quotes
[Atrix 4G Q&A, Help & Troubleshooting] Paschalis:
Just, unlock the phone, install the new CWM recovery, and wait..

wait for a ROM release, or just wait for more positive feedback, may convince you to flash the leaked 2.3.4 .. just what i do..
[Atrix 4G Q&A, Help & Troubleshooting] congtin2005:
I decided to wait but can't wait until ATT releases the update, so I rolled with it.
[Atrix 4G Q&A, Help & Troubleshooting] dubyajaysmith:
On 2.3.4 and love it. Going to try tenfars when I get off but I love flashing and its been so long since I bought the atrix ... another flashoholic relapsed ^_^ but if you're content then wait. I don't care if some things are semi broke, not enough it can't be my daily driver for a few days. Don't see myself going back to 2.2-

posted via Atrix in lapdock
[Atrix 4G Q&A, Help & Troubleshooting] nsaia:
Yeah. I'm waiting too. I have no real need for cwm until there's some actual stuff to flash. Once the att version of 2.3.4 is released there will be a ton of development done. Hopefully the unlock will be built into the update as Kenneth indicated. I can wait until then.
[Atrix 4G Q&A, Help & Troubleshooting] phro321:
Noa that I know I have an option I'll judder wait. Thanks again everyone who helped.
[Atrix 4G Q&A, Help & Troubleshooting] CHUI2CH:
Lol one plus of flashing is now I can use my ESPN radio app, and Netflix woot
[Atrix 4G Q&A, Help & Troubleshooting] kan51:
a week or two till we get the official update to 2.3.4.
[Atrix 4G Q&A, Help & Troubleshooting] vanstorm:
I'm doing the same. Waiting for official release but reading everything I can on the subject so I'm ready when it happens.
[Atrix 4G Q&A, Help & Troubleshooting] Sir_Brizz:
Personally I'm waiting because Exchange support is something I can't do without (and the third party solutions on the Market really don't work for me). I also just want to see what Motorola does with their GB release, if it's good enough I'll wait for CM to release for the Atrix.

I have no problem unlocking and flashing at all, I'm just cautiously optimistic about the rom everyone is using right now :)
[Atrix 4G Q&A, Help & Troubleshooting] gnahc79:
The HKTW 2.3.4 bug thread is keeping me at bay even more. Questionable battery life is a big one for me :). All of these workarounds to keep 2.2.2 functionality is not something I consider stable. Usable for dev/test/sandbox usage to try out stuff? Definitely. But not much else IMO.
[Atrix 4G Q&A, Help & Troubleshooting] G_0:
That's my same thought here.

Whats the point of installing something "Newer" if you lose all that functionality? Its fun to play if you can, but I need my phone to be working. So for right now I'm waiting until the official, or another option.
[Atrix 4G Q&A, Help & Troubleshooting] demens13:
Dont see any reason to unlock now either and deal with fixing all the bugs.

What do you need CWM for if there are no ROMs to flash right now? And isn't there a version for the locked BL as well?

I definitely dont need this yet. Gingerbread isn't even that big of an upgrade, especially a buggy one that isn't meant for your phone.

Plus i'd like more info about if this is reversible incase some problems come up that require warranty service. Right now people are saying its not.
[Atrix 4G Q&A, Help & Troubleshooting] 2leaponover1:
I thought you had to be unlocked/rooted to flash the themes. That's the big deal for me I like designing and customizing my home screen. Is this true or not? I want to have different symbols and colors up top instead of what it comes with.
[Atrix 4G Q&A, Help & Troubleshooting] Sinful Animosity:
All you need is root to flash a theme. Since we have Tenfar's bootstrap recovery still. But that requires you to be tethered to the wall to boot into that recovery.

With the unlocked bootloader, we can boot up anywhere at anytime.
[Atrix 4G Q&A, Help & Troubleshooting] ccrows:
You pretty much answered your own question.

If you are currently happy, then why mess with a beta?

Rumor has it that the official update might be coming somewhere in July.

That will also give extra time for more 3rd party Apps in the market a chance to catch up with Gingerbread too... :)
[Atrix 4G Q&A, Help & Troubleshooting] rpolansky:
I am waiting...seems like too many bugs (and I am very pleased with the way my Atrix runs now).

And I saw this posted by the moderator on the Motorola Atrix forum:

Being on official software will also be a pre-requisite. So to any of those impatient folks... Well that probably wasn't a good idea.

I assume you can flash back an sbf if you want the ota update when it comes out but I don't want to hassle with that if I don't have to....

See:

https://supportforums.motorola.com/thread/45654?start=855&tstart=0

This refers to Gingerb but still I don't want to take a chance.
[Atrix 4G Q&A, Help & Troubleshooting] GoodFoot:
Lack of fingerprint reader functionality is a big hold up for me. I'll wait until that's working before I load anything new.
[XPERIA X8 General] proadi96:
Hi as everyone knows nokia n8 has synaptics digitizer and it has Software Emulated Dualtouch ... is someone know some dev ( or at least some person) that have n8? If nokia can have dualtouch i want it too! But i dont know how to do it ;p
[XPERIA X8 General] anmiman:
but n8 is symbian...and symbian is wayyyyy different than android.
[XPERIA X8 General] proadi96:
Ehhh all right so we cant do nothing ... im dissapointed ;D
[XPERIA X8 General] josip-k:
Its probably because n8 has 2 sensors, and x8 has just one.
[XPERIA X8 General] sukartochen:
What the fuc k tread here..., why so hard for you to use search button in this forum.. there are million f uck tread llike this before...., stop spamming here with this usseles thread.., stop complain you phone and buy new phone if you want play game with multi touch..., please mode delete this fu ck thread..
[XPERIA X8 General] proadi96:
But if they have the same digitizer they supposed to have the same amout of sensors no?
[XPERIA X8 General] josip-k:
I dont think so... i dont know...
[XPERIA X8 General] josip-k:
Haha, you are ****in' stupid sukarotchen
[XPERIA X8 General] codfreak:
There IS already a fake DT for synaptics and a real DT for Cypress.
[XPERIA X8 General] proadi96:
But n8 and nexus one has synaptics and they has software emulated dt ! Nexus one has android so we can have it too!
[XPERIA X8 General] SpliFFdu95240:
Not right !

No fake DT, only pinch zoom !
[XPERIA X8 General] codfreak:
Oh sorry, I´m just confused about all the MT threads.
[XPERIA X8 General] proadi96:
Ehh maybe synaptics users just need to accept that it cant run dualtouch ... but without dx we will not have pinch zoom ! Big thanks doixanh :)
[XPERIA X8 General] Aiduharan:
apparently the some of the samsung galaxy s2 phones with the tegra processor have the cypress equlizer
[Windows Mobile Development and Hacking General] matixslp:
Hi all,

I have a LG GW550, it's the worst phone I've ever had!

Ok, let's face it, it's bad but I won't replace it!

The phone has 3 dedicated button, which launch 3 differents app all programed by the manufacturer. Those app are: smart contact, mail and app, and are completely useless and unoptimized!

I would like to re map the button so I can open the alarm clock, celetask and speed reader.

I've played a little and figured out that the buttons open the .exe of each app on \windows.

So, i tried to delete .exe's unsuccessfully! Tried to rename celetast.exe as SmartEmail.exe and copy over the original, but all my effort was useless, ergo ... I'm here asking for help!

Thanks in advance!

matixslp
[Windows Mobile Development and Hacking General] manhab:
make a hard reset
[G Tablet Q&A, Help & Troubleshooting] tech2pc:
Long story short...was running Vegan-tab Gingeredition fine for about 2 weeks then one day got real slow and started to get endless reboot issue. NVflashed back to stock but noticed that wireless would not turn on. When activated it tried to start then gives "Error" message. I flashed to a few different ROMS and still have the same issue.

Anyone now how I can resolve this issue. Ready to throw in the towel. Thanks.
[G Tablet Q&A, Help & Troubleshooting] goodintentions:
Sounds lioe hardware problem.
[G Tablet Q&A, Help & Troubleshooting] tech2pc:
Yeah was thinking that myself. Maybe someone had the same issue and resolved it. We'll see.
[G Tablet Q&A, Help & Troubleshooting] dexdash:
yeah if you have done all the steps- reformatted cleared cache and dalvik like you are supposed to, it probably hardware. only other thing i could think of is trying to completely discharge the battery much like you would do with a computer "unplug" to reset a freeze up- really grasping at straws here.
[G Tablet Q&A, Help & Troubleshooting] ramerco:
make sure you are doing a data wipe/factory reset even after you nvflash. Alterntively, you can repartition teh internal SDCARD from within CWM.
[G Tablet Q&A, Help & Troubleshooting] goodintentions:
Personally I don't think that's the problem. But doesn't hurt to try.
[G Tablet Q&A, Help & Troubleshooting] tech2pc:
Tried it but still not working. Will try battery drain and see what happens.

Thanks for all suggestions.
[G Tablet Q&A, Help & Troubleshooting] dexdash:
i know you have tried different roms, but have you tried different Kernels? could be some weird issue for that too.
[G Tablet Q&A, Help & Troubleshooting] Mantara:
Good point. I would flash pershoots and clemsyns latest kernels and see if it changes your results.
[G Tablet Q&A, Help & Troubleshooting] ljohnso16:
kernel! that would make sense, im pretty new to the gtab but for the last few days i have been trying to load diff roms, with little success, but during my flashing on a restore to 1.2 i noticed i have a wifi problem, but i dont know how i could have hardware issue, this thing is brand new and its my babby i dont even drop it or throw it, not ever so i dont think the issue (in my case at least) is hardware issue.
[G Tablet Q&A, Help & Troubleshooting] mreik:
Bump on this, I'm experiencing the same thing.. Any input from OP or otherwise?
[G Tablet Q&A, Help & Troubleshooting] tech2pc:
Unfortunately never found a fix for it. I even took the gTablet apart to make sure the antennae wires weren't disconnected which they weren't. I believe it's a hardware issue. Tried getting Viewsonic tech support on the line but no response.

Let me know if you find anything out on your end. Good luck!
[G Tablet Q&A, Help & Troubleshooting] mreik:
I'll probably try to get it back to stock and send it back to Amazon under the assumption it's a hardware issue. Thanks for the quick reply, bc this is really bothering me..
[G Tablet Q&A, Help & Troubleshooting] rajeevvp:
If there is a hardware error, it may show up in the kernel or Android logs. See this thread, and get me the kernel logs first using dmesg.
[G Tablet Q&A, Help & Troubleshooting] jmbach:
I have a problem with intermittent wifi error on Flashback 8.x. Occasionally when I shut down and restart my tablet I get 'error' displayed next to wifi. Powering down and up may or may not fix it. Sometimes wiping cache via CWM works and will fix it quicker. I have attached a zip file that has two dmesg and logcat files one marked good and one marked bad. These represent working and non working wifi. Maybe somebody can make something of it.

Jim
[G Tablet Q&A, Help & Troubleshooting] rajeevvp:
Your Wi-Fi hardware seems to be flaking out. There are clear errors in the dmesgbad.txt file:

<4>[ 66.035915] bcmsdh_sdmmc: probe of mmc0:0001:1 failed with error -110
<4>[ 66.048711] bcmsdh_sdmmc: probe of mmc0:0001:2 failed with error -110
<4>[ 66.066313] bcmsdh_sdmmc: probe of mmc0:0001:3 failed with error -110
...
<4>[ 98.368522] dhd_module_init: sdio_register_driver timeout

Error -110 is a timeout error. It means that the SDIO subsystem (through which the WLAN connected to the main board) failed to respond to a command sent to it.
[G Tablet Q&A, Help & Troubleshooting] jmbach:
Hi rajeevvp,

Saw those as well but did not know what error -110 meant. This only happens intermittently when going to sleep and waking up or if powering down and up. Also I do not seem to have this issue with CM7. Not sure if CM7 and FB 8.x handle initiation routines differently for wifi and this may be a problem or if it is how the drivers handle startup. I downgraded the drivers once from a post you made elsewhere and the problem was less often but not nil.

Will be willing to do more testing/debugging if you want me to or try mods to the system. Would be interesting if there was some way of polling the hardware to get more lower level information.

Anyway I am game if you are.

Jim
[G Tablet Q&A, Help & Troubleshooting] rajeevvp:
If I had to hazard a guess, I would say that your hardware is the problem--it doesn't initialize itself properly everytime it is activated (either when powered on or when coming out of sleep). Consider sending it back.

Those error messages are from the kernel (the WLAN driver, to be precise), so this is not a ROM issue. If you didn't have problems with CM7 (which version BTW?) it is likely because it had an older pershoot kernel.

If you want to try "fixing" this problem using software, your best bet is to try one of the older pershoot kernels, going back one by one, until the problem "stops"--but I doubt that it is the kernel for these reasons:

1. Pershoot hasn't modified the WiFi driver source and firmware binary blobs since April '11, so both the CM7 you had on before and the current ROM will very likely have had the same drivers. If you have a problem with the current ROM, you will very likely have a problem with CM7 if you go back to it now.

2. The SDIO/SDHC/MMC subsystem is screwy on some VS hardware. VS has a device called the gTablet, but, with slightly different hardware inside it. For eg: some people have had problems with one kind of internal SD card. Keeping this in mind--and what follows here is very speculative--I see that you have a slightly different WLAN HW: Most users, going by the collection of dmesg outputs that I have, have a MAC address (manufacturer) prefix of 'e0:2a:82'. You have: '00:27:13'. Both are assigned to the "Universal Global Scientific Industrial Co., Ltd.", but, does the difference mean slightly different hardware? I don't know, but, keep this in mind anyway.

Still, as I said, I think it's a hardware problem (or a hardware problem caused by messing around improperly with nvflash).

To verify that it's a hardware problem, try Clemsyn's kernel for your ROM. It's closer to the VS stock kernel than pershoot's is. Finally, you could also revert completely back to stock VS firmware.
[G Tablet Q&A, Help & Troubleshooting] jmbach:
If it is a hardware problem due to nvflash then is there a solution using nvflash. Also if it was due to nvflash would not the problem be consistent and not intermittent? I guess that would depend on what changes you think nvflash may have caused. All I have used it for is to flash between 1.1 and 1.2 BL using roebeet's packages.

Will try your suggestions. If it is consistent across kernels/ROMs then I agree it is hardware based.

I'll report back my findings once I am done. Might take a while since it is an intermittent problem.

Thanks for your insight.

Jim
[G Tablet Q&A, Help & Troubleshooting] TEK112:
This may sound elementary, but I am surprised no one has suggested manually pushing the wifi module to the ROM. Pershoot has had users experience this error countless times and reflashing the kernel did not work in all cases. What did work was manually pushing the wifi module through ADB or root explorer. That is my suggestion.
[G Tablet Q&A, Help & Troubleshooting] rajeevvp:
Quite possibly. But, then you'll have to do what this user wanted to do, which I thought was the right idea then, given that the BCT contains a lot of delicate system-related data.

Can't say for sure, but, I would really think it over before deciding to overwrite my BCT and ODM data with someone else's BCT and ODM as happens in a full nvflash. I don't have that much of a problem with users using nvflash on individual Android-specific partitions and the bootloader partition.

No, that's not the case here, TEK112, for a number of reasons. Go through his log messages.
[G Tablet Q&A, Help & Troubleshooting] TEK112:
I am not an android developer, so please bare with me. I don't understand given the log why a module push would not seem like a thing to try. Please help me understand.

I am not convinced it is a hardware issue. It very well could be as these devices don't exactly have a low failure rate. However, I would expect a greater error, like a backplane error to show if it was hardware as the odds of the wifi module itself to fail are low, in comparison. It timed out trying to register the device. It sounds like a corrupted driver for the wifi module. Perhaps corrupted data that was never completely removed. That would seem to me like a more plausible solution as a hardware failure is pretty much binary or very erratic. The fact that the wifi error only presents when the device is used after a while and a clearing of the local cache fixes it up makes it highly suspect. I would suggest a cleansing enema above and beyond an nvflash, something equivalent to Calkulins format all, but compatible with the 1.2BL. After that, a clean install of 4349 TnT and see if it persists.

Like I said, I'm not a dev, but I know just enough about linux to make me dangerous. Please let me know what you think.

Thanks.
[G Tablet Q&A, Help & Troubleshooting] rajeevvp:
Let's get the obvious out of the way first:

1. User says he is running FB 8.x which according to that ROMs changelogs have pershoot kernel 2.6.32.46.

- Verify that the kernel matches what user says using dmesg output. Versions match.

- User has not indicated that he has reflashed a new pershoot kernel.

- Even if he has flashed a new kernel but not moved the bcm4329.ko to the proper place for HC, it doesn't matter because he will be using the exact same modules anyway.

2. OK, with the obvious out of the way, let's look at the non-obvious, and in this case, unlikely, possibilities.

a) He had 2.6.32.43 originally (unlikely given what user says), but, then flashed to a newer 2.6.32.46, so user has a new kernel but old WLAN drivers. Replicate the condition and you'll find that the driver will load and the WiFi will work fine.

b) There is both a version mismatch and a bootloader type mismatch for the modules. ie. a new 1.2 kernel and an old 1.1 WLAN kernel module. Again, if you do the test, you will see that the WiFi works.

c) Everything matches up, but, he used Froyo modules instead of the GB/HC ones. If you test, you will see that the module loads fine, but, this time the WLAN does not work.

Whatever the combination, there are no hardware-related error messages like the user's.

(The reason for the pershoot kernel being so tolerant of these kind of mismatches is that the drivers have not been modified much since around April this year. So you could go back quite a bit before the kernel fails to load the drivers with some kind of module incompatiblity message.)

Frankly, this whole paragraph doesn't make much sense. You can see frank HW-related error messages in the kernel logs so it's puzzling that you think it is a version mismatch issue or some kind of vague corrupted data (which data?) issue instead. You have encountered flaky hardware before, right?

Alright, if I haven't convinced you and if you still think this is due to a version mismatch, the test is extremely simple. Find me a kernel/bootloader/module combination which will produce this error message:

<4>[ 66.035915] bcmsdh_sdmmc: probe of mmc0:0001:1 failed with error -110
<4>[ 66.048711] bcmsdh_sdmmc: probe of mmc0:0001:2 failed with error -110
<4>[ 66.066313] bcmsdh_sdmmc: probe of mmc0:0001:3 failed with error -110
...
<4>[ 98.368522] dhd_module_init: sdio_register_driver timeout

It shouldn't take more than a day or two to check the various combinations going back to some fairly old kernels.

Well... since you asked for it: I think you are danger in this instance, TEK... ;)
[G Tablet Q&A, Help & Troubleshooting] TEK112:
(*dusts self off*)

That wasn't nearly as bad as I thought it would be. ;)

Sorry, if it came off confusing. I am not suggesting a version mismatch or taking working parts from working kernels and interchanging them. What I meant to ask was is it possible that a corrupted update.zip (one that did not pass md5 validation) could be causing flaking out of the wifi module? I know that I had a bad kernel (did not pass md5) which I flashed and it only affected wifi after the tablet went to sleep. I did not run a log as I thought a quick flash would be easier and rule out obvious issues, so I cannot compare it to what this user is experiencing.

I know that it is hardware related, but I am not sure hardware is to blame for the failure. I feel it is a software issue causing hardware failure. I would think the first place to look is the ROM and I don't know why a full teardown and rebuild seems non-helpful.

I appreciate your help trying to explain this to me. I want to learn more and am thankful you didn't tear into me.
[G Tablet Q&A, Help & Troubleshooting] jmbach:
Well here are the results of my testing and to no suprise I conclude that my hardware has become flakey.

Essentially I went back to CM7, then to stock 3588. Had same issue in all ROMs, just not as easy to replicate. (Took more power offs and ons to reproduce the issue). Not sure why. :confused: Maybe slight driver changes or just random chance. Either way I have sent the tablet back for hopeful repair of problem. Perhaps they will do more than flash the latest ROM on it.

Thanks for your help/insight rajeevvp

Jim
[G Tablet Q&A, Help & Troubleshooting] TEK112:
They seem to like to replace the motherboard. If you ask them specifically to (just for completeness sake) they will for a $36 charge. So, even if they deny warranty or decide not to replace the motherboard, the worst it will cost you is under $40. Just be patient it may take about two weeks after receiving it for them to turn it around. Also, don't let them buddy up with you. They try to play like your friend and get you to admit you rooted the device so they can try and void your warranty. I hope all goes well for you.
[G Tablet Q&A, Help & Troubleshooting] rajeevvp:
Well, looks like jmbach has saved me a lot of typing, so I'll make this short.

Actually, you were--at least initially. Then you changed to this corrupted data scenario:

Going by what you said above, I doubt that what you described is what happened: It would be a mini-miracle if could load a working kernel from a corrupted zip file.

Now you know why.
[G Tablet Q&A, Help & Troubleshooting] TEK112:
Sorry if that is how it came across, but I did specifically write this in my initial post, so I am not sure how I suggested a version mismatch:

I really do appreciate your assistance in helping me understand, but I don't know why a corrupted kernel update could not run if a corrupted ROM update.zip can, corrupted meaning not passing md5 validation. I don't want you to think I am talking about an unreadable update.zip. I have seen ROMs that FC all over the place with freezing, random reboots and SODs go away after reflashing a newly downloaded version of the same ROM. I have also seen wifi errors and USB mounting issues cleared up by manually pushing modules that should have pushed themselves correctly during the update.zip of the same kernel.

If you care to take it offline so we don't clutter the thread, I understand. Or, if you'd rather give up all hope for me, I understand too. Thanks for the clarification so far.