yashsingh1/xdaforums huggingface dataset:
[Defy Android Development] niksy+:
No it's not, it's fine. When something is off there's just a white outline, but when it's on and it's not connected - it's greyed out. Turn on your WiFi somewhere where without access points and you'll see the icon is greyed out.

On the other hand, when you do connect via bluetooth it turns blue. So...that's it, it's all fine :cyclops: :good:

This has got to be the most irrelevant post I've ever made :D

P.S. The 30/10 build is running wonderful so far! :fingers-crossed:
[Defy Android Development] okij:
Yes, I did all tests with 720p, I just checked again to be sure. :)

What might also make a difference are CPU clocks: My Defy+ is a bit overclocked to 300/600/900/1100 MHz. I remember that those 1100 MHz were recommended or necessary for walter79's 720p solution.

---------- Post added at 09:44 AM ---------- Previous post was at 09:33 AM ----------

That must be the reason why it's called Bluetooth! :D

No, it's useful because you made a good explanation for this outline / non-outline behaviour, which for some at first is difficult to understand. I remember that this has also been questioned and answered some weeks ago. :)
[Defy Android Development] desihu:
happens when you press both up and down vol key while booting....
[Defy Android Development] leito824:
the location in the weather widget does not work ..! ¿? = (
[Defy Android Development] Hagis:
well now is jus great...

I made system and data backup in custom recovery builded in latest nightly, test other rom, install back CM10.2 and restored it from backup. Now my phone is stuck on On motorola logo. No blue or red light. Any advice? Is my Defy+ bricked?

Please help my friends!
[Defy Android Development] navinshark:
So ur not able to enter custom recovery, you may be need to flash sbf. If stucking in Moto logo means ur phone is still alive and not bricked :P
[Defy Android Development] espaciosalter20:
I'm truly excited this days! I'm going to have a 'new' defy (OK, it's the not working defy from my sister) but I could surely bring him back from death (I suspect that isn't a real death after all, but she got a new phone so she doesn't need it anymore) and with kitkat around the corner, I will going to have the good old days of android development back to my days!

Enviado desde mi Nexus 7 usando Tapatalk 4
[Defy Android Development] Antiga Prime:
Well, overclocked and replaced the app; camera FC's when switching to video mode (cleared app data, of course). Guess it must be CM 10.2 specific.
[Defy Android Development] pasor1:
You're right ... sorry, my mistake :rolleyes: , "skipbrokendatacall" patch is correctly applied to build.prop in the latest build ;)
[Defy Android Development] YetAnotherForumUser:
The camera can also FC because of unsupported - but configured - options. I've seen this after enabling 'power shutter' in the video camera. Manually editing the relevant .xml to disable that option brought the camera back to life...

Sent from... Who cares?
[Defy Android Development] TJKV:
I know it's early, but anyone looked at the kitkat code? I am going through slimkat's code, seems this commit from frameworks_native now goes into system_core. Also the battery service stuff moved from frameworks_base to native, for the 1% patch. But it also changed a lot, not sure what happens there now. Guess I have to wait for the people who actually know how to code to step in first :P

But it seems like only these things have changed majorly, I was able to place most of the other commits in their respective places fairly easily. OFC no clue if it compiles yet.
[Defy Android Development] slimshady76:
I can confirm 720p recording is working as expected in the last build, with my Defy+ overclocked to 1200MHz. I just shot three short videos (3, 4 and 6 minutes respectively) and they were perfect (within the camera's capabilities). I took the time to clean all the recent apps before opening the camera though.
[Defy Android Development] defim:
I had today also a boot-loop. First i thought about /data corruption, but the cause was that XPrivacy crashed while writing its usage-settings. After that it could not start anymore at reboot, crashed all other apps and reboot loop. Removing the app from active modules list fixed it...
[Defy Android Development] Quiksilver20:
What build are you referring to?
[Defy Android Development] syllogyking:
so I tried replacing mms.apk from 20/10 build in latest version I'm running, but group mms still not sending/receiving txts. Quarx, can you please look into this when you get a chance?
[Defy Android Development] TJKV:
Tried to compile just now. TWRP needs to be updated for 4.4, some changes in system/core/include/mincrypt/rsa.h. We'll have to revert to using prebuilt recovery to get it compiling till then.

Also chromium needs 'javap" from /usr/lib/jvm/.../. So I had to do "sudo update-alternatives --install /usr/bin/javap javap /usr/lib/jvm/jdk1.6.0_45/bin/javap 1". This wasn't needed in 4.3.

Apart from that there are a whole bunch of problems in libhardware_legacy. Got through some audio.h compile errors but wifi related stuff is more than I can comprehend. These will need CM patches etc for compatibility I am guessing, as the code is basically AOSP right now. CM hasn't pushed the kk branches yet, last time I checked.
[Defy Android Development] okij:
Many thanks for making OTG on the Defy possible! :good::cyclops:

Yesterday I ordered an USB OTG cable with external power supply to be able test this feature. :D Even though it has not arrived yet, I already installed your OTG kernel, also because you wrote:

Unfortunately, this isn't fully true, because with your OTG kernel I noticed that there are ehci_pm wakelocks reported by WakeLock Detector again. :silly: Thit means that [MENTION=4855459]Blechd0se[/MENTION]'s commit for fixing bug #13 isn't implemented into your OTG kernel yet.

Therefore I would like to ask you to apply Blechd0se's commit to your OTG kernel and post it again so we can test it (as there also might be the possibility that ehci_pm wakelock is needed for USB OTG, even though it is not needed for normal USB operation.) :)
[Defy Android Development] su8044:
+1

I know that ATM i don't have any data left for the month, but still i can't see the E or H or 3G symbol on the status bar so i think it isn't working on the latest build (30-10-2013) , can someboy else confirm this?...

Also, everythink else is working great. no more battery drain, no lag, no wakeup delay, phone runs smooth, battery seems to be less hot on this build, maybe some wifi drops but i still have to test, the torch drawer tilemissing doesn't bother me, and everything else seems to be running fine.

Great work developers
[Defy Android Development] bone101:
3G Symbol is working here...

no need Tod know
[Defy Android Development] TJKV:
Yippee, 3.0.8 test build in OP :D
[Defy Android Development] N34S:
Hi everyone!

I don't know if any of you has already faced this problem, but when I start up the phone with the usb cable plugged in, windows gives me "usb device not recognized" error and identifies it as "unknown device", and the battery doesn't charge from usb port, and every time I have to disconnect and reconnect the cable to get back the usb charge. may be due to an incompatibility in the kernel or is just the 2nd-boot module? please help me
[Defy Android Development] MarcinRN:
just flashed it and seems something went wrong. now can't get it to boot nor enter recovery. the cause could be flashing straight from cm7 though but be awared anyway :laugh:

ok it's weird but it started to boot & booted after plugging usb cable in. :D
[Defy Android Development] Shubhamqweasd:
yes , just plug in the usb , and boot the phone , it will work , btw man nice observation :D
[Defy Android Development] MarcinRN:
you can enter twrp with usb plugged in as well but it seems broken just as in latest cm10.2 (can't install any zips, backup & restore works).
[Defy Android Development] overclockthesun:
Just Flashed the 3.0.8 build. No Wifi for me :( I did get stuck on first boot. Just plugged in the usb cable and it booted in. But no Wifi!!! :(
[Defy Android Development] defim:
For me to. Also, via adb I get always the serial 1234567890abcdef
[Defy Android Development] walter79:
Thats normal. 3.x kernel use different adb. It is a fix for adb. (iserial)
[Defy Android Development] overclockthesun:
reflashed the 3.0.8 build. Still no WiFi for me.
[Defy Android Development] defim:
Sorry,I forgot to say I have 30-10 with 2.6 kernel
[Defy Android Development] N34S:
Me too.
[Defy Android Development] Quarx:
Anyone here, who installed test build and can boot without usb and got work wifi?

Or only i lucky...
[Defy Android Development] grandpa2007:
wifi works fine...,boot without usb with 2nd-boot-uart...
[Defy Android Development] Fight4Music:
Won't boot without usb (charger) but wifi is working fine.(for me :P) installed ontop 30.10s build :)

I can confirm that 2ndboot UART works without the need of USB/charger.

Bluetooth is also working, but sometimes it causes ui freezing ..

(I had the same issue with your latest debug build "just_zip_file", don't know it's relatet to bluetooth)

At last i can't acess twrp. So i will go this way -> 2ndinit -> 10.1 --> 10.2 to revert to 30.10 build.

Dear Quarx,

could you update 2ndinit to twrp ? It would be much easier :) (take a look at my flashing way above, its the same when you come from stock, its not possible to flash 10.2 thru cwm..) Or could you provide a flashable zip of twrp?

Thanks for your good work :)

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Defy Android Development] MarcinRN:
wifi also fine here, boots fine without usb only with uart mode.
[Defy Android Development] Kayant:
Wifi works well it did drop connection once but reconnected quickly. Booted with usb as I don't know about booting with uart.

It's amazing how far it has come thanks for the work ^_^
[Defy Android Development] walter79:
If you have problems with 3.x kernel. plug usb cable and enable ADB in bootmenu and run 2nd-boot from bootmenu. This works for me on first boot.

:D Dualboot will come. (sdcard - 1gb /system)

View attachment 2367213
[Defy Android Development] walkunder:
Indeed, for normal users the only way to get to CM10.2 is through the path, since CWM cannot flash the lastest CM10.2 anymore.

Unless the 2ndboot comes with TWRP. It will be great to have it. :)

Flashed 10/30 with these steps:

reboot and enter TWRP

Backup data and system

Wipe - data, system, cach and dalvik

flash 10/30

flash min-gapps

Restore data

boot

it is working great so far, battery is wokring great for the first night. I still have the wifi list don't update bug and I can have torch as a tile before unlock the phone, but maybe it is because I restored the data.

Data arrow is back. PPTP VPN connection is still not working.
[Defy Android Development] sunil_defy:
pwd for 30-10 build pl ?

how do I install the 4.3 build i tried doing it directly on the top of 10.1 but it failed !
[Defy Android Development] walkunder:
does your CM10.1 build comes with TWRP or CWM? You need TWRP to flash CM10.2 builds.
[Defy Android Development] GodSlayer:
Excuse me for the probably dumb question, but why is all this rush for the 3.0 kernel?
[Defy Android Development] sunil_defy:
It has TWRP...i couldn't find the 30-10 build.
[Defy Android Development] thekguy:
Ion, hwcomposer, etc is there in only 3.0.8 kernel for us. Means smoother and faster ROM
[Defy Android Development] dkv2222:
Another dumb question.

Can someone tell me the pros and cons of this kernel? N is it better than the 2.6 one?
[Defy Android Development] grandpa2007:
...crazy...without sim

Gesendet von meinem MB526 mit Tapatalk 4 Beta
[Defy Android Development] grandpa2007:
Del...
[Defy Android Development] walkunder:
go to the first page of this thread, you will find the work of god.
[Defy Android Development] runeupo:
he's human, he takes money...

use Paypal to thank Quarx, Blechd0se and other devs:thumbup::thumbup::thumbup:
[Defy Android Development] Quarx:
Yes, very old bug(since cm7). You need enable airplane mode.
[Defy Android Development] thekguy:
New kernel works great, very fast. Handles around 10 background apps fine. The only thing which stops me from using it as a daily driver is no in-call sound. Wi-Fi etc work fine. HW decoder too
[Defy Android Development] :
I also mentioned a bug in CM 10.2 with the 2.6 kernel. I can connect my bluetooth keyboard, but I can not write with it. This feature was working with the old bluetooth driver which was included in CM 10 Android 4.1.2 20130318.

Is there any opportunity to use the old bluetooth driver? Can I extract the driver from the old rom and include it in the newest build? Or is there more work to have the old bluetooth driver work?
[Defy Android Development] scooter66:
How do I update from 20131020 to 20131030 and preserve my setup?

I just installed 20131020 recently and am having a great time with an awesome ROM. Gives the Defy a new lease on life.

I have never had to update a ROM from a setup I am happy with. How do I do so and keep my apps and config? I don't remember seeing anything about this, though I am sure it exists, and never really cared, since I never worried about it before.
[Defy Android Development] runeupo:
delete
[Defy Android Development] gkkovacs:
Tried to flash 20131020 on a previous CM10.2 version, but TWRP has restarted during flashing and phone is now in a red moto logo bootloop, no recovery.

Also, 20131030 has been removed from Quarx's server, only available in mirror.

Was there any problem with it?
[Defy Android Development] overclockthesun:
@Quarx,

Well, my Wifi actually works! However, the wifi icon stays Gray in colour. Also Play store is the only app not working on Wifi!:crying:

In order to get TWRP working, I had to set USB debuggin on and set it to apps+adb. I can confirm too that booting in with 2ndinit-uart works fine.

Another thing. Wired headset is not detected when plugged in. Audio starts the second the headset is plugged in but audio plays over the loudspeaker not the headset. no headset icon in the status bar tray. :confused::confused:

Finally, if you had seen some of my posts regarding "Allow purgeable assets" in the sense that I could not turn it off....and it neither showed i\up in build.prop!!!! well it slowed down my system to a standstill....... I found the problem..... it was

Xposed Framework. :eek: Installing it caused "ALlow purgeable assets to remain on even without being present in the build.prop and slowed down the system to a point it was unuseable....

Even to get rid off it... I had to first unselect the option in performance and then uninstall Xposed framework. Usually after a reboot it would show up again...... Thought you might want to know. This is some weird behaviour ...... was not present in 10.1 builds ....I started noticing it only on builds from 10.2 onwards.

Btw, this kernel is really fast.....cam not working as mentioned in the OP.
[Defy Android Development] slimshady76:
Maybe it's too late to report it now that 3.0.8 kernel has gained full momentum, but in Oct 30th build automaitc WiFi detection (and therefore, cLock's weather updates) isn't working for me. Flashed from scratch, starting from SBF.
[Defy Android Development] thekguy:
Grey WiFi icon = No connection to Google servers. Ensure correct gapps are flashed. I used minimal gapps and it worked fine(including play store). The headset bug is already in the list. That xposed problem is something else altogether:what:
[Defy Android Development] overclockthesun:
Hey thanks man. I quite forgot this is version 4.3.1 and not just 4.3. Flashed minimal gapps and viola! Play store working again.

However, Wifi icon was still grey:crying: So I flashed the wpa_supplicant.zip in this thread somewhere ....and now the Wifi icon is Blue:fingers-crossed::fingers-crossed:! @Quarx you can please take note of the grey/blue thingy with wifi icon ....gets solved with the wpa_supplicant.zip file.

As far as Xposed Framework goes..... yes its weird but it does happen. I have reproduced it almost 15 times! from the 8th one onwards I deliberately reproduced it eliminating possible culprits to see if it was some other app causing it...... finally on the 15th attempt, I had eliminated every other possibility except the Xposed framework .... I had my doubts about it..... finally I confirmed it :( ....too bad, I really liked xposed framework a lot. Now I can't have 5 toggles per row due to this on my phone.

It all started when I flashed the DHT 22-23 sbf to get rid off my Telephony layer problem. The sbf solved the reboot problem. But I couldn't root it using any method on XDA, so I used "unlocked_recovery" to install cm10.2. Everything worked except the "Allow purgeable assets" It kept showing up no matter what and the first thing I usually installed was Xposed framwork.

.... However, I still had my doubts. ..... I finally managed to root using Framaroot! Just one click and rooted.

So, I started from scratch again.

A full sbf flash later and on rooting again the same problem occurred after installing Xposed framework.....that's when I tried it for the 15th time and Xposed framework was teh culprit :eek::eek::eek:

I hope @Quarx or someone else into coding can figure out the weird behaviour.

As of now. Wifi is perfect! and blue icon is achieved through flashing spa_supplicant for me...Crossbreeder works too:good:

Update:

Just installed the apps from 4.4 Kitkat leaks and everything works fine. No FC's or other problems. I just wiped the data for the respective apps. Now I am going back to 30-10 version as I need my headset for the working week.

Quarx this kernel is great and fast :) Hope we can have it fully working soon with 4.4 too! count me in for full time use of the this rom and kernel once the headset is fixed.

Edit2: Only way to go back to 10.2 is to flash full sbf? Wipe does not help.
[Defy Android Development] thekguy:
I can use gapps without wpa supplicant change, so the problem is probably somewhere else. I was able to go back to regular builds by system+data+cache wipe and restore without any issues
[Defy Android Development] sevenrock:
seems to be fixed: https://github.com/Quarx2k/jordan-kernel/commit/70ae794bf09616a8d61fcc20ad79c1349eac0ee5
[Defy Android Development] razorinc:
Sry for noob questions but why play store won t work (it says no connection) and why under android version says 4.1.2?
[Defy Android Development] Fight4Music:
[MENTION=4977500]sevenrock[/MENTION]

Thanks, can't wait for next test build :)

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Defy Android Development] hrk:
Well, it's really easy to verify. The kernel exposes information about the frequencies through the following files:

/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
/sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state

The first one it a list of the available frequencies, the second one is a matrix, in the first column you have the frequencies, in the second column the time spent in each one.
[Defy Android Development] alwayspunk:
little bit off

I am sorry if this is off topic. Is there a possibility for our defy to get android 4.4? Has it been released yet?
[Defy Android Development] mauroaraujo:
What are still doesn't funcionating?
[Defy Android Development] rsk_kelkar:
Can someone mod the system files to get KitKat Gradient Status bar like given here and post the resulting files here?? I dont have access to my desktop for a few days to mod the files myself. Thanks :good:
[Defy Android Development] rahul32111:
can anyone help me with the cpu frequencies on 30/10 biuld with 2.6 kernel

i use viper audio for music, but on 30/10 build when screen is off, the song cuts(probably due to lower cpu frequencies during sleep)

i have used this mod on PA 4.3, Mokee 4.3 etc. (new mokee build has the same use, i guess they are based on quarx work)

i m using same governor(interactive) and scheduler (deadline) as i used on earlier builds

so tell guys, how to configure frequencies for sleep?
[Defy Android Development] okij:
Additional info to bug #22

Thanks for your hint to the according files! :)

While "scaling_available_frequencies" always shows the currently set frequencies (also after changing them with SetVsel or Blechd0se's Aero Control), "time_in_state" stays at the frequencies that were set at boot time (i.e. in boot menu).

I'm sure that before the first custom kernels, "time_in_state" was changed accordingly when changing them with SetVsel, so that CPU Spy always showed the correct frequencies. For your No-frills CPU Control app it must be the same.

That's why I'm thinking that something inside the kernel must still be buggy, because with the custom kernels "time_in_state" doesn't get updated anymore.

I hope that [MENTION=513620]Quarx[/MENTION] or [MENTION=221788]Blechdose[/MENTION] will be able to fix it. :fingers-crossed:
[Defy Android Development] overclockthesun:
So can I, but my WiFi icon is still grey in colour. As far as wiping goes, I cannot go back to a 2.6 kernel build without a full sbf flash .
[Defy Android Development] niksy+:
:D

*EDIT* lol @ Fight4Music :D Cheers, mate :D

*EDIT#2* Thanks for wanting to thank me xD
[Defy Android Development] Fight4Music:
Quarx2k created branch kitkat at Quarx2k/android

:D

*Edit* [MENTION=4442286]niksy+[/MENTION] lol :D

You were faster :P Sorry I can't thank you, my 8 thank you are depleted :(
[Defy Android Development] MarcinRN:
maybe Defy gets to be first 512mb ram device to test the so called optimisation and how kitkat performs on it. fingers crossed!
[Defy Android Development] TJKV:
That'll indeed be a newsworthy achievement :D

I'll try to keep up with the big Q with Slimkat :)
[Defy Android Development] Quarx:
Kitkat soon, but for now, new test 3.0 build uploaded:)
[Defy Android Development] YaPeL:
Chances of having audio tunneling? or is like low latency audio? thanks, and congratulations for your achievements
[Defy Android Development] major9:
Changelog ?
[Defy Android Development] Fight4Music:
https://github.com/Quarx2k?tab=activity

All gits which are going to "CM10.2-3.0" :)
[Defy Android Development] slaphappy76:
No SIM

With the Today 3.08 Kernel Build i don't have access to the SIM... :/:crying:
[Defy Android Development] Fight4Music:
Why todays test build is removed from d-hst?
[Defy Android Development] Quarx:
Reuploaded due: (Now sim works)
[Defy Android Development] Fight4Music:
Okay, thanks! :)
[Defy Android Development] major9:
3.08 Kernel - Phone reboots everytime I try to make a call.
[Defy Android Development] slaphappy76:
SIM Works / PlayStore not

Now SIM works :) Thx :victory:

but the Problem for me is coming.. over the PlayStore I don't have access to USB / Storage at the end of install process... :confused:
[Defy Android Development] Fight4Music:
I can confirm this.

I have heavy battery drops after a reboot with kernel 3.0.8 (tested twice)