yashsingh1/xdaforums huggingface dataset:
[Defy Android Development] TJKV:
I found some time to flash PAC4.3 and look at kmsg, this is what happens when USB is connected:

<6>[ 481.749481] cpcap spi2.0: notify_accy: accy=0
<4>[ 481.755035] USB connected!
<6>[ 481.755065] musb_pullup2 - Enabling USB Pullups
<4>[ 481.755096] Enable usb
<6>[ 482.052032] MUSB BUS RESET as b_peripheral
<6>[ 482.065185] android_work: did not send uevent (0 0 (null))
<6>[ 482.123901] MUSB BUS RESET as b_idle
<6>[ 482.144866] android_usb gadget: high speed config #1: android
<6>[ 482.149963] android_work: sent uevent USB_STATE=CONNECTED
<6>[ 482.157501] android_work: sent uevent USB_STATE=CONFIGURED

And this is what happens when SB4.3 is connected to USB:

<6>[ 244.340362] cpcap spi2.0: notify_accy: accy=0
<4>[ 244.346649] USB connected!
<6>[ 244.346679] musb_pullup2 - Enabling USB Pullups
<4>[ 244.346710] Enable usb
<6>[ 244.855468] MUSB BUS RESET as b_idle
<6>[ 244.871887] android_work: sent uevent USB_STATE=CONNECTED
<6>[ 244.927215] MUSB BUS RESET as b_peripheral
<6>[ 244.934356] android_work: sent uevent USB_STATE=DISCONNECTED
<6>[ 244.950805] android_work: sent uevent USB_STATE=CONNECTED
<6>[ 245.023529] MUSB BUS RESET as b_peripheral
<6>[ 245.027160] android_work: did not send uevent (1 1 (null))
<6>[ 245.095397] MUSB BUS RESET as b_peripheral
<6>[ 245.104888] android_work: sent uevent USB_STATE=DISCONNECTED
<6>[ 245.123443] android_work: sent uevent USB_STATE=CONNECTED
<6>[ 245.195495] MUSB BUS RESET as b_peripheral
<6>[ 245.202239] android_work: sent uevent USB_STATE=DISCONNECTED
<6>[ 245.220184] android_work: sent uevent USB_STATE=CONNECTED
<6>[ 245.291259] MUSB BUS RESET as b_peripheral
<6>[ 245.298736] android_work: sent uevent USB_STATE=DISCONNECTED
<6>[ 245.315643] android_work: sent uevent USB_STATE=CONNECTED

Does this give you any clue as to what's going wrong? [MENTION=4173406]Kayant[/MENTION] [MENTION=4855459]Blechd0se[/MENTION]
[Defy Android Development] Blechd0se:
Looks like the android usb gadget driver doesn't work correct.

Did you change anything related to this in kernel?

I don't know which patches the slim team did related to usb.

You can search for this messages in the source code (there you can

really see whats happening) and try to fix the reconnecting :)

Gesendet von meinem Nexus 7 mit Tapatalk 4
[Defy Android Development] Kayant:
[MENTION=4148153]TJKV[/MENTION]

Just saw you don't fully revert the removal of the USB stuff

Need this ---> https://github.com/SlimRoms/packages_apps_Settings/commit/75096de24fb12e4b849ddfc1fb9c7af786f0a167

And use slim4.3 and my test system_core that I made for slim. Also either fork and revert this commit ---> https://github.com/SlimRoms/android_prebuilt/commit/a975b14b66188197ab787371a65bda1eebb3e14e we need for our kernel.

Or use CM's but it will be bigger and have unnecessary junk :p.

I think it will work then I hope :)
[Defy Android Development] TJKV:
No, I use quarx's AeroKernel branch directly for the kernel. So no changes in kernel by me or slim. So I'm not really sure which repo to search for the error mesages in, kernel or system_core or frameworks_base etc.

If the error messages are located in the kernel then it seems a bit weird to me that this error is happening. I (with my limited knowledge) had thought the kernel was the lowermost "layer" and it didn't have too many dependencies with the higher "layers" like the dalvik vm or framework or whatever. Also the same branch seems to work in SB4.2, and all the other JB roms we have. That's why I was thinking the problem might be in frameworks_base or system_core or something. Where do you think I should start?

