Database Develop

[ROM][Gingerbread] 2.3.2 | Clean Android | AOSP | Joestone

ALL CREDITS GO TO JOESTONE
This is the AOSP of Joestone
He made a version of Gingerbread for our phone.
This version is clean, so no cyanogenmod, just Android
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is a topic where joestone writes daily updates about his project:
http://logout.hu/bejegyzes/joestone/joestone_gt540_2_3/friss.html
This on other forums:
Android Forum PL
4pda.ru Forum
If you have other links from forums, please post it!
What is working:
Wifi,
Audio
GSM , mms send and receive, automatic apn setup, mobilinternet
Bluetooth
Sensors
Camera
SD card
USB connection
Google market , gmail
GPS, aGPS
Root
APP2SD
FMradio
What is not working:
PCSUITE
Screen calibiration
Fixes in newest verison
DSP Manager is working
iptables and tuneling enabled in the kernel
the default cpu clock was changed to 600 MHz
the cardiotrainer app (and hopefully all others which gave maps error) works
Hopefully increased speed for wifi , hsdpa, umts
the kernel was updated by the lg's source released on 2011.04.12.
Click to expand...
Click to collapse
Some more screenshots of this version:
Download Link
Posted 05-22-11 so 22 May
For fastboot -> ginger....zip
For recovery -> recovery....zip
Video of first version: http://www.youtube.com/watch?v=cQNOJqLyuT0
_________________
For fastboot installation
Code:
fastboot -w
fastboot erase boot
fastboot erase system
fastboot flash boot boot.img
fastboot flash system system.img
fastboot reboot
This is a video of a earlier version so it is just for the impression. In the version in this topic is much more working http://www.youtube.com/watch?v=9z5u8d_Db6o

According to the benchmark results this ones a lot faster right?
Sent from my GT540 using XDA App

I haven't try a benchmark yet but I can tell you because it is still in development it's not totaly smooth.
Joost

Ok
Sent from my GT540 using XDA App

What kernel is this based on? My hope is he's recompiling the (I think 2.6.35?) kernel native to Gingerbread, rather than the other ROM's which have been using a variation on the original LG 2.6.29 kernel. If so, I'd hope we can port that kernel over to CM7.

themono said:
What kernel is this based on? My hope is he's recompiling the (I think 2.6.35?) kernel native to Gingerbread, rather than the other ROM's which have been using a variation on the original LG 2.6.29 kernel. If so, I'd hope we can port that kernel over to CM7.
Click to expand...
Click to collapse
As you can see on one of the screenshots, this is still kenrel 2.6.29. A few russian are making kernel 2.6.35 http://4pda.ru/forum/index.php?showtopic=215440
Joost

Cool, I'll try it when it has more functions working.

joostvhoek said:
As you can see on one of the screenshots, this is still kenrel 2.6.29. A few russian are making kernel 2.6.35 http://4pda.ru/forum/index.php?showtopic=215440
Joost
Click to expand...
Click to collapse
Thanks Joost. Looking forward to seeing the results of that Russian work.

How lucky are we?! Seriously, to have two projects working to bring Gingerbread to the GT540... I bought mine mid December 2010 with 1.6 installed and look at us now...

great job, just don't give up

fishears said:
How lucky are we?! Seriously, to have two projects working to bring Gingerbread to the GT540... I bought mine mid December 2010 with 1.6 installed and look at us now...
Click to expand...
Click to collapse
We have got the east european guys!! WHahahahah (evil laughing)
Joost

I have added a youtube video in the startpost.
Joost

As soon as this is into the Beta stages I will use it, still in alpha stages at the moment am I correct? I want off of CM7 if I'm honest, I just love stock things.

keewanchoapsss said:
As soon as this is into the Beta stages I will use it, still in alpha stages at the moment am I correct? I want off of CM7 if I'm honest, I just love stock things.
Click to expand...
Click to collapse
I don't know in wich stage it is. I call it pre-beta... It is no more alpha because pretty much is working.
Joost

I will get this version as soon as more things are improved.I liked the CM7 version but the battery problem caused too much problems for me.I hope this version will get improved as soon as possible.

Keep up the good work!

I'll try it
Glad to know that enybody else try tot do something with our phone.
But I dont undrstand what is benefit of original android. But as alternative that cool to see a difference between stuf. Would be cool if someone third try to make a CAF version. I think it has a more perfomanse responsibilities and many impruvements.
Keep up the work, good luck.

fishears said:
How lucky are we?! Seriously, to have two projects working to bring Gingerbread to the GT540... I bought mine mid December 2010 with 1.6 installed and look at us now...
Click to expand...
Click to collapse
I think I got mine at about the same time too. Kudos to the developers of both versions of gingerbread.

