yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] grimstar:
No Boot after reboot

Hey everyone...long time lurker, first time poster.

I just updated to 1.1.0 and everything was fine until i try to reboot. I get the HTC Evo logo and it just sits there. I also experienced some some reboots on the phone after switching from 1.0.2 to 1.1.0. I have 0004 hardware.

I can atleast confirm that the camera was working (front and back) and camcorder mode worked for me. I'm willing to help debug this issue with the devs to see if it isn't just an isolated incident...I also tried doing a wipe and reinstall of CM 6.1.1 & kernel which resulted in the same issue. :confused:

edit: Just to make it clear, I was able to boot up the first time after flashing. Once I hit the OS I did a reboot without changing any settings. All I get it the white screen. Nothing else. If I pull battery and go into recovery (amon 1.8.0) and reflash the kernel I can boot back into CM. If I reboot, same thing happens.
[EVO 4G Android Development] patelkedar91:
Any 3d benchmarks on this?

An3dbenchmark / Neocore / Nenamark / etc.

What about any high-end games like Dungeon Defenders, Shrek Kart HD, Toon Warz, etc?
[EVO 4G Android Development] jr19703:
I had the reboot issue with new BFS. It flashed fine and booted the first time then on the reboot hung on the white screen. I tried the CFS twice and could get it to load. I wiped everthing 3 times before flashing on RA 1.8. Oh and no camera on hardware 003 with the BFS. Went to clear cache on camera settings but was not highlighted?

Jason
[EVO 4G Android Development] conflikt:
New kernel is awesome, don't get much hang time on boot. That sucks Collin_Ph won't work, think it would be possible to update it if it is possible and add to the thread?
[EVO 4G Android Development] bbedward:
Im going to bed, but as for the benchmarks i get around 32-33 on neocore and about 20-21 on nenamark when overclocked to 1.15

I phrased that poorly, it's not recommended to use the tweak on a kernel with havs, but if you are using the SVS builds there will be no conflicts and it should work fine.
[EVO 4G Android Development] conflikt:
tried the fastboot.exe command, said error: cannot load 'splash1.nd'
[EVO 4G Android Development] conflikt:
thank you, ill more then likely try it out, i know the AVS version seems to run better for me, although when i was running no-havs with collins tweak i was getting crazy battery life.
[EVO 4G Android Development] land2634:
I'm having reboots with all versions of 1.1.0. The reboot happens when the battery is charging and hits 100%. Then it hangs at the white screen. I have to go in and clear cache/davlik to even get the phone to boot again, only to repeat the process once the battery reaches 100%. I usually keep wifi on around the house, so that could be it.
[EVO 4G Android Development] conflikt:
Post a logcat, I'm sure bedward can figure out the problem from there.
[EVO 4G Android Development] land2634:
I'll probably give it a go tomorrow. Gotta get some sleep and had to flash back to the stock CM kernel to make sure my alarm goes off in the morning lol.
[EVO 4G Android Development] bbedward:
splash1.nd needs to be on your local computer and it just can't find the file (make sure you used the correct path), or just put it in the same directory as fastboot to make it easy
[EVO 4G Android Development] gswarriorfan:
Do I need setcpu for this kernal to work correctly?
[EVO 4G Android Development] thedarksavant:
No. Some people turn it off and get better performance and battery life. Others have reported that they need it so it doesn't throttle too low and cause poor wake performance.

I've tried it with and without SetCPU and have no strong opinions either way.

If you really want the skinny, search around. There's a lot of posts from both sides of the fence from those claiming SetCPU gives crazy battery life and performance to those claiming Android doesn't need CPU throttling and it could damage your phone.
[EVO 4G Android Development] conflikt:
couldnt flash the splash screen because i am not running .76, am running .79 so what i did was renamed the splash1.nb to splash1.img. I then made a PC36IMG.ZIP with that and the android-info.txt file in it put it on the root of my SD Card, then flashed that way :cool:

Id imagine a few people might end up having to do it that way because of the .79 Hboot with the older 002 hardware evos haha
[EVO 4G Android Development] Mayonesa:
questions... i was on GB but jumped back to Miui... i am using this kernel and the phone feels fine.. fast etc.

i did however noticed the trickle charging not working. of course i wasnt sure this would work since im using Miui but i wanted to try.

at the same time i did noticed trickle wasnt working right ( as it did in the early stages of the kernel... any trickle kernel...)

using the batt moniter app and it doesnt go to the 0 Ma like it used too.

