yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] Puenos:
As far as I've seen this was the most promising thread about porting meego here..

So I would suggest to just contact the ones who dived deeper into the matter and even made some progress.

Thread: http://xdaforums.com/showthread.php?t=764255
[Nexus S Android Development] stroughtonsmith:
Unfortunately the graphics driver they released is specific to Android, and Android's version of libc. I don't believe there's a way to get that running on GNU/Linux or MeeGo :-(
[Nexus S Android Development] tominater12:
Being the noob I am what is meego?
[Nexus S Android Development] stroughtonsmith:
Nokia (and Intel)'s future smartphone/tablet platform. A real Linux distribution designed for mobile devices, entirely new touch based UI, GPU acceleration, multitouch, etc.
[Nexus S Android Development] tomislavp4:
Whoever gets this done gets a beer from me :) I am really excited about meego but I wont be able to buy the n9 because im on contract untill march next year. If you can get this to run on the nexus s than it should run on the sgs too, that way I can use meego wothout buying a new phone;) Keep it up
[Nexus S Android Development] stroughtonsmith:
Am hoping to have it up and running on the HD2 first, and then hopefully some of the work we do for that will port over to the Nexus S. Can't wait for the N9…
[Droid Eris Q&A, Help & Troubleshooting] xzillerationer:
I recently flashed KaosGingerbread. I did a nandroid backup first. I tried to do a nandroid restore, and gave me this "run 'nandroid-mobile.sh' via adb". I've tried letting it charge, clearing up SD space, and looked on how to run the adb stuff. None of it has worked, and I can't figure out how to run 'nandroid-mobile.sh' via adb. I'm using RA eris v1.6.2. Help
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
The first thing you should do is to inspect the recovery log immediately after the (restore) error occurs in Amon_RA. There is a menu item available in Amon_RA (under "Other", iirc) which will copy the recovery log file at /cache/recovery/log to the root folder of your SD card. Then you can look at it using adb:

adb shell ls /sdcard/ (look for the file, I think it will be named "recovery.log" or similar)
adb pull /sdcard/whateverthefilenameis.log ./recovery.log

or just

adb pull /cache/recovery/log ./recovery.log

or just

adb shell cat /cache/recovery/log

Alternatively, if you are not familiar with ADB, you can use the Amon_RA "Toggle MS-USB" mode to mount the /sdcard to your PC (after you use the Amon_RA menu to copy the log file to your SD card root), and then copy the log file to your PC for viewing.

There are two reasons for looking at the log file.

1) The first is that Amon_RA himself told you to do so in his announcement post.

2) The second reason is that the Amon_RA process (/sbin/recovery) which spews that

Error : run 'nandroid-mobile.sh restore' via adb!

error message actually just got through running exactly that script... and it failed!

So, if you re-run it, it will certainly fail again, assuming that you use the same command line that Amon_RA did (which is an extremely good idea, BTW). And when it fails when you run it manually, it will produce error messages that give you an idea of what the failure problem was.

So, as you see, you might as well just look at the recovery log in the first place, rather than re-running "nandroid-mobile.sh" just to see it fail once again, and produce the same error messages that are already in the recovery log file.

Probably you ought to post up (here) a copy of your recovery log - some types of errors will not be correctable by running "nandroid-mobile.sh" manually.

If you insist on experimenting, note that "nandroid-mobile.sh" has some documentation built in to it - start a shell on your phone (in Amon_RA recovery mode, natch), and type the command

nandroid-mobile.sh --help

If you do that, you will find that there are lots of command line options. Inspecting Amon_RA's "/sbin/recovery" program using the well known Unix/Linux/Cygwin "strings" tool, you will find that Amon_RA calls restore commands which look like this:

/sbin/nandroid-mobile.sh -r -e --norecovery --nocache --nomisc --nosplash1 --nosplash2 --defaultinput -s SUBNAME

