yashsingh1/xdaforums huggingface dataset:
[Defy Android Development] Proverbs2:
still no transparent status bar :(

I still can't get the transparent status bar mod to work on Maniac's latest build. I re-downloaded the nightly, modified the SystemUI again, and even tried installing the modified SystemUI on another phone, which I was upgrading to CM7 for a friend. I did a full data wipe, and also wiped cache & dalvik, before installing. The status bar always remains black on the homescreen (though it is semi-transparent everwhere else, including on the lockscreen, in every app, and during transition animations).

I'd prefer not to use another theme. I've been using my own semi-transparent png files to create a custom theme that I like very much. (And yes, I did add those files into AL's SystemUI.apk before flashing.) The files I've edited are the following:

shade_bg.png

status_bar_background.9.png

status_bar_close_on.9.png

statusbar_background.9.png

On all previous builds up to and including the September 14th build (which I had been using until I upgraded to the latest), replacing those files with my custom ones always yielded a beautiful semi-transparent status bar and notification pulldown menu. Now, it no longer works. I'm sure there is no problem with the edited files themselves, since I copied them directly from the zip I had been using (which still works perfectly when I flash it) into the SystemUI of the latest build.

If anyone has any ideas of what could possibly be going wrong, I’d be grateful.
[Defy Android Development] [] AL []:
I do have some ideas but I don't know if I really feel like sharing them now...

2 replies ago, I've asked you to compare your SystemUI.apk with mine and even gave a link to a s/w to do so: you've ignored that.

I'm not forcing you or anyone to use my theme I was suggesting you to do my zip + my theme as a TEMPORARY debugging step - which you've ignored also.

I've asked you not to use this thread but to PM me first to try to solve this and you've also chose to ignore that...

Your modded pngs are probably NOT the issue here (why not share or attach them anyway in the first place?) and it's most likely the way you pushing the SystemUI.apk to the phone that is. You say that you've replaced your pngs in my SystemUI.apk ...but which zip did you flash exactly? Again, not mine isn't it?

And I'll stop here because I admit that I'm a little.... let'say... annoyed.
[Defy Android Development] Proverbs2:
I'm sorry if I offended you by posting here instead of sending you a PM. Since your previous suggestions hadn't worked, I didn't want to bother you personally; I just hoped that someone else here would be able to help. In the future I hope you'll be a bit more polite, but thanks anyway for the reply.

I did not see the point in doing a file comparison between your SystemUI.apk and mine, since I had already tried your SystemUI.apk (after adding my modded pngs to it using 7-zip), and the result was the same.

I don't believe that my method for getting the modified SystemUI onto the phone could be the problem either. I always just add it into the CM7 nightly zip file (using 7zip) prior to installing the nightly. (The CM7 nightly itself is the zip I was referring to. Sorry for being unclear about that in my previous posts.)

I thought perhaps there was another png file that I needed to make transparent; that's why I listed the files that I had already changed. Alternatively, maybe there is some background png file that wasn't being used in the older nightlies but is being used now? I'll try installing another theme temporarily, as you suggest.

Edit: and by the way, I'll be happy to share my modded SystemUI.apk as soon as I get it working again. I've already done so several times in the past (in this thread).
[Defy Android Development] [] AL []:
So very politely...

When I started to use to transparent mod (also months ago) I first tried to do like you've now described and replace the SystemUI.apk within the nightly zip before install. The result of that was that I either had a black statusbar or even none at all. So I quickly realized that modding a signed nightly zip is not the best thing to do - especially replacing such an important file as SystemUI.apk AND without re-siging the zip.... So the best way to do it is to use a separate zip file with your mods and sign it (even with temp keys) and flash it right after an unaltered nightly. I've been doing that since and never had a problem until sometimes last month when the TLS support was implemented; just around the last nightly you've used your mod successfully.... This in turns, [as maniac103 kindly explained a few pages back] just required to include a recent nightly's update-binary within the patch.zip [in signed.zip\META-INF\com\google\android\] to rectify the problem.

I don't see why you write that my previous suggestions didn't work because you still did not try them [namely: nightly + my zip + a transparent theme].

Alternatively if I you would have supplied us your transparent files, I could have put them in my zip and re-sing it, but you didn't.

If you don't want to use a separate zip, there are also alternative methods to push the file on a fully installed and booted up nightly build.

There was one such method clearly explained in a link that I previously gave you (have you read it or tried it?) or you could also push it through adb.

The first thing I wrote to you is that the tweak works for me as usual so I doubt that any new (SystemUI.apk) file has to be modified, but you seem to keep focussing on that and maybe miss the important info...

And that's really all I have to tell you on this now...
[Defy Android Development] Proverbs2:
Ah, that explains it! Thanks a million. I'll push the file after installing the nightly.
[Defy Android Development] G3Sidhu:
changelog of new nightly?

cm-7-20121025-UNOFFICIAL-jordan-signed.zip
[Defy Android Development] popadic022:
+1
[Defy Android Development] difr:
maniac103, explain, please

>adb shell ifconfig usb1 down
ifconfig: SIOCSIFFLAGS: Permission denied

with cm7 by Fuzz I had no such problems.

"Root access" option (apps&adb) has no effect on it.

now I use

>adb "su -c 'shell ifconfig usb1 down'"

it works, but...

why? :)
[Defy Android Development] [] AL []:
In fact no; what you've quoted only explains how to properly make a 'patch'.zip on a recent nightly, It's what you didn't quote that might explain the problem you're experiencing. ;)

