Related
I'm not new to flashing custom roms in the WinMo world but, I just got my Hero like 3 days ago. I have searched and read about everything here so far and from what I have read the reason for flashing custom roms is SPEED and CUSTOMIZATION.
Well, I have flashed twice and ended up re-rooting and going back stock. I'm not trying to take anything away from the developers because I know it's hard work. I did it with my old TP with WinMo for a couple of years. When I flashed my custom WinMo roms they where ALWAYS faster than any stock rom.
HOWEVER it seems to me like none of these roms for the Hero are ready for prime time yet and from what I'm reading all of the decent developers have crossed over to the Evo so the chance of us getting some decent roms in minimal at best.
So my question is should I just wait till something is released that is more stable or should I cross over as well? AGAIN I'm not trying to take anything at all away from the developers. I expected some differences coming from WinMo. I just wanted to know if anyone else felt the same way. If not, what rom are you running? Is it faster than the stock .6 rom from sprint? Does the camera work?
What ROMs did you try? I've used DamageControl and am now on Darchdroid and have had no issues on either. Both run way faster and have way better battery life than stock. Everything works. There are tons of members here that would say the same thing...
What ROMs have you tried? Any ROM with an overclocked kernel will be faster than stock. All current ROMs also have working camera.
Are you waiting until everything finishes syncing? The first 20 minutes of your ROM experience will be a little slow as it pulls down whatever info you plugged in for Google/Facebook/Twitter/etc., but once that's done your custom ROM will be smooth sailing. I've used Fresh 2.0d, 2.1.2, PureHero, and now DarchDroid 2.7 and they've all been substantially faster than stock. Especially with OC and JIT, there's a tangible difference.
I'd trying something again and let everything sync up. I've been impressed by DarchDroid, but I'm also an AOSP fan.
What roms have you tried?
I use Buufed 2.0b and it is very fast. I used FreshToast 2.1, which was also fast until I jacked with the settings. Others are also fast as well.
If you are describing the first boot after flashing a rom, that may be because dalvik-cache needs to be built...this take a few minutes to do, but it is a one-time thing (unless you move to another rom or wipe your dalvik-cache).
abadasstanker69 said:
I'm not new to flashing custom roms in the WinMo world but, I just got my Hero like 3 days ago. I have searched and read about everything here so far and from what I have read the reason for flashing custom roms is SPEED and CUSTOMIZATION.
Well, I have flashed twice and ended up re-rooting and going back stock. I'm not trying to take anything away from the developers because I know it's hard work. I did it with my old TP with WinMo for a couple of years. When I flashed my custom WinMo roms they where ALWAYS faster than any stock rom.
HOWEVER it seems to me like none of these roms for the Hero are ready for prime time yet and from what I'm reading all of the decent developers have crossed over to the Evo so the chance of us getting some decent roms in minimal at best.
So my question is should I just wait till something is released that is more stable or should I cross over as well? AGAIN I'm not trying to take anything at all away from the developers. I expected some differences coming from WinMo. I just wanted to know if anyone else felt the same way. If not, what rom are you running? Is it faster than the stock .6 rom from sprint? Does the camera work?
Click to expand...
Click to collapse
Its not like the developers left along time ago. All of them pushed out a final release before they left, and it was only 2 devs.
Also, they all run smoother then stock. Have you tried damagecontrol? Or try ANY of the overclocked roms. You can get OC on any rom now with separate flashable kernels.
Darchdroid is also the most basic rom you can use, but not basic in the area of customization. Its the only rom not built on htc framework, so there is close to zero bloat and it runs extremely smooth.
abadasstanker69 said:
I'm not new to flashing custom roms in the WinMo world but, I just got my Hero like 3 days ago. I have searched and read about everything here so far and from what I have read the reason for flashing custom roms is SPEED and CUSTOMIZATION.
Well, I have flashed twice and ended up re-rooting and going back stock. I'm not trying to take anything away from the developers because I know it's hard work. I did it with my old TP with WinMo for a couple of years. When I flashed my custom WinMo roms they where ALWAYS faster than any stock rom.
HOWEVER it seems to me like none of these roms for the Hero are ready for prime time yet and from what I'm reading all of the decent developers have crossed over to the Evo so the chance of us getting some decent roms in minimal at best.
So my question is should I just wait till something is released that is more stable or should I cross over as well? AGAIN I'm not trying to take anything at all away from the developers. I expected some differences coming from WinMo. I just wanted to know if anyone else felt the same way. If not, what rom are you running? Is it faster than the stock .6 rom from sprint? Does the camera work?
Click to expand...
Click to collapse
I am running Darchdroid and recommend you do too. It is faster than the most fastidious fast rom.
I don't wanna put anyone out there and I can't really remember the specific ones I tried but one that stood out was here
forum.xda-developers.com/showthread.php?t=683746
Everyone kept saying great things about a "fresh" rom so I figured that was it. When I used it the thing ran slow, my camera didn't work, and my picture messages wouldn't come in.
I was going to use another one but, I just thought it was a relatively new phone so maybe there wasn't sufficient work done yet
thatjerk said:
I am running Darchdroid and recommend you do too. It is faster than the most fastidious fast rom.
Click to expand...
Click to collapse
Yeah, I am going to agree. As far as overall speed, Darchdroid is the best. I'm also partial to Launcherpro over the included ADWLauncher. I have 7 homescreens full of stuff and it still runs fine.
Which version of Fresh did you use? I've had some issues with the earlier 2.x versions, but it's been pretty stable since 2.0d.
EDIT: FreshToast...I've ran that one for the longest time. The only time it would go slow on me is when I jacked with the settings in SetCPU.
abadasstanker69 said:
I don't wanna put anyone out there and I can't really remember the specific ones I tried but one that stood out was here
forum.xda-developers.com/showthread.php?t=683746
Everyone kept saying great things about a "fresh" rom so I figured that was it. When I used it the thing ran slow, my camera didn't work, and my picture messages wouldn't come in.
I was going to use another one but, I just thought it was a relatively new phone so maybe there wasn't sufficient work done yet
Click to expand...
Click to collapse
Check out how fast this is..
http://www.youtube.com/watch?v=oHg5SJYRHA0&sns=em
wow such fast responses! lol
Sorry if I stepped on any toes but, I just tried a couple and got results that where no where near the instantaneous difference you got in the WinMo world. Maybe I should have stuck with it for a while longer....
I did have a little info up on Facebook but I REFUSE to twitter!! LMAO The contacts I have are numerous so maybe that's a contributing factor. I'm not sure. I really wanted a Froyo rom but, from what I understand, it's still in Beta.
I really just want something fast and reliable. I often use my bluetooth for HOURS on end so something less harsh on the battery would also be extremely helpful.
I will try whatever suggestions you guys have. I know you have been in the Android world way longer than me. I had XDAndroid on my TP but this is a dramatic difference.
thatjerk said:
Check out how fast this is..
http://www.youtube.com/watch?v=oHg5SJYRHA0&sns=em
Click to expand...
Click to collapse
LMAO I got RickRoll'D
abadasstanker69 said:
I don't wanna put anyone out there and I can't really remember the specific ones I tried but one that stood out was here
forum.xda-developers.com/showthread.php?t=683746
Everyone kept saying great things about a "fresh" rom so I figured that was it. When I used it the thing ran slow, my camera didn't work, and my picture messages wouldn't come in.
I was going to use another one but, I just thought it was a relatively new phone so maybe there wasn't sufficient work done yet
Click to expand...
Click to collapse
Camera works in that ROM. If you had another experience, something was done wrong.
thatjerk said:
Check out how fast this is..
http://www.youtube.com/watch?v=oHg5SJYRHA0&sns=em
Click to expand...
Click to collapse
Well played, sir. If you want to watch a real benchmark of Freshtoast: http://www.youtube.com/watch?v=byhykf6D6m4
illogic6 said:
Camera works in that ROM. If you had another experience, something was done wrong.
Click to expand...
Click to collapse
I don't see how I could have "done it wrong" I mean it's pretty self explanatory. I opened the camera app and got a broken TV set in purple and blue on my screen. Everything else worked....just slowly. Maybe a bad download.....maybe. I don't know. But how could someone possibly flash wrong and still get it to run? That makes no sense.
abadasstanker69 said:
I don't see how I could have "done it wrong" I mean it's pretty self explanatory. I opened the camera app and got a broken TV set in purple and blue on my screen. Everything else worked....just slowly. Maybe a bad download.....maybe. I don't know. But how could someone possibly flash wrong and still get it to run? That makes no sense.
Click to expand...
Click to collapse
You need to make sure you wipe in recovery before flashing a new ROM. It sounds like that could possibly be the issue.
illogic6 said:
You need to make sure you wipe in recovery before flashing a new ROM. It sounds like that could possibly be the issue.
Click to expand...
Click to collapse
I never read anything about that! lol wow I feel like such a noob. Do i do that from the menu that pops up when restarting? The one I update the custom rom from?
illogic6 said:
Well played, sir. If you want to watch a real benchmark of Freshtoast: http://www.youtube.com/watch?v=byhykf6D6m4
Click to expand...
Click to collapse
that's just sexy
abadasstanker69 said:
I never read anything about that! lol wow I feel like such a noob. Do i do that from the menu that pops up when restarting? The one I update the custom rom from?
Click to expand...
Click to collapse
Yes. Wipe data, dalvik-cache, and sd-ext if you have one.
Flash the custom ROM. When it loads sign into your gmail and give it 5ish minutes to synch your calendar/contacts/mail from the cloud. Once that is completed, you'll want to head to the market and grab "overclock widget" and make sure you're clocked to appropriate speeds.
From then on, the speed improvement should be obvious.
Ok, I successfully rooted and installed other apps on my NC tonight. Thanks for the great directions! This really makes it a great option at $249 over something like the Galaxy Tab. It still of course has all the remnants of Barnes & Noble everywhere. What are the chances that we will eventually get a custom ROM or perhaps Cyanogenmod so we can truly have a generic Android tablet? I just don't know how much something like that would entail and wonder if anyone can provide a little more info.
Thanks!
I think we'll see some custom goodies, but with everything so early on, I expect it'll take a few weeks before we see the big stuff.
I'm willing to be patient, I'm rooted, and don't mind where I am now, considering the NC hasn't even been on shelves for 3 weeks yet.
graymulligan said:
I think we'll see some custom goodies, but with everything so early on, I expect it'll take a few weeks before we see the big stuff.
I'm willing to be patient, I'm rooted, and don't mind where I am now, considering the NC hasn't even been on shelves for 3 weeks yet.
Click to expand...
Click to collapse
lol not even 2 weeks..it came out the 19th
Oh I know it will take some time. It's pretty good like it is after rooting. I just wanted to know more about how feasible it is. Could there potentially be huge roadblocks?
nlowhor said:
Oh I know it will take some time. It's pretty good like it is after rooting. I just wanted to know more about how feasible it is. Could there potentially be huge roadblocks?
Click to expand...
Click to collapse
The only roadblock I can potentially forsee is B&N holding out on releasing the source for the NC.
I think it's hard to say without someone actually working on it. Also, we don't have many options for a factory reset now, so development can be kind of risky.
ZeroSX said:
The only roadblock I can potentially forsee is B&N holding out on releasing the source for the NC.
Click to expand...
Click to collapse
yes, because the drivers and kernel are needed
bg
The drivers are out there, and look to be the same ones in use by other Cyanogen targets (the TI WAN chip is in the AOSP tree already, the PowerVR SGX chip is pretty common).
In fact the nook color looks a lot like a motorola droid, from a HW point of view, IIRC.
Thanks for the info. This all sounds like good news. Really looking forward to CM or some other AOSP-style ROM.
B&N has released the source and the developers kit. Start hacking!
...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'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
For a long while now an on many different roms I have noticed my phone rebooting at what appears to be random atleast twice a week.
It's never been when in a call and I often only notice it because I see the boot animation on my phone out of the corner of my eye while it was doing nothing but being sat on my desk! Also I know when it has done it because it has switched back to my default network which I am not normally on.
For me I have had it on everything from CM7 to Juwes to docs rom to stock. If this is not normal behaviour I fear that my phone may have a hardware fault
Post your random reboot experiences here!
My experience: rarely with Darky 10.1, I got one today with Juwe 5.1 but I installed this rom two days ago and still making some experiment.
Bye.
always close to stock cfroot only + own changes = never had issues ...
Both my husband and I get them at least twice a week also, we are on stock JVH that we got from O2 through Kies, not rooted or anything. we are thinking of phoning samsung tomorrow, we never had any of these on 2.2, so I think it must be software with us both getting them since 2.3. both our phones are still in guarantee, although if it is software I dont know what they can do
TBH I haven't actually been on a pure stock rom for quite some time. From what I remember I would get the occasional random reboot but probably not quite as often as I have done since turning to custom roms.
Could some fundamental change that many custom roms make cause this?
Or could perhaps a certain rogue app which I have had installed on many different roms be causing this?
kezgez said:
Both my husband and I get them at least twice a week also, we are on stock JVH that we got from O2 through Kies, not rooted or anything. we are thinking of phoning samsung tomorrow, we never had any of these on 2.2, so I think it must be software with us both getting them since 2.3. both our phones are still in guarantee, although if it is software I dont know what they can do
Click to expand...
Click to collapse
Yes this is partly why I decided to create this thread and try to get to the bottom of it. My warranty runs out in 2/3 months and the paranoid side of me fears a hardware issue. I also started on 2.2 and don't think I got quite as many, if any, random reboots then which seems to coincide with your experiences.
Deck6rd said:
Yes this is partly why I decided to create this thread and try to get to the bottom of it. My warranty runs out in 2/3 months and the paranoid side of me fears a hardware issue. I also started on 2.2 and don't think I got quite as many, if any, random reboots then which seems to coincide with your experiences.
Click to expand...
Click to collapse
Yeah our guarantee runs out in about 6 or 7 weeks which is why I thought of phoning them, my phone has been back once because the motherboard or whatever its called had to be replaced. do you think it could be hardware?
kezgez said:
Yeah our guarantee runs out in about 6 or 7 weeks which is why I thought of phoning them, my phone has been back once because the motherboard or whatever its called had to be replaced. do you think it could be hardware?
Click to expand...
Click to collapse
I have no idea. I'm starting to think probably not. so far 75% of people to this poll have reboots either daily or weekly. I think it could be a software bug in all gingerbread based roms but i really don't no. Would be interesting to flash back to stock froyo and see if it persists then.
Keep an eye on this thread and hopefully we can get to the bottom of this
kezgez said:
Both my husband and I get them at least twice a week also, we are on stock JVH that we got from O2 through Kies, not rooted or anything. we are thinking of phoning samsung tomorrow, we never had any of these on 2.2, so I think it must be software with us both getting them since 2.3. both our phones are still in guarantee, although if it is software I dont know what they can do
Click to expand...
Click to collapse
Ideal time to flash a custom rom with root. Follow the white rabbit.........
blockbuster 2.4
Are those who never get any random reboots mostly on stock roms? if so which roms?
mhm...............
Deck6rd said:
so far 75% of people to this poll have reboots either daily or weekly. I think it could be a software bug in all gingerbread based roms but i really don't no
Click to expand...
Click to collapse
question/thread title is "Does your phone suffer from random reboots?" so majorityof people that does not have any reboots/problems will not join to read so they will not vote
also by the thread title in some way youre determining the anserw yet still youve got 15 people voted (thats not authoritative + 350 thread openings...) & 33% of them said NEVER
I used to get random reboots on stock firmware, because samsung can't write software! Since running cm7 based software (insanity cm) I haven't had one single reboot, the stability is mindblowing and it is super stable, however it is not really for flashing novices, just my humble opinion
Sent from my GT-I9000 using XDA Premium App
I'm with 2.3.4 JVP, and usually after an uptime of around 333 hours the phone reboots itself, happened twice...
$omator said:
question/thread title is "Does your phone suffer from random reboots?" so majorityof people that does not have any reboots/problems will not join to read so they will not vote
also by the thread title in some way youre determining the anserw yet still youve got 15 people voted (thats not authoritative + 350 thread openings...) & 33% of them said NEVER
Click to expand...
Click to collapse
Yes I do admit I haven't received the amount of feedback I was hoping for in this thread. And yes I am fully aware that polling on here is far from an accurate way of gathering data exactly for the reason you suggested but still I hoped to learn something about the extent of this phenomenon.
Also when I wrote that quote that you critisied for being inaccurate it was correct at the time. If not a little premature
However please feel free to share your experiences (or lack of) the topic in question.
I voted 'very rarely' - usually when running a buggy app that uses all RAM and CPU.
No reboots by itself so far.
to much, using dark core 2.6 , pilotx rom
Wow I thought I am the only who suffer with this..LOL...My phone is running JVO 2.3.3 and I updated it via Kies...no root no lagfix, quite a virgin Galaxy S..hahaah...
Very rarely, and it was only after this one time I had to swap batteries and didn't allow the phone to fully shutdown which must've caused some corruption. Even though I restored a backup certain things just seemed off and turned out I did had problems with reboots and so after that, most likely being the cause.
Besides that, after putting in a fresh ROM and whatnot, never had issues, not before the incident save once maybe.
I have changed to juwe 5.1 today from his 5.0. Was playing angry birds and left phone down for minute, then soon as screen locked it rebooted itself. Have not tried with other apps yet. Will post back when tried them out