yashsingh1/xdaforums huggingface dataset:
[Epic 4G Android Development] vocaltreat:
ok sir.....calm down.....#1 ive seen this happen before on different roms......all our phones have minds of there own.... are you on eb13 or eco5......are you on rfs or ext4.....i like to know these things...it helps me to better help you....have you already odined and started fresh?
[Epic 4G Android Development] thedevilslettucemd:
Like I said, my phone won't boot unless i'm lucky. I can't get into recovery to even flash a new kernel :/
[Epic 4G Android Development] thedevilslettucemd:
I apologize. I just didn't appreciate the "It's your fault" response. I'm on Syndicate 1.1.0 so EC05/EXT4. I can't get the phone to even start so it's impossible for me to odin or flash a new kernel. Is there a known trick to get the phone to boot from this state?

Sorry for the double post.
[Epic 4G Android Development] chris41g:
ive been a strict visionkernel user, before that twilight kernel... but this is definately a kernel issue. its not user error. at least not on my phone. i monitor my phone carefully, i partitioned it myself, it runs journals on, with writeback journaling. no undervolting. i stress test it at every level. i dont apply settings at boot. this is not a mere your phone cant handle the clock error...

@trobertson, try hitting the power button repeatedly while putting the battery in, that worked for me a few times...
[Epic 4G Android Development] robl45:
can anyone tell me definatively how the heck to tell if an app is causing the phone not to sleep? I've tried many times and can never figure out a definative way to see. but I know something is weird.

I fully reset and wiped the phone. I went ahead and tried the new ACS rom and this kernal. spareparts is showing phone running at 14% now when I couldn't get below 20% before. so something was screwing it up. but I've used those apps all before so I'm really confused at this point.

I have setcpu, running ondemand 100-1000 and voltage control doing bfq schedule. I have my remote desktop program installed and mybackuproot. nothing else. so is there a specific program that will show when its not sleeping? I've tried a lot of them and not much luck figuring anything out.

and can I just say DAMN ACS is such a smooth rom.
[Epic 4G Android Development] kstephens98:
I've had trouble with this kernel also. I've tried 3 different roms and it always ends badly. I'v had to Odin back to stock 3 times cause it continuously messes up my phone and my cm recovery. Flame if you must, but this kernel is not right. 1.1 worked great. 1.2 not so much.
[Epic 4G Android Development] theimpaler747:
Did you use the trick posted about 1 page ago?
[Epic 4G Android Development] vocaltreat:
ok you said your phone boots SOMETIMES? ...when it does i would go to dl mode asap and odin that f er.........but till then.....pull bat and leave it out for like 20 min..just let it sit....then put back in and try it again
[Epic 4G Android Development] vocaltreat:
try cleaning your sd card up.....i think someone mentioned pulling sd card to see if it still acts up
[Epic 4G Android Development] vocaltreat:
that being the pull batt hit power button 2 times put batt back in and go to dl mode :)
[Epic 4G Android Development] vocaltreat:
by the way...i have ran this kernal for like 2 weeks with no prob other then it wasn't COMPLETELY stable on 1.45..it would freeze every once in a blue moon...but no corruption.......some phones just cant handle it....warning is posted in the op........ALWAYS read the warning....1.45 is pretty damn high for some to handle...and then theres unicorn phones like mine that can just about take anything i throw at it :)
[Epic 4G Android Development] chris41g:
yea and the warning says if your phone cant handle it.. it will lock up so just lower the clock and try again.. nothing about bricking, or making it almost impossible to reliably turn on.. there is something else wrong with the kernel, its not the purely the clock speed, as i stated, the phone handled the clock speed just fine, never locked up
[Epic 4G Android Development] thedevilslettucemd:
Yes I did, still no go :/.

Okay i'll try this. Has odining back to stock fixed the problem for some people? -crosses fingers-
[Epic 4G Android Development] chris41g:
Odining did not fix my problem, but it is worth a try...
[Epic 4G Android Development] vocaltreat:


Sooo while on stock...when u odined......it still had the same issue?
[Epic 4G Android Development] Custodian:
We as users accept this sacrafice.
[Epic 4G Android Development] Top Nurse:
A similar problem came up in the beta Bonsai 4.1.0. Since the same stuff is going on I will share my thoughts. I think we are really pushing the envelope lately on a good many roms. IMHO, some of our epic's have marginal hardware (though still sellable from manufacturers point of view) and what we are doing to them is bricking them.

