Related
Weird issue...
Doesn't matter which rom, when I'm not on stock, my phone will freeze...
I have used odin and flashed one click root, clockwork mod then installed different kernels, roms and with same result. It will freeze eventually until I pull the battery... am I doing something wrong here?
I mean, I completely wiped using Odin so I don't see the residual thing here.
And in case there are, I wiped data, cache, dalvic prior to flash or followed chefs instructions to the T.
Am I the only one that's experiencing this? (probably am T_T)
Any inputs would be appreciated.
Same here. I've found that its the custon kernels that cause it. I just flash the rom I want and then flash the stock kernel back.
Sent from my Epic 4G using the power of the Holy Spirit
Hey, thanks for writing to confirm. good to hear that I'm not the only one but sucks to be one of the few...
I have done multiple wipes, cache clearing (both cache and dalvik)
Gone fresh from di18 fresh install, rooted and unrooted (I heard that old 1 click conflicts with genius dog's kernel) I have come to conclusion that it's the under voltaging that's the culprit here... I may be wrong but what kinda grinds my gears is that why is that only you and me are having these issues?
I'm using Andromeda kernel and it seems to be stable for me.
Any ways around this ??
I just recently started having this problem. I never had it until the day I flashed bakedsnack 1.3. The ROM is wonderful besides the occasional freezing. I usually freeze up about 2 times a day and have to pull the battery. This ROM does use a custom kernel though and I was OC'd to 1.3ghz but reflashed and went to 1ghz and still freezing.
Have you tried OC kernel before? i.e. genius dog's kernel. (not dogging Genius dog or anything. I'm naming his because his kernel is most widely used and I'm dying to use it.)
Just want to try to eliminate the culprit here lol.
Also try flashing andromeda kernel and see if your problems persists because I'm having no problems however my mflops will never go over 8.5 T_T
Hey guys,
I know everyone is going to first think, What the hell, this is too easy what a noob.
Anyway, point is, ive been looking for a tutorial on this for ages and just can´t find one.
On all Android Roms they always just write things like "Also make sure to intall the kernel" and thats it or when you look through generall ROM tutorials for android you just see "Don´t forget to install the coresponding kernel"
Nothing on how to do it.
So I have the following questions please:
1. I want to install this ROM on my HTC HD2
http://forum.xda-developers.com/showthread.php?t=1316632
Click to expand...
Click to collapse
How do I install the kernel for it?
2. It tells me to partition the SD card, I really don´t get what they mean with all of those numbers?
Please send me to a tutorial where it is explained or explain it, it would really be a great great help. Thank you!
Well.
First thing - it depends on whether you want to flash the Magldr or cLK version.
I highly recommend cLK, with it you can use ClockworkMod Recovery, which will allow you to easily install pretty much everything that's in correct zip format.
So if you flash the cLK version, afterwards you just download the kernel (that's in the thread you provided) in the .zip format and save it on your sdcard. Then go into Clockworkmod Recovery (if you don't know what it is, search the net, and study) and flash zip from sdcard. That's it for the kernel.
If you want to use Magldr, I can't help with that, I'm using cLK.
About SD partitioning - there is a good guide here https://docs.google.com/document/d/1dhXJZPjZzBHcAtIE_jfEeuG988UDUaP7GfZk909nNCc/edit?hl=en&authkey=CLDJw80N&pli=1
It's a guide made especially for AmeriCan Android ROM, but the partitioning part is well written and it should work for all ROMs like that.
Just check it out, if you need anything more, let me know.
Thanks man.
This is great.
Did it with cLK and it was really easy.
Thanks!
Edit.
I need some help on this ROM. I tried to post this question in the ROM thread but it wont let me so im hoping someone can help me here.
My phone won´t boot anymore. It just gets stuck at the HTC logo with this ROM installed.
What I did was:
1. Wiped data and cleared cache
2. Installed kernel via CWM (from SD)
3. Installed ROM via CWM (from SD)
4. After succesful install (with out errors at least) i press reboot now.
And from then on its just suck at the HTC logo.
Ive left it for over an hour now just to be sure but nothing.
Can someone tell me what is wrong with it?
Thanks!
Cheesus182 said:
Thanks man.
This is great.
Did it with cLK and it was really easy.
Thanks!
Click to expand...
Click to collapse
No problem mate, if anything more, just ask - here or PM.
Edit:
P.S. if you wanna confirm that you have the new kernel installed, just go to settings, about phone and there you see the kernel info.
I'm going to jump this existing thread as I also have a beginners question on the same subject...
I already installed a ROM (NexusHD2) and having huge battery drain problems (drains from 100% to dead in aprox. 15 hours on 100% standby with no applications running), but having less than 10 posts on this forum, I can't ask in the thread for the particular ROM. But I see a lot running this ROM with a tytung_r14 kernel, so I figured that I probably had to install this as well and I'm going to try it, but one question though...
Was I supposed to install the kernel BEFORE installing the ROM? Or can I just go and install the kernel now and all will be dandy?
Thanks.
Just flash Rom again in Recovery mod then flash kernel later on. It's gonna be fine, I believe.
Sent from my Desire HD using xda premium
Why should I do a recovery flash of my ROM and then flash kernel afterwards instead of just flashing the kernel right now if that is possible?
The ROM was flashed friday afternoon, so it's a pretty clean ROM.
You can flash kernel at anytime, you don't have to reflash anything.
Also, it might not be the kernel, which is responsible for your battery life.
Search for thread called something like ultimate battery guide for android and there are all things you can do to check what's wrong and make your battery life great. I did that, and am very satisfied.
DaneX said:
I'm going to jump this existing thread as I also have a beginners question on the same subject...
I already installed a ROM (NexusHD2) and having huge battery drain problems (drains from 100% to dead in aprox. 15 hours on 100% standby with no applications running), but having less than 10 posts on this forum, I can't ask in the thread for the particular ROM. But I see a lot running this ROM with a tytung_r14 kernel, so I figured that I probably had to install this as well and I'm going to try it, but one question though...
Was I supposed to install the kernel BEFORE installing the ROM? Or can I just go and install the kernel now and all will be dandy?
Thanks.
Click to expand...
Click to collapse
I'm currently running the existing ROM on my SD card, and I'm not experiencing any battery drain what so ever...
I've also installed the ROM in NAND previously and didn't experience any heavy battery drain as well.
But to answer your question, no you weren't suppose to install the kernel before installing the ROM; The ROM (in SD or NAND format) already comes with a compiled kernel (It's a file called zImage).
You can install the kernel and you should just be dandy. Just remember that your battery life is heavily influenced by your cell reception and by the synching that occurs in the background.
To give you a reference, my phone is at 89% has been on standby for 13.5 hours with WIFI ON and data ON, but with data synching turned OFF for facebook and gmail. I'm also currently running it through the SD card with kernel r13. You should get similar results with the newer or existing kernel.
g.s said:
To give you a reference, my phone is at 89% has been on standby for 13.5 hours with WIFI ON and data ON, but with data synching turned OFF for facebook and gmail. I'm also currently running it through the SD card with kernel r13. You should get similar results with the newer or existing kernel.
Click to expand...
Click to collapse
Is this with the NexusHD2 ROM?
When my phone is "sleeping" with screen/WiFi/Sync/Bluetooth OFF my phone is using 55-60 mA.
With the screen on and lowest standard brightness setting it is at 115-125 mA
DaneX said:
When my phone is "sleeping" with screen/WiFi/Sync/Bluetooth OFF my phone is using 55-60 mA.
Click to expand...
Click to collapse
That means that you have a lurking app that keeps your phome from going into standby,so called partial wake.
Go into you app Spare Parts, click on battery history, choose other usage, since last boot or unplugged.
The screen on and running percentages tell you about the wake lock.
If it is nearly the same, that means you have almost no partial wakes.
If running is much higher, than screen on, that means you have some app that keeps phone awake.
Now choose partial wake usage in Spare Parts and it'll show you the apps.
And now you either uninstall them or change settings.
I'm on AmeriCan Android rom, getting 1-4mAh consumption in standby.
DaneX said:
Is this with the NexusHD2 ROM?
When my phone is "sleeping" with screen/WiFi/Sync/Bluetooth OFF my phone is using 55-60 mA.
With the screen on and lowest standard brightness setting it is at 115-125 mA
Click to expand...
Click to collapse
Yep, this is with the NexusHD2 ROM. My phone during standby, only draws about 2-4mA.
55-60mA during sleep/standby is not normal. Are you in an area with bad cell reception?
I think I found out the cause of some bootloopings and its the "Log Switch" option in project menu.
When we try to root the rom and the the phone reboots:
A)if he reboots ok, you must go again into project menu (*#*#2846579#*#*) and "switch off" the Log.
Everyone tell us we must switch this thing on in order to root the phone but no one says that we should turn it off again after proccess completed....
B) if starts immediatly with bootlooping and never booted againd after the rooting proccess just take the battery out andenter into recovery (vol up + Power). Once there make a "Data factory reset" and reboot.
The phone will then start normally this time with no Bootloopings.
With luck you have SU installed and the phone is rooted.
If yes, just go to project menu (*#*#2846579#*#*) and "switch off" the Log.
If not just try the rooting again
But the major deal is the Log Switch.
Hope it helps anyone
I never had bootloops with 2.3 official rooted and log switch was turned on before and after
I'm happy for you!
Moved to General
Thought this may be helpful to some, it has no place in the development section.
Thanks for the contribution, i would usually close, but as it could be helpful, on this occasion i will move it.
Take it easy
O_G
yes don't close it please as I noticed that many had bootloop issues with these releases. I was one of them but this finished after switching the log of. In my caes that solved my problems.
I had thought that too but none of the combinations i tried worked.
I had tried switching off Logging,factory data reset,flashed again without rooting and after 2-3 days that everything seemed that worked normal and i had loaded all apps i wanted, bootloop appeared again and had to factory data reset again in order to use phone.
So i gave up and reverted to 2.2
I never had bootloops but if that's really what's causing it, that's a great catch!
Congrats!
well as I said with me, since I have done this the bootlooping stoped.
Before Everytime I reboot the bootlooping started and only stoped with a factory reset. Then I tried to switch Log Off again and not a single bootloop and more than 48 hours.
Flashed OC kernel, UOT Kitchen, etc etc and phone running perfect.
Look, I have flashed and tested this rom many many many times and alwas endup with bootlooping eventually. This did the trick for me and I consider it a major step as I can now use the rom freely and without being afraid.
As I said, is just 1 more Idea that people having this issue could try out and see if helps.
I just took the liberty of sharing this so that in case o dispair for some, they can have other alternatives.
Didn't help me, actually it did the opposite...my phone didn't boot loop until I went and touched the freaking "Log switch" option...should have let it ON...GRRRR....Got to taste Huawei's bad medicine again...or my own...I should have known; if it ain't broken, don't try to fix it!
lololol
Huawei's each one with own personality...
Druida69 said:
lololol
Huawei's each one with own personality...
Click to expand...
Click to collapse
Indeed!
Mine, for example, had precisely the opposite behaviour.
In order to root the phone, with the latest official GB ROM, i had to switch the logging to On. Otherwise i got bootloop with every ROM. I was also unable to root the official roms without logging On.
Well, at least it was coherent.
Question: When we flash a new ROM the logging is turned off by default, right?
If so, how can it influence negatively the ROM stability?
Druida69 said:
lololol
Huawei's each one with own personality...
Click to expand...
Click to collapse
Tell me about it.
SilveRRing said:
Indeed!
Mine, for example, had precisely the opposite behaviour.
In order to root the phone, with the latest official GB ROM, i had to switch the logging to On. Otherwise i got bootloop with every ROM. I was also unable to root the official roms without logging On.
Well, at least it was coherent.
Question: When we flash a new ROM the logging is turned off by default, right?
If so, how can it influence negatively the ROM stability?
Click to expand...
Click to collapse
You understand it opposite m8.
You must turn the Lon On to root the phone.
After root my advice is to turn it back Off again as it was from the beginning..
Ah ok, nevermind then. lol
my x5 dont have bootloop but this topic will help very people,thanks for the trick lol
---------- Post added at 09:14 PM ---------- Previous post was at 09:12 PM ----------
driuda you have a theme of UOT Kitchen??? I make one for me but failed,please help me?i dislike stock theme is for children hehehe
at the moment I only used UOT this time to change the battery icon to battery percentage circular.
Its one of those must haves that I miss from official rom, the battery percentage....
Coking a theme is very easy. You just choose all the option you want and in the end upload the framework-res.apk and SystemUI.apk files and wait for the coking.
After that pick up the file and flash it with CWM.
mhh i dont think that the log switch is the only thing that causes bootloops.
first i installed 2.3.5 and a few hours later i switched the og on. The bootloops started.
So i had to do a factory reset...
Now after the reset I quikly turned off the log switch. but just a few hours later it started again bootlooping......
any other ideas? or do i have to go back to miui? when yes can i do the following?
: 1. factory reset
2. get root
3. install cwm
4. install my backup?
let me see if I understand.
You installed the latest official release, then you switch the log on? for what?
I assume you switch it on to root. Did you root it?
Yes yes you did well by turn it off as the log is off by default.
Next step should be installing the CWM 5.0.2.7.
Unfortunatly after bootlooping start only solution is factory reset which means having the phone all wiped again which is a pain after a few hours of putting it at our taste.
I think restoring a MIUI backup through CWM won't work.
I have tried this preocedure several times with MIUI or any other custom rom.
The correct way to go gack is downgrading to an official 2.2 release, then root it, install CWM, install a MIUI rom (in your case) doing all the 3 wipes. After you confirm that the rom was installed correctly and is working you can then go to CWM and restore a backup.
Druida69 said:
let me see if I understand.
You installed the latest official release, then you switch the log on? for what?
I assume you switch it on to root. Did you root it?
Yes yes you did well by turn it off as the log is off by default.
Next step should be installing the CWM 5.0.2.7.
Unfortunatly after bootlooping start only solution is factory reset which means having the phone all wiped again which is a pain after a few hours of putting it at our taste.
I think restoring a MIUI backup through CWM won't work.
I have tried this preocedure several times with MIUI or any other custom rom.
The correct way to go gack is downgrading to an official 2.2 release, then root it, install CWM, install a MIUI rom (in your case) doing all the 3 wipes. After you confirm that the rom was installed correctly and is working you can then go to CWM and restore a backup.
Click to expand...
Click to collapse
yes i did turn it on becuase i wawnted to prepare it for rooting but since im not at home since 3 days i cant.
But after the bootlooping i turned it off, but it bootlooped later again....
thank you for the intriductions!
edit: where can i find the 2.2 stock rom for germany? and how to install it? like 2.3.5?
levibuko said:
yes i did turn it on becuase i wawnted to prepare it for rooting but since im not at home since 3 days i cant.
But after the bootlooping i turned it off, but it bootlooped later again....
thank you for the intriductions!
edit: where can i find the 2.2 stock rom for germany? and how to install it? like 2.3.5?
Click to expand...
Click to collapse
if it is to downgrade and then move forward to any other rom, custom or not, you can use any version don't loock spexifically to a german one.
Here you have a list of stock rom:
http://forum.xda-developers.com/showthread.php?t=1167882
http://wiki.modaco.com/index.php/Huawei_Firmware_U8800 (MOdaco Wiki)
http://forum.xda-developers.com/wiki/index.php?title=Huawei_U8800_IDEOS_X5 (XDA Wiki)
Check progress in DEV section http://forum.xda-developers.com/showthread.php?t=1562595
( I have posted less than 10 posts, so I can't write in the dev section. )
Stupid question : is it using Holo?
And, if it is based on CM9, it is rooted, isn't it?
If WiFi works, I'm SURELY going to try this!
I installed it yesterday. Wifi works, it uses Holo, hat root and performs better than I expected.
Thx.
I' ve put it on. It's really laggy, but it works!
It's a good start, but if this is the best performance the legend can give, I think I won't ever change definitevly to ICS. Maybe it can be optimizated for the Legend hardware to become smoother.
Thanks for testing, but it has not got hardware acceleration yet. For testing purpose, you could overclock it up to 787 MHZ safely, and the overall performance get better notably.
/=\lex said:
Thx.
I' ve put it on. It's really laggy, but it works!
It's a good start, but if this is the best performance the legend can give, I think I won't ever change definitevly to ICS. Maybe it can be optimizated for the Legend hardware to become smoother.
Click to expand...
Click to collapse
Yea is pretty smooth overall eventhough hardware aceleration is not working, this port looks really promising,
Tried it yesterday and in My view its the smoothest ics ROM ever tested.i had some fcs but will try Tor correct rights via rommanager.if GPS is working i will use this one.its a must Have for me.
Sent from my Legend using XDA
Thanks for testing, but it has not got hardware acceleration yet. For testing purpose, you could overclock it up to 787 MHZ safely, and the overall performance get better notably.
Click to expand...
Click to collapse
I'll try keeping it on for more time. By my first impression, it doesn't look so buggy, I think it is also quite stable. I'll tell you if I find anything.
Anyway, this is a great ROM, thanks for your work!
EDIT : Stupid question : to install GApps I have to flash the zip, right?
EDIT 2x : Yea, it was a very stupid question. Flashed from clockwork recovery. Works perfectly.
Its getting better and better. but still GPS not working. Hope you get it fixed soon.
Realy great job!!!!!
really good job. Just need GPS and Camera.
Hoping for 2.5 soon...also hoping based on Android 4.0.4.
How is work going?
Sent from my Legend using XDA
I have a problem with the latest 3.0 version.
After i flash gapps i keep getting boot loops.
If i dont flash it and just flash the rom it boots fine.
Dont know what the problem is. Can someone help me?
I have the exact same problem as DareFace, but I think zeubea is aware of the problem.
zeubea-cm-9.0.0-ALPHA3.0.1 and Google Apps
I tried install this ROM multiple times today, everything works until i install gapps (full or tiny). After that phone enters infinite boot-loop (HTC logo on white background).
Radio 7.13.35.05
Bootloader HBOOT-1.01 (S-ON)
ClockworkMod Recovery 5.0.2.0
Edited @ 08:31PM GMT+2
After installing gapps over gapps works as a charm. That's weird...
I had the same bootloop problem until I installed another kernel that Zeubea provided. It's till get some fc's, mainly for clock and email, but the email still works, clock is inaccessible atm.
It's even better than cm 7.2RC1, running oc'ed at 787mhz ! It's so smooth and beautiful. Let's hope that the gps and camera will get fixed soon. If I had capabilities to donate, I so would do it.
Thanks Zeubea! The Legend community loves you, keep up the wonderful work of making our ICS dreams come true when htc can't and won't deliver.
The reason for bootlooping is the clock issue.
The default clock in 3.0.0 is 806MHz - something every Legend doesn't handle, so it bootloops.
The 3.0.1 version has this "problem" fixed.
I faced another issue releted to sounds. I change both ring and notification sounds and after some time i realise that they are reverted to default!
I have this weird thing where the danish keyboard force-closes.
It's everytime i type the word "lige". It doesn't do it with the english keyboard
I've tried to turn off the spelling correction, since it's in english, and there isn't a danish one, but it doesn't help.
Other than that it's great
bootlooping after flashing cm9 gapps, possible fix
boots up normally after flashing the zip in CWM, but after flashing gapps it bootloops, and after awhile of countless flashing i discovered it bootloops even before flashing gapps, so i tried different step to flash it and finally it boots up normally, here's what i did :
1) full wipe, dalvik cache and cache partition, factory reset
2) flash the main cm9 zip
3) full wipe, dalvik cache and cache partition, factory reset (again)
4) flash gapps (not tiny version)
5) reboot, if it boots up normally thats great, if not its ok, continue to step 6
6) boot into CWM
7) dont wipe or anything*
8) flash the main cm9 zip
9) instead of rebooting device, continue by just flashing gapps (not tiny version)
this were the steps i did to fix the bootloops after flashing gapps, apparently the gapps tiny version is not compatible with cm9 on the htc legend thats why i stick to the normal gapps file, i hope this helps anyone of u experiencing the bootloops after flashing gapps
I have some kind of problem with wifi connection. If "Keep Wi-Fi on during sleep" is set to "Only when plugged in". After I wake up phone wifi is turned on it cannot find any networks.
EDIT: Logcat trimmed to "network|wifi|power|conectivity" http://pastebin.com/pdUAbfDy
And terminal emulator displays an error "Unfortunately, Terminal Emulator has stopped" when I try to open it.
EDIT: Logcat http://pastebin.com/ChRUu3jS
Hello,
extremely sorry i am a noob and i cannot actually post in the development section so i thought i would let every 1 know about a few bugs i've com accross in the rempuzzle 2.43 rom:
1. when transfering files from bluetooth the Rom keeps Re-Booting for no reason at all it just Re-boots while transfering of files
2. and also the few links which have been replaced with the torrents are not working i tried digital battery, wil etc results came of not even a single Kbps tranfer due to not a single seeder on the torrent, if not i would like to recommend a few sites;
speedyshare . com
Fileden . com
here u can upload the links they will expire but it takes atleast 6 months for a link to actually expire on speedyshare according to my own experience of uploading
hope i dont piss any one here, i love this forum.
thank you
Hi. I cant help really other than to suggest a clean reflash,I.e. wipe system,data,cache and dalvik cache then reflash.
1. I don't and have never used Bluetooth transferring,sorry.
2. Kylon has a file sharing host and the torrent is a back up for when his limit is reached on the hosting,it will be reset soon I think so then all the links will be available.
MANCHESTER together UNITED forever
Thank you very much, and actually i have done what u are talking about complete flash even tried completely rooting the phone from scratch by installing ruu exe files etc. but the problem stil remains.
any ways found an alternative for that in an app named box.
still thanks alot for your reply
hey sory to again bother but i have installed the rom with cwm latest one but still there is a charging problem the charge gets extremely slow after 60% after 3 hours of charge on 1% charge was gained i.e. it went to 61% dont know what to do can u help ??
.
hanx1990 said:
hey sory to again bother but i have installed the rom with cwm latest one but still there is a charging problem the charge gets extremely slow after 60% after 3 hours of charge on 1% charge was gained i.e. it went to 61% dont know what to do can u help ??
Click to expand...
Click to collapse
If it's a problem unique to you and other users haven't reported it too (check the RemPuzzle thread), then it could be a bad flash. Try reflashing it (check md5sum before flashing). It the problem still exists, then we'll have to look at other possibilities. Also, did you transfer app data back to this ROM using Titanium Backup/My Backup Pro after flashing? And did you wipe dalvik cache after the flash?
Sent from my Desire HD using xda premium
well i did not clear the delvic cache after the flash but i did clear it before flashing i even tried completely re rooting the cellphone by installing ruu then rooting in through unrevoked with custom recovery i.e. cwm 5x and then going onwards to flashing and all... but still the problem persists well m trying some other rom just to check if the charging fixes or it remains the same in other roms as well if it does then it means it will the fault of my cell phone not the rom so i'll get back to you soon enough
and thanx alot