yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] Marsbar:
4.4a HAVS 1113 BSOD last_kmsg

Will upgrade to 4.4b but just in case it still helps, here's the last_kmsg I got this morning running 4.4a HAVS 1190MHz at 1113MHz max using OnDemand.

Interesting section (I guess):

[26836.497283] AVS setting V to 950 mV @245 MHz

[26836.498535] PM: suspend of devices complete after 11.067 msecs

[26836.499633] power_suspend_late return 0

[26836.500335] PM: late suspend of devices complete after 1.371 msecs

[26836.500335] clocks on: uart_clk

[26836.500396] wakeup wake lock: i2c

[26837.497161] msm_i2c msm_i2c.0: Transaction timed out

[26837.497558] msm_i2c msm_i2c.0: Error during data xfer (-110)

[26837.498687] PM: early resume of devices complete after 997.378 msecs

[26837.500335] tps65023 0-0048: Write for reg 0x5 failed

[26837.501190] acpuclock: Unable to drop ACPU vdd: 245000.

[26837.504699] PM: resume of devices complete after 5.182 msecs
[Desire Android Development] Kinma:
I guess not.

Yesterday, after playing with the new Derise HD ROM, I flashed Defrost 4.4 (standard version, full wipe etc.).

After that ran stable, I flashed the 4.4a HAVS. In 1 hour (while the phone was in my pocket doing nothing) the battery went from 83% to 63%. While trying to find out what happened the phone died on me (bsod).

I then flashed the 4.4a SVS version. After 5 minutes the phone died again, so I reflashed the standard 4.4 version.

I lost 3% overnight and the phone is running without any further problems.

BTW.: at no time yesterday did I use SETCPU.
[Desire Android Development] Marsbar:
Is that the /proc/last_kmsg you got immediately after the boot? Looks like you might have rebooted since the crash - perhaps to copy over the new kernel? It looks like you booted, connected your USB, then 60 seconds later restarted.

last_kmsg is updated each time you reboot the phone, so if you want to get useful info you need to (eg) copy it to SD as soon as it reboots.

Edit: actually it just looks like completely the wrong kernel. Looks like you have the same problem as Dan (IIRC) - last_kmsg simply not being updated at all.

[ 0.000000] Linux version 2.6.32.9-27243-g48d7a22 (root@mythtv)

Geoff
[Desire Android Development] danarama:
I've done a factory reset and still have that same last_kmsg from April.
[Desire Android Development] Theteenystar:
Does anyone has the new Radio installed ?

Should it work with 4.4 ? Normaly yes, or ?
[Desire Android Development] The Asgard:
Had a FC with 4.4b HAVS kernel after about 10 Hrs. Seem to occur after the Alarm went off this morning. Always when idle/coming out of sleeep. Not using SetCPU. Previously I was using the 998 HAVS Kernel 4.4 which never crashed upto 4.4b being released.
[Desire Android Development] @ngel:
Here's the sequence:

1. Figured out the lockdown

2. Pulled out battery and reinserted it

3. Power-on in Recovery

4. Once powered on, hooked via USB to computer

5. Issued adb pull /proc/last_kmsg last_kmsg.txt

I noticed the old kernel signature and I can't figure it out: the last_kmsg is generated at almost every boot (it's not always there...), so it's impossible I have an old one sitting there since ages ago.

What's going on?
[Desire Android Development] Kali-:
/proc/last_kmsg is taken after a "kernel crash" or with soft reboot

for wont wake up bug, last_kmsg is not useful because phone didn't crash just do not wake up (if u connect to phone with adb u see it is still alive)

anyway, i think latest kernel posted by richard have sorted this problem
[Desire Android Development] Marsbar:
Hmm. I'm inclined to believe that the recovery mode might be the problem. You're essentially booting into a mini-linux environment (AIUI), so it will have its own /proc.

Next time, just boot into normal android, and copy the file from there using astro or es file explorer.

