yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 General] demandarin:
Well I have a note 10.1 and nexus 7. Note is completely stock and runs flawless. My nexus 7 is running stock rom with custom kernel. That runs flawless also. Even before custom kernel, superstock, it ran extremely well without any issues for me. My nexus 7 never had issues OP described. Nexus 7 is stable as a mofo ;) never had any issue with that Asus tablet. So lets not go there with since its an Asus, its automatically bad/defective or whatever..lol.

I also have a SG3 which is great ;) superStock.
[Galaxy Note 10.1 General] dxwilliams40:
Try vanilla android on a samsung device like the galaxy nexus and you will have a very different experience. Asus devices are fine once some tweaks have been made, but my tf300 was extremely sluggish on stock. Just got the note and it blows the doors off my tf300 in every category except the note does not have jellybean yet and the tf300 does.
[Galaxy Note 10.1 General] BarryH_GEG:
Here's what I've learned by researching IO on Asus' tablets. People who have no issues and people *****ing about lag etc. are both right. It depends on what you're doing with the device. People with a lot of syncs running in the background or that have multiple apps or a single multithreaded app going that create concurrent processes are more likely to experience issues. Here's a post from someone I know well talking about it. I actually shipped him his N7 from the States. If he says it lags, it lags. ;) His post is in a 67 page thread aptly entitled "The LAG Thread."

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

There's another recently discovered issue that occurs when available storage drops below 3GB. Performance hits the wall. So one or both are probably causing OP's issues.

http://www.gottabemobile.com/2012/09/17/nexus-7-performance-issues/
[Galaxy Note 10.1 General] nonione:
Well I have a galaxy nexus and ever since jellybean its smoother than ever, sometimes even better than on my note 10.1 except if its on cm 10

Just look at the size of the ROMs cm10 is 150 mb while for example high on android is 750 mb, there's definitely a difference performance wise
[Galaxy Note 10.1 General] PsiPhiDan:
If you ran stock JB on Samsung Galaxy Note 10.1 and then the skinned JB (when it finally drops) and you'd see a difference I'm sure. Not AS much since this tablet is a beast, but you'd see improvements.

If vanilla android was the issue, skinning it could only make it worse. They are still utilizing all of the code of vanilla android, and adding their own stuff to it. That can only bog things down. It does on every device I've ever seen.

Finally, I've never heard or see these issues on the Nexus 7. Sounds like you got a lemon. Everything I've heard is that it's the most fluid tablet to date.
[Galaxy Note 10.1 General] tenderidol:
You should visit the Nexus 7 sub-forum (especially the Lag thread) for an alternate view.
[Galaxy Note 10.1 General] aletheus:
The 'obsession' with AOSP stems from a Linux purity thrust. Most OEMs do NOT release their mods to android back as open source contributions, which technically, under the gnu gpl, they should. Samsung-skinned android OS is kind of like Linux mint as opposed to Linux Fedora. Fedora comes out of the box with ABSOLUTELY NO proprietary software, whereas Linux mint ships with flash, Google search (which is NOT open source). So when you run Konqueror (stock KDE browser) you have to download and choose Google as your search engine. Otherwise, it uses duckduckgo, which I prefer..I use ddg on my android tablets even.... I just don't like my search history being chronicled.

AOSP was started in this spirit, which is why gApps are separate and have to be flashed independedntly. Check out https://www.youtube.com/watch?v=CjaC8Pq9-V0&feature=youtube_gdata_player for more information, and a ton of geeky fun.

GT-P6800

GT-N8013
[Galaxy Note 10.1 General] poid:
The 'obsession' is because in the past vanilla Android was clearly faster/more stable than skinned versions. If I compare the Galaxy S to the Nexus S, touchwiz was a slow laggy joke while vanilla Android outperformed it in every way.

Add to that much faster updates, which was much more important as Android matured, and a stellar dev community, and you have a group of people who have preferred Nexus devices over any other.

It has also been easier to flash Nexus devices, and they are virtually impossible to brick. You dont need to use anything like Kies/Odin/Heimdall etc, just install the Android SDK and use fastboot/ADB to set it up, then off you go. Unlocking a bootloader is a single command you use once, and you dont need to flash new bootloaders for updated versions of Android (updating my A500 was a complete pain compared to my Nexus S because of this).

