Hi all,
I've just signed up to let you know this:
I'm using Sabsa Prime V6.0 and discovered a graphical issue.
The buttons on the right of the dialer screen (wich appears when you have to typ your pin) are a little bit smaller then the others..
How to fix this? It's not the worst thing on earth of course but it would be nice to see it fixed!
Take a look at the attachment..
Hmm... Doesn't happen on mine. I'm on the same ROM.. Dialer looks fine.
Maybe its because you're on a different language?
Anyway, I hate to be the one to point this out but wrong section buddy. This thread should've been in the Q&A.
Edit: In anycase, a new version v6.5 is out with a fixed dialer. Flash that one over your current ROM and see if it fixes it.
He does not mean the phone dialer but the number screen that appears when you need to type your password to unlock your phone/screen. It happens to me as well and I'm on sabsa prime 6.5. I would like to see it fixed if it's even possible.
Sent from my HTC Desire HD
narvinye said:
He does not mean the phone dialer but the number screen that appears when you need to type your password to unlock your phone/screen. It happens to me as well and I'm on sabsa prime 6.5. I would like to see it fixed if it's even possible.
Sent from my HTC Desire HD
Click to expand...
Click to collapse
Yes, that´s what I mean, but since I´m new here I´m not able to post this kind of 'graphic bug' in the official Sabsa Prime development thread :S
nielshouten said:
Yes, that´s what I mean, but since I´m new here I´m not able to post this kind of 'graphic bug' in the official Sabsa Prime development thread :S
Click to expand...
Click to collapse
It haa been mentioned in the dev forum. Happens for me as well.
Sent from my HTC Desire HD using xda app-developers app
nielshouten said:
Hi all,
I've just signed up to let you know this:
I'm using Sabsa Prime V6.0 and discovered a graphical issue.
The buttons on the right of the dialer screen (wich appears when you have to typ your pin) are a little bit smaller then the others..
How to fix this? It's not the worst thing on earth of course but it would be nice to see it fixed!
Take a look at the attachment..
Click to expand...
Click to collapse
Try version 6.5 and perform a clean install , I use the same ROM and I don't have this issue
waelwa said:
Try version 6.5 and perform a clean install , I use the same ROM and I don't have this issue
Click to expand...
Click to collapse
I'm using 6.5 and I did a clean install and have this graphical error.
Sent from my HTC Desire HD
I´m using Version 6.5 and my dialer looks perfect.
If only you were paying attention when you looked the attached image. Look again it is not the dialer..
Sent from my HTC Desire HD
Related
Hi there,
I'm a it tech with skills in Linux, OSX and Windows. I'm an amateur cook, with more of a take apart and figure out why things tick kinda cook, who wants to help.
I own a HTC wildfire, and have tested WildPuzzle, upto v7.3. I am in the process of cooking a froyo Rom for the wildfire. Based on a combination of the Chinese Rom, puzzle Rom and the open source Android sdk.
I guess I'm more just putting forth both my skills and my Rom, ASAP.
Just here to help really.
Peace
Sent from my HTC Wildfire using XDA App
can you help me?
Cant wait to see the chefs special
I don't have a ps3 but u can see if there's anything I can do once I get home.
Chefs special XD I like that.
Sent from my HTC Wildfire using XDA App
Elbie said:
I don't have a ps3 but u can see if there's anything I can do once I get home.
Chefs special XD I like that.
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
thanks in advance
Elbie said:
Hi there,
I'm a it tech with skills in Linux, OSX and Windows. I'm an amateur cook, with more of a take apart and figure out why things tick kinda cook, who wants to help.
I own a HTC wildfire, and have tested WildPuzzle, upto v7.3. I am in the process of cooking a froyo Rom for the wildfire. Based on a combination of the Chinese Rom, puzzle Rom and the open source Android sdk.
I guess I'm more just putting forth both my skills and my Rom, ASAP.
Just here to help really.
Peace
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
Would you mind solving the bug in clockworkmod which means that when the wildfire is turned off and charging, the light remains of even after unplugging the charger (to get the light to go out you need to remove the battery)
I must admit I haven't witnessed that bug myself. Could you tell me how you came about this bug?
Sent from my HTC Wildfire using XDA App
Elbie said:
I own a HTC wildfire, and have tested WildPuzzle, upto v7.3. I am in the process of cooking a froyo Rom for the wildfire. Based on a combination of the Chinese Rom, puzzle Rom and the open source Android sdk.
Click to expand...
Click to collapse
Hi, danne_jo's rom (v8 - froyo based) is based on the chinese rom itself. Mixing stuff from v7.x and v8 can provide wierd bugs.
- You might get in touch with HCDR.jacob though, working on an overclock module for wildfire, he made some interresting progress (read that somewhere).
- You can also work on the psfreedom, which seems to disable some useful features on wildfire (such as wifi) but I guess it's kinda related as the wifi hardware might be plugged on the usb chip.
- Or you could dive in mods, and try to port the rotary lockscreen to wildfire (I tried, it works great but I can't find where to "resize" the layout, vanilla lockscreen looks too big, rotary lockscreen is out of the screen)
edit: you might want as well to look at useful modding/tweaking tools such as apktool / (bak)smali.
hey elbie any answer for my problem
Help
Sent from my HTC Wildfire using XDA App
Sympnotic said:
Hi, danne_jo's rom (v8 - froyo based) is based on the chinese rom itself. Mixing stuff from v7.x and v8 can provide wierd bugs.
- You might get in touch with HCDR.jacob though, working on an overclock module for wildfire, he made some interresting progress (read that somewhere).
- You can also work on the psfreedom, which seems to disable some useful features on wildfire (such as wifi) but I guess it's kinda related as the wifi hardware might be plugged on the usb chip.
- Or you could dive in mods, and try to port the rotary lockscreen to wildfire (I tried, it works great but I can't find where to "resize" the layout, vanilla lockscreen looks too big, rotary lockscreen is out of the screen)
edit: you might want as well to look at useful modding/tweaking tools such as apktool / (bak)smali.
Click to expand...
Click to collapse
Have a look at the lockscreen thats in the openfire rom, is the perfect size.
Elbie said:
I must admit I haven't witnessed that bug myself. Could you tell me how you came about this bug?
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
It also happens with wildpuzzle rom... It's triggerred when you plug charger in and you turn off your phone. You won't be able to turn on the phone unless you reseat the battery.
Sent from my HTC Wildfire using XDA App
hector28 said:
It also happens with wildpuzzle rom... It's triggerred when you plug charger in and you turn off your phone. You won't be able to turn on the phone unless you reseat the battery.
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
Doesn't happen to me at all, i've used both v7.3.1 and v8
hi guys, i go in recovery mode ,then in advanced,i click on report error an this is the answer
/tmp/recovery.log/was copied to/sd card/clockworkmod/recovery.log./please open rom manager to report the issue.
wath's wrong?
When rooted turn the phone off and put it on charge. If you take it off charge the light will remain
Sent from my HTC Wildfire using XDA App
It's asking you to open Rom manager to sent the report since clockworkmod has no WiFi access
Sent from my HTC Wildfire using XDA App
brilldoctor said:
When rooted turn the phone off and put it on charge. If you take it off charge the light will remain
Click to expand...
Click to collapse
Now this I can replicate, however I don't need to remove the battery to power on. Also noticed that when off, if you plug it into a pc, adb will notice recovers there. Looks Like it doesn't truly turn off. Although I believe this is covered in another thread.
I have not had a chance yet to test
Many things as my boilers sprung a leak and taken out part of my ceiling.
Will be back to testing thing asap.
I have however been trying to mix up a few things with my portable kitchen
So far I notice the power issue doesn't present itself with the Chinese Rom. But it does with my chefs special. Which atm is majoritivly Chinese Rom and android source. I am using HTC Facebook/Twitter from puzzle v7.3 and its ok, buggy, lots of fc with lots if things, but... Blazing fast
Hopefully, once boiler etc fixed, I can release an alpha Rom.
Peace
Sent from my HTC Wildfire using XDA App
If it helps my wildfire has a amtel panel
It causes crash pressing the trackball using non-htc'ish parts
is there anyway to view sent item , inbox, etc.. rather than all messages for my hp sms?
hp sms?
Im a Handcent user, havent found a single sms app that works as well.. Plus I really dont like the HTC stock sms app.
So Sorry I havent been around much. My Boiler leaked taking out half my ceiling... not good.
Have been cooking on my portable kitchen though (Netbook running OSX Sow Leopard with a virtual Ubuntu Kitchen)
So far I have a 2.2 ROM...BUT....It's about as stable as jelly XD
Will be as quick as I can.. but creation takes it's time.
Peace
I would love a stock ROM without any customizations based on the latest sources dropped in AOSP, would anyone be kind enough to build me one? I'm sure I'm not the only one to want this. I don't got the kind of net or computer to compile myself (the source download itself is 6GB which is a bit difficult for me at the moment).
If you're rooted I think this is what you want http://forum.xda-developers.com/showthread.php?t=1905961
Sent from my Nexus 7 using xda premium
I haven't look for just a stock build of that, but haven't seen one anywhere. The above link is just for drivers/binarys and isn't a full ROM.
Not sure but I think that is the major difference between the two?
Sent from my Nexus 7 using xda premium
Gigabitex2 said:
Not sure but I think that is the major difference between the two?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
This... it is only the new drivers.
Sent From My Toro+ via White Tapatalk
Be wary though, I think flashing the drivers mixes things up behind the scenes, for example I'm always running bug less beast for stability and I after I flashed the drivers everything seemed fine, till I went to the hospital and well they got free WiFi which would always connect properly, u just have to open a webpage to accept terms, conditions and then u can use their WiFi, well the other day (still on bugless beast) I tried to connect it would not obtain IP address what so ever so I couldn't even get to the splash screen to accept conditions and activate the WiFi, so I thought hmm I been here before plenty of times using my n7 with the mentioned ROM and had no issues with their WiFi then I started to think it was them and WiFi must be screwed up at the moment, and well that never changed my phone was fine so I decided f-it reflash the ROM on my n7 and boom that was the fix, anyways go download the latest bugless beast he updated to latest jro03r and is completely stock aosp with a nice reboot menu and camera/lock screen shortcut are included as well
Sent from my Nexus 7 using xda app-developers app
Hi,
Anyone knows if this new drivers solve the black line problems that appears for less than a second using soft or white backgrounds like tapatalk and chrome?
Thank you.
luzifers said:
Hi,
Anyone knows if this new drivers solve the black line problems that appears for less than a second using soft or white backgrounds like tapatalk and chrome?
Thank you.
Click to expand...
Click to collapse
Nope. Still there.
Sent from my Nexus 7
Ok thx,
We'll be waiting for the next update from Google to solve this little problem.
I built the android-4.1.1_r6 branch a few hours ago, and have it running now. It has nothing
installed and is really useless as-is, I will upload it if you really want it.
EDIT:
I just went ahead and uploaded it
http://www.mediafire.com/?9yivy1dh53dhnco
flash system.img, boot.img with fastboot
boot into recovery wipe data/factory reset
install Nexus7-Binary-Update-JRO03R.zip
or it wont work.
install gapps-jb-20120726-signed.zip if you want
any Google services.
I also uploaded ClockworkMod touch 6.0.1.4 for grouper
http://forum.xda-developers.com/showthread.php?t=1913562
JRO03S.
I use that and it work very well. I don't see any difference between r
This and the original D
Sent from my Nexus 7 using xda app-developers app
I did not see any diff ether, and went back to D, finely having a device that I can
build the OS from official source is nice though.
capoooro said:
http://forum.xda-developers.com/showthread.php?t=1913562
JRO03S.
I use that and it work very well. I don't see any difference between r
This and the original D
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Hi
I'm wondering if anyone can help me out with this. I have the desire c (branded to 3 and rooted) it has worked great for awhile but recently the screen keeps going into landscape and getting stuck there (even when holding it up right) I've tried turning auto rotate off but it still happens usually a restart fixes it for awhile but then it starts again. I found a app on the market that can force it back into portrait but then I can't make some apps full screen like YouTube. I've tried a factory reset a few times both through settings and by pushing power and volume up but not long after it starts happening again.
Anyone have any idea why this is happening?
Thanks.
Sent from my HTC Desire C using xda app-developers app
Maybe you should backup your current rom, and then install a custom one maybe some files relating to the sensors could be corrupt.
Thanks i may try using a generic rom to see if it fixes it. What's the best way to back up my current rom? Gonna need to go back to it if I have to sent it off to get fixed.
Sent from my HTC Desire C using xda app-developers app
Well I tried nameless Rom but it didn't fix it so looks like I'm gonna have to send my phone off for repair
Sent from my HTC Desire C using xda app-developers app
Try calibrating your sensors.
Sent from my Texus 4 toaster
Thanks I tried that but no luck the odd thing is the sensor seems to work cause I can play that game where you control the ball with the sensor. But its started doing other stuff now like it keeps turning the screen on on its own and putting phone on loud speaker and pausing music etc.
Sent from my HTC Desire C using xda app-developers app
Weird... The game works, but the accelorometer doesn't work at other places
Sent from my Texus 4 toaster
My wife's Desire C has the same problem. Stuck in landscape most of the time. Screen turning on, phonecalls sometimes suddently go to speaker. Sensors are working fine if you ask me.
I was trying to root it when I read this topic, I still might try a custom rom though.
Glad I'm not the only one who had this problem. Maybe there's a fault with some of the handsets or something.
I gave up and sent mine off for repair now.
Sent from my HTC Wildfire S A510e using xda app-developers app
andrewtjb said:
Well I tried nameless Rom but it didn't fix it so looks like I'm gonna have to send my phone off for repair
Sent from my HTC Desire C using xda app-developers app
Click to expand...
Click to collapse
Heyyy!!! Did u find any solution for your problem. My phone is also starting to behave in the same way....
I think I found the solution. It seems like the problem is with HTC's ROM based on ICS 4.0 and 4.0.4. I tried just about any ROM based on ICS (stock and custom) with any kernel combination and the problem repeats itself.
Flashed CM 10.1 and the problem is gone.
s1m0n.lfs said:
I think I found the solution. It seems like the problem is with HTC's ROM based on ICS 4.0 and 4.0.4. I tried just about any ROM based on ICS (stock and custom) with any kernel combination and the problem repeats itself.
Flashed CM 10.1 and the problem is gone.
Click to expand...
Click to collapse
wich rom do you use, what CM 10.1 based rom?
mareeck said:
wich rom do you use, what CM 10.1 based rom?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2265060
All others are sh**y unmaintained ports with tons of bugs that are never going to be fixed.
s1m0n.lfs said:
http://forum.xda-developers.com/showthread.php?t=2265060
All others are sh**y unmaintained ports with tons of bugs that are never going to be fixed.
Click to expand...
Click to collapse
that's CM10 not CM10.1 there is a big diference betwin them, but any way i'm glad that you have solved the problem this way
i am also having same issu
Don't know how to put this, whenever I slide pages on my nexus 7, the page pulls back. Removing widgets seems to make it better. Anyone else having this issue? Sorry if this thread already exists. If it does can you direct me?
Nexus7 on 4.2
Sent from my Nexus 7 using xda app-developers app
Would u happen to be using Nova launcher?
Sent from my Nexus 7 using Tapatalk HD
dadoc04 said:
Would u happen to be using Nova launcher?
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
If I understand the original poster correctly then this happens to me too.
And it also happens on stock launcher...
This happens on stock launcher. Its irritating to say the least.
Sent from my Nexus 7 using xda app-developers app
MauriceZ said:
This happens on stock launcher. Its irritating to say the least.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
So is it like this post describes it?
Trying to determine whether we are talking about the same thing here
http://forum.xda-developers.com/showthread.php?p=33921887
Sent from my Nexus 7 using Tapatalk 2
DanteGR said:
So is it like this post describes it?
Trying to determine whether we are talking about the same thing here
http://forum.xda-developers.com/showthread.php?p=33921887
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Yes, thanks!
MauriceZ said:
Yes, thanks!
Click to expand...
Click to collapse
Np my friend
I'm having the exact same thing
DanteGR said:
Np my friend
I'm having the exact same thing
Click to expand...
Click to collapse
Having the same issue as well.
Is this thing software related ?
I am kind of worried as this device is known for his smoothness !
Meg4mi said:
Having the same issue as well.
Is this thing software related ?
I am kind of worried as this device is known for his smoothness !
Click to expand...
Click to collapse
I hope it's software relayed...
Anyway, does the following video show what u guys are also experiencing??
It is the best one i found reproducing our problem..
http://www.youtube.com/watch?v=98mdDwhyWPg
DanteGR said:
I hope it's software relayed...
Anyway, does the following video show what u guys are also experiencing??
It is the best one i found reproducing our problem..
http://www.youtube.com/watch?v=98mdDwhyWPg
Click to expand...
Click to collapse
That is exactly the problem i have got.
BTW i have tried to use go launcher ex.
It seems to solve the problem for me.
Can you guys try it ? and confirm my thoughts ?
Meg4mi said:
That is exactly the problem i have got.
BTW i have tried to use go launcher ex.
It seems to solve the problem for me.
Can you guys try it ? and confirm my thoughts ?
Click to expand...
Click to collapse
Go launcher ex is the next thing i am trying then mate.
Will get back to you with impressions asap
Sent from my JellyBean Renovated HTC One X Quad-Core Beast
DanteGR said:
I hope it's software relayed...
Anyway, does the following video show what u guys are also experiencing??
It is the best one i found reproducing our problem..
http://www.youtube.com/watch?v=98mdDwhyWPg
Click to expand...
Click to collapse
Yes this is what I mean but much worse in my case. Removing the widgets solved it though in my case.
Meg4mi said:
That is exactly the problem i have got.
BTW i have tried to use go launcher ex.
It seems to solve the problem for me.
Can you guys try it ? and confirm my thoughts ?
Click to expand...
Click to collapse
Go launcher Ex seems to do the trick my friend. So far so good!
Sent from my Nexus 7 using Tapatalk 2
DanteGR said:
Go launcher Ex seems to do the trick my friend. So far so good!
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
So this is proving that the issue is software related ^^.
Meg4mi said:
So this is proving that the issue is software related ^^.
Click to expand...
Click to collapse
Yes but i will keep monitoring go launcher's behavior just to be sure it doesn't happen again
Many thanks for proposing this!
Sent from my JellyBean Renovated HTC One X Quad-Core Beast
DanteGR said:
Yes but i will keep monitoring go launcher's behavior just to be sure it doesn't happen again
Many thanks for proposing this!
Sent from my JellyBean Renovated HTC One X Quad-Core Beast
Click to expand...
Click to collapse
You are welcome !
But still weird that only few people have this issue ?
What rom and android version are you running ?
I am running rooted stock 4.2 with multi-user (GF^^).
To recap i have got the problem with :
- go launcher hd for pad
- nova launcher
- stock launcher
on the other hand no issue with go launcher ex.
I must add that i feel the UI very heavy.
when i am web browsing, pinch to zoom is not as reactive as on my one X.
Same thing about scrolling over a page.
Are you guys experiencing this aswell ?
I have this issue, and its VERY annoying.
I on the other hand, DON'T THINK ITS AN ISSUE! I think this is just normal.
The only reason we notice it, is we have devices that are much more responsive.
I have a HTC One X, and can literally flick the screen and it goes where I want it, the Nexus is more of a drag than a flick.
Wilks3y said:
I have this issue, and its VERY annoying.
I on the other hand, DON'T THINK ITS AN ISSUE! I think this is just normal.
The only reason we notice it, is we have devices that are much more responsive.
I have a HTC One X, and can literally flick the screen and it goes where I want it, the Nexus is more of a drag than a flick.
Click to expand...
Click to collapse
+1
Same for my S3 vs. the N7.
This could probably be "fixed" if the Lauchers were able to distinct a "flick" from a "swipe". On the phone I touch much more pixels with one flick, than on the tablet , due to its smaller screen.
Wilks3y said:
I have this issue, and its VERY annoying.
I on the other hand, DON'T THINK ITS AN ISSUE! I think this is just normal.
The only reason we notice it, is we have devices that are much more responsive.
I have a HTC One X, and can literally flick the screen and it goes where I want it, the Nexus is more of a drag than a flick.
Click to expand...
Click to collapse
I agree with what you say, but it seems there is a problem with the inertia.
Look at those screenshot https://www.evernote.com/shard/s64/...33f1f9e7d013/dd9030c957c51b5f1bc1fee19803038f
You'll see that the purple line go back instead of going straight. It acts as if the screen was too sensitive and was taking into account the fact that you lift your finger off the screen.
If you have an android phone, try to swipe with trace enable. You'll notice that the purple line go straight as it should.
For me at least on my one x, the pruple line (inertia) go straight and i have no problem when swiping through home screen.
Edit : Just to let you know. I have tried Apex launcher and it appears there is no "pull back" problem. Actually it is luquid smooth^^
I don't think it is a problem of launcher, as you can see on the screenshot I was not on the home app that the launcher is, but in chrome.
It happens no matter what app you are on, as I think it is either related to software or hardware.
But I must admit I feel like it is hardware.
there are a lot off topic conversations going on the official Cyanogenmod ROM thread that have nothing to do with CM development and it'd be better for the community if we keep all those conversations..questions about CM in this thread..
-
-
-
Nice. Can't believe no one thought of this earlier.
Maybe a stupid question but I can't find it online.
What's the difference between Expirimental, nightlies, etc?
And what's the order of al these?
blackroseMD1 said:
Nice. Can't believe no one thought of this earlier.
Click to expand...
Click to collapse
I mentioned it days ago in the Development thread.
I didn't start one because I can't keep the Original post updated.
Glad someone else who can started a thread.
Donstil said:
Maybe a stupid question but I can't find it online.
What's the difference between Expirimental, nightlies, etc?
And what's the order of al these?
Click to expand...
Click to collapse
Experimental is usually a build started by a dev to test changes made
Nightlies are builds scheduled every night regardless if changes have been made
Milestones have all the big bugs ironed out and signify overcoming big developmental hurdles
RC (release candidate) is what it sounds like. It's a build that has the potential to be stable if no further bugs appear
Stable has all the bugs worked out.
Do we still have the Black screen during calls? I swore it worked this morning then all my calls went black. Didn't realize how important buttons were on calls to me until it happened. I'm on the latest nightly
Sent from my HTC One using xda premium
Anybody where to find their photos after coming from a sense rom...?
Sent from my HTC One using xda premium
dcowboys2184 said:
Anybody where to find their photos after coming from a sense rom...?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Data/media/dcim
Sent from my HTC One using xda premium
XSafire said:
Experimental is usually a build started by a dev to test changes made
Nightlies are builds scheduled every night regardless if changes have been made
Milestones have all the big bugs ironed out and signify overcoming big developmental hurdles
RC (release candidate) is what it sounds like. It's a build that has the potential to be stable if no further bugs appear
Stable has all the bugs worked out.
Click to expand...
Click to collapse
Oké thanks:good:
joshyy_rey said:
Data/media/dcim
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Nothing there... when flashed bank on sense all my photos are there but when on a aosp rom nothing appears
Sent from my HTC One using xda premium
dcowboys2184 said:
Nothing there... when flashed bank on sense all my photos are there but when on a aosp rom nothing appears
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
That's where mine went. Just copy everything you need to your desktop and drop where needed after you flash cm
Sent from my HTC One using xda premium
How's the battery compared to Sense 5?
F4M0U569 said:
How's the battery compared to Sense 5?
Click to expand...
Click to collapse
My personal experience yields about 25% less battery life. If course ymmv
Sent from my HTC One using xda premium
Has anyone yet compared the camera quality of CM and Stock ROM?
fka said:
Has anyone yet compared the camera quality of CM and Stock ROM?
Click to expand...
Click to collapse
Stock is better as it relies on sense framework for image processing. So, optimised for the one hw
Sent from my HTC One using xda premium
lolrenx said:
Stock is better as it relies on sense framework for image processing. So, optimised for the one hw
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Will there be any chance of including the regarding parts when we get the official 4.2 update from HTC?
fka said:
Will there be any chance of including the regarding parts when we get the official 4.2 update from HTC?
Click to expand...
Click to collapse
No idea. I'd say no since someone would have to reverse engineer the HTC software. I don't see that happening, but it's just a guess.
Sent from my HTC One using xda premium
lolrenx said:
No idea. I'd say no since someone would have to reverse engineer the HTC software. I don't see that happening, but it's just a guess.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Too bad... Hopefully someone will create some kind of AOSP-Stock-Hybrid-ROM.
I will ask in Q&A if somebody is already at it, if not i will see if i can spare some time to get involved into Android developing and try to create one...
Issues
Apologies if I have missed anything where this has been covered before. I have read pretty much every page of the dev thread. I have been an xda user for years but only just opened an account to ask a couple of questions.
I can report the proximity/ blank screen during calls still exists with 18052013 nightly. Not that I saw anything about this in the change log.
Can I ask if this is any issue for everybody with the HTC One or just some? (I have the international version)
Is there a fix in the works for this?
It looks like the notification LED colour cannot be changed right now. I have tried a couple of colours but green is the only one that works.
I noticed something else small. The facebook app from the Sense 5.0 original ROM had the option to "sync only existing contacts" but with this ROM we have only "sync" which syncs all contacts. Not sure if this is an easy fix but it would be nice to have back. I do understand none of the "sense" apps or tools are available in AOSP.
Thanks for the hard work and helps everybody
Probably kind of random, but anyone have any luck with the One/CM 10.1 syncing with a Jawbone Up (a fitness monitor bracelet)? It worked fine on stock, but refuses to sync since moving to CM. I'm on the latest nightly. Any info appreciated!
Sent from my HTC One using xda app-developers app