If you haven't rebooted since the crash you might find it's still there, as it goes.
[Desire Android Development] @ngel:
Hi Kali-,

unfortunately both bolded sentences above are not true to me: during lockdown if I connect my Desire to PC and try a adb devices command I get nothing. Furthermore, last lockdown came with 4.4b HAVS 1190 running @ 1113 via ondemand SetCPU. :confused:
[Desire Android Development] @ngel:
This is what I always tried in the past, but with no luck: the file wasn't there.

So this time I tried via recovery, and I was "lucky". :rolleyes:
[Desire Android Development] popy2006:
Now flashed the 4.4b HAVS Kernel over OTA.

After that i have used the SetCPU App to set the Kernel to 1119Mhz and clicked SetOnBoot.

The desire freezes and now it hangs in an reboot loop. It reboots to the PIN Screen ... reboot ... and so on

How can ill fix this througth ADB? What file should i delete that 1119Mhz isnt set on boot.

Please help - i am offline :-(

cu

pOpY
[Desire Android Development] Marsbar:
From the horse's mouth! Fair enough.

It does seem to me that the last couple I've posted have both had issues with the i2c bus just before the crash. Also my phone won't respond to power+upvol+OJ when this happens - does this suggest I'm seeing something different to the "no-wake" bug?
[Desire Android Development] richardtrip:
New svs kernel (Kali-) posted

Kali- posted a new SVS kernel (cyanogenmod forums) to try if you have wake-problems.

Please give it a go (i'm getting tired of this just as you all are :-).

SVS Kali 1113Mhz 2.6.34

If this kernels fixes the wake problem i hope we can move on to a .35 kernel.

Don't use the WiFi N-mode module with this kernel.
[Desire Android Development] UpSpin:
yeah, the wake bug is annoying, especially because you can't control it.

I use HAVS 4.4b running at 998MHz and had the wake issue, sort of. It was slepping, not responding, pressed some buttons, nothing, hold volume down, power and OJ several seconds and entered the boot menu :confused:

Really odd, I'll give the Kali Kernel fix a try and report back in a few days :p
[Desire Android Development] x01a4:
The 4.4b SVS kernel @ 998Mhz seem pretty stable for me.
[Desire Android Development] atomfix:
Well all of this is happening with opendesire as well, I moved from OD to defrost hoping that I would move from that problem because my I'm now having exactly the same problems on defrost as I had on OD which is my battery draining like no tomorrow. Surely..... what ever new was added that started this problem, can you remove it please. I want my phone to last at least a day. Not 5 hours :/
[Desire Android Development] The Asgard:
Thats because its based on the same Kernel and pretty much the same code bar the bells and whistles.
[Desire Android Development] atomfix:
So what ever was added to start causeing these problems, why dnt Richard or Adam release an update that could stop all of this?
[Desire Android Development] golf60:
Is there a Chance to add contact-send via Sms in the ROM?
[Desire Android Development] golf60:
With the vork Kernel are no problems with wake up or black screen .. is the Code so diffrent?
[Desire Android Development] @ngel:
That's an interesting point: when an issue can't be easily fixed often is why there are actually two issues, one hiding the other and vice versa.

I've always assumed that "no-wake" (that I call "lockdown") is something like this:

- the Desire won't exit from standby mode, regardless of what method you try / is supported by the ROM;

- the Power+DownVolume+OJ combo doesn't work;

- connecting the Desire via USB results in nothing (adb doesn't "see" it, Windows doesn't even detect it playing the USB connected sound);

- if the LED was blinking or on at the time of the lockdown, it remains in that state;

- it happens regardless of the Desire is connected via USB, to the charger or disconnected at all;

- it happens regardless of the number and/or nature of the installed apps;

- it happens even if one choses "cancel" at the very start of the configuration wizard, so without configuring Google account and stuff;

- it happens 99% of the times with HAVS kernels;

- the battery drain is slightly increased while lockdown is in progress;

- all running services are stopped (for instance, JuicePlotter stops recording data);

- the radio becomes dead (no incoming calls, SMSs, etc.).

That's my experience.
[Desire Android Development] Tweak³:
Maybe you try another Radio?
[Desire Android Development] @ngel:
Perhaps you can suggest them the solution? :rolleyes:
[Desire Android Development] atomfix:
Just updated to the new latest radio which just been leaked. And its still draining like before
[Desire Android Development] @ngel:
There's no radio relationship with lockdowns.

Never mind.
[Desire Android Development] Tweak³:
Today my phone ringed when I was called, while the phone was in the "no-wake" bug.

Edit: Sorry, it was a SMS, if that matters.
[Desire Android Development] Tweak³:
I had problems with battery drain, using the 32.47.00.32U_5.10.05.23, too.

32.44.00.32U_5.09.05.30_2 is much better for me I´ve found out.
[Desire Android Development] masi0:
Have you tried this http://developer.android.com/sdk/win-usb.html drivers?
[Desire Android Development] ikbentim:
LOL!

After installing 0.7 i got an email from Google saying "Welcome to Android, your new Nexus One has many cool and useful features"

/edit

Usb working

Wifi hotspot working
[Desire Android Development] viper_campbell:
Mirror :)

HERE
[Desire Android Development] lpachuong:
THank you so much Richard. Love you :)