See the output of "nandroid-mobile.sh --help" for what SUBNAME is (presumable the folder name that has the desired nandroid backup set in it.

good luck

bftb0
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
Well... as predicted, the log contains the source of your error:

...
Restore path: /sdcard/nandroid/HT9aaaannnnn/BDS-20110109-1844

error: /sdcard/nandroid/HT9aaaannnn/BDS-20110109-1844/nandroid.md5 not found, cannot verify backup data
...

Now, it is a mystery to me why the "nandroid.md5" file would not be found. It is always, always, always, created when a nandroid backup has been performed. If you didn't screw around with contents of your SD card, the only thing I can presume is that you filled up your SD card during the nandroid restore. That is to say - you had an error that occurred during the nandroid backup and you failed to take notice of it.

The "nandroid.md5" file contains the MD5 checksums of each of the backup images in the backup folder, so clearly it must be the last thing created... and so, if you filled up your SD card... it would fail to be created.

This is bad news on several fronts; let me explain why. First, though, here is an example of a file listing of one of my recent nandroid backups:

$ adb shell ls -l /sdcard/nandroid/HT*/BDS-CELBFroyo_3.9-20110109-1756/
----rwxr-x 1 system sdcard_r 2621440 Jan 9 17:56 boot.img
----rwxr-x 1 system sdcard_r 125323968 Jan 9 17:57 data.img
----rwxr-x 1 system sdcard_r 131 Jan 9 17:57 nandroid.md5
----rwxr-x 1 system sdcard_r 105811200 Jan 9 17:56 system.img

You will note a couple things about the above: first (from the file dates) the "data.img" and the "nandroid.md5" files are the last two files created during the backup on an Eris, and second - that "data.img" is a BIG file (125 MB in the above example).

That means that if you filled up the SD card writing a big file, the big file in question was probably "data.img". That's the file that contains all your user data and application settings - including your GF-related data. It is stored in a "yaffs2" archive format, and when it is unpacked during a nandroid restore operation, the /sbin/unyaffs command is used.

If you were to clean up your SD card, you could manually recreate a "nandroid.md5" file by hand, and then attempt a nandroid recovery.

Here is what a "nandroid.md5" file looks like:

$ adb shell cat /sdcard/nandroid/HT*/BDS-CELBFroyo_3.9-20110109-1756/nandroid.md5
b94da50ce57174e4a1583da1bf07071c boot.img
db9f1fc53f86a8186da448d0347d09d8 data.img
dc989fe4d74bdee8e9be0ff8cfc2075b system.img

Pretty simple, really. Just the MD5 checksum of each of the three files "boot.img", "data.img", and "system.img". There is a "md5sum" command available under Amon_RA, so it would be trivial for you to hack together a "nandroid.md5" file to place in your backup folder BDS-20110109-1844.

Now, you would be performing an "unyaffs" operation on a presumably corrupted "data.img" file - you might be able to get your data out of this operation, or maybe not. The resulting partially-restored system might go into a boot loop, as there are important files stored in /data/system (for instance).

good luck.

bftb0
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
To anybody else reading this thread, it is worthwhile to re-iterate two things about using Amon_RA's recovery:

[SIZE=+2]1) Amon_RA's original instructions in his announcement thread, to wit:[/SIZE]

"[SIZE=+1]Always check recovery.log before posting your issues![/SIZE]"

[SIZE=+2]2) Error conditions in Amon_RA [/SIZE]

[SIZE=+1]If an error occurs, you will see an "(E)" on your screen[/SIZE]

No blinking lights, no different text colors or bold fonts - you need to inspect the output of every command action that the Amon_RA recovery performs, and watch for the appearance of ANY line that contains an "(E)". Sometimes the associated error message is very brief - pay attention!

[SIZE=+1](E) means ERROR![/SIZE]

Don't ignore any (E) you see - (E) means ERROR!
[Streak 5 General] waynebampton:
This contains the procedure to restore the software back to Android 1.6 factory condition.

The following tutorial will teach you how to restore your Dell Streak from Android 2.1 to Android 1.6

1. Download the stock recovery ROM and stock official Dell ROM.

2. Rename the stock official Dell ROM to Update.pkg and copy it to your Dell Streak SD card.

3. Turn on your Dell Streak while holding camera button to boot Streak into fast boot mode.

4. Tap on Fast boot Mode button, wait 10 seconds then connect to your PC.

IF YOUR STREAK DOES NOT ENTER FASTBOOT MODE GO TO MY COMPUTER, AND DEVICES ON ANDROID PHONE RIGHT CLICK AND PRESS UPDATE DRIVERS AFTER UPDATE FOLLOW 3 AND 4 AGAIN.

5. Open a command prompt, and navigate to the folder where your fast boot-windows.exe is stored.

6. Enter fastboot-windows.exe -i 0x413c flash recovery c:\recovery.stock.img. Make sure the .img file is in c:\ directory. The program will now update the recovery image to your Dell Streak.

7. Once the phone displays Recovery Done, remove the battery and insert it again.

8. Hold down vol up and vol down button while turning on your Streak to boot into Recovery mode, and choose option 2.

