yashsingh1/xdaforums huggingface dataset:
[MDA II, XDA II, 2060 ROM Development] pichit_assa:
I got this "ERROR 100: MODEL ID ERROR",... pl help

I try to upgrade XDA2 rom from "ruu172104wwe_t-mobile-uk" to "XDAII_172181_Final" and I got this error "ERROR 100: MODEL ID ERROR"

How can I slove this problem?

First I have O2 rom and I upgraded to "ruu172104wwe_t-mobile-uk", when I try to upgrade to "XDAII_172181_Final" everything look fine till the error occur I can open my O2 anymore on the screen show just message "serial v1.03"

Please help,.. Thank
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brianrad:
Okay so I know this may sound impossible but is there any way I can get some of the gestures from the Galaxy S4 on my S3? Basically I only like the hand swipe to unlock and for switching through music and stuff... Is there any application or rom that can do this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
try any aosp Rom
[Verizon Samsung Galaxy S 4] petec920:
Hi all im new to samsung coming from htc everything jas seemed to be alot easier but my question is will there eventually be a pure android 4.2.2 and also where is the file for ota update so I can stop them thanks much I advance for any help
[Verizon Samsung Galaxy S 4] Eric214:
Technically all you have to do is freeze a Verizon app like Backup Assistant Plus (just one you couldn't normally disable if you weren't rooted) and if an OTA tries to do anything it will see your rooted by the fact it can't see those apps and the OTA will fail anyway.
[Verizon Samsung Galaxy S 4] petec920:
Thanks much yea I started using titamium backup to freeze uninstall stuff but I wanna I gues get my ram usae alot lower so battery is evem better than what it already is lol
[Android Q&A, Help & Troubleshooting] juancarlos_la:
Hello mates!

I have a I9300 SGS3 and I decided to change the ROM to a Akop, but I've had several drawbacks:

- The main problem is that sometimes the phone is locked. Light touch buttons respond, but the screen freezes and I have to pull the battery or hold down the power button for several seconds. This causes problems, because it seems that the data is corrupted, and when you start again, you delete the application settings, and sometimes the phone does not start, and should I reinstall the ROM.

- Eventually, when I open the panel automatically closes applications, and so if I try several times. This does not happen often, but a couple of times a day

The installation procedure I follow is as follows:

1. Enter to recovery mode from CMW touch 6.0.3.1

2. Wipe data / factory Reset

3. Wipe cache partition

4. Mounts and storage -> format /cache

5. Mounts and storage -> format /system

6. Mounts and storage -> format /data

7. Mounts and storage -> format /preload

8. Mounts and storage -> format /sdcard

9. Mounts and storage -> format /data and /data/media (/sdcard)

10. Advanced -> wipe dalvik cache

11. Install zip from sdcard -> choose zip from external sdcard -> Install ROM package

12. Install zip from sdcard -> choose zip from external sdcard -> Custom Kernel

13. Install zip from sdcard -> choose zip from external sdcard -> Install Gapps

14. fix permissions

15. Reboot system now

I hope you can help me with this problem because I can not find any solution.

My thanks in advance.

Greetings!
[One (M7) Q&A, Help & Troubleshooting] Sedariya11:
Hi guys got my hands on HTC One yesterday and I noticed that on top of the status bar there is an extra light coming from the screen.. Is it normal like everybody had it or its just me? Can anyone Pl confirm? Thanks below is the pic:
[One (M7) Q&A, Help & Troubleshooting] Riyal:
It's part of the theme of sense 5 don't worry.
[One (M7) Q&A, Help & Troubleshooting] Sedariya11:
Thank you very much buddy I m very relaxed now.. I was so worried but you are a savior.. I could have given 1000 thanks but it's not allowing me .. Lol.. Thanks again buddy.. :beer:
[One (M7) Q&A, Help & Troubleshooting] ECEXCURSION:
Lol I had the same concern the other day when looking for dead pixels.

Sent from my HTC One
[One (M7) Q&A, Help & Troubleshooting] Zepid:
Hah, I only just noticed it on mine, you have great eyes! :laugh:
[One (M7) Q&A, Help & Troubleshooting] Riyal:
Hahaha! No worries mate! I myself was worried about that also for days when I first got it! Found it on the homescreen then tried opening the app drawer and it's still there. Tried other apps and it still persists. I just noticed it's a theme when I boot into recovery and didn't saw it anymore.
[T-Mobile, Samsung Galaxy SIII] dpshptl:
Does anyone know what the read and write speed is for the internal memory?
[Ouya General] mybook4:
I don't know about you guys, but my Ouya stays on 1080p all of the time. This would normally be great for most uses, but Mupen64plus is a tad laggy at 1080p. I'd rather play at 720p so things might be smoother.

