yashsingh1/xdaforums huggingface dataset:
[Defy Android Development] TJKV:
Check the md5sum of the ROM zip, it should be df6fa60a7c65679d825cd24354b8c125. Then clean again and flash only the ROM. If home button works then try my minimal gapps, see OP.

EDIT: Sorry the OP is not updated to my minimal gapps thread, it is located here.
[Defy Android Development] UncleDan:
I am really said I cannot use SlimBean which I loved in previous versions. Major bugs are no notifications at all, browser not working and awful slowness in opening apps (while interface is super smooth). I cannot really figure out what is wrong:(
[Defy Android Development] TJKV:
What happens with a fresh flash without gapps or anything else? And what does the logcat look like?
[Defy Android Development] UncleDan:
I will try and report tomorrow
[Defy Android Development] TJKV:
Slimbean Weekly 7.8 is rolling out to official devices, thought I should update for the Defy too. See here for official changes, they've reorganized the Settings screen. For baseband selection, scroll all the way down to Advanced Options -> Device.

Apart from those changes, I've made this (30 step volume like kayant had done) by myself (that is, not an official slimbean change). I also tried to do this but it didn't seem to work, it still takes the torch a few seconds to turn on. Also the strobe effect doesn't happen properly. I think it has to do with the way the torch app is being compiled, not the source of the app. But anyone wanting it to be instantaneous can take the Torch.apk from the latest CM10.1 build and replace in /system/app before flashing in the zip file or after flashing using a root explorer.

About the bugs:

1. Video recording: I flashed just the ROM as it is with no gapps or any other addons, and played with it for a while. Then I recorded a 3 minute video, audio didn't cut. But I had raised the vsels in Bootmenu, earlier I had underclocked it a bit. So upping vsels a bit may be worth a try if anyone has the audio cutting off bug.

2. Reboot to Bootmenu/Recovery: After a fresh flash (ie with full /data and /system wipe), the Advanced Reboot option under Developer Settings will be set to 'Hide on Lockscreen' but it still doesn't show the Advanced (Recovery and Bootmenu) options even when not in the Lockscreen. But changing that option once and changing it back to 'Hide on Lockscreen' fixes it and it starts working normally.

Also after a fresh flash and after fixing the above problem, rebooting to recovery or bootmenu still doesn't seem to work. But this becomes alright after manually going to bootmenu by pressing vol down at the blue LED and then going to TWRP and CWM recoveries. After doing that, next reboot onwards rebooting to bootmenu and recovery (goes to CWM recovery) seems to work just fine. I think I noticed this in CM10.1 too, not too sure.

3. Button backlight brightness of course is still 100%.

The build is uploaded, find it in the link in Post 6.

---------- Post added at 07:57 PM ---------- Previous post was at 07:26 PM ----------

I just tried the AIO Aroma with the new 7.8 weekly build, email app seems to work fine now.
[Defy Android Development] Antiga Prime:
I was thinking, maybe these problems happen due to the way you compile? Could you test with a +5 minute video?

This problem has been going on since a few months back, with all latest CM 10/ 10.1 ROMs.
[Defy Android Development] TJKV:
Not sure what you mean, the actual compiling is just two commands, no other way to do it. But if you mean toolchains etc, I don't know about those really. I guess Kayant's setup is being used for those things, as almost all the repos I use are basically Kayant's, I have just forked them. So maybe he can better answer this :)

About the 5+ minute video, I'll let you know in a while.

EDIT: Okay in a 6:41 video, audio worked until around 6:30. Are you sure it works perfectly in Illusion? I'll try Illusion anyway soon...

EDIT 2: Okay I shot a similar 6:41 video in Illusion, this time the file was half the size as in SB (395MB vs 191MB, 18fps vs 14fps) for the same time length and the audio stopped at around 3:24. So honestly it looks to me like it is a broad problem in all JB roms for our phone, ie Quarx's domain :P

You mentioned media_profiles.xml before, why don't you try editing it to make the video 640x480 and see if it works?
[Defy Android Development] DanielNIX:
Thankx! I just checked and with 7.8 works fine for me too!

The problem with the "charging, discharging" in the lockscreen must be upstream 'cause I tried the english interface and it's correct.

I contacted the developers and explained the problem, we'll see! ;)

edit: suggested the corrected translation on crowdin
[Defy Android Development] level_666:
Illusion v2.5 changelog is amazing, but it's android 4.3, ¿Does this mean that we will have to wait Quarx to get 4.3 working?
[Defy Android Development] thekguy:
You have answered your own question. FYI, answer is yes
[Defy Android Development] dkv2222:
Im on illusion v2.1 now.

I wanna upgrade to slimbean 7.8 (latest) but don't wanna lose all apps

Will a dirty install do?

Cuz the restore process in titanium sucks :/
[Defy Android Development] TJKV:
You can try, but if bugs pop up then you know the source of the bugs.

As for Titanium, you could purchase the pro version or use some other backup app, maybe helium.
[Defy Android Development] dkv2222:
Helium gives me errors with the backup pwd and stuff.

N I can't get the pro version of titanium

So any other solutions?
[Defy Android Development] TJKV:
There might be other backup apps, but this thread's not the place to find them...and like it says in post 6, full wipe and flash is the only recommended way to avoid bugs. So do a dirty flash at your own risk!
[Defy Android Development] dkv2222:
Thanks anyways :)
[Defy Android Development] fabiosarts:
i got problems about radio connection, it sometimes connect, and sometimes i got a null connection, i've tryed to install baseband changer just in case the slim baseband changer could be failing, but i can't see the icon on the app list, i've checked the logcat and all i've found yet it's an reference to rmnet0 device, is that the modem or something like this?

