yashsingh1/xdaforums huggingface dataset:
[Sony Ericsson XPERIA X10 Mini] Crazy Seed:
I don't know 2, but i notice this thing when i'm in the street and the Sun is a little stronger, i hardly can see what's on the screen even with full brightness in Gb Roms, but on Eclair i was able to see good :S, so that's why i wanted to set equal values on Gb roms like on Eclair in terms of brightness.

I'm currently using ultra-brightness, better than eclair it's not, but i don't know yet if it is good enough to see good with strong sun xD :S , but maybe it can solve the problem xD, but setting ultra-brightness On or Changing values of brightness to higher will it be the same in terms of Battery consumption?.

Thanks for answer :)
[Sprint HTC One (M7)] SeanBond:
This is all I want: Dropdown Notifications, rooted.

Thats it, I don't want any horrible themes, any transparent crap.
[Sprint HTC One (M7)] Sloth:
Stock rooted :thumbup:
[Sprint HTC One (M7)] felacio:
No, no, no. You don't want stock rooted. You want something like stock rooted. Only stock rooted can give you that.
[Sprint HTC One (M7)] flex360:
nah man

only stock rooted does that man

come on

only stock rooted
[Sprint HTC One (M7)] sauprankul:
C-c-c-combo breaker!

In all seriousness, I'm pretty sure there is a flash able zip available for viper ROM that takes away the transparency.

And don't insult the devs' hard work, even if you don't completely agree!

It's on the Viper page. 3rd post I believe.
[Sprint HTC One (M7)] felacio:
Don't be such a fan boy. "Stock rooted"? Are you daft! He clearly wants stock rooted.

"Stock rooted"... don't make me laugh!
[Sprint HTC One (M7)] FrostyF7:
Common br0s he obviously wants stock rooted with some stock rooted features. All of you need to get it together...
[HTC Droid DNA] Infinite Jest:
Now that the cat is out of the bag as to the cause of the DNA's color woes (kudos to beaups), I thought I'd throw something else out there. I've noticed now across both sense 4+ and sense 5 ROMs that the DNA employs some kind of very aggressive dynamic contrast algorithm as dark images or large amount of text moves across the screens while slowly scrolling though it, especially noticeable in browser applications, effectively cause a 'pumping' or manipulatable shift in display brightness. Obviously, this is most jarring when the majority of the background is white and darker areas are introduced. Also, it occurs both with auto-brightness on and off, being most noticeable at lower brightness in darker ambient conditions. I've used various kernels with the same behavior. I know that this feature is commonly used in media presentation, but it seems way overdone in general use outside of videos compared to other devices I own and have owned in the past. I'm curious as to whether this is possibly something kernel or OS related that could be addressed or a deeper issue. Thanks.

Finally, it appears to be present in the HTC One as well:

http://xdaforums.com/showthread.php?t=2243483
[HTC Droid DNA] t1gartist:
im going to say kernel but dont hold me to it as i dont know exactly how the os controls that aspect of graphics

what rom are you on
[HTC Droid DNA] Infinite Jest:
I was on a couple of sense 5 ROMs, viper DNA, and now Carbon and all have exhibited this issue with different kernels.
[HTC Droid DNA] Infinite Jest:
Any other thoughts on this? It must be a source kernel " feature" but it still annoys the hell out if me.
[LG Optimus G Pro] andygold:
I don't think i noticed this until the recent Value Pack update. Maybe it was happening before, but I'm not sure,

If I open an email from the stock email app and then either pinch together or apart, when I let go, the part of the page where I just was is no longer there and I'm left in an entirely different part of the page. For example, I might be on the bottom of the page, and pinch inward to shrink it a bit. I'm watching the image under my fingers shrink, maybe 1/4", and then I let go to view the smaller image. Problem is that once I let go, I might be anywhere on the page, and it might bring me back up to the top, or anywhere else. I can't find any reason for this, and I think it's a new phenomenon for me, since the upgrade.

Anyone else seeing this? And is there a fix for this? It does not happen when I'm using a browser, just email.
[Nexus 4 Q&A, Help & Troubleshooting] ntn359:
I want to know what's the difference btw nexus 4 rev10 n rev11?

Sent from my Nexus 4
[Nexus 4 Q&A, Help & Troubleshooting] Sn00ky:
http://celltraderonline.com/content.php?118-Knowing-The-Difference-Nexus-4-REV-10-Vs-Nexus-4-REV-11
[Upgrading, Modifying and Unlocking] rik_trendell:
Hi there,

