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)
Related
Hello guys,
I'm new to this forum but I read it from time to time since a few months.
I own an Iconia Tab A101 that I already rooted and so far I haven't received the OTA update toward ICS probably beacuse I used a Stock Rom from Vache which is not a full stock rom.
I already found few ICS ROMs but as I use this tablet for my job, I don't want to mess up with it. So far it dosen't say it would work with an Iconia A101, but only a A100. Did anyone already tried it on the A101 ? (I can't aford to lose my 3G conection/driver as I use it everyday to send my jobs forms)
Is there any way I could upgrade toward ICS without losing my applications and datas ? (I can handle the root and adhoc/wpasuplicant issue later..)
I wish I could install/use Nandroid to get a full backup of my tablet before just in case.... Would you advise me to use that application ? How do I do that ?
I alreadytried to install CWM but failed to it. I probably did something wrong or in the wrong order.
Anyway thanks for your help ! I love this forum.
Best regards
Fabien
Try looking harder. There's a leak of the official A101 ICS ROM in the development section.
The official A101 ICS ROM in the development section
FloatingFatMan said:
Try looking harder. There's a leak of the official A101 ICS ROM in the development section.
Click to expand...
Click to collapse
Would you be so kind and point me/us to the leak of the official A101 ICS ROM in the development section?
I wasn't able to find it...
Thank you,
Adrian
Try this link http://narod.ru/disk/47785011001.df...cer_AV041_A101_0.004.00_WW_GEN1-root.zip.html (CWM version)
Infomediasvc said:
I already found few ICS ROMs but as I use this tablet for my job, I don't want to mess up with it. So far it dosen't say it would work with an Iconia A101, but only a A100. Did anyone already tried it on the A101 ? (I can't aford to lose my 3G conection/driver as I use it everyday to send my jobs forms)
Is there any way I could upgrade toward ICS without losing my applications and datas ? (I can handle the root and adhoc/wpasuplicant issue later..)
Click to expand...
Click to collapse
Acer didn't release ICS for A101 yet, so it's normal that you didn't receive OTA upgrade.
There is a leak of an old ICS build for A101 here: http://forum.xda-developers.com/showpost.php?p=25561591&postcount=6
I'm running it and it works fine. I just needed to delete and recreate APN, as the migrated one was disabled for some reason.
(P.S. You need to install all four update.zip from the archive in order. These are incremental and you cannot skip any.)
Thank you leomatt & smokku for you quick and clear answers. That's the spirit!
Thanks again,
Adrian
Thank you so much ! It worked like a charm.
Next step will be root (again), and adhoc support.
This may help:
1.Load Update1.zip onta a SD card. Rename it Update.zip. THIS IS IMPORTANT!
2. Press POWER and VOL- (the top vol button) and flash the ROM. The reboot will hang. Just power off and continue.
3. Repeat for the remaining updates, one at a time.
4. The final reboot will work and the ROM will be flashed. If error messages are encountered or constant rebooting is experienced, do a factory restart.
This worked for me and restored my Acer back to A101. (I had loaded ICS for A100 and lost 3g...I can't help fiddling with things I don't understand........
GrigAdri said:
Thank you leomatt & smokku for you quick and clear answers. That's the spirit!
Thanks again,
Adrian
Click to expand...
Click to collapse
Hey. No need to thank me for telling you it even existed in the first place, that's perfectly OK.
For someone so utterly incapable of finding something so simple (seriously, third hit on a search), I suggest you don't even THINK about flashing it; you'll brick your tab.
Someday you'll get, that this forum is about people helping each other, not feeling superior to others.
FloatingFatMan said:
Hey. No need to thank me for telling you it even existed in the first place, that's perfectly OK.
For someone so utterly incapable of finding something so simple (seriously, third hit on a search), I suggest you don't even THINK about flashing it; you'll brick your tab.
Click to expand...
Click to collapse
Insulting people is a bad habit. Some day you will find out why!
Details ?
FloatingFatMan said:
Hey. No need to thank me for telling you it even existed in the first place, that's perfectly OK.
For someone so utterly incapable of finding something so simple (seriously, third hit on a search), I suggest you don't even THINK about flashing it; you'll brick your tab.
Click to expand...
Click to collapse
This link : http://forum.xda-developers.com/showpost.php?p=25561591&postcount=6
i about an OFFICIAL rom, not a stock rom modified, or a leaked one, etc..
It would be great if you guys could CLEARLY say what is made for ?
If it's for A100, its for A100, A101 for A101, etc... as well as for which kind of rom it is made for, etc ?
For someone who is used to it, it's easy ! However, even for a newbie there is nothing about Android terminology ! The poor guy is lost and nothing makes sense to him/her.
For example : ROM means Read Only Memory (as oposed to Ram which is Random Access Memory (volatile memory) ) right !!!
Well if the ROM is the operating system, then you don't only read it as you also write in it and can replace its content as well ! However, Android (the os) is a ROM !! Even for someone coming from the IT world, it's kind of confusing ! ;-)
By the way, it says not to install Busybox, but I had to, after to fix some apps.
The wpa_suplicant file however doesn't fix the adhoc issue so far.
I'll get back to the old file in the meantime.
Infomediasvc said:
i about an OFFICIAL rom, not a stock rom modified, or a leaked one, etc..
Click to expand...
Click to collapse
There isn't one.
Are you happy now?
smokku said:
There isn't one.
Are you happy now?
Click to expand...
Click to collapse
Quite happy !
Didn't I read oficial in "Path for the official A101 updating to ICS" ?
GrigAdri said:
Insulting people is a bad habit. Some day you will find out why!
Click to expand...
Click to collapse
I didn't insult anyone, but I can, if you like.
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!
This isn't another one of those 'can somebody port Sense' threads.
Please note that this thread is for developer-oriented discussion. If you don't have anything to say to help development, please refrain from posting here.
Also note that ideas are welcome. Just check if the idea you're about to post has already been posted by somebody else.
Right now, it's just multiple people working on this. No team, just individuals.
As of the last edit of this post, there has been little to no progress:
I'm constantly working on builds. The current, and the only goal I'll be striving towards as of now is using a T-Mo HTC One X ROM in combination with RaymanFX's CM10.1 RC2 build.
XDA RC @abcdjdj has reported that he has fixed a lot of errors in his build, and is now stuck at the bootanimation. If you can help him in any way, here is what's wrong with his build. He's using FXP's CM9 as a base and a 4.0 HTC One X with Sense 4 ROM as a port.
The OP will constantly be updated with any progress anyone makes.
We're currently using this XDA thread to help us port the ROM.
--------------------------------
Here's everything I have to share on my build:
PORT: HTC One X, T-Mobile Edition| Android 4.2.2
BASE: Sony Xperia S, nozomi | Android 4.2.2
------------------------
ITesters needed. If you can work through adb commands and can provide me with logcats, please leave a post about it in the thread.
And finally, a note to anyone that may be cursing me for working so very slow (because I admit, this is very slow):
Please understand that all this isn't easy for me. I have painfully slow internet, making each download at least one hour, and thus a pain. My time on this project is limited every day, so progress is slow.
Reserved.
someone755 said:
Okay, so this is the work that has already been done and some of the mysteries that puzzle me right now:
I've edited the CM9 kernel's ramdisk, like stated in the tutorial I'm using (see post 1). As of now, the kernel itself is broken and even if the ROM was complete, not even the booting would work. (Well, booting works as far as showing the boot logo (the green FXP one) goes. But the LED notification light for entering recovery doesn't light. Bootloop over and over...)
Many of the lib files intended to be copied from one lib folder to the other are missing on our Nozomis... My question is, what are the consequences...?
My main issue here is that the zip won't flash. The recovery (no matter which I choose) just returns an 'ERROR' and refuses to flash the file...
Another question would be how to repack an .elf kernel into a boot.img. Because now, I'm trying with letting the CM9 kernel in the zip (since it is an .img) and then flash the modified .elf kernel that I repacked with Flashtool. Inefficient, but at least there's a way.
So currently, the priority list would be:
1.Get zip to flash
2.Fix kernel
...Not necessarily in that order. We could fix the kernel first, but there isn't much gain to it if the ROM zip can't even be flashed to test if it truly works...
Click to expand...
Click to collapse
Bro, it may be possible to get Sense on our devices. Even I have been working on getting Sense booted on our device. My status:-
PORTED FROM - HTC ONE X
BASE - FXP 215 CM9
STATUS - Gets past kernel and even loads bootanimation. Fixed many errors in the logcat. Gets stuck at bootanimation and even displays a message saying that System is not responding, would you like to close it.
I couldn't manage to fix any more errors in the logcat so I gave up but you have rekindled my spirit to get Sense booting on out device. I will upload my rom soon along with the logcat.
Cheers,
abcdjdj
Wow, you actually got the thing to boot?
The only question is how did you manage that based off of a tegra CPU? Would be very interested in seeing that...
On a not-so-very related note, your port was of ICS and Sense 4 , correct?
Am I the only one around here that favors old software?
someone755 said:
Wow, you actually got the thing to boot?
The only question is how did you manage that based off of a tegra CPU? Would be very interested in seeing that...
On a not-so-very related note, your port was of ICS and Sense 4 , correct?
Am I the only one around here that favors old software?
Click to expand...
Click to collapse
Not fully booting but I think close to booting. I followed the guide mentioned by you in the OP and one by one eliminated all errors that I could eliminate. I had been working on Sense for around a month during my school holidays but now I am not getting any free time. And yes it is Sense 4 (Android 4.0.4).
Sent from my LT26i using xda app-developers app
But isn't the Tegra3 completely different than our FUJI board?
Especially the graphics, those must be out of control on your ROM...
If I were you, I'd at least take the AT&T version of the HOX.
Oh yeah, I forgot to ask: is it the same if I try and port from a MSM8260 board (the same as the Xperia) and the later S4 Qualcomm versions (used in the Xperia T, AT&T One X etc.)? Because porting from a CDMA phone (HTC Rezound) seems to make the work harder...
Thankfully, my summer holidays have just begun, so I have plenty of free time (that's also the reason I started my project).
P.S.
Yeah, maybe that's exactly what I should do. Ditch the CDMA phone and start with the Snapdragon S4 One X!
I would prefer Sense 3.x, but oh well, at least Sense4 is also Sense
http://www.xda-developers.com/android/sense-4-ported-to-sony-xperia-devices/
I just found this. It's not even that old...
Anyways, I've been thinking if the devs of this would be able to help us.
This development stuff gets boring pretty quick when you do it for the 10th time
@samuel2706, could you give these guys a little hand?
But he's a HTC Dev... Wouldn't we need something more like a nexus or better yet a Xperia developer?
someone755 said:
But he's a HTC Dev... Wouldn't we need something more like a nexus or better yet a Xperia developer?
Click to expand...
Click to collapse
Yes,, maybe, but he also could give a little help. Can't he?
Sent From my LT26i using Tapatalk 4
Contact the guy who did this http://forum.xda-developers.com/showthread.php?t=2184706
Well, I thought I'd make this thread so that devs could help each other to actually work together and create a working Sense ROM. So naturally, all help is welcome from anyone.
Anyways, I'm on my way to finishing yet another try, this time with the AT&T One X. Fingers crossed that it at least makes it to the bootanimation.
EDIT: I see that the easiest way to get Gapps is with including the default /data folder from the original HTC ROM (with vending, youtube etc.). But I have to add that to the updater-script. So, I want to ask, is /dev/block/mmcblk0p14 the data partition on the Nozomi?
What's happening?
samuel2706 said:
What's happening?
Click to expand...
Click to collapse
Hi,
I am porting [or trying to port] Sense 4 from HTC One X to Xperia S. I used FXP 214 CM9 as a base. I followed this guide - http://forum.xda-developers.com/showthread.php?t=2245786
Then I fixed as many errors as I could by checking the logcat and got it till the Bootanimation. But now I need help to get it to boot. So, I have attached the logcat from my latest build.
Thanks for your help,
abcdjdj
Maybe copying a few more files could help. Maybe act like your xperia is a HTC device? http://forum.xda-developers.com/showthread.php?t=1222746
Could be worth a try and play with this copying a bit...
Seems to be failing at dalvik; very strange, it doesn't show any major errors on first glance however I'll take a longer look at when I can, however I can link you to this thread that may help you in the meantime Porting
What about this one? http://forum.xda-developers.com/showthread.php?t=2276871
Nice and automated, but the question is, will it work?
I'm trying it with the HOX, just need to wait for it to copy to the phone...
All this seems like a big race -- who will get it working first? Hyped!
Kinda makes me wish I still had my xperia S I could have given this a real good go at; but instead I have a galaxy s4, so it's going to be mostly logcats and such I can help with, I don't like blind building things; made that mistake before.
A blind build is better than no build. Unless it makes bricks...
Thanks a lot for helping out.
Though I'll never understand how a pro HTC dev can go to Sony and then Samsung. ;P
I just hope THIS time my kernel will boot... Cause if it doesn't ... [censored]...
EDIT: Okay, [censored] is happening... Why can't I make this zip flash? I've done it a million times, but all I get is ERROR... ;-;
unfotunatly, i'm not a dev. but i really like the idea. specially if considering porting htc one sense version to our nozomi. i think it would fit like a glove
Can KitKat be ported onto our Arc S phones ????
Sent from my LT18a using xda app-developers app
Perhaps...
http://forum.xda-developers.com/showthread.php?t=2431179
17th_angel said:
Perhaps...
http://forum.xda-developers.com/showthread.php?t=2431179
Click to expand...
Click to collapse
That was just a discussion thread... and now some people think that just because it can run on 512MB RAM they can install it on their phones straight away... If kitkat ever comes to the Arc/S it will take a while for it to become stable enough for daily use. Also, the drivers we use are old since there have been no updates. If you guys want kitkat running successfully on this device, these old drivers need to be integrated with the new software, which is very tedious. Mike is already going to drown under 4.2 and 4.3, adding another OS to the pile will place him under more stress.
Don't assume the work we developers do is simple, just because an update came out that meets the system specifications means it can run just by downloading and installing it in recovery. If you ever tried to create a ROM by yourself, you'll find out that a lot of work needs to be done, along with many user complains and flooding your development thread with useless posts. That's how messed up the user community is nowadays. Jader's UHD ROM thread is one example of how users interact with the developer.
僕のLT18iから送られてきた
Im sorry, but which part of perhaps its a "definitely yes"?
I just point to that thread so he and anybody with the same question can see that it really going to depends on how google code it and how hard could be for the developers to bring that code to our devices...
I never declared that it will be a fact, but you have to admit that the 512 MB its a nice hope.
17th_angel said:
Im sorry, but which part of perhaps its a "definitely yes"?
I just point to that thread so he and anybody with the same question can see that it really going to depends on how google code it and how hard could be for the developers to bring that code to our devices...
I never declared that it will be a fact, but you have to admit that the 512 MB its a nice hope.
Click to expand...
Click to collapse
That reply was for that thread itself since some prick was like "hey Kitkat runs on 512MB devices"... I wasn't even referring to you in the first place.
Yes, it is hopeful but not promising, see Mike's reply at the thread itself
僕のLT18iから送られてきた
Yes, it's possible to port Android 4.4 for our device but it all really depends on if there will be any developer / developers who want to spend their time porting 4.4 for our device. Mike have started working on it for our devices, but we will see when or if he releases it or not.
I might see if I'm able to sync the sources, but the main problem on my end is that my PC is really bad and not suited for development.
Sent from my LT15i using Tapatalk
Yes, Harsh is developing the same, follow the link
http://forum.xda-developers.com/showthread.php?t=2134257&page=184
The fact that it can run, does not mean that it will run.
Either way, I am sure the devs will be porting it over in no time.
Sent from my Nexus 5 using xda app-developers app
Developers are trying hard, hope to see KK on Arc S soon
Fyi harsh isn't developing kitkat.. It's just a kitkat ui for his rom update...
Sent from my Xperia Neo V using Tapatalk 2
yes it is try to search if you wanna stable blasting fast rom with kitkat teme then flash super jelly bean by harsh with kitkat ui
---------- Post added at 08:02 PM ---------- Previous post was at 07:56 PM ----------
but kitkat based in my option is bet AORP kitkat rom try it
Just as a suggestion, I'm currently using VanirAOSP and it's pretty good. All I've to say is that right now one should get the vanir_anzu_4.4.2.012814 version, as the latest, vanir_anzu_4.4.2.022314, has a few additional bugs. On the mentioned good version WiFi works, everything is fairly smooth and you're left with enough space to actually install the apps you want, which seems to be an issue on many roms due to Arc's small internal memory.. Only real problem's the default browser lagging terribly, but I hear that's a general issue? Anyway, for anyone interested in kitkat on Arc it's definitely worth checking out.
Here's the thread: http://forum.xda-developers.com/showthread.php?t=2627083
If you want a good KK experiance I recomend carbon Rom just serach or let me doin' it for you her you are sir http://forum.xda-developers.com/showthread.php?t=2575425
AORP is stable for me.... you might wanna check
I m using AORP[anzu] from 2 weeks and it works awesome.
Scayris said:
Just as a suggestion, I'm currently using VanirAOSP and it's pretty good. All I've to say is that right now one should get the vanir_anzu_4.4.2.012814 version, as the latest, vanir_anzu_4.4.2.022314, has a few additional bugs. On the mentioned good version WiFi works, everything is fairly smooth and you're left with enough space to actually install the apps you want, which seems to be an issue on many roms due to Arc's small internal memory.. Only real problem's the default browser lagging terribly, but I hear that's a general issue? Anyway, for anyone interested in kitkat on Arc it's definitely worth checking out.
Here's the thread: http://forum.xda-developers.com/showthread.php?t=2627083
Click to expand...
Click to collapse
I will try VanirAOSP (out of curiosity), thanks for suggesting.
DuckyMomo said:
If you want a good KK experiance I recomend carbon Rom just serach or let me doin' it for you her you are sir http://forum.xda-developers.com/showthread.php?t=2575425
Click to expand...
Click to collapse
Tried it. Really cool ROM, some minor bugs but its OK
KitKat 4.4.2 AOKP and ART-runtime enabled
It is very well possible to use KitKat 4.4.2 on our phones. Even with ART-runtime enabled. I personally use AOKP (Android Open Kang Project)'s KitKat version, and I managed to get ART-runtime enabled and running very fast and smooth.
You can find the ROM here: http://forum.xda-developers.com/showthread.php?t=2624761
Of course you have to first install the kernel, which is given in the zip-file. Just unzip the kernel and Flashboot it to your device. Then go into CWM-recovery and go to Mounts and Storage and activate USB-mount. Locate the full AOKP-zip and place it on your SD-Card, as wel as the minimal Gapps for 4.4.2., found here : http://forum.xda-developers.com/showthread.php?t=2012857. Unmount the USB, and install the zip as usual through the menu for it. Then, after installing AOKP, install the minimal Gapps.
Reboot and let your device sit for a while, or play around with it a bit....
I proceeded with installing Mounts2SD from playstore, while before having prepared my class10 8 Gb sdcard into two partitions. One partition FAT32, size about 6Gb and one partition EXT2 size around 2 Gb. Move everything to SD-card through the menu of Mounts2sd, except Dalvik-cache. NEVER MOVE THIS!!! (Don't move dalvik-cache to SD...)
Reboot at least two times to let the script (Mounts2sd) settle in... After this I installed Pimp-my-Rom from playstore and activated the nav-bar and some other scripts to improve the experience. Also I odexed (after finishing all my modifications) the phone through this : http://forum.xda-developers.com/showthread.php?t=2527732
I then went to CWM-recovery through a reboot and made a full backup, which I advice you to do also, in case something goes horribly wrong.
Reboot to AOKP. As you can see, this ROM is awesome-fast beyond belief already. I had benchmarks in AnTuTu of around 6000, with NoFrills-CPU at 1401 Mhz. But, it can be faster if you choose to run ART-runtime instead of Dalvik. Be sure to remove all unwanted programs before switching to ART-runtime, because it'll take a lot of space in cache, and every program you don't need (system-programs that is) will reserve more space for ART.
Only and ONLY if your system is running smoothly on Dalvik, I advise you to go to your Phone-settings, (under Settings of course) and tap on 'Build-number' like 10 times. You will now become a developer. An extra menu will appear under Settings, where you can choose to run the ART-runtime library. Choose this and you will reboot.
Wait, wait and wait a long time for reboot. After initial booting everything has to be updated to ART-compiled apps. This will take a long time per app. Just wait and don't disturb your phone. If you get to the phone after booting, then you probably succeeded... You can check under the same settings-tab under Developer-options. If ART is selected, then you have it.
I strongly advice in case of mishaps regarding loss of network etc. to just reboot. Wait, wait and eventually you'll get there. Make a backup as soon as you have a stable working system under CWM-recovery.
I have been running stable ART under this AOKP-rom for about two weeks now and I'm really happy with it. Not only is the phone lightning-fast (6417 under AnTuTu, with CPU on my Arc LT15i on 1401 Mhz), but smooth as hell! Batterytime is amazing. This is as fast as it's gonna get! (I must have tried almost every ROM out there from stock 4.0.1 to 4.4.2...)
Hope you'll try and may it work for you too...!
(BTW my ultimate thanks to the guys from Open Kang Project!)
P.S. stock-browser is lagging... as usual under 4.4, but I use Dolphin and it is fast! Some toggles require reboot to function again. Some programs might fail you due to not being ready for ART. Facebook is a mess for instance, sometimes quitting unresponsice etc. Otherwise I have encountered no problems whatsoever.
Tried ION kernel and stuff and I can say that apart of one or two really minor bug the KK experience is just awesome and will be better within some months i suggest you to follow all the "Xperia Overlay" thing a I hope it gonna be amazing:laugh:
Hello,
I detected the following systematic problems of cm9..11
1.) Skype cannot be started at all. It does not even react on a click of its icon. And no error message appears.
2.) the akku load status is shown incorrect during load process. E.g. after 4 hours load it shows 37% instead of true 100% (which is shown after reboot).
3.) The wonderful app 'lgCamera' runs very slow and jerky. This was fine in Android 2.x versions.
4.) the FM radio app for the WFS radio tuner (no internet radio!). How can I find it (and flash it into the system folder as a system app)?
I suppose that everybody can confirm my problems!?...
Are those already known by the development team? Cause I wonder that they are not fixed in ALL CyanogenMod versions yet!
Will there be a chance to expect their fix soon?...
5.) Furtheron I have big compatibility problems when flashing cm9..cm11 ROMs and others. Error message: "cannot load volume /misc. Can't partition non-vfat: /storage (vfat)". For nearly each ROM I have to change the recovery. Currently I change between the following recoverys (one of them allways works):
twrp-2.2.2.0, twrp-2.7.1.0, Phil-Z 6.43.7, cwm-5.0.2.8, cwm-6.0.5.3. Nobody else having that problem?...
Is there any recovery version that can read all 'formats' of zip files?...
Will there be compatibiliy at least at the backup files between all of them?...
Thank you VERY much for a quick help!
1.) not compatible anymore, say Thanks to Skype
2.) This is probably problem with battery not reading voltage correct anymore on charger (happens) for me on all roms even stock. (After 100000 of flashes and almost 3years old down sucked battery
3) ics and up isn't made for this phone, slow downs and other incompatibility can happen.
4) There is a solution called spiritfm(free) Google it, you will find the xda thread.
5) twrp 2.2.2.0 and cwm 5 is working on all ROMs beside newer kk builds (needs recovery compiled with TLS support, newest ones available)
Greetings Kevin
Hallo Kevin,
I am so glad that you answer! Thank you very much!!
to 1.) Yes, I realised meanwhile that Skype 4 ist still running fine. So the reason why the new Skype 5 version does not work on Wildfire S (or even on all CM versions of all devices??) you don't know!?...
to 2.) So this is a general Andrid 4.x problem of Wildfire S device only?... (cause e.g. on Galaxy S4 stock (of my girl-friend) it works fine!...
to 4.) Thank you. I installed this free version '0918fr.apk' but I get the error message (su rights confirmed): "Error: No FM accessible. SU: 0 Fm:BC2 SU:0 Bt:3 Ht:0 Mo:BCU". It does not seem to be compatible although I have read everywhere that it should work. Is this maybe antoo old version? Or what can be the reason?...
to 5.) So I used newer version 'cwm-6.0.5.3' and 'twrp-2.7.1.0', as I mentioned, but then these versions do not support older version than KK. E.g. 'CronMod-INT2EXT+_signed.zip'. This is the problem. Any solution?...
Is TLS ment as 'Thread-local storage'?...
Another short request:
a) Video recording with cm11 on Wildfire S works now without any patch. But if I record a video longer than about 5 seconds and I want to watch it directly after having stopped recording (timeframe about 7 seconds) then the camera app crashes. Can you confirm that on Wildfire S? What can be the reason?...
If Olivier's camera patch will help here as well I have not tested yet...
b) Management of Launcher and App screen is somehow circumstancial or not even possible. This is why the option 'Homescreen' is missing in 'Personalization' ('cm-11-20140816-Nightly') although the related screenshots of cm11 in XDA show this option!! E.g. App icons cannot be sorted alphabetically or cannot be manually moved within the screen. Or the home panel is the most left one instead of the middle one. Etc.
Any reason why the option 'Homescreen' was deleted (in XDA cm11 screenshots for Wildfire S still show it!! S. http://forum.xda-developers.com/showthread.php?t=2735775 )?...
c) CM11 OTA update suggests me 'cm-11.0.0-RC9' as the first in the list. Is this really more actual than the installed 'cm-11-20140816-Nightly' (version 11.0-20140816) ?...
d) In this version the Email system app is missing. Why?
Any zip to flash it anywhere? Or do I have to use one of the market?...
e) No warm reboot option available anymore in cm versions?...
Thanks for your help again, Kevin!
Many greetings, Falk
to 5.) I could solve that problem meanwhile by myself. I downloaded a modified version of cwm 6.0.5.3 here:
http://click.xda-developers.com/api...5.0] - Post #52 - XDA Forum&txt=the new build
But I still do not know what was modified! You?...
6.) you forgot the ever present mobile data bug at least for cm9 and cm10. Which no1 evens bothers to mention
Beeefalo said:
6.) you forgot the ever present mobile data bug at least for cm9 and cm10. Which no1 evens bothers to mention
Click to expand...
Click to collapse
Because it does not exist? I never faced any bug like that.
aWFSuser said:
Because it does not exist? I never faced any bug like that.
Click to expand...
Click to collapse
oh, its super present .
It was a "common" problem in cm9, cm10 based roms, at least judging from the various threads dating back to 2013. And as I discovered yesterday its also present in CM11 RC9 for me.
Occurence of the bug is very random and seems to be bound to certain providers which makes it hard to debug/fix i guess.
Sadly, from what I've read "deal with it and toggle airplane mode when you need mobile data" or "install cm7" are the ways to handle this bug.
cheers
Beefalo