yashsingh1/xdaforums huggingface dataset:
[Epic 4G Android Development] codest3r:
I doubt it's the SD Card. It's been solid for me. No files ending up in LOST.DIR. Checked out fine on my last scan on a Windows box after re-partitioning it.

What's Download Manager? I'm not sure what that is. :confused:

In Ti I changed App processing mode to 'Auto, Indirect' and 'Interactive' in addition to the default 'Auto, Direct' and that didn't change the outcome. I also tried using the ROM's Busybox and that didn't change the outcome.

I installed one app from the Market. Went to Ti. Backed it up. Uninstalled it. It would restore it then. After reboot, it wouldn't restore again.

I also tried "fix permissions" from CWM and that didn't help.

Attached log cat. If a kmsg redirect to file would help let me know, I'll get it too.

If this is just me you all can ignore - I'll just start fresh on the next release. ;)
[Epic 4G Android Development] lost_:
Using TB labels would make restoring so much easier. I have several labels, but the most important ones are Core, Restore and Freeze. Core are for apps I need to setup the system and test stability (terminal emulator, etc). Restore is for the rest of the apps that I would like to have after the system is good. Freeze is for system apps I don't need.

One thing about using TB labels is to make sure /sdcard/data/com.keramidas.TitaniumBackup is backed up or doesn't get deleted during a wipe or flash. This is where TB settings and labels are stored, and, if "Auto-sync TB settings" is checked, TB would restore your labels after a fresh install (you can clear data to get it to read it again).
[Epic 4G Android Development] saramon:
Look in the list for Titanium, you should see an app called download manager, I am not sure it will work, not at all, but try clearing data from there, restarting, and try it again. If not, not sure where to go from there...
[Epic 4G Android Development] rbjem:
Its great you got wimax working...but when are we getting 4G? trolololol, jk.

Developement speed is blazing! I can hardly keep up.

Great work peoples!
[Epic 4G Android Development] it.:
Thanks guys!
[Epic 4G Android Development] wis3m0nkey:
This is so awesome was waiting for 4G on AOSP :D

I would press thank you 10 times if I can switching to CM tonight, I assume I'll need to use open garden to tether 4g right?
[Epic 4G Android Development] fromchaos0646:
for everyone talking about juice defender, its just my personal experience but ive gotten way better battery life without jd than with it.
[Epic 4G Android Development] tbob18:
Agreed. It never helped me at all.. Autostarts on the other hand helped dramatically. :)
[Epic 4G Android Development] birdturbo:
Is there ANY way around this?? I think it looks ugly and all my recipients hate it. I guess it's a drawback of AOSP :(
[Epic 4G Android Development] :
My absolute favorite rom, and the only reason I bought Rom Manager Premium. Just wanted to clutter this thread, but seriously its so effing smooth.

Sent from my Samsung Galaxy Tab Plus with XDA Premium
[Epic 4G Android Development] theblusmurf:
I do apologize. It has probably been posted but where can I find the changelog of the nightlies?
[Epic 4G Android Development] mrcollpepper:
tw. roms split them as well. maybe i misunderstood your question.
[Epic 4G Android Development] birdturbo:
There were a couple of TW roms that I used to run that did not split texts. It would send as one full text. I just think the "(1/2)" and "(2/2)" are really tacky.
[Epic 4G Android Development] RyleyinSTL:
http://cm-nightlies.appspot.com/?device=epicmtd

---------- Post added at 08:36 PM ---------- Previous post was at 08:35 PM ----------

....yes....set your text client to split messages at 160chrs. This resolves the issue.
[Epic 4G Android Development] mrcollpepper:
someone correct me if i am wrong, but i believe that is how it is "1/2" &"2/2" and you are stuck with it
[Epic 4G Android Development] birdturbo:
Ok, so I went into the stock SMS app and unchecked the split counter option in Settings and it does what I want it to. I just hate the whole "(1/2)" and "(2/2)" business. However, I went into GoSMS and the split counter option isn't there :(
[Epic 4G Android Development] inameiname:
I see. Well I guess the best way to test the restore, then, would be to completely erase the current ROM with a fresh install of the latest nightly, and see what happens. Thanks.
[Epic 4G Android Development] SirLeto:
I have the camera wake issue again now that I flashed Nightly 12.
[Epic 4G Android Development] inameiname:
Gotcha. Cool. Now, would the "Tasker" you are talking about just ES Task Manager or whatever it is called?

