yashsingh1/xdaforums huggingface dataset:
[Sprint HTC EVO 4G LTE] the_hustleman:
Based on experience, all my points are valid.

And yes, that is somewhat of a step back on hardware.

HTC and all other android makers had removable batteries for years, it was yet another advantage android had over iPhone from a hardware perspective.

Now that advantage is gone.

Still no good reason to remove it.

As far as your other points, like i said if you aren't a heavy user, you can get by but I'm a heavy user and no phone on the planet can go 24 hours on a charger.

Also a battery loses 50% of its charge capacity after a year

---------- Post added at 03:15 PM ---------- Previous post was at 03:11 PM ----------

But look at the gs3, slimmest phone, yet nice battery (not as nice as the razr maxx) and its still removable.

Learn something HTC
[Sprint HTC EVO 4G LTE] om4:
S3 does not have a nice unibody frame made from aircraft grade aluminum that has been treated with micro arc oxidation, is it necessary no. Is it a gimmick, considering how thin the frame is and the design of it then in some cases yes, the design allows for natural stress fractures at the weakest points but that's valid with any design. Is it better then the galaxy? Better quality material does not directly lead to build quality but I'm willing to root for the phone that is 3x stronger then stainless steel
[Sprint HTC EVO 4G LTE] crzycrkr:
Um.....
[Sprint HTC EVO 4G LTE] SoraX64:
Yeah.. Pretty sure it's considerably lower than that.
[Sprint HTC EVO 4G LTE] sgt. slaughter:
Still wondering the reason 24hrs matters so much......try charging while u sleep. It's amazing what happens over night to it....

Sent from my Wolfpack EVO
[Sprint HTC EVO 4G LTE] om4:
Lol it shouldn't matter unless you don't sleep and are constantly using the phone for hours on and with all radios turned on
[Sprint HTC EVO 4G LTE] Anthonicia:
Really. I mean if ur on meth then I understand. My company hired three meth heads to delivery parts and gave them EVO LTEs. The one guy came back with no complaints, said he charged on the road while driving. The other meth head brought his EVO back in parts bc he got bored and started tweaking it. The last guy brought back a totally different phone. True story bro...

Ask me about my ability to annoy complete strangers!
[Sprint HTC EVO 4G LTE] the_hustleman:
Smh @ light users
[Sprint HTC EVO 4G LTE] stevemoffler:
Haha

Sent from my LTEVO
[Sprint HTC EVO 4G LTE] lreyes:
I'd like to see jelly bean on my old Motorola flip phone ;)
[Sprint HTC EVO 4G LTE] eXplicit815:
I've gotten the same, if not better with mine.
[Sprint HTC EVO 4G LTE] Robert542:
I remember back to my Samsung moment days when my battery wouldnt last till lunch time so I was pleased with the battery life on my 3D and I am ecstatic with the battery life on my Lte. HTC is headed in the right direction with battery life.
[Sprint HTC EVO 4G LTE] om4:
But a huge step back in multitasking :(
[Sprint HTC EVO 4G LTE] Robert542:
That is true, HTC took away a core function of Android.
[Galaxy S II Q&A, Help & Troubleshooting] tlf55:
Is it possible that underclock to 1000mhz would make my SMS not send ?

I had a problem some week ago about that some SMS send quickly after an other (like one sec after the first SMS) stay at "Pending" without sendin .. I thought it has solved by himself but it occured again today, the only thing i see is that i underclocked my CPU to 1000MHZ

There is no undervolting, and i didn't touch to /system or put tweaks ..

I full wiped, flashed stock rom and flashed Siyah, then underclocked to 1GHZ with Extweaks, didn't touch to anything else ..

So my question is .. Is it possible that underclock may cause some interferance or something like that with my modem that could make possible that some sms send very quickly just stay on "Pending"
[Galaxy S II Q&A, Help & Troubleshooting] Jokesy:
NO!

Underclocking to 1GHz will never do that. Something else must be responsible for it. Maybe a temporary network problem
[Galaxy S II Q&A, Help & Troubleshooting] tlf55:
Even underclocking to 800 mhz ? i did it wrong, i just saw that it was on 800 mhz .. :/ but i didn't see the difference with 1ghz, cause with my phone i just do some SMS (no game or something like that)

I'm satisfacted with 800 mhz, should i leave it like that if you think that it isn't possible that 800 mhz couldn't cause interference and things like this .. or should i go 1ghz ?
[Galaxy S II Q&A, Help & Troubleshooting] Jokesy:
If your phone is running fine, then Leave it like that. Sometimes, I use 800-100MHz myself, anytime i need my phone for two days without charging it.

The problems Underclocking might give you, are phone Freezing, Black screen, Soft reboot etc
[Galaxy S II Q&A, Help & Troubleshooting] kilometers4:
Sounds like your apns are having problems. Have you tried restarting your device a few times?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] PatrickNkamgnia:
Hi All,

