yashsingh1/xdaforums huggingface dataset:
[Desire HD Android Development] shuster46:
Sorry,

can anyone provide some kernel again? I'm stuck with my rooting HTC Desire 500.

(all these threads are now very old, I know, but I just did my rooting now:()

thanks in advance for any help or link you can give.

Roberto.
[Desire HD Android Development] Youngunn2008:
OK to set back to default.
[Desire HD Android Development] synergye:
What do your you man by black screen? I thought earlier when people were talking about black screens they meant their phone rebooted. Now I'm thinking it's a different issue. Could you explain or get a kmsg or last_kmsg of it happening? Thank you again.
[Desire HD Android Development] dan-fish:
Last time I checked this had the saga stuff merged in. Could it be built for saga?
[Desire HD Android Development] xhejtman:
For me, the black screen means:

1) phone does not display anything but black screen

2) with recent kernels, backlight was on (i.e., hw keys backlighted, one could see that screen is backlighted as well), with older kernels, baclight was off, just black screen

3) phone does not respond to any touches or hw keys including power button

4) phone responds to adb

5) most of apps have crashed, just few remained running

6) there is no oops or anything obvious in dmesg

7) logcat reports that most apps died

my logs from this situation with R17.1 including R17.1 kernel is here:

http://xdaforums.com/showthread.php?p=32660803#post32660803

This does not happened with your 0.1 or 0.2 kernel, but I keep testing. Only problem with your kernel I see is dying wifi.
[Desire HD Android Development] synergye:
Thank you. Has anyone on the nightlies had the black screen issue (not reboot)? This is seeming more and more like userspace since it's only reported on random's cm builds.
[Desire HD Android Development] pnoire:
CFX nightlies --> Nope, I had no black screen issue with stable kernel and performance kernel

From users CM-nightlies and CFX-nightles in french threads --> no black screen at all

and good news, the issue of artifacts in Draw Something seems solved in nightlies 1012 !
[Desire HD Android Development] bananagranola:
Nope, I haven't had problems with the black screen issue (or any problems really) on either the regular kernel or the performance kernel. But I didn't have any of the stability issues from a couple nightlies back either.

EDIT: I'm running cfX 1012.
[Desire HD Android Development] whiperhack:
I can confirm all of this. :)
[Desire HD Android Development] BaT420:
I've had it only happen once the black screen on the oct 11th build with the .02 kernel. Happened a few minutes after flashing .02 I had to do a battery pull to get the phone back up but its been like 16 hours since then and no black screen yet just that once.
[Desire HD Android Development] chrisz5z:
On nightlies, only have the black screen issue on the performance kernel. It will finish optimizing apps then once it says starting apps I get black screen.

What about having a mid-grade kernel? :)....maybe one that has clocks in between the stable & performance

Sent from a satellite
[Desire HD Android Development] EmptyArea:
From my experience the black screen will occur rarely, and if I wait and combine holding back button and pressing power button repeatedly it will eventually begin responding again.

This is on random's rom and hasn't happened since flashing 0.2

It behaved similarly to issues I can force with over clocking or undervolting on any ROM.

