Database Users

Mdeejay FroYo Sense Matted v. 1.4 - HD2 FONE AUTO RESTARTING ISSUES

I installed Mdeejay FroYo Sense Matted v. 1.4 the other day on my HD2 and it worked well
However 4 - 5 hours later I noticed my fone automatically restarted, why is that? My battery was at 80% so I thought nothing of it until 4 - 5 hours later when it happened again
Any ideas whats going on? and more importantly how I resolve it?
Thanks
P.S. I have posted twice in the development forum but have received no help

this usually happens when you are overclocked/undervolted and the phone cant handle it. First try disabling overclock and if the issue persists change to a non undervolted kernel.
btw you shouldnt be posting problems in the development section, just a heads up

First try disabling overclock and if the issue persists change to a non undervolted kernel
Click to expand...
Click to collapse
As far as I am aware I have never enabled overclock, where in the phone do I check to ascertain whether its enabled or disabled?
btw you shouldnt be posting problems in the development section, just a heads up
Click to expand...
Click to collapse
I never would have done so, but have waited 3 days, posted twice in the ROM section and failed to received any replies - thanks for your response and time

you can check weather your overclocked or not with setcpu here: http://forum.xda-developers.com/showthread.php?t=505419 and youre probably undervolted because your using the mdeejay kernel included in his roms (correct me if im wrong). Try a kernel from the autobuild here: http://oe.netripper.com/files/htcleo_autobuild_evo_tree/ they are not undervolted or overclocked.

JJbdoggg said:
you can check weather your overclocked or not with setcpu here: http://forum.xda-developers.com/showthread.php?t=505419 and youre probably undervolted because your using the mdeejay kernel included in his roms (correct me if im wrong). Try a kernel from the autobuild here: http://oe.netripper.com/files/htcleo_autobuild_evo_tree/ they are not undervolted or overclocked.
Click to expand...
Click to collapse
I'm also having this issue with Mccm v3.4 evo build Hastarin 8.5 kernel. Currently every feature is working, camera, camcorder,mms, stable data and more. If I switch kernels to the latest Nov 26 th kernel will I lose any features?
Sent from my HTC HD2 using XDA App

sorry for delay and thanks for your response,
which kernal do you recommend? is their a guide floating around on "how to update your kernal"
please help
thanks

FreeKernel Feedback (Bootloader bypass) UPDATE:VIDEO

Please post all feedback/comments to do with the FreeKernel here
DO NOT SPAM THE BOOTLOADER CRACKING THREAD, IT IS FOR DEVELOPERS ONLY.
zdzihu said:
The bootloader has been bypassed using the kexec/miniloader method
We are able to boot custom kernels now!
Anyway... this is the first release of the fully working custom kernel (flashable via xRecovery). I haven't had much time to work on it so it's kind of proof-of-concept. Tested for 48h without any problem (not even a reboot).
FreeKernel-alpha1:
http://www.mediafire.com/?d8v914keiqsmc3n
This is the alpha version of custom 2.6.29 kernel based on the SE sources. I do not plan to work on this release anymore - it is just for testing purpose. From today on I'll start to port SE stuff to the latest (GBread) kernel.
Changes:
- removed 32 fps cap
- implemented netfilter (Droid wall, native USB/wifi tethering etc.)
- undervolted to 0.950mV to save battery
- don't remember what else I did, I bet something nasty
- super ugly boot logo!
Requirements:
- baseband .52 + the relevant kernel
- clean 2.1 ROM, compatibile with .52 baseband (e.g. .504)
- working xRecovery
Please note I am not responsible for any damage this software may cause to your device! Use it at your own risk!
There is absolutely no support for this alpha release!​
Click to expand...
Click to collapse
So, if you want to test this new kernel, please keep in mind it is only compatible with stock 2.1 firmwares (.504 and above) that are compatible with baseband 52.
It is only for testing purposes, and any feedback for this alpha kernel is purely for the benefit of others, Z is not and will not be supporting this version, do not expect it to be ready for daily use!
Please post your results and how you get on with the kernel.
Video of FreeKernel
http://vimeo.com/21838810
does anyone know how to embed it?
I tested the kernel on baseband .46 on TripNMIUI 0.3.2, and the removal of the FPS cap is incredible, the phone is so much smoother and fluid it is unbelievable - it is like having a new phone. I noticed the screen feels a lot more responsive aswell!.
Obviously it is not at all compatible with the ROM, there is no radio and there are frequent reboots, but just a taster in terms of things to come
Apologies for the poor video, but I think its enough to get the general gist of the smoothness

