Related
...I lucked out and got a brand new one with 1.0.0 firmware, so I stuck with it and used the AutoNooter for that version, then blocked B&N from pushing updates. I have the whole thing running basically how I want it to now and I'm very happy, but I have one burning question:
Is it worthwhile to overclock it and would that really enhance my user experience at this point? I've never overclocked anything before and the last thing I want to do now, after all the tweaking I did and money spent, is to destroy the little guy.
So, experts hereabouts:
Given my hardware, firmware, etc., do you think it's safe and worth the effort to use a kernel to push it to 1.1Ghz or 1.0Ghz? Are these kernels stable or am I going to regret it when something really wacky happens?
I keep mulling it over, so any help is greatly appreciated.
Most people seem to report that 950 Mhz is tops for 2.1 (the android version currently on your nook). It highly unlikely that it will harm the hardware and you will see a modest increase in performance.
For 2.2 and 2.3 (CM7) people are going as high as 1.1 GHz without issue. I'm currently at 1 Ghz and am enjoying it. No problems (knock on wood).
Thanks for the response! I was also concerned that staying at 1.0.0 was unwise or that, perhaps, I should try using Android 2.2, but that all seemed to be fairly experimental/scary to me.
junkrobot said:
Thanks for the response! I was also concerned that staying at 1.0.0 was unwise or that, perhaps, I should try using Android 2.2, but that all seemed to be fairly experimental/scary to me.
Click to expand...
Click to collapse
I have only had my NC for a little over a week now and have had all the popular roms installed. I have tried CM7, Froyo and Honeycomb. It's all pretty easy just make sure you read all the install instructions and you should be fine. Also I made nandroid backup as well as a titanium pro backup of my apps. So it is pretty easy to revert back to my stock rom if I wanted. My suggestion is to read through the threads for all the different roms in the development section, it will give you a good grasp of how to install and what bugs are still existing. A good start for you is to get titanium backup and rom manager so you can do the backups first then start experimenting to see what you like.
From my limited testing I don't think CM7 and Honeycomb are quite ready yet, they still need a couple things worked out which I am sure will happen soon especially with the SDK released for Honeycomb now. I liked Honeycomb the best but a couple apps I use regularly wouldn't run for me at the present stage(Aldiko and IMDB, I didn't try much else as I really use those apps alot and couldn't live without them). As for CM7, everything I tried worked well but the battery drain seemed rather high for my liking compared to stock. I am now running Froyo customized 0.6.8ver2, I loaded it on last night so haven't had much time to play around with it yet but so far it seems to run pretty well, all apps I have tried work. Not sure on the battery drain yet but will keep an eye on it.
If you need some help let me know, I am not an expert but haven't bricked my NC yet and I don't mind helping out where I can.
kevin
Thanks a ton, Kevin! This seems like a really nice community. I'm going to keep researching and see what I can conclude. I made a back-up with Clockwork the other day just in case something weird happened, so I'm weighing out the pros and cons while sifting through these threads. Honestly, I don't have a problem with how things are running now, but making a little snappier, in the parlance of the boards, would be nice. I wonder if there's a way I can up the performance without overclocking it?
Also, this is the method I used to block B&N updates:
http://forum.xda-developers.com/showthread.php?t=946969
It seems there was a bit of debate as to if this would actually do the trick, so I'm kind of worried. My NC has been connected to wifi constantly since day one, so I don't know if this is/isnot working. Anyone have any advice in this regard or experience? How do updates get pushed?
junkrobot said:
Thanks a ton, Kevin! This seems like a really nice community. I'm going to keep researching and see what I can conclude. I made a back-up with Clockwork the other day just in case something weird happened, so I'm weighing out the pros and cons while sifting through these threads. Honestly, I don't have a problem with how things are running now, but making a little snappier, in the parlance of the boards, would be nice. I wonder if there's a way I can up the performance without overclocking it?
Click to expand...
Click to collapse
Hey Junkrobot - Just take your time. It takes a little while to get a feel for things. I have been rooting and installing roms on Android phones since they came out. At first, I would worry a lot but as I gained experience, I felt more comfortable. Now I think I enjoy trying ROMs more than actually using the device like a normal person.
The Nook Color is a great device to get started because it boots from the sd card which means it is nearly impossible to brick. If something gets messed up, you can always boot from a bootable sd card and install a rom or restore a backed up image. That said, if you enjoy the device as it is, there is no rush to upgrade.
I think part of my anxiety is just the sheer amount of time it took me to get things in order since I was so new at it. Day one was pretty stressful, as I'm sure it was for most folks.
Just an FYI, the Nook is really hard to brick since it boots up first from the SD card. You can always make a CWR card which should allow you to flash it back to stock or another ROM.
Does backing up in Clockwork also preserve my apps and settings?
I'd be really stoked if I could also somehow be sure that OTA can't push an update on me. In my mind, B&N is out there, waiting to strike.
No, use Titanium Backup or MyBackUp
I have Gingerbread working nicely thanks to this wonderful forum, but sadly I am scared that my kids will kill me without the Read to Me option. Is anyone working on this?
not that i'm aware of. there are lots of folks on xda that want the B&N stock apps to be ported, but i haven't seen that anyone is actively working on them.
thanks was just reaching out to find out so I could have an idea, would be nice though. Thanks again for the info.
buffalosolja42 said:
thanks was just reaching out to find out so I could have an idea, would be nice though. Thanks again for the info.
Click to expand...
Click to collapse
There are two problems facing us:
1) The Nook app is not open source, so B&N can slap us around with a cease and desist, if devs go posting a modified version of it. This is the same reason that all the other non stock OS builds modified the boot image.. it's B&N's.
2) Even if that weren't a problem, the special nook app relies on the heavily modified framework of their Eclair build. So, while it is not impossible, it is unruly, and combined with #1, doesn't make for a project worth undertaking..
Ok, I'm a little overwhelmed by the number of nook roms out there, and I would like to know what everyone uses and why.
I've tried 2, and they all have benefits/negatives and I'm trying to figure out which to be my daily driver, while we wait for the next generation of roms to come about.
constellanation said:
Ok, I'm a little overwhelmed by the number of nook roms out there, and I would like to know what everyone uses and why.
I've tried 2, and they all have benefits/negatives and I'm trying to figure out which to be my daily driver, while we wait for the next generation of roms to come about.
Click to expand...
Click to collapse
well which 2 have you already tried?
I personally use CyanogenMod 7, but that's because I use it on my Droid, and that's because it's the first ROM I found when I got my droid.
I haven't had it crash on me yet, but there was a Wi-Fi problem I had to fix through ADB. (Link) Otherwise, it's been more than good enough for a daily driver. I really haven't had experience with other ROMs. I just flashed the thing with CM7 while I was still in B&N. I would recommend a Honeycomb ROM, but that's not very "complete" yet.
Sorry I can't say much else (), but I gave my $.02.
barrist said:
well which 2 have you already tried?
Click to expand...
Click to collapse
I wasn't going to mention them so I could hear everyone's full opinion despite what I've tried and not hold back because I've tried it.
However, I don't want to be a **** so it's cm7 and HC v.4 now don't let that sway your opinions!
dkabot said:
I personally use CyanogenMod 7, but that's because I use it on my Droid, and that's because it's the first ROM I found when I got my droid.
I haven't had it crash on me yet, but there was a Wi-Fi problem I had to fix through ADB. (Link) Otherwise, it's been more than good enough for a daily driver. I really haven't had experience with other ROMs. I just flashed the thing with CM7 while I was still in B&N. I would recommend a Honeycomb ROM, but that's not very "complete" yet.
Sorry I can't say much else (), but I gave my $.02.
Click to expand...
Click to collapse
I was having the wifi issues to (Atleast I assume it's the same, I would just lose connection and have to reconnect pretty consistently) the thing that actually bothered me most about it was the back and menu buttons up at the top right. To small, wanted a different more tablety layout.
constellanation said:
I was having the wifi issues to (Atleast I assume it's the same, I would just lose connection and have to reconnect pretty consistently) the thing that actually bothered me most about it was the back and menu buttons up at the top right. To small, wanted a different more tablety layout.
Click to expand...
Click to collapse
Oh, no the Wi-Fi issue was much worse. I couldn't get the chip to activate! At least the fix worked, though.
If "too small" is the problem, increase the LCD Density.
If you want a more tablet-like layout, you will have to deal with Honeycomb in its current state.
If you don't like the CM7 buttons, use SoftKeys or Button Savior.
(I would post links, but I can't.)
I tried soft keys, but I haven't tried button savior. and didn't know about lcd density. If I go back (which isn't in my nature with roms) I may try it out.
I'm really liking honeycomb especially as far as layout, but I would like a bit more stability. But really I Can live with whatever, the nook is really my fourth internet device and currently just a toy.
constellanation said:
I tried soft keys, but I haven't tried button savior. and didn't know about lcd density. If I go back (which isn't in my nature with roms) I may try it out.
I'm really liking honeycomb especially as far as layout, but I would like a bit more stability. But really I Can live with whatever, the nook is really my fourth internet device and currently just a toy.
Click to expand...
Click to collapse
The solution is patience, then.
Wait for the Google to give us the source, and all your problems will be solved.
(Don't forget that HC is a port of the SDK emulator image.)
well I knew that, that's why I wanted to know what everyone else is using so maybe I could try some other things out... during that wait it out time
Well... if you want to try a Galaxy Tab-like experience, try this:
Install Nookie Froyo
Set LCD Density to 250
Install ADW and set the app drawer to paged.
(Continue with other minor tweaks here)
i'm rolling nookie froyo 0.6.7, but i'm going to move up to 0.6.8 soon. i like it, but i'm sure honeycomb is much better. since the bugs in hc for the nook color are still being hammered out, though, i'm going to stick with the stable froyo rom for the time being.
dkabot said:
Well... if you want to try a Galaxy Tab-like experience, try this:
Install Nookie Froyo
Set LCD Density to 250
Install ADW and set the app drawer to paged.
(Continue with other minor tweaks here)
Click to expand...
Click to collapse
Is this rom an actual port of the tab, or is it just made to look like the tab?
droiddoes69 said:
i'm rolling nookie froyo 0.6.7, but i'm going to move up to 0.6.8 soon. i like it, but i'm sure honeycomb is much better. since the bugs in hc for the nook color are still being hammered out, though, i'm going to stick with the stable froyo rom for the time being.
Click to expand...
Click to collapse
Yeah this is kind of the info I was looking for, trying to see which roms had what features and still had the best stability.
HC is awesome, but not yet a daily driver (unless you're the adventurous type) I have a friend who is about to buy a nc for himself and he wants me to root it for him. I have no problems with a buggy rom for me, but for him I need stable yet best.
not sure where you are getting the idea that there are so many roms to choose from.
We have stock rooted, nookie froyo, honeycomb v3 and cyanogenmod (gingerbread).
there is one modified version of cyanogenmod -- firemod and one customized nookie froyo build. thats about it as far as i know... am i missing a bunch of roms somewhere?
you can try all of them out relatively quickly and form your own opinion but if you insist....
stock rooted is the most functional option at the moment. oc to 1100mhz for speed and other tweaks. nookie froyo is second with faster overall 'smoothness' but still has some bugs to work out. third is cyanogenmod which is quickly catching up to froyo and is my personal favorite. just needs video acceleration at this point. last is honeycomb but very fun to play with.
lafester said:
not sure where you are getting the idea that there are so many roms to choose from.
We have stock rooted, nookie froyo, honeycomb v3 and cyanogenmod (gingerbread).
there is one modified version of cyanogenmod -- firemod and one customized nookie froyo build. thats about it as far as i know... am i missing a bunch of roms somewhere?
you can try all of them out relatively quickly and form your own opinion but if you insist....
stock rooted is the most functional option at the moment. oc to 1100mhz for speed and other tweaks. nookie froyo is second with faster overall 'smoothness' but still has some bugs to work out. third is cyanogenmod which is quickly catching up to froyo and is my personal favorite. just needs video acceleration at this point. last is honeycomb but very fun to play with.
Click to expand...
Click to collapse
That might be all of them, it seems a bit more for anyone walking into this dev thread, with the internal and on sdcard roms.
But seeing them listed out like this is very helpful thank you!
Is there large differences between the customized roms and their noncustomized origins?
personally id recommend rooted stock rom. Ive tried nookie froyo and honeycomb v4. Froyo was really slow. It was really frustrating browsing with it. Honeycomb is much faster than froyo but a lot of apps dont install. Stock rom was stable and I wasnt able to install just a couple of apps that I tried from the android market
personally, i'm only adventurous to the point of rooting. after that, i want stability. i don't mind staying a release or 2 behind the most recent releases just so i know the issues are being dealt with.
with froyo, i'm able to use my own launcher and customize pretty much to my liking. i still don't see all the apps i want in the market, but there are enough forum posts here and on android central that link you to apk downloads so that you can install them through adb. i've seen some fixes for this, but it seems to be an issue on both froyo and hc. hope this helps!
survivor_evil said:
personally id recommend rooted stock rom. Ive tried nookie froyo and honeycomb v4. Froyo was really slow. It was really frustrating browsing with it. Honeycomb is much faster than froyo but a lot of apps dont install. Stock rom was stable and I wasnt able to install just a couple of apps that I tried from the android market
Click to expand...
Click to collapse
I didn't like how much the stock rom seemed like, well a nook color which is great but in this instance I wanted to get a tablet!
droiddoes69 said:
personally, i'm only adventurous to the point of rooting. after that, i want stability. i don't mind staying a release or 2 behind the most recent releases just so i know the issues are being dealt with.
with froyo, i'm able to use my own launcher and customize pretty much to my liking. i still don't see all the apps i want in the market, but there are enough forum posts here and on android central that link you to apk downloads so that you can install them through adb. i've seen some fixes for this, but it seems to be an issue on both froyo and hc. hope this helps!
Click to expand...
Click to collapse
With my phone, I'm less adventurous, I have calmed down to where now I only put release candidate and stable cm roms.
However I got this nook for a really really great deal (100$ plus the cover) and I want to try out whatever I can (and if possible help, though I have little to none coding skills) I might have to try the froyo build out since it's technically the only one I Haven't tried based on the above list (minus the 2 custom roms)
I kinda wish there was a customized version of the stock rom.
I guess the oc kernel counts?
zealious said:
I kinda wish there was a customized version of the stock rom.
I guess the oc kernel counts?
Click to expand...
Click to collapse
I actually just bought setcpu to try overclocking the kernals a little bit on my NC.
What would You customize about stock?
after flashing back to froyo i must say it is far better then I remembered.
maybe it's the newer kernels but it is fast and smooth. hardware video works which i was missing on cm7.
so i change my (current) order to nookie froyo, then stock rooted, followed by cm7 and then honeycomb. i would try them all though and see for yourself.
I've seen modifying build.prop, using sqllite, and changing the name of the otacerts file. Doesn't seem build.prop is valid here until someone gets a hold of one with the new update. But I don't want to lose my root. So, what's the consensus? (please vote in the poll)
Here are the 3 mentioned:
1. Rename OTA Certs
2. Use Sqllite
3. Edit Build Prop
The build.prop is sort of experimental but seems to be working so far from reports.
The consensus is definitely to read the other 1000 threads on the subject before starting yet another one.
Really? There are 1000 other threads that compare all 3 options?
All the ones I read are where someone brings up one thing and then a few other people chime in on a different one. I was trying to find out, in one place, what the most recommended one was.
It is my fault for not creating a poll at first.
It is your fault for being a jackass.
ADude said:
The consensus is definitely to read the other 1000 threads on the subject before starting yet another one.
Click to expand...
Click to collapse
I'd say he's read the 1000 threads, given the fact that he rattle off a list of suggested solutions from those threads.
FWIW, I too am interested in knowing if this issue has been settled. Just rooted my NC the other night, am really enjoying all teh apps I've downloaded and would be happy to block updates and wait for a rooted 2.2 update.
So if anyone knows the definitive answer ot the OP's question, please do let us know.
for what it's worth
doncaruana said:
I've seen modifying build.prop, using sqllite, and changing the name of the otacerts file. Doesn't seem build.prop is valid here until someone gets a hold of one with the new update. But I don't want to lose my root. So, what's the consensus?
Click to expand...
Click to collapse
Don,
I haven't read the reputed 1,000 other posts on this topic, so I don't know what consensus may have been reached there, but this is my take on it:
- otacerts renaming isn't going to be reliable
- the sqllite fix (modding the fota.mode item) is a permanent fix, which eliminates any possibility of OTA updates creating problems
- modding build.props may work, even if you don't have a master to reference from.
I.e., some reasonable higher settings for ro.build.version.incremental, ro.build.description, and ro.build.date MAY do the trick, even if they're not a clone from a legit updated version. I don't know (perhaps someone else does) if perhaps only one of those is really necessary, E.g., something like ro.build.description=2.1.0.428.int.enc.rrdp.s39975 may be enough to do the trick, since it holds the main versioning string (currently at 1.1.0.328).
So my recommendation if you want to be sure would be to do the sqllite fix.
- Mark
Flash CM7..... problem solved
I added links to the 3 methods I mentioned, for everyone's reference anyway. I did also read somewhere that someone said that installing CMR would stop OTA updates as well. But didn't see a lot of discussion about that.
xwint3rxmut3x said:
Flash CM7..... problem solved
Click to expand...
Click to collapse
I don't think CM7 is ready for prime time on the NC. Last I saw video driver and flash still had issues. I too would like to see a 2.2 stock update so it could be rooted. BTW I am running Nookie Froyo right now and it is pretty sweet.
I tried the CM7 Agnostic SDCard option and nightly build and, well... did I mention it isn't ready for prime time?
But I am one of those fringe lunatics that never says anything important, never gets noticed, and is instantly marginalized. I'll likely die an early death and no one will notice...
Sorry, to get back on topic, I don't think CM7 is ready yet for Nook Color.
Nothing to see here, move along.
migrax
Agree. CM7 is not quite up to where it needs to be as a daily driver.
build.prop flat out works... End of story.
Of course someone needs to get the build.prop from the new one when it's released, so if you're really scared about it, stay off wifi I suppose. But it usually takes a while before people start getting it.
khaytsus said:
build.prop flat out works... End of story.
Of course someone needs to get the build.prop from the new one when it's released, so if you're really scared about it, stay off wifi I suppose. But it usually takes a while before people start getting it.
Click to expand...
Click to collapse
The build prop only blocks one update. In order to block the Froyo update, you'd need the build prop for the Froyo update. That would only work until there is another update. Then you need the build prop from that update to block it. It becomes a vicious, never ending cycle. I may be incorrect in my understanding though.
I don't think anyone really knows at this point which is why there are "1000 threads" on the topic. We just all have to sit back, drink a beer or 7, and wait until the next update is being pushed out. I personally went with the SQlite edit in Root Explorer. Seemed like the easiest way to me.
Pre-dawn raid said:
I don't think anyone really knows at this point which is why there are "1000 threads" on the topic. We just all have to sit back, drink a beer or 7, and wait until the next update is being pushed out. I personally went with the SQlite edit in Root Explorer. Seemed like the easiest way to me.
Click to expand...
Click to collapse
That's what I'm going to try. I found the entry, but haven't changed it to "manual" from "auto" yet.
Update questions
I'm running Android 2.1 on my rooted Nook Color. What will happen if I don't block Barnes & Noble's upcoming update in April? Will my NC merely become unrooted and operate like a regular stock Nook Color? Is it possible that any damage will be done to the NC?
I'm actually curious to see exactly what an updated, unrooted NC will look like and how it will operate. I know that somebody eventually will come up with a way to root an Android 2.2 Nook.
My rooted 1.0.0 NC (Dec. ~8 autoroot) ignores the updates *DOING NOTHING AT ALL*. I can use the Market, download books from BN, etc.
Knock on wood!
cameraz said:
I'm running Android 2.1 on my rooted Nook Color. What will happen if I don't block Barnes & Noble's upcoming update in April? Will my NC merely become unrooted and operate like a regular stock Nook Color? Is it possible that any damage will be done to the NC?
I'm actually curious to see exactly what an updated, unrooted NC will look like and how it will operate. I know that somebody eventually will come up with a way to root an Android 2.2 Nook.
Click to expand...
Click to collapse
From what I've read on other Andriod devices, it relocks the device and you lose superuser. Still, I'm curious if all the apps I downloaded with root will work after the update. The device was a b-day gift for my sister and she really loves the e-reader aspect, hence why HC and nookie froyo haven't been slapped on there.
Well, if you run the stock launcher on a rooted Nook, you still see all the apps you have downloaded from Market in Extras. So I would assume that the 2.2 upgrade could preserve the apps you have on there. Though, I would always recommend doing a backup, getting updated, wait for whatever exploit is employed and re-enable your apps.
colorado_al said:
Agree. CM7 is not quite up to where it needs to be as a daily driver.
Click to expand...
Click to collapse
Don't tell that the to hundreds of CM7 users running this as a daily.
Honestly, the only functionality "hurting" right now is video performance, as caused by an audio wierdity. Past that, I can't think of alot of broken stuff CM7 needs fixed. Sleep battery performance can be improved i guess... as it is, i like CM7 ALOT more than Froyo (no more SOD!)
migrax said:
I don't think CM7 is ready for prime time on the NC. Last I saw video driver and flash still had issues. I too would like to see a 2.2 stock update so it could be rooted. BTW I am running Nookie Froyo right now and it is pretty sweet.
I tried the CM7 Agnostic SDCard option and nightly build and, well... did I mention it isn't ready for prime time?
But I am one of those fringe lunatics that never says anything important, never gets noticed, and is instantly marginalized. I'll likely die an early death and no one will notice...
Sorry, to get back on topic, I don't think CM7 is ready yet for Nook Color.
Nothing to see here, move along.
migrax
Click to expand...
Click to collapse
I'm with you. Tried the CM7 from SDCard yesterday. It was okay, but it didn't exactly rock my world. Waiting for all the bugs to get worked out. In the meantime, sticking with Nookie Froyo.
Divine_Madcat said:
Don't tell that the to hundreds of CM7 users running this as a daily.
Honestly, the only functionality "hurting" right now is video performance, as caused by an audio wierdity. Past that, I can't think of alot of broken stuff CM7 needs fixed. Sleep battery performance can be improved i guess... as it is, i like CM7 ALOT more than Froyo (no more SOD!)
Click to expand...
Click to collapse
I skipped over Nookie Froyo, but I used stock Root for awhile, and i've been on Cm7 for awhile and I love it. I agree video is not at 100% on cm7, but I really don't spend alot of time watching video on my nc at all. I downloaded the nook app from the market, and the tablet works great. The devs have done a great job, I have no issues using CM7 as my daily driver.
Gotta back you up madcat since we're the only pro CM7 users on this thread
Hello xda. I've been a big selfish user of the stuff provided here for a while, as have many. I own an XPERIA X8 and it's the best phone I've ever owned (ehem.. perhaps because it's the first smartphone I've ever owned). I just wish it was a little better. I enjoyed the stock stuff for a while until my internal storage filled up too much, then I rooted and upgraded it to an easy to install Froyo ROM as it was my first time doing such things (as good as I am with programming PC's, I thought I would surely screw that up). It was great and had kept me happy for over a year, but I didn't realise how old Froyo was until I heard about Jellybean and 'Project Butter' and how it even outperforms old versions of Android. I've been limited in Froyo to relatively basic stuff anyway so I thought since I'd basically installed an android version only one step up from the stock Eclair, there'd be a lot of better versions out there.
This is where my nightmare begun. Since I already had xRecovery, I thought the process would be as simple as "download rom, install in xRecovery". A bit too ambitious, I ended up "soft bricking" my phone and having to fix it by going back to Eclair. Then, somehow, I could not even root the damn thing under the guidance of any tutorial. It's like it suddenly caught an immunity. After ages of meddling I managed to do so and get to the next step. Then the problem occurred that Superuser wasn't kicking in and allowing anything root access. I also had problems getting a new kernel on the phone and ended up only managing to install some random kernels I wasn't even sure supported the rom I was trying to install. I had some more problems trying to install CWM and it was around then I noticed another occurring problem. Apparently for installation of Jellybean, I needed to unlock bootloader, which apparently can't be done on devices with a certain version of motherboard. Mine is 11W41. I heard that this sometimes doesn't matter depending on the specific version, but after all the problems and reading up how hard it would be to recover from a problem if it occurred. So after a long time not finding alternate solutions, I decided to go for something lower.
Ice Cream Sandwich apparently had a similar problem, but I didn't spend long looking (by that time it was really late at night and I just wanted to at least get rid of Eclair again). Eventually I installed Gingerbread, which managed to work well... the second time I tried. The first time I mucked something up and ended up going back to Eclair yet again. Well, now I at least have the GingerXperia Revolution V3 rom installed, but I'm still wondering if this is the best I can do according to the X8. So yeah, that's the rant of my nightmarish story, but this is, ehem, a Q&A... so my question is, before I get too settled with my current phone set-up, is there any better option for my phone? Have I misunderstood some things and I actually do have a way of updating my kernel in order to install a better rom? From a rom, I obviously just want a well-packed version of android (Froyo was way to simplistic, having very few options to improve the experience), which is fast and suitable for every day use. As a bonus I would like it to be swappable so I can increase the RAM with SD memory and increase internal storage size (even with the ability to move apps to the SD, the phone fills up way too fast). I'd be very surprised if I've managed to pick the best way to upgrade my phone.
I know this heavily depends on opinion, so I just want to hear it. If there is better things I can do to it, I could do with a point in the right direction!
i honestly read that long post. welcome to xda mate.
tbh, i haven't tried that particular rom yet. so i can't tell you rom is "better" (which is subjective, if you ask me), so i'll try to answer the other points in your post.
since you have a locked bootloader, we're limited to roms, apps, and tweaks. a different kernel would do wonders to your phone, but since that's out of the question i think the best way to go is how to improve performance using other methods. please note that whatever i write here is my opinion. other users may think differently.
apps: i use mounts2sd for swap and a better alternative to our native app2sd feature. greenify is another app that is getting great reviews, though i try to not use task killers as much as i can. if you're into mobile gaming chainfire 3d is another app you could use.
tweaks: crossbreeder and v6 supercharger. i've personally used (using CB right now) try them and see. remember to make a backup to be safe.
that's all i can think of in short notice. i'm sure there are others and you just need to look in xda more. also, try a couple of roms before you get settled on one.
Deji666 said:
Hello xda. I've been a big selfish user of the stuff provided here for a while, as have many. I own an XPERIA X8 and it's the best phone I've ever owned (ehem.. perhaps because it's the first smartphone I've ever owned). I just wish it was a little better. I enjoyed the stock stuff for a while until my internal storage filled up too much, then I rooted and upgraded it to an easy to install Froyo ROM as it was my first time doing such things (as good as I am with programming PC's, I thought I would surely screw that up). It was great and had kept me happy for over a year, but I didn't realise how old Froyo was until I heard about Jellybean and 'Project Butter' and how it even outperforms old versions of Android. I've been limited in Froyo to relatively basic stuff anyway so I thought since I'd basically installed an android version only one step up from the stock Eclair, there'd be a lot of better versions out there.
This is where my nightmare begun. Since I already had xRecovery, I thought the process would be as simple as "download rom, install in xRecovery". A bit too ambitious, I ended up "soft bricking" my phone and having to fix it by going back to Eclair. Then, somehow, I could not even root the damn thing under the guidance of any tutorial. It's like it suddenly caught an immunity. After ages of meddling I managed to do so and get to the next step. Then the problem occurred that Superuser wasn't kicking in and allowing anything root access. I also had problems getting a new kernel on the phone and ended up only managing to install some random kernels I wasn't even sure supported the rom I was trying to install. I had some more problems trying to install CWM and it was around then I noticed another occurring problem. Apparently for installation of Jellybean, I needed to unlock bootloader, which apparently can't be done on devices with a certain version of motherboard. Mine is 11W41. I heard that this sometimes doesn't matter depending on the specific version, but after all the problems and reading up how hard it would be to recover from a problem if it occurred. So after a long time not finding alternate solutions, I decided to go for something lower.
Ice Cream Sandwich apparently had a similar problem, but I didn't spend long looking (by that time it was really late at night and I just wanted to at least get rid of Eclair again). Eventually I installed Gingerbread, which managed to work well... the second time I tried. The first time I mucked something up and ended up going back to Eclair yet again. Well, now I at least have the GingerXperia Revolution V3 rom installed, but I'm still wondering if this is the best I can do according to the X8. So yeah, that's the rant of my nightmarish story, but this is, ehem, a Q&A... so my question is, before I get too settled with my current phone set-up, is there any better option for my phone? Have I misunderstood some things and I actually do have a way of updating my kernel in order to install a better rom? From a rom, I obviously just want a well-packed version of android (Froyo was way to simplistic, having very few options to improve the experience), which is fast and suitable for every day use. As a bonus I would like it to be swappable so I can increase the RAM with SD memory and increase internal storage size (even with the ability to move apps to the SD, the phone fills up way too fast). I'd be very surprised if I've managed to pick the best way to upgrade my phone.
I know this heavily depends on opinion, so I just want to hear it. If there is better things I can do to it, I could do with a point in the right direction!
Click to expand...
Click to collapse
why made you think that you needed to post that bolded part?
just read....read....read...the rom threads and use the search button
CnC-ROCK said:
why made you think that you needed to post that bolded part?
just read....read....read...the rom threads and use the search button
Click to expand...
Click to collapse
Maybe I was feeling sociable and friendly and wanted to share my story? Why made you think that you needed to quote and bolden it?
And what do the threads and search functions have to do about anything? Im asking for help specific to my phone and what I've done to it, so unless you're gonna help I just dont see the logic in going into all this effort to reply to my topic. I mean really, don't bother, I'm not worth it...
@cascabel
Installed that mounts2sd but on launching it I got a message about root permissions not being granted. It's a common problem I'm noticing. Only some apps achieve root access. I think the problem might be to do with an outdated SU binary, but the topic for the ROM said not to update it after installing. I updated it beforehand but the ROM must have its own binaries or something.
Deji666 said:
Maybe I was feeling sociable and friendly and wanted to share my story? Why made you think that you needed to quote and bolden it?
And what do the threads and search functions have to do about anything? Im asking for help specific to my phone and what I've done to it, so unless you're gonna help I just dont see the logic in going into all this effort to reply to my topic. I mean really, don't bother, I'm not worth it...
@cascabel
Installed that mounts2sd but on launching it I got a message about root permissions not being granted. It's a common problem I'm noticing. Only some apps achieve root access. I think the problem might be to do with an outdated SU binary, but the topic for the ROM said not to update it after installing. I updated it beforehand but the ROM must have its own binaries or something.
Click to expand...
Click to collapse
you asked for some help...but did you search or read other people's posts before that?
that was my point...:silly:
if you're using superuser, try switching to supersu. the update the binaries. it should work then :thumbup:
btw, i'm not sure but i think swap is only for custom kernels. my bad.
cascabel said:
if you're using superuser, try switching to supersu. the update the binaries. it should work then :thumbup:
btw, i'm not sure but i think swap is only for custom kernels. my bad.
Click to expand...
Click to collapse
Yes, swap works only on custom kernel
work hard, play hard
CnC-ROCK said:
you asked for some help...but did you search or read other people's posts before that?
that was my point...:silly:
Click to expand...
Click to collapse
Yes, asking for help, not info. The help would be specific to my phone, rom, lack of bootloader unlock etc
I did manage to flash a new kernel with flashtool but only certain ones work and im not sure why.
However I installed crossbreed as suggested and it was successful, so thats nice. I'll try some more suggestions later.