Related
Hello everyone! Last night I spent about 3 hours installing the JACXHERO-v2.6.6 rom onto my Tmobile G1 using a method from unlockr.com (http://theunlockr.com/2009/08/22/how...g-best-method/). Unfortunately, it runs extremely slow right now.
For example, when i press home after sending a text message it goes to the HTC screen and simply sits there for about 30 seconds. At first I thought this was due to the weather widget updating but even when I took it off it still does this. Another thing is that it will sometimes take 10 seconds to switch screens when i slide my finger.
I know I am still new to this and realize there are some veterans on this forum that have a lot more experience with this. Can anyone please suggest to me what to do?
The bottom line is, all i want to do is run a stable and lag free (or fast) Rom.
Thanks guys!
i am taking a few liberties...
from the line, that you want a stable and fast rom, i assume you would like another rom besides hero. so download the latest stable rom off of cyanogen's thread.
after you download it and put it on your sdcard go into recovery then to the recovery console and type
Code:
mke2fs -j /dev/block/mmcblk0p2
that will format your ext3 partition.
now type in the recovery console
Code:
reboot recovery
once the phone boots up into recovery again, wipe the phone then flash the rom, then reboot when it is finished.
alright will do but i was wondering if you could give me a step by step instruction on how to do all this (like i said im very new to this sort of thing) =/ im sorrry
mrxkpex said:
alright will do but i was wondering if you could give me a step by step instruction on how to do all this (like i said im very new to this sort of thing) =/ im sorrry
Click to expand...
Click to collapse
i'm no rocket surgeon but here goes
download rom
place on root (no folders) of sdcard
power down phone
boot into recovery with home and power
scroll down to recovery console
enter command above to format ext3.
then type reboot recovery to boot back into recovery
select data wipe/factory reset
press home to confirm
now select flash any .zip (assuming you have cyanogen's 1.4 recovery image, if not, name rom to update in windows or update.zip for mac/linux prior to putting on phone, then select apply update.zip sdcard instead of any .zip)
hit home after selecting your rom (again 1.4 recovery)
when it is done flashing select reboot
happiness is yours.
yes you must wipe the phone and your ext3 partition since you are coming from hero to AOSP (cupcake/donut) (opposite applies as well).
mrxkpex said:
Hello everyone! Last night I spent about 3 hours installing the JACXHERO-v2.6.6 rom onto my Tmobile G1 using a method from unlockr.com (http://theunlockr.com/2009/08/22/how...g-best-method/). Unfortunately, it runs extremely slow right now.
For example, when i press home after sending a text message it goes to the HTC screen and simply sits there for about 30 seconds. At first I thought this was due to the weather widget updating but even when I took it off it still does this. Another thing is that it will sometimes take 10 seconds to switch screens when i slide my finger.
I know I am still new to this and realize there are some veterans on this forum that have a lot more experience with this. Can anyone please suggest to me what to do?
The bottom line is, all i want to do is run a stable and lag free (or fast) Rom.
Thanks guys!
Click to expand...
Click to collapse
dude youre using such and OLD OLD OLD hero rom... a rom thats is getting much hype nowadays is hero2 1.5.1
hero in its current stages arent lag free. no rom is lag free... you will experience some kind of lag always anyways.
brian_v3ntura said:
dude youre using such and OLD OLD OLD hero rom... a rom thats is getting much hype nowadays is hero2 1.5.1
hero in its current stages arent lag free. no rom is lag free... you will experience some kind of lag always anyways.
Click to expand...
Click to collapse
i still have jac 1.4 on my computer. i thought about flashing it once just to see how HUGE the improvement in hero roms has gotten
[ROM]JACxHEROSki-v2.1 - Experimental
...that's all I have to say.
SG_Shadow said:
[ROM]JACxHEROSki-v2.1 - Experimental
...that's all I have to say.
Click to expand...
Click to collapse
So are you saying Cyanogen's "experimental" builds aren't fast? If you were following the Hero scene closely you would know that every Hero build is "experimental," some just happen to be faster than others.
I recommend flashing one of the new ROMs such as Hero2 1.5.1, Modaco 2.2 (requires some tweaking to get flying), JACHEROSki 1.7r2(older but more stable/fast), or Drizzy's 1.4r1
NOTE: this is just my OPIONION
Cyanogens, is based on doughnut, so it looks the same as cupcake etc.. with custom enhancements (personally i think its fantastic)
The hero roms (in my experiance) its a case of reading the threads and trying a few to see what runs / works best for you
thanks a lot guys! it really helped! i have one quick question though
a lot of you have been recommending hero2 1.5.1 rom and i just watched a video on youtube for it where the guy was explaining how fast it was lol (and from the looks of it his seemed to have no lag when scrolling from left to right a bunch of times even with widgets)
my question is: is it really much faster and more stable? there are so many times where i'll be in my messages or something and i press the home key and theres a loading screen for like 30 seconds...i used the unlockr.com's method to partition my sd card to ext3 and what not
if i download and install the new hero rom, what are some suggestions on how to make it run faster?
people keep mentioning 96 mb partition or something like that and i have no idea what there talking about or how to do it
also, just in case i want to go back to the original os that came with the phone, how do i do it?
try moving the cache that is the first thing to do with hero there is a lot of maintence that go along with hero
i have had my ATT N1 for a few months now and all has been great. I rooted awhile back and have been using Cyanogen 5.0.7 to great success. I have the pershoot kernal and never really had any issues.
Well, that has all changed. Recently I have been rebooting any many different occasions. It almost always does it when I am in Maps and navigation, which is not good because I need it in my life having relocated.
I have decided that maybe I will look to update my Cyanogen or maybe go over to 2.2. I did this today and still having these issues. I tried Kang and it still rebooted randomly and when I tried Modacos r17 it just would keep rebooting at the setup screen. I think that has to do with not having the stock kernal.
Any clues as to what is happening? I really need help and do not want to stop using Android, but I need my phone to be reliable.
If it happens on any ROM and with no correlation to anything - sounds like HW problem.
Did you use overclocked kernel?
I do have a overclocked under volted kernal
sounds like bad sw. get back to stock 2.1 update 1 (if you can) and see if your phone is stable...
WIPE all ( everything ) , and flash 2.2
http://forum.xda-developers.com/showthread.php?t=692609
Follow those 3 easy steps there !
Does your phone lock up (unresponsive) before rebooting?
Phone doesnt lock up. I tried wiping evertyhing but could not wipe the sd partition. Is that necessary? I have done full wipe's (data, dalvik, & cache) and still had similar results. I have updated my kernal to the newest pershoot and I installed Kang .9b1 and so far have only had 1 rebbot. It happened when I was in the browser and went to a flash heavy site to see how it worked. Is there any 2.2 roms that keep it close to stock? I am not a total fan of adw launcher.
Have a look in this thread,
http://forum.xda-developers.com/showthread.php?t=703687
I'm really determined to figure out what is causing this issue for so many people! I've managed to cure my reboots for the time being, and it seems it is kernel related. That said, we need as many people as possible to give feedback as experiences seem to differ in regards to the ROMs and Kernels people are using.
Regards.
I looked over that thread and see some similarities but it is still not totally consistent with my issues. I am running Kang now fine but still have reboots that I won't call so random anymore. It happens when I use Maps for the first time, and definitely when I go to a flash site on the browser.
I cannot successfully use any other ROM since once I install it it goes into boot loop. This is driving me crazy and do not like the thought of being stuck to one ROM since it is the complete reason I bought this phone.
Hey guys, I'm having a problem
Sorry if I'm posting this in a wrong area
Well, I'm using CyanogenMod 7.2.0 stable by Kabaldan for Milestone A853. Then I tried to install CyanogenMod 9 Nightly (from Skrilax build bot), the latest version. Everything was going well, then when I tried to boot, a screen about "Android is updating applications" appeared, and then after updating, the phone hard rebooted, back to the M logo. Then I left it booting again, and it rebooted again, though this time the update screen didn't appeared. Sometimes I get the first screen to appear, but I can't even touch the phone because it reboots before I try to do so. I tried installing CyanogenMod 10 (Skrilax nightly build bot again) and the same error happened! What is happening to my phone? I've never found anyone with this problem
Please help me! Thanks.
Did you perform a full wipe before applying CM9/10?
Eiertschik said:
Did you perform a full wipe before applying CM9/10?
Click to expand...
Click to collapse
If by full wipe you mean the three wipe options in OpenRecovery (Dalvik, Data and Cache) then yes. I even deleted the /system folder and nothing!
UPDATE: I tried to install CM10, removed system, data and cache through ADB and dalvik cache, installed CM10 and gapps. When booting, the first screen asking for language rapidly appears, and reboots. I tried to boot again, then I rapidly touched the screen when the screen appeared, and it didn't reboot! Well, that's better, but CM10 is too lagged for daily use, that's why I want to install CM9!
I'm using CM10 from couple of days..
I get enough RAM to run apps that I daily use...check for unwanted apps that are not being used, disable it through hwa setting app. Just use it for a day .. IMO CM10 is better than CM9.
BTW I removed gtalk, maps, email, exchange service and other unwanted apps from OR...which I don't use at all..
Sent from my Milestone using xda app-developers app
Hell Angel 1910 said:
Hey guys, I'm having a problem
Sorry if I'm posting this in a wrong area
Well, I'm using CyanogenMod 7.2.0 stable by Kabaldan for Milestone A853. Then I tried to install CyanogenMod 9 Nightly (from Skrilax build bot), the latest version. Everything was going well, then when I tried to boot, a screen about "Android is updating applications" appeared, and then after updating, the phone hard rebooted, back to the M logo. Then I left it booting again, and it rebooted again, though this time the update screen didn't appeared. Sometimes I get the first screen to appear, but I can't even touch the phone because it reboots before I try to do so. I tried installing CyanogenMod 10 (Skrilax nightly build bot again) and the same error happened! What is happening to my phone? I've never found anyone with this problem
Please help me! Thanks.
Click to expand...
Click to collapse
If nothing solves your problem, you should reflash the SBFs and start all over again. I had to do this sometimes. Formatting the SDCard (after backing-up your personal data) also helps to prevent this from ocurring.
Well, never mind, I was robbed saturday. Thanks for the help folks
Sad! But it's a chance to get a better phone. Good luck!
Tiago Costa said:
Sad! But it's a chance to get a better phone. Good luck!
Click to expand...
Click to collapse
Really sorry to know that you have said goodbye to your great milstone... Anyway, I'd like to share what I did when I was in your situation:
- Flash the stock ROM to come back to stock 2.1
- Erase and format SD card
- Partion the SD card angain
- Root the fone and flash to the latest CM10
And now, my stone works like a charm and I have not yet to have idea to change to a new phone now :victory:
Just for sharing!
justforlove said:
Really sorry to know that you have said goodbye to your great milstone... Anyway, I'd like to share what I did when I was in your situation:
- Flash the stock ROM to come back to stock 2.1
- Erase and format SD card
- Partion the SD card angain
- Root the fone and flash to the latest CM10
And now, my stone works like a charm and I have not yet to have idea to change to a new phone now :victory:
Just for sharing!
Click to expand...
Click to collapse
and BPSW for 2.1.1 is needed? or optional?
It's optional.
You only have to wipe data,dalvik-cache and data (you will lose all your information, so backup everything) and to create an ext partition on your sdcard.
Erovia said:
It's optional.
You only have to wipe data,dalvik-cache and data (you will lose all your information, so backup everything) and to create an ext partition on your sdcard.
Click to expand...
Click to collapse
yeah I know, I read the dev thread but can't make replies there. I am now on CM10 from 09/24 (last 4.1.1) and considering about CM10 4.2 but I was little bit confused about BPSW. And will there be problem If I will uprgade from 2.2? Because I don't have nandroid backup of 2.1
(FYI, the current CM10 is based on Android 4.1.2.
4.2 will be the next version of Android and probably CM11 will be based on it.)
Anyway, i upgraded from 2.2 to 4.0.4 and then to 4.1.1 and now 4.1.2.
I believe you can upgrade from 2.2 to 4.1.2 without any problem.
(but always make a nandroid before upgrading)
Yes, it's perfectly possible upgrade from 2.2 Stock ROM, although it's more difficult to root it.
I did it without any problems.
Is there any difference between upgrading from 2.1 or from 2.2?
Erovia said:
(FYI, the current CM10 is based on Android 4.1.2.
4.2 will be the next version of Android and probably CM11 will be based on it.)
Anyway, i upgraded from 2.2 to 4.0.4 and then to 4.1.1 and now 4.1.2.
I believe you can upgrade from 2.2 to 4.1.2 without any problem.
(but always make a nandroid before upgrading)
Click to expand...
Click to collapse
Yeah, sorry for that mistake, my fault. I upgraded from 2.2 to 4.0.4 and now I have 4.1.1. I tried to upgrade to 4.1.2 from 4.1.1 but it was laggy (10/16 and 10/17) so I restore it back to 4.1.1 which is pretty stable and I will wait to better time for this upgrade, because it is my main phone and my boss is upset when I am not available when he calls me
Tiago Costa said:
Yes, it's perfectly possible upgrade from 2.2 Stock ROM, although it's more difficult to root it.
I did it without any problems.
Is there any difference between upgrading from 2.1 or from 2.2?
Click to expand...
Click to collapse
I've read somewhere, that one must upgrade to 2.2 because upgrading from 2.1 will cause problem with some hardware module.
zemko said:
Yeah, sorry for that mistake, my fault. I upgraded from 2.2 to 4.0.4 and now I have 4.1.1. I tried to upgrade to 4.1.2 from 4.1.1 but it was laggy (10/16 and 10/17) so I restore it back to 4.1.1 which is pretty stable and I will wait to better time for this upgrade, because it is my main phone and my boss is upset when I am not available when he calls me
Click to expand...
Click to collapse
Kabaldan is working on it. It seems, if the CPU's clockspeed is under 600MHz, then something is wrong with the GPU performance. (So you should consider using Performance CPU governor.)
Erovia said:
Kabaldan is working on it. It seems, if the CPU's clockspeed is under 600MHz, then something is wrong with the GPU performance. (So you should consider using Performance CPU governor.)
Click to expand...
Click to collapse
I know that someone wrote it in dev thread for CM9 or CM10, but my battery is pretty weak, I am glad that with Juice defender it lasts for 12 hours and Performance governor is pretty aggressive to battery drain. Anyway thanks for answering my nooby questions
Hi guys, I have done research on this but seem to get very different responses, I wanted to flash my cappy to Cyanogenmon 10.1 nightly (jellybean 4.2.2) but now I'm not sure, I've flashed it for testing for an hour before going back to stock, the problems I had is that boot times seemed to be a LOT longer and after I restored my messages with Titanium Backup the messaging app force closed as soon as I open a conversation. I also met a guy when buying resistors (to make a jig lol) and he said that when he had cyanogenmod his battery went down twice as fast and his apps started force closing (but I don't know when that was and if the mod is more stable now).
So, I really need some advise and want to know the pros and cons of the mod, also would be nice to know how I can backup and restore my messages without FC's, also how can I get the samsung apps that came with the phone to cyanogen mod (and would restoring data from a nandroid backup restore all my apps?).
Thanks in advance,
Nik
You have many more options, not only CM10.1 (still in experimental stage) and stock. What firmware you'll chose is your personal preference. Take a look at Captivate Android Development section. Notice how many downloads most popular ROMs have. Do you think those thousands of people fight every day with stability issues and FC? Me personally, I'll never go back to stock. After trying many different ROMs I found what I'm looking for and my phone is now faster (including boot time), stable (I don't remember last FC) and can do way more compared to stock. My battery life with JB is actually better than stock GB. And yes, you can have Samsung apps. For me this bloatware was one of the first things to remove after rooting stock GB. My very first ROM to flash was CM10 stable. Never had any issues with it. Most of the problems are user created (corrupted flash files, incorrect flash sequence, missed reset/format steps, incorrect system data restore from previous Android versions, etc). And you don't need a jig to enter download mode. I never had one, had my phone soft bricked twice, flashed it countless times with Odin and through CWM... and it's still alive. Read carefully all the tutorials and troubleshooting guides.
Val D. said:
You have many more options, not only CM10.1 (still in experimental stage) and stock. What firmware you'll chose is your personal preference. Take a look at Captivate Android Development section. Notice how many downloads most popular ROMs have. Do you think those thousands of people fight every day with stability issues and FC? Me personally, I'll never go back to stock. After trying many different ROMs I found what I'm looking for and my phone is now faster (including boot time), stable (I don't remember last FC) and can do way more compared to stock. My battery life with JB is actually better than stock GB. And yes, you can have Samsung apps. For me this bloatware was one of the first things to remove after rooting stock GB. My very first ROM to flash was CM10 stable. Never had any issues with it. Most of the problems are user created (corrupted flash files, incorrect flash sequence, missed reset/format steps, incorrect system data restore from previous Android versions, etc). And you don't need a jig to enter download mode. I never had one, had my phone soft bricked twice, flashed it countless times with Odin and through CWM... and it's still alive. Read carefully all the tutorials and troubleshooting guides.
Click to expand...
Click to collapse
WOW Thanks for such a detailed reply, the reason I needed a jig is that odin froze during flashing and I got bricked (the brick screen didn't work as download mode in this case). I'll have a look at other ROMs, may I ask what ROM you went with at the end?
Thanks,
Nik
10.1 is fine and stable. messaging is a system app, so don't try to restore it, but restoring only the data should work.
after flashing, you can expect the rom to have a long boot the first time, and to be pretty laggy for as long as 10 minutes. later boots will be quicker. I also use an app, system tuner, to prevent a number of apps from loading at startup.
I stayed with cm10.1, after trying a few other roms. for me cm10.1 is fav.
nosurlife said:
I'll have a look at other ROMs, may I ask what ROM you went with at the end?
Click to expand...
Click to collapse
Yes, but it's gonna cost you $10 per every flash/testing I did for you. And the total is a lot of money... :laugh:
Read your PM -> Info what I use + links where to find it on XDA. But again, first read carefully all tutorials and flash instructions.
laughingT said:
10.1 is fine and stable. messaging is a system app, so don't try to restore it, but restoring only the data should work.
after flashing, you can expect the rom to have a long boot the first time, and to be pretty laggy for as long as 10 minutes. later boots will be quicker. I also use an app, system tuner, to prevent a number of apps from loading at startup.
I stayed with cm10.1, after trying a few other roms. for me cm10.1 is fav.
Click to expand...
Click to collapse
Thanks, I'll look into it.
Val D. said:
Yes, but it's gonna cost you $10 per every flash/testing I did for you. And the total is a lot of money... :laugh:
Read your PM -> Info what I use + links where to find it on XDA. But again, first read carefully all tutorials and flash instructions.
Click to expand...
Click to collapse
I wish I could spam the thanks button multiple times haha, I'll go check out the ROMs, so there's no way to keep my txts?
And is there any difference in RAM usage between stock and other ROMs?
Thanks,
Nik
nosurlife said:
Thanks, I'll look into it.
I wish I could spam the thanks button multiple times haha, I'll go check out the ROMs, so there's no way to keep my txts?
And is there any difference in RAM usage between stock and other ROMs?
Thanks,
Nik
Click to expand...
Click to collapse
You can backup your texts with a app like Titanium Backup.
BWolf56 said:
You can backup your texts with a app like Titanium Backup.
Click to expand...
Click to collapse
I did that but now the messaging app has the conversations when I open it but when I try to open a conversation it FCs,
What can I do now?
nosurlife said:
I did that but now the messaging app has the conversations when I open it but when I try to open a conversation it FCs,
What can I do now?
Click to expand...
Click to collapse
Ok fixed it, did a reset and restored with SMS Backup & Restore now no FCs.
Thanks to everyone I am now happily running Slim Bean release 3 (4.2.2).
CyanogenMod 10.1 taking more RAM
BWolf56 said:
You can backup your texts with a app like Titanium Backup.
Click to expand...
Click to collapse
Hi,
I have flashed my cappy with CM 10.1 Nightly(JB 4.2.2), but now it seems this is using more RAM. already in captivate we have only 512 MB RAM and it uses about 322 MB of it. Is there any solution for this ?? or will flashing some other rom will help ?
mangaicaptivate said:
Hi,
I have flashed my cappy with CM 10.1 Nightly(JB 4.2.2), but now it seems this is using more RAM. already in captivate we have only 512 MB RAM and it uses about 322 MB of it. Is there any solution for this ?? or will flashing some other rom will help ?
Click to expand...
Click to collapse
That's normal.
As long as your phone runs fast and smooth, don't worry about your RAM. Also, if you have bunch of apps running in the background, stopping them will lower your RAM consumption.
BWolf56 said:
That's normal.
As long as your phone runs fast and smooth, don't worry about your RAM. Also, if you have bunch of apps running in the background, stopping them will lower your RAM consumption.
Click to expand...
Click to collapse
Aww I was going to say that haha, the main thing to watch is CPU as RAM is managed differently on android from a PC.
Another thing I noticed is that having a lot of widgets can cause a bit of lag too.
RE: RAM usage
mangaicaptivate said:
I have flashed my cappy with CM 10.1 Nightly(JB 4.2.2), but now it seems this is using more RAM. already in captivate we have only 512 MB RAM and it uses about 322 MB of it. Is there any solution for this ?? or will flashing some other rom will help ?
Click to expand...
Click to collapse
As laughingT suggested, try an app like System Tuner to try to get startup apps under control. Greenify is another app to try before jumping ROMs. You can also go into Settings->Apps and Disable apps you do not use (personally I disable Gmail among others, seems to help battery life too). Additionally, alternate kernels may give you more usable RAM.
Edit: oops, missed the second page of posts... great responses to this question already
Just to confirm - uninstall/freeze apps you don't use (careful with system apps, some are required for the OS to run properly) but don't install any memory managers or task killers, especially auto task killers. They will only make things worse (slow). Android with full memory runs faster and smoother. Also, don't clear app cache for no reason.
After I bought the phone in 2010, it took me 6 months to build up the nerve to root. Then 2 weeks after that to start flashing.
I went back to stock GB rom at one point and gave up - from my experience,GB is the least stable of the Android versions, bloats the easiest and is overall a lousy system. It;s the armpit of Android, really.
At one point last summer I gave up on Captivate and started using an old iPhone gifted from a friend. At that point the Cappy has 3 hour batter life, nothing worked, and absolutely nothing worked stably - I thought Android was done for, but I was wrong. After about 3 months with the iPhone, I woke up the Cappy, took her back to stock (and I am talking Eclair here) and then forward to CM10. I never looked back. I am currently on yesterday's nightly CM10.1. CM10 Stable was buttery smooth and with no problems at all, but now I am hungry for the new features, so I update the CM10.1 builds about once a week.
This is not to say other builds are not as good. CM is the ROM that revived my Cappy. I am happy with it, it works and is consistently developed with high quality control. I have no reason to switch. But there are many other fantastic-looking roms out there. The Experia roms, the PAC man roms .. they seem to have unique feature sets and stable code.
What I am saying, is that DO NOT stick to stock. And although CM is a great choice, there are many, many options out there .
PS: I have soft-bricked my phone a lot of times. After the first couple times, you will a) learn the value of backing up your data before doing anything, and b) you will have all the files/programs on your computer to revive your phone with a few well-rehearsed steps. (having a backup phone also does not hurt - for a long time I carried the iPhone with me - worried the cappy would crap out on me. I finally stopped worrying)
Best of luck.
dozyaustin said:
After I bought the phone in 2010, it took me 6 months to build up the nerve to root. Then 2 weeks after that to start flashing.
I went back to stock GB rom at one point and gave up - from my experience,GB is the least stable of the Android versions, bloats the easiest and is overall a lousy system. It;s the armpit of Android, really.
At one point last summer I gave up on Captivate and started using an old iPhone gifted from a friend. At that point the Cappy has 3 hour batter life, nothing worked, and absolutely nothing worked stably - I thought Android was done for, but I was wrong. After about 3 months with the iPhone, I woke up the Cappy, took her back to stock (and I am talking Eclair here) and then forward to CM10. I never looked back. I am currently on yesterday's nightly CM10.1. CM10 Stable was buttery smooth and with no problems at all, but now I am hungry for the new features, so I update the CM10.1 builds about once a week.
This is not to say other builds are not as good. CM is the ROM that revived my Cappy. I am happy with it, it works and is consistently developed with high quality control. I have no reason to switch. But there are many other fantastic-looking roms out there. The Experia roms, the PAC man roms .. they seem to have unique feature sets and stable code.
What I am saying, is that DO NOT stick to stock. And although CM is a great choice, there are many, many options out there .
PS: I have soft-bricked my phone a lot of times. After the first couple times, you will a) learn the value of backing up your data before doing anything, and b) you will have all the files/programs on your computer to revive your phone with a few well-rehearsed steps. (having a backup phone also does not hurt - for a long time I carried the iPhone with me - worried the cappy would crap out on me. I finally stopped worrying)
Best of luck.
Click to expand...
Click to collapse
Yep, I'm never going back to stock I'm running slim bean (based on CM) android 4.2.2 and really enjoying all the features, the phone is so much smoother and looks much more professional then GB (no offense google lol).
Thanks,
Nik
Hi guys, I have an old G1 at home that I've been using as a time killer, to play chess and some music. I want to try changing the ROM on it, because I have some problems with it, but i'm not sure where to begin. I'll give a quick rundown of the phone's problems and what I'm trying to do. This is an old machine I bought for my dad awhile ago. It's not been used for some time and I wanna to do something with it. It has a lot of problems which I don't understand. For example I cannot connect to google nor through a data plan on a simcard or through Wifi. I've seen threads having some tips on this but none helped. Same problem with some applications - facebook, teamviewer and so on. They just won't connect, although wifi works fine with the browser, so I don't know what going on. There are other problems as well and I think it's running slower than it should because it won't even manage to do stuff a generic G1 should - videos have to be heavily converted to even run - trying any video player is useless - it'll lag as hell. I have to convert to a specific audio and video format with lowered fps, then it runs ok, but still only using the generic video player. Anything else will just become a comic book.
Anyway - this is a phone I got off eBay and it already came rooted and with the Super D rom loaded (kernel 2.6.29.6-SuperD) So because all the problems I want to reflash it completely to try find out, whether it's all hardware related or the rom's unstable... Now, because it is already rooted and I'm new to this, I don't know where to start.
I have looked through a few rooting/flashing guides, but my problems is: I don't know whether I need to do it all, or can skip a few steps, because it being rooted already. For example whether I need to downgrade anything again, or not before going on. My first important question is, is there a point in flashing anything higher than android 1.6? As the phone is very limited with it's resources, I'm not sure, whether for example flashing the 2.2 froyo CM rom will do any good. Secondly: there are several different guides out there and I don't know which one is good for me. I believe I tried the one click thing once, but it didn't work then, but not sure what was the problem. I presume it is because I either didn't have to do all of it, or I didn't do something else I was supposed to.
So all in all, if someone could point me to a good guide, that would take in account the option, that it already is rooted and I just need to change the Rom, it would be greatly appreciated.
Magicnet2 said:
Hi guys, I have an old G1 at home that I've been using as a time killer, to play chess and some music. I want to try changing the ROM on it, because I have some problems with it, but i'm not sure where to begin. I'll give a quick rundown of the phone's problems and what I'm trying to do. This is an old machine I bought for my dad awhile ago. It's not been used for some time and I wanna to do something with it. It has a lot of problems which I don't understand. For example I cannot connect to google nor through a data plan on a simcard or through Wifi. I've seen threads having some tips on this but none helped. Same problem with some applications - facebook, teamviewer and so on. They just won't connect, although wifi works fine with the browser, so I don't know what going on. There are other problems as well and I think it's running slower than it should because it won't even manage to do stuff a generic G1 should - videos have to be heavily converted to even run - trying any video player is useless - it'll lag as hell. I have to convert to a specific audio and video format with lowered fps, then it runs ok, but still only using the generic video player. Anything else will just become a comic book.
Anyway - this is a phone I got off eBay and it already came rooted and with the Super D rom loaded (kernel 2.6.29.6-SuperD) So because all the problems I want to reflash it completely to try find out, whether it's all hardware related or the rom's unstable... Now, because it is already rooted and I'm new to this, I don't know where to start.
I have looked through a few rooting/flashing guides, but my problems is: I don't know whether I need to do it all, or can skip a few steps, because it being rooted already. For example whether I need to downgrade anything again, or not before going on. My first important question is, is there a point in flashing anything higher than android 1.6? As the phone is very limited with it's resources, I'm not sure, whether for example flashing the 2.2 froyo CM rom will do any good. Secondly: there are several different guides out there and I don't know which one is good for me. I believe I tried the one click thing once, but it didn't work then, but not sure what was the problem. I presume it is because I either didn't have to do all of it, or I didn't do something else I was supposed to.
So all in all, if someone could point me to a good guide, that would take in account the option, that it already is rooted and I just need to change the Rom, it would be greatly appreciated.
Click to expand...
Click to collapse
First thing I would do is just factory reset it through recovery (power on while holding home) and see if all works after this. Super d is for sure one of my favorite donut ROMs and it shouldn't be having the issues you have.
If that does little or nothing than write down all info from bootloader (power on while holding camera) here and the version of recovery you have (written in recovery screen)
Sent from my Nexus 7 using Tapatalk 2
Hi. Thanks for the quick reply. I've already reset it multiple times, but it didn't change anything. What most angers me, is the Wifi issue (because I know my dad has been using his dataplan and it worked fine and when I tried it later, it just didn't work anymore) and the video thing.
As for the info:
Hboot-1.33.2005 (Drea11000)
Clpd-4
Radio-2.22.23.02
Recovery is ClockworkMod Recovery 2.5.0.7
Magicnet2 said:
Hi. Thanks for the quick reply. I've already reset it multiple times, but it didn't change anything. What most angers me, is the Wifi issue (because I know my dad has been using his dataplan and it worked fine and when I tried it later, it just didn't work anymore) and the video thing.
As for the info:
Hboot-1.33.2005 (Drea11000)
Clpd-4
Radio-2.22.23.02
Recovery is ClockworkMod Recovery 2.5.0.7
Click to expand...
Click to collapse
Yes it is strange, try finding a ROM called donut by Laszlo, search is down right now but it should be within the first five pages or so in developers thread. Put on sdcard along with this
http://www.androidfilehost.com/?fid=23212708291678371
First flash super wipe in recovery and then flash new ROM
If it all does not work still we will go from there
Sent from my Nexus 7 using Tapatalk 2
Right, so I've got some new info on this. I wanted to go reflash, but just for the sake of it, I re-wiped though recovery and nothing changed. then on the second time, the market suddeny started working through wifi, which it has not for the past few months, even after 3 or 4 wipes. So it started working, but the signal kept failing. It found the first application, downloaded, installed, then "network problem" so I reflashed using the files you mentioned. It worked beautifully on the first fly, for which I am grateful. This was my main concern - I had no idea, whether I needed to change the radio or bootloader or anything prior to trying to flash the rom. So the rom works nice, the market and facebook and teamviewer do connect now using wifi, but I keep loosing the signal. Better said - he stays connected to wifi, just that the applications keep throwing network errors and loose connection. So I presume, it will be either hardware related, or I was wondering, if a change of radio might help... Secondly, I keep getting one more problem I had with the old Rom and that is - when using ES File explorer, when I close by pushing the back button, it closes and then an error says it stopped working and needs force closing. Wondering how this kind of error can transfer between different Roms. Again - posibly hardware related? I don't know.
Anyway, the rom works nice, so I'll try it out and see if it's better than the previous one. One question though - when flashing to a different Rom, do all of them have specific requirements for radio and bootloader and recovery and so on, or is the setup I have ok for flashing anything, that is suited for the G1?
EDIT: One more thing I just remembered. The Superwipe, as I read the description, was supposed to wipe everything + the SD card as well. First of all I noticed that it took just about a second or two, which I thought was a bit too quick, but the SD card was not wiped at all, so I'm thinking, that theoretically there could be a file on there, that causes the problems, that have transfered from Rom to Rom, as it was not wiped at all. I'll reformat the SD card, superwipe it, reflash the Rom and see what will happen. Will post the results first thing tomorrow.
It only wipes ext partition not fat32
Only newer ROMs will require a different bootloader/radio, which also will give you more ram so it is preferred. See ezterrys post on the 2708+ update or read the through the thread below this on where I discussed the benefits of upgrading with another dream user
Sent from my Nexus 4 using XDA Premium 4 mobile app
Right, so from what I see from the other thread of yours, CM5 should be a good Rom to try. I will definitely wanna go there, cause while the current Rom seems a bit better than the Super D, it seems it uses up more memory - can't install as many apps as before and I'm keeping it pretty low on apps. And I definitely want to see, whether it will improve any of the lingering problems I've been having, or whether it'll be worse. So judging by what you told the other guy, I already have the right bootloader as I have the 2005 with fastboot enabled, but I'll have to update the radio. Here's what I'm not sure and that is, which to choose. Should I stay with the current SPL and get the same radio the other guy had (RADIO-2.22.19.26i) or should I go straight for the 13d SPL with radio-2.22.27.08? I would say, for now would be safer to stay with current SPL, update the radio and then flash Rom + Gapps and see what it does. Plus if I remember right, you said that to get the ramhack I need the 13d spl, which doesn't support fastboot...
You got it all, well you don't need to change radios, the one he has is a Europe version, yours is more us. Both work fine for cupcake, donut and eclair ROMs. You can try out the other if you were getting poor reception but not needed
Cm5 will work fine for you as of now, just full make a backup, wipe, superwipe, fastboot -w whatever, then flash ROM, then gapps then reboot
The ram hack is awesome but so is learning fastboot. I do recommend you at some point upgrade to the .13d SPL but I think its a good idea to flash a few things first and be comfortable before doing so. If you have issues having fastboot is helpful in fixing things
Sent from my Nexus 4 using XDA Premium 4 mobile app
Ok. So what I did is partition the SD card using the nice "Mini tool partition wizard" and went for a 250 MB ext4, made a backup, left the radio be so far, wiped, flashed the CM5 and Gapps and I have to say I'm impressed at how swift the Rom works. It appears to be generally faster than both the SuperD and Laszlo Donut Roms. I have been testing it only a short while yet, but the wifi, although it shows constantly weak signal (one or two lines), it hadn't lost connection yet, which gives me hope and the apps2ext seems to work perfectly right away. At least I'm able to move them around and it installs straight there, without any failure so far and the apps work so thumbs up.
This deserves a big thanks to you for the supplied info. Before I wrote this thread, I was about to try one of the long guides - which would take me through downgrading and everything - you saved me a lot of stress man I'll play around with this and will try going for the ram hack a bit later. I'll let you know any bugs I notice...
P.S.: You were right to suggest getting familiar with fastboot and adb - it's a great thing and it's good to know I've got it set up and running fine.