Originally Posted by mwie

Hey show-p,

re: the USB thingie on Baad's thread: http://forum.xda-developers.com/show...postcount=6105:

my mistake: USB in my car is working with Bricked 0.4.
Plug-in and there it goes...

With 0.5 it seems like car is getting access but can't read anything...
When I unplug it's shortly showing "reading contents" and then it can't do any further reading obviously... :)

What's changed between 0.4 and 0.5 on the USB part?
Blaming HTC here, not you anyway! :)

I'll test 0.55 - but as I think you didn't do anything on the USB I fear it will not work either...

Anyway - beer to come!!

- mwie -

That is very much appreciated!

From .4 to .5 I updated the usb driver.
from .5 to .55 there were no changes to usb. Is it possible to get a kmsg & logcat @ issuetracker? So that I can have a look at this?
(would be best to get them from both, .4 and .5(5))

Originally Posted by Twister988

Thanks for that...

Well, @ 1,54 GHz it is stable..

Any other "Pro´s" to flash to 0.55 instead of activated voltage control?
Any performance-improvements?

And about voltage control: When (in mV) it gets dangerous for the CPU?

Kernel is capped @ 1,35 Volt. (1350mV)
This is not even used by the current frequencies. Highest used is 1325mV @ 1782Mhz.
This should be "safe". but again, not all chips are created equal. My guess is as good as yours

Originally Posted by nicob

Hi show-p1984,

Could you please tell me how adding "Handle problems with rebooting on the Latitude E5420/E6420" would benefit the sensation? I was really puzzled by that when i found it in the diffs...

0.55 runs great by the way...

Also, what is the current problem with the smartass2 governor, that you don't recommend it? Or isn't it superior to ondemand?

It's in the bump to 2.6.35.14 isn't it? That's only the complete kernel push. That isn't even used in our kernel. (I push every change to avoid getting patch rejects when bumping again)

BTW, there are some changes not yet present on gcode. I dev too fast for that

Originally Posted by show-p1984

That is very much appreciated!

From .4 to .5 I updated the usb driver.
from .5 to .55 there were no changes to usb. Is it possible to get a kmsg & logcat @ issuetracker? So that I can have a look at this?
(would be best to get them from both, .4 and .5(5))

Need to read the ksmg & logcat intro to know how to use it - once done, I'll provide the requested!