Ah okay thanks :) Will try this weekend.
[Defy Android Development] Blechd0se:
Its definitely in Android OS-part, because USB works on CM10.x releases. I can't really tell you much more because Quarx is the

maintainer of this part. I know he had some troubles too while porting the new usb code, but he solved it (as always ;) ).

Everything in kmsg is directly from kernel, no other things are in between. But somehow the communication fails, its likely that some slim-patch

causes this problem. You can change the kernel driver behaviour to support the new OS changes (driver/usb/gadget/), but i wouldn't recommend that.

As [MENTION=4173406]Kayant[/MENTION] mentioned, try to figure out which commit causes the problem and revert it.

Also system_core sounds more reasonable here, since framework might be a to high "layer" ;)

Btw. you guys gained a lot of experience, you should start writing your first patches for CM :)
[Defy Android Development] pgreed:
This Rom is memory hungry and from time to time free memory dropping below 4MB and system freeze. I think is needed a better memory organizer because in this stage is nor suitable for ours Defy.
[Defy Android Development] Kayant:
http://xdaforums.com/showthread.php?p=42393476
[Defy Android Development] Rawwr:
I wish it was 4.1.2 :(
[Defy Android Development] retekevo:
Anyway this is a very very very good rom!!!! I felt in love... But the ram usage... :mad:
[Defy Android Development] ldiomedi:
I flashed the Rom because I like tablet ui of pa, but on 4.2.2 does not looks good as in 4.1.2. That's my personal liking. So I went back to mokee 4.2.2 and didn't use it for much time. People must stop complaining about ram issues. There's some thing that can be done for better performance. Greenyfi, supercharger, crossbreader, etc. But don't forget this is a first release. Kayant one week ago said he stop building 4.2.2 for serious problem that he couldn't fix. And now we have other powerful option for our phone, so I believe the critiques must be constructive and if the Rom don't work/like for you, just don't complain about the performance. Personally I'm waiting for rootbox and slim. Those are so interesting for me. Great work, Kayant, as always!

I know, my English isn't good. Sorry about that. :D

Enviado desde mi MB526 usando Tapatalk 2
[Defy Android Development] delight535:
Could you send a link for Mokee 4.2.2? :) Thanks!

BTW: Thank you Kayant for the great work! Any news on the other roms?
[Defy Android Development] pgreed:
I don't complain about ROM I just said that ram usage overwhelmed the Defy resources. Yes a slim version is a better option. Anyway a very impressive work!
[Defy Android Development] cupioscire:
As far as I know paranoid team released the source, so.. We are waiting :D

Gesendet von meinem XT890 mit Tapatalk 4
[Defy Android Development] Kayant:
Well you're going to have to wait quite a bit as I have a lot of school work to do atm but I will sync my repos up so if anyone is too impatient they can build it them selves
[Defy Android Development] TJKV:
Is SB buildable right now? If not would you mind listing out approximately whats left? I'll see if I can spare some time to try my hand at it again :P

BTW 4.1.2 SB is building fine for me, I managed to remove the offending disable bootanimation setting in Performance options. Figured out what to remove for the voltage tweaks too but was too lazy to do it. Might not go ahead with it now, I like 4.2.2 a lot :D
[Defy Android Development] matiasrey:
If you do build SB 4.2.2 please upload it, i´d love to be your guinea pig! I´ve been waiting for that particular rom...
[Defy Android Development] Kayant:
Yh it's been buildable for a while really all are buildable but all don't work right :p Oh that's great to hear nice how did you go about removing it yh I will going to be I try but don't find the all the relating java code first time and forgot and started working on 4.2.2 again. You can sent me a pull request and I will merge that in :D
[Defy Android Development] TJKV:
Not sure how to request that...but here are the commits:

https://github.com/tejus/android_pa...mmit/e0697ad7eb4b4d2d0d70ac78efffa078a148daae

https://github.com/tejus/android_pa...mmit/df8a324ce45609896c87c327bc86da535ebc36ad