here's the piece of logcat

unable to find stats for iface rmnet0
[Defy Android Development] Antiga Prime:
You need to reboot your phone in an area where there is a good connection, or else you won't get a signal. It's already been happening to me on Illusion and both Slimroms and turning airplane mode on/off does not work. The internal baseband switcher doesn't work, so use this baseband switcher instead, but uninstall whichever one you installed first.

---------- Post added at 12:55 PM ---------- Previous post was at 12:51 PM ----------

Just flashed the latest Slimrom, restored all my apps + data + system configuration, and recorded a 5:04 minute video using the default camera app; the audio did NOT cut :good: Haven't touched default Vsels (just as before) and all HWA is on for EVERYTHING. Beats me as to why it happened on the previous build.
[Defy Android Development] TJKV:
Good to hear. But try after using it for a bit, just to make sure. BTW baseband switcher doesn't work? because it seems to work fine for me, I am able to switch to my SEA basebands just fine. Would you and whoever else it isn't working for try a few different basebands and reboot and see?

As far as I can tell, the different basebands are located in /system/etc/motorola/basebands/*region*/*name*/ in zip files. I think the baseband in use will be extracted to /system/etc/motorola/bp_nvm_default. Comparing these locations between the latest CM10.1 and my latest SB in meld reveals no differences. If anyone is feeling brave maybe they can try replacing the files in bp_nvm_default with their location files from the zip files, at their own risk :P

