yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] ssewk2x:
FINE, I'll try it again ;)

While it's running, can I just pipe up and say that I'm really digging this ROM/Kernel combination? It's like I have a brand new phone again, and I didn't have to shuck out a pile of cash to verizon. Open Source fscking rocks, man.

Anyway .. the backup appears to be frozen again. But, this time it shows a file that it is apparently working on. The name is "event_data@1330048291314.txt" if that means anything to anyone.

Upon some investigation, it's a dropbox log file (located in /data/system/dropbox) .. strange. I wonder what would happen if I deleted it? Nothing .. but now I'm gonna reboot recovery and try another backup...I don't really give a rodent's rectum if dropbox doesn't quite get backed up right, so here goes nothing.

Well, now it's just getting stuck sooner on a different file. It looks like the tar process is dying. Run a ps | grep clockwork in an adb shell after it hangs, and you'll see what I mean.

Ok .. enough of this. I need some sleep tonight.
[Fascinate Android Development] Special_opps:
This worked.
[Fascinate Android Development] neh4pres:
Did you wipe dalvik also? Well it worked for 2 of us.. Thanks for trying. i know it's not the cause, but thought it would be a nice workaround after it worked for me.

What ROM are you on? If you have not tried aokp yet you should really give it a look. Best rom i have seen. Does everything i want it to.
[Fascinate Android Development] shelby04861:
Thought I would share a little bln info. When I restored one of my backups it had the nts 1.1.4 and when I switched to the 1.1.5 it stopped and I never realized it. Something either changed or I don't have a setting right. I went back to 1.1.4 and will play with it another time, but at least it is working again .
[Fascinate Android Development] sol_671:
I was wondering why I never had the backup problem while some of you are.. maybe it is the cache, since I always wipe both when ever I'm making a backup.
[Fascinate Android Development] Glocjt:
Just wanted to drop in and say that I just flashed THS 6.5 and Glitch B5 for THS 6.1, and everything seems to be going smoothly. I've tested data transitioning between 3G/wifi/airplane and haven't had any issues.

