yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Gear] Skeleton:
That is good news then. If I could ask you something, before I begin the root process ...

If I root my phone:

- do I have to reinstall all my apps?

- do all loose all my settings (emails accounts, etc)?

How do I root the phone?
[Samsung Galaxy Gear] le3ky:
Go to the Note 3 section on xda. They'll probably have a sticky explaining the best way :p
[Samsung Galaxy Gear] Bladder61:
I had a similar issue with my S4. Samsung music stayed persistant in my notifications bar running in the background. It was also on my lockscreen as a widget. I was able to go into settings/app manager and Turn Off the app. I did a reboot of the phone and all is well. I have since gone back in and turned the app back on and it does not repeat the errant behavior.
[Samsung Galaxy Gear] cydonian66:
It's really weird that whenever you connect your phone to the Gear it starts the Music app, mine hasn't done that ... yet. However, as far as controlling music, mine has worked perfectly fine with Google Music (or Play Music or whatever it's called now). Also, volume up and down should work, however, the first time after you connect your Gear, if you try turning up the volume on the phone, an alert will pop up saying something like "Are you sure you want to increase volume? Loud music can be damaging" (forgive my inaccuracy), you have to press OK on the phone first, then it will work fine. It's really irritating, but better than nothing.

I hope that made sense?
[Samsung Galaxy Gear] Skeleton:
Thanks to all for your comments and suggestions.

What I have deduced is:

- Samsung Music consists of two modules, but the user is aware of only one. The front end is what the user interacts with; it is essentially a file manager. The back end is the audio processor. In my case, there is a disconnect between the two. I can enter the front end and see the list of song files, but I can not play any song which is because the back end is not able to be accessed.

- There is evidence of disconnect between front end and back end. In the front end, I can enter [Settings ^ Play speed]; what I should see is a sliding scale from 0.5x to 2.0x. In my case, the labels are missing when moving the slide bar, and the slide bar does not remember my change rather it remains at 10% setting. I suspect the speed setting is stored in the back end, for which the front end (in settings) can not access the variable's parameter, nor can it later update the value.

- The back end program of Music does work for me. This is proven by selecting a song file in "My Files" explorer, then choosing "Sound player" from the context menu. For me, the song file then successfully plays. I suspect the player is the back end of Music because the icon in the context menu is the same (blue triangle with green music note).

- When Gear is making a connection with Note, it asks Note for the name of default media player. This causes Note to open momentarily the Samsung Music player in silent mode. Note then closes Music as experienced by most users, but in my case Music stays open because of a bug on my system/configuration.

Why is this happening?

- Some writers elsewhere wrote about the interconnection between many Samsung apps because of their interdependence on TouchWiz. Perhaps Music is one such program. Maybe something (other app or my configuration) has triggered Music to break for me.

- At this point I am left suspecting another user app has caused Samsung Music to break between the front and back end. Note, this problem has only arisen in the past month, but in that time I have installed a few more apps and the previous apps have auto-updated themselves. So, I am now left to uninstalling them and testing their effect.
[Samsung Galaxy Gear] Skeleton:
Problem SOLVED

Alas - Problem SOLVED.

It is frequently suggested that Music Player can be repaired by flushing the cache in "Music". In my case, this never solved my problem.

However, today I discovered another cache that can also contribute to the problem, and thus offer a solution.

The following worked for me ...

Step 1

- Settings ^ Application Manager

- App = "Media Storage"

- Action = "Clear data"

Step 2

- Samsung Music

- All song files are removed.

Step 3

- Scan Media

Step 4

- Samsung Music

- All song files are relisted.

- All song files now play. YEAH
[Android Q&A, Help & Troubleshooting] DanielGrady:
Im not really a noobie at this I am a phone tech and know a little about phones

I down loaded the mk3 deodex rom I'm not having any bad issues with the rom I've done everything

right. The only problem I'm having is the hotspot mod I've downloaded both odex

and deodex files my phone doesn't take a SIM card its cdma of course because

its sprint. Is there another hack/mod or anything that can fix my issue. I've downloaded into system and on sd

but still same problem. If y'all can find it and fix it please email me dannygrady.dg@gmail. Com

Thanks Daniel
[JASJAR, XDA Exec, MDA Pro General] patching:
Help - I have both a Qtek 9090 and a Vodafone V1620 which I use a Jabra BT250V Bluetooth headset with. I have been using all day and then all of a sudden the Bluetooth will disconnect and I can not Longer connect my headset to the PDA.

I have tried a soft reset, unpairing the headset and recreating it but nothing seems to work.

Also I have a collegue who also is having a problem where he can hear the person on the phone but they cannot hear him.

here is the Device information for both devices

Vodafone V1620

Rom Version: 1.31.00 WWE

Rom Date: 12/13/04

Radio Version: 1.12.00

Protocol Version: 1337.42

ExtRom Version: 1.31.175 WWE

Qtek 9090

Rom Version: 1.40.00 WWE

Rom Date: 03/10/05

Radio Version: 1.12.00

Protocol Version: 1337.42

ExtRom Version: 1.40.147 WWE

Does anybody have any ideas if this is the PDA's or the headsets
[JASJAR, XDA Exec, MDA Pro General] chris_khho:
I just recently bought the Jabra BT250v.

The experience is that it is not as good as the previous model BT250 / BT258.

Everytime after softreset, the connection will disconect even the BT icon (not headset icon) is there.

You then have to disable the bluetooth connection and enable it to get the connection back....(softreset is not required though cause u have already done...)

Hope this help..

Cheers,
[JASJAR, XDA Exec, MDA Pro General] Jorgee:
Just to clarify, is your device (v1620) a Universal? Isn't it supposed to be the v1640? Here in spain it's called the v1640 but not sure from where you are.

If it is a Universal, pls post your POWER settings when running on Battery.
[JASJAR, XDA Exec, MDA Pro General] Kassad:
I have a MDA Pro with a benq-siemens BT headset and am having the same problems. My MDA seems to switch off BT after a call.

my power settings are that the phone shuts off when not used for 3 minutes. Does anybody have a solution?
[LG Optimus L9 P760, P765, P768, P769] ajay74:
Dear friend

First of all i make you clear that this is not my work I signed the app. Using cert signer and made it flashable zip so that you can install MX player using CWM,

The advantage is that you need not to reinstall the app every time after resetting your phone

Like system app. It will remain in your phone after wiping and resetting your phone too

If you ain't like this app then you can remove it by using Root App Remover which is available in playstore

The link to flashable MX player is

https://app.box.com/s/i357orilspobxqigqhb4

Thanks

Have a good day
[LG Optimus L9 P760, P765, P768, P769] Techgod:
LOL...u can always move any app in system using LINK2SD !!!...no need of flashing anything.
[LG Optimus L9 P760, P765, P768, P769] ajay74:
Dear friend

I too know you can convert it as system app using link2sd. Infact i am too using it to link my app to my 2nd partition of sd card

I posted it just to have another option for making any app as system app

LOL
[LG Optimus L9 P760, P765, P768, P769] AndreaL9:
Without even using Link2SD, you can put it as simply copying the app in system / app and set permissions in

r-w

r

r

And reboot device

Inviato dal mio P760 utilizzando Tapatalk
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] frosty37:
I updated from cyanogenmod 10.1.3 with full wipe, cleared cache and dalvik cache. I can text for thr first hour or so then messages will not send. I have tried using different Apn's but nothing. Any help is much appreciated.
[Nexus 7 Q&A, Help & Troubleshooting] crietmann:
I'm in a bit of a hard place - I'd previously unlocked, loaded TWRP and rooted my Gen1 Nexus 7. I can no longer boot into recovery and get the " no command" message. This also gets in the way of the KitKat upgrade process. With all that said, the tablet works fine under 4.3 stock.