Oh and I stopped disabling HWA too, honestly I prefer the (probably) slow loading times (though I can't seem to notice any difference) because scrolling is so much smoother when HWA is on. Memory usage isn't a problem too, I anyway don't use too many apps or multitask a lot. There is enough to run maybe three or four apps, like if I use the Upload to Dropbox feature in Titanium Backup it will launch the Dropbox app for me to sign in and grant titanium access, so I have to use KeepassDroid to get the password, and Authenticator for the time based code to login. That's four apps right there...
[Defy Android Development] fabiosarts:
YAY i've tryed an baseband apk i've found on another android forum, instead an flashable zip, works like a charm, i'm currently using illusion too, but if i see it laggy, i'll try slimbean again :D

i've uploaded the apk i've used to fix my signal problem ^^

another question...if i compile systemui.apk or any of these main packages, can i just replace it? or i need to do extra things? like manual dexing and so?

i'm totally newbie with such things, but the fact i can modify the os is the main reason i choose android :)
[Defy Android Development] level_666:
On illusion I've found a couple of bugs: the numbers in the clock app are not aligned, the ksm same paging checkbox and the limit number of processes doesn't save the status after a reboot.

Enviado desde mi MB526 usando Tapatalk 4 Beta
[Defy Android Development] TJKV:
Limit number of processes isn't supposed to save across boots.

Now KSM doesn't seem to be working on SB, maybe on Illusion too. [MENTION=4173406]Kayant[/MENTION], any idea? Also init.d scripts don't load!
[Defy Android Development] Kayant:
Yh that has been an issue since 4.1.2 :p I think the problem is in the vendor_slim... Will look at it later
[Defy Android Development] Walking dead:
so that explains at least some problems one is button backlight.

ran #lsmod command and backlight.ko is not loaded .

manually loaded the module and button brightness is now working as it should be.

su
modprobe backlight
[Defy Android Development] yogesh324:
hi to make ksm work just replace the bootmenu folder in the rom zip with a folder from ur previous build i.e. slim 7.2 thats all i have tested it and its working in illusion rom
[Defy Android Development] TJKV:
Not exactly....

Anyway I diff'd the contents of the ramdisk of CM10.1, where init.d and KSM are working fine against the contents of SB 7.8 ramdisk, found some differences. I edited it, and replaced it in SB 7.8 and backlight brightness control now seems to work, which means that init.d works i guess :)

But ksm still doesn't show up in processes (ksmd), so KSM is still not working properly. I'll test it a bit more and then upload the working build.

if you do the following in adb shell or in terminal emulator, only the pages_to_scan and run values will be non zero, the other values are zero. This means KSM is not working. If the other values are non zero too then KSM is working

for i in /sys/kernel/mm/*ksm*/*; do echo ""; echo -n "$i - "; cat $i; done;

[MENTION=4173406]Kayant[/MENTION], I'm still unable to remember which repo the relevant files are located in, so all I can do right now is edit the ramdisk after the ROM is compiled :p :o
[Defy Android Development] yogesh324:
Well I m not much familiar with linux so I just used this command

cat /sys/kernel/mm/ksm/run

and the result is 1 which means ksm is running... well I maybe wrong as I read the above command on some site after searching through google
[Defy Android Development] TJKV:
Run the command I posted, on SB some values are zero while they are non zero on CM10.1. I think the value of run becomes 1 only because we have enabled KSM in Performance menu, while it actually doesn't work.

I'm not familiar with scripts either, i got that command from zeppelinrox :P
[Defy Android Development] yogesh324:
yes u are right exept for those two other values are zero I guess it's not working.... well I ll be watin for u or Kayant to try fix it thanx
[Defy Android Development] antarix:
[MENTION=4148153]TJKV[/MENTION]. I can't see lock screen mod and some others might be missing as well.

I can't find them in interface.
[Defy Android Development] TJKV:
http://www.slimroms.net

http://www.slimroms.net/images/slimsettings.pdf
[Defy Android Development] Kayant:
Update

It looks like Quarx has got 4.3 working which means it's time for me to set up 4.3 :) ---> https://www.facebook.com/photo.php?...00002190862720&type=1&relevant_count=1&ref=nf

Also [MENTION=4148153]TJKV[/MENTION] is building an update for Slim 7.8 with init.d fixed hopefully. From comparing CM implementation to Slim I have fixed some things and made it move like CM's which should hopefully fix the issue I hope. https://github.com/tejus/android_vendor_slim/pull/1

Also IllusionRom has been rebased to using uXylon ---> http://xdaforums.com/showthread.php?t=2354170

Video ---> http://www.youtube.com/watch?v=qu-oIDZrSlw
[Defy Android Development] UncleDan:
[MENTION=2386803]TKV[/MENTION] you were right. Using your minimal gapps I got SlimBean working!!!
[Defy Android Development] Neurom707:
This means an update for illusion :D ?
[Defy Android Development] F.Ace:
I think after quarx fix all bugs in 4.3, there will an update for illusion.

Sent from my MB526
[Defy Android Development] Neurom707:
Kayant builds illsuion, and i meant because of new base
[Defy Android Development] Kayant:
Yes Yes :) The uXylon base is 4.3 and he has abadoned 4.2 from what I can see so only option is to push forward ;) From what Quarx says I think they 4.3 and 4.2 are pretty much on the same level atm.

[MENTION=4148153]TJKV[/MENTION] How is the build going??
[Defy Android Development] TJKV:
Check your PM, it isn't going anywhere :P

I'm right now testing all my gapps, will upload refreshed ones as soon as I find a good replacement lib for the crashing CM10.2 keyboard (crashes when you swipe)
[Defy Android Development] Kayant:
If you get more errors that are similar just delete the intermediates folder with rm -rf then run make again.
[Defy Android Development] Antiga Prime:
Given that the init scripts were not working, wouldn't that explain why the internal baseband switcher wasn't working, since the "02baseband" file wasn't loading?

In case anyone is interested in getting the backlight buttons to work before any new update, you can create a script with smanager with the code provided by [MENTION=4817189]Walking dead[/MENTION] and set it to run as "su" and "boot".

On a side note, I have recorded already 3 long videos (+5 minutes), the first two were right after flashing the ROM, and the 3rd right after rebooting once I depleted the initial battery charge. On the first two the audio did not cut, on the 3rd the audio before the last 5 seconds of the video. All HWA is enabled, and Vsels have been left on their default value.