Btw, tracking is not working the rest is okie. :)
[Desire Android Development] radiosilence:
Sexual, I'm getting great Linpack scores (45+) with this one, awesome new kernel!
[Desire Android Development] infexis:
This is a milestone in Desire Android development.

I really cant wait untill i come home from work :D

btw: can someone please confirm if mic works in calls?
[Desire Android Development] defectivereject:
What's the ext4 option??
[Desire Android Development] StrongOneX:
omg haha we dont need wifi hotspot now because the regular wifi tethering app works now
[Desire Android Development] vivus:
Error flashing the ROM

Hi,

I come from ROM BraFro v4. That ROM was working except for ... mic!

Now I have flashed this ROM (after a full wipe), but at the end I have received this message:

Formatting BOOT:...

Writing BOOT:...

E:Error finishing BOOT:

E: Failure at line 386:

write_raw_image PACKAGE:boot.img BOOT:

Installation aborted

What can I do to flash properly?

Thanks
[Desire Android Development] intellitech:
Re: [ROM-FroYo] DeFroST 0.7 Desire(Camera,Portable Hotspot,BlueTooth+A2SD)

Seems you might have a corrupted ROM. Download it again and flash it.

-------------------------------------

Sent via the XDA Tapatalk App
[Desire Android Development] vivus:
Downloaded 2 times: 1 from RapidShare, the second one from MegaUploads.... :(
[Desire Android Development] sruon:
Might be this thing I read about corrupted sectors requiring a boot.img smaller than 2302kb or something.
[Desire Android Development] mrlebowski:
i have the thelm problems but i start this rom and i have no problems
[Desire Android Development] stewcp:
I'm missing loads of paid apps from the market place... e.g. Pure Calendar Widget, Got To Do (paid version)... anyone else noticing this? any ideas... I've read in the past about such things but didn't take much notice :(

On the plus side... rom is great... fast, seems stable, mic working and I'm a happy boy :D
[Desire Android Development] Dredwerker:
0.7 appears to be marginally slower when set to full overclock with setcpu.

I am getting 1313 as opposed to 1349 with 0.6.

Much respect out to RT for getting another version out though :)
[Desire Android Development] vivus:
You're right! I hope this doesn't give me problem in the coming days...
[Desire Android Development] richardtrip:
Maybe you have bad blocks on the boot partition. With 2 or more bad-blocks the boot.img size has to be under 2304kb. See what i can do later this evening.
[Desire Android Development] vivus:
Maybe I can check immediately flashing i.e. MCR 3.1?

UPDATE:

boot.img size on Modaco ROM is 2338 and I flashed successfully the ROM.

Anyway, if you have some suggestion, you're wellcome ;-)

