Develop Bugs

[Q] tablet reboots after going to sleep

Hi.
I installed a custom ROM (CM10) yesterday but ever since then, when the screen is turned off, it will restart after about 1 minute. If I try to turn the screen on again before 1 min, it'll restart. In other words, when it goes to sleep, restart will be required. Please help me on solving this issue. I searched a lot and I thought maybe it has to do with the maximum CPU frequency, I tried changing it but didn't help.
Any ideas on how to solve this problem?

What did you wipe during the install? And what ROM did you install?
Probably to start the best thing to do is redownload the rom, do a full wipe (cache, davlik cache, data, and system), then reflash the rom.

RE
Romman0 said:
What did you wipe during the install? And what ROM did you install?
Probably to start the best thing to do is redownload the rom, do a full wipe (cache, davlik cache, data, and system), then reflash the rom.
Click to expand...
Click to collapse
Thank you for the response.
Yes I did wipe the tablet (a full wipe as you mentioned) before flashing the ROM.
First I had tried Jellytime Sosei and when I realized the problem, I tried "Build 4 Linaro Stock" from this post but still the problem exists :/ Before installing the first ROM, I had done a full wipe, but not for the second one.
Thanks again for helping me.

Try a full wipe to build 1 from the sosei thread, build 1 or 2 from the linaro thread, or the original cm10 thread. Those were the most stable for me. It's a weird issue, so it's probably a bad download or flash issue.

Its screaming bad install or bad settings, wipe twice then flash again, make sure to change nothing for speed, governor, io scheduler, and stock included kernel.
Don't even install an app for OC. It may be a huge bug showing for the first time, if we go carefully we'll find it, or get it going properly again. Occasionally the blackhole wipe used can clear up flash issues, but wipes internal sd as well.
Tapatalked from my HTC DNA

Thank you guys. I'll try what you said when I get home.
Romman0 said:
Try a full wipe to build 1 from the sosei thread, build 1 or 2 from the linaro thread, or the original cm10 thread. Those were the most stable for me. It's a weird issue, so it's probably a bad download or flash issue.
Click to expand...
Click to collapse
I'm gonna give those three that you said a try, when I get home. But, can you give me the link of the original CM10 thread that you're saying? I thought there isn't one for A100, since I didn't find it on their website. Is there a official CM10 ROM for A100?

There is no Official CM10 for the A100, Romman was referring to this link for the original CM10: http://forum.xda-developers.com/showthread.php?t=1792634

OK, after wiping everything twice and also wiping internal SD, I flashed "Build 2" from CM10 Unofficial Builds thread. Apparently this one doesn't have that bug and everything is fine, but the problem is that it's buggy and clock doesn't show well and when you press recent apps button, the overlay doesn't cover the bottom of the screen. So, I'm gonna try and flash Build 1 or maybe newer Builds and see what I get.
But is there a work around for the clock and other bugs problem in Build 2?

aminbandali said:
OK, after wiping everything twice and also wiping internal SD, I flashed "Build 2" from CM10 Unofficial Builds thread. Apparently this one doesn't have that bug and everything is fine, but the problem is that it's buggy and clock doesn't show well and when you press recent apps button, the overlay doesn't cover the bottom of the screen. So, I'm gonna try and flash Build 1 or maybe newer Builds and see what I get.
But is there a work around for the clock and other bugs problem in Build 2?
Click to expand...
Click to collapse
There isn't one, no, but it was corrected in B4. I think. I'm building this stuff without the device so I can only go by reports. You're reporting issues that no one else has, is your device functional otherwise? Like is it ok on a stock Rom? Using the correct gapps, any other changes or mods?
Tapatalked from my HTC DNA

pio_masaki said:
There isn't one, no, but it was corrected in B4. I think. I'm building this stuff without the device so I can only go by reports. You're reporting issues that no one else has, is your device functional otherwise? Like is it ok on a stock Rom? Using the correct gapps, any other changes or mods?
Tapatalked from my HTC DNA
Click to expand...
Click to collapse
It was totally OK on the stock ROM and this never had happened, not even once.
I'm using the gapps that I got from your CM10 ROMs thread, which is apps for v 4.1.2. I haven't changed ANYTHING else in the tablet, no mods or customization at all... :/
P.S. I tried Build 4 again, this time I fully wiped everything before flashing, but again, the bug still exists. gonna try some other guys' ROM to see if the problem is with this ROM or it's from my device.

