Database Users

CM10 Nightlies for Fascinate!

Just noticed that fascinatemtd is finally being included on the CM10 nightlies! I've been following the Jelly Bro roms up to last week. Although I've been using it as my daily driver, I'm looking forward to even more stability.

Anything not working?

Hilbe said:
Anything not working?
Click to expand...
Click to collapse
I couldn't get the market to download any apps on 8/22. 7/26 gapps. Wiped all three coming from Jt's newest build. Tried twice.

rjkxb2 said:
I couldn't get the market to download any apps on 8/22. 7/26 gapps. Wiped all three coming from Jt's newest build. Tried twice.
Click to expand...
Click to collapse
JT's last build (19 August) had zero issues for me. Last night I dirty-flashed to the 8-23 nightly (after wiping caches) and all is well including app installs with market.
Sent from my SCH-I500 using xda premium

is anyone running the nightly on a alt carrier ?
if so can i get a link to the fix

The wifi reception on the 8/24 nightly with devil kernel 1.2.1 is not as strong as on ths ics build 15 with devil 1.1.3
Smoother than ics, but doesn't feel quite as fast.

What CWM are people using. I was running 7.2 and tried flashing while CWM 3 was installed, it rebooted in CWM 6 and it said it installed fine, but im stuck on the Cyanogenmod boot screen for like 10 minutes...
also is there a way to turn a ROM ZIP file into something I can use Odin to flash it with? I can get into recovery, but I dont ahve a mini USB reader to install a new ROM on.

I was running build 15 teamhacksung ICS, then went to 8/24 build CM10.. cleared all cache, etc, installed cleanly. Loved jelly bean, but it's still very half baked, not usable as an every day phone.
Just went back to CM9 nightly, into which teamhacksung ICS was rolled into today, and everything is nice and quick again. will go back to CM10 when the bugs are worked out.

audiphile said:
I was running build 15 teamhacksung ICS, then went to 8/24 build CM10.. cleared all cache, etc, installed cleanly. Loved jelly bean, but it's still very half baked, not usable as an every day phone.
Just went back to CM9 nightly, into which teamhacksung ICS was rolled into today, and everything is nice and quick again. will go back to CM10 when the bugs are worked out.
Click to expand...
Click to collapse
Really?? 8/24 nightly and all of Jt's builds before that worked great. Very snappy and I've had zero problems. I haven't been back to ICS since probably JT's second build. The nightlies or paranoid android are what I use now daily, and I haven't had a bug problem in quite some time.

I'm been on CM10 8/19 nightly since it dropped. Everything works. I use it heavily for work and personal.
I've put off updating my ROM to another nightly, because it takes me a hour or two to get everything restored back the way I want it. Seems you really do need to do both wipes and a cache flush, then flash ROM, then latest JB apps, to assure best results. I've tried cutting corners twice, and both times, it's bit me in the ass.
Kind of hoping they'll hit a "stable" point on the nightlies soon, and I'll catch up then. I ran CM9 happily for about a month, but I'm so pleased with the additional smoothness, stability and additional features of JB, I haven't looked back since I switched.

tbaddley said:
I'm been on CM10 8/19 nightly since it dropped. Everything works. I use it heavily for work and personal.
I've put off updating my ROM to another nightly, because it takes me a hour or two to get everything restored back the way I want it. Seems you really do need to do both wipes and a cache flush, then flash ROM, then latest JB apps, to assure best results. I've tried cutting corners twice, and both times, it's bit me in the ass.
Kind of hoping they'll hit a "stable" point on the nightlies soon, and I'll catch up then. I ran CM9 happily for about a month, but I'm so pleased with the additional smoothness, stability and additional features of JB, I haven't looked back since I switched.
Click to expand...
Click to collapse
Strange, I have the exact opposite experience. I install everything clean, never cut corners.. CM10 seems to have some memory leak.. it start out really beautiful and smooth.. within hours, it's not usable. CM9 remains stable for days in a row, so i'm back to that for a while.

I've been using the nightly CM-10 builds since 8/23. What's the consensus? If I want to flash to the latest build, do I need to wipe the data and cache?
Thanks!

gm2racer said:
I've been using the nightly CM-10 builds since 8/23. What's the consensus? If I want to flash to the latest build, do I need to wipe the data and cache?
Thanks!
Click to expand...
Click to collapse
That's been my experience, and the thing holding me back from upgrading right now. Definitely going to flash to the latest by this weekend, to see if there are any changes/improvements.
I'm just glad I haven't experienced any memory-leak type behavior. I will admit, though, that I've had it do the "sleep of death" thing twice in ~2 weeks. It may have come back to life on it's own, but I was impatient and pulled the battery in both instances.

