Hi all,
I wondered if anyone was running Co-pilot on Modaco 3.0? This was working great on my previous stock rom but since updating it freezes after around 30 minutes use. If left the device gets quite warm as well. Anyone else had this problem and, more importantly, found a fix?
My problem is that I updated to 3.0, and 1.91 kernel and updated my radio at the same time. Does anyone have any idea which is likely to be causing the problem?
Cheers for any advice,
Michael
should add that this is happening after around 30ish minutes use. I was on radio 63.18.55.06JU_6.35.08.29 but have just downgrade to the one before (I realise there is a newer version but it really seems to drain my battery).
After a bit of searching it seems I am not the only one with this problem so I will keep this thread up to date in case it is of any use to others. I now have co-pilot sat next to my computer running trying to replicate the problem.
and finally, does anyone know what the stock radio for t-mobile UK is? I suppose it will help me narrow down quicker if I dropped back to this one to see how I get on.
cyberkid2002 said:
Hi all,
I wondered if anyone was running Co-pilot on Modaco 3.0? This was working great on my previous stock rom but since updating it freezes after around 30 minutes use. If left the device gets quite warm as well. Anyone else had this problem and, more importantly, found a fix?
My problem is that I updated to 3.0, and 1.91 kernel and updated my radio at the same time. Does anyone have any idea which is likely to be causing the problem?
Cheers for any advice,
Michael
Click to expand...
Click to collapse
using 3.0 here; works ok. went on a 80 mile trip today; 1hr 15m still telling me to go!
Mine doesnt freeze but it does loose GPS signal quite often.
Thanks for the replies. Can I be nosy
PHP:
and ask what radios your both using? I switched to .22 and used satnav for a 30ish minute drive and seemed fine, no loss if signal etc. but phone was still getting incredibly hot.
Will give it a proper try new years day and see if it really has improved.
Working ok with modaco 3.0 and radio .29 . Always did get hot.
So there are people on here that get good (not fantastic) performance from there GPS with stock, while others like myself have terrible gps performance with stock. I can't lock on, only 2 satellites in view ext. ect, ect. I even tried all the lbstest changes people recommended and i had no change, while others say its fixed.
When I flashed JH7 from odin one click download I got really good results, locking on after a minute or less down to 10 M and with 9 statalites in view.
but I've read others didn't have the same result as me and nandroided back.
Are we sure we all have the same GPS hardware? why do all of our results vary so much with the same rom on the same hardware.
mattbeau said:
So there are people on here that get good (not fantastic) performance from there GPS with stock, while others like myself have terrible gps performance with stock. I can't lock on, only 2 satellites in view ext. ect, ect. I even tried all the lbstest changes people recommended and i had no change, while others say its fixed.
When I flashed JH7 from odin one click download I got really good results, locking on after a minute or less down to 10 M and with 9 statalites in view.
but I've read others didn't have the same result as me and nandroided back.
Are we sure we all have the same GPS hardware? why do all of our results vary so much with the same rom on the same hardware.
Click to expand...
Click to collapse
It could be that some people master clear, when others haven't. I use SRE and my performance is amazing with the GPS. DG does some tweaks still i believe, and my gps tracks amazingly.
Other than that, I have NO clue why. Maybe people have more trees in the area and get less lock? Only thing I can think of.
thanks for the reply, it turns out that after doing a master reset and reflashing jf6 my gps is running better. I dont know what changed but it is performing the same as jh7 was. I guess back to the drawing board
my gpa worked better stock, and with the overclock kernel and utb. I then used jf7 and sre and I'm thinking about going without sre, or maybe move ap only version.
I didn't try jf7 without sre though so I can't know what it will do. I actually have a feeling that my recent poor performance is nothing but a coincidence though. I'll give it a few days and a road test.
Sent from my SAMSUNG-SGH-I897 using XDA App
Mine works fine with JF6, utb, and lagfix ext4.
Wife's also works fine with JF6 and utb.
We used google navigation on hers yesterday and it worked just fine.
Part of the problem is not everyone is testing GPS the same way. The best test is using the NAV application - and not just on a simple route in the neighborhood. Combination highway and local driving - see if the NAV thinks you are on the street or keeps trying to reroute you. Does it tell you about turns or think you missed them?
Also Track your travels and view it on Google maps - really zoom in and see if you wander through buildings.
I think some of it may have to do with system blocking - more things running in the background may have to dow ith how often the GPS updates.
Hi,
I'm still running the oc'd 2.2 Overcome fw with oclf and from the moment it booted I was just like Woohooo, that's pretty fast right there!
At 1,4 GHz games ran like a charm and flash vids also. Response time to input is absolutely amazing in comparison to stock rom.
So for those who already flashed to 2.3 on their tabs:
Is it worth it to update to GB?
And lets keep things like power management or battery indication aside and please focus on useful features like the lit buttons while the screen is on eg.
I got everything ready and off to go update, but I somehow love the tab right now and don't wanna mess up this high perf thingy and am afraid, that I'll not be able to reproduce this condition.
Thanks in advance.
K here you go.
The 4 "hard" button lights never turn off. Drives me nutts.
I ran quadrant and got a score of a lowely 940. I am used to getting over 2400 at 1.4 ghz. Plus the test ran wierd. The graphics were really low end, makes me think our graphics card is not being utilized correctly as of now with current update.
Linpack gave me a 11. As opposed to the 19, 20 i got at 1.4
I dont think we have voodoo lagfix yet. I stream alot of video, and I need this fix!
Had to contact Gameloft to get fresh links for all my games as the old ones were for 2.2. That sucked explaining to them I have a "official" firmware that is not out yet.
Had to reinstal uninstal flash several times to get it to work correctly. Finaly had to settle on 10.1. Web pages indicated I didnt have flash.
In my opinion, I would wait untill you can overclock it. Or atleast a cm7. I am gonna stay on it to mess around with some games that need 2.3.3
I was excited about the prospect of an actual google voice. As it needs gingerbread to work correctly, but that is a bust so far cause our phone number cannot do incomming calls. So basically it works the same as on 2.2.1. You can use it in conjuntion with groove ip to call out and get voicemails, but no incomming calls. Google chat is a bust also. No video chat for us yet.
Also, I havent seen any conformation that we can go back to 2.2 or 2.2.3
HIT THE THANKS BUTTON IF I HAVE HELPED.
Sent from my GT-P1000 using XDA Premium App
Well, after some time on GB I don't wanna go back =)
Only the OC/UV kernel is a bit tricky.
Hey guys, as far as the Nexus One and CM 7 goes, what are the optimal settings to keep checked in CM settings, and what's the best kernel/settings for speed, but great battery life? I downloaded and installed Pershoot's kernel. Please let me know because I need the phone for long periods of time for two weeks, but I can't get an extended battery. I'm new to the N1, hence why I ask you all and can't test on my own. Thanks!
CM7 is pretty well pre-configured for great battery life and great performance. I don't know if there is much you could change that would show any benefit within the install.
I think redstar has been creating some of the most popular kernels as of late. Great performance and battery life (from what I read).
Also, if you aren't running the nightlies, I can highly recommend it. There have been some substantial performance enhancements and battery savings that have been a result of some major bug fixes. Build #87 has been working great for me.
bassmadrigal said:
CM7 is pretty well pre-configured for great battery life and great performance. I don't know if there is much you could change that would show any benefit within the install.
I think redstar has been creating some of the most popular kernels as of late. Great performance and battery life (from what I read).
Also, if you aren't running the nightlies, I can highly recommend it. There have been some substantial performance enhancements and battery savings that have been a result of some major bug fixes. Build #87 has been working great for me.
Click to expand...
Click to collapse
Thanks so much, but could anyone else please provide me with further/specific/good cyanogen mod settings for the N1, such as what to check, how much VM heap, etc?
I'm gonna stick with pershoot for kernels, as i use him for the G2, and before the G1.
I freakin' love nightlies, BUT, the reason I'm running stable is because I'm leaving the country for two weeks, and I won't have access and the freedom to change my ROM due to not having a computer all the time. Hence the stable version - I do love nightlies though!
To reiterate, what are the best CM settings for CM7? Thanks in advance, guys!
Well, if you are going to run stable, do a search for the "wonk fix" and flash that zip. It is one of the major fixes in the nightlies that improves battery life.
I'm still not sure that there are any settings you could really play around with that would show any tangible benefit.
And with build #87, it has been rock solid for me. I thought the ADW EX transistions in the past were smooth. You don't need to constantly update the nightlies if you can find a good one. Just sit it out until you feel like updating again. And #87 is a great one to be at.
bassmadrigal said:
Well, if you are going to run stable, do a search for the "wonk fix" and flash that zip. It is one of the major fixes in the nightlies that improves battery life.
I'm still not sure that there are any settings you could really play around with that would show any tangible benefit.
And with build #87, it has been rock solid for me. I thought the ADW EX transistions in the past were smooth. You don't need to constantly update the nightlies if you can find a good one. Just sit it out until you feel like updating again. And #87 is a great one to be at.
Click to expand...
Click to collapse
Sounds good, man. Thanks for your help and telling me about the wonk fix! Although I'm not 100% sure what it's for.
Should home and messaging in memory be checked?
One more issue, when I nees to press the capacitive home, menu, back, and search button, I always have to tap a bit higher than where thee keys are actualy located on the screen.everything else about the touch screen is fine. what's the reason for this?
isikh said:
Sounds good, man. Thanks for your help and telling me about the wonk fix! Although I'm not 100% sure what it's for.
Should home and messaging in memory be checked?
One more issue, when I nees to press the capacitive home, menu, back, and search button, I always have to tap a bit higher than where thee keys are actualy located on the screen.everything else about the touch screen is fine. what's the reason for this?
Click to expand...
Click to collapse
The wonk fix was an issue that plauged CM for quite a while on the N1. It caused hard lockups of the microphone and the screen. Also, because of it, the microphone was never able to enter its low-power sleep state. With the wonk fix, you won't have any issues with the mic, and the phone will reach its low-powered sleep state.
I have never enabled the keep in memory options. My understanding is these settings were more for devices that had limited RAM (like the G1), because Android would dump these programs to free up memory for other apps, so when you went to them, it would take a while for the system to restart them. I haven't ran into a need to do this on the N1. The heap size limits the amount of ram that an app can use. Unless you are running some crazy memory intensive apps, there is really no need to adjust this. It won't help most of the apps that are out there.
As for the capacitive buttons, welcome to the wonderful world of the N1 digitizer (touchscreen). I don't know of any way to adjust this, but you get used to it pretty quickly.
bassmadrigal said:
The wonk fix was an issue that plauged CM for quite a while on the N1. It caused hard lockups of the microphone and the screen. Also, because of it, the microphone was never able to enter its low-power sleep state. With the wonk fix, you won't have any issues with the mic, and the phone will reach its low-powered sleep state.
I have never enabled the keep in memory options. My understanding is these settings were more for devices that had limited RAM (like the G1), because Android would dump these programs to free up memory for other apps, so when you went to them, it would take a while for the system to restart them. I haven't ran into a need to do this on the N1. The heap size limits the amount of ram that an app can use. Unless you are running some crazy memory intensive apps, there is really no need to adjust this. It won't help most of the apps that are out there.
As for the capacitive buttons, welcome to the wonderful world of the N1 digitizer (touchscreen). I don't know of any way to adjust this, but you get used to it pretty quickly.
Click to expand...
Click to collapse
Okay - I'll keep those disable then, and yay digitizer. Also, I don't know if it's the wonk fix, but my camera is force closing now
isikh said:
Okay - I'll keep those disable then, and yay digitizer. Also, I don't know if it's the wonk fix, but my camera is force closing now
Click to expand...
Click to collapse
No, the wonk doesn't affect the camera. What is your radio version (aka baseband)? With the N1s we usually just refer to the two sets of numbers after the underscore "_" (eg 5.08, 4.06, etc). The 5.08 is the version that google sent out with the Gingerbread update and overall seems to be the best consistent performer for the phones. The 4.06 seems to crash the camera and/or camcorder. The 5.12 seems to be really hit or miss. Some phones it runs great, others they get all sorts of issues. I usually recommend the 5.08.
bassmadrigal said:
No, the wonk doesn't affect the camera. What is your radio version (aka baseband)? With the N1s we usually just refer to the two sets of numbers after the underscore "_" (eg 5.08, 4.06, etc). The 5.08 is the version that google sent out with the Gingerbread update and overall seems to be the best consistent performer for the phones. The 4.06 seems to crash the camera and/or camcorder. The 5.12 seems to be really hit or miss. Some phones it runs great, others they get all sorts of issues. I usually recommend the 5.08.
Click to expand...
Click to collapse
Okay, and my apologies, with college I've missed and forgot key things about android - how do I find my radio version? Boot into fastboot or the bootloader?
EDIT: Under basband version, on the about phone menu, it says:
32.24.00.22U_4.03.00.21_2
Is that baseband 4.03?
Yes, the radio on your phone is 4.03. I would highly recommend updating it to 5.08. There is a basic guide in the wiki for it, or you can hit up the N1 wiki on xda for a more in depth guide.
the wonk fix and and kinda directly related to that fix greatly fixed some battery issues which kinda makes running the last stable version not worth it. the newest nightly is so much improved on battery idle current draw that its something needs to be emphesized. its that good where you can be unplugged for 8 hours and lose 3% battery idle standby, wifi on. 3-4mA current draw.
that aside, pershoots kernel is great, redstar too. there's not much i do anymore with settings on cm7 cause its so good lately.
bassmadrigal said:
Yes, the radio on your phone is 4.03. I would highly recommend updating it to 5.08. There is a basic guide in the wiki for it, or you can hit up the N1 wiki on xda for a more in depth guide.
Click to expand...
Click to collapse
Where is said wiki located?
I'd like an in depth, detailed noob guide as to avoid messing up the phonee
Also, thanks for the info Roger. I'm gonna stick with nightly #87 since peeople are saying the battery life is great and it's stable.
isikh said:
Also, thanks for the info Roger. I'm gonna stick with nightly #87 since peeople are saying the battery life is great and it's stable.
Click to expand...
Click to collapse
that's the perfect choice, you will be very happy.
isikh said:
Where is said wiki located?
I'd like an in depth, detailed noob guide as to avoid messing up the phonee
Click to expand...
Click to collapse
I'm on my phone so it is hard to do links, but if you go into the Nexus One General forum, I think it is one of the first few stickys in there.
Wiki:
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One
Did quite a bit of searching and still can't nail down an answer. Does anyone have latency issues with the N6 running Marshmallow? Ever since upgrading in Marshmallow (ran last few releases of Chroma w/ various kernels) it takes FOREVER to load webpages. To run a speedtest, it takes 20-30 seconds (or more) to find a server, then shows upwards of 50 mbps download speed. The speed is there, but it is not getting through. I know there are known Wifi issues with M on the N6, but it gets frustrating. It is an issue that exists through both clean flashes and dirty flashes. Any help?
Thanks!
I had made a couple of posts about this and I'm noticing it too! The WiFi is just really dodgy! What I was able to dig up was that it was a change in the radio file this time that seems to be kind of buggy! Someone told me that you could download a lollipop stock image and flash the radio from that, and that it's independent of the OS itself. I haven't tried it yet, but I am noticing this issue too! I hope it gets fixed soon because it's a frustrating bug!