Auto analogy:

If 5 people spend $50,000 each on funny car engines, from the same vendor, some are just going to run faster. Some will last 10 runs and some are going to blow up on the dyno stand.

We have not been able to ascertain why some (~10%) Bonsai 4.1.0 roms blow up. We have searched far and wide and down some arcane routes which leads us to an inescapable conclusion: If you can't afford to race DON'T modify your engine...

Sent from Bonsai 7.0.3
[Epic 4G Android Development] thedevilslettucemd:
Unfortunately, I think my phone is completely bricked. I can't get it to boot at all now.
[Epic 4G Android Development] epic4GEE:
Ok with no answers to these couple of bricks.....I'm getting skurd. I'm still going to tough it out tho.....crossing fingers x
[Epic 4G Android Development] theimpaler747:
The answer was posted above. It is per phone; as Nurse so cleverly said, if you have no money to lose, don't race ;)
[Epic 4G Android Development] thedevilslettucemd:
I understand this concept clearly, but it is my strong opinion that a kernel should not even come close to bricking a phone at its DEFAULT settings. A kernel should be safe for ALL phones, not "capable" phones. In other words, a kernel should run the bare minimum safe settings for all devices, with an OPTION to push devices further. The attitude that is being taken with regard to this particular case is frankly upsetting to say the least. Yes, we take a risk installing any custom software but I think it's perfectly reasonable to expect a tested kernel (at it's default settings) not to permanently damage a phone. I appreciate everyone who has attempted to help me with this issue but I think I'm unlucky enough to have a $500 paperweight on my hands at this point. I will take the steps necessary to file a claim with Asurion. I feel completely responsible for putting this kernel on my phone in the first place, knowing there was a risk. However, the kernel developer should take responsibility for creating the software that did the damage, and recall the software being that there is CLEARLY a problem (before you wind up with half a forum full of pissed off users with bricked phones). That is all.
[Epic 4G Android Development] theimpaler747:
Hence on the OP:
[Epic 4G Android Development] hussmanne:
Another brick here, no power on, tried the battery out power button trick. Left it on the charger, switched batteries etc. I don't blame anyone, but I would think it would be good to temporarily pull the kernel and update the title/op until a fix can be found.
[Epic 4G Android Development] hussmanne:
Also, highest speed I was running was 1300mhz.
[Epic 4G Android Development] epic4GEE:
Not to argue good sir, but it was a good analogy....hardly an answer tho;)

I'm sticking it out though as I said, I will hold only my self responsible.

Question tho, I saw Chris was in srf 1.1, but what about the other guys?
[Epic 4G Android Development] k0nane:
Please note the ROM has absolutely nothing to do with it. Thanks.
[Epic 4G Android Development] thedevilslettucemd:
That's regarding OCing. My phone ran at your kernels stock voltages and no higher than 1.0GHz. Same with several of the others who are bricked. This is obviously something else and you need to stop denying that.
[Epic 4G Android Development] rjmjr69:
And also note the big disclaimer.........

Please PULL battery hold POWER button for upto a minute. let it go

Open keyboard Push the number 1 key hold then press power you should have

Download MODE....... Google
[Epic 4G Android Development] bigray327:
It's weird that I was running this fine since the minute it came out, and just tonight it started not powering on. I'm lucky, a battery pull is working.
[Epic 4G Android Development] theimpaler747:
There is something else with your phone most likely. As I mention, the majority of users are running this fine. Just because a few have issues doesn't make it a massive problem. Tom will look into it, but it is most likely either going to be fixed by him or an issue with some of the phones being pushed too far.
[Epic 4G Android Development] k0nane:
This - and we are on the case right now.

If anyone is concerned, simply flash back to 1.1.
[Epic 4G Android Development] rjmjr69:
Theres got to be a common cause here. What apps did you all recently add?did you flash a new theme? Or a new apk? App from here or another forum? Did you OC to much UV? did you match the hash for the download?
[Epic 4G Android Development] vocaltreat:
Please

guys when you have issues it is very helpful to us when you let us know