I have an XDA 2 running Microsoft Pocket Pc Version 4.20.0. I would like to install WM 200 SE, please can you tell me where I can get this from. Also I have unlocked mine from O2 so I can use my Orange Sim, is there anything I need to do when istalling WM2003SE as I dont want to loose any settings etc...

Rik
[Upgrading, Modifying and Unlocking] rik_trendell:
XDAII

1.72.00 WWE

Radio: 1.17.00
[Upgrading, Modifying and Unlocking] Rudegar:
http://www.milinkito.com/swf/bart.p...+bart+a+dull+boy....&Submit=Crear+nueva+frase

;)

http://xdaforums.com/viewtopic.php?t=16916
[Upgrading, Modifying and Unlocking] rik_trendell:
Hi I don't quite understand all this stuff about the ROM? also whats that link (milinkito) all about?
[Upgrading, Modifying and Unlocking] blackhat:
i have the same problem, i want windows mobile 2003 second edition but i am not sure how to install it, and i dont know too much about anything with rom, etc.

my info:

rom version ; 1.60.00WWE

rom date ; 12/03/03

radio version ; 1.10.00

protocol version ; 1337.18

extrom version 1.60.50

i want to install the latest stuff so when i hard reset my pda it wont goto windows mobile 2003, i always want second edition but i am a newbie.
[Upgrading, Modifying and Unlocking] blackhat:
and i also don't know where my pda was made, when i look at the bottom of the box it says made in taiwan, whats the difference between the england and australian etc, can I use that sin thing?
[Upgrading, Modifying and Unlocking] Rudegar:
the milinkito site is an atempt at being humours since if it display right should show bart typing

"all ask and no seach makes bart a dull boy"

as in a ref to the shining added that all this infomation is available to people who take a look round the forum

about the install being somewhat diff then well you got 3 options

1 stick with normal 2003

2 wait untill somebody makes it easier

3 read it and read it untill you understand and then perform it

as far as i know then there really is no easier way of upgrading it

about country ID then it have nothing to do with where it was made

since devices sold on the southpole would not likely be made there aswell ;)

the country id try doing a search for country id since sooooo many people ask about it i would be surprised if it's location was not reviealed in some of the answers to their questions
[Upgrading, Modifying and Unlocking] zairyaab:
Following are few DETAILED STEPS FOR NEWBIES to install WINDOWS MOBILE 2003 SECOND EDITION.

1. Download Windows Mobile 2003 Second Edition (DCS)

Run the .exe file and you are done and upgraded to wm2003se with builtin Radio Version 1.14.00

Download Windows Mobile 2003 Second Edition (Mysterman's Edition)

Run the .exe file and the upgrade process starts, sit back and wait till you get the "Congratulations" Screen.

(NOTE : Mysterman's wm2003se has its own radio file which is v1.14.00)

Some of you would like to upgrade to Windows Mobile 2003 Second Edition (Mysterman Edition) but would like to use a Radio Version of Mamaich (v1.18.00) here are the steps :

1. Download Windows Mobile 2003 Second Edition (Mysterman Edition)

Download 1.18.00 Radio Version by Mamaich

Create a new folder on your desktop and then right click on your .exe file of wm2003se(mysterman edition) and then click on winzip and then click on extract to and then extract the file to that new folder located on desktop.

Open that folder there you will find HimaClearJumpCode,HimaGetDeviceData,HimaUpgradeUt,ms_.nbf,nk.nbf & radio_.nbf.

Delete or cut radio_.nbf from that folder to some other folder and then extract radio_.nbf from Mamaich's 1.18.00 Radio Version.

Hit refresh in that folder and then double click HimaUpgradeUt.exe and the upgrade process starts, sit back and wait till you get the "Congratulations" Screen.

You are done with the installation of wm2003se(Mysterman Edition)with Radio v1.18.00 (Mamaich Edition)
[AT&T Samsung Galaxy S 4 Original Android Developme] svs57:
use native Linux :)
[AT&T Samsung Galaxy S 4 Original Android Developme] sendust7:
L.O.L, I totally agree :D

But my past experience is that most users prefer Windows :)
[AT&T Samsung Galaxy S 4 Original Android Developme] Dean1650:
I am not sure, but I don't think this will work on a fresh install of Cygwin. When i installed cygwin i selected "all" for packages. The directory structure does not match your script, /bin is not under /usr but in the root of cygwin directory. Also, i checked the installed packages, many are missing, and when i search cygwin.com for the missing, i cant find quite a few. Im new to cygwin, as in this op, but not new to software. i tried several boot.img (4.3) thinking it might be the image, but it was a strech and all failed the same. I dont find the .dll your script is looking for, so the error is correct.

