yashsingh1/xdaforums huggingface dataset:
[Fascinate General] sarkozy:
It's just as stable as any TW based rom. Use the stock kernel until you're versed enough in the live oc system to flash the Glitch kernel.

You can, but undervolting has been proven to be useless in saving any battery so don't bother. Use stock voltages.

Read the op.

The kernel uses RIL blobs from the EC09 modem, but EH03 works as well.

Read the guide to flashing AOSP roms in this section, it should be there.

That no longer applies since these roms repartition the phone to YAFFS/MTD. Forget everything you knew about touchwiz based stuff, different animal altogether.
[Fascinate General] errolroach:
Possible noob question alert...

I'm coming from Build 26...to flash Build 27. Do I need to wipe data? Or just cache/dalvik? Be gentle.
[Fascinate General] Stephen.k.spear:
just cache and dalvik

Sent from my glitched aokp unicorn.
[Fascinate General] speedingcheetah:
use the newer build 27..as the original one has sms totally screwed...not sure if the OP has been updated
[Fascinate General] ZeroLozen:
Any color calibration in AOKP build 26?
[Fascinate General] Stephen.k.spear:
There is on 27

Sent from my glitched aokp unicorn.
[Fascinate General] ZeroLozen:
Thank you sir! Will flash this evening. Fantastic work to everyone working on this!
[Fascinate General] icyhandofcrap:
No wifi problems reported so far? Is the nav bar enabled by default or is that removed (don't want to see it!)

Will flash tonight, thanks!
[Fascinate General] Stephen.k.spear:
It didn't show up for me but its toggle able in ROM control

Sent from my glitched aokp unicorn.
[Fascinate General] fulaman:
What version of glitch should one use with Build 27 of AOKP, icy glitch v14 b5 for 6.1?
[Fascinate General] ssewk2x:
That's the one. Working very well on my phone right now :)
[Fascinate General] fulaman:
Thanks my friend

---------- Post added at 12:52 PM ---------- Previous post was at 12:20 PM ----------

What would you guys say the best governor is using NStools? Glitchondemand or Smootha$# ?
[Fascinate General] sageDieu:
it didn't, I don't remember what exactly happened. I'll ask him, he is my best friend IRL. if he's willing then I will let you guys know.
[Fascinate General] bobloblaw1:
I wasn't implying that you were.

Again, aokp and cm have a different focus. CMs is not to have as many features as possible.
[Fascinate General] droidstyle:
thats whats wierd because cm use to be all about the features instead of being vanilla.
[Fascinate General] neh4pres:
Glad someone shares my thoughts.
[Fascinate General] bobloblaw1:
I should rephrase. Cm has never been about rapid build cycles (for the most part, sure nightlies are available but official builds have always been far between) to get every new feature out.

And honestly cm's focus has shifted and changed with time. A rom that went from being a solo project on one phone to a team effort on hundreds of phones has to change its goals if it wants to have any semblance of achievable purpose. Recently its seemed as if cm has focus more on device trees and the stuff that lurks below the ui while aokp has built on top of that base!

Also, the device you are on plays a large role in whether cm or aokp is better.

For now, aokp is king for the most part.
[Fascinate General] Hook33:
Bug?

Since glitch milestone 5 (I'm on the current skunk glitch build), I've been getting a slight lag on wake unlock. This doesn't happen every time, but when it does, the screen is really dim and the text turns to a yellow hue and there's a delay 0-5 until the screen is responsive. I've tried different govs and turning off features, no over clock etc., but I can't seem to get rid of it. This is on a three wipe install. Is this a known bug? I'm stumped and suggestions? :confused:
[Fascinate General] neh4pres:
This helps my understanding. Thanks.
[Fascinate General] TomTcom:
I'm running build 38 AOKP. My question is how can I make the wifi tether app that's built-in, use a specific IP or narrow the IP ranges it uses?

When doing a log cat, dnsmasq starts and appears to give ranges of 192.168.48-42. I can't determine how dnsmasq is setting this.

My purpose is to limit the scope or statically assign, or dhcp reserve the tethered IP that is given out. Only one device will ever connect to my phone, my Asus TF101.

I'm attempting to have the same IP as the home wifi in order to use hostnames to be able to seamlessly connect when using SSH.

In the hosts file, when DNS loads, it won't allow 2 IP's for one hostname. Only the first one in the file is read.

I have dug through many of the files in /data/misc/wifi.....

I can see how certain things get configured but not much beyond that. I also attempted to search github for AOKP but not much luck on that.

Also, I'm trying to avoid using another app to do this. Any ideas?
[Fascinate General] swagooo:
flixster crashes

I just registered so I cannot post in the development forum, otherwise I would post this there.

Flixster app crashes on my fascinate build 38 when trying to stream a trailer. gets a few seconds in and freezes, then reboots. It happened on build 37 so i just updated to 38 and now it is still crashing.

Also, similar trouble with YouTube videos. Some work, most dont.

fyi. ty.
[Fascinate General] TomTcom:
Try uninstall/reinstall of flash. Clear cache and clear data on the two apps giving you issues. See if that helps.
[Fascinate General] AuroEdge:
So for Fast Charge, it charges across all 4 pins correct? I was recently messing around with my Verizon car charger and noticed that it only has two wires soldered to leads on the micro usb connector.

Does it really matter if a car charger has the 4 leads wired to and if so how do you tell before you buy?
[Fascinate General] ssewk2x:
I have no idea where you got your information, but that is NOT how fast charge works, nor how USB works, even. Here's what actually happens:

Your phone can take a charge from any standard USB connection - either to a wall charger, or a computer or whatever. Whenever USB is connected, there is a little bit of information exchanged with the other device (yes, even a wall charger has a little software on it that does this). This is where the amount of power that will be provided to the phone is negotiated. There is code in the kernel that requests a certain amount of power based on the device type. Normally, if the kernel sees anything other than a wall charger, it will request a lower current, and therefore a slower charge. The fast charge option simply makes the kernel always request the higher current, no matter what is plugged in. It does this by just assuming that any device plugged in is an AC wall charger and handling it that way. A slight downside to this is that when it does this after being plugged into a computer, it does not set up any other USB connections - so ADB, mass storage, USB tethering, etc., will not work while fast charge is enabled. But, it really does charge crazy faster on a computer that way, so sometimes its worth it.

The short version: LOL, wut?? No, it doesn't matter. No, never charges with all four wires. Whoever told you that was a few tacos short of a combination platter.
[Fascinate General] AuroEdge:
First and last time I take a review on Amazon at face value I spose :)
[Fascinate General] sageDieu:
search "three wolf moon" on amazon for good reviews
[Fascinate General] TomTcom:
Lol! I saw that a while ago. Frickin hilarious!
[Fascinate General] swagooo:
aside from the youtube video problem, i have run into some new problems now.

i tried setting my cpu speeds to 1300 mhz and 400 mhz min and then my device would not boot up correctly. it would load up to the home screen then freeze immediately and reboot indefinitely.

i just reflashed it now and was wondering if anyone else had experienced this when messing with cpu settings? i am using glitched aokp build 38

ty.

edit: just found the new glitched 38 build 6-07-2012 so im gonna try that and hope it fixes things. will report back.

i guess my phones limit is 1200 mhz, still pretty unstable at that. i guess ill try 1000 mhz with live oc at 105-110%. should be ok and hopefully gimme a lil boost.
[Fascinate General] droidstyle:
glitch is my favorite kernel more so because of the quality devs working on it. although I would give the new devil kernel a shot...working really nice for me so far. im seeing more stability when trying to overclock on the devil kernel jmo...
[Fascinate General] swagooo:
what settings are you using? the devil kernel sounds very tempting....:cool:
[Fascinate General] Pixelation:
I'm back on my fascinate, have red recovery installed...running gee wiz 2.8

I tried to flash gummy 1.20 and came into error 07.

What do I need to do to get Gummy on, I followed normal flashing instructions..wiping then flashing...but error 07...

DROID DOES, Apple did...like I forgot when
[Fascinate General] icemanwbs:
Well, not sure what happened but, I flashed the build 38 ( from 37) and ran into a few problems. First , I lost my lock screen, which wasn't really a big deal. Kinda cool actually to just hit power button and go right to home screen. However, I also started having problems with sound, namely the notifications and incoming calls. So after missing a few important calls, I first tried to just flash back to the build 38( without the Devil kernel)....no dice. So I was forced to go back to 37 ( without Devil ). All is right again. I'll try again to upgrade to the 38 build, when I have some time. Btw, I DID wipe all three, ( always do ). :D
[Fascinate General] ztotherad:
nice to see you pix, welcome back! what class is your sd card? and did you try droidstyle's guide?

also, going to a mtd rom (ics) you need to flash ths b1 or b2 (posted in the guide i referenced before, bro) that should set it up for you.

now a question for myself, do i need to go back to stock from mtd gb (omfgb) to get to ics or can i just install ths or go straight to cm9/aokp?
[Fascinate General] mezster:
Both need to flash cwm fixed for cm7. Red cwm won't work. Refer to droidstyle's guide in general forum.
[Fascinate General] ztotherad:
bro, i have cwm fixed 4 cm7

ignore my prior question i went from omfgb to cm9 with no problems
[Fascinate General] Pixelation:
Thank You, figured if make something over this fascinate I barely ever used.

Got it all thanks again just running cm7 for now

Edit: Got it, section 3, thanks again

DROID DOES, Apple did...like I forgot when
[Fascinate General] ztotherad:
bro once you use a samsung device motorola devices are obsolete
[Fascinate General] Pixelation:
I've had the fascinate since October 2010...just never used it much. I had a Droid 2 r2d2 that I bought and used that till I got x2....they are great devices think I liked my charge better, but non the less the fascinate is a nice wifi only app device now :)

On another note, I used Droid styles guide for flashing ics ROMs and when I was trying to flash TH2 it started install then rebooted to recovery. So then I tried TH1...same thing, it didn't install... so i restored to cm7 then noticed my new SD card was damaged... SOOOO I took it out, and stuck it back in :) and bam :) installed

DROID DOES, Apple did...like I forgot when
[Fascinate General] Pixelation:
After restoring eho3 through Odin, flashing cwm 4CM then install ths 2 then Aokp...everything works great, except when I power off...it brings me to recovery. I have noticed this with cm7 & Gummy also. Is there a fix for that, or something I'm missing?

Thank you in advance :)

