yashsingh1/xdaforums huggingface dataset:
[Moto X Q&A] plammos:
Hi, i have rooted my 4.2.2 Moto X Brazilian, and now we are receiving the upgrade to 4.4 Kit Kat, but i heard it will be a problem

How can i upgrade?

Thanks
[Moto X Q&A] flashallthetime:
Do not take the ota, wait for the sbf firmware and flash with rsdlite, I have seen and read more problems due to accepting an ota, patience my friend. No guarantee that you will have an issue but its better to be safe than sorry
[Moto X Q&A] kamikass:
SAme here, but what If I unroot via toolkit? Dangerous?
[Moto X Q&A] GoClifGo05:
If you have deleted system apps, flashed a custom recovery or things like that then either SBF back to the original 4.2.2 firmware or 4.4 when available. If its only root you can just take the OTA. It will kill root during the process.
[Xperia Play Q&A, Help & Troubleshooting] Lazka099:
can someone help me with this problem?

im using a ICS original + by dany XP...

here link http://xdaforums.com/showthread.php?t=2300843

well its doesnt affect with performance.. but still it make me worried sometime..

(already tried reboot and pull battery... no differen)
[Xperia Play Q&A, Help & Troubleshooting] Lazka099:
im just soft reset.. and it solved.. for now..

but after im reboot my phone.. my notice bar will goin missing again...

:confused:

now im really dont know how to fix this...
[Xperia Play Q&A, Help & Troubleshooting] Jecmenn:
If i get it right, sometimes your statusbar disappear. If yes it means that your SystemUI force closed. You can do only two things now. 1.) Try flash different SystemUI.apk. 2.) Reinstall ROM.

But please try to post more information.
[Xperia Play Q&A, Help & Troubleshooting] Lazka099:
ah yes... im sorry for my bad english...

well.. i think my systemUI is error? can u help me find systemUI compatible with my ROM now?

(well my status bar always disappear if my phone reboot.. try soft reset and it will show.. but after im reboot second time it will disappear...)

oh btw thank you for reply..
[Xperia Play Q&A, Help & Troubleshooting] Jecmenn:
Try this: http://xdaforums.com/showthread.php?t=2239625
[Samsung Galaxy S Blaze 4G] InkSlinger420:
mine....
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Just one more for good measure..
[Samsung Galaxy S Blaze 4G] lanrrydon:
THANKS

At last the official N. is here.. thanks ink.........for the hard. work..

:good:
[Samsung Galaxy S Blaze 4G] daboross:
I blindly installed this with CM updater not realizing that it was 11 not 10! I'll do a full wipe and reinstall soon, just noting that wifi doesn't turn on now though a reinstall will fix it I bet.

Awesome work!
[Samsung Galaxy S Blaze 4G] tommyboy8125:
Yea I noticed the same thing, if you do a dirty flash or even just restore data from 10.2 it breaks the WiFi. Everything else works great.
[Samsung Galaxy S Blaze 4G] micl9:
LOL X3. Full wipe,reinstalled and all is good. Awesome work Ink!
[Samsung Galaxy S Blaze 4G] Chitown021:
Awesome! Wish I had noticed this was up before I left the house and my WiFi behind... oh well, will flash after work.
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Good morning everyone..Glad to see some have found the new thread already today..:D
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Incase anyone curious..if there was any issues upgrading the nightly, check android version number in about phone..its now 4.4.2...I have also noticed that after updating with cmupdater, after the flash, one should boot into recovery by button combo and wipe cache and dalvic before allowing to boot..seems to help with any issues..
[Samsung Galaxy S Blaze 4G] tommyboy8125:
I'll try that later and see if it fixes the broken WiFi after updating.
[Samsung Galaxy S Blaze 4G] blazetim:
The youtube app no longer works on the newest build. Anyone else having issues with it? Says cant connect touch to retry. Worked fine before
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Are you using an adblock app?

Edit: Mine works fine but then again, I flashed the 4.4.1 minimal gapps from slim last night..Either way, YouTube is a Google app..not built into the ROM..so the bug lies there (if you aren't using a adblocker..because that DOES interfere)..
[Samsung Galaxy S Blaze 4G] blazetim:
no ad blockers. i tried re-installing and tried different modems and still nothing. Went back to the 12-10-13 rom and it works again. I dont get it
[Samsung Galaxy S Blaze 4G] InkSlinger420:
I don't either..but it won't be the modem..but the update has changed a few things..try the slim gapps package I posted in the other unofficial thread if ya want to..again..its a Google app..
[Samsung Galaxy S Blaze 4G] blazetim:
is the slim one the one on the first page? I am currently using your kk version gapps
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Its here

http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/978-addons4-4/downloads/dlsearch

Choose slim or full..
[Samsung Galaxy S Blaze 4G] dirty_s0ciety:
I know I couldn't possibly be crazy but while I was using my phone...pie controls popped up and I don't know how to do iy..is it enabled in this ROM?

Sent from t-769 running 4.4
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Was it pie or Nav ring? I don't believe pie is enabled in it..maybe wrong..but if it was I assume we would have an option in settings..
[Samsung Galaxy S Blaze 4G] dirty_s0ciety:
[MENTION=5190980]InkSlinger420[/MENTION] it was pie controls but i can't seem to find it in the settings

Sent from t-769 running 4.4
[Samsung Galaxy S Blaze 4G] nmccord:
Google now is great and is part of the kitkat experience
[Samsung Galaxy S Blaze 4G] njstein:
If I remember, right, there is an option to turn off Google Now in the settings, bottom right within Now. The persistent Search bar has no off switch. So two options: 1) Use Apex or Nova Launcher, they both have the option to turn off. Of course, then you're using that launcher and not GEL. 2) Use Titanium to freeze Google search.
[Samsung Galaxy S Blaze 4G] iamlazy:
Or you can install minimal gapps and use launcher3 which has an option to turn the search bar off and doesn't have an always running google now listener.
[Samsung Galaxy S Blaze 4G] K3NN3Y:
Worked

Thanks, worked like a charm. :D
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Thanks guys for helping out...Been a bit busy today with some "projects"..
[Samsung Galaxy S Blaze 4G] Jserrano56:
Ink, I sent 3 more logcats while using the speakerphone during video chat they're all from 4.2 but the speakerphone was working 100% no mic issue or muting

Edit: do you want me to flash 4.4 to compare the logcats?
[Samsung Galaxy S Blaze 4G] Sigma47:
whoa dude, thx for the lecture dad. get a tat and take a 420 break. I've been flashing nightlies since "jesusfreak" ROMs on the HTC magic and have bought multiple cases of beer for the devs on all the devices I've owned. You haven't got coin from me bc I have never used any of your work. In my prior post I was confirming a bug report that another user had initially posted. My post was simply meant to suggest that the bug was real and not an isolated incident as a result of the other user's config. . I use BT daily and in my exp on xda over last 5 yrs have found many devs do not and for that reason I believe BT issues are often last fix, if ever, on ROMs. Back to CM10... maybe its time for a new phone.
[Samsung Galaxy S Blaze 4G] ohgood:
Not cool, not cool at all. If you read the Devs comment and took offense, you need the 420 break. Follow the thread, thus is one of the most relaxed, easy going Devs out there.

Happy New Year
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Truly surprised you got bent..(even more surprised it took you 3 days to think that up..).I'm not gonna feed the trolls so you are welcome to rollback to whatever ROM ya came from and go be a smartass over in their thread..
[Samsung Galaxy S Blaze 4G] Sigma47:
Hey I'm no troll buddy... your prev response was laden self importance and condescension. I was simply stating some behavior that I observed and there seemed to be some confusion as to the functionality of BT (you yourself, as I suspected, don't use it) and you got all "poor me I do this for free" idk I wasn't complaining bout the ROM was just noting an issue and YOU appeared to have taken some offense from that. Next time I'll keep hush and let you field questions about Google now... bc that's a dev
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Again..it should be a dropped issue (the one you keep whining about)..If you took what I said a little on the chin..then YOU need to relax..And I see that you say you've been doing a BUNCH of flashing and donating..(blah blah blah), Then why you rocking 6 thanks..? Sounds like a troll to me....Let's clean it up in here..or your welcome to leave..and a GOOD dev monitors his DEVELOPMENT thread and helps wherever he can (with your snippity Google now comment)
[Samsung Galaxy S Blaze 4G] InkSlinger420:
If you would...that would be great..I have nothing to compare it to..;)
[Samsung Galaxy S Blaze 4G] dsulliii:
Excellent and Superior

InkSlinger420, this is all-too-late in the coming, and I only wish that I'd been following you much earlier to provide you some encouragement. I am VERY slow to upgrade. This is the FIRST time I've ever been brave enough to flash a NIGHTLY. And I did it ONLY because of what I've been seeing in your development. Yeah, there's a few things not working, and even some from quite a while back. But those are minor in comparison to how awesome this ROM is. I just flashed the 12/28/2014 NIGHTLY yesterday and am totally loving it. I want you to know that you have an outstanding public presentation and you are to be congratulated for maintaining your composure as well as you do. Your technical skills match right up there with your personality. KUDOS!

Bluetooth -- don't use, never have, probably never will.

Speakerphone -- would really like to see it 100% perfect. I'd be glad to provide anything that I can to you in order to help you out. I have a smidgen of technical prowess and a lot of willingness to take chances since I can usually recover from any disaster.

Camera scanner apps -- yeah, a REAL big one for me. As with the speakerphone, if there's ANYTHING that I can contribute to help you nail those down, then feel free to ask. As much as I rely on them, though, this ROM's quality surpasses the effect on me of no-longer being able to scan barcodes. I just do them WITHOUT this phone <grin>.

I'm a fair guinea pig. If you need me to take a chance for you, I will. Just let me know.

-- David
[Samsung Galaxy S Blaze 4G] Jserrano56:
I'll try to get logcats tonight probably won't be able to until tomorrow tho, but my only question is since speakerphone won't work since it mutes the mic in a phone call, why is it different in the case of video chatting where it does work in 4.2?
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Thats a fantastic question.. And take your time with the logs.. I have a few things going on as well
[Samsung Galaxy S Blaze 4G] xWolf13:
And you too Ink! Take your time. :D
[Samsung Galaxy S Blaze 4G] Jserrano56:
Happy New Year Everyone!

[MENTION=5190980]InkSlinger420[/MENTION] I'll have the logcats some time within the next 2 days, just curious do you have a logcat of working speakerphone as in like a phone call? Or do I need to flash CM10 and get a logcat of that too so we can compare logcats and see what was changed or what broke between builds?
[Samsung Galaxy S Blaze 4G] InkSlinger420:
I have working..I need error log...
[Samsung Galaxy S Blaze 4G] JetSquad:
Camera Bugs

I recently upgraded from cm10 to cm11. It works pretty good! There is a slight issue I've notice tho. Recording video on the back camera and front facing camera don't work with the default app. It will freeze for a few seconds then start the timer as if it was recording but when you hit the recording button again to stop it the video does not exist anywhere. I checked the gallery and the default location for recordings. Instagram also wont record in the app or process video on this rom when choosing from the gallery. Snapchat does work(with pictures and recording videos) with the front facing camera but not the back doesnt work(when recording video). Sorry for all the specifics, I'm not sure what would help and what wouldn't. Thats the only thing I've come across that doesn't work :( , besides what you've stated before. Its a very good rom tho! :good: :D
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Yep..the videocamera is dodgy..as well as the regular camera..its a known issue and actively being addressed..glad to know you like it otherwise though..
[Samsung Galaxy S Blaze 4G] phenomejohn:
Here, use the Google Play edition camera apk: http://www.androidauthority.com/stock-android-camera-apk-photo-sphere-236196/

Works for recording video after a 2-second pause. Just uninstall the default Gallery app before trying to install this apk.
[Samsung Galaxy S Blaze 4G] Jserrano56:
[MENTION=5190980]InkSlinger420[/MENTION]

Sent 4 logcats

Noticed a new problem details are in the email
[Samsung Galaxy S Blaze 4G] InkSlinger420:
[MENTION=4935978]Jserrano56[/MENTION]

Just looking them over..thanks man:thumbup:
[Samsung Galaxy S Blaze 4G] Jserrano56:
For everyone complaining about Bluetooth, its fixed and it might not even have been broken to begin with, first time I used it on CM11 and it successful paired with my car and worked
[Samsung Galaxy S Blaze 4G] dledwith2:
Could you elaborate on what you feel is fixed and what nightly fixed it? I'm not a regular bluetooth user so I haven't experienced any problems. I wouldn't mind taking a look at your logcats if you found something helpful in there.
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Bluetooth has never been an issue with me, on any rom that uses cm as its base, being as ANY rom I build, I use CMs device files(which BT has not been touched as far as I am aware),ie. SLIM,PAC (which I officially maintain) and CM ofcourse. It may be BT device specific but I test BT with my wireless mouse as I dont have a headset, and it always connects fine..
[Samsung Galaxy S Blaze 4G] Jserrano56:
January 2nd nightly and if you want logcats of me running bluetooth I can provide some? And I didn't encounter any bluetooth issues other uses reported issues with bluetooth
[Samsung Galaxy S Blaze 4G] centenj:
All of a sudden I'm having call issues. Just updated to the 010214 nightly.
[Samsung Galaxy S Blaze 4G] alphasurfer:
I'm getting pop-ups saying out of network, or errors saying phone.apk not available at times or something like that!
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Have we full wiped before flashing lately to ensure residual changes are gone? Should be done before reporting issues (not intended to sound rude)..and sometimes cm pushes changes late in the build cycle which can botch a few things..Not saying that's what happened, but please, anyone who uses nightlys regularly, please full wipe and reflash clean before reporting bugs..that way I know what we are working with..thanks guys.
[Samsung Galaxy S Blaze 4G] lcalin77:
I'm having the same problem (12/31/13) plus 1:sometimes when I try to make a call, after I press send, it's going to the home screen and I can't return to dialer screen, can't hang out the call until the the other party hangs up. 2: when I receive a call (not all the time) I hear the ring tone but my screen won't come on and I can't answer the call, only after pressing power button few times I am able to answer the call if they didn't hang up already.

Thank you.
[Samsung Galaxy S Blaze 4G] InkSlinger420:
[MENTION=4935978]Jserrano56[/MENTION] I have called in backup and we are actively working on the speakerphone issue..Just a heads up..
[Samsung Galaxy S Blaze 4G] alphasurfer:
I always do a clean full wipe etc, and as quoted above i also have the screen issue when receiving a call it wont come on! I understand the need to remind people of doing a full wipe. Thanks again :)
[Samsung Galaxy S Blaze 4G] alphasurfer:
this is one of the popups!
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Alright guys, Flash back to a build where it didnt occur while i look into it..itll probably be fixed itself in the next day or so.. ;)
[Samsung Galaxy S Blaze 4G] Jserrano56:
I noticed that too, I gave ink a logcat about the problem I noticed.

But I'd do what he suggested just flash back to the previous nightly where you didn't encounter that problem.
[Samsung Galaxy S Blaze 4G] dledwith2:
I've had the black screen when phone is ringing issue for a while now too but it doesn't seem to be on every call.

Are the logcats erased on the installation of every new rom or do they accumulate to a set size?

I noticed that the recovery was bumped to 6.0.4.6 in the rom changelog. How do I get a copy of this to flash?
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Samsung Galaxy S Blaze 4G	6.0.3.8	6.0.3.8 (as official CWM site goes, thats the latest,other devices HAVE been bumped up) ie. http://www.clockworkmod.com/rommanager

Logcats are removed on clean flash.. and the black screen is a wakelock bug that is hit or miss on 4.4..

Philz has an updated version of his touch for 4.4..Just read the thread..http://xdaforums.com/showthread.php?t=2461823
[Samsung Galaxy S Blaze 4G] dledwith2:
Yeah I saw that on the clockworkmod site, that's why I asked. What is the relationship between cyanogenmod and clockworkmod? Are they one and the same?

Since getting on the nightly train, I haven't done a clean flash, just downloading and installing the new rom from within the current rom. So whatever that does automagically. Before flashing the first nightly, I formatted, /system /data /cache and wiped dalvik cache. I may have even run that black hole tool mentioned earlier in the unofficial thread.
[Samsung Galaxy S Blaze 4G] InkSlinger420:
As far as relationship goes.. http://answers.yahoo.com/question/index?qid=20120416174428AAuhZHo

and logs run in a circular buffer..They dont stick around unless you logcat em

http://developer.android.com/tools/help/logcat.html
[Samsung Galaxy S Blaze 4G] Jserrano56:
Not asking for an ETA

But anything stand out (I mean as in something obvious shouting: HEY! LOOK AT ME! IM THE PROBLEM! FIX ME... lol) in the logcats?
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Yep..there is..but now uber and I get to try to figure out why..;)
[Samsung Galaxy S Blaze 4G] Jserrano56:
Good luck, since I have a new Kindle Fire HD 7 I now use that to Video Chat so CM11 is staying on my phone (daily driver) so I'd you need logcats or anything let me know.

Btw love the rom! CM11 runs smoother on my phone than it does on my tablet, still exploring the rom and features tho.
[Samsung Galaxy S Blaze 4G] InkSlinger420:
There's a slim ROM and my PAC 4.4 are fixing to drop as well (now that camera and speaker don't matter;) )
[Samsung Galaxy S Blaze 4G] osbaldov:
Does anyone have a problem where there is no 4g lte option on networks or is it just me?
[Samsung Galaxy S Blaze 4G] Jserrano56:
Ink, no disrespect or anything but battery life... Should it be this bad? I know it's not the battery, I have 2, and I was getting at least 9/10 hours on 4.2?
[Samsung Galaxy S Blaze 4G] taodan:
To have LTE, the radio must support it and the ROM is not ported for LTE

Sent from my Galaxy S Blaze 4G
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Dialer code: band select *#2262# Automatic, WCDMA, GSM, LTE .... band preferences

(should getcha up..But CM doesnt recognize 4g/LTE as icon ,I believe. Itll be H or H+(HSPA) )
[Samsung Galaxy S Blaze 4G] InkSlinger420:
This is NOT true. CM DOES support it. Its just not an option in the screen as most of the time it is defaulted 4g..The other options are more for low coverage/ battery saving options..You are correct about the radio,though most radios for the devices we use (or borrow) are 4g/LTE.
[Samsung Galaxy S Blaze 4G] InkSlinger420:
No, Thats not normal..What the hell do you have sucking up SDcard time? Thats MASSIVE..And/or, whats your daily usage? (ie. apps,streaming,PLEASE GOD NO FACEBOOK,LOL....)
[Samsung Galaxy S Blaze 4G] Jserrano56:
I'm using my phone like I did in 4.2, I'm a moderate to heavy user, and I'm clueless as to what using all the SD card time? Umm I'll flash a newer nightly tomorrow
[Samsung Galaxy S Blaze 4G] champ784:
I saw that some people were having issues with their network settings... I did too! My data would go on and off for a while... Eventually, I just messed around with the network settings... Idk how, but my phone was set to automatically use the MetroPCS network instead of T-Mobile... I switched it back, and it's back to normal now... It was after updating from one nightly to another

Sent from The Blaze of The Doctor
[Samsung Galaxy S Blaze 4G] InkSlinger420:
I was gonna suggest checking APN settings as well [MENTION=5290269]champ784[/MENTION] ..good call..
[Samsung Galaxy S Blaze 4G] osbaldov:
Thanks guys solved my problem! :thumbup::thumbup:
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Awesome..glad your back up..

The thanks button works too...;)
[Samsung Galaxy S Blaze 4G] minkmendor:
I cant get past the nightly version from 12-30-13 if i want to make phone calls. every nightly after that either crashes the app or the signal drops down to zero and call fails. This has been tested with fresh installs (wiping cache partition, dalvik, and factory reset). This version im on now , the 12-30-13 was working good until the wireless stopped working :/. any help would be appreciated!
[Samsung Galaxy S Blaze 4G] Jserrano56:
The solution is literally a couple post like 4 or 5 above yours... Under APN it's set to MetroPCS change it to T-Mobile
[Samsung Galaxy S Blaze 4G] minkmendor:
I Already did that. This setting was also set to MetroPCS on previous versions. The call's still fail and the app crashes as well when on the Tmobile.
[Samsung Galaxy S Blaze 4G] Skywalker.00:
I thought the telephony bug was just me... It exists in my Beanstalk. Good to know. Looks as though a fix is being merged, though.

http://www.cmxlog.com/11/t769/

---------- Post added at 01:22 AM ---------- Previous post was at 01:21 AM ----------

So give it until next nightly or the one after. Should be good to go ;)
[Samsung Galaxy S Blaze 4G] InkSlinger420:
As CVD said over on the exhilarate thread..cm has a madhouse of msm8660 kernel tweaks being worked on and many things ,(camera bugs and such) being worked on in overtime right now..the next few nightlys for both our devices may be hit or miss until things get settles in..

Edit: Uber and I are in cahoots to get this speakerphone bug worked out..that's first on OUR device specific bug list.
[Samsung Galaxy S Blaze 4G] dsulliii:
1/5/2013 still looking good

Info only (positive): I upgraded to cm-11-20140105-NIGHTLY-t769.zip and it is running every bit as beautifully and smoothly as its predecessors. For the first time, however, I did have a dialing/calling problem. It was a "force close" error, so I was going to try to reproduce it with a clean start. I cleared the cache on the dialing and phone apps, and then I performed a CWM-recovery clean cache partition. I rebooted into the OS and then could not reproduce the error. In fact, my speaker phone is working excellent in this build as-well-as both the phone and dialing apps. It seems odd that I do not experience as many problems as some of the responders do because I tend to tinker a bit and would be a very likely candidate for problems. I'm very happy with the work you're doing on this and the progress you are making. Oh -- camera -- seems to work excellent as well.

So if you find yourself in a spot of needing to see why somebody else's is not working but mine does, just let me know what I can provide to you in order to help out.

-- David :cowboy:
[Samsung Galaxy S Blaze 4G] InkSlinger420:
So your saying speakerphone and videocamera are up for you now? We have all been working hard on getting those dialed in..and a lot of progress has been made in the last few days..