Related
The Motorola Droid X Froyo Release is apparently fraught with errors. Everything from random reboots, to file corruption, and flaky wireless.
So... for once I'm glad Samsung isn't releasing their OTA. Maybe we get lucky and avoid all that BS?
My froyo works fine
Sent from my SAMSUNG-SGH-I897 using XDA App
We already have froyo.
Sent from my SAMSUNG-SGH-I897 using XDA App
dewt said:
We already have froyo.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Only the leaked version..
Sent from my SAMSUNG-SGH-I897 using XDA App
Our leaked version of Froyo is no better. It is full of bugs as well. The biggest issue would be can't reply emails with original message included. And I found the Gallery app is incredibly buggy dealing with photos. It often forgets that it has created thumbnail files for the photos and keep treating the thumbnail files as new photos. As a result, the number of photos keeps multiplying. I had about 20 photos on my external SD card and the highest number of photos shows up in Gallery app is 200.
... I'm talking OTA not the leaked version.
And so far I'm not having the issues you have with Gallery or Email. I take it you started from scratch (wiped it clean) and didnt attempt to restore any data with tibu?
avgjoegeek said:
... I'm talking OTA not the leaked version.
And so far I'm not having the issues you have with Gallery or Email. I take it you started from scratch (wiped it clean) and didnt attempt to restore any data with tibu?
Click to expand...
Click to collapse
Never used tbiu. I always starts clean. The email bug is well documented. Maybe it only shows up when you use Exchange email. But that's what a lot ppl use for email these days.
There is no guarantee that the final release will be any better. It's software and there will always be bugs. The i9000 Froyo has been finalized and leaked out. Our JI6 was built around 9/20 or so. Critical bugs like this show up this late is not a good sign. Either we have to wait until Dec. to get the Froyo or it will be released this month with these bugs in them.
avgjoegeek said:
The Motorola Droid X Froyo Release is apparently fraught with errors. Everything from random reboots, to file corruption, and flaky wireless.
So... for once I'm glad Samsung isn't releasing their OTA. Maybe we get lucky and avoid all that BS?
Click to expand...
Click to collapse
These people are having problems with the official Froyo release on the Droid X. We will probably have some problems too. The current Froyo for captivate has always been considered a pre-release Beta, so adopting early will get you some bugs - but there is no guarantee the final build will be better.
I think the known bugs (like email reply and contact groups) will be easily fixed before the final release - but I am sure we will find others.
HoustonHeart at the VZW forum says:
"I've tested the official builds (not leaked) and it is past 1Y and already on the EP2X build which are pretty final. Probably still Early fall however till it offcially goes out to everyone.
Yes it performs better the device was made for it. Yes it*fixes major issues. Yes 4g (thank God) is stable. The official still has bloatware even if not as much. Verizon needs to remove that garbage and leave it an option. P.S> Netflix also performs better. As well as camera use."
http://community.vzw.com/t5/DROID-Charge-by-Samsung/EP1W/td-p/659935/page/2
Can anyone verify the claim that other offical Gingerbread builds are being tested? Is this why an OTA is not being released yet?
Sent from my SCH-I510 using xda premium
There were simultaneous EP1? and EP2? builds being put out from Samsung. For all we know EP2X is the same as EP1W. The two different things were just built in different locations.
Hi Guys,
I'm very new to this scene and have already started experimenting with ROMS (running Leedroid at the moment). I've just had a quick play with Coldblooded CM10 and love it but I'm intrigued about the current 'broken list'.
Is this just the way it goes with ROM Development on a new device that it goes through multiple iterations until the dev engineers a fix to all the issues? Does it make any difference when HTC for example eventually release the kernel source (which I assume they will once the official JB release comes out). I'm guessing stuff like the headphone issue/in-call echo will be 'fixed' in the official release from HTC so could be implemented in existing ROMs?
Hope that makes sense and I haven't just broken a load of noob xda rules....
Thanks
basically a rom is never really finished.
theres always something to be ironed out or a bug that needs to be squashed. or sometimes its just enhancements,
but yea like you said until htc releases the source then stuff wont be 100%
Even when they do release the sources, there's still lots of things that potentially might not work.
Like take for example CM9 (ICS based) - although there are kernel sources out already for HTC's ICS, a bunch of things are not yet working. You can blame that on closed-source drivers, like wifi or camera, etc.
So it might take a while for everything to work properly, but as long as we have dedicated developers like xkonni, intervigil, etc, there's nothing to be worried about.
Sent from my HTC One S using xda premium
Nice thanks guys that makes sense. I just assumed that things like drivers could be poached and reused but I guess a lit of that is part of the sense framework.
I look forward to seeing what happens
Sent from my HTC One S using xda app-developers app
dillinga said:
Hi Guys,
I'm very new to this scene and have already started experimenting with ROMS (running Leedroid at the moment). I've just had a quick play with Coldblooded CM10 and love it but I'm intrigued about the current 'broken list'.
Is this just the way it goes with ROM Development on a new device that it goes through multiple iterations until the dev engineers a fix to all the issues? Does it make any difference when HTC for example eventually release the kernel source (which I assume they will once the official JB release comes out). I'm guessing stuff like the headphone issue/in-call echo will be 'fixed' in the official release from HTC so could be implemented in existing ROMs?
Hope that makes sense and I haven't just broken a load of noob xda rules....
Thanks
Click to expand...
Click to collapse
No worries man this was a very legit question.
I'm a little confused by the range of options available for the Photon Q. Of course, CM12 is still in development, but does CM11 have a stable build at this point? What are people's experiences with it, and do they recommend updating from stock?
I'm mainly thinking about it because I'm starting - very slowly - to stumble across app compatibility issues, and I want to hold off updating my phone for at least another year. Kind of holding hope that Blackberry will finally release an Android phone.
kennyminot said:
I'm a little confused by the range of options available for the Photon Q. Of course, CM12 is still in development, but does CM11 have a stable build at this point? What are people's experiences with it, and do they recommend updating from stock?
I'm mainly thinking about it because I'm starting - very slowly - to stumble across app compatibility issues, and I want to hold off updating my phone for at least another year. Kind of holding hope that Blackberry will finally release an Android phone.
Click to expand...
Click to collapse
CM11 has EOL'd. Final official release 6-26 (obviously the jbbl version for the QHD). Newer builds with stagefright patches have been released (see MCP1's builds over in RHD).
CM12 has also EoL'd.
CM12.1 is still in development.
CM13 (Android M/6.0/Marshmallow) has not started yet.
Sent from my ATRIX HD using XDA Free mobile app
I've been using pure white Nexus ROM for a while but the dev Trevelyan announced he would no longer be supporting it with the monthly Google security updates.
Does this mean that any phone using this custom ROM is now insecure and users should find an alternative option or just go back to stock Google ROM to ensure they continue to get the monthly security patches?
Thanks.
I guess either no one cares about security or have moved on to nougat!
Yes, no more updates means you won't be secure anymore, since vulnerabilities will be found but never fixed. Note that going back to stock won't help you, as stock also no longer gets security updates (October was the last one). You'd need to switch to a different custom ROM.
I guess I'll need to find my new daily. Looks like nougat ROMs are still iffy in terms of full functionality.
Exactly my problem. Unstable / not anymore developed roms . I'm just gonna stick to good old SlimKat..
I guess I'll stick with pure white then. If no ROMs are getting any updates from Google then they will all have the same potential security risks? At least ElementalX kernel incorporates security patches and enforces SELinux. Maybe time to buy the new pixel.... The N5 had served me well, but security is paramount for me.
There are still some custom ROMs that get security updates (e.g., CyanogenMod).
How can CM get security updates if Google has stopped providing them for the Nexus 5? I don't understand? Thanks
For a few things (the non-free vendor drivers), you're right; those pieces don't get updated. But most of Android isn't device-specific, so the community takes the updates Google pushed to AOSP for the devices they do still support and ports them to the ones they don't.
OK. What's considered best daily CM ROM?
I'd personally recommend the latest official nightly.