yashsingh1/xdaforums huggingface dataset:
[EVO 4G Original Development] mhwarfield:
Yeah, unfortunately, I've done it both ways including a superwipe 3 pass wipe using Smelkusmod (Amon_RA) recovery as well. I thought I had mentioned that earlier a couple of times. I have it on the SD card and I can swap back and forth and, to date, I haven't found a single thing that worked under that which didn't work under the latest CWM given a manual wipe (which is all you can do under that recovery anyways).

I'll run it again under that but "incomplete wipe" means a bug. I'm a systems level programmer and linux kernel maintainer. If there's some persistent data that is surviving a wipe that disrupts a newly installed ROM, that's an uninitialized data problem and a bug that needs to be shot anyways.
[EVO 4G Original Development] cryptic3:
So like i had an issue with the 12/26 nightly in the keyboard the speaker or voice search button force closed the keyboard app and since then the keyboard wouldn't work at all just kept saying Google search force closing so i force stop the keyboard app Google search even wiped cache and dalvik still force closed i had to super wipe and flash again. Anyone having this issue
[EVO 4G Original Development] mhwarfield:
Ah! And that, Shirlock, is what we call a clue.

You are incorrect in your statement about it being "/data" but you pointed me to a clue that told me what the true problem was. It's not /data if you are running a2sd. Then it's an interaction with a2sd. I read the article you referred to. Some of what they say is true if and only if you are not running a2sd. Then, it's a problem on /data. What they did say is that you needed to run down the data directory for that app and delete it entirely. Problem is that, if you don't reformat (or clean) /sd-ext, you are going to run into this problem as well if you are running a2sd (which I am). Running a couple of super wipes in Amon_RA PLUS a factory reset wipe resulted in reformating of my /sd-ext and everything seems to be slowly reloading and restoring.

It's also not so much a difference between Amon_RA and CWM as it is to do with the interaction regarding a2sd. Now that I know what that is, CWM is just as effective as Amon_RA but it could explain a LOT of confusion with people blaming CWM for weird things that really are related to a2sd. I would still argue that an install should handle that situation gracefully if that data existed in advance but that's another arguement for another time.

So, you gave me the thread to pick at to find the problem even though, literally, what you stated was incorrect. Not a problem. I deal with that all the time. The real clue was pointing me to that URL that put the idea in my head where the problem REALLY lay. That's invaluable. You gave me what I really needed.

It's been a massive install (I have close to 200 apps on this phone - I define the term "stress testing") but things seem to be going well at this point. It still took some effort. I had to do the wipe and reformat and install and then resync everything but a2sd didn't seem to come up quite right and I had to run a2sd and reboot, then install a pile of apps till data got to 90%+ on /data and then run "a2sd install" again and then reboot and continue on. I'm on the track now to fiinishing all the reinstalls cleanly this time. That's a bonus and sets a backup stake in the ground for this ROM. I'm very pleased with where this is going now.

Verry good. You have my deepest appreciation in pointing me at that thread. That needs to be documented better what that error means at the very least. You handed me the clue I needed and gave me the key. Many thanks! :D
[EVO 4G Original Development] souleman:
He said it is a problem with the data partition.. Not the /data directory. If your running a2sd, then your data partition is not /data, it is mounted to /sd-ext when in recovery. What Jamie said is EXACTLY right. Error 24 is due to not properly wiping the data on your phone.

And CWM is known for having problems with properly deleting the data from the phone. Doesn't matter if it's /data or /sd-ext/app or anything else. That is the reason that the superwipe script files were originally written. That is actually the basis for the superwipe option in smelkusmod recovery.

The one thing that superwipe doesn't delete (and it should..) is an ext partition on the SD card. But my guess is that it ran into problems if the partition doesn't exist. I don't even use the superwipe option. If you use smelkus and you wipe system and then wipe data, you have a clean system to install a new rom. All this "wipe 3 times" and stuff, that is from when CWM was the standard.
[EVO 4G Original Development] aheeejd:
I just wanted to throw up here that i flashed the latest nightly, & normally when I run a2sd, I always choose to move the dalvik cache to SD ext, unless specifically told not to do that like in papasmurfs cm9 thread. Anyway today i chose "no" to moving dalvik & my phone is really snapping. Of course drew could have done something in the latest, but i just figured I'd throw this up here.