Apologies if this deemed off topic at all.
[Desire HD Android Development] synergye:
That's the stable kernel. It's using higher bus clocks than in nightlies just a few days ago ;)
[Desire HD Android Development] wigankev:
I just got a black screen on Jellytime with stable kernel
[Desire HD Android Development] Youngunn2008:
I only had the black screen lockups on jelly time. Upon switching to cfx I then had lockups whilst trying to do heavy operations. Since new kernels no problems whatsoever. My phone is running the performance kernel oc'd to 1305 with no problems and is faster than I can ever remember. Even fixed the lag in the stock keyboard. Yaaaaay
[Desire HD Android Development] synergye:
I've been reviewing a multitude of logs from various users (have a spreadsheet now of them with info), and believe there were actually three separate issues. The first was the memory corruption/reboot kernel issue which is now fixed. Then there was a fb issue which caused the screen to go black in kernel which is also fixed. There is another separate userland issue which seems to only be apparent in RB's cm build (please nobody take offense). Why on the newest nightlies it would appear nobody has had this issue, save for separate performance kernel related lockups which were then fixed by switching to the stable kernel. I believe this has something to do with a change in qcom display for him (I use CM's), but have yet to track down what exactly he did differently to cause this. There's also a chance that it's something he did device related, however he keeps all that closed source.

Just reporting findings after going through a plethora of logs and documenting each one (thank you to the many very diligent users). Now I'm off to fix some other bugs on other devices such as US SGS and Jewel (evo 4g lte).
[Desire HD Android Development] synergye:
v0.3 was a reasonably mild update (just patched to 3.0.46 from LK), but I just wanted to update on what I'm doing for v0.4. I'm working on sweep2wake with configurable priority, and fast charge. I'm going to be using an aroma installer with both variants of kernel packaged in, as well as an option to disable/enable sweep2wake, and fast charge upon install ;). This should be the best option for users as if someone dowloads the kernel on their phone and can't run the performance variant, they can flash the same package again and select the stable variant instead.

Edit: ****, didn't mean to double post :/
[Desire HD Android Development] Galaen:
Sorry if this is off topic, but I have a question about sleep2wake. It looks pretty neat, but I have never used it. How easy is it for the phone to turn on in a pocket? That is really my only concern. Thanks!

Sent from an Inspire 4G
[Desire HD Android Development] synergye:
On HTC holiday some users had that problem, others didn't. I personally never thought it was worth any decrease in battery life, but many users like it. I'll be doing a script which will copy to /syatem/bin so you can just run sw from terminal emulator to enable or disable it. If any of you use imoseyon's kernels I'm going for a similar setup as far as userspace modification goes.
[Desire HD Android Development] LinoX:
I have it with performance kernel.but it's weird...when I flashed cfx (for the first time) and the 0.2 performance kernel it worked with no problems. Then I "explored" codefirex's features changing a some settings(like disabling zram for performances).the phone hang up. And it didn't start again. Black screen on startup. Flashed the standard kernel and the room booted fine again (don't know why) gotta try with the new 0.3 and see if it works.

But right now Wi-Fi is the big issue :)

Edit: tried 0.3 performance. Bootloops (while 0.2 performance hangs) before bootanim.I don't know how to get the bootloop log because the log gets overwritten by the stable kernel one when the system starts.
[Desire HD Android Development] synergye:
On cfX it will keep the previously set max at boot to lower the boot time. This means any potential instabilities will really show at hoot. I think it's related to the kernel bus clock in performance for you since they go up with each clock. So 1024mhz on stable may not be stable for you with the performance variant.
[Desire HD Android Development] Galaen:
Well, I will still give it a chance. Discovery is 90% of the fun, right? I am still a noob using a terminal emulator, so I will have to research this sw command. Gonna learn some new things tonight. I'm excited! :D

Sent from an Inspire 4G
[Desire HD Android Development] synergye:
Ah, I'm sorry if I was misleading. It isn't an actual command, but instead I'm gonig to add a s2w (sweep2wake) scripts named that to /system/bin so all you will need to do is run "sw1" to enable, or "sw0" to disable (at least that's my plan...we'll see how this goes).

Edit: More than one person s-on here? Please let me know so I know if I should include a "s-on" option in the Aroma script to flash on s-on devices.
[Desire HD Android Development] bamonkey:
late to respond but I am ENG S-OFF...best way to go :laugh:
[Desire HD Android Development] synergye:
In about 10-15min there will be a new v0.4 kernel up with fast charge capability. I spent awhile getting an aroma installer setup, then ran it and forgot how much longer makes flashes take. It's absurd for a kernel flash to take that long! I think I came up with a good solution instead. You must type these without quotes in terminal emulator :

"sh /system/bin/fcon.sh" to enable fast charge

"sh /system/bin/fcoff.sh" to disable fast charge

"sh /system/bin/fconboot.sh" to always enable fast charge at boot

"sh /system/bin/fcoffboot.sh" to always disable fast charge at boot

Tomorrow I should finally have a good sweep2wake implementation that doesn't drive me bonkers with button led settings as well. The new kernel also has the default 1996MHz and 2016MHz voltage slots changed for better stability (at least you can get through a bench now).
[Desire HD Android Development] zomer331:
KangBang kernel v3 stable valid no-zip,when I've tried to flash.

What is the problem?
[Desire HD Android Development] Rikodu:
Are these commands for all who are using the 0.4 kernel ?
[Desire HD Android Development] synergye:
Damn! I literally just uploaded, but yes. I also added slightly better instructions for it in the OP. Basically if you always want fast charge run the fconboot line, etc. Each corresponds to it's description. You can also temporarily disable the fconboot option by choosing fcoff, then rebooting to re-enable.

