Related
so....... yeah. I've been working on this since MoDaCo dropped the Galaxy Nexus rom dump a few days ago. so far...... the phone vibrates when I hit the power button. It showed a boot screen once, and nothing more..... I do not plan on releasing this rom, well, ever. Unless I can get it to boot fully. If/when that happens, I'll post it up if it does, it'll be full of bugs that I probably won't know how to fix, so, sorry
If anyone else wants to try porting and gets it done before me, more power to ya if not, please pray that I at least get to the lockscreen xP
More info when stuff happens
UPDATE: December 11th, 2011, thus far, it boots, but touchscreen still does not work... Will keep trying.
always wanted to do this,
RESERVED
and,
RESERVED AGAIN
thanks you are also there..
tj_style has successfully booted ics sdk on our fih-fbo & ported the touchscreen drivers..
nothing else is working other than that
here's a video-
www.youtube.com/watch?v=_13ikGCviJg
may you should ask him for help..
i think it would more easy porting sdk than the dump porting as system dump is already coded for a device with completly different hardware..
nitindeck said:
thanks you are also there..
tj_style has successfully booted ics sdk on our fih-fbo & ported the touchscreen drivers..
nothing else is working other than that
here's a video-
www.youtube.com/watch?v=_13ikGCviJg
may you should ask him for help..
i think it would more easy porting sdk than the dump porting as system dump is already coded for a device with completly different hardware..
Click to expand...
Click to collapse
true, although the sdk is missing tons of stuff... so i just thought porting this would be easier haha guess not... i mean ive gotten further than most devs, my device at least powers on i think im gonna try a different kernel. maybe tomorrow.... ill report back
great work man keep going on you will get it
Source Code OUT NOW!!
groups.google.com/group/android-building/browse_thread/thread/4f85d9242667a85f?pli=1
nitindeck said:
Source Code OUT NOW!!
groups.google.com/group/android-building/browse_thread/thread/4f85d9242667a85f?pli=1
Click to expand...
Click to collapse
i know ive been working on it since yesterday
ICS ported to HTC G1
ICS has been ported to HTC G1 the first android phone... so it is just matter of time that we could also get it in our device..
http://forum.xda-developers.com/showthread.php?p=19648827
welp, i got it to boot, and it goes to the lockscreen, but then goes into bootloop... and the touchscreen doesnt work...... ah.. lots of work ahead, but i think the hard parts over ill keep updating!!!
keep going man you will get it
ICS Update by Huawei
Huawei U8860 Honor Official ICS Beta Update Released.....I am not a programmer so this might be a DUH! post...but still came across so shared...maybe the great Devs can shed some light..
Specs:
Chipset Qualcomm MSM8255T Snapdragon
CPU 1.4 GHz Scorpion
GPU Adreno 205
News Update: http://bbs.huaweidevice.com/cn/forum/index.php?app=forum&mod=Detail&act=index&id=32441
ICS Update: http://www.huaweidevice.com/cn/technicaIndex.do?method=gotoProductSupport&productId=3826&tb=0
hope it would be fast port coz' m' totally failed
this would be MUCH easier to port, considering propriotary drivers, and the chipset is nearly exactly the same. im gonna work on this when i get home.
I WILL LET YOU KNOW MY PROGRESS TONIGHT STAY TUNED!!!
^ I am tuned to hear updates from you on ICS ............
c_anuraag said:
Huawei U8860 Honor Official ICS Beta Update Released.....I am not a programmer so this might be a DUH! post...but still came across so shared...maybe the great Devs can shed some light..
Specs:
Chipset Qualcomm MSM8255T Snapdragon
CPU 1.4 GHz Scorpion
GPU Adreno 205
News Update: http://bbs.huaweidevice.com/cn/forum/index.php?app=forum&mod=Detail&act=index&id=32441
ICS Update: http://www.huaweidevice.com/cn/technicaIndex.do?method=gotoProductSupport&productId=3826&tb=0
Click to expand...
Click to collapse
More Data Here.....
https://www.codeaurora.org/gitweb/quic/la/?p=kernel/msm.git;a=shortlog;h=refs/heads/msm-3.0
egarly waiting
c_anuraag said:
More Data Here.....
https://www.codeaurora.org/gitweb/quic/la/?p=kernel/msm.git;a=shortlog;h=refs/heads/msm-3.0
Click to expand...
Click to collapse
kernels... i dont know a thing about em.. xD
this is odd....
you download the .zip, inside it goes like this
.zip
u8860IceCream_B863_Kernel2.6.35
dload
UPDATE.APP
if I'm not mistaken, .app is a Mac OSX file extension.... Anyone know how to decompile or extract it on windows? cuz i'm stuck.
alx294 said:
this is odd....
you download the .zip, inside it goes like this
.zip
u8860IceCream_B863_Kernel2.6.35
dload
UPDATE.APP
if I'm not mistaken, .app is a Mac OSX file extension.... Anyone know how to decompile or extract it on windows? cuz i'm stuck.
Click to expand...
Click to collapse
Bro...i was able to use below to extract Update.App using a Perl Script that I found here:
http://android.modaco.com/topic/311344-repacking-updataapp-was-new-version-of-split-updatapl/
I installed Perl from here : http://www.perl.org/get.html#win32
the command : perl split_updata.pl update.app extracts the files recovery.img and system.img along with other files that I have no clue about. However this does throw lots of CRC errors....
I am not a Perl script expert maybe you can look further into that
General informations:
This thread's aim is only to represent a central meeting and discussion point for BCM21553 developers and, in particular, for the open Kernel/ROM sources development for the Samsung Galaxy Pocket GT-S5300 (codenamed Cori).
Information for common users:
As already described in the previous section, if you are not a developer, please restrict your posts to the general discussion thread so that developers can maintain good communication. Every post that is not strictly respecting these rules will be reported to the forum moderators. Thanks for your understanding.
For any other BCM21553 device related question or information, please, use this thread as a reference point, instead:
[DEVS ONLY][BCM21553 series] CyanogenMod 11 for BCM21553 Development Discussion
As someone already might know, I'm streambinder, from MoltenMotherBoard team.
I have already followed some projects for the GT-S5300, but especially kept in contact
with some of the events related to the porting of ROM and Kernel sources for BCM21553 chipset based devices.
In this precise moment, the sources in my possession allow you to be able to compile
a bugfree CWM 5.0.2.8 (based on CyanogenMod 7 code) with a kernel based on the Samsung stock one.
The only - fundamental - problem was due to the fact that unless I hadn't used the prebuilt INIT binary
token in the Samsung stock firmware boot.img, the phone would not work - or, better, boot up.
This means that until the situation - regarding this issue - doesn't change, our access to the porting of custom ROM
would be barred.
Recently, I decided to give Cori another chance and rework my sources, looking at the wonderful work brought
by the BroadcomCM team on CyanogenMod 9 (in particular, thanks to @bieltv.3 and @Alberto96) and @psyke83 on CyanogenMod 11.
They've not only been able to run these two ROMs in a more or less crude way, but this developer has been able to write
the necessary strings to make the INIT binary of some of these BCM21553 devices opensource.
Strong of this informations, I readjusted some of the sources of BroadcomCM's CyangenMod 9, which includes
all the progress carried out by both the team and psyke83, in order to make them work even on Cori,
and am now next to the first test of the CWM 6.X.X.X, based on IceCreamSandwich code.
At the same time, @akhbh is working on the KitKat code based CWM.
I hope I can give more information about any progress as soon as possible.
The General Discussion thread for non-development issues is here:
*.[DISCUSSION] CyanogenMod 11 For Galaxy Pocket GT-S5300 Discussion Thread
Made a first test of CWM based on CyanogenMod 9 code.
It seems it cannot flash it as it weighs so much compared to its partition configuration value: in fact, the maximum boot partition size is set up to 5.0MB, but the compiled boot.img weighs 5.3MB.
Will have to resize its weight in order to make it fill into the partition.
@akhbh, have you had any complication in these terms, with CyanogenMod 11 sources?
@psyke83, what do you suggest to do? Do you think an increasement of boot partition would be a better idea?
streambinder said:
Made a first test of CWM based on CyanogenMod 9 code.
It seems it cannot flash it as it weighs so much compared to its partition configuration value: in fact, the maximum boot partition size is set up to 5.0MB, but the compiled boot.img weighs 5.3MB.
Will have to resize its weight in order to make it fill into the partition.
@akhbh, have you had any complication in these terms, with CyanogenMod 11 sources?
@psyke83, what do you suggest to do? Do you think an increasement of boot partition would be a better idea?
Click to expand...
Click to collapse
No, I didn't faced those complications. My boot.img weighted around 4.5 MB in lzma compression mode. In gzip, it increased to more than 5 mb.
akhbh said:
No, I didn't faced those complications. My boot.img weighted around 4.5 MB in lzma compression mode. In gzip, it increased to more than 5 mb.
Click to expand...
Click to collapse
Perfect.
Which kernel have you based your build on?
streambinder said:
Perfect.
Which kernel have you based your build on?
Click to expand...
Click to collapse
Well, I took the GeTux kernel for cori, had to change the board name though and then compile it. CWM was booting even before changing the board name but there was no reaction from the phone on trying to boot cm9/cm11
And after changing board name, a black screen on trying to boot
Another info: When tried to merge cori source into the bcm21553 common one, it did compile but gave bootloop of GT-S5300 logo on trying to boot as well as when trying to go in CWM.
Bieltv.3 recommended to use cori source instead of the bcm21553 common one so we used cori sources
akhbh said:
Well, I took the GeTux kernel for cori, had to change the board name though and then compile it. CWM was booting even before changing the board name but there was no reaction from the phone on trying to boot cm9/cm11
And after changing board name, a black screen on trying to boot
Another info: When tried to merge cori source into the bcm21553 common one, it did compile but gave bootloop of GT-S5300 logo on trying to boot as well as when trying to go in CWM.
Bieltv.3 recommended to use cori source instead of the bcm21553 common one so we used cori sources
Click to expand...
Click to collapse
I suggest to use our Kernel sources for now, too: it will automatically bypass few errors/issues/bootloops that we cannot now fight with.
The most important thing is to make INIT working from sources (hope it will be working
on my CM9 sources, too) and check that every our configuration is correctly working and
making Cori boot into recovery.
Once we'll make it perfectly working without any kind of issue, will be the right time to try
to make Cori supported with the BC21553-common kernel.
streambinder said:
I suggest to use our Kernel sources for now, too: it will automatically bypass few errors/issues/bootloops that we cannot now fight with.
The most important thing is to make INIT working from sources (hope it will be working
on my CM9 sources, too) and check that every our configuration is correctly working and
making Cori boot into recovery.
Once we'll make it perfectly working without any kind of issue, will be the right time to try
to make Cori supported with the BC21553-common kernel.
Click to expand...
Click to collapse
Okay, I will use your kernel sources and try if something is changed once I reach home. For now, I neither have this device nor a PC, as I'm in another city.
Will be keenly watching your work. Will start after reaching home around the end of September
akhbh said:
Okay, I will use your kernel sources and try if something is changed once I reach home. For now, I neither have this device nor a PC, as I'm in another city.
Will be keenly watching your work. Will start after reaching home around the end of September
Click to expand...
Click to collapse
No problem, mate.
Here you have every source in my possession:
platform_kernel_samsung_cori
platform_device_samsung_cori
Keep in contact with me, as I will need some informations by you.
Anyway I'm now making another build, keeping some not so much important binaries excluded, so that I can make the compiled boot.img fill into our little Cori's boot partition. I know it's a dirty workaround, but if it works, I'll use it untill @psyke83 will suggest me a better way to do.
streambinder said:
No problem, mate.
Here you have every source in my possession:
platform_kernel_samsung_cori | github.com
platform_device_samsung_cori
Keep in contact with me, as I will need some informations by you.
Anyway I'm now making another build, keeping some not so much important binaries excluded, so that I can make the compiled boot.img fill into our little Cori's boot partition. I know it's a dirty workaround, but if it works, I'll use it untill @psyke83 will suggest me a better way to do.
Click to expand...
Click to collapse
have u tried to build cwm v6 from cm9 source ??
cleverior.ipul said:
have u tried to build cwm v6 from cm9 source ??
Click to expand...
Click to collapse
Of course, mate. I'm working on it, right now.
It doesn't seem to boot, strange if the same INIT binary sources are working for @akhbh.
#UPDATE
In order to troubleshoot, I'll give you some info.
For his build I used these sources:
platform_kernel_samsung_cori
platform_device_samsung_cori
android_device_samsung_bcm21553-common
Applied some lines on our bcm21553-bootimg.mk, too, in order to exclude parted and mke2fs and make the compiled boot.img weigh less.
@cleverior.ipul, can you link me your kernel sources, as akhbh said he used your ones for CM11.
@akhbh, which modifies have you applied in order to compile CWM based on CM11 code? Which device tree?
#UPDATE 2
Attached my compiled boot.img.
If anyone of you would extract it (you can easily use this tool: bootimgtools - read how to use it in the README) and make a diff with the CM11 one (just extract the ramdisk of both boot.imgs and - in the terminal - use this command: diff -urN /path/to/cm9/ramdisk /path/to/cm11/ramdisk > diff.patch), would make to me a huge favour.
Let me know.
streambinder said:
Of course, mate. I'm working on it, right now.
It doesn't seem to boot, strange if the same INIT binary sources are working for @akhbh.
#UPDATE
In order to troubleshoot, I'll give you some info.
For his build I used these sources:
platform_kernel_samsung_cori
platform_device_samsung_cori
android_device_samsung_bcm21553-common
Applied some lines on our bcm21553-bootimg.mk, too, in order to exclude parted and mke2fs and make the compiled boot.img weigh less.
@cleverior.ipul, can you link me your kernel sources, as akhbh said he used your ones for CM11.
@akhbh, which modifies have you applied in order to compile CWM based on CM11 code? Which device tree?
#UPDATE 2
Attached my compiled boot.img.
If anyone of you would extract it (you can easily use this tool: bootimgtools - read how to use it in the README) and make a diff with the CM11 one (just extract the ramdisk of both boot.imgs and - in the terminal - use this command: diff -urN /path/to/cm9/ramdisk /path/to/cm11/ramdisk > diff.patch), would make to me a huge favour.
Let me know.
Click to expand...
Click to collapse
I think we didn't had significant changes. Perhaps the same as totoro. But, that resulted in the internal_sd not mounting error in cwm.
Sadly, as said before, I am away from my home city and can't provide the files to you and can't do the boot.img diffs as well
Try to ask psyke83, he might have a solution for that
akhbh said:
I think we didn't had significant changes. Perhaps the same as totoro. But, that resulted in the internal_sd not mounting error in cwm.
Sadly, as said before, I am away from my home city and can't provide the files to you and can't do the boot.img diffs as well
Try to ask psyke83, he might have a solution for that
Click to expand...
Click to collapse
Then, if you didn't make any massive change upon the sources, then I'll only try using your kernel.
Can you give me your kernel sources, mate, please?
streambinder said:
Then, if you didn't make any massive change upon the sources, then I'll only try using your kernel.
Can you give me your kernel sources, mate, please?
Click to expand...
Click to collapse
Currently, I can provide you the boot.img only. For the sources, @cleverior.ipul can provide the kernel sources coz as said earlier, his kernel is used. Well, we were working together to bring cm11 but weren't successful
akhbh said:
Currently, I can provide you the boot.img only. For the sources, @cleverior.ipul can provide the kernel sources.
Click to expand...
Click to collapse
Ok, please send it to me, will compare it with my package.
streambinder said:
Ok, please send it to me, will compare it with my package.
Click to expand...
Click to collapse
Here it is:
http://www.4shared.com/zip/1nKFbOJ2ba/ccccGetux_CM11.html
streambinder said:
Of course, mate. I'm working on it, right now.
It doesn't seem to boot, strange if the same INIT binary sources are working for @akhbh.
#UPDATE
In order to troubleshoot, I'll give you some info.
For his build I used these sources:
platform_kernel_samsung_cori
platform_device_samsung_cori
android_device_samsung_bcm21553-common
Applied some lines on our bcm21553-bootimg.mk, too, in order to exclude parted and mke2fs and make the compiled boot.img weigh less.
@cleverior.ipul, can you link me your kernel sources, as akhbh said he used your ones for CM11.
@akhbh, which modifies have you applied in order to compile CWM based on CM11 code? Which device tree?
#UPDATE 2
Attached my compiled boot.img.
If anyone of you would extract it (you can easily use this tool: bootimgtools - read how to use it in the README) and make a diff with the CM11 one (just extract the ramdisk of both boot.imgs and - in the terminal - use this command: diff -urN /path/to/cm9/ramdisk /path/to/cm11/ramdisk > diff.patch), would make to me a huge favour.
Let me know.
Click to expand...
Click to collapse
here the link source https://github.com/cleverior/android_kernel_samsung_cori
i've changed the board name. If your device can not boot after using the zImage from this source, then rename init.bcm21553.rc to init.gt-s5300.rc.
@streambinder, what is grom? As bieltv.3 said that init built grom for cori is required to fix adb over cwm recovery. If adb gets working, then possibly the black screen while booting cm11 might get fixed
akhbh said:
@streambinder, what is grom? As bieltv.3 said that init built grom for cori is required to fix adb over cwm recovery. If adb gets working, then possibly the black screen while booting cm11 might get fixed
Click to expand...
Click to collapse
Sincerely don't what are you talking about.
Anyway, have to try to understand where's the problem with the not-booting CWM.
Will try with your sources and let you know.
In this post, I would like to explain what kexec-hardboot patch is.
@kernel developers: I would like to ask you to merge this patch to your kernels, because it is essential part of MultiROM - it allows to boot any kernel without changing the boot partition. I realize that it is no small request, but the patch is not big, touches relatively stable parts of kernel and should not cause any problems. Thank you.
What is kexec?
It is syscall of Linux kernel, which allows you to boot another Linux kernel without restarting the device - "Linux boots itself". The functionality is equivalent to fastboot -c *cmdline* boot zImage initrd.img, but without PC and fastboot. It is fairly known thing, so more info at wikipedia and man kexec.
What is the difference between normal and hardboot exec?
Kexec-hardboot patch adds a real device restart to that process, so that all the drivers can be properly reinitialized. It stores new kernel to RAM, reboots the device as usual, and kernel from boot partition immediately jumps to the one which was stored to RAM before reboot.
Unlike grouper's kexec-hardboot patch, this one only requires the host kernel to be patched. This is one of the improvements Tasssadar made, and I think it is pretty significant.
To sumarize the process:
kexec --load-hardboot.... is called and kernel it loaded into RAM.
kexec -e is called. Special info is written to memory (to area which is not overwritten on reboot) and the device is rebooted.
After reboot, very early in the boot process, kernel checks if that special info is present in RAM and if so, it loads new kernel from RAM and jumps to it.
Kexecd' kernel starts and boots.
For more info, read the original thread.
Patches:
Kernel patch: https://gist.github.com/PatrikKT/50faf32e8931d51c0c9a,
This is the kernel patch. Only the host kernel needs to be patched.
Related CONFIG options:
CONFIG_KEXEC=y
CONFIG_KEXEC_HARDBOOT=y
CONFIG_PROC_DEVICETREE=y
CONFIG_ATAGS_PROC=n # This one is turned on automatically, but it is not needed, so you can disable it.
All these options must be enabled.
Userspace kexec binary: https://github.com/Tasssadar/kexec-tools
I had to change some things in kexec userspace binary because of some kernel bugs, complete description is in that repository. You can get statically built binary at https://github.com/Tasssadar/multirom/blob/master/install_zip/prebuilt-installer/multirom/kexec
Usage:
Once you have the kernel patches and kexec userspace binary in place, just run following command to boot into new kernel:
Code:
kexec --load-hardboot zImage --initrd=initrd.img --mem-min=0x20000000 --command-line="$(cat /proc/cmdline)" --dtb
kexec -e
Note the command line parameter - cmdline from bootloader is not added automatically, you have to put it there by yourself.
Authors:
This patch was made by Mike Kasick for Samsung Epic 4G. Since that, it was ported to several devices, one of them is Asus Transformer TF201 - he used patch from TF201 and modified it a bit (basically just changed few SoC specific constants). People at #ubuntu-arm helped him out with that, thanks.
For hammerhead, he has improved the patch a bit - only the host needs to be patched now and he has added support for DTB.
This thread was used as a template Credits to @Tasssadar for his Nexus 5 patch
Awesome people helping with our G2's development. Thank YOU!
patrik.KT said:
I would like to ask you to merge this patch to your kernels, because it is essential part of MultiROM - it allows to boot any kernel without changing the boot partition.
Click to expand...
Click to collapse
What benefit would there be to non-MultiROM users? (Just curious.)
blastagator said:
What benefit would there be to non-MultiROM users? (Just curious.)
Click to expand...
Click to collapse
Any. Just any.
Actually I can't think of anything. It's only to bring the device to a full reboot to load a new kernel.
Odoslané z môjho HTC Desire 601
blastagator said:
What benefit would there be to non-MultiROM users? (Just curious.)
Click to expand...
Click to collapse
Not for common user, in epic4g kexec used by kernel devs to test a new kernel build without replace the existing kernel.
They just load a temporary kernel to test. Then that kernel will gone after a reboot.
Hope to see new kernels that support MultiRom! Great work man!
Would this allow a multiboot with AOSP and Stock roms?
AbdulrahmanAmir said:
it doesnt work while i have stock and the secondary is aosp (dU-dirty.unicorn) when i boot the secondary it works sound only but no display just black screen plzz help
Click to expand...
Click to collapse
The patch is not necessary at the moment, because of the locked bootloader. It's just for devs to be prepared with their kernel when we can unlock the bootloader, so that multirom will work as it should.
Odoslané z môjho HTC Desire 601
Thanks for your great thread. But there is no instruction about how we can add that patch to kernel source. Could you write more details about implanting this patch?
No response??
mohamaadhosein said:
No response??
Click to expand...
Click to collapse
Download the patch file from first post and place it in the kernel root directory. Then you should use this command to check if there are any conflicts: git apply --check <path_to>.patch
If there are no errors, use this to apply: git apply <path_to>.patch
Sorry for the late response but I checked xda when I wasn't home and I forgot to reply when I got home
Odoslané z môjho HTC Desire 601
Hey, some changes need to be made to the patch.
On line 353, change the number from 22 to 21. Also, it has some errors when modifying head.S, which I had to fix manually..
But guys, my kernel is building with the latest multirom. This **** is going to maybe work soon!
I'll keep you all posted.
Thank you man
Guys, I think I've done it. Kexec hardboot patched kernel for 5.1.1 and thus multirom compliant, which I am preparing to build with twrp. this is very exciting.
When will it be ready?
Are you kidding me? No ETAs. I literally haven't even announce it yet and somebody asks for an ETA.... It will be ready once I test everything to boot well on my device.
patrik.KT said:
Download the patch file from first post and place it in the kernel root directory. Then you should use this command to check if there are any conflicts: git apply --check <path_to>.patch
If there are no errors, use this to apply: git apply <path_to>.patch
Sorry for the late response but I checked xda when I wasn't home and I forgot to reply when I got home
Odoslané z môjho HTC Desire 601
Click to expand...
Click to collapse
It says the patch is corrupted on the line 375
Warning: Use this on you Own Risk
Features:
S2W D2W
Stereo Call Record
GPU Tweak
NO Write Protection for System Partition
AWB LCD Custom Color for .Rec 709 Profile
Few little Code Changes
How to:
Load boot.img into fastboot folder
run this command:
"fastboot boot thedreamer-Desire510-64bit.img"
When the Device Boot UP and is Stable
Flash the boot.img with:
"Fastboot flash boot thedreamer-Desire510-64bit.img
Download:
http://forum.xda-developers.com/devdb/project/?id=8179#downloads
Source:
GitHub
I Give no Support i make this Kernels Only for me and post it for other 64bit MSM8919 User to Use.
I Integrate only my Wishes
XDA:DevDB Information
TheDreamer, Kernel for the HTC Desire 510
Contributors
Thestealth2, thestealth2, RBHeromax
Source Code: https://github.com/thestealth131205/HTC_Desire_510_64bit
Kernel Special Features:
Version Information
Status: Stable
Stable Release Date: 2015-02-10
Created 2015-02-10
Last Updated 2015-02-10
I'd love to try it. Is there a link to download it please?
Burtrum57 said:
I'd love to try it. Is there a link to download it please?
Click to expand...
Click to collapse
thanks for the source it coould prove useful in compiling a custom rom for the 64bit i may have to re sync the cm11 repo and give it a shot..
could you also provide a link to the boot.img so we dont have compile the kernel lol.. cheers..
excuse me if i sound stupid,but what is "AWB LCD Custom Color for .Rec 709 Profile" actually? is it actual modified screen colors or is it just the custom kcal driver?
Kcal driver. For Rec. 709 Calibration. My display is calibrated with a Colorimeter.
Download is in First Post
Sent from my HTC Desire 510 using XDA Free mobile app
Thestealth2 said:
Kcal driver. For Rec. 709 Calibration. My display is calibrated with a Colorimeter.
Download is in First Post
Sent from my HTC Desire 510 using XDA Free mobile app
Click to expand...
Click to collapse
do you remember which file you modified for the calibration? i would like to apply it to my kernel,i dont wanna bug you :silly:
See source and merge with youre source
Thestealth2 said:
See source and merge with youre source
Click to expand...
Click to collapse
i build for the 32bit,i cant merge a 3.10 kernel with a 3.4 one :silly:
I write you next days a pn. Have no time at the moment.
You can push a 64 bit stock kernel to git an the push my source than can you see all changes. ?
Just a question...
Exactly which toolchain you use to compile??
I'm about ready to flash your kernel - thestealth131205 I'll update after i get my flash on.
Thestealth2 said:
Features:
NO Write Protection for System Partition
AWB LCD Custom Color for .Rec 709 Profile
Few little Code Changes
Download:
http://www.dhm-server.de/thedreamer-Desire510-64bit.img
Source:
GitHub
Click to expand...
Click to collapse
Thank you for your kernel, have been using it for a month (on my EU) and it works very well!
However, could you make some progress please...
As it is seen on this forum your work is the only one for 64bit. So, could you consider some suggestions?
Namely in their 32 verisons of modded kernels developpers write here about improving screen touch responsiveness and removing HTC's backdoor "debugging" access... How about it?
download link unavailable
See first Post
RE: THEDREAMER 64 bit
Thestealth2 said:
See first Post
Click to expand...
Click to collapse
Last I touched base/read with you and RBHEROMAX, if I understood correctly, you were going to be changing something so I've been trying to remain patient and wanted to inquire about this. I picked up a Samsung Galaxy S5 Sport (sprint) all stock to entertain myself with. LOL. I have the utmost respect for you and Rbheromax, I'd like to thank you again for your dedication and time put into this project and the respect and patience you give to everyone that asks you questions on any level. You are very special individuals giving the gift of knowledge to all that seek it.
All that came together to make the 64 bit HTC Desire 510 project. All that came to the rescue to make THEDREAMER possible. You are pioneers and not afraid of a challenge. I don't know if you have any sort of recognition for everyone that takes the time and puts fourth the effort to share the GIFT OF KNOWLEDGE. If not, I'd like to declare Tuesday, March 31, 2015 programmers appreciation day! And you both deserve the GOLDEN THUMBS UP AWARD just because I appreciate your patience, and you caring enough to share knowledge with individuals that otherwise wouldn't have the opportunity to delve into this field.
THANK YOU!
Hopefully I'm not breaking any rules by speaking up. But I. Believe it's time for some recognition with a simple shout out saying THANKS, YOU MADE A DIFFERENCE IN MY LIFE.
paying it forward....
:highfive:
Should the kernel name be "3.10.28-g36bd0f8-dirty (root @ speedstarlap)" after installing?
I'm trying to enable S2W and can't seem to get it working, was wondering if the kernel installed right, or if there were other versions - you said you have MSM8919, whereas my 510 shows up as MSM8916- a typo or actually different chips? (if possible, could you please tell me how to enable S2W if the kernel installed right?)
@edit - Managed to get it... "working" - if I lock the screen and swipe to right and left near the menu buttons within 2-3 seconds from locking, it works. otherwise it doesn't. D2W is fully dead though. I'll poke around it a bit more and see if I can get it to work properly...
Hi, which gcc are u using? and how to compile the dt.img?
I compiled a kernel for D820, only with stock dt.img could bootup. It boots into bootloader if I use the dt.img which I compiled from stock kernel source.
could u help me?
Kernel works great and great improvement in speeds! Thanks
I've a problem. Sometimes the touchscreen doesn't react after waking up my phone. But the volume up and down and the power button work.
Can this be because of the kernel? I don't know. Please help.
Lonely_Boz said:
I've a problem. Sometimes the touchscreen doesn't react after waking up my phone. But the volume up and down and the power button work.
Can this be because of the kernel? I don't know. Please help.
Click to expand...
Click to collapse
I have the exact same problem I have to restart my device for screen to be back in action
USB Driver
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE500CL/ASUS_Android_USB_drivers_for_Windows_20150212.zip
ZE550ML ROM
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550ML/UL-Z008-WW-2.12.40.9-user.zip.secure
ZE551ML ROM
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-2.12.40.9-user.zip.secure
Kernel source
ZE550ML/ZE551ML
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550ML/zenfone2_2_12_40.zip
Great!! Looking forward for great dev support..
Fire code said:
USB Driver
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE500CL/ASUS_Android_USB_drivers_for_Windows_20150212.zip
ZE550ML ROM
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550ML/UL-Z008-WW-2.12.40.9-user.zip.secure
ZE551ML ROM
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-2.12.40.9-user.zip.secure
Kernel source
ZE550ML/ZE551ML
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550ML/zenfone2_2_12_40.zip
Click to expand...
Click to collapse
Links for ZE551ML and ZE550ML ROMs are broken.
BACKUP
Quote:
Originally Posted by Fire code
USB Driver
https://drive.google.com/open?id=0B-1_qo5woThsQkNWQnVwZG9CVzA&authuser=0
ZE550ML ROM
N/A(sorry ~i didn't backup this~ )
ZE551ML ROM
https://drive.google.com/open?id=0B-1_qo5woThsTnM3bjQxaHJoUzg&authuser=0
Kernel source
ZE550ML/ZE551ML
http://dlcdnet.asus.com/pub/ASUS/Zen...e2_2_12_40.zip
https://drive.google.com/open?id=0B-1_qo5woThsOHhkTUNEUFItdFU&authuser=0
I can't wait tell I get this device. Nothing but good old cyanogenmod and aosp roms.
Sent from my SM-T230NU using XDA Free mobile app
Anyone rip any apps out and had success with them running on AOSP yet?
Do you guys think there will be an Ubuntu Touch edition for the ZenFone 2? It has an Intel CPU, I really wish that.
update link
USB Driver:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE500CL/ASUS_Android_USB_drivers_for_Windows_20150212.zip
ZE500CL
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE500CL/UL-ASUS_Z00D-WW-12.16.4.3-user.zip
ZE550ML
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550ML/UL-Z008-WW-2.12.40.11-user.zip
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550ML/UL-Z008-WW-2.12.40.9-user.zip
ZE551ML
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-2.12.40.11-user.zip
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-2.12.40.9-user.zip
hp420 said:
Anyone rip any apps out and had success with them running on AOSP yet?
Click to expand...
Click to collapse
You can get some ZenFone 2 apps From :-
I have deodexed rom.
and ported some apps and they are working flawlessly on CM11 without any bug.
http://forum.xda-developers.com/and...enfone-2-apps-port-root-t3073195#post59906345
ThunderSky7 said:
You can get some ZenFone 2 apps From :-
I have deodexed rom.
and ported some apps and they are working flawlessly on CM11 without any bug.
http://forum.xda-developers.com/and...enfone-2-apps-port-root-t3073195#post59906345
Click to expand...
Click to collapse
Deodexed rom meaning you have a zenfone 2 stock deodexded rom? Do you have a link to it or the rom is private?
You should add screenshots.. :good:
thanks for drivers
sooo much repo'ing to get AOSP before the compiling even begins. There's gotta be a better way for them to maintain the repository. :/
Edit:
After downloading around 40 gigs of files from AOSP, won't compile on our phones. Looks like build tools are only 64-bit and the Debian Jessie chroot I'm using on the phone isn't allowing the 64-bit tools to execute. Our kernel reports that it IS in fact x86_64, but I can't seem to find the phone's /lib64 directory to map to the chroot. So, something that could be fun is now a huge headache -- may need to put together a pc just to build this kernel & hope I still have enough bandwidth from my ISP to repo another 40 gigs.
ycavan said:
sooo much repo'ing to get AOSP before the compiling even begins. There's gotta be a better way for them to maintain the repository. :/
Edit:
After downloading around 40 gigs of files from AOSP, won't compile on our phones. Looks like build tools are only 64-bit and the Debian Jessie chroot I'm using on the phone isn't allowing the 64-bit tools to execute. Our kernel reports that it IS in fact x86_64, but I can't seem to find the phone's /lib64 directory to map to the chroot. So, something that could be fun is now a huge headache -- may need to put together a pc just to build this kernel & hope I still have enough bandwidth from my ISP to repo another 40 gigs.
Click to expand...
Click to collapse
It's already several years ago Android build tools migrated to x64-only. So, you cannot build Android (even 32bit version) on x32 machine.
Zenfone 2 kernel is 64bit. But Android itself is 32bit. You still can start 64bit binaries if you want. I'm using 64bit busybox and some other utilities I've made.
I didn't try to compile Zf2 kernel yet because there is no unlocked bootloader exist, so you simply can't boot your own kernel.
I was able to apt-get lib64 on debian jessie ( was called libc6-amd64 ) & that moved things along until the assembler refused to load libz.so. No amount of looking around helped figure that one out since libz.so did exist.
This is just something fun to do while waiting for the unlocked bootloader. Wouldn't it be nice to be able to just compile your own kernel on your phone?
Compilation requires a lot of typing in command line. I cannot imagine doing this on phone. It's simply crazy. I'm not even talking about time needed for compilation.
I'm using PC (with linux VM) to compile everything.
sorg said:
Compilation requires a lot of typing in command line. I cannot imagine doing this on phone. It's simply crazy. I'm not even talking about time needed for compilation.
I'm using PC (with linux VM) to compile everything.
Click to expand...
Click to collapse
@sorg..so currently is there anything that you have produced for zenfone 2? and is it possible for this phone to be developed once asus release and unlock the BL?
cangcan said:
@sorg..so currently is there anything that you have produced for zenfone 2? and is it possible for this phone to be developed once asus release and unlock the BL?
Click to expand...
Click to collapse
Yes, i've compiled many binaries already.
Of course it's possible to develop for ZF2. There is ASUS Nexsus Player (fugu) device in CM12 repository which is basically very close to ZE550/ZE551. So, there is already a lot of code in Cyanogenmod. But, i prefer stock ROM anyway.
sorg said:
Yes, i've compiled many binaries already.
Of course it's possible to develop for ZF2. There is ASUS Nexsus Player (fugu) device in CM12 repository which is basically very close to ZE550/ZE551. So, there is already a lot of code in Cyanogenmod. But, i prefer stock ROM anyway.
Click to expand...
Click to collapse
That's good news sorg, great to know you've been getting some code flowing while waiting for the bootloader unlock tool.:thumbup: I'll have to check out your repositories when I get the chance, especially since I wanted the device tree for my rom projects.
Sent from the Ace's MB865 using Tapatalk
edit: nvm