yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] legola:
Downloading it right now. Is it right that the file is only about 140MB?
[Galaxy S II Android Development] okoska2:
Yes, 146*890*606 bytes
[Galaxy S II Android Development] okoska2:
Question

Opinions?
[Galaxy S II Android Development] Nasty_z:
Look man, I understand this is your first ROM. Now, as you already know, we have CM9, the only changes you made are de-bloating the rom. But, we can all already do that using Titanium Backup, I'd say you gotta add something to this ROM to attract users. Don't get me wrong, you've done a great job. I mean, I can't even do what you did. But all the same, these people won't try out the ROM unless they find something new or better in it.

Looking forward to something better from you. I know you got the potential. :)

If it was a suggestion you wanted, if you make a CM10 ROM, I'll definitely try it!

Cheers. ;)
[Galaxy S II Android Development] okoska2:
I mean, thank you have written. I was thinking is I think the only cm10 development is still very immature and 1-2 months you will have a usable condition.
[Galaxy S II Android Development] okoska2:
V2 update

V2 update available!
[HTC Sensation] jazzzzzzz:
A stupid question actually... But i need it.. :) :)

I like to play music while calling.... As a background music actually and the receiver should also hear it..

Any way???
[Samsung Infuse 4G] Kevinr678:
Just making a topic seeing how everyone's doing in the infuse forums. As you can tell in my Sig I jumped over yo the SIII seeing as I had an available upgrade. Still have my infuse though as backup :D But I mainly just wanted to see how it is over here.
[Samsung Infuse 4G] theROMinator:
Me too :D
[Samsung Infuse 4G] andros11:
As you may have already seen, Jelly Beans are now on the menu! Just missing a bit of butter :p

Sent from my sweet and buttery Infuse
[Samsung Infuse 4G] Truckerglenn:
Better then ever. New Roms, New Ports, ICS w/BT and JB.
[Samsung Infuse 4G] pacallen:
Still loving mine! My infuse was my first real smartphone (previously had a Noxia 5800 which sort of counts I guess, but first Android anyway)... I love that its so easy to play with and nearly impossible to brick (though flashing a new bootloader through heimdall and have it fail halfway through did make me pucker a bit!). The JB roms are quite stable and definitely breathe some new life into this (not even that old) phone.
[Huawei Ideos X6] chrillefr:
Jump over and read, please.

http://xdaforums.com/showthread.php?p=27147931
[Asus Transformer TF700] gck1973:
I am running into an issue where I picked up the $99 Best Buy Special, and it is not working.

The device connects, and shows it is connected, but does not work. Here are the symptoms...

- No keys work on keyboard.

- Touch Screen does not work

- Touch Pad does not work

- Does not display dock version

- Shows dock icon in task bar

- Batteries on both devices show no status and 0%

I have reset the device, ensured i have the .22 update, and connected before power up.

Please see screen shots attached.

Any thoughts? Old Firmware?

Thanks for the help on this.