As far as I can see, only one commit being a Power VR clock speed tweak from Quarx.:

"Refresh PVR modules.

Improves performance when not on performance governor by including this patch:

https://github.com/Quarx2k/jordan-kernel/commit/108cd2c41c59b198e158a7c7747ecded26b3d7ab"

Performance improvement always interesting to see and try :silly:

Edit:

sorry the commit was from SkrilaxCZ:

"Fix low performance issues for vdd2_opp below 3

commit 108cd2c41c59b198e158a7c7747ecded26b3d7ab 1 parent 6da1ceea87

SkrilaxCZ authored a day ago

Quarx2k committed a day ago"

and not clockspeed but bus speed...:

+ if (cpu_is_omap3430())
+ /* pin the memory bus bw to the highest value */

Edit #2

for LeopardSurd and:

--> you guys have tried increasing your lower clock vSel by any chance?

Radio change +sensor + waking up phone need juice at 300 MHz... ;P
[Defy Android Development] maniac103:
adb doesn't have root access by default in my builds. To enable it, you can use 'adb root' (if allowed in the settings).

---------- Post added at 03:47 PM ---------- Previous post was at 03:46 PM ----------

+ a fix to the music app (correctly resume music playing after a call).
[Defy Android Development] difr:
I see it, thanks.

so even if I've switched "Root access" option to "adb" (or "apps&adb") I must prefix every "adb shell" command with "su -c" anyway? (looks like so)
[Defy Android Development] maniac103:
No. As said: Just run 'adb root' once after connection, afterwards, adb will have root access.
[Defy Android Development] LeopardSurd:
Tried it already. No effect. Also, my Defy+ is 4 steps overcklocked (to 1200) and the Vsels have normal values, they are not untervolted.
[Defy Android Development] Robi959:
Is this work on Defy+ .. http://download.cyanogenmod.com/?device=jordan_plus&type=stable or something else ?
[Defy Android Development] popadic022:
works.
[Defy Android Development] kapil_dheer:
I tried to update to the latest nightly the usual way......but this time stuck at bootanimation....did nothing unusual.

Had to revert back to my nandroid of 18 nightly.

I have a red lens defy and installed a defy plus build on gb kernel.

He nobody faced the same situation...i'll give a second try...
[Defy Android Development] [] AL []:
Unless you flashed a bl6 or 7 sbf, the defy plus nightly brings you no advantage over the regular one. (and might wven cause problems w charging) So if it's not the case, probably better to stick with the defy build with a kernel included (none in +)...
[Defy Android Development] popadic022:
try to put custom rom on sd, go to recovery, wipe data/cache. install rom.

i alslo have bootloop after install new build (i was change bootananimation) but i instal again and everything is ok (change to original animation).
[Defy Android Development] oliyoup:
I have a Force Close with parameters when I want to save my changes in the brightness levels of display (define other levels in automatic backlight menu).

Am I the only one having this problem?
[Defy Android Development] measel:
which build?
[Defy Android Development] maniac103:
What values did you enter?

Please provide logcat.
[Defy Android Development] oliyoup:
oops, sorry I made a mistake, I am in the wrong thread, I just installed CM10 for a try, I am so used to read this thread...