I get this error:

$ sh modify-boot-sgs4.sh boot.img

Unpack/Repack SGS4 ROM Boot Image

Initial Release (14 Jul 2013)

sendust7 @ xda developers

Current directory: /home/modify-boot-sg4

Unpacking boot image...

/usr/bin/perl.exe: error while loading shared libraries: cygssp-0.dll: cannot open shared object file: No such file or directory

UPDATE: well I went through the cygwin install/update again and after searching for each package you listed, installing everything associated with each package, your scripts WORK. I have unpacked/edited/repacked and loaded. ADB as root......profit

Thanks for this
[AT&T Samsung Galaxy S 4 Original Android Developme] Ms. K:
Thanks

Hi,

When I understand more I can't wait to revisit this instruction. But I love that it's here for me.

Ms. K:angel:
[AT&T Samsung Galaxy S 4 Original Android Developme] Keithgordon:
nevermind

nevermind
[AT&T Samsung Galaxy S 4 Original Android Developme] ocaldini:
hello

Hi! I'm trying...but my ramdisk folder remains empty!

dump:

$ sh modify-boot-sgs4.sh boot.img

Unpack/Repack SGS4 ROM Boot Image

Initial Release (14 Jul 2013)

sendust7 @ xda developers

Current directory: /cygdrive/c/cygwin64/home/modify-boot-sgs4

Unpacking boot image...

Page size: 2048 (0x00000800)

Kernel size: 7157864 (0x006d3868)

Ramdisk size: 1142288 (0x00116e10)

Second size: 0 (0x00000000)

Board name:

Command line: console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3

Writing boot.img-kernel ... complete.

Writing boot.img-ramdisk.gz ... complete.

Unzipping: boot.img-ramdisk.gz to boot.img-ramdisk

modify-boot-sgs4.sh: line 23: cpio: command not found

_____________________________________________________

I'm doing this on 4.3 MJ7 I9505 kernel.

I assume I can unzip myself boot.img-ramdisk.gz, right?
[AT&T Samsung Galaxy S 4 Original Android Developme] lijojohnson:
Make sure you install the cpio packages for cygwin.

You can install additional packages by running the setup/install again.

You can also search for cpio via the search bar at the top left when presented with the list of packages.

Hope that helps.
[AT&T Samsung Galaxy S 4 Original Android Developme] Keithgordon:
Hello

Can anyone tell what is wrong? it keeps saying its doing it, but it does nothing...

Home@Home-PC ~

$ cd modify-boot-sgs4

Home@Home-PC ~/modify-boot-sgs4

$ pwd

/home/Home/modify-boot-sgs4

Home@Home-PC ~/modify-boot-sgs4

$ sh modify-boot-sgs4.sh boot.img

Unpack/Repack SGS4 ROM Boot Image

Initial Release (14 Jul 2013)

sendust7 @ xda developers

Current directory: /home/Home/modify-boot-sgs4

Unpacking boot image...

Page size: 2048 (0x00000800)

Kernel size: 7195952 (0x006dcd30)

Ramdisk size: 1144962 (0x00117882)

Second size: 0 (0x00000000)

Board name:

Command line: console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3

Writing boot.img-kernel ... complete.

Writing boot.img-ramdisk.gz ... complete.

Directory: boot.img-ramdisk already exists

Press ENTER to repack boot image or CNTL-C to exit (and modify ramdisk offline):

Repacking boot image...

find . | cpio -o -H newc | gzip > /home/Home/modify-boot-sgs4/ramdisk-repack.cpio.gz

4560 blocks

./mkbootimg.exe --cmdline 'androidboot.hardware=qcom user_debug=31 zcache' --base 0x80200000 --kernel boot.img-kernel --ramdisk ramdisk-repack.cpio.gz -o boot-repack.img

sh: ./mkbootimg.exe: Permission denied

Althoug, now it is telling me Permission Denied, I don't know why, or how to change that in windows 7, but it wasn't giving me any errors before, it just wasn't writing the image
[AT&T Samsung Galaxy S 4 Original Android Developme] ocaldini:
Thank you, you helped me a lot! It worked!

Oh, when I searched for cpio I had to click on "default" ( and select "install" on the windows before clicking "advance"), to install it properly!

A VERY IMPORTANT INFORMATION:

I was trying with Cygwin 64 bit and I had problem repacking it.

I found out mkbootimg only works on Linux 32 bits.

So it is necessary to use Cygwin 32 bit version!

Finally it worked! Thanks a lot!

