yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] pukemon:
Oh forgot to mention, i usually order a bunch of el cheapos from hong kong. Premium protectors usually do last longer, but if you find some decent cheap ones it can be more economical. I usually get 5 for $4 shipped from hk, and the skinomi i just ordered was $6 for one. Usually 2 or 3 premium ones are $10-$15. Doing the math and usually changing protectors about every 6 weeks id rather buy 10 from hk and that will last the life of the phone.

Sent from my samsung gt i9250 using powers of the unicorn.
[Samsung Galaxy Nexus] kwazi:
I've always been a big fan of ZAGG protectors. I have them on most of my devices. They can be a REAL pain to apply, but once you get the hang of it, it's not so bad. I've never had a problem with them. I did screw up an installation once.. was a bit too aggressive with the squeegee, left a bunch of marks, but they were nice enough to ship me a free replacement :)

This time, I'm trying Skinomi. Mainly because ZAGG now charges a ridiculous shipping fee for Canada ($17 on a 12$ protector!!). Whereas Skinomi ships for free to Canada.

Anyways whichever you decide, here are some lovely coupon codes :)

skinomi: get25 (25% off)

zagg: youmobile (cant remember but it was 3$ off my order)
[Samsung Galaxy Nexus] :
I ordered a Zagg. Also have one on my Vibrant and I'm used to it. Very durable and wipes clean since it does collect smudges easily. Replacement warranty is good, too.
[Samsung Galaxy Nexus] AfroCreame:
If you're in the states, verizon sells a 3pack of pretty decent screen protectors. I picked mine up at a local store.
[Samsung Galaxy Nexus] qman66:
never buy accessories from a verizon store. they rip u off.
[Samsung Galaxy Nexus] doubleperfect:
Waiting for the martin fields screen and camera protector. Should be available shortly after the galaxy nexus gets released in Asia (whenever that may be).

My friend has it on his S2 and I didn't even realize it was on.
[Samsung Galaxy Nexus] BFirebird101:
Invisishield
[Samsung Galaxy Nexus] Noodles5666:
I always use Zagg on all my electronics. JSYK www.zagg.com is running 50% off today and tomorrow site wide and free shipping for orders over $29.99. I got my GN and full body MacBook Air shiel for $34.99 shipped.
[Samsung Galaxy Nexus] rdoliv:
I was using Zagg Invisibleshield in my last 2 devides (Nokia E61 and currently the Nexus).

However, I bought the LG Nexus 4 yesterday, and I wanted to buy the Hi-Def Insisible Shield (not available yet to Nexus 4).

Because of that, I will try a different protection and buy the Skinomi for a change (front and back cover).
[Samsung Galaxy Nexus] thephantom:
Tested zagg before. Lasted less than a month. Hate the feel, hate the orange peel, hate the yellowish color. Bought skinomi and everything was better
[Samsung Galaxy Nexus] BlackJou:
I bought a zagg screen protector at radioshack last week for $4.50 and it looks really nice on the phone
[Samsung Galaxy Nexus] kawaski47:
I really like XO protectors. And If you want more economical packaging and save some money you can get a skin from bestskinsever.com. 2.95 shipping in the US
[Samsung Galaxy Nexus] emptyfoxhole:
I will never buy anything other than Skinomi protectors anymore. They are really easy to set properly and the protection is great. I've used them on 3 Android phones, all from different manufacturers and they work amazingly.

Never tried Zagg since I started using Skinomi first.
[Samsung Galaxy Nexus] z0mghii:
I have an extra skinomi screen protector, with the entire package. I can send it to you for free if you just pay for the shipping.

I don't really like the rubber feel that comes with skinomi/zagg protectors, although it offers probably the maximum amount of protection you can get with screen protectors
[Samsung Galaxy Nexus] vinfletcham07:
I can definitely vouch for skinomi. i've had it for my last two phones, and i don't think id get any other brand. one think that i didn't even realize i appreciated about their protectors after buying an alternate brand is that they make the screen look really nice. they don't take away or interfere with the color at all. very appreciated. got another brand of screen protector when i first got my gn, and its like it put a matte finish on my screen.

i do swear that next time, if i can find someone to put my screen protector on, i will pay them to do it. i am terrible at it apparently. i have tried ALL the tricks. steam.... steam... you name it.

there was a tiny tiny speck of dust that made a little bubble on the screen, and my skinomi was on a bit crooked and it kept creating bubbles in the corners where my case overlapped. it drove me insane, so i just took it off.

