yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] Relaxasaurus:
Anyone else getting bootloops?

Wiped data/caches, installed Build 34, Gapps. Phone always boots into blue recovery.

*Repeat*

?_?

Ps- Just noticed the Glitch splash screen tries to load a split second before blue recovery. Gonna flash the THS build and start from scratch & cross fingers >_<

Pps- aaaand flashing THS build 2 didn't work. First time I bricked my phone, woohoo!
[Fascinate Android Development] Stephen.k.spear:
Did you 3 finger to recovery?

Sent from my Glitched AOKP Unicorn.
[Fascinate Android Development] AmanteNJ:
New at all this ICS roms ... just wondering if i need to wipe data every time a new build is released.
[Fascinate Android Development] Relaxasaurus:
Nah didn't do that, may have been an issue coming from 29? No idea.. but I'm in the process of Odin'ing now...
[Fascinate Android Development] yeahdude38:
Highly recommended to avoid any boot loops or any other problems. Just backup your apps with titanium backup so when your new rom is installed you can put all your apps/data right back quickly.

Its like you never lost anything....
[Fascinate Android Development] Robtao:
Would there be any advantage to this:

1. Wipe Cache & Dalvik

2. Make Nandroid (cleaner?)

3. Wipe Data

4. Flash ROM

5. Advanced Restore Data only

Or would it be the same as wiping after the restore?

Somewhere I got the impression that the new ROM might play nicer with the cleaner restored data if Cache & Dalvik were wiped previous to the backup.

If it doesn't make any difference to the ROM to wipe before the backup versus after the restore it is probably a waste of time.
[Fascinate Android Development] sageDieu:
to be fair, I keep updated titanium backups in case anything goes wrong, BUT I have dirty flashed every rom since build 26 of aokp. I have not done a data wipe since build 28. that includes every official build, and many test builds steve sends me.

I dirty flashed cm7 to get out of a bootloop, I'm lazy as hell, and it worked. all my ics apps and stuff were there. dirty flashed back into ics after that. some people seem to be getting bootloops for not wiping data, but my laziness is proof that a data wipe is not always necessary.
[Fascinate Android Development] AmanteNJ:
I did that from 31 to 32.1 and some apps wont even lunch, They are installed but cant be accessed
[Fascinate Android Development] Robtao:
So the "cleaned advanced Nandroid Restore data only" procedure may be only a placebo and actually provides the same results as a dirty flash. And some of us just get lucky and I may sometimes be one of those. Maybe based on apps installed.

or, is it possible to improve the odds of the data only restore working? It is pretty quick, and I am lazy too.

Anyone with any evidence to support either theory? I know my limited knowledge of what goes on in a backup, restore, wipe, or flash leaves me pretty much at the mercy of a well stated opinion, and I bow from the waist to anybody who really knows what's going on in there.:)
[Fascinate Android Development] bobthesalesclerk:
Tried. Still no auto rotate. I am going to flash back to stock when I get home and just start over. I never realized how much I use it until I lost it lol.

Also apps still auto rotate fine but I have to go into nova settings and force portrait to get it back.

sent from my ice cream sandwiched Samsung fascinate
[Fascinate Android Development] shorttripp86:
After flashing the latest Glitched version of b34, whenever I boot into recovery it takes me to the blue CWM (THS-style recovery, not the stock blue recovery) It happened after i chose to only wipe cache/dalvik when I upgraded from b33. Tried wiping all three and reflashing next and it still happens.
[Fascinate Android Development] Stephen.k.spear:
All the AOKP roms use of blue recovery always have.

Sent from my Glitched AOKP Unicorn.
[Fascinate Android Development] sageDieu:
all I know is, I'm lazy and never ever wipe anything and have no issues. I just was on build 33, flashed 34, gapps, kernel and a bunch of inverted apps without wiping anything and it all works fine.
[Fascinate Android Development] droidstyle:
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.

---------- Post added at 09:13 AM ---------- Previous post was at 09:11 AM ----------