Here's the rub - one morning stumbling out of bed I stepped into a loop of USB cable that was charging the Nexus, yanked the cable and tablet violently enough to damage the USB port. Data communications or charging no longer work via USB. Fortunately I can still charge via dock and pogo pins.

Besides buying a new tablet or replacing the ports (about $60 on eBay) can anyone suggest another method to recover or load a bootloader?
[Nexus 7 Q&A, Help & Troubleshooting] RootTheMachine:
Pretty sure you mean recovery, not bootloader.

The OS still works right? Just flash a recovery using an app like flashify and you're good to go.
[Nexus 7 Q&A, Help & Troubleshooting] bftb0:
Not sure what flashing a bootloader has to do with this.

If your bootloader is locked, you can't "flash an unlocked one"*, but even if you could, that wouldn't help as you still would not have use of fastboot via the USB to do a "fastboot flash of a recovery". And fastboot only speaks to the tablet when the bootloader is running, not when a kernel is loaded (recovery or regular boot).

To get a custom recovery re-installed, you can do that by using "dd" to overwrite the recovery partition from ANY root-privileged shell (either a custom recovery or a rooted ROM). So there's the rub: you need something running with root privilege.

If that is not the case (rooted ROM) you need to either find a "root exploit" for your current ROM, or get your USB plug repaired. You could run ADB over your WiFi network (instead of via the USB cable) or just use a terminal emulator app to run exploit codes.

