[ROM][ICS][7/9] Android Open Kang Project Fascinate Milestone 6 (4.0.4)

Search This thread

ssewk2x

Senior Member
Oct 24, 2010
1,382
1,392
Detroit, MI
OnePlus 8T
Google Pixel 8 Pro
ive been flashing and restoring this way since build 26 withno issues. i wipe data, flash latest build + gapps, boot once, reboot recovery, advance restore data only. for some reason I have always had less issues doing this method as opposed to a actual dirty flash. although coming from build 33 to 34 I wiped caches and flashed with no issues.

Wow .. you've been getting lucky. If it works, then great. But if it doesn't, wipe. That's what I always say, anyway.

i dont think you need to go all the way back to stoc, just wipe data and reflash b34...

This ^^, plus don't do that data restore. Here's what I do about recovering from a data wipe:

1. make a tibu of all apps + system data
2. any apps that have their own backup options (apex / nova do, for example), go through and do that.
3. make sure I know my google account passwords!!
4. hold my breath and do the data wipe. reboot.
5. once i'm back, do the whole google sign-in, set up my phone. If I have access to wifi, let the market restore my apps.
6. for any apps that have their own backup options, go through and restore their settings.
7. in TiBu, restore any apps that didn't get restored by the market (a few happen like that), but DONT RESTORE ANY OF THEIR DATA YET.
8. for a very select few apps (OI Safe, OI Notepad, llama, alarm clock +, OI shopping list, and a few others I use) use TiBu to restore data only. Err on the side of NOT restoring data in tibu.
9. Re-configure any apps that require accounts / logins by hand.

Do that and you'll probably be reasonably ok.

Also, I hate wiping data, so I don't do it unless:

1. the OP says it's absolutely required. Sometimes I try to get away with avoiding it, but I usually get burned.
2. if I get burned on option 1, or if I start to experience boot loops or other bizarre behavior right after flashing, and a dalvik / cache wipe doesn't clear it up.

Also also, I *always* wipe cache and dalvik whenever I flash anything. In fact, I have a zip file that does it for me automagically.

---------- Post added at 10:54 AM ---------- Previous post was at 10:10 AM ----------

There's also an auto-rotate enable setting under System Settings -> Accessibility. I spotted it this morning. Maybe that's one that some have missed who are having auto-rotate issues?
 
Last edited:

droidstyle

Inactive Recognized Contributor
May 7, 2011
6,471
3,604
Fort Wayne
Wow .. you've been getting lucky. If it works, then great. But if it doesn't, wipe. That's what I always say, anyway.



This ^^, plus don't do that data restore. Here's what I do about recovering from a data wipe:

1. make a tibu of all apps + system data
2. any apps that have their own backup options (apex / nova do, for example), go through and do that.
3. make sure I know my google account passwords!!
4. hold my breath and do the data wipe. reboot.
5. once i'm back, do the whole google sign-in, set up my phone. If I have access to wifi, let the market restore my apps.
6. for any apps that have their own backup options, go through and restore their settings.
7. in TiBu, restore any apps that didn't get restored by the market (a few happen like that), but DONT RESTORE ANY OF THEIR DATA YET.
8. for a very select few apps (OI Safe, OI Notepad, llama, alarm clock +, OI shopping list, and a few others I use) use TiBu to restore data only. Err on the side of NOT restoring data in tibu.
9. Re-configure any apps that require accounts / logins by hand.

Do that and you'll probably be reasonably ok.

Also, I hate wiping data, so I don't do it unless:

1. the OP says it's absolutely required. Sometimes I try to get away with avoiding it, but I usually get burned.
2. if I get burned on option 1, or if I start to experience boot loops or other bizarre behavior right after flashing, and a dalvik / cache wipe doesn't clear it up.

Also also, I *always* wipe cache and dalvik whenever I flash anything. In fact, I have a zip file that does it for me automagically.

---------- Post added at 10:54 AM ---------- Previous post was at 10:10 AM ----------

There's also an auto-rotate enable setting under System Settings -> Accessibility. I spotted it this morning. Maybe that's one that some have missed who are having auto-rotate issues?

Yea I agree the steps you listed is pretty much text book...normally I try the method I previously posted first, then if wierd **** starts its time to wipe data and restore apps only thru tibu and contacts thru google...Up until build 26 or 27 thats what I had to do everytime, but the last few builds dont seem to mind a little dirty flashing :D
 

philthy

Member
Jun 15, 2010
21
0
Within build 34's zip, can I delete the following file, /system/media/boot_audio, without affecting the flashing process? Or is the file necessary for flashing.

Also, is there an option with settings to disable boot audio?
 

kallell

Senior Member
Apr 11, 2009
630
82
Within build 34's zip, can I delete the following file, /system/media/boot_audio, without affecting the flashing process? Or is the file necessary for flashing.

Also, is there an option with settings to disable boot audio?

Ya, in rom control i believe. Disabled by default unless steve changed it.
 

ljbrenes

Senior Member
Feb 10, 2011
342
26
MI
Why am I not getting voice guidance when usging the GPS!!!!!!