Yeah, I had a feeling that was GPS-set on cellular radio needing to be on....period. So regardless of that fact, you are saying if I install this "Tasker" app, it will automatically start GPS/Cellular Signal when I open the apps (such as Navigation, GPS Test, and such).
[Epic 4G Android Development] bender beerman:
i dunno about stock, but u can turn the counter off in gosms
[Epic 4G Android Development] birdturbo:
Do you mind showing me where? I can't seem to find that option!
[Epic 4G Android Development] bit1:
Man,a new nightly already?13, here I come.then to play with toads latest ;-)

Sent from my Epic, thanks to the letters X, D, &A.
[Epic 4G Android Development] mocsab:
sorry ------ mistaken post - whoops -
[Epic 4G Android Development] diego1985:
Likewise.
[Epic 4G Android Development] JettMartinez:
I know right? It's almost like they come out ....nightly or something :D
[Epic 4G Android Development] RyleyinSTL:
Settings --> Advanced --> Send settings --> Split large messages
[Epic 4G Android Development] birdturbo:
No, I got that. I'm just referring to the Sms counter. The option to turn it off is in stock, but I can't find it in GoSms.
[Epic 4G Android Development] RyleyinSTL:
This Tasker

But ya....Tasker will enable GPS when you open Navigation (or whatever other apps to define it to enable with), turn off airplane mode for a few seconds to "activate" the GPS chip and then turn airplain mode back on (leaving GPS on and actively working). Then when you exit the application you can set Tasker to also shut the GPS off.

Its as slick as hell. The Wiki and forum for the app explain everything you need to know but PM me or whatever if you want any help setting up the programming.

...or perhaps download CDMA WS and do something like this and you won't have to mess with the airplane mode on/off BS...actually I'm going to look into that.

---------- Post added at 09:50 PM ---------- Previous post was at 09:45 PM ----------

****, sorry...for me the SMS send-button shows an active character countdown above the word send in GO SMS. I don't think I had to configure that.
[Epic 4G Android Development] murso74:
to be included in next nightly:

epicmtd: Update prebuilt kernel, with changes from change ID: I3cccbbc2 (android_device_samsung_epicmtd)

epicmtd: Force higher dvfs limit for stable hd recording on some devices (android_kernel_samsung_victory)

epicmtd: Don't ever allow camera button to wake the device, divert from stock (android_device_samsung_epicmtd)

tomorrow has me all excited. looks like tonight just adds a new lock screen. gonna skip it for now
[Epic 4G Android Development] birdturbo:
All good, man! I just want to turn off that counter haha. :D
[Epic 4G Android Development] RyleyinSTL:
That new holo style for the rings lock is very ICS-ish. Me likes.
[Epic 4G Android Development] zanderman112:
That's why its called HOLO. That's the Android UI's name starting in ICS. And all manufacturers are required to keep it.

Sent from something with a Ｋモ尺れモㄥ.
[Epic 4G Android Development] nastypup:
I have a question about WiMax. I used Nightly 10 because I read that the WiMax toggle was fixed. When I turned on WiMax, it toggles 4G. Is that's what is supposed to happen? I'm so confused because, as far as I know, WiMax and 4G are not the same. But, then again, I don't know much <LOL>.
[Epic 4G Android Development] RyleyinSTL:
^^ WiMax and 4G are one and the same.
[Epic 4G Android Development] lbe:
In my experience not wiping the cache and dalvik seems less problem. when I have problem I reflash Google app zip after install the nightly to fix the wierd issue.
[Epic 4G Android Development] darkierawr:
Mines not working -_-

It looks standard. OFJIE
[Epic 4G Android Development] XxLostSoulxX:
Yea WiMaXX is the same as 4G

Quick lesson:

Clear's Network is called WiMaXX (4G)

Light Squared is LTE(Long Term Evolution) (4G)

HSPA is T-Mobile and AT&T's 4G which stands for High Speed Packet Access

All the same few differences but yeah its all 4G

That was funny kinda like talking in 3rd person its the same haha
[Epic 4G Android Development] worldwidepmp:
Look under ring lock style in CM7 settings in lockscreen.
[Epic 4G Android Development] darkierawr:
Yuh huh...

It's selected. It just doesn't work.
[Epic 4G Android Development] stilesja:
Actually none of those are actually 4g but the standards body decided to let them call it 4g as long as it represented a substantial improvement to 3g and is a precursor to full 4g... just sayin' ;-)