1: what rom you are on

2: if you are eb13 or ec05

3: if you are rsf or ext4

4: what kernel your using (of course in this thread we know)

5: Apps you were using (new or with kernel)...everything helps

6: how long you have been running Kernel or rom or what ever is the problem

If you think your phone is bricked....PLEASE take out batt for at LEAST 20 min....

Press power button 2 times before you put it back in (i know some of you have tried but try again after batt rests) Putt batt back in and try to go into dl mode. If you get there odin to stock ...ota to eco5...root, flash rom and keep the kernel it comes with or go to one your comfortable with.

Again i know some of you have tried most of this before but it doesn't hurt to try once more for ****s and giggles.......Sorry for the inconvenience,.... i dont think Thomas is around atm . But i know he will handle the situation :D
[Epic 4G Android Development] thedevilslettucemd:
A kernel's default configuration should not push

any

phone too far. Any potentially dangerous configurations should be optional with their own disclaimers, at least that would be the honest way to do it. It seems everyone who is having the issue is beginning to have the issue now so we will see just how many phones wind up bricked as a result of this kernel in the near future.
[Epic 4G Android Development] theimpaler747:
Not at all. The end user should be wise enough to read the disclaimer and know what they are flashing.
[Epic 4G Android Development] k0nane:
10-10-10char
[Epic 4G Android Development] thedevilslettucemd:
The disclaimer warned of overclocking and overvolting woes, I didn't overclock or touch the voltages. I still take responsibility for using the kernel in the first place, but it certainly isn't acceptable that the kernel contained

default

customizations that pushed my phone too far.
[Epic 4G Android Development] theimpaler747:
Please just read above. :rolleyes:
[Epic 4G Android Development] stir fry a lot:
What are you, 12 years old? Any logical person would look at 1.45ghz and know that there is a possibility of there being a meltdown. When flashing anything, especially kernels there is an inherent risk of something getting fubar'd.
[Epic 4G Android Development] epic4GEE:
I agree 100% k0, but it is something to note. If 100 srf users brick with vision1.2 and zero brick with bonsai on vision1.2, then its something you just can't ignore.
[Epic 4G Android Development] bigray327:
Sounds like you guys don't want to hear when your software is causing issues. Duly noted, there are other less douchey developers to try.
[Epic 4G Android Development] k0nane:
It is, though - overwhelming data suggests that. Also:

Anyone with issues, do this! Even if you can't get DL mode, this may well get you up and going!
[Epic 4G Android Development] hussmanne:
If you want to ride the wave of the future, you're bound to wipeout on the edges of the universe!
[Epic 4G Android Development] vocaltreat:
also agree....i only stated a run down of what info to give when your phone is screwing up with any problem in general.....not just whats going on here. :)
[Epic 4G Android Development] thedevilslettucemd:
Please refer to the following thread to see the damage that has been done by this kernel so far.

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

Read thoroughly before you flame like a child. I never touched the overclocking features of the kernel.
[Epic 4G Android Development] k0nane:
Folks, please keep it civil. Arguing is far from productive. Please try the tip above.
[Epic 4G Android Development] theimpaler747:
Again, we ARE looking at it. The fact is, you may not blame us for your responsibility as a user that you neglected. Please, try the tip k0 posted.
[Epic 4G Android Development] vocaltreat:
repost from k

Originally Posted by MysteryEmotionz View Post

Try resetting the hard ware.

1) remove battery door

2) look below camera on the left side. You should see a little hole.

3) using a ball point pen or bent paper clip insert the tip into that hole.

4) press and hold for 10 seconds.

5) boot into download

6) odin to ec05
[Epic 4G Android Development] stir fry a lot:
**** happens. Its working fine on many people's phones so far and I assume nothing happened to the handful of beta tester's phones before this as well.
[Epic 4G Android Development] dyehya:
Someone that is having issues getting the phone to turn on intermittently and is willing to try a slightly modified kernel based on Vision Kernel 1.2 BUT IN NO WAY IS OFFICIAL ACS RELEASE. This is just my personal kernel that I used to make it a bit more stable for my phone. I wasn't planning on releasing but as I haven't had a problem I am curious to see if my changes will "fix" the issue that you may be having. I am not releasing the file publicly but would like someone experiencing the issue that is willing to try it to PM me or talk to me on Fossnet IRC nick Cyc.

