yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 10.1 General] k1mu:
Galaxy tab 7 forum:

http://xdaforums.com/forumdisplay.php?f=1482
[Nokia Lumia 920] alex21074:
Hello, i was wondering, it is possible to change the firmware of the nokia 920 (ie from rm-820 to rm-821 euro)? Also will the frequencies stay? I just want to buy the 920 from rogers and flash the firmware to get my home language on it and be still able to use it on wind mobile))
[Nokia Lumia 920] tomcahill:
It does not appear so, no. I tried to flash my Nokia 920 (RM-820) with a RM-821 ROM and it killed it. Had to wait until just the other day when the RM-820 ROMs finally appeared.
[Nokia Lumia 920] alex21074:
Ok, I guess we can wait and see, because if i cannot add Russian to my planned rogers' lumia 920, then i wont buy the phone at all, i'll stay with my N8((( I know one could flash the lumia 800 to different firmware numbers, maybe they just need to figure out how to do this i guess))
[Nokia Lumia 920] tai4de2:
The Rogers 920 comes with the COMPLETE set of Windows Phone languages, including Russian.

No need to flash any new ROMs.
[Nokia Lumia 920] alex21074:
ok thanks, this is the display language right? not just the keyboard?
[Nokia Lumia 920] tai4de2:
That is correct. All of those are *display languages* and not just the keyboard (there's a separate but similarly huge set of supported keyboards).
[Nokia Lumia 920] alex21074:
ok thank you for the information))
[HTC One S] hungtvht:
I need ship rom for HTC one S [s3] with SID: HTC_621. Please!:(
[HTC One S] Spastic909:
Did you try looking in the dev section?
[Desire HD Q&A, Help & Troubleshooting] jibdev:
Hey guys,

This has been a big problem for me. My DHD often looses cell reception and it doesn't come back so I always have to activate then deactivate Airplane mode to get the bars back. Now first I have to say that this didn't use to happen when I was using the original firmware but for the past year I have been using many ROMs and I always have the same problem. For some ROMs I loose reception once or twice a day and for others more than five times. So if I don't carefully check my phone every hour I could miss phone calls.

I know some of you will tell me to flash the original ROM but really I can't go back from Jellybean to gingerbread. It would break my heart :crying:

So if you have any advice or solution to my problem I would really appreciate it! ;)

Thanks.
[Desire HD Q&A, Help & Troubleshooting] jibdev:
anyone?
[Desire HD Q&A, Help & Troubleshooting] kingofnice:
Try to learn about radios and maybe flash one, carefully...I'm clueless about those...but I think that's it.

- hit my thanks button if i helped you -
[Nexus 7 Themes and Apps] bourne-nolonger:
Just trying out the new keyboard and swype feature. Does it support multi finger swype? sort of like keymonk.

It seems to support it to some degree, but it's sketchy at best. Just curious what everyone else is experiencing.
[Nexus 7 Themes and Apps] nolook:
not sure about the two finger swype but regular swiping is working much better for me than the latest official swype beta...

Sent from my Nexus 7
[Nexus 7 Themes and Apps] bourne-nolonger:
Interesting. I haven't used it long enough to compare it to swype. I stopped using swype though because I eventually got frustrated with it. Good to hear you find it better!

I'll keep playing with it.
[Nexus 7 Themes and Apps] jiiikoo:
Is there any way to turn this feature on, on any other keyboard than the US one? Im from Finland and id be very happy to be able to try this feature.
[Nexus 7 Themes and Apps] bourne-nolonger:
Not to sure to be honest. I guess Google isn't supporting other languages with their swype feature yet?

Sent from somewhere w/ GNex
[Nexus 7 Themes and Apps] ROFLkopter:
I'm using the swipe feature now, I love it. I could never get in to Swype, but I got into the feature with the 4.2 keyboard straight away

Sent from a Paranoid Nexus 7 with XDA Premium!
[Nexus 7 Themes and Apps] Raijin:
Is almost perfect, to not say perfect, because sure Google improves it more.

