yashsingh1/xdaforums huggingface dataset:
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] rodman01:
Yes, I had and have still this problem with some of "my" roms. Could solve it on disco with adding libandroid_server.so and libandroid_runtime.so from a previous build, which was working, to the latest or newest build. Could fix it on F-AOSP with adding the kernel from a previous build to the current. Both are aosp based roms. But I do not have the problem with Paranoid Android rom. Which is wired for me. And I don't have it with CyanideL, RR, but also with bliss rom (which are cm based roms). With bliss rom, also the kernel change hack doesn't work. I cannot get it to boot, regardless what I am trying. This annoys me and makes me crazy....But the reason of this problem, I couldn't find yet. So this hacks are not really satisfying and it could be that tomorrow they might not working anymore. What I have noticed is that the boot.img is now 4.5 MB with nameless kernel included. In previous builds the boot.img had always 4.3 MB. Maybe there is the reason to find? Any help and suggestion or what ever is appreciated from me too, and if I can make a step further I will led you know.

Edit: from bliss I can provide a logcat. Would this perhaps help?
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] aaz03:
Not sure if logcat helps but if you can yes it would be cool.

https://review.slimroms.eu/#/q/project:SlimRoms/android_build Looking on the gerrit for overall changes on the rom and i found these commits that i highly suspect of fcking the build up, all the other changes made since the last working build (july 26) are on other devices or on frameworks, which cannot stop booting that way(or at least not at the samsung screen)

Reverted the one about lzma and the other about factorypackage and launched a build, wait& see
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] rodman01:
Ok fine and thanks, yes thats a good idea. I already reverted this 2 commits too and started a new build- In the meantime I reverted back to 5.1.1 r6 and changed external/chromium_org and libcore, but without success or even a change. I can get it to pass the samsung logo with flashing a certain range of kernels, one after the other and finally it boots up without errors and fc with agni pure 4.4.5 sammy...but if I flash this agni right above the rom then its stucking on bootloop...passed the samsung logo, but not booting up...here attached is a logcat I think from my yesterday tries....maybe it helps and if its only for a new idea where we can look at...
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] aaz03:
i cleaned my ccache so my builds take much more time, could you please try reverting all the commits of 28 july on build/ and retry?

Edit: on your logcats there are errors everywhere but it looks like it has a common problem: Java, try reverting this commit https://review.slimroms.eu/#/c/6532/2/core/main.mk
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] rodman01:
My dirty build with only this 2 commits reverted doesn't change anything....stopping at samsung boot logo....will search for the above commit and restart a new build...

---------- Post added at 02:30 PM ---------- Previous post was at 01:52 PM ----------

No difference....again stucking at samsung logo...and if I flash an older, think 4 weeks old nameless kernel it boots, till android is optimizing and after reaching the 100% it reboots and is bootlooping...
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] aaz03:
It boots? Logcat please?

Well, my own nameless kernel haven't got changes from my side since the last working build i made, and the last update from nameless on the kernel is from june 12 so i really doubt about a kernel issue.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] rodman01:
Yes it boots, but only if I flash the old nameless kernel on top, which is also dated around mid of june I guess...l reverted the build repo back till LVY48C commit...build is just finishing and I will flash this soon.

---------- Post added at 03:10 PM ---------- Previous post was at 02:57 PM ----------

Again no difference, stopping at samsung boot logo....I think the problem is not related to the build repo....how is your new build running, still building or already finished?
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] aaz03:
Still building, finished soon.

I can't see where the problem is if it's not build related, there must be some changes done to the manner of kernel building, the kernel in itself didn't change for a while so it can't be this. Have you tried flashing AGNI pureCM straight after flashing the rom?
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] rodman01:
yes I did, but its the same: not passing the samsung logo...but if I flash the cm kernel from netux (1st post of aicp rom) then it boots but got black screen. Think its vendor/samsung related....but if I flash then the sammy agni kernel on top, it boots, going well till android is updating 100% and bum: reboot and endless bootloob... could it be related to the updater script? That the kernel or something other doesn't meet the right partition anymore? Or selinux? And only the cm kernel rearrange this and got the agni kernel to boot the rom? Just thinking, I know it doesn't make a real sense. And I already compared the updater scripts and found no difference in this direction.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] aaz03:
The last change made to /vendor/ by crazyweasel is from june 11, so way before our problem, i don't think it could be that

EDIT: Flashed latest PureCM on top of my build, booting but bootloop, trying with SMDK version
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] rodman01:
Sure the problem is not vendor related, but I meant its clear that the cm kernel from netux is not working with the crazyweazel blobs, and thats why this kernel gives black screen. But with that kernel the rom passes the samsung logo, which it doesn't, with the inbuild nameless and not with agni kernel. Thats the strange thing for me.

---------- Post added at 03:53 PM ---------- Previous post was at 03:50 PM ----------

Have you also already tried different kernels? I can upload a few of them in flashable zips if you want.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] aaz03:
YAAAAY, it boots now with AGNI SMDK 4.4.5 i got it booting, now we have to figure WHY ? No changes were made to my kernel or to the vendor repo...

EDIT: just checked, no more Settings FC :D
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] rodman01:
wow and cool and gongrats :good:, and you only reverted the lzma and packaging commit? Then I will start a new and clean flash at once....only this 2 commits?

---------- Post added at 04:14 PM ---------- Previous post was at 04:07 PM ----------

Couldn't it be in recovery or else? Why is boot.img now bigger, then in earlier builds? Kernel size remained exact the same, as you said no kernel changes in nameless sources and no changes in crazy weasel....
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] aaz03:
Reverted all the suspicious commits i saw on android/build :silly: but the problem isn't even there

I had a doubt so i checked flashing the build i made BEFORE reverting the commits, i flashed the old one i made yesterday with agni smdk aaand it just booted, the problem is not coming from the commits but from elsewhere.

Could you please upload me an official i9305 kernel from cyanogenmod? (one built from cyanogenmod sources only), nameless kernel isn't based on cm's smdk kernels, i will simply change the base of my kernel if it works
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] rodman01:
I am not building with pur cm kernel, sorry. Sammy RR and Paranoid runs with nameless, normal RR runs with DerTeufel, cyanideL runs with caynide L repo and F-AOSP only runs with a 4 weeks old nameless. Here you can find the mentioned kernels: https://www.androidfilehost.com/?w=files&flid=36386
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] aaz03:
Ok thanks anyway i'm gonna try all those and tell which are working or not
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] rodman01:
The uploaded cm kernel is made by netux and linked in AICP OP: http://xdaforums.com/showpost.php?p=59398633&postcount=1
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] aaz03:
CM-kernel: Samsung Logo

AICP-kernel: Samsung Logo

Nameless-kernel: Samsung Logo

Cyanide-kernel: Samsung Logo

Derteufel-kernel: Samsung Logo

AGNI 4.4.5: bootloop animation

AGNI SMDK 4.4.5: Booting perfectly

Well... looks like i'm gonna have to investigate further... :eek:
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] rodman01:
For me its strange, because your rom is also build with crazyweasel vendor and nameless device tree and so the smdk kernel shouldn't be the best choice, or? Although I already noticed earlier that the last agni smdk kernels are also working with sammy based roms.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] aaz03:
Wait a minute... I'm using F2FS and none of the kernels you provided to me are F2FS ready... then it's pretty normal that they all end on a samsung logo ... I'm quite tired today sorry :silly:
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] rodman01:
ah ok sure, then its a different thing :)...no problem, same here left my bed at 5am, when it was nearly dark outside :).
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] aaz03:
Anyway will try to build a SMDK based kernel and port my personnal changes to it... Thanks a lot for your help
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] rodman01:
you are welcome, but I wasn't of any or much help :(....hopefully you or we could find a solution, because this is driving me crazy since weeks now....it begun with faosp, and I have it now also with blissrom...
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] aaz03:
Ported all my changes to the original CyanogenMod kernel (including f2fs) , hope it works and boots well

