yashsingh1/xdaforums huggingface dataset:
[LG Optimus Black] mart1234:
Just got my phone and im having problems setting up my mail..

Orange tell me the phone dose not support push email..

LG tells me that it dose..

can some one please shed some light on this matter? and help me set it up, if it does actually have push.

Thank you
[LG Optimus Black] ogremount:
I have the Yahoo app a and it does push email. I receive just about instantly my emails.

Just look about specific app for your email.
[LG Optimus Black] wiqi546:
Yeah it does support push emails (i have checked Gmail, Yahoo and Hotmail). Which service do you want to configure?

PS: even with the default stock email client.
[LG Optimus Black] mart1234:
I just cannot seem to get it to work at all...i have a Hotmail account and Gmail, so im not fussed. i just would like push email on my phone.

thank you for the help.
[LG Optimus Black] wiqi546:
Here you go.

Open the Stock LG Email Client.

If you haven't configured any email accounts yet, it will prompt you to add one. Otherwise click menu and goto accounts to add one.

Click OK on the prompt.

For Gmail, Yahoo Mail, Hotmail etc select Other.

Type your email address, password and make sure to select "Enable Push" radio box!

Click Next.

Click Next on the pop-up message.

Type desired account name and your name. Click Done.

And you have successfully configured your Push enabled email service on your LG OB. :)
[LG Optimus Black] mart1234:
everything comes up as you have shown apart from the "Enable Push" radio box! I can however go into settings and check 'auto retrieve'(except push email). I Have checked the box and still no push?
[LG Optimus Black] ogremount:
Sounds like something is wrong with your phone settings. Update it , make backup.

Reset to factory default and try again.

I am on Orange btw so don't think is some Orange restriction.
[LG Optimus Black] mart1234:
just done an update on it but it says it has the latest version. just done a reset on it and still no luck. starting to drive me mad.
[LG Optimus Black] mart1234:
been on the phone and into the orange shop, now they are saying Orange dose not support push email on the LGOB-p970 only with blackberry and iphone!!!
[Android Q&A, Help & Troubleshooting] revaaron:
I was just about to make a thread about this. I'm willing to make a app that does this, but I don't know the file structure of where google does things.

If you download the Google Voice App, you can see that some where they store all the SMS data about a txt, they just don't expose that to the user through the web interface.

My idea is to take the Google Voice SMS DB, convert it to the XML format supported by SMS Backup & restore and then merge the 2.

Does anyone know where the db of SMS is stored in the Google Voice app?

If this app existed or I could make it, I would be able to send through the web-interface and my ipad, etc. Now I don't cause when people reply and I'm at my phone, I have no clue what they are talking about.
[Galaxy S I9000 Q&A, Help & Troubleshooting] malcho:
Hi,

As subject said my audio is not synced with video when i record video with hacked camera.

I use hybrid 2.0 rom and most of the roms use hacked camera.

How to solve this?

Hybrid 2.0 lite on semaphore 1.7.0
[Galaxy Ace S5830 General] Alpha que:
Hey guys,

Im new here, and this is my first post :)

I have a Samsun Galaxy ace, There are 2 main custom rom's Ive

Heard of, Villian rom and First UA rom, and recently the cyanogen one i think..

Anways, which do you people think is the best ROM to install?

Performance wise and Playing games like NOVA 2 (I found a HVGA Version of it)

I cant post the link, so I found it on youtube though..
[Xoom General] Michael@:
I tried to root my 3G XOOM (MZ606) last night and eventually I did brick it but I am not sure. I did definitely dl the wrong img file (as I didnt read here before :) Anyway everything of the procedure went fine till I had to type the commands (like adb remount) after reboot. Actually the XOOM does not seem to connect to my wireless hotspot anymore (is that due to a missing key?) and it remains in the boot up screen (just the MOTO logo)

Is there any solution to get the XOOM reconnected may be? Can anyone push me into the right direction? Do I really need those certain cable (someon mentione in any thread here)?

--

thanx a lot for your help

Michael
[Xoom General] kenfly:
if you have ANY type of screen coming up, its not bricked. Depending on your situation, you just need someone whos good with ADB/Fastboot to get things back to where they need to be.

---------- Post added at 01:19 PM ---------- Previous post was at 01:17 PM ----------

