Related
I honestly thought that I would find an answer for this but apparently I truly am "special" or weird in this one. I am brand new to the world of rooting and roms and currently have the latest version of Cleangb running on my epic. Fantastic rom and a giant thanks to any and all involved. One thing that has always driven me crazy about the epic is whenever you lose your signal or regain your signal there is an audible sound. I am sure getting rid of it is as easy as just deleting the audio file for it but I have done some searching through the root directory and cannot find the audio file for it. Does anyone know the location of this file? Also is it safe to delete or does one need to replace it with a blank audio file?
danipoak said:
I honestly thought that I would find an answer for this but apparently I truly am "special" or weird in this one. I am brand new to the world of rooting and roms and currently have the latest version of Cleangb running on my epic. Fantastic rom and a giant thanks to any and all involved. One thing that has always driven me crazy about the epic is whenever you lose your signal or regain your signal there is an audible sound. I am sure getting rid of it is as easy as just deleting the audio file for it but I have done some searching through the root directory and cannot find the audio file for it. Does anyone know the location of this file? Also is it safe to delete or does one need to replace it with a blank audio file?
Click to expand...
Click to collapse
I can tell you that the tone is not present on cm7 & 9. But I am have never been able to find where its stored.
Sent from my SPH-D700 using xda premium
/system/media/audio/ui the file should be in here. i am on cm9 so i cant tell you the exact name of file. i dont like sounds other than ringtone, notification and alarm so i delete the entire ui folder and all unused ringtones etc.
s89281b said:
/system/media/audio/ui the file should be in here. i am on cm9 so i cant tell you the exact name of file. i dont like sounds other than ringtone, notification and alarm so i delete the entire ui folder and all unused ringtones etc.
Click to expand...
Click to collapse
I took a look at the CleanGB zip and searched the ui folder and found no sounds there...And an extensive Google search netted the same results. Seems the question has been asked a bunch of times across multiple forums and devices, but no has responded with a clear answer. Maybe one of our devs out here can find the solution. Although I am really starting to think it is possibly built into the ROM framework, instead of just a notification sound...
It has been attempted by our best devs. It is cooked into the TW ROM to where it has never been found.
Sent from my SPH-D700 using xda premium
I will try just moving the entire ui folder out and see if that does anything and report back. If that doesn't work then yeah hopefully one of the devs can clarify if it is built into the rom. Thanks for the posts everyone.
And then throw on an AOSP ROM like CM7 and problem solved.
Sent from my SPH-D700 using xda premium
kennyglass123 said:
And then throw on an AOSP ROM like CM7 and problem solved.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
I would like to try CM7 at some point but I am a little apprehensive about it at the moment. What led me to root and put a new rom on was how disgusted I was with the constant freezing of stock. CleanGB appeared to look the most stable of any out there. Since I use easytether a lot I liked that the mobile hotspot was also unlocked. Correct me if I am wrong but CM7 does have some tethering issues does it not? It just seemed like there were a few more issues associated with it than CleanGB at this point. I am open to convincing though!
kennyglass123 said:
It has been attempted by our best devs. It is cooked into the TW ROM to where it has never been found.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Somehow I missed your reply. That clear it up quite a bit though. My only question though is CleanGB is based of of GB and not TW so does that mean he just cooked it into the GB rom as well?
danipoak said:
Somehow I missed your reply. That clear it up quite a bit though. My only question though is CleanGB is based of of GB and not TW so does that mean he just cooked it into the GB rom as well?
Click to expand...
Click to collapse
CleanGB is based off TW stock. It's not AOSP Gingerbread, it just has the TW apps removed.
Sent from my SPH-D700 using Tapatalk
I have no problem using wifi tether with CM7 with 4G or the native tether works well with 3G.
Sent from my SPH-D700 using xda premium
Since this is my first time posting I just wanted to say thank you to everyone that has helped make this forum as good as it is, I have learned so much about my phone from here.
Now my issue at hand is that my camera on my GSM galaxy nexus does not work, since upgrading to jelly bean 4.2 I can't seem to get it to work, but my gallery works just fine, now I have tried multiple Roms, and wiped my phone many times, have also tried with twrp and cwm neither of which work, I have also searched every where on the internet to no avail, is there anyone with any insight as to how I can fix this?
You changed ROMs but did you change GAPPS?
063_XOBX said:
You changed ROMs but did you change GAPPS?
Click to expand...
Click to collapse
I thought I have tried a few different ones, I guess I am not really sure I know I have tried just the camera and gallery zip from more than one place, and I am running the cataclysm rom which doesn't say you need GAPPS sperate
Just wanted to clarify I just tried installing 4.2 GAPPS and it's still doing the same thing any other ideas
Sent from my Galaxy Nexus using xda app-developers app
No one else has run into this???
Sent from my Galaxy Nexus using xda app-developers app
CM, AOSP, AOKP, 4.1.2 Bluetooth A2DP Solved?
This worked for me, so I figured I'd share.
Unpair, turn off bluetooth, reboot. Using root explorer, go to /system/etc/bluetooth.
With text edit, open "input.conf" file. Change "idle timeout" to "0" (no timeout). Fix permissions, reboot, then pair devices again.
It might take about a minute for media to connect, but media stays connected with no drops.
Don't know why, but my uneducated guess is for some reason maybe it's reading "in seconds" instead of "in minutes". Anyway,p worked for me, try it let me know and share this post.
Sent from my SAMSUNG-SGH-I747 using xda premium
I dont have that file in my system/etc/bluetooth folder...?
Sent from my SGH-I747 using xda app-developers app
I don't have the file either. But I'm trying on latest 4.2
Sent from my SGH-I747 using xda app-developers app
geoldr said:
I don't have the file either. But I'm trying on latest 4.2
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Oh, me too. Is that why? Maybe the devs just forgot the file for the 4.2 builds?
Sent from my SGH-I747 using xda app-developers app
File is only on 4.1.2 ROM's.
Sent from my SAMSUNG-SGH-I747 using xda premium
mfc719 said:
File is only on 4.1.2 ROM's.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
So can we find the equivalent file for 4.2? Im searching google at the moment. Ill drop a heads up if i find anything
Sent from my SGH-I747 using xda app-developers app
Last night I was on Slim 4.2. I copied the files from his 4.1.2 ROM into the folder. Seemed to work, but got a lot crackle. Maybe if I deleted the original first it would have been better.
Sent from my SAMSUNG-SGH-I747 using xda premium
mfc719 said:
Last night I was on Slim 4.2. I copied the files from his 4.1.2 ROM into the folder. Seemed to work, but got a lot crackle. Maybe if I deleted the original first it would have been better.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
If you got crackle, then it didn't really work at all. Right? Are you just referring to the absence of bass that was fixed?
Does anyone know of a 4.1 ROM that has working bluetooth? ill DL it and pull the file and test it out.
mfc719 said:
CM, AOSP, AOKP, 4.1.2 Bluetooth A2DP Solved?
This worked for me, so I figured I'd share.
Unpair, turn off bluetooth, reboot. Using root explorer, go to /system/etc/bluetooth.
With text edit, open "input.conf" file. Change "idle timeout" to "0" (no timeout). Fix permissions, reboot, then pair devices again.
It might take about a minute for media to connect, but media stays connected with no drops.
Don't know why, but my uneducated guess is for some reason maybe it's reading "in seconds" instead of "in minutes". Anyway,p worked for me, try it let me know and share this post.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
I went temporarily back to Tasks last 4.1 build and I see the file, but everything is commented out. And it says "Defaults to 0 for no timeout". So technically mine is set to 0, and I still have no bass. Just no luck for us bluetooth people.
geoldr said:
I went temporarily back to Tasks last 4.1 build and I see the file, but everything is commented out. And it says "Defaults to 0 for no timeout". So technically mine is set to 0, and I still have no bass. Just no luck for us bluetooth people.
Click to expand...
Click to collapse
Supposedly, if you set
lpa.decode = false
in /system/build.prop
the bass issue is fixed. Its in one of these Q&A threads. Havent tried it cause that is for 4.1.2 only.
I stole the input.conf, main.conf, and network.conf files from a stock ROM and palced them in my /system/etc/bluetooth folder, set permissions, rebooted and......
didnt work. same exact issue complete with a total screen lock.
Boo!
jpride said:
Supposedly, if you set
lpa.decode = false
in /system/build.prop
the bass issue is fixed. Its in one of these Q&A threads. Havent tried it cause that is for 4.1.2 only.
I stole the input.conf, main.conf, and network.conf files from a stock ROM and palced them in my /system/etc/bluetooth folder, set permissions, rebooted and......
didnt work. same exact issue complete with a total screen lock.
Boo!
Click to expand...
Click to collapse
I tried the lpa.decode thing and it did not work.
Just so you guys know. The way Bluetooth is handle is totally different in 4.2 than it is on 4.1.
task650 said:
Just so you guys know. The way Bluetooth is handle is totally different in 4.2 than it is on 4.1.
Click to expand...
Click to collapse
That has become painfully apparent for me in the last few hours... Could you suggest a resource to educate us on the new methods?
Sent from my SGH-I747 using xda app-developers app
jpride said:
That has become painfully apparent for me in the last few hours... Could you suggest a resource to educate us on the new methods?
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Looks like were not getting any proper A2DP from AOSP for now. Which sucks. And TW ROM's are also crap. It was broken in 4.1, then working fine in 4.2, now they broke it again, and it doesn't seem like anybody is working on it.
geoldr said:
Looks like were not getting any proper A2DP from AOSP for now. Which sucks. And TW ROM's are also crap. It was broken in 4.1, then working fine in 4.2, now they broke it again, and it doesn't seem like anybody is working on it.
Click to expand...
Click to collapse
I was just browsing the google android dev site and they are definitely aware of it they have assigned an engineer as of November. Popular opinion is that the problem resides in the core stack(don't ask me).
Sent from my SGH-I747 using xda app-developers app
jpride said:
That has become painfully apparent for me in the last few hours... Could you suggest a resource to educate us on the new methods?
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Download source, find a way to fix the code, hope to fix Bluetooth is just about the only way.
jpride said:
I was just browsing the google android dev site and they are definitely aware of it they have assigned an engineer as of November. Popular opinion is that the problem resides in the core stack(don't ask me).
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
From what you are saying it sounds like the problem might only be solved with the next android iteration. Maybe 4.2.2. All I know is that after I installed 4.2 on my Nexus 7 and paired it to my car, the bluetooth audio cuts out a lot. So I am guessing this is a problem across 4.2 in general.
I found this page about the Nexus 7. Many users complaining about Bluetooth stutter.
http://code.google.com/p/android/issues/detail?id=39633
FYI. I'm reposting this from the SlimBean 4.2.1 Rom forum. I switched over to SlimBean 4.2.1 from Tasks ROM as a test of the Bluetooth issue. Here is a report. Mind you, its very cursory at this point. I'll have way more reliable data/info after tomorrow.
Depending on the app, my Bluetooth Audio streaming seems to be working. I just tested with Subsonic Streamer, both streaming online and local music sitting on my phone. Neither of those worked, i.e. erratic pacing, static clips, etc. I also used Audible to play an audiobook and it worked fine for about 5 minutes. I even turned the screen off to trigger the effect. Nothing. Maybe its not the best quality ever, yet. But its something. *shrug*
Click to expand...
Click to collapse
jpride said:
FYI. I'm reposting this from the SlimBean 4.2.1 Rom forum. I switched over to SlimBean 4.2.1 from Tasks ROM as a test of the Bluetooth issue. Here is a report. Mind you, its very cursory at this point. I'll have way more reliable data/info after tomorrow.
Click to expand...
Click to collapse
Sounds great! Task released an update with some changes to BT. But when I tried it I used poweramp and it was the same, unfortunately. Do you think you could download the free trial of poweramp and see if it work with the SlimBean ROM?
Delete please, I spoke too soon
On any CM10 based ROM, when I take a picture, it saves EXIF date as December 8, 2002. This wouldn't be bad except I use a lot of applications that create albums based on that date. Also, Dropbox reads this date instead of the filename or created date.
Does anybody have a solution for this? I've used different camera apps and it still does it.
mattman86 said:
On any CM10 based ROM, when I take a picture, it saves EXIF date as December 8, 2002. This wouldn't be bad except I use a lot of applications that create albums based on that date. Also, Dropbox reads this date instead of the filename or created date.
Does anybody have a solution for this? I've used different camera apps and it still does it.
Click to expand...
Click to collapse
This has been a problem since cm9 days. I think it was you that brought it up before and it basically fell on deaf ears. All I know is it doesn't do it in stock or Miui only CMx or anything based on CyanogenMod. I don't know if this has any connection but backups done directly in CWM have the same date code where as in Rom Manager it doesn't. Could the camera app and CWM be pulling from the same source?
Sent from my LG-P930 using xda app-developers app
Swetnes said:
This has been a problem since cm9 days. I think it was you that brought it up before and it basically fell on deaf ears. All I know is it doesn't do it in stock or Miui only CMx or anything based on CyanogenMod. I don't know if this has any connection but backups done directly in CWM have the same date code where as in Rom Manager it doesn't. Could the camera app and CWM be pulling from the same source?
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
Yeah, it was me who brought it up and yes, it was ignored. I even submitted a bug to CM and now I can't find the bug in their system. This bug is actually the only thing keeping me from permanently switching to any CM10.1 based ROM.
If anybody has a fix or workaround, please let me know.
Sent from my LG-P930 using xda premium
mattman86 said:
Yeah, it was me who brought it up and yes, it was ignored. I even submitted a bug to CM and now I can't find the bug in their system. This bug is actually the only thing keeping me from permanently switching to any CM10.1 based ROM.
If anybody has a fix or workaround, please let me know.
Sent from my LG-P930 using xda premium
Click to expand...
Click to collapse
Its the date thing plus Bluetooth, YouTube and reboot issues for me that keeps me going back to ICS. BTW I would like for you to try my latest tweaked version of v20f NitroTNT v 2 and see what you think. I believe I have finally solved the lag issue that has been an issue for our phones. Its a culmination of efforts from HO!NO!, lyfkevin and you. Let me know what you think. Also I modified the build.props file so no need to input access point info for it to work on AT&T. Enjoy.
One more thing, wind kernel 3.6 is built in.
Sent from my LG-P930 using xda app-developers app
cm10.1 is slowly getting better, ricardo had MHL working on 10.1 on his phone, it doesn't work on mine for some reason still trying to figure out why, that was always my main reason for staying on ICS, that and battery life, but the battery life is as good as ICS now, if they get mhl working i won't even need ics anymore. my bluetooth is working fine by the way i think it's fixed 100%, i can even use mine iwth a ps3 controller, car stereo etc without issues. my youtube also works great when i disable HW overlays in dev options (thanks mattman for that tip)
i have only seen mhl work on my phone with mattmans liquid nitro and stock ICS, i imagine it would work on your TNT rom also since its based on stock unless you changed something related to it
any solutions x this problem¿??¿'
Try unbricking your phone. Before it would show 12/8/2002 and after unbrick the correct date and time show up in EXIF data. Using 10.1.2 stable with wind 2.5
gtharea said:
Try unbricking your phone. Before it would show 12/8/2002 and after unbrick the correct date and time show up in EXIF data. Using 10.1.2 stable with wind 2.5
Click to expand...
Click to collapse
Just did that today with the guide you linked to and using 10.1.2 with 2.5 as well. It didn't work.
mattman86 said:
Just did that today with the guide you linked to and using 10.1.2 with 2.5 as well. It didn't work.
Click to expand...
Click to collapse
I remember that I did some research on this a good while ago on this. If I remember correctly, the code was right, it was something to do with the lib files that can't be decompiled and tweaked.
mattman86 said:
Just did that today with the guide you linked to and using 10.1.2 with 2.5 as well. It didn't work.
Click to expand...
Click to collapse
@mattman86: Have you tried microslav_mm's cm10? I don't know if it's the 3.4 kernel or the LG camera app but dates work fine. The ROM does have its quirks, but very good overall, been running it for the last week no BSOD's or reboots.
http://forum.xda-developers.com/showthread.php?t=2107530
Sent from my LG-P930 using xda app-developers app
Swetnes said:
@mattman86: Have you tried microslav_mm's cm10? I don't know if it's the 3.4 kernel or the LG camera app but dates work fine. The ROM does have its quirks, but very good overall, been running it for the last week no BSOD's or reboots.
http://forum.xda-developers.com/showthread.php?t=2107530
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
Yes, I have. I've tried just about every CM10 based ROM on here and they all have the problem. The CM team won't even look at the buy when I submit it.
I followed the unbrick guide above and now the problem even exists on stock ICS.
been looking around forever for an answer and found an app for acer devices which works on my S2 on PA 3.99. it doesn't completely fix the camera but helps A LOT so i thought i'd share:
it's called Acer EXIF Fixup on the Play Store.
i just created an account to share this info so i can't post a proper link but check it out and hope it helps!
hxxps://play.google.com/store/apps/details?id=net.lappyfamily.android.coconut&hl=en
lostcheese said:
been looking around forever for an answer and found an app for acer devices which works on my S2 on PA 3.99. it doesn't completely fix the camera but helps A LOT so i thought i'd share:
it's called Acer EXIF Fixup on the Play Store.
i just created an account to share this info so i can't post a proper link but check it out and hope it helps!
hxxps://play.google.com/store/apps/details?id=net.lappyfamily.android.coconut&hl=en
Click to expand...
Click to collapse
@mattman86 have you tried this it really works. There were about 17 photos it found without correct exif data and fixed it automatically.
Sent from my LG-LU6200 using xda app-developers app
As the title states, this thread was created for the sole purpose of discussion on CM 10.2 nightlies.
Discuss bugs, ask questions, discuss apps, describe your experience and anything else.
TWRP 2.6.x is confirmed to work for these nightlies.
Cwm 6.0.3.6 is confirmed thanks to polarbe4r
To those new or unaware :
So yesterday as of August 13th, CM has been releasing nightlies for Android 4.3.x for our D2tmo. Go to get.cm and click on D2tmo to download them.
Please don't forget to download the latest GAPPS for 4.3.0 from goo.im/gapps and keep in mind the latest GAPPS function only on the latest 4.3.0 current release.
My experience with it so far : I've had very bad run ins with CM on the d2tmo personally in the past. Audio bugs, bad battery, random bootloops occasionally. I would however like to report the nightlies seem stable, smooth and decent on battery. So far with the exception of Focal the New camera app, I have not noticed a problem, luckily the 4.3 AOSP camera is included in. I recommend sticking to stock kernel for the time being. I tried a couple of third party kernels and had some restarts and graphic bugs. So please, if you have tested the nightlies yet, please leave some feedback for the user and the developers.
Please use the following GAPPS for these 10.2 night lies :
http://goo.im/gapps/gapps-jb-20130813-signed.zip
Sent from my SGH-T999 using Tapatalk 2
Let's see if this upkeeps like I tried with cm10.1 lol.
Instagram video bug is still there. Anything else I should check for people? I'm on it all day and still no issues for actual phone and daily usage for me.
Sent from my SGH-T999 using xda premium
mt3g said:
Let's see if this upkeeps like I tried with cm10.1 lol.
Instagram video bug is still there. Anything else I should check for people? I'm on it all day and still no issues for actual phone and daily usage for me.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Just got a weird system crash when I'm on the market. I'll clear cache and report back.
Edit : Rebooted and it was gone actually. Weird haha.
Sent from my SGH-T999 using Tapatalk 2
mt3g said:
Let's see if this upkeeps like I tried with cm10.1 lol.
Instagram video bug is still there. Anything else I should check for people? I'm on it all day and still no issues for actual phone and daily usage for me.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I thought Instagram released an update that solved this? I know I saw at least one person claim it did.
DocHoliday77 said:
I thought Instagram released an update that solved this? I know I saw at least one person claim it did.
Click to expand...
Click to collapse
Just tested this on the most recent release of Instagram and he's right its not fixed. Forced close on front camera capture.
Sent from my SGH-T999 using Tapatalk 4
DocHoliday77 said:
I thought Instagram released an update that solved this? I know I saw at least one person claim it did.
Click to expand...
Click to collapse
It apparently allows you to choose a video in your gallery already or something, but no *not fixed. I don't play with instagram too much. Use it cause my sister uploads all my nieces pictures there and cause of a bet with a friend, that I won't get into lol.
Sent from my SGH-T999 using xda premium
thanks for this thread, i will be here often
i had an issue with focal already though, both times with HDR turned on. once when moving the focus circle around it froze, then after taking a pic, the image went to gallery sideways and i tried turning the phone or scrolling the images, it froze again
i do not have this issue with 10.2 on my new Nexus 7
Focal itself has been buggy for me on everything but yes, our phone included haha.
Sent from my SGH-T999 using Tapatalk 4
prepping my phone for the move to liquid smooth to cm10.2. I am doing a super wipe on it so i want to make sure everything is in order be back with my comments soonish.
I'll hopefully have enough time this weekend to fiddle with my phone and try whatever nightly is up at the time. One thing I'll say right now is that I'll setup everything like I have it right now. Might lose a few mods I recently got but no big deal, all reversible. I hope there's no problems restoring from 4.3 to a 4.2.2 CWM backup.
Jay Rock said:
I'll hopefully have enough time this weekend to fiddle with my phone and try whatever nightly is up at the time. One thing I'll say right now is that I'll setup everything like I have it right now. Might lose a few mods I recently got but no big deal, all reversible. I hope there's no problems restoring from 4.3 to a 4.2.2 CWM backup.
Click to expand...
Click to collapse
I had no issue last week restoring a 4.1.2 backup. You should be fine. I also have mine sent to external though.
Sent from my SGH-T999 using xda premium
Seems pretty stable for me, no issues so far, but only flashed this afternoon. I'll update the nightlies and report any issues.
Sent from my SGH-T999L using xda app-developers app
mt3g said:
I had no issue last week restoring a 4.1.2 backup. You should be fine. I also have mine sent to external though.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
You mean your backup is stored on an external SD card?
I had a screen of death while listening to play music and skipping a track with holding the volume up feature.
Dirty Upgraded from Nightly 8-13 to Nightly 8-14. Upgraded Gapps as well. FC'd for the first reboot on Phone (Dialer was not present from 8-13).
Used all day on Dirty Upgrade without issue after a few reboots. Play Store could not update any software and Helium could not take a backup.
Got home and Clean installed 8-14 and Gapps. Zero problems after install on typical applications. Rebooted for Google to Restore Apps from Backup. File Manager can not display /storage/emulated/0 or /storage/emulated/legacy after enabling root mode. Had to use /mnt/shell/emulated/0 and /mnt/shell/emulated/legacy (Yes I know they are the same location, but just for thoroughness I used both).
Using Terminal Emulator you are able to see that /storage/emulated/legacy exists, but /storage/emulated/0 does not.
Code:
su
cd /storage/emulated
ls -a
Jay Rock said:
You mean your backup is stored on an external SD card?
Click to expand...
Click to collapse
I move them there as i hate dealing with /0 folders lol.
sswb27 said:
I had a screen of death while listening to play music and skipping a track with holding the volume up feature.
Click to expand...
Click to collapse
And I'll test Play Music on my home tonight, I have poweramp but just to confirm for you. Are they stored on sdcard or are you streaming?
Further bugs
Slider shortcut will not stick to just say slider only no shortcuts. It always reverts back. Haven't found a fix yet.
Sent from my SGH-T999 using xda premium
mt3g said:
I move them there as i hate dealing with /0 folders lol.
And I'll test Play Music on my home tonight, I have poweramp but just to confirm for you. Are they stored on sdcard or are you streaming?
Further bugs
Slider shortcut will not stick to just say slider only no shortcuts. It always reverts back. Haven't found a fix yet.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I was streaming for a couple hours while at work but it only happened once. After the reboot it didn't do it again, so maybe it was a fluke.
sswb27 said:
I was streaming for a couple hours while at work but it only happened once. After the reboot it didn't do it again, so maybe it was a fluke.
Click to expand...
Click to collapse
No such thing
Sent from my SGH-T999 using xda premium
You know what, I'll flash it tonight, will test until weekend if anything goes bad for me, otherwise will stay on it.
Anyone having any issues with root access after first install. Can't seem to get mine to run.