Unable to use bootV2.4.2 and newer

[GoogleCodeExporter]

Did you search through the other issues to make sure that this issue has
not been already reported? Yes
Did you look at the FAQ http://openetna.com/openetna/test ? Yes

What steps will reproduce the problem?
1. Flash bootV2.4.2 or bootV2.4.4
2.
3.

What is the expected output? What do you see instead?
Various crashes during boot, sometimes in OpenEtna boot screen, sometimes in CM 
screen. Sometimes the system completes boot sequence, but crashes within a 
minute of usage.

What version of the boot.img and system.img are you using?
bootV2.4.2 or boot V2.4.4
systemV6.1-rc4 or rc5

Can you provide logcat output during that error?
Not sure how to get it during boot

Please provide any additional information below.
bootV2.4.1 is stable as a rock, the phone seems to work just fine with it and 
the latest system image.

Original issue reported on code.google.com by krollo...@gmail.com on 28 Nov 2010 at 2:53

[GoogleCodeExporter]

have you tried fastboot -w? It helepd me once, now I allways do backup and 
Fastboot -w before flashing to build

Original comment by alkaida...@gmail.com on 28 Nov 2010 at 3:20

[GoogleCodeExporter]

When I was trying to get rc4 going, I've tried flashboot -w, tried cat 
/dev/zero > /dev/mtd{1,2,3,4,6}.

Original comment by krollo...@gmail.com on 28 Nov 2010 at 3:45

[GoogleCodeExporter]

I have exactly the same crash problem when using the bootV2.4.2 or V2.4.4 
despite many fastboot-w and others methods.

I'm still stopped with the booyV2.4.1 (currently v2.4.1 boot and system RC5 and 
no problems of this kind)

I would be disappointed that openetna project stops here for me

Thank you for your great job and sorry for my English

Original comment by cedric.v...@gmail.com on 28 Nov 2010 at 7:57

[GoogleCodeExporter]

same as issue 292

Original comment by tony...@gmail.com on 29 Nov 2010 at 2:52

[GoogleCodeExporter]

I though so too, but 292 is marked as FAQ, yet there's no solution in the 
comments.

Original comment by krollo...@gmail.com on 30 Nov 2010 at 12:26

[GoogleCodeExporter]

I'm assuming that all of you are following the steps for making sure the phone 
is entirely empty. Note that no new nightly or no change in Openetna would make 
it work because in my opinion the problem is residual data still on the phone.

Original comment by savalent...@gmail.com on 30 Nov 2010 at 1:52

[GoogleCodeExporter]

The best way I could find to clear the phone was to do cat /dev/zero into all 
the partitions except mtd5. That was done multiple times. Is there anything 
else I'm missing.

I'm curious why you suspect residual data, given the fact that boot2.4.1 works 
flawlessly.

Also, this issue seems to happen only to people who went to rc4 straight from 
1.5. Perhaps it's caused not by something left over from 1.5, but rather by not 
having something left over from pre-rc4 builds...

Either way, maybe a look at the change history between 2.4.1 and 2.4.2 would 
provide at least some clue? If nightly builds between those two releases are 
available somewhere, I could try narrowing down which particular build caused 
the issue.

Original comment by krollo...@gmail.com on 30 Nov 2010 at 2:46

[GoogleCodeExporter]

system v6.1-rc4/boot v2.4.2¶
•Fixed issue 49 'AGPS is not working' by Richard A. Burton 
•Added support for using the Home- and Backbutton LEDs as notification by 
Richard A. Burton 
•Fixed issue 191 'Gapps does not install on reboot' 
•Added support for overclocking by saxando4u

in my opinion, [•Added support for overclocking] is the reason. 

Original comment by tony...@gmail.com on 30 Nov 2010 at 5:43

[GoogleCodeExporter]

Hi,

In the last install that i make a wipe, i install one app that shows cpu speed, 
and before i install setcpu i already had the cpu runing at 710Mh. So 
overcoocking is not being optional. Is default.

(If some one don't have install SetCpu, and can install "Temp+CPU V2" please 
confirm my findings)