I did Odin the BG bootloaders right before flashing THS 6.5 (which I realized I didn't have after seeing the last bits of discussion here :P), and I've been able to do a backup in Glitch CWM just fine.
[Fascinate Android Development] yonith:
This is a stupid question but in the OP it says this kernel has Voodoo Sound 10, does that mean voodoo sound is built in or does it mean it supports the voodoo sound app if I download it?
[Fascinate Android Development] neh4pres:
It supports the app
[Fascinate Android Development] sixstringsg:
Both.
[Fascinate Android Development] ssewk2x:
So, I still can't do a backup with glitch recovery, but i can use the b3 kennel with stock recovery to make backups. That will do for now. My other slight complaint is that if i turn on didle, i get sleep of death after a while, every time. No biggie, i can just leave it off :)
[Fascinate Android Development] OhioYJ:
Haha, after a while? Let my phone sit for 10 seconds with the screen off and it won't wake up. Everytime.
[Fascinate Android Development] sageDieu:
So my battery life has been great running the latest beta on AOKP 25. 15 hours of battery and almost an hour of screen time, my battery is at 73%.
[Fascinate Android Development] kyleco:
Happens on mine also. Using THS 6-6.5

Sent from my frozen, Glitched out AOKP
[Fascinate Android Development] ssewk2x:
#define A_WHILE 10_seconds
[Fascinate Android Development] thisguy23:
I love being able to push this phone to its max. That said here's the setup:

ICS AKOP 25 Glitch 14 B5 for 6.0

1200 step with 118 LOC

Glitch OnDemand with some OV and UV. (see pics)

Nenamark 2 went from 24.7FPS stock to 30.0+!

118 LOC is the MAX I can currently go. with UV or OV more on any step locks the phone. Still 36mhz OC bus, ram, and gpu is pretty good for this phone!

Thank you devs for such a great kernel. I am going to try and get more from this when I have time to play with the voltages more. Right now its stable for two days.
[Fascinate Android Development] bobloblaw1:
I'm not sure if I was being daft but it seems the links for b5 are wrong and I couldn't find a post with the proper ones. Perhaps I missed it, but on the chance I didn't here are the links so no one following me has to dig as I had to.

B5 for THS Build 6

B5 for THS build 6.1 & 6.5
[Fascinate Android Development] sixstringsg:
I haven't updated the OP because I've been working 18 hour days. There are posts with them in it though.
[Fascinate Android Development] neh4pres:
Less work more play mister. Lol
[Fascinate Android Development] sageDieu:
so far everything is great, didle and stuff. I've found one reproducable issue with it: if I enable wireless tether with the phone charging and let it sit for a little while, the screen won't respond to the power button.. it's odd though because one time when it happened, I received a phone call after enabling tether, so I answered and prox sensor turned off he screen... it wouldn't turn back on during or after the call. the screen was stuck off, but I could still hold the conversation.

Sent from my ICS SCH-i500
[Fascinate Android Development] sageDieu:
also with bln, it seems to work for whatever duration is set in ariesparts.apk so there might be something unintentionally conflicting there.

Sent from my ICS SCH-i500
[Fascinate Android Development] Sheradrax:
Could some one point me to where the int voltages setting are for the different leakage settings? B5 seems to be more touchy with the live oc settings. I was able to get higher live oc on previous builds.

Sent from one twisted fassy. Mmm... ice cream.
[Fascinate Android Development] xain713:
Yea b5 gave me lots of sod never had em before so I went back to b4 it just works better for my phone :)
[Fascinate Android Development] Anthony2816:
When I install this kernel (CM9-fascinatemtd-Glitch-V14-B5-ForBuild6.zip) on my Verizon Fascinate (on top of TeamHackSung's ICS 6.5 rom), I no longer have 3G. The only way to access the internet is via wi-fi.

Is this just me, or is it a known problem?

(Hopefully this is the correct forum...)
[Fascinate Android Development] sixstringsg:
Well, your zip says "forbuild6" whereas your ROM is not just build six. Grab the right one here
[Fascinate Android Development] Anthony2816:
The only other one that looks closer says it's for 6.1. Should I try that, or wait for one that says it's for 6.5?
[Fascinate Android Development] sendan:
Use the one for 6.1, it's fully up to date from what I can see.
[Fascinate Android Development] droidstyle:
I agree with six, you should of flashed the 6.1 version instead of the 6.0 version as clearly stated in the guide.
[Fascinate Android Development] djk21108:
Did anyone else see the new cm9 is out for fascinate on their nightly website?

http://cm-nightlies.appspot.com/?device=fascinatemtd
[Fascinate Android Development] sendan:
That looks like cm7.
[Fascinate Android Development] djk21108:
Yeah I kinda notice. Hmm. I wonder why it isn't cm9 yet? They haven't released a nightly in over a month.
[Fascinate Android Development] sixstringsg:
The Cyanogenmod build cluster is just getting finished up, they had to buy all new hardware recently. CM9 nightlies will come along shortly.
[Fascinate Android Development] ssewk2x:
Ok, so one other problem that's annoying me besides the "no backup in glitchy recovery" thing.

Has anyone else seen their phone just kind of "forget" about custom ringtones and notifications stored on the SD card? All the sudden, my phone will be silent and I'll check the sound settings and all of my custom sounds have vanished as options. A reboot usually gets them back, but only temporarily. I am trying to figure out if it's a kernel or rom issue at this point, so if anyone has any insight, please let me know.

Thanks. Sorry to be sounding more like a noob user than a seasoned developer, btw. I'll get back to the latter soon, I hope.
[Fascinate Android Development] sageDieu:
this has not happened to me at all that I can remember on any rom. what's your setup?

Sent from my ICS SCH-i500
[Fascinate Android Development] xsc0rchx:
I have been doing a little bit of research on this issue and I have found out some interesting information about my phone. I wanted to see if anyone else has noticed these types of issues or if there is just something specific with my phone.

I use "Where is my Droid's power at" to monitor my batter usage and identify applications that may maintain a wake lock. I also use "CPU Spy" to monitor my processor state. I have noticed that my batter life has not been as good as it was in GB, then I noticed that "Android OS" was maintaining a wake lock when monitoring my battery state. I then decided to disable background sync that that resolved the utilization. I also noticed after disabling background sync that when I charge my phone it now maintains Deep sleep. I though this was interesting because I did not have this issue in GB.

I believe there may also be a correlation with this behavior and the fact that I use "Droid wall" to white list applications that should have 3G / Wifi access. I think because I block Android OS that when it attempts to connect it maintains a wake lock on my phone. The interesting part is that when the application is blocked I only get about 3 log hits for access throughout the day.

I have also experienced some issues with Deep Idle, whenever this feature is enabled my phone goes into SOD and when I plug in USB to logcat, I notice my phone is dead. This will occur over night when my batter is initially at 80%.

Again I just wanted to see if there was input on these issues or to see if anyone else has experienced any of this.

thanks
[Fascinate Android Development] tripacer99:
I believe I saw somewhere that Android 4.0.4 fixes the whole "Android OS" battery issue. Now we just need to wait until google officially releases it...gah
[Fascinate Android Development] erivnocmc:
And when will fix on the phantom calls?
[Fascinate Android Development] xsc0rchx:
Thanks, I thought I was crazy!
[Fascinate Android Development] sixstringsg:
We can only fix that so much in software. Ultimately it is a hardware issue that we are trying to minimize with software.
[Fascinate Android Development] sendan:
I think sbrissen fixed this in THS 6.5

check the changelog.
[Fascinate Android Development] ssewk2x:
Currently, it's THS 6.5 with Glitch 14b5 for THS 6.1. I had restored a bunch of apps with TiBu, which I'm thinking may be the culprit now. So now I'm trying a full data wipe, then restoring user apps only (no data) in TiBu to see if that helps.

But .. so far, the phone hasn't found my custom ringtones yet. I wonder if there's something that's just plain hoarked with the media scanner, or if I have too much crap on my SD card or something.

Anyway. I'll see if anything improves after this wipe / minimal restore operation and let y'all know.

Also, apologies for cluttering up a kernel thread with this stuff (especially if it turns out to not be a kernel issue).
[Fascinate Android Development] erivnocmc:
Why is it hardware? After all, the stock firmware do not have phantom calls.
[Fascinate Android Development] thisguy23:
Just wanted to add my $0.02 about OC. The HTC One has a 1.5ghz 4 core processor and a 12 core gpu. If you are worried that OC 300 - 500 MHz is going to kill your battery faster... um I'm sure our battery life is much better! I have no proof of this other than common sense. Thank you for allowing me to vent.
[Fascinate Android Development] bobloblaw1:
Common sense is great except for when the process common sense is being applied to may be counter-intuitive. Some folks say multi-core equals more power use. Others say its less because each core can draw less power and finish tasks more quickly and return to idle. I'm not really sure where the results and real world tests stand at this point.

But that's really an apples to oranges comparison. Back to the topic at hand regarding battery life. 3 ideas:

1. Give the battery a few full cycles prior to forming an opinion.

2. Black (and red) is your friend on an AMOLED screen. A black wallpaper, black MMS app, and black theme for any other app you use frequently will give you more battery life.

3. If the battery life is still disappointing get a epic touch 4G batter which will give you an extra 300 mah and will fit the stock casing.

Edit: I can't count
[Fascinate Android Development] neh4pres:
This battery life is amazing.. Stock battery.
[Fascinate Android Development] neh4pres:
....... And the upload picture from xda app is not working :(
[Fascinate Android Development] ssewk2x:
Recovery Backup issue update:

I discovered after some poking around that we have a /datadata partition, and a symlink to it in /data, such that /data/data points to /datadata, which is on its own partition. In recovery, the datadata partition is not mounted, and its mount point does not exist.

So, I launched our recovery, got into an adb shell, and did:

$ mkdir /datadata

$ mount /datadata

Then proceeded to run a nandroid backup. It has already progressed past the point where it would lock up on /data. I believe this hack has hacked my way around this problem. In fact, I know it has .. my backup just finished successfully. I would also imagine the same commands would need to be done prior to restoring from my backup.

What I do not understand is why the directory and mounting of it is missing in the first place. Perhaps something in the recovery ramdisk needs to be patched to address the missing mount point?

Side note: since wiping data and NOT restoring any of it with TiBu, my phone has not forgotten about my ringtones .. so far. Hopefully that was the secret sauce for that issue.
[Fascinate Android Development] sixstringsg:
Now that we have device trees for fascinate, we should be able to build official ramdisks and hopefully it will work.
[Fascinate Android Development] neh4pres:
It's good to have you back
[Fascinate Android Development] ssewk2x:
Yup! And if the dev tree you get still has the bug, we can still fix it here.

One of these days I've got to get set up again to build this beast and start working on it again.
[Fascinate Android Development] k_nivesout:
ssewk2x - I'm curious as to what SD card you're using? It seems like some people have issues even getting MTD roms to install with some SD cards, or have (what sound like) SD card-related issues on ICS. In the ICS threads I see a lot of people reporting issues with the gallery not finding their pictures, or music apps not seeing the music on their SD cards, etc, while other people (including me) don't have any such issues.

I guess my thought was just that maybe some of these issues could be attributed to the actual SD card, it would be interesting to see what would happen if those with the issues were able to try out a different SD card to see if the issues persist.
[Fascinate Android Development] ssewk2x:
I'm using the stock SD card that came with the phone. I don't think I've even ever had it out of the device! I've never had SD card related issues either - from what I've been able to glean from the history of events, the people who installed the EC09 leak from p3droid made up the vast majority of folks who experienced SD card problems. Since I never used that ROM or any of its derivatives and waited until JT & The Gang got the problem licked, I've been doing ok.

I really think my problem this time around was because of restoring stuff with TiBu. Since I un-did that mistake, everything has been peachy.
[Fascinate Android Development] sarkozy:
What's so odd about the recovery problem, is not everyone is having issues with nandroids. I've made several backups over the last few days with B5 on AOKP and CM9.
[Fascinate Android Development] sixstringsg:
Captivate doesn't have the issue at all from what I've seen. Also, I know that doing 3-finger breaks recovery on the Fascinate, but I had to on mine. How do I fix it again? Is going back to stock required? I've heard a few opinions on that.
[Fascinate Android Development] ssewk2x:
Yeah, that's tricky. Maybe the aokp folks are doing something different with the /datadata stuff? I know what's happening, but I can't see a difference in the code between stock CWM and our stuff. Maybe later on I'll have a look at the filesystem under stock CWM and see if that's different.

Six, what exactly has happened? I at least used to be able to just flash glitch again from the 3-finger recovery. If you can't get to that, then I think just odin the CWM that's fixed for cm7, and you can flash whatever you need to from there.
[Fascinate Android Development] Anthony2816:
When I switched from the kernel that came with TeamHackSung ICS 6.5 to Glitch V14b5 for 6.1, I noticed the Clockwork was altered: Blue text changed to red, Glitch logo added, menu items changed (wipe cache changed to wipe cache and dalvik). Perhaps when the alterations were added, something broke the backup system?
[Fascinate Android Development] sixstringsg:
I was trying to build a CM9 kang that boots for the Fascinate. It wouldn't make it to the boot animation, so I had to three-finger into recovery. I then flashed the latest build, and when I went to reboot, it rebooted straight into recovery. I cleared /cache and dalvik, same thing. Reflashed Glitch, tried again, same thing.
[Fascinate Android Development] sageDieu:
that's happened to me multiple times, no idea why and nobody has looked into it at all. you will have to Odin back... just make a backup, Odin to froyo, then Odin gb radio and cwm4 for cm7, then use 3 finger to boot recovery and flash ics.

Sent from my ICS SCH-i500
[Fascinate Android Development] tonu42:
Quickest method to escape that.

http://rootzwiki.com/topic/15496-how-to-get-out-of-recovery-boot-loop-on-ics-fascinate/
[Fascinate Android Development] k_nivesout:
Hm, well if you haven't had any issues since then, maybe it was related to titanium backup. I just know I've seen lots of posts where people have similar issues on ICS with things on the SD card sometimes "disappearing" or not working correctly. The strange thing being that it only seems to affect some people, which makes me wonder what it is they're doing differently (if anything).

Not sure why the 3-finger seems to bork the recovery on the fascinate, but what you describe is exactly what happens after 3-fingering. There's no need to do something as drastic as odin'ing all the way back to stock, I've had success with simply reflashing the CWM4 recovery fixed for CM7 in odin, and then reflashing the rom/kernel from there.
[Fascinate Android Development] johnsma22:
Not that this is really important, just something that I noticed going from V14 B4 for use with THS 6.1 to V14 B5 for use with THS 6.1. After flashing V14 B5 the battery percentage is no longer visible under the time and date on the lock screen.

It shows up there when it's plugged in and charging. I could have sworn that the battery percentage was there under Glitch V14 B4? Maybe I'm going crazy, as I've been flash happy lately, LOL!
[Fascinate Android Development] kyleco:
Has anyone tested this with AOKP 26? It's built from source now, not sure if it's still going to work with the Glitch 6.1. Not by a computer to test, but I'll update as soon as possible.

Sent from my SCH-I500 using Xparent Blue Tapatalk
[Fascinate Android Development] speedingcheetah:
Just tried it...ver meant for build 6....lost 3g data connection..everything else seemed fine.

Flashed the one for build 6.1...everything is good....

Now..if only i knew what all the difference was between all the io scheduler and cpu governors were...i would be dangerous...
[Fascinate Android Development] neh4pres:
Everybody, please stop flashing build 6 kernels with build 6.1/6.5 based roms.... It's just nonsense
[Fascinate Android Development] speedingcheetah:
Well...it be nice to know what build AOKP (insert build # here) is based off of...maybe I missed it somewhere....

Anyway...using AOKP and Icy Glith Icy Glitch V14 for 6.1....Everything..expcet for Torch is working fine....

Anyone know of a working Torch app for ICS...or is it a rom/kernel combination thingy that is borking the torch for me...??
[Fascinate Android Development] sixstringsg:
Well, I am one of the builders of AOKP, and it is based off latest source, thus 6.1. For the next beta we probably won't building 6 anymore.
[Fascinate Android Development] speedingcheetah:
Ok..so..hopefully..the Glitch kernel will be updated too...I wouldn't want to flash the wrong kernel version to a newer build of AOKP...I was a tad confused which version build 26 was based off of...6..or 6.1....

The performance increase with Glitch is a worlds of difference...my phone kept chocking while simply trying to play music on the stock kernel..laggy like crazy...flashed Glitch...worlds better...on my hardware anyway..
[Fascinate Android Development] sixstringsg:
It is updated, I just haven't done the OP yet.
[Fascinate Android Development] BlingDynasty:
I tried this setup and I noticed that my phone wasn't very stable at 118 LOC, but at 114 with the voltage increases at 1200 it's running smoothly and it the temperature remains fairly stable under heavy usage. The performance actually seems more stable than it does at the default clock frequency in terms of battery life and temperature so far (half a day).

Thanks to the devs for their amazing work. I never expected my phone to be improving at this time when I bought it in 2010!
[Fascinate Android Development] Azuma73:
Six, I hate to ask, but which one is to be updated?:confused: Glitch or AOKP?

Thanks!!
[Fascinate Android Development] sixstringsg:
Both? AOKP has nothing to do with glitch.
[Fascinate Android Development] fulaman:
When you set the voltage for 1200, do you mean 1200 mhz? I'm a bit confused with your settings.
[Fascinate Android Development] bobloblaw1:
Yes, the 1200mhz step may actually run at a different frequency depending on Live OC. Voltages are set for steps regardless of what the clock speed for that step actually ends up being.

Example:

1200 step with 0% live OC (100%) = 1200mhz

1200 step with 10% live OC (110%) = 1320mhz

Each example would run at the same voltage setting because they are both on the 1200mhz step even though the clock speed differs due to the Live OC.
[Fascinate Android Development] sfobrien:
Does the latest Glitch take care of the issue when you answer a call the volume is super loud? I know when I ran CM7 it did.

Thanks.
[Fascinate Android Development] redrol:
Has anyone tried external microphones with this kernel? I hear it works with version beta 3 and that makes me very happy if it is true.:)
[Fascinate Android Development] neh4pres:
Never knew there was an issue with external mics
[Fascinate Android Development] redrol:
External mics do not work on any CM7, 9 or AOSP builds. Its very sad.
[Fascinate Android Development] droidstyle:
yes it sure does.
[Fascinate Android Development] shag_on_e:
+1, with the init.d call_boost script one can fine tune in call volume, which is perfect for us OCD sucka$ B-)

~~~~There is no spoon~~~~
[Fascinate Android Development] pntballer505:
I noticed the BLN in the newest V14 B5 for 6.1 timesout

after a few seconds. Even after changing it in NStools.

Has this been brought to anyone's attention already?
[Fascinate Android Development] sixstringsg:
We know.

10char
[Fascinate Android Development] pntballer505:
Okay okay, Just checking. Very snappy kernel,

thanks for the continued updates.
[Fascinate Android Development] neh4pres:
Use the aires parts app included with the rom to adjust backlights timeout
[Fascinate Android Development] sfobrien:
Great thanks.
[Fascinate Android Development] speedingcheetah:
BLN isn't working for me in AOKP build 26 and this kernel...sigh..
[Fascinate Android Development] k_nivesout:
Alright, so as was previously noted in the thread, BLN isn't working like everyone's used to on B5. If you want solid BLN it's best to stick with B4. If you've already flashed B5, you'll need to reflash the rom you're on, then B4. No need to wipe data, so you're not losing anything.