Tried custom kernel just for kicks on trips miui 3.2...bb 54 and up super unstable no network/wifi tons of reboots....
bb 52 and bb49 no network but wifi IS working no sd card mount though
gonna test other roms aswell....

For install custom kernel to be need xrec by Z not from flashtool.
All works, clean install bb 2.0.46 and 2.0.A.0.504.
Dont problems.
I done back to my custom rom way xrec and flashed the patch bb.49, nothing problem.
cheers

this will not work on bb .46 i have tried and failed. no network at all. have tried on several roms... only eternity roms are working on this kernel on bb .52....
supposedly it is suppose to work with bb .49 have not tested on this bb so i cant say for sure.
guaranteed on .52 build 504...
results on quadrant show fps cap has been removed.
overclock is not possible but undervolting is
colors have not yet changed but should upon release of other custom kernels

Can I brick my x10 with this or only bootloop it (because bootloop is fixable with SEUS)

will this work with freex10 and can anyone give me a link to the main thread where zdhihu posted this? i can't find it. thanks.

PlayGunsta said:
Can I brick my x10 with this or only bootloop it (because bootloop is fixable with SEUS)
Click to expand...
Click to collapse
You can't brick it as you only flash some files to the system, and you should still be able to access xrecovery if it bootloops

THIS IS ONLY USABLE WITH STOCK 2.1 ON. 52 BASEBAND!!!
This is a test kernel not meant as anything more than a proof of concept. There is absolutely no reason to flash this unless you are personally working on making your own custom kernels. This kernel is not even an alpha release, it will never be developed or supported. If you choose to flash it just to toy around don't whine about functionality.
When custom kernels are available anything the hardware is capable of and drivers can be written for will be possible. Everyone needs to calm down and quit asking the same questions over and over.
Sent from my X10i using XDA Premium App

Have uploaded a video, does anyone know how to embed it in the post?

Thanks for the video!

a2ha said:
Thanks for the video!
Click to expand...
Click to collapse
no problem

BTW. will it work on Freex10?

a2ha said:
BTW. will it work on Freex10?
Click to expand...
Click to collapse
No. Z posted it in the bootloader cracking thread. This is only meant for stock 2.1 FW on. 49-.52 BB and is not functional for daily use. This is only meant as a test if you want a stable new kernel its still going to take a little while.
Sent from my X10i using XDA Premium App

a2ha said:
BTW. will it work on Freex10?
Click to expand...
Click to collapse
It won't work with any ROM 100% - its just designed for testing, you won't be able to use it for daily use yet.
If you just want to try it out, its possible it will boot up on freex10 and you will see the effects of not having a FPS cap - but it is unlikely the majority of things will work, like radio etc. as it is meant for stock 2.1 roms.
If you do want to try it, make a backup on xrecovery first

I dont know what you have xD
What do you mean with "its not ready for dayly use" ?
I use it now since yesterday afternoon and everything works perfect!
I had no random reboots and everything is very smooth!
My Battery lost 1 % with stable 1 Ghz (playing around and testing).
So not be scared! flash it!

Whitecookie said:
What do you mean with "its not ready for dayly use" ?
I use it now since yesterday afternoon and everything works perfect!
I had no random reboots and everything is very smooth!
My Battery lost 1 % with stable 1 Ghz (playing around and testing).
So not be scared! flash it!
Click to expand...
Click to collapse
As in its only supported by the stock 2.1 ROM, and if you run into any problems with it, its not being supported so you won't get a fix

so for example if i install this kernel on my freex10, how can i remove it later if i have problems with it?

a2ha said:
so for example if i install this kernel on my freex10, how can i remove it later if i have problems with it?
Click to expand...
Click to collapse
Create a backup on xrecovery before installing it, and then when you need to go back just restore it

