Related
I realize that it is early to create threads like this, but I wanted to know if it was just an error in my phone or in general.
I installed Android 4.4 compiled by Grarak but I can not read the sms, quend I get one if I try to read the app crashes
I only found this little guide now! In my case it worked!
http://forum.xda-developers.com/showpost.php?p=47042307&postcount=243&nocache=1&z=3127877558581531
Now it remains to be solved wifi and small graphical issues.
Just a Alpha project
maybe basic on nexus 5 some file
just waiting
I'm actually surprised how stable it is at the moment.
Since I have too few posts to join the "[DISCONTINUED] Team Venom presents: ViperDHD 2.3.0 | Sense 4.1 | 4.0.4 | Smooth | OTA" thread I have to post here...
Everyone who uses this ROM knows there's been an OTA update message popping up due to supposedly not legit ROM. Caveat is I know I have legit but I am sure much of my updates & tweaks would break whatever is used to validate. Since it is EOL anyway I had chosen to disable the OTA but it didn't seem to stay off.
Fast forward 2 months & I find my phone dead at a blank screen. Reboot, same. Clear cache & Dalvik, reboot, same. Factory reset, same. So I use Ext4 to make a backup & then restore last months image, working again. Interesting is that the name of image made of the faulty ROM contains "unknown" rather than ViperDHD.
So question is: Is whatever OTA update being offered by TeamViper's server FORCING itself onto DHD's now despite not being correct? I mean from what I read we're not supposed to accept the update because it bricks devices yet we're still being alerted over & over to accept the OTA update.
I find it a bit nervy to have a ROM ***** about not be "legal" (I assume point is anti-kang?) over & over when I know I got my image from the official thread AND then if it did force an update that crashed my phone that would be over the line. Concern here is that I will face the same issue again since it's happened once.
bump
Do I need to post a better description? Figured I'd not be the only one hit by this.
Perhaps most people have moved on from 4.0-based ROMS.
Perhaps but there is activity on the ViperDHD thread, I just lack enough posting rank to post there and figured this port would kill 2 birds one stone so to speak.
Not looking for active development and it was fine the way it was until these bum OTA's started up recently.
tlund said:
Perhaps most people have moved on from 4.0-based ROMS.
Click to expand...
Click to collapse
OK, so no takers & no helpful input? Seem this ROM has more than a few serious issues despite having some great features & what would appear to be a serious developer base for the various "Team Venom" ROMs.
Would be nice if they would make one last update to DISABLE their broken OTA check, flawed anti-kang detection, and some the of "tweaks" that simply don't work like umm... the all CPU tweaks or the backlight that lists crazy values? Funny, click donate in Venom Tweaks, crash the app consistently!
Seems a bit drastic that I now need to dig the file system to try and rip out the hooks that enable the above problem "features".
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] [NIGHTLY] [4.4.4] CyanogenMod 11 for Samsung Galaxy Nexus
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:
CM11-M11 stable?
Hello,
I have a short question regarding the stability of the newest snapshot M11 of CM11. Are there any bugs which may prevent using it in a productive environment? I'm giving the device away and it probably won't be updated afterwards. M11 would replace the currently installed M7, I stopped updating regularly after having endured an unstable device for two months prior to M7 (and I do not wish to give it away having a nightly installed).
Since a long time ago the native sip client has been fixed. There are other kitkat ROMs out there for other devices which still have an audio bug rendering the sip client useless. Could someone link me to this ROM's fix so other developers could apply it to their ROMs?
I've been trying to search for it myself but I can't find it. Thanks a lot! [emoji4]
Silpion said:
Hello,
I have a short question regarding the stability of the newest snapshot M11 of CM11. Are there any bugs which may prevent using it in a productive environment? I'm giving the device away and it probably won't be updated afterwards. M11 would replace the currently installed M7, I stopped updating regularly after having endured an unstable device for two months prior to M7 (and I do not wish to give it away having a nightly installed).
Click to expand...
Click to collapse
The latest M release should be pretty stable.
Hello @Ziyan
Many thanks for your amazing work.
I just want to know that when we can expect CM 12 for Galaxy Nexus ?
Any news about M12 release? Still not seeing it on the building queue page...thanks Ziyan for your effort!
ImTheDroid said:
Hello @Ziyan
Many thanks for you amazing work.
I just want to know that when we can expect CM 12 for Galaxy Nexus ?
Click to expand...
Click to collapse
By the time they start pushing nightlies (in December), maguro should be fully functional (meaning it will be built too), or I may release test builds earlier
Codename89 said:
Any news about M12 release? Still not seeing it on the building queue page...thanks Ziyan for your effort!
Click to expand...
Click to collapse
They said they'll build it on the weekend.
When Galaxy Nexus Maguro CM M12 build?
Hello Ziyan,
[Edit]: Sorry, I saw the previous post after I posted this question.
I still don't see the M12 for Galaxy Nexus Maguro. Although I see in another thread you mentioned that it will happen once you ask the CM team to build it, but nothing seems to have happened. Just wanted to have this last one of CM11 as it might be better to keep for a long time (in the light of the fact CM12 is coming but might take some time to stabilize). So, any idea, when is the build going to take place?
Thanks...
(I would like to post in the mail thread, but my post count seems to be a problem, anyway..)
After the update to cm11 m12 my phone works really smooth.
As other I noticed that generally the rom degrades its performance after some days probably because of the memory trimm.
I also evidenced performance issues in cm 11 m11 due to Google now voice detection of "Ok google" so I disabled it.
I registered in xda to thank you.
In the CM12 roadmap [1] there's:
1) Watering down of SELINUX protections or Encryption by default. These are base protections L is introducing and we should support these items as such. If your device fails to allow encrypting, it will not get a CM sanctioned release.
Click to expand...
Click to collapse
Currently CM11 kernel has SELINUX set to permissive to fix some bugs (in the dialer iirc), but enforcing should be possible. Just have to add some rules:
https://source.android.com/devices/tech/security/selinux/validate.html
Getting encryption to work without watering it down sounds impossible when it expects hardware backing, which tuna doesn't have. [2]
(Technically tuna hw has TEE support, but google disabled it for keystore already due to a power usage bug [3])
Edit:
Seems like Google left the old software encryption still in:
https://android.googlesource.com/platform/system/vold/+/69f4ebd
(use_keymaster == 0)
Didn't look at CTS yet if one still passes without hardware keymaster.
Or what's your take on it?
[1] http://www.gadgtspot.com/2014/10/31/roundtable-cyanogenmod-12-roadmap-leaked-fun-times-ahead/
[2] http://source.android.com/devices/tech/encryption/index.html#storing_the_encrypted_key
[3] http://nelenkov.blogspot.it/2012/07/jelly-bean-hardware-backed-credential.html
Same here...
Anyone else got problems with video playback in YouTube in the 20150201 nightly?
*Deleted
sorry, delete please
SELinux
Hi there Ziyan,
I don't know if it's a choice or something went wrong in the 05-10 CM11 Weekly build for the Maguro Gnex but the SELinux is disabled... Just wanted to point it out since i know that you guys usualy build with SELinux set to Permessive...
Have a good day
SELinux
Hi @Ziyan SELinux is still disabled in last weekly...
gps fix cm11 maguro
Hi Guys,
I can't get gps fix with cm11 maguro http://forum.xda-developers.com/galaxy-nexus/development/rom-cyanogenmod-11-kvt49l-samsung-t2405147
can anyone help me with this issue? I've tried 'fastergps' app without any luck
kernel left alone, I didn't changed it
Phone freezes and reboots right after wake up in CM11 20150626 Snapshot
Hi everyone,
I just updated the phone from CM11 nightly of a version maybe two months old to the latest CM11 20150626 Snapshot, and I get this problem.
Right after the phone reboots, the locking, unlocking works fine. After a while (seems every app finishes its starting up), when I lock the phone and wake it up, the phone freezes right away and reboots a while later.
Can anyone let me know how to identify or solve this problem? Thanks.
Edit:
Ok, I just did a factory reset and now it seems to be running ok.
Edit:
I finally found out it's because I forgot to flash kernel for the PGM app.. how stupid I am.
Thank for great ROM.
@Ziyan and any people who help to create the great ROM for our device, Last year we hope to use KITKAT and now we fulfill this great ROM. Thank you every one.
Q&A for [ROM][UNOFFICIAL][5/7] CyanogenMod 12.1 | Beta 1
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][UNOFFICIAL][5/7] CyanogenMod 12.1 | Beta 1. 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!
Great job guys. Going to wait till a more stable build but you guys should be very proud of yourselfs. None the less this is great work. Made my day knowing there are people like you guys.
Build you just posted
Just downloaded it and tested, the issues with the navbar/status bar etc. are still there.
Can' t wait for this to be finished, thanks for the hard work.
I just got to flashing this
I don't get navbars, status bar, or notifications shade either.
Volume buttons do nothing, trying to change brightness crashes Settings, there is no power menu.
The default CM12.1 wallpaper is also missing (black screen) and there is an icon missing from the dock.
Strange.
I couldn't test the camera (because I can't navigate anything without back or home buttons), so I can't say much about that.
Keep up the good work though, I'm more than willing to test any new builds!
Keep us posted!
Camera m9 sense port
Has anyone tried using the sense port for all aosp roms from
http://forum.xda-developers.com/lg-g3/themes-apps/mod-htc-one-m9-camera-port-t3056305
To see if that makes the camera work?
After flashing the 2 June build and then the current build, all seems to be working.
Interested....however need 2.8 firmware as base and everything working good battery life before I make the transition which I'm guessing could be awhile. Dolby audio also very important.. will keep checking thread for updates thanks for your efforts
Sent from my HTC One M9 using XDA Free mobile app
In safe mode :/
I installed it and everything but it boots into safe mode, problem is when i try to turn it off using power button it just restarts phone into safe mode without asking to power off or anything! Anyone got anything?
Not sure if OP or any of the devs are reading the Q&A section,
but I've been using the latest build (with the 2 June flash before, of course) on 1.32.* as my daily ROM since the statusbar/softkeys fix was posted.
Some interesting negatives/bugs I've noticed:
No double tap to wake
Battery usage data never shows up
Cannot search for service providers (Get an error, but selecting auto works and finds the correct carrier)
Possibly unrelated but the quick settings tiles for the notifications shade are extremely limited (No volume or independent brightness tiles, et cetera. I think these need to be implemented by the rom developer, as they exist for other CM12.1 devices on official roms)
Otherwise, I think all is working fine. (Well, minus what was marked "broken" (camera, USB OTG, ...) but it looks like there were recent commits on github for the SoC, so maybe this or a fix for newer frameworks is coming!)
Battery life is better than sense, and everything is much snappier. Xposed works (using v65 for now), as do most lollipop modules. (Except Amplify which blocks no wakelocks, but I think this is an arm64 issue because many M9 users are reporting this in the Amplify thread, even on Sense/"stock" roms.)
If anyone sees this (with more than 10 posts lol) please direct OP to the Q&A section so he can see these issues.
I'll continue to use this for now, I haven't had the reboot problem other people are experiencing.
If there's anything someone would like me to test, I'm more than willing, just let me know.
ptv9 said:
Has anyone tried using the sense port for all aosp roms from
http://forum.xda-developers.com/lg-g3/themes-apps/mod-htc-one-m9-camera-port-t3056305
To see if that makes the camera work?
Click to expand...
Click to collapse
I think the actual rom implementation (drivers/firmware) is the problem with the camera.|
It turns out that mods removed the download link in that thread anyway.
Sorry!
Unofficial cm 12.1 hima
I have flashed the ROM as instructed ... And all works well until the phone goes to "sleep". I an unable to wake the device. I have to power off and reboot phone. Is there a fix for this?
Downgrading Firmware
I've frankly had quite enough of the Sense UI, however, after flashing this ROM, I experienced the sporadic reboots and navbar issues which many other users have posted about. Some say that flashing back to the 1.32 firmware (in my case from 2.7) will fix the issue, but won't this bring back overheating issues and terrible performance?
@BananaMasamune and @rickymartel01,
Did you both flash the 2 June build before the 5 July build? That seems to have fixed navbar issues for most people.
Downgrading firmware fixed sleep and reboot problems for most of us as well.
I was never on 2.x so I'm not sure about performance problems, but it definitely feels faster and more fluid than Sense on 1.32.x
European
Is it working for European device?
---------- Post added at 08:58 AM ---------- Previous post was at 08:43 AM ----------
Is it working for Eruropean devices?
@dreznik82,
My device isn't from the United States, and it works for me.
Check to see if your phone is GSM or CDMA.
There is a list on HTC's website somewhere that lists carriers, and tells what version of the phone they have. Many of the GSM phones are WWE (world-wide edition, international) and can be used with this.
Nice work
Good work guys. How long you reckon it would take to get this as a stable nightly build once broken items have been resolved?
Also no status bar and navigation bar on mine as well
Does anyone know if xposed works ?
fix for downgrade
could you try to fix the ''downgrade'' problem in the next update?
because I am not able to downgrade (don't know why)
thanks
@Galaxysm , Xposed works.
@Rogi1997 , Are you S-Off?