I take this opportunity to say congratulations and thank you for all your work.
[Defy Android Development] diogo.sena:
Well, since defy+ clock goes up to 1000 by default

Using 1200mhz clock with 1000mhz vsel, is an overclock AND an undervolt ;)
[Defy Android Development] popadic022:
is there any chance for fix "end call bug" in future releases?
[Defy Android Development] LeopardSurd:
No, when I set the 4-th clock to 1200 I changed the vsel too, over 60 (I don't remember exactly, it is a vsel used by Motorola Milestone with 1200 by default).
[Defy Android Development] Proda:
Quick question. Can you guys use catlog app in previous maniac build? I can't use it in White Rabbit 1.8beta2 which is based on previous maniac's build.
[Defy Android Development] measel:
works here on maniac 18 AND 25
[Defy Android Development] kapil_dheer:
Finally did a clean install and reinstalled the apps.....do see a speed increase.

I joined back cm7 15 days back. Tried quarx's cm10. The rom is just awesome......being on cm7, always kept track of it.....they recently solved battery drain issue with Walter offering his umts and batteryd files......used on maniac's latest defy plus build on my defy and the battery life seems getting better....been using it for 8 hours now......link as follows....

http://xdaforums.com/showthread.php?p=33254749

Is It real or placebo.....maniac maybe can analyse this.....there files are only for defy red lens not defy plus.
[Defy Android Development] bhupatib:
Coming back after 5months of CM9/CM10 joyride, I'm pretty surprised by CM7.2's progress. At times it feels so smooth (with scroll cache enabled ) that it can shame HWA! There is comparatively obscene amount of free memory with apps staying in background seemingly forever :P Data disconnects are much reduced and reconnects seamlessly (downloadeded a 140MB file without having to manually toggle data multiple times) and battery life is back to 1%/hrs on 2g.

Price of progress?

That aside, today I got a strange "blackout" on maniac's latest (MB525, Red). It wasn't a shutdown as mashing the power button didn't wake it and only reinserting battery powered up the phone. Things are normal since but I guess it's the RIL problem that measel confirmed on his thread. I'll try to recreate.
[Defy Android Development] sayonara0:
dunno, but for me it is 6mA vs 20 mA per hour in deep sleep according to Battery Monitor Widget.
[Defy Android Development] DeeKay11:
I rarely experience crashes on CM7, but there is an issue that sometimes causes reboots, which I don't fully understand but have a crude solution for.

Occasionally, when turning on the phone or (very often) when unplugging it after USB sharing, the system would become very laggy, sometimes completely freeze and eventually reboot itself (after a few minutes).

Looking at CPU utilization through a task manager, you'll find it nearing 100%, but there are seemingly no processes that eat up CPU at all, except 'system' (at first) and 'android.process.media', that takes about 10%-15%. Now, with the prior there's not much you can do, but killing 'android.process.media' instantly stops the CPU usage.

What I did is to simply add the following commands to run at each startup of the Terminal app, and just type "km" a few seconds after the SD card has been loaded following a USB disconnect:

export PATH=/data/local/bin:$PATH
su -
alias km="ps | grep \"android.process.media\" | awk {'print \"kill -9 \"\$2;'} | sh"
echo "km alias set to: `ps | grep \"android.process.media\" | awk {'print \"kill -9 \"\$2;'}`"

I noticed that the system starts the process again eventually, but I don't know whether there's any damage done.

It worked for me for the past few months anyway.
[Defy Android Development] [] AL []:
Well, no advantage was maybe pushing it a bit; one can just think of HD video recording being one of them...

[Although with very limited tesing, I seem to get better results with Wide setting...]

But I would truely like to believe those deepsleep numbers; not that I don't trust you, but I'll have to replicate that for myself...

6mA is what I get at night in airplane mode (no wifi either) with the regular build; I get around 14mA in standby during the day and that is with 2G + wifi on/no data.

You mind sharing a bit more details on what GB kernel you use and what CPU clocks/voltages you're doing the comparison with?

Anyhow, I'm running the plus build now, so I'll test this out for a couple days...

And if there are others

red lenses (ONLY!!)

owners that want to do some testing as well, I'll try to save them some trouble by attaching 2 cwmr zips to flash right after the nightly. The GB kernel is the CM9 kernel from Epsylon3's builds website and the battery fix [sorry maniac I know you don't like to see those around too much...] is one that Auris provided somewhere before. Although, I've updated the two files to include a recent nightly's update-binary; so that they work fine with post TLS support builds (Sept 2012). They work; I used them to install Oct 25th-plus build.

Edit:

the CM9 kernel attached is the kernel-gb-234.zip from here including boot and devtree [and recent update-binary]

I'm also attaching an additional Kernel (5 month newer than the other..); the 4.5.2-109_DHT-22 from walter79's MSGinger thread [with same devtree and update-binary].

--> Btw, I've tried them both for almost a day each and I see no difference whatsoever in deep sleep's current draw between regular jordan and jordan-plus buidls... ;) Still looking for more info/proof on how to go from 20mA/h to 6 :silly:
[Defy Android Development] wmiki75:
at me, Camera do not find SD card :(

?maybe conflict with debug mode, or i do not know why
[Defy Android Development] bhupatib:
Well for me the crashes happened in a different scenario and I've been able to somewhat recreate them: Browsing on opera mobile with a couple of heavy pages loading (in poor cell reception) or copying a file to a >100mb zip in xplore. The crash causing event in both of these fairly normal usage case was that I'd manually locked the device midway during their operations.

Configuration: SBF-clean install, maniac1025, Red MB525, 1000/600/300MHz @ 55/45/25, Boosted

So the conclusion I can draw from my rather unscientific observation is that the crash perhaps occurs due to the aggressive CPU screen off profile (boosted=smartass++) or due to the RIL trying to reconnect, when the device was loaded.
[Defy Android Development] Llamatron:
Follow up to my MMS problems, I definitely couldn't find a way to make them work properly on Orange FR, so I just switched carrier and now receive MMS properly. Yes it's a bit of a defeat :(

But while playing around with settings I noticed something: the size of sent MMS is determined by the values we have in mms_config.xml as changing them changes the size of sent MMS, but it sends them around half thoses values (for example 324x242 while the settings are set to default at 640x480). No idea if it's a bug or a feature. I could send much larger pictures ignoring thoses settings by using ChompSMS so I guess it's not a carrier limit reducing the pictures so much.

As I'm aware it seems very few people use MMS, having them unlimited in my plan, and having done a bit of java before, I installed android SDK and CM's source code following a tutorial but my first build attempt have been unsuccessfull. I'm also still a bit lost with what I see in the folder for Mms.apk, but I'll keep trying and probably try to use maniac's source to start with, when I figure a bit more how to use github.

In the meanwhile if someone with more knowledge than me understands the code for Mms.apk and finds a way to have the pictures sent at the proper resolution (640x480 seems standard and is a good size/quality compromise), be my guest :p

I hope I don't annoy too much with my MMS obsession :D
[Defy Android Development] diogo.sena:
I bet that change vsels to stock will solve this...
[Defy Android Development] [] AL []:
Well, sorry for the obvious question, but have you tried to increase the default mms_config.xml value to 1280x960?

I can't help you with building from source since I don't have a Linux pc (and my old cpu doesn't allow virtualization...).

But since this Mms.apk is a system app, it should be relatively easy to decompile, do that change and recompile it.

I might try it later or tomorrow [although I do not have an unlimitted plan and it will cost me money to try it out afterwards :crying:] :silly:

That reminds me that I still haven't figured out what Maniac wrote about the Music.apk and the "Videos" app tray icon...first part of this post still crying :laugh:

I'd pretty much follow the same kind of procedure for your issue here...

Oh! I almost forgot why I've decided to post this reply in he first place: it was that I've just found another issue with SMS today

- maybe an old and known issue, idk- but if anyone could confirm the problem on their setup, I would really appreciate...

--> See pic attached it's pretty much all explained on there. [edit: just press and hold the "c" key to get that "ç" character]

I've reproduced this problem with three different Mms apks that I have.

So I have no clue if that means that it is related to cm7 or not...
[Defy Android Development] LeopardSurd:
Tested it on my stock Defy+ ROM (GB). There is no such issue. Perhaps is CM7 related. Strange enought.
[Defy Android Development] bhupatib:
Hmm...don't think mine is too low but will try.
[Defy Android Development] Llamatron:
Yes, it resizes to 648x484, not 640x480.

EDIT: tried your issue and it is the same for me, but I red on some french carrier forum that it's a SMS problem with some special characters.

EDIT 2: still haven't managed to compile, but I think I found where the image resize happens: in com/android/mms/ui/UriImage.java , at line 202 if scaleFactor could be a float maybe it would be possible to set its value using the limits instead of in this while loop, tho I'm a bit afraid there's reasons why it's an int :/ maybe a quick and dirty fix could be replacing scaleFactor *= 2 by scaleFactor++
[Defy Android Development] adiq_ambro:
That's not an issue. SMS with non ASCII character has limit of 70 letters.
[Defy Android Development] Llamatron:
I finally managed to compile Mms.apk (by using and building the official Cyanogen sources, feels a bit like squashing a fly with a nuke).

With scaleFactor *= 2 replaced by scaleFactor++ , the same image I was using for testing and was reduced before around 320x240 is now resized to 518x387, and the conversion to mms just take a tiny bit more time, but I'm still wondering if there wouldn't be a way to maximize the resolution within the preference's limits.
[Defy Android Development] popadic022:
is there any chance for proximity sensor fix (call end issue). for me it's only "bug" on cm7. can that sensor work like on stock rom?
[Defy Android Development] Llamatron:
Mission acomplished, after trying to make the resize scale a float in the CM7 method, and for some reason always having images slightly bigger than the max as result, I used my pro copy/paster skills to replace the method used to resize images before sending them in a MMS by the one in CM9's as it uses a float for the resizing. I then changed the way it was calculating which scale to use and bingo: I has max resolution MMS images.

As the images at 640x480 were way smaller than the max size of 300kB, I also changed the default jpeg compression rate from 80 to 90, which doesn't make the file a lot bigger.

I attached the modified source files if some dev wants to include the change in his release. If you want a flashable zip check AL's post on next page.
[Defy Android Development] LeopardSurd:
I must say that the bug with screen off during a call is pretty annoying in CM7. For 3 days I use the official Defy+ GB rooted stock ROM and have no problem with this bug.
[Defy Android Development] popadic022:
its only problem with cm7. i used for 1 month stock rom and everything works ok. now i use cm9-mig edition for few days without that bug. i try to copy sesors file from stock to cm7 and nothing. i see that sensor on cm work only in landscape mode (glow red lamp) in portrait mode not glow. if work on stock and cm9, why not work on cm7? everything else is perfect.
[Defy Android Development] LeopardSurd:
What about CM10. Does it has this bug?
[Defy Android Development] DeeKay11:
This bug exists on both CM7, CM9 and CM10 and is commonly referred to as a sensor issue (or cheesy drivers/libs). There are two workarounds for this problem:

* Put your thumb above the sensor and lightly press on the screen at that point for 2 seconds.

* Get a Torx screwdriver and do this: http://www.youtube.com/watch?v=uMk1S90MjbY

I still get screen locks after the 2nd workaround, but a lot less often.
[Defy Android Development] popadic022:
i never used cm10.
[Defy Android Development] [] AL []:
Good work!! -thanks!

I played around again with Mms apks today and also tried yours and it does make mms pictures bigger and better.

Although I still don't get the logic behind the resizing (nevermind explaining but); here's two examples of what I got:

i) original pic: 1280x854 137KB (1.1MP)
cm mms: 640x427 44KB (0.27MP) <= scaled down 4:1
llama's: 640x427 66KB (0.27MP) " " "

ii) original pic: 5184x3456 4.45MB (18MP)
cm's: 324x216 9KB (0.07MP) <== scaled down by 250:1 !!!!!
llama's: 640x426 43KB (0.27MP) <== scaled down by 66:1

So example #2 shows that stock cm7's Mms.apk clearly has problems with big pictures resizing...

--> what the heck!, see the difference by yourself [pics attached]

OK quickly..: your flashable zip wasn't one at all; I don't know which 'easy enough guide' you've read, but

you were missing the whole META-INF folder !!!

You can have a look at my guide on this maybe; updated just recently in order to work on recent cm7 nightly builds post-TLS support (Sept 2012).

Anyhow, I've re-zipped your modded Mms.apk and I'm attaching here.

And I had a go at finding out what you did and I tried to do it on a different Mms.apk that I'm currently using [and posted here 2 weeks ago - but since then themed a couple notification icons, emoticons and the app icon] and "mission accomplished" it worked for me also.

So I'm attaching it also for whoever might be interested in trying it out.

So thanks again for your work/mod [and to be kind enough to point us to where the changes you've made were].

Cheers.

/AL