i dont think you need to go all the way back to stoc, just wipe data and reflash b34...
[Fascinate Android Development] djk21108:
It's so fast. Great work guys. Dirty flash is fine for this one. Nice job sneaking Terminal Emulator in there as well.
[Fascinate Android Development] ssewk2x:
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?
[Fascinate Android Development] droidstyle:
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
[Fascinate Android Development] philthy:
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?
[Fascinate Android Development] vlucchetti:
settings-rom control-general UI-disable boot audio. Just check the box.
[Fascinate Android Development] kallell:
Ya, in rom control i believe. Disabled by default unless steve changed it.
[Fascinate Android Development] shorttripp86:
Oh okay, nevermind then. I guess I was expecting the Glitch style red recovery since its the Glitched AOKP version. Thanks
[Fascinate Android Development] icyhandofcrap:
Nope I have that on.
[Fascinate Android Development] ljbrenes:
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?
[Fascinate Android Development] JoeDat:
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?
[Fascinate Android Development] ccmichael:
Try disabling and reenabling your usb devices within Windows Device Manager.
[Fascinate Android Development] JoeDat:
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.
[Fascinate Android Development] Stephen.k.spear:
Did you turn off fast charge?

Sent from my Glitched AOKP Unicorn.
[Fascinate Android Development] Stephen.k.spear:
We got something way better than red glitch recovery now.... Hahahaha! <- evil laugh...

Sent from my Glitched AOKP Unicorn.
[Fascinate Android Development] JoeDat:
Yessir. I can mount my storage on my PC, no problem. MTP and UMS both work. It's just not recognizing the ADB bridge.
[Fascinate Android Development] HuskerDad3:
Having same problem here. Tried turning fast charge on, then off, and rebooting...no luck.
[Fascinate Android Development] JoeDat:
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
[Fascinate Android Development] dallas6672:
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.
[Fascinate Android Development] gt43aw:
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.
[Fascinate Android Development] shag_on_e:
Yeeeah! I knew y'all could pull it off!

~~~~There is no spoon~~~~
[Fascinate Android Development] gt43aw:
Whatever phone you buy next, that's the phone I go to. I can upgrade now, but I'm in no rush until I know what phone youl all be developing on.
[Fascinate Android Development] steve2711:
Boot mp3

Stephan,

34 is very slick, and with a cache wipe only all works beautifully, in fact I donated. BUT, can you offer the previous 33 Boot mp3 of the Rolling Stones, as an alternative? Thanks for your amazing work.
[Fascinate Android Development] JoeDat:
That's actually a good suggestion, although I've resolved it already (posted above)

http://xdaforums.com/showpost.php?p=25309382&postcount=1636

It would be worth it to try your suggestion first for others seeing the same problem.
[Fascinate Android Development] neh4pres:
What kernel are you flashing? And why
[Fascinate Android Development] sageDieu:
That's classified information, if I told you I'd have to kill you.
[Fascinate Android Development] neh4pres:
I haven't flashed 34 yet.. But now I know to back up the boot audio.. It went very good with the new boot ani
[Fascinate Android Development] neh4pres:
I'm prepared to defend myself, and am willing to take the risk
[Fascinate Android Development] ljbrenes:
all of my gapps fc after I flashed build 34
[Fascinate Android Development] bobloblaw1:
Way to go guys on the secret. I think everyone will be quite pleased.
[Fascinate Android Development] neh4pres:
What secret?
[Fascinate Android Development] rkerrddd:
Ver 34 loving it
[Fascinate Android Development] bobthesalesclerk:
Build 34 is solid. Everything is working. Data wipe solved my rotation issue. Thanks everyone.

