yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] TrevE:
yeah sorry about the original up, its hard working in RDP on a crappy dsl connection.

Does the stock LWP work again?
[EVO 4G Android Development] smw6180:
Tested Magic Smoke, Nexus and Maps and they're all fine, no more FCs.
[EVO 4G Android Development] TrevE:
cool, added to post2. should hold everyone over for now ill do my tweaks again to it for next build. working on getting some stuff compiled now using toasts community source :D
[EVO 4G Android Development] myndwire:
yep, all 7 of the non-functional ones are now working, and the nexus one is back. awesome -- thanks man!
[EVO 4G Android Development] myndwire:
oOoOoO kernel source stuff... let the games begin, i can't wait!! DC is going to own even harder now.
[EVO 4G Android Development] jblazea50:
looking forward to the new features; any chance of doing something like an undervolted kernel (probably will help with battery life); also, something like pressing the "Menu" button to wake the phone as well as to unlock instead of pressing power button and dragging the lock wheel down (should have option for both)
[EVO 4G Android Development] TrevE:
yeah i plan on having a few kernel flavors offered in post2 and on dcupdater so you can easily switch between them. also compiling up some modules you never knew you needed :)

thell be good stuff in the coming days
[EVO 4G Android Development] fenixjn:
Wow I got it to 66.1 wakes
[EVO 4G Android Development] myndwire:
I can hardly wait -- those are my favorites, the ones I *don't* know that I need ;)

A quick OT question .. I have the EXACT same setup as you hardware-wise, SD-wise, and I'm seeing you have that Mugen extended battery.. A lot of people have said a lot of different things about it. What's your experience like compared to the stock battery? Its the same size physically, right? BatteryBoss pretty much says that the 1750/1800mah batteries all suck, but I'd rather hear it from an actual user of one before dropping ~40 bucks or shrugging the option off altogether.
[EVO 4G Android Development] TrevE:
i used it in my hero, and was happy with it. it fits in the same casing as the old battery. i actually just picked this one up offa a friend yesterday - havent ran through a test yet with it.
[EVO 4G Android Development] driguez:
Damn it i wiped, everything was ok but the 3G started failing again, i have the new radio and im not in a 4G area so i didn't bother doing the wimax fix. Back to 3.2.2.1 for now.

Sent telepathically via my Evo.

-_-
[EVO 4G Android Development] VSack:
I'm starting to think it was a bit flukey. I started in on imaxreed's additions to my KillEmAll list, and before I rebooted I was hitting in the 50s again.

I'm gonna start tweaking settings again to see if I can lower it with some heartbeat eliminations.
[EVO 4G Android Development] TrevE:
did you update profiles? theres no changes between 221 and latest with system libs or bin becides adding in a flac module...
[EVO 4G Android Development] spinkteck:
since i swtiched to this ROM, when i check the "powertop -d" i get this msg

/sbin/modprobe : not found

anyone know why? but the list still loads afterward
[EVO 4G Android Development] TrevE:
pretty sure this is the module that _could_ be loaded to show actual power not %'s, but we dont have the module so we fall back to %'s
[EVO 4G Android Development] myndwire:
i get that too. the modprobe binary is being called from a static location (/sbin) when it's not there. you could just symlink it in recovery mode and it'd likely go away, you'll just have to mount the filesystems first.

ln -s /xbin/system/modprobe /sbin/modprobe

when both root and /system filesystems are mounted read/write. i haven't done it because i really don't mind, but that's how it'd work from the linux side of things..
[EVO 4G Android Development] spinkteck:
O aiight. thanx :D

I dont know how to do that process, but since its fine, i dont mind
[EVO 4G Android Development] myndwire:
ya, i wouldn't worry about it, although we may want that implemented into the rom moving forward.
[EVO 4G Android Development] guyver2077:
installed 3.2.3 + patch

So far so good.

Any additional info on the camera resolution fix? (from the change log)
[EVO 4G Android Development] TrevE:
was mostly for the 3d gallery, was stuck at some low res before 640x320 or something whack. we got thatup tothe full 8mp i put in some build.prop changes too but cant confirm if they actually did anything.