I have tried going to maps first, I have installed ivonia text to speech, nothing! no voice!! Funny thing is, it worked the very first time I used navigation, and then never worked again!

Help please?
 

JoeDat

Senior Member
Jan 5, 2011
164
33
For the life of me, I cannot get multiple PCs (all of which were fine and haven't changed) to recognize the phone with USB debugging enabled. None of them can detect the device with the 'adb devices' command. I've tried everything. I even went so far as to Odin back to stock and start from scratch. I removed and reinstalled the Samsung and Google drivers from the SDK. Nothing works. Is anyone else seeing this on the latest build?
 

ccmichael

Senior Member
Oct 11, 2010
116
27
Try disabling and reenabling your usb devices within Windows Device Manager.

Sent from my SCH-I500 using XDA
 

JoeDat

Senior Member
Jan 5, 2011
164
33
Try disabling and reenabling your usb devices within Windows Device Manager.

Sent from my SCH-I500 using XDA

I actually tried wiping them out completely, rebooting, and letting them reinstall. Something I've done in the past to clear up an issue like this. No dice this time around.
 

HuskerDad3

Senior Member
Feb 11, 2011
51
8
Lincoln, NE
For the life of me, I cannot get multiple PCs (all of which were fine and haven't changed) to recognize the phone with USB debugging enabled. None of them can detect the device with the 'adb devices' command. I've tried everything. I even went so far as to Odin back to stock and start from scratch. I removed and reinstalled the Samsung and Google drivers from the SDK. Nothing works. Is anyone else seeing this on the latest build?

Having same problem here. Tried turning fast charge on, then off, and rebooting...no luck.
 

JoeDat

Senior Member
Jan 5, 2011
164
33
Having same problem here. Tried turning fast charge on, then off, and rebooting...no luck.

So, I have a GTab p4wifi (GT-P7510). I have the drivers for that, but not installed on my PCs I'm sitting in front of. I installed that driver. Boom, it's working. The drivers installed using the standard Fassy package from Samsung are no longer picking up the adb bridge on this phone for me for some reason. Dunno why.

Give these a try. Can't hurt. You can always reinstall the old drivers.

http://org.downloadcenter.samsung.c...72/GT-p7510_USB_Driver_v1_3_2360_0-Escape.exe
 
Last edited:

dallas6672

Senior Member
Aug 13, 2011
79
22
Is there anything smoother than butter? I think maybe my Fascinate at the moment.:D

Anyone else's Wifi & Airplane mode status bar icons get tiny when they're both enabled. Tried a data wipe and reflash but still does the same thing.

Screenshot_2012-04-25-14-59-30.png
 
Last edited:

gt43aw

Senior Member
Jan 4, 2012
133
35
For the life of me, I cannot get multiple PCs (all of which were fine and haven't changed) to recognize the phone with USB debugging enabled. None of them can detect the device with the 'adb devices' command. I've tried everything. I even went so far as to Odin back to stock and start from scratch. I removed and reinstalled the Samsung and Google drivers from the SDK. Nothing works. Is anyone else seeing this on the latest build?

Try pulling battery, plug in and put in download mode so computer recognizes it. Then put battery back in reboot and see if it works.


Sent from my SCH-I500 using XDA
 
  • Like
Reactions: JoeDat

Top Liked Posts

  • There are no posts matching your filters.
  • 80
    Do to the total disregard for the flashing instructions and some individuals trying to find answers without attempting to find it themselves first. I have come up with a list of things I except to see before I will even acknowledge a question from here on out.

    If you have a Question try these first.

    1) You must me on the most recent Devil up build. Questions about AOKP Official builds or older Glitched builds should be referred to the most recent Devil up build first. Verify you are on the right ROM having people complain about having a mesmerize on the Verizon network or not getting data/mms because they flashed a Fascinate ROM is ridiculous. If you don't even know what device your on you shouldn't be flashing custom ROMs.

    2) You should try a redownload of the ROM and Gapps, a wipe of data, dalvik, and cache, a flash and a test of the problem before restoring apps or data. That includes the back this phone up option in the gaps installer. Don't check it that until you test your issue.

    3) If you problem is with a single app delete it and redownload it from Google play.

    4) Read the OP and the last 10 pages of the thread completely, if your answer is there your question will be ignored. It will take you just as long to read those pages as it will for me to find it and copy it or re type it.

    5) Believe me when I say I take a lot of pride in this ROM. We use this ROM everyday. We test every feature before it's released. If you say you are having an issue and we tell you it's not the ROM…. It's you if you try and argue that your posts will be ignored.

    More be added if stupidity incurs. Have a nice day.

    Love,
    Steve. :)

    Thanks goes out to JT, Sbrissen, Romann, Sixstring, TKGlitch, Efpophis and more may be added.
    aokptitleblue-1.png

    I want to thank CyanogenMod and Team Hacksung for doing such an awesome job on getting ICS on the captivate. This project would be nothing without their contributions.

    changelog-2.png

    Newest change logs are available at the AOKP site
    installation-1.png
    1. Make sure you're on CWM fixed for CM7
    2. MAKE A NANDROID
    3. wipe data/factory reset in recovery
    4. flash ROM if you're on ICS, if not flash this THS build 2 first
    5. flash Gapps
    6. reboot
    downloads-4.png

    Download HERE http://forum.aokp.co/

    Official AOKP Builds www.aokp.co
    ^^^ Built with Latest SW Glitch and the regular gcc 4.4.3 toolchain

    Devil builds for Fassy, Mez and Show http://android.encounterpc.com/stevespear426/aokp/
    ^^^ Built with Latest Devil (.99) and the Linaro 4.7.1 toolchain


    contribute-1.png

    We spend countless of hours doing this for next to nothing. Posts, views, and donations encourage me, and everyone else who helps out.

    Donate to Me
    Donate to Romann
    Donate to Whitehawkx
    Donate to Jonathan Grigg
    Donate to Zaphod-Beeble
    Donate to ProTekk

    Donate to CyanogenMod

    Every donation is cherished and loved.

    If you'd like to help contribute by writing code, feel free to stop by IRC and talk to us!
    source-2.png

    Check out the ROM source on github. Open source, in the spirit of community kangage.

    If you'd like to help with AOKP, please don't hesitate to contact me. I'd love to get as many developers in on this as possible!


    submit features or report bugs here

    Best way to help out or contact us is via IRC.

    Build 26 2/28
    Fixed- Red Box, Bootani
    Added- Nova, Unicorn Porn(livewallpaper-SFW)

    Build 27 2/29
    Fixed Signal Bars
    Fixed AriesParts

    Milestone 4 3/8
    Phantom Ringer work around

    Build 28
    Bugmailer fixed
    Reboot menu swapped around and fixed.
    Compass fixed - Credit Sbrissen

    Build 31
    Everything I dunno
    Autobrightness smoothing phase 1
    Compass for ICS apps like Gmapps
    BigRam Glitch Kernel
    DataData fix script (just run "datafix" as root in you terminal and take direction from there if you run out of space)
    and more stuff ill add when I remember.

    Build 33
    1) Nav Bug fixed
    2) Init.d fixed for real this time.
    3) Autobrightness Phase 2
    4) Adb over network
    5) Boot audio added

    Build 34
    1) Efpophis fixed notification sounds and ringer sounds, also fixes the boot_audio drop off.
    2) Jpeg-turbo - instead of explaining it just go mess around in your gallery or contacts or anything with jpeg processing. Try and bog it down… I DARE YOU!
    3) Some stability improvements for video and camcorder.
    4) Decreased min auto brightness, and increased the max. I haven't messed with the light sensor poll so if you want it to change faster set the sample interval in custom brightness settings.
    5) Added BLN back to its old Glitchy glory for blinking notifications and all that jazz. Good spot Efpophis.
    6) New settings for Davlik heap size.

    Milestone 5
    1) Turned boot_audio off by default
    2) Updated to 4.0.4 r1.2

    Build 35
    1) Theme Engine
    2) Hybrid UI -> if you want to use Hybrid UI Please Readme

    For some reason build 35 doesn't like some apps on the SDcard if you are getting Acore FCs logcat the next force close and move the app responsible to the phone memory.

    Build 35.1
    DROPPED HYBRID FOR NOW
    Fixed themes and the acore force closes due to apps on the SDcard.

    Build 36-38
    Now builds SW kernel fresh in every build
    No more wifi scan internal, now wifi scans in background
    Sbrissen fix for split SMS
    maybe more can't remember

    Build 39
    Official support for Mesmerize and Showcase.

    Build 40
    Switch to the Devil kernel
    Using Linaro 4.7.1 toolchain

    Milestone 6
    Init.d appears to still be broken if you want/need it push this to /init.d

    Official build has Glitch and the regular toolchain, Devil has Devil (.99) and the linaro toolchain. Both kernels are interchangable so find which rom/kernel combo works for you and sit tight while we wait/work on Jelly Bean.
    36
    We had a meeting last night. Ok so here is the plan. Milestone6 will be aokp's last ics build. We start on jelly bean after the source drops. Milestone6 will come with 2 options the official non linaro build for those with issues, and I will put out a linaro build for those who want it. I will include the latest devil kernel, and from here until jelly bean look too the devil for kernel updates. He had assured me he will be making devil kernels for jb. No etas, we are waiting for the source drop.

    sent from my devil unicorn
    33
    Linaro milestone 6 is in the oven it wont be out until tomorrow morning so I can test it. it will come with devil 99 unless there is an issue. As you guys know this is our last ics build so I gave you all the options you could ask for as far as linaro/glitch/devil combinations find the one that works for you and sit tight for JB.
    25
    For those of you who aren't on Twitter... (ask yourself why) JT has got the fascinate up and running on CM10 (everything but GPS) he should be posting a build shortly (next few days...) He's also dropping his source (why I love him and also why everything I do is 100% open) so you guys should be getting so CM10 and AOKP love on Jelly bean very shortly. Congrats on staying alive through another update fassy owners...
    23
    OP updated with new/last ICS builds. See you guys on the other side.