Database Develop

[REQ] Virtuous "Primadonna"

How hard would it be to port this to the Vivid after obtaining permission from the devs? I see Inquisition has been ported over and is looking quite good.
I know Sense 4 is causing issues but is this the only difficult problem to overcome? Or the RIL? Or are these combined?
Sent from my HTC Vivid

slapdaddy said:
How hard would it be to port this to the Vivid after obtaining permission from the devs? I see Inquisition has been ported over and is looking quite good.
I know Sense 4 is causing issues but is this the only difficult problem to overcome? Or the RIL? Or are these combined?
Sent from my HTC Vivid
Click to expand...
Click to collapse
Once we get a working AOSP base, porting will be more easy.

Brand New said:
Once we get a working AOSP base, porting will be more easy.
Click to expand...
Click to collapse
I'm not so sure that's going to affect anything, since Sensation ports are already being handled with relative ease due to the Sense-based ROM -> Sense-based ROM idea. AOSP will help to port completely diverse images like CM9 and AOKP,

It has been mentioned before the sense 4 works perfectly except for ril. Asop will not help advance this since the framework is completely different. Our ril needs to be manual programmed into the smali code in framework.
Sent from my HTC PH39100 using xda premium

RUU HTC Sense ICS (HTC Wildfire C)

THIS IS ONLY FOR DEVELOPERS. DO NOT ATTEMPT TO FLASH THIS AT ALL. YOU HAVE BEEN SEVERELY WARNED.
Device specs: http://www.phonearena.com/phones/HTC...7037/fullspecs
Enjoy
RUU_GOLF_U_ICS_40A_HTC_Europe_1.35.401.1_Radio_10. 08.98.09H_1.05.98.08M2_release_260338_signed.exe
RUU_GOLF_U_ICS_40A_HTC_Europe_1.45.401.1_Radio_10. 08.98.09H_1.05.98.11M3_release_262024_signed.exe
thanks to jmztaylor
http://forum.xda-developers.com/show....php?t=1658056
Hello developers will be possible that our Sense HTC Wildfire may have ICS?

Porting sense 4 from the original desire C ruu: Not possible
Porting it from other ARMv6 devices: Possible.
I know the hero and WFS have both got it booting. So if you want to investigate into porting it. Go ahead.

I think that the phone name is desire c.... However our best bet is to wait for a port to an arm6 device (there is a work in progress in wildfire s forum) because desire c is arm7 and a port would be very difficult..

elia222 said:
I think that the phone name is desire c.... However our best bet is to wait for a port to an arm6 device (there is a work in progress in wildfire s forum) because desire c is arm7 and a port would be very difficult..
Click to expand...
Click to collapse
I think it was going to be called the Wildfire C, but then HTC renamed it to the Desire C. To make it seem like a premium device on a budget. (I guess). The WFS thread is a mess of flaming and trolling, and its been closed. So any updates won't be going on there. Although, someone managed to shrink the RUU down enough to fit the WFS partition sizes.

http://www.xatakandroid.com/moviles-android/htc-golf-asi-sera-el-sucesor-de-la-gama-wildfire

it is impossible, haha

tathanhlam66 said:
it is impossible, haha
Click to expand...
Click to collapse
Nothing is impossible, that's how we've got sense 2.1, sense 3.5, gingerbread and ICS on our phone. Once it gets ported to another ARMv6 device, we can work from there.
Sent from my HTC Wildfire using xda premium

somebody check it ruu?

Hi all,
The thread was locked indeed but we are now discussing the ROM on the leaked ruu thread. We have it booting to boot animation however audio/power is causing dalvik to fail, and causes a bootloop.
You could always look at our github to see what we have changed/added/improved/fixed. We will be doing this for the marvel (Wildfire S) and as soon as it boots we will inform you asap.
We are looking for a bit of help so if you see something obvious that we have missed then send us a pull request over github.
Sent from my HTC Wildfire S A510e using xda premium

how we can run this without a kernel 3?
someone should port drivers or create them
and this phone is too old,i think noone will do something like this
it s too difficult
just think this: desire s has a kernel 3 and sense 4 is working fine,but it has A LOT OF problems(crash,freeze,semi-functionl things)
i don t think our phone can support it with sense,we at least should have a fully working cm9 first
i think