toast just pulled perflock and got some oc'ing going. damn he works fast. ill be building a new kernel or two soon if all is well so we cn get some setcpu action going.
[EVO 4G Android Development] driguez:
Should i update it? IIRC i did update after i noticed the issue, it along w prl, but im not 100% sure.... Im flashing again maybe its an issue within my area. I can always nandroid.

Sent telepathically via my Evo.

-_-
[EVO 4G Android Development] SouL Shadow:
Well, reboot became constant, so I did a full wipe and flashed 3.2.3. So far so good. I did noticed prior to wiping that df listed /app-cache as 0k available. Now it's at 0k used. Dunno if that would have been the problem but i'll keep an eye on it as I re-install things.
[EVO 4G Android Development] MCLFLN:
PowerTOP

Collecting data for 15 seconds

/sbin/modprobe: not found

< Detailed C-state information is not available.>

P-states (frequencies)

576 Mhz 0.0%

499 Mhz 0.0%

461 Mhz 0.0%

384 Mhz 0.0%

245 Mhz 100.0%

Wakeups-from-idle per second : 746.7 interval: 15.0s

no ACPI power usage estimate available

Top causes for wakeups:

53.5% (394.4) AudioTrackThrea : do_nanosleep (hrtimer_wakeup)

44.5% (328.1) <interrupt> : gp_timer

0.4% ( 3.0) er.ServerThread : schedule_hrtimeout_range (hrtimer_wakeup)

0.3% ( 2.5) <interrupt> : msm_hsusb

0.3% ( 2.1) er.ServerThread : futex_wait (hrtimer_wakeup)

0.3% ( 2.0) rild : __netdev_watchdog_up (dev_watchdog)

0.1% ( 1.0) <kernel core> : msmsdcc_probe (msmsdcc_check_status)

0.1% ( 1.0) m.android.phone : futex_wait (hrtimer_wakeup)

0.1% ( 0.5) <kernel core> : schedule_delayed_work_on (delayed_work_timer_fn)

0.1% ( 0.5) Smack : Packet Wr futex_wait (hrtimer_wakeup)

0.0% ( 0.3) iqfd:tombstone : schedule_hrtimeout_range (hrtimer_wakeup)

0.0% ( 0.3) iqd:cserial : do_nanosleep (hrtimer_wakeup)

0.0% ( 0.3) <kernel core> : neigh_table_init_no_netlink (neigh_periodic_timer)

0.0% ( 0.2) iqfd : schedule_hrtimeout_range (hrtimer_wakeup)

0.0% ( 0.1) iqd:jjob : sk_reset_timer (tcp_delack_timer)

0.0% ( 0.1) iqd:jjob : schedule_hrtimeout_range (hrtimer_wakeup)

0.0% ( 0.1) iqd:jjob : sk_reset_timer (tcp_write_timer)

0.0% ( 0.1) m.android.phone : sk_reset_timer (tcp_write_timer)

0.0% ( 0.1) Transaction : futex_wait (hrtimer_wakeup)

0.0% ( 0.1) ObexHelper : schedule_hrtimeout_range (hrtimer_wakeup)

0.0% ( 0.1) watchdog : futex_wait (hrtimer_wakeup)

0.0% ( 0.1) <kernel core> : queue_delayed_work (delayed_work_timer_fn)

0.0% ( 0.1) <kernel core> : page_writeback_init (wb_timer_fn)

xrandr: not found

Suggestion: Enable the CONFIG_HPET_TIMER kernel configuration option.

Without HPET support the kernel needs to wake up every 20 milliseconds for

some housekeeping tasks.

Suggestion: Enable the CONFIG_ACPI_BATTERY kernel configuration option.

This option is required to get power estimages from PowerTOP

Suggestion: Enable the CONFIG_USB_SUSPEND kernel configuration option.

This option will automatically disable UHCI USB when not in use, and may

save approximately 1 Watt of power.

Recent USB suspend statistics