Sent from my PC36100 using Xparent Blue Tapatalk 2
[EVO 4G Original Development] mhwarfield:
Wow... From the ChangeLog, it looks like last night was CAMERA night! Camera here, camera there, camera updates everywhere. 19 commit entries for camera out of 23 total. I thought the camera had been working pretty nice already but I guess I was missing a few details. :p
[EVO 4G Original Development] HunterZ0:
Those 12/29 nightly changes don't seem to have fixed anything substantial for me; even did a superwipe before installing. Problems:

"Unfortunately, Gallery has stopped" FCs when trying to record videos in camcorder mode (even via Movie Studio, so I'm not sure why that app is baked in).

Settings menu in Gallery is completely blank.

Flash LED turns off when screen turns off (this is the only ROM I've ever used that does this).

And of course GPS still doesn't work.

Going to keep using and following this ROM for a while, though, as it is really great otherwise, and it's nice to see the active development.
[EVO 4G Original Development] mhwarfield:
Yeah, concur. The GPS is a problem but this ROM seems to be running smoothly for me now that I've gotten past the data / sd-ext issue with installs. I just reflashed CWM and did a dual rom (main + gapps) through ROManager and CWM recovery and everything went smooth as silk. GPS is my big hangup but, when I'm on the road, the little phone is just a MiFi for the Nexus 7 (CM10.1 nightly) and the GPS is working perfectly in that for Google Maps, Navigation, Atlanta Traffic, and TomTom Nav so the GPS in the EVO is not as critical.
[EVO 4G Original Development] HunterZ0:
Looks like some camera fixes are in the 12/30 nightly. Didn't get a chance to install it today, so I'll probably wait until tomorrow's build to see what else comes through.
[EVO 4G Original Development] Captain_Throwback:
12/30 Nightly broke Bluetooth.

EDIT: But it appears to be working on 12/31.
[EVO 4G Original Development] Soul H4ck3r:
Anyword on fixing the voicedialer.apk app & im thinking its more then just a apk...Ive installed a few other voice dialers from other jb roms and still no go after 2012.12.31 update!!!!

Any Idea's on a fix?
[EVO 4G Original Development] HunterZ0:
Thanks for the heads-up. I'll be testing Bluetooth sometime later this week, and will try to confirm whether it's working.

I've noticed no significant changes between 12/29 and 12/31 so far. All issues that I previously posted about still exist.

I also forgot to mention that the battery status section of Settings shows "Battery usage data isn't available". I'm pretty sure that all of the JB Evervolv builds have been this way.
[EVO 4G Original Development] souleman:
Did you get a logcat to show what the errors were?
[EVO 4G Original Development] Rammv:
Is there a gapps to flash with this or is it baked in?
[EVO 4G Original Development] Captain_Throwback:
You need to flash 4.2 gapps. I posted a link not too far back in this thread.

P.S. While Bluetooth did turn on with the 12/31 build, it wouldn't connect to my devices. I went back to 12/29 (because BT didn't work at all on 12/30)
[EVO 4G Original Development] Rammv:
Thank you.
[EVO 4G Original Development] roxicodine:
Is there a change log for the nightly's? or at least pin points to whats added/changed/removed?
[EVO 4G Original Development] jlmancuso:
This will sound rude but if you downloaded nightlys and have not noticed the change log at the bottom of the nightly list. Maybe you should get reading glasses. Lol. Just poking fun. Its there just look.:p
[EVO 4G Original Development] oodork123:
Not to be rude but when I saw the changelog, all our says 12/31/12-01/01/2013 changelog.:beer:
[EVO 4G Original Development] preludedrew:
If there's no commit messages in the changelog, that means nothing was merged the day before. An example of a changelog: http://dl.evervolv.com/static/n/2012.12.31/changelog-2012.12.31.html
[EVO 4G Original Development] Joshmccullough:
Quick off-topic post......

Hey all-

I posted this 'forum' to gather some help/tips in learning Linux with an eye toward personal home use and Android dev help.

http://xdaforums.com/showthread.php?p=36194535#post36194535

I don't want to clutter up the forum or get too off topic, but if anyone who's familiar/fluent with Linux could take a peek and maybe drop me a quick hint or two, it'd be greatly appreciated.

Now, back on topic, thanks for the on-going ROM work that's keeping my OG Evo running strong in late-contract year two!
[EVO 4G Original Development] fido9956:
GPS Fix?

First of all, thanks for all the active development! I have to say, it's amazing that I can install the latest Android OS on an "old" device like this and have it run smooth as silk. Good to keep in mind when every day you hear an announcement for the latest and greatest X-core processor :rolleyes:

Anywhoo - has anyone had any success getting the GPS to work on the nightlys, or know if a fix is on the roadmap? I believe this is is a known issue.

The lack of Netflix support / 4G, and iffy camera has actually increased my general productivity substantially :D

Thanks again for all your efforts...

Cheers, and happy new year!
[EVO 4G Original Development] mhwarfield:
My latest attempts with and without the GPS Flash zips have failed even on the latest nightlies. I know he tried dropping back to the earlier code that "worked" but that didn't work either. I don't know if he has a roadmap to fixing it or where his focus is. It's probably my last major bug-a-boo with this ROM.

One minor bug-a-boo since about 12/27 has been RomManager (I know - Hey... I like CWM and and its user space RomManager management and CWM works just fine if you go the manual route through recovery, for me, YMMV) and even for updates and for wipes as long as you deal with the sd-ext. Last few nightlies, ROM manager has blone an FC when trying to reboot (recovery or install). Error on the latest nightlies is "error attempting superuser function). Yet, managing backups work and even a simple "reboot into recovery" works. I even get the "RomManager has been granted superuser permisions" when doing the things that work, so it's not su that's to blame (maybe). Just install and backup hurl chunks. No, I don't have logcats on it (yet)...
[EVO 4G Original Development] merrygocow:
hello i am new to this phone and i wanna install this rom so i wanna make sure that i'm going to flash this correctly. i am currently on classic rom, have s-on, smelkus recovery, and haven't partitioned my sd card yet.

so what i need to do is:

partition sd card (found a guide already)

install a2sd via terminal

boot to recovery

wipe everything (factory, system, caches)

install rom (Evervolv-Acies-3.2.0-Nightly-2013.01.02-supersonic)

boot to bootloader

fastboot flash boot boot.img

boot to recovery

install 12/12/12 gapps

wipe caches

reboot system

is this correct? any help is greatly appreciated.
[EVO 4G Original Development] HunterZ0:
I do all my wiping and flashing from recovery, with the ROMs sitting on the SD card. Sometimes I even download the ROMs directly on the phone, so there's no need to connect to my PCs for any part of the operation.

I believe this is the recovery I'm using: http://xdaforums.com/showthread.php?t=1661543

It can do wipes, flashes, fix permissions and I think partitioning.

I think this is what you want to do if you're using the recovery ROM that I am using:

- Boot to recovery.

- Partition SD card (only need to do this once, and probably only if you are going to use a2sd; the other steps are done every time you want to change ROMs).

- Wipe everything (including SD-EXT, excluding SD). Triple wipe if paranoid.

- Flash Evervolv ROM.

- Flash 12/12/12 JB gapps.

- If paranoid, wipe caches and/or fix permissions.

- Reboot to regular mode.

Apparently a2sd is built into Evervolv such that you can install it from a terminal prompt. You will probably want to install it as a last step, and you will need to re-install after every time you re-flash an OS ROM. These posts might help with installing it:

http://xdaforums.com/showthread.php?t=1801389

http://xdaforums.com/showpost.php?p=21222591&postcount=1374

http://forums.miui.us/showthread.php?1656-How-to-use-setup-a2sd
[EVO 4G Original Development] fido9956:
Thanks for the info! I second your notion that the GPS bug is my only major issue with this ROM. Hopefully we'll get confirmation of if this issue is on the roadmap or not.

Cheers...
[EVO 4G Original Development] merrygocow:
thanks. one more question because yeah i am paranoid haha, but since i am s-on, i need to go into bootloader to flash the kernel right? that's what i do for my htc one v so i was just wondering if it's the same here.

edit nvm got it.
[EVO 4G Original Development] HunterZ0:
You mean to flash a custom kernel after flashing Evervolv? I tried MazWoz' kernel once, and it was just another .zip to be flashed from recovery sometime after flashing the OS ROM. It doesn't seem to be updated that frequently, though, so I've been sticking with Evervolv's included kernel.

Note that whenever you flash a community-made OS ROM, you should be wiping a lot of stuff first. This will blow away your gapps, custom kernels, a2sd installs, etc., too, however, so they'll need to be re-flashed immediately after flashing the OS ROM.
[EVO 4G Original Development] partyman1971:
Kernel

I hope this does not sound dumb, but can someone tell me where in the .zip file i can find just the kernel?
[EVO 4G Original Development] Captain_Throwback:
The kernel is part of the boot.img. But there's no need to flash it separately, unless you tried flashing a custom kernel (because there are no 4.2 kernels). Reflashing the ROM zip would accomplish the same purpose. There's no need to fastboot flash the kernel on this device; recovery does it just fine.
[EVO 4G Original Development] partyman1971:
I figured that Captain, i was just hoping to get only the Kernel like what Mazwoz made, i don't really want to flash the ROM again and have all that extra stuff put in there is all. No big deal. I am wanting to compare the evervolv kernel that this ROM comes with against Mazwoz's and see how much my battery life changes. The Mazwoz one kind of drains pretty fast. Thanks for your reply Captain.
[EVO 4G Original Development] Mazda:
Unlike Mazwoz, the kernel that comes stock with his ROM isn't compiled on its own so if you would like to do that....you would have to compile the kernel from Evervolv on your own.

Here's the source btw if you want to give it a go! :)

https://github.com/Evervolv/android_kernel_htc_qsd8k
[EVO 4G Original Development] partyman1971:
Thanks Mazda, but that is WAY WAY WAY out of my league. Thanks for letting me know how it was done. Are there any other Kernels out there that run on 4.1.2?
[EVO 4G Original Development] mhwarfield:
Thanks!

Very nice.

I have been meaning to ask where the sources were and then kept forgetting to ask. That's good for reference as well if you're comfortable with pawing through kernel sources and know what you're looking for. :)
[EVO 4G Original Development] 88exp88:
Just for reference what are other users battery life on 4.2.1?
[EVO 4G Original Development] jlmancuso:
I have not run it long enough yet to give battery life, but it seems about the same as 4.1x. I install it play with it for a bit and then band back.
[EVO 4G Original Development] Soap:
4 hours at 86% on airplane mode, standby screen off with a 3500mah battery. I win?
[EVO 4G Original Development] blz_phnx:
Can anybody confirm tether works, mine isn't even after i put in password
[EVO 4G Original Development] Chirpout:
I got the same issue a few nightlies ago. I haven't tried since.
[EVO 4G Original Development] Captain_Throwback:
Just tried it on 12/29 nightlly (the last one that bluetooth pairs on) and it turns on but I can't connect to it. So it appears to be not working properly.
[EVO 4G Original Development] maherov:
Does anyone remember the last nightly where the GPS was working?
[EVO 4G Original Development] Captain_Throwback:
I would assume that would be the last 3.1 (Android 4.1.2) nightly. All of the Evervolv 3.2 (Android 4.2.x) builds do not have working GPS.
[EVO 4G Original Development] Soul H4ck3r:
My GPS works here!!!! I'm on cricket
[EVO 4G Original Development] Captain_Throwback:
On what build? And we're talking about hardware GPS, not location-based. Try Navigation and see if it works.
[EVO 4G Original Development] meldryn:
looks like mazwoz just posted a 4.2 GPS fix. I'd assume it might work on this rom as well.

http://xdaforums.com/showthread.php?p=36521779
[EVO 4G Original Development] old.geek:
Nvm. Wrong rom.
[EVO 4G Original Development] Captain_Throwback:
Will be testing this post-haste with the 12/29 nightly. Will report back shortly.
[EVO 4G Original Development] Captain_Throwback:
Good news! GPS fix from MazWoz thread works on this ROM! GPS works, and now Ingress, Google Nav, and TeleNav all work! Brilliant!! Go throw some thanks over at MazWoz!

Now to see if Bluetooth is working on the latest Nightly. Maybe I'll actually try out MazWoz's ROM . . .

---------- Post added at 11:01 AM ---------- Previous post was at 10:06 AM ----------

And Bluetooth pairing works again with the 1/10 Nightly!

With that and the GPS fix, I think this ROM is all I could for, unless someone finds a way to get WiMAX working and builds a front-facing camera driver from scratch.
[EVO 4G Original Development] Chirpout:
El Capi-Tan... do you use tether or have you confirmed it's functionality?
[EVO 4G Original Development] Captain_Throwback:
Just tried it and while it turns on, I still can't connect a device to it.
[EVO 4G Original Development] mhwarfield:
Ah... Sad day I must bid this forum adieu. I love my EVO 4G, and it has served me well, but, I've been thinking about an upgrade for some time, more for an International phone than anything else, and I just heard my daughter-in-law's phone just died (they're on the same service). So my new phone (a Note 2 - Moby Phone) is on the way and my old phone will be reset back to stock and bequeathed to her. Another day or two and I wave the EVO bye-bye and wish it a happy new home where it will live on. Since it's already S-OFF w/ CWM, my son will have it on CM7 for her in a heart beat once the profile is updated (not that she really cares). :p

All take care and I hope they get the GPS thing straight before long. Too bad I won't be able to test it out. :D
[EVO 4G Original Development] Captain_Throwback:
GPS has a fix now.

And you should put smelkusMOD on there before you give it away . . ;)
[EVO 4G Original Development] amagnatta:
Anyone lose the t9 dialer in latest nightly?
[EVO 4G Original Development] bnasty06:
no not yet
[EVO 4G Original Development] maherov:
I lost mine a few nightlies ago, you don't know how good a feature it is until you lose it
[EVO 4G Original Development] amagnatta:
T9 is back in 1/11 as well as native video camera working again without FC.

Nice work!
[EVO 4G Original Development] Chirpout:
Do you mind checking the tethering?
[EVO 4G Original Development] Captain_Throwback:
Tethering is still a no go. Turns on, but no devices can connect.
[EVO 4G Original Development] NxNW:
wait, are we talking about wi fi hotspot "tethering"? or usb cable tethering? or something else? i'm coming late to the conversation.

i assume you are talking about wifi hotspot wireless tethering, and that WPA2 is a requirement for you.

if security is *not* a requirement, tethering works fine if you change security to "open". at least it does for me: i'm posting this right now using this feature...
[EVO 4G Original Development] blz_phnx:
Is notification LED working on 1/11
[EVO 4G Original Development] NxNW:
Yes, notification LED works on 1/11
[EVO 4G Original Development] Soul H4ck3r:
Drew puts change logs ...it shows what was changed and fixed!!!!! Each day has one!!!!
[EVO 4G Original Development] Soap:
Every time I see you post something, I feel like you are yelling at us :p with the excessive exclamation points!!!!!!!!
[EVO 4G Original Development] blz_phnx:
Yea yea yea i knooooow......just didn't see anything for evo, y i asked
[EVO 4G Original Development] Soul H4ck3r:
Lol death....I'm addicted to the exclamation points

And just habit sorry. Negative on the yelling
[EVO 4G Original Development] mirage1234:
I have run into a problem that I have not seen before (not sure if phone or sprint network issue)....hope someone can help. I have been getting an error message that ends calls or when calls drop. The message: Unfortunately, the process com.android.phone has stopped.

I have only seen this randomly over the last week or so since updating to 1-07 and 1-11 rom versions. I have completely wiped the phone and rebuilt it from scratch but I am still randomly getting this error message. Is the sprint network doing something that could cause this...? Or is there something specific wrong with my phone?

Any guidance appreciated.

Additional info -

The phone log does not show any record of the call when dropped like this...so no record of call at all in log. A real problem for me.
[EVO 4G Original Development] Skeptical:
Edit: It acts the same when phone is powered off. I guess I was just hoping it was software related.... Nice knowing you EVO, but I guess it's time to move on.

Thank you EVERYONE who has contributed in any way to making my phone the awesome device that it could be, and keeping it valid for so long.

_____________

Hi All. I'm having an issue that no one else seems to be having, and was just wondering if anyone's heard of it.

I installed the 1/11 nightly for the first time with this rom. Full system/factory/caches wipe in SmelkusMod. Installed rom and gapps 2012.12.12. Everything seems to have gone ok, but the phone will not charge. I'm at work right now so I can't do much testing. I have it plugged into my computer USB, the orange light turns on and charges for a few seconds, then stops as if I unplugged it. I can unplug and plug it back in and it does the same thing. I've tried disabling USB Debug, and Daydream with no effect. Tried different cable and computer. I don't have a wall charger atm to try that. I can try a reflash later, but just wanted to see if anyone had any insight to this. Let me know if you need anymore info.

Thank you in advance,

~Brandon
[EVO 4G Original Development] blz_phnx:
How can we add more toggles in pulldown, i c others have sync, rotate, silent etc.
[EVO 4G Original Development] Chirpout:
I think there's a mod for that going around. If i run across it again I'll post a link in here.

*Edit * This might be it...

http://xdaforums.com/showthread.php?t=1999125
[EVO 4G Original Development] NxNW:
there are probably plenty of people in Q&A who can help with this manipulative, passive-agressive, non-Evervolv-development-related question. Try there. Or just get a new battery.
[EVO 4G Original Development] blz_phnx:
How would i add the toggles after flashing the zip?