[ROM][KANG][08/05/12]CM10 Release Canidiate 1

Status
Not open for further replies.
Re: [ROM][JB][08/03/12]CyanogenMod 10 [Beta 4]

Hmm, you're right.. I didn't even notice that.. maybe op can post it..

I didn't flash this build yet so I haven't needed to check md5 yet,.

sj

Sent with my Epic 4G Touch on CM9-8/04 @ 128 dpi using Tap@Talk Pro v2.2.4

check the size. the first time i downloaded it, it was 40 mb, it should be 150mb
 
Re: [ROM][JB][08/03/12]CyanogenMod 10 [Beta 4]

the size is 150 MB, i've downloaded the ROM a couple of times already, still the same. i'm using the EL29 recovery.
 
Re: [ROM][JB][08/03/12]CyanogenMod 10 [Beta 4]

I meant, even just the OP would have told that info.

Do I think that the mod will work? No, because it is made for GB and no one has mentioned any success with it.

Would something designed for JB like this work? Yes, absolutely.

I don't post much, but felt the need to chime in here. I think what was meant is that even if this were for JB, it wouldn't be fixing the problem. The script was never intended to fix any of it. From my understanding, and if I remember correctly from when I first started using the device almost a year ago, the script was intended to, upon detecting LOS, restart the radio on the device. It doesn't prevent such an event from happening, it simply gives a reboot/refresh when it detects an event related to LOS. This could be oversimplified, but it is my understanding from what I remember.
 
Re: [ROM][JB][08/03/12]CyanogenMod 10 [Beta 4]

The thing is, the logs are meant to report why when a LOS event occurred, the LoSD daemon didn't catch it. It really wasn't designed to discover the reason LOS was happening in the first place. This script (and the work Viperboy did prior to it) got really good at identifying what was taking place when a LOS event occurred, but not why.

Ohhh okay, So what do you suggest to capture WHY in our logs?


Also, I've been hearing good things from some people about the latest beta, so I'm going to try some testing.

Here are my steps:

I started on Cm9. I am Mobile Odining back to Gingerbread, stock, + Root and Mbile Odin Injected. Had Mobile Odin Wipe Data / cache / Dalvik (never done that before...So hope Mobile Odin didn't mess up. (just checked, it didn't.)

So on boot, I am instantly connected to 4g (hmmm forgot what Touchwiz was like lol)

I am back on EL29.
2.3.6
FG20
EL29

I am going to get a GPS lock, then bypass Sprint Proxy
(Forgot, my phone is a refurb and can never get a GPS lock, or update PRL/Profile idk why)

Rebooted after removed Sprint Proxy, Now to ODIN

Flashed Stock EL26 Kernel with CWM.
Formatted all a few times
Installed beta 4, no Gapps
Wiped again...
confused why I see CM9 boot screen.......
4.1.1
FG20
DK Beta 4

I tried a few fixes that were mentioned here these are the results:

First, no changes, just the no GAPPS:
when I click the screen off, it flickers. No wake yet. Call works right after boot. Will wait for a while.
Turned 4G on, called again, it froze. Rebooted, call worked, 4G on, Call worked again. Wait a few minutes. Called again about 20 mins after, still worked. Installed CPU spy, unplugged phone. Will check Deep Sleep, still no Wake locks.

Since the first reboot. No issues. Granted, without GApps, I'm not doing much with it. I will go to bed and leave it off the charger to see what happens. Will test more tomorrow.

okay, now it says it is going to deep sleep, then I turn the screen off an I get wake locks every 5 seconds! Pulling logs, patience.
Still to do:

LoS test:
Turn off Network locations
Don't use wifi or 4G(4g seems fine)
Try the scripts
Try original Gapps
Try DK gapps/ Lowridder


Test Deep Sleep/wake lock:
Max Processes = 1
Turn off notification light.
Turn off auto sync?

Battery Life:
Undervolt to 800?
 
Last edited:
My text messages won't send. I've rebooted , wiped cache and dalvik , fixed permissions, wiped app data. Still nothing. Any ideas that aren't using go sms

Sent from my SPH-D710 using Android Central Forums
 
Any posts about installing are being ignored on my end. To my regular users please do not assist people with help on installing. These people asking for directions that are clearly stated in my op will end up with a hard bricked device.
 
Re: [ROM][JB][08/03/12]CyanogenMod 10 [Beta 4]

For what it's worth, I have noticed a direct correlation between poor battery life (from a wakelock) and the random wakes. I noticed I'd either have some deep sleep and constant random wakes, or no deep sleep and no random wakes. After thinking about it for a bit, this explains why some users are seeing no random wakes - because their devices are never entering a state where they were asleep to begin with. I would imagine any device will exhibit the random wakes, it's just that those that are already always awake are effectively immune to it.
 
Any posts about installing are being ignored on my end. To my regular users please do not assist people with help on installing. These people asking for directions that are clearly stated in my op will end up with a hard bricked device.

I noticed this boots cwm6. Not going to try it butthe nightlies on ics have cwm6. Do you think flashing straight to cm10 would work?
 
I noticed this boots cwm6. Not going to try it butthe nightlies on ics have cwm6. Do you think flashing straight to cm10 would work?

:banghead: Sssuuuurrrreeeee......Go ahead. Just make you got a stack of papers near you cause you phone will become a 500 dollar paper weight :banghead:
 
  • Like
Reactions: Downtown Taco
ThankYou DK! Will you hate me if I ask for an md5? :)

Sent from my Samsung Epic 4G Touch using Tapatalk
 
Re: [ROM][JB][08/03/12]CyanogenMod 10 [Beta 4]

I'm getting the Status 7 zip error after a wipe, /system format didn't help. Using EL26, like always. Never happened to me before...

Same, Wiped three times manually and ran Calk's wipe three times as well.
 
Re: [ROM][JB][08/03/12]CyanogenMod 10 [Beta 4]

Same, Wiped three times manually and ran Calk's wipe three times as well.

Ahh, found the problem I'm pretty sure. DK deleted /system/etc/init.d but forgot to take out these lines in the updater script:

set_perm_recursive(0, 2000, 0755, 0755, "/system/etc/init.d");
set_perm(0, 0, 0755, "/system/etc/init.d");

They're failing since the directory doesn't exist, and aborting the install.
 
  • Like
Reactions: Jocelyn84
Ok I can tell you by formatting system in recovery prior to flashing will cause a status 7 cause it looks at your current build.prop and by formatting system you delete the build.prop. Follow my directions in the op. format system nor use calks wipe all script is in my op.
 
  • Like
Reactions: Jocelyn84
Status
Not open for further replies.

Trending Posts

Forum statistics

Threads
957,606
Messages
6,973,716
Members
3,163,863
Latest member
sulagmu1