Related
Hi, I'm a newer, I would like to ask if there is an Android ROM that can Bluetooth, WIFI, Camera and 3G work so far?Is there any ROM that also have HTC Sense?
If I install the ROM, will I damage my WinMo file?As I am still using HTC Official ROM now. Just worry can't go back if not satisfy and back to WinMo
Many thanks
Do Some Research B4 Posting!!!
Always backup your phone numbers and information you never want to lose, then start messing and testing with new items.
All awnsers are here already on the forum, and even within the first 5 posts.
Start looking in the android and windows mobile parts.
I didn't lose any data i had, cause i read everything there is to read
husam666 said:
Do Some Research B4 Posting!!!
Click to expand...
Click to collapse
I thought that you were the one who did not search?
ernestyung look in the sticky thread, there you will find your answers.
Thanks for all replies...
In fact, I read the forum for the whole day and what I have found so far is that all touch pro 2 android 2.2 ROM did not fix all problem yet. Therefore, I am asking for any ROM that works for all function even 2.1 ROM.
As far as I know, HD2 has launched the 2.2. ROM with all function working, don't know if that ROM can be applied on Touch Pro 2?
Thank you
ernestyung said:
Thanks for all replies...
In fact, I read the forum for the whole day and what I have found so far is that all touch pro 2 android 2.2 ROM did not fix all problem yet. Therefore, I am asking for any ROM that works for all function even 2.1 ROM.
As far as I know, HD2 has launched the 2.2. ROM with all function working, don't know if that ROM can be applied on Touch Pro 2?
Thank you
Click to expand...
Click to collapse
The ROM itself has no impact on hardware functions working, and those are all kernel issues. It doesn't matter if you put the same 2.2 HD2 ROM on your phone (which is easy to do) the TP2 kernel is more advanced than the HD2, and therefore further behind.
I have android running on my TP2 (verizon). Its nice to have both OS's on 1 phone, but its still very unstable, no sound, gps, cam, bluetooth, screen goes black 1 out of 3 times, phone still Lags. Im pretty sure these guys will get it right in a near future, so big ups for them!
Reefermattness said:
The ROM itself has no impact on hardware functions working, and those are all kernel issues. It doesn't matter if you put the same 2.2 HD2 ROM on your phone (which is easy to do) the TP2 kernel is more advanced than the HD2, and therefore further behind.
Click to expand...
Click to collapse
Do I need to Hard SPL before install and run the Android ROM on my memory card if I'm using official HTC ROM?Because it's dual boot winmo and android,that's why I'm not pretty sure.
u just gota test out different roms to find your liking!
ernestyung said:
Do I need to Hard SPL before install and run the Android ROM on my memory card if I'm using official HTC ROM?Because it's dual boot winmo and android,that's why I'm not pretty sure.
Click to expand...
Click to collapse
If you would read a little bit you would find out this doesn't even install to your internal memory(NAND), it installs to your SD card, hence why you can dual boot......
Reefermattness said:
If you would read a little bit you would find out this doesn't even install to your internal memory(NAND), it installs to your SD card, hence why you can dual boot......
Click to expand...
Click to collapse
Thank you Reefermattness~!!What I read all is just install in my memory card and that is....However, what I read from HD2 thread is that they need to hardSPL the handset before install the android ROM...That's why I worry so much....
ernestyung said:
Thank you Reefermattness~!!What I read all is just install in my memory card and that is....However, what I read from HD2 thread is that they need to hardSPL the handset before install the android ROM...That's why I worry so much....
Click to expand...
Click to collapse
Well a quick tip is don't read the HD2 forum for a TP2.
There are people that use this with stock ROM/Radio just fine.
Many thanks....Im playing around with the Andriod ROM with my TP2 now....quite fun
Hope that the final version is coming soon~~
Is there any such thing as a "final version"?
Questions and concerns have been clarified so closing thread.
If anybody needs further help, have a look at the stickies or open up a new thread.
seach is currently down.. i appologize..
so the past few weeks i've flashed what seems to be every rom that is out, and it's update.. i've sifted through them and narrowed it down to a few i switch between.. im to the point to where i'm curious as to the whole process and whats required to make a rom.. im sure there is a good deal that goes with it, but i'd just like to hear the jist of it all.. i currently run a windows xp os. im on a s-off droid incredible.. much thanks..
20twins10 said:
seach is currently down.. i appologize..
so the past few weeks i've flashed what seems to be every rom that is out, and it's update.. i've sifted through them and narrowed it down to a few i switch between.. im to the point to where i'm curious as to the whole process and whats required to make a rom.. im sure there is a good deal that goes with it, but i'd just like to hear the jist of it all.. i currently run a windows xp os. im on a s-off droid incredible.. much thanks..
Click to expand...
Click to collapse
Check out the chef central forum on this site. There is a kitchen that can be useful for modifying existing roms. Also, there is a topic titled "some advice" by cyanogen. That has some links that will help you get started. You should look into running some flavor of Linux (i prefer ubuntu, but you aren't limited to that distro). What is your experience so far?
sent from my Droid incredible using the xda app
I have no experience with any Linux distribution. Years back I always wanted to get into it just never did.. I'm good with taking pre existing code and learning it and adding to it.. I know I'd be going with a sense based rom, and try to add some functions from other existin told..
I will have to check out the chef forum here. I've never clicked over to it , bit it definitely sounds like it will ne helpful.. much thanks..
Sent from my ADR6300 using XDA App
*Any major linux distro
*Dsixda Kitchen: http://forum.xda-developers.com/showthread.php?t=633246
*ROM (comes in zip form)
*APKTool: Follow the video below to get that downloaded and setup on linux
The 4 basic things you will need, you can search the forums here for the Kitchen. Like previously stated you can use Ubuntu or Linux Mint which is based off Ubuntu.
A forum Member named Heyitslou made a tutorial on how to use the APKTool also: http://blip.tv/file/4382608.
The kitchen is pretty straight forward on what you can do with it...just follow the thread on how to set it up.
Remember be patient while you are making your ROM (some trial and error, best to work on a phone you dont rely on for important calls)...I have made my first ROM this weekend...I swear I had to cook it 50 times to get it working properly with what i wanted to change and add...so 50 ROM flashes=alot of time you wont be able to get calls... just a heads up. I am pretty sure next time I edit in some changes it will be faster and easier...The Kitchen is a great tool and does what you want..just got to know what not to do in the kitchen...it could be messy.
magneticzero said:
*Any major linux distro
*Dsixda Kitchen: http://forum.xda-developers.com/showthread.php?t=633246
*ROM (comes in zip form)
*APKTool: Follow the video below to get that downloaded and setup on linux
The 4 basic things you will need, you can search the forums here for the Kitchen. Like previously stated you can use Ubuntu or Linux Mint which is based off Ubuntu.
A forum Member named Heyitslou made a tutorial on how to use the APKTool also: http://blip.tv/file/4382608.
The kitchen is pretty straight forward on what you can do with it...just follow the thread on how to set it up.
Remember be patient while you are making your ROM (some trial and error, best to work on a phone you dont rely on for important calls)...I have made my first ROM this weekend...I swear I had to cook it 50 times to get it working properly with what i wanted to change and add...so 50 ROM flashes=alot of time you wont be able to get calls... just a heads up. I am pretty sure next time I edit in some changes it will be faster and easier...The Kitchen is a great tool and does what you want..just got to know what not to do in the kitchen...it could be messy.
Click to expand...
Click to collapse
im going to look into the Cygwin method as dsixda stated in the kitchen thread.. im anxious to getting to ripping out parts of roms and merging if possible..
so ima switch to the virtualbox/ubuntu method for this.. i think it will be easier for me to solve issues with community support this way..
20twins10 said:
so ima switch to the virtualbox/ubuntu method for this.. i think it will be easier for me to solve issues with community support this way..
Click to expand...
Click to collapse
I recommend just going ahead and installing the OS directly, but that's just what I would do.
sent from my Droid incredible using the xda app
maybe at some point in the future if my brain becomes that curious to the OS itself.. for now this method will do..
so i downloaded the java6 bin and jre, trying to install it via terminal i'm getting nowhere..
dpkg-i command not found
java installed
kitchen installed
now to go rip apart my laundry tub plumbing and replace it..
whats the nitty gritty on getting behind the scenes on a previously compiled ROM??
When building an androidinstall.tar from scratch, do I need to include the META-INF file as well?
I will try without it as this build was for a different phone that I extracted and decompressed. I have already separated the apps and placed them in their own /data folder and removed them from the /system folder.
It is an unodexed build so no .odex files were included.
I was looking through other builds I have on hand and noticed no META-INF file, thats the reason for asking.
First error:
[ 127.061609] init: Unable to open persistent property directory /data/property errno: 2
Then a whole mess of kernel errors, possibly due to wrong system...
FIXED! Awaiting boot animation to finish.
Honeycomb boot animation is SO cool looking!
EDIT: NOT fixed, refuses to finish booting. Will work on it more to see if I can get it to boot up.
So far I've gotten to the point where the D-pad and keyboard light but boot animation continues.
Build is Android 3.0 Honeycomb with parts and drivers taken from "system_gingerbread_unodex" listed on sourceforge.
Someone tell me what I've missed here as it's about 80% finished booting and hangs after D-pad lights, animation continues until I pull the battery, about 10 minutes.
Getting an error "cannot execue /system/bin/leds.sh, no such file or directory", even though I made sure to copy it and went back and checked it.
Sorry if this looks like I'm using the forum as a sounding board, but I found an experimental build of Honeycomb for the MSM7201A and wanted to try it out.
Watch me cook the only Kaiser I have left...
All but giving up for now, will dig deeper. I know HC was NEVER meant to run on our Kaisers but it would be fun to see it happen.
Wow you are insane! (I mean that in a good way)
I have a Xoom tablet that runs honeycomb, but can't even imagine it running on our sweet Kaiser. Heck, I don't even like gingerbread: uses too much RAM.
Keep us posted, it sounds like a wonderful experiment.
I'm so close yet so far with it because I'm using more and more of Gingerbread in the build. I even ended up trying to change the build.prop file to accomidate some of the changes in dimensions and clock speeds...
I think I'm about 90% there, just have some issues with the bootanimation restarting, which I may change to the nexus for the smaller size. (HC boot animation is somewhere around 14mb compared to our partly 875kb nexus animation). That could be half the problem because the bootanim uses so much of the ram...
To be continued...
Ok This is a very interesting project
I am from the vogue forum but since my touch broke and the build process is identical I just sort of wander around trying to help with what I know.
So at one time I did a lot of porting and it appears according to your first post this is what you did. What phone did you take the rom from?
If its from the wildfire (I know there was a honeycomb movement in there for a while) I can definitely help because that is where I did most of my porting from
And the META-INF question... When I port I usually trash a bunch of folder straight away ... including META-INF
Good to know there are "floaters" around helping as needed.
BTW, it IS from the Wildfire port. Considering the MSM family is bascally the same, I'm trying to use that as a starting point.
The META-INF file contains certificates and what-not but isn't needed for our phones.
My biggest issue right now, as with any Gingerbread release, is finding drivers for our devices. Froyo drivers won't work because they lack the correct signature. Same as if someone tries to install the HTC flip clock on a plain android without the sense build, it just doesn't work.
I have this project and trying to port the kernel we use to the Raphael (Touch pro/Fuze), which is a major task in and of itself. I tried HaRet before with the Kaiser and I jus HATE it.
Biggest issue with the Fuze right now is to get it CID unlocked so I can try installing the kernel to NAND and go from there.
With that being said, I don't know what kind of progress I'll be making with HC in the near future, if any.
Ok, I went back and restarted the project from scratch. Someone else ported the bootanimtion and different aspects of HC to a Froyo port on the Xperia X1 forum.
I recompiled everything at first, moving the "app" folder inside a new folder named "data", since our NAND constraints limit the build size to under 102mb for /system.
Once again I am stuck at the boot animation. It will go full-speed for a minute then restart and run slow. The only parts taken from the X1 were the app folder and media/bootanimation.zip
I'll dig a little deeper, maybe ask around the X1 forum for help.
Would be nice to finally figure this out though.
Hi PoXFreak. It seems like you're a very good dev. Could i help you somehow or could you link me to somewhere where i could get all the tools for rom and kernel building. Im a C++ learner, i've written a few apps, but only big thing i've done in android is installed sdk and modified a rom to have apps i need after install. I'd rly like to improve our kaisers.
P.S. dou you put anynthing compilled by urself in android rom (without kernel)? And where are the drivers located? system/lib/modules/[kernelversion]/ or system/lib/modules/ ???
zxxxy said:
Hi PoXFreak. It seems like you're a very good dev. Could i help you somehow or could you link me to somewhere where i could get all the tools for rom and kernel building. Im a C++ learner, i've written a few apps, but only big thing i've done in android is installed sdk and modified a rom to have apps i need after install. I'd rly like to improve our kaisers.
P.S. dou you put anynthing compilled by urself in android rom (without kernel)? And where are the drivers located? system/lib/modules/[kernelversion]/ or system/lib/modules/ ???
Click to expand...
Click to collapse
The .so files go into /system/lib/modules/(kernelversion).
Sent from my Android on HTC Kaiser using XDA App
I have yet to make a complete working build from my work so no, I have nothing "new" to contribute to any android builds. All I'm doing is combining and rearranging/replacing/removing files already in builds.
To date, I have not had the time to work on this. I would like to be able to devote more time but I have too much on my plate already. Not to say I'm dropping the ball, just putting it on the rack for awhile.
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:
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)