[FIX][20-NOV] Omega v33.1 and v33.2 (+stockXXELK4) GPS fix - Galaxy S III Themes and Apps

**Symptom**
Loosing GPS fix on I9300 after 20sec-20mins on latest XXELK4 / Omega v33.1+v33.2 ROM mainly in case of 1st lock on more then >10 satellites.
**Possible solution**
Flash in CWM this one for fixing the GPS issue on Omega v33.2 (tested on 33.1 and was working).
**How it's done**
I simply took all related GPS files from previous Omega version where GPS was working fine and replaced them.
**How to install**
Simply via CWM and perform eventually permission fix after (just for case)
**Result**
Before I was loosing all GPS satellites in 20-30sec, now it looks stable, locking up to 15(17max) satellites
**Which solution I tried before and didn't help**
FasterGPS, setting the parameters
Reflashing Omega on Omega (noWipe)
Reseting aGPS data, downloading new one
Installing another modem, now I'm on I9300DDDLJ1
Turning off GPS, Google location, location via Wifi, rebooting phone and re-enabling again.
Wiping cache + Dalvik-cache + Fixing permissions (after this step I had to reflash no-Wipe the ROM)
Flashing another kernels - stock, GalaxiSih, now I'm on Boeffla-Kernel
**Warning**
Be sure you have nandroid backup and/or reflash no-wipe in case of troubles (wasn't however observing any issues by myself so far).
**Where you can use it ?**
Tested so far on Omega v33.1, confirmed working on Omega v33.2 as well including some other XXELK4 stock/custom based ROMs
Not needed for Omega >=v33.3 or patched stock ROM XXELK4
**Just press THANKS if it worked**
Thanks to Omegas Team.

All you need to do to fix is flash a different kernel

Kickasskev said:
All you need to do to fix is flash a different kernel
Click to expand...
Click to collapse
Incorrect. Lots of people running 4.1.2 on various kernels and still facing the same problem. Myself included having tried 3 different kernels.
Sent from my GT-I9300 using xda app-developers app

Kickasskev said:
All you need to do to fix is flash a different kernel
Click to expand...
Click to collapse
Not helping. Already tried. This is nearly annoying like the hello hello bug. Not all got it and every phone needs a different fix.
Edit: Tried the fix before and don't work for me. Can't get no fix after flashing but it could also related that I got a custom kernel installed. You say you on custom kernel too. Did you flashed the video fix?
Throwing out of the window from my flying Ferrari killer S3 driven by a proud omega team member

Chris_84 said:
Edit: Tried the fix before and don't work for me. Can't get no fix after flashing but it could also related that I got a custom kernel installed. You say you on custom kernel too. Did you flashed the video fix?
Click to expand...
Click to collapse
No, just Omega, custom Kernel and then this simple fix. Wait for the 1st fix, also be connected to data/Wifi. Best for testing is GPS test.
*sorry* I just flashed also another modem just prior to that fix, see 1st post...however when I flashed different modem before I was trying to fix GPS issue, it didn't help at all

shaarky said:
No, just Omega, custom Kernel and then this simple fix. Wait for the 1st fix, also be connected to data/Wifi. Best for testing is GPS test.
Click to expand...
Click to collapse
Don't know for sure but think maybe the video fix who install the old libs brake GPS again but I'm not sure. As I wrote in omega thread. After dirty flash it works perfect even with custom kernel and after installing the video fix it brake down again.
Throwing out of the window from my flying Ferrari killer S3 driven by a proud omega team member

It's working so far.
I haven't flashed fix video but installed siyah so sooner or later I'll need the video fix.
I'll let you know how it goes.
Sent from my GT-I9300 using xda app-developers app

shaarky said:
**Symptom**
Loosing GPS fix on I9300 after 20sec-20mins on latest XXELK4 / Omega v33.x ROM mainly in case of 1st lock on more then >10 satellites.
**Possible solution**
Flash in CWM this one for fixing the GPS issue on Omega v33.2 (tested on 33.1 and was working).
**How it's done**
I simply took all related GPS files from previous Omega version where GPS was working fine and replaced them.
**How to install**
Simply via CWM and perform eventually permission fix after (just for case)
**Result**
Before I was loosing all GPS satellites in 20-30sec, now it looks stable, locking up to 15(17max) satellites
**Which solution I tried before and didn't help**
FasterGPS, setting the parameters
Reflashing Omega on Omega (noWipe)
Reseting aGPS data, downloading new one
Installing another modem, now I'm on I9300DDDLJ1
Turning off GPS, Google location, location via Wifi, rebooting phone and re-enabling again.
Wiping cache + Dalvik-cache + Fixing permissions (after this step I had to reflash no-Wipe the ROM)
Flashing another kernels - stock, GalaxiSih, now I'm on Boeffla-Kernel
**Warning**
Be sure you have nandroid backup and/or reflash no-wipe in case of troubles (wasn't however observing any issues by myself so far). Tested so far on Omega v33.1 only, but should work on v33.2 as well including some other XXELK4 stock based ROMs
**Report and let others know if this helps or not and/or press THANKS**
Thanks to Omegas Team.
Click to expand...
Click to collapse
Tried all what you have said you had tried and also no luck - still having GPS problems.
Installed the fix.
Before installation, using Waze, I used to get a fix within 5 seconds, and then I used to lose the signal after 3-5 Mins. max.
After installation - got a fix same within ~5 secs, and I kept it on for about 10 mins and I had no signal loss.
I will try it further on my way home (about 20-30 min drive) and post results.
Thanks alot - hope this might just do it!
***EDIT***
Drove 20-25 mins home - all working fine.
Will do more testing tomorrow, but looks like this is the fix, for me anyhow.
Big thanks!

Work for me.
This fix work for me. Test during 40 min of navigation .I´m on Omega 33.1 with video fix and Kernel Perseus 26.1
Will test again on the end of the day.

is the "use wireless network" is turn on on your rom??
or turn off??

not working for me on omega 33.2 + stock kernel

liad1981 said:
is the "use wireless network" is turn on on your rom??
or turn off??
Click to expand...
Click to collapse
Is ON
Sent from my GT-I9300 using Tapatalk 2

Small report:
Today morning I use GPS (Waze and Be On Road) to navigate to my work (15km).
Lost signal every 3 - 5 minutes. Strange.
In my work I flash your fix.
Navigate (Be On Road) approximately 15km to customer and 15km to work. Working absolutely good.
Thank you.
I will test later much more and report again.
Update1: On the way home from work gps navigation (Be On Road) work like a charm. I am lucky
Update2: Today on way from home to work, working very well. Thank you. Now I vote for YES

Hi my friend. But suddenly your fix work here. Did another full wipe. Installed my usual stuff and got no fix. Then I thought I try again your zip and it works for now. Will test how long but really hope that's it.
Sent from my GT-I9300 using xda premium

i installed 33.2 with no wipe on 33.1 and i had the gps problem.
it found the first fix but after 2-3 minutes the fix isnt possible.
i did a first check with your fix and it seems to work now...tomorrow on my way to office i will give it a try
thx

How did I miss this! Going to flash and test on the way to work tomorrow...looks promising!
Sent from my GT-I9300 using Tapatalk 2

Not sure i tried this one, but just flashed it and will try in about 2 hours and will report back.

For me it's working now.. I'm on Omega 33.2 and latest Siyah
tapatalked via SGS3 on OMEGA and Motomoto00

Oke, just had my 25 minutes drive.
Flashed your zip before went on the road, double checked that Use wireless networks was enabled again, this afternoon i disabled it and gps worked again.
And from work to home, not one single drop off gps noticed using Sygic.
Also watched carefully to Sygics speed meter and it was corresponding with the speed i actually drove, not going from 30 to 100 i saw yesterday before gps broke down.
Looks your file did it for me.

Deleted

Related

[FIX][STOCK][4.0.4][14/07]Working Camera + Video on 4.0.4 with non-stock kernels

Obsolete
This workaround was only relevant some time ago while custom kernels did not yet have updated sources from Samsung to work on 4.0.4 ROMs. This is no longer the case so this info is completely irrelevant now.
There are plenty of people complaining about camera and video playback problems when using custom kernels on the newest 4.0.4 builds such as XXLQ5 or XWLPM .
I tried a few things and managed to find a fix for it.
Installation
Just take the CWM zip file and apply it on your ROM. It will leave a backup of the 2 files that will be replaced.
Removal
The Restore zip can be "installed" to remove the patched files and put back the original ones that were kept on your device.
Tested and working both for Camera preview and Video playback, on XWLPM.
Note: This is a temporary fix until the kernel devs have enough information to properly update their code, and when that happens this fix can be uninstalled.
Heyy Tungstwenty, another great fix by you!
Well done, it works great! Now also videoplayback works fine with siya on 4.0.4!
Now the only thing left not working on 4.0.4 with Siya is the bluetooth...
Thanks again!
he he he go 4.04 gooo!
Thanks man.
Hi @Tungstwenty
Time to go OUT of stock Kernel XWLPM and move to Siyha Kernel, thanks a lot my friend...
Cheers
Thanks again for the fix.
But I found a mayor problem with custom 4.0.3 kernels on 4.0.4 firmware.
This bug is, to my opinion, so big, it's not worth anymore to use a custom 4.0.3kernel on 4.0.4...
I tested this with all Siya kernels 3.3.2 and above.
Try this to reproduce this bug:
1)Put on your wifi
2) Reboot your device with wifi on.
3) Go to: settings-display-brighteness/ Try to change a value, and see if it sticks.
It doesn't. For example: I had it on autobrightness. Can't get it off autobrighteness anymore, with wifi turned on.
But it is not only brighteness settings. Other settings cannot be made also with wifi on. For example put lockscreentext on your lockscreen. You can't; it doesn't show on the lockscreen. And probably many other settings have the same problem..
When I turn off wifi, and reboot, all off a sudden I can make the changes, and they stick.
Then i flashed CFroot 4.0.4 kernel. Now I can make changes with wifi on...
Can anybody try and see if they can reproduce this issue?
Thanks in advance...
EDIT: SOLVED by doing a wipe.
It must have been some old data from the nandroid data backup I restored.
Normally I don't post stuff like this if I'm not completely sure.
But the strange part of this story remains that I did had the above issues with one kernel and not with the other.
So I guessed it was kernel related.
This turned out to be a false conclusion.
Thanks for the tips!
The Undertakerr said:
Thanks again for the fix.
But I found a mayor problem with custom 4.0.3 kernels on 4.0.4 firmware.
This bug is, to my opinion, so big, it's not worth anymore to use a custom 4.0.3kernel on 4.0.4...
I tested this with all Siya kernels 3.3.2 and above.
Try this to reproduce this bug:
1)Put on your wifi
2) Reboot your device with wifi on.
3) Go to: settings-display-brighteness/ Try to change a value, and see if it sticks.
It doesn't. For example: I had it on autobrightness. Can't get it off autobrighteness anymore, with wifi turned on.
But it is not only brighteness settings. Other settings cannot be made also with wifi on. For example put lockscreentext on your lockscreen. You can't; it doesn't show on the lockscreen. And probably many other settings have the same problem..
When I turn off wifi, and reboot, all off a sudden I can make the changes, and they stick.
Then i flashed CFroot 4.0.4 kernel. Now I can make changes with wifi on...
Can anybody try and see if they can reproduce this issue?
Thanks in advance...
Click to expand...
Click to collapse
I actually had that happen to me when i was on Neat Rom. Don't know what caused it but I ended up switching roms.
The Undertakerr said:
Thanks again for the fix.
But I found a mayor problem with custom 4.0.3 kernels on 4.0.4 firmware.
This bug is, to my opinion, so big, it's not worth anymore to use a custom 4.0.3kernel on 4.0.4...
I tested this with all Siya kernels 3.3.2 and above.
Try this to reproduce this bug:
1)Put on your wifi
2) Reboot your device with wifi on.
3) Go to: settings-display-brighteness/ Try to change a value, and see if it sticks.
It doesn't. For example: I had it on autobrightness. Can't get it off autobrighteness anymore, with wifi turned on.
But it is not only brighteness settings. Other settings cannot be made also with wifi on. For example put lockscreentext on your lockscreen. You can't; it doesn't show on the lockscreen. And probably many other settings have the same problem..
When I turn off wifi, and reboot, all off a sudden I can make the changes, and they stick.
Then i flashed CFroot 4.0.4 kernel. Now I can make changes with wifi on...
Can anybody try and see if they can reproduce this issue?
Thanks in advance...
EDIT: SOLVED by doing a wipe.
It must have been some old data from the nandroid data backup I restored.
Normally I don't post stuff like this if I'm not completely sure.
But the strange part of this story remains that I did had the above issues with one kernel and not with the other.
So I guessed it was kernel related.
This turned out to be a false conclusion.
Click to expand...
Click to collapse
Just did the test now and when I was about to post the results I saw your edit
I'm using 3.3.3d XWLPG and installed a minimal deodexed XWLPM as a secondary ROM to work on this fix.
I did the steps you mentioned (for brightness level and for lockscreen owner info) and didn't manage to find any problems, so I'm glad it now works for you as well.
BTW, was it a full wipe or wipe cache/dalvik?
Tungstwenty said:
Just did the test now and when I was about to post the results I saw your edit
I'm using 3.3.3d XWLPG and installed a minimal deodexed XWLPM as a secondary ROM to work on this fix.
I did the steps you mentioned (for brightness level and for lockscreen owner info) and didn't manage to find any problems, so I'm glad it now works for you as well.
BTW, was it a full wipe or wipe cache/dalvik?
Click to expand...
Click to collapse
I'm getting offtopic here, because it has nothing to do with your camera fix
But I'm still investigating the matter now as we speak.
When on Siya, only a full wipe solves the problem I have above.
Because I'm curious(And lazy), I restored my Nandroid Data backup again(XWLPG nandroid with Siya 3.3.2) I only restore data.
Then I have the above problem again.
Now the strange part: Also Dorimanxx Kernel solves my problem.
So this thing I have, seems to be contained to SIYA kernel.
When I flash back to Siya, I have the problem again.(All new Siya versions tested)
Flashing then to any other Kernel, problem solved again.
But Siya can't be the problem also, because when I fully wipe also Siya will work.
I'm going further back to an older Siya to try if it makes any difference, but I think this will become one of the "android secrets" I will never find the cause of...
Sorry for the offtopic.
The Undertakerr said:
I'm getting offtopic here, because it has nothing to do with your camera fix
But I'm still investigating the matter now as we speak.
When on Siya, only a full wipe solves the problem I have above.
Because I'm curious(And lazy), I restored my Nandroid Data backup again(XWLPG nandroid with Siya 3.3.2) I only restore data.
Then I have the above problem again.
Now the strange part: Also Dorimanxx Kernel solves my problem.
So this thing I have, seems to be contained to SIYA kernel.
When I flash back to Siya, I have the problem again.(All new Siya versions tested)
Flashing then to any other Kernel, problem solved again.
But Siya can't be the problem also, because when I fully wipe also Siya will work.
I'm going further back to an older Siya to try if it makes any difference, but I think this will become one of the "android secrets" I will never find the cause of...
Sorry for the offtopic.
Click to expand...
Click to collapse
I don't think it's offtopic
This is indeed very strange, but here's a possible explanation:
The custom kernels (Siyah, Dorimanxx, ...) each have their own tweaks; they're not exactly the same. While they might share lots of common changes and improvements, they do have different things hence the word "custom".
There's a possibility that the sequence of events to make the camera work is contained not only on the binaries (the ones in the zip file I posted), but also on some cached data that was already picked up when you first ran the camera app, which invoked a service, which in turn invoked a library, etc. Later, when reopening the camera, now with the "fixed" binaries, there might still be bad data that a particular kernel is not expecting. Even if you came from Siyah when initially running the camera app, the original libraries might have cached strange data that the kernel will no longer recognize even after the binaries are now in line with the kernel. And another kernel might have code that is lenient enough to still work with it.
I have been fiddling with the bluetooth part to try to make it work, and this was exactly one of my steps. Whenever attempting code changes, I wiped all the data to make sure the device is starting fresh and if it doesn't work, it isn't due to bad starting data but only the code.
Unfortunately, none of the several things I tried worked and I don't think it's very likely I'll find a solution for bluetooth.
Tungstwenty said:
I have been fiddling with the bluetooth part to try to make it work, and this was exactly one of my steps. Whenever attempting code changes, I wiped all the data to make sure the device is starting fresh and if it doesn't work, it isn't due to bad starting data but only the code.
Unfortunately, none of the several things I tried worked and I don't think it's very likely I'll find a solution for bluetooth.
Click to expand...
Click to collapse
thanks a lot for the camera fix now I can use official 4.0.4 more often with my favourite kernel - Siyah
Tungstwenty said:
There are plenty of people complaining about camera and video playback problems when using custom kernels on the newest 4.0.4 builds such as XXLQ5 or XWLPM .
I tried a few things and managed to find a fix
Click to expand...
Click to collapse
Hay man tnx. Im trying to fix my LQ5 with siyah 3.3.3d kernel.
Sent from my GT-I9100 using xda app-developers app
cdaarif said:
Hay man tnx. Im trying to fix my LQ5 with siyah 3.3.3d kernel.
Click to expand...
Click to collapse
I have worked on this fix using XWLPM as a secondary ROM (I'm still on XWLPG) but this should work both for LPM and LQ5.
cdaarif said:
Hay man tnx. Im trying to fix my LQ5 with siyah 3.3.3d kernel.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Man Bluetooth don't work my LQ5 with siyah 3.3.3d kernel. Plz work n fix this.
Sent from my GT-I9100 using xda app-developers app
Tungstwenty said:
I have been fiddling with the bluetooth part to try to make it work, and this was exactly one of my steps. Whenever attempting code changes, I wiped all the data to make sure the device is starting fresh and if it doesn't work, it isn't due to bad starting data but only the code.
Unfortunately, none of the several things I tried worked and I don't think it's very likely I'll find a solution for bluetooth.
Click to expand...
Click to collapse
cdaarif said:
Man Bluetooth don't work my LQ5 with siyah 3.3.3d kernel. Plz work n fix this.
Click to expand...
Click to collapse
This is just a fix for Camera + Video. I know bluetooth is also not working but as I posted before, I tried to fix it as well but don't think it's doable without changing the kernels. Kernel devs will have to find a way to fix it.
Working bluetooth on LPM with stock Kernel and camera with your hack.
marbutina said:
Working bluetooth on LPM with stock Kernel and camera with your hack.
Click to expand...
Click to collapse
If you're using stock kernel you can (should) uninstall my camera/video hack. It's only needed for custom kernels.
Thanks.
In the Galaxy Note forums it appears that hardcore has fixed the bluetooth in 4.0.4 sammy roms
It seems to be a kernel issue like Tungstwenty said earlier
hardcore said:
Well whaddaya know...
K3-9:
- Bluetooth now works for 4.0.4 ROMS
Click to expand...
Click to collapse
maybe his fix will work for S2 4.0.4 roms too
link to his site/news article
link to the newest hardcore note kernel source code
Krendelrus said:
In the Galaxy Note forums it appears that hardcore has fixed the bluetooth in 4.0.4 sammy roms
It seems to be a kernel issue like Tungstwenty said earlier
maybe his fix will work for S2 4.0.4 roms too
link to his site/news article
link to the newest hardcore note kernel source code
Click to expand...
Click to collapse
Thanks for the above info!
Best to repeat this message in the Siya thread, and/or send Gokhanmoral this info by PM. He might be able to use Hardcore's sources to fix bluetooth in Siya kernel...
Edit: I see you allready did that. Thanks again! Maybe soon we can have working bluetooth with a custom kernel, that would be great!

my autorotation stopped working :((

I tried flashing diff roms with full wipe. No luck
Is this hardware fault u think? Where is the sendor located?
Download this app, called Sensor View:
https://play.google.com/store/apps/details?id=com.bytemystery.sensorview&hl=ro
and switch to accelerometer, orientation, and gyro, and see if it shows anything when you move the device. If it doesn't, it probably is a hardware problem.
Had this once
Hi,
I also had this once with Android Revolution HD (4 or earlier..) Programs like the suggested showed absolutely no reaction from the gyroscope so I really thought I ruined something.
Wiped everything and flashed a stock rom, that helped at last.
It might however actually be the gyroscop defect...
sandulea said:
Download this app, called Sensor View:
https://play.google.com/store/apps/details?id=com.bytemystery.sensorview&hl=ro
and switch to accelerometer, orientation, and gyro, and see if it shows anything when you move the device. If it doesn't, it probably is a hardware problem.
Click to expand...
Click to collapse
I tried the app. The values didnt change.
My gyroscope isnt working either btw tried few games and can steer to left and right.
Im gonna do a stock flash and if it still dont work, deliver it in for warranty fix.
I'll let u know if its a software issue.
I am running stock rom and I don't know if the Note 2 is supposed to work upside down (I use it like that all the time when I am charging it in portrait mode) but it doesn't so I installed Ultimate Rotation Control (a hold over from the stock nexus 7 rom days when it wouldn't autorotate). It should work in your situation, try it and let us know.
Same thing happened to me but i found out it was kernel related, im on omega rom and im now using neak, all ok now.
Sent from my GT-N7100 using XDA Premium HD app
I flashed omega 7 and it worked. but then i flashed redpill kernel and it didnt work again
good thing it aint the hardware fault!
toofank said:
I flashed omega 7 and it worked. but then i flashed redpill kernel and it didnt work again
good thing it aint the hardware fault!
Click to expand...
Click to collapse
that's good
Ok here's the dilema..
perseus and redpill give the autorotation/gyroscope problem. while Neak, Notecore and other kernels that dont have fatex support dont give that issue!
The sad part is that I MUST have fatex support so i can swap my ext sd with int sd.
any other kernels besid eredpil & persues that lets me do that??
also .. the main q is... why did this suddenly start happening? I used those kernels before without any gryo/rotation issues.
ok... flashed a few times and now its working as it did before.
running wanam rom + perseus and ext/int sd swap!
toofank said:
I tried flashing diff roms with full wipe. No luck
Is this hardware fault u think? Where is the sendor located?
Click to expand...
Click to collapse
Had the same issue...i was swapping between cm 10.1 and jb leak and suddenly autorotation was all over the place(not coming back to portrait) even after reflashing clean instal(cm10.1 or jb leak)...for me the fix was kind off lucky...disabled(unselect) calibration in cm10.1 under system settings/system/calibration and it all came back to normal...
may come handy for others too

Re: JellyBean - JELLYTIME for DHD/Inspire4g - 4.2 R2 Available

Re: JellyBean - JELLYTIME for DHD/Inspire4g - 4.2 R2 Available
ROM is good but very laggy compared to r32 and Google now speech does not work or crashes I have been using r2 for nearly a weak now. Did anybody try with kangbang 2.5 kernel ? Is it still laggy
Sent from my Desire HD using xda app-developers app
R3 is out nw
R4 as well
maxxjaxx said:
R3 is out nw
Click to expand...
Click to collapse
R4 is out as well. While i am interested in putting it on my DHD, I am a noob. Any pointers on how to do this step by step (the guides are bit confusing on terminology)?
Thanks.
Growing sntfri
Great ROM! i use it now
mobilizedport said:
R4 is out as well. While i am interested in putting it on my DHD, I am a noob. Any pointers on how to do this step by step (the guides are bit confusing on terminology)?
Thanks.
Click to expand...
Click to collapse
Are you rooted already?
R: Re: JellyBean - JELLYTIME for DHD/Inspire4g - 4.2 R2 Available
chrmica said:
ROM is good but very laggy compared to r32 and Google now speech does not work or crashes I have been using r2 for nearly a weak now. Did anybody try with kangbang 2.5 kernel ? Is it still laggy
Sent from my Desire HD using xda app-developers app
Click to expand...
Click to collapse
I'm with R4. With [email protected], interactive gov and SIO is really fast and smooth without lags. This ROM works great!
Sent from HTC UzDesireHD
R4 runs on my Desire HD without any problem except GPS does not work. Already tried several things to fix it (reinstall ROM, full wipe, antenna exchange) unfortunately without any success. I hope this is just an issue with the ROM and not with my hardware...
hefepauli said:
R4 runs on my Desire HD without any problem except GPS does not work. Already tried several things to fix it (reinstall ROM, full wipe, antenna exchange) unfortunately without any success. I hope this is just an issue with the ROM and not with my hardware...
Click to expand...
Click to collapse
GPS works for me on GoogleMaps, Navigon and Open GPS Tracker, but not for MyTracks. Maybe it's just the app you are using?
Skilljoy said:
GPS works for me on GoogleMaps, Navigon and Open GPS Tracker, but not for MyTracks. Maybe it's just the app you are using?
Click to expand...
Click to collapse
I've tried several apps incl. Google Maps, GPS Tracker, GPS Test, GPS Status,... all without any success. No reception at all.
When GPS is active, shouldn't there be an icon displayed in the top bar?
GPS Signals ... finally
I finally fixed my GPS issues!
The following description worked for me:
1. Download a stock ROM (DHD_WWE_3.12.405.1_STOCK_rooted_by_nitr00.zip)
2. Put the ROM in root folder of SD-card
3. Full Wipe (using 4EXT-Recovery)
4. Flash stock ROM via Recovery
5. If your bootloader is HTCdev unlocked don't forget to flash the stock ROM boot.img via fastboot
6. Reboot
7. Check with GPS Test (or similar) if you receive some satellites and if you get a fix
8. Reboot again to recovery
9. Flash JellyTime ROM
10. Flash G-APPS
11. once again-> don't forget to flash the JellyTime ROM boot.img via fastboot if your bootloader is HTCdev unlocked
12. Reboot
I get a GPS fix now in about 6 to 10 seconds. I am so glad!

[Q][ROM][AOSPA:Android 4.4.2] Paranoidandroid 4.0 BETA 3

Currently on this rom and gps is not working for me,.......Is it a bug? are there any specific gaps to use with this rom,..... maybe i need to change some permissions in the app security section? @deedwar
logcat file https://drive.google.com/file/d/0B1dyEUF7ImLrSlFQcHdhM1E1VWM/edit?usp=sharing
matej18 said:
Currently on this rom and gps is not working for me,.......Is it a bug? are there any specific gaps to use with this rom,..... maybe i need to change some permissions in the app security section? @deedwar
logcat file https://drive.google.com/file/d/0B1dyEUF7ImLrSlFQcHdhM1E1VWM/edit?usp=sharing
Click to expand...
Click to collapse
No problem i will take a look at it and see what i can do. Very busy at work over the next 2 days but i will see what i can do.
@deedwar This is probably known, but anyway, i decided to make a logcat; Installed today the new version, beta 4, ....and at first i noticed that the lightbulb does not work, gps problem goes on, and the camera app in this version will not even start,........, done a fresh install, wiped everthing,........, then went back to my recovery, started up version 3 and suddenly the camera in version 3 shows the same problems,.....this kernel of ours, hmmmm, just cant wait to see how the camera thing is going to fixed,..................... i like your work....
logcat: https://drive.google.com/file/d/0B1dyEUF7ImLrMkV1MlVZbHg0YTQ/edit?usp=sharing
after installation of some non stock camera app, the functionality of my camera is back on stock application and is working(version 4 rom)........,kinda strange and i hope this will last
matej18 said:
after installation of some non stock camera app, the functionality of my camera is back on stock application and is working(version 4 rom)........,kinda strange and i hope this will last
Click to expand...
Click to collapse
Camera and video sometimes takes a couple of reboots before it is working. Not sure why this is the case but it does solve the issue for me.
Thanks for the great work on XS, deedwar, could you elaborate more on the GPS issue? Have you experienced it?
Today I installed BETA4, and I am very satisfied with battery life and smoothness.

[ROM] [24/12/15] [Unofficial] CM 10 for HTC Desire 300 [Public Beta]

Unofficial CM 10 for HTC Desire 300 (g3u)
device_htc_g3u v0.8b (24/12/15)
Traded stagefright bug for a new kernel
(no more stagefright and a freshly compiled kernel)
device_htc_g3u v0.77b3 (04/10/14)
Battery comsumption (hot)fix
(rls should no longer drain your device)
device_htc_g3u v0.77b2 (01/10/14)
Wifi is working
(wifi0 is forced into compliance)
device_htc_g3u v0.77b (25/9/14)
jellybean
(nom nom nom)
Full Disclosure
This is my first android project, so go easy on me.
Project Status
It's usable as a phone
So any willing beta testers are welcome to join the 'fun' and report further bugs.
Project !Status
mobiledata works but will drain your battery
(if you need to use it, reboot after switching it off)
libaudio is not fully functional
(stock has no mic unless in a call and custom has no speaker)
USB only works in mtp mode
(mass_storage mode appears to be incompatible with rmt_storage)
FM Radio not available
(required apps are currently not compiling)
Camera (front) appears unstable
(didn't bother to check what might be the cause)
TODO
[high priority]
fix libaudio (recording in stock or speaker in custom)
[medium priority]
fix libril -> mobile data drains the battery
[low priority]
enable apps2sd -> 2GB internal should suffice for the time being
check if cm supports proximity & light sensors -> they do work fine
fix mass_storage -> mtp is working
fix video recording -> it's a phone not a camcorder
fix video playback -> at least they are running
fix camera -> it's a phone dammit
find a better fix for wifi -> it works for now
fix graphical glitches
Disclaimer
Use at you own risk. This is a public beta and not meant for daily use. Please keep that in mind.
I can not be held accountable for any damage you might cause to your device if you decide to flash this file.
Requirements
HTC Desire 300 with unlocked Bootloader and custom recovery
(S-ON or S-OFF does not matter)
Download
Click me if you want the initial wifi free version (9d0a8fcca957d09dbaf306a1986d14dd)
Click me if you want to drain your battery (688c2779b4864ed9b568260477708049)
Click me if you like the stock kernel (1ba8a225bc7772f34f1e56bff51bfe27)
Click me if you dare (78bbcf5bf0eb26520efff6d49adac106)
Warning!!! If you are not a certified beta tester the zip file might explode upon extraction!!! You have been warned!
Installation
Enter recovery and begin by backing up your current system.
Next choose Wipe Data / Factory Reset from the main menu and Wipe Dalvic from the advanced submenu.
Last but not least use the mount submenu to format system.
Now use sideload or zip install to start beta testing this tasty jellybean.
Special Thanks
go out to anyone who has ever contributed something to a msm8225, ath6kl or htc related android project
device_htc_g3u
kernel_htc_g3u
Branch: Android 4.1.2
Version: 3.4.0-g12f638f
Config: g3u_defconfig
Toolchain: arm-eabi-4.6
Click to expand...
Click to collapse
compiled by 4m8
(My mind is a swirling miasma of scintillating thoughts and turgid ideas.)​
What are the requirements ? I guess I should use the only recovery available for the device ? and also, since we don't have s-off working for this device I think we have to flash the boot.img right ?
I'd recommend using the recovery from this build for the job. It won't crash unlike the philz version.
And no, you don't need to flash boot seperately. The only requirement is an unlocked bootloader.
S-ON only protects hboot and radio from flashing so you can safely install this release from the recovery.
Don't forget to backup your current system.
I'm downloading the files now, will test and report ASAP
Can i promote this in 2 german Forums? ist German translation available?
when do you think you will fix wifi?
HUGE THANKS IN FORWARD FOR COMPILING CM!
After the experiment:
the Rom stable and fast, but Wi-Fi does not work and do not contain FM radio
Front camera not working
I wish you success in your work and I hope you update the version of Android to be higher than 4.1.2
Thank you very much ..
4m8 said:
I'd recommend using the recovery from this build for the job. It won't crash unlike the philz version.
And no, you don't need to flash boot seperately. The only requirement is an unlocked bootloader.
S-ON only protects hboot and radio from flashing so you can safely install this release from the recovery.
Don't forget to backup your current system.
Click to expand...
Click to collapse
In which way will PhilZ CWM crash? will it still install the rom or not? will it brick my phone?
bassam_tayyan said:
After the experiment:
the Rom stable and fast, but Wi-Fi does not work and do not contain FM radio
Front camera not working
I wish you success in your work and I hope you update the version of Android to be higher than 4.1.2
Thank you very much ..
Click to expand...
Click to collapse
Ah yes FM. It's included in the custom libaudio that can't connect to the speaker.
Which I currently simply replace with the stock lib to make it work as a phone so it can be used to test battery consuption etc.
Sadly the cm apps used for fm won't compile for me. So even if I get libaudio working FM would still be untestable without non cm apps.
I'll add it to the todo once the libaudio trouble is resolved.
The wifi is an annoying issue. I manged to get it to load the drivers so the p2p0 socket gets created.
But it tries to restart it as STA which if my google fu is correct it shouldn't do, since this firmware does not need restarting.
The front camera is a curious bug. It works absoluetly fine for me until I point it towards my face.
So it's either a problem with the proximity sensor or the nasty htc camera tries some facial recognition crap and dies.
If I ever decide to logcat the camera I can tell you more.
Now for a higher version, don't get your hopes up. At least not from my side.
First I'll try my best to fix this up. Then I'll wait for htc to release the kernel so I can get a closer look at the configuration
for this device and maybe adjust it to make this rom even better. Then again the last kernel I compiled was 10 years ago for a gentoo install.
LukeHorizon said:
In which way will PhilZ CWM crash? will it still install the rom or not? will it brick my phone?
Click to expand...
Click to collapse
If you are quick it will install fine. So if you prefer to live dangereously, don't let me stop you
I don't know if it is only an error that is presented on my device. Or maybe it was updated since then.
But for me philz recovery by SPSPawn does boot into a dead state. If you reboot it will crash until a panic reset is triggered.
Actually it is allready crashed while you are in recovery. Therefore you are on a timer until the device resets or you decide to
take out the battery.
I had the same problem on my build and it was caused by cwm always ignoring the ueventd.rc I had prepared because I didn't know
I had to copy it to root and not to recovery.
I've never bothered to figure out which missing element of this script was responsible because I had to substitute it in any case.
But honestly, tell me. Why do you prefer philz? I'm allready (so far unsuccessfully) trying to port twrp. If you have a few good arguments
I might be willing to try compiling a fixed version of philz aswell.
Well i didnt want to use a pc right now ... A TWRP port would be amazing
Is mobile data working?
Can you make your recovery flashable via cwm?
LukeHorizon said:
Well i didnt want to use a pc right now ... A TWRP port would be amazing
Is mobile data working?
Can you make your recovery flashable via cwm?
Click to expand...
Click to collapse
It always tried to download the google language pack for my region until I aborted it. So, yes mobile data should be available.
You mean put the recovery into an update zip thingy, right. Well I could, but you will have used a pc before I'll find the time to upload it.
I'll keep it in consideration for the next update.
Well, atleast internet
When do you think you'll fix wifi?
Regarding to wifi, it will be fixed once it's fixed. Or if you prefer the usual response: When it's done.
This will happen either after or before libaudio is fixed. And that's about as specific as I can get.
Well, it was worth a try still thanks for your effort!
Okay, here goes.
First I tried installing the ROM with the PhilZ recovery because I already had it on my phone, didn't work. Gave me some kind of error (not sure about the error code anymore). Flashed your recovery, worked flawlessly. Now for the ROM.
It's pretty stable, I've had only one strange crash and that was in the first 2 minutes of using it so I don't even know if it counts. The additional CM settings panel works fine, quick toggles are ok, I haven't tried overclocking yet - I'll leave that to someone else. But I have found some bugs:
-proximity sensor not working (screen doesn't go black when you place it up to your ear)
-ambient light sensor not working (auto brightness doesn't work)
-video recording doesn't work
-the camera app glitched up the first time I tried to zoom (was fine afterwards)
-sometimes when going from portrait to landscape I got 1 second of weird graphical glitches
-signal indicator seems to be stuck at 2 out of 4 bars and doesn't move
Overall very nice, keep up the good work!
luxb said:
Okay, here goes.
First I tried installing the ROM with the PhilZ recovery because I already had it on my phone, didn't work. Gave me some kind of error (not sure about the error code anymore). Flashed your recovery, worked flawlessly. Now for the ROM.
It's pretty stable, I've had only one strange crash and that was in the first 2 minutes of using it so I don't even know if it counts. The additional CM settings panel works fine, quick toggles are ok, I haven't tried overclocking yet - I'll leave that to someone else. But I have found some bugs:
-proximity sensor not working (screen doesn't go black when you place it up to your ear)
-ambient light sensor not working (auto brightness doesn't work)
-video recording doesn't work
-the camera app glitched up the first time I tried to zoom (was fine afterwards)
-sometimes when going from portrait to landscape I got 1 second of weird graphical glitches
Overall very nice, keep up the good work!
Click to expand...
Click to collapse
I guess wifi isnt working for you right?
It's not working, but I didn't put it on the list since he already knows it's bugged.
Well, i'll try today
Lets see what happens
Anyway, forgot to unpack the file ... GApps come with it?
SOOO, booting went fine, working like a charm... quicksettings page not available, quicksettings bar is working properly
Mobile Data works flawless, and i guess the rest is just fine
German language worked instantly
it feels way faster then Sense, a HUGE Thanks for you, makes me actually like that phone again ...
I'd like to promote it in German forums if i WiFi is fixed in near future
regards!
LukeHorizon said:
[...]
GApps come with it?
[...]
German language worked instantly
it feels way faster then Sense, a HUGE Thanks for you, makes me actually like that phone again ...
[...]
Click to expand...
Click to collapse
No, you have to get gapps on your own. Since there are multiple options you can choose for yourself. But if you did not format system,
as I've mentioned in the install instructions, chances are high that google apps did get picked up by the install script.
I am not sure if it can take them from the stock rom but it can and will take them from a cm rom and keep them on reinstall.
(I am really not very pleased by this behavior!)
I also should have mentioned that the primary language is decided by the simcard. (Which is annoying since I prefer english in any case)
Randnotiz:
Es freut mich das ich Dir den Spass am Gerät zurückgeben konnte.
Natürlich darfst Du es in deutschen Foren weiterverbreiten sobald die gröbsten Fehler behoben sind.
Einzige Vorraussetzung ist, daß Du es nicht als Deine Arbeit ausgibst.
luxb said:
[...]
-proximity sensor not working (screen doesn't go black when you place it up to your ear)
-ambient light sensor not working (auto brightness doesn't work)
-video recording doesn't work
-the camera app glitched up the first time I tried to zoom (was fine afterwards)
-sometimes when going from portrait to landscape I got 1 second of weird graphical glitches
-signal indicator seems to be stuck at 2 out of 4 bars and doesn't move
[...]
Click to expand...
Click to collapse
Wow. That's much more broken than I expected it to be. Kudos.
Regarding the sensors. I currently am using the stock lib. And logcat let's me assume that they are working as they should.
(i.e they don't crash or drift into madness afaik)
Maybe the stock lib doesn't play well with cm, or you are expecting features from cm that are not implemented.
I will definetly try to compile a working sensor lib in the future, so I guess we'll see....
Camera is also just the stock lib for now. So it's no surprise that somethings might be acting up.
I need a lot of research into that subject before I can specify the requirements for the camera in my boardconfig.
The graphical glitches are rather minor and can be ignored for now. I am aware they exist.
But for now I'd rather focus on the more prominent broken features.
Like wireless for those of us that can't or won't use mobile data. (I belong to the 2nd group)
I noticed the signal indicator aswell. but that should be a problem of the radio compatibility.
We can't flash radio and I'm using the stock libril as the radio interface which should give maximum compatibility in theory.
Of course it doesn't irl... typical -_- (I hate you, Murphy!)
Sidenote:
Why did you remove your avatar? I really wanted to make some "stop trying to kill spoderman" remark...
@all:
Does anyone have any clue how to use the mock locations for gps? They are enabled, but so far I couldn't find any way to set them to a specific location.

Categories

Resources