benjamingwynn said:
Hi all,
The thread was locked indeed but we are now discussing the ROM on the leaked ruu thread. We have it booting to boot animation however audio/power is causing dalvik to fail, and causes a bootloop.
You could always look at our github to see what we have changed/added/improved/fixed. We will be doing this for the marvel (Wildfire S) and as soon as it boots we will inform you asap.
We are looking for a bit of help so if you see something obvious that we have missed then send us a pull request over github.
Sent from my HTC Wildfire S A510e using xda premium
Click to expand...
Click to collapse
I've been following the thread in the WFS dev section. Will replacing libs from sense 4.0 with CM9/AOSP Libs solve any issues. Or have you already tried that? Could it be a conflict between Beats Audio and the power management driver? Would you have to sacrifice beats to get it working?

Justice™ said:
I've been following the thread in the WFS dev section. Will replacing libs from sense 4.0 with CM9/AOSP Libs solve any issues. Or have you already tried that? Could it be a conflict between Beats Audio and the power management driver? Would you have to sacrifice beats to get it working?
Click to expand...
Click to collapse
Yeah we have replaced the libs, and yes we may have to sacrifice beats audio, although we could also used modified beats libs that were ported to AOSP, but i'm not sure that would integrate it with the onboard beats on/off system :/

Even if we were able to make this possible for our device, it would be unbearably laggy and slow. In my opinion its not worth doing it although its not bad trying. My opinion

rayven18 said:
Even if we were able to make this possible for our device, it would be unbearably laggy and slow. In my opinion its not worth doing it although its not bad trying. My opinion
Click to expand...
Click to collapse
It depends. While ICS can suffer from some slowdown on our device (Atleast at stock clockspeed). It is still usable and can still perform well. As we've seen with Sense 2.1 Gingerbread on the wildfire. It is very fast. And I mean, as fast as stock froyo sense. Which is nothing like CM7 is. So maybe Sense 4 will be even fast and optimized?

Sense 2.1 is not fully working
And ics need a kernel 3
And we don t have enought ram to run this

so it work or don't work?

kylon said:
Sense 2.1 is not fully working
And ics need a kernel 3
And we don t have enought ram to run this
Click to expand...
Click to collapse
You don't need a 3.x kernel to run ICS at all.

benjamingwynn said:
You don't need a 3.x kernel to run ICS at all.
Click to expand...
Click to collapse
you need it for fully working camera,wifi tether,hotspot,bluethoot and stability
anyway as i said we need more ram,wildfire c has at least 450 mb aviable

kylon said:
you need it for fully working camera,wifi tether,hotspot,bluethoot and stability
anyway as i said we need more ram,wildfire c has at least 450 mb aviable
Click to expand...
Click to collapse
Well. Clearly we don't. Because we have ICS with Camera, Bluetooth, WiFi-Tethering working on a 2.6 kernel. Besides, we can use MTD partitions if we don't have enough for the rom. Because we have 512mb of rom. So we can allocate that with MTD partitions.

kylon said:
you need it for fully working camera,wifi tether,hotspot,bluethoot and stability
anyway as i said we need more ram,wildfire c has at least 450 mb aviable
Click to expand...
Click to collapse
Agreed with Justice, the kernel is NOT the issue here, it's simply getting the correct patches to interface the software with the older chipset and HAL, or so I think?

No CM9/10 for IncS?

I haven´t found any info around the web about CM team making a vivo release? Does anybody have information about that?

weaselEST said:
I haven´t found any info around the web about CM team making a vivo release? Does anybody have information about that?
Click to expand...
Click to collapse
The CM team tend to not discuss a lot of what they will release untill it is due soon. Guess it's to stop people nagging about deadlines.

They are probably waiting for the source code and kernel.

acme anvil said:
They are probably waiting for the source code and kernel.
Click to expand...
Click to collapse
Source code for HTC ROM? Or what?

