Never had a problem until the 2.3.4 update - Nexus S Q&A, Help & Troubleshooting

I got my Nexus S the first day it came out back in December. I never suffered from any of the other complaints that many others have posted. All was good until I got the 2.3.4 update. Ever since 2.3.4 landed on my phone, I've started to become a victim to the notorious random reboot bug for the first time ever. I must have had at least 6 reboots occur in the middle of phone conversations & one or two random ones while I was not in the middle of a call. It's starting to piss me off. Anyone else have this issue since the update??

Are you rooted or just running 2.3.4 stock?

MotorcycleKopp said:
I got my Nexus S the first day it came out back in December. I never suffered from any of the other complaints that many others have posted. All was good until I got the 2.3.4 update. Ever since 2.3.4 landed on my phone, I've started to become a victim to the notorious random reboot bug for the first time ever. I must have had at least 6 reboots occur in the middle of phone conversations & one or two random ones while I was not in the middle of a call. It's starting to piss me off. Anyone else have this issue since the update??
Click to expand...
Click to collapse
having Nexus S for 2 weeks or so no restarts, call drops etc... running 2.3.4 GRJ22/KD1

obsanity said:
Are you rooted or just running 2.3.4 stock?
Click to expand...
Click to collapse
I'm all stock. Never rooted yet.

Using a case?
Sent from my Transformer TF101 using XDA Premium App

zephiK said:
Using a case?
Sent from my Transformer TF101 using XDA Premium App
Click to expand...
Click to collapse
I used that Platinum case from Best Buy for the first couple months, but have since been going without one. Only thing I still got on my phone now is a Zagg screen protector.

Its odd that you're getting reboots :/ you can root and fix your problems by yourself
Sent from my Transformer TF101 using XDA Premium App

Really? Hmmm I never really looked into rooting too much before & I definitely didn't know that it could resolve issues like mine. I might just have to look into rooting now, if no other advice or fix gets brought up. I'd prefer not to root, but I guess that's just because I've never done it before.
Would rooting by itself resolve my issues? Or would I need to do some additional steps like programing or something as well? (I have no experience with programing either)

MotorcycleKopp said:
Really? Hmmm I never really looked into rooting too much before & I definitely didn't know that it could resolve issues like mine. I might just have to look into rooting now, if no other advice or fix gets brought up. I'd prefer not to root, but I guess that's just because I've never done it before.
Would rooting by itself resolve my issues? Or would I need to do some additional steps like programing or something as well? (I have no experience with programing either)
Click to expand...
Click to collapse
No. Rooting requires no programming knowledge at all. With a phone like the Nexus S, it's so easy to unlock. It's not a one-click as other phones but it doesn't require a exploit to root.
All rooting requires is a person to follow the instructions provided to them. The hardest part to the rooting process is installing the drivers for it. It's not that hard but people always get confused on installing the ADB drivers.
The biggest thing with rooting that would resolve your "rebooting" problem is flashing a more stable kernel. A lot of people (including myself) agree that Netarchy's 1.3.4 kernel is more stable than the stock kernel provided by Google. The only downside to rooting for you at this point is that you'll lose all of your data upon unlocking the bootloader. It is a security measure.

Good info. I appreciate it. Sounds like I need to start backing everything up & researching rooting and flashing kernels. Any good links or posts that you recommend on these topics?

MotorcycleKopp said:
Good info. I appreciate it. Sounds like I need to start backing everything up & researching rooting and flashing kernels. Any good links or posts that you recommend on these topics?
Click to expand...
Click to collapse
Check out the stickied posts in Nexus S General. If you ever need help, I'm more than willing to help you out but at least give it a try out on your own but if there are any preliminary questions. I'm more than willing to answer them.
Kernels: no need to read up on them. Netarchy's 1.3.4 kernel is what you want. Hands down. Netarchy destroys the competition in terms of kernels for daily usage.
Trinity is the type for people who wants to maximize the most out of their phone but it can be heavily unstable for some people and focuses more on hardcore OCing and things like that.
Stock modded kernel: no thanks.
Netarchy offers the most features that you'd want. OC is there but its optional, its left at the stock clocks of 1.0 GHz. If you want more than that, you'd have to set it on your own.
Overall summary of the rooting process,
- Install ADB drivers / set up Android SDK
- Get it to detect your device
- fastboot oem unlock
- fastboot flash recovery whatevertherecovery.img is
- Go into recovery
- Flash away! (if you want to use stock ROM + root then just flash the su.zip in the stickied thread)
At most it'll take you roughly maybe 10 minutes to do? Maybe even less than that, it's really simple.

Related

black bar on top ...

