Related
For Nexus S 01/02/2014
Cm 10.2.1 Stable
http://download.cyanogenmod.com/get/jenkins/57343/cm-10.2.1-crespo.zip
http://get.cm/get/e36
For gapps 20130813
http://goo.im/gapps/gapps-jb-20130813-signed.zip Working.
http://www.androidfilehost.com/?fid=23060877490000124 Working.
http://dongworkmod.org/gapps/gapps-jb-20130813-signed.zip.torrent Torrent.
CM 10.2.1 has been branched and released, officially ending our planned release process for Jellybean (Android 4.3) code. Included in the release are various devices that did not see a 10.2.0 build, such as the Droid RAZR HD, Photon Q, Nexus Q, Nook, Nook HD & HD+ and more. Downloads can be reached via our download portal using the following link.
This release does not bring a wealth of new features on top of 10.2.0, but instead focuses on bug fixes, APN updates, localization (translations), and some back port of code (and fixes) from CM11 (Android 4.4 Kitkat).
For those interested in a list of changes, feel free to browse our Gerrit for 10.2 mergers between December 2nd, 2013 and January 31st, 2014. To those who prefer to build your own releases, the 10.2.1 code can be found under the branch name ‘stable/cm-10.2′on our Github.
Source: http://www.cyanogenmod.org/blog/cm-10-2-1-maintenance-release
i wrote this for people that who didn't realized about Add ROW scheduler (android_kernel_samsung_crespo)
To activate it Setting/Performance settings/ i/o scheluder/ change it ROW instead of deadline and check the box which write apply at startup.
Source
lagloose said:
Hey people,
here's an alternate kernel for CM10.2 compiled from original CM sources, except following changes originally done by cn.fyodor:
- raise the max surfaceflinger FPS up to about 65~68
- make the Vsync thread more favorable for Android system
- squeeze a bit memories to userspace from the Kernel
This kernel should give a smoother UI experience. Klusark mentioned that raising FPS might break some apps. I didn't have any problems yet, but i guess this could happen for some games. Please report back here, if you find any problems. I agree with Klusark to not cut some more memory from 'camera space' to ensure all camera/video functions are working. However, if you like have a try, and tell me what you think.
Flash as usual via recovery. DO NOT wipe anything before and DO A BACKUP FIRST !!!
Download link
Greetz
Click to expand...
Click to collapse
Oh yeah
Many thanks!
The long wait is finally over!
Are there any issues or is everything working?
Gesendet von meinem Nexus S mit Tapatalk 4 Beta
4I-I said:
Are there any issues or is everything working?
Click to expand...
Click to collapse
Just finished downloading. Will flash and test for a while and report.
4I-I said:
Are there any issues or is everything working?
Gesendet von meinem Nexus S mit Tapatalk 4 Beta
Click to expand...
Click to collapse
I've been using it for an hour and there is no issues with the apps I use at least.
p.s. why is this not in the development section?
i can't open market or something with wi-fi and some times had camera problem not so much.
Victory! Downloading and will post impressions later on. Will try a dirty flash and see what happens
@maintainers of crespo device:
Just had a look at changelog...
IMHO you should re-enable system property 'ro.sys.fw.bg_apps_limit' in crespo build because it's very useful on low memory devices. So revert the 'revert' patch ( ) http://review.cyanogenmod.org/#/c/48640/
Greetz
wifi problem not related with the nightly it was my modem.
Everything (that I use) running smoothly.
Upgraded from @noloukos unofficial builds.
Dirty flash from cm10.1 nightly. Focal kinda force closes a lot and Nova gets killed almost all the time. Facebook app giving only ANR. But the ROM seems smoother.
Will probably do a full wipe when I get home
andrei1015 said:
Dirty flash from cm10.1 nightly. Focal kinda force closes a lot and Nova gets killed almost all the time. Facebook app giving only ANR. But the ROM seems smoother.
Will probably do a full wipe when I get home
Click to expand...
Click to collapse
focal just once worked for me when i open the normal camera first.
Been testing for almost five hours. Had all my user apps from 4.2 installed on the ROM. I have to admit the ROM is pretty smooth compared to 4.2.2. The only bug I noticed is the FC when switching from primary cam to secondary(back) cam and back to primary cam again. Also, data connection upstream and downstream arrows don't show up on the signal bars when enabling 3G.
Yes, cameras are a bit buggy.
Anyone using Nova Launcher? Is it getting killed a lot? Like after going back from any app?
Focal and camera not working for me.
Also, cant redefine the lockscreen shortcuts.
Downloading.. :good::good:
No love for be nexus s 4g
Sent from my Nexus S 4G using xda premium
I've layered a lot of ROMs on this phone without wiping and finally encountered a problem. Settings won't open any more. I started with some unofficial d801 CM 10, then put the official d802 CM 10 nightly with a d801 kernel, then a d801 CM 10 final, then CM 11 M1, and I've installed a few nightlies since. I'm not sure when it broke, sometime between the M1 CM 11 release and the 2013-12-11 nightly.
Since I haven't seen anyone else reporting a problem like this I'm guessing piling up all these ROMs is the source of the problem. The help I'd like is finding the crash report so I can try to figure out where things are going wrong. Where might I find the crash report? If it's not typically generated, how can I use ADB to debug the Settings app?
It'd be nice if someone knows a quick fix for this. But I'd still like to learn how to investigate it myself.
Thanks!
Wipe
Sent from my LG-D803 using XDA Premium 4 mobile app
dibarnu said:
I've layered a lot of ROMs on this phone without wiping and finally encountered a problem. Settings won't open any more. I started with some unofficial d801 CM 10, then put the official d802 CM 10 nightly with a d801 kernel, then a d801 CM 10 final, then CM 11 M1, and I've installed a few nightlies since. I'm not sure when it broke, sometime between the M1 CM 11 release and the 2013-12-11 nightly.
Since I haven't seen anyone else reporting a problem like this I'm guessing piling up all these ROMs is the source of the problem. The help I'd like is finding the crash report so I can try to figure out where things are going wrong. Where might I find the crash report? If it's not typically generated, how can I use ADB to debug the Settings app?
It'd be nice if someone knows a quick fix for this. But I'd still like to learn how to investigate it myself.
Thanks!
Click to expand...
Click to collapse
Have you tried wiping cache and davlik cache in recovery and fixing permissions......could be a quick fix
Hi,
Any suggestion for a stable ROM ?
Thank you all
You are asking what ROM to run in the paranoid android forum section.... What rom do you think we would suggest? Paranoid android of course....
#stayparanoid
Sorry and thanks
Paranoid is by far the best rom I had
Can't live two days on the stock rom (Sony)
Anyone with OPPO find 7 is running Paranoid ROM can tell us how is it and if there are any issues . thanks
ma8ash said:
Anyone with OPPO find 7 is running Paranoid ROM can tell us how is it and if there are any issues . thanks
Click to expand...
Click to collapse
I'm using The latest version of PA 4.6 beta on my find 7 QHD as my daily driver and love it.
Haven't noticed any major issues, battery life is really good. Wifi, 3G, and bluetooth all work flawlessly. (I haven't tried LTE because I haven't got it on my mobile plan)
The only issue that I've encountered is that, on a couple of games I have, sometimes they become slow and unresponsive (family guy game and 2014), I didn't have these problems on ColorOS.
PA 4.6 is currently beta so I'm not really concernecd and I think the minor issues will be ironed out in future updates.
Thank you very much
I have tried PA 4.6 Beta 5 today
My story here
T
Paranoid and mahdi room
ma8ash said:
Anyone with OPPO find 7 is running Paranoid ROM can tell us how is it and if there are any issues . thanks
Click to expand...
Click to collapse
Had a very bumpy ride with the first installation. I think I forgot to reset to factory settings, so it might be my fault.
Second installation was better. There are certain things I don't love:
Chrome browser runs on windowed version, no matter what setting you try to change.
Battery seems very short. I need to recharge halfway through my day.
I can't get the gestures to work when the screen is off. (double tap works great, nothing else).
Everything else is buttery smooth. Maybe I'm just unlucky with a few glitches here and there.
Chrome issue happens on any ROM with floating mode implemented. Its a google chrome issue. They have fixed it in their latest beta.
#stayparanoid
I just can advice you to use PA. It's my personal favorite
PA Lollipop where?
I have searched high and low. Where can I find PA 5.0.x for my Find 7?
flemmingski said:
I have searched high and low. Where can I find PA 5.0.x for my Find 7?
Click to expand...
Click to collapse
We haven't released any pa 5.0....on any device.
#stayparanoid
Error downloading rom
Whenever I try to download the latest paranoid android rom for the find7s (qhd), I get an "error executing updater binary" message. I looked up and saw that you had to install the latest cyanogenmod nightly first, which I did, but I still couldn't get it to work. I first wiped everything (data,dalvik,cache) then I installed the cyano nightly, then I wiped the data, then I installed paranoid android and I still get the error. I am also running the latest twrp recovery (2.8.6.0). Thanks in advance for anyone that can help me out
chair96 said:
Whenever I try to download the latest paranoid android rom for the find7s (qhd), I get an "error executing updater binary" message. I looked up and saw that you had to install the latest cyanogenmod nightly first, which I did, but I still couldn't get it to work. I first wiped everything (data,dalvik,cache) then I installed the cyano nightly, then I wiped the data, then I installed paranoid android and I still get the error. I am also running the latest twrp recovery (2.8.6.0). Thanks in advance for anyone that can help me out
Click to expand...
Click to collapse
Use the legacy build.
Hey there, proud owners of Redmi Note 3 Pro. Since, there are two cm13 variants, both currently under development, so I decided to start this thread, to compare both variants and help other users to decide which to flash. And, if they mess up or want to revert back or any other problem occurs, help them and guide them through the whole process.
I want other people to participate to and list the pros and cons of both the roms with their respective version name. It will help others to decide better about which rom to flash and all.
WARNING: By flashing the new/updated firmware, you might have trouble going back to miui7 based on 5.1.1. I tried flashing fastboot stable rom, and I was having wifi, no sime, etc issues. And when flashing CM13 again, the issue were resolved. This is because of the firmware change.
For those who are also having no sim/wifi issues on miui7 after flashing fastboot or recovery rom, do not immediately come to confusion that you have lost your imei or efs partition, try going back to CM13 to check whether the issues still exist or not.
ADVICE: Make a complete backup of your miui rom using twrp alka. NOTE: Official twrp will not help you create the backup of every single patition, so please download and flash twrp alka as your recovery. Even if you don't want to make a backup, I ADVICE you to backup atleast efs partition, it may come handy later.
Nope...You can restore the splash image from your previous mm backup to get MI spalsh image. eace:
Sent from my Redmi Note 3 using Tapatalk
CM13 by Santhosh M
Build date: 17 - 06 - 2016
1. Minor bluetooth related bugs.
2. Slow gps. But it works.
3. Some force close issues.
4. LED notification settings error. Led are working, only they seems to ignore the manual settings.
5. Other small things i may have not noticed.
There may or may not be camera force close, the patch for it is uploaded right below the downloading link in his thread. Everything thing else seems to be fine. The firmware/radio is from a leaked source and thus a bit unstable and may cause some problems. If it causes problems, flash some other Android M based radio for redmi note 3 pro. Make sure not to flash radio from some other device, you may end up getting bricked or loosing your imei.
HTML:
http://forum.xda-developers.com/redmi-note-3/development/rom-cyanogenmod-13-0-xiaomi-redmi-note-3-t3350656
Build by banmeifyouwant & thestrix
Build date: 19 - 06 - 2016
Bugs:
1. Wrong bluetooth address and mac address.
2. Some bluetooth services that i may have not noticed.
3. Some force close issues that can be solved by wiping the data/cache of the app or cache from recovery.
The rest seems be good. GPS working. Voice recognition in google app working. No com.android.phone force close. No music force close. If you have some problems, then flash the radio package after flashing the rom.
HTML:
http://forum.xda-developers.com/redmi-note-3/development/cyanogenmod-13-t3398789
Another bug in cm ROMs. Music app force closes if u have more than 250+ songs listed in ur music app.
Just tested by me. I had more songs and I was getting FCS. Just to verify, I created .nomedia file in some folders and music player plays well.
Some one needs to fix it. I tested with cm13 by banmelfyouwant and mokee.
Sent from my SHIELD Tablet using XDA-Developers mobile app
srihari210 said:
Another bug in cm ROMs. Music app force closes if u have more than 250+ songs listed in ur music app.
Just tested by me. I had more songs and I was getting FCS. Just to verify, I created .nomedia file in some folders and music player plays well.
Some one needs to fix it. I tested with cm13 by banmelfyouwant and mokee.
Sent from my SHIELD Tablet using XDA-Developers mobile app
Click to expand...
Click to collapse
I have exactly 589 songs and no fc in music app. If you are having fx, clear cache and dalvik and then try again.
This thread is not in the correct section.
Polls, Guides, Tips and Tricks should reside in General category.
Please refrain from creating such threads in the development section.
I have been noticing a lot of such threads here.
Cheers.
dagger said:
This thread is not in the correct section.
Polls, Guides, Tips and Tricks should reside in General category.
Please refrain from creating such threads in the development section.
I have been noticing a lot of such threads here.
Cheers.
Click to expand...
Click to collapse
Sorry about that, i am new at XDA and thus didn't knew on which section to post this, so i just posted it under snapdragon section. I didn't know this section was reserved for just development reason only.
Even Flour_Mo rom is highly stable with everthing working
http://www.miui.com/thread-4341855-1-1.html
June 7 build
What are the bugs in Santhosh's build?
Does GPS work in his build?
jain_pranav said:
What are the bugs in Santhosh's build?
Does GPS work in his build?
Click to expand...
Click to collapse
Yes gps works, but somebody complained that it was slow in his latest built 17
I have been using banmeifyouwant build. It's very smooth but GPS is an issue for me. Will be shifting to Santhosh's build now.
archit.bajpai.ab said:
Yes gps works, but somebody complained that it was slow in his latest built 17
Click to expand...
Click to collapse
The BanMeIfYouWant build would crash/reboot when I tried to use the gps for navigation.
I switched back to Santhosh's latest and the gps was slow. It wouldn't lock at first, but after 5-10 minutes I was able to connect and haven't had an issue connecting since.
Santhosh's build is more stable in my opinion, so that's what I recommend.
Yaranaika said:
The BanMeIfYouWant build would crash/reboot when I tried to use the gps for navigation.
I switched back to Santhosh's latest and the gps was slow. It wouldn't lock at first, but after 5-10 minutes I was able to connect and haven't had an issue connecting since.
Santhosh's build is more stable in my opinion, so that's what I recommend.
Click to expand...
Click to collapse
Can you list all the pros and cons of that rom here. It would really help other to know what they will get when they flash
archit.bajpai.ab said:
both the roms use MM bootloader
Click to expand...
Click to collapse
I use the userdebug bootloader form the leaked CAF rom. :silly:
jain_pranav said:
What are the bugs in Santhosh's build?
Does GPS work in his build?
Click to expand...
Click to collapse
Yeah his build is very much stanle. The only downgrade is that you will lose 4k recording that is only available in banmeifyouwant built
archit.bajpai.ab said:
Yeah his build is very much stanle. The only downgrade is that you will lose 4k recording that is only available in banmeifyouwant built
Click to expand...
Click to collapse
No, 4K recording also working on another CM13 ROM, it's made by TheStrix and you know, he's currently working with our device for the real Official CM13.
MOVZX said:
No, 4K recording also working on another CM13 ROM, it's made by TheStrix and you know, he's currently working with our device for the real Official CM13.
Click to expand...
Click to collapse
Glad to hear. I still can't understand why banmeifyouwant a d santhosh are working seperately for the same goal. Shouldn't they be working together for the official cm13, that way the updates will be made faster.
banmeifyouwant said:
I use the userdebug bootloader form the leaked CAF rom. :silly:
Click to expand...
Click to collapse
So, you rom is technically not using the mm bootloader, instead its more like custom one.
And one more thing. Why you and santhosh are working differently on the same rom. Wouldn't it be better to merge both and hence release a more better rom. If you both can work diiferently and create such a rom in a nich of time, then if you work together, you both can create a perfectly stable rom in no time.
MOVZX said:
No, 4K recording also working on another CM13 ROM, it's made by TheStrix and you know, he's currently working with our device for the real Official CM13.
Click to expand...
Click to collapse
Where did you get this build?
Sent from my kenzo using Tapatalk
Has anyone else tried it?
I have no idea who built it.
For me no sound and no wifi.
I'm downloading it now.
Where did you download it from?
Sent from my ZTE A2017U using XDA-Developers mobile app
troy5890 said:
Where did you download it from?
Sent from my ZTE A2017U using XDA-Developers mobile app
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=529152257862691649
Thank you WesTD
Sent from my ZTE A2017U using XDA-Developers mobile app
No camera. Haven't tested much but it is stable after 12 hrs.
camera, WiFi and sound are not working.
Looks like this guy uploaded it.
It is definitely in alpha stage. I hope the dev keeps working on it.
Has anyone else tried BrokenOS from AFH?
I use it as my daily driver, only problem I have had is it will not switch back to network data from wifi without rebooting.
I am not linking to it because the devs dont like xda.
RUNNERX said:
It is definitely in alpha stage. I hope the dev keeps working on it.
Has anyone else tried BrokenOS from AFH?
I use it as my daily driver, only problem I have had is it will not switch back to network data from wifi without rebooting.
I am not linking to it because the devs dont like xda.
Click to expand...
Click to collapse
Hola
I knew that the Dysfunctional team had released a BrokenOS instance for the Axon 7, but I never used it because the builder / maintainer put the unsupported tag in the filename. Also given lack of updates I thought they weren't going to officially support the Axon 7. Have you any recent updates?
No update but it is very stable.
Are you guys able to rollback to zadmix or you 6.0.1 backup if you try this 14.1 ROM?
After wiping system and cache I reinstalled cm13 then restored my backup. Couldn't go straight from 14.1 to restore it would fail.
What Gapps are you guys using for this? Link?
RUNNERX said:
No update but it is very stable.
Click to expand...
Click to collapse
So thanks to your input, I jumped in and installed the BrokenOS ROM. WOW, I now regret not giving them a try much earlier. First AOSP based ROM that seems to work ok, the audio is not quite there yet but still very usable with V4A enabled.
I tried to reproduce the issue that occurs when Wifi is off by trying the Wifi off <-> Wifi on toggle numerous times and I am able to get cellular data back without issues. I did do a clean wipe of my existing stock ROM before attempting to install the BrokenOS ROM, immediately followed by Gapps install. Not sure if that sequence of installation helped. I also noticed that first boot takes a good 5 to 10 minutes to complete.
So for folks out there looking for a decent third party ROM with lots of customization, the "unsupported" instance of BrokenOS looks ok. I will still revert back to CM13.1 whenever Unjustified Dev and DrakenFx complete their work.
One item to note is that the existing release of BrokenOS only has up to the August 5 security patches.
QAM said:
So thanks to your input, I jumped in and installed the BrokenOS ROM. WOW, I now regret not giving them a try much earlier. First AOSP based ROM that seems to work ok, the audio is not quite there yet but still very usable with V4A enabled.
I tried to reproduce the issue that occurs when Wifi is off by trying the Wifi off <-> Wifi on toggle numerous times and I am able to get cellular data back without issues. I did do a clean wipe of my existing stock ROM before attempting to install the BrokenOS ROM, immediately followed by Gapps install. Not sure if that sequence of installation helped. I also noticed that first boot takes a good 5 to 10 minutes to complete.
So for folks out there looking for a decent third party ROM with lots of customization, the "unsupported" instance of BrokenOS looks ok. I will still revert back to CM13.1 whenever Unjustified Dev and DrakenFx complete their work.
One item to note is that the existing release of BrokenOS only has up to the August 5 security patches.
Click to expand...
Click to collapse
Sent u pm
QAM said:
So thanks to your input, I jumped in and installed the BrokenOS ROM. WOW, I now regret not giving them a try much earlier. First AOSP based ROM that seems to work ok, the audio is not quite there yet but still very usable with V4A enabled.
I tried to reproduce the issue that occurs when Wifi is off by trying the Wifi off <-> Wifi on toggle numerous times and I am able to get cellular data back without issues. I did do a clean wipe of my existing stock ROM before attempting to install the BrokenOS ROM, immediately followed by Gapps install. Not sure if that sequence of installation helped. I also noticed that first boot takes a good 5 to 10 minutes to complete.
So for folks out there looking for a decent third party ROM with lots of customization, the "unsupported" instance of BrokenOS looks ok. I will still revert back to CM13.1 whenever Unjustified Dev and DrakenFx complete their work.
One item to note is that the existing release of BrokenOS only has up to the August 5 security patches.
Click to expand...
Click to collapse
HI, do you know ifGPS is working on that ROM? On CM13 it doesn't seem to work or lock straight away so maps is quite laggy,
I need GPS so though I'd ask before flashing this custom ROM
borijess said:
What Gapps are you guys using for this? Link?
Click to expand...
Click to collapse
The origin of this version comes from Cyanogenmod forums. Look at this thread for more info on this alpha release, including GApps: https://forum.xda-developers.com/axon-7/how-to/available-zte-axon-7-lineage-14-1-t3530943
shia786 said:
HI, do you know ifGPS is working on that ROM? On CM13 it doesn't seem to work or lock straight away so maps is quite laggy,
I need GPS so though I'd ask before flashing this custom ROM
Click to expand...
Click to collapse
Are you asking about when it is on GPS only in settings?
I use high accuracy and don't have a problem.
QAM said:
So thanks to your input, I jumped in and installed the BrokenOS ROM. WOW, I now regret not giving them a try much earlier. First AOSP based ROM that seems to work ok, the audio is not quite there yet but still very usable with V4A enabled.
I tried to reproduce the issue that occurs when Wifi is off by trying the Wifi off <-> Wifi on toggle numerous times and I am able to get cellular data back without issues. I did do a clean wipe of my existing stock ROM before attempting to install the BrokenOS ROM, immediately followed by Gapps install. Not sure if that sequence of installation helped. I also noticed that first boot takes a good 5 to 10 minutes to complete.
So for folks out there looking for a decent third party ROM with lots of customization, the "unsupported" instance of BrokenOS looks ok. I will still revert back to CM13.1 whenever Unjustified Dev and DrakenFx complete their work.
One item to note is that the existing release of BrokenOS only has up to the August 5 security patches.
Click to expand...
Click to collapse
Where did you find the BrokenOS ROM for the Axon 7? Tried googling and going to their website but didn't find anything.