G
[Asus Transformer TF700] wolfman87:
Try charging it first.
[HTC Wildfire S] akshatsourav:
help guyz :(

i just unlocked bootloader from htcdev..

now i m rooted by super one click !!

I tried to load recovery via “fastboot flash recovery recovery.img”

The process went ok, however I am not able to start recovery. After choosing recovery, HTC logo just appears forever....

tried using rom manager but no luck :(

any help ??
[HTC Wildfire S] akshatsourav:
no one here to help ??
[HTC Wildfire S] HannaBlu:
Have you tried to pull out the SD card, restart in recovery (vol down + power) ?

I just fried my phone a few days ago and had the same issue, all i had to do is to pull the SD card.... lemme know if it works ;)
[HTC Wildfire S] akshatsourav:
no luck....

ny way thanx :(
[HTC Wildfire S] dady000:
What version of recovery has you flashed? Can you go to HBOOT? If yes run fastboot and flash new another recovery.

BTW: Wait?

load? that command from adb flash new recovery!
[HTC Wildfire S] akshatsourav:
flashed alredy all the reciveries here....

no luck :(

only having htc logo above white screen !!
[HTC Wildfire S] dady000:
OK can you tell me what exactly did you with phone? All reinstalling etc. OK i think you can go to HBOOT. :D So install lastest CWM recovery 5.0.2.8 THERE. And you starting recovery throught - reinsert battery, volume down+ power on -> bootloader > recovery. Right?
[HTC Wildfire S] gdjindal:
help friends i am also facing exactly same problem

i also tired every thing i have found in XDA related to this problem but nothing works please somebody help us

& could somebody tell me that how i can unroot my WFS so that i can update my stock rom

please help
[HTC Wildfire S] mindfreak62:
Badluck :'(

The solution of your question is HTC made some kindda hardware change in WFS shipped i guess after May 2012 due to that change you cant see CWM but your 4 keys might be lightning if you installed the latest CWM but you cant enter

Your recovery mode :mad: INCASE you find a solution please please do.let.me know :)
[HTC Wildfire S] WoefulDerelict:
An answer... sorta.

As mindfreak62 stated this is indeed an issue rooted in some unpublished hardware revision to the WFS. There are a handful of users with the issue and it is presently under investigation here. There is currently no solution that will allow you to run a custom recovery and many ROMs have the same issue. Your best bet presently is to stick with stock firmware until the issue is resolved. You can get back to this state by flashing your device with an RUU.
[HTC Wildfire S] akshatsourav:
yup im with stock :(
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] purple zebra:
Hi all, I could really really use some help.

Today I decided to try and flash CM9 RC2 and I seem to have messed up big time.

I startred by rooting, using Dr Ketan's guide. That all went smoothly, and root was working.

I put the CM9 zip file on the SD card, turned off my phone, got back into CWM recovery, and most tutorials recommended, selected full data wipe... this is where something seemed to go wrong. While perfoming the data wipe, it seemed to freeze. I let it sit for a while, hoping it would sort itself out, but it didn't, and then it rebooted itself and went into a boot loop.

I can't get back into recovery mode, but I can get into download mode. So I thought the best thing to do would be to flash a stock firmware using odin.

I downloaded the latest german LRG firmware (which I was on before I started) from Sammobile, connected my phone to odin, selected the MD5 file, and pushed start. Again, this is where I got stuck. It just hangs on Nand write start. I've tried this twice now, and it gets stuck at the same stage (about 90% finished)

I have no idea what to do now and really need help. I'm not a total n00b, or at least I thought I wasn't, but I seem to have gotten in way over my head. What should I do?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] CJSlim79:
Edit: see you tried already...
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] dr.ketan:
This is classical case of super brick.

You should not hav to wipe on ics. I think u must be on stock kernel. Every corner you may see warning, wiping and reset on ics can brick device, but its unfortunate you didn't notice it.

Anyway check your flash counter is zero and send it to service.centre to claim ur warranty.

If u running out of warranty, fing.a link for 'how to revice bricked note from my signature. And try it.

Edit : i wud like to know, as you said u went to cwm recovery, so at the time of wiping you wr on which kernel?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] letters_to_cleo:
Hi Bud,

From your predicament, first let me tell you what you have done wrong.... You mentioned you're in LRG Rom already and you wanted to flash CM9 after that.... right?

Well, I guess the process you did was totally wrong. You have to download stock GB N7000(from Dr. Ketan's thread) and using that stock GB Rom, that is the time you can install AbysNote kernel to root and install CWM on your phone. Now after that, download mobile ODIN (from google playstore) and flash the CM9 from there.

THAT's the one you should have done before. Remember, there are no easy way of jumping ROMS especially if your already in ICS... IF YOU WANT TO FLASH TO ANOTHER ICS ROM.

My rule of law would be to downgrade first to STOCK GB and from there, ROOT, install CWM and mobile ODIN and that'll be the time you can flash already to the new ICS ROM of your choice.

So here's what your going to do. Since your still able to boot in download mode, Download any stock GB ROM and flash it using PC ODIN. After that, seee if you can bootup your Note already to STOCK GB ROM. If and If you are able to already, then download a clean kernel preferably Abyss Kernel and flash it with your STOCK GB so that you can gain root and have CWM installed. From there, download Mobile Odin pro and flash the CM9 (that you ultimately want to be installed on your Note)

Hope everything's going to be fine and Good luck bud! :fingers-crossed:

Cheers! ;)
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] purple zebra:
Hello, I know its been several days, but I just wanted to update on the situation.

