First off, let me start by saying I know this thread probably should be under the 3.99 RC2 Paranoid Android Captivate development thread, but I haven't made 10 posts yet (any question I've ever had has been asked already and every bit of advice I've ever had has been given already).
Now, I was running PA 2.54 for Samsung Captivate. I just upgraded to the 3.99 RC2 last night, and I'm befuddled. What happened to all of the features? The settings are not as in depth and customizable as they once were. The three major qualms I have are the absence of the slide to unlock shortcuts on the lockscreen (or whatever they're called, and I'm talking about the shortcuts that you were able to place on the lock ring), the inability to edit the functions of the four hardware keys (you're able to edit the home and menu keys, but not the search key, which I really enjoyed), and the lack of performance options in the settings menu. Why are these missing? I understand this is a release candidate I'm running, but that has nothing to do with the absence of these features. It just seems odd to me that I upgraded my version of PA, and now these key features that sold me on said rom are missing. Does anybody have any input or explanations?
FYI I'm running NOVA launcher, not Trebuchet (which came as the default launcher on PA 2.54), but I can't see how this has anything to do with my problem(s).
Any input would be greatly appreciated! And I apologize again if this is in the wrong area of the forum! Thanks a lot!
I haven't tested the latest ported PA, but in my experience light AOSP ROMs run much better on Captivate. The hardware is just too limited to handle all full-featured ROMs bells and whistles and offer smooth UI in the same time. If you want to see/test all custom ROM features without changing ROMs often, then try PAC-ROM. It's an All-in-One package with features from CM, AOKP and PA.
Well, PA runs smoothly on my Captivate, but I get where you're coming from. I actually flashed PAC Rom for a day, but switched back because it wouldn't run smoothly at all. By far the choppiest performance I've ever seen from a ROM, even though I love the idea of it. I'm now running Dirty Unicorns, which has all of the features I want, since, like PAC Rom, it uses features from PA, AOKP, and CM, but it is much less resource intensive.
Related
Well I want to start off by saying that I've rooted my N1 and tried several cooked roms including CM's and the Modaco version. I keep searching for a reason to use a custom rom. Every time I do, I end up reverting back to stock. I just don't get the purpose. I understand cooking Windows Mobile roms to get newer OS versions that included new features and stuff, and cooking in new updated apps... I've searched and searched looking for some solid reason to stay on a custom rom, but I can't find one.
The Nexus One is just awesome and pretty clean as it is out of the box. It seems like when I use a cooked rom, it's more bloated then stock and I "try" to make it work as my stock rom did, with same apps and homescreen setup (I like Launcher Pro/Dialer One). I know some of the roms include "newer kernels" which I'm guessing is like a newer build but I don't see anything really that "pops" out. I understand rooting the device to gain full access to the system. But you can root a stock rom.
I also understand porting different systems like Desire/Hero/whatever. But aside from cosmetics, rooting, overclocking, and undervolting... why use a custom roms?
And mods, I've searched and searched, and read and read, I've seen the stickies. I'm looking for specifics.
player911 said:
aside from cosmetics, rooting, overclocking, and undervolting... why use a custom roms?.
Click to expand...
Click to collapse
I think you summed it up pretty well. cosmetics, rooting, overclocking, and undervolting.
For me, custom roms is worth it JUST for trackball wake up, and unlock, on the nexus. I hated having to use the power button way at the top.
For some, its so you can use an entirely open source phone, free from proprietary google apps.
The great chefs put a ton of thought into all the additions they use, create, and implement. Things that save battery life, improve user experience, or fix bugs / quirks.
There isn't a huge demand for ROM's for the N1 because we're at the forefront of Android right now. We're the one's with 2.2. We have flash. Everyone else is getting ports of what we get stock. This will continue for the foreseeable future, until Google selects another handset to be its in-house testing model, or launches Nexus Two/Dev Phone 4 (counting N1 as 3). Once we're obsolete, then, and only then, will you see the modding community pick up and you'll see big reasons to go with custom ROM's.
CM has the latest android code that is publically availalble. (He just synced code today). The little features that are missing are enough for me. Things like invisible lock screen, to the newly added gestures in the music app(great for driving).
If you're not a tweaker by nature then stock OS code will suffice. Me? I can't get enough of the new little things that add up to an overall great package.
/cm nutriding
Because it's fun.
720p recording.
http://forum.xda-developers.com/showthread.php?t=698287
Titanium Backup and N1 Torch
ATnTdude said:
There isn't a huge demand for ROM's for the N1 because we're at the forefront of Android right now. We're the one's with 2.2. We have flash. Everyone else is getting ports of what we get stock. This will continue for the foreseeable future, until Google selects another handset to be its in-house testing model, or launches Nexus Two/Dev Phone 4 (counting N1 as 3). Once we're obsolete, then, and only then, will you see the modding community pick up and you'll see big reasons to go with custom ROM's.
Click to expand...
Click to collapse
Yea that makes sense.
I just feel that custom roms are more bloated then stock. I've been looking into trying one of the "Super Clean OC/UV Rooted" roms. But then again I think the stock OS is just the Bee's Knee's.
What is "bloated"?
There are zillions of reasons for custom ROMs, visual and functional:
Apps2SD
USB and WiFi tethering
Locales
OpenVPN
Dropbear, Bash, etc (better Linux experience)
Trackball colors, notifications
Torch (using flash LED as flashlight)
Deep system options made visible / changeable, lots of customization options
Most of Froyo features were implemented in custom ROMs way before Froyo test build.
My setup is VERY far from stock. And I use everything mentioned above. I can't even move to Froyo, because I need Apps2SD to work - overloaded with big apps.
I think that's a great reason..
player911 said:
Yea that makes sense.
I just feel that custom roms are more bloated then stock. I've been looking into trying one of the "Super Clean OC/UV Rooted" roms. But then again I think the stock OS is just the Bee's Knee's.
Click to expand...
Click to collapse
No reason why you can't use Cyanogen's Quick Root + Pershoot's OC/UV Kernel on FroYo to benefit from rcxquake's wonderful modded Flash .apk and watch Hulu. It's obviously not quite as complete as CM 5.0.x (desperately missing trackball wake), and despite having root for some reason I still can't rm -f and pm uninstall com.amazon.mp3.apk from adb shell, but it gets almost everything done for me. The main thing that made FroYo live-able for me was the addition of ogdobber's Black Bar, which I had gotten very used to on CM5. That said, I can't wait for a CM flavor of FroYo...
willverduzco said:
No reason why you can't use Cyanogen's Quick Root + Pershoot's OC/UV Kernel on FroYo to benefit from rcxquake's wonderful modded Flash .apk and watch Hulu. It's obviously not quite as complete as CM 5.0.x (desperately missing trackball wake), and despite having root for some reason I still can't rm -f and pm uninstall com.amazon.mp3.apk from adb shell, but it gets almost everything done for me. The main thing that made FroYo live-able for me was the addition of ogdobber's Black Bar, which I had gotten very used to on CM5. That said, I can't wait for a CM flavor of FroYo...
Click to expand...
Click to collapse
Have you tried "adb remount" to remount the System partition in read/write mode first?
I'm sure I'm setting myself up here, but what advantages are there to the custom ROMs at this point?
I'm running stock Froyo 2.2 (I did update the radio to 5.08, though), stock bootloader, and I'm not rooted. I'm on T-Mobile in the Tampa, FL area.
I'm not sure if it's a coincidence, or just because most people that are posting on XDA are running custom ROMs, but I don't really have ANY of the problems most people on here have. My battery life is great, and the phone is overall VERY stable. I've tried other launchers, themes, etc., but I always prefer the stability of the stock setup over aesthetics.
The few issues I have had I can attribute to poorly written apps (force closes, battery vampires), or known hardware problems (mediocre 3G connectivity at times, etc).
I can understand if you have a phone like the MyTouch that never got any official updates after 1.6, or you want to try the next leaked software on your phone. But the Nexus One has had tons of official support and updates up to this point. Before Froyo was officially released, I found myself better off with stock recovery to load the latest, greatest Froyo build.
Sorry for the rambling, but I would greatly appreciate any education I can get on what's packed into these custom ROMs that everyone gets so excited about.
THANKS!
Don't really feel like typing all the reasons haha, but there's a lot of stuff to enjoy with custom roms. If stock works for you that's great. I don't know anyone that's ever gone custom and wanted to go back but I'm sure it happens. End of the day it's whatever makes you happy. A lot of us want more than just a great experience, we want to see what's possible. You can view the changelog for the latest Cyanogenmod(most popular custom ROM) build here http://github.com/CyanogenMod/android_vendor_cyanogen/blob/froyo/CHANGELOG.mkdn
1. More control over the appearance of the OS. Get rid of that ugly white notification bar and replace it with a sexy black one, for example.
2. Removing the stock apps from the phone that you don't use or want. Why have them sitting there taking up space and potentially resources for no reason? Sure they don't take up much in terms of storage space, but if you use a lot of apps, every little bit counts.
3. Undervolting and over/underclocking. Get that extra little performance boost, or cut it back. When I was UV'd to 800mV and UC'd to 806mhz, I noticed no performance difference or problems (note: I don't play 3d games on my phone) and my battery life was insane. 24 hours of normal use would put me to 65% give or take.
4. Relating to number one, more control over other things. I've ripped stock, but customized, apps from random ROMs and pushed them to my phone. Black Facebook & Twitter widgets (white ones are ugly), darkened (black & dark grey) stock messaging interface with white text, etc.
5. Trackball Alert Pro.
I'm sure that others can add more, but the above are the main reasons I rooted mine.
A tiny little thing called Apps2SD+, for example.
Multiple audio/video decoder support.
Lots of Linux binaries bundled.
Lots of modifications to stock software (contacts, browser) that increase their usefulness (for example, do you really like to type "about:debug" each time you want to change browser client after reboot?).
etc etc.
Thanks for all the great info.
The underclocking sounds interesting. I don't play any games on my phone, and extra battery life is always nice.
I'm not too interested in customizing the appearance too much. Coming from an iPhone, I'm pretty happy with the looks of the stock Froyo UI compared to that.
Again, thanks for the time you guys took to give me some information. I greatly appreciate it!
Sent from my Nexus One using XDA App
Ryjabo said:
1. More control over the appearance of the OS. Get rid of that ugly white notification bar and replace it with a sexy black one, for example.
...
5. Trackball Alert Pro.
Click to expand...
Click to collapse
This was reason #1 and 2, 3, 4, 5, 6, 7 for me, respectively
Track ball skip song.. Enough said.
If I install a custom ROM, when a new one comes out, do I have to install the ROM from the start and I loose my setings etc. or do I just update it?
Depends on the ROM maker. Most make their ROMs backwards-compatible, so you can upgrade. Going between different makers' ROMs you mostly need to wipe and start fresh (though there are apps that can back up and restore pretty much everything).
I am thinking to try Cyanogenmod ROM, bot I don't wan't to cofigurate all the things when a new ROM comes out.
Here's what I'm running:
* BootLoader - 1.1 branch
* ROM - VEGAn-7.0.0-RC1-Harmony
* Kernel - 2.6.32.36-cyanogenmod [email protected] #1
* Gingerbread 2.3.3
I downloaded and installed the APK from here
http://forum.xda-developers.com/showthread.php?t=750765
It runs (ie - doesn't FC), but I have no control of the EQ settings - the faders don't move when I drag. Other versions that I have tried FC.
Am I missing something simple stupid?
ETA:
You guys Fk'n rock. I helped my boss root his Kindle Fire with CM7. He bought it with the sole intent of turning it into a 7" Android tablet. Everything we needed (directions wise) was right here. If there was a button to thank all the contributors at once, I would hit it. Thanks!!!!
Yes, DSPManager is just the app "control" interface. It ties in to a lot of code/source that is implemented in other aspects of the ROM when building a ROM from source (adding the needed libraries, making edits to other files, etc..).
The app does nothing without the supporting code compiled in to the ROM as well.
That's what I was finding while doing more searching after I posted. It appears that my ROM does not support the DSP stuff.
The bass response is horrible (as in almost not there) and the overall max volume output is super low.
What's a good ROM that does support DSPManager? (and do I need to wipe the device or can I simply lay the new ROM over top of the old one?)
THANKS!!!!
I don't know of any ROMs for the Gtablet that support DSPManager.
It's a CyanogenMod feature coded in to their source and even they don't support it on the Gtablet.
Well crap
Thanks anyway.
A Few of them do, Falashback and Gtabcomb are 2 that I know for sure work and some others as well but yeah no go with Cyanogen. If you must use a rom that DSPmanager doesnt work with, you could try Volume+. Now dont hold me to that because you may have the same issue with that app but Im not quite sure.
As far as Im concerned, a sound enhancing app is an ABSOLUTE MUST if you own a Gtab so that comess first. Thats is indeed one of the major reasons I dont use CM but like I said I never tried to see if volume+ works so see whats up with that., If not Id jump right over to one of the HC roms. They might not be as fast as CM aand others but they are very much stable enough to use as an every day driver.
Hope this helps.
p.s. looks like ICS is getting closer and closer sso hopefully we dont need either!!
Sent from my gTablet using XDA Premium App
i only have my note for a month or so, i did a bit of research on roms, bur comparing to my old p990 the number of roms for n7000 is really massive
already checked number of sites as well i.e. http://www.galaxynoteroms.com/ but can't find rom that is right for me
basically i want stock based rom (with working pen, hdmi, fm radio) but tweaked so it is smoother (and preferably without that annoying 1,5 second lag after home button is pressed) i don't need any additional eye candy, disabled camera sounds and enabled call recording would be nice extras but i guess i could find ways to do it separately
which rom can you recommend to start my search?
Thread closed as its a best ROM thread.
After playing around with CM10, 11, and now Mokee44, I'm looking at which is the most responsive version for my HD. My use is mostly to read books, with some web browsing. I like to the look and feel of Mokee, but sometimes things feel like running through molassess.
I updated due to the lack of any new fixes, security or improvements on the older versions, not really due to any new feature add.
What is the general recommendation on the best, most responsive OS version I should be running?
sangahm said:
... sometimes things feel like running through molassess.
Click to expand...
Click to collapse
Isn't that just the nature of the beast?
As only my luck would have it, I dropped my coffee mug on my beloved TAB PRO and shattered the screen. I dug out the ol' HD+ to use while I was waiting for parts. I quickly remembered what I didn't like about it. But I still have it and still appreciate the big, beautiful display. The best performance I could squeeze out of it was with CM12 de-bloated to the absolute bare bones and any and all animations turned off. It felt better, but still suffered form random reboots.
I'll be watching, though. I hope you find a better answer.
My husband has been running CM 12.1 for awhile now on his HD (that's the final version of CM 12.1 found in @amaces "obsolete" folder). We had some trouble at one point but it was due to an improperly prepared SD card used for the flashing (my fault...). He's never had any issues with that ROM other than the well-known shut-down issue (I don't think he could be retrained at this point to do anything BUT hold in the power button until the screen goes black!). No unexpected closures or shut-downs. We had one frightening episode of screen blinking but that turned out to be an app update that didn't like the OS, so we figured that out eventually.
I've configured a version of CM 13 for him on a "new" HD. The only issue I've had with it so far is Trebuchet acting squirrely when trying to move/delete home screen icons. I finally just installed Nova Launcher to have done with it. No Wi-Fi issues as seems to be common with Marshmallow ROMs.
I have to say both of these ROMs run pretty well. They don't seem sluggish. Maybe that's because I'm so used to my Nook Tablet which, for all its virtues, is certainly a little slower than the HD (though still very useful). Still, no one would confuse these devices for a brand new "X".
I'd certainly give at least the CM 12.1 a try. We've also run CM 11 before it and there is not much difference except for gaining access to additional apps that would not run under CM 11.
nmyshkin said:
My husband has been running CM 12.1 for awhile now on his HD (that's the final version of CM 12.1 found in @amaces "obsolete" folder). We had some trouble at one point but it was due to an improperly prepared SD card used for the flashing (my fault...). He's never had any issues with that ROM other than the well-known shut-down issue (I don't think he could be retrained at this point to do anything BUT hold in the power button until the screen goes black!). No unexpected closures or shut-downs. We had one frightening episode of screen blinking but that turned out to be an app update that didn't like the OS, so we figured that out eventually.
I've configured a version of CM 13 for him on a "new" HD. The only issue I've had with it so far is Trebuchet acting squirrely when trying to move/delete home screen icons. I finally just installed Nova Launcher to have done with it. No Wi-Fi issues as seems to be common with Marshmallow ROMs.
I have to say both of these ROMs run pretty well. They don't seem sluggish. Maybe that's because I'm so used to my Nook Tablet which, for all its virtues, is certainly a little slower than the HD (though still very useful). Still, no one would confuse these devices for a brand new "X".
I'd certainly give at least the CM 12.1 a try. We've also run CM 11 before it and there is not much difference except for gaining access to additional apps that would not run under CM 11.
Click to expand...
Click to collapse
Thanks, I'll try that one.
Do you have a link for amaces downloads, or the thread for them?
sangahm said:
Thanks, I'll try that one.
Do you have a link for amaces downloads, or the thread for them?
Click to expand...
Click to collapse
The CM 12.1 for hummingbird can be found at https://notredame.app.box.com/s/26a...e&sortDirection=desc&pageSize=20&pageNumber=5
You want the one dated 20151018. That's his final version.
The CM 13 ROM I am currently configuring is at https://notredame.app.box.com/s/26a...e&sortDirection=desc&pageSize=20&pageNumber=4
It's the one dated [20]160129. There may be better-behaved alternatives but I chose this one because we want working HDMI and it seems to be the last one with that functionality.
Edit: Whoops! Almost forgot that you also need to flash SuperSU_v.2.46.zip to enable full root for either ROM.
I know this thread is a bit old, but I would recommend the AOSP 6 version of this ROM with nano gapps. ( https://builds.unlegacy-android.org ) Even though the 7.1 builds are fine, they're just a bit more buggy than Android 6. There are still weekly updates and the performance and battery have been great for me. I'm not running it without root so I can't comment on that. I also don't know about HDMI functionality.
eyzakfunk said:
I know this thread is a bit old, but I would recommend the AOSP 6 version of this ROM with nano gapps. ( https://builds.unlegacy-android.org ) Even though the 7.1 builds are fine, they're just a bit more buggy than Android 6. There are still weekly updates and the performance and battery have been great for me. I'm not running it with root so I can't comment on that. I also don't know about HDMI functionality.
Click to expand...
Click to collapse
Wow! What a potential treasure trove. We're really happy with the CM 13 ROM I referenced above, but I'm going to take a look at the AOSP 6 ROMs and check out the HDMI--not to mention the shut-down issue.
I see a slew of 7.1 ROMs for acclaim!!!
Do we know who the developer is?
nmyshkin said:
Wow! What a potential treasure trove. We're really happy with the CM 13 ROM I referenced above, but I'm going to take a look at the AOSP 6 ROMs and check out the HDMI--not to mention the shut-down issue.
I see a slew of 7.1 ROMs for acclaim!!!
Do we know who the developer is?
Click to expand...
Click to collapse
I believe it's amaces. Same dev as the CM builds, but the Unlegacy Project is definitely smoother than the AOSP builds he posts. And no shut off issue for me, only a problem with auto rotate sometimes not working. That's easily fixed with a reboot though.
nmyshkin said:
The CM 12.1 for hummingbird can be found at https://notredame.app.box.com/s/26a...e&sortDirection=desc&pageSize=20&pageNumber=5
You want the one dated 20151018. That's his final version.
The CM 13 ROM I am currently configuring is at https://notredame.app.box.com/s/26a...e&sortDirection=desc&pageSize=20&pageNumber=4
It's the one dated [20]160129. There may be better-behaved alternatives but I chose this one because we want working HDMI and it seems to be the last one with that functionality.
Edit: Whoops! Almost forgot that you also need to flash SuperSU_v.2.46.zip to enable full root for either ROM.
Click to expand...
Click to collapse
Those ROMs you don't need to flash ROOT. You enable that by Settings -----> Android Debug (or something like that)
secretwolf98 said:
Those ROMs you don't need to flash ROOT. You enable that by Settings -----> Android Debug (or something like that)
Click to expand...
Click to collapse
It may be. I've got the SU zip on the SD card I used to flash both ROMs so I assume I used it. Been flashing a lot of ROMs lately. They all run together after awhile!
nmyshkin said:
It may be. I've got the SU zip on the SD card I used to flash both ROMs so I assume I used it. Been flashing a lot of ROMs lately. They all run together after awhile!
Click to expand...
Click to collapse
What ROM do you recommend for hummingbird? I don't use HDMI and I don't use it for reading.
secretwolf98 said:
What ROM do you recommend for hummingbird? I don't use HDMI and I don't use it for reading.
Click to expand...
Click to collapse
I'm probably not the best person to ask. It's my husband with the HD and he mainly uses it for video (Kodi, MX Player), some browsing, and comics (Perfect Viewer). The HDMI is really important to him so that's the first filter in choosing a ROM. He also has a low tolerance for bugs. The shut-down issue is about all he can deal with. For him, the CM 13 ROM is just about perfect. When I was setting it up I was also impressed, once I replaced the launcher.
But there's been a lot of work done since CM 13 so......
nmyshkin said:
I'm probably not the best person to ask. It's my husband with the HD and he mainly uses it for video (Kodi, MX Player), some browsing, and comics (Perfect Viewer). The HDMI is really important to him so that's the first filter in choosing a ROM. He also has a low tolerance for bugs. The shut-down issue is about all he can deal with. For him, the CM 13 ROM is just about perfect. When I was setting it up I was also impressed, once I replaced the launcher.
But there's been a lot of work done since CM 13 so......
Click to expand...
Click to collapse
If we could get the right side up screen and latest LineageOS 13 with everything working, I would be so happy and I would use that. That concludes the shut down bug, and battery eating really fast. I also don't like lag. I do video games, so that won't work well with the lag.
I think I installed the unlegacy 6.0.1 ovation for my hd+ but my video playback is very stuttering with audio on the default gallery app. I installed dolphin and tried youtube and the video/audio sutters alot. Anyone have this problem? It is very responsive and reading books is great but this media playback problem is an issue as the screen to too beautiful for just reading documents. I did search and notice one person or twohaving this problem but I'll ask anyway cause that was a few years ago and I can't seem to narrow down a solution if there is any. It's a new install with just 3 apps running.