weaselEST said:
Source code for HTC ROM? Or what?
Click to expand...
Click to collapse
They are waiting for the source code for kernel 3.0.16. Currently, it only works for Sense ROM's and not AOSP ROM's. AOSP for our device uses 2.6.x GB kernel hacked to work with ICS which is why our ROM's aren't fully stable yet unless your using the stock 3.0 kernel.
I emailed HTC regarding kernel sources and was told they will release it 90-120 days after the release of the WWE ICS RUU. The RUU was released a few weeks ago, so a few months to go unfortunately.

ZaySk said:
They are waiting for the source code for kernel 3.0.16. Currently, it only works for Sense ROM's and not AOSP ROM's. AOSP for our device uses 2.6.x GB kernel hacked to work with ICS which is why our ROM's aren't fully stable yet unless your using the stock 3.0 kernel.
I emailed HTC regarding kernel sources and was told they will release it 90-120 days after the release of the WWE ICS RUU. The RUU was released a few weeks ago, so a few months to go unfortunately.
Click to expand...
Click to collapse
exacly
s*ck but we must waiting
check ice cold sandwich
4 me best ics rom
5!

Just curious, what is the difference between AOSP kernel and Sense kernel in general? If I got the source for the Sense kernel, what do I need to do to make it work for AOSP?

itandy said:
Just curious, what is the difference between AOSP kernel and Sense kernel in general? If I got the source for the Sense kernel, what do I need to do to make it work for AOSP?
Click to expand...
Click to collapse
do you have the source ;o !
and you would need to build a aosp kernal based on the sense source

naathaanb96 said:
do you have the source ;o !
and you would need to build a aosp kernal based on the sense source
Click to expand...
Click to collapse
Just don't get so excited. It's just a big IF. ,-)
What do you meaning building an AOSP kernel based on the Sense kernel? I previously compiled some AOSP kernels from source but dunno about porting Sense kernel to AOSP.
Sent from my Incredible S using Tapatalk 2

itandy said:
Just don't get so excited. It's just a big IF. ,-)
What do you meaning building an AOSP kernel based on the Sense kernel? I previously compiled some AOSP kernels from source but dunno about porting Sense kernel to AOSP.
Sent from my Incredible S using Tapatalk 2
Click to expand...
Click to collapse
i think you need to compile a AOSP kernal from the sense kernal source. id private message kaijura or lord clokan or nik, being developers they would be able to tell you more do you know someone who is a htc dev or something ?

naathaanb96 said:
i think you need to compile a AOSP kernal from the sense kernal source. id private message kaijura or lord clokan or nik, being developers they would be able to tell you more do you know someone who is a htc dev or something ?
Click to expand...
Click to collapse
I wish I do but I don't
Sent from my Incredible S using Tapatalk 2

Now as the source code is available, we can hope for stable ICS rom.

Well ICS is already kind of stable just some minor bugs if you mean that. However JB would very likely be possible imo.

Our devs are working on it and I'm sure CM10 will be on our device Nik just got a port from DHD ROM booting and will release it tomorrow Also Floatshow and djpbx are building a JB ROM from source and I guess they're making awesome progress, too. So it's just about time, mate

Nice to see that my old thread has been awaken
Waiting from CM10 now.

Just a matter of time. Gonna be a fun few weeks
Sent from my HTC Incredible S

Nik got it booting!
Sent from my HTC Incredible S using xda premium

Nik released his JB rom stating he uses CM10 kernel. I understand that kernel is phone specific and does that mean we well see a CM10 alpha build really soon?

weaselEST said:
Nik released his JB rom stating he uses CM10 kernel. I understand that kernel is phone specific and does that mean we well see a CM10 alpha build really soon?
Click to expand...
Click to collapse
It doesn't surely mean that but it's possible

What about CM9. will we get it?
Sent from my Incredible S using Tapatalk 2

3.0 Kernel for AOSP JB?

I've been using Codename ever since it came out but I got tired of the problems related to the Kernel and switched to ProjectX. I and I'm sure others really want to use a smooth and working JB ROM.
Is there anyone working on the 3.0 Kernel for our device? I know Nik said he contacted someone to help us out but there's been no news on that front yet.
If anyone knows how to modify Kernels, Adi_pat gave some tips here -
http://forum.xda-developers.com/showthread.php?p=33291894
He'll probably help us out if we make some progress in booting up Codename with it at least