Went to performance settings after compiling and clicked around to make sure nothing has conked out, couldn't find anything wrong. But no guarantees, I don't know Java either. i just followed the variables and ripped out anything relevant :P
[Defy Android Development] Roshan_P:
I tried to flash PAC rom but once the phone boots I keep getting errors like "setup wizard.apk has stopped working" and "process.acore not working".

I came from Xperia D 4.1.

I tried redownloading the ROM and flash it again through TWRP, still the problem persists.

I did all the wipes and used minimal gapps of tejus.k.v!

Am I missing something?:/
[Defy Android Development] TJKV:
Wipe /system in TWRP along with /data and reflash
[Defy Android Development] rol525:
I make a patch for MB525 for have minimal changes in the build.prop (now is MB525 not MB526) and the battery files from MB525

Link:http://www.mediafire.com/?fjydr02ewlwoq6j
[Defy Android Development] stirlitz99:
Great job Kayant with the PAC!

I came from your Codename Android 3.6.6, that strangely started to become unstable after half a year of use.

My Defy is green lens, oc-d to 1.1GHz and everything seems to be working fine, but BT. I can't use my Nokia BT headset, because it sounds like frogs talking. :) ... hopefully you'll find the solution.

Just minor lagging (absolutely bearable for daily use), but has several extras that I like over CM10.1... probably I'll change for Codename Android's similar version (if you make it).

Thanks for the hard work!

ps: would definitely love a green lens 720p video mode ;)
[Defy Android Development] TJKV:
I'm sure Kayant would love it too, let him know when you get it working ;)
[Defy Android Development] rol525:
I recommended for MB525 user flash my patch battery and build.prop:http://www.mediafire.com/?fjydr02ewlwoq6j

Try it,for me work.
[Defy Android Development] TJKV:
Okay will try Kayant's recommendations and then drill down on those messages if it doesn't work.

Kayant may be experienced enough for that now, but not me. I could say that I still hit android with a large club to get it to fit in to my phone. Specifically my tool of choice is Meld. I have even three way folder diffed the frameworks_base branches of CM, quarx, and SB. Took my computer 15 minutes to generate that.
[Defy Android Development] juried:
I love slim, and am hoping you will keep plugging away at this. I am currently on slim 8.1, but the trial I had with 4.3 - wow what a difference. Way to go chaps!
[Defy Android Development] Kayant:
You can test to see if only settings is needed for it to work... Use $ mmm packages/apps/Settings instead of make bacon. Then copy the new Settings.apk and profit :)
[Defy Android Development] TJKV:
Hmm yup but there have been some recent commits in Settings which have frameworks base parts too. If I fork it now those commits will be added too. I could git reset --hard to the position it was when I last compiled but I don't remember what that was. And anyway I compile only when I sleep because I need my laptop to be on Windows during the day. But either way I can't do anything till the weekend, I have to work on an Urban Design submission/presentation now. I shouldn't be on XDA right now either :p So bye till this friday at least :p
[Defy Android Development] dkv2222:
What's femblack?
[Defy Android Development] TJKV:
What ROM? Are you using Xposed? If so what modules?
[Defy Android Development] ldiomedi:
Femblack its a dev who made an xposed module to modify lots of things on how android looks.

MB526 paranoiqueado con AOSPA 3.99
[Defy Android Development] TJKV:
That's what i thought too, so I asked him what modules he uses :P
[Defy Android Development] ldiomedi:
http://xdaforums.com/showthread.php?t=2294419

There is the femblack module

MB526 paranoiqueado con AOSPA 3.99
[Defy Android Development] TJKV:
Um yeah, I know. Now enough ot here.

EDIT:

[MENTION=4173406]Kayant[/MENTION]: About the settings app commit, I assme you meant I should change the Settings.global lines back to Settings.secure. But that entire block has been rewritten in a different way, but I changed it back anyway. Or did you mean something else?

EDIT 2:

Okay that change is not the only thing that has to be reverted if it should work I think:

packages/apps/Settings/src/com/android/settings/deviceinfo/UsbSettings.java:168: package Settings does not exist
Settings.Secure.putInt(getContentResolver(), Settings.Secure.USB_MASS_STORAGE_ENABLED, 0 );
^
packages/apps/Settings/src/com/android/settings/deviceinfo/UsbSettings.java:168: package Settings does not exist
Settings.Secure.putInt(getContentResolver(), Settings.Secure.USB_MASS_STORAGE_ENABLED, 0 );
^
packages/apps/Settings/src/com/android/settings/deviceinfo/UsbSettings.java:172: package Settings does not exist
Settings.Secure.putInt(getContentResolver(), Settings.Secure.USB_MASS_STORAGE_ENABLED, 0 );
^
packages/apps/Settings/src/com/android/settings/deviceinfo/UsbSettings.java:172: package Settings does not exist
Settings.Secure.putInt(getContentResolver(), Settings.Secure.USB_MASS_STORAGE_ENABLED, 0 );
^
packages/apps/Settings/src/com/android/settings/deviceinfo/UsbSettings.java:176: package Settings does not exist
Settings.Secure.putInt(getContentResolver(), Settings.Secure.USB_MASS_STORAGE_ENABLED, 1 );
^
packages/apps/Settings/src/com/android/settings/deviceinfo/UsbSettings.java:176: package Settings does not exist
Settings.Secure.putInt(getContentResolver(), Settings.Secure.USB_MASS_STORAGE_ENABLED, 1 );

Either way CM settings app also uses the "function = UsbManager.USB_FUNCTION_MASS_STORAGE;" type of code here so I'm guessing this isn't where the problem is...
[Defy Android Development] Rawwr:
Kayant, just wanted to know when u will be releasing carbon and PA 4.3 ? IK u have released PA 4.3, u said that u will make a particular thread for both of the ROMs, could u please tell me ? I m on Illusion 2.1 now, just wanted to try Carbon, i hope u dont get pissed off, thanks for ur work, sire.
[Defy Android Development] level_666:
Here:
[Defy Android Development] Rawwr:
U ain't kayant !

Neither i asked u,

Ok ?

Dont try to act smart :)
[Defy Android Development] level_666:
Well, seems like you are sharp-eyed!

However, I'll show you someone who truly IS Kayant...

Here:

For further discussions, please go...

Here: http://xdaforums.com/announcement.php?a=81

...or send me a PM.

But don't keep this HERE. OK?

Enviado desde mi MB526 usando Tapatalk 4
[Defy Android Development] Kayant:
Well what he said was right at the end of the day. ---> http://xdaforums.com/showpost.php?p=45299539&postcount=544

Thanks for the help

Ok to clear any further misunderstanding the 4.3 thread will be a go when TJKV and I have fixed the USB issue. Also we might decide to wait for a bit as Quarx will be back soon and some important updates may come in and because we don't have that much time now as we are back at school there wouldn't be a lot of updates going forward.
[Defy Android Development] fabiosarts:
baseband changer doesn't works with slim beam :S
[Defy Android Development] TJKV:
Which version are you using? Works fine for me in all but the 7.2 version as init.d was broken in that.
[Defy Android Development] Antiga Prime:
I'm pretty sure init.d wasn't working on "Slim-mb526-4.2.2.build.7.8-UNOFFICIAL-20130728-1557", which is too bad since it's the only one that didn't have the audio bug during video recording, at least not for me when I tried it.
[Defy Android Development] fabiosarts:
the last build :eek:

Slim-mb526-4.2.2.build.8.1-UNOFFICIAL-20130901-1120.zip

illusion works very well, but it as slow as any CM10 jellybean :3
[Defy Android Development] Antiga Prime:
Init.d works on that build, and I can confirm that changing basebands in the "advanced" menu does in fact work.
[Defy Android Development] fabiosarts:
it's a shame for me :(

