yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] wtr_dhd:
Like I said I'm on Rasbeanjelly rom. And yeah I used stock 4.2.2 for months too, and those hiccups are indeed annoying, and sometimes switching between homescreens lagged too, or app drawer.

I wouldn't say it was iOS'ish smooth at all, I'd say for android you need a decent high-end quad core phone to have such smoothness. A Note 2 for example even with crappy Touchwiz on it is SOO smooth, it destroys the Gnex in terms of smoothness and speed.. But ok, that's an unfair comparison :)
[Samsung Galaxy Nexus] icase81:
I'll disagree. Its better than my GS3 was stock. I am getting 18+ hours with 2+ hours of screen time on the stock battery, and have the official extended battery on the way. In order to get more than 10-12 hours on the GS3 I needed to root and put an aftermarket ROM and/or kernel, and it CERTAINLY beats the hell out of my buddy's HTC One.
[Samsung Galaxy Nexus] LarsAussems:
@ jsgrpahicart

very funny.

@ hwong

I don't have a lot of widgets; only dashclock and a weather widgets which refreshes every 4 hours.

What I hate is that sometimes it's just so daaaaaaaaaaaamn slow. I'm just like whatsapping and the keyboard ( swiftkey ) just doesn't open. I'm listening to music through poweramp and I get a message, I open it and the moment whatsapp opens, poweramp closes. It's so goddamn annoying. It makes me wanna smash my phone ( figure of speach ofcourse )
[Samsung Galaxy Nexus] hhwong:
try the ak kernel then, and try using westwood/sio/interactive, with 180000min/1200000max, the real battery saver is both the min and min screen off, just set it to 180000 and you will have fairly good battery. I normally get 22hours ish if i just let my phone idle on table, and about 4-5 hours normal use.
[Samsung Galaxy Nexus] jsgraphicart:
Well its true. No two people are going to come in here and tell you the same combo of ROM and kernel. You are going to get a bunch of different answers. The best thing for you to do is to just start trying them out. We all had to do it before we found what worked for us. What works for us may not work for you.
[Samsung Galaxy Nexus] LarsAussems:
Thank you, will try. Is it also just butter smooth? That is now my biggest concern. I accept that the battery s*cks and that it doesn't get any better.
[Samsung Galaxy Nexus] hhwong:
unfortunately, buttery smooth for android is only buttery smooth when you compare to previous versions of android, there will be hiccups no matter what devices you are on, probably due to the os mechanic, i dont know **** about the coding so I really cant say anything about it. but AFAIK, android wont be as smooth as ios in ui for a while, not until they overhaul the entire system like they did in ics and jb. =/ at least thats what everyone is telling me.....

TL;DR - buttery smooth vs 4.1/4.0.
[Samsung Galaxy Nexus] LarsAussems:
Alright, thanks for your help.
[Samsung Galaxy Nexus] speedyink:
Just yesterday I made an iPhone user jealous at how buttery smooth scrolling is on my GNex running 4.2.2 (showed him the text app with a long list of texts and pictures). He couldn't believe how much smoother it was than his iPhone 4.

AOKP M1/Franco kernel
[Samsung Galaxy Nexus] hhwong:
well, i have both ip5 and gnex, my brother has a nexus 4 too, when i tried to compare ip5 with n4, the ui is smooth on both devices, however android will hiccup randomly while ios generally stay smooth, i am not saying iphone never lags, they do as well, but its only under heavy work load, unlike android where they can just lag out of no where, both devices lag under heavy work load, i get that, but somehow android still lag randomly, thats the only thing i am not happt with android, other than that, it is the perfect os comparing to ios.
[Nook Touch General] sarmasm:
Hello:

As stated above, I've a NST 1.1 succesfully rooted with TouchNooter 1.11.20

It has worked fine for months, and it was working fine today:

The device was switched off

I turned it on

I read some with CoolReader

I switched it off

Later on (3 hours or so) I turned it on and since then it's stuck on the start screen, the one that says "nook tm by Barnes & Noble" and has a line of five dots below.

The black dot cycles through the white dots.

If I try to restart it using the power button, the screen flashes and then remains there, never pasing through the "Read forever" screen.

If I simply wait, the screen freezes, displaying "nook tm by Barnes & Noble" with the black dot in one of the five dots below, no longer cycling. If I then try to restart it using the power button, the screen flashes and then remains there, cycling through the white dots, never pasing through the "Read forever" screen... and then it freezes after a while.

