Related
I'm using this thread to share working pdroid patches I've got for various Galaxy Nexus roms. This was made using the patcher being developed here (patcher is in the 4th post). The patcher is currently linux-only, but will also work with cygwin in windows. I'm posting the finished flashable zip here as a convenience to anyone who can't use it themselves. Please note that I am not one of the people actively developing this patcher, just a willing tester who happens to own a toro Gnex.
If you don't know what Pdroid is, this is the thread for it on xda. Basically, it lets you deny permissions to apps on a per-permission basis, without risking apps crashing. Same basic idea as LBE privacy guard, but in my opinion executed better. Plus, open source is always a plus. Even though the official patcher there won't work for us yet, check the official thread. You'll need to download the app from the market and follow the same instructions, just using the zips I'll post here (or make your own).
I'll include a revert.zip for anything I post here, but please note that I take no responsibility for anything that happens to your phone. Make backups before flashing things. Try TWRP if you haven't, it's faster at backup/restore than CWR and does a bunch of other neat stuff like compressed backups and queued zip flashing. Also, in case of things breaking, please note that these revert zips are (1) only going to work if you are running the same rom used to create the zip and (2) just a slimmed down version of the rom's zip. What this means is that if you flash a pdroid zip and you need to revert, the surest thing to do is just re-flash your rom without wiping anything.
I'll try to update this thread as I get more patches working. Here's where my own experiments stand:
Link to my dropbox folder with files, notes below
Working patches:
-AOKP b39 (toro):
-AOKP b39 (maguro):
-CM9 Nightly: Patched build: 2012/06/19
--Note: Not sure if these will automatically fail with later nightlies or only when something relevant is updated in the rom. Feel free to try, just reflash your rom if it bootloops.
-Stock AOSP(+root, busybox): Patched build: 2012/06/02
-Paranoid Android v1.4a
Not Working (Yet):
-Liquidsmooth 1.5RC4:
-Slim ICS 4.0:
Unless otherwise noted, these are all for the toro (verizon) Galaxy Nexus. It's pretty quick and easy for me to make new patches so feel free to request something. But please be aware that sometimes it's a few days between when I can devote any time to this and don't be offended if I don't reply to you right away.
Just to reiterate, all you need to do for this is download the "Pdroid Patch Zip" file for your rom, flash it in recovery, and download Pdroid from Google Play.
Finally, be aware that the first boot after flashing can take a very long time, without any indication like the "Android is Upgrading..." screen. Don't assume it's bootlooping! Seriously, put the phone down and do something else for a bit. Anything in the tested section I've either personally flashed on my phone or someone else reported as working. If you're sure you're getting a bootloop on a clean install, my only advice is to do a full revert to stock and re-unlock/root/etc and see if it works then. Though rare, it is possible for something to be corrupt that persists across the usual "clean install" routine.
Isn't that what Permissions Denied does?
https://play.google.com/store/apps/details?id=com.stericson.permissions
Wow, I didn't realise you could patch AOKP on ICS yet. Have been waiting for this for so long. How would I go about applying your patch for AOKP gsm?
xternal said:
Wow, I didn't realise you could patch AOKP on ICS yet. Have been waiting for this for so long. How would I go about applying your patch for AOKP gsm?
Click to expand...
Click to collapse
For gsm you'd need a new patch. There are instructions in the first thread I linked to if you'd like to try it out. I might make one in a bit since I expect that to be a popular request and I expect it to work.
danger-rat said:
Isn't that what Permissions Denied does?
https://play.google.com/store/apps/details?id=com.stericson.permissions
Click to expand...
Click to collapse
Same idea, different approach. Permissions denied generally causes apps to crash if they need info that they are denied. I also had a major issue with it a while back that I ended up doing a factory reset for, but I think that's been fixed since then.
Not sure how pdroid gets around apps fc'ing (maybe it spoofs data so apps go on running normally? It has an option to set your own values I haven't played with much), but it works very smoothly.
xternal said:
Wow, I didn't realise you could patch AOKP on ICS yet. Have been waiting for this for so long. How would I go about applying your patch for AOKP gsm?
Click to expand...
Click to collapse
Quick update, I put up a maguro for AOKP, and I also updated the OP quite a bit since I last posted. Finally got around to testing the patches I made; getting better at reading the patching process as well to tell when a patch will work before flashing it, too.
At far as updates go, I don't really intend to follow the cm9 nightlies as I don't run them myself. I'll probably continue to try new versions of AOKP and paranoid android as they come out. I'll continue to try the roms that don't patch yet with new versions of the patcher as they are released.
Thank you. The maguro patch works for me.
Edit: not sure, but this likely breaks 2 apps: Listen, Drive.
I've been using LBE Privacy to control permissions and this app doesn't crash apps that have permissions blocked. It's one of their selling points, doesn't crash apps.
deaffob said:
I've been using LBE Privacy to control permissions and this app doesn't crash apps that have permissions blocked. It's one of their selling points, doesn't crash apps.
Click to expand...
Click to collapse
PDroid source has been released, whilst LBE created by a 'suspect' chinese company. I put the suspect in inverted comma's because nothing has actually been proven.
The patch works a treat on GSM aokp, many thanks
edit: looking at it though, it seems it doesn't find all the permissions correctly. I am assuming this is a limitation of the current pdroid as it is not designed for ics.
For instance it does not find hardware controls. Google Drive has access to hardware controls to take photos/videos.
Thanks for the confirmations on the maguro zip, I edited the post to reflect that it's definitely working.
I hadn't heard of LBE before making these threads but from what I've read it seems like people generally prefer pdroid. I'll check it out at some point but it looks like it does a bit more than I'd want it to, and pdroid being open source is definitely a plus.
IIRC, there's certain instances where apps can bypass LBE but not PDroid. I think reboot is one of those times due to when LBE loads.
I've been running LBE but lately the service keeps stopping because it doesn't get root soon enough after boot. Trying this now on Paranoid. Thanks!
i have used this patch for CM9 but after the Bootscreen have i a Blackscreen -.- what can i do?
SGDynamite said:
i have used this patch for CM9 but after the Bootscreen have i a Blackscreen -.- what can i do?
Click to expand...
Click to collapse
I'm guessing you are running a different build/more recent nightly? I might take that link down as it was meant as more of a proof of concept if the cm9 patcher was working and it's unlikely anyone is going to be flashing that particular build just to test pdroid.
The most effective thing would be to just re-flash the original rom's zip, you don't need to wipe anything. The revert zip file is basically just four files copied from a given rom's original zip, services.jar, core.jar and framework.jar in /system/framework, and build.prop in /system.
xternal said:
LBE created by a 'suspect' chinese company. I put the suspect in inverted comma's because nothing has actually been proven.
Click to expand...
Click to collapse
I hadn't heard of pdroid until I was on the Nexus, so I'm not familiar with it to compare, but I'm currently using LBE and blocking its data connections with Droidwall. Perhaps a bit overkill... but works great as far as I can tell.
Sent from my Galaxy Nexus using xda premium
JoeSyr said:
I'm guessing you are running a different build/more recent nightly? I might take that link down as it was meant as more of a proof of concept if the cm9 patcher was working and it's unlikely anyone is going to be flashing that particular build just to test pdroid.
The most effective thing would be to just re-flash the original rom's zip, you don't need to wipe anything. The revert zip file is basically just four files copied from a given rom's original zip, services.jar, core.jar and framework.jar in /system/framework, and build.prop in /system.
Click to expand...
Click to collapse
I think I flashed it to a nightly a day or two after 5-18 and it worked, but it definitely did not work on 5-27 or 5-29.
If the patch doesn't work for you, pull the battery, then hold volume up and down while you hold power, then use volume up and down to get to recovery option--press power to select. Either flash the revert or the old from there on top of the non-working one. Don't clear data partition and you won't lose anything.
@Joesyr, I think there is some interest in CM9 nightly patches...would you mind making a CM9 patch maybe once a week? I haven't had any luck making the patch on my own.
robjective said:
I think I flashed it to a nightly a day or two after 5-18 and it worked, but it definitely did not work on 5-27 or 5-29.
If the patch doesn't work for you, pull the battery, then hold volume up and down while you hold power, then use volume up and down to get to recovery option--press power to select. Either flash the revert or the old from there on top of the non-working one. Don't clear data partition and you won't lose anything.
@Joesyr, I think there is some interest in CM9 nightly patches...would you mind making a CM9 patch maybe once a week? I haven't had any luck making the patch on my own.
Click to expand...
Click to collapse
Well the last cm9 nightly I tried didn't patch at all (I believe it was a 5/29 build). I will try tinkering with things as I get the time but I'm not really at the level of fully understanding these kinds of failures yet.
Next time there's an updated cm9 patch I will try to get a working pdroid zip and I'll consider weekly updates. I'm also generally willing to make these on request as it's a pretty quick process. Fiddling with dropbox links is probably the longest part of any of this.
Any particular issue you're having with the patcher? I've been thinking I could write a little tutorial for getting cygwin up and running since I imagine that for most people the limiting factor is just that they don't have a linux environment to work in. But until I get the time to do that I can help troubleshoot.
Can you make a patch for stock root.
Thx
Has anybody experienced random rebooting? All was fine until I opened a non system app. Then it just started rebooting randomly after opening any app. I ran it on Maguro with AOKP b37.
soloxp said:
Can you make a patch for stock root.
Thx
Click to expand...
Click to collapse
Yup, not sure if the rom I just put up is the same you were looking for but it's the first one I've been able to get to patch correctly with the aosp patch.
Just flashed the Toro AOKP b37 patch, tested and working great here. Thank so much! Awesome work!!
or at least it seems like it.
i downloaded the port over version the other day before all the "close this thread now" stuff. And i have loved it so far.
But, i just got a notification on my phone that said there was an update available, out of curiousity as to it being verizon or venom, i clicked download and it said the following.
"You using illegal copy of our ROM, to fix it apply update" and so forth and so on.
My question is the Venom rom now ready and they are just sending out an update to get up to their specs or is this update going to kill my phone. I have no problem taking this rom off and putting something on if this update was designed to kill the old version, just want to get some answers before i go in any directs.
was just struck off guard today with this development...
thanks,......
jhollon said:
or at least it seems like it.
i downloaded the port over version the other day before all the "close this thread now" stuff. And i have loved it so far.
But, i just got a notification on my phone that said there was an update available, out of curiousity as to it being verizon or venom, i clicked download and it said the following.
"You using illegal copy of our ROM, to fix it apply update" and so forth and so on.
My question is the Venom rom now ready and they are just sending out an update to get up to their specs or is this update going to kill my phone. I have no problem taking this rom off and putting something on if this update was designed to kill the old version, just want to get some answers before i go in any directs.
was just struck off guard today with this development...
thanks,......
Click to expand...
Click to collapse
i don't think anybody would side with venom if they released an update that killed somebody's phone over a ported rom.
wiredout46 said:
i don't think anybody would side with venom if they released an update that killed somebody's phone over a ported rom.
Click to expand...
Click to collapse
i agree, i was just trying to find out if anyone else had seen this and did the update to see what gives.
UPDATE: i tried to install the update and it fails every single time. not sure what it is supposed to do, but it fails. just thought i would shoot the update to everyone. i am fairly certain that i am not the only one.
thanks,
see if the ROM that we are using was ported from got an update.. since it's a port, it's likely the update is for sprint...
thought that is what it might be, but the "illegal" ROM part made me wonder a bit more than usual..
http://forum.xda-developers.com/showpost.php?p=47380724&postcount=213
turge had asked members of the verizon one community to supply fixes to enable verizon to work properly with the intl venom rom
this wasnt meant to have people fix up the rom for verizon and release it.....when its meant to be released to the public, it will be
our server cant distinguish between actual kang roms (ie chinese ones which are so prevalent) and ports that are being worked on....my advice is to not use a venom rom on your verizon one until turge or jan release it via an official thread
it wouldnt be an update from verizon as its not a verizon based rom with verizon ota files in it
nitsuj17 said:
http://forum.xda-developers.com/showpost.php?p=47380724&postcount=213
turge had asked members of the verizon one community to supply fixes to enable verizon to work properly with the intl venom rom
this wasnt meant to have people fix up the rom for verizon and release it.....when its meant to be released to the public, it will be
our server cant distinguish between actual kang roms (ie chinese ones which are so prevalent) and ports that are being worked on....my advice is to not use a venom rom on your verizon one until turge or jan release it via an official thread
it wouldnt be an update from verizon as its not a verizon based rom with verizon ota files in it
Click to expand...
Click to collapse
Perfectly said, Sir.
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][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?
Keep the trouble shooting questions for each specific ROM or Kernel to THEIR threads. So that way Devs can be made aware of any errors to be able to work on, if need be, and for when people are searching for solutions to their problems the answers won't be scattered around. Consolidation makes everything easier!
What's your build? What are you loving about it? Any MOD recommendations?
Mine:
Viper10 ROM by TeamVenom
ElementalX Kernel
&
A.R.I.S.E
Sound Systems™ audio MOD
I'm a first time rooter (introduced to it by my fiance) and aspiring developer. I am going back to school to get that ball rolling. I'm socially awkward whilst being a social butterfly (once I'm out of my shell). The A.R.I.S.E team and TeamVenom have helped me to come out of that shell here on XDA so I'm ready to get socializing and talk all things root! However, I don't want to blow up their threads with unrelated posts...and so I've created this thread - so let's have at it and share ideas, opinions, and have fun! Remember to keep issue/ questions related to each ROM, Kernel, MOD etc. posted ON THEIR threads! So please include a link to their XDA thread when sharing what you've got.
Be kind and respectful. And have fun!
(Still need assistance with getting your HTC 10 rooted? Check This Guide out!)
https://youtu.be/1iAYhQsQhSY
Mine are
LeeDrOiD10 ROM
either with the build-in
~clumsy~ Kernel
or
ElementalX Kernel
No sound mods as the audio boost of LeeDrOiD is workin' just fine with the build in DACs
Used Viper for a long time and it is a great ROM. In fact I went to LeeDrOiD10 cause the tweaks on Viper10 are just so many, and most of them I've never used at all. On LeeDrOiD there are just a few tweaks, where all those I need and use are present.
Cheers
Only Cool Kids Reply to Their Empty Threads
EDIT: Lol got a post while taking 10 years to write this one...so it doesn't appear as though I was my own first response...but if I wrote like a normal person, I would have been.
TL;DR - Zip below will get rid of red message during boot, REQUIRES S/OFF, if you choose to flash this I'm NOT responsible for bricked phones, this zip file works for US Unlocked HTC 10 phones - but I'll rewrite the files inside to match your CID if you need me to, not originally my work and I don't know who's it is...sorry!
-Rename the zip file 2PS6IMG.zip & place it in the external SD card
-Boot down to download mode and if it's all groovy there will be a message at the bottom outlining that it found the "2PS6IMG" zip file and will tell you to press VolUp to proceed with the flash or VolDwn to continue to the normal download mode screen options
NOTE: if your screen doesn't display that initial message at the bottom and just goes to the normal download mode options then you've named the zip file wrong. Make sure that you didn't end up with 2PS6IMG.zip.zip during the renaming process - it HAS to read 2PS6IMG.zip or download mode will not see it as it is scanning for that name exclusively!
- If you got the message go ahead and hit volume up and, when prompted at the end, hit the power button. If you're phone boots down immediately after hitting the volume up button DON'T FREAK and leave it be. It'll kick back up and finish it's thing.
- Reboot and enjoy! (First boot up may take longer than you're comfortable with, that's normal chill for a moment and it'll all work out)
(First to reply to my own thread, crazy stuff happening here...watch out! )
Never understood why the TL;DR is put at the bottom. I know I write novels...I love words but I feel the TL;DR is more thoughtful to place at the top...so you don't have to wade through the overwhelmingly copious amounts of my words to find out there was a TL;DR option. Always thinking of you :angel: however, surely there exists an individual who not only continues and reads my posts in their entirety, but is as entertained reading it as I am writing it!
.............
Anyway, since this is meant to be a thread in which we share fun rooting tweaks and whatnot, I thought I'd go ahead and add this zip file. If you aren't a fan of the red message during the boot up that appears after you've successfully rooted - I've got your solution! I do have to apologize... I'm not sure who the original creator is. My fiance sent the file to me through Bluetooth and I rewrote a couple lines in the file so it would work with my CID. I tried to find the correct individual or thread to link in order to give them the proper credit, but there were a few posts for it so I'm unsure who it is. Just know I'm not trying to claim this for my own... just sharing the love :victory:
MAKE SURE YOU ARE S/OFF BEFORE DOING THIS! YOU'RE FLASHING THIS ON YOUR OWN ACCORD, I'M NOT RESPONSIBLE FOR ANY SOFTWARE/ HARDWARE FAILINGS
This is for the US Unlocked phones. So if you're not US Unlocked, but you want up in this sexy zip action, let me know and I can rewrite the file for you. The CID just needs to be rewritten to match the one on your phone. As a precaution I also rewrote the "mainver" line. It had the original 1.21.531.1 (T-Mobile's current software number) to the updated 1.80.617.1 (the current software number for US Unlocked). I wanted it all lined up perfectly, just in case, however IDK if you need to rewrite the "mainver" live in that text file my phone is fully functional after the rewrite and flash so I'm confident that I took the right steps. I posted what I've got going on for my custom ROM/ Kernel in the OP, if that's important for you to know. I've got the instructions above in TL;DR - no need to repeat. Let me know if you have any questions!
:highfive:
5m4r7ph0n36uru said:
Mine are
LeeDrOiD10 ROM
either with the build-in
~clumsy~ Kernel
or
ElementalX Kernel
No sound mods as the audio boost of LeeDrOiD is workin' just fine with the build in DACs
Used Viper for a long time and it is a great ROM. In fact I went to LeeDrOiD10 cause the tweaks on Viper10 are just so many, and most of them I've never used at all. On LeeDrOiD there are just a few tweaks, where all those I need and use are present.
Cheers
Click to expand...
Click to collapse
Thank you for the reply! I haven't checked LeeDrOiD10 out personally, but I saw it on my fiances phone when he got uber frustrated at a camera defect post viper update. The V10 ROM update caused our kernel to be temporarily incompatible...so he temporarily ditched V10 and tried LeeDrOiD10.
He was saying the same things as you in regards to fewer customisation's. And hebmade mention of it being a little more user friendly. But, ultimately, he returned to V10
EDIT:@5m4r7ph0n36uru what exactly does the LeeDrOiD10 ROM offer in terms of the sound boost? An equalizer? Or a little more than that. I didn't check that feature out. I didn't know it was one. My other half may have known though. We love the crazy amounts of tweaking you can do with Viper4Android in the A.R.I.S.E. MOD and all their tweak.prop files/ profiles that we can load up!
Being a spectator of LeeDrOiD10 was sufficient enough for me...only because I know myself, and I LOVE having as many options and open doors, in regards to messing around with my phone, as possible. Tis more dangerous waters to tread that way...but that's all the fun! And I'm confident enough in myself to be able to recover from most things. After all XDA has strong support to offer!
Yeah I know and it always has been fun changing nearly every detail in a ROMs behavior as it is possible on Viper10. But in fact I guess I'm maturing from this phase in my live where modding was the one and only, as we'd say in germany.
In fact I'm getting older and less fascinated by all those features. Maybe it'll come a time when I'll again become fascinated by modding and tuning every tiny bit of a ROM, but at the moment I really just need some basics.
Sent from my HTC 10 using XDA Labs
5m4r7ph0n36uru said:
Yeah I know and it always has been fun changing nearly every detail in a ROMs behavior as it is possible on Viper10. But in fact I guess I'm maturing from this phase in my live where modding was the one and only, as we'd say in germany.
In fact I'm getting older and less fascinated by all those features. Maybe it'll come a time when I'll again become fascinated by modding and tuning every tiny bit of a ROM, but at the moment I really just need some basics.
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
There's a flavor for everyone! And our taste buds change over time for sure. So long as you're happy with your phone and its features, that's all that matters!