is there a way to mod the camera flash so it lets me use it even if the battery is really really low...I want to set the threshhold at 0 percent...sometimes...I just need to take a pic...and 20 percent is more than enough for one quick flash for a pic.
seansk said:
is there a way to mod the camera flash so it lets me use it even if the battery is really really low...I want to set the threshhold at 0 percent...sometimes...I just need to take a pic...and 20 percent is more than enough for one quick flash for a pic.
Click to expand...
Click to collapse
anyone? please???
seansk said:
anyone? please???
Click to expand...
Click to collapse
When does it prevent you from using the flash? I've used mine at less than 20% but have had wifi, gps and data connection turned off. I wonder if unchecking the power saver and efficiency boxes would help?
EDIT: Okay, I see what you mean. I finally got it to say the flash couldn't be used because the battery level is too low. I turned off power saving and it still didn't work. I tried ProCapture which I like a lot because it doesn't compress the images thus better quality. It has a "torch" option on its flash menu so I tried that. The flash stays on continuously in that mode, even with a low battery. I took a shot in total darkness and it didn't seem to work. the flash was on but no picture? Maybe with some light it would work? ProCapture is free to try so you might want to try it to see if that would work under normal night conditions. I guess it won't work in total darkness like the auto flash will.
Another edit: I noticed that the flash was disabled right at 15% so I did some searching and found this: With root explorer (or any rooted file explorer), go to sys/camera_led_status/low_cap_limit. There you will find the number 15 for 15%. I tried to change this to 5 but the file is locked and I don't know enough to unlock it, rename it and then change it through adb. I think I read that you can't do this through root explorer. Maybe someone with knowledge of how to do this will know how to do it. I'm sure it is relatively simple and a zip file could even be written to change it. At least we now know where the setting is!
frodoboy said:
When does it prevent you from using the flash? I've used mine at less than 20% but have had wifi, gps and data connection turned off. I wonder if unchecking the power saver and efficiency boxes would help?
EDIT: Okay, I see what you mean. I finally got it to say the flash couldn't be used because the battery level is too low. I turned off power saving and it still didn't work. I tried ProCapture which I like a lot because it doesn't compress the images thus better quality. It has a "torch" option on its flash menu so I tried that. The flash stays on continuously in that mode, even with a low battery. I took a shot in total darkness and it didn't seem to work. the flash was on but no picture? Maybe with some light it would work? ProCapture is free to try so you might want to try it to see if that would work under normal night conditions. I guess it won't work in total darkness like the auto flash will.
Another edit: I noticed that the flash was disabled right at 15% so I did some searching and found this: With root explorer (or any rooted file explorer), go to sys/camera_led_status/low_cap_limit. There you will find the number 15 for 15%. I tried to change this to 5 but the file is locked and I don't know enough to unlock it, rename it and then change it through adb. I think I read that you can't do this through root explorer. Maybe someone with knowledge of how to do this will know how to do it. I'm sure it is relatively simple and a zip file could even be written to change it. At least we now know where the setting is!
Click to expand...
Click to collapse
Yes thats exactly what I did in root explorer in sys/camera_led_status/low_cap_limit, I set it to 5, 1, 0, did not make any difference. Also Its retarded that you cannot use flash while you're in a call....if you talking to someone and trying to take a picture it says you cannot use flash since you're in a call....wtf does that have to do with the flash!!! There should be a file somewhere in the sense UI system to change these settings, If anyone has found anything please share...or if you can think of something please share as well...
I actually like the dialer and contact aspect of sense UI and how it integerates and automatically finds linked friends, how it updates friends status in facebook and twitter, (although they still need to integrate google plus)...all the other stuff of sense I do not like...I've changed to ADW ex...and widget locker...
I doubt there's a way to get that stuff with a senseless rom since its so integerated into the system...If there is I would flash another rom in a sec and just install that aspect of sense....
so apparently I can't use flash under 20% battery...under a certain temperature and when I'm in a call...So basically don't use flash....lol....I messed around with files under sys/camera_led_status which I believe controls temperature and battery limitations and also /sys/android_camera_awb_cal which I believe limits flash while you're in a call...I backed up deleted the directories and rebooted but they came right back...is this part of the kernel...I believe this requires S-off because I am unable to change this part of the system...or perhaps someone can do a quick kernel mod and take off all those limitations...
I got a better one for you.
Turn on the wireless access point feature, activate the camera and try to use the flash.
Binary100100 said:
I got a better one for you.
Turn on the wireless access point feature, activate the camera and try to use the flash.
Click to expand...
Click to collapse
you gotta be kidding me!!!!
question 1. Are the other roms the same?? I"m unlocked and rooted but on stock rom. do senceless, beastmod or revolution have the same problem...I'm guessing they would since they use the same camera apk...or maybe not, If not i'm flashing to something else RIGHT NOW.
questions 2. are we ever going to see CM9 on the amaze....screw sense I want ICS AOSP asap...
seansk said:
so apparently I can't use flash under 20% battery...under a certain temperature and when I'm in a call...So basically don't use flash....lol....I messed around with files under sys/camera_led_status which I believe controls temperature and battery limitations and also /sys/android_camera_awb_cal which I believe limits flash while you're in a call...I backed up deleted the directories and rebooted but they came right back...is this part of the kernel...I believe this requires S-off because I am unable to change this part of the system...or perhaps someone can do a quick kernel mod and take off all those limitations...
Click to expand...
Click to collapse
As I understand it, you tried to change the value to 0, 1, 5 and it still didn't work. If you looked at the file, it was still set to 15 right? I think you have to unmount the system, then pull it from your phone to your computer, alter the file and then push it back to the phone and remount the system. I have no idea how to do that. Binary is pretty good at writing little zips to do that sort of thing. I don't know if permanently changing that value will do anything though. I do know that root explorer says it changes the file but it doesn't.
frodoboy said:
As I understand it, you tried to change the value to 0, 1, 5 and it still didn't work. If you looked at the file, it was still set to 15 right? I think you have to unmount the system, then pull it from your phone to your computer, alter the file and then push it back to the phone and remount the system. I have no idea how to do that. Binary is pretty good at writing little zips to do that sort of thing. I don't know if permanently changing that value will do anything though. I do know that root explorer says it changes the file but it doesn't.
Click to expand...
Click to collapse
I tried changing this by root explorer as well. The directory already says that it's R/W so I tried changing these values. As a result I was unable to force the changes either. I'm curious if something else changes the values back. Perhaps the camera app itself? I have no idea why the directory is set to r/w. However if you check any custom rom you will not see a /sys directory in there which makes me believe that it is in fact kernel related. That being said you would have to decompile the kernel itself, edit those values and reflash the kernel again. I might be able to do this for you however since everyone seems to have a different kernel and suffer from ORD (obsessive rom flashing disorder) I would find the work as pointless. My suggestion is to request it from your favorite developer for future kernels.
Binary100100 said:
I tried changing this by root explorer as well. The directory already says that it's R/W so I tried changing these values. As a result I was unable to force the changes either. I'm curious if something else changes the values back. Perhaps the camera app itself? I have no idea why the directory is set to r/w. However if you check any custom rom you will not see a /sys directory in there which makes me believe that it is in fact kernel related. That being said you would have to decompile the kernel itself, edit those values and reflash the kernel again. I might be able to do this for you however since everyone seems to have a different kernel and suffer from ORD (obsessive rom flashing disorder) I would find the work as pointless. My suggestion is to request it from your favorite developer for future kernels.
Click to expand...
Click to collapse
crap I wish I was a developer!!! instead I had to go and fix teeth and become a dentist!!! but I'm very much into electronics. Is there a book I can read to start developing?
btw where do I post the request? in development or general?
seansk said:
crap I wish I was a developer!!! instead I had to go and fix teeth and become a dentist!!! but I'm very much into electronics. Is there a book I can read to start developing?
btw where do I post the request? in development or general?
Click to expand...
Click to collapse
I would suggest in the forum that consists of the kernel that you are using.
Example:
If you have QuikSense then post the request in the QuikSense forum or PM the developer (in this case xboarder56) directly.
If you use Faux's kernel then post it in that thread.
No need to start a new thread for a request. However if you feel that it is absolutely necessary do it in General because the Development section is not really a section mod requests.
Binary100100 said:
I tried changing this by root explorer as well. The directory already says that it's R/W so I tried changing these values. As a result I was unable to force the changes either. I'm curious if something else changes the values back. Perhaps the camera app itself? I have no idea why the directory is set to r/w. However if you check any custom rom you will not see a /sys directory in there which makes me believe that it is in fact kernel related. That being said you would have to decompile the kernel itself, edit those values and reflash the kernel again. I might be able to do this for you however since everyone seems to have a different kernel and suffer from ORD (obsessive rom flashing disorder) I would find the work as pointless. My suggestion is to request it from your favorite developer for future kernels.
Click to expand...
Click to collapse
Thanks Binary. You are sooooo smart!!
Flash limitation is controlled by kernel... Not sure why HTC decided to do that, but I can easily change this value in my next release from 20% to 10% or 5%.....
Of course if you decide to use the stock kernel, there's nothing much you can do about it... It is hardcoded in the kernel code.
Happy New Year!
faux123 said:
Flash limitation is controlled by kernel... Not sure why HTC decided to do that, but I can easily change this value in my next release from 20% to 10% or 5%.....
Of course if you decide to use the stock kernel, there's nothing much you can do about it... It is hardcoded in the kernel code.
Happy New Year!
Click to expand...
Click to collapse
Thanks
I think 5 percent is reasonable...also can you change the limitations for temperatureand also take off limitations when making a call and using wifi hotspot...the phone does not allow to take flash while its in low temp, when making a call or when using wifi tethering/hotspot.....thanks faux
seansk said:
Thanks
I think 5 percent is reasonable...also can you change the limitations for temperatureand also take off limitations when making a call and using wifi hotspot...the phone does not allow to take flash while its in low temp, when making a call or when using wifi tethering/hotspot.....thanks faux
Click to expand...
Click to collapse
Yeah that's HTC for you. Always thinking ahead. You never know when your phone might be damaged by taking a picture with the flash activated while using it as a hotspot. In regards to the cold... I live in Detroit, work at night and I've used it a couple of times without issue. How cold does it have to be? I kinda wanna see this! LOL! It's gotten down to about 19F here... can't remember if I had used the camera though.
But I can understand why you wouldn't want to use the flash in cold weather. Might cause an avalanche or wake a bear or something. Yikes! Smart thinking HTC!
Binary100100 said:
Yeah that's HTC for you. Always thinking ahead. You never know when your phone might be damaged by taking a picture with the flash activated while using it as a hotspot. In regards to the cold... I live in Detroit, work at night and I've used it a couple of times without issue. How cold does it have to be? I kinda wanna see this! LOL! It's gotten down to about 19F here... can't remember if I had used the camera though.
But I can understand why you wouldn't want to use the flash in cold weather. Might cause an avalanche or wake a bear or something. Yikes! Smart thinking HTC!
Click to expand...
Click to collapse
lmao....it bothers me that I'm talking to my gf and she wants a picture of something i have to hang up take the picture send then call back wtf!!!!! and don't even get me started on wifi hotspot...how does this make sense????????????????? sense ui should be called retarded ui cause it does not make "sense" no pun intended.
seansk said:
lmao....it bothers me that I'm talking to my gf and she wants a picture of something i have to hang up take the picture send then call back wtf!!!!! and don't even get me started on wifi hotspot...how does this make sense????????????????? sense ui should be called retarded ui cause it does not make "sense" no pun intended.
Click to expand...
Click to collapse
To HTC or to whomever it may concern,
I intend to propose a class action lawsuit pending on verification of an intentional design flaw that prevents the consumer to use the flash on the device while talking on the phone while also using the device as a wifi hotspot in subzero degree weather. I discovered this flaw while taking pictures of Bigfoot eating Santa's raindeer at the North pole just after Christmas. Unfortunately I was unable to take proof of evidence of the situation because of the mentioned designed flaw. While I was on the phone with animal control they demanded photographic evidence of the situation. Because I was not able to comply due to this design flaw the raindeer could not be saved thus there will be no more Christmas. Evidence of the intention for the mentioned limitations is the simple fact that the appropriate error messages are programed into the kernel source. However because you fail to include the wireless drivers, the kernel source cannot be utilized to compile a patch for this flaw.
Shame on you HTC.
I should be a prosecutor.
Binary100100 said:
To HTC or to whomever it may concern,
I intend to propose a class action lawsuit pending on verification of an intentional design flaw that prevents the consumer to use the flash on the device while talking on the phone while also using the device as a wifi hotspot in subzero degree weather. I discovered this flaw while taking pictures of Bigfoot eating Santa's raindeer at the North pole just after Christmas. Unfortunately I was unable to take proof of evidence of the situation because of the mentioned designed flaw. While I was on the phone with animal control they demanded photographic evidence of the situation. Because I was not able to comply due to this design flaw the raindeer could not be saved thus there will be no more Christmas. Evidence of the intention for the mentioned limitations is the simple fact that the appropriate error messages are programed into the kernel source. However because you fail to include the wireless drivers, the kernel source cannot be utilized to compile a patch for this flaw.
Shame on you HTC.
I should be a prosecutor.
Click to expand...
Click to collapse
omg rotflmao........so basically we really can't fix the hotspot issue or the call issue!!....I'm beginning to not like HTC...and I definitely don't like sgs2...I better start designing my own phone....the N1 never had this kind of BS problems....I used it as hotspot...called...took pictures alll the way down to 0 battery and it was made by HTC...what changed??? I still like my N1 better lol...hopefully next year we'll get
new years resolution dream phone:
720p super amoled PLUS "not pentile" screen
8 or more Mega pixel back side illuminated sensor with a f/2.2 or less and a wide lense camera lense with good optics and good audio quality while recording video.
able to use flash without limitations!!!!!!!!!!!!!!!!!!!!!!!!!
no flash bleed into camera sensor that requires 3 rounds of electrical tape
No screen bleed from the soft buttons
10 hour talk talk battery preferably over 2200 mAMp battery
STOCK ICS with custom amazing camera software like that amaze has now.
NO CARRIER BRANDING NO BLOATWARE. is this so much to ask
a phone that can drill and fill my patients teeth, do root canals and make crowns for them...ok maybe this last one is asking too much.
is this so much to ask???
seansk said:
...is this so much to ask
a phone that can drill and fill my patients teeth, do root canals and make crowns for them... is this so much to ask???
Click to expand...
Click to collapse
Ummm... yes. I believe the best you can do is create a phone with a jackhammer for a vibration mode, shove it in the patients mount and keep calling it. But of course some other people would use it for... inappropriate purposes.
Example from one of SassyBoB's reviews: https://market.android.com/details?...t=W251bGwsMSwyLDEsImNlbml4LmFuZHJvaWQudmJyIl0.
Related
All these wonderful ROMs; I am impressed but:
1) I obtained my HTC Touch Pro by trading an unwanted/unneeded old notebook computer for it so kinda sorta in a way I got the phone "for nothing".
Addition: IE: I didn't purposely spent $400 to get this phone. I just got it.
2) I don't really need a pocket PC.
Addition: Not now. Not today. Maybe later.
3) I don't really need a smart phone.
Addition: The key word being "need". All I "need" right now is a phone. I'll trade all the cool fancyness for battery life. My old Straight Talk phone could sit there on standby for a week and not have the battery indicator drop more than a couple notches if even that much. I could use it for all week without charging it. Yes, I know the TP is a Pocket PC and a phone; just making a point.
4) The battery life on this thing is horrible (24 hours on standby costs 20%+ of the battery power) I assume it's because it's doing all those extra Pocket PC/Windows stuff in the background.
Addition: If I charge it before I go out and charge it while I'm out it may last the entire day but likely not.
5) All I really *need* is a camera phone. Phone calls, voicemail, text/media messages, snapshot and video, ...that's about it.
6) The extra unneeded stuff is taking up flash-ram space that could be used for storing pictures and video.
Addition: Strip it all out and I'll have room for lots of pic and videos.
7) Flashing back to the original ROM is easy and takes a few minutes so no harm done by "dumbing-down" the current ROM.
Addition: When I want the smart phone I'll flash on a super-duper all-singing-all-dancing ROM.
8) A Pocket PC is very cool but if I want a portable computer I have a much more powerful very nice netbook that is more or less a part of my body so I don't *need* another computer on my person.
That said, has anybody make a stripped down/basic/bare minumum/no frills/no extras/maximum battery life/minimum flash memory used/no fancy stuff/no wifi/gps/internet connection/nuttin-but-a-camera phone ROM?
Addition: IE: Don't do nothing but make calls and take pictures. Simple. Fast. Maximum battery life. A Dumb Phone (for now anyway).
Thanks.
P.S. No. I don't wish to trade it for a dumb phone. I may some day want a smart phone/Pocket PC but not right now.
Fred Doolie said:
4) The battery life on this thing is horrible (24 hours on standby costs 20%+ of the battery power) I assume it's because it's doing all those extra Pocket PC/Windows stuff in the background.
Click to expand...
Click to collapse
I'm not sure what your expectations are, but only losing 20% in 24 hours is great! I doubt you'll do any better than that. An always active data connection, GPS, and Wi-Fi are the big things that are going to kill battery life, not the OS. I would make sure you have the matching rilphone.dll for the version of radio you are using, however.
Fred Doolie said:
That said, has anybody make a stripped down/basic/bare minumum/no frills/no extras/maximum battery life/minimum flash memory used/no fancy stuff/no wifi/gps/internet connection/nuttin-but-a-camera phone ROM?
Click to expand...
Click to collapse
What you've basically described is a Stock ROM. These are basically just ROMs with the newest build of Windows Mobile and some essential apps, meaning that memory and CPU usage is low. But most of the things that consume battery are switch-off-able, such as the backlight, WiFi, 3G connection, GPS, Bluetooth etc. through the Settings menu or the Comm Manager. If you haven't flashed your phone to a custom ROM yet, you won't get much more basic than the standard 6.1 ROM that your carrier put on the phone to start with.
If you do want Windows Mobile 6.5 but don't want all the frills, you can either be brave and cook a stock-like ROM yourself, or try one from the forums:
[KITCHEN][ROM][WWE][MAR-13-2010] RomRom WM6.5 23547 stock-like Kitchen & ROM is the most updated stock-like kitchen/ROM.
rmcknight:
>I'm not sure what your expectations are, but only losing 20% in
> 24 hours is great!
But that's in Airplane mode (all radios off)! With the radios on it will stand by for about a day before the battery is dead.
Expectations:
"Standby time: Up to 462 hours for WCDMA"
"Talk time: Up to 378 minutes for WCDMA"
http://www.htc.com/www/product/touchpro/specification.html
Reality:
More like up to 120 hours and up to 90 minutes.
---------------------------------------------------------------------
Ben Dude,
>What you've basically described is a Stock ROM.
>meaning that memory and CPU usage is low.
>much more basic than the standard 6.1 ROM that your carrier
>put on the phone to start with.
Sad to hear. The ROM that came with the phone is full of extra stuff and sucks the battery like crazy. The Energy ROM I flashed has even more stuff seems to be easier on battery life. We'll see. This Energy ROM is very cool and maybe I DO want a smart phone right now. The main thing was the battery life. I thought stripping down a ROM would increase battery life due to less stuff running and taking up precious flashram space. Well, SD cards are cheap I guess. I can move as much as possible to external storage.
Maybe I'll have to learn to cook. A stripped-down stock ROM with *everything* removed except phone and camera software. It boots up to a nice wallpaper with two buttons that say "Phone" and "Camera". All radios except phone deactivated. It might be fun to learn how to do that.
Thanks, Guys.
I would happily trade you an LG Xenon for your Fuze.
Fred Doolie said:
rmcknight:
Maybe I'll have to learn to cook. A stripped-down stock ROM with *everything* removed except phone and camera software. It boots up to a nice wallpaper with two buttons that say "Phone" and "Camera". All radios except phone deactivated. It might be fun to learn how to do that.
Thanks, Guys.
Click to expand...
Click to collapse
You can try, but you'll still have to flash the entire operating system; as far as I know it's not as easy as what you've said. I suppose the closest would be a 6.1 ROM without Manila (HTC Sense), no bloatware installed and the hotkeys set as 'phone' and 'camera'. But I doubt that it would be worth trying to truly 'cook out' things like GPS, as they really can be switched off with one button press, and that's probably why nobody does (hence your search for a ROM ).
I've had amazing battery life using the ROM in my sig (dont even think about using android though-- it's fun but not ready for daily use).
install S2U2 -- it makes locking easier but also reduces how often the screen turns on in your pocket. You can set up the screen off delays and such and it saves you a ton of battery life.
Disable the touchflo home screen-- it's pretty superfluous and probably drains battery faster.
If battery life is really bad, consider buying a new one. Check the total talk time (start -> settings -> device information -> call duration) to get an idea of how used the phone is. Those counters don't reset when you flash a new ROM.
try timolols and turn off data.
@ Myrddin
I'll bet you would! Thanks but I want this phone; just trying to make it "My Phone" rather than "Sprint's Phone".
@Storm 717
>I've had amazing battery life using the
> ROM in my sig
I'll try it. As long as I still have my Sprint Picture Mail. It's the only app I really use and need.
>install S2U2 -- it makes locking easier
Been there done that. LOVE it!
>Disable the touchflo home screen
BTDT
>Check the total talk time (start ->
>settings -> device information ->
>call duration) to get an idea of how
>used the phone is.
What you talkin' 'bout, Willis?
See the screenshots.
As long as I have posted them, anybody see a problem with the versions and numbers?
just make sure if you flash to flash a CMDA one and not a GSM rom or you will likely brick your phone
jul644 said:
just make sure if you flash to flash a CMDA one and not a GSM rom or you will likely brick your phone
Click to expand...
Click to collapse
Yes, I've read that and believe it but why? Wouldn't it just not work and then you flash a proper ROM over it?
I know that if you give a little donation to NRGZ or the Capn they can do a perfect ROM for your "need"
Talk to them!
I hate to promote my own ROM, but give my stock-like ROM a try. It's almost exactly what you describe.
Alternatively, I can whip up an even more stripped-down version if you like. Let me know.
.
Fred Doolie said:
Yes, I've read that and believe it but why? Wouldn't it just not work and then you flash a proper ROM over it?
Click to expand...
Click to collapse
its because the amount of voltage/wattage to the radio (the part that connects to the network) is different between gsm and cmda so when you flash a cmda rom on a gsm(sim card)phone then it literally breaks it and also happens vis-versa
response and modification request
jul644 said:
its because the amount of voltage/wattage to the radio (the part that connects to the network) is different between gsm and cmda so when you flash a cmda rom on a gsm(sim card)phone then it literally breaks it and also happens vis-versa
Click to expand...
Click to collapse
Well, that's bad designing. You'd think there would be a check for that in the hardware in case some noobie tech at Sprint/Verizon/AT&T was really tired and tried to update your phone with the wrong ROM. Like a splashscreen saying "GSM Verizon Diamond ROM detected - This is a Touch Pro 1 CDMA Phone" and then it just stops dead on that screen with an endless do-nothing loop.
************
MODIFICATION REQUEST, YOU BRAINS OUT THERE! CAN IT BE DONE?
SAVE US FROM OURSELVES! Can the phones be modified to detect improper ROMs so it doesn't even try to fully boot up/blow up? Some of us are really stu.. frightened noobies.
************
Or a modification in the [one of those files in the RUU folder] that examines the phone and refuses to proceed if the .nbh filoes doesn't match the phone it sees".
Is there any other way to brick a phone. The child in me wants to play with cool stuff but the adult in me says if "it aint broke don't fix it! You don't need a $400 brick"!
* Yes, I know about Hackentosh but don't understand how it works.
On the official HTC site, you can only download a ROM after you type in your phone's serial number, which checks that you have the right hardware for the upgrade. As far as HTC care, this matter has been dealt with. I would guess that techs working for carriers probably have to input your SN too.
There are so many tutorials and guides on this site for first time flashers that if they don't read them first, it's their own fault for being ignorant. Most chefs will warn about it too.
ben_duder said:
Most chefs will warn about it too.
Click to expand...
Click to collapse
Yes but sadly a few don't. I have seen at least one post in the CDMA section that mentions way down "Remove the sim card while flashing the ROM". Oop, that's a GSM phone, no? If I would missed that one line I may have flashed that ROM by accident. Also, a few say something like "For the TP" but don't mention CDMA or GSM anywhere. You have to HOPE it's in the correct section. I just wanted to be 100% safe from accidents.
---
Moot point though; I'm through with flashing. None of the ROMs I found were as smooth and fast as the stock ROM. Beautiful, oh yes, but slow and locking up the phone every little while. It stinks but it runs fine.
I think it's just probably because this site is dedicated to getting the most out of our devices and what you're looking for just doesn't fit in with that. In my experience, I've never had a slow, unstable or just unusable stock ROM. I think your best bet is just to buy a bigger microSD card if you want more space for media, stick with WM6.1 and switch off everything you don't need (3G connection, Wi-Fi, screen brightness, any bloatware, Bluetooth, you know the rest).
With regards to the CDMA/GSM issue, I've never really considered it because I've never been the first to try out a ROM. If it really was posted in the wrong section (which I think is unlikely) it would only take one person other than yourself to flash it and comment before everyone realised. Just make sure you're not that person
Fred Doolie said:
Well, that's bad designing. You'd think there would be a check for that in the hardware in case some noobie tech at Sprint/Verizon/AT&T was really tired and tried to update your phone with the wrong ROM. Like a splashscreen saying "GSM Verizon Diamond ROM detected - This is a Touch Pro 1 CDMA Phone" and then it just stops dead on that screen with an endless do-nothing loop.
************
MODIFICATION REQUEST, YOU BRAINS OUT THERE! CAN IT BE DONE?
SAVE US FROM OURSELVES! Can the phones be modified to detect improper ROMs so it doesn't even try to fully boot up/blow up? Some of us are really stu.. frightened noobies.
************
Or a modification in the [one of those files in the RUU folder] that examines the phone and refuses to proceed if the .nbh filoes doesn't match the phone it sees".
Is there any other way to brick a phone. The child in me wants to play with cool stuff but the adult in me says if "it aint broke don't fix it! You don't need a $400 brick"!
* Yes, I know about Hackentosh but don't understand how it works.
Click to expand...
Click to collapse
First answer is that yes the manufacturers DO in fact have a way to block improper roms. This is why they initially have a CID lock. CID locks prevent the usage of Non-Carrier roms being installed on the phone. Once its had this lock removed, you are able to install non-factory firmwares ( like the ones these wonderful chefs create for us ). In a sense, you take it in your own hands if you flash the wrong firmware for your device, because you have already removed the protection from the carrier.
Second answer. A Hackintosh is computer not made by apple that is running Apples OSX. There are several ways to achieve this, one of which is using an EFI ( Apples Bios Type ) Emulator such as Chameleon or Boot123 , or by using a chipset capable of running the Vanilla ( OEM ) Kernel as is ( Specific Intel chipsets ). I could help direct you to the proper places to discuss this in a PM if you want further information.
Hope those answers helped some
pyraxiate said:
1) CID locks prevent the usage of Non-Carrier roms being installed on the phone.
2) A Hackintosh is computer not made by apple that is running Apples OSX.
Click to expand...
Click to collapse
1) I see. Thanks.
Thought!
The official Sprint upgrade ROM package works on a locked phone. I've installed it. It flashed and worked.
The official Sprint upgrade ROM's .nph file is a signed ROM, right? A signed ROM will get past the CID lock.
You guys are geniuses. Why not put a "sign" code into a cooked ROM for safety? Leave the CID protection in place and let it block incorrect ROMS. Am I being too simplistic?
2) The hackintosh line was a leftover from when I was composing the post. I should have seen and removed it.
Hi im so sorry for making yet another thread for the camera autofocus noise but it seems devs keep ignoring this.
the camera auto focus on different roms will be worse. sometimes doing it when you turn the phone on when you use flashlight and even sometimes when the card is being read. and im sick of hearing devs blame it on the camera model or that its always been there. my camera never made any noise till i installed miui and ever since it makes noise even when i revert to stock roms. the best its been is on villian rom.
this is obviously a problem with the firmware being used or something else that devs are doing or not doing. can someone please devote some time to get this fixed please. im not the only one who feels this way and i think its wrong for devs to lead us to believe its normal when its clearly not if it effects different on different roms and that obviously the noise wasnt there before. i think its a serious fix needed.
so please please please someone get to the bottom of this
PLEASE NO ONE POST INLESS YOUR HERE TO WORK TOWARDS A FIX
mikeinessex said:
PLEASE NO ONE POST INLESS YOUR HERE TO WORK TOWARDS A FIX
Click to expand...
Click to collapse
Actually i posted to let you know that if you have an OC camera, it's normal. All OC cameras make that noise, no matter what rom you are using
Sp1tfire said:
Actually i posted to let you know that if you have an OC camera, it's normal. All OC cameras make that noise, no matter what rom you are using
Click to expand...
Click to collapse
and like i said before if thats so then mine wouldnt of not made noise then now makes it. so please no comments like that on here please its not getting this problem sorted
mikeinessex said:
and like i said before if thats so then mine wouldnt of not made noise then now makes it. so please no comments like that on here please its not getting this problem sorted
Click to expand...
Click to collapse
Ok, sorry for stating the obvious. Please find somebody with an OC camera that doesn't act like that, be it on stock or custom rom and then we can talk about fixing things. If that's default behavior for OC cameras and looks like it is, no dev can fix it. But i have a fix for you: replace your phone with another SII that doesn't have an OC camera. Easiest fix in the world and you can do it yourself.
Sp1tfire said:
Ok, sorry for stating the obvious. Please find somebody with an OC camera that doesn't act like that, be it on stock or custom rom and then we can talk about fixing things. If that's default behavior for OC cameras and looks like it is, no dev can fix it. But i have a fix for you: replace your phone with another SII that doesn't have an OC camera. Easiest fix in the world and you can do it yourself.
Click to expand...
Click to collapse
i seen people who have had se firmwares and the update gave them oc and visa versa. so obviously the firmware code has no relavence to the camera. if what you say was right then the above wouldnt be possible. check out the camera firmware upgrade thread and see for yourself
I'm checking that thread often, cause i'm interested in a fix myself, but i still don't buy that firmware change, since no one else succeeded in changing an OC camera to a SC one. There's only 1 report of it. Can't really compare 1 report to all the owners with an OC camera that confirmed the clicking noises regardless of roms, firmware updates and everything else. I got no quarrel with you and i really wish you could find someone with an OC camera that doesn't behave like that. I couldn't find any and i investigated both on several forums and in real life with friends who own SII.
P.S. And i'm pretty sure if that guy uploads his apk your phone will say camera already has the latest update and can't install it.
Sp1tfire said:
I'm checking that thread often, cause i'm interested in a fix myself, but i still don't buy that firmware change, since no one else succeeded in changing an OC camera to a SC one. There's only 1 report of it. Can't really compare 1 report to all the owners with an OC camera that confirmed the clicking noises regardless of roms, firmware updates and everything else. I got no quarrel with you and i really wish you could find someone with an OC camera that doesn't behave like that. I couldn't find any and i investigated both on several forums and in real life with friends who own SII.
P.S. And i'm pretty sure if that guy uploads his apk your phone will say camera already has the latest update and can't install it.
Click to expand...
Click to collapse
the apk doesnt work. you cant do it like that i tried. u have to have a firmware upgrade apk or be compiled from scratch. just taking the apk out through root explorer wont make any difference.
Tested all the firmware update apks posted in that thread. None could be applied and my cam remained OC002, even though people reported that they had 002 and it turned to 009, which i highly doubt it can be done just by updating camera, cause 009 is an older version and camera wouldn't let you downgrade to a previous version. My phone has no root, so i don't have any other options than wait for another firmware update from Samsung.
Sp1tfire said:
Tested all the firmware update apks posted in that thread. None could be applied and my cam remained OC002, even though people reported that they had 002 and it turned to 009, which i highly doubt it can be done just by updating camera, cause 009 is an older version and camera wouldn't let you downgrade to a previous version. My phone has no root, so i don't have any other options than wait for another firmware update from Samsung.
Click to expand...
Click to collapse
been speaking to codework. would have to be pushed in through system/ect/firmware and it seems that the roms only come with oc type firmwares. so the roms have never been giving the phone the options for the se type firmwares. things are started to prove my point now. think codework is looking into it more now cause my theory is started to maybe be true
I have OCED11 ver of camera and today I heard that sound when entering camera, and when switching from photo to video mode. I don't remember hearing it before, but if others have it also, then it's nothing abnormal. I bought phone 1 month ago, and didn't install any custom apps and etc.
Sorry for the rather ominious title. But its hard to actually picking a proper title for some subject :/
I have had a SGS2 for a couple months now and I have had a few issues with it that I hope some of you might be able to help with.
1:
I stood at an army training ground and was recording FullHD video with the phone but when it dropped to 15% battery it refused to record anymore or take pictures. Is there some way to "mess with" or hack it to simply keep recording till the battery is dead?
2:
I had a circular battery mod for my phone which worked fine of the original rom which was KE7 for a Nordic phone. But now trying to flash the same battery mod with CWM bootloops my phone . I have tried to see if I can find any battery mods like it, but the only ones I have been able to find so far has been the kind that uses the regular battery icon and just adds the percentage.
I would actually like the circular one as I prefer that one, but is there even one that would work on the KH3 Rom?
3:
I see people mentioned Deodexed and odexed as terms, but what does that mean and what is the actual difference between the 2 of them?
I hope someone might be able and willing to help with either all of the 3 questions or just some of them. And thanks in advance for your time.
MeX_DK said:
Sorry for the rather ominious title. But its hard to actually picking a proper title for some subject :/
I have had a SGS2 for a couple months now and I have had a few issues with it that I hope some of you might be able to help with.
1:
I stood at an army training ground and was recording FullHD video with the phone but when it dropped to 15% battery it refused to record anymore or take pictures. Is there some way to "mess with" or hack it to simply keep recording till the battery is dead?
2:
I had a circular battery mod for my phone which worked fine of the original rom which was KE7 for a Nordic phone. But now trying to flash the same battery mod with CWM bootloops my phone . I have tried to see if I can find any battery mods like it, but the only ones I have been able to find so far has been the kind that uses the regular battery icon and just adds the percentage.
I would actually like the circular one as I prefer that one, but is there even one that would work on the KH3 Rom?
3:
I see people mentioned Deodexed and odexed as terms, but what does that mean and what is the actual difference between the 2 of them?
I hope someone might be able and willing to help with either all of the 3 questions or just some of them. And thanks in advance for your time.
Click to expand...
Click to collapse
I see you use CMW recovery so you must be rooted
this rom
http://forum.xda-developers.com/showthread.php?t=1198334
Along with the Villain tweak app provides everything your after easily.
There are also lots of themes in the thme section for your tweeking needs
This is a KG6 rom but there isnt much difference imho.
Deodexing basically means files/things are easier to mess around with.
Problem is I like the stock feel of the Rom, hence why I have never really bothered flashing something like MRC, Cynoagen, Villian etc.
I prefer to just keep things normally and then "tweak" the few things I am not entirely happy with. So I was primarily looking for fixes/hacks that could be applied on an existing rom rather then a full new rom entirely.
But thanks for the suggestion regardless
MeX_DK said:
Problem is I like the stock feel of the Rom, hence why I have never really bothered flashing something like MRC, Cynoagen, Villian etc.
I prefer to just keep things normally and then "tweak" the few things I am not entirely happy with. So I was primarily looking for fixes/hacks that could be applied on an existing rom rather then a full new rom entirely.
But thanks for the suggestion regardless
Click to expand...
Click to collapse
A man after my own heart! thats good because Villain is completely stock Samsung just pretty much Deodexed, no themes no bulls**t.
The only tweaks/themes that are applied will be by you
Also If you like Cyanogen you could always check the version for the sgs2 its pretty complete now only a few things left to sort out (bluetooth being the major one).
Well I just flashed the KH3 rom just the other day and I would like to actually give that one a tryout before deciding to try another rom .
But the only thing that really bugs me is why the phone so stubbornly decides to stop wanting to use the camera at 15%. I mean there must be a hacked camera.apk out there that works for me ratehr then having to flash a completely different rom to get what I "want".
MeX_DK said:
Well I just flashed the KH3 rom just the other day and I would like to actually give that one a tryout before deciding to try another rom .
But the only thing that really bugs me is why the phone so stubbornly decides to stop wanting to use the camera at 15%. I mean there must be a hacked camera.apk out there that works for me ratehr then having to flash a completely different rom to get what I "want".
Click to expand...
Click to collapse
Found your mods for the stock rom, Here you go
http://forum.xda-developers.com/showthread.php?t=1154278
http://forum.xda-developers.com/showthread.php?t=1104051
Thanks a lot for your time and effort
I recently flashed my Samsung Fascinate with PowerWashed Team's PWGB Version 2.0 (Beta 3). I'm terribly new to using custom ROMs, but I'm quite pleased with the results. I've only had one concern with this ROM regarding the back light on the soft keys. They light up every time I touch my screen or press a hard key.
I've attempted to find a setting for this in the OS and in CwM Voodoo Lagfix Recovery v2.5.1.x screen, but wasn't able to find such a setting (Again, I'm very green so it could be right under my nose and I simply don't know it.)
I also attempted to install myriad apps to keep the back light off on screen touch including:
Screen Filter (No effect)
Night Mode (No effect)
Light Flow Lite - LED Control (No effect)
Light Manager - LED Settings (This app actually stops the back light from coming on, however it's unpredictable and works >15% of the time)
I've also done a lot of searching on the matter. I've seen where others have stated the problem, but none where there was a solution or enough information for me to further investigate a way to fix this. It's also been complicated to find information due to a variety of search terms (soft keys, led, etc.) yielding results about the camera or other things that are unrelated to my issue coupled with my lack of direct knowledge on the matter.
I'd really appreciate any advice on either directly fixing this or a source of information so I may learn more from what is causing this behavior and fixing it myself. Thanks, everyone for all the time and effort you've put in for making things like this accessible to individuals like me. I can't tell you how much I appreciate it.
This behavior is a product of the kernel, and most people find it desirable. If you install the kernel control app nstools, you should see an option called cmled timeout, allowing you to set the led backlight timeout.
Posted from my Galaxy Tab with CM10
MultipleMonomials said:
This behavior is a product of the kernel, and most people find it desirable. If you install the kernel control app nstools, you should see an option called cmled timeout, allowing you to set the led backlight timeout.
Click to expand...
Click to collapse
Thanks for the information! Unfortunately, the ROM I flashed has a stock kernel and doesn't offer this option. So, I suppose that's the first thing I need to address, but now I know where the problem lies! Thank you so much for your time and input, I'll put it to good use.
Are you saying the back lights light up even if you just touch the screen? That's strange, they only have ever lit up for me when I actually touch a soft key or hit the power button to wake the phone up.
Well good luck, I'm not sure what kernel is best for GB as I started flashing custom roms during ICS and I'm now on Jelly Bean and never going backwards.
Crawshayi said:
Are you saying the back lights light up even if you just touch the screen?
Click to expand...
Click to collapse
Yes, exactly this. It is really odd and very bothersome when trying to read at night. Even if I use the volume rocker to turn the page the lights will come on. It's maddening. I'm currently looking at the kgb kernel, but I think the nstools led option isn't actually going to address this quirk. (Directly, I believe I will end up disabling the led altogether)
If you don't mind, what rom did you choose?(Ignore, I was on mobile and did not see your signature at the time)
How has the performance been? I'm interested in doing the same, but was afraid my fascinate wouldn't handle jb very well.
Well needless to say it's different for everybody when it comes to roms, sometimes your phone will have no problem running a certain rom where as someone else's might not even boot. As for myself I've been pretty fortunate and have been able to try any rom I've wanted to with success, and I'll give you a few of my thoughts on it.
If you're wondering about performance, well simply put JB blows everything else away and runs like a dream on the Fascinate. Once you spend a few days with it you'll never want to go back honestly. Even on our aging hardware, it runs amazingly fast, even without kernel performance tweaks.
Anyway, as far as roms go, if you're most concerned with stability and reliability then I would highly suggest CM10 (whatever the latest nightly version is). Of all the roms I've tried, it's by far the one that's given me the least hassle. That said, I'm quite fond of the tweaks offered in AOKP, mainly the voltage settings (for battery life) and the fact that it seems to vibe much better with Devil kernel than CM10 does. I've been running my current rom/kernel for a couple of weeks now, and I'm happy enough with how it's running to keep it as my daily driver for a while.
This isn't to say the GB roms aren't any good, because of course they are, but considering how nice JB roms run on our phone you'd be doing a disservice by not at least giving them a shot.
Crawshayi said:
If you're wondering about performance, well simply put JB blows everything else away and runs like a dream on the Fascinate. Once you spend a few days with it you'll never want to go back honestly. Even on our aging hardware, it runs amazingly fast, even without kernel performance tweaks.
Click to expand...
Click to collapse
You sold me on the idea of JB. Flashed it today, and I love it so far. Plus, my soft key lights aren't constantly on! Win-win.
Thank you so much for the guidance. Your input helped turn a satisfactory experience with ROMs into a trully positive one.
Glad to hear you liked it man, I was reluctant at first too due to (at the time) no 'official' releases, but I'm glad I made the jump. I'm quite enjoying AOKP M1 and will probably stay on it for a long time. Which rom did you end up trying?
Crawshayi said:
Glad to hear you liked it man, I was reluctant at first too due to (at the time) no 'official' releases, but I'm glad I made the jump. I'm quite enjoying AOKP M1 and will probably stay on it for a long time. Which rom did you end up trying?
Click to expand...
Click to collapse
I was really impressed with your review, so I chose to go with the same rom. It also seemed like the most stable option and easiest for me to understand the installation procedure (very important for me since this is my only device and more than just my daily driver, it's my life line). I had been extremely hesitant to go to JB for fear of junking my phone up, but I'm really glad I took the extra risk. I just needed an extra bit of encouragement. Thanks again for all your input!
If you managed to install AOKP smoothly you can pretty much install any rom the same way, basically meaning wipe data and cache/davlik then flash whatever you want to. Luckily this phone happens to be very hard to break, and you'd have to do something pretty extreme to brick it. I highly recommend Titanium backup pro so you can just backup the apps you want, and restore them in no time when you're trying different roms. Also, I've been using some voltage settings that make battery life insanely good, so if you're interested in doing that let me know and I'll post them.
olalaelaine said:
I was really impressed with your review, so I chose to go with the same rom. It also seemed like the most stable option and easiest for me to understand the installation procedure (very important for me since this is my only device and more than just my daily driver, it's my life line). I had been extremely hesitant to go to JB for fear of junking my phone up, but I'm really glad I took the extra risk. I just needed an extra bit of encouragement. Thanks again for all your input!
Click to expand...
Click to collapse
Regarding the key back light, since you are on aokp jellybean now if you still want to tweak the settings, goto settings and then device settings. There you can adjust the timeout on them
Crawshayi said:
If you managed to install AOKP smoothly you can pretty much install any rom the same way, basically meaning wipe data and cache/davlik then flash whatever you want to. Luckily this phone happens to be very hard to break, and you'd have to do something pretty extreme to brick it. I highly recommend Titanium backup pro so you can just backup the apps you want, and restore them in no time when you're trying different roms. Also, I've been using some voltage settings that make battery life insanely good, so if you're interested in doing that let me know and I'll post them.
Click to expand...
Click to collapse
just a little hint: NEVER RESTORE SYSTEM APPS WITH TITANIUM YOU WILL GET BOOTLOOP
Sent from my SCH-I500 using Tapatalk 2
I've restored Nova before that was a system backup with no problems but I agree about anything else. Not sure what system apps anyone would even want to backup really
Crawshayi said:
I've restored Nova before that was a system backup with no problems but I agree about anything else. Not sure what system apps anyone would even want to backup really
Click to expand...
Click to collapse
Dude I mean like system UI or settings lol
Sent from my SCH-I500 using Tapatalk 2
bbrad said:
Dude I mean like system UI or settings lol
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
I've actually done that before just to see what happened (system settings) and it didn't bootloop, it simply didn't restore anything. Not that I mind re-setting everything after a clean install, just figured I'd try to save a little time
Crawshayi said:
I've actually done that before just to see what happened (system settings) and it didn't bootloop, it simply didn't restore anything. Not that I mind re-setting everything after a clean install, just figured I'd try to save a little time
Click to expand...
Click to collapse
Are you trying too teach him too restore system apps lol?
Sent from my SCH-I500 using Tapatalk 2
Nope not at all, just chiming in on what happened when I tried it. It should be a no brainer to anyone flashing roms to not restore system apps, even if they're new to it honestly
Crawshayi said:
Nope not at all, just chiming in on what happened when I tried it. It should be a no brainer to anyone flashing roms to not restore system apps, even if they're new to it honestly
Click to expand...
Click to collapse
I know but it would surprise you I've had people complain because they flashed a i9000 ROM and it didn't work because the developer is stupid LOL
Sent from my SCH-I500 using Tapatalk 2
We've all had various levels of frustrations regarding the Huawei overlay (for me, the battery saving options killing music apps no matter the settings). We saw how they reacted to the Kitkat cutoff; maybe we should start a petition for a stock L update?
bob60626 said:
We've all had various levels of frustrations regarding the Huawei overlay (for me, the battery saving options killing music apps no matter the settings). We saw how they reacted to the Kitkat cutoff; maybe we should start a petition for a stock L update?
Click to expand...
Click to collapse
I'm not having this problem on any of my 3 mate2 devices. got to be operator error.
As much as I'd love a stock ROM, I doubt it would work. It's like asking Samsung to do a stock ROM.
But since our phone's source is out and AOSP's source is out, we just need a developer with our phone to get Lollipop.
This phone will never get Lollipop.
Suuuuuuuuure, Hauwei claims it is coming. However isn't that the same song and dance that they said in regards to this phone and Kit Kat?
I will believe it when I see it. I would encourage everyone else to not hold their breath.
ur misinformed. Huawei never once said or claimed to update the mt2-l 03 to KK.
Won't matter to me...stock 4.3 is super stable, battery life is excellent and unless some app I want to use, requires 4.4 or above,
I'll stick with what it came with. Just because there is a "new" OS, doesn't make it better...JUST NEW.
I actually prefer 4.3 also. I hate how kitkat screws up the sd card with write security. I know that sd kitkat fix are available for rooted phones but I still have problem with it. If LL removes that restriction then maybe I will update to LL. Otherwise I would prefer to stick to 4.3.
superbass311 said:
ur misinformed. Huawei never once said or claimed to update the mt2-l 03 to KK.
Click to expand...
Click to collapse
They did to me. Before I bought it in early July, I had more than one support chat with Huawei reps confirming that it would be updated. Two different reps told me the same line - it was 4.3 at launch, and would be updated to KitKat within 60 days but they could not confirm a firm date. I wouldn't have bought it without that assurance.
whatsitsnamenow said:
I actually prefer 4.3 also. I hate how kitkat screws up the sd card with write security. I know that sd kitkat fix are available for rooted phones but I still have problem with it. If LL removes that restriction then maybe I will update to LL. Otherwise I would prefer to stick to 4.3.
Click to expand...
Click to collapse
My SD is tweaked as it is so I personally hope an update will fix it. Most of the time when using Root Explorer or any other, I cannot move filed from the SD card to internal storage or vise versa. Such as pushing an app to system/data (or app) or pushing a ringtone to system/media It shows as if there is no SD mounted however there clearly is because my music files and videos play just fine and they are on the card.
For some reason my SD card gets unmounted at times. I can't see the movies/pictures in it. I go to settings and i unmount and mount the sd card and then it's fine
pucherto123 said:
For some reason my SD card gets unmounted at times. I can't see the movies/pictures in it. I go to settings and i unmount and mount the sd card and then it's fine
Click to expand...
Click to collapse
I try that too but I still cant move things to internal storage for some reason. I can't even edit the build.prop to try to fix it
MikeyLee said:
I try that too but I still cant move things to internal storage for some reason. I can't even edit the build.prop to try to fix it
Click to expand...
Click to collapse
Just out of curiosity, you don't have a text file called set_immutable_list anywhere in your system folder? There is one on the Chinese Mate 2's and whatever location is listed in the set immutable list file is blocked even if you have root. I have found a way around it, just sounds like the same problem I experienced before I found a fix.
MikeyLee said:
My SD is tweaked as it is so I personally hope an update will fix it. Most of the time when using Root Explorer or any other, I cannot move filed from the SD card to internal storage or vise versa. Such as pushing an app to system/data (or app) or pushing a ringtone to system/media It shows as if there is no SD mounted however there clearly is because my music files and videos play just fine and they are on the card.
Click to expand...
Click to collapse
Have you tried un-check "Mount namespace separation" in SuperSU as mentioned here:
http://forum.xda-developers.com/showpost.php?p=56166409&postcount=14
I am 100% happy with 4.3 as well. I was very concerned with getting this phone, but the battery life sucked me in. I love the fact that I can basically do anything I want on my phone all day, and not need a charger. Everything works smooth and it is extremely stable. There is nothing I can't do with this phone, that I had done with KitKat or Lollipop. I think more companies need to look at what Huawei has done with this phone and follow their lead. Instead of going thinner, they should be concentrating on battery life. I have had phones with much better specs, but they weren't nearly as smooth. I think people worry too much about the OS.
Battery life is the most important factor for me these days in a phone , obviously with the implication that other aspects of the phone are also descent. I'm really baffled, bewildered, confused when someone buys a $600-$1000 phone when you can put up a very decent gaming PC for an equivalent amount with 10 times firepower. What bothers me is those reviewers criticizing the phone for not having a very high ppi or not achieving a certain benchmark score or not having a fingerprint reader etc when you won't be needing/using/noticing them anyway. In my opinion, the HAM2 is a very impressive phone; in fact one of the best along with 1+1 when it comes to getting more than what you're paying for. I have to say I'm surprised that the HAM7 doesn't seem to follow HAM2 pricewise !
medwatt said:
Battery life is the most important factor for me these days in a phone , obviously with the implication that other aspects of the phone are also descent. I'm really baffled, bewildered, confused when someone buys a $600-$1000 phone when you can put up a very decent gaming PC for an equivalent amount with 10 times firepower. What bothers me is those reviewers criticizing the phone for not having a very high ppi or not achieving a certain benchmark score or not having a fingerprint reader etc when you won't be needing/using/noticing them anyway. In my opinion, the HAM2 is a very impressive phone; in fact one of the best along with 1+1 when it comes to getting more than what you're paying for. I have to say I'm surprised that the HAM7 doesn't seem to follow HAM2 pricewise !
Click to expand...
Click to collapse
Agree 100% Value for money is what I'm after. That and great battery life. HAM2 comes through on both.
Hardware, OS, pixel density isn't as important, IF it is designed, optimized correctly. Other than benchmark programs,
I've run my HAM2 against an N6, S5, and there MIGHT be a blink of an eye difference in launching and running apps.
Specs on phones have far outstripped the software's ability to take advantage of the horsepower.
Why anyone spends 700 or more on a device, when there are mid range alternatives, that perform as well, I just don't get
it.
Grab a phone with lollipop on it and you will see what youre missing. And even better battery life. My e970 gets about 25% better battery life. Not to mention the new capabilities. This phone with L on it would be nothing short of amazing..
Moody66 said:
Grab a phone with lollipop on it and you will see what youre missing. And even better battery life. My e970 gets about 25% better battery life. Not to mention the new capabilities. This phone with L on it would be nothing short of amazing..
Click to expand...
Click to collapse
We've just got to be patient and wait for Tom to make our dreams come true. At this point, I don't even care about the Huawei update. I asked them about it again today on Instagram and they said it still has a release date of the first half of this year (can you get any more vague?) and they'll share info with us once they get more information. Not very promising if you ask me.
xordos said:
Have you tried un-check "Mount namespace separation" in SuperSU as mentioned here:
http://forum.xda-developers.com/showpost.php?p=56166409&postcount=14
Click to expand...
Click to collapse
This actually seems to have worked. Thanks for the find!
ScoobSTi said:
We've just got to be patient and wait for Tom to make our dreams come true. At this point, I don't even care about the Huawei update. I asked them about it again today on Instagram and they said it still has a release date of the first half of this year (can you get any more vague?) and they'll share info with us once they get more information. Not very promising if you ask me.
Click to expand...
Click to collapse
Agreed 100%. Looking forward to it. I can see this phone going three or four days if he manages a lollipop build. Not putting any faith into Huawei. And having the CC version makes the chances even slimmer. Only donated a few times to developers. He will for sure be the next. Lost hope anyone would even try.