Thank you SO much to Dr.Ketan for pointing me in the right direction. A combination of these 2 guides (http://xdaforums.com/showthread.php?t=1661590&page=2 http://xdaforums.com/showthread.php?t=1667886) has managed to help me repartition my internal memory and get up and running again. I've got a stock gingerbread rom running, and all seems to be well.

I realise I was very stupid to do a wipe on an ICS kernal. I read about the problem for 1 particular Kernal back in may, and hadn't read the updates since, and so didn't realise it effected EVERY ICS kernal since then. It's my own stupid fault for not re-reading the warnings. Let this be a lesson kiddies, a little bit of knowledge is a dangerous thing.

Again, thank you so much for the help, to all involved, you are an asset to the community!
[HTC One X] chester-2k11:
hi all i have been flashing my htc one x for a bit now and i wanted try miui boot i needed to follow this

Here is a boot.img flasher, for easier flashing boot.img !!!

Instructions

1-Boot to Bootloader

2-Make sure your One X displays "fastboot usb" at the header of the fastboot screen

3-Extract the boot.img flasher zip you downloaded anywhere on your PC & run the script relating to your OS (windows, linux or mac)

4-Press the power button once, click volume down, highlight recovery & press power (This will take you to recovery)

5-Flash the downloaded ROM via recovery normally

6-Reboot

7-Enjoy!!!

i have done this but didn't have the rom on the phone and now i cant get it to boot have tried to restore with my back up stock rom no luck have tried to flash another custom rom i had still the same phone just keeps rebooting ..

help lol
[HTC One X] ckpv5:
The main thing here is flashing boot.img that belongs to the ROM that you are flashing.

When you flash the custom rom that you have, you need to flash its boot.img.

Why don't you mount usb storage in recovery and put in the MIUI rom.zip that you want to flash ?
[HTC One X] chester-2k11:
hi thanks done it now
[Nexus 7 Q&A, Help & Troubleshooting] M@cross:
Can anyone confirm if there is a quick way to add the stock ICS browser back onto the nexus 7 without having to root? Thx
[Nexus 7 Q&A, Help & Troubleshooting] AaronDC19:
Cool story bro. Tell it again. :good:

Seriosuly...what is this?
[Nexus 7 Q&A, Help & Troubleshooting] SoHaunted:
Yeah, put the apk on your sd and install it.

Derp.
[Nexus 7 Q&A, Help & Troubleshooting] M@cross:
I downloaded the browser.apk and have tried just double tapping it to install but it won't let me.
[Nexus 7 Q&A, Help & Troubleshooting] SoHaunted:
Go into developer options or apps in settings and make sure to check "install unknown apps"
[Nexus 7 Q&A, Help & Troubleshooting] brianjr1:
Erm

You can just check install apps from unknown sources in the security part of your settings. On a side note, please watch this video...
[Nexus 7 Q&A, Help & Troubleshooting] M@cross:
Thanks for the link to the video:thumbup:

After searching it looks like nobody has successfully installed the stock ICS browser on the n7 without having to root the device.

I'll just start getting used to chrome then
[T-Mobile, Samsung Galaxy SIII] jknakes:
is it possible to add more languages to the stock samsung keyboard? i would like to add czech, but it's not one of the current options. i've switched to gokeyboard, but like the stock one more. i'm not rooted (waiting for the imei problems to be sorted out).
[T-Mobile, Samsung Galaxy SIII] androholic:
I highly recommend you try switkey keyboard. I'd heard so many great reviews on it, but i just stuck with what I was using because it worked well, but now that I've tried it I'm BLOWN AWAY by awesome it is! They have so many language packs, and if you try it, I bet you'll love it. I highly recommend it, there is so much more functionality, they've given me features I didn't even know I needed. Best of luck!
[Sprint HTC EVO 4G LTE] 00dahc:
Can you please try the following on your stock phone:

1. Turn on the flash, tap to focus on something and take a picture.

2. Turn off flash, try to tap to focus on something.

Will it focus for you?

If I take a picture with flash and then turn it off and try to focus on something, it will not focus.
[Sprint HTC EVO 4G LTE] BrianBaker:
Tapping won't focus like you described but it still auto focuses on its own for me.
[Sprint HTC EVO 4G LTE] 00dahc:
Ah ha, so this isn't just me and my buddies phones doing this.

Interesting.

Thanks for confirming the issue.
[Sprint HTC EVO 4G LTE] cruise350:
Worked perfectly on mine. Tap focus worked with flash on and off just like you asked. I am currently running MeanRom 2.1.
[Sprint HTC EVO 4G LTE] 00dahc:
Whoops, I shouild have mentioned. "if your phone is stock" :D

Thanks man.
[Motorola Droid Bionic] majeiks:
I have been able to flash the CM9 ROM over the ICS leak using Safestrap 2.0. Unfortunately, I'm doing a wipe each time and losing my data.

Is there a way, perhaps using Titanium Backup, to flash a new nightly build of CM9 while keeping all my apps, settings, etc?

Getting the CM9 nightly builds from Droid Hive (see http://xdaforums.com/showpost.php?p=27849500&postcount=1)
[Galaxy Note GT-N7000 General] satishp:
Today,I was playing around with my Note, still worried about the black clipping and blocky videos changing ROM after ROM and didnt find any solution.

Out of curiosiry, I copied the GammaTest image to my PC, went to my display adapter settings, and cranked up the gamma from 1.0(default) to 1.5-1.9 and guess what?

http://imageupload.org/en/file/235342/gamma-normal.jpg.html

The first image shows the gammatest as it should. Here the computer's default gamma is set to 1

I increased my gamma value to 1.5-1.9 and this is the result.

http://www.imageupload.org/en/file/235344/gammahigh.jpg.html

And when setting the gamma to highier values, play all your test videos and images, there will be clipping and blocky pixellation just like you see on the Note. Try this for yourself on your PC.

This clearly shows that the clipping on the note is a software issue rather than a hardware defect and if we could somehow get to tune the gamma on the note, its the END of all the clipping and the horrible video playback.

A point to note is, when increasing gamma values, the images tend to become artificially bright and on reducing them, they tend to get darker. Maybe this explains why the Note produces the best whites as far as AMOLED displays are concerned and seems to be brighter than all the other Galaxy devices which includes, the Galaxy S, S2 and S3.

So the only and truly effective solution is to find a way to tune gamma values under the MDNIE settings and this should be implemented in a kernel. I've seen none so far which is capable of doing this. All CM9 based ROMS have Gamma control disabled under MDNIE settings. This also explains why the same problems were corrected on the Google Nexus with the LEAN Kernel.

This is definitely a GAMMA issue and definitely Software related.

I may be wrong, please do feel free to correct me if so.
[Galaxy Note GT-N7000 General] pboesboes:
Although I do agree (in my non-expert and in this regard completely worthless opinion) it is probably a software issue, this does not confirm whether our Notes' black crush is caused by software or hardware, or if it is fixable. This only means that you can make your display crappy by cranking up the gamma too high. The same result can be achieved in different ways.
[Galaxy Note GT-N7000 General] Rivan_92:
I still dont understand the gamma test picture.. Which numbers should be seen? I see 4 to 21 perfectly and can barely see 3.. Should 2 and 3 be seen too?

Sry if I went off topic.. :)
[Galaxy Note GT-N7000 General] satishp:
First of all, the image should be quite dark to see in a lit environment and on an ideally calibrated display, the image show a gradual fade to black. So theoritically speaking, on a good display, the left side is barely visible and is seen as a dark gray fading to black.

On the stock ICS kernels, the image is seen upto 4 and then clips to black. If you enable, Force GPU acceleration, you can see upto 1 which means more clipping. On stock GB, you can see all the way to 1. It varies from kernel to kernel.
[Galaxy Note GT-N7000 General] satishp:
We just need some way to access the gamma control under MDNIE settings on the Note which is at present, disabled on the CM9 kernel and is not present on any other kernels either.
[Galaxy Note GT-N7000 General] panyan:
When you wrote "CONFIRMED" i thought there was some quote from Samsung saying it was a software issue and they were looking into it :(
[Galaxy Note GT-N7000 General] satishp:
I had mailed GSMArena regarding this issue and even after they published it and many other blogs too, Samsung didnt give a damn about it. So I dont think they do now either. The EMMC Bug is more of a fatal issue and to date, even after announcing that they are "working" on a fix, there are none. People are literally bricking from the latest stock when all the other custom kernels have disabled the MMC_CAP_ERASE value from their kernels. So its better not to rely on Samsung for anything. They just sell their phones and thats it. The Note and everything alike are experimental phones and we are their lab rats. They basically only focus on the flagship Galaxy Phone. read GS3 and new ways to sell it.
[Galaxy Note GT-N7000 General] Entropy512:
Yeah because we have a unique display that is different from the I9100/I777 - so display tweaks for those won't work on N7000.
[Galaxy Note GT-N7000 General] gbb14:
problem

1) Seriously guys, we have to get to the root of this problem. If we can get to the gamma setting on this display we can solve the problem. But how hard can it be to get there?

2) On the other hand, i think that what you did, was change the gamma on an LCD display. As far as I know there are a lot of diferences between LCD and OLED, appart from the fact that we have a pentile display (2 subpixels per pixel, pixels are in RGBG formation) and the LCD uses 3 subpixels per pixel (RGB).

