yashsingh1/xdaforums huggingface dataset:
[Defy Android Development] popadic022:
thx, for reply.
[Defy Android Development] Proverbs2:
transparent status bar

For months, I've been using this method to make my status bar transparent. I just updated from the September 14th build to the latest, and used the same procedure as always to modify the status bar. This time, however, the status bar stays black on the homescreen, but it's transparent everywhere else (on the lockscreen and in every app). Any idea why the transparency isn't working on the homescreen?
[Defy Android Development] snaky90:
Updating new maniac's build !!!
[Defy Android Development] popadic022:
this build "cm-7-20121018-UNOFFICIAL-jordan_plus-signed" or new?
[Defy Android Development] snaky90:
I'm using cm-7-20121018-UNOFFICIAL-jordan_plus-signed ;)
[Defy Android Development] [] AL []:
I basically use the same method (post #2 on one of my threads) and have no such problem with Oct 18th nightly.

Here, you can flash or compare (Winmerge) your SystemUI.apk with mine maybe.

*** Warning: this is for October 15th and Oct 18 builds from Maniac ONLY.***

If you ignore the line above, it's your own problem and fault.

Cheers

/A
[Defy Android Development] Proverbs2:
OK, thanks, I must have done something wrong this time. I'll try again.

EDIT: Hmmm, I still have the same problem. I went through the whole process of editing my SystemUI.apk again, and I even tried copying the classes.dex file from your SystemUI.apk into mine, but I still get the same result: the status bar stays black on the homescreen. It's transparent on the lockscreen and in every app, and it is even transparent briefly during the transition animation when returning to the homescreen from settings or from an app. I can't figure out what's going on.
[Defy Android Development] Sidz4u:
Wish if CM7 had MIUI like page toggles in notification bar.

But when its about speed, Cm7 has no match ;)
[Defy Android Development] juan296:
ManiAc:

2 stupid question,

1) can you implement/add sim unlocker in your nightly build? Is annoying add this patch after of each nightly.

2) when i use bootanimation with sound,it doesn't work (the Sound) .. maybe you can help us:)

Thanks for support! You're my hero xd

Arch Linux User ..
[Defy Android Development] mistis:
from cm10 to cm7

is it possible to go back from cm10 (ver from 20120912 so before custom kernel was introduced) to cm7 without a full wipe?
[Defy Android Development] UEman:
No, it is not possible.
[Defy Android Development] Llamatron:
I'm trying to troubleshoot a couple of issues I have with MMS on Maniac's builds, by default they appear as slideshow and are compressed way too much (to 10k while my carrier's max is 600k).

From what I gathered the problem happens when my carrier can't properly identify the phone model, so I took a look at MMS.apk's mms_config.xml and noticed the uaProfUrl points to an error 404: http://www.google.com/oha/rdf/ua-profile-kila.xml

I tried to edit it to see if pointing it to the moto one ( http://uaprof.motorola.com/phoneconfig/MotoMB525/profile/MotoMB525.rdf ) has any effect, but I'm a total noob at modding apks so failed to install a modded apk I made.

Anyone got an idea if I'm on a good track with this user agent / uaprof thing?
[Defy Android Development] maniac103:
At least it makes sense. Updated Mms.apk with userAgent = MB525 and uaProfUrl=http://uaprof.motorola.com/phoneconfig/MotoMB525/profile/MotoMB525.rdf attached. Please try it.
[Defy Android Development] Llamatron:
Nop, no luck :( I even tried with MotoMB525 as user agent to match the file name but no, it still comes as 10k slideshow.

One weird thing is that when I choose the Nokia N95 UA from the list provided in the SMS app it doesn't come back as a slideshow, but it's 10k big, while the N95 is known from them (I had one before my defy), and surely can load bigger images than that.

Thanks for trying anyway :)
[Defy Android Development] popadic022:
Does any try this "com.lousou.mms_bubbles46" mms.apk? I use this application on cm7.2 and has many more options than the standard. it might help. On xda forum was a tread but its closed (you can find that file with google).
[Defy Android Development] LeopardSurd:
hmm, I rarely send a MMS but I must recognize that some of my felas told me that they sent me some MMSs but I didn't received them. Also, the problem with the size attachment seems to be annoying. Hope it will be fixed. Anywah, maniac's build (the latest) is great. No problems until now.

Btw, does someone know a solution for the issue with the screen that doesn't wake up during a call?
[Defy Android Development] popadic022:
i have problem with mms, but problem is wrong deafult apn settings (apnsconf) for my provider. after change conf, now its work ok. but sometimes after call end it show only black screen (rarely). last maniac rom is great (fast, stable, good battery life,....) for me it's stable not nightly version :)
[Defy Android Development] 2Pints:
Yes, and no, my return path/switching method is as follows: starting with CM7...

use an app to back up your call data and sms texts, use titaniuim back up for your apps.

go to recovery and make a full back up of CM7, if you want you can rename this from a numeric system to date/name ie CM7_18_OCT_2012 )

install CM10 from scratch ( only needs to be done once)

Use titanium back up to get your apps back ( but not all apps and not system data!!) get your call data +sms logs back using the back up/restore apps.

make a full backup in recovery, again re-name this if you want to CM_10_18_OCT_2012, then from recovery just select CM7 or 10, restore your backups and you should be good to go, swtiching beteen the two.

this will take time, and its not exactly fast, if it gets stuck at boot re move the battery if its stilll stuck try flashing the latest version of the rom your trying to re-install.

for extra security test your back up before going back/re-flashing, and keep a copy of some back ups on your p.c.
[Defy Android Development] [] AL []:
ur wc. I'd download the nightly again, wipe cache and dalvik, install it then install the zip I gave you, wip cache and dalvik again and see how that goes.

Edit: in fact, my zipped SystemUI.apk has no modded png so you should also apply a transparent enabled theme. You can try WizAL_v1.8... ;)

