yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] TheSgrash:
hi all,

i flashed the 11 juve nightly but how can i activate the app2ext mode and move automatically all my aps from /data to /sd-ext/data???

i read of a fix: where can i found it?

thank you
[Miscellaneous Android Development] aorth:
Hmm, I see some stuff about swap there. Are you enabling swap somehow...? I know we have ramzswap, but I've never seen that message before...
[Miscellaneous Android Development] psyke83:
It's a long-shot, but try rebooting to recovery and wiping your dalvik cache.
[Miscellaneous Android Development] wbrambley:
I'm using swapper 2 and a swap partition, I think its better than chewing ram and I haven't managed to kill a SD card yet.
[Miscellaneous Android Development] wbrambley:
Been there, wiped everything. Formatted system and re installed then restored data backup.

Gave up and started fresh now with 1/7 official and wifi fix.

Will let you know how it goes, all good so far.
[Miscellaneous Android Development] GJSmith3rd:
Swap Partitions, Swap Files and Comcache

Information found at the following link from the CyanogenMod Wiki states that Swap or Compcache (compressed ram swap) can be verified by using an ADB shell and typing 'free'.

http://wiki.cyanogenmod.com/wiki/Swap_and_Compcache

I have Compcache enabled and I also have a Swap partition on the SD (just in case it could be used by a ROM) and my swap information from 'free' reports 0 swap usage. Maybe a conflict between Compcache and Swap Partition?

Also. I'm running June 11 build with V6 Super Charger and Link2SD (all apps and libs linked to ext sd partition and dalviks on internal) without any problems or reboots. Perfect! Thanks.

Finally, I have a small quirk occasionally that when I disable the lock screen, via notification power widget, my CyanogenMod custom home and search softkey settings do not function. If I enable lock screen again from the power widget they function as configured,
[Miscellaneous Android Development] wbrambley:
battery saver?

Hi, is this also valid in our gingerbread build? https://github.com/ferhung/android_...mmit/7203672aac2afca54c9a6cfb0c57d7ec30a06d15

It may explain why I've seen apps that use the compass using battery after they have been killed/exited.
[Miscellaneous Android Development] psyke83:
That will change the akmd service to never run, which will probably mean that the compass would never work...

Will it improve battery? Yes, just because the sensor will never be used... ;)

Edit: no, I was mistaken. The sensor library will start the service on demand, so it's probably best to disable it. I already have the service disabled in my U8160 port.

aorth,

If you're going to try this, don't use the "oneshot" service property. Even ferhung changed this in a later commit: https://github.com/ferhung/android_...mmit/2381af8154bfb140669e561b060065b506ed8e5f

Adding this may also reduce battery drain for wireless, but I haven't tested it properly:

on property:init.svc.wpa_supplicant=stopped
stop dhcpcd_wlan0

The biggest problem we have with battery, however, is the wakelock triggering in the rpcrouter_smd_xprt driver every 30 minutes or so (while the phone is idle). Each time the wakelock triggers, the phone exits and eventually re-enters deep sleep. This continual process drains battery.

On my Samsung GT-I5500 port (msm7x27) with a 2.6.32 kernel at the same baseline commit, this wakelock never triggers. I'm not sure if it's a bug with the msm7x25 chipset, Huawei's modifications, or perhaps something we're missing in the CM7 port needed by the RIL proprietary files...
[Miscellaneous Android Development] Hetfield666:
@aorth

did you try the

ro.ril.fast.dormancy.rule=0

in build.prop?

it looks like to decrease battery usage (in theory it should decrease but it's buggy)

can i ask you the status of "pending" stuff?

1) some adriano's audio changes

2) some adriano's pixel patches

3) latest CM code

4) some psyke's changes not ported from u8160

5) this compass change

anything else i'm missing?
[Miscellaneous Android Development] psyke83:
That's a voodoo property. It doesn't exist anywhere in the CM7 source, or in the proprietary Huawei blobs.

It may work on another device that has this support patched in by the vendor (either in the framework, or the proprietary rild/libril, etc.), but it's simply not used at all on the Huawei U81x0 devices.
[Miscellaneous Android Development] Hetfield666:
that's why i could not find it in our build.

i saw lots of guys talking about it.

ok, discard it so :)
[Miscellaneous Android Development] psyke83:
I just noticed something. If the compass is used, the akmd service will start. However, when the compass sensor is released, akmd continues running. This may be a possible culprit for random battery drains...
[Miscellaneous Android Development] Hetfield666:
psyke, anything about the camera too?

