I searched all over the internet and couldn't find a solution for this problem. I'm getting this "warning: camera failed" issue.
I've tried EVERYTHING, and nothing solved my problem. Can someone help me?
I've tried:
Wipe / Factory Reset
ICS Stock ROM / GB Stock ROM / MIUI ROM
Download other camera App
Clear Camera Data
Format
Thank you.
update.
BUMP.
My country can't support imported smartphones.
I'm in a trap. Please, help me someone =(
Thanks in advance.
Did you try anything with camera FW?
Wysyłane z mojego GT-I9100 za pomocą Tapatalk 2
gaeilge said:
Did you try anything with camera FW?
Wysyłane z mojego GT-I9100 za pomocą Tapatalk 2
Click to expand...
Click to collapse
not at all. Should I try updating it?
You may try reflashing it even with the same FW. Just to "renew" FW because it could get corrupted. Sometimes it helps.
Wysyłane z mojego GT-I9100 za pomocą Tapatalk 2
I couldn't find any thrwad teaching how to renew the camera firnware, so I accessed the secret menu of the camera ( *#7412365#) and pressed phone to com write. Got a invalid version error. Do you guys know any thread that will show me how to find the correct version? Thanks!
you may reflash your camera with any FW you want (sometimes it just won't work) or just "refresh" it by flashing the same FW you originally had (in case it's corrupted). it's your choice and to find more help about it you may follow this link:
http://forum.xda-developers.com/showthread.php?t=1098834
here a little help about what is what:
http://forum.xda-developers.com/showpost.php?p=18014779&postcount=1050
and most importantly, the source:
http://4pda.ru/forum/index.php?showtopic=236715&st=200#entry8681010
(you may use google translator, it's quite ok)
now, flashing:
first check which FW you have in your camera (like SCEF02, OMEF01 etc). than download proper zip from this site:
http://turbobit.net/download/folder/1112392
unpack the FW you want (.bin file like RS_M5LS.bin) and copy it to \sdcard. later on you go to *#34971539# and use "Phone to CAM FW Write" option to write chosen FW to camera. wait a little bit and restart your phone. that's it. just check again which FW you have and if camera works.
if this method didn't work you may use quite the same one but improved a little by a 4pda.ru user named Pako777. he prepared his own factorytest.apk but to use his method you need ROOT. if you'd need me to, I can translate it to you step by step.
I had the same problem and it was fixed by changing the kernel. I guess a particular version of siyah was giving that problem.
Most probably this should work.
well, as vitorsubs wrote in the very first post hetried different ROMs so perhaps different kernels too...
gaeilge said:
you may reflash your camera with any FW you want (sometimes it just won't work) or just "refresh" it by flashing the same FW you originally had (in case it's corrupted). it's your choice and to find more help about it you may follow this link:
http://forum.xda-developers.com/showthread.php?t=1098834
here a little help about what is what:
http://forum.xda-developers.com/showpost.php?p=18014779&postcount=1050
and most importantly, the source:
http://4pda.ru/forum/index.php?showtopic=236715&st=200#entry8681010
(you may use google translator, it's quite ok)
now, flashing:
first check which FW you have in your camera (like SCEF02, OMEF01 etc). than download proper zip from this site:
http://turbobit.net/download/folder/1112392
unpack the FW you want (.bin file like RS_M5LS.bin) and copy it to \sdcard. later on you go to *#34971539# and use "Phone to CAM FW Write" option to write chosen FW to camera. wait a little bit and restart your phone. that's it. just check again which FW you have and if camera works.
if this method didn't work you may use quite the same one but improved a little by a 4pda.ru user named Pako777. he prepared his own factorytest.apk but to use his method you need ROOT. if you'd need me to, I can translate it to you step by step.
Click to expand...
Click to collapse
Ok, I did understand all your instructions and threads, but I am afraid of ruinning it all. I'm not used to this kind of update. My infos are:
CAM FW Ver: SCEE09
Phone FW Ver: TBEC28
What is the best FW Ver to download, so it will work properly?
Should I downgrade to gingerbread before i do it?
Thanks.
EDIT -> OMG IT WORKED, I WISH I COULD BUY YOU ALL A BEER. OMG, YOU GUYS ARE SO AMAZING. OMG, WORDS CAN'T DESCRIBE MY HAPPINESS.
good, good, I'm happy for you too.
I'm just sorry I couldn't reply to your post earlier so you wouldn't worry... I overslept it... Overslept it much too much . Anyway, now you know and most importantly it worked. Best of luck!
Wysyłane z mojego GT-I9100 za pomocą Tapatalk 2
Related
Descriptions :
I modified the software FloatingTouch from Xperia Sola, to maximize the sensitivity of the touchscreen.
Installation via CWM
Download here http://www.mediafire.com/download.php?epi0mtxms8yiegi
After Installation Open Root Explorer. Open build.prop with text editor in the system, and copy this code :
# Set to 1 if floating touch available
ro.floatingtouch.available=1
Please feedback after installation
I think it improves the touch screen a little bit. Before i use this,if i swipe between the home screens,sometimes it will look like it move to the next homescreen,but it will just stay at the same homescreen.i will need to swipe a little bit harder to chnge homescreen. I hope u understand what im saying here.
After i try, i just use a little bit force and the homescreen changes. Its almost as smooth as GB
Sent from my LT18i using xda premium
Just checking, will this work on the latest 4.0.4 rom?
So, since our displays do not have the hardware required for FloatingTouch, thus they cannot make any use of AirTouch Service, what exactly does this mod do?
iR¡[email protected]!* via Tapatalk 2
I flash it with cwm then boot loop
can it work on 4.0.3??
I had flash it on my stock ics 4.0.3 arc s and it's seem smoother... i don't know if it really work but no bootloop...
so far i see have that not so much effect on ICS 4.0.4
Wow its work !!
Much effect to gb
Wysyłane z mojego LT18i za pomocą Tapatalk 2
Rizal Lovins said:
Descriptions :
After Installation Open Root Explorer. Open build.prop with text editor in the system, and copy this code :
# Set to 1 if floating touch available
ro.floatingtouch.available=1
Click to expand...
Click to collapse
my friend i dont understand this part
i open build.prop and copy and paste # Set to 1 if floating touch available ro.floatingtouch.available=1 ANYWHERE i want or need to paste into the right place??
pls help 10s
Tested on 4.0.4, its work!
flash with cwm, open build.prop and at the botom give ro.floatingtouch.available=1, reboot and take your screen cleaner, make a test!
iridaki said:
So, since our displays do not have the hardware required for FloatingTouch, thus they cannot make any use of AirTouch Service, what exactly does this mod do?
iR¡[email protected]!* via Tapatalk 2
Click to expand...
Click to collapse
Iridaki may have a point here, maybe it is just wishfull thinking and it seems smoother in our dreams?
datagubben said:
Iridaki may have a point here, maybe it is just wishfull thinking and it seems smoother in our dreams?
Click to expand...
Click to collapse
Actually yes, it is a placebo effect.
The service doesn't even run on our phones, the apk does not even appear installed.
It really doesn't require an expertise to understand that this does not work.
If you want, you could also try adding this line to your build.prop:
Code:
ro.smoothtouch.display=1
The effect should be just about the same.
this is like porting the eXmor R sensor to the good old X10, its a hardware thinggy and no offense, this does nothing to our ARC/S.
iridaki said:
Actually yes, it is a placebo effect.
The service doesn't even run on our phones, the apk does not even appear installed.
It really doesn't require an expertise to understand that this does not work.
If you want, you could also try adding this line to your build.prop:
Code:
ro.smoothtouch.display=1
The effect should be just about the same.
Click to expand...
Click to collapse
May I know which part of build.prop should I add this line?
Just after in.appropriatetouch.ing = 1
Ultimate Notification LED fix for Xperia (ICS 4.0.4, 4.1.B.0.587)
Introduction
One of the most annoying bugs in the everyday use of Sony's official ICS firmware version 4.1.B.0.431 (and later, including v4.1.B.0.587) is that the notification LED only works for missed calls, and it doesn't notify anything else anymore.
Ironically, the previous beta firmware ICS 4.0.3 v4.1.A.0.562 showed a specular bug: the notification LED didn't notify missed calls, but it was working for everything else (SMS, Email, ..).
The "Ultimate Notification LED fix"
I've got around fixing this bug by reversing and doing a minor change in a 4.1.B.0.587 framework file (services.[o]dex).
The patched file has the notification LED working for everything as it was in GB firmware: the LED now blinks for missed calls, sms, emails, and any other application showing LED notifications (eg: K9-mail, Whatsapp..).
This patch works on all Xperia devices with 4.1.B.0.587 firmware, and it has been tested initially tested on a Xperia Mini Pro sk17i.
Disclaimer
These files come with no warranty, express or implied.
By downloading and using files linked in this page you express your understanding that you use those files at your sole risk.
No one can be held responsible for any damage directly on indirectly related to files linked in this page.
If you flash something to your phone you must remember that there's always a minimal chance that something goes wrong: you know it, I can't be held responsible if your phone gets wrecked, if your working LED flashes during a work meeting and you get fired, or anything else.
Downloads and Install Instructions
To install this fix you have to be in a stock ICS 4.0.4 firmware v4.1.B.0.587, with root and ClockWorkMod (CWM) recovery installed.
To install the fix simply download the right package for you, and:
make sure your phone is charged! It's always safer when you need to flash something.
put the downloaded ZIP it in the root of your SD Card
reboot into CWM recovery
Do a Nandroid backup using CWM ("backup and restore" => "backup"): you shouldn't end in a bootloop if you download and apply the proper file, but it is a good practice to a CWM backup before applying mods and patches, so you can easily restore it and go back if anything goes wrong!
did I mention to do a Nandroid backup?
choose "Install ZIP from sdcard" => "Choose zip from sdcard"
browse to the ZIP in your SD Card
choose apply and reboot device.
enjoy a properly working led
The right package to download for you depends on your current system framework files status.
Use the following list and infos to find the proper download for you:
If you have an Xperia device on stock ICS 4.0.4 v4.1.B.0.587, and never applied other LED patches: install Busybox if you don't have it already, and download the following universal patch Ultimate_4.1.B.0.587_Notification_LED_FIX_UNIVERSAL_stock_rom_by_zxp.zip.
Note: Busybox must be installed on your device before installing this package, or it will not work. The patch scripts expects Busybox to be installed into /system/bin or /system/xbin.
If you never applied any patch and don't know what to download, this is the file you want!
Why: it is smaller, and only replaces the services.odex file with the patched one, that's all you need; the services.odex is automagically generated in your device, that's why Busybox is used, and this is what makes this package "universal".
If you your device currently has arcatarc's fix applyed: download Ultimate_4.1.B.0.587_Notification_LED_FIX_by_zxp_FOR_arcatarc_fix_users.zip
Why: if you used on arcatarc fix, this package will restore 4.0.B.0.587 framework files along with the patched services.odex, because arcatarc's fix installed the old 4.1.A.0.562 framework files and this change needs to be reverted.
If you are using a stock deodexed ICS 4.0.4 v4.1.B.0.587 firmware: download Ultimate_4.1.B.0.587_Notification_LED_FIX_FOR_DEodexd_roms_by_zxp.zip
Why: it will replace the services.jar with the patched classes.dex inside.
This works for all Xperia Devices, including but not limited to the Xperia Mini Pro sk17i/a.
If you are using the old firmware v4.1.B.0.431: you are lucky, I originally released the Ultimate LED FIX for firmware 4.1.B.0.431, you can download it from the old version thread.
If you are using a newer firmware: you have to wait for Sony to release this firmware for my sk17i, so that I can port the patch over the new version, or wait for someone to port it.
Background info, closing notes and thanks
As already specified this patch is based off stock 4.1.B.0.587 framework: I simply deodexed with baksmali, manually edited one .smali file to change the offending code that prevented the LED to work properly, and packed everything back.
I hope to find time to post very soon a Tutorial on how to apply the fix yourself, for educational purposes and to help less experienced people to port it over newer versions.
Experienced users should be able to compare the stock 587 baksmali-ed services.odex and the patched one to find the small change, and port it over new versions without the need of my forthcoming guide.
If you happen to port this patch to a newer firmware please post a link to your thread, so that I can add it in this post to inform users with such firmware that a patch exists for them.
If you want to inform other users of this patch please link back to this thread and don't simply re-upload/re-post a package. A link to this thread is the only way to be sure that users chose the proper package and can be updated if there is the need for a new/updated patch.
Bugs & Known Issues
This patch is now used by thousand of users without any reported issue or strange behavior.
If you install this patch and you end in a boot loop it means you have applied the wrong package. Please re-read the download info & instructions, and apply the proper zip. Period.
If you find any real problem please post it, and I'll update this section.
Changelog
2012.10.04 (current): applied my fix to the new firmware version 4.1.B.0.587, and released specific packages for this firmware version. The universal package now supports busybox both in xbin and sbin.
Additional Notes for those coming from arcatarc's fix
If you have used arcatarc "partial" fix you may have noticed that it had 2 major user visible problems:
the LED notification for missed calls was not working
it showed a single white blink when some notifications appeared in the statusbar: eg the Xperia Keyboard "choose input method" notification caused a white LED blink each time it appeared.
This patch doesn't have those problem, everything (seems!) to work as it should!
was waiting for [.587] Awesum
Bad thing is, that this led fix works only with stock sms app. I use other sms client, and with this, led don´t blink.
happyBOY78 said:
Bad thing is, that this led fix works only with stock sms app. I use other sms client, and with this, led don´t blink.
Click to expand...
Click to collapse
Maybe the problem lies in the alternative sms client? This fix is proven to work with email, gmail, sms, whatsapp, missed call... not only stock sms!
PS: at least this was true for .431, I appreciate feedback on the fix on this new .587 firmware because something may have changed.
zxp said:
Maybe the problem lies in the alternative sms client? This fix is proven to work with email, gmail, sms, whatsapp, missed call... not only stock sms!
Click to expand...
Click to collapse
Will this work with XS app port?
If so can I use in my rom?
Developing an ICS rom
Allen Hu said:
Will this work with XS app port?
If so can I use in my rom?
Developing an ICS rom
Click to expand...
Click to collapse
I'm sorry I don't know what is the XS app port are you speaking of.
Generally speaking it will work for you if your custom ROM uses a stock, unmodified, services.jar/[o]dex. Else you'll lose functionality or customizations.
zxp said:
I'm sorry I don't know what is the XS app port are you speaking of.
Generally speaking it will work for you if your custom ROM uses a stock, unmodified, services.jar/[o]dex. Else you'll lose functionality or customizations.
Click to expand...
Click to collapse
I mean the apps from Xperia S resized....
And is it ok if I added the v6 supercharger in services.jar ?
i have .431 patch on .587 already. which package should i use?
happyBOY78 said:
Bad thing is, that this led fix works only with stock sms app. I use other sms client, and with this, led don´t blink.
Click to expand...
Click to collapse
For me it works fine with non-stock sms app (GO SMS pro). Missed calls, etc works too zxp - Thx for the fix!
tested working on my stock 4.1.B.0.587 ST15i
Allen Hu said:
I mean the apps from Xperia S resized....
And is it ok if I added the v6 supercharger in services.jar ?
Click to expand...
Click to collapse
Xperia S apps, should work fine just like any other app with this patch I think.
I never used v6 supercharger, but as far as I can understand from a quick look it dynamically patches a given services.jar rather than simply replacing it (which is what my patch does).
So if you have v6 supercharer patch my patched service.jar/[o]dex you should have it both supercharged and with the working LED.
spyblaster91 said:
i have .431 patch on .587 already. which package should i use?
Click to expand...
Click to collapse
If you applied my .431 patch on .587 you can simply use the same type you already used. Eg: if you used the "universal" one, you can use the "universal" one again, it will override the previous one.
Which one should i apply...im using markphyton rom .587 doomkernel
Sent from my R800i using xda app-developers app
Im using the fix for .431 and works great on my .587, whats new in this one? should i change my mod?
Seems to work fine in my xperia Arc LTi15.
Thanks!
thank you so much man, finally my ARC S notif LED its work like a charm :fingers-crossed: ....
Do you know if this patch works for the Real ICS r6 rom (based on 4.1.B.0.587)?
Which package should I use in case it works?
Thanks a lot in advance!
Deshabilitado said:
Im using the fix for .431 and works great on my .587, whats new in this one? should i change my mod?
Click to expand...
Click to collapse
Yes you should use this new version on a .587 based ROM, because if you use the fixed .431 file you are actually missing some fixes/changes that sony did in input method handling and other misc code, that you will restore by applying the new .587 patch.
evo10 said:
Which one should i apply...im using markphyton rom .587 doomkernel
Click to expand...
Click to collapse
ecejmpe said:
Do you know if this patch works for the Real ICS r6 rom (based on 4.1.B.0.587)?
Which package should I use in case it works?
Click to expand...
Click to collapse
If those roms are deodexed you should use the third package (Ultimate_4.1.B.0.587_Notification_LED_FIX_FOR_DEodexd_roms_by_zxp.zip) else you have to use the first (Ultimate_4.1.B.0.587_Notification_LED_FIX_UNIVERSAL_stock_rom_by_zxp.zip): either way you must be sure that your ROM has a unmodified services.jar(/odex) or you'll loose some customization.
Im using .587. Which one i need to download?
Sent from my WT19i using Tapatalk 2
Is there a way to install it without a root or unlocked bootloader?
Thanks
botski said:
Im using .587. Which one i need to download?
Sent from my WT19i using Tapatalk 2
Click to expand...
Click to collapse
Please read the Downloads and Install Instructions section in the first post, it contains a detailed answer to your question.
I've started a discussion topic about Samsung's new headache SysScope and System Status: Modified
Finally we think we've fixed the problem for now (until samsung comes up with something new)
What Tested/Reported :
"Device Status" in Settings should always remain "Normal"
"System Status" on Bootloader screen should always remain "Official" (Except "Flash Counter" and "Current Binary", they are bootloader related)
FOTA Firmware Update Check is working but we're not sure because there is no update
It's reported that AllShare is working
A CWM package made from N7100 XXDME1 firmware: SysScopeFix_n7100_XXDME1.zip
* the Apk files in the cwm package may not be compatible if you have a different device/firmware. Backup your rom first!
[For Developers]
You can take a look at the modified sources and commits.
All the info you need is on Github: https://github.com/sinancetinkaya/DeviceStatus
This is an open project. If you have anything to contribute, please feel free to join.
Current Collaborators :
dwitherell (Big thanks to him)
[email protected]
I'm gonna try it soon.
After flashing this MOD, I will not be needing TriangleAway?
SandeepEmekar said:
I'm gonna try it soon.
After flashing this MOD, I will not be needing TriangleAway?
Click to expand...
Click to collapse
No, you will need it to reset Flash Counter and Current Binary
System Status (Bootloader) should always remain "Official" (Not the Flash Counter and Current Binary)
Click to expand...
Click to collapse
Thanks go back to [email protected] for getting this idea going and putting it all up on github! Glad I could lend a hand
Now hopefully some folks that know a thing or two will come by and make it even better
This really needs more attention.
Edit: To make sure it will work on all Samsung firmware (for the usual status in settings) and all ROMs (for the download mode status), is it possible to make an Xposed mod? That would be helpful, because it won't need to be adapted to every ROM.
Sent from my GT-N7100 using Tapatalk 4 Beta
hameerabbasi said:
This really needs more attention.
Edit: To make sure it will work on all Samsung firmware (for the usual status in settings) and all ROMs (for the download mode status), is it possible to make an Xposed mod? That would be helpful, because it won't need to be adapted to every ROM.
Sent from my GT-N7100 using Tapatalk 4 Beta
Click to expand...
Click to collapse
for the settings, it should be no problem since i coped with the settings's status by modding it months ago. no idea for the counter or status in the download mode though
ykk_five said:
for the settings, it should be no problem since i coped with the settings's status by modding it months ago. no idea for the counter or status in the download mode though
Click to expand...
Click to collapse
Does the download mode need to be nodded for each ROM version?
Sent from my GT-N7100 using Tapatalk 4 Beta
hameerabbasi said:
Does the download mode need to be nodded for each ROM version?
Sent from my GT-N7100 using Tapatalk 4 Beta
Click to expand...
Click to collapse
i have not examine about the download mode yet
ykk_five said:
i have not examine about the download mode yet
Click to expand...
Click to collapse
As far as I've seen, with TA version 2.37, it does reset the download mode custom status if you're on the stock ROM/kernel/recovery. It doesn't with version 2.99.
Sent from my GT-N7100 using Tapatalk 4 Beta
hameerabbasi said:
As far as I've seen, with TA version 2.37, it does reset the download mode custom status if you're on the stock ROM/kernel/recovery. It doesn't with version 2.99.
Sent from my GT-N7100 using Tapatalk 4 Beta
Click to expand...
Click to collapse
i tried ta twice only and i gave up finally becoz the custom mode status in download mode is not a problem for me anymore, i mean i don care if it shows custom or not as long as i can reset/reflash the phone back to stock version for maintenance, just in case and touch wood.
although i had another idea to change to status in download mode but it is too risky and i don want to wait for 2 weeks again to get my phone's motherboard replaced (i hard bricked my note 1 before)
perhaps the op has brighter ideas to cope with it
ykk_five said:
i tried ta twice only and i gave up finally becoz the custom mode status in download mode is not a problem for me anymore, i mean i don care if it shows custom or not as long as i can reset/reflash the phone back to stock version for maintenance, just in case and touch wood.
although i had another idea to change to status in download mode but it is too risky and i don want to wait for 2 weeks again to get my phone's motherboard replaced (i hard bricked my note 1 before)
perhaps the op has brighter ideas to cope with it
Click to expand...
Click to collapse
I don't like to comment about the things (like this) that I don't know well.
To communicate with bootloader you need a kernel that has j4fs driver.
As long as I know Perseus kernel has that. And may be that's why on perseus kernel TA is able to reset it without a restart.
Somebody with a good linux kowledge can mount bootloader partition with a proper kernel like perseus and can see what ChainFire is changing.
[email protected] said:
I don't like to comment about the things (like this) that I don't know well.
To communicate with bootloader you need a kernel that has j4fs driver.
As long as I know Perseus kernel has that. And may be that's why on perseus kernel TA is able to reset it without a restart.
Somebody with a good linux kowledge can mount bootloader partition with a proper kernel like perseus and can see what ChainFire is changing.
Click to expand...
Click to collapse
i am using self modded perseus and j4fs can be loaded as modules for other kernels
btw, i really dono perseus can reset the counter on the fly. may be i will try it later. thx for ur big hints
IT IS WORKING!
I flashed it on Omega v16 and now i have status NORMAL!
Thank you and I wish you everything best in life man!!!
I have tested before with everything available so far including wiping and Triangle Away - every possible version and nothing worked! This WORKS!
Edit:
I just noticed that even though the download of apps from the Samsung store does not work yet but this does not bother me for now.
DaveBG said:
IT IS WORKING!
I flashed it on Omega v16 and now i have status NORMAL!
Thank you and I wish you everything best in life man!!!
I have tested before with everything available so far including wiping and Triangle Away - every possible version and nothing worked! This WORKS!
Edit:
I just noticed that even though the download of apps from the Samsung store does not work yet but this does not bother me for now.
Click to expand...
Click to collapse
glad to hear that. what did u do and how did u test it?
DaveBG said:
I just noticed that even though the download of apps from the Samsung store does not work yet but this does not bother me for now.
Click to expand...
Click to collapse
Yes, unfortunately Samsung has spent big efforts to mess up with our powerful Note2
They've put the same check routines into several APKs.
Honestly I have no intention/time to check all of them.
That's why we put the sources on github and wrote what we did.
Tell your rom developer about this, he can easily do the same thing to the other APKs that we've missed.
I just want only one thing from people: Please send your additional solutions(commits) to my github.
Two head is always better than one
@DaveBG
I couldn't find anything in SamsungApps.apk
Can you send the not working program's apk you've downloaded from the Samsung App Store?
DaveBG said:
...I just noticed that even though the download of apps from the Samsung store does not work yet but this does not bother me for now.
Click to expand...
Click to collapse
Yes, what [email protected] said - more info/names of apks that aren't working would be awesome
I've installed this mod and I still have modified in device status in settings and the same in download mode plus I have flash count 1 in download mode even though I've reset flash counter in triangle away. BTW triangle away shows me flash counter 0, and system status normal but other options that I mentioned shows me modified. I'm using Adam kernel, Philz recovery and DMC3 firmware.
Wysłane z mojego GT-N7100
za pomocą Tapatalk 4
djlukas1983 said:
I've installed this mod and I still have modified in device status in settings and the same in download mode plus I have flash count 1 in download mode even though I've reset flash counter in triangle away. BTW triangle away shows me flash counter 0, and system status normal but other options that I mentioned shows me modified. I'm using Adam kernel, Philz recovery and DMC3 firmware.
Wysłane z mojego GT-N7100
za pomocą Tapatalk 4
Click to expand...
Click to collapse
Saw that, investigating
Okay guys, for now we're trying to get rid off SysScope completely
For now FOTA firmware update checking is working without SysSope (I guess )
You can see more details on github
That's all for now
I'm currently on PAC ROM, right now. I tried to install an apk file from my sd card, however, the "Install" button doesn't work but the "cancel" button is working. I already checked the "Unknown Sources", but it's still the same. Any advice?
check pac thread, I asked that question
always read a few last pages of topic and OP
Wysyłane z mojego YP-G70 za pomocą Tapatalk 2
Thanks!
KOala888 said:
check pac thread, I asked that question
always read a few last pages of topic and OP
Wysyłane z mojego YP-G70 za pomocą Tapatalk 2
Click to expand...
Click to collapse
OK, sir. got it.
already been there, so the HALO app is causing the issue.
But, my trick was to do a back up and then boot into cwm , do a factory reset, after that, advance restore from int.sd card,just "data", and it's fixed.
thanks for the response, by the way.
I HOPE EVERYONE IS FAMILIAR WITH THE WORD EUPHORIA.
WELL GET READY TO EXPERIENCE THAT FEELING ON YOUR SONY XPERIA U
I PROUDLY PRESENT MY FIRST ROM i.e. Uphoria v1
A NEW AND FRESH LOOK FOR YOUR XPERIA U IS AWAITING YOU
GO AHEAD AND DOWNLOAD SUPPOSEDLY THE MOST DIFFERENT ROM ON XDA FOR YOUR XpU
YOUR COMMENTS AND FEEDBACKS WILL BE HIGHLY APPRECIATED.
DUE TO SOME REASONS I HAD TO BREAK THE ROM INTO 2 PARTS
THE LINK TO THE SOFTWARE FOR JOINING THE FILE IS THIS
SCREENSHOTS IN THE 2ND POST
HERE ARE THE LINKS
Uphoria v1.zip.001
Uphoria v1.zip.002
FLASH THE STOCK FIRMWARE FIRST FOR BEST EXPERIENCE
FLASHING INSTRUCTIONS:
1. WIPE DATA
2. WIPE CACHE AND DALVIK CACHE
3. FLASH ROM
4. REBOOT AND DONE!!
SOME KNOWN BUGS
1. SOME MIGHT GET A MESSAGE "ERROR OCCURED WHILE TETHERING". I NEITHER HAVE WIFI NOR DO I HAVE NET CONNECTION ON MY XpU. SO PLEASE SOMEONE CHECK THIS OUT ON YOUR XpU AND REPORT
2. THE TURQUIOSE THEME IS YELLOW IN COLOR. I WILL MOSTLY FIND A FIX FOR THIS AND POST THE THEME.APK.
3. YOU SAY
PLEASE DROP IN YOUR FEEDBACKS BELOW. SUGGESTIONS FROM DEVELOPERS FOR THE BETTERMENT OF THE ROM ARE WELCOME AND NEEDED.
CREDITS:
JDWALKER- For his build.prop tweaks
GEKTHEBOSS- For his tweaks
SammiSaysHello- For her theme pack
munjeni- For his cwm kernel
ZN6- For his JB Style System UI
A BIG THANKS TO ALL YOU PEOPLE OUT THERE. THIS WOULDN'T HAVE BEEN POSSIBLE WITHOUT YOUR CONTRIBUTIONS. THANK YOU
IF YOU REALLY LIKED MY ROM, THEN PLEASE HIT THE THANKS BUTTON.
TURQUOISE THEME FIX http://forum.xda-developers.com/showthread.php?p=43209186
Screenshots
Here are some screenshots
downloading will try when i go to my free time thanks
japoina92 said:
downloading will try when i go to my free time thanks
Click to expand...
Click to collapse
thanks a ton
do post your feedback
Later will backup my actually rom, split your two files ( 001,002) and eill try.
And post my feedback to you
japoina92 said:
Later will backup my actually rom, split your two files ( 001,002) and eill try.
And post my feedback to you
Click to expand...
Click to collapse
Sure and thanks.
after downloading the file splitter and joiner program, just open the Uphoria v1.zip.001 with it. It will join both the files.
if any problem to download the program from the website, then do tell me. I will upload the .exe file
now backing up my current system, I will flash by flashtool and try your rom. when tested some time I will write some feedback.
catches show a nice rom!
what FW recommend you? .54 or .89??
japoina92 said:
now backing up my current system, I will flash by flashtool and try your rom. when tested some time I will write some feedback.
catches show a nice rom!
what FW recommend you? .54 or .89??
Click to expand...
Click to collapse
the message "error occured while tethering" was there since i flashed the .89 fw by Tim_Italy....its ws still there even after i flashed the stock fw .54...so i dnt knw wether every1 will get the msg or nt...after that i also changed the SI version and flashed it the clean way (through PCC) but it ws still there...even that had a lot of bloatware...m currently running it on .54 without any prob
jst to inform...this rom ws originally built on .89 so has the build.prob of .89 but i have been running this rom since a week or so on .54 without any issues
sorry if u felt this post a little too long , i jst thought that this bit of info might b helpful
$$sweet devil$$ said:
the message "error occured while tethering" was there since i flashed the .89 fw by Tim_Italy....its ws still there even after i flashed the stock fw .54...so i dnt knw wether every1 will get the msg or nt...after that i also changed the SI version and flashed it the clean way (through PCC) but it ws still there...even that had a lot of bloatware...m currently running it on .54 without any prob
jst to inform...this rom ws originally built on .89 so has the build.prob of .89 but i have been running this rom since a week or so on .54 without any issues
sorry if u felt this post a little too long , i jst thought that this bit of info might b helpful
Click to expand...
Click to collapse
hey i have the sollution for fix "tethering" http://forum.xda-developers.com/showthread.php?t=2247807
hoppefully you fix this bug in .89 FW
EDIT: now im on your rom! will try all okey
EDIT2: and this for fix the GPS in .89 if anyone have problems https://play.google.com/store/apps/details?id=org.fastergps use it for you country .
japoina92 said:
hey i have the sollution for fix "tethering" http://forum.xda-developers.com/showthread.php?t=2247807
hoppefully you fix this bug in .89 FW
EDIT: now im on your rom! will try all okey
EDIT2: and this for fix the GPS in .89 if anyone have problems https://play.google.com/store/apps/details?id=org.fastergps use it for you country .
Click to expand...
Click to collapse
thanks alot....i will surely fix the tethering asap
thanks fr trying my ROM...please post feedback
My first mpressions on your rom are than i feel inspired with the framework and the themes,he wallpaper choose in all themes are good and brilliant.
My suggestions for next rom are if you can put aroma installer and put elements how cybershot 5.7.2 is really good ( in my old rom ) and update your build.prop with the last JDWalker 1.9 build.prop seems amazing brilliant results. If you can put a choose in aroma for governors, maybe can add more stability and battery friendly ( deppend on own chroose.
SORRY FOR MY BAD ENGLISH... IM SPANISH USER NOT ENGLISH XD
And THANKS FOR YOUR TIME
japoina92 said:
My first mpressions on your rom are than i feel inspired with the framework and the themes,he wallpaper choose in all themes are good and brilliant.
My suggestions for next rom are if you can put aroma installer and put elements how cybershot 5.7.2 is really good ( in my old rom ) and update your build.prop with the last JDWalker 1.9 build.prop seems amazing brilliant results. If you can put a choose in aroma for governors, maybe can add more stability and battery friendly ( deppend on own chroose.
SORRY FOR MY BAD ENGLISH... IM SPANISH USER NOT ENGLISH XD
And THANKS FOR YOUR TIME
Click to expand...
Click to collapse
thank u so mch for ur valuable feedback
i will surely keep in mind all the points while putting together v2
did u experience bugs of any kind??
about the JDWALKER build.prop, i was already looking forward for it and will definitely put it in v2...thanks
No bro im only experience the bug with the turqoise theme but not a problem at all, all the rest ar0e good for me, if you can delete othe apk's( i considered any apks how bloatware ) but dont worry all can delete the undwanted apks haha.
If you can,can add an option in aroma for debloat completly your rom. ( in my choice i delete thoose apk, all related with other keyboards except voice search and the original keyboard xperia, maps, street, talkback, and other i dont remember, i delete apks from / data partition. Your rom now is light and fuctional for me
Thanks a lot will try for a while
japoina92 said:
No bro im only experience the bug with the turqoise theme but not a problem at all, all the rest ar0e good for me, if you can delete othe apk's( i considered any apks how bloatware ) but dont worry all can delete the undwanted apks haha.
If you can,can add an option in aroma for debloat completly your rom. ( in my choice i delete thoose apk, all related with other keyboards except voice search and the original keyboard xperia, maps, street, talkback, and other i dont remember, i delete apks from / data partition. Your rom now is light and fuctional for me
Thanks a lot will try for a while
Click to expand...
Click to collapse
thanks...and i was about to debloat it but nt every1 would like apps like timescape and all gone, so i thought that i will add an option for it in the v2 of it with aroma...this is just an experimental version to test my ROM...the future version would be much more stable and better
Hehe will try it and report any bug or problem with it. For fix all in next versions
Just a couple of hints:
For GPS issues:
I've managed to get a temp solution bypassing sony ericsson supl server. Goes like this:
Change your gps.conf file, in SUPL_HOST=supl.sonyericsson.com > SUPL_HOST=supl.vodafone.com
and change your cacert.txt file in /etc/suplcert/ by my attachment.
About joining the 2 files, if you use linux, you can join them manually by:
cat FILEONE.001 FILETWO.002 > JOINFILE.ZIP
easy huh?
BTW: just downloaded this ROM, but i'm trying a little more another. In about a week or so I'll post a review here
raf.lozano said:
Just a couple of hints:
For GPS issues:
I've managed to get a temp solution bypassing sony ericsson supl server. Goes like this:
Change your gps.conf file, in SUPL_HOST=supl.sonyericsson.com > SUPL_HOST=supl.vodafone.com
and change your cacert.txt file in /etc/suplcert/ by my attachment.
About joining the 2 files, if you use linux, you can join them manually by:
cat FILEONE.001 FILETWO.002 > JOINFILE.ZIP
easy huh?
BTW: just downloaded this ROM, but i'm trying a little more another. In about a week or so I'll post a review here
Click to expand...
Click to collapse
Firstly, what are the gps issues people are facing, i am not facing any
Secondly, why are you calling this a temporary solution?? Is it jst an alternative?
Sent from my ST25i using xda app-developers app
Turqiouse Theme Fix
1. download the attachment
2. replace it with the BlueTheme.apk in system/vendor/overlay/framework
3. set permissions to RW R R
4. Reboot
"Error occurred during tethering" appears whenever tethering is put on with data off.
So, IMO there's nothing to fix unless you just want the notification to not appear. Tethering works anyway.
Sent from my ST25i using xda app-developers app
dotafan said:
"Error occurred during tethering" appears whenever tethering is put on with data off.
So, IMO there's nothing to fix unless you just want the notification to not appear. Tethering works anyway.
Sent from my ST25i using xda app-developers app
Click to expand...
Click to collapse
Yes, it does work. But the notification might raise doubts in some people's mind. So looking for a fix
Bdw hope u liked my ROM
Sent from my Xperia U using xda app