yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S Blaze 4G] mdneilson:
My battery life is OK, but not great. I know there was a kernel issue (just got fixed on my MT4GS) that may be causing the issue. Do you have CPU Spy installed? Are you getting any time reported as deep sleep?
[Samsung Galaxy S Blaze 4G] chrisxbell714:
No I never heard of CPU spy but I use cool tool for system stats and every startup for litterlly almost 10 mins sometimes less the first core tops out the second core doesn't doesn't do anything unless I open up an app or something and I have it set to 1350mhz to squeeze a little more battery as well with lowest brightness all the time, Even tried resseting the boot setting for the cpu to see if it would help and it didnt. Someone else said the CPU speed doesn't stick but it actually does stick just the setting is buggy and shows 1512, cool tool showed my setting properly. I have the same apps from dark knight so I know its not them and I know I'm not doing anything wrong lol flashing wise

Sent from my SAMSUNG-SGH-T769
[Samsung Galaxy S Blaze 4G] mdneilson:
You have some really terrible cell coverage. Bad reception can cause a lot of battery drain. My cpu spy is reporting normal deep sleep activity. I am at 74 percent on my battery with over an hour screen on and Wi-Fi always on. Do you get better reception with dark knight?

EDIT: Also, dual core on phones is the same as on PCs. The second core won't get used unless an app is specifically coded to use two, or the system decides to offload to the other core. Offloading is rare, as most apps don't require that much power, so to conserve battery the system will cache another process to make power available to the forefront app. On PCs you can set core affinity, so a program will always use core 1 (the second core - the first is core 0). I don't know if there is a way to set affinity on a phone, but it shouldn't be necessary unless you are a massive multi-tasker.

Sent from Tapatalk on Android.

---------- Post added at 09:43 PM ---------- Previous post was at 09:37 PM ----------

Also, can we update the title of this thread to reflect the ROM's new status as CM official?
[Samsung Galaxy S Blaze 4G] chrisxbell714:
Compared to dk8 about the same reception but WiFi seems stronger with cm10, depending on where I am in my house I get 2 to 4 bars, signal in my area is pretty decent 3 to 4 bars when I'm out driving I get an average 2 mb/s on just data. I used CPU spy here are the results it only lasted 7 mins this time after reboot luckily.

Sent from my SAMSUNG-SGH-T769
[Samsung Galaxy S Blaze 4G] chrisxbell714:
I know about CPU affinity for PCs I'm pretty much a computer geek lol

Sent from my SAMSUNG-SGH-T769
[Samsung Galaxy S Blaze 4G] mdneilson:
lol. I think most people on here are, but I don't like to assume.

My CPU spy stats look very much the same... the device doesn't seem to throttle well. It is either in the lowest clock, highest clock, or deep sleep. Tweetcaster, Messaging or text pages in Chrome (what I've used since reboot) shouldn't need 1512Mhz of CPU. I am using the on-demand profile - i've used conservative before with the same results. :confused:
[Samsung Galaxy S Blaze 4G] chrisxbell714:
Exactly Im using cfq with ondemand but somethings wrong somewhere, probably kernel i can deal with it for now I figured I would share my experience so far but thanks man I guess I'll go back to xcom for now haha

Sent from my SAMSUNG-SGH-T769
[Samsung Galaxy S Blaze 4G] JazzedRob:
Yes... please

This is a feature I really want, if it can be worked out.

I also wonder if it is feasible to merge the internal memory with the internal USB storage. That way we'd only have internal memory and external SD (versus the internal memory, internal SD, and external SD). Would that mess up the way the phone interfaces with the computer? I just wish I had a bit more memory for larger apps, and didn't have to deal with the weird storage set up.
[Samsung Galaxy S Blaze 4G] chrisxbell714:
Media used alot of battery when I left my phone unplugged over night I noticed this before.

Sent from my CM10 Blaze
[Samsung Galaxy S Blaze 4G] skwrl:
Applied BLN fix, wiped cache and dalvik cache. Smart Keyboard pro keeps crashing on me. It just keeps flickering and disappearing as I type. Longest I've been able to type is one sentence without it disappearing. Halp >_<
[Samsung Galaxy S Blaze 4G] Animosity:
is anyone else having download problems. Nothing is downloading off of the browser
[Samsung Galaxy S Blaze 4G] shaikmonster:
Are you looking on the internal card
[Samsung Galaxy S Blaze 4G] mdneilson:
Custom MTD partitions would be able to do what you want with expanding /data with space from the internal_sd. Unfortunately it is a messy hack that requires a lot of work, it would be way down on the priority list for this phone since it really only just got dev work started, and completely moot since moving an app to the sd card in the default app manager will move it to the internal sd anyway.