Hope I am in the good place to present my problem (i'm new in the forum and I'm just learning the "how to").

Yesterday I've rooted my Gnote (GTN7000 XXLPT - ICS just installed from OTA update). It was the paradise before i decide to instal "DPI change" ...

I set the DPI from 160 to 240 and then save + reboot ... Till that moment, my GNote stuck on the launching logo (Samsung Galaxy Note N7000).

I'm not an expert of Android (the proof ...) and I'm looking for the safest and easiest (step by step) solution to revive my GNote.

I know that XDA is an expert forum and therefore I please every of you that will see my request to help me ...

Ps: A part from the root I have applied no other manipulation on the phone (even the setup of the debuger mode).

Your kind help with this will be saving for me, given that there is no repair / after sale service available in my country.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] tibosee:
Flash a safe kernel (speedmod),enter recovery and wipe data.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] PatrickNkamgnia:
Thank you for your reply Tibosee,

However, I wonder how I can flash the kernel (a little step by step tutorial will be welcome).

Please help with this.

Regards.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Rivan_92:
I´d recommend flashing this kernel (HydraCore) http://xdaforums.com/showthread.php?t=1749863
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] evilspyre:
If you had searched you would have known that you shouldn't use the app to change the DPI. Once you have reflashed a ROM or installed a new kernel, then use Rom Toolbox instead or edit the build.prop manually to change the DPI.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] jeriz:
Don't be to hard on him its not stupid to think that an app on market will work as advertised
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Chillz88:
Dont use apps to change dpi.. it wont work mostly.. i had the same problem on my note.. change it manually via your build prop..
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] jeriz:
Rom toolbox works if you don't want to mess with build prop but evilspyre already mentioned that
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] PatrickNkamgnia:
Dears,

Thanks a lot for all assistance with this. Google play will never lies me as long as XDA will be there !

From your various explanations I've drawn the process below (please confirm that my comprehension is correct):

1 - Download and install Mobile Odin (Please provide a link to the safest version); Dont know if Odin will see the phone since i've not activated the debuger mode when the phone parameters was accessible.

2 - Download and install Hydracore Kernel;

3 - Connect the phone on the PC and run Odin (at this step I am not sure to know what to do);

4 - Flash and enjoy (Hope I'll reach this step)

May be the procedure with CWM will be more practicable, especially in case Odin do not see the phone ... But I really not know how to handle it. That's the reason why I was asking a Step by Step assistance.

Thanks and Regards
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] joey_oggie:
You only use one of the two applications; Mobile Odin or PC Odin. You don't have to use them together. Since your phone doesn't boot, then I assume Mobile Odin is out of the question. I'm gonna write a quick guide to use PC Odin.

1- Download PC Odin from this link: http://ul.to/xt4607xx (you can search the forum, you will find many download links for Odin 1.85)

EDIT: Here's another link, the 1st one doesn't want to work anymore. http://k0nane.info/rom/odin-185.zip You can google "odin 1.85" and open the first link (it should be an xda forums attachment)

2- Download the standard tar file of the Hydracore 3.5 kernel from this thread: http://xdaforums.com/showthread.php?t=1749863

3- Open PC Odin and click on PDA and choose your kernel tar file downloaded from step 2.

4- Remove all check marks and leave only Auto Reboot and F. Reset Time CHECKED.

5- Turn your phone off and remove the battery and reinsert it.