fishears said:
How lucky are we?! Seriously, to have two projects working to bring Gingerbread to the GT540
Click to expand...
Click to collapse
Agree. Amazing really, especially considering how old the hardware is, not supporting flash, etc. At least with 2.3 we have some hope of using some of the newer apps.
themono said:
My hope is he's recompiling the (I think 2.6.35?) kernel native to Gingerbread, rather than the other ROM's which have been using a variation on the original LG 2.6.29 kernel
Click to expand...
Click to collapse
Good if its easy but just like compiling kernels on linux, newer kernels cause some big headaches with drivers. I'd rather have the older kernel and have it working correctly then wait for the newer kernel to function properly.
Anything in the newer kernel that we need/want?

First of all yes this is an advantage of having 2.3.1 aswell but its hard to put in words.
second can i ask when would it be updated to the latest 2.3.3 from aosp?
third i got the phone on 28 sept 2010 and on that day was my birthday and also on that day joestone released the rootgt540!
look at the progress of openetna and you will realise that we will get new kernels, just that we need to establish a fully working rom first.
what is CAF?

[Dev] ICS Kernel Source code is out!

Hi All,
Devs, kernel and buildroot for ics is up on gitorious!
Let's the fun begin!
Cheers,
LeTama
*** edit ***
Oups, missed previous thread on the topic, sorry djnilse, my damn browser didn't refresh properly. Mods, you can remove the thread or I can keep if for any custom kernel release

so this is where the fun begins

letama said:
Hi All,
Devs, kernel and buildroot for ics is up on gitorious!
Let's the fun begin!
Cheers,
LeTama
*** edit ***
Oups, missed previous thread on the topic, sorry djnilse, my damn browser didn't refresh properly. Mods, you can remove the thread or I can keep if for any custom kernel release
Click to expand...
Click to collapse
its ok
and i agree: let the fun (and headaches) begin

hi letama do you remember me? I'm a mobile programmer I don't know what's usually modded in a kernel used for custom firmwares, but if you need help or testing or need to check code, I can do that
let's rock!

does this mean proper custom roms are now possible as opposed to stock roms with busybox and superuser

letama said:
Hi All,
Devs, kernel and buildroot for ics is up on gitorious!
Let's the fun begin!
Cheers,
LeTama
*** edit ***
Oups, missed previous thread on the topic, sorry djnilse, my damn browser didn't refresh properly. Mods, you can remove the thread or I can keep if for any custom kernel release
Click to expand...
Click to collapse
HI!
Thank you very much Master !
Almost certainly will need your help....for release custom kernel ! Good luck professor !!!

philmein said:
does this mean proper custom roms are now possible as opposed to stock roms with busybox and superuser
Click to expand...
Click to collapse
No, it's not related. Custom roms were already possible without kernel source, I tried cm9 for instance.
The problem with Archos is that it's not really worth it. Custom to do what? Archos firmware is quite "stock", no bloat to remove, so aosp is quite similar and doesn't bring much.
CM9 is in major work, it's going to be interesting soon but it will require lot's of work to adapt it and make it as stable as stock firmware. It's not too difficult to get basic stuff when mixed with proprietary binaries.
Kernel sources are interesting to:
- learn kernel stuff
- overclock / add governors
- add missing drivers (dvb cards, etc...)
- port to gen8 devices
- debug problems like wifi for instance (bad example, this one will be tough).

great letama !
many works now !

Great news! Now waiting for Ubuntu with the new kernel, WiFi and video hw fully employed. I'm a poor programmer myself but if there is a bug in the software I always run straight into it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(And they are always there, of course.) So I think there will be a lot of them to be found.

letama said:
Kernel sources are interesting to:
- learn kernel stuff
- overclock / add governors
- add missing drivers (dvb cards, etc...)
- port to gen8 devices
- debug problems like wifi for instance (bad example, this one will be tough).
Click to expand...
Click to collapse
-develop a way to copy new modules to .ext4 system image (and make a backup
of this file to /mnt/storage)

letama said:
No, it's not related. Custom roms were already possible without kernel source, I tried cm9 for instance.
The problem with Archos is that it's not really worth it. Custom to do what? Archos firmware is quite "stock", no bloat to remove, so aosp is quite similar and doesn't bring much.
CM9 is in major work, it's going to be interesting soon but it will require lot's of work to adapt it and make it as stable as stock firmware. It's not too difficult to get basic stuff when mixed with proprietary binaries.
Kernel sources are interesting to:
- learn kernel stuff
- overclock / add governors
- add missing drivers (dvb cards, etc...)
- port to gen8 devices
- debug problems like wifi for instance (bad example, this one will be tough).
Click to expand...
Click to collapse
Archos' fw is quite "stock" but it's slower than other ICS firmwares...
I have a Transformer with ICS here, and it's definitely smoother (less lag) than my G9 101..
And it's not a CPU/GPU difference

faenil said:
Archos' fw is quite "stock" but it's slower than other ICS firmwares...
I have a Transformer with ICS here, and it's definitely smoother (less lag) than my G9 101..
And it's not a CPU/GPU difference
Click to expand...
Click to collapse
Agreed, but don't forget memory difference... I'm convinced that it kills omap4 perfs. I guess we'll see with the new turbo 1G.
Anyway, some news back on the subject, overclocking is very easy on this kernel to go from 1G -> 1.2 "standard way" with governors that can be handled by setcpu or other. It seems stable, didn't run extensive tests though.

