Develop Bugs

HTC 3x3 People Widget

Hi
I have just been playing trying to find out if it's possible to replace certain elements of the Android OS with ones from other providers to improve certain aspects.
My main reason for doing this is that my Hero (latest Orange UK 1.5 ROM) has the HTC People Widget which only has the 1x3 option. I'm led to believe that the T-Mobile G2 has a version of the widget that offers other settings (i.e. 3x3).
So the main question is, is it possible to rip the APK from one phone and install it on another?
What I've tried so far leads me to believe the answer is "no".
I've been provided with the apk from a T-Mobile G2
I have a rooted Hero so have booted to the recovery console, deleted the version from my phone (htccontactwidgets.apk and htccontactwidgets.odex) and replaced it with the apk file provided (renamed to htccontactwidgets.apk) then rebooted. Got nothing on this attempt.
My second attempt I used the new apk with the old odex file, this time the widget returned but was still the 1x3 version from my ROM.
Has anybody successfully replaced the 1x3 widget with the improved one from the G2 ROM?

DJBenson said:
Hi
I have just been playing trying to find out if it's possible to replace certain elements of the Android OS with ones from other providers to improve certain aspects.
My main reason for doing this is that my Hero (latest Orange UK 1.5 ROM) has the HTC People Widget which only has the 1x3 option. I'm led to believe that the T-Mobile G2 has a version of the widget that offers other settings (i.e. 3x3).
So the main question is, is it possible to rip the APK from one phone and install it on another?
What I've tried so far leads me to believe the answer is "no".
I've been provided with the apk from a T-Mobile G2
I have a rooted Hero so have booted to the recovery console, deleted the version from my phone (htccontactwidgets.apk and htccontactwidgets.odex) and replaced it with the apk file provided (renamed to htccontactwidgets.apk) then rebooted. Got nothing on this attempt.
My second attempt I used the new apk with the old odex file, this time the widget returned but was still the 1x3 version from my ROM.
Has anybody successfully replaced the 1x3 widget with the improved one from the G2 ROM?
Click to expand...
Click to collapse
did you try flashing modaco roms? the 3x3 people widgets , i had it since i dont even remember when. i think it's from the 2.73 roms.

deeren said:
did you try flashing modaco roms? the 3x3 people widgets , i had it since i dont even remember when. i think it's from the 2.73 roms.
Click to expand...
Click to collapse
I don't really want to flash the whole phone, I'm happy with it now, i'd just like the enhanced People widget.
I'm guessing it will be standard in the official 2.x ROM.

Your missing out then
modaco 3.1 is exactly the same as the stock HTC rom only about 10x faster. I don't even find it lagging on the keyboard even on the phone keypad. You will have a much more pleasurable experience on modaco 3.1 plus you will have the 3x3 people widget

DJBenson said:
I don't really want to flash the whole phone, I'm happy with it now, i'd just like the enhanced People widget.
I'm guessing it will be standard in the official 2.x ROM.
Click to expand...
Click to collapse
it has already been released in the official 2.73 hero rom.
http://forum.xda-developers.com/showthread.php?t=559622
u can install the latest one

yea just get a new generic rom, and install it.

Oh ok, so there is a newer "generic" ROM than the one on my Orange-branded hero? Cool, will check that out.

yea, i had the orange branded as well, and i put the newer generic one, it has the 3x3 widget

I've just taken the plunge and installed v3.1 of MCR, glad I did

See i told you that you'd be impressed!

DJBenson said:
I've just taken the plunge and installed v3.1 of MCR, glad I did
Click to expand...
Click to collapse
hehehe. welcome to the flashing addiction!!!!

I have been on the XDA and Modaco scene for a very long time as a viewer and have partaken in flashing custom ROMs several times before but I always have the feeling at the bottom of my gut that if things go wrong I'll be devastated. The Hero is quite simply the best phone I've ever owned (I said my N95 as good and was reluctant to upgrade from that until I found the Hero) which is why I didn't want to knacker it up, but the benefits far outweigh the risks as far as Paul's ROMs are concerned.
I've read with interest people saying that the MCR 3.1 ROM is draining their battery, and I too thought this but then noticed in the "Spare Parts" app that an app I'd installed (ShootMe) was taking up a lot of processor time sat in the background, so the next charge should prove it's normally 3rd party apps that drink battery power
On a final note, just have to say I absolutely love the Dropbear SSH server, makes it so much easier to tinker with the phone being able to SSH from a desktop.