6- Turn your phone on by pressing and holding the Power button + Menu button + Volume Down button (to get into Download mode).

7- Connect the phone to the USB cable and connect it to the computer. Odin should show a yellow box.

8- Press Start in PC Odin. The yellow box will turn green which means a successful flash.

9- Now you can wipe data safely (never wipe data using stock ICS kernel btw). :)
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] chasmodo:
How is flashing the kernel going to solve the problem of a b0rked build.prop? Get out of here people.

The only solution to his problem is to flash a custom Rom.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] PatrickNkamgnia:
Hi Chasmodo,

I was just about to flash the Kernel of my GNote following Joey's + others advices above.

Please why do you think flashing the Kernel is not advisable? ... Do you think the phone will thereafter completely brick?

Please answer these two questions as quick as you can ... My finger is on the "red bouton" just waiting for you.

Could you also provide a link to a step by step tutorial in case the solution proposed by Joey is safe but comes unsuccessful ?

Thank you for your contribution.

Regards.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] foxmeister:
If your build.prop is corrupted/broken, flashing a new kernel won't fix it because it won't replace your build.prop.

As Chas said, the easiest fix would be to flash a custom ROM, as this will replace your build.prop.

Regards,

Dave
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] joey_oggie:
Well, to flash a new ROM, he needs to be on a safe kernel...

And anyway, I thought wiping data = factory reset. Isn't that right? If so, then wouldn't the wipe fix his problem? I'm new to this stuff so excuse me if that's completely wrong.

Well, from what I read, most (if not all) Samsung stock ICS kernels have a bug which would corrupt the data partition when you wipe on any of them. The problem would appear when you wipe ON them, and not wipe them. :)

I would wait till he replies to be on the safe side. In the meantime, try to burn some time and read some of the threads in the Note's android development section.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] apurvapatel:
Also flashing the stock Samsung ROM would also solve the problem as it would replace the wrongly edited build.prop with the stock build.prop.

Assuming you have the stock ROM downloaded on your PC, flash it using PC ODIN as explained in an earlier post.

Everything downloading, installing and rooting the stock ROMs is explained here by Dr Ketan

Once that is done, you can root your stock ROM and install mobile odin. You can then flash any custom kernel which is safe and has the brick bug covered. Factory wipe using a safe custom kernel wont brick your phone then.

I am not sure if flashing a safe custom kernel and doing a factory reset would replace the faulty build.prop file with a stock one directly. Chasmodo could explain more....

Flashing a stock ROM would surely replace everything with stock. So you have a clean stock state from which you can play around (rooting, custom kernels/ROMS, etc)
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] jeriz:
Wiping /data won't touch /system where build.prop is

---------- Post added at 09:04 AM ---------- Previous post was at 08:55 AM ----------

Xda is full of instructions on how to use odin search it. Flashing a kernel won't fix your problem. Best to do as previously advised and flash a new rom, stock or custom either will do

AND DON'T PANIC take it slow and don't do anything before you understand the process your phone is currently in no danger what so ever but a faulty flash can definitely brick it
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] PatrickNkamgnia:
Thank you all,

Really hope that this issue will help all GNote users when solved. Sure we are approaching the solution ...

I read in Dr Ketan tutorial the following:

Don't wipe anything from stock ICS recovery

Don't factory reset/Hard reset on stock ICS.

Don't flash any Wipe version of ICS ROM

Yesterday, after my GNote freezed on the "Samsung Galaxy Note N7000" image I tried to hard reset by wiping user data via ICS recovery (just after rooting the phone with CWM.

Does it means that my GNote is now bricked?

If it is the case shoud I anyway continue to follow Dr. Ketan tutorial to flash my GNote with a stock rom?

Regards.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] apurvapatel:
Very sorry to say buddy, your Note most likely is bricked. I hope I am wrong.

Try installing a stock ROM, preferrably Ginger Bread ROM via PC ODIN. If it fails, most likely, at FactoryFS write, then your phone is surely bricked.

Let us know how it goes, we can guide you further accordingly.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] letters_to_cleo:
see if you can still go to download mode and reflash a stock GB on your device. If it's successful then your good to go... if not, then look for the thread here to revive a brick phone.. note down the errors your getting (if there are any errors at all) when your going to reflash it again.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] apurvapatel:
Since you did do a hard reset, most likely it is bricked. If indeed it is bricked, there are 3 options you got.