---------- Post added at 04:09 AM ---------- Previous post was at 03:18 AM ----------
[AT&T Samsung Galaxy S 4 Original Android Developme] Keithgordon:
Yeah, I did that...same result...the problem is with permissions, when I run it in compatibility mode, it tells me permission denied. I'm suspecting

it is a Windows 7 problem, mkbootimg.exe is saying permission denied. I appreciate the answer though. maybe an antivirus program is blocking it or something. my cygwin icon is showing the security essentials icon on it for some reason...i dunno, i'll research it some more and figure it out when I have time, thanks again
[AT&T Samsung Galaxy S 4 Original Android Developme] ocaldini:
I'm doing this on windows 8.1 64bit with cygwin 32 bits. It works. I don't use antivirus, turn off security essentials and other system protecting programs, I'm sure you will do it.
[AT&T Samsung Galaxy S 4 Original Android Developme] mom4ence:
Try it with boot.img from I9505 International , unpack and repack without problem , flash it and phone restart and vibrate constantly.

Any ideas how to fix this problem ?
[Galaxy S II Q&A, Help & Troubleshooting] krypnix:
hi..

my device is Samsung Galaxy S2 GT-I9100G.

i need help with installing the neat4.8 EOM..it seems after flash the ROM, i'm stuck forever in the first boot and unable to enter CWM

already flash may times but the problem still occur..

can somebody help me? i'm really appreciate that...

currently before flashing the neat4.8 ROM, i'm running on the JB stock ROM which is I9100GXXLSR

thanks...
[Galaxy S II Q&A, Help & Troubleshooting] Sun90:
From where did u dwnld the Neat 4.8? can u give me the link :)
[Galaxy S II Q&A, Help & Troubleshooting] krypnix:
I download the Neat ROM 4.8 in this thread

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

and the link is

http://www.androidfilehost.com/?fid=22979706399755717
[Galaxy S II Q&A, Help & Troubleshooting] Sun90:
1) After Dwnld'ng the rom did u check that file size is correct and the 'Md5' is matching.

2)Did u format the 'Preload' before flashing.

3)Was ur phone rooted and a wrk'ng CWM installed before .
[Galaxy S II Q&A, Help & Troubleshooting] krypnix:
how to do the 'Md5' matching for step no.1? i think i already download the completely actual file size.

sorry for noob on step 1

for step no.2 i already done that with full wipe...

for step no.3, my phone is already root and installed with CWM6
[Galaxy S II Q&A, Help & Troubleshooting] Sun90:
if u cannot enter Recovery mode for now, u cant do much but flash a Stock Firmware meant for ur device (I9100G) from PC 'ODIN' and start all over again :)
[Galaxy S II Q&A, Help & Troubleshooting] krypnix:
i already done that step revert back to stock ROM and install it again many times..but it seems failed, i guess i will try it again...

thanks for the help..:)
[Galaxy S II Q&A, Help & Troubleshooting] krypnix:
Now i found the solution for this case..

1.recovery

2.wipe data/factory reset

3.wipe cache

4.advanced/wipe dalvik cache

5.mounts and storage

6.format system

7.format data

8.format cache

9.format preload

10.install rom

11.wipe data/factory reset

12.wipe cache

13.advanced.wipe dalvik cache

14.reboot system

after doing the above step , i can install the Neat ROM perfectly.:)
[Galaxy S II Q&A, Help & Troubleshooting] andrewwright:
Skip 3,7,8,11 no need but the rest is standard
[Ouya General] TopherBarnett:
There's no hardware keys to press on the OUYA to get it to boot into fastboot/recovery mode. They seem to think it is a tiny minority that they shouldn't have to care about, but I don't especially feel like bricking my device. I figured I'd try to drum up a little more support on XDA.

Make your voice heard here: http://forums.ouya.tv/discussion/1380/recovery-mode/p1
[Ouya General] TadeoNYC:
http://xdaforums.com/showthread.php?t=2326377

Let OUYA know we want custom ROMs supported
[Ouya General] Simonius007:
+1
[Ouya General] player911:
You just use a USB keyboard for the hardware keys.

Or download a Reboot into recovery app.

I'm not sure how Ouya could resolve this unless you are requesting a feature set on the next wave of hardware.

As far as I know there are already several custom ROMs and recovery solutions?
[Ouya General] TopherBarnett:
Thanks for the links. Didn't realize that thread was about the same thing because the title was a bit misleading.

