Related
I flashed Trigger 3.0 when it first came out, I was so happy with the rom that I took a abreak from flashing different roms. A week ago I started to get some force closes and they became a bit more frequent. Over the past couple of days I have been looking for a new rom to run. I started with Explodingboy's Simply Honey 3.6, then tried Simply Honey v1.0XE and Heathen's Private stock 2.0. Each time I flashed a rom I came started by odin-ing to JDF first.
With all of the roms I got the same problem, which leads me to thing it's hardware based rather than the roms. I would flash the rom, the rom would work fine for a few hrs then the phone would freeze while asleep. The only way to wake the phone was to do a battery pull. This sleep freeze would happen 30-40% of the time the phone would go to sleep.
I'm going to try to flash a 2.2 rom and see if my phone does any better, the others were 2.3.3 or 2.2.1
What kernel are you running?
Hardware takes quite a bit of abuse to deteriorate. In fact, most "hardware parts" will just simply die, not slowly deteriorate.
Sdobron said:
What kernel are you running?
Click to expand...
Click to collapse
With Trigger 3.0 I was running overstock OC/OV, with no problems for many weeks.
Once I started looking for a new rom, a few days ago, I always used the default kernel.
Do you mean ODIN to JDK?
Thats the stock base for Vibrant.
Side note: I have been unable to use my screen while device is plugged in, to dosent make the right touches and bounces around the screen...I was thinking I needed to ODIN to JDK, so I did... nothing changed, now I'm thinking I might need to get a new phone... #FYI
Thats actually pretty interesting. For awhile I had the same problem it just wasn't as frequent as yours. I'm using the Overstock kernel which I think it was what mine was related to. I had my sleep profile in setCPU set really low, I bumped it up and havn't had any problems since.
studiozeroseven said:
Do you mean ODIN to JDK?
Thats the stock base for Vibrant.
Side note: I have been unable to use my screen while device is plugged in, to dosent make the right touches and bounces around the screen...I was thinking I needed to ODIN to JDK, so I did... nothing changed, now I'm thinking I might need to get a new phone... #FYI
Click to expand...
Click to collapse
Actually the phone ships with JFD, so your wrong haha. xD
Longcat14 said:
Actually the phone ships with JFD, so your wrong haha. xD
Click to expand...
Click to collapse
Java Development Kit
To the OP, maybe you've restored some corrupt titanium data. Only restore apps and no system data after a fresh flash and see what happens.
How about u coding to stock and leave it alone see if u have same problem if not then its not hardware related
Sent from my SGH-T959 using XDA Premium App
hotadef said:
How about u coding to stock and leave it alone see if u have same problem if not then its not hardware related
Sent from my SGH-T959 using XDA Premium App
Click to expand...
Click to collapse
I second this. Go back to stock, and see what happens. Also, do NOT restore any backups at all, leave everything clean.
Also you can try and use System Panel, and see wich apps are running in the background, and then Titanium Backup to freeze app by app (not system apps of course) and see if any of these are causing you the FCs.
Hey all thanks for all the responses. I was reading them all yesterday but did not want to reply and jinx my trigger 3.2 flash. I've now been running trigger 3.2 for close to a day and no FCs.
I can say I did anything different with this flash to make it more stable. I went back to JFD via odin and use Ti to restore user apps and system apps (ONLY: wifi, bluetooth, user dictionary, and MMS)
thanks again for everyones help.
Glad to hear it is worked out.
My wife and I had Motorola XT720s and her USB borked out the other day. Our carrier replaced hers with a Vibrant and sent her on her way. Needless to say, she liked the XT720 and wants me to take the Vibrant. Since we have been on the most unholy of manufacturers (locked bootloader and no updates-yep was sold and bought on 2.1 [eclair kernal] over a year ago) I have been maintaining both our phones. We have successfully upgraded our phones to 2.2, miui, CM6/7 all with the locked bootloader and a little erseverance and a lot of adb learning.
My question is what can I do with the Vibrant and what are the better ROMs that you have? I am not affraid to get into the guts of the phone and work from that way. She just got it yesterday and when I got home, she pitched the switch to me, so this weekend, I'll root it, back up and then checkout the forums to see what is what.
Good ROMs/ Kernals (stability v experimental)?
Overclocking?
How to unlock the bootloader? I kow how on Nexus S but that is not this obviously.
Known issues with the phone in general, either software or hardware (i.e power button breaks after 2 mos. Stuff like that)
I already looked at the sticky nOOb guide for rooting. Is that update.zip the best way. Or should I use z4 or Superoneclick? I used Universal Androot before but that doesn't support Froyo kernals.
Basically, what do you like and and your opinions. The decision will be mine but I like to be informed. And I actually do like to read the threads, but we just got this yesterday and wanted to put out the feelers.
Thanks to all for your help and I look forward to the responses.
first, if your hardware locked, youre gonna havr to find the thread on how to unlock... do this FIRST.
We have several roms, they range from stable to fast and unstable
Imo, that would be froyo like bionix to cm7 respectively.. cm7 flys but its batt sucks and gps is practicallu nonexistant (not that good iin froyo tho)
There is oc up to like 1.7ghz tho my phone doesnt do more than 1.6 stable...
Also, never use kies under any circumstance and learn to use odin Well.
Thats my advice... welcome
Sent from a cell tower to the XDA server to you.
younix258 said:
first, if your hardware locked, youre gonna havr to find the thread on how to unlock... do this FIRST.
We have several roms, they range from stable to fast and unstable
Imo, that would be froyo like bionix to cm7 respectively.. cm7 flys but its batt sucks and gps is practicallu nonexistant (not that good iin froyo tho)
There is oc up to like 1.7ghz tho my phone doesnt do more than 1.6 stable...
Also, never use kies under any circumstance and learn to use odin Well.
Thats my advice... welcome
Sent from a cell tower to the XDA server to you.
Click to expand...
Click to collapse
That's great. Just the sort of thing I am looking for.
Couple of questions.
As far as OC. Is that an app or is it through a differnt kernal. I know that some kernals oc and undervolt or stock cpu and undervolt. There is an app in the market that was for Motorola that was called Milestone Overclock (I know real original right) and with that and SetCPU was able to oc my 550mhz to 1100. Is there a Vibrant app similar?
How do I tell if my hardware is locked? Once I know, then I will search the threads for that. I already saw some in here with regards to how to do it. I already got into stock recovery last night just to check and see if I could (have't put CWR in or rooted yet-will do that later on tonight). Does this mean it isn't HWL or am I completely missing the target?
Odin I assume is what RSDlite is to Motorola. You power up to bootloader, connect to PC and flash "stock" sbf files (which is basically what came in the box). I always like to have that on hand just in case. I'll google and check it out.
Thanks for the info and glad to be here.
Read the noob stockier guide. Has all the info you need. Also in the development section down load the aio vibrant toolbox. Has Odin, all the files you need. I recommend the rom bi winning V3. It has a kernel that can overclock. You need an app for that tho. I like set CPU because it has profile management for off screen, charging etc.. good luck.
To tell if your hardware locked turn your phone off and hold down both volume rockers and press the power button when you see the vibrant logo pop up, keep holding untilled it goes away then pops up again. Then let go of the power. It should boot into recovery mode. It will be black screen with blue letters that say reboot phone, reinstall packages, wipe data. It may take a few times to get the hang of it. If your unable to then your phones is hardware locked.
Okay, youce been in recov so youre not hw locked.... greggory, you only have to hold power button till you see anything oon the screen the first time... holding it after that just makes it hw reboot whivh works, but is a waste of time.
Okay OP, odin has some nice ffeatures that let you flash bootloaders and firmware both.. truthfully, you can flash ANY rewritable media in your phone except internal and external sd from.odin afaik.
Oc requires an oc kernel and an oc app... app for ocing include voltage control, which was made for samsung galaxy s, set cpu, which i dislike, cpu master, no-frills ... all of em work most of the time and i use Voltage control..
Am i forgetting tto address anything?
Sent from a cell tower to the XDA server to you.
Ok so I've been using for a few days & I have to say the I really like this phone. Rooted and installed CWR lickity-split. Want to mess around and get more comfortable with surroundings, but have a few questions.
I dl'd Tegrak OC and am using it just fine. Any suggestions on stock kernal settings. Not applying any ROMs/Kernals for now, but setting suggestions would be helpful.
Got USB connection loop. Think I have a fix for that. Need to test some more.
Do I really have to name it update.zip to make "it" work, or can I name it anything else. Tried a few other names and they don't seem to install. Update.zip v buttermilkbiscuit.zip. why?
Does zipthemer work on this phone and do I have to name it Update.zip to make it work?
To change fonts, where do I put ttf? In settings there is a font changer, but where is the folder for that. Know it isn't /system/fonts BC that is a global changer but can't find it anywhere else. Looked in /data, /android and /sdcard. Clues?
Woodrube said:
Ok so I've been using for a few days & I have to say the I really like this phone. Rooted and installed CWR lickity-split. Want to mess around and get more comfortable with surroundings, but have a few questions.
I dl'd Tegrak OC and am using it just fine. Any suggestions on stock kernal settings. Not applying any ROMs/Kernals for now, but setting suggestions would be helpful.
Got USB connection loop. Think I have a fix for that. Need to test some more.
Do I really have to name it update.zip to make "it" work, or can I name it anything else. Tried a few other names and they don't seem to install. Update.zip v buttermilkbiscuit.zip. why?
Does zipthemer work on this phone and do I have to name it Update.zip to make it work?
Click to expand...
Click to collapse
Ok i think you should flash rom an kernel it takes phone to another an you do have to name it update.zip that is what recovery looks for an that is how custom one is installed i dont know what zip themer is but if u mean apply thme with zip then yes u can
Sent from my SGH-T959 using XDA App
Jasonhunterx said:
Ok i think you should flash rom an kernel it takes phone to another an you do have to name it update.zip that is what recovery looks for an that is how custom one is installed i dont know what zip themer is but if u mean apply thme with zip then yes u can
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I'll flash soon enough, just want to get my feet wet a bit. Only had phone for two days, so still picking and searching. More suggestions on ROMs/kernals, other than above?
Zipthemer is sweet. It takes all unzipped Metamorph.xmls, packages into one .zip and also creates and undo.zip too. Great themer.
There is a font changer in settings, but where is the folder to put the ttf file? /system/font is global, but looked in /data and /android and can't figure where to put it.
Just doing some house cleaning in my account and found this thread. It was my first thread in the Vibrant fora, just 5 short months ago.
Seems like so long ago. Have learned so much since then. Some have gone and some are still here, but I love this phone and the community that supports it.
Woodrube said:
Just doing some house cleaning in my account and found this thread. It was my first thread in the Vibrant fora, just 5 short months ago.
Seems like so long ago. Have learned so much since then. Some have gone and some are still here, but I love this phone and the community that supports it.
Click to expand...
Click to collapse
Lmao I was reading this thread going .... is wood trolling us right now till the last post then I looked at the dates lol
Sent from my SGH-T959 using XDA
Woodrube said:
Just doing some house cleaning in my account and found this thread. It was my first thread in the Vibrant fora, just 5 short months ago.
Seems like so long ago. Have learned so much since then. Some have gone and some are still here, but I love this phone and the community that supports it.
Click to expand...
Click to collapse
Lol ... I couldn't resist! Just had to take a peak here - esp. seeing Woody's name and "New to the phone" in the title!! :what:
Woodman ...
The Vibrant fora wouldn't be the same experience without your participation, brother. Your ICS Guide thread (and our extensive GB BL discussion ... lol) originally inspired me to take the ICS leap (as well build the nerve to finally register and participate in threads here - ie. I was a long time "lurker"). Haven't looked back since.
Thanks for your efforts to ensuring all our Vibrant experiences stay ... well ... "Vibrant"!
That is funny. I just went back a re-read that thread. There is some good Q and A in there about all types of scenarios. Alot of familiar names too that have moved up in the ranks of experience as well.
Woodrube said:
That is funny. I just went back a re-read that thread. There is some good Q and A in there about all types of scenarios. Alot of familiar names too that have moved up in the ranks of experience as well.
Click to expand...
Click to collapse
Haha ... I just did the same. That thread could have been called, "Everything you wanted to know about ICS ... but weren't afraid to ask." Hilarious.
I'm not sure what wasn't discussed. We hit all the corners including some homescreen screenshots as icing on the cake. Great (re)read!
I completely forgot that some of the Zen crew had joined in ... Mostdef, bobshute, xriderx66. Lol. :thumbup:
Noobs these days
Sent from my SGH-T959 using xda premium
This was fun to read, seeing Wood just entering the Vibrant community. The new guy on the block. Now look at you, you're one of the most recognized Vibrant users.
I remember my first post on XDA. I was messing around with Rom Manager and accidentally installed CWR. You wouldn't believe how much I was panicking, I thought I had bricked my phone! Lol, shows how much I knew.
Actually, that's why my name is "N00B_IN_N33D", because I was a noob who was in need of help. After I figured out how to Odin back to stock, which removed the (what I thought was) evil CWR I thought I wouldn't mess with my phone anymore. However s15274n talked me into flashing a custom froyo rom, Trigger, if I remember correctly. From there I blossomed in my understanding of Android and my Vibrant...
Anyhow, back on topic. It's amazing how experienced people have become here.
Sent from my SGH-T959 (Samsung Vibrant)
xriderx66 said:
Noobs these days
Click to expand...
Click to collapse
We all growed up real good.
N00B_IN_N33D said:
This was fun to read, seeing Wood just entering the Vibrant community. The new guy on the block. Now look at you, you're one of the most recognized Vibrant users.
[...]
Anyhow, back on topic. It's amazing how experienced people have become here.
Click to expand...
Click to collapse
The Woodman deserves his due "respect" (but you have to say it the way AliG would to get the full effect). True Zen-like patience and an extremely rare dedication to help people. He's good peoples. No doubt!
Speaking of the way-back machine ... I can't even remember what Froyo was like. Do you? Then there's Eclair (yikes!). :what: I do remember the jump from Froyo to GB was pretty substantial. CM7 with those novel toggle bars and major speed boosts. Then ICS just took the phone to another level.
I remember the first time I rooted my phone, I was soooo damn nervous that I'd end up with a brick. I was just using SuperOneClick ... lol. The first time using Odin after reading all the horror stories here. The first time waiting through the VLF EXT4 conversion (seemed to take forever).
Been a fun ride.
yosup said:
The first time waiting through the VLF EXT4 conversion (seemed to take forever).
Click to expand...
Click to collapse
The first time I flashed a Froyo Voodoo kernel, I was in my basement watching a west coast baseball game and it was late. The wife and kids were asleep and like you said, it took forever. Forgot to turn the volume off when I did it. So I am sitting there watching the game and I see the Bali palm tree. I think cool, whatever. I return to the game and out of nowhere, I hear this lady's voice. Thought it must have been the parabolic on TV picking up some lady in the stands. Then I hear it again. Kind of freaked me out until I realized it was LINDA. I'll tell ya, if you are ready for her, she'll freak you the f**k out.
Anyways, thanks for the kind words. I remember one of the many freak out, panic sessions I've had in the past and there was always someone who helped me out. Just feel it is my duty to give back. Now if I can solve this Encryption Error bug, I'll have come full circle. It is driving me nuts.
I remember one of my first threads back in 2009
It was a fake Hero ROM for G1
I bashed on two devs and everyone was pissed at me....then when I moved to the Vibrant I got a clean start
Woodrube said:
The first time I flashed a Froyo Voodoo kernel, I was in my basement watching a west coast baseball game and it was late. The wife and kids were asleep and like you said, it took forever. Forgot to turn the volume off when I did it. So I am sitting there watching the game and I see the Bali palm tree. I think cool, whatever. I return to the game and out of nowhere, I hear this lady's voice. Thought it must have been the parabolic on TV picking up some lady in the stands. Then I hear it again. Kind of freaked me out until I realized it was LINDA. I'll tell ya, if you are ready for her, she'll freak you the f**k out.
Anyways, thanks for the kind words. I remember one of the many freak out, panic sessions I've had in the past and there was always someone who helped me out. Just feel it is my duty to give back. Now if I can solve this Encryption Error bug, I'll have come full circle. It is driving me nuts.
Click to expand...
Click to collapse
atleast your LINDA issue was panicked and gone.
I was in the bathroom taking a dump while the conversion went on... it freaked me out, and my mom thought i was watching porn in there -.-'
She then told this story at our family reunion... Almost died of embarrassment
I am living with what I'll refer to as a successfully rooted NT...
Got 9.9.9 showing
installing a lot of apps - most work, some don't but that's due to no camera, bluetooth, etc. that I discover later
Now, as crazy as this may seem, I'm sure there are some of us out there who want to get our NT's as fully "droided up" as possible, and then, lo and behold, leave it alone. Just enjoy it (with all due credit to the devs who have made it possible!).
So, for the rest of us, can someone offer a "checklist" of any outstanding mods that should be done? I am not out here too much but what about this CM7 and/or CM9 I hear about? Will this represent the final frontier?
My goal in asking this question is to understand when I've reached a point where I no longer feel compelled to fiddle with my device, but also feel I've advanced it as far as technologically and functionally possible
once we get a fully working cm7 and cm9, the NT will essentially be a full android tablet.
cm9 is ice cream sandwich(android 4), cm7 is gingerbread(android 2.3)
final frontier? maybe but right now both are in alpha stage development -and it has come really far in the past 2 weeks since the bootloader was cracked/hacked/bypassed
Great! Now, the question becomes, will it be necessary to install CM7 to get to CM9, or will it be possible to go right to CM9 (which I am assuming is the better of the two choices).
wedmiston said:
Great! Now, the question becomes, will it be necessary to install CM7 to get to CM9, or will it be possible to go right to CM9 (which I am assuming is the better of the two choices).
Click to expand...
Click to collapse
straight to cm9
Sent from my Nook Tablet using XDA PREMIUM
Anybody willing to risk a guess as to timeframe to CM9? Just curious...I'm patient.
wedmiston said:
Anybody willing to risk a guess as to timeframe to CM9? Just curious...I'm patient.
Click to expand...
Click to collapse
When it's done. the main holdup on cm9 from reading the dev section is- sleep of death other than that essentially everything else works i believe. personally my guess is probably next week for an alpha release, but that is completely upto the people working on it.
no hardware video acceleration yet.
cm7 main holdup is wifi and sleep of death- again they fix those two items and -again- probably next week depending
Forgive my ignorance, but what is "sleep of death?" unless by that you mean bricking it. What would be the reason to go with CM7 if CM9 is apparently a more advanced version of android and is on a parallel development track?
wedmiston said:
Forgive my ignorance, but what is "sleep of death?" unless by that you mean bricking it. What would be the reason to go with CM7 if CM9 is apparently a more advanced version of android and is on a parallel development track?
Click to expand...
Click to collapse
1 Sleep of death is basically the inability to wake the nook from sleep mode. On stock nooks and working android devices the power button usually puts it to sleep. Right now CM on the nook puts it to sleep without allowing it to wake. It doesn't brick the device but it requires you to hard reset/reboot the device to make it usable again. When I say "hard reset," I mean in the traditional sense (holding a button sequence or cutting off power to FORCE a restart the device). I do NOT mean a "factory reset" that erases everything.
2 CM7 is already fully developed and released on other devices. In theory it should be far more stable and reliable than CM9, which is bleeding edge and unfinished in general. In other words, CM9 is practically guaranteed to have more bugs since it's got so much new stuff in it.
wedmiston said:
Forgive my ignorance, but what is "sleep of death?" unless by that you mean bricking it. What would be the reason to go with CM7 if CM9 is apparently a more advanced version of android and is on a parallel development track?
Click to expand...
Click to collapse
cm9 is a different kernel then cm7. What this means is not all apps will work on cm9. cm7 in theory should have better app compatibility, but cm9 should be better optimized for the NT.
As for sleep of death, I am pretty certain what it is, is every time the tablet goes to sleep. it dies.... why by now they have probably buried dozens of poor helpless NTs who never got a proper chance at life.... all in the name of progress. (ok sarcasm aside, SOD is simply you can't bring it back out of sleep. while I suppose you could simply disable sleep mode, doing so would badly hurt battery life, Also I believe they are trying to get bluetooth up and running as well for cm9)
So I hear you say cm7 = better app compatibility and cm9 = better optimized for the NT. In honor of super bowl season, sounds a bit like "great taste, less filling."
In other words, which would be the better choice between the two (assuming bugs have been worked out and both are stable)?
personal preference?
honestly, it'll be whichever you like best, with the way they have it setup to bypass the bootload in the nook tablet, you should be able to flash Either with the press of a button or two, try one for a week, try the other for a week, then decide which you like best.
you do have to remember cm7 is more for phones, which cm9 is more for tablets....
I agree with lenardo. The better of the two is the one that meets your needs. That said, I am more looking forward to CM9. I installed it on my phone a month ago and love it. It feels so much more polished. Not that I had any issues with CM7, but it just feels like "this is what Android should be." But beware ... once you start flashing and modding, it's quite addictive.
Sent from my SCH-I500 using Tapatalk
Thanks - based on your reply and what I was reading in a recent thread on choosing CM7 or CM9, I think I'll wait for 9 since I don't have the phone , only the NT.
I assume there will be some big announcement and posting along with step by step installation instructions?
wedmiston said:
Thanks - based on your reply and what I was reading in a recent thread on choosing CM7 or CM9, I think I'll wait for 9 since I don't have the phone , only the NT.
I assume there will be some big announcement and posting along with step by step installation instructions?
Click to expand...
Click to collapse
announcement is likely, step by step instructions will most likely involve using cwm to install. So if you haven't already installed it, install cwm now so you will be ready
http://forum.xda-developers.com/showthread.php?t=1458630
as for cm9 vs cm7 as the others have stated most people are waiting for cm9. I will most certainly give both a try. unless there is an app that I can't live without that just won't run on cm9, I will probably be using it. If I find I can't use certain apps with cm9, then I will be moving to cm7. However I will give both a try. there is little point in making a decision with only looking at one side of the choice.
ckevinwelch said:
I agree with lenardo. The better of the two is the one that meets your needs. That said, I am more looking forward to CM9. I installed it on my phone a month ago and love it. It feels so much more polished. Not that I had any issues with CM7, but it just feels like "this is what Android should be." But beware ... once you start flashing and modding, it's quite addictive.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
Oh, I forgot to mention that CM9 should support tablet-focused apps as well.
Sent from my SCH-I500 using Tapatalk
Checked out the thread and downloaded the Nook recovery Flasher.apk - is this is what I install and use if necessary?
lol I couldn't agree more with wedmiston post on developments of the NT.. I know these guys are working full time to ~freethenook~ and it takes some diligence to simply stay up to date with these fast moving mods and alterations.... But its interesting to see how these is evolving.
---------- Post added at 10:35 PM ---------- Previous post was at 10:33 PM ----------
I'm patient.....................lmao
wedmiston said:
Checked out the thread and downloaded the Nook recovery Flasher.apk - is this is what I install and use if necessary?
Click to expand...
Click to collapse
Yes. to explain what the recovery flasher app does. it installs clockworkmod (cwm) or the nook stock recovery. the stock recovery is what you would use to fix your nook if you really screw it up somehow. you can access it by holding the power and nook buttons at the same time while booting up. (i.e. the power is off, turn it on with both the n button and the power button, holding them until it gives you the option to restore stock firmware).
Clockwork mod would replace this. If you use the recovery flasher to flash cwm, then instead of the option to reset the device to factory settings, holding the power button + n button on bootup will get you into the CWM menu. cmw can be used for several things. It can backup your firmware so you can restore things if you screw up. (i.e. backup your rooted firmware, so resetting isn't unrooting anymore) or it can flash zip files to modify your existing firmware. you would be using the flash zip files function to flash the cm9 or cm7 firmware once they are done.
There isn't much atm that you can do with cwm other then backup your current firmware in case you screw something up, however I would suggest doing so. it's always good to have an easy way to fix things if you screw it up somehow playing around makes it easy.
The flasher apk will also allow you to flash back to the default barnes and noble recovery if you wanted to get rid of cwm for some reason I can't think of.
EDIT: you can also download "Quickboot" from the google market to get to the recovery menu without rebooting and holding the n button + power button.
Also useful to know. controls in CWM: + and - buttons will move between options. n button will select whatever you are on, and the back button is the power button.
To piggyback on the reply above there really isn't any need for quick boot as Indirect's App ALSO allows to "reboot recovery" from within the app.
As the system would need to be running in order you use this, there really isn't any need for both app's strictly to get to recovery.
The advantage of Quick Boot is that it also offers you the option to "reboot" the device which I believe is currently only possible by turning it off and then back on. Not a big deal but it will save an extra step.
The disadvantage of Quick Boot is that it will also provide you with the option to boot into the bootloader. DON"T click that.
Land Master said:
To piggyback on the reply above there really isn't any need for quick boot as Indirect's App ALSO allows to "reboot recovery" from within the app.
As the system would need to be running in order you use this, there really isn't any need for both app's strictly to get to recovery.
The advantage of Quick Boot is that it also offers you the option to "reboot" the device which I believe is currently only possible by turning it off and then back on. Not a big deal but it will save an extra step.
The disadvantage of Quick Boot is that it will also provide you with the option to boot into the bootloader. DON"T click that.
Click to expand...
Click to collapse
u can also do a quick reboot by using terminal emulator, and doing su and then reboot, very quick...
Let me preface this with the following (usually stated by the biggest idiot in the room) I am not a total noob when it comes to computer related stuff. I have been building and maintaining networks for better than a decade. Android is a bit new to me but I can follow directions and get things working without fail... usually. Also, Please let me state this is in no way shape or form a bash against the devs. This is an honest to god post looking for others feedback to make sure I am not missing something.
I guess this is a question for others that have run both CM 9 and CM 10. Has anyone noticed a degradation of performance when running CM 10 vs CM 9 from SD on a 16gb NT?
I have tried several versions of CM 10 and all have the same issues. SOD, games don't work, frequent power downs... the usual complaints. I originally skipped CM 9 because hey I wanted the latest and greatest but decided after reading some other threads about stability to give CM 9 0.5.3 a try. Wow what a night and day difference. Everything that didn't work in 10 works perfectly in 9(using the same card and partition layout).
On my CM10 installs I tried reformatting the SD card numerous times (Transcend 8GB/CL4). I tried the last 3 updated versions posted by chrmhoffman(SP?) I've wiped and re-wiped dalvik and cache, though to be honest from the SD version I am not sure if it does anything. I have tried re-downloading the files in the event they were corrupted. I've verified that I properly placed updater-script for the SD install. I have spent hours verifying and re-verifying I didn't miss something. Other than the B&N repartition I have nothing special done to my nook. I haven't even installed a recovery or rooted the stock OS.
So perhaps I'm doing it wrong? Will an internal install make a difference?
I have read many a thread and haven't found anything comparing the 2. If they exist and this has been mentioned please direct me to the appropriate reading material.
SlowCobra96 said:
Let me preface this with the following (usually stated by the biggest idiot in the room) I am not a total noob when it comes to computer related stuff. I have been building and maintaining networks for better than a decade. Android is a bit new to me but I can follow directions and get things working without fail... usually. Also, Please let me state this is in no way shape or form a bash against the devs. This is an honest to god post looking for others feedback to make sure I am not missing something.
I guess this is a question for others that have run both CM 9 and CM 10. Has anyone noticed a degradation of performance when running CM 10 vs CM 9 from SD on a 16gb NT?
I have tried several versions of CM 10 and all have the same issues. SOD, games don't work, frequent power downs... the usual complaints. I originally skipped CM 9 because hey I wanted the latest and greatest but decided after reading some other threads about stability to give CM 9 0.5.3 a try. Wow what a night and day difference. Everything that didn't work in 10 works perfectly in 9(using the same card and partition layout).
On my CM10 installs I tried reformatting the SD card numerous times (Transcend 8GB/CL4). I tried the last 3 updated versions posted by chrmhoffman(SP?) I've wiped and re-wiped dalvik and cache, though to be honest from the SD version I am not sure if it does anything. I have tried re-downloading the files in the event they were corrupted. I've verified that I properly placed updater-script for the SD install. I have spent hours verifying and re-verifying I didn't miss something. Other than the B&N repartition I have nothing special done to my nook. I haven't even installed a recovery or rooted the stock OS.
So perhaps I'm doing it wrong? Will an internal install make a difference?
I have read many a thread and haven't found anything comparing the 2. If they exist and this has been mentioned please direct me to the appropriate reading material.
Click to expand...
Click to collapse
Take a look at the CM9, CM10 and the kernel 3.0 threads in the developer section. There are two flavors of CM9 out there, one compiled with the GB kernel and one compiled with the ICS kernel (sorry, but I can't recall at which point chrmhoffman moved his CM10 build to the newer kernel). All of the problems you mentioned are well know bugs in the 3.0.x kernel at this time, and the devs are working feverishly to resolve them. In the meantime, running CM9 with the GB kernel (2.65.x) will give you a more stable platform, but no access to the advanced features in the newer kernel -- hardware video acceleration being the most obvious of the new features.
With all of that being said, I've been switching between chrmhoffman's latest CM10 build and demetris' latest CM10/cherry pick build for the last couple of days, and they are both tremendously improved over their earlier builds in terms of stability. I would confidently use either one as a daily driver at this point.
Ugh, see I'm an idiot. I totally spaced on the fact that it wasn't running 3.x kernel.
OK beyond that I still find CM10 really unusable and I'm not sure how others are getting it to function so well. I've tried the last 3 revisions with the same results on each of them. Could it be a matter of not running it from internal? Has anyone tried the SD version then switched to emmc? If yes what were your results and observations?
Sent from my NookTablet using xda app-developers app
I actually find that ROMs run better from my SD card, but that's probably due to my SD card having pretty good speeds. As for the problems that currently exist on the CM10 ROMs, there isn't going to be much difference in BSODs and random reboots between running from internal and SD.
Solar.Plexus said:
I actually find that ROMs run better from my SD card, but that's probably due to my SD card having pretty good speeds. As for the problems that currently exist on the CM10 ROMs, there isn't going to be much difference in BSODs and random reboots between running from internal and SD.
Click to expand...
Click to collapse
Yep, the biggest improvements I've seen is from turning on "Don't Keep Activities" in the Developer Options and setting the CPU Governor to HOTPLUG in the Performance Options. With these set, I'm actually able to run for days at a time without getting an SOD failure.
spcagigas said:
Yep, the biggest improvements I've seen is from turning on "Don't Keep Activities" in the Developer Options and setting the CPU Governor to HOTPLUG in the Performance Options. With these set, I'm actually able to run for days at a time without getting an SOD failure.
Click to expand...
Click to collapse
Are you ****ting me? Days? With those settings I am lucky to get mins! Seriously the reason for the post was that I get 20 mins tops before I have to reboot it. Then it takes forever to reboot stating it is optimizing applications.
I did a clean install of 04/10 the day it came out and I haven't had a single reboot or SOD. I do have some minor issues with video playback but YouTube works as does MX Player (with software decoder). Battery life has been great too with about 2 1/2-3 days on a charge.
This is with the ROM Installed to internal emmc.
Sent from my Barnes & Noble Nook Tablet using xda premium
LifeWOutMilk said:
I did a clean install of 04/10 the day it came out and I haven't had a single reboot or SOD. I do have some minor issues with video playback but YouTube works as does MX Player (with software decoder). Battery life has been great too with about 2 1/2-3 days on a charge.
This is with the ROM Installed to internal emmc.
Sent from my Barnes & Noble Nook Tablet using xda premium
Click to expand...
Click to collapse
Ill give that version a shot and see what happens.
Ok so I looked at the latest CM10 and it looks like 0.5.3. I have tried that revision with the same abysmal results as the 5.2 and 5.1 or whatever the 2 previous revisions were.
Ugh talk about frustrating! I truly don't understand what I can be doing wrong that others can daily drive it and I can't even get 30 mins out of it.
SlowCobra96 said:
Are you ****ting me? Days? With those settings I am lucky to get mins! Seriously the reason for the post was that I get 20 mins tops before I have to reboot it. Then it takes forever to reboot stating it is optimizing applications.
Click to expand...
Click to collapse
No ***ting at all. I let my son run my NT until the battery died yesterday. I plugged it in for a few hours (probably more like 6 or 7 hours, to be honest). Powered it up 12 hours ago and unplugged it to check on battery performance. Now it's been running for 12+ hours without an SOD, and is at 85% battery...
I hate you! hahaha Just kidding. I think I hate my nook right now though.
Hey guys, all well and good but I would recommend you due to serial number implemented now be careful when you show it on public forums. Maybe b&n is watching you :banghead:
Sent from my Barnes & Noble Nook Tablet using xda app-developers app
Have to 2nd the no SODs. Got a few with the first few releases but nothing since. I'm on Chris' CM10 (internal), no changes to CPU etc. The battery life is still bad but I try not let it get too low so I plug it in every night to charge.
Nikkiel
Sent from my Barnes & Noble Nook Tablet using xda premium
Some of you are really making me feel like this! haha It seems that all of you running solid appear to be running it internally. I'm starting to get the funny feeling that the SD modified version may be the problem.
demetris_I said:
Hey guys, all well and good but I would recommend you due to serial number implemented now be careful when you show it on public forums. Maybe b&n is watching you :banghead:
Sent from my Barnes & Noble Nook Tablet using xda app-developers app
Click to expand...
Click to collapse
Thanks for the warning/reminder... I hadn't even thought about that...
I installed CM10 on my Droid X2 and I just couldn't get past the screen sensitivity -- everything was jumpy to the point where the phone wasn't usable. Is this something others have noticed, too? Is there a way to adjust the sensitivity?
sjwoo said:
I installed CM10 on my Droid X2 and I just couldn't get past the screen sensitivity -- everything was jumpy to the point where the phone wasn't usable. Is this something others have noticed, too? Is there a way to adjust the sensitivity?
Click to expand...
Click to collapse
What do you mean it was jumpy? Are you saying it is too sensitive? I dont know of any way to adjust it but I have no problems with it.
jsgraphicart said:
What do you mean it was jumpy? Are you saying it is too sensitive? I dont know of any way to adjust it but I have no problems with it.
Click to expand...
Click to collapse
Yeah, way too sensitive. Damn, maybe it's just my Droid X2. I'd scroll up an down and it was just super sensitive, moving up and down at the slightest touch.
- Sung
Also -- the screen seemed to flicker way more. I think some of it was intentional (the screen dimming and brightening). As much as I liked the look, I went back to CM7.
I haven't noticed any screen flicker, or too sensitive touch
It has seemed less sensitive, to me
You are not the only one. Had same thing on my DX2. It happened 4-5 times.
I just kept trying to get "power off / reboot" screen and reboot. After reboot everything was good.
Also had faster battery drain, purchased a 3600mAh and it would almost last 10 hours on CM10.
Two days ago went back to CM7, battery will last 14-16 hours with same usage.
Going to wait for next CM10 release to try again.
Sent from my MB870 using xda app-developers app
sjwoo said:
Also -- the screen seemed to flicker way more. I think some of it was intentional (the screen dimming and brightening). As much as I liked the look, I went back to CM7.
Click to expand...
Click to collapse
Thasian483 said:
You are not the only one. Had same thing on my DX2. It happened 4-5 times.
I just kept trying to get "power off / reboot" screen and reboot. After reboot everything was good.
Also had faster battery drain, purchased a 3600mAh and it would almost last 10 hours on CM10.
Two days ago went back to CM7, battery will last 14-16 hours with same usage.
Going to wait for next CM10 release to try again.
Sent from my MB870 using xda app-developers app
Click to expand...
Click to collapse
You guys need to understand that this ROM will never be perfect. Even the next update will have issues.
Understand, also understand ANY ROM can have issues, including Vz ROMs.
It's about what works for each person, in this case I am waiting for the next release, please don't get defensive because we had issues. They happened, no big deal, we have made decisions to move back to CM7.
I happen to think DZK has done a great job with CM10 and I will be moving back.
Sent from my MB870 using xda app-developers app
Thasian483 said:
Understand, also understand ANY ROM can have issues, including Vz ROMs.
It's about what works for each person, in this case I am waiting for the next release, please don't get defensive because we had issues. They happened, no big deal, we have made decisions to move back to CM7.
I happen to think DZK has done a great job with CM10 and I will be moving back.
Sent from my MB870 using xda app-developers app
Click to expand...
Click to collapse
Oh I'm not being defensive. Sorry to come off that way. I just see that you guys are newcomers to the forums. A lot of newcomers have been posting about issues not understanding that our Droid X2 is not like other phones that get custom ROMs. Our CM10 is not really complete and most likely never will be because motorola hates us and doesnt want to unlock our bootloaders. If you guys are new to the DX2, I didnt want you expecting a full featured bugless ROM like, lets say the Galaxy Nexus would get. Even though its CM10, we are running it on a Gingerbread Kernel which will always cause issues. That, along with not being able to change or update the drivers doesnt help. Thats why I said even the next update will most likely have the same issues. Most of us just chose to deal with them.
jsgraphicart said:
Oh I'm not being defensive. Sorry to come off that way. I just see that you guys are newcomers to the forums. A lot of newcomers have been posting about issues not understanding that our Droid X2 is not like other phones that get custom ROMs. Our CM10 is not really complete and most likely never will be because motorola hates us and doesnt want to unlock our bootloaders. If you guys are new to the DX2, I didnt want you expecting a full featured bugless ROM like, lets say the Galaxy Nexus would get. Even though its CM10, we are running it on a Gingerbread Kernel which will always cause issues. That, along with not being able to change or update the drivers doesnt help. Thats why I said even the next update will most likely have the same issues. Most of us just chose to deal with them.
Click to expand...
Click to collapse
I wasn't aware of the Motorola situation when I purchased the DX2, but quickly found out. I came from the Samsung world (Fascinate) as my last device and it seemed custom ROM's were very easy. With the DX2 it has been anything but easy. But for now really happy with the device overall and the CM10 ROM will make it great. The primary reason for my move back to CM7 was a call issue that seems to be well documented. If it isn't corrected with the new version of CM10 I will make adjustments and stick with it. Also the DX2 community here on XDA is great.
I haven't had the any call issues, but I make/receive very few calls
mostly texts and emails
jsgraphicart said:
Oh I'm not being defensive. Sorry to come off that way. I just see that you guys are newcomers to the forums. A lot of newcomers have been posting about issues not understanding that our Droid X2 is not like other phones that get custom ROMs. Our CM10 is not really complete and most likely never will be because motorola hates us and doesnt want to unlock our bootloaders. If you guys are new to the DX2, I didnt want you expecting a full featured bugless ROM like, lets say the Galaxy Nexus would get. Even though its CM10, we are running it on a Gingerbread Kernel which will always cause issues. That, along with not being able to change or update the drivers doesnt help. Thats why I said even the next update will most likely have the same issues. Most of us just chose to deal with them.
Click to expand...
Click to collapse
Hey there -- just wanted to also say that I hope I wasn't coming off as a complainer (which probably meant I was!). I'm totally and absolutely grateful for all of dragonkiller's work on porting CM. I HATED my Droid X2 with BLUR -- and it has been a great joy to use since I switched to CM7.2.
I do wonder, though, that Jellybean requires a more powerful processor? CM10, outside of the sensitivity issue, felt slower in every way. I just may keep CM7.2 on this phone forever -- it's just a great ROM.
If JB felt slower to you then something is wrong. Did you install it from a clean 2.3.4 SBF?
Sent from my JB'd X2
GoClifGo05 said:
If JB felt slower to you then something is wrong. Did you install it from a clean 2.3.4 SBF?
Sent from my JB'd X2
Click to expand...
Click to collapse
Actually upgraded from CM7 to CM10 first time. Since moving back to CM7, I did an SBF with a clean install of CM10 and things are MUCH BETTER. Not going back at this point. This is only day two, but things are good. I did figure out that when I installed an app that CM10 did not like the screen started acting strange, but getting rid of the app and rebooting solved the issue.
I did end up with one strange problem, still working on it. I used Titanium to restore most of my apps, but wanted to do a clean install on Flash Player. So went in found the apk from my file mgr, selected "install", went to what I call the Android Install screen with two buttons at the bottom (Cancel & Install), tried to select the Install, nothing happened. I do have "Unknown Sources" checked in Security. I have tried other apk's just to test and none seem to work. Tried to move the apk's to the SD0 card, and that had no effect either. The strange thing, I had Flash Player working before going back to CM7.