http://en.m.wikipedia.org/wiki/4G

Edit: that and the carriers were calling it 4g amway lol
[Epic 4G Android Development] || Acer ||:
That's awesome. Maybe the devs will change the clock to ICS font as well!
[Epic 4G Android Development] bender beerman:
edit: well, i thought i could, but then i couldn't find it... looks like i can show u how to insert your foot into your mouth really well, tho. o.O

BEER!
[Epic 4G Android Development] Domminater:
Is 4g tethering working?
[Epic 4G Android Development] XxLostSoulxX:
Well yeah i was just being simple but yeah your right too.

Besides are carriers are retarded in 2014 guarantee they'll say 5G lol or 4G+ Something like that
[Epic 4G Android Development] nastypup:
Anyone having a problem with callers complaining that they're hearing an echo of themselves? They all sound crystal clear to me, I sound crystal clear to them but they hear their own voices being repeated a second or 2 later.
[Epic 4G Android Development] Tirregius:
Absolutely top notch battery life on nightly 12. I have a 2800 Mah Yoobao, battery (highly recommended) and I'm @ 40% with 3.21 hrs screen on and 1.7hrs voice calls. Active wallpaper, auto brightness, outside half the day - ondemand 200/1000.

Have a strange issue where audio was feeding back from the mic to the earpiece upon "call" with no audio coming in from the call. I read that toggling "mute" and/or "speaker" might be a fix for call audio routing, but that has not worked for this one. It has randomly worked fine. No rhyme or reason.

I'm not switching away from CM for anything, now. Really the slickest Epic you can have, IMO ;-) .

(Was excited to see 10 pages of posts tonight only to find at least 5 dedicated to something to do with a Kitten BBQ, or something.)

Was really shocked to see how well games run on this rom. Dead space and MC3 are, well, [margarine slick].

Beautiful engineering, CM.

---------- Post added at 09:44 PM ---------- Previous post was at 09:42 PM ----------

That's a hoot. Read this .3 seconds after I posted.

Yes. I'm hearing myself! See above.
[Epic 4G Android Development] Zeinzu:
To change the ring there's a new option called ring lock style, for those having trouble finding it.
[Epic 4G Android Development] Domminater:
Alright, well what settings work best within wifi tether?
[Epic 4G Android Development] murso74:
First time I updated the nightly with ROM manager I had to redo gapps. Do we have to do that with each subsequent nightly?
[Epic 4G Android Development] Xinlitik:
Does having wifi active keep the phone in awake mode for anyone else? 3g allows deep sleep, but wifi doesn't for me
[Epic 4G Android Development] tbob18:
I don't think I've seen this good of battery life on my phone...ever. 1% left. :D
[Epic 4G Android Development] zman0900:
I too have been having the stuttering HD video problems and it still exists on 13. I saw that 14 is going to have the higher dvfs limit which stops the processor from going below 800MHz while recording (right?) so I decided to build the kernel with that and try it. Doesn't seem to have solved the problem for me.

So then I thought, why not take this to an extreme and see what happens. With my KernelSanders, I overclocked the phone to 1500, and set min and max freq at 1500. My kernel is forked from the CM kernel and doesn't have any changes that should directly affect the camera, except for maybe SLQB, but that didn't seem to make any difference. Anyway, I recorded another video, and still had the stuttering, and not any less. So it seems like extra processor speed doesn't really help the problem.

Good luck with the fix, I hope someone is able to figure it out. I'm really loving everything else about CM, especially the 4G, so I can live without the video.
[Epic 4G Android Development] zrmxp95:
The only thing that keeps me from this rom is when I activate a new call the speaker is maxed out...that defiantly hurts when you talk to loud people over the phone :)
[Epic 4G Android Development] Zeinzu:
I've already tried the test build with the patch as well and it doesn't fix the video recording. All of us with the issue should send logs for the devs to look over so we can get this fixed once and for all.
[Epic 4G Android Development] retrobits:
On 13, camera button still wakes screen when playing music. Its actually the "focus" button that's most troublesome, since that event is activated with just a light brush of the camera button. Phone in pocket keeps screen on too much, and eats battery.

Other than that, everything else has the viscosity of churned dairy spread.
[Epic 4G Android Development] cfusion:
I have to say this ROM is awesome and I get unprecedented battery life. Thanks devs...

My phone also maxes out volume when I answer the phone, using yesterday's nightly....