DROID DOES, Apple did...like I forgot when
[Fascinate General] ztotherad:
it might be mixed up like 'reboot recovery & reboot system' may be mixed up, can you reboot in recovery & get into system?

btw: bro wouldnt it be pretty rad to have aokp/gummy on the x2?
[Fascinate General] Pixelation:
sure, after I do power menu reboot it brings me to recovery, then I reboot from there....I'm wondering about the reboot option in Odin.

I'm also noticing sd card is a POA...have to keep re inserting...

It would be awesome to have those for x2....Gummy is a glorified Liberty, shame Kejar gave up on it... :(

I just hit 3300 on quad advanced with fassy...lol glitch kernel and CPU 1200, min 400....woot

DROID DOES, Apple did...like I forgot when
[Fascinate General] ztotherad:
kejar gave up on gummy or liberty, bro?
[Fascinate General] Pixelation:
Liberty

DROID DOES, Apple did...like I forgot when
[Fascinate General] Pixelation:
X13thangelx and Kejar31 agreed to new Gummy for X2....yw :)

DROID DOES, Apple did...like I forgot when
[Fascinate General] ztotherad:
i saw that bro, thats going to be kickass
[Fascinate General] Pixelation:
Yes yes yes!!!

DROID DOES, Apple did...like I forgot when
[Fascinate General] scarfman4:
I saw on the AOKP thread that some were noticing AOKP latest builds getting hot. I gave official build 39 a try and Spare Parts kept showing my Fascinate running a steady 39-41C. I wasn't playing any heavy graphical games or anything; just surfing the web got it up to 41C, and not doing anything but charging got it up to 39C after it had been off for a while.