sent from my ice cream sandwiched Samsung fascinate
[Fascinate Android Development] sixstringsg:
Have I not said yet in here that Smasher got TWRP working? Well, he did, and I will release it soon in the Glitch thread.
[Fascinate Android Development] yeahdude38:
flashed over from build 30 to 34 today and my question is did you add some kind of sound volume or something? as soon as i activate volume+ my music gets very distorted so i need to turn it off. on build 30 it was great and i got my volume tuned perfectly for music. what can i either disable and/or tune for my audio now to have a boost or be able to use my volume+ again?? volume boost is necessary with this new bigger case for my bigger battery.
[Fascinate Android Development] ssewk2x:
You should be able to modify your volume+ settings and dial it back in. I did fix an audio issue in the kernel that was causing everything to basically think it was running thru headphones! Fixing that has naturally boosted the volume of almost everything (except call audio - I'm still looking at that).
[Fascinate Android Development] yeahdude38:
Yea i been tryin to screw with it but no luck. Only time it sounds good is without volume+ but no more awsome loudness. Could it have something to do with this dspmanager app thats been added to the rom now??? Or is it system side maybe?
[Fascinate Android Development] StuckinMemphis:
I had the same thing happen. I flashed without a data wipe just cache and dalvik. So I wiped cache and dalvik again, reflashed gapps and everything is good.

Build 34 working great on the Showcase by the way.
[Fascinate Android Development] dave3588:
Niceee!!!!
[Fascinate Android Development] ssewk2x:
That's a possibility. There's dspmanager and music fx both...you might want to make sure those are both effectively disabled, too.

That said, I've got volume+ also, and everything still sounds great...i did have to back the max volume off a bit, tho. I have it on 8 now, down from 10.
[Fascinate Android Development] yeahdude38:
Backing down to 8 sounds decent with "good quality" eq setting. I guess im used to 13 so it made a huge difference to me. Ill play around and freeze those 2 with tibu to see wat happens. If nothing then oh well. Not the end of the world lol. Thnx for the help...
[Fascinate Android Development] fulaman:
Do you guys think V6 Supercharger is necessary for Build 34 glitched?
[Fascinate Android Development] Deliquified:
Fairly certain dspmanager and volume+ conflict as they both are software eq mods (correct me if I'm wrong) where as voodoo sound is hardware eq. Gotta pick dsp or volume+, not both. The best sound quality settings I've found is deleting musicfx & dspmanager app, and run voodoo sound at +0, tune speaker for music, and under volume+ select good quality setting and customize it with volume set to +7, bass and echo at 0. Turn your phone volume down 2 clicks from max for non bassy songs, and 3 for bass heavy. Should sound great with minimal/zero distortion. Hope this helps everyone.
[Fascinate Android Development] djk21108:
I must say, this is some pretty absurd battery life I'm getting. Haven't seen anything like this before.

http://imgur.com/a/Yl3tX
[Fascinate Android Development] kallell:
Personally, i don't think you'll see much of a difference at this point.
[Fascinate Android Development] gt43aw:
Did u remember to reflash gapps?
[Fascinate Android Development] nothingblooms:
Which Glitch thread would that be?
[Fascinate Android Development] TomTcom:
Loving 34. I came from gummy. I followed directions and everything worked perfectly. No outstanding issues I can think of. Thank you.
[Fascinate Android Development] Stephen.k.spear:
Not released to the public yet. We like to play with it and tease for a while first. :-)

Sent from my Glitched AOKP Unicorn.
[Fascinate Android Development] sixstringsg:
The only Glitch thread there is...
[Fascinate Android Development] Stephen.k.spear:
You can put any mp3 you want in system/app boot audio

Sent from my Glitched AOKP Unicorn.
[Fascinate Android Development] nothingblooms:
Thanks Stephen! I figured it wasn't quite ready yet :)
[Fascinate Android Development] Stephen.k.spear:
I think six is going to put out an official glitch kernel with twrp recovery soon, and if all goes well you'll see it in the roms shortly after. These recovery don't build like the old ones so smasher made stand alone recovery.imgs I figured out how to include them in the glitch kernel builds but the roms have been giving me trouble... I'll figure it out though don't you worry.

Sent from my Glitched AOKP Unicorn.
[Fascinate Android Development] sageDieu:
so does that mean we might also be getting updated glitch? I know tk is always hard at work, wonder if there is anything new we could get.
[Fascinate Android Development] sixstringsg:
Remember that belongs in the kernel thread, not here.
[Fascinate Android Development] phxshadow:
Need help just installed b34. but can't activate phone there is no dial pad after placing call to press one to activate. Any help appreciated
[Fascinate Android Development] TCStehle:
Dial *22899 to activate and update prl.
[Fascinate Android Development] phxshadow:
Thanks got it activated !!!

Google is down what a bad time.
[Fascinate Android Development] k_nivesout:
I've never had to activate after flashing a rom, the only time I use *228 is for the occasional PRL update. Guess I was just curious if there was a reason for the activation?
[Fascinate Android Development] m771401:
I just want to say thanks for all that you guys do.

I initially loaded the B34 ROM from AOKP site but I wasn't seeing the boot audio option for example. I noticed that the kernel was dated 4/21.

So I loaded the B34 Glitched version and so came with it the boot audio option and what not.

So I'm a little confused. What kernel is suppose to be in B34-AOKP and does it not include the boot audio, jpg enhancement, etc that's been recently mentioned?
[Fascinate Android Development] HuskerDad3:
Thanks, found that the problem was my usb hub. Duh.
[Fascinate Android Development] vlucchetti:
Going to gush about this build. Outstanding job.

Sometimes you get builds that are just okay, sometimes one with a neat feature, but to have so much in one build that runs so well, you just shake your head in wonder and amazement at the talent behind it all.
[Fascinate Android Development] Stephen.k.spear:
1) boot audio is not kernel related it frameworks.