i've tryed with differents baseband chager, even for the advanced menu, i can't get it working :(
[Defy Android Development] lexer98:
This happened to me a few times with different rom .. :silly:

-Turn off the phone

-Pull out the battery and SIM

-Leave the phone 20m

-put it together and see if it works
[Defy Android Development] ldiomedi:
If you want a good experience with jelly bean (4.3) you should try paranoid with the latest blechdose kernel. Just the zimage, not the ramdisk. Best combination I ever use.

MB526 paranoiqueado con AOSPA 3.99
[Defy Android Development] fabiosarts:
that's weird, i tyred by third time and...this time worked, even without shuting down the phone or waiting thanks :D

thanks, i heard good about paranoid android, i'll try someday :D

for now i want to focus trying slimbean
[Defy Android Development] rol525:
Paranoid is awesome.I can play Real Racing 3 in graphics medium with 25+ FPS.Battery is ok 2 days with 2 h 30 m of screen.
[Defy Android Development] rahul32111:
guys is there any option to use navigation buttons on PA 4.3. my led buttons light is dead, so cannot use my phone without nav buttons

edit : ok got it in hybrid settings > interface
[Defy Android Development] antarix:
Yes but you can't disable hardware buttons.

Go to PA settings

Interface and choose the navigation bar percentage value to consume on the display.
[Defy Android Development] rahul32111:
ok thanks for reply

is it normal : bluetooth share stopped working message while turning bluetooth on(not able to use bluetooth)

i m on PA 4.3 rom with 10.09 kernel
[Defy Android Development] sUpErwHoO:
Which is the best kernel version to try with illusion?

Sent by an alien.
[Defy Android Development] niksy+:
It's a problem with the bluetooth libs, not the kernel. Use the libs from CM10.2. This has been talked about on multiple occasions now and the libs have been posted for anyone who doesn't want to download the CM10.2 zip.

Here's the post - http://xdaforums.com/showpost.php?p=45235004&postcount=526

Copy and overwrite the current files and set the correct permissions. And try searching first the next time :silly:
[Defy Android Development] juried:
Great news: I have got bluetooth going on Slimbean 4.3. I did a logcat capture and found that a lib file was missing. So I copied the file over from Slimbean 4.2.2 and it worked.

The relevant file plus its containing folder is /system/vendor/lib/libbt-vendor.so.

After copying the file plus its folder structure into /system and fixing permissions, I was able to pair with my tablet and send a file. Haven't tried other bt actions yet.
[Defy Android Development] Kayant:
Good spot :)

Also [MENTION=4148153]TJKV[/MENTION] it's better we disable this ---> https://github.com/tejus/android_de...mmit/613ee2f3a35f3a18571fbf5e9373a99570ce8efe . It actually has to opposite effect of helping :p I don't get why the lib file would be missing kinda weird :confused:
[Defy Android Development] TJKV:
Hmm okay I'll enable scissor. How could you tell it had a negative effect though? I couldn't see any difference before or after :P Our phone has the SGX530 btw, the Galaxy S has the 540...

I saw a few bt related commits in various branches the past month, something might have broken it. Or maybe it was broken right from the beginning, no clue :P

EDIT: okay libbt seems to be from https://github.com/SlimRoms/device_common/tree/jb4.2 in slim4.2, missing in 4.3 branch. But it only has configs for the nexus devices. So must not be the right one...
[Defy Android Development] UncleDan:
[MENTION=4173406]Kayant[/MENTION] on PA I am having continuous data issues: if I want to try another kernel which one should I point to and which file I must delete from zip before flashing, please?

I answered myself, sorry for stupid question:
[Defy Android Development] ldiomedi:
I'm using the Sep 10 kernel since 3 days ago. Very good results. Just replace the zimage or delete the ramdisk from the zip. It's on the cm10.1 thread.

Edit: here is the post http://xdaforums.com/showthread.php?p=45476274

MB526 paranoiqueado con AOSPA 3.99
[Defy Android Development] EldonTyrell:
[MENTION=4148153]TJKV[/MENTION] , just a quick thanks for SB 8.1 from 9/1. 110 hrs uptime and still going strong. :)

Could be coincidence, but my device (red lense MB525) seems to have no ril problems on this ROM. I also changed freq/vsel for the first time, so it could be that. Either way, I was lucky to make it 48 hrs before.