i go commando now. screen looks awesome BTW. :D
[Windows Phone 7 Q&A, Help & Troubleshooting] emanuelparedes:
Do you guys know if there will be a version of Drag Racing available for WP7? When i had an Android smartphone, i was addicted to that game, and i would like to play it on my Trophy. If you know something, let me know please.

A screenshot of the game:

Thanks ;)
[Windows Phone 7 Q&A, Help & Troubleshooting] t00ny45:
There is a game called Shifters. It's something like that, but with better graphics.
[Windows Phone 7 Q&A, Help & Troubleshooting] emanuelparedes:
Thanks , i'll try that game.
[Windows Phone 7 Q&A, Help & Troubleshooting] anichillus:
hy...I don't know if it will be, but i would like that also :)

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

I've tried that and it sucks compared to drag racing ;)
[Windows Phone 7 Q&A, Help & Troubleshooting] sensboston:
Agree. 3D is not for that kind of games...

P.S. BTW, original Drag Racing is too addictive, just a time killer! I'm happy that this game is not available for WP7 :D
[Windows Phone 7 Q&A, Help & Troubleshooting] speedfreak228:
i too would love to have this game
[Windows Phone 7 Q&A, Help & Troubleshooting] anichillus:
now it has been released a version similar to drag racing , it's called "drag race" search it in marketplace ;)
[Windows Phone 7 Q&A, Help & Troubleshooting] jdbastardy:
I found it on the Market too...
[Samsung Epic 4G Touch] cidica:
I've read these forums since they were put online and I've followed all the issues with the phone even before I got it. I knew about the LOS issues and even with it I got the phone. While I've had LOS a total of 4 times even before I rooted my phone after rooting it I did notice it a bit more.

kinda going to reference this thread that was just brought up.

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

Now normally I would not really post a thread but I do have a few ideas after reading a lot of the things on this forum over the last few months. I remember reading that the source that samsung released for the phone was not correct(correct me if I am wrong here) Was something about it not matching the md5 check with what we have on our phones exactly (ie sounds like samsung left things out or maybe they put up an old source code?)

