Facing Bootloops Anyone Can Help me Out Running Mutanam V5... Boeffla Kernel... I Wipe All Factory Data Then Install nameless Then Flash Gapps.. With Philzz Recovery. Still Getting bootloops 
[ROM][5.1.1][EOL][Lollipop][Official][Nightlies] NamelessROM 2.1
- Thread starter dhiru1602
- Start date
- Status
Bootloops :/
I have the same
Facing Bootloops Anyone Can Help me Out Running Mutanam V5... Boeffla Kernel... I Wipe All Factory Data Then Install nameless Then Flash Gapps.. With Philzz Recovery. Still Getting bootloops
I have the same
Yes, you face the same problem because both of you obviously didn't read the thread.
As far as I remember there was a similar bug with signal bars at beginning of cm11. Look in settings about phone and look at the signal intensity.
---------- Post added at 11:15 PM ---------- Previous post was at 11:09 PM ----------
Yes. Today I started from zero, and all needed patches for i9300 are there.
Nah, not everything is public. For example patches to opt telephony are missing.
Ohhh. I'm so disappointed
Had to go back to CM11. Will there be any update of this soon? Or....dead?
Don't say that man you need to read both cm12 and nameless thread to know actually what's going on. These days some of the stuff about each thread is found on the other one.
Guys, I have a good news to share. Apparently the N7100 kernel rebase proved to be good and I have some change of plans with the HWC. Initial tests were very promising and it is the first time in years that my S3 was able to match the performance of my Nexus 4.
It has been a known fact that the HWC on our device was doing nothing and it was a mere placebo. However, that is not the case now. We have managed to get full functionality out of HWC and here are few examples.
In the above example, you can notice that the Wallpaper is being composed by the HWC. The Original size of the wallpaper is 1600x1256, which is quite oversized for our device, but the HWC takes care of the resizing to match the screen size. This makes the wallpaper looks much more neat and the overall performance of the launcher is greatly improved.
In the above image, you can see that the video playback is performed using HWC. It's a Full HD video which is resized using the HWC to match the screen size. The SurfaceView that displays the video content is being composed by the HWC instead of using GLES as it was the case before. Using HWC to compose video content improves battery life during video streaming and playback.
The performance has greatly improved especially during scrolling in certain places. There are few bugs which which prevent proper functioning of the device especially at times when the screen decides to go completely blank, which we are currently looking into. I would like to thank @tdcfpp for his outstanding work when it comes to ARM disassembly and his work with the Opensource Gralloc. Without his contributions, things wouldn't have moved forward. I am glad that he had not given up on his S3 and decided to buy another S3 even when his device broke . :good:
I am currently on a long awaited vacation and I cannot work on anything until the end of next week. However, I have pushed all of the sources regardless of the change in plans with HWC. I will consider having a new development branch with includes a rebased kernel along with few changes for the HWC and I will merge the changes to the mainstream when things are in good shape.
Long live S3!
This is the only one reason I am still surfing s3 forum even if I don't have s3
. @tdcfpp, @dhiru1602 : you are best devs here keeping this device alive..
.
for those who are asking for code : ask google to give you android 6.0 source, If they made available to you then ask here for sources..
Not a single dev drop sources of uncompleted project if he/she want to fix it or still working on it..
Neither Google nor Dhiru..
he/she will only share code after his satisfaction of project or he/she tired of working on it and giving up on that project..
.
.
now, yes, lollipop development for i9300 is parted..
AFAIK : Dhiru and Javi, maintainer of i9300 for nameless rom
And : @Moster2, @JustArchi, @arter97 who are working on cm12.
so many asked for teaming up in one.
but there are separate ways for both teams..
Nameless strongly working for openness..
cm12 is working on stable build..
so, they can't be teamed up with different destination, right ?
for example, cm11 removed source build camera HAL and introduced wrapper for camera using stock precompiled lib..
but nameless guys still on open hal of camera..
Javi and Dhiru are in touch for almost year, after this such long time they are able do such real development here..
they really hard working devs here, not just working around issues..
As dhiru, former member of TeamHackSung, made Galaxy SL fully open source device same as for lg p970..
and Javi, Expert is arm disassembly, made open source gralloc ( and many things going on locally), fixed very annoying after call battery ..
these are too much experienced devs..
.
as I remember, two years ago, Javier was just a normal dev who was compiling roms and understanding logs and fixing normal issues..
now look where he is : fixing hwc with Dhiru : historical moment in s3 development..
.
Let dhiru publish his sources after fixing things, then other devs like @JustArchi, @Moster2 take a look on source then they will also help to fix some remaining on unseen problem, then there will be true teamwork..
we need just more time and there will be one devs union in s3 section..
.
every one of them is important here..
thanks for keeping this device alive..
Sorry if I said something wrong..
.
suing dev for source or any other thing only make him stop development for this device, so think before pointing dev..
.
Last edited:
Oh wowThis is the only one reason I am still surfing s3 forum even if I don't have s3
. @tdcfpp, @dhiru1602 : you are best devs here keeping this device alive..
.
for those who are asking for code : ask google to give you android 6.0 source, If they made available to you then ask here for sources..
Not a single dev drop sources of uncompleted project if he/she want to fix it or still working on it..
Neither Google nor Dhiru..
he/she will only share code after his satisfaction of project or he/she tired of working on it and giving up on that project..
.
.
now, yes, lollipop development for i9300 is parted..
AFAIK : Dhiru and Javi, maintainer of i9300 for nameless rom
And : @Moster2, @JustArchi, @arter97 who are working on cm12.
so many asked for teaming up in one.
but there are separate ways for both teams..
Nameless strongly working for openness..
cm12 is working on stable build..
so, they can't be teamed up with different destination, right ?
for example, cm11 removed source build camera HAL and introduced wrapper for camera using stock precompiled lib..
but nameless guys still on open hal of camera..
Javi and Dhiru are in touch for almost year, after this such long time they are able do such real development here..
they really hard working devs here, not just working around issues..
As dhiru, former member of TeamHackSung, made Galaxy SL fully open source device same as for lg p970..
and Javi, Expert is arm disassembly, made open source gralloc ( and many things going on locally), fixed very annoying after call battery ..
these are too much experienced devs..
.
Now for @Moster2, @JustArchi : they are devs, but not as experienced as dhiru and javi, they are still learning lot of things..
as I remember, two years ago, Javier was just a normal dev who was compiling roms and understanding logs and fixing normal issues..
now look where he is : fixing hwc with Dhiru : historical moment in s3 development..
same will go with archi, moster etc after year, maybe they will be in place of Javier. and Javier, Dhiru maybe retired from this device..
but right now : let them be on their own..
.
I am neither praising Dhiru, Javi not insulting Archi, Moster2..
every one of them is important here..
just real facts here..
thanks for keeping this device alive..
Sorry if I said something wrong..
.
suing dev for source or any other thing only make him stop development for this device, so think before pointing dev..
.
Sent from my handphone, not yours
Dhiru got the hwc blob with all it's dependencies working. The only thing not working are some full screen games.
Guys, I have a good news to share. Apparently the N7100 kernel rebase proved to be good and I have some change of plans with the HWC. Initial tests were very promising and it is the first time in years that my S3 was able to match the performance of my Nexus 4.
It has been a known fact that the HWC on our device was doing nothing and it was a mere placebo. However, that is not the case now. We have managed to get full functionality out of HWC and here are few examples.
In the above example, you can notice that the Wallpaper is being composed by the HWC. The Original size of the wallpaper is 1600x1256, which is quite oversized for our device, but the HWC takes care of the resizing to match the screen size. This makes the wallpaper looks much more neat and the overall performance of the launcher is greatly improved.
In the above image, you can see that the video playback is performed using HWC. It's a Full HD video which is resized using the HWC to match the screen size. The SurfaceView that displays the video content is being composed by the HWC instead of using GLES as it was the case before. Using HWC to compose video content improves battery life during video streaming and playback.
The performance has greatly improved especially during scrolling in certain places. There are few bugs which which prevent proper functioning of the device especially at times when the screen decides to go completely blank, which we are currently looking into. I would like to thank @tdcfpp for his outstanding work when it comes to ARM disassembly and his work with the Opensource Gralloc. Without his contributions, things wouldn't have moved forward. I am glad that he had not given up on his S3 and decided to buy another S3 even when his device broke . :good:
I am currently on a long awaited vacation and I cannot work on anything until the end of next week. However, I have pushed all of the sources regardless of the change in plans with HWC. I will consider having a new development branch with includes a rebased kernel along with few changes for the HWC and I will merge the changes to the mainstream when things are in good shape.
Long live S3!
That's fantastic.. nice work!
The only thing I was not liking on AOSPs was the lack of proper graphics support.
Nameless brought a first working HWC for AOSP, and I'm really glad this is now taken to the next level.
And I also got some questions :
1. Is the "fence" source in s3cfb properly working?
A few custom kernels out there which is already based on other Exynos 4412 devices that got a KitKat update(such as N7100 & E210) had an issue with fencing with the new s3cfb source. @Moster2 got a workaround, explicitly disabling fencing completely. I'm curious to see if fencing works with your awesome progress..
2. Will the new HWC properly work with Samsung's Mali r3p2?
I actually doubt it will, but several users of my kernel report that NamelessROM(KitKat) works perfectly fine with my kernel with just the Mali blobs changed(including libMali, libUMP). I'm wondering if using Samsung's Mali r3p2 will break anything with the new HWC.
Seems to work properly with the stock n7100 kernel. But I'll have a look when I have time. Do you know how to reproduce the fence issue?
Yes
https://github.com/ArchiDroid/ArchiKernel/commit/88e64b4f8a61f8bc8d92e9ac8df9d8071084105c
If your kernel source contains ifdefed parts and doesn't cause graphical glitches, it works fine with fences.
And is that a lot of work to get working or is that unknown?
How is the memory management ?.In AOSP ROM Ram issue is plaguing since beginning.
Without support of a surfaceflinger expert, it can be very hard.
---------- Post added at 06:49 PM ---------- Previous post was at 06:47 PM ----------
Well, then I'm 95% sure that fences do work.
There where some artifacts caused by a bug in UMP, but I think I've fixed them.
---------- Post added at 07:02 PM ---------- Previous post was at 06:49 PM ----------
Look here:
https://github.com/NamelessRom/android_hardware_samsung_slsi_exynos4/tree/android-4.4/libgralloc_ump
https://github.com/NamelessRom/android_hardware_samsung_slsi_exynos4/tree/android-4.4/libUMP
Last edited:
- Status
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
307
What is NamelessROM?
NamelessROM Gerrit Review
ANNOUNCEMENT: We are looking for Device Maintainers to expand our support, please visit our IRC channel or PM @Evisceration, or @dhiru1602 for information.
Disclaimer
Got a bug report? Want to request a feature? Need extended support?
Installation Instructions
Contributions and Credit
Downloads
189Guys, I have a good news to share. Apparently the N7100 kernel rebase proved to be good and I have some change of plans with the HWC. Initial tests were very promising and it is the first time in years that my S3 was able to match the performance of my Nexus 4.
It has been a known fact that the HWC on our device was doing nothing and it was a mere placebo. However, that is not the case now. We have managed to get full functionality out of HWC and here are few examples.
In the above example, you can notice that the Wallpaper is being composed by the HWC. The Original size of the wallpaper is 1600x1256, which is quite oversized for our device, but the HWC takes care of the resizing to match the screen size. This makes the wallpaper looks much more neat and the overall performance of the launcher is greatly improved.
In the above image, you can see that the video playback is performed using HWC. It's a Full HD video which is resized using the HWC to match the screen size. The SurfaceView that displays the video content is being composed by the HWC instead of using GLES as it was the case before. Using HWC to compose video content improves battery life during video streaming and playback.
The performance has greatly improved especially during scrolling in certain places. There are few bugs which which prevent proper functioning of the device especially at times when the screen decides to go completely blank, which we are currently looking into. I would like to thank @tdcfpp for his outstanding work when it comes to ARM disassembly and his work with the Opensource Gralloc. Without his contributions, things wouldn't have moved forward. I am glad that he had not given up on his S3 and decided to buy another S3 even when his device broke . :good:
I am currently on a long awaited vacation and I cannot work on anything until the end of next week. However, I have pushed all of the sources regardless of the change in plans with HWC. I will consider having a new development branch with includes a rebased kernel along with few changes for the HWC and I will merge the changes to the mainstream when things are in good shape.
Long live S3!17355
The link is in the OP. You just need to flash it.
They will be merged when the source is available.
I have fixed mobile data. The fix will be in the next build along with GPS fix and few fixes to prevent reboots.