has anyone created just a black status bar? I really don't want to install any ROMS at the moment (I am rooted).
Thanks!
It looks nice, I'm waiting for the unrooted CM7 or whatever, I'm rooted but afraid to download any ROMs
Mikeglongo said:
It looks nice, I'm waiting for the unrooted CM7 or whatever, I'm rooted but afraid to download any ROMs
Click to expand...
Click to collapse
1. Cm7 is rooted.
2. Why would you be scared?
Sent from my LG-P999 using XDA App
I thought the new cm7 comes out for unrooted users instead of having to go ito ROM manager and what-not to get it?
And that's why I'm worried... I'm not really that tech-savvy with this stuff, so I'm hesitant on installing anything.. don't want to brick my phone
Someone will write a updated for the framework-res soon enough. I wonder how it will look with lcd bleeding.
Why flash an entire custom rom for just a black status bar?
Mikeglongo said:
I thought the new cm7 comes out for unrooted users instead of having to go ito ROM manager and what-not to get it?
And that's why I'm worried... I'm not really that tech-savvy with this stuff, so I'm hesitant on installing anything.. don't want to brick my phone
Click to expand...
Click to collapse
You have to be rooted to flash anything. Rom manager isnt ready yet, but clockwork recovery works just fine. And you cant brick a phone by flashing a rom.
Sent from my LG-P999 using XDA App
Mikeglongo said:
I thought the new cm7 comes out for unrooted users instead of having to go ito ROM manager and what-not to get it?
And that's why I'm worried... I'm not really that tech-savvy with this stuff, so I'm hesitant on installing anything.. don't want to brick my phone
Click to expand...
Click to collapse
Honestly more people should be like you. If you're not comfortable doing the things you see on this forum like rooting, using a custom recovery and flashing roms it's best that you refrain from doing so. A lot of people mess stuff up and don't have enough knowledge to fix it, then panic and cause more problems for themselves.
I was extremely timid with my g1, but now 2 phones later I'm much more comfortable messing with this stuff. The best advice I can give is for you to just read all kinds of stuff on these forums until you get a good idea about what different things do and how they can help and/or hurt what you want to do with your phone, then decide for yourself if you want to proceed.
And yes, like the last poster said, CM is only available to root users. You might be thinking of Gingerbread (Android 2.3) which will be available to non-root users "soon" according to tmobile.
Hope this helps ya out man.
Thanks a lot guys, yes I used ROM manager and it didn't work and it got me stuck at the LG sign when rebooting, and I panicked, so I exchanged my phone.
Got a new one, rooted it for whatever reason - maybe just to freeze bloatware.
I'll just wait for the Gingerbread. I just hope it solves the battery problem? 0_o I'm a stickler for battery, so I need to know soon because I'll just return my phone and get a different one (possibly a blackberry since the battery was always good on my old one), just always wanted to adventure into a smartphone
smjfosho said:
You have to be rooted to flash anything. Rom manager isnt ready yet, but clockwork recovery works just fine. And you cant brick a phone by flashing a rom.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
actually u can brick a phone JUST by flashing a ROM...unlikely given some reasonable intelligence...but it does happen...radios...radios..radios...also...kernels...
I'd say the best method is to just wait for the Official Gingerbread update from LG.
Flashing roms is fun and easy but not everyone has to be a crackflasher. CM7 will never be available for unrooted phones as you have to be rooted to flash it.
The G2x is very new and ClockWorkMod recovery isn't even ready for prime time yet. I would hold off at least until CWM Recovery has a decent automated boot process for our phones.
As far as bleeding screens, you WILL be able to see it with the all black bar. I have 2 G2x's here which 1 I haven't returned yet and has a screen bleed. It is noticeable. I did conclude that the "Sense-themed" bar in Eaglesblood isn't noticeable because of the contrasting colors. So take that with some consideration.
Mikeglongo said:
Thanks a lot guys, yes I used ROM manager and it didn't work and it got me stuck at the LG sign when rebooting, and I panicked, so I exchanged my phone.
Got a new one, rooted it for whatever reason - maybe just to freeze bloatware.
I'll just wait for the Gingerbread. I just hope it solves the battery problem? 0_o I'm a stickler for battery, so I need to know soon because I'll just return my phone and get a different one (possibly a blackberry since the battery was always good on my old one), just always wanted to adventure into a smartphone
Click to expand...
Click to collapse
Hahahahahahahhaha
avetny said:
Hahahahahahahhaha
Click to expand...
Click to collapse
My thoughts exactly,
Aren't blackberries notorious for turning themselves on and off? Maybe that explains the battery life
Haha, real funny, no my blackberry never turned on and off

Sensation user here considering going S-Off and rooting, advice?