We should join our forces and start on a mission to solve this issue once and for all.

Regards.
[Galaxy Note GT-N7000 General] shatroghistro:
It is DEFINITELY a software issue. Try this out: reboot your phone, and while it is still booting and slowish, quickly start the calculator and see the top of the screen perfect and then, for no apparent reason, it gets some kind of a half-circle color spill. Also, when you open the gallery, find a folder with a stock video clip with jelly fish, and when you open that folder, gallery turns to black, and for a half of second it is perfect and then gets sort of color rendering problem. Final test is to start the camera when the night falls, switch to camcorder (for the smoothness), and just look at the screen, it is perfect, no black clipping, and then, as soon as you take the picture, the picture spoils and you get the black clipping- the live image on the screen while observing is totally normal. So, it is 100% SW issue!

I compared my Note to my friend's SIII and the screen is much darker on S3, and images themselves. So, it IS gamma issue. When you open the front camera on the SIII, in a bit darker environment, and look at yourself, you barely see the shape of your head, since gamma is much lower and it only picks up the bright parts, such as your forehead and cheeks. Also, images appear much MUCH darker on the s3 screen than what you see in reality. That is what samsung did to solve the issue: lowered the gamma.

Hope I gave some useful info (no pressure to hit the thanks button :D)

Cheers