The current generation of Samsung devices are IMO the first gen where Touchwiz works really well. I have absolutely no desire to flash any ROM over the stock Sammy ROM because it works so freaking well. If i get a Note 2 i'm sure it'll be the same, but i am still waiting to see what the new Nexus devices will look like.

I think with the Note 10.1 we have an excellent device that helps us forget just how buggy and crap Touchwiz has been in the past.
[Galaxy Note 10.1 General] MercuryStar:
poid, most of those problems you mentioned are still true.

Adding the manufacturer's customisations to Android still results in fewer and slower Android OS updates, still results in slower, clunky software (this is not so much a problem on extremely powerful processors like in the Note - more noticeable on slow processors like the Tab 2 - why they downgraded the processor in that I'll never know).

Touchwiz has indeed improved a lot, but the fact that it is a customised version of Android still means that Samsung has more work to do in order to push out upgrades and optimise the new software to run smoothly on the device.
[Galaxy Note 10.1 General] mbucks911:
thats not because of vanilla android, its because of asus hw. the galnex with stock jellybean (the kind that it boots with, no cm or aokp) is just as solid as this, and most of the custom roms are as well. the galaxy nexus did not sell many units because not a lot of people know a lot about nexus and the android ecosystem, and it wasnt as hyped with all the commercials and ads as, say the gs2, gs3, or one x.
[Galaxy Note 10.1 General] BarryH_GEG:
All 100% true. And meaningless to the 95% of Android users not considered "enthusiasts." The SGS2 sold 28MM the Note I 7MM and the SGS3 20MM in 100 days. The GN sold 500K. That kind of tells you what the general device purchaser thinks is important and it isn't AOSP. Performance isn't about h/w or s/w in isolation. The GN has a crappy camera, awful display, and horrible battery life. AOSP and JB or KLP can't fix that. Same thing with the h/w issues on the N7. Samsung's always done a great job of tuning the h/w and s/w on their devices to perform better together. Samsung's stock browsers have always blown away all others because of the h/w acceleration they include. Same thing with the additional codecs they provide for audio and video. It's nice to have options through the devs on XDA but not everyone views their devices as a science project.

The performance issues are pretty much gone because of more RAM and faster processors. I have a Teg3 One X and I love Sense. The integration between apps makes me more productive and allows me to get stuff done (EG: rejecting a call with a message and adding it as a task to Outlook to follow-up with one swipe) faster than diddling with a bunch of non-integrated third party apps. Since I actually use my devices getting a 1K higher score in AnTuTu or orgasming over screen transitions is less important than what they're capable of actually doing. The price you pay for an overlay is later (if at all) updates but to some that's an OK trade off. Ask the VZW and Sprint GN owners about getting updates on their "pure Google" devices. They may not agree that's a benefit that always works as described.

I can't root and ROM because of security and registering on foreign GSM networks when I'm traveling so I couldn’t if I wanted to. But I agree with you. The Note and my One X (after the last update) don't leave me wishing I could.
[Galaxy Note 10.1 General] erica_renee:
Nexus 7 is very flawed . but not its os

I will be getting my note 10.1 tomorrow or wed at the latest.

I see alot of nexus 7 talk in this thread and thought i would tell my story.

The nexus 7 software is very nice near flawless there is some issues with touch response and dead spots on the screen. The device itself has a huge design flaw . This is caused by two things. Number one being the bezel is to small under the screen . the lip on the left side has been reduced to allow for the digitizer connections this causes either the bezel to warp or the screen to become loose and lift up and move. This movement is causing screens to crack and shatter. There are issues with A Yellowish spots burn in on the screen as well as screen flashing from issues with light sensor calibration. CM 10 Does help with that issue some. but shutting off the sensor. There are people posting about the device making a squeeling sound then just going off and never coming back on Speakers going bad or not working head phone jack not working.. And so on..

I had a nexus pre order it came in with a few of the above issues. I got a advanced replacement had to send it back on the day it arrived because of huge screen issues. Due to the big hassle with trying to get a refund i sent the other back. its been nearly two months They have both devices back and all of my money..

IN SHORT the nexus 7 is plegued with issues if you have one and its working Lucky you.. But there are more bad then good.. it was pushed to market too soon in my opinion.. but the device i had ran very well and fast . its a great size to pack around but not so good for web browsing .screen to small..

Anyway my opinion only read the nexus 7 forum if you feel anything about is wrong . its all there ..