Alright, so in the past I've owned an HTC HD2 that I was able to Android on by stumbling though the posts here, a Samsung Galaxy S Vibrant that I was able to root, albeit slowly and clumsily, and also my fiancee's old HTC Mytouch 3G. It has seemed though that after rooting and flashing a custom ROM on each phone, a few months later, problems begin to arise. The phone will start lagging, freezing, crashing, etc. It becomes unresponsive at times, won't receive or send calls/messages at times, etc. Now, I readily admit that this is most likely my fault due to my inexperience, so this raises my next question.
Should I attempt to go S-off and what not with my Sensation? Is it worth the risk? Could someone walk me though it, like leading the blind lol, as where to I won't make any mistakes?
A little background, I love my Sensation, and I really like the Sense 3.0 UI, though some of the widgets not updating, such as Friend Stream and News, is really rather aggravating.
So, with my history of rooted/custom ROM phones going bad, and my being mostly satisfied with my Sensation, should I bother going S-Off and rooting? Will I notice a great improvement in performance? Do any ROMs out there offer a version of Sense 3.0?
Thanks for you help, it is greatly appreciated,
Signed,
A lost noob
The whole process is easier than the hd2. It's a must for me there are plenty of roms and they all will improve the speed of your device
You can overclock your cpu to 1.5 like the processor was intended to be used. Go in to the development thread and there's a noob guide in stickies, read it a few times and go for it its easy and safe if you follow every step.
Roms are installed from sd via cwm like on the hd2
Get reading if your stuck ill help you the best I can.
Sent from my CM7 Sensation XE using xda premium
Alright, will do, thanks for that.
It'll have to wait a day, I called T-Mobile today to get a replacement phone, as I have dust under my screen, they're sending me a replacement next day air, should arrive tomorrow. That is pretty damn good service if I may say so. Though I have to keep the original back, a shame, as it has a couple nicks that bug me to no end.
Specialk47150 said:
Alright, will do, thanks for that.
It'll have to wait a day, I called T-Mobile today to get a replacement phone, as I have dust under my screen, they're sending me a replacement next day air, should arrive tomorrow. That is pretty damn good service if I may say so. Though I have to keep the original back, a shame, as it has a couple nicks that bug me to no end.
Click to expand...
Click to collapse
Be careful, as I almost rooted my phone two months ago when ROM's started flying around this forum. Thankfully I waited, since I am now on my third replacement Sensation because they have all developed dust under the screen. If you root it, dont expect to be able to return it. You better REALLY like that dusty look if you do!
webmaster said:
Be careful, as I almost rooted my phone two months ago when ROM's started flying around this forum. Thankfully I waited, since I am now on my third replacement Sensation because they have all developed dust under the screen. If you root it, dont expect to be able to return it. You better REALLY like that dusty look if you do!
Click to expand...
Click to collapse
So wait and be sure that I have a good phone and don't root until I do, ok, lol, thanks.
Assuming this is the guide in question?
http://forum.xda-developers.com/showthread.php?t=1192300
webmaster said:
Be careful, as I almost rooted my phone two months ago when ROM's started flying around this forum. Thankfully I waited, since I am now on my third replacement Sensation because they have all developed dust under the screen. If you root it, dont expect to be able to return it. You better REALLY like that dusty look if you do!
Click to expand...
Click to collapse
But you can go back to Stock ROM without root an S-ON. I had to return my device, so I flashed the stock ROM and went back to S-ON. It was no problem at all...
Specialk47150 said:
Assuming this is the guide in question?
http://forum.xda-developers.com/showthread.php?t=1192300
Click to expand...
Click to collapse
Apart from Revolutionary not working for three times and CWM not installing through Revolutionary everything went fine. If something doesn't work as expected just google it - there is someone out there with the same problem.
I tried a few ROMs and kernels out there and i can strongly recommend Bulletproof due to its stability. The best about it is that it's stock based (http://forum.xda-developers.com/showthread.php?t=1214023).
It will work even better with the Bricked Kernel (http://forum.xda-developers.com/showthread.php?t=1256668) and system tuner of the market. I am using the new 1.2.5 test-kernel (it's unbelievable fast).
There is only a issue with the camera causing an fc. But you can fix it using the sense 3.5 hack from faux: http://www.multiupload.com/7BIGBQTDLF
greetings
Manuel Büchel said:
Apart from Revolutionary not working for three times and CWM not installing through Revolutionary everything went fine. If something doesn't work as expected just google it - there is someone out there with the same problem.
I tried a few ROMs and kernels out there and i can strongly recommend Bulletproof due to its stability. The best about it is that it's stock based (http://forum.xda-developers.com/showthread.php?t=1214023).
It will work even better with the Bricked Kernel (http://forum.xda-developers.com/showthread.php?t=1256668) and system tuner of the market. I am using the new 1.2.5 test-kernel (it's unbelievable fast).
There is only a issue with the camera causing an fc. But you can fix it using the sense 3.5 hack from faux: http://www.multiupload.com/7BIGBQTDLF
greetings
Click to expand...
Click to collapse
Yeah, hopefully I don't run into any problems, I'll end up bricking my phone if I do...
As for the ROM, I've been strongly considering Android Revolution HD.
I have never rooted a phone before now. The process was so simple, if you follow the guide correctly. I'm on Android Revolution HD 3.6.2 and loving it. Very fast a stable, no issues or force closing.
Just remember to back up everything.

[Q] G2x slows down every few days, needing reboot

Hello, I've been running xboarder56's rooted GB OTA (not the tweaked one) for about 2 months now with almost no problems. However, my phone slows down and starts getting laggy to the point of being unusable after a day or two, and the frequency seems to be increasing. I don't run many background services. Only rebooting fixes the problem temporarily. I'll try to load a webpage on either opera mobile or the stock browser while listening to music and the music starts skipping and popping while the page loads slower than usual, but after rebooting it's fast again with no skipping.
I've been searching the forums and Google and seen a few others with this problem but can't find a fix for it. I've tried clearing the Dalvik cache (with NVflashed CWM) but it didn't seem to help any. Is this a common problem with LG-based Gingerbread ROMs, and does anyone else here still have this problem? I started having this problem after running my last ROM, CM7 RC1 after a month, and when I switched to my current ROM I did do a full wipe/factory reset. I'm thinking about trying the new-ish CM7.1.0.1 stable ROM or Weapon G2x and am wondering if those have this problem as well. Any suggestions? Thanks for your time!
I have honestly had that problem with every most roms I've tried at some point. Maybe not instantly, but it will eventually start to slow down like you described in which i have to reboot.
Dang. Do you think a fix actually exists for this, or does everyone have this problem? It's strange since I can't find much discussion about this.
It sounds like you have an app gobbling up memory and not releasing it. All Android phones such be rebooted around once a week to keep things nice and tidy.
jboxer said:
It sounds like you have an app gobbling up memory and not releasing it. All Android phones such be rebooted around once a week to keep things nice and tidy.
Click to expand...
Click to collapse
That's the issue I have with any 2.3.3 builds. But with 2.3.4 straight for 2 days now, hasn't experienced this issue yet. Unlike 2.3.3 that even within a day, it needs a reboot. I think there is a problem with LG's memory management.
-----------
sent from my calculator with android
jose makalolot said:
That's the issue I have with any 2.3.3 builds. But with 2.3.4 straight for 2 days now, hasn't experienced this issue yet. Unlike 2.3.3 that even within a day, it needs a reboot. I think there is a problem with LG's memory management.
-----------
sent from my calculator with android
Click to expand...
Click to collapse
If I flash CM7.1.0.1 stable, will ClockWorkMod 3.0.2.7 that I flashed for the CM7 RC suffice? Or do I need to update that too before flashing? Sorry to drag the thread along.
LuponX said:
If I flash CM7.1.0.1 stable, will ClockWorkMod 3.0.2.7 that I flashed for the CM7 RC suffice? Or do I need to update that too before flashing? Sorry to drag the thread along.
Click to expand...
Click to collapse
It should work fine flashing any zip, but the 5.0.2.0 version of CWM is far better. Flashing it with the One Click tool is a no brainer. Go ahead and update it. It will only take you a few minutes of your time.
jboxer said:
It sounds like you have an app gobbling up memory and not releasing it. All Android phones such be rebooted around once a week to keep things nice and tidy.
Click to expand...
Click to collapse
Do you have any evidence to support that? From what i've read android is made to run better when more memory is used.
http://www.androidcentral.com/ram-what-it-how-its-used-and-why-you-shouldnt-care
I never had to reboot my Nexus One, or even my T-mobile G1.
I've tried just about every rom for the g2x since i got it about a month ago and they are slow down. I'm not on the 2.3.4 rom and it started out great; now its almost unusable.
Anyone know whats wrong?? i'm about to call t-mobile and try to get another phone. I don't understand how they can release phones that just don't work. How can my single core 1ghz Nexus one be faster then this dual core 1ghz phone?
i'm just on stock and i have to reboot my phone every single day or else it's not useable. i have like zero apps on my phone almost so i know that can't be the problem, it's ridiculous
Sent from my LG-P999 using XDA App
tokimaromi said:
i'm just on stock and i have to reboot my phone every single day or else it's not useable. i have like zero apps on my phone almost so i know that can't be the problem, it's ridiculous
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Good to know it isn't only me. I'm trying some more tests on my phone to see whats going on. I think i'm gonna call tmo soon and see what they say.
i'm sure they won't have a good reply for you but definitely share with us if they do! i understand having to reboot the phone like once every three days or so but every single day is totally unacceptable
Sent from my LG-P999 using XDA App
Did anything ever come from this? I'm completely stock, just got this phone the other day. This phone lags harder then my HD2 I just had, which I would have kept if the digitizer didn't go out.
Are you guys on stock? If so then i highly recommend going custom. LG can't code for crap, so lots of stuff that was wrong with this phone has been fixed in the recent custom roms/kernels.
I've had the same issue until i recently switched to Phoenix Blood rom. I recommend it if you want to forget when was the last time you rebooted and still use the phone buttery smooth. I am using Faux kernel and the ROM is rock solid for me. Recently ran and the V6 script(instructions are on the rom's page in development section) with it and now it's even better! Give it a try you would love it;-)
Sent from my LG-P999 using XDA App
Okay I'll check it out later, ya I'm out the box right now but not for long.
Sent from my LG-P999 using xda premium
Yeah get on a ROM without any LG coding or framework. If you guys prefer a more stock 2.3.3 feeling I would suggest Bionix Reloaded.
I make it a habit to reboot my phone every night before I sleep.

My first flashing... (no trenchcoat involved)

So, I finally flashed a ROM onto my Atrix 2 for the first time the other day.
Synopsis
​Long story short the twitter app crashed my phone and threw it into a boot-loop, I did some research, quickly learned the in's-and-out's of flashing ROM's, flashed the stock-ROM for my device, fully updated my device, and became a better man for it...okay, well maybe not that last part!
The nitty-gritty
​What happened was I was trying to update my twitter when the app locked up after hitting the 'submit' button. I tried to force-close the program but to no avail. Then I had the bright idea of shutting down my phone. This is where the fun began.
After re-booting my phone, I discovered that it was stuck in a boot-loop. Now, my phone has been rooted for a little over a month. There were no issues that occurred after I rooted my phone up until that point. This is what leaves me to believe that Twitter corrupted some app data.
After this happened I took to the internet and scoured over forums (this one chief among them), articles, videos, and even asked a few fellow-android users here in the real world. Everywhere I looked lead me to this term I had feared up until this point: Flashing.
I understood that flashing a ROM was just like installing a new operating system. I had toyed around with Linux before just a bit and am savvy-ish when it comes to computers. However, I was so terrified of bricking my phone in trying to flash a new ROM onto it (I would have been track-phoning for around a year until my next manufacturer subsidy came out on my account.)
After discovering terms like deodexed, CM7, stock, AP Fastboot, RSD Lite, and hardware-key reset, I felt like I was finally able to attempt the flashing. The first few attempts failed as I didn't realize I didn't have enough battery life to sustain the flashing process.
After charging it up, I flashed the stock ROM onto my phone. The moment it went from the red M puddle screen to the dripping AT&T sphere, then onward to the ROM was a moment of pure joy (not to sound corny.) I felt like I had beat-the-system. A problem that would have forced others to return their phone to the store was a problem that I fixed myself.
Final Thought
​I know this is rather cinematic for it being a simple flash job on an android device. But, for me, this was quite exhilarating. I'm not comfortable flashing anything lower than full-release ROM's (beta and alpha ROM's are a bit beyond my scope right now.) But, I do look forward to testing out various full-release ROM's as they become available.
AscottW said:
So, I finally flashed a ROM onto my Atrix 2 for the first time the other day.
Synopsis
​Long story short the twitter app crashed my phone and threw it into a boot-loop, I did some research, quickly learned the in's-and-out's of flashing ROM's, flashed the stock-ROM for my device, fully updated my device, and became a better man for it...okay, well maybe not that last part!
The nitty-gritty
​What happened was I was trying to update my twitter when the app locked up after hitting the 'submit' button. I tried to force-close the program but to no avail. Then I had the bright idea of shutting down my phone. This is where the fun began.
After re-booting my phone, I discovered that it was stuck in a boot-loop. Now, my phone has been rooted for a little over a month. There were no issues that occurred after I rooted my phone up until that point. This is what leaves me to believe that Twitter corrupted some app data.
After this happened I took to the internet and scoured over forums (this one chief among them), articles, videos, and even asked a few fellow-android users here in the real world. Everywhere I looked lead me to this term I had feared up until this point: Flashing.
I understood that flashing a ROM was just like installing a new operating system. I had toyed around with Linux before just a bit and am savvy-ish when it comes to computers. However, I was so terrified of bricking my phone in trying to flash a new ROM onto it (I would have been track-phoning for around a year until my next manufacturer subsidy came out on my account.)
After discovering terms like deodexed, CM7, stock, AP Fastboot, RSD Lite, and hardware-key reset, I felt like I was finally able to attempt the flashing. The first few attempts failed as I didn't realize I didn't have enough battery life to sustain the flashing process.
After charging it up, I flashed the stock ROM onto my phone. The moment it went from the red M puddle screen to the dripping AT&T sphere, then onward to the ROM was a moment of pure joy (not to sound corny.) I felt like I had beat-the-system. A problem that would have forced others to return their phone to the store was a problem that I fixed myself.
Final Thought
​I know this is rather cinematic for it being a simple flash job on an android device. But, for me, this was quite exhilarating. I'm not comfortable flashing anything lower than full-release ROM's (beta and alpha ROM's are a bit beyond my scope right now.) But, I do look forward to testing out various full-release ROM's as they become available.
Click to expand...
Click to collapse
In all technicality all you're doing when flashing a rom (at least now) is installing some tweaked files such as build.prop or some tweaked system files for themes. By no means is it a new OS. But once a main kernel Dec finished up with a CM7 kernel we should be able to flash a custom kernel which is the meat of what really runs your phone. Really the stuff we can do right now only really have to do withtl the UI.
But anyways welcome to the world of android development!
Sent from my MB865 using XDA
Congrats on flashing your first ROM . Sorry to hear it didn't completely work out for your. Quick question: did you wipe the Dalvik Cache as part of the flashing process?
By the way, most of the ROMs labeled "beta" are pretty stable. If a ROM has had more than a few updates and it's still in beta, it's mostly because the developer is either planning on adding more features for the full release or is a perfectionist
Well, as you can tell it's a sharp learning curve. But welcome to the world of Android hacking/modding/whateveryoucallit, and happy flashing
wait, are you telling me that there are actually people who do research before complaining about some little thing they don't know how to do?!?!?!?!?!?!?
FINALLY
Sent from my MB865 using XDA
LOL.. good story/nice read.. Welcome!
I would say it worked out pretty well. I will probably flash a custom ROM later on this week. I will also keep reading up on the whole process and the it's and out's.
I cleared both user data and the dalvik cache as well. Pretty much at that point I was desperate. Lolz
Sent from my MB865 using xda premium
lkrasner said:
wait, are you telling me that there are actually people who do research before complaining about some little thing they don't know how to do?!?!?!?!?!?!?
FINALLY
Sent from my MB865 using XDA
Click to expand...
Click to collapse
Hahaha.. Well, with this involving my phone (for which I don't have the hundreds of dollars to buy one outside the manufacturers subsidy) I wanted to make sure I was doing things right.
Sent from my MB865 using xda premium
AscottW said:
I would say it worked out pretty well. I will probably flash a custom ROM later on this week. I will also keep reading up on the whole process and the it's and out's.
I cleared both user data and the dalvik cache as well. Pretty much at that point I was desperate. Lolz
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
its really easy, so you should go ahead, the roms we have are way better than stock. Lithium is y favorite right now.
alteredlikeness said:
LOL.. good story/nice read.. Welcome!
Click to expand...
Click to collapse
Glad you enjoyed it! I am happy that my twitter app decided to crash, now.
Sent from my MB865 using xda premium
AscottW said:
Hahaha.. Well, with this involving my phone (for which I don't have the hundreds of dollars to buy one outside the manufacturers subsidy) I wanted to make sure I was doing things right.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
I second that.. better to take your time to research, and do things right the first time...
lkrasner said:
its really easy, so you should go ahead, the roms we have are way better than stock. Lithium is y favorite right now.
Click to expand...
Click to collapse
^Total opinion about stock and custom... I'm on stock/odex/modded/tweaked with some bells and whistles... nice, responsive, and stable..
Sent from my mind using XDA
alteredlikeness said:
^Total opinion about stock and custom... I'm on stock/odex/modded/tweaked with some bells and whistles... nice, responsive, and stable..
Sent from my mind using XDA
Click to expand...
Click to collapse
I agree. Spent this weekend working on the Stock 2.3.6 rooted/odexed. Added the Superv6, and other mods, hotspot wifi fix, removed bloat. Definitely more fun this way. Then again I had a buttload of practice on my original ATRIX.
And thank god for the bootstrap and FXZ !!!!
dicksteele said:
And thank god for the bootstrap and FXZ !!!!
Click to expand...
Click to collapse
Yes without that I would of had an expensive paperweight to many times
dicksteele said:
I agree. Spent this weekend working on the Stock 2.3.6 rooted/odexed. Added the Superv6, and other mods, hotspot wifi fix, removed bloat. Definitely more fun this way. Then again I had a buttload of practice on my original ATRIX.
And thank god for the bootstrap and FXZ !!!!
Click to expand...
Click to collapse
How exactly do I identify bloatware? I have two programs to do that Titanium backup and Rom Manager as well as a few 3p uninstallers. However, I never know exactly what to delete?
AscottW said:
How exactly do I identify bloatware? I have two programs to do that Titanium backup and Rom Manager as well as a few 3p uninstallers. However, I never know exactly what to delete?
Click to expand...
Click to collapse
DON'T ever delete any programs. It is better to use something like bloat freezer, and freeze these apps, than to delete them.
The updates check for missing "bloatware" and will fail to install the updates due to ANY missing apps, that came with the stock image.
If you want a debloated image, then use one of the more custom ROMS like lithium, or Supercharged, etc.
If you use a debloated ROM, then you can always flash the fxz back before any updates come out, we tend to start screaming pretty load on here when updates start to arrive as you may have already seen this week with the ICS leaks.
P.S. It is VERY hard to hardbrick this phone, it took me killing the signature on the kernel to get my first hardbrick, and I have had 3 more hardbricks. I have the warranty through att, so I never worry about things like that, since I am a dev and take my phones life into my own hands, and ATT always has exchanged my phone on the spot for over 12 years now.... You can softbrick (bootloop), but that is an easy fix with the FXZ (lifesaver). So not too much to worry about hurting your phone with flashing...
jimbridgman said:
DON'T ever delete any programs. It is better to use something like bloat freezer, and freeze these apps, than to delete them.
The updates check for missing "bloatware" and will fail to install the updates due to ANY missing apps, that came with the stock image.
If you want a debloated image, then use one of the more custom ROMS like lithium, or Supercharged, etc.
If you use a debloated ROM, then you can always flash the fxz back before any updates come out, we tend to start screaming pretty load on here when updates start to arrive as you may have already seen this week with the ICS leaks.
P.S. It is VERY hard to hardbrick this phone, it took me killing the signature on the kernel to get my first hardbrick, and I have 3 more hardbricks. I have the warranty through att, so I never worry about things like that, since I am a dev and take my phones life into my own hands.... You can softbrick (bootloop), but that is an easy fix with the FXZ (lifesaver). So not too much to worry about hurting your phone with flashing...
Click to expand...
Click to collapse
LOL, I was laughing so hard when XDA crashed last night. I was sure we caused it with our ICS Freak out!!!!
lkrasner said:
LOL, I was laughing so hard when XDA crashed last night. I was sure we caused it with our ICS Freak out!!!!
Click to expand...
Click to collapse
I though the same thing, and I was kind of glad it did crash though, so that I could find that article with the interview of cyanogen that was posted on the XDA-dev home page.
AscottW, I am like you -I read and researched and forum'd my evening/early morning hours away with regards to the whole rooting and flashing and so on. I have never done such things with a phone before, but being fairly computer savvy myself felt like after several hard weeks learning as much as I could, flashed MY first ROM. (Did a little happy dance myself when I saw the custom boot animation for the first time, think I even let out a little school boy squeal as well! -Glad no one was around to hear that)
Still reading and researching and forum'ing at every free moment I have (girlfriend and kids think my laptop has become permanently attached to my, well... lap!) and am really interested in possibly getting myself to a point where I can be of some usefulness in the dev world.
Admittedly, after flashing for the first time, I got foolish with CWM and did basically what seemed like deleting the system partition and told the Android OS to get lost. Big mistake. Got stuck in a crazy splash screen loop and wouldn't load Android OS for the life of me. That said, with the help of the good people here on this forum, I was able to be walked through a AP Fastboot FXZ file fix, updated back to 2.3.6, and started over -making damn sure I knew what I was doing before doing ANYTHING! lol
Feel like: "I just had sex"
http://www.youtube.com/watch?v=lQlIhraqL7o
PhoenixNghi said:
Feel like: "I just had sex"
http://www.youtube.com/watch?v=lQlIhraqL7o
Click to expand...
Click to collapse
lol @ this!

Is unlocking worth it?

I've had my infinity for a couple of weeks now and I'm really frustrated with the lag. I want to unlock it but I've heard stories of people who owned one and a manufacturer defect didn't appear for a month. For example a couple of black lines appearing that won't go away. So far I haven't found any defects but I'm worried that if I unlock then something will happen and I can't return it.
Sent from my LG-P999 using Tapatalk 2
Yep do it. Get some love!:good:
I really want to. But would it be wise to wait a few more weeks to make sure there's no defects?
Sent from my LG-P999 using Tapatalk 2
Is unlocking worth it?
The answer will always be yes.
Is the tablet worth much before unlocking?
No
Thats OK said:
Is unlocking worth it?
The answer will always be yes.
Is the tablet worth much before unlocking?
No
Click to expand...
Click to collapse
I agree but if something happens like the screen randomly giving out then I'm screwed
Sent from my LG-P999 using Tapatalk 2
laod said:
I agree but if something happens like the screen randomly giving out then I'm screwed
Click to expand...
Click to collapse
In the meantime while you're deciding whether to unlock or not, go into "Settings / Developer Options" and put a check in "Force GPU rendering". Then under "Window animation scale", Transition animation scale" and "Animator duration scale", disable all of those.
I go tired of the slideshow animations, so I disabled them all. My tablet has the appearance of snappiness now. Rooting, unlocking, and romming my tablet didn't get rid of the horrible slideshow. Disabling animations does.
Thanks for the tip. How likely are issues to show up? And if they do will asus cover it? If it's not very likely then ill unlock and install cromi
Sent from my LG-P999 using Tapatalk 2
laod said:
Thanks for the tip.
How likely are issues to show up?
And if they do will asus cover it?
If it's not very likely then ill unlock and install CROMi
Click to expand...
Click to collapse
A bit of a tough call...boils down to luck of the draw so to speak.
Asus may give you grief even with a locked tab.
My own experience:
Had the Infinity since July 2012.
Minor light bleed at first: diminished to a point where it isn't noticeable.
Some clicking around the glass at first: one spot now above the power port-no issue for me since this tablet is in a Bobj case.
Unlocked and re-rommed with original CleanROM around October\November or whenever JB first was pushed.
Few months to go and my tab will be a year old so if I make it with no hardware failures unlocking was the best option for me.
*note
I dropped this tab off a nightstand 4 weeks ago and dinged the corner (it was in a light folio) it never skipped a beat.
Bottom line
It's your call
Ok thanks. Disabling the animations and enabling force gpu rendering solved my problems with lag. So for now I have no need to unlock. My plan now is to wait a month or maybe 2 and then unlock if no issues come up. Thanks for the advice
Sent from my LG-P999 using Tapatalk 2
Thats OK said:
Is unlocking worth it?
The answer will always be yes.
Is the tablet worth much before unlocking?
No
Click to expand...
Click to collapse
I'm aware to not make a lot of friends in saying this ... but I found the stock JB ROM a decent system. For me it has not really been as bad as you can read here a lot. Have to say though that I never had to use the ICS stock version, which seemingly really was not a good choice.
I have unlocked mine and flashed a custom ROM, but in my case more for the fun of it. Using the stock ROM until your warranty runs out is a good option. You might look into rooting it anyway, which will not harm your warranty.
FordPrefect said:
I'm aware to not make a lot of friends in saying this ... but I found the stock JB ROM a decent system. For me it has not really been as bad as you can read here a lot. Have to say though that I never had to use the ICS stock version, which seemingly really was not a good choice.
I have unlocked mine and flashed a custom ROM, but in my case more for the fun of it. Using the stock ROM until your warranty runs out is a good option. You might look into rooting it anyway, which will not harm your warranty.
Click to expand...
Click to collapse
Why would you not have friends by saying stock is good?
Non-stock ROMs have seen tremendous success their ongoing development is just icing on the cake.
I'm sure there are thousands of happy users that have no idea that aftermarket ROMs even exist.
Thats OK said:
Why would you not have friends by saying stock is good?
Non-stock ROMs have seen tremendous success their ongoing development is just icing on the cake.
I'm sure there are thousands of happy users that have no idea that aftermarket ROMs even exist.
Click to expand...
Click to collapse
Just thought because everyone is beating on the fact that only custom ROMs make this thing fly. Again, I'm a very new Infinity user, my only experience with stock ROMs is from using the JB 10.4.4.25 version. And this is a good choice in my opinion.
FordPrefect said:
Just thought because everyone is beating on the fact that only custom ROMs make this thing fly. Again, I'm a very new Infinity user, my only experience with stock ROMs is from using the JB 10.4.4.25 version. And this is a good choice in my opinion.
Click to expand...
Click to collapse
The stock ROM is mixed bag -- some have actually preferred ICS to JB, and there are some that prefer it the other way around. Nonetheless, I'd be surprised if you wouldn't prefer custom ROMs to the stock versions once you unlock and flash away.
I do underwrite fully your statement that if the stock ROM doesn't bother you, it's not that of an immediate need to unlock and flash a custom ROM, especially if you are an easily frightened Infinity owner.
I know this forum seems aimed at custom ROMs.
Certainly no need if one is pleased with the tablet in it's pure form.
XDA is a site that used to forge development vs. troubleshooting.
It's all good tho...everyone enjoys helping as much as possible.
No worries
I'd say just root then install browser2ram and set that up in the stock browsers debug settings, then wait for the next update which should be in a month or so.
After the update see if you are still wanting and then decided if you want to unlock. Remember this is a techie site and people here tend to advise people to take more aggressive actions, as they are speaking from an area that they are very comfortable, but I tend to advise people like yourself to be more conservative and patient.
mc_365 said:
I'd say just root then install browser2ram and set that up in the stock browsers debug settings, then wait for the next update which should be in a month or so.
After the update see if you are still wanting and then decided if you want to unlock. Remember this is a techie site and people here tend to advise people to take more aggressive actions, as they are speaking from an area that they are very comfortable, but I tend to advise people like yourself to be more conservative and patient.
Click to expand...
Click to collapse
thanks. actually i am one of the more aggressive action types of people. i rooted my phone and installed a custom rom within an hour of getting it lol. I really want to unlock my tab because i love custom roms, however it is an expensive device and i have heard stories of the poor quality control asus has. If it weren't for that i would have unlocked it and installed cromi a few days after getting it.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD

Categories

Resources