Hi guys,
Some progress are made.
Finished building kernel :victory:
Tryed on Sense 4 (by @coolos ) BOOTS
Tryed on ported Sense 5 BOOTLOOP :crying:
Thanks to @coloured_chalk for his kernel source and begin and important dev for this project :highfive:
Thanks to @coolos for teach me porting Sense 5 and some more useful things :good:
Best Regards,
Marco Marinho
Please mention others devs. I don't know very much the HTC Desire Z community
I'll try this like... next year or something. heheheh
(can we get an MIUI port instead? much needed by now.)
---------- Post added at 12:03 AM ---------- Previous post was at 12:00 AM ----------
Also, does this work on an rom with sense 4.1? because I'm currently running a sense rom...
@_MarcoMarinho_ good idea, although I think it would be a hard undertaking:
* Other members and I have tried porting JellyBean ROMs but we don't yet know of a way to get the hardware keyboard fully working (lights, auto rotate, etc.);
* That ROM you linked still appears to be in alpha state, perhaps it's best to wait until everything is functioning on that first or look for Sense 5 on another similar device (although the Desire HD has the advantage of being the same resolution which makes everything much easier);
* All of the Desire Z developers working on JellyBean pretty much abandoned 4.1.2 in order to start work on 4.2.2 so unless Sense 5 can be ported to 4.2.2 this could cause problems because I know that many improvements were made, for example in cn.fyodor's AOSP JB, between these two versions;
* The Desire Z has limited RAM and Sense is very heavy, although HTC may have remedied this in Sense 5 so it may run fine;
* I wouldn't even know where to begin on the kernel, all I know is that Sense kernels can't run AOSP ROMs and AOSP kernels can't run Sense ROMs. I have no idea why though. I would have thought all it takes is some small modification of the Andromadus 3.x kernel.
On a positive note, this would be awesome and I'd much rather use Sense 5 than previous Sense versions, namely because I can't live without gapless playback which ICS lacks. I would like to help but I currently lack a booting computer although I hope this is remedied soon!
HTCDreamOn said:
@_MarcoMarinho_ good idea, although I think it would be a hard undertaking:
* Other members and I have tried porting JellyBean ROMs but we don't yet know of a way to get the hardware keyboard fully working (lights, auto rotate, etc.);
* That ROM you linked still appears to be in alpha state, perhaps it's best to wait until everything is functioning on that first or look for Sense 5 on another similar device (although the Desire HD has the advantage of being the same resolution which makes everything much easier);
* All of the Desire Z developers working on JellyBean pretty much abandoned 4.1.2 in order to start work on 4.2.2 so unless Sense 5 can be ported to 4.2.2 this could cause problems because I know that many improvements were made, for example in cn.fyodor's AOSP JB, between these two versions;
* The Desire Z has limited RAM and Sense is very heavy, although HTC may have remedied this in Sense 5 so it may run fine;
* I wouldn't even know where to begin on the kernel, all I know is that Sense kernels can't run AOSP ROMs and AOSP kernels can't run Sense ROMs. I have no idea why though. I would have thought all it takes is some small modification of the Andromadus 3.x kernel.
On a positive note, this would be awesome and I'd much rather use Sense 5 than previous Sense versions, namely because I can't live without gapless playback which ICS lacks. I would like to help but I currently lack a booting computer although I hope this is remedied soon!
Click to expand...
Click to collapse
Yes, but we can build the kernel with ION support. Then we only need to take the files from HTC Desire HD e replace some to make it work on our device. The only thing we need to create/build is the kernel, so won't be difficult right?
BTW, @HTCDreamOn , I saw that you took the kernel for saga and make it work on vision, so you can do the same right? They had the kernel source in the thread :good:
Regards,
Marco Marinho
As mentioned, I think sense 5 is too heavy for our device. The desire HD has an additional 256 MB of ram over our device. A fully functional CM11 is probably the best we can ask for our device.
sharptv said:
As mentioned, I think sense 5 is too heavy for our device. The desire HD has an additional 256 MB of ram over our device. A fully functional CM11 is probably the best we can ask for our device.
Click to expand...
Click to collapse
Sense 5 is not so heavy, and I am pretty sure it will work great on DZ. Only problem is kernel and drivers (biggest problem).
sharptv said:
As mentioned, I think sense 5 is too heavy for our device. The desire HD has an additional 256 MB of ram over our device. A fully functional CM11 is probably the best we can ask for our device.
Click to expand...
Click to collapse
The only thing that is impossible is the impossibility As @coolos said the only problem is the kernel and drivers :highfive:
coolos said:
Sense 5 is not so heavy, and I am pretty sure it will work great on DZ. Only problem is kernel and drivers (biggest problem).
Click to expand...
Click to collapse
But if others do it, so we can do it
Regards,
Marco Marinho
Ok first of all most people are having difficulties booting Dr.Globs Sense5 atm,
so I suggest either trying Unimaginable (IncS section) or Imaginable (DHD section), both confirmed booting fine, or of you want Sense4+, link to AceTify is in my sig. Obviously you need ION kernel to boot any of these. Of course that's for testing/debuging only, you need a permission if you choose to release re-ported ROM
sharptv said:
As mentioned, I think sense 5 is too heavy for our device. The desire HD has an additional 256 MB of ram over our device. A fully functional CM11 is probably the best we can ask for our device.
Click to expand...
Click to collapse
Desire 300 has 512MB and is running Sense5 lite.
-SmOgER said:
Ok first of all most people are having difficulties booting Dr.Globs Sense5 atm,
so I suggest either trying Unimaginable (IncS section) or Imaginable (DHD section), both confirmed booting fine, or of you want Sense4+, link to AceTify is in my sig. Obviously you need ION kernel to boot any of these. Of course that's for testing/debuging only, you need a permission if you choose to release re-ported ROM
Desire 300 has 512MB and is running Sense5 lite.
Click to expand...
Click to collapse
I'm not saying to port from snese 5 Dr.Globs, I only quoted a thread that he opened, I only quoted to show that the differences BTW Desire Z and Desire HD aren't much. We only need to change a little things to make it work on our device.
The first step is porting the kernel with ION support. I'm currently working on it :highfive:
I will facing unkown problems. I already tryed to change the source code, update the toolchain and is the same
-SmOgER, can you help me with this. Look at the attachments please
Regards,
Marco Marinho
Ask @coloured_chalk or @tweakos,
I'am not very big expert on kernels.
_MarcoMarinho_ said:
I'm not saying to port from snese 5 Dr.Globs, I only quoted a thread that he opened, I only quoted to show that the differences BTW Desire Z and Desire HD aren't much. We only need to change a little things to make it work on our device.
The first step is porting the kernel with ION support. I'm currently working on it :highfive:
I will facing unkown problems. I already tryed to change the source code, update the toolchain and is the same
-SmOgER, can you help me with this. Look at the attachments please
Regards,
Marco Marinho
Click to expand...
Click to collapse
you use wrong make syntax the proper should look something like
Code:
make ARCH=arm CROSS_COMPILE=$CROSS_COMPILE -j`grep 'processor' /proc/cpuinfo | wc -l`
You set CROSS_COMPILE var with the path to yours toolchain but didnt use it later. Another missed part is ARCH . Also -j with CPU thread num will decrease compilation time
Look at http://oldwiki.cyanogenmod.org/wiki/Building_Kernel_from_source for more info
ps ION support is kind of easy if the kernel sources are with proper drivers for it. When I have time to work over my kernel I should update the drivers to be able to add ION support.
Cheers
Neo2SHYAlien said:
you use wrong make syntax the proper should look something like
Code:
make ARCH=arm CROSS_COMPILE=$CROSS_COMPILE -j`grep 'processor' /proc/cpuinfo | wc -l`
You set CROSS_COMPILE var with the path to yours toolchain but didnt use it later. Another missed part is ARCH . Also -j with CPU thread num will decrease compilation time
Look at http://oldwiki.cyanogenmod.org/wiki/Building_Kernel_from_source for more info
ps ION support is kind of easy if the kernel sources are with proper drivers for it. When I have time to work over my kernel I should update the drivers to be able to add ION support.
Cheers
Click to expand...
Click to collapse
Now works *-* Thnks bro, really thnks :highfive:
Once again, error -_-
Regards,
Marco Marinho
_MarcoMarinho_ said:
Now works *-* Thnks bro, really thnks :highfive:
Once again, error -_-
Regards,
Marco Marinho
Click to expand...
Click to collapse
Try different toolchain. If you use linaro 4.8 try older version 4.7 or 4.6
Good news guys,
Kernel - BOOTS :victory:
And I get it the drivers :good:
So the next step it's port it. I will check if the ion support it's enabled
Check op for more information.
Happy new year to everyone
Ok, first try porting sense 5.
At the begin graphics glitches and then black screen, reboots and do the same :crying:
Gona try with a different kernel :highfive:
Feedback soon.
FAILED!
Trying to do a clean kernel now. I will build ASAP. Keep your Eyes Open
As I don't know anything about that kind of stuff, all I can do is wish you good luck and thank you for keeping our dear old device alive
All the best for 2014 man !
_MarcoMarinho_ said:
FAILED!
Trying to do a clean kernel now. I will build ASAP. Keep your Eyes Open
Click to expand...
Click to collapse
is there any Navigation Bar option available in this upComing ROM?
try porting this unless you found a D300 one already o.o
http://forum.xda-developers.com/showthread.php?t=2584435
Related
As you may know, HTC have just released the kernel source code, and i've been having a play.
Nothing massively exciting yet, but if you want your kernel to feature...
- Additional filesystems (EXT4, NFS, CramFS, SquashFS 4.0)
- Freshly compiled tun.ko module
- CompCache 0.5.4 support
- Required iptables functionality for DroidWall
...then you can install this package over the top of the latest MCR.
This is pretty much untested at the moment, so Nandroid backup first (of course), and i'm taking requests for future improvements. This is seperate from the main MCR thread for now simply because of it's untested nature!
I'd like to add...
- Port to 2.6.29 kernel
...but as I say this is just an early first-stab at a custom kernel. I thought i'd put it out there as I know many people like to run EXT4 on their A2SD partitions.
Download: MoDaCo
Enjoy!
P
Changelog
1.2
Added DroidWall support
1.1
Internal (non public) Test Release
1.0
Initial Release
Added source download.
P
We could look into Bluetooth OBEX file transfers now...
oblika said:
We could look into Bluetooth OBEX file transfers now...
Click to expand...
Click to collapse
http://code.google.com/p/androidobex/source/checkout
Version 1.2 up, added DroidWall support.
P
MCK 1.2 is now rolled into MCR 2.8. This thread will remain as the test bed / source code post.
P
good going Paul.
Good work Paul ,I apriciate your hard work. You are our HERO.
gangstaunitg said:
Good work Paul ,I apriciate your hard work. You are our HERO.
Click to expand...
Click to collapse
Bump - i second that!
MasterOfDesasters said:
Bump - i second that!
Click to expand...
Click to collapse
I have to third that.
modaco said:
As you may know, HTC have just released the kernel source code, and i've been having a play.
Nothing massively exciting yet, but if you want your kernel to feature...
- Additional filesystems (EXT4, NFS, CramFS, SquashFS 4.0)
- Freshly compiled tun.ko module
- CompCache 0.5.4 support
- Required iptables functionality for DroidWall
...then you can install this package over the top of the latest MCR.
This is pretty much untested at the moment, so Nandroid backup first (of course), and i'm taking requests for future improvements. This is seperate from the main MCR thread for now simply because of it's untested nature!
I'd like to add...
- Port to 2.6.29 kernel
...but as I say this is just an early first-stab at a custom kernel. I thought i'd put it out there as I know many people like to run EXT4 on their A2SD partitions.
Download: MoDaCo
Enjoy!
P
Click to expand...
Click to collapse
I'd love to help test this however I'm new to Android so when you say MCR I assume you mean the latest Modaco Rom? So I should install MCR then install this? Sorry and thanks, looking forward to giving it a go
will this have CDMA support by any chance for the CDMA hero?
jman069 said:
I'd love to help test this however I'm new to Android so when you say MCR I assume you mean the latest Modaco Rom? So I should install MCR then install this? Sorry and thanks, looking forward to giving it a go
will this have CDMA support by any chance for the CDMA hero?
Click to expand...
Click to collapse
The MCK kernel was added to the custom ROM in version 2.8, so if you want it all you have to do is install the MOdaco ROM 2.8
Well may be it is possible to make clean Android OS available for HTC Hero since kernel sources are released? With no Sense UI etc.
NoXXX said:
Well may be it is possible to make clean Android OS available for HTC Hero since kernel sources are released? With no Sense UI etc.
Click to expand...
Click to collapse
There seem to be more and more people expecting that
all our hopes r on the devs. only they can provide us something. good job guys. keep it up.
*sorry. double post*
No sense UI..................Slightly off topic
frandavid100 said:
There seem to be more and more people expecting that
Click to expand...
Click to collapse
I dont understand all the people not wanting sense UI
if you dont want it, go into settings--------manage applications-----find touch flo and clear defaults....
The next time you press the home button, just press launcher and make it your default home screen.
There you have it...
Sorry Paul for going slightly off topic
Some people do not want it because they find it heavy.
By using the clear defaults method you only visually disabling it, but in the background the sense ui processes are still running.
ZenorGR said:
Some people do not want it because they find it heavy.
By using the clear defaults method you only visually disabling it, but in the background the sense ui processes are still running.
Click to expand...
Click to collapse
Ever heard about Paul's Rosie remover? I think what people want is to get features of e.g. Cyanogens work in a ROM, and the ability to modify. In fact if you remove Rosie, add some vanilla android apps and change the Hero drawables in the framwork.apk you'll get a "vanilla" looking and working kind of ROM.
EDIT: It is now fully working except camera. Stay tuned
EDIT2: CM6 Alpha Preview is available from here
Here is the github repo: http://github.com/loxK/android_device_htc_hero
Here is the issue: http://github.com/loxK/android_device_htc_hero/issues#issue/3
Status:
- wifi ok
- BT ok
- Accelerometer: ok
- Jogball: ok
- HW keys: ok
- Camera: fails
- Touch screen: fails
What about the mic, is it working? Thanks for your help to the hero community. Are you going to return to us?
This happens because some of the libs (HTC + android) are meant to be dl-opened and some are prelinked.
You can always play around with ldd to find which are dynamic and which aren't.
libaudio / libaudioeq / libhardware_legacy tend to cause problems.
Touch screen is now working, was kernel related. But proprietary libs are still not getting linked correctly...
gewoontim said:
What about the mic, is it working?
Click to expand...
Click to collapse
I can send voice commands to the phone witch are recognized.
gewoontim said:
Thanks for your help to the hero community. Are you going to return to us?
Click to expand...
Click to collapse
I do not belong to anyone. I do the work I need for me, or concerning Hero, for my girlfriend needs. I just share it, that is all.
But please do respect the " [dev] " in the thread subject and do not pollute and wait for a release.
Can you give these libs a try?
http://www.multiupload.com/EIPA5SFXAW
I created a full Froyo build with HTC propitiatory drivers.
Let me know if you need anything else.
Feeyo said:
Can you give these libs a try?
http://www.multiupload.com/EIPA5SFXAW
I created a full Froyo build with HTC propitiatory drivers.
Let me know if you need anything else.
Click to expand...
Click to collapse
I tried but same error. So u managed to build/run it from source? Is your vendor or device tree somewhere online ?
after having JIT working on Sense 2.1 (thanks for Feeyo) and having the official 2.1 Froyo is the most important thing - I think
The communities eyes are on you guys C:
Good luck!
Lox_Dev said:
I tried but same error. So u managed to build/run it from source? Is your vendor or device tree somewhere online ?
Click to expand...
Click to collapse
I have build it from source yea and got booted up. Although I am having a lot of issues with FC's. I used the sapphire tree with edits and used the 2.1 Hero proprietary drivers to compile it correctly.
I got struck on that spl thing, but Darchstar have near working froyo for cdma. So there is probably some solution to touchscreen problem at least. Look here:
http://forum.xda-developers.com/showthread.php?t=686893
and here:
http://github.com/darchstar
It is now fully working except camera (didn't sleep for 24 hours now and still awake!).
Stay tuned!
Woah great work! I'm guessing you will release it when you get the camera working?
I will defiantly flash as soon this is out
Cant wait
Lox_Dev said:
It is now fully working except camera (didn't sleep for 24 hours now and still awake!).
Stay tuned!
Click to expand...
Click to collapse
awesome stuff, cant wait to try a froyo build.
Now this shows who's the real "ROM assembler". None of the popular* ROM "developers" have achieved this. Thanks and congrats Lox_Dev!
* I'm referring to those people who are considering themselves experts in ROM "development".
DSF said:
Now this shows who's the real "ROM assembler". None of the popular* ROM "developers" have achieved this. Thanks and congrats Lox_Dev!
* I'm referring to those people who are considering themselves experts in ROM "development".
Click to expand...
Click to collapse
You're right ;-)
DSF said:
Now this shows who's the real "ROM assembler". None of the popular* ROM "developers" have achieved this. Thanks and congrats Lox_Dev!
* I'm referring to those people who are considering themselves experts in ROM "development".
Click to expand...
Click to collapse
in fairness RaduG compiled Cyan 5.0.7 from Source. He's been on holiday since before Froyo sources were released (AND RaduG is 17!)
But definately, Lox is one of the forefront devs to have looked at Hero, along with Paul, MoDaCo who prefers to deal with Sense than Cyan
Im quite looking forward to trying this. Thank you for your hard work!
it doesn´t mind for me if the camera is not working because i do not use it, but only if you can´t solve it, i think that you can release it and then make an update.zip fix for the camera like other devs.
but whitout any hurry, this is only my opinion.
i can´t wait to flash this.
good job man.
It must be fun to know that xda and twitter get hammered by people waiting for a download link . Great effort, Lox. Again you start the route to a great variety of Froyo Roms on our not yet old-fashioned Heroes
Thanks for making your source tree public and let others benefit from your findings. Nice stroke.
Things you might want to test: (you asked on twitter)
- Proximity sensor
- Brightness sensor
- Location searching through WLAN
- Gmail sync
- Full market access
- Alarm clock
- su (root)
BTW: Can't wait to modify my Exchange password policy removal tool to work on Froyo. If you need assistance in testing, let me know
just a question, will we be able to flash it tonight?
This is the new base with Sense 3.5
Let's start the porting!!
-All the thanks to coolexe
-Android 2.3.4
-Sense 3.5
-New Optimized Sense! VERY FAST & SMOOTH!!!
-First base from Desire S
-New Base from HTC Bliss 1.10.401.0 - NO CHINESE LEAK - tnx to capychimp
Click to expand...
Click to collapse
INITIAL BASE FROM DESIRE S:
http://www.multiupload.com/03ZBV41PW7
https://rapidshare.com/#!download|857l32|2986199375|saga_sense3.5_0901.zip|331700|R~AB36E81E1EAA0582A2DDBDACE9E3E1AA|0|0
NEW BASE FROM HTC BLISS (by capychimp) :
The Devs can download the capy's port for Desire HD and make a porting to HTC LEO
This is the capy's Thread: http://forum.xda-developers.com/showthread.php?t=1245938
NOTE:Do not Flash this Rom!! it's requires a porting to work on HTC Leo! I'm not responsable!
EDIT: I think we need a new kernel for Sense Roms with Android 2.3.4/2.3.5. Probably with RafPigna or Tytung Kernels this rom bootloops. Waiting for news and tests or news from kernel developers
EDIT2: sbryan12144 posted a news on kernel tests...if someone need a kernel for Android 2.3.4 with sense, pm to him! Thanks to sbryan12144!!!
I had posted the video of Sense 3.5 only a couple of days back - http://forum.xda-developers.com/showthread.php?t=1242932
Looks like Sense 3.5 is optimized for older / lower processing capability devices. Along with the Desire's kernel source (yet to be released - but they eventually have to within 90 days of release of the update), this would make an interesting port!
ph03n!x said:
I had posted the video of Sense 3.5 only a couple of days back - http://forum.xda-developers.com/showthread.php?t=1242932
Looks like Sense 3.5 is optimized for older / lower processing capability devices. Along with the Desire's kernel source (yet to be released - but they eventually have to within 90 days of release of the update), this would make an interesting port!
Click to expand...
Click to collapse
Desire's GB kernel source will be released?? It can solve a lot of problems (glitches, ecc.)
When was the Gingerbread upgrade for Desire released ? I mean the exact date...
DannyBiker said:
When was the Gingerbread upgrade for Desire released ? I mean the exact date...
Click to expand...
Click to collapse
From the file I downloaded from htc's developer site, seems to be 1st of Aug (11:22 AM) - am in India, so factor in GMT +5.30.
This means 1st of November should be the deadline for the source code...
omg..i cant wait for first relase!
It could delete bugs like graphic or camcorder ? I just want to know...
Sense 3.5 is a downgrade. Trust me, you'll be back to Sense 3.0 shortly after, it's a simplified version of sense targeted(sexist) to women.
bartass127 said:
omg..i cant wait for first relase!
It could delete bugs like graphic or camcorder ? I just want to know...
Click to expand...
Click to collapse
Still no graphics drivers probably. We'll have to wait till we get desire's source.
protomanez said:
Sense 3.5 is a downgrade. Trust me, you'll be back to Sense 3.0 shortly after, it's a simplified version of sense targeted(sexist) to women.
Click to expand...
Click to collapse
From the video posted it appears to be very similar to 3.0...not sure where the 'simplified' parts are...it has the carousel, the little 3d flip when moving screens, and all the fancy options in the dropdown-quick settings tab. How could this be mainly for women? Pink colors? I think the speed and more optimized for our older phones outweigh the very minor differences to regular 3.0.
Hope a port does come out, I will want to try this .
And damn kernel source, they are dragging their feet sooooo badly on that, wtf are they doing??? HTC keeps going forward but slowly forgetting about the old supporters...im sure if devs in here got paid what htc engineers do, we'd have the desire kernel loooong time ago....geesh
Well, if it's a version of Sense that can run on less powerful device it will still be interesting. We might be able to merge the two versions...
XxXPachaXxX said:
EDIT: I think we need a new kernel for Sense Roms with Android 2.3.4/2.3.5. Probably with RafPigna or Tytung Kernels this rom bootloops. Waiting for news and tests or news from kernel developers
Click to expand...
Click to collapse
No. kernel should be fine. I ported a few roms to the HD2 with Sense 3.0 and android 2.3.4. Be sure to watch your logcats and make sure not to replace libmode10fx.so and libaudioflinger.so. I would release if I had an HD2 lol. Maybe sometime in the future..
theslam08 said:
From the video posted it appears to be very similar to 3.0...not sure where the 'simplified' parts are...it has the carousel, the little 3d flip when moving screens, and all the fancy options in the dropdown-quick settings tab. How could this be mainly for women? Pink colors? I think the speed and more optimized for our older phones outweigh the very minor differences to regular 3.0.
Hope a port does come out, I will want to try this .
And damn kernel source, they are dragging their feet sooooo badly on that, wtf are they doing??? HTC keeps going forward but slowly forgetting about the old supporters...im sure if devs in here got paid what htc engineers do, we'd have the desire kernel loooong time ago....geesh
Click to expand...
Click to collapse
The simplified parts are the changed drawers, bigger buttons and pretty much that's it. The phone you're seeing "Sense 3.5" on is a phone put by the press as "targeting women". Our phone is not THAT old it's pretty mid-tier, however it will be interesting to see how it runs.
Probably will be cool to see the changes, but not so much as a daily driver. Expect shovelware?
See said articles:
http://reviews.cnet.com/8301-19736_7-20097250-251/new-details-emerge-for-female-focused-htc-bliss/
http://androidandme.com/2011/08/new...-women-and-men-with-pink-shirts-hits-the-fcc/
sbryan12144 said:
No. kernel should be fine. I ported a few roms to the HD2 with Sense 3.0 and android 2.3.4. Be sure to watch your logcats and make sure not to replace libmode10fx.so and libaudioflinger.so. I would release if I had an HD2 lol. Maybe sometime in the future..
Click to expand...
Click to collapse
OK Bro!! actually i can't make a porting...i'm not at home for some days. What kernel u use with android 2.3.4 and Sense 3.0?? All the thanks to you!!
Couldn't boot this lol. I'm getting old
Iit booted for me but lopps near Lockscreen (same as sense 3 DeisreS). Something wrong in Andreno 3.5, UI
loops Because file libs That changed
i try without change libs ... without port it working boot No Loop
but after Unlock & setup ... home page reload ... reload ...
Need New libs for that ...
boxmax said:
loops Because file libs That changed
i try without change libs ... without port it working boot No Loop
but after Unlock & setup ... home page reload ... reload ...
Need New libs for that ...
Click to expand...
Click to collapse
Yep after few try the capy's 1.1 version it boot but looop with tyhung r11 kernel.. Em...
Will try others kernel see how..Damn can't wait for it to run on our Great HD2 ! Fingers cross ...
imilka said:
Couldn't boot this lol. I'm getting old
Click to expand...
Click to collapse
I don't think so my friend
If we work together .. only time.. to get it running on HD2 he he..
boxmax said:
loops Because file libs That changed
i try without change libs ... without port it working boot No Loop
but after Unlock & setup ... home page reload ... reload ...
Need New libs for that ...
Click to expand...
Click to collapse
Wrong driver, you are a hero !
maybe this can help-
http://forum.xda-developers.com/showthread.php?t=1245938
http://forum.xda-developers.com/showthread.php?t=1246626
Sense 3.5 on desire hd
Glad to see all talented devs on this xD
imilka said:
Couldn't boot this lol. I'm getting old
Click to expand...
Click to collapse
dungphp said:
Iit booted for me but lopps near Lockscreen (same as sense 3 DeisreS). Something wrong in Andreno 3.5, UI
Click to expand...
Click to collapse
boxmax said:
loops Because file libs That changed
i try without change libs ... without port it working boot No Loop
but after Unlock & setup ... home page reload ... reload ...
Need New libs for that ...
Click to expand...
Click to collapse
mccmjoon76 said:
Yep after few try the capy's 1.1 version it boot but looop with tyhung r11 kernel.. Em...
Will try others kernel see how..Damn can't wait for it to run on our Great HD2 ! Fingers cross ...
Click to expand...
Click to collapse
FRIENDS! sbryan12144 can get this rom booting in the first page he says:
"No. kernel should be fine. I ported a few roms to the HD2 with Sense 3.0 and android 2.3.4. Be sure to watch your logcats and make sure not to replace libmode10fx.so and libaudioflinger.so. I would release if I had an HD2 lol. Maybe sometime in the future"
So asked him the kernel...waiting i think rafpigna 2r0 or 1r9 GB can work. Tytung kernel is only for rom without sense.bye All the news in this thread....
Hi guys- I have seen a website or page on how to build your own rom.
how difficult is it on 1 to 10?- 10 being very difficult.
what tools do I need?
many thanks
Well it depends how you create the rom and what type of ROM you are creating.
If you plan to simply take an already made rom.zip, make a few little modifications, and zip it back up...it obviously isn't very hard, and likewise its not very satisfying.
If you want to compile a rom from source, then its a bit harder than the process above. To be more specific let's first talk about android versions that are officially supported by the desire: froyo, and gingerbread. Compiling roms based on those honestly isn't that hard. You just need some basic Linux/terminal knowledge. The device and kernel source is actually meant to work by default so you don't need to make any further adjustments. It as simple as opening terminal, downloading the source, and running a build command. Give it an hour (more or less depending on how food your PC is) and you should have a freshly made ROM that you built from source. Yay...some satisfaction.
The hardest thing in my opinion (I've tried all three of these) is compiling a rom based on an android version that isn't officially supported by the desire. (Ice cream sandwich or jellybean). With roms based on these android versions you will have to scour to internet for a working device, vendor and kernel tree. (Hint, hint: WoH and evervolv/nikez). Even once you get the right device tree it probably won't work. You will have to make further adjustments, and even then I'm sure you will be bombarded with build errors. But eventually once you get it to compile successfully....most satisfying thing ever
So yea thats my answer. Keep in mind that I've tried (and eventually succeeded) with all three of the above, and that I've got quite limited programming knowledge. (2 high school comp sci courses, where I learned some java.)
Sent using xda-developers app
building your own rom
Chromium_ said:
Well it depends how you create the rom and what type of ROM you are creating.
If you plan to simply take an already made rom.zip, make a few little modifications, and zip it back up...it obviously isn't very hard, and likewise its not very satisfying.
If you want to compile a rom from source, then its a bit harder than the process above. To be more specific let's first talk about android versions that are officially supported by the desire: froyo, and gingerbread. Compiling roms based on those honestly isn't that hard. You just need some basic Linux/terminal knowledge. The device and kernel source is actually meant to work by default so you don't need to make any further adjustments. It as simple as opening terminal, downloading the source, and running a build command. Give it an hour (more or less depending on how food your PC is) and you should have a freshly made ROM that you built from source. Yay...some satisfaction.
The hardest thing in my opinion (I've tried all three of these) is compiling a rom based on an android version that isn't officially supported by the desire. (Ice cream sandwich or jellybean). With roms based on these android versions you will have to scour to internet for a working device, vendor and kernel tree. (Hint, hint: WoH and evervolv/nikez). Even once you get the right device tree it probably won't work. You will have to make further adjustments, and even then I'm sure you will be bombarded with build errors. But eventually once you get it to compile successfully....most satisfying thing ever
So yea thats my answer. Keep in mind that I've tried (and eventually succeeded) with all three of the above, and that I've got quite limited programming knowledge. (2 high school comp sci courses, where I learned some java.)
Sent using xda-developers app
Click to expand...
Click to collapse
Thanks for that-
Sound very complicated
I am a webdesigner but have no knowledge of developing.
Wanted to try and build a really good rom to make the desire a really good phone for photography.
I have on my phone your rom and RSK supersense 3.5 rom running - coz I like the camera
and I would like to make a rom to turn it into a photography rom for my phone.
any advice??
creating your own rom
Chromium_ said:
Well it depends how you create the rom and what type of ROM you are creating.
If you plan to simply take an already made rom.zip, make a few little modifications, and zip it back up...it obviously isn't very hard, and likewise its not very satisfying.
If you want to compile a rom from source, then its a bit harder than the process above. To be more specific let's first talk about android versions that are officially supported by the desire: froyo, and gingerbread. Compiling roms based on those honestly isn't that hard. You just need some basic Linux/terminal knowledge. The device and kernel source is actually meant to work by default so you don't need to make any further adjustments. It as simple as opening terminal, downloading the source, and running a build command. Give it an hour (more or less depending on how food your PC is) and you should have a freshly made ROM that you built from source. Yay...some satisfaction.
The hardest thing in my opinion (I've tried all three of these) is compiling a rom based on an android version that isn't officially supported by the desire. (Ice cream sandwich or jellybean). With roms based on these android versions you will have to scour to internet for a working device, vendor and kernel tree. (Hint, hint: WoH and evervolv/nikez). Even once you get the right device tree it probably won't work. You will have to make further adjustments, and even then I'm sure you will be bombarded with build errors. But eventually once you get it to compile successfully....most satisfying thing ever
So yea thats my answer. Keep in mind that I've tried (and eventually succeeded) with all three of the above, and that I've got quite limited programming knowledge. (2 high school comp sci courses, where I learned some java.)
Sent using xda-developers app
Click to expand...
Click to collapse
htc_desire_luke said:
Thanks for that-
Sound very complicated
I am a webdesigner but have no knowledge of developing.
Wanted to try and build a really good rom to make the desire a really good phone for photography.
I have on my phone your rom and RSK supersense 3.5 rom running - coz I like the camera
and I would like to make a rom to turn it into a photography rom for my phone.
any advice??
Click to expand...
Click to collapse
any software needed ??
htc_desire_luke said:
any software needed ??
Click to expand...
Click to collapse
here is a summary of what you need and main steps, from hd2 forum.. next time do a search before post.
Obviously you have to use a desire device tree.
http://forum.xda-developers.com/showthread.php?t=2488670
There is an entire section dedicated to this subject, found in
creating your own rom
paolo-red1 said:
here is a summary of what you need and main steps, from hd2 forum.. next time do a search before post.
Obviously you have to use a desire device tree.
http://forum.xda-developers.com/showthread.php?t=2488670
Click to expand...
Click to collapse
sound very difficult-
my laptop is running linux and i think 64bits- I am running opensuse 12.1 KDE
but thats all i know
will have to do some more reading on this, I dont think I will be able to just pick it up and go.....
You are kiddin' me
Enviado desde mi HTC Desire
creating your own rom
Jack4L_ said:
You are kiddin' me
Enviado desde mi HTC Desire
Click to expand...
Click to collapse
what do you mean Im kiddin you?
Hallo i watch all this roms... They are all 4.2.2. In the sort time adroid L its out... And i have the big question when we have one real update ??? I have this phone 9 months until now i live in eu
gkm8123 said:
Hallo i watch all this roms... They are all 4.2.2. In the sort time adroid L its out... And i have the big question when we have one real update ??? I have this phone 9 months until now i live in eu
Click to expand...
Click to collapse
100% agree but unfortunately duo to mate 2 is out they have no plan to update mate1 to 4.3 or 4.4:crying:
i really think ham is good phablet and deserve better support from manufacturer.
mazi_v said:
100% agree but unfortunately duo to mate 2 is out they have no plan to update mate1 to 4.3 or 4.4:crying:
i really think ham is good phablet and deserve better support from manufacturer.
Click to expand...
Click to collapse
This kind of support let me turn away from Huawei. A pitty. But i want decent support. A phone schould get 2 year regular updates. Thats wat a customer deserves
Well you'll have to dive deeply into it to do the job of building a custom Android ROM. I just downloaded the kernel sources from the official JB (4.1) release, but I'm not sure how far I can get with that. Some experienced devs here posted that they would need Huawei's sources for KitKat to build a KitKat ROM, but I also have an Ascend P1 and I'm running a custom KitKat CyanogenMod build from the forums here although Huawei only released ICS (4.0) Kernel sources. I will have a try with a custom cross compiling toolchain of mine that I use for my Radxa Rock, but it's quite generic. I'll let you know how far I could get if at all.
Cheers!
The kernel build was successful, but I've simply used Google's latest toolchain (arm-linux-androideabi-4.6-android-4.4.4_r1). I'm now syncing the most recent Android repo, that will take some time. I will try to set everything up to start compiling tomorrow morning or something...
Just in case you want to build the kernel yourself as well: There is an indentation issue in one of Huawei's Makefiles for the touchscreen, you'll see an error message about it if you run the first make according to the README_kernel.txt. You can just add tabs and your file should look like this:
[drivers/huawei/device/touchscreen_Mate/Makefile]
Code:
[COLOR="DarkOrange"]#
# Makefile for the touchscreen drivers.
#
# Each configuration option enables a list of files.
obj-y += synaptics_i2c_rmi.o
obj-y += rmi_dev_6.o
obj-y += rmi_f54_6.o
obj-y += rmi_fw_update_6.o
all:
make -C /lib/modules/$(shell uname -r)/build M=$(PWD) modules
clean:
make -C /lib/modules/$(shell uname -r)/build M=$(PWD) clean[/COLOR]
CyReVolt said:
The kernel build was successful, but I've simply used Google's latest toolchain (arm-linux-androideabi-4.6-android-4.4.4_r1). I'm now syncing the most recent Android repo, that will take some time. I will try to set everything up to start compiling tomorrow morning or something...
Just in case you want to build the kernel yourself as well: There is an indentation issue in one of Huawei's Makefiles for the touchscreen, you'll see an error message about it if you run the first make according to the README_kernel.txt. You can just add tabs and your file should look like this:
[drivers/huawei/device/touchscreen_Mate/Makefile]
Code:
[COLOR="DarkOrange"]#
# Makefile for the touchscreen drivers.
#
# Each configuration option enables a list of files.
obj-y += synaptics_i2c_rmi.o
obj-y += rmi_dev_6.o
obj-y += rmi_f54_6.o
obj-y += rmi_fw_update_6.o
all:
make -C /lib/modules/$(shell uname -r)/build M=$(PWD) modules
clean:
make -C /lib/modules/$(shell uname -r)/build M=$(PWD) clean[/COLOR]
Click to expand...
Click to collapse
A kitkat kernel that would make you in my opinion almost immortal for Mate users
henk_j said:
A kitkat kernel that would make you in my opinion almost immortal for Mate users
Click to expand...
Click to collapse
We'll see, I'm still learning about the stuff, but the chances look quite fair. I've set up the rest of the environment and the build is running now. But I guess it will take some more hours. I usually need about 3.5 hours to build chrome, firefox or libreoffice. AOSP should be similar. I'll see how far it got today evening/night. But for now it looks good, I'm running with -j4 as recommended. ^^
CyReVolt said:
We'll see, I'm still learning about the stuff, but the chances look quite fair. I've set up the rest of the environment and the build is running now. But I guess it will take some more hours. I usually need about 3.5 hours to build chrome, firefox or libreoffice. AOSP should be similar. I'll see how far it got today evening/night. But for now it looks good, I'm running with -j4 as recommended. ^^
Click to expand...
Click to collapse
if you have more cores processor why dont increase the thread value so that build process will complete more quickly
svvv said:
if you have more cores processor why dont increase the thread value so that build process will complete more quickly
Click to expand...
Click to collapse
I have 2 cores, so 4 is quite fine. The next option would have been 16.
Take your time! we need more developers
Any news ?
Really appreciate the works here.
so many had forgotten Mate 1 and P6 since 2 & 7 came out...
For me the first editions are always the best although the the 2nd might have little differences or improvements (but always have flaws or bugs more than the 1st editions)..
so very much grateful and thanks for devs that spent their time looking at mate 1 and p6...
Will donate if theres any need for it..count on me for that..
[email protected]
gkm8123 said:
Any news ?
Click to expand...
Click to collapse
Come on, I'm writing every couple of hours...
Well, the news is: v8 failed in some point. I've just resynced the AOSP repo to start over. ^^ I'll let you know how it went today evening. I also have a job, you know.
CyReVolt said:
Come on, I'm writing every couple of hours...
Well, the news is: v8 failed in some point. I've just resynced the AOSP repo to start over. ^^ I'll let you know how it went today evening. I also have a job, you know.
Click to expand...
Click to collapse
Ok no problem, thank so much for your help
Well, the newer patches didn't resolve the issue so I decided to try the normal user build (I tried a full debug build first). For now it looks very promising. I'm not sure if I can figure out how to to fix the issue I had, so if this one fails at the same point (although as far as I understood it was one of the debug parts so it shouldn't), it might get a little harder. We'll see ^^
thank you mate.. i mean CyReVolt.
i hope ur doing ok with ur job also,, and really hope u give us a good news..
cumanisengdoang said:
thank you mate.. i mean CyReVolt.
i hope ur doing ok with ur job also,, and really hope u give us a good news..
Click to expand...
Click to collapse
Sure, np... actually, it failed again due to the same problem, and I quickly figured out the cause (I already had suspected that): I'm on a strongly hardened Linux system, and the
Code:
mksnapshot
tool was killed due to NX protection (see http://wiki.gentoo.org/wiki/Hardened/PaX_Quickstart#Understanding_PaX). So if you're running a PaX protected kernel or similar you might run into the same issue. Duh... -.-
It's up and running again, so let's wait for a result!
While waiting you can try the Android kernel I have attached. Don't ask me how to do that. I have no clue. This is just for fun. And for you!
Considering work: It was actually quite funny today because I had to work on a Mac and OSX feels just horrible to me. My boss asked me to take a glance at Xcode and especially the new beta and Swift. I'm so glad to be back at my Linux machine now.
CyReVolt said:
Well you'll have to dive deeply into it to do the job of building a custom Android ROM. I just downloaded the kernel sources from the official JB (4.1) release, but I'm not sure how far I can get with that. Some experienced devs here posted that they would need Huawei's sources for KitKat to build a KitKat ROM, but I also have an Ascend P1 and I'm running a custom KitKat CyanogenMod build from the forums here although Huawei only released ICS (4.0) Kernel sources. I will have a try with a custom cross compiling toolchain of mine that I use for my Radxa Rock, but it's quite generic. I'll let you know how far I could get if at all.
Cheers!
Click to expand...
Click to collapse
The main problem is not the kernel. We can build a kitkat rom with the 3.0.8 kernel , but we have no source for display part , audio part. We have to use the prebuilt hwcomposer , grallloc etc. . These prebuilt libs are compatible only with the android version of the stock rom they are coming from and with the kernel they are patched for.
With sources of display driver we can patch the kernel and the driver to work on KK . Like I did JB on ZTE V11,V71,V55 tablet with 2.6.35 kernel , but that device was QC based device with available display driver sources. (http://forum.xda-developers.com/showthread.php?t=1629630)
I have compiled a 4.3 rom for mate , but I am stuck at display. There are changed routines in framework which are not working with 4.2's display drivers . One solution can be to get these sources , or to change the framework to work with the 4.2' display driver.
The Mate is my first non QC chipset based device , but also the last too. This is my fourth device from Huawei and until now I was satisfied , they simply do not care Mate customers. The release of the KK for Mate is just a few hours job , but they wont do it.
joe.stone said:
The main problem is not the kernel. We can build a kitkat rom with the 3.0.8 kernel , but we have no source for display part , audio part. We have to use the prebuilt hwcomposer , grallloc etc. . These prebuilt libs are compatible only with the android version of the stock rom they are coming from and with the kernel they are patched for.
With sources of display driver we can patch the kernel and the driver to work on KK . Like I did JB on ZTE V11,V71,V55 tablet with 2.6.35 kernel , but that device was QC based device with available display driver sources. (http://forum.xda-developers.com/showthread.php?t=1629630)
I have compiled a 4.3 rom for mate , but I am stuck at display. There are changed routines in framework which are not working with 4.2's display drivers . One solution can be to get these sources , or to change the framework to work with the 4.2' display driver.
The Mate is my first non QC chipset based device , but also the last too. This is my fourth device from Huawei and until now I was satisfied , they simply do not care Mate customers. The release of the KK for Mate is just a few hours job , but they wont do it.
Click to expand...
Click to collapse
Thats why we have to get some sense into their heads thats trough they're Wallet. The only way tot make them do this strangely by hurting them where it counts.
Alright, I'm getting the point now... so I did some research.
The GPU is a Vivante GC4000, so might this help https://github.com/laanwj/etna_viv ?
I wouldn't mind the sound at first. I would love to work on this somehow.
Can you point out which files I should look at? I know a bit about the ARM/Thumb ISA, so I'd try to reverse engineer a little to either adjust the pre-built drivers or the framework using them. =) I don't give up very quickly, you know! Finally, I'd just contact Huawei and talk straight to them. Thanks in advance for all your efforts.
Cheers
CyReVolt