go into recovery and wipe Everything/ factory reset, wipe cache, and go into advanced and wipe dalvik cache. then flash any rom available here in the DEV section.
[Xoom General] Michael@:
hmmm I found out how to do that

>go into recovery and wipe Everything/ factory reset, wipe cache

but what means

>and go into advanced

? There is no advanced option at the recovery menu. So may be thats an otion once I choose 'reboot system now'?

And just for my understanding, that

>then flash any rom available here in the DEV section

is not necessary just may be in my interest, right?

--

Thanx anyway, great help

Michael
[Xoom General] tincbtrar:
It might help us if you tell us what model your Xoom is...3g/wifi - us/uk - all the specifics.

Hopefully you knew this before you installed the wrong image.

Then we can help you get back to where you need to be.

And 'flashing any ROM here in the development section' is what got you here in the first place so I wouldnt do that.
[Xoom General] Michael@:
Hola,

well I will definitely be more careful now. Actually I did read about those issue with the Wifi only device before but... So what specifications I could deliver?

So far I saw on the screen also printed on its backside its an MZ606 purchased from MOTOROLA china directly. I possibly wouldnt have tried to lunlock and root if those gadget could at least connect to the google market... sorry for complaining but the cn.MOTOROLA market does have very few and mainly chinese apps only. Further on before the procedure I stuck in now the OS has been Android 3.1

Hope those background information allows some more conclusions but

right now I am still trying to figure what kenfly ment by mentioning

>go into advanced and wipe dalvik cache

If I understand for example those guys http://xdaforums.com/showthread.php?t=560207 right (hopefully it is allowed to put that link here) it seems to be a procedure before flashing a new ROM. What I am asking myself is do I right now not have a working one anymore? May be I misunderstood in the past but so far I thought the sequence is unlock> root> custom rom... and so far I think I am not successfully rooted yet so I wouldnt be supposed to flash a new ROM. So I think what I need to do now is to get my device successfully rooted before wiping the 'dalvik cache', am I wrong?

--

Cheers Michael
[Xoom General] okantomi:
Did you flash the ClockworkMod recovery before rooting [after unlocking], and if so, which version?

If you don't have that installed, you wouldn't see the advanced option in the recovery menu.

You have a wifi model and I think the wifi hardware is all the same so you could flash the US Xoom system image and that should solve your access and updates problem, But since it's a HongKong Xoom, there may be some differences, so try it out but use caution.
[Xoom General] Michael@:
hey guys looks as I dont get the message. I am still stuck at the recovery screen. I did

>go into recovery and wipe Everything/ factory reset, wipe cache

but whats next? Rebooting does not change anything, still the same logo screen only. So am I supposed to apply a proper image by 'apply update...'?

--

Cheers
[Xoom General] tincbtrar:
You say you have a 3G Xoom - but the MZ606 is WiFi only.

Do you remember what image you applied to mess things up in the first place?
[Xoom General] Michael@:
sure, the name is rootboot.img

It should be the one from 3*w.addictivetips.com, '/?attachment_id=45936'. I separated the link as I dont wanna mislead anyone here but I hope its still possible to follow up ;)

--

Thanx for your help

-sorry for the 3G thing, no idea why I did type that. It definitely is a WiFi only

-and i idd not do any clockworld thing before or what ever. It has been just an ordinary MZ606 automatically updated to the 3.1 android version, but unlocked. For unlocking I used the android.sdk and typed the command to do so, thats everything I did before getting stucked with those rooting procedure
[Xoom General] Michael@:
Hey guys dont leave me alone. I may tend to do another stupid thing :) ... well I am capable to find former posts about how to recover so on but as U asked some more details it seems to be depending on which exact device I have and what exactly I did before. So I hope U could still guide me to the harbor
[Xoom General] princenoob:
hey.ur on 3.1 right?

I assume you have knowoedge on fasboot.

Find the appropriate boot.img for ur device then flash it via fasboot.

Maybe u flash the wrong boot.img

---------- Post added at 07:15 AM ---------- Previous post was at 07:11 AM ----------

Or go back to stock. http://developer.motorola.com/products/software/
[Xoom General] Michael@:
well the problem (after data/factory reset and wiping cache) is the application (android.sdk) still cant find the device... I assume thats due to device still stuck at the M logo and I cant tpe in the WiFi password for example.