is anybody else not able to send mms ?

tbaddley said:
That's been my experience, and the thing holding me back from upgrading right now. Definitely going to flash to the latest by this weekend, to see if there are any changes/improvements.
Click to expand...
Click to collapse
I've done a couple of flashes without wiping the data or cache with no ill effect.

Flashed the 9.1.12 CM10 nightly this morning. Only wiped Dalvik cache, nothing else. Kept all my apps/settings. Everything but Google Music was working great, so I flashed the GApps again, went into Play, uninstalled/reinstalled Music, and everything works now.
GPS locks in pretty quickly in GMaps and all of my GApp and 3rd party apps are working normally.
If this continues to be stable, I'll be more likely to flash more nightlies, with fewer days between upgrades.

phone call static
Has anyone experienced static when making phone calls. I was using the 8/26 build and everyone that I called complained that they couldn't understand me because there was a lot of static. I flashed the 9/1 build and I get the samething but a little worst. Other than the static everything is working great.

Bassmas5 said:
Has anyone experienced static when making phone calls. I was using the 8/26 build and everyone that I called complained that they couldn't understand me because there was a lot of static. I flashed the 9/1 build and I get the samething but a little worst. Other than the static everything is working great.
Click to expand...
Click to collapse
No static here... I've been running the cm10 nightlies (stock kernel) for about a week without any issues. I updated to the 09-04 build last night after just wiping cache and dalvik, along with a test kernel that JT posted yesterday that's designed to provide a bit more power to the radio in order to maybe fix the intermittent loss of data. So far so good.
One thing - I've had some issues after experimenting with using link2sd (a great tool) to move various apps to /system to save precious space on /data. It seems that after moving Google maps; voice; Gmail; and similar core apps to system, play store reports update after update for the apps I've moved.
Sent from my SCH-I500 using xda premium

i was running SC3 milestone 2 (gingerbread).
i odin'd to stock EH03 then rooted it.
tried flashing the CM10 ROM via CWM recovery 2.5.1.x (red), 3.0.0.5 (blue), and 3.0.0.8 (yellow). they all abort saying that there is an error on the .zip file.
any suggestions?
edit: followed this: http://forum.xda-developers.com/showthread.php?t=1238070; stock GB -> THS ICS -> JB. yay!

Anyone else notice that auto brightness isn't working, or maybe it's just me? Using the 9/10 nightly.
Edit: Seems to be working now, before I had all -1's in the light sensor levels but now I'm getting actual values.

[Q] 4.1.2 on top of PA?

Can I install 4.1.2 on top of Paranoid Android's custom ROM? (Trinity kernel) The one thing I have noticed so far on PA is that the home screen still has no rotation which I know 4.1.2 fixed. Not a huge deal, but I am assuming that means PA is still based on the earlier JB version. Will it break anything if I manually update to the latest? I am new to tablets/rooting so I wanted to check before I tried it. (Almost bricked my tablet earlier today cause I had the wrong .zip for PA. Made me hesitant...)

Lazarus416 said:
Can I install 4.1.2 on top of Paranoid Android's custom ROM? (Trinity kernel) The one thing I have noticed so far on PA is that the home screen still has no rotation which I know 4.1.2 fixed. Not a huge deal, but I am assuming that means PA is still based on the earlier JB version. Will it break anything if I manually update to the latest? I am new to tablets/rooting so I wanted to check before I tried it. (Almost bricked my tablet earlier today cause I had the wrong .zip for PA. Made me hesitant...)
Click to expand...
Click to collapse
Lastest release PA 2.2 is based on 4.1.2.

Lazarus416 said:
Can I install 4.1.2 on top of Paranoid Android's custom ROM?
Click to expand...
Click to collapse
No, you cannot.

[help] whatsapp - tablets not supported on defy plus

so last night i flashed the CM10 Sister jelly bean 3.12.
everything works fine except I'm having a problem with my whatsapp!
Alert!
Note: tablets are currently not supported.
I get this error in the start screen
wth? since when Motorola defy+ became a tablet lol?
please guys solve my problem

Earsugar said:
so last night i flashed the CM10 Sister jelly bean 3.12.
everything works fine except I'm having a problem with my whatsapp!
Alert!
Note: tablets are currently not supported.
I get this error in the start screen
wth? since when Motorola defy+ became a tablet lol?
please guys solve my problem
Click to expand...
Click to collapse
even i m on 3.12
no problems with whats app at all