This is being written with the "swype" feature in my Galaxy Nexus. Too fast, and can be used with another languages. The system detects the route and compares it with the dictionary. Almost always it detect the right word. Sometimes (very few!) it detects another word, so click in the corrector and add the correct. If you enter some word with orthographic errors, it detects it and is introduced and corrected perfectly, like if you are using the normal keyboard. Is good also with punctuation and spaces.

Using it in vertical position and perfect, always I wrote in vertical in old keyboard I have lots of errors because my big fingers. Since I have installed Android 4.2, I don't needed to use the landscape mode, so I'm happy to see how I can write now at the speed of thunder and chat without getting angry :)

Thanks Google!
[Nexus 7 Themes and Apps] rmm200:
If the new keyboard keeps people from getting angry when they chat - it should be mandatory for XDA posters.
[Nexus 7 Themes and Apps] euskalzabe:
Frankly I hate it. It makes no sense in my mind to drag my finger over letter that I don't need for a word, yet through which I have to go in order to get to the next letter I need... I'd much rather type normally
[Nexus 7 Themes and Apps] idbaghera:
I've got last update for my Galaxy Nexus and now I'm on 4.2, i cant find anywhere Swype keyboard ..its on English (U.S.A) keyboard

Why?
[Nexus 7 Themes and Apps] tcat007:
It's just called android keyboard, that now allows swiping. Swype is a third party keyboard you really don't need anymore.
[Nexus 7 Themes and Apps] idbaghera:
Ok i understand is not calling swype on nexus, but android keyboard not working like a swype keyboard, thats is the problem... :(

Edit, its working just in Englis (USA) language :(

10x man
[Nexus 7 Themes and Apps] ezas:
I'm way faster on Swype. I hate trying to hit each key perfectly and and/or moving my hand to enter the suggested. But to each his own.

I have to try this new swipe since people seem to like it.
[Nexus 7 Themes and Apps] punitenshu:
Did they add in any variety of custom dictionary sync? That's one thing I really like about the version of Swype I have now. I no longer need to re-teach the keyboard all the technical jargon every time I get a new device.
[Nexus 7 Themes and Apps] ethanfel:
i got some issue with the newz android keyboard, sometimes the word are show twice
[Nexus 7 Themes and Apps] tcat007:
The personal dictionary allows you to add words directly (Skype doesn't), but I don't think it works. I added a few email addresses and typing the first 2-3 letters don't bring up the address. Swype had problems with words beginning with a number, so does android. I find android just as accurate. I like having a "." on the numeric keyboard that's not on Swype.
[Nexus 7 Themes and Apps] penhapus:
I like it...

never used Swype before because it seemed a bit counter-intuitive, but really like it on the nexus 7 (possibly because typing is a pain normally)

I can see why some people will hate it, mind - some people hate predictive text for similar reasons.
[Nexus 7 Themes and Apps] ezas:
I spent some time with swipe. It's pretty accurate but just feels clunky in places. What I really missed though was the shortcuts that Swype has like swiping from the Swype key to the 5 key to bring up a number pad and swiping from the Swype key to the shift key to change case. And I don't like having to change keyboards to enter numbers. I like the convention of a long hold to get numbers and common punctuation like in Swype.
[Nexus 7 Themes and Apps] punitenshu:
My version of Swype has a '.' on the numberpad. Are you actually referring to the number pad (accessed by swyping from the Swype key to the #5 or long pressing on the "123" key) or the symbol/number keyboard accessed by quick pressing on the "123" key?

Swype also lets you add to the dictionary--it just does it whenever you key in a new word, as opposed to having you specifically go through the hassle of adding words to the dictionary. That's why I was impressed with the versions of Swype that sync online--so I don't need to re-teach it words I've already taught it on other devices.
[Nexus 7 Themes and Apps] tcat007:
Ahhh forgot about the actual numpad. I always found it easier to press the 123 key, and don't think there's a "." there.

The android keypad lets you add words as you're typing too, I just find the "+" in the dictionary more convenient (at least on initial set-up). I also like the nicknames you can add to the personal dictionary, for "words" that Swype doesn't recognize (or suggest)... Like I have "2mark@..." as an email, if it's in Swype dictionary it won't come up as a suggestion, but in android, set a nickname like "mrk" or anything you want, and the suggestion will pop up.

I have nothing against Swype, used it for a year, I just find "little" things about android I like better. I don't type a lot, so may not know all the secrets to Swype (or Android). I do like the new Swype theme options!
[Nexus 4 Android Development] mskip:
/dev/block/platform/msm_sdcc.1/by-name:

lrwxrwxrwx root root 2012-11-13 19:02 DDR -> /dev/block/mmcblk0p24

lrwxrwxrwx root root 2012-11-13 19:02 aboot -> /dev/block/mmcblk0p12

lrwxrwxrwx root root 2012-11-13 19:02 abootb -> /dev/block/mmcblk0p15

lrwxrwxrwx root root 2012-11-13 19:02 boot -> /dev/block/mmcblk0p6

lrwxrwxrwx root root 2012-11-13 19:02 cache -> /dev/block/mmcblk0p22

lrwxrwxrwx root root 2012-11-13 19:02 grow -> /dev/block/mmcblk0p25

lrwxrwxrwx root root 2012-11-13 19:02 m9kefs1 -> /dev/block/mmcblk0p8

lrwxrwxrwx root root 2012-11-13 19:02 m9kefs2 -> /dev/block/mmcblk0p9

lrwxrwxrwx root root 2012-11-13 19:02 m9kefs3 -> /dev/block/mmcblk0p10

lrwxrwxrwx root root 2012-11-13 19:02 metadata -> /dev/block/mmcblk0p18

lrwxrwxrwx root root 2012-11-13 19:02 misc -> /dev/block/mmcblk0p19

lrwxrwxrwx root root 2012-11-13 19:02 modem -> /dev/block/mmcblk0p1

lrwxrwxrwx root root 2012-11-13 19:02 persist -> /dev/block/mmcblk0p20

lrwxrwxrwx root root 2012-11-13 19:02 recovery -> /dev/block/mmcblk0p7

lrwxrwxrwx root root 2012-11-13 19:02 rpm -> /dev/block/mmcblk0p11

lrwxrwxrwx root root 2012-11-13 19:02 rpmb -> /dev/block/mmcblk0p16

lrwxrwxrwx root root 2012-11-13 19:02 sbl1 -> /dev/block/mmcblk0p2

lrwxrwxrwx root root 2012-11-13 19:02 sbl2 -> /dev/block/mmcblk0p3

lrwxrwxrwx root root 2012-11-13 19:02 sbl2b -> /dev/block/mmcblk0p13

lrwxrwxrwx root root 2012-11-13 19:02 sbl3 -> /dev/block/mmcblk0p4

lrwxrwxrwx root root 2012-11-13 19:02 sbl3b -> /dev/block/mmcblk0p14

lrwxrwxrwx root root 2012-11-13 19:02 system -> /dev/block/mmcblk0p21

lrwxrwxrwx root root 2012-11-13 19:02 tz -> /dev/block/mmcblk0p5

lrwxrwxrwx root root 2012-11-13 19:02 tzb -> /dev/block/mmcblk0p17

lrwxrwxrwx root root 2012-11-13 19:02 userdata -> /dev/block/mmcblk0p23

Also provided by c900712 is the Voodoo Report file for the Nexus 4 it may be interesting reading for some people.

EDIT:

Originally posted by Houstonn in post#28

LG Nexus 4 Mako - LGE960 JVP15Q

Number Start (sector) End (sector) Size Code Name
1 1024 132095 64.0 MiB 0700 modem
2 132096 133119 512.0 KiB FFFF sbl1
3 133120 134143 512.0 KiB FFFF sbl2
4 134144 138239 2.0 MiB FFFF sbl3
5 138240 139263 512.0 KiB FFFF tz
6 139264 184319 22.0 MiB FFFF boot
7 184320 229375 22.0 MiB FFFF recovery
8 229376 230935 780.0 KiB FFFF m9kefs1
9 230936 232495 780.0 KiB FFFF m9kefs2
10 232496 234055 780.0 KiB FFFF m9kefs3
11 234496 235519 512.0 KiB FFFF rpm
12 235520 236543 512.0 KiB FFFF aboot
13 236544 237567 512.0 KiB FFFF sbl2b
14 237568 241663 2.0 MiB FFFF sbl3b
15 241664 242687 512.0 KiB FFFF abootb
16 242688 243711 512.0 KiB FFFF rpmb
17 243712 244735 512.0 KiB FFFF tzb
18 244736 245759 512.0 KiB 8301 metadata
19 245760 278527 16.0 MiB FFFF misc
20 278528 311295 16.0 MiB 8300 persist
21 311296 2031615 840.0 MiB 8300 system
22 2031616 3178495 560.0 MiB 8300 cache
23 3178496 15267839 5.8 GiB 8300 userdata
24 15267840 15268863 512.0 KiB FFFF DDR
25 15268864 15269854 495.5 KiB 8300 grow

Mark.
[Nexus 4 Android Development] c900712:
check ur email
[Nexus 4 Android Development] mskip:
Thank you thats everything I needed.

Mark.
[Nexus 4 Android Development] zyy757:
That's really helpful, thank you! And I am interest to know how to get mount point from a new device? Thanks again.
[Nexus 4 Android Development] EddyOS:
Anyone fancy being nice and making a file to use with dsixda's kitchen? Wanna play about with stock ROM build before I get my N4
[Nexus 4 Android Development] Harry GT-S5830:
Just extract system img and then you must make a file for mako to make kitchen work (maybe)
[Nexus 4 Android Development] EddyOS:
All that's the easy part, it's getting the right mount points so it'll flash correctly. Comparing the OP to existing device files doesn't mean a lot to me unfortunately! Here's the edify_defs file for the Galaxy Nexus if someone wants to help out?

# Samsung Galaxy Nexus (GSM/HSPA+)

change_mnt=yes

param1=ext4

param2=HSMMC

sys_mnt=\/dev\/block\/platform\/omap\/omap_hsmmc.0\/by-name\/system

cache_mnt=\/dev\/block\/platform\/omap\/omap_hsmmc.0\/by-name\/cache

boot_mnt=\/dev\/block\/platform\/omap\/omap_hsmmc.0\/by-name\/boot

data_mnt=\/dev\/block\/platform\/omap\/omap_hsmmc.0\/by-name\/userdata

sdcard_mnt=???

fix_boot3=yes
[Nexus 4 Android Development] mskip:
Just download Voodoo Report from the Market and save the output to your usb storage. It will save a zip file to your Internal Storage that has all the info you need.

Mark.
[Nexus 4 Android Development] EddyOS:
Also got the issue of not being able to deodex the ROM using the kitchen as it's not supporting SDK17 yet...d'oh!
[Nexus 4 Android Development] vinnyutd6899:
Any ETA for your tool kit please?
[Nexus 4 Android Development] mskip:
Im working on it right now and have everything set up im just going through all the procedures and adding the FAQ section in the Toolkit.

I will need 1 or 2 testers to make sure the insecure boot image works properly and the nand backup and 1-click works as I dont have a device to test on. As like many others I waited up to order it on the Play Store but had to take my son to school and when I got back it had sold out :(

Any testers available tonight?

Mark.
[Nexus 4 Android Development] c900712:
I can test if you want. Just send me an email when you would like to.
[Nexus 4 Android Development] vinnyutd6899:
i will test it :cool:
[Nexus 4 Android Development] mskip:
Can someone who has fastboot drivers set up please try BOOTING (not flashing) this insecure boot image to see if it boots into Android. If it gets stuck just long press the power button the reboot normally.

Mark.
[Nexus 4 Android Development] MadCobbler:
Yeah thats worked for me
[Nexus 4 Android Development] P0MM3S:
+1

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Android Development] mskip:
Thank you very much I can finish building the toolkit now. I will post when its ready for testing and see who is available. The initial version will have custom recovery operations blocked as it isnt available yet but it shouldnt be long before a working recovery is built.

Mark.
[Nexus 4 Android Development] Kstarz:
I'm up for testing mskip, also any insight as to why these insecure boot images aren't booting after being flashed yet?
[Nexus 4 Android Development] mskip:
Which insecure boot images arent booting? They dont need to be flashed, just booted to boot the phone and give adb root access.

The one I made and posted a few posts back has been reported to work fine.

Mark.
[Nexus 4 Android Development] Kstarz:
Yes booting it works fine but flashing it doesn't and I am unsure why it doesn't.
[Nexus 7 Q&A, Help & Troubleshooting] Count Magnus:
[Q] Update Nexus 7 to 4.2 using ClockwordMod Recovery - "assert failed" (Status 7)

Can anyone help.

I am updating my Nexus 7 to 4.2. I am using customer recovery "ClockwordMod v6.0.1.0"

After its Verifying the current system......

I get an error

assert failed: apply_patch_check("/system/bin/gzip", "52721e60f8823587e11849ce524854559b88e7de", "afdda757b22b444f41726d2c1a83012869")

E:Error in /sdcard/094f6629314a.signed-nakasi-JOP40C-from-JZO54K.094f6629.zip

(Status 7)

Installation aborted.

Not clear what this means.

I got a simular error when I tried to update normally with Stock recovery. When I tried it this way earlier it did not work and I got to the Android on his back with the Red Triangle. I then got in to Stock recovery but the error above was simular.

Any help appreciated.
[Nexus 7 Q&A, Help & Troubleshooting] gokart2:
Believe it means that files checksum doesn't match what they think it should, meaning it was modified. So if it doesn't match, no flashy. Had the same issue with my build.prop, fixed it. Then it failed on the file for the 720p camera mod. Tried fixing it.... but that's a no go. Basically if you can find a stock rooted ROM, then copy over the file that fails....u should be good.
[Nexus 7 Q&A, Help & Troubleshooting] Alejandrito:
I downloaded and tried an unmodified file and got the same error upgrading from 4.2 to 4.2.1
[AT&T, Rogers HTC One X, Telstra One XL] ez4nick:
I have been looking on amazon for a micro usb otg cable and they are pretty cheap (no more than $2), but most of them say they will take 17-28 says for standard shipping and I think that is pretty crazy. So for anyone who as bought one where did you get it from? Somewhere besides amazon or did you wait for it?
[AT&T, Rogers HTC One X, Telstra One XL] ez4nick:
ok then what is the right section?
[AT&T, Rogers HTC One X, Telstra One XL] CheesyNutz:
hmm lets think about this for a bit .... think REAL hard :confused::rolleyes::eek:
[AT&T, Rogers HTC One X, Telstra One XL] ECEXCURSION:
It's the q and a section man...

Sent from my HTC One XL
[Galaxy Note II Q&A, Help & Troubleshooting] G.H.O.S.T_13:
hi,

i would like to change the voice of my GPS , the wife who give the help to find my road in the gps is completly horrible !!:eek:

is there a way to just change the voice ..??
[Galaxy Note II Q&A, Help & Troubleshooting] HJADR:
I assume you mean the voice of the googlemaps lady. Every navigation has his own voice. Tomtom software can change the voice. But I too love to change the googlemaps women.
[Galaxy Note II Q&A, Help & Troubleshooting] poplectic:
Yep get a new wife thats my tip.
[Galaxy Note II Q&A, Help & Troubleshooting] monkeybone12:
There is a program that does this. Costs money.

Called assistant by speaktoit.

Epic4GT with different ROMs every few days. Thanks Devs!
[Galaxy Note II Q&A, Help & Troubleshooting] G.H.O.S.T_13:
I've recently installed the OMEGA rom , and when i used the Googlemaps GPS , the wowen voice was nice , but google told me to install the original voice ... how can i get back to the voice from the OMEGA rom ..?
[Android Software/Hacking General [Developers Only]] dee890:
Hello I am trying to create and flashable .zip file that alters just the Audio file. Can I create a zip file that can be flashed on any rom? I want to replace the Audio file with my own in system/media/audio.

Here is my thread to help better explain:

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

If I put the META-INF file into the zip Does that alter the rom META-INF when someone flashes it?

Any help would be great!!!

Thanks
[Galaxy S III General] Obagleyfreer:
**** SAMSUNG HAVE APPLIED A SUDDEN DEATH FIX VIA A SOFTWARE UPDATE****

STOCK KERNEL: XXELKC AND NEWER

STOCK RECOVERY: XXELKC AND NEWER

ALSO ANY CUSTOM KERNEL AND RECOVERY THAT ARE BUILT FROM THE UPDATED SOURCES. THERE HAVE BEEN CASES OF SDS ON DEVICES THAT HAVE UPDATED BUT TO WHAT EXTENT THE DAMAGE WAS AT ALREADY BEFORE FLASHING WE DON'T KNOW.

WHO'S AFFECTED?

It seems that at the moment the only devices that have suffered from SDS are the 16GB version with:

eMMC: VTU00M

FW Rev: 0xF1

To check your eMMC version download eMMC Brickbug Check from Google Play.

What you want is the eMMC version and the FW Rev.

THE FIX

Samsung have now released a Sudden Death Fix via a patched Kernel and Recovery in latest firmware. Firmware Version: XXELKC

Simply update OTA or download XXELKC firmware (or newer) from sammobile.com and flash using Odin.

You need both the stock recovery and kernel installed for it to work properly, or a custom kernel and recovery built from the updated sources

ie Latest Perseus Kernel and PhilZ Recovery are examples

LINKS

For more info about SDS, who could be effected and how to fix check out this awesome thread by rootSU

For a detailed look at how the fix works check out this thread here.

WARRANTY

For those of you in Europe who have rooted your phone it appears that this doesn't void warranty. Check this thread for more info.

Also this website could prove very handy for anyone with a European or UK handset that has died.
[Galaxy S III General] DeadSOL:
Okay, here's what just happened to me:

I went to sleep in the night with my phone's battery at around 29%. I just woke up and my phone's home button wouldn't respond. Then, the power button wouldn't respond! I took the battery out and put it back in. It still wouldn't respond! So, I plugged the charger in and then it showed me that it had begun charging. I turned the phone on and as soon as it reached the lock screen, it turned itself off. It did that twice more so I decided to let it rest. Now, it turns on. (>_>)

Apparently, 29% of its battery was somehow consumed last night. I really don't know how!!!! My wifi was on,it seems, but around 30% battery drain in just a few hours?!! That's insane! I'm on stock DL4. Not even rooted!

So it's not a "death" case, per se, but I had a really bad scare. :(
[Galaxy S III General] UncleBeer:
What happened: Went to bed, left phone on charge, woke to the green "fully charged" light, but no response to buttons. Pulled the battery to make it reboot, and now nothing. Neither download nor recovery modes, no charging light, nothing. It's off for repairs.

What ROM/Firmware: Wanam's J5 (which I'm convinced had nothing to do with it.)

What kernel: stock

OV or UV: Nooooo

Where phone was made: No idea

Where battery was made: stock; no idea
[Galaxy S III General] Shug69:
Seems like a weakness somewhere on the motherboard. Mine died on charge about a month ago. No led no nothing bought in late May. New motherboard working fine. Hoping the problem is identified and fixed now and I don't have the same **** again in three months time.
[Galaxy S III General] ph512:
My story started last Tuesday night. My S3 was working fine: used it as satnav getting to work for night shift and used it a few times at work until I checked it at approx 9:30pm (about three hours into shift) and it was dead - nothing would make it respond.

Got home next morning and my caring wife asks me if it's still the same - I dishearteningly relied that it was. Then she announces that hers was now dead! She had been using hers normally the night before, as I had. She had plugged it in to charge overnight and when she woke in the morning the green light was on, but she couldn't turn it on - she did battery pull, etc, but nothing would revive hers either.

Clearly something has killed our S3's, but not spontaneously as we were in different places at the time of failure. Mine had been happily charging whist I traveled to work and it had over 80% the last time I had noticed / used it before it died - my wife's just died on the charger overnight at our house.

Two dead S3's in the space of 9 hours and I have no idea why...

Both were stock unrooted international models purchased from carphone warehouse at the same time. Both had the recent JB update too (I did both via Kies when it was released).

The only common element I consider could be a cause is the charger we use in our house (but as mine died some time later after being used for several hours away from my house I really don't see any technical explanation for it).

I'm baffled - Carphone warehouse faults tracker now says they have fixed them both and they are awaiting dispatch to our store for collection - maybe they can then offer soom explanation of thefaults / causes.

Either way I reckon I'll bin the "common" charger as a "just in case"!