Related
This thread is to help people with questions about my Jelly Bean ROM's.
Anything related to scripts (that I don't support for now)
[*]Anything related to re-size of my ROM
[*]Anything related to problems/issues you are facing which is not related to ROM (it can be third party apps)
[*]And questions in general....
Please respect everyone and help each other, If I am not replying to your messages doesn't mean I am not addressing you ( I will be busy always bringing in latest things)
Impression!
Firstly, your JB 4.2 rom is great though it still WIP.
Camera / video recoder still is a big issue on every JB rom excepts one here , how to fix it and related question still ahead. But I cant wait for a stable version, I am going to install and using your rom right now ^^
I'd love mobile photography, so I still looking for a new release include camera issues solved. For now, I am happy with your latest release! Thank for now and happy new year to you :victory:
// Sorry for my bad English.
elpvn said:
Firstly, your JB 4.2 rom is great though it still WIP.
Camera / video recoder still is a big issue on every JB rom excepts one here , how to fix it and related question still ahead. But I cant wait for a stable version, I am going to install and use your rom right now ^^
I'd love mobile photography, so I still looking for a new release include camera issues solved. For now, I am happy with your latest release! Thank for now and happy new year to you :victory:
// Sorry for my bad English.
Click to expand...
Click to collapse
Thank you and Happy New Year to you too..
Recommended SD card partitioning using 4ext
1024
Skip
Skip
EXT4
Thanks
INT2EXT
@ vijendrahs: Btw, can you made your rom build-in INT2EXT script? I think it will help we so much ^^
Thank again, special about Vietnamese include in your rom
Hi !
I have a question about the cpu governor :
- What is the best actually (ondemand ?)
- IO Scheduler, deadline ?
further very fast and very stable for me, my "tweak" for speed :
- KSM active
- 16 bits transparancy
- Dithering disabled
- 0,5x for each transition/animation/windows
Another dot : I have deleted all the ringtones to make space (before flash), and now I have only 504kb free on system, strange ? (stock hboot)
thanks VJ
Most of he tings are working well but I found some minor issues:
1. Random apps closed unexpectedly
2. I cannot enter to developer options, i got the message "Unfortunately, settings has stopped"
3. Strange java exception with fbreader and aldiko when open new book
4. Ugly artifacts when using camera
5. Missing FM radio application, it will be great if there is an internal app
I am using 4.0 and just find that there is 4.1.
Quick setting panel not work properly!
Bug report on your latest release:
Quick setting panel not work properly, it's missing on normal mode and just show properly in landscape mode
EDIT: Solved.
Also it will be great if you find little bit time to update the first page of the dev post with more information about ROM's features, know bugs and etc.
At the moment there is not such information except in the posts, but the you should read all of them if you want to find something you looking for ....
General question about recovery: a bit afraid to mess up the phone. I use Amon_RA recovery for the moment but read everywhere that it's better to use 4EXT. Can I simply install that recovery over the Amon_RA one? And then I can easily repartition the internal memory?
Many thanks for the guidance!
dEX2340 said:
General question about recovery: a bit afraid to mess up the phone. I use Amon_RA recovery for the moment but read everywhere that it's better to use 4EXT. Can I simply install that recovery over the Amon_RA one? And then I can easily repartition the internal memory?
Many thanks for the guidance!
Click to expand...
Click to collapse
Yes just run the 4EXT recovery apk and it will overwrite the existing recovery.
Take a back up of your SD card, wipe everything, partition 1-1.5gb of ext4 as primary partition and rest fat32. Ignore other secondary partitions. Its pretty straight forward with the tool.
Good luck.
Sent from my HTC Desire
balthor80 said:
Hi !
I have a question about the cpu governor :
- What is the best actually (ondemand ?)
- IO Scheduler, deadline ?
further very fast and very stable for me, my "tweak" for speed :
- KSM active
- 16 bits transparancy
- Dithering disabled
- 0,5x for each transition/animation/windows
Another dot : I have deleted all the ringtones to make space (before flash), and now I have only 504kb free on system, strange ? (stock hboot)
thanks VJ
Click to expand...
Click to collapse
On CM10.1 I find the interactive governor works best, along with a minor overclock to 1113. It's super smooth at that. I also use the same 0.5x animation tweeks. I do not like the 16 bit transparancy or disabling dithering, just don't like how it looks.
I'll give KSM a shot. I haven't tried that.
Has anyone tried Chrome? It has weird rendering issues for me. Anyone else?
Sent from my HTC Desire using xda app-developers app
is there a way to delete wallpaper into trebuchet : i have a static picture of green grass but i would like a black background.
I searched on forum but didn't found any answers for that
PS: the 4.1 version works great except missed call led notification and video cam.
has someone got a working Google tts for the cm 10.1?
managed to install it, but it doesn't talk.
anyone?
thanks
Klewe said:
has someone got a working Google tts for the cm 10.1?
managed to install it, but it doesn't talk.
anyone?
thanks
Click to expand...
Click to collapse
Yes, I would also like to know this, each time I tap the little mic on Google Talk it just FC
Parastie said:
Has anyone tried Chrome? It has weird rendering issues for me. Anyone else?
Sent from my HTC Desire using xda app-developers app
Click to expand...
Click to collapse
I have pico tts and talk back installed. They seem to work fine. Is there a specific thing you'd like me to test?
Sent from my HTC Desire using xda app-developers app
What's with hardwaredecoding for videoplayback? Does it work now?
Parastie said:
Has anyone tried Chrome? It has weird rendering issues for me. Anyone else?
Sent from my HTC Desire using xda app-developers app
Click to expand...
Click to collapse
I've tried it and it's true that there is some issues with it. Less than with the V3 but still there.
I think the main problem is that chrome need a lot of memory available and use more process / CPU than the original navigator.
Just a thing I want to know. I tried the V4 and the V4.1. In the V4, it was possible to add a widget with a long press on the desktop but when I've installed the V4.1, I wasn't able to find this functionality anymore.
Well, I didn't have the time to wipe and redo the installation again so I would like to know if it's just me or if this functionnality has been removed intentionnaly ?
Another question, about the lockscreen this time.
In the version 4.1.2, it was possible to change the wallpaper of the lockscreen but with the new one, they have removed this functionnality. Does anyone know how to change it to have a wallpaper different from the desktop ? (I know it's not from the rom but android itself)
Still, even if it has less fonctionnality, I prefer the previous one ... It would have been better if it was possible to arrange the lockscreen with widget (or app ?) like the desktop ! (well, it's just my point of view)
Parastie said:
I have pico tts and talk back installed. They seem to work fine. Is there a specific thing you'd like me to test?
Sent from my HTC Desire using xda app-developers app
Click to expand...
Click to collapse
In Google Talk, I have a little mic icon next to some of my contacts but when I tap on it the aplications force closes. Can you please try to reproduce this?
Also, voice commands doesn't get past the loading screen..
hi, just wondering if there are any roms available that are completely stable and finished for this phone?
if not, (as i have not found any), is the original stock rom (rojers) available to download anymore?
thanks guys..
jmpcrx said:
hi, just wondering if there are any roms available that are completely stable and finished for this phone?
if not, (as i have not found any), is the original stock rom (rojers) available to download anymore?
thanks guys..
Click to expand...
Click to collapse
After reading a lot, I believe I can confirm that only GB, and stock ICS are stable, as with no issues, some little glitches but no deal breakers. As for Rogers, there's only Osimod GB ROM based of Rogers. The rest are based of UCLJ3
lasuazo said:
After reading a lot, I believe I can confirm that only GB, and stock ICS are stable, as with no issues, some little glitches but no deal breakers. As for Rogers, there's only Osimod GB ROM based of Rogers. The rest are based of UCLJ3
Click to expand...
Click to collapse
ok thanks lasuazo ;--)
I guess omni and cm11
jmpcrx said:
hi, just wondering if there are any roms available that are completely stable and finished for this phone?
if not, (as i have not found any), is the original stock rom (rojers) available to download anymore?
thanks guys..
Click to expand...
Click to collapse
I may be off base here but I guess the [4.4] cyanogenmod 11 and omni ROM are pretty much stable ...
Though the pretty much is still a while away from complete the following are the general bugs with bubor's amazing Roms:
There is an audio bug when making VoIP calls which gives audio latency ..
There is fixed camera rotation which means all the pictures are in landscape
There is no Wi-Fi direct
Google experience launcher is not that Good looking (I know I am complaining)
Google maps 7 has issues but can be dual loaded with maps 6 so they work
Backlight,PPI, lag all have fixes though
Battery drain is a bit more
But as far as performance goes... They are pretty smooth..
So I guess make your choice
thefusor said:
I may be off base here but I guess the [4.4] cyanogenmod 11 and omni ROM are pretty much stable ...
Though the pretty much is still a while away from complete the following are the general bugs with bubor's amazing Roms:
There is an audio bug when making VoIP calls which gives audio latency ..
There is fixed camera rotation which means all the pictures are in landscape
There is no Wi-Fi direct
Google experience launcher is not that Good looking (I know I am complaining)
Google maps 7 has issues but can be dual loaded with maps 6 so they work
Backlight,PPI, lag all have fixes though
Battery drain is a bit more
But as far as performance goes... They are pretty smooth..
So I guess make your choice
Click to expand...
Click to collapse
i wish i could agree with you.. im running kitkat crdroid, and like every rom i have flashed over the years, has plenty of bugs that make it very annoying as a daily rom. phone switching off twice a day, icons/widgets dissapearing after rebooting, becomes laggy after a week or so of usig the rom, laggy browsing on all browsers, trebucket crashing regurly etc etc, thats on top of the bugs you list.. the only roms that are stable are completely finished official cm or miui roms (which there are none for this fone..). the stock rom is the only one that has not given me trouble. with the greatest respect to those that put their time i to make these roms, im sure people who flash them make them out to be more stable than they really are unfortunatelly.
Maybe we have developer aura or something like that? I'm sure I just used 4.4 PAC ROM for a week without reboot or any crashes. Bluetooth, fixed camera rotation and VoIP - yes, these are issues we can't fix, the same is with google maps v.7 (we just have no hardware NEON support that uses v.7 of maps). There is also issue with wi-fi: if you turn it off, it sometimes don't turns on until reboot. As for myself, I just never turn it off.
Besides of these issues, everything is smooth and stable. Really is. But I got sometimes trebuchet crashes - this was a time when I flashed dirty and didn't make a factory reset - the new trebuchet version sometimes conflicts with the data from old version. I just went to Settings - Apps, found Trebuchet (or Launcher3 if old version) and tapped Erase Data. And the issue was gone! But I recommend to always make a factory reset with new ROM. That's really important.
And even if you have those constant trebuchet bugs whatever you do (icons disappearing is also a trebuchet bug, I never encountered it though), just install a different launcher. Google now launcher is the basic, and is like trebuchet in many ways, miui one is also good, and others, they are many!
I had problems with some icons disappearing when the system reboots. I found that the icons that disappeared were for applications which were installed on the SD card. When I moved them to the system, they stopped disappearing.
Makshow said:
Maybe we have developer aura or something like that? I'm sure I just used 4.4 PAC ROM for a week without reboot or any crashes. Bluetooth, fixed camera rotation and VoIP - yes, these are issues we can't fix, the same is with google maps v.7 (we just have no hardware NEON support that uses v.7 of maps). There is also issue with wi-fi: if you turn it off, it sometimes don't turns on until reboot. As for myself, I just never turn it off.
Besides of these issues, everything is smooth and stable. Really is. But I got sometimes trebuchet crashes - this was a time when I flashed dirty and didn't make a factory reset - the new trebuchet version sometimes conflicts with the data from old version. I just went to Settings - Apps, found Trebuchet (or Launcher3 if old version) and tapped Erase Data. And the issue was gone! But I recommend to always make a factory reset with new ROM. That's really important.
And even if you have those constant trebuchet bugs whatever you do (icons disappearing is also a trebuchet bug, I never encountered it though), just install a different launcher. Google now launcher is the basic, and is like trebuchet in many ways, miui one is also good, and others, they are many!
Click to expand...
Click to collapse
like i said in my first post, i do really appriciate the fact that people spend Alot of time cooking theese roms, and it easy for me to come along and moan about them, but i have found over the years that after using a custom rom for a couple of weeks or so, its like the ram seems to gradually get eaten away, the device gradually slows down, becomes laggy and ultimately unuseable (not just this fone, and not just me that says this). im not saying all are like this, just many i have used, mainly because they never get finished.
i am very open though to people suggesting that i am doing something wrong, and maybe you have picked up on that something.. you say you do a factory reset, can i ask, do you mean a factory reset in the fone settings, or are you referring to a full wipe using cwm/twrp? as when i flash, i wipe everything accept what i dont want wiped on the external sd.. i dont factory reset, is this after you have flashed the new rom? or before you flash a new rom?
also thank you for the erase data tip for trebucket, i will try that.. i have not used the google now launcher yet, but i tried using miui launcher but when i went back to trebucket the lockscreen stayed as the miui lockscreen, which has happened on past cm roms, so i just deleted it.
just gets a bit frustrating when you spend hours getting everything working/setting up personalisation, then the phone just seems to start getting worse day by day, but maybe like you say, its cos i "dirty flashed"?
linuxguy42 said:
I had problems with some icons disappearing when the system reboots. I found that the icons that disappeared were for applications which were installed on the SD card. When I moved them to the system, they stopped disappearing.
Click to expand...
Click to collapse
i did think that, and im sure you are right, but i have had every app/folder/widget dissappear twice now, then, randomly over several restarts, some widgets/apps will replace themselves over the top of the new ones i have just newly placed there.. strange, but i have came across this before on cm roms, so im sure there is a bug there somewhere, even if it is not too common..
jmpcrx said:
you say you do a factory reset, can i ask, do you mean a factory reset in the fone settings, or are you referring to a full wipe using cwm/twrp? as when i flash, i wipe everything accept what i dont want wiped on the external sd.. i dont factory reset, is this after you have flashed the new rom? or before you flash a new rom?
Click to expand...
Click to collapse
Yes, what you do should suffice. I meant cwm/twrp wipe (boot, system, data, cache, android.secure). SD card is not touched. So you are doing fine with that, but anyway, there has to be something make those issues... Can you look at /system/addon.d folder? There is stored info about files that will be preserved even if you install a new ROM with a wipe. If there are many leftovers from ROMs or programs you tried earlier, then you should try to manually clear this folder before new ROM install.
the device gradually slows down, becomes laggy and ultimately unuseable
Click to expand...
Click to collapse
That was the point with pre-4.2 ROMs, and even with 4.2 there was a bug with gallery thumbnails which made it to eat gigabyte and more of storage after some time. That was fixed in CM 10.1.3. Also a Lite-Kernel used by earlier ROMs is very great, but has its issues, for example, systemui crashes when camera launch after some phone use and sleep of death.
I used CM 10.1.3 for a a three months and still keeping a backup of it for a some case. There was no slowing or lagging, it was almost perfect (if you don't use VoIP or BT handset) even after those months of use. Strangely, but I didn't have even "settings -> about crash" issue bubor listed!
Welll here are some tip which have helped me
jmpcrx said:
i wish i could agree with you.. im running kitkat crdroid, and like every rom i have flashed over the years, has plenty of bugs that make it very annoying as a daily rom. phone switching off twice a day, icons/widgets dissapearing after rebooting, becomes laggy after a week or so of usig the rom, laggy browsing on all browsers, trebucket crashing regurly etc etc, thats on top of the bugs you list.. the only roms that are stable are completely finished official cm or miui roms (which there are none for this fone..). the stock rom is the only one that has not given me trouble. with the greatest respect to those that put their time i to make these roms, im sure people who flash them make them out to be more stable than they really are unfortunatelly.
Click to expand...
Click to collapse
i .. umm.. well i agree that as of now they have issues but they will get better .. ours is an old device... so i guess we should tread slowly . which is exactly what the developers are doing .. .
and i agree on the ram hungry part but there are ways for that too . .
funny i have been messaging people to help me post this stuff through them . . but well thats the prob with being a junior member .
My personal tested suggestions for omni rom which have really incremented to the performace some of which are :
- using one of the lightest launchers as i find trebuchet and even google launcher RAM hungry is 'Lightning Launcher' the bloody app itself is in BYTES!!
-also i use link2sd with ext4 that helps in storage and also use sd maid for regular clean up.
-also i have been testing memory swapping using linux swap partition on sd card (class 10 ) and yeah i know it degrades sd card but oh well like Glados testing testing testing
-i have also switch off startup at boot for certain apps
and i apologize for posting what maybe well known tricks or improvs but i really dont know where else to post these (still have the ten post ban from posting )
and if these dont help then sorry to waste your time . .
PS anyone think an F2FS file system like for the nexus7 would\might help ?
tl;dr use the given tips maybe they might help . . and with custom roms i guess you have to spend time to keep them running well .
Makshow said:
Yes, what you do should suffice. I meant cwm/twrp wipe (boot, system, data, cache, android.secure). SD card is not touched. So you are doing fine with that, but anyway, there has to be something make those issues... Can you look at /system/addon.d folder? There is stored info about files that will be preserved even if you install a new ROM with a wipe. If there are many leftovers from ROMs or programs you tried earlier, then you should try to manually clear this folder before new ROM install.
That was the point with pre-4.2 ROMs, and even with 4.2 there was a bug with gallery thumbnails which made it to eat gigabyte and more of storage after some time. That was fixed in CM 10.1.3. Also a Lite-Kernel used by earlier ROMs is very great, but has its issues, for example, systemui crashes when camera launch after some phone use and sleep of death.
I used CM 10.1.3 for a a three months and still keeping a backup of it for a some case. There was no slowing or lagging, it was almost perfect (if you don't use VoIP or BT handset) even after those months of use. Strangely, but I didn't have even "settings -> about crash" issue bubor listed!
Click to expand...
Click to collapse
ok thanks, i cleared the data in trebucket, and started again with placing apps/widgets on home screen, and i also have deleted the hacked version of adobe flash that you install with dolphin browser, and, supprisingly after a couple of days of testing, my apps/widgets are not deleting themselves, the phone is significantly less laggy, and i have had no switch offs, so, im very pleased with that! so id suggest against downloading that version of flash player with this rom..
thefusor said:
i .. umm.. well i agree that as of now they have issues but they will get better .. ours is an old device... so i guess we should tread slowly . which is exactly what the developers are doing .. .
and i agree on the ram hungry part but there are ways for that too . .
funny i have been messaging people to help me post this stuff through them . . but well thats the prob with being a junior member .
My personal tested suggestions for omni rom which have really incremented to the performace some of which are :
- using one of the lightest launchers as i find trebuchet and even google launcher RAM hungry is 'Lightning Launcher' the bloody app itself is in BYTES!!
-also i use link2sd with ext4 that helps in storage and also use sd maid for regular clean up.
-also i have been testing memory swapping using linux swap partition on sd card (class 10 ) and yeah i know it degrades sd card but oh well like Glados testing testing testing
-i have also switch off startup at boot for certain apps
and i apologize for posting what maybe well known tricks or improvs but i really dont know where else to post these (still have the ten post ban from posting )
and if these dont help then sorry to waste your time . .
PS anyone think an F2FS file system like for the nexus7 would\might help ?
tl;dr use the given tips maybe they might help . . and with custom roms i guess you have to spend time to keep them running well .
Click to expand...
Click to collapse
some good tips there, thankyou, i havent tried any of them yet, but i will have a go at some of them and see what happens.. thanks thfusor..
jmpcrx said:
hi, just wondering if there are any roms available that are completely stable and finished for this phone?
if not, (as i have not found any), is the original stock rom (rojers) available to download anymore?
thanks guys..
Click to expand...
Click to collapse
For what it's worth, I recently had to reflash and decided to use dman325's stock UCLJ3. (He has two versions, stock and one with the aosp lockscreen. If you decide to use either, use the stock one. dman325 had to resign the aosp one with a test signing key that, recently, got invalidated or declined and it prevents Google Play from updating past 3.7.15 and Google Play Services wont install at all because of a shared_uid fault due to certificate conflict, etc.)
I got frustrated with the amount of bloat in an otherwise vendor fun-packed rom, so I went in and hacked out lots of crap. Largely relying on either "what is safe to get rid of" lists for similar samsung phones and my own poking around/guestimation using dex2jar and jd-gui. I really, honestly don't understand what InputEventApp.apk was meant to do. Seriously. But, getting rid of it reduced the logcat spam tremendously. Also, the wsslcm* apks are somewhat frightening in appearance.
I've gone a few steps further, I modified android.policy.jar smali to prevent the emergency dial option from showing up on the lock screen - I accidentally pocket dialed 911 a year ago and am not about to do that again. I also modified the kernel ramdisk image to set ro.debuggable=1 and ro.secure=0. I tried, while I was at it, to replace /dev/random with /dev/urandom, but I'll have to do some experimenting.
I've added a few static binaries for proper gnu utilities. bash, ls, grep, sort, du, etc. It surprises me that a functional shell environment doesn't get more attention on phones with keyboards.
So, that's my $0.02. Try the stock UCLJ3 and fiddle with it a bit. Good luck.
etherfish said:
For what it's worth, I recently had to reflash and decided to use dman325's stock UCLJ3. (He has two versions, stock and one with the aosp lockscreen. If you decide to use either, use the stock one. dman325 had to resign the aosp one with a test signing key that, recently, got invalidated or declined and it prevents Google Play from updating past 3.7.15 and Google Play Services wont install at all because of a shared_uid fault due to certificate conflict, etc.)
I got frustrated with the amount of bloat in an otherwise vendor fun-packed rom, so I went in and hacked out lots of crap. Largely relying on either "what is safe to get rid of" lists for similar samsung phones and my own poking around/guestimation using dex2jar and jd-gui. I really, honestly don't understand what InputEventApp.apk was meant to do. Seriously. But, getting rid of it reduced the logcat spam tremendously. Also, the wsslcm* apks are somewhat frightening in appearance.
I've gone a few steps further, I modified android.policy.jar smali to prevent the emergency dial option from showing up on the lock screen - I accidentally pocket dialed 911 a year ago and am not about to do that again. I also modified the kernel ramdisk image to set ro.debuggable=1 and ro.secure=0. I tried, while I was at it, to replace /dev/random with /dev/urandom, but I'll have to do some experimenting.
I've added a few static binaries for proper gnu utilities. bash, ls, grep, sort, du, etc. It surprises me that a functional shell environment doesn't get more attention on phones with keyboards.
So, that's my $0.02. Try the stock UCLJ3 and fiddle with it a bit. Good luck.
Click to expand...
Click to collapse
thanks etherfish, if i continue to have probs i may well do that, i was thinking about going back to stock. dont think i have the confidence to fiddle like you have though as im more of a windows man than linux, but thanks for the great advice
jmpcrx said:
thanks etherfish, if i continue to have probs i may well do that, i was thinking about going back to stock. dont think i have the confidence to fiddle like you have though as im more of a windows man than linux, but thanks for the great advice
Click to expand...
Click to collapse
Well, you learn by doing, I believe. Also, I have a classy - for a flip phone - Motorola Razr2 v8 kicking around I can always put my SIM into if I've managed to hose my captivate glide. Also, I'm replying because I can't post in the rom development forum until I have 10 posts. Hurray for well founded, but nonetheless arbitrary restrictions. So, a number of things have piqued my curiosity.
So, first of all, this surprised me in the logs:
Code:
I/Launcher( 2263): onCreate(): product model family:U1 product model : GT-I9221
I'd always wondered why I had an SGH-I927 when other phones, like the remarkably similar Galaxy R, are GT-I9103. Is/was GT-I9221 an internal reference?
Also, there are other inconsistencies, for example:
Code:
D/RILJ ( 426): [1718]> REQUEST_GET_NEIGHBORING_CELL_IDS
D/RILJ ( 426): [1718]< REQUEST_GET_NEIGHBORING_CELL_IDS error: com.android.internal.telephony.CommandException: REQUEST_NOT_SUPPORTED
If you jump into the debug/field test menu system, (dial *#*#197328640#*#* ) you can bring up the list of neighboring cells in both GSM and WCDMA modes... So, why is the request marked not supported? Furthermore, why didn't samsung disable the request in the first place if they went to the trouble of disabling it from working. I imagine this has a reason, but I doubt it's a terribly great one.
And the FM receiver? I do believe our broadcom BCM4329 is a bluetooth+wifi_in_an_sdcard (well, SDIO really, but still, not pci-e and not usb.) and has an FM receiver built in, but it's omitted and hidden?
Code:
W/AudioPolicyManager( 112): FM radio recording off
Oh, the conspiracy theories. And then there's the weird lines you discover if you dump the string identifiers from /system/bin/drexe!
For example, these lines are all sequential:
Code:
broadcast -a android.provider.Telephony.SECRET_CODE android_secret_code://767*3855
InvokeOemRequestHookRaw broadcast factorst OK
InvokeOemRequestHookRaw factorst fail %d
/system/.configure.txt
(what's with /system/.configure.txt???)
Do not type 767*3855 into your phone. It's the factory wipe code or possibly part of it. I do believe drexe is the DataRouter you often see spamming the logs with:
Code:
E/DataRouter( 107): usb connection is true
E/DataRouter( 107): DSR is ON. Don't send DTR ON.
And we find these strings in drexe:
Code:
__initialize_usb_ipc
/data/.usb_stream
usb connection is true
InvokeOemRequestHookRaw usbstatus true is success
oh, and:
Code:
pipe failed (%s)
fork failed (%s)
child pid = %d.
execute sh.
system/bin/sh
execl fail %d
What do you think? Why does drexe seem to have code to support and start a shell? Well, if nothing else, thank you for reading.
P.S. I don't suspect anything the least bit conspiracy like, malicious, or devious. I've worked for some huge companies; i don't think it'd be likely.
etherfish said:
Also, I'm replying because I can't post in the rom development forum until I have 10 posts. Hurray for well founded, but nonetheless arbitrary restrictions.
Click to expand...
Click to collapse
Technically, you can post in cappy dev forums started from 3 posts. I saw someone posting there his fourth post.
As for other things you listed... Well, I'll be glad to have an FM receiver in our glide. But I really think that reason for all this staff can be as simply as hands growing from wrong place or restricted development time...
Makshow said:
Technically, you can post in cappy dev forums started from 3 posts. I saw someone posting there his fourth post.
As for other things you listed... Well, I'll be glad to have an FM receiver in our glide. But I really think that reason for all this staff can be as simply as hands growing from wrong place or restricted development time...
Click to expand...
Click to collapse
I recently, after some research, also installed dans stock (i decided to go complete stock since i didnt know what the lock screen thing meant).
I havent had any trouble with being outdated. Only thing i noticed (unless im doing it wrong, im new to this phone) was that screencaps dont work. its power button and volume down, right?
Other things id like to customize are data being in the top drawer instead of bluetooth (since i never use it), and id like to be able to see who texted me on the lock screen, but while still using the stock messaging app, and without an app having to constantly run.
Other than those couple of things its been great!
im HOPING down the road for an un-buggy or at least minimally buggy version of 4.4. well see what happens with that i guess.
Some help
Pawprints1986 said:
I recently, after some research, also installed dans stock (i decided to go complete stock since i didnt know what the lock screen thing meant).
I havent had any trouble with being outdated. Only thing i noticed (unless im doing it wrong, im new to this phone) was that screencaps dont work. its power button and volume down, right?
Other things id like to customize are data being in the top drawer instead of bluetooth (since i never use it), and id like to be able to see who texted me on the lock screen, but while still using the stock messaging app, and without an app having to constantly run.
.
Click to expand...
Click to collapse
well i always say stock is best cause it IS optimized however there are things like keep and total Google integration that i like so i updated to kit kat
for screen caps if they dont work i could maybe suggest an application called super manager its pretty loaded it has screen cap and may even give you prox sense wake up for device.
also customizing the drawer hmm.. i guess you could try xposed framework but please be careful and make a backup before
as for who texts you and the content of the text you could try dash clock its able to do a lot
hello guys I was just wondering if I could get some help since I returned back to fully Ice Cream Sandwich Stock. I completely removed all the system bloat with link2sd, uninstalled all att crap. Can anyone recommend me something since I feel the ram consuption still to high... battery so far is doing kind of good almost as in crdroid
But i believe it can be improved. Any recommended settings or something else i can do? Already tried lite kernel but it gave me some issues. Rather keep stock. Any recommendations please guys. Also if you know a "ok google" like app or something as a swifty assistant would be nice. Please recommend. Thanks in advance
jmpcrx said:
hi, just wondering if there are any roms available that are completely stable and finished for this phone?
if not, (as i have not found any), is the original stock rom (rojers) available to download anymore?
thanks guys..
Click to expand...
Click to collapse
Hi,
well that depends.. on what you mean with "finished"
I have tested all (3 months ago) available ROMs for the Glide. IMO the best available ROM is PACman but as said it depends. I used pac_i927-milestone.1.RC1.4.zip for a long time (months) without having any issues besides Bluetooth Headset which is a general problem in JB and higher version). I have tried other PACMan ROM versions as well but the above one was the best of stability and battery life (in my case).
So it depends what features you really need or are a must-have for you. If you do not have bluetooth headsets I would recommend the above otherwise .. well I would recommend sediROM
Regards
xdajog
---------- Post added at 02:39 PM ---------- Previous post was at 02:33 PM ----------
lasuazo said:
hello guys I was just wondering if I could get some help since I returned back to fully Ice Cream Sandwich Stock.
Click to expand...
Click to collapse
Haven't done that before but would be rooted ICS stock also ok for you?
If so:
--> search for thread ID 1994902 or search for: [ROM] Stock UCLJ3 Rooted, Deodexed, Zipaligned
(sorry not allowed to post links..)
Regards
xdajog
[Q&A] [SM-T520] CyanogenMod 11.0 Official Nightlies for the Tab Pro 10.1 Wifi (picas
Q&A for [SM-T520] CyanogenMod 11.0 Official Nightlies for the Tab Pro 10.1 Wifi (picassowifi)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [SM-T520] CyanogenMod 11.0 Official Nightlies for the Tab Pro 10.1 Wifi (picassowifi). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Guys, I am using m11 snapshot version and I sense that the battery is draining very fast and the tab is heating up too . For example , I played 30min of hay day and lost 35 % of my battery and it was very hot while I played . Playing on my xperia ultra z for 1 hour and 30 minutes, lost only 27 % of my battery and it does not heat up like the tab . Anyone have these problems , is this normal? Some kernel to recommend I use , I'm using the stock cm11 kernel .
Best regards.
MastherAndroid said:
Guys, I am using m11 snapshot version and I sense that the battery is draining very fast and the tab is heating up too . For example , I played 30min of hay day and lost 35 % of my battery and it was very hot while I played . Playing on my xperia ultra z for 1 hour and 30 minutes, lost only 27 % of my battery and it does not heat up like the tab . Anyone have these problems , is this normal? Some kernel to recommend I use , I'm using the stock cm11 kernel .
Best regards.
Click to expand...
Click to collapse
Try the latest nightly. I have made big changes to the interactive governor that reduce the power utilization.
crpalmer said:
Try the latest nightly. I have made big changes to the interactive governor that reduce the power utilization.
Click to expand...
Click to collapse
Thank crpalmer. I'll try that last buid, I was using the day 18/10, but it has the problem of freezing. so I roll back to m11.
Is there a way to get screencast to work? I've tried to use the cast screen within the display setting but it doesn't work...
I can get Chromecast to work but not screencast..
Sent from my SM-T520 using XDA Free mobile app
Hi,
I've encounterd some issues when copying files from my PC (Windows 7) to the SD card inserted in the tab, both cnnected by the USB data cable.
The copy sometimes stops with an error message : the device is no more connected. In fact, it is still, and the tab begins to be slow. The only way back is to disconnect and reboot the tab.
As I had formatted the SD with the stock ROM, I re-formated it with CM : the issue is still present.
NB : the usb cable data is almost new (from September 14) and the SD card never bugged before (with stock ROM I mean).
Thanks
Since Nightly of 21 I get a Camera Crash. The following messages will be displayed, otherwise only "Can not connect to camera". The Annex also provides the log.
Would love to post directly in the appropriate thread, but need only 10 posts ...
I have it as a system app. After I clear cache and wipe data and uninstall all updates and aplly you recommended version it crashes......But thank you anyway. It seems to me that youtube app can not be a system app, it can not be updated, you have to install it in clean way from the begining...
Back camera issue
I have the 20141025-Nightly (updated today), but the back camera doesn't work
---------- Post added at 06:44 PM ---------- Previous post was at 06:31 PM ----------
KL7000F said:
Since Nightly of 21 I get a Camera Crash. The following messages will be displayed, otherwise only "Can not connect to camera". The Annex also provides the log.
Would love to post directly in the appropriate thread, but need only 10 posts ...
Click to expand...
Click to collapse
I got the same issue
20141026 nightly camera issue
Hi, I am running 26/10 nightly and get a "can't connect to camera" error on Facebook. Also, no camera app is working. Just a message to let you know.
daddyscooltv said:
Is there a way to get screencast to work? I've tried to use the cast screen within the display setting but it doesn't work...
I can get Chromecast to work but not screencast..
Sent from my SM-T520 using XDA Free mobile app
Click to expand...
Click to collapse
There is a Hack called #MirrorEnabler that will allow for that
R-thur said:
Hi, I am running 26/10 nightly and get a "can't connect to camera" error on Facebook. Also, no camera app is working. Just a message to let you know.
Click to expand...
Click to collapse
There have been a lot of camera changes lately. Can you ("you" being those reporting camera problems) remind me next weekend if it is still a problem? Nothing has changed in the device related to the camera and, given that I don't have a lot of time this week, I would like to make sure that those changes have stabilized before I try to see if we have a device specific problem that is somehow being triggered as a result of those change (aka, nothing has changed in our device so either the upstream changes are broken or they triggered a problem that was latent in our device support).
crpalmer said:
Try the latest nightly. I have made big changes to the interactive governor that reduce the power utilization.
Click to expand...
Click to collapse
There was no way, as last night it still heats up a lot and the battery dies very fast , which does not happen in the damn stock rom.
I also get camera crashes on the October 26th and October 27th nightly. However, I was able to get an application called HD camera ultra to function with the back camera on the 27th build. So, at least third party camera apps can access the camera hardware as of 20141127. I also note accelerated battery consumption versus stock rom. I've dropped my maximum CPU speed to 1700 and forced minimum to 250. Hopefully I can squeeze a little more juice out of the battery. Overall, I still think this is a much better ROM than stock.
Sent from my SM-T520 using Tapatalk
BoulderGeek said:
I also get camera crashes on the October 26th and October 27th nightly. However, I was able to get an application called HD camera ultra to function with the back camera on the 27th build. So, at least third party camera apps can access the camera hardware as of 20141127. I also note accelerated battery consumption versus stock rom. I've dropped my maximum CPU speed to 1700 and forced minimum to 250. Hopefully I can squeeze a little more juice out of the battery. Overall, I still think this is a much better ROM than stock.
Sent from my SM-T520 using Tapatalk
Click to expand...
Click to collapse
What battery life are you getting under what usage?
What was your min CPU spped before forcing it to 250?
crpalmer said:
What battery life are you getting under what usage?
What was your min CPU speed before forcing it to 250?
Click to expand...
Click to collapse
Hi, Chris,
I was at 400/1900. I never timed the runtime. It just seemed to need to go on the charger about twice as fast as stock. So, maybe 5 or 6 hours of occasional use in the day, versus 10-11 on stock. General e-mail, static webpage reading, Flipboard and Play News reading, etc. No video or YouTubing.
I did do a Hangouts videochat, yesterday. Front facing camera, audio and microphone worked fine. I tried to switch to rear and it crashed. So, that's cool. I use front camera more than back. I typically take photos with my phone, not the tablet.
What's the optimal scheduler? Interactive?
Thanks for your work on this ROM. Even though the SM-T520 has blazing hardware, I was a little envious of my GF with my old Galaxy Tab 10.1, since it ran CM11 just fine. Now I have the best of both worlds.
crpalmer said:
There have been a lot of camera changes lately. Can you ("you" being those reporting camera problems) remind me next weekend if it is still a problem? Nothing has changed in the device related to the camera and, given that I don't have a lot of time this week, I would like to make sure that those changes have stabilized before I try to see if we have a device specific problem that is somehow being triggered as a result of those change (aka, nothing has changed in our device so either the upstream changes are broken or they triggered a problem that was latent in our device support).
Click to expand...
Click to collapse
Hello crpalmer,
the error is still present. The current nightly of 28 does not change this. A complete Fullwipe and new reinstall did not help. Also, third-party apps can find no connection to the camera.
Greetings and thanks for your great work!
Andy
Camera wont open.
just updated to today's nightly dated today the 29th released few minutes ago, and camera won't open again, getting the error: won't connect to camera. i will try and apply a patch for camera fix and see how it goes.
Thank you hopefully we will have a fix soon. Thank you.
Also can someone please help i have 16GB and CM11 only recognizes 11GB of internal storage, is there any fix....
lbejta said:
just updated to today's nightly dated today the 29th released few minutes ago, and camera won't open again, getting the error: won't connect to camera. i will try and apply a patch for camera fix and see how it goes.
Thank you hopefully we will have a fix soon. Thank you.
Also can someone please help i have 16GB and CM11 only recognizes 11GB of internal storage, is there any fix....
Click to expand...
Click to collapse
As I said, I don't have much time this week and to remind me next week if it hasn't fixed itself...
Camera works again, using nightly 30/10
This is a no-frills thread.
I am looking for additional competent testers to provide proper feedback.
Testers are assumed to be experienced. Thank you.
Okay here it is.
Flash in order of appearance. Required.
cm_ivy-test_rebuild.zip
cm13_ivy_updater_system-etc.zip <--Fixes audio.
cm13_ivy_updater_bootimage_ round1.zip <-- Fixes external storage
Thanks @MotexT for initial testing and feedback.
So, working:
All CM apps; RIL; WiFi, Bluetooth; Theme Engine, Audio, Bluetooth/WiFI Hotspot work confirmed
Buggy:
Bluetooth (crashes of Bluetooth Share);
Camera (color bugs, frontal camera take photos with glitches);
Initial load/Load after reboot (glitches, performance loss - solving easy with locking/unlocking device);
AutoBrightness (small delay when switching brightness levels on the fly)
Screen Recorder
Not working:
NFC;
External SD Card;
OTG
Click to expand...
Click to collapse
Again this is alpha. This is for sinlge sim, you are welcome to test on dsds, i would be very interested in the results.
Cyanogenmod Source
Thanks to/for
@CTXz Sources and convincing me to get a Z5P instead of another Sammy device.
Sony Kitakami Platform Developer Organization
@zacharias.maladroit For answering questions, many questions. [ still have more... xD ]
Those of you without a sense of humor, go away.
Okay current features i'm working on and stuff that works/doesn't work
UVC support enabled in kernel. probably need to build rom-side support still. libuvc avutils etc.
- This is for plugging in camera devices in conjuction with apps like LegitDashcam.
USB Gadget functionality as per pelya's work ,
- pelya/android-keyboard-gadget
I am working my kernel source here toward net-huntery goodness.
The rest you tell me, and you tell me properly. Messages like
"waahhh my whatchamhoozit is all floompy"
are not acceptable.
This is not a random discussion thread either. Idle chatter belongs in general.
This is also NOT a discussion thread for Xposed,Viper, etc..
Thank you.
m
Notes and Updates
NOTE
SELinux is COMPLETELY disabled on this build. If You want security go back to stock.
SELinux enforcing is the goal though.
I strongly recommend using a "traditional" root os SuperSU over systemless-root.
Reasons:
Opengapps requires a factory-reset or fresh install to set up correctly!
Privacy Guard based root sucks. It forgets alot of permissions granted.
Use BETA-SuperSU-v2.52
Would have posted earlier but needed a smoke break *>cough<*
NOTE: this initial offering is in 3 parts due to limited bandwidth issues.
When i have resolved external storage i will upload a new build.
NFC may take a little longer.
Breathing Room
Reserved 2
@MotexT will be posting screens, as time permits, in post number 4.
Trolls will be burned.
Screenshots
Here we have some screenshots. If you need more - PM me, will add them ASAP. Also include the type of screenshot.
I'm using a single SIM version.
Please continue the work. I'll start testing by the weekend.
lukeaddison said:
I'm using a single SIM version.
Please continue the work. I'll start testing by the weekend.
Click to expand...
Click to collapse
Thanks,
If i can get you to specifically test and log screen recorder that would be great. [including during playback]
Currently it appears to function but when it comes to playback of the recorded file, playback breaks.
Thanks.
m
Hy well this thread need a clean start
And I will test it this weekend
(single sim) hopefully it works like a charm and till then i hope you fix some little bugs you mention
BTW cause I have a SmartWatch (moto360)
Does the Bluetooth restart or dont work like it should be?
Sent from my E6553 using XDA-Developers mobile app
So, a small report about this ROM. For now I'm using it two days in a row, and it's pretty stable - you can use main functions without any troubles: WiFi, RIL, Themes Engine etc. Bluetooth works great, crashes sometimes and automatically restarts - not a big deal. It's a really smooth for alpha build and could be used even as daily driver if you close your eyes on some small bugs with not so important stuff. Anyways, testers are welcome
KOALAaufPILLEN said:
Hy well this thread need a clean start
And I will test it this weekend
(single sim) hopefully it works like a charm and till then i hope you fix some little bugs you mention
BTW cause I have a SmartWatch (moto360)
Does the Bluetooth restart or dont work like it should be?
Click to expand...
Click to collapse
K, actually i don't know. But it's cool that you have a smart watch, would you mind be a tester/logger for that function in particular?
That would be great.
Thanks
m
Single sim
How to solve this？:crying:
Full selinux support is present.
MTP Enabled
installing '/sdcard/cm_ivy-test_rebuild.zip'...
checking for MD5 file...
Skipping MD5 check: no md5 file found
target:sony/cm_ivy/ivy:6.0.1/Nega_spork/76b3bfd6c4:user debug/test-keys
could not detect filesystem for /dev/block/bootdevice/by-name/system,assuming ext4
mount:failed to mount /dev/block/bootdevice/by-name/system at /system failed;no such volume
E:Error executing updater binary in zip '/sdcard/cm_ivy-test_rebuild.zip'
Error flashing zip '/sdcard/cm_ivy-test_rebuild.zip'
updarting partition details...
......done
Hi , you are most likely using the wrong recovery for your device
See here and get a correct recovery
http://forum.xda-developers.com/xperia-z4/development/twrp-xperia-z3-fota-recovery-t3346298
moonbutt74 said:
Hi , you are most likely using the wrong recovery for your device
See here and get a correct recovery
http://forum.xda-developers.com/xperia-z4/development/twrp-xperia-z3-fota-recovery-t3346298
Click to expand...
Click to collapse
it really works!Thank you
Ok cleaned this up a bit.
I don't really have much issue with discussion on GIT etiquette, and tips to keep your "house clean" as it were. I think that's a good thing with devs working together on things like that.
Here's the bottom line. If you are merging commits into a kernel you have to keep the original authorship, period. To do otherwise is kang. We all know this.
Now if some dude has some private repo where during personal testing authorship is removed, but anything merged into the public kernel or the release repo/binary maintains proper authorship, then that is a bit gray, but the user is not clearly attempting to claim authorship at all.
If anyone sees a blatant kang, or attempt to hide/claim authorship, please report to the mods for handling. If this particular point needs more discussion, please open up a thread about it and have a non flame war discussion about it.
@moonbutt74 - I do ask that you make it very blatantly sure what your public release repo is, and that your authorship is maintained, and I actually recommend you do not link your personal playground repo to avoid situations.
Thanks guys.
After looking thru all and speaking with the OP, I am closing this thread.
Just got a bit tired of little bugs in the CM13 based roms and thinking about switching back to CM11. The only concern is the lack of security updates after the maintainers abandoned the projects for newer android versions.
Did anyone here try downgrading? Or maybe never upgraded? Is it wise to do so?
Some of my issues with CM13 based roms which have put me off:
Insane lag when reciving calls
Adopting Storage doesn't work half the time
Front Camera crashes
Mobile Data issues
Lock Screen Wallpaper Issue
Music suspend bug
Battery drain Issue
LOL brother. I am still using CM 11 build 14/11/15 with Xcelerate kernel build 4/12/15.
I still used this OS as it gives me atleast 500+mb ram which I require a lot for gaming.
At battery 100%............(with airplane mode on)...wifi on After 3hrs of continuous wifi gaming my battery drops to around 20%.
So I guess battery life is good.......though i haven't activated any sim cards(that would be a different story)
I don't have any voice(call) related problem though. Only bug is HDR. Once a picture is clicked with HDR on, you have to exit camera to click again in HDR mode
I actually need a CM 13 rom which provide such performance.(I was thinking about Slim rom 0.4 by Aniket Lamba)
So if anyone can suggest me better rom then please let me know. For me stability & usability matters more than recent builds.
I always will appreciate any information whether good or bad
I used to like KK as it was last in the line of the Holo interface and it was the only 4.x available for our phone, so I used it for fairly long and didn't switch to LP until MM came around. Along with Xcelerate it was really good: decent battery life, smooth experience and fast charging. But now that I've grown to like the Material interface as well, I've been using MM more often these few months, especially Slim6, which I feel gives the same feel I used to get on KK: stability and smoothness.
KK is still one of my more favourite ROMs, but given that KK is mostly dead by now and there are more developments and features in LP and MM, I think I'll just stick to Slim6.
amangupta53 said:
Some of my issues with CM13 based roms which have put me off:
Insane lag when reciving calls
Adopting Storage doesn't work half the time
Front Camera crashes
Mobile Data issues
Lock Screen Wallpaper Issue
Music suspend bug
Battery drain Issue
Click to expand...
Click to collapse
1) I don't get this
2) I don't use Adoptive Storage, heard it screws with WiFi
3) I don't get this (it has been fixed recently)
4) Depends on ROM
5) GravityBox (for AOSP MM), or this guide (which also works on CM13)
6) Disable MPDecision. Strangely when I downgraded to CM11 I was still getting the bug.
7) Depends on ROM
The issues I had with CM11 were generally the use of Apollo and the HDR issue as stated in the post before mine. And the music bug after downgrading. Apart from those I was happy with it, and I wouldn't mind a single bit to change back to it. I just don't understand the hate regarding KK, especially in the MIUI 8 thread...
NightRaven49 said:
I used to like KK as it was last in the line of the Holo interface and it was the only 4.x available for our phone, so I used it for fairly long and didn't switch to LP until MM came around. Along with Xcelerate it was really good: decent battery life, smooth experience and fast charging. But now that I've grown to like the Material interface as well, I've been using MM more often these few months, especially Slim6, which I feel gives the same feel I used to get on KK: stability and smoothness.
KK is still one of my more favourite ROMs, but given that KK is mostly dead by now and there are more developments and features in LP and MM, I think I'll just stick to Slim6.
1) I don't get this
2) I don't use Adoptive Storage, heard it screws with WiFi
3) I don't get this (it has been fixed recently)
4) Depends on ROM
5) GravityBox (for AOSP MM), or this guide (which also works on CM13)
6) Disable MPDecision. Strangely when I downgraded to CM11 I was still getting the bug.
7) Depends on ROM
The issues I had with CM11 were generally the use of Apollo and the HDR issue as stated in the post before mine. And the music bug after downgrading. Apart from those I was happy with it, and I wouldn't mind a single bit to change back to it. I just don't understand the hate regarding KK, especially in the MIUI 8 thread...
Click to expand...
Click to collapse
Hate towards KK is only because most of the apps are working great in >LP than in KK. If MIUI with LP is given then it can be easily a great choice for armani. MIUI ram issues have sorted out but only thing is standby time(wifi on) is low.
NightRaven49 said:
I used to like KK as it was last in the line of the Holo interface and it was the only 4.x available for our phone, so I used it for fairly long and didn't switch to LP until MM came around. Along with Xcelerate it was really good: decent battery life, smooth experience and fast charging. But now that I've grown to like the Material interface as well, I've been using MM more often these few months, especially Slim6, which I feel gives the same feel I used to get on KK: stability and smoothness.
KK is still one of my more favourite ROMs, but given that KK is mostly dead by now and there are more developments and features in LP and MM, I think I'll just stick to Slim6.
1) I don't get this
2) I don't use Adoptive Storage, heard it screws with WiFi
3) I don't get this (it has been fixed recently)
4) Depends on ROM
5) GravityBox (for AOSP MM), or this guide (which also works on CM13)
6) Disable MPDecision. Strangely when I downgraded to CM11 I was still getting the bug.
7) Depends on ROM
The issues I had with CM11 were generally the use of Apollo and the HDR issue as stated in the post before mine. And the music bug after downgrading. Apart from those I was happy with it, and I wouldn't mind a single bit to change back to it. I just don't understand the hate regarding KK, especially in the MIUI 8 thread...
Click to expand...
Click to collapse
The music bug persisting after the downgrade is what's keeping me back. I, too, don't use Adoptive storage for all the bugs it brings - even on AOSP. But this means I'm running out of space by the end of the month because of necessary evils like WhatsCrap.
The gravitybox mod is good to know, although I don't use xposed, but really is simply a hassle to effectively change your wallpaper - especially when I'm changing them every other week.
I've recently tried disabling MPDecision - the music seems to be playing fine but I can't help but notice sightly degraded performance all around.
slst said:
Hate towards KK is only because most of the apps are working great in >LP than in KK.
Click to expand...
Click to collapse
Funny when there was a time when apps couldn't run properly on ART...
amangupta53 said:
I, too, don't use Adoptive storage for all the bugs it brings - even on AOSP. But this means I'm running out of space by the end of the month because of necessary evils like WhatsCrap.
Click to expand...
Click to collapse
Adoptive Storage is a hassle to set up: you need to format your SD card (which meant I had to shift everything out before converting it), and TWRP has no way to read such encrypted storage, so I didn't use it after the first time I tried it. Also you could do with regular housekeeping of your phone's storage; usually I keep WhatsApp images for a year before deleting them (after keeping the important ones and archiving the rest).
amangupta53 said:
The gravitybox mod is good to know, although I don't use xposed, but really is simply a hassle to effectively change your wallpaper - especially when I'm changing them every other week.
Click to expand...
Click to collapse
Xposed is very helpful, but if you don't want to use it then I won't force you.
Generally in those CM12/13 ROMs if I wanted to switch between lockscreen wallpapers I would leave a couple of those wallpapers in the /data/system/users/0 folder, just renamed to let me know which file is which wallpaper. Whenever I wanted to change them I just renamed them to the proper filename.
amangupta53 said:
I've recently tried disabling MPDecision - the music seems to be playing fine but I can't help but notice sightly degraded performance all around.
Click to expand...
Click to collapse
You don't have to leave MPDecision off the whole time: just disable it when listening to music, and re-enable it afterward.
Thank you everyone for your valuable comments:good:. It seems I can finally move on to CM 13:fingers-crossed:.(mostly slim6 version)
Note: I don't have music stop bug in CM11 though( may be related to firmware version or kernel. don't know why different people have different bugs:silly
Dr. Joy Das said:
Thank you everyone for your valuable comments:good:. It seems I can finally move on to CM 13:fingers-crossed:.(mostly slim6 version)
Note: I don't have music stop bug in CM11 though( may be related to firmware version or kernel. don't know why different people have different bugs:silly
Click to expand...
Click to collapse
What I think is that the KK firmware/modem we all flashed for CM13 builds has something to do with the music suspend bug. This is probably the reason why downgrading back to CM11/12.1 doesn't seem to fix this issue.
Anyway, seems like I'll just stick with CM13 for now.
NightRaven49 said:
Funny when there was a time when apps couldn't run properly on ART...
Click to expand...
Click to collapse
Sorry my friend i think its past now.
amangupta53 said:
What I think is that the KK firmware/modem we all flashed for CM13 builds has something to do with the music suspend bug.
Click to expand...
Click to collapse
Well not really, as the same v7.0.5.0 is used for CM11, 12 and early 13 builds. It's most likely a kernel issue, given that disabling MPDecision fixes it somewhat.
slst said:
Sorry my friend i think its past now.
Click to expand...
Click to collapse
I totally didn't know that, like totally dude
/sarcasm