Thanks for your support!
[Desire Android Development] Dredwerker:
I got that too. Some handy little videos in the email :)
[Desire Android Development] Dredwerker:
In quadrant that is :)
[Desire Android Development] Marsbar:
These I can concur - the others I can't tell one way or the other.

I assumed it was the same bug just slightly different symptoms, but you're right - perhaps it's a completely different bug altogether.

Just occurred again with 4.4b, FWIW. And again, loads of i2c errors at the end of last_kmsg.

I also note a few bit flip errors in the file, which might suggest I'm running the processor too high, eg:

[ 807.567099] s5spend: abort suspend

[ 807.659423] batt: 81%, 4011 %V, )5 mA (%4 avg), 29.0 C, 109 mAh

[ 807.660736] sus0end: enter suspend

 807.660858] PM: Syncifg filesastems ... done

[ 807.462200] Freezing user space proceSses ... (elapsdd 0.02 sEcond3) done.

Will try running at 998MHz and see if I hit it again.
[Desire Android Development] nitrox1:
So far asop good, havs 4.4 b 1190 mhz with 1300 mV, running at 1113 mhz.

1113 mhz with the 1300 mV, has been very good for me. 18 hrs so far.

Thanks

Sent from the 25th century.
[Desire Android Development] Kali-:
no, like all other kernel is based on same source

some user sames more affected by this bug (i didnt have this problem)

i'm sure the major bug on bravo board file on our kernel is now fixed, but richard spoke me about also IR Kernel .35 on N1 is affected by the same bug
[Desire Android Development] The Asgard:
FC for me after 8-10 Hrs. Thats was without SetCPU installed so running at stock speed.
[Desire Android Development] kelix:
quiet times

Hi all, has anyone else tried "quiet times" ? It wont work for me! The settnings apply but then at the alotted time nothing happens :(
[Desire Android Development] nvivas:
Going to give it a try during the weekend. Will post back results.
[Desire Android Development] davdavo:
No Don't give up Richard, keep working on it :D
[Desire Android Development] richardtrip:
Give up.....awgthtgtta.......Not in my dictionary i guess :-).
[Desire Android Development] Marsbar:
I guess you need a better dictionary

errr, I'll get my coat :)
[Desire Android Development] danarama:
Make it a warm one, it's a bit nippy out there today.
[Desire Android Development] greatdain:
Been using this kernel all day today... no probs at all... had huge issues before - lets hope this does it...
[Desire Android Development] richardtrip:
Very nice camera features coming :-)

Cyanogen:

camera: Implement stability detection and continuous AF

camera: Camera UI cleanup

And 2.6.34 kernels based on Kali-'s work (svs + havs).
[Desire Android Development] buchman:
Downloading now
[Desire Android Development] atomfix:
Nice :D do you know if the deaf by sleep is fixed and the high battery usage?
[Desire Android Development] richardtrip:
Update

Version 4.5:

CyanogenMod fixes:

* - Camera: Implement stability detection and continuous AF

* - Camera: Camera UI cleanup

* - lots of minor fixes/translations

Kernel changes:

* Revert to 2.6.34 for stability (havs + svs).
[Desire Android Development] @ngel:
Great! :D

10chars
[Desire Android Development] nitrox1:
Nexus FRG83 is out, hope we see it soon.

Sent from the 25th century.
[Desire Android Development] richardtrip:
Never got deaf by sleep :-)

We don't know for sure if it's fixed because it needs more testing. One thing for sure is that on 2.6.34 it doesn't show up that often. Battery usage seems ok to me. Using the 4.5 HAVS 1113Mhz version atm.
[Desire Android Development] @ngel:
You lucky guy... :(

:D
[Desire Android Development] SkyWalker1726:
Sorry byt What are the Differences Between HAVS and SVS kernels ?

i already know that SVS (Static Voltage Scaling) & HAVS (Hybrid Adaptive Voltage Scaling)

does that mean that in HAVS the Voltage will increase if needed , but in SVS it's not gonna increase even if needed ?

and which one is better ?
[Desire Android Development] Latty:
I haven't had any issues on any of the HAVS kernels since 4.3 either :P (unless I'm overclocking too much). Lol, guess I'm lucky too