EDIT: it's ok if you want to try to include it in your rom [MENTION=4613083]rodman01[/MENTION] , look on my github, if you finish your build before mine just tell me how it goes
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] aaz03:
Cm kernels work with Slim simply because they are CM-Based , for the first build the kernel was the CM-kernel from DerTeufel (now i'm using Nameless's ones because Derteufel's kernel is quite outdated... )

Seems like Slim hasn't finished uploading sources atm, fetch errors...
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] :
AFAIK Slim is not cm based, which is why I was asking earlier why you were going to base on CM and not slim?
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] rodman01:
Thats what I thought too...slim is slim and more aosp related then to cm, isn't it?
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] :
Please correct me if I'm wrong but slimroms, omni, and cm are all separate branches from the aosp tree(technically so is stock samsung) so I don't think making any of these roms is possible with the base from another. (or if possible, not logical)??
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] trubul:
5.1?

How's work going? :)
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] aaz03:
Well seems like Slim have problems on their githubs every time i start a repo sync i get at a moment or another a "fetch error", will build as soon as their sources are disponible i'll have time i'm on holidays
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] aaz03:
Hope you're all ready guys ;)
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] dawidd6:
Yessss, i will test it :) :) :)
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] yogivirus:
hi,

Cool, would like to see a full AOSP rom out for community testing :highfive:

Regards,

yogi
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] rodman01:
How is the build running? Has it finished and how are your first tests?
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] dawidd6:
Yea, how is work going [MENTION=5573054]aaz03[/MENTION]?
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] rodman01:
first check in terminal whether there is no further error above. Sometimes the dtbs error "hides" an other one.....If its the only error, then I have the dbts fix on my dropbox: https://www.dropbox.com/sh/17gg52cqananrm8/AACnPzHw4oDmplKgzZxUQGf3a?dl=0

I found it a couple of times ago but don't remember where the commit is, but I hope you can just copy and paste the files and rename them to just makefile or copy the lines included and paste them all to: kernel/samsung/smdk4412/arch/arm->makefile and

kernel/samsung/smdk4412/arch/arm/boot->makefile
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] aaz03:
Can't count how many times i checked it and no, no errors other than DTBS , at first i was using nameless sources, then i switched to Netux's sources , still the same error , same thing , will try your fix thanks.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] winxuser:
if the dtbs error is the only error in the build then its fine, it will finish compiling, how many jobs are you making it compile with,,, eg -j8
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] aaz03:
----- Making recovery image ------
Copying baseline ramdisk...
Modifying ramdisk contents...
[B]cp: impossible to evaluate «/home/n0aaz/slim/out/target/product/i9305/root/init.recovery.*.rc»: no file or folder of this type
make: [/home/n0aaz/slim/out/target/product/i9305/ramdisk-recovery.img] Error 1 (ignored)[/B]
/home/n0aaz/slim/out/target/product/i9305/recovery.img maxsize=8562048 blocksize=4224 total=5955584 reserve=88704
Made recovery image: /home/n0aaz/slim/out/target/product/i9305/recovery.img
Construct recovery from boot
mkdir -p /home/n0aaz/slim/out/target/product/i9305/obj/PACKAGING/recovery_patch_intermediates/
PATH=/home/n0aaz/slim/out/host/linux-x86/bin:$PATH /home/n0aaz/slim/out/host/linux-x86/bin/imgdiff /home/n0aaz/slim/out/target/product/i9305/boot.img /home/n0aaz/slim/out/target/product/i9305/recovery.img /home/n0aaz/slim/out/target/product/i9305/obj/PACKAGING/recovery_patch_intermediates/recovery_from_boot.p
[B]failed to reconstruct target deflate chunk 1 [(null)]; treating as normal[/B]
chunk 0: type 0 start 0 len 4567050
chunk 1: type 2 start 4567050 len 1362688
chunk 2: type 0 start 5337093 len 2043
Construct patches for 3 chunks...
patch 0 is 208 bytes (of 4567050)
patch 1 is 446670 bytes (of 770043)
patch 2 is 156 bytes (of 2043)
chunk 0: normal ( 0, 4567050) 208
chunk 1: deflate ( 4567050, 1387423) 446670 (null)
chunk 2: normal ( 5954473, 1111) 156