But this got me to thinking after rooting the phone the other day and noticing LOS far more then I ever have (10 times within 4 days and this was running Calk's rom granted all roms do have the issue not trying to single any one rom out by any means)

What if Samsung actually did something within the kernal itself (and they left it out) that either beefed up the radio for cell signal or something along those lines yet they left out "their" code for doing the same thing for rooted phone on purpose? Don't get me wrong I do love this phone rooted or not (which I currently went back to stock without root tonight)

My reason for bringing this up is this. While I was un rooted (regardless of seeing LOS or not which I did) I noticed a few things between stock and root when it comes to phone signal. Even before rooting I've never really had many issues with my phone in my APT never once had LOS yet after rooting I did. I normally put my phone in one spot while I'm on my computer I don't pay attention to it much cause if I'm online I normally am not going to be on my phone yet after rooting the other day and doing what I normally do with my phone a few hours later I went to leave and picked up my phone and noticed I had a LOS and it had been there for awhile.

Now this is normally a spot where I get full 3G bars and NEVER have any issues at all yet after rooting it showed up. After going back to stock tonight I did what I would normally do and no LOS in sight. It honestly makes me wonder while I know a few people are having the LOS issue even with the stock rom (I've had it) it would seam that after rooting it comes it far more often then not which I find very odd why would "root" cause this issue and on top of that why would the 3G signal actually drop from Full bars to 2-3 bars in the same spot. It's almost like Samsung in general did something with the Android Source and the radio together to kind of deter people from rooting.

I dunno just some thoughts I had mind you it is 5am here and I am a little tired so not all of my thoughts are totally there and kinda scatter brained but this just crossed my mind and figured I would bring it up and see what others might think about this.
[Samsung Epic 4G Touch] eman3316@optonline.net:
Seriously, you wasted all that time posting this this when you should have just went to bed?

Next time you have the choice to post something like this or to just go to bed, choose go to bed...

-> eman is very mean this morning. I need to be nice, it's Thanksgiving and all my posts since I have awoken have just been mean!

Going to try and be nice the rest of the day! Happy Thanksgiving everyone!
[Samsung Epic 4G Touch] cidica:
Yes thanks for being an ass and not even actually contributing anything. Great work in that department. :rolleyes:
[Samsung Epic 4G Touch] paranoid android85:
Update your modem to eg31, go back to stock kernel. If you have los go into task manager and clear ram to get rid of los. That's all we can do now to limit los until we get another modem update. Los happens if your rooted or not, some more than others
[Samsung Epic 4G Touch] lojak29:
Ontop of the los its bad enuff that samsung makes poor radios in general compared to moto and htc.. i believe even if the los is fixed the ooor radio build that samsung is known for will still contribute to problems ... if they had the radio strength of the photon the epic touch would be far superior ...but until then we need a phone to function and act as a phone and sgs2 wont ...
[Samsung Epic 4G Touch] Just_s:
Nice thought, but the reality is that there many, many stock phones with LoS. The only reason that there appears to be more issues with rooted phones is that most rooted users are using custom kernels. Go to a stock kernel and watch your LoS drop back to the same level it would be on a non-rooted stock phone. I have the luxury of having a stock phone in the house along with my rooted one and I have been able to verify this in realtime on an ongoing basis. To the point that I can definitely say that my wife's stock E4GT experiences twice as many LoS incidents as my rooted E4GT running the Rogue Stock 1.1 kernel.

I couldn't disagree more! DO NOT update to the EG31 modem and then go to stock kernel. You may be asking for trouble and since there is no going back from EG31, you could be stuck in a bad way as many have reported.

What you want to do is flash a stock kernel with your current setup and give it a few charging cycles/days to settle in and see if that helps. If not try some of the other posted fixes for data and signal. There are many. Some in my signature.

If none of those work and you feel like you have too many LoS experiences and poor data, then you could try flashing EG31 to see if it helps (knowing in advance that it is a one way ticket and you'll be stuck on that modem until someone figures out a way to provide the EG30 modem or some official source is released.) Might also make it difficult to return the phone for any reason as you will never be able to get back to showing the stock EG30 Baseband in the About phone menu (though most techs won't be savvy/care enough to check.) EG31 works great for me, but it does not for many others.

It's been crazy watching people flashing modems for no good reason and then *****ing about the outcome.

Reading first is better than flashing first 100% of the time.
[Samsung Epic 4G Touch] akaiNe-iSolutions:
Haven't had one Los on stock kernel, vipers fix works. End. feels good to be unbanned and able to help
[Samsung Epic 4G Touch] daneurysm:
OP, while we do appreciate your efforts in the brainstorming department you could have picked one of the hundreds (literally) of threads discussing this to post in.

A few things:

1.) Rooting does not cause LOS

2.) Stock phones get LOS

3.) Custom Kernels seem to increase LOS occurance

4.) You can be rooted with the stock kernel (and have the same frequency of LOS as pure stock)

5.) Some people are more heavily affected than others

6.) Being in a fringe service area seems to make it worse for some but not others

7.) This has all been discussed ad nauseum

A few other things:

1.) mkasick built a kernel to be as-stock-as-possible. I ran it for almost 2 weeks without a single LOS. I am now running it again. I got less LOS than stock (which was infrequent but did occur), but, I'm going to stick with calling it 'as good as stock' LOS performance.

2.) chris41g has integrated the changes mkasick made into LoSTKernel experimental builds. Others may have as well.

3.) Different phones seem to have varying levels of susceptibility in the same physical area with the same configurations...It appears there may be a hardware component to some units.

4.) Whether Sprint/Samsung's update can address all of these issues (if they are even separate issues at all) remains to be seen.

5.) Don't screw with flashing modems unless you know what you are getting yourself into. (I, personally, am having an awesome time with EG31 modem and mkasick's kernel....others are experiencing nightmare LOS with stock kernel). There is no going back to EG30 modem yet

sage
[Samsung Epic 4G Touch] JohnCorleone:
Yeah, I got lucky I guess. I am one of those who has better results on EG31 but I wasn't at first. I was quietly regretting my decision until Chris updated the kernel to EG31 w/CWM5. If you aren't having severe LOS then stay put and experiment with different kernels. I was not happy for a few days as I didn't have LOS to begin with, I thought it was the fix and jumped in immediately. Thankfully things have really stabilized and actually improved for me
[Samsung Epic 4G Touch] daneurysm:
I took a few days to think about it and gauge the responses from others since I actually have almost no LOS problems stock, none on mkasick's kernel and very very very few on LoSTKernel exp. But the vast majority of issues seemed to be from people who were on a custom kernel. The rest that were on stock kernel seemed to match the percentage that is screwed no matter what so I jumped in. I'm glad I did. I haven't ventured off of mkasick's kernel, LoSTKernel exp will be next up. That kernel just flies...

