yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Player 4.0, 5.0] TheRealBubba:
I had been wondering the same thing, Txordi, and I understood your question to refer to build time...
[Samsung Galaxy Player 4.0, 5.0] KOala888:
feels like a rocket when moving from PAC :)

Wysłane z mojego Nexus S za pomocą Tapatalk 4
[Samsung Galaxy Player 4.0, 5.0] iurnait:
The thing is, when compiling with Linaro, there are a whole bunch of errors to resolve. I had screwed things up a while back and I have to go find those changes for linaro to compile successfully agsin

Sent from my Samsung Galaxy S 5 running PAC-ROM.
[Samsung Galaxy Player 4.0, 5.0] dstarfire:
What happened to the option to force close the current app on long-press of the back button? It used to be in the 'developer options' section, but that section has disappeared. I've scoured the other settings sections and can't find that option anywhere.
[Nexus S Q&A, Help & Troubleshooting] br0adband:
So I'm getting back into the smartphone game again after being away awhile and I got a Nexus S today basically free of cost, practically brand new without a mark on it. Previous owner had it as a temporary phone during a warranty repair job of his primary phone and when he picked up the repaired one they said he could keep the Nexus S (wish I could get that lucky).

Anyway, while I know there are a ton of different ROMs available for this fantastic (albeit older) device, here's what I really want and I'm not sure it's possible. I've used CM in the past on several devices and one of the things that I always loved first and foremost was the ability to change tracks during music playback by holding the volume up/down button(s) (long press as a short press adjusts the volume). Now, I'm not a coder, not a developer, not a ROM builder, etc - I basically enjoy the work of others provided by their ROMs and so on.

This time out I've decided to try and stick with a pure stock ROM (which I'm not sure of at the moment, the NS has 4.1.2 on it but I plan to do testing with the factory 4.0.4 and 4.1.1 images as well just to see what's going on). Since those are factory images they're obviously not rooted so I can use WugFresh's Nexus Toolkit to handle the rooting for me.

So here's my question: is the ability to use the volume controls for changing tracks during music playback (with the screen off) a ROM-specific thing or is it kernel-specific - I've never been able to find an accurate answer to this question and I've asked it several times on different forums over the past 4+ years and still nothing of substance has ever been given as a response.

I know that some music players advertise they can do it (I've seen PowerAMP mentioned a few times but it just doesn't appear to work for me, ever, on any device). Again, I'd prefer to stay stock as much as possible, save for rooting the device, and then hopefully find out either a) I have to use a custom ROM with this feature enabled in it, or b) it's kernel related and I can just install a custom kernel which I can tolerate since it'll help on several aspects.

Sorry to make this so wordy but that's just how I am.

tl;dr version: I want to remain as stock as possible, with root only, and be able to change tracks during audio/music playback with the screen off by using the volume control buttons. Is it possible with just installing a custom kernel (given this Nexus S is bootloader unlocked) or not?

Hopefully someone can offer an answer that'll put a smile on my face but, if not that's fine too I suppose, I can just drop back to CM10 (4.1.1) stable and stick with it, not sure 4.1.2 really does all that much to improve things and 4.2.2 apparently is just too big for the limited 512MB of RAM in this NS to be smooth sailing.

Thanks...
[Nexus S Q&A, Help & Troubleshooting] Lukemolina:
This feature is build in with the app "Uber Music" its a setting called "Use volume buttons to control media"

It works great and its awesome if you don't mind putting in a few dollars to get the app

Cheers,

Luke
[Nexus S Q&A, Help & Troubleshooting] br0adband:
UberMusic looks nice, sure, but it doesn't do what I was hoping it would (and was suggested in the post above). The setting preference says "Enable headset controls" and I already have that ability: I have a cord from Apple earbuds where I removed/desoldered the original factory earbuds (because they're crap) and then replaced them with a pair of Koss IEMs that I like. So even though the cord looks like I'm using Apple earbuds I'm not.