P.S. please, those of you with good screens, post images here of your good note

http://xdaforums.com/showthread.php?t=1801333
[Galaxy Note GT-N7000 General] gbb14:
ok, it is software. good. let's solve it !
[Galaxy Note GT-N7000 General] shatroghistro:
It is not that easy..supercurio worked on it for 6 months and then left us hanging... He is not obliged, though..
[Galaxy Note GT-N7000 General] satishp:
We need a kernel which can access the gamma control. That is the only 'real' solution for this issue. You are right about the s3 having lower gamma and hence darker images. I've seen this myself and thats why I mentioned on my post that the Note's screen looks brighter due to the heavily cranked up gamma.

Apparently, this might be an issue with pentile amoled. Lower the gamma and lose pure whites for a clipping free darker image like on the Galaxy S or S3 or crank it up and get "richer" looking colours and whiter whites at the cost of extreme clipping in darker shadows.

This is the root of the cause. Improper gamma. Now only if someone who is experienced in developing Kernels would somehow enable gamma control which is present in the MDNIE settings but strangely disabled due to unknown reasons.

I saw that Liquid Black ROM has Gamma Control but didnt try that ROM yet. I really love the Tablet Mode in the Paranoid ROMS. So I want to stick to it while getting a solution.
[Galaxy Note GT-N7000 General] baz77:
I tend to agree with satish, it is then a hardware issue that could be remedied partly at cost other colours. I guess I was wrong, I use to think it was only caused by lower quality images, like watching tv on old crt, then watching same on hdtv, that also looks crap lol.
[Galaxy Note GT-N7000 General] satishp:
I wasn't comparing LCD and OLED. I just wanted to prove the point that it is indeed gamma which is set higher on the Note and it is not a hardware issue. I dont know why no kernel for the Note is able to access the gamma control settings. Maybe like Entropy said, the Note's display panel might be a unique design such that any tweak applied on the display may cause unwanted results. As you all know OLEDs have certain hidden characteristics and its more or less like DNA. Every OLED panel is different. So the manufacturer tunes it into the most optimum settings possible on the particular technology used in the panel. But here, Samsung just did it wrong.

If you have noticed, many custom ROMS offer scaling down the brightness even below the default Samsung values and thats when AMOLED's hidden weaknesses start showing up.

In the end, I feel the only solution to this is a Kernel which enables the Gamma Control or somehow enabling the Gamma Control in CM9 which is currently disabled in most CM9 based ROMS.