[ROM][UNOFFICIAL] CyanogenMod 10.1 Nightlies / Releases [SR3]

Search This thread
By:
Advanced…
Mustaavalkosta

Mustaavalkosta

Senior Member
Dec 25, 2010
2,476
9,436
37
Tampere
opendesireproject.org
Frankk said:
Hello Mustaavalkosta, I am an happy user of your great ROM.

Apart from the problem of reboot/freeze i am experiencing since the inclusion of faux123 patch I am not having any major problem. I have tryed to get a logcat in recovery with last_mesg.zip without success. I'm back to M3 now, I will try again soon (i periodically try new nightlies).

I am posting because of a problem I am having with autofocus (not working at all) in some apps, in particular with QRDroid.

I have emailed the QRDroid support telling them that in other apps autofocus is working fine, and here is their reply:

Code: 
Hi Francesco,

I have spoken with our head developer and we cannot reproduce this issue.

The code to focus is inside the XZing library which QR Droid uses and we have not modified this.

The most probable cause is that your  specific device -or specific custom ROM- handles autofocus with a different code. This special code could be handled by QuickMark and not ZXing, and this is why Quickmark for example can focus as you say.

Kind regards

QR Droid Customer Support

Do you have any idea of what could cause the problem?

Thank you,
Francesco
Click to expand...
Click to collapse

Sounds and seems like XZing library problem to me if every app using it shows no auto-focus while it's working on other apps.

Sent from my Nexus 7 3G using Tapatalk HD
 
MusikMonk

MusikMonk

Senior Member
Aug 6, 2008
637
314
35
Paris
Roberto_Lim said:
Actually, I had the same problems with Barcode Scanner from ZXing.

Sent from my Desire HD using xda premium
Click to expand...
Click to collapse

Weird enough it's working fine for me, and I've just checked (on the 20/04 nightly) to make sure that it didn't break recently. Tried with "No continuous focus" both checked and unchecked.

Edit:
Sorry, false positive. Turned out I had to close the application for the settings change to get applied. Unchecking the aforementioned option does break auto-focus for me.
 
Last edited:
Roberto_Lim

Roberto_Lim

Senior Member
Jul 25, 2012
1,322
765
MusikMonk said:
Weird enough it's working fine for me, and I've just checked (on the 20/04 nightly) to make sure that it didn't break recently. Tried with "No continuous focus" both checked and unchecked.
Click to expand...
Click to collapse

The issue might depend on which camera sensor the phone comes with. I have an Omnivision sensor.

Sent from my Desire HD using xda premium
 
MusikMonk

MusikMonk

Senior Member
Aug 6, 2008
637
314
35
Paris
Roberto_Lim said:
The issue might depend on which camera sensor the phone comes with. I have an Omnivision sensor.

Sent from my Desire HD using xda premium
Click to expand...
Click to collapse

Well, I don't remember what my sensor was (and too lazy to search where it was stored). But at any rate I've updated my previous post. Looks like the "bug fix" option is required for the ZXing barcode reader. And I've also tested QR Droid and I don't have autofocus either.
 
  • Like
Reactions: Roberto_Lim
iopetja

iopetja

Senior Member
Apr 23, 2010
142
41
Ljubljana
LG G8
Both BS and QM autofocused immediatelly here. But I did flash JB camera, if that counts.

----
If I helped, please hit the Thanks...

DHD smoothie by Mustaavalkosta's M3
 
I

ivanhoe74

Senior Member
Apr 7, 2010
163
45
Novi Sad
Frankk said:
Hello Mustaavalkosta, I am an happy user of your great ROM.

Apart from the problem of reboot/freeze i am experiencing since the inclusion of faux123 patch I am not having any major problem. I have tryed to get a logcat in recovery with last_mesg.zip without success. I'm back to M3 now, I will try again soon (i periodically try new nightlies).

I am posting because of a problem I am having with autofocus (not working at all) in some apps, in particular with QRDroid.

