[ROM]{PORT} Eclipse ICS 1.2

[myfishbear]

i did this to suppress the motorola nag partition... it still charges if your desperate for battery... use your stock charger... it will save your battery.... the trick is you use it till it dies and while its off charge it to 100 to keep the battery calibrated

 

[bofis]

fair enough. So were any of the patches changed or are the ones on my sd card identical besides the governors patch?

 

[myfishbear]

same patches except the gsm patch and cdma... they were fixed cuz of a dir typo... just new links for the others

 

[bofis]

So I even tried re-downloading the audio revert patch, but it throws an error and doesn't work when I try installing it in recovery. Would freezing Ultimate Beats in TiBu cause me issues?

 

[myfishbear]

let me look at it could be an old version i uploaded

 

[myfishbear]

So I even tried re-downloading the audio revert patch, but it throws an error and doesn't work when I try installing it in recovery. Would freezing Ultimate Beats in TiBu cause me issues?

i bet it would try this instead, i missed some ;s in the script i fixed it and reposted it here https://docs.google.com/open?id=0B1lBKdIuoce6ZHFfNlh3aGVPLWM

 

[bofis]

Thanks for the updated script! Rom seems to be running great, however after being plugged in next to my bed all night last night, my alarm didn't go off this morning. When I checked my phone, the screen would not turn on and it was blinking a white LED notification. I had to hold power and volume down to reboot it, and now it's okay. Any idea what that might have been?

 

[myfishbear]

what oc did you use? my 1320 seems to be the most stable... 1320 lovolt rests at 850ma which can make some devices hang

 

[Gumdrop]

Thanks for the updated script! Rom seems to be running great, however after being plugged in next to my bed all night last night, my alarm didn't go off this morning. When I checked my phone, the screen would not turn on and it was blinking a white LED notification. I had to hold power and volume down to reboot it, and now it's okay. Any idea what that might have been?

I had just about the same problem on 1320 OC, I woke up this morning and my phone was off and really hot and wouldn't turn back on until I cooled it off. Yesterday was the first day I used the ROM though so I'm guessing ICS was indexing and my battery was not calibrated, and my phone had a lot going on so it got too hot and turned itself off to prevent damage. But Idkkk :blink:

 

[NTchrist]

pretty awesome bug

So, I've been running 1.2.3b for a few days, and decided to flash 1.2.4. my system is unusably slow. upon further research, init seems to create a shell process that spawns ~1000 new ones a second. these new processes dissapear very quickly and I am unable to stop their splitting. Any ideas to save my system without a data wipe? This rom is awesome and I would love some help.View attachment 55366

edit: when I kill the one with the ppid of 1, init just makes another one

useful lines of ps output: (full ps output in attachment)

USER PID PPID VSIZE RSS WCHAN PC NAME
root 1 0 460 256 c012abf0 00008720 S /init
root 28341 1 2120 296 c009c02c 00112808 S /system/xbin/sh
root 28371 28341 2120 300 c009c02c 00112808 S /system/xbin/sh
root 28399 28371 2120 300 c009c02c 00112808 S /system/xbin/sh
root 28427 28399 2120 300 c009c02c 00112808 S /system/xbin/sh
root 28455 28427 2120 300 c009c02c 00112808 S /system/xbin/sh
root 28484 28455 2120 300 c009c02c 00112808 S /system/xbin/sh
root 28516 28484 2120 300 c009c02c 00112808 S /system/xbin/sh
root 28547 28516 2120 300 c009c02c 00112808 S /system/xbin/sh
root 28575 28547 2120 300 c009c02c 00112808 S /system/xbin/sh
root 28603 28575 2120 300 c009c02c 00112808 S /system/xbin/sh
root 28604 28603 10188 6220 00000000 00008d9c R /system/xbin/sh


Here are the steps I went through:

fastbooted .217 ota
wipe data
boot
root / safestrap2.0 / CWM via jsnweitzel droid 4 ICS utility
reboot
power off
recovery
toggled safe ON
installed 1.2.3b
rebooted
installed google now 6
rebooted
installed way too many applications (setcpu and adfree are the only ones that required root)
ran like this for a few days... ran beautifully
flashed 1.2.4
rebooted
flashed 1320oc, speedscript and governors
rebooted
(system locked up a few times)
flashed stock oc from thread
rebooted
(rom very slow)
rebooted
flashed 1.2.4 again
rebooted
flashed google now, toggle
rebooted
wiped cache
rebooted
(system very slow)
(this is where I am now and where I got the ps output from)

 

[myfishbear]

So, I've been running 1.2.3b for a few days, and decided to flash 1.2.4. my system is unusably slow. upon further research, init seems to create a shell process that spawns ~1000 new ones a second. these new processes dissapear very quickly and I am unable to stop their splitting. Any ideas to save my system without a data wipe? This rom is awesome and I would love some help.View attachment 55366

edit: when I kill the one with the ppid of 1, init just makes another one

useful lines of ps output: (full ps output in attachment)