I haven't been keeping up with things, but the "motochopper" exploit was exactly that - a method of rooting a stock ROM that avoids fooling with fastboot or the lock state of the bootloader. But that was a while ago, and I don't know whether it still works against newer stock ROMs. (Besides, you neglected to even mention what is currently on your tablet)

Good luck.

*actually you can, but only if you have a rooted ROM or custom recovery running AND you previously captured a raw dump of a certain partition while the bootloader was in an unlocked state (bootloader is encrypted on a per-tablet basis). I think osm0sis disclosed this method a long long time ago.
[Nexus 7 Q&A, Help & Troubleshooting] crietmann:
I apologize for my probable misuse of terms - in short (unless I can find a root exploit) a new Nexus 7 may be on my XMas list. I greatly appreciate your input.
[Nexus S Android Development] tchaari:
SlimRoms is a custom android operating system. The main goal is to offer users a slimmed down but still feature rich alternative to other android operating systems.

The entire SlimTeam work together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.

All of the sources can be publicly viewed through GitHub and you can stop by the public Gerrit to submit patches of any type.

SlimKat is the project name for SlimRoms based on Android 4.4 and offers the following original features:

The Real Dark Slim

Full system-wide dark interfaces. - If you like it smooth and classy.

Custom Shortcuts. Everywhere.

Hardware keys, Navigation Ring, Navigation Bar, Lockscreen, Tiles, Notifications etc. - We've got you covered.

System-Wide Keyboard Controls

Rotation, cursor control, optional emoticions, etc. - You'll be tapping away to your heart's content.

SlimCenter

Downloads, contact information, system app removal. - More fun than you can shake a stick at.

Camera Features

Trueview, Smart Capture. - Capture life moments with ease.

Important links:

slimroms.net - The official webpage where you find everything you need to know about SlimRoms.

Downloads - Download the rom, gapps and other addons.

Installation instructions - Follow these steps to the letter if you're about to install SlimRoms on your device.

Latest Changelog - Read here if you want information on changes in latest build.

FAQ - The most frequent asked questions with answers.

Kernel Source - The source of your device's kernel.

Get in touch! - Contact SlimRoms at these places if you have questions, requests or feedback.

Google+

Twitter

Facebook

Forum

Disclaimer: SlimRoms are not responsible for any damages to your device.
[Nexus S Android Development] tchaari:
So time for a first slim kitkat taste. The first beta will be available in few minutes on the slimroms.net

The screenshots in the OP aren't up to date yet :)

Big big thanks to:

- cn.fyodor, steve676 and cyanogenmod team for the sources.

- Derteufel for the kernel

- adm1jtg for the long hours of testing
[Nexus S Android Development] nexususer:
geat !!

still no download link !! :(
[Nexus S Android Development] smit.sanghavi:
Patience my friend, patience :)
[Nexus S Android Development] Setting.Out:
Can you provide a link to patience?.. I always seem to run out.. ;)
[Nexus S Android Development] tchaari:
Sorry guys, there was an error in the build script and it compiled from 4.3 sources. The 4.4 beta will be available in few hours :)
[Nexus S Android Development] Setting.Out:
Link is up!!.. or is that the wrong 4.3 that I downloaded?

__________________________________________________________________________________________________

Well, it looks like kitkat.. :) is fast like kitkat.. :) Hmm.. probably not 4.3.. :)

Booted up, smooth and fast.. so far all settings seem to work, no app issues.. Very nice work..
[Nexus S Android Development] Setting.Out:
Playstore is a little crashy... if I try to download/install more than 1-2 apps at a time it crashes..
[Nexus S Android Development] tchaari:
Yes it is the right link. Builds are up :)
[Nexus S Android Development] marfillaster:
Request: Please add GEL as an add-on also the google keyboard. Thanks. Really smooth rom.:good:
[Nexus S Android Development] Viadanna:
Good job. I did a manual build last night but seems the same as the one you uploaded.