Moving pictures to the external sd may be possible with symlinks, but both storage places use fat partitions that doesn't support symlinks. I think there is a way to insert a symlink in the root folder, but I'd have to dig more and I'm swamped with work rn. Thinking about it, you'd want to bind mount the directory, so if the sd card were removed, pictures would still store on the internal memory.

The BLN fix isn't needed for the official CM nightly. Try fixing permissions for the kb.
[Samsung Galaxy S Blaze 4G] skwrl:
The BLN fix seemed to fix my sounds not working though. Just tried fixing permissions and it seems to be working fine now :) Thank you!
[Samsung Galaxy S Blaze 4G] chjema:
Wow...now im bootlooping. Sigh..

Back to Gingerbread for me. the only stable ICS is Thaz and Stock. So back to tweaked I go.

(nothing against anyone, just SOD sucks)
[Samsung Galaxy S Blaze 4G] mdneilson:
This is JB, not ICS, and a nightly. If bulletproof is what you need, then definitely steer clear of nightlies.
[Samsung Galaxy S Blaze 4G] Captivate-me:
Is there a way to revert from the nav bar or turn it off...or will I have to reflash to get rid of it?

TIA
[Samsung Galaxy S Blaze 4G] jparnell8839:
you should be able to reflash without wiping data to get rid of it... in theory...
[Samsung Galaxy S Blaze 4G] chjema:
Bro..IM a tester for them....So..yeah..

JB ICS doesnt matter they both have serious probs atm Except for stock which is bleh

But I do know dras. is working hard on this, and Team Fah-q is about to drop some serious ****.

I know whats up.
[Samsung Galaxy S Blaze 4G] junkypong:
Waiting for the next nightly...i hope we get it tonight!
[Samsung Galaxy S Blaze 4G] mdneilson:
I was mostly trying to be facetious, but obviously failed - it's pretty clear that you know what direction is up. I didn't know you were a tester for them though (thanks btw). Good to know that heaps of headway are incoming.
[Samsung Galaxy S Blaze 4G] Chitown021:
Dr4stic you are awesome man! Read your post in your other thread and I am downloading your unofficial build for the 17th now. I can't thank you enough for all of your hard work! I am looking forward to the official nightlies to start back up for us in the coming days :thumbup:

Sent from my Samsung Galaxy S Blaze.
[Samsung Galaxy S Blaze 4G] grundlestain:
the black screen lock ups and bln strangeness are both happening on my vibrant as well as my blaze, the vibrant is on an older jb nightly by a day or two and the blaze is on the 12 but its the identical issues as is hitting us. hopefuly it will be worked out soon but i just wanted people to know that its not so much a blaze prob as it is a cm issue.
[Samsung Galaxy S Blaze 4G] dr4stic:
Thanks for mentioning that. I get worried that people think I'm making excuses.

Actually, I may have made an exchange of some dev work for helping debug the sod problem. It happens on my GS3 and another dev is wrangling up people across the different platforms to try and squash it. The exchange was for a working current BLN.... hopefully that pans out :)
[Samsung Galaxy S Blaze 4G] sgolem:
I've been working on a problem with my internal storage for a few days now. I can't mount it. I can browse to /sdcard0 and it's there, but empty. With superuser I can't change anything. Right now I can't download anything because of it. My external sd card is working perfectly, and apps install with no problems.

I've formatted the cache and reinstalled several times. Still, the problem persists. I noticed there were several people with problems with the camera saving to the internal memory, but nothing has worked so far.

If anyone has discovered a workaround, I'll be happy. I just need to get my contacts from my old phone,- it'll only send them via bluetooth, which I cannot download due to this problem.

Other than that, this is working almost perfectly. This is a beautiful mod. Thank you for all your hard work!
[Samsung Galaxy S Blaze 4G] Chitown021:
The unofficial 17th update is working great for me so far. It seems to be less laggy. Apps open faster & smoother. Data seems a bit slow but that's probably due to me being at work. Data is always bad here.

Sent from my Samsung Galaxy S Blaze.
[Samsung Galaxy S Blaze 4G] BrownLarry:
How do you change the bln settings? I don't seem to be having any issues with this build. Do you need to turn it on? Where's it located?
[Samsung Galaxy S Blaze 4G] Animosity:
Should I wipe data and such on the new unofficial build 17?
[Samsung Galaxy S Blaze 4G] Captivate-me:
Did a full wipe and flashed unofficial build 17....so far smooth sailing. No sod, and not resets while listening to music...I've been listening for about 2 hours straight-I'm all smiles :)

