[Q] Froyo, Cyanogen Mod 6 - Nexus One Q&A, Help & Troubleshooting

I just put the cyanogen mod 6 on my nexus and after flashing gapps i cant get past the "touch the android to start" screen. i have restored and reflashed at least five times and still cant get past the first screen! Anyone else had these problems?

Havent had any problems myself. Have you tried touching the 4 corners of the screen with the android in a clockwise order to skip setup? If you can do that, then it should be as simple as logging into the marketplace and setting up your account there. If all else fails try downloading a new version of the gapps from cyans cm6 thread and reflashing.

will do sir, ill give it a go!

isolated_epidemic said:
Havent had any problems myself. Have you tried touching the 4 corners of the screen with the android in a clockwise order to skip setup? If you can do that, then it should be as simple as logging into the marketplace and setting up your account there. If all else fails try downloading a new version of the gapps from cyans cm6 thread and reflashing.
Click to expand...
Click to collapse
that should get it fixed up, worked for me atleast 10 times

This happened to me. I think I flashed the gapps for edr79 or something (since its link was once a neighbor to the CM6 link). Either way erase the one you have and search for the frf83 gapps, or frf91 gapps and try the whole process again. Or go with the answer above, that should work either way.

Related

Installed Hero twice and having issues

I installed Hero the latest version and whenever I get the phone on it says "the process android.process.acore has stoped unexpectedly. Please try again" What do I do, I been without a working phone for almost 7 hours now
mikesx4911 said:
I installed Hero the latest version and whenever I get the phone on it says "the process android.process.acore has stoped unexpectedly. Please try again" What do I do, I been without a working phone for almost 7 hours now
Click to expand...
Click to collapse
Without making things too complicated, and to simply get you back up and running. just flash another ROM....
That way you will have your phone back in working order and you can do some more research regarding ROMs. Keep in mind that many of the Hero ROMs are still somewhat buggy but are coming along nicely. The good news is there are many Hero ROMs to choose from so picking another will likely fix your acore process force close.
im seriously ready to shoot this phone I wiped, cleared the ext 3 times and if i ever get to the OS cuz most of the time Im stuck at HTC and the little hero keep looping. I will wipe ext and alt wipe and try to load up a different rom
im seriously ready to shoot this phone I wiped, cleared the ext 3 times and if i ever get to the OS cuz most of the time Im stuck at HTC and the little hero keep looping. I will wipe ext and alt wipe and try to load up a different rom
Click to expand...
Click to collapse
Yeah..i think that would be a good idea. You can try cyanogen's rom. Probably the 3.9.10 version, which is a pretty fast and stable rom, and then just get Ted417's Hero theme(which I think is the best Hero theme out there) flashed on there to give you that Hero look minus the widgets of course, if that's the look you're going for.
eessel said:
Yeah..i think that would be a good idea. You can try cyanogen's rom. Probably the 3.9.10 version, which is a pretty fast and stable rom, and then just get Ted417's Hero theme(which I think is the best Hero theme out there) flashed on there to give you that Hero look minus the widgets of course, if that's the look you're going for.
Click to expand...
Click to collapse
that theme is garbage lol. It wont even install, I tried like 4 times. WTF!!!!
Are you using ext4?
i got it working lol
mikesx4911 said:
i got it working lol
Click to expand...
Click to collapse
Mind telling us what you did to fix it so others may know if they have the same problem?
Hi there, I'm having the same problem.
Hero was fine until I did a factory reset (I'd cleverly managed to lock myself out of it via the security swipe).
Anyway, did the factory reset and now I get the android.process.acore has stopped unexpectedly problem.
I'm not that keen on installing other ROMs at this point, just hoping you can share your solution.
I'm guessing but it seems to be connected to my contact card within contacts. (If i wipe the info in that and log out of facebook the issue stops).
trstn said:
Hi there, I'm having the same problem.
Hero was fine until I did a factory reset (I'd cleverly managed to lock myself out of it via the security swipe).
Anyway, did the factory reset and now I get the android.process.acore has stopped unexpectedly problem.
I'm not that keen on installing other ROMs at this point, just hoping you can share your solution.
I'm guessing but it seems to be connected to my contact card within contacts. (If i wipe the info in that and log out of facebook the issue stops).
Click to expand...
Click to collapse
What I did was load a different rom non hero first, than updated to a hero rom and it worked. Because I couldn't figure out how to get rid of it lol. But personally I stopped using the hero rom, there to slow, and missing to much stuff such as bluetooth and etc.
mikesx4911 said:
What I did was load a different rom non hero first, than updated to a hero rom and it worked. Because I couldn't figure out how to get rid of it lol. But personally I stopped using the hero rom, there to slow, and missing to much stuff such as bluetooth and etc.
Click to expand...
Click to collapse
for what its worth. hero itself is not a theme. and neither is cyanogens roms. when you said that "this theme is garbage" you may have been talking about the wrong item.
also to get rid of a rom, just wipe, plain and simple.

Cyanogen 4.2.11.1 Issues

Hi there Android people.
I am having some issues with running the current Cyanogen *4.2.11.1*.
Phone: G1 Drea100 PVT 32B with stock 1GB SD
using anmon RA 1.5.2 recovery image
-wipe all available in menu.
-created a new partition- FAT32, Ext1 (upgraded to 4), Swap 32MB
-wiped all again.
-repair SD: ext
-flash signed-dream-devphone-userbug-ota-14721
-Once the flash above completed I did not restart, I simply flashed to update-cm-4.2.11.1
-reboot
Once it boots, my home process stops responding if I touch anything. This last for about 15 seconds, after that it seems to responds fine, but the browser and market place seems to auto-close on me from time to time, and I get random phone reboots, after a few reboots my phone simply stops turning on. I have to wait about 10 minutes to get into recovery and try to flash all over again.
I tried fix_permissions in the terminal, no luck.
I did some reading and noticed a lot of people are running different Radio/SPL versions other than stock, I am no super user, so I don't know if any of this effects ROMs, or if I should be flashing either for any sort of benefits I am missing out on? could this be the issue? Current SPL/Radio below:
HSPL10.95.3000
CDLP-4
Radio-2.22.19.261
Any input would be much appreciated.
Thanks,
D3AD PIX3L said:
Hi there Android people.
I am having some issues with running the current Cyanogen *4.2.11.1*.
Phone: G1 Drea100 PVT 32B with stock 1GB SD
using anmon RA 1.5.2 recovery image
-wipe all available in menu.
-created a new partition- FAT32, Ext1 (upgraded to 4), Swap 32MB
-wiped all again.
-repair SD: ext
-flash signed-dream-devphone-userbug-ota-14721
-Once the flash above completed I did not restart, I simply flashed to update-cm-4.2.11.1
-reboot
Once it boots, my home process stops responding if I touch anything. This last for about 15 seconds, after that it seems to responds fine, but the browser and market place seems to auto-close on me from time to time, and I get random phone reboots, after a few reboots my phone simply stops turning on. I have to wait about 10 minutes to get into recovery and try to flash all over again.
I tried fix_permissions in the terminal, no luck.
I did some reading and noticed a lot of people are running different Radio/SPL versions other than stock, I am no super user, so I don't know if any of this effects ROMs, or if I should be flashing either for any sort of benefits I am missing out on? could this be the issue? Current SPL/Radio below:
HSPL10.95.3000
CDLP-4
Radio-2.22.19.261
Any input would be much appreciated.
Thanks,
Click to expand...
Click to collapse
Why did you use "signed-dream-devphone-userbug-ota-14721"
I'm no pro but I used the base image that cyanogen recommends on his wiki page. The DRC83 defanged located here:
http://wiki.cyanogenmod.com/index.php/Latest_version#Defanged_DRC83
staunty said:
Why did you use "signed-dream-devphone-userbug-ota-14721"
I'm no pro but I used the base image that cyanogen recommends on his wiki page. The DRC83 defanged located here:
http://wiki.cyanogenmod.com/index.php/Latest_version#Defanged_DRC83
Click to expand...
Click to collapse
He used that because it is the proper image to use. A defanged file simply means that it has been rendered safe to download with no fear of infection. The link on his site is to the file used by the OP, so no worries there. Also, your radio is good, so do not worry about that either.
I have to ask, because you did not mention part of the process that should be happening. You flash the HTC image, then you do not reboot and flash the CyanogenROM. At this point you reboot. What happens? It should flash the radio, go to an HTC screen, stay for awhile, then reboot itself back to recovery where it gives a message regarding the cache being cleared. At this point you reboot for the actual boot process. Is this not happening for you?
cloverdale said:
He used that because it is the proper image to use. A defanged file simply means that it has been rendered safe to download with no fear of infection. The link on his site is to the file used by the OP, so no worries there. Also, your radio is good, so do not worry about that either.
I have to ask, because you did not mention part of the process that should be happening. You flash the HTC image, then you do not reboot and flash the CyanogenROM. At this point you reboot. What happens? It should flash the radio, go to an HTC screen, stay for awhile, then reboot itself back to recovery where it gives a message regarding the cache being cleared. At this point you reboot for the actual boot process. Is this not happening for you?
Click to expand...
Click to collapse
You are correct- after flashing CM the phone will flash the radio and reboot to the recovery screen where I will reboot again. Sorry for not including that detail.
Home process hanging in the beginning is not a problem, most people have that happenning. Eventhough home screen is shown, Android is still booting up, you just have to wait a little bit for everything to finish up.
Problems with stock apps usually indicate that something went wrong with instalation of the rom (i.e HTC 1.6 rom was not installed properly) so you may want to re-flash that again followed by CM rom of your choice.
Next time you phone reboots itself, try to get a log (there's more on how to do it in Cyan's thread), it's the only way to find out what happens.
Last, but not least, stock 1GB card is not advised for swap/apps2sd because if it's slow speed (it's class 2). Get one that's faster (class 6 preffered) and try that out, it may be the source of your problems after all.
Good luck.
how do i install this Cyanogen on my G1 with 1.6 firmware ?
simple007 said:
how do i install this Cyanogen on my G1 with 1.6 firmware ?
Click to expand...
Click to collapse
http://tinyurl.com/yjuy6u3
But in all seriousness
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod
This would work. Please use search, this is such a n00b question.
Did another fresh install, so far no issues.
I will get a log the next time I install to see if I can track down the issue.
Also had time to install Enoch 4.2.11.2 theme. <3 this theme.
I will be heading to Frys today to pick up some cooling fans for the old PC, I will take a look for new mini SD
thank you to everyone that responded.
Just got home from Frys Electronics.
Purchases an A-DATA 8GB Class 6 microSD.
wiping/flashing again.
I am having a hard time learning about the swap file part of all this... I can find guides on how to create a Swap Partition, but not sure how to make it work and/or optimize it.
So I created a 32MB Swap- Previously I read the commands to enable Swap through the terminal- "linux_swap_en=1" I have used this and it does indeed turn on swap, but is there some sort of command to optimize? I believe tweaking the swap files is adjusting the "swappiness"?
The other way I enabled the Swap file was from the spare parts menu- Enabling Compache enabled my Swap file. Does this need adjustment? for size? or any other parameters? Or is this kind of an auto on for Swap?
Sorry I am a total noob, and want to know if I am missing out, I just keep loving this phone more and more.
I will be buying Cyanogen some beer soon ^_^
I've played with swap a long time ago and never quite understood it neither. As of lately, I've been running 10mb hack (in the developement section) and it works great. If you're inclined to get the swap thing going I suggest you read this thread. This will give you an idea of how to enable and tweak swap-related tasks.
Glad to hear that you have original problems taken care of (so far at least).
Good luck.
I think I just may have bricked my phone...
I did all the steps stated in my first post while flashing to 4.2.12.2 and got things going great. Flashed Enoch's Theme 4.2.12.2. Everything was rocking.
Then today, it shut it self off, I rebooted. Got to Enoch load screen then shut off, tried it again, and it won't even get past the G1 splash screen. I have had this happen a few times before, where it would power off randomly and I had to pull the battery, wait like 5 minutes and then get into recovery and clear/flash again. Now I am getting into recovery but after a minute or so it just shuts itself off again.
Can't wipe, Can't flash, cant even get into Cam+power to flash back to previous RC...
Not really sure what to do at this point...
If I do manage to get it running again, I do wonder why its doing this.
I use Cachemate to clear my catche and task killer to kill apps. Could Cachemate be the culprit in this mess, its the only app that I own that uses root? Not sure what else to blame it on other than the G1 one being one big POS and is only good if you can even get a ROM to run on it. I am 5 minutes away from ordering a Nexus.
once again thanks in advance for any input you can provide.
D3AD PIX3L said:
I think I just may have bricked my phone...
I did all the steps stated in my first post while flashing to 4.2.12.2 and got things going great. Flashed Enoch's Theme 4.2.12.2. Everything was rocking.
Then today, it shut it self off, I rebooted. Got to Enoch load screen then shut off, tried it again, and it won't even get past the G1 splash screen. I have had this happen a few times before, where it would power off randomly and I had to pull the battery, wait like 5 minutes and then get into recovery and clear/flash again. Now I am getting into recovery but after a minute or so it just shuts itself off again.
Can't wipe, Can't flash, cant even get into Cam+power to flash back to previous RC...
Not really sure what to do at this point...
If I do manage to get it running again, I do wonder why its doing this.
I use Cachemate to clear my catche and task killer to kill apps. Could Cachemate be the culprit in this mess, its the only app that I own that uses root? Not sure what else to blame it on other than the G1 one being one big POS and is only good if you can even get a ROM to run on it. I am 5 minutes away from ordering a Nexus.
once again thanks in advance for any input you can provide.
Click to expand...
Click to collapse
This sounds like a hardware issue, and not a bricking. Try a new battery, this may fix it, otherwise I am not sure.
cloverdale said:
This sounds like a hardware issue, and not a bricking. Try a new battery, this may fix it, otherwise I am not sure.
Click to expand...
Click to collapse
I will try the other battery I have at home in my other G1 and report back
D3AD PIX3L said:
I will try the other battery I have at home in my other G1 and report back
Click to expand...
Click to collapse
I tried it.
Same issue.
I did noticed that the batter pins were abnormal... One was sticking out more which was normal according to my other G1, the other 2 were shoved down. I tried to mess with the 2 to get them to pop back up to their normal position with no luck.
I am thinking about ordering a replacement.
okay, so tonight I am going to take the G1 apart and see if I can get those pins straightened out. Not sure if it will help, but its better than declaring it a paper weight.
will post the outcome.
Just out of curiousity (and I don't exactly know where I'm going with this) will your phone turn on and stay on if you plug it in (usb or charger)?
borodin1 said:
Just out of curiousity (and I don't exactly know where I'm going with this) will your phone turn on and stay on if you plug it in (usb or charger)?
Click to expand...
Click to collapse
It does not.
I think i will take both phones apart and swap out the screen since that is why I don't use the one. I watched a visual walkthrough seems easy enough
Has anyone disassembled their G1 and reassembled successfully? any tips?
Started to take apart the non-cracked bricked G1.
Once I removed the motherboard and started on the next step, I realized how bad it would be to end up getting the parts swapped and then have it not work... Put it back together and loaded up the latest Cyanogen on my working cracked G1.
*shrugs* it will do for now.
Waiting till the end of next month to order my Nexus 1, then I will have fun ripping apart both G1's and hopefully end up with one great looking, fully functional G1 to possibly sell or keep as an extra phone...
thanks to all who replied!

[Q] nexus one cyan mod problem - big one for me

hey guys, new to rooting my device. always been heavy into customization and seen alot of work on here for cyanogen mod. so - went ahead and did the one click root. worked fine, checked with superuser permissions, and rom manager. downloaded cm 6.0.0 stable. "flashed" that rom onto my device, and it asked me to reboot to take effect. so hit reboot. and it is now stuck on the startup boot logo for cm6 with the blue android with the circle around the edge (im sure you all know what im on about) having a look about cant seem to see anybody else with this problem.
heres hoping somebody will help me out, hopefully make me look like a prat and tell me its something really simple and easy to do. beacuse im not liking my phone right now at all :/
Boot into recovery, wipe the device, then reflash the rom.
okay, after having a play i've got it to boot into cm6.0.0 with google addon, however it now says there is no internet connection. anybody?
wiggey1337 said:
hey guys, new to rooting my device. always been heavy into customization and seen alot of work on here for cyanogen mod. so - went ahead and did the one click root. worked fine, checked with superuser permissions, and rom manager. downloaded cm 6.0.0 stable. "flashed" that rom onto my device, and it asked me to reboot to take effect. so hit reboot. and it is now stuck on the startup boot logo for cm6 with the blue android with the circle around the edge (im sure you all know what im on about) having a look about cant seem to see anybody else with this problem.
heres hoping somebody will help me out, hopefully make me look like a prat and tell me its something really simple and easy to do. beacuse im not liking my phone right now at all :/
Click to expand...
Click to collapse
Stick to stock rom, CM6 kills your battery within a day, half a day if you are a heavy user. I am a lot into customization too but after moving to cm6 I moved back to stock within a week. I think your phone is hinting to you not to install cm6
i didnt know cm6 did that to be fair brother. however, that doesnt solve my problem at the moment. if i find i cant live with it, then ill reset back to stock or a different rom, but at the moment my main priority is to get access to my internet again for the time being whilst i look into different roms
Mine did the same thing. I just waited and within 5 to 10 minutes my phone started and I was able to use it.
Sent from my Nexus One using XDA App
wiggey1337 said:
okay, after having a play i've got it to boot into cm6.0.0 with google addon, however it now says there is no internet connection. anybody?
Click to expand...
Click to collapse
Have you inserted the appropriate APN settings? Are you talkin about 3G or WIFI?
Enter/select the correct APNs for your carrier.

After booting aospCMod 2.3.2

So for the past two days I've been trying to flash the new AOSP Gingerbread ROM, but although I follow everything straight from the wiki it always seems to get stuck on the HTC screen after the last reboot. Help me please!
EDIT: So I somehow got the rom to boot last night using RA recovery but after loading up a notice says Setup Wizard not being able to respond...etc, etc. Also after booting my home, call, and search buttons don't work at all. not even for other roms. PLEASE HELP!
020211 So after following instructions from this post: http://forum.xda-developers.com/showpost.php?p=11078749&postcount=4860 i was finally able to boot CM7 fully and without problems. If you're having problems with booting aosp's gingerbread rom just use this guy's instructions (at the bottom) and you should be good to go.
Make sure u install manually through clockworkmod mod first format boot system data and cache then install the rom let it boot then reboot and install gapps without wiping and reboot then you should be good I'm using the normal clockworkmod 2.5.2 and it works great
Sent from my HTC Hero CDMA using XDA App
okay thanks! ill try that and get back to you.
so no luck at booting. i'm still stuck at the HTC Boot screen.
i tried also and still no luck .. i hate this
to anybody having problems flashing GB, try these steps EXACTLY:
1) use clockwork 2.5.0.1 and follow the wipe/format process in the wiki
2) flash the rom then gapps
3) FLASH A CAPPED 691 KERNEL
This seems to be a continued issue, and I think it is because some phones can't handle high clock speeds like 768. The recovery currently posted by aosp (cwm 3.0.0.5) is overclocked and therefore will not boot, same with the kernel in the rom. Report back here if it works, I have already updated the wiki to advise people of this. Good Luck.
So i tried it again with the capped kernel and it still didn't work. also tried it without firerat's MOD but still a no go.
I'm upgrading aosp 2.3.2 rom from nightly build #188. Before flashing aosp rom plesae try to wipe everything like data, dalvik-cache, battery and rotate status. BTW, I'm using RA-Recovery not ClockworkMod.
i installed it after the standard wipes and thats it and its working just fine at 768 on my hero200. didnt have any issues and im loving the rom, but i am having one issue. this link is to my issue in q and a. if you can help feel free to hop on my thread and reply. other than that, i juast wanted to say this rom is great!
sai5o4 said:
So i tried it again with the capped kernel and it still didn't work. also tried it without firerat's MOD but still a no go.
Click to expand...
Click to collapse
Did you also flash a capped recovery?
sent from my hero, which no longer sucks ass
il Duce said:
Did you also flash a capped recovery?
sent from my hero, which no longer sucks ass
Click to expand...
Click to collapse
I agree with that. He should try a recovery that's not overclocked.
Root-Hack-Mod-Always™
Yeah I'm using clockwork 2.5.0.1.
sai5o4 said:
Yeah I'm using clockwork 2.5.0.1.
Click to expand...
Click to collapse
Well, I hate to say it but you must be missing a step somewhere. FYI in the OP for gingerbread the cwm3.0.0.5 is now capped at 691, so try that one again. Wipe both wipe options, go to mounts and format boot,system,data,cache, then gn into advanced wipe dalvik twice. Flash the rom,gapps,deca #43 capped 691 kernel, reboot. The first boot should take a while so be patient. Report back here if you can't get it, and I would recommend going into the live help room (aospbot IRC) which in the OP for GB. Good luck.
So still no luck. But I'm determined to somehow fix this no matter how many times I try!
Sent from my HERO200 using XDA App
sai5o4 said:
So still no luck. But I'm determined to somehow fix this no matter how many times I try!
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
I think you should back up your sd card and then format it in your pc. Then start all over. From the recovery on down. Skip any mods till you get booted up. Like keyboards and boot screens etc. And try the capped cwm recovery. Hope it helps good luck
Something.About.Me.You.Dont
Like.Its.Cool.I.Understand.AWAH
Still no luck on booting aospCMod. Like they say no two heroes are the same. But that doesn't mean I'm still not going to try again and again and again (xinfinity).
got it to boot but...
so i somehow got it to boot using ra-recovery but right as i loads it says the setup wizard has unexpetedly stopped processing. any help?
sai5o4 said:
020211 So after following instructions from this post: http://forum.xda-developers.com/showpost.php?p=11078749&postcount=4860 i was finally able to boot CM7 fully and without problems. If you're having problems with booting aosp's gingerbread rom just use this guy's instructions (at the bottom) and you should be good to go.
Click to expand...
Click to collapse
Glad I could help man! Glad to see you got it worked out!
There's a readme in the Aosp 2.3.2 OP. It's right under the files, labeled README. I think it would help if anyone having trouble actually reads through this. skipping steps causes problems.
also, Factory reset skips over the /system partition. I recommend wiping /system partition if you're coming from another rom, or if you are decided to start fresh. You have to go into the partitions menu to actually format the /system partition.
mtran2988 said:
You have to go into the partitions menu to actually format the /system partition.
Click to expand...
Click to collapse
This is true if you use CWM (which I do not ) but if you fastboot wipe all the partitions you will have no issues w/ RA as the OP discovered once he used the instructions that I posted.
touble with vvm
uh not quite sure if this is rite place to post this but looked better than the rest, so i got the rom running fine and it is wonderful improvement to my what use to be my wifes stock hero. Only problem is with the visual voice mail, i copied it from the stock hero before flashing, than after flashing copied it back, it works in the sense that i can see the voicemail in the app and even the voicemail to text works, but 2 things are wrong, 1 is i cant clear voicemail notification in the status bar without rebooting phone, and now she gets a text from a 9069 that tells her phone has recieved a voicemail, found a work around for the second one i blocked the number using blacklist so the text dont come thru nomore, but how i can i fix the fact that the only way to clear the voicemail notification is to reboot the phone? Any help, comments or suggestions would be greatly appreciated. Or is there somewhere i can dl the latest sprint vvm app?? or are they device specific. Thank you in advance for any help