Earsugar said:
so last night i flashed the CM10 Sister jelly bean 3.12.
everything works fine except I'm having a problem with my whatsapp!
Alert!
Note: tablets are currently not supported.
I get this error in the start screen
wth? since when Motorola defy+ became a tablet lol?
please guys solve my problem
Click to expand...
Click to collapse
Uninstall and reinstall. Fixed the problem for me.

Also a simple reboot can help to fix that issue, as it happened to me.

I moved from CM10 to CM10.1 today and I'm facing this issue as well. Running Defy+ and the latest nightly (20130709v2) I tried everything mentioned in this thread but still getting the "Tablets not supported" message. No problems with CM10 at all. Any ideas, guys? This is kind of a dealbreaker to me if it doesn't work, which is a pity, because 10.1 really seems so much nicer otherwise. I also want to take this chance to thank everyone who have contributed to making our Defy the king of all the smartphones, especially Quarx!
Never mind, got it working. Here's what I did:
1) Cleared Whatsapp's cache and data, everything I could from Android's settings.
2) Uninstalled Whatsapp.
3) Booted to Custom Recovery, wiped cache and dalvik.
4) Booted back to Android, installed Whatsapp from Play Store and it was working.
Guess I did things in a wrong order the first time.

Earsugar said:
so last night i flashed the CM10 Sister jelly bean 3.12.
everything works fine except I'm having a problem with my whatsapp!
Alert!
Note: tablets are currently not supported.
I get this error in the start screen
wth? since when Motorola defy+ became a tablet lol?
please guys solve my problem
Click to expand...
Click to collapse
Hay man i too got the same issue !!
wat i did was just cleared my phones dalvick cache memory and cache !! well now its fixed simple !!
http://www.quarx2k.ru

Well.. i tried waatevr u guys advised to.. cleared cache nd stuf..
But it dint work, untill i rebooted my phn.. Haha, i dont believe it.. it just needed a good old reboot.

Im back lol....

Well after all these yrs im back to my ole trusty vibrant.
Broke my S2 yesterday with no insurance :-/
So here I am and don't really recall all the procedures....but im getting there slowly.
Currently im still running team whiskeys bionix v 1.3.1 from back in the day.
Any tips and tweeks would be appreciated

Or don't....don't plan on using this dinosaur for long

Shortbus-Driver said:
Or don't....don't plan on using this dinosaur for long
Click to expand...
Click to collapse
This "dinosaur" can run Jelly Bean 4.2 in case you didn't know, plenty of custom ROMS in the development section. If your staying on 2.2 then there are really no "tips and tricks", as those ROMs are very stable. The basic steps for flashing a ROM with this phone in recovery mode are as follows : format system, data and cache under "mounts are storage"(this is optional but recommended for a clean install). The next steps are necessary everytime you install a ROM unless told otherwise by the developer : wipe data/factory reset, wipe cache, wipe dalvik cache (under advanced) then install your ROM, now go back to the advanced section and fix permissions, now reboot and wait ten minutes. Note, if your going to flash from 2.2 to jelly bean then you will have to flash the ROM twice, the first flash just updates your recovery mode.
Sent from my SGH-T959 using Tapatalk 2

Thanks I wouldn't have known to flash twice on the jb ...I woulda just flashed back to stock and gone from there.
Also if im correct back when this phone was the phone to have ....flashing anything over gb meant loss of gps,wifi, along with other issues....does thus still hold true today?

Shortbus-Driver said:
Thanks I wouldn't have known to flash twice on the jb ...I woulda just flashed back to stock and gone from there.
Also if im correct back when this phone was the phone to have ....flashing anything over gb meant loss of gps,wifi, along with other issues....does thus still hold true today?
Click to expand...
Click to collapse
Gps is always iffy for the vibrant, but we are fine for the rest. :thumbup:
Nexus⁴ PAC 360° Productions

Shortbus-Водитель said:
Или не....не планируете использовать этот динозавр надолго
Click to expand...
Click to collapse
Phone is quite good, much better than the new HTC Desire Triple with an easy-beating screen! I ran it by Sadanand 4.3.1, works perfectly!

Cyanogenmod Samsung Logo Hang

Is anyone else having the problem where if you turn off your phone and turn it back on it'll sometimes freeze at the Samsung logo. If you do a battery pull and turn the phone back on again, it'll boot like normal.
Firmware: MDL
ROM: Cyanogenmod 10.1 RC2
Recovery: TWRP

What twrp version?

xBeerdroiDx said:
What twrp version?
Click to expand...
Click to collapse
TWRP 2.5.0.2
I used your HOW-TO guide to complete everything
Loki+TWRP+Motochopper CASUAL
Wiping Device
Flashing ROM