Thanks!
[Samsung Galaxy S Blaze 4G] sgolem:
Found a workaround. Found a roundabout way to get the .vcf files off my old phone and onto my pc. From there, put them on Google contacts, and then, synced to my phone. Perhaps Googledocs can be a viable workaround to some of the other problems people might be having.
[Samsung Galaxy S Blaze 4G] Chitown021:
I did an install over the 10/12 nightly and it's working fine but a full wipe can never hurt.
[Samsung Galaxy S Blaze 4G] marchingknight11:
I'm having an issue with the phone app chugging down my battery life. The battery stats say that the phone has used 62% battery life, which is strange, because 1) usually the display is by far the biggest power drain, but its only at 7% and 2) I only made 2 calls today. My battery was down to 9% after about 4 hours.

Anyone else had this problem?
[Samsung Galaxy S Blaze 4G] shaikmonster:
Holy crap... me too. I am on the 10/17 ROM. No reboots, but that is crazy...
[Samsung Galaxy S Blaze 4G] 2vivid:
Phone calls took up quite a bit more of my battery. I was at 30% took a 3 min call and it dropped to 23% before it might have dropped a percent but never 7%. But I hardly ever take calls anyways
[Samsung Galaxy S Blaze 4G] shaikmonster:
Wonder if the official 10/18 had that issue?
[Samsung Galaxy S Blaze 4G] johnb380:
Well the official build is up but it's only 100 bites more then the 10.12 build so idk if anything has even changed....

Hey dr4stic this is basically the same build u put out yesterday right...

I'm just gonna flash over top ur build Imo it should be fine....

I I wanted to give everyone a tip that seems to make this rom run better... After u flash and boot for first time and turn bln off and move sound rockers for notifications to sound and set everything up make sure u reboot once cuz I noticed that setting were resetting and some wouldn't take effect until I did I'm thinking maybe some of the reason I was getting reboots and sod last time on 10.12 build...

Any ways just my 2 cents hope it helps u

---------- Post added at 08:12 AM ---------- Previous post was at 07:25 AM ----------

Hey everyone idk if this will help but it seems to have stopped my SOD so try it off a clean install and see I know it's stupid but... what have u got to lose here's my other post

http://xdaforums.com/showthread.php?p=32958269

[ROM][OFFICIAL] CyanogenMod 10 (JellyBean) Nightly Builds for SGH-T769

---------- Post added at 08:13 AM ---------- Previous post was at 08:12 AM ----------

O and the only other thing I did different is set my cpu to interactive
[Samsung Galaxy S Blaze 4G] junkypong:
Is there difference between the build dr4stic released yesterday and the today's nightlies??
[Samsung Galaxy S Blaze 4G] marchingknight11:
I am having a problem with the camera flash being impossible to turn off. Even when I change the setting to force flash off, the flash is still used when I take a picture.

Anyone else? Is there a fix?
[Samsung Galaxy S Blaze 4G] dr4stic:
Guys, I'm curious to test my kernel patches with a known-better OS build... CM9. I ran a build and I was wondering if some of you could test it for me and let me know if there are any problems with it. Since the configurations are similar from CM10 for a number of things, and it's using mostly the same kernel base... I'd like some feedback.

Please visit my new funhouse thread in the android dev section to download it, thanks :)
[Samsung Galaxy S Blaze 4G] chrisxbell714:
New cm nightly still have most of the bugs from last release....*face palm*

Sent from my CM10 Blaze
[Samsung Galaxy S Blaze 4G] Flowbyte:
The new official build does not have the phone battery drain issue.

---------- Post added at 03:43 PM ---------- Previous post was at 03:42 PM ----------

In fact I've been using it all day and I've had no issues at all.
[Samsung Galaxy S Blaze 4G] marchingknight11:
I noticed that. flashed earlier today over the old one and haven't had the problem at all. I have had a couple more minor issues, but to solve them I might just do a wipe and flash tonight.
[Samsung Galaxy S Blaze 4G] chrisxbell714:
Then why does he CPU still max out for 10 mins at startup still. And the frequencies are messed up more now if you don't have interactive on the CPU maxes out continuously and even still its horrible I'm texting and the CPU is using max frequency...

Sent from my CM10 Blaze
[Samsung Galaxy S Blaze 4G] marchingknight11:
I would guess the reason would probably be that the CPU max issue you are having was not fixed. I don't believe the post said "the 10/18 build of CM10 is perfect and has absolutely no issues". he said this one particular issue that we were having was fixed.