Hey . Is this really working cos owain in ours minipro forums said its only first april joke, and we cant yet load custom kernel. Is there any difference between x10 bootloader and minis ??? How long it will take to do a fully working roms , softs to ours xperias ???
Sent from my X10minipro using XDA App

@ Whitecookie:
Do you use the .504 2.1 ROM?
Does someone if it works with 2.0.2 (the ROM which Eminence V1.2 is based on) works 100% with this kernel?

[POLL] SOD (sleep of death) issues/cases on ICS - Is it happening to you?

For ICS users only
I was just curious, since many users (including me), never got SOD on the phone, not even once..
And being a heavy user, I tried many GB and ICS builds (But I use Criskelo's stuff most of the time...)and so far no SOD..
Just give your vote, for the statistics (or curiosity? )
Thanks
.

When using the Rocket Rom, 1.5, I only ever got one and that was when sync was on and wifi was doing it's little glitch-out thing. Other than that, have never had one on 1.5.

It happened often when i flashed via Mobile ODIN. Re-flashing via full PC ODIN and then installing iMilka's AOSP has given me no problems.
I don't have any hard evidence that mobile odin is to blame, but flashing with full PC odin make a big difference for a friend and I.

Lots of SODs when running Chinese Repack, just a couple since switching to imilka's AOSP.
Repack flashed via Mobile Odin.

chasmodo said:
Lots of SODs when running Chinese Repack, just a couple since switching to imilka's AOSP.
Click to expand...
Click to collapse
Didnt try imilka's , started up (and staying) with Criskelo's and then tried a couple of other builds just to compare ...
Never got SOD on any of the other builds including ,when running CF repack with gapps 7.1
And always flashing with Mobile Odin with the necessary full wipes
.

I have not had a single SOD. Was on ROMOW ICS until imilka AOSP, have used imilka V1-V4 and been on V4 since release day with 0 SOD's. Mobile Odin CF Repack to imilka.

Have had several on Midnote.....matter of fact just had one 2 minutes ago...lol Otherwise this rom is perfect!

I just had one on the latest stock build of GB from India. I haven't rooted my phone or anything. Interesting. I will keep my eye on this thread. Thanks!

Feel free to mock me .... but what do you mean when you say SOD (screen of death)? Total system crash?

For some reason I get about 3 a day. I'm pretty sure its app installed. Once I raised the minimum CPU to 500 it got a lot better. When I get a chance I'll reinstall everything.
All in all I'm pretty sure its user error and not the rom. I'm using asop rom v4.
Sent from my GT-N7000 using xda premium

Yep same question here. (what do you mean by SOD?)
Many times I have the black screen when launching some app that sometimes work and sometimes don't (when I reboot the app is not accessible anymore).
I have an issue, it seems access to the external SD is not functioning well. Since I moved to ICS, I can't tell if it's Rom related or if its the SD that's faulty (it seems all OK when plugged to the computer).
I might have also to reboot when wifi toggled back on is not working well.
I'm using criskeloRom +15 toggles (but had more or less the same behavior with all the rom I used, Midnote or RocketRom).

Never on Criskelo's 1.5 ROM....in fact it is now 3 days without a reboot...I have had a couple of crashes without need for reboot, but its when Touchdown updates the stock contact list, which even happened on gingerbread...

Are you guys sure this is ROM related and not some other software?
I had SOD on GB

been using Team Rocket 1.5 since the first release, I totally had 4 times of SOD, not that much really.

i been using midnote repacked by me for atleast 6 days now NO SOD.
i give u guys a secret.
download midnote.dont download gapps from that thread.
download gapps from hptouchpad cm9 thread.its called gapps v11
youtube is tablet version.

@betoNL
Actually, it's not screen of death. It's sleep of death.

Using Chinese repacked ICS, flashed using Mobile Odin, got 4 SOD, once per day, going back to GB.

chasmodo said:
@betoNL
Actually, it's not screen of death. It's sleep of death.
Click to expand...
Click to collapse
Yep...just the other day I corrected somebody that wrote screen of death instead of sleep...
And I now I made the same mistake
Thanks for the observation though...
Just corrected it.
.

I am on criskelo v1 b3 with kernel Angelom, modem lb1, setcpu, but i have SOD yet
I love ICS and Chrome and i don't want return to GB

intruda119 said:
For some reason I get about 3 a day. I'm pretty sure its app installed. Once I raised the minimum CPU to 500 it got a lot better. When I get a chance I'll reinstall everything.
All in all I'm pretty sure its user error and not the rom. I'm using asop rom v4.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Yes, let's continue blaming the user despite how some have gotten SOD on a fresh flash on a stock Chinese ROM with no apps installed.

Neutrino Rom cannot wake up after a long period of idle

I am currently at Neutrino rom V2.5p2 GT
my phone have some problem that it cannot wake up after a long period of idle, such as EVERYDAY I wake up in the morning but I cannot wake my phone up. I have to pull my battery off and back in to reboot the device. This problem made me fail to receive morning calls for a whole week.
I am using Juicedefender, but not sure if it is the cause of problem.
Since this is the first custom rom I flash and I love Neutrino, but I think stability is a must to me. Are the V2.5p2 EE or V2.2 having a better stability? should I try them? or any patch can fix this problem?
Thank you so much!

same as u with 2.5p2 ee
wait for the next build

Sleep of death as its known, not always rom specific many of us experience it on different roms under different loads under different situations.
There's a few of us trying to track down the underlying problem, but at the moment we are all trying out different things which some work for people and not others
so agreed with the above just wait for the next build maybe that will work for you.

Harrison85 said:
Sleep of death as its known, not always rom specific many of us experience it on different roms under different loads under different situations.
There's a few of us trying to track down the underlying problem, but at the moment we are all trying out different things which some work for people and not others
so agreed with the above just wait for the next build maybe that will work for you.
Click to expand...
Click to collapse
Like i've said in the Neutrino thread - it's a CM7 bug that was present in the original weekly.
Flash the 023 kernel, wipe dalvik, reboot.
023 seems to have fixed the problem for me. Going through a second day without random reboots, sleep of death.
Link to the kernel can be found in the faux dev thread, but it's also in my sig.

I think my phone must be hate custom ROMs because it have SOD for Jokersax and Turl CM9 as well as Neutrino ROM. Did flash some faux kernel but solve nothing. Still running Jokersax CM9 although SOD simply because of ICS. My own opinion, don't try CM9 unless you are ready to stay with it until official release.
Sent from my MB860 using XDA

ko_wei13 said:
I think my phone must be hate custom ROMs because it have SOD for Jokersax and Turl CM9 as well as Neutrino ROM. Did flash some faux kernel but solve nothing. Still running Jokersax CM9 although SOD simply because of ICS. My own opinion, don't try CM9 unless you are ready to stay with it until official release.
Sent from my MB860 using XDA
Click to expand...
Click to collapse
What's your WIFI sleep policy set to?
And just to be 100% sure - do you wipe properly during rom flashing?

xploited said:
What's your WIFI sleep policy set to?
And just to be 100% sure - do you wipe properly during rom flashing?
Click to expand...
Click to collapse
I didn't enable wifi. Just using data plan. The setting for 'Keep Wi-Fi on during sleep' is Always as default.
I'm using N_01.100.00R baseband, could it be the issue? Any baseband recommend to use in Asia?
I follow what Jokersax said, format /system, wipe user data, wipe cache and dalvik cache in CWM. I manage to flash every single ROM and boot normally. Weird.
Sent from my MB860 using XDA

xploited said:
Like i've said in the Neutrino thread - it's a CM7 bug that was present in the original weekly.
Flash the 023 kernel, wipe dalvik, reboot.
023 seems to have fixed the problem for me. Going through a second day without random reboots, sleep of death.
Link to the kernel can be found in the faux dev thread, but it's also in my sig.
Click to expand...
Click to collapse
I am going to flash the 023 for a try. I just flash it in cwm recovery and that will be ok?

OK I have just flashed the 023 kernal, let me test my device for a few days to see whether SOD still exist, thanks!

ko_wei13 said:
I didn't enable wifi. Just using data plan. The setting for 'Keep Wi-Fi on during sleep' is Always as default.
Click to expand...
Click to collapse
I am using the default ATT baseband N_01.77.30P.
But from my experience, the reboot / sleep of death issue is most definitely related to WiFi.
Try setting Wifi sleep to "off when the screen is off" and switching to 023 kernel.
Haven't had any issues with this set up in the last 2 days.

xploited said:
I am using the default ATT baseband N_01.77.30P.
But from my experience, the reboot / sleep of death issue is most definitely related to WiFi.
Try setting Wifi sleep to "off when the screen is off" and switching to 023 kernel.
Haven't had any issues with this set up in the last 2 days.
Click to expand...
Click to collapse
Read from other thread with the workaround solution by installing Load Monitor or Wake Lock to prevent phone to go into deep sleep and fail to wake up. Now my phone run at 216Mhz instead of deep sleep when screen off. So far no SOD experience yet. But don't know how my battery life ink this case. Will update again after more observation.
[edit] no luck for load monitor. Get a SOD after 2 hours. Trying wake lock now. So far 6 hours no SOD. Will keep update.
Sent from my MB860 using XDA
Jokersax CM9 v0.4.1

I flashed the 023 1.3GHz kernal and the SOD disappeared last night!
I think the 023 1.0GHz kernal also work
I will observe for a few more days and report it here

Neutrino V2.6 GT and GT+ comes with 023 Kernel. It might solve the SOD as well. Downloaded. Will try it now..
Sent from my MB860 using XDA

ko_wei13 said:
Neutrino V2.6 GT and GT+ comes with 023 Kernel. It might solve the SOD as well. Downloaded. Will try it now..
Sent from my MB860 using XDA
Click to expand...
Click to collapse
I think the problem is solved with the 023 kernal! 2 days after flashing with no problem even set the wifi to be always on.
I think V2.6 EE version is worth trying since it include the CM7 kernal and claimed to have amazing battery efficient! But the V2.6 version introduced Launcherpro and many changes so I am not going to change it at this point, maybe a few days later.

Can I just flash the V2.6 stock CM7 kernal on my V2.5p2?
where can I find that CM7 kernal???

stainlesteel said:
Can I just flash the V2.6 stock CM7 kernal on my V2.5p2?
where can I find that CM7 kernal???
Click to expand...
Click to collapse
Why would you want the 2.6 kernel on 2.5p2?
For me 023 fixed the SOD issues.
Anyway, if you want to try the 2.6 kernel, download the rom, extract boot.img from the archive and flash it via fastboot, wipe dalvik, reboot.
If i were you, I would switch to 2.6 entirely. Haven't had any SODs in the past 24 hours since flashing.

stainlesteel said:
I think the problem is solved with the 023 kernal! 2 days after flashing with no problem even set the wifi to be always on.
I think V2.6 EE version is worth trying since it include the CM7 kernal and claimed to have amazing battery efficient! But the V2.6 version introduced Launcherpro and many changes so I am not going to change it at this point, maybe a few days later.
Click to expand...
Click to collapse
Flashed V2.6 GT and no SOD so far, but Play Store keep FC. Now revert back to CM9 Jokersax v0.4.1 with wake lock to keep my CPU on when screen off. No SOD for 2 days, but battery only can stay around 10hrs.
Sent from my MB860 using XDA

Oh I found the kernal swaping thread and the problem is solved!

I got is every once in a while with neutrino 2.2

My neutrino 2.6 have a priblem in search and home buttons.

Siyah Kernel Update Problem! Read Before Flash It!!!

Resently I update my Kernel to Siyah Kernel v3.1rc6 . The ROM that i used it with was ICS Resurrection Remix 1.5 and I wanted to update to 1.7 .... Until 1.5 the update was fast and nice .... But since I update my kernel to the Siyah i coundn't update my ROM ! When it was ready to update it started to show a list of Galaxy's ex. gt-i9100G-P-I and so on and then stopped with the error status 7. I tried another ROM ,the same thing. I update the kernel to 3.1.2, nothing changed. So I formatted with original ROM through Odin and then tried the same ROM i tried from the first try and Bingo!!!!! The update proceeded with no problem! So the final concution is this: The Siyah Kernel might have a bug, and from the error that was listed in my device screen, considering the comparison of the phone type like "gt-i9001->gt-i9001t :No","gt-i9001->gt-i91001 :Yes, continue the update". I am not a developer and i don't want to play the guy that knows everything .... This crossed my mind consedering a similar post that a skillful guy twicked his "build.ini" and he fixed the problem. If anyone can give a strayed answer about this problem and what should I do (because maybe I did something wrong, I am an n00b after all) or someone talk to Siyah Dev. Team to inform them about that problem.....

another siyah f+=-up? This guy is losing his complete reputation within 2 weeks...

so i am not the only on with some kind of problem after flashing that kernel ? The other guy had the same problem as me or i need to add another problem to the reasons i will never use that kernel again ?

Nio9345 said:
so i am not the only on with some kind of problem after flashing that kernel ? The other guy had the same problem as me or i need to add another problem to the reasons i will never use that kernel again ?
Click to expand...
Click to collapse
Suggest then that you do not customize your phone as all customization comes with a risk however small .
Makes it even more likely when the Siyah kernel problem post next to this post is not read by the OP .
jje

JJEgan said:
Suggest then that you do not customize your phone as all customization comes with a risk however small .
Makes it even more likely when the Siyah kernel problem post next to this post is not read by the OP .
jje
Click to expand...
Click to collapse
i didn't quite catched that .... Can you explain it a bit,please ?
And please tell me : i did something wrong with the kernel or is a wide spread problem ?

Hi mate.
In the resurrection thread it was mentioned to flash stock cm kernel before updating rom. I'm Happy you worked out a solution for your problem by yourself and that you can enjoy your phone again.
There where some serious problems with 3.1rc6 afaik. I read in other threads that some bricked their phones by a factory reset wipe using this kernel version.
I understand how frustrating it is when your in such pitty situation but i also understand the devs point. Most of them are spending their whole free time to share their ideas/work with others. They cant hardcore test everything alone. Therefore ReleaseCandidate versions are published so some flash freaks can test it out and report back. To cut it down: dont expect a bugless RC version. If youre one of the flash-freaks then go for it, test it and report issues to the dev/their thread. They will for sure be gratefull for your help.
Regards

clonednull said:
Hi mate.
In the resurrection thread it was mentioned to flash stock cm kernel before updating rom. I'm Happy you worked out a solution for your problem by yourself and that you can enjoy your phone again.
There where some serious problems with 3.1rc6 afaik. I read in other threads that some bricked their phones by a factory reset wipe using this kernel version.
I understand how frustrating it is when your in such pitty situation but i also understand the devs point. Most of them are spending their whole free time to share their ideas/work with others. They cant hardcore test everything alone. Therefore ReleaseCandidate versions are published so some flash freaks can test it out and report back. To cut it down: dont expect a bugless RC version. If youre one of the flash-freaks then go for it, test it and report issues to the dev/their thread. They will for sure be gratefull for your help.
Regards
Click to expand...
Click to collapse
Let me make myself clear (I am not angry, as I said i am a 100% n00b) ... The reason i put this thread is for someone to tell me IF i did something wrong or IF the kernel has a bug wasn't fixed by now ... If the first apply then i want someone to tell me what i did wrong or if the second apply then someone who knows the Siyah Dev. team to inform them about this bug, because in their site i can't contact them to tell them about this problem ... I know that a developer's job is heavy and he CAN'T possibly think all the possibilitys or bugs and he can't have 1.000.000 devices to test it 100%. So sorry if I look like i blame them about something, that was never my intetion... The Siyah Kernel is awesome in every way and i want really to install it again with that problem fixed
and also thanks for mantion that step from ressurection thread .... i didn't see it
and also i mentioned that i updated my kernel to 3.1.2 and the problem persisted .....

Not really necessary to clutter the forum with this even more.
Here's a thread on the same topic http://forum.xda-developers.com/showthread.php?t=1615058
...or just post in the Siyah kernel itself.
Closed