yashsingh1/xdaforums huggingface dataset:
[Defy Q&A, Help & Troubleshooting] remix96:
+1 Sense 4 on Defy will be awesome :victory:

---------- Post added at 04:16 PM ---------- Previous post was at 04:16 PM ----------

Maybe he tell the Developer of "Sense4All" project...
[Defy Q&A, Help & Troubleshooting] droid_<3er:
Why is it you again? You came to XDA right after we kicked hemil out, and promised us a sense 2.1 rom for defy.

I hope you remember because we initially suspected you WERE another one of hemil's accounts. Then you stalled

and made an xperia themed rom instead. Now you're asking others to cover up for the work you should have done?

I can't believe it. You're no better than hemil. At least he actually published something.

Well, I don't think Sense4All's developer can help us. He's got an unlocked bootloader in every single device he works with.
[Defy Q&A, Help & Troubleshooting] Defy@1.1Ghz:
+ 1 for Defy with Sense 4
[Defy Q&A, Help & Troubleshooting] merhans:
I think there will be NEVER a sense port to defy!!!! Its quite impossible and 512mb are to less for sense 4 quite to less for sense 4a.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Brad387:
I unintentionally hid some SNS contacts from Facebook. I want them back, but how?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] JulG7:
In settings > Accounts & sync > Sync your facebook profile

You can add the account if there isn't.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Brad387:
Tried that...
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] gatapass:
Hi, sorry for my english,

It's my first kingdroid, and i don't find the dialer dpi mod.

I have try dpi changer, but the phone won't restart after.

How i can change the dpi on kingdroid 4.2, where is it the dpi dialer mod or how use it ?

A lot of thanks.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] StanleyD:
What is your current dpi at the moment?

You can change the dpi in build.prop file.

1. Use Root Explorer or any explorer which can give you root access.

2. Go to System and open the build.prop file in text editor mode (using root explorer) or you can copy build.prop on your computer and edit it using Notepad++.

3. Once you open the build.prop file look for line which says: ro.sf.lcd_density=XXX (here XXX will be the assigned value)

4. Change XXX to 240 (if you want smller icons) or 320 (if you want larger icons)

5. Save and exit the text editor

Hope this helps :good:
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Akiainavas:
Or install Rom Toolbox, select "Performance" and use the slider to set any DPI you want.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] alarajh:
1. Install "Rom toolbox" from play store

2. Go to performance and click on "build.prop Editor"

3. Choose "ro.sf.lcd_density"

4. Enter the number of the required density
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Ayush770:
Link for romtool box - https://play.google.com/store/apps/...wxLDEsImNvbS5qcnVtbXkubGliZXJ0eS50b29sYm94Il0.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] jamir5:
is rom tool box safe to change dpi? if i change value will it be permanent?

rom tool box is quite good,how bout icon changer? any one uses it without prob?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] jon3sh:
No dpi can be changed anytime you want.
[Galaxy S II Q&A, Help & Troubleshooting] lowrider82:
Hi all,

I recently got my GS2 and am currently using the latest miui rom from miuiandroid, however I was considering cMIUI or MIUI.us...anyone that has tried all and knows their stuff can tell me what they think? Are they as stable as miuiandroid's ROM? What are the pros/cons?

Also I have been using SiyahKernel but apparently gokhan has stopped supporting GS2 and now only does GS3...any other kernel you would suggest that is better than siyah and allows 1.6ghz stable oc?

Thanks in advance for helping a newbie!
[Galaxy S II Q&A, Help & Troubleshooting] reinbeau:
Thread closed

The answer is subjective, try them and make your own decision.
[Fascinate General] thefnbiz:
So I have a vzw fascinate that im using as basically a media device. Bought it used and it worked flawlessly. After I reset it, I had to bypass the activation. That worked like a charm, as well. I power cycled the phone once and upon booting it brought me to the screen where it asks "english or spanish." I selected english, thinking I had to re-enter the bypass code, but then it went straight to the main screen. It was then that I realized the home, menu and seach buttons stopped working. They all still light up, though only the back button responds wit haptic feedback. Im positive the buttons arent broken. This happened within hours of me purchasing the phone and before the power cycle, it worked fine. Any ideas?? This sux!
[Galaxy S III Q&A, (US Carriers)] Schaweet:
Will the issues with RIL keep us from getting AOSP ROMs on this device or is it something that Devs can overcome?

