Related
Hi,
Thanks to thiagodark I've finally rooted my phone (Got it in Feb)
Now for step 2 ... Flashing Roms
Can some one suggest where I start? I see that the [ROM] [Nightly] CyanogenMod 7 (alpha) is pretty popular ... would that be a recommended start?
Two things I look to after flashing a rom would be a) install BLN (so, the rom has to have support for that) and b) should have the power widget in the notification (where I can pull down notification and toggle wifi, sound, bluetooth or whatever). Would also prefer if the a 2.3.4 Rom.
Two other things I'd like to know and would really appreciate help with are:
a) Can I flash a rom and then install any kernel ... are they all compatible?
b) I did a Google Search and found these steps to Flash a Rom:
Flash a Custom ROM
1. Head over to our Nexus S ROMs section, choose a ROM you want and download it and save it to your computer.
2. Plug your phone in and mount the internal storage so we can transfer files to it.
3. Copy the ROM .zip file over to the root of the internal storage (NOT in any folders, just on the internal storage itself).
4. Turn off the phone.
5. Turn the phone on by holding down Volume Up and Power until Fastboot mode comes up.
6. Scroll down and select Recovery and wait for the phone to reboot into recovery mode.
7. Once in recovery mode, scroll to Backup, then select Backup and wait for the phone to backup its current ROM.
8. Once it is done, select Wipe Data
9. Then select Flash zip from SD Card
10. Select choose zip from sd card.
11. Select the ROM’s zip file you loaded onto the internal storage earlier and wait for it to flash. Done!
12. Repeat to load a different ROM.
Click to expand...
Click to collapse
My question is .... Is step 7 what is called a Nandroid? And do I need to do this every time or do I just need to do it when I think that the current setup is good enough to back up? ... yes, I will do it the first time and then only when I think I like a Rom, but want to try another and may revert.
Thanks a ton
Paparasee said:
Hi,
Thanks to thiagodark I've finally rooted my phone (Got it in Feb)
Now for step 2 ... Flashing Roms
Can some one suggest where I start? I see that the [ROM] [Nightly] CyanogenMod 7 (alpha) is pretty popular ... would that be a recommended start?
Two things I look to after flashing a rom would be a) install BLN (so, the rom has to have support for that) and b) should have the power widget in the notification (where I can pull down notification and toggle wifi, sound, bluetooth or whatever). Would also prefer if the a 2.3.4 Rom.
Two other things I'd like to know and would really appreciate help with are:
a) Can I flash a rom and then install any kernel ... are they all compatible?
b) I did a Google Search and found these steps to Flash a Rom:
My question is .... Is step 7 what is called a Nandroid? And do I need to do this every time or do I just need to do it when I think that the current setup is good enough to back up? ... yes, I will do it the first time and then only when I think I like a Rom, but want to try another and may revert.
Thanks a ton
Click to expand...
Click to collapse
First you will want to do is download ROM manager onto your phone, then flash the latest Recovery from within it.
Then you should do a Nandroid (this is the backup option in recovery... do this while everything is stock) this backsup your whole phone (apart from SD card) so if you screw something up you can restore it! It is real useful, you can nandroid as much as you like, all it is is an image of your phone.
If you are just starting out i would avoid the CM nightlies and find the stable thread which is 7.0.3. That coupled with Netarchys latest kernel (includes BLN) really works wonders.
As far as the actuall flashing, all you need to do is copy both zip files onto your sd card, reboot into the recovery (you can do that from within the ROM manager).
Once in the Recovery, wipe data,cache and dalvik, then select flash from zip and choose the rom.
Wipre cache and dalvik again and then flash the kernel and restart the phone.
Thats it you should be good to go. If you ever get any Force Closes restart into recovery again and run the Fix permissions
Happy flashing
Edit
Compatibility wise, CM 7.0.3 is still android 2.3.3 (will be updated to 2.3.4 with cm7.1) so you need a 2.3.3 kernel. You also need to know if your phone is NS3G or NS4G, they are not compatible
Thanks bringonblink ... guess I'm starting to get an understanding now.
Is this Rom Manager available on the market? ... I'll check
Since rooting, I've used my phone for a day, so I presume you suggest that I wipe data and then do the nandroid in step 7 above, then install the Rom manager and go from there?
I understand your suggestion of the stable CM7. Since there is just one link for the download, no confusions
The Netarchy though is a different story ...
What is the CFS and BFS build stuff.
I'm currently using a Nexus S i9020 with 2.3.4.
So, I use the CM7 + which version of Netarchy?
Thanks once again
Paparasee said:
Thanks bringonblink ... guess I'm starting to get an understanding now.
Is this Rom Manager available on the market? ... I'll check
Since rooting, I've used my phone for a day, so I presume you suggest that I wipe data and then do the nandroid in step 7 above, then install the Rom manager and go from there?
I understand your suggestion of the stable CM7. Since there is just one link for the download, no confusions
The Netarchy though is a different story ...
What is the CFS and BFS build stuff.
I'm currently using a Nexus S i9020 with 2.3.4.
So, I use the CM7 + which version of Netarchy?
Thanks once again
Click to expand...
Click to collapse
Rom Mangager is in the market yes.
No before you wipe , flash, crack, hack ANYTHING else again do a bone stock Nandroid backup and save it on your pc or something. This is because RIGHT NOW your phone is in a working state. THEN wipe cache ,dalvik and data and flash Rom.
7.0.3 is really nice, i had been keepign upwith the nightlies but for me 7.0.3 is the sweet spot... will flash to 7.1 stable when its out though xD.
CFS and BFS are different types of shedulers that run the phone (there is a proper explanation in netarchys thread on the first post i think)
You will want to get CFS as it is mroe stable and generally more user friendly lol.
You'll want CM7.0.3 + CFS Universal 2.3.3 1.3.4
Hey bringonblink ... thank you for your reply
I installed Rom Manager as suggested and then flashed the latest Recovery from within it. Booted into Recovery and did a backup. I then went rebooted, went to my internal storage and found the backup in a clockworkmod folder.
I then went to Rom Manager again and clicked on "Install Rom from SD card". I chose update-cm-7.0.3-NS-signed.zip, ticked Backup, Wipe Data and cache and Wipe Dalvik Cache then pressed ok to reboot.
I then got the big triangle with the ! and droid ... waited, nothing happened so I pressed power and volume up. ... this takes me to the regular stock recovery.
Why not to CWM recovery? Did I do something wrong?
Thanks for any help
Hmm flash the recovery again, but from rom manager choose reboot to recovery, don't actually update in rom manager
Sent from my Nexus S using XDA App
bringonblink said:
Hmm flash the recovery again
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I guess that was the key ... when I flashed recovery again, and then chose to install the rom with all those options ticked, it worked!!!!
Am now using a custom rom ... THANK YOU!!!
Now to the Netarchy kernel ... again ... through CWM recovery I presume.
PS: I never expected a reply so soon ... thought you might be sleeping ... thanks again.
Paparasee said:
I guess that was the key ... when I flashed recovery again, and then chose to install the rom with all those options ticked, it worked!!!!
Am now using a custom rom ... THANK YOU!!!
Now to the Netarchy kernel ... again ... through CWM recovery I presume.
PS: I never expected a reply so soon ... thought you might be sleeping ... thanks again.
Click to expand...
Click to collapse
Thats alright was on my way to work , so on the phone with xda app xD.
Yup same deal again for kernel
Thanks pal ... really appreciate it!
Installed the kernel & google addons too!
All ok now except ... don't have Gmail why is that and how do I get Gmail?
Thanks again!
Paparasee said:
Thanks pal ... really appreciate it!
Installed the kernel & google addons too!
All ok now except ... don't have Gmail why is that and how do I get Gmail?
Thanks again!
Click to expand...
Click to collapse
Market
Sent from my Nexus S using XDA App
matt2053 said:
Market
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Ayeeeeeeeee
For some strange reason, when I go to the market from my PC, I see Gmail, but when I try to install, I get the message:
This item cannot be installed in your device's country!
If I go through the market on my phone, I just cannot find gmail although there is a lot of other apps that include the word gmail.
incidentally ... after flashing CM7, anything I try installing through my PC browser gives the same result as above...
By the way ... any reason why gmail is not included with the rom and with the google addons?
Gmail is in the usual Google Apps package. Maybe try flashing it again.
Paparasee said:
For some strange reason, when I go to the market from my PC, I see Gmail, but when I try to install, I get the message:
This item cannot be installed in your device's country!
If I go through the market on my phone, I just cannot find gmail although there is a lot of other apps that include the word gmail.
incidentally ... after flashing CM7, anything I try installing through my PC browser gives the same result as above...
By the way ... any reason why gmail is not included with the rom and with the google addons?
Click to expand...
Click to collapse
gmail is not available yet in some countries. what you can do is install marketenabler and fake your provider and install gmail.
on cm7, the google apps are not included as they are propriety apps, they are not open source ( if u understand what i mean)
a few years ago, google tried to sue cyanogen for distributing the google apps through cyanogenmod. they then reached an agreement that cyanogenmod could exist provided no gapps were included within.
Hey, thanks for that explanation ... let me check the work around
Hey! am back!
Rather than go through the the trouble of installing market enabler, I just went about testing a couple of other Roms ... since I also wanted to know in what way other roms were different.
I tried Liquid and Infinity ... both were nice and both had gmail, so was happier with them! Wonder why Google went after the cyanogen guys, but the others include those apps
Anyway ... am now downloading Zulu.
After having installed custom roms such as Cyanogen-mod, Liquid and Infinity, I've realized that there are some must haves ...
a) Gmail & Talk (working over 3G)
b) Sip over 3G
c) Power Controls in notification (sexy as in Liquid)
d) screen lock as in Cyanogen (the modded rotary type with an option to add a 3rd party app)
e) BLN support (have not yet got used to the small lights turning on as in BLN but, guess I'll learn).
Would some one know of a Rom that caters to the above ... I'm experimenting with each, but if someone can help, I'd be able to settle in faster
Cheers!
Paparasee said:
Hey! am back!
Rather than go through the the trouble of installing market enabler, I just went about testing a couple of other Roms ... since I also wanted to know in what way other roms were different.
I tried Liquid and Infinity ... both were nice and both had gmail, so was happier with them! Wonder why Google went after the cyanogen guys, but the others include those apps
Anyway ... am now downloading Zulu.
After having installed custom roms such as Cyanogen-mod, Liquid and Infinity, I've realized that there are some must haves ...
a) Gmail & Talk (working over 3G)
b) Sip over 3G
c) Power Controls in notification (sexy as in Liquid)
d) screen lock as in Cyanogen (the modded rotary type with an option to add a 3rd party app)
e) BLN support (have not yet got used to the small lights turning on as in BLN but, guess I'll learn).
Would some one know of a Rom that caters to the above ... I'm experimenting with each, but if someone can help, I'd be able to settle in faster
Cheers!
Click to expand...
Click to collapse
They went after Cyanogen because it is the biggest Most ROMS are based off of it too.
BLN is needed in the kernel, not ROM, Netarchys support this.
I think you will like NScollab, runs off of CM7 with some nice tweaks, also includes netarchys kernel as default.
Oh and it already has all gapps included , including gmail
What a coincidence ... was just downloading NScollab ... 28% done
Thanks!
bringonblink ... am liking this NScollab rom
Edit: Never mind ... googled and found ... no use to me
When I go to the market, I get a pop up asking me if I need to install some apps. Any idea what they do and if it is needed?
The apps are:
Google Chrome to Phone ... never heard of this
Google Goggles ... I know this and won't need it.
Kickback
Soundback
Talkback ... these are the 3 I have no idea about!
Click to expand...
Click to collapse
Thanks ... and cheers!
Both have been fixed but I remain very curious as to WTF, I don't know enough about Android to make any guesses??
Bug 1, running CM 10.1 and somewhere along the line of updating to the latest daily (Maybe March 20, not sure?) my browser began to not work right, I could go to any webpage w/o a problem but if I clicked on a link in the page I was on I would wind up with a blank page. This was not intermittent, it failed every time. I could open a page but could not open any link from the first page.
Bug 2, couldn't fix bug one other than wipe and re-install from scratch (which I did later) so I restored my backup of CleanRom and all seemed well until I tried to install a new app and couldn't get Google Playstore to open. It would say "Loading" and sit there forever. I used the Goo manager to download the latest Google apps and that fixed the problem but.... Playstore worked at the time the backup was made and was set to automatically update. After the restore it didn't try to update, it just hung trying to open.
Again, both are fixed, bug 1 by a fresh install of CM 10.1 and bug 2 by a new download of GAPPS but I'd sure like to know what caused the hiccups....
All your files were moved to a 0 folder and that's why you can't get anything loaded up on cleanrom and you don't need to flash gapps and touch wiz roms. And also aosp rooms aren't always gna be 100% perfect since there will be bugs so don't be complaining about having problems.
Sent from my SCH-I535 using xda app-developers app
If you have no idea what you're talking about and you (obviously) didn't read my post, please don't reply, OK? Thanks.
I start with a fresh wipe of my phone and then install BeanStalk with gapps (I'm currently using BS version 4.4.275 with gapps 20140105. Everything is fine for months. Then a couple of apps will start to crash a few times (the camera, dialer, browser and google apps). I've stopped using titanium backup and clockwork mod to restore my data because they were causing issues. Then the force closes become more and more frequent. I ran fix permissions and i have know clue if it helped or not. Then finally all hell breaks loose and everything begins to force close and give errors of no space left on phone. No launcher will stay open everything just bugs out. This seems to be an on going matter. It doesn't seem to resolve no matter what rom I run. I've gone through every folder sizing it and my phone is not out of space. I am getting very frustrated with my Infuse. I don't understand what some of the stuff means in my catlog file. If someone could help I'd greatly appreciate it.
i found out that Google+ and Google Drive might be the cause (such as when you upload or backup your photos to those clouds)
if you have time, go read those last 10 pages of BeanStalks, you will see what others have offered to resolve this issues
as for me, I'd do full wipe, specially format the sdcard0 (keep the Rom and Gapps to your SDcard1), and stop using the two Google services mentioned above. and use another Gapps (I am using the minimal one) Good luck!
Same problem with Unofficial CM 11.2 also
Exactly the same issue I am having with Unofficial CM 11.2 from scott.
I have been using Scott Harts Unofficial CM from 10.1 to 11.2 on my Samsung infuse and each time i notice a pattern.
Each of the above ROMs start out pretty smooth, and the phone works without any issues for 6 months or so. Then occasionally and app or two start crashing. Then in a weeks time all hell breaks loose and almost all apps start crashing such that the phone becomes unusable. Especially trebuchet starts crashing and that is the end of story.
In the past i have noticed this happens a month or so after an updated rom has been released and I used to upgrade to the new one and the cycle continues.
I am currently on the latest Unoffical CM 11_2 (Kitkat) and the appropriate Gapps installed and the same issue has happened twice.
I have tried the following to fix the issue and nothing helps
1. Clear data for trebuchet and a bunch of other apps.
2. Reinstall Gapps
3. Wipe Cache >> Wipe Dalvik Cache
4. Wipe Cache >> Wipe Dalvik Cache > install Gapps
5. Wipe Cache >> Wipe Dalvik Cache > install custom Rom >> install gapps >> wipe cache and dalvik again
The only way I have been able to get it working in the past is
1. Wipe data/factory reset > Clear Cache > clear Dalvik cache and possibly reinstall ROM and gapps (not sure, but I guess factory reset also does the trick)
So my phone is stuck in this mode and I would like to help debug the situation. Can someone help with the next steps? So that I can capture all required information before I do a factory reset .
Unable to get RSA prompt
Well I went ahead with a factory reset, installed Unofficial CM11_2 from Scott. Got the latest gapps from goo.im and phone seems normal again. But that is the expected behavior untill it starts acting up again.
I tried a lot to connect the phone through ADB and each time it remains unauthorized.
I tried on 2 different laptops, Windows 7, Windows Vista as well as Ubuntu - it always remained unauthorized and no matter what i tried ... changing USB ports , OS machines...nothing helped.
I never got the RSA signature prompt on my phone so could not do anything with ADB.
Any body has any ideas ?
hemen_kap said:
Well I went ahead with a factory reset, installed Unofficial CM11_2 from Scott. Got the latest gapps from goo.im and phone seems normal again. But that is the expected behavior untill it starts acting up again.
I tried a lot to connect the phone through ADB and each time it remains unauthorized.
I tried on 2 different laptops, Windows 7, Windows Vista as well as Ubuntu - it always remained unauthorized and no matter what i tried ... changing USB ports , OS machines...nothing helped.
I never got the RSA signature prompt on my phone so could not do anything with ADB.
Any body has any ideas ?
Click to expand...
Click to collapse
This has been an issue for a while, if the problem is showing up like this:
http://forum.xda-developers.com/showthread.php?t=2175261
Honestly haven't tried ADB with the newer stuff (namely Beanstalk), I just know that ADB as been a problem in the past for Scott's ROM's.
joel.maxuel said:
This has been an issue for a while, if the problem is showing up like this:
http://forum.xda-developers.com/showthread.php?t=2175261
Honestly haven't tried ADB with the newer stuff (namely Beanstalk), I just know that ADB as been a problem in the past for Scott's ROM's.
Click to expand...
Click to collapse
Yes, it is the same problem. Any suggestions ? How is the AOSP based Carbon ROM, any idea if it has the same issue too ?
hemen_kap said:
Yes, it is the same problem. Any suggestions ? How is the AOSP based Carbon ROM, any idea if it has the same issue too ?
Click to expand...
Click to collapse
Not sure about the other ROM's. I could go on a flashing journey, but I have two new devices I'm getting adjusted to right now. If you are not tied down to CM (don't know if it's your DD), I would suggest trying Carbon or CyanFox.
Me, I didn't need ADB that much at the time so I stuck with what I have. Not a solution, but I hope you find a ROM that works (partnered with a minimal gapps).
joel.maxuel said:
Not sure about the other ROM's. I could go on a flashing journey, but I have two new devices I'm getting adjusted to right now. If you are not tied down to CM (don't know if it's your DD), I would suggest trying Carbon or CyanFox.
Me, I didn't need ADB that much at the time so I stuck with what I have. Not a solution, but I hope you find a ROM that works (partnered with a minimal gapps).
Click to expand...
Click to collapse
Unfortunately the infuse is the only phone I have (so my DD)...but the lure to test the ADB on carbon is also compelling for me. Let me try moving to a non smart phone and try this out.
OK. So i installed the Carbon KK nightly, and encountered the same issue. adb devices always lists the phone as
0123456789ABCDEF unauthorized.
Also i never received the rsa prompt...
Moreover the device key seems to suggest it is some default value as compared to an actual device key.
Got it Working !!!
Ok so finally got it working.
I moved away from Scott's Unofficial CM11_2 on my daily driver and moved to Carbon ROM. Loving the new rom so far.
Once i moved to this ROM, I started adb on my desktop (adb kill-server, adb start-server) and was waiting
then on phone enabled Developer options and Android debugging over USB and connected the phone to desktop, and zingggg I get the RSA prompt.
One important thing it read is that you phone should be unlocked when you connect it to your desktop, so in case you have things like PIN or gestures that lock your screen....ensure that your screen is not locked when the phone is being connected.
Not sure if this was the issue or if it was the CM rom,,,but issue is resolved, I am loving Carbon...so not going back to CM to check the lockscreen theory....but worth a try for someone who is pulling his/her hair out like i was.
Ciao !!!
---------- Post added at 05:00 PM ---------- Previous post was at 04:41 PM ----------
missed mentioning that do not worry about the device id of 0123456789ABCDEF....i noticed it does not change for me even when adb connects properly.
It is the unauthorised state that needs to change to device.
What's the default launcher on Carbon, or does it give you a choice like Beanstalk?
Will be retiring the Infuse soon, so am thinking on what ROM to put on when I go to sell it (or give away). The requirement is that is not overwhelming to a new user. Cyanogenmod has a lot of customization, but it doesn't necessarily get in the way. I'd call it borderline overwhelming. Beanstalk is quite overwhelming, because you are forced to pick a launcher right from the beginning (even though I like it for the Jellybean qualities).
Because of these, I just may return it to stock, but have it rooted and with CWM.
joel.maxuel said:
What's the default launcher on Carbon, or does it give you a choice like Beanstalk?
Will be retiring the Infuse soon, so am thinking on what ROM to put on when I go to sell it (or give away). The requirement is that is not overwhelming to a new user. Cyanogenmod has a lot of customization, but it doesn't necessarily get in the way. I'd call it borderline overwhelming. Beanstalk is quite overwhelming, because you are forced to pick a launcher right from the beginning (even though I like it for the Jellybean qualities).
Because of these, I just may return it to stock, but have it rooted and with CWM.
Click to expand...
Click to collapse
I do not see any option to select a launcher like Scotts CM had. So i guess there is no direct option to select it.
Quick search in the running apps shows Launcher 3 running, and apk also available in the priv-app folder in rom, so can conclude launcher is Launcher3.
I did not find it overwhelming in any way.
-Hemen
hemen_kap said:
I do not see any option to select a launcher like Scotts CM had. So i guess there is no direct option to select it.
Quick search in the running apps shows Launcher 3 running, and apk also available in the priv-app folder in rom, so can conclude launcher is Launcher3.
I did not find it overwhelming in any way.
-Hemen
Click to expand...
Click to collapse
I flashed it last night (latest nightly), and it gave me the option of either Launcher3 or Google Now Launcher. I think if someone who was new to the device would be stumped a little by this, but would probably select the Google Now one (the question would be would they press once or always) and be done with it.
Having something recognizable runs at an advantage here compared to Beanstalk, where, unless you know CyanogenMod (or have played with a lot of launchers) you wouldn't know what to select. That would be overwhelming.
Anyway, I wiped the data again, breezed through setup (skipped everything but language and time zone), so it's all ready to go. If need be I can get them set up with a network and Google account before I throw them to the wind.
EDIT:
I see why I got the prompt ... I used the Paranoid Android micro apps package, which includes ... the Google Now Launcher.
hemen_kap said:
Exactly the same issue I am having with Unofficial CM 11.2 from scott.
I have been using Scott Harts Unofficial CM from 10.1 to 11.2 on my Samsung infuse and each time i notice a pattern.
Each of the above ROMs start out pretty smooth, and the phone works without any issues for 6 months or so. Then occasionally and app or two start crashing. Then in a weeks time all hell breaks loose and almost all apps start crashing such that the phone becomes unusable. Especially trebuchet starts crashing and that is the end of story.
In the past i have noticed this happens a month or so after an updated rom has been released and I used to upgrade to the new one and the cycle continues.
I am currently on the latest Unoffical CM 11_2 (Kitkat) and the appropriate Gapps installed and the same issue has happened twice.
I have tried the following to fix the issue and nothing helps
1. Clear data for trebuchet and a bunch of other apps.
2. Reinstall Gapps
3. Wipe Cache >> Wipe Dalvik Cache
4. Wipe Cache >> Wipe Dalvik Cache > install Gapps
5. Wipe Cache >> Wipe Dalvik Cache > install custom Rom >> install gapps >> wipe cache and dalvik again
The only way I have been able to get it working in the past is
1. Wipe data/factory reset > Clear Cache > clear Dalvik cache and possibly reinstall ROM and gapps (not sure, but I guess factory reset also does the trick)
So my phone is stuck in this mode and I would like to help debug the situation. Can someone help with the next steps? So that I can capture all required information before I do a factory reset .
Click to expand...
Click to collapse
Hi,
I was using CM 10.1 from Scott for like a year and didn't have any trouble at all, really the best ROM. Only had two small problems: wouldn't film on 720p without bugging, and MHL to HDMI was not working.
Now I installed CM 11, with latest gapps ( didn't know there was a CM11.2 ), and camera issue on filming is the same. But now it's worse, battery life is lasting half the time it was before, and gallery is crap, bugging every time. Did you have the same issues? Tell me the post of CM11.2 please..
Sent from my SGH-I997 using XDA Free mobile app
jloibman said:
Now I installed CM 11, with latest gapps ( didn't know there was a CM11.2 ), and camera issue on filming is the same. But now it's worse, battery life is lasting half the time it was before, and gallery is crap, bugging every time. Did you have the same issues? Tell me the post of CM11.2 please..
Click to expand...
Click to collapse
Not sure about this, but I think CM 11.2 is referred to as KitKat 4.4.4, which would be latest in the CM thread. So you are probably already running it.
Sent from my Asus MeMO Pad 8"
jloibman said:
Hi,
I was using CM 10.1 from Scott for like a year and didn't have any trouble at all, really the best ROM. Only had two small problems: wouldn't film on 720p without bugging, and MHL to HDMI was not working.
Now I installed CM 11, with latest gapps ( didn't know there was a CM11.2 ), and camera issue on filming is the same. But now it's worse, battery life is lasting half the time it was before, and gallery is crap, bugging every time. Did you have the same issues? Tell me the post of CM11.2 please..
Sent from my SGH-I997 using XDA Free mobile app
Click to expand...
Click to collapse
apart from the issues that i mentioned - my experience with CM 11.2 has been great. There are some obvious things like MHL etc that do not work, but those are known issues.
joel.maxuel said:
I flashed it last night (latest nightly), and it gave me the option of either Launcher3 or Google Now Launcher. I think if someone who was new to the device would be stumped a little by this, but would probably select the Google Now one (the question would be would they press once or always) and be done with it.
Having something recognizable runs at an advantage here compared to Beanstalk, where, unless you know CyanogenMod (or have played with a lot of launchers) you wouldn't know what to select. That would be overwhelming.
Anyway, I wiped the data again, breezed through setup (skipped everything but language and time zone), so it's all ready to go. If need be I can get them set up with a network and Google account before I throw them to the wind.
EDIT:
I see why I got the prompt ... I used the Paranoid Android micro apps package, which includes ... the Google Now Launcher.
Click to expand...
Click to collapse
You can download the Nova Launcher from the google play store if you want to have the same experience as with Scotts Beanstalk. I love the carbon ROM but I am so accustomed to the Nova launcher that I cant live without it.
hemen_kap said:
Exactly the same issue I am having with Unofficial CM 11.2 from scott.
I have been using Scott Harts Unofficial CM from 10.1 to 11.2 on my Samsung infuse and each time i notice a pattern.
Each of the above ROMs start out pretty smooth, and the phone works without any issues for 6 months or so. Then occasionally and app or two start crashing. Then in a weeks time all hell breaks loose and almost all apps start crashing such that the phone becomes unusable. Especially trebuchet starts crashing and that is the end of story.
In the past i have noticed this happens a month or so after an updated rom has been released and I used to upgrade to the new one and the cycle continues.
I am currently on the latest Unoffical CM 11_2 (Kitkat) and the appropriate Gapps installed and the same issue has happened twice.
I have tried the following to fix the issue and nothing helps
1. Clear data for trebuchet and a bunch of other apps.
2. Reinstall Gapps
3. Wipe Cache >> Wipe Dalvik Cache
4. Wipe Cache >> Wipe Dalvik Cache > install Gapps
5. Wipe Cache >> Wipe Dalvik Cache > install custom Rom >> install gapps >> wipe cache and dalvik again
The only way I have been able to get it working in the past is
1. Wipe data/factory reset > Clear Cache > clear Dalvik cache and possibly reinstall ROM and gapps (not sure, but I guess factory reset also does the trick)
So my phone is stuck in this mode and I would like to help debug the situation. Can someone help with the next steps? So that I can capture all required information before I do a factory reset .
Click to expand...
Click to collapse
OK the exact same problem has started again today on Carbon ROM. Wonder if this is a Cyanogen thing, as that seems to be common between the two.
Anyone else facing this ?
-Hemen
hemen_kap said:
OK the exact same problem has started again today on Carbon ROM. Wonder if this is a Cyanogen thing, as that seems to be common between the two.
Anyone else facing this ?
Click to expand...
Click to collapse
Hmm, don't think I kept a ROM on my Infuse long enough to encounter this problem (except for my several months with CM 10.1, no issues). As for other phones, I use Jellybean on my semi-retired HTC and did not have this problem (closest I came was when I tried out Fly-On mod - lag closures often). But I don't think It's a Jellybean problem.
I think (and this may have been covered already) this has to do with the piddly datadata partition filling up. One way to check is open a terminal emulator (app on the phone of adb shell) and type:
Code:
df
Look for datadata in that listing. If it is in the 90% range, that spells trouble. If that is the case, you could try one of two solutions.
I don't know what possessed the developers to separate the data partitions in KitKat (I know, for "performance reasons") but leave 1/2 a GB for it. Lower end phones these days give you twice that.
Over the past few years or so I've installed ROMs going back to ICS. 99% of the time there was absolutely no issue. I habitually do a (1) factory wipe, (2) dalvik wipe, (3) system format, (4) sdcard0 format, (5) install ROM zip, (6) install gapps, (7) wipe cache and (8) wipe dalvik.
In the hundreds of ROMs I've installed and tested, 1 or 2 were bad compiles, and everyone soon knew it. They were immediately removed from any host site. So, if you're having issues, (1) install you ROM as above, (2) perhaps install a smaller gapps, and/or (3) check that you're not overloading your phone from the PlayStore.
The last and rarest issue could be your phone, but rule of thumb that works 99% of the time is: (1) assume it's always your fault first, and (2) read, read, read, read, read.
***I'm not sure if this is done properly, but it seemed right and felt natural, like childbirth.***
I have found that Google Bookmark sync is not included in the latest Gapps and that is because there is no official BookMarkSync for Lollipop.
But Behold! I have found a version that works in Lollipop so I made it flashable from recovery!
Just flash it after GApps and you will be able to accept it to sync when you start up your phone, or it can be done at any time on any Lollipop ROM. The reason I say Lollipop is because of the new folder structure. Just make sure to add the browser sync to your account sync settings and allow it access the first time you open your browser after this. You might also want to go back and check under accounts on the device if bookmark sync is actually synced.
You would still want to follow the normal flash procedure, wipe caches before, after, whatever your preference but I do it after flashing.
You may have to wipe your browser data after boot if you have already installed a rom and have been using it. I did not, wiping cache and dalvik cache seemed to be sufficient.
If this doesn't work for anyone please let me know, and let me know what errors or issues you get. I can try to fix it, but believe me, this dang thing took me forever to get right, so it should work. The folder structure threw me off as well as the permissions. But I finally got it right so I hope you enjoy. I know I missed having my Google Bookmarks.
I attached it as well as included a google drive link. ENJOY
Google Drive Link
for me it work perfectly on Captivate i897 LP5.1.0 OmniRom Lollipop.
Thank you :fingers-crossed::fingers-crossed::fingers-crossed:
I have the Verizon G4 and the option to sync bookmarks is not present under the settings page where you specify to sync gmail, contacts, etc.
Can you make it work with marshmallow? I am getting "Sync is currently having problems. Will be back shortly."
Hey guys and gals I've been fighting with this issue for a while and can't seem to find a way to fix it. I'm running the newest nightly for CM12 via safestrap and I've done a complete wipe and fresh install and I still can't install facebook. Tried clearing the data and cache from the google apps that were recommended via other threads.
This morning I did an entire wipe, installed stock, rooted, installed Facebook successfully, then installed Safestrap, made a new slot, installed CM, and facebook fails on install. Tried installing via Playstore as well as manually with the APK and both fail basically the same way though when doing the APK it doesn't give the 504 error.
So I'm hoping someone out there has another idea of something to try, in the interim I've been running Facebook lite, which works but notifications are unstable for me. It would be easier if I could run the normal app but it's been fighting me at every turn.
Thanks
Luke
Did you try pasting the .APK directly in /data/app and setting appropriate permissions?
Alright I figured I'd come back to this since I did end up finding a solution. I didn't try pasting the APK direct since I had read of some issues with guys doing that and having to wipe the device and I didn't want to have to do that. So I ended up using Titanium backup to backup the copy from the stock rom install that was working, and then restore it into the CM12 install and it worked. Wouldn't update via Play Store but it did work to get a functional install.
So if other guys find this thread down the road, this might be a way to make it work.
Take care!
Luke
I don't know why it wasn't working when you tried to install the apk, but sometimes happened to me something similar. I wasn't able to install any app from the PS, it always trow me an error, I don't remember the exact number, but if it wasn't 504, is really close. The only workaround was to delete my Google account and format data, and when it turned on I skipped the Google first startup wizard and went straight to the play store, and when it prompted to log on, I did and worked flawless. Glad to know that you already fixed it, but this workaround may help someone else
Enviado desde mi RAZR HD mediante Tapatalk