1100/58 800/43 600/33 300/18 for anyone that may want to experiment.
[Defy Android Development] Kayant:
Btw guys the king is back ^_^
[Defy Android Development] delight535:
[MENTION=4148153]TJKV[/MENTION]: Can you tell me if there are any other bugs in your 4.3 Slimbean, than the listed ones? Because if those are all that are listed in the description, then I think I can live with them for some time. :)

I tried Kayant's PA, it looks like it runs great, but I don't know how to set the global DPI to 240. And I did not find where to center my clock. Can I do it with PA?
[Defy Android Development] Antiga Prime:
It's in Hybrid settings. You might have to enable the advanced options first in Hybrid, not sure, not on PA anymore. You'll also have to clear/reset the settings for the individual apps that might have a different DPI than the default.
[Defy Android Development] ldiomedi:
you can set the global dpi in Hybrid properties/interfaz. but there's some apps that have custom dpi like gmail. For those you have change it manually. And for the clock centered you can use the xposed framework whit the module Xblast. It has many things to change. I''m using it right now
[Defy Android Development] lexer98:
Quarx github is on fire men !! :D
[Defy Android Development] TJKV:
Okay I finally found the file that contains the function android_work, but not sure where or even what "android_usb gadget" is. Here is the function itself:

static void android_work(struct work_struct *data)
{
[COLOR="red"]struct android_dev *dev = container_of(data, struct android_dev, work);[/COLOR]
struct usb_composite_dev *cdev = dev->cdev;
char *disconnected[2] = { "USB_STATE=DISCONNECTED", NULL };
char *connected[2] = { "USB_STATE=CONNECTED", NULL };
[COLOR="red"]char *configured[2] = { "USB_STATE=CONFIGURED", NULL };[/COLOR]
char **uevent_envp = NULL;
unsigned long flags;

spin_lock_irqsave(&cdev->lock, flags);
if (cdev->config)
uevent_envp = configured;
else if (dev->connected != dev->sw_connected)
uevent_envp = dev->connected ? connected : disconnected;
dev->sw_connected = dev->connected;
spin_unlock_irqrestore(&cdev->lock, flags);

if (uevent_envp) {
kobject_uevent_env(&dev->dev->kobj, KOBJ_CHANGE, uevent_envp);
pr_info("%s: sent uevent %s\n", __func__, uevent_envp[0]);
}[COLOR="Red"] else {
pr_info("%s: did not send uevent (%d %d %p)\n", __func__,
dev->connected, dev->sw_connected, cdev->config);[/COLOR]
}
}

Anyway this code outputs in kmsg (PAC):

<6>[ 482.065185] android_work: did not send uevent (0 0 (null))
<6>[ 482.123901] MUSB BUS RESET as b_idle
<6>[ 482.144866] android_usb gadget: high speed config #1: android
<6>[ 482.149963] android_work: sent uevent USB_STATE=CONNECTED
<6>[ 482.157501] android_work: sent uevent USB_STATE=CONFIGURED

but in Slim:

<6>[ 245.027160] android_work: did not send uevent (1 1 (null))
<6>[ 245.095397] MUSB BUS RESET as b_peripheral
<6>[ 245.104888] android_work: sent uevent USB_STATE=DISCONNECTED
<6>[ 245.123443] android_work: sent uevent USB_STATE=CONNECTED
<6>[ 245.195495] MUSB BUS RESET as b_peripheral
<6>[ 245.202239] android_work: sent uevent USB_STATE=DISCONNECTED
<6>[ 245.220184] android_work: sent uevent USB_STATE=CONNECTED

So could it be that dev->connected and dev->sw_connected need to be 0 in Slim too for usb to work?

Not sure where these two members get their values from beyond this line:

struct android_dev *dev = container_of(data, struct android_dev, work);
[Defy Android Development] Kayant:
[MENTION=4148153]TJKV[/MENTION] So reverting it in settings also don't work??

it seems like this ---> https://github.com/tejus/android_de...mmit/613ee2f3a35f3a18571fbf5e9373a99570ce8efe

Is actually also useful for our device but I think some other things were also needed for it to work properly. Also it don't know if that works on 4.2 btw.