Please unpin this thread. - EVO Shift 4G General

UPDATE: 7.1 "stable" is OK but personally I prefer nightlies.
They are not stable! In fact RC1 boot loops! Please flash the latest nightly and google apps going forward!
Nightlies available here:
http://download.cyanogenmod.com/?type=nightly&device=speedy
Change log and link to nightlies here as well:
http://cm-nightlies.appspot.com/?device=speedy
Gapps here:
http://goo-inside.me/gapps/gapps-gb-20110828-signed.zip
http://goo-inside.me/gapps/gapps-gb-20110828-newtalk-signed.zip
1) Copy zips to sd card
2) Backup with ti backup
3) Flash latest clockwork recovery through rom manager
4) Reboot into clockwork recover and run backup from clockwork recovery (aka nandroid)
5) mount usb storage in clockwork recovery and copy ti backups and clockwork recovery backup to your computer. Also copy any other important files on the sdcard (Especially pictures in the DCIM folder).
6) Copy nightly and gapps zips file to phone's sdcard
7) Wipe cache, wipe dalvik cache (under advanced), wipe battery stats
8) Install zips from sd card in this order:
a) CM_Speedyxxx.zip
b) googleapps 828-signed.zip
c) newtalk.zip
9) Reboot phone and wait 10 minutes phone should be in cm7 and working.
10) verify you can open market.
11) If you have problems try starting back at step 7 in clockwork and wipe data/factory reset
Questions/problems should be posted here:
http://forum.xda-developers.com/showthread.php?t=1001578
Optimal settings for CM7 on Sprint here (work in progress):
http://forum.xda-developers.com/showthread.php?t=1262313
These builds may be marked as Rc1 and stable but they are way old and NOT stable.
Before you ask, as of right now the nightlies are the most stable version of CM7 being release right now.

bump.
Please sticky this.

I agree with these not being stable, and the nightlies are far more stable. But you might want to revise the bootlooping on RC1 statement. It can be stopped from bootlooping by flash it, full wipe while its flashed, flashing gaps, and then it will work fine. I haven't tried another kernel after doing that though.

linuxman008 said:
I agree with these not being stable, and the nightlies are far more stable. But you might want to revise the bootlooping on RC1 statement. It can be stopped from bootlooping by flash it, full wipe while its flashed, flashing gaps, and then it will work fine. I haven't tried another kernel after doing that though.
Click to expand...
Click to collapse
Pointless. Just like flashing RC1.

VICODAN said:
Pointless. Just like flashing RC1.
Click to expand...
Click to collapse
Eh, I use mikshift anyway, but when It came out, it was the only rom I had on my sd card, and I needed to make a phone call, so I was forced to make it work. That method saved my life, or at least made it so I could get a ride home, other than that, I wouldn't use it.
In fact, the only reason I would consider the "stables" would be so that I can not have to pay so that I can get updates (with the only paid roms for the shift being the nightlies, I think there is no reason to buy full rom manager)

You don't have to pay for the nightlies, don't know if you are aware of the mirror for the nightlies, but no pay there. Only have to pay if you want to download thru rom manager. Just thought i'd point thay out
Sent from my PG06100 using Tapatalk

linuxman008 said:
In fact, the only reason I would consider the "stables" would be so that I can not have to pay so that I can get updates (with the only paid roms for the shift being the nightlies, I think there is no reason to buy full rom manager)
Click to expand...
Click to collapse
perhaps you missed this thread
http://forum.xda-developers.com/showthread.php?t=1001578
....
cm7 never charges for anything - even with all the crazy amounts of bandwidth they use...

Just to confirm, it's preferable to flash the nightly rather than CyanogenMod 7 for the HTC Evo Shift 4G :: V7.1.0 (9 Oct 2011) just posted?

sdk234 said:
Just to confirm, it's preferable to flash the nightly rather than CyanogenMod 7 for the HTC Evo Shift 4G :: V7.1.0 (9 Oct 2011) just posted?
Click to expand...
Click to collapse
Yes, I'd still rather flash a nightly.
I'm 100% sure 7.1.0 Oct 9 2011 has bugs. Maybe not the bootloop 7.1 RC1 had but nightlies usually have newer features and more bugfixes than any milestone release.

VICODAN said:
Yes, I'd still rather flash a nightly.
I'm 100% sure 7.1.0 Oct 9 2011 has bugs. Maybe not the bootloop 7.1 RC1 had but nightlies usually have newer features and more bugfixes than any milestone release.
Click to expand...
Click to collapse
You're 100% sure CM7.1 has bugs? Have you used 7.1?

I'm using update-cm-7.1.0-Speedy-signed.zip, released 10/9, without issue. OC'd to 1.5 gHz, using ScaryKernel 3.

jesusice said:
You're 100% sure CM7.1 has bugs? Have you used 7.1?
Click to expand...
Click to collapse
Keyboard shortcuts.
Bug.

