Is there any hint to look for in the logcat to confirm whether the problem is actually related to lack of gapps ?
[Firmware][GT-N7000][4.2.1] CyanogenMod 10.1 unofficial builds // discussion thread
- Thread starter Entropy512
- Start date
Is there any hint to look for in the logcat to confirm whether the problem is actually related to lack of gapps ?
It's no more stable than the nightlies were. I want to be very clear: While normally it is up to the maintainers to determine whether a device is eligible for RC/stable, neither xplodwild nor myself approved of this device entering RC/stable. Netflix doesn't work without horrible hacks (they put one in, but it is one that has no business in a stable release - this alone is something I consider a blocker), I still see periodic reports of various games crashing, I experienced a hard freeze while attempting to download Real Racing 3 and last_kmsg still doesn't work, and UI performance is utterly atrocious.
Why don't they leave the CM10.1 as it is. As @Entropy512 states it does not entitle it to be RC then suddenly we have stable. There is something seriously going wrong with them. People who have been following the progress aren't such dum f***s to realize this 
Its good market for new players trying there hands on CM. "Stable" name good for buyers
Its good market for new players trying there hands on CM. "Stable" name good for buyers
And investors
The bigger the number of installs... Etc
Gesendet von meinem GT-N7000 mit Tapatalk 4
The bigger the number of installs... Etc
Gesendet von meinem GT-N7000 mit Tapatalk 4
B
baz77
Guest
As the benchmarks show, it had a negative impact on memmove()
Some problem I am facing in the stable cm 10.1.3 ....contact is fcing every time I click on the phone icon. Have tried several workarounds like cleaning data/cache but the same problem every time.
Can anyone please suggest a solution. I have done all searches on xda and Google but to no avail. Thanks
Sent from my GT-N7000 using XDA Premium 4 mobile app
---------- Post added at 02:27 PM ---------- Previous post was at 02:20 PM ----------
Well, I managed to make it work for the time being by doing the following-
Clicked on contact and dialled a number directly from inside contact instead of the dialer.
The dialer has been working without any FC since then.
I don't know if this is a permanent solution though but if this helps other members facing the same problem, I would be glad to have been of some help.
Sent from my GT-N7000 using XDA Premium 4 mobile app
Can anyone please suggest a solution. I have done all searches on xda and Google but to no avail. Thanks
Sent from my GT-N7000 using XDA Premium 4 mobile app
---------- Post added at 02:27 PM ---------- Previous post was at 02:20 PM ----------
Well, I managed to make it work for the time being by doing the following-
Clicked on contact and dialled a number directly from inside contact instead of the dialer.
The dialer has been working without any FC since then.
I don't know if this is a permanent solution though but if this helps other members facing the same problem, I would be glad to have been of some help.
Sent from my GT-N7000 using XDA Premium 4 mobile app
Did you restore any previous call log? If so, do not do that. It FCs and you cant make or receive calls
You included a samsung_smdk4412-common cherry pick for a Note build? Our CM doesn't use smdk4412-common at all AFAIK. It uses galaxys2-common instead.
You had edited the source code manually, and you expected to see complaints in the i9100 forum? Srsly?
How many guys would've done the same?
I believe you meant memcpy
Also, with memcpy performance is doubled without using NEON, except on BM_memcpy/8. Here NEON doubles vs non NEON.
I'm not sure which one is used more frequently, but i'm sure it's not the /8
Did you restore any previous call log? If so, do not do that. It FCs and you cant make or receive calls
Yup, I did.... Using TB. I think that has been the problem. Will take care when I flash cm roms hereon..
Sent from my GT-N7000 using XDA Premium 4 mobile app
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
88Text of original post shamelessly kanged from codeworkx and edited to be appropriate for N7000. Some links may still go to I9100 stuff. If you can't figure out replacements on your own for links that go the wrong place, you shouldn't be here.
DO NOT POST UNTIL YOU HAVE READ THE FIRST FOUR POSTS OF THIS THREAD IN THEIR ENTIRETY.
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.2 (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.
- There are bugs and we know them all. Don't try to report bugs or complain about. We'll blacklist you.
- No, we don't accept feature request. We've enough work to do with fixing bugs.
- Don't ask for changelogs!
- Never ask for new builds!
- Use it or leave it!
- Don't create a ROM based upon this! Creating a ROM on a buggy and unstable base is a stupid idea!
- kkthxbye
- UI: Apps like NHK are broken
- Audio: bugs, missing features
- Camera: Recording partially broken
- FM Radio: unsupported
- TV Out: unsupported, not likely to ever work (there is small hope now but not much)
- Lots of missing and yet unimplemented features
- and a lot more
First time installing CyanogenMod 10.1 to your Galaxy S II, or coming from another ROM:
- Make sure you're NOT RUNNING A KERNEL WITH THE MMC-SUPERBRICK-BUG. If you're unsure, flash this ClockworkMod-Recovery using Odin/Heimdall.
- Make sure you're running a proper working ClockworkMod-Recovery
- Copy GApps and CM10.1 ZIPs to your internal SDCard
- Boot into Recovery
- Flash CM10.1 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 system data using Titanium Backup!
- Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
Upgrading from earlier version of CyanogenMod 10.1:
- Copy CM10.1 ZIP to your internal SDCard
- Boot into Recovery
- Flash CM10.1 zip from internal SDCard
- Reboot
CM10.1 unofficial builds:
20121212: http://d-h.st/u13
Google Apps:
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 without respect!
Screenshots kanged straight from codeworkx. Seriously, it's CM, the screenshots will look almost identical on all phones
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!30Things definitely broken
In addition to the stuff in OP from codeworkx:
Wifi tethering doesn't work - Bluetooth tethering does
HWComposer barely works - passes vsync and not much else. Run NHK World Live TV app and you'll see why it's broken
Lots of core non-device specific CM features are not yet reimplemented. This includes stylus gesture support, palm rejection, and control of stylus hover icon.
Camera doesn't appear on lockscreen - and it will not appear at all with many gapps packages
Audio HAL isn't fully reimplemented - no dock audio, etc.
Bluetooth SCO (calls) is busted and bluedroid spits out all sorts of bluetooth sleep control errors. We probably need to rework power management from the current mechanisms.28Switchover should happen before tomorrow's nightlies, so tomorrow's nightly SHOULD be CM10.1 for N7000.26Misc other stuff
The holidays are coming up here in the USA. I have family visiting this weekend, and will be visiting my parents for a week the following week. I have a lot of preparation to do and my laptop can't build CM, so don't expect much to happen until the new year.25
Thanks for the detail. I'm starting to poke at mali. I attempted to get the latest N7105 blobs running on my N8013, end result was sprinklies. I ****ing hate sprinklies, I have yet to figure out why some blobs cause them and some don't.I'm french and on the same carrier. This popup is due to an update of a specific application of "free mobile". The application is "messagerie visuelle" (specific access to answer machine).
They've add an auto-configuration of this wifi network.
This popup is launch by the application after the first reboot after the update and has nothing to do with CM.
And the configuration of this EAP-SIM wifi network don't work because EAP-SIM authentification is not include in CM10 as it was in CM9...
But pesonally I don't care lol
I prefer devs to focus on the next magical kernel with super mali drivers
(thanks by the way)
Sent from my GT-N7000 using xda app-developers app
Once I can get something that works on n8013 I'll backport to n7000.
I'm basically 95% done polishing CM10.0 to perfection on Xperia T (only things remaining are getting someone to merge a few outstanding patches, and fixing scaling of anamorphic videos on HDMI), once I finish that I'll poke at N7000 for a bit.