Edit: using 32.44.00.32U_5.09.05.30_2 for my radio, if it makes any difference
[Desire Android Development] richardtrip:
Did you already tested it? Maybe it is stable now on your device also :-)
[Desire Android Development] kai84m:
Is the issue with corruption of SD Cards resolved now?
[Desire Android Development] nitrox1:
+ 1

Also trying radio 32.48.00.32U_5.11.05.14, will let you know, if anything notable

Sent from the 25th century.
[Desire Android Development] @ngel:
Just retaken back the Desire from my childern, they was playin' Asphalt the hard way! :D

Flashing now.;)
[Desire Android Development] webrosc:
I'm giving 4.5 a try, got a nandroid of 4.0 ready though as i found that very very very stable
[Desire Android Development] shokwaav:
camera crashes when I try to start it. Defrost 4.5
[Desire Android Development] kai84m:
I tried the last version of DeFrost: A good Rom, but after i installed a other kernel from Defrost Setup it corrupted my SD-Card!

Had to completely repartition and reformat my SD-Card!

Never had such an Issue with any other ROM (I tried a few Roms ;))
[Desire Android Development] Tsuneku:
Where is the Ota in Defrost ? :confused:
[Desire Android Development] Holted:
great stability with 4.4 svs @998-1113 , been testing since 4.0, no luck yet with havs, but no problems with SVS, downloading 4.5 now.

testing HAVS 1113, uc to 998mhz
[Desire Android Development] kenkiller:
The CG CircleMod + Colored icons don't seem to work properly on 4.5.

The numbers in the battery indicator is white against a white notification bar, the network indicator arrows are all white as well. Yet the package is labelled as 4.5...any ideas why?

edit : ok managed to change the background bar color in cyanogenmod settings....but any ideas why the colored network indicator didn't appear?
[Desire Android Development] webrosc:
Had an issue doing my Titanium restore, Bonsai Blast seemed to cause a reboot then boot loop, took that out of the restore and all was fine, it even put my widgits back :D
[Desire Android Development] nitrox1:
Been on defrost from 1.x's, never had a corrupted sd card from flashing any kernel or update.

Just was reading about the long term effects of a2sd.

4.5, with 4.5 havs 1113 mhz kernel, running great with ondemand governor. Did throw a wobbly using the interactive governor though.

Sent from the 25th century.
[Desire Android Development] nitrox1:
Apps draw, under defrost setup, then press the top right spanner icon.

Sent from the 25th century.
[Desire Android Development] kelix:
Has anyone got "quiet time" in cymods sound settings to work?
[Desire Android Development] richardtrip:
Did you install one off the latest radio's?
[Desire Android Development] senis1:
Parrot 3200LS-COLOR paiting unsuccessful

Helo.

My Desire with DeFroST 4.4 can't pair with Parrot Car Kit. When I used stock FROYO, pairing was successful, but there were other problems (contact sync, Voice Dialing, Parrot's mic didn't work, ...).

What could help me in this situation?
[Desire Android Development] m0nji:
Colored Icons dind't Work for me too.

I had also mini reboots with havs 1113mhz. I tested only 2 1113 havs kernels none of them seems to work for me. But i also tested every 998mhz havs kernel since defrost 3.8! All of them working great with my phone. Can you offer plz a 4.5 998mhz havs kernel?
[Desire Android Development] ajanu:
I am also not getting coloured icons only circle battery.

I had an issue last night where the phone would not call in or out.until a reboot. It dropped.the call then could not connect again. I was not moving I am 99% sure it was not reception since it was showing 4 bars.
[Desire Android Development] x01a4:
Wow, just flashed 4.5!

The camera-app is amazing! Awesome job.

