Related
Hi @all,
i tried to find a solution for my problem, but i still couldn't find one.
My Desire HD:
ROM: CoreDroid HD GB 2.3.3 V5.0 & FROYO V3.3
Android Version: 2.3.3
Sense Version: 2.1
Baseband: 12.28e.60.140fP_26.04.04.17_M2
Kernel Version: 2.6.35.10-g1418c33
Software Number: CoreDroid Desire HD V5.0
My Problem:
I flashed my original ROM with the CoreDroid HD GB 2.3.3 V5.0. Everything works fine, except the camera. If I try to make a picture, it seems, that the color depth is like 8bit. -> See attached picture.
Flashing another ROM like RCMixHD_v5.6_ORG -> same problem.
Is there still existing a thread for this Problem or does some knows what i can do?
Greetz Andy
That looks awesome
A question: Does the live view of the camera show the same picture? Or is it correct and only changes when saving?
Anyway I would recommend a full wipe & reflash of the ROM. If that doesn't fix the problem, there might be a serious problem.
The picture looks also on live view so bad.
I tried different ROMs and for wipe datas i allways used the Full_wipe_1.3.zip
I don't think that it's a hardware problem, because with the original ROM it allwaxs worked fine before i flashed.
I did following things:
- had original ROM
- downgraded from Baseband 1.75.x to 1.32.x (followed Forum Thread HOWTO...)
- Radio S-OFF and ENG S-OFF
- Flashed new ROM CoreDroid
- Radio Update to 12.28e.60.140fP_26.04.04.17_M2
I hope this helps....
Thanks
Did you already try other ROMs? It might fix the problem, if you do a full wipe and flash a different ROM, if it is ROM specific.
Have you already tried to go back to stock ROM and checked whether the problem persists?
Yeah, i tried the RCMix ROM and the Revolution HD ROM.
I didn't try stock rom yet. Didn't still found the thread with stock ROMs, so, don't know where to download from.
Does someone knows the title of the stock ROMs Thread?
Its definetely a ROM issue . So my suggestion to you is :
- Either the issue come from not properly functioning ROM or not properly functioning KERNEL . By re-flashing them , I guess you would managed to fix the problem .
- If you have made a BACKUP before flashing your new ROM , you should just restore your previous ROM and maybe the issue would disappear .
Ok, so i'll make a Kernel Update and try another ROM or Stock ROM (tomorrow) and then post you my results.
I hope that works
I die a kernel update, Radio Update, flashed stock rom 1.32 but this didn't fix the Problem.
Any other ideas that can be a solution für my Problem?
Hi,
I have the exact same problem with my DHD. Was a solution ever found?
For me, 'till today, sadly not
I think the camera sensor is busted. If you already flash lots of different roms and still not fixing it, best probable guess would be the hardware itself.
Hi Everyone,
Long time listener, first time caller.
Over the last couple of months, I have tried virtually every ROM I can get my hands on for my DHD, and I always do a full wipe (format) of /system, /data, /cache, Dalvik, and .android_secure before install.
The only ICS ROM I can get working fully is Blackout, but it is Sense 3.6.
I have tried Viper, and *really* like it, but Bluetooth is broken (in 1.2.0, .1, .2, and .3)
That seems to be the case for me with Sense 4 ROMs (lite or full); if Bluetooth works, then WiFi is broken. If WiFi works, then Bluetooth is broken.
ROMs I've tried (latest):
Viper
Miui
Jellytime
ARHD
Blackout (S3.6, which is where I'm at b/c it works)
IceCold
IceSense
CosmicSandwich
Sabsa
codefireX
Kernels I've tried (various releases up to latest):
Beastmode
KangBang
Virtuous
So, I'd like to know if there is such a thing as a fully-working ICS/JB ROM with Sense 4? I cant seem to find one. W/o Bluetooth and WiFi, nothing can be considered a "daily driver", imo... especially w/o Bluetooth, if you know what I mean.
Thanks!
I'm baffled; all of those ROMs should have both BT and wifi fully working. What's your recovery and version?
EDIT: and what's your radio?
coolhands said:
Hi Everyone,
Long time listener, first time caller.
Over the last couple of months, I have tried virtually every ROM I can get my hands on for my DHD, and I always do a full wipe (format) of /system, /data, /cache, Dalvik, and .android_secure before install.
The only ICS ROM I can get working fully is Blackout, but it is Sense 3.6.
I have tried Viper, and *really* like it, but Bluetooth is broken (in 1.2.0, .1, .2, and .3)
That seems to be the case for me with Sense 4 ROMs (lite or full); if Bluetooth works, then WiFi is broken. If WiFi works, then Bluetooth is broken.
ROMs I've tried (latest):
Viper
Miui
Jellytime
ARHD
Blackout (S3.6, which is where I'm at b/c it works)
IceCold
IceSense
CosmicSandwich
Sabsa
codefireX
Kernels I've tried (various releases up to latest):
Beastmode
KangBang
Virtuous
So, I'd like to know if there is such a thing as a fully-working ICS/JB ROM with Sense 4? I cant seem to find one. W/o Bluetooth and WiFi, nothing can be considered a "daily driver", imo... especially w/o Bluetooth, if you know what I mean.
Thanks!
Click to expand...
Click to collapse
bananagranola said:
I'm baffled; all of those ROMs should have both BT and wifi fully working. What's your recovery and version?
EDIT: and what's your radio?
Click to expand...
Click to collapse
Same here, bluetooth is one of the few things that ALWAYS work (except for 4.2.1, but that's expected).
Are you wipping between flashes ?
Thanks for the replies, guys.
As I outlined above, yes, I am fully wiping b/t ROM installs - even restores - please see my method in first post.
I am using ClockworkMod Recovery (HBoot for booting) and have paid for ROM Manager, which entitles me to further updates to CWM than what is available on Play. I currently have 5.8.1.5 installed (CWM Touch).
The radio varies from ROM to ROM it seems, and I should have documented which version in each ROM, but right now, in Blackout, it is reporting 12.56.60.25P_26.10.04.03_M. <--- That number stays consistent, afaik, but the first letter will change (U and T, iirc).
When I say that Bluetooth doesnt work, specifically what happens is that it either doesnt pair with any device, or if it does pair, no sound will be transmitted or the pairing will only last for a second, maybe two seconds at most.
Deleted.
Sent from a dream.
The radio shouldn't be changing with each ROM unless you change it. But with that said, nothing seems out of the ordinary. You could try reflashing your radio manually? Other than that I'm out of ideas.
bananagranola said:
The radio shouldn't be changing with each ROM unless you change it. But with that said, nothing seems out of the ordinary. You could try reflashing your radio manually? Other than that I'm out of ideas.
Click to expand...
Click to collapse
I dont know much about that, but with that said, I just re-flashed Viper 1.2.3 and my radio now reads:
12.56.60.25U_26.10.04.03_M, which is different than it was above with Blackout.
I have not tried re-flashing my radio manually. I wouldnt know which one would give me a better chance of success...
bananagranola said:
The radio shouldn't be changing with each ROM unless you change it. But with that said, nothing seems out of the ordinary. You could try reflashing your radio manually? Other than that I'm out of ideas.
Click to expand...
Click to collapse
Once I flash a new ROM, the kernel and the radio are the same I had or the new ROM comes with its own kernel and radio?
Thanks in advance
roms do not come with radios tho they do have their own kernels. Radios are region based not rom based so there is no rom specific radio just what works best in your area.
Sent from my Desire HD using xda premium
Reinaldo33897 said:
roms do not come with radios tho they do have their own kernels. Radios are region based not rom based so there is no rom specific radio just what works best in your area.
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
Thanks for the explanation. So, if I bought my mobile in Spain, the radio is different if I had bought, for example in France?
depends on how close they are to each other whether same service is used in Spain as in France or if they are totally two different service. I would Google the carrier you use then see what radio they shipped with. Even in the radio thread you may find an answer to which radio is good for you in the area your at.
Sent from my Desire HD using xda premium
Reinaldo33897 said:
depends on how close they are to each other whether same service is used in Spain as in France or if they are totally two different service. I would Google the carrier you use then see what radio they shipped with. Even in the radio thread you may find an answer to which radio is good for you in the area your at.
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
Thanks a lot. I gonna do what you have said
you have tried almost every rom except for the ( pacman rom v18 ) its a jelly bean 4.1.2 based rom , i am stuck with it , every thing is working perfectly ( wifi , bluetooth , camera .... etc )
with some common tweaks i get an excellent battery life ,its even better than it was in the stock gingerbread rom ...
by the way , its non-sense rom
ghassan haddad said:
you have tried almost every rom except for the ( pacman rom v18 ) its a jelly bean 4.1.2 based rom , i am stuck with it , every thing is working perfectly ( wifi , bluetooth , camera .... etc )
with some common tweaks i get an excellent battery life ,its even better than it was in the stock gingerbread rom ...
by the way , its non-sense rom
Click to expand...
Click to collapse
I'll try it. Thanks.
What are the "common tweaks" for battery life?
coolhands said:
I'll try it. Thanks.
What are the "common tweaks" for battery life?
Click to expand...
Click to collapse
Visit Following link
http://forum.xda-developers.com/showthread.php?t=1189755
Hi there,
lately there have been OTA updates for CID HTC__023 and TELNZ001 which brought a new base (3.17) and some troubles (touch not responding) when using old (3.14) based custom roms.
The OTA brought a hboot update including an update to the touchscreen controller and therefore it only works correctly when using the corresponding 3.17 base kernel.
As slowly various CIDs are getting OTA updates to new base with new touchscreen controller firmware, these devices will have touchscreen issues on 3.14 based roms. But this kernel will help those people out.
adamnz had the initial idea in the thread linked above to try the 3.17 kernel on a 3.14 rom, so I followed up and created a flashable zip with all neccessary modules for those who are stuck with stock HTC ROM atm.
As I am running sense based RD-MIUI, I created a MIUI compatible boot.img, too which incorporates some ramdisk tweaks as init.d-support (busybox run-parts), volume-wake-deep-sleep-fix and run shelld service to prevent MiuiHome FCs.
03.02.2013: Base 3.17.781.2 (CID TELNZ001)
Grab the flashable zip from here: endeavoru_base_3.17.781.2_kernel.zip
Thx to adamnz for providing the OTA file and yumcimil for a full nandroid backup. :highfive:
Base 3.17.728.1 (CID HTC__023)
Grab the flashable zip from here: endeavoru_base_3.17.728.1_kernel.zip
Infos on different boot images
boot.img is the fully untouched 3.17 stock kernel while boot_miui.img has some tweaks as described above.
As the tweaks in boot_miui.img should have no drawbacks when used with non-miui-rom (and users reported that the stock one does not work but the miui one does),
boot_miui.img is the prefered kernel even when not running MIUI (if you do not want to repack).
Repacking
As JB sense roms around use the HTC stock kernel, which ramdisk is quite the same compared to this kernel, you can easily repack this kernel with the one from your favourite ROM. Please use the boot.img for this instead of boot_miui.img and do not forget to flash the zip file with the modules. This way you get all the rom-specific features and tweaks the rom chef included in his ramdisk.
Installation
Make a nandroid before, flash zip from recovery, flash boot.img from within the zip via fastboot, wipe cache and reboot.
Re: [KERNEL][Base 3.17.728.1] HTC JB Stock & MIUI
Thanks for this!
Sent from my One X running Blade v4.6.0. At a mere 240 MB, with tons of AROMA Mods and tweaks, this, is what you want.
Confirmed working with ViperX 3.3.2 using boot_miui.img, on HTC__023.
Touch works
cheers
Working with insert coin 15.1.1 with vid HTC_001!!
fantastic!
Works very well with Blade v4.6.0 (de-sensed) on HTC__023. Battery drain is less than 0.5% per hour in deep sleep.
[KERNEL][Base 3.17.728.1] HTC JB Stock & MIUI
marcosorano said:
Working with insert coin 15.1.1 with vid HTC_001!!
Click to expand...
Click to collapse
Yeah, this kernel works with all CIDs, but there are no real improvements. At least I did not notice any.
But for those with CID 023 and latest OTA update (3.17) this kernel allows them to use 3.14 based roms again. :good:
@all
Thanks for trying this one out and reporting back. Really much appreciated.
hi, i have touchscreen problems. part of my touchscreen not working. but im on 3.14.720 stock rom. and i didn't get the update yet. i want to try this flashable zip. what should i do? does the update fix touchscreen problems?
nevermore6990 said:
hi, i have touchscreen problems. part of my touchscreen not working. but im on 3.14.720 stock rom. and i didn't get the update yet. i want to try this flashable zip. what should i do? does the update fix touchscreen problems?
Click to expand...
Click to collapse
You would need to unlock your bootloader via htcdev, flash custom recovery and then flash the kernel zip in recovery and the kernel image in bootloader with fastboot.
nevermore6990 said:
hi, i have touchscreen problems. part of my touchscreen not working. but im on 3.14.720 stock rom. and i didn't get the update yet. i want to try this flashable zip. what should i do? does the update fix touchscreen problems?
Click to expand...
Click to collapse
What CID do you have?
The offical 3.17 base update only rolled out for CID HTC_023 atm. As this update brought something new to the touchscreen controller, this 3.17 kernel is needed to run 3.14 based roms.
If you have a CID different from HTC_023 (OR did not yet installed the official 3.17 OTA), running this kernel will not change anything regarding to your problem. But of course you can try, it will not cause any harm. Just follow the instructions in OP.
EDIT: Just overread the STOCK in your post. Need to grab a cup of coffee.
But gffmac is right: Just need to mention that unlocking the bootloader will wipe your /data-Partition (userdata).
nevermore6990 said:
hi, i have touchscreen problems. part of my touchscreen not working. but im on 3.14.720 stock rom. and i didn't get the update yet. i want to try this flashable zip. what should i do? does the update fix touchscreen problems?
Click to expand...
Click to collapse
It's unlikely to fix a touchscreen problem that was present on a stock rom especially if you haven't unlocked it previously. You maybe have a hardware problem with it
JohnnyInBriz said:
It's unlikely to fix a touchscreen problem that was present on a stock rom especially if you haven't unlocked it previously. You maybe have a hardware problem with it
Click to expand...
Click to collapse
Absolutely... Did not even think about that...
REALLY need to grab a cup of coffee. Now! :silly:
hi man!
can i use this kernel on my HOX?
ROM:Nocturnal JellySense+ v5.0 (3.14)
CID: HTC_044
thanks for reply
mrberni said:
Yeah, this kernel works with all CIDs, but there are no real improvements. At least I did not notice any.
But for those with CID 023 and latest OTA update (3.17) this kernel allows them to use 3.14 based roms again. :good:
@all
Thanks for trying this one out and reporting back. Really much appreciated.
Click to expand...
Click to collapse
With the stock kerneli ave some touchscreen problem when connected to usb now with your kernel it's solved
omer_hyltz said:
hi man!
can i use this kernel on my HOX?
ROM:Nocturnal JellySense+ v5.0 (3.14)
CID: HTC_044
thanks for reply
Click to expand...
Click to collapse
This kernel should work with every jb sense based rom.
marcosorano said:
With the stock kerneli ave some touchscreen problem when connected to usb now with your kernel it's solved
Click to expand...
Click to collapse
Really glad to hear that it helped you out. :highfive:
can this be worked on h boot unsupported version too or its just for the people who are already updated their h boot ??
Nani2000 said:
can this be worked on h boot unsupported version too or its just for the people who are already updated their h boot ??
Click to expand...
Click to collapse
Of course you need a jb compatible hboot the run this kernel.
Working fine on Venom ViperX JB 3.3.2
CID: H3G__001
HBOOT: 1.39
What's battery life using this on Viper like compared to Skydragon?
Hey guys,
So I flashed the Jellytime AOKP v7 on my DHD and the G Sensor is not working... I tried playing temple run and a few other games (I tilt the screen but nothing happens)... Do you have a solution??? If so please help!!
shad0wrid3r said:
Hey guys,
So I flashed the Jellytime AOKP v7 on my DHD and the G Sensor is not working... I tried playing temple run and a few other games (I tilt the screen but nothing happens)... Do you have a solution??? If so please help!!
Click to expand...
Click to collapse
Its an issue with auto rotation. You need to flash the rooted stock ROM (somewhere around here), do the basic setup & flash JellyTime again.
A simple search would have solved this problem without the need to make a new thread
What Guy said. But also: JellyTime AOKP is quite old. If it's AOKP you're after, there's another AOKP ROM running around now that's newer. You might want to check that out.
GuyInTheCorner said:
Its an issue with auto rotation. You need to flash the rooted stock ROM (somewhere around here), do the basic setup & flash JellyTime again.
A simple search would have solved this problem without the need to make a new thread
Click to expand...
Click to collapse
If you could find the ROOTED stock rom I would be very thankful
http://forum.xda-developers.com/showthread.php?t=1970972
I am using the new Oxygen JB 4.2.2 rom based on CM10.1 My problem is that I can't get GPS working. Any suggestions as to what I can do to fix that. Also will flashing the matching RIL for the RADIO I am using is that recommended on a CM 10.1 rom or not? Will it do any harm if I do flash the matching RIL?
heywheelie said:
I am using the new Oxygen JB 4.2.2 rom based on CM10.1 My problem is that I can't get GPS working. Any suggestions as to what I can do to fix that. Also will flashing the matching RIL for the RADIO I am using is that recommended on a CM 10.1 rom or not? Will it do any harm if I do flash the matching RIL?
Click to expand...
Click to collapse
RILs are only for pre-GB Sense ROMs.
ok thanks