thanks all ... I eagerly await my note 10.1 tablet ..
[Galaxy Note 10.1 General] poid:
Mercury, agree the actual issues are still there (underlying), just these new phones and tabs have so much processing power that it negates the sloppy code.

Actually i wonder if it means that manufacturers will get even lazier with the efficiency of their skins in the future if they can just apply power/RAM to the problems, rather than needing efficient code?
[Galaxy Note 10.1 General] tenderidol:
Thanks for all the input; I definitely learned a lot.

I purchased the N7 knowing about the screen issue. It is primarily used by my son for occasional games, youtube and netflix to free up my wife's iPad and my Note 10.1. As long as the games don't crash and youtube doesn't buffer, he is perfectly fine with it. He loves the size and the portability as well.

The problems I mentioned in the OP has gotten better actually. After reading the "lag thread" and understanding the hardware limitation of Asus tablets (even the most expensive ones), it appears that while I was installing apps from the Play store and Amazon appstore one after another, poor little N7 was trying to keep up as much as it can... After a few reboots and no more downloading/installing new apps sequentially, it's been working fine so far.

I have to look into how to diagnose the screen lift issue, because, I've been checking that particular area for any signs, but it looks just like the rest of the screen. Who knows, may be I received a "normal" one.

As a side note, Note 10.1 converted my wife from a "possible iPhone 5 buyer" to a "definitely waiting for Note II".
[HTC One X] Jamz442:
Hey guys!

Just a quick question.

Basically I'm in the process of installing a new Sense 4+ ROM on my One X.

I was just about to run the RUU process of the guide, but it won't let me finish because I have a low battery.

So, my One X is just connected to the wall outlet, however the bootloader menu is still showing, but the red light is also showing. It's currently on the Fastboot menu. Even when I click POWER DOWN, the device just boots to the bootloader menu and stays there.

Does this mean the handset is still charging? I HOPE SO!

Need your confirmation guys! :)
[HTC One X] faiz02:
I don't think so.. but I would like you to get a 2nd opinion.
[HTC One X] eyosen:
Try issuing

Fastboot getvar battery-voltage

Command several minutes apart, then you will know if it's charging.
[HTC One X] Jamz442:
Thanks for the tip! Will get back to you and let you know :)
[HTC One X] Jamz442:
Okay Basically it went down! :(

I don't think it charges... But how am I meant to get it to charge?!
[HTC One X] faiz02:
Flash CWM 5.8,4,0 again. I guess it allows charging

also just to be on the safe side, Flash any 2.17 based rom and charge your phone to 100 %

Then start all over again.
[HTC One X] Jamz442:
EDIT: I left it on my laptop plugged it..and its going up again! Seems as though it charges on my laptop.. :D !
[HTC One X] Jamz442:
Okay basically this is taking long guys.

The reason why I can't flash recovery or unlock my bootloader again is also because I have a low battery :(
[HTC One X] faiz02:
if it's charging.. then leave it over night.. start the process in the morning.
[HTC One X] Jamz442:
Hmm, it keep's alternating up and down... For some reason I tried the process again.

What battery % is 3600mV? :confused:

Let me try for another 30mins or so, I shall reply once after 30mins, then again after night. Hopefully it works!
[HTC One X] faiz02:
here is the link for the problem you are going through hope this helps
[HTC One X] Jamz442:
Thanks a lot! I will let you know how it goes tomorrow :D
[HTC One X] eyosen:
If someone helps you, use the thanks button instead. :cool:
[Galaxy S III Q&A, Help & Troubleshooting] Ston:
Hi,

Does anyone know of a way of working around or solving this problem? Basically if I enable Picasa web sync, it pulls down all 7gb of photos to the phones storage which isn't ideal. The stock Jelly Bean gallery on my previous Galaxy Nexus did not do this, it just showed some thumbnails and then downloading the picture when you open it.

So possible options to solve the issue:

1) Get the apk for the stock Jelly Bean and use that gallery (if that would work?)

2) symlink from the phone storage to the external sd card for the gallery cache (I'm not sure if Android would allow that?)

3) use a different app from the play store.

4) anything else?