Active Device name
[EVO 4G Android Development] smw6180:
Not entirely sure of the point in posting that and nothing else. But with that many wakeups are you checking it with the screen on? Turn off the screen, wait about 60 seconds and then try it again.
[EVO 4G Android Development] MCLFLN:
Sorry, when I edited the post I overwrote why I was posting it. Other's have posted almost the exact same results and no progress seems to have been made for them. I was just adding that I too was seeing the same behavior. Here is another output with the screen having been off since before the previous post:

Collecting data for 15 seconds

< Detailed C-state information is not available.>

P-states (frequencies)

576 Mhz 0.0%

499 Mhz 0.0%

461 Mhz 0.0%

384 Mhz 0.0%

245 Mhz 100.0%

Wakeups-from-idle per second : 643.1 interval: 15.0s

no ACPI power usage estimate available

Top causes for wakeups:

62.2% (394.3) AudioTrackThrea : do_nanosleep (hrtimer_wakeup)

35.6% (225.7) <interrupt> : gp_timer

0.5% ( 3.0) er.ServerThread : schedule_hrtimeout_range (hrtimer_wakeup)

0.3% ( 2.1) <interrupt> : msm_hsusb

0.3% ( 2.0) er.ServerThread : futex_wait (hrtimer_wakeup)

0.3% ( 2.0) rild : __netdev_watchdog_up (dev_watchdog)

0.2% ( 1.0) m.android.phone : futex_wait (hrtimer_wakeup)

0.2% ( 1.0) <kernel core> : msmsdcc_probe (msmsdcc_check_status)

0.1% ( 0.5) Smack : Packet Wr futex_wait (hrtimer_wakeup)

0.1% ( 0.5) <kernel core> : schedule_delayed_work_on (delayed_work_timer_fn)

0.1% ( 0.3) iqfd:tombstone : schedule_hrtimeout_range (hrtimer_wakeup)

0.1% ( 0.3) iqd:cserial : do_nanosleep (hrtimer_wakeup)

0.1% ( 0.3) <kernel core> : neigh_table_init_no_netlink (neigh_periodic_timer)

0.0% ( 0.2) iqfd : schedule_hrtimeout_range (hrtimer_wakeup)

0.0% ( 0.1) m.android.phone : sk_reset_timer (tcp_write_timer)

0.0% ( 0.1) iqd:jjob : schedule_hrtimeout_range (hrtimer_wakeup)

0.0% ( 0.1) Transaction : futex_wait (hrtimer_wakeup)

0.0% ( 0.1) iqd:jjob : sk_reset_timer (tcp_delack_timer)

0.0% ( 0.1) iqd:jjob : sk_reset_timer (tcp_write_timer)

0.0% ( 0.1) ObexHelper : schedule_hrtimeout_range (hrtimer_wakeup)

0.0% ( 0.1) <kernel core> : queue_delayed_work (delayed_work_timer_fn)

0.0% ( 0.1) <kernel core> : page_writeback_init (wb_timer_fn)

xrandr: not found

Suggestion: Enable the CONFIG_HPET_TIMER kernel configuration option.

Without HPET support the kernel needs to wake up every 20 milliseconds for

some housekeeping tasks.

Suggestion: Enable the CONFIG_ACPI_BATTERY kernel configuration option.

This option is required to get power estimages from PowerTOP

Suggestion: Enable the CONFIG_USB_SUSPEND kernel configuration option.

This option will automatically disable UHCI USB when not in use, and may

save approximately 1 Watt of power.

Recent USB suspend statistics

Active Device name
[EVO 4G Android Development] Emrys_90:
AudioTrackThrea is caused by a misbehaving app, I found for me it was caused by Scrambled Net. Another user posted that ShootMe caused it if the take a picture by shutter sound or something was turned on.
[EVO 4G Android Development] SouL Shadow:
Wiped, reflashed, reinstalled and so far so good. I did notice 1 little problem. Prior to 3.2.3 The Weather Channel app would display an icon with current temp in notification bar and would be visible when you pull down the notifications. Now with 3.2.3 the icon is there but nothing shows up when you pull down the notifications.
[EVO 4G Android Development] SouL Shadow:
Yes, I found that shootme, a screenshot program, when set to take a picture when you "shout", will constantly cause wake-ups as it checks the mic. I went from 600+ while shootme was running down to under 90 after I turned it off.
[EVO 4G Android Development] liquidkernel:
TrevE... found a problem with the ROM. VPN is not working (PPTP connections). It simply sits at "Connect" and then times out. I flashed Fresh just to see if it was my VPN server or the phone, and it works fine with Fresh.