Either way Wifi and 3G performance is better, but, I would not recommend anyone to flash EG31 modem...make risky decisions on your own.
[Samsung Epic 4G Touch] JohnCorleone:
Yeah, fortunate for us, it has worked out for the better but if you do it, know that you have to live with your decision until the next update or go to EG12.
[Samsung Epic 4G Touch] nacron:
Running lost kernel on my Refurb e4gt and I've only had Los 3 times. My old phone with zedomax would loss almost every other day
[Samsung Epic 4G Touch] daneurysm:
How does the stock kernel fare?
[Samsung Epic 4G Touch] Just_s:
+1 Pretty much wrote the same thing one post above yours. I think it is very good to repeat this point over and over. I can't believe that people still flash **** without any pause nearly 4 years into Android's public existence. I've spent the entire week helping people who flashed the EG31 modem without even knowing what a modem is or what it does. And then seeing people recommending EG31 left and right as a fix for everything from slow data to gout. Of course not warning anyone of the fact that this is a flash of no return. It's crazy.
[Samsung Epic 4G Touch] -viperboy-:
There has been a development today on the LoS issue, someone in the dev thread (sorry, don't remember their name at the moment) found some interesting things in the logcat that occur only when LoS. I plan to work on the script tonight and get another build out. Stay tuned :)
[Samsung Epic 4G Touch] Just_s:
It was trifthen and yes he did find some interesting info. I am very curious to see what happens when you integrate that into LoS Checker.

I also have to say that you continue to impress with your unending spirit of cooperation in everything you do. I remember that same spirit everytime you were around at MIUI.us and was appreciative of it then as I am now. More about advancement, less about ego. We need more devs like you viper.
[Samsung Epic 4G Touch] nacron:
In the few hours I was running stock kennel I didn't get los lol
[Samsung Epic 4G Touch] daneurysm:
That's all I'm sayin', lol.
[Samsung Epic 4G Touch] nacron:
Spoke too soon, rebooted my phone 4 times in the past 2 days for los
[Xoom Q&A, Help & Troubleshooting] ssss25:
Has anybody been able to get openvpn working on 3.2.1? Can you please help with steps if u can.

Currently I get through the auth and at get config I get

Cannot allocate tun/tap dev dynamically.

I know I don't have tun.ko in my /system/lib/modules. I got the one for 3.2 but it seem to work. I didn't find a tun.ko for 3.2.1.

Help :-)
[Nook Touch Android Development] mali100:
Useful update.zip's

rom_backup.zip

Makes a backup of all the files that are on the /rom partition. Saves it to the SD-card /backup/rom_backup.tgz.

This partition contains some important data, that is unique for every device (serial, MAC, ...).

install_stock_1.1_recovery.zip

Installs the recovery from the stock 1.1 update.

MinimalTouch

Automatic Rooting + Gapps by eded333

install_remount_commands.zip

Adds the commands systemrw (remount /system rewritable) and systemro (remount /system readonly).

If you have useful update.zip's that should be included here, please let me know.
[Nook Touch Android Development] ros87:
Great work

I see you listed "install zip" as one of the features tested, does that mean we can create update.zip's and run them trough cwm?
[Nook Touch Android Development] mali100:
Yes, you can create update.zip's and run them trough cwm, install zip works fine. That should make some of the rooting guides and changes of the framework easier.
[Nook Touch Android Development] ros87:
It sure would!

I noticed that regular update zips use "update-script" while the B&N files use "updater-script", do both work?
[Nook Touch Android Development] mali100:
I think update-script is the old, no longer supported file-format. As far as I know CWM (since version 3) only supports updater-script with an updater-binary (that interprets the script). I only tested the latter.
[Nook Touch Android Development] user4242:
make it fully working without ghosting and we have the base for custom roms, this is simply great. :)
[Nook Touch Android Development] tebra:
very good news.

I hope, a step closer to CyanogenMod or other custom Rom...
[Nook Touch Android Development] met67:
Would it be possible to resize the image to fit in a smaller uSD?
[Nook Touch Android Development] eded333:
Thanks for taking the time into making this tool available for the NST, this opens the possibilities even more for our ereader :)
[Nook Touch Android Development] ros87:
Yes that should be possible, I almost fell of my chair when uncompressing the archive :D

I'm guessing he just smacked the files onto his 2GB card and made an image of it ;)

But yes it's a problem beyond SD cards, I have my Ubuntu VM on a SSD with limited space so 2GB is not a small issue for me ;)