Regards.
[Galaxy S III Q&A, Help & Troubleshooting] StormtrooprDave:
Try going into settings then data usage then click on gallery and tick restrict background data
[Galaxy S III Q&A, Help & Troubleshooting] Ston:
Thanks, but that's just going to limit the app. I'd like to be able to see all the photos but just as a thumbnail or stored on the card.
[Captivate Q&A, Help & Troubleshooting] RJ287:
First things first. This is NOT a "Which ROM is the best".

I want to know which version of Android

under any circumstances

, and almost specifically about specifications, will, does, or should run best on a Rogers i896 captivate. I have tried many different roms ranging from 2.2, 2.3, 2.3.3, 2.2.3, 4.01, 4.03, 4.1.1 etcetc and so far here are my observations:

The higher up in version, the better the battery life was, but the more glitches/issues/(sometimes lag) I encountered.

For the more technical people: Which version of android should run best on a Captivate considering things like bootloader etc (stuff I know nothing about).

Again, I'm not asking what ROM is better, and I understand that every ROM is different, but I want this from a technical standpoint!

Okay, thanks for taking the time to read the above paragraph and I'm looking forward to the knowledge.
[Captivate Q&A, Help & Troubleshooting] rratalia:
For me, version 2.3.7 (CM 7.2) runs the best. Just bone stock CM. But then again that might be because I don't use this phone that often but it feels like it just runs better.
[Captivate Q&A, Help & Troubleshooting] mikey199:
ICS runs so much faster. Slim ICS is probably the quickest. Devil kernel is a fast kernel. Put em together!
[Captivate Q&A, Help & Troubleshooting] rratalia:
Well, I admit that you might be right. My particular captivate never ran ICS or JB without performance problems, but that is just from my personal experience.
[Captivate Q&A, Help & Troubleshooting] pyrosin:
I would like to know too. I put cm10 on my gfs phone and have had problems. What are most used gingerbread roms? I have looked through the forums but can't find anything solid, others input would help alot I had an epic myself just got gs3. The most stable daily I ran on my epic was 2.3.7. Would like something for her she doesn't ***** about.
[Captivate Q&A, Help & Troubleshooting] ulbonado:
I never ran 4.0.x due to fear of the notorious "encryption unsuccessful" bug, so I can't comment on that one, but now running 4.1.2 (Slim Bean 2.7) and it is definitely smoother, faster, and more stable than any 2.3.x ROM ever was for me. My GB ROMs used to slow down and eventually hang, requiring a reboot every 2-3 days. 4.1.x has never done that-- it just runs and runs. It's so good, it has pretty much cured my previous thoughts of upgrading to a new phone.

As for the bootloaders, they only matter during boot, as the name implies. After that, they don't matter. Just make sure you have the GB bootloaders and you can use any ROM you want.
[Captivate Q&A, Help & Troubleshooting] hednik:
slim bean 2.7 works wonders for me and so did the previous version. Skip google now and you will be golden, at least form my experience.
[Captivate Q&A, Help & Troubleshooting] arse87zx:
Google now runs really bad on my phone as well. I wonder why it uses so much ram, it doesn't seem to be doing so much.
[Captivate Q&A, Help & Troubleshooting] Simba501:
I reverted to the standard Google Search. I find that it has more usefulness. Google Now seemed really cool, but in practice, I don't have much use for it.
[Captivate Q&A, Help & Troubleshooting] sthodupunuri:
There is no specific version that runs naturally better. The smoothness of the rom depends on the developer and what changes he/she made to stock. No version of android after Froyo is naturally better than the others. While it is true that new versions of android bring new features, a good rom will run well regardless of version. This is the reason that stock is usually much more stable than custom roms. Stock is built for stability, so this boils down to which rom works best on your phone and with your preferences. The glitches and lag happen because most of the newer versions of android were never actually released for the captivate, so developers are porting from other sources. Another reason for glitches and lag is the limitations of captivate hardware. There is a reason why it does not receive any updates from samsung anymore. In samsung's eyes the phone's hardware has reached its potential. The captivate was released about 2 years ago, so according to Moore's law the software being released today is for devices that are 2 times more powerful. The fact that jelly bean is able to run at all on this phone is a feat to be proud of so kudos to the developers.

Also, bootloader does not have that much of an impact on performance. The bootloader is just the code that "loads the boot", or turns on the phone. The only thing that changing bootloader affects is compatibility with certain roms.

