Related
Hi all, thanks for taking the time to read.
I have a LG G2X, love the feel, the display, the specs and the price. Hate the phone....in every other way
I am on my 4th G2X now b/c I keep taking it back to T-Mobile to get a new one based on the following things my phone does:
1. It restarts 1-2x a week, randomly with or without a power adapter plugged
2. It freezes up every other day or so and requires a hard restart (battery pull) to resume use
3. It frequently takes 5+ minutes to get a GPS lock (tried in several cities coast to coast US)
Now if it were just the first phone I could say lemon, but every G2X I have owned does this, T-Mobile told me it was a known issue with the phone but couldn't tell me if it was software or hardware in nature.
So my question to you fellow forumites is this: Is the issue hardware related (move on to another phone) or software (Rom install fixes all my worries and I'm happy forever and ever and ever)?
If you're still using the stock ROM, and are still on 2.3.3, then you are experiencing SW suckage... Get a custom CM7 Rom on there and enjoy some of the finer benefits. Stability will be better but you won't be dead-set stable. GPS has been an issue for some since the inception of the phone. Others have GREAT GPS reception.
Research the Development forums and find a CM7.2 ROM that best suits you. You can of course go CM9 (ICS) but you won't get HW Acceleration and some things just flat out don't work yet.
New2my8125 said:
If you're still using the stock ROM, and are still on 2.3.3, then you are experiencing SW suckage... Get a custom CM7 Rom on there
Click to expand...
Click to collapse
The stability and GPS performance are greatly enhanced by the stock 2.3.4 ROM, also, if you're not a CM7 fan.
mog44net said:
Hi all, thanks for taking the time to read.
I have a LG G2X, love the feel, the display, the specs and the price. Hate the phone....in every other way
I am on my 4th G2X now b/c I keep taking it back to T-Mobile to get a new one based on the following things my phone does:
1. It restarts 1-2x a week, randomly with or without a power adapter plugged
2. It freezes up every other day or so and requires a hard restart (battery pull) to resume use
3. It frequently takes 5+ minutes to get a GPS lock (tried in several cities coast to coast US)
Now if it were just the first phone I could say lemon, but every G2X I have owned does this, T-Mobile told me it was a known issue with the phone but couldn't tell me if it was software or hardware in nature.
So my question to you fellow forumites is this: Is the issue hardware related (move on to another phone) or software (Rom install fixes all my worries and I'm happy forever and ever and ever)?
Click to expand...
Click to collapse
Software...........I am running Hellfire Phoenix ROM and flashed a GPS fix, and new baseband, now I get GPS locks within <>10 seconds, my phone never freezes, or reboots.
wmm said:
The stability and GPS performance are greatly enhanced by the stock 2.3.4 ROM, also, if you're not a CM7 fan.
Click to expand...
Click to collapse
+1
Sent from my LG-P999 using xda premium
wmm said:
The stability and GPS performance are greatly enhanced by the stock 2.3.4 ROM, also, if you're not a CM7 fan.
Click to expand...
Click to collapse
Thanks for the great responses guys, just another reason I love this forum.
I should have given a few more details, I am running stock 2.3.3 on T-Mobile in the US.
Few questions for a techie (but virgin ROMer):
1. Is the 2.3.4 stock available OTA? I haven't seen any available upgrades.
2. What does baseband refer to? (trying to educate myself on the terms)
3. Any favorite ROMs? My must haves are stability and speed, other than that any goodies/awesomeness is welcome but the first two are absolute.
I am tempted to stick to stock ROMs as I haven't flashed one myself yet and this phone is my lifeblood b/c of work.
On a scale of 1-10 where 1 is "I did it with on accident when I dropped it down the stairs" and 10 is "the most difficult thing you will ever do in your life" what is the difficulty for a ROM virgin to sucessfully flash to 2.3.4 (if it is not available OTA) or CM7/other ROMs,etc?
I am technical, 12 year IT professional with MCSA/CCNA, etc but haven't done much research into the ROM biz. If its not too difficult is there a "Must read" guide for noobs?
mog44net said:
Thanks for the great responses guys, just another reason I love this forum.
I should have given a few more details, I am running stock 2.3.3 on T-Mobile in the US.
Few questions for a techie (but virgin ROMer):
1. Is the 2.3.4 stock available OTA? I haven't seen any available upgrades.
2. What does baseband refer to? (trying to educate myself on the terms)
3. Any favorite ROMs? My must haves are stability and speed, other than that any goodies/awesomeness is welcome but the first two are absolute.
I am tempted to stick to stock ROMs as I haven't flashed one myself yet and this phone is my lifeblood b/c of work.
On a scale of 1-10 where 1 is "I did it with on accident when I dropped it down the stairs" and 10 is "the most difficult thing you will ever do in your life" what is the difficulty for a ROM virgin to sucessfully flash to 2.3.4 (if it is not available OTA) or CM7/other ROMs,etc?
I am technical, 12 year IT professional with MCSA/CCNA, etc but haven't done much research into the ROM biz. If its not too difficult is there a "Must read" guide for noobs?
Click to expand...
Click to collapse
Difficulty is pretty low. If you can follow instructions, and understand what you're doing, then you should be good to go. If you want 2.3.4, you're gonna need to use LG's ****ty software. Either you use KDZ flasher, or LG's official PC suite. Both crashed on me constantly on Win7 x64. I was lucky/unlucky, it crashed right after writing the baseband (low level radio firmware). It hadn't even partitioned anything yet if I tried to turn it on, not even a backlight was showing. So I had to use NVflash to completely repartition it to stock. After that, I flashed CWM (clockworkmod), the custom recovery. Nowadays, TWRP is available. TWRP is awesome, and they have awesome Devs. TWRP (teamwin recovery project) is touch based rather than CWM and traditional volume key and power button navigation. There is CWM touch, but it's extremely experimental and I find it too glitchy compared to TWRP. TWRP is a work in progress however and there may be issues (I had one but it was easily fixed with one command when I spoke with the Devs on irc) I haven't had any serious ones though. IMO it's easier to NVflash in a Linux environment, because there is no messing around with drivers. But after drivers are installed on windows, the difficulty level plateaus.
As for my favorite ROM, that would currently temasek cm7 builds. They're stable, fast and they're customizable as f***.
I don't have any links right now, because I'm on my phone, (I can grab them later/soonish) you're going to want tga_gunman's thread named something along the lines of "One click recovery flasher" that's for CWM recovery. If you want TWRP, there's a thread that has TWRP in the title.
Also look for "ROM for recovery under NVflash" or something similar to that. That will take you back to complete stock 2.3.3 no matter what happened software wise, unless you somehow managed to break the baseband. The baseband is the only thing that cannot be fixed by NVflash, only can be fixed by LG's ****ty PC software.
For temasek's cm7 builds, the thread is not created by temasek, but the builds are by him. It should be at build 133 or 134.
If you need anything else, PM me maybe.
Good deal, I'm planning on following this thread from the general section (http://forum.xda-developers.com/showthread.php?t=1594650).
I'm leaving out of state but will work on it over the weekend.
Thanks for all your help and support everybody, any additional comments are welcome before I start flashing this weekend.
Q - Do I need to get the owain's baseband flash fix or not with the ROM you sugested, the comments on the thread are confusing me a bit. If so where can I download the correct one, can't seem to find it in the Dev threads.
mog44net said:
Good deal, I'm planning on following this thread from the general section (http://forum.xda-developers.com/showthread.php?t=1594650).
I'm leaving out of state but will work on it over the weekend.
Thanks for all your help and support everybody, any additional comments are welcome before I start flashing this weekend.
Q - Do I need to get the owain's baseband flash fix or not with the ROM you sugested, the comments on the thread are confusing me a bit. If so where can I download the correct one, can't seem to find it in the Dev threads.
Click to expand...
Click to collapse
You only need that baseband fix if you have the latest baseband (March 2012) from v21y. It should be available in owain's hopto.
tahahawa said:
You only need that baseband fix if you have the latest baseband (March 2012) from v21y. It should be available in owain's hopto.
Click to expand...
Click to collapse
Help a noobie out, what/where is owain's hopto?
Edit: I'll test without the fix, to be sure and flash the baseband if needed, i understood from the comments in the ROM's thread that its needed for Bluetooth calls.
I might have found the baseband fix link (http://forum.xda-developers.com/showthread.php?t=1776843) can anyone confirm?
mog44net said:
Help a noobie out, what/where is owain's hopto?
Edit: I'll test without the fix, to be sure and flash the baseband if needed, i understood from the comments in the ROM's thread that its needed for Bluetooth calls.
I might have found the baseband fix link (http://forum.xda-developers.com/showthread.php?t=1776843) can anyone confirm?
Click to expand...
Click to collapse
That's the one
Edit: if you need Bluetooth calling on the new baseband, don't flash any cm ROMs. Stay on the old one if you need/want Bluetooth calling.
tahahawa said:
That's the one
Edit: if you need Bluetooth calling on the new baseband, don't flash any cm ROMs. Stay on the old one if you need/want Bluetooth calling.
Click to expand...
Click to collapse
Firstly thanks for all the good Q/A, like a good forum noobie, I'm marking thanks each reply.
I want to make sure I understand your comment. This is what I understood, let me know if I'm off/on. The CM Roms do not work with BT calling, so I should stick with stock if that's important to me? I would assume then for me to get beyond my current issues (OP) my best bet would be to Flash the 2.3.4 stock?
Thanks again for the info and time.
***edit***
Nix the above. I completely read it wrong, thought you were saying all CM ROMs didn't work with Bluetooth. Just so on the current Baseband.
I'm on Jul 15 2011 Baseband currently, so I'll attempt the CM7 ROM this weekend when I'm back home and able to devote more focus. Coming from stock 2.3.3 do I need to flash a kernel as well or will that be in the ROM <---showing my ROM noobness but unashamed to learn.
mog44net said:
Firstly thanks for all the good Q/A, like a good forum noobie, I'm marking thanks each reply.
I want to make sure I understand your comment. This is what I understood, let me know if I'm off/on. The CM Roms do not work with BT calling, so I should stick with stock if that's important to me? I would assume then for me to get beyond my current issues (OP) my best bet would be to Flash the 2.3.4 stock?
Thanks again for the info and time.
Click to expand...
Click to collapse
If you decide to get the newer baseband (you get it with 2.3.4 kdz, only way to get new baseband) and bt calling is important, do not go to cm. If you don't mind staying on the older baseband, bt calling will work fine on cm.
tahahawa said:
If you decide to get the newer baseband (you get it with 2.3.4 kdz, only way to get new baseband) and bt calling is important, do not go to cm. If you don't mind staying on the older baseband, bt calling will work fine on cm.
Click to expand...
Click to collapse
Lol, I feel so dumb, its like learning a new language while being held underwater.
kdz=?
I'm trying to understand why I would decide to get the newer baseband? If I do I can use BT calling but can't use CM7 ROMs, if I don't I can use CM7 ROMs and BT calls should work fine. Dont see the upside to upgrading the baseband, unless it has issues?
BTW as I haven't seen it, I get happy feelings when I look at your avatar
mog44net said:
Lol, I feel so dumb, its like learning a new language while being held underwater.
kdz=?
I'm trying to understand why I would decide to get the newer baseband? If I do I can use BT calling but can't use CM7 ROMs, if I don't I can use CM7 ROMs and BT calls should work fine. Dont see the upside to upgrading the baseband, unless it has issues?
Click to expand...
Click to collapse
KDZ = LG's proprietary file type to update their phones via PC officially. A lot of people say the new baseband gives them better gps and call quality. Basically if you don't change baseband to the new one, everything will work perfectly. If you DO switch, everything will work perfectly, but only on stock. Everything will work on cm except Bluetooth calling with the new baseband. I don't think it's worth restricting yourself to stock because of the new baseband and and bt calling. My recommendation? Don't change baseband, just go to cm. Also, soon we might start to see android 4.1.1 jelly bean. They won't be stable for a while though.
Too much fun.
Couldn't wait, just finished flashing CWM, then backed up, then wiped like 400x then dropped the CM7 ROM you sugested.
Longest 10 minutes of my life letting it sit.
Working great, I'll update here with any additional info or create a new thread.
TY TY TY all
Update -
Still working great, only two issues.
* Cellular network is only showing E, played with the settings but can't seem to get any G networks.
* Google apps/play isn't installed, I think I have this one figured out to download/flash from here (http://forum.xda-developers.com/showthread.php?t=1049154) (http://goo.im/gapps/) but I'm confused about which one to DL.
help plox?
mog44net said:
Update -
Still working great, only two issues.
* Cellular network is only showing E, played with the settings but can't seem to get any G networks.
* Google apps/play isn't installed, I think I have this one figured out to download/flash from here (http://forum.xda-developers.com/showthread.php?t=1049154) (http://goo.im/gapps/) but I'm confused about which one to DL.
help plox?
Click to expand...
Click to collapse
If it's cm7 get the latest gb one, if it's cm9 get the latest ics one... It has gb or ics in the name of the file.
Sent from my LG-P999 using xda app-developers app
cainG2x said:
If it's cm7 get the latest gb one, if it's cm9 get the latest ics one... It has gb or ics in the name of the file.
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
Much thanks, i'll do that now.
Any ideas on being stuck on EDGE network only?
mog44net said:
Update -
Still working great, only two issues.
* Cellular network is only showing E, played with the settings but can't seem to get any G networks.
* Google apps/play isn't installed, I think I have this one figured out to download/flash from here (http://forum.xda-developers.com/showthread.php?t=1049154) (http://goo.im/gapps/) but I'm confused about which one to DL.
help plox?
Click to expand...
Click to collapse
Yeah goo.im/gapps is the best. For the cell network, try going settings> wireless>mobile>network operators and select "select automatically"
So I found a tool on XDA that allows me to put the ROM of choice to be ported and the base ROM. I'm trying to port Paranoid Android 2.00 since we don't have it, and now that we have somewhat steady CM10 nightlies I *should* be able to use it as a base. (The tool is called RomPorter)
So I went ahead and compiled a ROM, but I'm not sure if I should flash. I mean if it was this easy to port ROM's wouldn't we have ROM's just popping up everywhere? I used the HTC One X International version's PA 2.00 as the input ROM btw. I have some coding experience in Java but if it's this easy to port without any coding required why hasn't it been done yet? Just curious. I looked at the CM9 guide to porting PA and I have to make a linux portal and all those things. Basically my main question is, will this work? I don't want to flash and end up hard bricking my phone. I went and checked the build.prop, and framework and it all seemed like a hybrid of CM10 nightly and Paranoid Android 2.00 but is there something I'm missing?
Thanks a lot guys! I'm tired of just being somebody who stands on the side and waits for things to get ported or created. I'm taking a heavy load in college but I want to try and port something at least to contribute.
Using the international base could cause a brick unless you ported an evita kernel too. The international one x has a different partition layout as well.
Read read read, check, double check and triple check. When your confident its possibly bootable, sure that it is not harmful THEN flash it to your device first. Ports are always going to start with bugs. Don't expect perfection, expect a WIP. Importantly, have fun learning. Most importantly , FIRST FLASH IS ALWAYS YOURS :beer::beer:
Added People port roms all the time for themselves. Now posting one on xda and maintaining a thread with dozens-hundreds of followers is a WHOLE DIFFERENT STORY
I just want to try it but I'm afraid it'll brick. I mean what's the worst case scenario? Boot loop then restore to my nandroid? Or being stuck with a brick forever? I don't have a backup phone at the moment lol. Maybe I should invest in one.
If you flash something that overwrites hboot you're hard bricked. That's what I meant by different partition layout.
Here's a easier start for jb paranoid Android port.....dload the HTC evo 4g lte jb paranoid port rom, unzip it, delete the included boot.img, use a hox boot.img from a hox jb rom to replace it with. Zip it and flash it.(use the one XL cm10 boot.img) It will give u a bootable port of jb paranoid Android. Then like most ports, you will start fixing bugs. Camera and wifi won't work, you will need to fix those for sure. But a lot will work so start with priority bug fix#1 and keep on goin
Added: paranoid android rom I would consider the land of the brave for first time porting. U may encounter fixes to be harder than some less modified roms.
I understand now what the scare was. But when taking the Evo LTE ROM and pushing our own boot.img it'll allow me to at least get it started to see what I need to get going and fix! That's a fantastic idea. I'm going to head over there now and see what ROM's they have. I mean technically we share very similar devices internally right? I haven't looked into the Evo specs much.
Shaddy-Z. said:
I understand now what the scare was. But when taking the Evo LTE ROM and pushing our own boot.img it'll allow me to at least get it started to see what I need to get going and fix! That's a fantastic idea. I'm going to head over there now and see what ROM's they have. I mean technically we share very similar devices internally right? I haven't looked into the Evo specs much.
Click to expand...
Click to collapse
make sure you pull out any radio images you find in the roms you look at.
Could I push the ones from a cm10 nightly?
No idea. Probably. Or just don't include one.
getting in contact with the developer for the Evo PA ROM. Hopefully this goes somewhere.
Don't we already have a pa rom? You've inspired me though. I'm going to look at porting roms too.
The PA ROM is still ICS, and the biggest killer is that the multi-touch fix is not incorporated because the ROM was cooked pre kernel release unfortunately. The latest update the dev was supposed to release didn't boot and I don't know what happened after that.
And do it! The more devs the better. I want some variety in this little community.
By the way, PARANOIDANDROID 2.00 is not out yet. The last OFFICIAL release is 1.992: Changelog. As for the port, I would love to port roms to our device, since it is my primary device.
I already port ROMs from the i9100 to i777(SGSII Internation to AT&T US Version), but this is a VERY simple operation. And you can use a pre-made program to port by ktoonsez called Flashaholics, but it is only for porting to the i777. I hope we eventually get that far but these 2 devices are far more similar that the One X/OneXL or Evo LTE/One XL.
Just use the latest paranoid rom with the latest cm10 boot.img. I did it a few times when I had my hox. And gunny is right. Either pull the radio or flash a hox radio after u flash ur port and u will get signal with working talk, text. 3g should work too, mms won't, streaming video will be iffy. Just run thru the major stuff, write down what's broken, prioritize it, then always make a nandroid of your previous build so u can revert back if fixes make things worse
---------- Post added at 01:09 AM ---------- Previous post was at 01:03 AM ----------
He's gonna work off a unofficial paranoidandroid jb 4.1 from the evo lte. It'll boot but there will be plenty of fixing to do. I think its for his use/learning, not sure if he plans on putting it up on forums
I don't plan on uploading it to the forums unless I get the features working. I'm off all day tomorrow so I'll probably give it a shot to see what I can do.
I also realized PA is not 2.00 after I posted that, buts its still a JB Paranoid ROM so it'll do for now while I learn.
It's really good seeing someone (who isn't a regular dev that I know of?) taking such initiative and asking the right questions and such in order to get some dev'ing underway.
Great job! :good:
stnguyen09 said:
It's really good seeing someone (who isn't a regular dev that I know of?) taking such initiative and asking the right questions and such in order to get some dev'ing underway.
Great job! :good:
Click to expand...
Click to collapse
Thanks! I appreciate it So I got a little ahead of myself and tried it tonight, I'm slowly following a guide and I THOUGHT I was doing everything correctly but it won't flash after "Verifying system partition size" and I got an error. This seems to be a common problem that leads to the updater script, so I'm going to take a look at it when I get up. Could just be a syntax error, or maybe I'm just building it wrong I'm kinda tired
U can always nab the updater script from cm10 hox also. Its been a while and I forgot to mention that. I had the same issue with the evo rooms and that did the trick:beer:
I tried: using the ports updater, the base, and a collaboration of the two and it still didn't go through. Maybe its something else ? I'll try it again to double check.
Alpha Omnirom 5.0 (Trying to get calls to work properly on CM first before doing more omni builds))
baseband is still unknown. So no phone calls or data.
Alpha Cyanogenmod 5.02 with working baseband
https://drive.google.com/file/d/0B4k5OpXTXcS9NF8zN1dreFAtOUk/view?usp=sharing
Build 5.0.1:
https://drive.google.com/file/d/0B4k5OpXTXcS9NVp0Sm9YMFdEUUE/view?usp=sharing
Calls should now work without lockups. Data seems flakey? Let me know your finding
(This is now working due to rolling back to old RIL blobs (pre 4.3). This means that the connection process takes longer on initial start-up and switching to air-plane mode as well. )
Leave wifi on to avoid reboots.
Also this doesnt have the camera bug fix yet that Derteufel made.
Nice.. Never been a fan of omni.. I'm more a cm or aosp person
Sent from my GT-I9305 using XDA Free mobile app
REVIEW
Thank you very much for this build for the i9305
I have been waiting for the first lollipop build
I installed this rom and this is a written review after one hour of usage
1 the phone boots without any problem
2 lollipop gapps are working
3 Sometimes wifi works and sometimes no
4 Bluetooth works
5 some random reboots and sometimes it stuck so I need to remove the battery to get it working again
6 no FCs at all
7 seems fast
8 when I open an app installe from play store the phone stucks and I remove the battery
Thanks again and I wish u improve this rom in the coming days
Good job mate but I think it'll be better to edit your thread to make something more attractive, Flash Guide for noobs , links to gapps, alternative dl links , what works, what doesn't , credits , shiet like this would be better for everyone.
The main problem of your rom seems to be the kernel (random reboots , wifi issues , random freezes)
Anyways , good luck and thank you for the rom
aaz03 said:
Good job mate but I think it'll be better to edit your thread to make something more attractive, Flash Guide for noobs , links to gapps, alternative dl links , what works, what doesn't , credits , shiet like this would be better for everyone.
The main problem of your rom seems to be the kernel (random reboots , wifi issues , random freezes)
Anyways , good luck and thank you for the rom
Click to expand...
Click to collapse
Thanks for the feedback.
This isnt meant for n00bs to flash yet. This is an alpha.
In Alphas you expect to get problems! This is only meant for testing and for trying out 5.0 on your device...
can we flash this normally?
CM 5.0.1 build added to OP. Please read notes about what isnt working before flashing!
So the latest build is the most stable one (CM12)? Can I help you in any way, testing, logs or something?
limnaln said:
So the latest build is the most stable one (CM12)? Can I help you in any way, testing, logs or something?
Click to expand...
Click to collapse
Well at this point in time no. I've just got to try to figure out whats going wrong still and then people can test to see if it works for them and if there is any long term problems with it. Until then its just make a change, compile and flash and I'll let people know if I get anywhere.
for me it is stuck on bootloop... first flashed wih wipe full/dalvik/cache then flashed gapps - bootloop. second dirty flashed again, booted, android is upgrading, optimizing apps, then rebooted and again bootloop... how to get past this ?
Tested. Boots okay. Data baseband ok. Incoming calls ok. Outgoing calls impossible. Tested with 2g
laurent.siku said:
for me it is stuck on bootloop... first flashed wih wipe full/dalvik/cache then flashed gapps - bootloop. second dirty flashed again, booted, android is upgrading, optimizing apps, then rebooted and again bootloop... how to get past this ?
Click to expand...
Click to collapse
As I said this doesnt have the camera firmware patch added so some people might get bootloops... I'll add this in the next day or two from Derteufel
infrag said:
As I said this doesnt have the camera firmware patch added so some people might get bootloops... I'll add this in the next day or two from Derteufel
Click to expand...
Click to collapse
So, we are at the final step - outgoing calls, huh?
There also appeared some new commits on nameless gerit, just informing
Outgoing calls can be made now. But it seems to lockup when hanging up. New link in OP for 'new' build.
Calls should now work!
This is using old ril blobs so initial connection from boot will take longer. Also I think data is stuffed a bit. Seems to take a long time to get connected. Seems to work for me after that though. Post your finding please!
Hopefully Derteufel can figure out the problem with the newer blobs but till then this is working if anyone is interested.
Edit: only got one question. Can wifi be turned off. Will disabling it cause bootloops?
infrag said:
Calls should now work!
This is using old ril blobs so initial connection from boot will take longer. Also I think data is stuffed a bit. Seems to take a long time to get connected. Seems to work for me after that though. Post your finding please!
Hopefully Derteufel can figure out the problem with the newer blobs but till then this is working if anyone is interested.
Click to expand...
Click to collapse
Yes, it does work indees! In and out! Really great, the whole system is smooth.
Great work. Will be swapping back to the i9305 from the note 2.. All we need now is for someone to work on the stock cm kernel to make it smoother.
Sent from my GT-N7105 using XDA Free mobile app
Great work on calls! Please let us know when you include the camera firmware fix so I can download again and flash, this is the only thing causing me bootloops and preventing me for further testing. Thanks
Sent from my GT-I9305 using XDA Free mobile app
winxuser said:
Great work. Will be swapping back to the i9305 from the note 2.. All we need now is for someone to work on the stock cm kernel to make it smoother.
Sent from my GT-N7105 using XDA Free mobile app
Click to expand...
Click to collapse
Stock kernel? We are only using that to get data working... I'm sure Derteufel will switch to his own kernel as soon as he irons out the problems with phone calls locking up etc. (Or he switches to old RIL blobs for now)
Then there will be the challenge of getting R4P0 drivers to work properly.
After that who knows? Fix opensource compass?
Then Nameless may have other upgrades to implement for HWC.
Hi all,
We are starting today daily AOSP builds for all 2014 Sony devices so that you can enjoy a NEXUS like experience
Thanks
SONY for publishing AOSP base gits
All AOSP developers and testers
Sources
https://github.com/fxpdev
Download
http://fxpblog.co/
howto flash
download Android SDK
http://developer.android.com/sdk/index.html#Other
in adt-bundle-windows-x86_64-xxxxxxxx/sdk/platform-tools folder you have the required files
copy the following files in same folder where your AOSP image files are
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
disconnect device, press power and enjoy!
What an excellent Xmas gift from the fxp team. Will try later today, thanks
???
For the newbies:
You don't need the entire SDK. Just download a small ADB and Fastboot package from XDA, it'll make your life much easier.
Builds are building and/or uploading, will be available on: http://fxpblog.co/aosp/aosp-5-0/
Bootloader locked or unlocked only?
lirondeespaña said:
Bootloader locked or unlocked only?
Click to expand...
Click to collapse
I'll be quick here:
Until root for a locked bootloader has been found for the Z3 series, no ROM can be flashed.
And even after (or if) you get a recovery and root working on a phone with a locked bootloader, there's still something you have to consider: you cannot flash boot images others than completely stock ones onto a device with a locked bootloader.
This ROM's functionality is completely different than that of any stock ROM, meaning it requires its own boot image (so, one that is not stock).
Is there a list of what doesn't work?
Sean09 said:
Is there a list of what doesn't work?
Click to expand...
Click to collapse
There are no builds yet so nobody can report back, but camera is said to be broken right now (as with any other AOSP ROM).
Maybe no builds today, they should announce this after at least one build is uploaded.
jsscx said:
Maybe no builds today, they should announce this after at least one build is uploaded.
Click to expand...
Click to collapse
That would have made sense.
Effort is underway nevertheless.
Be interested to see how long it takes to achieve Daily Driver status. I suspect that's far away... Be surprised if DD aosp for z3c arrives before the z4c hits shelves.
Anyway thanks for working on the z3c. Look forward to peoples experiences with this.
Lol...trust in them,they are nearly the only ones who work a lot on our device.And I just couldn't keep patience,z3c is not popular ,which causes it so slow to see any booting builds on it
edit:
finally found it,http://uploaded.net/f/dv4mt9
sry for previous words.
will test
edit2:
Flashed.
1.no modem band,while wifi works
2.nfc dosen't work
3.no sound,no camera
There may be more issues,but these ones make it not a daily drive...
but at least it boots,and works smoothly!Thank you.
Nothing works? Sony has the code for them I don't understand why they're not releasing them.
jsscx said:
Lol...trust in them,they are nearly the only ones who work a lot on our device.And I just couldn't keep patience,z3c is not popular ,which causes it so slow to see any booting builds on it
edit:
finally found it,http://uploaded.net/f/dv4mt9
sry for previous words.
will test
edit2:
Flashed.
1.no modem band,while wifi works
2.nfc dosen't work
3.no sound,no camera
There may be more issues,but these ones make it not a daily drive...
but at least it boots,and works smoothly!Thank you.
Click to expand...
Click to collapse
Thanks for posting your exoerinece for others to know what's what.
Given this is the first build.... We can only expect improvements which is a good thing. Now they have the build trees and nightlies in order. So let's hope for good progress to follow.
Either way this is good news.. We all have itchy feet for aosp, but at least the devs are now beginning to make strides. So thanks to them for that alone.
There's a 29/12 build. I wonder if it's anything new or just a daily build.
Also, @freexperia what are the sources you're using? I tried looking through your GitHub account but didn't find an aries device tree -- or are you just using the sonyxperiadev branches?
EDIT: Would you guys mind if I mirrored a build every once in a while? DepositFiles and Uploaded cap their download speeds at 50kB/s, way below what most of the planet has.
EDIT2: Here's the mirror I made (hope it's alright with you guys). Took me over 2 hours to get 300MB of data downloaded lol don't want anyone else to feel my pain.https://drive.google.com/open?id=0BzcBVe17cfU-eFp1WnZ3VDRtbUE
I'll be compressing everything I upload with LZMA/LZMA2 and at least a 256MB dictionary -- I'd advise you to have at least 300MB of RAM free when extracting these archives.
Anything RIL-related isn't working (at least not as I can see) -- I have a logcat attached of me fooling around, opening a few apps and such. Perhaps it'll help somebody.
hi
we use sony ones
mirroring is useless since new build comes every day
br
someone755 said:
There's a 29/12 build. I wonder if it's anything new or just a daily build.
Also, @freexperia what are the sources you're using? I tried looking through your GitHub account but didn't find an aries device tree -- or are you just using the sonyxperiadev branches?
EDIT: Would you guys mind if I mirrored a build every once in a while? DepositFiles and Uploaded cap their download speeds at 50kB/s, way below what most of the planet has.
EDIT2: Here's the mirror I made (hope it's alright with you guys). Took me over 2 hours to get 300MB of data downloaded lol don't want anyone else to feel my pain.https://drive.google.com/open?id=0BzcBVe17cfU-eFp1WnZ3VDRtbUE
I'll be compressing everything I upload with LZMA/LZMA2 and at least a 256MB dictionary -- I'd advise you to have at least 300MB of RAM free when extracting these archives.
Anything RIL-related isn't working (at least not as I can see) -- I have a logcat attached of me fooling around, opening a few apps and such. Perhaps it'll help somebody.
Click to expand...
Click to collapse
freexperia said:
hi
we use sony ones
mirroring is useless since new build comes every day
br
Click to expand...
Click to collapse
Thanks for that!
But does each build improve on the previous one? A lot of the daily builds are in essence just copies of the older builds with the only difference being the time at which they were built. At least that's the situation with daily CM builds for this and some other devices.
someone755 said:
Thanks for that!
But does each build improve on the previous one? A lot of the daily builds are in essence just copies of the older builds with the only difference being the time at which they were built. At least that's the situation with daily CM builds for this and some other devices.
Click to expand...
Click to collapse
Dailies are a development tool, not a consumer tool. They are built with what is in the repo's at that time, every day.
If you want builds that are consumer focused with constant improvements over previous you should only flash release builds. Not only will dailies not always be better then the previous, its very likely that they will be worse at time.
jug6ernaut said:
Dailies are a development tool, not a consumer tool. They are built with what is in the repo's at that time, every day.
If you want builds that are consumer focused with constant improvements over previous you should only flash release builds. Not only will dailies not always be better then the previous, its very likely that they will be worse at time.
Click to expand...
Click to collapse
I am aware of that, but I was merely pointing out that not every build brings changes as many builds' only difference than the rest is the date on which it was built -- often, the repo stays the same for several days.
I am in no way blaming them or requesting anything from them, just wanted to point out why I believe mirrors aren't pointless.
Is there a changelog for this rom guys? or am I looking in the wrong place. Cheers
someone755 said:
I am aware of that, but I was merely pointing out that not every build brings changes as many builds' only difference than the rest is the date on which it was built -- often, the repo stays the same for several days.
I am in no way blaming them or requesting anything from them, just wanted to point out why I believe mirrors aren't pointless.
Click to expand...
Click to collapse
Maybe what we need is changelog
I have nothing to do with the ROM.
I just happened to find it available to download at the usual Android file hosting spot.
I'm not a tester or affiliated in any way.
I will not post links out of respect for the dev's.
But if you've been around, then you know the usual places to look and how to find ROM's.
-----------------------------
Bootlegger's ROM
They usually base on GZOSP?
Placing a phone call reboots phone. I believe that's a known issue on all custom ROM's ATM.
Tried installing opengapps but while the zip doesn't have any errors during install, nothing got installed. I think that's another known issue across the board.
What's nice though is Bootlegger's already has a bunch of customization options built in. :good:
Center clock option obviously doesn't work too well (hello stoopid notch). :laugh:
Steps to install ROM
Boot to TWRP
Install ROM.zip
Install TWRP.zip (because ROM install removes it)
Reboot and play
CZ Eddie said:
Placing a phone call reboots phone. I believe that's a known issue on all custom ROM's ATM.
Tried installing opengapps but while the zip doesn't have any errors during install, nothing got installed. I think that's another known issue across the board
Click to expand...
Click to collapse
If you know the Dev, let them know about DU trees.
There's no such issues on dirty unicorn.
It kind of defeats the purpose of having a phone if every time you get a call the phone reboots! I'm grateful that work is being done on custom ROMs but at this time, at least to me is a no go if I can't receive a phone call on my phone. After all, that's why I have a phone. Also, is there a link? I don't see one on the OP.
No link because it's considered rude to post links to a devs work without their permission.
I'm sure when the ROM is ready for prime-time, they will post a thread for it over in the ROM section?
I read in another section that Hangouts phone works on these new ROM's devs are building/tinkering with right now.
Paradoxxx said:
If you know the Dev, let them know about DU trees.
There's no such issues on dirty unicorn.
Click to expand...
Click to collapse
I see that DU has been working on the Pixel 3(XL) for half a month now, any inclination as to why it isn't public yet?
Sent from my Pixel 3 XL using Tapatalk
superchilpil said:
I see that DU has been working on the Pixel 3(XL) for half a month now, any inclination as to why it isn't public yet?
Click to expand...
Click to collapse
Most maintainers don't like releasing a build until most important things work such as ril, volte, mms, etc etc.
superchilpil said:
I see that DU has been working on the Pixel 3(XL) for half a month now, any inclination as to why it isn't public yet?
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
AnierinB said:
Most maintainers don't like releasing a build until most important things work such as ril, volte, mms, etc etc.
Click to expand...
Click to collapse
No idea.
I built it, everything was working perfectly. Did not find any issues at all, and was using it until yesterday's December images dropped.