Related
just to make sure... If i want a theme- put it on sd card, rename it to update, apply update, and reboot??? It doesn't work for me. It stays stuck on the G1 screen. Does it have something to do with rom i'm using: update-cm-4.1.9.2-signed???
Just in case... Yes its rooted, I've even tried other HERO ROMS(and i have successfull), but 4 some reason I don't know how to apply a theme. And YES!! I'm a n00b.
Thanx in advance
yes your process is correct, BUT you have to make sure the theme you apply is matched with your rom. if you have cm 4.1.9.2 rom, you have to make sure you get the 4.1.9.2 compataible theme. also some themes may take up to 10 minutes to fully boot up.
-insert flame here-
the theme must be compatible with the rom like for 4.1.9.2 the theme has to be based off of the 4.1.9.2 theme template. the same goes for any rom and theme. as long as they are compatible then there shouldn't be any problems. if you want a bigger choice of themes then the stable roms are better.
but yeah, check to see if your theme is compatible with 4.1.9.2, if it isn't then that is the problem.
also you have the process correct.
This should really be in the Q&A section, it seems you haven't really read much of what themes are about. You can only flash themes made SPECIFICALLY for the rom you are running (In your case cm 4.1.9.2) Since I don't see too many themes around made for that rom, I'll assume you're flashing a theme not made for the rom this will cause the G1 screen loop.
To get back to your old system, just flash the rom OR the theme template again and you should be good to go. Next time match the theme versions with rom versions before you go flashing.
Dfanzz said:
just to make sure... If i want a theme- put it on sd card, rename it to update, apply update, and reboot??? It doesn't work for me. It stays stuck on the G1 screen. Does it have something to do with rom i'm using: update-cm-4.1.9.2-signed???
Just in case... Yes its rooted, I've even tried other HERO ROMS(and i have successfull), but 4 some reason I don't know how to apply a theme. And YES!! I'm a n00b.
Thanx in advance
Click to expand...
Click to collapse
First, even though your question is about a THEME, it's still a question and should go in the Q&A section.
In response, your theme MUST be compatible with your rom. So if the theme you are trying is not CM 4.1.9.2 compatible, then you COULD get problems.
EDIT: DAMN, did it really take me so long that 4 people answered before I did? geez lol
Fast guns around here, I think he gets the point though :]
slow pokes =)
Just to clarify to further help you understand, a theme is composed of many of the same files as the original ROM. However, this time around they have been modified to look like what you see as the theme. Therefore, when you install a theme, you are actually replacing those files with the ones with different looks. That is why you need to make sure your theme is made for the ROM, because different programs and files, chances are, will not work and will result in a bootloop.
is there a way to take a .zip file that someone has posted, and cook it into the rom i'm building? its the droid x keyboard (themed). I took a look at the contents of the .zip and I'm not sure if I can just manually place the files or what? for instance in the system folder there is app/apk and lib/lib file. can i just take the apk and put it in /system/app and the lib file into /system/lib? and if so... what happens with the META-INF folder thats in there? and help is greatly appreciated!!
ok, you are trying to make a rom while you dont even know the components of a flashable zip???
in order to make the rom WORK, you will need to write about 275 lines of code (update-script), and thats just for amon-ra recovery (amend scripting). then, you also got edify scripting, which will be the norm soon. you will also need a 280 line edify script (updater-script) AND an edify binary coding page (update-binary). roms are not easy...
i would rethink making a rom, no offense meant.
thanks for you 2 cents. however irrelevant it may be. I'm not looking to write any code, either there is an easy way to place the .zip files in the rom or there isn't, in which case i will continue to flash through cwm
as cooking your own rom, do you mean releasing it publicly? if you mean just for yourself, then this might be a bit easier.
hell no man, i'm not nearly smart enough to release a public rom. i found the htc kitchen the other night and a stock rom download that i have been playing with, trying to tweak it to my liking, last thing needed is this keyboard to boot without a separate flash!
so thats where the confusion is coming from.
open up the META-INF/com/google/android/update-script file in the zip with a text editor. tell me what it says.
show_progress 0.1 0
copy_dir PACKAGE:system SYSTEM:
show_progress 0.1 10
ok no symlinks ur safe. just copy the files into the directorys they are in in the zip. for example, keyboard.apk in /system/app/ would be put in /system/app/ on the rom. ignore the META-INF folder that is for the sigs and scripts.
sorry about my first post i assumed you meant to release a rom and were a bit over your head. hah there arent many skilled enough to make roms. thats why we are all here.
thanks buddy... i appreciate your help!
no problem... if you like the droid x kb you might want to check out the gingerbread one as well. thats nice too. i'm a swype guy tho.
I really like the gingerbread kb, I just got my evo yesterday, but I had the ginger kb on my epic. I just havent found my way around all the evo forums and found all the hidden gems yet lol. I assumed they had a port for the evo but wasn't too sure
wow just yesterday and you are already messing with the roms... i wonder where you will be in a month or two.
lol i had a hero for a long time... from what I'm seeing so far they aren't too much different in reguards to where things are. I guess only time will tell, but probably not for i don't know **** about code. Best I can do is delete and add some apk's and png's!
hah ok i assume you are rooted already? that must be hell coming from the hero.
yes I already have root and cwm installed. That was the first thing I did when I got home yesterday =)
ok. as a suggestion i would try out myns warm twopointtwo and caulkins EViO 2 (i kno sense, but i like them both) and i am hearing fantastic things about miui. i'll try that one tomorrow.
welcome to the evo crew.
yeah i read some good things about miui also. i like mikfroyo. but i haven't updated to .4 yet. I have been busy playin with stock and seeing what i can do with that kitchen. just flashed an update and that kb installed perfectly... thank you
hah no problem. i'm going to bed now so 'night and happy MLK day
Is your device changing its orientation to landscape way too quick?
If the answer is yes, read up, here is the solution.
I hate Froyo autorotation on Galaxy S.
It turns into landscape way too quick, even when I'm picking the device from the table.
Since there was no reaction from Samsung, I decided to fix this for them.
This involves decompiling framework.jar file, editing file:
Code:
android\view\WindowOrientationListener$SensorEventListenerImpl.smali
I attached a modified file. I dont exactly know what changes there are, I modified some values at random
For devs:
To be more serious, I decompiled SGS JS3 framework.jar and replaced WindowOrientationListener$SensorEventListenerImpl.smali from DesireHD's eViL-NXSense-HD-v.1.1_BETA (random pick). Having the right implementation of sensor listener i started to tweak it, changing some values.
If you want to tweak it further to your needs, focus on MAX_TRANSITION_TILT, MAX_TILT, PARTIAL_TILT constants.
(forgot to add) For a full reference: http://hi-android.info/src/android/view/WindowOrientationListener.java.html
Three files are attached to this post:
[rotation-fix]modified_JSX-CWM.zip - clockworkmod packages with fixed framework.jar, this is what an user needs
First boot after the update may take up to 5 minutes!
I do seem to have random errors due to firmware fragmentation. If you are a regular user and want this fix, you should rather ask your ROM developer for implementing it in his ROM, because at current state I cant guarantee if its compatible with ANY custom configuration.
auto_rotation_devs.7z original and recompiled framework.jar files form JS3/5 as well as original and patched smali.
//edit: lol accidently voted for front page Just a blind click sorry
On a second thought this might be interesting for more than SGS people, so maybe accident was not so bad.
let me try
not working for me
You mean? Bootloop/no changes?
I need some feedback;
Is this working for you?
Do you like it?
It might be slipstreamed into all current ROMS, you just need to encourage ROM developers to do so
xan said:
You mean? Bootloop/no changes?
I need some feedback;
Is this working for you?
Do you like it?
It might be slipstreamed into all current ROMS, you just need to encourage ROM developers to do so
Click to expand...
Click to collapse
it didnt work at all nothing has change
Sec gotta check update.zip
Was ina hurry yesterday.
Ok the update.zip was borked, replacing.
Hi xan. Good stuff, definitely an improvement over the factory settings.
Thanks for this. Flashing via CWM went flawless.
thanks, I appreciate your feedback
Same fix but on JS5
Hello.
Is there any chance to do same but on the JS5 framework?.
Thanks.
Sure, will upload patched JS5 framework in few hours.
xan said:
Sure, will upload patched JS5 framework in few hours.
Click to expand...
Click to collapse
Thanks, that will be great, because i hate too the auto rotation on froyo and this is what i was looking for.
great work
it a little more quickly,
Unfortunately, not as fancy-rotation
keep it up
It doesn't function at my SGS
Now my rotation doesn't work at all...
Try harder ;p
JS5 version up.
How about a revert back zip if something goes wrong?
I am on JS3, so I should use auto_rotation-FIX-CWM.zip or auto_rotation-FIX-JS5-CWM.zip
Thanks, Froyo's autorotation is pain in the ass.
Look forward to your answer.
Thanks.
Both should work, according to my tests. auto_rotation-FIX-CWM.zip or auto_rotation-FIX-JS5-CWM.zip
If you are familiar with adb, just adb pull /system/framework/framework.jar
I doubt it wont work.. Anyway will look into it.
Is it working on JPY too ?
99% its not.
does it work ok for js5....??? can i restore the previous WITH the original...???
ok, I tried your fix, works fine, but one thing, and that is that mine volulme controls are absolutely messed up :-D
for example, when I click on a side to increase/decrease ringer volume, it says Playing via Bluetooth instead of Ringer Volume, or instead of Media Volume it says Silent Ringtone, etc...
It's quite messed up, I saved my framework.jar before flashing so I am back on my original.
I have JS3 ROM Darky's 9.2.
Any idea what could be the problem?
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