Related
I'm looking to purchase a Galaxy S in Canada, and I'm just worried with the problems that I'm hearing here for the Bell Vibrant owners. For the Vibrant owners, I'm hearing problems such as the internal SD died and so a motherboard replacement is required to fix it, the phone refuses to boot, etc. Owners of the Rogers Captivate, please report back so you can help me, as well as helping other Rogers Captivate owners.
I hope this isn't a repost btw. I did a search and didn't find anything here..
Hey,
I purchased one the day it was released in Victoria, BC. Since then, I've rooted, nandroid backup, and installed the OCLF and a bunch of other cool ****.
I'm constantly turning it on and off. On and off. I have the screen brightness to the max (that's the way I like it), and at stock firmware, it's freaking awesome! Runs really smoothly. I don't really find much lag, but I can see room for plenty of improvement, which are going to be coming up shortly. My biggest complaint is the battery life (65% of mine goes to the brightness), but lasts just as long as any phone on standby. I went on eBay and got 3 batteries and a charger for $10. All hail, removable batteries.
I don't doubt more phones will come out within the next month or two, but if you want one today. I'd recommend it.
Let me know if I can influence your decision in anyway.
100% agree with TheShamsMan above ^
Got this phone from Vancouver @ Day 1 when Rogers launched it. Have done a ton of flashing on it, adding things, removing things, turning on and off the phone..haven't had a single problem with it so far. GPS has worked wonderfully for my needs so far(haven't tried car navigation yet though but i'm sure it would aswell work well). 100% recommend the phone. Even though some info for the Nexus S is out, I think the Captivate's looks beat it hands out. Let me know if you have any question~
Only had it a few days, but delighted with it so far.
I wasn't thrilled with the battery life, until I figured out the default wi-fi sleep policy was killing it.
The phone is pretty good, i've had it about 2 1/2 weeks right now.
I did encounter the shutdown issue though, but after using CaptivateKeepAlive for a little while (and then uninstalling it), it has seemed to gone away, though it did happen one more time recently, so I'm playing around with the battery and seeing what the trouble is (I have contacted futureshop though, and have a replacement phone waiting for me whenever they get more in stock).
Besides that issue, I'd say the battery is the only other thing. It seems to me, that even after applying all the good settings, I use quite a bit of battery. Its hard to tell because I play games on the phone often, but using batteryplotter and spareparts, it seems that most of this is caused by my wifi, and the phone always in a 'running' state. I don't mind very much right now, as I'm always near a plug, and I could make it last a day if I needed to without charging (though no games, and very little use).
So Battery problems, and shutdown problems aside, the phone is lovely. I have no GPS problems like ATT phones report, and no problem with lag either (though perhaps I just don't notice it yet).
All in all, the phone is quick and responsive, and the 16GB internal SD is quite nice. I wonder though, if its possible to use the roms for the ATT captivate on the Rogers captivate? (given the phone is a different model #)
FiniteSM said:
I have no GPS problems like ATT phones report, and no problem with lag either (though perhaps I just don't notice it yet).
Click to expand...
Click to collapse
I hope the your GPS non-issue is the rule and not the exception on the Rogers Captivate. I do remembering reading an article where a Rogers rep stated that their phone with throughly tested to make sure the GPS was fixed.
Assuming it's the rule ... I wonder what change they made to get the GPS working as it should?
crabjoe said:
I hope the your GPS non-issue is the rule and not the exception on the Rogers Captivate. I do remembering reading an article where a Rogers rep stated that their phone with throughly tested to make sure the GPS was fixed.
Assuming it's the rule ... I wonder what change they made to get the GPS working as it should?
Click to expand...
Click to collapse
I dont know what they tweaked...but it also works great for me.
All in all the phone is great. I am coming from a Blackberry Bold 9000 that I used for 2 years and decided that I wanted to try something differents.
The Wifi Sleep policy is something you should change when you get your phone.
Settings -->Wireless and network --> Wi-Fi settings --> (menu button) Advanced Settings -->Wifi Sleep policy --> Never
The constant switching between wifi and 3G drains the battery like you won't believe!
Thanks guys. Looks like I'll have an excellent time with my Captivate.
It's nice to hear that no one's Captivates died on them yet. It has me worried, but at the same time I think the whole thing was blown out of proportion.
Hey,
I bought my Captivate from Rogers on Sept 25 (I believe it was the launch date) in Ottawa, ON. I tried out the stock firmware and everything worked swimmingly. I had great GPS locks, the phone was quick enough for anything I did, and did everything it was supposed to. As long as I was mindful of how bright my screen was and whether GPS/WIFI/Syncing was toggled, I was able to push my phone reasonably into the second day without charging it.
Since the first few days, I've been loading Cognition software (currently 2.4) onto my phone. Not because the stock firmware was horrible or anything, I'm just an obsessive tinkerer who needs the absolute best performance and reliability out of his phone. Unlike many of the AT&Ts out there, I didn't break my GPS after loading cognition. My phone is lightning quick, whether it is picking up a GPS satellite lock or playing my music through the auxiliary input in my car. The battery lasts just as long as it ever did, maybe even longer. Again, Cognition isn't a miracle battery cure, and you still have to be mindful of any running apps in the background or if any of the GPS/WiFi/Syncing is toggled to really max out your battery life. Alternatively, you could get an app like locale which automates things like that for you.
If you're looking to buy a version of the Samsung Galaxy S, I really can't think of a better version to buy than the Rogers one. I haven't had ANY troubles with it and it seems to have the least amount of problems between the ones released in Canada and the US. I may be wrong on that, since my researched focused mostly on the Captivate, but perhaps someone could verify what I just said.
I'd go for it,
Tom
The phones pretty damn fantastic, I just wish Samsung would drop Touchwiz and release vanilla Android. Seriously, no one likes it, and everyone likes new versions of Android.
FiniteSM said:
All in all, the phone is quick and responsive, and the 16GB internal SD is quite nice. I wonder though, if its possible to use the roms for the ATT captivate on the Rogers captivate? (given the phone is a different model #)
Click to expand...
Click to collapse
DOUBLE POST! (Sorry guys, not sure if it's an issue here, I know on some forums it is)
To answer your question, yes you can. Personally, i've had issues with data not working and OCLF + stock is more than fast enough for me, after I got rid of TwLauncher. One thing to note though, is that you will have a permanent ATT screen before the "I896" screen, so if that bugs you, stay away.
I picked up the Captivate last night and loving it a lot. However I am having a few problems with it that I dunno how to solve yet. One of em is the poor battery life, and another is texting. I'm not gonna repost it here. If I have to, I'll make another thread.
Thanks for the feedback guys!
This is all very good news. I had the Samsung Vibrant (Bell) version before and never really ran into big problems other than some freezes, but let go of it because my buddy's internal SD died, so that phobia caused me to get the Captivate, since they are all the same internals..
Mine is coming in the mail from retentions.. Lets hope i'm not disappointed. Already got a case from SGP lined up and on its way, also the 2 battery + battery charger combo. Already know what to expect.. Surprised that the GPS is fixed!.. I will be sure to check when I receive my unit tomorrow.
Has everyone checked it with the actual GPS receiver turned on? Because, I know that the "wireless networks" gps box always works. But what if it is unchecked, and only the GPS box is on, does it still work then?
FiniteSM said:
I wonder though, if its possible to use the roms for the ATT captivate on the Rogers captivate? (given the phone is a different model #)
Click to expand...
Click to collapse
I would also like to know if someone can please confirm whether the roms for the ATT captivate (i-897) are still compatible with the Rogers Captivate (i-896), just incase I want to flash a rom in the future.
Also, if the OCLF is safe to install? Or do we have to wait for one specially made for the Rogers Captivate?
So I got one for $34, delivered today. Looks perfect other than a couple scuffs on the bottom corners. The seller said it was working fine (despite listing saying it was for parts/not working). I don't have any usable cell service where I live without getting a booster and antenna of some sort, so I don't care about activating it. I plan on using it basically as an internet tablet to check email, etc.
I do not have an sd card, charger, or data cable yet, they should come tomorrow. Since the battery is close to dead, I can't find out much. It turns on fine, gets to the home screen and has that "too many pattern attempts" screen (screen looks perfect, not a single scratch by the way) with the google login. I know not to try a full hard reset with the battery being about dead, but I have tried to bring up the menu option so I know how to get there when I do get it charged. I have tried every key combination method I can find with no luck, keys ~seem to all be working from what I can tell, read in the comments that a few people had no luck. One time I got that screen with the android and shovel, waiting for download. I was wondering if that is from the factory, or if that means it's been rooted?
Basically, all I really want to do is restore it to stock for right now. Maybe something better down the line, I'd just like to use it for now since I've never even really seen a smartphone before, because nobody has one with the poor cell service here. I have the EE19 build downloaded, and I see the restoring to stock thread. I want to do it the right way. So, if it has lagfix installed, I see I need to disable that. Any other things I should know about? I was just wondering if it sounds rooted, if I need to do something else if it is. I don't have a lot of time on my hands to do research, although I did a little already, and I have a very limited internet connection so I can't download a lot of things, I wasn't expecting to need to do this when I communicated with the seller.
Thanks for any advice or tips.
Edit: I was also wondering the best way to go about checking the ESN, or if I should try. Like I said, I don't care to activate it on US Cellular, but if I'd resell it or something. I know I could use PagePlus, but the Verizon tower is 30 miles away, so not much chance of that working well either. I don't think it should be stolen or anything, but was thinking if the account ever got settled or anything....
Well I got it, posting from it now. Only problem is unsuccessful download errors in app market, after download is almost complete. On wifi. I tried every solution I found for that with no success. Other than that, no problems.
Tried every fix for the market, deleting cache, changing permissions on vendor.apk, etc. Seeing it was a common problem with few solutions that work, I flashed CM7. That worked great, apps installed fine, but of course wireless cut out constantly, not usable for long. Saw that was common, tried everything with no luck. Went back to stock, then airplane mode, now market works fine. It fails whenever not in airplane mode. So I'm sticking with this for now.
Can't activate anyway, but best I saw was -104db, but mostly no service. My LG tracfone does a little better with reception.
Sent from my SCH-I500 using XDA App
But I have been reading lots of things and am still not exactly sure what the benefit of installing a rom is. I am on t-mobile pre paid, so I am only getting EDGE for the moment. So speed is not going to be an issue, because I am limited by my network.
My battery has to be charged maybe 2 times a day. That is an annoyance, and that is one thing I think will be benefited by the rom.
I have never had a smartphone. So I am just learning what my phone is actually capable of doing. I am sure I do not even know a fraction of what my phone can do, but I am loving all the neat apps I have gotten. Living wallpapers, games, virtual guitars.....google sky map (which is amazing btw),
And I have been seeing all of these themes, and tweaks. The themes I think I understand, but can I even install a theme if I have stock system?
I know this is all preferences, but some suggestions and advice would be appreciated......
The benefit as I see it is basically getting a refined and more efficient OS onto your phone. Stock phones tend to come with a lot of bloatware that can both slow down the phone and take up space, not to mention that some items can also draw away the very limited amount of battery we already have to begin with.
Generally it also opens up the phone even more to being able to do additional things that require root access, etc. The way I think about it, in a very general and broad scope, is like buying a PC from a store and just using out of the box versus taking it home, formatting it, and then putting on a scaled down version of Windows (or other OS) that doesn't have all the added junk. Again, that's a rough example but hopefully you know what I mean.
Even when my phone was stock, I didn't have to charge it twice a day.
Consider removing some of the 'just for fun' apps and see if that makes a difference in battery life.
Chances are the OP needs to disable the H+ and only activate on E...... twice a day is nuts. I've only seen that on a HTC evo.... I use mine heavyly(spelling?) And only have to charge it when I get home.
Sent from my SAMSUNG-SGH-I997 using XDA App
Debloating is one of the main things.
For example, one of the DRM services in the stock AT&T ROM is a known battery hog.
The stock Rogers ROM has Carrier IQ, which is basically spyware.
Go ahead and flash yourself a custom ROM, I'm sure that'll help your battery life, because I mean 2 times a day is CRAZY, even on the Inspire's 1230mAh battery, it'll live all day (albeit, it'll be close to dead by the end, heavy usage sucks).
If you need help, go ahead and ask, but it's not hard.
So I'm looking over the current options and right now it's not really looking like it's promising. I have my Galaxy S3 rooted and with the help of tools like TitantiumBackup I've managed to clean up the stock ROM pretty well. Another thing of note is I actually get some surprisingly good sound quality out of my SGS3. I realize the US models aren't supposed to have the Wolfson DAC, but somehow mine sounds absolutely incredible with no noise that I can hear or anything (it's enough that I've been wondering if Samsung might have slipped the Wolfson into this one and perhaps there is variance in the DACs actually being used.) It even drives my headphones (modified HD555s -- basically you can consider them to be like the HD595s since of course I did the foam mod, but with the soundstage mod and a custom cable they're actually a bit better possibly) extremely well. It's worth noting that I have frozen the built in equalizer or whatever it was that I thought seemed like it was meant to mess with the sound (I like my devices to produce a relatively neutral sound.) Despite some complaints out there, I actually like the sound out from my US model SGS3 better than things like my Cowon D2 (which, btw, has a Wolfson DAC) and don't even use my CMoy (which has an AD8620 OPAMP that makes it sound far better than a typical OPA2132 CMoy IMO at only the cost of a bit of battery life) which I love the sound of because to me it sounds amazing on its own.
I only mention all of this because while I'm not a true audiophile per se, quality is of extreme importance to me all the same and I'm reading of issues with sound in the current custom ROMs which is not something I'm ok with. I want it to continue to sound this amazing. The idea of losing sound quality with a custom ROM bothers me. I like the idea of a few of the updates like Project Butter (though it's worth noting that mine does run fairly smoothly since I keep the number of programs running all the time as minimal as I can) and I really like the idea of having a custom ROM where I could maybe tweak more things (perhaps including better battery life options like maybe a better CPU governor built in? It drives me crazy how much my phone can run down over just a few hours while the screen is off even with SetCPU set to set the CPU to 384MHz and switch to the powersave governer with WiFi and mobile data both disabled and me not receiving any calls or texts.) For that matter, even while on it's not helping as much as it seems like it should, but I can't help but to notice that there are some more advanced CPU governors that I don't seem to have as an option and I wonder if perhaps a custom ROM could even help there as well. Plus I just plain like being able to tweak more things to my exact preferences instead and again a custom ROM helps. But, if I have to give up that sound quality that's a big problem. I think also it might be a problem to lose the camera. I don't use it a lot, but every now and then I really do kind of want to have it. Especially it would absolutely suck to lose the ability to scan QR codes or to have to do so via the front camera, but every now and then I do take some actual photos to share.
So my question is, have any of the custom ROM options out there reached that level of stability and quality to actually be worth updating and without losing those two things? The SGS3 has been out a fair while now, so it's hard for me to believe that there hasn't been a bit more progress along these lines, but I realize that it's no simple process to create a custom ROM all the same. (In fact, I only think more progress would have been made than what I've read thus far because the SGS3 is just so very popular. If it had been a less popular phone I wouldn't necessarily expect that much, but between its features, hardware, and etc, it's a pretty popular phone.) I want all the benefits of a custom ROM, but what I've read so far of them says to me that it's just not worth the trouble. Once I find one that really works I kind of want to stick to it as much as I can as I have a lot of apps installed and configured just so for my preferences. It sounds like I'm going to have to wait a good while yet though. Or have any of the custom ROMs finally "gotten there yet"?
ive been using CM10 roms for daily use and tehy do everything i need them to do without any limitations.
i suggest you make a nandroid of all your current setup and play with some custom roms. you can always revert back if you dont liek it or cant configure them match your usage. it made my S3 experience much better, btu everyone is dfferent.
---------- Post added at 08:08 PM ---------- Previous post was at 08:07 PM ----------
there are also sound mods and stuff that are accessible with ROMs. ive never tried them but some people swear by them
You don't have any sound issues of any kind? Does the rear camera work perfectly?
BTW, I don't want any sound mod that actually changes the sound. I want it to basically leave the sound alone and produce it as well as it can without modification. None of that Beats or whatever like some do (I think that was what HTC was pushing?)
beats is a sound thing, yeah. it hink its just an equalizer though. i have used audio through headphone jack and over bluetooth to my headphones and the quality is fine for me. im not an audiophile though. it all kinda sounds the same to me lol
the only sound issues i have with my ROM are after flash some sounds do not function until you slide the volume slider from 100 to 0 then to 100 again. Its these types of quirks that come with custom rom sometimes.
my camera is working perfectly. its not as good as the touchwiz one however.
edit: heres a sound mod that might/might not interest you
http://forum.xda-developers.com/showthread.php?t=1883262
long as you do a nandroid you can always revvert back to your preferred current setup. you should also backup your IMEI
There are roms that are optimized stock. Maybe CleanRom. Don't think he adds sound mods but may be wrong. You may have used app to underclock CPU and it shows UC but probably not actually working on stock kernel as clocking must be enabled on kernel. Know this is true with overclocking.
I actually prefer to avoid all sound modifications whatsoever. Even equalizer. I like the results of a relatively neutral sound being fed to these headphones, it comes out just perfect for me. That's part of what I was worried about as some of the custom ROMs sometimes try to have stuff like that built in (and I guess that equalizer or whatever it was was Samsung or Verizon kind of doing that in the stock ROM even.)
About the camera, I actually have a commercial camera app anyway. If the only problem people have been having was the built-in app, that's a non-issue.
What's this about sounds not working until you go to zero and back though? Does this interfere with anything such as receiving phone calls (eg does it sometimes not ring because the sound isn't playing?)
BTW, where do I actually find the "official" CM10 for this phone?
no the sound works all the time after the adjustment. it takes 2 secodns to do. open volume, slide them all to 100, then all to 0, then all to 100 again.
http://get.cm/?device=d2vzw&type=snapshot
i think that these M builds are the monthyl most stable ones.
Personally I'm waiting for something built on the official VZW JB release. And yes I know I have months to wait... :-\
Sent from my SCH-I535 using xda app-developers app
There is no DAC from Wolfson but yes it sounds kick ass! Qualcom is a beast! There S4 chip is there pride and joy so they didn't want to lag behind when it comes to quality audio! God does it sound so much better then my galaxy nexus. Qualcom is making the best arm chips right now. Can't wait to see how insane the 4 core S4 is!
I COMPLETELY AGREE WITH MY FELLOW MEMBERS WHEN IT COMES TO AVOIDING ALL THOSE STUPID AUDIO MODS LIKE BEATS AND SOME OTHERS OUT THERE. THEY SUCK AND DISTORT THE AUDIO!
Sent from my SCH-I535 using xda premium
ddurandSGS3 said:
no the sound works all the time after the adjustment. it takes 2 secodns to do. open volume, slide them all to 100, then all to 0, then all to 100 again.
Click to expand...
Click to collapse
Ah, have I misunderstood? Do you just mean it only needs this to be done after the initial flash of the custom firmware itself? That's definitely no big deal at all...
prdog1 said:
There are roms that are optimized stock. Maybe CleanRom. Don't think he adds sound mods but may be wrong. You may have used app to underclock CPU and it shows UC but probably not actually working on stock kernel as clocking must be enabled on kernel. Know this is true with overclocking.
Click to expand...
Click to collapse
Well, I want to try to do this just once or at least no more than minor updates after this hopefully, so if I'm going to go ahead I want to go ahead and go straight to Jelly Bean.
I think SetCPU wouldn't be sold as only requiring root access to do its work if it required a custom kernel. It probably just works with the internal power management features that should be built in more or less by default.
mike216 said:
There is no DAC from Wolfson but yes it sounds kick ass! Qualcom is a beast! There S4 chip is there pride and joy so they didn't want to lag behind when it comes to quality audio! God does it sound so much better then my galaxy nexus.
Click to expand...
Click to collapse
Interesting... I do definitely wonder why some people have complained about hearing noise and such then. Perhaps a bad setting and/or that MusicFX app (finally had time to dig through the list to find out what exactly it was called and that's the one that I just assumed was probably an equalizer/effects processing thing that would modify the sound, but honestly I never had any use for it even if it's not and never bothered to try it.) I'm glad to hear that I'm not the only one who thinks that the US SGS3 actually sounds good. I was beginning to wonder if my ears were maybe just getting that bad somehow even though I'm still far pickier than everyone I personally know, lol.
Let me ask you this, is the so called "Voodoo Mod" any good at least? I was never clear on exactly what it was supposed to do for audio. I know things like Beats probably mostly rely on a bit of processing to increase bass and probably play with things like stereo separation or something, but I've never been clear on what that one was trying to do exactly other than that people claim it's actually an improvement for many devices.
Anyway, back on the topic at hand, I think I'm more or less convinced to at least go ahead and give CM10 a shot. I'll use that newer monthly build from earlier this month after clearing enough space to make a full backup. (Besides CWM's backup option I've already backed up my apps and settings using TitaniumBackup, so in a worst case scenario it shouldn't be too painful if things go wrong and I have to go all the way back to a stock image with a factory reset or something. Is that option in CWM the correct thing, or must I use something separate for a Nandroid backup?) Also, it may sound silly, but how exactly do I backup my IMEI? I was looking for that already upon digging through a large tutorial thread a while back and it seemed to require something I couldn't get to work (when I try the numbers mentioned in the dialer I don't get any hidden menus, just a dialtone. Other than that I could only find something about manually restoring it if it has been completely damaged or lost which wasn't a fun looking process.)
Nazo said:
I think SetCPU wouldn't be sold as only requiring root access to do its work if it required a custom kernel. It probably just works with the internal power management features that should be built in more or less by default.
Click to expand...
Click to collapse
It is sold that way. Depends on the manufacturer of the device. On stock HTC kernel it will lock 2nd core at max speed, kill battery life and cause heating problems. That is why I said it may not work correctly and without another app to monitor CPU you don't know what it is doing. How it works with Samsung I wouldn't know as I run custom kernels when possible and don't worry about clocking on stock kernels as they are under performing already.
Don't restore system apps with titanium backup! Only data apps (apps from the market)
CM is great good choice. I love the theme engine CM10 has and all CM10 based roms.
I'll tell you a super easy way to backup your IMEI! Need Root!
Download (terminal emulator)
Enter these commands. su (hit enter)
reboot nvbackup (hit enter)
It will reboot and create the backup on a built in backup partition on your SD card. The only way you could delete the backup is if you formated your SD. Super easy I just hope it works lol....
Sent from my SCH-I535 using xda premium
Two quick questions before I take the final plunge.
1. Is the CWM backup to external flash function sufficient, or do I need something further for a true backup? (It says "Nandroid" in one part, but otherwise I'm not sure if it's truly "Nandroid." It seems like it just backs up each individual file or something and I get the impression that Nandroid is more of an image of the firmware? If it isn't sufficient, what should I use?
EDIT: Found this tutorial. Basically that's what I've done except instead of bothering with Odin I used the EZ-Recovery app to flash CWM directly from the phone itself (along with EZ-Unlock 1.2 from here to unlock the bootloader) as per another tutorial. The other tutorial just didn't call it a "Nandroid" backup, so I wasn't sure.
2. If anything goes wrong, is there a stock ROM image I can use for the Verizon SCH-I535 with Odin? So far my searching has taken me to a site that practically has every stock ROM for the SGS3 but that one... (Or at least if it has that one I couldn't find it on there, which isn't saying much since every single region was listed separately...)
The best way to get recovery is to get the latest recovery from the man who's created them all from the very beginning.
Get rom manager and flash the latest straight from that app. You must make sure your bootloader is unlocked. If you took the latest OTA from Verizon it locked your bootloader.
As long as your unlocked and rooted you can go straight in rom manager and flash touch recovery especially for your Verizon galaxy s3.
I've been using the latest touch recovery on my D2tmo, nexus 7,galaxy nexus and Asus infinity and it's worked perfect.
Make a backup of your current rom for safety before flashing. You can create a backup and rename it to whatever you want straight from rom manager!
I personally wouldn't back up to the external. It might work fine but when it comes to backups I just go straight to the internal
Sent from my SCH-I535 using xda premium
---------- Post added at 08:33 AM ---------- Previous post was at 08:26 AM ----------
I soft bricked my phone because after taking the latest OTA it locked my bootloader! Recovered it fully from here
http://forum.xda-developers.com/showthread.php?t=1840030
I seen the take to your local Verizon store bla bla bla.
Got in download mode at 4am and recovered in 15 minutes.
I wish I had someone that knew what I now know and that's why I'm here to help my fellow members!
Sent from my SCH-I535 using xda premium
Hehe, funny thing about that. It tried to automatically update without bothering to ask. I presume because I had the FWupdate app frozen (for I guess fairly obvious reasons) it utterly failed and then complained, then demanded that I update again after a while, giving me an option to defer it. (I never did figure out how to get it to stop pestering, but I guess that's a non-issue.) So I didn't ever get a locked bootloader simply because it failed to do what it was trying to do.
Anyway, I've installed CM10 and so far so good. Well, I gave myself a good scare by forgetting to do a factory reset (*sigh* I wish I didn't have to do that, but, after all, it's a significant change going from a highly modified VZW infested ICS to a cleaner custom Jelly Bean) and it sat there stuck on the boot logo until I reread the instructions and rebooted to fix it (at least CM doesn't wipe out the CWM recovery like the stock ROM does...) I still have a LOT to do to get everything all reinstalled and reconfigured. I'm not going to be able to finish it all tonight, so won't really be able to comment about the results of the switch until tomorrow I guess. It's not helping that it's taking absolutely forever to download the Google Play package and all (and then I get to redownload a lot of the apps, though hopefully TitaniumBackup can safely restore a lot of it.)
EDIT: BTW, is it just me or do they really REALLY need to provide basic info on how to do simple tasks like the actual installation process itself, installing Google Play, and etc? I'm no stranger to googling for info, but wow what a pain to figure this all out (especially it never occurred to me that the gapps zip would have to be installed using CWM. I thought it was for the firmwares themselves only, not them and apps...)
EDIT2: Oh wow. I had no idea how much work this was really going to be! I said before that a full ROM install is something I wanted to do once. Well, I definitely want to never do this again. I'm having to fight all sorts of things. Google didn't even want to recognize my phone at first despite successfully connecting my accounts and registered apps such as, oh, I don't know, Titanium Backup Pro just for instance weren't showing up as already purchased... -.- I think I finally got it all restored and they now properly show up as owned, but I've lost hours just fighting with all of these various things...
It also seems to have serious issues with my WiFi. I haven't figured out what is going on exactly, but it seems like I'm having to turn wifi off and on a bit to get it to properly connect again -- I've put in my password so many times I'm about to go absolutely insane (unfortunately, for various reasons I'm still stuck on WEP 128-bit, so I have to type in a large hexidecimal encryption key and I'm just about ready to go postal.) Hopefully once everything is finally all setup and configured all will be well, but at the moment I've lost a pretty good bit of sleep while fighting this and barely have it up and running. I probably should have waited for an off day to do this.
Nazo said:
Hehe, funny thing about that. It tried to automatically update without bothering to ask. I presume because I had the FWupdate app frozen (for I guess fairly obvious reasons) it utterly failed and then complained, then demanded that I update again after a while, giving me an option to defer it. (I never did figure out how to get it to stop pestering, but I guess that's a non-issue.) So I didn't ever get a locked bootloader simply because it failed to do what it was trying to do.
Anyway, I've installed CM10 and so far so good. Well, I gave myself a good scare by forgetting to do a factory reset (*sigh* I wish I didn't have to do that, but, after all, it's a significant change going from a highly modified VZW infested ICS to a cleaner custom Jelly Bean) and it sat there stuck on the boot logo until I reread the instructions and rebooted to fix it (at least CM doesn't wipe out the CWM recovery like the stock ROM does...) I still have a LOT to do to get everything all reinstalled and reconfigured. I'm not going to be able to finish it all tonight, so won't really be able to comment about the results of the switch until tomorrow I guess. It's not helping that it's taking absolutely forever to download the Google Play package and all (and then I get to redownload a lot of the apps, though hopefully TitaniumBackup can safely restore a lot of it.)
EDIT: BTW, is it just me or do they really REALLY need to provide basic info on how to do simple tasks like the actual installation process itself, installing Google Play, and etc? I'm no stranger to googling for info, but wow what a pain to figure this all out (especially it never occurred to me that the gapps zip would have to be installed using CWM. I thought it was for the firmwares themselves only, not them and apps...)
EDIT2: Oh wow. I had no idea how much work this was really going to be! I said before that a full ROM install is something I wanted to do once. Well, I definitely want to never do this again. I'm having to fight all sorts of things. Google didn't even want to recognize my phone at first despite successfully connecting my accounts and registered apps such as, oh, I don't know, Titanium Backup Pro just for instance weren't showing up as already purchased... -.- I think I finally got it all restored and they now properly show up as owned, but I've lost hours just fighting with all of these various things...
It also seems to have serious issues with my WiFi. I haven't figured out what is going on exactly, but it seems like I'm having to turn wifi off and on a bit to get it to properly connect again -- I've put in my password so many times I'm about to go absolutely insane (unfortunately, for various reasons I'm still stuck on WEP 128-bit, so I have to type in a large hexidecimal encryption key and I'm just about ready to go postal.) Hopefully once everything is finally all setup and configured all will be well, but at the moment I've lost a pretty good bit of sleep while fighting this and barely have it up and running. I probably should have waited for an off day to do this.
Click to expand...
Click to collapse
Strange that you are having so many issues. First off, when I flash a new ROM I put the ROM and the latest GApps on the sdcard. Do a factory reset, clear dalvik cache, install the ROM then the GApps. As far as wifi, I didn't have a problem when I ran CM10, but maybe there is something messed up in the latest version. Are you running the nightlies or the M versions?
The M version from the link above (the 2012 10-11 one.) At first I thought the issue I was having was the one from before where it would decide that my network with the hidden SSID was out of range automatically the moment it lost connection (either me leaving the area or turning off WiFi) but I not only tried to use the hidden SSID enabler, but also even went so far as to just re-enable the SSID broadcast on the router, so it's no longer hidden. It seems like it's having troubles initializing the WiFi. Maybe I somehow managed to freeze/remove an app that did something or other along these lines (though I just can't see how given that it can work, it just has issues.) I'm having to turn it off and on once or twice to get it to finally reconnect. I guess it's not bad since I have the power widget in the notifications tray that makes this a bit easier, but that doesn't make this any more fun at all to deal with. EDIT: In fact, whereas the hidden SSID issue I ran into previously had it just show up as being out of range after it lost the connection until I "forgot" the network setting and reconfigured it again, it looks like nothing shows up at all until I turn it off and on -- but I don't have to redo the network setting, so this is definitely a completely different issue. I think actually it's like it's just not correctly enabling the wifi on startup if it was left on when I rebooted so I have to turn it off and back on to get it to truly turn it on in the first place.
And yeah, I cleared the cache and did a factory reset before installing. Well, bear in mind that it naturally was showing up as a different device and all. So some initial configuration was definitely going to be required to even get started, and I was switching from ICS to JB (and completely different sorts of ROMs besides) so some initial fight was inevitable even if CM10 were the most established and stable build ever made just going from the one to the other. Actually, one interesting feature of Titanium Backup Pro (once I finally got it to recognize that I had the Pro version in the first place) is apparently the ability to change the device ID to seem to be the same as far as installed programs and such go, so now Google Play among other things thinks this is the same exact device as before now as opposed to being a new device. It's actually weird because the "new" one doesn't even show up on Google Play's settings anymore (and Google still hasn't gotten around to fixing it such that we can remove devices, so I still have my old Archos 43 PDA listed in there for instance.) Between everything, Google now is letting me once again access my software without re-buying or relying on backups (which is especially good because a few things seem to just get stuck when I try to restore them -- it just sits there forever, not ever really installing.)
BTW, I lost all the Verizon-specific special numbers such as *86 for voicemail. Apparently CM10 doesn't bother to list them (but then as they are vendor specific I guess that's not a big surprise.) Is there any sort of list of the numbers Verizon uses out there -- maybe even including whatever special numbers that might be more specific to this phone itself (such as that hidden menu or whatever)?
EDIT: Ok, so far things are starting to come together slowly but surely. One oddity though, I noticed at the end of my work shift that, rather than the usual 10% or so of battery time lost, it seemed to have lost about 20%. I wouldn't go so far as to say it's double -- it might be more like 15% many times -- but it is very odd all the same. I thought I was seeing a bad trend along these lines last night, so went ahead and put SetCPU back on there with the profile to do powersaving and serious underclocking when the screen is off and in both cases I used the "conservative" CPU governor for the normal use with the maximum CPU speed at about 1GHz (conservative is supposed to be like ondemand with a better tendency towards power saving at the expense of taking longer to scale the CPU upwards when needed.) As this is CM10, there should be no room for doubt that the CPU is being scaled down -- in fact in the performance menu I often see the CPU at a mere 384MHz (which is my minimum setting) -- so I'm just not sure what to think just yet. The settings menu for the battery life shows mostly just basic system processes like the screen, idle, and etc being the main culprits for battery usage, so again odd since the screen is the main thing yet is off during my working hours (with the very short exception of my breaks.) I don't think the automatic brightness setting is any higher or anything either and, in fact, configured it to use generally lower settings until the maximum brightness.
Guess more tweaking and testing is needed to be sure, but it's odd all the same. If anything CM10 is running LESS all the time by way of hidden services and such (though as far as things that actually show up in the likes of Android Assistant I'm having to fight far more things including an "analog clock" that isn't even in the app list so I'm hoping is just the normal clock despite the fact that "analog clock" in normal firmwares is actually a separate extra thing.) Guess I'll still have to wait and see to some extent.
Edit2: Haha, I just read that you have to recalibrate the battery meter after flashing, so it'd probably just not being very accurate is all. I grabbed an app to help do that so hopefully this is all that was going on (and if I go by Android Assistant's voltage status I'd say that it definitely is off.)
Edit3: (Just kind of adding as I go along here.) Now that all the basics are in place and I had some time and the desire to drain the battery more quickly (as part of the recalibrate process you're supposed to drain it until it automatically shuts down) so I plugged in my headphones and started listening. So far so good. I was really hoping that one of the advantages of a custom ROM would be a more precise volume control (Google really dropped the ball on that one! Sometimes you're trying to get it just right and end up stuck between either a bit painfully too loud or annoyingly too quiet with no in-between) but other than some dissapointed wishful thinking, it seems sound-wise this release of the SGS3 CM10 is just fine. I don't really hear any bloat or distortion in the bass and in general the usual modifications that they do to the sound just aren't there (or at least if they are they are subtle enough to fool my, let's say "bronze" ears since I'm definitely at the bottom of the audiophile chain, lol.) In one thread where someone asked how the Qualcom compared to the Wolfson sound-wise someone said it was a bit tinny, but if it is it's far too subtle for me to notice (and this is bearing mind that these are headphones with a slight bass roll-off, so it does seem like I'd notice any significant loss in the lower ranges pretty quickly. In this respect I'm happy or at least satisfied that nothing has gone wrong.
Also, one way or the other the wifi issue seems to have gone away. I'm guessing it was an app I had frozen that I reenabled, but that's just a guess. It's so hard to be 100% sure with these things unless you apply a long painful scientific process every single step of the way...
I'm STILL trying to figure out a way to configure the haptic feedback level. It seems to be all on or all off with no ability to reduce strength of feedback that I've found so far.
Another word to the wise, backup your imei. Not sure if that was mentioned yet
Also, your ROM will work better after a charging cycle or two. It will initially scam for media and such I believe which maybe part if the reason you're seeing slightly higher usage at first. Also, in general you'll get slightly less battery life on aosp. I don't find much use in most battery stats though. They're easily manipulated.
Sent from my Galaxy Nexus using xda app-developers app
Well, I had a small accident. I was replacing some fonts and manually selecting which ones to replace with what when I threw in Arial Unicode and another font that was still slightly large. I'm assuming because the font files were so big, but it completely stopped booting. After fighting with it for hours upon hours (and I have since found what might be a font zip file for CWM now that it's far too late to do me any good -- though of course it would have had to replace those particular fonts and it seems like most of my attempts to replace them ended up replacing everything but them.) I just couldn't get a driver to install for the phone while CWM was running (I don't know if you can maybe get an adb shell or what, but without the driver you obviously can't.) In the end, I ended up having to reformat and reinstall CM10 from scratch. So far (knock on wood) none of the real problems I was having before have really repeated. (And this time around I just kept my font changes minor and no gigantic overkill fonts.) Sadly, TitaniumBackup can't restore all apps it seems (it just sort of freezes on some) but overall I've managed to restore most of it. I was waiting to make a backup in CWM until I had fully gotten everything configured and running the way I wanted it. Guess I should have done one sooner, but now I'm close to the original goal of having it basically right where I want it before making the backup (thank goodness TitaniumBackup at least was able to get the bulk of the work. And I love how it can even restore the device ID so that as far as everything is concerned this is the same phone I've always been using.)
It does still have a worse battery life compared to the stock ROM, but I guess it's not too bad. Still better than most phones no matter how you look at it. I'm not entirely sure it wasn't the battery being somewhat at fault though. I was using a third party battery by Anker. By the feel of it, it actually is surprisingly dense for a third party battery -- it weighs about the same amount as the stock battery -- so it might actually have a pretty good capacity, but at the same time I'm not 100% sure it truly is every bit as good. At first it certainly seemed to be, but maybe it's starting to wear down more quickly overall. For now I guess I'll switch back to stock (my original plan was to just store it at some 70% or so capacity so it should last and then punish these two third party batteries, but now I guess I'll consider them to be the backups instead. I don't like that the charge goes as high as 4.33V or so though. 4.2V is supposed to be considered pushing things pretty hard as it is, so I have a bad feeling about the overall lifetime of these batteries...) Again I have SetCPU hopefully helping out a bit (I like that CM10 has options for this that it can set on boot, but it doesn't have any other options than that and I like how I can have SetCPU actually lower things much further while the screen is off. I don't care if some processes take longer to, well, process while the screen is off after all, so there's no reason not to use a lower CPU setting IMO.) Actually, I was beginning to become quite concerned because the battery was actually going down just doing a few basic things like restoring backups while plugged into the charger despite having the governor on conservative, the maximum CPU frequency at 1066MHz, and the I/O set to SIO (which at least one person claims is better, though I wasn't 100% convinced from what little I could tell -- if anyone has any suggestions for the best balance between battery life and performance in this respect I'm curious. I try to keep it on something that kind of scales so that games and such still work fine without me having to change it specifically for each or something while it could still at least not kill the battery when it's not being pushed as hard.)
Interesting thing about the whole WiFi thing. I read on one thread where someone suggested changing the device name (in the developer options) to no longer have a dash in it to stop the intermittent WiFi dropouts. It's kind of ridiculous and should have absolutely no effect whatsoever on this, but so far it actually seems like it might have worked. Again, knock on wood... It's odd though because I never had that trouble with the stock firmware (then again, for all I know it didn't have a dash in its default device name and I doubt I ever changed it if it was even an option though I can't really remember one way or the other if I could have.) I won't know for sure for a while as it was kind of random before, but so far it's looking promising at least. And I haven't had any trouble with it picking up my network yet either.
BTW, I forgot to do the IMEI backup before somehow. Is it too late to for it to be any good now? I know, I know, but I was a bit excited about the prospect of going to CyanogenMod 10 in the first place and just forgot along the way I guess. I went ahead and ran it ("reboot nvbackup" from the terminal anyway -- it sure would be nice if it actually properly shut down first instead of doing a cold reboot -- but other than some tiny blue text in the corner that might or might not have said something to the effect of that it was making a backup it just flashed by and booted up normally. I was expecting a recovery menu or something.) But I don't know if it's going to do any good to have run it now. Is there anything other than the IMEI itself contained in that data that I should be concerned about? I think the IMEI is correct still (I checked the numbers in the settings at least and they seem to correspond to what I wrote down from under the battery) but I'm not sure about anything beyond the numbers themselves.
Nazo said:
Well, I had a small accident. I was replacing some fonts and manually selecting which ones to replace with what when I threw in Arial Unicode and another font that was still slightly large. I'm assuming because the font files were so big, but it completely stopped booting. After fighting with it for hours upon hours (and I have since found what might be a font zip file for CWM now that it's far too late to do me any good -- though of course it would have had to replace those particular fonts and it seems like most of my attempts to replace them ended up replacing everything but them.) I just couldn't get a driver to install for the phone while CWM was running (I don't know if you can maybe get an adb shell or what, but without the driver you obviously can't.) In the end, I ended up having to reformat and reinstall CM10 from scratch. So far (knock on wood) none of the real problems I was having before have really repeated. (And this time around I just kept my font changes minor and no gigantic overkill fonts.) Sadly, TitaniumBackup can't restore all apps it seems (it just sort of freezes on some) but overall I've managed to restore most of it. I was waiting to make a backup in CWM until I had fully gotten everything configured and running the way I wanted it. Guess I should have done one sooner, but now I'm close to the original goal of having it basically right where I want it before making the backup (thank goodness TitaniumBackup at least was able to get the bulk of the work. And I love how it can even restore the device ID so that as far as everything is concerned this is the same phone I've always been using.)
It does still have a worse battery life compared to the stock ROM, but I guess it's not too bad. Still better than most phones no matter how you look at it. I'm not entirely sure it wasn't the battery being somewhat at fault though. I was using a third party battery by Anker. By the feel of it, it actually is surprisingly dense for a third party battery -- it weighs about the same amount as the stock battery -- so it might actually have a pretty good capacity, but at the same time I'm not 100% sure it truly is every bit as good. At first it certainly seemed to be, but maybe it's starting to wear down more quickly overall. For now I guess I'll switch back to stock (my original plan was to just store it at some 70% or so capacity so it should last and then punish these two third party batteries, but now I guess I'll consider them to be the backups instead. I don't like that the charge goes as high as 4.33V or so though. 4.2V is supposed to be considered pushing things pretty hard as it is, so I have a bad feeling about the overall lifetime of these batteries...) Again I have SetCPU hopefully helping out a bit (I like that CM10 has options for this that it can set on boot, but it doesn't have any other options than that and I like how I can have SetCPU actually lower things much further while the screen is off. I don't care if some processes take longer to, well, process while the screen is off after all, so there's no reason not to use a lower CPU setting IMO.)
Interesting thing about the whole WiFi thing. I read on one thread where someone suggested changing the device name (in the developer options) to no longer have a dash in it to stop the intermittent WiFi dropouts. It's kind of ridiculous and should have absolutely no effect whatsoever on this, but so far it actually seems like it might have worked. Again, knock on wood... It's odd though because I never had that trouble with the stock firmware (then again, for all I know it didn't have a dash in its default device name and I doubt I ever changed it if it was even an option though I can't really remember one way or the other if I could have.) I won't know for sure for a while as it was kind of random before, but so far it's looking promising at least. And I haven't had any trouble with it picking up my network yet either.
BTW, I forgot to do the IMEI backup before somehow. Is it too late to for it to be any good now? I know, I know, but I was a bit excited about the prospect of going to CyanogenMod 10 in the first place and just forgot along the way I guess.
Click to expand...
Click to collapse
No your OK you can get your IMEI underneath where your battery is. There's a tutorial on YouTube
Sent from my SCH-I535 using xda premium
Hey,
So its been like 3-4 years since i been big into putting roms onto phones and rooting and such. I just lost my old phone.. fell outta my pocket while riding my motorcycle on the interstate.... Just bought this LG Leon. Its running 5.0.1, and I know I can root in via King, not concerned about the security issues tbh. What I am concerned about is wether or not anyone was able to install Cyanogenmod 12.1 on the phone yet... I can't find anything on it, which can't say as im surprised it being a $100 phone from metro pcs. What I have found is that people were able to root it.
I really want to put Cyanogenmod on it cuz all of the bloat ware on this phone is driving me nuts.... like holy ****, why release a phone thats gonna be slow with all your **** no 1 uses on it.. end rant.
Also anyone figure out a way to make lolipop revert the windows/tabs/recently opened menu from cards to tiles?
There was a CM12.1 ROM available on another forum but the thread was closed due to some complaints from impatient people who weren't getting their free updates as fast as they felt entitled to. I've still got it running on my Leon. Except for a couple of bugs it's been stable for me. The only real issues are that GPS can force a reboot unless permissions are set a certain way and the charging percentage won't report correctly. I'm keeping it because the phone runs much smoother with CM12. I hope the developer doesn't totally abandon it because of some ungrateful people.
I am also running the unofficial cm12,on my Leon, and I plan on keeping it, I hope that the Lept team continues to work on cm for the Leon. I have a question about GPS causing reboots unless permissions are right. Could you explain what you changed to prevent reboots? Thank you.
Set Privacy Guard to 'always ask' for any location based app. Alternatively, you can set GPS to battery saver mode. It makes no sense, but battery saver mode seems to keep the GPS antenna on, without it showing as being on, but it has to be, because my Maps app is dead on accurate when it shouldn't be. The GPS Test app doesn't recognize it as being on but it pinpoints my location, even when there's no WiFi location anywhere around (for rough location). This had not caused a restart, which does happen in High Accuracy mode.
Thanks man