I googled a bunch, but couldn't find much on how to force a manual resolution change (short of buying a 720p-only TV…not an option).

I did some digging of my own. Here's what I found:

In /sys/class/graphics/fb0 are several files I believe are related to HDMI output:

"cat mode" displays:

"cat modes" displays:

I figured I would take a shot at changing the resolution to 720p. I performed the following as root:

When I ran the command, the screen went blank (at least it did something, lol).

I then tried to change back to D:1920x1080p60 with the following

The screen remained blank. I tried several other modes in the list 600p, 480p, 768p, but none worked. I set mode to D:1280x720p-60 and rebooted the Ouya. The console booted back up, but it was still in 1080p. I checked the mode file. It had reverted back to D:1920x1080p-60.

Hopefully this helps us get somewhere
[Ouya General] Paulenski:
I need this on my TV, I haven't checked what it's outputting thru adb(it's connected to comp atm) but it's oversizing when I first got the console. My guess is it's forcing 1080p on the TV.
[Ouya General] GizmoTheGreen:
I've got the same issue, there's really no reason to not have settings for this, it's really stupid :/
[Ouya General] FrostyWolf:
If it's just leaking a bit off the screen you need to go into your TV settings and adjust overscan. I've plug it into 2 1080 and 2 720 tvs and have had no issue besides that.
[Ouya General] sonofskywalker3:
I have a cheap insignia tv with no overscan settings, only zoom, and even the best one doesn't show everything...
[Ouya General] professorpoptart:
For years I didn't know my tv had it. Mine calls it "hd size" hidden 3 menus deep.

Size 2 is what I set it to
[Ouya General] GizmoTheGreen:
it's quite alot missing and my tv has no overscan settings. there was 16:9, 4:3, zoom 1 and zoom 2. neither helped any (zoom just made it worse)

it's a 1366x768 resolution tv but it obviously takes 1080p and scales it down (my ps3 works fine in 1080p!)

I'm hoping 720p output from the ouya would solve it.
[Ouya General] FrostyWolf:
Strange! I've tried in on a couple of monitors of various resolutions and sizes since my last post, but same on all of them, so I can't even replicate this to test options to fix it :/
[Ouya General] GizmoTheGreen:
I seem to have slight more luck doing this:

1. echo 0 > /sys/class/graphics/fb0/device/enable

2. echo (videomodefrommodesfile) > /sys/class/graphics/fb0/mode

3 echo 1 > /sys/class/graphics/fb0/device/enable

atleast I get picture after doing this but it's the top half center of the screen only... :/
[Ouya General] Asadullah:
I don't have my ouya yet but try an app like anycut that allows you to make activity shortcuts. I used it on my htc evo 4g lte to make a shortcut that would change the screen resolution to 480p. Also maybe a build.prop edit would work.

Nope tested out anycut it's a no go
[Ouya General] muriani:
I intend to use this primarily on a 4:3 display, through a VGA adapter.

What sucks is that no matter what /sys/class/graphics/fb0/mode is set to (1280x1024 in my case), the Ouya insists on only using a 16:9 viewable area... restricting games like Towerfall and retro emulators to a little box in the middle of the screen.

Also, if 1080p or 720p modes are not read in the monitor EDID, it defaults to a letterboxed 640x480 which is even worse.

Heck the 360 supports 4:3 displays appropriately, even if the game doesn't. At least if the game has a 4:3 mode it can use it, and isn't forced into letterbox.
[Ouya General] khanning88:
You can change resolutions using the activity manager command.

'am display-size'

eg.

am display-size 1920x1080

am display-size 1080x720

am display-size 720x480
[Ouya General] Xerion:
That only changes the virtual size, not the actual displayed resolutions. So far nothing works to actually display at 1280x720 on ouya, whereas some android stick I have lets you just choose that resolution and works fine at the same monitor. With the ouya I'm stuck to 640x480, so I can't use with the screen I intended and have to buy a new screen now :/
[Ouya General] muriani:
That works to some extent for me, through my VGA adapter.

For example, if I echo D:1280x1024p-74 > /sys/class/graphics/fb0/mode

then I'll get a 1280x1024 screen on my 4:3 LCD, but with only a 16:9 play area.

Using am display-size 1280x1024 will crop it down to a 4:3 720p instead of filling out the rest of the screen.

At this point I'm not sure if I'm running into limitations on the ouya, or fighting the VGA adapter. Eventually this all does have to go through the VGA adapter as the display I'll be using has no DVI or HDMI input.

E: While connected directly to my LCD via HDMI->DVI, it's actually quite curious, if I set the resolution to 1024x768, and confirm on the monitor that it is receiving that res, I have a letterboxed 640x480 play area in the corner.

When I am display-size 1024x768, the play area SHRINKS further. I think this does not quite what we expect.
[Ouya General] TopherBarnett:
Same thing happens to me with HDMI-DVI into a widescreen monitor. Curious part is that none of the widescreen resolutions actually show up in the modes file. On the off chance, I tried echo D:1280x720p-60 > /sys/class/graphics/fb0/modes, but it didn't work.
[Ouya General] muriani:
You have to use one of the modes listed in /sys/class/graphics/fb0/modes.

Also, echo it to /sys/class/graphics/fb0/mode, not modes.

Before you do, echo 0 > /sys/class/graphics/fb0/device/enable, echo your mode, and then echo 1 > /sys/class/graphics/fb0/device/enable

If your screen is still blank, try hitting a button on the controller.
[Ouya General] TopherBarnett:
Sorry, should have been more clear. I did all that, I was just trying to see if I could add an extra resolution into the 'modes' with "echo D:1280x720p-60 > /sys/class/graphics/fb0/modes", then activate it in the 'mode' with "echo D:1280x720p-60 > /sys/class/graphics/fb0/mode". No luck.
[Ouya General] muriani:
Ah, no.

I may be way off, but from what I can tell the entries in modes are more like aliases to the stored monitor EDID settings.

Oddly enough, the -60 modes almost never worked for me. I tended to use -74 modes if they were available and those worked better.

Out of curiosity, what are the contents of your modes file?
[Ouya General] TopherBarnett:
D:640x480p-60

D:640x480p-74

D:800x600p-59

D:800x600p-74

D:1024x768p-60

D:1024x768p-74

D:1280x1024p-74

D:1280x1024p-59

D:1152x864p-74
[Ouya General] muriani:
...huh. And this is a widescreen monitor? Those are all 4:3/5:4 aspects.

Try D:1280x1024p-74 if you don't mind, and let me know what happens.

That's worked best for me, but with a 4:3 monitor. Not sure how it'll act on yours.

The only other option I can think of is one from the other thread - the HDMI switch with the EDID spoofer.
[Ouya General] TopherBarnett:
At 74 I get a really weird sync issue. At 60, the picture is there, but its smaller and toward the upper left hand corner.
[Ouya General] muriani:
Strange.

I think the only solution for you is gonna be something that spoofs the EDID like that switch.

Ouya really needs to fix that.

Something else I've noted is that occasionally the modelist isn't consistent. Sometimes it'll report a very limited set of modes, sometimes I get more after unplugging the cable and plugging it in.

Weirdness.
[Ouya General] Grawl:
I have the cheapest full HD TV possible (125 Euros, 22"), and mine can change the screen size. Your TV should be able to do that too.
[Ouya General] TopherBarnett:
Yes, a lot 1080p TVs are able to 720p as well, but that option may be several menus deep or possibly non-existent on some models. It still doesn't play nice with computer monitors though. A ouya-side software solution would fix both issues.
[Ouya General] kpa2727:
I have some interesting results. I have 2 Lcd Hdtv's 32 inch, 720p only, Samsung i'd love to use. it's a 2006 but theres no ability that I've found in service menus or normal to turn off overscan. so i'm boned there, for kicks I linked it up to my insignia 42 inch from about 2011 era. I got the same screen cut I was like great same crap, then magically I founda overscan setting in menus. turned it off and every emulator I ran side loaded or not including apps looked fantastic. the scale was right and everything was crisp. So in my opinion confirmed this is a Overscan issue. what we need to do is figure out how other android devices scale to overscan then implement that here.
[Ouya General] crymsonfyre:
any luck!?

Any?
[Ouya General] pedrovay2003:
Does the Mod Collection for Ouya really not work? I set it to 720p in there, and I was able to get 60fps, 720p recordings from an Elgato Game Capture HD. The model I have can't record 1080p and 60fps (it has to be either 720p/60fps or 1080p/30fps), so to get that framerate, it had to be 720p. Games also run noticeably better when I set it to 720p in the Mod Collection, too.
[T-Mobile, Samsung Galaxy SIII] Brawsley:
Greetings! This is the first time I've felt compelled to post in the forums, so I apologize in advance if this happens to be in the wrong section. I've been running CyanogenMod 10.1 on my Samsung Galaxy S3 SGH-T999VVLLH2 (Mobilicity) for quite some time now, and have only recently been interested in downloading and installing the nightly installments that are released.

I haven't had any issues installing the new nightlies at all, until seemingly after revision 20130513. It seems that after this installment, I receive an "assert failed, get prop, status 7" error, upon the attempt at installing any newer nightly revisions. Now, I did a tremendous amount of digging around before I decided to make the post, and discovered that within the newer revisions, the updater-script now seems to flag certain Baseband versions of the phone, and prior to revision 20130513 (currently have), it didn't, and I had no issues installing.

When I go into the CyanogenMod settings, all of the nightly updates are available, as usual, up to the latest at the time of the post (20130524) but none will install. In the latest revisions the updater-script does show a similar version (T999VVLDLL1), which I've come to understand is an update for the software.

Am I required to do another update before installing the latest CyanogenMod 10.1 nightlies? Or is there another solution I haven't discovered yet? Any help regarding this would be greatly appreciated. Thanks!

On a side note, I am running the latest ClockWorkMod Recovery as well.
[T-Mobile, Samsung Galaxy SIII] squabbi:
Im surprised that it happened to you on an AOSP recovery. Usually it happens when its a modded recovery with a kernel.

Try TWRP. Or check for an update. :)
[T-Mobile, Samsung Galaxy SIII] TheLastSidekick:
You need to flash a firmware update that will update the bootloader. Not the UVDMD5 one though for sure because that's for T-Mobile. Maybe the other one. Lemme try linking you to the thread.

Edit : here read up on this before flashing http://xdaforums.com/showthread.php?t=2290118

T999V VLDLL1 Bootloader + Modem (Flashable .zip)
[T-Mobile, Samsung Galaxy SIII] yanikd:
Correct. Once I flashed this my random reboots completely stopped.
[T-Mobile, Samsung Galaxy SIII] yotaxd:
I have same problem and same phone t-online Firmware is up to date but i rooted for first time with no problem but cyanagon wont instal status 7 error. Please help
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
The latest T999V firmware is VLDMF2. It's been out less than a week so many cm and aosp roms will not have added I to their asserts to allow install.

Downgrade to LL1 firmware for now and it should flash.

Or change the asserts in the updater script
[T-Mobile, Samsung Galaxy SIII] yotaxd:
I have 4.1.2

Dunno i live in europe. thought firmware is different than us or so

First i used this i used "cm-10.1-20130716-NIGHTLY-d2tmo.zip" and "gapps-jb-20130301-signed" but Statuts 7 error than i tried : T999V_VLDLL1_noradio_v3 but there is also Status 7 error.

when i boot into recovery mods it says CWM-based Revovery v5.5.0.4 : : CF-v1.5 is this OK ?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Well first thing you should do is update that old recovery. May be that's all you need.

The reason I mentioned the T999V firmware is because that's what the rest of the thread was for, so I assumed that's the model you had.

What model is your device? The T999 is a US only variant, the T999V is the Canadian variant. The European models should be the international ones, I9300.

If yours is international, do not flash anything you find here!
[T-Mobile, Samsung Galaxy SIII] yotaxd:
If yours is international, do not flash anything you find here!

i do not know if its internatianl oder t-mobile. but it should be t-mobile because starting the phone there is t-mobile logo and it is rent from t-mobile

:)

