yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy SL i9003] sgsI9003:
Ok I will try the two methods & see if the speed can be faster, if no speed gain then I stick to myphoneexplorer only as it has everything minus the user interface of airdroid.

BTW I have the router right beside me 3 feet away.
[HTC EVO 3D] notfuzzi:
I have had this problem before but not to this extent. A lot of my text messages aren't being received on the other end. I'm on Warm Rom and I have tried reflashing the rom, kernel, updating prl and profile. When I called Sprint about this issue before they just had me flash to stock and then gave me the runaround until the issue seemed to just resolve itself.

Has anyone else had this issue? Anything else I can try? Is there a way to install a different PRL? I can't flash the new radio because I'm on hboot 1.5. Or should I flash back to stock and take the update for now?
[HTC EVO 3D] cobraboy85:
ummm... why don't you try flashing a different ROM bud. but even still there are no details in your post. warm ROM? cool story. so is that sense 3.0 or 3.5? what kernel?

flash a different ROM. if that fixes the issue, well good for you. if it doesn't, then take your phone into sprint because it has defective pArts.

also, can you make phone calls and browse the internet?
[HTC EVO 3D] pwrmedia:
Yep, just went through this from 1/14-1/18. Not your ROM, not your phone, it's a Sprint issue. Only things you need to do on your end is wipe the cache in your messaging app, and double check via Google Voice (if you have it synced w/ your Sprint #) to see which messages are (or aren't) going through. The network will eventually purge whatever is backlogged hours or days later to the respective recipients, probably in the early morning hours, and you'll be accused of duplicate texts. Yay Sprint. :rolleyes:
[HTC EVO 3D] notfuzzi:
Yeah other people started telling me of issues with texting as well. I went back to stock and flashed all the updates. I guess I'll go back and unlock it and reinstall my custom Rom. Thanks for the replies guys.
[HTC EVO 3D] EniGmA1987:
I have problems like this and SMS radio errors on Sense ROMs all the time, especially at night. I never have a problem on MIUI though so maybe you should give that a try
[HTC EVO 3D] notfuzzi:
I have thought about MIUI and other AOSP roms several times, but every once in a while I do want to watch something in 3d. If they could get 3d fixed, I would probably give it an honest go.
[HTC EVO 3D] EniGmA1987:
Doubt that will ever happen :/
[HTC EVO 3D] notfuzzi:
Yeah I kind of figured that.
[Galaxy S II Themes and Apps] uppon2:
Deleted Post
[Nexus S Q&A, Help & Troubleshooting] heinst:
I am looking for a crystal clear version of the ICS Bootanimation or as clear as it can get. Anyone know of a good bootanimation ICS file?
[Nexus S Q&A, Help & Troubleshooting] att1cus:
Try this out. I got it for my captivate (backup phone) and it's way nicer. I can't find the thread any longer so I put it on mediafire. Props to the original poster/maker.

http://www.mediafire.com/?3b35a0sc2sx3ys4
[Nexus S Q&A, Help & Troubleshooting] neo_x22000:
is this flash able???

sent from Ice Cream Infused NS4g
[Nexus S Q&A, Help & Troubleshooting] att1cus:
yep fo sho
[HTC Amaze 4G] cndctrdj:
I tried searching but not much came up... In WiFi calling mode if I talk on the phone for a few minutes the speakers seem to shut off for about 5 seconds then come back on. Neither I nor the person I'm on the phone with can hear or speak to eachother... Anyone have this happen?
[HTC Amaze 4G] thompsd:
I've noticed this seems to be ROM dependent, try using Xboarders latest, it works well and I have not noticed any artifacts.
[HTC Amaze 4G] cndctrdj:
Thanks, I'll see what I can find out when I root and play around a bit, I was hoping to wait for ics before I messed around too much
[Galaxy Note GT-N7000 General] legion1911:
Use this picture as a home screen wallpaper, lock screen wallpaper and look at it in the gallery. It looks different in each of those 3 places on my device.