VICODAN said:
Keyboard shortcuts.
Bug.
Click to expand...
Click to collapse
So, you HAVE used CM7.1? Can you elaborate more as to what the bug is?
This thread was needed when our last RC was months old but it's now outdated and no longer needed. It should be unsticked. CM7.1 is rock solid.

jesusice said:
So, you HAVE used CM7.1? Can you elaborate more as to what the bug is?
This thread was needed when our last RC was months old but it's now outdated and no longer needed. It should be unsticked. CM7.1 is rock solid.
Click to expand...
Click to collapse
You remember that bug when you opened the keyboard and pressed e and it opened email? The one that was only fixable on a reboot?
I have not flashed it. Why would I? How is it different than a nightly? It's a nightly build that's labeled "stable".

VICODAN said:
I'm 100% sure 7.1.0 Oct 9 2011 has bugs. Maybe not the bootloop 7.1 RC1 had but nightlies usually have newer features and more bugfixes than any milestone release.
Click to expand...
Click to collapse
VICODAN said:
You remember that bug when you opened
I have not flashed it. Why would I? How is it different than a nightly? It's a nightly build that's labeled "stable".
Click to expand...
Click to collapse
If you haven't flashed it then you should avoid advising others not to flash it. And I have had that weird KB issue before but not in the last month or more, so I wouldn't assume a bug that you once had is still present in a ROM that you haven't flashed yet. And if it's no different than a nightly build, what's the point of telling people not to flash it but to instead flash a nightly? People should flash CM7.1 if they want to have official support. Bug reports on nightlies are laughed at.
Again, this PSA is outdated and unneeded now.

jesusice said:
If you haven't flashed it then you should avoid advising others not to flash it. And I have had that weird KB issue before but not in the last month or more, so I wouldn't assume a bug that you once had is still present in a ROM that you haven't flashed yet. And if it's no different than a nightly build, what's the point of telling people not to flash it but to instead flash a nightly? People should flash CM7.1 if they want to have official support. Bug reports on nightlies are laughed at.
Again, this PSA is outdated and unneeded now.
Click to expand...
Click to collapse
Changed the thread title, updated OP.

VICODAN said:
Changed the thread title, updated OP.
Click to expand...
Click to collapse
Works for me

The only bugs that I've noticed are with Music Folder Player Free and a one time bug with the camera.
Music Folder Player Free - With the screen on songs play fine until I go to scroll through a folder/list of songs or if the screen is rotated. It starts to stutter and skip while I'm interacting within the program. With the screen off music will randomly stutter and skip and get worse as the song plays. Stock Android music player doesn't have this issue.
Camera - I tried to take a picture today and my phone seemed to lockup; none of the capacitive buttons would work and a menu pop-up didn't go away. When I pulled my phone back out of my pocket the screen was completely garbled and grainy. Had to pull the battery, but afterward everything was fine again.

Philpot85 said:
The only bugs that I've noticed are with Music Folder Player Free and a one time bug with the camera.
Music Folder Player Free - With the screen on songs play fine until I go to scroll through a folder/list of songs or if the screen is rotated. It starts to stutter and skip while I'm interacting within the program. With the screen off music will randomly stutter and skip and get worse as the song plays. Stock Android music player doesn't have this issue.
Camera - I tried to take a picture today and my phone seemed to lockup; none of the capacitive buttons would work and a menu pop-up didn't go away. When I pulled my phone back out of my pocket the screen was completely garbled and grainy. Had to pull the battery, but afterward everything was fine again.
Click to expand...
Click to collapse
You could always try a nightly?

Why is the latest 7.1.0 stable for Speedy not posted on Cyanogen Mirror Network? I grabbed it elsewhere not long after it came out, but seems weird that it still does not show up there.

Related

[Q] CM7 7.0.3 Last Stable?