dont know
[EVO 4G Android Development] mlmob:
Loaded up setcpu (no pre-installed defaults on CM 6.1.2), and it says the default gov was ondemand - supposed to be smartass right? Giving that a go with your tweaks :)
[EVO 4G Android Development] dthomas03:
Is anyone else having wake screen issues during an incoming call? I am using svs + cfs 1.1.0 kernel ...on CM 6.1.2. SetCpu is set to conservative [1113 - 384].

Other than that...this kernel is very nice. Thanks for all ur hard work!
[EVO 4G Android Development] conflikt:
wow, the BFS/AVS with the newest MIUI is very very snappy and awesome battery life. Also downgraded from .79 hboot to .76 hboot so i can use fastboot to flash splash screens instead of putting it in a zip then flashing and all that other not so fun stuff.
[EVO 4G Android Development] Crossrocker:
Bbedward, pmed you

A drop of Chuck Norris's semen was placed on the IPhone. We now have the Htc Evo.
[EVO 4G Android Development] EndlessDissent:
I'm using MIUI, and my trickle charging is fine with 1.1.0 BFS + AVS.
[EVO 4G Android Development] EndlessDissent:
@bbedward, do you use the old updating scripts for your zips (Amend), or the new scripts (Edify)? I was about to flash Clockwork 3.0.0.4, but it only works with the new scripts.
[EVO 4G Android Development] bbedward:
Anykernel uses the newer scripting so you should be fine
[EVO 4G Android Development] Mayonesa:
weird cause trickle hasnt been working for me.. it did at 1st in the early stages of trickle but not on the latest... its not just kernel, its the other found here.

not sure what i may be doing that may cause it not to work right.
[EVO 4G Android Development] EndlessDissent:
Thanks. Unfortunately, Clockwork is still a little buggy. Went back to Amon. Good timing, too. Looks like he's about to release his updated recovery.
[EVO 4G Android Development] EndlessDissent:
Hmmm... I had my phone on the charger for, like, 16 hours or so, and all I had were 0, -1, and the occasional -2 mA values.

Did you use the phone after it reached 100%? Have you tried reflashing the kernel? I have no idea why it wouldn't work.
[EVO 4G Android Development] Mayonesa:
it use to reach 0 ma but not any more... dont know if something is working on the phone preventing it from charging that far.. no clue...
[EVO 4G Android Development] EndlessDissent:
Check Spare Parts for partial wake usage. Maybe some app is running in the background and using battery power.
[EVO 4G Android Development] Brian Rubin:
Hey, n00b question. This looks like a neat Kernel that I'm tempted to try, but I wanna know. I'm running Cyanogen 6.1.2 on my 0003 EVO. That being said, which kernel should I use, CFS or BFS?

Thanks!
[EVO 4G Android Development] thedarksavant:
Start with BFS and if you have issues try CFS. Same with avs. Start with it and if you have issues go to svs.
[EVO 4G Android Development] Brian Rubin:
Got it, thanks!
[EVO 4G Android Development] EnderTheThird:
I'm running CM 6.1.2 on my 003 Evo, and I had trouble with random reboots using BFS w/ avs. I'm trying svs now. Just so you know, in case you run into the same problem.

Update: Still getting random reboots. Went back to stock CM 6.1.2. Wish I knew what was going on here!
[EVO 4G Android Development] Crossrocker:
Everyone!!! Use smartass+bfs avs+ setcpu 844 Max 245 min. This will give best performance and best battery life. Try and report back. Then spread the word :D

A drop of Chuck Norris's semen was placed on the IPhone. We now have the Htc Evo.
[EVO 4G Android Development] Brian Rubin:
Thanks for the warning! I'm currently using the SBC version 8 beta kernel and am testing it out a bit, but I like it so far, so maybe you could try that one.
[EVO 4G Android Development] anaglich:
BFS AVS provides poor scrolling performance, no matter the configuration. CM7.

BFS SVS still poor in terms of usability/ smoothness. Harder to tell, but would appear to be just slightly "quicker" than AVS in this situation. CM7.