The major change is removing 1.45GHz (wasn't stable at all for me and I think the clocking not setting it to that high might be the cause of the issue)

I also added a 1.36GHz step as that is the highest my phone can go and maintain 100% stability. I left 1.4GHz there to try it but still freezes on occasion.
[Epic 4G Android Development] thedevilslettucemd:
I never knew this existed o.O. Trying right now.
[Epic 4G Android Development] chris41g:
I'd like to reiterate, I don't think there is blame to be spreading from anyone but the user who modded their phone (me) we all take that inherent risk. I was only informing of the situation, and trying to explain that I felt it is something other than just the 1.45 clock speed, as it ran stable on my phone, and never got hot, or force closed. I'm not new to this, and I don't believe that it has anything to do with just the clock speed directly.. the phone was behaving like it was out of memory, almost like it was right before I lost root with pimp my cpu.. I personally believe it is related to the memory UV. but regardless, like I have said before, I've always been a supporter of visionkernel, twilight kernel and acs.. I'm certain that whatever the problem is, whether its a phone tolerance problem or something in the code, tanimn k0nane and thomas will get it straightened out.. btw.. my phone seems to be straightening itself out just keep turning it on and off using the battery pull thing..
[Epic 4G Android Development] thedevilslettucemd:
I just took the phone apart, that isn't a reset button at all.
[Epic 4G Android Development] k0nane:
I'll take Mystery's word and three brick recoveries on it... (And I still don't have a device.)
[Epic 4G Android Development] thomasskull666:
Hey everyone, lemme say a few things to start off. Yes the user is taking the risk of flashing this kernel but they should be able to trust the developer to make sure it runs smoothly. That being said, something is wonky in the code that is causing problems on a few users' phones. I am looking into the issue as we speak and have removed the download link in the OP for the time being.

Please keep in mind that this apparently does not affect everyone, but enough people have had problems that I will discontinue development to make sure this bug is fixed.
[Epic 4G Android Development] MysteryEmotionz:
I will post a picture of the actual area in question in my thread. Some one already started in the other thread that they disamnled the hole phone and seen the button but had no idea what it was for.
[Epic 4G Android Development] k0nane:
Thanks for the update.
[Epic 4G Android Development] thedevilslettucemd:
Believe what you want, behind that little nub is nothing but a plastic transistor.

NOTE: I have one of the first phones to be released (Early September) so maybe newer phones have it and older ones don't?
[Epic 4G Android Development] MysteryEmotionz:
I have a launch device
[Epic 4G Android Development] musclehead84:
Come on guys quit blaming the developers. I bricked my phone from bonsai and I don't blame them one bit. Stay stock if you don't like it. Then u don't have to worry. Its not that acs doesn't like it if something is wrong with their software. If they did they wouldn't be looking into it lime they are. Why would they pull it. I've had no lockups running at 1.45 since it came out. My phone runs it just fine. Out of all the people that flashed this kernel there are what three bricks? That honestly isn't a high percentage. All I'm saying is thetmre is a disclaimer in the op. Don't blame them. They do this for free. Thanks all and good luck with your phones. I hope it all works out for you.

Sent From My Evo Killer!
[Epic 4G Android Development] djbacon06:
hear, hear! Our devs take good care of us. it's not like they are trying to cause harm to anyone's phone.
[Epic 4G Android Development] MysteryEmotionz:
hardware reset information can be found here http://xdaforums.com/showthread.php?p=13047288#post13047288
[Epic 4G Android Development] epic4GEE:
Right on Thomas, just so you know I'm not switching this kernel out until I see something I don't like and so far....I like:cool:

I know you and the rest of the acs team will figure this out.....if anything goes wrong I'll be sure to let you know, if all goes well I'll be sure to let you know.....thanks again!!!
[Epic 4G Android Development] stir fry a lot:
From the thread in general it sounds like a bad idea to use the power off/reset option in the phone's menu. Best just to pull the battery instead.
[Epic 4G Android Development] ecooce:
I just want to suggest one thing,that kernel devs leave screen/RAM voltage alone until you put more goodies in,and revisit UVing of screen/RAM later...

On another note,I think the "reboot mod" is flakey,anyone remeber windows 98/98se,it was shutting down and not writting everything it was supposed to...
[Epic 4G Android Development] MysteryEmotionz:
Theres claims of the power button causing issues also.

The reboot mod is done how it was on eclair. I doubt this is the root of the problems
[Epic 4G Android Development] itisagoodname:
One thing to add to this... every time i use the reboot function, it hoses my battery %. If i shut down normally, it comes back to the same percentage before shutting down.

just my .02$
[Epic 4G Android Development] ecooce:
I've had this happen many times when I was using this kernel,but also on other kernels,just yesterday before I odined I was at 68%,reboot,16%,turned the phone off,61%....
[Epic 4G Android Development] cache83:
i noticed that when i just flashed back to vision1.1 right now from vision1.2 (amidst all this madness -- just to be safe)... the "Build number" says VisionKernel v1.0 -ACS

also, i remember when i had vision1.2 installed the "Build number" was TwilightZone x.x - hajime something

... anyone else notice that? either that was a harmless discrepancy or i've been downloading the wrong VisionKernel_v1.1.zip and VisionKernel_v1.2.zip files lol
[Epic 4G Android Development] ecooce:
I noticed this,its because kernel devs went crazy (lol) and stopped using the standard location for kernel build info,shouldn't it be in the "kernel version" location... At some point you had TZ kernel,and when you updated to vision this info wasn't changed. As for the v1,he forgot to change the kernel version on that release...

Edit::: I had to start putting my ROM version in the "firmware" area,so my latest ROM was "Frankenstein ????? 2.2.1",lol,ohwell
[Epic 4G Android Development] Top Nurse:
It may help you to know that a dmesg log we got just before it bricked, on Bonsai 4.1.0, showed a whole bunch of oneDram errors. We couldn't find anything conclusive, but just some anecdotal evidence of some errors just before it bricked. Now how that translated to a brick is unknown, but some of us were hypothesizing that under volted ram may have beedn the cause.

Sent from Bonsai 7.0.3
[Epic 4G Android Development] westicle:
Impossible! The code couldnt be causing problems! The impaler said that any problems HAD to be user error, and you know that he knows exactly what he's talking about because he's a MOD. ;)

So don't beat yourself up dev, because this isn't your fault, it's just those pesky (non-OP reading) users fault.
[Epic 4G Android Development] ecooce:
LOL,if that were only true...
[Epic 4G Android Development] epic4GEE:
Well Thomas I felt it was too much to risk, I went ahead and flashed genocide. As I read thru all the recent posts again it seems like most people that bricked were indicating odd things, like poor performance and such. Things that sound a lot like a bad flash...idk just a thought.
[Epic 4G Android Development] Custodian:
Good deal. I on the other am riding this **** till my phone don't boot lmao....
[Epic 4G Android Development] dyehya:
Yeah he forgot to change the Build string but not a big deal :)
[Epic 4G Android Development] dyehya:
Potential Fixed Build

I have a theory on the cause of the issue and have a modified Vision 1.2 Kernel I build and am using personally. If someone has ran Vision 1.2 and experienced problems with booting but was able to recover the phone successfully, I NEED YOUR HELP! I need someone that has had the issue and came back from the brink to test out my modified kernel.

I believe the clock frequency that is cooked in may be what is causing the boot issue. I won't go into details here but I believe for now, removing 1.45GHz resolves the issue. I also included a 1.36GHz step because 1.4GHz wasn't 100% stable on my phone but 1.36GHz doesn't freeze. I also increased the voltage at 1.3GHz and 1.36GHz to 1.4V to improve stability.

If you had boot issues and successfully got it restored or working please PM me or contact me on FOSSnet nickname "Cyc" so I can give you the updated Kernel. I would really like to test this ASAP to know if it resolves the issue or if we need to look elsewhere.
[Epic 4G Android Development] philowneus:
I had corruption on 1.4. had to odin cause I didn't do a backup and flashing over top did nothing to help. running with only voltage control and its great. I prefer my battery life any way.

EDIT: so i read more about the issues. They said dont shutdown or restart. well of course i did shutdown from the menu. sent me into a bootloop. but no brick.