I cant say I have had problems with the battery. If anything I'm finding mine is lasting a lot longer than it used to. Charged my hero 3 days ago and its still green now. This is with using wi-fi every now and again. Auto updating rss, e-mails etc and I text a lot. Now this I find unbelievable but its true I have the stock HTC battery too. On the stock HTC F/W I was re-charging every night.

welshboy09 said:
I cant say I have had problems with the battery. If anything I'm finding mine is lasting a lot longer than it used to. Charged my hero 3 days ago and its still green now. This is with using wi-fi every now and again. Auto updating rss, e-mails etc and I text a lot. Now this I find unbelievable but its true I have the stock HTC battery too. On the stock HTC F/W I was re-charging every night.
Click to expand...
Click to collapse
3 days??????with data connection 24/24??? how do you manage that? i only manage 18 hours with mine. of course with data connection always on, calls, im's, mails

The data connection isn't always on. Wifi is on most of the time, but that gets turned off automatically for a while. But y/day 3G was on all day and it still didn't drain much battery.

[Q] Games exit when phone left idle (screenoff+lockscreen)

Hello everyone,
I been using my One X for exactly 1 week, coming over after 2 solid years with a modded Desire.
So far, I cant seem to solve this 1 problem which never plagued my Desire (with its lowly 570mb ram).
Problem:
When I run a game (tried on Princess Punt, Angry Birds space) and i look away for a minute, screen turns off as its normal.
Now on my old desire, when I unlocked phone I got right back into the game. With One X, I am sent to desktop after a brief black screen. I select the game from recent apps, and it starts from title screen? What is going on?
I think same happens to internet aswell but it loads the page up again and most cases where i was reading, so no big deal.
Anyone knows how do I fix this?
Background info:
International One X running official 1.29.4x1.xx
Bootloader unlocked and rooted
Stock rom, no modifications
almost no extra running apps/services. usually 280-400mb free ram.

Search threads about the one X multitasking. The apps are killed more aggressively as needed...

I believe there is a fix for this if you have root
Sent from my HTC One X using Tapatalk 2

KrisPerry said:
I believe there is a fix for this if you have root
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
I have root yes and since I managed a nandroid backup last night, not afraid to flash new rom.
Could you kindly point me in right direction?

asestar said:
I have root yes and since I managed a nandroid backup last night, not afraid to flash new rom.
Could you kindly point me in right direction?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1669074&page=10

[Q]CM10 Flinny Test build

Hi XDA,
I'm currently running latest Flinny CM10 test build (125), and an issue I've had for a while is that even when the phone is locked, but screen is on, I can pull down the notification bar and do actions. Is this normal? Is there a setting somewhere that needs to be switched off? I am using Apex launcher.
Cheers.

As far as I know this is a standard behavior since android 4.0 (ICS). There is no settings to disable it.
Someone correct me if I’m wrong
EDIT: If you have enabled screen security (pattern, PIN, password) you should not be able to pull down the notification bar. You should be able to pull it down only with slide lock.

I enabled a simple gesture unlock and yes now I can't pull down the notification bar.
It still seems strange that this is normal behaviour.
Thanks heaps!

yup... That's normal...
I also face some issue which is the ROM could not connect to external gps device... I think that's issue exist in CM10 since have same issue with galaxy smtd...

Yeah I don't have working orientation, light or gyro sensors still. It seems like some people have this problem and others don't depending on hardware revision.

Sorry for writing sth different here but i didnt want to create a new topic, so...
I had this andromadus version on my DZ but i didnt find any pre installed camera app, anyone else who had this or do i have to reload the rom (maybe sth went wrong during downloading)
Sent from my GT-N8010

Vauvenal7 said:
Sorry for writing sth different here but i didnt want to create a new topic, so...
I had this andromadus version on my DZ but i didnt find any pre installed camera app, anyone else who had this or do i have to reload the rom (maybe sth went wrong during downloading)
Sent from my GT-N8010
Click to expand...
Click to collapse
Just wondering... Do u install gapps? If not, you should do that when u install it for the first time (after you install the rom).

