Hi my gf just got a new nook color and I was planning on adding CM7 (don't plan on doing nightlies) on it.
I've been trying to read as much as I can but there's a lot of information going around..
Are there SOD issues with RC1?
Also if I flash a completely different ROM..
can anyone tell me the difference the stock experience gives as the ereader (since technically that's partially why she bought it) compared to running just the nook app as the ereader on CM7? would it be worse?
Thanks in advanced
Okay, my first reaction is that you need to read the thread about workarounds for the rooted stock nook. That gives you a good idea what is annoying.
SOD occurs but most people get it about once a day or less. PBD does occur as well, but I've never had it myself.
Personally, the issues that are put forth in the workaround section is enough that the stock ereaded rooted is more or less gimped compared to cm7 or cm7 based rom.
Sounds like you should go with CM7 from SD card and dual boot. Doesn't touch the stock experience so you can use both options and see what works best for you with no real mod to the machine.
Phatdawg said:
Okay, my first reaction is that you need to read the thread about workarounds for the rooted stock nook. That gives you a good idea what is annoying.
SOD occurs but most people get it about once a day or less. PBD does occur as well, but I've never had it myself.
Personally, the issues that are put forth in the workaround section is enough that the stock ereaded rooted is more or less gimped compared to cm7 or cm7 based rom.
Click to expand...
Click to collapse
Way to misrepresent! SOD was squashed a few weeks ago, I do not remember what biuld. PBD was also squashed thanks to fattire.
There are very few reports of ether.
Up until last night I was running N121 and 6/30 kernel with out rebooting all week. I also was able to go 3+ days without charging with moderate use.
painter_ said:
Way to misrepresent! SOD was squashed a few weeks ago, I do not remember what biuld. PBD was also squashed thanks to fattire.
There are very few reports of ether.
Up until last night I was running N121 and 6/30 kernel with out rebooting all week. I also was able to go 3+ days without charging with moderate use.
Click to expand...
Click to collapse
that's great news.
can you tell me the exact details of what you're running ?
such as CM7 build xx and what kernel?
darkamikaze said:
that's great news.
can you tell me the exact details of what you're running ?
such as CM7 build xx and what kernel?
Click to expand...
Click to collapse
darkamikaze, Read the last sentence of what you quoted in your last post and the answer will reveal its self.
painter_ said:
Way to misrepresent! SOD was squashed a few weeks ago, I do not remember what biuld. PBD was also squashed thanks to fattire.
There are very few reports of ether.
Up until last night I was running N121 and 6/30 kernel with out rebooting all week. I also was able to go 3+ days without charging with moderate use.
Click to expand...
Click to collapse
"Way to misrepresent"?
Nice.
Let's analyze your awesome post.
1) It's been squashed.
2) They are very few reports of ether.
Hence it hasn't been squashed. They both still occur. And are still issues. And for me it's a daily SOD issue.
There is no "misrepresent". If someone wants to challenge me on these things, that's fine. I've been extremely active in the forums both here and cm7 over the last 2-3 weeks (since I just bought my nook color). I am posting from recent experience.
Phatdawg said:
"Way to misrepresent"?
Nice.
Let's analyze your awesome post.
1) It's been squashed.
2) They are very few reports of ether.
Hence it hasn't been squashed. They both still occur. And are still issues. And for me it's a daily SOD issue.
There is no "misrepresent". If someone wants to challenge me on these things, that's fine. I've been extremely active in the forums both here and cm7 over the last 2-3 weeks (since I just bought my nook color). I am posting from recent experience.
Click to expand...
Click to collapse
C'mon guys, it's all good
So OP guy (too lazy to scroll up ).
Go here: http://download.cyanogenmod.com/?type=nightly&device=encore
Get the top link.
Go here: http://coachz.inetpro.org/~dalingrin/nook/kernels/
Click the latest date, then the correct kernel (if you're running off SD or eMMC)
Install both, wipe cache/dalvik, enjoy!
SOD has been fixed for me as well in the more recent stuff. PBD I used to care about, but since going back to 1.2 and then CM7 again it is down to 4%, which is fine for me
mm one of the recent nightly if i'm reading right causes some black screen issue?
That is probably the SOD, there's a post every couple days about it on the cm7 forums.
I don't see PBD posts often. Maybe once or twice over the last few weeks.
Related
So I've been read a few threads, but haven't found anything yet. Not to break "the golden rule" of CM7, but are we close/will we ever get stock-like battery life for CM7? It has greatly improved since the early days of CM7 nightlies, and I've seen mad-murdock various fixes. I also know that dalingrin is working on it, but would like to know with the new 2.2 OEM ROM coming out, what the haps is
Thanks all for the great work and great community!
We don't get stock-like battery because CM7 doesn't sleep. The current kernel (2.6.29 I think) panics when comming out of sleep, hence, 'sleep of death'. Dal says that he's solved the SOD problem in the new kernel (2.6.32) he's working on. It's just not stage ready yet.
There was talk last week about the new kernel possibly not being included in the first stable release of CM7. If I remember right, it's because they want to focus on getting a polished, bug-free, and stable version going on the current kernel (which has many backports from the new kernel, so we're not at a real big disadvantage) before completely debugging the new one.
woot1524 said:
We don't get stock-like battery because CM7 doesn't sleep. The current kernel (2.6.29 I think) panics when comming out of sleep, hence, 'sleep of death'. Dal says that he's solved the SOD problem in the new kernel (2.6.32) he's working on. It's just not stage ready yet.
There was talk last week about the new kernel possibly not being included in the first stable release of CM7. If I remember right, it's because they want to focus on getting a polished, bug-free, and stable version going on the current kernel (which has many backports from the new kernel, so we're not at a real big disadvantage) before completely debugging the new one.
Click to expand...
Click to collapse
Thanks for the complete and informative reply. I just like being in the loop
woot1524 said:
We don't get stock-like battery because CM7 doesn't sleep. The current kernel (2.6.29 I think) panics when comming out of sleep, hence, 'sleep of death'. Dal says that he's solved the SOD problem in the new kernel (2.6.32) he's working on. It's just not stage ready yet.
There was talk last week about the new kernel possibly not being included in the first stable release of CM7. If I remember right, it's because they want to focus on getting a polished, bug-free, and stable version going on the current kernel (which has many backports from the new kernel, so we're not at a real big disadvantage) before completely debugging the new one.
Click to expand...
Click to collapse
My only correction is that most of the 2.6.32 work has been done by Verygreen. I don't want to take credit for his great work.
Just want to say thanks for all the hard work, and I too am interested in this issue being fixed. It's the only thing holding me back from what looks like a great release in CM7.
Count me is as waiting for this.
For now I just shut down and reboot when I want to use it. Other then this issue, CM7 is great on the Nook.
Once SOD is solved, the nook color is going to really shine. Dalingrin, your 413a kernel is absolutely stunning. Keep up the good work devs!
dalingrin said:
My only correction is that most of the 2.6.32 work has been done by Verygreen. I don't want to take credit for his great work.
Click to expand...
Click to collapse
have you seen the issues with latest ALSA and kernel?
Seems we are all having crashes of hardware acceleration after a while of use. Only fix is a reboot
Any change to kink at this before next week?
Must say otherwise this kernel had been with smooth high performance on video and games.
From 1.1 Nook Color with 1.1 ghz overclock
Canadoc said:
have you seen the issues with latest ALSA and kernel?
Seems we are all having crashes of hardware acceleration after a while of use. Only fix is a reboot
Any change to kink at this before next week?
Must say otherwise this kernel had been with smooth high performance on video and games.
From 1.1 Nook Color with 1.1 ghz overclock
Click to expand...
Click to collapse
Dal said he was busy/away this weekend, so won't see anything til later. It is a beta test kernel, after all I flashed it but had some crashes, so I restored a backup I made right before.
That being said, I hate sounding like a whining brat (like a lot of people on here). I really am just curious with how things are (in an inquisitive manor, not a "I WANT IT NOW" one). Truth be told, the NC has come SOOOO far in the last few months, and I have been so stoked to be along for the ride.
I like to think I was the first person ON EARTH to load up Dal's kernel the day he fixed the hardware acceleration. I love the discussions on here, and (most) of the people. It is really a cool and special thing to be involved in a community like this. I know most devs may think that when I (and others?) say thank you, it's in a manor that may sound insincere, but really, you guys are awesome.
Due to all the development here, I started teaching myself Java and how to use the SDK to try and make apps that can benefit people on here in some way. I just wish I knew more about development of the actual kernel/rom. After this term I plan on dual booting to ubuntu on my x64 desktop to try and get into compiling/editing the source, but have to get through this term. CFD and incomp. fluid mechanics take up a bit of time
Really. Thank you all! You are all awesome!
/rant
Another perspective
Let me offer some perspective on this.
We used to have Motion LS800 WinXP tablet at work. It basically had standby SOD problem. Would not wake from sleep (power down, suspend to RAM). We ended up putting it in hibernation (power down, suspend to HDD) instead. Those of you who remember WinXP laptops may know what I'm talking about.
We went through updates, hotfixes, service packs, an entire upgrade to Win Vista. Nothing solved problem. Finally an upgrade to Win 7 allowed the LS800 to sleep properly. All in all, it took Microsoft 3+ years to give us a fix.
Going by that performance standard, CM7 should have Nook standby SOD issue solved sometime in the year 2014. Anything before then would be pure gravy.
EDIT: Actually, I hope I didn't offend CM7. It's not a standby "problem," it is a standby compromise, to allow development on other front.
Some PCs have sleep problems because of USB and ACPI quirks unfortunately. They are usually hardware and/or BIOS issues not related to the OS. I think MS tightened down the requirements for Windows certification since. But there are ways to get XP usually sleeping right (I've spent a lot of time on it lol).
swaaye said:
... problems because of USB and ACPI quirks ... usually hardware and/or BIOS issues ...
Click to expand...
Click to collapse
True, lab mainly rocking pre-Prescott p4 Dell-branded boxes, no reason to upgrade, but none can really sleep.
Regarding the LS800, same hardware, different OS, still counts as a software fix. How many thousands of engineers in MS Windows division? There's only three developers for CM7 Nook.
I'd say that merits cutting them some slack, not a lot, just a little, maybe expect fix by year 2015.
If you want sleep issues, try building a hackintosh! At least CM7 turns off the screen and then turns back on again. My hackintosh experiment ran great other than sleep, which left me frustrated to the point of selling off the hardware.
Anyway, I love CM7. Works great on all other fronts. While I appreciate the battery life of stock, everything else is just frustrating by comparison. I'd love to see a nice HC build someday, along with app-makers getting some tablet-compatible updates out (at least so the apps don't force quit). I'm so conflicted on what to run at this point that I dare not try any other ROMs. I don't want all my time on my NC to be in CWM.
iDidItAll4theNookie said:
If you want sleep issues, try building a hackintosh! At least CM7 turns off the screen and then turns back on again. My hackintosh experiment ran great other than sleep, which left me frustrated to the point of selling off the hardware.
Anyway, I love CM7. Works great on all other fronts. While I appreciate the battery life of stock, everything else is just frustrating by comparison. I'd love to see a nice HC build someday, along with app-makers getting some tablet-compatible updates out (at least so the apps don't force quit). I'm so conflicted on what to run at this point that I dare not try any other ROMs. I don't want all my time on my NC to be in CWM.
Click to expand...
Click to collapse
Ran a hackitosh on my eee pc 1000h. Worked fine. Now just dualbooting Win7 and Ubuntu with Burg
Hi Guys,
I've been with Android since truly day 1.
I lived with my G1 for a long time and together we endured lots of roms. Cyanogen is what most always ran on my G1. Finally, after all the bugs, slow downs and issues, I got a nexus 1 and kept it stock. It's been an amazingly unfrustrating experience and I truly fear any cooked roms.
I do however, have some gripes with stock android. One of the biggest is the lack of permissions controls in apps.
Today, I read that cyanogen is implementing permissions blocking at the app level on the nightly builds. I am VERY intrigued and want to give this a go.
http://www.androidpolice.com/2011/0...port-for-revoking-and-faking-app-permissions/
So to everyone, how stable is cyan compared to stock 2.3.4? Is it still the same old buggy, bloated, incomplete rom as it was, or have they been able to keep it light, stable and full of extra features?
Please let me and the other readers know!
Thanks!
DownloaderZ said:
Hi Guys,
I've been with Android since truly day 1.
I lived with my G1 for a long time and together we endured lots of roms. Cyanogen is what most always ran on my G1. Finally, after all the bugs, slow downs and issues, I got a nexus 1 and kept it stock. It's been an amazingly unfrustrating experience and I truly fear any cooked roms.
I do however, have some gripes with stock android. One of the biggest is the lack of permissions controls in apps.
Today, I read that cyanogen is implementing permissions blocking at the app level on the nightly builds. I am VERY intrigued and want to give this a go.
http://www.androidpolice.com/2011/0...port-for-revoking-and-faking-app-permissions/
So to everyone, how stable is cyan compared to stock 2.3.4? Is it still the same old buggy, bloated, incomplete rom as it was, or have they been able to keep it light, stable and full of extra features?
Please let me and the other readers know!
Thanks!
Click to expand...
Click to collapse
I love it right now.. before it was bloated and totally incomplete and now they got it working pretty darn good you asked at a good time! but for some users.. still causing issues. For some like myself it is perfect right now absolutely no problems I took a while to stick with GB because of all the problems with CM7 I had an htc magic which was pretty similar to the dream and I understand most the problems you probably faced. I've tried a bajillion cooked rooms myself and ever since I moved to the nexus one I just stick with a few (I tried so many on the magic it was my first android and wasted so much time -_-) I would suggest you give this one a try it still has extra features but most of which I find useful
It makes it noticeably snappier and battery life is better. 99% win (wireless LAN reception is a bit worse). I went from stock 2.3.4 to CM7 and am kicking myself for not doing it 16 months ago lol. Maybe there were issues with cooked Roms earlier but the n1 is a mature platform and I haven't noticed any major issues with cyanogen 7.03, of course YMMV
Sent from my GT-P1000 using Tapatalk
I have been running the nightlies for weeks and they have been very stable for me. I have not had any significant problems and really like using them. #85 put the permissions blocking in yesterday and I tried it with a few apps. Seems to work fine. I liked stock rom, but personally could not do without trackball wake and lots of other wonderful features in cm.
Once you go custom you wont ever go back to stock.
Make sure you understand how to flash a custom recovery and how to get to it first.
he said he had cm on his hero so he must now about custom roms..
i think it is currently very stable and good apart from the wonk issue.
CM7 Nightlies have been gold for me. Except couple bootloops. I'm on #83 now with data throttle removed. I love my Dinc
Sent from my ADR6300 using XDA App
I have been running CM7 since shortly after the official Froyo was released from Google. I had to send my phone back for the powerbutton and so I rooted it right before and tried out one of the CM6 nightlies. It was amazing. The features in every subsequent version have only built on the quality of CyanogenMod. I have been a nightly user ever since (although I only flash nightlies every week or so).
It has been extremely stable for me and I have converted a few friends (most recently a friend with the Desire HD) and they don't know how they dealt with the stock crap for so long.
So in short, give it a shot. Do a nandroid beforehand if you are worried, as then you can go right back if you don't like it.
You can only control the permissions on cm7 nightlies. That feature isn't available in the stable release I believe.
Sent from my Xoom using XDA Premium App
cyanogen 7 starting at nightly #74 has introduced some new bug fixes which greatly improve standby battery life, so that now idle current with screen off is 3-4mA. its so good now, that you can leave your phone unplugged over night for 8 hours and only lose like 3% battery. and this is WITH wifi and email accounts turned on and syncing.
this makes the nexus one like a brand new phone and turned it into a proper normal device in the sense that you can now rely on superb battery life. you know that when you arent using it and the screen is off, when you come back to it you will have the same battery percentage as when you left it.
its a no brainer to use the nightly just because of this alone.
Ever since the 2.3.4, I've been happy with the battery life and fixes with the GPS. Currently my uptime is 190+ hours without the usual sluggish response that requires a restart.
Running CM7 I found more random issues from the call quality being distorted and random reboots, to other random bugs that I need something stable.
Sent from my Nexus One
i often go 550 hours between reboots on cyanogen.
Haven't seen anything new since Hyperdroid CM7 2.1.0, which was released going on 2 months ago now, and GBX V12 before that. Just wondering if he's moved on to something else, and if we should be expecting anything new anytime soon. I don't want to give up on Hyperdroid, but if Pongster's gone, I guess it will be time to move on to something new
I guess you didn't realize he has a new baby either on the way or already here and a regular job to contend with. Pongster's build is pretty stable if you ask me. Just uses more battery than other ROMs that I have used on my phone.
slbenz said:
I guess you didn't realize he has a new baby either on the way or already here and a regular job to contend with. Pongster's build is pretty stable if you ask me. Just uses more battery than other ROMs that I have used on my phone.
Click to expand...
Click to collapse
Mine just work fine. Medium-heavy use gives me max of 15hrs.
Sent from my Calculator with Android.
low and heavy usage are different for every person. mAh are more informative and on this side the battery was worse for me than on other builds.
Hyperdroid cm7 works no problems for me. 15 - 18hrs is OK for me
Sent from my HD2 using XDA App
slbenz said:
I guess you didn't realize he has a new baby either on the way or already here and a regular job to contend with. Pongster's build is pretty stable if you ask me. Just uses more battery than other ROMs that I have used on my phone.
Click to expand...
Click to collapse
No, I didnt realize that, and after searching through his ROM forums, didnt see anything about it and gave up searching. His ROM is more than stable though and I love it. I get up to 18 hr's a day of battery on normal usage, with a couple tweaks too though. Its the only ROM I've been using since I first tried his GBX V2.0, but if he's taking time off to handle personal stuff then I'm gonna go flash crazy trying other ROM's now. Just wondering if we could expect anything new from him is all. Thanks for the info though.
Dorimanx High End
Switch to Dorimanx High End Rom, best Rom imo, has best support by far, smooth, fast, and updated constantly.
Sully6789 said:
No, I didnt realize that, and after searching through his ROM forums, didnt see anything about it and gave up searching. His ROM is more than stable though and I love it. I get up to 18 hr's a day of battery on normal usage, with a couple tweaks too though. Its the only ROM I've been using since I first tried his GBX V2.0, but if he's taking time off to handle personal stuff then I'm gonna go flash crazy trying other ROM's now. Just wondering if we could expect anything new from him is all. Thanks for the info though.
Click to expand...
Click to collapse
No problem. Like you because there hasn't been a recent update, I have been trying other ROMs. So far, Tytung's Nexus HD2 v2.8 build the last couple of weeks has been very stable for me, similar to Pongsters but with even less battery drain. 3% battery loss vs. 5% battery loss on overnight standby. Also, actual app use, Tytung's build on my phone is about on average 50mA less than Pongsters. Though I do somewhat miss the CM configurations possible on Pongster's build. Both are great builds, but it again boils down to what you want on your phone. For me, solid GPS and Bluetooth are what I need and that is what Tytung brings to me. But Pongster's build is slightly more responsive and more configurable. Good luck flashing other ROMs. Let us know what you find out.
Right now I'm using D4RK MIUI V 4.0.1 by Zx The Ripper xZ. I hadn't tried a MIUI ROM before but I gotta say, I'm very impressed. I love the customization it offers, along the with overall look and feel. I had to go with ADW Launcher though, just because that's what I'm used to with HyperDroid. I get a full days worth of battery after calibration, and the integrated AGPS libs is a plus too. Tytung really knocked it outta the park with that one, and put our HD2's one step closer to becoming an almost full fledged native device. I'm gonna use it for a few days, and then I think I'll try Dorimanx High End Rom, and probably Tytung's Nexus HD2 after that, just because I know Tytung's stuff is always top notch. Theres so many choices, I'm just gonna have fun with it, and maybe try em all Thanks guys.
i read on a rom thread that the high battery drain for cm7 roms is related to the lockscreen and email.apk. if you delete email.apk and chose another lockscreen than default the battery drain should be gone. but i didn't try cause i'm on miui.
think this was written in the dorimax rom thread.
I have used CM7 and TW quite a bit in my day. What I've noticed is that while CM7 is very snappy TW is not that bad on its own. Why would I prefer 2.2 then? Simply put CM7 is a beta. Nothing more nothing less.
At first the data going out and phantom button presses (the LED buttons act like they've been physically pressed by you) weren't a big deal. But after some time it became a huge hassle pulling the battery often so that I could sync data. When the phantom button presses went berserk it was impossible to use the phone. GPS has always been a sore spot on the Fascinate. On TW it doesn't always lock immediately but does within a minute. On CM7 it would typically take 15+ min if it ever did lock. Battery life is not that great on the AOSP hack. Uptime is 6h11m at 87% battery using UKB v2.1 (ED01 2.2 Froyo).
CM7 is awesome despite these shortcomings. It's awesome that jt is making this for our phones. I am merely writing something that I wish I would've been able to read when I first tried CyanogenMod for the Fascinate. I have a Motorola Droid with CM7. It's really nice and I believe this to be b/c it's been on there much longer than the Fascinate. I hope in time CM7 becomes stable enough for every day use.
cool story bro
Title should be 2.2>CM7, at the moment anyway.
AuroEdge said:
I have used CM7 and TW quite a bit in my day. What I've noticed is that while CM7 is very snappy TW is not that bad on its own. Why would I prefer 2.2 then? Simply put CM7 is a beta. Nothing more nothing less.
At first the data going out and phantom button presses (the LED buttons act like they've been physically pressed by you) weren't a big deal. But after some time it became a huge hassle pulling the battery often so that I could sync data. When the phantom button presses went berserk it was impossible to use the phone. GPS has always been a sore spot on the Fascinate. On TW it doesn't always lock immediately but does within a minute. On CM7 it would typically take 15+ min if it ever did lock. Battery life is not that great on the AOSP hack. Uptime is 6h11m at 87% battery using UKB v2.1 (ED01 2.2 Froyo).
CM7 is awesome despite these shortcomings. It's awesome that jt is making this for our phones. I am merely writing something that I wish I would've been able to read when I first tried CyanogenMod for the Fascinate. I have a Motorola Droid with CM7. It's really nice and I believe this to be b/c it's been on there much longer than the Fascinate. I hope in time CM7 becomes stable enough for every day use.
Click to expand...
Click to collapse
/me slaps AuroEdge for this Blasphemy
Hey! Remember 2.1? lolololololol
Skrazz said:
Hey! Remember 2.1? lolololololol
Click to expand...
Click to collapse
yea, I suppose that pretty soon people are gonna start saying that 2.1 was better than the AOSP GB roms we have now as well. Douchebags
I actually get better GPS on the AOSP roms. I've moved back to TW until I'm sure the SD card issues are resolved, but AOSP was much better for me other than that.
I think the take away here is that no single solution works best for every person or phone.
kidserious said:
yea, I suppose that pretty soon people are gonna start saying that 2.1 was better than the AOSP GB roms we have now as well. Douchebags
Click to expand...
Click to collapse
That's quite a leap.
I picked 2.2 > 2.3 instead of 2.2 > CM7 because both have/had a way of messing up sd cards.
Im sorry but the latest MIUI Fascinatemtd rom is pretty much the greatest experience I have ever had on a phone and it is GB based. I haven't had one problem with it yet(fingers crossed).
AuroEdge said:
I picked 2.2 > 2.3 instead of 2.2 > CM7 because both have/had a way of messing up sd cards.
Click to expand...
Click to collapse
2.2 on the fascinate was an epic FAIL. We waited FOREVER for froyo source to drop and when it did, it was so crappy that it fixed/improved NOTHING on AOSP. If it wasn't for fascinatemtd, I wouldn't even have a fascinate still. Thank you jt1134. Oh, and FYI, the SD card issue has been resolved for about a week now. /me still slaps AuroEdge for saying TW is better than mtd.
Sent from my SCH-I905 using Tapatalk
If/when official GB comes out for our phone, it could quite possibly help jt1134 fix the remaining issues with CM7, as some of it are just slight changes in the kernel that need fixed to make things work, but what is available for Froyo doesn't help, nor does what is currently available for GB. Will everything be magically fixed with GB? Probably not, but it could help fix the minor issues that are still there.
kidserious said:
2.2 on the fascinate was an epic FAIL. We waited FOREVER for froyo source to drop and when it did, it was so crappy that it fixed/improved NOTHING on AOSP. If it wasn't for fascinatemtd, I wouldn't even have a fascinate still. Thank you jt1134. Oh, and FYI, the SD card issue has been resolved for about a week now. /me still slaps AuroEdge for saying TW is better than mtd.
Sent from my SCH-I905 using Tapatalk
Click to expand...
Click to collapse
I'd be back on VGB in a heartbeat if anyone could verify that the SD card issues are fixed. I've seen it claimed a couple places, but never with any justification presented. There's a report just up on RW of an SD failure on the latest version. Of course the report may be attributable to user error, but I'd feel better about it if someone could actually point to the fix rather than just claim everything is ok.
I've been excited for what possibilities lie in wait for CM7. Especially if this new v2.3 leak is real and useful. I really like CM7.
drnihili said:
I'd be back on VGB in a heartbeat if anyone could verify that the SD card issues are fixed. I've seen it claimed a couple places, but never with any justification presented. There's a report just up on RW of an SD failure on the latest version. Of course the report may be attributable to user error, but I'd feel better about it if someone could actually point to the fix rather than just claim everything is ok.
Click to expand...
Click to collapse
There were two changes that Jt made to his kernel a couple of weeks ago that were causing the SD card issues. Jt identified these particular changes and has IN FACT reverted both of these commits. The kernel is now safe and so is your SD card. I've been on vgb/pool party for about two weeks straight now, no SD card issues.
Sent from my SCH-I500 using Tapatalk
kidserious said:
There were two changes that Jt made to his kernel a couple of weeks ago that were causing the SD card issues. Jt identified these particular changes and has IN FACT reverted both of these commits. The kernel is now safe and so is your SD card. I've been on vgb/pool party for about two weeks straight now, no SD card issues.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
Hmm, I've been trying to keep up with his RW thread, but must have missed that post. I saw some mention of kernel changes in the CM7 thread, but nothing specific to the SD card issue. Not saying you're wrong, just pointing out why I'm concerned.
What do you make of the reported SD failure to mount in CWM on the newest VGB?
If you want to be 100% safe, just use glitch. It uses the froyo bootloader and is not a part of any of the issues to do with SD cards.
the vanilla kernel from JT is for pure speed but glitch gives some awesome things for tweaking performance like voodoo and undervolting/overclocking.
sageDieu said:
If you want to be 100% safe, just use glitch. It uses the froyo bootloader and is not a part of any of the issues to do with SD cards.
the vanilla kernel from JT is for pure speed but glitch gives some awesome things for tweaking performance like voodoo and undervolting/overclocking.
Click to expand...
Click to collapse
There have been SD failures using glitch. I love the kernel, but it isn't a cure in itself.
drnihili said:
There have been SD failures using glitch. I love the kernel, but it isn't a cure in itself.
Click to expand...
Click to collapse
then they would be due to user error or some other unrelated thing.
Sent from my MIUI SCH-i500
sageDieu said:
then they would be due to user error or some other unrelated thing.
Sent from my MIUI SCH-i500
Click to expand...
Click to collapse
That's an interesting hypothesis, on what do you base it?
Which ROM do you feel works the best for your Vibrant? Of course this is a matter of opinion, which is exactly what I want to hear. I'm running CM 10.1.3 right now and enjoying it. At times it can feel a little bit sluggish but I don't know if it's the ROM or my phone. I'd also be interested in hearing about your experiences with battery life in each ROM. I've been thinking of trying CyanAOSP because it's less cluttered and I have a hunch it would be more snappy.
Hopefully I'm not breaking any rules, I just wanted a really recent thread comparing the strengths and weaknesses of all the recent Jellybean ROMs. This isn't a question thread, it's more of an opinion thread.
I'm using CM10.2 build date - 10/15 for a day now. Have no problems. Everything works fine, including GPS after ds. Battery drain is normal.
selmandeli said:
I'm using CM10.2 build date - 10/15 for a day now. Have no problems. Everything works fine, including GPS after ds. Battery drain is normal.
Click to expand...
Click to collapse
What's DS? Also, have you tried 10.1.3?
oneupe1even said:
What's DS? Also, have you tried 10.1.3?
Click to expand...
Click to collapse
DS is DeepSleep. Its a state in which the phone uses minimal battery and thus the battery is saved.
oneupe1even said:
What's DS? Also, have you tried 10.1.3?
Click to expand...
Click to collapse
If you mean the official CM 10.1.3, yes I tried it. It is stable and smooth. You can use it as a daily driver.
selmandeli said:
I'm using CM10.2 build date - 10/15 for a day now. Have no problems. Everything works fine, including GPS after ds. Battery drain is normal.
Click to expand...
Click to collapse
I just saw that you were using CyanAOSP. How would you compare it to CM 10.1.3 and 10.2?
Also, do you know where I can get the 1.75 ROM? I've heard the 2.0 has problems.
been running cyanaosp 2.0 since its release and its been fine beside a few random reboots, but im sure it was cause i had my device oc'd to high. this rom is perfect for me as i play alot of games.
Hi all,
New member of the forums, but I've been reading as much as I can about my Vibrant (Fascinate?) and I'm still kind of confused as to which model my phone really is. It's a Telus model sgh-t959d, but after flashing CyanAOSP 3.0.0 for the i9000, my phone info shows model GT-i9000. I understand there are similarities between these devices, but I was a little nervous about bricking my phone by flashing the wrong ROM. Well, it was a painless process that took less than 2 minutes! I upgraded from PassionICS, which was a good ROM, but kind of laggy. After a day of use, I can say CyanAOSP is much quicker, more refined and more fun to use. The customizations offered by Nova launcher are quite extensive and make it feel like a new phone. I highly recommend this ROM! Many thanks to the hard working devs!
Anybody have kernel recommendations to get more battery life out of CM 10.1 or 2?
CM
Im using CM 10.1.3 stable, think this is a best and stable ROM
I was using one of the CM 10.2 nightlies (10/25 specifically) for about a week before giving up on some serious battery drain and background android OS data usage issues... First time I ever exceeded my 5gig threshold pushing me down to slower speeds. Also USB data transfer simply stopped working after about a week... couldn't even mount via recovery.
Ultimately had to get new ROM files into my phone via the microSD/USB adapter and internally transferring to the internal directory.
That said, CM 10.2 itself is a very pleasant experience if you can avoid such issues - In hindsight I'd strongly suggest giving it a try but with a build that's known to be stable and without any such major issues if you intend to use it as a daily driver (the 10/15 build has been recommended more than once in my forum trawling). Lesson learned!
I made the switch last Saturday (6 days ago) to SlimBean Build 2 however, which is also based on 4.3.1. By comparison to my last experience, this has zero issues falling back to deep sleep, even after loading it down with all my favorite apps and sync settings. I've had one random reset to recovery in the middle of a phone call, and gps performance has been hit or miss so far, but otherwise there's a lot to like! Battery is back to respectable charging intervals and background data is in check. ROM itself is very zippy. Lock screen by comparison to CM 10.2 seems slightly sluggish to respond. I'll likely be sticking with this for a while.