letama said:
Agreed, but don't forget memory difference... I'm convinced that it kills omap4 perfs. I guess we'll see with the new turbo 1G.
Anyway, some news back on the subject, overclocking is very easy on this kernel to go from 1G -> 1.2 "standard way" with governors that can be handled by setcpu or other. It seems stable, didn't run extensive tests though.
Click to expand...
Click to collapse
yeah, the RAM...
good news about the overclock anyway

[KERNEL]HydraCoreNirvana n16[ENDED]

Although this kernel is ended. I think I should put the downloads here:
http://sourceforge.net/projects/maxfuacm/files/Kernel/HydraNirvana/GT-N7000/
Critical Remind:
Flashing this kernel will make your phone Lose Warranty. So please Fully Get Understand of what you are doing. I have no responsibility of any of your lose by flashing this.
Before you download and flash, to farthest avoid bootloop or bricking your phone, please make sure you have read and understand sections from 4 to end.
Please be wisely use the "search this thread" at the top right corner, if you can not see it, click
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
there. And be sure you have already read the OP. New-asked-but-already-answered questions will be ignored and maybe disliked or even scoffed by other members.
I will never talk about ETAs (Estimated Time of Arrival). So please save your keyboard or touchscreen.
Please forgive me if I did not answer your question, even you asked before some one I answered. Please informe with message if you need me to answer it. Although I can not guarantee I will answer questions promptly, the carefulness of the answers is guaranteed. If the answer is important to you, please bookmark it cause I may edit the answer post with update instead of posting another one.
And if anyone don't like any part of my word. Please send me a message instead of posting here. All words above are my begging for the nattiness of this thread. I won't open another thread of discussion, cause I saw the discussion theads were mostly useless. Holding one thread is easier.
Thanks to:
@g.lewarne, @hardcore, @chandler929, @Formhault, @androidindian, @noteandfound, @chasmodo, @TeamHacksung, @samsung, @CyanogenMod team, ......,
and a lot of names to add.
Brief:
First, I would like to thank the people I mentioned and not mentioned in section 2. Notably g.lewarne, you are always the owner of HydraCore. Thank you for your great work. Galaxy Note now became a legend with your masterpiece.
Secondly, I would like to thank all people who gave me support, encourage and advise. Under your help, HydraCore has became a really universal and almost perfect kernel.
In this new thread, the legendary Universal Kernel has a new name -- HydraCoreNirvana. I think the word Nirvana can tell the story of HydraCore. With the new name, the kernel steped onto a new stage -- bootable on JB leaks. It is not fully functional, but it is a good beginning.
I have to say that I am not a dev. And I am another Child's Slave who use lavatory time as off hours. I really don’t know how far I can go on this. So please, forgive me if someday I got stuck and be absent like Gavin.
......long after n6......
For a long time I kept absent. I really found it hard to go on especially after the CM team upgraded the Mali driver. I am not the right guy to do the library job. So I switched to Samsung Opensource codes.
The first thing I did was building the Speedmod. I succussed. Meanwhile I made a build with Speedmod kernel image and PhilZ touch recovery initramfs. These builds worked fine with new released TouchWiz Jelly Beans. However, the CM code is going away with the Samsung Opensource codes. There are too many differences between them. The HOME button key issue was one result of this. It is harder and harder to combine CM and TouchWiz in one kernel. It is not just an universal initramfs, the kernel image itself needs to be universalized.
So I have to make a lamentable decision that from now on, I will stick with Samsung Opensource codes. So TouchWiz Jelly Beans will be supported prior to CM and other AOSP roms which have good enough kernels. Legacy features of HydraCore will be transplanted to the new builds one by one with careful test. CM and other AOSP roms maybe bootable with the new builds, but the functionality will not be guaranteed.
At last, thank you all for your long time support. I will keep on building this kernel and try my best to keep it Hydra for everyone. But for now, I can only step on one side, and I choose TouchWiz.
......more to add......
Technical Description:
Safety: mem_cap_erase disabled, so this is a safe kernel.
ROM Support:
ICS (4.0.X):
TouchWiz Based: TouchWiz ICS fully supported. Official MIUI still can not boot to system, adb works.
AOSP Based: CM9 fully supported, AOKP and some PA......, and maybe other untested roms.
JB (4.1.X):
TouchWiz Based: TouchWiz JB, MIUI made by TWJB + Patchrom from http://www.miui.com/extra.php?mod=download/rom&fid=133 fully supported.
AOSP Based: CM10 fully supported, AOKP and some PA......, and maybe other untested roms.
JB (4.2.X):
TouchWiz Based: Not out even leaked yet
AOSP Based: CM10.1 has bootloop with display.
Recovery: CWM 6 non touch recovery from @Phil3759: http://forum.xda-developers.com/showthread.php?t=1927097.
Root privilege: ADB and LBE superuser.
Usage:
Place the ZIP in the TF card.
Root the phone: If you and if you are sure that you have a safe kernel with CWM jume to next. If you phone is unrooted, Flash the TAR version in Odin to get Root and CWM.
Now you may meet bootloop, Press UP + HOME + POWER until you see the CWM interface. (the phone will never boot to the system with a stock rom flashed a TAR version)
Flash the ZIP in CWM.
Enjoy
Please don't ask me how to use CWM. If you don't know, don't flash any kernel.
Download with Changelog:
Instructions:
These are SourceForge folders, so open in a browser. The corresponding source is included in the same folder.
Not all releases will be kept in this post, find the old ones in the repository. I will keep all files as long as possible. (It seems SourceForge don't delete old files.)
Little trick: maybe you can try middle-click the links, a new tab maybe opened.
Notice: If you met black screen or bootloop after flashing the tar file. Try the zip package (The recovery should be working). The standalong Mali libraries might fix the problem.
n16:
Download: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n16/
Changelog:
Kernel: Pushed kernel version to 3.0.83.
Defconfig: Reverted pmem settings to fix video overlap. The bug is reported fixed.
Defconfig: Reenabled Samsung MTP. The hang of the MTP software on my MIUI v5 TouchWiz Patchrom fixed.
Makefile: Brought more legacy HydraCore tweaks including cpu and fpu tweaks.
n15:
Download: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n15/
Changelog:
Kernel: Pushed kernel version to 3.0.82.
Network: Fixed wifi tethering.
Audio: Fixed mic in software like talking animals, recoders, etc.
Mali: Tweaked thresholds to reduce lag on some heavy interface like MIUI desktop. Further tweaks may be needed.
Tweaks: Some small tweaks.
Platform: Switched to coLinux. Now it is ideal for me. It is a real linux like vmware, it uses less resource like cygwin, and it is fast like a directly installed linux.
Toolchain: Switched back to Linaro 4.7 with LTO.
n14:
Download: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n14/
Changelog:
Kernel: Pushed kernel version to 3.0.81 with cma port.
Superuser: Switched to LBE superuser with some simple permission management.
Defconfig: Brought more legacy HydraCore options which may be not noticeable.
HydraFS: Some workaround to MIUI. Now official MIUI v4 can boot to adb, positive. But the system is still not usable.
Platform: Switched to cygwin.
Toolchain: Switched to cygwin 4.6.3.
Filename: Yes, X.Y.Fu is still me, it is my name in short.
test builds:
Link: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Testbuild/
These builds are test builds. They usually contains new features or fixes. These changes need test. Read the README file in folders for more information.
build environment:
Link: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Platform/
Just follow the readme file.
TODO and TOFIX:
Add Multi-ROM-on-SdCard support.
Investigate the reason of the CM10 and CM10.1 failure boot.
Make MIUI v4 bootable. Fix CM boot problems.
AOSP MIUI JB support.
Bring back more HydraCore features.
Bring ability to set GPU frequency. This is extremely hard to me.
Bring ability to set CPU voltages. Found the location of the settings. Working on it.
Bring more ability to alter the kernel without reflash.
Tweak all the script included.
Study on offcial source code of JB.
64GB cards. I am not sure. 64GB exceeds Fat32 limitation. and exfat is not supported correctly.
Vibration Strength not alterable on AOSP roms. I am still working on this, maybe compile two different modules will solve the problem.
Q&A Collection:
How to flash: like I said if you don't know how to flash, then don't flash. Or you can read section 4.
Can I flash on ...?: Please get to know you rom type, AOSP or TouchWiz based, then please read section 4.
Bootloop/Freeze/..., help!: please be concrete, I can not answer questions simple like this.
Possible reasons of Black Screen: From n9, standalong Mali libraries are located in the zip. Try to use the zip package. It might fix the problem.
Possible reasons of Bootloop:
Please check your rom type see whether your rom is supported.
Another reason is the unsuppored modules. Look in to /system/lib/modules if it exist. And delete dhd.ko, j4fs.ko, scsi_wait_scan.ko and Si4709_driver.ko if they exist. Deleting dhd.ko may also fix WIFI problem.
Possible reasons of Lag: Check the governor and IO settings. Or maybe just clean the RAM. At last, reboot.
Possible reasons of Freeze: Usually happens after a heavy load work. Try to reboot. Reboot usually works.
...adding...and...collecting...
Old Versions:
n13: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n13/
n12: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n12/
n11: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n11/
n10: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n10/
n9: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n9/
n8: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n8/
n7.JBT: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n7.JBT/
n6.JBT: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n6.JBT/
n5.JBT: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n5.JBT/
n4.JBT: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n4.JBT/
n3.JBT: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n3.JBT/
n2.JBT: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/6th_v7.6.JBT/
n1: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/5th_v7.6.2/

Great maxfu. You have a lot to say and we'd love to listen
Sent from my GT-N7000 using Tapatalk 2

Finally...
ANG.MAHAL.NG.NOTE.KO

maxfu said:
My sixth compilation with experimental TWJB leak support:
https://sourceforge.net/projects/maxfuacm/files/Galaxy Note/MaxFu_HydraCore/v7.6.JBT.1/
Click to expand...
Click to collapse
Seriously? We can finally OC the jb leaks? AWESOME!!!

I guess cm10.1 kernel is next?
ANG.MAHAL.NG.NOTE.KO

It's fantastic, thanks man.

Thanks man a new life for our great Hydracore..............

Another awesome release from Maxfu
thanks man.

Will it really work on JB Leaks ???
M waiting for ur reply ..... ill it really work on JB leaks ??? ( especially latest Ultimate Rom )

Immortal Nerd said:
M waiting for ur reply ..... ill it really work on JB leaks ??? ( especially latest Ultimate Rom )
Click to expand...
Click to collapse
I build this JB support with Ultimate XXLSA, should be OK with XXLSC. But please be in mind that it is experimental. AFAIK the camera service has problem.

Haints said:
Seriously? We can finally OC the jb leaks? AWESOME!!!
Click to expand...
Click to collapse
Yes, you will have OC. But camera maybe gone.

maxfu said:
I build this JB support with Ultimate XXLSA, should be OK with XXLSC. But please be in mind that it is experimental. AFAIK the camera service has problem.
Click to expand...
Click to collapse
Is there any critical problems in the sixth compilation for leaked jb? If not, I well flash this right away
Edit : so the camera is break in the latest kernel? Hmm alright I think I will wait for the next compilation really great work maxfu, thank you for make the hydra core can run in leaked JB :good:

XXLSC Wait,.,
Sent from my GT-N7000 using xda premium

Is video camera, 1080 works for with cm10 rom?
Escaped from cuban Asylum. Cell 462

Should be. But not on CM 10.1
cuba462 said:
Is video camera, 1080 works for with cm10 rom?
Escaped from cuban Asylum. Cell 462
Click to expand...
Click to collapse

Hi maxfu. The original HydraCore 7 is unsupported by the awesome jellybam. This would be?
Sent from my GT-N7000 using xda premium

MaxFu_HydraCore_v7.6.2_OC.zip is corrupted

capu81 said:
MaxFu_HydraCore_v7.6.2_OC.zip is corrupted
Click to expand...
Click to collapse
download it again ?

capu81 said:
MaxFu_HydraCore_v7.6.2_OC.zip is corrupted
Click to expand...
Click to collapse
Have you already checked md5?
ANG.MAHAL.NG.NOTE.KO

noteandfound said:
Have you already checked md5?
Click to expand...
Click to collapse
Oh, yeah, sure, no doubt...

Huawei Ascend P7 Marshmallow Update

Hello,
i have a Huawei Ascend P7 smartphone
i live in the netherlands and iw ondered if there was anyone who already received an ota marshmallow update?
beacuse i read online that huawei posted to update the Huawei ascend p7 in germany already!
so if you have received an ota update for the huawei ascend p7
could you please tell i to me?
als, could you say in wich country you received the OTA UPDATE?

Where did you read this? Link, please.
Sent from my Moto X Force using Tapatalk

Marshmallow for p7? AHAHAHAHAH nice joke mate ??

Celes TheMaskE said:
Marshmallow for p7? AHAHAHAHAH nice joke mate ����
Click to expand...
Click to collapse
Why?.. Is it impossible?

I am from Germany and have a P7 too. The German telecom wrote an article about an update to android 6 but this was a mistake.
There ist no update... And I think there will be also no one. The P7 is too old.

There is hardly any chance that our Huawei ever gets marshmallow, atleast not officially. Also Developers have no interest in this phone and that's why p7 hasn't got marshmallow via a custom rom. Though I'm not a developer, I will try to build CM for this phone in this summer and see what comes out of it.

TheSproker said:
There is hardly any chance that our Huawei ever gets marshmallow, atleast not officially. Also Developers have no interest in this phone and that's why p7 hasn't got marshmallow via a custom rom. Though I'm not a developer, I will try to build CM for this phone in this summer and see what comes out of it.
Click to expand...
Click to collapse
Glad to hear that, hope some developer comes in to build a CM, so the development would go smoother

TheSproker said:
Also Developers have no interest in this phone and that's why p7 hasn't got marshmallow via a custom rom.
Click to expand...
Click to collapse
The problem is not in absence of interest, but in GPU driver. Even though we have Mali GPU, Huawei used HAL from Vivante GPU (legacy of P6).
So until you can't get rid of prebuilt surfaceflinger and Vivante's hwcomposer, you won't be able to build AOSP / CM based custom ROM.

Kostyan_nsk said:
The problem is not in absence of interest, but in GPU driver. Even though we have Mali GPU, Huawei used HAL from Vivante GPU (legacy of P6).
So until you can't get rid of prebuilt surfaceflinger and Vivante's hwcomposer, you won't be able to build AOSP / CM based custom ROM.
Click to expand...
Click to collapse
Well, it's just a matter of some hard work. And since there are not may developers around( like Arca, who quitted developing) willing to commit time for p7, that's why we don't have marshmallow yet. So there is always a workaround, for example the s7 was thought to never even have a kernel not even mentioning the fingerprint, but after a long time a workaround was found by devs. So more devs = success.

You're funny! :laugh:
I'm not going to keep discussing with you, cause you don't understand what you're talking about.
Keep dreamig.

Kostyan_nsk said:
The problem is not in absence of interest, but in GPU driver. Even though we have Mali GPU, Huawei used HAL from Vivante GPU (legacy of P6).
So until you can't get rid of prebuilt surfaceflinger and Vivante's hwcomposer, you won't be able to build AOSP / CM based custom ROM.
Click to expand...
Click to collapse
Hi Kostian, and there is no way to obtain these drivers?

nicolawilco said:
Hi Kostian, and there is no way to obtain these drivers?
Click to expand...
Click to collapse
They are not open source. In AOSP source code hwcomposer has just a skeleton, every vendor implements it by himself. In our case we just don't have any alternative implementation for our SoC except one with Vivante HAL.
I'm trying to apply drivers from other device with Mali-450 GPU, there are couple variants I have not tried yet, but most probably their result will be negative.

Kostyan_nsk said:
The problem is not in absence of interest, but in GPU driver. Even though we have Mali GPU, Huawei used HAL from Vivante GPU (legacy of P6).
So until you can't get rid of prebuilt surfaceflinger and Vivante's hwcomposer, you won't be able to build AOSP / CM based custom ROM.
Click to expand...
Click to collapse
This would certainly explain the piss poor gui performance on our little device. I always knew something fishy was at miss.
Just as an idea. I've read that p8 lite has similar gpu to p7, different soc of course. Would it be possible to extract the gpu fun part from the kernel of p8 lite and transfuse it to p7 kernel? On huawei official site there is an official kernel for p7 made for easy download.... Although I'm guessing the camera would be a major issue.
AOSP really would be (is) a dream.

http://android.corekeygen.xyz/downl...e-for-huawei-ascend-p7-sapphire-edition-9963/
http://marshmallow-tips.net/tips-upgrade-update-huawei-ascend-p7
Is this fake? => Virus

RangerP7 said:
http://android.corekeygen.xyz/downl...e-for-huawei-ascend-p7-sapphire-edition-9963/
http://marshmallow-tips.net/tips-upgrade-update-huawei-ascend-p7
Is this fake? => Virus
Click to expand...
Click to collapse
Fake

TheSproker said:
There is hardly any chance that our Huawei ever gets marshmallow, atleast not officially. Also Developers have no interest in this phone and that's why p7 hasn't got marshmallow via a custom rom. Though I'm not a developer, I will try to build CM for this phone in this summer and see what comes out of it.
Click to expand...
Click to collapse
Good luck mate...
Sent from my PE-TL10 using XDA-Developers mobile app

not possible

adammohammed2014 said:
not possible
Click to expand...
Click to collapse
It's possible.
I'm still not giving up.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

hello, when do you think it will be possible to try this rom? thank you

nicolawilco said:
hello, when do you think it will be possible to try this rom? thank you
Click to expand...
Click to collapse
friends I regret to say that despite the efforts of the developers to try to have this optimized device to finish, if we think about it, it has been 1 year without recovery updates and kernels.

[WIP] Wayland, libhybris (Plasma Mobile, Mer, Sailfish OS..)

Hi,
so, this would be the perfect linux phone. If. only. I. could. get. this. to. bloody. work. :crying:
So, I've built a kernel to enable linux containers and booted a plasma mobile system. But the screen stays black. No way to get something to display on the framebuffer. Something is broken. Why does libhybris fail? No idea.
Code:
[email protected]:/home/phablet# test_egl
Segmentation fault
Why can I not get anything to draw on the framebuffer? No idea.
Code:
cat /dev/urandom > /dev/graphics/fb0
XDG_RUNTIME_DIR=/home/phablet weston --tty=0 --backend=fbdev-backend.so --device=/dev/graphics/fb0
And so on.
This needs someone more qualified than me. Maybe we can collect bounties or something? I chip in with 50€ for a running wayland client. :good:
UPDATE 2017-03-24:
Things are coming along better than I hoped. :laugh:
Tony Lindgren et al. and TheKit both independently have wayland running on this device, with mainline (4.12) support nearing completion, and SailfishOS on the other hand successfully driving most hardware via libhybris on a 3.0.8 kernel atop a LineageOS 14.1. base. Kudos! :laugh:
Linux OMAP mailing list: http://www.spinics.net/lists/linux-omap/
SailfishOS local_manifest_maserati.xml: https://gist.github.com/NotKit/95ec76f4eff149e61753ae467f613cbe

Good luck porting a genuine Linux OS to this phone. The keyboard is excellent for semi desktop use. Android is nice but native Linux would be sweet.

I'd just like to wish you good luck with this too.
I don't know how relevant this is, and you've probably seen it anyway, but there's a thread on Maemo about porting Salifish to the Droid 4 (though it doesn't sound like much is happening), but someone there might have some ideas?
https://talk.maemo.org/showthread.php?t=91305

