[GT-I9001][ROM][ION][JB][4.3.1][JLS36I] CyanogenMod 10.2 by ADC-Team - Release 5 (ION) - Kernel 3.4.x [EOL]

[anuseb89]

owhh my..all these while.. all custom rom for i9001 starting frm android 4..
cant make video calls??

so i need to go back 2.3.6 for this?

owhh my..

it has been discussed min 999999999999999 times that cm does not support video calls..and aosp also..and if you want to use it , yes you have to goto 2.3.6..

ps::I don't know what is the point of having that video call option. I have never seen anyone who is using it practically.. This is android world friend , we have hell lot of reliable apps which can be installed over cross platform devices for video call and all..

Have a nice evening..

 

[silverTwins]

so basically now it has been discussed 1*10^15 times

Sent from my GT-I9001 using XDA Premium 4 mobile app

 

[anuseb89]

so basically now it has been discussed 1*10^15 times

Sent from my GT-I9001 using XDA Premium 4 mobile app

He he.. Looks like that.. But dont worry.. Within next week it will increase by another 5 or 10..

Sent from my Nexus 5 using xda app-developers app

 

[smeroni68]

ADC Team is glad to announce that a new Tester has been "hired" in the team!!

He is a well known user on our xda forum section, and he asked for an high "salary"... we'll need to work more in the nights to pay him, but we found a good compromise!!

We leave directly to him the honor to present himself...

For any detail go to DEV thread!! http://xdaforums.com/showthread.php?t=2421230

 

[aorestes]

hehehe... sorry guys .. yeah, the video call thingy should most obviously been discussed since it is an obvious feature that was not included in the custom rom .. it must had alerted few users before me...
just that i didnt know about it, wasnt aware and didnt involve in the discussion .. that's why i asked ..
it didnt came to mind just like that, i really did tried to make a video call, and couldnt find the button in contact .. so it made me wonder ..

thanks for the clarification though.. ^_^;

 

[XeLLaR*]

hehehe... sorry guys .. yeah, the video call thingy should most obviously been discussed since it is an obvious feature that was not included in the custom rom .. it must had alerted few users before me...
just that i didnt know about it, wasnt aware and didnt involve in the discussion .. that's why i asked ..
it didnt came to mind just like that, i really did tried to make a video call, and couldnt find the button in contact .. so it made me wonder ..

thanks for the clarification though.. ^_^;

Well, the front camera works tho...you can use hangouts or skype for Video chat and it is also free.

Gesendet von meinem Nexus 4 mit Tapatalk 2

 

[Jann F]

My mobile is getting slower every day, I suspect that is because of the lacking TRIM implementation in the Kernel...

Do you guys experience the same slow down?

 

[XeLLaR*]

My mobile is getting slower every day, I suspect that is because of the lacking TRIM implementation in the Kernel...

Do you guys experience the same slow down?

TRIM is not needed for our type of EMMC. If you really want to try it yourself you can checkout "Fstrim" in the Playstore. It will tell you that its not supported.

Gesendet von meinem Nexus 4 mit Tapatalk 2

 

[aorestes]

My mobile is getting slower every day, I suspect that is because of the lacking TRIM implementation in the Kernel...

Do you guys experience the same slow down?

get the kitkat 4.4.2 from devcon_team ... it's much faster and smoother .. i tried this, yes it did feel very laggy ..
kitkat somehow works better eventhough still in beta, but works like a charm..

 

[Jann F]

TRIM is not needed for our type of EMMC. If you really want to try it yourself you can checkout "Fstrim" in the Playstore. It will tell you that its not supported.

Gesendet von meinem Nexus 4 mit Tapatalk 2

I already tried the needed commands in adb shell, but it only tells me that it's not supported by the kernel.

I got an SEM08G chip manufatured by SanDisk and according to it's product sheet it does support TRIM.
According to the CM Wiki it is also built in some Nook Color devices and is not affected by any brickbugs, therefore it would be possible for us to use it and speed our Device up
(http://wiki.cyanogenmod.org/w/EMMC_Bugs)

 

[rolandvrielink]

hi devs,

first of all: Keep up the good work!!

are the devs still working on this rom?
because they have updated already CM10.1 and CM11??

grtz roland

 

[anuseb89]

hi devs,

first of all: Keep up the good work!!

are the devs still working on this rom?
because they have updated already CM10.1 and CM11??

grtz roland

This is the least used rom ( after the stock rom..he he ) in our community..cm11 is much much better with regards to everything and frequent updates will be for cm11.. I would recommend you try it than waiting for an update of this one..

Sent from my Nexus 5 using xda app-developers app

 

[XeLLaR*]

Hi people,

I want to ask here how many people still use this rom.

Just write in a post "Here" so we can see how many people use it.

Gz
X

Gesendet von meinem Nexus 4 mit Tapatalk 2

 

[AnandMuralidhar]

Hi people,

I want to ask here how many people still use this rom.

Just write in a post "Here" so we can see how many people use it.

Gz
X

Gesendet von meinem Nexus 4 mit Tapatalk 2

I think it would be better if you ask the people using this ROM to thank a particular post instead of posting "Here", So as to avoid Spamming in the thread.

 

[DreamerTKM]

I think it would be better if you ask the people using this ROM to thank a particular post instead of posting "Here", So as to avoid Spamming in the thread.

Although they are asking everyone here to survey for how many people still using this ROM. But in my opinion, CM11 nearly reach the stable state as there are only minor and uncritical bugs that yet to be solved. ADC should plan to reduce their work load by stop releasing the older version of CM such as 10.1 & 10.2 and concentrate on CM11.

Maybe this will surely affect some of the users in this forum that still using the older version of CM but ADC team is providing all these ROM for FOC.

By discontinuing the older CM release,

1. they can have more time for their own life
2. few testers will be free up from testing the older CM version and focus on CM11 which may greatly improve the bug detection rate
3. they no need to take time to find out the weird / unsolved bugs in older CM version
4. able to speed up the development of CM11

We should try to adapt to new environment changes and the same applied to the android development as newer version will surely bring more benefits and fixes to end user. Just by personal opinion though and sorry if I hurt you.

 

[Mudu kai]

Although they are asking everyone here to survey for how many people still using this ROM. But in my opinion, CM11 nearly reach the stable state as there are only minor and uncritical bugs that yet to be solved. ADC should plan to reduce their work load by stop releasing the older version of CM such as 10.1 & 10.2 and concentrate on CM11.

Maybe this will surely affect some of the users in this forum that still using the older version of CM but ADC team is providing all these ROM for FOC.

By discontinuing the older CM release,

1. they can have more time for their own life
2. few testers will be free up from testing the older CM version and focus on CM11 which may greatly improve the bug detection rate
3. they no need to take time to find out the weird / unsolved bugs in older CM version
4. able to speed up the development of CM11

We should try to adapt to new environment changes and the same applied to the android development as newer version will surely bring more benefits and fixes to end user. Just by personal opinion though and sorry if I hurt you.

same opinion here

 

[Scalibq]

I guess that's why they're asking. Not much happens in this thread anymore, so it looks like not many people use CM10.2.
Which makes sense I suppose. I used CM10.2 myself, but moved to CM11, because I am a 'bleeding edge' user.
Then there are other people who stick to CM10.1, because it's a very stable and mature release. CM10.2 does not really offer anything useful over CM10.1 anyway.
So I suppose development for CM10.2 has been slowed down (I noticed there weren't as many K^Kernel releases either, no 370 MB kernel for example, which only makes CM10.2 run even worse, because it's a very heavy OS for our limited hardware).
Perhaps it's time to abandon CM10.2.

 

[Christopher83]

Thank you guys for your opinions! It's important for us to know what you think about this...
We'll release another build of CM 10.1 and CM 10.2, they are under test.
Then, we'll probably put EOL (End Of Life) status on CM 10.2, since it's to heavy for our device and it's impossible to reduce Surface Flinger reservation for custom kernels, because it becomes very unstable and bad working, this is the explanation for only one memory configuration on K^Kernel for JB 4.3.
CM 10.1, instead, since is still used by many of you, will be updated with important and useful features/bug fixes, even though CM Team completely moved on CM 11, so there're not so many updates from their side.

 

[ze7zez]

I support the team focus on one version. For us users it is also beneficial because less time is constant jumping from system to system.

 

[DevConnection_Team]

CyanogenMod 10.2 by ADC-Team - Release 3 (ION)

CM10.2 ION Release 3 is ONLINE!!

Enjoy!!

ROM:

• Synched with CM sources
• init: Remove duplicated commands (credits to erik96)
• ariesve: Add libdashplayer (credits to Christopher83)
• sepolicy: Allow SurfaceFlinger to read from /data/local/tmp (credits to Christopher83)
• BoardConfig: Build only the device provided CameraHAL (credits to Christopher83)
• BoardConfig: Use Qualcomm optimizations for Bionic libs (credits to Christopher83)
• cameraHAL: Fix taking a photo after video recording at 720P (credits to CastagnaIT)
• cameraHAL: fixed focus workaround for panorama (credits to CastagnaIT)
• overlay: config: Fix USB Tethering interface regex (credits to Christopher83)
• BoardConfig: Use retire fence for display (credits to Christopher83)
• prop: Enable non-omx mp3 decoder and remove obsolete max hidden apps (credits to arco68)
• Various changes for bluetooth (credits to arco68)
• cm: Remove unsupported settings (credits to Christopher83)
• AriesParts: Remove non translatable values (credits to Christopher83)
• AriesParts: Revised code for Utils class (credits to Christopher83)
• AriesParts: Support for BLN settings (credits to Christopher83)
• AriesParts: Italian translation for BLN settings (credits to Christopher83)

KERNEL:

• Kernel 3.4.77
• ancora: don't use FB console (credits to hadidjapri)
• msm: rotator: Wait for the pending commits in finish IOCTL (credits to Padmanabhan Komanduru)
• Updates and fixes to ARM memory management, timers and specific architecture routines (credits to CAF Team)
• Updates and fixes to ALSA and ASOC sound drivers (credits to CAF Team)
• Updates and fixes to Bluetooth drivers (credits to CAF Team)
• Updates and fixes to diagnostics driver (credits to CAF Team)
• Updates and fixes to EMMC/SD drivers (credits to CAF Team)
• Updates and fixes to IPC Router driver (credits to CAF Team)
• Updates and fixes to ION driver (credits to CAF Team)
• Updates and fixes to OnDemand CPU governor (credits to CAF Team)
• Updates and fixes to power management drivers (credits to CAF Team)
• Updates and fixes to serial drivers (credits to CAF Team)
• Updates and fixes to sync drivers (credits to CAF Team)
• Updates and fixes to framebuffer and display drivers (credits to CAF Team)
• Updates and fixes to qseecom driver (credits to AnilKumar Chimata)
• Updates and fixes to radio drivers (credits to CAF Team)
• Updates and fixes to USB drivers (credits to Rajkumar Raghupathy, Pavankumar Kondeti, Manu Gautam)
• Updates and fixes to video encoder/decoder drivers (credits to CAF Team)
• Updates and fixes to ZRam and ZSMalloc drivers (credits to CAF Team)
• Fix OTG support (credits to Rajkumar Raghupathy, Murali Nalajala, Vijayavardhan Vennapusa)
• drivers: staging: Fix Zcache (credits to Steve Kondik)
• mach-msm: Some changes to Ancora, Ancora_Tmo, Apache and Ariesve boards (credits to arco68)
• netfilter: xt_qtaguid: report only uid tags to non-privileged processes (credits to JP Abgrall)
• netfilter: x_tables: fix ordering of jumpstack allocation and table update (credits to Will Deacon)
• msm: kgsl: Protect against a potential overflow in kgsl_sg_alloc (credits to Jordan Crouse)
• msm: kgsl: avoid zero length scatterlist allocation (credits to Prakash Kamliya)
• msm: pm2: Setup memory for save/restore cpu registers early (credits to Christopher83)
• workqueue: Added null check and warning (credits to Srinivasarao P)
• android: lowmemorykiller: add lmk parameters tunning code. (credits to seungho1.park)
• android/lowmemorykiller: Account for total_swapcache_pages (credits to Liam Mark)
• defconfig: Disable CONFIG_ENABLE_VMALLOC_SAVING (credits to arco68)
• defconfig: Disable KGSL shadow writes (credits to arco68)
• ARM: kconfig: select HAVE_EFFICIENT_UNALIGNED_ACCESS for CPUv6+ && MMU (credits to Will Deacon)
• usb: msm72k_otg: Update OTG status management (credits to Christopher83)
• usb: msm72k_otg: Allow USB bus overdraw for Legacy OTG (credits to Christopher83)
• msm: Qdsp5v2: audio: Migrate to ION. (credits to Kalyani Polepeddy)
• audio: msm: qdsp5v2: Switch hostPCM driver to ION (credits to Kalyani Polepeddy)
• Initial commit for ION compilation errors (credits to Kalyani Polepeddy)
• msm: audio : Enable LPA (credits to Kalyani polepeddy)
• audio : Copyright correction. (credits to Kalyani polepeddy)
• msm: audio VOIP fixes. (credits to Kalyani polepeddy)
• msm: Remove all references to pmem from audio files (credits to Laura Abbott)
• qdsp5: memset stack buffer allocation (credits to Asish Bhattacharya)
• exFAT: Update to v1.2.5 (credits to arco68)
• defconfig: Disable NTFS and build exFAT as built-in (credits to arco68)
• Revert lowmem and vmalloc patches (credits to arco68)
• sensors_ariesve: gp2a_proximity: Fix unbalanced enable for proximity IRQ (credits to Christopher83)
• misc: bln: New implementation and changes for BLNv10 (credits to Christopher83)
• Update defconfigs (credits to Christopher83)

About BLN
New features have been implemented and applied various changes to better manage existent features and provide additional in-kernel features:

1. Add in-kernel management of notifications with static lights
2. Possibility to set separate intervals for blink ON and OFF transitions
3. Possibility to set or not set static lights after the timeout of blinking lights
4. Better timeout management for in-kernel blinking lights
5. Use a dedicated workqueue for scheduled works for blinking and static lights
6. Turn the lights off after system resume if a notification is ongoing
7. Remove duplicated calls to wakelock routines
8. Free up the reserved space when the module is removed
9. Some code cleanup, comments, copyright updates and other minor changes

You can find more details by looking at the commit on kernel repo:

misc: bln: New implementation and changes for BLNv10​

You'll also have an updated AriesParts (Advanced Settings) where you can find the new implementations to control BLNv10 features, so you can avoid to use external apps (eg. BLN Control) and simply set your preferred backlight notification settings inside BLN tab of AriesParts.
You can find more details by looking at the related commit on device repo:

AriesParts: Support for BLN settings​