Related
Well, I ditched my iphone to try out the nexus one... I just got the phone today and I barely know how to use it stock (2.1). Phone is untouched, brand new from google...
I guess I would like to take advantage of the phones power and more importantly, try out version 2.2.... any advice where to begin, tutorials etc? thx in advance, I will go back to reading this site!
First, get to know your phone. Use it as long as you can before rooting, until you get used to it and EVERYTHING it does. When it starts to get boring, ROOT it! By that time you should know every secret the phone offers!
not a big fan of patience... I would like to learn to root it and play around... but nothing brick like...
2.2 would be nice and anything else people recommend, lol....
thx man, goodnight.
Mr.Kakarot said:
Well, I ditched my iphone to try out the nexus one... I just got the phone today and I barely know how to use it stock (2.1). Phone is untouched, brand new from google...
I guess I would like to take advantage of the phones power and more importantly, try out version 2.2.... any advice where to begin, tutorials etc? thx in advance, I will go back to reading this site!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=688000
Inside there's a link, follow the Pre-requisites on that link first... and setup ADB first.
ok so set up that ab thing first then follow the tutorials... also, should I have mentioned it is a *rogers 3g phone (att&t)
thx again and goodnight 4 real
If you barely know how to use it stock.... you should probably figure that out before you go around rooting it, flashing custom ROMs, and trying the latest BETA OS release. Once you've got the stock OS figured out and are getting bored with it, THEN root and move on.
Learn how the phone works. This is no iPhone and the settings with this phone are plentyfull. Have in mind that after you flash a Cyanogen ROM for instance, you will have 4 times more settings to play with, hence the advice to learn the basic functions on your N1. But anyways, you will come to a certain point where the GEEK in you wakes up and you wanting MORE..
DO also know that when you want to root your phone, you need to unlock you phone. Doing this will VOID YOUR WARRANTY. I will also advise you to use your phone for a period of time to see that there are no issues with hardware and build of the phone (buttons, dust under screen, trackball not working, not chargin, loose connectors etc etc..), just to be safe. Coz once you unlock it, there is NO going back to lock it again (at this point)
Setting up ADB and Recovery can be the most struggling with drivers and interface but once that is passed and you start using recovery on a daily or weekly basis, is all smooth ride from there. I guarantee you many hours customizing and experimenting with this phone than any other non-andoid phones you have had in the past.. is pretty much an addiction. i have rebooted this phone more the last 3 months than any other phones in my whole lifetime .
Rule of thumb is always have a recent Nandroid (backup done in recovery) before flashing. Flashing ROM's are usually safe as safe can be. Kernels are not risky to flash either, but remember that Kernels are the ones that controls voltages and speed of you Processor and other things, and flashing wrong Kernels can result in non functioning behavious in your OS and worst case, the processor overheating, so know what you are doing when flashing Kernels. At one point you will start trying out kernels because if you are on a hunt for more battery life, the ROM + Kernel combination are the main things that makes this happens.
Then , a last note: I addvise you to NOT update radios if you don't have any problems with the one you have. The Radio's are the one that controls your ability to call controls your phone's antenna and Wi-Fi. If you DO flash radios and happen to terminate the process, i guarantee you a bricked phone. So beware. If you upgrade to FROYO, one of the processes is flashing a new radio. So let things runs it course once in process.
Have fun trying to optimize your phone to last as long as it can on one battery charge...
If you like to begin in Android World you can start from the following blog
nextworldmobile.com. It has reviews of Android Applications that you must put on your mobile plus Flashing Tutorials etc.
Theunlockr.com is a great website for rooting and anything on the nexus. They also have videos
-------------------------------------
Sent from my Nexus One
pretty valid points from all of you, thanks very much.... I think I will give it a week or atleast the weekend... once I got in on luck.... maybe I will move on
I do buy and sell phones a lot... might be best to wait and see if there is a way to reverse the process and keep warranty intact first?
thx a bunch.
since the OTA Froyo should be coming in by maybe end of next week, i'd wait and just mess with 2.1 for now
jblazea50 said:
since the OTA Froyo should be coming in by maybe end of next week, i'd wait and just mess with 2.1 for now
Click to expand...
Click to collapse
It should definitely be soon, and will give you a chance to have new software and features without voiding your warranty. Win-win :-D
jblazea50 said:
since the OTA Froyo should be coming in by maybe end of next week, i'd wait and just mess with 2.1 for now
Click to expand...
Click to collapse
I really recommand to do that exact thing:
learn nandroid (backups )
then play with your 2.1
2.2 will be out before you could have learned everything you wanted from 2.1
thx again, I am pretty excited about 2.2... coming from a 3gs... I kind of thought I would not like my n1.. but I see no problems with 2.1.... I cannot imagine the performance increase it claims.... gonna be sweeeeet.
So, anything non warranty killing you guys recommend? apps/tweaks etc? thx
Mr.Kakarot said:
thx again, I am pretty excited about 2.2... coming from a 3gs... I kind of thought I would not like my n1.. but I see no problems with 2.1.... I cannot imagine the performance increase it claims.... gonna be sweeeeet.
So, anything non warranty killing you guys recommend? apps/tweaks etc? thx
Click to expand...
Click to collapse
You can download Launcher Pro from the Market to replace the current home Launcher. It will allow you to have up to 7 home screens and makes everything a whole lot smoother when you swipe between the screens.
sweeeeet tip bro, thx!
i believe that there exists a non-warranty-voiding method of updating to froyo. it's much faster than 2.1, and battery life is also improved.
for apps, there are threads about it but, some that are just pretty darn neat would include:
google skymap
barcode scanner
google goggles
some augmented reality apps would be:
layar
wikitude
for a better typing (rather swiping) experience, get swype. you should be able to find instructions on how to put it on around here, and there is a non-timed release in the apps/themes section
i use 'and explorer' as a file explorer
pandora is a must if you like internet media
google listen isn't bad (although i hear good things about other apps) for pulling down any podcasts you like
and, go give the navigation app a try. it's the bees knees. not only does it give turn by turn directions, but as long as you load the trip while in a 3g or wifi connection, it caches the whole thing, so you can drive through dead zones and won't lose the the path, as long as you have gps signal. plus, it switches to street view to show you the destination, when you get there
timothydonohue said:
i believe that there exists a non-warranty-voiding method of updating to froyo. it's much faster than 2.1, and battery life is also improved.
...
Click to expand...
Click to collapse
yeah, i updated mine via the non-warranty-voiding method, but since i like some of the apps that require root, i had it rooted
to update to frf50 (Froyo) without voiding warranty, you need to download the OTA file and rename to update.zip and place in the root of the SD card
1. power off phone
2. hold down volume down button and press power
3. scroll to recovery and hit power (should take you to screen with an exclamation mark or something similar
4. while holding down power button, press volume up
5. this should take you to stock recovery and you can now apply update.zip from sd card
those may be the correct steps, i don't think i'm missing anything; there's some guide located in the general forum
thx for the app suggestions, I will try them all
as for the above instructions... each site I try to grab 2.2 from.. says it no longer exists? thx
timothydonohue said:
i believe that there exists a non-warranty-voiding method of updating to froyo. it's much faster than 2.1, and battery life is also improved.
for apps, there are threads about it but, some that are just pretty darn neat would include:
google skymap
barcode scanner
google goggles
some augmented reality apps would be:
layar
wikitude
for a better typing (rather swiping) experience, get swype. you should be able to find instructions on how to put it on around here, and there is a non-timed release in the apps/themes section
i use 'and explorer' as a file explorer
pandora is a must if you like internet media
google listen isn't bad (although i hear good things about other apps) for pulling down any podcasts you like
and, go give the navigation app a try. it's the bees knees. not only does it give turn by turn directions, but as long as you load the trip while in a 3g or wifi connection, it caches the whole thing, so you can drive through dead zones and won't lose the the path, as long as you have gps signal. plus, it switches to street view to show you the destination, when you get there
Click to expand...
Click to collapse
ps: will pandora work in Canada? thx
I would like to know how many of you had successfully updated their SGS (Samsung Galaxy S) to Froyo. I think this will help us understand the failure rates so people who do not want to risk bricking their phone.
1) Updated with no problems
2) Updated with problems
3) Tried to update and having problems
4) Did not update at all
If you are talking about roms.. Well most are a 1. I habent heard of an official froyo update. And.if.you by chance do.brick it, there are ways to unbrick it pretty easily.
Sent from my SAMSUNG-SGH-I897 using XDA App
I have the Bell Vibrant which is the I9000M.
I thought that Bell released an official update for their new Froyo. Check it out here
mobilesyrup.com/2010/12/08/bell-samsung-galaxy-s-vibrant-upgrade-to-os-2-2-froyo-coming-december-10th/
Did update my Bell Samsung Galaxy S GT-I9000M with Bell release Froyo available using Kies and all seemed to be running smoothly until I had issues connecting my bluetooth and trying the voicedialing features that did not work in my case and after got Force close on every apps. Did a shutdown and got the device in a loop at boot up.
Will try tonight to reload the device with 2.1 and see from there to retry 2.2.
Finger cross !
I upgraded with no problems but I did do a factory reset as things started to get a bit slow and from what Ive read it is a good idea to do a reset to get rid of any residual 2.1 stuff on the device. Since then the update has been working well for me...
KNOCK ON WOOD!!!
I have 2 SGS phones so you'll just have to add another vote to the "successful upgrade" option in addition to the one I was able to cast
I've flashed the following 2.2's without any problems so far:
- unofficial JK3 (Canada) via ODIN
- official JK4 (Canada) via Kies
- straight JPU via ODIN
- JPU Doc RomMOD v2 via update.zip recovery
No problems with flashing.
And yes, clearing data & cache is helpful (mandatory?). Backups are good!
there is NO problem upgrading.
the Internal SD failure comes AFTER you have SUCCESSFULLY upgraded the phone, a few hours to a few days later
ssj2miguelx said:
I would like to know how many of you had successfully updated their SGS (Samsung Galaxy S) to Froyo. I think this will help us understand the failure rates so people who do not want to risk bricking their phone.
1) Updated with no problems
2) Updated with problems
3) Tried to update and having problems
4) Did not update at all
Click to expand...
Click to collapse
AllGamer said:
there is NO problem upgrading.
the Internal SD failure comes AFTER you have SUCCESSFULLY upgraded the phone, a few hours to a few days later
Click to expand...
Click to collapse
Cool. That makes this type of poll misleading then because someone reporting success today may have issues tomorrow (we can't change our vote correct?).
That's right. I saw your post about your phone going bust. Sorry to hear that.
I just can't get Kies to work -- it just says "connecting to device" and it hangs
Also can't install MPT USB drivers -- always fails. I installed the correct x64 bit Windows 7 drivers and everything.
Ughh
Wow. I didn't think people would have problems after the update. Man, I really should wait until we all know that its okay to update. I am new when it comes to the SGS so if I fail at it, I don't want to start crying. This is such a nice phone....so if it works, why break it?
ssj2miguelx said:
Wow. I didn't think people would have problems after the update. Man, I really should wait until we all know that its okay to update. I am new when it comes to the SGS so if I fail at it, I don't want to start crying. This is such a nice phone....so if it works, why break it?
Click to expand...
Click to collapse
Same - I am hessitant now to upgrade.
I had one of the original phones, it sucked, no GPS, etc. and it died on me.
I got a new phone, for free, my buddy works at bell, GPS works fine, and this one I think had the internal card failure b/c one day it just went black - reboot and the bottom lights light up but it doesn't boot in.
I did a recovery mode -> hard reset seemed to fix it -- tho i lost all my apps and contacts etc.
Now I haven't rooted or lag fixed, but I REALLY want froyo.
But what's the point ? I already had to do a reset b/c of internal card failures in the past, that means im almost guaranteed to lose this one if i upgrade,...
Funkadelick said:
Same - I am hessitant now to upgrade.
I had one of the original phones, it sucked, no GPS, etc. and it died on me.
I got a new phone, for free, my buddy works at bell, GPS works fine, and this one I think had the internal card failure b/c one day it just went black - reboot and the bottom lights light up but it doesn't boot in.
I did a recovery mode -> hard reset seemed to fix it -- tho i lost all my apps and contacts etc.
Now I haven't rooted or lag fixed, but I REALLY want froyo.
But what's the point ? I already had to do a reset b/c of internal card failures in the past, that means im almost guaranteed to lose this one if i upgrade,...
Click to expand...
Click to collapse
If your card is gonna die its gonna die no matter if you upgrade or not....Flashing just seems to speed up the corruption.
Thats a good question. People seem to be having big issues with this new Froyo update here, http://forum.xda-developers.com/showthread.php?t=867157. I really hope Bell gets a fix for this new "firmware Froyo 2.2" that they just released.
If the Nexus S is the so similar to the SGS I9000M why dont we have Gingerbread (2.3) yet?
Again people. It's not the froyo update that's a problem it's bad internal SDcards. These phones were dying before froyo came out and without ever flashing anything.
If they're gunna die, they're gunna die. Flashing just helps to speed up the failures. SO flash away and hope it blows before your warranty is up.
Funkadelick said:
Same - I am hessitant now to upgrade.
I had one of the original phones, it sucked, no GPS, etc. and it died on me.
I got a new phone, for free, my buddy works at bell, GPS works fine, and this one I think had the internal card failure b/c one day it just went black - reboot and the bottom lights light up but it doesn't boot in.
I did a recovery mode -> hard reset seemed to fix it -- tho i lost all my apps and contacts etc.
Now I haven't rooted or lag fixed, but I REALLY want froyo.
But what's the point ? I already had to do a reset b/c of internal card failures in the past, that means im almost guaranteed to lose this one if i upgrade,...
Click to expand...
Click to collapse
If I was you I'd flash the crap outta your phone. If your black screen was due to a weak internal SD then it's gunna go. So flash it and hope it goes so you can get a new(repaired) one. Of course the wait time is a bit long right now for repairs. And there's no guarantee that the newly repaired one won't blow.
Damn this phone....
And yes, clearing data & cache is helpful (mandatory?). Backups are good!
Click to expand...
Click to collapse
How to do it?
It will delete also my files (photos, music....) on the internal memory?
Regards
Sent from my GT-I9000 using Tapatalk
AllGamer said:
there is NO problem upgrading.
the Internal SD failure comes AFTER you have SUCCESSFULLY upgraded the phone, a few hours to a few days later
Click to expand...
Click to collapse
yeah!
my phone upgrade went well..but i have occasional force closure on apps. Then one day it just hang using Msn Talk Pro and I had to pull the battery out to reboot and it never came back on - stuck after the bootup S logo. grrrr..
how long does the warranty repair usually takes?
Anyone in Vancouver Canada that are non Bell subscriber have any problem bringing it in? Which store do you guys go to? I will try the same store for hassle free repair job. Thanks
Videonut said:
Again people. It's not the froyo update that's a problem it's bad internal SDcards. These phones were dying before froyo came out and without ever flashing anything.
If they're gunna die, they're gunna die. Flashing just helps to speed up the failures. SO flash away and hope it blows before your warranty is up.
Click to expand...
Click to collapse
Is there a chance that my phone has a bad internal SDcard?
betaboy00 said:
yeah!
my phone upgrade went well..but i have occasional force closure on apps. Then one day it just hang using Msn Talk Pro and I had to pull the battery out to reboot and it never came back on - stuck after the bootup S logo. grrrr..
how long does the warranty repair usually takes?
Anyone in Vancouver Canada that are non Bell subscriber have any problem bringing it in? Which store do you guys go to? I will try the same store for hassle free repair job. Thanks
Click to expand...
Click to collapse
Took mine into the bell store at guilford mall, originally purchased at wireless wave.Unlocked and being used on the fido network. No issue at all, the guy took down my cell number as a way to track its progress.
ssj2miguelx said:
Is there a chance that my phone has a bad internal SDcard?
Click to expand...
Click to collapse
There's no way to know for sure. Some ppl seem to have a bunch of force closes bfore it dies and others just turn it on and it's dead.
Hi so I just heard that the D3 was rooted two days ago (been keeping up until a week ago). I'm not exactly a pro in this area or have ever rooted a device before but I have spent quite a few hours today reading up on the process and any info I could find.
Basically I just want to know if I should root my D3 or wait out another week or so? I heard that a SBF (?) hasn't been found yet so the stock rom can't be recovered and there is really no recovery net yet so should anything go wrong, there aren't a lot of options.
There is a one-click method to root but I'm going to try the original method using the adb shell (lol still researching what on earth to do with that still, just installed the android sdk :x). I'm not concerned about the process of rooting my droid, it's what comes after that makes me hesitant in doing so.
I read that there is a (seemingly simple) method to unroot the D3 by deleting the su file in some directory and rebooting (can't remember, it seemed legit however). Would "unrooting" have any consequences or would your device be back to the exact same state it was in right before you rooted? I'm not planning to drastically mess around with my D3 should I root it. Just want to take a few screenshots in an app to help out a dev, freeze any bloatware that won't cause problems, do a complete nand backup, and... thats about all that comes to mind right now.
I guess what I'm trying to ask is if rooting my D3 tonight would have any irreversible consequences and if there is any benefit in holding off the root?
Oh! Btw the OTA, I know that rooting won't affect ones ability to receive the update but that it will unroot your device and keep it that way. Would the rooting-discovery process have to start anew for people who update using the OTA (Thinking Verizon might patch the root-exploit) ? I know that updating via OTA isn't too bright anyway because devs just take the update and build on it before releasing it on their own custom ROMs and whatnot, but I feel official updates are somehow more stable (most likely flawed thinking, feel free to correct me on that lol).
Yes - SBF is an important component which would guarantee 100% pre-root configuration.
Removing the su binary and the superuser app would however put the phone back in factory state for this exploit. But anything you do while rooted inside /system is your responsibility to correct. Motorola patches usually verify only file existence/checksums and not creation/modification dates, so you should be fine with simple push of the removed (or renamed) stuff back. I remember I was able to update my D2G without unrooting in the past, but that's not necessarily granted for any other updates of that or any other Motorola phone. Ideally, you want phone in factory state to guarantee update will pass.
Another issue is nand backup you mentioned. Custom recovery isn't yet available for this phone. You can't do nand backups. So even this "safety net" isn't here. Installing custom recovery is a "100% secure way" to have OTA updates fail to apply since it messes up with phone's /system files. Un-doing CWM is a bit more complex than unrooting only and if not done carefully - a sure way for a soft brick. SBF is what we all want before start messing with anything, IMO.
So if an OTA updates fails for whatever reason, your phone will get soft bricked or?
I don't think ill be updating anway, but its good info to know for the future.
Sent from my DROID3 using Tapatalk
I would say root the device and don't worry about unrooting. If you have to return it to the store or something, unfreeze the apps and delete su. Once you mess with it though, it will be very difficult (impossible?) to ever make /system binary identical to the factory image without an sbf. That said, I doubt VZW takes the time to investigate this very closely.
But I don't see any other reason to ever unroot. When the OTA update comes down, just don't install it. In a few days after its first released, the community developers will tell you how to install it with root and not botch anything up.
Dmw017 said:
So if an OTA updates fails for whatever reason, your phone will get soft bricked or?
I don't think ill be updating anway, but its good info to know for the future.
Sent from my DROID3 using Tapatalk
Click to expand...
Click to collapse
No - fortunately not. It will just say "Update failed" and phone will reboot back to normal.
Regarding updates - you may want to reconsider - updates usually fix bugs, bugs like the bluish camera or the wrong geotagging. Or stuff like phone shooting at max brightness after removal from HD dock.
But as the other poster mentioned - the community would do the hard work for you 'back-porting' the update to a rooted phone. Sure enough - we need custom recovery to be made before we can install any 'backported' updates or other customizations.
But all will come with time.
If you need to use an app that requires root (like openvpn or VPNC), or if you want to remove some of the unwanted apps Verizon stuck on the phone, you should root of course, but if you don't care about such stuff and want to be 'compliant' with stock software - stay as is, until at least SBF comes.
Yeah I rooted already but should an update come, I could always unroot my device. An update would be really welcome too. Yeah the bluish tint on the cam is bad but there are soft fixes for that. What I really really want out of the update is the huge improvement in battery life I've heard about. Im using the extended battery right now and straight up, it sucks. I've heard good things about the extended battery but mine lasts ... maybe 10 hours under light - medium usage, playing music for several hours and having the display on for about an hour. I expected a lot more. Numerous people have reported getting 24-48 hrs of life while others got 15 under normal/heavy use.
There have been a few reports of peope already receiving an OTA update (devs/testers most likely) but have said many pf the d3s current issues were fixed with it, primarily the blue tint on cam and the battery life.
Honestly, with root, I figured my battery would outlast a day like a champ, but there have been no/minimal improvements, even with every piece of bloat frozen. I even froze google Maps because it constantly showed up as using cpu (and therefore battery), have my radio set to cdma, and only have 1 gmail account syncing.
Sent from my DROID3 using Tapatalk
I bought the N1 on the day it came out and it's still going fine. Well I must provide soem caveats here so say it's not the original unit. I have gone through 2 RMA's with HTC and 2 paid for repairs for the power button. The last time the power button failed, the repair only lasted abouit 6 weeks and when I complained they sent me a refurb rather than fix it.
For me the only issues for the N1 are
- flaky touch sometimes (go to suspend and back usually fixes it)
- constantly running out of system memory and all apps I can move are moved to the SD card.
So it's either get a new phone or root the N1. Given that the phone works for what I want rooting and a new firmware might be the answer.
So given that I have never rooted a phone or installed new firmware, can people suggest the most appropriate firmware I should be looking at and the easiest way to get there. The phone is currently on 2.3.6 (OTA).
There is so much conflicting information out there it's hard to know what the best route is.
Thanks
lchiu7 said:
I bought the N1 on the day it came out and it's still going fine. Well I must provide soem caveats here so say it's not the original unit. I have gone through 2 RMA's with HTC and 2 paid for repairs for the power button. The last time the power button failed, the repair only lasted abouit 6 weeks and when I complained they sent me a refurb rather than fix it.
For me the only issues for the N1 are
- flaky touch sometimes (go to suspend and back usually fixes it)
- constantly running out of system memory and all apps I can move are moved to the SD card.
So it's either get a new phone or root the N1. Given that the phone works for what I want rooting and a new firmware might be the answer.
So given that I have never rooted a phone or installed new firmware, can people suggest the most appropriate firmware I should be looking at and the easiest way to get there. The phone is currently on 2.3.6 (OTA).
There is so much conflicting information out there it's hard to know what the best route is.
Thanks
Click to expand...
Click to collapse
I have a rooted N1 that I bought in February of 2010, a month after they became available. It was rooted when I bought it on eBay and running one of the CM ROMs. I don't know how to root a phone, sorry.
I DO know how to load ROMs and have variously updated and modded the phone myself. I have been fortunate in that my power button has never failed, but while I was running a series of OTA ROMs (ROMs based on the pure Android released from Google) I noticed that the latest ones disabled the trackball wake feature, meaning that the power button was the only way to wake the phone. I had gotten used to trackball wake with the first CyanogenMod ROM, and so once I learned that the power button was a weak spot, I decided that a CM ROM or a modded AOSP ROM was the only option.
As there were some issues with CM ROMs that took months to work out (see WONK), I went with an AOSP ROM that I found here http://forum.xda-developers.com/showthread.php?t=1121595 . It's now a dead thread, but the links to the 3.1 version of the ROM is still there. I use the apps2SD version of the 3.1 ROM.
There are several more ROMs that are more recent, but this one is the best one I have ever found. You will need to root your phone and install a custom recovery (like AmonRA or ClockworkMod) to use it, but I have found that everything works well and it is extremely stable. I have over 70 apps on my phone with over 80MB of internal memory still available.
The only problem I have ever had is an intermittent battery drain, which I was able to fix by wiping the cache files (Dalvik and regular caches). The custom recoveries have the ability to do this. Apparently any corruption of the cache files causes excessive battery drain, but wiping them (which causes the phone to rebuild them on the next boot - a 4 minute process!) gives you fresh cache files and fixes the problem.
If you are willing to learn how to root your phone and install a custom recovery, I can recommend that ROM. Once the first part is done, loading a custom ROM is as easy as putting the zipped ROM file on your SD card, getting to the bootloader and telling it to install the zip.
Well just so you know, rooting or installing any ROM will never stop the touch input problems. Its my main dislike about the N1. Apps2SD would solve your storage issues though and all the extra little perks of rooting just sweeten the deal.
Replacing a phone is expensive and just not necessary for the N1 yet. May as well root in my opinion. CM7.1 is now perfectly stable, include trackball wake, can support A2SD as far as I know and has some nice extras too.
As well as that it shouldn't be TOO much longer until we get a decent ICS ROM.
Hope that helps you.
addam360 said:
Well just so you know, rooting or installing any ROM will never stop the touch input problems. Its my main dislike about the N1. Apps2SD would solve your storage issues though and all the extra little perks of rooting just sweeten the deal.
Replacing a phone is expensive and just not necessary for the N1 yet. May as well root in my opinion. CM7.1 is now perfectly stable, include trackball wake, can support A2SD as far as I know and has some nice extras too.
As well as that it shouldn't be TOO much longer until we get a decent ICS ROM.
Hope that helps you.
Click to expand...
Click to collapse
Thanks. I never expected the new ROM to fix the touch input problems. That is a fundamental hardware issue.
I was thinking along the same lines regarding ICS. It's gone AOS now and I now see somebody has built a port for the N1 already. So if I wait a bit if I choose to install some custom firmware, if the reports suggest ICS runs fine on the N1 (to confirm that Google didn't release it because there was a performance issue with the N1 and ICS) then that's the route I will take. In for a penny, in for a pound I guess!
lchiu7 said:
(to confirm that Google didn't release it because there was a performance issue with the N1 and ICS)
Click to expand...
Click to collapse
The issue is not because of performance, its the system partition size is not enough... Gosh! Did u know Galaxy Nexus's system dump is 600MB+
I used to be a Droid 1 user and I played with a lot of custom ROMs. Got the Droid 4 on release day and I'm thinking of playing around with custom ROMs.
If I install the recovery and a custom ROM, isn't the factory restore option always on the phone so anytime I want, I can restore the phone to the day I got it?
Are there any downsides to installing custom ROMs as of now (such as battery, glitches, etc)
I rooted my phone and I've seen a decline in battery life. There is another thread about it but I wanted to ask here, anybody else have this issue?
Lastly, is it worth installing custom ROMs now or just waiting for the official ICS update? I basically just want a working phone with the best battery possible. The only reason I rooted was to uninstall the bloatware on the phone however wifi tether and screenshot are nice to have.
Thanks!
Installing any custom ROM right now is going to be a little risky simply because there are no fastboot files to restore your phone with. Now, SafeStrap does a pretty good job of minimizing that risk by creating what is essentially a dualboot environment allowing you to run a secondary ROM on your phone while leaving the stock ROM intact.
I am running the ICS Beta ROM by Hashcode and it is running really well for me. Battery life has been fine, pretty much on par with stock. Being a beta there are things that are not perfect but I am using it as a daily driver with no issues. You can find a list of known bugs in the ROM OP. Although it seems to be hit a miss with some of them. I have had no issues with wifi or mobile data connections at all.
I ran stock rooted for about 1 1/2 weeks and didn't notice any decline in battery life personally. Not I froze apps rather than uninstalling anything so I could get them back if I needed to. And I really didn't freeze much unless it was something I saw running in the background that I knew I wouldn't need/use.
Really, if you are just looking for a phone that works with the best battery life, you are probably better off staying with stock. In my experience with the Droid 2, no ROM I ran could touch stock for battery life. And really, I think the stock experience on the D4 is fine. The bloatware wasn't overly bad IMO, smart actions is pretty neat, and the UI was plenty snappy. I'm just a flashaholic.
I am quite happy with stock after debloating it.
Sent from my DROID4 using XDA
Thanks for explaining safestrap. Does it actually set up a dual-boot environment, or does it swap out /system, /data, etc. I've tried reading hashcode's blog, but the instructions are a little fuzzy on what exactly is going on. I don't have my D4 yet, and I'd like to get a handle on what exactly safestrap is doing before I take the plunge.
Currently I have a D1 and I'll fully admit I'm spoiled that it is essentially unbrickable. Once, I screwed it up so bad that it wouldn't even boot up into recovery. I have no idea how I managed that, but a quick session with RSDlite fixed everything...
Of course, I know a lot more now than I did back then, but here is hoping we get hold of some fastboot images for the D4 soon...
I finally took the plunge and installed Safestrap. Once your phone is rooted, you just run an APK installed on your phone. The process feels incredibly clean, and I was completely comfortable that as long as I was careful, nothing bad would happen. This proved to be true.
It really does set up a dual-boot. I spent several hours today playing with CM9, and when I was done, I simply disabled the safe system, and the phone booted right back up into my rooted and debloated stock. The most dangerous part is making sure that you do NOT try to flash over the non-safe system, and, in fact, Safestrap generally won't even let you do that.
Not only did I find that Safestrap worked great, but CM9 works better on the Droid 4 than almost any other device I have played with it on. If they can make sure that the data connection is reliable and get the font camera working, it is practically ready for prime time. Everything else works great. I am now confident that we will see CM9 for the Droid 4 as soon as CM itself is complete and stable, since drivers do not seem to be a problem on this phone. I also suspect we will see some CM7-based roms quite quickly as well.
I am also very glad of the option to always easily revert back to the stock system without losing anything, it will make going to the Verizon store very easy if I ever need to.
I also came from a D1, installing ROMs was so easy, I'm a little hesitant on this one especially since a genuine ICS update is on the way. I might wait for that before I try custom ROMs. I use a front camera a lot so CM9 is unfortunately out of question. My battery issue was solved with a calibrate (deleting batterystats) even though it's not supposed to work, I can confirm that it definitely worked for me.
Once you toggle on the safe system, installing ROMS is just as easy as it was on the D1. What is nice, though, is you can keep your stock system fully in tact. I actually keep my phone on a simple rooted stock, but when a friend asks about Android ICS, I just toggle on the safe system, and boot it up. When I'm done, I toggle off the safe system, and back to stock. Safestrap is awesome.
core2kid... this is moto, the official update is gonna take 3-6 months so i would not suggest waiting it out.
i came from a D1 as well and safestrap bugged me out for a while... but once i installed and started using it i really like it. think of it as a dual-boot.
1 is your stock system that you do not f** with... you just leave it so that you have a backup should you f** up your...
2nd system is the one you flash all your ROMs on... no matter what you do to it, the first system is not touched, so you have to try REALLY hard to brick it.
Thanks. I'll give it a go. Last question, if I have hardware issues with the phone, is there a way to restore it to factory so I can warranty it? My main concern is my battery dying. I don't want to be stuck with a useless phone because the battery is in built.
i cant say with 100% certainty, but theres got to be a way.
as for the battery... it will probably die the day after your warranty is up, and by then there will be DIY replacement kits.
greekchampion04 said:
as for the battery... it will probably die the day after your warranty is up, and by then there will be DIY replacement kits.
Click to expand...
Click to collapse
With my luck, I can see that happening :/