Definitely a CM thing since I didn't get it previously.

My ears don't appreciate it,thinking of setting a tasker task to auto set volume on phone answer as a workaround.

Todd
[Epic 4G Android Development] Speedin07si:
Camera button wake is supposedly fixed in tonights build.

Sent from my 4G Cyanogen Epic.
[Epic 4G Android Development] fromchaos0646:
so im getting a few graphical errors after nightly 13.

one being the dialer. notice the top.

then the contacts. notice the top again.

then dolphin. notice the little white bar at the top, right above the status button. it just appears as i scroll down.

and again in dolphin. the seach bar is abnormally huge.

and now the lense and then followed by the rotary lockscreen.

i know i might be knitpicking but this is quite annoying to me. is anyone else having these problems? i even reinstalled, wiped, and reflashed twice. still didnt work. any tips? im sure that this will be fixed with tonights update anyways, but still.
[Epic 4G Android Development] CogDancer:
Camera button wake problems still occur for me on nightly 13. It only wakes within ~60s of screen off, but that's been the case for me for the last week or two.

On a probably unrelated note, has anyone else had issues with lockscreen toggling via either the notification widget or the settings menu? It's very difficult for me to identify any predictable pattern, but when I try to enable the lockscreen after the phone has been on for several hours, it often will not turn on until I reboot the phone. I've tried changing the timeout settings to zero and using Tasker to turn the lockscreen on upon screen off, but nothing has worked so far. It's not a big deal, but it would be nice to be confident that my phone is locked every time I tell it to lock.
[Epic 4G Android Development] lbe:
Same to me it broke my Google contact and had to reflash gapps. I had dalvik cache checked in Rom manager. Think it has something to do with it.
[Epic 4G Android Development] saramon:
My dialer/contacts looks the same

---------- Post added at 03:34 PM ---------- Previous post was at 03:34 PM ----------

Happened to me too, and I also had Dalvik checked
[Epic 4G Android Development] vita10gy:
I hope no one takes this the wrong way, but is anyone actually even working on the bugs? Or should we hold off for a while on annoying people about them, and rather just keep a list up to date on the wiki.

I know when we do software bringing on new features generally takes precedence over perfecting existing things during furious development phases, plus everyone wants to do the glamorous new stuff over slogging though error logs.
[Epic 4G Android Development] Speedin07si:
Have you seen the changelog??? seems to me like the hard working devs. Have fixed a lot of bugs since the initial release of CM7....

Some bugs take backseat to others but still will get figured out in due time....

Just my .02.

Sent from my 4G Cyanogen Epic.
[Epic 4G Android Development] MeetFace:
I think that regardless of whether the devs are ironing out the bugs (and they are), keeping track of bugs (listed by nightly) on a Wiki is ALWAYS helpful, especially when you can clean up the traffic.

Back in the Team Viper days, we had a fairly extensive Wiki that we directed people to, cleaned up the thread quite a bit.
[Epic 4G Android Development] vita10gy:
There's more to a change log than fixing these 5-6 issues. If you actually read with what I wrote, despite even prefacing it by warning you not to take it the wrong way, "Hard working" has nothing to do with my question.

Again, when you develop software a perfectly reasonable approach is to take your list of requirements, and your roadmap of where you want to be, and take off in those directions. Making sure each requirement is perfect before you move on isn't necessary, and is often a fool's errand since you can break one thing by doing another.

My question, in a sense, was the exact opposite of your implication. I'm wondering if we're unnecessarily badgering people over things that they have no intention to look at, because they wouldn't make any sense to look at, until we're farther along.

Trust me, there's few things more annoying to a developer than getting constant updates on the status of a bug that you have no intention of fixing for a while, never told anyone you were fixing, and never implied should be perfect. I'm just making sure we/I am not being that person.

In other words I'm wondering if the "active participation" on the forum about this small handful of persistent issues is counter productive, or if we should just quietly make that helpful wiki page for them, until such a time comes when they let us know major development is complete, and they're shifting their focus to ironing out those bugs.

Or, to phrase it a slightly different way, I never implied these bugs were being forgotten about, would never be fixed, etc, but if no one is literally attempting to fix these specific problems as we type, then we're just the kids in the back seat going "are we there yet? are we there yet? are we there yet? are we there yet?" when we bring them up 4 times on every page of the thread.
[Epic 4G Android Development] MeetFace:
Vita's post is a legitimate concern, +1 for Wiki bug-tracking.
[Epic 4G Android Development] jnadke:
I may have started something... *sigh*