Don't know...try re-downloading and restarting recovery.
[Desire HD Android Development] Rikodu:
Just flashed the 0.3 kernel, I'll flash the newest version and report back

Thanks a lot Synergye, ur doing a great work
[Desire HD Android Development] synergye:
Thank you, but I messed up...I had forgotten to copy the fixed set on boot/off boot scripts into the auto-zip folder I use. I just uploaded v0.4.1 with the fixed scripts for setting fastcharge on boot, and removing the on boot functionality.

Edit: wow...third times the charm
[Desire HD Android Development] Rikodu:
I flashed the 0.4.1 kernel , taped the cammands ... everything's working good so far

But how to know that my phone is fast charging ? (dumb question)
[Desire HD Android Development] zomer331:
My fault. You have right, I downloaded bad, not full size file.

Thanks
[Desire HD Android Development] synergye:
It will say so in the battery log due to a line I put in...I'm mobile and don't remember what it is but I'm sure it has either fast or force in it, so you could get a log and ctrl-f. In any case, it took v0.4.2 to get the on boot scripts working right...third time's the charm I guess.
[Desire HD Android Development] zomer331:
Edit:

Are You going to add some toogle of FAST CHARGE in notiffication bar or new options in codefireX settings ROM for easier use?

:)
[Desire HD Android Development] Rikodu:
Maybe I should wait for v0.4.3 to be uploaded lol :D

just kidding

Im dowmloading it
[Desire HD Android Development] synergye:
Yes to both. The fast charge sysfs line is pretty standard I used, so most devices that support it will be able to use the setting :D. I have no clue what went on with the AOKP toggle, haha.
[Desire HD Android Development] zomer331:
Hah, ok, I see. :) I saw a option for it in main aosp settings.

For sure, isn't fast charge dangerous for phone(mainboard, screen voltage, cable etc)) or for battery?

What's Your opinion?
[Desire HD Android Development] synergye:
Not this implementation. It just sets the mode in USB charging to AC. Great for car chargers, cheap chinese chargers, or computer charging.
[Desire HD Android Development] Rikodu:
strange, i still dont have the fast charge mode. should i reboot or what ?
[Desire HD Android Development] LinoX:
Synergye, thanks for the reply but I think it's something different.

I did a lot more tests and I found that with 0.3 stable AND performance governor (it should always stay at max freq or am i wrong?) i can run the phone really fine and without problems at 1843 mhz.

Something strange happens with smartassv2 or performance at 1305/1401 it just hang the phone when selecting them.

With cm 7.2 default governor (was it ondemand?) and frequency table I always used the phone at 1520mhz max (don't remember the number but I'm sure it was 1.5ghz)

So I set the phone this way:

in settings 1843mhz/performance/set on boot

in setcpu 149/1200/smartassv2

Basically the phone boots as high speed (I didn't try higher speeds because I don't want to risk) and then I lower the cpu.

No hangs so far.

Maybe there's something wrong in the 1.3/1.4ghz? Can you check it?

I would take a picture of the cpu times in states but I'm missing the "Take screenshoot" entry in the power button menu.

Thanks again.
[Desire HD Android Development] synergye:
Ugh, because of where I put it, it doesn't show up in a standard logcat (but *should* in a kmsg). I'll be sure to add better logging later.

Looking into it. Awhile back on the Andromadus kernel there was one bus clock alone that a few saga devices really didn't like. I have a feeling it could be the bus clock used for one of those in the performance kernel which is why it's not going so well. They (as you) can use higher and lower bus clocks, but that one stopped users from using it. It was ~1.534GHz if I recall correctly. I may just have them use the next step up for the performance kernel and see how that goes as a test for you...for now I need to sleep.

Edit: I just realized that due to not adding a line to the fconboot script, if that script is alone run, a reboot is required for it to take affect. I apologize to anyone who used that script only without rebooting. I will fix it in the next release.
[Desire HD Android Development] Rikodu:
No harm done , you did a great job, and you need some rest

Have a good night :D
[Desire HD Android Development] LinoX:
Thanks mate (not for my particular problem, for all your work).

Sweet dreams.