Vauvenal7 said:
Sorry for writing sth different here but i didnt want to create a new topic, so...
I had this andromadus version on my DZ but i didnt find any pre installed camera app, anyone else who had this or do i have to reload the rom (maybe sth went wrong during downloading)
Sent from my GT-N8010
Click to expand...
Click to collapse
As with every CM build after 4.1.11.1 on the G1, ALWAYS FLASH GAPPS AFTER FLASHING THE ROM.

cm made a 4.2 donut where the base was flashed first still, so starting with eclair gapps where flashed after
Sent from my HTC Vision using xda premium

blackknightavalon said:
As with every CM build after 4.1.11.1 on the G1, ALWAYS FLASH GAPPS AFTER FLASHING THE ROM.
Click to expand...
Click to collapse
I did, yet ther was no camera app pre installed
Even the icon on the unlock streen existed, but when i unlocked it with the cam symbol nothing happened, it just went back to the lockscreen
I had mimicry before and therefore i got used to flash gapps, so did i with this jb rom too
Sent from my GT-N8010

I love this ROM, everything I generally use on a regular basis works fine. My only real problem is this ROM is a serious power drain, within an hour of being unplugged in the morning I have already lost 10% of the battery, by mid afternoon I am forced to plug the phone back in, this is something of an issue as I work at hospitals and plugging appliances into the mains is a violation of health and safety regulations, but I need my phone so I do what ya gotta do. Is there any way to reduce the drain from this ROM as I am fairly sure it is not any applications I have installed causing it, as none are running in the background when I check running apps.

plug it in to a computer with a logcat running, see what is going on that way. or if you aren't able to sit in front of a computer for a while watchdog is a nice app for this (keep in mind it should be for testing basis and be removed later as it to will always be running in the background)
Sent from my HTC Vision using xda premium

evernote makes phone slow
I am using this rom (build 124) and I have and after restoring all my apps it became really slow. After some try/error I found that uninstalling some apps solved the problem. After that I started installing my apps again one by one and I found installing evernote make the phone near unusable.
Anybody is experiencing this? it also happen if I install "camera 360".

I am running build 127 of this ROM which definitely seems faster than build 126 which was the first one I tried and seems to be quick enough to actually use it most of the time.
When things do go slow it seems to be when switching to a new app and seems more likely to happen is the new or old app is big.
Regarding more apps slowing things down I wonder if it is actually more widgets and background services. If this is, as I suspect, do to with how many apps can be cached in RAM for fast switching then the more apps have something running in the background, for example to sync with a cloud service or to keep a widget updated, the less RAM there will be for the apps you are trying to use and there will therefore be a greater chance the app you are trying to start has to be started from scratch.

These threads really need to stop, Flinny's test build is just that A TEST BUILD problems/issues are expected.

I think it's normal...anyway it don't obstruct me

tarroyo said:
These threads really need to stop, Flinny's test build is just that A TEST BUILD problems/issues are expected.
Click to expand...
Click to collapse
In my case I am certainly NOT contributing in order to criticise. Of course I know a test build may have issues but, like many others I suspect, I am happy to try the latest thing. When things don't work quite right it is worth discussing it. If we can understand what is happening we can help each other mitigate the issue and maybe even have something useful to feed back to developers.
I was running build 127 and things had become very slow. I have now updated to build 128 and the phone is fast again. At this stage I am not sure if this has anything to do with the new build or whether it is down to apps. I have all 45 apps installed but for many of those that sync to cloud services I have not yet got round to setting up the username/password for that to happen so this may be limiting the amount of background activity to a level where it doesn't get in the way. I'll try setting some of them up and see what happens.

Android 4.2 Issues on Galaxy Nexus

Hello Guys
Let's share the bugs that everyone experiencing with the new stock JOP40C Android 4.2 for Galaxy Nexus
I'll go first
I have a problem when in a call the phone keeps doing a weird vibration and once i done the call i find the phone on the homescreen and have to go to the notifications menu to hang up
the other issue is randomly force close for the launcher and some apps
the camera is very laggy when rotating from landscape to portrait
anybody experiencing those issues ?
Ok guys anybody experiencing random reboot on the stock android 4.2 Galaxy Nexus
You can star this for Google to fix : http://code.google.com/p/android/issues/detail?id=39912​