i "feel" but i may be totally wrong, a similar issue, after the camera app closes it looks like the battery usage i a bit higher.
[Miscellaneous Android Development] aorth:
1) The libaudio I have are still here, waiting to be merged into CM (they're in all of my builds, though): http://review.cyanogenmod.com/#/c/17091/

2) I compiled a build with the pixel patches, but never uploaded it. I kinda got hung up on the wifi issue for wbrambley. I'll upload one this weekend I guess.

3) yahhhhhhhh. Though gingerbread is really a ghost town these days, not much "new" CM code merged lately: http://review.cyanogenmod.com/#/q/status:merged+branch:gingerbread,n,z

4) Most of psyke's changes are in my builds. I never pushed the source to CM because I got busy, and I wanted to make sure they didn't break anything (open-source gralloc, copybit, etc), and I have too many patches pending in CM anyways, and they'd all conflict with each other.

5) I don't have much time for original research... I'll wait until people have something more concrete to start testing.

It all takes time. :)
[Miscellaneous Android Development] indieguy:
WiFi issue

Hi guys!

I've flashed this build, but the problem i had with the RC0 is always there.

I can't get working the wifi connection. It askes for my WPA key but it seems to can't establish the connection.

I tried to take a look at the "possible fix" but I can't see how to fix it.

Hope someone can give me an advice.

Thanks a lot :fingers-crossed:
[Miscellaneous Android Development] psyke83:
aorth & ac1953,

I noticed a few people remarking about instability/random reboots on your recent builds. I'm getting the same feedback on my U8160 build as well as my Samsung galaxy5 port.

In the case of the galaxy5, I changed quite a bit (upgrading from a 2.6.32 to 2.6.35 kernel, with untested drivers), so random reboots are not too unexpected. My U8160 port, however, doesn't have any significant recent changes. Some of the U8160 users tested an older kernel from a known stable release, and their phones continued with stability problems.

At first I thought it was a bad patch that I applied from the pending list on gerrit, but now I'm thinking that it may be code shared between the three devices (U8150, U8160, galaxy5). One thing that comes to mind is Adriano's new libaudio, which I have also adapted for my Samsung port.

Well, I've removed all patches from my local source, reverted libaudio to the older version and gone back to the stable 2.6.32 kernel for my galaxy5 port... I'm waiting for feedback on stability from my users. I may try something similar with my U8160 port soon, too. I'll keep you updated if I find anything that may be useful for you guys.
[Miscellaneous Android Development] Hetfield666:
actually adriano did several libaudio revisions.

i'm stuck with last u8150 may's version and had no reboots at all.
[Miscellaneous Android Development] tulangabol:
DSP Manager Lag with default governors and default cpufreq

I can't enable dsp manager with default settings in CM7.2...

I try to add this line in init.rc :

#/* < DTS2010070701414 guoyun 20100707 begin */
#Add scaling method for MEDIA
on property:audio.governor=1
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor performance

on property:audio.governor=0
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor ondemand
#/* DTS2010070701414 guoyun 20100707 end

But not help with this issue...

Any suggestion please???

But i want use dsp manager without change min-max cpu settings...

I use sd card card class 2 or 4 (I don't know what class my sd card)

---------------------------------------

I'm try to add this line in my init.rc :

# /* < DTS2010080902195 wanghao 20100809 begin */
# Add change CPU frequency method for performance
on property:powersave.cpufreq=1
write /sys/devices/system/cpu/cpu0/cpufreq/ondemand/powersave_bias 90
write /sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold 80

on property:powersave.cpufreq=0
write /sys/devices/system/cpu/cpu0/cpufreq/ondemand/powersave_bias 0
write /sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold 60
# /* DTS2010080902195 wanghao 20100809 end > */

But in my research nothing happen with that line command (change default to ondemand before that)...

I want to get scaling freq cpu to get best performance...

Sorry for my bad english

Thank you...

Use CM7.2 updated 11 June with boot.img/kernel may 17 (i stuck in splash screen with boot.img 11 june)

---------------------------------------

Edit:

Sorry not init.rc but in init.local.rc

I add that lines in my init.local.rc because i can't compiler/build my own kernel...
[Miscellaneous Android Development] aorth:
psyke, it's possible. It seems the instability came in around the May 17th build, at which point I added the new libaudio. I had been thinking it might be WPA Supplicant 0_6_X, because I also moved from 0_5_X to 0_6_X starting in that build.

It's worth noting that official CM builds for U8150 don't have the new libaudio, and I believe we've had reports of random reboots on those builds too. Ironically, the libaudio was just merged into CM by arcee lastnight. Heh.

Keep us posted. Cheers.
[Miscellaneous Android Development] Hetfield666:
as mentioned before i'm using 17th may and had no reboots at all.
[Miscellaneous Android Development] isofra:
me too I'm using last Alan version and no reboot at all! All seems be perfect :)
[Miscellaneous Android Development] aorth:
Thanks both. That's good to hear, although makes the issue even more strange.

btw, I haven't had time to post a new build this weekend. I was busy with real life things, and rooting / porting Clockwork Mod to another device (U8185). For what it's worth, my several remaining patches in CyanogenMod's review queue have been merged finally, so when I get a chance I'll push a few more up there. This means that the next official nightlies will have the latest libaudio as well as the barcode scanner fix we discussed last week.
[Miscellaneous Android Development] psyke83:
Maybe not too strange. I'm also getting conflicted reports from my users, and I didn't see any random reboots on my devices. People have also complained that the camera stops working on my new U8160 build using joilaroi's patch that was sent upstream (but again, I can't trigger the problem).
[Miscellaneous Android Development] trekker99:
For what it is worth, I am also running the latest aorth build and I don't get random reboots either. my guess it is either some feature i am not using or it is the interaction between the rom and some software I didn't install which is the cause of these reboots.