Luck ain't gonna cut it, neither is talking. This needs an experienced developer capable of debugging, distro-building and kernel patching. Perhaps @Mentor.37, @joojoobee666, @Hashcode, @stargo .. or we could collect money to give this phone to another interested developer.
It is not an easy process but very doable for someone with the right experience and skill set. Now how about some substantial encouragement? As said, I chip in at 50€ for any running wayland client. Who else is in
EDIT: Hell what, not that I am wealthy but I am raising to a 100€. Hundred bucks. Who's up for the challenge

FYI,
All of the latest branches for Wayland, libhybris, etc use the DRM API for rendering. (Look at Linux kernels 3.10+). This is probably why you're seeing a segmentation fault as those nodes don't exist in our 3.0 kernel setup.
To add to this complexity you would need new OMAP4430 PVR binaries built for DRM to match up with said newer kernel. (Our kernel GPU blobs use the framebuffer API in 3.0 kernel).
- Hash

Hashcode said:
the DRM API […] don't exist in our 3.0 kernel setup.
Click to expand...
Click to collapse
Mr. Tony Lindgren is working on upstreaming patches to bring up the device on mainline kernel, but that project is in its infancy.
Hashcode said:
To add to this complexity you would need new OMAP4430 PVR binaries built for DRM to match up with said newer kernel. (Our kernel GPU blobs use the framebuffer API in 3.0 kernel).
Click to expand...
Click to collapse
Now that's basically a death sentence for this idea, isn't it? https://github.com/robtaylor/pvr-omap4-dkms is not going to be of much help, eh? :crying:

eMPee584 said:
Mr. Tony Lindgren is working on upstreaming patches to bring up the device on mainline kernel, but that project is in its infancy.
Now that's basically a death sentence for this idea, isn't it? https://github.com/robtaylor/pvr-omap4-dkms is not going to be of much help, eh? :crying:
Click to expand...
Click to collapse
Yes, unfortunately the robtaylor github is based on PVR version 1.9.2166536 which is about 4 years old now. :/

Hashcode said:
Yes, unfortunately the robtaylor github is based on PVR version 1.9.2166536 which is about 4 years old now. :/
Click to expand...
Click to collapse
I think the pyra tree has sgx working for omap3 and omap5, including tiler for omap5 so that might be usable for some omap4 patches too?
Regarding the droid 4 mainline kernel status, I'm still hoping to get the PMIC core support merged for v4.11. Then I have a regulator driver working and and a basic USB and UART multiplexing driver. Those need still cleaning up before posting though. The pending TI LMU patchset seems to get the LCD backlight working for the lm3532, and now I'm trying to get the LCD working for fun :laugh: I guess it should work with omapdrm and panel-dsi-cm with some modifications. Anyways, hoping to be posting more patches over next few weeks and some kernel test branch to play with.

tmlind said:
I think the pyra tree has sgx working for omap3 and omap5, including tiler for omap5 so that might be usable for some omap4 patches too?
Regarding the droid 4 mainline kernel status, I'm still hoping to get the PMIC core support merged for v4.11. Then I have a regulator driver working and and a basic USB and UART multiplexing driver. Those need still cleaning up before posting though. The pending TI LMU patchset seems to get the LCD backlight working for the lm3532, and now I'm trying to get the LCD working for fun :laugh: I guess it should work with omapdrm and panel-dsi-cm with some modifications. Anyways, hoping to be posting more patches over next few weeks and some kernel test branch to play with.
Click to expand...
Click to collapse
OK got the LCD console working last night That's with omapdrm with most of the kernel.org sre/linux-n900.git patches in n950-display branch. I still have some pixelclock getting miscalculated issues and need to clean up things, but then should be able to post a test branch to play with. No idea what it might take to get the rest of the accelerated graphics going but hopefully others people can take it from there.

tmlind said:
OK got the LCD console working last night That's with omapdrm with most of the kernel.org sre/linux-n900.git patches in n950-display branch. I still have some pixelclock getting miscalculated issues and need to clean up things, but then should be able to post a test branch to play with. No idea what it might take to get the rest of the accelerated graphics going but hopefully others people can take it from there.
Click to expand...
Click to collapse
Not very usable at least with just omapdrm.. But still a fun test
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 22:34 ---------- Previous post was at 22:09 ----------
eMPee584 said:
Why can I not get anything to draw on the framebuffer? No idea.
Code:
cat /dev/urandom > /dev/graphics/fb0
XDG_RUNTIME_DIR=/home/phablet weston --tty=0 --backend=fbdev-backend.so --device=/dev/graphics/fb0
And so on.
This needs someone more qualified than me. Maybe we can collect bounties or something? I chip in with 50€ for a running wayland client. :good:
Click to expand...
Click to collapse
My guess is that the dss kernel driver is missing LCD command mode flush based on the framedone interrupt if nothing shows up.
Won't help with the segfault though.

tmlind said:
Not very usable at least with just omapdrm.. But still a fun test
OK finally posted the WIP patches I'm using against Linux next currently at droid4-wip-next-20170203:
http://muru.com/linux/d4/patches/
What works currently is MMC, eMMC, WLAN, keyboard, LCD and touchscreen. For UART,
you need the custom cable and make sure VBUS is not connected.
Click to expand...
Click to collapse