If (with screen frozen or not) I try to use the power -> screen flash -> hold down left + right lower buttons it remains in the same screen.

If (with screen frozen or not) I plug it through USB to my PC it will flash the screen, the black dot cycling through the white dots; I do gain r/w acces to the local drive and SD Card

After removing the SD Card, I've tried all of the above, with no change.

So: it doesn't complete the start up and I can't shut it down completely.

Any suggestins on how may I unbrick my NST?

Awaiting your kind reply,
[Nexus 4 Q&A, Help & Troubleshooting] tchen510:
When I plug IB my headphones they work but when I press the volume rockers the external speakers beep instead of the earphones. Am I doing something wrong?
[General Topics] cruisin-thru:
I have a Skypower bluetooth clip on headset and also a Sony Ericsson HBH-65 headset. Both work fine for pick up/cancel calls when using the xda2 with nothing installed. Because I have a Holux bluetooth gps, I needed to install the fantastic blutooth tools program which made the gps operate flawlessly, however if I now discover and pair either headset neither will work. They both bring up bluetooth tools, I have only one installed at any one time, I install as headset and everything seems fine but when making/receiving calls with headset mode activated, the headset does nothing, the calles arent routed to the headset, its as if the headset doesnt exist. Anybody have a suggestion please :?:
[General Topics] cruisin-thru:
I have now reverted to pocket bluetooth tools 1005 and everything working normally again. If anybodt else has this problem please let me know if you managed to solve it as I prefer the latest bluetooth tools.
[General Topics] Mosser:
The only problem i found with the new bluetooth tools is that you have to click on the 'bluetooth headset is enabled' in the profile menu which you really need to keep on the today screen all the time, i found i just tap the bluetooth icon in the bluetooth tools menu, then tap on the enable in the profile menu and i can the make and end and answer calls using the button on the headset, when making calls you can only dial either the number you just typed in, or the last number dialled
[General Topics] brix3:
Bluetooth tools e Qtek 2020

Where can I find 'bluetooth headset is enabled' ?

Thank you,
[General Topics] Camstech:
Click Start, Settings, Today, then the items tab. Put a tick in the "profile" box.

Cheers
[Sony Xperia P, U, Sola, Go] olcimanic:
I realised that my XU doesn't responds any changes on stock or not stock keyboards vibration settings.

In any changes of vibration settings it doesnt effects, all the way phone vibrates at its max. Is it on every Xperia U or just me??

Btw i tried B.10, B.54,C.10, B.89, Zperience V1, eXperience v2 it's all the same...
[Sony Xperia P, U, Sola, Go] rajen77:
Hi! I looked at myself, I would not have discovered a large difference between the weak and the strong. I have a MIUI rom.
[Sony Xperia P, U, Sola, Go] olcimanic:
Well i have no difference :D
[Samsung Galaxy S Relay 4G] Chrizuki:
Does this root method work for Jelly Bean 4.1.2 running Relay devices?
[Samsung Galaxy S Relay 4G] crunkjuice:
yes this should would with any firmware
[Samsung Galaxy S Relay 4G] Chrizuki:
I've done most of the instructions said and everything seems fine with my phone. I have SU and it is rooted, but I'm stuck on "25. Type rm recovery-from-boot.p" because when I type it in, it says that the rm failed because there was no such file or directory. Is it really important/necessary to have a custom recovery?
[Samsung Galaxy S Relay 4G] Jay Dogg:
Quick answer is no you do not need the custom recovery but it is a good idea to have it. As far as step 25 goes make sure you are in the correct directory. Once you have gotten into your phone using adb shell type cd system. Then type pwd and make sure you are in /system. If you are in system type "ls" and see if the file "recovery-from-boot.p" is there. Repeat these steps for the "install-recovery.sh" file. Now if both file are gone off your phone you can Repeat steps 9 to 14 BUT SKIP STEP 12 or even better if the files didn't exist at all then your should be rooted and already have the custom recovery. You can check to see if you have the custom recovery by booting into recovery by holding down Home, Volume Up and Power or by typing adb reboot recovery but make sure you are not in adb shell.