Sorry to ask, but how to reproduce this? What do you mean they appear as slideshow? You never see a single pic?

As far as compression goes, I've just tried with a single picture and it came in about 4x smaller [pic1].

Are you using Droidwall by any chance?

As I remember, Maniac brought some changes to MMS some time ago (~2-3 months ?) which I believe made MMS able to send/recieve messages even when "Wireless & networks/Mobile networks/Data Enabled" is unchecked. But you still have to make sure that MMS.apk is allowed access on data/3G (Droidwall's second column checkbox). ...just a guess here...otherwise, do like me and send yourself one to test it out hehe :p

What I still find annoying with SMS/MMS is that the sent/recieve times are sometimes messed up [pic3] but I realized that it might not be (only) due to the app's code [but carrier also].

Funny that the MMS comes up here today, I was just playing around with other versions of MMS that I've found on other xda devices forums...

Here's one that I found on a Sony forum (can't remember more details than this sorry) that has the old bubble-style messages [pic2]. The beauty of it is also that you can theme almost every part of it (background, text bubbles, add recipient, top/bottom bars, new message icon, ....). Quite easy to do since it's a system app and there's no need to re-sign the apk; just drop new pngs over [with same name obviously] and it's done. I did a few changes already and I must also add that I've tweaked it to get the "enter" key [allows writing sms on multiple lines] instead of the smileys key.

[So you can't install it as a regular app; rename it to Mms.apk, copy it to system/app (rename your stock Mms.apk's file extension first as a backup), set its permissions to 0:0-644 and reboot]
[Defy Android Development] LeopardSurd:
I've just send me 2 mms-es with a photo and a video made with my phone. The sent items are well compressed but the received files are to much compressed. The video at least seems to have a very bad quality. After the playback of the received video ends, there is a message that tell me the video is compressed to fit my phone but it seems that the operator think I have som low end java phone and not an Android phone. On the stock GB rom, I didn't encountered this problem. Anyway, the mms-es are obsolete.

About that screen disabled during phone calls, here are more details. It's an old problem.

P.S. yes, it seems that the mms can be sent even the data is disabled. Great addition from maniac.
[Defy Android Development] Llamatron:
Easiest way to reproduce it for me is having Orange France as carrier and a phone that's not in their database, but I red people from other countries so on other carriers having a similar problem. I have been on another carrier for a month and MMS were fine there, but that other carrier is having peering issues with Google which is a bigger problem for Android phones.