I am not. Also, and unrelated, I'd like to point out the redundancy of your title. Android 4.2 issues on, say android 4.0.4 would be revolutionary, but as you've directed this... Anyways, did you update ota, or flash the image manually? I've read of many issues from the image flashes prior to ota, that I haven't experienced at all since my ota on my drive home.

In stock browser in full screen mode i'm having a weird effect on loading bar on top, don't know if thats supposed to be like that or not.. just strange and sometimes the adress bar becomes bugged strange behavour

Yeah you might wanna reword that title...
Anyway, this update SUCKS!!!!!!! I was trying to be positive about it... Focusing on the cool new stuff... But then that shifted to at least neutral with the crappy changes.... But now this just sucks!!!!!!!!! I just got my first launcher FC EVER!!!! On my galaxy nexus.
No root, never flashed, been stock all the way on this phone just like any regular user. I used to root on my tmobile g2 but decided to keep my gnex all stock.
So what he hell!?!?! Force closing stock launcher!?!?!? Are you freaking kidding me?!? This update is turning into a total joke, its not funny google! Your pulling anAPPLE move on your most loyal customers(nexus customers!)
EDIT: this is a rant.. I was pissed at how badly 4.2 has screwed my phone up. But no i didnt mean the part about being as bad as apple..
I do think 4.2 sucks though. Especially compared to 4.1.2, in my experience they seemed to have sacrificed new features and "style" over stability with 4.2

roadrunnerx7 said:
Yeah you might wanna reword that title...
Anyway, this update SUCKS!!!!!!! I was trying to be positive about it... Focusing on the cool new stuff... But then that shifted to at least neutral with the crappy changes.... But now this just sucks!!!!!!!!! I just got my first launcher FC EVER!!!! On my galaxy nexus.
No root, never flashed, been stock all the way on this phone just like any regular user. I used to root on my tmobile g2 but decided to keep my gnex all stock.
So what he hell!?!?! Force closing stock launcher!?!?!? Are you freaking kidding me?!? This update is turning into a total joke, its not funny google! Your pulling anAPPLE move on your most loyal customers(nexus customers!)
Click to expand...
Click to collapse
Drama queen, much?
Sent from my Galaxy Nexus using xda premium

"the camera is very laggy when rotating from landscape to portrait" --> Yes, this is extremely annoying.
And also I find that when the camera shot in landscape mode, about 10% of the upper and lower part of the viewfinder are cropped (i.e. the things you actually shot are more than what you saw in the camera app)

1). I don't have problem with phone call
2). Yes, launcher FCed! But only happened once after first reboot after flashing factory image.

DirgeExtinction said:
Drama queen, much?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
No, just needed to rant
Plus the fc had just happened like 5min before i posted that. It was weird... I was browsing here on chrome, then pressed the home button and tried opening the launcher, and it got stuck loading for like 10sec... Then fc'd. Soo i tried again and it got stuck again and fc'd. Third time it finally worked.
I expect these things on rooted devices or custom launchers... But on stock its just sad, especially when it's never happened before the ota.

Mines running very stable.
Sent from my Galaxy Nexus using xda premium

https://code.google.com/p/android/issues/detail?id=39595&colspec=ID Type Status Owner Summary Stars
make sure you star this to take google's attention

Soldier 2.0 said:
Mines running very stable.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Same I have no issues so far!

got no issues at all ! amazing battery enhancement for me ! from 2:3 hours of screen on time (from 100-10)to 3:2 hours of screen on time from (80-1%) charging to 100 and testing it out now ! m happy and the phone always sleeps even when the screen is on i found this part funny ! i still think its a bug !

SupaDupaFly24 said:
Same I have no issues so far!
Click to expand...
Click to collapse
I have no problems too, but i have an question, in camera setting the maximum picture size should be 5 MP ?
Sent from my Galaxy Nexus using xda app-developers app

yev.gavrikov said:
I have no problems too, but i have an question, in camera setting the maximum picture size should be 5 MP ?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Yep