Now i dont have the dtbs error but still the same issue and i think that the main problems are what i bolded, noticed that pure AOSP devices like Asus Fugu had a file init.recovery.fugu.rc but our i9305 doesn't have this
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] rodman01:
I think the kernel file is too big....try it with changing the kernel defconfig maybe you then will get it smaller and the build finish without error....maybe there is much better solution in boardcommonconfig where the filesystem is defined. But I don't know how and to what sizes and settings.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] winxuser:
Also try a fresh build sometimes i have errors during compile. So i make clobber then recompile

---------- Post added at 09:53 PM ---------- Previous post was at 09:52 PM ----------

And does it also stop actual compiling or does it hang.. If it hangs just leave it
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] aaz03:
I always do a clean build, i delete the old /out before each build. This doesn't stop that's the point, it just hangs over and over and during this moment, nothing moves, my RAM usage gets slowly to 100% and the cpu usage isn't moving from 2-3%, it's totally inactive: I can leave it for hours it won't change.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] rodman01:
great many thanks, I will test it as soon as possible :good::highfive:....at the moment I am building bliss with more or less completely changed repos to RR and cyanide and CM blobs or better the muppets blobs...will see whether this will bring a change. But after this I will test your kernel, thanks :cowboy:
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] aaz03:
FUUUUUUUUUUUUUUUUUUUUU, Still the same problem, excepted that this time, it reboots on recovery after a while on the logo.

Still the same solution: AGNi Smdk...
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] rodman01:
gggrrrrr how angry, I know how this is feeling....lets see what my try is giving with the cm based bliss rom. Although I think it won't bring us further to a solution for your slim and my faosp....rom is still building...
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] aaz03:
New try with CM vendor blobs from TheMuppets aaaand... it fails again with the same reboot to recovery and the same agni fix...
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Obeca:
Where can i find the settings for themes and the charging up to 1200 mAh?
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] rodman01:
Same here new build with smdk blobs failed, but also flashing agni on top doesn't help. Only flashing cm kernel from netux behind led it boot. But getting bootloop after optimizing apps. Flashing the same kernel (DerTeufel) whih is included in the rom build, it led the rom start without problems. Wifi is not working and maybe other things too, which I don't know yet....I don't understand this all :crying: :confused:

---------- Post added at 07:33 AM ---------- Previous post was at 07:27 AM ----------

After flashing agni smdk on top again, everything is fine....

I have started a new build with your cm kernel from source, I am looking forward to seeing which surprises are now present :)
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Mrxyzl:
Slimrom does not use cm theme engine so you have to download the layer app from playstore then download some layers and apply layer from there.

The charging current in latest build is already at 1200mah, i believe:good:
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] rodman01:
[MENTION=5573054]aaz03[/MENTION] I am getting build errors with your cm kernel: init.recovery.*.rc not possible, file or folder not found and recovery.img too large. Do you have an idea what I have to change?
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] hexisg:
I hope you can make it work as it should with the latest sources....this rom is , and i hope it will be , among the best there are for I9305.