in my case, i seldom use the camera, my wifi uses wpa2 aes, ssid not hidden. in terms of apps, i use juicedefenderplus to save battery, no fancy scripts to "tweak" my phone. if there are other things i should mention to investigate this problem, let me know!
[Miscellaneous Android Development] francois227:
wifi test fixed the random reboot (well, as of this moment, no random reboot, everything is smooth and stable). cheers!:D
[Miscellaneous Android Development] Allanitomwesh:
Haven't had a reboot in a while, but I'm suspecting the red hang up button switches off the phone. Who made it put the phone to sleep anyways? It was more convenient when it took you home,like on froyo.
[Miscellaneous Android Development] Power-Inside:
You can bring back that functionality by looking for an end button behaviour in the "Spare Parts" app.
[Miscellaneous Android Development] wbrambley:
my tests were inconclusive, less reboots but the black screen and not waking up continued. I installed the ICS build and had reboots with that too. however I have since restored a backup of 1/7 official with the wifi patch already applied and have had no problems for the last 3 days. Explain that!
[Miscellaneous Android Development] Allanitomwesh:
Worked like a charm. Neat. I don't like messing with dev tools unless I know what I'm looking for.
[Miscellaneous Android Development] psyke83:
@aorth,

I found some bcm4325 source from an LG GT540 (Swift). You can find it in the platform archive (vendor/lge/wifi) of the Eclair V20C source release: http://www.lg.com/global/support/opensource/opensource-detail.jsp?detailCustomerModelCode=GT540

Edit: actually, the kernel driver is in the kernel tarball, in drivers/net/wireless/bcm4325.

To get this working you would probably need to modify the initialization code for the Huawei, and/or adapt for the 2.6.32 kernel. Maybe it'll give you ideas if you do a diff between the bcm4329 source and this source...

I still think that Huawei's source supports the U8150 wireless, though, and we're overlooking something simple.

Edit 2: I also finished a big update of the bcm4329 source. I started from the latest version of the source in the ics_chocolate kernel, inclded some extra patches from the nv-tegra kernel fork, and finally, I added the necessary changes needed to support the Huawei (configurable via Kconfig). I also found that using the newest firmware from the nv-tegra platform/hardware/broadcom repository fixes all my problems with combo scanning, hidden networks and channels >11.

You may want to check it out: https://github.com/psyke83/codeauro.../gingerbread-dev/drivers/net/wireless/bcm4329

Firmware: http://nv-tegra.nvidia.com/gitweb/?...09a71bd9f14d34c2bbb89c5e;hb=gingerbread-tegra
[Miscellaneous Android Development] Three-0-3:
My build doesn't read sim, June 11th reads sim.

Hi,

I made nightly based on official tree (I extracted files newly from Fusion IDEOS) .

It boots up and GUI works, but no service (means can't find carrier). Settings->About Phone ->Status shows no IMEI.

Alan's 11th June version of nightly reads sim, get carrier, and shows IMEI.

I tried the Alan's device_huwaei_u8150 tree, but no service, no IMEI.

Any clue appreciated.
[Miscellaneous Android Development] wbrambley:
I had a similar problem. Was going to test the compass disabled thing. All I can think is that Alan has not uploaded his latest changes to git.
[Miscellaneous Android Development] aorth:
There's nothing in my local tree that would explain that behavior, haha. If official builds from CM work, then your builds should work. Did you try the official CM builds at http://get.cm/ ?
[Miscellaneous Android Development] mega g:
sorry, but why not resize animated wallpaper?
[Miscellaneous Android Development] Three-0-3:
Alan, Thank you very much for your info.

The official CM build works!

So my build environments for U8150 is bad (No problems for Nook Color).

Ummmm.
[Miscellaneous Android Development] luk82:
alan do you have any plan to release the new nightly with sygic patch this weekend?
[Miscellaneous Android Development] wbrambley:
Hmmm. Did you find anything in your build enviroment? I am still in same situation. builds perfectly. In fact I have built about 8 unofficial

versions today and all have the same problem.

adb logcat -b radio

http://pastebin.com/XJfyC7BK
[Miscellaneous Android Development] psyke83:
It seems that you don't have the proprietary files added to your build system. Execute the extract-files.sh script while in the u8150 folder.
[Miscellaneous Android Development] wbrambley:
I do, also re-ran extract-files.sh yesterday to be sure a requirement had not changed. 40 files on list and 40 files in /vendor/huawei/u8150/proprietary/(plus folders)

Going to set up a vm running the recomended ubuntu 10.4 and see what that changes.
[Miscellaneous Android Development] Three-0-3:
No, I couldn't find anything special. I re-checked out the branch gingerbread again, built, but no IMEI shown.

Thank you for your logcat especially "-b radio". It is same as my bad case, which begin with Network mode set to 0, and

RILJ couldn't find rild socket (at least within 8 times).

I found the good case (by official build or Alan's build ROM) began with RIL line;

D/RILC ( 127): [RIL qcril.c 2560] RadioState Uninitialized --> Radio Unavailable [Event PowerUpIniterUpInit]

(ref: http://pastebin.com/BsPNgY83 )

I'll try to find the RILC process (127 in the avobe case) is spawned or not in the bad case,

if spwaned, why died? if not spawned, why not?
[Miscellaneous Android Development] umaga2012:
The random reboots were becoming a bit of a problem for me even after flashing the wifi test zip.so I decided to install the official stable CM build.It also has reboots but not as often as Aorth's June 11th build. Hopefully Aorth will fix this in the next build. Otherwise great ROM Mr Allan!
[Miscellaneous Android Development] wbrambley:
I found the problem(sorry psyke83, you were part right). For some reason the extract-files.sh in Aorth's git does not pull libauth.so and libril.so and a couple of others. Look up https://github.com/tilal6991/proprietary_vendor_huawei/tree/master/u8150.

I coppied the files i didn't have from here and now have radio!
[Miscellaneous Android Development] aorth:
Sure. But I got busy. Also, the Jelly Bean branches just got added to CM, so now when you update CM7 repos it pulls in those too... kind a pain in the ass (and a lot of data). I just haven't had time to do that and upload a build yet. Sorry!

Sorry, the extract-files is really only there for proof of concept... it's actually not used by anyone. I haven't used it in probably a year or so... so I have no idea what state it's in. The CyanogenMod build server gets the proprietary files from a pre-built repo (and that's the one I use locally as well): https://github.com/TheMuppets/proprietary_vendor_huawei

I'll get around to fixing extract files eventually... but as you can see it's not that important once you know where the proprietary files are. :\
[Miscellaneous Android Development] Three-0-3:
The missing file is libril.so .

The missing file was libril.so in my case.

I used extract-files.sh to make u8150-vendor-blobs.mk and took two days to notice libril.so should be in the PRODUCT_COPY_FILES list.

Here is the diff of extract-files.sh:

@@ -67,6 +67,7 @@

adb pull /system/lib/libqcamera.so ../../../vendor/huawei/$DEVICE/proprietary/lib/libqcamera.so

adb pull /system/lib/libqmi.so ../../../vendor/huawei/$DEVICE/proprietary/lib/libqmi.so

adb pull /system/lib/libqueue.so ../../../vendor/huawei/$DEVICE/proprietary/lib/libqueue.so

+adb pull /system/lib/libril.so ../../../vendor/huawei/$DEVICE/proprietary/lib/libril.so

adb pull /system/lib/libril-qc-1.so ../../../vendor/huawei/$DEVICE/proprietary/lib/libril-qc-1.so

adb pull /system/lib/libril-qcril-hook-oem.so ../../../vendor/huawei/$DEVICE/proprietary/lib/libril-qcril-hook-oem.so

adb pull /system/lib/libwms.so ../../../vendor/huawei/$DEVICE/proprietary/lib/libwms.so

@@ -136,6 +137,7 @@

vendor/huawei/__DEVICE__/proprietary/lib/libqcamera.so:system/lib/libqcamera.so \\

vendor/huawei/__DEVICE__/proprietary/lib/libqmi.so:system/lib/libqmi.so \\

vendor/huawei/__DEVICE__/proprietary/lib/libqueue.so:system/lib/libqueue.so \\

+ vendor/huawei/__DEVICE__/proprietary/lib/libril.so:system/lib/libril.so \\

vendor/huawei/__DEVICE__/proprietary/lib/libril-qc-1.so:system/lib/libril-qc-1.so \\

vendor/huawei/__DEVICE__/proprietary/lib/libril-qcril-hook-oem.so:system/lib/libril-qcril-hook-oem.so \\

vendor/huawei/__DEVICE__/proprietary/lib/libwms.so:system/lib/libwms.so \\
[Miscellaneous Android Development] francois227:
have you tried flashing it over stock rom?
[Miscellaneous Android Development] masantula:
Hi guys, i haven't flashed new ROM on my U8150 in awhile, wondering how stable this ROM is for everyday use including whatsapp, sms, calling and music playing, nothing more. Thanks..
[Miscellaneous Android Development] luk82:
it's perfect for everyday use, you can flash it without worries.
[Miscellaneous Android Development] masantula:
Sweet. Thanks for the info..
[Miscellaneous Android Development] aorth:
I'm back!

I've been busy the past few weeks with work and then CM9 on my Galaxy Tab (it's stable now, w00t!). I'm going to sync my CM7 tree tonight so I can put out a test build with Sygic patches this weekend. Even if it works, the problem is that the patches are a bit invasive in the Android framework, and ac1953 still has to submit them upstream to CM for them to ever be included in an official build. Let's see if it works first...

btw, I bought the "new" U8185 a few weeks ago, I already ported ClockworkMod Recovery to it, so I want to start porting CM9 soon. Unfortunately that means less time for U8150. :) Now you all should buy new phones which psyke83 or me are playing with ;)
[Miscellaneous Android Development] umaga2012:
Nope. Will that help? The official stable rom still has reboots and so does the July 15th nightly.Or could it be a hardware problem with my device ? I'll flash it over stock then see if the problem persists.
[Miscellaneous Android Development] bartiest:
Excuse me for asking, but why chose the U8185? I don't see much difference with "our" U8150, besides the cpu. Was your U8150 showing malfunctions?

The bloke who asked if this ROM is safe for daily usage: don't hesitate or doubt between others (i saw your question pop up on a CM9 thread): This is the ROM you want. ICS-roms work, but not fluent enough to use without some light irritation.
[Miscellaneous Android Development] masantula:
Oh sweet, was deciding between the two, thanks much for shedding this light, will go with this one:)

Thanks again.

EDIT: I have recovery ClockMod 3.0.2.4, would this work or i NEED to get the new recovery, reason being is caz i have flashed recovery on my Nexus via bootloader but haven't on the Ideos. is the bootloader just the IDEOS page? When i do fastboot devices, i get the reply ? fastboot. When i do fastboot reboot the phone does respond and reboot so just wondering..
[Miscellaneous Android Development] Allanitomwesh:
Yeah,the bootloader is the frozen ideos page. It actually still works fine with 3.0.2.4 except for nandroid backups getting an error,which you can use titanium to avoid. Good to be up to date though. Plus it's blue :D
[Miscellaneous Android Development] masantula:
Oh great, my good man aorth made a flashable version of the new recovery so will update it and flash this ROM. Thanks guys for the help :)
[Miscellaneous Android Development] aorth:
My main phone is a Galaxy Nexus. I originally bought the U8150 to learn about Android and write lots and lots of documentation and push code to github in order to help out budding young devs who didn't know where to start (the phone is very popular in Kenya, where I live). I actually haven't used the U8150 in months. I compile, push patches, and help out here when I can, just for fun. :)

The U8185 is very cheap in Kenya. It has a CPU based on the ARMv7 architecture, an 800MHz stock frequency, a GPU, and has a 45 nm die size. Comparitively, the U8150 is based on ARMv6 (meaning no NEON instructions, used for hardware decoding of many things like audio and video), a 528MHz stock frequency (Huawei overclocks it to 600MHz), no GPU, and a 65 nm die size (meaning it's bigger, and less efficient).

Good enough reasons? :)

Last month I tried to get Koush to update the "official" ClockworkMod Recovery in ROM Manager to 5.0.2.8, but I could never get ahold of him. I found out that the 3.0.2.4 one actually does work (at least for flashing), so I gave up. For what it's worth, I made a zip of 5.0.2.8: http://goo.im/devs/aorth/roms/u8150/cwm_5.0.2.8_u8150.zip

Cheers