Having said that, I can already control the Play (single click), Pause (single click), and Next track (double click) functionality, but obviously the dedicated volume buttons on the remote don't work for whatever reason. The Nexus S has a proper TRRS jack but it seems like no Android phone makers care enough to actually allow for such volume control through that jack. And the typical triple click Previous track functionality doesn't work either, sadly (and that's with any remote I've ever tried, even earbuds/IEMs that claim to work or are "designed for Android."

So again, I'm trying to control changing tracks (Next and Previous) with the volume rocker on the phone itself and when the screen is off, that's it. Since the phone is in my hand 99% of the time and my thumb is on the volume rocker, it's infinitely more efficient to change tracks with a slight movement of the thumb than trying to grasp the inline remote and double click or whatever.

Sure is odd why this question is so difficult to get an answer to over the years... :eek:
[Nexus S Q&A, Help & Troubleshooting] dpeeps74:
Most custom roms support this. It's not a kernel thing afaik. You may be able to find a mod to get it working on stock. It seems like I've seen it before in the ns4g themes & mods but I could be wrong.

As for triple press on the headphones, it's always worked for me with poweramp on multiple headphones.
[Verizon Samsung Galaxy Note II] BobbysWorld83:
I came from a 4.1.1 ROM and I backed up and formatted my card to Fat32,I'm now running this ROM and now my card isn't allowing me to restore anything from it, I can see it but can't do anything with it, no error message or anything.... I'm so confused... Please help ASAP:confused:
[Verizon Samsung Galaxy Note II] johnfranckiv:
If you switched to a 4.2.x rom you wont be able to restore anuthing due to where 4.2 roms store info... due to the multi user modes.
[Verizon Samsung Galaxy Note II] kintwofan:
So finish that explanation. OP check the cm10.1 thread. In the op is a downgrade zip. Flash that then restore your backup
[Verizon Samsung Galaxy Note II] BobbysWorld83:
But I want to us the pictures and stuff from my sd card on the 4.2.2 Rom, am I able to do that??
[Verizon Samsung Galaxy Note II] kintwofan:
I'm confused, what ROM are you on and what ROM, are you wanting to go to? as far as your pictures, all that is so on your sd card and will be if you flash that zip fin the cm10.1 thread. They are just stored in different directories. The 4.2 ROMs have different directories then 4.1to make multi user possible. So before going any further answer my last question and we'll get you straight.
[Verizon Samsung Galaxy Note II] BobbysWorld83:
Ok I came from a 4.1.1 Rom, now I'm using Liquid Smooth 2.3 which is a 4.2.2 Rom and I made sure my sd card was fat32 backed up everything... That's where I'm stuck
[AT&T Samsung Galaxy Note II] Astom22:
What's the best way to invert as many apps as possible while running 4.8?

I have tried to search on my phone, but haven't had much luck.

Sent using Galaxy Note 2 w/ CleanROM 4.8
[One (M7) Q&A, Help & Troubleshooting] mfadhil:
Hey guys

I just rooted my HTC One yesterday and installed a custom rom on it, all went well until my brain went stupid and formatted data, system, sdcard and i had no nandroid backup in place. I just upgraded from a HTC One X and from what i know, previously i could just flash CWM and mount usb and it'll go work normally. However, for my situation now, none of the recoveries actually allow me to mount usb.

Also, i'm on 1.29.404 and i can't find any RUUs that is the same as this. I also cant execute adb push for rom because my computer doesnt recognise my phone in adb devices. Can anyone help me out with this issue ? :(

cheers!
[One (M7) Q&A, Help & Troubleshooting] Shree.bhagwat:
Hi

Greetings,

Install HTC drivers for abd to recognize your phone, this will help you to atempt abd sideload and also fastboot commands

Flash the recovery againg

"fastboot flash recovery name-of-recovery-.img"

And try again by adb sideload this is your last option before flashing a ruu
[One (M7) Q&A, Help & Troubleshooting] ryan9316:
I'm in a similar boat, did a "format data" in TWRP and now I can't boot. I can access the phone via ADB tho. I'll let you know if I find a solution.
[One (M7) Q&A, Help & Troubleshooting] NoDroid4U:
Same thing here

I also did the same thing. However, I can't boot into recovery at all; It says its about to boot into recovery, then the phone just turns off. The only thing I can do is boot into the bootloader, and lock or unlock it. Right now, its unlocked. I've tried everything. I would love to just use an ruu exe., but the only one I've found isn't working for my phone for whatever reason. I kept getting error 132 signature error. The ruu I was using was "RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3" I was using a similar version ( I think it was 1.29.300 or something), and yes, I relocked my bootloader before using the ruu; If anyone knows of a different, newer version, or really, anything at all that can help, it would be greatly appreciated.
[One (M7) Q&A, Help & Troubleshooting] Shree.bhagwat:
Hi

Greetings,

Have to tried this code after installing the recovery

"fastboot erase cache" if not unlock your bootloader install recovery and try this code
[One (M7) Q&A, Help & Troubleshooting] NoDroid4U:
Hey thanks for replying; Unfourtently, even after reflashing twrp and clearing the cache, it still just shows the entering recovery mode and the restarts. In fact, now it is constantly restarting until I boot it into bootloader and power the system down that way. Any other suggestions?

Thanks
[One (M7) Q&A, Help & Troubleshooting] matt95:
that RUU won't work because you have to match your version-main to the RUU you are about to flash, if that version-main doesn't match than you will get that error 132 which is normal in your case... if you want to know which is your version main just type

fastboot getvar version-main
[One (M7) Q&A, Help & Troubleshooting] NoDroid4U:
Thanks; I've found the correct ruu, but now I have a new problem. As of right now its .zip and not .exe; I cant boot into recovery and adb isnt working either. Any suggestions for getting it on the phones memory, seeing as there is no sd card I can remove?
[One (M7) Q&A, Help & Troubleshooting] bradr00lzd00d1:
I had my phone booting the entering recovery screen for about half a sec and would always boot back into the OS so I installed TWRP through fastboot than went to factory reset in the hboot menu and it booted into recovery it worked for me but Idk if it will work for you
[One (M7) Q&A, Help & Troubleshooting] matt95:
i think you downloaded an OTA and not a RUU

---------- Post added at 09:05 AM ---------- Previous post was at 09:04 AM ----------

i won't suggest to hit that factory reset button! causa actually it soft-bricked some devices... you've been lucky
[One (M7) Q&A, Help & Troubleshooting] NoDroid4U:
No such luck; Is there anyway at all to push it to the internal memory using fastboot?
[One (M7) Q&A, Help & Troubleshooting] matt95:
as long as i know the only file that you can flash in that OTA is the firmware.zip that will update your bootloader but i'll do it after some more tries...

please paste here the output of

fastboot getvar all
[One (M7) Q&A, Help & Troubleshooting] ryan9316:
Have you tried "fastboot -w" this will factory reset your phone from fastboot. Then try re-flashing recovery again.
[One (M7) Q&A, Help & Troubleshooting] ratcom:
I've had this problem on the one x plus, what I did and please bear with me, it does work ;) Firstly flash cwm and clear cache, once you have done that you should be able to boot recovery. Once in cwm format everything including data! yep I said data! then reboot back to fastboot and flash TWRP and rewipe everything again (including data) then sideload or push your rom across to your phone.

Done this twice now on mine when I got bricked (for no reason!) I can only think the file system becomes corrupt somehow.
[One (M7) Q&A, Help & Troubleshooting] mfadhil:
alright guys, i solved the issue and my phone is back to normal !

to those guys still facing the issue, i suggest you flash the latest cwm then try using the sideload function > adb sideload <filename.zip>

mine came back to life after that, heh:D

cheers!
[One (M7) Q&A, Help & Troubleshooting] NoDroid4U:
Also fixed

Hey guys, thanks so much for everyones help last night. I also got mine all fixed and set away. For anyone interested, I used the ruu and steps in this thread: http://xdaforums.com/showthread.php?t=2250904

Thanks again to everyone for their help!
[Samsung Epic 4G Touch] montecristo1:
I recently purchased a foldable (portable) bluetooth keyboard for my Sprint Samsung Epic 4G Touch. This keyboard was purchased through ebay for $22.79. So I decided to share and write at a glance review for anyone needing/wanting a working portable bluetooth keyboard.

Features: (based on ebay's store's page)

Ideal for typing emails, testing.

Easy operation.

Good touch feeling and quiet keystrokes.

66 keys lay out.

Built-in rechargeable Li-ion battery.

Full size keyboard when unfold: 26cm x 9.5cm x 1cm - 10.24inch x 3.74inch x 0.39inch.

Compact when folded: 13.3cm x 9.5cm x 2.2cm - 5.24inch x 3.74inch x 0.87inch.

Specification: (based on ebay's store's page)

Interface: USB 1.1/ 2.0 /3.0.

Number keys: 66.

Modulation mode: 2.4G straight fh sequence.

Transmission power: Class2 level.

Standby current: ＜2mA.

Working current: ＜10mA.

Standards: bluetooth V1.0/ 2.0/ 3.0.

Standby time: 60 days.

Work time: 8 hours per day sustainable 30 days.

Compatible With: (based on ebay's store's page)

Smartphones.

Nokia symbian S60 V3, V5 and later.

Windows mobile 5.0, 6.0, 6.1, 6.5 and later.

iPad, iPad2, Touch, iPhone 3G 4G 4S.

Android 2.3.3 and later OS smartphone.

Sony PS3 game player.

Personal computer PC (Windows, Mac OS) and the home theater PC(HTPC) UMPC (Android , Windows OS, to be customized).

My smartphone:

Sprint Samsung Epic 4G Touch (SPH-D710)

Build: FI27

Stock TW (ICS) 4.0.4

Pros: fits in my pocket, can actually type on it, battery seems to last (3 days so far without charging and accidentally left it on for one day), light and sturdy, no need to buy batteries for it, all keys work on my android, easily recognized my smartphone out from the box, off and on switch on the top- you can easily turn it off while it is folded...

Cons: the stand that comes with this keyboard does not have a slot to place it inside the keyboard like Verbatim's bluetooth keyboard- so you will have to carry it if you need it, the keys are rubber/silicone and not plastic (i prefer plastic), the locking switch does not lock the keyboard easily- had to use my car keys to switch the keyboard to lock, the space bar is divided into two- my thumb sometimes hits between, takes some time to get use to the layout if you frequent use a full keyboard- shift button is on the bottom on right and bottom left...

I bought my keyboard from

shcfstore

You can check this seller too:

http://www.ebay.com/itm/Portable-Fo...ocking_Stations_Keyboards&hash=item3a7eed6d56

Hope this helped.
[Samsung Epic 4G Touch] jahjah440:
Nice review, although someone should make something like this for the Epic:
[Samsung Epic 4G Touch] jt323bd:
Just bought one. Hoping it's pretty easy to type on.
[T-Mobile Samsung Galaxy S 4] Orical:
I rooted my device tonight after beating my head over the forums on all the horror stories people are posting and having a good standing history here at XDA with all the devices I've rooted in the past without so much as a blank screen.

Anyways, I ran root and got everything set up and noticed my connection took a nasty dive. I had incredible 4G signal before root and now it bounces back and forth between edge and 4G.

I can't see why root would effect signal but theres gotta be a way to correct it.
[Galaxy S 4 General] blackscourge:
A big thanks to the developer for this flawless root method for my I9500 on UBUAMDK.

The Cofface method did install the recovery but did not fully root.

This roots perfectly: http://xdaforums.com/showpost.php?p=41042903&postcount=20&nocache=1&z=5328519083559513
[Galaxy S 4 General] cmd512:
Curious though:

XXUAMDK: 526212

UBUAMDK: 534999

So yes, while this method will work, UBUAMDK still looks a newer kernel based on the changelist. No idea what was changed (as usual), but at this early stage, they're probably doing quite a bit of bug fixes.

I'll ask Ivan in his thread, thanks for the heads up.
[Galaxy S 4 General] bala_gamer:
May be they are just mentioning the change log in kernel and changes are made on both kernel and rom sides.

But whatever, just flashed this custom kernel and it didn't brought back the red tint issue (for me), so it should be as new as Sammy since it uses upd1 sources
[Galaxy S 4 General] guyluvsgals:
It Works.....Titanium Backup works:good::victory::o
[Galaxy S 4 General] jaidev.s:
Does this increase binary flash count ?
[Galaxy S 4 General] bala_gamer:
if im not wrong the counter is displayed on the download mode screen on s3, but i cant see the download counter screen anywhere in s4, am i missing something?
[Galaxy S 4 General] bungadudu:
It is hidden. Just use triangleaway...
[Galaxy S 4 General] hazri1974:
Triangle away support s4 i9500 as of now?...
[Galaxy S 4 General] hassan89:
Will this work on XXUAMDE?
[Galaxy S 4 General] Riki277:
Can anyone confirm that the root works on or is there any root that works?

Baseband version: I9500UBUAMDK

Kernel version: 3.4.5-534999

Sorry, I'm new to this rooting stuff, and thanks!
[Galaxy S 4 General] tgardner:
Yes, I can confirm it.
[Galaxy S 4 General] garofuentes:
How can I get CMW in my rooted S4

This is great! I was able to flash my S4 and now it's rooted. Thanks!!

Does anyone know how can I install cmw in my rooted S4 I9500UBUAMDK?

Thanks!
[Galaxy S 4 General] HS™:
http://xdaforums.com/showthread.php?t=2262110

[GT-i9500] cofface CWM 6.0.3.2 RECOVERY & ROOT (EASY and WORKING) New update

It works I have tested on same firmware
[Galaxy S 4 General] garofuentes:
Thanks, I'll try it right now!
[Galaxy S 4 General] HS™:
http://xdaforums.com/showthread.php?t=2276803&highlight=rooting+and+recovery

This method works for sure
[MDA II, XDA II, 2060 ROM Development] beljames:
As a regular contributor to various motor car forums I am always amazed at how idiots destroy perfectly serviceable cars in an attempt to 'improve' them. Anyway - today, I am one of those idiots.

I recently purchased a QTEK 2020 which I got a bit cheap on account of it not having 'iMate' written on it. Before I get really into it and put software and stuff on it, I'd like to upgrade my ROM from 1.66 to 1.72, which I have found on this site. Do I have to go through all of the xda2nbftool stuff (which I more or less understand)? Presumably yes, to change the Operator (only?). I'm quite happy for the machine to think that it is an iMate, but presumably this does not work!

I am happy with my machine. It hasn't crashed yet. But it annoys me that it might not be quite as good as yours...

(I so feel like one of those people who wants to remove his cylinder head and replace it with pineapple's to make the engine run sweeter)
[MDA II, XDA II, 2060 ROM Development] Rudegar:
i dont really understand what you are asking

are you asking

1 about changing operator and so sim locking ?

2 are you asking if you need the pretty manual xda2nbftool way to upgrade xda2's ?

3 are you asking if it will work upgrading to 1.72 ?

1 you can sim unlock your device without changing rom

a rom never require you to use a special operator but the preset settings will be the operators who put out the rom

2 yes currently it's the only way with time people are likely to make it a bit more gui like the xdatools for xda1

3 it should work but some people are reporting issues with it or maybe that was the beta of 1.72

read about the exp of others in the posts about 1.72
[MDA II, XDA II, 2060 ROM Development] beljames:
Sorry - it's a simple question.

If I had an iMate I could just use the RUXXX upgrade without any fuss to upgrade to 1.72

However, I have a QTEK 2020. I guess therefore I have to use xda2nbftool to modify the operator name to QTEK - otherwise it will not work (despite the 2 devices being identical). I do not want to unlock a SIM or anything else (it is unlocked by default).

Just looking for confirmation of the above paragraph!

I read about the experience of others using the 'official' 1.72 and it seems okay (better battery life etc.)

Cheers
[MDA II, XDA II, 2060 ROM Development] Rudegar:
there are 2 errors i think which stop people from just flashing their xda2 flavor with any rom update in the form of an exe file

1 is country code error if the rom is released in one country it often have a block which will stop people from upgrading their another country xda2 with it, not sure why they do that

2 maybe a form of device block so you dont upgrade your qtek with the imate

i'm sure if you had an imate and the country code dident differ you would be able to upgrade without using xda2nbftool

with time a GUI tool like xdatools for xda1 will come and you'll be able to get around all these blocks without having to type

and such
[MDA II, XDA II, 2060 ROM Development] wfberg:
If you want to upgrade your Qtek to Imate's 1.72 ROM, yes, you need to do all that stuff.

It's actually quite simple, the description on http://wiki.xda-developers.com/wiki/HimalayaRomFlashing is full, accurate, and is actually suited to Qtek owners without changing a single instruction.

I flashed my device (though on the first go it ended up in a dead-ish screen and I had to re-flash) and it works swimmingly.

However, you might get somewhat nervous encountering such dead-ish screens; and for good reason, flashing is dangerous after all.

Perhaps it's best to wait for a Qtek upgrade, they seem to be holding back a bit, so perhaps they're waiting to integrate WM2003 Second Edition, which should be a much larger upgrade. Also, you'll still be covered by warrantee.

If you're having specific problems with your 1.6x ROM, it could conceivably be a good idea to upgrade to the iMate ROM (using the instructions on the wiki), but if you're not having any problems, or problems that also occur in 1.72, or which are a result of 3rd party software you're using; don't bother.
[MDA II, XDA II, 2060 ROM Development] beljames:
You are right that QTEK seem to be a little slow in releasing anything. In fact I can't find any detailed 'official' support on QTEK outside the pages of this forum. Their website appears to be in swedish and is of very little use!

The QTEKCorporation website doesn't even list the 2020! Strange, as I understand that HTC own QTEK.

Most vendors (Expansys for example) list the 2020 as 'discontinued' (which is how I managed to negotiate a big discount!)

I tried to gatecrash club-iMate but they didn't like my IMEI number, and when I asked why not they said that they don't support my device.

I don't really care (assuming that my machine never has a problem...) and is it seems to do everything I want it to, I'll wait before updating the ROM. Maybe something will come from QTEK eventually - although I am not sure from where!!

Cheers
[MDA II, XDA II, 2060 ROM Development] Rudegar:
well qtek were the first ones out with 1.66 it came on my device before most people had gotten 1.60