Let's hope (for Richard's sake) this kernel is stable ;)
[Desire Android Development] tosomax:
Hi guys, i have a little problem.

When i'm calling and i'm using stocks earpieces, it doesn't use the headphone's microphone but the phone's microphone.

is this normal?

Srry for my bad english hope you will understand
[Desire Android Development] danarama:
Never really played with it much before, but it makes me want to take pictures.

Its such a shame theres that cheap plastic cover on the battery door.

It amazes me how much better pictures come out without the battery door on.
[Desire Android Development] x01a4:
Yeah the plastic covering the lense is crap. I ordered a fitted sapphire glass at a watchmaker to replace the plastic thing.

Seems kind of crazy for a mobile phone, but ok ;)
[Desire Android Development] danarama:
Ahh I've been wondering who I could ask to do that. Thanks
[Desire Android Development] danarama:
Wow. Never been able to run havs stable even at 998. Now at 1113 and no problems except a reboot immediately after flash.

So far, so good. Well done
[Desire Android Development] Holted:
have had the exact same experience, initial reboot after flash and stable since.
[Desire Android Development] danarama:
Also svs at 1190 seemed ok but didn't test long. Normally have to run at 1113
[Desire Android Development] mr_clean5953:
this sucks ive been on 4.5 for 4 hours and ive had 2 black screens and one restart.

the newer kernals worked way better can we not put them back up and use them
[Desire Android Development] danarama:
Can have different results for different people. If you downloaded them in the past, boot into recovery and flash them from /sdcard/defrostsetup

Or download from the page where Richard hosts all his Rom and kernels. Just copy and edit a link from post 1
[Desire Android Development] mr_clean5953:
thanks dude
[Desire Android Development] @ngel:
How "stability detection" is supposed to work? I don't see any control about it...

Thanks.
[Desire Android Development] @ngel:
GOSH! The forum rollback took us ages ago! :eek:

Well, just want to share that 4.5a with DeFroST_4.5_1113MhzPM_havs is the very first HAVS kernel that survives the nighttime for me. :D Great job!

Only a side note: I'm experiencing a nighttime slight battery drain that was not present the last time I checked it (was on 4.1 or something):

I'm investigating if it can be related to the radio ROM (I'm running 32 .48.00.32U_5.11.05.14) or to DeFroST 4.5 itself, giving that my apps and configurations never changed.
[Desire Android Development] Narfx:
Any reason why 4.5a was removed from the op post? I have it installed and I'd like to know if some serious bug was discovered.
[Desire Android Development] atomfix:
I'm wondering the same thing :S what's going on Richard?
[Desire Android Development] dw515:
Like @ngel said.... seems to be a forum roll-back (;

It's not a problem with 4.5a ;)

(http://xdaforums.com/showthread.php?p=8315751#post8315751)
[Desire Android Development] p3anut:
I'm also wondering what it is :confused:
[Desire Android Development] asmaridis:
Three questions:

1. There is no absolutely no way to make the beautiful HTC Widgets work on AOSP?

2. I downloaded DeFrost 4.5a zip file (90 MB). Then I downloaded using DeFrost Setup the HAVS version. How do I know if it installed properly? No indication in Settings --> About Phone.

3. I thought SetCPU was included in DeFrost, but I can't find it. It's not even on the market place. How do I get it?

Thank you
[Desire Android Development] UpSpin:
1. Nope. Install ADW.Launcher to get a very customizeable launcher and use alternative Widgets. Or buy and install Launcher Pro Plus, which is also a very customizeable launcher and mimics some HTC Widgets. However, honest opinion, search for alternative widgets, there are better widgets available than the HTC ones.

2./3. You can buy SetCPU in the market (donate) or download it for free here:

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

There you'll see the max. supported frequency, which indicates in some way what kernel you've installed. But be careful with overclocking, don't do it if you don't need it. Not every phone supports the highest frequency. Some only support the stock speed, some a bit more, and a few support the highest frequency.