Related
Few n00b questions.
Firstly, how do i flash a nightly on my phone? lets say im running ofw 2.2 SEA edition? Do i follow the same procedure as if to flash RC1... do i also need to flash gapps similarly.
Secondly, are the links on quarxs' CM7 for defy thread up-to-date? or are there newer versions of gapps and nightlies floating around somewhere
Third, i have noticed that there is an issue with network and wi-fi when i flash cm7 RC1 over the nordic sbf. when i go back to official 2.2 SEA there is no hassle at all. Since i live in india i was wondering if that was the issue. I can easily take care of the network problem using "baseband switcher for defy" but it still doesnt help the wi-fi problem.
My question is.. will using the new BOOTSEA nightly solve this problem. I am assuming from the name is boot"SEA" im assuming its built southeastasia specific.
Fourth, ive used CM7 RC1 for a while and apart from the wifi issue i got problems with camera and video... it absolutely doesnt work, wether it be in potrait or landscape or whatever setting... the app just force closes. Any fixes for that.. ive got green lens.
please help!!! and i hope other similar questions can be added by members here so as to make this thread an FAQ for distressed users like me.
Thanks
deathw15h said:
Few n00b questions.
Firstly, how do i flash a nightly on my phone? lets say im running ofw 2.2 SEA edition? Do i follow the same procedure as if to flash RC1... do i also need to flash gapps similarly.
--> I'd say install RC1 and gapps first, then try a nightly by just wiping cache and Dalvik - no need to install gapps again since they're on your phone now. If you install a BOOT version and want to go back to an earlier CM7 nightly, then you might want to start from scratch, reflash froyo and install RC1 + gapps again.
Secondly, are the links on quarxs' CM7 for defy thread up-to-date? or are there newer versions of gapps and nightlies floating around somewhere
--> mostly up to date, but I don't worry about gapps too much as I believe that the Market gets updated automatically anyway (but I might be wrong about that). On the OP, the link to the gapps should show you up to date versions; but read the comments on there - very important.
Third, i have noticed that there is an issue with network and wi-fi when i flash cm7 RC1 over the nordic sbf. when i go back to official 2.2 SEA there is no hassle at all. Since i live in india i was wondering if that was the issue. I can easily take care of the network problem using "baseband switcher for defy" but it still doesnt help the wi-fi problem. My question is.. will using the new BOOTSEA nightly solve this problem. I am assuming from the name is boot"SEA" im assuming its built southeastasia specific.
---> same here my wifi DL speed was really bad for the last month or so on CM7; only after BOOT179-4 install, my wifi speed somewhat got back to normal.
Fourth, ive used CM7 RC1 for a while and apart from the wifi issue i got problems with camera and video... it absolutely doesnt work, wether it be in potrait or landscape or whatever setting... the app just force closes. Any fixes for that.. ive got green lens.
---> My camera and video worked on RC1 (and earlier) but video recording had some chopiness at times. Around July 11th nightly, Quarx released a camera fix (in that nightly) that solved the problem for me. But then days later, on newer nightly builds, I got the FC problem on video camera (same as you but red lens here). Then with BOOT179-4, camera was fine again and so the wifi speed; so all good for me.
--------> I really don't know what's going on with the video camera: many poeple have problems and many have it working on every nightly builds. It has been a problem from day one for Quarx on CM7-jordan... You have to try and see which build works for you I guess. And like you said, BOOT-SEA definitely looks like something you should try - many people liked it and many people say yesterday nightly is the best for them so far... so go on and have fun with testing
---> Before you do more testing though, you can always do a backup from the custom recovery so it will be easy for you to restore your current phone state -if nothing improves. I do this all the time: stock recovery factory reset, nordic flashing, RC1 install then restore my (BOOT179-4 now) backup.
Please help!!! and i hope other similar questions can be added by members here so as to make this thread an FAQ for distressed users like me.
---> I did try to help - I hope I did! If so, you can use that "Thanks" button - hehe!
---> Not sure that a thread entitled "nightly doubts" will become a very popular
FAQ thread though
Thanks
Click to expand...
Click to collapse
........................
[] AL [] said:
........................
Click to expand...
Click to collapse
thanks for all the help
There is a FAQ for flashing cm7 go and read it There is no need for threats like This
Send from my brain using Tapatalk
dumrul said:
There is a FAQ for flashing cm7 go and read it There is no need for threats like This
Send from my brain using Tapatalk
Click to expand...
Click to collapse
i went thru the whole FAQ but my doubts are regarding the nightlies which it doesnt address hence the thread.
thx for the concern though.
downloaded the BOOTSEA, but there is another file "cm7-110726-0018-BOOTSEA-Jordan.zip.md5sum" mentioned below it. ( there are similar md5sum files for all nightlies...) are they essential ? and how do i use them.
wanted to clarify before proceeding.
deathw15h said:
downloaded the BOOTSEA, but there is another file "cm7-110726-0018-BOOTSEA-Jordan.zip.md5sum" mentioned below it. ( there are similar md5sum files for all nightlies...) are they essential ? and how do i use them.
wanted to clarify before proceeding.
Click to expand...
Click to collapse
Md5 files are to verify your download is not corrupted one. Which you can compare the md5 after downloading the zip file and regenerating the md5 of downloaded file and check against the one in the server.
Sent from my MB525 using XDA App
deathw15h said:
thanks for all the help
Click to expand...
Click to collapse
No problem.
Go read here on the official CM7-jordan thread: http://forum.xda-developers.com/showthread.php?t=1033654&page=943
And from post 9429 particularily; pretty much goes in the same direction I was pointing at regarding the wifi and video camera...
How's the BOOTSEA doing for you?
The nightly ones is just the output that the ones who are working on the rom ups to us. Normally have all that part on topic that say "next version:..."
If you wanna try the nightly one, use as the *.zip that you download when got the "rc1 v2" for exemple. So wipe the phone, choose install from a zip of the sdcard and choose the *.zip, been it the rc1 or the nightly build.
The md5sum file is the one that contains the 5sum from the file. Its nornaly given when you have to download a big file and have fear to corrupt the file. If you use linux, go on terminal and type "5sum file" when file is the name of any file that you have. It will give you a big number. This is the 5sum. The *.md5sum have the 5sum of the respective *.zip nightly rom.
Sent from my MB525 using XDA App
how is the battery life with the nightly builds?
what android version is the 27/7 nightly build using? is it 2.3.5?
yup..its 2.3.5
I'm using this thread to share working pdroid patches I've got for various Galaxy Nexus roms. This was made using the patcher being developed here (patcher is in the 4th post). The patcher is currently linux-only, but will also work with cygwin in windows. I'm posting the finished flashable zip here as a convenience to anyone who can't use it themselves. Please note that I am not one of the people actively developing this patcher, just a willing tester who happens to own a toro Gnex.
If you don't know what Pdroid is, this is the thread for it on xda. Basically, it lets you deny permissions to apps on a per-permission basis, without risking apps crashing. Same basic idea as LBE privacy guard, but in my opinion executed better. Plus, open source is always a plus. Even though the official patcher there won't work for us yet, check the official thread. You'll need to download the app from the market and follow the same instructions, just using the zips I'll post here (or make your own).
I'll include a revert.zip for anything I post here, but please note that I take no responsibility for anything that happens to your phone. Make backups before flashing things. Try TWRP if you haven't, it's faster at backup/restore than CWR and does a bunch of other neat stuff like compressed backups and queued zip flashing. Also, in case of things breaking, please note that these revert zips are (1) only going to work if you are running the same rom used to create the zip and (2) just a slimmed down version of the rom's zip. What this means is that if you flash a pdroid zip and you need to revert, the surest thing to do is just re-flash your rom without wiping anything.
I'll try to update this thread as I get more patches working. Here's where my own experiments stand:
Link to my dropbox folder with files, notes below
Working patches:
-AOKP b39 (toro):
-AOKP b39 (maguro):
-CM9 Nightly: Patched build: 2012/06/19
--Note: Not sure if these will automatically fail with later nightlies or only when something relevant is updated in the rom. Feel free to try, just reflash your rom if it bootloops.
-Stock AOSP(+root, busybox): Patched build: 2012/06/02
-Paranoid Android v1.4a
Not Working (Yet):
-Liquidsmooth 1.5RC4:
-Slim ICS 4.0:
Unless otherwise noted, these are all for the toro (verizon) Galaxy Nexus. It's pretty quick and easy for me to make new patches so feel free to request something. But please be aware that sometimes it's a few days between when I can devote any time to this and don't be offended if I don't reply to you right away.
Just to reiterate, all you need to do for this is download the "Pdroid Patch Zip" file for your rom, flash it in recovery, and download Pdroid from Google Play.
Finally, be aware that the first boot after flashing can take a very long time, without any indication like the "Android is Upgrading..." screen. Don't assume it's bootlooping! Seriously, put the phone down and do something else for a bit. Anything in the tested section I've either personally flashed on my phone or someone else reported as working. If you're sure you're getting a bootloop on a clean install, my only advice is to do a full revert to stock and re-unlock/root/etc and see if it works then. Though rare, it is possible for something to be corrupt that persists across the usual "clean install" routine.
Isn't that what Permissions Denied does?
https://play.google.com/store/apps/details?id=com.stericson.permissions
Wow, I didn't realise you could patch AOKP on ICS yet. Have been waiting for this for so long. How would I go about applying your patch for AOKP gsm?
xternal said:
Wow, I didn't realise you could patch AOKP on ICS yet. Have been waiting for this for so long. How would I go about applying your patch for AOKP gsm?
Click to expand...
Click to collapse
For gsm you'd need a new patch. There are instructions in the first thread I linked to if you'd like to try it out. I might make one in a bit since I expect that to be a popular request and I expect it to work.
danger-rat said:
Isn't that what Permissions Denied does?
https://play.google.com/store/apps/details?id=com.stericson.permissions
Click to expand...
Click to collapse
Same idea, different approach. Permissions denied generally causes apps to crash if they need info that they are denied. I also had a major issue with it a while back that I ended up doing a factory reset for, but I think that's been fixed since then.
Not sure how pdroid gets around apps fc'ing (maybe it spoofs data so apps go on running normally? It has an option to set your own values I haven't played with much), but it works very smoothly.
xternal said:
Wow, I didn't realise you could patch AOKP on ICS yet. Have been waiting for this for so long. How would I go about applying your patch for AOKP gsm?
Click to expand...
Click to collapse
Quick update, I put up a maguro for AOKP, and I also updated the OP quite a bit since I last posted. Finally got around to testing the patches I made; getting better at reading the patching process as well to tell when a patch will work before flashing it, too.
At far as updates go, I don't really intend to follow the cm9 nightlies as I don't run them myself. I'll probably continue to try new versions of AOKP and paranoid android as they come out. I'll continue to try the roms that don't patch yet with new versions of the patcher as they are released.
Thank you. The maguro patch works for me.
Edit: not sure, but this likely breaks 2 apps: Listen, Drive.
I've been using LBE Privacy to control permissions and this app doesn't crash apps that have permissions blocked. It's one of their selling points, doesn't crash apps.
deaffob said:
I've been using LBE Privacy to control permissions and this app doesn't crash apps that have permissions blocked. It's one of their selling points, doesn't crash apps.
Click to expand...
Click to collapse
PDroid source has been released, whilst LBE created by a 'suspect' chinese company. I put the suspect in inverted comma's because nothing has actually been proven.
The patch works a treat on GSM aokp, many thanks
edit: looking at it though, it seems it doesn't find all the permissions correctly. I am assuming this is a limitation of the current pdroid as it is not designed for ics.
For instance it does not find hardware controls. Google Drive has access to hardware controls to take photos/videos.
Thanks for the confirmations on the maguro zip, I edited the post to reflect that it's definitely working.
I hadn't heard of LBE before making these threads but from what I've read it seems like people generally prefer pdroid. I'll check it out at some point but it looks like it does a bit more than I'd want it to, and pdroid being open source is definitely a plus.
IIRC, there's certain instances where apps can bypass LBE but not PDroid. I think reboot is one of those times due to when LBE loads.
I've been running LBE but lately the service keeps stopping because it doesn't get root soon enough after boot. Trying this now on Paranoid. Thanks!
i have used this patch for CM9 but after the Bootscreen have i a Blackscreen -.- what can i do?
SGDynamite said:
i have used this patch for CM9 but after the Bootscreen have i a Blackscreen -.- what can i do?
Click to expand...
Click to collapse
I'm guessing you are running a different build/more recent nightly? I might take that link down as it was meant as more of a proof of concept if the cm9 patcher was working and it's unlikely anyone is going to be flashing that particular build just to test pdroid.
The most effective thing would be to just re-flash the original rom's zip, you don't need to wipe anything. The revert zip file is basically just four files copied from a given rom's original zip, services.jar, core.jar and framework.jar in /system/framework, and build.prop in /system.
xternal said:
LBE created by a 'suspect' chinese company. I put the suspect in inverted comma's because nothing has actually been proven.
Click to expand...
Click to collapse
I hadn't heard of pdroid until I was on the Nexus, so I'm not familiar with it to compare, but I'm currently using LBE and blocking its data connections with Droidwall. Perhaps a bit overkill... but works great as far as I can tell.
Sent from my Galaxy Nexus using xda premium
JoeSyr said:
I'm guessing you are running a different build/more recent nightly? I might take that link down as it was meant as more of a proof of concept if the cm9 patcher was working and it's unlikely anyone is going to be flashing that particular build just to test pdroid.
The most effective thing would be to just re-flash the original rom's zip, you don't need to wipe anything. The revert zip file is basically just four files copied from a given rom's original zip, services.jar, core.jar and framework.jar in /system/framework, and build.prop in /system.
Click to expand...
Click to collapse
I think I flashed it to a nightly a day or two after 5-18 and it worked, but it definitely did not work on 5-27 or 5-29.
If the patch doesn't work for you, pull the battery, then hold volume up and down while you hold power, then use volume up and down to get to recovery option--press power to select. Either flash the revert or the old from there on top of the non-working one. Don't clear data partition and you won't lose anything.
@Joesyr, I think there is some interest in CM9 nightly patches...would you mind making a CM9 patch maybe once a week? I haven't had any luck making the patch on my own.
robjective said:
I think I flashed it to a nightly a day or two after 5-18 and it worked, but it definitely did not work on 5-27 or 5-29.
If the patch doesn't work for you, pull the battery, then hold volume up and down while you hold power, then use volume up and down to get to recovery option--press power to select. Either flash the revert or the old from there on top of the non-working one. Don't clear data partition and you won't lose anything.
@Joesyr, I think there is some interest in CM9 nightly patches...would you mind making a CM9 patch maybe once a week? I haven't had any luck making the patch on my own.
Click to expand...
Click to collapse
Well the last cm9 nightly I tried didn't patch at all (I believe it was a 5/29 build). I will try tinkering with things as I get the time but I'm not really at the level of fully understanding these kinds of failures yet.
Next time there's an updated cm9 patch I will try to get a working pdroid zip and I'll consider weekly updates. I'm also generally willing to make these on request as it's a pretty quick process. Fiddling with dropbox links is probably the longest part of any of this.
Any particular issue you're having with the patcher? I've been thinking I could write a little tutorial for getting cygwin up and running since I imagine that for most people the limiting factor is just that they don't have a linux environment to work in. But until I get the time to do that I can help troubleshoot.
Can you make a patch for stock root.
Thx
Has anybody experienced random rebooting? All was fine until I opened a non system app. Then it just started rebooting randomly after opening any app. I ran it on Maguro with AOKP b37.
soloxp said:
Can you make a patch for stock root.
Thx
Click to expand...
Click to collapse
Yup, not sure if the rom I just put up is the same you were looking for but it's the first one I've been able to get to patch correctly with the aosp patch.
Just flashed the Toro AOKP b37 patch, tested and working great here. Thank so much! Awesome work!!
** If you are interested in taking over the project, pm me **
Offical Site
XDA Forums
Google+
Twitter
Facebook
IRC(User)
JIRA
Disclaimer
Flash at your OWN Risk
How to Install
Install TWRP
Factory Reset
Format System
Install ROM
Install Google Apps
Install SuperSU
How to Update
Goto SuperSU -> Settings -> Install SuperSU backup script
Goto Settings -> About phone -> System Updates -> Check now
This will download and install latest OTA
DOWNLOAD
TWRP
ROM
Google Apps
SuperSU
Known Issues
Developer Stuff
COMPILE YOURSELF
Github
Gerrit
IRC(Dev)
Changelog​
XDA:DevDB Information
OmniROM, ROM for the Sprint Samsung Galaxy Note II
Contributors
UtkarshGupta, XpLoDWilD, Entropy512, OmniROM Team
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
ROM Firmware Required: SPH-L900
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: Nightlies
Created 2014-04-10
Last Updated 2014-12-08
Nice
My name is Skripka and I approve of this. :good:
Excited to try this out. Read up on OmniRom, I am particularly interested in the multi-workspace piece.
I just started working with JIRA at my workplace, I was just thinking today that it would be great for Rom developers.
Sent from my SPH-L900 using Tapatalk
this rom is really awesome; esp with plasma. nice to see it in development thread finally:good:
cmart4 said:
this rom is really awesome; esp with plasma. nice to see it in development thread finally:good:
Click to expand...
Click to collapse
Definitely might have to try this rom. It's either this or Paranoid.. not sure what the difference are Really want to get Plasma going though!
slick_rick said:
...
Known bugs:
- Check sbrissen's CM11 thread...
Click to expand...
Click to collapse
Out of curiosity, I thought that Cyanogen and Omni were separate since CM went commercial..? I thought that some of the CM devs (like Chainfire, XplodedWild, and Dees_Troy) were upset with that and decided to start their own ROM (hence OmniRom)...
Regardless, I'm very excited to see OmniRom has its own page now in our Android Development. It will make it much easier to see how each nightly performs and if there are any bugs that need to be reported.
Additionally, there's a lot of info/support/feature requests/etc here.
Thanks slick_rick!!
altimuh said:
Out of curiosity, I thought that Cyanogen and Omni were separate since CM went commercial..? I thought that some of the CM devs (like Chainfire, XplodedWild, and Dees_Troy) were upset with that and decided to start their own ROM (hence OmniRom)...
Regardless, I'm very excited to see OmniRom has its own page now in our Android Development. It will make it much easier to see how each nightly performs and if there are any bugs that need to be reported.
Additionally, there's a lot of info/support/feature requests/etc here.
Thanks slick_rick!!
Click to expand...
Click to collapse
They are separate for the most part but I am using sbrissens cm11 device tree as a base for omni l900 tree so any bugs there will be here.
Sent from my Nexus 7 using Tapatalk
slick_rick said:
They are separate for the most part but I am using sbrissens cm11 device tree as a base for omni l900 tree so any bugs there will be here.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
On Omni's page they talk about mulitwindow being up to the individual dev who brings it to each device. Is it possible to get that added in the future, or is that going to be up to Omni?
Thanks for the info and thanks for your hard work!!
Thanks for all your hard work and not given up on us like people's. Just downloaded and look forward to trying it out. On a side note I've been spending all my free time in the XDA University forums trying to teach myself how to compile and build. I've got Ubuntu and all the tools but having a 14 month old son n being a single dad in the evenings haven't given me much free time to practice and read.
So i can appreciate all the time and effort you put in to doing this all.
Thank you slick-rick for this great ROM. For me, everything is running flawlessly so far but I have a question. I used Phil's Touch to install the ROM originally and as I mentioned it's running great. This morning I checked for an update and there is a new nightly available. When I went through the process to install the nightly it said that it was only compatible with TWRP. Is this correct, or is it OK to continue with the installation even though I have Phil's Touch? Thank you again for all your work.
Sent from my SPH-L900 using XDA Premium 4 mobile app
davesbest said:
Thank you slick-rick for this great ROM. For me, everything is running flawlessly so far but I have a question. I used Phil's Touch to install the ROM originally and as I mentioned it's running great. This morning I checked for an update and there is a new nightly available. When I went through the process to install the nightly it said that it was only compatible with TWRP. Is this correct, or is it OK to continue with the installation even though I have Phil's Touch? Thank you again for all your work.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Which Nightly did you install? Any nightly build after 1/10 or so should be able to OpenDelta update script via PhilZ/CWM just fine.
Skripka said:
Which Nightly did you install? Any nightly build after 1/10 or so should be able to OpenDelta update script via PhilZ/CWM just fine.
Click to expand...
Click to collapse
I haven't installed a nightly yet. I was waiting to make sure i could do it with phils. Thank you so much for the help. Going to install it now.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Well, that didn't go so good. When I go to system update and do "flash now," it boots to philz recovery but I keep getting "installation aborted" messages. Any ideas?
Thanks. Dave.
Sent from my SPH-L900 using XDA Premium 4 mobile app
SuperSU won't allow me to update binary and tried to use root explorer stated that I didn't have root. ?
Sent from my Transformer TF101 using Tapatalk
Is anyone else getting high Google Services usage? It's the highest usage listed in the battery settings
EGOvoruhk said:
Is anyone else getting high Google Services usage? It's the highest usage listed in the battery settings
Click to expand...
Click to collapse
Check your wakelocks...I saw it and made it go away by changing location to "Device only".
'no service' issue
I had this rom running for a couple of days, then had an issue with an app (xbmc), and decided to go back to macksrom....didn't realize that once you install 4.4.2, you can't go back to 4.1.2...anyway after trying to restore to macksrom failed twice on the data restore, I went ahead and reloaded omnirom, and worked through the xbmc issue....didn't realize until my wife found me at the grocery store that after bringing it back via restore I had no service...and I couldn't find anyway to get service either....
Is this a known issue, or do you know if I did something wrong?
---------- Post added at 07:41 PM ---------- Previous post was at 07:20 PM ----------
hinesw said:
I had this rom running for a couple of days, then had an issue with an app (xbmc), and decided to go back to macksrom....didn't realize that once you install 4.4.2, you can't go back to 4.1.2...anyway after trying to restore to macksrom failed twice on the data restore, I went ahead and reloaded omnirom, and worked through the xbmc issue....didn't realize until my wife found me at the grocery store that after bringing it back via restore I had no service...and I couldn't find anyway to get service either....
Is this a known issue, or do you know if I did something wrong?
Click to expand...
Click to collapse
Just did a complete re-install of the omnirom zip file....seems to be back to normal. Of course, now I have to get all my apps back on and placed the way I like 'em....oh well.
Skripka said:
Check your wakelocks...I saw it and made it go away by changing location to "Device only".
Click to expand...
Click to collapse
Tried this for two days - one mostly on WiFi and one out and about. First day on WiFi I got waaaaaaay better battery, but the second day I got not so good results with Google maps - it took a while to "find my location"....also with location set to 'Device Only', I got high battery use from the weather channel app I have installed, and Dashclock widget can't find my geo location and report.... I think I'll take the slightly higher battery drain with a fully functioning GPS setting.
Thanks for the tip though - it could be super handy for someone mostly on WiFi.
altimuh said:
Tried this for two days - one mostly on WiFi and one out and about. First day on WiFi I got waaaaaaay better battery, but the second day I got not so good results with Google maps - it took a while to "find my location"....also with location set to 'Device Only', I got high battery use from the weather channel app I have installed, and Dashclock widget can't find my geo location and report.... I think I'll take the slightly higher battery drain with a fully functioning GPS setting.
Thanks for the tip though - it could be super handy for someone mostly on WiFi.
Click to expand...
Click to collapse
If you're not traveling, just set DashClock's location manually. Can't vouch for Weather Channel's app, but Weatherbug Elite plays fine with it and doesn't care.
The location pinging with Google Now is insane...and there's no way I know to stop the thousands of location wakelocks short of changing the location preference. Not even changing the app permissions for the location services does any good. And that isn't just an OmniROM issue, but for ever 4.4 ROM I know of.
They are released officially und http://download.cyanogenmod.com/?device=n1 :victory:
With the lastest "cm-11-20140126-NIGHTLY-n1.zip" I get no location data - wich makes the N1 unusable for Maps, Foursquare, Ingress aso..
Switches back to "cm-11-20140124-NIGHTLY-n1.zip" everything works fine again.
Flash with stock recovery?
Is there a way to flash a nightly build with the sotck recovery? If not how to change the recovery? Thx
dryll said:
Is there a way to flash a nightly build with the sotck recovery? If not how to change the recovery? Thx
Click to expand...
Click to collapse
You will not be able to flash this with the stock recovery. I imagine once it goes stable CM will push out an official update that will work on the stock recovery setup.
Until then, TWRP works great: http://forum.xda-developers.com/showthread.php?t=2537080
dryll said:
Is there a way to flash a nightly build with the sotck recovery? If not how to change the recovery? Thx
Click to expand...
Click to collapse
I bet I could make that happen. Probably just a reverse of what I do to make it flash in TWRP instead of stock. I bet I could add the first line back in and have it flash properly.
Harfainx said:
I bet I could make that happen. Probably just a reverse of what I do to make it flash in TWRP instead of stock. I bet I could add the first line back in and have it flash properly.
Click to expand...
Click to collapse
Flashify works great for installing TWRP, just backup your stock recovery first, that way you can flash it back before rebooting recovery and flashing colour OS. 27th Nightly is available.
mcteague said:
Flashify works great for installing TWRP, just backup your stock recovery first, that way you can flash it back before rebooting recovery and flashing colour OS. 27th Nightly is available.
Click to expand...
Click to collapse
I meant flash nightlies in stock recovery. I have TWRP on mine, but I bounce back and forth for testing.
Sent from my N1 using Tapatalk
Harfainx said:
I meant flash nightlies in stock recovery. I have TWRP on mine, but I bounce back and forth for testing.
Sent from my N1 using Tapatalk
Click to expand...
Click to collapse
I'm 90% certain stock recovery will not flash nightlies, as it will only flash ZIPs signed with specific signing keys.
Unless CM is signing their nightly ZIPs with the same key as their "official" releases, which is highly unlikely.
Entropy512 said:
I'm 90% certain stock recovery will not flash nightlies, as it will only flash ZIPs signed with specific signing keys.
Unless CM is signing their nightly ZIPs with the same key as their "official" releases, which is highly unlikely.
Click to expand...
Click to collapse
Correct. Currently since they're coming direct from CM as nightlies, they aren't final stable versions. Those will be released like the other two were, and I'm sure will be built to flash in the N1 Stock Recovery.
Location not working
location still not working on latest nightly (130214).
anyone has any idea on how to fix it? the 240114 nightly is not longer on the getCM servers.
Anyone on M6? Thoughts?
I went straight from CM10.2 (CM edition N1) to 11 M6, so I don't know how battery life compares with Omni or other ROMs... would love to hear from those of you that have tried other ROMs and can compare with M6.
With M6, I am getting ~4% battery drain over 7 hours overnight (2G network on only).
All People Update CM. there is the cm-11-20140724-NIGHTLY
First update to the latest nightly in CM page, after that you can update via OTA in your phone, there is Daily updates!!
O-Click, Works, meaby a second lag (while focusing?)
O-Touch Works, not as the touchpad of your lap but works, And for some reason changing the VM to ART works better for me.
3G works
Battery last very good, and its suposed to las more in stand-by if you use ART instead of Dalvik
ART works well by the way.
ThommmF said:
They are released officially und http://download.cyanogenmod.com/?device=n1 :victory:
With the lastest "cm-11-20140126-NIGHTLY-n1.zip" I get no location data - wich makes the N1 unusable for Maps, Foursquare, Ingress aso..
Switches back to "cm-11-20140124-NIGHTLY-n1.zip" everything works fine again.
Click to expand...
Click to collapse
Hi,
I am trying to install Cyanogend mod. N1 a OPPO
The steps are simple, but not working,
I've tried: (http://download.cyanogenmod.com/?device=n1&type=snapshot)
** Cm-11-20140804-SNAPSHOT-M9-n1
cm-11-20140805-NIGHTLY-N1
cm-11-20140124-EXPERIMENTAL-n1.zip
They all show the same error.
"Installation failed"
I downloaded the. zip for wifi, ethernet MAC, WINDOWS ........ and still shows the same error.
:crying:
ThommmF said:
They are released officially und http://download.cyanogenmod.com/?device=n1 :victory:
With the lastest "cm-11-20140126-NIGHTLY-n1.zip" I get no location data - wich makes the N1 unusable for Maps, Foursquare, Ingress aso..
Switches back to "cm-11-20140124-NIGHTLY-n1.zip" everything works fine again.
Click to expand...
Click to collapse
Sorry to bump a 3 year old thread for such an unrelated reason, but you have PMs disabled, and, well, CM11 is not that appealing anymore so I'm confident not many people are gonna read this anyway [any mods reading this, please spare my soul :silly: ]
That said, I just wanted to ask you why you rated my porting of LAOS 15 Trebuchet so poorly, since you didn't leave any comment; if it's some bug, crash or other error i can look into it.
BTW you can answer me on the app's thread if you wish (https://forum.xda-developers.com/android/apps-games/app-lineageos-15-trebuchet-laucher-rom-t3667436)
ThommmF said:
They are released officially und http://download.cyanogenmod.com/?device=n1 :victory:
With the lastest "cm-11-20140126-NIGHTLY-n1.zip" I get no location data - wich makes the N1 unusable for Maps, Foursquare, Ingress aso..
Switches back to "cm-11-20140124-NIGHTLY-n1.zip" everything works fine again.
Click to expand...
Click to collapse
Thank you for leaving your feedback, here are some answers to your points:
- (update mechanism) i actually caught a nasty bug in XDA Labs web console which prevents me from uploading new builds there (and I also deleted all previous reviews in the attempt to reupload the app ??); (i already filed a bug report and managed to get the dev's attention so I hope it gets fixed soon)
- (open source) being a porting, the app mostly shares the original staging/trebuchet15.1 source code, with only a handful edits for fixing crashes due to compatibility errors (and is built with gradle plugin 2.3.3 instead of 3.0.1)
- (very buggy) it inherits all current staging/trebuchet15.1 bugs, not that much from my tests, but yes, there are some
I have tested these roms on my find 7a and they work great. I'm not sure of these will work with find 7 so please do a nand backup and report back in the thread if it works. Credits to the devs for these releases.
Asylum_Omni
AOKP Official Nightlies
NamelessROM Nightlies
Asylum-omni!
That reminds me of my Note 1 days. Deff getting this now.... Is there an asylum thread about?
shure2 said:
Asylum-omni!
That reminds me of my Note 1 days. Deff getting this now.... Is there an asylum thread about?
Click to expand...
Click to collapse
I found the roms by browsing goo.im but I don't think there are any threads for either rom besides this one for now
uppon2 said:
I found the roms by browsing goo.im but I don't think there are any threads for either rom besides this one for now
Click to expand...
Click to collapse
Thanks for sharing. I know Chas has set up a thread or two on XDA before so I'll patiently wait for him to start one up.
Anyone tried this?http://androxfer.in/get.php?p=AOKP-....zip&utm_medium=referral&utm_source=pulsenews
Apparently it works on 7a
I will give it a shot now
Edit* This appears to be the same as the one I linked in the OP but a newer build from Dirk. I am assuming this has now gone in to an official status as I can find it on the AOKP site. OP has been updated with the official site being the link - Thank you for pointing it out as it has now made me realise it was official! - I remember seeing a post from Dirk on Google+ about it being supported but I had forgotten to keep an eye out on the actual AOKP site.
Also added official CM nightlies to OP
Do any of this work with the Find7 (not 7a)?
jampola said:
Do any of this work with the Find7 (not 7a)?
Click to expand...
Click to collapse
I'm not sure. You could make a nand backup then try if you want. I think as soon as there is an AOSP rom built for the find 7 QHD you could use the kernel from that and put it in roms built for find 7a and everything should be fine. Until then it might not function at 100 percent.
Thanks for posting the links dude!
So the AOKP nightly for the FInd 7, that's for the "Find 7" not the 7a? And is it for the 9077? AOKP doesn't specify the device model
Cheers
TheSmokingAndroid said:
Thanks for posting the links dude!
So the AOKP nightly for the FInd 7, that's for the "Find 7" not the 7a? And is it for the 9077? AOKP doesn't specify the device model
Cheers
Click to expand...
Click to collapse
Well Dirk Rettschlag has mentioned it here as the Find 7 but I have used the version displayed in the screenshot from his G+ plus the release on the official AOKP site which also lists it as Find 7 on my Find 7a and it works perfectly. Do a nand backup and have a shot at testing it?
DOES IT WORK?
Find 7 (x9076) compatibility?
Is it compatible with the QHD Find 7?
Anyone having SU issues on the latest Nameless nightly?
JRW 28 said:
Anyone having SU issues on the latest Nameless nightly?
Click to expand...
Click to collapse
What issues are you facing?
uppon2 said:
What issues are you facing?
Click to expand...
Click to collapse
SuperSU kept force closing and was non responsive at all both times I installed the ROM on clean installs. Could get no root features or root apps to work?
I've seen this before as SuperSU needed the binaries updated but I could get no progress with it??
JRW 28 said:
SuperSU kept force closing and was non responsive at all both times I installed the ROM on clean installs. Could get no root features or root apps to work?
I've seen this before as SuperSU needed the binaries updated but I could get no progress with it??
Click to expand...
Click to collapse
Try downloading superuser by clockwork and busybox by Stephen and use those and see how that plays out
uppon2 said:
Try downloading superuser by chainfire and busybox by Stephen and use those and see how that plays out
Click to expand...
Click to collapse
Didn't even think about that. Thanks. Running C-Rom right now as I liked it on my S4. Just getting used to this phone. A big upgrade from the S4!
JRW 28 said:
Didn't even think about that. Thanks. Running C-Rom right now as I liked it on my S4. Just getting used to this phone. A big upgrade from the S4!
Click to expand...
Click to collapse
I liked C-Rom but it gave me issues installing it. Every time I tried to run it it would not pass the boot animation; after 10 minutes of it sitting there the same thing would happen on reboot. The only way I got it to work was by dirty flashing over the top of itself. After installing all of my apps i went to reboot and upon pressing and holding the power button it forced a hot reboot that would not pass the boot animation. I gave up after trying this a few times. I didn't report this to the dev as he has lots of stuff going on.
uppon2 said:
I liked C-Rom but it gave me issues installing it. Every time I tried to run it it would not pass the boot animation; after 10 minutes of it sitting there the same thing would happen on reboot. The only way I got it to work was by dirty flashing over the top of itself. After installing all of my apps i went to reboot and upon pressing and holding the power button it forced a hot reboot that would not pass the boot animation. I gave up after trying this a few times. I didn't report this to the dev as he has lots of stuff going on.
Click to expand...
Click to collapse
Had similar issues first time I tried booting C-Rom. When I seen Nameless on the Oppo forums their instructions added wipe system after full wipe an it seems to be working good like that. I now factory reset, then wipe system, dalvik and cache under advanced and it seems to be working fine like that
JRW 28 said:
Had similar issues first time I tried booting C-Rom. When I seen Nameless on the Oppo forums their instructions added wipe system after full wipe an it seems to be working good like that. I now factory reset, then wipe system, dalvik and cache under advanced and it seems to be working fine like that
Click to expand...
Click to collapse
I have always formatted system. Most roms will have it in the script but I have always done it manually