I read in this comment 
(http://code.google.com/p/openetna/issues/detail?id=323#c4) made by 
GiorgioMicotti that the overcloking depends on the quality of the chip, maybe 
the chip bare pass the quality test, and don't support this speed. 

One way to check this was to buid a boot image whit out overcooking config so 
krollokot can test it.

Original comment by ivolu...@gmail.com on 30 Nov 2010 at 11:09

[GoogleCodeExporter]

You know, I think you're right on the money. When I first tried to install rc4, 
I had it installed for a couple of days despite the constant crashing, which 
meant I left the phone turned off for long periods of time. What I noticed was 
that if I left the phone off for the night, in the morning it would work fine 
for maybe 4-5 minutes, and then start crashing again. It sounds like the 
overclocking change causes it to overheat. Maybe some of us are just unlucky to 
have sub-standard chips in our phones that can't handle overclocking?

Original comment by krollo...@gmail.com on 30 Nov 2010 at 1:37

[GoogleCodeExporter]

Do you have setCpu install? If not try to install Temp+CPU V2 to see the CPU 
speed, an then install set cpu and change to a lower speed and see if it 
manager to hold working. 

Original comment by ivolu...@gmail.com on 30 Nov 2010 at 1:45

[GoogleCodeExporter]

Weren't we talking about something different than the setcpu and overclocking 
issues?

Original comment by savalent...@gmail.com on 30 Nov 2010 at 3:35

[GoogleCodeExporter]

We were talking about some of us being unable to boot the phone with anything 
higher than boot2.4.1, and it looks like the problem might be overclocking code 
in the newer images.

Is there a way to disable overclocking in the newer boot images? Config setting 
maybe?

Original comment by krollo...@gmail.com on 30 Nov 2010 at 3:51

[GoogleCodeExporter]

Quote from 2.4.2 changelog:

c835f52 Added support for overclocking. Also slightly changed available
frequencies, there are more available now below 528 MHz. I'm still not sure if
at boot it's set at 528 or higher.

That last sentence is kinda scary...

Original comment by krollo...@gmail.com on 1 Dec 2010 at 3:30

[GoogleCodeExporter]

if it still crashs, simply try in the same way u'd do with a big cpu on ur 
computer:
cool it!

Just to try if its really an overheating issue,

use a fan and a cold room , unplug battery at all time , just use usb power 
source....

Original comment by saiy...@gmail.com on 1 Dec 2010 at 2:53

[GoogleCodeExporter]

Well, I don't really have a fridge handy and I'm not the only one in the house, 
so I can't keep it cool.

Is it really that hard to tell me how to set the CPU to a lower frequency 
through config files or something? I can get the sources and build them locally 
if need be...

Original comment by krollo...@gmail.com on 1 Dec 2010 at 3:20

[GoogleCodeExporter]

After more than two hours tried to start up the phone and install SetCPU before 
crashing (I tried countless times) (before the phone boot looping or starts and 
crashed ...)
I finally succeeded and lowered the frequency (which is at 710 since RC4/5)
and then not crash. So I did some tests and for me, at 690MHz my phone don't 
crash and works normally. (I'm in boot V2.4.4 and system RC5).
When I return the frequency to 710 (with SetCU) crash the phone again.

I think some CPU don't support 710Mhz may be ...

Original comment by cedric.v...@gmail.com on 1 Dec 2010 at 3:38

[GoogleCodeExporter]

Surely some CPU won't be able to run at 710 MHz. I'm sorry this caused some 
trouble, but a tester told me that the board booted at 528 MHz if it wasn't set 
otherwise by the user. I'll try to fix this but unfortunately the next release 
is not going to be released soon, we're in the middle of a major upgrade to the 
kernel and we can't release anything until this is done, and it could take a 
month or so. So for the time being I just suggest you to stay with the older 
boot images, or flash 2.4.1, install setCPU, tick "set on boot" and select 
frequencies below 528, and THEN upgrade to newest boot.img.

Original comment by GiorgioM...@gmail.com on 1 Dec 2010 at 8:25

[GoogleCodeExporter]

Original comment by GiorgioM...@gmail.com on 1 Dec 2010 at 8:25

• Changed state: Accepted

[GoogleCodeExporter]

Thanks Giorgio! The older images work fine for now, but it would be nice to 
have it fixed in future releases.

Original comment by krollo...@gmail.com on 1 Dec 2010 at 9:42

[GoogleCodeExporter]

I would think it's worth patching that but as i don't know how much work it 
represent... i won't insist :)

Yet disabling that frequency doesn't look like a very big fix ? Isn't that some 
conf file to edit ?

I'm really curious why my phone would be very stable on 710Mhz while other 
peoples get random crashes. Do you think we can have a really different chip ? 
If someone is crazy enough to open up is phone ( i mean people who get crashes) 
it would be very interesting :p

Original comment by Tetsuo6...@gmail.com on 2 Dec 2010 at 11:00

[GoogleCodeExporter]

Sure, I could open it up and see, but I think it's probably just a matter of 
luck. CPUs of the same model are usually made the same way, regardless of their 
rated frequency, and then are sorted into bins depending on burn-in tests. So 
it could be that most of these chips are good enough to be stable most of the 
time at 710, while others are not stable most of the time.

That said, I wonder if the guys with stable phones had their devices rooted and 
used SetCPU before rc4, and that setting somehow stuck around for the new 
kernel. I know I've never touched mine before installing rc4, never ran SetCPU 
(in fact, it crashes with 2.4.1)... It all depends on where these settings are 
kept.

I've found another app that seems to set the freq., CPU Tuner. I'll try 
installing again today, maybe its settings will stick around...

Original comment by krollo...@gmail.com on 2 Dec 2010 at 11:16

[GoogleCodeExporter]

I managed to get SetCPU working and the image booted. I can confirm that if 
SetCPU is not used the max freq. is at 710. It still crashes at boot pretty 
often, but at least once SetCPU gets a chance to load, it's stable.

Original comment by krollo...@gmail.com on 3 Dec 2010 at 2:26

[GoogleCodeExporter]

I've already committed the fix in git. The next kernel should be stable for you.

Original comment by GiorgioM...@gmail.com on 3 Dec 2010 at 6:50

[GoogleCodeExporter]

Thanks a lot Giorgio! Appreciate your help.

Original comment by krollo...@gmail.com on 3 Dec 2010 at 3:11

[GoogleCodeExporter]

Please try system 6.2-rc1 and boot 3.0.

Original comment by polyth...@gmail.com on 1 Feb 2011 at 12:41

• Changed state: ConfirmFix

[GoogleCodeExporter]

Original comment by polyth...@gmail.com on 7 Feb 2011 at 7:33

• Changed state: Fixed