wayland jackpot
tmlind said:
Click to expand...
Click to collapse
ultra. you earn half the bounty for firing up wayland, along with https://forum.xda-developers.com/showpost.php?p=71138243&postcount=18 . :good:

eMPee584 said:
ultra. you earn half the bounty for firing up wayland, along with https://forum.xda-developers.com/showpost.php?p=71138243&postcount=18 . :good:
Click to expand...
Click to collapse
Hey thanks and sorry for the long delay in replying, I used it to buy some HD docks at $5 each
And just to update the mainline kernel status, audio and display patches are still pending. 3G data works but reboots the system after 10 - 20 minutes.
Sebastian Reichel has some nice pages about that at:
http://elektranox.org/2017/08/0022-droid4/
Then for booting custom distros directly from any partition, please check out utagboot I posted last night at:
https://github.com/tmlind/utagboot
Regards,
Tony

PostmarketOS has made lots of progress in recent weeks, even has the beginnings of a porting wizard. With nearly full mainline support, this shouldn't be too hard to bring up? :fingers-crossed:

eMPee584 said:
PostmarketOS has made lots of progress in recent weeks, even has the beginnings of a porting wizard. With nearly full mainline support, this shouldn't be too hard to bring up? :fingers-crossed:
Click to expand...
Click to collapse
Yeah should be totally doable and fun project, go for it! I've mostly used alpine as my rootfs anyways for past year as it nicely fits to mmcblk1p23
Also looks like the LCD patches are finally getting merged for v4.16.
Then I'm slowly working on getting a 4MB buildroot-kexecboot bootloader image posted that can be flashed to mmcblk1p13.. For legacy v3.0.8 based kernels we have an issue with kexec where the android images depend on SafeStrap configuration being on vfat mmcblk1p25.. I think we should update the LineageOS based images to have initramfs just parse the current root partition from kernel cmdline if available and that way mmcblk1p25 can be reformatted as ext4 and is usable. Anybody got a chance to work on that?
Regards,
Tony