From what I understand, the USB keyboard can only be used to crash the startup into recovery using the sysreq key trick, but if it can't get past the init.d file, you're stuck in NVflash mode without the Secure Boot Key, essentially bricking your device. So now our only real hope is that OUYA changes their mind and gives us the SBK, or some sympathetic dev from their camp leaks them.
[Ouya General] player911:
Ahhh. I didn't know it basically crashes your system.

Oddly the Ouya is the only device I don't want to hack. I don't see anything advantageous about flashing anything.

I'd be curious to know what Ouya says. They're box is hackable but I'm not sure if they would like people flashing to other ROMs that doesn't use their market.
[Ouya General] ooBONGoo:
you guys do know that some apps like quickboot (https://play.google.com/store/apps/details?id=com.siriusapplications.quickboot&hl=en) can boot your Ouya into recovery mode? What I would like to see is getting the SBK like TopherBarnett suggested so that at least we can all be guaranteed our Ouya won't get bricked permanently because the android community is innately tinkerers when it comes to android softmods and customization.
[Ouya General] bornagainpenguin:
How about bugfixes? How about a way to continue using the device three years down as a media player even after OUYA 2017 is out and the first revision of the console is increasingly abandoned? How about a way to back up your games and saves? Maybe even just a Link2SD type solution for the increasingly meager seeming 8GB internal storage?

Look, I'm in the same boat as you--the OUYA is the first Android device that I've owned where I haven't really felt a burning need to root and install a custom rom on it as soon as I could. Most of my Android devices haven't lasted a week before I had them rooted, using a custom recovery and a custom rom without the OEM crapware infested sludge slowing me down. The OUYA is the only one where I've actually used the defaults and said to myself, "Yeah, I could learn to really like this..."

Only there are some outstanding bugs that simply don't seem to be a priority and aren't getting fixed. The OUYA team has demonstrated an unwillingness to openness and an inability to communicate to its users. In the past whenever I had these types of issues, it was the community which solved most of my issues, long after the manufacturer had moved on to seek new dollars. The only reason I bought the OUYA was because of the promised openness of the console and the ability to use it with custom firmwares.

So, despite being mostly happy with my purchase I still want the promised openness that I bought the OUYA for in the first place, even if I do like the current looks of the software and want to stay as stock as possible. Otherwise there will be many who like myself will simply not bother with the next iteration of the console and no one will need to worry about what the 2017 edition OUYA looks like because there won't be one.

--bornagainpenguin
[Ouya General] player911:
I agree but I feel this article is being a little too harsh. Ouya people aren't stupid. They know whats up with the hardcore guys like us. It's not even been out a month (July 4th or something). I'm sure they are balls to the wall with getting devs on board and bug fixes and just making the thing run properly for the 95% of people who use it the way it was intended.

Once they get their crap together and things start to begin flowing naturally and they find a little free time, they might think up something.

Has anyone tried Rom Manager or anything? There has to be some way to Reboot into Recovery other then a hardware solution.

But I just don't get it. There IS a way to hack this thing... but people are complaining that it's a little dicey. Try hacking a Xbox by taking the whole thing apart and flashing a firmware to the disc drive which requires a special PC adapter. BrickCentral if something were to go wrong. Killing your device is a taken risk when you do anything done here.

I really can't see Ouya doing anything about this. If they go out of their way to make it easy to run stock android, then it might turn Ouya devs off. Perhaps once the unit is EOL, they'll provide a final rom with some extra recovery options.
[Ouya General] Oscar_david:
There are a number of ways to boot into recovery: adb, third party apps like Quick Boot, terminal emulators. But there is currently no way to do it through hardware.

Essentially, we're missing the equivalent of "volume up+power" most of us are familiar with from rooting other devices. This makes soft bricks pretty much the same as hard bricks. And that's the problem.
[Ouya General] IncognitoMan:
Like Oscar_david pointed out... these are all software solutions to a hardware problem....

IF, for example, you flash an improper kernel or something goes haywire enough to cause it not to boot far enough in to atleast enable adb... you have a softbrick that can NOT be fixed by any software solution.

Sadly the real solution is one we probably will never get... and that's via unlocked bootloader or the keys so we can flash from bootrom recovery
[Ouya General] Shiftone:
It's mad that the OUYA guys omitted a hardware key from their design - I can't think of any other Android arm SoC based mini computer that doesn't have a pin hole button to enter recovery. All the mini stick computers like the mk802 and Google TV boxes like Pivos have this feature...
[Ouya General] bornagainpenguin:
That's the thing--I could have bought a Pivos, but didn't because I wanted to have the best of both worlds and play games as well as videos. I thought the OUYA would offer that to me, but the longer it takes to fix things the less hopeful I become. :(