Do not forget to touch the screen without unlocking in lock screen.

What is the lowest number you can see? 4? 1?

Do you see only black and white or also other colors on this picture?

This image is a 800 x 1280, bit depth 32, PNG.

So no scaling, no more excuses for not showing it correctly.

http://img85.imageshack.us/img85/9524/samsunggalaxynotegammat.png

:)
[Galaxy Note GT-N7000 General] EarlZ:
Immediate drop off from 1 to 0
[Galaxy Note GT-N7000 General] legion1911:
So the lowest you can see is 1? Where? In the Gallery?
[Galaxy Note GT-N7000 General] Tubgirl:
Nice pic...

I can only see down to 4 (cannot see 3,2,1) in gallery. On home and lock screen I can see down to 1.My ROM is LA4.

Why is this??
[Galaxy Note GT-N7000 General] c900712:
In gallery 0 and 1 is same not visible but when i set it as wallpaper/lockscreen 0 is black 1 is visible
[Galaxy Note GT-N7000 General] friedje:
So in how is this a screen test ?

The screen is still the same ...

You could ultimately call it a display driver test,

that shows that samsung screwed up the driver implementation
[Galaxy Note GT-N7000 General] noteworthy:
What should it ideally look like?

I can barely see 1 and 2 as too dark but I can make it out.I can start to see 3 clearly and then it gradually gets lighter to 21.

What seems not right is the big jump in brightness going from 10 to 11.
[Galaxy Note GT-N7000 General] Thugsin313:
Guys guys guys, enough with the screen issue threads! seriously, its like you are forcefully looking for issues! There are 4 notes in my house, 3 black and 1 white, 2 bought locally and 2 ordered from handtec.com, and none of them have any issues! If u find the screen so disturbing why did u buy it?

oh, ok, so u found the so called issues after purchasing the device.

Here is an advice, SELL it!

Sent from my issue less GT-N7000!
[Galaxy Note GT-N7000 General] EarlZ:
I dont think this is a screen issue thread, but a similar thread already exists which is here

Sure you dont have issues, so why care about these threads LOL!

@legion1911

In the stock gallery: I can see upto 3 and 2 is a sharp cut off, Try to hold the home button to bring out the task switcher you would see the cut off start to creep down to #8.

On the lock screen it looks horrible lol! the transition to 0 is smoother but I see random black lines when I touch the screen.
[Galaxy Note GT-N7000 General] noteworthy:
Not really sure if this test means anything.On my notebook I can't see 0 to 3 at all.I can only see from 4 onwards.What does that say about my notebook?
[Galaxy Note GT-N7000 General] ranjan.alva:
Gallery - 4

Home screen - 1

Lock screen - 1
[Galaxy Note GT-N7000 General] EarlZ:
This test is some what related to the black clipping, this is the reason why we get a sudden color clip to black.
[Galaxy Note GT-N7000 General] EdgaBimbam:
gallery 4

lock and home screens 1
[Galaxy Note GT-N7000 General] TML1504:
same here!!

another interesting thing: when you enter the pic in gallery you can sometimes (!) see for a very short time down to 1, then after i guess 1/10s it goes up to 4. this happens not every time opening the picture, it seems it is (cpu) load dependent. try it!

this perhaps suggests that it's an energy saving mechanism or any other kind of "optimization" which is the main cause of the cut-off!

although: the screen quality differs in big amounts between different units, as i mentioned in some posts before!
[Galaxy Note GT-N7000 General] edanfalls:
Guys guys guys, enough with the "moaning about what other people are interested in talking about" comments! Seriously, it's like it bothers you that people are interested in discussing things on a forum!

There's a difference between finding things "disturbing" and "interesting". If you don't find it interesting, kindly ignore the thread. Personally, I don't have any issues with my screen, yet I still find some of the issues people have been having interesting.
[Galaxy Note GT-N7000 General] voxano:
The same here. Except in the "Movie" screen mode, when the gallery image is displayed down to 3.