9. Wait till it installs and it will boot into Android. You have finished restoring Dell Streak to factory condition.
[HD2 General] teedotem:
Hi guys, my T-MOUS HD2 just failed on me today.

I installed a NAND android update this morning and it was all good for a while, I left it on the couch for 20 min and after I came back, the display didn't work. Everything else is functioning normally: LCD's backlight, buttons, touchscreen. The phone was able to boot into android and function as normal but it's just that the LCD will not display anything (just black).

I have installed the stock rom by going into HSPL blind, but that didn't change anything, still no LCD.

My question is: has anyone else encountered this before? Could it be an LCD problem or a display chip problem? Should i invest and buy a replacement LCD screen?

thanks guys.
[HD2 General] Kailkti:
Hmm iunno if the problem of auto brightness persists in NAND builds too, but anyways, try putting your hd2 screen near a very bright light and try to turn the screen on, if that works yay, its not bricked, and i suggest you turn off auto brightness in settings after. If that doesn't work then damn....
[Touch Diamond, MDA Compact IV General] shana1974:
(Sorry for my English, I'm french speaker)

Hi all,

Sorry, I don't know if I post in right place.

I have a problem with my HTC Diamond ... I've tried to install a prog for unlock sim 'cause when I put a sim card with another phone provider I have a message on the phone that said me that the sim is locked.

So, I've install "Diamond Unlocker", a message tell me that the rom isn't compatible with my phone.

My phone switch off automatically.

Now, when I try to turn off, nothing appear, the phone doesn't turn on :(

I've put the gsm in charge, change the battery, but doesn't work

Please, someone can help me ?

Thanks a lot

Farah
[Touch Diamond, MDA Compact IV General] Hakim Rahman:
try to hard reset your device after that reFlash with official rom :):)

you can find Rom official in http://www.shipped-roms.com/index.php?category=windows mobile&model=Diamond :)
[Touch Diamond, MDA Compact IV General] shana1974:
Thanks a lot Hakim for your reply.

But how I can do that ?

In my previous post I said that I can't turn on my Diamond.

So, how I can flash if I can't connect it to my computer ?
[Touch Diamond, MDA Compact IV General] mheatas:
i have same problem
[Touch Diamond, MDA Compact IV General] Hakim Rahman:
you've tried to hardreset your device..??:confused:
[Touch Diamond, MDA Compact IV General] mheatas:
yeah, htc doesn't react to hard reset,soft and bootloader
[Touch Diamond, MDA Compact IV General] luscinia:
almost same story

I have a very similar problem .

The only difference is that my phone is a mda vario IV (t-mobile)

and my download was a different one .

If I turn it on it shows the t-mobile screen and turns off immediately .

Hard reset doens't work since it doesn't react to the soft reset button .

It would be really really awesome if anyone had an idea to solve this/these problem/s
[Touch Diamond, MDA Compact IV General] cod69account:
You might have bricked your phone......Try getting into bootloader mode, if ya can do that much you might be able to load one of the custom ROMS or at least the right one;)
[Touch Diamond, MDA Compact IV General] grandma90:
Yes , bricking seems to be the only explanation for this behaviour.

Why on earth did you try to unlock your phone yourself?!

If i have a problem , i go to a service center nearby and pay a fee of almost 10E to unlock my phone.They know what to do , even gine me waranty.

You are not the only brave person i see trying to unlock a headset by himself.A friend holds the record for bricking headsets. In 2 months he bricked not less then 12 headsets because he was to stubborn to take them to a service center.

Some things are best not to be dealt with. I personally am afraid to flash a W6.5 ROM on my headset , because i might end up bricking it.
[Touch Diamond, MDA Compact IV General] Huckleberry88:
I remember there used to be many threads related/similar to your problem.

Have you guys tried to search for that issue?

Just an example:

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

Good luck!
[Captivate Q&A, Help & Troubleshooting] PizzaAmerican23:
So I was running cognition 2.4.1 for a long time, and my battery life was awesome. It would barely go down at all if I didn't use it, and would make it through the day with about half to spare. On normal days I unplug at 630am and at 5pm it would be at ~70% (if i didn't really use it at all). Even if I did use it it would still last a long time.

I finally decided to flash a new/different rom and thats where my problems started. I flashed Assonance 5.0 and the battery life got worse (at 5pm i was at about 45%) so i just assumed it was the rom and that cognition was better on battery life. So my next flash was back to cognition (a newer version, b7 i think), which improved battery life, but it was barely noticeable, and was no where near what it used to be. Next I tried pheonix v1.5 and that was probably the worst yet, as my phone almost died by 5 oclock.

