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
There are several roms for kitkat on the nexus all promising everything works and good speed...some are based on the nexus 5 factory images...others are based on the aosp sources....my question is which is going to give the "most bang for the buck"?
Does using "ART" actually provide verifiable app speed increases?
famewolf said:
There are several roms for kitkat on the nexus all promising everything works and good speed...some are based on the nexus 5 factory images...others are based on the aosp sources....my question is which is going to give the "most bang for the buck"?
Does using "ART" actually provide verifiable app speed increases?
Click to expand...
Click to collapse
Yes for the second question.
Dont know if you know that KITKAT is not out official for N4. So now we all running the hybrid version of KITKAT.
The binaries used are from 4.3. So just wait for the official N4 KITKAT ROM or else till then try the N5 KITKAT PORT v3 OR AOSPA KITKAT. Both are good,but PORT is better.
Go with the Port
Though the ASOP build make it out first, the N5 Port is super stable and just about everything is working. It's now my daily driver.
og1502 said:
Though the ASOP build make it out first, the N5 Port is super stable and just about everything is working. It's now my daily driver.
Click to expand...
Click to collapse
+ one on the Nexus 5 port, the only thing that doesn't work for me is compass although navigation works.
there are some complaints in the thread that some things don't work, but those are from people who cant follow instructions.
One question on the Nexus 5 port, do you know which browser can watch Flash video/content?
I have installed the latest flash player 11.1 apk. Suppose the Firefox can show the flash, but it fail. Have a search on web, there is no much information about it...
Also the new business search in dialer and new caller id feature only works in port. For now...
[ LTE Nexus 4 | Kit Kat ] ?
Hello!
So CM11 Nightlies have F2FS support. TWRP 2.8.0.1 supposedly (I cant get it to work) has support for it as well. I heard that TWRP requires an F2FS kernel in order for the option to format to F2FS to appear.
Now, Are there any F2FS kernels available for AOSP ROMs? Is there a way to change filesystems to F2FS right now?
Thanks for any help!
RevolcFael4 said:
Hello!
So CM11 Nightlies have F2FS support. TWRP 2.8.0.1 supposedly (I cant get it to work) has support for it as well. I heard that TWRP requires an F2FS kernel in order for the option to format to F2FS to appear.
Now, Are there any F2FS kernels available for AOSP ROMs? Is there a way to change filesystems to F2FS right now?
Thanks for any help!
Click to expand...
Click to collapse
Not sure if its available for the g2, but even if it was i think itd a bit too risky for you to transform into it, it could lead into bad bricking. you wouldnt notice a speed difference neither! slower phones like the MOTO G, NEXUS 4, GALAXY NEXUS all go faster, but for a device already so fast, you wont tell a thing.
but each to their own, try it if you really want!
idonttakedrugs said:
Not sure if its available for the g2, but even if it was i think itd a bit too risky for you to transform into it, it could lead into bad bricking. you wouldnt notice a speed difference neither! slower phones like the MOTO G, NEXUS 4, GALAXY NEXUS all go faster, but for a device already so fast, you wont tell a thing.
but each to their own, try it if you really want!
Click to expand...
Click to collapse
Oh.
I already moved everything off my phone.
Anyways, CM!1 nightlies dont boot after the F2FS compatability. Is there anything I can do to make it work?
Hi
The f2fs thread is not up to date and has broken links.
Can anyone list some f2fs ROMS and kernels, kitkat or lollipop that i can try out?
Thanks
GorfDroid said:
Hi
The f2fs thread is not up to date and has broken links.
Can anyone list some f2fs ROMS and kernels, kitkat or lollipop that i can try out?
Thanks
Click to expand...
Click to collapse
Interested as well. Did you ever manage to install Lollipop with F2FS?
raz123 said:
Interested as well. Did you ever manage to install Lollipop with F2FS?
Click to expand...
Click to collapse
I did actually but you'll need an f2fs compatible kernel like sabermod Franco kernel.
Everyone says you need an f2fs compatible ROM but that has not always been my experience. I've used it with just an f2fs kernel and it worked.
I no longer use f2fs though. I use ext4 with journaling off. I understand it is the same thing and my phone is just as snappy.