With most user agents I tried, in the conversation view of the default app the MMS shows as a a picture with a big play icon over it. When clicked it opens what looks like a video player, showing first a tiny picture compressed to 10k for 5s, then the text for another 5s. No zoom or save picture option available.

Using the N95 or Sony user agent that are available in Cyanogen's MMS app at least it shows as a picture with text below in the conversation view, but when the picture is clicked the full view has a resolution around 150x200 and weights 10k too. I can zoom and save the picture from there (it's shown as a normal picture in gallery, quickpic or whatever I choose)

Whatever the user agent is it looks like with the default MMS app is sending it as a 10k pic, as it is sent rather fast while I have a slow 3g connection where I live. With ChompSMS and playing a bit with the settings I apparently could send a bigger picture as it took way longer to send, but it's been received as 10k.

It's not really an issue with Maniac's build, more like some carriers having a too strict policy when it comes to MMS, or are trying to save some bandwidth while giving the finger to their users. Or maybe the wide variety of Android devices not playing well with that policy.

Other relevant facts:

I know someone who is on the same carrier and bought her Android phone from them who doesn't seem to have the issue.

I red some people who had the same issue on another carrier and managed to get it working by using a custom Mms.apk and NexusOne user agent.

I red about someone on the same carrier who had bought a recent phone and had the same problem. After talking with the carrier's level 2 support they added it to their list of known devices, fixing the issue for him.

I'd be curious to know what user agent and uaprof the stock defy uses, but I'm not sure if it is still relevant when being on Cyanogen, or any other custom ROM for that matter.

I got the apk decompile, customize, recompile, install routine right, so I'll probably play around with user agents and uaprofs and maybe post my results if I manage to get something working, but if I can't fix it I'll just change carrier and hope for the best.

EDIT: got uaprof from here http://www.uaprof.com/Motorola/ but the user agent they give looks more like a web browser user agent
[Defy Android Development] maniac103:
If I read the decompiled code of BlurConversations and MotoSettingsProvider correctly, the stock ROM uses the user agent 'motoa955'. Might be worth a try.

Gesendet von meinem MB525 mit Tapatalk 2
[Defy Android Development] Llamatron:
Nop still no joy, tested with default or modded Mms.apk

I have a phone meeting with an Orange technician in the coming week, we'll see if something can be done on the carrier side.

Again thanks a lot for your help :)