Camera wake is NOT A BUG!

It means YOU installed something that is keeping your phone awake. It's up to YOU to figure out what that is, or wipe your /data and start over.

If the button doesn't wake the phone after a while of having your screen off (30-60 seconds),

then your phone is working fine

. That means GPIOs are being disabled as they should (and thus, your phone is deep sleeping).

Your power button is actually (typically) attached to an IRQ, which wakes the processor directly.

The camera only wakes the phone because the processor is already awake, and in the button/keys configuration file for android, there's a line that says the camera button is able to wake the screen. The processor sees the button press, checks to see if it can wake the screen, and then does so. In deep sleep, the GPIO for the camera button is shut down, so it never gets the signal.

At any rate, Decad3nce pushed a patch that will forever disable camera wake for Nightly-14, which is funny because it's like sticking black masking tape over the light that says "error!"

I'm looking forward to the entertainment of how many people say camera wake is fixed.

In the old Vogue community, us Devs tried to actually explain how things worked. Apparently that doesn't work here, because nobody reads what you write.
[Epic 4G Android Development] ac16313:
I read what you wrote ;)

Thanks for the explanation again.
[Epic 4G Android Development] tazfanatic:
I have said it wasn't a bug multiple times and got told I was wrong so I just shut my mouth.
[Epic 4G Android Development] jnadke:
It's not usual to allow the other buttons to wake the screen, but it serves as a quick and easy debug to make sure the phone is sleeping correctly and GPIOs are being shut off.

So, Decad3nce's patch is technically correct.
[Epic 4G Android Development] jtw78:
Are there any tools that you would recommend for finding the culprit. I'm using the stock battery data and Spare Parts, but that hasn't led me to the app that's keeping my phone awake. I've uninstalled a few things that have been keeping my phone awake, but that hasn't really helped.

On a related note, is there a better way to backup and restore apps and data? I'm using Titanium, but I've also seen that it introduces bugs (like this one, possibly). Should I manually install the apps and then restore the data through Titanium? Any thoughts would be appreciated. Thanks.
[Epic 4G Android Development] rprockey:
Please search before you post. This too has been addressed many times. Here's the answer again. Well it's one answer.

First run CPU Spy, and look at the Deep Sleep %. If it's low, something is keeping your phone awake. CPU Spy in Android Market: https://market.android.com/details?...251bGwsMSwyLDEsImNvbS5idmFsb3Nlay5jcHVzcHkiXQ..

Next run Better Battery Stats, hit the first drop down and select Partial Wakelocks. The first one or two processes are your culprits. Find out what app the process belongs to and why it's are waking your phone.

Search XDA for Better Battery Stats, There is a dedicated thread in which the developer posted the apk.

Restore your data with which ever tools you find to be convenient and useful. However if you find problems, please wipe data, reflash, load your app from the market, or side load the apk and see if the problem still exists, before posting it for the devs to review. It's more helpful to them if there are fewer variables.

There is a CM7 Tips thread started in the general section. You could ask other users about app restore techniques there.

Good Luck!
[Epic 4G Android Development] CogDancer:
Thanks for that detailed explanation! I understood that the camera button wake was technically working as designed, but I was still a bit fuzzy on the details and the rationale for the design. My comment was written under the incorrect belief that the camera button was no longer supposed to wake the phone in nightly 13, since I saw that in the changelog when I downloaded it, but I guess that change was committed after 13 was built.

Anyway, I know how frustrating it is when people ignore the correct information and keep asking pointless questions, so I really appreciate you taking the time to explain things once more in detail. Hopefully after the next nightly no one will say any more about it. :D
[Epic 4G Android Development] vita10gy:
Too be fair, people can complain they don't LIKE the camera wake, even it's not a "bug". With our two stage button the screen wakes with the slightest pressure.

Menu wake is an option in the settings, it would be cool if camera wake was one too, or just outright disabled for our particular phone if possible. What is Cyanogen about if not giving people 92348923 options over every piece of minutia their phone can do? :D

The fact that your phone wouldn't wake from a deep sleep doesn't much matter if it never sleeps because the camera wake wakes it every 18 seconds in your pocket.

I don't care much myself, but I think the over arching point is a valid change request, if you can avoid getting bogged down in hyperventilating over the misuse of the word bug.