PS-I know some of the things seem unconnected to your original question, but I wanted to help you completely understand my answer.
[Captivate Q&A, Help & Troubleshooting] RootTheMachine:
Pretty much... I would have to say after using the Captivate on all versions except Eclair that Gingerbread runs the best. Not stock Gingerbread, but CM7 Gingerbread. While ICS/JB feel fast and smooth because of the hardware acceleration and nice animations, the system feels much slower overall and is often subjected to lag/lockups (partially due to things mentioned by the previous post). Things like Google now and Chrome were almost unusable for me. I would attribute the Gingerbread affinity due to the fact that the Captivate and Nexus S are very close hardware-wise, and that hardware was designed to run Gingerbread. CM7 was very fast, and if it weren't for the appearance of GB compared to JB, I would have stuck with it.
[Captivate Q&A, Help & Troubleshooting] pyrosin:
The stock gingerbread was getting worse by the day that's why I convinced her to put a rom on it. I never touched anything beyond gingerbread on my epic because I needed the phone to work for work. I will look into a gingerbread rom for stability.
[Captivate Q&A, Help & Troubleshooting] Microman1934:
SlimBean

I'D say SlimBean with sovaphone or somting kernal
[Captivate Q&A, Help & Troubleshooting] xtremists:
can you guys tell me which is the best modem for battery use and best rom and kernel for battery am using slim 2.7 latest with stock kernel semophrne something i would appreciate if you guys share you experience :)
[Captivate Q&A, Help & Troubleshooting] RootTheMachine:
Modem depends on geographical location, and the rest depends on what works best for your phone. That should be a decent setup though.
[Captivate Q&A, Help & Troubleshooting] Kaiotee:
ICS

For pure battery life I think Fasty KK4 was an excellent Gingerbread. I remember actually being blown away by the battery life.

As far as great performance, Team Nyx ICSSGS was the most rock solid! AOSP 4.0 was light and really fast with decent battery life. All in all, I would say that is my overall favorite of the roms I've run through the ol' cappy.
[HTC One S] JknRich:
Well I been looking around the forum now and wondering if rooting my brand New one S is worth it.

What can you do after you root the phone.

What does it give you the option to do.
[HTC One S] usaff22:
Same as any other phone, except downgrade bootloader and radio.

Flash kernels, flash ROMs, tweaks, lockscreens, record screen etc.

Sent from my locked, tampered ville
[HTC One S] LibertyMonger:
I am kinda wondering the same thing. It seems the only thing rooting will be good for is volume wake, certain apps that require root and custom theme modifications. I am thinking of rooting i guess but until there is a bugless ROM I don't think I am gonna fool with any.
[HTC One S] touch of jobo:
Even if you dont actually root the OS, unlocking the device and flashing a custom recovery gives you the ability to make and restore nandroid backups.

Personally I like the device much better with a custom ROM and kernel and boot splash ;)

So as for whether 'it' (the benefit: an unlocked device with custom ROM) is worth 'it' (the cost: the time and effort of rooting),

if you're happy with the device as is and you consider rooting/flashing a hassle and a chore, then no.

If on the other hand, you have some gripes that custom ROMs address, and you can flash it while watching a sitcom with your other eye, and/or enjoy the tinker, then yes.

-Jobo
[Galaxy Note II Q&A, Help & Troubleshooting] AntonyHwang:
Hello,

Are there any method that we can unlock the GT-N7100 by ourself, or software like the international toolkit that can unlock the Galaxy S3.

Can anyone help me please~

Thank You...
[Galaxy Note II Q&A, Help & Troubleshooting] 05GT:
The N7100 is unlocked from the factory...
[Galaxy Note II Q&A, Help & Troubleshooting] MadfishGTB:
Most phones bought on contract here in the UK are normally locked to that network. There is the option of getting the network to unlock the phone at a small charge if required.

Would be nice to know if there was a way of doing this yourself to save the cost...
[Galaxy Note II Q&A, Help & Troubleshooting] gee2012:
Here is the link to the Sammobile unlock thread http://www.sammobile.com/unlock/index.php?phone=N7100, it seems the N7100 is allready listed. Unlocking costs 15 euro`s and seems to work good. haven`t used it myself though. But it is a reputable site i guess.
[Galaxy Note II Q&A, Help & Troubleshooting] rjwriter78:
If I buy this unlocked off of Amazon, can I use on Sprint LTE network?
[Galaxy Note II Q&A, Help & Troubleshooting] 05GT:
No. It's unlocked to GSM networks.