Flickering in Notification Bar
I have observed one strange thing on takju 4.2, If the notification window in already pulled down and and suddenly some new notification comes(like sms, email etc), all the notifcations start flickering wildly till I clear them all.
I am on stock no rooting nothing.

GNEX 4.2 default browser
Hi
Really hope someone can answer this for me, I've got a stock GNEX just got 4.2 by deleting my Google Services Framework cache and hitting update. Everything seems to be ok, but I still have the stock (blue icon) browser, I thought the default browser is chrome on 4.2. Also I don't seem to be able delete it, no biggie just annoying to have an app that I'm never going to use.
Anyway to remove it manually without rooting etc..
Many Thanks in advance to anyone that can answer this

Only issue I've noticed so far is the camera rotation is indeed very slow on my phone too.

Now, in 4.2, every notification makes my phone vibrate. This doesn't happen with earliers versions. I don't know if it is a "new feature", but I don't like it.

pookieman123 said:
Hi
Really hope someone can answer this for me, I've got a stock GNEX just got 4.2 by deleting my Google Services Framework cache and hitting update. Everything seems to be ok, but I still have the stock (blue icon) browser, I thought the default browser is chrome on 4.2. Also I don't seem to be able delete it, no biggie just annoying to have an app that I'm never going to use.
Anyway to remove it manually without rooting etc..
Many Thanks in advance to anyone that can answer this
Click to expand...
Click to collapse
According to Google : Chrome is not part of the AOSP but for the new devices such as Nexus 4,7,10 it's the default browser but old devices like Galaxy Nexus i guess for now the default browser will be the Android Browser , who knows maybe with next major release of Android that will change
As for how to delete the default browser you need root privilege to delete the app apk from the system apps using something like Root Explorer