How long has it been doing this/at what point did it start?

I've only had the phone for about 2-3 days and when I got it I immediately flashed CM. So ever since I flashed it?
I just noticed it last night though.
No changes. Only CM was flashed. No different kernal

emckai said:
I've only had the phone for about 2-3 days and when I got it I immediately flashed CM. So ever since I flashed it?
I just noticed it last night though.
No changes. Only CM was flashed. No different kernal
Click to expand...
Click to collapse
This has been seen in some builds of 4.3. If you let it boot a long time it'll usually get past that and then be ok. Technically, the 2.5 build of twrp is not for 4.3 roms so you might try 2.6.3.0. But that's been met with mixed success.

jd1639 said:
This has been seen in some builds of 4.3. If you let it boot a long time it'll usually get past that and then be ok. Technically, the 2.5 build of twrp is not for 4.3 roms so you might try 2.6.3.0. But that's been met with mixed success.
Click to expand...
Click to collapse
RC2 is a 4.2.2 build.
Last night I decided to just try and let it hang and see if it'll get past it but 2 minutes later it never did. So I just held the power button (10 seconds) to shut it down and restart.

Sorry, didn't read your whole post and missed the rc2.

jd1639 said:
Sorry, didn't read your whole post and missed the rc2.
Click to expand...
Click to collapse
No problem. Just wondering what is causing this issue, seems like some people in the Cyanogenmod thread is also having this issue.

It's happening on the cm10.2 roms too and seems to be related to the recovery used. See if twrp 2.6.3.0 works for you.

SOLVED: According to Cyanogenmod this is a known issue. Check the #2 post in the OFFICIAL cyanogenmod thread.

I switched custom recovery. TWRP to CWM and everything is booting just fine. (knock on wood) I'll turn off and on my phone a couple more times and see if it's actually the custom recovery.

cwm has had far fewer problems on the S4 than twrp. i've always rolled with cwm touch across my devices just out of preference. glad i havent had to deal with any of these twrp issues. glad you're sorted. cheers

Just rebooted my phone a couple of times (about 10 times) and it didn't hang at samsung logo anymore.
Thanks everyone!

emckai said:
SOLVED: According to Cyanogenmod this is a known issue. Check the #2 post in the OFFICIAL cyanogenmod thread.
Click to expand...
Click to collapse
LMAO, that's not "solved". It's simply acknowledging there is a problem. hahah
So guys, the problem is not just in CyanogenMOD. It's also in stock 4.3 GE and 4.4 ROM's. And I get it regardless of what version of TWRP or Philz CWM I use.
It's something that started with 4.3 and is still present in 4.4 (stock GE & AOSP both). Because I never had the problem on any 4.2 ROM's.

CZ Eddie said:
LMAO, that's not "solved". It's simply acknowledging there is a problem. hahah
So guys, the problem is not just in CyanogenMOD. It's also in stock 4.3 GE and 4.4 ROM's. And I get it regardless of what version of TWRP or Philz CWM I use.
It's something that started with 4.3 and is still present in 4.4 (stock GE & AOSP both). Because I never had the problem on any 4.2 ROM's.
Click to expand...
Click to collapse
x2 to all of the above. Known issue for S4s on 4.3 and 4.4 and although a couple of ROMs have claimed that they're "solving" it as of yesterday's nightlies it ain't fixed....
Just hold down power till the Samsung screen disappears then immediately let go. It'll try again. Repeat, repeat, repeat as necessary and eventually it will work.

Okay, it's definitely a kernel issue.
I've ruled out recovery and ROM.
For instance, I flashed an AOSP 4.4 ROM and it was freezing at Galaxy S4 splash screen on almost every single reboot.
Then I flashed a different kernel and the issue immediately and completely disappeared. I've done 20+ reboots since.
I flashed Ktoonsez 4.4 AOSP kernel btw. That's what fixed it for me.

CZ Eddie said:
Okay, it's definitely a kernel issue.
I've ruled out recovery and ROM.
For instance, I flashed an AOSP 4.4 ROM and it was freezing at Galaxy S4 splash screen on almost every single reboot.
Then I flashed a different kernel and the issue immediately and completely disappeared. I've done 20+ reboots since.
I flashed Ktoonsez 4.4 AOSP kernel btw. That's what fixed it for me.
Click to expand...
Click to collapse
I've been using the same kernel since yesterday afternoon and haven't hung once either. I've tried it with CWM and TWRP because my hangs used to occur when I rebooted system from recovery and both have worked just fine.