PS: There's a breakfast for you when you wake up 37V84645EU062853B :)
[Desire HD Android Development] synergye:
Thank you! I'll be doing a new performance bus table tomorrow to troubleshoot and hopefully allow more to run it if that is the issue (which makes sense). Have a good day or night.
[Desire HD Android Development] estremodesign:
http://xdaforums.com/showpost.php?p=32751996&postcount=10886 :confused:
[Desire HD Android Development] rikusuicide:
which kernel should i use with jb paranoid android?
[Desire HD Android Development] synergye:
I have looked into this with a guy on IRC who suffers this problem. The facts are that people with the same panel have no issue. And the hardware doesn't vary THAT much on these devices. The logs (kmsg, dmesg, logcat) look the same as on a device that doesn't have this issue with your panel , so without an affected device there really isn't much I can do. Basically testing blind for a problem which will have no changes on logs. I'm really feeling like it could be a hardware issue since so few users have the issue (when many with identical hardware don't), and the device is a bit older (old enough for hardware to start going bad like this. I'm sorry, but this is just how it is, and I wish there was something more I could do.

You may try the performance variant to see if your device can run it, otherwise stick with the stable version.
[Desire HD Android Development] estremodesign:
Understand, but this problem just jb 3.0 kernel older jb kernels no problem and not one me :( (sense kernel 3.0 rom no problem )

http://xdaforums.com/showpost.php?p=32755334&postcount=10895
[Desire HD Android Development] dr0o2o:
I have this vertical lines display bug too. I don't know it can help but I noticed whole screen is with vertical lines when is off. It's hard to see it but I see this on specified angle when direct light spots on display (lamp). It looks like rainbow lines from bug fixed already but barely visible.

Another bug that I'm facing on every jb rom with your kernel is black screen with backlight on when sound is played and display is off. I'm wondering why my device is so unique because it should be fixed by paul_nl commit long time ago. Actually it's fixed for everyone but not for me. I posted this issue on your cm and jelly time bug trackers with logs and video. I can provide additional info if you need. Currently I'm using ice cold sandwich with no issues but jb is so smooth compared to ics...
[Desire HD Android Development] artov:
Flashed the V0.4.2 stable kernel on top of Jellytime R12 and it's smoothness is unprecedented. Absolutely 0 lag! For the first time I have the feeling that JellyBean is working as it should be. Thanks Syn!
[Desire HD Android Development] rikusuicide:
is it normal that the performance kernel has higher drain?
[Desire HD Android Development] chrisz5z:
What clock speed do you run?

Only ROMs that have given me 100% smoothness was variants of aosp gingerbread & sense 4a. I've tried all aosp based ics/jb roms & can't seem to get it, maybe just my phone

Sent from a satellite
[Desire HD Android Development] artov:
SmartassV2 min 245 max 1024 and it's totally solid, these are default in the kernel.
[Desire HD Android Development] iPwn_:
Aosp GB was smooth?? Lol what...

Just scroll through any app that has a list or open the web browser and scroll or zoom and everything runs at like 5 FPS. Put too many widgets in the launcher and it lags.

Anyway, the JB ROMs are choppy when the DRM Protected Storage process is running on the first boot but after that they are the smoothest ROMs for Ace by any measure. The launcher never skips a frame, the notification panel never skips a frame, the multitasking tray never skips a frame, the web browser is as smooth as Safari in iOS, etc.
[Desire HD Android Development] synergye:
Have you tried aospx or codefireX?
[Desire HD Android Development] WordsworthESP:
Hmmm... I'm guessing it's your configuration, as both are far smoother and have less lag than ANY Sense ROM I've ever used - stock GB ROM included. Even older ROMs like Redemption ICS were faster on my device.

Sent from my Inspire 4G w/codefireX
[Desire HD Android Development] chrisz5z:
When it comes to scrolling smoothness, sure ics/jb wins. With transition animations i always have stutters. Sometimes i turn animations off all together because it gets annoying. Never had transition stutters with the latest BlackICE. As for raw speed codefireX is quicker

Yep, i have.....codefireX is faster but has more transition stutters than aospx....doesn't matter how much i overclock it. Wish i could get your performance kernel working but it freezes before i can get to the launcher :)
[Desire HD Android Development] qazsxdcfv:
Man , im using CM10 ,... does the performance kernel gave the battery insanity ? Thanms

Sent from my hTC Desire HD powered CM10 by Syngergy(e)™
[Desire HD Android Development] bananagranola:
Are you asking if the performance kernel drains battery faster? I haven't noticed that it has; in fact, both the recent kernels have seemed to improve battery life by quite a bit.
[Desire HD Android Development] synergye:
That's an issue with the adreno blobs we're using right now. They're considered early jb preview, and dropped graphics performance way down. Even my sgs3 which blows the Nexus away in terms of speed, is far less fluid than the Nexus due to the early adreno drivers. From what I've heard, it's mostly due to excessive debugging.

Sent from codefireX
[Desire HD Android Development] csection:
I so want to use the performance kernel, but for some weird reason I can't (May be its just the crappy h/w in my phone). I am on 10/12 CodefireX Nightly

V0.2 would cause my european DHD to reboot continously (before actually entring the GUI of OS)

V0.4.2 would cause my phone to freeze just before the CynogenMod boot animation starts
[Desire HD Android Development] LinoX:
Same for me. Synergye is working on it :)
[Desire HD Android Development] bananagranola:
Wait, just to avoid misconceptions: no, I don't think he is working on making the performance kernel able to work on all Ace phones. He stated that he posted the performance kernel separately because he knew some phones' hardware would simply not be able to run it.

EDIT: apparently I'm wrong.
[Desire HD Android Development] LinoX:
He stated that he's going to change the performance kernel (working on the bus table) so that more Ace users can use it :)
[Desire HD Android Development] bananagranola:
Oh, ok, my bad. You must have more updated information than me. Ran out of thanks today; otherwise, I'd give you one.
[Desire HD Android Development] LinoX:
sarcastic, dude? :) look @post 103. I understood that but maybe I got it wrong...
[Desire HD Android Development] synergye:
Alright guys, have a far better fast charge behavior now for the next release...no need for ****ty scripts any longer (now based on yank555-lu's sensation patch). Now working on a good way to enable/disable sweep2wake. I want to refrain from scripts, but force sysfs modifications to stay over reboot. This way it can stay clean for the nightlies so I don't need to copy any other scripts.

Due to how improved fast charge behavior is, I may end up just building separate versions for sweep2wake for now so I don't accidentally create new bugs for enabling/disabling on boot (or other sysfs bugs), and can release a solid kernel first. Also tweaked the stable variant's bus clocks a bit more to better tested clocks in hopes this users have better 1.7GHz+ clocks ;).