Running 3.2.2.1.

//edit: VPN fixed. Installed 3.2.3 after a wipe.
[EVO 4G Android Development] MCLFLN:
hmmm... I am not running shootme. Also, top doesn't really show anything going on:

# top -n 1 -t

top -n 1 -t

User 1%, System 8%, IOW 0%, IRQ 0%

User 6 + Nice 0 + Sys 28 + Idle 300 + IOW 0 + IRQ 0 + SIRQ 0 = 334

PID TID CPU% S VSS RSS PCY UID Thread Proc

2033 2033 8% R 1020K 536K fg root top top

502 1737 0% R 333640K 62216K fg system AudioTrackThrea system_server

502 1738 0% R 333640K 62216K fg system AudioTrackThrea system_server

502 1739 0% R 333640K 62216K fg system AudioTrackThrea system_server

502 1717 0% R 333640K 62216K fg system AudioTrackThrea system_server

502 502 0% S 333640K 62216K fg system system_server system_server

808 1164 0% S 213088K 41704K fg radio CIQ connection com.android.phone

502 897 0% S 333640K 62216K fg system er.ServerThread system_server

9 9 0% S 0K 0K fg root kmmcd

10 10 0% S 0K 0K fg root btaddconn

11 11 0% S 0K 0K fg root btdelconn

12 12 0% S 0K 0K fg root kondemand/0

13 13 0% S 0K 0K fg root smd_tty

14 14 0% S 0K 0K fg root qmi

15 15 0% D 0K 0K fg root rpcrouter

16 16 0% S 0K 0K fg root krpcserversd

17 17 0% S 0K 0K fg root detection/0
[EVO 4G Android Development] M@XLOL:
woa i am confused whats newest version? I am running 3221
[EVO 4G Android Development] driguez:
3.2.3 if im not mistaken.

Sent telepathically via my Evo.

-_-
[EVO 4G Android Development] josharmour:
I do not have HDMI out either. This is a deal breaker for me.

I need to put shipped rom back on here..
[EVO 4G Android Development] seriousblack25:
Ok right now im having a problem with the wifi connection on both hotspot and wifi tether i get online then kicks me off constantly does anyone know of an easy fix this started happening after i came from Fresh i went back to stock latest RUU then DC
[EVO 4G Android Development] fallentimm:
What's wrong with hdmi? Set output in settings first time and it works fine
[EVO 4G Android Development] VoXHTC:
I have to ask a dumb question:

Whats the difference between my rooted version of DC and the one that was JUST rooted a little while ago tonight? Just a different method of gaining root access?
[EVO 4G Android Development] fallentimm:
Yeah after you gain root with flash method it gives you recovery then you run toast method to knock nand. So your essemtially doing whitslack method.

Nodiff
[EVO 4G Android Development] healthpellets:
ok, so i just downloaded the color theme via DC updater. i was given the option to reboot in to recovery and apply the theme.

the phone rebooted and now i'm at a screen with the android robot and a white triangle with an exclamation point.

wtf? any help please?
[EVO 4G Android Development] muncheroo:
nm deletye me
[EVO 4G Android Development] apollooff320:
pull your battery. I had to do the same thing a couple updates back. I think it was clockwork that caused the problem and I had to flash back to RA recovery for it to work.
[EVO 4G Android Development] huynhc:
i think you lost your custom recovery? you probably had clockwork's recovery before you re-did the flash from scratch maybe?

In any case, get RA's recovery here

follow those instructions... you can do fastboot or adb method. Once you flash over the new recovery, you should be problem-free. PM me if you have issues and I will try to help....but I am a Android newb (first droid phone for me)
[EVO 4G Android Development] healthpellets:
ok, so pulling my battery isn't gonna totally screw me? i guess at this point (about 10 mins in) i don't have much choice.