Thank you for your hard work.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] aaz03:
Just go to smdk4412-common and change the max allowed size for recovery in boardcommonconfig
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Obeca:
Just installed layers manager and vivid colorwhite installer rro and getting error, "Unfortunately, Layers has stopped."
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] aaz03:
You must be using an old layers theme, since a recent update of overlay manager, you don't need installers anymore, the installed theme is shown as a module in the manager.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] rodman01:
Had you have to do it the same way for your build? I am wondering because this error does not occur with your nameless based kernel and also not with DerTeufel or nameless kernel. :confused:And what is the max size possible and allowed for that partition or recovery?

Btw: for my latest test build, I removed the rom block building from makefile, but again with no effect....stopped at Samsung logo :(....so block building with the imgs .dats etc seems also not causing our problem....
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] aaz03:
Always have done in that way. We don't care about recovery size because actually flashing a rom on our device doesn't replace the existing recovery, it's just a fix to get the build to finish

Actually i suspect Selinux to be the thing that makes the difference between AGNI and cyanogen kernel
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] rodman01:
Can you try: open your new rom zip and replace boot.img with one of your previous built boot.imgs, one from when the rom was still booting?

I did that with my latest rom builds (block and with out block) based on smdk blobs. Inside kernel is DerTeufel and I replaced boot.img by an other DerTeufel boot.img built for normal RR a couple of days ago. And it is working now: booting and starting, passing the setup wizard without problems or errors.

---------- Post added at 02:35 PM ---------- Previous post was at 02:31 PM ----------

But its not working just and only flashing the kernel zip on top. Its only working when I replace and include it in the rom zip itself.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Obeca:
Sorry I dont understand, how or where could I select the theme since you said that I should not install anything?
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] aaz03:
Will try while home, thanks for the advice, it means that there have been some changes in the way boot.img is built

You install the themes from play store as usually but you don't need to launch the downloaded theme's installer, newest themes are as for Cm, not launchable, you just have to enable them in manager
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] rodman01:
I am quite sure that there are changes....as mentioned before: boot.img from nameless is now: 4.5Mb instead of 4.3 in previous builds and also boot.img from DerTeufel is now 5.5MB instead of 5.4 or 5.3 in previous builds.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Obeca:
How would I enable if the layers manager when open is "Unfortunately, layers is stopped"? Sorry, Im new to this
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] aaz03:
Uninstall all theme you have and the manager too and reinstall, you must have an incompatibility between a theme and the manager
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] aaz03:
At least we know that, now we just have to search for which recent repo change messed it all up

Edit could you try building with AGNI as stock kernel? I really want to know if agni is immunised against this bug , if it works, then there is some change in agni that we must port. If not, it is definetly a boot.img issue
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] rodman01:
I tried it, but I got build errors...I cannot remember exactly which one, but I tried to solve them, without success. Something with no config script or run script or so, if I remember right. And I had/have no idea how to do this.. if you can teach me, I can start a build later and post the error...
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Obeca:
Thanks mate! You really is so good! This is the best lollipop rom that I have tried. :good::good::good:
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Mrxyzl:
Installed an app called stage fright detector and found out this rom in vulnerable. Wonder if there will be a fix soon...
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] aaz03:
Stagefright wasn't fixed at the time of my last build, next build coming soon there with 5.1.1_r9 and it looks like, according to the changes operated in libstagefright, that the issue is fixed/going to be fixed soon.

I have to say, for next build there is ~80% chances that with stock kernel you end on samsung bootanimation and the only fix is to use AGNI kernel smdk4x12. No worry no brick, just that the rom isn't booting with stock kernel , as mentionned previously with rodman01

Edit: rom is uploading, as i said, stock kernel doesn't work so go with AGNI, link is on third post.

Edit²: Cyanogen samsung vendor blobs don't like Uber Toolchain, Keyboard not working until you go in keyboard settings and turn on the material switch
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Mrxyzl:
Can i flash over the previous build or do i have to clean install?
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] aaz03:
I will highly recommend clean install as the new build is based on r9 and has plenty of changes
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Mrxyzl:
Thanks, downloading now and will test it soon