Related
Hello everyone
I noticed that Desire C was introduced.
It's hardware looks very similar to our old Hero.
I'm curious, would it be possible to port ICS + Sense. Not sure about the ARM (6 or 7?)on the Desire, I remember that this caused problems in the past.
What do You guys think ?
Cheers!
brat.haneq
I think that it's not possible. We have from where to port ICS - Eris, HeroC.
But why did you do a thread in Development Area?
Hi there
Yeah, it should be general or qa section, I was so hyped by the possibility of port, that I posted without thinking.
Sorry about that, can someone move this thread to aproptiate section?
Cheers
Brat.haneq
Sent from my Hero using XDA
I don't agree, I think this could be possible for many reasons. But what I can say is that if the devs of the Samsung galaxy ace are capable of porting sense 4 to their device, I see no reason ( except ram) that could make us think that the port is impossible
To finish, many people say that ics is in a way lighter than gb, in general. So there is only a sense port remaining.
But as the specs are quite similar...why would it be impossible?
Sent from my HTC Hero using XDA
I think this will be same like with explorer sense 3.5,it will be ported sooner or later...
slobo2712 said:
I think this will be same like with explorer sense 3.5,it will be ported sooner or later...
Click to expand...
Click to collapse
That's exactly what I thought about
I like you slobo lol
Sent from my HTC Hero using XDA
lolo7291 said:
That's exactly what I thought about
I like you slobo lol
Sent from my HTC Hero using XDA
Click to expand...
Click to collapse
lol, gay! =)
jk.
in other hands, there are few devs left on the old hero. who will port it? no one!
Guys, the DesireC is the Eris. Or have I missed something?
The DesireC doesn't have a Sense ICS build, they have an AOSP build. Our AOSP build is ported from theirs.
stritfajt said:
Guys, the DesireC is the Eris. Or have I missed something?
The DesireC doesn't have a Sense ICS build, they have an AOSP build. Our AOSP build is ported from theirs.
Click to expand...
Click to collapse
the Desire C is a brand new phone heres a youtube video http://www.youtube.com/watch?v=yJFsC08IZoQ
This is only for developers if they still have here RUU from desire c
DOWNLOAD
slobo2712 said:
This is only for developers if they still have here RUU from desire c
DOWNLOAD
Click to expand...
Click to collapse
I'm taking a look at it right now
Edit: Weird. system.img is 798MB large and I can't seem to extract it... Where did you find this RUU?
stritfajt said:
I'm taking a look at it right now
Edit: Weird. system.img is 798MB large and I can't seem to extract it... Where did you find this RUU?
Click to expand...
Click to collapse
I found it here http://forum.xda-developers.com/showthread.php?t=1658056 there is guy who extracted it with ext2explore in kitchen,but yes that will be problem it's relly large srecno
extracted it
all files together are about the 470mb
EDIT: removed a lot (apps) now it is 297mb
will try to remove some more files..
nickholtus said:
extracted it
all files together are about the 470mb
EDIT: removed a lot (apps) now i have 297mb
will try to remove some more files..
Click to expand...
Click to collapse
hoho This forum is incredible Everybody together we have infinite intelligence.... Limits exist only in our mind
I greet your work, developers
aleksandar.1 said:
hoho This forum is incredible Everybody together we have infinite intelligence.... Limits exist only in our mind
I greet your work, developers
Click to expand...
Click to collapse
yes, I think we're not a lot on this forum but we know we're a good team together ^^,
Look, personally, I would never have thought that ICS would work on our little hero.
But if it runs as smooth as i'd like it to be, I think I would reconsider the fact I want a one x
Can't deodex it
why not.
change api level to 15
nickholtus said:
why not.
change api level to 15
Click to expand...
Click to collapse
Why deodexing it? It's already deodexed for most apks
I'm trying to cook it a bit but this ROM is so HUGE!!
I just can't believe it would be possible to flash it in system/app
I think we'd better try to have as a base the modules from the working ICS, shouldn't we?
----------------------
EDIT 1
Hey hey!! I cleaned up the System/app folder and now it's size is...144MB...without mail, and without calendar...what a shame!!
But System/ stills 376MB...we're almost there!!
We need to be less than approximatively 190MB (accepting the fact that we will need custom mdt partionning)
lolo7291 said:
Why deodexing it? It's already deodexed for most apks
I'm trying to cook it a bit but this ROM is so HUGE!!
I just can't believe it would be possible to flash it in system/app
I think we'd better try to have as a base the modules from the working ICS, shouldn't we?
----------------------
EDIT 1
Hey hey!! I cleaned up the System/app folder and now it's size is...144MB...without mail, and without calendar...what a shame!!
But System/ stills 376MB...we're almost there!!
We need to be less than approximatively 190MB (accepting the fact that we will need custom mdt partionning)
Click to expand...
Click to collapse
I got the whole /system down to 270MB. But I had do delete quite a lot of APKs... I don't have time to work on it more right now though, maybe later.
I got rom size araund 160 mb but can't install it,i think problem is in update - script maybe...
Hey guys.
I am new to android developing.
I started by porting the CM10.1 ROM from HTC Desire, but my phone is stuck at the Huawei logo when it boots up.
I can still flash another ROM, but that is not the problem.
I want to know how to fix this. I want it to go past the Huawei Logo.
By the way, I used this procedure: http://forum.xda-developers.com/showthread.php?t=1598713 and I used Aurora ICS 5.0 for the base ROM. I know it doesn't have the same version of android, but there is no reason I shouldn't be experimenting like this.
Can anyone help?
Thanks.
rqmok said:
Hey guys.
I am new to android developing.
I started by porting the CM10.1 ROM from HTC Desire, but my phone is stuck at the Huawei logo when it boots up.
I can still flash another ROM, but that is not the problem.
I want to know how to fix this. I want it to go past the Huawei Logo.
By the way, I used this procedure: http://forum.xda-developers.com/showthread.php?t=1598713 and I used Aurora ICS 5.0 for the base ROM. I know it doesn't have the same version of android, but there is no reason I shouldn't be experimenting like this.
Can anyone help?
Thanks.
Click to expand...
Click to collapse
Delete phone.apk and try it?
Sent from my U8800-51
You can't port CM10.1 ROM to ICS ROM as base. That is inpossible.
I know
Mlopik said:
You can't port CM10.1 ROM to ICS ROM as base. That is inpossible.
Click to expand...
Click to collapse
I know, but it is not completely impossible.
I also tried to port it with CM10.1 that you are trying to fix, but I still get the same thing.
I will setup logcat and upload the information here.
Thanks.
Need to ask something
Hey again.
I haven't had time to do anything to my phone yet.
I am replying to ask if there is an awesome tutorial out there that could help me with this porting?
Currently, to port my ROM, I replaced files in port ROM from base ROM. Should I replace files in base ROM from port ROM?
Thanks for the help.
Hi Again
Hello.
I found out that there was a problem with the base ROM.
I have ported CM10.1 from U8800! Yaay!
But there are four things that are not working:
- WiFi
- Bluetooth
- Cam Recording
- Sound
Can you guys tell me how to fix the audio? In the logcat, it says that there is no sound output.
Thanks
CatLog results
Hey guys.
I've got the log attached to this reply. Have a look at the audio events and see what is wrong. I can't figure it out by myself.
Thanks
When will you releasing it fully functional?
Working on JB
Djuganight said:
When will you releasing it fully functional?
Click to expand...
Click to collapse
I have just ported the Jelly Bean from u8800pro to u8800non-pro, so I will be working on this ROM.
Seriously, I have no idea when I will be releasing a fully functional ROM. Because I have my studies as well, so I don't get much time to work on the ROM.
The audio is working in this ROM (wasn't working in the previous port),
The things that are currently not working are:
- WiFi
- Bluetooth
- Video Recording
I will try my best to do as much as possible.
I am new at building android ROMs, so please don't expect too much from me
I will be needing some help from other developers as well.
Do you think I should make a thread for this? or is there already enough not-fully functional JB ROMs there?
Thanks.:good:
Lololololol ridiculous!
Another porting, same issues...
How many are now? 4, 5 Jelly beans?
Ooo man, some times is just better to stay quiet....
Djuganight said:
Lololololol ridiculous!
Another porting, same issues...
How many are now? 4, 5 Jelly beans?
Ooo man, some times is just better to stay quiet....
Click to expand...
Click to collapse
I know how you feel. I also feel that way.
I would like to build Jelly Bean from source, like Blefish is doing right now, but I need a 64bit computer for that (mine is only 32bit. Unless there is a hack for this, I can't build from source.
I think everyone is going to start porting Jelly Bean ROMs until one starts working. :silly:
Everyone is porting the rom with the intention of making ir fully working and then abandon development. Why don't you and others continue the work that is already done instead of making a new port which will end up like the others.
Like your are having compatibility issues due to your 32bit computer, perhaps our device is incompatible with JB...
Djuganight said:
Everyone is porting the rom with the intention of making ir fully working and then abandon development. Why don't you and others continue the work that is already done instead of making a new port which will end up like the others.
Like your are having compatibility issues due to your 32bit computer, perhaps our device is incompatible with JB...
Click to expand...
Click to collapse
U8800 is compatible with JB.
Djuganight said:
Everyone is porting the rom with the intention of making ir fully working and then abandon development. Why don't you and others continue the work that is already done instead of making a new port which will end up like the others.
Like your are having compatibility issues due to your 32bit computer, perhaps our device is incompatible with JB...
Click to expand...
Click to collapse
Our device will remain compatible with every new android untill android will be using some new architecture of processor, so "sometimes it's better to stay silent".
OP, abandon your trials of getting a working JB using copy-paste ports. It can be only ported from source.
P.S.: just install ubuntu x64 and try to build something like CWM recovery out of forumber's source. If it builds, you can build anything you want. Today's computers know how to emulate x64. I'm myself using an old pentium d 820 (i386, sse2 and that's all) and I can build.
Mlopik said:
U8800 is compatible with JB.
Click to expand...
Click to collapse
That I don't know for sure but I believe our is. But why 4 or 5 JB around, all with exactly same issues
Now I and others also pick up a JB Rom, mod it here and there and then instead of 4/5 roms we can have dozens. Then again non working well. This makes sense?
Djuganight said:
That I don't know for sure but I believe our is. But why 4 or 5 JB around, all with exactly same issues
Now I and others also pick up a JB Rom, mod it here and there and then instead of 4/5 roms we can have dozens. Then again non working well. This makes sense?
Click to expand...
Click to collapse
It's still same ROM with other features.. It isn't simply fix Wi-Fi without source.
Djuganight said:
That I don't know for sure but I believe our is. But why 4 or 5 JB around, all with exactly same issues
Now I and others also pick up a JB Rom, mod it here and there and then instead of 4/5 roms we can have dozens. Then again non working well. This makes sense?
Click to expand...
Click to collapse
Because most of devs or those who like to be called developers don't have required knowledge and then leave the project as an excuse.
Honestly I have no hope that we can see a JB rom fully functional.
dark_vader said:
Because most of devs or those who like to be called developers don't have required knowledge and then leave the project as an excuse.
Honestly I have no hope that we can see a JB rom fully functional.
Click to expand...
Click to collapse
Why you don't make some for android yourself? if it's so simply.
nagato.fm said:
Our device will remain compatible with every new android untill android will be using some new architecture of processor, so "sometimes it's better to stay silent".
OP, abandon your trials of getting a working JB using copy-paste ports. It can be only ported from source.
P.S.: just install ubuntu x64 and try to build something like CWM recovery out of forumber's source. If it builds, you can build anything you want. Today's computers know how to emulate x64. I'm myself using an old pentium d 820 (i386, sse2 and that's all) and I can build.
Click to expand...
Click to collapse
So I can install ubuntu x64 on my x86 laptop? Are you talking about a virtual machine or installing ubuntu x64 on the actual laptop?
And as for others: Instead of saying that JB is not compatible with our device and all that sh*t, why don't you encourage me and give me some solutions.
Anyways, I am not posting this JB ROM until it's fully functional, because I might stop development as well (getting interested in firefox os).
rqmok said:
So I can install ubuntu x64 on my x86 laptop? Are you talking about a virtual machine or installing ubuntu x64 on the actual laptop?
And as for others: Instead of saying that JB is not compatible with our device and all that sh*t, why don't you encourage me and give me some solutions.
Anyways, I am not posting this JB ROM until it's fully functional, because I might stop development as well (getting interested in firefox os).
Click to expand...
Click to collapse
First of all,your CPU must support x64,If it supported,you can install x64 to you computer.
If you want install x64 system in virtual machine (like VirtualBox),you CPU must support VT-x or AMD-V (virtualization).
You can check virtualization and x64 support via SecurAble;
http://securable.en.softonic.com
Hi all,
Is there any chance to run Sailfish OS on a non-Jolla phone? I would prefer a bigger screen and I'd prefer to not wait for their phone.
Assuming that the drivers from Android are compiled for the same Linux kernel version as I want to run in Sailfish, they should be loadable.
So then it's just a question of whether Sailfish is written to use the same devices (in /dev) in the same ways.
Anybody know?
Cheers.
tabstop said:
Hi all,
Is there any chance to run Sailfish OS on a non-Jolla phone? I would prefer a bigger screen and I'd prefer to not wait for their phone.
Click to expand...
Click to collapse
First of all, Sailfish is not yet released to public, and most propably wont be before Jolla phone hits markets. So you can't get it before
tabstop said:
Hi all,
Assuming that the drivers from Android are compiled for the same Linux kernel version as I want to run in Sailfish, they should be loadable.
So then it's just a question of whether Sailfish is written to use the same devices (in /dev) in the same ways.
Anybody know?
Cheers.
Click to expand...
Click to collapse
Nobody knows yet, because nobody hasn't been able to have a look at it, since it hasn't been released. But I doubt that the kernel would match, since it doesn't even match on different Android phones. There are always some minor changes.
tabstop said:
Hi all,
Is there any chance to run Sailfish OS on a non-Jolla phone? I would prefer a bigger screen and I'd prefer to not wait for their phone.
Click to expand...
Click to collapse
Yes i think it will be possible run Sailfish on non-Jolla phone, anyway you should wait because there is no image for arm cpu in public.
tabstop said:
Assuming that the drivers from Android are compiled for the same Linux kernel version as I want to run in Sailfish, they should be loadable.
So then it's just a question of whether Sailfish is written to use the same devices (in /dev) in the same ways.
Anybody know?
Cheers.
Click to expand...
Click to collapse
in android devices in /dev very often is used from binary blobs.
and this blob compiled againts another libc called bionic and it is not compatible with glibc, but Jolla phone will use android drivers via special library.
Sailfish OS for Motorola XT910 ( Droid RAZR )
tabstop said:
Hi all,
Is there any chance to run Sailfish OS on a non-Jolla phone? I would prefer a bigger screen and I'd prefer to not wait for their phone.
Assuming that the drivers from Android are compiled for the same Linux kernel version as I want to run in Sailfish, they should be loadable.
So then it's just a question of whether Sailfish is written to use the same devices (in /dev) in the same ways.
Anybody know?
Cheers.
Click to expand...
Click to collapse
Well, the Sailfish OS runs on linux kernel thats for sure and soon it will have the capability to run almost all of the android apks, which means it can not be totally different form android form 'under-the-hood' so there is always some room to try it on your android devices.
I haven't really tried to explore Sailfish OS much, but if u do, plz tell me and I would like to do it on my phone (Moto xt910).
If you come across any guide for installing Sailfish OS on non-jolla phones, plz post the links here.
sidbhatt11 said:
Well, the Sailfish OS runs on linux kernel thats for sure and soon it will have the capability to run almost all of the android apks, which means it can not be totally different form android form 'under-the-hood' so there is always some room to try it on your android devices.
Click to expand...
Click to collapse
running apk doesn`t mean anything, i can run apk on my windows 7.
internaly it is GNU Linux, not android.
sidbhatt11 said:
I haven't really tried to explore Sailfish OS much, but if u do, plz tell me and I would like to do it on my phone (Moto xt910).
If you come across any guide for installing Sailfish OS on non-jolla phones, plz post the links here.
Click to expand...
Click to collapse
you should understand that nobody care about your motorola or what ever device you own. 3.5 developers that can build nemo mobile image will not do it just because of your request.
If I remember right the first demo shown of it was on a nexus phone. so of course it will run on android phone.
tsaxda said:
If I remember right the first demo shown of it was on a nexus phone. so of course it will run on android phone.
Click to expand...
Click to collapse
can you give URL?
EnErGy[CSDX] said:
can you give URL?
Click to expand...
Click to collapse
I just remember seeing a video demo of it on youtube and the guy giving the demo said it was running on a galaxy nexus. I don't have the link but you could find it easily on youtube.
It's an open source,isn't it?
c786764052 said:
It's an open source,isn't it?
Click to expand...
Click to collapse
Silica components and that fancy home screen are not open source
I must admit I really like this OS.. even if it is similar to blackberry 10 for some aspects.. if this os will be avaiable for rooted android phones, i will certainly install it on mine!
I'd install it fast if my phone could get this (LG L5), but I think it's too weak on it. Maybe Sony Ericsson xperia neo would take this.
Sent from my LG-E610 using xda app-developers app
N9 arm port is here who starts porting?
EnErGy[CSDX] said:
Yes i think it will be possible run Sailfish on non-Jolla phone, anyway you should wait because there is no image for arm cpu in public.
in android devices in /dev very often is used from binary blobs.
and this blob compiled againts another libc called bionic and it is not compatible with glibc, but Jolla phone will use android drivers via special library.
Click to expand...
Click to collapse
since the N9 port of Sailfish OS is now available:
h**p://jollausers.com/2013/12/the-comprehensive-guide-to-port-sailfish-to-n9/
and the arm chipset in the N9 (OMAP3630) is equal to many Android devices like the Defy+ h**p://en.wikipedia.org/wiki/OMAP it would be nice to hear that someone begins with the porting to other Android devices. Hopefully also for my Droid 4 (OMAP4430).
https://github.com/KonstaT/sailfishos_kernel_jolla_msm8930
thx to Konsta @ talk.maemo.org
cvp said:
https://github.com/KonstaT/sailfishos_kernel_jolla_msm8930
thx to Konsta @ talk.maemo.org
Click to expand...
Click to collapse
Would be great if it could run on Galaxy note 2 or 3.
I was searching a bit about snapdragon 430 and the devices that use it.
And i came across a device with the same specs as redmi 3s(land)
So, i was wondering,
Could we use it?
Its stable and built on AOSP
Device link=http://m.gsmarena.com/bq_aquaris_u_plus-8378.php
Rom links=https://www.bq.com/en/support/aquaris-u-plus/support-sheet
No. You'll have to ask the developers to 'PORT' the ROM to run on the intended device.
zans1023 said:
No. You'll have to ask the developers to 'PORT' the ROM to run on the intended device.
Click to expand...
Click to collapse
Well, i suppose it wont be hard to to that since the hardware is exactly the same
Jure_aleksic said:
Well, i suppose it wont be hard to to that since the hardware is exactly the same
Click to expand...
Click to collapse
Hardware is same
The kernel is not.
Some stuff like fingerprint sensor wouldn't work.
Jure_aleksic said:
I was searching a bit about snapdragon 430 and the devices that use it.
And i came across a device with the same specs as redmi 3s(land)
So, i was wondering,
Could we use it?
Its stable and built on AOSP
Device link=http://m.gsmarena.com/bq_aquaris_u_plus-8378.php
Rom links=https://www.bq.com/en/support/aquaris-u-plus/support-sheet
Click to expand...
Click to collapse
Those are stock ROM links, probably not much interesting in these ROM's anyway
The kernels are different, CPU frequencies also different.
Yappuccino said:
The kernels are different, CPU frequencies also different.
Click to expand...
Click to collapse
Frequencies are the same
Jure_aleksic said:
Frequencies are the same
Click to expand...
Click to collapse
Kernel still isn't the same.
You can try replacing the vendor directory, and the /system/etc/firmware directory, and you will still get many features don't work.
Please suggest some apps that make best use of 64 bit custom roms .. thanks in advance!
Honestly... Google camera is about it, and it's quality is questionable compared to stock camera.
The whole "64-bit" thing is seriously over-hyped... other than the few apps that are 64-bit only (of which, only Google Camera comes to mind) I don't think you will see a noticeable performance change in apps that have both 32 and 64 bit versions.
Don't get me wrong, I am glad developers got 64-bit OS's working on this device, any advancement in custom ROMs is awesome and the devs deserve a lot of praise because I am sure it was hard work.
Am I right in thinking all the Oreo ROMs are 64bit? And you just flash in the same way as any other ROM?
eemgee said:
Am I right in thinking all the Oreo ROMs are 64bit? And you just flash in the same way as any other ROM?
Click to expand...
Click to collapse
Some of them that aee updated weekly/monthly are 64-bit now... Really they are 32/64-bit hybrids, but many are still 32bit
eemgee said:
Am I right in thinking all the Oreo ROMs are 64bit? And you just flash in the same way as any other ROM?
Click to expand...
Click to collapse
Flash them like normal, except you must use the 64 bit version of TWRP.
username8611 said:
Flash them like normal, except you must use the 64 bit version of TWRP.
Click to expand...
Click to collapse
No since official twrp 3.2.0-0 it supports 64 bit