Keep in mind this is a NIGHTLY. not a stable build. If you are going to use it, you have to expect there to be stability issues and bugs. If you can't deal with them, pick another ROM.
[Samsung Galaxy S Blaze 4G] Flowbyte:
Possibly I should of said that the new nightly does not have the issue that the phone application shows as using excessive amounts of battery when looking at battery stats...
[Samsung Galaxy S Blaze 4G] chrisxbell714:
I know its buggy I know its nightly I know its basically a beta...ive been using it since the first unofficial but how can the battery issue be fixed if the CPU is erratic? I've been patiently waiting for an update and it hasn't helped me thats why I said something in the first place.

Sent from my CM10 Blaze
[Samsung Galaxy S Blaze 4G] marchingknight11:
The battery issue is fixed because the problem was that the phone app was draining the battery, and that no longer happens. Ergo, the issue has been fixed. The CPU being erratic is a separate issue.

I really don't see what's unclear about this.

Also, you've only been "patiently waiting" for a little over a week. Things don't happen that quickly. continue being patient, and post a clear and well worded bug report.
[Samsung Galaxy S Blaze 4G] chrisxbell714:
I don't have time to argue with you I'm not 5, I'm SORRY I'm aggravated because this update is worse than the last release.

Sent from my CM10 Blaze
[Samsung Galaxy S Blaze 4G] dr4stic:
Seriously? Aggravated?

Do you have ANY idea how much time I put into fixing the break that happened between the 12th and 13th nightly? It was taking me 4.5 hours just to run a build, and then test. And you're aggravated? And in all of that time, I'm sorry I couldn't fix the wifi bug or make BLN any less wonky. I needed time to sleep.

I haven't asked for any donations, like many other devs do. But I do ask that you not be a baby.

You don't have to use this rom. I've been working with a ton of phenomenally talented people in order to make this happen, and I'm pretty confident that they couldn't give a crap if you are aggravated or not.

And guess what... it's the Big Android Barbecue this weekend. That means it's unlikely that many more bugs will get fixed between now and the end of it. That's because the people that are working hard so that you don't have to endure the pain that is touchwiz... well, they're getting their drink on.

For the rest of you that might be bothered by the extrabugginess that seems to be happening since 10/12... The last M release was 10/11, it happens once a Month (hence the M) and is expected to be a semi-stable release. The reason our patches had to wait a few days was because CM was in a soft freeze for the M release. Once the M was released, a whole slew of experimental stuff was committed. That means breakage (which you saw) and bugs (which you still continue to see).

For those that have supported and cheered me on, I do appreciate it. This wasn't a 6 day from release to official nightly. I've literally been working on this since I got my phone in April. The ICS sources were simply the last piece of the puzzle.

Thank you all.
[Samsung Galaxy S Blaze 4G] chrisxbell714:
I appreciate what you have done I never said I didn't, you have helped all us blazers, but is it so horrible that I got a little aggrevated when I updated and realized its worse, is it really that bad its not like I'm mad at you personally....I didn't expect it to be worse I was thinking it would be more stable, my expectations were too high and for that I am sorry. If I said something to offend you I apologize.

Sent from my CM10 Blaze
[Samsung Galaxy S Blaze 4G] shaikmonster:
This is a big omelet. Gonna break a lot of eggs before it is ready to eat. Report the issues, be polite, and give thanks.

We do this because it is fun. If not... go back to stock. Thanks dr4stic... Having lots of fun! Now go get some sleep.
[Samsung Galaxy S Blaze 4G] ggonsalv:
I couldn't agree more
[Samsung Galaxy S Blaze 4G] namaui:
Currently running the newest nightly, and it appears to be much more stable and a bit faster too. There is a bit of graphical funkiness going on with Youtube, but I can live with it. CM Updater works very well, just wish it would wipe cache partition and dalvik cache during the update for me, I had no network after many reboots until I wiped them. Thanks for the hard work, its really progressing nicely.
[Samsung Galaxy S Blaze 4G] strungoutfan78:
Im still on the 10/18 build and im having strange issues with Swype. Half the time my suggestions don't show and im stuck using whatever word Swype had suggested. This is fixed by switching input to standard android keyboard and then back to Swype, but it eventually reverts. Im using the ICS Swype apk. Anyone else?

Sent from a magical unicorn using CM10
[Samsung Galaxy S Blaze 4G] chjema:
Switch to Swipe Beta,
[Samsung Galaxy S Blaze 4G] dispozable:
Have you tried TouchPal? I put it in the apps and themes section if you wanna check it out. I like it a lot better than swype.
[Samsung Galaxy S Blaze 4G] johnb380:
SwiftKey 3 is the best
[Samsung Galaxy S Blaze 4G] strungoutfan78:
Yeah I really like touchpal but the word prediction is so bad it made me just want to throw my phone. If they fixed it I would use it for sure. Swype beta sure is nice though. Just wish it had the tasty blue ICS theme.:)

Sent from a magical unicorn using CM10
[Samsung Galaxy S Blaze 4G] dr4stic:
I'm fairly sure that the latest Swype (released just a few days ago) now has theming support. It was one of the "what's new" bullet points :)

Been a long time Swype user, love it.... and now because of you, I'm off looking for themes!
[Samsung Galaxy S Blaze 4G] sgolem:
I found out my problem. It was located between the phone and the seat. I followed instructions - but - I didn't format the internal sdcard partition. I suppose this boils down to me being scared to do so. I had a hunch that I should have, but after reading all the bricking storys abound on the internet I got nervous. The instructions I followed didn't mention this, so I played it safe. Ultimately though, it suppose it boils down to me being a noob :).

I want to post my fix, in case anyone else has this problem.

The way I fixed it was this. When I got brave enough, I connected my phone via usb to my computer in the clockwork recovery mod and reformatted the sd drive as a fat32, which was then accessible in windows. Then I did a wipe on the dalvik and cache, as well as the previously installed 2012817. I then installed the 2012818 nightly as normal. Bam. It works perfect. I mean, flawless. I fixed this 24 hours ago, and so far it hasn't even crashed once, anywhere. Even Apollo has been stable, despite previous reports. *crosses fingers*.

Basically, this mod rocks. Thank you so much for your hard work. I'm SO glad I was able to figure out my problem.
[Samsung Galaxy S Blaze 4G] Chitown021:
Ran into my first issue in several days while using the latest (10/19) nightly My phone froze up while receiving an incoming call. My phone was asleep when I heard it start to ring. It rang for about 2 seconds then went silent (screen never lit up). I hit the power button to try to wake it up and nothing. I couldn't even get it to reboot by holding down volume + power. Finally had to pull the battery.
[Samsung Galaxy S Blaze 4G] strungoutfan78:
Ok I have my first real issue now too. I'm cooking a batch of malt and hops for an amber ale and I have to boil them for 30 minutes. I used the countdown timer on my phone and it appeared to be working ok. I left the timer to use the browser for a few minutes. I then pulled down my notifications where it said I have a timer running with 17:47 left. Then I noticed it wasn't counting down so I tapped it. It brought me right back to the timer but my timer was gone. It had been reset and the notification still shows 17:47. Hope I don't screw up $50 worth of beer ingredients.:eek:

Sent from a magical unicorn using CM10
[Samsung Galaxy S Blaze 4G] jbats:
Just wanted to throw it out there the battery pull is only necessary in cases of loss of phone carrier services. Personally i hold the power button down for 5-8 secs performing a force shutdown. Currently running the cm10 10/20 build. Other than a few screen glitches when performing to many tasks at once, havent had a SOD or any freeze for that matter after !0/18 upgrade. Experience youtube screen flicker but not even worth mentioning. Great build, props to dr4stic for all your hard work!!!! Also the phone seems to enter deep sleep during long conversations and ive found shaking the phone(idk why) or pressing the vol up down buttons will wake it. Hope this helps. :):)

SGH T769 cm10
[Samsung Galaxy S Blaze 4G] dispozable:
First bug in a long time.... I lost call audio. Well...half of it. No settings have been changed for the last few nightlies, at least since 17. Strange as it worked most the night, then just suddenly denies me sound from calls. They can hear me but I cant hear a thing. No biggie though, just flashed the new nightly and it fixed. Did anyone else notice a sound level drop on build 20? Maybe I just got a bad audio book...
[Samsung Galaxy S Blaze 4G] Ltitus8900:
Hi. There is something that is pissing me off. I would like my phone to sync with my phone's external SD card. Or I would like to just get rid of or merge the one gig internal with the phone's internal storage so the phone will only see my actual SD card as the only SD card. Is this possible? If so how :(:(:(
[Samsung Galaxy S Blaze 4G] mdneilson:
This has been covered earlier in the thread. They will eventually get around to allowing the camera app to save to the external sd, but it is not a priority. There may be a way to use symlinks or bind mounting to do the same, give it a shot (bind mounting is better). Expanding /data is pointless, messy, and could affect the stability of the rom, just move stuff manually if you're getting low on storage.
[Samsung Galaxy S Blaze 4G] Ltitus8900:
Thank you very much for the quick response I appreciate it.