Finally I decided I would go back to cog 2.4.1 even though it was outdated. I figured this would solve all my problems. I was wrong as my battery life is absolutely terrible right now. At one point yesterday it drained 12 percent in 30 mins.

Something else also happened yesterday. As it was almost going to die i plugged it into my car charger for about 10 mins. It was at 15% when i put it on and 19 when i took it off. After that my battery life was almost normal again as it only drained 4 percent over the next 3 hours. Later on that night I charged it back up to 50 percent and about 10 mins after taking it off the charger it said it was at 5 percent. It stayed at 5 percent for the rest of the night and did not die ( about 4 hours).

Theres definitely a problem and I know it was to do with the battery reading. I think i just need to reset the battery stats.

FYI every time i flash a new rom i always flash back to stock jf6, make sure its 100% battery, wipe data and cache, etc etc etc. so im not sure why this is happening.

I also tried wiping stats through clockworkmod recovery, but i dont think it really does anything.
[Captivate Q&A, Help & Troubleshooting] Auridran:
The proper way to wipe battery stats/recalibrate your battery:

Charge up to 100% with the phone on. Disconnect the charger and turn the phone off. Connect the charger; you're now in charge mode. Charge up to 100%, disconnect the charger and turn on the phone. As soon as the phone is on, turn it off. Connect the charger to put it into charge mode again, and charge up to 100% again. Some people also say that before starting this process it's a good idea to kill the battery completely.

That is how you bump charge, or recalibrate the battery. After bump charging is the best time to wipe battery stats.
[Captivate Q&A, Help & Troubleshooting] Miami_Son:
I can't find batterystats.bin on the phone to delete it. Is the only way via terminal mode or Clockwork?
[HD2 General] Lord60:
I flashed to the NAND rom, and of course, needed the correct APN settings. I've seen a number of requests for assistance, so here's what I got direct from the TMOUS tech support.

1. You need TWO APN's in there. One will be called T-Mobile Data and the other will be T-Mobile MMS

2. go to settings, wireless networks, Mobile networks, Access Point Names

3. click on the menu button and reset to default so that you can start from scratch.

4. once cleared, click on menu and then new APN

5. Name the new APN T-Mobile Data

6. Once created, click on it, and go into it. Fill in as follows... if it says <not set> below, this means skip it and do not touch it or change it in anyway

Name: T-Mobile Data

APN: epc.tmobile.com

Proxy: <not set>

Port: <not set>

Username: <not set>

Password: <not set>

Server: <not set>

MMSC: http://mms.msg.eng.t-mobile.com/mms/wapenc

MMS Proxy: <not set>

MMS Port: <not set>

MMS Protocol: WAP 2.0

MCC: 310

MNC: 260

Authentication type: <not set>

APN type: <not set>

Once done with the above, back out, and hit the menu and add a new APN. This new APN will be called T-Mobile MMS. Once created, go into as you did above, and the settings will be virtually identical with the APN type: mms See below:

Name: T-Mobile MMS

APN: epc.tmobile.com

Proxy: <not set>

Port: <not set>

Username: <not set>

Password: <not set>

Server: <not set>

MMSC: http://mms.msg.eng.t-mobile.com/mms/wapenc

MMS Proxy: <not set>

MMS Port: <not set>

MMS Protocol: WAP 2.0

MCC: 310

MNC: 260

Authentication type: <not set>

APN type: mms

Now back out of that, and you will see the two APNS listed. Only ONE will have the radio button available for you to select to activate. When you click the button, it will activate and light up green. When you do this, the 3G/H symbol may disappear for a second. Back out of there twice, and check to make sure that Mobile Network has a check mark next to it, and "Connected" Appears under that. If you see "connection failed" then it's a good idea to reboot your phone. Once you reboot, you can test MMS capability by simply sending yourself a picture message.

Have fun and say thanks.
[HD2 General] dharvey4651:
Are you implying that it auto-switches between the two? If so then this is a fantastic discovery. Otherwise I truely see no real need for 2 APN's..
[HD2 General] buzz killington:
This actually makes sense. We were discussing mms on prepaid without data and it works, so we're pretty sure it goes through t-zones to send mms. The winmo roms probably do have code in them that automatically switches to send, not sure if android roms can figure it out, maybe the nexus one builds can.
[HD2 General] samsamuel:
Nothing to do with figuring anything out. Look at the last line of each settings, apn type.

The mms one should have "apn type mms ", whilst the data one ends " apn type default,supl "