Perhaps somebody here is capable of cooking up additional screen modes with different settings...
[Galaxy Note GT-N7000 General] edanfalls:
Interesting test.

Gallery: can see down to 4.

Wallpaper: can see down to 1 (with 24-bit rendering)

Wallpaper: can see down to 3 (with 16-bit rendering)

Lock screen: can see down to 1

Web browser: can see down to 1

Another interesting thing this helped show me was when resizing in the browser (stock or Opera), it was using static dithering... which is just bizarre :confused:

Also, seeing down to 1 is a bit too far. I'm on a calibrated Hazro S-IPS monitor at the moment which can clearly distinguish down to #3. Shows that these Super AMOLEDs are too bright...
[Galaxy Note GT-N7000 General] frat289:
Gallery. Sometimes on 2 sometimes on 4. On homescreen 1. On lock screen i can see f...in lines!
[Galaxy Note GT-N7000 General] DaanJordaan:
Gallery - 4

Lockscreen - 1 with lots of banding

Homescreen - 1

Browser - 1

But this is just Samsungs screen calibration.

Deeper blacks in the gallery, it's not a bug it's a feature.

Like Sony's Bravia engine for example.

IMHO Samsung did a bad job.
[Galaxy Note GT-N7000 General] madbird:
here are my results of this 'test' (i only count what i see when i look straight toward the device)

Galaxy Note

gallery 2

background 4

lock screen 4

PC

Samsung 22" @1680x1050 (display1 gaming setup) 4

LG 22" @1680x1050 (display2 office setup) 2

HTC HD2 Coredroid 3.6 (Gingerbread 2.3.5)

gallery 6

background 10

lock screen not tested

Asus EEEPC 1215N

5

but what is the meaning of this 'test'?
[Galaxy Note GT-N7000 General] Xaddict:
Gallery is 16bit.
[Galaxy Note GT-N7000 General] MartijnMM:
No, at least 24bit.
[Galaxy Note GT-N7000 General] sky|ined:
Looks like you too have got some issues :D
[Galaxy Note GT-N7000 General] valtersboze:
Gallery 3

KKA fw
[Galaxy Note GT-N7000 General] co2gaz:
KLL3

Gallery 4

HomeScreen 1

LookScreen 1

:rolleyes:
[Galaxy Note GT-N7000 General] mrlo:
Gallery Stock - 4

Gallery + Voodoo Screen Tuning - 2

HomeScreen 1

LookScreen 1
[Galaxy Note GT-N7000 General] viperx0219:
i can see no. 3... 2-0 is not visible.
[Galaxy Note GT-N7000 General] Barkotron:
No, the Android gallery has been 16 bit since 2.1. Apparently someone thinks that making the pictures look like crap is an acceptable trade off for the worthless 3d effects.

The lock screen looks different because there's some kind of filter over the image.
[Galaxy Note GT-N7000 General] SpecialStar:
Galery 4

Lockscreen 1

Homescreen 1

on customRom ;)
[Galaxy Note GT-N7000 General] flipee:
Gallery - 4

Lockscreen - 1

Homescreen - 1
[Galaxy Note GT-N7000 General] ocoegna:
There is a dramatic drop in brightness below:

Lock screen: 5

Home screen: 4

Gallery: 4

It's really annoying with videos. Dark scenes get horribly pixellated.
[Samsung Epic 4G Touch] fonebone2:
Running Calkulin's 2.8.1 with Desperado kernel and Market tells me Netflix is incompatible with my device. I have the LCD resolution app installed but resetting to 240 doesn't help.
[Samsung Epic 4G Touch] brianhot1:
try this

http://xdaforums.com/showthread.php?t=1177986
[Samsung Epic 4G Touch] Ja5oN:
That is interesting, I am running the exact same setup (less the res change) and I use Netflix all the time... I bet is does have something to do with the changing of the resolution. Have you rebooted after changing back to 240?
[Samsung Epic 4G Touch] AndroidFanatic206:
Well what Android version you using also often doesn't work with 2.1 and below.
[Samsung Epic 4G Touch] fonebone2:
Figured it out: I had to