USER PID PPID VSIZE RSS WCHAN PC NAME
root 1 0 460 256 c012abf0 00008720 S /init
root 28341 1 2120 296 c009c02c 00112808 S /system/xbin/sh
root 28371 28341 2120 300 c009c02c 00112808 S /system/xbin/sh
root 28399 28371 2120 300 c009c02c 00112808 S /system/xbin/sh
root 28427 28399 2120 300 c009c02c 00112808 S /system/xbin/sh
root 28455 28427 2120 300 c009c02c 00112808 S /system/xbin/sh
root 28484 28455 2120 300 c009c02c 00112808 S /system/xbin/sh
root 28516 28484 2120 300 c009c02c 00112808 S /system/xbin/sh
root 28547 28516 2120 300 c009c02c 00112808 S /system/xbin/sh
root 28575 28547 2120 300 c009c02c 00112808 S /system/xbin/sh
root 28603 28575 2120 300 c009c02c 00112808 S /system/xbin/sh
root 28604 28603 10188 6220 00000000 00008d9c R /system/xbin/sh


Here are the steps I went through:

fastbooted .217 ota
wipe data
boot
root / safestrap2.0 / CWM via jsnweitzel droid 4 ICS utility
reboot
power off
recovery
toggled safe ON
installed 1.2.3b
rebooted
installed google now 6
rebooted
installed way too many applications (setcpu and adfree are the only ones that required root)
ran like this for a few days... ran beautifully
flashed 1.2.4
rebooted
flashed 1320oc, speedscript and governors
rebooted
(system locked up a few times)
flashed stock oc from thread
rebooted
(rom very slow)
rebooted
flashed 1.2.4 again
rebooted
flashed google now, toggle
rebooted
wiped cache
rebooted
(system very slow)
(this is where I am now and where I got the ps output from)

i just fixed it and im uploading 1.2.4b

 

[Technix2002]

Thanks for the updated script! Rom seems to be running great, however after being plugged in next to my bed all night last night, my alarm didn't go off this morning. When I checked my phone, the screen would not turn on and it was blinking a white LED notification. I had to hold power and volume down to reboot it, and now it's okay. Any idea what that might have been?

Uh, oh... I noticed the same thing this morning. Went to bed close to midnight, woke up a few times because of my 2 year-old and noticed around 5am that my phone had rebooted itself (saw the glow from it as it restarted). It actually attempted to boot back up into Eclipse ICS 1.2.4, but after getting to the slide screen it restarted again then it totally shut off at the Safestrap 2.0 screen. I noticed my phone was hot to the touch. I let it cool down for a while, took the micro SD out put the stock CPU speed script on it along with "Speedscript" thinking it was the 1320 OC that might have caused my issue. I flashed those both and it booted back up into E-ICS 1..2.4, butit still got really warm while charging and now at idle (no charger attached) it continues to stay warm and the battery is draining quicker.. I'm thinking of flashing back to E-ICS 1.2.3b to save battery and to not risk overheating while on charger. Did anything change in the charging logic and/or is it something in the governors? IDK, because I'm not a Dev or someone who knows enough about all of this. Thanks, btw: your Eclipse ROMS have been awesome and thanks for your work!

 

[NTchrist]

Uh, oh... I noticed the same thing this morning. Went to bed close to midnight, woke up a few times because of my 2 year-old and noticed around 5am that my phone had rebooted itself (saw the glow from it as it restarted). It actually attempted to boot back up into Eclipse ICS 1.2.4, but after getting to the slide screen it restarted again then it totally shut off at the Safestrap 2.0 screen. I noticed my phone was hot to the touch. I let it cool down for a while, took the micro SD out put the stock CPU speed script on it along with "Speedscript" thinking it was the 1320 OC that might have caused my issue. I flashed those both and it booted back up into E-ICS 1..2.4, butit still got really warm while charging and now at idle (no charger attached) it continues to stay warm and the battery is draining quicker.. I'm thinking of flashing back to E-ICS 1.2.3b to save battery and to not risk overheating while on charger. Did anything change in the charging logic and/or is it something in the governors? IDK, because I'm not a Dev or someone who knows enough about all of this. Thanks, btw: your Eclipse ROMS have been awesome and thanks for your work!

you've almost definitely got the same init bug I got. no idea what caused it (haven't had a chance to look at his code yet). The phone is getting warm because of the extra processes not only idling your processor at 30-60% but also keeping your CPU at 1200 or 1320 100% of the time. Once you flash to the new version, it should go away.

 

[myfishbear]

new fixed version check op... dont install any oc or speed script if your overheating. i think most ppl had problems due to the cpu not being set to hotplug as well.

 

[NTchrist]

new fixed version check op... dont install any oc or speed script if your overheating. i think most ppl had problems due to the cpu not being set to hotplug.

should this also fix the 1320oc crashing? or just the init bug? I'm just trying to figure out if I've got a bum device or if there were code errors there as well. my understanding is that 1320 should be pretty stable unless run at 100% for hours at a time