Go through uggies' thread. Excellent tutorial of manually partitioning the corrupted partitions by forest1971.

Second option is custom PIT method by hg42 at this thread. Does the same thing, re partitioning the corrupt partitions, in a little automated (easier) way.

Third, check in download mode if your binary count is zero and "Custom ROM" shows No. If it is zero, take it to the service center to get it repaired under warranty. Do not tell them that you rooted your phone. Just tell them that after an upgrade the phone is stuck at this screen and it wont start. As long at the binary count is zero, they wont know if the phone was rooted or if it had a custom kernel/ROM installed.

Personally, I have been through what you are going at the moment. I had bricked my Note and followed forest's excellent guide from uggies' post about manually partitioning the internal memory. Believe me, it is a headache and you loose about 3gb of your internal 11gb space. And even after repartitioning and getting the phone to start again, there is no guarantee that it will run smooth. For me, after installing a ROM after reviving, my phone would freeze up for no reasion. Solution? Repartitioning and and loosing a little more internal space. Finally I got frustrated enough to take it to the service center and get it replaced.

Even if your binary count is up, there are ways to reset it on a bricked non working Note and then take it to the service center.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] PatrickNkamgnia:
Ok thanks.

I'll try and revert to you.

I'm getting desperated... However, could I flash GB with my deemed faulty kernel ? will it work anyway ?

Just a precision before: I've updated my rom from GB to ICS recently (September 2nd) via WIFI, may my ICS stock rom be a safe one covering me from brick risks ?

Regards.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] PatrickNkamgnia:
Thanks again,

However, all what you explained still really complicated for me ... I think, from your previous post that the better way to know if my GNote is bricked is to:

1 - Download ODIN PC;

2 - Download a stock GB rom;

3 - See if it goes well and thereafter reflash an ICS

My only problem is to know if ODIN will be able to install the stock GB rom with a Kernel which may be bad.

Is it another easiest way to first verify if the phone is bricked. Note shall be taken to the fact that 1)- there is no Samsung repair service in my location. 2) - When I rooted my phone with CWM I red something like ... the method will not increase the binary count.

Let me summarize all what hapens hereafter for you to better understand my situation and may be provide an accurate solution:

1 - August 30th - GNote running on GB official - No pb;

2 - September 2th - The phone proposed wifi update to ICS that I've applied;

3 - I was interested in removing adds from some application then I decided to root;

4 - September 8th - I rooted with CWM (put 3 files in the SD card then install super user and others from the recovery);

5 - I goes great ... but it was not anougth, so I decided to change DPI to avoid wraping of long application names in the menu;

6 - I installed "DPI change", move de DPI from 160 to HDPI 240 (if I remember exactly) then save and restart;

7 - The phone restart but still not moving from the "Samsung Galaxy Note N7000" startind splashscreen;

8 - Afraid to brick the phone I restarted the phone in the recovery mode (Vol High + Center + On) and I choose "whipe .... factory reset" (or something similar)

9 - The phone still stucked on "Samsung Galaxy Note N7000" screen ...

10 - I registered with XDA to meet and chat with experts ...

Does it help you to accurate your opinion?

Regards.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] apurvapatel:
First and foremost, stay calm. :) I know, easier said than done...

The rooting method you used, with the 3 files (cwm.zip and other) indeed wont increase your binary count. It would be zero for your phone since you havent flashed any custom kernel.

Just to inform you, if you flash anything custom via PC ODIN, it will increase your binary count. If you ever want to flash custom Kernel or ROM, always do it either through a safe custom Kernel :p or via Mobile ODIN.

Also, from my experience, the best method to upgrade your ROM is offline. When you get the message from Samsung about a new update, do not download it. Dr Ketan has his excellent thread about the stock ROMS which he updates regularly. Download the ROM you need and flash it via ODIN, PC (for stock) as well as Mobile (for stock and custom) are good.

Coming back to your querry, the easiest way to verify if it is bricked or not is to flash a ROM.