EDIT: weird, motoa955 looks more like Droid 2 user agent according to google
[Defy Android Development] Proverbs2:
AL, I tried flashing your SystemUI.apk (with the semi-transparent png files that I've been using), and I still get the same problem: black status bar on the homescreen. The png files I've edited are "status_bar_background.9.png", "statusbar_background.9.png", "status_bar_close_on.9.png", and "shade_bg.png". Perhaps there is another png file that I need to edit as well? Using semi-transparent edits of just those png files has always given me a semi-transparent status bar & notification pulldown on previous builds...
[Defy Android Development] [] AL []:
When I first read this, I thought: yes he's right, but thinking more about it I find that this ain't quite true. Although smartphones are becoming the norm and pretty much everyone will get one eventually (I mean it's the old dumb phones that are becoming obsolete), not everyone has/will have 3G/4G/LTE high speed connection. So for those (ok maybe rare) occasions when you need to quickly send a pic, short voice recording (or what not), MMSes are really convenient and even easier to send than an email with an attachment. So yes I think that they still have their place on our phones and that it would be nice that the maximum file size be either selectable or reasonably set (10k is not and here 40 kb pic is borderline also...).

Just because I do not like to leave things unanswered...

If you have tried to select both "Keep screen awake" and "Always use proxyimity" in "Call settings", then the problem is most likely hardware side and not cm7 related - at least people asking or reporting such issue here have solved it as so.

So the old answers to the old problem are:

- clean and dry your screen;

- make sure no screen protector covers the proximity sensor area;

- get an app from the Market to check proxy readings and if you do not get all zeros (dead/non functioning h/w) try to calibrate it;

- adjust the torque of the top-right corner screw at the back on the phone (inside);

- if all the above fails, open up the phone and make sure that the sensor is set properly and that nothing is stuck between the screen and sensor itself

You can't really expect a magic answer to a quickly described problem and by asking people to read a thread where many people have reported a similar problem with more or less success... Have you tried any of the solutions listed there or anything at all to solve the issue?

Sorry to answer this way, but we have to be more pro-active when seeking help here...
[Defy Android Development] oSandmaNo:
Why MMS when you have whatsapp? :confused:

Over here a single MMS costs the same as calling someone for 10 minutes. Plus the recipient recieves a link that will take him/her to a website where he has to enter a passcode to download the MMS! Not like before :banghead:
[Defy Android Development] Llamatron:
Some people have phones without internet on it, and I have unlimited MMS, why would I use a 3rd party app to do something my phone should already be able to do?
[Defy Android Development] measel:
the old forum problem:

people (including me) tend to project own experiences on others. Meaning: Someone wants a solution to a problem and not an advice how to do it differently... I hope you know what I mean.

I NEVER ever used MMS and have no idea why I should use it. But if someone wants it to work, then we shouldn't question his/her motivations but rather help, or... well not help. ;)
[Defy Android Development] [] AL []:
Well, why have whatsapp then? I know I don't; nor do I have fb, twtr or even YT on my Defy for that matter and I survive very well so far thank you ;)

Here, 1 MMs costs about the same to send (free on reciever side) as would a daily allowance of 1Mb of data on a SLOW2G internet browsing and only takes a single press on a "Download" button (in the worst case because I believe that I've recieved a few before w/o even pressing it)...

So let's not just generalize from our own personal usage profile and let's look at the bigger picture and let's answer this together: where in the world can we sill find (and also will find for a good while from now) the most smartphones per square in/cm?

I'd have to verify and think more about which exact files are which [I haven't touch those for months...] but perhaps your .9 files are messed up, perhaps an unrecoverable error on your sd card, perhaps something go messed up somewhere... the list could be long and I don't think this thread is the place to continue this topic on -btw...

[PM me instead if you really believe I can help you. thx]

But sorry the only help I can bring you for now is written above basically: that zipped SystemUI.apk file works fine for me on the same nightly build and with my theme applied. So try to reproduce that first and again: nand backup, redownload nightly, install it + my zip + theme and see... If that fails a complete data backup (with TB, SMS2SD and alike) and a fresh CM7 install from sbf flashing never hurts.
[Defy Android Development] oSandmaNo:
I see!! :D

Sorry :)
[Defy Android Development] LeopardSurd:
Those settings were already done, I don't use screen protectors. The sensor is fine.

I'l try to make the hints posted by you in red. Thanks!
[Defy Android Development] wmiki75:
Wifi

Any CM7 ROM, does not see this wifi netwrok:

http://kepfeltoltes.hu/view/121021/defycm10_12-10-21-11-27-59_www.kepfeltoltes.hu_.png

CM10 connected it instant.

Any idea, why?

(I do not like CM10 power widget, and few settings)
[Defy Android Development] sayonara0:
^^^ iirc in cm7 by default the highest possible wifi channel number is 11.
[Defy Android Development] wmiki75:
can i set more wifi channel scan, in somewhere?
[Defy Android Development] maniac103:
Settings -> Wireless networks -> Wifi -> Menu key -> Advanced -> Regulatory domain :)
[Defy Android Development] Force F:
Hi everyone

Im really new to the motorola flashing and rooting i read most of the post but still abit confused

Can i install this rom on my defy+ and use same instruction posted on page one

Also gapps link which one i can use there is too many in the link provided

And is kernel already included in the rom or do i have to install it.

Really appreciated any help
[Defy Android Development] popadic022:
if you have defy plus you don't have any kernel (already have gb kernel), you only need to have rooted phone, download last maniac 103 release ( https://github.com/maniac103/android_device_motorola_jordan-common/downloads ) and install. root phone is different for android 2.3.5 (use superoneclick) & 2.3.6 ( http://xdaforums.com/showthread.php?t=1216982 ). and don't forgot to add google apps after install rom or you can add apps to rar file before installing rom. :)
[Defy Android Development] Force F:
Thank you so much i did hit the thanks for you :)
[Defy Android Development] ktmbikerman:
Go to:

Settings > Wireless networks > Wifi > Menu key > Advanced > Regulatory domain