I've been running 7.0.2 off my SD for many months - quite happy though I would like the deep sleep and some of the new USB features. Has there been an updated stable version beyond 7.0.3? I remember seeing a 7.1.X on one of these threads.
Also - if I update the CM7 version, will my current data/apps remain intact?
Thanks
Polar
There is a 7.1 RC but the nightlys are pretty much stable these days.
You shouldn't lose any data but make sure to back up
---
- Sent from my LG Optimus V using Tapatalk
My friend, run the newest nightly, you will be glad you did! It even has the OverClock kernel built in! Plus the boot up speed has increased significantly. And more...................
Wipe Cache and Dalvik Cache--Install nightly
Be sure to get the nook tweaks app from Dalingrin, from the market!
http://download.cyanogenmod.com/?device=encore
Install nightly #150, you can download it from Rom Manager. Make sure it includes Google Apps too.
Colchiro said:
Install nightly #150, you can download it from Rom Manager. Make sure it includes Google Apps too.
Click to expand...
Click to collapse
If all the nightlies are pretty much stable, why not just tell him to install the latest nightly?
I think it's a toss up. The old stable builds aren't exactly perfect but I also don't think that the. 32 kernel is perfect yet either. We are still a ways away from a really polished CM7 for NC, I think. The recent builds are faster though.
I was very happy with Nightly 134 but changed to a later nightlies and had various problems. Luckily found a source that carried 134, reinstalled it and have been once again extremely satisfied.
Thank you everyone for the replys. I've been very hesitant to change what works since I use my nook and BT keyboard for work, business trips. I've looked but, can't seem to find - how do I clear the "Cache and Dalvik Cache? Going to try a nightly soon and hope my data is retained. I've used Titanium backup just in case.
Thanks
Just test out different builds. For me, I'm still running the RC1 from the tutorial a while back in the general section. I haven't had any problems besides the occasional problem with not waking up once every 5 days or so?
The best is to just get it the way you want it, and stop messing with it. Use it.
Based on this thread, I went from the last stable....to the newest nightly...(157 at the time)....all is well BUT, my Hulu + app now says the device is no longer supported..I've uninstalled and reinstalled from a backup, but ....nada....any ideas? (sorry for hijack)
Yoke
Edit: Update: I went backwards downgrading to 7.0.3, still had the 'device not supported' on hulu plus, so I started over from scratch, reformatted my SD card and reinstalled the latest nightly, restored apps from titanium backup and everything works fine...something must just have gotten corrupt. Hulu plus really does work nice in the nook color. So does netflix.
Yoke

[ROM] TouchPad UNOFFICIAL CM9 Nightly Builds [DISCONTINUED]