TheDareDevil said:
I've been using Codename ever since it came out but I got tired of the problems related to the Kernel and switched to ProjectX. I and I'm sure others really want to use a smooth and working JB ROM.
Is there anyone working on the 3.0 Kernel for our device? I know Nik said he contacted someone to help us out but there's been no news on that front yet.
If anyone knows how to modify Kernels, Adi_pat gave some tips here - http://forum.xda-developers.com/showthread.php?t=1899335&page=38
He'll probably help us out if we make some progress in booting up Codename with it at least
Click to expand...
Click to collapse
Upon the exit of JB roms ago, were used GB modified kernel, now with source code maybe will be possible to compile a fully working kernel, but afaik there are no 3.x kernel for JB, maybe someone is working out of xda on irc channel but don't known..
Sadly I do not have much competence, plus I don't have the phone it's to repair....

There is kernel 3 for incredible 2 and desire s..may be someone can port it..
Sent from my HTC Incredible S using xda app-developers app

I might be crazy, but I remember reading a post not too long ago about a dev that was writing the 3.0 kernel from source for our phones. I haven't heard an update since then, but I remember hearing it was someone with relation to the cm9 team. It sounded promising, but that development was very slow.
Sent from my HTC Incredible S using xda app-developers app

TheMegosh said:
I might be crazy, but I remember reading a post not too long ago about a dev that was writing the 3.0 kernel from source for our phones. I haven't heard an update since then, but I remember hearing it was someone with relation to the cm9 team. It sounded promising, but that development was very slow.
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
Off the top of my head I seem to recall Noverbose saying he was trying to write a 3.0 Kernel. I also remember at least one other person mentioning something similar to, so there are people working on this. From what I understand it's not easy - I doubt we'll see anything this side of Christmas tbh. I hadn't realised that the Inc 2 and DS had a 3.0 Kernel though. Anyone know if they are actually a made from source version, rather than the same hacked version that we have in Codename, for example?

Well tbh honest a working GB kernel would do too.
Like the front camera and chrome and screen flickering etc.
Damn I wish kaijura was here
Sent from my HTC Incredible S using xda app-developers app

CyanideJack said:
Off the top of my head I seem to recall Noverbose saying he was trying to write a 3.0 Kernel. I also remember at least one other person mentioning something similar to, so there are people working on this. From what I understand it's not easy - I doubt we'll see anything this side of Christmas tbh. I hadn't realised that the Inc 2 and DS had a 3.0 Kernel though. Anyone know if they are actually a made from source version, rather than the same hacked version that we have in Codename, for example?
Click to expand...
Click to collapse
Yes those 3.0 kernels are compiled from source. I checked out AOSP ROM threads in the Desire S and Inc 2 section that had 3.0 kernel, then looked up the creator of the ROM on github and found the sources. I was going to try tackle the 3.0 kernel to get a hang of the make system before building CM9, but I don't have enough monthly data left to download the kernel toolchain! Nov 1st is close, so I can get to work soon! :highfive:
The best way to build an AOSP 3.0 kernel for our device would probably be to look at the source code for 3.0 kernels on our sister devices, and figure it out from there.

ZaySk said:
Yes those 3.0 kernels are compiled from source. I checked out AOSP ROM threads in the Desire S and Inc 2 section that had 3.0 kernel, then looked up the creator of the ROM on github and found the sources. I was going to try tackle the 3.0 kernel to get a hang of the make system before building CM9, but I don't have enough monthly data left to download the kernel toolchain! Nov 1st is close, so I can get to work soon! :highfive:
The best way to build an AOSP 3.0 kernel for our device would probably be to look at the source code for 3.0 kernels on our sister devices, and figure it out from there.
Click to expand...
Click to collapse
Well holy crap, dude, get on that! Seriously though, getting a working 3.0 kernel for our device would go a long way to making JB a usable ROM for our device. Would it be possible to port JellyTime or a similar JB ROM to our device as well?

The source doesn't need changing, it is the ramdisk that is the problem. I have been trying to get help, but so far no luck, adi_pat said he would take a look, but it is hard for me to test as I no longer have an inc s