I had three soft reboots already since yesterday (at least that I noticed, maybe more while I wasn't looking). This is a clean install (flash_all.sh from the factory image).
To hell with it, I'm going back to my beloved CM10.

Have you noticed...

Everyone wants to unlock their bootloader so they can run a custom ROM, the supposed purpose being to improve performance and gain new features. But then, once they get the new ROM on there, they keep posting about all the problems they are having, and how this, that or the other doesn't work as well as stock. After goofing with every, and I mean EVERY ROM available for the Razr M, IMHO there's absolutely no reason to use a custom ROM if you are expecting "like stock" performance. It's fun, it's addicting, it can get crazy sometimes, but don't expect it to ever be "Final". More than likely, it will be abandoned the moment a new phone or Android version comes along, and you'll be left with all those unsolved FCs and "almost works" features left hanging. Sad, really.
And then there's the whole "let's take the stock ROM from some other phone entirely and try to make it work on our phone" thing. I totally don't get that. If you like the Necco Choco-Android-o-rama's OS so well, why not just buy that phone instead? I'm just sayin'...
Rooting? That's totally different. I don't know what they do in other countries for bloatware, but Verizon certainly loads up some stinker software here in the US. Tell me, unless you're really into that sort of thing, why would the average shmoe care about Zappos? I certainly don't! And, if I wanted an app for NFL football, I'm perfectly capable of picking one from Google Play, yeah? Same with all the Amazon shtuff. Yeah I get it, advertising helps cover manufacturing costs, and all that jazz. Sure they do it to every new PC from Brand Name X too, but at least you can uninstall it. So rooting is sort of revenge for hogging my limited storage space and then limiting my ability to do anything about it.
And since I'm on this rant anyway, please... PLEASE!!! No more of this "Let's see if we can make our Android look like an iPhone" crap. Or worse, "Windows 8 Phone" crap! - Ewww! That's like taking a Jaguar and trying to make it look like a Ford Pinto... you might manage it, but who the heck would want it?
This rant has been a Public Service Announcement. The thoughts and views expressed herein are not to be considered... period. :silly:

You said it!
I linked to this from my restore where I have a commentary section.

I totally agree. Don't flash ROMs if your going to complain. Its one thing to report to the devs and quite another to ***** about it. And good on ya for the entire rant.
Sent from my XT907 using Tapatalk 4

I really hope the motox stock can be ported.
It would be a big event if he & others did it.
I thank them on each post.
http://forum.xda-developers.com/showthread.php?t=2412427

I originally rooted and unlocked my bootloader on this phone because of the screen shake issue that a Motorola introduced in an update if that didn't happen I may not of rooted the phone its stock ROM has such a good layout its no wonder so many complain. I however knew what I was getting into. Rule of thumb to new flashers backups are your friend and don't piss off the developers.

I like stock... de-bloat it and its good to go... just wish I could find something to mod the navi bar... remove the recent apps button replace it with the menu button and change color of it...
Sent from my XT907 using xda app-developers app

well, the main reason why folks are not as excited about the new ROMs, is b/c there are not any ground-breaking features on the 4.2.2 or 4.3 operating systems. When I got my first android, I had Froyo. Folks were dying to get to Gingerbread in order to vastly increase performance/battery life.
the deal with Jelly Bean, is that the upgrade from stock 4.1.2 to 4.2.2 or 4.3 is minimal at best - and the changes are mostly aesthetics (although, I read that 4.3 has better bluetooth connectivity). but mostly, 4.2.2/4.3 are primarily geared towards tablets.
the race is on now to see what KitKat can bring to current phone users.
in terms of improvements, just as radorix said, these custom ROMs eliminated the shakes that I was getting on 4.1.2. so for me, while that was not a huge deal, it's enough for me to go custom.
personally, I like the tiles layout of 4.2.2 as well as the AOKP customization, so I'll stick with that for now given that my battery life/performance is stock-like.

*claps* You said it. The Razr M has actually been the first Android phone I owned where I've kept the stock ROM. I think it does fine with 4.1.2 atm, and if I really wanted a change I'd probably just theme it.

The only thing that matters to me is stability and speed. I like a fast phone and I like to o/c, push the phone. I like to test things and try to understand its problems rather than build myself because I don't have the time. If I can find the right medium between speed and stability it becomes my dd, naturally. But stock was built for a reason and every now and then I go back to 4.1.2 because I miss some of the features. Like the far left quick settings menu and Circle Clock. Why have to find a work around to add all these features and fixes to a reimagined custom OS that causes more problems when its already working? We wouldn't have anything to work with if we didn't have the source to start at!

Couldn't agree more. I've had 9 different android devices in the past 4 years. Only ones I haven't rooted are my Sony tablet s (original, don't even get me started with their abandonment of this thing, hey let's leave bugs, make a seemingly unlockable boot loader, not share any code, abandon it after realizing all the bugs exist, then support everything we make after it) and my original nexus 7. I too came back to a stock debloated deodexed ROM for the RAZR M.
Sent from my Sony Tablet S using XDA Premium 4 mobile app

JPHoller said:
Couldn't agree more. I've had 9 different android devices in the past 4 years. Only ones I haven't rooted are my Sony tablet s (original, don't even get me started with their abandonment of this thing, hey let's leave bugs, make a seemingly unlockable boot loader, not share any code, abandon it after realizing all the bugs exist, then support everything we make after it) and my original nexus 7. I too came back to a stock debloated deodexed ROM for the RAZR M.
Sent from my Sony Tablet S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Lol. Not the only Sammy device they've dropped. Heard of the Galaxy Player 4.2?
Oh and ezknives, you do realize the menu button is completely redundant right? Considering it pops up if needed and isn't even supported/required for Holo apps
Sent from my XT907 using Tapatalk 4

sloosecannon said:
Lol. Not the only Sammy device they've dropped. Heard of the Galaxy Player 4.2?
Oh and ezknives, you do realize the menu button is completely redundant right? Considering it pops up if needed and isn't even supported/required for Holo apps
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
Not for me... with-in various apps it does not... when on different ROMs and I removed the multitasking feature and replaced it with a menu key I was able to utilize features that was other wise inaccessible... like deleting messages in Facebook app for instance... that cannot be done without a menu button or opening your browser and requesting the desktop site... I just need my menu key its never there when I need it...and I don't know what halo apps are nor use it I don't believe...
Sent from my XT907 using xda app-developers app

ezknives said:
Not for me... with-in various apps it does not... when on different ROMs and I removed the multitasking feature and replaced it with a menu key I was able to utilize features that was other wise inaccessible... like deleting messages in Facebook app for instance... that cannot be done without a menu button or opening your browser and requesting the desktop site... I just need my menu key its never there when I need it...and I don't know what halo apps are nor use it I don't believe...
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Holo means apps designed for android 4.0+.
It's the ICS+ ui style. There should be a way to access the menu without a dedicated button - either built-in or by telling the system it's a legacy app that needs the settings button to appear
Sent from my XT907 using Tapatalk 4

netizenmt said:
Everyone wants to unlock their bootloader so they can run a custom ROM, the supposed purpose being to improve performance and gain new features. But then, once they get the new ROM on there, they keep posting about all the problems they are having, and how this, that or the other doesn't work as well as stock. After goofing with every, and I mean EVERY ROM available for the Razr M, IMHO there's absolutely no reason to use a custom ROM if you are expecting "like stock" performance. It's fun, it's addicting, it can get crazy sometimes, but don't expect it to ever be "Final". More than likely, it will be abandoned the moment a new phone or Android version comes along, and you'll be left with all those unsolved FCs and "almost works" features left hanging. Sad, really.
Click to expand...
Click to collapse
Meh. I disagree. I've been running CM since it went official and I haven't had any complaints. I experience much-better-than-stock performance and battery life, plus it is way more customizable. I love it!

allc0re said:
Meh. I disagree. I've been running CM since it went official and I haven't had any complaints. I experience much-better-than-stock performance and battery life, plus it is way more customizable. I love it!
Click to expand...
Click to collapse
I just tried it again. Froze on reboot, wouldn't let me into recovery, same BS as all the 4.3 versions. And I wrote the book, well thread, on how to install it, so yeah I wiped etc.
Sent from my XT907 using Tapatalk 4

i'm enjoying better than stock performance on the stable 4.2.2 branch, and i built a custom kernel for CM10.1 for better performance. I tried the 'stock' life and its boring lol. The custom ROM features and better performance are what makes it worth it in my view. 4.3 will be even better as work is continually being done on it, and it hasn't been out that long. Also, I think we need to give appreciation to the devs for giving us options as far as what we can run on this phone compared to being stuck with only one choice.

CM is getting good. Recently the "display freezing" issue got fixed, also more fixes for cardock audio and wifi. It simply takes a while to get it all done properly (with that what's left is SIM I/O and HDR (works with Moto X camera application)).
@netizenmt: Booting to recovery is not affected by the ROM you have installed, so you screwed up the installation at some point.

Skrilax_CZ said:
CM is getting good. Recently the "display freezing" issue got fixed, also more fixes for cardock audio and wifi. It simply takes a while to get it all done properly (with that what's left is SIM I/O and HDR (works with Moto X camera application)).
@netizenmt: Booting to recovery is not affected by the ROM you have installed, so you screwed up the installation at some point.
Click to expand...
Click to collapse
Would you offer a build for a Bluetooth phone user that has the SD swap working?
One that might quiet this thread?

netizenmt said:
I just tried it again. Froze on reboot, wouldn't let me into recovery, same BS as all the 4.3 versions. And I wrote the book, well thread, on how to install it, so yeah I wiped etc.
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
There are a few tricks to getting 4.3 installed and running but it will never happen if u just quite and go back to stock before u get it up and running correctly. I had a terrible time getting 4.3 to boot, keyboard forcing close, stability etc but I figured all that out and wouldn't think of going back to stock. The amount and way if partions the internal drive alone will keep me from ever going back to stock.
Sent from my XT907 using Tapatalk 2

stanlalee said:
There are a few tricks to getting 4.3 installed and running but it will never happen if u just quite and go back to stock before u get it up and running correctly. I had a terrible time getting 4.3 to boot, keyboard forcing close, stability etc but I figured all that out and wouldn't think of going back to stock. The amount and way if partions the internal drive alone will keep me from ever going back to stock.
Sent from my XT907 using Tapatalk 2
Click to expand...
Click to collapse
You actually just made my whole point.
While it's cool you had time, patience, skill and effort to resolve your issues with 4.3, that's not the point of this thread. So do I. The point is, if you think you're going to slap one of these ROMs on and everything is going to work like stock, forget it. If that's what someone expects, they should stick to stock.
Sent from my XT907 using Tapatalk 4