1) restore LCD resolution to 240;

2) clear data on Market.
[Samsung Epic 4G Touch] Ja5oN:
Right on man!
[Samsung Epic 4G Touch] jyaworski:
I had an issue like this when I wanted to install betterbatterystats. To do this more easily, try out "LCD Density Modder Pro" in the Market. Works like a charm!
[Asus  Eee Pad Transformer Prime] ChungWingKeung:
When will ASUS unlock our bootloader:confused::mad:
[Asus  Eee Pad Transformer Prime] Lorthirk:
Who knows...
[Asus  Eee Pad Transformer Prime] ajamils:
Instead of creating hundreds of useless threads, it would be more productive if you bug Asus about it.
[Asus  Eee Pad Transformer Prime] Lani Kai:
I read that Asus delays it by a few days every time someone posts a thread whining about it.
[Asus  Eee Pad Transformer Prime] jerdog:
Hmm - I have a feeling this has been answered and/or discussed a few times....
[HTC Excalibur] arblacksmith:
I can't beam contacts to my new auto cd receiver with my HTC S620. When I try, the bluetooth icon states searching and stays in the search mode forever. I do have the visibility set to on my auto device and I can manually make and receive calls through the auto cd receiver. Actually, I tried beaming contacts to my my wife's Motorola and it does the same thing. Any way to solve this problem?
[General Questions and Answers] disastaa:
Hi to everybody.

First : my Android skillz are rly low, so i hope you dont kill me about the following questions :)

Minutes ago i've talked to sony customer service, and that good man told me to ask on this forum because they cant help me directly.

I've bought a used Arc S with installed doomkernel.

The phone is now rly slow, are laggin, freezes and more.

Apps like angry bird are lagging too.

Thats not normal with 1.4 Ghz CPU and 512MB ram.

I think the previous owner make something wrong or anything else.

( i dont use so much other apps in the background, and reset to factory settings are unhelpful too )

So my question is :

how can i flash that phone to the normal stock rom & stock kernel ?

Can somebody tell me which tools i need to flash my phone back ?

Pls remember .. i have rly low android skillz, so would be great if you used not so hard vocabulary :)

Phone Specs:

Model: LT18i

Android version: 2.3.4