CyanideJack said:
Well holy crap, dude, get on that! Seriously though, getting a working 3.0 kernel for our device would go a long way to making JB a usable ROM for our device. Would it be possible to port JellyTime or a similar JB ROM to our device as well?
Click to expand...
Click to collapse
I'm gonna worry mainly about compiling CM9 from source once November hits, that's gonna take up the majority of my time. After I get the first release of CM9 out, I'll start work on a 3.0 kernel if it hasn't been done yet. I have no experience whatsoever dealing with kernels though, except for small ramdisk edits, so don't expect any miracles.
It should be possible to port other JB ROM's over using one of nik's ported JB ROM's as a base and reference point, the only problem is I don't know exactly what files I have to substitute to port a ROM. I've PM'd nik about that a few hours ago, so hopefully I'll get some more information on the subject. Nik has been a big help to my dev efforts as a whole.
l0st.prophet said:
The source doesn't need changing, it is the ramdisk that is the problem. I have been trying to get help, but so far no luck, adi_pat said he would take a look, but it is hard for me to test as I no longer have an inc s
Click to expand...
Click to collapse
Interesting, if it's only the ramdisk that needs changing, couldn't you look at the ramdisk from one of niks JB ROM's? Or is it not as simple as that? I'm assuming the latter, seeing as if it were that obvious I'm sure someone would've done it by now. If you ever need help testing, send me a PM I'd be more than willing to test for you.

ZaySk said:
I'm gonna worry mainly about compiling CM9 from source once November hits, that's gonna take up the majority of my time. After I get the first release of CM9 out, I'll start work on a 3.0 kernel if it hasn't been done yet. I have no experience whatsoever dealing with kernels though, except for small ramdisk edits, so don't expect any miracles.
It should be possible to port other JB ROM's over using one of nik's ported JB ROM's as a base and reference point, the only problem is I don't know exactly what files I have to substitute to port a ROM. I've PM'd nik about that a few hours ago, so hopefully I'll get some more information on the subject. Nik has been a big help to my dev efforts as a whole.
Interesting, if it's only the ramdisk that needs changing, couldn't you look at the ramdisk from one of niks JB ROM's? Or is it not as simple as that? I'm assuming the latter, seeing as if it were that obvious I'm sure someone would've done it by now. If you ever need help testing, send me a PM I'd be more than willing to test for you.
Click to expand...
Click to collapse
About using one of Nik's JB roms as a reference
What I understood was that the rom has been built around the old 2.6.x kernel and has to be modified again to work with the 3.0.x kernel, if you guys get one up and running. If that is the case, wouldn't you be going down the wrong path if you model it around nik's existing 2.6.x roms?
We need kaijura here, he was our AOSP kernel master. Hopefully he is doing ok, and has found something else other than xda because he hasn't been online for months. At least other devs, like lordclokan and kali- have moved on and are active with other devices... kaijura hasn't been on at all. Anyone been in contact with him/her?

markj338 said:
About using one of Nik's JB roms as a reference
What I understood was that the rom has been built around the old 2.6.x kernel and has to be modified again to work with the 3.0.x kernel, if you guys get one up and running. If that is the case, wouldn't you be going down the wrong path if you model it around nik's existing 2.6.x roms?
We need kaijura here, he was our AOSP kernel master. Hopefully he is doing ok, and has found something else other than xda because he hasn't been online for months. At least other devs, like lordclokan and kali- have moved on and are active with other devices... kaijura hasn't been on at all. Anyone been in contact with him/her?
Click to expand...
Click to collapse
I know, it would be going down a pretty redundant path. If I was able to port over a JB ROM using nik's ROM's as a base, then my ported ROM would inherit all the same bugs nik's ROM's already have.
I wish kaijura was still around, I have so many questions I want to ask about compiling from source! Luckily lordclokan was a massive help to me in that regard. Kaijura's github hasn't seen action in months either, sadly.

Forgive my ignorance, but isn't the Desire HD essentially our device with a bigger screen and less memory? That being the case, could we not just port across one of the 3.0 Kernels from that?