I wrote this tutorial because the Samsung Galaxy Relay 4g I was rooting had these files "recovery-from-boot.p" and "install-recovery.sh" which was more or less a fail safe for the phones recovery. Every time the phone booted it was checking the recovery and replacing it with the stock recovery by using those two files. So my work around was to get the phone rooted and delete those two files then reflash the custom recovery.
[Samsung Galaxy S Relay 4G] Jorakal:
This procedure worked perfectly for me, thanks. I just bought this phone for my Wife. It auto-upgraded to Jelly Bean OTA, and I was ready to root and load recovery. I'm now rooted, and took my first nandroid backup.

The only thing I had to figure out, was how to boot to download mode and recovery. I've done this procedure on many phones and tablets, including a Samsung Galaxy S2, but this phone was a little different. After pressing the volume key, home, and power, you have to release all buttons as soon as you see any text on the screen. For download mode, I had to immediately press volume up within 2 seconds, or it would continue to something else.

I'm curious about this clockwork recovery too. Was it originally written for another device? It works good. I just don't see it offered for this phone in Rom Manager.

Again thanks for taking time to type up this procedure, and for the extra steps at the end for the override. :)
[Samsung Galaxy S Relay 4G] Nardholio:
CWM isn't in ROM Manager probably because we haven't submitted it to them :D
[Samsung Galaxy S Relay 4G] devis:
cannot cannot for the life of me get this phone to go in recovery. Basically stuck right at step 11. Nothing doing. I hold V down, power, home then I get a msg that tells me V down to power off and V up to start download. Anything I do, phone will just reboot. What am I missing?
[Samsung Galaxy S Relay 4G] Jay Dogg:
Step 11 is to boot into download mode not recovery but in post 6 Jorakal said "The only thing I had to figure out, was how to boot to download mode and recovery. I've done this procedure on many phones and tablets, including a Samsung Galaxy S2, but this phone was a little different. After pressing the volume key, home, and power, you have to release all buttons as soon as you see any text on the screen. For download mode, I had to immediately press volume up within 2 seconds, or it would continue to something else." I didn't have to do it that way but if it worked for Jorakal it may work for you.

If that doesn't work for you, you can always try using adb to reboot into download mode the command is "adb reboot download", this will work for you but you may run into problems on step 14 if you can't boot into recovery using "Home, Volume Up and Power" because by the time you can use adb to boot into recovery the phone has already replaced your custom recovery with the stock one.
[Samsung Galaxy S Relay 4G] devis:
I'll try... thanks!
[Samsung Galaxy S Relay 4G] mazak23:
I conclude it is in Odin program.

But on the phone even when its finished in Odin, still white Downloading... And green : Do not turn off target.

Is it right, as I have some problems after reboot.

It is like crashing 3 or 4 times, you can see that on my video.

http://youtu.be/3V24FbY0jH8

I used Odin 3.07 and Super User 1.34

In phone I can see :

Qualcomm secureboot : enable - is that OK?

UPDATE:

All is working fine now.

I follow all steps again.

We don't need to do it with adb, all related commands to adb could be done in shell apk.

Regards and thanks for tutorial.
[Samsung Galaxy S Relay 4G] esilence:
I had to struggle with two points. But got them afterwards. Hence it would be great if you update the instructions:

11. Boot the Samsung Galaxy S Relay 4G into download mode by holding down Home, Volume Down and Power ​

For me, I also had to need to hold down these buttons, but then after message text is coming up, I also then had to release all the buttons and then press Volume up within one second, 2 seconds are too late. Please for that reason just give a note mentioning this in case if its not enough.

please also complete the notice:

NOTE: To confirm the device is connected and working, look for the blue COM box with the word Added!! inside the message box

otherwise I was really confused because in the COM box there is no such text coming in it, and didnt know if I can go ahead or not.

Please check and rewrite the numbers in correct order after 14 - 15 - 14

also because of this:

16. Use volume down key to select UPDATE-SuperSU-v1.25.zip and hit power.​

That was the most difficult part for me as I was getting the message: "E: failed to verify whole-file signature" and the installation failed. I found the solution after many google tries. which is in our case to restart the instruction from 15. and go ahead without failing each steps till 16.

Hence, note: In case of failure, repeat the steps from 15 again.
[Samsung Galaxy S Relay 4G] Ziida:
Can I ask what the significance of running step 28 (the repeat step) is?

Is it necessary for recovery to work properly? I only ask because i installed the recovery following these steps up to but not including step 16, and then tried installing the new bootloader, modem, and latest CM nightly, but it's not getting past the CM splash screen