Kernel Version: 2.6.32.9-DooMKernel ( DoomLord@chaos #15)

Build number: XPERIA Mod 5.0 Arc S [4.0.2.A.0.62]

Thx a lot !!!
[LG Revolution] patsoxfan:
Well I like what everyone has done.

I am using Gingervolt, blitz 2.1 Gingerfussion 3.8 and ics tweaks

Now for some reason atleast once a day my phone will start to vibrate. The only way to stop is to pull the battery.

Has anyone run into this/

Is there a fix that I have not found while searching these forums?
[LG Revolution] elreydotcom:
Your best bet is to kill anything that involves vibrate on your phone. I used to get that every now and then, and thought it had something to do with using setcpu. When it happened after I uninstalled setcpu, turned off all vibration and haven't had that issue since.
[LG Revolution] keynith:
I had that issue until I used setcpu and put the minimum at .768. Hope that helps

Gingerfused Gingervolt 1.3 + Blitz
[LG Revolution] Grizzy3:
I believe it's an issue with blitzkreig. BK 2.1 was suppose to fix that problem but I guess it didn't for some people. This only happened to be twice then went away. Others haven't been so lucky. But I would try maybe not overclocking too much and keeping the min above 245. You can check out the Blitzkreig thread in the development section too. Other people mentioned the problem there as well.

By the way I use CPU Master. Not sure if that makes a difference.
[LG Revolution] rocknrolla818:
I have had this problem as well and it doesn't happen so often but I found that instead of having to do a battery pull you can hold the power button and it will stop mostly annoying that it does it since you can't stop it or do anything except restarting
[LG Revolution] dadecamp:
Haptic Feedback

This has happened to me as well. I thought it was because of blitzkrieg 2.0 and 2.1 but still did it after reflashing to stock kernel. I think it has to do with haptic feedback because it starts while pushing home or back buttons.

I will try setting min cpu to 765.

I have not had to pull battery, it just reboots after about +/-20 seconds.
[LG Revolution] dastaak:
My phone does the samething vibrate for a long time every 4 to 6 hrs n then reboot not sure what to do. I uninstalled setcpu n super script running blitz 2.1 n gingervolt 1.3
[LG Revolution] splat matt:
My girlfriend's Revo is vibrating non stop once or twice a day. It is running gingervolt 1.3 and that is it. She runs very few apps and I am going to go through the list to see if there are any apps causing problems. This vibrating issued existed before rooting and installing the gingervolt. I attribute the problem to reside with the code Verizon uses to activate and install bloatware. From what I can see there is some Verizon encoded bloatware that cannot be stripped out (that is not network CDMA verification code).

I can say this phone is frustrating and really wish that android phones would be released with without carrier tweaks. I switched back to an iPhone just because at the end of the day I still have battery life, no carrier bloatware, and the music integration with my car is less problematic. The thing is - it kills me to have an iPhone from geek standpoint. I applaud google for taking a stand with the carriers and revoking the developer phone status on the samsung CDMA dev phones. The carriers really need to stay out of the firmware of these phones and just apply their configs for the device to work on their network and leave it alone from there. This would yield to more frequent official updates and possibly an android device that is much more stable (provided the manufacturer doesn't screw things up with their overlays). Sorry for the rant.

With that being said has anyone found additional solutions to vibration issue?

Thanks,

matt
[LG Revolution] markapowell:
The vibration issue is the phone getting stuck in the shut down process. People who run blitzkrieg have this issue, but its nothing major so hasn't really been worked on. Those not running blitzkrieg kernel, try Gingerhome ROM, then go back to gingervolt to see if that fixes it. If its constantly doing it after that, let us know.
[LG Revolution] billney:
I had this too multiple times a day until I set my min to 768. Hasn't happened since.
[LG Revolution] kcarden:
Sorry for blank...

my issue seems to be battery related. I just got the reset with 33% and now i have 6%

Devs.. look into it!
[LG Revolution] markapowell:
That's nothing to worry about. It's still at 33%
[LG Revolution] kcarden:
well I've come down to the conclusion that it has something either to do with that or the notification light. for instance i only get the reset when the blue light comes on. so maybe it has something to do with the blue notification light? is there any lead on where the promblem resides?
[LG Revolution] elreydotcom:
From what we have found, it seems to be related to the vibrate function.
[LG Revolution] splat matt:
So far this seems to work. How has your battery life been with the min set this high?

***Update***

buttons are flashing at the bottom and it rebooted. I think I'm going to unroot & warranty the device for her. Then for valentines day buy her an iPhone and sell the warrantied Revo.
[Motorola Droid X2] tprouty:
so I installed v6 supercharger and I used the kernel tweaks and now im boot looping.

I tried to wipe data from factory recovery, and im still boot looping.

I cant get past the M logo....

does anyone know how to get into the modified recovery to run a restore?
[Motorola Droid X2] Jubomime:
If you've tried wiping from android recovery and you're still stuck at M, you'll have to sbf.
[Motorola Droid X2] 03civicdx:
This.
[Motorola Droid X2] Peperm1nt:
Get the init scripts I the cm7 .zip and push to correct spot...the set correct perms.

Tapin' the Talk on the xSquared
[Motorola Droid X2] iBolski:
If you're getting stuck at the M while trying to boot back into BSR, then it means you didn't flash the patched BSR after installing CM7. You must install the new BSR after booting into CM7 if you wish to flash anything after that.

At this point, since you used the V6 Turbocharger scripts (which HAS a disclaimer that it CAN cause bootloops, so I would suggest staying away from it), you're going to have to SBF back and start over since you can't even boot up to even try to fix the issue. If you would have installed the patched BSR after installing CM7, then you would be able to boot into BSR and reflash CM7 to fix your issue.

Factory reset won't help. it doesn't wipe out the init.d scripts which is why that didn't help.
[Motorola Droid X2] tprouty:
I have installed the patched BSR, and used it so I know it works.
[Motorola Droid X2] iBolski:
Okay. Usually, the hanging at the M is a sign of using the wrong BSR. I guess at this point, your only recourse is to SBF.

Just remember, the original BSR can be used BEFORE you flash CM7 on. But, once you have CM7, you must install and run the patched BSR before you attempt to reboot into BSR or you get the symptoms you were describing.

I had this issue the first time I used CM7. I ran the APK to install the program, but I forgot to actually RUN the BSR application and tell it to install itself and then click on the Recover button. So, even though I installed the APK itself, I forgot to actually install the recover program to run upon reboot. :eek:

Luckily, I wasn't at a boot loop, so I just booted back into CM7 and finished the steps I missed.
[Motorola Droid X2] jsgraphicart:
The problem is probably caused by the V6 Supercharger script. They may not work with CM7. As well as probably all the other scripts out there unless its modified right.
[Motorola Droid X2] tprouty:
Thanks for all the input, trying to start the SBF now.

I had BSR all set for CM7, ran the install recovery after loading CM7 and actually installed a zip(speedy V7) after being on CM7.

I removed all those files with speedy and wanted to use V6 because it worked better when i was on eclipse than speedy did. I was running the scripts and wanted to test the waters with the kernel script and thats where i got hung up. all the other scripts in V6 workd great! lesson learned dont mess with kernel tweaks when i get back up!
[Motorola Droid X2] Infantry667:
The I/O scheduler tweak in KAK is known to cause bootloops on the X2

SBF'd from my tasty X2 MAXX
[General Questions and Answers] ismore:
I have a Galaxy Tab 7 WIFI (P1010) Purchased online in the USA that I had delivered to my home in Tunisia. It had a problem right out of the box. It starts fine and will work for a few minutes, but then reboots and goes into a constant reboot cycle. I tried a factory reset, but that had no effect. CircuitCity.com, where I purchased it will not help me because it has been more than 14 days from purchase (didn't receive it for more than a month after purchase) and Samsung won't help me because I am in Africa and it was purchased in the USA. I took it to a Samsung authorized service center here in Tunisia, but they could not help me because Samsung USA would not give them access to the stock USA ROM, and they were afraid that a Tunisian ROM would brick it. I tried flashing a European Gingerbread ROM, but that did not fix the problem. It still boots, but only works for a couple of minutes before rebooting. What I would like to find is the stock Froyo ROM so I can at least restore my warranty. The stock setup was PDA: KC6 / CSC: KC6 (XAR). I would also be interested in any other ROMS that are known to work with US versions of the P1010 (wifi only) Tab. Thanks.
[Xoom General] ashwanikoul:
I installed the stock motorola US wifi xoom 1st and then it auto updated to honeycomb 3.1 to 3.2 to 3.2.2 to ICS finally.. all in an hours time

of course the 3g doesnt work..

but what the hell
[Xoom General] te0o:
Could you give me some details about how you installed the Wi-Fi ROM?
[Xoom General] Yamaraj:
Because the update concerns the GED Xoom WiFi-only US model as of yet. The Honeycomb 3.2 refresh took months to reach EU/Asian 3G models the last time.
[Xoom General] ashwanikoul:
download the GED rom from here http://developer.motorola.com/products/software/MZ604_HWI69.zip/

extract to platform tools

fastboot flash boot boot.img

fastboot flash system system.img

fastboot flash recovery recovery.img

fastboot flash userdata userdata.img

fastboot erase cache

fastboot oem lock ( need not do this)

using adb

like you have to go to stock if you are on a custom ROM

then flash via fastboot

and its all done...