I see it's also missing the widget enable control in Settings.

I've got Play store crashing but must be related to the change in DPI, as I'm dirty flashing from my unofficial build that had default DPI.
[Nexus S Android Development] smit.sanghavi:
I think GEL won't be coming to SlimKat until Google releases a working official APK in the Play Store. Google is probably holding off until they find it stable enough.
[Nexus S Android Development] coolek33:
Installed with CWM 6.0.4.3, TWRP 2.6.3.0 won't work. And it seems faster and smoother than build 2. Thanks for awesome work.
[Nexus S Android Development] adm1jtg:
For all those having playstore issues are you using slimgapps beta 1? Are you using ART?

http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/978-addons4-4/downloads
[Nexus S Android Development] marfillaster:
I download the full slimkat gapps instead which contains GEL. It's running smooth. My only concern is location service sucking up battery even in battery saving mode.
[Nexus S Android Development] skorpion1977:
Hello Folks,

can it be, that Widgets don't work on lock Screen? At least I can't find the Options in the security menu.

regards, skorpion
[Nexus S Android Development] rho57:
Security>Lockscreen widgets
[Nexus S Android Development] coolek33:
Yeah it's not here yet. Or we're both blind.
[Nexus S Android Development] skorpion1977:
As I said, I can't find it in the Security Menu. It isn't there in SlimKat.

skorpion
[Nexus S Android Development] Viadanna:
Oh, lockscreen widgets are disabled for low memory devices, which includes the Nexus S. I believe at least some the settings should be shown, such as to disable maximized widgets as these are disabled.

To enable widgets in lockscreen just change ro.config.low_ram=true to false in /system/build.prop and reboot using your preferred method. This has the collateral effect of enabling Ok, Google hotword. Might make the device slower thou.
[Nexus S Android Development] devil188:
Get NSTools from Market.

Then change your I/O scheduler to deadline, if not yet done.

Also change your governor (CPU) to smartassv2 :)
[Nexus S Android Development] giorgos3924:
i tried to install slimkat 4.4 and i get error for recovery.

i tried to install recovery and finally i lost root. i succeeded install android 4.4 with 6.0.4.3 recovery and finally i am without root access.

how can i root it again?

will i lose all data?

i am running slimkat 4.4.2 beta 2.3 weekly-2387
[Nexus S Android Development] anshumandash:
You need to enable root in developer options within slimkat.

Sent from my Nexus 4
[Nexus S Android Development] giorgos3924:
i download root checker from market

and i get message: "Sorry this device does not have proper root access"

i tried to install touch recovery because now i have non touch version and it says for root access.

in developer option i have already enable, in "Root access", the "Apps and ADB" option.
[Nexus S Android Development] anshumandash:
Root is not enabled by default in slimkat and you need to enable it in developer options. If you run root checker without enabling root, you will get error. Also I am not sure why do you need root to flash touch recovery? You can boot into recovery and flash anything. You don't need root for that.
[Nexus S Android Development] giorgos3924:
i tried to install touch recovery with "Recovery tools" and get error for not rooting device.

and i download root checher from market to check the root status and get error too.

now i check the development option and i have already check in root acces the "apps and adb" option
[Nexus S Android Development] smit.sanghavi:
Try to dirty flash the ROM again.

For installing touch recovery, use a flashable zip. You'll find it in a thread in the development thread.

Here you go : http://xdaforums.com/showthread.php?t=2032337
[Nexus S Android Development] giorgos3924:
dirty flash worked fine! device is rooted.

now for cwm 6.0.4.3 touch version flashable zip is ok?

just flashing like rom?
[Nexus S Android Development] coolek33:
Just flash zip. U can get CWM from post #93
[Nexus S Android Development] seibott:
Can somebody help me with this error please? Installed super user, restarted my phone and still no luck. The App is even allowed by the ROM's default root permission thing.

Sent from my Nexus S
[Nexus S Android Development] coolek33:
First enable root permission for apps and adb in dev settings. If U have problems flash super SU.
[Nexus S Android Development] seibott:
Thank you. I have tried doing what you said and it still shows the same error. This screenshot might clarify what I'm trying to tell. Thank you.