Sorry for the noobish question, but I've been reading this may be an issue that can't be solved.
[Galaxy S III Q&A, (US Carriers)] killerT721:
I don't think this will be a problem if developers makes aosp for ICS and not for jellybean. This is a big problem for Resound aosp since developers wanted to fix RIL for ICS aosp but we still haven't gotten ICS officially and HTC never released ICS source. Plus side is Samsung released their source for gs3 on att and T-Mobile so we sld see it soon for verizon
[Galaxy S III Q&A, (US Carriers)] ExodusC:
I'm confused though, I thought the RILs were only a problem when devices shifted from Gingerbread to ICS due to how different they are. I would imagine actual hardware drivers are probably the same between ICS and JB, but I could be wrong.
[Galaxy S III Q&A, (US Carriers)] Stephen.k.spear:
They only released kernel source. Not the ril, from what I have seen. With the exception of the gnexus which we have the source for, no Samsung device has working aosp and 4g on Verizon. That's not saying we won't try, but I wouldn't expect cm9 this week...

sent from my devil unicorn
[Galaxy S III Q&A, (US Carriers)] tekhna:
RIL will be a huge issue preventing AOSP ROMs. But this should be in the Q&A or general discussion section.
[Galaxy S III Q&A, (US Carriers)] Stephen.k.spear:
I think it's fair to say it will be our only issue. There will be many many peeps working on it though.

sent from my devil unicorn
[Galaxy S III Q&A, (US Carriers)] Schaweet:
Sorry about the wrong forum. I saw the Q&A one after I posted here.
[Galaxy S III Q&A, (US Carriers)] Marcismo55:
With all the variations we have of this device on AT&T, Sprint, T-Mo and Verizon utilizing the same chipset there is a definitely a possibility RIL will be cracked. I would imagine once it is figured out for a device on a specific carrier, it would be due time until that fix is ported to others.

With all the Devs I see who have picked up this device I have faith RIL will be cracked but obviously it will take time.
[Galaxy S III Q&A, (US Carriers)] stiltzkin:
Pardon my ignorance of exactly how RIL works, but how different is each one for each carrier variation on a phone like this? Say someone in the Sprint community actually does the low-level dirty work and reverse-engineers their RIL line-by-line in smali. What would that mean for us? How different is a Sprint CDMA radio interface from a Verizon one on the same SoC? Obviously LTE would be a different story.

With the incredible number of people that are about to be behind this flagship phone, I have no doubt the RIL issue will be overcome regardless. This ain't no Droid Charge.
[Galaxy S III Q&A, (US Carriers)] tonu42:
Probably not interchangeable, some parts of it maybe.

And Steve did you get a gs3. Sending this from aokp on your builds for fascinate :)
[Galaxy S III Q&A, (US Carriers)] Stephen.k.spear:
The other carriers use gsm their ril will do nothing for us.

It's in route should be in my hands by Saturday or Monday. I will not use touch wiz and be happy about it. At some point you will see aokp on this device. One way or another.

sent from my devil unicorn
[Galaxy S III Q&A, (US Carriers)] tonu42:
You just made my day :)
[Galaxy S III Q&A, (US Carriers)] Marcismo55:
+1

Thank you for the correction about RIL as well.
[Galaxy S III Q&A, (US Carriers)] LLStarks:
Stephen, will the RIL be the same for Sprint and US Cellular?

I hope the work is shareable across CDMA carriers.
[Galaxy S III Q&A, (US Carriers)] Stephen.k.spear:
US cellular possibly, Sprints lte not wimax maybe.

sent from my devil unicorn
[Galaxy S III Q&A, (US Carriers)] Stryker1297:
wrong forum this is for q and a
[Galaxy S III Q&A, (US Carriers)] tonu42:
No, this is more or less apprpriate for this forum, during launch people would like to be able to see the status of development right away.

So you can take your 31 posts and go whine somewhere else.
[Galaxy S III Q&A, (US Carriers)] nosympathy:
I am going to be returning my iPad to get this phone outright. It has better get CM9 or AOKP.

I do wonder though concerning the LTE side how different the actual coding is per the different carriers. So like said before, for LTE, if someone cracked sprints, or AT&T's LTE coding, if it could be translated to Verizon.

Tell me if I am wrong, but don't all three carriers have identical phone hardware? All three have the same LTE chips, just set to run on different freq bands?
[Galaxy S III Q&A, (US Carriers)] LLStarks:
Forgive me if I sound skeptical, but why would the S3 be special?

Were the Strato and Charge simply not popular enough to get a healthy dev scene for RIL cracking?
[Galaxy S III Q&A, (US Carriers)] tonu42:
No, cause they were all basically rebadged phones. Charge was essentially a fascinate with 4g.

Strato was a repeat epic 4g, when the droid 2/3/4 had the reigns of keyboards already.
[Galaxy S III Q&A, (US Carriers)] LLStarks:
So, is the S3 the first Samsung phone of consequence where the RIL cracking is going to be a huge target?

If that's the case, this sounds like unknown territory moreso than being rather difficult.
[Galaxy S III Q&A, (US Carriers)] neyenlives:
heck no.....the Fascinate is a good historical example and the Charge was the Fascinate all over again but with LTE thrown in which killed it in terms of development beyond Touchwiz based roms
[Galaxy S III Q&A, (US Carriers)] Schaweet:
Guess this is now the least of our worries.
[Galaxy S III Q&A, (US Carriers)] kidhudi:
So even if sammy updates the OS to Jellybean 4.1 and updates the RIL for JB the devs will still have to "crack" the RIL in order to have aosp roms? Please don't say this I have a thunderbolt right now and We still have RIL issues for ICS. That would suck to ditch the t-bolt just to have the s3 and have the same damn RIL issues. I am up for a new phone 8/20 and i am torn between the S3 and the nexus. Do you guys think this phone will ever have a working aosp Jellybean ported rom? ( i hope i am saying it right)
[Galaxy S III Q&A, (US Carriers)] droidstyle:
yes i believe it will get aosp...devs like jt1134 wrote tbe ril from scratch(mtd) and a year later we had cm7, miui, cm9, aokp on the fascinate....point is it may be awhile before it happens, but imo this will be the first 4g lte device with aosp.
[Galaxy S III Q&A, (US Carriers)] killerT721:
Without an unlocked boot loader development is really gonna suffer on this phone which sucks since RIL may not get fixed
[Galaxy S III Q&A, (US Carriers)] Stephen.k.spear:
I hate to say it but I think this device just died. I'm already getting rid of mine and it hasn't even been released yet. I'm getting a Gnexus and not dealing with any of this crap. Sorry to be debbie downer, but F*ck that.
[Galaxy S III Q&A, (US Carriers)] neyenlives:
the device hasn't even been launched yet, and we already have broken through and got root and custom recovery, so to be honest, it's way too soon to be writing it off.....if you want to go back to 2010 hardware on a GNex to get JB then great, but don't make it sound like the entire community has collapsed just because you have no patience

http://xdaforums.com/showpost.php?p=28420589&postcount=47
[Galaxy S III Q&A, (US Carriers)] LLStarks:
People are stressed out because the GNex is a sure thing. Everything will work.

The S3 is a bet, a good bet, but still a bet. JB and custom roms are not a guarantee.
[Galaxy S III Q&A, (US Carriers)] neyenlives:
the thing i think many people don't understand is one does not have to reach CM/AOSP compatibility to have an extremely customize-able and fast device. The Fascinate and Charge from Samsung are great examples of devices that ended up having great development work done even though in the case of the Charge it still hasn't gotten full open source compatibility. The RIL is what is holding it back too.....but to be honest the roms jt and the rest were making based on Touchwiz were phenominal. I also know how good CM on the Fascinate was so I have been on both sides of the issue.
[Galaxy S III Q&A, (US Carriers)] tonu42:
Nope, Invisiblek was able to load a custom kernel on it. As far as I can tell right now, we have everything we need to get everything going on this phone.

So as of now:

System writing : :D

Recovery Writing: :D

Kernel: :p has a workaround

Steve please come back :)
[Galaxy S III Q&A, (US Carriers)] LLStarks:
Worst case scenario, we're stuck with the current workaround or a scripted version of it.

But at least we'd have custom kernels.
[Galaxy S III Q&A, (US Carriers)] Stephen.k.spear:
The wife is keeping the galaxy s3 so it will be around if this mess gets cleared up. But let's be realistic. I develop for AOKP. I need a device that will run jb in the near future. So I'll be lurking but you'll see more of me on the fascinate and gnexus forums for the being. I think these guys are doing great work and I think the tw ui is actually very nice. It's just not something I can spend time in right now.
[Galaxy S III Q&A, (US Carriers)] tonu42:
fair enough, I'll be lurking the fascinate forums, if I need you hollah at you, I'll pm you.
[Galaxy S III Q&A, (US Carriers)] walloftvs:
So what's the status on RIL cracking? I seen a very small set of posts saying that the AOSP RIL for LTE and/or CDMA radios has been figured out but can't find much.

If this is indeed true, this is absolutely huge -- coming from the Rezound, I can attest to that.

So are these reports legit? Or do I simply suck at searching? lol. :laugh:
[Galaxy S III Q&A, (US Carriers)] killerT721:
I also would like to know if this has been confirmed coming from a rezound.
[Galaxy S III Q&A, (US Carriers)] walloftvs:
http://review.cyanogenmod.com/#/c/18352/

Crazy this isn't getting more attention. Or like I said, maybe I'm looking in the wrong place. :confused:
[Galaxy S III Q&A, (US Carriers)] killerT721:
This looks great! Wonder if it works
[Galaxy S III Q&A, (US Carriers)] neyenlives:
There is rumor that CM9 will compile and most likely work now.....not sure how many times it has been done just yet. Thats why it hasn't been publicized much yet I reckon.
[Galaxy S III Q&A, (US Carriers)] ken830:
I got my phone two days ago, but I've noticed this from the very beginning. Completely stock with latest OTA (Sprint). I've been collecting screenshots and taking notes to try to find a pattern and to better understand the problem. Check out the 100% screen-shots below. I've added some arrows. Notice that once you see artifacts on a letter, the same artifacts appear on every occurrence of that letter (of the same size/font/etc). For instance, the lowercase letter "r" appears three times in big, white, heading font and all exhibit the exact same artifacts. The "r" in the grey subtext and the "r" in heading ("Wireless") do not. Both "F" characters in the "OFF" button look identical as welll (forgot to put some arrows here).

The problem seems random and affect random letters at random times. The fact that the screenshot sees it means that it is not a problem with the screen. It is actually in the screen buffer. It seems like a font rendering issue, since the artifacts are identical on all occurrences of the character.

Changing fonts doesn't fix it. Changing text size doesn't fix it. I can interact with the screen, and the artifacts remain. But if I change screens (select an option, open/close an app, etc.) then the artifacts change. By change, I mean it may go away but other artifacts may show up. It is not super common, but if I navigate around the options menu (because it has a lot of text), I will probably see it within 15-30 seconds. Some are so minor, that I don't easily notice.

Has anyone else seen these before?!

The attached zip file contains a few more untouched (except for hiding personal info in one) screenshots. I have a lot more screenshots if anyone is interested.
[Galaxy S III Q&A, (US Carriers)] kronium:
I get them too. Only noticed it in the system menu though.
[Galaxy S III Q&A, (US Carriers)] ken830:
I rarely see it outside of the system menu, but it might be because there's a lot less text. But it does happen. The second screenshot above showed that it could happen in the homescreen (the alarm widget) and here's one in the "Reddit is Fun" app. All the letter "o" characters in the title bar are messed-up:
[Galaxy S III Q&A, (US Carriers)] universem2:
Solution??