The problem with the ramdisk that come with the official ROM's that have 3.0 kernels, is that they are built for the sense framework and don't work on AOSP ROM's. The ram disk that is included with Nik's JB ROM's is heavily modified to run a GB kernel with ICS / JB sources, so the problem is I don't have a base to work from, I am basically trying to merge the two init's to make the 3.0 kernel boot.
Saying that we need to port 3.0 kernel is probably a bit misleading, and for that I apologise, the kernel itself has very little Sense specific stuff, it's the ramdisk that is responsible for launching the kernel that is the issue here at the moment.

The only problem with the desire HD kernel would be that our front camera would not work
+ I forgot to link to adi_pat's post - http://forum.xda-developers.com/showthread.php?p=33291894
Sent from my HTC Incredible S using xda app-developers app

l0st.prophet said:
The problem with the ramdisk that come with the official ROM's that have 3.0 kernels, is that they are built for the sense framework and don't work on AOSP ROM's. The ram disk that is included with Nik's JB ROM's is heavily modified to run a GB kernel with ICS / JB sources, so the problem is I don't have a base to work from, I am basically trying to merge the two init's to make the 3.0 kernel boot.
Saying that we need to port 3.0 kernel is probably a bit misleading, and for that I apologise, the kernel itself has very little Sense specific stuff, it's the ramdisk that is responsible for launching the kernel that is the issue here at the moment.
Click to expand...
Click to collapse
Well you can prolly get ideas from adi ( he posted http://forum.xda-developers.com/showpost.php?p=33302707&postcount=387 not sure if you saw it) he seems to know what's up.

TheDareDevil said:
The only problem with the desire HD kernel would be that our front camera would not work
+ I forgot to link to adi_pat's post - http://forum.xda-developers.com/showthread.php?p=33291894
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
So it looks like the furthest things got regarding a 3.0 Kernel was;
Adi_Pat said:
chan
Ok so 2.6.35 works with Jellybean. Why not pack the ramdisk with zImage compiled from 3.0.y sources(Considering you are using standard boot.img format[?]) Because to get it to boot, you would not require any hacks/changes to source, editing ramdisk(init.rc) is enough to make it boot initally.
EDIT: You may also need to change init binary.
Click to expand...
Click to collapse

l0st.prophet said:
The problem with the ramdisk that come with the official ROM's that have 3.0 kernels, is that they are built for the sense framework and don't work on AOSP ROM's. The ram disk that is included with Nik's JB ROM's is heavily modified to run a GB kernel with ICS / JB sources, so the problem is I don't have a base to work from, I am basically trying to merge the two init's to make the 3.0 kernel boot.
Saying that we need to port 3.0 kernel is probably a bit misleading, and for that I apologise, the kernel itself has very little Sense specific stuff, it's the ramdisk that is responsible for launching the kernel that is the issue here at the moment.
Click to expand...
Click to collapse
Very interesting, thanks for the informative post. :good:

zaysk said:
very interesting, thanks for the informative post. :good:
Click to expand...
Click to collapse
happy november!!!

markj338 said:
happy november!!!
Click to expand...
Click to collapse
A very happy November indeed

[Q] MIUI V6?

Is anyone working on or is it even possible to try and port MIUI v6 to the m7spr at this moment?

jasonroberts92 said:
Is anyone working on or is it even possible to try and port MIUI v6 to the m7spr at this moment?
Click to expand...
Click to collapse
So far, there aren't any V6 releases that I can get my hands on (only one I had access to at one point was a very early beta...I think like the first one, and if I remember right, it was for the Nexus 5 or 7...can't remember). I doubt anyone with access to their betas will share, as it's a sure fire way to get yourself banned from beta testing.
Right now, I'm focusing on some theme stuff I'm doing for Sense 6, but once I'm done with that, I'm going to work on porting an AOSP based 4.4.2 V5 to the m7.

That's awesome news hopefully that would resolve the camera prob I have been having with miui based on 4.2.2
Sent from my HTCONE using Tapatalk

nwo122383 said:
That's awesome news hopefully that would resolve the camera prob I have been having with miui based on 4.2.2
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Yea awesome indeed! Been having the camera issue too. Hope he had good fortune with that project