Related
I'm trying to install Hyperdrive RLS10. The flash instructions say to install an AT&T build prop and I've also seen users mention that you will need to fix the google client database for the rom to function properly on AT&T. I can not locate any AT&T build prop to flash and do not know how to fix the google client database. Would anyone be able to help me so that I can get this rom working properly?
mrpoe222 said:
I'm trying to install Hyperdrive RLS10. The flash instructions say to install an AT&T build prop and I've also seen users mention that you will need to fix the google client database for the rom to function properly on AT&T. I can not locate any AT&T build prop to flash and do not know how to fix the google client database. Would anyone be able to help me so that I can get this rom working properly?
Click to expand...
Click to collapse
If you don't know how to do those, you might wanna look into flashing a AT&T ROM first and learn more about what you're attempting to do. (Google is a good friend)
P.S.: Please, don't double post.
BWolf56 said:
If you don't know how to do those, you might wanna look into flashing a AT&T ROM first and learn more about what you're attempting to do. (Google is a good friend)
P.S.: Please, don't double post.
Click to expand...
Click to collapse
I'm aware of what I'm attempting to do. The build prop on this rom needs to be edited or replaced or reflect AT&T since the rom base is Verizon. I'm not new to flashing roms; I've just never had to edit/replace a build.prop for a rom port from another carrier. I've searched google and the rom thread before posting this question. I'm just trying to see if anyone else from the community would be able to advise me what edits I would need to make to the build.prop or if they could help point me in the right direction for a build.prop zip that I could flash through TWRP. I expected the typical "why don't you just google it" response, but was hoping that someone would be helpful enough to actually assist me.
P.S.: I only started this thread after I realized my original post was in a thread with little to no activity.
mrpoe222 said:
I'm aware of what I'm attempting to do. The build prop on this rom needs to be edited or replaced or reflect AT&T since the rom base is Verizon. I'm not new to flashing roms; I've just never had to edit/replace a build.prop for a rom port from another carrier. I've searched google and the rom thread before posting this question. I'm just trying to see if anyone else from the community would be able to advise me what edits I would need to make to the build.prop or if they could help point me in the right direction for a build.prop zip that I could flash through TWRP. I expected the typical "why don't you just google it" response, but was hoping that someone would be helpful enough to actually assist me.
P.S.: I only started this thread after I realized my original post was in a thread with little to no activity.
Click to expand...
Click to collapse
I didn't mean to sound like ''Why don't you just google it''. You gave really low information on your experience and such, therefor, I made a safe suggestion.
Basically, you have to change the phone model to SGH-I747 in the build.prop file with something like notepad.
As for the other part, I have no idea, and this time, google will actually be helpful as I'm sure people attempted this before.
BWolf56 said:
I didn't mean to sound like ''Why don't you just google it''. You gave really low information on your experience and such, therefor, I made a safe suggestion.
Basically, you have to change the phone model to SGH-I747 in the build.prop file with something like notepad.
As for the other part, I have no idea, and this time, google will actually be helpful as I'm sure people attempted this before.
Click to expand...
Click to collapse
I was able to locate the build.prop edits buried in a thread about google wallet. I'm still not sure about the other part, but I have the rom up and running on at&t LTE with no issues. I appreciate your patience. I try to search as thoroughly as I can, unfortunately, work often gets in the way.
mrpoe222 said:
I was able to locate the build.prop edits buried in a thread about google wallet. I'm still not sure about the other part, but I have the rom up and running on at&t LTE with no issues. I appreciate your patience. I try to search as thoroughly as I can, unfortunately, work often gets in the way.
Click to expand...
Click to collapse
Clearing client database means clearing data and cache in the play store app. That's what worked for me on with that issue...or loading another Google account then deleting it then adding your main one.
Verizon Galaxy S3 running RLS10 - call echo issue
Hey, first of all I wanted to say to the developers of the Hyperdrive RLS ROM, this has become one of my preferred ROMS - great stability, battery life, etc. I just upgraded from RLS9 to RLS10. FYI, I always wipe everything prior to installing a ROM. Anyway, installation went off without a hitch and the ROM runs great, but since I upgraded to this ROM, I am getting an echo with every single call even with bluetooth. Not sure if anyone else is having this issue, and if there's a fix for it? Would appreciate any feedback! Thanks, and thank you to the developers for all the work you do.
jpc477 said:
Hey, first of all I wanted to say to the developers of the Hyperdrive RLS ROM, this has become one of my preferred ROMS - great stability, battery life, etc. I just upgraded from RLS9 to RLS10. FYI, I always wipe everything prior to installing a ROM. Anyway, installation went off without a hitch and the ROM runs great, but since I upgraded to this ROM, I am getting an echo with every single call even with bluetooth. Not sure if anyone else is having this issue, and if there's a fix for it? Would appreciate any feedback! Thanks, and thank you to the developers for all the work you do.
Click to expand...
Click to collapse
the echo is just on your end, correct?
go to settings >accessibility and make sure turn off all sounds is not checked to begin with. now go to settings > sound and make sure your volume levels are correct and sound is turned on.
also, phone > menu > Call settings > additional settings and then uncheck noise reduction. some people have reported less echo and clearer calls with this turned off.
jpc477 said:
Hey, first of all I wanted to say to the developers of the Hyperdrive RLS ROM, this has become one of my preferred ROMS - great stability, battery life, etc. I just upgraded from RLS9 to RLS10. FYI, I always wipe everything prior to installing a ROM. Anyway, installation went off without a hitch and the ROM runs great, but since I upgraded to this ROM, I am getting an echo with every single call even with bluetooth. Not sure if anyone else is having this issue, and if there's a fix for it? Would appreciate any feedback! Thanks, and thank you to the developers for all the work you do.
Click to expand...
Click to collapse
A few have reported the same issue on the thread but no real solution beyond hit speaker on then off and it goes away. Reason that works ? I have no clue.
Hi,
I am really full of compliments about the good work of some guys that have done a good job in building the actual CyanogenMod versions for Wildfire S.
Thank you sooo much!!
But what I currently do not completly understand...
Why are most of the CM users really happy about version 10.2 or version 11.0 (like orig. CyanogenMod or WFSY) when those versions - last version of CM 9.2.2 included - do not even have GooglePlay/PlayStore and Data2SD (or Link2SD) installed?...
The last (and obviously most advanced CM version) CM9 (alpha9, v.9.2.2) would already be a wonderful solution for the WFS phone (I tested it!!) and it is said to be nearly finished (even video camera is working now at the version of Olivier) BUT both mentioned, absolutly necessary components are missing (and nobody mentioned it yet). Or what can I do with a phone where I cannot install new apps at all?..
So what is it that I misunderstand?...
I would be very happy if anybody could inform me about how I can find a version that has a complete set of system apps or how/where I can find both missing components to complete them by myself. (and even more happy if the cyanogenmod update function would still find some updates)
Otherwise I would guess that not any of the existing CM-based versions for Wildfire S can be used at all...
Should all the past work for creating a CM version (Android 4.x !!) for the (unfortunately!) one and only COMPACT smartphone on the world, 'Wildfire S' (I must admit, it is in fact!!) should have been completly in vain ???... I couldn't believe it.
Thank you guys very much for your nice explanations!
All the best to this wonderful community,
from Falk
CyanogenMod said:
Google Apps are the proprietary Google-branded applications that come pre-installed with most Android devices, such as the Play Store, Gmail, Maps, etc. Due to licensing restrictions, these apps cannot come pre-installed with CyanogenMod and must be installed separately.
Click to expand...
Click to collapse
Gesendet von meinem Xperia Z mit Tapatalk
Hi Olivier,
many thanks for your tip. You did not mention the point directly but I could answer most of my questions by mayself then.
Now I installed CM9 'cm-9-20140720-Olivier-marvel' together with 'CronMod-INT2EXT+_signed'. Works pretty fine!
Only little questions have been left now...
1.) How can I sort my app icons by subjects/folders (s. HTC Sense)? This Trebuchet launcher does not seem to support anything like that. If there is no chance, which launcher would you suggest instead?
2.) There is no really 'useful' version of CM10 or CM11 for WFS yet, is there? I couldn't find. Do you think there will be s.o. still working for a final version next time?... (why is Wildfire but not Wildfire S an official CM development?)
2b.) At your current version CM9, is there any problem left that should still be fixed? Everything works fine here yet...
3.) Therefore the OTA updater for CM would be a fine feature like in CM9 vers. 9.1.0 (but no updates found yet!). But your current CM9 version does not support it any more. Any reason for that?
3a.) Are updates possible anyway without flashing the whole ROM?
3b.) Is there anybody managing OTA any update of CM (v. 9..11) for WFS?
3c.) Are OTA updates from cm9 to cm11 possible?
4.) Skype does not react when clicking the icon to start it. Any idea what is the problem?...
5.) Some system programs (e.g. contacts or call manager) do not have that nice design than before. There is no chance/choice to exchange them?... (if yes, how and where to find alternatives?)
Thank you again for your final responses!
First of all this really does not belong in the development section, in Q&A perhaps.
And you just can't ask every single think that comes up in your mind, you gotta search a little bit and try it out for yourself.
Now, 1. Trebuchet does support folders but not auto-arranging. Most of the popular launchers support this.
2. The current CM10 and CM11 are perfectly functional and working. Though they lag a bit (which is fair considering our old device). And the wildfire only had an official CM7 which is very old now.
2b. If you don't have a problem it does not contain a problem.
3. OTA is working for CM11. But for CM9 a OTA makes less sense considering that its stable now.
4. No idea.
5. Again you have to look for yourself, nobody can babysit you all the time.
thanks very much!
Okay, maybe question 1 might belong to Q&A. That's it. Sorry.
To make you understanding (sorry to write again so much!)...
to 1.) Did not expect that it would support it. So I did not even search for!... Thanks, this drag/drop solution is more than perfect!!
to 2.) Sorry, then I am not able to find them. I searched a lot and found actual version like 'WFSY11.0-WFS-V5.5, 20140723' or 'cm-11-20140726-NIGHTLY-marvel' where not even back button or Android option menu worked. Lots of functions are missing. I did not try 'cm-11-20140810-NIGHTLY-marvel' but do not expect more within one month. The same with cm version 10.2. In a thread I read that it was give up because cm11 is already working better.
**** So would you please give me the link to the finished versions of cm10 and cm11, please? ****
(a patch for the video camera problem seems to be existing shortly now...)
to 2b.) My first problem I saw was missing updater in cm9 for version 10 and 11. And the strange Skype problem. And video problem was fixed JUST before!! BT seems to have restrictions as well. So there is good reason to ask this question!?..
to 3.) It seems as if simple updating from Android 4.0 to 4.2 (cm10) and 4.4 (cm11) isn't possible!?... Officially it seems to work. E.g. OTA of Samsung offered update from 4.2.2 to 4.4. Strange!... How/why does it work here?...
Remark: So I suppose it is CyanogenMod which does not support it... It will not work without 'Titanium Backup' here...
to 4.) I suppose you will have the same problem!? Maybe you have opportunity to try out quickly!?... Skype really does not seem to run on WFS cm9+INT2EXT+. Isn't that strange?... (I reinstalled it already. No chance.)
to 5.) I asked this HERE because it belongs to SYSTEM apps (contacts or call manager) that cannot easily be exchanged, as far as I know!... Can they?...
There is one thing I would like to add, after your remarks to my point 2... Maybe I could not find the right sources. But this is because there is no resource pool (about WFS at XDA anywhere. Instead there just appear 'lonely' links in some threads. And instead of telling/explaining the systematics (if there is one) you guys generally just mention the fact (e.g. a link). So this makes it hard for non-insiders. You understand what I mean?...
(so e.g. I will have to ask (in another thread) how I can find the 'FM radio' app (no streaming!) which is missing in CM9 - instead of just looking at the right page where they are collected)
I would be really happy to get to know at least where you guys have found the informations for all what you do when 'cooking' new versions, etc.!...
Cause then I would have read about all that much more!... Instead of blaming me. Sorry, if I do not have that general info that you got already.
Maybe you understand better now!?... Would be fine.
Anyway, thanks a lot for your short repsonses. Have a nice day!
Again only things that are directly related to development are to be placed in development section. And NO if you have a problem with a rom you have to ask it in Q&A. Read the development forum rules in the stickies attached to the top of the section.
And you could also try reading through the stickies in the general section. It will give you some understanding.
Now CM10 and CM11 works, the threads are pretty high in the development section, you can find them if you look. The version of CM11 you used is the right one (the NIGHTLY) and back button does work. Try the later versions. Officially updating to a higher version is different and large corporations can spend time and money to make it work. But it just is not possible (or rather safe) with the variety of unofficial roms. You could try but most probably fail. You can install different apps for call and messaging and they will work. Search for those apps. CM9/10 works fine and have very less amount of problems. Now remember that this is a very old device and the devs are doing it NOT as a profession. So every single thing will never work.
Now as a last your largest problem is you think everything will be written somewhere in front of your eyes. It will not be. You have to use Google before asking a question. And also you just have to calm down and fix your attitude.
aWFSuser said:
First of all this really does not belong in the development section, in Q&A perhaps.
Click to expand...
Click to collapse
That was my fault, I'd moved this out of a thread and mistakenly put it in the Development section. All sorted now.
thanks again for your time to answer!!
I know, I sound as if I would not know which hard work you guys do. But I do, aWF Suser. And I mentioned that already in the beginning.
And I have heard already from your collegues that it would be a good idea if things could be organised some better. The official cm versions e.g have a central resource pool. Or the android-Wiki and CM-Wiki notes are all out-dated (from 2012) !!... Etc.
But PLEASE understand this more as a suggestion than a criticism - from a user that in your eyes only expects and criticises but cannot give. This is not the case!
Thank you!
I know it is an old smartphone I have. And I would have bought a new one already a long time ago. But even Samsung Galaxy Mini is too big in size and some important functions you will only find in the big version. Why is that so? Nobody can explain!... (i would pay the same price for a small phone!!! Handy devices must not be worse and more expensive than big ones!!)
The WFS is just the only really COMPACT smartphone all over. And I am sad that the industry detected a trend to bigger displays. The opposite is the trueth. Nearly all my friends e.g. like to have a compact phone but those always a beginner versions/hardware which cannot be understood at all.
Really sad. It is a big strange hole in products on market, isn't it?...
Unfortunately you did not give me tips how I could find a way to get more familiar with what and how you guys are doing. Is it a secret? I could imagine to do some work here as well. I am very interested in how you are doing your development work!...
Thank you again...
Now it is sure...
Olivier's last CM9 version still has bugs, not only the problem with lgCamera and Skype but also at the akku loading status.
It seems as if it is not correctly refreshing. The loading curve (s. settings) slows down a lot and shows e.g. after 4 hours loading still 43%. But after rebooting it changed to the right value finally: 100%.
So again my question before, as Olivier unfortunately put away the OTA update function (but ment that it is not necessary anymore):
How can this version be fixed?
As far as I know you don't offer patches but only complete ROMs...
Okay first sorry for being rude as posting in the development section was not your fault.
Now the main problem with our device is not that its old but that it has a armv6 cpu which is not supported by later android versions. So development for developers is tougher and bugs will remain. I mentioned the general stickies before there you can find some useful guides.
And have you installed GAPPS in CM9 because some apps depend on it and won't work without it.
And just to be clear, I'm not really a developer but just a user like you.
I never said CM9 doesn't have bugs. It's is clearly stated in its OP that:
modpunk said:
This ROM is not meant for daily use!
Click to expand...
Click to collapse
Hallo Olivier,
never mind. But I just understood it like that. As you gave the reason for the OTA non-support in your ROM.
So if I misunderstood you... what is your reason then?...
In fact it would bring us forward if you could please comment my questions and/or give tips to solve the mentioned problem.
@so please give me a chance to fix the akku status bug. This is really annoying.
Can you confirm that problem? And if so will you fix it?
And if so how can I update it by OTA updater? Or alternatively at least by a patch but not by a new complete ROM !?...
@TO the Skype problem...
First of all: can you confirm my problem?...
To your question: I used your ROM from 20th Aug. (119.518 KB) This one contains already gapps, I suppose. Cause Google Play and the other stuff was already installed!...
@TO lgCamera...
This wonderful camera app worked fine with EQDKP (v.2.3.5) but now it is too slow and hops a lot. Can you confirm that?
And if so do you have any idea why this is a problem?...
@how can I add FM Radio (analog) support?...
Thank you very much for your feedback!
PS: So if the last version of CM9 is not ment for daily use... which CMx version is it then? Is there none?...
Currently your cm9 works fine. Only those three problems so far...
Do you care for my bug messages?... (or where can I post them?)
Hallo aWF Suser,
yes, I know the problem with the arm version. You must not excuse for any bug in CM.
I do not have problems with bugs. I have more problems when they cannot be fixed easily (missing OTA updater) or errors are not heard or cared for so that bugfixes will not be available at all...
By the way the phone Wildfire (without 'S') is supported by Standard CyanogenMod and also has an ArmV6 processor!...
You mean I should read again the forum rules?... What is it that is is still annoying you in my style of writing?...
Olivier's ROM I used (s. previous message) obviously contained GAPPs already. GooglePlay atc. was already installed. So this should not be the reason, should it?...
First of all: can you confirm my Skype problem, aWF Suser?... I expect it to be in each CM9 version!...
Thank you very much for your support!
PS: By the way, I have compatibility problems when flashing ROMs. For nearly each ROM I have to change the recovery. Is there any that can read all 'formats' of zip files?...
Falk2 said:
Hallo aWF Suser,
yes, I know the problem with the arm version. So you must not excuse for any bug in CM.
I do not have problems with bugs. I have more problems when they cannot be fixed easily (missing OTA updater) or bugfixes are not available at all...
By the way the phone Wildfire (without 'S') is normally supported at CyanogenMod and also has an ArmV6 processor!...
You mean I should read again the forum rules?... What is it that is is still annoying you in my style of writing?...
Olivier's ROM I used (s. next message) obviously contained GAPPs already. GooglePlay atc. was already installed.
So this should not be the reason, should it?...
First of all: can you confirm my Skype problem, aWF Suser?... I expect it to be in each CM9 version!...
Thank you very much for your support!
PS: By the way, I have compatibility problems with ROMs. For every second ROM I have to change the Recovery. Is there any that can read all 'formats' of zip files?...
Click to expand...
Click to collapse
The Wildfire is listed officially only for CM7 (gingerbread) . After that it has not been supported. I am not asking you to read the rules, in the stickies in general section there is a thread that lists some guides to some useful things. And is OTA that necessary because in most cases a dirty flash is enough to upgrade from one version to another as long as its the same android version. Upgrades between different android version would not be possible even with OTA (as lots of things change, it will probably end in a bootloop). I am not using CM9 currently so can't speak for that.
So then which CM version are you using on your WFS? And why?
I flashed cm11 shortly but it still has too many problems. E.g. the camera app crashes after successfully recording a video, the launcher only has two pages, launcher does not seem to support folders, etc.
Do you know where I can find the actual todo list? (AndroidWiki unfortunately is not maintained anymore!)
I will give Paranoid 4.45 a try yet. Maybe this is better!?...
Otherwise I will keep cm9 and hope that we can find out why Skype is not running.
Oooh, that is important... I can make a 'dirt flash'? This is very fine!! Then OTA is not that necessary, of course. But there is still no reason to left it away, is it? Especially because all this observing and searching for the update is NOT necessary! Can't understand Olivier here...
Could you comment my PS as well, please?...
(error log: "cannot load volume /misc. Can't partition non-vfat: /sto .. (vfat)")
http://forum.xda-developers.com/htc-wildfire-s/development/cyanogenmod-10-t2908631
is there any better rom than this rom? how can i improve battery life with screen on? i want it for daily driver, i do not use bluetooth ad2p but i dont know what armv7 features means...
for me its affordable atm and give a new life to the oldie and shiny wfs
Which rom is the most stable for everyday use?
(With working wi-fi tethering)
Q&A for [ROM][UB][Linaro][KitKat][4.4.4]Carbon Rom[Unofficial]
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:
Camera app replacement
Hey guys, thanks for the Carbon Rom - looks real good, is nice & fast.
I have one question.
I've installed Google Camera and I liked it better than default CM one. I tried to freeze CM camera so that Google Camera would be default everywhere, but pressing hardware camera button doesn't work (there is only a one-time vibro, camera doesn't launch, when CM is defrost it launches, obviously).
Is there any way I can set Google Camera to launch via hardware button? I'd like to delete CM camera to keep everything neat & tidy.
Thank you guys in advance!
Problem with Carbon rom
Hi, I'm new at this and I had a problem when I installed your rom on my Xperia S. I managed to root it and install CWM perfectly... But when I flashed your rom, without any problems, and tried to reboot, the phone never rebooted. I just stays with the screen off and when I press the power on button for a while it only vibrates and that's it. I used to have the official Xperia 4.1.2 rom. HELP!!!!
If unlocked bootloader, maybe you should flash tft.
You can have a look at the main thread someone has the same problem....
I'm trying to build carbon rom for aoba (Ion), I have ths error :
out/target/product/aoba/obj/SHARED_LIBRARIES/libOmxVenc_intermediates/venc/src/omx_video_base.o] Erreur 1
Anyone knows about you this problem ?
Please help
please help me, my earphones cannot be detected after clean install. but is working with the stock rom,
lexjay said:
please help me, my earphones cannot be detected after clean install. but is working with the stock rom,
Click to expand...
Click to collapse
I think this problem is known.
Which earphones are you using?
I think newer ones are not supported because of missing drivers but i am not sure.
HDMI
Is it hard to make hdmi support? I use 4.1 only for hdmi. There are another 4.4 roms with hdmi, but carbon is best.
Akimov said:
Is it hard to make hdmi support? I use 4.1 only for hdmi. There are another 4.4 roms with hdmi, but carbon is best.
Click to expand...
Click to collapse
Yes it is hard to support hdmi since, afaik, there was no proper support built for it in the sources used by carbon.
build fails on OMX codec
Hi all!
Has anyone tried to build the ROM from sources?.. well I have and it fails while building the obj for OMXCodec --> OMXCodec.cpp:4569 --> frameworks/av/media/libstagefright/OMXCodec.cpp:4569:11: error: 'OMX_AUDIO_PARAM_FLACTYPE' has no member named 'nBitsPerSample'
If anyone met the same problem and fixed it, please share the fix/work-around.
So far i've edited OMX_Audio.h and inserted an OMX_U32 nBitsPerSample var in the OMX_AUDIO_PARAM_FLACTYPE struct.
It compiles on, but i'm not sure this is Ok.
Thanks!
negreamp said:
Hi all!
Has anyone tried to build the ROM from sources?.. well I have and it fails while building the obj for OMXCodec --> OMXCodec.cpp:4569 --> frameworks/av/media/libstagefright/OMXCodec.cpp:4569:11: error: 'OMX_AUDIO_PARAM_FLACTYPE' has no member named 'nBitsPerSample'
If anyone met the same problem and fixed it, please share the fix/work-around.
So far i've edited OMX_Audio.h and inserted an OMX_U32 nBitsPerSample var in the OMX_AUDIO_PARAM_FLACTYPE struct.
It compiles on, but i'm not sure this is Ok.
Thanks!
Click to expand...
Click to collapse
Yeah well I tried to build it too yesterday evening, but I'm not getting any error nor the output zip file! Where did You find the error?
Mmmm... I don't really remember.
I was building the project just like in the 'how to' (I mean literally, step-by-step), and it just crashed at that point.
However, it turns out that there is another external module that is not supported and should not even be in the sources. Let me know if you encounter the same problems.
I have been using this rom for about a month now, good so fare.
But since a couple of days I'm starting to have some bugs (like the music lagging and even stopping when I'm doing other things on my phone) and some lags from time to time. Sometimes it's really smooth, but most of the time it's very slow and not confortable to use.
Any ideas how I could speed it up and make it smoother ? I already overcloked it
help the stock launcher keeps reseting after reboot
VoIP issue
hi all,
i am ussing carbon rom 4.4.4 on my xperia s lt26i, every thing is good but viber does not work!!!!
Changelog of today built?
thx
thx for the new build
is viber work on this last build!!!!!
Sync contact
Hi, how can i sync my contact from google accounts?
And is able to use Google Play on this rom?
Thanks!
Carbon 0808
Hello,
can anyone please upload Carbon version 0808. On link is not any more for download.
Thanks in advance.
@Darth Inferno can you please upload previous kernel from previous build
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?
Q&A for [ROM][OFFICIAL CM12][5.0.2] Official Cyanogenmod 12 Nightlies
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][OFFICIAL CM12][5.0.2] Official Cyanogenmod 12 Nightlies. 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!
Cm9aphla said:
That is yet to be tested but I will get back to you on that.
Click to expand...
Click to collapse
MultiRom error :E:Error executing updater binary in zip
Is anyone else having issues with GPS?
Misc. battery drain
Is anyone else having this issue? Misc. now consumes 77% of my battery. I thought google fixed this back in November?
**
Hello! nightly 0113-0114 cause google play service error, I cant acess my google play neither my play services stop. Do You know any solution for that? Thanks! BTW updated via cyandelta.
Sent from my Nexus 7 using XDA Free mobile app
also I cannot find the Google account remover only cancel sync....
Sent from my Nexus 7 using XDA Free mobile app
Baseband Version Unknown
Hello all, i flashed the CM o114 nightly and so far it's all good, except for the baseband, it says:
Baseband Version Unknown
on my Nexus 7 2013 4G
Is anybody else facing this issue?
I looked everywere and found no info before posting here.
You may have to see this thread.
[ROM][Unofficial CM12][5.0.2]CM12 Preview Builds for Deb - 1/06
And this thread.
[Q&A] [ROM][Unofficial CM12][5.0.1]CM12 Preview Builds for Deb - 12/18
jffonseca10 said:
Hello all, i flashed the CM o114 nightly and so far it's all good, except for the baseband, it says:
Baseband Version Unknown
on my Nexus 7 2013 4G
Is anybody else facing this issue?
I looked everywere and found no info before posting here.
Click to expand...
Click to collapse
copenkagan said:
Is anyone else having issues with GPS?
Click to expand...
Click to collapse
Can anyone confirm that their GPS works at all? I can't get my GPS to work. It gets no satellites in GPS Test app on the Play Store. It can only acquire location by wifi scan, not GPS satellites. I have the Nexus 7 2013 32GB (flo) running CM12 without root or mods.
GPS not working
What with navbar settings? They ve disappeared
Having issues with Bluetooth and GPS here. Bluetooth is working but with lots of skipping. its not my player or my music stream. Same song plays fine with headphone and N7 speakers. And I also have totally lost my GPS, didn’t even notice until I checked with GPS Checker.
For having a working GPS you need to install another kernel until cm has fixed it.
I installed this one and gps work's just fine.
http://forum.xda-developers.com/showthread.php?t=2809979
Any word on fixing the email app crash from Combined view?
Won't Boot with SuperSu by Chainfire
Hi all, I have issues booting after updating from nightly to nightly. Here's the situation:
After updating from any CM12 nightly to a newer CM12 nightly, my tablet gets stuck on the boot splash screen (the one where it says Google and has the lock icon at the bottom) and I can't boot at all. I have tracked the issue to SuperSu by ChainFire. My SuperSu settings are attached below. Is this just me or is it everyone else too? If it is just me is there any way to fix it permanently rather than wiping /system and needing to re-flash everything all over again?
If you lost mobile data or gps sensors, please try this zip.
mod_bootcmd_selinux_permissive.zip
is simple zip to add "androidboot.selinux=permissive" to kernel boot command line.
mod_bootcmd_selinux_noneperm.zip
is revert permissive zip.
Thanks.
Cyanogenmod = Awesome !
I was disappointed with 1.23 nightly though 1.24 fixed it up, hoping that some apps that come with Cyanogen like the music player get a landscape setup; irritating that it rotates back to portrait. Nexus 7's a tablet! ,content is best in landscape hoping you guys could work on it
1.30 Interface issue
On last nightly (1.30) i found a bug in interface in horizantal view. Buttons (menu, back option) are not drawn correctly .
wolfanger said:
On last nightly (1.30) i found a bug in interface in horizantal view. Buttons (menu, back option) are not drawn correctly .
Click to expand...
Click to collapse
This is fix commit. Merged today.
http://review.cyanogenmod.org/#/c/87367/
It will fix next nightly.