Related
I currently have a Vibrant and I feel like this phone was a total POS until almost 6month later when voodoo lag fix came along and ROMS started to come out that had working GPS, better data, etc etc... If not for the dev community I would have thrown this thing out the window the 2nd time the GPS couldn't find me on google maps...
I love tinkering with a phone, but I also want to start with a phone that doesn't have random reboots, crappy GPS, slow file system lag and all the other crap I had to deal with the Vibrant (and my first android MyTouch 3g)... Althought most issues have been ironed out now, it took almost a year since I first purchased my Vibrant, and I am looking to upgrade either to G2x, Sensation or GSII. Don't want to start a battle which is better, but from what I gathered so far from G2x:
-Screen: hit or miss, some complain about bleed, some say its the best thing ever... seems like the quality control is really a hit or miss with the display
-Data: Won't connect to 4g network, generally seems to be unreliable and signal strength weaker than most phones but has a great GPS
-Battery: Heard there is a battery drain issue, some say its corrected with factory reset?
-Integration: Stock android 2.2? So I am guessing contacts aren't linked together to social network profiles?
-Build Quality: Better than most other phones, rock solid not many complain
-Speed: Looks like its a pretty quick phone for running on an un-optimized OS, will get quicker with updates
Before anyone starts praising and telling me this phones potential and that CM is going to make this awesome, I really don't care... my Vibrant had the potential to not be a total POS either, a year later its somewhat tolerable and right about the time when dual core phones have come out and me starting to look for upgrade. So I guess I just want to know what are some known issues with the phone today that you guys have noticed. I know there is no perfect phone, but I want something that can be tolerable for at least a little while before a custom rom comes out that doesn't breaks more things than it fixes
Me Personnally
I too also came from the vibrants ., and was also fed up with the crappy support from samsung, and that an official cm has still not seen the light of day.
Thats the reason i got the g2x. From what i heard, its completely open. Alot of the top devs for cm have or are getting the phone.
I think the screen bleed is something that everyone is going to have to get used too. I have some bleeds at the corner of my screen too.
Performance wise; without tweaks, just straight out of the box for me, this has destroyed my vibrant with teamweaskys latest rom.
I wont get the sensation because of the locked bootloader, and i am not going to trust or put up with the crap that samsung gave us with the vibrant.
This phone is AWESOME!!!!!!! i am loving it so much.
apart from the screen bleed, all the other issues you see here, are all temporary, i mean real temporary.
Ps
Saw a tweet come in with some peeps already running gingerbread on there gx2
Same Reason why I bought the phoen was because the bootloader is unlocked, but unfortunately this phone has to many other issue's.
timafey said:
-Screen: hit or miss, some complain about bleed, some say its the best thing ever... seems like the quality control is really a hit or miss with the display
-Data: Won't connect to 4g network, generally seems to be unreliable and signal strength weaker than most phones but has a great GPS
-Battery: Heard there is a battery drain issue, some say its corrected with factory reset?
-Integration: Stock android 2.2? So I am guessing contacts aren't linked together to social network profiles?
-Build Quality: Better than most other phones, rock solid not many complain
-Speed: Looks like its a pretty quick phone for running on an un-optimized OS, will get quicker with updates
Click to expand...
Click to collapse
These are my opinions.
-Screen: Yes, some bleed more than others. I think this issue has been blown way out of proportion as it seems the majority of users have to manipulate screen brightness, environment and content displayed on the screen in order to show bleed.
-Data: I only have 2G in my area. When I'm out in 4G areas away from home, I just set the connection to force 4G data and it's smokin' fast, never drops.
-GPS: Most of the time it locks on instantly for me on any Froyo ROM. Sometimes it takes about 60 seconds. If it looks like it's going to take a while, I usually close Maps, open GPS Status & Toolbox to refresh the AGPS data and it'll lock solid again. This should be fixed as soon as Gingerbread drivers are available.
-Battery: Battery is up to par with other Android phones in my opinion. Seems better on any tweaked out Froyo or Gingerbread ROM.
-Integration: I don't use social network/contact integration so I can't even touch on this. Don't know how and not interested. Sorry.
-Build Quality: Good weight, doesn't feel cheap. Generally accepted that it has Gorilla Glass. I have a couple extremely light scratches on my screen, so it's probably a good idea to get a screen protector if you care about such things. I just haven't touched a screen protector I like so I don't use one. I've taken the back off about 15 times and there is now one spot on the phone that if I squeeze, it creaks a little bit. Can't tell with normal use and still feels solid.
-Speed: Stock ROM is a little sluggish but with a couple flashable mods, maybe a kernel, this phone is super fast. I don't even feel the need to overclock. Currently running EaglesBlood Froyo 1.05 with faux's froyo kernel at the time of this writing.
Hope some of this helps you out.
Edit: And with an unlocked bootloader, just flash recovery and start crackflashing away. Love not messing with bootloaders.
Add Randomly REFORMATS to the list. My phone has reformatted itself randomly three times now since i've had it. stock. Once it like forgot it had an OS and just kept looping itself and then installed the OS randomly. Badass phone.
MavrcK145 said:
Add Randomly REFORMATS to the list. My phone has reformatted itself randomly three times now since i've had it. stock. Once it like forgot it had an OS and just kept looping itself and then installed the OS randomly. Badass phone.
Click to expand...
Click to collapse
I can atest this also has happened to me. LG has a class action suit against them, you should all file your complaints.
I made a thread about this because it could give insight as to whether there are deeper hardware issues that could lead to some of these software instabilities;
The 3.5 mm audio jack has very audible noise/hiss on it when the amplifier is turned on (up to 1 second after any sound finishes playing, such as after the tone you hear when changing the ringer volume). This should be completely inaudible if the circuit itself is designed properly and everything is shielded where it should be, and if the components related to power supply/filtering are working properly. If someone could test this (takes 5 seconds) with their good and faulty phones, stock or modded, it may demonstrate something.
More: non-reboot bugs. On pressing the power button to unlock the phone today (3 days since factory reset, 1.5 weeks since buying) the unlock slider is missing, except for the white triangle pointing to the right. Sliding it makes it appear and play the animation, and it appears next unlock.
Another random: Holding volume down until it is vibrating non-stop and then powering down the phone causes some apps to show and do random things after the power down animation plays, before the screen suddenly blanks.
I still urge owners of variably configured G2x's to test for the presence of noise as described in my thread- if LG has hardware problems instead of all software, not everything is safe by modding the ROM. Perhaps the noise is shoddy software coding. The DAC and opamps used here would not create that, only the circuit design.
k00zk0 said:
I made a thread about this because it could give insight as to whether there are deeper hardware issues that could lead to some of these software instabilities;
The 3.5 mm audio jack has very audible noise/hiss on it when the amplifier is turned on (up to 1 second after any sound finishes playing, such as after the tone you hear when changing the ringer volume). This should be completely inaudible if the circuit itself is designed properly and everything is shielded where it should be, and if the components related to power supply/filtering are working properly. If someone could test this (takes 5 seconds) with their good and faulty phones, stock or modded, it may demonstrate something.
More: non-reboot bugs. On pressing the power button to unlock the phone today (3 days since factory reset, 1.5 weeks since buying) the unlock slider is missing, except for the white triangle pointing to the right. Sliding it makes it appear and play the animation, and it appears next unlock.
Another random: Holding volume down until it is vibrating non-stop and then powering down the phone causes some apps to show and do random things after the power down animation plays, before the screen suddenly blanks.
I still urge owners of variably configured G2x's to test for the presence of noise as described in my thread- if LG has hardware problems instead of all software, not everything is safe by modding the ROM. Perhaps the noise is shoddy software coding. The DAC and opamps used here would not create that, only the circuit design.
Click to expand...
Click to collapse
I don't even think I own a pair of headphones anymore... hahaha. I'll try this with a set of powered speakers as soon as my children let me.
Wow I was going to buy G2x. Can anybody answer about 4G data part who use it on regular basis? Is it really not reliable?
I was thinking of upgrading from HD2 to g2x mainly because of 4G and front camera, but if 4G is not properly working on this one, I have to select some different phone then..
I've tried most ROMs that are out for the MT4g, and I can say there is a massive variety. I really love the ability to fly between ROMs like this, but there is one glaring fact that I can't get by: they each have very evident weaknesses.
Yesterday, I flashed MIUI for the second time. The first time didn't last long - I quickly reverted to whatever I was using before, probably CM7 or VU. This time, however, I immediately became enamored by its quickness. Responsiveness I had only found on iDevices previously was very evident - and after installing launcherpro, I had the smoothest and most enjoyable surface-level device you could ask for. Polish was very evident in many parts (The two-pixel tall battery meter that would be above the notification bar was quickly a hit with me.) However, I quickly learned that it was not entirely translated from Chinese - the search button from the homescreen would produce only Chinese results. The registration for MIUI's built-in services was built around Chinese websites. On top of these evident, but manageable, issues, I noticed that music would randomly skip, sometimes multiple songs at a time. This issue kept reappearing in third-party music apps. Also, netflix was plain awful. A notification would lag the video and make the audio be out of sync. And that was only when the video actually worked. I ended up switching ROMs this morning when I accidentally turned screen brightness down to the lowest setting which made the screen permanently black, which for some reason has no method to fix. I was not willing to set everything up again.
Of course, before this I had to have a reason to switch from another ROM, right? CM7 has been my go-to for an acceptable Android experience. It works, but has a good number of rough edges, and isn't the smoothest experience ever. It does, however have many aspects that are universally compatible with almost every other Android device on the market running the same ROM, like the theme manager. Updates come almost every day if you are willing to flash a ROM every once in a while. Under the right circumstances, it is pretty speedy. My dealbreaker with it is poor radio performance. I don't know how MIUI would fit in with radio performance, as I was only on it for a day. Sense ROMs seem to have exemplary radio performance. CM7 randomly drops Wifi and is on edge where sense roms would have one or two bars of HSPA+. In addition, it takes longer for CM7 to actually connect to data services when you want to connect to a webpage or something.
My second most common ROM is Virtuous Unity. I think it has some cool eye candy, and has awesome data performance. Unfortunately this is as far as it goes for me. Sense is bulky. Really bulky. Looking at the built-in process manager shows a constant use of 4/5 of the RAM. This is not OK. I could quickly notice that the graphics performance for everything other than the launcher and certain built-in apps quickly decreased. The same apps would run smoothly on a ROM like CM7.
I guess my point is that it has been a while in the development for this device. Why hasn't anyone made a ROM that can pull the best aspects of these together?:
-The visuals and ludicrous responsiveness of MIUI
-The low resource consumption and crazy customization like CM7, as well as generally good compatibility with media apps
-The outstanding radio performance of Virtuous unity and other Sense ROMs
Maybe I'm completely in the dark here on why this might not be possible. Let me know if there's some ROM that I haven't tried yet that comprises these features and you may have found me my new daily driver.
I don't really know what to say to help ya out.
Running MIUI was fine for me, I never saw any Chinese and I ran MIUI for 2 months straight back in the summer. And the notifications never lagged apps, it bugged me when i was on Navigation, but I would turn that pop up off.
Sense ROM's were fine for me as well, I never experienced the bad graphics that you're talking about. I always played games and everything was fine. Sense always takes up more RAM but that's never an issue, even with Sense 3.0 ROM's you're still left with 100mb's or so. Even with 4/5 of your RAM taken that's not a problem as unused RAM is wasted RAM anyways.
And as for CM7, it's always my favorite and "go-to" ROM. It's always smooth and buttery for me 24/7 and has never slowed up on me. Wifi never drops on me and I get the same radio reception that I get on Sense ROM's.
Maybe you have certain apps installed or something that's causing you to have these weird problems with CM7 and Sense. As for MIUI, I never saw Chinese lettering so now sure how I can respond on that one.
I'm on Miui and I love it. You can overclock it and even undervolt a little too if you want but even overclocking the battery life is still really good.
Sent from my HTC Glacier using XDA App
on miui right now and pretty content with myself
never saw chinese either personally, and never really felt like i needed to go to the miui site for any support, this place has been great for any issues i've had
as for the screen blacking thing, this is a known issue and is fixed by sliding the "trackball" to the right to bring the brightness back up or knowing where the brightness button on the settings page is.
and i personally feel GPS locks on faster in miui then it does when i was on tdj's 3.5 port. i unno, it took awhile for gps to lock on that but in miui it locks on so quickly lol
if you are really having that hard of a time getting full functionality out of the ROMs you are installing you are doing it wrong.
darinmc said:
if you are really having that hard of a time getting full functionality out of the ROMs you are installing you are doing it wrong.
Click to expand...
Click to collapse
Everything the OP is talking about is opposite of my experience.
My radio works fine. GPS is zippy on the new leak.
I watch netflix at work ... Ive been through 6 documentaries and 28 episodes of Man Men.
MY experience with all the mentioned ROMs have been great.
If you dont do the recommended steps or do additional research Im gonna have to "+1" the comment above.
Sense: loved the flow of functions, hated the animations & batt life
CM7: Loved the reliability and speed, hated the blandness
MIUI: Love the themes, speed and batt life. Hate the contact manager
(I make my UI look sleeker and more sophisticated than an iphone)
People that dont like it because it looks like an iphone or acts like one is because you let act like one or look like one. You gotta understand all the eatures to appreciate it
MIUI.us has been my everyday ROM for over 2 months now. The only concurrent issue with it is with MIUI Music, where it would entirely lock up the phone even when I followed the advice and disabled certain options in the app that "helped" solve the problem.
Other than that, I haven't seen anything else wrong with it up to this day. I use my phone a whole lot, meaning I watch a lot of youtube videos on it, and even HD TV Shows (Go Kamen Rider Fourze!! ) without any problems whatsoever.
Check out the Doubleshot port if you want to swich to something different every now and then. It's pretty good as well, works great!
Give MIUI.us a second chance, just make sure you wipe everything beforehand. Check everything out and you'll be happy enough once you use it for a while longer, you'll see.
Right now I've got the latest BeatMOD BlissSense ROM with Beats Audio and it's an okay ROM, with the same downside as most Sense ROMs, it is a bit slow here and there.
[EDIT] Oh yeah, about the radio reliability, I've got the best radio results with CM7 and AOSP ROMs. Have you tried flashing the Panache Radio ROM to see if it helps?
Well, that's my two cents
For the Chinese search results hit the search button then menu then change the default search engine.
The only other Chinese I saw was in the themes app, but I find it much easier to get themes from English forum sites.
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
The only thing I really don't like about the Galaxy S4 is that the vibration is fairly weak. Working in an office I need to have my phoen on vibrate as a colorful ringtone is simply not an option. But I miss text messages and phone calls on occasion because I just don't feel the phone vibrating in my pocket.
Heck even if I have it laying on a nearby table sometimes I still don't hear it vibrating.
I have come up with a sollution acceptable work around to this issue!
I made a vibration sound as my ring tone. So now when the phone vibrates it also goes BzzzBzzzBzzz out of the speaker.
It's barely loud enough to be heard by anyone but you if it's in your pocket. If anyone else does hear it, it still just sounds like a normal vibrating phone. No obnoxious ringtone.
If you want to try this out I've included 3 WAV files in the attached zip.
- Base Vibration Sound.wav - This is the sound file I used as a base for the final ringtones I made. I have scoured the internet looking for vibration sounds. This one is the one that sounded most like an actual vibrating phone. Use this file as your source if you want to try this technique out but don't like the final products I created.
- Ringer Vibration.wav - I added some bass and increased the volume, and extended the length of the original source file so make a loud, long, steady vibration sound that is roughly the length of a normal incoming call vibration.
- SMS Vibration.wav - Same bass and volume changes as the Ringer Vibration, but it's 3 short bursts insead of one long steady vibration. I did this because 3 short burts is how I've always set my my SMS vibration sequence. There are pauses between each vibration in the squence so you can hack up he file and change the vibration pattern as needed easily enough.
Hopefully this idea helps someone else.
Note, I still have the phone vibrate and ring in settings so it still vibrates. The vibration sound is jus in addition.
This is still a work in progress for me. So if you can improve on it please do and share your version here! If there are any real audiophile geeks out there who can make this sound really good, please share your talents! I am NOT an audio guy by any means. I just found a vibration sound file online and modded it with a little cutting and pasting and enhancement options using a free program called Audacity on Ubuntu. So if someone has and knows how to use high quality audio modification software to do this properly, by all means please show us what youv'e got!
Wow, thinking "out of the box"! Good sh*t! Another way to strengthen ur vibrate is through ktoonesz kernel, in the extras menu (ktweaker, comes with the kernel), you can change the strength.
norml said:
Wow, thinking "out of the box"! Good sh*t! Another way to strengthen ur vibrate is through ktoonesz kernel, in the extras menu (ktweaker, comes with the kernel), you can change the strength.
Click to expand...
Click to collapse
I use CyanogenMod for the T Mobile variant (I have a 919) and it has a feature to let you increase the strength of the vibration. But even at it's max it's not that powerful.
Does hat ktoonesz kernel make a significant difference for your variant? I don't have access to the kernel but I can certainly get devs to port that mod to 919 kernels if it works.
I think the problem isn't how much power that is sent to the vibration motor. It's that the unit itself doesn't vibrate much.
If you've never seen one, all a vibration unit is is a small electric motor with a lopsided weight on the end so it wobbles when it spins. When it spins fast the wobble becomes a vibration.
The S4 vibration unit (I'm trying REALLY hard not to call it a vibrator....haha) simply doesn't have a very lopsided weight on the end of the motor. So it doesn't wobble much.
I never messed with it, I just use his recomended settings (except for oc)...it ranges from 15-125. I'll mess with it and see for you. As far as a kernel goes, it's the best imo, never fc my phones unless I oc it to the max, which is 2.3 I think, I can oc to 2.1 with no problems. The incredible part is that it is great on the battery, even oc'd, i get better battery life than stock, weird imo, but I'm still very new to all this.
VIBRATOR check, LOL, didn't seem to change at ALL, felt the same, I have seen a lot of ppl commenting on it though, on how it works. You mentioned you don't have axx to it? You mean to work on it?
norml said:
I never messed with it, I just use his recomended settings (except for oc)...it ranges from 15-125. I'll mess with it and see for you. As far as a kernel goes, it's the best imo, never fc my phones unless I oc it to the max, which is 2.3 I think, I can oc to 2.1 with no problems. The incredible part is that it is great on the battery, even oc'd, i get better battery life than stock, weird imo, but I'm still very new to all this.
VIBRATOR check, LOL, didn't seem to change at ALL, felt the same, I have seen a lot of ppl commenting on it though, on how it works. You mentioned you don't have axx to it? You mean to work on it?
Click to expand...
Click to collapse
No I mean that kernel just runs TW roms, doesn't it? Or am I thinking of a different one?
I always run CM/AOSP ROMs and never use TW
Skipjacks said:
No I mean that kernel just runs TW roms, doesn't it? Or am I thinking of a different one?
I always run CM/AOSP ROMs and never use TW
Click to expand...
Click to collapse
He has Touchjizz and AOSP. NEW ver got rls'd today as a matter of fact.
file link http://goo.gl/AWZK5
OG thread http://forum.xda-developers.com/showthread.php?t=2289140
norml said:
He has Touchjizz and AOSP. NEW ver got rls'd today as a matter of fact.
file link http://goo.gl/AWZK5
OG thread http://forum.xda-developers.com/showthread.php?t=2289140
Click to expand...
Click to collapse
I've been using Albino's ChronicKernel. Its also really good if you want to try that out.
Sent from your phone. You should be careful where you leave that thing.
There are a few silly issues I'm having with the phone and I just want to find out if anything can be done, for my sanitys sake.
I hate the way the screen lights up when I plug my headphones in.
I hate the fact that the countdown timer will vibrate only in vibrate mode (unlike my M7 which made a noise) but when not in vibrate mode it was only make a noise. I guess it makes sense if you think about it, but to me, its nonsense. I want it to vibrate AND make a sound in either mode, hell I'd even take sound+vibrate in ringer on mode at this point. So I can be listening to music and the timer goes off (in vibrate mode) and if I don't feel the vibration in my pocket, tough. Hard to explain, but I have to call back to the HTC M7, it didn't do this, it worked.
I hate the way that the alarm clock has increasing volume only once. If you snooze the phone, the next time the alarm goes off, it goes off full blast, no increasing volume.
I've been using XtreStoLite Deo-Mod Edition 2.4 rom with a week or so now and it's great. But I have noticed some issues which really worry me. I got this phone because it's fast. But when I press the power button there is a definate delay until the screen lights up and Facebook messenger for reasons unknown makes the phone unusable, it lags so bad and even the soft keys don't work. Never did this on other phones and my partners non-rooted S6 is fine.
It does make me wonder, is all this rooting and custom ROM worth it. So far, I've got odd lag and an app which nearly breaks the phone. If I could adblock and restore apps without rooting, I think I would unroot.
Then sell it and be happy
What is your question exactly then?
jody2k said:
Then sell it and be happy
Click to expand...
Click to collapse
Can we automate it so your response is posted for every thread talking about issues with this phone?
My Question is, are any of my issues "fixable". I know xposed could do a lot of things for the M7. Is there something I've missed which can help me with my issues?
X82X said:
Can we automate it so your response is posted for every thread talking about issues with this phone?
My Question is, are any of my issues "fixable". I know xposed could do a lot of things for the M7. Is there something I've missed which can help me with my issues?
Click to expand...
Click to collapse
Chill i was making a joke
Have you tried full wipe? Or completely unroot to stock? Then back?
I have.
My Mrs has a unrooted stock S6 which I use for comparison.
The lag issues and issue with Messenger are only my phone, the isues I have with the screen lighting up with headphones plugged in and the alarm clock, we both share those.
I know the lag and messenger issue could be fixed by going back to stock, but this is the problem with custom roms and rooting. You get given nice features and you risk losing them all when going back to stock. I can live without messenger and the wake up lag I can just put up with, but it isn't right. I guess in truth I expected too much from this phone, I wanted it to be blazing fast and it just doesn't feel it.
There isn't a great range of roms either, my M7 had literally dozens of roms to try but I find with the S6, there are like only a handful.