Related
Hi,
I wanted to know if there is any way to run a different OS on this phone that supports all of the hardware.
I love the specs of this phone - and the form factor, however, it doesn't matter which ROM I use, the phone is just so unbearably slow. Even with the light ROMs.
I simply hate Windows Mobile. The processor is not that slow - it should be able to do plenty - but everything takes 3 seconds at least to open. I've missed an inordinate number of phone calls just because the stupid send button takes 10 seconds to respond.
Is there any option at all to forgo a WM ROM and use a different OS entirely?
How can I take advantage of the amazing hardware - but not be dragged down by the software?
HELP!
Moved as not ROM Development.
Try flashing stock then ROM, changing Hard-SPL.. etc.
Never had problem with slow OS unless the ROM is an issue to which is very uncommon..
If it really takes 10 seconds to get the phone to answer a call...
One thing to check is memory -- Do you have a lot of stuff in your calls list or MMS texts? Clear them out.
Which ROMS have you tried? Any 6.1 or 6.5s?
There is no other usable OS now -- Android is getting close but it won't work with all the phone's components
OS Lag
stylez said:
Moved as not ROM Development.
Try flashing stock then ROM, changing Hard-SPL.. etc.
Never had problem with slow OS unless the ROM is an issue to which is very uncommon..
Click to expand...
Click to collapse
The last ROM I flashed that's exactly what I did - I flashed to a stack ROM - changed the Hard SPL.
The ROM I love - Shifu did a phenomenal job - but after a while - everything just begins to lag...and it's not just this ROM - it's every ROM. After a few weeks - everything just starts to miss a beat and then slowly unravel.
I'm surprised that you've never had any problems with the OS - the consensus is that WM is a generally slow OS - I just thought maybe there's a way to take advantage of the great hardware in the phone without having to use this OS.
Thanks for the advice though.
If you have any other suggestions - they would be much appreciated.
burtcom said:
If it really takes 10 seconds to get the phone to answer a call...
One thing to check is memory -- Do you have a lot of stuff in your calls list or MMS texts? Clear them out.
Which ROMS have you tried? Any 6.1 or 6.5s?
There is no other usable OS now -- Android is getting close but it won't work with all the phone's components
Click to expand...
Click to collapse
Maybe not 10 seconds - but I have missed plenty of calls because the phone was completely unresponsive.
I do have a LOT of SMS' - maybe that's it. I just flashed to a new ROM (jjblaster3's 6.5) - it's great for now. I hope it stays that way. But they all start off great...you start installing a few programs and then nothing moves.
Thanks for the SMS/call history advice - I'll start clearing out now.
Anything else you can think of would be great.
I went through similar problems. Currently I am using the ROM "forum.xda-developers.com/showthread.php?t=428261". This was the best ROM that I tested for my Kaiser.
I was not very fan of windows mobile too, because that i installed android at sdcard and recently found a very good application "forum.xda-developers.com/showthread.php?t=623792" to streamline the boot process for the android, without having to wait for the windows mobile start and then boot the android. Android is fantastic, but as has already been said not everything works. The GPS and camera are the major problems yet.
Thanks
bernabap said:
I went through similar problems. Currently I am using the ROM "forum.xda-developers.com/showthread.php?t=428261". This was the best ROM that I tested for my Kaiser.
I was not very fan of windows mobile too, because that i installed android at sdcard and recently found a very good application "forum.xda-developers.com/showthread.php?t=623792" to streamline the boot process for the android, without having to wait for the windows mobile start and then boot the android. Android is fantastic, but as has already been said not everything works. The GPS and camera are the major problems yet.
Click to expand...
Click to collapse
Thanks for the advice - I'm not going to head down the Android route yet...but I will check out the ROM you suggested. Have you tried any 6.5 ROMs you liked? I'm running jjblaster3 6.5 v2 right now.
Well personally, I like the STAXXX STYLE ROMs...they are 6.5.3...and VERY fast in my opinion.
ROM Suggestions
Thanks for the suggestion, any ROM recommendations would be much appreciated, here is what I'm looking for:
1) A fast ROM
2) No bugs with common things like text messages, bluetooth, WiFi, Internet
3) Good battery life
4) And if possible - 6.5 - but not mandatory
I know a LOT of hard work goes into cooking the ROMs, so I'm not complaining - but I've found that there are always small bugs that are real deal breakers for me.
I've tried:
1) AthineOS Manila Edition
Text issues, backlight issues
2) Shifu (3.2)
Text issues, screen rotation issues, wifi issues, phone got stuck a lot towards the end (had to soft reset twice a day at times)
3) Jjblaster3 v2
Battery life (very poor - need to charge twice a day) - because there is no easy way to switch between 3G and GPRS (any quick fix for this?)
shar1r said:
Thanks for the suggestion, any ROM recommendations would be much appreciated, here is what I'm looking for:
1) A fast ROM
2) No bugs with common things like text messages, bluetooth, WiFi, Internet
3) Good battery life
4) And if possible - 6.5 - but not mandatory
I know a LOT of hard work goes into cooking the ROMs, so I'm not complaining - but I've found that there are always small bugs that are real deal breakers for me.
I've tried:
1) AthineOS Manila Edition
Text issues, backlight issues
2) Shifu (3.2)
Text issues, screen rotation issues, wifi issues, phone got stuck a lot towards the end (had to soft reset twice a day at times)
3) Jjblaster3 v2
Battery life (very poor - need to charge twice a day) - because there is no easy way to switch between 3G and GPRS (any quick fix for this?)
Click to expand...
Click to collapse
This baby is fast as hell! http://forum.xda-developers.com/showthread.php?t=618767 try it
Any known bugs?
gmaniac2008 said:
This baby is fast as hell! http://forum.xda-developers.com/showthread.php?t=618767 try it
Click to expand...
Click to collapse
I have actually already downloaded that one - so as soon as my battery is more than 50% - I'll flash.
Thanks!
Do you know of anything to look out for bug-wise?
shar1r said:
I have actually already downloaded that one - so as soon as my battery is more than 50% - I'll flash.
Thanks!
Do you know of anything to look out for bug-wise?
Click to expand...
Click to collapse
No bugs reported so far
Hey Guys,
Ever since I first experienced this bug, it seems more and more people are coming forward explaining the same symptoms.
Connection drops, OS becomes unresponsive, freezes, and then you are greeted by the 'X' animation. After the phone reboots, it freezes once again and returns you to the 'X' animation and the process repeats until you pull the battery.
There seems to be no direct trigger as it can occur when on a call, when browsing or even when the phone is idle.
I've read through various threads on different forums in an attempt to reveal some kind of pattern, yet reports are coming from users on different ROMs with different kernels and different apps. I've created this thread in the hope that if people contribute their experiences, we can draw some kind of reasoning behind the development of the bug and offer some hope for resolving the issue in then future.
So guys, what are your experiences of the BLOD? What ROM were you running? What kernel were you running? Do you overclock, underclock or remain at stock? Anything you think may contribute to this annoying bug.
Thanks in advance.....
Reserved for future use
My experience began after updating to Kang-o-Rama 0.6 final (CM 5.0.6) after using Kings Desire Port aswell as using Paul's Desire ROM and Cyanogenmod previously. Originally it happened to me in the gym. While listening to music I recieved an SMS and the phone suddenly crashed and went into the BLOD. I had to pull my battery for it to stop. Since that occasion, I began to suffer the BLOD 3-5 times a day, sometimes when on a call and other times when the phone was idle. I tried wiping and reinstalling countless times, flashed stock Cyanogen and the later versions of K-o-R which would give my phone a slight reprieve ,however eventually the BLOD would hunt me down and return.
Eventually I believed it was a Cyanogenmod specific bug, especially after reading this thread,
http://forum.cyanogenmod.com/index.php?/topic/43-odd-crash/
Since I thought it was CM specific I went away and flashed Enom's ROM which again gave me a reprieve but only until I charged the phone at night. I awoke in the early house to find my phone rebooting away as I slept. This pattern continued for 3 nights until last night which was my first BLOD free night.
Now i'm not 100% sure as to what cured my looping last night but I flashed a new kernel yesterday (IR .33.5) and also on the advice of this thread,
http://www.google.co.uk/support/forum/p/android/thread?tid=2711ea74ef3d9aee&hl=en
I wondered whether the fact that I'd started using the stock alarm clock app could have triggered this so called 'notification bug'. I returned to using Gentle Alarm from the market and cancelled my stock Androdid alarm.
Right now i'm waiting to see how long I go without a BLOD before investigating if it was specifically the new kernel or changing the alarm which got me through the night. Will report back if anything changes.
I'm pretty sure this is a form of a kernel panic. I know Cyanogen had made some type of tweet or post regarding this. I'll try to find it and edit this post when done
wesbalmer said:
I'm pretty sure this is a form of a kernel panic. I know Cyanogen had made some type of tweet or post regarding this. I'll try to find it and edit this post when done
Click to expand...
Click to collapse
Cyanogen posted something regarding it being a system_server crash in the CM thread and that we needed logs of the event occuring before he could draw any conclusions. I managed to dump and adb logcat of the event while it was happening, although it was just a panic loop of which a segment was posted on the Cyanogenmod forum I posted above. Has anyone managed to capture a log of the BLOD as it starts? That would be a great help.
I got my N1 about 4 weeks ago and it worked OK until I flashed the Froyo radio. from that point on I could not get any rom to run in a stable way - my reboots happened 3 - 4 times a day and got to the point where I would get stuck in the boot loop. Pulling the battery did not always solve the problem although I found that if I kept the battery out for several minutes my chances of getting the phone to boot into either the ROM or recovery would be better.
I noticed at the same time that once the boot loop started I could not get into recovery until my phone had at least booted into the ROM successfully once.
Flashing back to the 4.04 radio reduced the random reboots to about once a day - usually at night after I had just plugged my phone in to charge. I was using the stock alarm app as a bedside clock.
After many days of frustration and the help from several people here at XDA, I finally came to conclusion that the problem must be hardware related and am returning my current device to HTC and am getting a new one.
I don't have a boot loop but I definitely experience the initial stages of this problem on a stock (unrooted, locked) N1 (at&t).
50% of the time when the N1 loses the connection (e.g. due to going into a garage) it will not re-acquire the signal. Searching for networks will hang, putting the phone in flight mode and then disabling flight mode will still result in no signal.
The only way to get a cell signal back is rebooting the phone.
Usually, searching for a network and/or enabling and disabling flight mode will result in the phone turning black and then rebooting.
I have the problem, too.
Just a few notes:
didn't have it on stock rom and Cyanogen 5.0.6, nor an Enomther's 1.8.1, started with Enomther's 1.9.2
This is not really a reboot, because a real reboot always helps. Other than a reboot, it starts directly at the X animation, not with the unmoving X before.
Seems to be a kernel panic.
I currently suspect that the panic happens when the RAM is full, especially if there is one single process that uses up massive amounts of RAM (could be in the background, of course).
I yesterday found that Sytrant (periodically sets time using internet time server) has a memory leak, and on closer inspection today found that it queries an ad server every few seconds and thus switches from sleeping to running state every few seconds. Also, it spawns root processes when setting time, which might lead to the system not wanting to kill it.
So, here's my current suspection (I'm not at all sure if that's true!):
The reboot loop only happens when the system runs out of memory.
In this case, Android should normally kick out other programs: First apps that are not running anymore, but are still in memory, second background jobs, and third services.
I guess there's some error in the killing logic in newer Cyanogen kernels and others that use Cyanogen parts (or maybe even in the orginal code from Google).
This somehow leads to a state where the kernel has no memory left and can't kill a process, too. -> Kernel panic
Maybe this is more probable if there is one big memory hog the kernel doesn't want to kill (because it's a service, or maybe because it has children running as root).
So, everyone who has this problem, please get a process monitor or task manager where you can see how much memory an app uses. OSMonitor is a very good one, and it can also sort the processes by memory usage. Start it periodically to find out if a process is constantly growing.
If you found such a process: Is it one that requires root? Does it run as a service? (Unfortunately, OSMonitor can't tell you if a process runs as service, or at least I didn't find it if it can. ES Task Manager can show that information, though, for example.)
Personally, I threw Sytrant off my phone now and will watch if that helps. I had reboot loops every two or three days, so I can't tell yet if it really will make a difference. I really hope so …
Edit: Of course, this theory does not really explain why the network drops before the boot loop starts. It could be, though, that the kernel tries to kill just anything to gain meomry, which might also be a system process that it responsible for the network. As the networks always seems to drop before the loop starts, maybe killing that process is what leads to the panic in the end.
Maybe, could … well, yes, this is just a theory. But at least it sounds good, doesn't it? ;-)
The more I read about this problem here and in other threads, the more I am convinced that my problem is probably not hardware related. My replacement phone arrives today but now I am wondering if I should return my original or not. Argg!
Is there a way we can all band together to try and get to the bottom of this problem? I am more than willing to do whatever testing those that know what to look for tells me to do.
Would one of the Guru's here be willing to guide us through a coordinated troubleshooting excersize?
Maybe we can start by trying to find out what we all have in common?
I have an AT&T/Rogers version of the N1.
I typically have the Facebook, Calendar Widgets on home screen.
Power Widget on 2nd screen
Use gmail but via the standard email client, not the gmail client.
Use the native alarm clock app in the dock at night
16GB ADATA MicroSD card.
I also install:
- ChompSMS (with icon widget on home screen)
- NewsRob (with Widget on home screen)
Did not get the reboots initially running the stock rom but they started the moment I installed paul's version of Froyo. I tried several of the other roms and had the same instability and BLOD's until I reverted back to stock and things stabalized again although I was still getting random reboots once a day or so.
While a hardware issue (especially RAM failure) could cause this issue, I don't think that it is the cause in most of the cases here. The fact that some don't experience it anymore after trying one or another software-related measure makes a hardware failure highly improbable, at least in their cases.
I won't rule that out, but until I tried everything else I can't conclude it must be a hardware faliure.
Please get OSMonitor and watch your processes. If after some days you still can't find a process using more than, say, 65 M, and still get the issue, you can be pretty sure that a memory leak isn't the problem for you.
The memory leak + killing bug guess is a good one and is quite probable. So let's check that first.
I think my FroYo rom problems are the same problems you guys are having. I think it's something with an app or an element of the OS or something.
http://forum.xda-developers.com/showthread.php?t=703508
I get the exact same issue on a handful of roms. Everything starts to force close, then it goes into boot loop, but, as someone said, doesn't really fully reboot, it just starts at the boot screen.
I've also noticed when things get funky, plugging in the USB cable makes it immediately go into a boot loop.
I start having this problem after I install the Quadrant Standard program, I was using the Kang-o-rama - Froyo when this happened. But after going back to Paul's Froyo everything is working perfectly again.
cmarti said:
I start having this problem after I install the Quadrant Standard program, I was using the Kang-o-rama - Froyo when this happened. But after going back to Paul's Froyo everything is working perfectly again.
Click to expand...
Click to collapse
I deleted quadrant, signed into market and all so it knew i uninstalled it, flashed a baked modaco R17, and it still boot looped on first reboot.
I suspect it is related to the 4.06 radio. My first boot loop started just after I installed the radio and before I updated the ROM itself.
DvTonder said:
I suspect it is related to the 4.06 radio. My first boot loop started just after I installed the radio and before I updated the ROM itself.
Click to expand...
Click to collapse
That doesn't explain mine though. I get the boot loop on some roms but not others, with the same radio.
MSigler said:
That doesn't explain mine though. I get the boot loop on some roms but not others, with the same radio.
Click to expand...
Click to collapse
Which ROMS are safe for you - I will flash one of them tonight and see if it works on my device as well - maybe we can narrow it down to a specific ROM.
Would also appreciate a list of the apps you use - I am thinking we should set up our phones as close to identical as possible to begin with and then start adding things to see what causes it. Thoughts?
DvTonder said:
Which ROMS are safe for you - I will flash one of them tonight and see if it works on my device as well - maybe we can narrow it down to a specific ROM.
Would also appreciate a list of the apps you use - I am thinking we should set up our phones as close to identical as possible to begin with and then start adding things to see what causes it. Thoughts?
Click to expand...
Click to collapse
The only roms that screw up for me are modded froyo roms. LeoFroyo works fine for some reason, as does the stock FRF50. I'll screenshot my apps in a minute and post them.
I have this on stock 2.1u1 EPE54B
I was getting some pretty random boot loops when running CM 5.0.7.1 and 4.04 radio. Noticed two things could (almost) cause it every time:
1) Not so much a cause, but Google Listen was running almost every time I went into a BLoD.
2) Something that WAS causing it.. I keep my phone on airplane mode at work with WiFi on, since I don't get a reception in the building. Reboot + turn off airplane mode when the phone is to that point = BLoD.
I actually flashed Kang-o-Rama and the 4.06 radio earlier, no problems now.
tjsimmons said:
I actually flashed Kang-o-Rama and the 4.06 radio earlier, no problems now.
Click to expand...
Click to collapse
Did you flash the Froyo version with SP3?
I am trying to get a solution for these 3 problems I am facing with Doc´s 7.6.2.
Maybe it is not a big deal to make it a perfect ROM but these 3 topics are annoying:
I wrote the same message already in Doc´s threat but no answer at all. in 5 min 10 new messages so nobody really takes care for a new question
Hi Guys,
Some problems I do have with the 7.6.2 and for sure I am not alone with these errors.
1 From time to time high energy consumption but sometimes not - this is crazy. One thing I realized when alarm is switched on for all weekdays then it sucks almost 20% in 5h - just in standby mode. Whats wrong here?
2 GPS signal is bad. When you using this tracking tools eg. cardio trainer it looses half time the GPS signal. Was definitely not with older ROMs.
Is that the modem version?
Is this part of the kernel?
3 Bluetooth works but whenever activating and deactivating getting a stupid message about an opp bla bla.
What is wrong?
Who can help?
Thanks
boris03
quite alot galaxy s users have reported issues with the gps reception i used to think its just a driver issue but upon reading into it would seem its related to the antenna. The wifi also suffers from this problem for me it does anyway. you can try out gps booster lite from market it does help outdoors to get a faster fix as for battery issues well im not so sure you would prob better asking in that thread if your still not heard try sending a pm that should work. good luck
boris03 said:
I am trying to get a solution for these 3 problems I am facing with Doc´s 7.6.2.
Maybe it is not a big deal to make it a perfect ROM but these 3 topics are annoying:
I wrote the same message already in Doc´s threat but no answer at all. in 5 min 10 new messages so nobody really takes care for a new question
Hi Guys,
Some problems I do have with the 7.6.2 and for sure I am not alone with these errors.
1 From time to time high energy consumption but sometimes not - this is crazy. One thing I realized when alarm is switched on for all weekdays then it sucks almost 20% in 5h - just in standby mode. Whats wrong here?
2 GPS signal is bad. When you using this tracking tools eg. cardio trainer it looses half time the GPS signal. Was definitely not with older ROMs.
Is that the modem version?
Is this part of the kernel?
3 Bluetooth works but whenever activating and deactivating getting a stupid message about an opp bla bla.
What is wrong?
Who can help?
Thanks
boris03
Click to expand...
Click to collapse
1.) Turn off your lagfix, run stock RFS see if you still get the issue.
Do a fresh install dont add ANY apps other than stock, observe for 1-2 days of battery usage.
2.) GPS is a hit or miss, hardware is broken.
3.) Never had issues with BT, I use it on a day to day basis to pass around files at the office.
Are you using one of those OC kernels? Or any of the suggested kernels for the matter? I was using Super Optimized Kernel for a while and the battery drain was outstanding even on the non-OC versions. Switched to SpeedMod 300hz. Haven't monitored the battery though but it seems better with normal usage. Also, what lagfix are you using? For a time I was using the Ext-4 Overkill lagfix from the ULF and I noticed considerably less battery life.
As Earlz suggested, try disabling lagfixes and tweaks and monitor..then if it is better than before perhaps using a different lagfix would be a solution. Try switching up kernels (remembering to disable lagfixes prior). Try running different launchers too. I'm no expert on how these things work and affect battery life, but this is all based from personal experience.
My GPS never worked from the start no matter what firmware/ROM I'm on so it seems to really be a hardware issue as EarlZ mentioned. If the problem came about after flashing 7.6.2 then try reflashing to stock firmware with repartition and installing 7.6.2 again after clearing cache and factory reset. Somehow that (having a super clean install) usually fixes random problems I get with any ROM. I'm not certain if it will have any affect on GPS performance but it's worth a try.
Bluetooth is still working fine for me. Perhaps the aforementioned clean install advice I gave could remedy this.
Hi there, i rescently installed DJP5 v8.0.1 . And have some problems with it. When i'm making call i hear the other side perfect, but they dont hear me well. Is it some issue with the ROM or ? Have someone else experienced similar problems?
darkfire_bg said:
Hi there, i rescently installed DJP5 v8.0.1 . And have some problems with it. When i'm making call i hear the other side perfect, but they dont hear me well. Is it some issue with the ROM or ? Have someone else experienced similar problems?
Click to expand...
Click to collapse
There is investigation on that one...
For now, it seems to be a modem issue from the stock modem of ADJP5
Flash another modem seems to fix this issue
darkfire_bg said:
Hi there, i rescently installed DJP5 v8.0.1 . And have some problems with it. When i'm making call i hear the other side perfect, but they dont hear me well. Is it some issue with the ROM or ? Have someone else experienced similar problems?
Click to expand...
Click to collapse
Sigh....Thats covered in the main thread for this rom, try a different modem.
Sent from my GT-I9000 using XDA App
Hey guys! This is my first post on XDA, though I've been using it for quite a while.
I'm not exactly looking for answers/solutions, but rather sharing my problem and see if someone else is having them too.
I have a Latin American version of the I91000 (TTT). I recently upgraded to ICS using the official firmware from Samfirmware (UHLPE). At first everything looked great. The performance improvement was noticeable from the first bootup. Not only was it faster, but the intro video was far smoother and looked nicer. The general UI changes are very nice, and I did notice an improvement in battery life.
However, I've been experiencing a couple of glaring issues that really mared the experience enough to make me want to go back to Gingerbread, which I will probably do.
These are the problems:
1. The mobile data connection is very unstable. Sometimes it just doesn't load anything, and sometimes I lose the signal altogether. The 3G/H/H+ icon disappears and all. I never had this problem in GB during the 6 months I've had this phone.
2. The Bluetooth audio connection also has problems. It's now more unstable and susceptible to interference, and the lag is also much more noticeable now. It was about .5 seconds before, but now it's more than a full second.
But that's not the worst issue. The media remote control functions just stopped working altogether, namely, the |<< , >>| , >/|| buttons on my headset. I have a Nokia BH505 Bluetooth headset, and I didn't have any of these problems before either.
So that's it. I would like to know if someone else is experiencing one or both of these issues. I'll also check the Samfirmware forums to look for replies on the matter. Thank you for your feedback.
Hello guys, I've recently switched to Darky 10.2 EE and then Resurrection (XXJVQ), always having the same problem. The phone may become extremly laggy, particularly when trying to browse the internet with various browsers (except using Opera -mini- which is very light and missing features). When browsing a page it will start lagging, stuck for some seconds and after a while even freeze! This is very annoying because I upgraded from 10.1 to improve these particular aspects and they got worse! At least when I was with 10.1 EE I could open 3 or 4 tabs with Opera Mobile.
Similarly the GPS application which I use may become laggy and stuck for a while (very frustrating when you are on the road) which didn't use to happen before.
Guys, as I am suspecting RAM issues, is there anything I can do to improve the ROM's memory performance/behavior? Maybe something I didn't do right...
I have just flashed this and it is laggy just out of the box. I'm very disappointed with Darky ROM.
Have you activated the lagfixes? Better yet, do you know what lagfix is?
snapper.fishes said:
Have you activated the lagfixes? Better yet, do you know what lagfix is?
Click to expand...
Click to collapse
Hello my friend. If you mean in recovery mode: both voodoo lagfix and system lagfix conversion are enabled, debug mode is off.
What they do exactly however, I am not sure.