Gimme time till the weekend
Already spent to much work time on flashing... %-(



sent from XDA App on HTC Sensation

i know it's a little bit offtopic... please don't blame me, i just want to know for sure (and i know a lot of experts are reading here...)

Originally Posted by show-p1984

[...]

This may occur if your phones chipset drivers are too old.
Flash this RUU: Click me
If it tells you that your model is not supported SuperCID first.
Then run revolutionary again and flash a recovery. In recovery choose the above mentioned options one by one. Then flash a ROM. Then flash Bricked.
Problem #fixed.

[...]

Originally Posted by mattdub1

hey show p , thanks for your work on this kernel... I have a question for you. I came from 2.3.3 stock and rooted it, then flashed a rom based on the 2.3.4 update... i read somewhere but couldnt' get an answer on it but i read that if you just flash a stock 2.3.4 rooted rom that you don't get all the updates like firmware and chipset updates that are in a ruu, is this correct?

Originally Posted by show-p1984

correct.
10chars

so for me it's like that: i was on software 1.35.162.1 (received via ota, vodafone branding, s-on), then i ran revolutionary, flashed recovery. from this point i started wiping everything and started with flashing roms. what i also did was flashing 10.56.9035.00U_10.14.9035.01 radio and 2.2.0169HMQ ril. that's how the phone is running currently (with ic 2.2.5 sse).

if i understood the postings above in the correct way, my phone does not have all current firmware files because i never flashed 1.45.401.2 official release?

what should i do now? i saw that there is also RUU_Pyramid_LE_HTC_Europe_1.72.401.1_Radio_10.58.9 035.00U_10.15.9035.02_2_release_214840_signed in the shipped rom thread, which is the most up2date one i think.

what i thought is:
1. make a nandroid backup
2. running RUU.exe (but which one? 1.45.401.2 or 1.72.401.1 or first the one and then the other one)
3. then revolutionary again
4. flash recovery
5. restore my nandroid

is it correct so far?

Indeed. Easiest way to get missing img files.

Originally Posted by smint86

i know it's a little bit offtopic... please don't blame me, i just want to know for sure (and i know a lot of experts are reading here...)







so for me it's like that: i was on software 1.35.162.1 (received via ota, vodafone branding, s-on), then i ran revolutionary, flashed recovery. from this point i started wiping everything and started with flashing roms. what i also did was flashing 10.56.9035.00U_10.14.9035.01 radio and 2.2.0169HMQ ril. that's how the phone is running currently (with ic 2.2.5 sse).

if i understood the postings above in the correct way, my phone does not have all current firmware files because i never flashed 1.45.401.2 official release?

what should i do now? i saw that there is also RUU_Pyramid_LE_HTC_Europe_1.72.401.1_Radio_10.58.9 035.00U_10.15.9035.02_2_release_214840_signed in the shipped rom thread, which is the most up2date one i think.

what i thought is:
1. make a nandroid backup
2. running RUU.exe (but which one? 1.45.401.2 or 1.72.401.1 or first the one and then the other one)
3. then revolutionary again
4. flash recovery
5. restore my nandroid

is it correct so far?

Sent from my HTC Sensation Z710e using XDA App

I'd only use the 1.45.401.2 RUU for now - the 1.72.401.1 isn't technically for our devices so I'd never recommend someone flash it outright

Originally Posted by tinky1

Indeed. Easiest way to get missing img files.

Sent from my HTC Sensation Z710e using XDA App

but which one? should i directly run RUU_Pyramid_LE_HTC_Europe_1.72.401.1_Radio_10.58.9 035.00U_10.15.9035.02_2_release_214840_signed or is it not recommended for standard htc sensation? i'm a little bit confused...

---------- Post added at 12:01 PM ---------- Previous post was at 12:00 PM ----------

Originally Posted by EddyOS

I'd only use the 1.45.401.2 RUU for now - the 1.72.401.1 isn't technically for our devices so I'd never recommend someone flash it outright

ok.. this answers my question! i will start right now

OK, just discovered after doing a benchmark:

1,78 GHz doesnt work - even not with 1,35v - just hangs, goodbye.
1,72 GHz is working - but the performance is worse than 1,54 GHz.

What to do there? Increase voltage? Decrease Voltage?

@show-p1984: How do you test the voltages? And how do you see, what is stable, and what is not?

Originally Posted by Twister988

OK, just discovered after doing a benchmark:

1,78 GHz doesnt work - even not with 1,35v - just hangs, goodbye.
1,72 GHz is working - but the performance is worse than 1,54 GHz.

What to do there? Increase voltage? Decrease Voltage?

@show-p1984: How do you test the voltages? And how do you see, what is stable, and what is not?

#1 Set clock, run 5 times cf-bench, if it runs stable, it's stable for now. (I actually run a stress test for 5 minutes on each frequency)
#2 If it is not, increase voltage. Test again.
#3 If it is not stable start #1.


Maybe it's just the limit for your cpu
(mine runs @ 1917 fine 1944 lets it crash)

Originally Posted by show-p1984

#1 Set clock, run 5 times cf-bench, if it runs stable, it's stable for now. (I actually run a stress test for 5 minutes on each frequency)
#2 If it is not, increase voltage. Test again.
#3 If it is not stable start #1.


Maybe it's just the limit for your cpu
(mine runs @ 1917 fine 1944 lets it crash)

Thx so far.

You said, the kernel "quits" at 1,35V. What does it mean? Higher voltages will be ignored? Or does it end in a "kernel-panic"?

Originally Posted by EddyOS

I'd only use the 1.45.401.2 RUU for now - the 1.72.401.1 isn't technically for our devices so I'd never recommend someone flash it outright

I RUU´ed my standard Sensation with 1.72, after i set supercid there wasn´t any problem! (originally its a t-mobile germany branded device) We should check if the new RUU also provides a new rpm partition, which included the new hw specific things in 1.45 RUU, that was the reason i made the RUU, to be fully up to date!