So how could I flash another ROM to the device without having the OS working on it properly?
[Xoom General] tincbtrar:
Do you have the proper drivers installed? Make sure you get them from Motorola.

Your device should be seen if ADB and Fastboot are set up correctly.

Once you can see the device I would use fastboot to reinstall the proper image (again from Motorola - they will have the correct Image for your Chinese Xoom)
[Xoom General] Michael@:
yes I do have the proper drivers from M and they worked perfectly before once I flashed the wrong image. May be my problem is too simple for U guys or as I am not capable to deliver appropriate information to get some help.

For my understanding it is obvious why my pc can't get the device as the device obciously cant get an wireless IP without knowing the WPA2 key and I cant type in the wireless key as the OS (on that device) does not fully start up. Which wireless device works without any basic configuration? So does mine I guess even though I am not expert... but even I deactivated any security measures on my router it still the device didn't connect (check only at the routers active device list)

Once again my question: How could I flash another ROM to the device without having the OS working on it properly? I think the OS is (part of) those wrong IMG i did flash before, so I assume I will never get it working

--

Regards
[Xoom General] princenoob:
Can u go to fastboot?

When the xoom bootup press vol down immediately.it says starting fastboot etc.

If your pc can detect it then flash the correct images to ur xoom.

Btw lets talk on yahoo msgr. Pm me ur email.im free this time.
[Xoom General] princenoob:
No no.why would you connect it on wireless router in the first place.connect it on ur pc! So if the pc detected it.then flash thru adb.
[Xoom General] Michael@:
oh thanx for that hint. I thought it works only connected via wifi. Well now the SDK states a number instead of the device name or MZ606. I hope its not my HTC Desire but I did deactivate the wireless on there.

So if it really is the MZ606 (I can take the battery off the HTC just to make sure ;) should I go back to the original image first, then install clockworld, then root?

--

thanx in advance
[Xoom General] princenoob:
Sdk only detects devices connected to pc.so your phone has nothing to do with it.did u already download the firmware for ur xoom?the link i post awhile ago download the rom there.do you know how to flash it thru fastboot?.if yes then i think u can revive ur xoom. :)

---------- Post added at 10:30 AM ---------- Previous post was at 10:25 AM ----------

if you have ur original copy of ur boot.img then flash it.if not better flash from stock.the use this tutorial to root. http://xdaforums.com/showthread.php?t=1242241

Please hit thanks if i help you in anyway. :)
[Xoom General] okantomi:
Michael@, you seem to be lacking some very basic understanding of how all of this works on the Xoom. No wonder you felt frustrated.never in a million years would I guess you would try to flash an update or recover your Xoom via a wireless connection.

That said, hopefully you are now on the right track. I wish you good luck.
[Xoom General] Michael@:
as I am trying to revcover my XOOM I am going to follow on this

http://xdaforums.com/wiki/index.php?title=How_to_flash_Recovery_Image

procedure flashing this

http://developer.motorola.com/produ...?cta=3fde4fc191b29738bcd4ed9600f9395a6b0b4c3c

file. Hope I am on the right track.

--

Cheers
[Xoom General] Michael@:
thanx okantomi for pointing out

>you seem to be lacking some very basic understanding

;) it might not have been obvious before :rolleyes: whom does that

>never in a million years would I guess you would try to flash an update or recover your Xoom via a wireless connection

tell more about :p
[Xoom General] okantomi:
NO! That is not a functional Xoom recovery!

Please use the instructions in the Xoom Heaven thread

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

You are right about using the stock images from motodev.
[Xoom General] Michael@:
this thread really makes me feel I am a nerd.

I assume U mean the 'Recovering Your Xoom' part of the ROOT user section even though I am not rooted yet. I already did "select the wipe data/factory reset option to completely wipe out the entire Xoom so ..." but where then I get to know " ...that you can start fresh"?

Update: If no other comment I would follow on the instruction

http://developer.motorola.com/products/software/

Update

Instructions to Flash & Re-Lock Your Motorola XOOM:

fastboot flash boot boot.img

fastboot flash system system.img

fastboot flash recovery recovery.img