With that said, there's a limit as to how small a fat32 partition can be, but 64MB is doable.
[Nook Touch Android Development] mali100:
I don't think a recovery is a good base for a custom rom. If you want to build one, use the update to 1.1 as base, you should be able to install it with this recovery.

Yes it is, I made it that big because I wanted some space for the backups. I will add an 128MB version tomorrow, when i upload a new beta with less ghosting.

I haven't µSD-cards that small ;)
[Nook Touch Android Development] FletchF:
Very cool! Do you expect to submit this upstream and have it supported in ROM Manager?
[Nook Touch Android Development] ros87:
Showoff!, 2GB is my biggest one, kinda the crown of my collection ;)
[Nook Touch Android Development] mali100:
Once it's stable and well tested, yes.

By the way, does someone know how the reboot to recovery from a running system works on other devices? Does this work on the Nook Color?

"adb reboot recovery" and "reboot to recovery" from CWM just cause a normal reboot to android.
[Nook Touch Android Development] ros87:
There's some trickery going on in u-boot:

When BootCnt is >= 8:

"checkbootcount=\
if fatload mmc ${mmcromdev}:2 0x81c00000 devconf/BootCnt 4; then\
calc.l *0x81c00000 + 1 0x81c00000;\
if itest.l *0x81c00000 < 0; then\
echo Bad Boot count (Fixed);\
mw.l 0x81c00000 0 1;\
fatsave mmc ${mmcromdev}:2 0x81c00000 devconf/BootCnt 4;\
fi;\
if itest.l *0x81c00000 > 7; then\
echo Boot count exceeded;\
echo Forced to boot into recovery mode for Factory Fallback; \
mw.b 0x81c00000 0 0x200;\
cp.s \"boot-recovery\" 0x81c00000 0xd;\
cp.s \"recovery --restore=factory --update_package=MISC:factory.zip\" 0x81c00040 0x3d;\
mw.b 0x81c00048 0xa 1; mw.b 0x81c0005a 0xa 1;\
fatsave mmc ${mmcromdev}:2 0x81c00000 BCB 0x200;\
mw.l 0x81c00000 0 1;\
fatsave mmc ${mmcromdev}:2 0x81c00000 devconf/BootCnt 4;\
else\
echo Boot count OK;\
fi;\
fi" \
[Nook Touch Android Development] FletchF:
On the NC running CM7:

Boot to Recovery from Rom Manager - works

Boot to Recovery from CM power menu - works

reboot recovery from adb - works

Reboot to Recovery from CWM - boots to CM
[Nook Touch Android Development] mali100:
Thats not what i meant. Other android devices allow it to boot from a running system directly into the recovery and I would like to know what function or switch is used for this. Or do you think they just set the boot-counter to 8?
[Nook Touch Android Development] mali100:
Ok, thanks for the info.
[Nook Touch Android Development] ros87:
No, but the recovery is almost certainly not called directly.

What other devices are doing I cannot say, but on the NST you write your intentions to BCB and then reboot methinks :)
[Nook Touch Android Development] met67:
Yes, but NC with CM7 uses a custom MLO written by fattire (IIRC).

On our NST it should be possible to write a boot script that loads an image/kernel or another based (e.g.) on the presence of a file on some partition. Look at the B&N sources, there is a pretty complex UBoot configuration that could give you more insight.
[Nook Touch Android Development] mali100:
You are right, thats how it works on the NST, but I would prefer to change the behavior to act like other devices, rather than changing the apps and binarys that we want to use.

Thats why I want to know which flag is set on other devices to determine that the recovery should be booted.

MLO is the X-Loader, I don't think that we have to change it.

I took a look into the configuration files for the NC and the NST, but till now I'm not 100% sure how that works.
[Nook Touch Android Development] user4242:
I meant that it's the base because it's from a recovery that we can flash custom roms.
[Nook Touch Android Development] met67:
You are right, fattire rewrote the u-boot to add a start menu. MLO was investigated wrt to some weird problems apparently caused by some boot command parameter...

This could be useful:

http://xdaforums.com/showthread.php?t=947698
[Nook Touch Android Development] mali100:
New version is online!

I managed to get the recovery build by the CM-Buildenv, which means a step closer to going upstream.

Rebooting to recovery on the NC is done by writing the string "recovery" to the address 0x40 of the BCB file, I implemented it the same way to the NST. Use the install_reboot_to_recovery.zip to use this function.