Edit: let's all calm down a bit...just read posts above mine. On rootz I say "this isn't XDA," when people get upset at one another. Now I think I'm just going to say "this isn't sparta."

Edit2: I may have figured out the boot issue as well, but I'm not going to release yet until I can properly test. I was able to recreate and make my device nearly unusable...that doesn't mean that I fixed it, haha.

Edit3: yeah...no s2w yet.
[Desire HD Android Development] bananagranola:
Wait wait, i'm not being sarcastic. Sorry if it came off as such. :) I just didn't see post 103 and just went with what synergye had said about the performance kernel before that. I just looked at 103 and you're right, it looks like he'll try some new tricks (which I don't understand) with it to try to get it to work on more phones.
[Desire HD Android Development] LinoX:
No problems :) I supposed you didn't read that... I wasn't upset, I used the smiley :)

Thank you all.
[Desire HD Android Development] synergye:
just uploaded v0.5. PLEASE read changelog and also the new info on fast charge. There is now no need to use scripts or manually enable in most situations.
[Desire HD Android Development] Rikodu:
Guys !!! this is chineese for me ...

anyone can make it easy to understand please ?
[Desire HD Android Development] synergye:
There's a new default behavior now. Any usb device that doesn't act as a peripheral (that you can't mount your phone as storage on) will fast charge. This means any car charger, wall charger, or other powered usb port with no peripheral capability will use fast charge. In other words the only device that won't fast charge is your computer (safer this way). If you really want to fast charge on your computer, then you can type the following in terminal emulator (or adb shell): echo "1" /sys/kernel/fast_charge/force_fast_charge

I recommend you stick with the new defaults however ;). Most use fast charge because of chinese chargers, or car chargers anyway.
[Desire HD Android Development] Rikodu:
Love you man !!!

I'm hetero .....
[Desire HD Android Development] wigankev:
What changes are you putting into Nightlies? Just Kernel? If so i'll flash this now