Searched this thread + Google, but no avail.
Is it okay updating to every nightlies?
After doing wipe cache/dalvik, do I need to login again to twitter, facebook,... etc? And registering my device with like prey, kindle,... etc?
I mean is it recommended, or should I update to the one I see with major fixes?
Sent from My Note to YOU using xda premium...
You can go through the changelog (http://changelog.bbqdroid.org/#n7000/cm9/next) and decide for yourself whether you want to upgrade to next nightly or not.
After you install a nightly, you need to wipe cache and dalvik. All your apps remain intact and you need not have to login again to any of the apps.
Agree. Modem makes no difference.
Switching WLAN-Standards also have no effect for me. Still a moaning router.
I think it's the wakeup-lag
My Note doesn't show the network operator in notifications!!!
Mine is SA Al Jawal (STC - Saudi Arabia).
Is it just me? I mean the phone works fine including data access, but would like to see SA Al Jawal instead of No Service.
Thanks!
No need for local_manifest hackery now that we're official.IIRC, most people with a windows machine who want to do ROM development spin up virtualbox and install ubuntu, and do the development there.
I use ubuntu native, and haven't tried windows development, or doing anything with eclipse, as I'm more interested in the kernel.
Go to wiki.cyanogenmod.com, and find the Galaxy S II build instructions.
Replace gingerbread with ics.
Replace galaxys2 with n7000.
IIRC you don't need to get rom manager anymore.
You may also need to create .repo/local_manifest.xml and add the device & kernel specific lines:
Code:<?xml version="1.0" encoding="UTF-8"?> <manifest> <project name="CyanogenMod/android_device_samsung_n7000" path="device/samsung/n7000" remote="github" /> <project name="CyanogenMod/android_kernel_samsung_smdk4210" path="kernel/samsung/smdk4210" remote="github" revision="ics" /> </manifest>
Been a while since I did it, so YMMV. My build area is about 15G, so make sure you allocate enough space if you decide to go down that path.
Not sure of the dependencies at all, that is all handled by the build environment.
If you provide me with a patch, I might look at trying to build for you, but you are probably better going to the virtualbox path.
The official ICS release gets us nothing or nearly nothing MHL-wise. Remember - I9100 has had kernel source for over two months and still no working MHL. There's a lot of proprietary userspace stuff Samsung did that isn't documented and has no source code.I don't expect the number of countries to make any difference. There was only one source code released. Actually more source code would make it harder, as there would then more work to compare the different source codes.
While my preferences are opposite yours, neither of us get to set developer priorities / interests.
Previously it has been said that MHL would require various high level changes in the ROM even after the MHL kernel changes were merged, while I guess that OTG would require mostly kernel changes, and then could be used directy at the shell level, or using the already available apps. I have looked at the OTG changes and there are many, more than my currently limited understanding can attempt to manually merge. I haven't looked at MHL at all.
I'm just going to confirm the battery drain everyone else is experiencing.
This is on a clean CM9 29th march build, with only battery monitor widget installed. Only Sync Contact is enabled (honestly, if Sync is having a problem, I think it's also a problem with the ROM as it comes with it).
Anyway, I started off with wifi off. After 2 hours, battery drain remains at 4 mA (I've seen 2 mA on ICS stunner with wifi on, in standby). Then I decided to turn on wifi and let it idle. Battery drain leaps to about 60 mA. Left it for a few hours to stabilize and so my battery drops from 100% to 70% in 5 hours. Battery drain hovers at 51 mA and stayed there.
Then I decided to turn off the wifi, but the battery drain is still going on. The last time I tried this was on an unclean ROM, but it took about another 8 hours for the battery drain to slowly go from 50 mA to 11 mA. I think the merge from the official kernel source seems to have lead to battery drain problems. I didn't have any battery drain problem before, on CM9.
<ignore>Another bug seems to be that the lockscreen is a bit slow to respond. I had to press the home key again so that it responds.</ignore> Nevermind, it's a known bug.
After you install a nightly, you need to wipe cache and dalvik.
That's weird. After the 15.05 nightly (approx., I install every 5 days) I started having SOD problems, even after full wipes and clean install. I can even easily reproduce it - if the phone is idle for a long time (a few hours when I sleep) and I receive a text message, the phone seems to crash. I can hear it receiving the message (by which I mean I can hear interference in my speakers, which kinda acts like a notification for me), but it does it continuously, and the phone cannot wake. I have to reboot it, and after booting I immediately receive the message as usual.
-Only happens after long periods of deep sleep with about 30% probability and only with text messages (calls and email work normally).
-nothing unusual in logs or last_dmesg
-happens on both my Notes, so not an isolated case
I'll try to investigate it for a bit as soon as I have some time.
Could you show me the schematic of the circuit you used to measure current draw? Basically, you threw a bunch of current drain numbers that are outright lies if you did not use an external current measurement method, considering our device has NO way of measuring current draw internally.
I'm sick of this bull**** - None of the developers can reproduce your claimed problems, and not a single one of you has posted a single shred of useful data, and now people are posting crap that I know is an outright lie because the data they claim to have is impossible to obtain without hooking up a dummy battery and an ammeter outside the device.
Next person to whine about wifi issues the developers are unable to reproduce without COMPLETELY following the instructions for diagnosing drain at http://xdaforums.com/showthread.php?t=1308030 is getting reported.
In short - don't complain about wifi drain unless you've got a complete kernel wakelock dump taken in the manner requested in that thread along with a Shark capture.
The new driver fixes power management issues in a number of situations (For example, I again see deep sleep above 80% during an arpdrain stress test, I haven't seen that since ICS was released) - maybe it breaks others. Without any data other than useless *****ing and whining, it won't change.
Edit: It seems like with the exception of the touchscreen issue, those experiencing wifi problems are all using the same router - which happens to be a combined DSL/wifi router and in my experiences, many of those are utter ****. (See how 2wire is at the top of the ****list in the thread I linked above...) If people actually encounter problems with routers that have a good track record of reliability and consistency (Off of the top of my head - ones running DD-WRT or Tomato, and Ubiqiti products), that would be interesting. If it's Belkin or a Netgear running stock firmware, don't even bother wasting my time.
NIt seems like with the exception of the touchscreen issue, those experiencing wifi problems are all using the same router - which happens to be a combined DSL/wifi router and in my experiences, many of those are utter ****. (See how 2wire is at the top of the ****list in the thread I linked above...) If people actually encounter problems with routers that have a good track record of reliability and consistency (Off of the top of my head - ones running DD-WRT or Tomato, and Ubiqiti products), that would be interesting. If it's Belkin or a Netgear running stock firmware, don't even bother wasting my time.
...
Edit: It seems like with the exception of the touchscreen issue, those experiencing wifi problems are all using the same router - which happens to be a combined DSL/wifi router and in my experiences, many of those are utter ****. (See how 2wire is at the top of the ****list in the thread I linked above...) If people actually encounter problems with routers that have a good track record of reliability and consistency (Off of the top of my head - ones running DD-WRT or Tomato, and Ubiqiti products), that would be interesting. If it's Belkin or a Netgear running stock firmware, don't even bother wasting my time.
Thank you. Is there any detailed knowledge base about such routers, with buggy firmware verisons listed, and alternative firmware/soultions? Or otherwise, list of "clean" wi-fi/dsl routers? Mine is TP-Link TL-WR941N
None, everything is Ok.Could anybody please have a look in their router, if the wlan-log is "spammed" by the note, too.
#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.
*/
http://changelog.bbqdroid.org/#n7000/cm9/next
Build #7
This is the kind of news that gets the day off to a good start! I'm also skeptical, given what Entropy has said about he audio HAL problems, but androidindian has been right before! :fingers-crossed:
Could you please show me which one of these changes is Galaxy Note specific? ...
The truth is that development for this project has stopped. The OP recetly mentioned he/she is feeling a burn-out.
The kernel dev is obviously taking pleasure in being rude with people who are stupid and/or ignorant...
It's just CM stuff being changed in the nightlies, which sometimes can make things worse for us.