fastboot flash userdata userdata.img

fastboot erase cache

fastboot oem lock

Note: If no userdata.img file is present in your download, please issue the command:

fastboot erase userdata

/updated

which might be advised at the linked guide to heaven under 'Other Useful Root Information:'

--

Michael
[Xoom General] rockhumper:
hey look another brick thread by another person who doesn't understand what a brick is...don't use the terminology if you don't know what it means. Getting tired of reading"brick"threads that aren't
[Xoom General] Michael@:
@rockhumper

Do U in general "understand" what a question is? If so are U sure U also understand what the meaning of my subject is? Thanx for your welcome and read the headline of threads to decide if U r interested or not.
[Xoom General] tincbtrar:
Did you download appropriate files and apply the image yet?

Curious to know how it went.

It should be a quick process once you get the proper image.
[Xoom General] Michael@:
not run the procedure yet, as I am still waiting for someone to tell me I am wrong again ;)
[Xoom General] GhostOfTheNet:
i'm already at home, so if you want...
[Xoom General] okantomi:
You're not a nerd...just sort of fearless, lol. Anyway, those instructions should work but just don't do the last step--don't relock. No need to. Also, you will have learned a lot from this experience and will probably be able to root successfully and even help others in the future. Don't worry, we were all there once. But you could do yourself a big favor by reading the threads in that link I gave you as well as other threads in General and Q&A. There are lots of problems and solutions in those threads.
[Xoom General] Michael@:
SOLVED the issue *** in the meantime. I found a post which related that issue to USBv1 vice versa USBv2. So it seems to be recommeded to ensure the device is connected to a USBv2 port.

***

i think thats not my kind of stuff. Following on the given instructions I get

C:\...Android\sdk\tools\boot.img

sending 'boot' (8192 KB)...

OKAY [ 0.734s]

writing 'boot'...

OKAY [ 1.640s]

finished. total time: 2.375s

C:\...Android\sdk\tools\system.img

sending 'boot' (262144 KB)...

FAILED (remote: (00120003))

finished. total time: 165.510s

tried several times already and yeah I am searching for other posts with that kinda feedback (feedback on the device is 'Failed to process command error (0x120003)')

***

--

Michael

@okantomi

thanx for the advice of reading... but I surely do. The point is there are millions of posts and they often dont fit exactly your own situation/intention or U dont know they fit what U want or its starts with one topic and shifts into a different direction without solving so especially in the beginning its difficult to get some orientation just by reading. So for me it works better to do, to fail and then get catched by the people whos postings are most valuable ;)
[Xoom General] Michael@:
I do not get it done...

Well I did follow on those given procedure and all finally went fine but once I tried to reboot the device remained at the dualcore screen. Now as I try to go through those procedure again flashing system.img fails. The device claims

Flashed image is lager than partition size

Failed to process command error(0x2)

Even the charging light does not glimse anymore so it looks as I will run out of energy very soon as the screen keeps on whole time and starting into recovery mode (to may be wipe out things once again) works till the green android logo, then it takes a while and the device automatically restarts but no menu like before. I better dont say what I am thinking about all this!

--

Michael
[Xoom General] okantomi:
I'm not trying to be difficult, actually really trying to help, as are the other posters, but I think we are all really confused as to your current status, what you are trying to do and what you are using/how you are trying to do it.

Any clear, easy to follow details would be helpful as we try to guide you.

My comment on reading was not aimed at just getting you to read everything, but trying to understand the basics of how to work with the Xoom. I sent you to the Xoom Heaven thread, because that thread has gathered a lorge amount of pertinent inormation. When you understand more how it all works and what you need to get started, it will be simpler for you to root and to get out of a jam.
[Xoom General] Michael@:
I was fine with your comment Okantomi really and I think all posts from all posters here (accept one) tried to help, I appreciate that.

Well what I am trying to do is what all my posts in this thread are about. I am trying to revive (hope this word is not preoccupied by any XOOM procedure) my XOOM as I stated in #24 of the same thread. I did definitely follow on it but it didnt work out so thats frustrating even though its not anyone else fault.

As it did not work out I tried to start the procedure from recovery mode again but once I am in the recovery mode I dont get the menu anymore but may be I have to push any button at a certain time... I dont know anymore and I have to research again.