Is anyone else seeing this or have any thoughts as to why this is happening?
[Fascinate General] scarfman4:
Also something I've noticed on AOKP builds I've tried is if the phone is off and I plug the charger in, the power button acts like it's disabled. On TW roms if I press the power button it will show the battery level status and if I press or hold it again it will power up. With AOKP the power button does nothing until I unplug the phone.

Anyone else seeing this? Is it just an AOKP thing or do CM9 roms also have this issue?
[Fascinate General] swagooo:
I just flashed over to build 39 of the glitched aokp rom family.

I was having a little issue with build 38 where during a call if I was using the speakerphone and I adjusted the volume, it would adjust the volume but also turn off the speakerphone but still leave the speakerphone button on. So, I would have to turn speakerphone off, then back on again every time I adjusted the volume of it.

Hopefully this build fixes it, if not, ill report back.
[Fascinate General] Hypnosis4U2NV:
Does the same for me..

Sent from my Commodore 64..

READY.

load"*", 8,1
[Fascinate General] rjkxb2:
This is most likely a noob question but is it "safe" to flash the newest AOKP over CM9 Kang and vice versa? (As long as I wipe data, cache, dalvik of course) I can't Odin or anything but want to test out AOKP. Just wondering how likely it is I'll run into a problem. Currently on CM9 Kang with Glitch V14 B6
[Fascinate General] sageDieu:
yes should be fine
[Fascinate General] rjkxb2:
Well no problems flashing to build 40. Devil .85 booted up and is running well. I read other builds had looping problems.
[Fascinate General] xHoLyx:
is it just me or you can't read other languages?

