Related
Undoubtedly this is the hottest topic on this forum (so it seems). Based on what I have seen, there has been no convincing proof on either way. The benchmarks score comparison are great, but my belief is it may not reflect day to day experience as most of time you never push the system to its max.
So my hypothesis is Transformer Infintiy's I/O issue related user experience can be fixed by software even if the underlying issue had been hardware related.
Since some people believes the opposite, and this is infinity forum. I wanted to make myself right for the sake of infinity owners. But given no previous good convincing test, I have decided to test one thing.
First video
This is one example video that Anandtech showed back in July that Infinity is indeed experiencing I/O issue. This video simply proved that while I/O is in use, the whole system slowed down. Based on the date of this post, which is 7/26/2012, I am assuming the firmware used was V9.4.5.22.
Second video
The credit of this video goes to BarryH. The reason why I included this is Galaxy note 10.1, which I owned for 3 weeks should be used as gold standard in this comparison as it is perhaps the only worth mentioning competition of TF700T and it is really great tablet of its own. You can clearly see that the downloading file in background really had no effect at all on the Galaxy Note 10.1.
Third video
The above is my very first Youtube video ever. But that's not a point. This is running stock ROM, rooted. No build prop tweaks. The only special thing I have installed here is Browser2Ram. So for this basically, I used AirDroid (WIFI file transfer application) and transferred 1G+ file over my network. While doing so, I basically opened browser, and went to the same site as Galaxy note 10.1 did in above. The little delay after opening browser is not hang in browser, but simply I forgot to set to landscape mode.
Conclusion: Based on these I believe I can conclude followings:
Compare first to third. Infinity had already significantly improved its I/O performance. How did it do? Clearly not by changing hardware, but rather software. So this proves my hypothesis of software can indeed fix I/O issue that user actually see.
*Please note that since I have browser2ram installed, this may be different for pure stock user experience. And Zeus users may even have better experience than me.
Special thanks goes to BarryH_GEG. Without him posting first two youtube clips I wouldn't have actually realized that Infinity's I/O issue had already been nearly completely fixed on my unit.
.
For clarification, basically all I am doing here is that there is indeed a way that what we call IO issue that can be alleviated by software modification. So if anyone state its all hardware and can never be fixed/improved, that is incorrect statement. However, this does not prove stock Infinity in the future will receive such update. So you can have a hope, but hope has no guarantee.
Different people use device differently so I say try the device and update to the latest firmware and see if you still face the IO issue that is significant enough for you. I can say that it is definitely not as bad as first video show. Whether you can tolerate the IO lag or not is simply your personal preference. In the end, all devices have lag to certain degree when stressed. Even PS3, Xbox 360, or high end PC games gets frame drops when you stress them. The question is whether you care, and whether you push to the limit.
If I ever get chance, I will try to turn off Browser2Ram and try do the same test again and see what the true stock experience is, though I am certain it is not as bad as Anandtech video.
Update 9/24/2012
Since some people are pointing to the issue resolution is purely due to Browser2Ram, I did same test with this time while AirDroid transferring 1.1 GB file over the WIFI, I launched Final Fantasy 3. No lag even while launching. Everything is smooth. However, if I launch Horn instead of FF3, I did notice significantly longer time to load. So this is simply proving what I have said. We can fix issue to certain degree but whether the certain degree is enough for a specific user is really dependent. I am ok not being able to play Horn while I am transferring 1GB data, but some may not.
Of course Browser2RAM will help on this, you're caching to just RAM instead of the stupidly slow NAND memory Asus decided to put in their flagship device. Try the same "test" on complete stock and you'll see that it's a vastly different experience.
Zeus ROM works around the I/O issue by reducing or even eliminating SQLite fsyncs. Risky business for your data, good for performance. I like my data without corruption, so I'll pass, but others may not see it that way. They simply want the performance this tablet should have had in the first place.
Asus did reduce the overall sluggishness slightly with the .26 update that changed from NOOP scheduler to CFQ in the kernel, but the tablet still stutters. Browsing is far from smooth, even with alternative browsers like Dolphin HD. Performance is decent right after a reboot, but once memory fills up and Android starts its memory management and closing down processes (doing a lot of fsyncs in the process) it grinds to a halt. This wouldn't be a problem if flash I/O performance was higher.
The CM-based ROMs starting to pop up for the TF700 seems to help on the performance as well, and that's still with the 2.6.39.4-based kernel. CM's always been smoother than pretty much any stock device in my experience though, so no surprise there. They can never completely get rid of it though, since it's a hardware issue. Asus were stupid and chose cheap, slow NAND that gets totally crippled if you're doing random writes. There's no magic software to just fix it.
I'm sorry, but I don't really see anything new here, and your "evidence" isn't really that, simply because you're not running stock. You're using Browser2RAM which greatly increases browsing performance by using RAM, which is several magnitudes faster than NAND flash. It's not even comparable. The TF700 (and TF201 and TF300 and TF101) I/O issue can never be completely fixed in software, only (slightly) improved, often at the cost of data safety (disable SQLite fsyncs or available RAM (Browser2RAM).
It's all well-known by now that Asus ****ed up (again!). If it weren't for the oh-so-sweet high resolution display and keyboard dock I'd get a different tablet.
Einride said:
I'm sorry, but I don't really see anything new here, and your "evidence" isn't really that, simply because you're not running stock. You're using Browser2RAM which greatly increases browsing performance by using RAM, which is several magnitudes faster than NAND flash. It's not even comparable. The TF700 (and TF201 and TF300 and TF101) I/O issue can never be completely fixed in software, only (slightly) improved, often at the cost of data safety (disable SQLite fsyncs or available RAM (Browser2RAM).
It's all well-known by now that Asus ****ed up (again!). If it weren't for the oh-so-sweet high resolution display and keyboard dock I'd get a different tablet.
Click to expand...
Click to collapse
Hi Einride,
Sorry if I directed you wrong way. But my point here is not to prove stock has already fixed issue or not even to say IO issue can be completely fixed. The latter is simply unknown. But I am just proving here that there are ways software can make difference in user front, which some people questions.
To be honest, how do you even know RAM is not bottle neck? What about GPU, which is far inferior to the new Ipad in fact its even worth than iPad 2 by far margin? We see a number, and see its less than others so concluded its the conundrum, which could be true by good chance but not a proof.
Here I am basically proved whatever the method is, there is a way to improve what people call IO issue can be alleviated by software approach.
Because Anandtech showed IO issue originally on infinity stating background 2MBps download resulted in marked degradation in browser performance. I basically had 1GB file transfer over WIFI using Airdroid.
So I basically proved here that my infinity, which clearly has not touched anything on hardwarewise, but have improved performance since Anandtech review.
As for Zeus fsync, I don't use Zeus so cannot speak for it. But if they turn off fsync and still keep the system stable without data loss, why would you care?
Having said all this, I don't know if ASUS will ever put effort in fixing issue because if they would why won't they simply install browser2ram as part of their firmware? But they are doing something as I noticed they took out pixit from background with latest firmware, which kept running in background for no reason..
Einride is on target. This is a hardware issue, so any "fix" is going to be a kludge and come with a bunch of compromise. I can't believe ASUS specced the same crazy slow flash on the 700 that they did the 201/300.
FWIW, The best/cleverest hack I have seen is the TF201 dev who has been playing with remounting the internal SD card to point at the removable microSD card. If this can be made to work smoothly, it means that if you have an external card that is specced much higher than the stock internal flash you could eliminate the issue completely.
But of course that is really hacky. It's one of those you could brick if you don't install it right kind of deals so I don't ever see it being a mainstream options for these tabs unless ASUS productized it which would be a big expense in support for them, so, again, it'll never happen.
I've got to push back a bit. I think this is firmware related, but not of the device of individual components. I think this can be fixed with "software"
tf201 said:
I've got to push back a bit. I think this is firmware related, but not of the device of individual components. I think this can be fixed with "software"
Click to expand...
Click to collapse
You can continue thinking that if it makes you feel better. I like and enjoy my Infinity but as a digital design engineer, to me this seems to clearly be a design issue @ the hardware level and will always limit the overall system to some degree. There are hard limits in any hardware software system. <Shrug>
My best advice to an end user is what I would give for any device issue: to decide whether it is a deal breaker for you *as it stands right now* and not sit around and wait for or bank on some kludgy cure that may be worse than the disease.
It's not too bad for me, I don't do tons of random I/O or web browsing. In fact, I'd say it would have taken me a long time to notice this on my own without the benchmarking and threads here... If it was unacceptable I would cut my losses and sell the tab and get a different device. Life is short, guys.
zenaxe said:
Einride is on target. This is a hardware issue, so any "fix" is going to be a kludge and come with a bunch of compromise. I can't believe ASUS specced the same crazy slow flash on the 700 that they did the 201/300.
FWIW, The best/cleverest hack I have seen is the TF201 dev who has been playing with remounting the internal SD card to point at the removable microSD card. If this can be made to work smoothly, it means that if you have an external card that is specced much higher than the stock internal flash you could eliminate the issue completely.
But of course that is really hacky. It's one of those you could brick if you don't install it right kind of deals so I don't ever see it being a mainstream options for these tabs unless ASUS productized it which would be a big expense in support for them, so, again, it'll never happen.
Click to expand...
Click to collapse
Well, again (and I now added to opening post) my point is not denying IO hardware issue existence. I am just simply providing proof here that it can be improved by software (to certain degree). Whether it is to the extent of users complete satisfaction would be different issue. However, to be honest, if you see my video and it was original retail packaged Infinity fully on stock and from the day 1 performance, don't you think less people would raise a voice? It's because software workaround can change what you see as user, and that's all I am proving here. So yes. this should give a hope to someone who thought, it's hardware related so never can be fixed. However, this does not confirm or deny ASUS to take a step and fix this because I am sure it will take some effort on their part, which clearly they have not spent so far if this had been a problem existed since TF201.
To put into extreme, they can modify OS such that all front end basic programs such as stock browser, movie player or whatever to actually run on RAM if that is what makes the difference. But would they do it? Absolute not, because they won't spend money on such big project for device that had already sold well and gained essentially best Android tablet metacritic reviews (I did not take actual poll but just following Infinity news daily, it seems like pretty much most site gives the highest score for android tablet).
So yup. I don't disagree with you guys that IO issue there. But my point here was to help people clarify that there are indeed ways to make better by software. Whether happens or not is out of my control and would simply be guess for anyone.
I'm not just a noob either. Here's why I think this is software related:
1) The performance is so bad that it precludes just the hardware. Maybe the hardware sucks but there is alot of performance lost somewhere cheap NAND from 2 years ago outperforms SQLite operations by >10x.
2) Performance seems to degrade with time. This is indictive of a wear leveling and writing algorithm which may or may not be able to be adjusted with firmware.
3) SQLite fsync performance appears to be tied to T3 frequency, that suggest there is something with the T3 drivers that could be tweaked vs NAND hardware limitations.
4)...
I'll also mention the OP is right. ASUS could do things with caching data before writing, and writing in chunks the NAND is best with limiting Virtual Ram etc.
HoushaSen said:
Hi Einride,
Sorry if I directed you wrong way. But my point here is not to prove stock has already fixed issue or not even to say IO issue can be completely fixed. The latter is simply unknown. But I am just proving here that there are ways software can make difference in user front, which some people questions.
To be honest, how do you even know RAM is not bottle neck? What about GPU, which is far inferior to the new Ipad in fact its even worth than iPad 2 by far margin? We see a number, and see its less than others so concluded its the conundrum, which could be true by good chance but not a proof.
Here I am basically proved whatever the method is, there is a way to improve what people call IO issue can be alleviated by software approach.
Because Anandtech showed IO issue originally on infinity stating background 2MBps download resulted in marked degradation in browser performance. I basically had 1GB file transfer over WIFI using Airdroid.
So I basically proved here that my infinity, which clearly has not touched anything on hardwarewise, but have improved performance since Anandtech review.
As for Zeus fsync, I don't use Zeus so cannot speak for it. But if they turn off fsync and still keep the system stable without data loss, why would you care?
Having said all this, I don't know if ASUS will ever put effort in fixing issue because if they would why won't they simply install browser2ram as part of their firmware? But they are doing something as I noticed they took out pixit from background with latest firmware, which kept running in background for no reason..
Click to expand...
Click to collapse
No misleading here, don't worry
You are just describing software workarounds, though. None of which can permanently fix it entirely since it's a hardware limitation.
A proper "fix" would greatly increase I/O performance with no downsides. Browser2ram helps browsing, nothing else. Disabling SQLite fsyncs increases risk of data corruption or data loss at the cost of better overall performance.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
tf201 said:
I'm not just a noob either. Here's why I think this is software related:
1) The performance is so bad that it precludes just the hardware. Maybe the hardware sucks but there is alot of performance lost somewhere cheap NAND from 2 years ago outperforms SQLite operations by >10x.
2) Performance seems to degrade with time. This is indictive of a wear leveling and writing algorithm which may or may not be able to be adjusted with firmware.
3) SQLite fsync performance appears to be tied to T3 frequency, that suggest there is something with the T3 drivers that could be tweaked vs NAND hardware limitations.
4)...
I'll also mention the OP is right. ASUS could do things with caching data before writing, and writing in chunks the NAND is best with limiting Virtual Ram etc.
Click to expand...
Click to collapse
I agree that they can probably make improvements with these kind of tweaks. The extent of the fix will always be limited by the low spec hardware in the end, though. So, I wouldn't encourage people to expect ginormous strides. For the most part, I expect more of the same with some evolutionary improvements but I doubt they will ever make a quantum leap. I would be angry if they made it worse but I'm an optimist at heart so I at least expect some slow improvement over time.
IMHO, as it stands it is usable and I'm hoping they can take it to "decent" (say the level pepole are seeing in Zeus). But to folks who are banging their heads against this constantly and unsatisfied as a result, I would still say there will be no true fix and you should bail on this device. It's a personal choice.
If you are willing to forgo your warrantly, I guess you could demo one of the custom ROMs. That probably shows you the extent of a software fix. But beware some of those fixes (cached writes) do put data integrity at risk. There is always a trade off.
Einride said:
Disabling SQLite fsyncs increases risk of data corruption or data loss at the cost of better overall performance.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
If I understand the fsync thing correctly it can only cause issues if the device suddenly powers off, correct? While that may be a risk, it's a *very* small risk and well worth the performance improvement, in my opinion... I've used ROMs that disable fsync for quite some time and have never had a single issue...
I tend to go by real-world results instead of "theory"...
Same thing with "browser2ram" - it can only cause an issue if the device suddenly powers off and even then - so you lose some web cache data - so what?? Who cares if you lose your browser cache - it's just a browser cache!
Besides, if your device is powering off suddenly, you have much bigger problems than worrying about your cached web data!
I truly agree with the OP. People get so caught up on benchmarks and "what could happen" (even though in practice, it really doesn't)... Truth is, we all just want a better end-user experience - if they can "work around" hardware limitations via software then it makes sense to do that.
Obviously, the hardware isn't going to change, so complaining about that will never help whereas implementing software tweaks to work-around these hardware limitations *does* actually help...
Just my two cents!
By the way, I've been *very* happy with the performance of my TF700 since installing the Zeus ROM - another perfect of example of someone using software to get around the hardware limitations - and it works very well! Another example of "real world" results - that's all of the evidence that I need!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Unfortunately random reboots are not simply theory in case of the Infinity, especially if you're doing some memory-aggravating stuff on yours. I'm getting one every few days.
d14b0ll0s said:
Unfortunately random reboots are not simply theory in case of the Infinity, especially if you're doing some memory-aggravating stuff on yours. I'm getting one every few days.
Click to expand...
Click to collapse
While I agree that random reboots are not simply theory, what does that have to do with what we are talking about here?
However, since you brought it up, I've personally never had a single random reboot on my TF700, which may be yet another example that most of this stuff can be fixed by software (since that does not occur on Zeus ROM)... So that just goes further to illustrate my point. I'm assuming that you are not running Zeus?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
jtrosky said:
another example that most of this stuff can be fixed by software (since that does not occur on Zeus ROM.
Click to expand...
Click to collapse
This is from the Quadrant thread. The rest of the conversation describing what SQLite is and the role it plays in overall IO performance is in that thread. All Zeus' ROM does is tweak the SQLite settings and if you read more in the other thread you'll understand why that plays a relatively minor role in overall IO performance. Bottom line is whether or not someone has memory and/or IO issues is more determined by what they do with their device than the s/w running on it. Which is why some people running stock are perfectly content while others are pulling their hair out.
P.S. - Sorry HoushaSen, the lack of information on what SQLite is and the obsession with Quadrant brought me back in to the discussion.
BarryH_GEG said:
To show you what Zeus' impact is, here's a comparison to a Note and TF300 on JB. Red is perecent slower than the Note, green faster. After tweaking SQLite, the remainder of the TF700's IO scores remain significantly below that of the Note (or SGS3 or One X) and some are worse than stock. If you use the TF300 on JB as a proxy for how the TF700 would perform after the update the column on the far right shows the difference between the two.
Click to expand...
Click to collapse
Wait until you see Zeus on Jelly Been. It's going to be so smooth and snappy and you will never think about I/O issue again!!!!
BarryH_GEG said:
This is from the Quadrant thread. The rest of the conversation describing what SQLite is and the role it plays in overall IO performance is in that thread. All Zeus' ROM does is tweak the SQLite settings and if you read more in the other thread you'll understand why that plays a relatively minor role in overall IO performance. Bottom line is whether or not someone has memory and/or IO issues is more determined by what they do with their device than the s/w running on it. Which is why some people running stock are perfectly content while others are pulling their hair out.
P.S. - Sorry HoushaSen, the lack of information on what SQLite is and the obsession with Quadrant brought me back in to the discussion.
Click to expand...
Click to collapse
No problem. In the end this is still gray zone that (at least in my opinion) nobody knows what the end result is, and I think you stated well. It's really depends on user experience.
For those missed my last couple line update on opening thread. I actually had 1.1GB file download going on my infinity, and launched FF3 game, which was a breeze. No lag. So IO issue had been fixed partly from original already (assuming IO was really poor from get go, but I cannot confirm this because I do not have original firmware, and did not play FF3 when I had one). But I definitely noticed significantly far less ANR, which was one major reason I originally returned my infinity and hesitant to come back from Galaxy Note 10.1. However, if I launch Horn instead of FF3, it takes forever and even got ANR, which I hadn't seen for a while on my Infinity. Whether this is related IO or memory cap of 1GB or some other internal limitation is unknown, but since all I had was AirDroid transferring file and Horn is only other thing running, I am assuming 1GB is sufficient; hence, most likely related to IO issue. But having said this, how many would really complain about this? Not sure. Because even on my PC (which is not that high end) but I can basically get same issue. If I encode video and try to run high graphic PC game, the machine stalls, and even gives freeze. Would everyone complain about this? Some would and say that's why you get better PC. The other accepts it is what is, and simply don't encode, and play high end game at same time.
I am pretty satisfied with Infinity as all the concern I had before coming back to Infinity from Note seemed to be solved (at least for me) and got back to Full HD screen; however, there are clearly still people out there concerned of IO performance thus the topic continues to arise. Once everyone gets satisfactory IO result, I believe we will see significantly less discussion about this (if ever happens).
The fact we know are:
1. IO hardware on Infinity is last generation and not as fast as main stream current generation expensive tablets.
2. Software can change what user see (whole point my this particular thread)
Fact nobody knows
1. Degree of how much software can change user experience. Whether enough to completely hide relatively poor performance of underlying IO hardware. Or opposite extreme is basically just soften up a little without true effect on most users.
2. Whether ASUS will even try fixing it.
Benchmark number is great to assess, but I really don't think that's what users are really interested unless someone who just want to say "hey my benchmark score is high!" If this is the case, nobody probably would ever get Apple because they are usually not after benchmark of individual component but rather they use decent hardware, minimize bottleneck by deciding all the hardware on their own, and write optimized OS. But individual pieces are not cutting edge for its price.
And in all honest, I am a bit lost at this point after writing this thread, what is it exactly that we are calling IO issue? Browser2Ram improved my browser speed but even Final Fantasy 3 runs fine from launch while I download a big file at its maximum speed. So I don't think it's browser2ram that did trick here, but rather ASUS already fixed IO issue for downloading file completely hogs the system. If the issue is slow stock browser, that may not be IO related. It may simply be ASUS did not optimize the stock browser. Maybe my system runs so well because I have turned all the bloatware off and many stock user aren't?
I don't see Browser2ram in the store. Got a link?
Sent from my Rooted TF700T
i wish i saw this thread before i bought my Infinity + screen protector + case.
hope that JB will help with some of this, but i didn't realize it was just cheap-ass NAND.
ugh.
xPSYCHOTRONx said:
I don't see Browser2ram in the store. Got a link?
Click to expand...
Click to collapse
http://mark-tech.blogspot.com/2012/06/browser2ram-fixes-transformer-prime.html
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
I am going to post what recently happened to my D850 G3 and see if anything similar has happened to others.
Now before I tell what happened to my phone, judging from the past posts I've made generally one of two things will occur.
1. Nearly all forum members who read it will ignore it and move on. (That's expected, if it didn't happen to them why respond?)
2. Those members (with the exception of the civil-mannered ones) who have post counts in the thousands will respond back with an inappropriate comment.
The civil-mannered ones usually always will respond with a suggestion or viewpoint which helps me understand the issue.
[This site is supposed to be about sharing knowledge and helping others, and I realize the "goober factor" does come into play at times.]
My phone got REALLY hot a couple of weeks ago and died. Sent it back to LG repair facility in Ft. Worth TX.
I got it back this last week and the tech stated on the paperwork that came with the repaired phone that the 32GB NAND flash memory chipset was replaced.
When I went online to see exactly where this chipset is located in the phone, it was the location where all the heat was coming from.
I am not a newcomer to computers and their associated hardware and I realize that smartphones are a different beast, so to speak. I've experienced and diagnosed hard drive failures, motherboard and DIMM RAM failures, CPU failures, CD/CD-R RW/DVD DVD-R/ failures, and so on. I have custom built over 50 computer for myself and customers, I have diagnosed and repaired close to 200 computers. All the previous in mostly the desktop format. Mobile phones and smartphones are in which I'm still in a big learning curve here.
What would cause the NAND ROM chipset to overheat like that? Could it be linked to using a custom ROM firmware? Could I have done something wrong?
Was it just hardware failure? I am extremely curious about this.
Anyone who has any constructive comments or suggestions are encouraged to share their opinions and/or views.
Many Thanks in Advance! :fingers-crossed:
Did you have a custom ROM installed on it? I would be surprised if LG covered you even if you had a custom ROM on it. I had the same problem as you once, and I returned it. No idea why my chip decided to fail though.
Likely simply just a case of random factory defect.
I would agree with shimbob, NAND overheating and failing before the processor doesn't follow the logical path of a custom ROM. For the NAND to overheat that would mean an insane amount of data calls and for that to happen the CPU/GPU has to be driving it. That should land up overheating the CPU/GPU first before the memory. What ROM were you running? Did you tinker with the any of the processor settings?
I don't think he'll answer, guys. He's not really asking for help or he would have provided the info you asked about in the first place. He's here to complain about how a genius such as himself could end up with a bad memory chip.
And to the OP (should he read this), that's what you had.
If it makes you feel any better, we felt just as bad as you when we read your post, which divides the world into three camps: the ignorant, the impolite, and those who help you over your little hurdles.
Very edifying.
usually happens after warranty expires or a new device comes out ?
i noticed it on my last 3 samsung galaxy phones.
havent had any other brand or series phones so i cant speak for them
so after about a year and a half my phone.s performance has been slowly decreasing despite my best efforts to keep it clean and organized and doing all the tricks to make it faster.
at the moment it is almost unusable . phone is now a little over 2 years old and is constantly freezing.
I have never dropped it and it was in the case since day one.
I keep same apps on it for 2 years and always to cache cleans and uninstall unused apps
also keep the internal memory under 50% yet none of that seems to help
it just keeps slowing down for some reason
anyone can explain what is goin on?
my laptop doesn't seem to lose any speed with age
fuzzysig said:
so after about a year and a half my phone.s performance has been slowly decreasing despite my best efforts to keep it clean and organized and doing all the tricks to make it faster.
at the moment it is almost unusable . phone is now a little over 2 years old and is constantly freezing.
I have never dropped it and it was in the case since day one.
I keep same apps on it for 2 years and always to cache cleans and uninstall unused apps
also keep the internal memory under 50% yet none of that seems to help
it just keeps slowing down for some reason
anyone can explain what is goin on?
my laptop doesn't seem to lose any speed with age
Click to expand...
Click to collapse
Phones use solid state storage, solid state storage decreases efficiency over time, they just break down the more that you install/uninstall/write/delete stuff to/from storage. With the way phones work, it is constantly reading/writing/dumping stuff to/from the cache partition(which is where everything that is loaded runs from and stores live data), this constant activity breaks down the efficiency of the cache partition, which cause lag during usage because it can't read to/from cache as efficiently as when it was new.
Also, as phones advance in hardware capability, certain apps(especially Google Play Services) are updated to the point that they require more from the hardware, older hardware can't run it/them as efficiently. Also, some older phones can't install some of the newer/more updated versions of apps, this leaves them using older versions which somewhere along the line are no longer supported, causing performance issues, especially a reduction in battery life and RAM speeds.
Laptops and PC are effected the same way, some older hardware can't install the newer versions of operating systems, or they can install the OS but certain parts of the software might have issues with certain pieces of older hardware and drivers, it just takes way longer with PC than it does with phones. Usually, the older systems are way past their prime before becomes an issue because users get new systems before they get that old, so they never see the performance issues that older hardware has with newer software.
Sent from my LGL84VL using Tapatalk
I have a Pixel XL that's hardbricked. Took it to a GSM shop they said the charging port works but something something CPU fried. No gsm shop in our city can fix this apparently but he heard that some folks could do it in New York City.
I don't want to recover the phone, just the data on it. Do you guys know shops that can do this ?
gtech99 said:
I have a Pixel XL that's hardbricked. Took it to a GSM shop they said the charging port works but something something CPU fried. No gsm shop in our city can fix this apparently but he heard that some folks could do it in New York City.
I don't want to recover the phone, just the data on it. Do you guys know shops that can do this ?
Click to expand...
Click to collapse
Not at any reasonable price point. What happened to the phone? Recovering the data from the flash devices would involve prohibitively expensive forensic data recovery, to the point of removing the flash devices from the board and interfacing with them using special tools. The people who have the means and the knowledge to do this are few and far between. Assuming there's no physical damage, someone with the Qualcomm Product Support Tool software and the appropriate binaries could potentially perform a low level reflash so the phone will boot...but again, the people who are actually able to do this are few and far between, assuming they even have the necessary files (which are not publicly available). The average repair shop will just replace the board, which means all the data is never recovered.
gtech99 said:
I have a Pixel XL that's hardbricked. Took it to a GSM shop they said the charging port works but something something CPU fried.
Click to expand...
Click to collapse
Speaking of a fried CPU, it means due to overheating CPU’s electrical components like transistors, diodes or capacitors are burned up. You will find overheating happened with some CPUs which didn’t have any fail-safe features or were overclocked by pushing high voltage. Sometimes using a faulty motherboard and faulty PSU can do this type of damage.becauseSo, you if you really ended up with a fried CPU, what is quite rare these days because, as said, modern CPUs have advanced thermal protection ( CPU will shut down automatically if it reaches a high temperature. If CPU temperature rises high due to high clock speed then it reduces the clock speed to a lower level ), you will have the worst luck to recover data from phone.
Note: it’s not possible to fix a fried CPU. Try to replace it with a new one.
V0latyle said:
Not at any reasonable price point. What happened to the phone? Recovering the data from the flash devices would involve prohibitively expensive forensic data recovery, to the point of removing the flash devices from the board and interfacing with them using special tools. The people who have the means and the knowledge to do this are few and far between. Assuming there's no physical damage, someone with the Qualcomm Product Support Tool software and the appropriate binaries could potentially perform a low level reflash so the phone will boot...but again, the people who are actually able to do this are few and far between, assuming they even have the necessary files (which are not publicly available). The average repair shop will just replace the board, which means all the data is never recovered.
Click to expand...
Click to collapse
I haven't done anything special with this phone. Never rooted it or installed other bootloaders, etc. It was a generic bland Pixel XL. It might have overheated a few times in the summer when I was using it in my car for Waze but otherwise nothing.
Before it shutdown for good it had some strange reboots and I think I recall there was some Pixel bug that was causing that. After doing that for a few weeks it stopped turning on completely.
Isn't a procedure like this available for the Pixel ?
https://flashfixers.com/recover-data-dead-phone-chip-off-data-recovery/
gtech99 said:
I haven't done anything special with this phone. Never rooted it or installed other bootloaders, etc. It was a generic bland Pixel XL. It might have overheated a few times in the summer when I was using it in my car for Waze but otherwise nothing.
Before it shutdown for good it had some strange reboots and I think I recall there was some Pixel bug that was causing that. After doing that for a few weeks it stopped turning on completely.
Isn't a procedure like this available for the Pixel ?
https://flashfixers.com/recover-data-dead-phone-chip-off-data-recovery/
Click to expand...
Click to collapse
That's what I was referring to by removing the flash device from the PCB. You would need fairly specialized tools, incluing a reader that's able to interface with the chip, and you'd have to have significant knowledge of how to interpret the raw data as the actual file structure. If you can find someone who thinks they can do this, good luck...but if it were me, I'd be charging about $150 an hour to do it.
And, this is all assuming that the data isn't encrypted. If it is (which Android does by default) then you're SOL.
V0latyle said:
That's what I was referring to by removing the flash device from the PCB. You would need fairly specialized tools, incluing a reader that's able to interface with the chip, and you'd have to have significant knowledge of how to interpret the raw data as the actual file structure. If you can find someone who thinks they can do this, good luck...but if it were me, I'd be charging about $150 an hour to do it.
And, this is all assuming that the data isn't encrypted. If it is (which Android does by default) then you're SOL.
Click to expand...
Click to collapse
Ah, ok. I'd pay 300$ to have this recovered is that reasonable ? Or it might be way more than that ? Guess I need to find a shop that does this sort of thing
gtech99 said:
Ah, ok. I'd pay 300$ to have this recovered is that reasonable ? Or it might be way more than that ? Guess I need to find a shop that does this sort of thing
Click to expand...
Click to collapse
Best of luck to you, honestly I think the money would be better spent elsewhere.