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
Related
I'm looking for a stable Android 4.0 or above ROM which can be flashed using Odin. Any threads or links?
zacszy said:
I'm looking for a stable Android 4.0 or above ROM which can be flashed using Odin. Any threads or links?
Click to expand...
Click to collapse
Well I am not aware of any 4.0 or above ROMs that can be flashed via ODIN. I am sure if any developer wants, they may be able to do it but I really think that flashing via recovery is always a better choice compared to ODIN. I see no advantage for ODIN flash...
Do you mind telling me why do you need odin flash???
Well..
thearif said:
Well I am not aware of any 4.0 or above ROMs that can be flashed via ODIN. I am sure if any developer wants, they may be able to do it but I really think that flashing via recovery is always a better choice compared to ODIN. I see no advantage for ODIN flash...
Do you mind telling me why do you need odin flash???
Click to expand...
Click to collapse
Well, I'm more familiar with Odin flashing compared to recovery mode, and it's a whole lot easier compared to other flashing methods. I don't find that the recovery mode is easy to understand, so you mind to provide me the steps (better if they are easier to understand and follow) and also a link to a stable Android 4.0 Rom?
zacszy said:
Well, I'm more familiar with Odin flashing compared to recovery mode, and it's a whole lot easier compared to other flashing methods. I don't find that the recovery mode is easy to understand, so you mind to provide me the steps (better if they are easier to understand and follow) and also a link to a stable Android 4.0 Rom?
Click to expand...
Click to collapse
Do you have root access on your phone? Every step is actually quite easy to follow. There are really good guides on both general and development sections. But beforewe delve into howto's you should clarify what constitutes STABLE for you...
We have ICS (4.04) as well as JB ( 4.1.2 and 4.2.2) in the development section. All are pretty good but here and there they may have some bugs. Just go to their threads check them out. On the very first page of a ROM thread what works and what doesn't are listed. Decide whether you can live with one of them then we can talk about howto's.
I recommend CM9, CM10 and CM10.1 all from the developer arco68...
OHHH with a custom recovery, you don't even need a computer to flash a new ROM. That surely is a bonus...
Sent from my GT-I8150 using xda app-developers app
Okay..
thearif said:
Do you have root access on your phone? Every step is actually quite easy to follow. There are really good guides on both general and development sections. But beforewe delve into howto's you should clarify what constitutes STABLE for you...
We have ICS (4.04) as well as JB ( 4.1.2 and 4.2.2) in the development section. All are pretty good but here and there they may have some bugs. Just go to their threads check them out. On the very first page of a ROM thread what works and what doesn't are listed. Decide whether you can live with one of them then we can talk about howto's.
I recommend CM9, CM10 and CM10.1 all from the developer arco68...
OHHH with a custom recovery, you don't even need a computer to flash a new ROM. That surely is a bonus...
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
I have root access on my phone. Well, I don't see the ROM thread that you mentioned. Stable means that the ROM is not easy to crash or eats up my RAM even when I'm not using it, while common bugs are still acceptable if they can be fixed (I can't find threads from arco68, so I don't know what you mean by his CM9 and all those so...)
Hope you can enlighten me more about this recovery method and the difference between the CMs (if possible, also include any differences between ICS and JB b'coz I don't know which one to choose)
Recovery is super easy:
Download the zip and put it on your SD (internal or external, makes no difference)
Then turn of your phone
Press and hold Volume up + Power button + home button
Once the screen turns on, release the power button, but keep holding onto the other two
Then the recovery menu shows up
choose install zip from SD
select the zip and hit install
finished
Here are the links, with more detailed instruction on how to do it
CM10.1
http://forum.xda-developers.com/showthread.php?t=2214042
CM10
http://forum.xda-developers.com/showthread.php?t=1990795
CM9
http://forum.xda-developers.com/showthread.php?t=1576874
Ups and downs?
Are there any down sides regarding the CM9 mod? And can I change the shortcuts on the lockscreen if I install CM9?
And also, what is CWM actually? I don't understand from the FAQs in the forums or other sites, so can you tell me what CWM is (CWM5 or CWM6) and how to access or install that?
Sorry, I'm really considered a total newbie in this sort of stuff 8(>o<)8
zacszy said:
Are there any down sides regarding the CM9 mod? And can I change the shortcuts on the lockscreen if I install CM9?
And also, what is CWM actually? I don't understand from the FAQs in the forums or other sites, so can you tell me what CWM is (CWM5 or CWM6) and how to access or install that?
Sorry, I'm really considered a total newbie in this sort of stuff 8(>o<)8
Click to expand...
Click to collapse
Its a kind of recovery, called ClockworkMOD. Now its the 6.0.3.0 version if I'm not wrong...
Linky: here
Okay, the process of installation of a custom recovery is tedious. Link: here DO NOT USE THE FILES IN THIS PAGE. JUST THE INSTRUCTIONS.
Now, flash the ROM (any of the three is fine. I personally recommend CM9 or 10 cus its in its RC stages, which means Resource... something)
The instructions is on the ROM page itself. And you're done. I or arco are not held responsible if your phone is screwed up in the process (very little chance) or
if your heart fails because its loading for a longer period than it should be.
HAVE FUN!
Sent from my 4.1 running Galaxy W.
iDelta said:
Now its the 6.0.3.0 version if I'm not mistaken.
Click to expand...
Click to collapse
In CM9, I see that the ClockworkMod needed is 5.5.xxxx, so wouldn't CM9 crash if i use the 6.0.3.0 version instead of 5.5.xxxx?
And also, does the CM9 have any bugs? Because I saw some in the posts by people about CM10 but not CM9 (refer to links of above comments)
Anyway, it is a pleasure to receive help from you and the person above.
zacszy said:
In CM9, I see that the ClockworkMod needed is 5.5.xxxx, so wouldn't CM9 crash if i use the 6.0.3.0 version instead of 5.5.xxxx?
And also, does the CM9 have any bugs? Because I saw some in the posts by people about CM10 but not CM9 (refer to links of above comments)
Anyway, it is a pleasure to receive help from you and the person above.
Click to expand...
Click to collapse
Well obviously, since its a custom ROM, its bound to have bugs. There's no such thing as a "perfect" ROM. And I have 6.0.1.something CWM and I have flashed every single ROM, from 9-10.1. So it shouldn't be a problem.
Sent from my 4.1 running Galaxy W.
zacszy said:
In CM9, I see that the ClockworkMod needed is 5.5.xxxx, so wouldn't CM9 crash if i use the 6.0.3.0 version instead of 5.5.xxxx?
And also, does the CM9 have any bugs? Because I saw some in the posts by people about CM10 but not CM9 (refer to links of above comments)
Anyway, it is a pleasure to receive help from you and the person above.
Click to expand...
Click to collapse
Man, if you want a stable rom, buy another phone.
iDelta said:
Well obviously, since its a custom ROM, its bound to have bugs. There's no such thing as a "perfect" ROM.
Click to expand...
Click to collapse
I believe I have caused some misinterpretation here. What I mean is that I want to know if there is anything that's not working in CM9. The stuff below is found from the CM9 thread.
What's working:
Audio
Receiving and making calls
GPS
Compass
Proximity sensor
Wifi
Bluetooth
USB mass storage
HW accelerated gui
HW accelerated video
Camera
Torch
Wifi and USB tethering
There isn't anything that's not shown as "not working", so I'm asking you about it just for confirmation.
If there isn't anything, I will flash CM9 soon. :laugh:
zacszy said:
I believe I have caused some misinterpretation here. What I mean is that I want to know if there is anything that's not working in CM9. The stuff below is found from the CM9 thread.
What's working:
Audio
Receiving and making calls
GPS
Compass
Proximity sensor
Wifi
Bluetooth
USB mass storage
HW accelerated gui
HW accelerated video
Camera
Torch
Wifi and USB tethering
There isn't anything that's not shown as "not working", so I'm asking you about it just for confirmation.
If there isn't anything, I will flash CM9 soon. :laugh:
Click to expand...
Click to collapse
Everything works fine.
For CM9 for sure.
Madzix said:
Everything works fine.
For CM9 for sure.
Click to expand...
Click to collapse
Yeah, CM9 is like the most stable out of the three... hardly any bugs
Sent from my 4.1 running Galaxy W.
iDelta said:
Its a kind of recovery, called ClockworkMOD. Now its the 6.0.3.0 version if I'm not wrong...
Linky: here
Okay, the process of installation of a custom recovery is tedious. Link: here DO NOT USE THE FILES IN THIS PAGE. JUST THE INSTRUCTIONS.
Now, flash the ROM (any of the three is fine. I personally recommend CM9 or 10 cus its in its RC stages, which means Resource... something)
The instructions is on the ROM page itself. And you're done. I or arco are not held responsible if your phone is screwed up in the process (very little chance) or
if your heart fails because its loading for a longer period than it should be.
HAVE FUN!
Sent from my 4.1 running Galaxy W.
Click to expand...
Click to collapse
I just noticed something in your post. Just to clarify, RC mean "Release Candidate" not resource something... Just so you know. First alpha's come, then beta's, and right before a FINAL version is released in which most of the bugs are squashed, a release candidate comes to make sure everything is working. If for example, no bugs remain in a release candidate, it is renamed to FINAL as far as I know
However, there are different understanding of these names on the internet. For example, for some, once a product is in a BETA phase, no more new features added from there on. However, that may not be true for CM releases here, I am not sure.
and @zacszy, both CM9 and CM10 are pretty stable. I have not encountered any show stopping bugs but that maybe because of the way I use my phone, as I dont play games. I use it mostly for productivity, internet surfing, couple of youtube videos, music...
Try them all. I am sure you will pick one that suits your needs..
thearif said:
both CM9 and CM10 are pretty stable. I have not encountered any show stopping bugs but that maybe because of the way I use my phone, as I dont play games. I use it mostly for productivity, internet surfing, couple of youtube videos, music...
Click to expand...
Click to collapse
Really appreciate your help @thearif and I would definitely try them out before really settling in with the CM I want
thearif said:
I just noticed something in your post. Just to clarify, RC mean "Release Candidate" not resource something... Just so you know. First alpha's come, then beta's, and right before a FINAL version is released in which most of the bugs are squashed, a release candidate comes to make sure everything is working. If for example, no bugs remain in a release candidate, it is renamed to FINAL as far as I know
However, there are different understanding of these names on the internet. For example, for some, once a product is in a BETA phase, no more new features added from there on. However, that may not be true for CM releases here, I am not sure.
and @zacszy, both CM9 and CM10 are pretty stable. I have not encountered any show stopping bugs but that maybe because of the way I use my phone, as I dont play games. I use it mostly for productivity, internet surfing, couple of youtube videos, music...
Try them all. I am sure you will pick one that suits your needs..
Click to expand...
Click to collapse
Thanks for the definition. Just saying, you can't call it fully stable cuz .... well that's impossible. It is only nearly stable.... you may have not said it but I'm just saying. Haha
Can your single core run 4.1? My Galaxy W can! That's how I sent this!
---------- Post added at 11:30 PM ---------- Previous post was at 11:29 PM ----------
zacszy said:
Really appreciate your help @thearif and I would definitely try them out before really settling in with the CM I want
Click to expand...
Click to collapse
Good luck :thumbup:
Can your single core run 4.1? My Galaxy W can! That's how I sent this!
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
Q&A for [ROM][4.4.4][TeamCanjica] CyanogenMod 11.0
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
question
Hi guys, i have a bug: calling history not show
Problem
It repeatedly giving error com.android.phone has unfortunately stopped . And the ROM is able to search the mobile networks but there is bar in signal strength . Means it not getting the signal .
Rest everything is ok .
PLease help me ASAP .
Does video recording work on your phone? Because I have camera app crashing all the time after switching to video.
Some Question about this ROM
Hi,
my Ace2 is still running under Stock Android 2.3.6. and I would like to Upgrade to CM.
For me stability and a working phone are more important than having the latest android Version, so my question is - which CM Version would you recommend? CM11 or is CM10.2 more stable? And is the latest version also the most stable one?
Is it correct that the only issue with CM11 is the Live streaming problem and with CM10.2 the memory leaks reported by some users- or are there more problems with these ROMS? A well working GPS is also important for me - is this the case?
And how difficult would it be to go back to stock 2.3.6. if CM is not working well for me?
Sorry for all the question and thanks in advance!
bootloop on the latest build from Rox
stuck on boot loop as is:
http://forum.xda-developers.com/showpost.php?p=56027724&postcount=5377
cm-11-20140807-UNOFFICIAL-codinap from @ace2nutzer
Install the firmware, reset the smartphone, then GAPS. If all at once, when you start on selecting the language setting is not. This, in my case, I tried several times. @ace2nutzer when to expect an update of your firmware
Hello
i have the i8160L,are the links you gave working on that version?
also if its working and i root that cm11,can i get back to my original firm later?
thanks
Bootloop
Rox, are you going to be fixing teh bootloop in the last build?
Also: the call log is empty, is there any fix for that?
Blackscreen
I want to record a logcat showing a black screen ocurring on wake up, with the s6d driver, in order to help in the resolution of the bug...
What's the priority level I should set for the catlog? Verbose, Debug, Info, Warnings, Errors, or Fatals?
Reboot loop with 1014 update
WARNING: I'm stuck in a reboot loop after updating to the recent 1014 version. Can't even get into recovery mode anymore. Flashed stock rom, installed CM again: same picture.
Grmblprmf said:
WARNING: I'm stuck in a reboot loop after updating to the recent 1014 version. Can't even get into recovery mode anymore. Flashed stock rom, installed CM again: same picture.
Click to expand...
Click to collapse
Flash chrono kernel..1014 build got a kernel broken...
@hackstorm1989
I have the GT-I8160L too.
This ROM specifically i haven't tried yet, but I've installed 2 different builds of NovaFusion CM11 (http://forum.xda-developers.com/showthread.php?t=2568105) and now I'm running J-TEAM AOSP (http://forum.xda-developers.com/showthread.php?t=2588054).
As TeamCanjica, both these ROMs are for the GT-I8160, but can be installed on GT-I8160L by changing the lines in the updater-script of the ROM (META-INF/GOOGLE/ANDROID/) where it checks the model of the device. I also read that the tee folder (system/lib/) of the ROM must be replaced by a copy of a tee folder from a running GT-I8160L firmware with SIM and carrier services properly working.
I've followed this guide:
http://brasildroid.com.br/showthread.php?t=23729
So, just by checking the updater-script of teamcanjica CM11, i GUESS it could be installed on GT-I8160L through the same 2 steps that i did with the other cited ROMs.
Also, I remember seeing other members running these ROMs on the L version while reading these 3 threads. I really wanna know what exactly differences are between these 2 device versions.
Please anyone let me know and correct me if I've posted any wrong information.
@soraxx
I can´t post in the main thread yet (10 post treshold), but maybe you read this or someone can copy this into the main thread.
I had exactly the same problem (audio but no video picture) and a simple change from stock browser to firefox solved it - Maybe it works for you too.
This should be main thread from now on
Same problem
Bootloop
14.10 bootloop
@ace2nutzer
I don´t agree with your statement that everything is working with the 07/08 build. I am using that build and the camera video recording is definitely bugged.
Elder666 said:
@ace2nutzer
I don´t agree with your statement that everything is working with the 07/08 build. I am using that build and the camera video recording is definitely bugged.
Click to expand...
Click to collapse
read this carefully:
http://forum.xda-developers.com/showpost.php?p=56171431&postcount=5436
Hi guys,
In stripped versions I notice camera quality and time of battery are worse... I'm going to try the build made for ace2nutzer 07-aug-2014 and stay on it by now.
Q&A for [ROM] [Alpha] Unoffcial CM12 for d2tmo
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] [Alpha] Unoffcial CM12 for d2tmo. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
CM12 for D2tmo
i installed CM12 but it does not detect my simcard PLZ help
Cant wait for new Lollipop roms!!!
Do you know if any time soon there will be a fix for mobile data?
thanks for effort
menace211 said:
Cant wait for new Lollipop roms!!!
Click to expand...
Click to collapse
Yeah, if they turn out like KitKat Roms I'm heading back to touchwiz jellybean, stock.
Liquidsmooth lollipop for S3
Hi,
Here are some builds for the S3, including the d2tmo. I've loaded the but had to go back to backup , there is a bug (black screen) with lollipop that i could not stay with it.
Sorry .. they did not allow me to put in the message an outside link to the downloads
Adam
fully functional work around to get lollipop on s3 d2tmo t999l
after doing a lot of research i have sucsesfully installed lollipop onto my s3 and got the camera to work with the camera for android app from the play store. the data also works the build i installed is the 12-20141125-unofficial-d2att after changing the script file to include d2tmo instead of the d2att. works great no real bugs except the time stamp on hangout mesages which is fixed by setting the time on the phone to network but turning of the reginal time set. thought this would be nice to share.
ps: stock camera and google camera still do not work but everything else does so this can be used as a daily driver links below to camera and build:
camera: https://play.google.com/store/apps/details?id=com.photo.android.camera&hl=en
build: http://forum.xda-developers.com/galaxy-s3-att/orig-development/cyanogenmod-12-t2944071
Added screen shots of apps used speed test and the edit that needs to be made to script file to make installable
lollipop for d2tmo install instructions
WHAT YOU NEED
the build location:
12-20141125-unofficial-d2att link: http://forum.xda-developers.com/galaxy-s3-att/orig-development/cyanogenmod-12-t2944071
in the same link is superSU
also will need gapps 5.0 lollipop
"camera for android" ( stock camera and google camera DOES NOT work)
link: https://play.google.com/store/apps/details?id=com.photo.android.camera&hl=en
total commander
instructions to exit the updater-script file to make the build installable on your d2tmo
1. open the file in total commander
2. META-INF> COM>GOOGLE>ANDROID
3. open and edit the updater-script by long pressing the file choosing unpack+edit
4. change d2att to d2tmo in the first line P.s. theres two words change both
5. go back and the editing is done now just wipe everything and flash just like any other rom the boot up takes about 8 to 9mins so dont worry about it being stuck in a loop, it isn't
do not forget to download superSU from the same link as the build and have gapps 5.0 when you flash
flash in this order: rom, gapps, superSU
important things that do work :
4g YES
bluetooth with android wear YES
gps YES
camera for android YES( stock camera NO google camera NO)
wifi YES
flash light YES
time needs to be adjusted(settings > date & time > check atumatic date & time (use network-provided time) uncheck automatic time zone, select time zone to finish time set)
sound YES
dsp YES
security YES unlocks only with power button (home button will not unlock your phone takes some getting use to)
keyboard YES
what was used to set up my phone: philz recovery, rescripted 12-20141125-UNOFFICIAL-d2att, superSU beta app,gapps 5.0, latest modem from xda for d2tmo t999L
leonid002 said:
after doing a lot of research i have sucsesfully installed lollipop onto my s3 and got the camera to work with the camera for android app from the play store. the data also works the build i installed is the 12-20141125-unofficial-d2att after changing the script file to include d2tmo instead of the d2att. works great no real bugs except the time stamp on hangout mesages which is fixed by setting the time on the phone to network but turning of the reginal time set. thought this would be nice to share.
ps: stock camera and google camera still do not work but everything else does so this can be used as a daily driver links below to camera and build:
camera: https://play.google.com/store/apps/details?id=com.photo.android.camera&hl=en
build: http://forum.xda-developers.com/galaxy-s3-att/orig-development/cyanogenmod-12-t2944071
Click to expand...
Click to collapse
Is it possible that you could upload d2att rom with changed script?
leonid002 said:
after doing a lot of research i have sucsesfully installed lollipop onto my s3 and got the camera to work with the camera for android app from the play store. the data also works the build i installed is the 12-20141125-unofficial-d2att after changing the script file to include d2tmo instead of the d2att. works great no real bugs except the time stamp on hangout mesages which is fixed by setting the time on the phone to network but turning of the reginal time set. thought this would be nice to share.
ps: stock camera and google camera still do not work but everything else does so this can be used as a daily driver links below to camera and build:
camera: https://play.google.com/store/apps/details?id=com.photo.android.camera&hl=en
build: http://forum.xda-developers.com/galaxy-s3-att/orig-development/cyanogenmod-12-t2944071
Added screen shots of apps used speed test and the edit that needs to be made to script file to make installable
Click to expand...
Click to collapse
Wiwee said:
Is it possible that you could upload d2att rom with changed script?
Click to expand...
Click to collapse
it looks like the file is too big to upload, here are the steps to edit the file manually, if you follow these you wont screw up
1. open the file in total comander
2. META-INF> COM>GOOGLE>ANDROID
3. open and edit the updater-script by long pressing the file choosing unpack+edit
4. change d2att to d2tmo in the first line P.s. theres two words change both
5. go back and the editing is done now just wipe everything and flash just like any other rom the boot up takes about 8 to 9mins so dont worry about it being stuck in a loop, it isnt
do not forget to download superSU from the same link as the build and have gapps 5.0 when you flash
flash in this order: rom, gapps, superSU
Wiwee said:
Is it possible that you could upload d2att rom with changed script?
Click to expand...
Click to collapse
files not uploading still sorry
leonid002 said:
files not uploading still sorry
Click to expand...
Click to collapse
I have determined I am an idiot. I downloaded the rom and tried to change the stuff you have listed and no love. If you have a chance to get it uploaded ( mega.co.nz with a public link maybe.....) please share would love to give it a shot.
PHP:
alarmdude9 said:
I have determined I am an idiot. I downloaded the rom and tried to change the stuff you have listed and no love. If you have a chance to get it uploaded ( mega.co.nz with a public link maybe.....) please share would love to give it a shot.
Click to expand...
Click to collapse
I'll get right on it thanks for the response,did it not let you flash it and say it's not compatible?
leonid002 said:
PHP:
I'll get right on it thanks for the response
Click to expand...
Click to collapse
No thank you for trying to help idiots like me. that is correct says not compatable
alarmdude9 said:
No thank you for trying to help idiots like me.
Click to expand...
Click to collapse
I got it to work at 3 in the morning so if I forgot something I'm sorry in advanced it's halfway uploaded right now with the changes in the script. Hope this helps. I also flashed with Philz recovery if that makes any difference
leonid002 said:
I got it to work at 3 in the morning so if I forgot something I'm sorry in advanced it's halfway uploaded right now with the changes in the script. Hope this helps. I also flashed with Philz recovery if that makes any difference
Click to expand...
Click to collapse
No apologies needed at all. Don't know if one version of the recovery matters or not. I know it did way back in the days of the CLIQ but I'm hoping not this far along
leonid002 said:
after doing a lot of research i have sucsesfully installed lollipop onto my s3 and got the camera to work with the camera for android app from the play store. the data also works the build i installed is the 12-20141125-unofficial-d2att after changing the script file to include d2tmo instead of the d2att. works great no real bugs except the time stamp on hangout mesages which is fixed by setting the time on the phone to network but turning of the reginal time set. thought this would be nice to share.
ps: stock camera and google camera still do not work but everything else does so this can be used as a daily driver links below to camera and build:
camera: https://play.google.com/store/apps/details?id=com.photo.android.camera&hl=en
build: http://forum.xda-developers.com/galaxy-s3-att/orig-development/cyanogenmod-12-t2944071
Added screen shots of apps used speed test and the edit that needs to be made to script file to make installable
lollipop for d2tmo install instructions
WHAT YOU NEED
the build location:
12-20141125-unofficial-d2att link: http://forum.xda-developers.com/galaxy-s3-att/orig-development/cyanogenmod-12-t2944071
in the same link is superSU
also will need gapps 5.0 lollipop
"camera for android" ( stock camera and google camera DOES NOT work)
link: https://play.google.com/store/apps/details?id=com.photo.android.camera&hl=en
total commander
instructions to exit the updater-script file to make the build installable on your d2tmo
1. open the file in total commander
2. META-INF> COM>GOOGLE>ANDROID
3. open and edit the updater-script by long pressing the file choosing unpack+edit
4. change d2att to d2tmo in the first line P.s. theres two words change both
5. go back and the editing is done now just wipe everything and flash just like any other rom the boot up takes about 8 to 9mins so dont worry about it being stuck in a loop, it isn't
do not forget to download superSU from the same link as the build and have gapps 5.0 when you flash
flash in this order: rom, gapps, superSU
Click to expand...
Click to collapse
alarmdude9 said:
No apologies needed at all. Don't know if one version of the recovery matters or not. I know it did way back in the days of the CLIQ but I'm hoping not this far along
Click to expand...
Click to collapse
https://mega.co.nz/#!8wdyVICK!ORYZsTOTdnXvgpEYVA6mJr9JbQJ0MCz_wFh8sA_xPNk
Try this I checked the file to make sure it was edited
leonid002 said:
https://mega.co.nz/#!8wdyVICK!ORYZsTOTdnXvgpEYVA6mJr9JbQJ0MCz_wFh8sA_xPNk
Try this I checked the file to make sure it was edited
Click to expand...
Click to collapse
awesome bringing it down now.
alarmdude9 said:
awesome bringing it down now.
Click to expand...
Click to collapse
so when you flash there should be a small error but it will continue flashing. let me know it goes
leonid002 said:
so when you flash there should be a small error but it will continue flashing. let me know it goes
Click to expand...
Click to collapse
Will do. Besides the camera everything else is working? Can't test it a lot tonight, just got called into work, but want to get it set up and a nandroid then play with it after work tomorrow.
alarmdude9 said:
Will do. Besides the camera everything else is working? Can't test it a lot tonight, just got called into work, but want to get it set up and a nandroid then play with it after work tomorrow.
Click to expand...
Click to collapse
when I first flashed the time for some reason was off but its pretty easy to fix, as for the camera install camera for android in the play store so you have some kind of working camera if that matters to you . everything else works perfectly a lot faster than the carbon ROM I had
Q&A for {GSM/CDMA}[DEVELOPMENT] -FXP130- CM7.2.0 - RELEASED - FreeXperia Project
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for {GSM/CDMA}[DEVELOPMENT] -FXP130- CM7.2.0 - RELEASED - FreeXperia Project. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Problem with Cyanogenmod 7.2 for XPeria Play (CDMA/Zeusc)
Cyanogenmod 9.1 works beautifully on my phone, but when I tried to install Cyanogenmod 7.2, the following error message keeps popping up immediately on the first boot: "the process com.android.phone has stopped unexpectedly"
I can't do much of anything else other than to keep closing the error message. I ended up putting Cyanogenmod 9.1 back on it, but I sure would like to try 7.2 to see how gingerbread 2.3.7 works.
Any help would be much appreciated.
Paul R said:
Cyanogenmod 9.1 works beautifully on my phone, but when I tried to install Cyanogenmod 7.2, the following error message keeps popping up immediately on the first boot: "the process com.android.phone has stopped unexpectedly"
I can't do much of anything else other than to keep closing the error message. I ended up putting Cyanogenmod 9.1 back on it, but I sure would like to try 7.2 to see how gingerbread 2.3.7 works.
Any help would be much appreciated.
Click to expand...
Click to collapse
Did some digging, and found this:
http://forum.xda-developers.com/showthread.php?p=28929283&highlight=my+version#post28929283
Agraceful's modified version works without issue. Also, I noticed that when booting into recovery after flashing the boot.img from his zip, using the volume keys works (just like cm9, just like described here: http://wiki.cyanogenmod.org/w/Install_CM_for_zeusc), where as with the official cm7.2, I had to use the home key to enter recovery.
cm is a lot nicer than stock gb, but why to use it on the gaming device like play, where gamepad doesnt work with this rom?
Paul R said:
Did some digging, and found this:
http://forum.xda-developers.com/showthread.php?p=28929283&highlight=my+version#post28929283
Agraceful's modified version works without issue. Also, I noticed that when booting into recovery after flashing the boot.img from his zip, using the volume keys works (just like cm9, just like described here: http://wiki.cyanogenmod.org/w/Install_CM_for_zeusc), where as with the official cm7.2, I had to use the home key to enter recovery.
Click to expand...
Click to collapse
did you try the cm7.3 or that's what they call it..
it was Created a lot later like almost end of 2013.. December..
its super stable and I love it cuz its super fast .. I would love to create a Modified kernel for it though.. with 200/700 Partition cuz the ram size is only like 90mb I think... Check this forum.. I have the Last post
http://forum.xda-developers.com/showthread.php?t=1128216&page=304
saqibkhan said:
did you try the cm7.3 or that's what they call it..
it was Created a lot later like almost end of 2013.. December..
its super stable and I love it cuz its super fast .. I would love to create a Modified kernel for it though.. with 200/700 Partition cuz the ram size is only like 90mb I think... Check this forum.. I have the Last post
http://forum.xda-developers.com/showthread.php?t=1128216&page=304
Click to expand...
Click to collapse
Haven't tried that yet, I'll definitely check it out. Thanks for that.
I'm running the latest nightly of Cyanogenmod 9. To be honest I don't know why it's a 'nightly,' I haven't had any problems with it. If anything it's better, because now FPSE works for me (I think the build.prop is different or something).
I would love to get a working version of Cyanogenmod 7 where the touchpads work with all my emulators. I'm mainly concerned about N64oid and ePSXe. I think the touchpads worked with agraceful's version of CM7 on ePSXe, but the circle button kept backing me out. N64oid ran super fast (much faster than CM9), but no touchpads.
There's all these cool gaming ROMs, but most of them are for r800i. Not too many options for r800x...
---------- Post added at 07:07 AM ---------- Previous post was at 06:58 AM ----------
Hmm... I checked out the link you were talking about, there's a file at the bottom called "
cm-7-20131222-FXP-zeus.zip".
I have r800x which is zeusc... would it be ok to put that on my phone, or is that a bad idea?
@Paul R I don't think so that would be a good idea.. maybe @darkharbinger might help us with this answer as I know he is working on a different version of a ROM for r800i..
and cm7 is faster then cm9 for the play.. I have tried that too..
if someone could help me (@Bakisha) in building a 210/700MB kernel for cm7 ROM as size is very small of the ROM even with Full Gapps and I don't like transferring APK.s to System as mostly they end up in FC's or errors..
saqibkhan said:
@Paul R I don't think so that would be a good idea.. maybe @darkharbinger might help us with this answer as I know he is working on a different version of a ROM for r800i..
and cm7 is faster then cm9 for the play.. I have tried that too..
if someone could help me (@Bakisha) in building a 210/700MB kernel for cm7 ROM as size is very small of the ROM even with Full Gapps and I don't like transferring APK.s to System as mostly they end up in FC's or errors..
Click to expand...
Click to collapse
I have another question. I was using Link2SD with Cyanogenmod 9 (the latest nightly) without issue.
But with Cyanogenmod 7.2, CWM Recovery does not recognize the sd-ext. It says "sd-ext not found, skipping sd-ext backup" or something like that.
Is there a way to make this work?
Also, sorry if this is a stupid question, but can I flash the CM9 kernel temporarily to backup and restore, then flash back to CM7? Or will this cause problems?
Edit: I just tried it. It worked fine, as far as I can tell. So, is there any way for me to install the version of Clockwork mod from CM9 onto CM7?