anyway i installed new recovery 6. via google play but in recovery mode there is still Status 7. even its t-mobile. i can try every version because there is always status 7 so i can not damge phone installing wrong version i think.:confused: o the other hand i have always wipe chare/ factory before installing the cyanagenmod. i must restore data now and system setting by advanced backup thats kinda annoying. but next i should maybe try INT. now:rolleyes:
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
If you don't know what model it is, don't flash anything!

Look under the battery.
[T-Mobile, Samsung Galaxy SIII] DJ_SpaRky:
They are adding the assert for T999VVLDMF2: http://review.cyanogenmod.org/#/c/45740/
[T-Mobile, Samsung Galaxy SIII] ohhacker:
[SOLVED!!]

i have this problem too when i want to install some roms like AOKP and JB 4.2.2 , i get same error !!

just go to recovery mode cwm then

go to mount and storage ---> unmount /system

now format /system and /data

try agian install cm rom , and it'l work :D :good:
[T-Mobile, Samsung Galaxy SIII] vialsofliquid:
HTC One

you guys got any ideas on the att M7 version of this problem. im almost positive i RUUd in order to flash CM but i couldnt get it to work. im on KitKat now cant get it to sideload or install from sd.

got any ideas?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Unique Boy:
I had a problem with my galaxy note n7000. The problem is on camera.