what should i expect on reboot? or should i reboot straight in to recovery and reflash?
[EVO 4G Android Development] thorpe24:
Stupid question. If I an running the latest DC rom do I have the latest radio? I don't have 4g but I read the new radio is better for battery life... Sorry still learning about this stuff
[EVO 4G Android Development] frozndevl:
4G problem here

I have performed the 10 step process in post #2, as well as following the start over instructions a few times. The only step I wasn't able to do was flash the radio file indicated in the download, it said verification failed. I was able to flash the latest radio usuing CAlkulin.

The symptom is that when I turn on 4G, it scans, says it is connecting to Spring, then goes to a disconnected state, then starts to scan again. I am in Seattle, so I have at least some 4G connection.

This phone is an exchange, which is why I am a bit late to the party. Here are the requested log files from post #2.

1) To my knowledge, my MAC address has not been broken. wimax_mtd and the other methods all match what is under the battery

2) See the attached logcat.txt

3)

# ls -l /data/misc/wimax/
ls -l /data/misc/wimax/
-rw-rw-rw- root root 201040 2010-07-05 22:41 38E7D858F5BB.tree.xml
---------- root root 201040 2010-07-05 22:08 38E7D858F5BB.tree.xml.orig
drwxrwxrwx wimax wimax 2010-07-05 21:54 sockets

Thanks in advance to whoever can help.

PS. On a sidenote, whenever I boot into recovery, my phone makes a little click after it shows the htc EVO white screen, it sounds like a busted vibration but my vibration is working fine. Anyone else have this, Im using amon's recovery.
[EVO 4G Android Development] healthpellets:
alright. pulled the battery and turner her back on. straight back to everything being good. will look in to my recovery issues later.

thanks ya'll.
[EVO 4G Android Development] Thomas1218:
Could some one be so kind as to point me to the links where I can download the latest radio and wimax updates so I can update to the latest dc build. I found one but the link was bad and I haven't found any others. Thanks
[EVO 4G Android Development] thorpe24:
So this doesn't come with the latest radios. I'm confused so we flash this rom. (which I did when it was posted 3.2.3) to get the new update (the one that broke root for like 3 days) but we need to get the radios ourself. Won't flashing the radio screw us up sorry I am still kind nw to this. Would someone care to explain?
[EVO 4G Android Development] apollooff320:
get the last radios here

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

flashing the radio shouldn't screw up nothing. I installed my radios first then installed DC afterwards and my phone is running fine. Hope this helps. I'm off to bed. Oh by the way ROMS usually never come with the radios you have to install them yourself.
[EVO 4G Android Development] Thomas1218:
Thanks a ton!
[EVO 4G Android Development] fallentimm:
Any news on oc or setcpu?
[EVO 4G Android Development] jamrich2:
Hi All,

I hope i don't get flamed for this question, but there are A LOT of posts and I can't seem to find this.

newbie to Android, but not to tech in general.

I am running the latest version of DC. I am fully rooted with NAND unlocked.

All is running great, I just i have one issue.

I can't seem to find DCUpdater, or any other DC specific apps there are supposed to be.

I see DCSUtility.apk in my System/apps folder along with a DCSIpl.apk and DCSStock.apk. But I don't have any DC apps in my actual apps list.

Is there something I am missing?

I did a full wipe before flashing the rom. I have read the first 2 posts as well as checked out the DC website.

EDIT: I am using Clockwork Recovery but from the first post it only seemed like installing updates would be affected, not actually using DCupdate

Any help you can offer would be greatly appreciated.

Cheers

jamie
[EVO 4G Android Development] itmustbejj:
I am getting 56.7 wakes since upgrading to latest 3.2.3. Me = Happy.

Great work Treve. Now I'm just trying this custom kernel itch under control....
[EVO 4G Android Development] YafaKlan:
I had 3.2.2 and I wiped and flashed 3.2.3. The synch icon on top refused to go away. I had to nandroid back to my old 3.2.2. Just thought I'd share.