tmlind said:
Then I'm slowly working on getting a 4MB buildroot-kexecboot bootloader image posted that can be flashed to mmcblk1p13.. For legacy v3.0.8 based kernels we have an issue with kexec where the android images depend on SafeStrap configuration being on vfat mmcblk1p25.. I think we should update the LineageOS based images to have initramfs just parse the current root partition from kernel cmdline if available and that way mmcblk1p25 can be reformatted as ext4 and is usable. Anybody got a chance to work on that?
Click to expand...
Click to collapse
OK I managed to get the first version of droid4-kexecboot pushed out if anybody cares to play with it:
https://github.com/tmlind/droid4-kexecboot
Regards,
Tony

tmlind said:
fun project, go for it!
Click to expand...
Click to collapse
no time/concentration to spare, sorry
but nice stuff! s0o looking forward to libre wayland HARDWARE KEYBOARD phones

tmlind said:
OK I managed to get the first version of droid4-kexecboot pushed out if anybody cares to play with it:
https://github.com/tmlind/droid4-kexecboot
Click to expand...
Click to collapse
Just pushed a 2017-12-20 image with v3.0.8 kexec wrapper script fixed if anybody dares to try it.
It might just work for booting a v3.0.8 based image if you also have SafeStrap installed so the initramfs can use the configuration for the active image..
The initramfs still needs to be fixed for droid4-kexecboot to boot images directly on any partition using kernel cmdline if anybody has a chance to work on that.
Booting mainline kernel images with droid4-kexecboot does not have these issues naturally.
Regards,
Tony

tmlind said:
Just pushed a 2017-12-20 image with v3.0.8 kexec wrapper script fixed if anybody dares to try it.
It might just work for booting a v3.0.8 based image if you also have SafeStrap installed so the initramfs can use the configuration for the active image..
The initramfs still needs to be fixed for droid4-kexecboot to boot images directly on any partition using kernel cmdline if anybody has a chance to work on that.
Booting mainline kernel images with droid4-kexecboot does not have these issues naturally.
Regards,
Tony
Click to expand...
Click to collapse
Doesn't seem to work for me.
It boots fine into kexecboot but pressing any key other than the volume keys causes it to freeze.
Sometimes even the volume keys don't work.
Pressing Q works sometimes, causing the screen to go black and stay that way.
Pressing R also works sometimes causing a reboot, everything else does nothing or causes it to freeze.
I don't have an uart connector so I can't get any details on what is happening exactly.
It is interesting though that utagboot does boot into kexecboot considering that it never booted anything else for me.
Ddroid never worked for me since it requires selinux (to install) which is only present in SS 3.75 but the modules don't work in SS 3.75 (segfaults during kexec).
I have to manually load the modules and run kexec from SS 3.72 to get a mainline kernel to boot.

... by the way, NotKit has made good progress in porting postmarketOS to our droid4 using libhybris: https://github.com/postmarketOS/pmbootstrap/pull/1039
This will probably become usable within a couple of weeks, yeah!