When using the camera in the dark flash turned on but when the picture is taken turns off right before the picture is taken. And leaving me with a dark picture. So I think the problem is on timing of flash.

??? Does anyone know, how to fix this problem?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Varad297:
is the phone rooted? you can try using the camera with an app like camerazoom fx.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Unique Boy:
Yes I have rooted

I have tried !! Till now no luck.:confused:

Is there any application to switch lower microphone to upper one.:cool:
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Varad297:
Is the phone rooted? Go to google play and download the app camerazoom fx. And then use the camera with that app. I do not know of any application for doing the microphone sswap
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Unique Boy:
Still camera having that problem. It seems photo is taken with flash. But after taking photo when I view it, photo is dark ( like photos without flash in dark place).
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Varad297:
Try to use the option of torch flash (a type where the flash will be perpetually on) try such options. Is the phone rooted...answer this question!)
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Unique Boy:
yes I have rooted. (I have told it on my second post)

On torch flash it works but it keeps flash ON until photo is taken. On any other option it didn't work.

I want to make it work on other options like auto, or flash ON option. Any idea?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Varad297:
Well u can try reinstalling the camera.apk in the /system folder. Else if the torch flash works well it's ok isn't it?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Unique Boy:
if there is no other option than flash torch than it is also enough. :rolleyes: but I have noticed that on flash torch the flash is not much brighter...