2) The device trees I use for the glitchy builds were not the AOKP device trees. I use my own because it takes to long for gerrit to push stuff through.

3) I guess what I'm saying is just use the glitchy builds it will have the most up to date kernels and goodies.

Sent from my Glitched AOKP Unicorn.
[Fascinate Android Development] m771401:
Thanks for the clarification.

Sometimes it's hard to make the distinction.
[Fascinate Android Development] drose6102:
Once again bravo... Everything working great.
[Fascinate Android Development] dandog96:
Can somebody tell me why my battery life is so poor? I can barely make it through a day. I cleared battery stats....
[Fascinate Android Development] droidstyle:
depending on how old your battery is, it could be on its way out. batteries lose life overtime.
[Fascinate Android Development] ssewk2x:
Also, consider the glitched builds to be very bleeding edge. There's also usually stuff in the kernel that hasn't made it into official glitch yet (but will next time glitch gets an official update).
[Fascinate Android Development] yeahdude38:
Quick question for u big battery guys. Reading a few pages back you guys are only using about 3% ish battery over night while your sleeping. What settings do u click in the rom to get this? My big battery seems to be using around 15% ish while its sittin for the night. 3500mah gorilla gadgets battery. Thanks
[Fascinate Android Development] dandog96:
Its definitely not that, the decrease in battery life started with this rom.
[Fascinate Android Development] kallell:
After a long battle with sepsis, she finally died.

4 days, 18 hours, 25 minutes on my 1800 mah battery. I suspect you could easily push this to a full 5 days with no usage other than it being on.

I know most of you will say "OMG that wasn't under a normal usage, blah blah." Yes, I know this. This is pretty light usage, only using my phone when i absolutely needed to - taking phone calls, sending a text or two, taking screenshots, etc. However, I wanted to see how long my battery would last if i wasn't sitting here raping my phone all day longs browsing reddit, playing games, or remoting in to my home pc.

Either way, this is damn good battery life. In the past, I have been accustomed to having at minimal 2-4% drain per hour even when my phone is completely idle and unused - especially while sleeping. In the end, this resulted in a LESS THAN 1% (computed to ~.87 %) battery drain per hour , with some minor usage worked in. That's pretty damn good.
[Fascinate Android Development] shag_on_e:
That is insane! Even for light use. I have noticed lately that my phone goes into deep sleep very quickly now, and if that screen is off power consumption almost stops. Back in the day she would suck down 30% sleeping. We've got the dream team hooking us up, that's for sure.

~~~~There is no spoon~~~~
[Fascinate Android Development] shelby04861:
Thumbs up on that post. Your numbers seem to make a lot more sense now. I can now see how those numbers were actually achieved with the time results. What you said and what you posted for numbers were a bit different. It is nice to know how long it can be made to last in a no charger situation. From what you showed it was extremely minimal use which allowed the phone to survive for so long. I suspect under what I would consider normal use, you would easily last the day. I guess that makes most of us extremely heavy users which is why we all get excited if our phones last the whole day. I am glad you posted the screenshots for us all. Kudos!
[Fascinate Android Development] kallell:
Thanks. It's good to know what the phone could do in a more "dire" situation. Like say you're camping without power and have a spare 1800 fully charged mah battery around. Having the phone on and only using in emergency situations you could get 5 days straight without a charge.
[Fascinate Android Development] philthy:
How are you guys achieving good to great battery life? I've been using the Fascinate specifically as my music player and I leave airplane mode on at all times. I only have a few apps installed such as Google Music, Voodoo Sound, OI File Manager, BetterBatteryStats, and Watchdog. I'm on build 33. I'm planning on wiping and flashing to build 34 since the recent posts have said battery life has increased.

Any tips on how to improve the battery life?
[Fascinate Android Development] droidstyle:
I have noticed no increase in battery life since build 29 big mem...its pretty much been solid every since. If your getting **** battery life it could be a couple things...

1) If your on the original battery and its a year old or more, its time to replace.

2) You could have a rogue app keeping the device awake causing excessive battery consumption aswell.

3) Bright colored or live wallpapers with lots (more than 3) widgets on your homescreen will shorten battery life.

Also Undervolting -50mv will net a slight increase in battery, but going anyfurther does nothing imo.

edit* I notice your android os at 67%, there is where your battery life is...there must be a app keeping your device running full tilt. 22hrs is not bad for how high your android os is running. Your device was pretty much awake for 19 out of the 22hrs its been on.