As I said earlier, on PC ODIN, flash a stock GB ROM. That will remove your custom kernel and install the stock kernel which is shipped with that stock ROM version. So you should be good.

While flashing the stock GB ROM, if PC ODIN gets stuck at NAND WRITE (or something like it) while writing FACTORYFS, than your phone is bricked.

If it flashes your without any error, it will reboot your phone and it should start perfectly. Once that is done, you are good to go. You can than download and flash an ICS ROM (stock or custom).

To summarize, what you need to do at the moment is, flash a stock GB ROM via PC ODIN and report back.

Revert back.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] :
fastest way is to flash buildprop from standard rom with cwm flashable. Some threads on that.

all on safe kernel ofc, then wipe cache and dalvik. Optional.

Only use rom toolbox in future or manual edit of buildprop in future :)

Sent with L0VE&CΔRE
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Bingoig11:
I had a similar problem while trying to change DPI on Liquid Smooth.

Tried to flash a stock GB ROM using ODIN, but bootloop after successful flash...

Don't like this...
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] :
mist roms are nonwipe, so you are bound to have stuff lingering that conflict, especially between ics and gb. In GB factory reset solves this. Dont do this on ICS.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Bingoig11:
Currently trying to install GB not ICS (I'm aware of the emmc bug).

What is strange, is that flash is successful but after rebooting, the bootloop appears.

I tried to enter stock recovery to wipe but cannot access it (don't know when to release Vol Up and Home buttons, tried several combinations no luck).
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] :
turn off phone

turn on phone

press volume up, home key and power at same time. Keep pressed, It will reboot and into recovery,

select with volune keys and confirm your option with power button.

practice makes perfect:)
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] nokiamodeln91:
download a factoryfs img of ur location from xda thread or sammobile and flash it using pc odin.... and check
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] :
preferably to prevent issues of your csc, or at least have a good efs backup.

The factory file is not likely downloadable. It is contained in all rom tar files that you can extract with 7zip lol. However, you can just flash the tar file.

Whats the purpose of only the factory file?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] nokiamodeln91:
that's what I meant.. The official factory firmware. tar. md5
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Bingoig11:
Yep, after a few search, I noticed that I should press all buttons at the same time, this was my mistake ;)

I succeeded to enter stock recovery, full wipe and boot GB again :D

So now I'm back to my favorite custom rom ;)

Thanks for your help ;)
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] :
your welcome happy flashing and be safe on safe kernels.

Dont forget to backup efs on multiple locations ;)
[Samsung Galaxy Nexus] viper98:
I want to upgrade to JB but all the guides I'm seeing are for upgrading from 4.0.4 to 4.1

I've got 4.0.2

can anyone help me out?
[Samsung Galaxy Nexus] IINexusII:
use efrants guide and flash either the takju or yakju builds if you have a GSM model
[Asus Transformer TF700] originalnabisco:
Hello,

I recently replaced my TF201 (Transformer Prime) with a TF700 from BestBuy.

I am impressed with how many problems they fixed, such as GPS, WiFi, and also impressed with the full HD screen!

The one main issue that bothers me is certain animations seem to stutter and are generally much slower than my TF201 was. I am even comparing it to two TF300 in front of me (one on ICS, one on JB) and the TF300's animations are so much more fluid and responsive.

1) One that is very apparent is screen rotation. If I am on the stock launcher with the default wallpaper with default icons and widgets if I change orientation it takes a long time to actually start changing orientation and the animation is not fluid and stutters. If I do the same thing with a TF300 in front of me the the time it takes to start changing orientation is 3 times faster, and the animation is completely fluid - I cannot see any stuttering or framerate drops.

2) Certain menu transitions have the same stuttering problem (although not as obvious since the transitions are fast). Pressing System Firmware Update is an example.

3) Also occasionally using certain Live Wallpapers (such as ASUS DayScene) will cause the Recent Apps menu to stutter a lot.

I just want to see if it is all TF700's that suffer this issue or if it is just mine.

I am running locked, stock OS, and rooted. Also have latest version from ASUS.

If anyone can test the scenarios I mentioned above and reply to this post it would be greatly appreciated.

Thank you!