aminbandali said:
It was totally OK on the stock ROM and this never had happened, not even once.
I'm using the gapps that I got from your CM10 ROMs thread, which is apps for v 4.1.2. I haven't changed ANYTHING else in the tablet, no mods or customization at all... :/
P.S. I tried Build 4 again, this time I fully wiped everything before flashing, but again, the bug still exists. gonna try some other guys' ROM to see if the problem is with this ROM or it's from my device.
Click to expand...
Click to collapse
If its fine on stock then its gonna be Rom or kernel, just never heard of this happening before. What governor did you use?
Tapatalked from my HTC DNA

Is there a super ultra wipe flashable script?

My phone's software/kernel/partition (or something like that) is so messed up that my battery life sucks on all roms (even on roms I changed back to after receiving the problem that never had the problem), my phone seems to overheat, and reboots/freezes all the time. Battery stats says nothing really. My battery life is like TWO to THREE times LESS than before I flashed a bunch of ROM and kernels.
So basically I need something flashable that:
- Wipe all RE-BUILDABLE partitions COMPLETELY (and then rebuilds them) and/or gives cleans all partitions
- Formats and cleans everything on the phone (in a way it doesn't break any default features of the phone)
- Fixes any kernel bugs/glitches that retain after flashing other kernels
- Fixes all modem issues (like that flashable modem fix I saw but incorporated with everything above)
- Sets everything to default settings
- COMPLETELY and SAFELY removes Wanam and XPOSED framework out of the phone (I think it is causing me problems)
Basically, I think I broke something and want to completely fix the issue, so I can SUPER clean flash a KitKat rom and not have uncommon issues that the ROM does not have (I'm currently on 4.3)

Mystery? said:
My phone's software/kernel/partition (or something like that) is so messed up that my battery life sucks on all roms (even a rom I changed back to after receiving the problem), my phone seems to overheat, and reboots/freezes all the time. Battery stats says nothing reallu. My battery life is like TWO to THREE times LESS than before I rooted it and flashed a ROM.
So basically I need something flashable that:
- Wipe all RE-BUILDABLE partitions COMPLETELY (and then rebuilds them) and/or gives cleans all partitions
- Formats and cleans everything on the phone (in a way it doesn't break any default features of the phone)
- Fixes any kernel bugs/glitches that retain after flashing
- Fixes all modem issues (like that flashable modem fix I saw but incorporated with everything above)
- Sets everything to default settings
- COMPLETELY and SAFELY removes Wanam and XPOSED framework out of the phone (I think it is causing me problems)
Basically, I think I broke something and want to completely fix the issue, so I can SUPER clean flash a KitKat rom and not have uncommon issues that the ROM does not have (I'm currently on 4.3)
Click to expand...
Click to collapse
Use your recovery (twrp being the best one to do this) and wipe everything. back up your internal memory, then remove your sdcard.
boot into recovery and go to wipe menu and click all the options. The wipe will fail on extsdcard but that's because you have removed your sdcard. shut power off, replace your sdcard and boot back into recovery. Flash whatever rom you have on your sdcard. This should fix any problem you have had. If you are still getting overheating bootloops bla bla bla, then this is a phone issue.
Oh and don't do a titanium restore since you don't know what exactly is messing with your phone.

Seconded, all opposed? <crickets.wav grasshoppers.wav.bak>...
Sent from my SM-N900T using Tapatalk

Mystery? said:
My phone's software/kernel/partition (or something like that) is so messed up that my battery life sucks on all roms (even on roms I changed back to after receiving the problem that never had the problem), my phone seems to overheat, and reboots/freezes all the time. Battery stats says nothing really. My battery life is like TWO to THREE times LESS than before I flashed a bunch of ROM and kernels.
So basically I need something flashable that:
- Wipe all RE-BUILDABLE partitions COMPLETELY (and then rebuilds them) and/or gives cleans all partitions
- Formats and cleans everything on the phone (in a way it doesn't break any default features of the phone)
- Fixes any kernel bugs/glitches that retain after flashing other kernels
- Fixes all modem issues (like that flashable modem fix I saw but incorporated with everything above)
- Sets everything to default settings
- COMPLETELY and SAFELY removes Wanam and XPOSED framework out of the phone (I think it is causing me problems)
Basically, I think I broke something and want to completely fix the issue, so I can SUPER clean flash a KitKat rom and not have uncommon issues that the ROM does not have (I'm currently on 4.3)
Click to expand...
Click to collapse
I would go back to stock for 2 days and see what happens.
TWEAKED N3

dragonstalker said:
Use your recovery (twrp being the best one to do this) and wipe everything. back up your internal memory, then remove your sdcard.
boot into recovery and go to wipe menu and click all the options. The wipe will fail on extsdcard but that's because you have removed your sdcard. shut power off, replace your sdcard and boot back into recovery. Flash whatever rom you have on your sdcard. This should fix any problem you have had. If you are still getting overheating bootloops bla bla bla, then this is a phone issue.
Oh and don't do a titanium restore since you don't know what exactly is messing with your phone.
Click to expand...
Click to collapse
Why go thru all the machinations with the extSD card? Why not just uncheck that in wipe options?
How about formatting partitions?

les_garten said:
Why go thru all the machinations with the extSD card? Why not just uncheck that in wipe options?
How about formatting partitions?
Click to expand...
Click to collapse
He does not need to format partitions. And when making suggestions, i tend to make sure that i make the process as simple as possible, and with as little wiggle room for error. Remove the Sdcard, there is no room for error. Can wipe something thats not there.

@dragonstalker, I did what you said, I think for the few hours on Darthstalker I was on, I was getting really good battery life
 @BACARDILIMON, but when I went to KitKat (stock rom). My battery life became worse than what I had when I made this thread. Da heck?!

Mystery? said:
@dragonstalker, I did what you said, I think for the few hours on Darthstalker I was on, I was getting really good battery life
@BACARDILIMON, but when I went to KitKat (stock rom). My battery life became worse than what I had when I made this thread. Da heck?!
Click to expand...
Click to collapse
what kernel did you flash with the kit kat rom. And did you make sure that it was a 4.3 compatible kit kat rom?

dragonstalker said:
what kernel did you flash with the kit kat rom. And did you make sure that it was a 4.3 compatible kit kat rom?
Click to expand...
Click to collapse
I flashed to stock through the instructions linked on the Infamous Touchwiz ROM for KitKat. I went to completely stock (with stock kernel) and my battery life got much more worse than before - after changing the settings and whatnot. Flashed Colonel X R13 and boom battery went to 6 hours although not as much as 8 like I used to have in the JB stock ROM days.

brightness issue and custom ROM's and which CM build to use?

Hi,
I'm about to buy a LG G Pad 8.3 and plan to root it and flash CM11 right away. I've read in a few places that there is a brightness issue with custom ROM's but haven't seen a clear way to avoid it or fix it (other than perhaps flashing stock reflashing CM?). I've also seen various posts suggesting fixes to this in the latest CM builds and also a custom kernel that could be used (AIC?). So which, CM build should I use (official, infected) and can anyone please explain how to avoid the low brightness issue?
Thankyou!

thegrantonstarcause said:
Hi,
I'm about to buy a LG G Pad 8.3 and plan to root it and flash CM11 right away. I've read in a few places that there is a brightness issue with custom ROM's but haven't seen a clear way to avoid it or fix it (other than perhaps flashing stock reflashing CM?). I've also seen various posts suggesting fixes to this in the latest CM builds and also a custom kernel that could be used (AIC?). So which, CM build should I use (official, infected) and can anyone please explain how to avoid the low brightness issue?
Thankyou!
Click to expand...
Click to collapse
Use whatever CM build you want. I don't know much about the other fix, I assume you mean when infected said he committed some change that is ROM side.
The other method is to pick whatever CM version you want(or other ROM for that matter). Use the AIC kernel installer and select custom ROM's when prompted. Then if you were on Stock LG 4.4.2 before you flashed CM you pick the 4.4.2 ROM, and if you were on Stock LG 4.2.2 before you flashed you pick the 4.2.2 ROM. 4.4.2 and 4.2.2 have nothing to do with CM version only which Stock LG ROM you started with.

Ok thanks
Sent from my Nexus 10 using XDA Premium HD app

thegrantonstarcause said:
Hi,
I'm about to buy a LG G Pad 8.3 and plan to root it and flash CM11 right away. I've read in a few places that there is a brightness issue with custom ROM's but haven't seen a clear way to avoid it or fix it (other than perhaps flashing stock reflashing CM?). I've also seen various posts suggesting fixes to this in the latest CM builds and also a custom kernel that could be used (AIC?). So which, CM build should I use (official, infected) and can anyone please explain how to avoid the low brightness issue?
Thankyou!
Click to expand...
Click to collapse
I think you are referring to a dimness issue when going to a custom rom from stock 4.4.2. Its related to the custom recovery not supporting soem changes to the partition or directory structure made by the LG update. Just make sure to update TWRP to 2.7.0.1 before flashing your custom rom.
Any rom will due. I'd advise sticking with the M-releases so you can get some stability and be able to do a monthly dirty flash. I've heard good things about infected's CM build.

ruibing said:
I think you are referring to a dimness issue when going to a custom rom from stock 4.4.2. Its related to the custom recovery not supporting soem changes to the partition or directory structure made by the LG update. Just make sure to update TWRP to 2.7.0.1 before flashing your custom rom.
Any rom will due. I'd advise sticking with the M-releases so you can get some stability and be able to do a monthly dirty flash. I've heard good things about infected's CM build.
Click to expand...
Click to collapse
Ok I'll risk this question (I thought that I knew the answer)....
Brightness
I was on Stock 4.4.2. I had rooted the Pad and then ensured that the version of TWRP installed is 4.4.2-v500-TWRP_2.7.0.1-recovery.zip.
So I should be fine when installing Infected's build of the Slimkat ROM as it also is built on 4.4.2 and yet I can't see a thing when it first boots.
The screen is way too dim. Eventually when I work blind to get it to finish its set up the screen is still very dim. Booting back into recovery it is fine and bright. A reboot and it is really nice and bright for about ten seconds and then it will reduce a small amount but placing into standby and then back on again and it is perfect.
It will remain perfect until I need to reboot it and then it will dim slightly until I place it into standby and then back on again and then it is absolutely perfect.
So what am I missing with the version of TWRP I have installed over that of the stock 4.4.2 UK OTA ROM and using any custom ROM based on 4.4.2...?
Thanks

vimesUK said:
Ok I'll risk this question (I thought that I knew the answer)....
Brightness
I was on Stock 4.4.2. I had rooted the Pad and then ensured that the version of TWRP installed is 4.4.2-v500-TWRP_2.7.0.1-recovery.zip.
So I should be fine when installing Infected's build of the Slimkat ROM as it also is built on 4.4.2 and yet I can't see a thing when it first boots.
The screen is way too dim. Eventually when I work blind to get it to finish its set up the screen is still very dim. Booting back into recovery it is fine and bright. A reboot and it is really nice and bright for about ten seconds and then it will reduce a small amount but placing into standby and then back on again and it is perfect.
It will remain perfect until I need to reboot it and then it will dim slightly until I place it into standby and then back on again and then it is absolutely perfect.
So what am I missing with the version of TWRP I have installed over that of the stock 4.4.2 UK OTA ROM and using any custom ROM based on 4.4.2...?
Thanks
Click to expand...
Click to collapse
From what I can understand, TWRP 2.7.0.1 should have fixed that startup dimness issue (reference: http://forum.xda-developers.com/showpost.php?p=52019098&postcount=343).
Otherwise, you can try flashing back to 4.2 stock rom before flashing to a custom rom (reference: http://forum.xda-developers.com/showpost.php?p=52564158&postcount=360).

ruibing said:
From what I can understand, TWRP 2.7.0.1 should have fixed that startup dimness issue (reference: http://forum.xda-developers.com/showpost.php?p=52019098&postcount=343).
Otherwise, you can try flashing back to 4.2 stock rom before flashing to a custom rom (reference: http://forum.xda-developers.com/showpost.php?p=52564158&postcount=360).
Click to expand...
Click to collapse
Thanks
I understood that as well but now get the impression that other influences could be a contributory cause. In the thread of Infected's SlimKat's ROM he had noted some build issues which could well have caused that, as others had noted it, and so compiled another build. One other who had noted it had flashed back to 4.2 and used 2.7.0.0 of TWRP and yet still got the issue.

vimesUK said:
Thanks
I understood that as well but now get the impression that other influences could be a contributory cause. In the thread of Infected's SlimKat's ROM he had noted some build issues which could well have caused that, as others had noted it, and so compiled another build. One other who had noted it had flashed back to 4.2 and used 2.7.0.0 of TWRP and yet still got the issue.
Click to expand...
Click to collapse
I was fighting a dimness issue on the latest Mahdi last weekend and went back to stock rooted because of it. Something definitely has changed since I took the 4.4.2 stock update from LG. I did not try going all the way back to 4.2 as an alternative. I do know that the issue is worked around in the TWRP with 2.7.0.1, however once I boot into Mahdi everything is very dim until I change the brightness slider.
In addition when I would change the brightness slider (in mahdi) the rate at which the screen would change was dramatically different from previously. Something in the 4.4.2 update has changed the way brightness works on the V500. I'm wondering if it is related to the fix that made the 7 led lights go away for so many (including me) on 4.4.2. I can say that it was annoying enough for me to revert to stock and simply run stock and rooted again...

I also noticed, with two or three different custom ROMs that supposedly had the brightness fix in there (AICP and Infected's CM nightly from the 21st) they both booted up with the backlight basically off. When scrolling the brightness meter, only the last 5th or so was usable, and approximately equivalent to the whole meter in stock. I went back to stock for that and other reasons, but I may try it again soon, especially if someone has a suggestion... I am leery of trying to go to 4.2.2 since I had such bad luck flashing LRS and could only get recovery 2.7.0.1 working properly.

I don't really like to draw comfort from other peoples issues as noted but I'm kinda glad that at least the methodology I was applying when I installed these custom ROM's was ok. Also the version of TWRP was applicable for the version of KK being used, to go with the bootloader, I guess.
What is being described since my last comment is typical also of what I'm seeing.
I'm tempted to just go back to stock KK, at least the full and complete range of brightness control works without issue.

I ended up biting the bullet, and found a TWRP 2.6.3.2 recovery that worked properly, though it is still incredibly dim brightness-wise. But now I was able to install LRS G Pad, which is stock based so it doesn't have the brightness issues... but hey, at least it's a custom ROM, right?

IBJamon said:
I ended up biting the bullet, and found a TWRP 2.6.3.2 recovery that worked properly, though it is still incredibly dim brightness-wise. But now I was able to install LRS G Pad, which is stock based so it doesn't have the brightness issues... but hey, at least it's a custom ROM, right?
Click to expand...
Click to collapse
No, it is not in custom ROM section, but a stock based that give the speed of AOSP into stock-like ROM, so it is the best choice for every device out there, plus, you can install some kernels that's made for stock...
Sent from my LG-V500 using Tapatalk

i got the same problem but i found a way to fix it,sort of.When my rom its booting the backlight is low,i installed the lux brightness app,i press the power button one time and the tablet sleeps,when it comes back i got full backlight.It stays full until reboot,in fact i will never do a reboot.Try that maybe fix your problem

Fix that
I found a fix for that,let the ROM boot and then press the brightness setting to full,press the power button to go to sleep and then press to wake up,that work for me,I can use any custom rom

[Resolved] Problem with first boot on stock based MM ROM

Hello guys.
May I ask your help for a weird issue I have since the MM based stock ROMs. Indeed, I run CM based ROMs since kitkat
But 3 weeks ago, I decided to test the Fulmics ROM. I did a full wipe (including internal storage), then I installed fulmics from internal storage, and after the first boot, I arrived on the lockscreen asking me to draw a pattern to unlock my phone (nothing about unlock SIM card).. But, obviously, I never configured the ROM to have that pattern, given the fact it's the first boot. And any of the random patterns I draw are working of course....
I tried different parameters in the Aroma installer (i double and triple checked that I had D855 chosen), I also tried with other MM based stock ROMs, but I still have this damn pattern. The weird thing is that I don't have this problem with LP based stock ROMs.
As I am using TWRP 3.0, I installed both official and unofficial versions. I even tried to reinstall TWRP 2.7, but the bug was still there.
Do you have any idea what's going on ? Thank you very much guys !!

After flashing, at first boot it sound take you through the setup stuff then take you to your home screen when you're finished. At that point you should be able to go into the settings and look at the lockscreen settings. Does it immediately go from the setup to the lockscreen, or is there a delay that causes the screen to get locked? Which other MM ROMs have you tried and had this happen with? I would think doing a full wipe beforehand would make this impossible unless it was maybe a bad build, which could maybe be possible if it was one ROM (maybe), but very unlikely multiple developers would happen to make this same mistake when building.

Hi akksnv, thank you for your answer !
akksnv said:
Does it immediately go from the setup to the lockscreen, or is there a delay that causes the screen to get locked? Which other MM ROMs have you tried and had this happen with?
Click to expand...
Click to collapse
Yes it goes directly to the lockscreen after the bootamination. I've tried different fulmics versions (3.1, 3.5, 4.0), the Nova Stock ROM, and the SeXy ROM, and yes, with all these ROMs I have this bug.
akksnv said:
I would think doing a full wipe beforehand would make this impossible unless it was maybe a bad build, which could maybe be possible if it was one ROM (maybe), but very unlikely multiple developers would happen to make this same mistake when building.
Click to expand...
Click to collapse
Yes, it's definitively a bug with my phone and not with these ROMs. And yes, it's very strange that after a full wipe, this locksreen stuff shows up... Because I use this pattern lockscreen on my actual Resurrection Remix ROM, but the wipe should erase every setting....
Other werid thing, I have 30 attemps to unlock the phone, and after the first try, the cycle counter goes to 29/30 and comes back to 30/30 after 3 seconds.

I saw something somewhere else that sounded like this kind of thing also happens if you have a locked/encrypted SIM card, could that possibly be the case? I don't know that this behavior would be different between LP and MM if this were the cause, but thought I'd mention it.

I have no idea about my sim card but maybe it worths trying to install without it in the phone.
Anyway, thanks for your help man !

For those it can help, I resolved my problem by installing a lollipop KDZ file, through LG Flashtool.
I don't know why, but my lockscreen problem disappeared after that.

[ROM][E6553][6.0.1] AOSP by FXP[160826] !!NEW WORKING CAMERA!! latest Security Patch

This Rom is pure AOSP made by FXP Team
I AM NOT RESPONSIBLE FOR ANY DAMAGES THAT MAY CAUSE YOUR DEVICE
Your Bootloader must be unlocked and TWRP recovery installed.
You must have a working adb and fastboot connection to your pc.
Installation:
-Place GApps on your internal SDcard
-Reboot into TWRP and make a Backup of your System (boot,system,data)
-In TWRP delete your data and cache/dalvik
-shutdown your device and restart into fastboot mode
-flash the extracted system.img "fastboot flash system system.img"
-reboot into TWRP und flash GApps
-shutdown your device and restart into fastboot mode
-flash the extractet boot.img "fastboot flash boot boot.img"
-restart your device (first start take a few minutes)
-done
The File "userdata.img" in the Rom zip just delete your internal SDcard so please dont flash it.
Recovery: In the Rom Download is a "recovery.img" this is the Sony AOSP recovery you can flash it but you cant do much with this and you dont need to flash it.
If you want to use TWRP, you have to boot your Devices with TWRP "fastboot boot twrpxxx.img". You have to do this everytime you want to use TWRP. I read that FXP fixed the kitakami-recovery bug, lets hope its in the next release.
Downloads: Rom 26.08.2016
TWRP
Root: Hotboot into TWRP and flash the latest betaSU.
Xposed: Hotboot into TWRP and flash latest Systemless Xposed framework and install latest Material Xposed Installer.

reserved

Screenshots?
Has anyone tested this out yet ? Stable? daumm im sounding like a dumb person lol
Would be nice daily driver? so many questions
Screenshots?

Can't flash this, it just comes up with an error in TWRP as soon as you try unfortunately. Guess it was a blind build that hasn't been tested.

lukeaddison said:
Can't flash this, it just comes up with an error in TWRP as soon as you try unfortunately. Guess it was a blind build that hasn't been tested.
Click to expand...
Click to collapse
You shouldnt flash it in twrp, you need to flash it from your pc. And it works perfect, i used this Rom for two days rooted with xposed and no Problems or Bugs except of the camera. I dont think that we need Screenshots because its pure aosp.

Trilliard said:
You shouldnt flash it in twrp, you need to flash it from your pc. And it works perfect, i used this Rom for two days rooted with xposed and no Problems or Bugs except of the camera. I dont think that we need Screenshots because its pure aosp.
Click to expand...
Click to collapse
Thanks for the information. This is the first none stock ROM that I've tried flashing on a Sony device. It's all a bit difficult compared to other devices I've used.
What commands do I use to flash this ROM?
I'm an idiot and didn't read the first post properly!

It's hard to download(ಥ_ಥ)

Trilliard said:
You shouldnt flash it in twrp, you need to flash it from your pc. And it works perfect, i used this Rom for two days rooted with xposed and no Problems or Bugs except of the camera. I dont think that we need Screenshots because its pure aosp.
Click to expand...
Click to collapse
so camera is not working at all? glad to hear that rom is working fine anyway.

justanpotato said:
so camera is not working at all? glad to hear that rom is working fine anyway.
Click to expand...
Click to collapse
Camera is working, but the pictures are not good. From ten tries one picture is good. Sony knows about that problem with the AOSP Camera Driver for MM but it doesnt look like they wanne fix it.

Took me a while to get it up and running but I'm there now - all seems good (apart from the known Sony camera issues).

Where is AOSP for E6533……
Thanx

Sorry for the noobish question, Camera Bug means none of the camera apps will work? or bug with only stock camera?
Can anyone clarify me plz....

Camera is working, but the pictures are not good.
[email protected] said:
Sorry for the noobish question, Camera Bug means none of the camera apps will work? or bug with only stock camera?
Can anyone clarify me plz....
Click to expand...
Click to collapse
Camera is working, but the pictures are not good. From ten tries one picture is good. Sony does know about this problem, i dont know when they are going to fix it.

Is this ROM going to be updated?

Hey, FXP made an Update... finally, linked it in the OP
I dont know anything about the changelog, going to test it.
Edit: Downloaded, flashed and booted... that was fast... lol forgot to clear my userdata result in bootloop xD
Ok Camera is complete broken now. Dont know what FXP made but its not good and access to twrp is still missing.

Sony are a joke when is comes to open source. All there DRM features have been ported already and always will be so why not just give it out so we can have a working AOSP ROM and custom! I'm no developer but these issues with camera and that can be easily fixed. It's definitely my last sony. Going Nexus next or the lg v20 might be my thing.

We have an update from friday with WORKING CAMERA on AOSP!!!! YEAH!!!!
And the pictures are good. Didnt test everything yet but looks quit good. I will try it for daily driver the next days.
Edit: It´s hard to make pictures in a dark area but if you have enough light around there the pictures are usable.

How is performance and (over)heat with AOSP?
Like is the snapdragon better controlled than on Stock? Would be a dream to be honest.

I have not tried the latest AOSP but generally yes performance and battery should be better as it's has a lot smaller footprint than Sony stock.
Will take a backup of my setup later and give this a shot. I see the AOSP 7.0 files are up too. Would porting snap camera or building cm from this not improve camera function more?

After using the latest build for a couple of hours i have to say... wow this is a very fast system. Everything i testet is working, only thing which isnt perfect is still the camera, focus is sometimes hard and as i said you need enough light. But as the dev from z5 made the camera working much better and this is the first rls with working camera overall for z3+ i think its just a question of time when we will have a perfect camera.
Performance is much better than with every Stock or Stock based Rom. Overheating issue sure still exists, this is caused by the processor not by the software. And we dont have a custom kernel for AOSP which is underclocked by default. I use kernel adiutor to make this and it helps mostly. The average Ram usage is at 800-900mb with GApps installed
Sad that Sony has to release three newer flagships before they publish the neccessary stuff to build aosp bugfree.
Oh and yes twrp still doesnt work, only way is still boot twrp from pc via fastboot.