Someone else had the same problem, but for the life of me, I cant find the post.
[EVO 4G Android Development] VSack:
If you enabled JIT, I believe DCUpdater automatically defaults to the banned app category. Check there, make sure its not checked, and if so, reboot. :)
[EVO 4G Android Development] itmustbejj:
read post 2 about account.db

This is not a 3.2.3 issue.
[EVO 4G Android Development] jamrich2:
Thank you. Hate to be a pain, but I am not sure where to find the banned app catagory.

In terms of JIT being enabled or not, I know what it is and what it does, but I have not done anything to enable or disable.

I flashed the rom, and don't seem to have any options. Is it possible that rom flash didn't work, but my phone still does? I flashed the rom and had no issues, is there a way to make sure I am actually using the DC rom?

Are nandroid backups specific to the rom, meaning i made my nandroid backup while using a different rom, then flashed DC, then restored the Nandroid. So am I screwing something up that way?

I really do appreicate any advice and help.

Thanks

jamie
[EVO 4G Android Development] Emrys_90:
Nandroid backups are specific to your phones current setup, if you made a nandroid backup while on a different rom and then restored that nandroid then your back on the other rom.

Go to Settings>About Phone>Software Information to find out which ROM your using.
[EVO 4G Android Development] sk63:
Yeah, Nandroid restores you old system. It basically takes a snapshot of your phone at a particular time and will restore it to exactly like it was, no matter what changes you made after the nandroid. An exception is radio/wimax which are not backed up as part a nandroid, so any changes made to them will stick.

For backing up apps and data between flashes, try Titanium Backup.
[EVO 4G Android Development] kamiller42:
Welcome to the "Screwed WiMax" club. I followed the procedure too and have 4g connectivity problems. (I used the signed radio and flashed fine with clockwork recovery.) Mac address seems fine. The only way I can connect to 4G now is turn off the phone and turn back on.

The reason you received verification error is because you tried to flash with a recovery not clockwork, maybe amon. Get ROM Manager and install clockwork.

I would like a pointer to instructions on how to fix the eternal scanning for 4g problem. The simpler the solution, the better.
[EVO 4G Android Development] healthpellets:
having nearly 100% awake time with 3.2.3

anyone else? any fixes?
[EVO 4G Android Development] rehh:
ahh didn't know that my radio/wimax was uneffected by nandroid backups.

I've been having all kinds of problems with 4G, so I tried restoring my phone back to factory using my orig nandroid backup, didn't work, my 4G is still broken, must have something to do with the radio/wimax flashes I did.

Have another prob that just started, can't boot my phone now with the power button unless I take the battery out first, buttons just flash, just started when I restored my phone back to factory........... any ideas?
[EVO 4G Android Development] Taupakari:
When you connect the Evo to an HDMI input on a television or a/v receiver the phone locks up and requires a battery pull to get it unlocked and running again. From my Google research it seems that this problem is not unique to DC roms and is even happening on stock, unrooted phones. However, HDMI out did work on my phone until recently so clearly something got borked along the way.
[EVO 4G Android Development] jamrich2:
Thank you SO much!! now it all makes perfect sense!

I will try Titanium!!

Cheers

Jamie
[EVO 4G Android Development] Babble0n:
Rosie Rotate?

Hey there, thanks for putting this ROM together, I am loving it...well most of it.

One thing I find irritating is that this phone only rotates to landscape in one direction. It is especially problematic when a headset is plugged in and you want to get to the landscape keyboard. I was hoping to include the 270 degree rotate functionality like in the Fresh ROM. I tried just flashing their "rosie rotate enable" patch over my DC ROM but that didn't work so I'm assuming there are some apk's that need to be modified/added to make it work but I don't know where to start or if I can even do that without being a serious ROM chef like some of the folks around here.

Can anyone point me in the right direction or just tell me this is not possible? I do PC software development but Android and the ROM thing are new to me as of 6/4/10.

I have a kitchen setup with DC as my base and I have the Fresh ROM and the patches to enable/disable the rotation if it's possible to Frankenstein those parts together.

Also, if this should have been posted in a different thread please forgive my ignorance and kindly point me to the proper discussion. Thanks!