Did you guys find a solution for this? Have you guys contacted Samsung?
[Galaxy S III Q&A, (US Carriers)] ken830:
Does this mean that you have the same issue too? From the lack of replies to this thread, it seems not many people do or they aren't OCD enough to care. Anyhow, I'm exchanging my phone for another reason (two dead sub pixels and several random reboots) so it will be interesting to see if the new phone behaves the same way.
[Galaxy S III Q&A, (US Carriers)] jacksparr0w:
Well it seems I have this issue as well but what concerns me the most is if this is a hardware defect. If I can flash a drastically different ROM from the stock one and the corrupted fonts do not appear then it is most likely a software issue however at this point I think it is a hardware issue. :(

Nothing else is wrong with my phone so I would hate to give it back just for this reason and then get a phone that has dead pixels or a screen filled with those black dots people here are tacking about.. :eek:
[Galaxy S III Q&A, (US Carriers)] hayabusa1300cc:
Here's mine
[Galaxy S III Q&A, (US Carriers)] ken830:
Hayabusa... Your font corruption is on a whole 'nother level!! Could you describe what happened? Is this a regular occurrence?

Good (?) thing mine has dead pixels and other issues, so I have no problem exchanging mine. If the new one does it too, then it is definitely more wide-spread.
[Galaxy S III Q&A, (US Carriers)] hayabusa1300cc:
Haha luckily I remember what to click on

It was the first time I seen it lol
[Galaxy S III Q&A, (US Carriers)] bohiti:
I sincerely doubt this is a hardware issue. Have you guys tried changing from the default font? (settings, display, font style) I haven't noticed anything like this, but I switched to helvetica s on the first day of random customizing, just because I remember reading someone who liked it. Seems nice enough, but I don't have much basis to judge fonts.
[Galaxy S III Q&A, (US Carriers)] ken830:
From my OP above:

After seeing this issue, I switched to Helvetica and have been using that since.
[Galaxy S III Q&A, (US Carriers)] jacksparr0w:
I have started using the Helvetica font style as well now and I have not noticed the artifact/corruption at all yet however If I do I will be sure to post it in this thread.

Edit: issue still exists but not as prevalent. I noticed it in settings and on the word today in calender. :banghead:
[Galaxy S III Q&A, (US Carriers)] ken830:
I've tried messing with fonts and sizes myself from the very beginning and it did not help. In fact, changing the font was what caused me to look carefully at the text on the screen and that's when I first started to notice the problem.

I've noticed that it comes and goes in waves... Once it happens, it happens a lot and is more severe. Then, it kinda stops, or is so subtle that it's not noticeable.

Here's a bunch more with various fonts and sizes.
[Galaxy S III Q&A, (US Carriers)] jacksparr0w:
I wish there was a way that we could solve this issue without having to take the phone back... I am so surprised that not many users are reporting this issue, maybe they are not noticing it on there galaxy s3. :confused:
[Galaxy S III Q&A, (US Carriers)] ken830:
Here's an update from me. I received my replacement phone last night and have set it up the same way as my first phone. Same apps, same everything. I used it all night last night, and all day today. So far, so good. No font corruption at all. I got the LG2 update this morning, so I have tried both LF9 and LF2 on the new phone. It's still a little too early to call, but I think this phone won't exhibit the font corruption. Just wanted to let you guys know in case you are near the end of your return period and have a chance to get a replacement phone.

On another note, the old phone had two dead subpixels. One red, one green. The new phone has a single dead blue subpixel. Blue is better, and one is better than two. I think I'll just settle. But boy, Samsung AMOLED screens just kinda suck. They feel like big power hogs and they aren't anywhere near bright enough outdoors.

EDIT: Just updated the old phone to LG2 as well and played with it for just a few minutes before I started to notice the messed-up fonts again.
[Galaxy S III Q&A, (US Carriers)] ken830:
It's been a couple of weeks and my new replacement phone has not shown any font corruption at all. jacksparr0w: You may want to see if T-Mobile can replace yours. Sprint did it, but I used the dead pixels as the reason for my replacement.
[Galaxy S III Q&A, (US Carriers)] OTAw:
T-mobile here and nothing of that sort. My guess would be corrupt font packages.

-Sent from my T999 / T-Mobile Galaxy SIII :)
[Sony Xperia P, U, Sola, Go] IROC_69:
when will we get the big button root software for our xperia P
[Sony Xperia P, U, Sola, Go] Felimenta97:
Probably not so soon.

Sent from my LT26i with Tapatalk 2
[Sony Xperia P, U, Sola, Go] Static-Noise:
Yup, I wouldn't hold your breath. It's going to be some time, if ever.

If you're really keen, I encourage you to learn how to develop and mod, but remember: If the big guns here haven't been able to achieve it, you probably won't.

And I'm not being offensive: I'm being honest.
[Samsung Galaxy S (4G Model)] MrPapito429:
My phone was stuck on searching for 3 weeks, after five resets I upgraded to CM7 then GummyMutt ICS, still did not work so I ualsed one click heimdall back to 2.3.6 GB, I checked phone stats and it said IMEI unknown so I rooted and upgraded to TeamAcid CM9 and still nothing can someone help me because all I can do is use Wi-Fi I'm willing to put up screenies on request but please help

Thnx, MrPapito429
[Samsung Galaxy S (4G Model)] lumin30:
If you lost your IMEI on stock GB and do not have a backup - you have a problem. If you made a nandroid backup when your IMEI was good - you are good. If you flashed one of the newer GB custom ROM's that used the Aroma Installer - you might have a back up.
[Samsung Galaxy S (4G Model)] MrPapito429:
Before I rooted and flashed , my fone had been on searching for over a week
[Samsung Galaxy S (4G Model)] Manumission:
Can you provide a little more information? Did you do anything before your phone lost its IMEI number (e.g., upgrade from Froyo to GB using Kies Mini)? That will help the people here hopefully help you.
[Samsung Galaxy S (4G Model)] MrPapito429:
Yea I upgraded from froyo to GB with Kies mini
[Samsung Galaxy S (4G Model)] lumin30:
Before you did anything to your phone your IMEI was bad?
[Samsung Galaxy S (4G Model)] MrPapito429:
Yea because fone stayed on searching after leaving it off for a day, 2 soft resets, and 5 master resets over the fone from tmobile
[Samsung Galaxy S (4G Model)] lumin30:
Then take it to T-Mobile. Flash bhundven's KJ6 stock one-click in the second link of my signature before you take it in so you will be unrooted and on complete stock.
[Samsung Galaxy S (4G Model)] MrPapito429:
Alright, I will try that thnx