Sent from my Nexus S
[Nexus S Android Development] coolek33:
Ok. But this is super user from slim rom not the superSU. Try it.
[Nexus S Android Development] smit.sanghavi:
Yes. Just like a regular old-fashioned flash. :p

---------- Post added at 11:25 PM ---------- Previous post was at 11:21 PM ----------

What do you mean by "installed superuser"?

Isn't it already present in the ROM. :what:
[Nexus S Android Development] giorgos3924:
thank you very much guys!

There's some bugs: When i take a photo with stock camera app and when i go to view the photo (right up corner - or slide to left from right) and with menu soft key open the menu and try to delete it the "delete" option does not working. Like dead digitizer!

But in galery app the delete option work fine.
[Nexus S Android Development] skinner12:
Hi, is it possible to change kernel? I mean, which kernel works better?

Also, I didn't find where to set to wake up phone with volume botton, is not yet possible?

Thanks

Inviato dal mio Nexus S utilizzando Tapatalk
[Nexus S Android Development] giorgos3924:
where's the theme chooser?
[Nexus S Android Development] coolek33:
It's in future plans.
[Nexus S Android Development] ui10:
Photosphere

Is someone succed to install PhotoSphere ?

The ad-on photosphere is not for the Nexus S.
[Nexus S Android Development] coolek33:
It's for mako, Hammerhead and Flo only ATM.
[Nexus S Android Development] fredpel:
I'm using Google Launcher (the one with Google Now on the leftmost screen), but on every reboot/restart it forgets to show on the homescreens the icons of the apps on the external memory.

Is it a known problem?
[Nexus S Android Development] ohitspat:
Whenever I input APN settings for Rogers in 2.3 it never saves and I don't get 3G/H above my signal bars. Hopefully a fix happens soon other than that no complaints about the ROM!
[Nexus S Android Development] VerminX:
Great ROM, it's my daily driver now.

My only wish now is compressed memory support since our aging device lacks memory so badly. What's a good compatible kernel with these options:

Touchwake

Volts unlocked and 1200 ; 1400 speeds

Bln

Thanks for your great work!

.....

Ok to answer my own question Devil Kernal (the latest) works awesome with this ROM!

Make sure to use devilkernal control app for best results.

This phone even old is getting better and better with every update since I bought it.

Thx again devs!!
[Nexus S Android Development] asmOne:
it is working to me.

---------- Post added at 12:42 AM ---------- Previous post was at 12:40 AM ----------

I guess volume button wakup not possible yet.

---------- Post added at 12:44 AM ---------- Previous post was at 12:42 AM ----------

what for themes Try the real dark slim in Settings/advanced settings
[Nexus S Android Development] coolek33:
Volume rocker awake is in display settings on the bottom.
[Nexus S Android Development] giorgos3924:
how can I change the resolution?
[Nexus S Android Development] skinner12:
In build.prop, based it's 182..
[Nexus S Android Development] khimois:
When do you think the next build will be up? Hehe, wanna try SlimKat. :)
[Nexus S Android Development] asmOne:
Bug report 2

Data connect status isn't showing..
[Nexus S Android Development] smit.sanghavi:
You mean the small arrows on the signal bars?

They were removed from KitKat in accordance with 'Project Svelte' by Google. They had to redraw the status bar every time to show those arrows and that used processor time and memory.

They have now been moved to quick settings.

---------- Post added at 11:51 AM ---------- Previous post was at 11:44 AM ----------

New build is up... :)

http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/636-crespo
[Nexus S Android Development] seibott:
It is already pre installed and as shown in the screenshot though it allows root access to titanium backup, the app doesn't work so it makes no sense. Had to flash super user again.

Sent from my Nexus S

---------- Post added at 01:36 PM ---------- Previous post was at 01:34 PM ----------

Sorry for the double post.

It is already pre installed and as shown in the screenshot though it allows root access to titanium backup, the app doesn't work so it makes no sense. Had to flash super user again.

Sent from my Nexus S
[Nexus S Android Development] giorgos3924:
some button dont work and i think it's resolution problem
[Nexus S Android Development] smit.sanghavi:
I got your point. Some apps behave a little abnormally with the in-built Superuser

I had the same issue with 'Nandroid Manager' to restore backups.

Steps I did:

1) Flash Superuser

2) Restore backup

3) Removed root

4) Dirty flash the ROM to get in-built Superuser back
[Nexus S Android Development] asmOne:
yes exactly I said that little arrows.. :good: