yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] sader2202:
Question here: since this is out, does this mean PA on Android 4.2.1 is close?

Hallowed Is The Sader
[Samsung Epic 4G Touch] Big Boy Laroux:
What is Desk Clock? Is that just "Clock" in the app list?

I flashed from CM10 to CM10.1 and just wiped cache and dalvik. Not seeing any issues, but wondering about this Desk Clock wipe.
[Samsung Epic 4G Touch] dastin1015:
I forgot about the ringer patch. I have it included for my next build.

Awesome! Haha idk about that.

I might be working on PA for the Evo 3D and E4GT after I get camera working on the 3D.

Desk Clock is the clock app. Wipe the data for it. The app has changed between 10 and 10.1 in such a way that it will FC unless you do.

私のEVO 3Dから送信される。
[Samsung Epic 4G Touch] Big Boy Laroux:
I asked this earlier, and am really interested to know the answer:

On Touchwiz (and in some market apps), you have the ability to store pictures directly to the external SD when taken. This feature is not available in the standard camera on CM10 or CM10.1.

Is this something related to the ROM, or to GAPPS?
[Samsung Epic 4G Touch] jlear3:
I'm sure if you go into system settings to advanced settings and then to the storage tab you can set the primary sd card. Internal or external
[Samsung Epic 4G Touch] Master_Ellis:
Holy Beef Jerkey 4.2.1 on the Epic4GTouch!

About to flash just wondering is the media server battery drain issue present in this ROM?
[Samsung Epic 4G Touch] Big Boy Laroux:
Sorry, i also meant to include that I know about this option you mentioned.

What I mean is a setting in the camera app itself that does not base off of the set storage.

I personally prefer to use internal SD for Apps (lots of space there) and external SD for media (videos, pictures, etc).

However, with the setting you mention, it is EVERYTHING (apps, pictures, etc) to either internal or external.

Camera ICS+ (and the stock touchwiz camera app) allow for the picture/recorded videos to be stored to the external SD, even when apps/downloads go to the internal SD.

Hope that makes sense.
[Samsung Epic 4G Touch] vanberge:
For me I have been getting awesome battery life.

It slept deep...

12 hours, 30 mins.

1 hour 25 min screen time.

Still over 50 % battery.

That's with 2x flashes of new versions as well.

...EDIT - SCREENIES...
[Samsung Epic 4G Touch] Master_Ellis:
Thank you

Cool Beans.

---------- Post added at 10:44 AM ---------- Previous post was at 10:36 AM ----------

I have the paid version of Camera ICS + and I can comfirm it allows storage to micro sdcard. I can live with usimg two camera apps :)
[Samsung Epic 4G Touch] Big Boy Laroux:
Yes, I have Camera ICS+ as well (which is how i know it can save direct to SD). :)

I REALLY like the new interface of the stock 4.2 camera, so was curious about adding that "save to SD" feature. I can live with either using Camera ICS+ or with moving media periodically if I use the stock camera, so not a huge deal. Was really just curious about where the feature would have to be added (ROM or GAPPS).
[Samsung Epic 4G Touch] Noan21:
I flashed a safe recovery, when I tried to flash the ROM i got an error about format() expects 4 args, got 5

Guessing I need to flash something else?
[Samsung Epic 4G Touch] vanberge:
Are you coming from a stock based JB build?

Those builds have an extra partition in them - I wonder if that's what's doing it.

If I were you, I'd back up my stuff (nand, titanium backup, etc) then I'd do a one of the one-click stock builds (FI27 is what I did).

Then I flashed the EL26 CWM kernel via odin.

Wiped data/factory reset

Installed his rom

installed gapps.

..edit..

also make sure you check the md5 to make sure it's a good download
[Samsung Epic 4G Touch] graffix31:
There is also a jelly bean wipe all script that tdunha, put together that is supposed to wipe that other partition. that might help.it is in the development section.
[Samsung Epic 4G Touch] Croathlete:
Re: [ROM] CyanogenMod 10.1 - WILD FOR THE NIGHT - Feb, 6, 2013

There's actually a menu option to fix permissions in the advanced menu of the recovery.
[Samsung Epic 4G Touch] skylenorman:
Went with the clean flash to 0206 that everyone recommended and now I can't connect to the GServers. I've got nothing but grey signal bars all the live long day.

EDIT: Used the methods described in this thread and was able to fix it. http://xdaforums.com/showthread.php?t=1541266
[Samsung Epic 4G Touch] JamesEh408:
I can't take it anymore! DLing now.

Thanks
[Samsung Epic 4G Touch] MattMatt0240:
Re: [ROM] CyanogenMod 10.1 - WILD FOR THE NIGHT - Feb, 6, 2013

Reboot recovery> advanced> fix permissions.

Just trying to help bro, just felt my first post was thorough enough.

Or you could use root explorer and manually fix permissions of the apk that is FC'ing, but that's a little more advanced.
[Samsung Epic 4G Touch] keithatoz:
I didn't detect any smart-assery! He stated in the post a couple of pages ago how to fix it, and I can verify it works. Reboot your phone into recovery, go to Advanced, and then Fix Permissions. After it finishes (takes a couple minutes) reboot and see if things are better.
[Samsung Epic 4G Touch] MarcAntonyy:
Just an update to this in case it happens to anyone else (google.process.gapps FCs).

I ended up trying this and the other posted solution and a few others (there's a lot of fixes posted across all the Android forums about it that work for some, but not others), but ultimately was banging my head on the desk.

Fortunately the phone decided to help me out and give me a clue. I got a "Permission requested: please sign into google" notification out of nowhere and it triggered the thought to fix permissions in recovery. I wiped cache/dalvik once more and then fixed permissions and the problem is now gone.

So at least in this case, that's all that was needed (permissions).

Edit: I now see someone else addressed this issue since my originally posting it, so yeah, if this happens try to fix permissions first.
[Samsung Epic 4G Touch] Phobophobia:
Thanks for the recommendation, I'll try this out.
[Samsung Epic 4G Touch] thelead:
Super weird one time issue with the 2/6 build. My wife calls, I pick up, say hello a few times and hang up because I don't hear anything. She calls back and says that a woman picked up, said hello and hung up. My wife has the 1/31 build on her phone. I have never had that happen before.
[Samsung Epic 4G Touch] thedarksavant:
You shouldn't let your mistress answer the phone ;)
[Samsung Epic 4G Touch] elzero26:
lol. Best excuse ever! J/K
[Samsung Epic 4G Touch] EmperorX:
Re: [ROM] CyanogenMod 10.1 - WILD FOR THE NIGHT - Feb, 6, 2013

The xda app freezes randomly without doing anything else. In fact it just happened to me for the third time this week..

Also you don't have to pull the battery when I hard locks. Just hold power for 10 seconds it will force a reboot.
[Samsung Epic 4G Touch] Aganar:
Re: [ROM] CyanogenMod 10.1 - WILD FOR THE NIGHT - Feb, 6, 2013

Good advice here. I wouldn't say perfect, as I'm still not getting metadata, but the audio is smooth and that's what matters. Will be staying on this build until things improve.

Sent from my CM10 Epic 4G Touch
[Samsung Epic 4G Touch] gamepro602:
Re: [ROM] CyanogenMod 10.1 - WILD FOR THE NIGHT - Feb, 6, 2013

Well... what I did is I deleted the Apollo apk from the system, rebooted the phone, and installed a another Apollo apk from the web:)

Heres the thread where I found it:

http://xdaforums.com/showthread.php?t=2076161
[Samsung Epic 4G Touch] Cipherblox:
I'm working on tracking down the keyboard overdraw bug. This is the bug where, when a user presses a key, fragments of previous key presses are shown along the edges of the preview.

I need someone to confirm some things for me though...

1. Confirm that pressing a key for the first time does not generate any overdraw in the above manner. However, pressing an adjacent key after the first key does generate the overdraw.

2. Has anyone ran into this issue on other 4.2 Jellybean builds for our phone? Or just this particular version of CM10.1? (<-Hopefully this isn't the case as everything would get substantially more complex)

Thanks,

-GP
[Samsung Epic 4G Touch] deaver_92:
Re: [ROM] CyanogenMod 10.1 - WILD FOR THE NIGHT - Feb, 6, 2013

A couple weeks ago someone was asking about getting into *#*#3282#*#* but after entering the msl it gave a "modem exception occurs" error. Didn't see any follow up on that. Anyone know how to get around that? Or if not then a way to edit the proxies? Thanks!
[Samsung Epic 4G Touch] Big Boy Laroux:
Re: [ROM] CyanogenMod 10.1 - WILD FOR THE NIGHT - Feb, 6, 2013

For #1, it does appear to be how you bare describing. Only does the overdraw if you press a key next to a key you had previously pressed.

No clue on #2
[Samsung Epic 4G Touch] agentsmith988:
I can confirm on the first keypress that there isn't any overdraw. But after that, it's crazy town. This is the first JB rom that I've had this issue with. I bypassed the issue by installing a LatinIME.apk (extracted copy of a stock JB keyboard iirc) that I pulled from another thread and then setting it as default. A little messy, but it works.
[Samsung Epic 4G Touch] Cipherblox:
First off, thanks to both of you for the testing.

I have to admit.... I didn't expect that response. The problem doesn't reside in the LatinIME.apk, but in the compiled ROM? I had heard of this happening on the GT-i9100 as well as our ROM, so I thought it may be affecting CM wide. No wonder I have yet to find anything wrong in the LatinIME source code...

Well I'll keep searching. Dastin, do you have any ideas? Is there a particular compiler flag you have set that may be messing with one of the destroy() functions?

Here is the GT-i9100 thread describing the problem: http://forum.cyanogenmod.org/topic/63976-cm101-bug-with-the-stock-keyboard/
[Samsung Epic 4G Touch] aaa12585:
I use Google Chrome as my default browser and I disable the stock internet browser. I find that Chrome will stop responding and I have to completely end the process in order for it to work again. It happens whenever I go to google.com, make a search, and try to re-adjust an already queried search. The keyboard will pop up and completely freeze the app. This does not happen within Chrome's built-in google search, only the search bars within the website. I am running 2/03 build and I'm not sure if this re-occurs in the newer builds.

Oddly enough, it seems to happen on some video site too (Through Chrome), whenever I'd try to use the search function through the website, the keyboard would pop up and, once again, freeze Chrome.

Either way, the issue seems to occur when using search functions that are integrated with websites. Anyone wanna throw a guess as to why this happens? I would test more thoroughly, but I wanted to post this just in case there is already a fix in the newer builds...

Will edit/update if I find something new.
[Samsung Epic 4G Touch] 0.0:
quick question: with GPS on, when going into maps, facebook, or any type of app that requires aGPS data to be downloaded, does your phone soft reboot?
[Samsung Epic 4G Touch] Phobophobia:
No. I did a clean flash to 2/3 and then dirty to 2/6.
[Samsung Epic 4G Touch] dastin1015:
I don't touch compiler flags. I only modify device repos and add in cherry-picks
[Samsung Epic 4G Touch] drilus:
Re: [ROM] CyanogenMod 10.1 - WILD FOR THE NIGHT - Feb, 6, 2013

Same thing happens to me. Very weird. Lol. Chrome locks up the exact same way.

I haven't found a fix.
[Samsung Epic 4G Touch] aaa12585:
Yeah, I have reason to believe it's the keyboard since it tries to pop up when I want to do the searches...
[Samsung Epic 4G Touch] EmperorX:
Re: [ROM] CyanogenMod 10.1 - WILD FOR THE NIGHT - Feb, 6, 2013

Use Chrome beta.
[Samsung Epic 4G Touch] NineInchNails:
Very Special favor to ask of someone here for our buddy Dastin :)

If you feel up to the task... PM me for details please. Senior member preferably that's been on XDA here for awhile.
[Samsung Epic 4G Touch] kobester:
Battery issues on 2/6

Early in the morning of the 7th I flashed 2/6 and then headed to bed. The next day I noticed that the battery performance was lower then normal. I thought it might of been the rom settling. Although today there was no change either. I unplugged the phone at 9 a.m. and went about my day. I made three short phone calls, read some news stories, listened to music, and did some very light texting. Most of the day it was in my pocket doing nothing. Anyway after 12 hours and 30 mins with a little over an hour screen time it is at 19 percent. I noticed in BBS that almost all of the awake time was for 200 mhz at 4 hours and 37 mins. With the rest being taken up by 500 mhz at 31 mins and 800 mhz at 31 mins. I'm attaching screenshots of the zoomed in battery usage screen, screen battery usage, BBS at CPU states since unplugged, and a main shot of the battery usage screen at 15 percent because I forgot to take and upload it when I did the others. Hopefully that helps with diagnosing the issues.

Also I'm running this rom on my SCH-R760 (US Cellular) after flashing a zip to convert it to work for my phone and network. It is using the ondemand governer which should be the stock one. I have not flashed any of exit_only's tweeks. This was a dirty flash from 2/3 the clean flash was the first release, perhaps it's time for another clean flash. I'm still a nublet when it comes to most of this so if you need more info let me know. Also if you dislike big blocks of text like the one above, sorry.
[Samsung Epic 4G Touch] EmperorX:
Re: [ROM] CyanogenMod 10.1 - WILD FOR THE NIGHT - Feb, 6, 2013

Disregard
[Samsung Epic 4G Touch] dastin1015:
Update relased! See changelog for details. Enjoy!
[Samsung Epic 4G Touch] tekanina:
Re: [ROM] CyanogenMod 10.1 - WILD FOR THE NIGHT - Feb. 8, 2013

In recovery go to advanced and go to fix permissions
[Samsung Epic 4G Touch] 0.0:
Re: [ROM] CyanogenMod 10.1 - WILD FOR THE NIGHT - Feb. 8, 2013

My friend is on cwm 6.0.2.7, and when I dirty flash this ROM, the com.android.phone process and systemUI force closes. Why is that?

Sent from my Nexus 4
[Samsung Epic 4G Touch] MattMatt0240:
Re: [ROM] CyanogenMod 10.1 - WILD FOR THE NIGHT - Feb. 8, 2013

Dalvik cache got moved, this has been discussed a few pages back. Reboot into recovery and fix permissions to resolve this issue. Recovery>advanced>fix permissions>profit
[Samsung Epic 4G Touch] 0.0:
Re: [ROM] CyanogenMod 10.1 - WILD FOR THE NIGHT - Feb. 8, 2013

Oh man...I full wiped my friend's phone. Lol. Telling him this, he will wanna kill me :p. I had to ask, because of the next update

Sent from my Nexus 4
[Samsung Epic 4G Touch] MattMatt0240:
Re: [ROM] CyanogenMod 10.1 - WILD FOR THE NIGHT - Feb. 8, 2013

Lol, on a more positive note, there's nothing better than a clean install :D
[Samsung Epic 4G Touch] 0.0:
is there a way to make my windows computer to recognize the phone with this ROM? for some reason, it can't. i have the drivers installed.

however, with another SGS II that a friend has that is not rooted and has touchwiz, my computer recognizes it. :confused:
[Samsung Epic 4G Touch] MattMatt0240:
Re: [ROM] CyanogenMod 10.1 - WILD FOR THE NIGHT - Feb. 8, 2013

Make sure development options are enabled (read OP) then check USB debugging
[Samsung Epic 4G Touch] guitar112232:
Do we have to fix permissions every time we update to the newest build for now on?
[Samsung Epic 4G Touch] Cipherblox:
No - only if you are flashing from a build prior to the Dalvik Cache moving to after the Dalvik Cache moving.
[Samsung Epic 4G Touch] themisterwilson:
Re: [ROM] CyanogenMod 10.1 - WILD FOR THE NIGHT - Feb. 8, 2013

When did it move?
[Samsung Epic 4G Touch] snakecharmer23:
Post number 2 on page 1 of this thread has your answer.
[Samsung Epic 4G Touch] kiswa:
In case anyone else encounters this; note that you cannot skip ahead to 2/8. First install 2/6 to get the needed changes, then fix permissions and reboot recovery and you can install 2/8.

At least, that's what worked for me.
[Samsung Epic 4G Touch] BronsonBohnet:
Re: [ROM] CyanogenMod 10.1 - WILD FOR THE NIGHT - Feb. 8, 2013

Still no MMS, 4G fix for me. I'm running modem FL12 RUNNING virgin Mobile.
[Samsung Epic 4G Touch] EmperorX:
Re: [ROM] CyanogenMod 10.1 - WILD FOR THE NIGHT - Feb. 8, 2013

I never fixed a thing... I did flash them in order but i never fixed permissions and dont have any fcs.
[Samsung Epic 4G Touch] gg_99:
I'd be interested in official word on this. This was a busy week for me so I'm in a position to want to skip 2/6.
[Samsung Epic 4G Touch] Cipherblox:
After looking through the source for the LatinIME keyboard (and getting my Official CM Bug Report shot down), I'm wondering if there is any benefit to forking from the CyanogenMod/android_packages_input_LatinIME and building it from your Team-Hydra Repo, Dastin. Shouldn't make a difference since you aren't adding any changes and committing, but worth a shot.
[Samsung Epic 4G Touch] SgtMacabre:
uuummmm......YAY!!!!!!!!!!!!! I've missed you Dastin!!!
[Samsung Epic 4G Touch] Big Boy Laroux:
Re: [ROM] CyanogenMod 10.1 - WILD FOR THE NIGHT - Feb. 8, 2013

Yep, me too. No issues. No FCs and never had to fix permissions.
[Samsung Epic 4G Touch] deaver_92:
Re: [ROM] CyanogenMod 10.1 - WILD FOR THE NIGHT - Feb. 8, 2013

What issues did you encounter from skipping 2/6?
[Samsung Epic 4G Touch] :
Re: [ROM] CyanogenMod 10.1 - WILD FOR THE NIGHT - Feb. 8, 2013

Flashed the latest build. My menu key rarely phantom presses now. It was really bad before. O.o
[Samsung Epic 4G Touch] theguz4l:
Is there a way to disable Battery LED when it is at 15% battery or so?
[Samsung Epic 4G Touch] dschachm:
Re: [ROM] CyanogenMod 10.1 - WILD FOR THE NIGHT - Feb. 8, 2013

Its a hardware issue.
[Samsung Epic 4G Touch] :
Re: [ROM] CyanogenMod 10.1 - WILD FOR THE NIGHT - Feb. 8, 2013

Not on my end. Whenever I would go back to factory stock or a TW ROM. The menu key didn't go off randomly. It only occurs when I flash an AOSP-Based ROM. Which is really weird.
[Samsung Epic 4G Touch] darkpoe:
My brother had the same issue, He got a new battery as discussed over and over in general threads and it went away. Usually happened to him with TW ROMS in low signal areas which would drain the battery quicker (higher load) or AOSP roms which may have a higher drain to begin with (which is what I've read as being the reason). But a new battery was the magic. This phone really spazzes when the battery is anywhere near bad.
[Samsung Epic 4G Touch] guitar112232:
Running the Feb 8 build and I am not having any issues at all. It is super stable!
[Samsung Epic 4G Touch] gg_99:
Wanted to report that I'm not having any problems (yet) either. I dirty flashed from 2/3 to 2/8 without issue (so did not need to go to 2/6 in between).
[Samsung Epic 4G Touch] Phobophobia:
I'm frequently getting "Can't connect to the camera" when I try to swipe over to the camera from the lock screen (I'm using a pattern lock) and "Gallery has stopped" when I try opening the camera app. If I try another couple times then it'll generally work, but it's annoying enough that it's probably worth fixing (or passing back to the CM devs if it's a CM issue) if anyone else is having the same problem.
[Samsung Epic 4G Touch] Omar04:
Re: [ROM] CyanogenMod 10.1 - WILD FOR THE NIGHT - Feb. 8, 2013

It happens in all 10.1. And on first keystroke not only after or later, is present since first time keyboard shows up and forever.
[Samsung Epic 4G Touch] dastin1015:
Re: [ROM] CyanogenMod 10.1 - WILD FOR THE NIGHT - Feb. 8, 2013

Wipe your data on the gallery app

私のEVO 3Dから送信される。
[Samsung Epic 4G Touch] vista178:
Re: [ROM] CyanogenMod 10.1 - WILD FOR THE NIGHT - Feb. 8, 2013

Still experiencing the keyboard graphical glitch. Is the swype-esque feature of the stock keyboard working for anyone? I'm also experiencing some glitching in setCPU to which I've included a screenshot. It may or may not be related to the keyboard glitch. My GPS doesn't accurately report the satellites with which it has a lock either. All issues are minor but there are still small bugs to work out. Thanks dev, this is easily the best ROM for the d710 to date.
[Samsung Epic 4G Touch] sjsharksfan420:
Re: [ROM] CyanogenMod 10.1 - WILD FOR THE NIGHT - Feb. 8, 2013

Hows the latest running for everyone? :)

sj

Sent from my pimped out E4GT on WftN-CM10.1 - 2/03 with Tap@Talk Pro 2.4.11
[Samsung Epic 4G Touch] Phobophobia:
Still can't connect to the camera the first time I try. Second time is fine.
[Samsung Epic 4G Touch] smbridges:
Best working recovery

Hey guys I know this has probably already been answered, but I have not seen it. What is that best CWM recovery that has tested out well with this rom and everything.

If you can please post some links of where i could find it.

Thanks
[Samsung Epic 4G Touch] Big Boy Laroux:
Re: [ROM] CyanogenMod 10.1 - WILD FOR THE NIGHT - Feb. 8, 2013

No camera issues here. Running latest build with official gapps. When was last time you did fresh/clean install?

---------- Post added at 04:29 PM ---------- Previous post was at 04:28 PM ----------

It has its own CWM built-in.
[Samsung Epic 4G Touch] csnv:
thanks for the awesome work!!.. ditched my CM9 b1 .. for this ROM, very nice.

MHL/HDMI still doesn't work though.. otherwise, everything is working great for me (Virgin Mobile)..
[Samsung Epic 4G Touch] rangerelf:
Re: [ROM] CyanogenMod 10.1 - WILD FOR THE NIGHT - Feb. 8, 2013

I've just flashed this and have playing with it all day, it's great. I installed Thumb Keyboard so I'm not having any of the graphical ghosting problems but I can confirm that it's happening with the stock keyboard.

Thanks for this jewel!
[Samsung Epic 4G Touch] Eldartho:
ran fi27 for a week and couldnt stand it.....flashed 2/8 build and damn its good!!!! no issues so far except maybe battery gets really warm??? or is that just me??? brand new seidio 3200mah battery to boot
[Samsung Epic 4G Touch] deaver_92:
Re: [ROM] CyanogenMod 10.1 - WILD FOR THE NIGHT - Feb. 8, 2013

It happens to me if the front facing camera is active. If the rear is active no fc's.

Edit: To see it for yourself, make sure kill apps with back button is checked then open camera and switch to front facing camera. Hold the back button to kill it, then try opening it front the lock screen. It should fc.
[Samsung Epic 4G Touch] Big Boy Laroux:
Re: [ROM] CyanogenMod 10.1 - WILD FOR THE NIGHT - Feb. 8, 2013

Well, I thought I had no camera problems. :)

I can confirm the above behavior and can reproduce those exact steps and get the “Gallery has stopped" message when trying to open the camera.

Edit to add: I then closed the app from the recent apps list and was then able to open the camera (and it brought me to the front-facing camera)
[Samsung Epic 4G Touch] Phobophobia:
I'm pretty sure I haven't used the front camera since I flashed 2/3. Would this still be a possible issue?

Fresh install of 2/3, then upgraded to 2/6 and then 2/8. The issue has been there on all three and wasn't there on my previous ROM (CM10).
[Samsung Epic 4G Touch] smbridges:
Re: [ROM] CyanogenMod 10.1 - WILD FOR THE NIGHT - Feb. 8, 2013

Does anyone know why I get this message from ROM manager "An error occurred while attempting to run privileged commands!"? If you have seen this before do you know a fix?
[Samsung Epic 4G Touch] Silentknyght:
I'm on 01/26 Build and this issue is still there. Interesting find.
[Samsung Epic 4G Touch] MarcAntonyy:
2/8 is running like buttah.

I have a question which admittedly isn't necessarily related to WFTN, but the process.google.gapps FC issues I was having had me looking into all sorts of things to resolve it, prior to fixing permissions. I'm curious to get some feedback on this.

What is the effect, using TB most likely, of integrating updates of system apps into the ROM? Is it a good idea/bad idea/pointless?

Additionally, what is the effect of integrating other non-system apps into the ROM? Say I wanted to integrate YouTube and/or Google Music into the ROM, so that they become system apps - what are the benefits/risks of doing this?