Sent from Inc 2 using Tapatalk 2
[Fascinate General] sageDieu:
can you give an example? a screenshot or link or something?
[Fascinate General] ncmcken:
@sageDieu, I can't post in the Development section, but wanted to reply to your post pasted here:

"has anyone else noticed Widgets not updating in Nova? I'm running the same Nova version as I did in build 38, but since I switched to 40 I haven't seen my clock widgets update hardly at all. I've tried my MIUI Weather clock as well as the stock ICS digital one".

I had the same problem and what fixed it for me was using TiBu option of - Integrate sys Dalvik into ROM - Could just be a coincidence, but widgets haven't had a problem since.
[Fascinate General] sageDieu:
just tried that, thanks, will report back.
[Fascinate General] Merman1983:
Anyone else having problems running the new version of Chrome? Used the betas just fine, but now I get an error every time I try to run it (I've reinstalled several times and even reverted to a beta via Titanium and no dice)

Running AOKP 38 Glitched + Devil .79

Error I receive "Critical functionality required to run Chrome is missing; either your Chrome installation is incomplete, or not compatible with this version of Android."
[Fascinate General] AuroEdge:
What release is the latest that is clear of the recent bugs? It's not clear to me which have the issues. I've experienced the SMS problems on 40.1.
[Fascinate General] droidstyle:
build 40 works great here...using the devil_.85 kernel. also you might try the latest skunkworks kernel.
[Fascinate General] MunkinDrunky:
I need so input in trying to diagnose my experience with a possible sleep of death, since i've never experienced it before.

I just upgraded a week ago to the ICS experience with the Gummy 1.2.0 rom coming from a long time use of PWGB and my phone has never run better, liking the feel of Gummy so far. Might try something later, but for now Im stickin with it.

The other night I powered off my phone then went to sleep. It was at 48% battery. I tried to power it on the next day and it was totally unresponsive to the power button. Thought it might be dead so I plugged it in to the ac charger. Gave it 10-20 minutes to try the power button again and it was still not responsive. Unplugged and tried-still nothing. Figured it needed a battery pull, did it and it responded and powered back on. It was 37% now. I fully charged it and powered it off for the rest of the day. Next day I powered it on again, this time it was responsive, but down to 8% battery life!? Will sleep of death sap that much battery when it is off?! Else I think I must have a bad battery (it the one it came with 2yr ago) or improper charging.
[Fascinate General] MunkinDrunky:
I haven't experienced any more non-responsive behavior, so I have some other questions. If I have read correctly the Gummy rom uses the glitch v14 kernel and I can see that in the phone info. I also read that changing the cpu clock speed and voltage requires Ns tools, i think, for this kernel. However, I see those controls in the gummy settings. Can I just set them from there? Will a nandroid back up restore properly if anything goes wrong with clock speed changes?
[Fascinate General] droidstyle:
you need nstools to adjust live oc and i/o scheduler with that kernel.

yes nandroid will save voltage settings, so make sure your setup is stable before making one.
[Fascinate General] sageDieu:
ditto to droidstyle on nstools.

as for battery, it is possible that the battery is just old and beginning to lose its charge just over time, you should look into extended batteries or at least a replacement for the stock one. it is just as possible that there is some kind of drain going on just from leaving it in the phone, so next time you want to power it off overnight or whatever try just taking the battery out after it turns off, then when you want it to turn back on just put it back in and turn on.

that's a definite way to see if it is the phone pulling power while off or if it's just an old battery not retaining its charge.
[Fascinate General] MunkinDrunky:
Yup battery must be bad or how the battery level being read is wrong. Just a few minutes ago turned it off at 48% then right back on, only to see it was at 7%! I have an extra battery now and need to charge that, then try to make sure its just a battery issue.

The other weird thing that happened right before that was when I was using my Google maps with gps. I do this occasionally just to test lock speed and accuracy, since before ICS my gps never worked. Took a minute to lock then put me in far Northern Canada (definitely not in Utah where I'm at) moving fast- my arrow was flying over all those icy lakes at an unreasonable rate. Any ideas? Im probably just going to odin and start fresh.

should mention I also have a DX2 and it will always lock in seconds, even indoors. I test both together since i am seeking reliable gps on my fascinate. Ive been reading about gps fixes but they are a bit dated for the gingerbread mostly. What would work in any of these ICS roms?
[Fascinate General] sageDieu:
dunno about the GPS but also note that there is a common issue with the battery showing the wrong level if you reboot with wifi enabled.
[Fascinate General] MunkinDrunky:
I re-downloaded all the files except the Samsung drivers and odined back then reflashed. GPS is perfect and no battery trouble either. First time must have been a bad download because odin failed a lot. This time no trouble at all. Thanks for the tip on the wifi too- I had no idea and left it on almost all the time.
[Fascinate General] AuroEdge:
Does the devil kernel in MS6 have a wake lock bug which has been fixed?
[Fascinate General] tonu42:
i use my fascinate as an extra device for music or what ever, and the battery drains completely from 100 all the way to 0 turned off. Any one know of a fix?
[Fascinate General] droidstyle:
Yup... same thing here.
[Fascinate General] tonu42:
this is mega weird. Happens right after I get my gs3 too
[Fascinate General] NPOA556:
What ROM/kernel are you running? I have had terrible battery life since switching to AOKP a few months ago. With almost no phone usage, wifi & mobile data off most of the day, my battery might last 10-12 hours from a full charge. It used to go 2 days on the stock GB ROM. I am running AOKP 40 w/ Devil 0.99. There has been some discussion of battery life in the AOKP thread, but every time someone brings it up, everyone jumps on them and tells them it is just their usage habits that cause short battery life. I don't believe that, as I do not use my phone much all day while at work. The battery stats say that the Android OS is by far the biggest consumer of battery. That tells me it is the ROM or kernel. I am not using LiveOC or doing anything fancy with the settings. Also, I am using an 1800mAh battery already. Other than trying a newer version of the ROM and/or kernel, what can I do? I had trouble restoring apps when I tried to flash AOKP MS6, so I just stuck with 40 because I don't have any problems other than poor battery life.
[Fascinate General] droidstyle:
I think you misunderstood whats being said...my fascinate gets good battery life while powered on. However, since upgrading to the gs3, my fascinate discharges a full charge in a day when powered off(Never knew this because I never left it off for a full day before). Pretty sure Tonu has the same issue.
[Fascinate General] NPOA556:
Sorry for the confusion. That is really strange, Obviously I can't offer any insight into that issue.

Regardless, I would still like some help/suggestions with my battery life problem. I just checked battery stats and saw that Android OS has used 53%. With screen and data off, I will lose ~8-10% an hour. I know that is not normal, and others do not seem to experiencing this. Do I just need to flash something else and see if it fixes it? Are there some settings that would have a big impact? Like I said, I am not overclocking or doing anything fancy for extreme performance. I could list all settings if it would be helpful.
[Fascinate General] tonu42:
You also got a gs3? than this is mega weird, I'e never heard of such a thing like this before any where.

UPDATE: Heres a temp fix. I turned off my device, pulled battery, reinserted, next day over night it was at full battery.