[Q] CM 7.1 with all the goodies

I'm having a problem installing CM 7.1 and all the speed/memory tweaks. Ive used MANY different roms with alot of tweaks but this one i driving me crazy. Im trying to install CM 7.1 in CWR 2.5.0.7 with the following tweaks...Firerats 1.5.9 auto patcher and KERN 2.6.35.14-10sept-v1 .....the problem is that i can not get it to boot!!!! if i dont install firerats the rom doesnt boot and goes back to CWR...if i do install firerats the screen just hangs on the htc logo...but without the tweaks CM7.1 boots fine
Please help!!
I did the following with success (this is from memory, hopefully I don't miss anything), I'm using firerats 1.5.8. I did not use a single fr patcher.
First, I flashed the firerats REMOVE zip, just to make sure I was really starting over. then flashed the latest CWM unofficial recovery...5.0.2.6.
rebooted to recovery after each step above though, and repeated wipe data/factory reset, wipe cache.
for firerats, had the mdpartmap settings at 125, 20 (just being extra cautious there, I'm seeing some lower numbers bandied about).
Anyway, from the pretty blue recovery screen, I then flashed fr-recovery, (I think it tells you to reboot to recovery again when done, possibly wiping again, anyway, it tells you) then flashed cm 7.1, gapps, kernal, and finally, fr-boot.
Seems I've heard of folks having some difficulty if they don't use a newer recovery, perhaps others can chime in on this.
After some initial settling in and reboots (it was a little hot at first, a few things were a little flakey), everything seems to be running great. I've only had it on here a few days, and I have not tweaked any performance settings, but so far, gps has been rock solid (isn't this ALWAYS a sticky point for some?) and runkeeper has stopped being so crash happy. Need to see how these things behave with age. A clean installation fixes a lot of things for awhile.
Okay, fired up gps status app, and boom, reboot. But like I said, haven't tweaked any performance settings, left everything at defaults. Will tinker eventually.
wow!!! thank you so much for the very fast reply. I am at work at the minute but i am going to try this ASAP!! Thanks again.
I will keep you informed as to how this worked out. Looks like it should work though
Ok thats awesome!! i got it all to work but i can not get android market to work. I just get FC everytime.
Is there a fix for this?
verybigleen said:
Ok thats awesome!! i got it all to work but i can not get android market to work. I just get FC everytime.
Is there a fix for this?
Click to expand...
Click to collapse
Hmm, not sure, did you use the gapps from the OP for CM7.1? Could try redownloading that and flashing it again.
also, what were your firerat settings in the partmap file? Just checking, in case you didn't use mine, which were generous, as I said.
That rather larger second number in the partmap file resolves a lot of market issues, I never have to apply any "market fixes"
My fault. I used 125 2 in the mtd instead of 125 20....worked great!!! now i can use the market...thank you so much!!! just have ooooooonnnneeeeee other small problem.
Now by busybox wont work. Keep saying no root access when obviously i do...and also i can not fix permissions in rom manager..theres always a problem eh.
Hope you can help...you've been great so far!!! got loads more internal space now
Hrm...I have to admit to never using busybox, at least not directly, I usually just install it if asked when I install/update Titanium Backup (after checking the allow unknown sources in applications settings). Are you trying to execute busybox from terminal or something? Apologies if you tried this but if you have Titanium (you should if you don't), then do this:
Go to titanium backup, go to problems then it will install busybox
I just cut and pasted that from ... somewhere.
verybigleen said:
My fault. I used 125 2 in the mtd instead of 125 20....worked great!!! now i can use the market...thank you so much!!! just have ooooooonnnneeeeee other small problem.
Now by busybox wont work. Keep saying no root access when obviously i do...and also i can not fix permissions in rom manager..theres always a problem eh.
Hope you can help...you've been great so far!!! got loads more internal space now
Click to expand...
Click to collapse
So I finally figured it out. I downloaded the cm nightly instead of stable and everything worked great.
Thank you so much for your help!!!
Sent from my HERO200 using XDA App
Just wanted to say. Just installed the new cm nightly and the new jaybobs kernal ....amazing...the new kernal is super fast and every body should use it! Its the Oct 22 build..I'm flying now
Sent from my HERO200 using XDA App

Categories

Resources