6/27/12: Unofficial nightlies are discontinued: http://forum.xda-developers.com/showthread.php?p=27955579#post27955579
This is a centralized thread to discuss any issues pertaining to my unofficial nightly cm9 builds. As Dalingrin stated, he doesn't plan to release many more Alphas for now unless there's a major change to test so this will be the best way to get the latest CM9 additions (other than building yourself!).
You should only need to wipe caches coming from a previous cm9 build. Remember, these are not tested builds, simply latest source, so there's a chance of "broken" builds as new features are merged in. Always keep a recent backup and/or be willing to do a full wipe. If you're coming from CM7 you should wipe /data if installing in CWM or use ACMEinstaller2 - see the original CM9 Alpha thread.
These builds are mostly a straight sync from source each night, no other extra modifications have been made (other than fixes to ensure is builds). You can find the latest merges into CM9 here: http://tinyw.in/cm9tpmerged (thanks jcsullins for the custom search). The build is sync'd at approx 4am EST and will be ready to download at approx 4.15am EST.
Downloads
There are multiple ways to get the nightlies:
1) Simply browse and find the latest build directly on our host: http://techerrata.co...angs/tenderloin
2) For live announcement of a new nightly arriving on the server follow our Tenderloin twitter account: https://twitter.com/...!/cm_tenderloin - PLEASE NOTE THIS IS AN AUTOMATED TWEET BOT NOT A LIVE PERSON (i.e. do not tweet @CM_Tenderloin expecting a reply)
3) *NEW* The nightlies also support OTA update notifications using the Goo Manager app, details here: http://tinyw.in/feSQ
Latest gapps are here:http://goo-inside.me/gapps
LCD Density fixes: These were taken from dalingrin's Alpha2 thread and are just updated with a new build.prop.
Change to 120dpi: http://tinyw.in/Ja5P
Revert to 160dpi: http://tinyw.in/VUht
Updates:
For updates/announcement on the builds follow me on twitter, or check back here.
4/2/12: http://forum.xda-developers.com/showthread.php?p=24346202#post24346202
3/27/12: TouchPad now has official nightlies! See my post here about the future of my builds: http://forum.xda-developers.com/showpost.php?p=24120253&postcount=219
3/11/12: Due to some merges on 3/9 you may need to reflash gapps when going from a nightly prior to 3/9 to later than 3/9.
2/28/12: HW video decoding (HD youtube and netfix) are now incorporated (still unmerged in mainline CM code). Thanks dalingrin and jcsullins for getting this together. This means the nightlies currently include everything in Alpha2 and whatever else merged since.
Credit and Thanks
Of course major thanks to Dalingrin, jcsullins, fattire, green and the rest of the CM touchpad team for making these builds possible. Thanks to my fellow winners in TeamWin and a special shout out to kevank for hosting and onicrom for build support
Nice to see you here eyeballer!
Thanks eyeballer and teamwin for all your hard work on the touchpad.
So this is all upstream stuff correct? Won't fix anything from 0.6 as related to hardware? Doesn't include the touchscreen drivers from the rootzwiki thread either?
Sent from my SPH-D700 using Tapatalk
Just trying to figure out what else I'm going to need to flash along with the nightlies
Sent from my SPH-D700 using Tapatalk
murso74 said:
So this is all upstream stuff correct? Won't fix anything from 0.6 as related to hardware? Doesn't include the touchscreen drivers from the rootzwiki thread either?
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Just straight CM source, until the updated touchscreen driver is merged you'll need to reflash that after updating the nightly.
i was just about to suggest to close my thread lol, nice to see you here eyeballer!
Tried downloading through the tablet itself and my laptop, all of those zip files are showing a corrupted file.
Sent from my Galaxy Nexus using Tapatalk
Ratzinc said:
Tried downloading through the tablet itself and my laptop, all of those zip files are showing a corrupted file.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Downloaded the newest night 2/17 last night just fine.
Ratzinc said:
Tried downloading through the tablet itself and my laptop, all of those zip files are showing a corrupted file.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Nburnes said:
Downloaded the newest night 2/17 last night just fine.
Click to expand...
Click to collapse
We did have some corruption issues with one of the mirrors but it has been resolved now.
eyeballer said:
We did have some corruption issues with one of the mirrors but it has been resolved now.
Click to expand...
Click to collapse
It seems like chrome beta will download a corrupt zip, while the stock browser dls fine
Sent from my SPH-D700 using Tapatalk
Dees_Troy's touchscreen driver fixes will be included from now, I cherry-picked them into the builds. Also from tonight's build reboot should work thanks to a patch from jcsullins.
hmm, I've done two nightly updates so far without any issues for a couple of days. The latest (0219) causes sods. will keep an eye on it. so far I've had 5 sods whenever screen goes to sleep or I put to sleep.
edit1: ok, after a little more than 5 sods it seems to have settled. guess there were some kernel changes that needed to "work in" first.
I updated to nightlies 0219 and lost my calendar data and calendar sync settings.
I had to reinstall gapps + gapps fix to get it working again.
Is this normal?
Sent from my HP Touchpad running ICS
EP2008 said:
I updated to nightlies 0219 and lost my calendar data and calendar sync settings.
I had to reinstall gapps + gapps fix to get it working again.
Is this normal?
Sent from my HP Touchpad running ICS
Click to expand...
Click to collapse
no, that is not normal. Typically this happens when gaps are mixed and there is a conflict. possible that one of the apps was corrupted? wild guess.
derausgewanderte said:
no, that is not normal. Typically this happens when gaps are mixed and there is a conflict. possible that one of the apps was corrupted? wild guess.
Click to expand...
Click to collapse
Any idea on how to fix it? I just flashed the second nightly update and had to put gapps and the gapps fix on it afterward.
This is using gapps 4.0.3 v11.
Sent from my HP Touchpad running ICS
EP2008 said:
Any idea on how to fix it? I just flashed the second nightly update and had to put gapps and the gapps fix on it afterward.
This is using gapps 4.0.3 v11.
Sent from my HP Touchpad running ICS
Click to expand...
Click to collapse
Are you clearing cache and dalvic cache before flashing the nightly? You don't need to clear data/factory reset.
Sent from my cm_tenderloin using Tapatalk
Pfredd said:
Are you clearing cache and dalvic cache before flashing the nightly? You don't need to clear data/factory reset.
Sent from my cm_tenderloin using Tapatalk
Click to expand...
Click to collapse
I did with this last update, but still no dice.
Only calendar seems to be affected, all other Google sync services work fine.
Sent from my Galaxy Nexus using Tapatalk
EP2008 said:
I did with this last update, but still no dice.
Only calendar seems to be affected, all other Google sync services work fine.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
unfortunately my experience with the same problem was when I used a wrong gapps. It hosed my calendar and email sync. I was able to recover the email sync, but never the calendar (it wouldn't even sync the google cal, let alone my hotmail cal). No matter what I did with the existing rom, no dice in fixing it using the correct gapps or fixes. I then decided to start from scratch, which really isn't that bad. I wiped data to factory and installed a fresh rom, gapps_ics_4.0.3_v11 and all sync problems vanished. I recovered a few apps with Titanium backup.
Backup valuable apps via titanium backup, reboot into cwm, make a backup of your current rom (just in case you decide to go back), wipe cache, dalvik and wipe data to factory, reboot into cwm and install a fresh nightly rom, then gapps_ics_4.0.3_v11. once back in CM you can recover your apps via titanium backup. Just don't recover any google apps or system apps.
cheers
Usually when tapping the notification area, you see your wifi router name and your battery icon and percent. On the nightly currently out, the percentage is broken as it isn't showing. Only the icon is showing
I am Z.

CM7 Kang Request

To anyone who builds their own CM7 kangs, could you please share a recent build?
Thanks in advance!
Edit: well that was fast, the CM team just released CM7.2 RC1!
http://www.cyanogenmod.com/blog/cyanogenmod-7-2-0-rc1-is-upon-us
http://get.cm/?device=speedy
Edit 2: RC1 is still the latest build, and it just bootloops.
If you're looking for a more recent ICS rom, i'd recommend Deck's pre-beta 4. Using it right now and it is the most stable ICS build yet.
MrLinky said:
If you're looking for a more recent ICS rom, i'd recommend Deck's pre-beta 4. Using it right now and it is the most stable ICS build yet.
Click to expand...
Click to collapse
The op asked about cm7 builds, not ICS.
c00ller said:
To anyone who builds their own CM7 kangs, could you please share a recent build?
Thanks in advance!
Click to expand...
Click to collapse
Check ROM Manager, I believe Sparks has a few cm7 kangs.. you could also check out UKE, its on ROM Manager and SDX.
Sent from my HTC Evo Shift using Tapatalk
crump84 said:
Check ROM Manager, I believe Sparks has a few cm7 kangs.. you could also check out UKE, its on ROM Manager and SDX.
Click to expand...
Click to collapse
Thank you, but the last I checked his kangs had some customizations that I did not want... I don't remember what they were, and if he hasn't uploaded a new one since then they would be a bit dated now anyway (e.g. missing some T9 dialer fixes done in late Feb)
Nevermind! CM7.2 RC1 is now available
http://get.cm/?device=speedy
c00ller said:
Nevermind! CM7.2 RC1 is now available
http://get.cm/?device=speedy
Click to expand...
Click to collapse
Cool let us know how it goes, I'm curious if it's stable or not. Also what customizations were you refering to in my rom builds?
I haven't had any luck with 7.2 RC1 yet.
I tried installing it over nightly #255 (cache/dalvik cache wipe) and after a full reset and it hard booted right after it got to the lock screen. I restored my nandroid (need the phone for work) but will try to download/install it again tonight and see what happens.
ratdog07067 said:
I haven't had any luck with 7.2 RC1 yet.
I tried installing it over nightly #255 (cache/dalvik cache wipe) and after a full reset and it hard booted right after it got to the lock screen. I restored my nandroid (need the phone for work) but will try to download/install it again tonight and see what happens.
Click to expand...
Click to collapse
Same result here, rebooting a few seconds after startup.
ratdog07067 said:
I haven't had any luck with 7.2 RC1 yet.
I tried installing it over nightly #255 (cache/dalvik cache wipe) and after a full reset and it hard booted right after it got to the lock screen. I restored my nandroid (need the phone for work) but will try to download/install it again tonight and see what happens.
Click to expand...
Click to collapse
nativ73 said:
Same result here, rebooting a few seconds after startup.
Click to expand...
Click to collapse
*waits for sparksco to act surprised*
ratdog07067 said:
I haven't had any luck with 7.2 RC1 yet.
I tried installing it over nightly #255 (cache/dalvik cache wipe) and after a full reset and it hard booted right after it got to the lock screen. I restored my nandroid (need the phone for work) but will try to download/install it again tonight and see what happens.
Click to expand...
Click to collapse
nativ73 said:
Same result here, rebooting a few seconds after startup.
Click to expand...
Click to collapse
Upon boot up, skip the sign-in, then wait for the reboot. Upon the next boot up, pull down the notification bar and turn off GPS. After this the reboot should stop.
ratdog07067 said:
I haven't had any luck with 7.2 RC1 yet.
I tried installing it over nightly #255 (cache/dalvik cache wipe) and after a full reset and it hard booted right after it got to the lock screen. I restored my nandroid (need the phone for work) but will try to download/install it again tonight and see what happens.
Click to expand...
Click to collapse
nativ73 said:
Same result here, rebooting a few seconds after startup.
Click to expand...
Click to collapse
Try flashing one of the kernels from HERE and hopefully that fixes it. That's the only thing I can think of this being a kernel issue.
cloverdale said:
Upon boot up, skip the sign-in, then wait for the reboot. Upon the next boot up, pull down the notification bar and turn off GPS. After this the reboot should stop.
Click to expand...
Click to collapse
Try a different kernel that should fix the reboot issues with GPS.
sparksco said:
Try flashing one of the kernels from HERE and hopefully that fixes it. That's the only thing I can think of this being a kernel issue.
So audio is confirmed working? I won't have time to flash this until later today..
Click to expand...
Click to collapse
Audio is working fine, but do not flash if you need GPS. It turns out that yes, you can prevent a reboot by quickly turning it off, you can immediately turn it back on, avoiding a reboot, and you can even get a lock on the GPS, but it will reboot again shortly thereafter.
I am going to try another kernel and report back later.
Edit: After flashing your port of "Pershoot/LordLockaN Kernel V14", the reboot issue has been fixed. I am working in my basement, and so cannot check to see if the GPS locks, but all else is well.
Edit2: Though your kernel ports fix the GPS reboot, they take away all audio.
cloverdale said:
Audio is working fine, but do not flash if you need GPS. It turns out that yes, you can prevent a reboot by quickly turning it off, you can immediately turn it back on, avoiding a reboot, and you can even get a lock on the GPS, but it will reboot again shortly thereafter.
I am going to try another kernel and report back later.
Edit: After flashing your port of "Pershoot/LordLockaN Kernel V14", the reboot issue has been fixed. I am working in my basement, and so cannot check to see if the GPS locks, but all else is well.
Edit2: Though your kernel ports fix the GPS reboot, they take away all audio.
Click to expand...
Click to collapse
I thought this might be the case with the audio in the rom and kernel. I need to work on a new kernel that will include some of the new audio changes that work with the rom.
sparksco said:
Also what customizations were you refering to in my rom builds?
Click to expand...
Click to collapse
Minor stuff like this and when I checked your site it had the fonts switched to roboto or something.
Anyway, now that we all confirmed that CM's 7.2 RC1 release is garbage, how can we go about letting them know so 100s/1000s of users don't go downloading and flashing something that doesn't work?
What really bothers me is the fact that the CM team stated "CM7.2 is more than ready for everybody to enjoy ", and I read that they have been doing a lot of offline testing of RC1 when clearly no one there tested this particular build. Does the Evo Shift 4G even have an official maintainer anymore (toastcfh)?
c00ller said:
Minor stuff like this and when I checked your site it had the fonts switched to roboto or something.
Anyway, now that we all confirmed that CM's 7.2 RC1 release is garbage, how can we go about letting them know so 100s/1000s of users don't go downloading and flashing something that doesn't work?
What really bothers me is the fact that the CM team stated "CM7.2 is more than ready for everybody to enjoy ", and I read that they have been doing a lot of offline testing of RC1 when clearly no one there tested this particular build. Does the Evo Shift 4G even have an official maintainer anymore (toastcfh)?
Click to expand...
Click to collapse
I'm not sure what minor stuff your talking about with my kanged build. I posted the flashable stock fonts. Anyways I don't know what CM is doing nor do I really care anymore. The reboot issue with GPS has been a issue with their kernels for quite sometime now but since I never use their stock kerenls I've never had that issue. I won't be building kanged CM builds anymore since I have own repo source.
Requesting once again, if anyone is making their own (working) builds from CM source.
This is based on cm7 but different in many ways.
http://www.gitorious.org/teamandroid/android/blobs/gingerbread-release/README.mkdn.
Follow my cm7 compiling guide but use these commands instead, then
$ ./Speedy.sh
There's already a build on rom manager along with Dread 7us and one_love_420's roms.

CM9 samsungs i9000 problems

I have updated with nightly cm9 for samsung s i900, all day long, and I have time to see some lags:
1. Wi-fi signal is bed and weak
2. restart one or two time by day
3. move slowly than xxjvu
4. After lat update my scree looks green...with nuance. Was missing a color.
I have downgrade to XXJVU, and problems was foxed, for the moment
But when I try to got back to cm9 nightly 19.06.12, the problem appeared again.
The solution was to come back to xxjvu, gone to dark night and after that come back to cm9..very hard problem. I was very afraid.
Have someone sow other problems? Because I want the developer to know all this thins to improve its!
The best!
mishulake said:
1. Wi-fi signal is bed and weak
2. restart one or two time by day
3. move slowly than xxjvu
4. After lat update my scree looks green...with nuance. Was missing a color.
!
Click to expand...
Click to collapse
#1 is something i haven't experienced at all, in fact wifi became faster and better with CM9
#2 happened to me a lot when I ran CM9 with their stock kernel, i use a Semaphore kernel now, and the phone works p much flawlessly. Reboots very rarely while I listen to music (Apollo & Spotify)alltid
#3 is just odd, going from stock 2.3.5 my phone sped up like crazy..
#4 what the hell
Sent from my GT-I9000 using xda premium
Samsung ICS yelow
Hr Kristian said:
#1 is something i haven't experienced at all, in fact wifi became faster and better with CM9
#2 happened to me a lot when I ran CM9 with their stock kernel, i use a Semaphore kernel now, and the phone works p much flawlessly. Reboots very rarely while I listen to music (Apollo & Spotify)alltid
#3 is just odd, going from stock 2.3.5 my phone sped up like crazy..
#4 what the hell
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
I can I do? I cant all ICS that I tried to install made the same, the screen became in yelow shades, darky, and big cotrast, imediately after instaling, with the animation!!!
Any advice will be apreciated!
when you have flashed, have you did all the Wipe ?
Before your flashing, did you a proper base ? (GB 2.3.6 for exmaple ?)
for the color of the lockscreen, i have the same 'problem' but that persist during 1s, so i don't care
mishulake said:
I have updated with nightly cm9 for samsung s i900, all day long, and I have time to see some lags:
1. Wi-fi signal is bed and weak
2. restart one or two time by day
3. move slowly than xxjvu
4. After lat update my scree looks green...with nuance. Was missing a color.
I have downgrade to XXJVU, and problems was foxed, for the moment
But when I try to got back to cm9 nightly 19.06.12, the problem appeared again.
The solution was to come back to xxjvu, gone to dark night and after that come back to cm9..very hard problem. I was very afraid.
Have someone sow other problems? Because I want the developer to know all this thins to improve its!
The best!
Click to expand...
Click to collapse
1. Yeap, I have the same problem with the signal but still I can surf with it in any place at my home + the wifi itself is better (My surfing is smoother and download speed is max)
2. Never happened to me (yet), which kernel are you using? I'm using Semaphore I think it's the best
4. WTF? never heard about this, I didn't update my Rom for two weeks so maybe that's why I don't have this problem, try to go back to 2.3.X Reroot & Semaphore kernel and try again installing that Rom
CM9 color screen problem
mishulake said:
I have updated with nightly cm9 for samsung s i900, all day long, and I have time to see some lags:
1. Wi-fi signal is bed and weak
2. restart one or two time by day
3. move slowly than xxjvu
4. After lat update my scree looks green...with nuance. Was missing a color.
I have downgrade to XXJVU, and problems was foxed, for the moment
But when I try to got back to cm9 nightly 19.06.12, the problem appeared again.
The solution was to come back to xxjvu, gone to dark night and after that come back to cm9..very hard problem. I was very afraid.
Have someone sow other problems? Because I want the developer to know all this thins to improve its!
The best!
Click to expand...
Click to collapse
After first restart, my scree become yellow. I want to put a video but the system cant give access. Right now I'm in cm7, and everything works, fine. No one know what is happen, because I want to install CM9, please!
REefault CM9 samsungs i9000 problems
Can say I have only experienced the restart issue, frequently, sometimes while the phone is sitting idle, and sometimes during calls, while on stock. Currently on July 02 CM9 and to solve the restart/reboot issue, I have been using MNICS kernel, and as of yesterday, the new MACKAY kernel. Hope this helps you with one of your problems. Also use jvu modem.
mishulake said:
Right now I'm in cm7, and everything works, fine. No one know what is happen, because I want to install CM9, please!
Click to expand...
Click to collapse
Stay on CM7 (are you on the latest CM7 build or an old one?) and retry this:
- First please, download the latest available nightly for CM9 link here!
- Then follow the step written by devs:
The thread for CM9 with instructions to flash is here: link !
- Upgrading from CM7?
Do a Nandroid Backup!
WIPE (wipe data/factory reset + wipe cache partition)
Install the ROM from internal sdcard using ClockworkMod Recovery
Click to expand...
Click to collapse
Be sure to do all this step and flash the latest nightly.
I already had to update from CM7 to CM9 twice and, each time, I got it working without problem. So please, try again, make sure to follow the steps and tell us if you're experiencing the same troubles again.
GuillaumeVDH said:
Stay on CM7 (are you on the latest CM7 build or an old one?) and retry this:
- First please, download the latest available nightly for CM9 link here!
- Then follow the step written by devs:
The thread for CM9 with instructions to flash is here: link !
Be sure to do all this step and flash the latest nightly.
I already had to update from CM7 to CM9 twice and, each time, I got it working without problem. So please, try again, make sure to follow the steps and tell us if you're experiencing the same troubles again.
Click to expand...
Click to collapse
Hi guys, I have the exact same issue.
updated from MIUI to CM9 and got yellow screen. Tried different ROMs and Kernel but no solution. Eventually I went back to CM7 and yellow gone away.
but when I try to flash CM9 .... here it comes again! I followed step by step flashing instructions.
any suggestion please?
@mishulake did you solve? how? thanks in advance!!

CyanogenMod 11.0 Stable Released - what is working, what is not?

They just released CyanogenMod 11.0 M6. However it really is the "Stable" C11.0 since they stopped calling "Stable" Releases "Stable". Now there are just the Milestone Releases every 2-4 weeks.
Read all about it: http://www.cyanogenmod.org/blog/cyanogenmod-11-0-m6-release
Here you can download the newest Stable (a.k.a. M6): http://download.cyanogenmod.org/?type=snapshot&device=ovation
Please post in this thread what works and what does not.
Cheers,
sb
I'm running the M4 right now.
Just install M6 via cwm recovery? Or do I need to do anything specific?
__________________
Sent from my LIFE PLAY using Tapatalk Pro.
---------- Post added at 08:24 AM ---------- Previous post was at 08:15 AM ----------
Also is ART working in this?
__________________
Sent from my LIFE PLAY using Tapatalk Pro.
Yes and yes.
Installed CM11 M6
I just installed the M6. Everything was running great until I had to plug in the charger. Now I am also getting the screen flicker. I did not clear the caches and I am using ART. As for ART I have not noticed that it is any faster than dalvik. I will probably switch back to test.
extrem0 said:
Yes and yes.
Click to expand...
Click to collapse
Yes and yes what? Please more details?!
Automan4966 said:
I just installed the M6. Everything was running great until I had to plug in the charger. Now I am also getting the screen flicker. I did not clear the caches and I am using ART. As for ART I have not noticed that it is any faster than dalvik. I will probably switch back to test.
Click to expand...
Click to collapse
Which method did you use for flashing? Link please
CM11 M6
sirbender42 said:
Which method did you use for flashing? Link please
Click to expand...
Click to collapse
I had a working CM10.2 so I downloaded the cwm-recovery-ovation-6.zip from the first post in the EMMC CM11 Install - updated 1/18 thread in the developers forum to my Nooks download folder. Then I downloaded the M6 snapshot from the get ovation builds link on the same page to my downloads folder. Finally I got the latest Google apps signed zip. All 3 downloaded to my Nook downloads folder. I then booted the Nook with a cwm that I had from installing 10.2 and flashed the newer cwm-recovery-ovation-6.zip to my internal emmc memory. Rebooted into the new recovery and flashed the cm11 m6 to internal emmc. Then flashed the google apps rebooted from recovery to cm11.
EMMC C11 Install - updated 1/18 thread http://forum.xda-developers.com/showthread.php?t=2600572
Latest Google apps http://www.google.com/url?sa=t&rct=...T134JI&usg=AFQjCNF5-cVMwChR1F7kICnKoFUjZ83OWg
I followed the For upgrades from CM10.x basic instructions on that page.
I find that the M builds aren't all that stable, even though they are considered to be. I haven't tried on a Nook yet, but on the Galaxy Nexus, the latest M6 constantly freezes my default launcher (Trebuchet) and I'm not the only one with this problem either (there are more similar cases on the CyanogenMod forum.)
HiddenG said:
I find that the M builds aren't all that stable, even though they are considered to be. I haven't tried on a Nook yet, but on the Galaxy Nexus, the latest M6 constantly freezes my default launcher (Trebuchet) and I'm not the only one with this problem either (there are more similar cases on the CyanogenMod forum.)
Click to expand...
Click to collapse
Well, the Nook HD+ has a fairly reproducible bug. About 30% of the time I swipe down the notification bar it crashes the currently running app and freezes the screen (black screen). After about 10 sec. you are back on the homescreen.
Strange that this wasn't catched in the most basic stability tests.
This bug even appears without pulling down the notification area. Sometimes the screen just turns black and freezes for 10 sec. After that you are back on the home screen. Very annoying. Luckily this doesn't happen very often. Unluckily it is very difficult to reproduce...and thus to fix I assume.
Alternative?
sirbender42 said:
Well, the Nook HD+ has a fairly reproducible bug. About 30% of the time I swipe down the notification bar it crashes the currently running app and freezes the screen (black screen). After about 10 sec. you are back on the homescreen.
This bug even appears without pulling down the notification area. Sometimes the screen just turns black and freezes for 10 sec. After that you are back on the home screen..
Click to expand...
Click to collapse
I've got the bug too...
Is there any KitKat ROM for the Nook HD+ that's stable? and does not have these "hiccups"? I'm getting no touch sensitivity during these lock screen resets, and have to restart via the physical button.
Well I have using the M4 build, and apart from a some rare crashes, it has been rock solid.
I think I will stick with for now, and not risk getting the bugs that you guys are reporting in M6. Also, I have it set up just right for my needs and would hate to start from scratch if I install to M6.
Palmahnic said:
I've got the bug too...
Is there any KitKat ROM for the Nook HD+ that's stable? and does not have these "hiccups"? I'm getting no touch sensitivity during these lock screen resets, and have to restart via the physical button.
Click to expand...
Click to collapse
Strange. I can always use the tablet after the hiccup just as before.
I would suggest you install the latest nightly. Since the bug is so obvious, they probably have already fixed it.
sirbender42 said:
Strange. I can always use the tablet after the hiccup just as before.
I would suggest you install the latest nightly. Since the bug is so obvious, they probably have already fixed it.
Click to expand...
Click to collapse
Not yet
Darrian said:
Not yet
Click to expand...
Click to collapse
http://review.cyanogenmod.org/#/c/63867/
In the next nightly this will be fixed (assuming this is the bug we have).
Update: Here is the Ovation Nightly Changelog: http://www.cmxlog.com/11/ovation
A couple of Cyanogenmod bug reports related to this issue have new comments saying that the problem is no longer happening.
https://jira.cyanogenmod.org/browse/CYAN-4047
https://jira.cyanogenmod.org/browse/CYAN-4091
I haven't tested it yet.
Hey guys, why do you think there are no nightlies for ovation anymore?
lerkin said:
Hey guys, why do you think there are no nightlies for ovation anymore?
Click to expand...
Click to collapse
The answer is in the CM11 thread. One of the users there reported there was some kind of glitch in the building process.
Sent from my BN NookHD+ using XDA Premium HD app
I put M6 on my HD for a while. I really missed all the Trebuchet tweaks that are available with 10.1 and 10.2 so I went back to 10.2.1 for now.
Sent from my BN Nook HD using XDA Free mobile app

Categories

Resources