EDIT: Just left my phone alone for a few minutes, and when I went to use it I found it turned off. Had to pull the battery in order to turn it back on. Last thing I did was to change the "Surface Improvement" back to "Fix color banding (default)". I had it set to "Disabled".
[Defy Android Development] UncleDan:
Last (very personal) bug of SlmBean 7.8 is that I have... Unknown battery fully loaded!!! I can't charge the phone despite battd being the same of CM10.1 and Xperia D. Any hint? Thanks for your patience.
[Defy Android Development] delight535:
Yes, according to the opening post, they should be on the same level with CM10.1. :) But many people complain about not having the phone.apk in the rom. And somebody wrote that the battery percentage is only showed at 10 percents. And another user said the wifi signal does not turn blue.

These last bugs might be because of some random errors, or they did not wiped data? But the phone.apk is missing for many users. :) That will be fixed by Quarx soon I think.
[Defy Android Development] Kayant:
Phone apk that's a weird one :p.... 10 percent is probably due to the 1% patch being lost during the merge of 4.3 and the WiFi signal am unsure since mine is fine and blue :)

If anyone hasn't tried it I think they should just backup its noticeably smoother( not all apps have been reinstalled and using Blechd0se Kernel)

Edit - Still butterly as before Google have done some major improvements with project butter it would seem
[Defy Android Development] TJKV:
I know right, it's really smooth! And Walter uploaded a Dialer.apk, but I personally use exDialer so not having the stock one is actally convenient :D

Anyway yes I'm using CM's system_extra repo, see my post one page back for the latest status of the build...
[Defy Android Development] delight535:
Thank you for the info. :) I will try 4.3. Maybe it is a stupid question, but will the battery indicator stay this way? Or can you make it show the battery by 1 percents?
[Defy Android Development] Kayant:
[MENTION=4148153]TJKV[/MENTION]

Make clean it is then :( .... If that doesn't work that the Overwork patch is needed..... I will port it again of so.... Time to work on 4.3 stuff :p
[Defy Android Development] TJKV:
make clean doesn't work, I tried that a few times too. Yeah I guess overwork is needed. This one right?
[Defy Android Development] Kayant:
Yh but there are quite a few conflicts ... Do u want to have a go? Or should I do it?
[Defy Android Development] TJKV:
I'll try it, what do you suggest though, cherry pick that commit and then fix any conflicts (those >>>>>>>head things right?) or do it manually as a new commit?

---------- Post added at 03:18 PM ---------- Previous post was at 03:03 PM ----------

Hmm there is a battd backup script in addons.d folder. If you don't mind doing a full wipe flash again then you could try to delete the script (80-battd.sh) and flash. Not sure if it will help or not though, just a hunch.
[Defy Android Development] Kayant:
Cherry-pick and and remove the conflicts (Yh the head things :p) But it's not always the same for each conflicts you may have to remove a bunch of code sometimes or not each conflict is different that's why no tutorial can teach you. You just have to look at the code and compare it to the commit you're cherry-picking and see what needs to go and what needs to stay or be replaced. One last thing leave the code for fastboot/engine.c the same don't change it based on the cherry-pick
[Defy Android Development] TJKV:
Okay about to merge. But I don't think there will be any of those head conflicts, I compared every changed line and checked :P

Only thing I have to do after cherry picking it is to undo the changes to fastboot/engine.c right? EDIT: Okay did that by cherrypicking your commit here :P
[Defy Android Development] Kayant:
Yh good job :) Make sure you're using CM's system extras or will get more fastboot errors :p
[Defy Android Development] Kayant:
Oh yh forgot you need to remove these two

#ifdef __arm__
/*
* b/7188322 - Temporarily revert to the compat memory layout
* to avoid breaking third party apps.
*
* THIS WILL GO AWAY IN A FUTURE ANDROID RELEASE.
*
* http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=7dbaa466
* changes the kernel mapping from bottom up to top-down.
* This breaks some programs which improperly embed
* an out of date copy of Android's linker.
*/
int current = personality(0xffffFFFF);
personality(current | ADDR_COMPAT_LAYOUT);
#endif

Diff'ing my version of the file against the slimroms version, the above section is replaced by the following in slim's version:

umask(077);

umask(077) was removed by Quarx's as one of the patch for system core and the arm one is not in CM and is not needed
[Defy Android Development] delight535:
[MENTION=4148153]TJKV[/MENTION]: I just installed Slimbean (Slim-mb526-4.2.2.build.7.8-UNOFFICIAL-20130728-1557.zip). The first thing I observed is while booting, after the blue LED comes green, instead of red. Is it right, or I messed something up? :)
[Defy Android Development] TJKV:
Nope, that's how it is in all the recent ROMs including the latest CMs. Makes more sense to have it green, like a 'good to go' rather than a red which is more like:

