Hello,
First post on this forum, took a lot of info from it, but I can't figure this one out by myself.
I have an issue with my camera. When I click on the camera icon, my screen blurs the same way as when you go to landscape mode, I get the B&W image of the camera icon, and the I get the message saying:
Sorry!
The application Camera (process com.android.camera) has stopped unexpectedly. Please try again.
~Force close
The same happens for the camcorder. I have tried both soft and hard resets, with and without sd card, booted with and without sd card.
I have a Rogers HTC Magic, so it's a 32A version. I'm running CyanogenMod 4.0.4 with CyanogenMod 1.4 RecoveryImage. I rooted my phone using FlashRec 1.1.2 (http://zenthought.org/content/project/flashrec). Ported 4.0.4 using bcrook's method (http://forum.xda-developers.com/showthread.php?t=544854), using the version based on 4.1.11.1.
I have done no 'crazy' things except for these. When I still had the stock Rogers ROM on there, I had no issues at all. This was less then 24 hours ago. I have installed a couple of apps from the market, but nothing intense.
I started having the issue with my camera the moment I started using the new ROM. However, even after re-flashing it (twice), the issue remains. I have pushed the 'Camera.apk' from the CyanogenMod 4.0.4 to my sd card and installed it, no luck.
As is clear, the issue is with the camera application. I can't use BarcodeScanner, since it relies on the camera as well. Same message shows up.
Is there any parent process/application that I can reinstall to make this work? I've redownloaded and reflashed 4.0.4 and the port based on 4.1.11.1, no luck.
FASTBOOK info
MODEL: PVT 32a Ship S-ON H
HBOOT: 1.33.0009
RADIO: 3.22.20.17
~Molochmaster
update your rom. Cyan has 4.1.11.1 now..
I was planning on using a stable release only, but I'll try 4.1.11.1 tomorrow! Hopefully it will fix something!
Flashing to 4.1.11.1 and applying bcrook's kernel patch fixed the issue for me. Thanks! Mods can close the thread now to prevent hijacking.
your issue was the kernel.
4.0.4 is a cupcake build. and the 4.1.11.1 kernel is a donut build.
so i guess that was the problem.
Hi, everyone:
My phone is Vodafone G2 Magic 32A, a problem has confused me for a period. When i tried 1.6, the problem occurred.
With any 1.5 rom, the phone work well. But with 1.6, 2.0,2.1 rom, the phone always auto reboot or crashed, whether i use the phone or not, and i think the reason is not a specific operation or software. I have tested all the rom i can find, and change the spl and radio for several times, but the problem still have. And the same problem also confuse other people. We have a group to discuss how to solve the problem, we all think the reason is not the hardware error, because the 1.5 version always work fine.
Here is some infomation of my G2 phone
SAPPHIRE PVT 32A ENG S-OFF H
HBOOT-1.33.2010 (SAPP10000)
CPLD-12
RADIO-3.22.20.17
Jun 2 2009, 17:27:03
we hope someone can help us to solve the problem
Hi，my phone is TIM，the information is
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.33.0008(SAPP10000)
CPLD-12
RADIO-3.22.20.17
the problems is the same as yours.
Very sad about it.
me too!
but,I have changed my phone SPL2007 did not crash when the FLASH ROM.
which kind of rom did you flash?
The same problem i had, as lots of people.
Unless rom 1.5, other rom include 1.6, 2.0 and 2.1, it made the G2 crashed and auto reboot.
We have doubted about the recovery img, spl, radio, and so on. And someone have tested all of them, the problem have still being.
This is my G2 information:
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.33.0009(SAPP10000)
CPLD-12
RADIO-3.22.20.17
May 8 2009,21:02:32
Hope someone can help us.
Thanks.
Same problem!
HTC G2
, is anybody can help us?
Or teach us a way to find the really problem
for example: a program running in our Magic phone, when the phone crash or reboot, it will record some useful infomation.
I had a similar problem, my G2 freezed totally when used other roms.
In my case, it seemed to be the kernel. Using 2.6.27 worked fine.
so vanilla android 1.5 worked, and GyD and MyHero worked, but not others.
When I ran MyHero, I also noticed that my CPU didn't seemed to scale.
I ended up substiting my phone for another of the same model.
using "adb logcat" didnt give me any information, the error did never get logged.
Hey, got the. Same. Phone running on. Android. 2.1 for a while now
You have too flash the. 32b rom. And. Then. Before booting the 32a port. Witch. Provided. On the same site where you downloade the rom from
I had. The same problem,
Good luck,
hi, i have 32A spl1.33.2010 recovery 1.5.2H radio 3.20.22.17
i had similar problems with stuck at htc boot screen or crash part way through set up, i was wiping and partitioning my sd card 96/512/fat32.
what worked for me was upgrading my spl and recovery to the above,
do back up
wipe- data/factory; davlik-cache;sd ext partition,
no partitions on sd card,
flash rom then flash 32A port then reboot system
currently enjoying ahmgsk port of eugenes espresso/hero 2.1 rom
i hope this helps??
Hello, iv got similar problem, on 1.5 work fine too but on on ROMs above 1.5 reboot my phone when i i use my camera i can do 1 picture but when i want to delete it phone just reboot, on google goggles too. I try Cyanogen ROM, SuperD and 1 ROM on android 2.x version. Someone maybe have same problem and fixed it ? or someone know how to fix it and btw i wiped data i try to install same ROM several times too and nothing helped
I'm having big problems with my 32A and any 1.6 ROM. Never tried changing the SPL though, but I've tried anything else: partitioning, installing different ROMS, almost every combination of wipe/reset and so on.
How could changing the SPL affect stability of a ROM?
Hello all,
I have just got a new HTC Dream and proceeded to do the following :
I started by flashing dreaimg.nbh drc 7, then a rooted using telnet following the instructions on cyanogen wiki. I then flashed the new radio 26i and the death spl. I have installed cyan 5.0.7t2 plus google apps.
Now however when I boot it up it is staying on the g1 boot up screen and not continuing. Earlier versions of cyanogen mod work but not 5.0.7 for some reason.
Any ideas?
i just had the same prob. im on moto droid. comming from droidmod 1.0 after reboot after flashin newest cgnmod it jut hangs on moto logo. went back to last backup
Cyan doesn't support the droid does it? :S
Mraellis said:
Hello all,
I have just got a new HTC Dream and proceeded to do the following :
I started by flashing dreaimg.nbh drc 7, then a rooted using telnet following the instructions on cyanogen wiki. I then flashed the new radio 26i and the death spl. I have installed cyan 5.0.7t2 plus google apps.
Now however when I boot it up it is staying on the g1 boot up screen and not continuing. Earlier versions of cyanogen mod work but not 5.0.7 for some reason.
Any ideas?
Click to expand...
Click to collapse
Make sure the death spl was installed and make sure to wipe before installing. Install cyan and then gapps without rebooting in between.
I usually have to install gapps after cyanogen. Some people before, some people after. It's kinda odd.
Also, for the droid, there is a cyanogenmod. Dunno if CM5 is on there yet, though. Don't really know anything about the Droid.
I read somewhere that there was a bug in 5.0.7 where you can't use the terminal method to install it, you have to use amon-ra recovery instead (I can't find the page anymore)
I think CM 5.0.8 fixes this
Hello,
I can not find similar topic in the HELP forum so let me start it (at least for new users of XDA forum).
At the very beginning I would like to thank bilal_liberty for all his work given for Liberty ROM. Same time I want to thank all participants of his success - all developers, testers and helpers for their time and patience..
Now, my problems:
1) I can not run WIFI hotspot. The icon is working, working and... doing nothing.
2) From time to time I can not run WIFI connection in my home. Of course everything is "ON", I tried to restart the phone, turn of the data transfers and some other tricks - the connection was working just after installing the ROM, but it is a lottery.
3) I have an issue with memory: I can't see the "SDCARD" memory - only when in TWRP mode, after mounting the SDCARD drive. When connecting in normal mode through USB - I can see only about 2 GB.
Is there any solution for those problems?
HTC One S(4), s-off, TWRP 2.7.0.1, hboot 2.15 (I don't believe 2.16 will change it but "if" - I'll upgrade, of course...
Thanks for any help.
Hello xklonik and welcome to our community,
to answer your questions in descending order.
3) Sixth Sense is not compatible with hboot 2.15, so that's why you have problems with your sd card inside the rom (recovery is somewhat, "standalone")
2 + 1 ) These problems are well known issues and reported over the development thread. Developers are working hard to try and fix these issues but it's also a fact that without the source code of the sense roms, there's only so much we can do.
Also maybe because of your incompatible boot, these issues are getting worse.
There are two solutions:
a) Either upfrade to hboot 2.16 (with the procedure at maximusHD thread)
or if you are scared of this procedure
b) stay on hboot 2.15 and use LibertyMAX instead (both hboot supported and is more stable in my opinion - and by stable I mean no weird wifi issues whatsoever)
Other than that, both roms are excellent and it's really a matter of preference which one to choose. :good:
ChrisAr said:
Hello xklonik and welcome to our community,
to answer your questions in descending order.
3) Sixth Sense is not compatible with hboot 2.15, so that's why you have problems with your sd card inside the rom (recovery is somewhat, "standalone")
2 + 1 ) These problems are well known issues and reported over the development thread. Developers are working hard to try and fix these issues but it's also a fact that without the source code of the sense roms, there's only so much we can do.
Also maybe because of your incompatible boot, these issues are getting worse.
There are two solutions:
a) Either upfrade to hboot 2.16 (with the procedure at maximusHD thread)
or if you are scared of this procedure
b) stay on hboot 2.15 and use LibertyMAX instead (both hboot supported and is more stable in my opinion - and by stable I mean no weird wifi issues whatsoever)
Other than that, both roms are excellent and it's really a matter of preference which one to choose. :good:
Click to expand...
Click to collapse
Hi ChrisAr.
Thanks for your reply.
I'm not scared with the hboot change I just couldn't see any reason to change it if the ROM (at all) was working. Now I see that my issues can be caused by this tinny missing so I'll update hboot after working hours
I'll update this thread after the upgrade.
Thanks for help.
No problem, glad to help
Be aware though. After upgrading hboot(following carefully MaximusHD's instructions), you must reflash recovery with 2.16 hboot support which can be found here -> mdmower.cmphys.com/twrp-ville/ (Cannot post full link due to post restrictions)
Just be sure to flash the one under /data/media storage (HBOOT 2.16.0000 only) header.
:good:
so.. there is a problem...
without any issue I succeed with hboot update to 2.16... however..
as you suggested, I also downloaded and upgraded TWRP with hboot 2.16 support (both, twrp-2.7.1.0a-ville-dm, twrp-2.7.1.2-ville-dm)...
unfortunately, after reboot to TWRP, I can not "mount SDCARD", which previously was available in hboot 2.15 & TWRP 2.7.0.1 in MOUNT menu..
also - I don't know why - I could not find my ROM on SDCARD and actually, I could not access the card at all...
so, I can not install anything.. I can boot to bootloader or TWRP, I can communicate with the cellphone via fastboot (I can change TWRP to any version I want)... I tried to flash-in my old version of TWRP, properly working with 2.15, but under 2.16 I have only 48 MB of free space when mounting the SDCARD
any advice?
I have:
***TAMPERED***
***UNLOCKED***
VLE PVT SHIP S-OFF RL
CID-HTC__032
HBOOT-2.16.0000
RADIO-1.20.50.05.16
OpenDSP-v33.1.0.45.1128
twrp-2.7.1.2-ville-dm
-------------------------------- edit ----------------------------------------
ok, I found the way out...
since my connection with phone works perfectly, only one way to deal with lack of space and no ROM on SDCARD was to push it via adb
adb push yourrom.zip /sdcard/yourrom.zip
the rest after this was easy (recovery -> install ROM -> configure -> enjoy)...
thanks again for links and support!
xklonik said:
so.. there is a problem...
without any issue I succeed with hboot update to 2.16... however..
as you suggested, I also downloaded and upgraded TWRP with hboot 2.16 support (both, twrp-2.7.1.0a-ville-dm, twrp-2.7.1.2-ville-dm)...
unfortunately, after reboot to TWRP, I can not "mount SDCARD", which previously was available in hboot 2.15 & TWRP 2.7.0.1 in MOUNT menu..
also - I don't know why - I could not find my ROM on SDCARD and actually, I could not access the card at all...
so, I can not install anything.. I can boot to bootloader or TWRP, I can communicate with the cellphone via fastboot (I can change TWRP to any version I want)... I tried to flash-in my old version of TWRP, properly working with 2.15, but under 2.16 I have only 48 MB of free space when mounting the SDCARD
any advice?
I have:
***TAMPERED***
***UNLOCKED***
VLE PVT SHIP S-OFF RL
CID-HTC__032
HBOOT-2.16.0000
RADIO-1.20.50.05.16
OpenDSP-v33.1.0.45.1128
twrp-2.7.1.2-ville-dm
-------------------------------- edit ----------------------------------------
ok, I found the way out...
since my connection with phone works perfectly, only one way to deal with lack of space and no ROM on SDCARD was to push it via adb
adb push yourrom.zip /sdcard/yourrom.zip
the rest after this was easy (recovery -> install ROM -> configure -> enjoy)...
thanks again for links and support!
Click to expand...
Click to collapse
Sorry I didn't see your post earlier. I was away on vacation.
In that time, sixth sense got 2.15 support.. Irony
Not sure why you had that problem. Maybe you had to perform a full wipe (from the recovery options) to force re-partitioning. Old hboot had created different partitions on phone's memory and you had to create them from scratch, for the new hboot.
Also I assume you know that when you change hboot, you have to re-install also everything from scratch since everything installs according to hboot. If you just upgraded hboot, it would not work as expected if you just left the old installation there.
Anyway, glad to hear this worked for you and that you also found a workaround with "adb push" by your self. Good job :good:
Enjoy this awesome ROM. (Just flashed it too this morning) :highfive:
yeas... actually I did the instalation agait too..
and unfortunately wifi still wont work
btw. I'm always performing full wipe, so have no idea what happened then..nevertheless, I've full space and rest of toys, just without wifi and hot spot, what in fact, eliminates this ROM.. :/
unfortunately 2) no one answered my mail regarding any ROM supporting all One S features (camera, wifi, hotspot, BT) and Sense 6 on newest kitkat... so I'm still in the oblivion.. waiting for some light..
just to confirm - build 106 - after changing 1.35a.32.45.27, WCNSS, ADSP, wifi & hotspot still not working,
what is interesting, previously the wifi icon only blinked - currently "scanning" & "disconnecting" subtitles are visible under this icon...
also previously just right after installing I could connect to my network and wifi was turned off just after authorisation and few next screens..
now with new 1.35a.32.45.27, WCNSS, ADSP I can not join at all..
I've been following your posts on the development thread.
This issue is really weird...I wanted to write about different WCNSS versions (some people flashed it from the Viper ROM) but I couldn't post due to post count restriction. Anyway, bilal noticed that too in his recent post. I have flashed everything you flashed and only reverted to radio 1.20 but with hsdpa fix (it is included in one of the flashable radios, don't know if it's included in the version you downloaded)
WiFi is working perfectly for me. Only this "keep always on" issue.
Hi everyone,
First off thanks to bilal for his amazing work, second I hope I am not off topic since this is a help thread for Liberty SixthSense.
After reading the entire development thread on this ROM, I still can't figure out how to install it on hboot2.15. I get a feeling that there is a different way to install this rom on 2.15, or I'm missing something.
So yes, I download the zips of r106 version and the radio 1.20 version. But afterwards I just do as I would do with any other ROM? I mean full wipe, dalvik cache wipe, recovery cache wipe, and then install from zips? and if so, which should be instlled first, the radio or the whole rom?
Mindue, I am noob at this, so I don't understand everything I've read so far and this would be the only way I know to install a rom.:silly:
quick checklist:
- S4
- recovery TWRP 2.7.1.0 the one from Cyanogenmod 11 since I'm on this rom now.
- S-OFF
- hboot 2.15
Hi!
I think you are good to go. Since you don't know any other way to install a ROM (adb sideload/push), I would say to be carefull what you wipe because you might erase the OS and you won't be able to transfer the zips from your computer (regularly, like a flash drive).
Other than that everything is good...recovery is for right hboot(since you already have cm11; official I suppose which is for 2.15)
Flash radio
Flash ROM -> choose full wipe during install
Never heard of recovery cache wipe so don't mess with that
Best of luck! :good:
ChrisAr said:
Hi!
I think you are good to go. Since you don't know any other way to install a ROM (adb sideload/push), I would say to be carefull what you wipe because you might erase the OS and you won't be able to transfer the zips from your computer (regularly, like a flash drive).
Other than that everything is good...recovery is for right hboot(since you already have cm11; official I suppose which is for 2.15)
Flash radio
Flash ROM -> choose full wipe during install
Never heard of recovery cache wipe so don't mess with that
Best of luck! :good:
Click to expand...
Click to collapse
Thank you! I will try and see where it leads me, if it fails I believe I can put back the cm11 right ? even with the new flashed radio.
As far as I know, there are no problems with cm11 and radios...but even if there is, you can always flash an older radio...but 1.20 is the recommended for our device in general.
Glad I could help :good:
Ok, so I try to flash the radio (before full wipe and rom flash) but it fails, I get the followings:
checking for MD5 file > no MD5 file found
verifying zip signature > failed
any ideas to where I went wrong?
LATER EDIT: scratch that, the problem was the 'ZIP signature files verification' box should have been unticked and thus no more md5 file required. --> radio flashed! now on 1.20. later I will try to flash the liberty rom. update afterwards
PS. found this in another thread:
"an md5 is not "added to a file", nor is it "a part of a file". An md5 is merely a hexadecimal readout of the contents of that file.
Here's how it works: A file is created, in our case it is a zip file. The creator or publisher of that file uses an md5 generator to generate the md5sum, which as I said before, is just a numerical readout (like a fingerprint) of the contents of that file. Now the end user has a tool to make sure that the file hasn't been compromised during a download or transfer. Using an md5 checker is a simple way to verify that the file is uncompromised. Input the md5 given by the publisher into an md5 checking app, then the app calculates the md5 of the file you've downloaded, if they match you know the file integrity is good."
Just installed the ROM, everything works fine, very fast and smooth, no WiFi problems, HOPEFULLY no radio problems (I previously had Venom Viper Sense5 and had major issues with radio and lots of random restarts).
ArcsONE said:
Just installed the ROM, everything works fine, very fast and smooth, no WiFi problems, HOPEFULLY no radio problems (I previously had Venom Viper Sense5 and had major issues with radio and lots of random restarts).
Click to expand...
Click to collapse
Glad to hear that.
I had also these random restarts, but they are gone now.
Enjoy
Still new here so can't post in the dev thread, but...
Installed the latest version (clean install), everything works solid. Hotspot works as before - have to turn it on, then reboot and Wi-Fi mostly works but occasionally needs restart to work. Other than that, everything is stable and quick, very happy with the ROM. As I primarily use 3G and don't rely on Wi-Fi as well as can use USB tethering instead of Wi-Fi hotspot, I'm not that annoyed by these issues.
However - on r107, I tried out the ElementalX 7.0 kernel as well but as I experienced issues with touch screen, I searched the thread and found a fix which turned out to be a special kernel. Therefore although the kernel in the ROM was updated and now there are no touch issues with the default kernel, the ElementalX kernel also needs updating. Really miss DT2W but a responsive touchscreen is more important to me.
Tried the kernel now after r111 install but the touch problem is still there so had to revert to default kernel.
I hope the kernel's developer sees this and can release an update :fingers-crossed:
no recent apps
I cant find the recent apps in this system
Problems
Hey guys, first post in this forum. I'm a total noob when it comes to rooting and roms and all this stuff, but if I didn't try it I would always be, so I tried this rom on my htc one s.
Several problems, I may have screwed up of course, I followed some tutorials, so I have this rom, but I am S-On, and my hboot is 2.15, I think that is what is causing me problems (SD card not recognized, meaning, no storage space, wifi problems, can't log in to google play).
But I can't get S-off, I've tried every single way, and something always goes wrong, I don't know what to do now, I think the solution would be to change to hboot 2.16, but I just can't do it, probably need to be S-off? No idea, would love to hear some feedback, I'll leave you with whatever it says on my bootloader.
TAMPERED
UNLOCKED
VLE PUT SHIP S-ON RL
HBOOT- 2.15.0000
RADIO - 1.15.50.05.29 (tried changing it, can't as well.)
OpenDSP - v31.1.0.45.0015
Plese help me guys, really don't know what to do, I think I might have accidentally deleted the stock Android.
Much thanks
Anyone else having problems with audio quality in calls? Any fix? I found liberty rom v2 on an italian forum, it says audio quality it's fixed in that, has anyone tried it?
VLE PVT SHIP S-OFF RL
CID - 11111111
HBOOT - 2.16.0000
RADIO - 1.20.50.05.16
OpenDSP-v33.1.0.545.1128
eMMC-boot