So a default data type app like browser uses the default apn,mms uses the mms apn, and Supl I think is to do with quick GPS.
[HD2 General] a320pylot:
mms

I tried these settings..can send text..but cant send a picture.....any thoughts?
[myTouch 4G Q&A, Help & Troubleshooting] jentzschman2000:
How do I get the home screen like the evo with that cool clock/wheather widget?
[myTouch 4G Q&A, Help & Troubleshooting] CyberStorm98:
Long press on your home screen, select widgets, scroll down to clock and select it. It will bring up a clock widget selector. Hit the right arrow at the bottom until you see the clock you want and hit select. There ya go.
[myTouch 4G Q&A, Help & Troubleshooting] jentzschman2000:
Sweet, thvm.

One more:

I like the curved action bar near the bottom that has the phone icon, app dock arrow, and the fav/cuctom button. How do i get that?

Thanks
[myTouch 4G Q&A, Help & Troubleshooting] stoneyjonez:
You would need to try a different rom with the standard version of sense, or see if you can find some type of theme.

Sent from my T-Mobile myTouch 4G
[myTouch 4G Q&A, Help & Troubleshooting] TeeJay3800:
Like the above post says, you'll need to root and load a custom ROM to get standard Sense on the MT4G. See my sig for a link to the direct port of the Desire HD ROM, it's awesome!
[myTouch 4G Q&A, Help & Troubleshooting] jentzschman2000:
Thank you for the help
[myTouch 4G Q&A, Help & Troubleshooting] TeeJay3800:
No problem! Hit the 'thanks' button if you'd like.
[Galaxy S I9000 General] liveboy100:
hello im new to all this android moding but I come from flashing nokia phone. I would like to know if there is a ROM that looks like samsung original? No cosmetic mods... All I want is speed speed speed. Someone help me :)
[Galaxy S I9000 General] Daneshm90:
1. Wrong section :)

2. If you want speed, stock firmware is as good as it gets imho. All these other "roms" are just deodexed variants which doesn't give you speed improvement just more theming options.

3. What you want is a good custom kernel. I'd recommend trasig's kernel. Been using it for a month now and its very stable.
[Galaxy S I9000 General] liveboy100:
right now im running

2.2

i9000bujp4

karnel- 2.6.32.9 root

froyo.bujp6

+ lag fix but my phone still lags in the apps menu

I wanna update to the latest version but dont know how (kies not working). So roms dont give speed? only karnels do? I also need slovenian language
[Galaxy S I9000 General] Daneshm90:
Like i said considering we're dealing with closed source and all these roms based on same firmware, deodexing,zipaligning...etc won't give you as noticable a difference as will a different kernel

In ur case ur looking for a ext4 kernel. May i suggest voodoo.
[Galaxy S I9000 General] grsgs:
Hello, I've been using darky's ROM since the beginning, and I must say that his 8.0 edition ( gingerbread ) is a hell of a fast ROM indeed ! Cosmetics is reduced to just the gingerbread theme, which is nice and gives a good feeling on SGS.

Hope I helped you with this one
[Galaxy S I9000 General] xan:
Hi I'm new and ignorant.

Hi I'm new and cant read.

Hi I'm new and [ . . . . . .].
[Galaxy S I9000 General] liveboy100:
Stupid know it all. Yes thank you for your help now all i need is a stock theme,guode to update to jpy and guide on how ro instal all of this. Once again im a noob and noobs must exist
[Galaxy S I9000 General] Flynny75:
Try.... Search? The help is here, just look for it before asking the same questions.
[Galaxy S I9000 General] timur525:
Dont talk **** on xan. Uv app is the ****.!
[Galaxy S I9000 General] dcarr622:
<sarcasm>Great attitude bro </sarcasm>

A bit of reading and searching was too much huh? Cripes.

Yes, everyone starts out as a noob. Just most of us choose to follow the well-outline procedures that the experts have already made very clear.
[Galaxy S I9000 General] Darkstriker:
You're WRONG. Newbs must exist. Noobs must not. And newbs should do non-newbs the favor of reading things like the FAQ

before

asking for help on the most basic things. We spend a lot of time making things as easy as possible for newbs.
[Galaxy S I9000 General] AbuYahya:
Hint. Look in general section under sticky. Stock ROM's listed.

The modified ROMs are in Dev section.

I recommend spikes. Installation is in spikes 1st post. But better to flash stock on first attempt.

P.s. if u fight fire with fire u all waste time. If your gonna answer a thread then a negative response takes just as long as a positive response.

sent from mobile