AND one more question

will camera flash problem be fixed if I buy and replace camera?

thank you Varad297 for your help
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Varad297:
Well it's true that torch flash isn't that bright. And i don't think a new camera can do it. But if your phone falls in warranty then you surely can unroot and send it to samsung service. Looks more of a software problem, and also a quite unique one too! Suggest u to private message some if the experts at xda for better help. :)
[RAZR HD Q&A, Help & Troubleshooting] charles47:
Does anyone know where I can find a good link to a CWM recovery file for the XT926? I have googled the piss out of it and all lead to the goo.im site and it says the file is no longer there.

Any ideas? Thanks
[RAZR HD Q&A, Help & Troubleshooting] killrhythm09:
Can't find a link to just CWM, but here's one that has TWRP and the stock Moto recovery also (just toss those if you don't want them):

http://d-h.st/ZOG
[RAZR HD Q&A, Help & Troubleshooting] charles47:
Thanks! I'm willing to try anything. BTW will that work as a recovery file I can use in ROM manager?
[RAZR HD Q&A, Help & Troubleshooting] killrhythm09:
I haven't tested it personally since I use TWRP, but it should work.
[MDA, XDA, 1010 Software Upgrading] bozo500:
Hi, I am very new to this hardware , I surfed this forum for two days tried to upgrade using Special Edition 1.2 ROM but when I run the program, it gives me following error and nothing happen.

ERROR: GetConnectionType - An existing connection was forcibly close remote host

Error getting connectiontype.

I used different computes another laptop but same problem, please HELP.

I am using Activesync 3.7 as 3.5 does not get connected.

Here is my phone detail

Hardware PW10B1

ROM Version 4.01.16 ENG

ROM date : 02/04/04

Radio Version : 6.25.02

Protocol Version : 32464
[MDA, XDA, 1010 Software Upgrading] LumpiStefan:
ROM 4.01.16 does not allow downgrading via Exe-Method.

You have to flash your device via SD-Card and Bootloader.

Stefan
[MDA, XDA, 1010 Software Upgrading] bozo500:
Hello, but I thought some of the users in this forum did unlock without using SD card, may be I am wrong.

One more request what type of SD card XDA takes, either plain SD card or SD/MMC card.

Help appriciated.
[Android Q&A, Help & Troubleshooting] t0ast1ng_t0ast:
Does anyone know of any good stock jelly bean looking status bar and notification menu apps that dont require roots? touch wiz looks awful and im trying to make it go away

the_t0aster
[General Monetization] Heisenberg420:
So I recently spent a great deal of time writing an app that changes CPU settings and it requires root. The only paid apps out there similar to it are setcpu and a few others. Obviously these apps are only available to root users which has to be less than 10% of the whole market...

What steps can I take to monetize it to its full potential? Its a capable app.. One of the main reasons I started this project was to do things that setcpu and trickster couldn't do.

Is it OK to start out at .99$ and expect people to buy it?