CFS AVS is much snappier, smoother to the touch. (Please note I was experiencing random reboots the last few days with this kernel. Could be the kernel, could be my alpha CM7 rom. Still, my preferred kernel. CM7.

CFS SVS is close to the AVS build, however I do still notice a jittery feeling to it. Flashing back to AVS. CM7.

My findings do not reflect battery efficiency at this point, but to me, knowing SBC is included and that I am wise with my usage, I am looking for smoothness in a kernel. To be honest, even with OC and with a performance governor, I am still waiting for a completely smooth kernel. And hey, if you would like to make my day, you could provide me with the latest CM7 kernel, SBC code infused. I would really appreciate it.
[EVO 4G Android Development] mwielgosz:
Im just wondering if a non sbc version of this kernel is (or could be made) available. The more I read, the more im skeptable about using the sbc mod...there's really no decent concrete evidence either way. Nothing that states that sbc DOES hurt the battery and nothing stating that it DOESNT (its all non specific not related to the mod itself). Personally, I've been using the mod for about a month already, but I feel that my overall battery life is faltering. May just be my imagination but id like to be careful.

Love this kernel and im sure there's a bunch of other people that wouldn't mind not having sbc.

Thanks

---

Evolved into a higher form of communication
[EVO 4G Android Development] bbedward:
http://downloads.zen-kernel.org/zendroid/ZenDroid-1.1.0-BFS-avs-NO_SBC-signed.zip

That's the only non-sbc variant I built, and I just happened to upload it a few hours ago ;)
[EVO 4G Android Development] anaglich:
The way I see it, at worst you will already be on to your next phone before the advantages to SBC are diminished by the disadvantages. Trickle charging never hurt anyone. The temperature is not significantly higher either. It is just seeing slightly longer charges.
[EVO 4G Android Development] conflikt:
Noticed after running both svs and avs of the BFS my CyanogenMod would bog down and run slow within a few days or so. Also experienced GUI jitter as well. I'm trying the CFS svs now, if all goes well ill do a nand backup and try the avs cfs version.

Another problem that I am having is that when I reboot my phone tends to sit on the splashscreen for about a minute before loading CyanogenMod. I did wipe cache/davlik cache and did not have setCPU running. Anyone experiance this? I'm running the. 76 Hboot and RA recovery.
[EVO 4G Android Development] bbedward:
I just equipped 3 EVOs with the bfs avs version (1 002 and 2 003's) - they all are on cm 6.1 and have the same results I have in terms of performance, if not better -> interesting how the devices vary so much :D

The CFS ll features that android kernel devs seem so fond of have only hurt interactivity and smoothness in my opinion, but the tweaks have raised quadrant scores (interesting enough). I'll see what I can do about a snappier CFS version (it may mean reverting most of the tweaks, granted they seem to be working for some people)
[EVO 4G Android Development] mwielgosz:
Cool thanks.

As far as temperature goes, sbc keeps the temperature very low when trickle charging. Its just that I just went out and bought this extended battery and I really don't feel like putting it in (possible) harms way quite yet. I love the way sbc works, i don't want to be the first one reporting on issues lol.

Thanks again everyone

---

Evolved into a higher form of communication
[EVO 4G Android Development] anaglich:
You are not alone. I always thought I needed a custom kernel to get the best battery life an performance, but after just flashing back to the CM stock, I couldn't be any happier. It was made for the rom and runs like butter. Excellent battery life to boot.

Now if only it came with Superior Battery Charging code...
[EVO 4G Android Development] Crossrocker:
Huh.. I don't have the same experience ever. It feels like a sense rom without zendroid or snap .. both bfs smartass

A drop of Chuck Norris's semen was placed on the IPhone. We now have the Htc Evo.
[EVO 4G Android Development] bbedward:
The stock CM kernel is sufficient, it's a bit less of a performer (most people don't notice) and the battery life is a bit less (havs improves that greatly, bfs is potentially a small improvement)
[EVO 4G Android Development] Crossrocker:
My music would lag and I could never multi task smoothly. That's the only reason I used cm and not a sense rom.

A drop of Chuck Norris's semen was placed on the IPhone. We now have the Htc Evo.
[EVO 4G Android Development] thedarksavant:
This makes sense. From what I've read and the tests results I've seen for Linux scheduling, CFS is great at batch processing and BFS is better at user interaction. So I could see how a BFS kernel could provide smoother user experience, while a CFS kernel kicks @$$ in quadrant.
[EVO 4G Android Development] EndlessDissent:
Yup. That's why I don't put much stock in benchmarks. The only one I use is FPS2D, and I only use that to test the stdev. (A low stdev means a smoother, more responsive experience, and it's very noticeable)
[EVO 4G Android Development] EJerVJerO:
If you watched the SBC threads you would know extended batteries have been tested and built on for quite awhile now with the kernels.
[EVO 4G Android Development] mwielgosz:
I've been following the thread and understand this. What I meant is that since I bought the extended battery, I don't feel much like having to waste the investment if this happens to turn into a sour apple 6 months to a year later. I still have a long time on my contract and there's no way im buying a cheap chinese battery again. Besides, I've been using sbc on the battery and it works great. Its more that its come to a risk im not willing to take atm.

Thanks!

---

Evolved into a higher form of communication
[EVO 4G Android Development] LifeInTheGrey:
I wanted to give a thank you to bbedward for this kernel.

Back in mid-December, something shorted in my phone and it severely diminished its ability to hold charge. I have been dancing with Sprint over the last three weeks attempting to get a replacement (as it is only 2 months old), and they have been on backorder for replacement inventory and have no notice about when they will be receiving a new batch. I actually unrooted it for the store to examine this problem, and they determined I would get approximately 4 hours maximum of battery life, and have since given me credit after credit deduction on my bill. As I simply would not tolerate having an operational phone for only 4 hours per day, I rerooted and went back to CM6 and ZenDroid knowing I would get better battery life from it.

I get about 17 hours of life from it now.

Obviously under normal conditions this would not be a feat, however it is over four times the life I would receive stock with approximately a 45% performance increase (based on Quadrant scores). I am truly endebted to you, for without this kernel (and CM, of course) I would be having a FAR more difficult time tolerating this.

So thank you, I appreciate your work; just wanted to share that.
[EVO 4G Android Development] Crossrocker:
Zendroid needs more popularity.. I'm experiencing the same results as snap.

A drop of Chuck Norris's semen was placed on the IPhone. We now have the Htc Evo.
[EVO 4G Android Development] wase4711:
if it didnt hang up/freeze on so many phones, it probably would be used more.

I've tried it on 2 EVO's numerous times, and I can NEVER get it to work for more than one reboot...
[EVO 4G Android Development] anaglich:
-----------------
[EVO 4G Android Development] conflikt:
Tested all 4 versions. All 4 start to run choppy within a few days. Also have slow boot times and screen lockups and random reboots/crashes I use CPU but only 998/285. My SD card is well organized and I just updated to the newest RA, radios/pri/prls. Going to try savage kernels to see what happens. The teams 1.5 removed SBC because HTC added in some sort of trickle effect. Ill report back, now running 1.5 BFS & HAVS without SBC.

Thanks for the hard work Zen. Think it would be possible to remove SBC and add the new HTC code? Also do you think with too many tweaks added into a kernel it would make certain phones run funny? Just wondering. I'm thinking its the low voltage, as with a CPU processor, not all processors play good with voltage. Although I got a G0 stepped Q6600 oc from 2.5-4.0 on stock voltage and air, been running it for 2 years with 0 problems. Have Gentoo on my 2nd hd. Althogh in th past BI've bought many processors that didn't overclock so well and required more voltage to overclock or vice versa.
[EVO 4G Android Development] bbedward:
Not sure , voltages are most likely anyway to cause instability, although I think kernels like netarchy and savage undervolt more hardcore than I do.

I have some CPU stuff for the 1.1.1 build, and my laptop is having some issues so it's going in for repairs this week, and it will take about a week -> so i'm cranking out development before that happens :P

I'm working on something a bit more special too -> that is, a 2.6.36 kernel base. I've nearly ported all of the stuff from the CM unified kernel to the 2.6.36 kernel, including the supersonic stuff. When I'm done I'll release a stock kernel test build (meaning basically a stock 2.6.36 kernel with the CM configuration and none of the zen stuff), to see how it goes ;)
[EVO 4G Android Development] conflikt:
Awesome, cannot wait. As said I'm thinking it is voltage issues. Because as others posted before that they run better on cm6 stock kernel. I'd be more then happy to beta the kernel.
[EVO 4G Android Development] conflikt:
And as said, i know from building custom PC's and overclocking or underclocking GPUs that 60% of the time you don't get a stable overclock or underclock with processors, that is without cranking up the voltage which then results in instability problems. Then other times you wont even get an overclock without having problems because the CPU/GPU cannot take the overclock or underclock. Heh before Sli come out I was running an old nvida card that wouldn't overclock or underclock without having problems, and that was with a aftermarket heatsink.
[EVO 4G Android Development] Crossrocker:
Gahhh! I hate this. Why cant zendroid achieve the same popularity that snap had?? Just because bbedward is a new dev doesn't mean he can't develop the best(my opinion) kernel form cm6. It drives me crazy when I compare the popularity of this thread with savage kernel! Haha sorry for this rant I had to get it out.

PS I think I'm like advertising your kernel. Lol every thread that asks for best batt life and best performance I just tell them zendroid. Boom! Haha

Ps2 love this kernel (incase you don't alredy know) :)

Okay I'm done. Peace

A drop of Chuck Norris's semen was placed on the IPhone. We now have the Htc Evo.
[EVO 4G Android Development] LifeInTheGrey:
Well I believe that Zen is missing a graphics suite that Snap has. We need a maestro like shift on our team.

Ride that evo train
[EVO 4G Android Development] BlueHarford:
No we are less aggressive. It would be nice for you to collaborate then just copy we've had in a public .36 Git on Git hub for well over 2 weeks
[EVO 4G Android Development] Crossrocker:
Haha I know you feel the same way too ;) and snap gained popularity before shift released graphix for it.

A drop of Chuck Norris's semen was placed on the IPhone. We now have the Htc Evo.
[EVO 4G Android Development] bbedward:
wasn't positive on the voltages, I'll probably end up raising them a bit next kernel build.

and didn't realize you had a .36 tree, doesn't look like it's working yet. I believe I got a .36 finished and compiled yesterday but i accidently reset the git tree :cool: so I lost a bunch of the fixes I made and have to re-do them.

Oh, and just curious, am I "the douche" lol, just curious -> not sure what I could have done to piss you off so it must be someone else. (I don't follow your github or anything, so I wasn't positive on your voltages or .36 tree, i just assumed they were more like netarchy's)
[EVO 4G Android Development] BlueHarford:
it compiles, just missing somethings.. its 95% there working on it now...

our tree has been public since day 1.
[EVO 4G Android Development] BlueHarford:
no, we are cm-kernel based and we made our changes ourselves, we got HAVS from intersect raven and SBC from M, and thats it, the rest is done manually by us.
[EVO 4G Android Development] MarkGbe:
any chance of getting a non HAVS version of the latest version?
[EVO 4G Android Development] Crossrocker:
Pm him

A drop of Chuck Norris's semen was placed on the IPhone. We now have the Htc Evo.
[EVO 4G Android Development] bbedward:
In the first post download one of the SVS versions (1.1.0 is the latest version atm)
[EVO 4G Android Development] MarkGbe:
ahh ok. i'm confused on the SVS thing. Hopefully it works ok. The default cyanogenmod kernel gives me random reboots.
[EVO 4G Android Development] thedarksavant:
All I know is after 16+ hours of evo love yesterday, I plugged it in and went to bed with 30+% battery left. I'm sure this is not all Zendroid, but I always seem to pull off these kinds of days when I'm using it.
[EVO 4G Android Development] bbedward:
Knock it off, this thread is going off topic...

2.6.37 kernel isn't practical yet because there's no stable android 3.6.37 source yet, 2.6.36 is barely practical considering there's no 2.6.36 msm source - but it is possible to whip together the msm parts.

And in other news...My laptop is officially off for repairs. I have my desktop until friday before i leave, so development will slow down for me anyway :P

Racing to get the latest upstream source isn't really a big deal anyway, it's a lot easier to just take changes that make a difference and apply them individually.

*edit*

Here's my 2.6.36 source, if anyone's interested in testing it. All the commits from cyanogen's 2.6.35 unified tree are within that first merge.

http://git.zen-kernel.org/zendroid/log/?h=android-msm-2.6.36-unified-zen
[EVO 4G Android Development] xNotta:
Would the kernel be causing my phone to keep rebooting when wifi is enabled?

My Evo made me Swype this from the XDA App.
[EVO 4G Android Development] bbedward:
Considering my time constraint expectations of 2011 i would love to collaborate, we were very successful (and still are, even though i haven't touched the git in awhile) at collaborating for the zen kernels (zen, zen-stable, zen-mm, and zen-rt). This is a slightly different situation. Last time I suggested just collaborating I was shot down, so i just continued doing what I was doing.

The whole reason I made the kernel was because there was nothing else that I really wanted to use, being that I have access to git.zen-kernel.org, I figured I'd make it public :D

I'm pretty satisfied with what I have right now and there's not really much more I want to do to the source except keep it updated and fix anything, if applicable. I only made a 2.6.36 base because I had nothing else to do (bored after the holidays). I didn't fork savage's because I didn't realize it was there, and when I did look at the git I didn't understand it (too few commits, I didn't know what was missing or complete or anything about it). I don't know if my source works yet, but everything that needs to be there is there.