I have emailed the QRDroid support telling them that in other apps autofocus is working fine, and here is their reply:

Code: 
Hi Francesco,

I have spoken with our head developer and we cannot reproduce this issue.

The code to focus is inside the XZing library which QR Droid uses and we have not modified this.

The most probable cause is that your  specific device -or specific custom ROM- handles autofocus with a different code. This special code could be handled by QuickMark and not ZXing, and this is why Quickmark for example can focus as you say.

Kind regards

QR Droid Customer Support

Do you have any idea of what could cause the problem?

Thank you,
Francesco
Click to expand...
Click to collapse

Had the same problem with Barcode Scanner, I went to apps, deleted data for Barcode Scanner and it started working.
 
ADB100

ADB100

Senior Member
Nov 3, 2006
1,495
119
tonylee000 said:
Searched for hotspot and the last mention is back at the end of jan and was working, only mine isnt, amni missing something?
Click to expand...
Click to collapse

Same here. I have tried almost all of the nightlies for the last 2-weeks (not sure about prior to that as I only recently just switched to CyanogenMod 10.1 and this ROM - breath of fresh air.....) and WiFi HotSpot doesn't work correctly. I can enable it and connect to it from a PC - I get a valid IP RFC1918 address (192.168.43.x), I can resolve names and I can ping the phone itself however I can't get any traffic 'through' the phone. I had a similar issue a while ago with the Sabsa Prime ROM and the default Orange APNs (UK) for some reason not allowing tethering (not sure how as its the phone that does the NATing and hiding the devices behind it?). The fix was to change the 'Consumer Broadband' APN settings, however I have been migrated over to EE now and the EE APN settings are the same as I had with the Sabsa Prime ROM that worked fine (I updated the apns-conf.xml file in /system/etc).

So our problem may be down to our carriers and the APN settings and not the ROM? Not sure though? My workaround is to install 'WiFi Tether for Root Users' and this seems to work fine.

Andy
 
Last edited:
  • Like
Reactions: nathancoast
F

Frankk

Member
Apr 27, 2006
31
2
ivanhoe74 said:
Had the same problem with Barcode Scanner, I went to apps, deleted data for Barcode Scanner and it started working.
Click to expand...
Click to collapse

Deleting data for qrdroid didn't solve the issue.
Installed Barcode scanner by zxing and it is working fine.
I will probably say goodbye to qrdroid...

Sent from my Desire HD using xda app-developers app
 
Mustaavalkosta

Mustaavalkosta

Senior Member
Dec 25, 2010
2,476
9,436
37
Tampere
opendesireproject.org
Does anyone know for certain if this call ends -> screen lights up when you move the phone away from your ear -> screen turns off for no reason behavior started happening at some specific point in nightlies or has it been there from the beginning? I also noticed this the very first time last weekend. I don't know how I can reproduce it without getting a huge phone bill but I thought to ask for more information anyways if someone is able to provide it. :)

I couldn't find anything from CM's jira so I guess it's not common problem for different devices. It's still also possible this can be fixed with just using proximity recalibrator (I don't currently use it, so I don't know...).
 
Mustaavalkosta

Mustaavalkosta

Senior Member
Dec 25, 2010
2,476
9,436
37
Tampere
opendesireproject.org
rjand

rjand

Senior Member
Oct 10, 2012
1,227
648
Mustaavalkosta said:
Does anyone know for certain if this call ends -> screen lights up when you move the phone away from your ear -> screen turns off for no reason behavior started happening at some specific point in nightlies or has it been there from the beginning? I also noticed this the very first time last weekend. I don't know how I can reproduce it without getting a huge phone bill but I thought to ask for more information anyways if someone is able to provide it. :)

I couldn't find anything from CM's jira so I guess it's not common problem for different devices. It's still also possible this can be fixed with just using proximity recalibrator (I don't currently use it, so I don't know...).
Click to expand...
Click to collapse

Doesn't happen to me on 0419 nightly, never noticed it on any nightly before that either. Just to be sure I am following you correctly - make call and place call near ear and screen turns off, call ends, screen then lights up, and for me stays lit until screen timeout is reached. It doesn't make a difference to me if the call is ended either by me or the dialled party, screen lights up once the call is ended and shows the call history (I called a number from the call history) and remains lit until the screen timeout is reached. Tested as well from keypad dialler, same thing, works no problem, but returns to home screen after call is hung up.

Edit:
I don't use proximity recalibrator. I usually wipe cache, system and dalvik cache before installing the nightly.
 
Last edited:
  • Like
Reactions: Mustaavalkosta
MusikMonk

MusikMonk

Senior Member
Aug 6, 2008
637
314
35
Paris
Mustaavalkosta said:
Does anyone know for certain if this call ends -> screen lights up when you move the phone away from your ear -> screen turns off for no reason behavior started happening at some specific point in nightlies or has it been there from the beginning? I also noticed this the very first time last weekend. I don't know how I can reproduce it without getting a huge phone bill but I thought to ask for more information anyways if someone is able to provide it. :)

I couldn't find anything from CM's jira so I guess it's not common problem for different devices. It's still also possible this can be fixed with just using proximity recalibrator (I don't currently use it, so I don't know...).
Click to expand...
Click to collapse

I only encountered the issue once (it was post 10/04, but can't remember further than that), and that was after full wiping and forgetting to install the calibrator. So it is most likely solved by that.
I'll see if I can reproduce tonight when I'm back home. Unlimited calls FTW! (But either way, voice messaging should do do fine and I would assume it's free worldwide, right?).

o0k00l said:
ADB is working fine connection is established however root permission is not coming...
Click to expand...
Click to collapse

Did you try to manually use "su"?
I don't have ADB installed at work so I can't test right now, but I'm pretty sure that I've used root over ADB at least once during the last week.
 
Last edited:
  • Like
Reactions: Mustaavalkosta
Mustaavalkosta

Mustaavalkosta

Senior Member
Dec 25, 2010
2,476
9,436
37
Tampere
opendesireproject.org
rjand said:
Doesn't happen to me on 0419 nightly, never noticed it on any nightly before that either. Just to be sure I am following you correctly - make call and place call near ear and screen turns off, call ends, screen then lights up, and for me stays lit until screen timeout is reached. It doesn't make a difference to me if the call is ended either by me or the dialled party, screen lights up once the call is ended and shows the call history (I called a number from the call history) and remains lit until the screen timeout is reached. Tested as well from keypad dialler, same thing, works no problem, but returns to home screen after call is hung up.

Edit:
I don't use proximity recalibrator. I usually wipe cache, system and dalvik cache before installing the nightly.
Click to expand...
Click to collapse

MusikMonk said:
I only encountered the issue once (it was post 10/04, but can't remember further than that), and that was after full wiping and forgetting to install the calibrator. So it is most likely solved by that.
I'll see if I can reproduce tonight when I'm back home. Unlimited calls FTW! (But either way, voice messaging should do do fine and I would assume it's free worldwide, right?).
Click to expand...
Click to collapse

Thanks for the additional clues. Yeah, it turned off when I tried to hit end call (I guess it was ended from the other end before me) and the screen just turned off just before I managed to touch the screen. I guess it's possible in theory that some display (kernel or qcom/display) commit is causing this but I'm not sure how it can only affect after-call behavior. Odd. Well, it's not that big of a deal but something I can keep an eye out. As far as I know, this doesn't even happen every time you finish your call which would suggest that proximity sensor just goes haywire sometimes. I'll install recalibrator and tune my values and see if the problem goes away. :)
 
Gio_ital

Gio_ital

Senior Member
Feb 22, 2013
281
84
Rome
Huawei P30 Pro
Xiaomi Mi 10
Mustaavalkosta said:
Thanks for the additional clues. Yeah, it turned off when I tried to hit end call (I guess it was ended from the other end before me) and the screen just turned off just before I managed to touch the screen. I guess it's possible in theory that some display (kernel or qcom/display) commit is causing this but I'm not sure how it can only affect after-call behavior. Odd. Well, it's not that big of a deal but something I can keep an eye out. As far as I know, this doesn't even happen every time you finish your call which would suggest that proximity sensor just goes haywire sometimes. I'll install recalibrator and tune my values and see if the problem goes away. :)
Click to expand...
Click to collapse

With recalibrator everything works fine

Sent from my Desire HD using xda app-developers app
 
  • Like
Reactions: Mustaavalkosta
You must log in or register to reply here.

Similar threads

mike1986.
[ROM] Android Revolution HD 7.3 & 9.2 | High Quality & Performance | O/C | Legendary
Replies
72K
Views
16M
laz61laz
laz61laz
Mustaavalkosta
[ROM][UNOFFICIAL] CyanogenMod 11 Nightlies / Releases [EOL]
Replies
5K
Views
1M
gongoscho
gongoscho
LorD ClockaN
  • Locked
  • Poll
[ROM]19-10-2012 | IceColdSandwich - 8.8 - AOKP | OMG, IT'S ALIVE EDITION
Replies
27K
Views
6M
Teichopsia
Teichopsia
K
[NIGHTLY][ROM][GWK74] CyanogenMod 7 for vendor Ace (HTC Desire HD & Inspire)
Replies
7K
Views
1M
WordsworthESP
WordsworthESP
LeeDroid
  • Locked
  • Poll
[ROM]LeeDrOiD HD V4.0.0 SE-3.0 [KERNEL]V4.0.0 16th Dec| HTC GB | OTA | CRT TV
Replies
23K
Views
3M
LeeDroid
LeeDroid

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 249
    Mustaavalkosta
    Mustaavalkosta
    These are UNOFFICIAL CM10.1 JellyBean Nightlies / Releases brought to you by Mustaavalkosta and TeamCodefire as a continuum to CM10 nightlies.

    GijgSN5.png
    A1gKSTb.png
    dz0CEmg.png
    TVboRJ4.png

    #include
    /*
    * Your warranty is now void.
    *
    * I am not responsible for bricked devices, dead SD cards,
    * thermonuclear war, or you getting fired because the alarm app failed. Please
    * do some research if you have any concerns about features included in this ROM
    * before flashing it! YOU are choosing to make these modifications, and if
    * you point the finger at me for messing up your device, I will laugh at you.
    */
    Click to expand...
    Click to collapse


    General:
    Builds are generated automatically each day week (except "releases" which will be done once a month and after SR1 when required) with latest changes from CM, Andromadus and myself. Builds use some required Andromadus' repos for msm7x30 that can be found from github (link below) and local device repo for ace. Kernel is based on synergye's KangBang kernel with some changes to fulfill some dependencies on this rom. Local manifest used for the builds can be found here. If the builds stop coming at some point, it most likely means there are changes in upstream that broke the build. I'll attend to solving such situations when I have time. Latest 7 nightlies will be kept on the server. If you want a longer history of them, you are free to archive them yourself.

    Thanks and credits:
    • Andromadus (for msm7x30 repos)
    • CodeAuroraForum
    • CyanogenMod
    • BananaGranola
    • Epic Beard Men
    • eXistZ
    • Flemmard
    • Flinny
    • Juansheng
    • KangBangKreations (shipped kernel is based on this)
    • paulb_nl
    • thachtunganh (s2w)
    • PipelinerArd (for initial spark for this project)
    • synergye
    • TeamCodefire (for build server and hosting, priceless)
    • a user (for provided tweaks)
    • Flow-Wolf (for the video review, see Q&A)
    • All the rest that have helped to construct these builds and develop software for ace directly or indirectly in the past.

    Githubs:

    Changelogs:


    Fresh installation instructions:
    20130313 and newer nightlies are not compatible with KangBang 3.x or older!
    1. Download Nightlies / Releases [BasketBuild mirror]
    2. Download gapps (goo.im/gapps)
    3. Put the files on SD card.
    4. Reboot to recovery.
    5. Do factory reset (ie. format /data, /cache, /sd-ext and /sdcard/.android_secure)
    6. Flash cm-10.1-xxxxxxxx-UNOFFICIAL-ace.zip
    7. Flash gapps-jb-xxxxxxxx-signed.zip
    8. Reboot and enjoy.

    Update installation instructions:
    20130313 and newer nightlies are not compatible with KangBang 3.x or older!
    1. Download Nightlies / Releases [BasketBuild mirror]
    2. Put the file on SD card.
    3. Reboot to recovery.
    4. Flash cm-10.1-xxxxxxxx-UNOFFICIAL-ace.zip
    5. Remember to reflash boot.img via fastboot if you are HTCDev unlocked.
    6. No need to flash gapps as CM backuptool script should take care of them.
    7. Reboot and enjoy.

    InspireMod

    Contact:

    Donations:
    (codefi.re donations are used to cover the server costs, my donations will be used to increase my beard growth in a way or another)


    Q&A:
    Q: What's "M-Series"?
    A:
    CyanogenMod said:
    We aren’t exactly sure what M stands for. “Monthly”, “milestone”, or perhaps “MINE ALL MINE!”. Whatever it is, I hope that we are meeting the needs of community.
    Click to expand...
    Click to collapse

    Q: Where are my developer and performance options?
    A: http://goo.gl/jpS8r

    Q: I've used HTC Dev unlock and flashed the rom but it won't boot. What should I do?
    A: HTC Dev unlock is pretty much useless when flashing roms from recovery. Until HTC One, it doesn't allow flashing boot partition from recovery which pretty much kills or cripples any custom rom if boot.img has been modified. You need to extract boot.img from the zip and flash it via fastboot. If you don't have fastboot executable anymore from flashing recovery, install Android SDK platform tools (Linux users should find it from distro's package management) and then reboot to bootloader, open command prompt and navigate to the location you extracted your boot.img and type:

    Code: 
    fastboot flash boot boot.img

    You need to repeat this everytime you flash new version of this rom to ensure everything will work fluently as long as you have just basic HTC Dev unlock.

    Q: What does the ROM look like?
    A: Video review by Flow-Wolf.

    Q: Feature X doesn't work, let's make 1000 posts about it to annoy everyone.
    A: Please, dont. Use search and then use search again and only then report your problem with necessary logs. [Logcat guide, thanks to MusikMonk for the link]

    Q: I hate you for not fixing this issue X!!!
    A: I love you too.

    Q: How I can build CM10.1 myself?
    A: Setup a basic Android build environment.
    Code: 
    mkdir cm10
cd cm10/
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1
mkdir -p .repo/local_manifests
wget https://github.com/Mustaavalkosta/android/raw/cm-10.1/local_manifest.xml -O .repo/local_manifests/cm_ace.xml
repo sync
cd vendor/cm/
./get-prebuilts
cd ../../
. build/envsetup.sh
lunch cm_ace-userdebug
mka bacon
    Once the build finishes you'll find your goods from out/target/product/ace/ directory.

    Q: My device rebooted itself all the way to the white HTC bootsplash. What should I do?
    A:
    synergye said:
    Regarding the reboots, it would be incredibly helpful if someone could get a last_kmsg after an unexpected reboot. To do so, go directly to recovery after the reboot (without booting into android) via the volume key and power button, then run adb pull /proc/last_kmsg on your computer and upload. I thought the issue was stemming from out of pmem errors like on vision which is why I increased pmem allocation again. Without any evidence, it's just guesswork though.
    Click to expand...
    Click to collapse
    Flashable zip to copy /proc/last_ksmg to your sdcard, no adb needed: http://downloads.codefi.re/mustaavalkosta/last_kmsg.zip

    Q: Something about something something something.
    A: Ask the guy/gal next to you.

    XDA:DevDB Information
    [UNOFFICIAL] CyanogenMod 10.1 Nightlies / Releases [SR3], ROM for the HTC Desire HD

    Contributors
    Mustaavalkosta
    ROM OS Version: 4.2.x Jelly Bean
    ROM Kernel: Linux 3.0.x
    Based On: CyanogenMod

    Version Information
    Status: Stable
    Current Stable Version: SR3
    Stable Release Date: 2013-11-25

    Created 2014-10-09
    Last Updated 2014-10-09
    View
    55
    Mustaavalkosta
    Mustaavalkosta
    SR1

    This will be the last milestone release until CM puts out another stable release or I get big enough breakthrough somewhere that it will require building a new ROM. This is just a heads up not to wait milestone builds to continue monthly. There's not much point to release almost identical ROMs just that people can feel they have the latest stuff in their phones. For that purpose there are nightlies. :)

    I also cleaned up directory structure a bit on codefi.re and thus also on goo.im. Nightlies can be found under "nightlies" directory from now on and these milestone builds are under "releases". I hope this change makes it a bit easier to follow the logic behind the builds.

    Thanks for all the contributions since RC5!

    Download: [codefi.re][goo.im]
    Buttonlight patch: [codefi.re][goo.im]
    Perf kernel: [codefi.re][goo.im]
    Changelog: [pastebin]
    Manifest: [github]

    ps. I recently got asked for an Android related job and I'll start soon so my time with this will be a bit more limited than it has been this far but I don't see this as a huge problem as the most time-consuming and urgent stage for this rom is already far behind.
    View
    44
    Mustaavalkosta
    Mustaavalkosta
    I changed crontab for nightlies to only produce a nightly build once a week on Mondays. There are not that many changes anymore that they would require daily builds. This frees build server resources for other users.

    I may still do SR1.2 at some point. My personal feel of the dalvik.vm.heapgrowthlimit change is that the lower value works better and I probably want to put that change out to SR releases too. It has been live on nightlies for some time.

    I'm now living at the new place and my move went smoothly. It's still a bit chaotic but I hope to get back to working on ace soon. Thanks for all the help and support on this thread for the past ~7.5 months. Many problems wouldn't have been solved without wide user feedback and testing. :)
    View
    41
    Mustaavalkosta
    Mustaavalkosta
    SR2

    So, here it is. It took a bit longer than an hour overall due various things but oh well, sleep is for the weak. :p

    Download: [codefi.re][goo.im]
    Buttonlight patch: [codefi.re][goo.im]
    Perf kernel: [codefi.re][goo.im]
    Changelog: [pastebin][codefi.re] (It doesn't include totally new repos, it was too messy with those.)
    Manifest: [github]

    ps. New gapps: http://goo.im/gapps/gapps-jb-20130812-signed.zip
    View
    38
    Mustaavalkosta
    Mustaavalkosta
    RC1

    You can now download RC1 build from: http://downloads.codefi.re/mustaavalkosta/cm-10-1-unofficial-ace/release-candidates

    BIG FAT DISCLAIMER:
    THIS IS NOT COMPARABLE TO OFFICIAL CYANOGENMOD RELEASE CANDIDATES. IT'S AS UNSTABLE OR STABLE AS THE LATEST NIGHTLIES HAVE BEEN AND EPIC BEARD MEN WILL SHAVE YOU WITH AN AXE IF YOU COMPLAIN ABOUT IT NOT BEING STABLE ENOUGH TO CALL IT RELEASE CANDIDATE. YOU HAVE BEEN WARNED.

    Sorry for the caps but I already saw my share of useless crying about semantics on cfx thread and SR naming scheme.

    Download and enjoy!
    View

New posts