If you need Flash Player on JellyBean, then do the following.
1. Download the Adobe Flash Player (v.11.1.115.12).
2. Copy the file to your device (tablet or a phone - it does not matter).
3. Install.
4. Start the browser.
5. Login to your browser settings and put the check in front of Flash Player.
6. Now you have the latest version of Flash Player!
7. Enjoy
aleeyt said:
If you need Flash Player on JellyBean, then do the following.
1. Download the Adobe Flash Player (v.11.1.115.12).
2. Copy the file to your device (tablet or a phone - it does not matter).
3. Install.
4. Start the browser.
5. Login to your browser settings and put the check in front of Flash Player.
6. Now you have the latest version of Flash Player!
7. Enjoy
Click to expand...
Click to collapse
This is not working as it should.
In defy 4.1 thread there is a guy saying that it has to do with some codec which maybe makes netflix not working either!
I have tried many flash players and no success, I think we will have to wait for quarx or epsylon or somebody else who makes it works!
yeah
Doesn't work, running cm10 4.1.1 on a bravo
scottman0830 said:
Doesn't work, running cm10 4.1.1 on a bravo
Click to expand...
Click to collapse
Its becfixedof a codec which needs to be fixed!
I hope quarx fix it soon!
I tried flash player in an atrix with jb and it worked excellent!
It also depends on what browser you are using. Stock browser works fine, and Dolphin is easy to get working.
http://forum.xda-developers.com/showthread.php?t=1846225
Sent from my EVO using xda premium
bilbo524 said:
It also depends on what browser you are using. Stock browser works fine, and Dolphin is easy to get working.
http://forum.xda-developers.com/showthread.php?t=1846225
Sent from my EVO using xda premium
Click to expand...
Click to collapse
It is not working for us Bravo and Defy users, there is a codec which is broken and needs to be fixed as well.
It works partially, but when you try to see some flash videos or use youtube it freezes browser.
Forgive me, didn't realize I had switched forums to a different device
Sent from my EVO using xda premium
bilbo524 said:
Forgive me, didn't realize I had switched forums to a different device
Sent from my EVO using xda premium
Click to expand...
Click to collapse
It's ok, you can stay a while if you would like. Some of us have never met anyone outside the realm of Bravo.
Dr. Orange said:
It's ok, you can stay a while if you would like. Some of us have never met anyone outside the realm of Bravo.
Click to expand...
Click to collapse
Then hang out at the Defy Forums . Its where I go when its slow here. Besides, they have the same bugs, glitches, and roms that we do (well, they have 1000x more niche roms, but they can all be ported rather easily). The Defy Forum is the best place to find updated info for our roms, mods, tweaks, tips, etc...
FYI -- The Bravo is basically a Defy Minus. A Defy minus the led flash, minus the 5mp camera, minus the GB kernel, minus the number of devs, minus the search button. Everything else is damn-near the same between the two phones; even our bootloaders are similar -- we have 9.12 and they have 9.10 -- its that .02 that keeps us from running GB kernels on the Bravo (other than the Bravo has different CG versions -- usually Defy CG value +1).
skeevy420 said:
Then hang out at the Defy Forums . Its where I go when its slow here. Besides, they have the same bugs, glitches, and roms that we do (well, they have 1000x more niche roms, but they can all be ported rather easily). The Defy Forum is the best place to find updated info for our roms, mods, tweaks, tips, etc...
FYI -- The Bravo is basically a Defy Minus. A Defy minus the led flash, minus the 5mp camera, minus the GB kernel, minus the number of devs, minus the search button. Everything else is damn-near the same between the two phones; even our bootloaders are similar -- we have 9.12 and they have 9.10 -- its that .02 that keeps us from running GB kernels on the Bravo (other than the Bravo has different CG versions -- usually Defy CG value +1).
Click to expand...
Click to collapse
It's stuff like that that makes me wonder why companies decide to offer two almost identical models of phone, when they can save so much money offering one device. I love my bravo though, it's my first smart phone and I've had no complaints what so ever concerning Motorola. But it doesn't make logical sense to offer the same thing in a different body. Maybe someone can enlighten me.
Never thought about checking out the defy forums, thanks for the tip skeevy.
Dr. Orange said:
It's stuff like that that makes me wonder why companies decide to offer two almost identical models of phone, when they can save so much money offering one device. I love my bravo though, it's my first smart phone and I've had no complaints what so ever concerning Motorola. But it doesn't make logical sense to offer the same thing in a different body. Maybe someone can enlighten me.
Never thought about checking out the defy forums, thanks for the tip skeevy.
Click to expand...
Click to collapse
The multiple phone issue is for different markets\carriers. There's a lot of phones, especially Motorola phones, that are almost the same as the next one -- DroidX, Bravo, Defy, Defy+, Cliq2; all those phones listed can easily port from each other with just a few libraries different between them -- usually camera, gps, and sensors.
For example, all our Bravo roms used to be Defy Ports until Quarx started doing CM roms for us. All we have to change is 3 camera libs, imager_cfg.bin, rename /lib/hw/whatever.jordan.so to whatever.kobe.so, add in the Bravo baseband, and change the build.prop to have the Bravo labeling --- that method works on almost all Defy roms, Since then, we've had a few camera revisions so you have to try different releases for the camera libs (there's 2 for CM7, 3 for CM9, and 1 for CM10) and some ports require you to use libandroid_server.so from a Bravo CM Release or from Stock Froyo. I've ported a lot of Defy Roms -- WR, PIkachu, all Miui roms are all Defy Ports.
The only reason MS2 doesn't fully work is its framework specifically looks for the Defy camera libs and replacing them with Bravo libs causes it to freeze on boot. I think it may be possible to decompile\smali the MS2 framework-res.apk and framework.jar and add in the Kobe camera java code to them to make our camera work with MS2, I just haven't gotten around to trying it. So far all I've tried is replacing the tether java code with CM7's to get tethering to work for me. MS2\Moto Roms have a phone home code attached to the tethering so if you don't pay for tethering you can't use it -- I tether my home wifi, not 3G, so it really bugs me that I can't tether my wifi to my PC.
skeevy420 said:
The multiple phone issue is for different markets\carriers. There's a lot of phones, especially Motorola phones, that are almost the same as the next one -- DroidX, Bravo, Defy, Defy+, Cliq2; all those phones listed can easily port from each other with just a few libraries different between them -- usually camera, gps, and sensors.
For example, all our Bravo roms used to be Defy Ports until Quarx started doing CM roms for us. All we have to change is 3 camera libs, imager_cfg.bin, rename /lib/hw/whatever.jordan.so to whatever.kobe.so, add in the Bravo baseband, and change the build.prop to have the Bravo labeling --- that method works on almost all Defy roms, Since then, we've had a few camera revisions so you have to try different releases for the camera libs (there's 2 for CM7, 3 for CM9, and 1 for CM10) and some ports require you to use libandroid_server.so from a Bravo CM Release or from Stock Froyo. I've ported a lot of Defy Roms -- WR, PIkachu, all Miui roms are all Defy Ports.
The only reason MS2 doesn't fully work is its framework specifically looks for the Defy camera libs and replacing them with Bravo libs causes it to freeze on boot. I think it may be possible to decompile\smali the MS2 framework-res.apk and framework.jar and add in the Kobe camera java code to them to make our camera work with MS2, I just haven't gotten around to trying it. So far all I've tried is replacing the tether java code with CM7's to get tethering to work for me. MS2\Moto Roms have a phone home code attached to the tethering so if you don't pay for tethering you can't use it -- I tether my home wifi, not 3G, so it really bugs me that I can't tether my wifi to my PC.
Click to expand...
Click to collapse
When my pc is fixed the first thing I will be doing its porting a defy rom following these steps, later when I see everything is working I will try compiling from source.
it works on Samsung Galaxy S3. Thank you so much
daywalker23 said:
it works on Samsung Galaxy S3. Thank you so much
Click to expand...
Click to collapse
Of course it is working for.you, this is just a problem now for Bravo and Defy users. I hope quarx fix that broken codec so we can watch flash videos and I think netflix too.
Its installed on my Samsung Google Nexus s (4.1.1)
After Adobe Flash Player installed, I started the browser, I open settings, then there's ==>
General, Privacy & Security, Accessibility, Advanced, Bandwidth Managament, Labs.
What is the next step to =>put the check in front of Flash Player.
I looking forward to your help and Thanks in advance
aleeyt said:
If you need Flash Player on JellyBean, then do the following.
1. Download the Adobe Flash Player (v.11.1.115.12)[/URL].
2. Copy the file to your device (tablet or a phone - it does not matter).
3. Install.
4. Start the browser.
5. Login to your browser settings and put the check in front of Flash Player.
6. Now you have the latest version of Flash Player!
7. Enjoy
Click to expand...
Click to collapse
XKrolis said:
After Adobe Flash Player installed, I started the browser, I open settings, then there's ==>
General, Privacy & Security, Accessibility, Advanced, Bandwidth Managament, Labs.
What is the next step to =>put the check in front of Flash Player.
I looking forward to your help and Thanks in advance
Click to expand...
Click to collapse
We can just go through the motions and install Flash Player, it doesn't actually work. Our platform has flash codec issues with ICS on up.
Worked
It worked on my Atrix HD 4.1.1 :good:
Worked on htc one x.
Hello,
I have full stock rom non rooted.
I installed this APK and used ICS quick browser from the android market. Works like a charm. Thanks.
Thanks for sharing
Related
Hey guys. I read on a couple of blog sites that the HTC Desire 2.1 Sense ROM has been leaked and it's currently being ported onto the Nexus One.
Is there any chance we can use this ROM to fill in the gaps for our 2.1 ROM, or maybe even just port this ROM directly onto our CDMA Hero's?
Here's one of the articles: http://phonedog.com/cell-phone-research/blog/htc-s-sense-ui-ported-over-to-nexus-one.aspx
This does mean there is an HTC 2.6.29 kernel. It's an HTC kernel, but not a Hero-specific kernel. This might make porting the kernel easier.... who knows.
HeroMeng said:
This does mean there is an HTC 2.6.29 kernel. It's an HTC kernel, but not a Hero-specific kernel. This might make porting the kernel easier.... who knows.
Click to expand...
Click to collapse
Could it help in getting camera to work on 2.0+ custom ROMs, even if it's for another phone?
Yes, it could. This means there's a 2.6.29 kernel for HTC Sense phones. We need to put in the device drivers (i.e. microphone, camera, speakers, trackball) and see if it works. If not restore a Nandroid and try again. Any devs correct me if I'm wrong?
oh wow it says the new flash is in it too...could that be ported to?
ko0pa11 said:
oh wow it says the new flash is in it too...could that be ported to?
Click to expand...
Click to collapse
I think that's a matter of an APK. It might have some dependencies that are in the .29 kernel, not sure.
Sorry I haven't searched yet, but could someone find me a link to a ROM from it? I'll try my hand porting some stuff.
yeh i can do some porting too we can make it a group project. but i really dont think it is possible. if anything perhaps we can take some stuff from the rom and port it to the 2.1 rom flipz has out and maybe get camera and stuff working.
I should've mentioned that's what I would've done.
I can't find the leaked rom after much googling. Might be on the Nexus One forum... brb.
Is this it?
Originally Posted by jonasl
I'm really interested in the keyboard apk (HTC_IME). As soon as I get my hands on it I can strip out sense checks and the connection to HTC custom settings database to enable language settings.
I've done this with the old HTC_IME:
http://forum.xda-developers.com/show....php?p=5475283
but many (including myself) want a hires version
Download it from here: http://www.romraid.com/paul/nexusone...ire-signed.zip
Click to expand...
Click to collapse
animal7296 said:
Is this it?
Click to expand...
Click to collapse
That's the HTC_IME that fits the hi-res Nexus screen.
I think MaDaCo got it from a inside source. The watermarking has been removed but he isn't convinced it is clean and ready for open distribution yet. (Doesn't want anyone to lose there job if its not clean)
He has promised that once it is clean and ready he will for sure post it for everyone to have.
thank you for the info^^^
i guess we wait it out..
dchadwick said:
I think MaDaCo got it from a inside source. The watermarking has been removed but he isn't convinced it is clean and ready for open distribution yet. (Doesn't want anyone to lose there job if its not clean)
He has promised that once it is clean and ready he will for sure post it for everyone to have.
Click to expand...
Click to collapse
post it as in, it works for our hero's?
maybe this will give people a chance to figure out a way to OC??? just a thought i hope so!!! i been waiting since 2.0 was announced to get it for sense! im so excited!
Android dev Modaco has gotten his hands on a watermarked copy of the HTC Desire ROM. He has successfully ported the too big ROM (too big for the N1 by 200 MB) into his Nexus phone. This could possibly be what all you Sense UI fans have been waiting for, though you shouldn’t be too excited just yet. Modaco has stated he doesn’t plan to release this ROM until he receives an unwatermarked version of it.
Hit the jump to see the details about Modacos ROM.
- If you rebuild the boot image replacing the kernel it runs. I’m running my own custom kernel with himem and bits.
- The system.img doesn’t fit on the N1 (!), it’s nearly 200MB. I booted by moving some stuff off the system partition.
- The trackball works.
- The 4 bottom keys work.
- The proximity sensor works.
- The LED works.
- The light sensor works.
- The compass and G sensor work.
- The camera works fine and is great with face recognition and touch focus.
- The FM radio loads, but makes no sound / finds no stations it seems. Maybe we need Desire radio ROM?
- The build I have is watermarked – i’ve removed the obvious visual watermarks but no, you can’t have this release – when I get a watermark free drop, yes!
- Flash 10.1 is included and works well.
- It’s FAST!
- WiFi works
- Bluetooth works
- 800×480 video recording, camera maxes out at 3MP (fixed in later builds)
More to follow!
[via Modaco]
amot said:
Android dev Modaco has gotten his hands on a watermarked copy of the HTC Desire ROM. He has successfully ported the too big ROM (too big for the N1 by 200 MB) into his Nexus phone. This could possibly be what all you Sense UI fans have been waiting for, though you shouldn’t be too excited just yet. Modaco has stated he doesn’t plan to release this ROM until he receives an unwatermarked version of it.
Hit the jump to see the details about Modacos ROM.
- If you rebuild the boot image replacing the kernel it runs. I’m running my own custom kernel with himem and bits.
- The system.img doesn’t fit on the N1 (!), it’s nearly 200MB. I booted by moving some stuff off the system partition.
- The trackball works.
- The 4 bottom keys work.
- The proximity sensor works.
- The LED works.
- The light sensor works.
- The compass and G sensor work.
- The camera works fine and is great with face recognition and touch focus.
- The FM radio loads, but makes no sound / finds no stations it seems. Maybe we need Desire radio ROM?
- The build I have is watermarked – i’ve removed the obvious visual watermarks but no, you can’t have this release – when I get a watermark free drop, yes!
- Flash 10.1 is included and works well.
- It’s FAST!
- WiFi works
- Bluetooth works
- 800×480 video recording, camera maxes out at 3MP (fixed in later builds)
More to follow!
[via Modaco]
Click to expand...
Click to collapse
this sounds exciting
nerdgasm
Oooo and I was starting to think I made a bad choice by getting the Hero seeing as how htc is coming out with all these new phones, looks like things are just getting started with all the goodness to come in the near future.
p.s.-i love this forum and all the smart people who know what the hell theyre doing
Hey I was wondering if there was any way that someone could make a sense rom for the droid 2 and if it would even run on it. Also why wouldn't it work it is just additions to the system/app and system/framework.
Please explain what a locked bootloader restricts. I know it means that you can't use un-official kernels but does that mean you can't change it to sense?\
I would love to have the new sense from the desire HD for the droid 2.
****BUMP****
from what i understand the big thing holding back alot of the dev work for stuff like that on the droid2 is the motorola locked bootloader.... so far i've seen themes and the like with alot of the motoblur taken out/turned off but nothing beyond that (not even an aosp) but i know that its being worked on by some good people and I am holding my breath for the goods to start flowing for both the 2 and the X.... in fact i would really like to have it by the big tx bbq.... kinda soon but i can dream
ljbaumer said:
Hey I was wondering if there was any way that someone could make a sense rom for the droid 2 and if it would even run on it. Also why wouldn't it work it is just additions to the system/app and system/framework.
Please explain what a locked bootloader restricts. I know it means that you can't use un-official kernels but does that mean you can't change it to sense?\
Click to expand...
Click to collapse
i adapted somehow htc sense to our Milestone (Droid 1 EU edition) , it works, but lacks speed due to the limited 256MB RAM available, secondly no-one has written a driver that emulated the bcm4329 hardware, so making bluetooth working ok is another major "not working".. even on older htc phones they had problems.
anyways i can say its possible is i did the reverse and put MotoBlur on Milestone, it works but somehow also lacks 512MB RAM here too.
to end this quick note,
HTC sense is not just an addition to the framework, its a different releas of the framework, every vendor does this, so like EU motorola did many updates on the milestone, but only first found now in droidx,droid2...
and porting it is not so simple, but i would think its possible, but i guess its too early for droid2 to have anything running as no real recovery exists, which loads before any os.
the one you got has a live /system when you open recovery, which means you can easily mess up your phone when you start modding to use sense, and pretty much make it unbootable, so a new sbf needs installed, which again means alot of testing before you actually get it working, and then backup? another problem to work with when you make small changes..
its not easy task without a real unlocked boot or a good recovery solution..
ok so technically what would I have to do to put sense on the droid 2?
ljbaumer said:
ok so technically what would I have to do to put sense on the droid 2?
Click to expand...
Click to collapse
It will never work 100% of even close enough to have the phone fully functional. People have been trying since the Original Droid. It's also tied into the RIL of phone.
Out of the blue question
What about just theming the home screen menubars to get the sense menubars only? Is that possible?
that should be possible, as a few themes available right now have already altered those files with success. Now you just have to grab a Sense based ROM form a Droid 1 and start copying and modding image files mostly i think. to make a deodexed hybrid of Sense and MotoBlur.
Is is possible to just to have the speed-dialer/contact app working the D2(that is the only real thing I will miss if I go with the D2)?
I'd move to the D2 right away if you can get the HTC keyboard mixed with the multitouch keyboard of the D2, and then add contact app(and all that comes with it), and music app. That all I really like out of my Eris.
If the D1 was able to get a sense port(from what i have seen) how come we cant get it on the D2?
Mackattack said:
If the D1 was able to get a sense port(from what i have seen) how come we cant get it on the D2?
Click to expand...
Click to collapse
the original Droid ran stock android, but the droid 2 has a custom framework (MotoBlur) and a locked bootloader.
Makes logical sens thanks
hello, what rom you would reccomend for bravo? camera is doesnt matter
lietuva70 said:
hello, what rom you would reccomend for bravo? camera is doesnt matter
Click to expand...
Click to collapse
MIUI. MIUI is based off CM7 but it has a lot more features. I've been having fun with it. Here is close to the latest version MIUI 1.9.2, I'll try getting 1.9.9 working a little while later, but it's not very hard, you could do it yourself.
rdannar's last rom based off miui is smooth like butter! highly recommend
Stock froyo diet works best for me
I am coming from Nexus one and the plain google experience just sucked for me (worst email client ever)
After removing bloatware from stock froyo , I like it. it is fast without the need of overclocking.
I also like data and battery manager, I am on 200mb data plan and have wifi at home and work , those features help me control data usage
With motoblur you can track your phone;s location if it is lost / stolen
I tried some of the roms published here but kept coming back to stock.
On the t-mobile G1, when the Motorola Cliq was released, we were able to copy the apk from the system dump of the cliq into the system or even just install as apk on the G1 (The apk for motorolas tracking thing....) It was just one apk maybe two it didn't require all blur and framework...
It probably does by now, have you considered checking into that though?
http://download882.mediafire.com/f9zhxz4ab1qg/xg038h071w035ax/MIUI.us_MB520_1.8.19_Eng.zip
tried most of the ROMs available and this MIUI just seems to be the best, next to no bugs and translations are all great.
A couple of guys in my office got fires for Xmas, and they want to put a stock rom on them so they can use it like a normal tab and get the google market place.
Can someone point me to a tutorial for putting a new rom on a fire and a link to stock ICS or stock honeycomb for them?
Thanks.
derricks2 said:
A couple of guys in my office got fires for Xmas, and they want to put a stock rom on them so they can use it like a normal tab and get the google market place.
Can someone point me to a tutorial for putting a new rom on a fire and a link to stock ICS or stock honeycomb for them?
Thanks.
Click to expand...
Click to collapse
There is no honeycomb port to the Fire (at least not yet anyway).
As for ICS, there is a port-in-progress that is in pre-alpha stage here:
http://forum.xda-developers.com/showthread.php?t=1411895
There is a stable (good for everyday use) port of CM7 (Gingerbread) here:
http://forum.xda-developers.com/showthread.php?t=1390773
As for how to flash ROMS, take a look at this thread:
http://forum.xda-developers.com/showthread.php?t=1399889
we are pretty much stuck with gingerbread right now as said above.
I'm using the CM7 that he linked to above. Downsides to this are that you loose the ability to use amazon prime videos and lending. Basicly, you loose the stock amazon app (which is integrated into the OS), so these are not available. You can however use the Amazon app from google apps, which allows you to read amazon books.
The ICS builds that are in progress still have to many issues for me to try them. Occasional issues with accessing SD card, no hardware video support and patchy sound.
Like what the above poster stated, your best bet at thee moment is cm7 if you are looking for a good, stable, daily os with marketplaces access. I personally am using the pre-alpha ICS build and am loving it despite the issues but it really is just for testing at this point.
Sent from my Amazon Kindle Fire using Tapatalk
Also the ICS builds do not support USB. So you would have to boot to TWRP to mount the SD card to load files from your PC to your Fire. Then boot back to the OS to use the device.
If they just want the google marketplace then you can root and install the market on the stock ROM. If you want a custom rom, your best bet right now is CM7. If you give it a month or two I'm sure there will be a decent ICS daily driver out.
It sort of depends on how far you need to go before they consider it a "normal tab." I use mine on the stock rom for stuff I would expect out of a normal tab.. watching video, reading, listening to music, some web browsing, every now and then some robo defense or the like, etc. It works fine like that for me.
Hello,
I just would like to share my experience of moving from the stock 4.1.2 Jelly Bean to the CM10 release, mostly for people who are still using stock 4.1.2 because I couldn't find such a thread before jumping to CM10.
I installed the 5th November nightly release of CM10 as the more recent ones (including the "stable" release) have an annoying problem : the Play Store reports some incompatibilities with apps which were working fine with the stock 4.1.2. It seems that this problem is due to the lack of free memory with the newest CM10 releases ...
The 11/05 CM10 was the last one with no Play Store problems, you can download it here for the Wingray :
http://dl.dropbox.com/u/2383656/cm-10-20121105-NIGHTLY-wingray.zip
EDIT : on the 6th December, I updated my Xoom from the 11/05 nightly to the 12/05 nightly, and so far I still didn't have the Play Store compatibility issue, which means the problem has been solved in between these two releases ...
Performances :
I must admit that I didn't think it was possible that a custom ROM was better optimized than the one made by Google itself ...
I was very happy with the fluidity of the stock 4.1.2, but when I used CM10 for the first time, I tried some websites known to be a bit laggy with the stock browser, and they were just close to perfect about fluidity with CM10 ! I couldn't find a laggy website with stock browser yet ... These tests were not involving overclocking.
So I then ran Quadrant and had a score of 2800, where I had 1900 with stock 4.1.2 ... !
I then overclocked the Xoom to 1,5 GHZ, and Quadrant reported a score of 4100, about equal to the Transformer Prime !
I don't really play with my Xoom but I tried to play to GTA III, and when overclocked, compared to the stock 4.1.2, I could put a lot more graphical details with a better fluidity. I really felt like using a whole new device. But most of the time I don't use overclocking as I want to save my battery life, and the overall fluidity of the Xoom running CM10 at 1GHz is very good.
A few people reported they found a performances increase with the very last nightly release. However, as it still have some compatibility problems with the Play Store, I will not jump on it.
I don't know if Cyanogen will try to solve this incompatibility issue as it maybe related to the Gapps taking too much storage space, and Cyanogen does not support Gapps ...
Updates :
I choosed a Cyanogen rom (instead of EOS) because with this one you can easily update to newer ROM release very easily, without the need to connect your Xoom to the PC, and without loosing datas : CM10 includes an update manager which proceeds just like an official Google OTA ! That's just perfect to me, I'm not sure if this does also exist on EOS, I couldn't find any informations about this.
So I have the feeling that my Xoom is still supported and updated, which is very good. Thanks a million to Cyanogen team !
Bugs :
I couldn't find bugs yet on the 11/05 release, I just had an unexpected reboot the very first time I used it, only after 5 minutes of use. Since then, I never had this problem again (3 days with no reboots for now).
Features :
I didn't try all of them yet, but there are plenty of cool features :
- overclocking ability with multiple policies possible to save battery life for exemple, or for the best performances all the time.
- other performances tweaks about RAM like "KSM" use, and some other parameters which allow better performances but lowering the battery life.
- root of course !
- the ability to light the charging LED, even when your Xoom is powered on.
- many many others, some I didn't tried/discovered yet.
So I am very happy now with CM10, and I would like to thanks Cyanogen again about this excellent work !
I would recommand to any stock 4.1.2 users to jump on to CM10, the Xoom will just be running better then !
Here is the link which explains how to jump to a Cyanogen ROM :
http://wiki.cyanogenmod.org/wiki/Mo...de#Installing_the_ClockworkMod_Recovery_Image
Have fun !
TeamEOS has all the features you mentioned and you can update it easily as well. Don't need a computer, they use GooManager. In short they are both good ROMs, there is nothing to dislike about both of those ROMs, both teams have putted a lot of effort into optimising the XOOM and adding functions/features. It's all up to user preference, with CM ROMs I get random reboots, while TeamEOS I don't get any of that.
Chaosgod27 said:
TeamEOS has all the features you mentioned and you can update it easily as well. Don't need a computer, they use GooManager. In short they are both good ROMs, there is nothing to dislike about both of those ROMs, both teams have putted a lot of effort into optimising the XOOM and adding functions/features. It's all up to user preference, with CM ROMs I get random reboots, while TeamEOS I don't get any of that.
Click to expand...
Click to collapse
How polished is the root/rom procedure for the Xoom? I came from the Transformer world and it was pretty well dialed in..not a lot of monkeying around or knowledge required.
What's the easiest way to get root and a custom rom?
rpavich said:
How polished is the root/rom procedure for the Xoom? I came from the Transformer world and it was pretty well dialed in..not a lot of monkeying around or knowledge required.
What's the easiest way to get root and a custom rom?
Click to expand...
Click to collapse
Idk, never rooted or used a Asus tablet. Once the Xoom is unlocked and rooted you really have no need for a PC unless you use fastboot & adb to flash, push, pull, etc.....
Sent from my Xoom using Tapatalk 2
Chaosgod27 said:
TeamEOS has all the features you mentioned and you can update it easily as well. Don't need a computer, they use GooManager. In short they are both good ROMs, there is nothing to dislike about both of those ROMs, both teams have putted a lot of effort into optimising the XOOM and adding functions/features. It's all up to user preference, with CM ROMs I get random reboots, while TeamEOS I don't get any of that.
Click to expand...
Click to collapse
Definitely. I've used both ROMs, but struggled with SOD's on EOS Stable and lag on the nightlies! CM10 solved both of these issues for me. Both ROMs are full of features and and a no brainer compared with stock.
Regards.
lynxboy said:
Definitely. I've used both ROMs, but struggled with SOD's on EOS Stable and lag on the nightlies! CM10 solved both of these issues for me. Both ROMs are full of features and and a no brainer compared with stock.
Regards.
Click to expand...
Click to collapse
Thanks a lot, that's interesting. I was more and more thinking about trying the EOS ROM, but I was too lazy about reinstalling all my softwares and data ...
What do you mean by "SOD" ?
It's very interesting to have the feedbacks of people having tried both custom ROMs, it would be cool if some other people could give their opinion.
dizzy33 said:
It's very interesting to have the feedbacks of people having tried both custom ROMs, it would be cool if some other people could give their opinion.
Click to expand...
Click to collapse
i have not tried EOS yet. CM10 runs absolutely flawless. I got a good 14hrs -/+ on the battery playing Deadzone, watching movings, browsing the net, skyping with my kids and I still have 28% left today. No OC. Having full R/W access to the External Sdcard is great. I now can Dropsync my folders from my Dropbox to the card for a quick handy on the go backup
EOS from what i have heard has some great features.....i will need to backup and give it a go here soon.
Sent by Samsung Galaxy Nexus (SCH-I515 Verizon LTE) using Tapa2
rpavich said:
How polished is the root/rom procedure for the Xoom? I came from the Transformer world and it was pretty well dialed in..not a lot of monkeying around or knowledge required.
What's the easiest way to get root and a custom rom?
Click to expand...
Click to collapse
Yes it's very easy, considering this is a google experience device all you really have to do is unlock it, flash in recovery and then using recovery flash in another ROM. You should have zero problems at all, considering the bootloader is unlocked.
Can anyone please tell me if one of the december CM10 nightly did solve the Play Store incompatibility problem ?
Thanks !
dizzy33 said:
Can anyone please tell me if one of the december CM10 nightly did solve the Play Store incompatibility problem ?
Thanks !
Click to expand...
Click to collapse
No need to ask this question almost everywhere.......I have not experienced any market issues.....
Sent by Samsung Galaxy Nexus (SCH-I515 Verizon LTE) using Tapa2
cdexsw said:
No need to ask this question almost everywhere.......I have not experienced any market issues.....
Sent by Samsung Galaxy Nexus (SCH-I515 Verizon LTE) using Tapa2
Click to expand...
Click to collapse
as long as you will not entirely answer my questions, I will still ask it, and I'm free to do it !
Yes you don't have this problem now, thanks for this information, but did you have this problem before ?
If you never had this problem, this means you may not be using the CM10 Gapps but the EOS one, or you just didn't realize that you actually have a compatibility issue with the Play Store ... It's easy, check the application named "eye in sky weather", if the store says that it's not compatible with your device, it means that you're facing the compatibility issue as this application is in fact compatible with the Xoom. Of course this problem is not only for this application, there are many others which are reported as not compatible ...
dizzy33 said:
as long as you will not entirely answer my questions, I will still ask it, and I'm free to do it !
Yes you don't have this problem now, thanks for this information, but did you have this problem before ?
If you never had this problem, this means you may not be using the CM10 Gapps but the EOS one, or you just didn't realize that you actually have a compatibility issue with the Play Store ... It's easy, check the application named "eye in sky weather", if the store says that it's not compatible with your device, it means that you're facing the compatibility issue as this application is in fact compatible with the Xoom. Of course this problem is not only for this application, there are many others which are reported as not compatible ...
Click to expand...
Click to collapse
I am using the latest nightly. In fact i have used all the December nightlies with no issues.
As far as gapps, i have used that lastest gapps 4.1.2 and i have tried gapps 4.2+. I used the gapps posted in the link on first page of this thread both packages i have experienced no issues, market is working fine, no incompatibilities.
As far as my comment about aking your questions.....ask in one place....no need to ask your question in every forum are start a new thread.....i was not being rude, it is in the forums rules.......
Good luck.....
Also, check your dpi settings....that will cause market issues. Search the forums & google the fix is simple...
Also try manual installing an older marker version or try or KDH 4.2 gapps.
These are all solutions to your issue(s). No one else may try and answer you question because they are not having or no longer have these issues.......what i posted above are the steps to fix the issue.
Sent by Samsung Galaxy Nexus (SCH-I515 Verizon LTE) using Tapa2
Thanks for these informations, I'll check this. But for now I have no problems with the market as I am using the 11/05 release. The problem came after this release and was known to be due to a free memory issue (check my first post of this thread). That's why I was asking if a recent release of CM10 did solve this problem.
EDIT : I just jumped from 11/05 nightly to 12/05, and I still have no problems with the Play Store, which means the Play Store compatibility problem has been solved in between these two releases ... Great news !
Thanks
Thanks man, that's what I needed to migrate, a good experience report.
I heard about incompatibilities, also that some apps won't work, but I can manage that. I'm now going to make a backup of my things and this weekend I want to install CM10. The main problem now is the backup, since I have a lot of things on it, both the internal memory and SD are quite full. XD
The most surprising thing is that I could not find any report about this bug correction, which was a very annoying bug, but I could find plenty of threads talking about this problem and trying to find workaround solutions ... None of them reported this bug does not exist anymore ...
Similar ROM experiences...
Chaosgod27 said:
TeamEOS has all the features you mentioned and you can update it easily as well. Don't need a computer, they use GooManager. In short they are both good ROMs, there is nothing to dislike about both of those ROMs, both teams have putted a lot of effort into optimising the XOOM and adding functions/features. It's all up to user preference, with CM ROMs I get random reboots, while TeamEOS I don't get any of that.
Click to expand...
Click to collapse
I had similar random rebooting issues using the CM9 ROMs on my tablet which is why I use Team EOS. Both ROMs do have similar features and it comes down to user preference and which UI you prefer.. but BOTH are quality software and greatly appreciated!