'oops something went wrong, your phone will self destruct in 5 seconds'
[Defy Android Development] delight535:
That's true. :D But since 2ndboot was introduced it was red. And yes, it was strange being red.

Thank you for your answer, and for your work making the roms!
[Defy Android Development] Kayant:
Quarx changed it some time ago when he updated the bootmenu.... And like [MENTION=4148153]TJKV[/MENTION] said it makes more sense this way...

[MENTION=4148153]TJKV[/MENTION] how's the build going?
[Defy Android Development] TJKV:
Done, but still no KSM it would seem :/

But init.d seems to work :)
[Defy Android Development] delight535:
I see, thank you for the info. :)

[MENTION=4148153]TJKV[/MENTION]: Slimbean is amazing. I used Mokee OS 4.2 before that, but Slim seems to be smoother, faster, and maybe more free ram. :) So right now I am very happy with it.

BTW: I saw Recents RAM bar function. What does it do? I enabled it, but do not know where to look for it.
[Defy Android Development] Kayant:
Hmmm so button backlight works like normal then??

I don't know why ksm isn't working (logcat??) because i though it was controlled here ---> https://github.com/tejus/android_vendor_slim/blob/slim4.2/prebuilt/common/etc/init.local.rc

It was in system core before ---> https://github.com/tejus/android_system_core/commit/2c45eb3e4f647a6958085cb08f3d35342d6f3a10

Then moved to local.rc ---> https://github.com/tejus/android_system_core/commit/943dba184eb5c0f46dc70a5db140c5b5ceb4b7a0

So I don't know :p
[Defy Android Development] TJKV:
Yup backlight is normal, not ultra bright :)

Hmm maybe we can ask Blechd0se for help regarding ksm?

But I flashed his 29th July kernel, still no KSM. So not kernel related probably...

I've attached the logcat from boot, if anyone knows what to look for then feel free to look :) It is with Blechd0se's 29th July kernel though, flashed it after flashing the ROM.

Build is uploaded :)
[Defy Android Development] Kayant:
Well at least that's one issue gone now :)
[Defy Android Development] TJKV:
Yup, one step at a time :)

But does KSM work on PAC and Illusion? What are you using right now?
[Defy Android Development] Kayant:
CM 10.2 Not sure if it works on PAC or Illusion since I don't use KSM :p....
[Defy Android Development] jassi32:
while using task manager ( long press home button) , you will see ram bar on top .......
[Defy Android Development] Blechd0se:
I am not sure if those permissions are set correct, is it the same setup as on CM10.x and whats the intention to set those parameters? Because from the kernel side everything looks good.

Anyway i don't recommend using KSM for now, yes in theory its a very powerful feature, but if you saw the same logs as i did you would

think **** theory.
[Defy Android Development] TJKV:
You mean the permissions in this commit?

Hmm okay if you don't recommend using KSM then I'll let SB be as it is for now :)
[Defy Android Development] razorinc:
can someone tell me which is the fastest rom here without the major bugs?
[Defy Android Development] yogesh324:
illusion and slim bean 7.8 both are awesome which can be used on regular basis
[Defy Android Development] hotdog125:
The roms here are mostly free of bugs. You try and see which ROM suits you more.
[Defy Android Development] jorgeoro:
hey, do these roms support ad-hoc wifi connections? I'm on a few months old build because of new cm10 builds dont support ad-hoc coonections..
[Defy Android Development] Kayant:
[MENTION=4148153]TJKV[/MENTION] they have a beta for the new nexus 7 btw
[Defy Android Development] antarix:
Kayant paranoid Android 3.90 for nexus4 is out with 4.3 as base.
[Defy Android Development] lexer98:
Slim bean 7.8 .. nice rom, very fast and stable :good:

Thanks for your work Kayant :highfive:
[Defy Android Development] runeupo:
;) credits to [MENTION=4148153]TJKV[/MENTION] for Slim

[mb525red on taki_jeden 09052013 [SlimBean based]]
[Defy Android Development] TJKV:
Only around 20% credits to me, for repeatedly doing repo sync and make bacon and uploading :p
[Defy Android Development] lexer98:
You'll port Paranoid Android ? ... or can provide me some links to read how to do ? I really want to learn some about porting ROMs from source ..i Use linux for years and know how to use the console very well .... but i can't find a good guide for learn about this.

Thanks ... :good: