[Firmware][SGH-I777][JB][4.1.1] CyanogenMod 10 preview | USER THREAD

Search This thread
R

redherring79

Guest
Dunno about alarms since I don't use my phone for that but I did notice that Android Beam isn't working. Not only is it not working (tried to send my wife a pic from my gallery and it acted like it went through but she ended up receiving a notification saying that Android Beam was not received) but it's also turning on my bluetooth instead!

This is from the latest nightly, 2/11.

Pretty sure Beam has always turned on Bluetooth for image transfers. I think that's how it works.

Sent from my SGH-I777 using Tapatalk 2
 
Last edited:

DefTaker

Senior Member
Jun 20, 2009
357
44
Pretty sure Beam has always turned on Bluetooth for image transfers. I think that's how it works.

Sent from my SGH-I777 using Tapatalk 2

No, beam doesn't use BT (it't never turned on my BT before either). It's NFC. One of the few NFC features that actually works on this phone since NFC is heavily crippled on our hardware (DAMN u Samsung!).

Oh well, will flash the latest nightly to see if it's been fixed. I know that 2/11's had an update so I'm wondering if that may have accidentally created the bug. Will test today's latest nightly build and will report back. If that doesn't work I'll have to try a full wipe and reflash.
 

jrod091

Senior Member
Feb 13, 2012
337
88
Atlanta, GA
No, beam doesn't use BT (it't never turned on my BT before either). It's NFC. One of the few NFC features that actually works on this phone since NFC is heavily crippled on our hardware (DAMN u Samsung!).

Oh well, will flash the latest nightly to see if it's been fixed. I know that 2/11's had an update so I'm wondering if that may have accidentally created the bug. Will test today's latest nightly build and will report back. If that doesn't work I'll have to try a full wipe and reflash.

It first uses NFC to get a connection then uses BT to actually make the transfer. It has ALWAYS done that for me. Just transfered a pic to my wife's s2 and my n10, both ended up using BT, like always

Sent from my SGH-i777 using xda app-developers app
 

DefTaker

Senior Member
Jun 20, 2009
357
44
It first uses NFC to get a connection then uses BT to actually make the transfer. It has ALWAYS done that for me. Just transfered a pic to my wife's s2 and my n10, both ended up using BT, like always

Sent from my SGH-i777 using xda app-developers app

Really? Didn't know that. But it's never left my BT on, if that's the case. I have always BT OFF and last night was the first time when using Beam, that the file did NOT transfer and it left BT ON on my phone.

I didn't upgrade my wife's i777 and hers was working fine (she's on build 2/08) and does not trigger BT to stay ON.
 

jrod091

Senior Member
Feb 13, 2012
337
88
Atlanta, GA
Really? Didn't know that. But it's never left my BT on, if that's the case. I have always BT OFF and last night was the first time when using Beam, that the file did NOT transfer and it left BT ON on my phone.

I didn't upgrade my wife's i777 and hers was working fine (she's on build 2/08) and does not trigger BT to stay ON.

Oh, I see what you're saying now, no, it shouldn't leave it on, it should just trigger it on fur the target then turn back off when the transfer is compete, I believe

Sent from my SGH-i777 using xda app-developers app
 

DefTaker

Senior Member
Jun 20, 2009
357
44
Oh, I see what you're saying now, no, it shouldn't leave it on, it should just trigger it on fur the target then turn back off when the transfer is compete, I believe

Sent from my SGH-i777 using xda app-developers app

No worries, flashed today's nightly and 2/12 seems to have fixed it. :silly:
 

msgfromside3

Senior Member
Nov 23, 2010
744
131
Leaving my WiFi on zaps the crap out of my battery. This normal behavior at this stage or is it just mine?

That has been normal behavior of almost anything for last couple of years because it is trying to scan for available wifi (guess what happens then?). I am not sure if it is still true, but you are supposed to be able to tweak the rescan interval from build.prop. I haven't done that for ages and I now turn my wifi off as soon as I get in my car.
 

TheDude

Senior Member
Dec 10, 2010
696
406
Nixa, MO
Google Pixel 8 Pro
That has been normal behavior of almost anything for last couple of years because it is trying to scan for available wifi (guess what happens then?). I am not sure if it is still true, but you are supposed to be able to tweak the rescan interval from build.prop. I haven't done that for ages and I now turn my wifi off as soon as I get in my car.

Yeah you can set your Wi-Fi scan interval to a higher amount to lessen the battery drain, as stated above in your build.prop, or just turn it off when not in use. I normally turn it off.

Got ya. Thanks guys
 

Entropy512

Senior Recognized Developer
Aug 31, 2007
14,088
25,086
Owego, NY
Leaving my WiFi on zaps the crap out of my battery. This normal behavior at this stage or is it just mine?

Nope. Leaving wifi on = best way to save battery (since it uses far less power to transfer data than the cell connection). The exception is if you have a misbehaving home network that spams your phone and wakes it up all the time.
 

rk249

Senior Member
Jun 24, 2012
351
108
Nope. Leaving wifi on = best way to save battery (since it uses far less power to transfer data than the cell connection). The exception is if you have a misbehaving home network that spams your phone and wakes it up all the time.
My home network does that, I have crazy wlan rx wakelock times, especially on cm kernel. I dont know what to do about them so I've just accepted it and moved on.
 

elherr

Senior Member
Jul 26, 2011
382
138
Isla de Malhado
uploadfromtaptalk1361038802787.jpg

*** FYI -- the ADB API has changed with 4.2.2. You will need to update your Android SDK (which includes adb, aapt... etc). Otherwise you will see a status of 'offline' when trying to connect. Also, you will have to acknowledge a notification on your phone prior to connecting.
 
Last edited:

ipa96

Member
Oct 12, 2011
28
17
Someone posted in the I747 thread that with the latest nightly they got HDMI out working. Anybody had success with our phone? I gave it a go, but no luck. What am I missing?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 112
    ATTENTION: THIS IS JUST A PREVIEW. MAY CONTAIN A LOT OF BUGS!
    NO SUPPORT!!!

    CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.1 (JB), which is designed to increase performance and reliability over stock Android for your device.

    Code:
    #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.
     *
     * Submitting bug reports on nightly builds is the leading 
     * cause of male impotence.
     */

    CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.



    First time installing CyanogenMod 10 to your Galaxy S II, or coming from another ROM:
    - Make sure you're running a proper working CWM Recovery
    - Copy GApps and CM10 ZIPs to your internal SDCard
    - Boot into Recovery
    - Flash CM10 zip from internal SDCard
    - Flash GApps zip from internal SDCard
    - DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot)
    - Reboot
    - Don't restore Apps using Titanium Backup!

    Upgrading from earlier version of CyanogenMod 10:
    - Copy CM10 ZIP to your internal SDCard
    - Boot into Recovery
    - Flash CM10 zip from internal SDCard
    - Reboot



    Experimental builds:
    http://d-h.st/JaT - 7/27/2012
    http://d-h.st/aMl - 8/3/2012
    http://d-h.st/iXg - 8/13/2012
    http://d-h.st/3KE - 8/18/2012
    http://d-h.st/QbU - 8/19/2012

    Google Apps:
    Get the latest Version from Rom-Manager.
    Newer, unsupported versions can be found at http://goo.im/gapps


    Webchat: http://webchat.freenode.net/?channels=teamhacksung-support

    Server: chat.freenode.net
    Channel: #teamhacksung-support

    Don't expect any support if you:
    - are not running stock cm-kernel
    - have installed any mods
    - have modified system files



    If you're going to reuse our work, which we're doing for free, be fair and give proper credits.
    This is the only payment we're really demanding and we deserve it to be mentioned because of the countless hours we've put into this project.
    Open-Source doesn't meant Out-of-Respect!!!


    Development Thread (DEVELOPERS ONLY): http://xdaforums.com/showthread.php?t=1796744


    ygKDil.png
    GeQbTl.png

    qNkWbl.png
    rK3uzl.png



    If you want to donate a few bucks for the work we're doing in our freetime, goto teamhacksung website and hit the big donate button.
    Thanks to all donators!

    KNOWN ISSUES:
    • Everything is broken until proven otherwise.
    • Known broken things include:
    • Mediascanner derps hard for many people, eating 100% CPU for 30-40 minutes on boot.
    • Missing many CM10 features
    • NFC totally untested
    • Anything broken on I9100 will be a problem on I777 too
    • Screenshots are from I9100. I'm lazy, and I777 isn't any different

    You want to live on the bleeding edge, you're probably gonna get cut
    77
    Update -
    Good news: I found out the source of the problem and built a fix this morning.
    Bad news: Severe thunderstorms yesterday afternoon knocked out my cable modem. I'm unable to upload a build or even the fix until it comes back.
    51
    RELEASE PULLED. I just discovered from user reports in the N7000 thread that this has the capability of triggering the infamous eMMC brickbug on installation. This is far less likely on I777 since almost no one is running intramfs-repacked UCLE5, but those people could experience severe unrecoverable problems. I will reopen this thread once I reimplement that fix.

    To be clear - the bug only affects initial flashing. If you are already running CM10, you are safe. If you are not already running CM10, DO NOT flash the release unless you are running a known safe kernel. Right now, I will only guarantee safety with the pulled release if you start from CM9.
    49
    Unless something comes up Monday evening and I'm too busy to build, I'll try to get the first I777 test build out monday evening for 4.2.1.

    Benefit of the wait for you guys? N7000/I9100 users are guinea pigs with ****ty builds that have all sorts of broken stuff. First I777 build will have all of the big issues resolved. :p
    42
    4.2 test build within the next few days, depending on my availability/time.

    Finally I think we've got the graphics breakthrough we need... just needs to be beat on/polished a bit.