Is the general consensus that Sense roms are general more stable and complete than AOSP roms?
I have tried a few of both, and it seems that every AOSP rom is incomplete.
By incomplete I mean it always seems to:
Reboot for no reason
Not mount the phones internal storage, nor mount the internal storage when connect to the computer (thus assigning it a drive letter)
Random app forcecloses
Now I know you can have problems like this on Sense roms too.
I would like to stay on a AOSP rom, since the ones i have liked have great built in tweaking menus/apps.
Are there any AOSP that dont fall into the above criteria of reboot (especially when using wifi), mounting internal storage on and off the computer (i keep my mp3's and movies on there!), and minor forcecloses?
I have yet to find a single AOSP rom that works like it needs to. So far, for stability sake, stick with a sense rom.
I am in the same boat as you BTW, I have been testing each AOSP (havent been many) hoping, but so far I am still stuck with Sense- which I absolutely cannot stand.
I hear ya
Thanks for the reply. I look forward to an AOSP build too that fits all my needs. I am tired of sense also, and even when I get on a Sense rom, i load up LauncherPro immediately and pretty much dont use much of the sense stuff.
I really liked the Ruby and Shadowrom, but i had freezes, reboots, and not internel storage mounting of course. I tried different kernels, tweaking, wiping, praying, beer drinking, and even subjected myself to watching a chick flick with my Fiancée, and still no luck (at least with the roms).
I keep a sharp eye out on the Development forums daily, hoping to pounce on the next AOSP rom that does everything (tethering, storage mounting, wifi without reboots, to name a few) that roms like Skyraider and Virtuous (sorry if i didnt name someones), and still has that great AOSP rom ability to configure and tweak to my hearts end.
dccoh said:
Is the general consensus that Sense roms are general more stable and complete than AOSP roms?
I have tried a few of both, and it seems that every AOSP rom is incomplete.
By incomplete I mean it always seems to:
Reboot for no reason
Not mount the phones internal storage, nor mount the internal storage when connect to the computer (thus assigning it a drive letter)
Random app forcecloses
Now I know you can have problems like this on Sense roms too.
I would like to stay on a AOSP rom, since the ones i have liked have great built in tweaking menus/apps.
Are there any AOSP that dont fall into the above criteria of reboot (especially when using wifi), mounting internal storage on and off the computer (i keep my mp3's and movies on there!), and minor forcecloses?
Click to expand...
Click to collapse
From my experience CM6 has none of those issues
Internal memory mounts it just doesnt display it in settings
And when I connect it to my computer I get both internal and external storages on my computer so I can access them both
I haven't had a random reboot untill I flash a custom kernal or if I overclock the original so I suggest don't overclock
But I still have the stupid email fc at startup but that's it
Sent from my ADR6300 using XDA App
Which build?
Really? May I ask which build or nightly build you are using? And which kernel with CM was giving you fc's? Thanks alot for the info too.
dccoh said:
Really? May I ask which build or nightly build you are using? And which kernel with CM was giving you fc's? Thanks alot for the info too.
Click to expand...
Click to collapse
I've been using all the nightlies from the 19th on up in order
I use the standard kernel that comes with each build
Every one so far gives me the email fc
Sent from my ADR6300 using XDA App
I currently run CM 6.0.2 with King's aosp kernel.
Internal storage is available when plugged into PC, doesn't show up (as has been stated.)
Rarely used Wifi anyway because I've got an unlimited data package, and can do my high-speed downloading on my laptop. Haven't even tried to use it since I've flashed, actually.
Had one random reboot when I setCPU to 1190mhz, oops. I remember my battery being excessively hot, as well. Since I generally run it at 768mhz, that doesn't bother me.
But why underclock my Incredible? Well, if I plan on doing something processor intensive, I'll crank it back up. If I use it for standard web browsing, video playback, etc, can barely tell the difference, and I unplug at 7:30am at 100% and get home from work at 5:30 at 70% on stock battery.
And honestly, the first ROM I flashed was CM6 RC3, and I swore to myself I'd never use it again, because it wasn't Sense.
You'll find the AOSP you like, it'll just take a few flashes. Besides, the developers aren't very possessive of their awesome accomplishments, that's why we get to use them.
For stability, Sense always wins...
But performance, which i personally care more about, AOSP roms are much better.
I'm running CM6 6.0.2 w/ King's Kernel, and all has been good. Just the battery life isn't so great, and bluetooth is kinda gimped. Aside from that, everything works, and i get no more random reboots.
I just wanted to revisit this topic because I typed in AOSP vs. Sense in google, and this was a result. Cyanogen Mod 6.1 final is damn near bullet proof and with the right research/widgets/kernel/etc can stomp just about anything.
Cyanogenmod should deliver great battery life as well as performance. Either 6 or 7 would produce great results
I'm on CM7 now and it's running GREAT.... no FCs or anything
So I'm pretty new, well very new, to the custom rom/kernel/recovery/etc game since my last phone was a POS and there was no point trying to make it do anything special, but ever since I got my S III, I've been trying to learn everything about how it all works. I have a Galaxy Tab and put a custom ROM on it a long time back, but I was never all that crazy about the latest and greatest till this phone came along. Considering it's my sole source of communication, I obviously need it to be functional, but there's a side of me that says it would be very hard to truly brick this phone (and please don't correct me if I'm wrong :cyclops: ) Anyway, I've played around with a few ROMs out there and am currently running the latest Crimson build which I love so far. I have a couple questions for those educated in all of this. First, and probably simplest, I've noticed that after flashing a new ROM and signing in to my Google account, apps I've acquired from the market sometimes download and install right away and sometimes don't. Is this just a somewhat-random phenomenon or is it within my control? I always use the same settings (sync automatically, keep this device backed up, etc) but they don't always have the same effect and I'm curious about it. Second, what do you guys recommend in the way of backing up apps? Not program-wise, but theory-wise...I make Nandroid backups whenever I make a major change and occasionally make individual app backups with ROM Toolbox Pro, but I use Nova launcher and it seems that a simple backup of my desktop layout is enough to get back my original look with the new ROM (and then I just let the apps download from the market). Is there an even better way to do this that I'm unaware of? I know that backing up apps has the added benefit of backing up data as well, but in my experience, restoring both app and data to a new ROM seems to have adverse effects...I inevitably have to uninstall and re-download the app. Maybe I'm doing something wrong but, again, I'm new to this. My last and most important question is regarding something I read about custom kernels only being usable with the UVALEM baseband. I don't know anything about phone modems but heard some people were getting better speeds with UVALH3 so I decided to flash it. This may have been a convenient coincidence but I'd never before observed speeds above 7-ish Mbps (my area has pretty lousy 4g coverage) and my first speed test gave me 12. I'm a little confused because everything has suggested custom kernels are NOT COMPATIBLE (always emphasized, too) with any other baseband yet I have an overclocked custom kernel with the aforementioned radio and have had no problems. Have I missed something or is something unusual happening? Thanks in advance, and sorry for the long post!
tonesofheresy said:
So I'm pretty new, well very new, to the custom rom/kernel/recovery/etc game since my last phone was a POS and there was no point trying to make it do anything special, but ever since I got my S III, I've been trying to learn everything about how it all works. I have a Galaxy Tab and put a custom ROM on it a long time back, but I was never all that crazy about the latest and greatest till this phone came along. Considering it's my sole source of communication, I obviously need it to be functional, but there's a side of me that says it would be very hard to truly brick this phone (and please don't correct me if I'm wrong :cyclops: ) Anyway, I've played around with a few ROMs out there and am currently running the latest Crimson build which I love so far. I have a couple questions for those educated in all of this. First, and probably simplest, I've noticed that after flashing a new ROM and signing in to my Google account, apps I've acquired from the market sometimes download and install right away and sometimes don't. Is this just a somewhat-random phenomenon or is it within my control? I always use the same settings (sync automatically, keep this device backed up, etc) but they don't always have the same effect and I'm curious about it. Second, what do you guys recommend in the way of backing up apps? Not program-wise, but theory-wise...I make Nandroid backups whenever I make a major change and occasionally make individual app backups with ROM Toolbox Pro, but I use Nova launcher and it seems that a simple backup of my desktop layout is enough to get back my original look with the new ROM (and then I just let the apps download from the market). Is there an even better way to do this that I'm unaware of? I know that backing up apps has the added benefit of backing up data as well, but in my experience, restoring both app and data to a new ROM seems to have adverse effects...I inevitably have to uninstall and re-download the app. Maybe I'm doing something wrong but, again, I'm new to this. My last and most important question is regarding something I read about custom kernels only being usable with the UVALEM baseband. I don't know anything about phone modems but heard some people were getting better speeds with UVALH3 so I decided to flash it. This may have been a convenient coincidence but I'd never before observed speeds above 7-ish Mbps (my area has pretty lousy 4g coverage) and my first speed test gave me 12. I'm a little confused because everything has suggested custom kernels are NOT COMPATIBLE (always emphasized, too) with any other baseband yet I have an overclocked custom kernel with the aforementioned radio and have had no problems. Have I missed something or is something unusual happening? Thanks in advance, and sorry for the long post!
Click to expand...
Click to collapse
1. As for apps downloading automatically from google; when you first set up your account again after flashing, there is an option asking you whether or not you want to back up and restore apps to google. If you check the restore option, it will download the apps that you already own that's been backed up. I usually just back up and restore my apps using TitaniumBackup so I always leave this option unchecked.
2. When I back up my apps using TiBa, I don't bother backing up the data. I just back up the apps, and then restore just the apps. All the apps data will have been saved and will be reloaded when you restore them. I've never used ROM Toolbox Pro so I can't say if it works the same with it.
3. People get different speed with the different radios. You just have to try the different radios and see which one works best for you.
4. I'm not really sure about the Kernel, but when I flash a radio, as long as it's OS and Carrier compatible, I just flash away. When I say OS compatible, I meant that I wouldn't flash JellyBean radio on a ICS ROM. Not sure if that would work, but I've never tried it. When I say carrier compatible, I wouldn't flash AT&T radio on T-Mobile phones.
I hope I've helped a little bit.
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
Hey guys how are you doing?
I don't know if this is supposed to be normal but my Nexus is becoming really slow. I've compared it with my father's Samsung Galaxy Gio (yes, that damn piece of brick) running a port of CM10 called Xperia Jelly Bean with an overclock to 1GHz (without messing with the low freqs) and my Nexus running CM11 was slower in terms of opening the SMS app, the contacts, the settings and so on.
I've tried everything, wiping every partition in the phone and installing many roms (CM12, fresh's AOSP Lollipop, CM11, Vanir, LiquidSmooth, CarbonRom, SlimRom, etc) and I even tried different kernels (DirtyV, Fancy and Franco for KK roms and BSmitty's kernel for L) but my perfomance goes from bad to even worse.
Most roms come with many apps I don't use like apollo, stock camera, stock messaging, aosp email app, lancher3 or trebuchet (I like google now but I tested not changing the launcher and it's about the same performance) and the default browser app, so I usually delete them with titanium backup.
I heard some weird sounds when I was with lollipop roms that worried me since I've never heard those sounds (looked like something tiny blowing up) so I am a little worried that those things caused some hardware to start malfunctioning or even stopped working. I am also having now troube with flashing a rom and it being stable. I usually wipe all the partitions, install ROM then Gapps (the most minimal ones) and then Kernel, wipe Cache again, reboot. Set everything (Gmail account and custom rom things like notification bar, locksreen, etc), reinstall the apps I need from google play, change to ART if needed/avaiable and go on. But sometime later the phone starts freezing and ends up turning off and when it turns on it stucks on the boot so I need to reinstall the rom.
What am I doing wrong? What can cause my device to behave like this? Is it a likely end of my device? I am worried and have little knowledge xd. Should I flash a stock rom? Which version is the more appropriate? What do you recommend for custom ROM, am I flashing them and applying everything alright?
EDIT: I forgot to mention that I did some benchmark tests and it does well as espected. Goes up to 20K with Lollipop, 15K with KitKat (1.5GHz) and 13-14K with KitKat (1.2GHz). I've tested it in FML 5.0.2 (last build) + Bsmitty kernel (about 2 weeks ago) and the KK ones I did yesterday with CM11 and fancy r60. The problem here is the menus that are freezing constantly and the basic apps that take too much time to load when compared to the time I bought it (I'm talking about Settings, Camera, Messaging, Dialer, Contacts, etc)
I feel the same way about my phone too! Btw, is installing new app on your phone slow? My phone takes about 15-20 secs to install an app.
I am by no means an expert, but the "weird sounds / stability of ROM flashing / constant freezing" that you're reporting, regardless of the ROMs that you're using, it sounds like your device may be on its last legs. How long have you had the device? Is it possible that some of your hardware components are failing?
In my own Gnex experience, I was using CM11 Snapshot ROMs for about a year. About 6 months after installing CM11, I started noticing massive slowdown and lagging. Similar to what you reported: slow launching of apps (even simple ones like the default SMS Messaging and Camera), freezing/crashing in Gmail and Chrome, very slow multitasking/tab/app switching, etc.
Google officially stopped supporting the Gnex at 4.3 so I would recommend that you try returning to the 4.3 Stock Nexus Image, and see if that improves your stability. I did that for my Gnex and installed the Xposed framework on top, and I've been happy with the results. I no longer use my Gnex as my daily phone so I can't speak to longer-term usage, but you may want to try this first before writing the device off entirely.
Well, after some time I finnaly put my phone working nicely again
I flashed and tried over and over again many combinations of rom, gapps and kernel until my phone worked nicely with something. I am with CM11 + PA Stock Gapps (with gapps-config.txt written of my own to avoid installing things I consider bloat) + Fancy Kernel (everything in their respective last versions).
Well, just an advice from me to anyone who starts having problems like me. If you are flashing much and testing many roms per day and your phone starts getting slow and not booting like it should boot (and having weird sounds) just stop for a while. Find a stable rom+kernel combination and let the phone work like that for some time. Then when you think you are ok, start flashing to your content again