and set it to 13
[Defy Android Development] bettlejus:
Hi all,

I have a stupid problem that bothers me very much

Some days ago a friend made a joke by changing my ringtone to something nasty sounding

Ok so far, I said, ok, I will chagen it to something else from Sound-Ringtone

Change it, set another one from the list, but when I receive calls the phone plays the ringtone that my friend set up,not the one I have changed from Phone Ringtone

I even deleted the sound file used for the ringtone, and now it won't play anything, it just vibrates

No matter what ringtone I choose from the list the phone won;t use it,. it;s very annoying, it;s like the phone has a secret setting somewhere that tells him what ringtone file to use, and it doesn;t takes into account my ringtone set-uo from the Phone Ringtone menu

Anyone can help me?

Motorola Droid Cyanogen 7
[Defy Android Development] sykoism:
A simple method to solve:

Rename the ringtone you want to use to that your friend had set.:p

Seem that wiping data is the permanent method to solve your problem.
[Defy Android Development] wmiki75:
I can not find regulatory domain, in cm7 :(

there are only "Wifi sleep policy option"

:(( i unable to find ch13 workplace router?

i insert to system/build.prop

ro.wifi.channels=14

and it finally works!!!
[Defy Android Development] maniac103:
You didn't fiddle around with build.prop, did you?

If you did, set ro.debuggable back to 1.

If you didn't, what's the build you're using?
[Defy Android Development] wmiki75:
cm-72-20120923-NIGHTLY-Defy.zip

i can not find "ro.debuggable" row in bulid.prop

insert it?

OK I find THE SOLUTION the Wifi problem

I must insert the:

ro.wifi.channels=14

line in the bulid.prop and the Defy find the Wifi router, on my workplace

THANK YOU
[Defy Android Development] ktmbikerman:
I'm really enjoying the speed and stability of CM7 again, especially the battery life is great...

One thing I do miss that CM10 offers is the option to switch off the notification LED during quiet hours.

Thanks maniac for continuing to make this rom one of the best the Defy will ever run.
[Defy Android Development] juried:
+1!

There are very few issues as far as I can see... one thing is that it seems the proximity sensor response after ending a phone call is intermittent - sometimes it works, sometimes not.

One other weird thing I have found, is that I set up a task in tasker to start car home when the phone connects via bluetooth to my car. Th weird thing is when I close car home, then the camera si up and running. Not sure when it gets activated..
[Defy Android Development] ktmbikerman:
Deep sleep Issue

I'm having deep sleep issues on the latest maniac defy plus build... sometimes the phone sleeps well, other times not. can anyone advise what the best way is to check what's causing the awake time?
[Defy Android Development] Llamatron:
I used BetterBatteryStats for that, well worth its price imo, and I don't know about a free alternative

https://play.google.com/store/apps/details?id=com.asksven.betterbatterystats&feature=nav_result
[Defy Android Development] measel:
BetterBatteryStats is free for xda members. search for the thread. ;) but good that you're supporting the dev.
[Defy Android Development] manoutch:
maniac103 *cm-7-20121018* Defy+

Hello, i'm trying to install last maniac103 build for Defy+ (cm-7-20121018) but i'm stuck in bootmenu: green led-red led etc.. but no problem with euroskank built ( CM7.2.0-20121010.2116-Defyplus)

My way to install:

full wipe data and cache and dalvick.

install zip.

Kernel: see my signature.

Can someone please tell me why?
[Defy Android Development] measel:
as far as I know you do not need to flash a kernel, since you own a defy+.

while you deleted your data anyways you could try flashing original (gb) sbf and start from scratch.

good luck (and don't forget gapps ;) )
[Defy Android Development] manoutch:
Thx, but don't want to flash again a sbf.

Last Quarks cm10 and other cm7 works with my system configuration, so don't understand why is different with Maniac103 built :confused:
[Defy Android Development] popadic022:
after one week on last manic103 rom, here is impresions:

1. fast, stable, good battery life, no reboots,....

2. "call bug" is not fixed (sometimes vibrate after end call, sometimes not).

3. after call only black screen, cant end call ( i must press power button to screen on "wake phone", then end call).), even the other side end call, call isnt end.