So, I'm new to this and have a Note 2 (SPH L900) from Sprint. I am trying to learn the terminology but I'm a quick study through interactive conversations in a forum board like this. I put cyanogenmod using clockwork on my rooted phone and I've noticed that the GPS fails to get a lock, the camera goes in and out of focus while recording video and the call volume is very low when I'm making a phone call.
For the GPS thing someone said to flash a stock TouchWiz and then re-flash cyanogenmod back on it and that seems to have fixed it. In my searches on how to do this or where to even get a TouchWiz I lost that original thread. Can someone help me understand how to get the original TouchWiz?
As far as the camera thing, I'm not sure if there's a different camera app that would suffice?
And the call volume I remember reading somewhere that there's a file that you can edit to change the call volume.
I've been all over trying to get this device working with cyanogenmod and getting lost in the interwebs and the terminology that I'm not used to. I've been recently starting to wonder if I should just go back to the original out of the box installation but I don't know how to do that either!?! LOL!
Thanks in advance for any and all help!
XDKYX said:
So, I'm new to this and have a Note 2 (SPH L900) from Sprint. I am trying to learn the terminology but I'm a quick study through interactive conversations in a forum board like this. I put cyanogenmod using clockwork on my rooted phone and I've noticed that the GPS fails to get a lock, the camera goes in and out of focus while recording video and the call volume is very low when I'm making a phone call.
For the GPS thing someone said to flash a stock TouchWiz and then re-flash cyanogenmod back on it and that seems to have fixed it. In my searches on how to do this or where to even get a TouchWiz I lost that original thread. Can someone help me understand how to get the original TouchWiz?
As far as the camera thing, I'm not sure if there's a different camera app that would suffice?
And the call volume I remember reading somewhere that there's a file that you can edit to change the call volume.
I've been all over trying to get this device working with cyanogenmod and getting lost in the interwebs and the terminology that I'm not used to. I've been recently starting to wonder if I should just go back to the original out of the box installation but I don't know how to do that either!?! LOL!
Thanks in advance for any and all help!
Click to expand...
Click to collapse
For the GPS issue, Flash the rom found here http://forum.xda-developers.com/note-2-sprint/development/classic-stock-ne2-4-4-2-deodexed-t2818246 , You don't even have to set up all the accounts just go in open up MAPS get the GPS lock then Flash back to your Cyanogenmod Rom and your GPS should work.
Now for the call volume I know alot of Roms are having issues with this. When you get or make a call what i do is after the call is started I turn my volume down as far as it will go and then turn it back up and the call volume is fine. If there is a fix for this I haven't ran across it yet.
Your camera Issue i haven't ran across that myself. But i'll browse these forums and see what i can come up with.
There are several CM based ROMS to choose from. If you prefer CM over TW (Samsung's interface overlay) then you should visit the development forums and choose a ROM that you feel is right for you. Personally I like Slim ROM and Carbon ROMs. The volume bug effects CM ROMS but there are a few ROMS that volume has been "pre-tweaked". Otherwise during a call turn volume down then back up and it should be much louder.
CM cameras tend to be slightly subpar to the stock TW camera as far as picture quality, lag, and focusing, etc, but for the most part all CM cameras do work ok. I personally prefer the stock TW based camera but that's not an option if using a CM based ROM.
There's no other way around the GPS bug other than what has been mentioned. Simply flash a stock type ROM that is based off the Samsung Touch Wiz ui overlay and do as Sothus said. Get a solid GPS lock using google maps. I highly recommend doing the same thing for LTE at the same time. Get in LTE coverage and make sure your phone is connected to LTE data service then get the GPS lock with Google Maps. Then immediately reboot into recovery, wipe system, data, cache, dalvic cache, flash MK4 or NE2 modem, then flash the ROM.
Also make sure you are using a current version of Clockwork recovery or better yet use Phil's version of Clockwork recovery. You can find it in the regular development forum not original development forum. Good luck.
tx_dbs_tx said:
There are several CM based ROMS to choose from. If you prefer CM over TW (Samsung's interface overlay) then you should visit the development forums and choose a ROM that you feel is right for you. Personally I like Slim ROM and Carbon ROMs. The volume bug effects CM ROMS but there are a few ROMS that volume has been "pre-tweaked". Otherwise during a call turn volume down then back up and it should be much louder.
CM cameras tend to be slightly subpar to the stock TW camera as far as picture quality, lag, and focusing, etc, but for the most part all CM cameras do work ok. I personally prefer the stock TW based camera but that's not an option if using a CM based ROM.
There's no other way around the GPS bug other than what has been mentioned. Simply flash a stock type ROM that is based off the Samsung Touch Wiz ui overlay and do as Sothus said. Get a solid GPS lock using google maps. I highly recommend doing the same thing for LTE at the same time. Get in LTE coverage and make sure your phone is connected to LTE data service then get the GPS lock with Google Maps. Then immediately reboot into recovery, wipe system, data, cache, dalvic cache, flash MK4 or NE2 modem, then flash the ROM.
Also make sure you are using a current version of Clockwork recovery or better yet use Phil's version of Clockwork recovery. You can find it in the regular development forum not original development forum. Good luck.
Click to expand...
Click to collapse
Thanks!
Is there a screen on my phone that I go into to "Get in LTE coverage"?
XDKYX said:
Thanks!
Is there a screen on my phone that I go into to "Get in LTE coverage"?
Click to expand...
Click to collapse
no. You have to be in a geological location where Sprint provides 4G LTE. You'll need to go to Sprint.com and see what areas are suppose to have it.
And then just by turning on my phone in one of those locations is all I would need to do? Or should I make a phone call?
Sent from my SPH-L900 using XDA Free mobile app
XDKYX said:
And then just by turning on my phone in one of those locations is all I would need to do? Or should I make a phone call?
Sent from my SPH-L900 using XDA Free mobile app
Click to expand...
Click to collapse
So I did this and it works great, the volume trick works and the GPS lock worked. thank you both so much!
On a side question is there anywhere that I can download the stock "L900VPUCNE2" ROM to flash with Clockwork in case I want to go back? I found a topic on this site that talks about when the upgrade was released but I Google and can't find a solid ROM that I can use to flash back. Thanks in advance!!!
XDKYX said:
So I did this and it works great, the volume trick works and the GPS lock worked. thank you both so much!
On a side question is there anywhere that I can download the stock "L900VPUCNE2" ROM to flash with Clockwork in case I want to go back? I found a topic on this site that talks about when the upgrade was released but I Google and can't find a solid ROM that I can use to flash back. Thanks in advance!!!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2780984
Stock ROM?
lennykravitz2004 said:
http://forum.xda-developers.com/showthread.php?t=2780984
Click to expand...
Click to collapse
so, this link that lennykravitz2004 just posted is the stock ROM that my phone would currently have or had before I put cyanogenmod on it, right? I just want to make sure before I start messing with it that this is in fact the same as what I had. I accidentally deleted the backup that I had through clockworkmod (not that the backup worked anyway) and want to try and make a solid stock backup. Thanks in advance!
XDKYX said:
so, this link that lennykravitz2004 just posted is the stock ROM that my phone would currently have or had before I put cyanogenmod on it, right? I just want to make sure before I start messing with it that this is in fact the same as what I had. I accidentally deleted the backup that I had through clockworkmod (not that the backup worked anyway) and want to try and make a solid stock backup. Thanks in advance!
Click to expand...
Click to collapse
Yes that is pure stock ROM. Note that when you use Odin to flash this you will have stock ROM, kernel, and recovery also it will not be rooted.
Sent from my XT1045 using XDA Free mobile app
Related
I have searched via various keywords for days and have not found an answer to my problem yet. I have only run across one other post (on another forum) that describes exactly my issue and they are asking the exact same question I have with no response.
I am using the AT&T Samsung Galaxy S3. I have downloaded CM 10.0.0 stable d2att on several occasions (different computers even), verified the md5, and installed on my phone. I have used CWM, CWM Touch, and TWRP to install hoping it was an issue there. Regardless of what I have done, I have the same issue addressed below:
I make or receive a phone call. No problems answering a phone call when it comes in. However when I hang up, the screen immediately goes back to sleep (which seems to be normal for the Nexus after researching). However, if I press the power button after the call is ended, the screen does not turn on at all. The hardware buttons (menu and back) do light up however and they remain lit. Regardless of what I do my phone stays stuck in this mode unless I hold the power button for about 10 seconds or so and force it to reboot, at which point it operates normal with no issues until my next phone call.
Has anyone experienced this issue and if so did you find a way to resolve it that does not require rebooting the phone? Right now this is the only thing keeping me from using the ROM as my daily driver.
Imo, AOSP-based ROMs run best when coming from stock. I flash back to touchwiz the before flashing them. Not sure if you've tried this.
Also, I had some small issues with the exact same rom that kept me from making it my daily driver. If you want stability, I can vouch for AOKP 4.1.2. I'm in no hurry for 4.2 with this rom running so well with no bugs or glitches
xBeerdroiDx said:
Imo, AOSP-based ROMs run best when coming from stock. I flash back to touchwiz the before flashing them. Not sure if you've tried this.
Also, I had some small issues with the exact same rom that kept me from making it my daily driver. If you want stability, I can vouch for AOKP 4.1.2. I'm in no hurry for 4.2 with this rom running so well with no bugs or glitches
Click to expand...
Click to collapse
Thanks. Seems that it was destined not to work. Oh well. I was on TW nearly everytime. I will give AOKP a shot. Should like it equally as well because I prefer AOSP roms. I am assuming you restore nandroid stock...or do you odin flash?
aybarrap1 said:
Thanks. Seems that it was destined not to work. Oh well. I was on TW nearly everytime. I will give AOKP a shot. Should like it equally as well because I prefer AOSP roms. I am assuming you restore nandroid stock...or do you odin flash?
Click to expand...
Click to collapse
I don't think it matters but I usually restore my tw/stock nandroid because it's right there and I don't lose root.
When I flashed the rom im currently running, I formatted /system /data and battery. Not sure if you care or need that info, just passing it on as this device has run really well for me on this OS.
I also flashed the Nexus 4 camera/gallery and the TW clock. The aokp camera is lame-o, and controlling the alarms is easier on the TW clock.
If you can't find them on the forum here (where I got them), PM me your email and I will send you the zips if you are interested. I believe I flashed them both in cwm, wiped cache/dalvik and then adjusted permissions in root browser to rw-r-r
AOKP's 4.1.2 jellybean milestone 1 is still on goo.im
xBeerdroiDx said:
I don't think it matters but I usually restore my tw/stock nandroid because it's right there and I don't lose root.
When I flashed the rom im currently running, I formatted /system /data and battery. Not sure if you care or need that info, just passing it on as this device has run really well for me on this OS.
I also flashed the Nexus 4 camera/gallery and the TW clock. The aokp camera is lame-o, and controlling the alarms is easier on the TW clock.
If you can't find them on the forum here (where I got them), PM me your email and I will send you the zips if you are interested. I believe I flashed them both in cwm, wiped cache/dalvik and then adjusted permissions in root browser to rw-r-r
AOKP's 4.1.2 jellybean milestone 1 is still on goo.im
Click to expand...
Click to collapse
I actually downloaded the camera/gallery apk for 4.2 as well as the keyboard. Already installed and running. Prefer both over the 4.1.2 versions installed on AOKP and CM10. Thanks for the info.
I tried to post this on cyanogen mods website but I was not allowed to post
I bought a AT&T Galaxy S III for my wife this weekend and ran into several problems installing cyanogenmod 10 on it.
Installing:
First the Heimdall program failed to "initialize interface" and no matter what I tried it failed to connect.
I managed to get it installed by using the ODIN to flash different clockwork mod (but that errored out on the when I went to flash cyanogenmod 10 )
So I used that to root it then installed cyanogenmod via rom manager by having that install the right clockwork mod then cyanogen 10.
It would be nice if they provided a ODIN Image for cyanogenmod
VoiceMail:
voicemail was missing its number after I installed cyanogen mod.
It took me forever to get this correct. Found out that you just forward to your mobile number. In the phone settings. or dial **004*PhoneNumber#
Also Google voice failed to setup correctly as well and had to use the **004 path.
Skype:
downloading via google play kept returning "package file invalid" (I cleared /cache and dalvik cache still failed) I ended up downloading it via the androiddrawer website and it installed (sideload?).
The problem with this is when using the voice or video chat the other side just hears very load static. Found someone claiming these problems came from cyanogenmod 10 not using the correct mics all the time. This is still an issue.
My questions are these issues fixed in the most recent version of Cyanogen the M releases? And if not are they known and someone working on them?
And does anyone have a fix for the static issue in skype?
JonoPorter said:
I tried to post this on cyanogen mods website but I was not allowed to post
I bought a AT&T Galaxy S III for my wife this weekend and ran into several problems installing cyanogenmod 10 on it.
Installing:
First the Heimdall program failed to "initialize interface" and no matter what I tried it failed to connect.
I managed to get it installed by using the ODIN to flash different clockwork mod (but that errored out on the when I went to flash cyanogenmod 10 )
So I used that to root it then installed cyanogenmod via rom manager by having that install the right clockwork mod then cyanogen 10.
It would be nice if they provided a ODIN Image for cyanogenmod
VoiceMail:
voicemail was missing its number after I installed cyanogen mod.
It took me forever to get this correct. Found out that you just forward to your mobile number. In the phone settings. or dial **004*PhoneNumber#
Also Google voice failed to setup correctly as well and had to use the **004 path.
Skype:
downloading via google play kept returning "package file invalid" (I cleared /cache and dalvik cache still failed) I ended up downloading it via the androiddrawer website and it installed (sideload?).
The problem with this is when using the voice or video chat the other side just hears very load static. Found someone claiming these problems came from cyanogenmod 10 not using the correct mics all the time. This is still an issue.
My questions are these issues fixed in the most recent version of Cyanogen the M releases? And if not are they known and someone working on them?
And does anyone have a fix for the static issue in skype?
Click to expand...
Click to collapse
Unless your wife can troubleshoot issues why install a custom ROM on her phone. My wife would kill me since she has no clue but I digress.
Why not flash 10.1 on the phone and download the gapps from the goo.im site and see if hat helps your issues. Maybe you got a bad flash and/or download. For the short amount of time I tried it I didn't have any of these issues you do. Those don't seem to be any bugs in the known bugs beyond maybe the static. Task's AOKP is another one to try if you want a custom stable rom.
Try another ROM or maybe a fairly stock rooted rom and see if that clears up any issues.
Are you using a Mac or a PC ? You mentioned Odin (for windows PC's) and heimdall (for all others). Honestly the best way is to flash a stock rooted ROM from the no tripping flash counter Rooting thread in Development and then flashing CWM in rom manager. Limiting having to flash in odin is the far better option. I've never ha d a bad flash in a custom recovery but everytime I have to use Odin I get extremely nervous.
Read Beerdroid's guide and you can't go wrong
hednik said:
Unless your wife can troubleshoot issues why install a custom ROM on her phone. My wife would kill me since she has no clue but I digress.
Why not flash 10.1 on the phone and download the gapps from the goo.im site and see if hat helps your issues. Maybe you got a bad flash and/or download. For the short amount of time I tried it I didn't have any of these issues you do. Those don't seem to be any bugs in the known bugs beyond maybe the static. Task's AOKP is another one to try if you want a custom stable rom.
Try another ROM or maybe a fairly stock rooted rom and see if that clears up any issues.
Are you using a Mac or a PC ? You mentioned Odin (for windows PC's) and heimdall (for all others). Honestly the best way is to flash a stock rooted ROM from the no tripping flash counter Rooting thread in Development and then flashing CWM in rom manager. Limiting having to flash in odin is the far better option. I've never ha d abad flahs in a custom recovery but everytime I have to use Odin I get extremely nervous.
Click to expand...
Click to collapse
agreed.
there are a couple good and stable stock/touchwiz custom roms as well as AOSP-based roms on this forum. i would steer clear of nightlies and super-custom roms that are always posting new updates. these are less stable imo.
put something on her phone thats solid and be sure to use the proper wiping and flashing procedures when you do so. wiping/flashing correctly makes ALL the difference on the software's performance while it's running on a device
xBeerdroiDx said:
agreed.
there are a couple good and stable stock/touchwiz custom roms as well as AOSP-based roms on this forum. i would steer clear of nightlies and super-custom roms that are always posting new updates. these are less stable imo.
put something on her phone thats solid and be sure to use the proper wiping and flashing procedures when you do so. wiping/flashing correctly makes ALL the difference on the software's performance while it's running on a device
Click to expand...
Click to collapse
Well I went with Cyanogen because I used it on my old droid incredible and its was great. I also want a stock like rom because I personally use a stock Nexus 4 and want my wifes phone to be similar and wanted to remove all the retarded extra apps atnt and samsung threw on.
So no idea if the 10.1 would fix the static issue then?
JonoPorter said:
Well I went with Cyanogen because I used it on my old droid incredible and its was great. I also want a stock like rom because I personally use a stock Nexus 4 and want my wifes phone to be similar and wanted to remove all the retarded extra apps atnt and samsung threw on.
So no idea if the 10.1 would fix the static issue then?
Click to expand...
Click to collapse
I can't say for sure but download and see if it works out of you. Thing with bugs is that they aren't always reproducible. I don;t see your issue as a known bug on 4.2.2. There are a few other ROM like super nexus in the dev section that are a practically stock nexus feel. Why not give that one a try ? Give AOKP a try as well.
Here's super nexus:
http://forum.xda-developers.com/showthread.php?t=2219944
hednik said:
I can't say for sure but download and see if it works out of you. Thing with bugs is that they aren't always reproducible. I don;t see your issue as a known bug on 4.2.2. There are a few other ROM like super nexus in the dev section that are a practically stock nexus feel. Why not give that one a try ? Give AOKP a try as well.
Here's super nexus:
http://forum.xda-developers.com/showthread.php?t=2219944
Click to expand...
Click to collapse
i'm an advocate of AOKP, but thats just my 2 cents. there is a very solid 4.1.2 milestone out and their 4.2.2 milestone will be released very soon.
although faryaab is a great kid and puts some good stuff together, remember that supernexus is a port and you could experience bugs (as i did). again, just my opinion
I have myself a Rogers based S3, that has the stock Jelly Bean OS on it.
Its bogged down, I don't like it anymore.
I have seen the OS on the Nexus unit's and find it to be WAY better (more fluid, more options and much better UI for texting)
Now for the explanation of this thread....
I have NO idea what I'm doing anymore when it comes to this phone. It's not rooted, NO CWM installed.. And i fear i may brick it if i don't know exactly what i'm doing.
That being said, i would like to go to a stock Google OS, or something very close to it.
What are my options? I would like to try and make this as pain free as possible. As far as i can recall, rooting//cwm and Os load on my captivate was really easy... This time around, i am finding way too many "possible" ways of doing everything. I think more or less, i need to be pointed to the right way so i don't get confused.
Anyone willing to toss me a hand on this one :fingers-crossed:
http://forum.xda-developers.com/showthread.php?t=2343223
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4
Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
saj222 said:
http://forum.xda-developers.com/showthread.php?t=2343223
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4
Click to expand...
Click to collapse
Instead of linking me to something I've already read, how about actually saying something.
I'm finding too many "this might work for rogers, this might not"
Last time i followed a tutorial meant for an AT&T unit, I hard bricked the phone, and ended up tossing it
Sorry if it was in the wrong section before Kenny.
How about me not responding at all next time? I know no one is forcing me but its simple enough to find this info by searching. I understand your hesitance... No one wants an expensive brick.
I'll put something together for you later today unless someone else beats me to it. Deal?
js593 said:
What are my options? I would like to try and make this as pain free as possible. As far as i can recall, rooting//cwm and Os load on my captivate was really easy... This time around, i am finding way too many "possible" ways of doing everything. I think more or less, i need to be pointed to the right way so i don't get confused.
Click to expand...
Click to collapse
Good thread to read: http://forum.xda-developers.com/showthread.php?t=1725839
First you need to get root. 2 easy ways here. First one is install a stock rooted ROM with Odin. Look for the Rogers image here: http://forum.xda-developers.com/showthread.php?t=1739426 Second one is to install CF-Root with Odin, here: http://forum.xda-developers.com/showthread.php?t=1963790 Make sure to get the one for I747M. Second option is faster b/c the zip is way smaller. Now you have stock root.
Next get GooManager https://play.google.com/store/apps/details?id=com.s0up.goomanager&hl=en. Run it, press menu and then install open recovery script or something like that. It will install TWRP custom recovery. Now you can flash ROMs. Perform Nandroid backup before commencing flashing.
For a pure Google like experience, give Slimrom or AOKP (Task650) a try. Very stable.
Slim - http://forum.xda-developers.com/showthread.php?t=2085739
AOKP - http://forum.xda-developers.com/showthread.php?t=1766684
Dandroid is the latest stock themed to the hilt like Cyanogenmod. Very stable.
Dandroid - http://forum.xda-developers.com/showthread.php?t=2121506
saj222 said:
Good thread to read: http://forum.xda-developers.com/showthread.php?t=1725839
First you need to get root. 2 easy ways here. First one is install a stock rooted ROM with Odin. Look for the Rogers image here: http://forum.xda-developers.com/showthread.php?t=1739426 Second one is to install CF-Root with Odin, here: http://forum.xda-developers.com/showthread.php?t=1963790 Make sure to get the one for I747M. Second option is faster b/c the zip is way smaller. Now you have stock root.
Next get GooManager https://play.google.com/store/apps/details?id=com.s0up.goomanager&hl=en. Run it, press menu and then install open recovery script or something like that. It will install TWRP custom recovery. Now you can flash ROMs. Perform Nandroid backup before commencing flashing.
For a pure Google like experience, give Slimrom or AOKP (Task650) a try. Very stable.
Slim - http://forum.xda-developers.com/showthread.php?t=2085739
AOKP - http://forum.xda-developers.com/showthread.php?t=1766684
Dandroid is the latest stock themed to the hilt like Cyanogenmod. Very stable.
Dandroid - http://forum.xda-developers.com/showthread.php?t=2121506
Click to expand...
Click to collapse
Thank you very much. I';ll be looking this over and attempting this tonight.
js593 said:
I have myself a Rogers based S3, that has the stock Jelly Bean OS on it.
Its bogged down, I don't like it anymore.
I have seen the OS on the Nexus unit's and find it to be WAY better (more fluid, more options and much better UI for texting)
Now for the explanation of this thread....
I have NO idea what I'm doing anymore when it comes to this phone. It's not rooted, NO CWM installed.. And i fear i may brick it if i don't know exactly what i'm doing.
That being said, i would like to go to a stock Google OS, or something very close to it.
What are my options? I would like to try and make this as pain free as possible. As far as i can recall, rooting//cwm and Os load on my captivate was really easy... This time around, i am finding way too many "possible" ways of doing everything. I think more or less, i need to be pointed to the right way so i don't get confused.
Anyone willing to toss me a hand on this one :fingers-crossed:
Click to expand...
Click to collapse
I'm using Task650 4.2.2. on my Rogers device and IMO it's the best out there. Never bricked my phone and smooth as butter.
thecoach1999 said:
I'm using Task650 4.2.2. on my Rogers device and IMO it's the best out there. Never bricked my phone and smooth as butter.
Click to expand...
Click to collapse
Hey guys.
So i got the phone rooted, and TWRP is installed. I have a NANDROID backup already done, but i'm a little confused on the roms. Could someone help me with this?
Last i recall, the roms were a single file, Ive downloaded the AOKP JB in this thread http://forum.xda-developers.com/showthread.php?t=1766684 but i'm confused on how to install the rom (as its a .zip file, there's multiple files in the folder....)
Thank in advance!
Edit - I tried to flash the rom anyways, and AOKP one Failed and turned up with an error. It comes up saying "Error executing updater binary in zip "
Edit2 - I just managed to flash Dandroid to the S3, but apps are failing to load everywhere. Unsure if this is something to do with the network or anything, but im also not getting LTE with Rogers.... Play store wont connect either (and i did to the Gapps update...?)
js593 said:
Hey guys.
So i got the phone rooted, and TWRP is installed. I have a NANDROID backup already done, but i'm a little confused on the roms. Could someone help me with this?
Last i recall, the roms were a single file, Ive downloaded the AOKP JB in this thread http://forum.xda-developers.com/showthread.php?t=1766684 but i'm confused on how to install the rom (as its a .zip file, there's multiple files in the folder....)
Thank in advance!
Edit - I tried to flash the rom anyways, and AOKP one Failed and turned up with an error. It comes up saying "Error executing updater binary in zip "
Edit2 - I just managed to flash Dandroid to the S3, but apps are failing to load everywhere. Unsure if this is something to do with the network or anything, but im also not getting LTE with Rogers.... Play store wont connect either (and i did to the Gapps update...?)
Click to expand...
Click to collapse
Before flashing you need to wipe. Data, system, dalvik and cache. Oh and before this put the new ROM files and anything you want to keep like pics on the external sdcard.
Do you have an updated bootloader? http://forum.xda-developers.com/showthread.php?t=2321310
Try re downloading the AOKP ROM and flash the while thing (the .zip). Then flash the gapps. You may have a bad download the first time.
With non-touchwiz ROMs you need to install the ROM and gapps. Do not install any gapps with dandroid.
saj222 said:
Before flashing you need to wipe. Data, system, dalvik and cache. Oh and before this put the new ROM files and anything you want to keep like pics on the external sdcard.
Do you have an updated bootloader? http://forum.xda-developers.com/showthread.php?t=2321310
Try re downloading the AOKP ROM and flash the while thing (the .zip). Then flash the gapps. You may have a bad download the first time.
With non-touchwiz ROMs you need to install the ROM and gapps. Do not install any gapps with dandroid.
Click to expand...
Click to collapse
I believe i ran into the issue blindly.
I forgot to update the bootloader before flashing it. Will try again when i get home and report back with anything.
..
fffft said:
If that sorts your issues, then call it done and thank the people that helped you.
The earlier suggestions were good and not to be faulted. However there is more than one way to do most things. So if you are not happy for whatever reason here is a slightly different approach. There are some very stable custom ROMs that are very snappy and have a similar no lag, fluid feel (Google calls this "butter") to them vis a vis the Nexus. So a simple approach to that result would be:
1. Download and install the Samsung S3 V7.0 toolkit (program)
2. Start the toolkit program
Choose "n" when asked if you want to update the program
Choose your phone version. This is probably "53" for you
Choose option #1 from the main menu to install the necessary USB driver to your PC
After the driver is installed, connect your phone to your PC with the Samsung USB cable.
If your phone is currently stable, you can skip steps #3 + 4.
If you are uncertain, then steps #3 + 4 will restore a stock Rogers firmware as a starting point:
3. Go to Samsung updates and download a stock Rogers firmware
4. Install the stock firmware. This is toolkit menu option #8, 4, 2
5. Download the custom Wicked Aroma ROM v10 (main thread here)
6. Copy the Wicked Aroma ROM to your phone. You can do this in windows by going to file manager and drag and drop the Wicked file (leave it zipped) on the "Samsung Mobile MTP Device - Phone/Data" folder icon.
7. Flash the Wicked ROM from "recovery mode"
Ensure that your battery is at least 80% charged. Then turn your phone off and disconnect the USB cable
Push and hold the home button, volume up and power button at the same time until you feel the phone vibrate and see blue text on screen in the upper left hand corner. Then release the buttons.
On the onscreen phone menu, choose wipe (factory reset)
Then choose install and select the Wicked_v10. zip file
The rest of the install will be automated on your phone screen. It will ask you to select a number of options. If you are uncertain, then just leave them at the default settings. Ensure that you leave the wipe cache setting as is when asked. And I'd recommend the stock theme and stock kernel to start. The rest you can leave as is or change to what sounds attractive to you.
Note that the wicked ROM will change your boot splash screen. Most people won't care and it's not that hard to revert if you don't like the logo for some reason. This is the logo that appears for a few seconds when you first power up a phone.
This is a very snappy, pretty much zero lag and stable ROM. I think that you'd like it.
.
Click to expand...
Click to collapse
Thanks for the lengthy reply.
I tried putting the new bootloader on there, and tried re-flashing, but it did the same thing. So, in the mean time i'm going to use the Dandroid rom (didn't install the Gapps) and it seems to be working okay. I just fear a bit as the phone seems to be running much warmer then it usually does....
In the mean time, ill use this one, and see if it makes a difference (it could still be loading all my settings and whatnot, so we'll see what happens. I love the look of this rom though. Very simple, very clean. Exactly what i was looking for. Those samsung stock themes are terrible.... Thanks a bunch for the help people. Greatly appreciate it!
Personal taste varies a lot and there are a lot of themed ROMs on this site. So you should be able to find something that you like. It sounds like you want something snappy and Spartan looking. If you like your results so far, then no need to go any further.
If you end up trying the Wicked ROM, perhaps choose the Miui or Holo launcher and ASOP lock screen options.
There are an endless variety of home screen themes to be discovered. And no way to know what you might like. A few random screen shots:
http://media02.hongkiat.com/cool-android-homescreens/Clood.jpg
http://media02.hongkiat.com/cool-android-homescreens/evening.jpg
http://main.makeuseoflimited.netdna-cdn.com/wp-content/uploads/2012/09/jb_holo_launcher.jpg
http://i380.photobucket.com/albums/oo248/jb-dan/DroidInc/d4281332.jpg
http://mycolorscreen.com/wp-content/uploads/homescreens_2012/270592/KLPOS7.png
http://desktopspotting.com/wp-content/uploads/2011/12/Minimal-Android-Home-screen.png
.
Just installed the Wicked rom on my S3. NICE! Need to play with the settings a bit to get it configured the way I like, but a definite keeper.
Very nice job.....Kudos!
Hello,
I've read through the Everything thread on Development, as well as searched using the xda search and google site search, but come up with nothing.
The Everything thread mentions that the current version of CWRM won't charge when the phone is off or in recovery, but I can't find anything about which version is the 'latest' (6.0.1.2, 5.0.2.7), nor if this also affects the TWRP recoveries (2.6.3, 2.4.1)? For that matter, I can't find anything that even mentions the charging problems at all aside from the Everything thread!
If there is a charging problem with all of the third party ROMs, is there a method to go back to the stock recovery after flashing in a ROM and backing up /efs/? I'm basically shooting for a fully functional phone and I don't plan on changing ROMs all over the place, just root and ICS.
Help?
Thanks!
TooG435 said:
Hello,
I've read through the Everything thread on Development, as well as searched using the xda search and google site search, but come up with nothing.
The Everything thread mentions that the current version of CWRM won't charge when the phone is off or in recovery, but I can't find anything about which version is the 'latest' (6.0.1.2, 5.0.2.7), nor if this also affects the TWRP recoveries (2.6.3, 2.4.1)? For that matter, I can't find anything that even mentions the charging problems at all aside from the Everything thread!
If there is a charging problem with all of the third party ROMs, is there a method to go back to the stock recovery after flashing in a ROM and backing up /efs/? I'm basically shooting for a fully functional phone and I don't plan on changing ROMs all over the place, just root and ICS.
Help?
Thanks!
Click to expand...
Click to collapse
I think something like 6.0.4 the latest CWMR. ( you can build with http://builder.clockworkmod.com/ , Existing Device option doesnt work)
It charges in latest TWRP, you can see "+" char when on charge next to the battery level.
Stock uses recovery for official upgrade, and factory reset. We have only offline charge issue, but recovery has no effect on it. Offline charger works with a limitation. I wouldnt bother you with the explanation, since you said you would like to use stock ICS.
You can backup efs in rooted rom without recovery. You can always flash recovery with odin phone in download mode.
Thanks.
I guess I had assumed the comment was referring to the builds in the Development forum, not the overall CWMR project! Is there a currently recommended recovery, or is it a toss up to personal preference? I'm not so much tied to ICS as tied to a completely working ROM - especially as I see all the bluetooth and skype issues with the JB ROMs, which (as far as I can tell) are still unresolved / unknown?
TooG435 said:
Thanks.
I guess I had assumed the comment was referring to the builds in the Development forum, not the overall CWMR project! Is there a currently recommended recovery, or is it a toss up to personal preference? I'm not so much tied to ICS as tied to a completely working ROM - especially as I see all the bluetooth and skype issues with the JB ROMs, which (as far as I can tell) are still unresolved / unknown?
Click to expand...
Click to collapse
I make TWRP for i927, we dont have other up to date, but you can build yourself.
Dont you have issue with stock ICS? I made up to date issue list in me CM 10.2, you could decide it suit for you or not, you may know stock limitation already.
I hope voip issue would be resolved soon.
bubor said:
I make TWRP for i927, we dont have other up to date, but you can build yourself.
Dont you have issue with stock ICS? I made up to date issue list in me CM 10.2, you could decide it suit for you or not, you may know stock limitation already.
I hope voip issue would be resolved soon.
Click to expand...
Click to collapse
My only real requirement in a phone is that it be reliable - I don't want to have to pop out batteries or have no audio on calls if I get stranded in the middle of nowhere. At this point, my phone is still in the mail - got a used one from a friend, but it hasn't arrived, so I haven't had much ability to experiment yet.
My Android experience is exclusively with a Transformer TF101, which had 4.0.4 ICS stock and is currently running Katkiss JB 4.2.2_226 (Katkiss 4.3 isn't stable enough for me yet, was getting daily crashes last time I tried). All of the phone components are new to me - and the Glide seems to have a more fragmented recovery scene than the TF101, which is pretty much TWRP or nothin'
Thanks again for your help!
Hi Friends,
Long story short, I am over all the Samsung specific features on my Note 3, and am ready to have a bit more performance and speed by moving to an AOSP/AOKP ROM. Last time I flashed was a LONG TIME ago, so I need your help in getting me there. Appreciate the help in advance!:
My Setup: Knox 0x0, ROM/Build: N9000TUVUDNE6 (T-Mobile Stock) - (Rooted with CF-Root, I believe), NO CUSTOM RECOVERY
1. I HAVE TO install a Custom Recovery to get an AOSP/AOKP ROM installed, correct?
1A. If yes, which Recovery would you recommend installing?
1B. If no, what are the ROMs that I can install those and links for it?
2. If a Custom Recovery is required, this will trip my KNOX count to x1, correct? And there is NO way to avoid it?
2A. If it CAN be avoided, how do I do it?
3. What is the BEST AOSP/AOKP ROM available out for the T-Mobile Note 3 right now? I am looking for the balance features and performance.
4. Are there any outstanding AOSP/AOKP issues that are big and NOT working right now, like Camera, GPS, Bluetooth and etc?
5. Do I have to install a special Kernel or firmware to move over from TW to AOSP/AOKP? If so, which one? Link?
6. Lastly, if a Custom Recovery is required, do these steps sound right for this transition:
1. Backup everyone on my TW phone RM, TitaniumBackup and etc
2. Install Custom Recovery
3. Do a Nandroid of my TW ROM
4. Wipe all Caches, System like 3 times
5. Install the AOKP ROM
6. Install GApps
7. Profit
Did I miss anything? Thank you for your help in advance!
ProFragger said:
Hi Friends,
Long story short, I am over all the Samsung specific features on my Note 3, and am ready to have a bit more performance and speed by moving to an AOSP/AOKP ROM. Last time I flashed was a LONG TIME ago, so I need your help in getting me there. Appreciate the help in advance!:
My Setup: Knox 0x0, ROM/Build: N9000TUVUDNE6 (T-Mobile Stock) - (Rooted with CF-Root, I believe), NO CUSTOM RECOVERY
1. I HAVE TO install a Custom Recovery to get an AOSP/AOKP ROM installed, correct?
1A. If yes, which Recovery would you recommend installing?
1B. If no, what are the ROMs that I can install those and links for it?
2. If a Custom Recovery is required, this will trip my KNOX count to x1, correct? And there is NO way to avoid it?
2A. If it CAN be avoided, how do I do it?
3. What is the BEST AOSP/AOKP ROM available out for the T-Mobile Note 3 right now? I am looking for the balance features and performance.
4. Are there any outstanding AOSP/AOKP issues that are big and NOT working right now, like Camera, GPS, Bluetooth and etc?
5. Do I have to install a special Kernel or firmware to move over from TW to AOSP/AOKP? If so, which one? Link?
6. Lastly, if a Custom Recovery is required, do these steps sound right for this transition:
1. Backup everyone on my TW phone RM, TitaniumBackup and etc
2. Install Custom Recovery
3. Do a Nandroid of my TW ROM
4. Wipe all Caches, System like 3 times
5. Install the AOKP ROM
6. Install GApps
7. Profit
Did I miss anything? Thank you for your help in advance!
Click to expand...
Click to collapse
Folks, anyone? Appreciate your prompt help the TW ROM is killing me LOL!
ProFragger said:
Hi Friends,
Long story short, I am over all the Samsung specific features on my Note 3, and am ready to have a bit more performance and speed by moving to an AOSP/AOKP ROM. Last time I flashed was a LONG TIME ago, so I need your help in getting me there. Appreciate the help in advance!:
My Setup: Knox 0x0, ROM/Build: N9000TUVUDNE6 (T-Mobile Stock) - (Rooted with CF-Root, I believe), NO CUSTOM RECOVERY
1. I HAVE TO install a Custom Recovery to get an AOSP/AOKP ROM installed, correct?
1A. If yes, which Recovery would you recommend installing?
1B. If no, what are the ROMs that I can install those and links for it?
2. If a Custom Recovery is required, this will trip my KNOX count to x1, correct? And there is NO way to avoid it?
2A. If it CAN be avoided, how do I do it?
3. What is the BEST AOSP/AOKP ROM available out for the T-Mobile Note 3 right now? I am looking for the balance features and performance.
4. Are there any outstanding AOSP/AOKP issues that are big and NOT working right now, like Camera, GPS, Bluetooth and etc?
5. Do I have to install a special Kernel or firmware to move over from TW to AOSP/AOKP? If so, which one? Link?
6. Lastly, if a Custom Recovery is required, do these steps sound right for this transition:
1. Backup everyone on my TW phone RM, TitaniumBackup and etc
2. Install Custom Recovery
3. Do a Nandroid of my TW ROM
4. Wipe all Caches, System like 3 times
5. Install the AOKP ROM
6. Install GApps
7. Profit
Did I miss anything? Thank you for your help in advance!
Click to expand...
Click to collapse
1. I HAVE TO install a Custom Recovery to get an AOSP/AOKP ROM installed, correct?
Yes, you need to install a custom recovery.
1A. If yes, which Recovery would you recommend installing?
Usually people recommend TWRP as their recovery of choice. You can download it at https://goo.im/devs/OpenRecovery/hlte/ Download the .img.tar and you can flash that as AP in Odin.
1B. If no, what are the ROMs that I can install those and links for it?
2. If a Custom Recovery is required, this will trip my KNOX count to x1, correct? And there is NO way to avoid it?
Yes, it will trip KNOX to 0x1. There is no way to avoid it, unless you have a Canadian Galaxy Note 3 (SM-N900W8)
2A. If it CAN be avoided, how do I do it?
3. What is the BEST AOSP/AOKP ROM available out for the T-Mobile Note 3 right now? I am looking for the balance features and performance.
All user preference. I like CyanogenMod for frequent updates, Carbon for the UI. Currently running Temasek's CM as it is a good mix of both Carbon and CM, imo.
4. Are there any outstanding AOSP/AOKP issues that are big and NOT working right now, like Camera, GPS, Bluetooth and etc?
Biggest issue seems to be the S-Pen not working after a while (requires a reboot) and NFC is not functioning, but some users have reported it to work with the SM-N900T
5. Do I have to install a special Kernel or firmware to move over from TW to AOSP/AOKP? If so, which one? Link?
You shouldn't have to install a special firmware, provided you're on the latest build of KitKat for the Note 3.
6. Lastly, if a Custom Recovery is required, do these steps sound right for this transition:
1. Backup everyone on my TW phone RM, TitaniumBackup and etc
2. Install Custom Recovery
3. Do a Nandroid of my TW ROM
4. Wipe all Caches, System like 3 times I have never seen accurate reports of this doing anything useful. Do the full wipe in TWRP, it will do everything you need to wipe.
5. Install the AOKP ROM
6. Install GApps
7. Profit
Essentially that's everything you need to do. If you want, you can install a custom Kernel, or install a flashable zip of SuperSU if you want to use that (compared to the built-in Superuser)
Hope this helps!
skadude66 said:
1. I HAVE TO install a Custom Recovery to get an AOSP/AOKP ROM installed, correct?
Yes, you need to install a custom recovery.
1A. If yes, which Recovery would you recommend installing?
Usually people recommend TWRP as their recovery of choice. You can download it at https://goo.im/devs/OpenRecovery/hlte/ Download the .img.tar and you can flash that as AP in Odin.
1B. If no, what are the ROMs that I can install those and links for it?
2. If a Custom Recovery is required, this will trip my KNOX count to x1, correct? And there is NO way to avoid it?
Yes, it will trip KNOX to 0x1. There is no way to avoid it, unless you have a Canadian Galaxy Note 3 (SM-N900W8)
2A. If it CAN be avoided, how do I do it?
3. What is the BEST AOSP/AOKP ROM available out for the T-Mobile Note 3 right now? I am looking for the balance features and performance.
All user preference. I like CyanogenMod for frequent updates, Carbon for the UI. Currently running Temasek's CM as it is a good mix of both Carbon and CM, imo.
4. Are there any outstanding AOSP/AOKP issues that are big and NOT working right now, like Camera, GPS, Bluetooth and etc?
Biggest issue seems to be the S-Pen not working after a while (requires a reboot) and NFC is not functioning, but some users have reported it to work with the SM-N900T
5. Do I have to install a special Kernel or firmware to move over from TW to AOSP/AOKP? If so, which one? Link?
You shouldn't have to install a special firmware, provided you're on the latest build of KitKat for the Note 3.
6. Lastly, if a Custom Recovery is required, do these steps sound right for this transition:
1. Backup everyone on my TW phone RM, TitaniumBackup and etc
2. Install Custom Recovery
3. Do a Nandroid of my TW ROM
4. Wipe all Caches, System like 3 times I have never seen accurate reports of this doing anything useful. Do the full wipe in TWRP, it will do everything you need to wipe.
5. Install the AOKP ROM
6. Install GApps
7. Profit
Essentially that's everything you need to do. If you want, you can install a custom Kernel, or install a flashable zip of SuperSU if you want to use that (compared to the built-in Superuser)
Hope this helps!
Click to expand...
Click to collapse
Ska, that was very helpful bud, thank you for responding!
Two follow up questions:
1. In an AOSP ROM why would one even need the S-Pen?
2. What are the main differences between CM, AOKP, PA, Carbon and etc and where can I find their best, baked versions? By best I mean, most updated developer support and popular?
Thank you again for your help!
ProFragger said:
Ska, that was very helpful bud, thank you for responding!
Two follow up questions:
1. In an AOSP ROM why would one even need the S-Pen?
2. What are the main differences between CM, AOKP, PA, Carbon and etc and where can I find their best, baked versions? By best I mean, most updated developer support and popular?
Thank you again for your help!
Click to expand...
Click to collapse
People use the S-pen as a stylus for their phone, without any if the features that Touchwiz provides.
As it stands, CM is updated every day with a nightly build, and our device maintainer has been on a tear recently. Carbon is updated frequently too.
My recommendation would be to try out temasek CM11, it has a good mix of all the AOSP features. Tons of stuff to customize!
skadude66 said:
People use the S-pen as a stylus for their phone, without any if the features that Touchwiz provides.
As it stands, CM is updated every day with a nightly build, and our device maintainer has been on a tear recently. Carbon is updated frequently too.
My recommendation would be to try out temasek CM11, it has a good mix of all the AOSP features. Tons of stuff to customize!
Click to expand...
Click to collapse
Thanks bud, I'll give them a shot. Was thinking about the SlimROM 4.4.4 or Pac Man... Any thoughts?
ProFragger said:
Thanks bud, I'll give them a shot. Was thinking about the SlimROM 4.4.4 or Pac Man... Any thoughts?
Click to expand...
Click to collapse
Never really tried it. Like I said, it's all a question of preference! Try it out, if you don't like it, just flash another one!
Also important: You will lose Wifi Calling and Voice over LTE.
Product F(RED) said:
Also important: You will lose Wifi Calling and Voice over LTE.
Click to expand...
Click to collapse
Don't care about WiFi calling, but what is voice of LTE? Is it anything related to having data connectivity WHILE being on the phone as well? As in, will it switch to a CDMA like behavior, where data does NOT work, when you are on a call?
Cause I can't have the latter. What does Voice over LTE mean? Thanks for your help!
P.S. Any direct links to some of these ROMs you guys are using? Thanks.
ProFragger said:
Don't care about WiFi calling, but what is voice of LTE? Is it anything related to having data connectivity WHILE being on the phone as well? As in, will it switch to a CDMA like behavior, where data does NOT work, when you are on a call?
Cause I can't have the latter. What does Voice over LTE mean? Thanks for your help!
P.S. Any direct links to some of these ROMs you guys are using? Thanks.
Click to expand...
Click to collapse
Normally on a phone call, your phone will go from LTE to 4G. This allows the phone to be on LTE the entire time because it makes the call go over LTE (as data, but it doesn't count against your data). If you wanna see what it's like without it, go into the dialer, hit menu, settings, and set it to never use it. Then make a call.
Product F(RED) said:
Normally on a phone call, your phone will go from LTE to 4G. This allows the phone to be on LTE the entire time because it makes the call go over LTE (as data, but it doesn't count against your data). If you wanna see what it's like without it, go into the dialer, hit menu, settings, and set it to never use it. Then make a call.
Click to expand...
Click to collapse
Ah, I see what you mean bud. But I am assuming that this feature is likely only native to T-Mobile? Is it?
I use my Unlocked Tmo N3 on AT&T. I don't think this would affect me, just like WiFi calling... thoughts?
Thanks
ProFragger said:
Ah, I see what you mean bud. But I am assuming that this feature is likely only native to T-Mobile? Is it?
I use my Unlocked Tmo N3 on AT&T. I don't think this would affect me, just like WiFi calling... thoughts?
Thanks
Click to expand...
Click to collapse
AT&T has VoLTE in limited markets, but I believe that you can only use it by flashing an AT&T based TouchWiz ROM.
Sent from my SM-N900T using Tapatalk
ProFragger said:
P.S. Any direct links to some of these ROMs you guys are using? Thanks.
Click to expand...
Click to collapse
Ok just thought I'd throw this out there at the risk of being thought of as "rude", even though I'm actually just trying to help. I've been a member of this community for a really long time now and it's an excellent source of information along with a lot of great people who are always willing to help, and you can definitely get the most out of it but you also have to be willing to help yourself. Helping someone who doesn't understand something is totally different from helping someone who says "fetch me a link because I don't feel like doing it myself". I'm certainly not saying that was your "intention" so hopefully you don't take it that way, I'm just trying to put it into perspective as to how it can come across to those who are taking their own time to help you out. Odds are people who are willing to help also don't really care for doing menial work (like searching for links, etc.) which basically everyone is capable of, so I'm just saying that it might help to keep that in mind. Another thing to remember is that 99.9% of the questions you'll probably ever think of have been answered or solved already, so when you do take the time to become familiar with stuff like the basic forum outline, searching, and how to rate and subscribe to threads, it's actually surprising how self sufficient you become just from learning those things. Anyway like I said I'm not trying to be ignorant or "bash" you whatsoever, just thought I'd throw that out there because most people on here will always be willing to help whenever they can, as long as you're willing to help yourself! Hope it helps man
Sent from a modified ColecoVision
Before you go and install other roms, what issues are you having with your phone? If it's just the touchwiz launcher, you can always install Nova Launcher and use Titanium Backup to freeze touchwiz and any bloatware that's in the way.
skadude66 said:
People use the S-pen as a stylus for their phone, without any if the features that Touchwiz provides.
As it stands, CM is updated every day with a nightly build, and our device maintainer has been on a tear recently. Carbon is updated frequently too.
My recommendation would be to try out temasek CM11, it has a good mix of all the AOSP features. Tons of stuff to customize!
Click to expand...
Click to collapse
I'm sorry to jump in on this chat, but I was thinking of jumping over to aosp also. Is there no replacement for action memo? And also, are there any aosp roms make an action memo type app open when I pull my s-pen out?
Thanks in advance,
Tommy
twatts723 said:
I'm sorry to jump in on this chat, but I was thinking of jumping over to aosp also. Is there no replacement for action memo? And also, are there any aosp roms make an action memo type app open when I pull my s-pen out?
Thanks in advance,
Tommy
Click to expand...
Click to collapse
There are definitely different apps you can use. Most people use Evernote, CM S-Pen Addon and Note Buddy. I don't think there's a way to get it to work right on stylus removal though.