well I got CM to boot by just rewiping and reflashing, but I'm still curious about step 28. I find every phone can have their quirks and it's important to learn them if your'e going to be flashing :o
[Samsung Galaxy S Relay 4G] robuser007:
Do I need to root te device to flash other roms ? I've red somewhere that I don't have to do this on this device.

My device has the latest official jelly been, so it has the latest radio & bootloader.

edit: It this the correct order ? (I always wipe all partitions before flashing a rom, expect recovery):

http://xdaforums.com/showpost.php?p=46578334&postcount=8
[Samsung Galaxy S Relay 4G] Jay Dogg:
Because of these files "recovery-from-boot.p" and "install-recovery.sh" which was more or less a fail safe for the phones recovery. Every time the phone booted it was checking the recovery and replacing it with the stock recovery by using those two files. So my work around was to get the phone rooted and delete those two files then reflash the custom recovery. Because at this point when you reboot the phone to delete those to files they have already ran and you don't have a custom recovery, all you have is root which is what you need to delete those two files =). It appears some people didn't have these files because they had already rooted there phone be for or where not on the most current OTA. If they didn't have the files then they were done at step 17 and if they had tried to go further would of gotten a errors at steps 25 and 27. But if they had the files and stopped at 17 they would no longer have a custom recovery after they had rebooted the phone. So over all steps repeat steps are just to make sure you have a custom recovery installed.

Thanks Jay
[Samsung Galaxy S Relay 4G] Ziida:
That's very informative. Thank you so much for the response! I guess I just didn't have to continue past step 17!
[Samsung Galaxy S Relay 4G] robuser007:
I get pit error: on heimdall and odin, what's the problem ?

Get PIT for mapping:

Complete(Write) operation failed!

Added!

edit: using another pc and it worked fine with heimdall (very easy to use).
[Samsung Galaxy S Relay 4G] kilo94:
Worked like a champ for me this morning, followed the steps closely. 4th phone rooted...still going strong...
[Samsung Galaxy S Relay 4G] xheretic:
Hello root experts! :D

I just downloaded all files needed for root and I've got one last question...after these 28 steps procedure whats about my personal data? It will be deleted? Like call log,sms, emails, settings etc... Or it will be untouched?

If no...please can You give me advice for any useful backup app

Many thanks in advance!

EDIT: Already rooted and everything seems to be fine
[Samsung Galaxy S Relay 4G] jwainner:
Having trouble getting superuser zip to intall

I keep getting signature verification failed. tried several places to get superuser zip; same error no matter where. Anyone had this issue?

Thx!
[Samsung Galaxy S Relay 4G] gtmaster303:
What's the point in doing steps 17 and onward?

EDIT: never mind

http://xdaforums.com/showpost.php?p=47052322&postcount=15

I will say though that my fresh phone worked fine without going past step 17.

Sent from my Galaxy S Relay
[Samsung Galaxy S Relay 4G] scopedial:
Good Root

Worked really well.

I was using adb on a mac though. Odin on my son's PC.

Also, I could not find the the recovery-from-boot or install-recovery files. Did something perform a clean-up

for me?
[Samsung Galaxy S Relay 4G] Balthasar85:
I followed the guide but I'm stuck at step 17.

I do not know what to do, I have root permissions but if I want to install a rom with CWM the result is an error.

Can you give me a hand?

Thank you very much.
[Samsung Galaxy S Relay 4G] Magamo:
Which image are you trying to install, which version of CWM are you using, and from what source?
[Samsung Galaxy S Relay 4G] Balthasar85:
I followed these steps:

I reboot the smartphone. I select "install zip from sdcard-> choose zip from sdcard" and select the room.

"CWM-based Recovery V6.0.1.2" I have tried to install the "cm-11-20140210-SNAPSHOT-M3-apexqtmo."

I do not use an external microSD
[Samsung Galaxy S Relay 4G] Magamo:
The copy of CWM you are using is far too old for the CM-11.0 builds. Please upgrade to either TWRP (posted in this forum), or grab the CWM image from the headers of the Carbon, FatToad and/or OmniToad threads.
[Samsung Galaxy S Relay 4G] Balthasar85:
I took the "CWM" from this forum, from this link:

http://xdaforums.com/attachment.php?attachmentid=1433905&d=1351304216
[Samsung Galaxy S Relay 4G] Magamo:
As I stated: Too old for CM-11.0 Please download a copy from one of the places I mentioned.
[Samsung Galaxy S Relay 4G] Balthasar85:
I have downloaded "apexq_recovery-10.2" but is .img. Odin wants .md5
[Samsung Galaxy S Relay 4G] Magamo:
Actually ODIN wants .tar.md5

