I just ported the Sensation Rom, using the dsixda kitchen. Everything seemed to be going fine until I flashed ROM and is giving me, "Can't open....... (bad)". thru the FAQ on the kitchen post it was stated I need to change the recovery menu, (I'm a flashaholic.. not a dev yet ) so how do I change the RM.....
Please help I would like to post this alpha tonight
*****if anyone wants the link******
it's the new sense 3.6 ics 4.0 Rom All help welcome
Now I'm probably totally wrong....
But looks to me like either a bad download or that things aren't signed properly.
I guess we'll both wait till someone more knowledgeable comes along
~ I'm a fungi
a senile fungus said:
Now I'm probably totally wrong....
But looks to me like either a bad download or that things aren't signed properly.
I guess we'll both wait till someone more knowledgeable comes along
~ I'm a fungi
Click to expand...
Click to collapse
OK will look at them again ...... and try to redo them...... thankss
(Do you think I should try to post in development forum also? )
ku_ said:
OK will look at them again ...... and try to redo them...... thankss
(Do you think I should try to post in development forum also? )
Click to expand...
Click to collapse
No, don't post in the Development forum, as this isn't Development (yet) - it's still a question.
I'll download your file and see what's going on.
EDIT: Well first off, the ROM is WAYYYYY too big. Did you remove anything from it? Did you set up any symlinks to the Data partition to make up for the space the EVO lacks on /system? How exactly did you port it? Did you only use the tools in the kitchen? Not only won't that give you a complete working (or booting, even) port, but you'll end up having duplicate files, for multiple devices. What kernel are you using? There isn't an ICS Sense kernel for the EVO, so I'm curious to know how you were able to mod the existing GB Sense kernel code (or maybe the modified ICS AOSP code?) to get it working.
EDIT 2: I see you're using the build.prop from the Sensation, which will cause problems. Also, the Sensation is a qHD device - did you resize anything for our WVGA screen? You're better off starting with trying to port the new Primo leak, but even then, you'll never get it to boot without an ICS Sense kernel.
Captain_Throwback said:
No, don't post in the Development forum, as this isn't Development (yet) - it's still a question.
I'll download your file and see what's going on.
EDIT: Well first off, the ROM is WAYYYYY too big. Did you remove anything from it? Did you set up any symlinks to the Data partition to make up for the space the EVO lacks on /system? How exactly did you port it? Did you only use the tools in the kitchen? Not only won't that give you a complete working (or booting, even) port, but you'll end up having duplicate files, for multiple devices. What kernel are you using? There isn't an ICS Sense kernel for the EVO, so I'm curious to know how you were able to mod the existing GB Sense kernel code (or maybe the modified ICS AOSP code?) to get it working.
EDIT 2: I see you're using the build.prop from the Sensation, which will cause problems. Also, the Sensation is a qHD device - did you resize anything for our WVGA screen? You're better off starting with trying to port the new Primo leak, but even then, you'll never get it to boot without an ICS Sense kernel.
Click to expand...
Click to collapse
Holy Shyznit batman!!!!!! ok i'm still learning Just wayy to eager to help out .... Capt.
I used the tools in the kitchen, this would've /is the alpha - all resizing and tweaks would have been done from alpha 1.0 (this 1) through the final.
Is there another kitchen I could use that will make this easier on the kid....lol
ku_ said:
Holy Shyznit batman!!!!!! ok i'm still learning Just wayy to eager to help out .... Capt.
I used the tools in the kitchen, this would've /is the alpha - all resizing and tweaks would have been done from alpha 1.0 (this 1) through the final.
Is there another kitchen I could use that will make this easier on the kid....lol
Click to expand...
Click to collapse
No. If you're just starting out porting, it's best to start with something that actually has a chance at working, so that you can understand how everything works and what everything does. Technically, you don't even need the kitchen to port a ROM - it makes it about as easy as it can, while recognizing that it's an experimental feature with limitations.
There's a thread about porting different versions of Sense that should help you with the files that you actually need to move, and the content in the (now closed) kitchen thread should help out if you have any issues (sd card won't mount, sound doesn't work, etc.).
I recommend you first try to port something close to the EVO, like a Shift ROM. Try to get Sense 2.1 working on the latest OTA. I bet that'll take a whole lot of work, if you can do it at all (different versions of GB). If you do, you'll definitely have some skills/tools that can help you in your quest for ICS Sense.
ku_ said:
Please help I would like to post this alpha tonight
Click to expand...
Click to collapse
Take it from someone who had cooked and posted literally hundreds of rums for multiple devices, and don't post anything until you've built at least 20 different (semi-)working roms for yourself first. You are opening the door to major criticisms (*****ing) and a lot of support work (which you may not be ready for) if you make your work public too prematurely.
Captain_Throwback said:
No. If you're just starting out porting, it's best to start with something that actually has a chance at working, so that you can understand how everything works and what everything does. Technically, you don't even need the kitchen to port a ROM - it makes it about as easy as it can, while recognizing that it's an experimental feature with limitations.
There's a thread about porting different versions of Sense that should help you with the files that you actually need to move, and the content in the (now closed) kitchen thread should help out if you have any issues (sd card won't mount, sound doesn't work, etc.).
I recommend you first try to port something close to the EVO, like a Shift ROM. Try to get Sense 2.1 working on the latest OTA. I bet that'll take a whole lot of work, if you can do it at all (different versions of GB). If you do, you'll definitely have some skills/tools that can help you in your quest for ICS Sense.
Click to expand...
Click to collapse
ok will do if I have a question or need help could I call you up, through gtalk?
indagroove said:
Take it from someone who had cooked and posted literally hundreds of rums for multiple devices, and don't post anything until you've built at least 20 different (semi-)working roms for yourself first. You are opening the door to major criticisms (*****ing) and a lot of support work (which you may not be ready for) if you make your work public too prematurely.
Click to expand...
Click to collapse
shhhhhooooooot *****ing ain't nothing new ..... lol I have tough skin But I do heed the warning and is grateful for the insight..... if night call you up also if possible.
haha you see?
I told you somebody more knowledgeable than me would come around...
Thanks guys
~ I'm a fungi
One major problem is there's not a fully functional kernel to boot ICSense soooo that's the first issue here, next would be if the dpi and images haven't been resized to match the evo's resolution there will be major visual flaws and possible won't boot, if you really want to start porting roms I'd suggest starting with a GB rom since they are stable and there's alot more info and tools out there to get it ported
________________________________
{We are legion, for we are many}
>Sent from my Anonymous DeathStar in the depths of GalaXy S2<
-Coming soon to an Evo4G near you?: [AoSP]EViL-MoD_FReEvO v0.1[Free your phone]-
Related
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.
This isn't another one of those 'can somebody port Sense' threads.
Please note that this thread is for developer-oriented discussion. If you don't have anything to say to help development, please refrain from posting here.
Also note that ideas are welcome. Just check if the idea you're about to post has already been posted by somebody else.
Right now, it's just multiple people working on this. No team, just individuals.
As of the last edit of this post, there has been little to no progress:
I'm constantly working on builds. The current, and the only goal I'll be striving towards as of now is using a T-Mo HTC One X ROM in combination with RaymanFX's CM10.1 RC2 build.
XDA RC @abcdjdj has reported that he has fixed a lot of errors in his build, and is now stuck at the bootanimation. If you can help him in any way, here is what's wrong with his build. He's using FXP's CM9 as a base and a 4.0 HTC One X with Sense 4 ROM as a port.
The OP will constantly be updated with any progress anyone makes.
We're currently using this XDA thread to help us port the ROM.
--------------------------------
Here's everything I have to share on my build:
PORT: HTC One X, T-Mobile Edition| Android 4.2.2
BASE: Sony Xperia S, nozomi | Android 4.2.2
------------------------
ITesters needed. If you can work through adb commands and can provide me with logcats, please leave a post about it in the thread.
And finally, a note to anyone that may be cursing me for working so very slow (because I admit, this is very slow):
Please understand that all this isn't easy for me. I have painfully slow internet, making each download at least one hour, and thus a pain. My time on this project is limited every day, so progress is slow.
Reserved.
someone755 said:
Okay, so this is the work that has already been done and some of the mysteries that puzzle me right now:
I've edited the CM9 kernel's ramdisk, like stated in the tutorial I'm using (see post 1). As of now, the kernel itself is broken and even if the ROM was complete, not even the booting would work. (Well, booting works as far as showing the boot logo (the green FXP one) goes. But the LED notification light for entering recovery doesn't light. Bootloop over and over...)
Many of the lib files intended to be copied from one lib folder to the other are missing on our Nozomis... My question is, what are the consequences...?
My main issue here is that the zip won't flash. The recovery (no matter which I choose) just returns an 'ERROR' and refuses to flash the file...
Another question would be how to repack an .elf kernel into a boot.img. Because now, I'm trying with letting the CM9 kernel in the zip (since it is an .img) and then flash the modified .elf kernel that I repacked with Flashtool. Inefficient, but at least there's a way.
So currently, the priority list would be:
1.Get zip to flash
2.Fix kernel
...Not necessarily in that order. We could fix the kernel first, but there isn't much gain to it if the ROM zip can't even be flashed to test if it truly works...
Click to expand...
Click to collapse
Bro, it may be possible to get Sense on our devices. Even I have been working on getting Sense booted on our device. My status:-
PORTED FROM - HTC ONE X
BASE - FXP 215 CM9
STATUS - Gets past kernel and even loads bootanimation. Fixed many errors in the logcat. Gets stuck at bootanimation and even displays a message saying that System is not responding, would you like to close it.
I couldn't manage to fix any more errors in the logcat so I gave up but you have rekindled my spirit to get Sense booting on out device. I will upload my rom soon along with the logcat.
Cheers,
abcdjdj
Wow, you actually got the thing to boot?
The only question is how did you manage that based off of a tegra CPU? Would be very interested in seeing that...
On a not-so-very related note, your port was of ICS and Sense 4 , correct?
Am I the only one around here that favors old software?
someone755 said:
Wow, you actually got the thing to boot?
The only question is how did you manage that based off of a tegra CPU? Would be very interested in seeing that...
On a not-so-very related note, your port was of ICS and Sense 4 , correct?
Am I the only one around here that favors old software?
Click to expand...
Click to collapse
Not fully booting but I think close to booting. I followed the guide mentioned by you in the OP and one by one eliminated all errors that I could eliminate. I had been working on Sense for around a month during my school holidays but now I am not getting any free time. And yes it is Sense 4 (Android 4.0.4).
Sent from my LT26i using xda app-developers app
But isn't the Tegra3 completely different than our FUJI board?
Especially the graphics, those must be out of control on your ROM...
If I were you, I'd at least take the AT&T version of the HOX.
Oh yeah, I forgot to ask: is it the same if I try and port from a MSM8260 board (the same as the Xperia) and the later S4 Qualcomm versions (used in the Xperia T, AT&T One X etc.)? Because porting from a CDMA phone (HTC Rezound) seems to make the work harder...
Thankfully, my summer holidays have just begun, so I have plenty of free time (that's also the reason I started my project).
P.S.
Yeah, maybe that's exactly what I should do. Ditch the CDMA phone and start with the Snapdragon S4 One X!
I would prefer Sense 3.x, but oh well, at least Sense4 is also Sense
http://www.xda-developers.com/android/sense-4-ported-to-sony-xperia-devices/
I just found this. It's not even that old...
Anyways, I've been thinking if the devs of this would be able to help us.
This development stuff gets boring pretty quick when you do it for the 10th time
@samuel2706, could you give these guys a little hand?
But he's a HTC Dev... Wouldn't we need something more like a nexus or better yet a Xperia developer?
someone755 said:
But he's a HTC Dev... Wouldn't we need something more like a nexus or better yet a Xperia developer?
Click to expand...
Click to collapse
Yes,, maybe, but he also could give a little help. Can't he?
Sent From my LT26i using Tapatalk 4
Contact the guy who did this http://forum.xda-developers.com/showthread.php?t=2184706
Well, I thought I'd make this thread so that devs could help each other to actually work together and create a working Sense ROM. So naturally, all help is welcome from anyone.
Anyways, I'm on my way to finishing yet another try, this time with the AT&T One X. Fingers crossed that it at least makes it to the bootanimation.
EDIT: I see that the easiest way to get Gapps is with including the default /data folder from the original HTC ROM (with vending, youtube etc.). But I have to add that to the updater-script. So, I want to ask, is /dev/block/mmcblk0p14 the data partition on the Nozomi?
What's happening?
samuel2706 said:
What's happening?
Click to expand...
Click to collapse
Hi,
I am porting [or trying to port] Sense 4 from HTC One X to Xperia S. I used FXP 214 CM9 as a base. I followed this guide - http://forum.xda-developers.com/showthread.php?t=2245786
Then I fixed as many errors as I could by checking the logcat and got it till the Bootanimation. But now I need help to get it to boot. So, I have attached the logcat from my latest build.
Thanks for your help,
abcdjdj
Maybe copying a few more files could help. Maybe act like your xperia is a HTC device? http://forum.xda-developers.com/showthread.php?t=1222746
Could be worth a try and play with this copying a bit...
Seems to be failing at dalvik; very strange, it doesn't show any major errors on first glance however I'll take a longer look at when I can, however I can link you to this thread that may help you in the meantime Porting
What about this one? http://forum.xda-developers.com/showthread.php?t=2276871
Nice and automated, but the question is, will it work?
I'm trying it with the HOX, just need to wait for it to copy to the phone...
All this seems like a big race -- who will get it working first? Hyped!
Kinda makes me wish I still had my xperia S I could have given this a real good go at; but instead I have a galaxy s4, so it's going to be mostly logcats and such I can help with, I don't like blind building things; made that mistake before.
A blind build is better than no build. Unless it makes bricks...
Thanks a lot for helping out.
Though I'll never understand how a pro HTC dev can go to Sony and then Samsung. ;P
I just hope THIS time my kernel will boot... Cause if it doesn't ... [censored]...
EDIT: Okay, [censored] is happening... Why can't I make this zip flash? I've done it a million times, but all I get is ERROR... ;-;
unfotunatly, i'm not a dev. but i really like the idea. specially if considering porting htc one sense version to our nozomi. i think it would fit like a glove
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)
I was able to use https://github.com/anestisb/android-prepare-vendor to prepare the vendor images to correctly build AOSP.
I submitted some changes to make it work with Pixel2-XL and they have been merged into main branch.
You have to wipe everything.
I dont know how to make proper zip images for TWRP so use fastboot
I use the fastboot script included in the zip after a full wipe and im all good
Thanks:
anestisb on Github
opengapps
not working:
pixel squeeze
AOSP 8.1 with google apps:
V3:
https://www.androidfilehost.com/?fid=889964283620776051
AOSP 8.1 stock (no gapps):
https://www.androidfilehost.com/?fid=817906626617955840
changelog:
v3:
Jan security update
v2:
updated camera
pixel launcher
updated wallpaper that was causing errors
fixed google setup errors during startup and boot
archive:
v2: https://www.androidfilehost.com/?fid=817906626617955877
V1:
https://www.androidfilehost.com/?fid=745849072291697825
During first boot google setup crashes a bit and I just skip it ...then on reboot I get complaints about stuff. but everything works. so......
deeproot said:
I built AOSP with OpenGapps and all I got was this forum thread
You have to wipe everything.
I dont know how to make proper images so use fastboot
I use the fastboot script included after a full wipe and im all good
Click to expand...
Click to collapse
Link?
Sent from my Pixel 2 XL using Tapatalk
yea, link?
?????
Don't tease us like this, lol. I'll flash anything at this point!
Sent from my Pixel 2 XL using Tapatalk
uplodz complete.
Interesting :good:
I've been doing my best to get my own build running for a few weeks now, and while everything else seems to work perfectly, I can't seem to figure out a way to get it to connect to mobile data. I'd be really interested to hear if there's something in addition to the build instructions provided by Google that you had to do to get it working!
I would just use your build, but my goal is to avoid gapps altogether. Hopefully the trick isn't to have gapps installed
Thanks!
prurigro said:
I've been doing my best to get my own build running for a few weeks now, and while everything else seems to work perfectly, I can't seem to figure out a way to get it to connect to mobile data. I'd be really interested to hear if there's something in addition to the build instructions provided by Google that you had to do to get it working!
I would just use your build, but my goal is to avoid gapps altogether. Hopefully the trick isn't to have gapps installed
Thanks!
Click to expand...
Click to collapse
I thought the whole point of gapps is Google *****es if you build a Rom with google apps installed already...
prurigro said:
I've been doing my best to get my own build running for a few weeks now, and while everything else seems to work perfectly, I can't seem to figure out a way to get it to connect to mobile data. I'd be really interested to hear if there's something in addition to the build instructions provided by Google that you had to do to get it working!
I would just use your build, but my goal is to avoid gapps altogether. Hopefully the trick isn't to have gapps installed
Thanks!
Click to expand...
Click to collapse
u did add in the propietary drivers i assume before u started making ur build?
this build is running smooth! i almost wanna say u couldve left gapps out n let ppl choose which they want to use but of cpurse this is only the beginning.. first thing i did was remove all those google hotword apks that fc, not had any issues yet and u already stated squeeze isnt on here but i nvr used that anyways
I was building from source today but my env has a ways to go before its useable.. it literally took all day to make aosp arm64 eng lol.. started gettin low mem stops towards the end so gonna look at it tom... i actually need to change it up and tweak settings cuz i only got 6gb ram
my set up tho is ur aosp, flash kernel 2.05 and magisk 15.1.. butter.. or shall i say vanilla??
prurigro said:
I've been doing my best to get my own build running for a few weeks now, and while everything else seems to work perfectly, I can't seem to figure out a way to get it to connect to mobile data. I'd be really interested to hear if there's something in addition to the build instructions provided by Google that you had to do to get it working!
I would just use your build, but my goal is to avoid gapps altogether. Hopefully the trick isn't to have gapps installed
Thanks!
Click to expand...
Click to collapse
aosp i dont think includes automatocally.. its runnin android web view n all lol instead of chrome that is
Now, I'm relatively new to the rooting world of Android. Is AOSP essentially custom ROMs? I know this is sort of a "if you don't know, you likely shouldn't be messing with it." I just love tweaking my phone!
So far only the squeeze doesn't work? Should the less advance user hold off until it's been tested a bit? Regardless, thanks for distributing your work to everyone on here! I love this community. Being able to share in the glory that is altering literally almost every aspect of your phone's software.
jgreen077 said:
Now, I'm relatively new to the rooting world of Android. Is AOSP essentially custom ROMs? I know this is sort of a "if you don't know, you likely shouldn't be messing with it." I just love tweaking my phone!
So far only the squeeze doesn't work? Should the less advance user hold off until it's been tested a bit? Regardless, thanks for distributing your work to everyone on here! I love this community. Being able to share in the glory that is altering literally almost every aspect of your phone's software.
Click to expand...
Click to collapse
for u id say hold off.. it works fine for me but it technically is a userdebug build.. AOSP =Android Open Source Project, Its basically Android built from Android source so typically devs can pull the source and make their own roms how they want them. Normally doesnt even have google apps like play store for example.
Its a very clean low lvl android OS and the dev controls every aspect of the build process.. its also been called Vanilla
this technically is "custom" but this initial build doesnt have many tweaks or customizations.. its merely a glimpse as to the possibilities
but hey, try it out if u got the itch, it wont hurt u lol plus the only real way to know the difference is to try it for yourself
jgreen077 said:
Now, I'm relatively new to the rooting world of Android. Is AOSP essentially custom ROMs? I know this is sort of a "if you don't know, you likely shouldn't be messing with it." I just love tweaking my phone!
So far only the squeeze doesn't work? Should the less advance user hold off until it's been tested a bit? Regardless, thanks for distributing your work to everyone on here! I love this community. Being able to share in the glory that is altering literally almost every aspect of your phone's software.
Click to expand...
Click to collapse
for u id say hold off.. it works fine for me but it technically is a userdebug build.. AOSP =Android Open Source Project, Its basically Android built from Android source so typically devs can pull the source and make their own roms how they want them. Normally doesnt even have google apps like play store for example.
Its a very clean low lvl android OS and the dev controls every aspect of the build process.. its also been called Vanilla
this technically is "custom" but this initial build doesnt have many tweaks or customizations.. its merely a glimpse as to the possibilities
but hey, try it out if u got the itch, it wont hurt u lol plus the only real way to know the difference is to try it for yourself
elliwigy said:
for u id say hold off.. it works fine for me but it technically is a userdebug build.. AOSP =Android Open Source Project, Its basically Android built from Android source so typically devs can pull the source and make their own roms how they want them. Normally doesnt even have google apps like play store for example.
Its a very clean low lvl android OS and the dev controls every aspect of the build process.. its also been called Vanilla
this technically is "custom" but this initial build doesnt have many tweaks or customizations.. its merely a glimpse as to the possibilities
but hey, try it out if u got the itch, it wont hurt u lol plus the only real way to know the difference is to try it for yourself
Click to expand...
Click to collapse
Honestly, I'd normally listen and hold off. But since I have a day off I think I'm gonna attempt it just for the sake of learning!
As long as it has the Play Store so I can download the apps I want, I'm good. If I can get all the apps I need to than I'll be a happy camper.
Say later on it's decided I want to go to another AOSP rom, am I going to have to wipe again? If I can get all my apps, won't have to wipe my device every other week, and can get my modules installed I should be good to do some good old fashioned experimentation.
I am not a smart man, at times. I'm gonna try it out. I have a few hours before anyone else is awake. Might as well use that time (un)wisely.
Plus I believe these "vanilla" ROMs, being what they are, can be modded to an even greater extent than the already pretty modifiable "stock" Pixel ones. Please correct me if I'm wrong.
prurigro said:
I've been doing my best to get my own build running for a few weeks now, and while everything else seems to work perfectly, I can't seem to figure out a way to get it to connect to mobile data. I'd be really interested to hear if there's something in addition to the build instructions provided by Google that you had to do to get it working!
I would just use your build, but my goal is to avoid gapps altogether. Hopefully the trick isn't to have gapps installed
Thanks!
Click to expand...
Click to collapse
I found this:
https://github.com/anestisb/android-prepare-vendor
I submitted my changes and they will update in a few days to the add tamien support.
I am going to hold off on this for now, as it's just a shell of what custom Android can be but just wanted to say thank you very much for getting the ball rolling. For giving us hope haha. I check the thread at least 4 times a day and my heart jumped when I saw this post! Good work!
Nice can we flash the Kernels that have been around here for a while on this rom?
patt2k said:
Nice can we flash the Kernels that have been around here for a while on this rom?
Click to expand...
Click to collapse
I flashed Elemental X and finger print stopped working.
deeproot said:
I found this:
https://github.com/anestisb/android-prepare-vendor
I submitted my changes and they will update in a few days to the add tamien support.
Click to expand...
Click to collapse
@deeproot
have you uploaded your WIP android_prepare_vendor anywhere? I would like to clone your changed repo and run this script if possible.
I attempted to manually add your changes in the pull request, but the script is breaking with a debugfs error
Thanks,
Edit: Found it, still getting same debugfs error.
Code:
[*] Extracting '/tmp/android_prepare_vendor.jlQiR6/taimen/opm1.171019.011/taimen-opm1.171019.011-factory-2df1c1cb.zip'
[*] Unzipping 'image-taimen-opm1.171019.011.zip'
[-] Symlinks have not been properly processed from /tmp/android_img_extract.FRWAOM/taimen-opm1.171019.011-factory-2df1c1cb/images/vendor.img.raw
[!] If you don't have a compatible debugfs version, modify 'execute-all.sh' to disable 'USE_DEBUGFS' flag
[-] Factory images data extract failed
[email protected] ~/Desktop/android-prepare-vendor $