Alternatively I was thinking if I should use the fastboot erase system command before flashing the system.img as the command window states something like partition seize not big enough...

--

Cheers Michael
[Xoom General] okantomi:
Where is your 3G MZ606 from (is it US, Euro, Asian, etc..)?

I ask becuse you are getting errors that I haven't seen, personally, like partition size too small...
[Xoom General] Michael@:
thanx Okantomi, I finally got it working again. Now I am at the same point I have been nearly a week ago... i have to find an image which works on my chinese WiFi only XOOM and allows me to connect to the market. I think I should try to follow up on yr former link Trying to get into heaven

And here is my next question: what is ClockworkMod good for? No need to reply if U think I can find the answer on my own but so far I only find posts stating how to install or that it makes a difference in recovering or but right now I do not know why I might want it.
[Xoom General] okantomi:
You do want ClockworkMod recovery because it does at least two very valuable things...it allows you to make a backup of your complete system image (saved to your external micro sdcard) so you can experiment, flash new roms/kernels/themes and if you are dissatisfied or run into problems, like you can't boot into the OS, you can restore your "nandroid" from the CWM recovery menu and you'll be up and running again. That is already priceless!

Also, it gives you a much easier way to flash roms, kernels, themes and other files as zip files...you usually don't have to pull up a terminal emulator or adb on your pc. There are other advantages, too. I like the solarnz version 3.2.0.0 R4c recovery, but there's also the Rogue recovery; both are custom made for the Xoom. Just don't boot into recovery using Rom Manager or really use it for anything (my advice) because it doesn't play nice with the Xoom IMHO.
[Xoom General] Michael@:
thanx again but still so many questions left...

First I think someone recommended me to flash the US ROM on my XOOM. For me a ROM is something different than those images I may flash once rooting, am I wrong again? I am good at that :p

Second following on the Universal XOOM Root post it recomments to flash a file named recovery-Tiamat-R4c-100611-1150-cwm.img ... which sounds as it already contains something for or like the clockworkmode. If so why it still is a different topic at the Universal XOOM Root post?

--

Good night for today
[Xoom General] okantomi:
OK. The file named recovery-Tiamat-R4c-100611-1150-cwm.img is the ClockworkMod recovery verion I recommend for the Xoom, especially with Tiamat Rom and/or kernel.

As part of the rooting process, after unlocking, you should flash this image file through fastboot (while connected to the pc via your Motorola usb cable). Follow the instructions in my guide so that you catch the Xoom after you flash the recovery image but before it boots into Honeycomb, otherwise you will overwrite the file you just flashed. It's a little tricky but if you read and follow the directions it's easy.

Then you just complete the process by downloading the Universal Xoom Root zip file onto your external micro sdcard, make sure the card is in your Xoom, boot into android recovery (follow the guide) then choose CWM recovery, then follow instructions for Universal Xoom Root. Following that (Xoom will reboot) you can then download the 2.2.1 Moray Rom zip file to the micro sdcard and flash it the same way.

The Rom is probably identical to "those images (you) may flash once rooting" as you say. You certainly need to be unlocked/rooted to modify your system.
[Xoom General] Michael@:
what does that mean to me? How can I know what ROM or kernel I have and if it is not the right one... ok I think I have to research.

with yr guide U mean this

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

thread, right?

just for my understanding, first I flash the ... TIAMAT... file for what purpose as later I am supposed to

from the Universal Xoom Root zip file and what is the recovery file then for?

...

And finally what is

that good for?

Okantomi I do not expect U (or anyone else to) answer all those questions but it somehow still refers to "reading" :D

For me it is nearly impossible to put all those spreaded information together in order to achieve what I want (and I am pretty familiar with many computer things), especially as I may not know exactly what I want to achieve (hope u can see the smile on my face).

Weekend is closing in

--

Thanx Michael
[Xoom General] albundy2010:
Read. Leave your device alone until you know what you're doing.

This thread is so bad I can't believe it is actually real and your not trolling.
[Xoom General] Michael@:
@albundy2010 U r right, a developer forum might be not suitable for those kinda question (and user :). Unluckily I didnt find a more suitable place, providing sustainable information and help.

I am sorry for that but I also think I dont push anyone to read my posts.