The process to create one is simple if you have a Linux system or cygwin.

mv apexq_recovery-10.2.img recovery.img

tar -H ustar -c recovery.img > apexq_recovery-10.2.tar

md5sum apexq_recovery-10.2 >> apexq_recovery-10.2.tar

mv apexq_recovery-10.2.tar apexq_recovery-10.2.tar.md5
[Samsung Galaxy S Relay 4G] yohan4ws:
You're making this far too difficult on yourself.

Download and flash this in Odin (from step 5 in the OP)

http://xdaforums.com/attachment.php?attachmentid=1433905&d=1351304216

Boot the phone holding volume up and home button, you'll be in the older version of CWM, choose flash from zip file

Then flash this :

https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/apexq_recovery-10.2-347.zip

Once done you can flash any rom.
[Samsung Galaxy S Relay 4G] RodimusConvoy:
So basically this thread needs to be updated? Especially if that cwm file in the very first post is now no longer any good.

---------- Post added at 02:24 PM ---------- Previous post was at 02:22 PM ----------

Ah just saw this. So it is still good? Confused...lol
[Samsung Galaxy S Relay 4G] Magamo:
Yes, that linked updated CWM is still good. Updating this thread would probably be a good idea, and I will include an ODIN compatible tar.md5 version of TWRP when I make a release of 2.7.0.0 later this evening.
[Samsung Galaxy S Relay 4G] gehstock:
Need PIT File

ODIN Needs PIT File.
[Samsung Galaxy S Relay 4G] REV3NT3CH:
Currently no ODIN pit file exists for relay that I know of...what's the issue you are having
[Samsung Galaxy S Relay 4G] gehstock:
Root Done on other Computer
[Samsung Galaxy S Relay 4G] dosmastr:
Sorry for resurrecting an old thread but this is where the question belongs.

for the CWM recovery, I looked online for the one for this exact phone... couldn't find one,

Which recovery rom did you use?
[Samsung Galaxy S Relay 4G] falle21:
In the op you have the link to cmw to use via Odin.

In this thread (http://xdaforums.com/showthread.php?t=2528752

[ROM][5.0.2]FatToad by TeamApexQ development, release and discussion) you have a zip version.
[Samsung Galaxy S Relay 4G] craighaggart:
The root procedure worked fine for me. Thank you for doing it!

Unfortunately, I've created a pretty severe problem due to my own stupidity. I downloaded ROM Toolbox Pro and started freezing the apps I don't use and don't want (which is actually why I rooted the phone), but I was clearly not careful enough. I froze a critical app. Now the phone fails to complete its bootup. It's stuck at the screen that just says "Samsung" (gets kinda blurry, then clear, repeating slowly) with the blue LED lit, as well as the menu button backlight (lower left) and return arrow (lower right).

Does anyone have a suggestion for getting beyond this loop? My PC doesn't see the phone when I plug it into the USB port.

BTW, I know this is a "legacy" phone, but the one I rooted is actually brand new overstock just purchased to replace my old one. I love having a QWERTY keyboard. There just don't seem to be any other Android phones out there like the Relay SGH-T699. I hoped to keep it a long time, so I'm pretty bummed that I seem to have semi-bricked it.
[Samsung Galaxy S Relay 4G] phred14:
If nothing else, you could power it off, then reboot into recovery, and do a factory reset, perhaps firmware reload. Better starting over than a brick. You could also do a nandroid backup, but I don't know if it's possible to pick your way through a nandroid backup to avoid the specific problem you're having
[Samsung Galaxy S Relay 4G] craighaggart:
You're right, and although I had tried unsuccessfully to do a factory reboot last night, tonight it worked for me. The only thing I remember doing differently this time is clearing the Dalvik cache first.

For whatever reason, my phone is back to factory ROM now so I'm a happy camper. I'll redo the root procedure ... and I will be MUCH more careful about freezing apps this time! Lesson learned.

This forum is such a great resource. Thanks!
[Samsung Galaxy S Relay 4G] phred14:
I will say that I'm very happy running Kit-Kat from the CM11 nightlies. In addition to simply being a bit newer, it's still under some degree of active maintenance, so your getting at least some security fixes - for instance Stagefright and Heartbleed, to name two. If you're rooting your phone the installation instructions shouldn't be any problem.